diff --git a/marked/H/T-REC-H.100-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.100-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/H/T-REC-H.100-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/H/T-REC-H.100-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/H/T-REC-H.100-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69fad3ac71201ac6bea51a43abb1e4fe0aee4a06 --- /dev/null +++ b/marked/H/T-REC-H.100-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df8219974b8a84147118f45987edb6ae88b29432509baf13f1f3d33d91dd9340 +size 46134 diff --git a/marked/H/T-REC-H.100-198811-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/H/T-REC-H.100-198811-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d58d184fcb4ca96c47405eee36d01cb7a0ca861f --- /dev/null +++ b/marked/H/T-REC-H.100-198811-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5a9649e5c594f4dd55c55e695fd6cfa078956d77635669f4a01a2b7f07e8416 +size 30336 diff --git a/marked/H/T-REC-H.100-198811-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/H/T-REC-H.100-198811-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf1c24b86d5fd197077079c2ef07a1bfd82266ea --- /dev/null +++ b/marked/H/T-REC-H.100-198811-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2903ca09732428000b0a929f178b350b7ab314133f953194af1f1d3e25d78459 +size 36532 diff --git a/marked/H/T-REC-H.100-198811-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/H/T-REC-H.100-198811-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aef92a722b7ca67f5f787bc8242bfde6c3835744 --- /dev/null +++ b/marked/H/T-REC-H.100-198811-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a0ba617a5f338bca0edb11b7a126be0fb30f2497b2ba26f08dbec7c37803b6b +size 78806 diff --git a/marked/H/T-REC-H.100-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.100-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e343a55d5afef87186fbf87c03b79c8ee63acf78 --- /dev/null +++ b/marked/H/T-REC-H.100-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d80c4ef582ff915819438f0eb5d73376cb7d1d44beba04538662c6b68f4a5073 +size 34164 diff --git a/marked/H/T-REC-H.100-198811-I_PDF-E/f6d72d7c790e7f585532140f3971639a_img.jpg b/marked/H/T-REC-H.100-198811-I_PDF-E/f6d72d7c790e7f585532140f3971639a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afa9ee6a9a5aa4404b4ed329306232959183af4a --- /dev/null +++ b/marked/H/T-REC-H.100-198811-I_PDF-E/f6d72d7c790e7f585532140f3971639a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05056f2ed9f65789410e2431ee7016c95b5822b1896d5abb180a011ae9c9fc5a +size 46333 diff --git a/marked/H/T-REC-H.100-198811-I_PDF-E/raw.md b/marked/H/T-REC-H.100-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ec134aaa6100ef08f7976a2416acaaf7c5ba31ae --- /dev/null +++ b/marked/H/T-REC-H.100-198811-I_PDF-E/raw.md @@ -0,0 +1,236 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**H.100** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**LINE TRANSMISSION +OF NON-TELEPHONE SIGNALS** + +--- + +**VISUAL TELEPHONE SYSTEMS** + +**ITU-T Recommendation H.100** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation H.100 was published in Fascicle III.6 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **VISUAL TELEPHONE SYSTEMS** + +*(former Recommendation H.61, Geneva, 1980; +amended at Malaga- Torremolinos, 1984 +and at Melbourne, 1988)* + +## **1 Definition** + +The **visual telephone service** is generally a two-way telecommunication service which uses a switched network of broadband analogue and/or digital circuits to establish connections among subscriber terminals, primarily for the purpose of transmitting live or static pictures. + +Special application one-way systems, e.g. surveillance and some information retrieval systems, or a non-switched videoconference service, can be regarded as degenerate cases of the visual telephone service. + +The visual telephone service also includes the associated speech. + +## **2 Facilities to be offered** + +The design of the visual telephone service shall be such as to offer at least the following basic facilities: + +- a) Transmission of live pictures such as head and shoulders of one person or a small group of persons, with moderate definition. +- b) Transmission of the associated speech. +- c) Transmission of graphics information such as drawings and documents with high definition (e.g. 625 lines or 525 lines). +- d) Video conference service, with or without the use of split-screen techniques. + +The above-mentioned services shall, in general, be bi-directional, although uni-directional operation should be possible. Also, some of the facilities can be omitted, if not required, in order to minimize costs. + +*Note* – At the subscriber terminal, the use of ancillary equipments, e.g. for document reproduction, video tape recordings, etc., shall be possible. + +## **3 System parameters** + +### **3.1 Picture standards** + +3.1.1 The video standards of the subscriber sets shall be compatible with, readily convertible to, or identical to, the local broadcast television standards. + +3.1.2 Two classes of picture standards are recommended for the visual telephone system. They are given in Table 1/H.100. + +TABLE 1/H.100 + +#### **Picture standards** + +| Class | Items | The region to which the figures should be applied | | +|----------|-----------------------------------------------|-----------------------------------------------------------|-----------------------------------------------------------| +| | | Regions where TV broadcasting uses 25 pictures per second | Regions where TV broadcasting uses 30 pictures per second | +| a | Number of horizontal scanning lines . . . . . | 625 | 525 | +| | Pictures per second . . . . . | 25
(2:1 interleaved) | 30
(2:1 interleaved) | +| | Aspect ratio . . . . . | 4:3 | 4:3 | +| | Video bandwidth. . . . . | 5 MHz | 4 MHz | +| b | Number of horizontal scanning lines . . . . . | 313 | 263 | +| | Pictures per second . . . . . | 25
(2:1 interleaved) | 30
(2:1 interleaved) | +| | Aspect ratio . . . . . | 4:3 | 4:3 | +| | Video bandwidth . . . . . | 1 MHz | 1 MHz | + +Class *a* standards are identical to the local broadcast video standards and will, in most cases, give sufficient definition for real-time picture transmission of a group of people (e.g. for conferencing) and of graphics material. + +Class *b* standards give sufficient definition for real-time transmission of a head and shoulder picture of one person or a small group. For the transmission of graphics information or other still pictures with high definition, a slow-scan technique has to be applied. For instance, a system using 625 or 525 horizontal scanning lines and 5, or less, pictures per second which gives a Class *a* definition in the 1 MHz bandwidth. + +Further study is required to define slow scanning parameters. + +## 4 Characteristics relating to split-screen techniques for Class *a* television conference systems1) + +In television conference systems which use split-screen techniques to make more effective use of the picture area, the following features for the terminals and transmitted signals are recommended. Preferred seating arrangement for such systems are given in Annex A. + +### 4.1 *Picture format* + +The transmitted picture should be 4 : 3 aspect ratio, split into upper and lower halves corresponding to the groups of seats. Viewed from the camera system, the left-hand group should be in the upper half and the right-hand group in the lower half. + +The split should occur at the end of lines 166 and 479 for 625-line television systems and at the end of line 142 in Field 1 and line 141 in Field 2 for 525-line television systems, as shown in Figure 1/H.100. + +Before display, the receive equipment may discard half lines and first and last lines which are liable to be averaged during standards conversion or vertical aperture correction of mixed signals. + +### 4.2 *Identification signal for split-screen system* + +#### 4.2.1 *Analogue video signals* + +The identification signal for split-screen system should be inserted in the vertical blanking period, because the control is required for each television frame or field. + +1) Split-screen techniques for systems using Class *b* standards require future study. + +The line where the identification signal is inserted and its signal format are under study. + +#### 4.2.2 *Digital video signals* + +An identification signal for split-screen system should be provided. In the case of codecs in Recommendations H.120 and H.130 the format shall be that specified in Recommendation H.130. + +### 4.3 *Compatibility with non-split-screen systems* + +The simplest kind of a video telephone terminal is composed of a single camera and other equipments. These terminals may be interconnected with split-screen system terminals. In that case, mechanical masks (if used) for the two split-screen displays (aspect ratio = 4 : 1.5) need to be removed, or if a display with 4 : 3 aspect ratio needs to be installed additionally. + +### 4.4 *Cameras and displays arrangement* + +The entrance pupils of the TV camera optical system should be as near as possible to the centre of the TV display showing remote conferees, in order to minimize errors in eye contact angle. + +Unless means are employed to place these pupils in line with the display, e.g. by use of half-silvered mirrors, the camera system should be sited above the display and central to it. + +In order to keep the maximum horizontal errors as small as possible, the cameras used had better be in a cross-fire system, as for example in Figure A-1/H.100, and the camera/display assembly should be sited on the central axis of the terminal. However, in some cases, adoption of parallel-fire system as shown also in Figure A-1/H.100 is necessary due to a restriction in equipment arrangement. + +Whether the two cameras are arranged in cross-fire or parallel-fire is left open to each Administration since the selection does not affect the interconnection of different systems. + +### 4.5 *Picture processing methods at transmitting terminals* + +In order to obtain the correct relationship between the signals from the two cameras for split-screen working, the cameras should be synchronized but the vertical drive pulses should be rephased. The drive to one should be advanced by one quarter of the vertical period while the drive to the other should be retarded by the same amount. This causes a central strip of the target of each camera tube to be used and so minimizes the effects of distortions in the corners of the targets. Figure B-1a)/H.100 illustrates the preferred method. + +Alternative methods which are not recommended although they do not give rise to problems of end-to-end compatibility are compared in Annex B. + +### 4.6 *Receiving equipment* + +The receiving equipment should be capable of working with discontinuities in the received signal that may be caused by switching between non-synchronous video sources. + +*Note* – A split-screen device should be capable of working with a codec with the input and output frequency tolerances as specified in Recommendation H.120. + +![Diagram of the 625-line television system vertical format. It shows two fields, Field 1 and Field 2, each divided into 'Left hand Group' and 'Right hand Group'. Line numbers are marked at the top: 23 1/2, 166, 167, 310, 336, 479, 480, 623 1/2. The number of lines for each segment is marked at the bottom: 25, 143 1/2, 144, 25, 144, 143 1/2. The total number of lines for each field is 312 1/2.](547f726730e589392f239257a833ede3_img.jpg) + +Diagram of the 625-line television system vertical format. It shows two fields, Field 1 and Field 2, each divided into 'Left hand Group' and 'Right hand Group'. Line numbers are marked at the top: 23 1/2, 166, 167, 310, 336, 479, 480, 623 1/2. The number of lines for each segment is marked at the bottom: 25, 143 1/2, 144, 25, 144, 143 1/2. The total number of lines for each field is 312 1/2. + +Left hand group: first complete lines 24 and 336 +last complete lines 166 and 479 +Right hand group: first complete lines 167 and 480 +last complete lines 310 and 622 + +Lines 16-20 inclusive and 329-333 inclusive may contain identification, control or test signals. + +#### *a) 625-line television system* + +![Diagram of the 525-line television system vertical format. It shows two fields, Field 1 and Field 2, each divided into 'Left hand Group' and 'Right hand Group'. Line numbers are marked at the top: 22, 142, 143, 263 1/2, 21 1/2, 141, 142, 262. The number of lines for each segment is marked at the bottom: 21, 121, 120 1/2, 21, 120 1/2, 121. The total number of lines for each field is 262 1/2. A small code 'CCITT-32372' is visible at the bottom right.](f6d72d7c790e7f585532140f3971639a_img.jpg) + +Diagram of the 525-line television system vertical format. It shows two fields, Field 1 and Field 2, each divided into 'Left hand Group' and 'Right hand Group'. Line numbers are marked at the top: 22, 142, 143, 263 1/2, 21 1/2, 141, 142, 262. The number of lines for each segment is marked at the bottom: 21, 121, 120 1/2, 21, 120 1/2, 121. The total number of lines for each field is 262 1/2. A small code 'CCITT-32372' is visible at the bottom right. + +Left hand group: first complete lines 22 (Field 1, 2) +last complete lines 142 (Field 1), 141 (Field 2) +Right hand group: first complete lines 143 (Field 1), 142 (Field 2) +last complete lines 262 (Field 1, 2) + +Lines 10-21 inclusive in Field 1 and 9 1/2-21 1/2 inclusive in Field 2 may contain identification, control or test signals. + +#### *b) 525-line television system* + +*Note 1* — The method of defining the line number is following Fig. 2-1 of CCIR Report 624 for 625 system, and Fig. 2-3 for 525 system. + +*Note 2* — The notation which is used for line numbers is as follows. Line 23 1/2 means that the picture starts (or finishes) half-way along line number 23. When totalling lines, a half-line is shown separately, e.g. 143 + 1/2. + +FIGURE 1/H.100 +Vertical format of split-screen video signal + +## ANNEX A (to Recommendation H.100) + +### **Seating arrangements when applying split-screen techniques for class a system** + +Preferred arrangements for video conferences using split-screen techniques are: + +A.1 The conference terminal accommodation should be for 6 primary seats in two adjacent groups of 3 as shown in Figure A.1/H.100. + +Provision for additional seating behind may be made, so long as allowance is made for the central gap between the two halves. For example, 4 additional persons may be seated on a second row as in the Figure. + +A.2 The chairman's position should be in the centre of the left-hand group of seats (viewed from the camera) with user controls accessible from both this position and the one of the chairman's left. + +Consequently, when split-screen pictures are displayed, stacked as received (i.e. shown as 3 over 3), the chairman's position is standardized as top centre. + +The suite of 3 chairs containing the chairman's position should also be regarded as the primary position for occasions when only half of a studio is in use. Such standardization is necessary for connection of 3 studios in conference using time-division multiplex of pairs of TV signals to share a common trunk between two studios. + +![Studio plan view diagram showing seating arrangements and camera positions.](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +The diagram illustrates a studio plan view for video conferencing. It shows a semi-circular arrangement of seats divided into two main groups: 'Primary seating (2 groups of 3)' and 'Secondary seating (2 groups of 2)'. The 'Preferred position for chairman' is marked in the center of the left-hand primary seating group. A 'Desk' is positioned in front of the seating area. Two 'Cameras' are shown on the right, with 'Optical axes' indicated by dashed lines. The cameras are labeled 'CCITT - 32351'. The diagram is divided into 'Top half scene' and 'Bottom half scene' by a horizontal line. A note indicates that solid line cameras are for cross-fire and dashed line cameras are for parallel-fire. The total seating in camera is 6 primary and 4 secondary. + +Studio plan view diagram showing seating arrangements and camera positions. + +*Note* – Solid line cameras are for cross-fire. Dashed line cameras are for parallel-fire. + +FIGURE A-1/H.100 +Studio plan view + +## ANNEX B + +(to Recommendation H.100) + +### **Picture processing methods in transmitting terminals** + +Alternative methods of obtaining the split-screen signal which are compatible with the recommended method and which might be useful for experiments and demonstrations are shown in *b)* and *c)* of Figure B-1/H.100. In method *b)*, the two cameras are directed upward and downward to pick up right and left halves of the conferencing room, respectively. Since circumferences of target and scanning areas are used, geometric and brightness distortions tend to occur. In method *c)*, vertical deflection currents are biased by the quantity corresponding to $\pm 1/4$ of target height. Vertical deflection bias adjustment is needed every time cameras are exchanged. In method *a)*, the vertical driving pulses are phase-shifted by $\pm 1/4$ V. The recommended method, *a)*, avoids the problems of methods *b)* and *c)*. + +![Diagram (a) showing vertical driving pulses being phase shifted. A camera on the left points to two processing blocks labeled 'Shifted VD1' and 'Shifted VD2'. These blocks output to two intermediate frames showing people. The top frame has regions labeled B' and B, with a dashed line between them. The bottom frame has regions labeled A' and A, also with a dashed line. Both intermediate frames then point to a final frame on the right, which is divided into regions A and B by a dashed line.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Diagram (a) showing vertical driving pulses being phase shifted. A camera on the left points to two processing blocks labeled 'Shifted VD1' and 'Shifted VD2'. These blocks output to two intermediate frames showing people. The top frame has regions labeled B' and B, with a dashed line between them. The bottom frame has regions labeled A' and A, also with a dashed line. Both intermediate frames then point to a final frame on the right, which is divided into regions A and B by a dashed line. + +a) Vertical driving pulses are phase shifted + +![Diagram (b) showing cameras directed upward and downward. A camera on the left has two output paths labeled 'Up' and 'Down'. The 'Up' path goes to a processing block and then to a frame with regions B' and B. The 'Down' path goes to a block labeled 'VD' and then to a frame with regions A' and A. Both frames point to a final frame on the right divided into regions A and B.](562f471e8153729557e6a4ee6343c32c_img.jpg) + +Diagram (b) showing cameras directed upward and downward. A camera on the left has two output paths labeled 'Up' and 'Down'. The 'Up' path goes to a processing block and then to a frame with regions B' and B. The 'Down' path goes to a block labeled 'VD' and then to a frame with regions A' and A. Both frames point to a final frame on the right divided into regions A and B. + +b) Cameras are directed upward and downward + +![Diagram (c) showing vertical deflection currents being biased. A camera on the left points to two processing blocks. The top block outputs to a frame with a 'Scan area' (top part) and a 'Target area' (bottom part), labeled with B' and B. The bottom block, labeled 'VD', outputs to a frame with regions A' and A. Both frames point to a final frame on the right divided into regions A and B. The text 'CCITT-49981' is in the bottom right corner.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +Diagram (c) showing vertical deflection currents being biased. A camera on the left points to two processing blocks. The top block outputs to a frame with a 'Scan area' (top part) and a 'Target area' (bottom part), labeled with B' and B. The bottom block, labeled 'VD', outputs to a frame with regions A' and A. Both frames point to a final frame on the right divided into regions A and B. The text 'CCITT-49981' is in the bottom right corner. + +c) Vertical deflection currents are biased + +VD = vertical deflection + +FIGURE B-1/H.100 +Picture processing method at transmitting terminals \ No newline at end of file diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/raw.md b/marked/H/T-REC-H.120-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..835acd68e5c2cdad2b6fb22883065b74cad27ebc --- /dev/null +++ b/marked/H/T-REC-H.120-199303-I_PDF-E/raw.md @@ -0,0 +1,2494 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.120** + +(03/93) + +**LINE TRANSMISSION +OF NON-TELEPHONE SIGNALS** + +--- + +**CODECS FOR VIDEOCONFERENCING +USING PRIMARY DIGITAL GROUP +TRANSMISSION** + +**ITU-T Recommendation H.120** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation H.120 was revised by the ITU-T Study Group XV (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +# --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +*Page* + +| | | | +|-----|----------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 1 | A codec for 625-lines, 50 fields/s and 2048 kbit/s transmission for intra-regional use and capable of interworking with the codec of 2..... | 1 | +| 1.1 | Scope ..... | 1 | +| 1.2 | Brief specification..... | 2 | +| 1.3 | Video interface..... | 3 | +| 1.4 | Source coder ..... | 3 | +| 1.5 | Video multiplex coding ..... | 8 | +| 1.6 | Transmission coding..... | 11 | +| 1.7 | Error correction..... | 12 | +| 2 | Codecs not requiring separate television standards conversion when used on interregional connections .... | 13 | +| | A codec for 525-line, 60 fields/s and 1544 kbit/s transmission for intra-regional use and capable of interworking with the codec of clause 1 ..... | 13 | +| 2.1 | Introduction ..... | 13 | +| 2.2 | Brief specification..... | 13 | +| 2.3 | Video interface..... | 14 | +| 2.4 | Source coder ..... | 14 | +| 2.5 | Video multiplex coding ..... | 15 | +| 2.6 | Transmission coding..... | 15 | +| 3 | A codec for 525-lines, 60 fields/s and 1544 kbit/s transmission for intra-regional use ..... | 16 | +| 3.1 | Introduction ..... | 16 | +| 3.2 | Outline of codec..... | 16 | +| 3.3 | Brief specification..... | 16 | +| 3.4 | Video interface..... | 18 | +| 3.5 | Pre- and post-processing..... | 19 | +| 3.6 | Source coding ..... | 21 | +| 3.7 | Audio coding ..... | 44 | +| 3.8 | Transmission coding..... | 44 | +| | Annex A – Graphics option – 625 line ..... | 46 | +| A.1 | Introduction ..... | 46 | +| A.2 | Graphics codec for videoconferencing graphics – Mode 1 ..... | 46 | +| A.3 | Graphics codec for videoconferencing-graphics – Mode 2 ..... | 48 | +| | Annex B – Encryption option – 625 line ..... | 50 | +| | Annex C – Graphics option – 525 line ..... | 50 | +| C.1 | Introduction ..... | 50 | +| C.2 | Facilities..... | 50 | +| C.3 | Coding ..... | 50 | +| C.4 | Transmission and synchronization..... | 51 | +| C.5 | Decoder..... | 51 | +| | Annex D – Encryption option – 525 line..... | 52 | +| | Annex E – Colour decoding and coding filters ..... | 52 | +| E.1 | Configuration..... | 52 | +| E.2 | Basic filter characteristics..... | 54 | +| E.3 | Advanced filter characteristics..... | 54 | +| | Annex F – An example of coding control sequence..... | 55 | +| | Annex G – Examples of entropy coding ..... | 56 | + +| | Page | +|----------------------------------------------------------------------------------|-------------| +| Appendix I – Outline description of operation of codecs in clauses 1 and 2 ..... | 58 | +| Appendix II..... | 59 | +| II.1    Cursor data..... | 59 | +| II.2    Frame structure ..... | 60 | +| II.3    Transmission of cursor data ..... | 60 | +| References ..... | 60 | + +# INTRODUCTION + +Clause 1 specifies the codec, developed for operation with the 625-line, 50 field/s television standard and the 2048 kbit/s primary digital group. Its architecture has been chosen to permit variations in the detailed design of certain of the functional elements having the greatest influence on the picture quality. This enables future developments, aimed at improving the performance, to be incorporated without affecting the ability of different coders and decoders to interwork. For this reason, no details are given of such items as motion detectors or spatial and temporal filters. The Recommendation confines itself to the details necessary to enable a decoder correctly to interpret and decode the received signals. + +The annexes to clause 1 which can be found at the end of this Recommendation give details of some additional optional features which may be provided to supplement the basic design. + +Under the general heading of codecs not requiring separate television standards conversion when used on interregional connections, clause 2 describes a version of the codec for 525-line, 60 field/s and 1544 kbit/s operation which also provides automatic television standards conversion when connected to the version of the codec described in 1 via a re-multiplexing unit (to convert between frame structures defined in 2.1 and 2.3/G.704) at the junction of the 2048 and 1544 kbit/s digital paths. This codec is also suitable for use within regions using the 525-line, 60 field/s television standard and 1544 kbit/s transmission. + +Other implementations of 2 are to be studied, for example: + +- a version of the codec for 625-line, 50 field/s and 2048 kbit/s operation capable of interworking with the codec described in 3; +- a version of the codec for 525-line, 60 field/s and 2048 kbit/s operation capable of interworking with the codec described in 1. + +Clause 3 describes a codec for intra-regional use in 525-line, 60 field/s and 1544 kbit/s regions. + +The frame structures associated with the codecs described in this Recommendation are to be found in Recommendation H.130. + +As the codecs are complex items using combined intraframe and interframe picture-coding techniques which tend to be known only to specialists, Appendix I is provided giving a brief outline of the principles involved in the codecs of 1 and 2. + + + +# CODECS FOR VIDEOCONFERENCING USING PRIMARY DIGITAL GROUP TRANSMISSION + +*(Malaga-Torremolinos, 1984; amended at Melbourne, 1988 +and at Helsinki, 1993)* + +The CCITT, + +*considering* + +- (a) that there is growing evidence of a customer demand for a videoconference service; +- (b) that circuits to meet this demand can, at present, be provided effectively by digital transmission using the primary digital group; +- (c) that the existence of different digital hierarchies and different television standards in different parts of the world complicates the problems of specifying coding and transmission standards for international connections; +- (d) that the eventual use of switched digital transmission networks should be taken into account, + +*appreciating* + +that rapid advances are being made in research and development of video coding and bit-rate reduction techniques which may lead to further Recommendations being proposed for videoconferencing at bit rates which are multiples or submultiples of 384 kbit/s during subsequent study periods so that this Recommendation may be considered as the first of an evolving series of Recommendations, + +*and noting* + +that it is a basic objective of the CCITT to recommend a unique solution for international connections as far as possible, + +*recommends* + +that the codecs having signal processing and interface characteristics described in clauses 1, 2 and 3, should be used for international videoconference connections. + +NOTE – Codecs of types other than those described in this Recommendation are not precluded. + +# 1 A codec for 625-lines, 50 fields/s and 2048 kbit/s transmission for intra-regional1) use and capable of interworking with the codec of clause 2 + +## 1.1 Scope + +Clause 1 defines the essential features of a codec for the digital transmission, at 2048 kbit/s, of signals for videoconference or visual telephone service in accordance with Recommendation H.100. The video input to the coder and output from the decoder in a 625-line, 50 fields/s signal, according to the “Class *a*” standard of Recommendation H.100, or alternatively, the 313-line, 50 fields/s signal of the “Class *b*” standard. Provision is also made for a sound channel and optional data channels. A brief description of the operation of the codec is given in Appendix I. + +--- + +1) The term “intra-regional” is used here to describe connections within a group of countries which share a common television scanning standard and a common digital hierarchy, and may or may not be in geographical proximity. The term “inter-regional” is used here to describe connections between groups of countries which have different television scanning standards and/or different digital hierarchies. + +The Recommendation starts with a brief specification of the codec (see 1.2) and a description of the video interface. This is followed by details of the source coder (see 1.4) which provides analogue-to-digital conversion followed by recoding with substantial redundancy reduction in the face-to-face mode. Subclause 1.5 deals with the video multiplex coder which inserts instructions and addresses into the digitized video signal to control the decoder so that it correctly interprets the signals received. Subclause 1.6 describes the transmission coder which arranges the various digital signals (video, sound, data, signalling) into a form compatible with Recommendation G.732 for transmission over 2048 kbit/s digital paths. Subclause 1.7 describes optional forward error correction facilities. Provision is made in the digital frame structure for the inclusion of other optional facilities such as a graphics mode, encryption and multipoint conferencing. Details of such facilities as are at present available are given in the annexes to this Recommendation. + +## **1.2 Brief specification** + +### **1.2.1 Video input/output** + +The video input and output are standard 625-line, 50 field/s colour or monochrome television signals. The colour signals are in, or converted to, component form. Colour and monochrome operation are fully compatible. + +### **1.2.2 Digital output/input** + +The digital output and input are at 2048 kbit/s, compatible with the frame structure of Recommendation G.704. + +### **1.2.3 Sampling frequency** + +The video sampling frequency and the 2048 kHz network clock are asynchronous. + +### **1.2.4 Coding techniques** + +Conditional replenishment coding supplemented by adaptive digital filtering, differential PCM and variable-length coding are used to achieve low bit-rate transmission. + +### **1.2.5 Audio channel** + +An audio channel using 64 kbit/s is included. At present, coding is A-law according to Recommendation G.711, but provision is made for future use of more efficient coding. + +### **1.2.6 Mode of operation** + +The normal mode of operation is full duplex. + +### **1.2.7 Codec-to-network signalling** + +An optional channel for codec-to-network signalling is included. This conforms to emerging ideas in CCITT for switching 2-Mbit/s paths in the ISDN. + +### **1.2.8 Data channels** + +Optional $2 \times 64$ kbit/s and $1 \times 32$ kbit/s data channels are available. These are used for video if not required for data. + +### **1.2.9 Forward error correction** + +Optional forward error correction is available. This is required only if the long-term error rate of the channel is worse than 1 in $10^6$ . + +### **1.2.10 Additional facilities** + +Provision is made in the digital frame structure for the future introduction of encryption, a graphic mode and multipoint facilities. + +### 1.2.11 Propagation delay + +When the coder buffer is empty and the decoder buffer full, the coder delay is less than 5 ms and the decoder delay is $130 \pm 30$ ms at 2 Mbit/s or $160 \pm 36$ ms when only 1.5 Mbit/s are in use2). + +## 1.3 Video interface + +The normal video input is a 625-line, 50 field/s signal in accordance with CCIR Recommendation 472. When colour is being transmitted, the input (and output) video signals presented to the analogue/digital convertors (and from the digital/analogue convertors) are in colour-difference component form. The luminance and colour-difference components, $E'_Y$ , $(E'_R - E'_Y)$ and $(E'_B - E'_Y)$ are as defined in CCIR Report 624. The analogue video input (and output) interface with the codec may be in the form of colour-difference components, colour components (R, G, B) or as a composite colour signal. The video interface is as recommended in CCIR Recommendation 656. + +Optionally, any other video standard which can be converted to give 143 active lines per field may be used. + +## 1.4 Source coder + +### 1.4.1 Luminance component or monochrome + +#### 1.4.1.1 Analogue-to-digital conversion + +The signal is sampled to produce 256 picture samples per active line (320 samples per complete line). The sampling pattern is orthogonal and line, field and picture repetitive. For the 625-line input, the sampling frequency is 5.0 MHz, locked to the video waveform. + +Uniformly quantized PCM with 8 bits/sample is used. + +Black level corresponds to level 16 (00010000). + +White level corresponds to level 239 (11101111). + +PCM code words outside this range are forbidden (the codes being used for other purposes). For the purposes of prediction and interpolation, the final picture element in each active line (i.e. picture element 255) is set to level 128 in both encoder and decoder. + +In all arithmetic operations, 8-bit arithmetic is used and the bits below the binary point are truncated at each stage of division. + +#### 1.4.1.2 Pre- and post-filtering + +In addition to conventional anti-aliasing filtering prior to analogue-to-digital conversion, a digital transversal filtering operation is carried out on the 625-line signal to reduce the vertical definition of the picture prior to conditional replenishment coding. As a result of this process, 143 active lines per field are used instead of the $287\frac{1}{2}$ active lines of the 625-line signal, although the effective vertical definition is greater than one-half of that of a normal 625-line display. An interpolation process in the decoder restores the 625-line signal waveform. + +#### 1.4.1.3 Conditional replenishment coding + +A movement detector identifies clusters of picture elements which are deemed to be moving. The basic feature is a frame memory which stores 2 fields of 143 lines, each line containing 256 addressable points. The memory is updated at the picture rate and differences between the incoming signal and the corresponding stored values are used to determine the moving area in the coder. A similar frame memory must exist at the decoder and be similarly updated under the control of addressing information received from the coder. It is not necessary to specify the techniques used for movement detection because they do not affect interworking, although they do affect the resultant picture quality. + +Detected moving areas are transmitted by differential PCM with a maximum of 16 quantization levels. The first picture element in each moving area is transmitted by PCM. Variable-length coding is used on the DPCM code words. + +--- + +2) These are typical figures. The delays depend on the detailed implementation used. + +The first picture element of each cluster and the complete PCM lines, when they are transmitted to provide systematic or forced updating, are coded in accordance with 1.4.1.1. + +##### 1.4.1.3.1 DPCM prediction algorithm + +The algorithm used for DPCM prediction is: + +$$X = \frac{A + D}{2}, \text{ where } X \text{ is the sample being predicted.}$$ + +See Figure 1. + +For the purpose of prediction, line and field blanking are assumed to be at level 128 (out of 256). + +![Diagram illustrating the DPCM prediction algorithm. It shows two horizontal lines: 'Previous line' and 'Previous field'. The 'Previous line' has three points labeled B, C, and D. The 'Previous field' has four points labeled A_S, A, X, and T1513820-93d01. The points A, C, and D are vertically aligned, indicating that X is the sample being predicted from A and D.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +The diagram shows two horizontal lines representing video fields. The top line is labeled 'Previous line' and contains three points marked with black dots, labeled B, C, and D from left to right. The bottom line is labeled 'Previous field' and contains four points marked with black dots, labeled AS, A, X, and T1513820-93d01 from left to right. Vertical alignment is indicated by the labels: B is above A, C is above X, and D is above T1513820-93d01. This illustrates that the sample X is predicted from the sample A on the previous field and the sample D on the previous line. + +Diagram illustrating the DPCM prediction algorithm. It shows two horizontal lines: 'Previous line' and 'Previous field'. The 'Previous line' has three points labeled B, C, and D. The 'Previous field' has four points labeled A\_S, A, X, and T1513820-93d01. The points A, C, and D are vertically aligned, indicating that X is the sample being predicted from A and D. + +FIGURE 1/H.120 +Identification of samples + +##### 1.4.1.3.2 Quantization law and variable-length coding + +511 input levels are quantized to a maximum of 16 output levels. The quantizer does not assume the use of modulo 256 arithmetic. + +The quantization law and associated variable-length codes which are used for both luminance and colour-difference picture elements in moving areas which are not horizontally subsampled are given in Table 1. + +**Error! Cannot open file.** + +The end-of-cluster code is 1 0 0 1 and is designated as code number 11. The end-of-cluster code is omitted at the end of the last cluster in a line irrespective of whether it is a luminance cluster or a colour-difference cluster. + +#### 1.4.1.4 Subsampling + +As the buffer fills, horizontal subsampling and field/field subsampling are introduced. + +##### 1.4.1.4.1 Horizontal subsampling + +Horizontal subsampling is carried out only in moving areas. Normally, in this mode, only even elements are transmitted on even numbered lines and odd elements on odd numbered lines. This gives rise to a line quincunx pattern in moving areas. + +Omitted elements are interpolated in the decoder by averaging the two horizontally adjacent elements. + +Interpolated picture elements are placed in the frame stores. A moving area cluster will always start with a PCM value and finish with a transmitted DPCM picture element, even during subsampling. This means that in some instances, the transmitted cluster needs to be extended by one element in comparison with the moving area declared by the movement detector. At the end of the active line, however, this cannot occur as clusters must not extend into blanking, so cluster shortening by one element can be necessary. + +TABLE 1/H.120 + +###### **Code table for non-horizontally-subsampled moving areas** + +| Input levels | Output levels | Variable-length code | Code No. | +|--------------|---------------|----------------------|----------| +| -255 to -125 | -141 | 1 0 0 0 0 0 0 0 0 1 | 17 | +| -124 to -95 | -108 | 1 0 0 0 0 0 0 0 1 | 16 | +| -94 to -70 | -81 | 1 0 0 0 0 0 0 1 | 15 | +| -69 to -49 | -58 | 1 0 0 0 0 0 1 | 14 | +| -48 to -32 | -39 | 1 0 0 0 0 1 | 13 | +| -31 to -19 | -24 | 1 0 0 0 1 | 12 | +| -18 to -9 | -13 | 1 0 1 | 10 | +| -8 to -1 | -4 | 1 1 | 9 | +| 0 to 7 | +3 | 0 1 | 1 | +| 8 to 17 | +12 | 0 0 1 | 2 | +| 18 to 30 | +23 | 0 0 0 1 | 3 | +| 31 to 47 | +38 | 0 0 0 0 1 | 4 | +| 48 to 68 | +57 | 0 0 0 0 0 1 | 5 | +| 69 to 93 | +80 | 0 0 0 0 0 0 1 | 6 | +| 94 to 123 | +107 | 0 0 0 0 0 0 0 1 | 7 | +| 124 to 255 | +140 | 0 0 0 0 0 0 0 0 1 | 8 | + +Adaptive element subsampling allows the transmission of normally omitted elements, either to remove interpolation errors or, to provide a softer switch to subsampling and thus improve the picture quality. The signalling of the extra elements is achieved by using, on horizontally subsampled lines only, 8 quantizing levels for normally transmitted elements and the remaining 8 levels for the extra elements. Also, a cluster can finish either on a normally transmitted element or an “extra” element. + +During horizontally subsampled lines, the quantization law and variable-length code shown in Table 2 will be used for both luminance and colour-difference samples in moving areas. + +With regard to prediction, if element A is a non-transmitted element in a moving area, it is replaced by $A_s$ (see Figure 1); if element D is part of a subsampled moving area, and not transmitted in the current frame, it is replaced by C. + +##### 1.4.1.4.2 Field/field subsampling + +Either field can be omitted. In the omitted field, interpolation takes place only in those parts of the picture which are estimated to be moving. “Stationary” areas remain unchanged. + +The estimated moving areas are formed from an OR function on the moving areas in the past and future fields, as shown in Figure 2. In the figure, x is a moving element if a OR b OR c OR d are moving. + +For the purpose of field interpolation, PCM lines are considered as non-moving and field blanking is assumed to be at a level of 128 out of 256. + +TABLE 2/H.120 + +###### **Quantization law and variable-length code table** + +| Quantization | | Variable-length codes | | | | +|--------------|---------------|-----------------------|----------|---------------------|----------| +| Input range | Output levels | Normal elements | Code No. | Extra elements | Code No. | +| -255 to -41 | -50 | 1 0 0 0 0 0 0 1 | 15 | 1 0 0 0 0 0 0 0 0 1 | 17 | +| -40 to -24 | -31 | 1 0 0 0 0 1 | 13 | 1 0 0 0 0 0 0 1 | 16 | +| -23 to -11 | -16 | 1 0 1 | 10 | 1 0 0 0 0 0 1 | 14 | +| -10 to -1 | -5 | 1 1 | 9 | 1 0 0 0 1 | 12 | +| 0 to +9 | +4 | 0 1 | 1 | 0 0 0 1 | 3 | +| 0 to 22 | +15 | 0 0 1 | 2 | 0 0 0 0 0 1 | 5 | +| 23 to 39 | +30 | 0 0 0 0 1 | 4 | 0 0 0 0 0 0 0 1 | 7 | +| 40 to 255 | +49 | 0 0 0 0 0 0 1 | 6 | 0 0 0 0 0 0 0 0 0 1 | 8 | + +![Diagram illustrating the interpolation process for luminance signals. It shows three fields: Field B1 (transmitted), Field B2 (omitted), and Field A1 (transmitted). Field B1 contains two samples, 'a' and 'b'. Field B2 contains one sample, 'x'. Field A1 contains two samples, 'c' and 'd'. The diagram shows the interpolation of 'x' from 'a', 'b', 'c', and 'd'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram shows three horizontal lines representing video fields. The left field is labeled 'Field B1 (transmitted)' and contains two samples, 'a' and 'b', marked with dots. The middle field is labeled 'Field B2 (omitted)' and contains one sample, 'x', marked with a dot. The right field is labeled 'Field A1 (transmitted)' and contains two samples, 'c' and 'd', marked with dots. The samples are aligned vertically across the fields, indicating they are from the same spatial location at different times. + +Diagram illustrating the interpolation process for luminance signals. It shows three fields: Field B1 (transmitted), Field B2 (omitted), and Field A1 (transmitted). Field B1 contains two samples, 'a' and 'b'. Field B2 contains one sample, 'x'. Field A1 contains two samples, 'c' and 'd'. The diagram shows the interpolation of 'x' from 'a', 'b', 'c', and 'd'. + +T1513830-93/d02 + +FIGURE 2/H.120 + +In the interpolator for monochrome or luminance signals, the operations $\frac{a + b}{2}$ and $\frac{c + d}{2}$ are carried out before the combined average is taken. Thus + +$$x = \frac{\left[ \frac{a + b}{2} \right] + \left[ \frac{c + d}{2} \right]}{2}$$ + +The interpolated values are placed in the frame store. + +### 1.4.2 Colour-difference components + +#### 1.4.2.1 Analogue-to-digital conversion + +The signal is sampled to produce 52 samples per active line (64 samples per complete line). The sampling pattern is orthogonal and line-, field- and picture-repetitive. For the 625-line input, the sampling frequency is 1.0 MHz, locked to the video waveform. + +The $(E'_R - E'_Y)$ and $(E'_B - E'_Y)$ samples are sited so that the centre of the first colour-difference sample on any line is co-sited with the centre of the third luminance sample (addressed as number 2). The $(E'_R - E'_Y)$ and $(E'_B - E'_Y)$ signals are stored and transmitted on alternate lines of the coded picture. The first active line of Field No. 1 contains $(E'_B - E'_Y)$ and the first active line of Field No. 2 contains $(E'_R - E'_Y)$ . The colour difference signal not being transmitted during any line is obtained at the decoder by interpolation. + +The vertical filtering (see 1.4.2.2) is arranged so that the effective vertical positions of the colour-difference samples in each of the 286 active lines coincide with those of the corresponding luminance samples. + +Uniformly quantized PCM with 8 bits/sample is used. + +The $(E'_R - E'_Y)$ and $(E'_B - E'_Y)$ signals are quantized using $\pm 111$ steps with zero signal corresponding to level 128. The analogue video signals are amplitude-limited so that the digitized signals do not go outside that range (corresponding to levels 16 to 239). The video levels are set so that a 100/0/75/0 colour bar signal (see CCIR Recommendation 471 for explanation of nomenclature) will occupy levels 17 to 239. + +As for the luminance signal, forbidden PCM code words are available for purposes other than transmitting video sample amplitudes. + +#### 1.4.2.2 Pre- and post-filtering + +In addition to conventional anti-aliasing filtering prior to analogue-digital conversion, a digital transversal filtering operation is carried out on the 625-line signal to reduce the vertical definition of the picture prior to conditional-replenishment coding. As a result of this process, 72 active lines of $(E'_R - E'_Y)$ and 71 active lines of $(E'_B - E'_Y)$ are used in Field No. 2 instead of $287\frac{1}{2}$ active lines per field of a 625-line signal. Similarly, Field No. 1 contains 72 active lines of $(E'_B - E'_Y)$ and 71 lines of $(E'_R - E'_Y)$ . An interpolation process in the decoder restores the 625-line signal waveforms. + +#### 1.4.2.3 Conditional replenishment coding + +Coloured moving areas are detected, coded and addressed separately from the luminance moving areas, but the same principles are employed. + +Detected moving areas are transmitted by differential PCM with a maximum of 16 quantization levels. The first picture element in each moving area is transmitted by PCM. Variable-length coding is used on the DPCM code words. + +Complete PCM lines are transmitted to provide systematic and forced updating coincident with luminance PCM lines. + +##### 1.4.2.3.1 DPCM prediction algorithm + +The algorithm used for colour-difference signals is: + +$$x = A$$ + +See Figure 1. + +##### 1.4.2.3.2 Quantization law and variable-length coding + +As for luminance component (see 1.4.1.3.2 and 1.4.1.4.1). + +#### 1.4.2.4 Subsampling + +Horizontal subsampling is carried out in exactly the same way as for the luminance signal, including adaptive element subsampling. + +Field/field subsampling of the colour-difference signals is also similar to that of the luminance signal. Either field can be omitted and, in the omitted field, interpolation takes place only in those parts of the picture which are estimated to be moving. Stationary areas remain unchanged. + +The estimated moving areas are formed by an OR function on moving areas in past and future fields in the same manner as for luminance (see 1.4.1.4.2). + +For colour-difference signals, the interpolated value of $x$ is $\left(\frac{a + c}{2}\right)$ or $\left(\frac{b + d}{2}\right)$ when $x$ is in Field 1 or Field 2, respectively. + +Both field and horizontal subsampling take place simultaneously with subsampling of the luminance signal and they are signalled to the decoder in the same way. + +## 1.5 Video multiplex coding + +### 1.5.1 Buffer store + +The size of the buffer store is defined at the transmitting end only and is 96 kbit/s. Its delay is approximately equal to the duration of one picture (40 ms). + +At the receiving end, the buffer must be of at least this length, but in some implementations of the decoder it may be longer. + +### 1.5.2 Video synchronization + +The method used for video synchronization permits the retention of the picture structure. The required information is transmitted in the form of line start and field start codes (LST and FST). + +#### 1.5.2.1 Line start code + +The line start code includes a synchronization word, a line number code and a digit to signal the presence of element subsampling. + +It has the format: + +0 0 0 0 0 0 0 0 | 0 0 0 0 1 0 0 0 | "S" | 3-bit line No. code | + +"S" is a 1 if horizontal subsampling occurs on the TV line following the line start code. "S" is a "don't care" condition on empty or PCM lines. + +The line number code comprises the least three significant digits of the line number, where Line 0 = first active line of Field 1 and Line 144 = first active line of Field 2. + +Lines numbered 143 and 287 are non-coded lines, used for field synchronization and line number continuity. + +#### 1.5.2.2 Field start code + +There are two field start codes, FST-1 and FST-2, where the first line of the field following FST-2 is interlaced between the first two lines of the field following FST-1. FST-1 indicates the start of the first field, starting with line number 0. FST-2 indicates the start of the second field, starting with line number 144, as shown in Figure 3. + +Each field start code comprises a line start code, followed by an 8-bit word, followed by the line start code of the first line of the next field. + +The field start code is given in Figure 4. + +For FST-1, F = 1 and for FST-2, F = 0. A = 0 for normal operation. If required, A = 1 is used to signal that the buffer state is less than 6 kbits (used in switched multipoint applications). S is the subsampling digit as defined in 1.5.2.1. + +Field subsampling is signalled by two consecutive field start codes of the same number. For example: + +| | | | | +|-------|---------------|-------|---------------| +| FST-1 | field of data | FST-1 | field of data | +|-------|---------------|-------|---------------| + +signifies that field 2 has been omitted and that its moving areas must be interpolated as described in 1.4.1.4.2 and 1.4.2.4. + +![Diagram showing Field 1 and Field 2 line numbers. Field 1 starts at 0, then 1, then 2, then 141, then 142. Field 2 starts at 144, then 145, then 146, then 284, then 285, then 286. A label T1513840-93/d03 is at the bottom right.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Line No. Line No. + +Field 1 0 \_\_\_\_\_ 144 \_\_\_\_\_ Field 2 + +1 \_\_\_\_\_ 145 \_\_\_\_\_ + +2 \_\_\_\_\_ 146 \_\_\_\_\_ + +\_\_\_\_\_ 284 \_\_\_\_\_ + +141 \_\_\_\_\_ 285 \_\_\_\_\_ + +142 \_\_\_\_\_ 286 \_\_\_\_\_ + +T1513840-93/d03 + +Diagram showing Field 1 and Field 2 line numbers. Field 1 starts at 0, then 1, then 2, then 141, then 142. Field 2 starts at 144, then 145, then 146, then 284, then 285, then 286. A label T1513840-93/d03 is at the bottom right. + +FIGURE 3/H.120 + +| LST | | | | | LST | | | | +|----------|----------|---|-----|----------|----------|----------|---|-----| +| 00000000 | 00001AAA | F | 111 | 0000F11F | 00000000 | 00001000 | S | 000 | + +FIGURE 4/H.120 + +### 1.5.3 Addressing of moving areas + +The positions of the clusters of picture elements along each line which are deemed to form parts of moving areas are addressed by means of an address of the start of the cluster and an “end-of-cluster” code (EOC). + +The form of coding is: + +| LST | PCM value | 8-bit address of the PCM picture element | Variable-length DPCM coded moving area | EOC | PCM value | 8-bit address | etc. | +|-----|-----------|------------------------------------------|----------------------------------------|-----|-----------|---------------|------| +|-----|-----------|------------------------------------------|----------------------------------------|-----|-----------|---------------|------| + +The PCM value is the amplitude of the first picture element of the cluster. When there is no colour-difference data, the EOC is omitted in the last luminance cluster of every line, i.e. both the LST and FST codes also signify end of cluster. + +The EOC is 1001. + +The address indicates the sample number along the line belonging to the first picture element of the cluster. + +A cluster cannot start at the last element of the line, i.e. (11111111) is a forbidden cluster address, nor can it extend into line blanking even during subsampling. + +The minimum gap between the end of one cluster and the start of the next is four picture elements, and the minimum length of a cluster is one picture element. + +### 1.5.4 Addressing of colour-difference data + +To permit the insertion of colour-difference data in a line containing moving picture elements, a colour escape code is inserted after the final luminance cluster in the line. This permits addresses to be re-used for colour clusters. + +The escape code is 00001001 (an invalid PCM value) and follows the end of cluster code of the last luminance cluster (if any), otherwise it follows the line start code. This is followed by the addresses, variable-length codes and EOC codes of the subsequent coloured clusters, the sequence being terminated by the line start code of the next line. + +The form of addressing of colour-difference moving areas is shown in Figure 5. + +![Diagram showing the sequence of codes for colour-difference data. The top row shows: ... | VLC luminance picture element | EOC | 00001001 | PCM value of first colour-difference picture element | Address of first colour-difference cluster | VLC codes | ... The bottom row shows: ... | EOC | PCM | Address | ..... | Line start code | .....](b90144cfbb81a2d610d920240fda689d_img.jpg) + +Diagram showing the sequence of codes for colour-difference data. The top row shows: ... | VLC luminance picture element | EOC | 00001001 | PCM value of first colour-difference picture element | Address of first colour-difference cluster | VLC codes | ... The bottom row shows: ... | EOC | PCM | Address | ..... | Line start code | ..... + +FIGURE 5/H.120 + +There are 52 colour-difference picture elements per line, the first of which is given an address with numerical value 4. The address range is therefore: + +00000100 to 00110111. + +A cluster cannot start at address (00110111) nor can it extend beyond this point, even during subsampling. The minimum gap between the end of one colour-difference cluster and the start of the next is 4 picture elements. The minimum cluster length is one picture element. Cluster bridging is not allowed between luminance and colour-difference clusters. + +A monochrome decoder will discard the information between the colour escape code and the next line start code. + +### 1.5.5 PCM lines + +PCM lines are used for systematic or forced updating and are signalled as shown in Figure 6. + +| | Invalid PCM code | Invalid cluster address | PCM value of first picture element of line | 254 × 8 bit PCM values | | +|-----|------------------|-------------------------|--------------------------------------------|------------------------|-----------------| +| LST | 1 1 1 1 1 1 1 1 | 1 1 1 1 1 1 1 1 | X X X X X X X X | X X . . . | 1 0 0 0 0 0 0 0 | + +FIGURE 6/H.120 + +With monochrome, all 256 elements in the line are transmitted using 8-bit PCM. + +With PCM lines, the subsampling digit "S" is ignored at the receiver. PCM lines cannot be horizontally subsampled. + +For the purpose of field interpolation, PCM lines are considered to be non-moving. + +With colour signals, the colour-difference data will comprise $52 \times 8$ -bit PCM values following the $256 \times 8$ -bit luminance elements. The colour escape code is not transmitted. A monochrome decoder will discard the colour-difference picture elements. + +## **1.6 Transmission coding** + +The transmission coder assembles the video, audio, signalling and optional data channels into a 2048-kbit/s frame structure which is in accordance with Recommendation G.704. It also provides justification facilities to enable the video sampling frequency to be independent of the network clock. + +### **1.6.1 Serial data** + +With all serialized data (video, audio and addressing), the most significant digit is in the leading position. Positive logic is used throughout. + +### **1.6.2 Audio** + +The audio is coded into 64 kbit/s using A-law PCM, as specified in Recommendation G.711. + +In the coder, the delay difference between the coded audio and video when the buffer is empty should be within $\pm 5$ ms. In the decoder, the delays must also be equalized, and the tolerance is under study. + +The audio output should be muted in the event of loss of frame alignment. + +### **1.6.3 Transmission framing** + +#### **1.6.3.1 General** + +The frame structure is defined in Recommendation H.130 which specifies how the frame is structured and for what purposes the time slots are used. This information need not be repeated here. + +Time slot 2 (odd) is allocated to codec-to-codec signalling and the functions of the various bits are specified in Recommendation H.130. In most cases, the action to be taken by the encoder and/or decoder according to whether each of these bits is 0 or 1 is evident from the specified purpose of the bit. In the few cases where this is not so, additional information is given below. + +#### **1.6.3.2 Use of certain bits in each octet in the odd frames of time slot 2** + +Studies to determine the most suitable methods for multipoint conferencing are still in progress, but from the preliminary results, a number of special features and facilities have been identified as being necessary and have therefore been included in the codec and frame structure. In "continuous presence" multipoint conferencing, a transmission channel may, at times, be shared by two codecs in different locations. This requires a reduction of the bit rate of each source so that the total bit rate is within the capacity of the channel. The "facilities bits", i.e. bits (see Recommendation H.130) 3.1.2 and 3.1.7, are used to signal the availability of this facility and the bits 4.9 and 4.15, signal the mode of operation and the active time slots in use at the output of the transmission coder. The details of how the foregoing bits are interpreted are given in Recommendation H.130. + +Bits 3.7 to 3.15 also provide facilities whose principal usefulness is likely to be multipoint conferencing. Information on the use of these bits together with details of the use of bits 1 and 2, which are essential to the basic requirements of keeping the encoder and decoder in step, are given below: + +##### **Bit 1 – For clock justification** + +The frequency control arrangements are as follows: + +The video sampling clock is locked to the line-scanning frequency of the incoming video signal, which has a permitted tolerance of $\pm 2$ parts in $10^4$ . + +The justification is controlled by a comparison frequency of (22 500/11) kHz, which is locked to the video clock. + +The clock for the digital channel has a frequency of $2048 \text{ kHz} \pm 50 \text{ parts in } 10^6$ . + +The phase of the channel clock is compared with that of the comparison frequency and when the channel-clock phase exceeds that of the comparison frequency by $2\pi$ radians, a 1 is transmitted. If the phase difference is less than $2\pi$ radians, a 0 is transmitted. + +##### **Bit 2 – To signal buffer state** + +The degree to which the encoder buffer is filled, measured in increments of 1 K ( $1 \text{ K} = 1024 \text{ bits}$ ), is signalled using an 8-bit binary code. The most significant bit (MSB) is in frame 1 of the multiframe, the second MSB in frame 2, etc. The buffer state is sampled at the start of the multiframe in which its state is transmitted. + +##### **Bit 3.7 – Fast update request** + +On receipt of this bit set to 1, the transmitter buffer is forced to decrease its fill and stabilize to a state of less than 6 K by preventing coded picture elements from entering the buffer. Bit A is set to 1 in the next FST. The two following fields are treated as complete moving areas and the encoder uses an arrangement for control of the subsampling modes to make the buffer overflow condition unlikely. + +##### **Bit 3.9 – Advance warning of interruption** + +This bit (set to 1) is used to warn a decoder that its received signal may be interrupted after the start of the next supermultiframe for a period of not more than two seconds. On receipt of bit 3.9 set to 1, a decoder will display a still picture for a period of not more than 2 s, or until an FST code is received with bit A set to 1. + +##### **Bit 3.11 – Sound power signal** + +This bit is used to signal the sound power in the audio channel. The power is integrated over a period of 16 ms (period of the supermultiframe), uniformly quantized to 8 bits and transmitted at supermultiframe rate. It is used during encrypted multipoint operations. In other cases, bit 3.11 is set to zero. + +##### **Bit 3.13 – Data distribution** + +This bit is set permanently to 0 in all encoders. When a 1 is received from the network (introduced, for example, by a multipoint control unit), the encoder will vacate the same time slots in its outgoing signal as signalled on the incoming stream by the settings of the relevant bits 4 (which identify the use of the time slots, see Recommendation H.130). It will confirm the action by transmitting the same bit 4 settings as received. This function should be carried out within 10 supermultiframe periods. + +##### **Bit 3.15 – Detection of looped ports** + +This bit is set to 1 in all codecs. It may be used by a multipoint control unit to detect whether one of its bidirectional 2 Mbit/s ports has been externally looped. + +## **1.7 Error correction** + +Provision is made for the optional use of forward error correction. This is required if the channel error rate is worse than 1 in $10^6$ for significant periods of time. The error corrector used is a (4095, 4035) five-error correcting BCH code (*Bose, Chaudhuri and Hocquengham*). The error-correcting decoder has the ability to correct up to 5 isolated errors and one burst of up to 16 errors in each block. At a channel error probability of $1 \times 10^{-4}$ , the corrected error rate is $1.25 \times 10^{-8}$ . The 60 parity bits which are required are obtained by removing the video from time slots 24 to 31 of frame number 15 of each multiframe. + +NOTE – The question of whether error correction should be provided on the signal, on the link, or both, should be studied. Also under study is the question of whether the audio should be corrected by the same error corrector or whether a separate error-correcting codec should be used. + +# **2 Codecs not requiring separate television standards conversion when used on interregional connections** + +## **A codec for 525-line, 60 fields/s and 1544 kbit/s transmission for intra-regional use and capable of interworking with the codec of clause 1** + +## **2.1 Introduction** + +Clause 2 indicates the changes and additions which must be made to the text of 1 in order to define the version of the codec for use with 525-line, 60 fields/s television standards and transmission at 1544 kbit/s. The two versions are capable of interworking via a re-multiplexing unit which can convert the 2.1/G.704 compatible frame structure on one side to the 2.3/G.704 compatible frame structure (with 6 time slots empty) on the other side. + +The two versions of the codec are identical in most respects, the important differences (apart from the obvious ones arising from different input and output signals) being confined to the digital pre- and post-filters and the signals for the control of the buffers. Moreover, the detailed algorithms of the pre- and post-filters do not need to be specified to permit interworking. Only an outline of their mode of operation together with the few necessary specifications are therefore provided. + +## **2.2 Brief specification** + +### **2.2.1 Video input/output** + +The video input and output are standard 525-line, 60 fields/s colour or monochrome television signals. The colour signals are in component form. Colour and monochrome operation are fully compatible. + +### **2.2.2 Digital output/input** + +The digital output and input are at 1544 kbit/s, compatible with the frame structure of Recommendation G.704. + +### **2.2.3 Sampling frequency** + +The video sampling frequency and 1544 kbit/s network clock are asynchronous. + +### **2.2.4 Coding techniques** + +Conditional replenishment coding supplemented by adaptive digital filtering, differential PCM and variable-length coding are used to achieve low bit-rate transmission. + +### **2.2.5 Audio channel** + +An audio channel using 64 kbit/s is included. At present, coding is A-law according to Recommendation G.711, but provision is made for future use of more efficient coding. + +### **2.2.6 Mode of operation** + +The normal mode of operation is full duplex. + +### **2.2.7 Codec-to-network signalling** + +An optional channel for codec-to-network signalling is included. + +### **2.2.8 Data channels** + +Optional $2 \times 64$ kbit/s and $1 \times 32$ kbit/s data channels are available. These are used for video if not required for data. + +### **2.2.9 Forward error correction** + +Optional forward error correction is available. This is required only if the long-term error rate of the channel is worse than $1$ in $10^6$ . + +### **2.2.10 Additional facilities** + +Provision is made in the digital frame structure for the future introduction of encryption, a graphic mode and multipoint facilities. + +**2.2.11** When the coder buffer is empty and the decoder buffer full, the coder delay is $31 \pm 5$ ms and the decoder delay is $176 \pm 31$ ms3). + +## **2.3 Video interface** + +The normal video input is a 525-line, 60 fields/s signal in accordance with CCIR Report 624. When colour is being transmitted, the input (and output) video signals are in component form. The luminance and colour-difference components, $E'_Y$ , $(E'_R - E'_Y)$ and $(E'_B - E'_Y)$ are as defined in CCIR Report 624. The video interface is as recommended in CCIR Recommendation 567. + +## **2.4 Source coder** + +### **2.4.1 Luminance component or monochrome** + +#### **2.4.1.1 Analogue-to-digital conversion** + +The signal is sampled to produce 256 picture samples per active line (320 samples per complete line). The sampling pattern is orthogonal and line, field and picture repetitive. For the 525-line input, the sampling frequency is 5.0 MHz, locked to the video waveform. + +Uniformly quantized PCM with 8 bits/sample is used. + +Black level corresponds to level 16 (00010000). + +White level corresponds to level 239 (11101111). + +PCM code words outside this range are forbidden (the codes being used for other purposes). For the purposes of prediction and interpolation, the final picture element in each active line (i.e. picture element 255) is set to level 128 in both encoder and decoder. + +In all arithmetic operations, 8-bit arithmetic is used and the bits below the binary point are truncated at each stage of division. + +#### **2.4.1.2 Pre- and post-filtering** + +##### **2.4.1.2.1 Spatial filtering** + +A digital filter reduces the $242\frac{1}{2}$ active lines-per-field of the 525-line signal to 143 lines-per-field, the same number as in the 625-line version of the codec. In the decoder, the digital post-filter uses interpolation to restore the signal to 525-lines per picture. + +##### **2.4.1.2.2 Temporal filtering** + +A recursive temporal pre-filter with non-linear transfer characteristics is used in the coder to reduce noise in the signal and increase coding efficiency. The frame store used in this filter can also be used as the storage element of a frame interpolator with variable coefficients which is used to reduce the transmitted frame rate to a value less than that of the input video signal. In 525-line to 525-line transmission, the transmitted frame frequency is locked to the video clock and is approximately 29.67 Hz (29.97 Hz times $3057/3088$ ) instead of the nominal video rate of 29.97 Hz. In 525-line to 625-line transmission, the transmitted frame frequency is nominally 25 Hz and is locked to the channel clock. + +Because the (television) frames are leaving the coder more slowly than they are entering, the coding process is suspended for one frame every $N$ th input frame. $N$ is approximately 100 for 525-line to 525-line operation and approximately 6 for 525-line to 625-line operation. + +In the decoder, the digital post-filter incorporates a frame store in some versions of the 625-line codec where it is used in the line interpolation process. In the 525-line version, in addition to its use for line interpolation, it is used as a temporal interpolator with variable coefficients to provide an extra output frame during those periods when the decoding is temporarily suspended. + +--- + +3) These are typical figures. The delays depend upon the detailed implementation used. + +## 2.5 Video multiplex coding + +### 2.5.1 Buffer store + +The size of the buffer store is defined at the transmitting end only and is 160 kbits. Of this, 96 kbits is used for smoothing the video data in the face-to-face mode and the remainder is used to accommodate the action of the frame interpolator (see 2.5.1.1) and the requirements of the graphics mode. + +At the receiving end, the buffer must be at least this length but in some implementations of the decoder, it may be longer. + +#### 2.5.1.1 Buffer control + +The amount to which the transmitting buffer is filled is used to control various coding algorithms (subsampling, etc.) and is signalled to the decoder to enable it correctly to interpret the received signals. In the 525-line codec, the transmission rate is less than the video input rate and hence the buffer tends to fill more rapidly than would be determined by the movement in the picture, only to empty again when the interpolator suspends the coding process. + +To avoid incorrect changes in coding algorithms, the buffer-state signal is modified to take account of the progressively changing coefficients of the interpolator in the pre-filter. The buffer then operates as though the data is coming from a video source whose frame rate is uniform and the same as the transmitted frame rate. + +## 2.6 Transmission coding + +The transmission coder assembles the video, audio, signalling and optional data channels into a 1544 kbit/s frame structure which is compatible with Recommendation G.704. + +### 2.6.1 Serial data + +See 1.6.1. + +### 2.6.2 Audio + +See 1.6.2. + +### 2.6.3 Transmission framing + +The frame structure, compatible with Recommendation G.704 and also compatible with that of the 625-line version in clause 1, is given in 2/H.130. + +#### 2.6.3.1 General + +See 1.6.3.1. + +#### 2.6.3.2 Use of certain bits in each octet in the odd frames of time slot 2 + +The use of certain of the bits in time slot 2 (odd) differs slightly from that given for the codec in clause 1. The differences are as follows: + +##### Bit 1 – For clock justification + +This bit is disregarded in 525-line decoders. + +To permit interworking with the 625-line codecs of clause 1, the 525-line coders must transmit a fixed bit-pattern which is used to control the frequency of the video clock in 625-line decoders. The exact form of the repetitive pattern need not be specified but it must contain seven “ones” and four “zeros” in 11 bits, e.g.: + +1 0 1 1 0 1 0 1 1 0 1 + +##### Bit 2 – To signal buffer state + +The degree to which the encoder buffer is filled, after correction for the interpolator (see 2.5.1.1), is measured in increments of 1 K (1 K = 1024 bits), and signalled using an 8-bit binary code. When working to a 525-line decoder, the buffer state is sampled every 3057 channel-clock periods. When working to a 625-line decoder, the buffer state is sampled 10 times during every 525-line field period. When the buffer input is suspended for a frame period, the buffer + +sampling is stopped. The sampled values of the buffer state are stored prior to transmission. The store may hold between zero and 23 values which have been modified to take account of the interpolator coefficients at the times of sampling. The modified sample values are read out [as bit 2 of TS2 (odd)] at a uniform rate; the most significant bit (MSB) in frame 1 of the multiframe, the second MSB in frame 2, etc. + +##### **Bit 3.7 – Fast update request** + +On receipt of this bit set to 1, the transmitter buffer is forced to decrease its full and stabilise to a modified state of less than 6 K by preventing coded picture elements from entering the buffer. Bit A is set to 1 in the next FST. The two following fields are treated as complete moving areas and the encoder uses an arrangement for control of the sub-sampling modes to make the buffer overflow condition unlikely. + +# **3 A codec for 525-lines, 60 fields/s and 1544 kbit/s transmission for intra-regional use** + +## **3.1 Introduction** + +A 1.5 Mbit/s interframe codec described under 3, is capable of transmitting and receiving a single NTSC video signal and audio signal using an adaptive predictive coding technique with motion-compensated prediction, background prediction and intraframe prediction. + +The aim of this codec is to effectively transmit video telephone and video conferencing signals which have relatively small movements. The video interface of the codec is a 525-line, 60 fields/s standard analogue television signal corresponding to the “Class *a*” standard of Recommendation H.100. + +## **3.2 Outline of codec** + +The essential parts of the codec block diagram are shown in Figure 7. The coder consists of three basic functional blocks, that is, pre-processing, video source coding and transmission coding. + +In the pre-processor, the input analogue NTSC video signal is digitized and colour decoded into one luminance component and two chrominance components. These three components are time division multiplexed into a digital video form, whose noise and unnecessary signal components are removed by the pre-filter. + +In the video source coder, the digital video signal is fed to the predictive coder where interframe and intraframe predictive coding techniques are fully utilized for minimizing prediction errors to be transmitted. The prediction error signal is next entropy-coded using its statistical properties to reduce redundancies. Since the coded error information is generated in irregularly spaced bursts, a buffer is used. If the buffer becomes full, the number of prediction error quantizing levels and/or picture elements to be coded is reduced to prevent any overflow. + +In the transmission coder, coded video and audio signals are first encrypted on an optional basis. The coded video signal is then forward error correction coded and scrambled. The three signals, coded video, coded audio and optional data signals are multiplexed into a 1544 kbit/s digital format with a frame structure as defined in Recommendation H.130. + +The decoder carries out a reverse operation. + +## **3.3 Brief specification** + +### **3.3.1 Video input/output** + +NTSC signals are used for the video input/output signal, with monochrome signals being additionally applicable. + +### **3.3.2 Digital output/input** + +The interface conditions for the digital output/input signal satisfy Recommendation G.703 specifications. The signal transmission rate is 1544 kbit/s. + +#### a) Coder + +![Block diagram of the Coder part of the H.120 codec. It shows three input streams: Video input, Audio input, and Data input. The Video input is processed through Pre-processing (A/D, Colour decoding and TDM, Prefilter), Video source coding (Predictive coding, Entropy coding, Transmission buffer), and Transmission coding (Encrypt, Error correct, Scramble) before entering the MUX and framing block. The Audio input is processed through an Audio coder and Delay, then encrypted and sent to the MUX. The Data input is sent directly to the MUX. The MUX and framing block also receives input from a Stuffing block and produces a Digital output. A line for 'Codec-to-codec information' is shown between the Video source coding and Transmission coding stages.](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +Block diagram of the Coder part of the H.120 codec. It shows three input streams: Video input, Audio input, and Data input. The Video input is processed through Pre-processing (A/D, Colour decoding and TDM, Prefilter), Video source coding (Predictive coding, Entropy coding, Transmission buffer), and Transmission coding (Encrypt, Error correct, Scramble) before entering the MUX and framing block. The Audio input is processed through an Audio coder and Delay, then encrypted and sent to the MUX. The Data input is sent directly to the MUX. The MUX and framing block also receives input from a Stuffing block and produces a Digital output. A line for 'Codec-to-codec information' is shown between the Video source coding and Transmission coding stages. + +#### b) Decoder + +![Block diagram of the Decoder part of the H.120 codec. It shows three output streams: Video output, Audio output, and Data output. The Digital input is processed through Framing and DMUX, which also interacts with a Destuffing block. The output of the Framing and DMUX is sent through Transmission decoding (Descramble, Error correct, Decrypt), then to Video source decoding (Receiving buffer, Entropy decoding, Predictive decoding), and finally to Post-processing (Postfilter, TDDM and colour encoding, D/A) to produce the Video output. The output of the Framing and DMUX is also sent through Decrypt and then through an Audio decoder and Delay to produce the Audio output. The output of the Framing and DMUX is also sent directly to produce the Data output. A line for 'Codec-to-codec information' is shown between the Transmission decoding and Video source decoding stages.](844077b3034f0030b404207db0ad76b4_img.jpg) + +Block diagram of the Decoder part of the H.120 codec. It shows three output streams: Video output, Audio output, and Data output. The Digital input is processed through Framing and DMUX, which also interacts with a Destuffing block. The output of the Framing and DMUX is sent through Transmission decoding (Descramble, Error correct, Decrypt), then to Video source decoding (Receiving buffer, Entropy decoding, Predictive decoding), and finally to Post-processing (Postfilter, TDDM and colour encoding, D/A) to produce the Video output. The output of the Framing and DMUX is also sent through Decrypt and then through an Audio decoder and Delay to produce the Audio output. The output of the Framing and DMUX is also sent directly to produce the Data output. A line for 'Codec-to-codec information' is shown between the Transmission decoding and Video source decoding stages. + +TDM Time division multiplexing + TDDM Time division demultiplexing + MUX Multiplexing + DMUX Demultiplexing + +T1513850-93/d04 + +FIGURE 7/H.120 + Codec blockdiagram + +### **3.3.3 Sampling frequency** + +The video sampling frequency is four times the colour sub-carrier frequency ( $f_{SC}$ ) and asynchronous with the 1544 kHz network clock. + +### **3.3.4 Time division multiplexed (TDM) digital video format** + +An NTSC signal is separated into a luminance component (Y) and two chrominance components ( $C_1$ and $C_2$ ). A time division multiplexed signal composed of Y and time-compressed $C_1$ and $C_2$ is employed in the source coding as the standard digital video format. + +### **3.3.5 Coding algorithm** + +Adaptive predictive coding supplemented by variable word-length coding is used to achieve low bit rate transmission. The following three predictions are carried out adaptively on a pel-by-pel basis: + +- a) motion-compensated interframe prediction for a still or slowly moving area; +- b) background prediction for an uncovered background area; and +- c) intraframe prediction for a rapidly moving area. + +Prediction errors for video signals and motion vectors are both entropy-coded using the following two techniques: + +- i) variable word-length coding for non-zero errors; and +- ii) run-length coding for zero errors. + +### **3.3.6 Audio channel** + +An audio channel using 64 kbit/s is included. The audio coding algorithm complies with Recommendation G.722. + +### **3.3.7 Data channel** + +An optional 64 kbit/s data channel is available, which is used for video if not required for data. + +### **3.3.8 Mode of operation** + +The normal mode of operation is full duplex, with other modes, e.g. the one-way broadcasting operation mode, also taken into account. + +### **3.3.9 Transmission error protection** + +A BCH error correcting code is used along with a demand refreshing method to prevent uncorrected errors from degrading the picture quality. + +### **3.3.10 Additional facilities** + +Provision is made in the digital frame structure for the future introduction of such facilities as encryption, graphics transmission and multipoint communication. + +### **3.3.11 Processing delay** + +The coder plus decoder delay is about 165 ms without that of a pre-filter and a post-filter. + +## **3.4 Video interface** + +The video input/output signal of the codec is an analogue NTSC signal (System M) in accordance with CCIR Report 624. + +## 3.5 Pre- and post-processing + +### 3.5.1 Analogue-to-digital and digital-to-analogue conversion + +An NTSC signal band-limited to 4.5 MHz is sampled at a rate of 14.3 MHz, four times the colour sub-carrier frequency ( $f_{SC}$ ), and converted to an 8-bit linear PCM signal. The sampling clock is locked to the horizontal synchronization of the NTSC signal. Since the sampling frequency is asynchronous with the network clock, the justification information is coded and transmitted from the coder to the decoder. + +The digital video data is expressed in two's complement form. The input level to the A/D converter is defined as follows: + +- sinc tip level (-40 IRE) corresponds to -124 (10000100); +- white level (100 IRE) corresponds to 72 (01001000). + +(IRE: Institute of Radio Engineers) + +As a national option, a pad can be inserted before the A/D converter if a level fluctuation should be taken into account at analogue transmission lines connecting terminal equipment and codec. + +At the decoder, the NTSC signal is reproduced by converting the 8-bit PCM signal to an analogue signal. + +### 3.5.2 Colour decoding and encoding + +The digitized NTSC signal is separated into the luminance component (Y) and the carrier band chrominance component (C) by digital filtering. The two baseband chrominance signals ( $C_1$ and $C_2$ ) are obtained by digitally demodulating the separated carrier band chrominance component. The effective sampling frequency after colour decoding is converted to 7.2 MHz ( $2 f_{SC}$ ) and 1.2 MHz ( $1/3 f_{SC}$ ) for the luminance signal and chrominance signals, respectively. + +The replica of the NTSC signal is obtained by digitally modulating the $C_1$ and $C_2$ signals and adding to the Y signal at the decoder. + +Filter characteristics for colour decoding and encoding are left to each hardware implementation since they do not affect interworking between different design codecs. Examples of recommended characteristics are described in Annex E. + +### 3.5.3 TDM signal + +A time division multiplexing (TDM) signal is constructed from the separated component signals. + +First, the $C_1$ and $C_2$ signals are time-compressed to 1/6. Next, each of the time compressed $C_1$ and $C_2$ signals, with their horizontal blanking parts removed, is inserted into the Y signal horizontal blanking interval on alternate lines. $C_1$ is inserted on the first line of the first field and on every other line following throughout the frame, while $C_2$ is inserted on the second line of the first field and on every other line following throughout the frame. + +Active samples for the Y signal are 384 samples/line and 64 samples/line for the $C_1$ and $C_2$ signals. The TDM signal is constructed with these active samples and 7 colour burst samples (B), which are inserted into the top of the TDM signal. + +As shown in Figure 8, the $C_1$ and $C_2$ signal sampling points coincide with that of the Y signal on every sixth sample. The $C_1$ and $C_2$ signals of only the odd lines are transmitted to the decoder. + +At the decoder, each component signal is again demultiplexed from the TDM signal, and time-expansion processing of 6 times is carried out for the $C_1$ and $C_2$ signals. + +NOTE – When a pad is inserted before the A/D converter as described in 3.5.1, pre-emphasis (de-emphasis) with a compensating gain for the $C_1$ , $C_2$ and colour burst signals is recommended at the source coder input (decoder output) to obtain better picture reproduction in coloured parts. + +![Diagram showing the conversion of an NTSC signal into a TDM signal format. The top part illustrates an NTSC signal line (63.6 μs) with pel numbers from 1 to 910. It highlights the horizontal sync, color burst samples (93, 94), and active samples for Y and C signals. The bottom part shows the TDM signal format for odd and even lines, divided into B (7 samples), C (64 samples), and Y (384 samples) segments, totaling 455 samples per TDM line.](97f61e67792478fb6ce089868e503063_img.jpg) + +NTSC signal (1 line: 63.6 μs) + +(68) (8) (36) (8) +(Number of samples) + +Colour Burst samples +93 94 + +$[(887 - 121)/2] + 1 = 384$ samples +Active samples for Y signal + +$[(882 - 126)/12] + 1 = 64$ samples +Active samples for $C_1$ or $C_2$ signal + +Pel number (4 $f_{sc}$ sampling) + +1 69 77 113 121 125 882 887 1 910 + +Reference timing point (Half-amplitude point of horizontal sync falling edge. +Synchronous with rising edges of frame pulse, line pulse and sampling pulse.) + +TDM signal format + +Odd line $(2n - 1)$ : $C^1_{93}$ $C^1_{125}$ $C^1_{137}$ (Note 2) $C^1_{881}$ $Y^1_{121}$ $Y^1_{123}$ $Y^1_{125}$ (Note 3) $Y^1_{885}$ $Y^1_{887}$ + +(Note 1) + +Even line $(2n)$ : $C^2_{94}$ $C^2_{126}$ $C^2_{138}$ (Note 2) $C^2_{882}$ $Y^2_{121}$ $Y^2_{123}$ $Y^2_{125}$ (Note 4) $Y^2_{885}$ $Y^2_{887}$ + +TDM signal (Number of samples) + +B (7) C (64) Y (384) + +Number of TDM signal + +1 8 9 71 72 73 74 454 455 + +T15 13860-93/d05 + +Diagram showing the conversion of an NTSC signal into a TDM signal format. The top part illustrates an NTSC signal line (63.6 μs) with pel numbers from 1 to 910. It highlights the horizontal sync, color burst samples (93, 94), and active samples for Y and C signals. The bottom part shows the TDM signal format for odd and even lines, divided into B (7 samples), C (64 samples), and Y (384 samples) segments, totaling 455 samples per TDM line. + +###### NOTES + +- 1 Odd line samples. A colour burst sample is repeated seven times. +- 2 Odd line samples. +- 3 Odd line samples. +- 4 Even line samples. + +FIGURE 8/H.120 +**TDM signal format** + +### 3.5.4 Pre- and post-filtering + +In addition to conventional anti-aliasing filtering prior to analogue-to-digital conversion, the following two filtering processes should be used as pre-filtering for source coding: + +- a) temporal filtering to reduce random noise included in the input video signal; +- b) spatial filtering to reduce aliasing distortion in subsampling. + +At the decoder, the following three filtering processes should be used as post-filtering in addition to conventional low pass filtering after digital-to-analogue conversion: + +- i) spatial filtering to interpolate the omitted picture elements in subsampling; +- ii) spatio-temporal filtering to interpolate the omitted fields in field repetition; +- iii) temporal filtering to reduce noise generated in the course of source coding. + +Although these filtering processes are important for improving reproduced picture quality, their characteristics are independent of interworking between different design codecs. Hence, pre- and post-filtering is left to each hardware implementation. + +## 3.6 Source coding + +### 3.6.1 Configuration of source coder and decoder + +The video source coder and decoder configuration of this codec is outlined in Figure 9. + +The predictive encoder converts the input video signal $x$ into the prediction error signal $e$ , using the motion vector $v$ . This conversion is controlled by the coding mode $m$ . + +The variable word-length (VWL) coder codes $e$ and $v$ into the compressed data $C$ using the variable length coding method. The transmission buffer memory (BM) smoothes out the irregularly spaced data $C$ . The coding mode $m$ is also coded. + +The frame memory parity information $p$ is used to check the identity of coder and decoder frame memory contents. If any parity error is detected, frame memories of both coder and decoder are reset by the demand refresh information (DR) and the demand refresh confirmation information (DDR). + +At the decoder, the variable word-length (VWL) decoder decodes $e$ , $v$ , $m$ and $p$ , and the predictive decoder reproduces the video signal $x'$ . + +### 3.6.2 Predictive coding + +#### 3.6.2.1 Coding modes + +Five coding modes as summarized in Table 3 are provided. All of the samples are coded and transmitted in normal mode, while half of the samples are omitted in subsampling mode. In field repetition mode, one or more consecutive fields are omitted (called multi-field repetition, see Note 1). If field repetition mode and subsampling mode are used in combination, only a quarter or less of the original picture elements are coded and transmitted. + +Subsampling is carried out in a quincunx way, namely by transmitting only odd-numbered pels on odd-numbered lines and even-numbered pels on even-numbered lines in each block-line (see Note 2). + +In field repetition mode, either the odd or even fields are omitted. For the omitted fields, both the prediction error $e$ and the motion vector $v$ are set to 0. + +###### NOTES + +1 If odd fields and even fields are mixed after field omission, a severe picture degradation takes place. Hence, 1 out of 2, 3 out of 4 or 5 out of 6 field omission is recommended. + +2 Each block-line consists of 8 lines as defined in 3.6.2.5. + +![Block diagram of source coder and decoder configuration. The top part shows the encoder: Input video signal x enters a Predictive encoder. A Motion vector detector sends motion vector v to the Predictive encoder. The Predictive encoder outputs prediction error e and parity check information p to a VWL coder. The VWL coder outputs compressed data C to a Buffer memory (BM). The BM outputs Compressed video output. The BM also sends Buffer memory occupancy information b to a Coding parameter control block. The Coding parameter control block sends Coding mode m to the Predictive encoder and the VWL coder. The Coding parameter control block is connected to DDR. The bottom part shows the decoder: Compressed video input enters a Buffer memory (BM). The BM outputs compressed data C to a VWL decoder. The VWL decoder outputs prediction error e and parity check information p to a Predictive decoder. The Predictive decoder outputs Output video signal x'. The Predictive decoder sends motion vector v to the VWL decoder. The Predictive decoder is connected to DR.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +Block diagram of source coder and decoder configuration. The top part shows the encoder: Input video signal x enters a Predictive encoder. A Motion vector detector sends motion vector v to the Predictive encoder. The Predictive encoder outputs prediction error e and parity check information p to a VWL coder. The VWL coder outputs compressed data C to a Buffer memory (BM). The BM outputs Compressed video output. The BM also sends Buffer memory occupancy information b to a Coding parameter control block. The Coding parameter control block sends Coding mode m to the Predictive encoder and the VWL coder. The Coding parameter control block is connected to DDR. The bottom part shows the decoder: Compressed video input enters a Buffer memory (BM). The BM outputs compressed data C to a VWL decoder. The VWL decoder outputs prediction error e and parity check information p to a Predictive decoder. The Predictive decoder outputs Output video signal x'. The Predictive decoder sends motion vector v to the VWL decoder. The Predictive decoder is connected to DR. + +T1513870-93/d06 + +| | | +|------|-----------------------------------------| +| $x$ | Input video signal | +| $x'$ | Output video signal | +| $m$ | Coding mode | +| $e$ | Prediction error | +| $v$ | Motion vector | +| $p$ | Parity check information | +| $C$ | Compressed data | +| $b$ | Buffer memory occupancy information | +| VWL | Variable word length | +| BM | Buffer memory | +| DR | Demand refresh request information | +| DDR | Demand refresh confirmation information | + +FIGURE 9/H.120 +Source coder and decoder configuration + +#### 3.6.2.2 Adaptive prediction + +Prediction functions are adaptively selected on a pel-by-pel basis as shown in Figure 10. The selection is carried out so as to minimize probable prediction errors. This is accomplished using the two prediction status signals, which are determined by prediction reference signals, for the preceding pels located on the previous and the present lines. + +When subsampling and/or field repetition are operated, omitted pels are interpolated in the prediction loop. + +TABLE 3/H.120 + +##### **Coding modes** + +| Coding modes | | Abbreviation | Operation | +|--------------|------------------|--------------|-----------------------------| +| 1 | Normal | NRM | Full sampling | +| 2 | Field repetition | FRP | One or more fields omission | +| 3 | Subsampling | SBS | 2:1 per omission | +| 4 | Stop | STP | Suspension of coding | +| 5 | Refresh | RFS | Renewal of frame memory | + +The notations defined for the i-numbered pel are as follows: + +- $X_i$ local decoder output; +- $Y_i$ interpolator output; +- $M_i$ motion compensated interframe prediction value; +- $B_i$ background prediction value; +- $I_i$ intraframe prediction value; +- \* + logical product; and +- + + logical sum. + +##### **3.6.2.2.1 Motion-compensated interframe prediction/background prediction** + +Prediction status signal $S_{1i}$ for pel $i$ is determined as + +$$S_{1i} = R_1(i - 455) * R_1(i - 456) + R_1(i - 456) * R_1(i - 454) + R_1(i - 454) * R_1(i - 455) \quad (3-1)$$ + +where prediction reference signal $R_1(i)$ is + +$$R_1(i) = \begin{cases} 0 \text{ if } |Y_i - B_i| \geq |Y_i - M_i|, \\ 1 \text{ if otherwise.} \end{cases} \quad (3-2)$$ + +Based on $S_{1i}$ , prediction signal $X_{1i}$ is given as + +$$X_{1i} = \begin{cases} M_i, \text{ if } S_{1i} = 0, \\ B_i, \text{ if } S_{1i} = 1. \end{cases} \quad (3-3)$$ + +If pel $i$ is either omitted due to subsampling and/or field repetition or forced intraframe coded or in burst $B$ , its corresponding $R_i(i)$ is set to 0 regardless of equation (3-2). + +![Block diagram of Adaptive prediction (FIGURE 10/H.120). The diagram shows an input signal passing through a Limiter to produce 'x'. This 'x' is subtracted from a 'Predicted value X2' at a summing node. The result is sent to a Quantizer, which outputs the 'Prediction error, e'. This error is added to a 'Local decoder output, X' at another summing node. The 'Local decoder output, X' is also fed into an Interpolator, which produces an 'Interpolator output, Y'. This 'Y' is fed into a Predictor block. The Predictor block contains three sub-prediction units: 'Intraframe prediction' (input 'I'), 'Motion compensated interframe prediction' (input 'M'), and 'Background prediction' (input 'B'). These units are controlled by switches labeled '1', '0', and '0' respectively, which are in turn controlled by prediction status signals 'S2' and 'S1'. The output of the selected prediction unit is the 'Predicted value X1'. The 'Predicted value X1' is also fed into the subtraction node. To the left of the Predictor block, there are two grid diagrams showing reference signals. The top grid shows 'R2' signals at positions (i-456), (i-455), (i-454) in the top row, and (i-2), (i-1), and 'S2i' in the middle row. The bottom grid shows 'R1' signals at positions (i-456), (i-455), (i-454) in the top row, and 'S1i' in the bottom row. A code 'T1513880-93/d07' is at the bottom right of the diagram.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +Block diagram of Adaptive prediction (FIGURE 10/H.120). The diagram shows an input signal passing through a Limiter to produce 'x'. This 'x' is subtracted from a 'Predicted value X2' at a summing node. The result is sent to a Quantizer, which outputs the 'Prediction error, e'. This error is added to a 'Local decoder output, X' at another summing node. The 'Local decoder output, X' is also fed into an Interpolator, which produces an 'Interpolator output, Y'. This 'Y' is fed into a Predictor block. The Predictor block contains three sub-prediction units: 'Intraframe prediction' (input 'I'), 'Motion compensated interframe prediction' (input 'M'), and 'Background prediction' (input 'B'). These units are controlled by switches labeled '1', '0', and '0' respectively, which are in turn controlled by prediction status signals 'S2' and 'S1'. The output of the selected prediction unit is the 'Predicted value X1'. The 'Predicted value X1' is also fed into the subtraction node. To the left of the Predictor block, there are two grid diagrams showing reference signals. The top grid shows 'R2' signals at positions (i-456), (i-455), (i-454) in the top row, and (i-2), (i-1), and 'S2i' in the middle row. The bottom grid shows 'R1' signals at positions (i-456), (i-455), (i-454) in the top row, and 'S1i' in the bottom row. A code 'T1513880-93/d07' is at the bottom right of the diagram. + +S Prediction status signal +R Prediction reference signal + +FIGURE 10/H.120 +Adaptive prediction + +##### 3.6.2.2.2 Interframe prediction/intraframe prediction + +Prediction status signal $S_{2i}$ for pel $i$ is determined as + +$$S_{2i} = R_2(i - 1) * R_2(i - 455) \quad (3-4)$$ + +where prediction reference signal $R_2(i)$ is + +$$R_2(i) = \begin{cases} 0 & \text{if } |Y_i - I_i| \geq |Y_i - X_{1i}|, \\ 1 & \text{if otherwise.} \end{cases} \quad (3-5)$$ + +Based on $S_{2i}$ prediction signal $X_{2i}$ is given as + +$$X_{2i} = \begin{cases} X_{1i} & \text{if } S_{2i} = 0, \\ I_i & \text{if } S_{2i} = 1. \end{cases} \quad (3-6)$$ + +If pel $(i - 1)$ is omitted due to subsampling, $R_2(i - 2)$ is used instead of $R_2(i - 1)$ . On the other hand, if pel $(i - 455)$ is omitted, $R_2(i - 454) * R_2(i - 456)$ is used instead of $R_2(i - 455)$ . If pel $i$ is forced intraframe-coded, its corresponding $R_2(i)$ is set to 1 regardless of equation (3-5). + +If pel $i$ is omitted due to field repetition, its corresponding $R_2(i)$ is set to 0 regardless of equation (3-5). When pel $i$ is not forced-intraframe coded, $R_2(i)$ in burst $B$ is set to 0. + +#### 3.6.2.3 Background generation + +The background prediction value is generated scene adaptively as + +$$b_i = b_i^{-f} + v(k) \operatorname{sgn} \left( Y_i - b_i^{-f} \right) u \left( Y_i - Y_i^{-f} \right) \quad (3-7)$$ + +where + +$$u \left( Y_i - Y_i^{-f} \right) = \begin{cases} 1 \text{ if } |Y_i - Y_i^{-f}| \leq L, \\ 0 \text{ if otherwise.} \end{cases} \quad (3-8)$$ + +$$v(k) = \begin{cases} 1, \text{ for one frame period in every block of } k \text{ frames} \\ 0, \text{ for consecutive } (k - 1) \text{ frames following the frame of } v(k) = 1 \end{cases}$$ + +and + +$b_i$ is the background prediction value for the present frame; + +$b_i^{-f}$ is the background prediction value for the previous frame; + +$Y_i$ is the interpolator output for the present frame; + +$Y_i^{-f}$ is the interpolator output for the previous frame; + +$u$ is the still area detection function; + +$k$ is the background update control parameter; and + +$L$ is the threshold value. + +Parameters $k$ and $L$ are set as $k = 8$ and $L = 1$ . It is noted that for hardware simplification, $b_i^{-f}$ , instead of $b_i$ , is used as background prediction value $B_i$ (see Figure 11). + +#### 3.6.2.4 Forced intraframe prediction + +This codec usually used the demand refresh mode to prevent the defected picture due to transmission errors from being left in the decoder frame memory. The demand refresh mode is carried out if BWP (bit 3.15.4 in codec-to-codec information) = 0, which indicates that backward path from decoder to coder is available. However, the cyclic refresh mode is also provided, considering such applications as broadcasting communication where no backward path (from decoder to coder) is available. This mode is carried out when BWP = 1. + +For either of the two refresh modes, the prediction function is forcibly set to intraframe prediction. + +In the demand refresh mode, the motion frame memory and the background frame memory are updated block-line by block-line within a frame time by writing the interpolator output simultaneously. Once demand refresh starts by receiving DRR in the coder, the following DRR (demand refresh request command) received is disregarded for one second (see Note). + +![Block diagram of background generation circuit. Inputs include 'Revision control signal BUC', 'Interpolator output Y', and 'Background prediction signal B'. The 'Still area detection circuit' receives 'Y' and 'BUC'. Its output goes to an AND gate along with 'BUC'. The AND gate output is labeled v(k) · u and goes to the 'Controller'. 'Y' also goes to a summing junction (+/-) whose output goes to the 'Controller'. The 'Controller' output goes to another summing junction (+/-) along with 'b-f' (from 'Background frame memory'). The output of this second summing junction is labeled 'b' and goes to the 'Background frame memory'. The 'Background frame memory' output is also labeled 'b-f' and goes to the 'Background prediction signal B' output. Reference code T1513890-93/d08 is shown at the bottom right.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +Block diagram of background generation circuit. Inputs include 'Revision control signal BUC', 'Interpolator output Y', and 'Background prediction signal B'. The 'Still area detection circuit' receives 'Y' and 'BUC'. Its output goes to an AND gate along with 'BUC'. The AND gate output is labeled v(k) · u and goes to the 'Controller'. 'Y' also goes to a summing junction (+/-) whose output goes to the 'Controller'. The 'Controller' output goes to another summing junction (+/-) along with 'b-f' (from 'Background frame memory'). The output of this second summing junction is labeled 'b' and goes to the 'Background frame memory'. The 'Background frame memory' output is also labeled 'b-f' and goes to the 'Background prediction signal B' output. Reference code T1513890-93/d08 is shown at the bottom right. + +FIGURE 11/H.120 +Background generation + +In the cyclic refresh mode, the two memories are simultaneously updated two lines at a time by writing the interpolator output. When a field is omitted due to field repetition, the background frame memory is updated by the signal which updates the motion frame memory. It should be noted that the command for the cyclic refresh mode is ignored in block-lines where updating based on the demand refresh mode is carried out. + +NOTE – If a transmission error happens on the line from the codec A to the codec B, the decoder of the codec B detects the error occurrence and generates a demand refresh request information (DR). This DR is passed to the coder of the codec B and transmitted as a demand refresh request command (DRR) to the codec A. When the decoder of the codec A receives DRR, a demand refresh confirmation information DDR is passed to the coder of the codec A. Finally, demand refresh mode is operated along with transmission of a demand refresh mode command (DRM) from the codec A to the codec B. + +#### 3.6.2.5 Definition of blanking and block-line and edge pels treatment + +**3.6.2.5.1** The kinds of pels arranged on a horizontal scanning line (see Figure 8), for which prediction functions are defined, are as follows: + +| | | +|-------------|-----------| +| Burst B | 7 pels; | +| Colour C | 64 pels; | +| Luminance Y | 384 pels. | + +The vertical blanking periods are treated in the same way as active lines. + +##### 3.6.2.5.2 Block-line + +See Figure 12. + +In the first field, 8 lines consisting of the 8th to the 15th lines form the first block-line, with every 8 lines following this forming each a block-line. In the second field, 8 lines consisting of the 7th to the 14th lines form the 33rd block-line. Each field has 32 block-lines. + +The last block-line in a frame is defined as the 8 lines which include the last line of the frame, or the line closest to the head line of the frame. The position of the video last line in the last block-line is coded as frame position. + +![Diagram of a video frame structure showing fields, block-lines, and reset lines. The top part shows a grid of lines numbered 1 to 256 for the first field and 1 to 256 for the second field. The first field has 7 lines in the first block-line, followed by 256 lines in the first block-line, and 6 lines in the reset lines. The second field has 256 lines in the first block-line, followed by 6 lines in the reset lines, and 256 lines in the first block-line. The diagram also shows the 'Last line in a frame', 'First line in a frame', 'First field', 'Second field', 'FP = 0', 'Last block-line', 'First block-line', 'Reset lines', and 'T1513900-93/d09'.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +Diagram of a video frame structure showing fields, block-lines, and reset lines. The top part shows a grid of lines numbered 1 to 256 for the first field and 1 to 256 for the second field. The first field has 7 lines in the first block-line, followed by 256 lines in the first block-line, and 6 lines in the reset lines. The second field has 256 lines in the first block-line, followed by 6 lines in the reset lines, and 256 lines in the first block-line. The diagram also shows the 'Last line in a frame', 'First line in a frame', 'First field', 'Second field', 'FP = 0', 'Last block-line', 'First block-line', 'Reset lines', and 'T1513900-93/d09'. + +FP Frame position +X Reset line + +NOTE – When the last line in a frame falls on the $n$ th line of the last block-line, $FP = \text{mod}(n,8)$ . + +FIGURE 12/H.120 +**Definition of block-line and reset line** + +##### 3.6.2.5.3 Reset lines + +The lines which are excluded from block-lines are defined as reset lines. These reset lines are clamped to 0 in the predictive coding and decoding loops, or the corresponding prediction values $X_2$ and prediction errors $e$ in Figure 10 are set to 0. The reset lines are prediction-coded in normal mode with adaptive prediction and by setting $v = 0$ . + +**3.6.2.5.4** Edge pels suffer from crosstalk due to interpolation between B and C, C and Y, and Y and B. In order to prevent such crosstalk, the first 3 pels in B, the last pel in B and the first pel in Y are clamped to 0 at the source coder input IDM signal as in Figure 13. + +![Diagram showing pel insertion for preventing crosstalk. It shows a sequence of pels: 0, C93, 0, C125, followed by a break, then C881, 0, Y123, followed by a break, and finally Y887. Below this, the diagram shows the lengths of the segments: 3 pels for the first segment (0, C93, 0), 3 pels for the second segment (C125), 1 pel for the third segment (C881), 64 pels for the fourth segment (Y123), and 384 pels for the fifth segment (Y887). The segments are labeled B, C, and Y. The diagram also shows 'T1513900-93/d10'.](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +Diagram showing pel insertion for preventing crosstalk. It shows a sequence of pels: 0, C93, 0, C125, followed by a break, then C881, 0, Y123, followed by a break, and finally Y887. Below this, the diagram shows the lengths of the segments: 3 pels for the first segment (0, C93, 0), 3 pels for the second segment (C125), 1 pel for the third segment (C881), 64 pels for the fourth segment (Y123), and 384 pels for the fifth segment (Y887). The segments are labeled B, C, and Y. The diagram also shows 'T1513900-93/d10'. + +NOTE – This figure shows an odd line in the first field. See Figure 8 as for pel numbers. + +FIGURE 13/H.120 +**Zero insertion for preventing crosstalks due to interpolation** + +**3.6.2.5.5** Edge pels are not treated specifically in the source coder and decoder. That is, video signals including reset lines and the 3 clamped pels in B are processed as if they were existing continuously (see Note). Consequently, even if a motion vector points to pels outside the active picture area, it functions as a delay control for the input time serial video signal. + +NOTE – The right end of each line in the picture is assumed to be connected to the left end of the next line, and the lower end of each frame is assumed to be connected to the upper end of the next frame. + +In the forced intraframe prediction mode, the prediction value for the first pel of each line is set to 0. + +For the burst signal, no adaptive prediction nor subsampling is applied and no motion vectors are transmitted. + +#### **3.6.2.6 Prediction and interpolation functions** + +Prediction functions and interpolation functions are shown in Table 4 for all of the coding modes. It should be noted that motion vectors for the colour signal can be set to 0 without much loss of coding efficiency. + +#### **3.6.2.7 Quantization** + +Prediction errors for video signals are quantized using one of the four quantizing characteristics indicated in Table 5, that is, $Q_0$ (57 levels), $Q_1$ (57 levels), $Q_2$ (51 levels) and $Q_3$ (37 levels). The same set of quantizing characteristics are applied regardless of prediction functions. + +#### **3.6.2.8 Limiter in prediction loop** + +No limiter is allocated in the prediction loop. Accordingly, the input signal $x$ for the prediction loop is limited to $-124 \leq x \leq 123$ so that the local decoder output $X$ is maintained in the $-128 \leq X \leq 127$ range. + +#### **3.6.2.9 Frame memory parity check** + +Parity is counted for each bit plane of the interpolator output during a video frame period from the 1st to the 64th block-line as defined in Figure 12. If block-lines are omitted in field repetition mode, parity is not counted during these omitted block-lines. + +Eight odd parity bits are sent to the decoder, where they are compared with the parity bits of the decoder interpolator output to detect uncorrected errors. If any difference between received and counted parity bits is found, a demand refresh is requested from the decoder to the coder. + +#### **3.6.2.10 Suspension of coding operation** + +When the information is generated to the degree that the transmission buffer memory overflows, coding operation is suspended by setting $e = 0$ and $v = 0$ . This stop mode is defined only in the coder. Interpolation and prediction functions for this mode are defined as either of NRM, SBS, FRP or RFS modes according to the control of the coding parameter controller. + +### **3.6.3 Motion vector transmission** + +#### **3.6.3.1 Block size** + +A block for motion compensation consists of 8 lines (vertical) by 16 pels (horizontal). + +#### **3.6.3.2 Maximum tracking range** + +Motion vectors are tracked in the range of +7 to -7 lines (vertical) and +15 pels (horizontal) at its maximum. The decoder should be able to reproduce any vector in this maximum range. + +TABLE 4/H.120 + +#### **Prediction and interpolation functions** + +| Coding mode | Kind of pel | Prediction functions P(Z) (Note 1) | | | Interpolation functions I(Z) (Note 2) | | | +|------------------|-------------------------------------|--------------------------------------------------------------------------------------------------|----------|----------|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------|----------| +| | | $P_Y(Z)$ | $P_C(Z)$ | $P_B(Z)$ | $I_Y(Z)$ | $I_C(Z)$ | $I_B(Z)$ | +| Normal | Coded | $Z^{-1}; S_2 = 1$
$Z^{-F+V}; S_2 = 0, S_1 = 0$
$P_b(Z) \text{ (Note 3)}; S_2 = 0, S_1 = 1$ | | $Z^{-F}$ | 1 | | | +| Subsampling | Coded | $Z^{-2} \text{ (Note 4)}; S_2 = 0$
$Z^{-F+V}; S_2 = 0, S_1 = 0$
$P_b(Z); S_2 = 0, S_1 = 1$ | | | 1 | | | +| | Omitted | (Not defined) | | | $\frac{1}{2} \left\{ \frac{1}{2} (Z^{-1} + Z^{+1}) + \frac{1}{2} (Z^{-H} + Z^{+H}) \right\}$ | $\frac{1}{2} (Z^{-1} + Z^{+1})$ | | +| Field repetition | Omitted | (Not defined) | | | $\frac{1}{2} (Z^{-262H} + Z^{-263H})$ | $Z^{-263H}; \text{first field}$
$Z^{-262H}; \text{second field}$ | | +| Refresh | N
R
M
Coded | $Z^{-1}$ | | | 1 | | | +| | S
B
S
Coded

Omitted | $Z^{-2} \text{ (Note 4)}$ | | | 1 | | | +| | | (Not defined) | | | $\frac{1}{2} (Z^{-1} + Z^{+1})$ | | | + +NOTES + +1 $S_1$ and $S_2$ are prediction status signals defined in 3.6.2.2. + +2 To deal with fractions generated by operation of $(A + B)/2$ , $(A + B + 1)/2$ is executed and the 8 MSBS are used. + +3 Background is generated as described in 3.6.2.3. + +4 $Z^{-1}$ , if the previous pel is coded. + +TABLE 5/H.120 + +##### **Quantizing characteristics** + +| $Q_0$ | | $Q_1$ | | $Q_2$ | | $Q_3$ | | +|-------------|--------------|-------------|--------------|-------------|--------------|-------------|--------------| +| Input range | Output level | Input range | Output level | Input range | Output level | Input range | Output level | +| 0 to 1 | 0 | 0 to 3 | 0 | 0 to 4 | 0 | 0 to 6 | 0 | +| 2 | 1 | 4 to 6 | 3 | 5 to 8 | 5 | 7 to 11 | 7 | +| 3 | 2 | 7 to 8 | 6 | 9 to 12 | 10 | 12 to 17 | 14 | +| 4 to 5 | 3 | 9 to 10 | 9 | 13 to 17 | 15 | 18 to 24 | 21 | +| 6 to 7 | 5 | 11 to 13 | 12 | 18 to 22 | 20 | 25 to 31 | 28 | +| 8 to 9 | 7 | 14 to 16 | 15 | 23 to 27 | 25 | 32 to 38 | 35 | +| 10 to 11 | 10 | 17 to 19 | 18 | 28 to 32 | 30 | 39 to 45 | 42 | +| 12 to 14 | 13 | 20 to 22 | 21 | 33 to 37 | 35 | 46 to 52 | 49 | +| 15 to 17 | 16 | 23 to 26 | 24 | 38 to 42 | 40 | 53 to 59 | 56 | +| 18 to 20 | 19 | 27 to 30 | 28 | 43 to 47 | 45 | 60 to 66 | 63 | +| 21 to 23 | 22 | 31 to 34 | 32 | 48 to 52 | 50 | 67 to 73 | 70 | +| 24 to 26 | 25 | 35 to 39 | 37 | 53 to 57 | 55 | 74 to 80 | 77 | +| 27 to 29 | 28 | 40 to 44 | 42 | 58 to 62 | 60 | 81 to 87 | 84 | +| 30 to 32 | 31 | 45 to 49 | 47 | 63 to 67 | 65 | 88 to 94 | 91 | +| 33 to 37 | 35 | 50 to 54 | 52 | 68 to 72 | 70 | 95 to 101 | 98 | +| 38 to 42 | 40 | 55 to 59 | 57 | 73 to 77 | 75 | 102 to 108 | 105 | +| 43 to 48 | 45 | 60 to 64 | 62 | 78 to 82 | 80 | 109 to 115 | 112 | +| 49 to 54 | 51 | 65 to 69 | 67 | 83 to 87 | 85 | 116 to 123 | 119 | +| 55 to 60 | 57 | 70 to 74 | 72 | 88 to 92 | 90 | 124 to 255 | 127 | +| 61 to 67 | 64 | 75 to 79 | 77 | 93 to 97 | 95 | | | +| 68 to 74 | 71 | 80 to 84 | 82 | 98 to 102 | 100 | | | +| 75 to 81 | 78 | 85 to 89 | 87 | 103 to 107 | 105 | | | +| 82 to 88 | 85 | 90 to 94 | 92 | 108 to 112 | 110 | | | +| 89 to 95 | 92 | 95 to 99 | 97 | 113 to 118 | 115 | | | +| 96 to 102 | 99 | 100 to 104 | 102 | 119 to 124 | 121 | | | +| 103 to 109 | 106 | 105 to 109 | 107 | 125 to 255 | 127 | | | +| 110 to 116 | 113 | 110 to 116 | 113 | | | | | +| 117 to 123 | 120 | 117 to 123 | 120 | | | | | +| 124 to 255 | 127 | 124 to 255 | 127 | | | | | + +NOTE – Characteristics are symmetrical with respect to zero. + +#### 3.6.3.3 Definition of vector direction + +The motion vector $v (v_x, v_y)$ is defined as + +$$v_x = x_a - x_b \tag{3-9}$$ + +and + +$$v_y = y_a - y_b$$ + +where the block positions in the present frame and in the corresponding previous frame are $(x_a, y_a)$ and $(x_b, y_b)$ , respectively. The $x$ and $y$ directions are identical to those of the horizontal and vertical scanning. This definition means that delay in the interframe prediction loop increases for $v_x, v_y$ greater than 0. + +#### 3.6.3.4 Motion detection method + +A motion vector is detected for each block by the interframe block matching method. Detailed detection methods are left to each hardware implementation (see Note). + +NOTE – When multi-field repetition is employed, the detected vector for the previous transmitted frame can be utilized as the initial value for vector detection in the present frame to be omitted, and the detected vector for the present frame can be utilized as the initial value for vector detection in the next frame, and so on. + +### 3.6.4 Coding parameter control + +#### 3.6.4.1 Control method + +Coding control is carried out by selecting quantizing characteristics described in 3.6.2.7 and coding modes described in 3.6.2.1. + +#### 3.6.4.2 Control timing + +Coding parameters are controlled according to the timing and commands as shown in Table 6. + +TABLE 6/H.120 + +#### Coding parameter, control unit and commands + +| Coding parameter | Control unit | Commands | +|------------------|------------------------------------------------------|---------------------------------------------------| +| Normal | Frame
Block-line (8 lines)
Block (8 × 16 pels) | SBC = 1, IFM = 1, FRP = 1 and
TRANS (SBS: off) | +| Quantization | Block-line | QC1 and QC2 | +| Field repetition | Block-line (Note) | FRP = 0 | +| Subsampling | Frame | SBC = 0 and FRP = 1 | +| | Block | TRANS (SBS: on) and FRP = 1 | +| Stop | Arbitrary | Prediction error $e = 0$
Motion vector $v = 0$ | +| Demand refresh | Block-lines | DRM = 0 and IFM = 0 | +| Cyclic refresh | Two lines | DRM = 1, IFM = 0 and CRM 1, 2 | + +NOTE – Consecutive 32 block-lines from the first through the 32nd block-lines or from the 33rd through the 64th block-lines are omitted for ordinary field repetition. Other methods are also possible using the FRP command controlled in the unit of block-line. + +#### 3.6.4.3 Control sequence + +The control sequence is determined based on buffer memory occupancy and other control information. Since this sequence does not affect interworking between different design codecs, it is left to each hardware implementation. However, the codec operating principle is that the coder determines all operating modes, which are transmitted with the coded video data to the decoder as a combination of commands. The decoder reproduces the video signal according to the received commands and data. A control sequence example is shown in Annex F. + +### 3.6.5 Entropy coding + +#### 3.6.5.1 Configuration of entropy coding + +The configuration of entropy coding is shown in Figure 14. The entropy coder compresses the data of the prediction error $e$ and motion vector $v$ , which are provided by the source coder, using variable length coding. These compressed data are multiplexed with coding mode data $m$ and fed into the transmission buffer memory. The multiplexed data format is outlined in Figure 15. + +![Figure 14: Configuration of entropy coding. A block diagram showing inputs (Parity coding mode p, m, SBS; Prediction error e; Motion vector v) entering blocks (Mode coding, VLC 1, VLC 2). The outputs of these blocks are combined in a MUX to produce Multiplexed data. A legend defines SBS as Subsampling and VLC as Variable word length coder.](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +Parity coding mode: p, m, SBS + +Prediction error: e + +Motion vector: v + +Mode coding + +VLC 1 + +VLC 2 + +MUX + +Multiplexed data + +T1513920-93/d11 + +SBS Subsampling +VLC Variable word length coder + +Figure 14: Configuration of entropy coding. A block diagram showing inputs (Parity coding mode p, m, SBS; Prediction error e; Motion vector v) entering blocks (Mode coding, VLC 1, VLC 2). The outputs of these blocks are combined in a MUX to produce Multiplexed data. A legend defines SBS as Subsampling and VLC as Variable word length coder. + +FIGURE 14/H.120 +Configuration of entropy coding + +![Figure 15: Multiplexed data format. A diagram showing a sequence of blocks representing a TV frame, divided into block-lines. Each block-line contains fields: FS, FMD, LMD, MVD, PED. The diagram shows the first, second, and n-th block-lines. A legend defines the fields: FS (Frame sync), FMD (Frame mode data), LS (Line sync), LMD (Line mode data), MVD (Motion vector data), PED (Prediction error data).](896e86ed12aff206d302c64f2e3091fa_img.jpg) + +1 TV frame + +First block-line: FS, FMD, LMD, MVD, PED + +Second block-line: LS, LMD, MVD, PED + +n-th block line: LS, LMD, MVD, PED + +T1513930-93/d12 + +FS Frame sync +FMD Frame mode data +LS Line sync +LMD Line mode data +MVD Motion vector data +PED Prediction error data + +Figure 15: Multiplexed data format. A diagram showing a sequence of blocks representing a TV frame, divided into block-lines. Each block-line contains fields: FS, FMD, LMD, MVD, PED. The diagram shows the first, second, and n-th block-lines. A legend defines the fields: FS (Frame sync), FMD (Frame mode data), LS (Line sync), LMD (Line mode data), MVD (Motion vector data), PED (Prediction error data). + +FIGURE 15/H.120 +Multiplexed data format + +#### 3.6.5.2 Commands for coding modes and data structure + +The commands for coding modes and data structure are defined as follows: + +##### 3.6.5.2.1 Frame sync (FS) + +The frame sync is a unique word to designate the start of a video frame and its value is: 0000000000000010. + +##### 3.6.5.2.2 Frame mode data (FMD) + +The format of the frame mode data is given in Figure 16. + +![Figure 16/H.120: Diagram of the frame mode data (FMD) structure. It shows a 'Head' section followed by fields PT, FM1, BC, FM2, FM3, and FM4. Below the fields are brackets indicating bit widths: 10 for PT, 10 for FM1, 10 for BC, 10 for FM2, 10 for FM3, and 30 for FM4. The text 'byte (Ø)' is below the brackets. The identifier 'T1513940-93/d13' is in the top right.](b6ad8b32179842fca5ad086cf22b03eb_img.jpg) + +| | | | | | | | +|------|----------|-----|----|-----|-----|-----| +| Head | PT | FM1 | BC | FM2 | FM3 | FM4 | +| | 10 | 10 | 10 | 10 | 10 | 30 | +| | byte (Ø) | | | | | | + +T1513940-93/d13 + +Figure 16/H.120: Diagram of the frame mode data (FMD) structure. It shows a 'Head' section followed by fields PT, FM1, BC, FM2, FM3, and FM4. Below the fields are brackets indicating bit widths: 10 for PT, 10 for FM1, 10 for BC, 10 for FM2, 10 for FM3, and 30 for FM4. The text 'byte (Ø)' is below the brackets. The identifier 'T1513940-93/d13' is in the top right. + +FIGURE 16/H.120 + +###### a) *Parity data (PT)* + +Odd parity for each of the 8-bit planes of the interpolator output during the previous frame period (MSB first). + +###### b) *Frame mode 1 (FM1)* + +The format of the frame mode 1 is given in Figure 17. + +![Figure 17/H.120: Diagram of the frame mode 1 (FM1) structure. It is a single row of 8-bit bytes: SBC, BRC, BUC, DRM, 1, FP2, FP1, FP0.](3b950edb26a62dde5f3c0f41d9983edc_img.jpg) + +| | | | | | | | | +|-----|-----|-----|-----|---|-----|-----|-----| +| SBC | BRC | BUC | DRM | 1 | FP2 | FP1 | FP0 | +|-----|-----|-----|-----|---|-----|-----|-----| + +Figure 17/H.120: Diagram of the frame mode 1 (FM1) structure. It is a single row of 8-bit bytes: SBC, BRC, BUC, DRM, 1, FP2, FP1, FP0. + +FIGURE 17/H.120 + +###### i) *Subsample control (SBC)* + +When SBC = 0, subsampling is carried out throughout the frame excluding burst signals, reset lines and block-lines with FRP = 0. See 3.6.2.1. + +###### ii) *Background revision control (BRC)* + +When BRC = 0, the contents of the motion frame memory are transferred to the background frame memory during this frame period. See 3.6.2.4. + +###### iii) *Background update control (BUC)* + +When BUC = 0, the background frame memory is updated. If BRC is operating, it has priority. See 3.6.2.3. + +###### iv) *Demand refresh mode (DRM)* + +When DRM = 0, coding is carried out with demand refresh mode. See 3.6.2.4. + +###### v) *Frame position, FP2-FP0 (see Note)* + +This 3-bit word designates the position of the head line of the video frame or the first line in the first field (MSB first). See Figure 12. + +NOTE – FP bits are employed for preventing degradation in the case where the input signals are asynchronously switched to another signal where those signals have different sync phase or different sync frequency. For this purpose, the horizontal sync pulse interval in the codec, namely the picture element numbers per line should be kept as 455 samples, even in the transition period. Furthermore, input signal switching which takes place during the reset line periods should be ignored. + +###### c) *Buffer control (BC)* + +The staying time of FS in the transmission buffer memory is coded into an 8 bit word (MSB first). See 3.6.6.1. + +###### d) *Frame mode 2 (FM2)* + +The format of frame mode 2 is given in Figure 18. + +| | | | | | | | | +|---|-----|-----|------|------|-----|-----|---| +| 1 | DRR | CMS | CRM1 | CRM2 | SF1 | MAF | 1 | +|---|-----|-----|------|------|-----|-----|---| + +FIGURE 18/H.120 + +###### i) *Demand refresh request (DRR)* + +When DRR = 0, the decoder requests a demand refresh to the coder. See 3.6.2.9. + +###### ii) *Colour/monochrome state (CMS)* + +Colour (bit = 1) / monochrome (bit = 0) where monochrome is optional and the default mode is colour. + +###### iii) *CRM1, CRM2: cyclic refresh mode* + +This 2-bit word designates the position of the two lines in a block-line which is cyclic refreshed. See Figure 19. See also 3.6.2.4. + +###### iv) *Spare frame mode (SF1)* + +###### v) *Mode addition flag (MAF)* + +When MAF = 0, FM4 is added. + +![Diagram showing the mapping of CRM1 and CRM2 bits to specific lines within a block-line. CRM1=0, CRM2=0 maps to lines 1 and 2. CRM1=0, CRM2=1 maps to lines 3 and 4. CRM1=1, CRM2=0 maps to lines 5 and 6. CRM1=1, CRM2=1 maps to lines 7 and 8. A bracket on the right groups all 8 lines as a 'Block-line'. Source: T1513950-93/d14](6b95a21425e452581ef1a50ee2a6d391_img.jpg) + +| | | | | | +|------|------|---------|------|------------| +| CRM1 | CRM2 | | Line | | +| 0 | 0 | { ————— | 1 | Block-line | +| | | ————— | 2 | | +| 0 | 1 | { ————— | 3 | | +| | | ————— | 4 | | +| 1 | 0 | { ————— | 5 | | +| | | ————— | 6 | | +| 1 | 1 | { ————— | 7 | | +| | | ————— | 8 | | + +T1513950-93/d14 + +Diagram showing the mapping of CRM1 and CRM2 bits to specific lines within a block-line. CRM1=0, CRM2=0 maps to lines 1 and 2. CRM1=0, CRM2=1 maps to lines 3 and 4. CRM1=1, CRM2=0 maps to lines 5 and 6. CRM1=1, CRM2=1 maps to lines 7 and 8. A bracket on the right groups all 8 lines as a 'Block-line'. Source: T1513950-93/d14 + +FIGURE 19/H.120 + +e) *Frame mode 3 (FM3)* + +National option 8-bit data. If not used, a code consisting of all ones (11111111) is inserted. + +f) *Frame mode 4 (FM4)* + +| | | | | | | | | | +|--------|------|------|------|---|------|------|------|------| +| Byte 1 | SF2 | SF3 | SF4 | 1 | SF5 | SF6 | SF7 | SF8 | +| Byte 2 | SF9 | SF10 | SF11 | 1 | SF12 | SF13 | SF14 | SF15 | +| Byte 3 | SF16 | SF17 | SF18 | 1 | SF19 | SF20 | SF21 | SF22 | + +SF2-SF22 Spare frame mode. + +##### 3.6.5.2.3 Line sync (LS) + +The line sync is a unique word to designate the start of a block-line and its value is: 0000000000000011. + +##### 3.6.5.2.4 Line mode data (LMD) + +The format of the line mode data is given in Figure 20. + +![Diagram of Line mode data (LMD) format showing a Head byte and an LDN byte.](e94cbc0895c6914a2bb53f150ab7495e_img.jpg) + +``` + ++------+-----+-----+-----+---+-----+-----+-----+-----+ +-------+ +| Head | QC1 | QC2 | IFM | 1 | LSK | FRP | SL1 | SL2 | | LDN | ++------+-----+-----+-----+---+-----+-----+-----+-----+ +-------+ + \_________________ 1 byte __________________/ \_ 1 byte _/ + T1513960-93/d15 + +``` + +The diagram illustrates the structure of the Line mode data (LMD). It begins with a 'Head' section consisting of eight bits: QC1, QC2, IFM, 1, LSK, FRP, SL1, and SL2. These eight bits are grouped by a bracket labeled '1 byte'. Following the head is the LDN (Line Data Number) byte, which is also grouped by a bracket labeled '1 byte'. The text 'T1513960-93/d15' is located at the bottom right of the diagram. + +Diagram of Line mode data (LMD) format showing a Head byte and an LDN byte. + +FIGURE 20/H.120 + +a) QC1, QC2: *Quantizing characteristics* + +| QC1 | QC2 | Characteristics (Table 5) | +|-----|-----|---------------------------| +| 0 | 0 | Q 0 | +| 0 | 1 | Q 1 | +| 1 | 0 | Q 2 | +| 1 | 1 | Q 3 | + +b) *Forced intraframe prediction mode (IFM)* + +When IFM = 0, the prediction function is fixed to intraframe prediction, throughout this block-line if DRM = 0, and at the two lines designated by CRM1 and CRM2 if DRM = 1. See 3.6.2.4. + +c) *Line skip (LSK)* + +When LSK = 0, the following byte (LDN, line data number) designates the number of block-lines which are skipped. See 3.6.5.5. LDN is coded similarly as the number of vector data, VDN. When LDN = *n*, consecutive (*n* + 1) block-lines are the same. Therefore $0 \leq n \leq 63$ . + +###### d) *Field repetition (FRP)* + +When FRP = 0, this block-line is omitted because of field repetition. This is valid even if IFM = 0. See 3.6.2.1. + +###### e) *SL1, SL2: Spare line mode* + +##### **3.6.5.2.5 Motion vector data (MVD)** + +The format of the motion vector data is given in Figure 21. + +###### a) *Vector data number (VDN)* + +Designates the byte number of the following vector data (VD) (in natural binary code, MSB first). + +###### b) *Vector data (VD)* + +Variable length coded motion vector data. + +![Diagram of Motion Vector Data (MVD) format. It shows a row of bytes: n7, n6, n5, 1, n4, n3, n2, n1, followed by a variable-length VD field, and a (Note) field. A bracket labeled 'VDN' covers the first eight bytes (n7 to n1). Another bracket labeled 'n byte' covers the VD field. The text 'T1513970-93/d16' is at the bottom right.](23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg) + +Diagram of Motion Vector Data (MVD) format. It shows a row of bytes: n7, n6, n5, 1, n4, n3, n2, n1, followed by a variable-length VD field, and a (Note) field. A bracket labeled 'VDN' covers the first eight bytes (n7 to n1). Another bracket labeled 'n byte' covers the VD field. The text 'T1513970-93/d16' is at the bottom right. + +NOTE – Dummy, see 3.6.5.4.6. + +FIGURE 21/H.120 + +##### **3.6.5.2.6 Prediction error data (PED) (variable word length coded)** + +The format of the prediction error data is given in Figure 22. + +![Diagram of Prediction Error Data (PED) format. It shows a row of bytes: PED, followed by a Dummy field containing '0'. A bracket labeled '(Integer) byte' covers the PED field. A bracket labeled 'Dummy' covers the second field. The text 'T1513980-93/d17' is at the bottom right.](1dbb1d90b2022a3a765c85929a515cc6_img.jpg) + +Diagram of Prediction Error Data (PED) format. It shows a row of bytes: PED, followed by a Dummy field containing '0'. A bracket labeled '(Integer) byte' covers the PED field. A bracket labeled 'Dummy' covers the second field. The text 'T1513980-93/d17' is at the bottom right. + +FIGURE 22/H.120 + +#### **3.6.5.3 Prediction error coding (VLC 1)** + +See Figure 14. + +##### 3.6.5.3.1 Coding method + +The quantizing level number corresponding to prediction error $e$ is coded based on its statistical characteristics. For $e \neq 0$ , variable word length coding is carried out using code V or F stating the quantizing level number (see Table 7). For $e = 0$ , run length code R is used to state a run (RL) of ineffective pels. Note that if RL = 1, a variable word length code $V_0$ or $F_0$ to state $e = 0$ is used (see Table 8). + +TABLE 7/H.120 + +###### Variable length code for non-zero amplitude prediction errors + +| Level number | Code length | V code | | Level number | Code length | F code | | +|--------------|-------------|---------|-------------|--------------|-------------|-------------|--| +| $V_0$ | 4 | 0 1 1 1 | | $F_0$ | 4 | 0 0 0 1 | | +| 1 | 2 | 1 S | | 1 | 6 | 1 1 1 1 1 S | | +| 2 | 5 | 0 1 1 0 | S | 2 | 6 | 1 1 1 1 0 S | | +| 3 | 7 | 0 1 0 1 | 1 1 S | 3 | 6 | 1 1 1 0 1 S | | +| 4 | 7 | 0 1 0 1 | 1 0 S | 4 | 6 | 1 1 1 0 0 S | | +| 5 | 8 | 0 1 0 1 | 0 1 1 S | 5 | 6 | 1 1 0 1 1 S | | +| 6 | 8 | 0 1 0 1 | 0 1 0 S | 6 | 6 | 1 1 0 1 0 S | | +| 7 | 8 | 0 1 0 1 | 0 0 1 S | 7 | 6 | 1 1 0 0 1 S | | +| 8 | 8 | 0 1 0 1 | 0 0 0 S | 8 | 6 | 1 1 0 0 0 S | | +| 9 | 9 | 0 1 0 0 | 1 1 1 1 S | 9 | 6 | 1 0 1 1 1 S | | +| 10 | 9 | 0 1 0 0 | 1 1 1 0 S | 10 | 6 | 1 0 1 1 0 S | | +| 11 | 9 | 0 1 0 0 | 1 1 0 1 S | 11 | 6 | 1 0 1 0 1 S | | +| 12 | 9 | 0 1 0 0 | 1 1 0 0 S | 12 | 6 | 1 0 1 0 0 S | | +| 13 | 9 | 0 1 0 0 | 1 0 1 1 S | 13 | 6 | 1 0 0 1 1 S | | +| 14 | 9 | 0 1 0 0 | 1 0 1 0 S | 14 | 6 | 1 0 0 1 0 S | | +| 15 | 9 | 0 1 0 0 | 1 0 0 1 S | 15 | 6 | 1 0 0 0 1 S | | +| 16 | 9 | 0 1 0 0 | 1 0 0 0 S | 16 | 6 | 1 0 0 0 0 S | | +| 17 | 10 | 0 1 0 0 | 0 1 1 1 1 S | 17 | 6 | 0 1 1 1 1 S | | +| 18 | 10 | 0 1 0 0 | 0 1 1 1 0 S | 18 | 6 | 0 1 1 1 0 S | | +| 19 | 10 | 0 1 0 0 | 0 1 1 0 1 S | 19 | 6 | 0 1 1 0 1 S | | +| 20 | 10 | 0 1 0 0 | 0 1 1 0 0 S | 20 | 6 | 0 1 1 0 0 S | | +| 21 | 10 | 0 1 0 0 | 0 1 0 1 1 S | 21 | 6 | 0 1 0 1 1 S | | +| 22 | 10 | 0 1 0 0 | 0 1 1 1 0 S | 22 | 6 | 0 1 0 1 0 S | | +| 23 | 10 | 0 1 0 0 | 0 1 0 0 1 S | 23 | 6 | 0 1 0 0 1 S | | +| 24 | 10 | 0 1 0 0 | 0 1 0 0 0 S | 24 | 6 | 0 1 0 0 0 S | | +| 25 | 10 | 0 1 0 0 | 0 0 1 1 1 S | 25 | 6 | 0 0 1 1 1 S | | +| 26 | 10 | 0 1 0 0 | 0 0 1 1 0 S | 26 | 6 | 0 0 1 1 0 S | | +| 27 | 10 | 0 1 0 0 | 0 0 1 0 1 S | 27 | 6 | 0 0 1 0 1 S | | +| 28 | 10 | 0 1 0 0 | 0 0 1 0 0 S | 28 | 6 | 0 0 1 0 0 S | | + +NOTE – S denotes sign. S = 0 for positive, S = 1 for negative. + +TABLE 8/H.120 + +###### **Run length code R for zero amplitude prediction errors** + +| RL
(Note 1) | Code length | Code word R | | | | Remark | +|----------------|-------------|-------------|-------------|-----------------------------|-------|-------------| +| 2 | 5 | 0 0 | 0 0 1 | | | | +| 3 | 5 | 0 0 | 0 0 0 | | | | +| 4 | 6 | 0 0 | 1 0 1 0 | | | | +| 5 | 6 | 0 0 | 1 0 0 1 | | | | +| 6 | 6 | 0 0 | 1 0 0 0 | | | | +| 7 | 7 | 0 0 | 1 0 1 1 1 | | | | +| 8 to 11 | 7 | 0 0 | 1 1 0 X X | | | X = 11 – RL | +| 12 | 8 | 0 0 | 1 1 1 1 0 1 | | | | +| 13 | 8 | 0 0 | 1 1 1 1 0 0 | | | | +| 14 to 17 | 8 | 0 0 | 1 1 1 0 X X | | | X = 17 – RL | +| 18 to 25 | 9 | 0 0 | 0 1 1 1 X X | X | | X = 25 – RL | +| 26 to 33 | 10 | 0 0 | 0 1 1 0 0 X | X X | | X = 33 – RL | +| 34 to 37 | 10 | 0 0 | 0 1 0 1 0 0 | X X | | X = 37 – RL | +| 38 to 64 | 12 | 0 0 | 0 1 0 0 1 X | X X X X | | X = 69 – RL | +| MK1 | 13 | 0 0 | 1 0 1 1 0 Y | Y Y Y Y Y Y | | | +| MK2 | 14 | 0 0 | 1 1 1 1 1 1 | Y Y Y Y Y Y | | Y = 0 to 63 | +| MK3 | 14 | 0 0 | 1 1 1 1 1 0 | Y Y Y Y Y Y | | | +| MK4 to 7 | 15 | 0 0 | 0 1 1 0 1 X | X Y Y Y Y Y Y | | X = 7 – MK | +| MK8 to 15 | 16 | 0 0 | 0 1 0 1 1 X | X X Y Y Y Y Y Y | | X = 15 – MK | +| MK16 to 19 | 16 | 0 0 | 0 1 0 1 0 1 | X X Y Y Y Y Y Y | | X = 19 – MK | +| MK20 to 34 | 18 | 0 0 | 0 1 0 0 0 1 | X X X X X Y Y Y | Y Y | X = 35 – MK | +| MK35 to 49 | 19 | 0 0 | 0 1 0 0 0 0 | 1 X X X X Y Y Y | Y Y Y | X = 50 – MK | +| MK50 to 56 | 19 | 0 0 | 0 1 0 0 0 0 | 0 1 X X X Y Y Y
(Note 2) | Y Y Y | X = 57 – MK | + +###### NOTES + +1 RL = $64 \times (\text{MK number}) + 1 + Y$ , $0 \leq Y \leq 63$ . + +2 The maximum run length is $(455 - 3) \times 8 = 3616$ . Corresponding MK and Y turn out to be 56 and 31, respectively. Hence, $0 \leq Y \leq 31$ for MK = 56. + +##### **3.6.5.3.2 Scanning sequence** + +Entropy coding for a video frame is carried out from the first to the last block lines, excluding reset lines. The frame sync (FS) and frame mode data (FMD) are codes in the first block-line. When the last line falls on the $n$ th line of the last block-line, the frame position is set to $FP = \text{md}(n, 8)$ . FP is transmitted to the decoder as a part of the frame mode data (see Note 1). + +Since the first three pels of each line are clamped to 0 in the predictive source coder, and the reset lines are so defined as described in 3.6.2.5.3, the pels to be entropy coded can be indicated as in Figure 23 (see Note 2). + +The scanning sequence is a block scan as shown in Figure 24. The first block after scan conversion consists of 4 pels $\times$ 8 lines = 32 pels. + +###### NOTE + +1 Without asynchronous switching of input video signals, the last block-line coincides with the 64th block-line and $FP = 0$ . + +2 Entropy coding is not carried out for the reset lines defined in Figure 12. The number of reset lines in the first field varies according to the FP value. + +![Diagram of two 452 x 256 blocks with padding. The top block has a 7-pixel high padding at the top and a 6-pixel high padding at the bottom. The bottom block has a 3-pixel wide padding on the left. The width of each block is 452 pixels, and the height of each block is 256 pixels.](e8e818455bb0d1a6153299a388b94868_img.jpg) + +Diagram of two 452 x 256 blocks with padding. The top block has a 7-pixel high padding at the top and a 6-pixel high padding at the bottom. The bottom block has a 3-pixel wide padding on the left. The width of each block is 452 pixels, and the height of each block is 256 pixels. + +T1513990-93/d18 + +FIGURE 23/H.120 +Entropy-coded pels + +![Diagram showing the scanning sequence for entropy-coded pixels. It is divided into three parts: 'Omitted' (3 columns), 'First block' (4 columns), and 'Second block' (16 columns). The 'Omitted' part shows 3 columns of circles. The 'First block' part shows 4 columns of circles with arrows indicating a zigzag scanning pattern. The 'Second block' part shows 16 columns of circles with horizontal arrows indicating a row-by-row scanning pattern. The labels 'Omitted', 'First block', and 'Second block' are at the bottom. The label 'T1514000-93/d19' is at the bottom right.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Diagram showing the scanning sequence for entropy-coded pixels. It is divided into three parts: 'Omitted' (3 columns), 'First block' (4 columns), and 'Second block' (16 columns). The 'Omitted' part shows 3 columns of circles. The 'First block' part shows 4 columns of circles with arrows indicating a zigzag scanning pattern. The 'Second block' part shows 16 columns of circles with horizontal arrows indicating a row-by-row scanning pattern. The labels 'Omitted', 'First block', and 'Second block' are at the bottom. The label 'T1514000-93/d19' is at the bottom right. + +FIGURE 24/H.120 +Scanning sequence + +##### 3.6.5.3.3 Group of codes + +See Table 9. + +TABLE 9/H.120 + +| | Symbol | Number of codes | Length of codes | +|----------------------|--------|-----------------|-----------------| +| Amplitude code No. 1 | F | 57 | 4, 6 | +| Amplitude code No. 2 | V | 57 | 2-10 | +| Run length code | R | 3615 | 5-19 | + +F Pseudo fixed length code for stating quantizing level number. This code is introduced to shorten the maximum code length. +V Variable length code for stating quantizing number. +R Variable length code for stating run length of ineffective pels for $RL \geq 2$ . + +##### 3.6.5.3.4 Code transition rule + +The rule is shown in Figure 25 and a prediction error coding example is given in Annex F. + +The following points should be noted: + +- the starting code is either the V or R code; +- the last run in a block-line may not be transmitted since the LS or FS command can be utilized as a termination of the last run; +- coding is carried out assuming that omitted pels due to subsampling do not exist; +- some 0s are filled at the tail tail-end of the PED as dummies to make the total number of bits for the block-line data a multiple of 8. + +![Diagram illustrating the code transition rule for prediction error data. It shows three states: F (Pseudo fixed length code), V (Variable length code), and R (Run length code). Transitions are as follows: F to V (labeled V5-V28 and F0-F4), V to F (labeled F5-F28), V to V (self-loops labeled V0 (rl=1) and V1-V4), V to R (labeled RL_i (rl>=2)), and R to V (labeled RL_i (rl>=2)). A 'Block-line start' arrow points to the V state.](c1278da91cbcabe32628e589ebc47418_img.jpg) + +``` + +graph TD + Start[Block-line start] --> V((V)) + V --> V0["V0 (rl = 1)"] + V --> V14["V1 - V4"] + V --> F((F)) + F --> V + V --> R((R)) + R --> V + F --> F528["F5 - F28"] + V --> V528["V5 - V28"] + V --> F04["F0 - F4"] + +``` + +Diagram illustrating the code transition rule for prediction error data. It shows three states: F (Pseudo fixed length code), V (Variable length code), and R (Run length code). Transitions are as follows: F to V (labeled V5-V28 and F0-F4), V to F (labeled F5-F28), V to V (self-loops labeled V0 (rl=1) and V1-V4), V to R (labeled RL\_i (rl>=2)), and R to V (labeled RL\_i (rl>=2)). A 'Block-line start' arrow points to the V state. + +T1514010-93/d20 + +###### NOTES + +- RL is a length of the run to be coded, while rl is a number of continued pels whose $e = 0$ . +- Prediction error data start with an R or V code. R code is used if $rl \geq 2$ . Otherwise V code is used. +- The code can shift to V even if $RL \geq 2$ to prevent a buffer memory underflow. + +FIGURE 25/H.120 + +###### Code transition rule for prediction error data + +##### 3.6.5.3.5 Code assignments for F and V + +See Table 7. + +Code assignments are common to the four quantizing characteristics $Q_0, Q_1, Q_2$ and $Q_3$ . + +##### 3.6.5.3.6 Code assignments for R + +See Table 8. + +#### 3.6.5.4 Motion vector coding (VLC 2) + +##### 3.6.5.4.1 Coding method + +A motion vector $v$ , is first coded with predictive coding whose output $\Delta v$ , is variable length coded throughout a block-line. + +##### 3.6.5.4.2 Predictive coding + +The prediction algorithm is the previous block prediction which is + +$$\Delta v = v - v_1 \quad (3-10)$$ + +where $v$ and $v_1$ represent the present and the previous block vectors. The operation is carried out for each $x$ and $y$ component in two's complement form. The operated results are expressed with 5 bits for the $x$ component and 4 bits for the $y$ component neglecting carries (MSB first). Note that the decoder carries out the inverse operation $v = v_1 + \Delta v$ in two's complement from neglecting carries. + +The motion vector for the first block (horizontal blanking) is set to (0,0). + +##### 3.6.5.4.3 Variable length coding + +For $\Delta v = (0,0)$ , a run length of zero is coded. For $\Delta v \neq (0,0)$ , variable length coding is applied with their code lengths shown in Figure 26. + +The coding of $\Delta v$ is carried out for the 28 vectors of the 2nd to the 29th blocks. + +The last run of $\Delta v = (0,0)$ may not be transmitted since VDN states the total bits of VD. + +![A grid diagram showing word lengths for motion vector prediction errors. The horizontal axis is labeled ΔVx and ranges from -16 to 15. The vertical axis is labeled ΔVy and ranges from -8 to 7. The grid contains numbers representing bit lengths. Most cells contain '13', with some containing '11', '9', '7', '6', '5', '4', '3', '15', or '1'. The '15' values are in the outer corners, and the '1' value is at the origin (0,0).](060e30970c1a5549f43dd504aa8aaed0_img.jpg) + +A grid diagram showing word lengths for motion vector prediction errors. The horizontal axis is labeled ΔVx and ranges from -16 to 15. The vertical axis is labeled ΔVy and ranges from -8 to 7. The grid contains numbers representing bit lengths. Most cells contain '13', with some containing '11', '9', '7', '6', '5', '4', '3', '15', or '1'. The '15' values are in the outer corners, and the '1' value is at the origin (0,0). + +T1514020-93/d21 + +FIGURE 26/H.120 +Word length for motion vector prediction errors + +##### 3.6.5.4.4 Code assignments + +The codes are assigned as shown in Table 10, where the maximum code length is 15. The variable length codes consist of 541 codes, or 512 codes for $\Delta v$ , 28 codes for run length and one TRANS code for transition of subsampling ON/OFF. + +TABLE 10/H.120 + +###### Variable length code and run length code for motion vector data + +| $\Delta Vx$ | $\Delta Vy$ | Code length | Code word | | | Number of codes | +|-------------|--------------------------|-------------|---------------|-------------------|----------------------------------------|-----------------| +| $\pm 1$ | 0 | 4 | 0 0 1 | Sx | | 2 | +| $\pm 1$ | $\pm 1$ | 5 | 1 1 | 1 SxSy | | 8 | +| 0 | $\pm 1$ | 5 | 1 1 | 0 1 Sy | | | +| $\pm 2$ | 0 | 5 | 1 1 | 0 0 Sx | | | +| 0 | $\pm 2$ | 6 | 1 0 1 1 | 1 Sy | | 4 | +| $\pm 3$ | 0 | 6 | 1 0 1 1 | 0 Sx | | | +| $\pm 1$ | $\pm 2$ | 7 | 1 0 0 | 1 1 SxSy | | 12 | +| $\pm 2$ | $\pm 1$ | 7 | 1 0 0 | 1 0 SxSy | | | +| 0 | $\pm 3$ | 7 | 1 0 0 | 0 1 1 Sy | | | +| $\pm 4$ | 0 | 7 | 1 0 0 | 0 1 0 Sx | | | +| $\pm 3$ | $\pm 1$ | 9 | 1 0 1 0 | 1 1 1 SxSy | | 30 | +| $\pm 1$ | $\pm 3$ | 9 | 1 0 1 0 | 1 1 0 SxSy | | | +| $\pm 2$ | $\pm 2$ | 9 | 1 0 1 0 | 1 0 1 SxSy | | | +| $\pm 3$ | $\pm 2$ | 9 | 1 0 1 0 | 1 0 0 SxSy | | | +| $\pm 4$ | $\pm 1$ | 9 | 1 0 1 0 | 0 1 1 SxSy | | | +| $\pm 4$ | $\pm 2$ | 9 | 1 0 1 0 | 0 1 0 SxSy | | | +| $\pm 5$ | 0 | 9 | 1 0 1 0 | 0 0 1 1 Sx | | | +| $\pm 6$ | 0 | 9 | 1 0 1 0 | 0 0 1 0 Sx | | | +| 0 | $\pm 4$ | 9 | 1 0 1 0 | 0 0 0 1 Sy | | | +| -8 to 7 | -5 to +5 (see Figure 26) | 11 | 1 0 0 0 0 1 | X X X X Sy | [X] = $\Delta Vx$ | 32 | +| -16 to 15 | -6 to +6 (see Figure 26) | 13 | 0 1 0 0 0 0 1 | X X X X X Sy | [X] = $\Delta Vx$ | 64 | +| -16 to 15 | -8 to +7 (see Figure 26) | 15 | 1 0 0 0 0 0 | X X X X X Y Y Y Y | [X] = $\Delta Vx$
[Y] = $\Delta Vy$ | 359 | + +| RL | Code length | Code word | | Number of codes | +|----------|-------------|-------------------|-----------------|-----------------| +| 1 | 3 | 0 0 0 | | 1 | +| 2 | 4 | 0 1 1 1 | | 1 | +| 3 to 6 | 6 | 0 1 1 0 X X | X X = 6 - RL | 4 | +| 7 to 12 | 7 | 0 1 0 1 X X X | X X X = 12 - RL | 6 | +| 13 to 20 | 8 | 0 1 0 0 1 X X X | X X X = 20 - RL | 8 | +| 21 to 28 | 9 | 0 1 0 0 0 1 X X X | X X X = 28 - RL | 8 | +| TRANS | 6 | 0 1 0 1 1 1 | | 1 | + +###### NOTES + +- Sx and Sy denote signs: $S_i = 0$ for positive, $S_i = 1$ for negative. +- XX..X and YY..Y are expressed in two's complement form (MSB first). + +##### 3.6.5.4.5 Transition code for subsampling (TRANS) + +The code TRANS indicates transition between ON and OFF for subsampling (SBS). For the first block in a block-line, SBS is set to OFF. Subsampling is then set to ON at the block just after the first TRANS code is inserted, and returned to OFF at the block just after the second TRANS code is inserted. The same sequence follows on. The TRANS code is expressed as a 6-bit word. When SBS = 0, transition code is disregarded in the decoder. + +##### 3.6.5.4.6 Dummy code insertion + +When a vector data (VD) for a block-line does not have exactly 8 multiple bits, a dummy code consisting of 1 to 7 bits is inserted at the tail of the vector data. + +The dummy code has 1 as the head, 0s as the body and 1 as the tail (see Table 11). + +TABLE 11/H.120 + +| Number of dummy bits | Dummy code | +|----------------------|------------| +| 1 | 1 | +| 2 | 11 | +| 3 | 101 | +| 4 | 1001 | +| 5 | 10001 | +| 6 | 100001 | +| 7 | 1000001 | + +##### 3.6.5.4.7 Code transition rule + +The rule is indicated in Figure 27 with a motion vector coding example given in Annex F. + +![Diagram illustrating the code transition rule for motion vector data and normal/subsampling mode change. It shows two states, NRM and SBS, connected by TRANS [010111] codes. The diagram includes a 'Block-line start' arrow pointing to the NRM state, and self-loops for each state labeled '[V] or [RL]'. The text 'T1514030-93/d22' is present in the bottom right.](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +``` + +graph LR + Start(( )) -- "Block-line start" --> NRM + NRM -- "TRANS [010111]" --> SBS + SBS -- "TRANS [010111]" --> NRM + NRM -- "[V] or [RL]" --> NRM + SBS -- "[V] or [RL]" --> SBS + style Start fill:none,stroke:none + +``` + +Diagram illustrating the code transition rule for motion vector data and normal/subsampling mode change. It shows two states, NRM and SBS, connected by TRANS [010111] codes. The diagram includes a 'Block-line start' arrow pointing to the NRM state, and self-loops for each state labeled '[V] or [RL]'. The text 'T1514030-93/d22' is present in the bottom right. + +NOTE – The same motion vector coding method is applied for both NRM and SBS modes. + +FIGURE 27/H.120 +Code transition rule for motion vector data +and normal/subsampling mode change + +#### 3.6.5.5 Block-line skipping + +If block-lines continue, in which all the prediction error $e$ , data and motion vector $v$ data are 0, and whose line mode data (QC1, QC2, IFM, FRP, SL1, SL2) are identical, their number is run-length coded with natural binary code as skipped block-lines. A run ends when it encounters FS or a block-line with new line mode data or some $e \neq 0$ or some $v \neq 0$ . A run also ends when variable length code $V_0$ appears due to underflow prevention. + +### 3.6.6 Buffer memory + +#### 3.6.6.1 Receiving buffer control + +The staying period of FS in the transmission buffer is counted with a 1/16 input video line frequency clock and transmitted to the decoder as BC command. The staying period is represented in eight bit binary code. Similarly, the staying period in the receiving buffer is counted and the operation of the receiving buffer is so controlled as to make the total delay time caused by the two buffer memories constant. + +NOTE – This control method is applicable even when the read out speed for the transmission buffer varies. + +#### 3.6.6.2 Memory size + +Transmission buffer memory size $B_S$ is defined as 180 kbits, while receiving buffer memory size $B_R$ should be more than 220 kbits considering the variation of the transmission buffer read out speed. + +NOTE – The delay time due to the transmission and receiving buffer memories becomes about 165 ms for $B_S = 180$ kbits and $B_R = 220$ kbits. + +#### 3.6.6.3 Underflow prevention + +If the occupancy of the transmission buffer decreases to a threshold, the run length coding for the prediction error is prohibited and variable length code $V_0$ is used. + +#### 3.6.6.4 Overflow prevention + +If the occupancy of the transmission buffer increases to another threshold, stop mode for setting forcibly all the prediction error and motion vector data to 0 is applied. + +## 3.7 Audio coding + +An audio channel using 64 kbit/s is included. The audio coding algorithm complies with Recommendation G.722. + +Since video coding and decoding introduces a significant delay as described in 3.3.11, the encoded audio signal should be delayed by the corresponding time in the coder and decoder to obtain the proper synchronization between video and audio at the decoder. The delay inserted in the audio coder should be the sum of a half of the buffer memory delay and other video coding process delay, while the delay inserted in the audio decoder should be the sum of a half of the buffer delay and other video decoding process delay. + +## 3.8 Transmission coding + +### 3.8.1 General + +The transmission coder assembles the video, audio, optional data and codec-to-codec information channels into a 1544 kbit/s digital stream. With all serialized data, the most significant digit leads. + +### 3.8.2 Encryption + +Video and audio signals can be independently encrypted on an optional basis. Their algorithms are under study. Keys and other control information can be transmitted through the message channel provided in the codec-to-codec information channel. + +### 3.8.3 Error correction + +An encoded (and encrypted) video signal is forward error corrected by a (255, 239) two-error correcting BCH code with the following polynomial generator: + +$$g(x) = (1 + x^2 + x^3 + x^4 + x^8) (1 + x + x^2 + x^4 + x^5 + x^6 + x^8)$$ + +One framing bit is added to each 255 bit error correction frame, and 16 such frames are assembled into one large frame as shown in Figure 28. The frame alignment pattern is 0001101y (y: for future multiframe alignment signal use). The other 8 bits are used for controlling purposes, whose protocol is under study. + +To correct a burst error of up to 32 bits, 16 phase interleaving is employed. The bit allocation rule is also indicated in Figure 28. Note that framing bits are excluded from interleaving. + +![Diagram illustrating error correction frames and interleaving. It shows 16 frames (Frame No. 1, 2, 3, 4, 14, 15, 16) with 255 bits each. The first frame has a framing bit S1. The second frame has a framing bit S2. The third frame has a framing bit S3. The fourth frame has a framing bit S4. The fourteenth frame has a framing bit S15. The fifteenth frame has a framing bit S16. The sixteenth frame has a framing bit S16. The diagram shows the interleaving of bits from these frames. The legend indicates: S1 S3 S5 S7 S9 S11 S13 = 0001101 (Multiframe alignment signal), S15 (Multiframe alignment signal), and S2 S4 S6 ... S16 (Control information).](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +Frame No. 1 2 3 4 14 15 16 + +S1 S2 S3 255 S4 S15 S16 + +S1 S2 S3 S4 S15 S16 + +T1514040-93/d23 + +S1 S3 S5 S7 S9 S11 S13 = 0001101 + S15 Multiframe alignment signal + S2 S4 S6 ... S16 Control information + +Diagram illustrating error correction frames and interleaving. It shows 16 frames (Frame No. 1, 2, 3, 4, 14, 15, 16) with 255 bits each. The first frame has a framing bit S1. The second frame has a framing bit S2. The third frame has a framing bit S3. The fourth frame has a framing bit S4. The fourteenth frame has a framing bit S15. The fifteenth frame has a framing bit S16. The sixteenth frame has a framing bit S16. The diagram shows the interleaving of bits from these frames. The legend indicates: S1 S3 S5 S7 S9 S11 S13 = 0001101 (Multiframe alignment signal), S15 (Multiframe alignment signal), and S2 S4 S6 ... S16 (Control information). + +FIGURE 28/H.120 +**Error correction frames and interleaving** + +### 3.8.4 Scrambling + +An error corrected video signal is scrambled with an 8-stage pseudo-random pulse generator to reduce stuffing required by the network restrictions. At each error correction frame bit, the scrambler is reset. The polynomial generator and the scrambled output pattern following the reset pulse for the input of all zeros are as follows: + +$$1 + x^4 + x^5 + x^6 + x^8,$$ + +$$1111010011 \dots 1001111011.$$ + +### 3.8.5 Frame structure and stuffing + +Clause 3/H.130 is applied. + +# **Annex A** (referring to clause 1 of Recommendation H.120) + +## **Graphics option – 625 line** + +(This annex forms an integral part of this Recommendation) + +## **A.1 Introduction** + +In order to comply with the requirements of Recommendation H.100, an optional graphics mode may be provided giving improved definition at the expense of ability to convey movement. Two suitable arrangements are as follows: + +## **A.2 Graphics codec for videoconferencing graphics – Mode 1** + +### **A.2.1 Facilities** + +The graphics mode provides, for still pictures, a capability of full 625-line luminance definition and colour definition which is better than that of the PAL and SECAM systems. It provides a limited capability for conveying movement, sufficient to permit pointing at items under discussion on the display. When the codec is in or adjacent to, the conference room, an alternative frozen-frame mode enables the face-to-face picture frozen for about 1.5 s while the graphics picture is being transmitted, to restart while the frozen graphics picture was displayed on another monitor. + +The definition in the graphics mode is sufficient to permit good reproduction of one-half an A4 page of typescript. + +### **A.2.2 Coding** + +The luminance and colour-difference signals are sampled at 12.5 MHz and 12.5/3 MHz respectively, the sampling frequency being locked to the television line-scanning frequency. + +The samples are converted to PCM with 6 bits/sample. The luminance signal has a two-level half-sampling-frequency dither signal added to it which reduces the quantization distortion to approximately that of 7-bit coding. + +Only the active picture area is sampled. Thus, there are 639 luminance samples along the line and two fields of 288 lines. + +One colour-difference sample occurs every three luminance samples. Two of the 6 bits from a colour-difference sample are added to each of the three associated luminance samples, giving three 8-bit words for three luminance samples plus one colour-difference sample. + +The $(E'_R - E'_Y)$ component is associated with the first, third, fifth, etc., active lines of Field No. 1, with the $(E'_B - E'_Y)$ component on the intervening lines, the pattern being reversed in Field No. 2. + +The colour-difference samples are delayed with respect to the luminance samples to which they are attached, so that when decoded, they are coincident with the luminance output. The centre of the first colour-difference element on a line is co-sited with the second luminance element. Similarly, the centre of the 213th colour-difference element is co-sited with the 638th luminance element. + +The luminance signal is amplitude-limited so that its PCM values are confined to the range: + +| | | +|----------------------------------------------------|-------------------| +| Black level..... | 000000 | +| White level (700 mV):
transmission between..... | 100111 and 111000 | +| Maximum level (750 mV)..... | 111011 | + +The colour-difference signals are limited to the range: 000000 to 111111 (0 to 63) with black level at 100000 (32). The 100/0/75/0 colour bar signal (see CCIR Recommendation 471 for explanation of nomenclature) fills the range: 000100 to 111100 (4 to 60). Prior to transmission, the colour difference codes are converted to the two's complement form by inversion of the most significant bit. This gives the range: 100000 to 011111 (-32 to 31) with the black level at 000000. The colour bar signal then occupies the range: 100100 to 011100 (-28 to 28). + +### A.2.3 Transmission and synchronization + +#### A.2.3.1 General + +The PCM words, formed as above, are transmitted to give a continuous update of the picture store in the receiver. The update pattern, which has been chosen to give smooth transitions on a changing picture, transmits every 19th luminance sample (with associated colour-difference data). The sequence of every 19th sample continues from one line to the next, as if the 639 elements in one active line are followed immediately (that is, without a gap for line blanking) by the 639 active elements in the next line. The use of this continuous sequence of samples makes line addressing unnecessary. A field synchronization code, followed by the address (in the range of 0 to 18) of the first luminance sample of the first active line, provides all the necessary synchronizing information. + +The field synchronization code comprises 8 bytes of the form 11110011 or 11111100, which are invalid PCM values. The order of the last two pairs of bits, 0011 or 1100, in each of the first seven bytes, representing 0 and 1 respectively, signals the address of the first element of the field. In the 8th byte, 1100 signals a first field (starting line 23) and 0011 a second field (starting line 336). + +The sequence in which the fields are transmitted by the address of the first luminance sample of the first line need not be specified because the decoder reconstructs the picture from the received addresses. A sequence which has been found satisfactory, giving no patterns with moving objects (e.g. a pointing finger), is as follows with the number in parentheses indicating a first or second field: + +1 (2), 13 (1), 6 (2), 18 (1), 3 (2), 10 (1), 15 (2), 4 (1), 0 (2), 8 (1), 12 (2), 5 (1), 14 (2), 9 (1), 17 (2), 2 (1), 11 (2), 7 (1), 16 (2), + +followed by: + +1 (1), 13 (2), 6 (1), . . . in the same sequence as above, but with the field number interchanged. + +After 38 fields, the complete picture has been replenished and the sequence repeats itself from the beginning. + +#### A.2.3.2 Data structure + +In each transmitted field, the data comprises 8 field synchronization bytes followed by 9685 or 9686 bytes of picture data (the total number of picture elements per field, $639 \times 288$ , is not divisible by 19). Fields where the address of the first element is in the range 0 to 16 have 9686 transmitted bytes, while those with the first element address 17 or 18, have 9685 transmitted bytes. + +Each byte of picture data comprises 6 bits of luminance data plus 2 bits of colour-difference data. The most significant bits of the colour-difference sample are transmitted first and the pairs of bits of the colour-difference data are placed in the least significant positions of the picture data byte. The data is arranged so that the luminance sample for the first picture element of a line carries with it the two most significant bits of the 19th colour-difference element belonging to the following line. The centre bits and the least significant bits of this colour-difference element are attached to the 20th and 39th along-the-line addresses respectively, these being the next two transmitted samples. + +There are no colour-difference data transmitted for the first line of the picture and, on the second line, the first 18 colour-difference elements of the second line cannot be reconstructed at the decoder. + +#### A.2.3.3 Data output + +The graphics data are generated at a nominal rate of 3.74 Mbit/s and are transmitted via a buffer store whose capacity is in excess of 160 kbits. The output to the transmission channel is at less than 2 Mbit/s, the actual value depending on the number of time slots allocated to video. When the buffer level at the end of a field exceeds 160 kbits, the sampling is suspended for two complete fields to allow the buffer to empty. + +If the level is then still in excess of 160 kbits, sampling is suspended for a further two fields. + +The octet structure of the output data must be aligned with the time slot structure of the primary rate interface. + +The approximate transmission time for a complete picture is therefore in the range of 1.6 to 4.6 s. + +### A.2.4 Decoder + +The received data are associated with addresses derived from the field synchronization code and assembled in a picture store having $639 \times 576$ addressable positions with 8-bit capacity. The data are stored in the multiplexed form (luminance and colour-difference) used for transmission. The contents of this store are read out sequentially, the luminance and colour-difference components demultiplexed, and the colour-difference components line-interpolated to give the $(E'_R - E'_Y)$ and $(E'_B - E'_Y)$ components simultaneously and coincident with their associated luminance. + +## A.3 Graphics codec for videoconferencing-graphics – Mode 2 + +### A.3.1 Facilities + +The graphics mode provides, for still pictures, the capability of full 625-line luminance and colour definition. It allows transmission for still pictures with studio quality, defined in CCIR Recommendation 601. The graphics codec can be operated in two modes. In the single shot mode, the face-to-face picture is frozen for about 4 s, while the graphics picture is being transmitted, to restart while the graphics picture is displayed on another monitor. In the continuous mode, the face-to-face picture is frozen during the graphics presentation. The graphics picture is continuously transmitted in order to reproduce slow movement, e.g. for blackboard presentations. When the graphics picture has stabilized or when the presentation is finished, the graphics picture is frozen and the face-to-face picture is restarted. + +The definition of the graphics mode 2 is better than that of the PAL, SECAM and NTSC systems and is sufficient to permit good reproduction of one-half of an A4 page typescript. + +### A.3.2 Coding + +The luminance signal ( $E'_Y$ ) and colour-difference signals ( $E'_R - E'_Y$ , $E'_B - E'_Y$ ) are sampled at 13.5 MHz and 6.75 MHz respectively, according to the encoding parameters of digital television for studios given in CCIR Recommendation 601. The sampling frequencies are related in the ratio 4 : 2 : 2. The sampling structure is orthogonal, line, field and picture repetitive. The samples of the colour-difference signals are co-sited with the first, third, fifth, etc. luminance sample in each line. All samples are uniformly quantized PCM-values with 8 bits/sample. + +Only the active picture area is sampled. There are 720 luminance samples along the line and two fields of 288 lines. + +The luminance signal is amplitude-limited so that its PCM values are confined to the range: + +Black level: 16; + +Peak level: 235. + +Each colour-difference signal exhibits 225 quantization levels in the centre part of the quantization scale with zero signal corresponding to level 128. + +Further details are given in CCIR Recommendation 601. + +### A.3.3 Transmission and synchronization + +#### A.3.3.1 General + +Luminance and colour-difference samples of each line are arranged as sets for four samples: + +$$\left[ (E'_B - E'_Y)_n, (E'_Y)_n, (E'_R - E'_Y)_n, (E'_Y)_{n+1} \right]$$ + +where + +$n = 0, 2, 4, 6, \dots, 718$ . Each set consists of four words with 8 bit word length. There are 360 sets in each line of the picture. + +The PCM sets are transmitted to give a continuous update of the picture store in the receiver. The update pattern which has been chosen transmits every 19th set. The sequence of every 19th set continues from one line to the next, as if the 360 sets in one active line are followed immediately (that is, without a gap for line blanking) by the 360 sets of the next line. The use of this continuous sequence of samples makes line addressing unnecessary. A field synchronization code, followed by the address of the first set of the first active line, provides all the necessary synchronizing information. The address is in the range 0 to 18. + +The field synchronization code comprises eight bytes of the form 11110011 or 11111100. These two codewords are not allowed for the coded video signal. The order of the last two pairs of bits, 0011 or 1100, in each of the first seven bytes, representing 0 and 1 respectively, signals the address of the first set of the field. In the 8th byte, 1100 signals a first field (starting line 23) and 0011 a second field (starting line 336). + +The sequence in which the fields are transmitted is defined by the address of the first set of the first line and need not be specified, because the decoder reconstructs the picture from received addresses. + +#### A.3.3.2 Data structure + +In each transmitted field, the data comprises 8 field synchronization bytes followed by the sets of picture data. In each set, $(E'_B - E'_Y)_n$ is transmitted first, followed by $(E'_Y)_n$ , $(E'_R - E'_Y)_n$ and $(E'_Y)_{n+1}$ . For transmission, a parallel-to-serial conversion takes place at the encoder. The most significant bits in the transmitted bit stream are leading. + +#### A.3.3.3 Data output + +The output bit-rate to the transmission channel is at less than 2 Mbit/s, the actual value depending on the number of time slots allocated to video. + +The octet structure of the output data must be aligned with the time slot structure of the primary rate interface. + +The approximate transmission time for a complete picture is 4 s. + +### A.3.4 Decoder + +The received data are associated with addresses derived from the field synchronization code and assembled in a picture store having a capacity of 6.6355 Mbits. The contents of this store are read out sequentially. + +### A.3.5 Interface + +#### A.3.5.1 Video interface + +- i) *Analogue interface* – An RGB-interface rather than a composite signal interface (PAL, SECAM) is recommended to maintain a high quality video signal. +- ii) *Digital interface* – The structure of sets defined in A.3.3.2 allows for definition of a digital interface according to CCIR Recommendation 656 for $E'_Y$ , $E'_R - E'_Y$ and $E'_B - E'_Y$ . + +#### A.3.5.2 Digital interface for transmission signal + +The graphics mode may be internal or external to the face-to-face codec. An external device may have a digital interface according to Recommendations X.21 and V.11 (leased circuits). The picture data must be delayed at least 40 ms with respect to the control signal C specified in Recommendation X.21. + +### A.3.6 Signalling of graphics mode 2 + +The graphics mode 2 is signalled in the codec-to-codec information with bit 3.1.5 set to 1. For nomenclature of the bits, see Recommendation H.130. + +### A.3.7 Compatibility with graphics mode 1 + +In the graphics encoder and decoder, additional means are incorporated to make graphics mode 2 compatible with mode 1. They are signalled by setting bit 3.1.0 to 1 in the codec-to-codec information. If bit 3.1.5 of the codec-to-codec information is received set to 0 and bit 3.1.0 is received set to 1, then the graphics codec automatically switches into mode 1. + +# **Annex B** (referring to clause 1 of Recommendation H.120) + +## **Encryption option – 625 line** + +Under study. + +# **Annex C** (referring to clause 2 of Recommendation H.120) + +## **Graphics option – 525 line** + +(This annex forms an integral part of this Recommendation) + +## **C.1 Introduction** + +The 525-line version of this graphics mode is very similar to the 625-line version for mode 1 specified in Annex A. It uses the same systematic replenishment technique and since the receiver is totally asynchronous from the transmitter, no adjustment for the differing picture rates is necessary. Instead of any form of standards conversion, the interworking between the 525-line and 625-line versions is provided by creating a small change in picture size. In 525 to 525-line transmission, the displayed picture size is the same as produced by the transmitting camera. In 525 to 625-line transmission, the displayed picture is reduced in size and is surrounded by a small black border (about 8%). In 625 to 525-line transmission, the displayed picture is expanded (equivalent to an overscan of about 8.5% in each border) so that a small amount of the transmitted picture area is not displayed. + +Most of the details of this graphics mode are identical to those of the 625-line version for mode 1 in Annex A, so that only the difference need be specified in this Annex. + +## **C.2 Facilities** + +The facilities are essentially the same as for the 625-line version. + +## **C.3 Coding** + +The luminance and colour-difference sampling frequencies are 10.08 and 10.08/3 MHz respectively, the sampling frequency being locked to the television line-scanning frequency. + +The arrangements for PCM coding are identical with the 625-line version but an area greater than the active picture area is sampled. There are 639 samples per line, the same number as for the 625-line version; 494 or 516 lines per picture are sampled. When a 525-line signal is being sampled at 10.08 MHz, only about 537 samples are required for the active line. The excess 102 samples, set to black level, are placed evenly on each side of the active line samples. + +For 525-line transmission, samples from the first active line of Field No. 1 (line 14) form the $(E'_B - E'_Y)$ component, while those from the first active line of Field No. 2 (line 277) form the $(E'_R - E'_Y)$ component. For 625-line transmission, samples from the first active line of Field No. 1 (line 9) form the $(E'_R - E'_Y)$ component and those from the first active line of Field No. 2 (line 272) form the $(E'_B - E'_Y)$ component. + +## C.4 Transmission and synchronization + +### C.4.1 General + +The systematic replenishment algorithm based on the consecutive transmission of every 19th sample is also used in the 525-line version. However, since the samples extend over almost the complete line period, the divide-by-nineteen clock is suspended for only one luminance sample period during line-blanking. During transmission to a 625-line decoder, 5 additional lines per field are included before the picture area starts together with 6 additional lines per field after the end of the picture area, increasing the lines per field from 247 to 258. The luminance and colour-difference values on the extra lines are set to black level. Also, the divide-by-nineteen clock is changed to divide-by-five while samples are being selected from the added lines. This deceives the 625-line decoder into believing that there are 19 lines (per field) of black above the picture and 22 lines below the picture, making the total number of lines per field equal to 288, the same value as in Annex A. + +The field synchronization code and the method of identifying fields are identical to those described in Annex A (except that the first line of Field No. 1 may be either line 14 or 9 and that of Field No. 2 either line 277 or 272). + +### C.4.2 Data structure + +In 525 to 525-line transmission, each transmitted field comprises 8 field-synchronization bytes followed by 8307 bytes of picture data. + +In 525 to 625-line transmission, each transmitted field comprises 8 field-synchronization bytes followed by 9685 or 9686 bytes of picture data, exactly the same as in the 625-line version in Annex A. In the 525-line coder the picture data are assembled from: + +| | | +|-------------------------------------------------------|-------------| +| 5 lines of 639 samples, every 5th sample . . . . . | 639 bytes; | +| 247 lines of 639 samples, every 19th sample . . . . . | 8207 bytes; | +| 6 lines of 639 samples, every 5th sample . . . . . | 766 bytes. | + +The number of bytes required from the 6 lines at the bottom of the picture is 739 or 740. The excess bytes (all at black level), arising from non-integral results of division, are discarded. + +Other details of the data structure are as in Annex A. + +### C.4.3 Data output + +The graphics data are generated at a nominal rate of about 4 Mbit/s and fed into buffer store. The output from the buffer is at less than 2 Mbit/s (depending on the number of time slots allocated to video). When the buffer level at the end of a field exceeds 160 kbits, the sampling is suspended for two complete fields to allow the buffer to empty. If the level is then still in excess of 160 kbits, sampling is suspended for a further two fields. + +The octet structure of the output data must be aligned with the time slot structure of the primary rate interface. + +The resulting transmission time for a complete picture is of the order of 1.7 to 3 s. + +## C.5 Decoder + +The received data are associated with addresses derived from the field synchronization code and assembled in a picture store having $639 \times 494$ addressable positions with 8-bit capacity. The data are stored in the multiplexed form (luminance and colour-difference) used for transmission. The contents of the store are read out sequentially, the luminance and colour-difference components line-interpolated to give the $(E'_R - E'_Y)$ and $(E'_B - E'_Y)$ components simultaneously and coincident with the associated luminance. + +The length of the line in the picture store is 639 elements; for a 525-line picture sampled at 10.08 MHz, the active line requires only 537 elements. When television blanking is applied to the output signals, the 102 extra elements are suppressed and the standard 525-line signal results. + +When receiving a signal from a 625-line terminal, 639 elements per line are received and stored. However, the first 19 active lines and the last 22 active lines of each field of the 625-line signal are not read into the store and are discarded. This, together with the effect of the line blanking on the horizontal output from the store, provides a 525-line display corresponding to the 625-line input picture after a border about 8% wide has been trimmed from all four edges. + +# **Annex D** + +(referring to clause 2 of Recommendation H.120) + +## **Encryption option – 525 line** + +Under study. + +# **Annex E** + +(referring to clause 3 of Recommendation H.120) + +## **Colour decoding and coding filters** + +(This annex forms an integral part of this Recommendation) + +## **E.1 Configuration** + +See Figure E.1. + +a) Digital colour separation circuit + +![Block diagram of a digital colour separation circuit. An NTSC signal at 4 f_sc enters from the left. One path goes through a 1H line delay. The output of the delay is subtracted from the original NTSC signal. The result is filtered by a Y-LPF and then a Y-SCT (4 f_sc) to produce the Y signal at 2 f_sc. Another path from the subtraction point goes through a C-BPF. The output of the C-BPF is multiplied by ±1 and then filtered by a C-LPF (2 f_sc) to produce the C1 signal at 1/3 f_sc. Another path from the C-BPF is multiplied by ±1 and then filtered by a C-LPF (2 f_sc) to produce the C2 signal at 1/3 f_sc.](9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg) + +Block diagram of a digital colour separation circuit. An NTSC signal at 4 f\_sc enters from the left. One path goes through a 1H line delay. The output of the delay is subtracted from the original NTSC signal. The result is filtered by a Y-LPF and then a Y-SCT (4 f\_sc) to produce the Y signal at 2 f\_sc. Another path from the subtraction point goes through a C-BPF. The output of the C-BPF is multiplied by ±1 and then filtered by a C-LPF (2 f\_sc) to produce the C1 signal at 1/3 f\_sc. Another path from the C-BPF is multiplied by ±1 and then filtered by a C-LPF (2 f\_sc) to produce the C2 signal at 1/3 f\_sc. + +b) Digital colour composition circuit + +![Block diagram of a digital colour composition circuit. The Y signal at 2 f_sc is filtered by a Y-IPF to produce a signal at 4 f_sc. The C1 signal at 1/3 f_sc is filtered by a C-IPF to produce a signal at 2 f_sc, which is then multiplied by ±1. The C2 signal at 1/3 f_sc is filtered by a C-IPF to produce a signal at 2 f_sc, which is then multiplied by ±1. The outputs of the Y-IPF and the multipliers are summed to produce the final NTSC signal at 4 f_sc.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +Block diagram of a digital colour composition circuit. The Y signal at 2 f\_sc is filtered by a Y-IPF to produce a signal at 4 f\_sc. The C1 signal at 1/3 f\_sc is filtered by a C-IPF to produce a signal at 2 f\_sc, which is then multiplied by ±1. The C2 signal at 1/3 f\_sc is filtered by a C-IPF to produce a signal at 2 f\_sc, which is then multiplied by ±1. The outputs of the Y-IPF and the multipliers are summed to produce the final NTSC signal at 4 f\_sc. + +| | | +|----------|-----------------------------------| +| H | Line delay | +| Y-LPF | Low pass filter for Y signal | +| Y-SCT | Subcarrier trapper | +| C-BPF | Band pass filter for C signal | +| C-LPF | Low pass filter for C signal | +| $f_{sc}$ | Colour subcarrier frequency | +| Y-IPF | Interpolation filter for Y signal | +| C-IPF | Interpolation filter for C signal | + +FIGURE E.1/H.120 + +## E.2 Basic filter characteristics + +See Table E.1. + +TABLE E.1/H.120 + +| Filter | Transfer function H(z) | +|--------|----------------------------------------------------------------------------------------------------------------| +| C-BPF | $(-Z^{-2} + 2 - Z^2)/4$ | +| Y-LPF | $(-3Z^{-3} + 19Z^{-1} + 32 + 19Z - 3Z^3)/64$ | +| Y-SCT | $(Z^{-5} - 3Z^{-3} + 10Z^{-1} + 10Z - 3Z^3 + Z^5)/16$ | +| C-LPF | $(Z^{-4} + 3Z^{-2} + 4 + 3Z^2 + Z^4)/12$ | +| Y-IPF | $(-3Z^{-3} + 19Z^{-1} + 32 + 19Z - 3Z^3)/64$ | +| C-IPF | $(Z^{-2} + 1 + Z^2)(Z^{-1} + 2 + Z)(-Z^{-8} - 2Z^{-6} + 2Z^{-4} + 6Z^{-2} + 6 + 6Z^2 + 2Z^4 - 2Z^6 - Z^8)/192$ | + +## E.3 Advanced filter characteristics + +See Table E.2. + +TABLE E.2/H.120 + +| Filter | Transfer function H(z) | +|--------|----------------------------------------------------------------------------------------------------------------| +| C-BPF | $(Z^{-8} - 9Z^{-6} + 17Z^{-4} - 23Z^{-2} + 28 - 23Z^2 + 17Z^4 - 9Z^6 + Z^8)/128$ | +| Y-LPF | $(-Z^{-7} + 4Z^{-5} - 10Z^{-3} + 39Z^{-1} + 64 + 39Z - 10Z^3 + 4Z^5 - Z^7)/128$ | +| Y-SCT | $(Z^{-5} - 3Z^{-3} + 10Z^{-1} + 10Z - 3Z^3 + Z^5)/16$ | +| C-LPF | $(Z^{-4} + 3Z^{-2} + 4 + 3Z^2 + Z^4)/12$ | +| Y-IPF | $(-Z^{-7} + 4Z^{-5} - 10Z^{-3} + 39Z^{-1} + 64 + 39Z - 10Z^3 + 4Z^5 - Z^7)/128$ | +| C-IPF | $(Z^{-2} + 1 + Z^2)(Z^{-1} + 2 + Z)(-Z^{-8} - 2Z^{-6} + 2Z^{-4} + 6Z^{-2} + 6 + 6Z^2 + 2Z^4 - 2Z^6 - Z^8)/192$ | + +# **Annex F** (referring to clause 3 of Recommendation H.120) + +## **An example of coding control sequence** (This annex forms an integral part of this Recommendation) + +![A graph showing the relationship between Buffer memory occupancy (T0 to T8) and Quantizing characteristics (Q0 to Q3) for different Coding modes (Normal, Field repetition, Field repetition and subsampling, Stop).](5000e9028ee2990f6242b2c0a952010d_img.jpg) + +The figure is a step-like graph illustrating the relationship between buffer memory occupancy and quantizing characteristics for different coding modes. The x-axis represents 'Buffer memory occupancy' with markers from 0 to T8. The y-axis on the right represents 'Quantizing characteristics' with markers Q0, Q1, Q2, and Q3. The y-axis on the left lists 'Coding modes': Normal, Field repetition, Field repetition and subsampling, and Stop. The graph shows that as buffer occupancy increases, the quantizing characteristic generally decreases (from Q0 to Q3). The 'Normal' mode starts at Q0 and steps down to Q3 at T5. The 'Field repetition' mode starts at T2 and steps down to Q3 at T6. The 'Field repetition and subsampling' mode starts at T6 and steps down to Q3 at T7. The 'Stop' mode is indicated by a vertical line at T8. + +| Coding mode | Start | End | Quantizing characteristic | +|----------------------------------|-------|-----|---------------------------| +| Normal | 0 | T1 | Q 0 | +| Normal | T1 | T2 | Q 1 | +| Normal | T2 | T3 | Q 2 | +| Normal | T3 | T4 | Q 2 | +| Normal | T4 | T5 | Q 3 | +| Normal | T5 | T8 | Q 3 | +| Field repetition | T2 | T3 | Q 1 | +| Field repetition | T3 | T4 | Q 2 | +| Field repetition | T4 | T5 | Q 3 | +| Field repetition | T5 | T6 | Q 3 | +| Field repetition | T6 | T7 | Q 3 | +| Field repetition | T7 | T8 | Q 3 | +| Field repetition and subsampling | T6 | T7 | Q 2 | +| Field repetition and subsampling | T7 | T8 | Q 3 | +| Stop | T8 | T8 | Q 3 | + +A graph showing the relationship between Buffer memory occupancy (T0 to T8) and Quantizing characteristics (Q0 to Q3) for different Coding modes (Normal, Field repetition, Field repetition and subsampling, Stop). + +FIGURE F.1/H.120 + +# **Annex G** (referring to clause 3 of Recommendation H.120) + +## **Examples of entropy coding** + +(This annex forms an integral part of this Recommendation) + +![A bar chart showing the quantization level number of prediction error 'e' over time. The y-axis is labeled 'e (Quantization level number)' and the x-axis is labeled 'Time'. The chart displays several bars of varying heights. Below the x-axis, there are labels for different regions and states: R2, V5, F6, F0, V0, V1, F2, V1, V6, F2, V1, R3, V1, V0, V2, R67, V5, F0, and R. A break in the x-axis is indicated by '//' between R67 and V5. A small code 'T1514070-93/d26' is present at the bottom right of the chart area.](e0113695dbf148bf5ec34354e544414b_img.jpg) + +The figure is a bar chart representing the quantization level number of a prediction error 'e' over a series of time intervals. The vertical axis is labeled 'e (Quantization level number)' and the horizontal axis is labeled 'Time'. The bars show varying heights, indicating different quantization levels. Below the x-axis, the timeline is divided into segments with labels: $R_2$ , $V_5$ , $F_6$ , $F_0$ , $V_0$ , $V_1$ , $F_2$ , $V_1$ , $V_6$ , $F_2$ , $V_1$ , $R_3$ , $V_1$ , $V_0$ , $V_2$ , $R_{67}$ , $V_5$ , $F_0$ , and $R$ . Double-headed arrows indicate the duration of each segment. A break in the timeline is marked with '//' between $R_{67}$ and $V_5$ . A small code 'T1514070-93/d26' is located at the bottom right of the chart. + +A bar chart showing the quantization level number of prediction error 'e' over time. The y-axis is labeled 'e (Quantization level number)' and the x-axis is labeled 'Time'. The chart displays several bars of varying heights. Below the x-axis, there are labels for different regions and states: R2, V5, F6, F0, V0, V1, F2, V1, V6, F2, V1, R3, V1, V0, V2, R67, V5, F0, and R. A break in the x-axis is indicated by '//' between R67 and V5. A small code 'T1514070-93/d26' is present at the bottom right of the chart area. + +FIGURE G.1/H.120 +**Coding of prediction error e** + +a) When SBS is off + +![Timing diagram for SBS off. It shows three horizontal timelines: ΔV, SBS, and Code. ΔV has four rectangular pulses of varying heights. SBS is a single line labeled 'OFF'. Code has labels RL3, ΔV2, ΔV3, ΔV1, RL1, ΔV1, ΔV3, RL3 aligned with the pulses of ΔV.](55086c71bc8ee4c0abc7160d26a8092c_img.jpg) + +Diagram illustrating the coding of motion vector $v$ when SBS is off. The top timeline shows the magnitude of the motion vector $\Delta V$ over time, represented by four rectangular pulses. The middle timeline shows the SBS (Spatial Boundary Signal) status, which is constant at OFF. The bottom timeline shows the corresponding code sequence: $RL_3, \Delta V_2, \Delta V_3, \Delta V_1, RL_1, \Delta V_1, \Delta V_3, RL_3$ , where each element is aligned with a pulse in the $\Delta V$ signal. + +Timing diagram for SBS off. It shows three horizontal timelines: ΔV, SBS, and Code. ΔV has four rectangular pulses of varying heights. SBS is a single line labeled 'OFF'. Code has labels RL3, ΔV2, ΔV3, ΔV1, RL1, ΔV1, ΔV3, RL3 aligned with the pulses of ΔV. + +b) When SBS is on + +![Timing diagram for SBS on. It shows three horizontal timelines: ΔV, SBS, and Code. ΔV has four rectangular pulses. SBS is a line that is ON during the first three pulses and OFF during the fourth. Code has labels RL2, RL1, ΔV2, ΔV3, ΔV1, RL1, ΔV1, ΔV3, RL3. Vertical dashed lines labeled TRANS mark the start and end of the ON period for SBS, aligning with the start of RL1 and the start of the second RL1.](7b96fce298a23fd76a01ff6c176c1059_img.jpg) + +Diagram illustrating the coding of motion vector $v$ when SBS is on. The top timeline shows the magnitude of the motion vector $\Delta V$ over time, represented by four rectangular pulses. The middle timeline shows the SBS status, which is ON during the first three pulses and OFF during the fourth. The bottom timeline shows the corresponding code sequence: $RL_2, RL_1, \Delta V_2, \Delta V_3, \Delta V_1, RL_1, \Delta V_1, \Delta V_3, RL_3$ . Vertical dashed lines labeled TRANS indicate the transitions of the SBS signal, aligning with the start and end of the ON period. + +Timing diagram for SBS on. It shows three horizontal timelines: ΔV, SBS, and Code. ΔV has four rectangular pulses. SBS is a line that is ON during the first three pulses and OFF during the fourth. Code has labels RL2, RL1, ΔV2, ΔV3, ΔV1, RL1, ΔV1, ΔV3, RL3. Vertical dashed lines labeled TRANS mark the start and end of the ON period for SBS, aligning with the start of RL1 and the start of the second RL1. + +T1514080-93/d27 + +FIGURE G.2/H.120 +Coding of motion vector $v$ + +# Appendix I Outline description of operation of codecs in clauses 1 and 2 + +(This appendix does not form an integral part of this Recommendation) + +Since the conditional replenishment codec is a complex and unfamiliar item, this simplified outline of its method of operation is included to make the Recommendation more easily comprehensible. More complete descriptions are to be found in published papers [1], [2]. + +A conditional replenishment codec operates by transmitting only those parts of a picture which differ significantly from one television frame to the next. This normally gives rise to data being generated in spurts separated by gaps in which no data are being generated. To match the non-uniform data generation to a channel transmitting at a uniform rate, a buffer is used to smooth out short-term fluctuations while, for longer-term variations, the coding algorithm is adaptively modified to change the rate of generation. In the event of too much data, caused for example by a lot of movement, the definition of the transmitted moving area is decreased, taking advantage of the reduced ability of the eye to perceive detail as the rate of movement increases. When little movement is present, the moving-area data are supplemented by data from non-moving areas in such a way that the whole picture is replenished over several picture periods. Picture stores are required at both transmitter and receiver and the objective is to make the content of the receiving store follow that of the transmitting store as closely as possible. + +The codec can be regarded as comprising three basic sections: the source codec, the video multiplex codec and the transmission codec. Figure I-1 shows an outline of the arrangement. + +![Outline block diagram of codec showing Coder and Decoder sections. The Coder section includes ADC, DPrF, CRC, VMC, TB, and TC blocks. The Decoder section includes DAC, DPoF, CRD, VMD, RB, and TD blocks. Control signals and data inputs/outputs are shown for both sections.](977811d1c73b74f801be9f4c376694ca_img.jpg) + +The diagram illustrates the signal flow and control structure of a codec. The **Coder** section (top) takes an input of **Video 625-lines, 50 fields/s** through an **ADC** (Analogue-digital converter). The signal then passes through a **DPrF** (Digital pre-filter), a **CRC** (Conditional replenishment coder), a **VMC** (Video multiplex coder), a **TB** (Transmission buffer), and a **TC** (Transmission coder). The **TC** block also receives **Sound** and **Facsimile Data** inputs. The output of the **TC** is a stream at **2048 kbit/s**. The **Decoder** section (bottom) receives this stream through a **TD** (Transmission decoder), which also outputs **Sound** and **Facsimile Data**. The signal then passes through a **RB** (Receiving buffer), a **VMD** (Video multiplex decoder), a **CRD** (Conditional replenishment decoder), a **DPoF** (Digital post-filter), and a **DAC** (Digital-analogue converter) to produce the final output. Control signals are shown between the **VMC** and **TB** blocks, and between the **VMD** and **RB** blocks. A reference label **T1514090-93/d28** is present near the **TD** block. + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Coder

ADC Analogue-digital converter

DPrF Digital pre-filter

CRC Conditional replenishment coder

VMC Video multiplex coder

TB Transmission buffer

TC Transmission coder

|

Decoder

DAC Digital-analogue converter

DPoF Digital post-filter

CRD Conditional replenishment decoder

VMD Video multiplex decoder

RB Receiving buffer

TD Transmission decoder

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Outline block diagram of codec showing Coder and Decoder sections. The Coder section includes ADC, DPrF, CRC, VMC, TB, and TC blocks. The Decoder section includes DAC, DPoF, CRD, VMD, RB, and TD blocks. Control signals and data inputs/outputs are shown for both sections. + +FIGURE I.1/H.120 +**Outline block diagram of codec** + +In the source codec, the video signal is first digitized and optionally pre-filtered. When used, the pre-filter conditions the signal for further processing by reducing noise to improve the performance of the subsequent movement detector and to reduce the subjective effects of subsampling. The movement detector, in conjunction with the picture store, determines which areas in the picture are deemed to be moving. Noise introduces uncertainties in this decision and, when two or more groups of picture elements along a scanning line are deemed to be moving but are separated by small numbers of non-moving picture elements (probably caused by noise), the moving groups and separating elements are combined to form a single cluster, thus minimizing the addressing information which is required. Clusters of moving picture elements are then coded using DPCM followed by variable-length (entropy) coding where the shortest codes are allocated to the most frequently-occurring DPCM prediction errors. + +The video multiplex codec adds to the video data the line- and field-synchronization signals together with addressing and other information (for example, whether PCM or DPCM is being transmitted) which must be transmitted in close association with the video to ensure that the decoder responds correctly. + +The buffer, which strictly is part of the source coder, accepts the irregularly spaced bursts of data and delivers them at a uniform rate for transmission. The extent to which the buffer is filled is monitored and this is used to modify the rate of data generation by the source coder. It can reduce the data rate by modifying the pre-filter response and the thresholds in the movement detector, and by initiating element and field subsampling. On the other hand, if the buffer tends to empty, it may initiate the generation of complete PCM coded lines to provide systematic updating of the picture stores. + +The transmission codec accepts the video data, adds a 64 kbit/s channel for sound, a 32 kbit/s channel for codec-codesignalling and optional additional data channels for facsimile, signalling or other data. It assembles the various signals into a frame structure, defined in Recommendation H.130 which is compatible with Recommendation G.732 and therefore suitable for transmission on 2048 kbit/s digital paths. In doing so, it provides the justification facilities to enable the clock for video processing to be independent of the network clock. + +# Appendix II + +(referred to in Annexes A and C) + +(This appendix does not form an integral part of this Recommendation) + +## II.1 Cursor data + +In order to point out to items in the frozen graphics picture during face-to-face mode, a cursor has to be provided. The cursor is defined by a horizontal address, a vertical address and bits for cursor specification. + +The horizontal address consists of 8 bits: + +| Horizontal address | Codeword | +|---------------------------|-----------------| +| 1st picture element | 0 | +| 4th picture element | 1 | +| 7th picture element | 2 | +| . | . | +| . | . | +| . | . | +| 715th picture element | 238 | +| 718th picture element | 239 | + +The vertical address consists of 8 bits: + +| Vertical address | Codeword | | +|-------------------------|-----------------|--------------------------------------------------| +| 1st line | 0 | The line numbers indicate lines in a full frame. | +| 5th line | 1 | | +| 9th line | 2 | | +| . | | | +| . | | | +| . | | | +| 569th line | 142 | | +| 573rd line | 143 | | + +For the horizontal address codewords of the form 1111xxxx, for the vertical address codewords of the form 11xxxxxx (x = 0 or 1) are forbidden. + +For cursor specification, 6 bits are used as follows: XCCSSS. + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| SSS Shape | 000 = small circle
001 = arrow to the top
010 = arrow to the bottom
011 = arrow to the right
100 = arrow to the left
101 = cross | +| CC Colour | 00 = black
01 = red
10 = green
11 = white | +| X on/off | 0 = cursor off
1 = cursor on | + +The cursor defines the centre of the small circle, the centre of the cross, or the peak of an arrow. + +The graphics codecs have been designed for the transmission of half an A4 page. If eight bits each are used for transmission of the horizontal and of the vertical address of the cursor, a resolution of the cursor positioning results which is 0.8 mm in the horizontal direction, and 1 mm in the vertical direction. + +## II.2 Frame structure + +The cursor data are embedded in a pulse frame of length 32 bits as follows: + +| | | | | +|----------------------|----------------------|--------------------|------------------| +| 0111111111 | X CC SSS | HHHHHHHH | VVVVVVVV | +| frame alignment word | cursor specification | horizontal address | vertical address | + +The frame alignment word cannot be simulated by the cursor data, as some codewords for the horizontal and vertical address are forbidden. + +For transmission, the frame alignment word is leading, followed by the data for cursor specification. In the horizontal and vertical addresses the most significant bits are transmitted first. + +## II.3 Transmission of cursor data + +The cursor data for the graphics codec is transmitted in time slot 17 of the transmission frame. + +# References + +- [1] DUFFY (T. S.) and NICOL (R. C.): A codec for visual teleconferencing, *Communications 82*, IEE Conference Publication No. 209, 1982. +- [2] NICOL (R. C.), CHIARIGLIONE (L.) and SCHAEFER (P.): The development of the European Videoteleconference Codec, *Globecom 82*, IEEE global telecommunications conference, 1982. \ No newline at end of file diff --git a/marked/H/T-REC-H.200-199303-I_PDF-E/raw.md b/marked/H/T-REC-H.200-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e34b44c22a4b08a8c6c02164a3de9f1fd7ce80cc --- /dev/null +++ b/marked/H/T-REC-H.200-199303-I_PDF-E/raw.md @@ -0,0 +1,221 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**H.200** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/93) + +**LINE TRANSMISSION +OF NON-TELEPHONE SIGNALS** + +--- + +**FRAMEWORK FOR RECOMMENDATIONS +FOR AUDIOVISUAL SERVICES** + +**ITU-T Recommendation H.200** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation H.200 was revised by the ITU-T Study Group XV (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +--- + +# NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|------------------------------------------------------------------------|-------------| +| 1 Audiovisual services ..... | 1 | +| 2 Harmonization of audiovisual services ..... | 1 | +| 3 Purpose of this Recommendation..... | 1 | +| 4 Framework ..... | 2 | +| 5 List of audiovisual services covered ..... | 2 | +| 6 List of networks covered..... | 2 | +| Annex A – Framework for Recommendations for audiovisual services ..... | 3 | + + + +# **FRAMEWORK FOR RECOMMENDATIONS FOR AUDIOVISUAL SERVICES** + +*(Melbourne, 1988; amended at Helsinki, 1993)* + +## **1 Audiovisual services** + +A number of services are, or will be, defined in CCITT having as their common characteristic the transmission of speech together with other information reaching the eventual user in visual form. This Recommendation concerns a set of such services which should be treated in a harmonized way; it is convenient to refer to the members of this set as “audiovisual services” (abbreviated to AV services). + +## **2 Harmonization of audiovisual services** + +While the various audiovisual services may easily be distinguished in terms of their user-application, common methods are used for the transport of signals representing speech, moving or still pictures, and associated controls/indications, and also telematic auxiliary facilities. The standardization process seeks the greatest possible harmonization of these common features, confining the distinction to the application layers wherever possible, in order to: + +- a) Maximize the possibilities for intercommunication between terminals intended for different applications; +- b) Maximize the commonality of hardware and software in the interests of economies of scale. The scope for commonality includes: audio and video input/output parameters, audio and video codecs, the control/indication set, frame structures and multiplexing, call control procedures (including multipoint). + +The embodiment of this harmonization policy will be a consistent set of Recommendations, consistent in the sense that all members of the set take into account all other members. + +## **3 Purpose of this Recommendation** + +The purpose of this Recommendation is to define the set that shall be consistent. In fulfilling this function it is important to distinguish, at a given time, between Recommendations and draft Recommendations. + +Recommendations are members of the set by virtue of their consistency with other adopted members of the set: these are listed in Annex A. It is of course necessary to ensure continued consistency when amendments are introduced. + +Draft Recommendations range from mere titles or outline contents through varying stages of maturity to a stable final draft. As many different intended members of the Recommendation H.200 set are developed in parallel to ensure consistency they should be treated as “provisional” members of the set. The list of set members including provisional items does not form part of this Recommendation, but this Recommendation should be updated in the future to include new members of the set formally adopted. + +## 4 Framework + +Recommendations in the H.200 set are arranged in three main sections: + +- a) *Service definitions* – These specify the service as seen by the user, including basic service, optional enhancements, quality, and intercommunication requirements, together with operational aspects; technical implementation methods are taken into account but not defined herein. +- b) *Infrastructure* – This section includes all the Recommendations which are applicable to two or more distinct services: these encompass network configuration, frame structures, control/indications, communication/intercommunication, and audio/video coding. The “infrastructure” includes this generality of signals which flow on unrestricted digital bearers on established network connections – it does not include the methods of call establishment and control, orchestrated by signals outside these bearers. +- c) *Systems and terminal equipment* – This section deals with the technical implementation of specific services: it therefore includes service-specific equipment for the application layer, and draws upon the infrastructure Recommendations to identify the detailed processes required for the particular service. + +An “other aspects” section is included, covering such matters as call control, including aspects which are particular to AV services but, some involving out-of-band signals, do not come within the scope of the infrastructure section above. + +## 5 List of audiovisual services covered + +The following audiovisual services shall be included in the harmonized set: + +- narrowband videophone ( $p \times 64$ kbit/s); +- broadband videophone (a teleservice for broadband ISDN); +- narrowband videoconferencing ( $p \times 64$ kbit/s); +- broadband videoconferencing (a teleservice for broadband ISDN); +- audiographic teleconferencing; +- telephony (a degenerate case of an AV service, included for intercommunication purposes); +- telesurveillance. + +The following audiovisual services are in the process of being defined, and consideration should be given to their inclusion in the set for either of the reasons given in 2. + +- video mail; +- videotex (including pictures and sound); +- video retrieval; +- high resolution image retrieval; +- distribution services. + +## 6 List of networks covered + +The possible use of the following networks is taken into account: + +- ISDN (basic and primary access); +- B-ISDN (using ATM); +- analogue (PSTN); +- LANs (e.g. FDDI); +- mobile/radio; +- leased lines (digital). + +# Annex A + +(to Recommendation H.200) + +## Framework for Recommendations for audiovisual services + +(This annex forms an integral part of this Recommendation) + +## A.1 Service definition + +*Recommendation No.* + +| | | | +|--------|------------------------------------------------------------|---------------------------------------| +| AV.100 | General AV services | Draft available | +| AV.101 | Teleconference service | F.701 (F.710
in Blue Book ) | +| AV.110 | General principles for audiographic conference service | F.710 | +| AV.111 | Audiographic conference service | F.711 | +| AV.120 | Videotelephony services – General | F.720 | +| AV.121 | Basic narrow band videophone service in the ISDN | F.721 | +| AV.122 | Broadband videotelephony services | F.722 | +| AV.130 | Videoconference service – General | F.730 | +| AV.131 | Videoconference services – General | | +| AV.132 | Broadband videoconference services | F.732 | +| AV.140 | Audiovisual interactive services – General | F.740 | +| AV.150 | (Other AV services not yet defined) | | +| AV.160 | (Audiovisual service applications) | | +| AV.161 | Service oriented requirements for telewriting applications | F.761 (F.730
in Blue Book ) | + +## A.2 Infrastructure + +| | | | +|--------|-----------------------------------------------------------------------------------------------------------------------------|-------| +| AV.200 | (General AV infrastructure) | | +| AV.210 | (Reference networks) | | +| AV.220 | (Transmission multiplex structure) | | +| AV.221 | Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices | H.221 | +| AV.230 | Frame-synchronous control and indication signals for audiovisual systems | H.230 | +| AV.231 | Multipoint control units for audiovisual systems using digital channels up to 2 Mbit/s | H.231 | +| AV.232 | (Broadband multipoint control) | | +| AV.233 | Confidentiality system for audiovisual services | H.233 | +| AV.240 | (Communication – Principles) | | +| AV.241 | System aspects for the use of the 7 kHz audio codec within 64 kbit/s | G.725 | +| AV.242 | System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s | H.242 | +| AV.243 | Procedures for establishing communication between three or more audiovisual terminals using digital channels up to 2 Mbit/s | H.243 | +| AV.250 | (Audio coding) | | +| AV.251 | Pulse code modulation (PCM) of voice frequencies | G.711 | + +| | | | +|--------|------------------------------------------------------------------------------|------------------------------------| +| AV.252 | 7 kHz audio-coding within 64 kbit/s | G.722 | +| AV.253 | (Audio coding at 24/32 kbit/s) | | +| AV.254 | Coding of speech at 16 kbit/s using low-delay code excited linear prediction | G.728 | +| AV.255 | Audio coding for storage/retrieval | MPEG audio
(DIS 11172 Part 3) | +| AV.260 | (Video coding) | | +| AV.261 | Video codec for audiovisual services at $p \times 64$ kbit/s | H.261 | +| AV.262 | (Video coding for use on B-ISDN) | | +| AV.263 | Video coding for storage/retrieval up to about 1 Mbit/s | MPEG-1 Video
(DIS 11172 Part 2) | +| AV.264 | (Video coding for storage/retrieval at less than 10 Mbit/s) | MPEG-2 | +| AV.266 | (Video coding for distribution) | | +| AV.270 | Overview of AGC Recommendations | T.120 | +| AV.271 | Audiographic conferencing | T.121 | +| AV.272 | Generic conference control | T.124 | +| AV.273 | Protocol stacks for audiographic and audiovisual teleconference applications | T.123 | +| AV.274 | Multipoint communications service | T.122 | +| AV.280 | (For future purposes) | | +| AV.290 | (Interworking with pre-existing systems) | | +| AV.291 | (Interworking with H.120/H.130 systems) | | + +## A.3 Systems and terminal equipment + +| | | | +|--------|----------------------------------------|-----------------| +| AV.300 | (General AV systems/terminals) | | +| AV.310 | (TC systems and equipment) | | +| AV.311 | Audiographic teleconference | Draft available | +| AV.320 | Visual telephone systems and equipment | H.320 | +| AV.321 | (Broadband visual telephone) | | +| AV.330 | (Equipment for AV retrieval, systems) | | +| AV.331 | Broadcasting type multipoint systems | H.331 | + +### A.4 Other aspects + +| | | | +|--------|---------------------------------------|--| +| AV.400 | (Other aspects) | | +| AV.410 | (Reservation systems) | | +| AV.420 | [Call control (including multipoint)] | | +| AV.440 | (Multipoint call set-up) | | + +NOTE – Entries in parentheses are indicative of the purpose of the various positions in the framework. \ No newline at end of file diff --git a/marked/H/T-REC-H.221-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.221-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/H/T-REC-H.221-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/H/T-REC-H.221-200903-I_PDF-E/20727e57890be6da5692a02d13c0a8ec_img.jpg b/marked/H/T-REC-H.221-200903-I_PDF-E/20727e57890be6da5692a02d13c0a8ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f799fa2261842122e7930d96b12d3326c79829f4 --- /dev/null +++ b/marked/H/T-REC-H.221-200903-I_PDF-E/20727e57890be6da5692a02d13c0a8ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e885c11ebf6203583d11886d7fe7a479cc75753cbc7d644902b96d71a9e10858 +size 70840 diff --git a/marked/H/T-REC-H.221-200903-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg b/marked/H/T-REC-H.221-200903-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c42073e81ab27a399a411fed20de33e8372d071c --- /dev/null +++ b/marked/H/T-REC-H.221-200903-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47f6274f1fcd305e185663c5a86c170f205b413858a550da984dc32792217bfc +size 53425 diff --git a/marked/H/T-REC-H.221-200903-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/H/T-REC-H.221-200903-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fb05690e79bd48076c78c5e1912de6d3e560a17 --- /dev/null +++ b/marked/H/T-REC-H.221-200903-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84a709dc556ec40623c8dc562c63e728bdee7c5b5a772a220737a9619d364315 +size 52632 diff --git a/marked/H/T-REC-H.221-200903-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/H/T-REC-H.221-200903-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d907eb6384966a16d0e9bd59989f8024b1fc2ba --- /dev/null +++ b/marked/H/T-REC-H.221-200903-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5804a7abd6f1423c3bab479f49dc2e2fc581239eb60ef43f9145845d712bc41 +size 54172 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/132ad076dd59b60fd549f7a612ed568b_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/132ad076dd59b60fd549f7a612ed568b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48654d728881ac086007209a71399043a688cc42 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/132ad076dd59b60fd549f7a612ed568b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cde9632b8569afed815950dd32474ee38f04e06a59bc93ae82ad701c8ce71021 +size 25802 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/143c8ee1010bf7669caabfbed815df1b_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/143c8ee1010bf7669caabfbed815df1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5df2ec4918113f7ce305e982295812bfa35d7b51 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/143c8ee1010bf7669caabfbed815df1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d023db85d5270e39c3b4f14f4b8b0d5c96c709b650d3482d7cf866154f57f749 +size 19816 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/1922717e4a5ef189ba4572ea65b2f0ae_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/1922717e4a5ef189ba4572ea65b2f0ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb92608600549e4a61f7add968410cf49bcb2f20 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/1922717e4a5ef189ba4572ea65b2f0ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d80f065f2c75987df41719dfb13d0a4f6cc805ab7f732f1f2e6b8743c9a823c0 +size 22895 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8b3fa916496efdd6983a126e9291dc60382ea97 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dec4cb6f2dcf8d2d1338311a2205418ab0a8a849a20807164af1822a31ce7cc9 +size 5818 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba5634143c97159f321f67f9917f70f119063f80 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:767adb66fa10c95f75eef50ed5cd92998b36b422e45f044d23b98d3a4714f408 +size 20741 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11e168116c4787f62eb49a95929d5cc93fe09476 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:218d0671333b29b60ac4d62015ee5c8b729276bda3fd6f10120b0ee939f6afaa +size 103108 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0a135d9d6ac0db2b85cfe6203b4b1db4131d640 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27331ba5906e1e1a0675874f867ffab6fa379e04a6b947aee69a1f69d03e5889 +size 56688 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e927c3d0800d9a09b73f1e42ba095147439cae5d --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:038435e62dcd223a4a0851f57ce445927bd8cca6915507ea46d910de31556122 +size 23586 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c50364c7a0cad457725e1445edd005c557dbc05c --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d043e4b9610478bfebf992770d741ffb9470090a6d5cd66d5161c85700a5f1b2 +size 41759 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2302de8ad7e7176281cb0c16a5eed271983fe00b --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d92f736b6bda55b6a926da7569bd8ad27f0bb875c7a5f96a43fcb484f09ff1cf +size 26430 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/3fa5b988fc31a30231724a06f3567c54_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3fa5b988fc31a30231724a06f3567c54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a9cf1d8b9e76d1cbfe456e305e08b234ad9a0af --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/3fa5b988fc31a30231724a06f3567c54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cbdb8caeec5d9bc3532f893a3329c8bc829d00698a287654131ca5d29cc7e3e +size 19115 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/54159e6d8f5ecc73ad262758e3a60677_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/54159e6d8f5ecc73ad262758e3a60677_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9e548cdc2e29d84f858b40c27c062bbd8b9d144 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/54159e6d8f5ecc73ad262758e3a60677_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95e05e4e86013e6469599760c91c6b6a4e862bda7388df6e56c8d8a3be2e8c7c +size 60589 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/56f125e1bc127f7ac3d210407957413c_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/56f125e1bc127f7ac3d210407957413c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bafee45707d7c50bf580771cec5bcf6272f5cd97 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/56f125e1bc127f7ac3d210407957413c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:509b8c25193a15660ec635ee4c34aa1657994212313e20a451aa0962a6caf894 +size 36536 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06cfbc2f3e52ab98e3fc6edded541113a16d1bd7 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c1c53fe01f14a22d50f50560b680c1234b13a29f30a55000a5ed70726cef2de +size 37230 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8154ef27d363c364fe0d917a05f995a3245a820e --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bc73a1df95082c8bfc442e1927126973472a286933441294f4805cc6fd68ccd +size 61369 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/6e9d059430baba0c363e33749f68b107_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14bfc85ff246264e5e3361ee205c315bbcb3c835 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:704e9fb300f23ae4fa8e9d61062b92608a7b000e530c3f23ab315917b80f86e8 +size 61066 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/78151e5dd542eada99ead8203dfce76b_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/78151e5dd542eada99ead8203dfce76b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0b815d20eb09095f7603b57348a26f6deaba87f --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/78151e5dd542eada99ead8203dfce76b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93cc3e2460a89a4ca6d59762fe949ac00144b33dc2f282f60f03a77e33be11b5 +size 18943 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/845e014e3b8677eb735d0e21f21206be_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/845e014e3b8677eb735d0e21f21206be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ec3878ede9f4cad9d07a9a751d59a0ef1b7fccc --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/845e014e3b8677eb735d0e21f21206be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80c51adcc17fe4e900e78c175097665d22fac6505739b8a629f0aabfdeef87fb +size 68187 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/8768e42bf1062f1af11f259fc52a92e9_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/8768e42bf1062f1af11f259fc52a92e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddb8199958a82db71c2d232a25c404040b0ba9fd --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/8768e42bf1062f1af11f259fc52a92e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3487a9c6f6cb96e9758671c3b8e2df8ac94945e9c9beecd1af1a5d7af5ce0c24 +size 28744 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ffc5725d26c12443db43e241d4b916a66d9f5eb --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86a561872bbeaaab1d16f2d156d0c57210037c919c9fa4e5740b2c4f12de31b7 +size 80956 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..558ddecd7f429ec50b861fd26c41225a63fef2e6 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b3f360f78a41716ec9874652cb5a60e2764f403d8cf9c820505064fc1a13a7c +size 25574 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9f3042d4946cb3ec1d20f163d2f041a3e251a6e --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76ca0e8841cfb7a1943563734b50c4eb84a8647d8fef8abcd424af0c98825f34 +size 28308 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/ae57a92114d2bd84ef81129e7fbdd89d_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/ae57a92114d2bd84ef81129e7fbdd89d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2c7a585e4abedf14ad4042f1099cf2a67cc1450 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/ae57a92114d2bd84ef81129e7fbdd89d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:394847dfdb24668e689dba843a72bb42f4a70d9c1cb0fc8eaa75d51caf497d8b +size 41295 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/b02ba0b73e95416eb547976f6145b169_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/b02ba0b73e95416eb547976f6145b169_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e83c93e17b6307bac9516f6d8a877591fb232c9 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/b02ba0b73e95416eb547976f6145b169_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16419372baedea9e24d0d025fb75dc13f80df3f1556bb376a54d68d5015f461b +size 34202 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/b11b654648249b38a82129a35555b481_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/b11b654648249b38a82129a35555b481_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cee6d1cd5818ebeb5e8f4b1b1805853b154210cd --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/b11b654648249b38a82129a35555b481_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:532e171a48a3b9bf1a95ed9fbbe0b311b50c162d76246e437aae4caea43813e9 +size 25144 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..863e2d9e3721c21794466511e5c6d37a93d3ab3e --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9deecee427a33fe867b3b92044a9cad449bf997443e4c53faa99f75a9db67a0 +size 19081 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/c2e2b17d61aecbead88a6278e4ba3605_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/c2e2b17d61aecbead88a6278e4ba3605_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6895065739b8c03100bff51f901a90d1584cc10d --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/c2e2b17d61aecbead88a6278e4ba3605_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c1f52ecf803fc54e7a69b5482c12ec7167018c43c901c50b7ccf8a6728e9ea3 +size 29005 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9dfb8ecffcad058c1595d06cc494c2511c6e270 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf929f3e89c3336c88ad185f01a1274469c65102c13abd61747a26465b1243b4 +size 83870 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/ce5c6c3f1a6331655b939aaaaba0ecba_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/ce5c6c3f1a6331655b939aaaaba0ecba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..268f2029fb46186b1412ee61f0818345e248e9c8 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/ce5c6c3f1a6331655b939aaaaba0ecba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4883f968d890e52d6109b6b6e31cbd1b7e647e7471388a9872fadbe8b4f0e328 +size 33092 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/ceb6fe29e2d57711907569c31182b3c2_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/ceb6fe29e2d57711907569c31182b3c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcb44ce293957ce49e1afdff56a3e99f68817c09 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/ceb6fe29e2d57711907569c31182b3c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50d912e1ed35cbbfbe5e5428060a03298d847e34071c6f668c17491335676f46 +size 23456 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40e1cfc6c054486466313ed01c9827fc4ba6907c --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:604eacf835fd6f2139d674e4f34f57ed02901ea3167cb162d7feb3bbf7fae5bf +size 83444 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29f7e15ed7935dda69eae9108746712f0bd2cc07 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d73f7282ee90d9737ad7dd0a93cb9162e642937e2f79e0c657e65720bf5a14d +size 104622 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97a74b58c6b92dd774e5bf9e838ee85427c7dae0 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9874ab21e27b6301bb10c81d8c09fe110116b01be8eeeb401d669054091ddcc4 +size 24528 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg b/marked/H/T-REC-H.225.0-202203-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c1504c38eef6e45c21703faa7103025e960d3f2 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eccab8a44aaaac5d3135b47283175c2dfbbc15b3a1c6289f976c4bbb29fb7877 +size 21169 diff --git a/marked/H/T-REC-H.225.0-202203-I_PDF-E/raw.md b/marked/H/T-REC-H.225.0-202203-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f090d588767bca6ae9a948b200ad565523867ca8 --- /dev/null +++ b/marked/H/T-REC-H.225.0-202203-I_PDF-E/raw.md @@ -0,0 +1,8193 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.225.0** + +(03/2022) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Transmission +multiplexing and synchronization + +--- + +**Call signalling protocols and media stream +packetization for packet-based multimedia +communication systems** + +Recommendation ITU-T H.225.0 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a white grid pattern, overlaid by a stylized 'ITU' text in blue. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Content delivery and ubiquitous sensor network applications | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.225.0 + +# Call signalling protocols and media stream packetization for packet-based multimedia communication systems + +## Summary + +Recommendation ITU-T H.225.0 covers the technical requirements for narrow-band visual telephone services defined in H.200 and F.720-series Recommendations, in those situations where the transmission path includes one or more packet-based networks, each of which is configured and managed to provide a non-guaranteed Quality of Service (QoS) which is not equivalent to that of N-ISDN, such that additional protection or recovery mechanisms beyond those mandated by Rec. ITU-T H.320 need be provided in the terminals. It is noted that Rec. ITU-T H.322 addresses the use of some other LANs which are able to provide the underlying performance not assumed by ITU-T Recs H.323 and H.225.0. + +This Recommendation describes how audio, video, data, and control information on a packet-based network can be managed to provide conversational services in H.323 equipment. + +Products claiming compliance with Version 8 of H.225.0 (this version) shall comply with all of the mandatory requirements of this Recommendation. Version 8 products can be identified by H.225.0 messages containing a **protocolIdentifier** value of {itu-t (0) recommendation (0) h (8) 2250 version (0) 8}. + +This revision incorporates the following changes: + +- 1) Enhancements for language capability exchange. +- 2) Modification to the scope regarding use on the Internet. +- 3) Clarification that the **Facility** message may be used to initiate call transfer. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.225.0 | 1996-11-11 | 16 | 11.1002/1000/3836 | +| 2.0 | ITU-T H.225.0 | 1998-02-06 | 16 | 11.1002/1000/4231 | +| 2.1 | ITU-T H.225.0 Annex I | 1998-09-25 | 16 | 11.1002/1000/4501 | +| 2.2 | ITU-T H.225.0 Annex G | 1999-05-27 | 16 | 11.1002/1000/4672 | +| 3.0 | ITU-T H.225.0 | 1999-09-30 | 16 | 11.1002/1000/4762 | +| 4.0 | ITU-T H.225.0 | 2000-11-17 | 16 | 11.1002/1000/5257 | +| 4.1 | ITU-T H.225.0 (2000) Amd. 1 | 2002-11-29 | 16 | 11.1002/1000/6164 | +| 5.0 | ITU-T H.225.0 | 2003-07-14 | 16 | 11.1002/1000/6452 | +| 6.0 | ITU-T H.225.0 | 2006-05-29 | 16 | 11.1002/1000/8805 | +| 6.1 | ITU-T H.225.0 (2006) Amd. 1 | 2007-01-13 | 16 | 11.1002/1000/9025 | +| 7.0 | ITU-T H.225.0 v7 | 2009-12-14 | 16 | 11.1002/1000/10624 | +| 7.1 | ITU-T H.225.0 v7 (2009) Amd. 1 | 2013-03-16 | 16 | 11.1002/1000/11859 | +| 8.0 | ITU-T H.225.0 (V8) | 2022-03-16 | 16 | 11.1002/1000/14946 | + +## Keywords + +H.225.0, H.323, multimedia communication, videoconferencing, VoIP. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2022 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---|---------------------------------------------------------------|----| +| 1 | Scope | 1 | +| 2 | References | 3 | +| 3 | Definitions | 5 | +| 4 | Abbreviations and acronyms | 5 | +| | 4.1 General abbreviations | 5 | +| | 4.2 RAS message abbreviations | 7 | +| 5 | Conventions | 7 | +| 6 | Packetization and synchronization mechanism | 8 | +| | 6.1 General approach | 8 | +| | 6.2 Use of RTP/RTCP | 11 | +| 7 | H.225.0 message definitions | 14 | +| | 7.1 Use of Q.931 messages | 14 | +| | 7.2 Common Q.931 information elements | 17 | +| | 7.3 Q.931 based H.225.0 call signalling message details | 27 | +| | 7.4 Q.932-based H.225.0 call signalling message details | 41 | +| | 7.5 H.225.0 call signalling timer values | 46 | +| | 7.6 H.225.0 common message elements | 46 | +| | 7.7 Required support of RAS messages | 60 | +| | 7.8 Terminal and gateway discovery messages | 61 | +| | 7.9 Terminal and gateway registration messages | 63 | +| | 7.10 Terminal/gatekeeper unregistration messages | 69 | +| | 7.11 Terminal to gatekeeper admission messages | 71 | +| | 7.12 Terminal to gatekeeper requests for changes in bandwidth | 76 | +| | 7.13 Location request messages | 78 | +| | 7.14 Disengage messages | 82 | +| | 7.15 Status request messages | 84 | +| | 7.16 Non-standard message | 88 | +| | 7.17 Message not understood | 89 | +| | 7.18 Gateway resource availability messages | 89 | +| | 7.19 RAS timers and Request in Progress (RIP) | 90 | +| | 7.20 Service control messages | 92 | +| | 7.21 AdmissionConfirmSequence | 94 | +| | 7.22 Error Code Mapping | 94 | +| 8 | Mechanisms for maintaining QoS | 95 | +| | 8.1 General approach and assumptions | 95 | +| | 8.2 Use of RTCP in measuring QoS | 96 | +| | 8.3 Audio/Video jitter procedures | 96 | +| | 8.4 Audio/Video skew procedures | 97 | + +| | Page | +|-----------------------------------------------------------------------------------|-------------| +| 8.5 Procedures for maintaining QoS | 97 | +| 8.6 Echo control | 97 | +| Annex A – RTP/RTCP | 99 | +| Annex B – RTP profile | 100 | +| Annex C – RTP payload format for H.261 video streams | 101 | +| Annex D – RTP payload format for H.261A video streams | 102 | +| D.1 Introduction | 102 | +| D.2 H.261A RTP packetization | 102 | +| Annex E – Video packetization | 104 | +| E.1 H.263 | 104 | +| Annex F – Audio and multiplexed packetization | 105 | +| F.1 G.723.1 | 105 | +| F.2 G.728 | 106 | +| F.3 G.729 | 106 | +| F.4 Silence suppression | 109 | +| F.5 GSM codecs | 110 | +| F.6 G.722.1 | 111 | +| F.7 TIA/EIA-136 ACELP | 112 | +| F.8 TIA/EIA-136 US1 | 113 | +| F.9 IS-127 EVRC | 115 | +| F.10 H.223 MUX-PDU packetization | 117 | +| Annex G – Communication between and within administrative domains | 118 | +| G.1 Scope | 118 | +| G.2 Definitions | 119 | +| G.3 Abbreviations | 120 | +| G.4 Normative references | 120 | +| G.5 System models | 120 | +| G.6 Operation | 123 | +| G.7 Signalling examples | 129 | +| G.8 Annex G profiles | 138 | +| Annex H – H.225.0 message syntax (ASN.1) | 143 | +| Annex I – H.263+ video packetization | 181 | +| Appendix I – RTP/RTCP algorithms | 182 | +| Appendix II – RTP profile | 183 | +| Appendix III – H.261 packetization | 184 | +| Appendix IV – H.225.0 operation on different packet-based network protocol stacks | 185 | +| IV.1 TCP/IP/UDP | 185 | +| IV.2 SPX/IPX | 188 | + +| | Page | +|--------------------------------------------------------------------------|-------------| +| IV.3 SCTP..... | 189 | +| Appendix V – ASN.1 usage in this Recommendation..... | 190 | +| V.1 Tagging..... | 190 | +| V.2 Types ..... | 190 | +| V.3 Constraints and ranges..... | 190 | +| V.4 Extensibility..... | 190 | +| Appendix VI – H.225.0 identifiers of tunnelled signalling protocols..... | 191 | + + + +# **Recommendation ITU-T H.225.0** + +# Call signalling protocols and media stream packetization for packet-based multimedia communication systems + +# **1 Scope** + +This Recommendation describes the means by which audio, video, data, and control are associated, coded, and packetized for transport between H.323 equipment on a packet-based network. This includes the use of an H.323 gateway, which in turn may be connected to H.320, H.324, or H.310/H.321 terminals on N-ISDN, GSTN, or B-ISDN respectively. The equipment descriptions and procedures are described in Rec. ITU-T H.323 while this Recommendation covers protocols and message formats. Communication via an H.323 gateway to an H.322 gateway for guaranteed Quality of Service (QoS) LANs and thus to H.322 endpoints is also possible. + +This Recommendation is intended to operate over a variety of different packet-based networks, including IEEE 802.3, Token Ring, etc. Thus, this Recommendation is defined as being above the Transport layer such as TCP/IP/UDP, SPX/IPX, etc. Specific profiles for particular transport protocol suites are included in Appendix IV. This packet-based network may be a single segment or ring, it logically could be an enterprise data network comprising multiple packet-based networks bridged or routed to create one interconnected network, or it could be the Internet. The possible means by which quality of service might be assured on this packet-based network, or on the Internet in general, is beyond the scope of this Recommendation. However, this Recommendation provides a means for the user of H.323 equipment to determine that quality problems are the result of packet-based network congestion, as well as procedures for corrective actions. It is also noted that the use of multiple H.323 gateways connected over the public ISDN network is a straightforward method for increasing quality of service. + +Rec. ITU-T H.323 and this Recommendation are intended to extend H.320 and H.221 connections onto the non-guaranteed QoS packet-based network environment conferences. As such the primary conference model1 is one with size in the range of a few participants to a few thousand, as opposed to large-scale broadcast operations, with strong admission control, and tight conference control. + +This Recommendation makes use of (RTP/RTCP) Real-time Transport Protocol/Real-Time Transport Control Protocol for media stream packetization and synchronization for all underlying packet-based networks (see Annexes A, B and C). Please note that the usage of RTP/RTCP as specified in this Recommendation is not tied in any way to the usage of TCP/IP/UDP. This Recommendation assumes a call model where initial signalling on a non-RTP transport address is used for call establishment and capability negotiation (see Recs ITU-T H.323 and H.245), followed by the establishment of one or more RTP/RTCP connections. This Recommendation contains details on the usage of RTP/RTCP. + +In Rec. ITU-T H.221, audio, video, data, and control are multiplexed into one or more synchronized physical SCN calls. On the packet-based network side of an H.323 call, none of these concepts apply. There is no need to carry from the SCN side the H.221 concept of a $P \times 64$ kbit/s call, e.g., 2 by 64 kbit/s, 3 by 64 kbit/s, etc. Thus, on the packet-based network side, for example, there are only single "connection" calls with a maximum rate limited to 128 kbit/s, not $2 \times 64$ kbit/s fixed rate calls. Another example has single "connection" packet-based network calls with a maximum rate limited + +--- + +1 An optional broadcast-only conference model is under consideration; of necessity the broadcast model does not provide tight admissions or conference control. + +to 384 kbit/s interworking with $6 \times 64$ kbit/s on the SCN side2. The primary rationale of this approach is to put complexity in the gateway rather than the terminal and to avoid extending onto the packet-based network features of H.320 that are tightly tied to ISDN unless this is necessary. + +In general, H.323 terminals are not aware directly of the H.320 transfer rate while interworking through an H.323 gateway; instead, the gateway uses H.245 **FlowControlCommand** messages to limit the media rate on each logical channel in use to that allowed by the H.221 multiplex. The gateway may allow the packet-based network side video rates to substantially underrun the SCN side rates (or the reverse) through the usage of a rate reducing function and H.261 fill frames; the details of such operations are beyond the scope of Rec. ITU-T H.323 and this Recommendation. Note that the H.323 terminal is indirectly aware of the H.320 transfer rates via the video maximum bit rate fields in Rec. ITU-T H.245 and shall not transmit at rates that exceed these rates. + +This Recommendation is designed so that, with an H.323 gateway, interoperability with H.320 (1990), H.320 (1993), and H.320 (1996) terminals is possible. However, some features of this Recommendation may be directed toward allowing enhanced operations with future versions of Rec. ITU-T H.320. It is also possible that the quality of service on the H.320 side may vary based on the features and capabilities of the H.323 gateway (see Figure 1). + +The general approach of this Recommendation is to provide a means of synchronizing packets that make use of the underlying packet-based network/transport facilities. This Recommendation does not require all media and control to be mixed into a single stream, which is then packetized. The framing mechanisms of Rec. ITU-T H.221 are not utilized for the following reasons: + +- Not using H.221 allows each media to receive different error treatment as appropriate. +- H.221 is relatively sensitive to the loss of random groups of bits; packetization allows greater robustness in the packet-based network environment. +- H.245 and H.225.0 call signalling messages can be sent over reliable links provided by the packet-based network. +- The flexibility and power of H.245 as compared to H.242. + +--- + +2 Note that video and data rates on the LAN side must match the video and data rates in the SCN side H.320 multiplex; the audio and control rates are not required to match. Stated another way one would normally expect that, using H.245 flow control, the LAN/SCN gateway will force the video and data rates to fit into the H.221 SCN multiplex. However, since audio may be transcoded in the gateway often, one will frequently find that the LAN audio rate and the SCN rate do not match. Also there should be no expectation that the H.221 bit rate for control (800 bit/s) will generally match the H.245 bit rate on the LAN side. Also note that the LAN rate may under-run the SCN rate for either/both video or/and data, but it cannot exceed the maximum amount that fits into the SCN side multiplex. + +![Diagram of H.323 protocol stack and H.225.0 scope. The H.323 protocol stack is shown as a layered model. The top layer contains AV app, Terminal control and management, and Data app. The next layer contains G.xxx, H.261, RTP, RTCP, H.225.0 terminal to gatekeeper signalling (RAS), H.225.0 call signalling, and H.245. The next layer contains Unreliable transport and Reliable transport. The next layer contains Network layer, Link layer, and Physical layer. A dashed line on the left indicates the LAN boundary. To the right, the H.323 gateway is shown with Other stacks and H.225.0 stack. Below the stack, a box labeled H.225.0 scope is shown. The label H.225.0_F01 is at the bottom right.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +H.225.0\_F01 + +Diagram of H.323 protocol stack and H.225.0 scope. The H.323 protocol stack is shown as a layered model. The top layer contains AV app, Terminal control and management, and Data app. The next layer contains G.xxx, H.261, RTP, RTCP, H.225.0 terminal to gatekeeper signalling (RAS), H.225.0 call signalling, and H.245. The next layer contains Unreliable transport and Reliable transport. The next layer contains Network layer, Link layer, and Physical layer. A dashed line on the left indicates the LAN boundary. To the right, the H.323 gateway is shown with Other stacks and H.225.0 stack. Below the stack, a box labeled H.225.0 scope is shown. The label H.225.0\_F01 is at the bottom right. + +**Figure 1 – H.225.0 scope** + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] Recommendation ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies.* +- [2] Recommendation ITU-T G.722 (2012), *7 kHz audio-coding within 64 kbit/s.* +- [3] Recommendation ITU-T G.728 (2012), *Coding of speech at 16 kbit/s using low-delay code excited linear prediction.* +- [4] Recommendation ITU-T G.723.1 (2006), *Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s.* +- [5] Recommendation ITU-T G.729 (2012), *Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP).* +- [6] Recommendation ITU-T H.221 (2009), *Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices.* +- [7] Recommendation ITU-T H.230 (2009), *Frame-synchronous control and indication signals for audiovisual systems.* +- [8] Recommendation ITU-T H.233 (2002), *Confidentiality system for audiovisual services.* + +- [9] Recommendation ITU-T H.242 (2009), *System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s.* +- [10] Recommendation ITU-T H.243 (2005), *Procedures for establishing communication between three or more audiovisual terminals using digital channels up to 1920 kbit/s.* +- [11] Recommendation ITU-T H.245 (2022), *Control protocol for multimedia communication.* +- [12] Recommendation ITU-T H.261 (1993), *Video codec for audiovisual services at $p \times 64$ kbit/s.* +- [13] Recommendation ITU-T H.263 (2005), *Video coding for low bit rate communication.* +- [14] Recommendation ITU-T H.320 (2004), *Narrow-band visual telephone systems and terminal equipment.* +- [15] Recommendation ITU-T T.122 (1998), *Multipoint communication service – Service definition.* +- [16] Recommendation ITU-T T.123 (1999), *Network-specific data protocol stacks for multimedia conferencing.* +- [17] Recommendation ITU-T T.125 (1998), *Multipoint communication service protocol specification.* +- [18] Recommendation ITU-T H.321 (1998), *Adaptation of H.320 visual telephone terminals to B-ISDN environments.* +- [19] Recommendation ITU-T H.322 (1996), *Visual telephone systems and terminal equipment for local area networks which provide a guaranteed quality of service.* +- [20] Recommendation ITU-T H.324 (2009), *Terminal for low bit-rate multimedia communication.* +- [21] Recommendation ITU-T H.310 (1998), *Broadband audiovisual communication systems and terminals.* +- [22] Recommendation ITU-T Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control.* +- [23] Recommendation ITU-T Q.932 (1998), *Digital subscriber signalling system No. 1 – Generic procedures for the control of ISDN supplementary services.* +- [24] Recommendation ITU-T X.680 (2015) | ISO/IEC 8824-1:2008, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation.* +- [25] Recommendation ITU-T X.681 (2015) | ISO/IEC 8824-2:2008, *Information technology – Abstract Syntax Notation One (ASN.1): Information object specification.* +- [26] Recommendation ITU-T X.691 (2015) | ISO/IEC 8825-2:2008, *Information technology – ASN.1 encoding rules – Specification of Packed Encoding Rules (PER).* +- [27] Recommendation ITU-T E.164 (2010), *The international public telecommunication numbering plan.* +- [28] ISO/IEC 10646:2020, *Information technology – Universal Multiple-Octet Coded Character Set (UCS).* +- [29] Recommendation ITU-T Q.850 (1998), *Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN user part.* +- [30] Recommendation ITU-T Q.950 (2000), *Supplementary services protocols, structure and general principles.* + +- [31] Recommendation ITU-T H.235.0 (2022), *H.323 security: Framework for security in H-series (H.323 and other H.245-based) multimedia systems.* +- [32] ISO/IEC 11571:1998, *Information technology – Telecommunications and information exchange between systems – Private Integrated Services Networks – Addressing.* +- [33] IETF RFC 1738 (1994), *Uniform Resource Locators (URL).* +- [34] Recommendation ITU-T Q.115.1 (2002), *Logic for the control of echo control devices and functions.* +- [35] IETF RFC 5646 (2009), *Tags for Identifying Languages.* +- [36] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3.* +- [37] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications.* +- [38] IETF RFC 3551 (2003), *RTP Profile for Audio and Video Conferences with Minimal Control.* +- [39] IETF RFC 4587 (2006), *RTP Payload Format for H.261 Video Streams.* +- [40] Recommendation ITU-T X.690 (2015) | ISO/IEC 8825-4:2015, *Information technology – ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER).* + +# 3 Definitions + +See definitions in Rec. ITU-T H.323. In Rec. ITU-T H.323 the term "endpoint" is used to refer to terminals, gateways, and MCUs as elements that are capable of receiving or initiating calls. In this Recommendation the term "terminal" is often used in a general way in descriptions of call setup, and should be understood as referring to an element that can take part in call setup, including a gateway or MCU. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +## 4.1 General abbreviations + +| | | +|-------|---------------------------------| +| BAS | Bit rate Allocation Signal | +| CIF | Common Intermediate Format | +| CRV | Call Reference Value | +| ECS | Encryption Control Signal | +| FFS | For Further Study | +| GOB | Group of Blocks | +| H-MLP | High speed Multi-Layer Protocol | +| HSD | High Speed Data | +| IA5 | International Alphabet No. 5 | +| IE | Information Element | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| LAN | Local Area Network | + +| | | +|---------|--------------------------------------------------| +| LD-CELP | Low Delay – Code Excited Linear Prediction | +| LSB | Least Significant Bit | +| LSD | Low Speed Data | +| MB | Macro Block (see Rec. ITU-T H.261) | +| MBE | Multi-Byte Extension | +| MCC | Multipoint Command Conference | +| MCN | Multipoint Command Negating | +| MCS | Multipoint Command Symmetrical data transmission | +| MCS | Multipoint Communication Service | +| MCU | Multipoint Control Unit | +| MF | MultiFrame | +| MLP | Multi-Layer Protocol | +| MPI | Minimum Picture Interval | +| MSB | Most Significant Bit | +| NA | Not Applicable | +| NS | Non-Standard | +| NSAP | Network Service Access Point | +| PCM | Pulse Code Modulation | +| PDU | Protocol Data Unit | +| QCIF | Quarter Common Intermediate Format | +| QoS | Quality of Service | +| RAS | Registration, Admission and Status | +| RTCP | Real-time Transport Control Protocol | +| RTP | Real-time Transport Protocol | +| SBE | Single Byte Extension | +| SC | Service Channel | +| SCM | Selected Communications Mode | +| SCN | Switched Circuit Network | +| TCP | Transport Control Protocol | +| TSAP | Transport Service Access Point | +| UDP | User Datagram Protocol | +| URL | Uniform Resource Locator | +| VCF | Video Command "Freeze picture Request" | +| VCU | Video Command "Fast Update Request" | + +## **4.2 RAS message abbreviations** + +| | | +|------|----------------------------------------------| +| ACF | Admissions Confirm | +| ARJ | Admissions Reject | +| ARQ | Admissions Request | +| BCF | Bandwidth Confirm | +| BRJ | Bandwidth Reject | +| BRQ | Bandwidth Request | +| DCF | Disengage Confirm | +| DRJ | Disengage Reject | +| DRQ | Disengage Request | +| GCF | Gatekeeper Confirm | +| GRJ | Gatekeeper Reject | +| GRQ | Gatekeeper Request | +| IACK | Information request Acknowledgement | +| INAK | Information request Negative Acknowledgement | +| IRQ | Information Request | +| IRR | Information Request Response | +| LCF | Location Confirm | +| LRJ | Location Reject | +| LRQ | Location Request | +| RAC | Resource Availability Confirmation | +| RAI | Resource Availability Indication | +| RCF | Registration Confirm | +| RIP | Request In Progress | +| RRJ | Registration Reject | +| RRQ | Registration Request | +| SCI | Service Control Indication | +| SCR | Service Control Response | +| UCF | Unregistration Confirm | +| URJ | Unregistration Reject | +| URQ | Unregistration Request | + +# **5 Conventions** + +In this Recommendation, "shall" refers to a mandatory requirement, while "should" refers to a suggested but optional feature or procedure. The term "may" refers to an optional course of action without expressing a preference. + +When a term such as "MCU" is used, an H.323 MCU is referred to. If an H.231 MCU is intended, this will be explicitly noted. + +In this Recommendation kilobits/second is abbreviated kbit/s and is measured in units of 1000. Thus, 64 kbit/s is exactly 64 000 bits per second. + +Unless otherwise specified, the aligned variant PER encoding of ASN.1 shall be used for all ASN.1 specified in this Recommendation. + +Q.931 message names are Capitalized. ASN.1 names are indicated in **bold**. + +NOTE – More recent Recommendations normally represent ASN.1 names using `courier` font. For consistency of presentation with other Recommendations of the H.323 system, ASN.1 names in this text are kept in **bold** typeface. + +# 6 Packetization and synchronization mechanism + +## 6.1 General approach + +Before any calls are made, an endpoint may discover/register with a gatekeeper. If this is the case, it is desirable for the endpoint to know the vintage of the gatekeeper it is registering with. It is also desirable for the gatekeeper to know the vintage of endpoints that register with it. For these reasons, both the *discovery* and registration sequences contain an H.245 style OBJECT IDENTIFIER that allows the vintage to be determined in terms of the version of Rec. ITU-T H.323 implemented. This sequence also may contain optional non-standard message parts to allow endpoints to establish non-standard relationships. At the end of this sequence, both gatekeepers and endpoints are aware of the version numbers and the non-standard status of each other. + +The version number is mandatory and non-standard information is optional in the Setup/Connect sequence described below to allow two endpoints to inform each other of their vintage and non-standard status. Note, however, that all H.225.0 call signalling messages have a field for an optional non-standard message in the User-user information element, and that all RAS channel messages have an optional field for non-standard information. In addition, a non-standard RAS message has been defined that can be sent at any time. + +The unreliable channel for registration, admissions, and status messaging is called the RAS channel. The general approach to starting a call is to send a mandatory admission request on the RAS channel3, followed by an initial Setup message on a reliable channel transport address (this address may have been returned in the admission confirmation message, or may have been known to the calling terminal). As a result of this initial message, a call setup sequence commences based on H.225.0 call signalling operations with enhancements described below. The sequence is complete when the terminal receives in the Connect message a reliable transport address on which to send H.245 control messages4. + +When messages are sent on the reliable H.225.0 call signalling channel, only one whole message shall be sent within the boundaries defined by the reliable transport; there shall be no fragmentation of H.225.0 messages across transport PDUs. (In IP implementations as outlined in Appendix IV, this PDU is defined by TPKT.) + +Once the reliable H.245 control channel has been established, additional channels for audio, video, and data may be established based on the outcome of the capability exchange using H.245 logical channel procedures. Also, the nature of the packet-based network-side multimedia conference + +--- + +3 A terminal that is not registered with a gatekeeper is not required to send an admissions request. + +4 Note that the H.245 address may be sent in the Alerting or Call Proceeding message to shorten call setup time. Note that the H.245 channel may be opened immediately after the receipt of the H.245 address in the Setup message. + +(centralized vs. distributed/multicast) is negotiated on a per connection basis5. This negotiation is performed per media, in the sense that, for example, audio/video may be distributed, while data and control are centralized. + +When messages are sent on the reliable H.245 control channel, more than one message may be sent within the boundaries defined by the reliable transport PDU as long as whole messages are sent; there shall be no fragmentation of H.245 messages across transport PDUs. (In IP implementations as outlined in Appendix IV, this PDU is defined by TPKT.) + +H.225.0 terminals shall be capable of sending audio and video using RTP via unreliable channels to minimize delay. Error concealment or other recovery action may be applied to overcome lost packets; in general audio/video packets are not re-transmitted since this would result in excessive delay in the packet-based network environment6. It is assumed that bit errors are detected in the lower layers, and errored packets are not sent up to H.225.0. Note that audio/video and call signalling/H.245 control are never sent on the same channel, and do not share a common message structure. H.225.0 terminals shall be capable of sending and receiving audio and video on separate transport addresses using separate instances of RTP to allow for media-specific frame sequence numbers and separate quality of service treatment for each media. However, an optional mode where audio and video packets are mixed in a single frame which is sent to a single transport address is for further study. + +T.120 capabilities are negotiated using H.245, and upon receipt of appropriate messages, T.120 conferences are established using the transport/packet-based network stacks of T.123 as appropriate. T.120 shall be conveyed over the packet-based network between endpoints on another transport address. Table 1 shows the number of TSAP identifiers used for each media on a point-to-point call. It is also true that a given H.323 terminal may be able to participate in more than one conference at a time, resulting in the use of additional TSAP identifiers. All H.245 logical channels used are unidirectional except for those associated with T.120, which are bidirectional. + +**Table 1 – TSAP IDs used by H.225.0 per point-to-point unicast call** + +| Usage of TSAP IDs | Reliable or unreliable | Well-known or dynamic | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------| +| Audio/RTP | Unreliable | Dynamic | +| Audio/RTCP | Unreliable | Dynamic | +| Video/RTP | Unreliable | Dynamic | +| Video/RTCP | Unreliable | Dynamic | +| Call Signalling | Reliable | Well-known or dynamic | +| H.245 | Reliable | Dynamic | +| Data (T.120) | Reliable | Well-known or dynamic | +| RAS | Unreliable | Well-known or dynamic | +| NOTE – If well-known TSAP identifiers are used, there can only be a single endpoint per network address. Also, in the direct call model the caller requires a well-known TSAP identifier for the Call Signalling channel to start the call. | | | + +Although the transport address for, say, audio and video, may share the same packet-based network address and differ only by TSAP identifier, some manufacturers may choose to use different packet- + +5 The LAN side conference may be part centralized and part distributed, as decided by the MC controlling the conference. However, the terminal is not aware of this fact. Generally, of course, all terminals will see the same Selected Communications Mode (SCM) (see Rec. ITU-T H.243 for a definition). + +6 Fast Update of full frames, MBs, or GOBs may be requested via H.245 signalling. + +based network addresses for audio and video. The only requirement is that the convention of Annexes A and B should be followed in the numbering of TSAP identifiers in the RTP session7. + +Table 1 describes the basic case of point-to-point unicast operations between two terminals. To facilitate the construction of gateways, MCUs, and gatekeepers, dynamic TSAP IDs may be used instead of well-known TSAP IDs. Tables 2 and 3 illustrate an example of TSAP ID usage for the gateway/MCU case, and for the gatekeeper case. + +**Table 2 – TSAP IDs used on one MCU/gateway port (Unicast example)** + +| Usage of TSAP IDs | Reliable or unreliable | Well-known or dynamic | +|-------------------------------|------------------------|-----------------------| +| Audio/RTP | Unreliable | Dynamic | +| Audio/RTCP | Unreliable | Dynamic | +| Video/RTP | Unreliable | Dynamic | +| Video/RTCP | Unreliable | Dynamic | +| Call Signalling | Reliable | Dynamic (Note) | +| H.245 | Reliable | Dynamic | +| Data (T.120) | Reliable | Dynamic | +| RAS | Unreliable | Dynamic (Note) | +| NOTE – See Note 1 of Table 3. | | | + +**Table 3 – Example of TSAP IDs usage by H.225.0 gatekeeper supporting the gatekeeper mediated call model of Figure 28/H.323 for a point-to-point call** + +| Usage of TSAP IDs | Reliable or unreliable | Well-known or dynamic | Number of channels | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------------------|---------------------| +| Call Signalling | Reliable | Dynamic or well-known (Note 1) | 2 per call (Note 2) | +| H.245 | Reliable | Dynamic | 2 per call (Note 2) | +| RAS | Unreliable | Well-known | 1 | +| NOTE 1 – If the well-known TSAP ID is used, the gatekeeper may be limited to a single endpoint per device; therefore, dynamic TSAP IDs should be used. | | | | +| NOTE 2 – 0 for direct call model; 2 for gatekeeper-mediated call model. | | | | + +Note that a reliable transport address is used for call setup for the terminal to terminal case, and also for the gatekeeper-mediated case. The reliable call signalling connection shall be kept active until a Release Complete message is received for all active calls signalled over the call signalling channel. + +Note that more than one H.245 channel may be open at a given time, i.e., an endpoint may be in more than one call/conference at the same time. Note also that within a specific call, a terminal may have more than one channel of the same type open, e.g., two audio channels for stereo audio. The only limitation is that there shall be one and only one H.245 control channel per point-to-point call. + +H.245 logical channel signalling is used to start and stop video, audio, and data protocol usage. This process calls for closing the open channel, and then reopening with a new mode of operation. As part of the process of opening the channel, before sending the open logical channel acknowledgment, the endpoint uses the ARQ/ACF or BRQ/BCF sequence to ensure that sufficient bandwidth is available for the new channel (unless sufficient bandwidth is available from a previous ARQ/ACF or BRQ/BCF + +7 Note that any TSAP ID can be used for the initial RTP session; the major reason to follow the RTP convention is for possible IETF RTP interoperability. + +sequence). In some cases, the gateway may find that the SCN side mode change occurs more quickly than the packet-based network side mode change, resulting in the possibility of the loss of audio information. The gateway may adopt several approaches at the discretion of the manufacturer: + +- a) the gateway may transcode audio, thus hiding the SCN mode changes; +- b) the gateway may simply throw away audio information; or +- c) the gateway may operate as an H.231 MCU, thus gaining control over all SCN side mode changes. + +No general rule exists concerning whether H.245 or RTP procedures (see Annexes A, B and C) take precedence; each conflict and its resolution is specifically mentioned in this Recommendation. + +Note also that there is no fixed association between SSRCs and logical channels; Rec. ITU-T H.245 provides this association which may be used for audio/video synchronization. + +In general, two types of conference modes of operation on the packet-based network side are possible: distributed and centralized. It is also possible that different choices may be made for different media, e.g., distributed audio/video and centralized data. Procedures for determining what sort of conference to establish are in Rec. ITU-T H.323; the messages of this Recommendation are intended to support all allowed combinations, noting that distributed control and data are for further study although supported by the H.245 capability signalling. + +## 6.2 Use of RTP/RTCP + +The H.225.0 endpoint shall be capable of using separate TSAP IDs for audio and video and the associated RTCP channels as described in Annexes A and B. Optionally, endpoints may choose to use different packet-based network addresses for audio and video, but for each packet-based network address the convention of Annexes A and B should be followed in the use of TSAP IDs. Using H.245 signalling, additional audio and video channels may be established if the terminal supports this capability. + +An optional capability to use a single transport address for both audio and video is for further study. + +Unless an exception is specifically mentioned here, implementations shall follow those of RTP as contained in Annex A unless modified by text in this Recommendation. Implementations shall follow the RTP profile (see Annex B) only as specifically mentioned in this Recommendation. + +RTP translators and mixers are not elements of the H.323 system, and any information about them in Annexes A and B shall be regarded as informative. Note that both gateways and MCUs have some aspects of both mixers and translators, and the information in Annexes A and B may be helpful in the implementation of gateways and MCUs. However, MCUs are not mixers, and mixers are not MCUs. Note that gateways, for example, on a packet-based network-to-packet-based network call via the gateway may act as translators. + +**Version (V):** Version 2 of RTP shall be used. + +**CSRC Count (CC):** Use of the CSRC count in this Recommendation is optional. When not in use, the value of CC shall be zero (0). The CSRC may be used by MCUs to provide information on contributors to the audio sum when distributed audio processing is occurring. Note that there are no capabilities associated with the ability to understand the CSRC count so the MCU/MC has no way of knowing whether and how the terminal in the conference makes use of the information. + +**CNAME:** In the simplest case of a point-to-point connection on the packet-based network, the SSRC is used to identify an audio/video source from a terminal, and the streams are associated by a CNAME as being supplied by the same endpoint as specified in Annex A. + +When using RTCP, either RR or SR packets shall be sent periodically as described in Annex A. The CNAME SDES message shall be used. Other SDES messages (see Annex A) are optional, but shall not be used for conference control or conference information when either H.245 and/or T.120 control + +functions are in use. Information provided by Rec. ITU-T H.245 and/or Rec. ITU-T T.120 shall be regarded as the correct information. + +The RTCP BYE message shall not be relied on for RTP session termination. The H.323 terminal determines when a call is disconnected via the procedures of Rec. ITU-T H.323. The only mandatory use of the RTCP BYE packet is for SSRC collision resolution. + +The H.323 terminal, when engaged in any conference, whether point-to-point or multipoint, shall restrict the logical channel bit rate averaged over a period as defined in Rec. ITU-T H.245 to that signalled in the H.245 **FlowControlCommands**, H.245 logical channel commands, and the T.120 flow control mechanism. + +When the H.323 terminal is connected to an H.323 gateway, the gateway shall use the means of ITU-T Recs H.245 and T.120 to force the H.323 terminal to transmit at a rate less than or equal to the SCN side media rates and receive at a rate equal or higher than the SCN rate, with the following exceptions: + +- Control bandwidth on the packet-based network need not match that in Rec. ITU-T H.221. +- Audio bandwidth on the packet-based network may match that in Rec. ITU-T H.221 on the SCN, but with gateway transcoding a match is not required. +- In the case where the gateway is using a rate reducer: the packet-based network-side H.323 terminal shall not exceed the H.245 signalled rate, which will probably be less than the rate being sent over the SCN. + +Encryption for H.323 endpoints is for further study. + +### 6.2.1 Audio + +Before considering how audio is packetized using RTP, attention must be directed toward how it is signalled via H.245, and the relationship of this signalling to RTP. In general, when the audio channel is opened, an H.245 logical channel is opened. H.245 signalling in the **AudioCapability** structure is given in terms of the maximum number of frames per packet. The frame size for this Recommendation varies with the audio coding in use. + +All H.323 terminals offering audio communication shall support G.711. For all frame-oriented audio codecs, receivers shall signal the maximum number of audio frames they are capable of accepting in a single audio packet. Transmitters may send any whole number of audio frames in each packet, up to the maximum stated by the receiver. Transmitters shall not split audio frames across packets, and shall send whole numbers of octets in each audio packet. + +Sample-based codecs, such as G.711 and G.722, shall be considered to be frame-oriented, with a frame size of eight samples. (See Annex B for additional information regarding guidelines for sample-based audio encoding.) For audio algorithms such as G.723.1 which use more than one size of audio frame, audio frame boundaries within each packet shall be signalled in-band to the audio channel. + +For audio algorithms which use a fixed frame size (see ITU-T Recs G.728 and G.729 for the frame size used by each) audio frame boundaries shall be implied by the ratio of packet size to audio frame size; in other words only whole audio frames shall be put in the RTP packet. + +**Payload Type (PT):** Only ITU-T payload types such as (0)[PCMU], (8)[PCMA], (9)[G722], and (15)[G728] shall be used for ITU-T codecs signalled in Rec. ITU-T H.245. Dynamic payload types exchanged using H.245 signalling shall be used for any ITU-T payload types not listed in Annex B. + +It is recommended that if an interruption in sequence numbers is observed, the receiver may repeat the most recent received sounds such that the amplitude of the repeated sound decays to silence; other similar procedures may be used at the discretion of the manufacturer. + +Each G.711 octet shall be octet aligned in an RTP packet. The sign bit of each G.711 octet shall correspond to the most significant bit of the octet in the RTP packet (i.e., assuming the G.711 samples are handled as octets on the host machine, the sign bit shall be the most significant bit of the octet as defined by the host machine format). + +When sending 48/56 kbit/s PCM toward the packet-based network, the H.323 gateway shall pad the extra 1 or 2 bits in each octet in accordance with Note 2 in Table 1b/G.711, and use the RTP values for PCMA or PCMU(8 or 0). For $\mu$ -law the padding consists of "1" in both the 7th and 8th bit. For A-law the 7th bit shall be 0 and the 8th bit 1. In the reverse direction the H.323 gateway shall truncate 64 kbit/s G.711 on the packet-based network side to fit the G.711 rate being used in H.320. Thus, on the packet-based network side only 64 kbit/s G.711 shall be used. + +When sending 48/56 kbit/s G.722 toward the packet-based network, the H.323 gateway shall pad the extra 1 or 2 bits in each octet, and use dynamic RTP payload types as signalled by Rec. ITU-T H.245 to differentiate between 64 kbit/s (which uses PT = 9) and the reduced rate cases. In the reverse direction the H.323 gateway shall truncate 64 kbit/s G.722 on the packet-based network side to fit the G.711 rate being used in H.320. Thus, on the packet-based network side only 64 kbit/s G.722 shall be used. + +If possible, the H.323 terminal should make use of the silence suppression feature of RTP, especially when the conference is multicast. The H.323 terminal shall be able to receive silence compressed RTP streams. Coders may omit sending audio signals during silent periods after sending a single frame of silence, or may send silence background fill frames if such techniques are specified by the audio codec Recommendation in use. + +### 6.2.2 Video messages + +**Payload Type (PT):** Only ITU-T payload types such as that for Rec. ITU-T H.261 or Rec. ITU-T H.263 shall be used for ITU codecs signalled in Rec. ITU-T H.245. Dynamic payload types may be used for codecs which can be signalled via H.245 and for which packetization formats have not been defined. + +**Marker (M):** The marker bit should be set according to the procedures described in Annex A except in cases where it would increase end-to-end delay. + +In order to recover from the loss of video packets, H.245 **VideoFastUpdatePicture**, **VideoFastUpdateMB**, and **VideoFastUpdateGOB** shall be supported. Use of the RTCP control packets Full Intra Request (FIR) [send me a full frame] and Negative Acknowledgment (NACK) [Send me certain packets] is optional, and signalled in H.245 capabilities. + +Error recovery method 3) as described in Section 5 of RFC 4587 [39] may be impractical if the NACK does not arrive within one frame time. + +H.261 is packetized on the packet-based network side as per Annex C. As long as sufficiently large RTP packets are available, fragmentation on MB boundaries by the transmitter is not required. However, if the H.323 terminal fragments H.261 packets on the RTP level, this fragmentation shall occur on MB boundaries. All H.323 terminals shall be able to receive MB fragmented packets as well as GOB fragmented packets, or packets with a mix of MBs and GOBs. Note that failure to support MB fragmentation in the transmitter may result in the loss of an entire GOB, and may also lower the packet rate. RTP packets used shall not exceed the size of the Maximum Transfer Unit (MTU) on a given packet-based network to maximize robustness of operation, but if the smallest independently coded element of the coding scheme (e.g., a macroblock) is larger than the MTU size it is not required to break up the packet over MTUs. MBs shall not be split across packets; all packets shall end on a GOB or MB boundary. The H.323 transmitter may choose to fill out a packet containing a small GOB with additional MBs, but this is not required. + +To preclude the possibility of corruption in multiple pictures caused by the loss of an RTP packet, the RTP packetizer in an H.323 endpoint shall not include video from more than one picture in an RTP packet. + +The SBIT is the number of most significant bits that shall be ignored in the first data octet. EBIT is the number of least significant bits that shall be ignored in the last data octet. + +The RTP packetizer shall not intentionally octet align video at the start of RTP packets. In other words, if $EBIT = n$ in an RTP packet, SBIT in the next RTP packet shall equal $8 - n$ , $0 < n < 8$ , and if $EBIT = 0$ in an RTP packet, SBIT in the next RTP packet shall equal 0. This requirement avoids possible additional end-to-end delay caused by bit-shifting. This requirement shall apply across picture boundaries. + +Annex D specifies an H.323 extension to the video packet header that contains an optional octet count. The use of this optional extension is described in Annex D. + +See Appendix IV for packet-based network-specific advice on video packetization. + +### 6.2.3 Data messages + +There are no special data messages or formats; T.120 is used on the packet-based network as per Rec. ITU-T T.123. Centralized vs. distributed data conferencing on the packet-based network is described in Rec. ITU-T H.323, and is negotiated via H.245. + +T.120 flow control on the packet-based network is managed using packet-based network protocols when requested by H.245 **FlowControlCommand** and **maxBitRate** limits. + +See Rec. ITU-T H.323 for the procedures used to connect a running T.120 conference to an H.323 conference, or to add an H.323 call to a T.120 conference. + +The protocol to be used by H.224 on the packet-based network is for further study. + +# 7 H.225.0 message definitions + +This clause concerns the definition of messages for call setup, call control, and communications between terminals, gateways, gatekeepers, and MCUs. + +The ASN.1 definitions for all H.225.0 messages appear in Annex H. + +## 7.1 Use of Q.931 messages + +Implementations shall follow Rec. ITU-T Q.931 as specified in this Recommendation. Terminals may also support optional H.450 APDUs in the User-User IE. The messages shall contain all of the mandatory information elements and may contain any of the optional information elements as defined in Rec. ITU-T Q.931 as described in this Recommendation. The H.225.0 endpoint may, according to Rec. ITU-T Q.931, ignore all optional messages it does not support without harming interoperability, but shall respond with a Status message that should contain Cause No. 95 "Invalid message, unspecified" to an H.225.0 message it cannot understand or decode due to a Q.931 or ASN.1 encoding error. + +Error handling procedures defined in clause 5.8 and associated sub-clauses of Rec. ITU-T Q.931 do not apply to H.225.0 endpoints. + +Each H.225.0 endpoint shall be able to receive and identify an incoming H.225.0 call signalling message including one containing an H.450 APDU in the User-user IE. It shall be capable of processing the mandatory H.225.0 call signalling messages; it may be capable of processing the optional H.225.0 call signalling messages. In any case, each H.225.0 endpoint shall be able to ignore messages unknown to it without disturbing operation. + +Each H.225.0 endpoint shall be able to interpret and generate the information elements mandated in the following for the respective H.225.0 call signalling messages and H.450 APDU in User-user IE. It may interpret and generate the optional information elements as defined below as well. It may also interpret other information elements of Q.931, or other Q-series or H.450 protocols. The endpoints shall be able to ignore unknown information elements contained in an H.225.0 call signalling message or H.450 APDU without disturbing operation. H.225.0 endpoints shall not send multiple information elements of the same type in the same message; for example, they shall not send multiple Calling Party Number information elements as described in Annex A/Q.951. + +Information Elements shall be encoded according to Rec. ITU-T Q.931, except where modified in this Recommendation. However, Rec. ITU-T Q.931 shall always dictate the proper ordering of information elements within a message, regardless of the order of elements listed within this Recommendation. + +Intermediate systems (gateways and gatekeepers) shall follow the rules below with regard to H.225.0 call signalling optional messages and information elements: + +- 1) The gateway should and the gatekeeper shall, after appropriate modification, forward all information elements (optional or mandatory) associated with mandatory H.225.0 call signalling messages either from the terminal to the gateway/terminal or in the reverse direction. This includes such information elements as User-user information and the Display information. +- 2) A gateway should forward all H.225.0 call signalling messages including those containing H.450 APDUs and information elements in both directions. +- 3) A gatekeeper shall forward all H.225.0 call signalling messages including those containing H.450 APDUs and information elements in both directions after appropriate modification. Note that the gatekeeper may act as a signalling element that can provide features (such as supplementary service features) and may therefore modify, terminate, or originate H.225.0 call signalling messages. + +H.323 gateways may be capable of converting H.450-series supplementary services and H.225.0 messages to the corresponding supplementary services and messages of ISO/IEC 11582, ISUP and other SCN signalling standards. Details are the scope of Rec. ITU-T H.246 and its annexes. + +H.323 gateways may be capable of passing on unmodified signalling messages of ISO/IEC 11582, ISUP and other SCN signalling standards using tunnelling of non-H.323 signalling in H.225.0. Details are in Annex M/H.323 (see M.1/H.323, M.2/H.323, etc.). + +In this version of this Recommendation, all references are to the 1998 version of Rec. ITU-T Q.931. The procedures of 3.1/Q.931 for circuit mode connection setup are followed. However, the implementer is reminded that although "bearer" is being signalled for, no actual "B-channels" of the ISDN type exist on the packet-based network side. Successful completion of the "call" results in an end-to-end reliable channel supporting H.245 messaging. Actually "bearer" setup is done using H.245. However, the use of Q.931 on the packet-based network side enables interworking with Q.931 on the SCN side as well as providing a well-tested framework for general connection oriented calling features. + +In general, the symmetric procedures of Annex D/Q.931 are used. This implies that the Q.931 state machine is followed as per Annex D/Q.931 with the exception that the procedure of D.3/Q.931 (Call collisions) shall not be followed; recovery from this glare condition is left to the application layer. + +Endpoints not supporting Q.931 shifted code sets shall ignore all Q.931 messages using such methods. + +Table 4 shows what messages are mandatory and optional for H.323 and H.225.0 call setup using Q.931 on the packet-based network. + +**Table 4 – H.225.0 usage of Q.931/Q.932 messages** + +| | Transmit
(M, F, O, CM) (Note 1) | Receive and act on
(M, F, O (Note 2), CM) | +|----------------------------------------|--------------------------------------------|------------------------------------------------------| +| Call establishment messages | | | +| Alerting | M | M | +| Call Proceeding | O | CM (Notes 3 and 6) | +| Connect | M | M | +| Connect Acknowledge | F | F | +| Progress | O | CM (Note 6) | +| Setup | M | M | +| Setup Acknowledge | O | O | +| Call Clearing messages | | | +| Disconnect | F | F | +| Release | F | F | +| Release Complete | M (Note 4) | M | +| Call Information Phase messages | | | +| Resume | F | F | +| Resume Acknowledge | F | F | +| Resume Reject | F | F | +| Suspend | F | F | +| Suspend Acknowledge | F | F | +| Suspend Reject | F | F | +| User Information | O | O | +| Miscellaneous messages | | | +| Congestion Control | F | F | +| Information | O | CM (Note 6) | +| Notify | O | O | +| Status | M (Note 5) | M | +| Status Inquiry | O | M | +| Q.932/H.450 messages | | | +| Facility | M | M | +| Hold | F | F | +| Hold Acknowledge | F | F | +| Hold Reject | F | F | + +**Table 4 – H.225.0 usage of Q.931/Q.932 messages** + +| | Transmit
(M, F, O, CM) (Note 1) | Receive and act on
(M, F, O (Note 2), CM) | +|----------------------|------------------------------------|----------------------------------------------| +| Retrieve | F | F | +| Retrieve Acknowledge | F | F | +| Retrieve Reject | F | F | + +NOTE 1 – M: Mandatory, F: Forbidden, O: Optional, CM: Conditionally Mandatory. Something is CM if it is required once an option is supported. +NOTE 2 – Note that Status shall not be sent in response to a message listed here as "O"; the receiver shall simply ignore the message if it does not support it. +NOTE 3 – Terminals intended to use gateways shall receive and act on Call Proceeding. +NOTE 4 – Release Complete is required to close the H.225.0 reliable call signalling channel. However, the call signalling channel shall remain open if other calls using the same call signalling channel are still in progress. Additionally, the Gatekeeper may set the **maintainConnection** flag to TRUE to prevent the closure of the call signalling channel. +NOTE 5 – The endpoint shall respond to an unknown message with a Status message; response to Status Inquiry is also mandatory. However, an endpoint is not required to send Status Inquiry. As a practical matter, the endpoint should be able to understand a Status message received in response to a message sent that was not known to the receiver. +NOTE 6 – Endpoints that support optional features that use these messages (such as H.245 tunnelling, H.450 supplementary services, tunnelling of signalling protocols, or features that use **genericData**) shall process these messages. + +## 7.2 Common Q.931 information elements + +### 7.2.1 Header information elements + +For all H.225.0 call signalling messages, there are three common fields that are mandatory in addition to the message type that are described in this clause. + +#### 7.2.1.1 Protocol discriminator + +As defined in 4.2/Q.931. + +Shall be set to 08H – this identifies the message as Q.931/I.451 user-network message (encoded following Figure 4-2/Q.931). If a gatekeeper is acting as a network to supply supplementary services, it may be appropriate to use another value. This is for further study. + +#### 7.2.1.2 Call reference + +As defined in 4.3/Q.931. + +A call reference value length of two octets shall be supported by any H.323 endpoint. + +The call reference value is chosen at the side originating the call and has to be locally unique. For subsequent communication, the calling and the called side shall use this call reference value in all the messages belonging to this particular call. + +The value is encoded following Figure 4-5/Q.931 for a two-octet call reference value. The most significant octet of the reference value is always encoded in octet No. 2. + +Note that the CRV is only unique on a particular part of a call, e.g., between two terminals, or between a terminal and a gatekeeper. If a given terminal has two calls in the same conference, each shall have the same conference ID but different CRVs. + +The call reference flag shall be set according to the procedures described in Rec. ITU-T Q.931. + +Note that the CRV values passed in RAS messages shall conform to the structure as specified in Rec. ITU-T Q.931. Specifically, the call reference flag shall be included as the most significant bit of the Call ReferenceValue. This restricts the actual CRV to the range of 0 through 32 767, inclusive. + +The Global Call Reference, as shown in Figure 4-5/Q.931 and having the numeric value 0, is used to refer to all calls on the Call Signalling Channel or the RAS channel. + +#### 7.2.1.3 Message type + +The message type is encoded according to Figure 4-6/Q.931 using the values specified in Table 4-2/Q.931. H.225.0 specific extensions are for further study. + +### 7.2.2 Message-specific information elements + +The general encoding rules for the following information elements are defined in 4.5.1/Q.931 and Table 4-3/Q.931. These rules shall be followed. The escape mechanism (see Figure 4-8/Q.931) is optional. + +#### 7.2.2.1 Bearer capability + +This information element is encoded according to Figure 4-11/Q.931 and Table 4-6/Q.931. If this information element is received in a packet-based network-to-packet-based network call, it may be ignored by the receiver. If this information element appears in a Setup message for a call-independent signalling connection as defined in Rec. ITU-T H.450.1, the coding shall follow 7.2.2.1.2. In all other cases, coding shall follow 7.2.2.1.1. The octet number references refer to Figure 4-11/Q.931. + +##### 7.2.2.1.1 Bearer capability default encoding + +H.323 entities shall encode the Bearer capability IE as follows unless indicated otherwise in subsequent clauses. + +*Extension bit for octet No. 3 (bit 8)* + +- Shall be set to "1". + +*Coding Standard (octet No. 3, bits 6-7)* + +- Shall be set to "00" indicating "ITU-T". + +*Information transfer capability (octet No. 3, bits 1-5)* + +- For calls originating from an ISDN endpoint, the information indicated to the gateway shall be forwarded. + +NOTE – This is to allow some advance information about the nature of the connection to be forwarded to the H.323 endpoint, e.g., voice only vs. data vs. video; this would have an impact on the bandwidth required as well as on the ability/willingness to accept the call or not. + +- Calls that originate from an H.323 endpoint shall use this field to indicate their wish to place an audiovisual call. Therefore, the field shall be set either to "unrestricted digital information", i.e., "01000" or to "restricted digital information", i.e., "01001". If a speech only call is to be placed, the H.323 terminal shall set the information transfer capability to either "speech" (i.e., "00000") or to "3.1 kHz audio" (i.e., "10000"). + +*Extension bit for octet No. 4 (bit 8)* + +- Shall be set to "0" if the information transfer rate is set to "multirate"; shall be set to "1" otherwise. + +*Transfer Mode (octet No. 4, bits 6, 7)* + +- Shall specify "circuit mode", value "00". + +###### *Information transfer rate (octet No. 4, bits 1-5)* + +- Shall be encoded following Table 4-6/Q.931 except that the value "00000" (for packet mode) is not permitted unless the gateway is connected to a packet network. + +###### *Rate multiplier (octet No. 4.1)* + +- Shall be present if information transfer rate is set to "multirate". +- The extension bit (bit 8) shall be set to "1". +- The bits 1 through 7 shall indicate the bandwidth needed for the call as defined in the following (note, that in contrast to Rec. ITU-T Q.931, a value of "0000001" is allowed here). +- For a call originating from an ISDN endpoint, the gateway shall simply pass on the information that it receives from the ISDN. +- For a call incoming from an H.324 endpoint, the gateway shall set the rate multiplier to 01H. +- For a call incoming from B-ISDN, some translation from Rec. ITU-T Q.2931 to Rec. ITU-T Q.931 needs to be performed. This is for further study. +- For a call originated from an H.323 endpoint, this shall be used to indicate the bandwidth to be used for this call. If the called system is another H.323 endpoint, this value may reflect the bandwidth to be used on the packet-based network, but the receiving terminal is not required to follow this information. If a gateway is involved, then this value shall reflect the number of external connections to be set up. The bandwidth needed for the call is the bandwidth needed on the SCN side, and may or may not match the bandwidth allowed on the packet-based network by the ACF/BCF messages. + +###### *Layer 1 protocol (Octet No. 5)* + +- The extension bit (bit 8) shall be set to "1". +- Bits 6 and 7 shall indicate the layer one identifier, i.e., "01". +- Bits 1 through 5 shall indicate the layer one protocol. +- The allowed values are G.711 (A-law "00011" and $\mu$ -law "00010") to indicate a voice-only call and H.221 and H.242 ("00101") to indicate an H.323 videophone call. + +*Octets Nos. 5a, 5b, 5c, 5d, 6 and 7 shall not be present.* + +##### **7.2.2.1.2 Bearer capability encoding for H.450.1 call-independent signalling connections** + +H.323 entities shall encode the Bearer capability IE as follows for call-independent signalling connections as defined in Rec. ITU-T H.450.1. + +###### *Extension bit for octet No. 3 (bit 8)* + +- Shall be set to "1". + +###### *Coding standard (octet No. 3, bits 6-7)* + +- Shall be set to "01" indicating "Other international standard". Note that when this coding standard is indicated, the coding defined in Rec. ITU-T Q.931 shall apply for octets 1 to 2 and bit 8 of octets 3 to 4. Information transfer capability, Transfer mode and Information transfer rate shall be encoded as indicated and no other octets shall be included. + +###### *Information transfer capability (octet No. 3, bits 1-5)* + +- Shall be set to "01000", indicating "Unrestricted digital information". + +###### *Extension bit for octet No. 4 (bit 8)* + +- Shall be set to "1". + +###### *Transfer mode (octet No. 4, bits 6, 7)* + +- Shall be set to "00", indicating "Call-independent signalling connection". + +*Information transfer rate (octet No. 4, bits 1-5)* + +- Shall be set to "00000", indicating "Call-independent signalling connection". + +*Octets 4.1 and higher shall not be included.* + +#### **7.2.2.2 Call identity** + +The possible use of the Call identity IE is for further study. This study should consider multi-stage dialling, including terminal-to-gatekeeper-to-terminal and terminal-to-gateway-to-terminal, and loose source routing. + +#### **7.2.2.3 Call state** + +This information element is encoded following Figure 4-13/Q.931. + +*Octet No. 3 coding standard (bits 8-7)* + +- Set to "00" to indicate ITU-T standardized coding. + +*Call state value (octet No. 3, bits 1-6)* + +- Set as per Table 4-8/Q.931 but do not use the global interface state values. Values are interpreted as User State as per use of Annex D/Q.931. Note that most of the listed codes will not be generated by an H.323 terminal. + +#### **7.2.2.4 Called party number** + +This information element is encoded following Figure 4-14/Q.931 and Table 4-9/Q.931. + +*Octet No. 3 extension (bit 8)* + +- Set to "1". + +*Type of number (octet No. 3, bits 5-7)* + +- Encoded following the values and rules of Table 4-9/Q.931. + +*Numbering plan identification (octet No. 3, bits 1-4)* + +- Encoded following the values and rules of Table 4-9/Q.931. A number in the form of a dialled digit string should be coded as "0000" (Unknown). If set to "1001" (Private Numbering Plan) in a packet-based network originated call, this indicates that: + - 1) the dialled digit string is not present in Setup; and + - 2) the call will be routed via an alias address in the User-user information. + +*Type of number (octet No. 3, bits 5-7)* + +- Encoded following the values and rules of Table 4-9/Q.931. A number with the Numbering plan identification coded as "0000" (Unknown) shall be coded as "000" (Unknown). A number with the Numbering plan identification coded as "0001" (ISDN/Telephony Numbering Plan, Rec. ITU-T E.164) with the Type of number coded as "000" (Unknown) may be used for backward compatibility. + +*Number "digits"* + +- Any number of IA5 characters, according to the formats specified in the appropriate numbering/dialling plan. + +NOTE – An E.164 number shall only consist of IA5 characters "0", "1", "2", "3", "4", "5", "6", "7", "8" and "9". + +#### **7.2.2.5 Called party subaddress** + +Use as per Rec. ITU-T Q.931. + +#### **7.2.2.6 Calling party number** + +This information element is encoded following Figure 4-16/Q.931 and Table 4-11/Q.931. + +##### *Type of number (octet No. 3, bits 5-7)* + +- Encoded following the values and rules of Table 4-11/Q.931. A number with the Numbering plan identification coded as "0000" (Unknown) shall be coded as "000" (Unknown). A number with the Numbering plan identification coded as "0001" (ISDN/Telephony Numbering Plan, Rec. ITU-T E.164) with the Type of number coded as "000" (Unknown) may be used for backward compatibility. + +##### *Numbering plan identification (octet No. 3, bits 1-4)* + +- Encoded following the values and rules of Table 4-11/Q.931. A number in the form of a dialled digit string should be coded as "0000" Unknown. If set to "1001" (Private Numbering Plan) in a packet-based network originated call, this indicates that: + - 1) the dialled digit string is not present in Setup; and + - 2) the call will be routed via an alias address in the User-user information. + +##### *Octet No. 3a* + +- Encoded following the values and rules of Table 4-11/Q.931. + +##### *Number "digits"* + +- Any number of IA5 characters, according to the formats specified in the appropriate numbering/dialling plan. + +NOTE – An E.164 number shall only consist of IA5 characters "0", "1", "2", "3", "4", "5", "6", "7", "8" and "9". + +H.323 endpoints shall not send multiple Calling Party Number IEs in the same message. Gateways may provide support for interworking with Q.931 SETUP messages that contain multiple Calling Party Number IEs. Gateways that provide such support shall map the first Q.931 Calling Party Number IE to the Calling Party Number IE of the H.225.0 Setup message, and map subsequent Q.931 Calling Party Number IEs to the **additionalSourceAddresses** field of the H.225.0 Setup message. Gatekeepers that route H.225.0 Setup messages initiated by an H.323 endpoint may insert a number in the **additionalSourceAddresses** field before forwarding it to its next recipient. + +#### 7.2.2.7 Calling party subaddress + +Use as per Rec. ITU-T Q.931. + +#### 7.2.2.8 Cause + +If received, the rules defined in Rec. ITU-T Q.850 apply. Note that either Cause or **ReleaseCompleteReason** is mandatory for Release Complete; the Cause IE is optional elsewhere. The Cause IE and the **ReleaseCompleteReason** (a part of the Release Complete message) are mutually exclusive. Gateways shall map from a **ReleaseCompleteReason** to the Cause IE when sending a Release Complete message to the circuit-switched side from the packet-based network side (see Table 5). (The reverse mapping is not required as packet-based network entities are required to decode the Cause IE.) + +Gateways shall also map from **AdmissionRejectReason** and **LocationRejectReason** to the Cause IE when sending a Release Complete message to the circuit-switched side after receiving an **AdmissionReject** or a **LocationReject** (see Table 6). + +**Table 5 – ReleaseCompleteReason to Cause IE mapping** + +| ReleaseCompleteReason code | Corresponding Q.931/Q.850 cause value | +|----------------------------|----------------------------------------| +| noBandwidth | 34 – No circuit/channel available | +| gatekeeperResources | 47 – Resource unavailable, unspecified | +| unreachableDestination | 3 – No route to destination | + +**Table 5 – ReleaseCompleteReason to Cause IE mapping** + +| ReleaseCompleteReason code | Corresponding Q.931/Q.850 cause value | +|--------------------------------------|-------------------------------------------------| +| destinationRejection | 16 – Normal call clearing | +| invalidRevision | 88 – Incompatible destination | +| noPermission | 127 – Interworking, unspecified | +| unreachableGatekeeper | 38 – Network out of order | +| gatewayResources | 42 – Switching equipment congestion | +| badFormatAddress | 28 – Invalid number format (address incomplete) | +| adaptiveBusy | 41 – Temporary Failure | +| inConf | 17 – User busy | +| undefinedReason | 31 – Normal, unspecified | +| facilityCallDeflection | 16 – Normal call clearing | +| securityDenied | 31 – Normal, unspecified | +| securityWrongSyncTime | 31 – Normal, unspecified | +| securityReplay | 31 – Normal, unspecified | +| securityWrongGeneralID | 31 – Normal, unspecified | +| securityWrongSendersID | 31 – Normal, unspecified | +| securityMessageIntegrityFailed | 31 – Normal, unspecified | +| securityWrongOID | 31 – Normal, unspecified | +| securityDHmismatch | 31 – Normal, unspecified | +| securityCertificateExpired | 31 – Normal, unspecified | +| securityCertificateDateInvalid | 31 – Normal, unspecified | +| securityCertificateRevoked | 31 – Normal, unspecified | +| securityCertificateNotReadable | 31 – Normal, unspecified | +| securityCertificateSignatureInvalid | 31 – Normal, unspecified | +| securityCertificateMissing | 31 – Normal, unspecified | +| securityCertificateIncomplete | 31 – Normal, unspecified | +| securityUnsupportedCertificateAlgOID | 31 – Normal, unspecified | +| securityUnknownCA | 31 – Normal, unspecified | +| calledPartyNotRegistered | 20 – Subscriber absent | +| callerNotRegistered | 31 – Normal, unspecified | +| newConnectionNeeded | 47 – Resource unavailable, unspecified | +| nonStandardReason | 127 – Interworking, unspecified | +| replaceWithConferenceInvite | 31 – Normal, unspecified | +| genericDataReason | 31 – Normal, unspecified | +| neededFeatureNotSupported | 31 – Normal, unspecified | +| tunnelledSignallingRejected | 127 – Interworking, unspecified | +| InvalidCID | 3 – No route to destination | +| hopCountExceeded | 3 – No route to destination | + +**Table 6 – AdmissionRejectReason/LocationRejectReason to Cause IE mapping** + +| AdmissionRejectReason or LocationRejectReason code | Corresponding Q.931/Q.850 cause value | +|-----------------------------------------------------------|---------------------------------------------------| +| calledPartyNotRegistered | 20 – Subscriber absent | +| invalidPermission | 127 – Interworking, unspecified | +| requestDenied | 31 – Normal, unspecified | +| undefinedReason | 31 – Normal, unspecified | +| callerNotRegistered | 31 – Normal, unspecified | +| routeCallToGatekeeper | Not applicable | +| invalidEndpointIdentifier | 127 – Interworking, unspecified | +| resourceUnavailable | 47 – Resource unavailable | +| securityDenial | 31 – Normal, unspecified | +| qosControlNotSupported | 63 – Service or option not available, unspecified | +| incompleteAddress | 28 – Invalid number format | +| aliasesInconsistent | 31 – Normal, unspecified | +| routeCallToSCN | 3 – No route to destination | +| exceedsCallCapacity | 41 – Temporary Failure | +| collectDestination | 31 – Normal, unspecified | +| collectPIN | 31 – Normal, unspecified | +| genericDataReason | 31 – Normal, unspecified | +| neededFeatureNotSupported | 31 – Normal, unspecified | +| securityWrongSyncTime | 31 – Normal, unspecified | +| securityReplay | 31 – Normal, unspecified | +| securityWrongGeneralID | 31 – Normal, unspecified | +| securityWrongSendersID | 31 – Normal, unspecified | +| securityIntegrityFailed | 31 – Normal, unspecified | +| securityWrongOID | 31 – Normal, unspecified | +| secuirtyDHMismatch | 31 – Normal, unspecified | +| noRouteToDestination | 3 – No route to destination | +| unallocatedNumber | 1 – Unallocated number | +| noBandwidthAvailable | 34 – No circuit/channel available | + +#### **7.2.2.9 Channel identification** + +Use is for further study; may be used to provide feedback on multiple call attempts. + +#### **7.2.2.10 Connected number** + +Encoded following 5.4.1/Q.951. + +#### **7.2.2.11 Connected sub-address** + +Encoded following 5.4.2/Q.951. + +#### **7.2.2.12 Congestion level** + +Shall not be used. + +#### **7.2.2.13 Date/time** + +Encoded following Figure 4-21/Q.931. + +#### **7.2.2.14 Display** + +Encoded following Figure 4-22/Q.931. The maximum length of the entire information element is 82 octets. + +#### **7.2.2.15 Extended facility information element** + +Any Extended Facility IE that is used to indicate unmodified semantics as defined in Q.95x-series Recommendations shall be encoded following 8.2.4/Q.932. In this case, the Service ADUs shall be formed according to ROSE (uses Rec. ITU-T X.680 (Specification of ASN.1) and Rec. ITU-T X.690 (Specification of basic encoding rules for ASN.1)) as defined in Rec. ITU-T X.229. + +#### **7.2.2.16 Facility** + +In order to signal call redirection specific to H.323 procedures (call forwarding, call transfer, redirecting a call to the MC, or forcing a call to be routed to the gatekeeper) or in case of supplementary service signalling according to Rec. ITU-T H.450, the User-user information element of the Facility message is used. This particular case shall be indicated by coding a Facility IE of length zero; i.e., the Facility information element shall consist of exactly 2 octets as follows: + +- Octet No. 1 (information element identifier) shall be set to "00011100" ("1CH") to indicate the Facility IE. +- Octet No. 2 (information element length) shall be set to "0" to indicate that no further octets belonging to this information element follow. + +In order to indicate call forwarding or call transfer, the Facility IE shall be empty and the **Facility-UUIE** shall indicate in the **alternativeAddress** or the **alternativeAliasAddress** the terminal to which the call is to be redirected. In this case, the **facilityReason** shall be set to **callForwarded**. + +To instruct an endpoint to call a different endpoint because the calling endpoint wishes to join a conference and the called endpoint does not have the MC, the Facility IE would be left empty as well. The **conferenceID** shall indicate the conference to join and the reason in the **Facility-UUIE** shall be **routeCallToMC**. + +Also, to instruct the calling endpoint to signal the called endpoint through the called endpoint's gatekeeper, the Facility IE is left empty. The **conferenceID** in the **Facility-UUIE** shall indicate the conference to join and the reason in the **Facility-UUIE** shall be **routeCallToGatekeeper**. + +Any Facility IE that is used to indicate unmodified semantics as defined in Q.95x-series Recommendations shall be encoded following 8.2.3/Q.932. In this case, the Service ADUs shall be formed according to ROSE (uses Rec. ITU-T X.680 (Specification of ASN.1) and Rec. ITU-T X.690 (Specification of basic encoding rules for ASN.1)) as defined in Rec. ITU-T X.229. + +#### **7.2.2.17 High layer compatibility** + +FFS. + +#### **7.2.2.18 Keypad facility** + +Encoded following Figure 4-24/Q.931. The use of the exclamation point character "!" shall represent a hookflash indication. Endpoints not supporting reception of the hookflash indication shall ignore the "!" if received. + +#### **7.2.2.19 Low layer compatibility** + +FFS. + +#### **7.2.2.20 More data** + +Shall not be used. + +#### **7.2.2.21 Network-specific facilities** + +Shall not be used. + +#### **7.2.2.22 Notification indicator** + +Encoded following 4.5.22/Q.931. + +#### **7.2.2.23 Progress indicator** + +Encoded following Figure 4-29/Q.931 and Table 4-20/Q.931. + +This information element is only required for interfacing an H.323 terminal to an ISDN- and ATM-based terminal where detailed call proceeding information is available. In this case, the gateway shall forward this information to the H.323 terminal. The H.323 end system need not interpret this information element. + +If this information element is generated by an H.323 terminal, the following restrictions apply: + +*Coding standard (octet No. 3, bit 6,7)* + +- Shall indicate "ITU-T" ("00"). + +*Location* + +- Following Table 4-20/Q.931. +- The values "user" ("0000"), "private network serving the local user" ("0001"), and "private network serving the remote user" ("0101") are permitted. + +*Progress description* + +- Following Table 4-20/Q.931. + +#### **7.2.2.24 Redirecting number** + +Encoded following 4.6.7/Q.931. Note that this IE is provided only to facilitate interworking with the SCN, and not to provide a mechanism for H.323-based call diversion services. Call diversion services in H.323 are defined by Rec. ITU-T H.450.3. + +#### **7.2.2.25 Repeat indicator** + +Shall not be used. + +#### **7.2.2.26 Restart indicator** + +Shall not be used. + +#### **7.2.2.27 Segmented message** + +Shall not be used. Note that there is no critical upper limit on the message size in Rec. ITU-T H.323 and this Recommendation. + +#### **7.2.2.28 Sending complete** + +Encoded following Figure 4-33/Q.931. + +No restrictions apply. + +#### **7.2.2.29 Signal** + +Encoded following Figure 4-34/Q.931 and Table 4-24/Q.931. + +No restrictions apply. + +#### 7.2.2.30 Transit network selection + +Shall not be used. + +#### 7.2.2.31 User-user + +Encoded following Figure 4-36/Q.931 and Table 4-26/Q.931, as modified here. + +The User-user information element shall be used by all H.323 entities to convey H.323-related information. Actual user-user information to be exchanged only between the involved terminals is nested in the **user-data** field of the **H323-UserInformation** PDU (to which no restrictions apply). + +The following restrictions apply: + +##### *Length of user-user contents* + +- Shall be 2 octets instead of 1 (as in Figure 4-36/Q.931). + +##### *Protocol discriminator* + +- Shall indicate ITU-T Recs X.680 and X.690 (ASN.1) coded user information ("00000101"). +NOTE – This is taken from the 1998 revision of Rec. ITU-T Q.931 that references the earlier revisions of ASN.1. The correct references to ASN.1 are ITU-T Recs X.680 (syntax) and X.691 (PER). + +##### *User information* + +- Shall contain an ASN.1 structure (H323-UserInformation) that, besides the H.323 relevant information, includes the actual user data as follows. The ASN.1 is encoded using the aligned variant of the packed encoding rules as specified in Rec. ITU-T X.691. + +The **H323-UserInformation** structure contains the **h323-uu-pdu** and **user-data** fields. + +The **h323-uu-pdu** field of the **H323-UserInformation** structure contains the following fields. Note that not all fields in **h323-uu-pdu** are permitted in every message. See the description of each individual message for restrictions. + +- **h323-message-body** – This field contains information specific to a particular H.225.0 signalling message, as described in 7.3 and 7.4. A sender may select a choice of **empty** if there is no need to send the UUIE field (**Facility-UUIE**, etc.) in a particular message, such as when a Facility message is used to transport non-call associated information. Note that beginning with version 4 of this Recommendation, if a message is associated with a particular call, then the sender shall include the UUIE field. This is necessary in order to provide the **callIdentifier** field. +- **nonStandardData** – This field carries information not defined in this Recommendation (for example, proprietary data). +- **h4501SupplementaryService** – This field carries a sequence of H4501SupplementaryService APDUs as defined in Table 3/H.450.1. +- **h245Tunnelling** – This element is set to TRUE if tunnelling of H.245 messages is enabled. Systems compliant with H.225.0 version 4 or higher shall set this element to TRUE if the Fast Connect procedure is used to establish the call. +- **h245Control** – This field carries a sequence of tunnelled H.245 PDUs. Each octet string shall contain exactly one H.245 PDU. +- **nonStandardControl** – This field contains control information not defined in this Recommendation (for example, proprietary control information). +- **callLinkage** – The contents of this field are typically controlled by a call linkage service. For the procedures and semantics of this field refer to Rec. ITU-T H.323. + +- **tunnelledSignallingMessage** – A tunnelled entire signalling message in its native format to support additional end-to-end call control signalling. The **tunnelledProtocolID** field identifies the protocol being tunnelled. The **messageContent** field is a sequence of actual entire tunnelled messages in their native binary format; this allows aggregation of tunnelled messages in one H.225.0 message. If the **tunnellingRequired** field is present, the call shall only proceed if tunnelling is supported. +- **provisionalRespToH245Tunnelling** – This flag is used to signal that the called entity has not yet decided whether H.245 tunnelling is applicable for this call. If present, the **h245Tunnelling** flag shall be ignored by the receiving entity. +- **stimulusControl** – This field is reserved for future use by the ITU-T for a stimulus-based protocol. +- **genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through H.225.0. + +The **user-data** field of the **H323-UserInformation** structure contains the following fields: + +- protocol-discriminator – This field is encoded following Table 4-26/Q.931. +- user-information – This field is encoded following 4.5.30/Q.931. + +## 7.3 Q.931 based H.225.0 call signalling message details + +Note that the lengths of the information elements specified in the tables below, where "\*" denotes an undefined maximum length, refer to messages that are generated by H.323 terminals only. The size of the User-user information element, not explicitly shown, is understood as the size of the PER encoded **H323-UserInformation sequence**. The total size of **H323-UserInformation** is limited to 65 536 octets. Regardless of the specified sizes, messages forwarded from the SCN side may have different (larger) sizes. + +Also note that an information element specified below as mandatory, optional, or forbidden refers only to whether or not H.323 terminals may originate such information elements. + +### 7.3.1 Alerting + +This message may be sent by the called user to indicate that called user alerting has been initiated. In everyday terms, the "phone is ringing". + +Follow Table 3-2/Q.931 (1998 version) as modified below in Table 7. + +**Table 7 – Alerting** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference | M | 3 | +| Message type | M | 1 | +| Bearer capability | O | 5-6 | +| Extended facility | O | 8-* | +| Channel identification | FFS | NA | +| Facility | O | 8-* | +| Progress indicator | O | 2-4 | +| Notification indicator | O | 2-* | +| Display | O | 2-82 | + +**Table 7 – Alerting** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|--------------------------|------------------------|-------------------| +| Signal | O | 2-3 | +| High layer compatibility | FFS | NA | +| User-user | M | * | + +The User-user information element contains the Alerting-UUIE defined in the H.225.0 Message Syntax. The **Alerting-UUIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**destinationInfo** – Contains an **EndpointType** to allow the caller to determine whether the call involves a gateway or not. + +**h245Address** – This is a specific transport address on which the called endpoint or gatekeeper handling the call would like to establish H.245 signalling. This address may also be sent in Call Proceeding, Progress, Connect, or Facility. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**h245SecurityMode** – An H.323 entity that receives a Setup message with the **h245SecurityCapability** set shall respond with the corresponding, acceptable **h245SecurityMode** in the Call Proceeding, Alerting, Progress, or Connect. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**fastStart** – Used only in the fast connect procedure, **fastStart** supports the signalling needed to open a logical channel. This uses the **OpenLogicalChannel** structure defined in Rec. ITU-T H.245, but the sender of this indicates the modes it prefers to receive and transmit, and the transport addresses where it expects to receive media streams. + +**multipleCalls** – If TRUE, this indicates that the sender of the message is capable of signalling multiple calls over a single call signalling connection. + +**maintainConnection** – If TRUE, this indicates that the sender of the message is capable of supporting a signalling connection when no calls are currently signalled over the connection. + +**alertingAddress** – Contains the alias addresses for the alerting party. + +**presentationIndicator** – Indicates whether presentation of the **alertingAddress** should be allowed or restricted. + +**screeningIndicator** – Indicates whether the **alertingAddress** was provided by the endpoint or network (gatekeeper), and whether the **alertingAddress** was screened by a gatekeeper. + +**fastConnectRefused** – A called endpoint should return this element in any message up to and including the Connect message when establishing a call to indicate that it refuses the Fast Connect procedure. + +**serviceControl** – Contains service-specific data, or references to it, that may be used as part of the setup procedure by the calling endpoint (e.g., a menu of options for call diversion) as described, for example, in Annex K/H.323. + +**capacity** – This field indicates the sending endpoint's available call capacity at this point in time, assuming that this Alerting message represents an active call. When sending this field, the endpoint shall include the **currentCallCapacity** element. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**displayName** – Provides an ordered list of names, along with language tags, that identify the called or calling user. The user's most preferred name and language should be indicated first, followed by alternative representations using the same or different language tags. The receiving user may select any of the offered names for display according to local preference. When the **displayName** field is present, it shall take precedence over the **Display IE**. However, the **Display IE** should still be provided for interworking with legacy systems. + +### 7.3.2 Call proceeding + +This message may be sent by the called user to indicate that requested call establishment has been initiated and no more call establishment information will be accepted. See Table 8. + +**Table 8 – Call proceeding** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|--------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference | M | 3 | +| Message type | M | 1 | +| Bearer capability | O | 5-6 | +| Extended facility | O | 8-* | +| Channel identification | FFS | NA | +| Facility | O | 8-* | +| Progress indicator | O | 2-4 | +| Notification indicator | O | 2-* | +| Display | O | 2-82 | +| High layer compatibility | FFS | NA | +| User-user | M | * | + +The User-user information element contains the **CallProceeding-UUIE** defined in the H.225.0 Message Syntax. The **CallProceeding-UUIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**destinationInfo** – Contains an **EndpointType** to allow the caller to determine whether the call involves a gateway or not. + +**h245Address** – This is a specific transport address on which the called endpoint or gatekeeper handling the call would like to establish H.245 signalling. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**h245SecurityMode** – An H.323 entity that receives a Setup message with the **h245SecurityCapability** set shall respond with the corresponding, acceptable **h245SecurityMode** in the Call Proceeding, Alerting, Progress, or Connect. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**fastStart** – Used only in the fast connect procedure, **fastStart** supports the signalling needed to open a logical channel. This uses the **OpenLogicalChannel** structure defined in Rec. ITU-T H.245, but the sender of this indicates the modes it prefers to receive and transmit, and the transport addresses where it expects to receive media streams. + +**multipleCalls** – If TRUE, this indicates that the sender of the message is capable of signalling multiple calls over a single call signalling connection. + +**maintainConnection** – If TRUE, this indicates that the sender of the message is capable of supporting a signalling connection when no calls are currently signalled over the connection. + +**fastConnectRefused** – A called endpoint should return this element in any message up to and including the Connect message when establishing a call to indicate that it refuses the Fast Connect procedure. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +### 7.3.3 Connect + +This message shall be sent by the called entity to the calling entity (gatekeeper, gateway, or calling terminal) to indicate acceptance of the call by the called entity. Follow Table 3-4/Q.931, as modified in Table 9 below. + +**Table 9 – Connect** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|--------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference | M | 3 | +| Message type | M | 1 | +| Bearer capability | O | 5-6 | +| Extended facility | O | 8-* | +| Channel identification | FFS | NA | +| Facility | O | 8-* | +| Progress indicator | O | 2-4 | +| Notification indicator | O | 2-* | +| Display | O | 2-82 | +| Date/Time | O | 8 | +| Connected Number | O | 2-* | +| Connected Subaddress | O | 2-23 | +| Low layer compatibility | FFS | NA | +| High layer compatibility | FFS | NA | +| User-user | M | * | + +The User-user information element contains the **Connect-UUIE** defined in the H.225.0 Message Syntax. The **Connect-UUIE** includes the following: + +**protocolIdentifier** – Set by the called endpoint to the version of H.225.0 supported. + +**h245Address** – This is a specific transport address on which the called endpoint or gatekeeper handling the call would like to establish H.245 signalling. This address shall be sent if sent earlier in Alerting, Progress, Call Proceeding, or Facility. + +**destinationInfo** – Contains an **EndpointType** to allow the caller to determine whether the call involves a gateway or not. + +**conferenceID** – Will contain a unique number to allow the conference to be uniquely identified from all others as received in the Setup. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**h245SecurityMode** – An H.323 entity that receives a Setup message with the **h245SecurityCapability** set shall respond with the corresponding, acceptable **h245SecurityMode** in the Call Proceeding, Alerting, Progress, or Connect. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**fastStart** – Used only in the fast connect procedure, **fastStart** supports the signalling needed to open a logical channel. This uses the **OpenLogicalChannel** structure defined in Rec. ITU-T H.245, but the sender of this indicates the modes it prefers to receive and transmit, and the transport addresses where it expects to receive media streams. + +**multipleCalls** – If TRUE, this indicates that the sender of the message is capable of signalling multiple calls over a single call signalling connection. + +**maintainConnection** – If TRUE, this indicates that the sender of the message is capable of supporting a signalling connection when no calls are currently signalled over the connection. + +**language** – Indicates the language(s) the user will use or in which the user would prefer to receive announcements and prompts. The field contains one or more RFC 5646 compliant language tags. + +**connectedAddress** – Contains the alias addresses for the connected (answering) party; the dialled digit string of the connected party is in the Connected Number IE. + +**presentationIndicator** – Indicates whether presentation of the **connectedAddress** should be allowed or restricted. If both **presentationIndicator** and the presentation indicator of the Connected Number IE are present and are in conflict, the presentation indicator of the Connected Number IE shall be used. + +**screeningIndicator** – Indicates whether the **connectedAddress** was provided by the endpoint or network (gatekeeper), and whether the **connectedAddress** was screened by a gatekeeper. If both **screeningIndicator** and the screening indicator of the Connected Number IE are present and are in conflict, the screening indicator of the Connected Number IE shall be used. + +**fastConnectRefused** – A called endpoint should return this element in any message up to and including the Connect message when establishing a call to indicate that it refuses the Fast Connect procedure. + +**serviceControl** – Contains service-specific data, or references to it, that could be used by an endpoint or gateway (e.g., for displaying a menu of options to a caller) as described, for example, in Annex K/H.323. + +**capacity** – This field indicates the sending endpoint's available call capacity at this point in time, assuming that this Connect message represents an active call. When sending this field, the endpoint shall include the **currentCallCapacity** element. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**displayName** – Provides an ordered list of names, along with language tags, that identify the called or calling user. The user's most preferred name and language should be indicated first, followed by alternative representations using the same or different language tags. The receiving user may select + +any of the offered names for display according to local preference. When the *displayName* field is present, it shall take precedence over the *Display* IE. However, the *Display* IE should still be provided for interworking with legacy systems. + +### 7.3.4 Connect acknowledgement + +This message shall not be sent. + +### 7.3.5 Disconnect + +This message shall not be sent by an H.323 entity. + +The contents and semantics of a *Disconnect* message received from the network are defined in Table 3-6/Q.931 and in 10.5 of ISO/IEC 11582. + +### 7.3.6 Information + +This message may be sent to provide additional information. It may be used to provide information for call establishment (e.g., overlap sending) or miscellaneous call-related information. It may be used to deliver proprietary features. + +This message may be sent by an H.323 entity. + +This message follows Table 3-7/Q.931 with the following modifications (see Table 10). + +**Table 10 – Information message content** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference | M | 3 | +| Message type | M | 1 | +| Sending complete | O | 1 | +| Display | O | 2-82 | +| Keypad facility | O | 2-34 | +| Signal | O | 2-3 | +| Called party number | O (Note) | 2-35 | +| User-user | M | * | +| NOTE – The Called Party Number IE will be used to carry numbers from a Private Numbering Plan when performing overlapped sending according to 8.1.12/H.323. | | | + +The *User-user* information element contains the **Information-UUIE** defined in the H.225.0 Message Syntax. The **Information-UUIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**fastStart** – This field shall not be included, and shall be ignored upon receipt. + +**fastConnectRefused** – This field shall not be included, and shall be ignored upon receipt. + +**circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. + +### 7.3.7 Progress + +This message may be sent by an H.323 gateway to indicate the progress of a call in the event of interworking with SCN. This message may also be sent by an H.323 endpoint before the Connect message, depending on supplementary service interaction. + +Follow Table 3-9/Q.931 and 10.10 of ISO/IEC 11582 as modified in Table 11. + +**Table 11 – Progress** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|--------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference | M | 3 | +| Message type | M | 1 | +| Bearer capability | O | 5-6 | +| Cause | O | 2-32 | +| Extended facility | O | 8-* | +| Channel identification | FFS | NA | +| Facility | O | 8-* | +| Progress indicator | M | 2-4 | +| Notification indicator | O | 2-* | +| Display | O | 2-82 | +| High layer compatibility | FFS | NA | +| User-user | M | * | + +The User-user information element contains the **Progress-UUIE** defined in the H.225.0 Message Syntax. The **Progress-UUIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**destinationInfo** – Contains an **EndpointType** to allow the caller to determine whether the call involves a gateway or not. + +**h245Address** – This is a specific transport address on which the called endpoint or gatekeeper handling the call would like to establish H.245 signalling. This address shall be sent if sent earlier in Call Proceeding, Alerting, Connect, or Facility. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**h245SecurityMode** – An H.323 entity that receives a Setup message with the **h245SecurityCapability** set shall respond with the corresponding, acceptable **h245SecurityMode** in the Call Proceeding, Alerting, Progress, or Connect. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**fastStart** – Used only in the fast connect procedure, **fastStart** supports the signalling needed to open a logical channel. This uses the **OpenLogicalChannel** structure defined in Rec. ITU-T H.245, but the sender of this indicates the modes it prefers to receive and transmit, and the transport addresses where it expects to receive media streams. + +**multipleCalls** – If TRUE, this indicates that the sender of the message is capable of signalling multiple calls over a single call signalling connection. + +**maintainConnection** – If TRUE, this indicates that the sender of the message is capable of supporting a signalling connection when no calls are currently signalled over the connection. + +**fastConnectRefused** – A called endpoint should return this element in any message up to and including the Connect message when establishing a call to indicate that it refuses the Fast Connect procedure. + +### 7.3.8 Release + +This message shall not be sent by an H.323 entity. + +The contents and semantics of a Release message received are defined in Table 3-10/Q.931 and in 10.5 of ISO/IEC 11582. + +### 7.3.9 Release complete + +This message shall be sent by a terminal to indicate release of the call. Afterwards, the Call Reference Value (CRV) is available for reuse. + +The disconnect/release/release complete sequence is not used since its primary purpose is to indicate the completion of release of circuit-switched resources. As this does not apply to the packet-based network environment, the single step method of sending only Release Complete is used. + +Follow Table 3-11/Q.931. Table 12 modifications apply. + +**Table 12 – Release complete** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|----------------------------------------------------------------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference | M | 3 | +| Message type | M | 1 | +| Cause | CM (Note) | 2-32 | +| Facility | O | 8-* | +| Notification indicator | O | 2-* | +| Display | O | 2-82 | +| Signal | O | 2-3 | +| User-user | M | * | +| NOTE – Either the Cause IE or the ReleaseCompleteReason shall be present. | | | + +If this message is sent in response to a Facility message with an empty Facility IE, the **ReleaseCompleteReason** shall be set to **facilityCallDeflection**. + +If this message is forwarded from a SCN by a gateway, the cause value shall be set as specified in Rec. ITU-T Q.931. + +The User-user information element contains the **ReleaseComplete-UUIE** defined in the H.225.0 Message Syntax. The **ReleaseComplete-UUIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**reason** – More information on why the call was released. A reason of **genericDataReason** indicates that the call was cleared as a result of a generic element or feature; in this case, additional information may be specified in the **genericData** field of the **h323-uu-pdu** of this message. A reason of **neededFeatureNotSupported** indicates that a feature required by one entity is not supported by + +another. A reason of **tunnelledSignallingRejected** is sent if the call is cleared because the sender does not allow tunnelled non-H.323 signalling and tunnelling is required in order for the call to succeed. A reason of **hopCountExceeded** indicates that the call was rejected because the **hopCount** value reached 0 and hence the call cannot proceed further. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**busyAddress** – Contains the alias addresses for the busy party. + +**presentationIndicator** – Indicates whether presentation of the **busyAddress** should be allowed or restricted. + +**screeningIndicator** – Indicates whether the **busyAddress** was provided by the endpoint or network (gatekeeper), and whether the **busyAddress** was screened by a gatekeeper. + +**capacity** – Indicates the sending endpoint's available call capacity after the call referenced in this Release Complete message has been released. When sending this field, the endpoint shall include the **currentCallCapacity** element. + +**serviceControl** – Contains service-specific data, or references to it, for post-call services (e.g., an error message or announcement) as described, for example, in Annex K/H.323. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**destinationInfo** – Contains an **EndpointType** to allow the caller to determine whether the call involves a gateway or not. + +**displayName** – Provides an ordered list of names, along with language tags, that identify the called or calling user. The user's most preferred name and language should be indicated first, followed by alternative representations using the same or different language tags. The receiving user may select any of the offered names for display according to local preference. When the **displayName** field is present, it shall take precedence over the Display IE. However, the Display IE should still be provided for interworking with legacy systems. + +### 7.3.10 Setup + +This message shall be sent by a calling H.323 entity to indicate its desire to set up a connection to the called entity. + +Follow Table 3-15/Q.931 as modified in Table 13. + +**Table 13 – Setup** + +| Information element | H.225.0 status (M/F/O/CM) | Length in H.225.0 | +|-----------------------------|---------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference | M (Note 2) | 3 | +| Message type | M | 1 | +| Sending complete | O | 1 | +| Repeat indicator | F | NA | +| Bearer capability | M | 5-6 | +| Extended facility | O | 8-* | +| Channel identification | FFS | NA | +| Facility | O | 8-* | +| Progress indicator | O | 2-4 | +| Network specific facilities | F | NA | +| Notification indicator | O | 2-* | +| Display | O | 2-82 | +| Keypad facility | O | 2-34 | +| Signal | O | 2-3 | +| Calling party number | O | 2-131 | +| Calling party subaddress | CM (Note 1) | NA | +| Called party number | O | 2-131 | +| Called party subaddress | CM (Note 1) | NA | +| Redirecting Number | O | 2-* | +| Transit network selection | F | NA | +| Low layer compatibility | FFS | NA | +| High layer compatibility | FFS | NA | +| User-user | M | * | + +NOTE 1 – Subaddresses are needed for some SCN call scenarios; they should not be used for packet-based network side only calls. +NOTE 2 – If an ARQ was previously sent, the CRV used here shall be the same. + +The User-user information element contains the **Setup-UUIE** defined in the H.225.0 Message Syntax. The **Setup-UUIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**h245Address** – This is a specific transport address on which the calling endpoint or gatekeeper handling the call would like to establish the H.245 signalling. This should only be provided by the sender if it is capable of handling H.245 procedures before receiving a Connect on the Call Signalling channel. + +**sourceAddress** – Contains the alias addresses of the source. The primary address shall be first. Note that the E.164 number of the source, if any, shall be contained within the Calling Party Number information element. + +**sourceInfo** – Contains an **EndpointType** to allow the called party to determine whether the call involves a gateway or not. + +**destinationAddress** – This is the address to which the endpoint wishes to be connected. The primary address shall be first. When calling an endpoint using only a dialled digit string, this address shall be placed in the H.225.0 call signalling message Called Party Number IE. The **destinationAddress**, if available, shall be included in the Setup message by terminals compliant with version 2 or higher of this Recommendation. + +**destCallSignalAddress** – Needed to inform the gatekeeper of the destination terminal's call signalling transport address; redundant in the direct terminal-to-terminal case. In all cases where the information is available to the sender of the Setup message, this field shall be filled in. + +**destExtraCallInfo** – Needed to make possible additional channel calls, i.e., for a $2 \times 64$ kbit/s call on the SCN side. Shall only contain dialled digit strings, E.164 numbers, or Private numbers and shall not contain the number of the initial channel. (See Note.) + +**destExtraCRV** – CRVs for the additional SCN calls specified by **destExtraCallInfo**. Their use is for further study. They can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**activeMC** – Indicates that the calling endpoint is under the influence of an active MC. + +**conferenceID** – Unique conference identifier. + +**conferenceGoal**: + +- **create** – Start a new conference. +- **invite** – Invite a party into an existing conference. +- **join** – Join an existing conference. +- **capability-negotiation** – Negotiate capabilities for a later loosely coupled conference. +- **callIndependentSupplementaryService** – Transport of supplementary services APDUs in a non-call related manner. + +**callServices** – Provides information on support of optional Q-series protocols to gatekeeper and called terminal. + +**callType** – Using this value, called party's gatekeeper can attempt to determine "real" bandwidth usage. The default value is **pointToPoint** for all calls; it should be recognized that the call type may change dynamically during the call and that the final call type may not be known when the Setup is sent. + +**sourceCallSignalAddress** – Contains the transport address for the source; this value shall be used in the ARQ message by the receiver of the Setup. In all cases where the information is available to the sender of the Setup message, this field shall be filled in. The value of **sourceCallSignalAddress** shall be equal to the value that was used in the ARQ by the sender of the Setup, and shall be echoed by the endpoint receiving the Setup in its ARQ. + +**remoteExtensionAddress** – Contains the alias address of a called endpoint in cases where this information is needed to traverse multiple Gateways. In all cases where the information is available to the sender of the Setup message, this field shall be filled in. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**h245SecurityCapability** – A set of capabilities the sender can use to secure the H.245 channel. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**fastStart** – Used only in the fast connect procedure, **fastStart** supports the signalling needed to open a logical channel. This uses the **OpenLogicalChannel** structure defined in Rec. ITU-T H.245, but the sender of this indicates the modes it prefers to receive and transmit, and the transport addresses where it expects to receive media streams. + +**mediaWaitForConnect** – If TRUE, indicates that the recipient of the Setup message shall not transmit media until sending the Connect message. + +**canOverlapSend** – If TRUE, indicates that the sender of Setup shall support overlap sending. + +**endpointIdentifier** – This is an endpoint identifier that was assigned to the terminal in the RCF message. This field shall be present when the Setup is sent towards the gatekeeper where the endpoint is registered, and shall not be present when the Setup is sent to any other entity. + +**multipleCalls** – If TRUE, this indicates that the sender of the message is capable of signalling multiple calls over a single call signalling connection. + +**maintainConnection** – If TRUE, this indicates that the sender of the message is capable of supporting a signalling connection when no calls are currently signalled over the connection. + +**ConnectionParameters** – Allow specification of parameters needed by gateways that provide multiple connection types and/or aggregation (for example, an H.323/H.320 gateway): + +- **scnConnectionType** – Provides information to a gateway on the type of individual connection used to produce the entire SCN call. Endpoints or gatekeepers should fill in this field if the information is available to them. If the option "multirate" is indicated, then the information transfer rate octet in the bearer capability shall also indicate "multirate" and the rate multiplier octet shall indicate the number of connections. In all other cases, if the **scnConnectionType** field is present, it overrides any indication about the individual connection type contained in the transfer rate (octet #4) and rate multiplier (octet #4.1) of the bearer capability IE. +- **numberOfSCNConnections** – Indicates the number of connections of type **scnConnectionType** which are aggregated together to produce the SCN call. This field, when multiplied by the bandwidth of the individual connection specified in **scnConnectionType**, denotes the bandwidth for the entire call on the SCN. Endpoints or gatekeepers should fill in this field if the information is available to them. Note that if the **scnConnectionType** is set to unknown, then a unit of bandwidth of 64 kbit/s is assumed. If both this field and the **scnConnectionType** fields are present, then the total bandwidth indicated shall agree with the total SCN bandwidth indicated by the transfer rate (octet #4) and rate multiplier (octet #4.1) of the Bearer capability IE. +- **scnConnectionAggregation** – Indicates how the individual connections are aggregated together to produce the complete SCN call. Endpoints or gatekeepers should fill in this field if the information is available to them. The default option, to be used when the actual aggregation mechanism is unknown, is "auto". Where bonding is known to be used, but the precise bonding mode is unknown, then the option "bonded-mode1" should be used. + +**language** – Indicates the language(s) the user will use or in which the user would prefer to receive announcements and prompts. The field contains one or more RFC 5646 compliant language tags. + +**presentationIndicator** – Indicates whether presentation of the **sourceAddress** should be allowed or restricted. If both **presentationIndicator** and the presentation indicator of the Calling Party Number IE are present and are in conflict, the presentation indicator of the Calling Party Number IE shall be used. + +**screeningIndicator** – Indicates whether the **sourceAddress** was provided by the endpoint or network (gatekeeper), and whether the **sourceAddress** was screened by a gatekeeper. If both **screeningIndicator** and the screening indicator of the Calling Party Number IE are present and are in conflict, the screening indicator of the Calling Party Number IE shall be used. + +**serviceControl** – Contains service-specific data, or references to it, that may be used as part of the setup procedure at the called endpoint (e.g., an image or icon to be displayed while alerting) as described, for example, in Annex K/H.323. + +**symmetricOperationRequired** – If present, indicates that the called endpoint must select identical transmit and receive audio capabilities. This element shall not be included unless the **fastStart** element is also included. + +**capacity** – This field indicates the sending endpoint's available call capacity at this point in time, assuming that this Setup message represents an active call. When sending this field, the endpoint shall include the **currentCallCapacity** element. + +**circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. + +**desiredProtocols** – Identifies the type of protocols, in order of preference, the originating endpoint desires for its call (e.g., voice or fax). A resolving entity may use this field to locate an endpoint that also supports the protocol, giving consideration to the order of preference. + +**neededFeatures** – This field specifies a list of generic features that are required in order for the call to succeed. + +**desiredFeatures** – This field specifies a list of generic features that are preferred for the call, but are not required in order for it to succeed. + +**supportedFeatures** – This field specifies a list of generic features that the sender support and has chosen to declare. + +**parallelH245Control** – This field carries a sequence of tunnelled H.245 Terminal Capability Set PDUs and optionally Master Slave Determination PDUs. Each octet string shall contain exactly one H.245 PDU. + +**additionalSourceAddresses** – This field carries a sequence of alias addresses that correspond to the second and subsequent Calling Party Number IEs in non-H.323 networks. For example, in ISDN, multiple calling party numbers may be present to support the "Two Calling party number information elements delivery option" defined in Annex A/Q.951. + +**hopCount** – This field specifies an integer value to indicate the number of hops the call signalling can traverse further. + +**displayName** – Provides an ordered list of names, along with language tags, that identify the called or calling user. The user's most preferred name and language should be indicated first, followed by alternative representations using the same or different language tags. The receiving user may select any of the offered names for display according to local preference. When the **displayName** field is present, it shall take precedence over the **Display** IE. However, the **Display** IE should still be provided for interworking with legacy systems. + +NOTE – If the **destExtraCallInfo** is present, a CRV for each call to be made may be supplied in **destExtraCRV**. These CRVs will be used to identify any response to each call launched. These procedures are for further study. If the **destExtraCRV** field is not present, a gateway shall aggregate all call information into a single response, with the effect that if one call fails on the SCN side, the entire call is treated as a failure. + +### 7.3.11 Setup acknowledge + +This message may be sent by an H.323 entity. However, it may be forwarded from the network via a gateway. Processing on receipt is optional, but an entity that indicates **canOverlapSend** in Setup shall support Setup Acknowledge. + +The contents and semantics of a Setup Acknowledge message received from the network are defined in Table 3-16/Q.931, as modified in Table 14. + +**Table 14 – Setup acknowledge** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|-------------------------------------------------------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference | M | 3 | +| Message type | M | 1 | +| Channel identification | FFS | NA | +| Display | O | 2-82 | +| User-user | M (Note) | * | +| NOTE – This element was not present in H.225.0 prior to H.225.0 (2000). | | | + +For backward compatibility with systems prior to H.225.0 version 4, the sender of this message shall not include the **h4501SupplementaryService** or the **h245Control** field in the **h323-message-body** field of the User-user information element. + +The User-user information element contains the **SetupAcknowledge-UIE** defined in the H.225.0 Message Syntax. The **SetupAcknowledge-UIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint, which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +### 7.3.12 Status + +The Status message shall be used to respond to an unknown call signalling message or to a Status Inquiry message. + +Follow Table 3-17/Q.931 as modified in Table 15. + +**Table 15 – Status** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|----------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference (Note 1) | M | 3 | +| Message type | M | 1 | +| Cause | M | 4-32 | +| Call State | M | 3 | +| Display | O | 2-82 | +| User-user | M (Note 2) | * | +| NOTE 1 – This message may carry the global call reference if the message applies to all calls on a connection carrying multiple calls. | | | +| NOTE 2 – This element was not present in H.225.0 prior to H.225.0 (2000). | | | + +For backward compatibility with systems prior to H.225.0 version 4, the sender of this message shall not include the **h4501SupplementaryService** or the **h245Control** field in the **h323-message-body** field of the User-user information element. + +The User-user information element contains the **Status-UUIE** defined in the H.225.0 Message Syntax. The **Status-UUIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint, which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +### 7.3.13 Status inquiry + +The Status Inquiry message may be used to request call status as described in 8.4.2/H.323. + +Follow Table 3-18/Q.931 as modified by Table 16. + +**Table 16 – Status inquiry** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|-------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference (Note 1) | M | 3 | +| Message type | M | 1 | +| Display | O | 2-82 | +| User-user | M (Note 2) | * | + +NOTE 1 – This message may carry the global call reference if the message applies to all calls on a connection carrying multiple calls. +NOTE 2 – This element was not present in H.225.0 prior to H.225.0 (2000). + +For backward compatibility with systems prior to H.225.0 version 4, the sender of this message shall not include the **h4501SupplementaryService** or the **h245Control** field in the **h323-message-body** field of the User-user information element. + +The User-user information element contains the **StatusInquiry-UUIE** defined in the H.225.0 Message Syntax. The **StatusInquiry-UUIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +## 7.4 Q.932-based H.225.0 call signalling message details + +The messages defined in the following are derived from ITU-T Recs Q.932 and H.450. Refer to ITU-T Recs Q.932 and H.450 for further details. + +Note that the lengths of the information elements specified in the tables below, where "\*" denotes an undefined maximum length, refer to messages that are generated by H.323 terminals only. The size of the User-user information element, not explicitly shown, is understood as the size of the PER-encoded H323-UserInformation sequence. The total size of H323-UserInformation is limited to 65 536 octets. Regardless of the specified sizes, messages forwarded from the SCN side may have different (larger) sizes. + +Also note that an information element specified below as mandatory, optional or forbidden refers only to whether or not H.323 terminals may originate such information elements. + +### 7.4.1 Facility + +The Facility message shall be used to provide information on where a call should be directed (**FacilityReason = routeCallToMC**), or for an endpoint to indicate that the incoming call must go through a gatekeeper (**FacilityReason = routeCallToGatekeeper**). + +In order to signal call redirection specific to H.323 procedures, the User-user information element of the Facility message is used. This particular case shall be indicated by coding a Facility IE of length zero. In this case, the Facility information element shall consist of exactly 2 octets. An H.323 entity shall handle the empty (H.323-specific) Facility IE properly and shall be capable of skipping other Facility IEs that it does not understand. + +The Facility message may be used to request or acknowledge a supplementary service according to H.450.x-series Recommendations. For that reason, one or more H.450 Supplementary Service APDUs shall be carried within the User-user information element of the Facility message. The H.450 Supplementary Service APDUs shall be coded according to clause 8/H.450.1. The Facility information element shall be contained with length zero. Note that a Facility message of H.225.0 version 2 or version 3 that carries only H.450 Supplementary Service APDUs might choose not to include the Facility-UUIE, but instead use the "**empty" h323-message-body** choice. In this case, a Facility message would not have a **callIdentifier** field in it. In H.225.0 version 4 and higher, a sender shall include a Facility-UUIE carrying a **callIdentifier** field in every call-associated Facility message, and shall set the **reason** field value to **transportedInformation**. + +If a Facility IE carrying semantics of Rec. ITU-T Q.932 and encoded as defined in Rec. ITU-T Q.932 and Rec. ITU-T Q.95x is present, it shall consist of at least 8 octets as required by Table 7-2/Q.932. The use of Facility IEs of that type is for further study. + +The Facility message may be used by an endpoint or gatekeeper to request the recipient to establish an H.245 channel between the two entities (**FacilityReason = startH245**). + +The Facility message may be used by an endpoint or gatekeeper to send a new set of tokens in the **tokens** and/or **cryptoTokens** field of the Facility message (**FacilityReason = newTokens**). This may be useful, for example, for applications in which tokens are used to allow some action to take place only for a limited amount of time. + +Follow 7.1.1/Q.932 and 10.8 of ISO/IEC 11582, as modified in Table 17. + +**Table 17 – Facility** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|-------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference (Note 1) | M | 3 | +| Message type | M | 1 | +| Extended facility | O (Note 2) | 8-* | +| Facility | O (Note 2) | 2 or 8-* | +| Notification indicator | O | 2-* | +| Display | O | 2-82 | +| Calling Party Number | F | NA | +| Called Party Number | F | NA | +| User-user | M | * | + +NOTE 1 – This message may carry the global call reference if the message applies to all calls on a connection carrying multiple calls. +NOTE 2 – If the Facility message is used for carrying Q.95x supplementary service signalling, one of either the Facility or Extended Facility information elements is required. If the Facility message is used for Supplementary Service control according to H.450.x-series Recommendations, or if the Facility message is used for the reroute to MC/GK functions, then the zero-length Facility information element is required. + +#### *Coding of Message Type information element* + +The message type information element of the Facility message shall be coded "0110 0010". + +The User-user information element contains the Facility-UUIE defined in the H.225.0 Message Syntax. The Facility-UUIE includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**alternativeAddress** – This is a specific transport address to which the calling party should direct the call; if present, **alternativeAliasAddress** is not needed. + +**alternativeAliasAddress** – Contains aliases that can be used to redirect the call; if an alias is provided, **alternativeAddress** is not needed. + +**conferenceID** – Unique conference identifier; not needed if the **conferences** field is used. + +**reason** – More information about the Facility message. A reason of **featureSetUpdate** indicates that the purpose of the message is to update **featureSet** information that was sent previously. A **reason** of **forwardedElements** indicates that the purpose of the message is to forward elements of another message in case that message cannot be sent, as would be the case when a routing gatekeeper receives a Call Proceeding message after it has already sent Call Proceeding. A reason of **transportedInformation** indicates that the purpose of the message is to transport higher-layer information, for example in the **h4501SupplementaryService** field; the **Facility-UUIE** in this case is included only in order to provide the **callIdentifier**. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**destExtraCallInfo** – Needed to make possible additional channel calls, i.e., for a $2 \times 64$ kbit/s call on the SCN side. Shall only contain dialled digit strings, E.164 numbers, or Private numbers and shall not contain the number of the initial channel. + +**remoteExtensionAddress** – Contains the alias address of a called endpoint in cases where this information is needed to traverse multiple Gateways. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**conferences** – One or more conferences that may be joined. + +**h245Address** – This is a specific transport address on which the endpoint or gatekeeper sending this facility would like the recipient to establish H.245 signalling. Note that this field may be present when an intermediate signalling entity is conveying the **h245Address** field from a Call Proceeding message. The receiving entity is instructed to initiate H.245 procedures only when **reason** is **startH245**. + +**fastStart** – Used only in the fast connect procedure, **fastStart** supports the signalling needed to open a logical channel. This uses the **OpenLogicalChannel** structure defined in Rec. ITU-T H.245, but the sender of this indicates the modes it prefers to receive and transmit, and the transport addresses where it expects to receive media streams. This field is present in a Facility message when a routing gatekeeper received it in a Call Proceeding message from the called user and is forwarding the information to the calling user. This field shall not be included by an endpoint. + +**multipleCalls** – If TRUE, this indicates that the sender of the message is capable of signalling multiple calls over a single call signalling connection. + +**maintainConnection** – If TRUE, this indicates that the sender of the message is capable of supporting a signalling connection when no calls are currently signalled over the connection. + +**fastConnectRefused** – A called endpoint should return this element in any message up to and including the Connect message when establishing a call to indicate that it refuses the Fast Connect procedure. This field is present in a Facility message when a routing gatekeeper received it in a Call Proceeding message from the called user and is forwarding the information to the calling user. + +**serviceControl** – Contains service-specific data, or references to it, that could be used by an endpoint or gateway (e.g., for displaying a menu of options to a participant in a call), as described, for example, in Annex K/H.323. + +**circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**destinationInfo** – Contains an **EndpointType** to allow the caller to determine whether the call involves a gateway or not. This field is present in a Facility message when a routing gatekeeper received it in a Call Proceeding message from the called user and is forwarding the information to the calling user. This field did not exist in the Facility message prior to H.225.0 version 4. + +**h245SecurityMode** – An H.323 entity that receives a Setup message with the **h245SecurityCapability** set responds with the corresponding, acceptable **h245SecurityMode** in the Call Proceeding, Alerting, Progress, or Connect. This field is present in a Facility message when a routing gatekeeper received it in a Call Proceeding message from the called user and is forwarding the information to the calling user. This field did not exist in the Facility message prior to H.225.0 version 4. + +### 7.4.2 Notify + +This message may be sent by an H.323 entity. Processing on receipt is optional. + +Follow Table 3-8/Q.931 as modified in Table 18. + +**Table 18 – Notify** + +| Information element | H.225.0 status (M/F/O) | Length in H.225.0 | +|----------------------------------------------------------------|------------------------|-------------------| +| Protocol discriminator | M | 1 | +| Call reference | M | 3 | +| Message type | M | 1 | +| Bearer capability | O (Note) | 5-6 | +| Notification indicator | M | 3 | +| Display | O | 2-82 | +| Connected Number | O | 2-* | +| User-user | M | * | +| NOTE – Included to indicate a change of the bearer capability. | | | + +For backward compatibility with systems prior to H.225.0 version 4, the sender of this message shall not include the **h4501SupplementaryService** or the **h245Control** field in the **h323-message-body** field of the User-user information element. + +The User-user information element contains the **Notify-UUIE** defined in the H.225.0 Message Syntax. The **Notify-UUIE** includes the following: + +**protocolIdentifier** – Set to the version of H.225.0 supported. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**connectedAddress** – Contains the alias addresses for the connected party; the dialled digit string of the connected party is in the Connected Number IE and may be replicated in the **connectedAddress** field along with any other known aliases. This field and the Connected Number IE may be conveyed to endpoints by intermediary devices that perform call transfers using methods such as those described in Clause 8.4.6/H.323. This field, and the Connected Number IE, may be sent to either the calling or called endpoint; "connected" in this context merely refers to the opposite endpoint in a call. + +**presentationIndicator** – Indicates whether presentation of the **connectedAddress** should be allowed or restricted. If both **presentationIndicator** and the presentation indicator of the Connected Number IE are present and are in conflict, the presentation indicator of the Connected Number IE shall be used. + +**screeningIndicator** – Indicates whether the **connectedAddress** was provided by the endpoint or network (gatekeeper), and whether the **connectedAddress** was screened by a gatekeeper. If both **screeningIndicator** and the screening indicator of the Connected Number IE are present and are in conflict, the screening indicator of the Connected Number IE shall be used. + +**destinationInfo** – Contains an **EndpointType** to allow the caller to determine whether the call involves a gateway or not. + +**displayName** – Provides an ordered list of names, along with language tags, that identify the called or calling user. The user's most preferred name and language should be indicated first, followed by alternative representations using the same or different language tags. The receiving user may select any of the offered names for display according to local preference. When the **displayName** field is present, it shall take precedence over the **Display** IE. However, the **Display** IE should still be provided for interworking with legacy systems. + +### 7.4.3 Other messages + +The call control messages which can carry optional Facility, Extended Facility, or Notification Indicator information elements are specified in 8.3. + +## 7.5 H.225.0 call signalling timer values + +The following Q.931 timers shall be supported: + +- The "setup timer" T303 (see Tables 9-1/Q.931 and 9-2/Q.931) defining how long the calling endpoint shall wait for an Alerting, Call Proceeding, Connect, Release Complete or other message from the called endpoint after it has sent a Setup message. This time-out value shall be at least 4 seconds. Note that some applications may appear in networks which have inherently longer delays (for example, compare the Internet to a local enterprise network or intranet). +- The "establishment timer" T301 (see Tables 9-1/Q.931 and 9-2/Q.931) defining after which time the calling endpoint shall stop waiting for the called endpoint to respond. This timer starts when Alerting is received and normally terminates on Connect or when the caller terminates the call attempt and sends Release Complete. This time-out value shall be 180 seconds (3 minutes) or greater. +- The "overlap sending timer" T302 (see Tables 9-1/Q.931 and 9-2/Q.931) defining after which time the called endpoint shall stop waiting for the dialled digits from calling endpoint while in the overlap sending. This timer starts when SETUP ACK is sent or INFORMATION received and normally terminates when sending complete indication is received. This timeout value shall be 10-15 seconds. +- The "overlap receiving timer" T304 (see Tables 9-1/Q.931 and 9-2/Q.931) defining after which time the calling endpoint shall stop waiting for the dialled digits from called endpoint user while in the overlap receiving. This timer starts when SETUP ACK is received restarts when INFORMATION is sent and normally terminates CALL PROCEEDING, ALERTING or CONNECT is received. This timeout value shall be at least 20 seconds. +- The "incoming call proceeding timer" T310 (see Tables 9-1/Q.931 and 9-2/Q.931) defining after which time the called endpoint shall stop waiting for the dialled digits from calling endpoint while in the overlap sending. This timer starts when CALL PROCEEDING is received and normally terminates on ALERTING, CONNECT or when the caller terminates the call attempt and sends Release Complete. The T310 timer shall be stopped and T301 timer shall be started upon receipt of a Progress Indicator IE with a value of 1 or 8. This timeout value shall be at least 10 seconds. +- The "status timer" T322 (see Tables 9-1/Q.931 and 9-2/Q.931) defining after which time the called endpoint shall stop waiting STATUS message response to STATUS ENQUIRY it has sent. This timer starts when STATUS ENQUIRY is sent normally terminates when STATUS message is received. This timeout value shall be at least 4 seconds. + +Note that the packet-based network-side values of these timers is the same as that used in the SCN. + +Other timers may be supported as part of optional H.450.x-series Supplementary Service Recommendations. + +## 7.6 H.225.0 common message elements + +This clause describes ASN.1 structures that are used in more than one Registration, Admission, and Status (RAS) messages. Some may also be used in the User-user part of the call signalling messages. + +**requestSeqNum** in messages is used to keep track of multiple outstanding requests. Any associated response messages (success or failure) shall have the corresponding **requestSeqNum** returned with it. Retransmitted messages shall have the same **requestSeqNum**. **RequestSeqNum** increments by 1 modulo 65536. + +The **protocolIdentifier** is included as part of discovery, registration and Setup/Connect to allow the parties involved to determine the vintage of the implementations involved. + +**nonStandardParameter**: This parameter is optional in the discovery, registration, and Setup/Connect sequences to allow the parties involved to determine the non-standard status of the endpoints involved. A gatekeeper or gateway is not obligated to pass on **nonStandardData** it does not support or understand as this might interfere with its operations. + +The **TransportAddress** structure is meant to capture the various transport formats and includes any transport-specific scheme in addition to the possibly local reference to a TSAP identifier. + +IPv4 and IPv6 addresses shall be encoded with the most significant octet of the address being the first octet in the respective OCTET STRING, e.g., the class B IPv4 address 130.1.2.97 shall have the "130" being encoded in the first octet of the OCTET STRING, followed by the "1" and so forth. + +The IPv6 address a148:2:3:4:a:b:c:d shall have the "a1" encoded in the first octet, "48" in the second, "00" in the third, "02" in the fourth and so forth. + +A **TransportAddress** of type **ipSourceRoute** in which the **route** SEQUENCE has no entries shall be interpreted as representing the same address as of type **ipAddress** which contains the same values for both **ip** and **port**. + +IPX addresses, **node**, **netnum**, and **port** shall be encoded with the most significant octet of each field being the first octet in the respective OCTET STRING. + +Note that this structure does not use the Transport Address = "packet-based network Address plus TSAP identifier" language of Rec. ITU-T H.323. Instead, the terms common in each transport domain are used. + +The **EndpointType** structure conveys information about the H.323 entity at the end of the signalling link. The H.323 entity would complete one or more of the **gatekeeper**, **gateway**, **mcu**, or **terminal** message elements. If the H.323 entity has an MC, then the **mc** Boolean would be TRUE. Clause 6.3/H.323 describes the representation of an MCU when collocated with a gateway; in this case, the H.323 device may include both the **gateway** and the **mcu** elements within its **EndpointType** definition. Presence of the **set** component indicates that the entity is a Simple Endpoint Type (SET) device as defined, for example, in Annex F/H.323. The bit positions in the **set** component indicate the type of SET device; their meaning is defined in Annex F/H.323 and other Recommendations that specify SET device types. The **supportedTunnelledProtocols** field supplies a prioritized list (highest priority first) of supported tunnelled protocols. + +The **TunnelledProtocol** structure identifies a tunnelled signalling protocol as described, for example, in M.1/H.323 and M.2/H.323. The **tunnelledProtocolObjectID** field is an **OBJECT IDENTIFIER** identifying the protocol being tunnelled. The **tunnelledProtocolAlternateID** provides an alternate identifier format. The **subIdentifier** field allows specification of a particular version of a standard protocol. + +The **TunnelledProtocolAlternateIdentifier** structure provides a string-based identifier format for a tunnelled protocol. The **protocolType** provides the general type of protocol, such as ISUP. The **protocolVariant** field provides a specific variation of that standard, such as ANSI. + +Tunnelled protocols that are defined as of this Recommendation are shown in Tables VI.1 and VI.2. Note that tunnelling is not restricted to the protocols listed in those tables. + +The **GatewayInfo** structure contains a **protocol** element, which allows the gateway to indicate the protocols it supports. + +The **SupportedProtocols** structure indicates a choice of protocols with which an H.323 entity has the capability to interwork. For example, selection of the **h310** choice indicates that the entity provides interworking with H.310. + +In each supported protocol capability structure (**H310Caps**, **H320Caps**, etc.), the **dataRatesSupported** element indicates the data rates supported for each protocol the device supports. The **supportedPrefixes** element indicates the prefixes associated with a supported protocol, and in some cases also with the data rates. + +The **McuInfo** structure contains a **protocol** element, which allows the MCU to indicate the protocols it supports. + +The **CapacityReportingCapability** structure indicates an endpoint's ability to report call capacity information. + +The **CapacityReportingSpecification** structure indicates the call capacity information that an endpoint is requested to report. **callStart** indicates a request for capacity information at the beginning of the call (i.e., in the ARQ or Setup). **callEnd** indicates a request for capacity information at the end of the call (i.e., in the DRQ or Release Complete). An empty **when** sequence indicates a request that the endpoint not report capacity information. + +The **CallCapacityInfo** structure allows an endpoint to indicate its call acceptance capacity for each type of call the endpoint supports. It therefore represents the current idle status of the endpoint. For example, in a voice gateway **CallCapacityInfo** would represent the number of idle circuits. + +The **CallCapacity** structure allows an endpoint to indicate its maximum capacity for each type of call and its current available capacity for each type of the call the endpoint supports. + +The **CallsAvailable** structure represents a subset of an endpoint's total call capacity. The **group** field allows the subset to be identified by a group label. The **group** may be the same as that reported in the **CircuitIdentifier**. + +The **DataRate** structure provides gateway protocol rate information. **channelRate** is the basic channel rate in hundreds of bits. **channelMultiplier** indicates the number of channels at the **channelRate**. For example, if a gateway supports a 3B call, **channelMultiplier** = 3 and **channelRate** = 640 for a 64 kbit/s channel. + +The **VendorIdentifier** structure allows a vendor to identify a product. The **vendor** element allows identification in terms of country code, extension, and manufacturer code. **productId** and **versionId** are text strings that can provide product information. The **enterpriseNumber** field identifies the manufacturer and is assigned by the Internet Assigned Numbers Authority (IANA). + +The **H221NonStandard** structure allows definition of a nonstandard field. The **t35CountryCode** element shall identify the country, as described in Annex A/T.35. The **t35Extension** element shall contain a country code extension that is assigned nationally, unless the **t35CountryCode** is binary "1111 1111", in which case this field shall contain the country code found in Annex B/T.35. The **manufacturerCode** shall be assigned nationally and identifies an equipment manufacturer. + +The **AliasAddress** structure is meant to capture the various external address formats that reference a particular transport location on the packet-based network. When registering an address consisting of dialled digits with a gatekeeper, an endpoint shall use the **dialedDigits** field and shall use only the digits 0-9. When registering an E.164 address with a gatekeeper, an endpoint shall use the **e164Number** field and shall use only the digits 0-9. When registering or otherwise representing a prefix, an endpoint shall use the **dialedDigits** field and shall use only the digits 0-9 and "#" and "\*". The **mobileUIM** field is an identification module for systems compatible with 2nd Generation and 3rd Generation wireless networks, and permits interworking with Public Land Mobile Networks as described, for example, in Annex E/H.246. When registering an ISUP address signal code with a gatekeeper, an endpoint shall use the **isupNumber** field. + +The **AddressPattern** structure allows specification of a wildcarded **AliasAddress** or a range of **PartyNumbers**. The **wildcard** field represents the possible wildcarded expansion of the **AliasAddress** structure. For dialled digits or E.164 numbers this expansion is possible at the end of the number. For email addresses the expansion is possible at the beginning. For example, if wildcard is "+1 303", the pattern could represent any number in the Denver area code. The **range** field of the **AddressPattern** structure represents a range of addresses, including the indicated start and end of range. + +The mechanisms that an endpoint uses to determine the address type is left as an implementation issue. The representation of the various number types in messages is captured in Table 19. Note that if an endpoint does not know the type or scope of an address, then it should represent this as Private Unknown when coded in H.225.0 call signalling messages and as a **dialedDigits AliasAddress** when coded in RAS messages. + +**Table 19 – Type of number representation mapping** + +| Type of number | Q.931 representation | H.225.0 information element representation | H.225.0 UIE representation | +|-------------------------------------------------------|--------------------------------------------------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| Unknown (default and version 1 interoperability mode) | Private Numbering Plan, Type of number = Unknown ("000") (Note 1) | Private Numbering Plan, Type of number = Unknown ("000") | dialedDigits AliasAddress (Note 2) | +| Private unknown | Private Numbering Plan, Type of number = Unknown ("000") (Note 1) | Private Numbering Plan, Type of number = Unknown ("000") (Note 1) | dialedDigits AliasAddress (Note 2) | +| Private, Level 2 Regional Number | Private Numbering Plan, Type of number = Level 2 Regional Number ("001") | Private Numbering Plan, Type of number = Unknown ("000") (Note 1) | privateNumber of PartyNumber AliasAddress, TypeOfNumber = level2RegionalNumber | +| Private, Level 1 Regional Number | Private Numbering Plan, Type of number = Level 1 Regional Number ("010") | Private Numbering Plan, Type of number = Unknown ("000") (Note 1) | privateNumber of PartyNumber AliasAddress, TypeOfNumber = level1RegionalNumber | +| Private, PISN specific Number | Private Numbering Plan, Type of number = PISN specific Number ("011") | Private Numbering Plan, Type of number = Unknown ("000") (Note 1) | privateNumber of PartyNumber AliasAddress, TypeOfNumber = pISNSpecificNumber | +| Private, Level 0 Regional Number (Local) | Private Numbering Plan, Type of number = Level 0 Regional Number ("100") | Private Numbering Plan, Type of number = Unknown ("000") (Note 1) | privateNumber of PartyNumber AliasAddress, TypeOfNumber = localNumber | +| E.164 Public number, unknown | ISDN/Telephony Numbering Plan, Type of number = Unknown ("000") | ISDN/Telephony Numbering Plan, Type of number = Unknown ("000") | e164Number of PartyNumber AliasAddress, TypeOfNumber = Unknown | + +**Table 19 – Type of number representation mapping** + +| Type of number | Q.931 representation | H.225.0 information element representation | H.225.0 UUIE representation | +|----------------------------------------------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| E.164 Public number, International Number | ISDN/Telephony Numbering Plan, Type of number = International Number ("001") | ISDN/Telephony Numbering Plan, Type of number = International Number ("001") | e164Number of PartyNumber AliasAddress, TypeOfNumber = internationalNumber | +| E.164 Public number, National Number | ISDN/Telephony Numbering Plan, Type of number = National Number ("010") | ISDN/Telephony Numbering Plan, Type of number = National Number ("010") | e164Number of PartyNumber AliasAddress, TypeOfNumber = nationalNumber | +| E.164 Public number, Network Specific Number | ISDN/Telephony Numbering Plan, Type of number = NetworkSpecific Number ("011") | ISDN/Telephony Numbering Plan, Type of number = NetworkSpecific Number ("011") | e164Number of PartyNumber AliasAddress, TypeOfNumber = networkSpecificNumber | +| E.164 Public number, Subscriber Number | ISDN/Telephony Numbering Plan, Type of number = Subscriber Number ("100") | ISDN/Telephony Numbering Plan, Type of number = Subscriber Number ("100") | e164Number of PartyNumber AliasAddress, TypeOfNumber = subscriberNumber | +| E.164 Public number, Abbreviated Number | ISDN/Telephony Numbering Plan, Type of number = Abbreviated Number ("110") | ISDN/Telephony Numbering Plan, Type of number = Abbreviated Number ("110") | e164Number of PartyNumber AliasAddress, TypeOfNumber = abbreviatedNumber | + +NOTE 1 – When Numbering plan identification = Private, the private number digits are encoded in **privateNumber of PartyNumber**, which includes the type of number. The Type of number field in the information element shall be ignored on reception, and coded according to this table on transmission. +NOTE 2 – A **privateTypeOfNumber = Unknown PartyNumber AliasAddress** shall be treated the same as a **dialedDigits AliasAddress**. + +The **MobileUIM** structure represents an identification module for systems compatible with 2nd Generation and 3rd Generation wireless networks. The choices available are: + +- **ansi-41-uim** – This is for wireless networks defined by American standards. +- **gsm-uim** – This is for wireless networks defined by European standards. + +The **ANSI-41-UIM** structure identifies an identification module for systems compliant with American standards for wireless networks. The choices available are: + +- **imsi** – This is for International Mobile Station Identification numbers. +- **min** – This is for Mobile Identification Numbers. +- **mdn** – This is for Mobile Directory Numbers. +- **msisdn** – This is for Mobile Station ISDN numbers. +- **esn** – This is for Electronic Serial Numbers. +- **mscid** – This is for Mobile Switching Centre numbers plus Market Identification or System Identification numbers. +- **sid** – This is for System Identification numbers. + +- **mid** – This is for Market Identification numbers. +- **systemMyTypeCode** – This is for vendor identification numbers. +- **systemAccessType** – This is for the system access type. +- **qualificationInformationCode** – This is for the qualification information code. +- **sesn** – This is for SIM Electronic Serial Numbers. +- **soc** – This is for System Operator Codes. + +The **GSM-UIM** structure identifies an identification module for systems compliant with European standards for wireless networks. The choices available are: + +- **imsi** – This is for International Mobile Station Identification. +- **tmsi** – This is for Temporary Mobile Station Identification. +- **msisdn** – This is for Mobile Station ISDN numbers. +- **imei** – This is for International Mobile Equipment Identification numbers. +- **hplmn** – This is for Home Public Land Mobile Network Numbers. +- **vplmn** – This is for Visiting Public Land Mobile Network Numbers. + +The **IsupNumber** structure represents an ISUP address signal code defined in Rec. ITU-T Q.763. The choices available are: + +- **e164Number** – This is for address signal codes that use a numbering plan according to ITU-T Recs E.163 or E.164. +- **dataPartyNumber** – This is not currently used. +- **telexPartyNumber** – This is not currently used. +- **privateNumber** – This is for address signal codes that use a numbering plan according to ISO/IEC 11571. +- **nationalStandardPartyNumber** – This is not currently used. + +The **IsupPublicPartyNumber** structure represents an ISUP address signal code that follows a public numbering plan: + +- **natureOfAddress** – This is for the numbering type used for this number. +- **address** – This carries the number digits. + +The **IsupPrivatePartyNumber** structure represents an ISUP address signal code that follows a private numbering plan: + +- **privateTypeOfNumber** – This is for the numbering type used for this number. +- **address** – This field carries the number digits. + +The **NatureOfAddress** structure represents a numbering type used with an ISUP number. The choices correspond to the Nature Of Address (NOA) indicator defined in Rec. ITU-T Q.762. The choices available are: + +- **unknown** – There is no specific numbering type or the numbering type is not known. +- **subscriberNumber** – This is for a subscriber number as defined in Rec. ITU-T Q.763. +- **nationalNumber** – This is for a national number as defined in Rec. ITU-T Q.763. +- **internationalNumber** – This for is an international number as defined in Rec. ITU-T Q.763. +- **networkSpecificNumber** – This is for a network-specific number as defined in Rec. ITU-T Q.763. +- **routingNumberNationalFormat** – This is for a network routing number in national (significant) number format as defined in Rec. ITU-T Q.769.1. + +- **routingNumberNetworkSpecificFormat** – This is for a network routing number in network-specific number format as defined in Rec. ITU-T Q.769.1. +- **routingNumberWithCalledDirectoryNumber** – This is for a network routing number concatenated with called directory number as defined in Rec. ITU-T Q.769.1. + +The mapping between ISUP address codes and H.225.0 address digits in **IsupNumber** is shown in Table 20: + +**Table 20 – Number representation mapping** + +| ISUP code | ISUP address signal | H.225.0 IsupNumber digits | +|----------------------------------------------------------------------------------|---------------------|---------------------------| +| 0 0 0 0 | digit 0 | 0 | +| 0 0 0 1 | digit 1 | 1 | +| 0 0 1 0 | digit 2 | 2 | +| 0 0 1 1 | digit 3 | 3 | +| 0 1 0 0 | digit 4 | 4 | +| 0 1 0 1 | digit 5 | 5 | +| 0 1 1 0 | digit 6 | 6 | +| 0 1 1 1 | digit 6 | 7 | +| 1 0 0 0 | digit 8 | 8 | +| 1 0 0 1 | digit 9 | 9 | +| 1 0 1 0 | Spare | A | +| 1 0 1 1 | code 11 | B | +| 1 1 0 0 | code 12 | C | +| 1 1 0 1 | Spare | D | +| 1 1 1 0 | Spare | E | +| NOTE – The value '1111' is mapped to Q.931 Sending Complete IE in Annex C/H.246. | | | + +The **ExtendedAliasAddress** structure provides a means for associating common information with alias addresses. The **presentationIndicator** indicates whether presentation of the **address** should be allowed or restricted. The **screeningIndicator** indicates whether the **address** was provided by the endpoint or by the network, and whether it has been screened by the network. + +The **Endpoint** structure is used to indicate back-up, redundant, or alternative information about an endpoint: + +- **nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). +- **aliasAddress** – This is a list of alias addresses, by which other endpoints may identify this endpoint. +- **callSignalAddress** – This is the call signalling transport address for this endpoint. +- **rasAddress** – This is the registration and status transport address for this endpoint. +- **endpointType** – This specifies the type of the endpoint. +- **tokens** – Tokens associated with this endpoint (i.e., endpoint described in the **Endpoint** structure). +- **cryptoTokens** – **CryptoTokens** associated with this endpoint (i.e., the endpoint described in the **Endpoint** structure). + +- **priority** – Used when a SEQUENCE of **Endpoints** is presented. Endpoints with lower priority numbers are preferred over endpoints with higher priority numbers. Endpoints without priority numbers are equivalent to those with a priority of 0 (highest priority). +- **remoteExtensionAddress** – Contains the alias address of an endpoint in cases where this information is needed to traverse multiple gateways. +- **destExtraCallInfo** – Contains external addresses for multiple calls. +- **alternateTransportAddresses** – Indicates support for transports other than TCP. + +The **AlternateTransportAddresses** structure conveys call signalling addresses for transports other than TCP. + +The **UseSpecifiedTransport** structure defines a choice of signalling transport protocols. A value of **tcp** indicate the TCP protocol, a value of **annexE** indicates the protocol defined by Annex E/H.323, and a value of **sctp** indicates the usage of the Stream Control Transmission Protocol (SCTP). + +The **AlternateGK** structure is used to indicate a list of alternative or back-up gatekeepers, or the assigned gatekeeper: + +- **rasAddress** – The transport address used for RAS signalling. +- **gatekeeperIdentifier** – Optionally included to identify the back-up or alternative gatekeeper. If it is supplied, it shall be included in future RAS messages sent to the back-up gatekeeper. +- **needToRegister** – Set to TRUE to indicate that the endpoint must register with the alternate before sending other RAS requests. +- **priority** – Indicates the priority of the gatekeeper back-up or alternative. A lower number implies a higher priority. + +The **AltGKInfo** structure is used to provide information about alternate gatekeepers: + +- **alternateGatekeeper** – Sequence of prioritized alternate gatekeepers. +- **altGKisPermanent** – TRUE to indicate that all future RAS signals should be redirected to a gatekeeper listed in the **alternateGatekeeper** field; FALSE if only the message that caused the Reject should be redirected. This flag shall be set to TRUE if a **needToRegister** flag is set to TRUE in the **alternateGatekeeper** field. + +The **QseriesOptions** structure supplies information to the gatekeeper or other endpoints concerning the support provided by a terminal for optional Q-series protocols. It is used in the ARQ, Setup, and GRQ messages. The usage of QSeriesOptions is not yet defined pending further study. + +The **GloballyUniqueID** and **ConferenceIdentifier** are meant to be globally unique identifiers (**GloballyUniqueID**), the use of which is described in Rec. ITU-T H.323. A **GloballyUniqueID** is encoded with octet zero being encoded first. A **GloballyUniqueID** is formed according to Table 21. + +**Table 21 – Globally unique ID formation** + +| Field | Data type | Octet No. | Note | +|---------------------------|-------------------------|-----------|---------------------------------------------------------------------| +| time_low | Unsigned 32-bit integer | 0-3 | The low field of the timestamp | +| time_mid | Unsigned 16-bit integer | 4-5 | The middle field of the timestamp | +| time_hi_and_version | Unsigned 16-bit integer | 6-7 | The high field of the timestamp multiplexed with the version number | +| clock_seq_hi_and_reserved | Unsigned 8-bit integer | 8 | The high field of the clock sequence multiplexed with the variant | +| clock_seq_low | Unsigned 8-bit integer | 9 | The low field of the clock sequence | +| node | Unsigned 48-bit integer | 10-15 | The spatially unique node identifier | + +The **GloballyUniqueID** consists of a record of 16 octets and shall not contain padding between fields. The total size is 128 bits. + +To minimize confusion about bit assignments within octets, the **GloballyUniqueID** record definition is defined only in terms of fields that are integral numbers of octets. The version number is multiplexed with the timestamp (*time\_high*), and the variant field is multiplexed with the clock sequence (*clock\_seq\_high*). + +The timestamp is a 60-bit value represented by Coordinated Universal Time (UTC) as a count of 100 nanosecond intervals since 00:00:00.00, 15 October 1582 (the date of Gregorian reform to the Christian calendar). + +The version number is multiplexed in the 4 most significant bits of the *time\_hi\_and\_version* field, and is set to 1 (binary "0001"). + +The variant field determines the layout of the **GloballyUniqueID**. The structure of a DCE **GloballyUniqueID** is fixed across different versions. Other **GloballyUniqueID** variants may not interoperate with a DCE **GloballyUniqueID**. Interoperability of **GloballyUniqueIDs** is defined as the applicability of operations such as string conversion, comparison, and lexical ordering across different systems. The *variant* field consists of a variable number of the MSBs of the *clock\_seq\_hi\_and\_reserved* field (see Table 22). + +**Table 22 – Contents of the DCE variant field** + +| msb1 | msb2 | msb3 | Description | +|------|------|------|--------------------------------------| +| 0 | – | – | Reserved, NCS backward compatibility | +| 1 | 0 | – | DCE variant | +| 1 | 1 | 0 | Reserved, Microsoft Corporation GUID | +| 1 | 1 | 1 | Reserved for future definition | + +The clock sequence is required to detect potential losses of monotonicity of the clock. The clock sequence is encoded in the 6 least significant bits of the *clock\_seq\_hi\_and\_reserved* field and in the *clock\_seq\_low* field. + +The *node* field consists of the IEEE address, usually the host address. For systems with multiple IEEE 802 nodes, any available node address can be used. The lowest addressed octet (octet number 10) contains the global/local bit and the unicast/multicast bit, and is the first octet of the address transmitted on an 802.3 packet-based network. + +The clock sequence value should be changed whenever: + +- the **GloballyUniqueID** generator detects that the local value of UTC has gone backward; this may be due to normal functioning of the DCE Time Service. +- the **GloballyUniqueID** generator has lost its state of the last value of UTC used, indicating that time may have gone backward; this is typically the case on reboot. + +While a node is operational, the **GloballyUniqueID** generator always saves the last UTC used to create a **GloballyUniqueID**. Each time a new **GloballyUniqueID** is created, the current *UTC* is compared to the saved value and if either the current value is less (the non-monotonic clock case) or the saved value was lost, then the *clock sequence* is incremented modulo 16 384, thus avoiding production of duplicate **GloballyUniqueIDs**. + +The *clock sequence* should be initialized to a random number to minimize the correlation across systems. + +A **GloballyUniqueID** is generated according to the following algorithm: + +- 1) Determine the values for the UTC-based timestamp and clock sequence to be used in the **GloballyUniqueID**. +- 2) Set the *time\_low* field equal to the least significant 32 bits (bits numbered 0 to 31 inclusive) of the timestamp in the same order of significance. +- 3) Set the *time\_mid* field equal to the bits numbered 32 to 47 inclusive of the timestamp in the same order of significance. +- 4) Set the 12 least significant bits (bits numbered 0 to 11 inclusive) of the *time\_hi\_and\_version* field equal to the bits numbered 48 to 59 inclusive of the timestamp in the same order of significance. +- 5) Set the 4 most significant bits (bits numbered 12 to 15 inclusive) of the *time\_hi\_and\_version* field to the 4-bit version number corresponding to the **GloballyUniqueID** version being created, as shown in Table 22. +- 6) Set the *clock\_seq\_low* field to the 8 least significant bits (bits numbered 0 to 7 inclusive) of the *clock sequence* in the same order of significance. +- 7) Set the 6 least significant bits (bits numbered 0 to 5 inclusive) of the *clock\_seq\_hi\_and\_reserved* field to the 6 most significant bits (bits numbered 8 to 13 inclusive) of the *clock sequence* in the same order of significance. +- 8) Set the 2 most significant bits (bits numbered 6 and 7) of the *clock\_seq\_hi\_and\_reserved* to 0 and 1, respectively. +- 9) Set the *node* field to the 48-bit IEEE address in the same order of significance as the address. + +If a system wants to generate a **GloballyUniqueID** but has no IEEE 802 compliant network card or other source of IEEE 802 addresses, then an alternative method should be used to generate a replacement value for the address. The ideal solution is to obtain a 47-bit cryptographic quality random number, and use it as the most significant 47 bits of the node ID, with the least significant bit of the first octet of the node ID set to 1. This bit is the unicast/multicast bit, which will never be set in IEEE 802 addresses obtained from network cards; hence, there can never be a conflict between **GloballyUniqueIDs** generated by machines with and without network cards. + +If a system does not have a primitive to generate cryptographic quality random numbers, then in most systems there are usually a fairly large number of sources of randomness available from which one can be generated. Such sources are system specific, but often include the percentage of memory in use, the size of main memory in bytes, the amount of free main memory in bytes, the size of the paging or swap file in bytes, free bytes of paging or swap file, the total size of user virtual address space in bytes, the total available user address space bytes, the size of boot disk drive in bytes, the free + +disk space on boot drive in bytes, the current time, the amount of time since the system booted, the individual sizes of files in various system directories, etc. + +For use in human-readable text, a **GloballyUniqueID** string representation is specified as a sequence of fields, some of which are separated by single dashes. + +Each field is treated as an integer and has its value printed as a zero-filled hexadecimal digit string with the most significant digit first. The hexadecimal values a to f inclusive are output as lower case characters, and are case insensitive on input. The sequence is the same as the **GloballyUniqueID** constructed type. + +The formal definition of the **GloballyUniqueID** string representation is provided by the following extended BNF: + +``` + +UUID = + + + +time_low = +time_mid = +time_high_and_version = +clock_seq_and_reserved = +clock_seq_low = +node = + +hexOctet = p +hexDigit = | | | | | | +digit = "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | + "8" | "9" +hyphen = "-" +a = "a" | "A" +b = "b" | "B" +c = "c" | "C" +d = "d" | "D" +e = "e" | "E" +f = "f" | "F" + +``` + +The following is an example of the string representation of a **GloballyUniqueID**: + +f81d4fae-7dec-11d0-a765-00a0c91e6bf6 + +**timeToLive** is a number of seconds that a registration is to be considered valid. + +The **H248PackagesDescriptor** structure is an octet string, which will contain ASN.1 PER encoded H.248 **PackagesDescriptor**. + +The **H248SignalsDescriptor** structure is an octet string, which will contain ASN.1 PER encoded H.248 **SignalsDescriptor**. + +The **FeatureDescriptor** structure is a **GenericData** element that is used to generically identify a feature. + +**CircuitInfo** – This structure provides information about the SCN circuit or circuits used for this call. The **sourceCircuitID** field provides information about the source circuit when the call originates on the SCN, and might be used by an ingress gateway to report the source circuit identifier to the gatekeeper. The **destinationCircuitID** provides information about the destination circuit when the call terminates on the SCN, and might be used by a gatekeeper to select a destination circuit on an egress gateway. + +The **CircuitIdentifier** structure designates a facility for purposes of reporting by a gateway or selection by a gatekeeper. The **CircuitIdentifier** structure supports a variety of interfaces. + +The **CicInfo** structure designates SS7 bearer channels. The **cic** field is the circuit identifier code as defined in Rec. ITU-T Q.763, encoded with the least significant bits in the first octet and the most significant bits in the last octet. The **pointCode** field contains the point code as defined in Rec. ITU-T Q.763. The first octet of the **pointCode** identifies the network (network indicator code) and the remaining octets identify the SS7 point code value. The **cic** and **pointCode** fields are variable in length to allow for national variants. + +The **GroupID** structure identifies a physical or logical **group** and a **member** (or set of **members**) within that group. For example, **group** could identify a physical interface, while **member** could identify a particular DS0 on that interface. If the **member** field is omitted, the gateway is expected to select an available facility in the specified **group**. + +The **CarrierInfo** structure contains information about the Carrier Selection. The **carrierIdentificationCode** identifies the carrier (like carrier identification code in ISUP IAM message) chosen by the subscriber or determined by the routing applications, as a binary string of digits. The **carrierName** field is another means to identify the carrier as an ASCII string. + +**carrier** – carrier identifier/selection code for call routing as determined by the routing applications or preferred by the subscriber. + +The **ServiceControlDescriptor** structure contains service-specific data, or references to it, intended for user presentation or other service control communications as described, for example, in Annex K/H.323. The following options are possible: + +- **url** – This selection contains a URL-referenced protocol or resource. +- **signal** – This selection contains a **SignalsDescriptor** as defined in Rec. ITU-T H.248.1, in binary format. The optional **streamID** and **notifyCompletion** elements shall be omitted from the **Signal** sequence in the **SignalsDescriptor**. +- **nonStandard** – This selection contains information not defined in this Recommendation (for example, proprietary data). +- **callCreditServiceControl** – This selection contains information related to controlling the duration of a call and advising the user of account balance information. + +The **ServiceControlSession** structure contains a description of a service control session as described, for example, in Annex K/H.323. It contains the following fields: + +- **sessionId** – An integer identifying this session that is unique for the client. Note that the identifiers received through different signalling paths (e.g., RAS and call signalling) are orthogonal and may overlap. +- **contents** – A **ServiceControl** structure with the relevant contents, or communication mechanism. +- **reason** – Indicates whether this is a new session (**open**) or a modification to an existing session (**refresh**), or that the session is being terminated by the provider (**close**) and existing resources such as a GUI, etc., should be closed. + +The **RasUsageInfoTypes** structure lists types of usage information that may be reported by an endpoint to a gatekeeper. The endpoint uses this structure to indicate its capabilities with respect to collecting and reporting usage information, and the gatekeeper uses this structure to request usage information of particular types. The **nonStandardUsageTypes** field allows a vendor to refer to proprietary usage information types. The **startTime** and **endTime** fields refer to the times at which a call started and ended, respectively. The **terminationCause** parameter refers to the reason that the call ended. + +The **RasUsageSpecification** structure is a template that allows a gatekeeper to request particular types of usage information at specific points in a call. The **when** field indicates the point or points in the call at which time the endpoint is requested to report the information; **start** refers to the start of + +the call, **end** refers to the end of the call, and **inIrr** refers to unsolicited IRR messages. The **callStartingPoint** field defines the point or points in the call that shall be considered the start of the call for the purposes of reporting usage information; a value of **connect** refers to transmission or reception of the Connect message, and a value of **alerting** refers to transmission or reception of the Alerting message. The **required** field indicates the types of usage information that the endpoint is required to report. A **RasUsageSpecification** structure in which nothing is selected in either the **when** or **required** fields indicates a request to disable the reporting of usage information. + +The **RasUsageInformation** structure is a collection of usage data pertaining to a particular call. The **nonStandardUsageFields** field allows a vendor to list usage information of proprietary types. The **alertingTime** field indicates the time at which the Alerting message was sent or received. The **connectTime** field indicates the time at which the Connect message was sent or received. The **endTime** field indicates the time at which the Release Complete message was sent or received. + +The **CallTerminationCause** structure indicates the reason for the end of a call. The **releaseCompleteReason** field indicates the **reason** that was specified in the Release Complete message. The **releaseCompleteCauseIE** field provides the Cause IE from the Release Complete message. + +The **BandwidthDetails** structure defines additional bandwidth usage information that is not available in the **BandWidth** structure. The **sender** field is set to TRUE if the message is sent by the sender of the stream, or FALSE if sent by the receiver. The **multicast** field is set to TRUE if the stream is multicast, or FALSE otherwise. The **bandwidth** field indicates the bandwidth used for the stream in units of hundreds of bits per second. The **rtcpAddresses** field indicates the RTCP addresses used for the media stream. + +The **CallCreditCapability** structure indicates certain capabilities of an endpoint related to billing for a call. By default, an endpoint is assumed not to have these optional capabilities. If a field in this structure is not included, this indicates that the status of the capability represented by that field has not changed since the last time it was reported. The **canDisplayAmountString** field indicates whether the endpoint can display a text string that contains the amount of currency in a user's account. The **canEnforceDurationLimit** field indicates whether an endpoint has the capability to disengage a call when a call duration limit indicated by the gatekeeper has elapsed. + +The **CallCreditServiceControl** structure allows a gatekeeper to provide certain billing-related control and information to an endpoint. This structure provides the following fields: + +- **amountString** – This field indicates the amount of money in a user's account, e.g., "\$10.00". The string shall include the appropriate currency symbol. Note that standard abbreviations for currency types, such as "USD" for United States dollars, are defined by ISO 4217. The **amountString** field shall be encoded in Basic ISO/IEC 10646 (Unicode). +- **billingMode** – This field indicates the billing mode for this call. A mode of **debit** indicates that the call will result in charges against the amount of money available in a user's account. A mode of **credit** indicates that the call will result in charges to be paid at a later time. An endpoint could use this information, for example, to determine the type of announcement to play or display. +- **callDurationLimit** – This field indicates the remaining amount of time allowed for a particular call. +- **enforceCallDurationLimit** – This field indicates whether the endpoint is requested to disengage the call after the amount of time indicated by **callDurationLimit** has elapsed. If this field is not provided, the endpoint shall interpret this to indicate that the directive has not changed from its previous state. +- **callStartingPoint** – This field indicates the point in the call that timing is requested to begin if call duration enforcement is provided by the endpoint. + +The **GenericData** structure consists of an **id** to identify the data, and the **parameters** field to convey the actual parameters. + +The **GenericIdentifier** structure provides various ways to identify an object. + +The **EnumeratedParameter** structure provides a generic parameter. It consists of an **id** to identify the parameter, and a **content** field to convey any associated data. + +The **Content** structure supports a number of different data types, including **raw**, **text**, **unicode**, **bool**, **number8**, **number16**, **number32**, **id**, **alias**, **transport**, **compound** and **nested**. This allows for flexible definition of a generic parameter. The **raw** choice allows for a parameter or set of parameters whose actual data structure is defined elsewhere; for example, it could consist of PER-encoded ASN.1 or data in type-length-value form, or could be an encapsulated message of another signalling protocol. + +The **FeatureSet** structure allows an entity to specify generic feature information. The entity specifies the set of features that it requires for successful completion of the call using the **neededFeatures** field, the set of features that it prefers but does not require using the **desiredFeatures** field, and the set of features that it supports in the **supportedFeatures** field. The **replacementFeatureSet** BOOLEAN is set to TRUE to indicate that this feature set replaces any previously sent feature set, or FALSE otherwise. + +The **TransportChannelInfo** structure provides information about a media transport channel. The **sendAddress** field is the transport address of the sender, and the **recvAddress** is the transport address of the receiver. + +The **RTPSession** structure provides a description of an RTP session. It has the following fields: + +- **rtpAddress** – This field provides the send and receive addresses of the RTP stream. +- **rtcpAddress** – This field provides the send and receive addresses of RTCP messages. +- **cname** – This field provides the CNAME as specified in clause 6 and in Annex A. +- **ssrc** – This field is used to identify the source of an RTP stream, as described in clause 6 and in Annex A. +- **sessionId** – This field provides the identifier of this RTP session, as described in Rec. ITU-T H.245. +- **associatedSessionIds** – This field provides the identifiers of associated RTP sessions, as described in Rec. ITU-T H.245. +- **multicast** – This field indicates whether this is a multicast session. +- **bandwidth** – This field indicates the bandwidth used for the stream in units of hundreds of bits per second. + +The **RehomingModel** structure is used to indicate the model used by an endpoint for identifying and re-registering to its assigned gatekeeper. The following options are possible: + +- **gatekeeperBased** – The endpoint will re-register with the assigned gatekeeper under when instructed to do so by the gatekeeper. +- **endpointBased** – The endpoint will poll the assigned gatekeeper and will re-register when the assigned gatekeeper responds to it. + +The **TransportQOS** structure is used to indicate the resource reservation capabilities supported by an endpoint. The following options are possible: + +- **endpointControlled** – The endpoint will apply its own reservation mechanism. +- **gatekeeperControlled** – The gatekeeper will perform resource reservation on behalf of the endpoint. +- **noControl** – No resource reservation is needed. + +- **qOSCapabilities** – The QoS capabilities of the endpoint are described by the fields in a **QoSCapability** structure. + +## 7.7 Required support of RAS messages + +Table 23 shows the RAS messages that are supported by different endpoint types. + +**Table 23 – Status of RAS messages** + +| RAS Message | Endpoint (Tx) | Endpoint (Rx) | Gatekeeper (Tx) | Gatekeeper (Rx) | +|--------------------|----------------------|----------------------|------------------------|------------------------| +| GRQ | O | | | M | +| GCF | | O | M | | +| GRJ | | O | M | | +| RRQ | M | | | M | +| RCF | | M | M | | +| RRJ | | M | M | | +| URQ | O | M | O | M | +| UCF | M | O | M | O | +| URJ | O | O | M | O | +| ARQ | M | | | M | +| ACF | | M | M | | +| ARJ | | M | M | | +| BRQ | M | M | O | M | +| BCF | M (Note 1) | M | M | O | +| BRJ | M | M | M | O | +| IRQ | | M | M | | +| IRR | M | | | M | +| IACK | | O | CM | | +| INAK | | O | CM | | +| DRQ | M | M | O | M | +| DCF | M | M | M | M | +| DRJ | M (Note 2) | M | M | M | +| LRQ | O | | O | M | +| LCF | | O | M | O | +| LRJ | | O | M | O | +| NSM | O | O | O | O | +| XRS | M | M | M | M | +| RIP | CM | M | CM | M | +| RAI | O | | | M | +| RAC | | O | M | | + +**Table 23 – Status of RAS messages** + +| RAS Message | Endpoint (Tx) | Endpoint (Rx) | Gatekeeper (Tx) | Gatekeeper (Rx) | +|--------------------|----------------------|----------------------|------------------------|------------------------| +| SCI | O | O | O | O | +| SCR | O | O | O | O | + +M Mandatory +O Optional +F Forbidden +CM Conditionally Mandatory +blank "Not Applicable" +NOTE 1 – If a gatekeeper sends a BRQ requesting a lower rate, the endpoint shall reply with BCF if the lower rate is supported, otherwise with BRJ. If a gatekeeper sends a BRQ requesting a higher rate, the endpoint may reply with BCF or BRJ. +NOTE 2 – Terminal shall not send DRJ in response to a valid DRQ from its gatekeeper. + +## 7.8 Terminal and gateway discovery messages + +The GRQ message requests that any gatekeeper receiving it respond with a GCF granting it permission to register. The GRJ is a rejection of this request indicating that the requesting endpoint should seek another gatekeeper. + +### 7.8.1 GatekeeperRequest (GRQ) + +Note that one GRQ is sent per logical endpoint; thus, an MCU or a Gateway might send many. + +The GRQ message includes the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any messages associated with this specific message. + +**protocolIdentifier** – Identifies the H.225.0 vintage of the sending endpoint. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**rasAddress** – This is the transport address that this endpoint uses for registration and status messages. The Gatekeeper shall send RAS messages to this address and not to the address from which the message was sent, unless the **rasAddress** cannot be decoded. + +**endpointType** – This specifies the type(s) of the endpoint that is registering (the MC bit shall not be set by itself). + +**gatekeeperIdentifier** – String to identify the gatekeeper from which the terminal would like to receive permission to register. A missing or null string **gatekeeperIdentifier** indicates that the terminal is interested in any available gatekeeper. + +**callServices** – Provides information on support of optional Q-series protocols to gatekeeper and called terminal. + +**endpointAlias** – A list of alias addresses, by which other terminals may identify this terminal. + +**alternateEndpoints** – A sequence of prioritized endpoint alternatives for **rasAddress**, **endpointType**, or **endpointAlias**. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**authenticationCapability** – This indicates the authentication mechanisms supported by the endpoint. + +**algorithmOIDs** – Indicates the entire set of encryption algorithms supported by the endpoint. + +**integrity** – Indicates to the recipient which integrity mechanism is to be applied on the RAS messages. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**supportsAltGK** – Indicates whether the endpoint supports the alternate gatekeeper mechanism. + +**featureSet** – This field specifies a set of generic features. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**supportsAssignedGK** – Indicates whether the endpoint supports the assigned gatekeeper mechanism. + +**assignedGatekeeper** – This field indicates the endpoint's current assigned gatekeeper. + +### 7.8.2 GatekeeperConfirm (GCF) + +The GCF message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the GRQ. + +**protocolIdentifier** – Identifies the vintage of the accepting gatekeeper. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**gatekeeperIdentifier** – String to identify gatekeeper that is sending the GCF. + +**rasAddress** – This is the transport address that the gatekeeper uses for registration and status messages. + +**alternateGatekeeper** – Sequence of prioritized alternatives for **gatekeeperIdentifier** and **rasAddress**. + +**authenticationMode** – This indicates the authentication mechanism to be used. The gatekeeper shall choose **authenticationMode** from **authenticationCapability** provided by the endpoint in GRQ. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**algorithmOID** – Indicates the encryption algorithm required by the gatekeeper. + +**integrity** – Indicates to the recipient which integrity mechanism is to be applied on the RAS messages. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, + +the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**featureSet** – This field specifies a set of generic features. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**assignedGatekeeper** – Assigned gatekeeper of the endpoint. + +**rehomingModel** – Indicates the mechanism to be used by the endpoint for re-registering to the assigned gatekeeper. + +### 7.8.3 GatekeeperReject (GRJ) + +The GRJ message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the GRQ. + +**protocolIdentifier** – Identifies the vintage of the rejecting gatekeeper. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**gatekeeperIdentifier** – String to identify gatekeeper that is sending the GRJ. + +**rejectReason** – Codes for why the GRQ was rejected by this gatekeeper. A reason of **genericDataReason** indicates that the request was rejected as a result of a generic element or feature; in this case, additional information may be specified in the **genericData** field. + +**altGKInfo** – Optional information about alternative gatekeepers. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**featureSet** – This field specifies a set of generic features. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +## 7.9 Terminal and gateway registration messages + +The RRQ is a request from a terminal to a gatekeeper to register. If the gatekeeper responds with a RCF, the terminal shall use the responding gatekeeper for future calls. If the gatekeeper responds with a RRJ, the terminal must seek another gatekeeper to register with. + +### 7.9.1 RegistrationRequest (RRQ) + +The RRQ message includes the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any response associated with this specific message. + +**protocolIdentifier** – Identifies the H.225.0 vintage of the sending endpoint. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**discoveryComplete** – Set to TRUE if the requesting endpoint has preceded this message with the gatekeeper discovery procedure; set to FALSE if registering only. Note that registration may age, and the endpoint will get a failure on an RRQ or ARQ with a reason code of **discoveryRequired** or **notRegistered** respectively. This indicates that the endpoint should perform the discovery procedure (either dynamic or static) before issuing the RRQ with **discoveryComplete** set to TRUE. + +**callSignalAddress** – This is the call signalling transport address for this endpoint. If multiple transports are supported, they shall be registered all at once. + +**rasAddress** – This is the registration and status transport address for this endpoint. The Gatekeeper shall send RAS messages to this address and not to the address from which the message was sent, unless the **rasAddress** cannot be decoded. + +**terminalType** – This specifies the type(s) of the endpoint that is(are) registering; note that the **mc** bit shall not be set by itself; either the **terminal**, **mcu**, **gateway**, or **gatekeeper** bit shall also be set. If **vendor** information is provided, this information shall be identical to that in **endpointVendor**. If the **terminalType** is **gateway** or **mcu**, then the optional **supportedPrefixes** value is a list of prefix addresses by which other endpoints may identify SCN protocols and data rates supported by this entity. This field may be used in addition to or as an alternative to the **terminalAlias** and **terminalAliasPattern** fields. All of the endpoint's supported prefixes shall be included in each RRQ unless the **additiveRegistration** option is specified, in which case the supported prefixes in an RRQ shall be added to the list of currently registered prefixes for the endpoint. With the additive RRQ, supported prefixes already registered to this endpoint shall be considered still registered. Note that prefixes are not part of a **PartyNumber** (E.164 or others). In order to register a **PartyNumber** (or a range or pattern of them), the endpoint shall use the **terminalAlias** and **terminalAliasPattern** fields as described below. + +**terminalAlias** – This optional value is a list of alias addresses, by which other terminals may identify this terminal. This field may be used in addition to or as an alternative to the **terminalAliasPattern** and **supportedPrefixes** fields. If the **terminalAlias** is null, a **terminalAlias** address may be assigned by the gatekeeper and included in the RCF. If the **terminalAlias** does not contain any **dialedDigits**, **partyNumber** or **isupNumber** address, a **dialedDigits.partyNumber** or **isupNumber** address may be assigned by the gatekeeper and included in the RCF. If an **email-ID** is available for the endpoint, it should be registered. Note that multiple alias addresses may refer to the same transport addresses. All of the endpoint's aliases that it desires to register shall be included in this list unless the **additiveRegistration** option is specified, in which case the endpoint aliases in an RRQ shall be added to the list of aliases currently registered for the endpoint. + +**gatekeeperIdentifier** – String to identify the gatekeeper that the terminal wishes to register with. + +**endpointVendor** – Information about the endpoint vendor. + +**alternateEndpoints** – A sequence of prioritized endpoint alternatives for **callSignalAddress**, **rasAddress**, **terminalType**, or **terminalAlias**. + +**timeToLive** – Duration of the validity of the registration, in seconds. After this time the gatekeeper may consider the registration stale. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**keepAlive** – If set to TRUE, indicates that the endpoint has sent this RRQ as a "keep alive". An endpoint can send a lightweight RRQ consisting of only **rasAddress**, **keepAlive**, **endpointIdentifier**, **gatekeeperIdentifier**, **tokens**, and **timeToLive**. A gatekeeper in receipt of RRQ with a **keepAlive** field set to TRUE should ignore fields other than **endpointIdentifier**, **gatekeeperIdentifier**, **tokens**, and **timeToLive**. The **rasAddress** in a lightweight RRQ shall only be used by a gatekeeper as the destination for an RRJ when the endpoint is not registered. + +**endpointIdentifier** – The **endpointIdentifier** provided by the gatekeeper during the original RCF. + +**willSupplyUUIEs** – If set to TRUE, this indicates that the endpoint will supply H.225.0 call signalling message information in IRR messages if requested by the gatekeeper. + +**maintainConnection** – If TRUE, this indicates that the sender of the message is capable of supporting a signalling connection when no calls are currently signalled over the connection. + +**alternateTransportAddresses** – This field conveys call signalling addresses for transports other than TCP. Inclusion of an address indicates support for the corresponding transport. + +**additiveRegistration** – If present, this field indicates that this message is an "additive" RRQ, meaning that the endpoint has sent this RRQ as an addition of information to an existing registration. An endpoint may send an additive RRQ consisting of only **callSignalAddress**, **rasAddress**, **terminalType**, **terminalAlias**, **terminalAliasPattern**, **alternateEndpoints**, **endpointIdentifier**, **gatekeeperIdentifier**, and **tokens**. A gatekeeper in receipt of an RRQ with the **additiveRegistration** field present shall ignore fields other than these. The **rasAddress** in an additive RRQ shall be used by a gatekeeper as the destination for the subsequent RRJ if the endpoint is not registered or if the **terminalAlias** and/or **terminalAliasPattern** conflicts with the gatekeeper's registration policy. + +**terminalAliasPattern** – This optional value is a list of address patterns specifying aliases and addresses by which other endpoints may identify this endpoint. This field may be used in addition to or as an alternative to the **terminalAlias** and **supportedPrefixes** fields. All of the endpoint's aliases and addresses shall be included in each RRQ unless the **additiveRegistration** option is TRUE, in which case the endpoint aliases and addresses in the RRQ shall be added to the list of aliases currently registered for the endpoint. + +**supportsAltGK** – Indicates whether the endpoint supports the alternate gatekeeper mechanism. + +**usageReportingCapability** – This field may be included by the endpoint to advertise its ability to collect and report various types of usage information. + +**multipleCalls** – If TRUE, this field indicates that the sender of the message is capable of signalling multiple calls over a single call signalling connection. + +**supportedH248Packages** – This field indicates a list of H.248 packages supported by this endpoint. + +**callCreditCapability** – This field describes certain billing-related capabilities of this endpoint. + +**capacityReportingCapability** – This field describes the endpoint's ability to report call capacity information. + +**capacity** – This field indicates the endpoint's maximum and current call capacity. When sending this field, the endpoint shall include the **maximumCallCapacity** and **currentCallCapacity** elements. + +**featureSet** – This field specifies a set of generic features. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**restart** – If set, this field indicates that this is the first RRQ sent by the endpoint after its reboot or after an abnormal event that resulted in loss of its calls. This allows the gatekeeper to perform any cleanup or other functions as necessary. + +**supportsACFSequences** – If set, this field indicates that the endpoint is able to receive and process a sequence of ACF messages in response to a single ARQ message. + +**supportsAssignedGatekeeper** – Indicates whether the endpoint supports the assigned gatekeeper mechanism. + +**assignedGatekeeper** – This field indicates the endpoint's current assigned gatekeeper. + +**transportQOS** – An endpoint may use this field to indicate its capability to reserve transport resources. + +**language** – Indicates the language(s) the user will use or in which the user would prefer to receive announcements and prompts. The field contains one or more RFC 5646 compliant language tags. + +### 7.9.2 RegistrationConfirm (RCF) + +The RCF message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the RRQ. + +**protocolIdentifier** – Identifies the vintage of the accepting gatekeeper. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**callSignalAddress** – This is an array of transport addresses for H.225.0 call signalling messages; one for each transport that the gatekeeper will respond to. This address includes the TSAP identifier. + +**terminalAlias** – This optional value is a list of alias addresses, by which other terminals may identify this terminal. This field may be used in addition to, or as an alternative to, the **terminalAliasPattern** and **supportedPrefixes** fields. It specifies the alias addresses that have been accepted from those proposed in the associated RRQ message. If none were proposed in the RRQ, this list gives aliases assigned by the gatekeeper. If this field is not included, and alias addresses were proposed in the RRQ, then the gatekeeper has accepted all of the proposed alias addresses. If this field is included and specifies a subset of the alias addresses proposed in the RRQ, then the Gatekeeper has accepted only those addresses. + +**gatekeeperIdentifier** – String to identify the gatekeeper that has accepted the terminal's registration. + +**endpointIdentifier** – A gatekeeper assigned terminal identity string; shall be echoed in subsequent RAS messages. + +**alternateGatekeeper** – Sequence of prioritized alternatives for **gatekeeperIdentifier** and **rasAddress**. + +**timeToLive** – Duration of the validity of the registration, in seconds. After this time the gatekeeper may consider the registration stale. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**willRespondToIRR** – True if the gatekeeper will send an IACK or INAK message in response to an unsolicited IRR message with its **needsResponse** field set to TRUE. + +**preGrantedARQ** – Indicates events for which the gatekeeper has pre-granted admission. This allows for faster call setup times in environments where admission is guaranteed through means other than the ARQ/ACF exchange. Note that even if these fields are set to TRUE, an endpoint can still send an ARQ to the gatekeeper for reasons such as address translation, or the endpoint does not support this modified signalling mode. If the **preGrantedARQ** sequence is not present, then ARQ signalling shall be used in all cases. The fields are: + +- **makeCall** – If the **makeCall** flag is TRUE, then the gatekeeper has pre-granted permission to the endpoint to initiate calls without first sending an ARQ. If the **makeCall** flag is FALSE, the endpoint shall always send ARQ to get permission to make a call. +- **useGKCallSignalAddressToMakeCall** – If the **makeCall** and **useGKCallSignalAddressToMakeCall** flags are both set to TRUE, then if the endpoint does not send an ARQ to the gatekeeper to make a call, the endpoint shall send all H.225.0 call signalling to the gatekeeper call signalling channel. +- **answerCall** – If the **answerCall** flag is TRUE, then the gatekeeper has pre-granted permission to the endpoint to answer calls without first sending an ARQ. If the **answerCall** flag is FALSE, the endpoint shall always send ARQ to get permission to answer a call. +- **useGKCallSignalAddressToAnswer** – If the **answerCall** and **useGKCallSignalAddressToAnswer** flags are both set to TRUE, then when an endpoint does not send an ARQ to the gatekeeper to answer a call, the endpoint shall ensure that all H.225.0 call signalling comes from the gatekeeper. If an endpoint has been instructed to use the gatekeeper when answering, but it does not know whether an incoming call has come from the gatekeeper (which may involve looking at the transport address), the endpoint shall issue ARQ irrespective of the state of the **useGKCallSignalAddressToAnswer** flag. +- **irrFrequencyInCall** – This indicates the frequency, in seconds, of IRR messages sent to the gatekeeper when the endpoint is in one or more calls. If it is not present, the gatekeeper does not want unsolicited IRR messages. When the endpoint is sending these IRR messages, the call reference value shall be made unique for the terminal, as it would have been generated in an Admission Request. However, this is not a "normal" CRV, and cannot be reused for further communication (DRQ, IRQ or BRQ). The call identifier shall be the same as used in the call signalling channel messages for the related call. +- **totalBandwidthRestriction** – This field limits the total use of bandwidth for the endpoint when in calls. If it is not present, there is no constant bandwidth restriction. +- **alternateTransportAddresses** – This field conveys call signalling addresses for transports other than TCP. Inclusion of an address indicates support for the corresponding transport. + +- **useSpecifiedTransport** – This field allows the gatekeeper to instruct the endpoint as to which signalling transport protocol to use for making calls. If this field is included and the specified transport is not **tcp**, then the **alternateTransportAddresses** shall also be included in this message. + +**maintainConnection** – If TRUE, this indicates that the gatekeeper (in the case of gatekeeper routing) is capable of supporting a signalling connection when no calls are currently signalled over the connection. + +**serviceControl** – Contains service specific data or addressing information that the endpoint may use for non-call related service control communication with the network as described, for example, in Annex K/H.323. + +**supportsAdditiveRegistration** – If present, this field indicates that the gatekeeper supports additive registration capabilities. If not present, the gatekeeper does not support additive registration. + +**terminalAliasPattern** – This optional value is a list of address patterns specifying aliases and addresses by which other endpoints may identify this endpoint. This field may be used in addition to or as an alternative to the **terminalAlias** and **supportedPrefixes** fields. It specifies the aliases and addresses that have been accepted from those proposed in the associated RRQ message. If none were proposed in the RRQ, this list gives aliases and addresses assigned by the gatekeeper. If this field is not included and address patterns were proposed in the RRQ, then the gatekeeper has accepted all of the proposed patterns. If this field is included and specifies a subset of the address patterns proposed in the RRQ, then the gatekeeper has accepted only those patterns. + +**supportedPrefixes** – This optional value is a list of prefixes by which other endpoints may identify this endpoint. This field may be used in addition to or as an alternative to the **terminalAlias** and **terminalAliasPattern** fields. It specifies the address prefixes that have been accepted from those proposed in the associated RRQ message. If none were proposed in the RRQ, this list gives prefixes assigned by the gatekeeper. If this field is not included and address prefixes were proposed in the RRQ, then the gatekeeper has accepted all of the proposed prefixes. If this field is included and specifies a subset of the address prefixes proposed in the RRQ, then the gatekeeper has accepted only those prefixes. + +**usageSpec** – This field may be included by the gatekeeper to request that the endpoint collect and report the indicated call usage information at the specified points in time. + +**featureServerAlias** – This field is reserved for future use by the ITU-T for a stimulus-based protocol. + +**capacityReportingSpec** – This field indicates the type of call capacity information that an endpoint is requested to report. + +**featureSet** – This field specifies a set of generic features. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**assignedGatekeeper** – Assigned gatekeeper of the endpoint. + +**rehomingModel** – Indicates the mechanism to be used by the endpoint for re-registering to the assigned gatekeeper. + +**transportQOS** – The Gatekeeper may use this field to indicate the resource reservation mechanism to be used by the endpoint. + +**language** – Indicates the language(s) associated with the user for calls or in which the user might receive announcements and prompts. If the endpoint provided language information in the RRQ, this field would normally contain the same information (if present). However, the Gatekeeper may use different language tags when resolving addresses or when responding to LRQs. Placing that + +information here will alert the user about such provisioned language information. The field contains one or more RFC 5646 compliant language tags. + +### 7.9.3 RegistrationReject (RRJ) + +The RRJ message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the RRQ. + +**protocolIdentifier** – Identifies the vintage of the rejecting gatekeeper. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**rejectReason** – The reason for the rejection of the registration. This field may contain an **invalidTerminalAliases** value, in which case it contains a list of aliases, addresses and supported prefixes that were determined to be invalid in the associated RRQ message. In any event, all of the aliases, addresses and supported prefixes from the associated RRQ are rejected along with those specified in the **invalidTerminalAliases** field. A reason of **genericDataReason** indicates that the request was rejected as a result of a generic element or feature; in this case, additional information may be specified in the **genericData** field. A reason of **registerWithAssignedGK** indicates that the request was rejected because the Assigned GK has become available; the endpoint registers to its assigned gatekeeper when it receives this reason. + +**gatekeeperIdentifier** – String to identify the gatekeeper that has rejected the terminal's registration. + +**altGKInfo** – Optional information about alternative gatekeepers. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**featureSet** – This field specifies a set of generic features. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**assignedGatekeeper** – Assigned gatekeeper of the endpoint. + +## 7.10 Terminal/gatekeeper unregistration messages + +### 7.10.1 UnregistrationRequest (URQ) + +The URQ requests that the association between a terminal and a gatekeeper be broken. Note that unregister is bidirectional, i.e., a gatekeeper can request a terminal to consider itself unregistered, and a terminal can inform a gatekeeper that it is revoking a previous registration. + +The URQ message includes the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any response associated with this specific message. + +**callSignalAddress** – This is one or more of the transport call signalling addresses for this endpoint which are to be unregistered. + +**endpointAlias** – This optional value is a list of alias addresses, by which other terminals may identify this terminal. This field may be used in addition to or as an alternative to the **endpointAliasPattern** and **supportedPrefixes** fields. If this field, the **endpointAliasPattern** field, and the **supportedPrefixes** field are not present, all aliases are unregistered in a single message. The **dialedDigits** value, if assigned, is required. Only values listed here are unregistered; this allows, for example, an **h323-ID** to be unregistered while leaving the **dialedDigits** value registered. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**endpointIdentifier** – Confirmation of identity; not sent by the gatekeeper. + +**alternateEndpoints** – A sequence of prioritized endpoint alternatives for **callSignalAddress** or **endpointAlias**. + +**gatekeeperIdentifier** – A **gatekeeperIdentifier** which the endpoint received in the **alternateGatekeeper** list in an RCF from the gatekeeper when it registered or in a previous URJ message. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**reason** – Used when the gatekeeper sends the URQ to indicate why the gatekeeper considers the endpoint unregistered. A reason of **maintenance** indicates that the gatekeeper or endpoint is being taken down for maintenance. A reason of **registerWithAssignedGK** indicates that the endpoint is being unregistered because the Assigned GK has become available; the endpoint registers to its assigned gatekeeper when it receives this reason. + +**endpointAliasPattern** – This optional value is a list of address patterns specifying aliases and addresses by which other endpoints may identify this endpoint. This field may be used in addition to or as an alternative to the **endpointAlias** and **supportedPrefixes** fields. If this field, the **endpointAlias** field and the **supportedPrefixes** field are not present, all aliases and addresses are unregistered in a single message. Otherwise, only values listed here are unregistered. + +**supportedPrefixes** – This optional value is a list of prefixes by which other endpoints may identify this endpoint. This field may be used in addition to or as an alternative to the **terminalAlias** and **terminalAliasPattern** fields. If this field, the **endpointAlias** field and the **endpointAliasPattern** field are not present, all aliases and addresses are unregistered in a single message. Otherwise, only values listed here are unregistered. + +**alternateGatekeeper** – Sequence of prioritized alternatives for **gatekeeperIdentifier** and **rasAddress**. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**assignedGatekeeper** – Assigned gatekeeper of the endpoint. + +### 7.10.2 UnregistrationConfirm (UCF) + +The UCF message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the URQ. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**assignedGatekeeper** – Assigned gatekeeper of the endpoint. + +### 7.10.3 UnregistrationReject (URJ) + +The URJ message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the URQ. + +**rejectReason** – The reason for the rejection of the unregistration. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**altGKInfo** – Optional information about alternative gatekeepers. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +## 7.11 Terminal to gatekeeper admission messages + +The ARQ message requests that an endpoint be allowed access to the packet-based network by the gatekeeper, which either grants the request with an ACF or denies it with an ARJ. + +### 7.11.1 AdmissionRequest (ARQ) + +The ARQ message includes the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any messages associated with this specific message. + +**callType** – Using this value, the gatekeeper can attempt to determine "real" bandwidth usage. The default value is **pointToPoint** for all calls. It should be recognized that the call type may change dynamically during the call and that the final call type may not be known when the ARQ is sent. + +**callModel** – If **direct**, the endpoint is requesting the direct terminal to terminal call model. If **gatekeeperRouted**, the endpoint is requesting the gatekeeper mediated model. The gatekeeper is not required to comply with this request. + +**endpointIdentifier** – This is an endpoint identifier that was assigned to the terminal by RCF. + +**destinationInfo** – Sequence of alias addresses for the destination, such as **dialedDigits**, **PartyNumber** (**e164Number** or **privateNumber**), or **h323-IDs**. When sending the ARQ to answer a call, **destinationInfo** indicates the destination of the call (the answering endpoint). If at least one alias is registered with a gatekeeper and no two aliases in the ARQ are registered to distinct people, the gatekeeper shall recognize the ARQ as referring to the registered identity. In the case of conflicting aliases the admission request should be rejected with cause **AliasesInconsistent**. If the gatekeeper does not provide this validation, it shall consider the first registered address to be the destination. + +**destCallSignalAddress** – Transport address used at the destination for call signalling. + +**destExtraCallInfo** – Contains external addresses for multiple calls. + +**srcInfo** – Sequence of alias addresses for the source endpoint, such as **dialedDigits**, **PartyNumber** (**e164Number** or **privateNumber**) or **h323-IDs**. When sending the ARQ to answer a call, **srcInfo** indicates the originator of the call. + +**srcCallSignalAddress** – Transport address used at the source for call signalling. + +**bandWidth** – The bidirectional bandwidth requested for the call, in units of 100 bits per second. For example, a 128 kbit/s call would be signalled as a request for 256 kbit/s. The value refers only to the audio and video bit rate excluding headers and overhead. + +**callReferenceValue** – The CRV from H.225.0 call signalling messages for this call; only local validity. This is used by a gatekeeper to associate the ARQ with a particular call. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**callServices** – Provides information on support of optional Q-series protocols to gatekeeper and called terminal. + +**conferenceID** – Unique conference identifier. + +**activeMC** – If TRUE, the calling party has an active MC; otherwise, FALSE. + +**answerCall** – Used to indicate to a gatekeeper that a call is incoming. + +**canMapAlias** – If set to TRUE, indicates that if the resulting ACF contains **destinationInfo**, **destExtraCallInfo** and/or **remoteExtensionAddress** fields, the endpoint shall copy this information to the **destinationAddress**, **destExtraCallInfo** and **remoteExtensionAddress** fields of the Setup message respectively, or into the Called Party Number IE if appropriate. If the endpoint is a gateway used to exit the H.323 network, the gateway will convert the destination information into the appropriate signalling format used outside of the H.323 network (for example, DTMF). If the GK would replace addressing information from the ARQ and **canMapAlias** is FALSE, then the + +gatekeeper should reject the ARQ. Systems compliant with H.225.0 version 4 and higher shall set this field to TRUE. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**srcAlternatives** – A sequence of prioritized source endpoint alternatives for **srcInfo**, **srcCallSignalAddress**, or **rasAddress**. + +**destAlternatives** – A sequence of prioritized destination endpoint alternatives for **destinationInfo** or **destCallSignalAddress**. + +**gatekeeperIdentifier** – A **gatekeeperIdentifier** which the endpoint received in the **alternateGatekeeper** list in an RCF from the gatekeeper when it registered or in a previous ARJ message. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**transportQOS** – An endpoint may use this field to indicate its capability to reserve transport resources. + +**willSupplyUUIEs** – If set to TRUE, this indicates that the endpoint will supply H.225.0 call signalling message information in IRR messages if requested by the gatekeeper. + +**callLinkage** – The contents of this field are typically controlled by a call linkage service. For the procedures and semantics of this field, refer to clause 10/H.323. + +**gatewayDataRate** – The requested data rate for the SCN side of a call through a gateway. This data rate if present shall be equal to the data rate specified in the Bearer capability IE of the Setup message. A gatekeeper might use this field in selecting a gateway to handle the call. + +**capacity** – This field indicates the sending endpoint's available call capacity at this point in time, assuming that the gatekeeper confirms the ARQ by sending an ACF. When sending this field, the endpoint shall include the **currentCallCapacity** element. + +**circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. + +**desiredProtocols** – Identifies the type of protocols, in order of preference, the originating endpoint desires for its call (e.g., voice or fax). A resolving entity may use this field to locate an endpoint that also supports the protocol, giving consideration to the order of preference. + +**desiredTunnelledProtocol** – This field identifies a protocol that is requested to be tunnelled. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**canMapSrcAlias** – If set to TRUE, indicates that if the resulting ACF contains **modifiedSrcInfo**, the endpoint shall copy this information to the **sourceInfo** field of the Setup message and/or to the Calling Party Number IE, if appropriate. If the gatekeeper would replace addressing information from the ARQ and **canMapSrcAlias** is FALSE, then the gatekeeper should reject the ARQ. + +NOTE – Both **destinationInfo** and **destCallSignalAddress** are optional, but at least one shall be present unless the endpoint is answering a call. There is no absolute rule which is preferred as this may be site specific, but the address should be provided if available. It is cautioned that the best results will be obtained by considering the nature of the transport protocols in use. + +### 7.11.2 AdmissionConfirm (ACF) + +The ACF message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the ARQ. + +**bandWidth** – The allowed maximum bandwidth for the call; may be less than that requested. + +**callModel** – Tells terminal whether call signalling sent on **destCallSignalAddress** goes to a gatekeeper or to a terminal. A value of **gatekeeperRouted** indicates that call signalling is being passed via the gatekeeper, while **direct** indicates that the endpoint-to-endpoint call mode is in use. + +**destCallSignalAddress** – The transport address to which to send H.225.0 call signalling, but may be an endpoint or gatekeeper address depending on the call model in use. + +**irrFrequency** – The frequency, in seconds, that the endpoint shall send IRRs to the gatekeeper while on a call, including while on hold. If not present, the endpoint does not send IRRs while active on a call, and it is expected that the gatekeeper will poll the endpoint. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**destinationInfo** – The address of the initial channel, used when calling through a gateway. + +**destExtraCallInfo** – Needed to make possible additional channel calls, i.e., for a $2 \times 64$ kbit/s call on the SCN side. Shall only contain **dialedDigits** or **PartyNumber** addresses and shall not contain the number of the initial channel. + +**destinationType** – This specifies the type of the destination endpoint. + +**remoteExtensionAddress** – Contains the alias address of a called endpoint in cases where this information is needed to traverse multiple gateways. + +**alternateEndpoints** – A sequence of prioritized endpoint alternatives for **destCallSignalAddress** or **destinationInfo**. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**transportQOS** – The gatekeeper may indicate to the endpoint where the responsibility lies for resource reservation. If the gatekeeper received a **TransportQOS** in ARQ, then it should include **transportQOS** (possibly modified according to gatekeeper implementation) in ACF. + +**willRespondToIRR** – TRUE if the gatekeeper will send an IACK or INAK message in response to an unsolicited IRR message when the IRR's **needsResponse** field set to TRUE. + +**uuiEsRequested** – The gatekeeper may request the endpoint to notify the gatekeeper of H.225.0 call signalling messages that the endpoint sends or receives if the endpoint indicated this capability in the ARQ by setting **willSupplyUUIEs** to TRUE. **uuiEsRequested** indicates the set of H.225.0 call signalling messages of which the endpoint shall notify the gatekeeper. + +**language** – Indicates the language(s) for this call, which may differ from those indicated in the RRQ if the Gatekeeper has additional information discovered via an LCF or some other mechanism. The field contains one or more RFC 5646 compliant language tags. + +**alternateTransportAddresses** – This field conveys call signalling addresses for transports other than TCP. Inclusion of an address indicates support for the corresponding transport. + +**useSpecifiedTransport** – This field allows the gatekeeper to instruct the endpoint as to which signalling transport protocol to use for making the call. If this field is included and the specified transport is not **tcp**, then the **alternateTransportAddresses** shall also be included in this message. + +**circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. For example, it allows a gatekeeper to instruct an egress gateway to select particular SCN facilities to be used for the call. + +**usageSpec** – This field may be included by the gatekeeper to request that the endpoint collect and report the indicated call usage information at the specified points in time in this call. + +**supportedProtocols** – This field indicates the protocols supported by the destination endpoint. + +**serviceControl** – This field contains service-specific data, or references to it, that could be used by an endpoint (e.g., a message to be played to the caller) as described, for example, in Annex K/H.323. + +**multipleCalls** – If TRUE, this field indicates that the destination endpoint is capable of signalling multiple calls over a single call signalling connection. If FALSE, the destination endpoint does not have this capability. If this field is not present, the gatekeeper does not know whether the remote endpoint has this capability. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**modifiedSrcInfo** – Alias address that should be used for the source endpoint, such as **dialedDigits**, **PartyNumber** (**e164Number** or **privateNumber**) or **h323-IDs**. This field should be used when the calling endpoint's alias address is translated/modified when attempting to route the call to the primary destination, or to any of the alternate endpoints. These addresses should be used by the endpoint for this call only. + +**assignedGatekeeper** – Assigned gatekeeper of the endpoint. + +### 7.11.3 AdmissionReject (ARJ) + +The ARJ message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the ARQ. + +**rejectReason** – This is the reason the admission request was denied. Note that the **rejectReason** of **routeCallToSCN** is an appropriate choice only when the ARJ is directed to an ingress gateway (the ARQ was sent by a gateway and the **answerCall** BOOLEAN in the ARQ is FALSE). If **rejectReason** is **routeCallToSCN**, the **rejectReason** for this choice also includes a telephone number, or list of telephone numbers, to which the gateway can redirect the call in the SCN, if the gateway supports such a procedure. If **rejectReason** is **exceedsCallCapacity**, the gatekeeper has determined that the + +destination does not have the capacity to accept this call at this point in time. A **rejectReason** of **collectDestination** indicates that the gatekeeper is requesting that the gateway collect the final destination address, and that the **serviceControl** field of the ARJ indicates the prompt to be presented to the user. A **rejectReason** of **collectPIN** indicates that the gatekeeper is requesting that the gateway collect a personal identification number or authorization code, and that the **serviceControl** field of the ARJ indicates the prompt to be presented to the user. A reason of **genericDataReason** indicates that the request was rejected as a result of a generic element or feature; in this case, additional information may be specified in the **genericData** field. The endpoint should re-register with the gatekeeper if it receives an error of **invalidEndpointIdentifier**. A reason of **registerWithAssignedGK** indicates that the request was rejected because the Assigned GK has become available; the endpoint registers to its assigned gatekeeper when it receives this reason. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**altGKInfo** – Optional information about alternative gatekeepers. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**callSignalAddress** – This is the gatekeeper's call signalling address returned when the reject reason is **routeCallToGatekeeper**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**serviceControl** – This field contains service-specific data, or references to it, that could be used by an endpoint (e.g., for displaying the reason a call failed) as described, for example, in Annex K/H.323. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**assignedGatekeeper** – Assigned gatekeeper of the endpoint. + +## 7.12 Terminal to gatekeeper requests for changes in bandwidth + +The BRQ message requests that an endpoint be granted a changed packet-based network bandwidth allocation by the gatekeeper, which either grants the request with a BCF or denies it with a BRJ. + +The gatekeeper may request that an endpoint raise or lower the bandwidth in use with a BRQ. If the request is to raise the rate, the endpoint may reply with either BRJ or BCF. If the request is for a lower rate, the endpoint shall reply with a BCF if the lower rate is supported, otherwise with BRJ. + +### 7.12.1 BandwidthRequest (BRQ) + +The BRQ message includes the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any messages associated with this specific message. + +**endpointIdentifier** – This is an endpoint identifier that was assigned to the terminal by RCF. + +**conferenceID** – ID of the call that is to have the bandwidth changed. + +**callReferenceValue** – The CRV from H.225.0 call signalling messages for this call; only local validity. This is used by a gatekeeper to associate the BRQ with a particular call. + +**callType** – Using this value, the gatekeeper can attempt to determine "real" bandwidth usage. + +**bandWidth** – The new bidirectional bandwidth requested for the call, in units of 100 bits per second. This is an absolute value that includes only audio and video bitstreams not counting headers and overhead. Unique multicast streams shall only add to the total bandwidth usage one time, even if there are multiple recipients of the media stream. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**gatekeeperIdentifier** – A **gatekeeperIdentifier** which the endpoint received in the **alternateGatekeeper** list in an RCF from the gatekeeper when it registered or in a previous BRJ message. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**answeredCall** – Set to TRUE to indicate that this party was the original destination (this party answered the call). + +**callLinkage** – The contents of this field are typically controlled by a call linkage service. For the procedures and semantics of this field, refer to clause 10/H.323. + +**capacity** – This field indicates the sending endpoint's available call capacity at this point in time, assuming that the gatekeeper confirms the BRQ by sending a BCF. When sending this field, the endpoint shall include the **currentCallCapacity** element. + +**usageInformation** – This field allows the endpoint to report usage information for this call. A gatekeeper shall not include this field when sending a BRQ. + +**bandwidthDetails** – Provides bandwidth information for each media stream that the endpoint is currently transmitting or receiving in the same units as the **bandWidth** field. Each multicast stream shall be reported only one time, even if there are multiple recipients of the media stream. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**transportQOS** – An endpoint may use this field to indicate its capability to reserve transport resources. + +### 7.12.2 BandwidthConfirm (BCF) + +The BCF message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the BRQ. + +**bandWidth** – The maximum allowed at this time in increments of 100 bits. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**capacity** – This field indicates the sending endpoint's available call capacity at this point in time. When sending this field, the endpoint shall include the **currentCallCapacity** element. This field is not included when the BCF is sent by a gatekeeper. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**transportQOS** – The Gatekeeper may use this field to indicate the resource reservation mechanism to be used by the endpoint. + +### 7.12.3 BandwidthReject (BRJ) + +The BRJ message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the BRQ. + +**rejectReason** – The reason the change was rejected by the gatekeeper. + +**allowedBandWidth** – The maximum allowed at this time in increments of 100 bits including the current allocation. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**altGKInfo** – Optional information about alternative gatekeepers. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +## 7.13 Location request messages + +The LRQ requests that a gatekeeper provide address translation. The gatekeeper responds with an LCF containing the transport address of the destination, or rejects the request with LRJ. + +### 7.13.1 LocationRequest (LRQ) + +The LRQ message includes the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any messages associated with this specific message. + +**endpointIdentifier** – This is an endpoint identifier that was assigned to the terminal by RCF. + +**destinationInfo** – Sequence of alias addresses for the destination, such as **dialedDigits**, **partyNumber** (**e164Number** or **privateNumber**), or **h323-IDs**. If at least one alias is registered with a gatekeeper and no two aliases in the LRQ are registered to distinct people, the gatekeeper shall recognize the LRQ as referring to the registered identity. In the case of conflicting aliases the location request should be rejected with cause **AliasesInconsistent**. If the gatekeeper does not provide this validation, it shall consider the first registered address to be the destination. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**replyAddress** – Transport address to which to send the LCF/LRJ. + +**sourceInfo** – Indicates the sender of the LRQ. The gatekeeper can use this information to decide how to respond to the LRQ. + +**canMapAlias** – If set to TRUE, indicates that if the resulting LCF contains **destinationInfo**, **destExtraCallInfo** and/or **remoteExtensionAddress** fields, the endpoint can copy this information to the **destinationAddress**, **destExtraCallInfo** and **remoteExtensionAddress** fields of the Setup message respectively. If the GK would replace addressing information from the LRQ and **canMapAlias** is FALSE, then the gatekeeper should reject the LRQ. Systems compliant with H.225.0 version 4 and higher shall set this field to TRUE. + +**gatekeeperIdentifier** – A **gatekeeperIdentifier** which the endpoint received in the **alternateGatekeeper** list in an RCF from the gatekeeper when it registered or in a previous LRJ message. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**desiredProtocols** – Identifies the type of protocols, in order of preference, the originating endpoint desires for its call (e.g., voice or fax). A resolving entity may use this field to locate an endpoint that also supports the protocol, giving consideration to the order of preference. + +**desiredTunnelledProtocol** – This field identifies a protocol that is requested to be tunnelled. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**hopCount** – This field defines the number of gatekeepers through which this message may propagate. When a gatekeeper receives an LRQ and decides that the message should be forwarded on to another gatekeeper, it first decrements **hopCount**. If **hopCount** is then greater than 0, the gatekeeper inserts + +the new hop count value into the message to be forwarded. If **hopCount** has reached 0, the gatekeeper shall not forward the message. + +**circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the Call Control signalling used in this Recommendation. When sending an LRQ in support of an ARQ or SETUP, the gatekeeper shall copy the call identifier from the ARQ or SETUP into the LRQ. An endpoint that sends an LRQ in preparation for initiating a call shall populate this field with the call identifier for the call. LRQs sent outside the context of a call will not include the call identifier field. + +**bandWidth** – The bidirectional bandwidth requested for the call, in units of 100 bits per second. For example, a 128 kbit/s call would be signalled as a request for 256 kbit/s. The value refers only to the audio and video bit rate excluding headers and overhead. + +**sourceEndpointInfo** – Sequence of alias addresses for the source endpoint, such as **dialedDigits**, **PartyNumber** (**e164Number** or **privateNumber**) or **h323-IDs**. The gatekeeper should copy the information for the endpoint on whose behalf it is sending this LRQ, or if, forwarding a received LRQ, the gatekeeper should copy the **sourceEndpointInfo** from the received LRQ. + +**canMapSrcAlias** – If set to TRUE, indicates that if the resulting LCF contains **modifiedSrcInfo**, the endpoint can copy this information to the **sourceInfo** field of the Setup message. If the LRQ is being sent by a gatekeeper as a result of receiving an ARQ, the gatekeeper shall copy this field from the ARQ. If the gatekeeper would replace addressing information from the LRQ and **canMapSrcAlias** is FALSE, then the gatekeeper should reject the LRQ. + +**language** – Indicates the language(s) the user will use or in which the user would prefer to receive announcements and prompts. The field contains one or more RFC 5646 compliant language tags. + +### 7.13.2 LocationConfirm (LCF) + +The LCF message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the LRQ. + +**callSignalAddress** – The transport address to which to send H.225.0 call signalling; uses the reliable well-known or dynamic port, but may be an endpoint or gatekeeper address depending on the call model in use. + +**rasAddress** – Registration, admissions, and status address for the located endpoint. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**destinationInfo** – Sequence of alias addresses for the destination, such as **dialedDigits**, **partyNumber** (**e164Number** or **privateNumber**) or **h323-IDs**. + +**destExtraCallInfo** – Contains external addresses for multiple calls. + +**destinationType** – This specifies the type of the destination endpoint. + +**remoteExtensionAddress** – Contains the alias address of a called endpoint in cases where this information is needed to traverse multiple Gateways. + +**alternateEndpoints** – A sequence of prioritized endpoint alternatives for **callSignalAddress**, **rasAddress**, or **destinationInfo**. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**alternateTransportAddresses** – This field conveys call signalling addresses for transports other than TCP. Inclusion of an address indicates support for the corresponding transport. + +**supportedProtocols** – This field indicates the protocols supported by the endpoint. + +**multipleCalls** – If TRUE, this field indicates that the located endpoint is capable of signalling multiple calls over a single call signalling connection. If FALSE, the endpoint does not have this capability. If this field is not present, the gatekeeper does not know whether the endpoint has this capability. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. + +**serviceControl** – This field contains addressing information that the endpoint may use for call-related service control communication with the network as described, for example, in Annex K/H.323. + +**modifiedSrcInfo** – Alias address that should be used for the source endpoint, such as **dialedDigits**, **PartyNumber** (**e164Number** or **privateNumber**) or **h323-IDs**. This field should be used when the calling endpoint's alias address is translated/modified when attempting to route the call to the primary destination, or to any of the alternate endpoints. If the LCF message results in an ACF reply to the endpoint, this field shall be copied into the ACF message. + +**bandWidth** – The allowed maximum bandwidth for the call; may be less than that requested. + +**language** – Indicates the language(s) supported by the remote user, including those used for announcements and prompts. The field contains one or more RFC 5646 compliant language tags. + +### 7.13.3 LocationReject (LRJ) + +The LRJ message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the LRQ. + +**rejectReason** – This is the reason the location request was denied. If **rejectReason** is **routeCallToSCN**, the **rejectReason** for this choice also includes a telephone number, or list of telephone numbers, to which the gateway can redirect the call in the SCN, if the gateway supports such a procedure. A reason of **resourceUnavailable** indicates that bandwidth is overutilized or that no entity registered with the gatekeeper has the capacity to handle a call to the requested location at the present time. A reason of **genericDataReason** indicates that the request was rejected as a result of a generic element or feature; in this case, additional information may be specified in the **genericData** field. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**altGKInfo** – Optional information about alternative gatekeepers. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**featureSet** – This field specifies a set of generic features that relate to this call. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**serviceControl** – This field contains addressing information that the endpoint may use for call-related service control communication with the network as described, for example, in Annex K/H.323. + +## 7.14 Disengage messages + +### 7.14.1 DisengageRequest (DRQ) + +If sent from an endpoint to a gatekeeper, the DRQ informs the gatekeeper that an endpoint is being dropped. If sent from a gatekeeper to an endpoint, the DRQ forces a call to be dropped; such a request shall not be refused. The DRQ is not sent between endpoints directly. + +Note that DRQ is not the same as **ReleaseComplete** since its purpose is to inform the gatekeeper of the termination of a call; the gatekeeper may not receive the release complete if it is not terminating the call signalling channel. + +The DRQ message includes the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any messages associated with this specific message. + +**endpointIdentifier** – This is an endpoint identifier that was assigned to the terminal by RCF. + +**conference ID** – ID of the call that is to have the bandwidth released. + +**callReferenceValue** – The CRV from H.225.0 call signalling messages for this call; only local validity. This is used by a gatekeeper to associate the message with a particular call. + +**disengageReason** – The reason the change was requested by the gatekeeper or the terminal. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**gatekeeperIdentifier** – A **gatekeeperIdentifier** which the endpoint received in the **alternateGatekeeper** list in an RCF from the gatekeeper when it registered or in a previous DRJ message. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, + +the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**answeredCall** – Set to TRUE to indicate that this party was the original destination (this party answered the call). + +**callLinkage** – The contents of this field are typically controlled by a call linkage service. For the procedures and semantics of this field, refer to clause 10/H.323. + +**capacity** – This field indicates the sending endpoint's available call capacity at this point in time, assuming that the gatekeeper confirms the DRQ by sending a DCF. When sending this field, the endpoint shall include the **currentCallCapacity** element. This field is not included when the DRQ is sent by a gatekeeper. + +**circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. + +**usageInformation** – This field allows an endpoint to report usage information for this call. A gatekeeper shall not include this field when sending a DRQ. + +**terminationCause** – This field describes the reason that the call ended. This information is more specific than the reason provided in the **disengageReason** field. A gatekeeper shall not include this field when sending a DRQ. + +**serviceControl** – This field contains service-specific data, or references to it, that could be used by an endpoint as described, for example, in Annex K/H.323. The gatekeeper could use this field to indicate that the call is ending because some account has expired or the amount paid for the call has been exhausted. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +### 7.14.2 DisengageConfirm (DCF) + +The DCF message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the DRQ. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**capacity** – This field indicates the sending endpoint's available call capacity after the call indicated in the DCF has been disengaged. When sending this field, the endpoint shall include the **currentCallCapacity** element. This field is not included when the DCF is sent by a gatekeeper. + +**circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. + +**usageInformation** – This field allows an endpoint to report usage information for this call. A gatekeeper shall not include this field when sending a DCF. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**assignedGatekeeper** – Assigned gatekeeper of the endpoint. + +### 7.14.3 DisengageReject (DRJ) + +DRJ is sent by the gatekeeper if the endpoint is unregistered. + +The DRJ message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the DRQ. + +**rejectReason** – The reason the request was rejected. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**altGKInfo** – Optional information about alternative gatekeepers. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +## 7.15 Status request messages + +The IRQ is sent from a gatekeeper to a terminal requesting status information in the form of an IRR. The IRR may be also be sent by the terminal at an interval specified in the ACF message without the receipt of an IRQ from the gatekeeper. This message should not be confused with the H.225.0 call signalling Status message. + +When an unsolicited IRR is sent by an endpoint to a gatekeeper of version 2 or higher, it may indicate in the **needResponse** field that it wishes the gatekeeper to acknowledge receipt of the IRR. In this case it fills in the **requestSeqNum** field with a number other than 1. The gatekeeper returns either an IACK (positive acknowledgement) or an INAK (negative acknowledgement) message, and shall return the same number in the **requestSeqNum** field. + +### 7.15.1 InfoRequest (IRQ) + +The IRQ message includes the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any messages associated with this specific message. + +**callReferenceValue** – CRV of the call that the query is about. If zero, this message is interpreted as a request for an IRR for each call the terminal is active on. If the terminal is not active on any calls, an IRR shall be sent in response to a **callReferenceValue** of 0 with all appropriate fields provided. If **callReferenceValue** is 0, the endpoint shall ignore **callIdentifier** – in this case the gatekeeper shall fill **callIdentifier** with 0. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**replyAddress** – A transport address to send IRR to, perhaps not that of the gatekeeper. + +**callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**uuiesRequested** – The gatekeeper may request the endpoint to notify the gatekeeper of H.225.0 call signalling messages that the endpoint sends or receives if the endpoint indicated this capability in the ARQ by setting **willSupplyUUIEs** to TRUE. **uuiesRequested** indicates the set of H.225.0 call signalling messages of which the endpoint shall notify the gatekeeper. + +**callLinkage** – The contents of this field are typically controlled by a call linkage service. For the procedures and semantics of this field, refer to clause 10/H.323. + +**usageInfoRequested** – This field may be included by a gatekeeper to request that the endpoint report the indicated call usage information in the IRR message. + +**segmentedResponseSupported** – This field indicates whether the gatekeeper will allow the endpoint to return call information for all calls in multiple IRR messages, or "segments". If this field is present, segmentation is allowed. Otherwise, segmentation is not allowed. This field is only significant when the gatekeeper sends an IRQ with a **callReferenceValue** of 0 and shall not be present otherwise. + +**nextSegmentRequested** – If the gatekeeper sends an IRQ message with **callReferenceValue** of 0 and includes the **segmentedResponseSupported** field, the endpoint may return an IRR with only part of the call information, indicated by including the segment field in the IRR. The gatekeeper may request the next segment by retransmitting the previous IRQ message with the **nextSegmentRequested** field set to the value of the next segment that the gatekeeper expects to receive. + +**capacityInfoRequested** – If present, this field indicates that the gatekeeper is requesting that the endpoint include call capacity information in the IRR. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +**assignedGatekeeper** – Assigned gatekeeper of the endpoint. + +### 7.15.2 InfoRequestResponse (IRR) + +The IRR message includes the following: + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**requestSeqNum** – In the case of a solicited IRR, this field shall contain the sequence number from the IRQ. In the case of an unsolicited report to a version 1 gatekeeper, this field shall contain one (1). + +In all other unsolicited IRRs, it shall contain a monotonically increasing number (to be returned by the gatekeeper in its response if **needResponse** is TRUE). + +**endpointType** – Provides information about the endpoint. + +**endpointIdentifier** – Value assigned by the gatekeeper in the RCF. + +**rasAddress** – Address for registration, admissions, etc. + +**callSignalAddress** – Address of H.225.0 call signalling. + +**endpointAlias** – Alias(es) for endpoint. + +**perCallInfo** – Information about a particular call: + +- **nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). +- **callReferenceValue** – H.225.0 call signalling CRV of that call that the response is about. +- **conferenceID** – Unique conference identifier. +- **originator** – If TRUE the endpoint being queried was the call originator, if FALSE the endpoint was the call destination. +- **audio** – Information about the audio channel(s). The **multicast** element shall be included if the session is multicast. +- **video** – Information about the video channel(s). The **multicast** element shall be included if the session is multicast. +- **data** – Information about the data channel(s). +- **h245** – The transport address of the H.245 control channel. +- **callSignalling** – The transport address of the H.225.0 call signalling channel. +- **callType** – Provides information on call topology. +- **bandwidth** – Current usage in increments of 100 bit/s; includes only audio and video excluding headers and overhead. +- **callModel** – Indicates the endpoint's idea of which call model is in use. +- **callIdentifier** – A globally unique call identifier set by the originating endpoint which can be used to associate RAS signalling with the modified Q.931 signalling used in this Recommendation. +- **tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. +- **cryptoTokens** – Encrypted **tokens**. +- **substituteConfIDs** – A listing of all ConferenceIDs received in H.245 SubstituteCID messages pertaining to the original RAS **perCallInfo conferenceID**. +- **pdu**: + - **h323pdu** – A copy of an H.225.0 and Q.931 PDU as requested by the gatekeeper in **uuiiesRequested** in either ACF or IRQ. + - **sent** – Set to TRUE to indicate the endpoint sent the **h323pdu**; set to FALSE to indicate the endpoint received the **h323pdu**. +- **callLinkage** – The contents of this field are typically controlled by a call linkage service. For the procedures and semantics of this field, refer to clause 10/H.323. +- **usageInformation** – This field allows the endpoint to report usage information for this call. +- **circuitInfo** – This field provides information about the SCN circuit or circuits used for this call. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**needResponse** – If this is set to TRUE and the gatekeeper indicated in either RCF or ACF that it will respond to unsolicited IRRs (by setting **willRespondToIRR** to TRUE), then the gatekeeper shall reply with an IACK or INAK. If the gatekeeper had not indicated in either RCF or ACF that it will respond to unsolicited IRRs (by setting **willRespondToIRR** to FALSE), then the gatekeeper may ignore the **needResponse** BOOLEAN. + +**capacity** – Indicates the sending endpoint's call capacity at this point in time. When sending this field, the endpoint shall include the **currentCallCapacity** element and should only include the **maximumCallCapacity** when responding to an IRQ that included the **capacityInfoRequested** element. + +**irrStatus** – This element should be returned in IRR messages in response to an IRQ sent by the gatekeeper. Absence of this element indicates that the IRR message contains complete call detail information. The following values are possible: + +- **complete** – Indicates that this IRR contains the last segment of call information for an IRQ which requests all call details. When segmentation is not used, this field indicates that the IRR contains all of the call details in a single IRR message. +- **incomplete** – Indicates that the endpoint is not able to fit all of the requested call information in a single IRR message when responding to an IRQ message that contained a **callReferenceValue** of 0. +- **segment** – This field indicates the segment number, which is a monotonically increasing value modulo 65536, of this IRR message when segmented IRRs are sent in response to an IRQ containing a **callReferenceValue** of 0. +- **invalidCall** – This field indicates that the call referenced in the IRQ message does not exist. + +**unsolicited** – H.323 version 4 and later endpoints shall set this field to TRUE in unsolicited IRR messages as described in 8.4.2/H.323 and shall set it to FALSE it in solicited IRRs. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +### 7.15.3 InfoRequestAck (IACK) + +The IACK message includes the following: + +**requestSeqNum** – This field shall contain the **requestSeqNum** that was in the IRR. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +### 7.15.4 InfoRequestNak (INAK) + +The INAK message includes the following: + +**requestSeqNum** – This field shall contain the **requestSeqNum** that was in the IRR. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**nakReason** – Reason the IRR was negatively acknowledged. + +**altGKInfo** – Optional information about alternative gatekeepers. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +## 7.16 Non-standard message + +The **NonStandardMessage** structure is as follows: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**featureSet** – This field specifies a set of generic features. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +## 7.17 Message not understood + +This message is sent whenever an H.323 endpoint receives a RAS message it does not understand or it cannot decode. In cases where the destination transport address for the XRS message is not available (i.e., the received RAS message could not be decoded), the XRS may be sent to the transport address from which the not understood RAS message was received. This transport address may be obtained from the underlying transport layer. An XRS message shall not be sent in response to an incoming XRS message. H.323 endpoints should transmit no more than one XRS message per second to the same transport address to avoid network congestion in situations where corrupted messages are received. + +**RequestSeqNum** – Shall be the **requestSeqNum** of the unknown message, if it can be decoded. If the unknown message cannot be decoded, this field is a monotonically increasing number unique to the sender. The **RequestSeqNum** should be used for backward compatibility with H.323 version 3 and lower endpoints. H.323 version 4 and higher endpoints should look at the **messageNotUnderstood** parameter to associate the XRS with a previously transmitted message. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**messageNotUnderstood** – Copy of the message that was received and was not understood. + +## 7.18 Gateway resource availability messages + +The Resource Availability Indication (RAI) is a notification from a gateway to a gatekeeper of its current call capacity for each H-series protocol and data rate for that protocol. The gatekeeper responds with a Resource Availability Confirmation (RAC) upon receiving a RAI to acknowledge its reception. + +### 7.18.1 ResourcesAvailableIndicate (RAI) + +The RAI message includes the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any response associated with this specific message. + +**protocolIdentifier** – Identifies the vintage of the sending endpoint. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**endpointIdentifier** – A gatekeeper-assigned endpoint identity string. + +**protocols** – Indicates the current data rates for each protocol which can be supported given the current state of the device. + +**almostOutOfResources** – When set to TRUE, the device is nearing or at capacity. Any action based on this field is at the manufacturer's discretion. If the device is not near or at capacity this field should be set to FALSE. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**capacity** – Indicates the sending endpoint's call capacity at this point in time. Note that if **capacity** is provided, the **almostOutOfResources** BOOLEAN should be ignored by the recipient, since the **capacity** field provides more detailed information; however, the **almostOutOfResources** BOOLEAN shall be properly set in order to maintain backward compatibility. When sending the **capacity** field, the endpoint shall include the **currentCallCapacity** elements. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +### 7.18.2 ResourcesAvailableConfirm (RAC) + +The RAC message includes the following: + +**requestSeqNum** – This shall be the same value that was passed in the RAI. + +**protocolIdentifier** – Identifies the vintage of the accepting gatekeeper. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +## 7.19 RAS timers and Request in Progress (RIP) + +Table 24 shows recommended default time-out values for the response to RAS messages and subsequent retry counts if a response is not received. (These values are subject to change with further implementation experience and input.) + +**Table 24 – Recommended default time-out values** + +| RAS message | Time-out value (s) | Retry count | +|--------------|--------------------|-------------| +| GRQ | 5 | 2 | +| RRQ (Note 1) | 3 | 2 | +| URQ | 3 | 1 | + +**Table 24 – Recommended default time-out values** + +| RAS message | Time-out value (s) | Retry count | +|--------------------|---------------------------|--------------------| +| ARQ | 5 | 2 | +| BRQ | 3 | 2 | +| IRQ | 3 | 1 | +| IRR (Note 2) | 5 | 2 | +| DRQ | 3 | 2 | +| LRQ | 5 | 2 | +| RAI | 3 | 2 | +| SCI | 3 | 2 | + +NOTE 1 – The time-out value should be recalculated based upon both the time-to-live (which may be indicated by the gatekeeper in the RCF message) and the desired number of retries. +NOTE 2 – In cases where the gatekeeper is expected to reply to an unsolicited IRR with IACK or INAK, the time-out may occur if no reply to the IRR is received. + +If an entity receives a request from a version 2 (or later) entity to which a response cannot be generated within a typical retry time-out period, it can send a RIP message specifying the period (in the **delay** field) after which a response should have been generated. As soon as a response is available, the responding entity should send the response and not wait for the RIP delay to expire. If a requesting entity has not received a response by the time the RIP delay expires, it shall resend the request. The responding entity can then either send a duplicate response or another RIP message. Figure 2 gives an example message exchange which demonstrates a number of aspects of the retry strategy. + +Vendors should be aware that any retries will have an impact on the call setup time, which should be minimized. Therefore, short retry times are desirable. So that remote entities can anticipate typical retry times for the purpose of deciding when to send a RIP message, entities should avoid retry periods less than 100 ms. Exponential backoff and adapting to measured round-trip times is encouraged. Entities can use the measured round trip time of the RRQ/RCF registration process to modify an initially conservative estimate (of a few seconds) for this purpose. Entities may also use the registration process to exchange version numbers to ensure that the RIP-based retry mechanism is not used when version 1 entities are involved in the signalling. + +![Sequence diagram illustrating the use of RIP messages. The diagram shows two vertical lifelines. On the left, a message 'Lost LRQ' is sent to the right lifeline. A 'Retry delay (e.g. 200 ms)' is indicated. The right lifeline responds with 'RIP'. A 'RIP delay (e.g. 1 s)' is indicated. The left lifeline then sends another 'LRQ' to the right lifeline. The right lifeline responds with 'RIP'. A 'Lost LCF' message is shown being sent from the right lifeline to the left lifeline. A 'RIP delay' is indicated. Finally, the left lifeline sends a third 'LRQ' to the right lifeline, which responds with 'RIP'. The diagram is labeled 'H.225.0_F02' at the bottom right.](3481cde1adf61b0452dd6489dada6d6a_img.jpg) + +Sequence diagram illustrating the use of RIP messages. The diagram shows two vertical lifelines. On the left, a message 'Lost LRQ' is sent to the right lifeline. A 'Retry delay (e.g. 200 ms)' is indicated. The right lifeline responds with 'RIP'. A 'RIP delay (e.g. 1 s)' is indicated. The left lifeline then sends another 'LRQ' to the right lifeline. The right lifeline responds with 'RIP'. A 'Lost LCF' message is shown being sent from the right lifeline to the left lifeline. A 'RIP delay' is indicated. Finally, the left lifeline sends a third 'LRQ' to the right lifeline, which responds with 'RIP'. The diagram is labeled 'H.225.0\_F02' at the bottom right. + +**Figure 2 – Example use of RIP message** + +The RIP message includes the following: + +**requestSeqNum** – This is the requestSeqNum of the request which is currently being processed. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted tokens. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**delay** – Specifies the amount of time in milliseconds that an endpoint shall wait before attempting a retry. The responding endpoint may respond before this period expires. + +## 7.20 Service control messages + +### 7.20.1 ServiceControlIndication (SCI) + +The SCI message is sent from a service provider to indicate to the service client that a separate service control session may be initiated towards the given address. It may be sent from a gatekeeper to an endpoint (e.g., for user presentation of service features) or from an endpoint to a gatekeeper (e.g., to upload a call processing script). Note that H.323 entities of version 3 or earlier are not able to decode this message and thus will not answer. + +The SCI message contains the following: + +**requestSeqNum** – This is a monotonically increasing number unique to the sender. It shall be returned by the receiver in any response associated with this specific message. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**serviceControl** – Carries a set of service control session information. + +**endpointIdentifier** – Set to the value received from the gatekeeper in the RCF message if the message is sent from an endpoint to its gatekeeper. + +**callSpecific** – Provided if the sessions given are relating to one specific call. The **callIdentifier**, **conferenceID** and **answeredCall** shall be set to the same value as in the ARQ message the service session is relating to. + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**featureSet** – This field specifies a set of generic features. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +### 7.20.2 ServiceControlResponse (SCR) + +The SCR message is sent to acknowledge the receipt of an SCI message, but does not necessarily mean that the service client will initiate the session as given in SCI. + +The SCR message contains the following: + +**requestSeqNum** – This shall be the same value that was passed in the SCI. + +**result** – This field indicates the result of processing the information contained in the SCI message. The following values are defined: + +- **started** – The requested service control was started. +- **failed** – There was some error with the request, so the request failed. +- **stopped** – The service control was stopped. +- **notAvailable** – The requested service control was not available at the time of the request. + +**nonStandardData** – Carries information not defined in this Recommendation (for example, proprietary data). + +**tokens** – This is some data which may be required to allow the operation. The data shall be inserted into the message if available. + +**cryptoTokens** – Encrypted **tokens**. + +**integrityCheckValue** – Provides improved message integrity/message authentication of the RAS messages. The cryptographically-based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to **integrityCheckValue** computation, this field shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value in the **integrityCheckValue** field and transmits the message. + +**featureSet** – This field specifies a set of generic features. + +**genericData** – This field is a list of generic elements related to features that are defined outside of the base H.225.0 specification. These parameters may be used, for example, for tunnelling information transparently through RAS. + +## 7.21 AdmissionConfirmSequence + +AdmissionConfirmSequence is a sequence of one or more RAS ACF messages. It may used by the gatekeeper to respond to a single ARQ message instead of the single ACF message when it has different security tokens, different translated source information, etc., that may not easily be expressed in a single ACF message. Endpoints indicate support for receiving AdmissionConfirmSequence by setting **supportsACFSequences** flag in RRQ. + +## 7.22 Error Code Mapping + +A Gatekeeper that needs to return an **AdmissionReject** message in response to an **AdmissionRequest** from an endpoint, as a result of having received a **LocationReject** or an H.501 **AccessRejection** in response to its sending a **LocationRequest** or **AccessRequest** message, should use Tables 25 and 26 to map the error code that it returns in the **AdmissionReject** message. + +**Table 25 – LocationRejectReason to AdmissionRejectReason** + +| LocationRejectReason | Corresponding AdmissionRejectReason | +|--------------------------------|-------------------------------------| +| notRegistered | calledPartyNotRegistered | +| invalidPermission | invalidPermission | +| requestDenied | requestDenied | +| undefinedReason | undefinedReason | +| securityDenial | securityDenial | +| aliasInconsistent | aliasesInconsistent | +| routeCallToSCN | routeCallToSCN | +| resourceUnavailable | resourceUnavailable | +| genericDataReason | genericDataReason | +| neededFeatureNotSupported | neededFeatureNotSupported | +| hopCountExceeded | noRouteToDestination | +| incompleteAddress | incompleteAddress | +| securityWrongSyncTime | securityWrongSyncTime | +| securityReplay | securityReplay | +| securityWrongGeneralID | securityWrongGeneralID | +| securityWrongSendersID | securityWrongSendersID | +| securityMessageIntegrityFailed | securityMessageIntegrityFailed | +| securityWrongOID | securityWrongOID | +| securityDHmismatch | securityDHmismatch | +| noRouteToDestination | noRouteToDestination | +| unallocatedNumber | unallocatedNumber | + +**Table 26 – AccessRejectionReason to AdmissionRejectReason** + +| AccessRejectionReason | Corresponding AdmissionRejectReason | +|------------------------------|--------------------------------------------| +| noMatch | noRouteToDestination | +| packetSizeExceeded | undefinedReason | +| Security | securityDenial | +| hopCountExceeded | noRouteToDestination | +| needCallInformation | undefinedReason | +| noServiceRelationship | noRouteToDestination | +| undefined | undefinedReason | +| neededFeature | neededFeatureNotSupported | +| genericDataReason | genericDataReason | +| destinationUnavailable | resourceUnavailable | +| aliasesInconsistent | aliasesInconsistent | +| resourceUnavailable | resourceUnavailable | +| incompleteAddress | incompleteAddress | +| unknownServiceID | noRouteToDestination | +| usageUnavailable | undefinedReason | +| cannotSupportUsageSpec | undefinedReason | +| unknownUsageSendTo | undefinedReason | + +# 8 Mechanisms for maintaining QoS + +## 8.1 General approach and assumptions + +Transport QoS (Quality of Service) on a packet-based network includes such characteristics as: + +- bit error rate; +- packet loss rate; +- delay. + +Any transport QoS-related signalling (e.g., a reservation request to a router) is done by the terminal as soon as possible, or by the gatekeeper on its behalf. The terminal may wish to make any reservations since the gatekeeper may not be logically near the terminal, or be able to make QoS related requests on behalf of the terminal. The means by which either the terminal or the gatekeeper make QoS or bandwidth reservations are beyond the scope of this Recommendation. + +The Sender and Receiver Reports of RTCP shall be the means by which QoS will be assessed. + +There are two types of congestion-related delay that might be measured: + +- short-term increases in delay that will result in a perceptible but not annoying slowing of the frame rate; +- a general rise in delay due to packet-based network congestion over time such that a feedback-based mechanism is useful. + +Essentially, short-term bursts are approached by error concealment, and a longer-term congestion is approached by reducing the multimedia load. The assumption is made that all packet-based network multimedia terminals are H.323 terminals, and all will attempt to reduce packet-based network usage as congestion rises rather than "steal" bandwidth from each other. + +Bit errors on a packet-based network generally are either corrected at a lower layer, or result in packet loss, so they are not considered further in this clause. + +Packet loss requires the receiver to be able to compensate for lost packets in a fashion that conceals errors to the maximum possible extent. For data and control, retransmission at the transport layer is used. For audio and video, retransmission is for further study. + +A given level of transport QoS results in a level of user-perceived audio/video QoS that is a function in part of the effectiveness of the methods used to overcome transport QoS problems. + +## 8.2 Use of RTCP in measuring QoS + +### 8.2.1 Sender reports + +The sender report serves three main purposes: + +- 1) allows synchronization of multiple RTP streams, such as audio and video; +- 2) allows the receiver to know the expected data rate and packet rate; +- 3) allows the receiver to measure the distance in time to the sender. + +Of these three purposes, 1) is the most relevant to this Recommendation. Manufacturers may make use of the sender reports in other ways at their discretion. + +The relevant field for stream synchronization is the RTP timestamp and the NTP timestamp in the sender report of RTCP. The NTP timestamp (if available) gives "wall clock" time and corresponds to the RTP timestamp which has the same units and random offset as the RTP capture timestamp in the media packets. + +### 8.2.2 Receiver reports + +Four parts of the Receiver Reports are used in this Recommendation to measure QoS: + +- 1) fraction lost; +- 2) the cumulative packets lost; +- 3) the extended highest sequence number received; +- 4) interarrival jitter. + +Items 2 and 3 are used to compute the number of packets lost since the previous receiver report. This can be taken as a long-term measure of packet-based network congestion. See clause 6.4.4 of IETF RFC 3550 [37] for a sample computation. If this loss rate exceeds a value set by the manufacturer, the H.225.0 terminal should reduce the media rates on the packet-based network side according to the procedures in 8.4. If item 1 exceeds a value set by the manufacturer, it may also be desirable to take corrective action. + +If the interval between receiver reports exceeds a value set by the manufacturer, H.323 terminals should use item 1 as an indicator of serious congestion requiring media rate reduction on the packet-based network side. + +Item 4 should be used as an indication of impending congestion. If interarrival jitter increases for three consecutive receiver reports, the H.323 sending terminal should take corrective action. + +## 8.3 Audio/Video jitter procedures + +Rec. ITU-T H.245 provides commands and procedures for round-trip indications using **RoundTripDelayRequest** and **RoundTripDelayResponse**. On a multipoint call the MC responds to a request from the endpoint. RTCP contains a method of calculating round-trip delays based on the Sender Report and the Receiver Report messages. Note that the quantity being measured in each case is not the same, so there is no conflict in using both methods to measure jitter. + +See 6.2.5/H.323 for a discussion of how H.245 level signalling can be used to optionally reduce jitter related delays. + +## 8.4 Audio/Video skew procedures + +See 6.2.6/H.323 for a discussion of how H.245 level signalling is used to limit the skew between different logical channels. + +## 8.5 Procedures for maintaining QoS + +A number of methods exist for the H.323 gateway/terminal to respond to an increase in packet loss or interarrival jitter in the far-end receiver. These methods can be grouped into those that are appropriate for a rapid response to a short-term problem, such as a lost or delayed packet, and those that are appropriate for a response to a longer-term problem such as growing congestion on the packet-based network. Note that these methods do not seek to maintain the current quality of service, but instead to provide for an orderly degradation of service. The following priorities shall be observed such that, if present, media shall be degraded in the following order: Video, Data, Audio, Control. + +### *Short-term responses* + +- reducing the frame rate for a short period of time: This may result in the H.323 gateway sending additional H.261 fill frames in the packet-based network to SCN direction to compensate for the packet under flow; +- reduce packet rate by switching to the optional mode where audio/video are mixed in one packet (for further study); +- packet rate can also be reduced via the use of MB fragmentation of the video stream. + +### *Longer-term responses* + +- reducing media bit rate (e.g., switching from 384 kbit/s to 256 kbit/s): This may involve a simple instruction to the encoder in a terminal, or it may involve the use of a rate reducer function in the H.323 gateway. These changes are signalled via H.245 **FlowControl** commands, or by logical channel signalling as appropriate; +- turning off media of lesser importance (e.g., turning off video to allow a large amount of T.120 traffic); +- returning a busy signal (adaptive busy) to the receiver as an indication of packet-based network congestion. This may be combined with turning off a media, or even all media other than the control Transport Port. Adaptive busy is signalled via a Q.931 cause value in Release Complete. + +It should be noted that responding to interarrival jitter in a multi-router path where a large percentage of packets arrive out of order is difficult. It may be impossible to distinguish this source of jitter from other sources, or to base error recovery strategy on measured jitter. However, packet loss is quantifiable and unambiguous. + +## 8.6 Echo control + +Control of acoustic echo is the responsibility of the H-series terminal. In general, given the delay involved in video/audio compression, it is assumed that all H.320, H.323 and H.324 terminals have some form of echo control (cancellation or switching). + +However, when the H.323 terminal is on a call with a GSTN telephone, it is typically the case that the GSTN phone does not support echo control. Thus, the user of the H.323 terminal may hear acoustic echo return from the GSTN side. This acoustic echo return can be minimized by the use of a speakerphone with echo control, or the use of a handset or earphones. Manufacturers may add loss to the audio path when an H.323 terminal is connected to a GSTN POTS phone. + +Control of hybrid (2- to 4-wire) echo. The hybrid circuit provides an interface between 4-wire transmission systems and 2-wire terminals. For ISDN speech calls that are carried through the GSTN at 64 kbit/s, echo cancellation is not required. For 64 kbit/s data calls, echo cancellation is not permitted. + +In the case of a decomposed gateway interfacing to an SS7 network, indications of the provision of echo cancellation are carried in the ISUP signalling message. The Echo Control Logic (Rec. ITU-T Q.115.1) in the H.323 media gateway controller (MGC) taking into account the signalling information will request to either enable or disable the echo cancellation function at the media gateway (MG). + +For voiceband data calls (modem calls) tone disabling of echo cancellation is provided by the modems by in-band tones. + +# Annex A + +## RTP/RTCP + +(This annex forms an integral part of this Recommendation.) + +RTP and RTCP are defined in IETF RFC 3550 [37]. IETF RFC 3550 is also referred to in Appendix I. Both this annex and Appendix I are being retained in this Recommendation for maintaining equivalence with earlier versions of this Recommendation. + +The reader should note that all references in [37] are to a bibliography, and are non-normative, with the exception of the reference to ISO/IEC 10646, which also appears in the references clause of this Recommendation. + +Readers should also note that the terminology used in [37] differs somewhat from that used in Rec. ITU-T H.323 and in this Recommendation according to Table A.1. + +**Table A.1 – Terminology correspondence** + +| H.323 and H.225.0 term | [37] (RTP/RTCP) term | +|------------------------------|---------------------------| +| media stream | data | +| transport address | transport address | +| packet-based network address | network address | +| TSAP identifier | port | +| Annex A | specification or document | +| shall | must | +| should | should | + +It should be further noted that "translators" and "mixers" are not part of the H.323 system. H.323 endpoints such as gateways and MCUs have some of the characteristics of translators and mixers, so this text has been retained as a guide to the implementer. However, support for translators and mixers is not part of H.323, and these clauses shall be considered informative. + +# **Annex B** + +## **RTP profile** + +(This annex forms an integral part of this Recommendation.) + +RTP Profile is defined in IETF RFC 3551 [38]. IETF RFC 3551 is also referred to in Appendix II. Both this annex and Appendix II are being retained in this Recommendation for maintaining equivalence with earlier versions of this Recommendation. + +See the introduction to Annex A; all the warnings mentioned there apply to this annex as well. + +# Annex C + +## **RTP payload format for H.261 video streams** + +(This annex forms an integral part of this Recommendation.) + +RTP Payload format for H.261 video streams is defined in IETF RFC 4587 [39]. IETF RFC 4587 is also referred to in Appendix III. Both this annex and Appendix III are being retained in this Recommendation for maintaining equivalence with earlier versions of this Recommendation. + +See the introduction to Annex A; all the warnings mentioned there apply to this annex as well. + +# Annex D + +## RTP payload format for H.261A video streams + +(This annex forms an integral part of this Recommendation.) + +## D.1 Introduction + +To facilitate interfacing H.323 video streams to the SCN via gateways, Rec. ITU-T H.323 defines a modified form of the RTP H.261 video payload. This eases buffer management and interoperability with remote SCN codecs. Support of the H.261A payload type is signalled using H.245 capability sets and in the **openLogicalChannel** message using RTP dynamic payload types. + +## D.2 H.261A RTP packetization + +This version is an extension of the version described in Annex C except that an additional 32-bit word is appended to the H.261 header. The procedures that are described in Annex C also apply to this annex. + +The H.261A data will follow the RTP header, as in: + +![Diagram of an RTP packet structure showing the RTP header, H.261A header, and H.261 stream payload across four 32-bit words.](3b8ac904c44dd47c5ccd03def99a19c4_img.jpg) + +The diagram illustrates the structure of an RTP packet. It is divided into four 32-bit words, labeled 0, 1, 2, and 3 at the top. Each word contains 8 bytes, numbered 0 through 7. The first word (0) contains the RTP header. The second word (1) contains the H.261A header. The third word (2) and the fourth word (3) contain the H.261 stream payload. Vertical ellipses on the left and right sides of the diagram indicate that the packet can contain multiple such words. The label H.225.0\_FD.2A is located at the bottom right. + +Diagram of an RTP packet structure showing the RTP header, H.261A header, and H.261 stream payload across four 32-bit words. + +The H.261A header is defined as: + +![Diagram of the H.261A header structure, showing the H.261 header, LGOBN, Res, and Byte count fields.](ce5c6c3f1a6331655b939aaaaba0ecba_img.jpg) + +The diagram shows the structure of the H.261A header. It consists of four 32-bit words, labeled 0, 1, 2, and 3 at the top. Each word contains 8 bytes, numbered 0 through 7. The first word (0) contains the H.261 header. The second word (1) contains the Last GOB Number (LGOBN) in the first 4 bytes, Reserved (Res) in the next 4 bytes, and the start of the Byte count in the third word (2). The third word (2) contains the remaining 24 bits of the Byte count. The fourth word (3) contains the start of the H.261 stream payload. Vertical ellipses on the left and right sides of the diagram indicate that the packet can contain multiple such words. The label H.225.0\_FD.2B is located at the bottom right. + +Diagram of the H.261A header structure, showing the H.261 header, LGOBN, Res, and Byte count fields. + +The fields in the H.261A header have the following meanings: + +*H.261 header*: 32 bits – As described in Annex C. + +*Last GOB Number (LGOBN)*: 4 bits – The GOB number of the last GOB in the RTP packet (max GOB number is 12 for Rec. ITU-T H.261). + +*Reserved (RES)*: Reserved. + +*Byte Count*: 24 bits – Indicates the cumulative number of octets that have been sent in the H.261 stream part of the RTP packets. If the last byte of a packet is only partially filled (as indicated + +by EBIT), then it is not counted in the cumulative byte count. This modulo $2^{24}$ byte count starts at a random value and is never reset. + +Both of the additional fields may be used when packets are lost or delivered out of order. The Byte Count can be used to determine how much stuffing will be needed in the SCN stream and facilitates buffer management. The last GOB number simplifies determining which GOBs have been lost due to packet loss. + +# Annex E + +## Video packetization + +(This annex forms an integral part of this Recommendation.) + +This annex describes RTP packetization details for video codecs. Table E.1 provides references to the definitions of video packetization formats that are not defined in this Recommendation. The remaining clauses of this annex define additional video packetization formats. + +**Table E.1 – Externally defined video packetization formats** + +| Encoding name | Packetization definition | +|-----------------------------------|--------------------------------------------------------------------------| +| ISO/IEC 14496-2
(MPEG-4 Video) | IETF RFC 3016, RTP Payload Format for MPEG-4 Audio/Visual Streams | + +## E.1 H.263 + +An RTP payload format for H.263 video is specified in IETF RFC 2190 for H.263 video bitstreams that do not contain the new features adopted in version 2 (the 1998 version) of Rec. ITU-T H.263 (the features using PLUSPTYPE or annexes subsequent to Annex H/H.263). An additional payload format which supports the enhanced features of H.263 version 2 bitstreams will be specified at a later date. A legacy packetization format widely used in industry (not as specified in IETF RFC 2190) may only be used if the peer indicated support for this format in the capability exchange. + +RFC 3551 [38] section 5 describes the procedure to use to signal H.263 video streams. + +# Annex F + +## Audio and multiplexed packetization + +(This annex forms an integral part of this Recommendation.) + +This annex describes RTP packetization details for audio codecs. Table F.1 provides references to the definitions of audio packetization formats that are not defined by this Recommendation. Table F.2 provides references to the definitions of multiplexed packetization formats. The remaining clauses of this annex define additional audio packetization formats. + +**Table F.1 – Externally defined audio packetization formats** + +| Encoding name | Packetization definition | +|--------------------------------|--------------------------------------------------------------------------| +| ISO/IEC 14496-3 (MPEG-4 Audio) | IETF RFC 3016, RTP Payload Format for MPEG-4 Audio/Visual Streams | + +**Table F.2 – Externally defined multiplexed stream packetization formats** + +| Encoding name | Packetization definition | +|------------------------------------------------------|----------------------------------------------------------------| +| H.222 multiplexed streams (MPEG-2 transport streams) | IETF RFC 2250, RTP Payload Format for MPEG1/MPEG2 Video | + +## F.1 G.723.1 + +This Recommendation specifies a coded representation that can be used for compressing the speech signal component of multimedia services at a very low bit rate. A G.723.1 frame can be one of three sizes: 24 bytes (6.3 kbit/s frame), 20 bytes (5.3 kbit/s frame), or 4 bytes. These 4-byte frames are called Silence Insertion Descriptor (SID) frames and are used to specify comfort noise parameters. There is no restriction on how 4-, 20-, and 24-byte frames are intermixed. The least significant two bits of the first octet in the frame determine the frame size and codec type (refer to Table 5/G.723.1 and Table 6/G.723.1 for more information on bit order). It is possible to switch between the two rates at any 30 ms frame boundary. Both (5.3 kbit/s and 6.4 kbit/s) rates are a mandatory part of the encoder and decoder. This coder was optimized to represent speech with near-toll quality at the above rates using a limited amount of complexity. + +All the bits of the encoded bit stream are transmitted always from the least significant bit towards the most significant bit. Note that this refers to the order of bits presented to the transport layer and not the order of bits on the wire. + +G.723.1 packetization conforms to Annex B except for the packetization interval (30 ms vs. 20 ms default): + +- 1) The first packet of a talkspurt (first packet after a silence period) is distinguished by setting the marker bit in the RTP data header. +- 2) The sampling frequency (RTP clock frequency) is 8000 Hz. +- 3) The packetization interval shall have a duration of 30 ms (one frame) as opposed to the default packetization of 20 ms. +- 4) Codecs should be able to encode and decode several consecutive frames within a single packet. +- 5) A receiver should accept packets representing between 0 and 180 ms of audio data as opposed to the default of 0 and 200 ms. + +## F.2 G.728 + +#### 1) *Frame packetization:* + +A G.728 frame (4 vectors: V1-V4, 10 bits each, V1 is the older – first to be played) is organized into 5 bytes (B1-B5). Referring to the figure below, the principle for bit order is "maintenance of bit significance". Bits from older vectors are more significant than bit from newer vectors. The Most Significant Bit (MSB) of the frame goes to MSB of B1 and the Least Significant Bit (LSB) of the frame goes to LSB of B5. For clarification: more significant bits from each vector are put in more significant bits of B1-B5 (the more significant bits of lower number B). + +![Diagram illustrating the mapping of 40 bits from 4 vectors (V1-V4) into 5 bytes (B1-B5) for a G.728 frame. The diagram shows 40 bit positions (0-39) arranged in 4 groups of 10 (V1, V2, V3, V4). These are mapped into 5 bytes (B1-B5), each containing 8 bits. The mapping is as follows: V1 bits 0-7 go to B1 bits 0-7; V1 bits 8-9 and V2 bits 0-5 go to B2 bits 0-7; V2 bits 6-9 and V3 bits 0-3 go to B3 bits 0-7; V3 bits 4-9 and V4 bits 0-2 go to B4 bits 0-7; V4 bits 3-9 go to B5 bits 0-7. The diagram uses arrows and dashed lines to show this bit-level mapping. A label 'Frame 1' is at the bottom. A small code 'H.225.0_FF.2A' is in the bottom right corner.](6e9d059430baba0c363e33749f68b107_img.jpg) + +Diagram illustrating the mapping of 40 bits from 4 vectors (V1-V4) into 5 bytes (B1-B5) for a G.728 frame. The diagram shows 40 bit positions (0-39) arranged in 4 groups of 10 (V1, V2, V3, V4). These are mapped into 5 bytes (B1-B5), each containing 8 bits. The mapping is as follows: V1 bits 0-7 go to B1 bits 0-7; V1 bits 8-9 and V2 bits 0-5 go to B2 bits 0-7; V2 bits 6-9 and V3 bits 0-3 go to B3 bits 0-7; V3 bits 4-9 and V4 bits 0-2 go to B4 bits 0-7; V4 bits 3-9 go to B5 bits 0-7. The diagram uses arrows and dashed lines to show this bit-level mapping. A label 'Frame 1' is at the bottom. A small code 'H.225.0\_FF.2A' is in the bottom right corner. + +For example: + +B1 contains 8 most significant bits of V1, MSB of V1 is MSB of B1. + +B2 contains 2 least significant bits of V2, the more significant of the two in its MSB, and 6 most significant bits of V2, the most significant of them is more significant at B2 also. + +B1 shall be put first to the packet (most significant byte in RTP) and B5 last. + +#### 2) *Multi-frame packetization:* + +Ending a single frame in an RTP packet might cause considerable network overhead. Therefore, sending a multi-frame packet is allowed in the following manner: + +An RTP G.728 packet shall contain a whole number of frames. + +Older frames (to be played first) shall be put first into the RTP packet. + +The timestamp would reflect the capturing time of the first sample, in the first vector (V1) of the first frame (the oldest information in the packet). + +#### 3) The marker bit shall retain the same meaning assigned to it in this Recommendation. + +## F.3 G.729 + +This Recommendation specifies a coded representation that can be used for compressing the speech signal component of multimedia services at a bit rate of 8 kbit/s. This coder was optimized to represent speech with toll or wireline quality at 8 kbit/s. This coder has an inherent robustness against random bit errors as well as against randomly and bursty erased frames. It represents speech with a high quality when operating in a noisy environment. A complexity-reduced version of the G.729 algorithm is specified in Annex A/G.729. A floating point version of these two algorithms is specified in Annex C/G.729. The speech coding algorithms in the main body of Rec. ITU-T G.729, in Annex A/G.729 and in Annex C/G.729 are fully interoperable with each other, so there is no need to further distinguish between them. + +A Voice Activity Detector (VAD) and Comfort Noise Generator (CNG) algorithm in Annex B/G.729 is recommended. This algorithm is applied to Annex F/G.729 (6.4 kbit/s with VAD/CNG), Annex G/G.729 (11.8 kbit/s with VAD/CNG), Annex B/G.729 (G.729 and Annex A/G.729 with VAD/CNG) and Annex I/G.729. A G.729 or Annex A/G.729 frame contains 10 octets; an Annex D/G.729 frame contains 8 octets; an Annex E/G.729 frame contains 15 octets; and the + +Annexes B/G.729, F/G.729 and G/G.729 comfort noise frame occupies 2 octets, as shown in Figure F.1. + +![](c19f37cdfc7768db716bfc0cc5934cfb_img.jpg) + +| | | | | | | | | | | | | | | | | +|---|------|---|---|---|---|------|---|---|------|---|---|---|---|---|---| +| 0 | | | | | | | | | | 1 | | | | | | +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | +| L | LSF1 | | | | | LSF2 | | | GAIN | | | | R | | | +| S | | | | | | | | | | | | | | E | | +| F | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | S | | +| 0 | | | | | | | | | | | | | | V | | + +RESV Reserved (zero) H.225.0\_FF.1 + +**Figure F.1 – Annexes B/G.729, F/G.729 and G/G.729 CNG packetization format** + +The transmitted parameters of a G.729, Annex A/G.729 or Annex C/G.729 10-ms frame, consisting of 80 bits, are defined in Table 8/G.729. The mapping of these parameters is given in Figure F.2. Bits are numbered as Internet order, that is, the most significant bit is bit 0. + +![](54159e6d8f5ecc73ad262758e3a60677_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---|----|---|---|---|---|---|---|----|---|---|---|----|---|---|---|----|---|---|---|---|---|---|---|---|----|---|---|---|---|---|---| +| 0 | | | | | | | | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | +| L | L1 | | | | | | | L2 | | | | L3 | | | | P1 | | | | | | | | P | C1 | | | | | | | +| 0 | | | | | | | | | | | | | | | | | | | | | 0 | | | | | | | | | | | +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | | + + + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----|---|---|---|---|---|---|---|----|---|---|---|-----|---|---|-----|---|---|----|---|---|---|----|---|---|---|---|---|--|--| +| C1 | | | | | | | | S1 | | | | GA1 | | | GB1 | | | P2 | | | | C2 | | | | | | | | +| 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | | + + + +| | | | | | | | | | | | | | | | | +|----|---|---|---|---|----|---|---|---|-----|---|---|-----|---|---|---| +| C2 | | | | | S2 | | | | GA2 | | | GB2 | | | | +| 8 | 9 | 0 | 1 | 2 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 0 | 1 | 2 | 3 | + +H.225.0\_FF.2 + +**Figure F.2 – G.729, Annex A/G.729 and Annex C/G.729 packetization format** + +Annex D/G.729 defines a 6.4 kbit/s rate extension of G.729 for momentary reduction in channel capacity, e.g., to handle overload conditions. Annex E/G.729 provides an 11.8 kbit/s extension of G.729 for better performance with a wide range of input signals, such as speech with background noise and music. Additionally, Annex E/G.729 has two operating modes, backward and forward adaptive, which are signalled by the first two bits in the packet header. + +The bits of a G.729-6.4 frame are formatted as shown in Figure F.3 (see Table D.1/G.729). Bits are numbered in Internet order; that is, the most significant bit is bit 0. A total of 64 bits are used. + +![](3349dc82c6333221b0610be6ee7250b6_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|---|---|----|---|-----|---|-----|---|----|---|---|----|----|---|---|---|----|---|----|---|-----|---|-----|----|---|---|---|---|---|---|--|--|--|--|--|--| +| 0 | | | | | | | | 1 | | | | | | | | | | 2 | | | | | | | | | | 3 | | | | | | | | | | +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | | | | | | | +| L | L1 | | | | | | | L2 | | | | | L3 | | | | | P1 | | | | | | | C1 | | | | | | | | | | | | | +| 0 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | | | | | | | +| 3 | | | | | | | | 4 | | | | | | | | | | 5 | | | | | | | | | | 6 | | | | | | | | | | +| 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | | | | | | | +| C1 | | | | S1 | | GA1 | | GB1 | | P2 | | | | C2 | | | | | | S2 | | GA2 | | GB2 | | | | | | | | | | | | | | +| 6 | 7 | 8 | 0 | 1 | 0 | 1 | 2 | 0 | 1 | 2 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 0 | 1 | 0 | 1 | 2 | 0 | 1 | 2 | | | | | | | + +H.225.0\_FF.3 + +**Figure F.3 – G.729-6.4 packetization format** + +The net bit rate for the Annex E/G.729 algorithm is 11.8 kbit/s and a total of 118 bits are used. The bits of a G.729-12 frame are formatted as shown in Figures F.4 and F.5 (see Table E.1/G.729). Figures F.4 and F.5 describe the fields for the forward adaptive mode and the backward adaptive mode respectively for the Annex E/G.729 algorithm. The two least significant bits are included as "don't care" bits and are used to complete an integer number of octets for the frame. + +![](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------|---|---|----|------|---|---|---|------|---|------|---|------|----|---|---|------|---|----|---|------|---|---|---|----|---|------|---|---|---|---|---|--|--|--|--|--|--| +| 0 | | | | | | | | 1 | | | | | | | | | | 2 | | | | | | | | | | 3 | | | | | | | | | | +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | | | | | | | +| 0 | 0 | L | L1 | | | | | L2 | | | | | L3 | | | | | P1 | | | | | | | P | C0_1 | | | | | | | | | | | | +| 0 | 0 | 0 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 0 | 0 | 1 | 2 | | | | | | | | +| 3 | | | | | | | | 4 | | | | | | | | | | 5 | | | | | | | | | | 6 | | | | | | | | | | +| 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | | | | | | | +| C1_1 | | | | C2_1 | | | | | | C3_1 | | | | | | C4_1 | | | | | | | | | | | | | | | | | | | | | | +| 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | | | | | | | +| 6 | | | | | | | | 7 | | | | | | | | | | 8 | | | | | | | | | | 9 | | | | | | | | | | +| 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | | | | | | | +| GA1 | | | | GB1 | | | | P2 | | | | C0_2 | | | | C1_2 | | | | C2_2 | | | | | | | | | | | | | | | | | | +| 0 | 1 | 2 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 5 | | | | | | | +| 9 | | | | | | | | 1 | | | | | | | | | | 1 | | | | | | | | | | 1 | | | | | | | | | | +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | | | | | | | +| C3_2 | | | | | | | | C4_2 | | | | | | | | GA2 | | | | GB2 | | | | DC | | | | | | | | | | | | | | +| 6 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | | | | | | | | | | | | | | | + +H.225.0\_FF.4 + +**Figure F.4 – G.729-12 packetization format for the forward adaptive mode** + +![Diagram showing the G.729-12 packetization format for the backward adaptive mode. It consists of four rows of packets, each containing multiple frames. The first row shows packets 0, 1, 2, and 3. Packet 0 contains frame P1. Packet 1 contains frame P0 and frame C0_1. Packet 2 contains frame C1_1. Packet 3 contains frame P2. The second row shows packets 3, 4, 5, and 6. Packet 3 contains frame C2_1. Packet 4 contains frame C3_1. Packet 5 contains frame C4_1. Packet 6 contains frame GA1, frame GB1, and frame P2. The third row shows packets 6, 7, 8, and 9. Packet 6 contains frame C0_2. Packet 7 contains frame C1_2. Packet 8 contains frame C2_2. Packet 9 contains frame C3_2. The fourth row shows packets 9, 1, 1, 1, 1, 1, 1, 1, 1, 1. Packet 9 contains frame C3_2. Packet 1 contains frame C4_2. Packet 1 contains frame GA2. Packet 1 contains frame GB2. Packet 1 contains frame DC. The diagram also includes frame indices (0-9) and bit indices (0-7) for each frame.](dd00cc2325415c09afb8bf178f60f33b_img.jpg) + +H.225.0\_FF.5 + +Diagram showing the G.729-12 packetization format for the backward adaptive mode. It consists of four rows of packets, each containing multiple frames. The first row shows packets 0, 1, 2, and 3. Packet 0 contains frame P1. Packet 1 contains frame P0 and frame C0\_1. Packet 2 contains frame C1\_1. Packet 3 contains frame P2. The second row shows packets 3, 4, 5, and 6. Packet 3 contains frame C2\_1. Packet 4 contains frame C3\_1. Packet 5 contains frame C4\_1. Packet 6 contains frame GA1, frame GB1, and frame P2. The third row shows packets 6, 7, 8, and 9. Packet 6 contains frame C0\_2. Packet 7 contains frame C1\_2. Packet 8 contains frame C2\_2. Packet 9 contains frame C3\_2. The fourth row shows packets 9, 1, 1, 1, 1, 1, 1, 1, 1, 1. Packet 9 contains frame C3\_2. Packet 1 contains frame C4\_2. Packet 1 contains frame GA2. Packet 1 contains frame GB2. Packet 1 contains frame DC. The diagram also includes frame indices (0-9) and bit indices (0-7) for each frame. + +**Figure F.5 – G.729-12 packetization format for the backward adaptive mode** + +An RTP packet may consist of zero or more G.729 or Annex A, C, D or E/G.729 frames, followed by zero or one Annex B/G.729 payloads. The presence of a comfort noise frame can be deduced from the length of the RTP payload. + +- 1) The first packet of a talkspurt (first packet after a silence period) is distinguished by setting the marker bit in the RTP header. +- 2) The sampling frequency (RTP clock frequency) is 8000 Hz. +- 3) The default packetization interval should have a duration of 20 ms. While 20 ms is the strongly recommended value, in some situations it may be desirable to send 10-ms packets. For example, consider a transition from voiced to unvoiced in the first 10 ms of the packet. If a 20-ms packetization interval were mandatory, then the transmitter would need to wait until speech is active again. +- 4) Codecs should be able to encode and decode several consecutive frames within a single packet. +- 5) A receiver should accept packets representing between 0 and 200 ms of audio data. + +## F.4 Silence suppression + +This Recommendation states that coders may send silence frames before the stop transmission during a silence period. Since not all audio coders have in-band signalling for silence, a general mechanism at the RTP level should be defined. An example might be sending an empty RTP packet. This is for further study. + +## F.5 GSM codecs + +GSM speech codecs include: GSM full rate (FR) [F-1], GSM half rate (HR) [F-2] and GSM enhanced full rate (EFR) [F-3]. Each codec produces three different speech traffic frame types, i.e.: + +- Speech frames – Contains actual speech data; +- Idle frames – Indicates no voice activity, all data bits are set to one; +- Silence Descriptor (SID) frames – Indicates start of a silence period, data describes background noise. SID frames are marked inband with a fixed bit pattern. + +### F.5.1 Frame packetization + +With all three GSM codecs speech traffic frame bits are packed into RTP frame most significant bit (MSB) first. One RTP packet may contain one or more GSM speech traffic frames. All endpoints shall be capable of receiving and identifying an idle frame. An idle GSM speech frame is filled with binary 1s. + +If an endpoint sets the `comfortNoise` parameter to `TRUE`, it shall send SID frames as specified in the comfort noise and discontinuous transmission (DTX) specifications of a particular GSM codec. During a silent period, a new SID frame, with (possibly) updated noise information, is sent periodically, that is every 24th frame. After a silence period, the marker bit shall be set to 1 in RTP header. + +#### Full-rate codec + +GSM full-rate codec sends a 260-bit (32.5 octets) frame every 20 ms. This information shall be packed into RTP frame with a four-bit prefix (0xD or 1101 binary), called signature. Therefore GSM FR payload within RTP shall consist of 33 octets. SID (Silence Descriptor) frame is marked inband by a SID codeword stored into codec parameters as described in reference [F-4] below. The payload size of a SID frame is 33 octets. The signature of a full rate SID frame shall be same as that of a full rate speech frame (0xD). RTP coded FR speech shall have a bit rate of 13 200 bit/s, not including the packetization overhead. + +#### Half-rate codec + +GSM half-rate codec sends a 112-bit (14 octets) frame every 20 ms. This information shall be packed into an RTP header without any prefixes/signatures. SID frame is marked inband by a SID codeword stored into codec parameters as described in reference [F-4] below. The payload size of a SID frame is 14 octets. RTP coded speech shall have a bit rate of 5600 bit/s, not including the packetization overhead. + +#### Enhanced full rate + +GSM EFR codec sends a 244-bit (30.5 octets) frame every 20 ms. This information shall be packed into an RTP header with a four-bit prefix (0xC or 1100 binary), called "signature". Therefore, GSM EFR payload within RTP shall consist of 31 octets. SID frame is marked inband by a SID codeword stored into codec parameters as described in reference [F-4] below. The payload size of a SID frame is 31 octets. RTP-coded EFR speech shall have a bit rate of 12 400 bit/s, not including the packetization overhead. + +### F.5.2 Informative references + +- [F-1] GSM 06.10 (ETS 300 961), *Digital cellular telecommunications system; Full rate speech; Transcoding*. +- [F-2] GSM 06.60 (ETS 300 726), *Digital cellular telecommunications system; Enhanced Full Rate (EFR) speech transcoding*. +- [F-3] GSM 06.20 (ETS 300 969), *Digital cellular telecommunications system; Half rate speech; Half rate speech transcoding*. + +- [F-4] ETSI, TIPHONE 03 001 (TS 101 318), *Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); Using GSM speech codecs within Recommendation ITU-T H.323*. +- [F-5] GSM 06.31 (ETS 300 964), *Digital cellular telecommunications system; Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels*. +- [F-6] GSM 06.81 (ETS 300 729), *Digital cellular telecommunications system; Discontinuous Transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels*. +- [F-7] GSM 06.41 (ETS 300 972), *Digital cellular telecommunications system; Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels*. +- [F-8] GSM 06.12 (ETS 300 963), *Digital cellular telecommunications system; Full rate speech; Comfort noise aspect for full rate speech traffic channels*. +- [F-9] GSM 06.62 (ETS 300 728), *Digital cellular telecommunications system; Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels*. +- [F-10] GSM 06.22 (ETS 300 971), *Digital cellular telecommunications system; Half rate speech; Comfort noise aspect for the half Rate speech traffic channels*. +- [F-11] GSM 08.60 (ETS 300 737), *Digital cellular telecommunications system; (Phase 2+) (GSM); In-band control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels*. + +## F.6 G.722.1 + +The speech coding algorithm defined in Rec. ITU-T G.722.1 encodes wideband audio signals with a 50 Hz to 7 kHz bandwidth into one of two bit rates, 24 kbit/s or 32 kbit/s, using 20 ms frames and a sampling rate clock of 16 kHz. The bit rate can be changed at any 20-ms frame boundary, although rate change notification is not provided inband with the bitstream. When operating at 24 kbit/s, 480 bits (60 octets) are produced per frame, and when operating at 32 kbit/s, 640 bits (80 octets) are produced per frame. Thus, both bit rates allow for octet alignment without the need for padding bits. + +The number of bits in a frame is fixed. However, within this fixed frame, G.722.1 uses variable length coding (e.g., Huffman coding) to represent most of the encoded parameters. Except for the categorization control bits parameter, all other bit stream parameters are represented by variable length codes, a variable number of bits. Figure F.6 illustrates this point and the order of the transmitted parameter fields. All variable length codes and the categorization control bits are transmitted in order from the leftmost (most significant (MSB)) bit to the rightmost (least significant (LSB)) bit. The use of Huffman coding means that it is not possible to identify the various coder parameters/fields contained within the bit stream without first completely decoding the entire frame. + +![Diagram of G.722.1 major bitstream fields and their order of transmission. It shows three fields: amplitude envelope bits, categorization control bits, and MLT coefficients bits. The first and third fields have a variable number of bits, while the middle field has 4 bits. Arrows indicate the transmission order from left to right.](a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg) + +| | | | +|------------------------------------------------------------|-----------------------------------|---------------------------------------------------------| +| First bit transmitted

amplitude
envelope
bits | categorization
control
bits | Last bit transmitted

MLT
coefficients
bits | +|------------------------------------------------------------|-----------------------------------|---------------------------------------------------------| + +← variable number of bits → +← 4 bits → +← variable number of bits → + +Diagram of G.722.1 major bitstream fields and their order of transmission. It shows three fields: amplitude envelope bits, categorization control bits, and MLT coefficients bits. The first and third fields have a variable number of bits, while the middle field has 4 bits. Arrows indicate the transmission order from left to right. + +**Figure F.6 – G.722.1 major bitstream fields and their order of transmission** + +Figure F.7 illustrates how the G.722.1 bit stream maps into an octet-aligned RTP payload. The encoder bit stream is split into a sequence of octets (60 or 80 depending on the bit rate), and each octet is in turn mapped into an RTP octet. + +An RTP packet shall only contain G.722.1 frames of the same bit rate. The RTP timestamp shall be in units of 1/16 000th of a second. + +![Diagram showing the mapping of G.722.1 encoded bitstream to RTP. A long horizontal bar represents the 'Sequence of bits (480 or 640) generated by the G.722.1 encoder for transmission'. Above the left end is 'First bit transmitted' and above the right end is 'Last bit transmitted'. Below this bar, vertical lines divide the sequence into segments. At the bottom, these segments are mapped to RTP octets. The first three are labeled 'RTP octet 1', 'RTP octet 2', and 'RTP octet 3', each containing 'MSB ... LSB'. An ellipsis indicates more octets. The final octet is labeled 'RTP octet 60 or 80' and also contains 'MSB ... LSB'.](ae57a92114d2bd84ef81129e7fbdd89d_img.jpg) + +Diagram showing the mapping of G.722.1 encoded bitstream to RTP. A long horizontal bar represents the 'Sequence of bits (480 or 640) generated by the G.722.1 encoder for transmission'. Above the left end is 'First bit transmitted' and above the right end is 'Last bit transmitted'. Below this bar, vertical lines divide the sequence into segments. At the bottom, these segments are mapped to RTP octets. The first three are labeled 'RTP octet 1', 'RTP octet 2', and 'RTP octet 3', each containing 'MSB ... LSB'. An ellipsis indicates more octets. The final octet is labeled 'RTP octet 60 or 80' and also contains 'MSB ... LSB'. + +**Figure F.7 – G.722.1 encoded bitstream mapping to RTP** + +## F.7 TIA/EIA-136 ACELP + +This vocoder is optimized for TIA/EIA-136 TDMA Digital Cellular and PCS systems. It includes voice activity detection (VAD), lost frame substitution and comfort noise generation (CNG) capabilities. The sampling rate is 8000 Hz and the compressed voice frame length is 20 ms. The vocoder produces a 148-bit speech-vector, s0 through s147, for each 20-ms voice frame. s0 is the most significant bit (MSB). Please refer to section 4 of reference [F.7-1] for more details. + +### F.7.1 TIA/EIA-136 ACELP frame format + +A speech indicator flag bit, SP, shall be generated by the vocoder and set to "1" to indicate a speech frame, or "0" to indicate a silence (comfort-noise) frame. This SP flag bit shall be inserted in bit-position 148. Bit position 149 is the BFI\_CN (bad frame or comfort noise indicator) and bit position 150 is the CNU flag (comfort noise update). Bit position 151 shall always be set to 0. + +The logical combinations of these three flags are described below. + +The 152-bit (19-octet) transmit frame is depicted in Figure F.8. Octets are formed starting with the LSB and moving towards the MSB. The LSB is transmitted first. + +| bit 0 (MSB) | 1 ... 146 | 147 | 148 | 149 | 150 | bit 151 (LSB) | +|-----------------------------|-------------|------|------|--------|------|---------------| +| s0 | s1 ... s146 | S147 | SP | BFI_CN | CNU | Always 0 | +| Speech vector/Comfort noise | | | Flag | Flag | Flag | Padding bit | + +**Figure F.8 – ACELP vocoder voice frame** + +### F.7.2 TIA/EIA-136 ACELP silence suppression mode + +In silence mode, the vocoder generates an ambient noise frame representation. This frame is used by the vocoder at the receiving end to regenerate the ambient noise of the transmitting end. The CN (comfort noise) parameters vector consists of only 38 bits, to which the three flag bits and seven padding bits (consisting of all zeros) are appended to form a six-octet frame. + +The 48-bit (6-octet) CN frame is depicted in Figure F.9. Octets are formed starting with the LSB and moving towards the MSB. The LSB is transmitted first. + +| bit 0 (MSB) | 1 ... 37 | 38 | 39 | 40 | 41 | 41-47 (LSB) | +|-----------------------------|--------------|------|------|--------|------|-------------| +| Cn0 | cn1 ... cn37 | S147 | SP | BFI_CN | CNU | Always 0 | +| Speech vector/Comfort noise | | | Flag | Flag | Flag | Padding bit | + +Key: + +SP Speech indicator + +BFI\_CN Bad Frame Indicator/Comfort Noise Indicator + +CNU Comfort Noise Update + +The logical values of these flags and their meanings are defined below: + +SP: 1 = speech frame; 0 = non-speech (comfort noise frame) + +BFI\_CN: + +If SP = 1 + +And BFI\_CN = 1 + +Then, this is a bad-voice frame + +Otherwise ( BFI\_CN = 0), this is a good voice-frame + +If SP = 0 + +And BFI\_CN = 1 + +Then this is a bad comfort-noise frame + +Otherwise ( BFI\_CN = 0), this is a good comfort-noise frame + +CN: + +If SP = 0 + +And BFI\_CN = 0 + +And CN = 1 + +Then, this is an update comfort noise frame + +Otherwise it is a non-valid CN frame + +NOTE – A wireless mobile vocoder shall set the BFI\_CN to 0. The receiving base station may set this flag to 1 if it is unable to correct errors introduced by the radio channel. + +**Figure F.9 – ACELP vocoder silence suppression frame** + +### F.7.3 TIA/EIA-136 ACELP packetization + +The packetization of IS-ACELP shall be in conformance with Annex B. + +- 1) The packetization duration shall be a whole multiple of 20 ms. +- 2) A packet may consist of one or more frames each. +- 3) Codecs should be able to encode and decode several consecutive frames within a single packet. +- 4) All the bits of the encoded bit stream are transmitted always from the least significant bit towards the most significant bit. + +### F.7.4 TIA/EIA-136 ACELP referenced standard + +[F.7-1] TIA/EIA-136, part 410, *TDMA Cellular/PCS – Radio Interface, Enhanced Full Rate Voice Codec (ACELP)*. Formerly IS-641. + +## F.8 TIA/EIA-136 US1 + +This vocoder is optimized for TIA/EIA-136 TDMA Digital Cellular and PCS systems. Reference [F.8-1] provides a detailed description of the vocoder. + +### F.8.1 TIA/EIA-136 US1 frame format + +The sampling rate is 8000 Hz and the compressed voice frame-length is 20 ms. The vocoder produces 244 ordered bits per voice frame. Three flag bits, BFI, SID and TAF, are added to the speech vector. One padding bit (in bit position 247) is added to form a whole number of octets (31). The last bit is referred to as the least significant bit (LSB). This vocoder also supports DTX (discontinuous transmission) silence mode. + +The transmit voice frame structure is shown in Figure F.10. + +| MSB – bit 0 | 1 ... 243 | 244 | 245 | 246 | 247 (LSB) | +|---------------|-------------|------|------|------|-------------| +| s0 | s1 ... s243 | BFI | SID | TAF | Always 0 | +| Speech vector | | Flag | Flag | Flag | Padding bit | + +**Figure F.10 – US1 vocoder voice frame** + +### F.8.2 TIA/EIA-136 US1 silence mode frames (TX-DTX) + +In silence mode, special frames called SID (for silence descriptor) frames are transmitted in a schedule specified in section 1.3 of reference [F.8-1]. + +A SID frame contains the same number of bits as normal speech frames, but the bit-map is different. See reference [F.8-1] for details. The SID frame contains comfort noise (CN) parameters and a 95-bit SID code-word. The SID code-word is all "0"s. Other unused bits in the 244-bit vector payload are also set to "0". (See Figure F.11.) + +| MSB – bit 0 | 1 ... 243 | 244 | 245 | 246 | 247 (LSB) | +|----------------------|---------------|------|------|------|-------------| +| cn0 | cn1 ... cn243 | BFI | SID | TAF | Always 0 | +| Comfort noise vector | | Flag | Flag | Flag | Padding bit | + +**Figure F.11 – Base station to landline, +comfort noise transmit frame (US1)** + +The logic of the BFI, SID and TAF flags is similar to the equivalent flags of the TIA/EIA-136 ACELP vocoder, described in F.7. + +### F.8.3 TIA/EIA-136 US1 packetization + +The packetization shall be in conformance with Annex B. + +- 1) The packetization duration shall be a whole multiple of 20 ms. +- 2) A packet may consist of zero, one or more frames each. +- 3) Codecs should be able to encode and decode several consecutive frames within a single packet. +- 4) All the bits of the encoded bit stream are transmitted always from the least significant bit towards the most significant bit. + +### F.8.4 TIA/EIA-136 US1 reference standard + +[F.8-1] TIA/EIA-136, part 430, *TDMA Cellular/PCS – Radio Interface, US1 Full Rate Voice Codec*. + +## F.9 IS-127 EVRC + +### F.9.1 IS-127 EVRC description + +#### F.9.1.1 General + +The TIA/EIA IS-127 Enhanced Variable Rate Codec (EVRC) is optimized for TIA/EIA IS-95 CDMA Digital Cellular and PCS systems. The sampling rate is 8000 samples per second and the voice frame length is 20 ms (that is, 160 samples per frame). EVRC encodes active speech at full rate or half rate and background noise (no speech present) at one eighth rate. It delivers toll quality speech at very low average bit rate. A detailed description of the EVRC codec can be found in the publicly available TIA/EIA IS-127 standard [F.9-1]. + +#### F.9.1.2 Compression rates + +The EVRC coder compresses its input signal using one of three rates: full-rate (rate 1), half-rate (rate 1/2), and eighth-rate (rate 1/8). Full- and half-rates are used primarily for encoding active speech while the eighth-rate is used for encoding background noise (silence mode). All frames are 20 ms long, regardless of encoding rate. + +#### F.9.1.3 Blanked packets + +To allow for in-band signalling or for secondary traffic (see section 1.4.1 of [F.9-1]), voice frames are blanked. The generated voice packet is simply not used and the decoder treats it as an erased packet. See [F.9-1] for details. + +#### F.9.1.4 Half rate + +Half-rate encoding is used, instead of the normal full-rate, when a signalling message has to be added to the traffic channel. + +#### F.9.1.5 Null 1/8 rate traffic channel data + +A rate one-eighth packet in which all bits are set to "1" is considered null Traffic Channel data. Such packets are declared "erased packets" and are handled as described in section 5 of [F.9-1]. + +Rate information and channel coding bits are added to the vocoder output bits for transport over the air, in accordance with TIA/EIA IS-95. + +The packet types, number of bits-per-packet, raw vocoder bit-rates and the aggregate rates (vocoder bits plus additional bits) are shown in Table F.3. + +**Table F.3 – EVRC packets and bit rates** + +| Packet type
(3 bits) | Rate | Bits/packet | Vocoder bit
rate | Aggregate rate | +|-------------------------|-----------------------------------------|-------------|---------------------|----------------| +| 1 | Full | 171 | 8.55 | 9.6 | +| 2 | Half | 80 | 4.0 | 4.8 | +| 3 (Note) | Fourth (service option-1 compatibility) | 40 | | | +| 4 | Eighth | 16 | 0.8 | 1.2 | +| 5 | Blanked | 0 | – | – | +| 6 | Full-rate with errors | 171 | – | – | +| 7 | Bad frame (erasure) | 0 | – | – | + +NOTE – Type 3 packets may only be generated by older IS-96 encoders. The IS-127 decoder shall treat these packets as erased-packets. + +### F.9.2 IS-127 EVRC packetization + +#### F.9.2.1 General requirements + +The transmission packetization shall be in conformance with Annex B. + +- 1) The packetization duration shall be a whole multiple of 20 ms. +- 2) A transmission packet may consist of zero, one, or more frames. +- 3) Codecs should be able to encode and decode several consecutive frames within a single transmission packet. +- 4) All the bits of the encoded bit stream shall always be transmitted from the least significant bit towards the most significant bit. + +#### F.9.2.2 Frame formats + +##### F.9.2.2.1 Full rate – F1 + +The EVRC full-rate, 176-bit (22-octet) transmit frame (F1), is depicted in Figure F.12. Octets are formed starting with the LSB and moving towards the MSB. The LSB (bit 175) is transmitted first. + +| Bit 0 (MSB) | Bits 1 through 170 | Bits 171 through 175 (LSB) | +|---------------|--------------------|----------------------------| +| s0 | s1 ... s170 | Always 0 | +| Speech vector | | Padding bits | + +Figure F.12 – F1, Full-rate EVRC frame + +##### F.9.2.2.2 Half rate – F2 + +The EVRC half-rate, 80-bit (10-octet) transmit frame (F2) is depicted in Figure F.13. Octets are formed starting with the LSB and moving towards the MSB. The LSB (bit 79) is transmitted first. + +| Bit 0 (MSB) | Bits 1 through 79 (LSB) | +|---------------|-------------------------| +| s0 | s1 ... s79 | +| Speech vector | | + +Figure F.13 – F2, Half-rate EVRC frame + +##### F.9.2.2.3 Eighth Rate – F3 + +The EVRC eighth-rate, 16-bit (2-octets) transmit frame (F3) is depicted in Figure F.14 below. Octets are formed starting with the LSB and moving towards the MSB. The LSB (bit 15) is transmitted first. + +| Bit 0 (MSB) | Bits 1 through 15 (LSB) | +|---------------|-------------------------| +| s0 | s1 ... s15 | +| Speech vector | | + +Figure F.14 – F3, Eighth-rate EVRC frame + +### F.9.3 IS-127 EVRC reference standards + +[F.9-1] TIA/EIA IS-127 (1997), *Enhanced Variable Rate Codec, Speech Service Option 3 for Wideband Spread Spectrum Digital Systems*. + +[F.9-2] TIA/EIA IS-95-B (1999), *Mobile Station-Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Systems*. + +## F.10 H.223 MUX-PDU packetization + +### F.10.1 Introduction + +The H.223 MUX-PDU is used by a packet-oriented multiplexing protocol designed for the exchange of one or more information streams between higher-layer entities such as data and control protocols and audio and video codecs, as defined in Rec. ITU-T H.223. + +Each information stream is represented by an H.245 unidirectional logical channel which is identified by a unique Logical Channel Number (LCN), an integer between 0 and 65535. LCN 0 is a permanent logical channel assigned to the H.245 control channel. All other logical channels are dynamically opened and closed by the transmitter using the H.245 OpenLogicalChannel and CloseLogicalChannel messages. All necessary attributes of the logical channel are specified in the OpenLogicalChannel message. For applications that require a reverse channel, a procedure for opening bidirectional logical channels is also defined in Rec. ITU-T H.245. + +The general structure of the multiplexer is shown in Figure 2/H.223. The multiplexer consists of two distinct layers: a Multiplex (MUX) layer and an Adaptation Layer (AL). + +Support of the H.223 payload type is signalled using H.245 capability sets and in the H.245 openLogicalChannel message using RTP dynamic payload types. + +### F.10.2 MUX-PDU packetization format + +The H.223 MUX-PDU specified by Figure 3/H.223 is carried as payload data within the RTP protocol. The order of bit transmission is specified in 3.2.2/H.223, and the field mapping convention is in 3.2.3/H.223. + +Though a MUX-PDU can occupy more than one RTP packet, a MUX-PDU shall start with the first octet of an RTP packet payload. + +Each RTP packet contains a timestamp that is derived from the sender's clock reference. The timestamp shall represent the target transmission time of the first byte of the H.223 MUX-PDU. The primary purpose of this timestamp is for the receiver to estimate and reduce any network-induced jitter, and to reproduce the H.223 bitstream with constant bit rate. + +The usage of the fields of the RTP header shall be as follows: + +- 1) An RTP dynamic payload type is used. +- 2) The RTP timestamp represents the target transmission time for the first byte of the MUX-PDU in the packet over the H.223 constant bitrate channel. This timestamp is derived from the clock frequency with a default value of 90 kHz. The sender can change this frequency, and the selected value is signalled by the **BitRate** parameter in the **H223Capability** structure in H.245 messages. If a MUX-PDU occupies more than one RTP packet, the RTP timestamp shall be the same on successive packets. The timestamp should be calculated based on the number of bytes included in the transmitted MUX-PDUs. +- 3) The marker bit of the RTP header is set to one in the last packet of a MUX-PDU, and otherwise must be zero. Thus, it is not necessary to wait for a following packet to detect the MUX-PDU boundary. + +The H.223 MUX-PDU follows the RTP header, as in: + +| | | +|------------|--------------| +| RTP header | MUX-PDU data | +|------------|--------------| + +# Annex G + +## Communication between and within administrative domains + +(This annex forms an integral part of this Recommendation.) + +## G.1 Scope + +It is expected that the overall H.323 network will consist of smaller subsets of equipment organized in some manner, such as by Administrative Domain. Because of the potentially large numbers of H.323 elements that will exist in H.323 networks, an efficient protocol is needed to allow calls to be completed between Administrative Domains. The most elementary example is for a user (an endpoint) in one Administrative Domain to reach a user (an endpoint) serviced by another Administrative Domain. While the H.225.0 RAS protocol can address many of the needs for communication between Administrative Domains, it is neither complete nor efficient for this purpose. + +For the same reason, an efficient protocol also needs to be specified between H.323 elements within the same Administrative Domain. + +This annex describes methods to allow address resolution, access authorization and usage reporting between and within Administrative Domains in H.323 systems for the purpose of completing calls. H.323 elements that communicate using the procedures described in this annex are known as Peer Elements. An Administrative Domain exposes itself to other Administrative Domains through a type of logical element known as a Border Element. Border Elements are special cases of Peer Elements, at least one of whose peers belongs to another Administrative Domain. A Peer Element may be co-located with any other entity (for example, with a gatekeeper). This annex does not require an Administrative Domain to reveal details about its organization or architecture. This annex does not mandate a specific system architecture within an Administrative Domain. Furthermore, this annex supports the use of any call model (gatekeeper routed versus direct endpoint). + +The general procedure is for Peer Elements to exchange information regarding the addresses each can resolve. Border Elements exchange information regarding the addresses their Administrative Domains can resolve. Addresses can be specified in a general manner or in an increasingly specific manner. Additional information allows elements within an Administrative Domain to determine the most appropriate Administrative Domain to serve as the destination for the call. Border Elements may control access to their exposed addresses, and require reports on the usage made during calls to those addresses. + +Figure G.1 indicates a number of reference points representing signalling among various elements in an H.323 network. In Figure G.1, the Administrative Domains are part of a global packet network without edges. Note that Figure G.1 is not an explicit definition of an H.323 system architecture, but is meant to illustrate signalling reference points. + +![Diagram of System reference points showing two administrative domains, A and B, connected by a central 'Back end services' node. Each domain contains 'Peer element' and 'Border element' nodes. Reference points are labeled: A (between border elements), B (between border and peer elements), C (between peer elements), and D (between elements and back-end services).](6ca842602b0473809416a9cf0d4106a4_img.jpg) + +The diagram illustrates the system reference points for H.323 elements across two administrative domains, A and B. At the top center is a box labeled 'Back end services'. Below it, two large circles represent 'Administrative domain A' (left) and 'Administrative domain B' (right). Inside each domain, there are 'Peer element' and 'Border element' boxes. In domain A, one 'Peer element' is connected to a 'Border element' (reference point B), and another 'Peer element' is connected to the first 'Peer element' (reference point C). The 'Border element' in domain A is connected to the 'Back end services' (reference point D) and to the 'Border element' in domain B (reference point A). The 'Border element' in domain B is also connected to the 'Back end services' (reference point D) and to a 'Peer element' (reference point B). The second 'Peer element' in domain B is connected to the first 'Peer element' (reference point C). Reference point D is also shown between the 'Peer element' and 'Back end services' in both domains. A small label 'H.225.0\_FG.1' is in the bottom right corner. + +Diagram of System reference points showing two administrative domains, A and B, connected by a central 'Back end services' node. Each domain contains 'Peer element' and 'Border element' nodes. Reference points are labeled: A (between border elements), B (between border and peer elements), C (between peer elements), and D (between elements and back-end services). + +**Figure G.1 – System reference points** + +Figure G.1 indicates the following reference points: + +A – Between Border Elements belonging to different Administrative Domains. + +B – Between Border Elements and Peer Elements within the same Domain. + +C – Between Peer Elements within the same Domain. + +D – Between H.323 elements and back-end services (not in the scope of this annex). + +Reference points A, B and C are the focus of this annex. As was mentioned earlier, a Peer Element may be co-located with some other H.323 element. + +Subclause G.7, Signalling examples, provides some signalling examples that may aid understanding. + +## G.2 Definitions + +This annex defines the following terms: + +**G.2.1 administrative domain:** An Administrative Domain is a collection of H.323 entities administered by one administrative entity. An Administrative Domain can consist of one or more gatekeepers (that is, one or more zones). + +**G.2.2 back-end services:** Back-End Services are functions such as user authentication or authorization, accounting, billing, rating/tariffing, etc. Back-end services and the protocol to exchange information with back-end services (if different than that in this annex) are not in the scope of this annex. + +**G.2.3 peer element:** As defined in Rec. ITU-T H.501, a Peer Element is a logical element that originates or terminates signalling messages defined in that Recommendation. This element may exist in combination with other H.323 elements, for example a combination of Peer Element, gatekeeper and gateway. An Administrative Domain may contain any number of Peer Elements. + +**G.2.4 border element:** A special case of the Peer Element, the Border Element is a functional element with at least one peer that is outside of its Administrative Domain. It supports public access into an Administrative Domain for the purposes of call completion or any other services that involve + +multimedia communication with other elements within the Administrative Domain. The Border Element controls the external view of the Administrative Domain. + +**G.2.5 clearing house:** A service (possibly in the form of a Border Element) that can provide resolution for all addresses (i.e., a type of aggregation point). + +## G.3 Abbreviations + +This annex uses the following abbreviations: + +| | | +|-----|--------------------------| +| AD | Administrative Domain | +| BE | Border Element | +| CH | Clearing House | +| DST | Daylight Saving Time | +| EP | Endpoint | +| GK | Gatekeeper | +| GW | Gateway | +| PE | Peer Element | +| SCN | Switched Circuit Network | +| T | Terminal | + +## G.4 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- Recommendation ITU-T H.323 (2006), *Packet-based multimedia communications systems*. +- Recommendation ITU-T H.501 (2002), *Protocol for mobility management and intra/inter-domain communication in multimedia systems*. +- Recommendation ITU-T H.460.2 (2001) *Number Portability Interworking between H.323 and SCN networks*. + +## G.5 System models + +This annex does not mandate a specific system architecture among Administrative Domains or within an Administrative Domain. The following subclauses provide some sample architectures, but these are to be viewed as illustrative rather than exhaustive. + +Remember that a Peer Element is a functional element that may exist together with any other H.323 element. Figure G.2 shows some examples of Peer Element implementations in combination with other elements. + +![Figure G.2: Peer element placement examples. Three boxes show different internal structures: 1) Gatekeeper over Peer element; 2) Gateway over Peer element; 3) Gateway over Gatekeeper over Peer element. H.225.0_FG.2](f2b561f8d2d2b8402379552179d9fbef_img.jpg) + +Figure G.2: Peer element placement examples. Three boxes show different internal structures: 1) Gatekeeper over Peer element; 2) Gateway over Peer element; 3) Gateway over Gatekeeper over Peer element. H.225.0\_FG.2 + +**Figure G.2 – Peer element placement examples** + +In general, an Administrative Domain is viewed as consisting of any number of zones and any number of Peer Elements. The relationships among Administrative Domains, and among Peer Elements within an Administrative Domain, may be any of a variety of organizations. The following subclauses describe example relationships and organizations. These are described as between Administrative Domains, but the Hierarchical, Distributed/Full-Mesh and Aggregation examples could also be used to organize Peer Elements within an Administrative Domain. + +Note again that the following examples are illustrative, and not meant to exclude other possible organizations. + +### **G.5.1 Hierarchical** + +Figure G.3 shows a simple hierarchical arrangement among Administrative Domains. In such an arrangement, a Border Element in an Administrative Domain would consult a Border Element in an Administrative Domain higher in the hierarchy to resolve an address. + +![Figure G.3: Sample hierarchical organization. A tree diagram showing Administrative domain A at the top, connected to domains B and C, which are further connected to domain D. H.225.0_FG.3](b11b654648249b38a82129a35555b481_img.jpg) + +Figure G.3: Sample hierarchical organization. A tree diagram showing Administrative domain A at the top, connected to domains B and C, which are further connected to domain D. H.225.0\_FG.3 + +**Figure G.3 – Sample hierarchical organization** + +### **G.5.2 Distributed or full mesh** + +An entirely distributed or full mesh model is possible, as shown in Figure G.4. In this example, a Border Element in each Administrative Domain communicates with Border Elements in the other known Administrative Domains. + +![Figure G.4: Sample distributed organization diagram showing four administrative domains (A, B, C, D) connected in a mesh-like topology.](26d6d8d333f84acff82b7a9f9b303da6_img.jpg) + +The diagram shows four rectangular boxes labeled 'Administrative domain A', 'Administrative domain B', 'Administrative domain C', and 'Administrative domain D'. Domain A is at the top left, B is at the top right, C is at the bottom left, and D is at the bottom right. A horizontal line connects A and B. A horizontal line connects C and D. A vertical line connects A and C. A vertical line connects B and D. A diagonal line connects A and D. Another diagonal line connects B and C. The lines cross in the center, forming an 'X' shape. The label 'H.225.0\_FG.4' is located at the bottom right of the diagram. + +Figure G.4: Sample distributed organization diagram showing four administrative domains (A, B, C, D) connected in a mesh-like topology. + +**Figure G.4 – Sample distributed organization** + +### G.5.3 Clearing house + +An example of a Clearing House arrangement is shown in Figure G.5. In this arrangement, each Administrative Domain consults the Clearing House to resolve addresses. Note that since a Clearing House is an entity that exists outside of an Administrative Domain, the Peer Elements that communicate with it are by definition Border Elements. + +![Figure G.5: Sample clearing house organization diagram showing a central Clearing house connected to four administrative domains (A, B, C, D).](8768e42bf1062f1af11f259fc52a92e9_img.jpg) + +The diagram shows a central rectangular box at the top labeled 'Clearing house'. Below it are four rectangular boxes arranged horizontally, labeled 'Administrative domain A', 'Administrative domain B', 'Administrative domain C', and 'Administrative domain D'. Lines connect the 'Clearing house' box to each of the four administrative domain boxes. The label 'H.225.0\_FG.5' is located at the bottom right of the diagram. + +Figure G.5: Sample clearing house organization diagram showing a central Clearing house connected to four administrative domains (A, B, C, D). + +**Figure G.5 – Sample clearing house organization** + +### G.5.4 Aggregation point + +Figure G.6 shows an example of an aggregation point. In this example, Administrative Domain B is an aggregation point that can provide address resolution for both itself and Administrative Domains C and D. As an example, Administrative Domain B may forward resolution requests from Administrative Domain A to Administrative Domain C, or may instruct Administrative Domain A to contact Administrative Domain C directly for certain destinations. If Administrative Domain B forwards a request from Administrative Domain A to Administrative Domain C, Administrative Domain B may cache Administrative Domain C's response. + +![Diagram illustrating an aggregation point example. It shows four boxes representing Administrative domains: 'Administrative domain A' at the top, 'Administrative domain B' below it, 'Administrative domain C' to the right of 'B', and 'Administrative domain D' below 'B'. Lines connect 'A' to 'B', 'B' to 'C', and 'B' to 'D'. A small label 'H.225.0_FG.6' is located below the 'C' box.](f431b5db0c635c95318cff1adbe10c05_img.jpg) + +``` + +graph TD + A[Administrative domain A] --- B[Administrative domain B] + B --- C[Administrative domain C] + B --- D[Administrative domain D] + style H.225.0_FG.6 fill:none,stroke:none + +``` + +Diagram illustrating an aggregation point example. It shows four boxes representing Administrative domains: 'Administrative domain A' at the top, 'Administrative domain B' below it, 'Administrative domain C' to the right of 'B', and 'Administrative domain D' below 'B'. Lines connect 'A' to 'B', 'B' to 'C', and 'B' to 'D'. A small label 'H.225.0\_FG.6' is located below the 'C' box. + +**Figure G.6 – Aggregation point example** + +### G.5.5 Overlapping Administrative Domains + +More than one Administrative Domain may be able to resolve a given address. For example, multiple Administrative Domains could contain gateways that can complete a call to a terminal in the GSTN. The selection of the appropriate destination Administrative Domain is the responsibility of the origination Administrative Domain. The algorithm employed to select the destination Administrative Domain is an implementation matter. + +## G.6 Operation + +### G.6.1 Use of H.501 messages + +Annex G/H.225.0 implementations shall make use of messages defined in Rec. ITU-T H.501. The entities exchanging H.501 messages are referred to in that Recommendation as Peer Elements. + +The following is a list of the H.501 messages used by this annex: + +ServiceRequest + ServiceConfirmation + ServiceRejection + ServiceRelease + DescriptorRequest + DescriptorConfirmation + DescriptorRejection + DescriptorIDRequest + DescriptorIDConfirmation + DescriptorIDRejection + DescriptorUpdate + DescriptorUpdateAck + AccessRequest + AccessConfirmation + AccessRejection + RequestInProgress + +NonStandardRequest +NonStandardConfirmation +NonStandardRejection +UnknownMessageResponse +UsageRequest +UsageConfirmation +UsageRejection +UsageIndication +UsageIndicationConfirmation +UsageIndicationRejection +ValidationRequest +ValidationConfirmation +ValidationRejection + +An Annex G/H.225.0 Peer Element receiving an H.501 request message not included in the above list shall respond with an UnknownMessageResponse message. + +Messages shall contain all fields defined by H.501 as mandatory, and may contain optional fields as required. + +### G.6.2 Address templates and descriptors + +A Peer Element obtains templates in these ways: + +- static configuration; +- receiving descriptors from other Peer Elements in response to general requests; +- receiving responses to specific queries. + +#### G.6.2.1 Static configuration + +A Peer Element will maintain templates for all the zones for which it is responsible. These templates may be explicitly provisioned in the Peer Element, or, in the case where the Peer Element co-exists with gatekeepers, these templates may be formed by summarizing information obtained from each gatekeeper with which the Peer Element communicates. The Peer Element may make this information available to other Peer Elements via responses to requests. An Administrative Domain may choose the level of detail to be provided by its Border Element(s). Examples include: + +- A Border Element that wishes to hide internal structure might provide one descriptor (with an indication to send an AccessRequest message) that describes its whole zone and refers to a gatekeeper that will handle all incoming calls. +- A Border Element that does not care about revealing internal structure might provide a set of templates, each describing the gatekeeper for a zone within the domain. +- A Border Element that is on a firewall (or one using the gatekeeper routed model) might provide a template for the whole zone with an indication to send a Setup message. +- A Border Element with holes in its domain (because numbers have been moved to another Administrative Domain) provides templates marked **sendAccessRequest** that indicate which Border Element should be used to contact the other Administrative Domain. +- A Clearing House Border Element (such as one that has a complete copy of, e.g., 44) might hold a template marked **sendAccessRequest** for each Administrative Domain within 44. + +Peer Elements need not keep a copy of the whole database. If a Peer Element does not hold a copy of the whole database, then it should contain statically configured **sendAccessRequest** templates indicating a Clearing House Border Element that will be used to resolve other queries. + +#### G.6.2.2 Receiving descriptors + +A Peer Element may request the statically configured templates from another Peer Element. The response to the request is decided by the Peer Element from which the templates are being requested. To request a transfer, the Peer Element sends a **DescriptorRequest** message specifying the descriptors it wishes to receive. If the owning Peer Element is able to transfer the descriptors, it responds with a **DescriptorConfirmation** message specifying all the templates. + +The requesting Peer Element may cache a copy of a template received in this manner until the template's lifetime expires, at which point the Peer Element should delete its copy of the template. If the owning Peer Element changes its statically configured templates before their lifetime has expired, then it shall send a **DescriptorUpdate** message to those Peer Elements of which it is aware. A Peer Element in receipt of a **DescriptorUpdate** message should delete, add, or change all indicated templates in its cache, or should request copies of the indicated descriptors from the owner. + +An intermediate Peer Element (a Peer Element between the originating and destination Administrative Domains, such as a Clearing House or aggregation point) may publish its own descriptors based on the descriptors it receives. For example, a Clearing House may indicate itself as the contact for an **AccessRequest** message even though the descriptors it received from another Border Element indicate that other Border Element as the contact. + +A Peer Element may indicate in a template the requirement for an originator to receive permission to place a call into an Administrative Domain. When the **callSpecific** flag is set in a template and the message type indicates that an **AccessRequest** message shall be sent, the originator shall provide per-call information in the **AccessRequest** message. If a Peer Element receives the **AccessRequest** message without per-call information and policy is to require per-call information, the Peer Element shall reply with an **AccessRejection** message with a **reason** of **needCallInformation**. + +A Peer Element may send a **DescriptorUpdate** message to other known Peer Elements, or the Peer Element may multicast a **DescriptorUpdate** message. If a **DescriptorUpdate** message is multicast, the Peer Element should consider the scope of the multicast. The **DescriptorUpdate** message may contain the descriptors that have changed. Alternatively, the **DescriptorUpdate** message may indicate only the identification of the descriptors that changed, allowing the recipient to query for the new information. If a large number of descriptors have changed, the information should be sent in multiple **DescriptorUpdate** messages so that a particular **DescriptorUpdate** message does not exceed the maximum transport packet size. + +#### G.6.2.3 Receiving responses to specific queries + +A Peer Element may send an **AccessRequest** message to another Peer Element asking for the resolution of a fully qualified or partially qualified address. The **AccessRequest** is usually sent over unreliable transport (e.g., UDP), although it may be sent over reliable transport (e.g., TCP). + +A Peer Element in receipt of an **AccessRequest** searches its database and responds with the most specific template for the destination. If multiple templates satisfy the request then the Peer Element shall return all matching templates. If the destination Peer Element is actually responsible for the alias address specified, the Peer Element will usually respond with a template indicating that either an **AccessRequest** or **Setup** message should be sent. If the destination Peer Element is a Clearing House, it will normally respond with a template indicating that the **AccessRequest** message should be sent. + +The destination Peer Element may also add templates to the response that it believes will be useful in the future. The addition of these templates should not make the response so large that the transport network will need to fragment it (e.g., 576 octets for IPv4 or 1200 octets for IPv6). + +For example, a Border Element that is tightly coupled with a firewall may provide two templates in its response to AccessRequest messages: one template with a short lifetime (of a few minutes or seconds) specifying the location to which a Setup message should be sent, and additional templates specifying that AccessRequest messages should be sent to the Border Element for other AliasAddresses within the Administrative Domain. + +A Peer Element may cache a template received in an AccessConfirmation until its lifetime expires. + +### G.6.3 Discovery of a Peer Element or set of Peer Elements + +#### G.6.3.1 Static + +A Peer Element may have an administered set of other Peer Elements that it may contact for address resolution. This administered set may be defined through a set of bilateral agreements, e.g., between an Administrative Domains and other Administrative Domains. The Administrative Domains may optionally utilize the service of a Clearing House. + +#### G.6.3.2 Dynamic + +On IP networks, ownership of Email-ID style addresses is defined by the DNS system. Thus, in the absence of any better information, a border element may do a DNS SRV record lookup on the part of the email-ID to the right of the "@" sign (for example, a DNS SRV lookup on **\_h2250-annex-g.\_udp.example.org** for **person@example.org**). The response to this lookup should be used to synthesize a **sendAccessRequest** template that can be used during the resolution process. Templates synthesized from DNS requests should not be cached for longer than the lifetime provided in the DNS response. + +#### G.6.3.3 Other methods + +The use of other methods to locate another Peer Element is for further study. + +### G.6.4 Resolution procedures + +#### G.6.4.1 Resolution procedure within Administrative Domains + +When a Peer Element is asked to resolve an AliasAddress (e.g., by a co-located gateway or gatekeeper), it finds matching templates in its cache. + +If more than one template matches, appropriate templates are selected and sorted according to local policy. For example, templates may be first sorted by wildcard length (more specific templates are better), then sorted by the type of protocol specified (**sendSetup** is better than **sendAccessRequest**). + +If multiple templates satisfy the request, then the Peer Element shall return all matching templates. + +If the template selection procedure produces no templates marked as **sendSetup**, then the Peer Element sends an AccessRequest message with a specific destination address to the address specified in the template. When it gets an answer from the Peer Element, it may store that in its cache and return to the requester the address to which to send the Setup message. + +#### G.6.4.2 Resolution procedure between Administrative Domains + +When a Border Element receives an AccessRequest message from a Border Element in another Administrative Domain, it searches through the templates in its cache and finds those that match the address in the query. + +If more than one template matches, the matching templates are first sorted by wildcard length (more specific templates are better). They are then sorted by the specified message type (**sendSetup** is better than **sendAccessRequest**). In each case all templates other than the most specific match are discarded. + +If the matched templates are marked as **sendAccessRequest** then the Border Element may choose to forward the AccessRequest message to the Border Element(s) specified in the template(s), or may choose to return the templates as they are. If the hop counter in the received AccessRequest message has reached zero, then the Border Element cannot forward the AccessRequest message to another Peer Element, but should instead return any matching templates. If the hop counter has reached zero and the Border Element has no information to provide in an AccessConfirmation, the Border Element should respond with an AccessRejection message indicating that the hop count was exceeded. + +At this point, the Border Element may use another Border Element (e.g., a Clearing House) to authorize the access request. To do that, it sends a ValidationRequest message, carrying access tokens supplied by the requesting Border Element in the AccessRequest rights. The recipient Border Element validates the tokens and returns ValidationConfirmation. + +The Border Element then returns an AccessConfirmation message containing the templates that it has found (these will have the same address and message type fields) and any other templates that it considers useful. + +If multiple templates satisfy the request, then the Border Element shall return all matching templates. + +If the access request contains specific call information, then the returned templates are valid only for the call requested. This is used when an Administrative Domain wishes to grant access on a per-call basis. In that case, the Administrative Domain may mandate the inclusion of call information per each AccessRequest sent to it. It does so by setting a flag in the templates that refer to it. + +### G.6.5 Usage information exchange + +Peer Elements may request other Peer Elements to provide them information about the usage of resources in specific calls. UsageIndication messages may be provided at any stage of the call. Also, multiple UsageIndication messages may be sent for the same call, each one with possibly more up-to-date information, or reporting on consecutive call segments or different media type usage. See G.6.5.1 for details. + +UsageIndication messages may be exchanged irrespective of whether the two Peer Elements have a service relationship between them. However the policy of a Peer Element may not allow such exchanges without a service relationship. In such a case, the Peer Element may reject the UsageIndication message, with a reject code of **noServiceRelationship**. + +UsageIndication requests shall be sent whenever a Peer Element requires them, either in the templates for which it serves as contact, or by indicating in the ServiceRequest message it sends during service relationship establishment with a remote Peer Element, or by so indicating in either of the UsageRequest, AccessRequest, ValidationRequest and ValidationConfirmation messages sent in the context of the call for which usage information is required. + +#### G.6.5.1 Multiple UsageIndications for the same call + +Multiple UsageIndications for the same call provide increasingly more up-to-date information on the same media types, or usage information about new media types created in the same call. Also, since Peer Elements may take over calls while being in progress, not all the UsageIndications necessarily originate from the same Peer Element. The following rules define the semantics: + +- 1) A UsageIndication message received with a **usageCallStatus** of **callInProgress** implies a subsequent UsageIndication with the same **callIdentifier** and **senderRole** should be received. If the recipient is configured for fault recovery it may choose to conclude after a configured time interval with no further UsageIndication messages that a fault has occurred, and may recover whatever data it can from the received UsageIndication messages. +- 2) Subsequent UsageIndication messages with the same **usageField** ids should report a **startTime** matching the **endTime** of the previous message (although this may be impossible for an alternate Peer Element). Recipients shall assume each report is for a distinct + +period. Other information in the **usageField** overrides the information received in previous messages with the same **usageField** id. + +- 3) A Peer Element should send a new **UsageIndication** message for each change in the media type during the call, e.g., audio stopped and fax started, or a codec has changed. If multiple media types are engaged at the same time (e.g., audio and video) they should be reported in the same **UsageIndication** message. + +#### G.6.5.2 Requesting and negotiating usage information during service relationship establishment + +A Peer Element **PEA** may include a **UsageSpecification** element in a **ServiceRequest** message to a second Peer Element **PEB**. This **UsageSpecification** element will be used to define the default usage information to be reported for all calls that take place while the service relationship exists between the two Peer Elements **PEA** and **PEB**. This **UsageSpecification** shall be used for all calls for which **PEB** sends **UsageIndications** to **PEA**. + +If a **UsageSpecification** element arrives at **PEB** in another message from **PEA** (for example, an **AccessConfirmation**), then the new **UsageSpecification** overrides the default **UsageSpecification** for all calls related to the new message. + +A Peer Element receiving a **ServiceRequest** that contains a **UsageSpecification** element should act as follows: + +- i) If the receiving Peer Element is willing to accept the **ServiceRequest** and the **UsageSpecification** contained within, it shall send a **ServiceConfirmation** message that contains the same **UsageSpecification** as the one received in the **ServiceRequest**. The **UsageSpecification** shall apply to both incoming calls to the recipient Peer Element from the requesting Peer Element and outgoing calls from the recipient Peer Element to the requesting Peer Element. +- ii) If the receiving Peer Element is willing to accept the **ServiceRequest** but is not willing to accept the **UsageSpecification** contained within, it shall either send a **ServiceConfirmation** message containing a different **UsageSpecification** that specifies the usage information that it is able to provide to the requesting Peer Element, or a **ServiceRejection** message with the reason set to **cannotSupportUsageSpec**. +- iii) If the receiving Peer Element does not support usage reporting at all, it shall return a **ServiceRejection** message with the reason set to **usageUnavailable**. + +A Peer Element receiving a **ServiceConfirmation** should act as follows: + +- i) If the **UsageSpecification** in the **ServiceConfirmation** is the same as the one sent in the **ServiceRequest**, then the originating Peer Element and terminating Peer Element have established a service relationship between them. +- ii) If the **UsageSpecification** in the **ServiceConfirmation** is different than the one sent in the **ServiceRequest** message, then if the originating Peer Element is willing to use the new **UsageSpecification**, the service relationship is established. If the originating Peer Element is not willing to use the new **UsageSpecification**, it shall send a **ServiceRelease** message with reason set to **terminated**. The originating Peer Element could then analyse the **UsageSpecification** returned in the **ServiceConfirmation** in order to build a new **ServiceRequest** message with a modified **UsageSpecification** that may be acceptable to both Peer Elements. +- iii) If the **ServiceConfirmation** does not contain a **UsageSpecification** (and the **ServiceRequest** did), then the Peer Element that sent the **ServiceConfirmation** cannot or will not employ usage reporting at the level of the service relationship. This is the case when, for example, the recipient Peer Element implements version 1 of this annex. In this case, the + +originating Peer Element can either terminate the service relationship (by sending a ServiceRelease message with the reason code set to **terminated**), or not terminate the service relationship. In either case, if the originating Peer Element is interested in receiving usage information about calls, it should request usage information using the mechanisms described in version 1 of this annex (i.e., sending **UsageSpecification** elements in either AccessRequest, AccessConfirmation (within the returned address templates), UsageRequest, ValidationRequest or ValidationConfirmation messages). + +### G.6.6 Number portability information signalling + +Rec. ITU-T H.460.2 describes mechanisms for number portability in H.323 networks. Support for H.460.2 requires that this annex be capable of transporting number portability information through address resolution message exchanges. The interface between the Annex G Border Element and the other H.323 network elements with which it communicates is not covered by this annex; it is assumed this interface is capable of transporting the H.460.2 number portability to and from the Annex G Border Element. + +When an AccessRequest is sent, it will transport the H.460.2 number portability information, if present, using the **genericData** field in the common information portion of the message. + +AccessConfirmation and AccessRejection messages will carry the corresponding number portability response information in the **genericData** field as well. In the case of an AccessRejection, the reject reason shall be **genericDataReason**. + +## G.7 Signalling examples + +These signalling examples are provided to illustrate basic operation. In these examples, assume that the Administrative Domains have agreements with each other, so the Border Elements have been provisioned with information (e.g., TCP ports) about each other. In many of the examples below, RAS LRQ/LCF messages are exchanged between a gatekeeper and a Border Element within the same Administrative Domain. This is purely for illustrative purposes, and analogous Annex G messages could be exchanged between the Border Element and a Peer Element residing within the gatekeeper. + +### G.7.1 Distributed or full mesh + +An example of a distributed network is shown in Figure G.7. + +![Diagram showing three Administrative Domains (A, B, and C) connected to a central point. Domain A is at the top, B is at the bottom left, and C is at the bottom right. Each domain box contains its name and associated patterns. Domain A: 1732*. Domain B: 1908*, 1908953*. Domain C: 1303538*, 1303*.](143c8ee1010bf7669caabfbed815df1b_img.jpg) + +``` + +graph TD + A["Administrative domain A +1732*"] + B["Administrative domain B +1908* +1908953*"] + C["Administrative domain C +1303538* +1303*"] + A --- B + A --- C + +``` + +Diagram showing three Administrative Domains (A, B, and C) connected to a central point. Domain A is at the top, B is at the bottom left, and C is at the bottom right. Each domain box contains its name and associated patterns. Domain A: 1732\*. Domain B: 1908\*, 1908953\*. Domain C: 1303538\*, 1303\*. + +H.225.0\_FG.7 + +**Figure G.7 – Distributed network for signalling examples** + +For this example, assume the Administrative Domains each have one Border Element, and that the Border Elements are configured to resolve addresses as follows: + +| Administrative Domain | Template definition | Comment | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| A | Descriptor "d1":
Pattern = 1732*
Transport address = BE A call signal address
Message type = sendSetup | Signalling for any call into AD A will be through AD A's Border Element. | +| B | Descriptor "d2":
Pattern = 1908*
Transport address = BE B annex g address
Message type = sendAccessRequest
Descriptor "d3":
Pattern = 1908953*
Transport address = GW B1 call signalling address
Message type = sendSetup | For calls to 1908*, an AccessRequest message is needed to get the destination's (i.e., a gateway) call signalling address.

For calls to 1908953*, the Setup can be sent directly to this particular gateway. | +| C | Descriptor "d4":
Pattern = 1303538*
Transport address = GK C1 call signal address
Message type = sendSetup
Descriptor "d5":
Pattern = 1303*
Transport address = BE C annex g address
Message type = sendAccessRequest | Calls to 1303538* will be routed through this particular gatekeeper.

Calls to 1303* can be signalled directly to the destination gateway, but an AccessRequest must be sent to obtain the gateway's call signalling address. | + +#### G.7.1.1 Exchange of zone information + +In the distributed, or full mesh, organization each Administrative Domain is aware of each other Administrative Domain, presumably through a number of bilateral contractual agreements. At any time, a Border Element in an Administrative Domain can query another Administrative Domain to obtain addressing information. An example of this signalling appears in Figure G.8. + +![Sequence diagram showing descriptor exchange between BE_A, BE_B, and BE_C. BE_A sends DescriptorIDRequest to BE_B, which responds with DescriptorIDReqConf. BE_A then sends DescriptorRequest (d2) and DescriptorRequest (d3) to BE_B, receiving confirmations. BE_A then sends DescriptorIDRequest to BE_C, which responds with DescriptorIDReqConf. BE_A sends DescriptorRequest (d4) and DescriptorRequest (d5) to BE_C, receiving confirmations.](9b6977f95ef47e2c87cd4979c09a7edb_img.jpg) + +``` + +sequenceDiagram + participant BE_A + participant BE_B + participant BE_C + Note right of BE_C: H.225.0_FG.8 + BE_A->>BE_B: DescriptorIDRequest + BE_B-->>BE_A: DescriptorIDReqConf(IDs=d2, d3) + BE_A->>BE_B: DescriptorRequest (d2) + BE_B-->>BE_A: DescriptorRequestConfirmation + BE_A->>BE_B: DescriptorRequest (d3) + BE_B-->>BE_A: DescriptorRequestConfirmation + BE_A->>BE_C: DescriptorIDRequest + BE_C-->>BE_A: DescriptorIDReqConf (IDs=d4, d5) + BE_A->>BE_C: DescriptorRequest (d4) + BE_C-->>BE_A: DescriptorRequestConfirmation + BE_A->>BE_C: DescriptorRequest (d5) + BE_C-->>BE_A: DescriptorRequestConfirmation + +``` + +Sequence diagram showing descriptor exchange between BE\_A, BE\_B, and BE\_C. BE\_A sends DescriptorIDRequest to BE\_B, which responds with DescriptorIDReqConf. BE\_A then sends DescriptorRequest (d2) and DescriptorRequest (d3) to BE\_B, receiving confirmations. BE\_A then sends DescriptorIDRequest to BE\_C, which responds with DescriptorIDReqConf. BE\_A sends DescriptorRequest (d4) and DescriptorRequest (d5) to BE\_C, receiving confirmations. + +**Figure G.8 – Example of descriptor exchange** + +Similarly, BEB queries BEA and BEC, and BEC queries BEA and BEB. + +#### G.7.1.2 Placing a call + +Suppose that T1 in Administrative Domain A initiates a call to 19085551515 (T2). On receipt of T1's ARQ, T1's gatekeeper sends an LRQ. A Border Element in Administrative Domain A, BEA, has previously received zone descriptors and knows how to process the request. As shown in Figure G.9, BEA sends an AccessRequest message to BEB, as specified in the descriptor BEA received from BEB. BEB replies back with T2's call signalling address (in this example, T2 could be any type of endpoint). T1 then sends the H.225.0 Setup message to T2's call signalling address following the normal procedures defined in Rec. ITU-T H.323 and its annexes. + +![Sequence diagram showing a simple call setup. T1 sends ARQ to GK_A1, which sends LRQ to BE_A. BE_A sends AccessRequest to BE_B, which responds with AccessConfirmation. BE_A sends LCF to GK_A1, which responds with ACF. T1 then sends Setup to T2.](c2e2b17d61aecbead88a6278e4ba3605_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_A1 + participant BE_A + participant BE_B + participant T2 + Note right of T2: H.225.0_FG.9 + T1->>GK_A1: ARQ + GK_A1->>BE_A: LRQ + BE_A->>BE_B: AccessRequest + BE_B-->>BE_A: AccessConfirmation + BE_A->>GK_A1: LCF + GK_A1-->>T1: ACF + T1->>T2: Setup + +``` + +Sequence diagram showing a simple call setup. T1 sends ARQ to GK\_A1, which sends LRQ to BE\_A. BE\_A sends AccessRequest to BE\_B, which responds with AccessConfirmation. BE\_A sends LCF to GK\_A1, which responds with ACF. T1 then sends Setup to T2. + +**Figure G.9 – Example of a simple call** + +Now, suppose that T1 initiates a call to 19089532000. In this example, BEA has previously obtained the call signalling address of a gateway in Administrative Domain B that will accept the call. As shown in Figure G.10, BEA can respond to the LRQ without any message exchange into Administrative Domain B, allowing T1 to send the Setup message directly to the gateway. + +![Sequence diagram for Figure G.10: Example of a call with cached address. Lifelines: T1, GK_A1, BE_A, GW_B1. T1 sends ARQ to GK_A1. GK_A1 sends LRQ to BE_A. BE_A sends LCF to GK_A1. GK_A1 sends ACF to T1. T1 sends Setup directly to GW_B1.](3fa5b988fc31a30231724a06f3567c54_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_A1 + participant BE_A + participant GW_B1 + T1->>GK_A1: ARQ + GK_A1->>BE_A: LRQ + BE_A-->>GK_A1: LCF + GK_A1-->>T1: ACF + T1->>GW_B1: Setup + +``` + +H.225.0\_FG.10 + +Sequence diagram for Figure G.10: Example of a call with cached address. Lifelines: T1, GK\_A1, BE\_A, GW\_B1. T1 sends ARQ to GK\_A1. GK\_A1 sends LRQ to BE\_A. BE\_A sends LCF to GK\_A1. GK\_A1 sends ACF to T1. T1 sends Setup directly to GW\_B1. + +**Figure G.10 – Example of a call with cached address** + +In another example, suppose that T1 initiates a call to 13035382899. Administrative Domain C has advertised its ability to accept a call to this number, and will accept call signalling through its gatekeeper in implementing the gatekeeper-routed model. As shown in Figure G.11, BEA can respond to the LRQ with an LCF that contains the call signalling address of a gatekeeper in Administrative Domain C without any message exchange into Administrative Domain C. + +![Sequence diagram for Figure G.11: Example of remote gatekeeper routed call. Lifelines: T1, GK_A1, BE_A, BE_C, GK_C1, T3. T1 sends ARQ to GK_A1. GK_A1 sends LRQ to BE_A. BE_A sends LCF to GK_A1. GK_A1 sends ACF to T1. T1 sends Setup to GK_A1. GK_A1 forwards Setup to GK_C1. GK_C1 sends Setup to T3.](132ad076dd59b60fd549f7a612ed568b_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_A1 + participant BE_A + participant BE_C + participant GK_C1 + participant T3 + T1->>GK_A1: ARQ + GK_A1->>BE_A: LRQ + BE_A-->>GK_A1: LCF + GK_A1-->>T1: ACF + T1->>GK_A1: Setup + GK_A1->>GK_C1: Setup + GK_C1->>T3: Setup + +``` + +H.225.0\_FG.11 + +Sequence diagram for Figure G.11: Example of remote gatekeeper routed call. Lifelines: T1, GK\_A1, BE\_A, BE\_C, GK\_C1, T3. T1 sends ARQ to GK\_A1. GK\_A1 sends LRQ to BE\_A. BE\_A sends LCF to GK\_A1. GK\_A1 sends ACF to T1. T1 sends Setup to GK\_A1. GK\_A1 forwards Setup to GK\_C1. GK\_C1 sends Setup to T3. + +**Figure G.11 – Example of remote gatekeeper routed call** + +Alternatively, T1's gatekeeper can implement the gatekeeper-routed model, as shown in Figure G.12. + +![Sequence diagram for a local gatekeeper routed call. Lifelines: T1, GK_A1, BE_A, BE_C, GK_C1, T3. The sequence starts with T1 sending an ARQ to GK_A1. GK_A1 sends an LRQ to BE_A, which responds with LCF. GK_A1 then sends an ACF back to T1. T1 sends a Setup message to GK_A1, which is then forwarded by GK_A1 to GK_C1, which finally forwards it to T3. The diagram is labeled H.225.0_FG.12.](3ce6b213ec556257e32ff7451182369d_img.jpg) + +Sequence diagram for a local gatekeeper routed call. Lifelines: T1, GK\_A1, BE\_A, BE\_C, GK\_C1, T3. The sequence starts with T1 sending an ARQ to GK\_A1. GK\_A1 sends an LRQ to BE\_A, which responds with LCF. GK\_A1 then sends an ACF back to T1. T1 sends a Setup message to GK\_A1, which is then forwarded by GK\_A1 to GK\_C1, which finally forwards it to T3. The diagram is labeled H.225.0\_FG.12. + +Figure G.12 – Example of local gatekeeper routed call + +### G.7.2 Clearing House + +An example of a configuration using a Clearing House is shown in Figure G.13. Refer to this figure for the following examples. In this example, the Clearing House holds addressing information for all Administrative Domains for which the Clearing House provides service. + +![Diagram showing a Clearing house connected to two Administrative domains, D and E. The Clearing house box lists patterns: 1908*, 1908953*, 1303538*, and 1303*. Administrative domain D box lists patterns: 1908* and 1908953*. Administrative domain E box lists patterns: 1303538* and 1303*. The diagram is labeled H.225.0_FG.13.](a83c022a6dac411615bcc38b7cd0d573_img.jpg) + +Diagram showing a Clearing house connected to two Administrative domains, D and E. The Clearing house box lists patterns: 1908\*, 1908953\*, 1303538\*, and 1303\*. Administrative domain D box lists patterns: 1908\* and 1908953\*. Administrative domain E box lists patterns: 1303538\* and 1303\*. The diagram is labeled H.225.0\_FG.13. + +Figure G.13 – Sample clearing house configuration + +For this example, the Border Elements in Administrative Domains D and E, and the Clearing House, contain the following information: + +| Administrative Domain | Template definition | Comment | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D | Descriptor "d1":
Pattern = 1908*
Transport address = BE D annex g address
Message type = sendAccessRequest

Descriptor "d2":
Pattern = 1908953*
Transport address = GW D1 Call
Signalling address
Message type = sendSetup | For calls to 1908*, an AccessRequest message is needed to get the destination's (i.e., a gateway) call signalling address.

For calls to 1908953*, the Setup can be sent directly to this particular gateway. | + +| Administrative Domain | Template definition | Comment | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E | Descriptor "d3":
Pattern = 1303538*
Transport address = GK E1 call signal address
Message type = sendSetup
Descriptor "d4":
Pattern = 1303*
Transport address = BE E annex g address
Message type = sendAccessRequest | Calls to 1303538* will be routed through this particular gatekeeper.

Calls to 1303* can be signalled directly to the destination gateway, but an AccessRequest must be sent to obtain the gateway's call signalling address. | +| CH | Descriptor "d1":
Pattern = 1908*
Transport address = BE D annex g address
Message type = sendAccessRequest
Descriptor "d2":
Pattern = 1908953*
Transport address = GWD D1 call signalling address
Message type = sendSetup
Descriptor "d3":
Pattern = 1303538*
Transport address = GK E1 call signal address
Message type = sendSetup
Descriptor "d4":
Pattern = 1303*
Transport address = BE E annex g address
Message type = sendAccessRequest | The Clearing House obtains descriptors from other ADs and holds this information for distribution during descriptor exchange. | + +#### G.7.2.1 Exchange of zone information + +In this example, a Clearing House exchanges information with Administrative Domains that subscribe to the Clearing House's service. The Clearing House holds the information it receives from each Administrative Domain and passes this information along to other Administrative Domains. In this example, the Clearing House appears as Administrative Domain E to Administrative Domain D, while Administrative Domains D and E are not necessarily aware of each other. See Figure G.14. + +![Sequence diagram showing descriptor exchange between BE_D, BE_CH, and BE_E. BE_D sends DescriptorIDRequest to BE_CH, which responds with DescriptorIDReqConf(IDs=d1, d2, d3, d4). BE_D then sends DescriptorRequest (d3) and receives DescriptorRequestConfirmation. BE_D sends DescriptorRequest (d4) and receives DescriptorRequestConfirmation. Then BE_CH sends DescriptorIDRequest to BE_E, which responds with DescriptorIDReqConf(IDs=d1, d2, d3, d4). BE_CH then sends DescriptorRequest (d1) and receives DescriptorRequestConfirmation. BE_CH sends DescriptorRequest (d2) and receives DescriptorRequestConfirmation.](845e014e3b8677eb735d0e21f21206be_img.jpg) + +``` + +sequenceDiagram + participant BE_D + participant BE_CH + participant BE_E + Note right of BE_E: H.225.0_FG.14 + BE_D->>BE_CH: DescriptorIDRequest + BE_CH-->>BE_D: DescriptorIDReqConf(IDs=d1, d2, d3, d4) + BE_D->>BE_CH: DescriptorRequest (d3) + BE_CH-->>BE_D: DescriptorRequestConfirmation + BE_D->>BE_CH: DescriptorRequest (d4) + BE_CH-->>BE_D: DescriptorRequestConfirmation + BE_CH->>BE_E: DescriptorIDRequest + BE_E-->>BE_CH: DescriptorIDReqConf(IDs=d1, d2, d3, d4) + BE_CH->>BE_E: DescriptorRequest (d1) + BE_E-->>BE_CH: DescriptorRequestConfirmation + BE_CH->>BE_E: DescriptorRequest (d2) + BE_E-->>BE_CH: DescriptorRequestConfirmation + +``` + +Sequence diagram showing descriptor exchange between BE\_D, BE\_CH, and BE\_E. BE\_D sends DescriptorIDRequest to BE\_CH, which responds with DescriptorIDReqConf(IDs=d1, d2, d3, d4). BE\_D then sends DescriptorRequest (d3) and receives DescriptorRequestConfirmation. BE\_D sends DescriptorRequest (d4) and receives DescriptorRequestConfirmation. Then BE\_CH sends DescriptorIDRequest to BE\_E, which responds with DescriptorIDReqConf(IDs=d1, d2, d3, d4). BE\_CH then sends DescriptorRequest (d1) and receives DescriptorRequestConfirmation. BE\_CH sends DescriptorRequest (d2) and receives DescriptorRequestConfirmation. + +**Figure G.14 – Example descriptor exchange with clearing house** + +#### G.7.2.2 Placing a call + +Suppose that T1 in Administrative Domain E initiates a call to 19085551515. The Border Element in Administrative Domain E has received descriptors from the Clearing House that indicate the Clearing House should be consulted for such a call. The Border Element sends an AccessRequest to the Clearing House Border Element. Based on the descriptors the Clearing House Border Element received from the Border Element in Administrative Domain D, the Clearing House Border Element sends an AccessRequest to the Border Element in Administrative Domain D. When the Clearing House Border Element returns the confirmation to the Border Element in Administrative Domain E, the confirmation contains the information sent from the Border Element in Administrative Domain D. T1's gatekeeper returns an ACF with T2's destCallSignalAddress, allowing T1 to send the Setup message to T2. See Figure G.15. + +![Sequence diagram showing call placement from T1 to T2 via GK_E1, BE_E, BE_CH, and BE_D. T1 sends ARQ to GK_E1. GK_E1 sends LRQ to BE_E. BE_E sends AccessRequest to BE_CH. BE_CH sends AccessRequest to BE_D. BE_D returns AccessConfirmation to BE_CH. BE_CH returns AccessConfirmation to BE_E. BE_E sends LCF to GK_E1. GK_E1 returns ACF to T1. Finally, T1 sends a Setup message directly to T2.](56f125e1bc127f7ac3d210407957413c_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_E1 + participant BE_E + participant BE_CH + participant BE_D + participant T2 + Note right of T2: H.225.0_FG.15 + T1->>GK_E1: ARQ + GK_E1->>BE_E: LRQ + BE_E->>BE_CH: AccessRequest + BE_CH->>BE_D: AccessRequest + BE_D-->>BE_CH: AccessConfirmation + BE_CH-->>BE_E: AccessConfirmation + BE_E->>GK_E1: LCF + GK_E1-->>T1: ACF + T1->>T2: Setup + +``` + +Sequence diagram showing call placement from T1 to T2 via GK\_E1, BE\_E, BE\_CH, and BE\_D. T1 sends ARQ to GK\_E1. GK\_E1 sends LRQ to BE\_E. BE\_E sends AccessRequest to BE\_CH. BE\_CH sends AccessRequest to BE\_D. BE\_D returns AccessConfirmation to BE\_CH. BE\_CH returns AccessConfirmation to BE\_E. BE\_E sends LCF to GK\_E1. GK\_E1 returns ACF to T1. Finally, T1 sends a Setup message directly to T2. + +**Figure G.15 – Example of call with clearing house** + +Alternatively, T1's gatekeeper could route the call signalling, as shown in Figure G.16. + +![Sequence diagram for Figure G.16: Example of local gatekeeper routed call with clearing house. Lifelines: T1, GK_E1, BE_E, BE_CH, BE_D, T2. The sequence shows ARQ, LRQ, AccessRequest, AccessConfirmation, LCF, ACF, and Setup messages.](5ee80a63ec53c60d7306b5a44984afcf_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_E1 as GKE1 + participant BE_E as BEE + participant BE_CH as BECH + participant BE_D as BED + participant T2 + + T1->>GK_E1: ARQ + GK_E1->>BE_E: LRQ + BE_E->>BE_CH: AccessRequest + BE_CH->>BE_D: AccessRequest + BE_D->>BE_CH: AccessConfirmation + BE_CH->>BE_E: AccessConfirmation + BE_E->>GK_E1: LCF + GK_E1->>T1: ACF + T1->>GK_E1: Setup + GK_E1->>T2: Setup + +``` + +H.225.0\_FG.16 + +Sequence diagram for Figure G.16: Example of local gatekeeper routed call with clearing house. Lifelines: T1, GK\_E1, BE\_E, BE\_CH, BE\_D, T2. The sequence shows ARQ, LRQ, AccessRequest, AccessConfirmation, LCF, ACF, and Setup messages. + +**Figure G.16 – Example of local gatekeeper routed call with clearing house** + +Another possibility is for the Clearing House to respond to the Border Element in Administrative Domain E with the contact information for the Border Element in Administrative Domain D, as shown in Figure G.17. + +![Sequence diagram for Figure G.17: Example of clearing house routing using contact info for remote BE. Lifelines: T1, GK_E1, BE_E, BE_CH, BE_D, T2. The sequence shows ARQ, LRQ, AccessRequest, AccessConfirmation, AccessRequest, AccessConfirmation, LCF, ACF, and Setup messages.](b02ba0b73e95416eb547976f6145b169_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_E1 as GKE1 + participant BE_E as BEE + participant BE_CH as BECH + participant BE_D as BED + participant T2 + + T1->>GK_E1: ARQ + GK_E1->>BE_E: LRQ + BE_E->>BE_CH: AccessRequest + BE_CH->>BE_E: AccessConfirmation + BE_E->>BE_CH: AccessRequest + BE_CH->>BE_D: AccessRequest + BE_D->>BE_CH: AccessConfirmation + BE_CH->>BE_E: AccessConfirmation + BE_E->>GK_E1: LCF + GK_E1->>T1: ACF + T1->>GK_E1: Setup + GK_E1->>T2: Setup + +``` + +H.225.0\_FG.17 + +Sequence diagram for Figure G.17: Example of clearing house routing using contact info for remote BE. Lifelines: T1, GK\_E1, BE\_E, BE\_CH, BE\_D, T2. The sequence shows ARQ, LRQ, AccessRequest, AccessConfirmation, AccessRequest, AccessConfirmation, LCF, ACF, and Setup messages. + +**Figure G.17 – Example of clearing house routing using contact info for remote BE** + +Now suppose that T1 initiates a call to 19089532000. The descriptors previously exchanged allow the Border Element to return the call signalling address to T1 without consulting the Clearing House, as shown in Figure G.18. + +![Sequence diagram for Figure G.18: Example of call using cached descriptor in local BE. Lifelines: T1, GK_E1, BE_E, GW_D1. The sequence shows ARQ, LRQ, LCF, ACF, and Setup messages.](78151e5dd542eada99ead8203dfce76b_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_E1 as GKE1 + participant BE_E as BEE + participant GW_D1 as GWD1 + + T1->>GK_E1: ARQ + GK_E1->>BE_E: LRQ + BE_E->>GK_E1: LCF + GK_E1->>T1: ACF + T1->>GK_E1: Setup + GK_E1->>GW_D1: Setup + +``` + +H.225.0\_FG.18 + +Sequence diagram for Figure G.18: Example of call using cached descriptor in local BE. Lifelines: T1, GK\_E1, BE\_E, GW\_D1. The sequence shows ARQ, LRQ, LCF, ACF, and Setup messages. + +**Figure G.18 – Example of call using cached descriptor in local BE** + +Next, consider a scenario where T1 initiates a call to 13035382899. The Border Element in Administrative Domain E had previously advertised that calls to 1303538\* could be routed directly to a gatekeeper in Administrative Domain E without need for an Access Request message, as shown in Figure G.19. (This advertisement does not indicate that the entity is a gatekeeper, only that a Setup message could be sent to a specified address.) The Border Element in Administrative Domain D received this information from the Clearing House, assuming the Clearing House in this example does not have a requirement to provide address resolution for these calls. + +![Sequence diagram for Figure G.19 showing a GK routed call using a cached descriptor. Lifelines: T1, GK_D1, BE_D, BE_E, GK_E1, T3. The sequence starts with T1 sending an ARQ to GK_D1. GK_D1 sends an LRQ to BE_D, which responds with LCF. GK_D1 then sends an ACF to T1. T1 sends a Setup message to GK_D1, which is then forwarded by GK_D1 to GK_E1, which finally sends a Setup message to T3.](1922717e4a5ef189ba4572ea65b2f0ae_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_D1 as GKD1 + participant BE_D as BED + participant BE_E as BEE + participant GK_E1 as GKE1 + participant T3 + + T1->>GK_D1: ARQ + GK_D1->>BE_D: LRQ + BE_D-->>GK_D1: LCF + GK_D1-->>T1: ACF + T1->>GK_D1: Setup + GK_D1->>GK_E1: Setup + GK_E1->>T3: Setup + +``` + +H.225.0\_FG.19 + +Sequence diagram for Figure G.19 showing a GK routed call using a cached descriptor. Lifelines: T1, GK\_D1, BE\_D, BE\_E, GK\_E1, T3. The sequence starts with T1 sending an ARQ to GK\_D1. GK\_D1 sends an LRQ to BE\_D, which responds with LCF. GK\_D1 then sends an ACF to T1. T1 sends a Setup message to GK\_D1, which is then forwarded by GK\_D1 to GK\_E1, which finally sends a Setup message to T3. + +**Figure G.19 – Example of GK routed call using cached descriptor** + +Recall that a Border Element may be combined with a gatekeeper, and may also route calls in the gatekeeper-routed model. An alternative signalling example is shown in Figure G.20. It is also possible to use the Border Element as a routing gatekeeper into an Administrative Domain if the descriptors are so configured. + +![Sequence diagram for Figure G.20 showing a call with a combined BE/routing GK. Lifelines: T1, GK_D1, BE_D, BE_E, GK_E1, T3. The sequence starts with T1 sending an ARQ to GK_D1. GK_D1 sends an LRQ to BE_D, which responds with LCF. GK_D1 then sends an ACF to T1. T1 sends a Setup message to GK_D1, which is then forwarded by GK_D1 to BE_D. BE_D then sends a Setup message to GK_E1, which finally sends a Setup message to T3.](ceb6fe29e2d57711907569c31182b3c2_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_D1 as GKD1 + participant BE_D as BED + participant BE_E as BEE + participant GK_E1 as GKE1 + participant T3 + + T1->>GK_D1: ARQ + GK_D1->>BE_D: LRQ + BE_D-->>GK_D1: LCF + GK_D1-->>T1: ACF + T1->>GK_D1: Setup + GK_D1->>BE_D: Setup + BE_D->>GK_E1: Setup + GK_E1->>T3: Setup + +``` + +H.225.0\_FG.20 + +Sequence diagram for Figure G.20 showing a call with a combined BE/routing GK. Lifelines: T1, GK\_D1, BE\_D, BE\_E, GK\_E1, T3. The sequence starts with T1 sending an ARQ to GK\_D1. GK\_D1 sends an LRQ to BE\_D, which responds with LCF. GK\_D1 then sends an ACF to T1. T1 sends a Setup message to GK\_D1, which is then forwarded by GK\_D1 to BE\_D. BE\_D then sends a Setup message to GK\_E1, which finally sends a Setup message to T3. + +**Figure G.20 – Example of call with combined BE/routing GK** + +In the example of Figure G.21, the Clearing House validates the call for the terminating Administrative Domain. The Clearing House also requires both originating and terminating Border Elements to send UsageIndications for the call. + +![Sequence diagram illustrating call validation and usage reporting with clearing house. Lifelines: T1, GK_D/BE_E, BE_CH, BE_D/GK_E, T2. The sequence shows ARQ, AccessRequest, AccessConfirmation, ACF, Setup, ValidationRequest, ValidationConfirmation, Connect, UsageIndication, UsageIndicationConfirm, Release Complete, DRQ, and DCF messages.](c93353297f7ed04bc9173ac1f224d406_img.jpg) + +``` + +sequenceDiagram + participant T1 + participant GK_D/BE_E + participant BE_CH + participant BE_D/GK_E + participant T2 + + Note right of T1: H.225.0_FG.21 + + T1->>GK_D/BE_E: ARQ + GK_D/BE_E->>BE_CH: AccessRequest + BE_CH-->>GK_D/BE_E: AccessConfirmation + GK_D/BE_E-->>T1: ACF + T1->>GK_D/BE_E: Setup + + T2->>BE_D/GK_E: ARQ + BE_D/GK_E->>BE_CH: ValidationRequest + BE_CH-->>BE_D/GK_E: ValidationConfirmation + BE_D/GK_E-->>T2: ACF + T2->>BE_D/GK_E: Connect + BE_D/GK_E-->>T1: + + GK_D/BE_E->>BE_CH: UsageIndication + BE_CH-->>BE_D/GK_E: UsageIndication + BE_D/GK_E-->>GK_D/BE_E: UsageIndicationConfirm + BE_CH-->>GK_D/BE_E: UsageIndicationConfirm + + T1->>T2: Release Complete + + T1->>GK_D/BE_E: DRQ + GK_D/BE_E-->>T1: DCF + + BE_D/GK_E->>T2: DRQ + T2-->>BE_D/GK_E: DCF + + BE_CH-->>BE_D/GK_E: UsageIndication + BE_D/GK_E-->>BE_CH: UsageIndicationConfirm + + GK_D/BE_E->>BE_CH: UsageIndication + BE_CH-->>GK_D/BE_E: UsageIndicationConfirm + +``` + +Sequence diagram illustrating call validation and usage reporting with clearing house. Lifelines: T1, GK\_D/BE\_E, BE\_CH, BE\_D/GK\_E, T2. The sequence shows ARQ, AccessRequest, AccessConfirmation, ACF, Setup, ValidationRequest, ValidationConfirmation, Connect, UsageIndication, UsageIndicationConfirm, Release Complete, DRQ, and DCF messages. + +**Figure G.21 – Call validation and usage reporting example with clearing house** + +## G.8 Annex G profiles + +### G.8.1 Introduction + +Rec. ITU-T H.501 offers a rich set of messages and fields that this annex may use for interaction between Administrative Domains and between Peer Elements within a single Administrative Domain. Many of the messages and fields are optional and can be used in a variety of ways to implement different services or service options. This clause specifies implementation profiles that define the messages, fields and procedures that are required in order to claim compliance with a specific profile. + +#### G.8.1.1 Profile signalling and negotiation + +The H.323 generic extensible framework may be used by a Peer Element to signal to another Peer Element the set of profiles that it needs for a transaction to be successful, the set of profiles it desires to use, and the set of profiles it supports. This profile negotiation signalling may be done either in an individual message exchange (e.g., in an AccessRequest/AccessConfirmation exchange), or during the establishment of a service relationship. Note that the establishment of a service relationship between two Peer Elements may not be required by a profile. + +##### G.8.1.1.1 Processing by the requesting entity + +A requesting entity (a Peer Element) uses the elements in the **FeatureSet** structure to specify the various profiles it requires. It specifies the set of profiles that it needs using the **neededFeatures** field, the set of profiles that it desires using the **desiredFeatures** field, and the set of profiles that it supports in the **supportedFeatures** field. All three of these fields are in the **FeatureSet** structure. + +In response to its request, a requesting entity should receive either a confirmation or a rejection message. + +If the request is rejected, the responding entity may have included a set of **neededFeatures** that the requesting entity must support in order for the request to be successful. If this is the case and the requesting entity supports the needed features (e.g., a specific profile), the requesting entity may re-issue a request specifying support for the profile needed by the responding entity. + +If the request is accepted, special procedures need to be applied to ensure that the negotiation operates in a backwards-compatible manner. This is done by the requesting entity checking that the profile that it specified as needed are listed as **supportedFeatures** in the response. If a requesting entity does not observe the profiles it needs in the response message's **supportedFeatures** field, then it shall assume that the responding entity does not support the profiles that it needs. If the requesting entity determines that it cannot continue under these circumstances, then it shall undo the operation it was trying to perform (i.e., send a ServiceRelease message if it originally sent a ServiceRequest message), so that the state in the responding entity is rolled back. + +##### G.8.1.1.2 Processing by the responding entity + +The responding entity looks at the profiles specified in the **neededFeatures** field of the request to determine if it can accept the request. It also looks in the **neededFeatures**, **desiredFeatures** and **supportedFeatures** fields to determine whether the profiles needed by it are supported by the requesting entity. + +If the responding entity determines that the necessary sets of profiles are supported by both entities, then the responding entity may acknowledge the request. The responding entity lists the set of profiles that it chooses to support in the **supportedFeatures** field of its reply. If the request is accepted, then all of the **neededFeatures** from the request must be included in the **supportedFeatures** field of the reply. The responding entity may also include **desiredFeatures**. + +If the responding entity needs additional profiles to be supported by the requesting entity, it shall reject the request. If it wishes to declare which profiles must be supported for the request to be successful, this should be specified using the **neededFeatures** field of the reject message. The responding entity may also include any **desiredFeatures** and **supportedFeatures** in the reject message. + +##### G.8.1.1.3 Identifiers + +The following identifier is used within a FeatureDescriptor to specify that the FeatureDescriptor applies to Annex G profiles. + +| Value | Description | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| idAnnexGProfiles | This identifier is used in the "id" field of a FeatureDescriptor to indicate that the FeatureDescriptor is describing the Annex G profiles needed/desired/supported. | + +The following table contains a list of the identifiers used within the generic extensibility framework that are relevant to this annex. + +| Standard INTEGER Value | Description | +|------------------------|------------------------------------------------------------------------------------------------------------| +| 0 | Identifier within a FeatureDescriptor indicating that the FeatureDescriptor is describing Annex G profiles | +| 1 | Identifier within an EnumeratedParameter that identifies Annex G Profile "A" | + +### G.8.2 Profile "A": Interzone call routing to a trusted gatekeeper + +This profile specifies a simple intra-domain service – per-call queries to another trusted zone for endpoint determination where the Annex G signalling address of the trusted zones is statically provisioned. This is one of the simplest uses of this annex and is similar to the use of RAS LRQ to query another zone for an endpoint. The same profile may be used to query a trusted Peer Element, which returns routes from domain-wide knowledge or obtains them by further Annex G queries. + +#### G.8.2.1 Required messages + +Entities complying with this profile shall support the messages indicated as "Mandatory" in the following table: + +| Message | Transmit
(Mandatory, Optional,
Recommended) | Receive and act on
(Mandatory, Optional,
Recommended) | +|-----------------------------|---------------------------------------------------|-------------------------------------------------------------| +| ServiceRequest | O | M (Note 1) | +| ServiceConfirmation | O | O | +| ServiceRejection | M | O | +| ServiceRelease | O | O | +| DescriptorRequest | O | M (Note 1) | +| DescriptorConfirmation | R (Note 2) | O | +| DescriptorRejection | M | O | +| DescriptorIdRequest | O | M (Note 1) | +| DescriptorIdConfirmation | R (Note 2) | O | +| DescriptorIdRejection | M | O | +| DescriptorUpdate | O | M (Note 3) | +| DescriptorUpdateAck | M | O | +| AccessRequest | M | M | +| AccessConfirmation | M | M | +| AccessRejection | M | M | +| RequestInProgress | M | M | +| NonStandardRequest | O | M | +| NonStandardConfirmation | O | O | +| NonStandardRejection | M | O | +| UnknownMessageResponse | M | M | +| UsageRequest | O | M (Note 1) | +| UsageConfirmation | O | O | +| UsageRejection | M | O | +| UsageIndication | O | M (Note 1) | +| UsageIndicationConfirmation | O | O | +| UsageIndicationRejection | M | O | +| ValidationRequest | O | M (Note 1) | + +| Message | Transmit
(Mandatory, Optional,
Recommended) | Receive and act on
(Mandatory, Optional,
Recommended) | +|------------------------|---------------------------------------------------|-------------------------------------------------------------| +| ValidationConfirmation | O | O | +| ValidationRejection | M | O | + +NOTE 1 – Shall be received and as a minimum rejected. +NOTE 2 – It is recommended that an entity return as a minimum a single descriptor for a template with SendAccessRequest pointing to itself. +NOTE 3 – Shall be received and acknowledged, but need not be processed. + +#### G.8.2.2 Required fields + +All fields defined as mandatory by Rec. ITU-T H.501 are also mandatory within this profile. + +Entities complying with this profile shall also support the fields specified in the following table. + +Other fields defined as optional by Rec. ITU-T H.501 may optionally be present. + +| Message or structure | Required field | Comment | +|------------------------------|-------------------------|--------------------------------------------------------------------------------------------------| +| AccessRequest message | destinationInfo | One address containing the fully-qualified E.164 address of the destination | +| | sourceInfo | Includes the domainInfo and endpointType | +| | callInfo | | +| AccessConfirmation message | templates | If any templates are present, then there is one template per each termination gateway/gatekeeper | +| | partialResponse | Set to FALSE | +| AddressTemplate structure | pattern | One specific pattern is present containing the E.164 number | +| | routeInfo | One instance present | +| | timeToLive | | +| RouteInformation structure | messageType | Present | +| | callSpecific | Set to FALSE | +| | contacts | One instance present | +| | type | Must be present if messageType = sendSetup | +| ContactInformation structure | transportAddress | The IP address of the gateway/gatekeeper | +| | priority | | + +#### G.8.2.3 Required procedures + +In this profile, entities may use the static discovery procedures of this annex (see G.6.3.1) and so will have a configured list of Peer Elements or gatekeepers to which requests can be sent. This list may contain alternates to be used only when the primary element cannot be reached or may simply add the alternates (if any) to the list. + +Entities may also use the dynamic discovery procedures of this annex (see G.6.3.2). + +Entities shall send an AccessRequest message to a selected Peer Element or gatekeeper for each call. If more than one Peer Element or gatekeeper is available to be queried for a given call, it is not specified whether they must be queried in sequence or may be queried in parallel. This choice is left to the requesting entity. + +The reply will have zero or more templates. **timeToLive** may be set to 60 seconds or less to indicate that it may not be used for another call. + +To improve interoperation with more general peers, it is suggested that in the case that the Peer Element does not implement descriptor support, it should follow the following procedures: + +- If a DescriptorIDRequest message is received, the Peer Element should return a DescriptorIDConfirmation message containing a single **DescriptorInfo**. This **DescriptorInfo** describes a descriptor containing a single template specifying **sendAccessRequest** pointing to the Peer Element itself. +- If a DescriptorRequest message is received, the Peer Element should return a DescriptorConfirmation message containing a single descriptor. This descriptor shall contain a single template specifying **sendAccessRequest** pointing to the Peer Element itself. + +#### G.8.2.4 Identifiers for Profile "A" + +The following identifier is used within an **EnumeratedParameter** to specify that the **EnumeratedParameter** specifies Annex G Profile A. + +| Value | Description | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| idAnnexGProfileA | This identifier is used in the "id" field of an EnumeratedParameter to indicate that Annex G Profile A is needed/desired/supported.
Note that the "content" field of the EnumeratedParameter is not present. | + +# Annex H + +## H.225.0 message syntax (ASN.1) + +(This annex forms an integral part of this Recommendation.) + +This Recommendation defines protocols for RAS (essentially a gatekeeper protocol) and call signalling (essentially protocol data units which reside in a User-user information element). These protocols are defined together in the following ASN.1 tree. Semantic definitions for the messages and various elements appear in previous clauses. + +``` +H323-MESSAGES {itu-t(0) recommendation(0) h(8) h225-0(2250) version(0) + 8 h323-messages(0)} DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +IMPORTS + + SIGNED{}, + ENCRYPTED{}, + HASHED{}, + ChallengeString, + TimeStamp, + RandomVal, + Password, + EncodedPwdCertToken, + ClearToken, + CryptoToken, + AuthenticationMechanism + FROM H235-SECURITY-MESSAGES + DataProtocolCapability, + T38FaxProfile, + QOSCapability + FROM MULTIMEDIA-SYSTEM-CONTROL {itu-t(0) recommendation(0) h(8) h245(245) +version(0) 15 multimedia-system-control(0)}; +H323-UserInfoInformation ::= SEQUENCE -- root for all H.225.0 call signalling +messages +{ + h323-uu-pdu H323-UU-PDU, + user-data SEQUENCE + { + protocol-discriminator INTEGER (0..255), + user-information OCTET STRING (SIZE(1..131)), + ... + } OPTIONAL, + ... +} + +H323-UU-PDU ::= SEQUENCE +{ + h323-message-body CHOICE + { + setup Setup-UIIE, + callProceeding CallProceeding-UIIE, + connect Connect-UIIE, + alerting Alerting-UIIE, + information Information-UIIE, + releaseComplete ReleaseComplete-UIIE, + facility Facility-UIIE, + ... + progress Progress-UIIE, + empty NULL, -- used when a Facility message is sent, + } +} +``` + +``` + +-- but the Facility-UUIE is not to be invoked +-- (possible when transporting supplementary +-- services messages in versions prior to +-- H.225.0 version 4) +status Status-UUIE, +statusInquiry StatusInquiry-UUIE, +setupAcknowledge SetupAcknowledge-UUIE, +notify Notify-UUIE +}, +nonStandardData NonStandardParameter OPTIONAL, +... +h4501SupplementaryService SEQUENCE OF OCTET STRING OPTIONAL, +-- each sequence of octet string is defined as one +-- H4501SupplementaryService APDU as defined in +-- Table 3/H.450.1 + +h245Tunnelling BOOLEAN, +-- if TRUE, tunnelling of H.245 messages is enabled +h245Control SEQUENCE OF OCTET STRING OPTIONAL, +nonStandardControl SEQUENCE OF NonStandardParameter OPTIONAL, +callLinkage CallLinkage OPTIONAL, +tunnelledSignallingMessage SEQUENCE +{ + tunnelledProtocolID TunnelledProtocol, -- tunnelled signalling + -- protocol ID + messageContent SEQUENCE OF OCTET STRING, -- sequence of entire + -- message(s) + tunnellingRequired NULL OPTIONAL, + nonStandardData NonStandardParameter OPTIONAL, + ... +} OPTIONAL, +provisionalRespToH245Tunnelling NULL OPTIONAL, +stimulusControl StimulusControl OPTIONAL, +genericData SEQUENCE OF GenericData OPTIONAL +} + +StimulusControl ::= SEQUENCE +{ + nonStandard NonStandardParameter OPTIONAL, + isText NULL OPTIONAL, + h248Message OCTET STRING OPTIONAL, + ... +} + +Alerting-UUIE ::= SEQUENCE +{ + protocolIdentifier ProtocolIdentifier, + destinationInfo EndpointType, + h245Address TransportAddress OPTIONAL, + ... + callIdentifier CallIdentifier, + h245SecurityMode H245Security OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + fastStart SEQUENCE OF OCTET STRING OPTIONAL, + multipleCalls BOOLEAN, + maintainConnection BOOLEAN, + alertingAddress SEQUENCE OF AliasAddress OPTIONAL, + presentationIndicator PresentationIndicator OPTIONAL, + screeningIndicator ScreeningIndicator OPTIONAL, + fastConnectRefused NULL OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL, + capacity CallCapacity OPTIONAL, + featureSet FeatureSet OPTIONAL, +} + +``` + +``` + + displayName SEQUENCE OF DisplayName OPTIONAL + } + + CallProceeding-UUIE ::= SEQUENCE + { + protocolIdentifier ProtocolIdentifier, + destinationInfo EndpointType, + h245Address TransportAddress OPTIONAL, + .../ + callIdentifier CallIdentifier, + h245SecurityMode H245Security OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + fastStart SEQUENCE OF OCTET STRING OPTIONAL, + multipleCalls BOOLEAN, + maintainConnection BOOLEAN, + fastConnectRefused NULL OPTIONAL, + featureSet FeatureSet OPTIONAL + } + + Connect-UUIE ::= SEQUENCE + { + protocolIdentifier ProtocolIdentifier, + h245Address TransportAddress OPTIONAL, + destinationInfo EndpointType, + conferenceID ConferenceIdentifier, + .../ + callIdentifier CallIdentifier, + h245SecurityMode H245Security OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + fastStart SEQUENCE OF OCTET STRING OPTIONAL, + multipleCalls BOOLEAN, + maintainConnection BOOLEAN, + language SEQUENCE OF IA5String (SIZE (1..32)) OPTIONAL, + -- RFC 5646 language tag + connectedAddress SEQUENCE OF AliasAddress OPTIONAL, + presentationIndicator PresentationIndicator OPTIONAL, + screeningIndicator ScreeningIndicator OPTIONAL, + fastConnectRefused NULL OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL, + capacity CallCapacity OPTIONAL, + featureSet FeatureSet OPTIONAL, + displayName SEQUENCE OF DisplayName OPTIONAL + } + + Information-UUIE ::= SEQUENCE + { + protocolIdentifier ProtocolIdentifier, + .../ + callIdentifier CallIdentifier, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + fastStart SEQUENCE OF OCTET STRING OPTIONAL, + fastConnectRefused NULL OPTIONAL, + circuitInfo CircuitInfo OPTIONAL + } + + ReleaseComplete-UUIE ::= SEQUENCE + { + protocolIdentifier ProtocolIdentifier, + reason ReleaseCompleteReason OPTIONAL, + .../ + callIdentifier CallIdentifier, + } + +``` + +``` + + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + busyAddress SEQUENCE OF AliasAddress OPTIONAL, + presentationIndicator PresentationIndicator OPTIONAL, + screeningIndicator ScreeningIndicator OPTIONAL, + capacity CallCapacity OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL, + featureSet FeatureSet OPTIONAL, + destinationInfo EndpointType OPTIONAL, + displayName SEQUENCE OF DisplayName OPTIONAL +} + +ReleaseCompleteReason ::= CHOICE +{ + noBandwidth NULL, -- bandwidth taken away or ARQ denied + gatekeeperResources NULL, -- exhausted + unreachableDestination NULL, -- no transport path to the destination + destinationRejection NULL, -- rejected at destination + invalidRevision NULL, + noPermission NULL, -- called party's gatekeeper rejects + unreachableGatekeeper NULL, -- terminal cannot reach gatekeeper + -- for ARQ + + gatewayResources NULL, + badFormatAddress NULL, + adaptiveBusy NULL, -- call is dropping due to LAN crowding + inConf NULL, -- called party busy + undefinedReason NULL, + ... + facilityCallDeflection NULL, -- call was deflected using a Facility + -- message + securityDenied NULL, -- incompatible security settings + calledPartyNotRegistered NULL, -- used by gatekeeper when endpoint has + -- preGrantedARQ to bypass ARQ/ACF + callerNotRegistered NULL, -- used by gatekeeper when endpoint has + -- preGrantedARQ to bypass ARQ/ACF + newConnectionNeeded NULL, -- indicates that the Setup was not + -- accepted on this connection, but that + -- the Setup may be accepted on + -- a new connection + + nonStandardReason NonStandardParameter, + replaceWithConferenceInvite ConferenceIdentifier, -- call dropped due to + -- subsequent invitation + -- to a conference + -- (see 8.4.3.8/H.323) + + genericDataReason NULL, + neededFeatureNotSupported NULL, + tunnelledSignallingRejected NULL, + invalidCID NULL, + securityError SecurityErrors, + hopCountExceeded NULL +} + +Setup-UUIE ::= SEQUENCE +{ + protocolIdentifier ProtocolIdentifier, + h245Address TransportAddress OPTIONAL, + sourceAddress SEQUENCE OF AliasAddress OPTIONAL, + sourceInfo EndpointType, + destinationAddress SEQUENCE OF AliasAddress OPTIONAL, + destCallSignalAddress TransportAddress OPTIONAL, + destExtraCallInfo SEQUENCE OF AliasAddress OPTIONAL, + destExtraCRV SEQUENCE OF CallReferenceValue OPTIONAL, + activeMC BOOLEAN, + conferenceID ConferenceIdentifier, +} + +``` + +``` + +conferenceGoal CHOICE +{ + create NULL, + join NULL, + invite NULL, + ..., + capability-negotiation NULL, + callIndependentSupplementaryService NULL +}, +callServices QseriesOptions OPTIONAL, +callType CallType, +..., +sourceCallSignalAddress TransportAddress OPTIONAL, +remoteExtensionAddress AliasAddress OPTIONAL, +callIdentifier CallIdentifier, +h245SecurityCapability SEQUENCE OF H245Security OPTIONAL, +tokens SEQUENCE OF ClearToken OPTIONAL, +cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, +fastStart SEQUENCE OF OCTET STRING OPTIONAL, +mediaWaitForConnect BOOLEAN, +canOverlapSend BOOLEAN, +endpointIdentifier EndpointIdentifier OPTIONAL, +multipleCalls BOOLEAN, +maintainConnection BOOLEAN, +connectionParameters SEQUENCE -- additional gateway parameters +{ + connectionType ScnConnectionType, + numberOfScnConnections INTEGER (0..65535), + connectionAggregation ScnConnectionAggregation, + ... +} OPTIONAL, +language SEQUENCE OF IA5String (SIZE (1..32)) OPTIONAL, +-- RFC 5646 language tag +presentationIndicator PresentationIndicator OPTIONAL, +screeningIndicator ScreeningIndicator OPTIONAL, +serviceControl SEQUENCE OF ServiceControlSession OPTIONAL, +symmetricOperationRequired NULL OPTIONAL, +capacity CallCapacity OPTIONAL, +circuitInfo CircuitInfo OPTIONAL, +desiredProtocols SEQUENCE OF SupportedProtocols OPTIONAL, +neededFeatures SEQUENCE OF FeatureDescriptor OPTIONAL, +desiredFeatures SEQUENCE OF FeatureDescriptor OPTIONAL, +supportedFeatures SEQUENCE OF FeatureDescriptor OPTIONAL, +parallelH245Control SEQUENCE OF OCTET STRING OPTIONAL, +additionalSourceAddresses SEQUENCE OF ExtendedAliasAddress OPTIONAL, +hopCount INTEGER (1..31) OPTIONAL, +displayName SEQUENCE OF DisplayName OPTIONAL +} + +ScnConnectionType ::= CHOICE +{ + unknown NULL, -- should be selected when connection type is unknown + bChannel NULL, -- each individual connection on the SCN is 64 kbit/s. + -- Note that where SCN delivers 56 kbit/s usable data, + -- the actual bandwidth allocated on SCN is still + -- 64 kbit/s. + hybrid2x64 NULL, -- each connection is a 128 kbit/s hybrid call + hybrid384 NULL, -- each connection is an H0 (384 kbit/s) hybrid call + hybrid1536 NULL, -- each connection is an H11 (1536 kbit/s) hybrid call + hybrid1920 NULL, -- each connection is an H12 (1920 kbit/s) hybrid call + multirate NULL, -- bandwidth supplied by SCN using multirate. + -- In this case, the information transfer rate octet + -- in the bearer capability shall be set to multirate + -- and the rate multiplier octet shall denote the + +``` + +``` + +-- number of B channels. +... +} + +ScnConnectionAggregation ::= CHOICE +{ + auto NULL, -- aggregation mechanism is unknown + none NULL, -- call produced using a single SCN connection + h221 NULL, -- use H.221 framing to aggregate the connections + bonded-model1 NULL, -- use ISO/IEC 13871 bonding mode 1. + -- Use bonded-model to signal a bonded call if the + -- precise bonding mode to be used is unknown. + bonded-mode2 NULL, -- use ISO/IEC 13871 bonding mode 2 + bonded-mode3 NULL, -- use ISO/IEC 13871 bonding mode 3 + ... +} + +PresentationIndicator ::= CHOICE +{ + presentationAllowed NULL, + presentationRestricted NULL, + addressNotAvailable NULL, + ... +} + +ScreeningIndicator ::= ENUMERATED +{ + userProvidedNotScreened (0), + -- number was provided by a remote user + -- and has not been screened by a gatekeeper + userProvidedVerifiedAndPassed (1), + -- number was provided by user + -- equipment (or by a remote network), and has + -- been screened by a gatekeeper + userProvidedVerifiedAndFailed (2), + -- number was provided by user + -- equipment (or by a remote network), and the + -- gatekeeper has determined that the + -- information is incorrect + networkProvided (3), + -- number was provided by a gatekeeper + ... +} + +Facility-UUIE ::= SEQUENCE +{ + protocolIdentifier ProtocolIdentifier, + alternativeAddress TransportAddress OPTIONAL, + alternativeAliasAddress SEQUENCE OF AliasAddress OPTIONAL, + conferenceID ConferenceIdentifier OPTIONAL, + reason FacilityReason, + ..., + callIdentifier CallIdentifier, + destExtraCallInfo SEQUENCE OF AliasAddress OPTIONAL, + remoteExtensionAddress AliasAddress OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + conferences SEQUENCE OF ConferenceList OPTIONAL, + h245Address TransportAddress OPTIONAL, + fastStart SEQUENCE OF OCTET STRING OPTIONAL, + multipleCalls BOOLEAN, + maintainConnection BOOLEAN, + fastConnectRefused NULL OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL, +} + +``` + +``` + + circuitInfo CircuitInfo OPTIONAL, + featureSet FeatureSet OPTIONAL, + destinationInfo EndpointType OPTIONAL, + h245SecurityMode H245Security OPTIONAL + } + + ConferenceList ::= SEQUENCE + { + conferenceID ConferenceIdentifier OPTIONAL, + conferenceAlias AliasAddress OPTIONAL, + nonStandardData NonStandardParameter OPTIONAL, + ... + } + + FacilityReason ::= CHOICE + { + routeCallToGatekeeper NULL, -- call must use gatekeeper model + -- gatekeeper is alternativeAddress + callForwarded NULL, + routeCallToMC NULL, + undefinedReason NULL, + ..., + conferenceListChoice NULL, + startH245 NULL, -- recipient should connect to h245Address + noH245 NULL, -- endpoint does not support H.245 + newTokens NULL, + featureSetUpdate NULL, + forwardedElements NULL, + transportedInformation NULL + } + + Progress-UUIE ::= SEQUENCE + { + protocolIdentifier ProtocolIdentifier, + destinationInfo EndpointType, + h245Address TransportAddress OPTIONAL, + callIdentifier CallIdentifier, + h245SecurityMode H245Security OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + fastStart SEQUENCE OF OCTET STRING OPTIONAL, + ..., + multipleCalls BOOLEAN, + maintainConnection BOOLEAN, + fastConnectRefused NULL OPTIONAL + } + + TransportAddress ::= CHOICE + { + ipAddress SEQUENCE + { + ip OCTET STRING (SIZE(4)), + port INTEGER(0..65535) + }, + ipSourceRoute SEQUENCE + { + ip OCTET STRING (SIZE(4)), + port INTEGER(0..65535), + route SEQUENCE OF OCTET STRING (SIZE(4)), + routing CHOICE + { + strict NULL, + loose NULL, + ... + } + } + } + +``` + +``` + + }, + ... + }, + ipxAddress SEQUENCE + { + node OCTET STRING (SIZE(6)), + netnum OCTET STRING (SIZE(4)), + port OCTET STRING (SIZE(2)) + }, + ip6Address SEQUENCE + { + ip OCTET STRING (SIZE(16)), + port INTEGER(0..65535), + ... + }, + netBios OCTET STRING (SIZE(16)), + nsap OCTET STRING (SIZE(1..20)), + nonStandardAddress NonStandardParameter, + ... +} + +Status-UUIE ::= SEQUENCE +{ + protocolIdentifier ProtocolIdentifier, + callIdentifier CallIdentifier, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + ... +} + +StatusInquiry-UUIE ::= SEQUENCE +{ + protocolIdentifier ProtocolIdentifier, + callIdentifier CallIdentifier, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + ... +} + +SetupAcknowledge-UUIE ::= SEQUENCE +{ + protocolIdentifier ProtocolIdentifier, + callIdentifier CallIdentifier, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + ... +} + +Notify-UUIE ::= SEQUENCE +{ + protocolIdentifier ProtocolIdentifier, + callIdentifier CallIdentifier, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + ... + connectedAddress SEQUENCE OF AliasAddress OPTIONAL, + presentationIndicator PresentationIndicator OPTIONAL, + screeningIndicator ScreeningIndicator OPTIONAL, + destinationInfo EndpointType OPTIONAL, + displayName SEQUENCE OF DisplayName OPTIONAL +} + +``` + +-- Beginning of common message elements section + +``` + +EndpointType ::= SEQUENCE +{ + nonStandardData NonStandardParameter OPTIONAL, + vendor VendorIdentifier OPTIONAL, + gatekeeper GatekeeperInfo OPTIONAL, + gateway GatewayInfo OPTIONAL, + mcu McuInfo OPTIONAL, -- mc must be set as well + terminal TerminalInfo OPTIONAL, + mc BOOLEAN, -- shall not be set by itself + undefinedNode BOOLEAN, + ..., + set BIT STRING (SIZE(32)) OPTIONAL, + -- shall not be used with mc, gatekeeper + -- code points for the various SET devices + -- are defined in the respective SET Annexes + supportedTunnelledProtocols SEQUENCE OF TunnelledProtocol OPTIONAL + -- list of supported tunnelled protocols +} + +GatewayInfo ::= SEQUENCE +{ + protocol SEQUENCE OF SupportedProtocols OPTIONAL, + nonStandardData NonStandardParameter OPTIONAL, + ... +} + +SupportedProtocols ::= CHOICE +{ + nonStandardData NonStandardParameter, + h310 H310Caps, + h320 H320Caps, + h321 H321Caps, + h322 H322Caps, + h323 H323Caps, + h324 H324Caps, + voice VoiceCaps, + t120-only T120OnlyCaps, + ..., + nonStandardProtocol NonStandardProtocol, + t38FaxAnnexbOnly T38FaxAnnexbOnlyCaps, + sip SIPCaps +} + +H310Caps ::= SEQUENCE +{ + nonStandardData NonStandardParameter OPTIONAL, + ..., + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix +} + +H320Caps ::= SEQUENCE +{ + nonStandardData NonStandardParameter OPTIONAL, + ..., + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix +} + +H321Caps ::= SEQUENCE +{ + nonStandardData NonStandardParameter OPTIONAL, + ..., + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, +} + +``` + +``` + + supportedPrefixes SEQUENCE OF SupportedPrefix + } + + H322Caps ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + ..., + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix + } + + H323Caps ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + ..., + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix + } + + H324Caps ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + ..., + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix + } + + VoiceCaps ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + ..., + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix + } + + T120OnlyCaps ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + ..., + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix + } + + NonStandardProtocol ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix, + ... + } + + T38FaxAnnexbOnlyCaps ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix, + t38FaxProtocol DataProtocolCapability, + t38FaxProfile T38FaxProfile, + ... + } + + SIPCaps ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + } + +``` + +``` + + dataRatesSupported SEQUENCE OF DataRate OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix OPTIONAL, + ... + } + + McuInfo ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + ... / + protocol SEQUENCE OF SupportedProtocols OPTIONAL + } + + TerminalInfo ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + ... + } + + GatekeeperInfo ::= SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + ... + } + + VendorIdentifier ::= SEQUENCE + { + vendor H221NonStandard, + productId OCTET STRING (SIZE(1..256)) OPTIONAL, -- per vendor + versionId OCTET STRING (SIZE(1..256)) OPTIONAL, -- per product + ... / + enterpriseNumber OBJECT IDENTIFIER OPTIONAL + } + + H221NonStandard ::= SEQUENCE + { + t35CountryCode INTEGER(0..255), + t35Extension INTEGER(0..255), + manufacturerCode INTEGER(0..65535), + ... + } + + TunnelledProtocol ::= SEQUENCE + { + id CHOICE + { + tunnelledProtocolObjectID OBJECT IDENTIFIER, + tunnelledProtocolAlternateID TunnelledProtocolAlternateIdentifier, + ... + }, + subIdentifier IA5String (SIZE (1..64)) OPTIONAL, + ... + } + + TunnelledProtocolAlternateIdentifier ::= SEQUENCE + { + protocolType IA5String (SIZE (1..64)), + protocolVariant IA5String (SIZE (1..64)) OPTIONAL, + ... + } + + NonStandardParameter ::= SEQUENCE + { + nonStandardIdentifier NonStandardIdentifier, + data OCTET STRING + } + +``` + +``` + +NonStandardIdentifier ::= CHOICE +{ + object OBJECT IDENTIFIER, + h221NonStandard H221NonStandard, + ... +} + +AliasAddress ::= CHOICE +{ + dialledDigits IA5String (SIZE (1..128)) (FROM ("0123456789#*,")), + h323-ID BMPString (SIZE (1..256)), -- Basic ISO/IEC 10646 (Unicode) + ..., + url-ID IA5String (SIZE(1..512)), -- URL style address + transportID TransportAddress, + email-ID IA5String (SIZE(1..512)), -- rfc822-compliant email address + partyNumber PartyNumber, + mobileUIM MobileUIM, + isupNumber IsupNumber +} + +AddressPattern ::= CHOICE +{ + wildcard AliasAddress, + range SEQUENCE + { + startOfRange PartyNumber, + endOfRange PartyNumber + }, + ... +} + +PartyNumber ::= CHOICE +{ + e164Number PublicPartyNumber, + -- the numbering plan is according to + -- ITU-T Recs E.163 and E.164. + dataPartyNumber NumberDigits, + -- not used, value reserved. + telexPartyNumber NumberDigits, + -- not used, value reserved. + privateNumber PrivatePartyNumber, + -- the numbering plan is according to + -- ISO/IEC 11571. + nationalStandardPartyNumber NumberDigits, + -- not used, value reserved. + ... +} + +PublicPartyNumber ::= SEQUENCE +{ + publicTypeOfNumber PublicTypeOfNumber, + publicNumberDigits NumberDigits +} + +PrivatePartyNumber ::= SEQUENCE +{ + privateTypeOfNumber PrivateTypeOfNumber, + privateNumberDigits NumberDigits +} + +NumberDigits ::= IA5String (SIZE (1..128)) (FROM ("0123456789#*,")) + +DisplayName ::= SEQUENCE + +``` + +``` + +{ + language IA5String OPTIONAL, -- RFC5646 language tag + name BMPString(SIZE(1..80)) +} + +PublicTypeOfNumber ::= CHOICE +{ + unknown NULL, + -- if used number digits carry prefix + -- indicating type + -- of number according to national + -- recommendations. + + internationalNumber NULL, + nationalNumber NULL, + networkSpecificNumber NULL, + -- not used, value reserved + + subscriberNumber NULL, + abbreviatedNumber NULL, + -- valid only for called party number at + -- the outgoing access, network + -- substitutes + -- appropriate number. + + ... +} + +PrivateTypeOfNumber ::= CHOICE +{ + unknown NULL, + level2RegionalNumber NULL, + level1RegionalNumber NULL, + pISNSpecificNumber NULL, + localNumber NULL, + abbreviatedNumber NULL, + ... +} + +MobileUIM ::= CHOICE +{ + ansi-41-uim ANSI-41-UIM, -- Americas standards Wireless Networks + gsm-uim GSM-UIM, -- European standards Wireless Networks + ... +} + +TBCD-STRING ::= IA5String (FROM ("0123456789#*abc")) + +ANSI-41-UIM ::= SEQUENCE +{ + imsi TBCD-STRING (SIZE (3..16)) OPTIONAL, + min TBCD-STRING (SIZE (3..16)) OPTIONAL, + mdn TBCD-STRING (SIZE (3..16)) OPTIONAL, + msisdn TBCD-STRING (SIZE (3..16)) OPTIONAL, + esn TBCD-STRING (SIZE (16)) OPTIONAL, + mscid TBCD-STRING (SIZE (3..16)) OPTIONAL, + system-id CHOICE + { + sid TBCD-STRING (SIZE (1..4)), + mid TBCD-STRING (SIZE (1..4)), + ... + }, + systemMyTypeCode OCTET STRING (SIZE (1)) OPTIONAL, + systemAccessType OCTET STRING (SIZE (1)) OPTIONAL, + qualificationInformationCode OCTET STRING (SIZE (1)) OPTIONAL, + sesn TBCD-STRING (SIZE (16)) OPTIONAL, +} + +``` + +``` + +soc TBCD-STRING (SIZE (3..16)) OPTIONAL, +... +-- IMSI refers to International Mobile Station Identification +-- MIN refers to Mobile Identification Number +-- MDN refers to Mobile Directory Number +-- MSISDN refers to Mobile Station ISDN number +-- ESN Refers to Electronic Serial Number +-- MSCID refers to Mobile Switching Center number + Market ID or System ID +-- SID refers to System Identification and MID refers to Market +-- Identification +-- SystemMyTypeCode refers to vendor identification number +-- SystemAccessType refers to the system access type like power down +-- registration or call +-- origination or Short Message response etc. +-- Qualification Information Code refers to the validity +-- SESN Refers to SIM Electronic Serial Number for Security purposes of +-- User Identification +-- SOC refers to System Operator Code +} + +GSM-UIM ::= SEQUENCE +{ + imsi TBCD-STRING (SIZE (3..16)) OPTIONAL, + tmsi OCTET STRING (SIZE (1..4)) OPTIONAL, + msisdn TBCD-STRING (SIZE (3..16)) OPTIONAL, + imei TBCD-STRING (SIZE (15..16)) OPTIONAL, + hplmn TBCD-STRING (SIZE (1..4)) OPTIONAL, + vplmn TBCD-STRING (SIZE (1..4)) OPTIONAL, + -- IMSI refers to International Mobile Station Identification + -- MSISDN refers to Mobile Station ISDN number + -- IMEI Refers to International Mobile Equipment Identification + -- VPLMN or HPLMN refers to Visiting or Home Public Land Mobile Network + -- number + ... +} + +IsupNumber ::= CHOICE +{ + e164Number IsupPublicPartyNumber, + -- the numbering plan is according to + -- ITU-T Recs E.163 and E.164. + dataPartyNumber IsupDigits, -- not used, value reserved. + telexPartyNumber IsupDigits, -- not used, value reserved. + privateNumber IsupPrivatePartyNumber, + -- the numbering plan is according to + -- ISO/IEC 11571. + nationalStandardPartyNumber IsupDigits, -- not used, value reserved. + ... +} + +IsupPublicPartyNumber ::= SEQUENCE +{ + natureOfAddress NatureOfAddress, + address IsupDigits, + ... +} + +IsupPrivatePartyNumber ::= SEQUENCE +{ + privateTypeOfNumber PrivateTypeOfNumber, + address IsupDigits, + ... +} + +``` + +``` + +NatureOfAddress ::= CHOICE +{ + unknown NULL, + subscriberNumber NULL, + nationalNumber NULL, + internationalNumber NULL, + networkSpecificNumber NULL, + routingNumberNationalFormat NULL, + routingNumberNetworkSpecificFormat NULL, + routingNumberWithCalledDirectoryNumber NULL, + ... +} + +IsupDigits ::= IA5String (SIZE (1..128)) (FROM ("0123456789ABCDE")) +ExtendedAliasAddress ::= SEQUENCE +{ + address AliasAddress, + presentationIndicator PresentationIndicator OPTIONAL, + screeningIndicator ScreeningIndicator OPTIONAL, + ... +} + +Endpoint ::= SEQUENCE +{ + nonStandardData NonStandardParameter OPTIONAL, + aliasAddress SEQUENCE OF AliasAddress OPTIONAL, + callSignalAddress SEQUENCE OF TransportAddress OPTIONAL, + rasAddress SEQUENCE OF TransportAddress OPTIONAL, + endpointType EndpointType OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + priority INTEGER(0..127) OPTIONAL, + remoteExtensionAddress SEQUENCE OF AliasAddress OPTIONAL, + destExtraCallInfo SEQUENCE OF AliasAddress OPTIONAL, + ... , + alternateTransportAddresses AlternateTransportAddresses OPTIONAL, + circuitInfo CircuitInfo OPTIONAL, + featureSet FeatureSet OPTIONAL +} + +AlternateTransportAddresses ::= SEQUENCE +{ + annexE SEQUENCE OF TransportAddress OPTIONAL, + ... , + sctp SEQUENCE OF TransportAddress OPTIONAL +} + +UseSpecifiedTransport ::= CHOICE +{ + tcp NULL, + annexE NULL, + ... , + sctp NULL +} + +AlternateGK ::= SEQUENCE +{ + rasAddress TransportAddress, + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + needToRegister BOOLEAN, + priority INTEGER (0..127), + ... +} + +``` + +``` + +AltGKInfo ::=SEQUENCE +{ + alternateGatekeeper SEQUENCE OF AlternateGK, + altGKisPermanent BOOLEAN, + ... +} + +SecurityServiceMode ::= CHOICE +{ + nonStandard NonStandardParameter, + none NULL, + default NULL, + ... -- can be extended with other specific modes +} + +SecurityCapabilities ::= SEQUENCE +{ + nonStandard NonStandardParameter OPTIONAL, + encryption SecurityServiceMode, + authentication SecurityServiceMode, + integrity SecurityServiceMode, + ... +} + +SecurityErrors ::= CHOICE +{ + securityWrongSyncTime NULL, -- either time server + -- problem or network delay + securityReplay NULL, -- replay attack encountered + securityWrongGeneralID NULL, -- wrong general ID + securityWrongSendersID NULL, -- wrong senders ID + securityIntegrityFailed NULL, -- integrity check failed + securityWrongOID NULL, -- wrong token OIDs or crypto alg + -- OIDs + securityDHmismatch NULL, -- mismatch of DH parameters + securityCertificateExpired NULL, -- certificate has expired + securityCertificateDateInvalid NULL, -- certificate is not yet valid + securityCertificateRevoked NULL, -- certificate was found revoked + securityCertificateNotReadable NULL, -- decoding error + securityCertificateSignatureInvalid NULL, -- wrong signature in the + -- certificate + securityCertificateMissing NULL, -- no certificate available + securityCertificateIncomplete NULL, -- missing expected certificate + -- extensions + securityUnsupportedCertificateAlgoOID NULL, -- crypto algs not understood + securityUnknownCA NULL, -- CA/root certificate could not + -- be found + ... +} + +SecurityErrors2 ::= CHOICE +{ + securityWrongSyncTime NULL, -- either time server problem or network + -- delay + securityReplay NULL, -- replay attack encountered + securityWrongGeneralID NULL, -- wrong general ID + securityWrongSendersID NULL, -- wrong senders ID + securityIntegrityFailed NULL, -- integrity check failed + securityWrongOID NULL, -- wrong token OIDs or crypto alg OIDs + ... +} + +H245Security ::= CHOICE +{ + +``` + +``` + + nonStandard NonStandardParameter, + noSecurity NULL, + tls SecurityCapabilities, + ipsec SecurityCapabilities, + +} + +QseriesOptions ::= SEQUENCE +{ + q932Full BOOLEAN, -- if true, indicates full support for Q.932 + q951Full BOOLEAN, -- if true, indicates full support for Q.951 + q952Full BOOLEAN, -- if true, indicates full support for Q.952 + q953Full BOOLEAN, -- if true, indicates full support for Q.953 + q955Full BOOLEAN, -- if true, indicates full support for Q.955 + q956Full BOOLEAN, -- if true, indicates full support for Q.956 + q957Full BOOLEAN, -- if true, indicates full support for Q.957 + q954Info Q954Details, + +} + +Q954Details ::= SEQUENCE +{ + conferenceCalling BOOLEAN, + threePartyService BOOLEAN, + +} + +GloballyUniqueID ::= OCTET STRING (SIZE(16)) +ConferenceIdentifier ::= GloballyUniqueID +RequestSeqNum ::= INTEGER (1..65535) +GatekeeperIdentifier ::= BMPString (SIZE(1..128)) +BandWidth ::= INTEGER (0..4294967295) -- in 100s of bits +CallReferenceValue ::= INTEGER (0..65535) +EndpointIdentifier ::= BMPString (SIZE(1..128)) +ProtocolIdentifier ::= OBJECT IDENTIFIER +TimeToLive ::= INTEGER (1..4294967295) -- in seconds +H248PackagesDescriptor ::= OCTET STRING -- This octet string contains ASN.1 + -- PER encoded H.248 + -- PackagesDescriptor + +H248SignalsDescriptor ::= OCTET STRING -- This octet string contains + -- ASN.1 PER encoded H.248 + -- SignalsDescriptor. + +FeatureDescriptor ::= GenericData + +CallIdentifier ::= SEQUENCE +{ + guid GloballyUniqueID, + +} + +EncryptIntAlg ::= CHOICE +{ + -- core encryption algorithms for RAS message integrity + nonStandard NonStandardParameter, + isoAlgorithm OBJECT IDENTIFIER, -- defined in ISO/IEC 9979 + +} + +NonIsoIntegrityMechanism ::= CHOICE +{ + -- HMAC mechanism used, no truncation, tagging may be necessary! + hMAC-MD5 NULL, + hMAC-iso10118-2-s EncryptIntAlg, -- according to ISO/IEC 10118-2 using + -- EncryptIntAlg as core block +} + +``` + +``` + + hMAC-isol0118-2-1 EncryptIntAlg, + -- encryption algorithm (short MAC) + -- according to ISO/IEC 10118-2 using + -- EncryptIntAlg as core block + -- encryption algorithm (long MAC) + hMAC-isol0118-3 OBJECT IDENTIFIER, -- according to ISO/IEC 10118-3 using + -- OID as hash function (OID is + -- SHA-1, + -- RIPE-MD160, + -- RIPE-MD128) + ... +} + +IntegrityMechanism ::= CHOICE +{ + -- for RAS message integrity + nonStandard NonStandardParameter, + digSig NULL, -- indicates to apply a digital signature + iso9797 OBJECT IDENTIFIER, -- according to ISO/IEC 9797 using OID as + -- core encryption algorithm (X-CBC MAC) + nonIsoIM NonIsoIntegrityMechanism, + ... +} + +ICV ::= SEQUENCE +{ + algorithmOID OBJECT IDENTIFIER, -- the algorithm used to compute the + -- signature + icv BIT STRING -- the computed cryptographic + -- integrity check value or signature +} + +FastStartToken ::= ClearToken (WITH COMPONENTS { ..., timeStamp PRESENT, dhkey +PRESENT, generalID PRESENT + -- set to "alias" -- }) + +EncodedFastStartToken ::= TYPE-IDENTIFIER.&Type (FastStartToken) + +CryptoH323Token ::= CHOICE +{ + cryptoEPPwdHash SEQUENCE + { + alias AliasAddress, -- alias of entity generating hash + timeStamp TimeStamp, -- timestamp used in hash + token HASHED { EncodedPwdCertToken -- generalID set to + -- "alias" -- } + }, + cryptoGKPwdHash SEQUENCE + { + gatekeeperId GatekeeperIdentifier, -- GatekeeperID of GK generating + -- hash + timeStamp TimeStamp, -- timestamp used in hash + token HASHED { EncodedPwdCertToken -- generalID set to + -- Gatekeeperid -- } + }, + cryptoEPPwdEncr ENCRYPTED { EncodedPwdCertToken -- generalID set to + -- Gatekeeperid -- }, + cryptoGKPwdEncr ENCRYPTED { EncodedPwdCertToken -- generalID set to + -- Gatekeeperid -- }, + cryptoEPCert SIGNED { EncodedPwdCertToken -- generalID set to + -- Gatekeeperid -- }, + cryptoGKCert SIGNED { EncodedPwdCertToken -- generalID set to alias -- + }, + cryptoFastStart SIGNED { EncodedFastStartToken }, + nestedcryptoToken CryptoToken, + ... +} + +``` + +``` + +DataRate ::= SEQUENCE +{ + nonStandardData NonStandardParameter OPTIONAL, + channelRate BandWidth, + channelMultiplier INTEGER (1..256) OPTIONAL, + ... +} + +CallLinkage ::= SEQUENCE +{ + globalCallId GloballyUniqueID OPTIONAL, + threadId GloballyUniqueID OPTIONAL, + ... +} + +SupportedPrefix ::= SEQUENCE +{ + nonStandardData NonStandardParameter OPTIONAL, + prefix AliasAddress, + ... +} + +CapacityReportingCapability ::= SEQUENCE +{ + canReportCallCapacity BOOLEAN, + ... +} + +CapacityReportingSpecification ::= SEQUENCE +{ + when SEQUENCE + { + callStart NULL OPTIONAL, + callEnd NULL OPTIONAL, + ... + }, + ... +} + +CallCapacity ::= SEQUENCE +{ + maximumCallCapacity CallCapacityInfo OPTIONAL, + currentCallCapacity CallCapacityInfo OPTIONAL, + ... +} + +CallCapacityInfo ::= SEQUENCE +{ + voiceGwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + h310GwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + h320GwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + h321GwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + h322GwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + h323GwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + h324GwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + t120OnlyGwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + t38FaxAnnexbOnlyGwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + terminalCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + mcuCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL, + ... + sipGwCallsAvailable SEQUENCE OF CallsAvailable OPTIONAL +} + +``` + +``` + +CallsAvailable ::= SEQUENCE +{ + calls INTEGER (0..4294967295), + group IA5String (SIZE (1..128)) OPTIONAL, + ..., + carrier CarrierInfo OPTIONAL +} + +CircuitInfo ::= SEQUENCE +{ + sourceCircuitID CircuitIdentifier OPTIONAL, + destinationCircuitID CircuitIdentifier OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + ... +} + +CircuitIdentifier ::= SEQUENCE +{ + cic CicInfo OPTIONAL, group GroupID OPTIONAL, + ..., + carrier CarrierInfo OPTIONAL +} + +CicInfo ::= SEQUENCE +{ + cic SEQUENCE OF OCTET STRING (SIZE (2..4)), + pointCode OCTET STRING (SIZE (2..5)), + ... +} + +GroupID ::= SEQUENCE +{ + member SEQUENCE OF INTEGER (0..65535) OPTIONAL, + group IA5String (SIZE (1..128)), + ... +} + +CarrierInfo ::= SEQUENCE +{ + carrierIdentificationCode OCTET STRING (SIZE (3..4)) OPTIONAL, + carrierName IA5String (SIZE (1..128)) OPTIONAL, + ... +} + +ServiceControlDescriptor ::= CHOICE +{ + url IA5String (SIZE(0..512)), -- indicates a URL- + -- referenced + -- protocol/resource + + signal H248SignalsDescriptor, + nonStandard NonStandardParameter, + callCreditServiceControl CallCreditServiceControl, + ... +} + +ServiceControlSession ::= SEQUENCE +{ + sessionId INTEGER (0..255), + contents ServiceControlDescriptor OPTIONAL, + reason CHOICE + { + open NULL, + refresh NULL, + close NULL, + } +} + +``` + +``` + + ... + }, + ... +} + +RasUsageInfoTypes ::= SEQUENCE +{ + nonStandardUsageTypes SEQUENCE OF NonStandardParameter, + startTime NULL OPTIONAL, + endTime NULL OPTIONAL, + terminationCause NULL OPTIONAL, + ... +} + +RasUsageSpecification ::= SEQUENCE +{ + when SEQUENCE + { + start NULL OPTIONAL, + end NULL OPTIONAL, + inIrr NULL OPTIONAL, + ... + }, + callStartingPoint SEQUENCE + { + alerting NULL OPTIONAL, + connect NULL OPTIONAL, + ... + } OPTIONAL, + required RasUsageInfoTypes, + ... +} + +RasUsageInformation ::= SEQUENCE +{ + nonStandardUsageFields SEQUENCE OF NonStandardParameter, + alertingTime Timestamp OPTIONAL, + connectTime Timestamp OPTIONAL, + endTime Timestamp OPTIONAL, + ... +} + +CallTerminationCause ::= CHOICE +{ + releaseCompleteReason ReleaseCompleteReason, + releaseCompleteCauseIE OCTET STRING (SIZE(2..32)), + ... +} + +BandwidthDetails ::= SEQUENCE +{ + sender BOOLEAN, -- TRUE=sender, FALSE=receiver + multicast BOOLEAN, -- TRUE if stream is multicast + bandwidth BandWidth, -- Bandwidth used for stream + rtcpAddresses TransportChannelInfo, -- RTCP addresses for media stream + ... +} + +CallCreditCapability ::= SEQUENCE +{ + canDisplayAmountString BOOLEAN OPTIONAL, + canEnforceDurationLimit BOOLEAN OPTIONAL, + ... +} + +``` + +``` + +CallCreditServiceControl ::= SEQUENCE +{ + amountString BMPString (SIZE (1..512)) OPTIONAL, -- (Unicode) + billingMode CHOICE + { + credit NULL, + debit NULL, + ... + } OPTIONAL, + callDurationLimit INTEGER (1..4294967295) OPTIONAL, -- in seconds + enforceCallDurationLimit BOOLEAN OPTIONAL, + callStartingPoint CHOICE + { + alerting NULL, + connect NULL, + ... + } OPTIONAL, + ... +} + +GenericData ::= SEQUENCE +{ + id GenericIdentifier, + parameters SEQUENCE (SIZE (1..512)) OF EnumeratedParameter + OPTIONAL, + ... +} + +GenericIdentifier ::= CHOICE +{ + standard INTEGER (0..16383,...), + oid OBJECT IDENTIFIER, + nonStandard GloballyUniqueID, + ... +} + +EnumeratedParameter ::= SEQUENCE +{ + id GenericIdentifier, + content Content OPTIONAL, + ... +} + +Content ::= CHOICE +{ + raw OCTET STRING, + text IA5String, + unicode BMPString, + bool BOOLEAN, + number8 INTEGER (0..255), + number16 INTEGER (0..65535), + number32 INTEGER (0..4294967295), + id GenericIdentifier, + alias AliasAddress, + transport TransportAddress, + compound SEQUENCE (SIZE (1..512)) OF EnumeratedParameter, + nested SEQUENCE (SIZE (1..16)) OF GenericData, + ... +} + +FeatureSet ::= SEQUENCE +{ + replacementFeatureSet BOOLEAN, +} + +``` + +``` + + neededFeatures SEQUENCE OF FeatureDescriptor OPTIONAL, + desiredFeatures SEQUENCE OF FeatureDescriptor OPTIONAL, + supportedFeatures SEQUENCE OF FeatureDescriptor OPTIONAL, + ... +} + +TransportChannelInfo ::= SEQUENCE +{ + sendAddress TransportAddress OPTIONAL, + recvAddress TransportAddress OPTIONAL, + ... +} + +RTPSession ::= SEQUENCE +{ + rtpAddress TransportChannelInfo, + rtcpAddress TransportChannelInfo, + cname PrintableString, + ssrc INTEGER (1..4294967295), + sessionId INTEGER (1..255), + associatedSessionIds SEQUENCE OF INTEGER (1..255), + ..., + multicast NULL OPTIONAL, + bandwidth BandWidth OPTIONAL +} + +RehomingModel ::= CHOICE +{ + gatekeeperBased NULL, + endpointBased NULL +} + +RasMessage ::= CHOICE +{ + gatekeeperRequest GatekeeperRequest, + gatekeeperConfirm GatekeeperConfirm, + gatekeeperReject GatekeeperReject, + registrationRequest RegistrationRequest, + registrationConfirm RegistrationConfirm, + registrationReject RegistrationReject, + unregistrationRequest UnregistrationRequest, + unregistrationConfirm UnregistrationConfirm, + unregistrationReject UnregistrationReject, + admissionRequest AdmissionRequest, + admissionConfirm AdmissionConfirm, + admissionReject AdmissionReject, + bandwidthRequest BandwidthRequest, + bandwidthConfirm BandwidthConfirm, + bandwidthReject BandwidthReject, + disengageRequest DisengageRequest, + disengageConfirm DisengageConfirm, + disengageReject DisengageReject, + locationRequest LocationRequest, + locationConfirm LocationConfirm, + locationReject LocationReject, + infoRequest InfoRequest, + infoRequestResponse InfoRequestResponse, + nonStandardMessage NonStandardMessage, + unknownMessageResponse UnknownMessageResponse, + ..., + requestInProgress RequestInProgress, + resourcesAvailableIndicate ResourcesAvailableIndicate, + resourcesAvailableConfirm ResourcesAvailableConfirm, + infoRequestAck InfoRequestAck, +} + +``` + +``` + + infoRequestNak InfoRequestNak, + serviceControlIndication ServiceControlIndication, + serviceControlResponse ServiceControlResponse, + admissionConfirmSequence SEQUENCE OF AdmissionConfirm +} + +``` + +GatekeeperRequest ::= SEQUENCE --(GRQ) + +``` + +{ + requestSeqNum RequestSeqNum, + protocolIdentifier ProtocolIdentifier, + nonStandardData NonStandardParameter OPTIONAL, + rasAddress TransportAddress, + endpointType EndpointType, + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + callServices QseriesOptions OPTIONAL, + endpointAlias SEQUENCE OF AliasAddress OPTIONAL, + ... + alternateEndpoints SEQUENCE OF Endpoint OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + authenticationCapability SEQUENCE OF AuthenticationMechanism OPTIONAL, + algorithmOIDs SEQUENCE OF OBJECT IDENTIFIER OPTIONAL, + integrity SEQUENCE OF IntegrityMechanism OPTIONAL, + integrityCheckValue ICV OPTIONAL, + supportsAltGK NULL OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + supportsAssignedGK BOOLEAN, + assignedGatekeeper AlternateGK OPTIONAL +} + +``` + +GatekeeperConfirm ::= SEQUENCE --(GCF) + +``` + +{ + requestSeqNum RequestSeqNum, + protocolIdentifier ProtocolIdentifier, + nonStandardData NonStandardParameter OPTIONAL, + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + rasAddress TransportAddress, + ... + alternateGatekeeper SEQUENCE OF AlternateGK OPTIONAL, + authenticationMode AuthenticationMechanism OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + algorithmOID OBJECT IDENTIFIER OPTIONAL, + integrity SEQUENCE OF IntegrityMechanism OPTIONAL, + integrityCheckValue ICV OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + assignedGatekeeper AlternateGK OPTIONAL, + rehomingModel RehomingModel OPTIONAL +} + +``` + +GatekeeperReject ::= SEQUENCE --(GRJ) + +``` + +{ + requestSeqNum RequestSeqNum, + protocolIdentifier ProtocolIdentifier, + nonStandardData NonStandardParameter OPTIONAL, + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + rejectReason GatekeeperRejectReason, + ... + altGKInfo AltGKInfo OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, +} + +``` + +``` + + integrityCheckValue ICV OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL +} + +GatekeeperRejectReason ::= CHOICE +{ + resourceUnavailable NULL, + terminalExcluded NULL, -- permission failure, not a resource + -- failure + invalidRevision NULL, + undefinedReason NULL, + ... + securityDenial NULL, + genericDataReason NULL, + neededFeatureNotSupported NULL, + securityError SecurityErrors +} + +RegistrationRequest ::= SEQUENCE -- (RRQ) +{ + requestSeqNum RequestSeqNum, + protocolIdentifier ProtocolIdentifier, + nonStandardData NonStandardParameter OPTIONAL, + discoveryComplete BOOLEAN, + callSignalAddress SEQUENCE OF TransportAddress, + rasAddress SEQUENCE OF TransportAddress, + terminalType EndpointType, + terminalAlias SEQUENCE OF AliasAddress OPTIONAL, + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + endpointVendor VendorIdentifier, + ... + alternateEndpoints SEQUENCE OF Endpoint OPTIONAL, + timeToLive TimeToLive OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + keepAlive BOOLEAN, + endpointIdentifier EndpointIdentifier OPTIONAL, + willSupplyUUIEs BOOLEAN, + maintainConnection BOOLEAN, + alternateTransportAddresses AlternateTransportAddresses OPTIONAL, + additiveRegistration NULL OPTIONAL, + terminalAliasPattern SEQUENCE OF AddressPattern OPTIONAL, + supportsAltGK NULL OPTIONAL, + usageReportingCapability RasUsageInfoTypes OPTIONAL, + multipleCalls BOOLEAN OPTIONAL, + supportedH248Packages SEQUENCE OF H248PackagesDescriptor OPTIONAL, + callCreditCapability CallCreditCapability OPTIONAL, + capacityReportingCapability CapacityReportingCapability OPTIONAL, + capacity CallCapacity OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + restart NULL OPTIONAL, + supportsACFSequences NULL OPTIONAL, + supportsAssignedGK BOOLEAN, + assignedGatekeeper AlternateGK OPTIONAL, + transportQOS TransportQOS OPTIONAL, + language SEQUENCE OF IA5String(SIZE (1..32)) OPTIONAL +} + +RegistrationConfirm ::= SEQUENCE -- (RCF) +{ + requestSeqNum RequestSeqNum, + +``` + +``` + +protocolIdentifier ProtocolIdentifier, +nonStandardData NonStandardParameter OPTIONAL, +callSignalAddress SEQUENCE OF TransportAddress, +terminalAlias SEQUENCE OF AliasAddress OPTIONAL, +gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, +endpointIdentifier EndpointIdentifier, +... +alternateGatekeeper SEQUENCE OF AlternateGK OPTIONAL, +timeToLive TimeToLive OPTIONAL, +tokens SEQUENCE OF ClearToken OPTIONAL, +cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, +integrityCheckValue ICV OPTIONAL, +willRespondToIRR BOOLEAN, +preGrantedARQ SEQUENCE +{ + makeCall BOOLEAN, + useGKCallSignalAddressToMakeCall BOOLEAN, + answerCall BOOLEAN, + useGKCallSignalAddressToAnswer BOOLEAN, + ... + irrFrequencyInCall INTEGER (1..65535) OPTIONAL, -- in seconds; + -- not present + -- if GK does + -- not want IRRs + totalBandwidthRestriction BandWidth OPTIONAL, -- total limit + -- for all + -- concurrent + -- calls + alternateTransportAddresses AlternateTransportAddresses OPTIONAL, + useSpecifiedTransport UseSpecifiedTransport OPTIONAL +} OPTIONAL, +maintainConnection BOOLEAN, +serviceControl SEQUENCE OF ServiceControlSession +OPTIONAL, +supportsAdditiveRegistration NULL OPTIONAL, +terminalAliasPattern SEQUENCE OF AddressPattern OPTIONAL, +supportedPrefixes SEQUENCE OF SupportedPrefix OPTIONAL, +usageSpec SEQUENCE OF RasUsageSpecification +OPTIONAL, +featureServerAlias AliasAddress OPTIONAL, +capacityReportingSpec CapacityReportingSpecification OPTIONAL, +featureSet FeatureSet OPTIONAL, +genericData SEQUENCE OF GenericData OPTIONAL, +assignedGatekeeper AlternateGK OPTIONAL, +rehomingModel RehomingModel OPTIONAL, +transportQOS TransportQOS OPTIONAL, +language SEQUENCE OF IA5String(SIZE (1..32)) OPTIONAL +} + +RegistrationReject ::= SEQUENCE -- (RRJ) +{ + requestSeqNum RequestSeqNum, + protocolIdentifier ProtocolIdentifier, + nonStandardData NonStandardParameter OPTIONAL, + rejectReason RegistrationRejectReason, + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + ... + altGKInfo AltGKInfo OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + assignedGatekeeper AlternateGK OPTIONAL +} + +``` + +``` + +} + +RegistrationRejectReason ::= CHOICE +{ + discoveryRequired NULL, + invalidRevision NULL, + invalidCallSignalAddress NULL, + invalidRASAddress NULL, -- supplied address is invalid + duplicateAlias SEQUENCE OF AliasAddress, + -- alias registered to another + -- endpoint + + invalidTerminalType NULL, + undefinedReason NULL, + transportNotSupported NULL, -- one or more of the transports + ..., + transportQOSNotSupported NULL, -- endpoint QoS not supported + resourceUnavailable NULL, -- gatekeeper resources exhausted + invalidAlias NULL, -- alias not consistent with + -- gatekeeper rules + + securityDenial NULL, + fullRegistrationRequired NULL, -- registration permission has + -- expired + + additiveRegistrationNotSupported NULL, + invalidTerminalAliases SEQUENCE + { + terminalAlias SEQUENCE OF AliasAddress OPTIONAL, + terminalAliasPattern SEQUENCE OF AddressPattern OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix OPTIONAL, + ... + }, + genericDataReason NULL, + neededFeatureNotSupported NULL, + securityError SecurityErrors, + registerWithAssignedGK NULL +} + +UnregistrationRequest ::= SEQUENCE -- (URQ) +{ + requestSeqNum RequestSeqNum, + callSignalAddress SEQUENCE OF TransportAddress, + endpointAlias SEQUENCE OF AliasAddress OPTIONAL, + nonStandardData NonStandardParameter OPTIONAL, + endpointIdentifier EndpointIdentifier OPTIONAL, + ..., + alternateEndpoints SEQUENCE OF Endpoint OPTIONAL, + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + reason UnregRequestReason OPTIONAL, + endpointAliasPattern SEQUENCE OF AddressPattern OPTIONAL, + supportedPrefixes SEQUENCE OF SupportedPrefix OPTIONAL, + alternateGatekeeper SEQUENCE OF AlternateGK OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + assignedGatekeeper AlternateGK OPTIONAL +} + +UnregRequestReason ::= CHOICE +{ + reregistrationRequired NULL, + ttlExpired NULL, + securityDenial NULL, + undefinedReason NULL, + ... +} + +``` + +``` + + maintenance NULL, + securityError SecurityErrors2, + registerWithAssignedGK NULL +} + +UnregistrationConfirm ::= SEQUENCE -- (UCF) +{ + requestSeqNum RequestSeqNum, + nonStandardData NonStandardParameter OPTIONAL, + ..., + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + assignedGatekeeper AlternateGK OPTIONAL +} + +UnregistrationReject ::= SEQUENCE -- (URJ) +{ + requestSeqNum RequestSeqNum, + rejectReason UnregRejectReason, + nonStandardData NonStandardParameter OPTIONAL, + ..., + altGKInfo AltGKInfo OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL +} + +UnregRejectReason ::= CHOICE +{ + notCurrentlyRegistered NULL, + callInProgress NULL, + undefinedReason NULL, + ..., + permissionDenied NULL, -- requesting user not allowed to + -- unregister specified user + securityDenial NULL, + securityError SecurityErrors2 +} + +AdmissionRequest ::= SEQUENCE -- (ARQ) +{ + requestSeqNum RequestSeqNum, + callType CallType, + callModel CallModel OPTIONAL, + endpointIdentifier EndpointIdentifier, + destinationInfo SEQUENCE OF AliasAddress OPTIONAL, + destCallSignalAddress TransportAddress OPTIONAL, + destExtraCallInfo SEQUENCE OF AliasAddress OPTIONAL, + srcInfo SEQUENCE OF AliasAddress, + srcCallSignalAddress TransportAddress OPTIONAL, + bandWidth BandWidth, + callReferenceValue CallReferenceValue, + nonStandardData NonStandardParameter OPTIONAL, + callServices QseriesOptions OPTIONAL, + conferenceID ConferenceIdentifier, + activeMC BOOLEAN, + answerCall BOOLEAN, -- answering a call + ..., + canMapAlias BOOLEAN, -- can handle alias address + callIdentifier CallIdentifier, +} + +``` + +``` + +srcAlternatives SEQUENCE OF Endpoint OPTIONAL, +destAlternatives SEQUENCE OF Endpoint OPTIONAL, +gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, +tokens SEQUENCE OF ClearToken OPTIONAL, +cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, +integrityCheckValue ICV OPTIONAL, +transportQOS TransportQOS OPTIONAL, +willSupplyUUIEs BOOLEAN, +callLinkage CallLinkage OPTIONAL, +gatewayDataRate DataRate OPTIONAL, +capacity CallCapacity OPTIONAL, +circuitInfo CircuitInfo OPTIONAL, +desiredProtocols SEQUENCE OF SupportedProtocols OPTIONAL, +desiredTunnelledProtocol TunnelledProtocol OPTIONAL, +featureSet FeatureSet OPTIONAL, +genericData SEQUENCE OF GenericData OPTIONAL, +canMapSrcAlias BOOLEAN +} + +CallType ::= CHOICE +{ + pointToPoint NULL, -- Point-to-point + oneToN NULL, -- no interaction (FFS) + nToOne NULL, -- no interaction (FFS) + nToN NULL, -- interactive (multipoint) + ... +} + +CallModel ::= CHOICE +{ + direct NULL, + gatekeeperRouted NULL, + ... +} + +TransportQOS ::= CHOICE +{ + endpointControlled NULL, + gatekeeperControlled NULL, + noControl NULL, + ... + qoSCapabilities SEQUENCE SIZE(1..256) OF QOSCapability +} + +AdmissionConfirm ::= SEQUENCE -- (ACF) +{ + requestSeqNum RequestSeqNum, + bandWidth BandWidth, + callModel CallModel, + destCallSignalAddress TransportAddress, + irrFrequency INTEGER (1..65535) OPTIONAL, + nonStandardData NonStandardParameter OPTIONAL, + ... + destinationInfo SEQUENCE OF AliasAddress OPTIONAL, + destExtraCallInfo SEQUENCE OF AliasAddress OPTIONAL, + destinationType EndpointType OPTIONAL, + remoteExtensionAddress SEQUENCE OF AliasAddress OPTIONAL, + alternateEndpoints SEQUENCE OF Endpoint OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + transportQOS TransportQOS OPTIONAL, + willRespondToIRR BOOLEAN, + uuiesRequested UUIEsRequested, +} + +``` + +``` + +language SEQUENCE OF IA5String (SIZE (1..32)) OPTIONAL, +alternateTransportAddresses AlternateTransportAddresses OPTIONAL, +useSpecifiedTransport UseSpecifiedTransport OPTIONAL, +circuitInfo CircuitInfo OPTIONAL, +usageSpec SEQUENCE OF RasUsageSpecification OPTIONAL, +supportedProtocols SEQUENCE OF SupportedProtocols OPTIONAL, +serviceControl SEQUENCE OF ServiceControlSession OPTIONAL, +multipleCalls BOOLEAN OPTIONAL, +featureSet FeatureSet OPTIONAL, +genericData SEQUENCE OF GenericData OPTIONAL, +modifiedSrcInfo SEQUENCE OF AliasAddress OPTIONAL, +assignedGatekeeper AlternateGK OPTIONAL +} + +UUIEsRequested ::= SEQUENCE +{ + setup BOOLEAN, + callProceeding BOOLEAN, + connect BOOLEAN, + alerting BOOLEAN, + information BOOLEAN, + releaseComplete BOOLEAN, + facility BOOLEAN, + progress BOOLEAN, + empty BOOLEAN, + ..., + status BOOLEAN, + statusInquiry BOOLEAN, + setupAcknowledge BOOLEAN, + notify BOOLEAN +} + +AdmissionReject ::= SEQUENCE --(ARJ) +{ + requestSeqNum RequestSeqNum, + rejectReason AdmissionRejectReason, + nonStandardData NonStandardParameter OPTIONAL, + ..., + altGKInfo AltGKInfo OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + callSignalAddress SEQUENCE OF TransportAddress OPTIONAL, + integrityCheckValue ICV OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + assignedGatekeeper AlternateGK OPTIONAL +} + +AdmissionRejectReason ::= CHOICE +{ + calledPartyNotRegistered NULL, -- cannot translate address + invalidPermission NULL, -- permission has expired + requestDenied NULL, + undefinedReason NULL, + callerNotRegistered NULL, + routeCallToGatekeeper NULL, + invalidEndpointIdentifier NULL, + resourceUnavailable NULL, + ..., + securityDenial NULL, + qosControlNotSupported NULL, + incompleteAddress NULL, + aliasesInconsistent NULL, -- multiple aliases in request +} + +``` + +``` + + -- identify distinct people +routeCallToSCN SEQUENCE OF PartyNumber, +exceedsCallCapacity NULL, -- destination does not have the + -- capacity for this call +collectDestination NULL, +collectPIN NULL, +genericDataReason NULL, +neededFeatureNotSupported NULL, +securityError SecurityErrors2, +securityDHmismatch NULL, -- mismatch of DH parameters +noRouteToDestination NULL, -- destination unreachable +unallocatedNumber NULL, -- destination number unassigned +registerWithAssignedGK NULL +} + +``` + +BandwidthRequest ::= SEQUENCE --(BRQ) + +``` + +{ + requestSeqNum RequestSeqNum, + endpointIdentifier EndpointIdentifier, + conferenceID ConferenceIdentifier, + callReferenceValue CallReferenceValue, + callType CallType OPTIONAL, + bandWidth BandWidth, + nonStandardData NonStandardParameter OPTIONAL, + ..., + callIdentifier CallIdentifier, + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + answeredCall BOOLEAN, + callLinkage CallLinkage OPTIONAL, + capacity CallCapacity OPTIONAL, + usageInformation RasUsageInformation OPTIONAL, + bandwidthDetails SEQUENCE OF BandwidthDetails OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + transportQOS TransportQOS OPTIONAL +} + +``` + +BandwidthConfirm ::= SEQUENCE --(BCF) + +``` + +{ + requestSeqNum RequestSeqNum, + bandWidth BandWidth, + nonStandardData NonStandardParameter OPTIONAL, + ..., + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + capacity CallCapacity OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + transportQOS TransportQOS OPTIONAL +} + +``` + +BandwidthReject ::= SEQUENCE --(BRJ) + +``` + +{ + requestSeqNum RequestSeqNum, + rejectReason BandRejectReason, + allowedBandWidth BandWidth, + nonStandardData NonStandardParameter OPTIONAL, + ..., + altGKInfo AltGKInfo OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, +} + +``` + +``` + + genericData SEQUENCE OF GenericData OPTIONAL +} + +BandRejectReason ::= CHOICE +{ + notBound NULL, -- discovery permission has aged + invalidConferenceID NULL, -- possible revision + invalidPermission NULL, -- true permission violation + insufficientResources NULL, + invalidRevision NULL, + undefinedReason NULL, + ..., + securityDenial NULL, + securityError SecurityErrors2} + +LocationRequest ::= SEQUENCE --(LRQ) +{ + requestSeqNum RequestSeqNum, + endpointIdentifier EndpointIdentifier OPTIONAL, + destinationInfo SEQUENCE OF AliasAddress, + nonStandardData NonStandardParameter OPTIONAL, + replyAddress TransportAddress, + ..., + sourceInfo SEQUENCE OF AliasAddress OPTIONAL, + canMapAlias BOOLEAN, -- can handle alias address + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + desiredProtocols SEQUENCE OF SupportedProtocols OPTIONAL, + desiredTunnelledProtocol TunnelledProtocol OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + hopCount INTEGER (1..255) OPTIONAL, + circuitInfo CircuitInfo OPTIONAL, + callIdentifier CallIdentifier OPTIONAL, + bandWidth BandWidth OPTIONAL, + sourceEndpointInfo SEQUENCE OF AliasAddress OPTIONAL, + canMapSrcAlias BOOLEAN, + language SEQUENCE OF IA5String(SIZE (1..32)) OPTIONAL +} + +LocationConfirm ::= SEQUENCE --(LCF) +{ + requestSeqNum RequestSeqNum, + callSignalAddress TransportAddress, + rasAddress TransportAddress, + nonStandardData NonStandardParameter OPTIONAL, + ..., + destinationInfo SEQUENCE OF AliasAddress OPTIONAL, + destExtraCallInfo SEQUENCE OF AliasAddress OPTIONAL, + destinationType EndpointType OPTIONAL, + remoteExtensionAddress SEQUENCE OF AliasAddress OPTIONAL, + alternateEndpoints SEQUENCE OF Endpoint OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + alternateTransportAddresses AlternateTransportAddresses OPTIONAL, + supportedProtocols SEQUENCE OF SupportedProtocols OPTIONAL, + multipleCalls BOOLEAN OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + circuitInfo CircuitInfo OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL, +} + +``` + +``` + + modifiedSrcInfo SEQUENCE OF AliasAddress OPTIONAL, + bandWidth BandWidth OPTIONAL, + language SEQUENCE OF IA5String(SIZE (1..32)) OPTIONAL +} + +LocationReject ::= SEQUENCE -- (LRJ) +{ + requestSeqNum RequestSeqNum, + rejectReason LocationRejectReason, + nonStandardData NonStandardParameter OPTIONAL, + ... + altGKInfo AltGKInfo OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL +} + +LocationRejectReason ::= CHOICE +{ + notRegistered NULL, + invalidPermission NULL, -- exclusion by administrator or feature + requestDenied NULL, + undefinedReason NULL, + ... + securityDenial NULL, + aliasesInconsistent NULL, -- multiple aliases in request + -- identify distinct people + routeCalltoSCN SEQUENCE OF PartyNumber, + resourceUnavailable NULL, + genericDataReason NULL, + neededFeatureNotSupported NULL, + hopCountExceeded NULL, + incompleteAddress NULL, + securityError SecurityErrors2, + securityDHmismatch NULL, -- mismatch of DH parameters + noRouteToDestination NULL, -- destination unreachable + unallocatedNumber NULL -- destination number unassigned +} + +DisengageRequest ::= SEQUENCE -- (DRQ) +{ + requestSeqNum RequestSeqNum, + endpointIdentifier EndpointIdentifier, + conferenceID ConferenceIdentifier, + callReferenceValue CallReferenceValue, + disengageReason DisengageReason, + nonStandardData NonStandardParameter OPTIONAL, + ... + callIdentifier CallIdentifier, + gatekeeperIdentifier GatekeeperIdentifier OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + answeredCall BOOLEAN, + callLinkage CallLinkage OPTIONAL, + capacity CallCapacity OPTIONAL, + circuitInfo CircuitInfo OPTIONAL, + usageInformation RasUsageInformation OPTIONAL, + terminationCause CallTerminationCause OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL +} + +``` + +``` + +} + +DisengageReason ::= CHOICE +{ + forcedDrop NULL, -- gatekeeper is forcing the drop + normalDrop NULL, -- associated with normal drop + undefinedReason NULL, + ... +} + +DisengageConfirm ::= SEQUENCE -- (DCF) +{ + requestSeqNum RequestSeqNum, + nonStandardData NonStandardParameter OPTIONAL, + ..., + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + capacity CallCapacity OPTIONAL, + circuitInfo CircuitInfo OPTIONAL, + usageInformation RasUsageInformation OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + assignedGatekeeper AlternateGK OPTIONAL +} + +DisengageReject ::= SEQUENCE -- (DRJ) +{ + requestSeqNum RequestSeqNum, + rejectReason DisengageRejectReason, + nonStandardData NonStandardParameter OPTIONAL, + ..., + altGKInfo AltGKInfo OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL +} + +DisengageRejectReason ::= CHOICE +{ + notRegistered NULL, -- not registered with gatekeeper + requestToDropOther NULL, -- cannot request drop for others + ..., + securityDenial NULL, + securityError SecurityErrors2 +} + +InfoRequest ::= SEQUENCE -- (IRQ) +{ + requestSeqNum RequestSeqNum, + callReferenceValue CallReferenceValue, + nonStandardData NonStandardParameter OPTIONAL, + replyAddress TransportAddress OPTIONAL, + ..., + callIdentifier CallIdentifier, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + uuiesRequested UUIEsRequested OPTIONAL, + callLinkage CallLinkage OPTIONAL, + usageInfoRequested RasUsageInfoTypes OPTIONAL, + segmentedResponseSupported NULL OPTIONAL, + nextSegmentRequested INTEGER (0..65535) OPTIONAL, + capacityInfoRequested NULL OPTIONAL, +} + +``` + +``` + + genericData SEQUENCE OF GenericData OPTIONAL, + assignedGatekeeper AlternateGK OPTIONAL +} + +InfoRequestResponse ::= SEQUENCE -- (IRR) +{ + nonStandardData NonStandardParameter OPTIONAL, + requestSeqNum RequestSeqNum, + endpointType EndpointType, + endpointIdentifier EndpointIdentifier, + rasAddress TransportAddress, + callSignalAddress SEQUENCE OF TransportAddress, + endpointAlias SEQUENCE OF AliasAddress OPTIONAL, + perCallInfo SEQUENCE OF SEQUENCE + { + nonStandardData NonStandardParameter OPTIONAL, + callReferenceValue CallReferenceValue, + conferenceID ConferenceIdentifier, + originator BOOLEAN OPTIONAL, + audio SEQUENCE OF RTPSession OPTIONAL, + video SEQUENCE OF RTPSession OPTIONAL, + data SEQUENCE OF TransportChannelInfo OPTIONAL, + h245 TransportChannelInfo, + callSignalling TransportChannelInfo, + callType CallType, + bandWidth BandWidth, + callModel CallModel, + ... + callIdentifier CallIdentifier, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + substituteConfIDs SEQUENCE OF ConferenceIdentifier, + pdu SEQUENCE OF SEQUENCE + { + h323pdu H323-UU-PDU, + sent BOOLEAN -- TRUE is sent, FALSE is received + } OPTIONAL, + callLinkage CallLinkage OPTIONAL, + usageInformation RasUsageInformation OPTIONAL, + circuitInfo CircuitInfo OPTIONAL + } OPTIONAL, + ... + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + needResponse BOOLEAN, + capacity CallCapacity OPTIONAL, + irrStatus InfoRequestResponseStatus OPTIONAL, + unsolicited BOOLEAN, + genericData SEQUENCE OF GenericData OPTIONAL +} + +InfoRequestResponseStatus ::= CHOICE +{ + complete NULL, + incomplete NULL, + segment INTEGER (0..65535), + invalidCall NULL, + ... +} + +InfoRequestAck ::= SEQUENCE -- (IACK) +{ + +``` + +``` + + requestSeqNum RequestSeqNum, + nonStandardData NonStandardParameter OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + ... + } + + InfoRequestNak ::= SEQUENCE -- (INAK) + { + requestSeqNum RequestSeqNum, + nonStandardData NonStandardParameter OPTIONAL, + nakReason InfoRequestNakReason, + altGKInfo AltGKInfo OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + ... + } + + InfoRequestNakReason ::= CHOICE + { + notRegistered NULL, -- not registered with gatekeeper + securityDenial NULL, + undefinedReason NULL, + ..., + securityError SecurityErrors2 + } + + NonStandardMessage ::= SEQUENCE + { + requestSeqNum RequestSeqNum, + nonStandardData NonStandardParameter, + ..., + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL + } + + UnknownMessageResponse ::= SEQUENCE -- (XRS) + { + requestSeqNum RequestSeqNum, + ..., + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + messageNotUnderstood OCTET STRING + } + + RequestInProgress ::= SEQUENCE -- (RIP) + { + requestSeqNum RequestSeqNum, + nonStandardData NonStandardParameter OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + delay INTEGER(1..65535), + ... + } + + ResourcesAvailableIndicate ::= SEQUENCE -- (RAI) + +``` + +``` + +{ + requestSeqNum RequestSeqNum, + protocolIdentifier ProtocolIdentifier, + nonStandardData NonStandardParameter OPTIONAL, + endpointIdentifier EndpointIdentifier, + protocols SEQUENCE OF SupportedProtocols, + almostOutOfResources BOOLEAN, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + ... + capacity CallCapacity OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL +} + +``` + +ResourcesAvailableConfirm ::= SEQUENCE --(RAC) + +``` + +{ + requestSeqNum RequestSeqNum, + protocolIdentifier ProtocolIdentifier, + nonStandardData NonStandardParameter OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + ... + genericData SEQUENCE OF GenericData OPTIONAL +} + +``` + +ServiceControlIndication ::= SEQUENCE --(SCI) + +``` + +{ + requestSeqNum RequestSeqNum, + nonStandardData NonStandardParameter OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession, + endpointIdentifier EndpointIdentifier OPTIONAL, + callSpecific SEQUENCE + { + callIdentifier CallIdentifier, + conferenceID ConferenceIdentifier, + answeredCall BOOLEAN, + ... + } OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + ... +} + +``` + +ServiceControlResponse ::= SEQUENCE --(SCR) + +``` + +{ + requestSeqNum RequestSeqNum, + result CHOICE + { + started NULL, + failed NULL, + stopped NULL, + notAvailable NULL, + neededFeatureNotSupported NULL, + ... + } OPTIONAL, + nonStandardData NonStandardParameter OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + integrityCheckValue ICV OPTIONAL, +} + +``` + +``` + featureSet FeatureSet OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + +} + +END -- of ASN.1 +``` + +# **Annex I** + +## **H.263+ video packetization** + +(This annex forms an integral part of this Recommendation.) + +IETF RFC 2429 specifies the RTP payload format for H.263 video bitstreams that contain the new "H.263+" features adopted in version 2 (dated 1998) of Rec. ITU-T H.263 (includes the features using PLUSTYPE or Annex I/H.263 through Annex T/H.263). + +The ability to support the H.263 payload format of RFC 2190 as specified in Annex E is required for H.263 bitstreams which do not use the new version 2 features of Rec. ITU-T H.263, because this support is needed for compatibility with prior implementations. However, the new payload format specified in RFC 2429 should be used even for bitstreams which do not contain the new version 2 features, provided the newer payload format is within the capabilities of the receiving terminals. + +# Appendix I + +## RTP/RTCP algorithms + +(This appendix does not form an integral part of this Recommendation.) + +The referenced informative material may be found in the following proposed Internet Standard: + +- SCHULZRINNE (H.), CASNER (S.), FREDERICK (R.) and JACOBSON (V.): RFC 3550, RTP: A Transport Protocol for Real-Time Applications, *Internet Engineering Task Force*, 2003. + +# **Appendix II** + +## **RTP profile** + +(This appendix does not form an integral part of this Recommendation.) + +The referenced informative material may be found in the following proposed Internet Standard: + +- SCHULZRINNE (H.), CASNER (S.): RFC 3551, RTP Profile for Audio and Video Conferences with Minimal Control, *Internet Engineering Task Force*, 2003. + +# Appendix III + +## H.261 packetization + +(This appendix does not form an integral part of this Recommendation.) + +The referenced informative material may be found in the following proposed Internet Standard: + +- Even, R.: RFC 4587, RTP Payload Format for H.261 Video Streams, *Internet Engineering Task Force*, 2006. + +# Appendix IV + +## H.225.0 operation on different packet-based network protocol stacks + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides additional details concerning the operation of H.225.0 on various actual packet-based network protocol stacks. Packet-based networks used in this Recommendation shall provide both reliable and unreliable modes of operation, including a means to distinguish packet boundaries. + +## IV.1 TCP/IP/UDP + +Note that UDP can fragment and reassemble large video packets, but that failure to perform MB packetization may lead to the loss of an entire GOB. + +IP multicast should be used for GRQ distribution as opposed to media access layer broadcast. + +| Unreliable delivery applications | Call signalling and H.245 channel | +|----------------------------------|-----------------------------------| +| UDP | TPKT
_____
TCP | +| IP | | +| Link Layer | | +| Physical Layer | | + +A TPKT is a packet format as defined in IETF RFC 1006. It is used to delimit individual messages (PDUs) within the TCP stream, which itself provides a continuous stream of octets without explicit boundaries. A TPKT consists of a one-octet version number field, followed by a one-octet reserved field, followed by a two-octet length field, followed by the actual data. The version number field shall contain the value "3", the reserved field shall contain the value "0". The length field shall contain the length of the entire packet including the version number, the reserved and the length fields as a 16-bit big-endian word. + +### IV.1.1 Discovering the gatekeeper + +#### IV.1.1.1 Discovery using multicast address or well-known port + +Following the gatekeeper discovery and registration procedures described in clause 7/H.323, endpoints should use the following multicast address or well-known port when attempting to discover the gatekeeper as appropriate for their network configuration: + +- UDP Address for multicast communication with gatekeepers: 224.0.1.41 +- UDP port for multicast communication with gatekeepers: 1718 +- UDP port for unicast RAS communication where no "other agreement" exists: 1719 + +Note that "other agreement" may include registration of an endpoint with a gatekeeper. + +Note that implementations should pay attention to the scope of the multicast so as not to flood the Internet with discovery messages. + +Assuming a gatekeeper has an IP address for example of 134.134.12.1, the following signalling may occur: + +- LRQ or GRQ arrives at 134.134.12.1: port 1719; +- LRQ or GRQ arrives at 134.134.12.1: port 1718 (note that this may occur with v1 GKs); +- LRQ or GRQ arrives at 224.0.1.41: port 1718. + +The gatekeeper may transmit an LRQ to the following addresses: + +- 224.0.1.41: port 1718 (multicast to all GKs); +- X.X.X.X: port 1719 (to a specific GK). + +Port 1719 should only be used when a request is sent unicast. This allows the receiver to know whether it should send a reject (xRJ) to the sender (it should in all cases). + +Port 1718 should only be used when a request is sent multicast. The receiver should respond with the appropriate response, depending on the message. For LRQ no reject required, the receiver does not reply for multicast requests. For GRQ, a directed GRJ should be sent to the source of the GRQ. + +#### **IV.1.1.2 Discovery using DNS (informative)** + +##### **IV.1.1.2.1 A URL for gatekeepers** + +As a first step, note that a gatekeeper is identified by a transport address and a gatekeeperIdentifier, which is a string. A gatekeeper is a particular resource on the Internet, so it is reasonable to specify it in a Uniform Resource Locator (URL). The protocol spoken by the gatekeeper is RAS, so the URL for a gatekeeper could be given by: + +`ras://gkID@domainname` + +gkID is the gatekeeperIdentifier, and domainname is a DNS domain name which identifies the gatekeeper's domain. Note that this is not necessarily a Fully Qualified Domain Name (FQDN) with an A-record – it is not required that this domain name has a physical transport interface with an IP number recorded in the DNS. If it is a FQDN, however, it is reasonable to insist that its IP number is that of the gatekeeper to which the URL refers. In this case, it is allowed to add an optional port number to the URL: + +`ras://gkID@domainname:port_no.` + +If no port number is given, then the well-known value of 1719 is taken as a default. + +The more interesting case is when this is not an FQDN, and then the domain name does not refer to a transport address listed in the DNS. The domain name then can refer to a pure "gatekeeper zone of authority". The next clause explains how to find the gatekeeper in this case. + +##### **IV.1.1.2.2 Finding the URL** + +The URL does not solve the problem of locating the gatekeeper, it just gives a standard format for the information to find. The problem is how to produce a transport address and gatekeeperIdentifier for RAS signalling given the domain name of a gatekeeper. + +If the gatekeeper has an IETF RFC 822-compliant identifier, it is easy to extract a domain name from the IETF RFC 822-compliant identifier of a gatekeeper. In fact, it may be convenient to give IETF RFC 822-compliant identifiers to endpoints, and then to stipulate that the domain name part of the identifier refers to the gatekeeper domain. + +###### **IV.1.1.2.2.1 The SRV resource record query** + +The first solution uses the fact that the gatekeeper is basically a system service, and the transport address of a named system service can be extracted from DNS by using a query for a new type of DNS Resource Record, called SRV (for "service location record"). Given a domain name, an + +SRV record query will be made for the transport address of the RAS service for that domain. The domain name itself, or one returned in the SRV response, is used as the gatekeeperIdentifier. The SRV record and its use are defined in IETF RFC 2782. + +###### IV.1.1.2.2.2 The TXT record query + +All current DNS implementations support the TXT resource record. Basically this is some free text that can be returned for each domain name. It is possible to store many TXT resources for a single domain. The standard stipulates that all TXT records will be returned when a query is made for them. + +It is possible to use TXT queries if the SRV queries fail. Assume the same convention for extracting a domain name that was suggested above. Either IETF RFC 822 compliant strings (email "-like" names) or IETF RFC 1768 compliant strings (URLs) can be used for gatekeeperIdentifiers. In either case the domain name is used to make a DNS TXT query for the domain name. The returned resource records are lines of free text, and the terminal will then look for lines in the response of the form: + +ras [@][:] [] + +The field is an optional gatekeeper ID which is separate from the domain name. If this field is missing, then the domain itself is assumed to be the gatekeeper ID. + +The field can be either the name of the A-record which contains the gatekeeper's IP address, or a raw IP address in dotted form. The domain name need not be fully qualified; if it is not, the subdomain in which the TXT record was found should be appended to it to form the fully qualified A-record name. + +The optional [:] can be used to specify a port number other than the standard RAS port. + +The optional [] field specifies the order in which the listed gatekeepers should be accessed for discovery or LRQ queries if there is more than one RAS TXT record. Lower numbers have higher priority. + +Note that this format, if the field is missing, assumes that the gatekeeper IDs are in fact legal domain names. However, if it is necessary for a single host to support multiple logical gatekeepers, each with a separate ID, the format will support this. This is because separate A-records can contain the same IP address. + +White spaces are used as delimiters between **ras** and **gk id** if present or **domain name**, and between **portno** and **priority**. White spaces consist of any number of spaces or tabs. + +Examples of valid gatekeeper TXT records: + +- ras gk1 +- ras gk1.company.com +- ras gk1:1500 3 +- ras 172.11.22.33:1500 2 + +The client parses the returned lines, and from them obtains the transport address of the gatekeeper within that domain to which it can send RAS messages. + +Since DNS requires a server to return all TXT records associated with a domain name, the client can filter out and process only those records which are useful to it. It also allows DNS to return an ordered list of gatekeepers which can serve as alternatives and back-ups as defined in Rec. ITU-T H.323. + +Note that the server returned in such a query might be an actual transport address in dotted decimal notation, or it could be an FQDN which itself requires an A-record query in DNS to determine the transport address. The advantage of using an FQDN is the usual hiding of actual IP numbers. The advantage of using IP numbers is that a second DNS query is avoided, thus speeding up this pre-call setup time. + +##### IV.1.1.2.3 Gatekeeper processing of email-IDs during ARQ and LRQ + +When the **destinationInfo** field of an ARQ or LRQ message contains an **email-ID** alias address, the gatekeeper should first check its registration database for the alias. If it cannot be resolved, the gatekeeper should parse the alias to recover its domain portion. If no domain is given, the gatekeeper may generate a default domain. The domain is then used to locate one or more gatekeepers, using the procedures in IV.1.1.2.2. The gatekeeper may then query all gatekeepers thus found with an LRQ/LCF/LRJ message exchange. + +Note that more than one gatekeeper may have corresponding TXT records in a single DNS domain. Consequently, a single DNS domain can "contain" more than one H.323 zone. Therefore, even if a gatekeeper cannot resolve an email-ID whose domain portion is one of its default domains, it may still query other zones in the same DNS domain. + +If the gatekeeper is presented with an unregistered alias which is an **h323-id** and the ID can be interpreted as a legal user portion of an IETF RFC 822 name, the gatekeeper may interpret the alias as if it were an email-ID in its default domain and attempt to locate the alias in some other gatekeeper. Similarly, an email-ID from an incoming LRQ may be stripped of its domain name by the gatekeeper so that it may be located as an h323-ID. + +### IV.1.2 Endpoint-to-endpoint communications + +Endpoints which wish to receive calls from endpoints outside the zone of their gatekeeper should use the following port for the Call Signalling channel: + +- Endpoint TCP Call Signalling Port 1720 + +While it is permitted to use dynamic values for these ports to allow multiple endpoints in a single device, it must be understood that this will prevent interoperation with endpoints outside the zone of the gatekeeper except via a gateway in the zone. + +## IV.2 SPX/IPX + +Note that since there is no network reassembly of large packets, the use of MB fragmentation is essential. + +| Unreliable delivery applications | H.245 channel call signalling channel | +|----------------------------------|---------------------------------------| +| PXP | SPX | +| IPX | | +| Link Layer | | +| Physical Layer | | + +### IV.2.1 Discovering the gatekeeper + +In IPX terminology, a "socket" is the equivalent of a "port" in IP and a "TSAP Identifier" in this Recommendation and in Rec. ITU-T H.323. + +On IPX-based networks, the gatekeepers should advertise the "gatekeeper service type" defined below to allow endpoints to locate them on a network. Likewise, endpoints should query for the "gatekeeper service type" to find the location of the nearest gatekeeper. + +- Gatekeeper Service Type FFS. + +NOTE – The service type is referred to as the SAP socket in some IPX documentation. + +### IV.2.2 Endpoint-to-endpoint communication + +Endpoints which wish to receive calls from endpoints outside the zone of their gatekeeper should use the following sockets for Call signalling. + +– Endpoint IPX Call Signalling Port FFS. + +While it is permitted to use dynamic values for these sockets to allow multiple endpoints in a single device, it must be understood that this will prevent interoperation with endpoints outside the zone of the gatekeeper except via a gateway in the zone. + +## IV.3 SCTP + +The protocol stack of H.323 over SCTP looks as follows: + +| | | +|-----------------------------------------|----------------------------------------------------| +| Unreliable delivery applications | Call signalling with tunnelled call control | +| UDP | SCTP | +| IP | | +| Link Layer | | +| Physical Layer | | + +Each H.225.0 call signalling message shall be transferred in separate SCTP DATA chunk. No headers shall be added (i.e., no TPKT). Ordered delivery shall be specified. + +### IV.3.1 Streams + +All messages of the same call shall use same SCTP stream. Implementation may use different streams for different calls. + +### IV.3.2 Payload protocol identifiers + +SCTP may be used with undefined payload protocol identifier (0) or with 13, which is the number assigned to H.323 by IANA. + +# Appendix V + +## ASN.1 usage in this Recommendation + +(This appendix does not form an integral part of this Recommendation.) + +This appendix lists the ASN.1 conventions that have been used in this Recommendation. Future revisions of this Recommendation should use only these constructs. Additional ASN.1 constructs will only be considered in exceptional circumstances. + +## V.1 Tagging + +All tags within this Recommendation are AUTOMATIC TAGS. + +## V.2 Types + +The following types may occur in the ASN.1 definitions of this Recommendation. + +| | | | +|---------------|-------------------|--------------| +| BIT STRING | IA5String | OCTET STRING | +| BMPString | INTEGER | SEQUENCE | +| BOOLEAN | NULL | SEQUENCE OF | +| CHOICE | NumericString | SET | +| GeneralString | OBJECT IDENTIFIER | SET OF | + +## V.3 Constraints and ranges + +This Recommendation uses size constraints ("SIZE") for strings, SET OF and SEQUENCE OF, value range constraints for integers, and permitted alphabets ("FROM"). + +## V.4 Extensibility + +This Recommendation uses the extension marker (ellipsis "..."). + +# Appendix VI + +## H.225.0 identifiers of tunnelled signalling protocols + +(This appendix does not form an integral part of this Recommendation.) + +This Recommendation supports the tunnelling of non-H.323 call signalling protocols, as described in 10.4/H.323. The Annex M/H.323 series of Recommendations (M.1/H.323, M.2/H.323, etc.) defines tunnelling for specific protocols. A tunnelled protocol in this Recommendation is identified by information in the **TunnelledProtocol** ASN.1 structure defined in 7.6 and in Annex H. This appendix provides a list of **TunnelledProtocol** identifiers that have been allocated to specific tunnelled protocols. + +Tunnelled protocols that are defined as of this Recommendation are shown in Tables VI.1 and VI.2. Note that tunnelling is not restricted to the protocols listed in these tables. + +**Table VI.1 – Tunnelled protocols identified by tunnelledProtocolObjectID** + +| Tunnelling specification | Protocol specification | tunnelledProtocolObjectID | subIdentifier | +|--------------------------|-------------------------|------------------------------------------------------------------------------------|---------------| +| M.1/H.323 | ISO/IEC 11572 and 11582 | {iso(1) identified-organization(3) icd-ecma(12) private-isdn-signalling-domain(9)} | (None) | +| M.2/H.323 | Rec. ITU-T Q.763 (1988) | {itu-t(0) recommendation(0) q(17) 763} | "1988" | +| M.2/H.323 | Rec. ITU-T Q.763 (1993) | {itu-t(0) recommendation(0) q(17) 763} | "1993" | + +**Table VI.2 – Tunnelled protocols identified by TunnelledProtocolAlternateIdentifier** + +| Tunnelling specification | Protocol specification | protocolType | protocolVariant | subIdentifier | +|--------------------------|------------------------|--------------|-------------------------|---------------| +| M.2/H.323 | ANSI T1.113-1988 | "isup" | "ANSI T1.113-1988" | "1988" | +| M.2/H.323 | ETS 300 121 | "isup" | "ETS 300 121" | "121" | +| M.2/H.323 | ETS 300 356 | "isup" | "ETS 300 356" | "356" | +| M.2/H.323 | BELLCORE GR-317 | "isup" | "BELLCORE GR-317" | "317" | +| M.2/H.323 | JT-Q761-4 (1987-1992) | "isup" | "JT-Q761-4 (1987-1992)" | "87" | +| M.2/H.323 | JT-Q761-4 (1993) | "isup" | "JT-Q761-4 (1993)" | "93" | + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.235.2-200509-I_PDF-E/raw.md b/marked/H/T-REC-H.235.2-200509-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..90d34812ca3d132cab42b5dbbb57e26d96d84543 --- /dev/null +++ b/marked/H/T-REC-H.235.2-200509-I_PDF-E/raw.md @@ -0,0 +1,761 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.235.2** + +(09/2005) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Systems aspects + +--- + +**H.323 security: Signature security profile** + +ITU-T Recommendation H.235.2 + +ITU-T + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global communication. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font, with "ITU" in a larger, bold font above it. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.235.2** + +# **H.323 security: Signature security profile** + +## **Summary** + +This Recommendation describes an optional security profile for deploying digital signatures to secure the H.225.0 signalling. + +In earlier versions of the H.235 subseries, this profile was contained in Annex E/H.235. Appendices IV, V, VI to H.235.0 show the complete clause, figure, and table mapping between H.235 versions 3 and 4. + +### **Source** + +ITU-T Recommendation H.235.2 was approved on 13 September 2005 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +### **Keywords** + +Authentication, certificate, digital signature, encryption, integrity, key management, multimedia security, security profile. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2006 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|------|-------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 2.1 | Normative references..... | 1 | +| 2.2 | Informative references..... | 2 | +| 3 | Terms and definitions ..... | 2 | +| 4 | Symbols and abbreviations ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Overview ..... | 5 | +| 6.1 | H.323 requirements ..... | 7 | +| 7 | Digital signatures with public/private key pairs details (procedure II) ..... | 8 | +| 8 | Multipoint conferencing procedures..... | 9 | +| 9 | End-to-end authentication (procedure III)..... | 9 | +| 10 | Authentication-only ..... | 11 | +| 11 | Authentication and integrity ..... | 12 | +| 12 | Computation of the digital signature ..... | 12 | +| 13 | Verification of the digital signature..... | 13 | +| 14 | Handling of certificates..... | 13 | +| 15 | Usage illustration for procedure II..... | 15 | +| 15.1 | RAS message authentication, integrity and non-repudiation ..... | 15 | +| 15.2 | RAS authentication only..... | 16 | +| 15.3 | H.225.0 message authentication, integrity and non-repudiation ..... | 17 | +| 15.4 | H.245 message authentication and integrity..... | 17 | +| 16 | H.235 version 1 compatibility ..... | 18 | +| 17 | Multicast behaviour ..... | 18 | +| 18 | List of secure signalling messages..... | 18 | +| 18.1 | H.225.0 RAS ..... | 18 | +| 18.2 | H.225.0 call signalling..... | 19 | +| 19 | Usage of sendersID and generalID ..... | 19 | +| 20 | List of object identifiers..... | 20 | + + + +# H.323 security: Signature security profile + +# 1 Scope + +This Recommendation describes an optional security profile for deploying digital signatures to secure the H.225.0 signalling. + +# 2 References + +## 2.1 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.235 (1998), *Security and encryption for H-series (H.323 and other H.245-based) multimedia terminals*. +- ITU-T Recommendation H.235.0 (2005), *H.323 security: Framework for security in H-series (H.323 and other H.245-based) multimedia systems*. +- ITU-T Recommendation H.235.1 (2005), *H.323 security: Baseline security profile*. +- ITU-T Recommendation H.235.6 (2005), *H.323 security: Voice encryption profile with native H.235/H.245 key management*. +- ITU-T Recommendation H.245 (2005), *Control protocol for multimedia communication*. +- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*. +- ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*. +- ITU-T Recommendation X.509 (2005) | ISO/IEC 9594-8:2005, *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks*. +- ITU-T Recommendation X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*. +- ITU-T Recommendation X.803 (1994) | ISO/IEC 10745:1995, *Information technology – Open Systems Interconnection – Upper layers security model*. +- ITU-T Recommendation X.810 (1995) | ISO/IEC 10181-1:1996, *Information technology – Open Systems Interconnection – Security frameworks for open systems: Overview*. +- ITU-T Recommendation X.811 (1995) | ISO/IEC 10181-2:1996, *Information technology – Open Systems Interconnection – Security frameworks for open systems: Authentication framework*. + +- ISO/IEC 9798-3:1998, *Information technology – Security techniques – Entity authentication – Part 3: Mechanisms using digital signature techniques.* +- IETF RFC 3280 (2002), *Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile.* + +## 2.2 Informative references + +- [ISO/IEC 14888-3] ISO/IEC 14888-3:1998, *Information technology – Security techniques – Digital signatures with appendix – Part 3: Certificate-based mechanisms.* +- [PKCS] PKCS #1 v2.0: *RSA Cryptography Standard*; RSA Laboratories; October 1, 1998; . +- [PKCS] PKCS #7: *Cryptographic Message Syntax Standard*, An RSA Laboratories Technical Note, version 1.5, Revised November 1, 1993; +- [RFC1321] IETF RFC 1321 (1992), *The MD5 Message-Digest Algorithm.* +- [RFC3447] IETF RFC 3447 (2003), *Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1.* + +# 3 Terms and definitions + +For the purposes of this Recommendation, the definitions given in clauses 3/H.323, 3/H.225.0 and 3/H.245 apply along with those in this clause. Some of the terms used in this Recommendation are also defined in ITU-T Recs X.800 | ISO 7498-2, X.803 | ISO/IEC 10745, X.810 | ISO/IEC 10181-1 and X.811 | ISO/IEC 10181-2. + +**3.1 certification authorities:** Certification Authorities (CAs), when used in the context of electronic signature, certify public verification keys by issuing "Certificates". + +**3.2 certificate repositories:** Certificate repositories (e.g., an X.500 Directory) hold user certificates and Certificate Revocation Lists (CRLs). They are trusted to make that information accessible but are not responsible for the content or accuracy of the information they receive from the CAs or the RAs. + +**3.3 digital signature:** Is a cryptographic transformation (using an asymmetric cryptographic technique) of the numerical representation of a data message, such that any person having the signed message and the relevant public key can determine that: + +- the transformation was created using the private key corresponding to the relevant public key; and +- the signed message has not been altered since the cryptographic transformation. + +**3.4 on-line certificate status providers:** The On-line Certificate Status Protocol (OCSP) enables applications to determine the revocation state of an identified certificate. OCSP may be used to satisfy some of the operational requirements of providing revocation information in a more timely way than is possible with CRLs. On-line certificate status providers can be seen as an alternative to the use of off-line CRLs. + +**3.5 proxy:** The proxy is an intermediate H.323 entity similar to a gatekeeper. The proxy may be a separate network node or may be collocated with the functionality of an H.323 entity such as of the gatekeeper. The proxy may perform security tasks such as signature and certificate verification and access control. + +**3.6 registration authorities:** Registration authorities act as intermediaries between users and CAs. They receive requests from users and transmit them to the CAs in an appropriate form. + +**3.7 time stamping authorities:** Time stamping authorities are mandatory for non-repudiation in case of key loss or key compromise. In practice, they provide a counter-signature to anyone, including a reliable time, over a hash and a hash identifier. + +**3.8 trust service provider:** An entity, which can be used by other entities as a trusted intermediary in a communication or verification process, or as a trusted information service provider. + +This Recommendation uses the following terms for provisioning the security services. + +**3.9 authentication-only:** This security service of the signature security profile supports user authentication where the user authenticates when correctly digitally signing some piece of data by the private key. Note that this security service does not provide countermeasures against arbitrary cut and paste, message manipulation or tampering attacks. Authentication-only may be useful for security proxies that verify authenticity of the message (data origin authentication) when forwarding the message to another destination (e.g., Gatekeeper). + +NOTE – The forwarding usually changes certain parts of the message; thus end-to-end integrity cannot be realized. + +Nevertheless, authentication-only can be applied on a hop-by-hop basis as well. Procedure III specifies this security service for an end-to-end scenario while procedure II specifies this security service for the hop-by-hop case. + +**3.10 authentication and integrity:** This is a combined security service that supports message integrity in conjunction with user authentication. The user authenticates when correctly digitally signing some piece of data by the private key. In addition to that, the message is protected against tampering. Both security services are provided by the same security mechanism. Combined authentication and integrity is possible only on a hop-to-hop basis. Procedure II specifies this security service. + +NOTE – When digital signatures are applied, a non-repudiation security service may be supported; this depends also on the settings of the key usage bits of the signing key in the certificate (see also RFC 3280). + +# 4 Symbols and abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|---------------------------------------| +| ARQ | Admission Request | +| ASN.1 | Abstract Syntax Notation One | +| CA | Certification Authority | +| CRL | Certificate Revocation List | +| DH | Diffie-Hellman | +| DNS | Domain Name Service | +| EP | Endpoint | +| EPID | Endpoint Identifier | +| GK | Gatekeeper | +| GKID | Gatekeeper Identifier | +| GRQ | Gatekeeper Request | +| ICV | Integrity Check Value | +| IP | Internet Protocol | +| ITU | International Telecommunication Union | + +| | | +|------|----------------------------------------| +| LDAP | Light-weight Directory Access Protocol | +| LRQ | Location Request | +| MCU | Multipoint Control Unit | +| MD5 | Message Digest 5 | +| NAT | Network Address Translation | +| OID | Object Identifier | +| OCSP | Online Certificate Status Protocol | +| PKCS | Public-Key Crypto System | +| RA | Registration Authority | +| RAS | Registration, Admission and Status | +| RSA | Rivest, Shamir, Adleman | +| RTP | Real-Time Protocol | +| SHA | Secure Hash Algorithm | +| URL | Uniform Resource Locator | + +# 5 Conventions + +In this Recommendation the following conventions are used: + +- "shall" indicates a mandatory requirement. +- "should" indicates a suggested but optional course of action. +- "may" indicates an optional course of action rather than a recommendation that something take place. + +The signature security profile may use the **voice encryption security profile** of H.235.1 for achieving voice confidentiality if necessary. + +Procedures II and III specify how to implement the security services for different scenarios as hop-by-hop and end-to-end with different security mechanisms such as asymmetric cryptographic (digital signature) techniques. + +While the message integrity service always provides message authentication, the reverse is not always true. For the authentication-only mode, the integrity assured spans only a certain subset of message fields. This applies to integrity services realized by asymmetric means (e.g., digital signatures). Thus, in practice, a combined authentication and integrity service uses the same key material without introducing a security weakness. + +Moreover, all hop-by-hop security information is put into the **CryptoSignedToken** element. This information is recomputed at every hop according to procedure II. + +End-to-end security information on the other hand (only possible when using the H.323 proxy and procedure III), basically computes similar information as put in the **CryptoSignedToken**, but stores that information in a separate **CryptoToken** of the message. This information is not changed in transit. A separate object identifier allows distinguishing between hop-by-hop and end-to-end **CryptoTokens**. + +Asymmetric techniques using digital signatures may apply on a hop-by-hop and/or also on an end-to-end basis. + +# 6 Overview + +This Recommendation describes an optional security profile for deploying digital signatures to secure the H.225.0 signalling. H.323 security entities (terminals, gatekeepers, gateways, MCUs, etc.) may implement this signature security profile for improved security or whenever required. + +The signature security profile mandates the GK-routed model and is based upon the H.245 tunnelling techniques; support for non GK-routed models is for further study. + +The signature security profile is applicable for scaleable "global" IP telephony; this security profile overcomes the limitations of the simple, baseline security profile of H.235.1. For example, the signature security profile does not depend on the administration of mutual shared secrets of the hops in different domains. It provides tunnelling of H.245 messages for H.245 message integrity and also provisions for non-repudiation of messages. The signature security profile supports hop-by-hop security as well as true end-to-end authentication with simultaneous use of H.235 proxies or intermediate gatekeepers. + +The features provided by these profiles include, for RAS, H.225.0 and H.245 messages: + +- User authentication to a desired entity irrespective of the number of application level hops that the message traverses. + +NOTE 1 – "Hop" is understood here in the sense of a trusted H.235 network element (e.g., GK, GW, MCU, proxy, firewall). Thus, application level hop-by-hop security when used with symmetric techniques does not provide true end-to-end security between terminals. + +- Integrity of all or critical portions (fields) of messages arriving at an entity irrespective of the number of application level hops that the message traverses. Integrity of the message itself using a strongly generated random number is also optional. +- Application level hop-by-hop message authentication, integrity and non-repudiation provide these security services for the entire message. +- Non-repudiation of messages exchanged between two entities irrespective of the number of application level hops that the message traverses can also be provided. Specifically, the non-repudiation is provided for critical portions (fields) of the message. For instance, this may be the case when an EP sends a SETUP message to its GK and the two (EP and GK) are separated by one or more proxies. + +Several attacks are thwarted by providing the above security services in a suitable fashion. These include: + +- Denial-of-service attacks: Rapid checking of digital signatures can prevent such attacks. +- Man-in-the-middle attacks: Application level hop-by-hop message authentication and integrity prevents against such attacks when the man in the middle is between an application level hop, say, a hostile router. When the man in the middle is an application level entity, such attacks are prevented by the presence of end-to-end user authentication and integrity for selected portions of the message. +- Replay attacks: Use of timestamps and sequence numbers prevent such attacks. +- Spoofing: User authentication prevents such attacks. +- Connection hijacking: Use of authentication/integrity for each signalling message prevents such attacks. + +This security profile is applicable in environments with potentially many terminals where password/symmetric key assignment is not feasible, e.g., in large-scale or global-scale scenarios. The signature security profile provides additional security services for non-repudiation using digital signatures and certificates. The digital signatures could use SHA1 or MD5 hashing and provides authentication and/or integrity (see procedures II and III). + +H.323 entities using authentication and integrity, or authentication-only on a hop-by-hop basis, shall use procedure II. H.323 entities using just authentication-only would not implement integrity. The authentication-only H.323 entities shall use procedure III for true end-to-end authentication. + +This Recommendation may apply message integrity protection that spans the entire message. For H.225.0 RAS the integrity protection covers the entire RAS message; for call signalling this covers the entire H.225.0 call signalling message including the Q.931 headers. + +The signature security profile allows to securely tunnel H.245 call control PDUs within H.225.0 facility messages. The H.245 key update and synchronization mechanisms require tunnelling, e.g., useful for very long duration calls. + +NOTE 2 – Key-update for secure G.711 speech coding should occur latest after transmission of $2^{30}$ 64-bit blocks, i.e., more than 12 days of ongoing conversation. + +The vertically shaded area (blue in the electronic copy) in Table 1 represents the scope of the signature security profile. When omitting the integrity indicated by the horizontally shaded area (green in the electronic copy), the authentication-only security profile results. An option within the signature security profile is to choose between RSA-SHA1 or RSA-MD5 digital signatures. The voice encryption security profile of H.235.6 (see 6.1/H.235.6) could be optionally used in conjunction with the signature security profile. + +**Table 1/H.235.2 – Signature security profile** + +| Security services | Call functions | | | | | | RTP | +|-------------------|------------------------|-----|------------------------|-----|-------------------|-----|-----| +| | RAS | | H.225.0 | | H.245 (Note) | | | +| Authentication | SHA1/ | MD5 | SHA1/ | MD5 | SHA1/ | MD5 | | +| | digital signature | | digital signature | | digital signature | | | +| Non-repudiation | SHA1/ | MD5 | SHA1/ | MD5 | SHA1/ | MD5 | | +| | digital signature | | digital signature | | digital signature | | | +| Integrity | SHA1/ | MD5 | SHA1/ | MD5 | SHA1/ | MD5 | | +| | digital signature | | digital signature | | digital signature | | | +| Confidentiality | | | | | | | | +| Access control | | | | | | | | +| Key management | certificate allocation | | certificate allocation | | | | | + +NOTE – Tunnelled H.245 or embedded H.245 inside H.225.0 fast connect. + +NOTE 3 – The signature security profile has to be supported also by other H.235 entities (e.g., gatekeepers, gateways and H.235 proxies). + +NOTE 4 – Available key usage bits in the certificate could also determine the security service provided by a terminal (e.g., non-repudiation asserted). + +For authentication, the user should use a public/private key signature scheme. Such a scheme usually provides for better integrity and non-repudiation of the call. + +This Recommendation does **not** describe procedures for: + +- Registration, certification and certificate allocation from a trust centre and private/public key assignment, directory services, specific CA parameters, certificate revocation, key pair update/recovery and other certificate operational or management procedures such as certificate or public/private key and certificate delivery and installation in terminals. + +Such procedures may happen by means that are not part of this Recommendation. + +The communication entities involved are able to implicitly determine usage of either the H.235.1 baseline security profiles or this signature security profile by evaluating the signalled security object identifiers in the messages (**tokenOID**, and **algorithmOID**; see also clause 20). + +The following procedures are described for use in this profile: + +Procedure II is based on digital signatures using a private/public key pair for providing authentication, integrity and non-repudiation of RAS, Q.931 and H.245 messages. Terminals may use this method if non-repudiation and sophisticated integrity is required. + +Depending on the security policy, authentication may be unilateral or mutual applying the authentication/integrity in the reverse direction as well and providing higher security thereby. The security policy of a terminal may allow "authentication-only" without computing cryptographic integrity (see clause 9). + +Gatekeepers detecting failed authentication and/or failed integrity validation in a RAS/call signalling message received from a terminal/peer gatekeeper respond with a corresponding reject message indicating security failure by setting the reject reason to **securityDenial** or other appropriate security error code according to 11.1/H.235.0. Depending on the ability to recognize an attack, and the most appropriate way to react to it, a gatekeeper receiving a secured **xRQ** with undefined object identifiers (**tokenOID**, **algorithmOID**) should respond with an unsecured **xRJ**, or may discard that message. The encountered security event should be logged. On the other hand, the endpoint shall discard the received unsecured message, time out and may retry once again by considering to choose different OIDs. Likewise, a gatekeeper receiving a secured H.225.0 SETUP message with undefined object identifiers (**tokenOID**, **algorithmOID**) should respond with an unsecured RELEASE COMPLETE and reason set to **securityDenied** or may discard that message. Similarly, the encountered security event should be logged. + +There is implicit H.235 signalling for indicating use of procedure II and the applied security mechanism based upon the value of the object identifiers (see also clause 20) and the message fields filled in. Object identifiers are referenced symbolically through letters (e.g., "A") in this text. + +This profile does not use the H.235 ICV fields; rather cryptographic integrity check values are put into the **signature** field of the **token** in the **cryptoSignedToken**. + +## 6.1 H.323 requirements + +H.323 entities that implement this signature profile are assumed to support the following H.323 features: + +- Fast connect; +- GK-routed model. + +# 7 Digital signatures with public/private key pairs details (procedure II) + +The following procedures shall be adhered to if procedure II is employed for hop-by-hop security: + +- SHA1 or MD5 along with the RSA algorithm should be used to generate the digital signature. Adherence to PKCS #1 and PKCS #7 facilitates interoperability in this regard. + +The **CryptoH323Token** field in each RAS/H.225.0 message shall contain the following fields: + +- **nestedCryptoToken** containing a **CryptoToken** which itself contains the **cryptoSignedToken** containing the following fields: + - **tokenOID** set to: + - "A", indicating that the authentication/integrity computation includes all fields in the H.225.0 RAS or call signalling message (see clause 11); + - "B", indicating that the authentication/integrity computation includes only a subset of fields (see clause 10) in the RAS/H.225.0 message for authentication-only. + - **token** containing the fields: + - **toBeSigned** containing the **EncodedGeneralToken** which actually is a **ClearToken** with the following fields set: + - **tokenOID** set to "S", indicating that **ClearToken** is being used for message authentication/integrity/non-repudiation; + - **timeStamp** contains the time stamp; + - **random** contains a monotonically increasing sequence number; + - **generalID** contains the identifier of the recipient (only in case of unicast messages); + - **sendersID** contains the identifier of the sender; + - **dhkey**, used to pass the Diffie-Hellman parameters as specified in this Recommendation during **Setup to Connect**: + - **halfkey** contains the random public key of one party; + - **modsize** contains the DH-**prime** (see Table 4/H.235.6); + - **generator** contains the DH-group (see Table 4/H.235.6). + +NOTE 1 – When the signature security profile is used without the voice encryption security profile then no Diffie-Hellman parameters should be sent and **dhkey** should be absent; **halfkey**, **modsize** and **generator** may be set to {'0'B,'0'B,'0'B}. + +- **certificate** contains the digital certificate of the sender where type indicates the certificate type ("V" for MD5-RSA certificates or "W" for SHA1-RSA certificates) and **certificate** carries the actual certificate (see clause 14). +- **algorithmOID** set to: + - "V" indicating the use of MD5-RSA signature; + - "W" indicating the use of SHA1-RSA signature. +- **params** set to NULL. +- **signature** containing the signature computed using SHA1 or MD5 RSA on all the fields (if **tokenOID** is "A", see clause 11) or certain critical fields (if **tokenOID** is "B", see clause 10) of the H.225.0 RAS or call signalling message. + +When **tokenOID** "A" is used for protection of tunnelled H323-UU-PDUs including all H.245 message contents, then the signature computation shall be done over the entire H.225.0 call signalling message with all fields according to the procedure described in clause 11. In case **tokenOID** "B" is used, authentication-only of the **CryptoToken** is achieved when applying the procedure III (see clause 10). + +- An entity (which may be one or more application hops away) for whom the signature is meant, verifies the signature. + +NOTE 2 – The recipient is able to detect usage of procedure II by evaluating the **algorithmOID** within the token of the **cryptoSignedToken** (detecting presence of "V" or "W"). + +# 8 Multipoint conferencing procedures + +MCUs shall support secured distribution of certificates upon request from terminals by the tunnelled H.245 **ConferenceRequest** and **ConferenceResponse** commands as described in 8.8.1/H.235.6. This allows terminals to request certificates from other terminals in a multipoint conference environment and thereby obtain certainty about the other participants' identity in the conference. + +**ConferenceRequest** conveys **requestTerminalCertificate** of which the following fields are set: + +- **terminalLabel**: used as addressing means of the remote terminal through the MCU; +- **certSelectionCriteria**: the sender may request certificates only of specific types; +- **sRandom**: a random challenge generated by the requesting sender. + +**ConferenceResponse** conveys **terminalCertificateResponse** of which the following fields are set: + +- **terminalLabel**: allows association of the returned certificate to the terminal. +- **CertificateResponse**: conveys the response from the MCU with fields set to: + - **terminalLabel**: identification of the remote terminal; + - **certificateResponse**: this is actually an octet string ASN.1 encoded from the **EncodedReturnSig** as: + - **generalID**: identification of the destination terminal; + - **responseRandom**: random challenge value generated by the MCU; + - **requestRandom**: **sRandom** played back; + - **certificate**: conveys the returned certificate where **type** indicates the certificate type as OID and **certificate** carries the digital certificate (see clause 14). + +# 9 End-to-end authentication (procedure III) + +Figure 1 shows a scenario with proxies separating GKs and EPs where two different **CryptoTokens** are used for hop-by-hop as well as end-to-end authentication and/or hop-by-hop integrity. The **CryptoToken** for hop-by-hop authentication applies only to the leg between two entities and has to be recomputed on every other leg. On the other hand, the **CryptoToken** for end-to-end authentication is generated just once by the sending endpoint and is not changed in transit by intermediate nodes. Intermediate nodes may validate signatures and certificates conveyed in end-to-end **CryptoTokens** and should forward the **CryptoToken** in transit. + +![Diagram illustrating the simultaneous use of hop-by-hop and end-to-end authentication in H.235.2. The diagram shows a sequence of entities: EP (Endpoint), PXY (Proxy), GK (GK), GK, PXY, and EP. Arrows indicate the flow of messages between them. Above the sequence, 'CryptoToken 1 for hop-by-hop authentication/integrity' is shown with lines pointing to the PXY and GK entities. Below the sequence, 'CryptoToken 2 for end-to-end authentication-only' is shown with a line pointing to the EP entities. The label 'H.235.2_F.1' is in the bottom right corner.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Diagram illustrating the simultaneous use of hop-by-hop and end-to-end authentication in H.235.2. The diagram shows a sequence of entities: EP (Endpoint), PXY (Proxy), GK (GK), GK, PXY, and EP. Arrows indicate the flow of messages between them. Above the sequence, 'CryptoToken 1 for hop-by-hop authentication/integrity' is shown with lines pointing to the PXY and GK entities. Below the sequence, 'CryptoToken 2 for end-to-end authentication-only' is shown with a line pointing to the EP entities. The label 'H.235.2\_F.1' is in the bottom right corner. + +**Figure 1/H.235.2 – Simultaneous use of hop-by-hop security and end-to-end authentication** + +NOTE 1 – The proxy may be a separate network node as shown in Figure 1 or may be collocated with the functionality of an H.323 entity, e.g., as part of the GK. + +NOTE 2 – Depending on the signalled **tokenOID**, the proxy is able to determine whether the received **CryptoToken** is destined for the proxy ("S") or some other recipient ("R"). + +NOTE 3 – Due to the fact that intermediate entities change signalling message contents on every leg, end-to-end integrity is not possible. + +For true end-to-end authentication across H.323 proxies or intermediate network elements, the sending endpoint/terminal shall compute a digital signature as follows. + +The **CryptoH323Token** field in each RAS/H.225.0 message shall contain the following fields: + +- **nestedCryptoToken** containing a **CryptoToken** which itself contains the **cryptoSignedToken** containing the following fields: + - **tokenOID** set to: + - "A", indicating that the hop-by-hop authentication/integrity computation includes all fields in the RAS/H.225.0 message (see clause 11); + - "B", indicating that the authentication computation includes only a subset of fields (see clause 10) in the H.225.0 RAS or call signalling message for authentication only. +- **token** containing the fields: + - **toBeSigned** containing the **ClearToken** field used with the following fields: + - **tokenOID** set to "R" indicating that **ClearToken** is being used for authentication-only/non-repudiation on an end-to-end basis; + +NOTE 4 – Which security service is actually being applied depends also on the key usage bits in the certificate. + +- **random** contains a monotonically increasing sequence number; +- **timeStamp** optionally for enhanced security only when the terminating end entities are time synchronized; +- **generalID** contains the endpoint identifier of the recipient (only in case of unicast). In case of hop-by-hop this is the identifier of the next hop; in case of end-to-end this is the far-end endpoint identifier; +- **sendersID** contains the endpoint sender; +- **certificate** contains the digital certificate of the sender where **type** indicates the certificate type ("V" for MD5-RSA certificates or "W" for SHA1-RSA certificates) and **certificate** carries the actual certificate (see clause 14); + +- **dhkey**, used to pass the Diffie-Hellman parameters as specified in this Recommendation during **Setup** to **Connect**: + - **halfkey** contains the random public key of one party; + - **modsize** contains the DH-prime (see Table 4/H.235.6); + - **generator** contains the DH-group (see Table 4/H.235.6). + +NOTE 5 – When the signature security profile is used without the voice encryption security profile, then no Diffie-Hellman parameters should be sent and **dhkey** should be absent; **halfkey**, **modsize** and **generator** may be set to {'0'B,'0'B,'0'B'}. + +- **algorithmOID** set to: + - "V", indicating the use of MD5-RSA signature; + - "W", indicating the use of SHA1-RSA signature. +- **params** set to NULL. +- **signature** containing the signature computed using SHA1-RSA or MD5-RSA on all the fields (if **tokenOID** is "A") or certain critical fields (if **tokenOID** is "B") of the H.225.0 RAS or call signalling message. + +The proxy may verify any obtained digital signature and/or certificate and may discard the message if not considered appropriate according to the local policy or the proxy shall forward the received **CryptoToken** further on. The proxy has to generate new H.235 signalling information elements for the hop-by-hop security according to procedures II or III. + +The entity terminating the leg (this could be a terminal), should verify received security information in the **CryptoToken** and depending on the presence of end-to-end security elements, may additionally evaluate the end-to-end **CryptoToken** information. The exact verification procedures in a terminal or an intermediate H.323 entity may vary according to local policy. + +# 10 Authentication-only + +Terminals may choose to implement authentication-only (using OID "B"). In this case, the authenticator is computed just over a subset (**ClearToken** inside **CryptoToken**) of the RAS/H.225.0 message. Authentication-only may be useful for true end-to-end authentication (see clause 9). The following fields in the **ClearToken** structure are used as the subset: + +- **tokenOID**: There is a separate token object identifier (tokenOID "B") for authentication-only implementation. +- **random**: The monotonically increasing sequence number. +- **timeStamp**: The time stamp. +- **generalID**: The identifier of the recipient (only in case of unicast messages). In case of hop-by-hop, this is the identifier of the next hop; in case of end-to-end, this is the far-end endpoint identifier. +- **sendersID**: The identifier of the sender. +- **dhkey**: The Diffie-Hellman parameters. This field and subfields are used during **Setup** to **Connect** messages. + +The authenticator is computed over the **ClearToken** inside the **EncodedGeneralToken** (i.e., **ClearToken**) of the **token** of the **cryptoSignedToken**. The digital signature shall be computed over the ASN.1-encoded bitstring of **ClearToken**. Before computing the digital signature, the **tokenOID** in the **ClearToken** shall be set to {0 0}. + +# 11 Authentication and integrity + +For authentication and message integrity over all the ASN.1-coded message fields (using OID "A"), the procedure is the following. + +The sender of a message shall compute the signature as follows: + +- 1) Set the signature value to a specific default pattern with a fixed length (e.g., 1024 bits). This step shall reserve space for the maximum length of a digital signature, which is possible due to a given certificate. The exact bit pattern here does not matter, but a good choice is a unique bit pattern that does not occur in the remaining message. +- 2) ASN.1 encodes the entire message; for RAS this shall include the entire H.225.0 RAS message; for call signalling this shall include the entire H.225.0 call signalling message. +- 3) Locate the default pattern in the encoded message; overwrite the found bit pattern all with zero bits. + +NOTE 1 – This may involve some trial-and-error steps in the rare case when the default pattern occurs more than once in the message. + +- 4) Compute the digital signature upon the ASN.1-encoded message using the method indicated by the **algorithmOID** "V" or "W" (see clause 12). +- 5) Substitute the default pattern in the encoded message with the computed digital signature value. In case the digital signature is shorter than the reserved space, leading zeros shall be put in front of the most significant bits of the signature value. + +The recipient receives the message and then proceeds as follows: + +- 1) ASN.1 decodes the message. +- 2) Extract the received digital signature value and keep it in a local variable SV. +- 3) Search and locate the signature value SV in the received encoded message. + +NOTE 2 – In rare circumstances where the signature value substring might occur several times in the entire message, steps 3-6 have to be iterated successively with a different starting search position. + +- 4) Overwrite the bit pattern in the encoded message all with zeros. +- 5) Compute the digital signature upon the encoded message using the method indicated by the **algorithmOID** "V" or "W" (see clause 12). +- 6) Compare SV with the computed signature value. The message is considered uncorrupted and authentic only if both signature values are equal; in this case, the authentication is successful and the procedure stops. +- 7) Otherwise, repeat steps 3-7 by restoring SV to the previous location and search for another match. If none of the matches yield a correct signature value comparison, then the authentication has failed and the message has been altered (accidentally or intentionally) during transit, or for some other reason. + +# 12 Computation of the digital signature + +The input to the digital signature generation process is an ASN.1-encoded bit string and includes the result of the message digest calculation process and the signer's private key. The details of the digital signature generation depend on the signature algorithm employed; the certificate determines the signature algorithm to be applied; when the key usage extension in the certificate is present, the **digitalSignature** bit must be set for the key to be eligible for signing. The signature value generated by the signer is encoded as a bit string and carried in the **signature** field. + +The method described in [PKCS #1, section E.8.1.1] for computing an RSA-based digital signature with appendix (RSASSA-PKCS1-v1\_5-SIGN) along with the procedures OS2IP, RSASP1, I2OSP and the EMSA-PKCS1-v1\_5-ENCODE method shall be used. + +# 13 Verification of the digital signature + +The input to the signature verification process includes the result of the message digest calculation process and the signer's public key. The recipient may obtain the correct public key for the signer by any means, but the preferred method is from a certificate obtained from the **certificate** field and then validated using the hash of the signer's certificate. The validation of the signer's public key may be based on the certification path processing (RFC 3280). The details of the signature verification depend on the signature algorithm employed. + +The method described in [PKCS #1, section E.8.1.2] for verifying an RSA-based digital signature with appendix (RSASSA-PKCS1-v1\_5-VERIFY) along with the procedures OS2IP, RSAVP1, I2OSP and the EMSA-PKCS1-v1\_5-ENCODE method shall be used. + +# 14 Handling of certificates + +For verification of digital signatures, the receiving entity must have access to the sender's certificate that is signed by a recognized certification authority (CA). There are several possibilities as to how the recipient can access the sender's certificate: + +- The certificate is included in the message exchange as described by procedures II and III; in this case, **certificate** holds the actual certificate and **type** holds OID "V" or OID "W". +- The recipient knows the certificate, possibly stored locally from an earlier exchange. +- Instead of including the certificate itself, the sender provides a URL where the certificate can be found. For this, **certificate** contains the URL and **type** is set to OID "P". +- The recipient obtains the certificate through some other means outside the scope of this Recommendation (e.g., LDAP directory lookup). + +Whenever a digital certificate is conveyed in a message, the receiving entity (gatekeeper, endpoint) shall check the identity of the sender (gatekeeper, endpoint) against the identity of the certificate in order to prevent man-in-the-middle attacks. + +For digitally signed messages sent from the gatekeeper to the endpoint, different possibilities exist for an endpoint to check the gatekeeper identity: + +- If the hostname is available, for example, in the common name attribute of the subject field or of the subjectAltName field in the certificate, the endpoint may check this hostname against the gatekeeper identifier. Additionally, the endpoint may use DNS to query the associated IP address and check it against the gatekeeper's IP address as presented in the gatekeeper's signed response message. +- For example, the gatekeeper identifier may be constructed by the IP address (represented as a 4 byte value in network byte order) concatenated with other identifying information of the gatekeeper identifier, truncated to the maximum length of senders ID field, which carries the gatekeeper's identity. The endpoint may additionally check the IP address belonging to the hostname against the IP address presented in the IP header of the response of the gatekeeper. + +NOTE – This method would not work as expected when Network address translation (NAT) devices are involved. + +- If the hostname is not available in the certificate, the IP address, which would be part of the certificate (*iPAddress subjectAltName*), shall be taken directly to perform the checks stated above. + +Users should carefully examine the certificate presented by the gatekeeper to determine if it meets their expectations. If the endpoint has external information as to the expected identity of the gatekeeper, the hostname check may be omitted. For instance, an endpoint may be connecting to a gatekeeper whose address and hostname are dynamic but the endpoint knows the certificate that the gatekeeper will present. In such cases, it is important to narrow the scope of acceptable certificates as much as possible in order to prevent man-in-the-middle attacks. In special cases, it may be appropriate for the endpoint to simply ignore the gatekeeper's identity, but it must be understood that this leaves the connection open to active attacks. + +If the hostname does not match the identity in the certificate, user oriented endpoints shall either notify the user (endpoints may give the user the opportunity to continue with the connection in any case) or terminate the connection with a bad certificate error. Automated endpoints shall log the error to an appropriate audit log (if available) and should terminate the connection (with a bad certificate error). + +Automated endpoints may provide a configuration setting that disables this check, but shall provide a setting, which enables it. + +Likewise, it is recommended that the gatekeeper perform an identity check for any digitally signed messages sent from the endpoint to the gatekeeper. How exactly the gatekeeper would implement such a checking is considered as a local matter and should be subject to implementation of the gatekeeper's security policy. As an example, one may imagine that the user name conveyed within the certificate may also be part of the H.323 identifier. Further on, the gatekeeper may crosscheck such identity information against locally administered/configured user data if available and may base a policy decision upon that. + +If the gatekeeper has external information as to the expected identity of the endpoint, the hostname check may be omitted. For instance, a gatekeeper may be connecting to an endpoint whose address and hostname are dynamic, but the gatekeeper knows the certificate that the endpoint will present. In such cases, it is important to narrow the scope of acceptable certificates as much as possible in order to prevent man-in-the-middle attacks. In special cases, it may be appropriate for the gatekeeper to simply ignore the endpoint identity, but it must be understood that this leaves the connection open to active attack. + +If the hostname does not match the identity in the certificate, the gatekeeper shall log the error to an appropriate audit log (if available) and should terminate the connection (with a bad certificate error). + +If a subjectAltName extension of type dNSName is present, that shall be used as the identity. Otherwise, the (most specific) Common Name field in the Subject field of the certificate shall be used. Although the use of the Common Name is existing practice, it is deprecated and Certification Authorities are encouraged to use the dNSName instead. + +Matching shall be performed using the matching rules specified by RFC 3280. If more than one identity of a given type is present in the certificate (e.g., more than one dNSName name), a match in any one of the set is considered acceptable. Names may contain the wildcard character \* which is considered to match any single domain name component or component fragment. For example, \*.a.com matches foo.a.com but not bar.foo.a.com. f\*.com matches foo.com but not bar.com. + +Procedures II and III provide means to carry a digital certificate. For efficiency, the digital certificates of the entities need to be transmitted at most only once if they are not already available in the entities through other means outside of this Recommendation. The certificate exchange thus should occur only at the beginning of a communication establishment: for RAS, this occurs either during gatekeeper discovery or, if this phase is omitted, then during gatekeeper registration. Similarly, for fast connect, where the certificate may be included in the initial call signalling messages but can safely be omitted in later call signalling messages. + +For this security profile, an X.509v3 (1997) certificate shall be used. Other certificate formats are for further study. + +# 15 Usage illustration for procedure II + +Consider the case in Figure 2 where each entity has its own private-public key pair/certificate. An entity may also possess multiple key pairs. In the figure, an H.323 proxy separates EP1 from GK1. + +![Diagram illustrating public-key usage in a GK-GK routed model. It shows two groups: the left group contains EP1 (key-pair1), a Proxy (key-pair2), and GK1 (key-pair3); the right group contains GK2 (key-pair4) and EP2 (key-pair5). Solid lines represent H.225.0 RAS messages, and dashed lines represent H.225.0 Call signalling. EP1 sends a dashed line to the Proxy, which sends a solid line to GK1. GK1 sends a solid line to GK2, which sends a dashed line to EP2.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Legend: + +- H.225.0 RAS +- - - - - H.225.0 Call signalling + +H.235.2\_F.2 + +Diagram illustrating public-key usage in a GK-GK routed model. It shows two groups: the left group contains EP1 (key-pair1), a Proxy (key-pair2), and GK1 (key-pair3); the right group contains GK2 (key-pair4) and EP2 (key-pair5). Solid lines represent H.225.0 RAS messages, and dashed lines represent H.225.0 Call signalling. EP1 sends a dashed line to the Proxy, which sends a solid line to GK1. GK1 sends a solid line to GK2, which sends a dashed line to EP2. + +**Figure 2/H.235.2 – Illustrating public-key usage in a GK-GK routed model** + +The H.323 proxy acts in a dual behaviour. On the one hand, the proxy terminates the authentication and integrity on each of its legs. The proxy actively includes the freshly computed authentication/integrity information in the outgoing RAS messages in a similar manner as described in procedure I of H.235.1. On the other hand, the proxy lets the end-to-end security information pass unmodified. The proxy may, however, verify received certificates and/or digital signatures in transit. + +Below, we illustrate the procedure details for RAS, H.225.0 call signalling and H.245 message authentication, integrity and non-repudiation. + +## 15.1 RAS message authentication, integrity and non-repudiation + +Consider the case for a hop-to-hop communication where EP1 wishes to send a RAS message, say an **ARQ** message, to GK1. EP1 generates a timestamp and a sequence number and includes it in the **timeStamp** and **random** fields respectively, along with the proxy's alias in the **generalID** field and the **sendersID** of EP1. These fields are present in the **ClearToken** field of the **EncodedGeneralTokens** present in the **token** of the **cryptoSignedToken** of the **CryptoToken** field of the **cryptoH323Token** of the **ARQ** message. This **cryptoH323Token** is one of at least several tokens in the **cryptoTokens** sequence. The **tokenOID** within the **cryptoSignedToken** is set to "A", indicating that all the fields in the **ARQ** message are signed. The **token** in **cryptoSignedToken** has **algorithmOID** set to "V", indicating the use of MD5-RSA or **algorithmOID** set to "W", indicating the use of SHA1-RSA and **params** set to NULL. EP1 then computes the signature based on the given signature algorithm using its private key. The signature is computed over all the fields of the **ARQ** message when **tokenOID** is set to "A". EP1 includes the computed signature within **signature** in the **token** field of the **cryptoSignedToken** field of the **CryptoToken** present in the **cryptoH323Token** of the **ARQ** message and includes its certificate in the **certificate** field. + +Similarly, for the end-to-end communication through a proxy, EP1 generates another **CryptoToken** containing a digital signature that covers certain critical fields (see clause 9) in the **ClearToken** of the **ARQ** message. The **tokenOID** in the **CryptoSignedToken** is set to "B", indicating authentication-only of that **ClearToken**; sets **tokenOID** in the **ClearToken** to "R", indicating end-to-end authentication, also **timeStamp**, **random**, **sendersID**, **generalID** and in case it is a **SETUP/CONNECT** also **dhkey**, sets in **token** the following fields: **algorithmOID** to "V" or "W", indicating the signature algorithm, **params** to NULL, and **signature** to the computed digital signature over the **ClearToken** fields. The **certificate** carries the digital certificate of EP1. The **ARQ** message is then sent to the proxy. + +Upon receiving the **ARQ** message, the proxy verifies the signature of those tokens that are addressed to it (in this case, say, that with **tokenOID** "A"). This is based on several criteria that include: + +- liveness of the timestamp, uniqueness of the **random**; +- identity of the **generalID** and own identifier; +- access permissions for the **sendersID**; +- matching of signature in **ARQ** message with that computed by GK1; +- verification of Diffie-Hellman parameters, e.g., testing whether the 1024-bit prime and generator are correct. Testing of whether the DH-parameters are secure is a time-consuming process and may be done only when local policy requires it; +- verification of the received certificate. + +If the signature is successfully verified, the proxy computes a new signature to insert (replace) in the **ARQ** message before forwarding it to GK1 as follows. The proxy replaces the **timeStamp**, **random**, **sendersID** and **generalID** fields in the **ClearToken** (**toBeSigned**) field using values relevant to the proxy-GK1 leg. The **timestamp** field contains the current timestamp, the **random** field contains the next monotonically increasing sequence number for the proxy-GK1 leg, the **sendersID** of the proxy and the **generalID** field contains the alias of GK1. The proxy then computes a new signature for this **ARQ** message using its private key and signature algorithm, inserts it in **signature** within **token** and adds its **certificate**. The proxy also includes the received end-to-end **CryptoToken** with its **ClearToken** in the new outgoing message and passes the **ARQ** message on to GK1. The signature, computed by EP1 based on selected fields of the **ARQ** message (**tokenOID** of "B") and which was not meant for the proxy, is also passed untouched in the **ARQ** message to GK1. + +Upon receiving the **ARQ** message, GK1 verifies the signatures, computes a new signature after modifying the **ClearToken** fields in **toBeSigned** suitably, inserts it in the **signature** field, adds its **certificate** and passes the **Setup** message on to EP2. Again, GK1 should forward any end-to-end information received in the separate **CryptoTokens** to the peer GK2 by including that information into a separate **CryptoToken** unmodified. + +## 15.2 RAS authentication only + +Consider the case for a hop-to-hop communication where EP1 wishes to send a RAS message, say an **ARQ** message, to GK1. EP1 generates a timestamp and a sequence number and includes it in the **timeStamp** and **random** fields respectively, along with the proxy's alias in the **generalID** field and the EP's id in the **sendersID**. These fields are present in the **ClearToken** field of **toBeSigned** present in the **token** in **cryptoSignedToken** of the **CryptoToken** field of the **cryptoH323Token** of the **ARQ** message. The **tokenOID** within the **cryptoSignedToken** is set to "B" indicating that only the specified subset fields in the **ClearToken** are signed. The **token** in **cryptoSignedToken** has **algorithmOID** set to "V" indicating use of MD5-RSA or "W" indicating use of the SHA1-RSA signature algorithm and **params** set to NULL. EP1 then computes the signature based on the signature algorithm using its private key. The signature is computed over the specified **ClearToken** + +fields of the **ARQ** message. EP1 includes the computed signature within **signature** in the **token** field of the **cryptoSignedToken** field of the **CryptoToken** present in the **cryptoH323Token** of the **ARQ** message and adds its **certificate**. + +Similarly, EP1 generates another digital signature for end-to-end authentication that covers certain **ClearToken** fields in a separate **CryptoToken** in the **ARQ** message. This digital signature (identified by **tokenOID** of "V" or "W") is included. The **ARQ** message is then sent to the proxy. + +Upon receiving the **ARQ** message, the proxy verifies the signature of those tokens that are addressed to it (in this case, say, that with **tokenOID** "B"). This is based on several criteria that include: + +- liveness of the **timestamp**, uniqueness of the **random**; +- identity of the **generalID** and own identifier; +- access permissions for the **sendersID**; +- matching of signature in **ARQ** message with that computed by GK1; +- verification of the received certificate. + +If the signature is successfully verified, the proxy computes a new signature to insert (replace) in the **ARQ** message before forwarding it to GK1 as follows. The proxy replaces the **timeStamp**, **random**, **sendersID** and **generalID** fields in the **ClearToken** field of **toBeSigned** using values relevant to the proxy-GK1 leg. The **timestamp** field contains the current timestamp, the **random** field contains the next monotonically increasing sequence number for the proxy-GK1 leg, and the **generalID** field contains the alias of GK1. The proxy then computes a new signature for this **ClearToken** using its private key and signature algorithm MD5-RSA or SHA1-RSA (**algorithmOID** ="V" or "W"), inserts it in **signature** within **token** of **cryptoSignedToken**, adds its **certificate** and passes the **ARQ** message on to GK1. The signature computed by EP1 based on selected **ClearToken** fields of the **ARQ** message (**tokenOID** of "B") and which was not meant for the proxy is also passed untouched in the **ARQ** message to GK1. + +Upon receiving the **ARQ** message, GK1 verifies the signature, computes a new signature after modifying the **ClearToken** fields in **toBeSigned** suitably, inserts it in the **signature** field and passes the **Setup** message on to EP2. The end-to-end signature information from EP1 is included untouched in the **Setup** message. + +## 15.3 H.225.0 message authentication, integrity and non-repudiation + +The procedure for H.225.0 messages is identical to that for RAS messages. The only difference is that the set of fields that need to be signed has to be identified for each H.225.0 call signalling message when the **tokenOID** is set to "B". + +## 15.4 H.245 message authentication and integrity + +Consider the case where EP1 wishes to send an H.245 message, say a **TerminalCapabilitySet** message, to EP2. EP1 checks to see if an H.225.0 message needs to be sent to the proxy. If so, then the H.245 message is tunnelled within that H.225.0 message. The fields within the H.225.0 message are set as described earlier for the transmission of a H.225.0 message. Since the H.245 message is tunnelled, the **h323-uu-pdu** in the **h323-UserInfo** message has its fields set as follows: + +- **h323-message-body** field is set to the H.225.0 message type that is being transmitted. +- **h245Tunnelling** set to TRUE. +- **h245Control** contains the H.245 PDU octet string. + +However, if no H.225.0 message transmission is pending, then the H.245 message is tunnelled within an ad hoc H.225.0 **facility** message. The **h323-uu-pdu** in the **h323-UserInfo** message has its fields set as follows: + +- **h323-message-body** field is set to **facility** which contains: + - **reason** set to **undefinedReason**; + - **tokens** and **cryptoTokens** set as for any H.225.0 message. +- **h245Tunnelling** set to TRUE. +- **h245Control** contains the H.245 PDU octet string. + +The **facility** message is then transmitted by EP1 to the proxy. + +In either case (whether a H.225.0 message transmission is pending or an ad hoc H.225.0 **facility** message is used), the proxy verifies the signature which is meant for it (in this case, depicted by **tokenOID** of "A") upon receiving the message. Then, if a H.225.0 message transmission is pending for the proxy-GK1 leg, the H.245 message is tunnelled within that message; otherwise, it is tunnelled within an ad hoc H.225.0 **facility** message. As in the case of transmission of any H.225.0 call signalling message, a new signature is computed for the H.225.0 message prior to its transmission from the proxy to GK1. The signature that was sent from EP1 to the proxy and that was not meant for the proxy is passed untouched by the proxy onto GK1. + +This clause provides a summary of how, and by which means, the signature profile secures the various H.323 signalling messages. + +# 16 H.235 version 1 compatibility + +While these security profiles are developed with H.235 version 2 (ITU-T Rec. H.235v2) in mind, it is also possible to apply the security profiles for H.235 version 1 (ITU-T Rec. H.235v1) with some minor modifications. A recipient is able to detect presence of the sender's H.235 protocol version by evaluating the security profile object identifiers (see clause 20). + +H.235 version 1 (ITU-T Rec. H.235v1) implementations: + +- do not set or evaluate the **sendersID** in the **ClearToken**. + +# 17 Multicast behaviour + +H.225.0 multicast messages such as **GRQ** or **LRQ** shall include a **CryptoToken** according to the procedures II and III where the **generalID** is not set. When such messages are sent unicast, then the message shall include a **CryptoToken**. + +# 18 List of secure signalling messages + +## 18.1 H.225.0 RAS + +| H.225.0 RAS message | H.235 signalling fields | Authentication-only | Authentication and integrity | Non-repudiation | +|---------------------|-------------------------|---------------------|------------------------------|------------------| +| Any | cryptoTokens | Procedure II/III | Procedure II/III | Procedure II/III | + +NOTE – For unicast messages, procedures II or III shall be applied with the security fields in the **CryptoToken** used. + +## 18.2 H.225.0 call signalling + +| H.225.0 call signalling message | H.235 signalling fields | Authentication-only | Authentication and integrity | Non-repudiation | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|------------------------------|------------------| +| Alerting-UUIE,
CallProceeding-UUIE,
Connect-UUIE, Setup-UUIE,
Facility-UUIE,
Progress-UUIE,
Information-UUIE,
ReleaseComplete-UUIE,
Status-UUIE, StatusInquiry-UUIE,
SetupAcknowledge-UUIE, Notify-UUIE | cryptoTokens | Procedure II/III | Procedure II/III | Procedure II/III | + +# 19 Usage of sendersID and generalID + +The **ClearToken** holds **sendersID** and **generalID** fields. When identification information is available, the **sendersID** shall be set to the gatekeeper identifier (GKID) for the gatekeeper-initiated message and to the endpoint identifier (EPID) for the endpoint-initiated messages. When identification information is available, the **generalID** shall be set to the GKID for endpoint-initiated messages and to EPID for the gatekeeper-initiated messages. When the identification information is not available, or in case of broadcast/multicast is ambiguous, the field is missing or shall contain a null string. Table 2 summarizes the situation: + +**Table 2/H.235.2 – Usage of sendersID and GeneralID** + +| Message | sendersID | generalID | +|----------------------------------------------------------------------------------------|-------------------------------------------------|-------------------------------------------------| +| Unicast GRQ | EPID if available, otherwise NULL | GKID | +| Multicast GRQ | EPID if available, otherwise NULL | | +| GCF, GRJ | GKID | EPID if available, otherwise NULL | +| Initial RRQ | | GKID | +| RCF | GKID | EPID | +| RRJ | GKID | | +| URQ, UCF, URJ, BRQ, BCF, BRJ, DRQ, DCF, DRJ, NSM, RIP, SCI, SCR, XRS (EP-to-GK) | EPID | GKID | +| URQ, UCF, URJ, BRQ, BCF, BRJ, DRQ, DCF, DRJ, NSM, RIP, SCI, SCR, XRS (GK-to-EP) | GKID | EPID | +| ARQ, IRQ, RAI | EPID | GKID | +| ACF, ARJ, BCF, LCF, LRJ, IRR, IRQ, RAC, LCF, LRJ, IACK, INAK | GKID | EPID | + +**Table 2/H.235.2 – Usage of sendersID and GeneralID** + +| Message | sendersID | generalID | +|-------------------------------|------------------|------------------| +| Unicast LRQ (EP-to-GK) | EPID | GKID | +| Unicast LRQ (GK-to-GK) | GKID | GKID | +| Multicast LRQ | EPID | | + +NOTE – GKID stands for gatekeeper identifier, EPID stands for endpoint identifier. Blank indicates a missing or null identification string. + +# 20 List of object identifiers + +Table 3 lists all the referenced OIDs (see also [OIW] and [WEBOIDs]). There are object identifiers for H.235v1 and for H.235v2. + +**Table 3/H.235.2 – Object identifiers** + +| Object identifier reference | Object identifier value(s) | Description | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| "A" | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 1}
{itu-t (0) recommendation (0) h (8) 235 version (0) 1 1} | Used in procedure II for the CryptoToken-tokenOID indicating that the signature includes all fields in the H.225.0 RAS or call signalling message (authentication and integrity). | +| "B" | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 2}
{itu-t (0) recommendation (0) h (8) 235 version (0) 2 2}
{itu-t (0) recommendation (0) h (8) 235 version (0) 1 2} | Used in procedure II for the CryptoToken-tokenOID indicating that the signature includes a subset of fields in the RAS/H.225.0 message (ClearToken) for authentication-only terminals without integrity.
Used in H.235.1 procedure IA for the CryptoToken-tokenOID indicating that the hash includes a subset of fields in the RAS/H.225.0 message (ClearToken) for authentication-only terminals without integrity | +| "P" | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 4}
{itu-t (0) recommendation (0) h (8) 235 version (0) 1 4} | Used in procedures II or III to indicate that certificate carries a URL. | +| "R" | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 3}
{itu-t (0) recommendation (0) h (8) 235 version (0) 1 3} | Used in procedure II for the ClearToken-tokenOID indicating that the ClearToken is being used for end-to-end authentication/integrity. | +| "S" | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 7}
{itu-t (0) recommendation (0) h (8) 235 version (0) 1 7} | Used in procedure II this token OID indicates message authentication, integrity and non-repudiation. | + +**Table 3/H.235.2 – Object identifiers** + +| Object identifier reference | Object identifier value(s) | Description | +|------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| "V" | {iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 4} | Used in procedure II or in procedure III as algorithm OID indicating use of MD5 RSA digital signature. | +| "W" | {iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 5} | Used in procedure II or in procedure III as algorithm OID indicating use of SHA1 RSA digital signature. | + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/H/T-REC-H.235.3-200509-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..832c149073914ad550b554bc4fd4eda0f6155741 --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52aa76f48c87dc590271a220d3c2a892ee0ae84e43812b73d03f550a7478db03 +size 181482 diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/H/T-REC-H.235.3-200509-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c31661a1b61fb16e482486d71af77335aeb8d178 --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35e5e54e467f02f79769434e4235490135e8c68ff8a0d80d25e293a99edab6f2 +size 111762 diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/H/T-REC-H.235.3-200509-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1a8476d9356ee4d00612fe2b4a735990a5ad154 --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b6f9127dc9be6293832ff59725672bb2e3e56f81116fb91d50c521e87686b0e +size 151753 diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.235.3-200509-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4b019343ee9abd3afa44deccdf9655c2e8dca8f --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95193810d2b19e1ad79cd2a2bfb931b2b002f2d3c0148e3b4c544fb785fd1ec4 +size 114067 diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/H/T-REC-H.235.3-200509-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15ecd1712fa551acf0842cbadffbeeccce336ccc --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2e29e2536fe8de8ddeb09a1a29731d167eebbbadd53d63d65953140eb0d4de9 +size 16298 diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.235.3-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35d080739dd40d3a774e0eb22c42d16e417ea49a --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37391e71877b06c2c4ce6e4a5a4a2f55300c1d800b0363f7e92dfe256ea6e463 +size 8342 diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.235.3-200509-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5540ac9213c5a5666a4744c0b9102f4c7cc3a8e --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54544cceed297f33c08f1878ab184f625e2b3a39d5a73df28142858dc318ec31 +size 143959 diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.235.3-200509-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c40f3221a1d84bb61f8f4712f9bac17baad9b83 --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bba4966a59acd8ede68cf3506998d82020a801897f010c4e57a1e88762d13e2 +size 13300 diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.235.3-200509-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40dcc7370b1567caf4d3eafda82859d31479d55b --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d961dd841c4a204119d4a6acd011ef1d9b0178c546baff1334540271a96629e +size 92194 diff --git a/marked/H/T-REC-H.235.3-200509-I_PDF-E/raw.md b/marked/H/T-REC-H.235.3-200509-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c44aeccb2d0eb6fb57beac624eba9b9c5b8007ef --- /dev/null +++ b/marked/H/T-REC-H.235.3-200509-I_PDF-E/raw.md @@ -0,0 +1,968 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.235.3** + +(09/2005) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Systems aspects + +--- + +**H.323 security: Hybrid security profile** + +ITU-T Recommendation H.235.3 + +ITU-T + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue, with "ITU" in a larger, bold font above the full name. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation H.235.3** + +## **H.323 security: Hybrid security profile** + +### **Summary** + +The purpose of this Recommendation is to describe an efficient and scalable, PKI-based hybrid security profile for version 2 or higher of ITU-T Rec. H.235.0. The hybrid security profile contained herein takes advantage of the security profiles in ITU-T Recs H.235.1 and H.235.2 by deploying digital signatures from ITU-T Rec. H.235.2 and deploying the baseline security profile from ITU-T Rec. H.235.1. + +In earlier versions of the H.235 sub-series, this profile was contained in Annex F/H.235. Appendices IV, V, VI to H.235.0 show the complete clause, figure, and table mapping between H.235 versions 3 and 4. + +### **Source** + +ITU-T Recommendation H.235.3 was approved on 13 September 2005 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +### **Keywords** + +Authentication, certificate, digital signature, encryption, integrity, key management, multimedia security, security profile. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +### INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2006 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 2.1 Normative references..... | 1 | +| 2.2 Informative references..... | 2 | +| 3 Terms and definitions ..... | 2 | +| 4 Symbols and abbreviations ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Overview ..... | 4 | +| 6.1 H.323 requirements ..... | 6 | +| 6.2 Authentication and integrity ..... | 7 | +| 7 Procedure IV ..... | 7 | +| 8 Security association for concurrent calls ..... | 9 | +| 9 Key update ..... | 10 | +| 10 Usage of elliptic curve techniques..... | 11 | +| 11 Illustration examples..... | 11 | +| 12 Multicast behaviour ..... | 14 | +| 13 List of secure signalling messages..... | 14 | +| 13.1 H.225.0 RAS ..... | 14 | +| 13.2 H.225.0 call signalling (single administrative domain)..... | 14 | +| 13.3 H.225.0 call signalling (multi-administrative domain) ..... | 15 | +| 14 List of object identifiers..... | 15 | +| Appendix I – H.235.3 enabled Gatekeeper Security Processor ..... | 16 | +| I.1 Discovery of a gatekeeper security processor ..... | 18 | +| I.2 Gatekeeper security processor operation..... | 19 | +| I.3 Processor token..... | 20 | +| I.4 GKSP illustration example ..... | 23 | +| I.5 List of object identifiers..... | 28 | + + + +## H.323 security: Hybrid security profile + +# 1 Scope + +The purpose of this Recommendation is to describe an efficient and scalable, PKI-based hybrid security profile for version 2 and higher of ITU-T Rec. H.235.0. The hybrid security profile contained herein takes advantage of the security profiles in ITU-T Recs H.235.1 and H.235.2 by deploying digital signatures from ITU-T Rec. H.235.2 and deploying the baseline security profile from ITU-T Rec. H.235.1. + +# 2 References + +### 2.1 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. + - ITU-T Recommendation H.235, version 1 (1998), *Security and encryption for H-series (H.323 and other H.245-based) multimedia terminals*. + - ITU-T Recommendation H.235, version 2 (2000), *Security and encryption for H-series (H.323 and other H.245-Based) multimedia terminals*. + - ITU-T Recommendation H.235.0 (2005), *H.323 security: Framework for security in H-series (H.323 and other H.245-based) multimedia systems*. + - ITU-T Recommendation H.235.1 (2005), *H.323 security: Baseline security profile*. + - ITU-T Recommendation H.235.2 (2005), *H.323 security: Signature security profile*. + - ITU-T Recommendation H.235.6 (2005), *H.323 security: Voice encryption profile with native H.235/H.245 key management*. + - ITU-T Recommendation H.245 (2005), *Control protocol for multimedia communication*. + - ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*. + - ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*. + - ITU-T Recommendation X.509 (2005) | ISO/IEC 9594-8:2005, *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks*. + - ITU-T Recommendation X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*. +- ISO 7498-2:1989, *Information processing systems – Open Systems Interconnection – Basic Reference Model – Part 2: Security Architecture*. + +- ITU-T Recommendation X.803 (1994) | ISO/IEC 10745:1995, *Information technology – Open Systems Interconnection – Upper layers security model*. +- ITU-T Recommendation X.810 (1995) | ISO/IEC 10181-1:1996, *Information technology – Open Systems Interconnection – Security frameworks for open systems: Overview*. +- ITU-T Recommendation X.811 (1995) | ISO/IEC 10181-2:1996, *Information technology – Open Systems Interconnection – Security frameworks for open systems: Authentication framework*. +- IETF RFC 3280 (2002), *Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile*. + +### 2.2 Informative references + +- [ISO|IEC 14888-3] ISO/IEC 14888-3:1998, *Information technology – Security techniques – Digital signatures with appendix; Part 3: Certificate-based mechanisms*. +- [PKCS] PKCS #1 v2.0: *RSA Cryptography Standard*; RSA Laboratories; October 1, 1998; . +- [PKCS] PKCS #7: *Cryptographic Message Syntax Standard*, An RSA Laboratories Technical Note, version 1.5, Revised November 1, 1993; . +- [RFC1321] IETF RFC 1321 (1992), *The MD5 Message-Digest Algorithm*. + +# 3 Terms and definitions + +For the purposes of this Recommendation, the definitions given in clauses 3/H.323, 3/H.225.0 and 3/H.245 apply. Some of the terms used in this Recommendation are also as defined in ITU-T Recs X.800 | ISO 7498-2, X.803 | ISO/IEC 10745, X.810 | ISO/IEC 10181-1, X.811 | ISO/IEC 10181-2 and H.235.0. + +# 4 Symbols and abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|-------------------------------| +| ALG | Application Level Gateway | +| ASN.1 | Abstract Syntax Notation One | +| BRJ | Bandwidth Reject | +| BRQ | Bandwidth Request | +| CA | Certification Authority | +| CRL | Certificate Revocation List | +| DB | Database | +| DH | Diffie-Hellman | +| DN | Distinguished Name | +| EP | Endpoint | +| GCF | Gatekeeper Confirm | +| GK | Gatekeeper | +| GKID | Gatekeeper Identifier | +| GKSP | Gatekeeper Security Processor | + +| | | +|------|-------------------------------------------------| +| GRJ | Gatekeeper Reject | +| GRQ | Gatekeeper Request | +| HMAC | Hashed Message Authentication Code | +| ICV | Integrity Check Value | +| ID | Identifier | +| IP | Internet Protocol | +| LDAP | Lightweight Directory Access Protocol | +| LRQ | Location Request | +| MCU | Multipoint Control Unit | +| MD5 | Message Digest 5 | +| NAT | Network Address Translation | +| OID | Object Identifier | +| PDU | Protocol Data Unit | +| PKI | Public Key Infrastructure | +| RAS | Registration, Admission and Status | +| RCF | Registration Confirm | +| RRJ | Registration Reject | +| RRQ | Registration Request | +| RSA | Rivest, Shamir and Adleman encryption algorithm | +| RTP | Real-time Transport Protocol | +| SHA | Secure Hash Algorithm | +| UDP | User Datagram Protocol | +| URQ | Unregistration Request | +| VoIP | Voice-over-IP | + +# 5 Conventions + +In this Recommendation the following conventions are used: + +- "shall" indicates a mandatory requirement. +- "should" indicates a suggested but optional course of action. +- "may" indicates an optional course of action rather than a recommendation that something take place. + +The hybrid security profile uses terms and definitions from ITU-T Recs H.235.1 and H.235.2. + +While the message integrity service always provides message authentication, the reverse is not always true. For the authentication-only mode, the integrity assured only spans a certain subset of message fields. This applies to integrity services realized by asymmetric means (e.g., digital signatures). Thus, in practice, a combined authentication and integrity service uses the same key material without introducing a security weakness. + +This security profile is applicable in environments with potentially many terminals, where static password/symmetric key assignment is not feasible, e.g., in large-scale or global-scale scenarios. + +Instead, this security profile assumes availability of a public-key infrastructure with assigned certificates and private/public-keys, directories, etc. In addition, this security profile deploys symmetric crypto techniques where applicable. + +This security profile introduces the terms "first" message and "last" message sent. Security protection of the first message (and probably also for the last message) is different from security protection of the remaining other messages. + +The "first message" sent is understood as a message that flows between two H.323 entities and establishes a security context. It makes symmetric key material available to both entities and, for example, marks the beginning of a call. For H.225.0 RAS, the first message is the RRQ and the related response message. For H.225.0 call signalling using fast start, the first message is SETUP and CONNECT. + +The "last message" terminates the established security context. The established key material shall be destroyed. For H.225.0 RAS, the last message is the URQ and related response message, while for H.225.0 call signalling the last message is RELEASE-COMPLETE. + +# 6 Overview + +This Recommendation describes an efficient and scalable, PKI-based hybrid security profile deploying digital signatures from H.235.2 and deploying the baseline security profile from H.235.1. This Recommendation is suggested as an option. H.323 security entities (terminals, gatekeepers, gateways, MCUs, etc.) may implement this hybrid security profile for improved security or whenever required. + +The notion of "hybrid" in this text shall mean that security procedures from the signature profile in ITU-T Rec. H.235.2 are actually applied in a lightweight sense and the digital signatures still conform to the RSA procedures. However, digital signatures are deployed only where absolutely necessary while highly efficient symmetric security techniques from the baseline security profile in ITU-T Rec. H.235.1 are used otherwise. + +The hybrid security profile is applicable for scaleable "global" IP telephony. This security profile overcomes the limitations of the simple, baseline security profile of H.235.1 when strictly applying it. Furthermore, this security profile overcomes certain drawbacks of H.235.2, such as the need for higher bandwidth and increased performance needs for processing, when strictly applying it. For example, the hybrid security profile does not depend on the (static) administration of mutual shared secrets of the hops in different domains. Thus, users can more easily choose their VoIP provider. This security profile thus supports a certain kind of user mobility as well. It applies asymmetric cryptography with signatures and certificates only where necessary and otherwise uses simpler and more efficient symmetric techniques. It provides tunnelling of H.245 messages for H.245 message integrity and also implements some provisions for non-repudiation of messages. + +The hybrid security profile mandates the GK-routed model and is based upon the H.245 tunnelling techniques. Support for non GK-routed models is for further study. + +The features provided by this profile include: + +For RAS, H.225.0 and H.245 messages: + +- User authentication to a desired entity irrespective of the number of application level hops that the message traverses. + +NOTE 1 – Hop is understood here in the sense of a trusted H.235 network element (e.g., GK, GW, MCU, proxy, or firewall). Thus, application level hop-by-hop security when used with symmetric techniques does not provide true end-to-end security between terminals. + +- Integrity of all or critical portions (fields) of messages arriving at an entity irrespective of the number of application-level hops that the message traverses. Integrity of the message itself using a strongly generated random number is also optional. +- Application-level hop-by-hop message authentication, integrity and (some) non-repudiation provide these security services for the entire message. +- Using the available public-key infrastructure, users can choose their service provider. Key-management for session key distribution is well integrated in the hybrid security profile. + +Suitable provision of the above-described security services thwarts several types of attacks, including: + +- *Man-in-the-middle attacks*: Application-level hop-by-hop message authentication and integrity prevents against such attacks when the man-in-the-middle is in an application-level hop, say, a hostile router. +- *Replay attacks*: Use of timestamps and sequence numbers prevent such attacks. +- *Spoofing*: User authentication prevents such attacks. +- *Connection hijacking*: Use of authentication/integrity for each signalling message prevents such attacks. + +This security profile assumes the GK-routed call model, where the fast connect call signalling method is applied. H.245 call control messages are securely tunnelled in H.225.0 call signalling messages and inherit thereby the H.225.0 security protection scheme. + +The signature security profile allows to securely tunnel H.245 call control PDUs within H.225.0 facility messages. The H.245 key update and synchronization mechanisms require tunnelling for key-update FACILITY message to be signalled and is useful, for example, for very long duration calls. + +The diagonally shaded area in Table 1 represents the security mechanisms that are used by the hybrid security profile. + +NOTE 2 – RSA certificates with MD5 ([RFC1321]) hashing are not part of this security profile. + +The voice encryption security profile of H.235.6 (see 6.1/H.235.6) could be optionally used in conjunction with the hybrid security profile. Its use is negotiated as part of the call set-up signalling. + +**Table 1/H.235.3 – Overview of the hybrid security profile** + +| Security services | Call functions | | | | +|------------------------|-------------------------------------------|-------------------------------------------|------------------------------|-----| +| | RAS | H.225.0 | H.245 (Note 3) | RTP | +| Authentication | RSA digital signature (SHA1) | RSA digital signature (SHA1) | RSA digital signature (SHA1) | | +| | HMAC-SHA1-96 | HMAC-SHA1-96 | HMAC-SHA1-96 | | +| Non-repudiation | (possible only on first message) | (possible only on first message) | | | +| Integrity | RSA digital signature (SHA1) | RSA digital signature (SHA1) | RSA digital signature (SHA1) | | +| | HMAC-SHA1-96 | HMAC-SHA1-96 | HMAC-SHA1-96 | | +| Confidentiality | | | | | +| Access control | | | | | +| Key management | certificate allocation | certificate allocation | | | +| | authenticated Diffie-Hellman key-exchange | authenticated Diffie-Hellman key-exchange | | | + +NOTE 1 – The hybrid security profile has to be also supported by other H.235 entities (e.g., gatekeepers, gateways and H.235 proxies). + +NOTE 2 – Available key usage bits in the certificate could also determine the security service provided by a terminal (e.g., non-repudiation asserted). + +NOTE 3 – Tunnelled H.245 or embedded H.245 inside H.225.0 fast connect. + +This Recommendation may apply message integrity protection that spans the entire message. For H.225.0 RAS the integrity protection covers the entire RAS message; for call signalling this covers the entire H.225.0 call signalling message including the Q.931 headers. + +For authentication, the user should use a public/private key signature scheme. Such a scheme usually provides for better integrity. + +This Recommendation does not describe procedures for registration, certification and certificate allocation from a trust centre and private/public key assignment, directory services, specific CA parameters, certificate revocation, key pair update/recovery and other certificate operational or management procedures such as certificate or public/private key and certificate delivery and installation in terminals. Such procedures may happen by means that are not part of this Recommendation. + +The communication entities involved are able to implicitly determine usage of either the H.235.1 baseline security profiles, H.235.2 signature profile, or this hybrid security profile by evaluating the signalled security object identifiers in the messages (**tokenOID**, and **algorithmOID**; see also clause 10/H.235.2). + +### 6.1 H.323 requirements + +H.323 entities that implement this hybrid security profile are assumed to support the following H.323 features: + +- Fast connect; +- H.245 tunnelling; and +- GK-routed model. + +### 6.2 Authentication and integrity + +This Recommendation uses the following terms for provisioning the security services. + +**Authentication and integrity:** This is a combined security service that supports message integrity in conjunction with user authentication. The user authenticates when either correctly digitally signing some piece of data with the private key or when correctly applying a related, shared secret. In addition to that, the message is protected against tampering. Both security services are provided by the same security mechanism. Combined authentication and integrity is possible only on a hop-to-hop basis. + +NOTE – When digital signatures are applied, a non-repudiation security service may be supported. This also depends on the settings of the key usage bits of the signing key in the certificate (see also RFC 3280). + +The following procedures are described for use in this profile. + +Procedure IV is based on digital signatures using a private/public key pair and deploying symmetric crypto techniques for providing authentication and integrity of RAS, Q.931 and H.245 messages. Terminals may use this method if efficient, scalable security is required. + +Depending on the security policy, authentication may be unilateral or mutual (i.e., applying the authentication/integrity in the reverse direction as well, thereby providing higher security). The preferred security mode is to have mutual authentication. + +Gatekeepers detecting failed authentication and/or failed integrity validation in a RAS/call signalling message received from a terminal/peer gatekeeper will respond with a corresponding reject message indicating security failure. This is done by setting the reject reason to **securityDenial**, or other appropriate security error code according to 11.1/H.235.0. Depending on the ability to recognize an attack, and the most appropriate way to react to it, a gatekeeper receiving a secured **xRQ** with undefined object identifiers (**tokenOID**, **algorithmOID**) should respond with an unsecured **xRJ** and reject reason set to **securityDenial** or may discard that message. The endpoint shall discard the received unsecured message, time out and may retry once again by considering to choose different OIDs. Likewise, a gatekeeper receiving a secured H.225.0 call signalling SETUP message with undefined object identifiers (**tokenOID**, **algorithmOID**) should respond with an unsecured RELEASE COMPLETE and reject reason set to **securityDenied**, or it may discard that message whereas a gatekeeper receiving a secured H.225.0 FACILITY with undefined object identifiers (**tokenOID**, **algorithmOID**) should respond with an unsecured FACILITY and reason set to **undefinedReason**, or it may discard that message. Similarly, the encountered security event should be logged. As part of the returned response, the sender may provide a list of acceptable certificates in separate tokens, in order to facilitate selection of an appropriate one by the recipient. + +There is implicit H.235 signalling for indicating use of procedure IV and the applied security mechanism based upon the value of the object identifiers (see also clause 13) and the message fields filled-in. In this Recommendation, object identifiers are referenced symbolically through letters (e.g., "A"). + +This profile does not use the H.235 ICV fields. Rather, cryptographic integrity check values are put into the **signature** field of the **token** in the **cryptoSignedToken** when referring to H.235.2, or the integrity check values are put in the hash fields of the **CryptoToken** when referring to H.235.1. + +# 7 Procedure IV + +The following procedures shall be adhered to if procedure IV is employed for hop-by-hop security. This procedure unites procedure I of clause 7/H.235.1 and procedure II of clause 7/H.235.2. + +For the first message, including corresponding response sent in each direction, H.235.2 procedure II (hop-by-hop authentication and integrity, see clause 7/H.235.2) shall be used with the following settings: + +- OID "A1" instead of OID "A" and OID "S1" instead of OID "S". Use of these OIDs allows identifying the hybrid security profile. +- **algorithmOID** in **tokenOID** shall be set to "W" indicating use of RSA-SHA1 signature. +- **signature** shall contain an ASN.1 encoded RSA signature (see clause 12/H.235.2). +- **certificate** should contain the sender's user certificate if not available otherwise to the receiver; **type** shall hold OID "W" indicating an included RSA-SHA1 certificate or OID "P" (see clause 20/H.235.2) indicating that **certificate** holds an URL. + +In a single administrative domain scenario, "the first message/response" is defined to equal the initial H.225.0 RAS message/response; this is usually either GRQ/GCF or RRQ/RCF. In a multi-administrative domain scenario, the first message/response within each domain is defined as above; the first message between the domains is defined as SETUP. + +Whenever a digital certificate is conveyed in a message, the receiving entity shall check the identity of the sender against the identity of the certificate according to the procedure in clause 14/H.235.2 in order to prevent man-in-the-middle attacks. + +Sender and recipient exchange and compute an authenticated Diffie-Hellman secret bit string. Table 4/H.235.6 provides an example of Diffie-Hellman group parameters and recommends taking the 1024-bit prime whenever possible, for security reasons. The Diffie-Hellman secret shall be computed for each leg, regardless of whether the voice encryption profile is deployed or not. + +From the common bit string that both parties compute, both parties derive a 160-bit secret by taking the least significant 160 bits. The resulting 160-bit secret acts as the password/shared secret that is used in ITU-T Rec. H.235.1. + +In a scenario with gatekeepers in distinct administrative domains, sender and receiver shall use two tokens in each direction for H.225.0 call signalling: + +- One **ClearToken** inside **CryptoToken**, which is used to compute the media key that is shared among the terminals (see 8.5/H.235.6). This is only necessary if voice encryption is to be deployed. +- A separate **ClearToken** is used to compute a link key that is shared among the sender and receiver entities for protection of the signalling link. This link key replaces the shared password among the gatekeepers in H.235.1. The **tokenOID** of that **ClearToken** shall be set to "Q", indicating use of Diffie-Hellman and hybrid security profile. Computation of the link key proceeds in the same manner as computation of the media key (see 8.5/H.235.6). + +NOTE 1 – For direct-routed environments, sender/receiver entities and terminals correspond. For GK-routed environments, the link key is shared hop-by-hop between each pair of peer gatekeepers, while the media key is shared on an end-to-end basis. + +In GK-routed environments, the GK shall forward the received Diffie-Hellman token from the endpoint to the next hop. + +For all but the very first message/response sent in each direction, H.235.1 procedure I (see clause 7/H.235.1) shall be used. This applies also in a scenario where multiple gatekeepers are located within an administrative domain. In this case, there is no need for asymmetric key management; instead, H.235.1 is sufficient. + +This Recommendation may be used with H.235 version 1 systems when taking care of restricted use of sendersID and generalID, as described in clause 19/H.235.2. + +It is anticipated that a gatekeeper should receive only a single **RRQ** including a DH-token with a digital signature from a particular fixed endpoint. However, lost or delayed **RCF/RRJ** messages may lead to retransmission using another signed **RRQ**. + +In the case of the untimely arrival of the corresponding registration response, at the endpoint, the endpoint may attempt another try. For this, the endpoint shall use the most recent DH token but use a new sequence number and a new timestamp. + +For a particular fixed endpoint, the gatekeeper shall use the most recently received signed **RRQ** message and derive the shared secret from that DH-token, regardless of whether or not the GK already has a shared secret available. Thus, the GK shall overwrite any existing shared secret with the newly derived secret. The GK shall respond with a signed **RCF** that holds the response DH-token. Preferably, the response DH token should be generated anew. + +NOTE 2 – The recommended and preferred method for key update is by using the FACILITY message as defined in clause 9. However, it is recognized that key update may be achieved using another additive signed **RRQ** with a new DH-token. + +NOTE 3 – A gatekeeper in possession of a shared secret shall respond to an HMAC-protected **RRQ** (according to ITU-T Rec. H.235.1) with an HMAC-protected response message. + +# 8 Security association for concurrent calls + +An optimization is provided for the case that a fixed pair of entities would process several independent calls in parallel using a single call signalling channel. Instead of establishing several link keys with Diffie-Hellman for each call, a security association is defined which spans multiple concurrent calls. + +More precisely, the security association spans all calls between a fixed pair of entities as long as the call signalling channel is alive. Entities use the **multipleCalls** flag within Setup to indicate the capability of signalling multiple calls over a single call signalling connection (see 7.3/H.323). + +If the single call signalling connection is used, then only one common link key needs to be established, see Figure 1. + +On the other hand, if the **multipleCalls** flag within SETUP is not set, then a link key shall be individually computed anew for each call. + +![Sequence diagram illustrating the security association for concurrent calls between entities A and B. The diagram shows two calls, Call 1 and Call 2, sharing a common security association. Both entities initialize their session key K_AB. Call 1 involves a SETUP (1) from A to B, followed by a CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT (1) from B to A. Call 2 involves a SETUP (2) from A to B, followed by a CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT (2) from B to A. Both calls conclude with a RELEASE COMPLETE message (2 and 1 respectively) from B to A. The security association is maintained throughout both calls.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +sequenceDiagram + participant A + participant B + Note left of A: K_AB := + Note right of B: K_AB := + Note left of A: Security association + Note right of A: Call 1 + Note right of B: Call 2 + + A->>B: SETUP (1): HMAC-SHA1(K_AB) + B-->>A: CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT (1): HMAC-SHA1(K_AB) + A->>B: SETUP (2): HMAC-SHA1(K_AB) + B-->>A: CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT (2): HMAC-SHA1(K_AB) + Note right of A: .... + B-->>A: RELEASE COMPLETE (2): HMAC-SHA1(K_AB) + Note right of A: .... + B-->>A: RELEASE COMPLETE (1): HMAC-SHA1(K_AB) + +``` + +H.235.3\_F01 + +Sequence diagram illustrating the security association for concurrent calls between entities A and B. The diagram shows two calls, Call 1 and Call 2, sharing a common security association. Both entities initialize their session key K\_AB. Call 1 involves a SETUP (1) from A to B, followed by a CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT (1) from B to A. Call 2 involves a SETUP (2) from A to B, followed by a CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT (2) from B to A. Both calls conclude with a RELEASE COMPLETE message (2 and 1 respectively) from B to A. The security association is maintained throughout both calls. + +**Figure 1/H.235.3 – Security association for concurrent calls** + +## 9 Key update + +An optional key update procedure allows either communication entity (GK or terminal) to refresh the currently-used session key with a new one. Such a key update should be initiated by whichever entity feels a need for it. A key update may be motivated by a compromised session key, the perception that the session key has or will become insecure, or other security policy criteria. These aspects are all outside the scope of this Recommendation. + +The initiator invokes the key update using the FACILITY message. The FACILITY message for key update conveys a new Diffie-Hellman token, an optional digital certificate, and a digital signature of the initiator. Upon reception of the FACILITY message, the recipient replies with a similar FACILITY message conveying his Diffie-Hellman token, an optional digital certificate, and a digital signature of the recipient. Upon completion of the key update procedure, initiator and responder shall use the computed new link key. + +- **tokenOID** of the **ClearToken** within FACILITY shall be set to "Q" indicating use of Diffie-Hellman and hybrid security profile. Computation of the link key proceeds in the same manner as computation of the media session key (see 8.5/H.235.6). + +The FACILITY message for key update purposes shall be protected according to H.235.2 procedure II. Any other FACILITY message without conveyed Diffie-Hellman token shall not be deployed for key update purposes and shall be protected according to clause 7/H.235.1 procedure I. + +# **10 Usage of elliptic curve techniques** + +This is for further study. + +# **11 Illustration examples** + +The flow diagrams in Figures 2 and 3 illustrate usage of this Recommendation in a basic message flow. Note that the diagrams do not show the complete message flow and that several messages are omitted for simplicity. Messages highlighted in light gray relate to the signature profile H.235.2, while dark gray messages relate to the baseline profile H.235.1. The figures emphasize the (most important) security parts of each message (H.235 CryptoTokens, Tokens) while omitting details. + +The flow diagram in Figure 2 illustrates the basic message flow in a scenario with one gatekeeper within a single administrative domain. Assuming that the gatekeeper certificate is known to all the terminals involved, and that the terminals know the gatekeeper certificate likewise, there is no need to transmit the certificates in-band during the registration procedure. + +![Sequence diagram showing call signaling between Terminal A, GK B, and Terminal C within a Domain. The sequence includes RRQ, RCF, key updates (K_AB, K_BC), ARQ, SETUP, CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT, FACILITY (for key updates), and RELEASE COMPLETE messages.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant TA as Terminal A + participant GB as GK B + participant TC as Terminal C + Note over TA, GB, TC: Domain + + TA->>GB: RRQ: DH_A, (Cert_A), Sig_A + TC->>GB: RRQ: DH_C, (Cert_C), Sig_C + GB->>TA: RCF: DH_B, (Cert_B), Sig_B + GB->>TC: RCF: DH_B, (Cert_B), Sig_B + Note over TA, GB: K_AB := + Note over GB, TC: K_BC := + TA->>GB: ARQ: HMAC-SHA1(K_AB) + GB->>TA: .... + TA->>GB: SETUP: HMAC-SHA1(K_AB) + GB->>TC: SETUP: HMAC-SHA1(K_BC) + TC->>GB: CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT: HMAC-SHA1(K_AB) + GB->>TA: FACILITY: DH_A, (Cert_A), Sig_A + GB->>TC: FACILITY: HMAC-SHA1(K_BC) + TA->>GB: FACILITY: DH_B, (Cert_B), Sig_B + GB->>TA: .... + Note over TA, GB: K'_AB := + TA->>GB: RELEASE COMPLETE: HMAC-SHA1(K'_AB) + GB->>TC: RELEASE COMPLETE: HMAC-SHA1(K_BC) + +``` + +H.235.3\_F02 + +Sequence diagram showing call signaling between Terminal A, GK B, and Terminal C within a Domain. The sequence includes RRQ, RCF, key updates (K\_AB, K\_BC), ARQ, SETUP, CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT, FACILITY (for key updates), and RELEASE COMPLETE messages. + +| | | | | +|-----------------|------------------------------------|-------|--------------------| +| Cert | User certificate | K, K' | symmetric link key | +| DH A | Diffie-Hellman Token $g^a \bmod p$ | Sig | digital signature | +| DH B | Diffie-Hellman Token $g^b \bmod p$ | | | +| EP | Endpoint (Terminal) | | | +| GK | Gatekeeper | | | + +**Figure 2/H.235.3 – Flow diagram in a single administrative domain** + +NOTE 1 – Figures 2 and 3 also cover the fast start procedure when the call signalling messages SETUP and CALL PROCEEDING/PROGRESS/ALERTING/CONNECT include the faststart token (see 8.1.7/H.323). Otherwise, non-faststart mode is assumed according to 7.3.1/H.323. Figure 2 shows also the key update procedure between Terminal A and Gatekeeper B using FACILITY. + +Figure 3 shows an example message flow in a scenario with different administrative domains. While the hybrid security profile is applied within each domain between terminal and gatekeeper as illustrated in Figure 2, the hybrid security profile may be applied also between both domains during the call establishment phase. + +NOTE 2 – Figure 3 omits any communication among border elements (BE) and any communication between GK-to-BE. Figure 3 also shows the key update procedure between both domains using FACILITY. + +![Sequence diagram illustrating a multi-administrative domain call establishment between Domain 1 (Terminal A, GK/BE B) and Domain 2 (GK/BE C, Terminal D).](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +The diagram illustrates a sequence of messages for call establishment across two administrative domains, Domain 1 and Domain 2. + +- Domain 1:** Terminal A sends an **RRQ** (DHA, (CertA), SigA) to GK/BE B. GK/BE B responds with an **RCF** (DHB, (CertB), SigB). Both parties derive a shared key $K_{AB} :=$ . Terminal A then sends an **ARQ** (HMAC-SHA1( $K_{AB}$ )). After some internal processing (indicated by '....'), Terminal A sends a **SETUP** (HMAC-SHA1( $K_{AB}$ )). +- Inter-domain:** GK/BE B forwards the **SETUP** message to GK/BE C. GK/BE C responds with an **RCF** (DHB, (CertB), SigB). GK/BE C then sends a **CALL-PROCEEDING** (DHC, (CertC), SigC) back to GK/BE B. Both GK/BE B and GK/BE C derive a shared key $K_{BC} :=$ . GK/BE B sends a **FACILITY** (DHB, (CertB), SigB) to GK/BE C, which responds with a **FACILITY** (DHC, (CertC), SigC). Both parties then update their key to $K'_{BC} :=$ . After more internal processing (indicated by '....'), GK/BE B sends a **RELEASE COMPLETE** (HMAC-SHA1( $K'_{BC}$ )) to Terminal A. +- Domain 2:** Terminal D sends an **RRQ** (DHD, (CertD), SigD) to GK/BE C. GK/BE C responds with an **RCF** (DHC, (CertC), SigC). Both parties derive a shared key $K_{CD} :=$ . GK/BE C sends a **SETUP** (HMAC-SHA1( $K_{CD}$ )) to Terminal D. Terminal D responds with a **CONNECT** (HMAC-SHA1( $K_{CD}$ )). After internal processing (indicated by '....'), Terminal D sends a **RELEASE COMPLETE** (HMAC-SHA1( $K_{CD}$ )) to GK/BE C, which then forwards it to GK/BE B. + +Sequence diagram illustrating a multi-administrative domain call establishment between Domain 1 (Terminal A, GK/BE B) and Domain 2 (GK/BE C, Terminal D). + +H.235.3\_F03 + +Figure 3/H.235.3 – Flow diagram in a multi-administrative domain + +# 12 Multicast behaviour + +H.225.0 multicast messages such as **GRQ** or **LRQ** shall include a **CryptoToken** according to procedure II where the **generalID** is not set. When such messages are sent unicast, then the message shall include a **CryptoToken** with the **generalID** set. + +# 13 List of secure signalling messages + +Procedure IV deploys procedure I of H.235.1 or procedure II of H.235.2, depending on the scenario and on the actual message, as indicated below. + +## 13.1 H.225.0 RAS + +| H.225.0 RAS message | H.235 signalling fields | Authentication and integrity | Non-repudiation | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------|-----------------| +| GatekeeperRequest, GatekeeperConfirm, GatekeeperReject if GK discovery is applied
RegistrationRequest, RegistrationConfirm, RegistrationReject if GK discovery is not applied | CryptoToken, ClearToken | Procedure II | Procedure II | +| Any other RAS message (Note 2) | CryptoToken | Procedure I | | +| NOTE 1 – For unicast messages, procedure II shall be applied with the security fields in the CryptoToken used. | | | | +| NOTE 2 – GK discovery and multicast messages are not sent. | | | | + +### 13.2 H.225.0 call signalling (single administrative domain) + +| H.225.0 call signalling message | H.235 signalling fields | Authentication and integrity | Non-repudiation | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------|-----------------| +| Setup-UUIE, Connect-UUIE (Note 1), Facility-UUIE (Note 2), Alerting-UUIE, CallProceeding-UUIE, Facility-UUIE, Progress-UUIE, Information-UUIE, ReleaseComplete-UUIE, Status-UUIE, StatusInquiry-UUIE, SetupAcknowledge-UUIE, Notify-UUIE | CryptoToken, ClearToken | Procedure I | | +| Facility-UUIE (Note 3) | CryptoToken | Procedure II | Procedure II | +| NOTE 1 – Assuming that either message is the first in each direction. | | | | +| NOTE 2 – Not used for key update. | | | | +| NOTE 3 – Used for key update. | | | | + +### 13.3 H.225.0 call signalling (multi-administrative domain) + +| H.225.0 call signalling message | H.235 signalling fields | Authentication and integrity | Non-repudiation | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------|-----------------| +| Setup-UUIE, Connect-UUIE (Note 1), Alerting-UUIE (Note 2), CallProceeding-UUIE, Facility-UUIE (Note 3), Progress-UUIE, Information-UUIE, ReleaseComplete-UUIE | CryptoToken, ClearToken | Procedure II | Procedure II | +| Alerting-UUIE (Note 4), CallProceeding-UUIE, Facility-UUIE (Note 5), Progress-UUIE, Information-UUIE, ReleaseComplete-UUIE, Status-UUIE, StatusInquiry-UUIE, SetupAcknowledge-UUIE, Notify-UUIE | CryptoToken, ClearToken | Procedure I | Procedure I | + +NOTE 1 – Assuming that either message is the first in each direction. +NOTE 2 – Any of those messages occurs as first message in either direction. +NOTE 3 – Used for key update. +NOTE 4 – Any of those messages does not occur as the first message in either direction. +NOTE 5 – Not used for key update. + +# 14 List of object identifiers + +Table 2 lists all the referenced OIDs. + +**Table 2/H.235.3 – Object identifiers** + +| Object identifier reference | Object identifier value(s) | Description | +|-----------------------------|-----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| "A1" | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 20} | Used as replacement for OID "A" in procedure II of ITU-T Rec. H.235.2 for the CryptoToken-tokenOID indicating that the RSA signature/hash includes all fields in the H.225.0 RAS or call signalling message (authentication and integrity). | +| "S1" | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 21} | Used as replacement for OID "S" in procedure II of ITU-T Rec. H.235.2 for the ClearToken-tokenOID indicating that the ClearToken is being used for message authentication and integrity. This OID in the end-to-end CryptoToken implicitly indicates also use of DH during fast start. | +| "Q" | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 22} | Used in procedure IV indicating that the ClearToken on the hop-by-hop link carries a Diffie-Hellman token. | +| "W" | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 23} | Used in procedure IV as algorithm OID indicating use of an RSA SHA1-based digital signature. | + +## Appendix I + +## H.235.3 enabled Gatekeeper Security Processor + +This informative appendix describes an implementation example for an H.235.3-enabled Gatekeeper Security Processor (GKSP) in conjunction with a gatekeeper. The purpose of the GKSP is to off-load certain H.235.3-specific security tasks such as execution of performance-expensive Diffie-Hellman operations, digital signature computations and verifications and X.509 certificate processing from a monolithic GK into a new and separate Gatekeeper Security Processor (GKSP) functional entity. There is at least one GKSP entity for each GK, yet one GK may serve also multiple GKSPs to increase scalability in the number of served endpoints and improve robustness of the entire system. + +Figure I.1 shows such a decomposed GK architecture where the GKSP holds the H.235.3 security functions. + +![Diagram of Gatekeeper Security Processor architecture showing Security Domains A, B, and C, endpoints (EP1, EP2, EPn), the GKSP, the Gatekeeper (GK), and the User DB.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +The diagram illustrates the architecture of an H.235.3-enabled Gatekeeper Security Processor (GKSP) across three security domains: Security Domain A, Security Domain B, and Security Domain C. + +- Security Domain A:** Contains multiple endpoints (EP1, EP2, EPn). Each endpoint is associated with a User/EP certificate and a User/EP private key. Arrows indicate bidirectional communication between these endpoints and the GKSP, labeled "H.225.0 w. H.235.3". +- Security Domain B:** Contains a Gatekeeper (GK) and a User DB. The GK is associated with a User/EP credential, a GK certificate, and a GK private key. The User DB is connected to the GK via an LDAP connection. The GKSP communicates with the GK via two arrows labeled "H.225.0 with H.235.3/H.235.1 and processor token". +- Security Domain C:** Contains another GKSP entity. +- GKSP (Gatekeeper Security Processor):** A central component that handles security functions for endpoints in Security Domain A. It includes internal modules for "DH processing", "Digital signature processing", and "X.509 cert processing". It also has a "NAT/FW" (Network Address Translation/Firewall) module. The GKSP is associated with a GKSP certificate and a GKSP private key. +- Connections:** + - Endpoints in Security Domain A connect to the GKSP with "H.225.0 w. H.235.3". + - The GKSP connects to the GK in Security Domain B with "H.225.0 with H.235.3/H.235.1 and processor token". + - The GK connects back to the GKSP with "H.225.0 with H.235.3/H.235.1 and processor token". + - The GK connects to the User DB via LDAP. + - The GKSP in Security Domain C is shown as a separate entity. +- Legend:** + - Dynamic shared secret (H.235.3):** Indicated by a bracket under the connections between endpoints and the GKSP. + - Security trust association:** Indicated by a bracket under the connections between the GKSP and the GK. It includes "Static shared secret (H.235.1)" and "Dynamic Shared secret (H.235.3)". + +Diagram of Gatekeeper Security Processor architecture showing Security Domains A, B, and C, endpoints (EP1, EP2, EPn), the GKSP, the Gatekeeper (GK), and the User DB. + +Figure I.1/H.235.3 – Gatekeeper Security Processor architecture + +NOTE 1 – The GKSP may hold further useful functions such as for example a NAT (network address translation function), a firewall, an application-level gateway (ALG) etc.; such functions may be part of the security processing or may be kept as separate internal functions, yet such functions are not described in this clause and remain as for further study. + +The GKSP serves a certain number of endpoints within an administrative security domain A. The GKSP may also communicate with another GKSP in some other administrative security domain C (not shown). + +NOTE 2 – The three administrative security domains do not necessarily have to be distinct in practice. The GKSP may be placed entirely within administrative security domain B where the GK belongs to, or alternatively, the GKSP may be placed within security domain A, or within a separate, own security domain (not shown). + +Using the GKSP, the Gatekeeper would not need to get involved in executing computational-expensive security operations. The GK still determines authorization and admission by matching an appropriate credential (e.g., alias name/DN name/certificate serial number, X.509 certificate) against the (internal/external) database holding the subscribed users with their permissions and credentials. Clause I.3 defines suitable credentials for use by an H.235.3-enabled GKSP. + +NOTE 3 – A possible LDAP interface between the GK and subscriber/user database is not subject to this Recommendation. It is also left to the policy of the gatekeeper on which criteria and credentials (e.g., alias name/DN name/certificate serial number) to realize the access control decision. It is left to the discretion of such a user database, which credentials (alias name/DN name/certificate serial number) are stored therein. + +NOTE 4 – The GKSP does not need to get involved in any matters regarding configuration or administration of users, subscribers and the GKSP does not need to access a user database. + +NOTE 5 – Those endpoints which deploy H.235.3 and the GKSP typically also hold a root certificate (not shown in Figure I.1). The root certificate allows the entity to verify the certificate of the entity (EP, GKSP). + +Communication between the GKSP and its GK, or among two GKSPs, is secured. For example, H.235.1 is applied when a statically configured shared secret is assumed. H.235.3 is applied that allows establishing a dynamic shared secret. In either case, GK and GKSP are assumed to have established a mutual trust relationship, be it either a static or a dynamic security association. The trust relationship may be chained when multiple GKSPs are involved. + +Thus, the GK trusts the GKSP for executing the far-end authentication procedures and for correctly realizing the security procedures. The GKSP reports the outcome of its security processing in a simple security assertion using the processor token to the GK. + +It is assumed that each H.235.3-enabled EP and the GKSP hold a X.509 certificate that trustfully binds the identity of the legitimate owner of the public key and a corresponding private key for signing. + +NOTE 6 – The public key corresponding to the private key is not shown explicitly in Figure I.1; typically, the certified public key is conveyed within the X.509 user/EP certificate. + +NOTE 7 – Not all certificates/private keys are shown for all endpoints/GKSP. + +NOTE 8 – The GKSP certificate typically is a server certificate. + +The GK is required to hold a distinct, unique GK certificate and a private key only if the GK deploys H.235.3 for communication with the GKSP. + +The GKSP is a stateful proxy operating inbetween the endpoints and the GK, or inbetween two gatekeepers. There is at least one GKSP entity for each GK, yet one GK may also serve multiple GKSPs to increase scalability in the number of served endpoints, and to improve robustness of the entire system. It is possible to arrange linearly chained H.235.3-specific GKSP elements as shown in Figure I.2. It is possible to arrange H.235.3-specific GKSP elements in a hierarchical architecture as shown in Figure I.3. + +There is at least one generic GKSP entity for each GK, yet one GK may also serve multiple generic GKSPs to increase scalability in the number of served endpoints and to improve robustness of the entire system. There may be one or more generic GKSPs between an endpoint and a GK: thus, linear or hierarchical, cascading configurations of several GKSP should in principle be possible. An endpoint always establishes a trust relation with its associated GK through one or more GKSPs. A single GK may have multiple trust relationships with multiple EPs. + +Figure I.2 shows an architecture with linearly chained GKSP elements. + +![Figure I.2/H.235.3 – Chained GKSP architecture diagram](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +A linear sequence of seven rectangular boxes connected by horizontal lines. The boxes are labeled from left to right: EP1, GKSP1, GKSP2, GK1, GKSP3, GKSP4, and GK2. + +Figure I.2/H.235.3 – Chained GKSP architecture diagram + +H.235.3\_F1.2 + +**Figure I.2/H.235.3 – Chained GKSP architecture** + +In Figure I.2, GKSP1 authenticates the RRQ message received from EP1, while GK1 or GK2 decide upon the authorization of EP1. GKSP1, GKSP2 (resp. GKSP3 and GKSP4) rely H.323 signalling messages between EP1 and GK1 (resp. GK1 and GK2). + +Figure I.3 shows an architecture with hierarchical, cascaded GKSPs elements. + +![Figure I.3/H.235.3 – Hierarchical GKSP architecture diagram](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +A hierarchical diagram. At the top, four boxes are connected horizontally: EP1, GKSP1, GKSP2, and GK1. Below this, a second row contains two boxes: EP2 and GKSP3. A vertical line descends from the bottom of the GK1 box to the top of the GKSP3 box, indicating a hierarchical relationship where GKSP3 is connected to GK1. + +Figure I.3/H.235.3 – Hierarchical GKSP architecture diagram + +H.235.3\_F1.3 + +**Figure I.3/H.235.3 – Hierarchical GKSP architecture** + +The GKSP has at least one IP address; typically a GKSP is an edge security device that is located at the border of two distinct administrative security domains. Thus, the GKSP may own two IP addresses, one IP address towards the H.323 endpoints/peer GKSP (administrative security domains A and C) and a different one internally towards the GK (administrative security domain B). + +### I.1 Discovery of a gatekeeper security processor + +It is assumed that an H.323 endpoint is not required to know of presence of a GKSP. The endpoint may have configured the IP address of the GKSP as the GK contact point. In a scenario with a GKSP present, the EP behaves exactly as in a scenario without a GKSP. The EP may use the GK discovery phase using **GRQ** to locate its serving GKSP. + +In the case where there is a GKSP that serves the requesting EP, the GKSP needs to find out if its GK supports a security processor. + +In the case where the GKSP intends to use H.235.1 towards the GK but a shared secret has not been configured between the GKSP and GK, the GKSP returns **GRJ** to the endpoint with **reason** set to **securityDenial/securityDenied**. Otherwise, the GKSP forwards the **GRQ** and includes a processor ClearToken and sets the profile element with element ID 0 as defined in Table I.1. Since, in this case, the GK supports the GKSP, the GK returns a **GCF/GRJ** and includes a processor token. + +In the case where the GKSP intends to use H.235.3 towards the GK, the GKSP forwards **GRQ** to the GK with the inclusion of a processor ClearToken and sets the profile element with element ID 0 as defined in Table I.1. A GKSP-enabled GK supporting this appendix responds by **GCF** and the inclusion of a processor ClearToken. + +A GK that does not support a security processor or a GK that has not implemented this appendix would ignore the conveyed processor token and would respond by **GCF/GRJ**. The GKSP is able to recognize this situation, as the received **GRQ/GRJ** does not convey a processor token. The GKSP then sends a **GRJ** to the endpoint with **reason** set to **securityDenial/securityDenied**. + +A GK that has received a **GRQ** from an endpoint directly without relay through a GKSP, and where the GK is aware of a GKSP, responds with an **GRJ** with **reason** set to **securityDenial/securityDenied** (without inclusion of a processor token). + +### I.2 Gatekeeper security processor operation + +The GK security processor performs at least the following functions: + +- Terminates the H.235.3 protocol to the H.323 endpoints, or to the peer GKSP, as defined by procedure IV. +- Runs the Diffie-Hellman H.235.3 protocol towards the H.323 endpoints/peer GKSP; i.e. performs the Diffie-Hellman modular-exponentiation operations. +- Performs verification of digital signatures received from H.323 endpoints or peer GKSP in H.235.3 secured messages. +- Security checks of received X.509 digital certificates: path verification, validity check, CRL check, etc. +- For message forwarding from the GKSP to the GK or to another GKSP, the GKSP generates new H.235 tokens (H.235.1 or H.235.3). The GKSP uses its GKSP identifier as **sendersID** and uses the gatekeeper identifier (GKID) as **generalID** in the baseline H.235 ClearToken. +- For messages received from the H.323 endpoint, the GKSP includes a processor token. For the initial **RRQ/GRQ** message, the processor token holds a security profile element with ElementID 0 that indicates the encountered authentication method. The GKSP may include a security profile element with ElementID 0 in any other H.225.0 RAS and/or Call Signalling message too. + +Further, the processor token holds one or more security profile elements that convey the credentials. + +Suitable credentials in the context of this appendix are: + +- ElementID 1 for providing the subject found in an X.509 certificate; +- ElementID 2 for providing the subjectAltName found in an X.509 certificate; +- ElementID 3 for providing the serial number found in an X.509 certificate; +- ElementID 4 for providing the issuer name found in an X.509 certificate; +- ElementID 5 for providing the endpoint identifier of the H.323 terminal. + +NOTE – The GK may additionally interpret the H.323 alias element in H.225.0 messages as a credential. Since the alias element is present anyway in messages, there is no need to define a separate alias element within a security profile element. + +GKSP also includes a security profile element with ElementID 6 to indicate an encountered error. If the authentication between H.323 endpoint and GKSP has been successful, then the GKSP may include a security profile element with ElementID 6 to indicate that no security error has been encountered. + +- In the case where the GKSP encounters security errors (digital signature wrong, certificate validation failed, etc.) in a message received from the H.323 endpoint or from the peer GKSP, the GKSP logs the error and forwards the message to the GK, includes a processor token with a security profile element of type ElementID 6 by indicating the type of error and lets the GK decide and react accordingly. +- In the case where the GKSP encounters security errors in a message received from the GK or from another GKSP, the GKSP logs the error and discards the message. +- Computes digital signatures for outgoing H.235.3 messages to the H.323 endpoints or peer GKSP. + +- Relays any H.225.0 messages between H.323 endpoint and gatekeeper or GKSP back and forth and performs the following operations on tokens: + - Communicates with its gatekeeper using the H.225.0 protocol where the H.235.3 tokens, received from the H.323 endpoints or from peer GKSP in the 1st handshake, are stripped off. + - Verifies embedded H.235.1 tokens received from H.323 endpoints, or from a peer GKSP, and strips them off for further relay of messages to the gatekeeper. + - Terminates H.235.1/H.235.3 protocol to its gatekeeper. + - Includes H.235.1/H.235.3 tokens towards the H.323 endpoints or towards peer GKSP for outgoing messages. + - Leaves the received H.225.0 messages received from H.323 EPs or GK basically intact; only rewrites tokens as defined above. + - The H.225.0 protocol between GKSP and its GK is secured using either H.235.1 baseline security profile or H.235.3 hybrid security profile. +- In the case where GKSP and GK or the GKSP and another GKSP deploy the H.235.3 hybrid security profile, the GKSP either: + - a) runs the H.235.3 protocol towards the GK or GKSP for establishing a new dynamic key upon reception of the first message from the first endpoint or peer GKSP; or + - b) initiates the H.235.3 protocol towards the GK or GKSP for establishing a new dynamic key before any other H.323 endpoint or peer GKSP have started communication. This would permit a dynamic shared secret to be in place, ready for application to protect the first handshake messages received from an H.323 terminal or peer GKSP; this would further shorten the overall security association setup time. +- The GKSP does not forward any H.235.3-specific FACILITY messages for key update. +- In the case where GKSP and GK or the GKSP and another GKSP deploy the H.235.1 baseline security profile, the GKSP applies the static shared key for protection of the H.225.0 RAS and/or Call Signalling messages. +- Keeps track of security associations; i.e., establishes the DH shared secret; maintains the dynamic shared secrets. Depending on its security policy, the GKSP may invoke re-keying for the maintained dynamic shared secret(s) using FACILITY messages. Once the H.323 terminal or peer GKSP has de-registered, the GKSP should discard the dynamic shared key and consider no security association in place. +- Maps transport ports (EP-GKSP and GKSP-GK) for H.225.0 RAS and/or Call Signalling protocols one-to-one. + +### I.3 Processor token + +Upon reception of an H.235.3 secured H.225.0 RAS and/or Call Signalling message with a conveyed X.509 certificate and digital signature, the GKSP removes the H.235.3 tokens and includes a separate processor token to the forwarded message to its GK or next GKSP (if any). + +With the processor token, the GKSP reports the encountered authentication method, the encountered endpoint identifier, the encountered name in the certificate (name or subjectAltName), the encountered serial number in the X.509 certificate, the encountered issuer name in the X.509 certificate or an error indication. The processor token plays the role of a simple security assertion testifying to the asserted security relationship (successful or failed) between the GKSP and the H.323 endpoints towards the GK. + +The GK is able to detect the presence of a GKSP by inspecting the received message and recognizing an included processor token. The GK interprets the absence of any processor token to indicate absence of any GKSP. + +The processor token is a ClearToken with the following fields used: + +- **tokenOID** holds an OID for "PT"; see Table I.2. +- **generalID** holds either: + - the endpoint identifier of the H.323 endpoint in the case of a received H.235 secured message from an H.323 endpoint or holds; + - the GK identifier in the case of a received H.235 secured message from the GK. +- **certificate** may optionally hold the received H.235.2/H.235.3 certificate received from the H.323 endpoint or peer GKSP. If this feature is implemented, the GKSP forwards the certificate to the GK. + +The usage of the subject/subjectAltName, or of the endpoint ID or of the certificate serial number or other lightweight credential should be preferred over including the entire certificate within the **certificate** field. This is because X.509 certificates tend to be a bigger piece of data and because of the potential problem of message fragmentation when certificates are included in UDP transported H.225.0 messages. + +- **profileInfo** holds at least one profile element. + +The processor token may hold several profile elements; among them as listed in Table I.1: + +Any other fields within GK security processor ClearToken remain unused. + +**Table I.1/H.235.3 – Specification of profile elements** + +| ElementID value | Description | Specification | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Indicates a profile element that conveys the authentication method.

The usage of this profile element is mandatory for the initial handshake (GRQ or RRQ) and optional otherwise. |
  • • Params remains unused.
  • • Element holds an Element where integer is set to one of the following values to indicate the encountered authentication method at the H.323 endpoint or peer GKSP:
    1. 1) other, unspecified and non-standard authentication method;
    2. 2) none (i.e. no authentication);
    3. 3) H.235.1 shared secret, (undefined by this appendix);
    4. 4) H.235.2;
    5. 5) H.235.3;
    6. 6) H.235.5, (undefined by this appendix);
    7. 7) H.235.4, (undefined by this appendix);
    8. 8) H.530, (undefined by this appendix).
| + +**Table I.1/H.235.3 – Specification of profile elements** + +| ElementID value | Description | Specification | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Indicates a profile element that holds the subject of the received certificate.
The usage of this profile element is optional. |
  • • ParamS remains unused.
  • • Element holds an Element where name or octets holds the subject of the received certificate.

NOTE – The GKSP may need to re-encode the subject from the X.509 Name representation into an octets string or BMP name representation.

| +| 2 | Indicates a profile element that holds the subjectAltName of the received certificate.
The usage of this profile element is optional. |
  • • ParamS remains unused.
  • • Element holds an Element where name or octets holds the subjectAltName of the received certificate.

NOTE – The GKSP may need to re-encode the subjectAltName from the X.509 Name representation into an octets string or BMP name representation.

| +| 3 | Indicates a profile element that holds the serial number of the certificate.
The usage of this profile element is mandatory. |
  • • paramS remains unused.
  • • element holds an Element where integer holds the CertificateSerialNumber of the received X.509 certificate.
| +| 4 | Indicates a profile element that holds the issuer of the certificate.
The usage of this profile element is mandatory. |
  • • paramS remains unused.
  • • element holds an Element where name or octets holds the issuer name of the received X.509 certificate.

NOTE – The GKSP may need to re-encode the issuer name from the X.509 Name representation into an octets string or BMP name representation.

| +| 5 | Indicates a profile element that holds the endpoint ID of the originating endpoint/terminal.
The usage of this profile element is optional. |
  • • paramS remains unused.
  • • element holds an Element where name holds the endpoint identifier of the originating endpoint/terminal.
| +| 6 | Indicates a profile element that holds an error indication.
The usage of this profile element is mandatory in any error case (> 0) but optional to indicate no error (0). |
  • • paramS remains unused.
  • • element holds an Element where integer holds one of the following encoded error values:
    0: no error
    1: securityDenied
    2: securityWrongSyncTime
    3: securityReplay
    4: securityWrongGeneralID
    5: securityWrongSendersID
    6: securityMessageIntegrityFailed
    7: securityWrongOID
    8: securityDHmismatch
    9: securityCertificateExpired
    10: securityCertificateDateInvalid
| + +**Table I.1/H.235.3 – Specification of profile elements** + +| ElementID value | Description | Specification | +|-----------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | 11: securityCertificateRevoked
12: securityCertificateNotReadable
13: securityCertificateSignatureInvalid
14: securityCertificateMissing
15: securityCertificateIncomplete
16: securityUnsupportedCertificateAlgOID
17: securityUnknownCA
18: unspecified security error
19: GKSP not supported. | + +### I.4 GKSP illustration example + +This clause shows example message flow diagrams (see Figures I.4 and I.5) for a GK security processor operating within an administrative security domain. Note, that Figures I.4 and I.5 only show those messages that are crucial for H.235.3; in practice there may be many more H.225.0 RAS and/or Call Signalling messages. + +In both figures, H.235.3-enabled H.323 terminal A and GKSP deploy the H.235.3 hybrid security profile; thus Terminal A and GKSP B do not share any static shared secret. In Figure I.4, GKSP and GK deploy the H.235.1 baseline security profile for protection of the H.225.0 RAS and Call Signalling messages. $K_{BC}$ represents the static shared secret that GKSP B and GK C share. + +Figure I.4 illustrates an entire call from terminal A through GKSP B and GK C. The call is GK-routed. At the beginning, terminal A and GKSP B negotiate a dynamic link key $K_{AB}$ according to H.235.3 during RAS registration. For this, Terminal A generates the **RRQ** message that conveys the Diffie-Hellman half-key $DH_A$ of A, holds A's certificate (optional), and A's digital signature upon all or parts of the **RRQ** message. + +GKSP B receives the **RRQ** and verifies the digital signature. This includes validation and verification of the conveyed digital X.509 certificate (if included) against A's root certificate, path verification, CRL checks etc. + +The GKSP forwards the **RRQ** message to GK C, adds a processor token (PT) including security profile elements: + +- 0 indicating H.235.3 (5); +- 2 holding the subjectAltName of A's certificate; +- 3 the serial number of A's certificate; +- 5 the endpoint ID of A. + +and applies the H.235.1 baseline security profile with the shared key $K_{BC}$ ; the HMAC-SHA1 integrity check is computed either on the entire **RRQ** message or only on certain parts of it. + +In case the certificate validation or digital signature validation fails, GKSP B cannot authenticate and authorize Terminal A; GKSP then logs an error, and forwards the incorrect **RRQ** to GK C. + +Gatekeeper C receives the **RRQ** message, verifies the integrity check by applying $K_{BC}$ and processes the processor token PT with the included profile elements. If GK C is able to successfully validate the **RRQ**, GK C authorizes Terminal A. GK C then responds by an **RCF** that is sent to GKSP B. + +GKSP B receives the **RCF**, recognizes that GK C has successfully authorized Terminal A and forwards an **RCF** to Terminal A, by computing and including its Diffie-Hellman half-key $DH_B$ , its certificate (optional) and signs the **RRQ** (fully or partially) with its private key. Terminal A validates the authenticity of the received **RCF** message. + +In the case where GKSP B successfully authenticates and authorizes Terminal A, GKSP B and Terminal A compute the dynamic shared secret $K_{AB}$ . This dynamic shared secret represents the established trust relationship between Terminal A and GKSP B. Otherwise, and in the case where GK C does not authorize Terminal A, GKSP B forwards an **RCF** to Terminal A by computing and including its Diffie-Hellman half-key $DH_B$ , its certificate (optional) and signs the **RRQ** (fully or partially) with its private key. Since Terminal A is not authorized, GKSP B does not keep $K_{AB}$ any further. GKSP B may record the failed **RCF** in a log file. + +Terminal A and GKSP B use this dynamic shared secret $K_{AB}$ to further protect H.225.0 RAS and Call Signalling messages using H.235.1 baseline security profile. GKSP B and GK C use H.235.1 baseline security profile for protection of the all H.225.0 RAS and Call Signalling messages. + +In the case where Terminal A receives an **RCF**, Terminal A does not proceed with the call setup. + +Figure I.4 also shows an error case where terminal A (or someone else) sends an unprotected **BRQ** message to the GKSP; this message could also have been due to an attack where the attacker somehow removed or compromised the H.235.1 security protection. GKSP detects the failed integrity verification and forwards the **BRQ** message including a processor token to the GK, whereas the security profile element indicates `securityMessageIntegrityFailed` (6). The GK recognizes the security violation and does not authorize the bandwidth request by rejecting it with a **BRJ** reply. + +At some point in time after the call has been established, terminal A decides to refresh the key $K_{AB}$ by performing a key updating procedure for $K_{AB}$ with GKSP B; $K'_{AB}$ represents the new updated key. At the end of the call, it is terminated by GK C. + +![Sequence diagram showing call flow between Terminal A, GK Security Processor B, and Gatekeeper C. The diagram illustrates the exchange of messages for call setup and teardown, with security tokens and HMAC integrity checks.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +``` + +sequenceDiagram + participant Terminal A + participant GKSP as GK Security Processor B + participant Gatekeeper C + + Terminal A->>GKSP: RRQ: DH_A, (Cert_A), Sig_A + GKSP->>Gatekeeper C: RRQ: PT(Eid0(5), Eid2, Eid3, Eid5), HMAC-SHA1(K_BC) + Gatekeeper C->>GKSP: RCF: HMAC-SHA1(K_BC) + GKSP->>Terminal A: RCF: DH_B, (Cert_B), Sig_B + Note over Terminal A, GKSP: K_AB := + Terminal A->>GKSP: ARQ: HMAC-SHA1(K_AB) + Gatekeeper C->>GKSP: ARQ: PT(Eid6(0)), HMAC-SHA1(K_BC) + Gatekeeper C->>GKSP: BRQ: PT(Eid6(6)), HMAC-SHA1(K_BC) + Terminal A->>GKSP: BRQ: + Terminal A->>GKSP: BRJ: HMAC-SHA1(K_AB) + Gatekeeper C->>GKSP: BRJ: HMAC-SHA1(K_BC) + Note over Terminal A, GKSP: + Note over GKSP, Gatekeeper C: + Terminal A->>GKSP: SETUP: HMAC-SHA1(K_AB) + Gatekeeper C->>GKSP: SETUP: PT(Eid6(0)), HMAC-SHA1(K_BC) + Terminal A->>GKSP: CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT: HMAC-SHA1(K_AB) + Gatekeeper C->>GKSP: CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT: HMAC-SHA1(K_BC) + Terminal A->>GKSP: FACILITY: DH_A, (Cert_A), Sig_A + GKSP->>Terminal A: FACILITY: DH_B, (Cert_B), Sig_B + Note over Terminal A, GKSP: K'_AB := + Note over GKSP, Gatekeeper C: + Terminal A->>GKSP: RELEASE COMPLETE: HMAC-SHA1(K'_AB) + Gatekeeper C->>GKSP: RELEASE COMPLETE: HMAC-SHA1(K_BC) + +``` + +Sequence diagram showing call flow between Terminal A, GK Security Processor B, and Gatekeeper C. The diagram illustrates the exchange of messages for call setup and teardown, with security tokens and HMAC integrity checks. + +H.235.3\_F1.4 + +| | | | | +|-----------------|------------------------------------------------|-----------|--------------------------------| +| Cert | User certificate | GKSP | Gatekeeper Security Processor | +| DH A | Diffie-Hellman Token $g^a \bmod p$ | HMAC-SHA1 | Computed integrity check value | +| DH B | Diffie-Hellman Token $g^b \bmod p$ | K, K' | Symmetric link key | +| Eid n | Security Profile ElementID with value n | PT | Processor Token | +| EP | Endpoint (Terminal) | Sig | Digital signature | +| GK | Gatekeeper | | | + +**Figure I.4/H.235.3 – Call flow with GK-security processor and H.235.1 message protection (GKSP-to-GK)** + +In Figure I.5, GKSP and GK deploy the H.235.3 hybrid security profile for protection of the H.225.0 RAS and Call Signalling messages. $K_{BC}$ represents the dynamic shared secret that GKSP and GK first negotiate and then share for further use within H.235.1 baseline security profile for protection of the H.225.0 RAS and Call Signalling messages. Figure I.5 also shows a H.235.1-enabled H.323 terminal D that shares a static shared secret $K_{DB}$ with its GKSP B. + +Figure I.5 illustrates an entire call flow from terminal A through GKSP B and GK C. The call is GK-routed. In Figure I.5, it is assumed that terminal A is actually the first endpoint that registers at the GK through the GKSP. + +Terminal A and GKSP B use this dynamic shared secret $K_{AB}$ to protect further H.225.0 RAS and Call Signalling messages using H.235.1 baseline security profile. GKSP B and GK C use H.235.1 baseline security profile for protection of the further H.225.0 RAS and Call Signalling messages using the dynamic shared secret $K_{BC}$ . + +At the beginning, terminal A and GKSP B negotiate a dynamic link key $K_{AB}$ according to H.235.3. During the first **RRQ/RCF** handshake between terminal A and GKSP where both entities establish a dynamic shared secret $K_{AB}$ , the GKSP and the GK also deploy H.235.3 to establish a dynamic shared secret $K_{BC}$ . + +The GKSP forwards the **RRQ** message received from terminal A, adds a processor token including three security profile elements: + +- 0 indicating H.235.3 (5); +- 3 the serial number of A's certificate; +- 6 indicating no error (0), + +and applies the H.235.3 hybrid security profile. Since GKSP B and GK C do not yet share any shared secret, GKSP and GK run the H.235.3 protocol and establish a dynamic shared secret $K_{BC}$ . + +Sometime later, terminal D registers at the GKSP B using H.235.1-secured **RRQ**. GKSP B forwards this **RRQ** to the GK C and includes a processor token. The processor token conveys three security profile elements + +- 0 indicating H.235.1 (3); +- 5 providing D's endpoint identifier; +- 6 indicating no error (0), + +and applies the H.235.3 hybrid security profile. Since the H.235.3 dynamic shared secret $K_{BC}$ has already been established before, GKSP secures the forwarded **RRQ** message using H.235.1 by applying $K_{BC}$ . GK C authorizes terminal D and replies with an **RCF** that the GKSP forwards to terminal D. + +At some point in time after the call from terminal A has been established through GK C, GKSP B decides to refresh the key $K_{BC}$ by performing a key updating procedure for $K_{BC}$ with GK C; $K'_{BC}$ represents the new updated key. + +Figure I.5 also shows an error case where GKSP receives a **RELEASE-COMPLETE** message from the GK. GKSP B detects that integrity verification fails; this message does not use the current key. The message could have been replayed or manipulated by an attacker or the GK uses an old and expired key. GKSP B logs the security event and discards the message without forwarding it to terminal A. + +At the end of the call, it is terminated by GK C. + +![Sequence diagram showing call flow with GK-security processor and H.235.3 message protection. Lifelines: Terminal D, Terminal A, GK Security Processor B, Gatekeeper C. The diagram shows messages like RRQ, RCF, ARQ, SETUP, CALL-PROCEEDING, FACILITY, and RELEASE COMPLETE with HMAC-SHA1 integrity checks.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +``` + +sequenceDiagram + participant D as Terminal D + participant A as Terminal A + participant B as GK Security Processor B + participant C as Gatekeeper C + + A->>B: RRQ: DHA, (CertA), SigA + B->>C: RRQ: PT(Eid0(3), Eid5, Eid6(0)), DHB, (CertB), SigB + C->>B: RCF: DHC, (CertC), SigC + B->>A: RCF: DHB, (CertB), SigB + Note over A,B: KAB:= + A->>B: ARQ: HMAC-SHA1(KAB) + B->>C: ARQ: PT(Eid6(0)), HMAC-SHA1(KBC) + D->>B: RRQ: HMAC-SHA1(KDB) + B->>C: RRQ: PT(Eid0(3), Eid2, Eid6(0)), HMAC-SHA1(KBC) + B->>D: RCF: HMAC-SHA1(KDB) + B->>C: RCF: HMAC-SHA1(KBC) + Note over D,A: .... + Note over A,B: .... + Note over B,C: .... + A->>B: SETUP: HMAC-SHA1(KAB) + B->>C: SETUP: PT(Eid6(0)), HMAC-SHA1(KBC) + B->>A: CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT: HMAC-SHA1(KAB) + B->>C: CALL-PROCEEDING/PROGRESS/ALERTING/CONNECT: HMAC-SHA1(KBC) + B->>C: FACILITY: PT(Eid6(0)), DHB, (CertB), SigB + C->>B: FACILITY: DHC, (CertC), SigC + Note over B,C: K'BC:= + Note over B,C: .... + C->>B: RELEASE COMPLETE: HMAC-SHA1(KBC) + B->>A: RELEASE COMPLETE: HMAC-SHA1(K'AB) + B->>C: RELEASE COMPLETE: HMAC-SHA1(K'BC) + +``` + +Sequence diagram showing call flow with GK-security processor and H.235.3 message protection. Lifelines: Terminal D, Terminal A, GK Security Processor B, Gatekeeper C. The diagram shows messages like RRQ, RCF, ARQ, SETUP, CALL-PROCEEDING, FACILITY, and RELEASE COMPLETE with HMAC-SHA1 integrity checks. + +H.235.3\_F1.5 + +| | | | | +|------------------|-------------------------------------------|-----------|--------------------------------| +| Cert | User certificate | GK | Gatekeeper | +| DH A | Diffie-Hellman Token $g^a \bmod p$ | GKSP | Gatekeeper Security Processor | +| DH B | Diffie-Hellman Token $g^b \bmod p$ | HMAC-SHA1 | Computed integrity check value | +| DH C | Diffie-Hellman Token $g^c \bmod p$ | K, K' | Symmetric link key | +| Eid n | Security Profile ElementID with value $n$ | PT | Processor Token | +| EP | Endpoint (Terminal) | Sig | Digital signature | + +**Figure I.5/H.235.3 – Call flow with GK-security processor and H.235.3 message protection (GKSP-to-GK)** + +### I.5 List of object identifiers + +Table I.2 lists the referenced OID that is to be used in conjunction with Table I.1. + +**Table I.2/H.235.3 – Object identifiers used by Appendix I** + +| Object identifier reference | Object identifier value(s) | Description | +|------------------------------------|-----------------------------------------------------------|--------------------------------------------------------------------------------------| +| "PT" | {itu-t (0) recommendation (0) h (8) 235 version (0) 4 15} | Used to indicate the GK processor Clear token for communication from a GKSP to a GK. | + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.235.4-200509-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/H/T-REC-H.235.4-200509-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ac4a34e45e2ee12292b929444f5cdcb2cde403a --- /dev/null +++ b/marked/H/T-REC-H.235.4-200509-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:490c59f5489090b81a35d32ed7c50db9930c700269dd87d4977cc1711e47d580 +size 205462 diff --git a/marked/H/T-REC-H.235.4-200509-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/H/T-REC-H.235.4-200509-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0690accfffe91d5a88e2eee6a0be02b9c7997b23 --- /dev/null +++ b/marked/H/T-REC-H.235.4-200509-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:135f3cda9eab7487ad7442a8f1cc5a9966743d7392bbeab3b7281c56888f35bc +size 29304 diff --git a/marked/H/T-REC-H.235.4-200509-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.235.4-200509-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cf3a6acb906afef9031c3df7dce69a4bc265961 --- /dev/null +++ b/marked/H/T-REC-H.235.4-200509-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c3f1d934cdce4b0667e41f30d17b50952418799b1ad17db8ae4b97a5ec72ba3 +size 3681 diff --git a/marked/H/T-REC-H.235.4-200509-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/H/T-REC-H.235.4-200509-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2117ed1f28cb4792ee59ce08a81c451b55507e12 --- /dev/null +++ b/marked/H/T-REC-H.235.4-200509-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:671b0e95f02238d7dd1049d9932a6e3892dc13914f2a7949fcbeffe98a5b87cc +size 201128 diff --git a/marked/H/T-REC-H.235.4-200509-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/H/T-REC-H.235.4-200509-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e3f98abd18f927febc5d5e82ea7da3d0bdaac2a --- /dev/null +++ b/marked/H/T-REC-H.235.4-200509-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ff7666e142ca0cbb1d6fe2d4152b570a37350c712e1365a09a955e2e400d5e4 +size 184842 diff --git a/marked/H/T-REC-H.235.4-200509-I_PDF-E/raw.md b/marked/H/T-REC-H.235.4-200509-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a1b94c9ea8b803b963aec0d447227a7213e239b0 --- /dev/null +++ b/marked/H/T-REC-H.235.4-200509-I_PDF-E/raw.md @@ -0,0 +1,812 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.235.4** + +(09/2005) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Systems aspects + +--- + +**H.323 security: Direct and selective routed call +security** + +ITU-T Recommendation H.235.4 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.235.4** + +## **H.323 security: Direct and selective routed call security** + +### **Summary** + +The purpose of this Recommendation is to provide recommendations of security procedures for using direct-routed call signalling in conjunction with H.235.1 and H.235.3 security profiles. This security profile is offered as an option and may complement the security profiles in ITU-T Recs H.235.1 and H.235.3. It also provides implementation details for clause 8.4/H.235.0 using symmetric key management techniques. + +In earlier versions of the H.235 subseries, this profile was contained in Annex I/H.235. Appendices IV, V, VI to H.235.0 show the complete clause, figure, and table mapping between H.235 versions 3 and 4. + +### **Source** + +ITU-T Recommendation H.235.4 was approved on 13 September 2005 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +### **Keywords** + +Authentication, direct-routed call security, encryption, integrity, key management, multimedia security, security profile, selective routed call security. + +### FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +### INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2006 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +### CONTENTS + +###### Page + +| | | | +|------|-----------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 2.1 | Normative references..... | 1 | +| 2.2 | Informative references..... | 1 | +| 3 | Terms and definitions ..... | 2 | +| 4 | Symbols and abbreviations ..... | 2 | +| 5 | Conventions ..... | 2 | +| 6 | Introduction ..... | 2 | +| 7 | Overview ..... | 3 | +| 8 | Limitations..... | 4 | +| 9 | Procedure DRC1 (corporate environment)..... | 4 | +| 9.1 | GRQ/RRQ phase ..... | 4 | +| 9.2 | ARQ phase..... | 4 | +| 9.3 | LRQ phase ..... | 4 | +| 9.4 | LCF phase..... | 5 | +| 9.5 | ACF phase ..... | 6 | +| 9.6 | SETUP phase..... | 7 | +| 10 | Procedure DRC2 (interdomain environment)..... | 9 | +| 10.1 | GRQ/RRQ phase ..... | 9 | +| 10.2 | ARQ phase..... | 9 | +| 10.3 | LRQ phase ..... | 9 | +| 10.4 | LCF phase..... | 9 | +| 10.5 | ACF phase ..... | 10 | +| 10.6 | SETUP phase..... | 12 | +| 11 | Procedure DRC3 (interdomain environment)..... | 14 | +| 11.1 | GRQ/RRQ phase ..... | 14 | +| 11.2 | ARQ phase..... | 14 | +| 11.3 | LRQ phase ..... | 14 | +| 11.4 | LCF phase..... | 14 | +| 11.5 | ACF phase ..... | 15 | +| 11.6 | SETUP phase..... | 16 | +| 12 | PRF-based key derivation procedure..... | 18 | +| 13 | FIPS-140-based key derivation procedure..... | 18 | +| 14 | List of object identifiers..... | 19 | + + + +## H.323 security: Direct and selective routed call security + +# 1 Scope + +The purpose of this Recommendation is to provide recommendations of security procedures for using direct-routed and selective routed call signalling in conjunction with H.235.1 and H.235.3 security profiles. + +This security profile is offered as an option and may complement the H.235.1 or H.235.3 security profiles. It also provides implementation details for clause 8.4/H.235.0 using symmetric key management techniques. + +# 2 References + +## 2.1 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.235 (2003), *Security and encryption for H-series (H.323 and other H.245-based) multimedia terminals*, Corrigendum 1 (2005), plus Erratum 1 (2005). +- ITU-T Recommendation H.235.0 (2005), *H.323 security: Framework for security in H-series (H.323 and other H.245-based) multimedia systems*. +- ITU-T Recommendation H.235.1 (2005), *H.323 security: Baseline security profile*. +- ITU-T Recommendation H.235.3 (2005), *H.323 security: Hybrid security profile*. +- ITU-T Recommendation H.235.6 (2005), *H.323 security: Voice encryption profile with native H.235/H.245 key management*. +- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*. +- ITU-T Recommendation X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*. +- ISO/IEC 7498-2:1989, *Information processing systems – Open Systems Interconnection – Basic Reference model – Part 2: Security Architecture*. +- ISO/IEC 10118-3:2004, *Information technology – Security techniques – Hash functions – Part 3: Dedicated hash-functions*. + +## 2.2 Informative references + +- ITU-T Recommendation H.235.2 (2005), *H.323 security: Signature security profile*. +- IETF RFC 4120 (2005), *The Kerberos Network Authentication Service (V5)*. + +# 3 Terms and definitions + +For the purposes of this Recommendation the definitions given in clause 3 of ITU-T Recs H.323, H.225.0, H.235.0 and X.800 | ISO 7498-2 apply. + +# 4 Symbols and abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| CT | ClearToken | +| DH | Diffie-Hellman | +| DRC | Direct-Routed Call | +| EK AG | The encryption key shared between EP A and GK G | +| EK BH | The encryption key shared between EP B and GK H | +| EK GH | The encryption key shared between GK G and GK H | +| ENC K; S, IV (M) | EOFB Encryption of M using secret key K and secret salting key S and initial vector IV | +| EPID | Endpoint Identifier | +| GK | Gatekeeper | +| GKID | Gatekeeper Identifier | +| gx, gy | Diffie-Hellman half-key of GK G, GK H | +| K AB | The encryption key shared between EP A and EP B | +| K AG | Shared secret (H.235.1, H.235.3) between EP A and GK G | +| K BH | Shared secret (H.235.1, H.235.3) between EP B and GK H | +| K GH | Secret, secret (H.235.1, H.235.3) between GK G and GK H | +| KS AG | Secret, shared salting key between EP A and GK G | +| KS BH | Secret, shared salting key between EP B and GK H | +| KS GH | Secret, shared salting key between GK G and GK H | +| PRF | Pseudo-Random Function | + +# 5 Conventions + +In this Recommendation the following conventions are used: + +- "shall" indicates a mandatory requirement. +- "should" indicates a suggested but optional course of action. +- "may" indicates an optional course of action rather than a recommendation that something take place. + +The object identifiers are referenced through a symbolic reference in the text (e.g., "I11"), clause 14 lists the actual numeric values for the symbolic object identifiers, see also clause 5/H.235.0. + +# 6 Introduction + +H.323 is often deployed using the gatekeeper-routed model (for example, to take advantage of better billing functionalities). The widespread use of gatekeeper-routed call models is also the + +reason why different security profiles, focused exactly on this call model, are defined within ITU-T Rec. H.235.0 (such as H.235.1, H.235.2, H.235.3). + +However, with the need to support an increasing number of parallel channels, the direct-routed call model with a gatekeeper could yield better performance and scalability properties. The advantage of this mode is the utilization of a gatekeeper for registration, admission, address resolution, and bandwidth control, while performing the call establishment directly between the end points in an end-to-end fashion. + +This Recommendation describes the enhancements for the H.235.1 baseline and for H.235.3 hybrid security profiles to support direct-routed calls with gatekeeper(s). + +# 7 Overview + +The H.235.1 baseline, as well as the H.235.3 hybrid security profiles, apply a shared secret (after the first handshake) to assure message authentication and/or integrity in a hop-by-hop fashion using the gatekeeper as a trusted intermediate host. Using the direct-routed call model, a shared secret between two endpoints cannot be assumed. It is also not practical to use a pre-established shared secret to secure the communication since, in this case, all endpoints would have to know in advance which other endpoint will be called. + +ITU-T Rec. H.235.4 addresses the scenario shown in Figure 1, where endpoints are attached to a gatekeeper and deploy direct-routed call signalling. The scenario assumes an unsecured IP network in the gatekeeper zone. + +It is assumed that each endpoint has a communication relation and a security association with its gatekeeper, and that each endpoint has registered securely with the gatekeeper using either the baseline or the hybrid security profile. + +Hence, the gatekeeper of the initiating endpoint (DRC1) or the gatekeeper of the terminating endpoint (DRC2) is able to provide a shared secret for the directly communicating endpoints using a Kerberos-like approach (see RFC 4120). + +![Diagram of a direct-routed call scenario (Figure 1/H.235.4). It shows two endpoints, A and B, connected to two gatekeepers, G and H. Endpoint A is connected to Gatekeeper G via an H.225.0 RAS message. Endpoint B is connected to Gatekeeper H via an H.225.0 RAS message. Gatekeeper G and Gatekeeper H are connected to each other via an H.225.0 RAS message. Endpoint A and Endpoint B are connected to each other via an H.225.0/Q.931 Call Signalling message. A dashed line between Endpoint A and Endpoint B represents the RTP media stream. The diagram is labeled H.235.4_F01 at the bottom right.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +``` +graph TD + G[Gatekeeper G] <-->|H.225.0 RAS| H[Gatekeeper H] + A[Endpoint A] <-->|H.225.0 RAS| G + B[Endpoint B] <-->|H.225.0 RAS| H + A <-->|H.225.0/Q.931 Call Signalling| B + A -.->|RTP media| B + style G fill:#fff,stroke:#000 + style H fill:#fff,stroke:#000 + style A fill:#fff,stroke:#000 + style B fill:#fff,stroke:#000 +``` + +Diagram of a direct-routed call scenario (Figure 1/H.235.4). It shows two endpoints, A and B, connected to two gatekeepers, G and H. Endpoint A is connected to Gatekeeper G via an H.225.0 RAS message. Endpoint B is connected to Gatekeeper H via an H.225.0 RAS message. Gatekeeper G and Gatekeeper H are connected to each other via an H.225.0 RAS message. Endpoint A and Endpoint B are connected to each other via an H.225.0/Q.931 Call Signalling message. A dashed line between Endpoint A and Endpoint B represents the RTP media stream. The diagram is labeled H.235.4\_F01 at the bottom right. + +**Figure 1/H.235.4 – Direct-routed call scenario** + +This Recommendation features two procedures, DRC1 and DRC2, for different environments. + +Procedure DRC1 (see clause 9) is applicable in corporate environments where the gatekeepers are situated within different (local) sites but where the sites adhere to a common corporate security policy. In such an environment it is assumed acceptable that the originating gatekeeper G determines the effective security policy for a call to be established; thus the originating + +gatekeeper G selects and chooses the applied security parameters. The terminating gatekeeper H will accept the chosen security parameters. + +Procedures DRC2 (see clause 10) and DRC3 (clause 11) are applicable in interdomain environments where the gatekeepers are situated within different administrative domains where each domain may employ a different security policy. + +Procedure DRC2 is applicable in cases where the calling endpoint or the gatekeepers do not support the Diffie-Hellman algorithm. In such an environment it is assumed acceptable that the terminating gatekeeper H determines the effective security policy for a call to be established; thus the terminating gatekeeper H selects and chooses the applied security parameters. The originating gatekeeper G will accept the chosen security parameters. + +Procedure DRC3 is applicable in cases where the calling endpoint does not support the Diffie-Hellman algorithm while the Gatekeepers in the calling and called domain both support the Diffie-Hellman algorithm. + +At the beginning of call registration, the procedures provide signalling means to negotiate which of DRC1, DRC2 or DRC3 is to be applied. + +# 8 Limitations + +This Recommendation does not address direct-routed scenarios without any gatekeeper. This remains for further study. + +# 9 Procedure DRC1 (corporate environment) + +The procedure described in this clause is applicable in corporate environments where the gatekeepers are situated within different (local) sites but where the sites adhere to a common corporate security policy. In such an environment, it is assumed acceptable that the originating gatekeeper G determines the effective security policy for a call to be established; thus the originating gatekeeper selects and chooses the applied security parameters. The terminating gatekeeper H will accept the chosen security parameters. + +## 9.1 GRQ/RRQ phase + +Endpoints capable of supporting this security profile shall indicate this fact during **GRQ** and/or **RRQ** by including a separate ClearToken with **tokenOID** set to "I10"; any other fields in that ClearToken should not be used. The H.235.4-capable gatekeeper that is willing to provide this functionality shall reply with **GCF** or **RCF** with a separate ClearToken included with **tokenOID** set to "I10" and all other fields in the ClearToken unused. + +## 9.2 ARQ phase + +Before an endpoint A starts sending call signalling messages to another endpoint B directly, the endpoint A or B shall apply for admission at the gatekeeper G or H using **ARQ**. Endpoint A shall include within **ARQ** a separate ClearToken with **tokenOID** set to "I10" and all other fields in the ClearToken unused. + +## 9.3 LRQ phase + +This procedure covers the case of both a single, common gatekeeper to the endpoints and the case of multiple, chained gatekeepers. In the case of multiple involved gatekeepers, gatekeeper G, in which zone the call originates, should locate gatekeeper H using the (multicast) **LRQ** mechanism as described by ITU-T Rec. H.323 clause 8.1.6, "Optional called endpoint signalling". The communication between two gatekeepers shall be secured according to H.235.1. For this, it is assumed that a common shared secret $K_{GH}$ is available. Since **LRQ** among gatekeepers is typically + +a multicast message, the shared secret $K_{GH}$ typically cannot be a pair-wise shared secret but is assumed to be actually a group-based shared secret within the potential cloud of gatekeepers. + +NOTE – This assumption limits scalability in the general case, and does not allow source authentication. However, it is believed that in corporate networks, with a limited, small number of well-known gatekeepers, such constraint and security limitations are still acceptable. Securing inter-gatekeeper multicast communication using digital signatures could overcome those limitations: however, this remains for further study. + +If the **LRQ** mechanism is used to locate the far-end gatekeeper, then **LRQ** shall convey a separate ClearToken with **tokenOID** set to "I10"; any other fields in that ClearToken should not be used. For the multicast case, the **generalID** in the ClearToken of **LRQ** shall not be used. Intergatekeeper communication using H.501 and/or H.510 remains for further study. + +## 9.4 LCF phase + +$EK_{BH}$ denotes the encryption key and $KS_{BH}$ denotes the salting key that are shared between endpoint B and gatekeeper H. As is described below, both Gatekeeper H and endpoint B separately compute this keying material from the shared secret $K_{BH}$ using a PRF. + +Gatekeeper H shall generate a random Challenge-B, encryption key material $EK_{BH}$ and salting key material $KS_{BH}$ from the shared secret $K_{BH}$ using the PRF-based key derivation procedure as defined in clause 12 where Challenge-B is substituted as **challenge** and $CT_{HG} \rightarrow \mathbf{h235Key} \rightarrow \mathbf{secureSharedSecret} \rightarrow \mathbf{keyDerivationOID}$ shall hold "AnnexI-HMAC-SHA1-PRF", see clause 14. + +$EK_{GH}$ denotes the encryption key and $KS_{GH}$ denotes the salting key that are shared between gatekeeper G and gatekeeper H. Gatekeeper H shall generate one random Challenge-G. Gatekeeper H shall generate encryption key material $EK_{GH}$ and salting key material $KS_{GH}$ from the shared secret $K_{GH}$ using the PRF-based key derivation procedure as defined in clause 14 where Challenge-G is substituted for **challenge**. $CT_{HG} \rightarrow \mathbf{challenge}$ shall hold challenge-G, the endpoint ID of the endpoint B shall be set in $CT_{HG} \rightarrow \mathbf{h235Key} \rightarrow \mathbf{secureSharedSecret} \rightarrow \mathbf{generalID}$ . + +Gatekeeper H shall transmit the encrypted $EK_{BH}$ and the encrypted $KS_{BH}$ to gatekeeper G. The enhanced OFB (EOFB) encryption mode (see 8.4/H.235.6) shall be used with the secret, endpoint-specific salting key $KS_{GH}$ . Applicable encryption algorithms are (see Table 6/H.235.6): + +- DES (56 bit) in EOFB mode using OID "Y1": optional; +- 3DES (168 bit) in outer-EOFB mode using OID "Z1": optional; +- AES (128 bit) in EOFB mode using OID "Z2": default and recommended; +- RC2-compatible (56 bit) in EOFB mode using OID "X1": optional. + +For the EOFB encryption mode, gatekeeper H shall generate a random initial value IV. For OID "X1", OID "Y1" and OID "Z1" the IV has 64 bits and shall be conveyed within $CT_{HG} \rightarrow \mathbf{h235Key} \rightarrow \mathbf{secureSharedSecret} \rightarrow \mathbf{params} \rightarrow \mathbf{iv8}$ ; whereas the IV has 128 bits for OID "Z2" and shall be conveyed within $CT_{HG} \rightarrow \mathbf{h235Key} \rightarrow \mathbf{secureSharedSecret} \rightarrow \mathbf{params} \rightarrow \mathbf{iv16}$ . + +Gatekeeper H shall include $ENC_{EK_{GH}, KS_{GH}, IV}(EK_{BH})$ and $ENC_{EK_{GH}, KS_{GH}, IV}(KS_{BH})$ in ClearToken $CT_{HG}$ with **tokenOID** set to "I13". The obtained ciphertext $ENC_{EK_{GH}, KS_{GH}, IV}(EK_{BH})$ shall be conveyed in $CT_{HG} \rightarrow \mathbf{h235Key} \rightarrow \mathbf{secureSharedSecret} \rightarrow \mathbf{encryptedSessionKey}$ ; the obtained ciphertext $ENC_{EK_{GH}, KS_{GH}, IV}(KS_{BH})$ shall be conveyed in $CT_{HG} \rightarrow \mathbf{h235Key} \rightarrow \mathbf{secureSharedSecret} \rightarrow \mathbf{encryptedSaltingKey}$ . The encryption algorithm shall be indicated in $CT_{HG} \rightarrow \mathbf{h235Key} \rightarrow \mathbf{algorithmOID}$ ("X1", "Y1", "Z1" or "Z2"). Challenge-B shall be placed within $CT_{HG} \rightarrow \mathbf{h235Key} \rightarrow \mathbf{secureSharedSecret} \rightarrow \mathbf{clearSaltingKey}$ . $CT_{HG} \rightarrow \mathbf{generalID}$ shall be set to the gatekeeper identifier G whereas $CT_{HG} \rightarrow \mathbf{sendersID}$ shall be set to the gatekeeper identifier H. + +Challenge-B shall be conveyed to endpoint B by inclusion of a **profileInfo** within the **ClearToken** $CT_{HG} \rightarrow \text{profileInfo} \rightarrow \text{elementID} = 0$ that identifies this particular profile element; + +$CT_{HG} \rightarrow \text{profileInfo} \rightarrow \text{paramS}$ left unused and $CT_{HG} \rightarrow \text{profileInfo} \rightarrow \text{element} \rightarrow \text{octets}$ shall hold Challenge-B. + +The **LCF** response shall hold the **ClearToken** $CT_{HG}$ . + +## 9.5 ACF phase + +The gatekeeper G, recognizing that endpoints A and B support this Recommendation, shall generate key material and **ClearTokens** as specified below. + +The gatekeeper is able to calculate a call-based shared secret $K_{AB}$ , besides the normal **ARQ** operation. This call-based shared secret is then propagated to both endpoints using **ClearTokens**. Those **ClearTokens** are conveyed within the **ACF** message and are sent back to the caller. + +Two **ClearTokens** shall be included, one $CT_A$ for the caller A and another one $CT_B$ for the callee B. Each **ClearToken** shall contain an OID ("I11" or "I12") within **tokenOID** that indicates whether the token is destined for the caller (OID "I11" for $CT_A$ ) or for the callee (OID "I12" for $CT_B$ ). + +GK G shall decrypt $CT_{HG} \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{encryptedSessionKey}$ to obtain $EK_{BH}$ and shall decrypt $CT_{HG} \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{encryptedSaltingKey}$ to obtain $KS_{BH}$ . + +The **ClearToken** as defined in this Recommendation may be used in conjunction with other security profiles such as with H.235.1 or with H.235.3 that deploy **ClearTokens** as well. In such a case, **ClearToken** from this Recommendation shall use those other **ClearToken** fields too. For example, in order to use this Recommendation in conjunction with ITU-T Rec. H.235.1, the fields **timestamp**, **random**, **generalID**, **sendersID**, and **dhkey** shall be present and shall be used, as described by the H.235.1 security profiles. + +The gatekeeper ID (GKID) of gatekeeper G shall be placed within $CT_A \rightarrow \text{sendersID}$ and within $CT_B \rightarrow \text{sendersID}$ whereas $CT_A \rightarrow \text{generalID}$ shall hold the endpoint identifier of endpoint A and $CT_B \rightarrow \text{generalID}$ the endpoint identifier of endpoint B. + +Gatekeeper G shall generate salting key material $KS_{GH}$ and encryption key material $EK_{GH}$ from $K_{GH}$ using the PRF-based key derivation procedure as defined in clause 12 with **challenge** substituted by $CT_{HG} \rightarrow \text{challenge}$ . + +The encryption keys $EK_{AG}$ and $EK_{BH}$ for the encrypted end-to-end key $K_{AB}$ shall be derived from the shared secret between the gatekeeper and the endpoints ( $EK_{AG}$ or $EK_{BH}$ ) using the PRF-based key derivation procedure as defined in clause 12 where both $CT_A \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{keyDerivationOID}$ and $CT_B \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{keyDerivationOID}$ shall hold "AnnexI-HMAC-SHA1-PRF", see clause 14 and $CT_A \rightarrow \text{challenge}$ shall hold Challenge-A. + +Gatekeeper G shall copy Challenge-B from $CT_{HG} \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{clearSaltingKey}$ into $CT_B \rightarrow \text{challenge}$ . + +$CT_B \rightarrow \text{profileInfo}$ shall hold the profile element that was conveyed in $CT_{HG}$ **profileInfo** such that in the end endpoint B obtains Challenge-B. + +This session secret $K_{AB}$ shall be encrypted by $EK_{AG}$ (for CT destined to endpoint A) or by $EK_{BH}$ (for the CT destined to endpoint B) using an encryption algorithm. + +The enhanced OFB (EOFB) encryption mode (see 8.4/H.235.6) shall be used with the secret, endpoint-specific salting key $KS_{AG}$ or $KS_{BH}$ . Applicable encryption algorithms are (see Table 6/H.235.6): + +- DES (56 bit) in EOFB mode using OID "Y1": optional; + +- 3DES (168 bit) in outer-EOFB mode using OID "Z1": optional; +- AES (128 bit) in EOFB mode using OID "Z2": default and recommended; +- RC2-compatible (56 bit) in EOFB mode using OID "X1": optional. + +For the EOFB encryption mode, the gatekeeper G shall generate a random initial value IV. For OID "X1", OID "Y1" and OID "Z1" the IV has 64 bits and shall be conveyed within $CT_A \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{params} \rightarrow \text{iv8}$ and within $CT_B \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{params} \rightarrow \text{iv8}$ ; whereas the IV has 128 bits for OID "Z2" and shall be conveyed within $CT_A \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{params} \rightarrow \text{iv16}$ and within $CT_B \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{params} \rightarrow \text{iv16}$ . + +The obtained ciphertext $\text{ENC}_{\text{EK}_{\text{AG}}, \text{KS}_{\text{AG}}, \text{IV}(\text{K}_{\text{AB}})}$ shall be conveyed in $CT_A \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{encryptedSessionKey}$ and $\text{ENC}_{\text{EK}_{\text{BH}}, \text{KS}_{\text{BH}}, \text{IV}(\text{K}_{\text{AB}})}$ shall then be conveyed in $CT_B \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{encryptedSessionKey}$ . The encryption algorithm shall be indicated in $CT_A \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{algorithmOID}$ and in $CT_B \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{algorithmOID}$ ("X1", "Y1", "Z1" or "Z2"). + +For the ClearToken destined to endpoint A, the endpoint identifier of endpoint B ( $\text{EPID}_B$ ) shall be placed within $CT_A \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{generalID}$ . Likewise for the ClearToken destined to endpoint B, the endpoint identifier of endpoint A ( $\text{EPID}_A$ ) shall be placed within $CT_B \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{generalID}$ . + +For the EOFB encryption algorithms, **encryptedSaltingKey** shall not be used. + +The gatekeeper G shall include both ClearTokens $CT_A$ and $CT_B$ in the **ACF** towards endpoint A. + +## 9.6 SETUP phase + +Endpoint A shall identify $CT_A$ by inspection of the **tokenOID** "I11" within ClearToken. + +Endpoint A shall verify that the obtained $CT_A$ is fresh by checking the **timestamp**. Further security checks shall verify the **generalID** and **sendersID** of the ClearToken and **generalID** within **V3KeySyncMaterial**. If the received $CT_A$ was verified as being fresh, endpoint A shall retrieve the IV and compute $\text{EK}_{\text{AG}}$ and $\text{KS}_{\text{AG}}$ as described above for the gatekeeper G. Endpoint A shall decrypt the **encryptedSessionKey** information found within **secureSharedSecret** of $CT_A$ to obtain $\text{K}_{\text{AB}}$ . + +If the received $CT_A$ was verified as being fresh, endpoint A is able to send a SETUP message to endpoint B. This SETUP message includes $CT_B$ . The SETUP message shall be secured (authenticated and/or integrity protected) according to ITU-T Rec. H.235.1 or according to ITU-T Rec. H.235.3 using $\text{K}_{\text{AB}}$ as the applied shared secret. For this, **generalID** in the H.235.1 hashed ClearToken (not $CT_B$ !) shall not be used unless endpoint A has already an $\text{EPID}_B$ available (e.g., through configuration or memorized from former communication). If endpoint A uses an $\text{EPID}_B$ value for **generalID** in SETUP, then endpoint A shall accept the value of the **sendersID** in the returned call signalling message as the true $\text{EPID}_B$ . + +Endpoint B shall identify $CT_B$ by inspection of the **tokenOID** "I12" within ClearToken. + +Endpoint B shall verify that the obtained $CT_B$ is fresh by checking the **timestamp**. Further security checks shall verify the **sendersID** of the ClearToken and **generalID** within **secureSharedSecret**. If the received $CT_B$ was verified as being fresh, endpoint B shall retrieve Challenge-B from $CT_{\text{HG}} \rightarrow \text{profileInfo} \rightarrow \text{element} \rightarrow \text{octets}$ , and retrieve the IV and compute $\text{EK}_{\text{BH}}$ and $\text{KS}_{\text{BH}}$ , Challenge-B substituted as **challenge** in clause 12 as described above for the gatekeeper. Endpoint B shall decrypt the **encryptedSessionKey** information found within **secureSharedSecret** of $CT_B$ to obtain $\text{K}_{\text{AB}}$ . + +In the case where the $CT_B$ is verified as being fresh, endpoint B is able to proceed with the call signalling by replying with CALL-PROCEEDING, ALERTING or CONNECT etc., as appropriate. In the case where the $CT_B$ is found not to be fresh, or the security verification of the SETUP + +message failed, endpoint B shall reply with RELEASE-COMPLETE and the **ReleaseCompleteReason** set to a security error as defined by 11.1/H.235.0. + +When media security is to be deployed (see 6.1/H.235.6), endpoint A and endpoint B shall exchange Diffie-Hellman half-keys according to 8.5/H.235.6 and establish a dynamic session-based master key from which media-specific session keys can then be derived. + +Endpoint B shall include **generalID** set to $EPID_A$ and **sendersID** set to $EPID_B$ for protection of any H.225.0 Call signalling message destined to EP A (e.g., Call Proceeding, Alerting or Connect). + +Figure 2 shows the basic communication flow: + +![Sequence diagram showing the basic communication flow (DRC1) between Endpoint A, Gatekeeper G, Gatekeeper H, and Endpoint B. The diagram illustrates the exchange of RRQ, RCF, ARQ, LRQ, LCF, and ACF messages, along with the generation of cryptographic keys and tokens for security protection.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +H.235.1 Baseline or H.235.3 F Hybrid Security Profile deployed, by applying a shared secret $K_{AG}$ to the communication between endpoint A and the gatekeeper G. + +H.235.1 Baseline or H.235.3 Hybrid Security Profile deployed, by applying a shared secret $K_{GH}$ to the communication between gatekeeper G and the gatekeeper H. + +H.235.1 Baseline or H.235.3 Hybrid Security Profile deployed, by applying a shared secret $K_{BH}$ to the communication between endpoint B and the gatekeeper H. + +``` + +sequenceDiagram + participant A as Endpoint A + participant G as Gatekeeper G + participant H as Gatekeeper H + participant B as Endpoint B + + A->>G: RRQ, incl. ClearToken("I10") + G-->>A: RCF, incl. endpointIdentifier EPID_A, incl. ClearToken("I10") + A->>G: ARQ, incl. ClearToken("I10") + G->>H: LRQ, incl. ClearToken("I10") + Note over H: Generate salting key material KS_BH and encryption key material EK_BH from the shared secret K_BH using PRF. +Generate salting key material KS_GH and encryption key material EK_GH from the shared secret K_GH using PRF. +Include ENC_EKGH, KSGH, IV(EK_BH) and ENC_EKGH, KSGH, IV(KS_BH) in ClearToken CT_HG + H-->>G: LCF, incl. CT_HG("I13") + Note over G: Generate salting key material KS_AG and encryption key material EK_AG from the shared secret K_AG using PRF. +Generate salting key material KS_GH and encryption key material EK_GH from the shared secret K_GH using PRF. +Obtain EK_BH and KS_BH from CT_HG. +Generate shared secret K_AB and two ClearTokens CT_A and CT_B where CT_A conveys ENC_EKAG, KSAG, IV(K_AB), EPID_A and GKID_G and CT_B conveys ENC_EKBH, KSBH, IV(K_AB), EPID_B and GKID_G. + G-->>A: ACF, incl. CT_A("I11") and CT_B("I12") + Note over A: Generate salting key material KS_AG and encryption key material EK_AG from the shared secret K_AG using PRF. +Reception of CT_A to extract the EPID_B as well as decryption to obtain the shared secret K_AB to be applied to direct call signalling + A->>B: Setup integrity protected by K_AB containing hashed token, as defined for baseline and hybrid security profiles as well as the CT_B("I12") + Note over B: Generate salting key material KS_BH and encryption key material EK_BH from the shared secret K_BH using PRF. +Reception of CT_B to extract the EPID_A as well as decryption to obtain the shared secret K_AB to be applied to direct call signalling, security check of the received setup message. + B-->>A: Call Proceeding, Alerting, or Connect integrity protected by K_AB containing hashed token, as defined for baseline and hybrid security profiles with the generalID set to EPID_A and sendersID set to EPID_B + +``` + +Sequence diagram showing the basic communication flow (DRC1) between Endpoint A, Gatekeeper G, Gatekeeper H, and Endpoint B. The diagram illustrates the exchange of RRQ, RCF, ARQ, LRQ, LCF, and ACF messages, along with the generation of cryptographic keys and tokens for security protection. + +H.235.4\_F02 + +Figure 2/H.235.4 – Basic communication flow (DRC1) + +# 10 Procedure DRC2 (interdomain environment) + +The procedure described in this clause is applicable in interdomain environments where the gatekeepers are situated within different administrative domains and where each domain may employ a different security policy. Procedure DRC2 is applicable in cases where the calling endpoint or the gatekeepers do not support the Diffie-Hellman algorithm. + +In such an environment, it is assumed acceptable that the terminating gatekeeper H determines the effective security policy for a call to be established; thus the terminating gatekeeper H selects and chooses the applied security parameters. The originating gatekeeper G will accept the chosen security parameters. + +## 10.1 GRQ/RRQ phase + +Endpoints capable of supporting this security profile shall indicate this fact during **GRQ** and/or **RRQ** by including a separate ClearToken with **tokenOID** set to "I20"; any other fields in that ClearToken should not be used. The H.235.4-capable gatekeeper that is willing to provide this functionality shall reply with **GCF** or **RCF** with a separate ClearToken included with **tokenOID** set to "I20" and all other fields in the ClearToken unused. + +## 10.2 ARQ phase + +Before an endpoint A starts sending call signalling messages to another endpoint B directly, the endpoint A or B shall apply for admission at the gatekeeper G or H using **ARQ**. Endpoint A shall include within **ARQ** a separate ClearToken with **tokenOID** set to "I20" and all other fields in the ClearToken unused. + +## 10.3 LRQ phase + +This procedure covers the case of both a single, common gatekeeper to the endpoints and the case of multiple, chained gatekeepers. In the case of multiple involved gatekeepers, gatekeeper G, in which zone the call originates, should locate gatekeeper H using the (multicast) **LRQ** mechanism as described by ITU-T Rec. H.323 clause 8.1.6, "Optional called endpoint signalling". The communication between two gatekeepers shall be secured according to ITU-T Rec. H.235.1. For this, it is assumed that a common shared secret $K_{GH}$ is available. Since **LRQ** among gatekeepers is typically a multicast message, the shared secret $K_{GH}$ typically cannot be a pair-wise shared secret but is assumed to be actually a group-based shared secret within the potential cloud of gatekeepers. + +NOTE – This assumption limits scalability in the general case, and does not allow source authentication. However, it is believed that in corporate networks with a limited, small number of well-known gatekeepers, such constraint and security limitations are still acceptable. Securing inter-gatekeeper multicast communication using digital signatures could overcome those limitations: however, this remains for further study. + +If the **LRQ** mechanism is used to locate the far-end gatekeeper, then **LRQ** shall convey a separate ClearToken with **tokenOID** set to "I20"; any other fields in that ClearToken should not be used. For the multicast case, the **generalID** in the ClearToken of **LRQ** shall not be used. Inter-gatekeeper communication using H.501 and/or H.510 remains for further study. + +## 10.4 LCF phase + +The gatekeeper H, recognizing that endpoints A and B support this Recommendation, shall generate key material and ClearTokens in **LCF** as specified below. + +$K_{BH}$ denotes the shared secret that is shared between endpoint B and gatekeeper H. $EK_{BH}$ denotes the encryption key and $KS_{BH}$ denotes the salting key that are shared between endpoint B and gatekeeper H. Gatekeeper H generates one random Challenge-B. Gatekeeper H shall generate encryption key material $EK_{BH}$ from the shared secret $K_{BH}$ using the PRF-based key derivation + +procedure with Challenge-B substituted as **challenge** as defined in clause 12 where $CT_B \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow keyDerivationOID$ shall hold "AnnexI-HMAC-SHA1-PRF", see clause 14. + +Gatekeeper H shall generate a salting key $KS_{BH}$ from $K_{BH}$ using the PRF-based key derivation procedure as defined in clause 12 with Challenge-B substituted as **challenge**. + +$EK_{GH}$ denotes the encryption key and $KS_{GH}$ denotes the salting key that are shared between gatekeeper G and gatekeeper H. Gatekeeper H generates one random Challenge-G. Gatekeeper H shall generate encryption key material $EK_{GH}$ from the shared secret $K_{GH}$ using the PRF-based key derivation procedure with Challenge-G substituted as **challenge** as defined in clause 12 where $CT_{HG} \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow keyDerivationOID$ shall hold "AnnexI-HMAC-SHA1-PRF", see clause 14. + +Gatekeeper H shall generate $KS_{GH}$ from the shared secret $K_{GH}$ using the PRF-based key derivation procedure with Challenge-G substituted as **challenge** as defined in clause 12. + +Gatekeeper H creates two ClearTokens in the **LCF** message. One $CT_{HG}$ for the Gatekeeper G and a $CT_B$ for the callee B. $CT_{HG} \rightarrow tokenOID$ shall contain an OID "I23" whereas $CT_B \rightarrow tokenOID$ shall contain OID "I12". + +Challenge-G shall be set in $CT_{HG} \rightarrow challenge$ , the gatekeeper ID of the Gatekeeper H shall be set in $CT_{HG} \rightarrow sendersID$ , the gatekeeper ID of the Gatekeeper G (copied from the **LRQ**) shall be set in $CT_{HG} \rightarrow generalID$ . + +Challenge-B shall be set in $CT_B \rightarrow challenge$ , the gatekeeper ID of the Gatekeeper H shall be set in $CT_B \rightarrow sendersID$ , the endpoint ID of the endpoint B shall be set in $CT_B \rightarrow generalID$ . If the **LRQ** has the endpoint ID of endpoint A in **LRQ**'s endpointIdentifier field, Gatekeeper H shall copy it into $CT_B \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow generalID$ , and shall also copy it into $CT_{HG} \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow generalID$ too. + +The **LCF** response shall hold the ClearToken $CT_{HG}$ and $CT_B$ if Gatekeeper H and endpoint B support DRC2 of this Recommendation too. + +Gatekeeper G having received the **LCF** message from Gatekeeper H, checks the ClearToken $CT_B$ and $CT_{HG}$ . Gatekeeper G uses Challenge-G as **challenge** and the PRF as in clause 12 to compute $KS_{GH}$ and $EK_{GH}$ from $K_{GH}$ and then to decrypt $CT_{HG} \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow encryptedSessionKey$ and obtains the $K_{AB}$ shared by endpoints A and B. + +## 10.5 ACF phase + +The gatekeeper H calculates a call-based shared secret $K_{AB}$ that is shared by endpoints A and B. This call-based shared secret is then propagated to both endpoints using ClearTokens. The ClearToken is first sent back to the originating gatekeeper G and then Gatekeeper G conveys the information within the **ACF** message back to the caller. + +Gatekeeper H shall encrypt the $K_{AB}$ by $EK_{GH}$ as $ENC_{EK_{GH}, KS_{GH}, IV(K_{AB})}$ and put the encrypted $K_{AB}$ into $CT_{HG} \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow encryptedSessionKey$ . + +The enhanced OFB (EOFB) encryption mode (see 8.4/H.235.6) shall be used with the secret, endpoint-specific salting key $KS_{GH}$ . Applicable encryption algorithms are (see Table 6/H.235.6): + +- DES (56 bit) in EOFB mode using OID "Y1": optional; +- 3DES (168 bit) in outer-EOFB mode using OID "Z1": optional; +- AES (128 bit) in EOFB mode using OID "Z2": default and recommended; +- RC2-compatible (56 bit) in EOFB mode using OID "X1": optional. + +For the EOFB encryption mode, Gatekeeper H shall generate a random initial value IV. For OID "X1", OID "Y1" and OID "Z1" the IV has 64 bits and shall be conveyed within $CT_{HG} \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow params \rightarrow iv8$ ; whereas the IV has 128 bits for OID "Z2" and shall be conveyed within $CT_{HG} \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow params \rightarrow iv16$ . + +The encryption algorithm shall be indicated in $CT_{HG} \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow algorithmOID$ ("X1", "Y1", "Z1" or "Z2"). For the EOFB encryption algorithms, **encryptedSaltingKey** shall not be used. + +Likewise, Gatekeeper H shall encrypt the $K_{AB}$ by $EK_{BH}$ as $ENC_{EK_{BH}, KS_{BH}, IV(K_{AB})}$ and put that encrypted $K_{AB}$ into $CT_B \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow encryptedSessionKey$ . + +The enhanced OFB (EOFB) encryption mode (see 8.4/H.235.6) shall be used with the secret, endpoint-specific salting key $KS_{BH}$ for endpoint B ( $CT_B$ ). Applicable encryption algorithms are (see Table 6/H.235.6): + +- DES (56 bit) in EOFB mode using OID "Y1": optional; +- 3DES (168 bit) in outer-EOFB mode using OID "Z1": optional; +- AES (128 bit) in EOFB mode using OID "Z2": default and recommended; +- RC2-compatible (56 bit) in EOFB mode using OID "X1": optional. + +For the EOFB encryption mode, Gatekeeper H shall generate a random initial value IV. For OID "X1", OID "Y1" and OID "Z1" the IV has 64 bits and shall be conveyed within $CT_B \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow params \rightarrow iv8$ ; whereas the IV has 128 bits for OID "Z2" and shall be conveyed within $CT_B \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow params \rightarrow iv16$ . + +The encryption algorithm shall be indicated in $CT_B \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow algorithmOID$ ("X1", "Y1", "Z1" or "Z2"). For the EOFB encryption algorithms, **encryptedSaltingKey** shall not be used. + +For the **ACF** response to endpoint A, two ClearTokens shall be included, one $CT_A$ for the caller A and another one $CT_B$ for the callee B. **ClearToken** $CT_A \rightarrow tokenOID$ shall contain an OID "I11". + +Gatekeeper G generates one Challenge-A, and generates encryption key material $EK_{AG}$ from the shared secret $K_{AG}$ using the PRF-based key derivation procedure with Challenge-A substituted as **challenge** using the PRF-based key derivation procedure as defined in clause 12 where $CT_A \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow keyDerivationOID$ shall hold "AnnexI-HMAC-SHA1-PRF", see clause 14 and sets $CT_A \rightarrow challenge$ to Challenge-A. + +Gatekeeper G shall encrypt $K_{AB}$ by $EK_{AG}$ as $ENC_{EK_{AG}, KS_{AG}, IV(K_{AB})}$ using an encryption algorithm and put the encrypted $K_{AB}$ into $CT_A \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow encryptedSessionKey$ . + +The enhanced OFB (EOFB) encryption mode (see 8.4/H.235.6) shall be used with the secret, endpoint-specific salting key $KS_{AG}$ . Applicable encryption algorithms are (see Table 6/H.235.6): + +- DES (56 bit) in EOFB mode using OID "Y1": optional; +- 3DES (168 bit) in outer-EOFB mode using OID "Z1": optional; +- AES (128 bit) in EOFB mode using OID "Z2": default and recommended; +- RC2-compatible (56 bit) in EOFB mode using OID "X1": optional. + +For the EOFB encryption mode, the GK G shall generate a random initial value IV. For OID "X1", OID "Y1" and OID "Z1" the IV has 64 bits and shall be conveyed within $CT_A \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow params \rightarrow iv8$ ; whereas the IV has 128 bits for OID "Z2" and shall be conveyed within $CT_A \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow params \rightarrow iv16$ . The encryption algorithm shall be indicated in $CT_A \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow algorithmOID$ ("X1", "Y1", "Z1" or "Z2"). + +The gatekeeper ID of the Gatekeeper G shall be set in CTA→**sendersID**, the endpoint ID of the endpoint A shall be set in CTA→**generalID**. The endpoint ID of endpoint B shall be copied from CTB→**generalID** into CTA→**h235Key**→**secureSharedSecret**→**generalID**. + +If Gatekeeper G has not filled the endpoint ID of endpoint A in **LRQ's** endpointIdentifier field before, Gatekeeper G shall fill the endpoint ID of endpoint A into CTB→**h235Key**→**secureSharedSecret**→**generalID**. + +For the EOFB encryption algorithms, **encryptedSaltingKey** shall not be used. + +The **ClearToken**, as defined in this Recommendation, may be used in conjunction with other security profiles such as H.235.1 or H.235.3 that deploy ClearTokens as well. In such a case, the ClearToken of this Recommendation shall use those other **ClearToken** fields too. For example, in order to use this Recommendation in conjunction with ITU-T Rec. H.235.1, the fields **timestamp**, **random**, **generalID**, **sendersID**, and **dhkey** shall be presented and shall be used, as described by the H.235.1 security profiles. + +The gatekeeper ID (GKID) of gatekeeper G shall be placed within CTA→**sendersID** whereas CTA→**generalID** shall hold the endpoint identifier of endpoint A. + +Endpoint A shall identify CTA by inspection of the CTA→**tokenOID** "I21". Endpoint A shall verify that the obtained CTA is fresh by checking the **timestamp**. Further security checks shall verify the **generalID** and **sendersID** of the ClearToken and **generalID** within **secureSharedSecret**. If the received CTA was verified as being fresh, endpoint A shall retrieve the IV and compute EKAG and KSAG as described above for the gatekeeper G using CTA→**challenge** as Challenge-A substituted as **challenge** within clause 12. Endpoint A shall decrypt CTA→**h235Key**→**secureSharedSecret**→**encryptedSessionKey** to obtain KAB. + +## 10.6 SETUP phase + +Endpoint A shall identify CTA by inspection of the CTA→**tokenOID** "I11". Endpoint A shall verify that the obtained CTA is fresh by checking the **timestamp**. Further security checks shall verify the **generalID** and **sendersID** of the ClearToken and **generalID** within **secureSharedSecret**. If the received CTA was verified as being fresh, endpoint A shall retrieve the IV and compute EKAG and KSAG as described above for the gatekeeper G using CTA→**challenge** as Challenge-A. Endpoint A shall decrypt CTA→**h235Key**→**secureSharedSecret**→**encryptedSessionKey** to obtain KAG. + +If the received CTA is verified as being fresh, endpoint A is able to send a SETUP message to endpoint B. This SETUP message includes CTB. The SETUP message shall be secured (authenticated and/or integrity protected) according to ITU-T Rec. H.235.1 or ITU-T Rec. H.235.3 using KAB as the applied shared secret. For this, **generalID** in the H.235.1 hashed ClearToken (not CTB!) shall not be used unless endpoint A already has an EPIDB available (e.g., through configuration or memorized from former communication). If endpoint A uses an EPIDB value for **generalID** in SETUP, then endpoint A shall accept the value of the **sendersID** in the returned call signalling message as the true EPIDB. + +Endpoint B shall identify CTB by inspection of the **tokenOID** "I12" within ClearToken. + +Endpoint B shall verify that the obtained CTB is fresh by checking the **timestamp**. Further security checks shall verify the **sendersID** of the ClearToken and **generalID** within **secureSharedSecret**. If the received CTB was verified as being fresh, endpoint B shall retrieve the IV, compute EKBH and KSBH, using CTB→**challenge** as Challenge-B substituted as **challenge** in clause 12 as described above for the gatekeeper H. Endpoint B shall decrypt CTB→**h235Key**→**secureSharedSecret**→**encryptedSessionKey** to obtain KAB. + +In the case where the CTB is verified as being fresh, endpoint B is able to proceed the call signalling by replying with CALL-PROCEEDING, ALERTING or CONNECT etc., as appropriate. In the case where the CTB is found not to be fresh, or the security verification of the SETUP message fails, + +endpoint B shall reply with RELEASE-COMPLETE and the **ReleaseCompleteReason** set to a security error as defined by 11.1/H.235.0. + +When media security is to be deployed (see 6.1/H.235.6), endpoint A and endpoint B shall exchange Diffie-Hellman half-keys according to 8.5/H.235.6 and establish a dynamic session-based master key from which media-specific session keys can then be derived. + +Endpoint B shall include **generalID** set to EPIDA and **sendersID** set to EPIDB for protection of any H.225.0 Call signalling message destined to EP A (e.g., Call Proceeding, Alerting or Connect). + +Figure 3 shows the basic communication flow: + +![Sequence diagram showing the basic communication flow (DRC2) between Endpoint A, Gatekeeper G, Gatekeeper H, and Endpoint B. The diagram illustrates the exchange of messages for registration, key derivation, and call signaling under different security profiles.](10781f43062bf3e9601a1e086710556c_img.jpg) + +The diagram illustrates the basic communication flow (DRC2) between Endpoint A, Gatekeeper G, Gatekeeper H, and Endpoint B. The sequence of messages and internal operations is as follows: + +- Endpoint A** sends an **RRQ** (incl. ClearToken("I20")) to **Gatekeeper G**. +- Gatekeeper G** responds with an **RCF** (incl. endpointIdentifier *EPIDA*, incl. ClearToken("I20")) to **Endpoint A**. +- Endpoint A** sends an **ARQ** (incl. ClearToken("I20")) to **Gatekeeper G**. +- Gatekeeper G** sends an **LRQ** (incl. ClearToken("I20")) to **Gatekeeper H**. +- Gatekeeper H** sends an **RRQ** (incl. ClearToken("I20")) to **Endpoint B**. +- Endpoint B** responds with an **RCF** (incl. endpointIdentifier *EPIDB*, incl. ClearToken("I20")) to **Gatekeeper H**. +- Gatekeeper H** sends an **LCF** (incl. CTB("I12"), CTHG("I23")) to **Gatekeeper G**. +- Gatekeeper G** sends an **ACF** (incl. CTA("I11") and CTB("I12")) to **Endpoint A**. +- Endpoint A** performs internal key derivation and message creation (detailed in a box). +- Endpoint A** sends a **Setup** message (integrity protected by *KAB*) to **Endpoint B**. +- Endpoint B** performs internal key derivation and security check (detailed in a box). +- Endpoint B** sends a **Call Proceeding, Alerting, or Connect** message (integrity protected by *KAB*) to **Endpoint A**. + +Security profile notes at the top of the diagram: + +- Endpoint A / Gatekeeper G:** H.235.1 Baseline or H.235.3 Hybrid Security Profile deployed, by applying a shared secret *KAG* to the communication between endpoint A and the gatekeeper G. +- Gatekeeper G / Gatekeeper H:** H.235.1 Baseline or H.235.3 Hybrid Security Profile deployed, by applying a shared secret *KGH* to the communication between gatekeeper G and the gatekeeper H. +- Gatekeeper H / Endpoint B:** H.235.1 Baseline or H.235.3 Hybrid Security Profile deployed, by applying a shared secret *KBH* to the communication between endpoint B and the gatekeeper H. + +Internal operations for **Endpoint A** (receiving ACF): + +- Generate salting key material *KSGH* and encryption key material *EKGH* from the shared secret *KGH* using PRF. +- Generate salting key material *KSAG* and encryption key material *EKAG* from the shared secret *KAG* using PRF. +- Obtain *KAB* from CTHG. +- Generate ClearToken CTA where CTA conveys ENCEKAG, KSAG, II(KAB), GKIDG and EPIDA. +- Copy CTB from the LCF into ACF. + +Internal operations for **Endpoint A** (preparing Setup): + +- Generate salting key material *KSAG* and encryption key material *EKAG* from the shared secret *KAG* using PRF. +- Reception of CTA to extract the EPIDB as well as decryption to obtain the shared secret *KAB* to be applied to direct call signalling. +- Create Setup message with CTB in it. + +Internal operations for **Gatekeeper H** (receiving RCF): + +- Generate salting key material *KSBH* and encryption key material *EKBH* from the shared secret *KBH* using PRF. +- Generate shared secret *KAB* and CTB where CTB conveys ENCEKBH, KSBH, II(KAB), EPIDB and GKIDH. +- Generate salting key material *KSGH* and encryption key material *EKGH* from the shared secret *KGH* using PRF. +- Generate CTHG where CTHG conveys ENCEKGH, KSGH, II(KAB), GKIDH and GKIDG. + +Internal operations for **Endpoint B** (receiving Setup): + +- Generate salting key material *KSBH* and encryption key material *EKBH* from the shared secret *KBH* using PRF. +- Reception of CTB to extract the EPIDA as well as decryption to obtain the shared secret *KAB* to be applied to direct call signalling, security check of the received setup message. + +Sequence diagram showing the basic communication flow (DRC2) between Endpoint A, Gatekeeper G, Gatekeeper H, and Endpoint B. The diagram illustrates the exchange of messages for registration, key derivation, and call signaling under different security profiles. + +H.235.4\_F03 + +Figure 3/H.235.4 – Basic communication flow (DRC2) + +# 11 Procedure DRC3 (interdomain environment) + +The procedure described in this clause is applicable in interdomain environments and where the calling endpoint does not support the Diffie-Hellman algorithm while the Gatekeepers in the calling and called domain both are capable of computing DH exchange. In such an environment, the session key is computed by exchanging DH parameters between originating gatekeeper and terminating gatekeeper. + +## 11.1 GRQ/RRQ phase + +The scenario covers multiple, chained gatekeepers. Endpoints capable of supporting this security profile shall indicate this fact during **GRQ** and/or **RRQ** by including a separate ClearToken with **tokenOID** set to "I30"; any other fields in that ClearToken are unused. The H.235.4-capable gatekeeper that is willing to provide this functionality shall reply with **GCF** or **RCF** with a separate ClearToken included with **tokenOID** set to "I30" and all other fields in the ClearToken unused. + +## 11.2 ARQ phase + +Before EP A calls EP B using DRC3, EP A sends an **ARQ** message to GK G and the **ARQ** message contains a separate ClearToken with **tokenOID** set to "I30" and other fields unused. + +## 11.3 LRQ phase + +On the reception of the **ARQ** message sent by EP A, GK G sends **LRQ** to GK H to inquire EP B's address since EP B does not belong to GK G's domain. GK G checks the ClearToken carried by the **ARQ** message finding that **tokenOID** is set to "I30", if GK G supports the DH algorithm, then it applies some pre-configured rules which determine that DRC3 should be chosen. + +Then GK G generates a **LRQ** message containing a ClearToken (within the CryptoHashedToken) with its **tokenOID** set to "I30" to indicate to GK H that a DH key negotiation is needed. The **dhkey** field of the ClearToken is filled with the caller's DH parameters ( $g, p, g^x$ ) generated by GK G and other fields are unused. + +GK G then sends this **LRQ** message to GK H. In the case of GK cloud, GK G sends the **LRQ** message to its immediately neighbouring GK which in turn forwards the **LRQ** message to its own immediately neighbouring GK. The forwarding process continues until the **LCF** message finally reaches GK H. + +For the multicast case, the **generalID** in the CryptoToken of **LRQ** shall not be used. If GK G was not able to locate the far-end endpoint B then GK G shall return **ARJ** to endpoint A. The communication between two gatekeepers shall be secured according to ITU-T Rec. H.235.1. + +If GK G does not support the profile, GK G is free to choose whether to fall back to DRC2, or return **ARJ** to endpoint A. If DRC2 is chosen, all subsequent phases including the **LRQ** phase are the same as those of DRC2. + +## 11.4 LCF phase + +After receiving the **LRQ** message from GK G, the GK H, recognizing that both endpoint A and B support this procedure, shall generate the session key $K_{AB}$ as specified below. + +Firstly, GK H produces a random Challenge-B, which shall be set to $CT_B \rightarrow \text{challenge}$ and $CT_B \rightarrow \text{h235Key} \rightarrow \text{secureSharedSecret} \rightarrow \text{keyDerivationOID}$ shall hold "AnnexI-HMAC-SHA1-PRF", and then uses the shared key $K_{GH}$ and the Challenge-B to derive the key material $EK_{GH}$ and the salting key $KS_{GH}$ using PRF-based key derivation procedure. + +Challenge-B shall be set in $CT_B \rightarrow \text{challenge}$ , the gatekeeper ID of the GK H shall be set in $CT_B \rightarrow \text{sendersID}$ , the endpoint ID of the EP B shall be set in $CT_B \rightarrow \text{generalID}$ . If **LRQ** has the endpoint ID of EP A in **LRQ**'s endpoint Identifier field, Gatekeeper H shall copy it into + +CTB→**h235Key**→**secureSharedSecret**→**generalID**, and shall also copy it into CTHG→**h235Key**→**secureSharedSecret**→**generalID** too. + +GK H then creates two ClearTokens in the **LCF** message. One CTHG for GK G whose **tokenOID** is set to "I33" and one CTB for EP B whose **tokenOID** is set to "I12". GK H generates the callee's DH parameters ( $g, p, g^y$ ). With the caller's DH parameters obtained from the **LRQ** message, GK H shall compute the session key $K_{AB} = g^{xy} \bmod p$ . + +Finally, GK H shall encrypt $K_{AB}$ using $EK_{BH}$ and $KS_{BH}$ as $ENC_{EK_{BH}, KS_{BH}, IV(K_{AB})}$ and put the encrypted $K_{AB}$ into CTB→**h235Key**→**secureSharedSecret**→**encryptedSessionKey**, and puts the callee's DH parameters into **dhkey** of CTHG. + +The enhanced OFB (EOFB) encryption mode (see 8.4/H.235.6) shall be used with the secret, endpoint-specific salting key $KS_{GH}$ . Applicable encryption algorithms are (see Table 6/H.235.6): + +- DES (56 bit) in EOFB mode using OID "Y1": optional; +- 3DES (168 bit) in outer-EOFB mode using OID "Z1": optional; +- AES (128 bit) in EOFB mode using OID "Z2": default and recommended; +- RC2-compatible (56 bit) in EOFB mode using OID "X1": optional. + +For the EOFB encryption mode, Gatekeeper H shall generate a random initial value IV. For OID "X1", OID "Y1" and OID "Z1" the IV has 64 bits and shall be conveyed within CTB→**h235Key**→**secureSharedSecret**→**params**→**iv8**; whereas the IV has 128 bits for OID "Z2" and shall be conveyed within CTB→**h235Key**→**secureSharedSecret**→**params**→**iv16**. + +The encryption algorithm shall be indicated in CTB→**h235Key**→**secureSharedSecret**→**algorithmOID** ("X1", "Y1", "Z1" or "Z2"). For the EOFB encryption algorithms, **encryptedSaltingKey** shall not be used. + +GK H sends the **LCF** message to GK G. If GK cloud is present, the **LCF** message is transferred in a relay manner. Along this path, each GK receives the **LCF** message from its upstream immediate neighbour and checks the **LCF** message containing CTHG and forwards the **LCF** message to its downstream immediate neighbour. + +If GK H does not support the DH algorithm, or security policy is not allowed for DRC3, a fallback to DRC2 will occur. Therefore, the **LCF** phase and all the subsequent phases are the same as those of DRC2. + +## 11.5 ACF phase + +After receiving the **LCF** message, GK G, recognizing **tokenOID** in the separate ClearToken is set to "I33", obtains callee's DH and creates a ClearToken denoted CTA with its **tokenOID** set to "I11" by means specified below. + +Firstly, GK G produces a random Challenge-A, which shall be set to CTA→**challenge** and CTA→**h235Key**→**secureSharedSecret**→**keyDerivationOID** shall hold "AnnexI-HMAC-SHA1-PRF", and then uses the shared key $K_{AG}$ and the Challenge-A to derive the key material $EK_{AG}$ and the salting key $KS_{AG}$ using PRF-based key derivation procedure. + +Secondly, GK G uses caller's DH parameters which are retained in the **LRQ** phase and, in conjunction with callee's DH parameters, computes the session key $K_{AG} = g^{xy} \bmod p$ . + +Then GK G copies the ClearToken CTB from the **LCF** message to the **ACF** message whose **tokenOID** is set to "I12". + +Finally, GK G encrypts $K_{AB}$ using $EK_{AG}$ and $KS_{AG}$ as $ENC_{EK_{AG}, KS_{AG}, IV(K_{AB})}$ and puts the encrypted $K_{AB}$ into CTA→**h235Key**→**secureSharedSecret**→**encryptedSessionKey**, and copies CTB from the **LCF** message into the **ACF** message. + +The enhanced OFB (EOFB) encryption mode (see 8.4/H.235.6) shall be used with the secret, endpoint-specific salting key $KS_{AG}$ . + +Applicable encryption algorithms are (Table 6/H.235.6): + +- DES (56 bit) in EOFB mode using OID "Y1": optional; +- 3DES (168 bit) in outer-EOFB mode using OID "Z1": optional; +- AES (128 bit) in EOFB mode using OID "Z2": default and recommended; +- RC2-compatible (56 bit) in EOFB mode using OID "X1": optional. + +For the EOFB encryption mode, the GK G shall generate a random initial value IV. For OID "X1", OID "Y1" and OID "Z1" the IV has 64 bits and shall be conveyed within $CT_A \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow params \rightarrow iv8$ ; whereas the IV has 128 bits for OID "Z2" and shall be conveyed within $CT_A \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow params \rightarrow iv16$ . The encryption algorithm shall be indicated in $CT_A \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow algorithmOID$ ("X1", "Y1", "Z1" or "Z2"). + +If it is found that the ClearToken (within **LCF**) **tokenOID** is "I23", it can be judged that a fallback to DRC2 has occurred, and GK G is free to choose whether to accept GK H's security policy. If it accepts, the **ACF** phase and the subsequent Setup phase will be the same as those of DRC2. Otherwise, respond with a corresponding reject message indicating security failure by setting the reject reason to **securityDenial**. + +GK G sends the **ACF** message to EP A. + +## 11.6 SETUP phase + +Endpoint A shall identify $CT_A$ by inspection of the $CT_A \rightarrow tokenOID$ "I11". Endpoint A shall verify that the obtained $CT_A$ is fresh by checking the timestamp. Further security checks shall verify the **generalID** and **sendersID** of the ClearToken and **generalID** within **secureSharedSecret**. If the received $CT_A$ is verified as being fresh, endpoint A shall retrieve the IV and compute $EK_{AG}$ and $KS_{AG}$ as described above for the gatekeeper G using $CT_A \rightarrow challenge$ as Challenge-A. Endpoint A shall decrypt $CT_A \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow encryptedSessionKey$ to obtain $K_{AG}$ . + +If the received $CT_A$ is verified as being fresh, endpoint A is able to send a SETUP message to endpoint B. This SETUP message includes $CT_B$ . The SETUP message shall be secured (authenticated and/or integrity protected) according to ITU-T Rec. H.235.1 or ITU-T Rec. H.235.3 using $K_{AB}$ as the applied shared secret. For this, **generalID** in the H.235.1 hashed ClearToken (not $CT_B$ !) shall not be used unless endpoint A already has an $EPID_B$ available (e.g., through configuration or memorized from former communication). If endpoint A uses an $EPID_B$ value for **generalID** in SETUP, then endpoint A shall accept the value of the **sendersID** in the returned call signalling message as the true $EPID_B$ . + +Endpoint B shall identify $CT_B$ by inspection of the **tokenOID** "I12" within ClearToken. + +Endpoint B shall verify that the obtained $CT_B$ is fresh by checking the timestamp. Further security checks shall verify the **sendersID** of the ClearToken and **generalID** within **secureSharedSecret**. If the received $CT_B$ is verified as being fresh, endpoint B shall retrieve the IV, compute $EK_{BH}$ and $KS_{BH}$ , using $CT_B \rightarrow challenge$ as Challenge-B. Endpoint B shall decrypt $CT_B \rightarrow h235Key \rightarrow secureSharedSecret \rightarrow encryptedSessionKey$ to obtain $K_{AB}$ . + +In the case where the $CT_B$ is verified as being fresh, endpoint B is able to proceed the call signalling by replying with CALL-PROCEEDING, ALERTING or CONNECT etc., as appropriate. In the case where the $CT_B$ is found not to be fresh, or the security verification of the SETUP message fails, endpoint B shall reply with RELEASE-COMPLETE and the **ReleaseCompleteReason** set to a security error as defined by 11.1/H.235.0. + +When media security is to be deployed (see 6.1/H.235.6), endpoint A and endpoint B shall exchange Diffie-Hellman half-keys according to 8.5/H.235.6 and establish a dynamic session-based master key from which media-specific session keys can then be derived. + +Endpoint B shall include **generalID** set to EPIDA and **sendersID** set to EPIDB for protection of any H.225.0 Call signalling message destined to EP A (e.g., Call Proceeding, Alerting or Connect). + +Figure 4 shows the basic communication flow: + +![Figure 4/H.235.4 – Communication flow in DRC3. A sequence diagram showing the interaction between Endpoint A, Gatekeeper G, Gatekeeper H, and Endpoint B. It details the exchange of registration and admission messages (RRQ, RCF, ARQ), location requests (LRQ, LCF), and admission confirmation (ACF) including Diffie-Hellman key exchange parameters and encrypted tokens. Finally, it shows the Setup and Call Proceeding messages between endpoints protected by the established session key K_AB.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant A as Endpoint A + participant G as Gatekeeper G + participant H as Gatekeeper H + participant B as Endpoint B + + Note over A, G: H.235.1 Baseline or H.235.3 Hybrid Security Profile deployed, by applying a shared secret K_AG to the communication between endpoint A and the gatekeeper G. + Note over G, H: H.235.1 Baseline or H.235.3 Hybrid Security Profile deployed, by applying a shared secret K_GH to the communication between gatekeeper G and the gatekeeper H. + Note over H, B: H.235.1 Baseline or H.235.3 Hybrid Security Profile deployed, by applying a shared secret K_BH to the communication between endpoint B and the gatekeeper H. + + A->>G: RRQ, incl. ClearToken("I30") + G-->>A: RCF, incl. endpointIdentifier EPID_A, incl. ClearToken("I30") + A->>G: ARQ, incl. ClearToken("I30") + Note right of G: Generate a DH-half-key(g^a mod p) +Include g^a mod p in ClearToken("I30") + G->>H: LRQ, incl. ClearToken("I30") + Note right of H: Generate a DH-half-key(g, g^b mod p) +Compute shared secret key K_AB = g^ab mod p +Include ENC_EKBH, KSBH, IV(K_AB) in ClearToken CT_B +Include g, g^b mod p in ClearToken CT_HG + H-->>G: LCF, incl. CT_B("I12"), CT_HG("I33") + Note right of G: Compute shared secret key K_AB = g^ab mod p +Include ENC_EKAG, KSAG, IV(K_AB) in ClearToken CT_A +Copy CT_B from the LCF into ACF +and CT_B conveys ENC_EKBH, KSBH, IV(K_AB) + G-->>A: ACF, incl. CT_A("I11") and CT_B("I12") + Note left of A: Generate salting key material KS_AG and encryption key material EK_AG from the shared secret K_AG using PRF. +Reception of CT_A to extract the EPID_B as well as decryption to obtain the shared secret K_AB to be applied to direct call signalling. +Create Setup message with CT_B in it. + A->>B: Setup integrity protected by K_AB containing hashed token, as defined for baseline and hybrid security profiles as well as the CT_B("I12") + Note right of B: Generate salting key material KS_BH and encryption key material EK_BH from the shared secret K_BH using PRF. +Reception of CT_B to extract the EPID_A as well as decryption to obtain the shared secret K_AB to be applied to direct call signalling, security check of the received setup message. + B->>A: Call Proceeding, Alerting, or Connect integrity protected by K_AB containing hashed token, as defined for baseline and hybrid security profiles with the generalID set to EPID_A and sendersID set to EPID_B + +``` + +H.235.4\_F04 + +Figure 4/H.235.4 – Communication flow in DRC3. A sequence diagram showing the interaction between Endpoint A, Gatekeeper G, Gatekeeper H, and Endpoint B. It details the exchange of registration and admission messages (RRQ, RCF, ARQ), location requests (LRQ, LCF), and admission confirmation (ACF) including Diffie-Hellman key exchange parameters and encrypted tokens. Finally, it shows the Setup and Call Proceeding messages between endpoints protected by the established session key K\_AB. + +Figure 4/H.235.4 – Communication flow in DRC3 + +# 12 PRF-based key derivation procedure + +This clause describes a procedure that defines how to derive key material from the shared secret and other parameters. + +The procedure in this clause allows computing an encryption key and a salting key from a shared key. The procedure is uniform irrespective of the shared secret ( $K_{AG}$ , $K_{BH}$ or $K_{GH}$ ). + +In order to obtain the target keying material (e.g., $EK_{AG}$ ), the PRF (see clause 10/H.235.0) shall be used with the parameters taken from Table 1 where the *inkey* parameter is set to the corresponding shared key (e.g., $K_{AG}$ ), and *label* shall be set to the corresponding constant (e.g., 0x2AD01C64 || **challenge-A**) where || denotes concatenation. The *outkey\_len* shall be set to the length of the required length of the target key material which depends on the chosen encryption algorithm. + +NOTE – For $EK_{AG}$ , $KS_{AG}$ , $EK_{BH}$ and $KS_{BH}$ the 32-bit constant integers (i.e., 0x2AD01C64 etc.) are taken from the decimal digits of $e$ (i.e., 2.71828...), and for $EK_{GH}$ and $KS_{GH}$ , the 32-bit constants integers are taken from the decimal digits of $\pi$ (i.e., 3.14159...). For $EK_{AG}$ , $EK_{BH}$ , $KS_{AG}$ , and $KS_{BH}$ , the 32-bit integers are from blocks of 9 decimal digits, respectively the first, second, fourth and seventh blocks. The value for $EK_{GH}$ comes from the first 10 decimal digits of $\pi$ , while $KS_{GH}$ comes from the subsequent 8 decimal digits of $\pi$ . + +**Table 1/H.235.4 – Calculating encryption and salting keys from a shared secret** + +| Target Key | PRF inkey | Constant challenge | +|------------|-----------|----------------------------------| +| $EK_{AG}$ | $K_{AG}$ | 0x2AD01C64 Challenge-A | +| $KS_{AG}$ | $K_{AG}$ | 0x150533E1 Challenge-A | +| $EK_{BH}$ | $K_{BH}$ | 0x1B5C7973 Challenge-B | +| $KS_{BH}$ | $K_{BH}$ | 0x39A2C14B Challenge-B | +| $EK_{GH}$ | $K_{GH}$ | 0x54655307 Challenge-G | +| $KS_{GH}$ | $K_{GH}$ | 0x35855C60 Challenge-G | + +# 13 FIPS-140-based key derivation procedure + +This clause may describe a procedure that defines how to derive key material from a shared secret and other parameters using a FIPS-140 compliant crypto module. This remains for further study. + +Table 2/H.235.4 – Object identifiers used by H.235.4 + +| Object identifier reference | Object identifier value | Description | +|-----------------------------|-----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| "I10" | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 48} | Used in procedure DRC1 during GRQ/RRQ and GCF/RCF and ARQ to let the EP/GK indicate support of DRC1. | +| "I11" | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 49} | Used in procedures DRC1, DRC2 and DRC3 for the ClearToken tokenOID indicating that the ClearToken CT A holds an end-to-end key for the caller. | +| "I12" | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 50} | Used in procedures DRC1, DRC2 and DRC3 for the ClearToken tokenOID indicating that the ClearToken CT B holds an end-to-end key for the callee. | +| "I13" | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 52} | Used in procedure DRC1 for the inter-gatekeeper ClearToken tokenOID indicating that the ClearToken CT HG holds an encryption key for the originating gatekeeper. | +| "I20" | {itu-t (0) recommendation (0) h (8) 235 version (0) 4 53} | Used in procedure DRC2 during GRQ/RRQ and GCF/RCF and ARQ to let the EP/GK indicate support of DRC2. | +| "I23" | {itu-t (0) recommendation (0) h (8) 235 version (0) 4 56} | Used in procedure DRC2 for the inter-gatekeeper ClearToken CT HG tokenOID indicating that the ClearToken holds an encryption key for the originating gatekeeper. | +| "I30" | {itu-t (0) recommendation (0) h (8) 235 version (0) 4 34} | For use in separate ClearToken in GRQ/RRQ, GCF/RCF, ARQ to indicate support for DRC3.
For use in separate ClearToken in LRQ to indicate carrying caller's DH parameters. | +| "I33" | {itu-t (0) recommendation (0) h (8) 235 version (0) 4 37} | For use in separate ClearToken in LCF to indicate carrying callee's DH parameters. | +| "Annex I -HMAC-SHA1-PRF" | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 51} | Used in procedures DRC1, DRC2 and DRC3 for keyDerivationOID within V3KeySyncMaterial to indicate the applied key derivation method in clause 12 using the HMAC-SHA1 pseudo-random function. | + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.235.5-200509-I_PDF-E/raw.md b/marked/H/T-REC-H.235.5-200509-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..81f517847a5a2b725c23a1a19de4cdfd8ba396b4 --- /dev/null +++ b/marked/H/T-REC-H.235.5-200509-I_PDF-E/raw.md @@ -0,0 +1,508 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.235.5** + +(09/2005) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Systems aspects + +--- + +**H.323 security: Framework for secure +authentication in RAS using weak shared +secrets** + +ITU-T Recommendation H.235.5 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.235.5** + +## **H.323 security: Framework for secure authentication in RAS using weak shared secrets** + +## **Summary** + +This Recommendation provides the framework for mutual party authentication during H.225.0 RAS exchanges. The "proof-of-possession" methods described permit secure use of shared secrets such as passwords which, if used by themselves, would not provide sufficient security. + +Extensions to the framework to permit simultaneous negotiation of Transport Layer Security parameters for protection of a subsequent call signalling channel are also described. + +In earlier versions of the H.235 sub-series, this profile was contained in H.235 Annex H. Appendices IV, V, VI to H.235.0 show the complete clause, figure, and table mapping between H.235 versions 3 and 4. + +## **Source** + +ITU-T Recommendation H.235.5 was approved on 13 September 2005 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +Authentication, passwords, security. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2006 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|------|--------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 2.1 | Normative references..... | 1 | +| 2.2 | Informative references..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Basic framework..... | 3 | +| 6.1 | Improved negotiation capabilities in H.235.0 ..... | 3 | +| 6.2 | Use between endpoint and gatekeeper ..... | 3 | +| 6.3 | Use of profile between gatekeepers..... | 6 | +| 6.4 | Signalling channel encryption and authentication..... | 6 | +| 7 | A specific security profile (SP1)..... | 6 | +| 8 | An improved security profile (SP2)..... | 8 | +| 8.1 | Call Signalling sequence number ..... | 9 | +| 8.2 | Generation of Weak Encryption Key from password ..... | 9 | +| 8.3 | Nonce size ..... | 9 | +| 8.4 | Initialization vector salting ..... | 9 | +| 8.5 | ClearToken encoding..... | 10 | +| 9 | Extensions to the framework (Informative)..... | 10 | +| 9.1 | Using the master key to secure the call signalling channel via TLS ..... | 10 | +| 9.2 | Use of certificates to authenticate the gatekeeper ..... | 12 | +| 9.3 | Use of alternative signalling security mechanisms ..... | 12 | +| 10 | Threats (Informative)..... | 12 | +| 10.1 | Passive attack..... | 12 | +| 10.2 | Denial-of-Service attacks ..... | 12 | +| 10.3 | Man-in-the-Middle attacks ..... | 13 | +| 10.4 | Guessing attacks ..... | 13 | +| 10.5 | Unencrypted gatekeeper half-key..... | 13 | + +# Introduction + +In many applications, an endpoint (or its user) and its gatekeeper may share only a "small" secret such as a password or a "personal identification number" (PIN). Such a secret (which we shall hereafter refer to as a "password"), and any encryption key derived from it, is cryptographically weak. The challenge/response authentication schemes, as described in clause 10, provide samples of plaintext and corresponding ciphertext and are, therefore, subject to a brute-force attack by an observer of the transaction when the authentications are keyed by simple passwords. Thus, the observer may recover the password or PIN and later pose as the endpoint to obtain service. + +A family of protocols under the generic heading of Encrypted Key Exchange use a shared secret to "obscure" a Diffie-Hellman key exchange in such a way that the attacker must solve a series of finite logarithm problems in order to validate a brute-force attack against the shared secret. In the Encrypted Key Exchange (EKE) of Bellovin and Merritt [B&M], the shared secret is used to encrypt the Diffie-Hellman public keys under a symmetric algorithm. In the Simple Password Exponential Key Exchange (SPEKE) method of Jablon [Jab], the shared secret is used to choose a different generator of the Diffie-Hellman group. These protocols combine the security of a strong Diffie-Hellman key exchange with use of the shared secret in such a way that an attacker cannot obtain known plaintext for use in a brute-force attack against the secret without solving the Diffie-Hellman finite logarithm problem. An advantage of such protocols is that they multiply the strengths of the Diffie-Hellman problem by the strength of the secret-key encryption (or vice versa). A potential disadvantage is that they are typically subject to patent protection. + +# ITU-T Recommendation H.235.5 + +## H.323 security: Framework for secure authentication in RAS using weak shared secrets + +# 1 Scope + +This Recommendation is usable by any gatekeeper or endpoint using the H.225.0 RAS protocols. + +# 2 References + +## 2.1 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.235.0 (2005), *H.323 security: Framework for security in H-series (H.323 and other H.245-based) multimedia systems*. +- ITU-T Recommendation H.235.1 (2005), *H.323 security: Baseline security profile*. +- ITU-T Recommendation H.245 (2005), *Control protocol for multimedia communication*. +- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*. +- Federal Information Processing Standard FIPS PUB 180-2, *Secure Hash Standard*, U.S. Department of Commerce, Technology Administration, National Institute of Standards and Technology, 1 August 2002. +- NIST Special Publication 800-38A 2001, *Recommendation for Block Cipher Modes of Operation – Methods and Techniques*. . + +## 2.2 Informative references + +- [AES] IETF RFC 3268 (2002), *Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security*. +- [B&M] BELLOVIN (S.), MERRITT (M.): U.S. Patent 5,241,599, August 31, 1993, originally assigned to AT&T Bell Laboratories, now assigned to Lucent Technologies. +- [Jab] JABLON (D.): Strong Password-Only Authenticated Key Exchange, *Computer Communication Review*, ACM SIGCOMM, Vol. 26, No. 5, pp. 5-26, October 1996. +- [NIST SP 800-57] NIST Draft Special Publication 800-57 (2005), *Recommendation for Key Management, Part 1: General Guideline*. +- [RFC2104] IETF RFC 2104 (1997), *HMAC: Keyed-Hashing for Message Authentication*. + +- [RFC2412] IETF RFC 2412 (1998), *The OAKLEY Key Determination Protocol*. +[RFC2246] IETF RFC 2246 (1999), *The TLS Protocol Version 1.0*. +[RFC3546] IETF RFC 3546 (2003), *Transport Layer Security (TLS) Extensions*. + +# 3 Definitions + +None. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|------------------------------------| +| ACF | Admission Confirm | +| AES | Advanced Encryption Standard | +| ARJ | Admission Reject | +| ARQ | Admission Request | +| CBC | Cipher Block Chaining | +| CTR | Counter Mode (see NIST SP 800-38A) | +| D-H | Diffie-Hellman | +| EKE | Encrypted Key Exchange | +| GCF | Gatekeeper Confirm | +| GK | Gatekeeper | +| GRJ | Gatekeeper Reject | +| GRQ | Gatekeeper Request | +| HMAC | Hashed Message Authentication Code | +| ICV | Integrity Check Value | +| ID | Identifier | +| LCF | Location Confirm | +| LRJ | Location Reject | +| LRQ | Location Request | +| MIM | Man-in-the-middle | +| OID | Object Identifier | +| PIN | Personal Identification Number | +| PRF | Pseudo-Random Function | +| RAS | Registration, Admission and Status | +| RCF | Registration Confirm | +| RFC | Request for Comments | +| RRJ | Registration Reject | +| RRQ | Registration Request | +| SHA1 | Secure Hash Algorithm 1 | + +| | | +|-------|------------------------------------------| +| SPEKE | Simple Password Exponential Key Exchange | +| TLS | Transport Layer Security | +| UDP | User Datagram Protocol | + +# 5 Conventions + +In this Recommendation the following conventions are used: + +- "shall" indicates a mandatory requirement. +- "should" indicates a suggested but optional course of action. +- "may" indicates an optional course of action rather than a recommendation that something take place. + +For further conventions, refer to clause 5/H.235.0. + +# 6 Basic framework + +## 6.1 Improved negotiation capabilities in H.235.0 + +ITU-T Rec. H.235.0 provides support for this security framework via the inclusion of the following generic element to the **ClearToken**: + +- **profileInfo** is a sequence of profile-specific elements, each identified by its own integer value as defined by the specific profile whose OID is carried in the **ClearToken.tokenOID**. + +In the following descriptions, several elements are passed in **profileInfo**; each of these elements will be given a name, rather than an identifying value, for ease of discussion. + +## 6.2 Use between endpoint and gatekeeper + +The basic framework, in which the requestor is an endpoint wishing to register with a gatekeeper, and the responder is that gatekeeper, proceeds in a straightforward manner. In the following, it is implicitly assumed that each **ClearToken** mentioned is identified with the **tokenOID** of the authentication profile. The **ClearToken** is assumed to be extended. The **random** and/or **random2** elements may be used by a profile in either of two ways: they may be included in the computation of the authentication key, and/or they may be included in a profile **ClearToken** in each subsequent RAS message (e.g., RRQ/RCF) to prevent replay. The endpoint registration exchange proceeds as follows: + +- 1) The endpoint announces its willingness to participate in one or more key negotiation and authentication schemes by including the appropriate object ID(s) for the desired profile(s) in **authenticationMechanism.keyExch** elements of the **authenticationCapability** element of the **GatekeeperReQuest**. It is assumed that each specific OID completely defines an authentication procedure in terms of public key system (e.g., Diffie-Hellman or Elliptic Curve) and specific group (e.g., one of the OAKLEY groups from RFC 2412), symmetric encryption algorithm (e.g., AES-128-CBC with ciphertext stealing), key derivation function (e.g., via the Pseudo-Random Function of clause 10/H.235.0), message authentication code (e.g., HMAC-SHA1-96 [RFC2104]), and the sequence in which they are used. The endpoint also includes one or more profile **ClearTokens** in the GRQ, each of which carries the OID for the specific profile offered and the necessary (encrypted) public key material in the following form: + - a) **tokenOID** carries the profile OID as offered in the **authenticationCapability** of the encapsulating GRQ. + - b) **timeStamp** may be used to assure currency and protect against replay. + +- c) **password** shall not be used for the actual password. + - d) **dhkey** carries the Diffie-Hellman key parameters, if used. The enclosed **halfkey** element is encrypted as specified by the selected profile. + - e) **challenge** is not required. + - f) **random** is supplied by the initiating party and is used to prevent replay attacks. + - g) **certificate** may be used if certificate exchange is part of the profile. + - h) **generalID** may be used if required by the profile. + - i) **eckasdhkey** carries the Elliptic Curve key parameters, if used by the profile. The enclosed **public-key** element should be encrypted as specified by the profile. + - j) **sendersID** may be used as specified by the profile. + - k) **profileInfo** element, **initVect**, may be supplied along with the (encrypted) public key material (**dhkey** or **eckasdhkey**) if the profile requires an initialization vector for decryption. + - l) If the initiator wishes to use key material derived from an earlier exchange, it shall include a **profileInfo** element, denoted **sessionID**, containing the identifier assigned during the earlier exchange. In this case, **dhkey**, **eckasdhkey** and/or **initVect** should not be included. + - m) If the initiator wishes to establish a TLS session for a call signalling connection, it may include one or more **profileInfo** elements containing TLS ciphersuites; the message shall contain only one ciphersuite (the one previously negotiated) if **sessionID** is present. + - n) If the initiator wishes to establish a TLS session for call signalling, it may include a **profileInfo** element containing a list of compression methods; only one compression method (the one previously negotiated) shall be included if **sessionID** is present. + - o) More **profileInfo** elements may be used for any additional parameters required for the procedures under the profile. +- 2) Upon receiving the GRQ, the gatekeeper selects an **AuthenticationMechanism** profile from the offered list, generates a suitable private key, computes the corresponding public key, generates an initialization vector if needed for symmetric encryption using the password, encrypts the public key, generates a unique session ID, and generates a random quantity, all of which are encoded into a **ClearToken**. Depending on the profile, the following use is made of the ClearToken elements: +- a) **tokenOID** carries the profile OID, as selected from the **authenticationMethod** of the encapsulating GCF. + - b) **timeStamp** may be used to assure currency and protect against replay. + - c) **password** shall not be used for the actual password. + - d) **dhkey** carries the Diffie-Hellman key parameters, if used. The enclosed **halfkey** element is encrypted as specified by the selected profile. + - e) **challenge** is used to carry an initialization vector, if required for key encryption as specified by the profile, or it may be used to carry a random string to be returned by the endpoint to prevent replay attacks. + - f) **random** may contain the unpredictable, unique value supplied by the requestor to prevent replay attacks. + - g) **certificate** may be used if certificate exchange is part of the profile. + - h) **generalID** may be used if required by the profile. + +- i) **eckasdhkey** carries the Elliptic Curve key parameters, if used by the profile. The enclosed **public-key** element should be encrypted as specified by the profile. +- j) **sendersID** may be used as specified by the profile. +- k) **random** (or an additional **profileInfo** element, denoted **random2**, if the profile requires both random numbers to remain in the message exchange) should contain an unpredictable, unique value supplied by the responder to protect against replay attacks. +- l) **initVect** is supplied along with the (encrypted) public key material (**dhkey** or **eckasdhkey**) if the profile requires an initialization vector for decryption. +- m) **sessionID** is a unique (to the gatekeeper) identifier used to identify this registration session. Under certain profiles, it may also be used as a TLS session ID for rapid establishment of a TLS-protected call signalling channel. +- n) **profileInfo** may be used for any additional parameters required for the procedures under the profile. + +The gatekeeper then computes the shared secret or master key using its private key and the (decrypted) public key from the GCF, and derives from the master key the necessary encryption keys, authentication keys, or other material, according to the profile. The above-described **ClearToken** is placed within the **GatekeeperConFirm** message. The GCF shall be integrity checked/authenticated using the derived authentication key, then sent to the endpoint. The authentication/integrity check may be returned in one of several ways, as specified by the profile: via a profile-specific **profileInfo** element, or via one of the procedures specified in ITU-T Rec. H.235.1. + +- 3) The endpoint examines the selected **authenticationMechanism.keyExch** from the GCF and extracts the parameters from the **ClearToken** identified by the corresponding **tokenOID**. The endpoint then selects its private key, computes the corresponding public key, and selects any other parameters required by the profile. The endpoint then computes the shared secret or master key using its private key and the (decrypted) public key from the GCF, and derives the necessary encryption keys, authentication keys, or other material from it, according to the profile. The endpoint shall then verify the integrity of the GCF. If the GCF does not verify correctly, the endpoint shall discard it, along with all the key material derived from it, and continue waiting for a valid GRQ message. Standard RAS recovery will lead to a retransmission of the GRQ, and, presumably, receipt of an undamaged GCF. If a few retransmissions fail to produce a successful response, the endpoint should cease attempting to register and inform its user that something is amiss. Note that each GRQ sent gives a gateway imposter one more chance to guess the user's password and have its guess validated by acceptance of the GRQ. If the integrity check of the GCF succeeds, the endpoint has validated the gatekeeper, and may proceed to register, and, in the process, authenticate itself to the gatekeeper. +- 4) The endpoint then populates a **ClearToken** with the profile **tokenOID** in a manner similar to that done by the gatekeeper as described above. Any fields from the GCF clear token that are considered as a challenge by the profile should be included in the **ClearToken**. If specified by the profile to avoid replay, the **ClearToken** shall include **random** and **random2** from the GCF received above. The **ClearToken** is then placed in a **Registration ReQuest** to be sent back to the gatekeeper. The endpoint should then authenticate the full RRQ message and send it to the gatekeeper. From this point onward, the endpoint should not accept, nor should it send, RAS messages that are not authenticated by the agreed-upon profile using the authentication key derived from the shared key material. +- 5) The gatekeeper receives the RRQ, and shall use the shared key material to verify the integrity of the RRQ against the included authentication and integrity check. If the integrity check fails, the gatekeeper shall ignore the received RRQ, and wait for a verifiable RRQ. If none arrives, the endpoint will eventually abandon the registration attempt and return to the + +search for a gatekeeper. If the integrity check succeeds, the gatekeeper will prepare a Registration Confirm message to send back to the endpoint. Depending on the profile, this RCF may contain a **ClearToken** that includes the **random**, **random2**, and/or **challenge** elements from the authentication profile **ClearToken** provided in the RRQ. The RCF, and all subsequent RAS messages, shall contain a verifiable authentication and integrity check computed using the negotiated authentication key and algorithm. + +- 6) When the endpoint receives the RCF message, it verifies the integrity via the included authentication and integrity check element. If not verified, the RCF shall be discarded; if no valid RCF is received, even after the RRQ is retransmitted, then the session shall be abandoned and the endpoint shall return to seeking a new gatekeeper. If the RCF is verified, the session ID and selected ciphersuite, if present, may be extracted from its **ClearToken** for later use in the establishment of a secure call signalling channel. + +## 6.3 Use of profile between gatekeepers + +Essentially the same procedure may be used between gatekeepers in an LRQ/LCF exchange. In this situation, no explicit profile selection is possible; the originating gatekeeper shall offer one or more profiles by including the appropriate **ClearToken(s)** as described for the GRQ message, above. The responding gatekeeper may choose an offered profile and should return the corresponding **ClearToken** as described above for the GCF message. Note that, in this case, the calling gatekeeper does not authenticate itself to the responding gatekeeper until it establishes a call signalling channel to that gatekeeper. + +This procedure may be employed in a multicast mode if a group of gatekeepers share a single secret to be used for this purpose. The multicast LRQ will be based on that secret; those gatekeepers that reply with LCF will use that key to decode the offered Diffie-Hellman public key, and will each choose their own **nonce** and Diffie-Hellman private key for their reply. The resulting session keys will be unique to the final pair of gatekeepers. + +## 6.4 Signalling channel encryption and authentication + +If gatekeeper routing is supported by the gatekeeper, the newly-negotiated master key material and identified cryptographic parameters may be used to authenticate and secure the call signalling channel, e.g., by establishing a TLS session for call signalling. If TLS is to be used, the gatekeeper shall include the selected **cipherSuite** and **compress** elements in the returned profile **ClearToken**. + +# 7 A specific security profile (SP1) + +This clause provides a standard security profile which is expected to provide a shared secret estimated to be equivalent to an 80-bit random number (see [NIST SP 800-57]). The profile consists of the following: + +- Object ID for this profile (denoted "SP1") will be {itu-t (0) recommendation (0) h (8) 235 version (0) 3 60}. +- Master key, $K_m$ , negotiation: Diffie-Hellman key exchange using the OAKLEY well-known group 2 [RFC 2412], followed by the SHA1 [FIPS PUB 180-1] hash reduction of the Diffie-Hellman secret: $K_m = \text{SHA1}(\text{Diffie-Hellman shared secret})$ . +- Symmetric encryption algorithm: shall be AES-128 in segmented counter mode with a 2-octet party discriminator, $D$ , a 12-octet initialization vector, $IV$ , and a 2-octet counter field, $C$ , such that $\text{counter} = D \parallel IV \parallel C$ , and $C = 0$ initially. See [NIST SP 800-38A] for a description of CTR mode. The party discriminator, $D$ , is set to 0x3636 when the $IV$ is generated by the party which issued the GRQ/RRQ, or LRQ, and is set to 0x5c5c when the $IV$ is generated by the party which responded with GCF/RCF, or LCF. Each party must + +insure that each IV it generates is unique; it may use its own method to insure this uniqueness. + +- Diffie-Hellman key encryption: shall use the AES-128 segmented counter mode to encrypt the Diffie-Hellman public key (represented as an octet string in network byte order); the initialization vector shall be carried in **ClearToken.initVect**, and the 16-octet key, $K_p$ , shall be constructed as the high-order 128 bits of the SHA1 hash of the user password: $K_p = \text{Trunc}(\text{SHA1}(\text{user password}), 16)$ , where $\text{Trunc}(x,y)$ truncates octet string $x$ to $y$ octets. Note that this is typically considered a weak key. +- Replay prevention: each party shall supply a 32-bit "random" number (which may contain a counter field to guarantee uniqueness); the random numbers are used explicitly in the computation of the derived keys, hence they each need only be transmitted once. +- Authentication key, $K_a$ , derivation: using the PRF defined in clause 10/H.235.0, which we denote as $\text{PRF}(\text{in\_key}, \text{label}, \text{outkey\_len})$ with $\text{in\_key} = K_m$ , and $\text{label} = \text{"auth\_key"} \parallel R_e \parallel R_g$ , where $R_e$ is a **nonce** obtained from **ProfileElement** of the GRQ and $R_g$ is a **nonce** obtained from a **ProfileElement** of the GCF, and $\text{outkey\_len} = 128$ . +- Message authentication and integrity function: using a **ClearToken** with **tokenOID** set to "SP1" and a **ProfileElement.octets** set to the HMAC-SHA1-96 hash value computed over the entire message as described in ITU-T Rec. H.225.0; this procedure shall be applied to all RAS and call signalling messages (except a GRQ, or LRQ, which does not contain a **sessionID**). +- Element encryption key, $K_e$ : selected elements of call signalling messages (or elements tunnelled therein) may be encrypted using AES-128 in segmented counter mode using key $K_e = \text{PRF}(K_m, \text{"encrypt\_key"} \parallel R_e \parallel R_g, 128)$ . For example, this key may be used to encrypt media session keys for distribution in **h235Key** elements as used in Fast Connect and/or H.245. When used in this manner, "SP1" is used as the encryption algorithm OID. + +This profile makes use of the **ProfileElements** defined in Table 1. These elements are carried in a **ClearToken.profileInfo** element sequence as defined in ITU-T Rec. H.235.0. + +**Table 1/H.235.5 – Profile elements** + +| Element name
(used in text) | ElementID
Value | Element
choice (length) | Element description | +|--------------------------------|--------------------|----------------------------|------------------------------------------| +| initVect | 1 | Octets (12) | initialization vector for EKE encryption | +| nonce | 2 | Octets (any) | an unpredictable, unique value | +| cipherSuite | 3 | Octets (2) | a TLS ciphersuite | +| compression | 4 | Octets (1) | a TLS compression algorithm | +| sessionID | 5 | Octets (1..) | unique, may match a TLS session ID | +| integrityCheck | 6 | Octets (12) | keyed checkvalue | + +The registration sequence shall consist of: + +- The endpoint shall send a GRQ with the **authenticationCapability** element containing an **AuthenticationMechanism.keyExch** containing OID "SP1" and a corresponding **ClearToken** with **tokenID** = "SP1" and **dhkey** containing a 1024-bit public key encrypted using **initVect** as the IV and the key derived from the user password, and **nonce** = a 32-bit random number selected by the endpoint. +- The gatekeeper shall reply with a GCF with the **authenticationMode** element equal to an **AuthenticationMechanism.keyExch** containing OID "SP1", and a **ClearToken** with **tokenID** = "SP1" and **dhkey** containing an unencrypted 1024-bit public key, and **nonce** = a 32-bit random number selected by the gatekeeper, along with an **integrityCheck** containing + +the authentication hash value computed using the derived authentication key, $K_a$ . Note that it is not necessary for the gatekeeper to encrypt its Diffie-Hellman half-key in the GCF in this profile because it is the first party to authenticate itself by demonstrating its ability to authenticate the GCF using the derived authentication key. This mode permits the gatekeeper to reuse its Diffie-Hellman keys with more than one endpoint. See clause 10.5. + +- The endpoint shall reply with an RRQ with the authentication and integrity check value in a **ProfileElement** with **elementID** set to **integrityCheck**, and **element** set to the value computed using the derived authentication key, $K_a$ . +- Subsequent RAS messages, including the RCF, shall be authenticated and integrity checked using the same procedure and key. H.225.0 Call Signalling messages (and tunnelled H.245 messages, if present) shall be authenticated using a **ClearToken**, with **tokenOID** set to "SP1", containing a **profileInfo ProfileElement** with **elementID** set to **integrityCheck** and **element** set to the computed value. +- The encryption key, $K_e$ , and the encryption algorithm AES-128 in segmented counter mode may be used by the gatekeeper and the endpoint to encrypt selected information transported over RAS, call signalling, and/or H.245. For example, the gatekeeper may distribute media encryption keys secured under $K_e$ and the profile encryption algorithm. +- If an endpoint is required to reregister, and it retains the original session ID and master secret, it should attempt to reregister using the original session ID and master secret by including the session ID explicitly in the GRQ (and not including a Diffie-Hellman half key) in its GRQ. +- This profile shall be usable between gatekeepers (see 6.3). + +# 8 An improved security profile (SP2) + +This clause defines a new security profile based on the original profile, SP1. It is identified informally as SP2 and formally with OID {itu-t (0) recommendation (0) h (8) 235 version (0) 4 62}. This profile is identical to SP1, except as specified in the following subclauses. The specific improvements over SP1 include: + +- Improvements in the call signalling message sequence numbering to counter replay attacks. +- Salting of the generation of the password-based encryption key using the endpoint alias in order to counter dictionary attacks. +- The nonce size is increased and made variable. +- A salting key is derived for use with the encryption initialization vector. +- A more efficient transport of the profile **ClearToken** is provided using **genericData**. + +SP2 uses the Profile Elements of Table 1, as well as the additional Profile Elements described in Table 2: + +**Table 2/H.235.5 – Additional profile elements for SP2** + +| Element name
(used in text) | ElementID
value | Element choice
(length) | Element description | +|--------------------------------|--------------------|----------------------------|--------------------------------------------------------------------------------------| +| seqNumber | 7 | Octets (4) | 32-bit sequence number in network byte order | +| connectID | 8 | Octets (2) | Signalling Connection Identifier.
(Optional, default = 0) | +| endpointID | 9 | Octets (variable) | ASN.1-encoded AliasAddress associated with the endpoint and its password. (Optional) | + +## 8.1 Call Signalling sequence number + +H.225.0 Call Signalling messages do not contain a sequence number because they are transported over a reliable connection (TCP) which is responsible for sequencing. Nevertheless, lack of a unique message identifier at the application level does expose call signalling to replay or reflection attacks. This problem can be countered by adding a sequence number, and an optional connection identifier, to each call signalling message. Note that this technique does not completely prevent a replay or reflection attacks, but it severely reduces the attacker's chances of success. + +Sequence numbers must be unique in each direction to prevent reflection. This can be accomplished, within practical limits, by requiring the issuer of the GRQ (endpoint) or LRQ (gatekeeper) message to start its call signalling transmit sequence number at 0 (zero) and its receive sequence number at $2^{31}$ , with corresponding behaviour by the receiving gatekeeper. This provides a very large time before any overlap can occur (almost 600 hours at the quite unusual rate of one message per millisecond). Successive calls using the same SessionID should transmit with the next unused sequence number in each direction. (To allow for lost messages over failed connections, the receiver should accept messages within a small (e.g., 5-10) window following the last received sequence number, and proceed from there.) Devices that support multiple simultaneous call signalling connections under the same session ID, may use an optional **connectID** to identify separate sequence number spaces for the calls. If not specified, the **connectID** is presumed to be 0 (zero). + +## 8.2 Generation of Weak Encryption Key from password + +In order to prevent dictionary attacks in which a PIN is guessed, used to encrypt a D-H public key, and then applied successively to all known endpoint aliases, it is desirable to "salt" the encryption key with the alias itself. In particular, the password-based key, $K_p$ , shall be computed from the concatenation of the password and the supplied **endpointID**: + +$$K_p = \text{Trunc}(\text{SHA1}(\text{user password} \parallel \mathbf{endpointID}), 16)$$ + +Typically, the **AliasAddress** in **endpointID** will be one of the aliases included in the GRQ **endpointAlias** element, but this is not necessary. For example, the **endpointID** may identify a gateway supporting many endpoints whose aliases are listed in **endpointType**. + +## 8.3 Nonce size + +Security Profile 1 requires each party to supply a 4-octet (32-bit) nonce as part of the key negotiation protocol. When supplied during the initial key negotiation, 32 bits is perhaps sufficient to insure freshness in those cases in which the responding gatekeeper reuses the same Diffie-Hellman public key but the requestor generates a fresh key. However, when negotiating new session keys from a previously-negotiated master key, the total of 64 unique bits may not provide sufficient difference between each set of derived keys. It is proposed that the nonce size be variable, with a minimum of 4 octets, and a maximum of 16. + +## 8.4 Initialization vector salting + +As an added obfuscation measure, a 112-bit session salting key, $K_s$ , is derived from the negotiated master key as: + +$$K_s = \text{PRF}(K_m, \text{"salting\_key"} \parallel R_e \parallel R_g, 112).$$ + +Construction of the initial AES-128-CM counter for encryption and decryption is then carried out as follows: + +$$\text{Counter} = (K_s \wedge (D \parallel \text{IV})) \parallel C, \text{ where } C \text{ is the 16-bit counter field, initially zero.}$$ + +## 8.5 ClearToken encoding + +Security profile 1 uses the **clearToken** sequence to carry the parameters of the profile. Every H.225.0 message contains a sequence of **ClearTokens**, except the **empty** choice of **h323-message-body**; all messages carry **genericData**. The structure of the SP1 procedures permit a rather regular structure for the **ClearToken**, which permits it to be ASN.1-encoded ahead of time, and carried as a **raw** parameter with **id.standard** set to 1 in a **GenericData** element identified by the SP2 OID. This form permits identification of the **clearToken** by the "null" OID {0,0}. Most importantly, it makes it easier to locate the token, and the check value within it, because the encoded form of the **ClearToken** alone becomes available as part of the normal encoding and decoding process. Thus it is faster to locate the integrityCheck element within the encoded clear token than within the entire encoded message. + +# 9 Extensions to the framework (Informative) + +The following elements may be incorporated into a security profile defined under this framework. + +## 9.1 Using the master key to secure the call signalling channel via TLS + +The key material negotiated during the RAS exchange may be used also to derive session keys for the protection of the call signalling channel under the TLS transport protocol ([RFC 2246], [RFC 3546]). In effect, the RAS negotiation replaces the initial TLS handshake protocol. This only makes sense, of course, if the call signalling will be gatekeeper-routed. This is especially useful for intergatekeeper authentication and signalling using the LRQ/LCF exchange. In this case, there is no third RAS message by which the calling gatekeeper can authenticate itself to the called gatekeeper using the negotiated key material, but the caller can be implicitly authenticated by its ability to establish the call signalling channel with the correct TLS session parameters. Figure 1 illustrates the flow of information involved: RAS is used to negotiate the session master key, the Session ID and the corresponding pre-master secret are distributed to the TLS software, and the Session ID is used by the call signalling layer to establish the call signalling channel over TLS. The means by which transfer of the secret is accomplished is implementation-dependent and beyond the scope of this Recommendation. Note that this Recommendation specifies port 1300 as the default TLS listen port for call signalling. The endpoint must, however, use one of the call signalling transport addresses supplied by the gatekeeper. + +![Diagram showing information flow for security profile and TLS across various layers and protocols. It includes AV applications (G.XXX, H.26X), Terminal control and management (H.225.0 RAS, Call signalling, H.245), and Data applications (T.124, T.125, T.123). Layers shown are Network security, Network layer, Link layer, and Physical layer. Transport layers are Unreliable and Reliable. Arrows indicate the flow of RAS, Software transfer, and Call signalling.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +Scope of H.235.0 + +| | | | | | | | | +|----------------------|----------------|---------------------------------|-------------------------------------------------|-------------------------|-------|-------|-------------------| +| AV applications | | Terminal control and management | | | | | Data applications | +| G.XXX | H.26X | RTCP | H.225.0 Terminal to gatekeeper signalling (RAS) | H.225.0 Call signalling | H.245 | T.124 | | +| Encryption | | | | | | T.125 | | +| RTP | Authentication | | | | | T.123 | | +| Unreliable transport | | | Reliable transport | | | | | +| Network security | | | Network layer | | | | | +| | | | Link layer | | | | | +| | | | Physical layer | | | | | + +H.235.5\_F1 + +RAS                      Software transfer                      Call signalling + ← - - - - →            ..... →                                    ← - . - . → + +Diagram showing information flow for security profile and TLS across various layers and protocols. It includes AV applications (G.XXX, H.26X), Terminal control and management (H.225.0 RAS, Call signalling, H.245), and Data applications (T.124, T.125, T.123). Layers shown are Network security, Network layer, Link layer, and Physical layer. Transport layers are Unreliable and Reliable. Arrows indicate the flow of RAS, Software transfer, and Call signalling. + +**Figure 1/H.235.5 – Information flow for security profile and TLS** + +The following description makes reference to the steps of the basic framework in Figure 1. + +### 9.1.1 Endpoint registration + +An endpoint may test the ability of a gatekeeper to support TLS-protected call signalling by including one or more **cipherSuite** elements and one or more **compression** elements in the profile **ClearToken** in the GRQ message sent in step 1, above. If the endpoint wishes to use a previously-negotiated session, it shall also include the **sessionID** in the **ClearToken** (and shall specify only the single ciphersuite and the single compression method which match the requested session). If the negotiation is to be based on an existing TLS session, no cryptographic material is required in the profile **ClearToken**, other than **nonce**. + +If a requested session does not exist, the gatekeeper shall select another authentication profile (if offered) or it shall return a GRJ with **GatekeeperRejectReason.resourceUnavailable**. If the requested session does exist, the master key material is obtained from the TLS session, and used (along with **random** from the GRQ and a gatekeeper-generated **random2**) to compute the authentication key for the RAS exchange. The **sessionID**, the **cipherSuite**, the **compress** method, and the gatekeeper's **nonce** shall be returned in the profile **ClearToken** of a GCF. + +If the gatekeeper can support TLS session negotiation, it shall compute the master key material as specified by the profile, assign a new session ID and return it in the profile **ClearToken** in the + +**sessionID**. The profile **ClearToken** shall also contain the required security parameters from step 2, above, along with a single selected **cipherSuite**, a single selected **compress** method, and the non-zero **sessionID**. Note that the key exchange method of the selected ciphersuite is immaterial. If the gatekeeper agrees to TLS protection of call signalling, all call signalling transport addresses exchanged in the subsequent RRQ/RCF or ARQ/ACF messages shall be TLS-enabled. + +If TLS negotiation and/or gatekeeper routing are not supported by the gatekeeper, then no TLS parameters shall be returned, but the authentication procedures may continue from step 3, as described above. The endpoint shall decide if it is prepared to proceed without TLS protection of the call signalling; it may choose to do so and still make use of the authentication profile. Upon successful completion of the registration sequence, the TLS session is available for use in rapid establishment of one or more call signalling connections to the gatekeeper, without the need to renegotiate keying material via public-key methods. + +TLS sessions have finite lifetimes. Therefore, it may become necessary for an endpoint to renegotiate session parameters and obtain a new session ID. This may be accomplished by exchanging the necessary **ClearToken** elements as described above in a lightweight ("keepalive") registration sequence. Such a sequence shall not affect the RAS authentication key. + +## 9.2 Use of certificates to authenticate the gatekeeper + +Although it may be impractical to exchange verifiable certificate chains in RAS (due to UDP packet size limitations), it is possible to have a server authenticate itself to the endpoint if the endpoint can obtain a trusted copy of the server's public key via some other means. The server can simply include, in the GCF message, a **CryptoH323Token.cryptoGKCert** with the **ClearToken.tokenOID** set to the selected security profile OID. + +## 9.3 Use of alternative signalling security mechanisms + +The parameters negotiated as part of a security profile under this Recommendation may be employed in transport and/or application level security mechanisms as determined by the specific profile. The **profileInfo** sequence added to the H.235 **ClearToken** has been provided for such use, if needed. + +# 10 Threats (Informative) + +## 10.1 Passive attack + +At the present time, the scheme described above is not vulnerable to passive attack, subject to the provision that the Diffie-Hellman negotiation is not vulnerable to a passive attack. + +## 10.2 Denial-of-Service attacks + +This scheme is subject to an active Denial-of-Service attack in which a third party responds to the initial GRQ with a spurious GRJ. This type of attack may, or may not, be identifiable: if the rejecting gatekeeper is legitimate, and knows the shared secret (e.g., the gatekeeper is the endpoint's gatekeeper and the **rejectReason** is **resourceUnavailable**), then the gatekeeper could complete the key negotiation and authenticate the GRJ by returning, in the GRJ, the same elements described for the GCF (with the exception that the OID returned in **authenticationMode** of the GCF would be returned in a **ClearToken.profileInfo** element of the GRJ). This is left as part of the definition of a specific profile. + +If the GRJ is not authenticated, it could be from an attacker. Before acting on the GRJ (e.g., looking for an alternate gatekeeper), the endpoint should wait for possible receipt of another GRJ or an authenticated GCF from the proper gatekeeper. Otherwise, the endpoint should try each gatekeeper + +suggested in any **altGKInfo** received in all GRJs (one of which is, presumably, legitimate). In any case, only the proper gatekeeper (which knows the shared secret) can return an authenticated GCF. + +## 10.3 Man-in-the-Middle attacks + +It is tempting to consider the exchange using an unencrypted Diffie-Hellman key exchange, followed by use of the password or PIN to derive session keys from the Diffie-Hellman secret. However, this form of the exchange is subject to a Man-in-the-Middle attack that can be used to discover the "small" shared secret by brute force using the Integrity Check Value provided by the legitimate gatekeeper in the GCF message. + +Any MIM can, of course, manipulate any authenticated RAS message to insure that the message will be discarded due to integrity check failure. If all messages can be manipulated, service can be denied. + +## 10.4 Guessing attacks + +An attacker may pose as either a legitimate endpoint, a legitimate gatekeeper, or both (Man-in-the-Middle), and attempt to guess the shared secret by trial and error. For example, the attacker (who is presumed to know the details of the authentication profile, but not the shared secret) can guess a shared secret and attempt to register by sending a GRQ using this guess. In general, the gatekeeper will respond to this attempt with a GCF containing the GK's public key (encrypted using the real shared secret), and an ICV computed using the derived key which depends on the GK's decryption of the attacker's encrypted public key. The attacker can use this information to verify its guess of the shared secret. If the guess confirms the ICV of the GCF, then it is likely equal to the actual shared secret; this can be confirmed by continuing with the registration sequence. If the guess cannot be used to reproduce the ICV of the GCF, then the attacker must make another guess and try again. With a small keyspace for the shared secret, the number of guesses for a brute-force search may not be prohibitive. This attack requires the active participation of the gatekeeper (or the endpoint if the attacker is posing as the gatekeeper). The traditional method for countering such an attack is to monitor the number of unsuccessful attempts and, when a threshold is reached, treat all subsequent attempts as invalid (at least for a specified period) and raise an alarm, but such procedures are implementation dependent. + +## 10.5 Unencrypted gatekeeper half-key + +As mentioned above, the EKE exchange may remain secure, under certain conditions, if the responding gatekeeper does not encrypt its Diffie-Hellman half-key. In particular, the gatekeeper must be the first party to demonstrate its knowledge of the shared secret (PIN) via the ICV. If this is not the case, then the gatekeeper (or an interloper posing as the gatekeeper) could simply try all possible PINs to decrypt the endpoint's D-H half-key, compute the resulting D-H shared secret, derive the authentication key, and test it against the ICV supplied by endpoint. This is not possible if the endpoint can check the ICV supplied by the gatekeeper first, and refuse to continue with registration if the ICV is not as expected. + +The use of an unencrypted half-key is advantageous to the gatekeeper in that it can reuse its corresponding private key with multiple endpoints. This would not be possible if the same key were distributed encrypted under multiple shared secrets or PINs. A third-party observer could collect examples of the half-key encrypted under two different PINs, say, then could search through the possible combinations of two PINs to see which pair produced the same half-key when decrypted. If there are, say, $10^8$ possible PINs, then there are only $10^{16}$ possible combinations to try. This is a problem equivalent to searching for a 54-bit random number, which is not at all infeasible. Even if more than one possible solution is found, the correct one could be quickly determined by use of a third observation. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/raw.md b/marked/H/T-REC-H.235.7-200509-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a7cb14f98637481308323db5497ebeebea2321dc --- /dev/null +++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/raw.md @@ -0,0 +1,1290 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.235.7** + +(09/2005) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Systems aspects + +--- + +**H.323 security: Usage of the MIKEY key +management protocol for the Secure Real Time +Transport Protocol (SRTP) within H.235** + +ITU-T Recommendation H.235.7 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.235.7** + +## **H.323 security: Usage of the MIKEY key management protocol for the Secure Real Time Transport Protocol (SRTP) within H.235** + +## **Summary** + +The purpose of this Recommendation is to describe security procedures for H.323/H.235-based systems for using the MIKEY key management protocol in conjunction with the Secure Real Time Transport Protocol. + +In earlier versions of the H.235 sub-series, this profile was contained in Annex G/H.235. Appendices IV, V, VI to H.235.0 show the complete clause, figure, and table mapping between H.235 versions 3 and 4. + +### **Source** + +ITU-T Recommendation H.235.7 was approved on 13 September 2005 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +### **Keywords** + +Media encryption, MIKEY key management, multimedia security, secure Real Time Transport Protocol, security profile, SRTP. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +### INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2006 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 2.1 Normative references..... | 1 | +| 2.2 Informative references and Bibliography ..... | 2 | +| 3 Definitions ..... | 2 | +| 4 Symbols and abbreviations ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Introduction ..... | 4 | +| 7 Overview and scenarios..... | 5 | +| 7.1 MIKEY operation at "session level" ..... | 6 | +| 7.2 MIKEY operation at "media level" ..... | 7 | +| 7.3 MIKEY capability negotiation ..... | 8 | +| 8 Security profile using symmetric security techniques ..... | 9 | +| 8.1 Terminating a H.323 call..... | 14 | +| 8.2 TGK re-keying and CSB updating ..... | 15 | +| 8.3 H.245 tunnelling support..... | 16 | +| 8.4 SRTP algorithms ..... | 16 | +| 8.5 List of object identifiers..... | 17 | +| 9 Security profile using asymmetric security techniques ..... | 17 | +| 9.1 Terminating a H.323 call..... | 21 | +| 9.2 TGK re-keying and CSB updating ..... | 21 | +| 9.3 H.245 tunnelling support..... | 23 | +| 9.4 SRTP algorithms ..... | 23 | +| 9.5 List of object identifiers..... | 23 | +| Appendix I – MIKEY-DHHMAC option ..... | 23 | +| I.1 Terminating a H.323 call..... | 27 | +| I.2 TGK re-keying and CSB updating ..... | 28 | +| Appendix II – Using H.235.4 for establishing a pre-shared secret..... | 30 | +| II.1 Terminating a H.323 call..... | 32 | +| II.2 TGK re-keying and CSB updating ..... | 32 | + +## Introduction + +The purpose of this Recommendation is to provide recommendations of security procedures for H.323/H.235-based systems to use the IETF MIKEY key management protocol in conjunction with the IETF SRTP security protocol. + +This Recommendation is written as a security profile of ITU-T Rec. H.235 that is offered as an option and may complement the other media security features of ITU-T Rec. H.235.6. + +This Recommendation enables the deployment of SRTP media security where the MIKEY key management supplies the necessary keys and security parameters among the involved endpoints end-to-end. This Recommendation can be deployed within a H.323 domain among H.235.7-enabled H.323 systems. This Recommendation defines the security protocol extensions to H.225.0 RAS and Call Signalling as well as H.245, along with the corresponding procedures. Furthermore, this Recommendation provides the capabilities to support interworking with IETF SIP entities that have implemented the MIKEY key management and SRTP. + +## H.323 security: Usage of the MIKEY key management protocol for the Secure Real Time Transport Protocol (SRTP) within H.235 + +# 1 Scope + +The purpose of this Recommendation is to provide recommendations of security procedures for H.323/H.235-based systems to use the MIKEY key management protocol in conjunction with the SRTP security protocol. + +This security profile is offered as an option and may complement the other media security features of H.235.6. + +# 2 References + +## 2.1 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.235.0 (2005), *H. 323 security: Framework for security in H-series (H.323 and other H.245-based) multimedia systems*. +- ITU-T Recommendation H.235.1 (2005), *H.323 security: Baseline security profile*. +- ITU-T Recommendation H.235.3 (2005), *H.323 security: Hybrid security profile*. +- ITU-T Recommendation H.235.4 (2005), *H.323 security: Direct and selective routed call security*. +- ITU-T Recommendation H.245 (2005), *Control protocol for multimedia communication*. +- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communication systems*. +- ITU-T Recommendation X.800 (1991), *Security Architecture for Open Systems Interconnection for CCITT applications*. +- ISO/IEC 10118-3:2004, *Information Technology – Security techniques – Hash functions – Part 3: Dedicated hash functions*. +- IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- IETF RFC 3711 (2004), *The Secure Real Time Transport Protocol (SRTP)*. +- IETF RFC 3830 (2004), *MIKEY: Multimedia Internet KEYing*. + +## 2.2 Informative references and Bibliography + +- IETF RFC 1305 (1992), *Network Time Protocol (Version 3) Specification, Implementation and Analysis*. +- IETF RFC 2327 (1999), *SDP: Session description protocol*. +- IETF RFC 2631 (1999), *Diffie-Hellman Key Agreement Method*. +- IETF RFC 3261 (2002), *SIP: Session Initiation Protocol*. +- IETF RFC 3264 (2002), *An Offer/Answer Model with the Session Description Protocol (SDP)*. +- IETF RFC ssss (2005), M. Handley, Van Jacobson, C. Perkins: *SDP: Session Description Protocol*, draft-ietf-mmusic-sdp-new-24.txt. +- IETF RFC wwww (2005), J. Arkko, E. Carrara et al: *Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)*, Internet Draft draft-ietf-mmusic-kmgmt-ext-14.txt, Work in Progress. +- IETF RFC zzzz (2005), M. Echner: *HMAC-authenticated Diffie-Hellman for MIKEY*, Internet Draft draft-ietf-msec-MIKEY-DHHMAC-11.txt, Work in Progress. + +# 3 Definitions + +None. + +# 4 Symbols and abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|--------------|--------------------------------------------------------------------| +| $a, b, e, d$ | private DH key of EP A, EP B, GK E, GK D | +| Cert | digital certificate (see RFC 3830) | +| CP/C | CallProceeding-to-Connect | +| CSB | Crypto Session Bundle (see RFC 3830) | +| $CT_B, CT_A$ | ClearToken for endpoint B, ClearToken for endpoint A (see H.235.4) | +| DRC1 | Direct-routed Call (see H.235.4) | +| $ENC_k(x)$ | Encryption of $X$ using key $k$ | +| env_key | Envelope key (RFC 3830) between endpoint B and endpoint A | +| EP | Endpoint | +| ESC | H.245 EndSessionCommand | +| DH | Diffie-Hellman | +| $DH_A$ | DH half-key of endpoint A | +| $DH_B$ | DH half-key of endpoint B | +| $g^a, g^b$ | Diffie-Hellman half-key of EP A, EP B | +| $g^e, g^d$ | Diffie-Hellman half-key of GK E, GK D | +| GK | Gatekeeper | +| HDR | MIKEY header payload (see RFC 3830) | +| $ID_A, ID_B$ | Identity (i.e., endpoint ID) of endpoint A, Identity of endpoint B | + +| | | +|----------------------------|------------------------------------------------------------------------------| +| IETF | Internet Engineering Task Force | +| Imsg | MIKEY message of the initiator (see RFC 3830) | +| KEMAC | MIKEY KEMAC payload message (see RFC 3830) | +| MAC( k , x ) | Keyed MAC on x using key k | +| Ma | MIKEY authentication key (see RFC 3830) | +| Me | MIKEY encryption key (see RFC 3830) | +| MIKEY | Multimedia Internet Keying | +| NTP | Network Time Protocol | +| PKE | MIKEY PKE payload message (see RFC 3830) | +| PKI | Public-Key Infrastructure | +| PRF | Pseudo-Random Function (MIKEY-PRF, see RFC 3830 sections 4.1.2-4.1.4) | +| Rand | random nonce (see RFC 3830) | +| Rmsg | MIKEY message of the responder (see RFC 3830) | +| rand() | random value | +| RSA | Rivest, Shamir and Adleman (public key algorithm) | +| sa , sb | shared secret among endpoint A and GK, shared secret among endpoint B and GK | +| sl | shared secret among gatekeepers | +| SDP | Session Description Protocol | +| SHA1 | Secure Hash Algorithm 1 (ISO/IEC 10118-3) | +| SIP | Session Initiation Protocol | +| SP | Security Policy (see RFC 3830) | +| SRTCP | Secure Real-time Transport Control Protocol | +| SRTP | Secure Real-time Transport Protocol (see RFC 3711) | +| SSRC | Synchronization source (RTP) | +| T | Timestamp (see RFC 3830) | +| TGK | Traffic Generating Key (see RFC 3830) between endpoint A and endpoint B | +| V | Verification message field (see RFC 3830) | +| ZZ AB | dynamic shared H.323 secret ZZ AB | +| {} | Zero, one or more occurrences | +| [] | Optional element | + +# 5 Conventions + +The object identifiers are referenced through a symbolic reference in the text (e.g., "G1"), clauses 8.5 and 9.5 list the actual numeric values for the symbolic object identifiers, for further information see also clause 5/H.235.0. + +Table 1 defines the five MIKEY key management protocols that are being referenced throughout this Recommendation: + +**Table 1/H.235.7 – MIKEY key management protocols** + +| MIKEY protocol | Description | OID value | Parameter identifier | Implementation | +|----------------|--------------------------------------------------------------------------------------------------|-----------------------------------------------------------|----------------------|-------------------------| +| MIKEY | Any MIKEY protocol | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 76} | 76 | Mandatory to implement | +| MIKEY-PS | Symmetric key distribution protocol using pre-shared symmetric keys and HMACs, (see RFC 3830). | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 72} | 72 | Mandatory to implement | +| MIKEY-DHHMAC | Diffie-Hellman key agreement protocol using pre-shared symmetric keys and HMACs; (see RFC zzzz). | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 73} | 73 | Optional | +| MIKEY-PK-SIGN | (RSA-based) public-key distribution protocol using digital signatures; (see RFC 3830). | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 74} | 74 | Mandatory to implement. | +| MIKEY-DH-SIGN | Diffie-Hellman key agreement protocol using digital signatures; (see RFC 3830). | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 75} | 75 | Optional | + +MIKEY (cf. 1st row of Table 1) refers to the MIKEY protocol family generally without indicating specifically any particular MIKEY key management protocol variant such as MIKEY-PS, MIKEY-DHHMAC, MIKEY-PK-SIGN or MIKEY-DH-SIGN. The related implementation of MIKEY shall encompass processing of the MIKEY messages such as MIKEY common header payload (RFC 3830 section 6.1), but does not necessarily require any implementation of a particular MIKEY key management protocol or implementation of a particular MIKEY information payload. The corresponding OID and parameter identifier shall be used in those cases where an H.323 endpoint does not know the actually used MIKEY protocol variant. In any other cases, it is recommended to use the specific OID and parameter identifier of the actual MIKEY key management protocol variant instead. + +# 6 Introduction + +There has been interest in using the security features of IETF SRTP "Secure Real-time Protocol" from ITU-T Rec. H.235. While former versions of H.235 already offer various media security features such as voice encryption using block ciphers and some limited RTP authentication (anti spam option), there are strong reasons to deploy SRTP: + +- use a stream cipher for improved performance, robustness and security; +- be interoperable with other SRTP terminals; such as SIP-based media terminals. + +NOTE – This Recommendation does not specify procedures for security interworking with SIP (RFC 3261); this remains for further study; + +- yield the improved security for RTCP protection; +- obtain improved integrity spanning the entire RTP/RTCP packet; +- deploy state-of-the art AES encryption algorithm; +- use session encryption/authentication keys derived from a pseudo-random function at both ends. + +Further on, a need has been identified to provide an RSA-based key management in addition to the Diffie-Hellman key agreement schemes provided by H.235. Likewise, non-PKI-based key management techniques are felt to be useful in the case where public-key infrastructures are considered not to be the choice. There is also interest to address the issues of lawful interception in the context of key management. + +The IETF has also made efforts to define a real-time capable key management scheme MIKEY (RFC 3830). This generic key management scheme interfaces well with SRTP and is able to provide master keys (TGKs) as well as session traffic keys either end-to-end or possibly end-to-middle/hop-by-hop. MIKEY is an optimized key management protocol that completes within at most two messages, making it ideal for fast start call setup in H.323. + +This Recommendation provides security procedures to deploy the MIKEY key management protocols from within H.323/H.235 in order to support SRTP media security. It is noted that there might be other alternative ways by which SRTP could be supported within H.323/H.235 but such measures are not addressed in this Recommendation and remain for further study. + +This Recommendation deploys the MIKEY key management protocols in a manner that is conceptually similar to the approach described in RFC wwwww where SIP (RFC 3261) carries MIKEY within SDP (RFC 2327, RFC ssss and RFC 3264). + +This Recommendation provides two security profiles with security procedures for two very distinct security infrastructures: + +- symmetric key-based security infrastructure supporting multiple gatekeepers (see clause 8); and +- asymmetric key-based security infrastructure (PKI) supporting multiple gatekeepers (see clause 9). + +# 7 Overview and scenarios + +Figure 1 shows the general scenario that this Recommendation addresses. At least two distinct H.323 endpoints A and B are part of this scenario. These endpoints may be H.323 terminals or H.323 media gateways, the latter with potential interface to other packet- or non-packet-based networks. In addition, at least one gatekeeper is assumed to be part of the environment. In case, there is only a single gatekeeper available, it is assumed that all H.323 endpoints are within that single gatekeeper zone only. In case multiple, chained gatekeepers exist, H.323 endpoints may be placed within different gatekeeper zones. It is further assumed that H.323 endpoints communicate directly end-to-end using the RTP media protocol. + +![Figure 1/H.235.7 – Scenario: A network diagram showing an H.323 Domain. It includes two endpoints, H.323 EP A on the left and H.323 EP B on the right. Between them are two gatekeepers: GK' (dashed box) and GK (shaded box). H.323 signaling arrows connect EP A to GK', GK' to GK, and GK to EP B. A direct bidirectional arrow labeled RTP connects EP A and EP B. The diagram is labeled H.235.7_F01.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph LR + subgraph H.323_Domain + GK_prime[GK'] + GK[GK] + end + EPA[H.323 EP A] -- H.323 --> GK_prime + GK_prime -- H.323 --> GK + GK -- H.323 --> EPB[H.323 EP B] + EPA <--> |RTP| EPB + +``` + +Figure 1/H.235.7 – Scenario: A network diagram showing an H.323 Domain. It includes two endpoints, H.323 EP A on the left and H.323 EP B on the right. Between them are two gatekeepers: GK' (dashed box) and GK (shaded box). H.323 signaling arrows connect EP A to GK', GK' to GK, and GK to EP B. A direct bidirectional arrow labeled RTP connects EP A and EP B. The diagram is labeled H.235.7\_F01. + +**Figure 1/H.235.7 – Scenario** + +Figure 2 shows the general security scenario indicating the usage of the MIKEY key management protocols and the SRTP media security protocol. The MIKEY key management protocols run between the H.323 endpoints A and B; the MIKEY key management protocols are encapsulated within containers within the H.245 signalling handshakes (Terminal Capability Set, Request Mode, Open Logical Channel handshakes and MiscellaneousCommand) and are transparent to any intermediate Gatekeeper(s). + +It is noted that an H.323 endpoint may actually be a gateway. For example, such a gateway may provide an interworking function to interface with SIP-based systems. In this case, the gateway may not necessarily terminate MIKEY but may further relay MIKEY and extend MIKEY for truly end-to-end key management among the involved multimedia terminals, thereby supporting end-to-end media security with SRTP. This approach would support security interworking between H.323/H.235 and SIP-based systems. The exact interworking functionality or specification of such gateways is not the subject of this Recommendation and remains for further study. + +![Figure 2/H.235.7 – Security scenario with MIKEY and SRTP: This diagram is similar to Figure 1 but adds security protocols. H.323 signaling flows through GK' and GK. A bidirectional arrow labeled MIKEY connects EP A and EP B, passing through the gatekeepers. Another bidirectional arrow labeled SRTP connects EP A and EP B directly. The diagram is labeled H.235.7_F02.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +``` + +graph LR + subgraph H.323_Domain + GK_prime[GK'] + GK[GK] + end + EPA[H.323 EP A] -- H.323 --> GK_prime + GK_prime -- H.323 --> GK + GK -- H.323 --> EPB[H.323 EP B] + EPA <--> |MIKEY| EPB + EPA <--> |SRTP| EPB + +``` + +Figure 2/H.235.7 – Security scenario with MIKEY and SRTP: This diagram is similar to Figure 1 but adds security protocols. H.323 signaling flows through GK' and GK. A bidirectional arrow labeled MIKEY connects EP A and EP B, passing through the gatekeepers. Another bidirectional arrow labeled SRTP connects EP A and EP B directly. The diagram is labeled H.235.7\_F02. + +**Figure 2/H.235.7 – Security scenario with MIKEY and SRTP** + +All the key management protocols described in this Recommendation proceed in two stages: + +- Stage 1 occurs during the H.225.0 RAS and Call Signalling phase. For the symmetric-key MIKEY protocols (MIKEY-PS or MIKEY-DHHMAC) this stage establishes an end-to-end shared $ZZ_{AB}$ between the endpoints A and B that is deployed as a pre-shared secret for MIKEY. For the asymmetric MIKEY protocols (MIKEY-PK-SIGN and MIKEY-DH-SIGN) this stage establishes dynamic shared secrets between the endpoint and its next hop (typically its serving gatekeeper); the dynamic shared secret is not related to MIKEY but serves to secure the H.225.0 Call Signalling between the endpoint and its next hop. +- Stage 2 occurs during the H.225.0 Call Signalling/H.245 protocol phases. This stage negotiates and runs the MIKEY protocol (MIKEY-PS, MIKEY-DHHMAC, MIKEY-PK-SIGN or MIKEY-DH-SIGN) between the endpoints A and B and establishes the MIKEY TGK. During stage 2, the MIKEY endpoints may also run the MIKEY re-keying and key update protocol to refresh or update the TGK. Terminating a call and discarding key material (TGK) may further occur during stage 2. + +## 7.1 MIKEY operation at "session level" + +The MIKEY key management protocols may operate on a "session-level"; i.e., the MIKEY TGK is applied for more than one media stream. It is recommended to run MIKEY at "session level" during the **TerminalCapability** handshake. + +**TerminalCapabilitySet** shall use **h235SecurityCapability** where **genericH235SecurityCapability** is used within **encryptionAuthenticationAndIntegrity** as follows: + +- **capabilityIdentifier** shall hold one of the MIKEY OIDs within **standard**; +- **maxbitRate** and **collapsing** remain unused; +- **nonCollapsing** with the following **GenericParameters** set when MIKEY is executed at a "session level" for all logical channels: + - **parameterIdentifier**: in **standard** using the value 0 to indicate MIKEY at "session level". + - **parameterValue** with the MIKEY (I or R) binary-encoded message within **octetString**. + - **supersedes** remains empty/unused. +- **nonCollapsingRaw** remains unused; +- **transport** (unused or default transport parameters). + +**OpenLogicalChannel** and **OpenLogicalChannelAck** shall not use **encryptionSync** for MIKEY operating at "session level". Likewise, **RequestMode** shall not use **genericModeParameters** of **ModeElement** for MIKEY when MIKEY is operating at "session level". + +**MiscellaneousCommand** shall use **encryptionUpdate** where **genericParameter** is used as follows: + +- **parameterIdentifier**: in **standard** using the value of 0 to indicate MIKEY TGK re-keying and CSB updating at "session level". +- **parameterValue** with the MIKEY (I or R) binary-encoded message within **octetString**. +- **supersedes** remains empty/unused. + +**LogicalChannelNumber** shall be ignored for MIKEY at session level and may hold any value. + +**RequestMode** shall use **capabilityIdentifier** within **genericModeParameters** of **ModeElement** as follows: + +- **capabilityIdentifier** shall hold one of the MIKEY OIDs within **standard**; +- **maxbitRate** and **collapsing** remain unused; +- **nonCollapsing** with the following **GenericParameters** set when MIKEY is executed at a "session level" for a particular logical channel: + - **parameterIdentifier**: in **standard** using the value 0 to indicate MIKEY at "session level". + - **parameterValue** with the MIKEY (I or R) binary encoded message within **octetString**. + - **supersedes** remains empty/unused. +- **nonCollapsingRaw** remains unused; +- **transport** (unused or default transport parameters). + +## 7.2 MIKEY operation at "media level" + +Likewise, the MIKEY key management protocols may alternatively operate on a "media-level"; i.e., the MIKEY TGK is applied only for a specific logical channel on a media stream. The **TerminalCapability** handshake should be used to negotiate the MIKEY protocol while **OpenLogicalChannel/Ack** should be used to transport the encoded MIKEY message. + +**TerminalCapabilitySet** shall use **h235SecurityCapability** where **genericH235SecurityCapability** is used within **encryptionAuthenticationAndIntegrity** as follows: + +- **capabilityIdentifier** shall hold one of the MIKEY OIDs within **standard**; +- **maxbitRate**, **nonCollapsing** and **collapsing** remain unused; +- **nonCollapsingRaw** remains unused; +- **transport** (unused or default transport parameters). + +**OpenLogicalChannel** or **OpenLogicalChannelAck** shall use the **genericParameter** within **encryptionSync** as follows: + +- **parameterIdentifier**: in **standard** using the value of the parameter identifier (see Table 1) corresponding to the negotiated MIKEY protocol; +- **parameterValue** with the MIKEY (I or R) binary-encoded message within **octetString**; +- **supersedes** remains empty/unused; +- **synchFlag** in **encryptionSync** shall be set to the dynamic payload number. **h235key** shall not be used by this Recommendation and shall be an empty octet string. **escrowentry** shall not be used. + +**MiscellaneousCommand** shall use **encryptionUpdate** where **genericParameter** within **encryptionSync** is used as follows: + +- **parameterIdentifier**: in **standard** using the value of the parameter identifier (see Table 1) corresponding to the negotiated MIKEY protocol; +- **parameterValue** with the MIKEY (I or R) binary-encoded message within **octetString**; +- **supersedes** remains empty/unused. + +**RequestMode** shall use **capabilityIdentifier** within **genericModeParameters** of **ModeElement** as follows: + +- **capabilityIdentifier** shall hold one of the MIKEY OIDs within **standard**; +- **maxbitRate** and **collapsing** remain unused; +- **nonCollapsing** with the following **GenericParameters** set when MIKEY is executed at a "media level" for a particular logical channel: + - **parameterIdentifier**: in **standard** using the value of the parameter identifier (see Table 1) corresponding to the negotiated MIKEY protocol. + - **parameterValue** with the MIKEY (I or R) binary-encoded message within **octetString**. + - **supersedes** remains empty/unused. +- **nonCollapsingRaw** remains unused; +- **transport** (unused or default transport parameters). + +## 7.3 MIKEY capability negotiation + +If MIKEY protocols are conveyed both in Terminal Capability Set/Request Mode and Open Logical Channel handshake, then the MIKEY in the Open Logical Channel handshake shall take precedence and overwrite prior key management information gained during Terminal Capability Set/Request Mode. + +Since endpoints may not implement the full set of all MIKEY key management protocols, or may even not have implemented any of them (i.e., endpoints potentially do not support this Recommendation at all), calling endpoints may not know about the supported MIKEY capabilities + +at the called endpoint. Therefore, it is recommended that the MIKEY key management capability be negotiated using Terminal Capability Set handshakes. + +During terminal capability negotiation, the calling endpoint should indicate its supported and acceptable MIKEY key management protocols. For this, the calling endpoint should indicate its supported MIKEY security capabilities. Within **genericH235SecurityCapability**, the calling endpoint shall set **capabilityIdentifier** to the OID value (see Table 1) according to the preferred security profile and MIKEY key management. The calling endpoint is also encouraged to supply other supported MIKEY protocols, in decreasing preference order according to its security policy and constraints. + +A called endpoint that does not support this Recommendation shall reject the call using **ReleaseComplete** with **ReleaseCompleteReason** set to **securityDenied** or may continue unsecured if allowed by its security policy rules. The caller is able to deduce that the callee does not support the requested MIKEY capability by inspecting the returned capability that does not convey a MIKEY capability. + +A called endpoint that supports this Recommendation but does not support a requested MIKEY protocol capability shall indicate its supported and acceptable MIKEY protocols during the Terminal Capability Set negotiation handshake. + +A called endpoint that supports this Recommendation and a requested MIKEY protocol, but does not support a particular combination of MIKEY/SRTP security algorithms and parameters (i.e., MIKEY security policy, SP), shall convey a MIKEY error message as response (see RFC 3830 sections 5.1.1, 5.1.2 and 6.1.2). The called endpoint should include its supported and acceptable MIKEY security policy (SP) with MIKEY/SRTP security algorithms and parameters. + +This Recommendation shall use tunnelling of H.245 messages within H.225.0 Call Signalling for the purpose of securing the H.225.0 Call Signalling messages. This Recommendation may even use non-tunnelling of H.245 message but then it is required that at least an integrity-protected secured transport (TLS, IPsec) be used to secure the H.245 messages. This variant is not further detailed in this Recommendation. + +This Recommendation should also preferably use fast connect where the tunnelled H.245 messages are encapsulated within H.225.0 Call Signalling Setup and CallProceeding-to-Connect. This would allow completing the MIKEY handshakes within two roundtrips at most. + +In order to protect against down-grade attacks during capability negotiation, an endpoint conforming to this specification shall adhere to the procedure described in RFC 3830 section 6.15 where the caller constructs a list of offered MIKEY key management protocol identifiers (KMIDs); see RFC 3830 section 8.3, and includes this list within the MIKEY general extension payload of each offered MIKEY protocol. + +For a full-duplex channel, SRTP is instantiated twice, once in each direction; while only one dynamic MIKEY master key (TGK) is negotiated between the H.323 endpoints. The endpoints instantiate directional SRTP session keys by applying distinct MIKEY crypto session identifiers to the MIKEY and SRTP key derivation function. + +# 8 Security profile using symmetric security techniques + +This clause describes a security profile of this Recommendation where only symmetric security techniques are deployed. + +Figure 3 shows a scenario that assumes (administered or configured) hop-by-hop shared secrets among the H.323 entities in the H.323 domain (*sa*, *sb* and *sl*); thereby permitting the deployment of H.235.1 baseline security (message authentication and/or integrity) of the H.225.0 RAS and Call signalling protocols. For ensuring authenticity (i.e., integrity) of the signalling messages exchanged + +between EP B and EP A, it is required that H.235.1 baseline security is deployed in a hop-to-hop fashion. + +Endpoint B is assumed to be loosely time-synchronized with the other H.323 endpoints; otherwise MIKEY is not able to run securely. + +NOTE – This Recommendation does not describe any means for (securely) synchronizing time clocks among the involved entities. It is generally assumed that such time synchronization can be achieved within corporate networks. + +![Diagram of Figure 3/H.235.7 – Hop-by-Hop scenario only with shared secrets. The diagram shows two H.323 endpoints, A and B, connected via two gatekeepers, GK D and GK E. H.323 signaling flows from EP A to GK D, then to GK E, and finally to EP B. SRTP data flows from EP B to GK E, then to GK D, and finally to EP A. Above the endpoints, three shared secrets are indicated: 'Shared-secret sa' between EP A and GK D, 'Shared-secret sl' between GK D and GK E, and 'Shared-secret sb' between GK E and EP B. A bracket labeled 'Dyn. DH shared-secret ZZ_AB' spans from EP A to EP B. Another bracket labeled 'Dyn. MIKEY TGK' also spans from EP A to EP B. Below the diagram, three 'H.235.1 Baseline security profile' labels are shown, each with a corresponding hatched pattern box. The label 'H.235.7_F03' is in the bottom right corner.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Diagram of Figure 3/H.235.7 – Hop-by-Hop scenario only with shared secrets. The diagram shows two H.323 endpoints, A and B, connected via two gatekeepers, GK D and GK E. H.323 signaling flows from EP A to GK D, then to GK E, and finally to EP B. SRTP data flows from EP B to GK E, then to GK D, and finally to EP A. Above the endpoints, three shared secrets are indicated: 'Shared-secret sa' between EP A and GK D, 'Shared-secret sl' between GK D and GK E, and 'Shared-secret sb' between GK E and EP B. A bracket labeled 'Dyn. DH shared-secret ZZ\_AB' spans from EP A to EP B. Another bracket labeled 'Dyn. MIKEY TGK' also spans from EP A to EP B. Below the diagram, three 'H.235.1 Baseline security profile' labels are shown, each with a corresponding hatched pattern box. The label 'H.235.7\_F03' is in the bottom right corner. + +**Figure 3/H.235.7 – Hop-by-Hop scenario only with shared secrets** + +The basic approach to this scenario is that the MIKEY-PS key distribution protocol (symmetric using pre-shared secrets), or if perfect forward secrecy is of concern, the MIKEY-DHHMAC key agreement protocol (Diffie-Hellman using HMAC), is being deployed in the H.323 domain. RFC zzzz is offered as an option complementing MIKEY, see Appendix I. + +For EP B (MIKEY initiator) calling EP A (MIKEY responder), a dynamic shared secret $ZZ_{AB}$ is established between EP A and EP B as part of H.225.0 RAS and Setup for a call. The $ZZ_{AB}$ dynamic shared secret is used as the MIKEY pre-shared secret further on, from which MIKEY in EP A and in EP B derives symmetric encryption and authentication keys (not shown in this figure). + +The calling EP B generates the MIKEY *TGK* (this is actually a master key) for the peer EP A. EP B builds the MIKEY protocol messages and encapsulates the entire MIKEY message in a container within the tunnelled **TerminalCapabilitySet/OpenLogicalChannel** message. GK E in a GK-routed environment would simply forward the MIKEY container to the other endpoint A without any decoding of MIKEY itself. EP A terminates the MIKEY protocol in the H.323 domain. + +Thus, EP B and EP A establish a *TGK*. + +The MIKEY-PS or MIKEY-DHHMAC protocol runs between EP B and EP A. In this way, the endpoints obtain the *TGK* and are able to derive the SRTP/SRTCP session keys. SRTP and SRTCP protocols apply these session keys end-to-end. + +NOTE 1 – MIKEY provides all the necessary parameters for SRTP (algorithms, key lengths, key lifetime, etc.) as part of the conveyed MIKEY policies. + +The gatekeepers are not actively involved in MIKEY processing and act as a store and forwarding relay of the encapsulated MIKEY messages. + +For a call setup originating from the EP A, the procedure is similar in the reverse direction with EP A being the initiator and EP B the recipient. + +NOTE 2 – The scenario shown in Figure 3 also supports the direct-routed call signalling model with non-routing gatekeeper(s). In such a direct-routed environment, the H.225.0 call signalling messages (Setup etc.) + +would be sent end-to-end within the H.323 domain without being relayed by the gatekeeper. See Appendix II for illustrations on how to use H.235.4 for that purpose. + +NOTE 3 – MIKEY uses timestamps within the security protocol as a means to ensure replay protection of the key management message. This demands that the clocks of the endpoints are loosely time-synchronized (within some acceptable clock skew). It is believed that such time-synchronization can be achieved using manually configured time clocks or some network time synchronization protocol (e.g., NTP RFC 1305). As such, time synchronization within the H.323 domain should be feasible at least for corporate networks; see also RFC 3830 sections 5.4 and 9.3 + +NOTE 4 – The combination of fast start and early media in conjunction with the MIKEY-DHHMAC protocol is not recommended. If fast start and early media is required then endpoints shall not use MIKEY-DHHMAC but rather apply MIKEY-PS. + +NOTE 5 – A scenario with only a single gatekeeper is a special case of the shown scenario with multiple gatekeepers. In this case, far-end gatekeeper/endpoint discovery is not necessary using LRQ/LCF. + +The following provides more detailed message flows of the scenario in Figure 3. This scenario assumes one or more routing gatekeepers within the H.323 domain where H.245 messages are being tunnelled within H.225.0 and fast start is applied. + +NOTE 6 – The flow diagrams also cover a direct-routed case (with non-routing gatekeepers) where H.225.0 call signalling messages are being exchanged directly between the endpoints without being forwarded by any gatekeeper, see Appendix II. + +The procedure described in this clause establishes an end-to-end shared secret $ZZ_{AB}$ among the H.323 endpoints EP A and EP B during stage 1 using Diffie-Hellman key agreement. This Diffie-Hellman key agreement occurs during the H.225.0 RAS registration and admission phase and, in case of multiple gatekeepers, during the inter-gatekeeper **LRQ/LCF**. The generated Diffie-Hellman shared secret serves as an end-to-end authentication key and lasts during the call. The MIKEY-PS (or MIKEY-DHHMAC) protocol occurs during stage 2 call establishment separately and establishes the MIKEY call-based secrets for the bearer channel. + +Appendix II describes an alternative and optional procedure using the DRC1 procedure of H.235.4 to let the gatekeeper generate and distribute a shared secret to EP A and EP B. + +The diagram in Figure 4 also shows the H.235.1 baseline security profile where each message is being secured entirely (authentication and integrity). Yet, similar message flows result when the authentication-only option of the baseline security profile is being applied (not shown). In this case, the HMAC shall not be computed over the entire message but rather only upon a subset (**ClearToken** inside **CryptoToken**) of the RAS/H.225.0 message. + +The example message flow shows the case for EP B (MIKEY initiator) calling EP A (MIKEY responder) using fast start (see Figure 4). The H.323 endpoints A and B initially register with the gatekeeper using **RRQ** and submit their DH half-key ( $g^a$ and $g^b$ ). The **ClearToken** (within the **CryptoHashedToken**) shall be used to convey the Diffie-Hellman half-key during **RRQ** and **ACF**. For this reason, the **challenge** field shall not be used. + +The Diffie-Hellman half-key shall be conveyed in **dhkey** as part of the **ClearToken**. The **ClearToken** shall use OID "TG" (see 8.5) instead of the baseline H.235.1 **ClearToken** OID "T", indicating that this security profile is being used in conjunction with H.235.1. The gatekeeper shall keep each half-key as long as the endpoint is registered. Endpoints when executing keep-alives or using lightweight re-registration (re-RRQ) shall not include any DH half-key. The **RCF** shall use the "TG" OID in the **ClearToken** to indicate that the gatekeeper supports this security profile. + +EP B trying to call EP A, asks for admission from the gatekeeper D (**ARQ**). The **ARQ** shall use the "TG" OID in the **ClearToken**. The OID "TG" shall be used in any other RAS messages within the **ClearToken** too. + +The scenario covers multiple, chained gatekeepers but may equally also support only a single gatekeeper. Discovery of the far-end endpoint should be accomplished according to 8.1.6/H.323 + +"Optional called endpoint signalling" using **LRQ/LCF**. This is how the initiating endpoint locates the far-end GK zone and thereby obtains the Diffie-Hellman half-key of the targeted called endpoint. If GK E needs to locate the far-end GK zone, then GK E shall send a **LRQ** message. For the multicast case, the **generalID** in the CryptoToken of **LRQ** shall not be used. If GK D does not support this profile, then GK D shall return **LRJ**. Otherwise, GK D shall return **LCF** that includes the Diffie-Hellman half-key of EP A. GK E shall then reply with **ACF** including the Diffie-Hellman half-key of EP A. If GK E was not able to locate the far-end endpoint A then GK E shall return **ARJ**. + +The communication between two gatekeepers shall be secured according to H.235.1. For this, it is assumed that a common shared secret *sl* is available. Since **LRQ** among gatekeepers is typically a multicast message, the shared secret *sl* typically cannot be a pair-wise shared secret but is assumed to be actually a group-based shared secret within the potential cloud of gatekeepers. This assumption limits scalability in the general case, and does not provide source authentication. However, it is believed that in corporate networks with a limited, small number of well-known gatekeepers, such constraint and security limitations are still acceptable. Securing inter-gatekeeper multicast communication using digital signatures could overcome these limitations; yet this remains for further study. + +EP B obtains the Diffie-Hellman half-key of EP A (**ACF**). The **ACF** shall hold the Diffie-Hellman key of the called endpoint within **dhkey** within the baseline **ClearToken** of H.235.1 but using OID "TG" instead of "T". Any other fields within the **ClearToken** shall not be modified by this security profile. + +NOTE 7 – The endpoints operate with a DH half-key that is static during the overall registration time and for all calls. This should not be a security weakness as long as each endpoint applies truly random half-keys. + +However, the endpoints shall provide a fresh 512 bit random value (i.e., 64 octets) within **challenge** along with their DH half-key, (see RFC 2631, section 2.3). These **challenge** values are call-based and introduce the necessary randomness and timeliness in the DH key generation. + +The originating EP B is then able to compute $g^{ab}$ and then the dynamic shared secret $ZZ_{AB}$ using a random **challenge** with the result obtained from MIKEY-PRF( $g^{ab}$ , 0x12F905FE || **challenge**) (see RFC 3830 sections 4.1.2-4.1.4). MIKEY is then able to derive the encryption (*Me*) and authentication keys (*Ma*) using the MIKEY-PRF (see RFC 3830 sections 4.1.2-4.1.4). + +During stage 2, the originating EP B shall generate a fresh MIKEY *TGK* and then shall build the MIKEY I\_message Imsg according to the MIKEY-PS protocol using *Me* and *Ma*; also the SRTP session keys can be derived from the *TGK* as described by RFC 3711, section 4.3 (not shown in the figures). + +The MIKEY I\_message shall be binary-encoded. + +The originating EP B should always include its DH half-key within **dhkey** in a **ClearToken**, thereby also enabling the GK-supported direct-routed model. The **ClearToken** shall be included as part of the Setup message and shall be sent towards the peer EP A. A routing gatekeeper shall forward the conveyed **ClearToken** (without modification of the MIKEY messages) to the next hop. + +The receiving EP A then computes $g^{ab}$ and the dynamic shared secret $ZZ_{AB}$ from MIKEY-PRF( $g^{ab}$ , 0x12F905FE || **challenge**) (see RFC 3830, sections 4.1.2-4.1.4). Then MIKEY derives the encryption (*Me*) and authentication keys (*Ma*) using the MIKEY-PRF (see RFC 3830, sections 4.1.2-4.1.4). Then the conveyed *TGKs* can be retrieved. + +From the *TGK* the receiving EP A is then able to derive the SRTP session keys as described by RFC 3711 section 4.3 (not shown in the figures). + +EP A may build a similar R\_message Rmsg but shall build that R\_message only when requested by EP B or if necessary (DH). That R\_message is being conveyed within the CallProceeding-to-Connect message (CP/C). + +The CallProceeding-to-Connect message (CP/C) is sent towards EP B. + +![Sequence diagram showing the interaction between H.323 EP A, GK D, GK E, and H.323 EP B. The diagram is divided into Stage 1 and Stage 2. Stage 1 involves key exchange and challenge-response. Stage 2 involves setup, ARQ, ACF, and CP/C messages. The diagram also shows the derivation of shared secrets sa, sl, and sb from a dynamic shared TGK.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg) + +dyn. shared H.323 secret $ZZ_{AB} = \text{MIKEY-PRF}(g^{ab}, 0x12F905FE \parallel \text{challenge})$ , + dyn. shared MIKEY encryption key $Me$ , + dyn. shared MIKEY authentication key $Ma$ + +Dyn. shared TGK (MIKEY) + +shared secret $sa$      Shared secret $sl$      shared secret $sb$ + +**Stage 1:** + +- EP A: $a := \text{rand}()$ +- EP A → GK D: RRQ("TG", $g^a$ , $\text{HMAC}_{sa}(\text{RRQ})$ ) +- GK D → EP A: RCF("TG", $\text{HMAC}_{sa}(\text{RCF})$ ) +- EP B: $b := \text{rand}()$ +- EP B → GK E: RRQ("TG", $g^b$ , $\text{HMAC}_{sb}(\text{RRQ})$ ) +- GK E → EP B: RCF("TG", $\text{HMAC}_{sb}(\text{RCF})$ ) +- EP B → GK E: ARQ("TG", IDA, $\text{HMAC}_{sb}(\text{ARQ})$ ) +- GK E → EP B: ACF("TG", $g^a$ , $\text{HMAC}_{sb}(\text{ACF})$ ) +- EP B → GK E: Setup("TG", Imsg, $g^b$ , challenge, $\text{HMAC}_{sb}(\text{Setup})$ ) +- GK E → GK D: Setup("TG", Imsg, $g^b$ , challenge, $\text{HMAC}_{sl}(\text{Setup})$ ) +- GK D → EP A: Setup("TG", Imsg, $g^b$ , challenge, $\text{HMAC}_{sa}(\text{Setup})$ ) + +**Stage 2:** + +- EP A → GK D: ARQ("TG", $\text{HMAC}_{sa}(\text{ARQ})$ ) +- GK D → EP A: ACF("TG", $\text{HMAC}_{sa}(\text{ACF})$ ) +- EP A → GK D: CP/C("TG", Rmsg, $\text{HMAC}_{sa}(\text{CP/C})$ ) +- GK D → GK E: CP/C("TG", Rmsg, $\text{HMAC}_{sl}(\text{CP/C})$ ) +- GK E → EP B: CP/C("TG", Rmsg, $\text{HMAC}_{sb}(\text{CP/C})$ ) + +See Figure 5 + +See Figure 6 + +H.235.7\_F04 + +Sequence diagram showing the interaction between H.323 EP A, GK D, GK E, and H.323 EP B. The diagram is divided into Stage 1 and Stage 2. Stage 1 involves key exchange and challenge-response. Stage 2 involves setup, ARQ, ACF, and CP/C messages. The diagram also shows the derivation of shared secrets sa, sl, and sb from a dynamic shared TGK. + +**Figure 4/H.235.7 – Example endpoint B calling endpoint A (GK-routed) with MIKEY-preshared** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $ \left. \begin{aligned} & \text{challenge} := \text{rand}() \\ & ZZ_{AB} = \text{MIKEY-PRF}(g^{ab}, 0x12F905FE \parallel \text{challenge}) \\ & Me := \text{PRF}(ZZ_{AB}, \dots), Ma := \text{PRF}(ZZ_{AB}, \dots) \\ & TGK := \text{rand}() \\ & I := \text{HDR}, T, \text{challenge}, [ID_B], \{SP\}, \text{ENC}_{Me}(TGK) \\ & \text{Imsg} := I, \text{MAC}(Ma, I) \end{aligned} \right\} \text{MIKEY} $ | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Figure 5/H.235.7 – MIKEY-preshared processing by EP B** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $ \left. \begin{aligned} & ZZ_{AB} = \text{MIKEY-PRF}(g^{ab}, 0x12F905FE \parallel \text{challenge}) \\ & Me := \text{PRF}(ZZ_{AB}, \dots) \quad Ma := \text{PRF}(ZZ_{AB}, \dots) \\ & \text{retrieve } TGK \\ & \text{Rmsg} := \text{HDR}, T, [ID_A], \text{MAC}(Ma, \text{Rmsg} \parallel ID_B \parallel ID_A \parallel T) \end{aligned} \right\} \text{MIKEY} $ | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Figure 6/H.235.7 – MIKEY-preshared processing by EP A** + +## 8.1 Terminating a H.323 call + +Since the involved endpoints maintain the state for MIKEY and SRTP, a proper termination procedure is vital. Figure 7 shows example message flows in case EP B (MIKEY initiator) terminates a call. Basically, the flow is according to 8.5/H.323 "Phase E – Call termination". + +NOTE – Figure 7 also shows optional disengage procedures for the case, when the endpoints completely de-register. The endpoints should then also discard the private DH-key ( $a$ or $b$ ) and the public DH half-key ( $g^a$ or $g^b$ ). + +Since the procedure for terminating a call is independent of this security profile, any applicable OID of the underlying security profile (H.235.1, H.235.3 etc.) may be used; thus, Figure 7 does not show any OID. + +If the endpoint registers again with the gatekeeper, then new DH half-keys shall be generated. However, complete de-registration is not necessary in any circumstance just for terminating the call. If the endpoint decides to stay registered with the gatekeeper, then the static DH half-keys may continue to be used. + +In case the endpoints stay registered and disengage is not being applied, the endpoints shall discard just the call-related information including the peer DH half-key, the **challenge**, the MIKEY keys $Me$ , $Ma$ , $TGK$ and related SRTP session information. + +![Sequence diagram showing the termination of a call by endpoint B. The diagram involves H.323 EP A, GK D, GK E, and H.323 EP B. It shows the exchange of Facility, ReleaseComplete, DRQ, and DCF messages, with corresponding HMAC calculations and discarding of old keys.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +dyn. shared H.323 secret $ZZ_{AB} = \text{MIKEY-PRF}(g^{ab}, 0x12F905FE \parallel \text{challenge})$ , +dyn. shared MIKEY encryption key $Me$ , +dyn. shared MIKEY authentication key $Ma$ + +Dyn. shared $TGK$ (MIKEY) + +Shared secret $sa$                      Shared secret $sl$                      Shared secret $sb$ + +``` + +sequenceDiagram + participant EP_A as H.323 EP A + participant GK_D as GK D + participant GK_E as GK E + participant EP_B as H.323 EP B + + Note right of EP_A: dyn. shared H.323 secret ZZ_AB = MIKEY-PRF(g^ab, 0x12F905FE || challenge), +dyn. shared MIKEY encryption key Me, +dyn. shared MIKEY authentication key Ma + Note right of EP_A: Dyn. shared TGK (MIKEY) + Note right of EP_A: Shared secret sa + Note right of GK_D: Shared secret sl + Note right of EP_B: Shared secret sb + + EP_B->>GK_E: Facility("TG", ESC, HMAC_sb(Facility)) + GK_E->>GK_D: Facility("TG", ESC, HMAC_sl(Facility)) + GK_D->>EP_A: Facility("TG", ESC, HMAC_sa(Facility)) + EP_A->>GK_D: Facility("TG", ESC, HMAC_sa(Facility)) + GK_D->>GK_E: Facility("TG", ESC, HMAC_sl(Facility)) + GK_E->>EP_B: Facility("TG", ESC, HMAC_sb(Facility)) + EP_B->>GK_E: ReleaseComplete("TG", HMAC_sb(ReleaseComplete)) + GK_E->>GK_D: ReleaseComplete("TG", HMAC_sl(ReleaseComplete)) + GK_D->>EP_A: ReleaseComplete("TG", HMAC_sa(ReleaseComplete)) + EP_A->>GK_D: ReleaseComplete("TG", HMAC_sa(ReleaseComplete)) + Note left of EP_A: Discard: +challengeString, ZZ_AB, g^b, +Me, Ma, TGK_BA + EP_A->>GK_D: DRQ("TG", HMAC_sa(DRQ)) + GK_D->>EP_A: DCF("TG", HMAC_sa(DCF)) + Note left of EP_A: Discard: +a, g^a + EP_B->>GK_E: DRQ("TG", HMAC_sb(DRQ)) + GK_E->>EP_B: DCF("TG", HMAC_sb(DCF)) + Note right of EP_B: Discard: +challengeString, ZZ_AB, g^a, +Me, Ma, TGK + Note right of EP_B: Discard: +b, g^b + +``` + +H.235.7\_F07 + +Sequence diagram showing the termination of a call by endpoint B. The diagram involves H.323 EP A, GK D, GK E, and H.323 EP B. It shows the exchange of Facility, ReleaseComplete, DRQ, and DCF messages, with corresponding HMAC calculations and discarding of old keys. + +**Figure 7/H.235.7 – Example endpoint B terminates a call** + +## 8.2 TGK re-keying and CSB updating + +MIKEY has built-in support for TGK re-keying and/or CSB information updating. The profile of this Recommendation shall use the MIKEY-PS procedure in RFC 3830, section 4.5, or if perfect forward secrecy is of concern, RFC zzzz, section 3.1 for this purpose that allows updating the TGK before expiration, or to update other information without changing the TGK. + +The TGK re-keying and CSB updating mechanism is useful to protect a bundle of logical channels under the same security policy. For this, it is recommended running the (full) MIKEY-preshared protocol as described in clause 8 just for the first logical channel. Any subsequent logical channel that is to apply the same MIKEY security policy or the same TGK, should use the CSB updating mechanism without the TGK re-keying mechanism in this clause by making reference to the initial CSB-ID and by omitting updated TGK data. This allows setting up logical channels or MIKEY crypto sessions more efficiently than by running the full MIKEY protocol on each logical channel. + +The MIKEY TGK re-keying or CSB updating messages shall be encapsulated and conveyed in a **MiscellaneousCommand** within a Facility message. The **tokenOID** of the **ClearToken** shall be set to "TG". + +If MIKEY is run at "media level", EP B has to determine for which logical channel the TGK re-keying and/or CSB updating should apply. EP A as the responder would equally use the **MiscellaneousCommand** within Facility to convey the MIKEY R\_message (if any). + +For TGK re-keying (see Figure 8), the EP B as the MIKEY initiator shall generate a new TGK. + +EP A as the responder may confirm the obtained TGK re-keying message if necessary as requested by EP B. EP A builds similar R\_messages. EP B sends the R\_message within the Facility message towards EP A. + +For CSB update, the above procedure is similar except that the MIKEY message shall not hold any TGK. + +![Sequence diagram for Figure 8/H.235.7 showing endpoint B updating a key. The diagram illustrates the exchange of Facility messages between H.323 EP A, GK D, GK E, and H.323 EP B. EP B initiates the process by generating a new TGK and sending an Imsg. EP A responds with an Rmsg. The diagram also shows the hierarchy of shared keys: dyn. shared MIKEY encryption key Me, dyn. shared MIKEY authentication key Ma, Dyn. shared TGK (MIKEY), Shared secret sa, Shared secret sl, and Shared secret sb.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +The diagram illustrates the sequence of messages for updating a key. At the top, a hierarchy of shared keys is shown using brackets and labels: + +- dyn. shared MIKEY encryption key $Me$ , +- dyn. shared MIKEY authentication key $Ma$ +- Dyn. shared TGK (MIKEY) +- Shared secret $sa$ +- Shared secret $sl$ +- Shared secret $sb$ + +The sequence of entities is: H.323 EP A, GK D, GK E, and H.323 EP B, connected by H.323 links. + +- EP B generates: $TGK := rand()$ , $I := HDR, T, [ID_B], \{SP\}, [ENC_{Me}(TGK)]$ , $Imsg := I, MAC(Ma, I)$ . +- EP B sends to GK E: Facility("TG", Imsg), $HMAC_{sb}(Facility)$ . +- GK E forwards to GK D: Facility("TG", Imsg), $HMAC_{sl}(Facility)$ . +- GK D forwards to EP A: Facility("TG", Imsg), $HMAC_{sa}(Facility)$ . +- EP A performs: [retrieve TGK], $R := HDR, T, [ID_A], V$ , $Rmsg := R, MAC(Ma, R)$ . +- EP A sends to GK D: Facility("TG", Rmsg), $HMAC_{sa}(Facility)$ . +- GK D forwards to GK E: Facility("TG", Rmsg), $HMAC_{sl}(Facility)$ . +- GK E forwards to EP B: Facility("TG", Rmsg), $HMAC_{sb}(Facility)$ . + +The diagram is labeled H.235.7\_F08 at the bottom right. + +Sequence diagram for Figure 8/H.235.7 showing endpoint B updating a key. The diagram illustrates the exchange of Facility messages between H.323 EP A, GK D, GK E, and H.323 EP B. EP B initiates the process by generating a new TGK and sending an Imsg. EP A responds with an Rmsg. The diagram also shows the hierarchy of shared keys: dyn. shared MIKEY encryption key Me, dyn. shared MIKEY authentication key Ma, Dyn. shared TGK (MIKEY), Shared secret sa, Shared secret sl, and Shared secret sb. + +**Figure 8/H.235.7 – Example endpoint B updating a key** + +NOTE – The confirming Facility from EP A to EP B is optional and only necessary when EP B also requests a verification message (MIKEY R\_message) using the V flag in MIKEY HDR. + +This Recommendation does not define any procedures for TGK re-keying and/or CSB updating invoked by the responder; this remains for further study. + +## 8.3 H.245 tunnelling support + +If further logical channels are to be added during a session, H.245 tunnelling mode shall be deployed where the tunnelled H.245 messages are being carried within a Facility message. + +## 8.4 SRTP algorithms + +This security profile shall use the truncated HMAC-SHA1-32 with an authentication tag length $n\_tag$ equal to 32 bits as the default authentication algorithm for RTP. Other authentication tag lengths as those defined by RFC 3711 shall also be supported and shall be negotiated through the MIKEY security policy (SP) parameter as appropriate. + +## 8.5 List of object identifiers + +| | | | +|------|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| "TG" | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 70} | Indicates a baseline ClearToken for H.235.1 in the context of this Recommendation. This OID also indicates that the MIKEY-PRF is used for computing the shared secret $ZZ_{AB}$ . | +|------|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# 9 Security profile using asymmetric security techniques + +This clause describes a security profile of this Recommendation that deploys asymmetric security techniques. Such a scenario provides most scalability. + +The existence of intermediate entities (i.e., gatekeepers) being able to intercept the MIKEY TGK and/or SRTP session keys may not always be acceptable. Figure 9 shows a scenario that deploys Public-Key Infrastructure (PKI) for establishing SRTP media keys fully end-to-end. + +Assumptions: It is assumed that both EP A and EP B possess a private key ( $SK$ ) as well as a certified public key ( $cert$ ). Nevertheless, EP A and GK E as well as EP B and GK D may share (administered/configured) shared secrets in case H.225.0 RAS and call signalling are being secured using H.235.1. It is further assumed that EP A and EP B be loosely time-synchronized, otherwise MIKEY is not able to run securely. + +Message authentication/integrity may be achieved either using pre-configured hop-by-hop shared secrets ( $sa$ , $sb$ and $sl$ ) and the H.235.1 baseline security profile or, in a more general case, using PKI to establish dynamic shared secrets with the H.235.3 hybrid Security profile. + +![Diagram of an end-to-end scenario using PKI with multiple gatekeepers (GKs).](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +``` + +graph LR + subgraph "Dyn shared-secret ZZ_AD" + EPA["H.323 EP A +SK_A, cert_A"] + GKD["GK D +SK_D, cert_D"] + end + subgraph "(Dyn) Shared-secret sl" + GKD --- GKE["GK E +SK_E, cert_E"] + end + subgraph "Dyn shared-secret ZZ_BE" + GKE --- EPB["H.323 EP B +SK_B, cert_B"] + end + EPA <--> |H.323| GKD + GKD <--> |H.323| GKE + GKE <--> |H.323| EPB + EPA <--> |SRTP| EPB + EPA -.-> |MIKEY-PK-SIGN or MIKEY-DH-SIGN| EPB + +``` + +The diagram illustrates a network architecture for secure communication. At the far left is 'H.323 EP A' and at the far right is 'H.323 EP B'. Between them are two gatekeepers, 'GK D' and 'GK E'. Above each entity is its cryptographic material: $SK_A, cert_A$ for EP A, $SK_D, cert_D$ for GK D, $SK_E, cert_E$ for GK E, and $SK_B, cert_B$ for EP B. Above the diagram, three shared secrets are indicated with brackets: 'Dyn shared-secret $ZZ_{AD}$ ' between EP A and GK D, '(Dyn) Shared-secret $sl$ ' between GK D and GK E, and 'Dyn shared-secret $ZZ_{BE}$ ' between GK E and EP B. Below the diagram, three security profiles are indicated with brackets: 'H.235.3 hybrid security profile' for the EP A to GK D segment, 'H.235.1 or H.235.3 hybrid security profile' for the GK D to GK E segment, and 'H.235.3 hybrid security profile' for the GK E to EP B segment. Arrows show H.323 signaling and SRTP media flows between EP A and GK D, GK D and GK E, and GK E and EP B. A label 'H.235.7\_F09' is in the bottom right corner. + +Diagram of an end-to-end scenario using PKI with multiple gatekeepers (GKs). + +Figure 9/H.235.7 – End-to-end scenario using PKI (multiple GKs) + +EP A and EP B run MIKEY-PK-SIGN or MIKEY-DH-SIGN end-to-end and thereby establish the MIKEY TGK from which the end systems derive the SRTP session keys. + +NOTE 1 – MIKEY-PK-SIGN satisfies the requirement of an RSA-based key management. + +NOTE 2 – Using PKI techniques, the more general H.323 environment featuring multiple, chained gatekeepers in a row should quite certainly be better covered than with less scaleable, and limited architectures using symmetric security techniques. + +NOTE 3 – The combination of fast start and early media in conjunction with the MIKEY-DH-SIGN protocol is not recommended. If fast start and early media is required, then endpoints shall not use MIKEY-DH-SIGN but rather apply MIKEY-PK-SIGN. + +The following paragraphs provide more detailed message flows of the scenario in Figure 9. This scenario shows multiple gatekeepers within the H.323 domain. + +The following figures further assume a routing gatekeeper (GK-routed model) where H.245 messages are being tunnelled within H.225.0 (Fast start). + +NOTE 4 – The flow diagrams also cover a direct-routed case (with a non-routing gatekeeper) where H.225.0 call signalling messages are being exchanged directly between the endpoints without being forwarded by any gatekeeper. + +The diagrams also show the H.235.3 hybrid security profile where the initial RAS messages are being secured entirely (authentication and integrity) using digital signatures and optional certificates. This is to establish dynamic shared secrets $ZZ_{BE}$ and $ZZ_{AD}$ between the endpoints and the next hop gatekeeper, thereby making static shared secrets superfluous. Yet, similar message flows result when the authentication-only option of the signature security profile is being applied (not shown). + +The example message flow shows the case for EP B (MIKEY initiator) calling EP A (MIKEY responder) (see Figure 10). + +During stage 1, H.323 endpoints initially register with the next-hop gatekeeper and submit their DH half-key ( $g^a$ and $g^b$ ). + +EP B, trying to call EP A, asks for admission at the gatekeeper E. EP B may request the peer certificate *certC* by including a security profile element in the **ClearToken** in case certificate information is not yet available to the EP. This security profile element shall use the following fields: + +- **elementID** set to 7 indicating a certificate request element; Figure 10 shows this as **certFlag**; +- **paramS** remains unused; +- **element** holds an Element where **flag** is set to TRUE. + +The ARQ and any following RAS and H.225.0 Call signalling messages are secured by the dynamic shared secret $ZZ_{BE}$ using H.235.1 baseline security profile. In case EP B requested certificate lookup, the GK E fetches *certC* from a local or other certificate repository and supplies the result(s) as part of the ACF within **certificate** of the **ClearToken** and includes a security profile element. This security profile element shall use the following fields: + +- **elementID** set to 8 indicating a certificate response element; Figure 10 shows this as **certFlag**; +- **paramS** remains unused; +- **element** holds an Element where **flag** is set to TRUE. + +In case the gatekeeper obtains multiple certificates for a peer endpoint/UA, ACF would actually hold multiple **ClearTokens**, each conveying a single certificate within **certificate**. The endpoint then chooses the appropriate one. However, it may occur that the certificate lookup takes too long; perhaps for example when contacting external repositories. If the gatekeeper is not able to supply the certificate(s) in time, or not at all, ACF is returned with an empty **certificate** in the **ClearToken** that holds a security profile element where: + +- **elementID** set to 8 indicating a certificate response element; +- **paramS** remains unused; +- **element** holds an Element where **flag** is set to FALSE. + +It is then the task of the endpoint to abort and attempt to locate the appropriate certificate by means not specified by this Recommendation. In case the gatekeeper is able to obtain the certificate outside the necessary response time boundary, the gatekeeper should indicate this situation by leaving **certificate** empty and including a security profile element within the **ClearToken** where: + +- **elementID** set to 8 indicates a certificate response element; + +- **paramS** remains unused; +- **element** holds an Element where **flag** is set to TRUE. + +In this case, the GK shall return this ClearToken within ACF. + +During stage 2, the originating EP B (MIKEY initiator) is then able to generate the fresh MIKEY TGK, and compute the related MIKEY I\_message Imsg by applying the MIKEY-PK-SIGN key management protocol (see Figures 11 and 12); or, if perfect forward secrecy is of concern, the MIKEY-DH-SIGN key agreement protocol (Diffie-Hellman using digital signatures). MIKEY-DH-SIGN is offered as an option. + +The SRTP session keys can be derived from the TGK as described by RFC 3711, section 4.3 (not shown in the figures). + +NOTE 5 – Figures 11 and 12 do not show every detail of MIKEY, some parts are not shown in the picture. + +The MIKEY I\_message is binary-encoded and is then being encapsulated in the H.245 **OpenLogicalChannel**. + +The **ClearToken** is enclosed as part of the Setup message and is sent towards EP A. A routing gatekeeper forwards the conveyed MIKEY I\_message (without modification of the MIKEY message) to the next hop. + +In case there are multiple routing gatekeepers, the call signalling messages among the gatekeepers may be secured by applying an administered shared secret and using H.235.1 or H.235.3 and private/public keys. + +From the TGK, EP A is then able to derive the SRTP session keys as described by RFC 3711, section 4.3 (not shown in the figures). + +EP A as the MIKEY responder is able to compile the MIKEY R\_message Rmsg using the MIKEY *Ma* key and include the MIKEY R\_message within the CallProceeding-to-Connect message (CP/C). + +![Sequence diagram showing H.323 call flow between EP A, GK D, GK E, and EP B. Stage 1 involves registration and key exchange (RRQ, RCF, ARQ, ACF). Stage 2 involves call setup and control (Setup, ARQ, ACF, CP/C).](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +Dyn. shared *TGK* (MIKEY) + +dyn shared secret $ZZ_{AD} = g^{ad}$      Shared secret *sl*      dyn shared secret $ZZ_{EB} = g^{eb}$ + +$SK_A, cert_A$      $SK_D, cert_D$      $SK_E, cert_E$      $SK_B, cert_B$ + +H.323 EP A +H.323 +GK D +H.323 +GK E +H.323 +H.323 EP B + +Stage 1 + +Stage 2 + +H.235.7\_F10 + +Sequence diagram showing H.323 call flow between EP A, GK D, GK E, and EP B. Stage 1 involves registration and key exchange (RRQ, RCF, ARQ, ACF). Stage 2 involves call setup and control (Setup, ARQ, ACF, CP/C). + +**Figure 10/H.235.7 – Example EP B calls EP A (multiple GK-routed) with MIKEY-PK-SIGN** + +``` + +TGK := rand() +env-key := rand() +Me, Ma := PRF(env-key, ... || Rand) +PKE := ENCPK-A(env-key, ... || Rand) +K := ENCMe(IDB || [TGK]) +KEMAC := ENCMe(IDB || [TGK]) +M := HMAC-SHA1(Ma, K) +I := HDR, T, rand(), [IDB | CertB], {SP}, [chash], KEMAC, PKE +Imsg := I, SignSK-B(I) + +``` + +**Figure 11/H.235.7 – MIKEY-PK-SIGN processing by EP B** + +``` + +Retrieve env-key, TGK +Ma := PRF(env-key, ... || Rand), +Rmsg := HDR, T, [IDA], HMAC-SHA1(Ma, Rmsg || IDA || IDB || T) + +``` + +**Figure 12/H.235.7 – MIKEY-PK-SIGN processing by EP A** + +A scenario with only a single gatekeeper is a special case of the shown scenario with multiple gatekeepers. In this case, far-end gatekeeper/endpoint discovery is not necessary using LRQ/LCF. + +## 9.1 Terminating a H.323 call + +Since the involved endpoints maintain the state for MIKEY and SRTP, a proper termination procedure is vital. Figure 13 shows an example of message flows in case EP B (MIKEY initiator) terminates a call. Basically, the flow is according to 8.5/H.323 "Phase E – Call termination". + +NOTE – Figure 13 also shows optional disengage procedures for the case, when the endpoints completely de-register. The endpoints should then also discard the private DH-key ( $a$ or $b$ ) and the public DH half-key ( $g^a$ or $g^b$ ). + +Since the procedure for terminating a call is independent of this security profile, any applicable OID of the underlying security profile may be used; thus, Figure 13 does not show any OID. + +If the endpoint registers again with the gatekeeper, then new DH half-keys shall be generated. However, complete de-registration is not necessary in any circumstance just for terminating the call. If the endpoint decides to stay registered with the gatekeeper, then the static DH half-keys may continue to be used. + +In case the endpoints stay registered, and disengage is not being applied, the endpoints shall discard just the call-related information including the peer DH half-key, the **challenge**, the MIKEY keys $Me$ , $Ma$ , $TGK$ and related SRTP session information. + +![Sequence diagram showing the termination of an H.323 call by endpoint B. The diagram illustrates message exchanges between H.323 EP A, GK, and H.323 EP B, including Facility, ReleaseComplete, DRQ, and DCF messages with HMAC calculations. It also shows the discarding of keys and session information at the endpoints.](088921fa3f5a44c8551815122517eefd_img.jpg) + +The diagram illustrates the message flow for terminating an H.323 call when endpoint B is the MIKEY initiator. At the top, a bracket labeled "Dyn. shared TGK (MIKEY)" spans across the GK. Below it, two brackets labeled "Shared secret $sa$ " and "Shared secret $sb$ " are positioned over the GK, indicating the shared secrets used for HMAC calculations. The sequence of messages is as follows: + +- H.323 EP B sends a **Facility(ESC, HMACsb(Facility))** message to the GK. +- The GK forwards this as **Facility(ESC, HMACsa(Facility))** to H.323 EP A. +- H.323 EP A responds with **Facility(ESC, HMACsa(Facility))** to the GK. +- The GK forwards this as **Facility(ESC, HMACsb(Facility))** to H.323 EP B. +- H.323 EP B then sends a **ReleaseComplete(HMACsb(ReleaseComplete))** message to the GK. +- The GK forwards this as **ReleaseComplete(HMACsa(ReleaseComplete))** to H.323 EP A. +- Both endpoints then execute a **Discard: env-key, Me, Ma, TGK** operation. +- H.323 EP A sends a **DRQ(HMACsa(DRQ))** message to the GK. +- The GK forwards this as **DRQ(HMACsb(DRQ))** to H.323 EP B. +- H.323 EP B responds with **DCF(HMACsb(DCF))** to the GK. +- The GK forwards this as **DCF(HMACsa(DCF))** to H.323 EP A. +- Finally, both endpoints execute a **Discard: a, ga** (for EP A) and **Discard: b, gb** (for EP B) operation. + +H.235.7\_F13 + +Sequence diagram showing the termination of an H.323 call by endpoint B. The diagram illustrates message exchanges between H.323 EP A, GK, and H.323 EP B, including Facility, ReleaseComplete, DRQ, and DCF messages with HMAC calculations. It also shows the discarding of keys and session information at the endpoints. + +Figure 13/H.235.7 – Example endpoint B terminates a call + +## 9.2 TGK re-keying and CSB updating + +MIKEY has built-in support for TGK re-keying and/or CSB information updating. This Recommendation shall use the MIKEY-PK-SIGN procedure in RFC 3830, section 4.5 for this purpose that allows updating the TGK before expiration, or to update other information (CSB) without changing the TGK. + +The TGK re-keying and CSB updating mechanism is useful to protect a bundle of logical channels under the same security policy. To this end, it is recommended running the (full) MIKEY-PK-SIGN protocol as described in clause 8 just for the first logical channel. Any subsequent logical channel that is to apply the same MIKEY security policy, or the same TGK, should use the CSB updating mechanism without the TGK re-keying mechanism in this clause by making reference to the initial CSB-ID and by omitting updated TGK data. This allows setting up logical channels or MIKEY crypto sessions more efficiently than by running the full MIKEY protocol on each logical channel. + +The MIKEY TGK re-keying or CSB updating messages shall be enclosed within a **MiscellaneousCommand** of a Facility message. The **tokenOID** of the **ClearToken** shall be set to "SG". + +For MIKEY at "media level", EP B has to determine for which logical channel the TGK re-keying and/or CSB updating should apply. EP A as the responder would equally use the **MiscellaneousCommand** within Facility to convey the MIKEY R\_message (if any). + +For TGK re-keying (see Figure 14), EP B as the MIKEY initiator shall generate a new TGK. mikey shall hold the corresponding MIKEY I\_message. + +The responder (EP A) may confirm the obtained TGK re-keying message if necessary as requested by EP B. EP A builds similar R\_message Rmsg. This R\_message is being conveyed within the Facility message. Rmsg is the corresponding MIKEY response message and shall be conveyed within **octetString** of the **GenericParameter**. EP A sends the Facility message towards EP B. + +For an initiator-initiated CSB update, the above procedure is similar except that the MIKEY message shall not hold any TGK (see Figure 14). + +![Sequence diagram illustrating EP B (Initiator) initiated TGK re-keying and key update. The diagram shows four entities: H.323 EP A, GK D, GK E, and H.323 EP B. Above them, a bracket labeled 'New dyn. shared TGK (MIKEY)' spans across all entities. Below this, three sub-brackets indicate shared secrets: 'dyn shared secret ZZ_AD = g^ad' for EP A and GK D, '(dyn) Shared secret sl' for GK D and GK E, and 'dyn shared secret ZZ_EB = g^cb' for GK E and EP B. Each entity has associated keys and certificates: SK_A, cert_A for EP A; SK_D, cert_D for GK D; SK_E, cert_E for GK E; and SK_B, cert_B for EP B. The sequence of messages is: 1. EP B sends a Facility message to GK E containing 'Facility(\](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +Sequence diagram illustrating EP B (Initiator) initiated TGK re-keying and key update. The diagram shows four entities: H.323 EP A, GK D, GK E, and H.323 EP B. Above them, a bracket labeled 'New dyn. shared TGK (MIKEY)' spans across all entities. Below this, three sub-brackets indicate shared secrets: 'dyn shared secret ZZ\_AD = g^ad' for EP A and GK D, '(dyn) Shared secret sl' for GK D and GK E, and 'dyn shared secret ZZ\_EB = g^cb' for GK E and EP B. Each entity has associated keys and certificates: SK\_A, cert\_A for EP A; SK\_D, cert\_D for GK D; SK\_E, cert\_E for GK E; and SK\_B, cert\_B for EP B. The sequence of messages is: 1. EP B sends a Facility message to GK E containing 'Facility(\ + +**Figure 14/H.235.7 – Example EP B (Initiator) initiated TGK re-keying and key update** + +NOTE – The confirming Facility from EP A to EP B is optional and only necessary when EP B also requested a verification message (MIKEY R\_message) using the V flag in MIKEY HDR. + +This Recommendation does not define any procedures for TGK re-keying and/or CSB updating invoked by the responder; this remains for further study. + +## 9.3 H.245 tunnelling support + +If during a session further logical channels are to be added, H.245 tunnelling mode shall be deployed where the tunnelled H.245 messages are being carried within a Facility message. + +## 9.4 SRTP algorithms + +This security profile shall use the truncated HMAC-SHA1-32 method with an authentication tag length *n\_tag* equal to 32 bits as the default authentication algorithm for RTP. Other authentication tag lengths, as those defined by RFC 3711, shall also be supported and shall be negotiated through the MIKEY security policy (SP) parameter as appropriate. + +## 9.5 List of object identifiers + +| | | | +|------|-----------------------------------------------------------|------------------------------------------------------------------------------------| +| "SG" | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 71} | Indicates a baseline ClearToken for H.235.3 in the context of this Recommendation. | +|------|-----------------------------------------------------------|------------------------------------------------------------------------------------| + +# Appendix I + +### MIKEY-DHHMAC option + +This appendix describes how to deploy the MIKEY-DHHMAC key management option in this security profile. + +This key management option assumes only a security infrastructure where shared keys are available. MIKEY-DHHMAC (RFC zzzz) provides the security property of perfect-forward secrecy (PFS) due to the inherent capability of the Diffie-Hellman mechanism. Thus, this key management option is applicable when PFS is required and PKI or digital certificates are not available. + +This scenario assumes gatekeepers within the H.323 domain. + +The procedure described in this clause establishes an end-to-end shared secret among the H.323 endpoints EP A and EP B using a Diffie-Hellman key agreement scheme. This Diffie-Hellman key agreement occurs during the H.225.0 RAS registration and admission phase and, in the case of multiple gatekeepers, during the inter-gatekeeper LRQ/LCF. The generated Diffie-Hellman shared secret serves as an end-to-end authentication key and lasts during the call. The MIKEY-DHHMAC protocol occurs during call establishment separately and establishes the MIKEY call-based secrets for the bearer channel. + +Figure I.1 illustrates an example where endpoint B is calling endpoint A through a routing GK. The flow is similar to Figure 4 except that the MIKEY-DHHMAC protocol is being deployed. The scenario assumes one or more routing gatekeepers (GK-routed model) where H.245 messages are being tunnelled within H.225.0 (Fast start). Call signalling may or may not pass through a gatekeeper; thus a routing gatekeeper is not necessary to support this scenario. + +NOTE 1 – The flow diagram also covers a direct-routed case (with a non-routing gatekeeper) where H.225.0 call signalling messages are exchanged directly between the endpoints without being forwarded by any gatekeeper. + +The diagram in Figure I.1 also shows the H.235.1 baseline security profile where each message is being secured entirely (authentication and integrity). Yet, similar message flows result when the authentication-only option of the baseline security profile is being applied (not shown). In this case, the HMAC shall not be computed over the entire message but rather only upon a subset (**ClearToken** inside **CryptoToken**) of the RAS/H.225.0 message. + +The example message flow shows the case for EP B (MIKEY initiator) calling EP A (MIKEY responder) using fast start (see Figure I.1). During stage 1, the H.323 endpoints A and B initially register with the gatekeeper using **RRQ** and submit their DH half-key ( $g^a$ and $g^b$ ). The **ClearToken** (within the **CryptoHashedToken**) shall be used to convey the Diffie-Hellman half-key during **RRQ** and **ACF**. For this reason, the **challenge** field shall not be used. + +The Diffie-Hellman half-key shall be conveyed in **dhkey** as part of the **ClearToken**. The **ClearToken** shall use OID "TG" (see 8.5) instead of the baseline H.235.1 **ClearToken** OID "T", indicating that this security profile is being used in conjunction with H.235.1. The gatekeeper shall keep each half-key as long as the endpoint is registered. Endpoints when executing keep-alives or using lightweight re-registration (re-RRQ) shall not include any DH half-key. The **RCF** shall use the "TG" OID in the **ClearToken** to indicate that the gatekeeper supports this security profile. + +EP B trying to call EP A, asks for admission from the gatekeeper D (**ARQ**). The **ARQ** shall use the "TG" OID in the **ClearToken**. The OID "TG" shall be used in any other RAS messages within the **ClearToken** too. + +The scenario covers multiple, chained gatekeepers. Discovery of the far-end endpoint should be accomplished according to 8.1.6/H.323 "Optional called endpoint signalling" using **LRQ/LCF**. This is how the initiating endpoint locates the far-end GK zone and thereby obtains the Diffie-Hellman half-key of the targeted called endpoint. If GK E needs to locate the far-end GK zone, then GK E shall send a **LRQ** message. For the multicast case, the generalID in the **CryptoToken** of **LRQ** shall not be used. If GK D does not support this profile, then GK D shall return **LRJ**. Otherwise, GK D shall return **LCF** that includes the Diffie-Hellman half-key of EP A. GK E shall then reply with **ACF** including the Diffie-Hellman half-key of EP A. If GK E was not able to locate the far-end endpoint A then GK E shall return **ARJ**. + +The communication between two gatekeepers shall be secured according to H.235.1. For this, it is assumed that a common shared secret $s_l$ is available. Since **LRQ** among gatekeepers is typically a multicast message, the shared secret $s_l$ typically cannot be a pair-wise shared secret but is assumed to be actually a group-based shared secret within the potential cloud of gatekeepers. This assumption limits scalability in the general case, and does not provide source authentication. However, it is believed that in corporate networks with a limited, small number of well-known gatekeepers, such constraint and security limitations are still acceptable. Securing inter-gatekeeper multicast communication using digital signatures could overcome those limitations; yet this remains for further study. + +EP B obtains the Diffie-Hellman half-key of EP A (**ACF**). The **ACF** shall hold the Diffie-Hellman key of the called endpoint within **dhkey** within the baseline **ClearToken** of H.235.1 but using OID "TG" instead of "T". Any other fields within the **ClearToken** shall not be modified by this security profile. + +NOTE 2 – The endpoints operate with a DH half-key that is static during the overall registration time and for all calls. This is not a security weakness as long as each endpoint applies truly random half-keys. + +However, the endpoints shall provide a fresh 512 bit random value (i.e., 64 octets) within **challenge** along with their DH half-key, (see RFC 2631, section 2.3). These **challenge** values are call-based and introduce the necessary randomness and timeliness in the DH key generation. + +The originating EP B is then able to compute $g^{ab}$ and then the dynamic shared secret $ZZ_{AB}$ using a random **challenge** with the result obtained from MIKEY-PRF( $g^{ab}$ , 0x12F905FE || **challenge**) (see RFC 3830, sections 4.1.2-4.1.4). Then MIKEY is able to derive the authentication key ( $Ma$ ) using the MIKEY-PRF (see RFC 3830, sections 4.1.2-4.1.4). + +During stage 2, the originating EP B shall generate fresh MIKEY random values $y$ with corresponding $g^y$ and then shall build the MIKEY I\_message Imsg according to the MIKEY-DHHMAC protocol using $Ma$ . + +The MIKEY I\_message shall be binary-encoded. + +The originating EP B should always include its DH half-key within **dhkey** in a **ClearToken**, thereby also enabling the GK-supported direct-routed model. The **ClearToken** shall be included as part of the Setup message and shall be sent towards the peer EP A. A routing gatekeeper shall forward the conveyed ClearToken (without modification of the MIKEY messages) to the next hop. + +The receiving EP A then computes $g^{ab}$ and the dynamic shared secret $ZZ_{AB}$ from $\text{MIKEY-PRF}(g^{ab}, 0x12F905FE \parallel \text{challenge})$ (see RFC 3830, sections 4.1.2-4.1.4). Then MIKEY derives the authentication key (*Ma*) using the MIKEY-PRF (see RFC 3830, sections 4.1.2-4.1.4). EP A then generates a MIKEY random value *w* and computes $g^w$ . Using the received DH half-keys, EP A computes *TGK*. + +From the *TGK*, the receiving EP A is then able to derive the SRTP session keys as described by RFC 3711, section 4.3 (not shown in the figure). + +EP A builds similar R\_message Rmsg. That R\_message is being conveyed within the CallProceeding-to-Connect message (CP/C). Rmsg is the corresponding MIKEY response message which is sent within a CallProceeding-to-Connect message (CP/C) towards EP B. + +The CallProceeding-to-Connect message (CP/C) is sent towards EP B. + +EP B retrieves the DH half-key and computes *TGK*. EP B then derives the SRTP session keys from the *TGKs* as described by RFC 3711, section 4.3 (not shown in the figure). + +![Sequence diagram for H.323 MIKEY-DHHMAC key exchange between endpoints A and B via gatekeepers D and E. The diagram is divided into Stage 1 and Stage 2. Stage 1 involves RRQ, RCF, LRQ, and LCF messages. Stage 2 involves Setup, ARQ, ACF, and CP/C messages. Cryptographic operations involving random numbers, SHA1, PRF, and MAC are shown in boxes for endpoints A and B.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +dyn. shared H.323 secret $ZZ_{AB} = \text{MIKEY-PRF}(g^{ab}, 0x12F905FE \parallel \text{challenge})$ , +dyn. shared MIKEY authentication key $Ma$ + +Dyn. shared $TGK$ (MIKEY) + +shared secret $sa$                      (dyn) Shared secret $sl$                      Shared secret $sb$ + +**Stage 1** + +**Endpoint A:** + +- $a := \text{rand}()$ +- Sends: $\text{RRQ}("TG", g^a)$ , $\text{HMAC}_{sa}(\text{RRQ})$ +- Receives: $\text{RCF}("TG", \text{HMAC}_{sa}(\text{RCF}))$ +- Receives: $g^a$ (from GK D) +- Sends: $\text{LRQ}("TG", \text{HMAC}_{sl}(\text{LRQ}))$ +- Receives: $\text{LCF}("TG", g^a, \text{HMAC}_{sl}(\text{LCF}))$ + +**Gatekeeper D:** + +- Receives: $\text{RRQ}("TG", g^a)$ , $\text{HMAC}_{sa}(\text{RRQ})$ +- Sends: $g^a$ (to Endpoint A) +- Receives: $\text{LRQ}("TG", \text{HMAC}_{sl}(\text{LRQ}))$ +- Sends: $\text{LCF}("TG", g^a, \text{HMAC}_{sl}(\text{LCF}))$ + +**Gatekeeper E:** + +- Receives: $g^b$ (from Endpoint B) +- Sends: $g^b$ (to Endpoint A) + +**Endpoint B:** + +- $b := \text{rand}()$ +- Sends: $\text{RRQ}("TG", g^b)$ , $\text{HMAC}_{sb}(\text{RRQ})$ +- Receives: $\text{RCF}("TG", \text{HMAC}_{sb}(\text{RCF}))$ +- Sends: $\text{ARQ}("TG", \text{HMAC}_{sb}(\text{ARQ}))$ +- Receives: $\text{ACF}("TG", g^a, \text{HMAC}_{sb}(\text{ACF}))$ +- Receives: $g^a$ (from GK E) + +**Stage 2** + +**Endpoint A:** + +- Sends: $\text{Setup}("TG", \text{Imsg}, g^a, \text{challenge})$ , $\text{HMAC}_{sa}(\text{Setup})$ +- Sends: $\text{ARQ}("TG", \text{HMAC}_{sa}(\text{ARQ}))$ +- Receives: $\text{ACF}("TG", \text{HMAC}_{sa}(\text{ACF}))$ +- Internal calculation: + - $w := \text{rand}()$ + - $ZZ_{AB} = \text{SHA1}(g^{ab} \parallel \text{challenge})$ + - $Ma := \text{PRF}(ZZ_{AB}, \dots)$ , $DH_A := g^w$ + - retrieve $DH_B$ + - $TGK := g^{wy}$ + - $\text{Rmsg}_{\text{FWD}} := T, \text{challenge}, [ID_A], ID_B, DH_A, DH_B, \text{MAC}(Ma, \text{Rmsg})$ +- Sends: $\text{CP/C}("TG", \text{Rmsg}, \text{HMAC}_{sa}(\text{CP/C}))$ + +**Gatekeeper D:** + +- Receives: $\text{Setup}("TG", \text{Imsg}, g^a, \text{challenge})$ , $\text{HMAC}_{sl}(\text{Setup})$ +- Sends: $\text{CP/C}("TG", \text{Rmsg}, \text{HMAC}_{sl}(\text{CP/C}))$ + +**Gatekeeper E:** + +- Internal calculation: + - $\text{challenge} := \text{rand}()$ , $y := \text{rand}()$ + - $ZZ_{AB} = \text{SHA1}(g^{ab} \parallel \text{challenge})$ + - $Ma := \text{PRF}(ZZ_{AB}, \dots)$ , $DH_B := g^y$ + - $\text{Imsg} := T, \text{challenge}, [ID_B], \{SP\}, DH_B, \text{MAC}(Ma, \text{Imsg})$ +- Sends: $\text{Setup}("TG", \text{Imsg}, g^a, \text{challenge})$ , $\text{HMAC}_{sb}(\text{Setup})$ +- Receives: $\text{CP/C}("TG", \text{Rmsg}, \text{HMAC}_{sb}(\text{CP/C}))$ + +**Endpoint B:** + +- Internal calculation: + - retrieve $DH_A$ + - $TGK := g^{wy}$ + +H.235.7\_Fl.1 + +Sequence diagram for H.323 MIKEY-DHHMAC key exchange between endpoints A and B via gatekeepers D and E. The diagram is divided into Stage 1 and Stage 2. Stage 1 involves RRQ, RCF, LRQ, and LCF messages. Stage 2 involves Setup, ARQ, ACF, and CP/C messages. Cryptographic operations involving random numbers, SHA1, PRF, and MAC are shown in boxes for endpoints A and B. + +**Figure I.1/H.235.7 – Example endpoint B calling endpoint A (GK-routed) +with MIKEY-DHHMAC** + +### I.1 Terminating a H.323 call + +Since the involved endpoints maintain the state for MIKEY and SRTP, a proper termination procedure is vital. Figure I.2 shows an example of message flows in case EP B (MIKEY initiator) terminates a call. Basically, the flow is according to 8.5/H.323 "Phase E – Call termination". + +NOTE – Figure I.2 also shows optional disengage procedures for the case when the endpoints completely de-register. The endpoints should then also discard the private DH-key ( $a$ or $b$ ) and the public DH half-key ( $g^a$ or $g^b$ ). + +Since the procedure for terminating a call is independent of this security profile, any applicable OID of the underlying security profile (H.235.1, H.235.3, etc.) may be used; thus, Figure I.2 does not show any OID. + +If the endpoint registers again with the gatekeeper, then new DH half-keys shall be generated. However, complete de-registration is not necessary in any circumstance just for terminating the call. If the endpoint decides to stay registered with the gatekeeper, then the static DH half-keys may continue to be used. + +In case the endpoints stay registered and disengage is not being applied, the endpoints shall discard just the call-related information including the peer DH half-key, the **challenge**, the MIKEY keys $Me$ , $Ma$ , $TGK$ and related SRTP session information. + +![Sequence diagram showing the termination of an H.323 call initiated by EP B. The diagram shows message exchanges between H.323 EP A, GK D, GK E, and H.323 EP B. It includes Facility, ReleaseComplete, DRQ, and DCF messages with HMAC calculations. At the bottom, boxes indicate discarded information like challengeString, DH keys, Ma, TGK, and private DH keys a and b.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +dyn. shared H.323 secret $ZZ_{AB} = \text{MIKEY-PRF}(g^{ab}, 0x12F905FE \parallel \text{challenge})$ , +dyn. shared MIKEY encryption key $Me$ , +dyn. shared MIKEY authentication key $Ma$ + +Dyn. shared $TGK$ (MIKEY) + +Shared secret $sa$                      (dyn) shared secret $sl$                      Shared secret $sb$ + +``` + +sequenceDiagram + participant EP_A as H.323 EP A + participant GK_D as GK D + participant GK_E as GK E + participant EP_B as H.323 EP B + + Note over EP_A, EP_B: Shared secrets and keys established + + EP_B->>GK_E: Facility("TG", ESC, HMAC_sb(Facility)) + GK_E->>GK_D: Facility("TG", ESC, HMAC_sl(Facility)) + GK_D->>EP_A: Facility("TG", ESC, HMAC_sa(Facility)) + + EP_A->>GK_D: Facility("TG", ESC, HMAC_sa(Facility)) + GK_D->>GK_E: Facility("TG", ESC, HMAC_sl(Facility)) + GK_E->>EP_B: Facility("TG", ESC, HMAC_sb(Facility)) + + EP_B->>GK_E: ReleaseComplete("TG", HMAC_sb(ReleaseComplete)) + GK_E->>GK_D: ReleaseComplete("TG", HMAC_sl(ReleaseComplete)) + GK_D->>EP_A: ReleaseComplete("TG", HMAC_sa(ReleaseComplete)) + + Note left of EP_A: Discard: challengeString, DH_A, Ma, TGK + Note right of EP_B: Discard: challengeString, DH_B, Ma, TGK + + EP_A->>GK_D: DRQ("TG", HMAC_sa(DRQ)) + GK_D->>EP_A: DCF("TG", HMAC_sa(DCF)) + Note left of EP_A: Discard: a, g^a + + EP_B->>GK_E: DRQ("TG", HMAC_sb(DRQ)) + GK_E->>EP_B: DCF("TG", HMAC_sb(DCF)) + Note right of EP_B: Discard: b, g^b + +``` + +H.235.7\_FI.2 + +Sequence diagram showing the termination of an H.323 call initiated by EP B. The diagram shows message exchanges between H.323 EP A, GK D, GK E, and H.323 EP B. It includes Facility, ReleaseComplete, DRQ, and DCF messages with HMAC calculations. At the bottom, boxes indicate discarded information like challengeString, DH keys, Ma, TGK, and private DH keys a and b. + +**Figure I.2/H.235.7 – Example endpoint B terminates a call** + +### I.2 TGK re-keying and CSB updating + +MIKEY has built-in support for TGK re-keying and/or CSB information updating. The profile of this Recommendation shall use the MIKEY-DHHMAC procedure in RFC zzzz, section 3.1 for this purpose that allows updating the TGK before expiration, or to update other information without changing the TGK. + +The TGK re-keying and CSB updating mechanism is useful to protect a bundle of logical channels under the same security policy. To this end, it is recommended running the (full) MIKEY-DHHMAC protocol as described above just for the first logical channel. Any subsequent logical channel that is to apply the same MIKEY security policy or the same TGK, should use the CSB updating mechanism without the TGK re-keying mechanism in this clause by making reference to the initial CSB-ID and by omitting updated Diffie-Hellman keys. This allows setting up logical channels or MIKEY crypto sessions more efficiently than by running the full MIKEY protocol on each logical channel. + +The MIKEY TGK re-keying or CSB updating messages shall be encapsulated and conveyed in a **MiscellaneousCommand** within a Facility message. The **tokenOID** of the **ClearToken** shall be set to "TG". + +For MIKEY at "media level", EP B has to determine for which logical channel the TGK re-keying and/or CSB updating should apply. EP A as the responder would equally use the **MiscellaneousCommand** within Facility to convey the MIKEY R\_message (if any). + +For TGK re-keying (see Figure I.3), the EP B as the MIKEY initiator shall generate a new TGK. **parameterValue** shall hold the corresponding binary-encoded MIKEY I\_message. + +EP A as the responder may confirm the obtained TGK re-keying message if necessary as requested by EP B. EP A builds a similar R\_message. This R\_message is being conveyed within the Facility message. EP B sends the Facility message towards EP A. + +For a CSB update, the above procedure is similar except that the MIKEY message shall not hold any TGK. + +![Sequence diagram showing the process of updating a key between H.323 EP A and H.323 EP B via Gatekeepers GK D and GK E. EP B initiates by generating x and DH_B = g^x, then sends an Imsg through the GKs to EP A. EP A responds by generating y and DH_A = g^y, then sends an Rmsg back through the GKs to EP B. Both endpoints then compute the new TGK = g^{xy}.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +dyn. shared MIKEY encryption key $Me$ , +dyn. shared MIKEY authentication key $Ma$ + +Dyn. shared $TGK$ (MIKEY) + +Shared secret $sa$                      (dyn) Shared secret $sl$                      Shared secret $sb$ + +H.235.7\_FI.3 + +Sequence diagram showing the process of updating a key between H.323 EP A and H.323 EP B via Gatekeepers GK D and GK E. EP B initiates by generating x and DH\_B = g^x, then sends an Imsg through the GKs to EP A. EP A responds by generating y and DH\_A = g^y, then sends an Rmsg back through the GKs to EP B. Both endpoints then compute the new TGK = g^{xy}. + +**Figure I.3/H.235.7 – Example endpoint B updating a key** + +This Recommendation does not define any procedures for $TGK$ re-keying and/or $CSB$ updating invoked by the responder; this remains for further study. + +# Appendix II + +### Using H.235.4 for establishing a pre-shared secret + +This appendix defines how to deploy Procedure DRC1 of ITU-T Rec. H.235.4 for establishing a pre-shared secret $ZZ_{AB}$ among endpoint B and endpoint A, assuming that no such end-to-end secret exists *a priori*. The method described in this appendix is applicable for the scenario with a single gatekeeper or with multiple gatekeepers. The procedure in this appendix does not involve DH computations during RAS registration or admission but rather deploys symmetric cryptography. + +Figure II.1 shows an example of a flow diagram for endpoint B calling endpoint A. + +![](f57c7b37d7a05a99618104f390089f03_img.jpg) + +dyn. shared H.323 secret $ZZ_{AB} = \text{MIKEY-PRF}(g^{ab}, 0x12F905FE \parallel \text{challenge})$ +dyn. shared MIKEY authentication key $Ma$ + +Dyn. shared $TGK$ (MIKEY) + +Shared secret $sa$                      Shared secret $sl$                      Shared secret $sb$ + +H.323 EP A              H.323              GK D              H.323              GK E              H.323              H.323 EP B + +Stage 1 + +RRQ(incl. ClearToken("I0"), $\text{HMAC}_{sa}(\text{RRQ})$ ) + +RCF(incl. $\text{EPID}_A$ , incl. ClearToken("I0"), $\text{HMAC}_{sa}(\text{RCF})$ ) + +Generate encryption key material $K'_{AD}$ from the shared secret $sa$ . +Include $\text{ENC}_{sa}(K'_{AD})$ in ClearToken $CT_{DE}$ + +LRQ(incl. ClearToken("I0"), $\text{HMAC}_{sl}(\text{LRQ})$ ) + +LCF(ClearToken("I0"), $CT_{DE}$ , $\text{HMAC}_{sl}(\text{LCF})$ ) + +RRQ(incl. ClearToken("I0"), $\text{HMAC}_{sb}(\text{RRQ})$ ) + +RCF(incl. $\text{EPID}_B$ , incl. ClearToken("I0"), $\text{HMAC}_{sb}(\text{RCF})$ ) + +ARQ(incl. ClearToken("I0"), $\text{HMAC}_{sb}(\text{ARQ})$ ) + +Generate encryption key material $K'_{BE}$ from the shared secret $sb$ . +Generate shared secret $ZZ_{AB}$ and two ClearTokens $CT_A$ and $CT_B$ . + +ACF(incl. $CT_A$ and $CT_B$ , $\text{HMAC}_{sb}(\text{ACF})$ ) + +challenge := rand() $Me := \text{PRF}(ZZ_{AB}, \dots)$ , $Ma := \text{PRF}(ZZ_{AB}, \dots)$ + $TGK := \text{rand}()$ + $I := \text{HDR}, T, \text{challenge}, [ID_B], \{SP\}$ , + $\text{ENC}_{Me}(TGK)$ + $\text{lmsg} := I, \text{MAC}(Ma, I)$ + +Setup("TG", $CT_A$ , +generalID := $\text{EPID}_A$ , + $\text{lmsg}$ , + $\text{HMAC}_{ZZ_{AB}}(\text{Setup})$ ) + +Stage 2 + +ARQ("TG", $\text{HMAC}_{sa}(\text{ARQ})$ ) + +ACF("TG", $\text{HMAC}_{sa}(\text{ACF})$ ) + +$Me := \text{PRF}(ZZ_{AB}, \dots)$ $Ma := \text{PRF}(ZZ_{AB}, \dots)$ +retrieve $TGK$ + $\text{Rmsg} := \text{HDR}, T, [ID_A]$ , + $\text{MAC}(Ma, \text{Rmsg} \parallel ID_B \parallel ID_A \parallel T)$ + +CP/C("TG", generalID := $\text{EPID}_B$ , + $\text{Rmsg}$ , + $\text{HMAC}_{ZZ_{AB}}(\text{CP/C})$ ) + +H.235.7\_FII.1 + +**Figure II.1/H.235.7 – Example endpoint B calling endpoint A (non-GK-routed) with MIKEY-preshared and H.235.4 DRC1** + +### **II.1 Terminating a H.323 call** + +The procedure for terminating a H.323 call shall proceed as described in 8.1. + +### **II.2 TGK re-keying and CSB updating** + +The procedure for TGK re-keying and/or CSB updating shall proceed as described in 8.2. + + + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.241-201202-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/marked/H/T-REC-H.241-201202-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecf24e1fb7b9d29933702bda661ef2c6aebecdc8 --- /dev/null +++ b/marked/H/T-REC-H.241-201202-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fab9e00256b5f903cc31129106b7259b14d211df92bdc7f59e2badda8e266dec +size 48483 diff --git a/marked/H/T-REC-H.241-201202-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/H/T-REC-H.241-201202-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..935237d9c32949e983077fa04d8ebd7f87ebadcc --- /dev/null +++ b/marked/H/T-REC-H.241-201202-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc61a5cc8e7aeb249ed01243526e3f3923aece46c1d6a71ca62568a84056aec5 +size 36244 diff --git a/marked/H/T-REC-H.241-201202-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.241-201202-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.241-201202-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.241-201202-I_PDF-E/a93de4c3f80bd4a972ab65510b09b68d_img.jpg b/marked/H/T-REC-H.241-201202-I_PDF-E/a93de4c3f80bd4a972ab65510b09b68d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7988afc8954695fa1f05df388d47499a4cd9d559 --- /dev/null +++ b/marked/H/T-REC-H.241-201202-I_PDF-E/a93de4c3f80bd4a972ab65510b09b68d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61492373c5435e4ca6e5ca13f75c98412a9183783213cfe2fcd7b9118c7ca471 +size 15882 diff --git a/marked/H/T-REC-H.241-201202-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg b/marked/H/T-REC-H.241-201202-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..986e6c0dd39ed2ef70b35d3dfe52102302d2269a --- /dev/null +++ b/marked/H/T-REC-H.241-201202-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a5f4c5566ae95d6b1f93e000fad325f585b0a5be8db498eb6a775349ef64fb4 +size 38158 diff --git a/marked/H/T-REC-H.241-201202-I_PDF-E/raw.md b/marked/H/T-REC-H.241-201202-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..163afd8dce7746cd84162ef90d3faf3e4b8a36af --- /dev/null +++ b/marked/H/T-REC-H.241-201202-I_PDF-E/raw.md @@ -0,0 +1,1941 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.241** + +(02/2012) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Extended video procedures and control signals +for ITU-T H.300-series terminals** + +Recommendation ITU-T H.241 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.241 + +## Extended video procedures and control signals for ITU-T H.300-series terminals + +## Summary + +Recommendation ITU-T H.241 defines the use of advanced video codecs, including those based on Recommendation ITU-T H.264, in ITU-T H.300-series terminals, including ITU-T H.310, ITU-T H.320, ITU-T H.321, ITU-T H.322, ITU-T H.323 and ITU-T H.324 terminals. It also defines generic extended signalling for use with all video codecs in the ITU-T H.300-series terminals. + +This revised version introduces a number of enhancements and clarifications to the previous version. Clarification concerns primarily the description on the signalling for ITU-T H.264 Annex G Scalable Baseline and Scalable High Profiles, a procedure for selecting the operating point of a scalable video coding (SVC) video stream, and the Capability Class of ITU-T H.241 capabilities. This version incorporates clause 6.2.5 introduced in ITU-T H.241 (2006) Amd. 1 (2008), allowing for the negotiation of particular video submodes of ITU-T H.264 encoding. It also incorporates clause 8.3.2.14, defining a new optional ITU-T H.264 capability parameter (MaxFPS), and Appendix II which contains non-normative examples describing the use of clause 6.2.5. Clause 8.3.2.14 and Appendix II were both introduced in ITU-T H.241 (2006) Amd. 2 (2009). + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|---------------------------|------------|-------------| +| 1.0 | ITU-T H.241 | 2003-07-14 | 16 | +| 1.1 | ITU-T H.241 (2003) Cor. 1 | 2004-03-15 | 16 | +| 1.2 | ITU-T H.241 (2003) Amd. 1 | 2005-01-08 | 16 | +| 2.0 | ITU-T H.241 | 2005-09-13 | 16 | +| 3.0 | ITU-T H.241 | 2006-05-29 | 16 | +| 3.1 | ITU-T H.241 (2006) Amd. 1 | 2008-06-13 | 16 | +| 3.2 | ITU-T H.241 (2006) Amd. 2 | 2009-12-14 | 16 | +| 3.3 | ITU-T H.241 (2006) Cor. 1 | 2011-05-14 | 16 | +| 4.0 | ITU-T H.241 | 2012-02-29 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2012 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 5.1 System terminology..... | 3 | +| 5.2 Message names..... | 3 | +| 5.3 Requirement terminology..... | 4 | +| 6 Commands and indications..... | 4 | +| 6.1 Control and indication (C&I) applicable to all video codecs..... | 4 | +| 6.2 C&I for use with ITU-T H.264..... | 4 | +| 7 Transport of coded video in ITU-T H.300-series systems ..... | 18 | +| 7.1 Transport of Recommendation ITU-T H.264 video streams..... | 18 | +| 8 Capability exchange signalling..... | 21 | +| 8.1 General ..... | 21 | +| 8.2 Signalling of ITU-T H.245 generic parameters in BAS-based systems..... | 22 | +| 8.3 ITU-T H.264 capabilities..... | 22 | +| Annex A – ITU-T H.264 transport for ITU-T H.323..... | 37 | +| Annex B – Reduced-complexity decoding operation (RCDO) for ITU-T H.264 Baseline Profile bitstreams..... | 38 | +| B.1 Scope ..... | 38 | +| B.2 Definitions ..... | 38 | +| B.3 General ..... | 38 | +| B.4 RCDO bitstreams..... | 38 | +| B.5 OpenLogicalChannel signalling..... | 39 | +| B.6 Procedures ..... | 39 | +| Appendix I – ASN.1 OIDs defined in this Recommendation..... | 45 | +| Appendix II – Examples of the set submode procedure ..... | 46 | +| II.1 Optimization of the picture aspect ratio ..... | 46 | +| II.2 Limiting the picture frame rate..... | 46 | +| II.3 Eliminating the adverse effects of picture rescaling..... | 47 | +| II.4 Improving bandwidth utilization by limiting maximum picture size..... | 48 | +| Bibliography..... | 51 | + + + +# Recommendation ITU-T H.241 + +## Extended video procedures and control signals for ITU-T H.300-series terminals + +# 1 Scope + +This Recommendation defines the procedures for use of advanced video codecs, including those based on [ITU-T H.264], in ITU-T H.300-series terminals, including ITU-T H.310, ITU-T H.320, ITU-T H.321, ITU-T H.322, ITU-T H.323 and ITU-T H.324 terminals. Such procedures include control, indication, capability exchange, and transport mechanisms. + +Additionally, this Recommendation defines generic extended video control, indication, and capability signalling, applicable for use with all video codecs used in ITU-T H.300-series multimedia terminals. + +Annex A specifies ITU-T H.264 transport for ITU-T H.323 systems, including Annex G of [ITU-T H.264] (Scalable Video Coding). + +Annex B specifies a reduced-complexity decoding process to be applied to ITU-T H.264 Baseline profile bitstreams when such use has been negotiated using [ITU-T H.241]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.221] Recommendation ITU-T H.221 (2009), *Frame structure for a 64 to 1 920 kbit/s channel in audiovisual teleservices*. +- [ITU-T H.230] Recommendation ITU-T H.230 (2009), *Frame-synchronous control and indication signals for audiovisual systems*. +- [ITU-T H.239] Recommendation ITU-T H.239 (2005), *Role management and additional media channels for H.300-series terminals*. +- [ITU-T H.242] Recommendation ITU-T H.242 (2009), *System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s*. +- [ITU-T H.243] Recommendation ITU-T H.243 (2005), *Procedures for establishing communication between three or more audiovisual terminals using digital channels up to 1 920 kbit/s*. +- [ITU-T H.245] Recommendation ITU-T H.245 (2011), *Control protocol for multimedia communication*. +- [ITU-T H.261] Recommendation ITU-T H.261 (1993), *Video codec for audiovisual services at $p \times 64$ kbit/s*. +- [ITU-T H.262] Recommendation ITU-T H.262 (2000), *Information technology – Generic coding of moving pictures and associated audio information: Video*. +- [ITU-T H.263] Recommendation ITU-T H.263 (2005), *Video coding for low bit rate communication*. + +- [ITU-T H.264] Recommendation ITU-T H.264 (2011), *Advanced video coding for generic audiovisual services*. +- [ITU-T H.310] Recommendation ITU-T H.310 (1998), *Broadband audiovisual communication systems and terminals*. +- [ITU-T H.320] Recommendation ITU-T H.320 (2004), *Narrow-band visual telephone systems and terminal equipment*. +- [ITU-T H.323] Recommendation ITU-T H.323 (2009), *Packet-based multimedia communications systems*. +- [ITU-T H.324] Recommendation ITU-T H.324 (2009), *Terminal for low bit-rate multimedia communication*. +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- [IETF RFC 6184] IETF RFC 6184 (2011), *RTP Payload Format for H.264 Video*. +- [IETF RFC 6190] IETF RFC 6190 (2011), *RTP Payload Format for Scalable Video Coding*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 picture aspect ratio:** The ratio between the intended horizontal width and the intended vertical height of a displayed picture. Picture aspect ratio is expressed as h:v, where h is horizontal width and v is vertical height (in arbitrary units of spatial distance). For the purposes of this definition, a picture is the complete displayed image (including both fields in the case of interlaced-scan video). For example, the picture aspect ratio for a common intermediate format (CIF) picture according to [ITU-T H.263] is 4:3. + +**3.2.2 sample aspect ratio:** The ratio between the intended horizontal distance between the columns and the intended vertical distance between the rows of the luma sample array in a frame. Sample aspect ratio is expressed as h:v, where h is horizontal width and v is vertical height (in arbitrary units of spatial distance). For the purposes of this definition, a sample is an individual luma picture element (pixel) making up the complete displayed image (including both fields in the case of interlaced-scan video). For example, the sample aspect ratio for a CIF picture according to [ITU-T H.263] is 12:11. + +**3.2.3 terminal:** A terminal is any end point and may be a user's terminal or some other communication system such as a multipoint control unit (MCU) or an information server. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|------------------------------------| +| 4CIF | 4x Common Intermediate Format | +| 4SIF | 4x Standard Interchange Format | +| AL-SDU | Adaptation Layer Service Data Unit | + +| | | +|-------|---------------------------------------| +| ASN.1 | Abstract Syntax Notation One | +| BAS | Bit-rate Allocation Signal | +| C&I | Control and Indication | +| CIF | Common Intermediate Format | +| IDR | Instantaneous Decoding Refresh | +| MBE | Multiple Byte Extension | +| MCU | Multipoint Control Unit | +| OID | Object Identifier | +| PAR | Picture Aspect Ratio | +| QCIF | Quarter Common Intermediate Format | +| QVGA | Quarter VGA | +| RCDO | Reduced Complexity Decoding Operation | +| RTP | Real-time Transport Protocol | +| SAR | Sample Aspect Ratio | +| SEI | Supplemental Enhancement Information | +| SIF | Standard Interchange Format | +| SVC | Scalable Video Coding | +| VUI | Video Usability Information | + +# 5 Conventions + +## 5.1 System terminology + +In order to simplify references, this Recommendation refers to two classes of signalling systems for ITU-T H.300-series terminals: + +- "BAS-based systems" refers to those systems that use signalling in the ITU-T H.221 bit-rate allocation system (BAS) channel; these include ITU-T H.320, ITU-T H.321 and ITU-T H.322 systems +- "ITU-T H.245-based systems" refers to those systems that use signalling according to [ITU-T H.245]; these include ITU-T H.310, ITU-T H.323 and ITU-T H.324 systems. + +## 5.2 Message names + +In this Recommendation, signalling messages which are common to both ITU-T H.245 and BAS signalling systems are referred to by their names, as given in Annex A of [ITU-T H.245], except in cases where their use in the unique BAS signalling environment is described. Message names are presented in **bold font** to distinguish them from the other text of this Recommendation. + +Table 5-1 provides a reference for corresponding ITU-T H.245 and ITU-T H.242/ITU-T H.230 messages mentioned in this Recommendation. + +**Table 5-1 – Corresponding ITU-T H.245 and BAS video signals** + +| ITU-T H.245 name | ITU-T H.230 mnemonic | +|------------------------------------------|--------------------------| +| h263Options.customPictureClockFrequency | ØCPCF | +| h263Options.customPictureFormat | ØCSFMT | +| h263Options.customPictureFormat | ØCPAR | +| h263VideoCapability.enhancementLayerInfo | ØSCLPREF | +| lostPartialPicture | lostPartialPicture | +| lostPicture | lostPicture | +| recoveryReferencePicture | recoveryReferencePicture | +| videoBadMBs | VB MBC | +| videoFastUpdateGOB | videoFastUpdateGOB | +| videoFastUpdateMB | videoFastUpdateMB | +| videoFastUpdatePicture | VCU | +| videoFreezePicture | VCF | +| videoNotDecodedMBs | videoNotDecodedMBs | +| videoSendSyncEveryGOB | ØGHOP | +| videoSendSyncEveryGOBCancel | Øcancel-GHOP | + +## 5.3 Requirement terminology + +In this Recommendation the following conventions are used: + +- "shall" indicates a mandatory requirement +- "should" indicates a suggested but optional course of action +- "may" indicates an optional course of action rather than a recommendation that something take place. + +# 6 Commands and indications + +## 6.1 Control and indication (C&I) applicable to all video codecs + +For further study. + +## 6.2 C&I for use with ITU-T H.264 + +The following C&I signals shall not be used with regard to any channel operating according to [ITU-T H.264]: + +- BAS signals ØCPCF, ØCSFMT, ØCPAR, ØSCLPREF +- lostPartialPicture +- lostPicture +- recoveryReferencePicture +- videoBadMBs +- videoFastUpdateGOB +- videoFastUpdateMB +- videoNotDecodedMBs +- videoSendSyncEveryGOB + +– **videoSendSyncEveryGOBCancel**. + +NOTE 1 – The above signals are either specific to [ITU-T H.263] or have parameters which do not correspond to ITU-T H.264 structures or value ranges. Replacement signals which could be used either with [ITU-T H.264] or in a generic form for any video codec are for further study. + +All other C&I not mentioned in this clause shall be used as specified elsewhere. + +NOTE 2 – For example, the use of **videoIndicateReadyToActivate** and corresponding BAS signal **VIR** is not affected by this Recommendation. + +### 6.2.1 **videoFreezePicture command in ITU-T H.264** + +When a video decoder according to [ITU-T H.264] receives a **videoFreezePicture** command, it shall freeze its displayed picture until one of the following events occurs: + +- a) a recovery point signalled in a recovery point service end interface (SEI) message (D.2.7 of [ITU-T H.264]) is reached +- b) reception of an instantaneous decoding refresh (IDR) picture +- c) A timeout period of at least six seconds has elapsed since the **videoFreezePicture** command was received. + +### 6.2.2 **videoFastUpdatePicture command in ITU-T H.264** + +When a video encoder according to [ITU-T H.264] receives a **videoFastUpdatePicture** command, the encoder shall enter the fast update mode by using one of the procedures specified in clause 6.2.2.1 or 6.2.2.2 below. The procedure in 6.2.2.1 is the preferred response in a lossless transmission environment. Both procedures satisfy the requirement to enter the fast update mode for ITU-T H.264 video encoding. + +NOTE 1 – The procedures re-initialize an ITU-T H.264 decoder completely so that valid video frames will be decoded. Such re-initialization is effective regardless of whether or not the decoder was previously decoding any video stream from any end point. + +The procedure should be accomplished as quickly as possible, but the re-initialization video stream shall be completely transmitted within three seconds of receiving the **videoFastUpdatePicture** command. + +NOTE 2 – The 3-second requirement is needed to avoid timeout of the six-second timer associated with the **videoFreezePicture** command, taking into account network and system latencies and possible cascaded MCUs. The **videoFreezePicture** command is used by multipoint control units (MCUs) as part of the video switching procedure (see clause 6.1.1 of [ITU-T H.243]). + +#### 6.2.2.1 **IDR procedure to respond to videoFastUpdatePicture** + +This clause gives one possible way to respond to **videoFastUpdatePicture**. + +The encoder shall, in the order presented here: + +- 1) immediately prepare to send an IDR picture (see clause 3 of [ITU-T H.264]) +- 2) send a ITU-T H.264 sequence parameter set corresponding to the IDR picture to be sent. The encoder may optionally also send other parameter sets +- 3) send a ITU-T H.264 picture parameter set corresponding to the IDR picture to be sent. The encoder may optionally also send other parameter sets +- 4) send the IDR picture +- 5) from this point forward in time, send or re-send any other sequence or picture parameter sets, not sent in this procedure, prior to their reference by any ITU-T H.264 slice, regardless of whether such parameter sets were previously sent prior to receiving the **videoFastUpdatePicture** command. Such parameter sets may be sent all at once (within the limits of [ITU-T H.264]), one at a time as needed, or in any combination of these methods. Parameter sets may be re-sent at any time for redundancy. + +#### 6.2.2.2 Gradual recovery procedure to respond to **videoFastUpdatePicture** + +This clause gives one possible way to respond to **videoFastUpdatePicture**. + +The encoder shall, in the order presented here: + +- 1) send a recovery point (supplemental enhancement information (SEI) message (D.2.7 of [ITU-T H.264])). +- 2) repeat any sequence and picture parameter sets that were sent before the recovery point SEI message, prior to their reference in a ITU-T H.264 slice. + +The encoder shall ensure that the decoder has access to all reference pictures, in output order, for inter prediction of pictures at or after the recovery point. For example, the encoder may mark all reference pictures as "unused for reference" by issuing a **memory\_management\_control\_operation** equal to 5 (see clause 8.2.5 of [ITU-T H.264]). + +The value of the **recovery\_frame\_cnt** syntax element in the recovery point SEI message shall be such that the time between reception of the **videoFastUpdatePicture** command and completing the transmission of the access unit, including the recovery point as specified in clause D.2.7 of [ITU-T H.264], is less than or equal to three seconds. + +Re-sending of parameter sets may be done all at once (within the limits of [ITU-T H.264]), one at a time as needed, or in any combination of these methods. Parameter sets may be re-sent at any time for redundancy. + +### 6.2.3 Recovery point SEI message + +ITU-T H.264 video decoders in ITU-T H.300-series terminals shall support reception of the recovery point SEI message (see clause D.2.7 of [ITU-T H.264]), and identify the signalled recovery point. + +Upon reception of a recovery point SEI message, the decoder shall continue to decode until the recovery point regardless of apparent errors in the stream, such as reference to absent pictures, and should not send a **videoFastUpdatePicture** command in response to such apparent error. + +If a **videoFreezePicture** is in force, the decoder shall not display the decoded pictures, and shall continue to display the previously frozen picture. If the **broken\_link\_flag** in the recovery point SEI message is set, the decoder may choose not to display decoded pictures until the recovery point is reached. + +If the decoder detects bitstream corruption between the SEI message and the recovery point in decoding order, a **videoFastUpdatePicture** command should be sent. + +### 6.2.4 ITU-T H.264-on BAS command + +For BAS-based systems, the ITU-T H.264-on BAS command defined in [ITU-T H.221] shall be used to signal that video according to [ITU-T H.264] is being transmitted. This command shall be used analogously to the BAS command ITU-T H.261-on. Video shall occupy the same capacity as stipulated in [ITU-T H.221] for the case of ITU-T H.261 video. The use of ITU-T H.264 Annex G scalable video coding (SVC) in BAS-based systems is for further study. + +### 6.2.5 Set submode procedure + +This clause defines a procedure that may be used by ITU-T H.320 and ITU-T H.245 systems to negotiate the use of a particular ITU-T H.264 video encoding submode. Such a submode may limit the ITU-T H.264 encoding to a specified group of sample aspect ratios (SARs), picture aspect ratios (PARs), and picture heights while it is in force. It may also reduce the **MaxMBPS** value in Table A.1 of [ITU-T H.264] (or its optional replacement **CustomMaxMBPS** in Table 8-5) to a lower value. Additionally, it may reduce the **MaxStaticMBPS** value in Table 8-9 to a lower value. + +Some examples illustrating the use of this procedure are given in Appendix II. + +#### 6.2.5.1 SetSubmode capability + +ITU-T H.320 and ITU-T H.245 systems may optionally support the set submode procedure. + +In [ITU-T H.320], this capability shall be signalled as a BAS message (see clause 3.1 of [ITU-T H.230]). is a BAS SBE message. + +In [ITU-T H.245], this capability shall be signalled in a generic capability message, as shown in Table 6-1. + +**Table 6-1 – ITU-T H.241 set submode capability identifier** + +| Capability name | ITU-T H.241 set submode capability | +|-----------------------------|---------------------------------------------------------------------------------------------------------| +| Capability identifier type | Standard | +| Capability Class | Video | +| Capability identifier value | {itu-t(0) recommendation(0) h(8) h241(241)
specificVideoCodecCapabilities(0) h264(0) set-submode(2)} | +| maxBitRate | This field shall not be included. | +| collapsing | This field shall not be included. | +| nonCollapsing | This field shall not be included. | +| nonCollapsingRaw | This field shall not be included. | +| transport | This field shall not be included. | + +#### 6.2.5.2 C&I messages + +C&I messages are used in this clause to indicate sets of submodes that are supported by the sender of the ITU-T H.264 encoding for that specific encoding, to request a submode of that sender, and to positively or negatively acknowledge such a request. + +The C&I messages defined in this clause shall not be used if video sent on the channel associated with the signalled channelID AMC is not encoded with ITU-T H.264. + +All C&I messages defined in this clause shall be carried as follows. + +#### 6.2.5.3 Signalling of messages for the set submode procedure + +For ITU-T H.245, each message shall consist of a **GenericRequest**, **GenericResponse** or **GenericIndication** according to Table 6-2 containing **GenericMessage.messageIdentifier** with the set submode capability OID as defined in Table 6-1, and a **subMessageIdentifier**. Each particular **subMessageIdentifier** listed in Table 6-2 has an associated **messageContent** syntax given in the following clauses. + +For ITU-T H.320, each set submode message shall be carried by a separate MBE message (see clause 2.2.3 of [ITU-T H.230]) which shall contain the same **subMessageIdentifier** value and parameter sequence as its ITU-T H.245 equivalent, coded according to the procedures in Annex A of [ITU-T H.239]. This MBE message uses the BAS code (see Table 2 of [ITU-T H.230]). The MBE contents are in the format: + +{ Start-MBE / N / / subMessageIdentifier / +zero or more message content bytes } + +ITU-T H.320-ITU-T H.245 gateways that signal the SetSubmode capability shall translate these messages between the ITU-T H.320 and ITU-T H.245 signalling systems as specified in Annex A of [ITU-T H.239]. + +Except for ITU-T H.320/ITU-T H.245 gateways, devices that receive **MessageContent** containing an unrecognized **parameterIdentifier** shall ignore such **parameterIdentifiers** and any associated **parameterValues**. + +#### 6.2.5.4 SetSubmode messages + +Table 6-2 lists all messages defined in the SetSubmode procedure. + +**Table 6-2 – Set submode procedure messages** + +| subMessageIdentifier | Message name | Message type
(for ITU-T H.245) | +|-----------------------------|-----------------------|-------------------------------------------| +| 1 | setSubmodeRequest | GenericRequest | +| 2 | setSubmodeResponse | GenericResponse | +| 3 | setSubmodeIndication | GenericIndication | +| 4 | cancelSubmodeRequest | GenericRequest | +| 5 | cancelSubmodeResponse | GenericResponse | + +For each message, the clauses below present a table indicating the message content and syntax. The sequence of **GenericParameters** in the **messageContent** shall be transmitted in the order given in each table. The parameter names given in each table correspond to those in Table 6-2 above. Parameters shall be sent as indicated in the "required presence" column of each table. + +#### 6.2.5.5 Generic parameters used in SetSubmode messages + +Table 6-3 lists the **GenericParameters** used in all **messageContent** sequences in the SetSubmode messages. + +**Table 6-3 – Set submode message parameters** + +| Parameter identifier | Parameter name | Parameter type | Parameter value | +|-----------------------------|-----------------------|-----------------------|------------------------| +| 40 | channelID | unsignedMin | Integer (0..65535) | +| 1 | par | booleanArray | Integer (0..255) | +| 2 | parX | unsignedMin | Integer (0..65535) | +| 41 | parY | unsignedMin | Integer (0..65535) | +| 3 | sar | unsignedMin | Integer (0..255) | +| 4 | sarX | unsignedMin | Integer (0..65535) | +| 42 | sarY | unsignedMin | Integer (0..65535) | +| 5 | submodeMaxMBPS | unsignedMin | Integer (0..65535) | +| 6 | submodeMaxStaticMBPS | unsignedMin | Integer (0..65535) | +| 7 | height | unsignedMin | Integer (0..65535) | +| 8 | maximumHeight | unsignedMin | Integer (0..65535) | +| 9 | minimumHeight | unsignedMin | Integer (0..65535) | +| 128 | acknowledge | logical | None | +| 129 | reject | logical | None | +| 130 | allowAnyHeight | logical | None | + +##### 6.2.5.5.1 channelID + +The channelID parameter shall be the AMC channel ID on ITU-T H.230 systems in Table 9 of [ITU-T H.239]. On ITU-T H.245 systems, it shall be a **logicalChannelNumber**. Intermediary devices such as gateways and MCUs that forward these parameters shall convert the parameter value to the appropriate AMC channel ID or **logicalChannelNumber** for the device to which the message is forwarded. + +##### 6.2.5.5.2 par + +This value is a Boolean array of picture aspect ratios (PARs). The PAR is the ratio of picture width to picture height, measured in units of distance (not samples). + +If bit 2 (value 64) is 1, this indicates a PAR of 4:3. + +If bit 3 (value 32) is 1, this indicates a PAR of 16:9. + +If bit 4 (value 16) is 1, this indicates a PAR of 5:4. + +If bit 5 (value 8) is 1, this indicates a PAR of 16:10. + +All other bits are reserved, shall be set to 0, and shall be ignored by receivers. + +##### 6.2.5.5.3 parX + +The parX parameter is the numerator of a picture aspect ratio (computed as parX/parY). The parX parameter shall be immediately followed by the picture aspect ratio denominator parY. parX is an unsigned integer between 1 and 65535. + +##### 6.2.5.5.4 parY + +The parY parameter is the denominator of a picture aspect ratio. It is an unsigned integer between 1 and 65535. The values of parX and parY shall be relatively prime. + +##### 6.2.5.5.5 sar + +The value of this parameter indicates the sample aspect ratio (SAR). The sar is the ratio of sample width to sample height. It shall be the ITU-T H.264 **aspect\_ratio\_idc** values defined in Table E.1 of [ITU-T H.264], or the value 255. + +The value of 255 shall only be used in the setSetmodeIndication message. In that message, it signifies the set of all SARs that may be carried on the video channel. + +##### 6.2.5.5.6 sarX + +The sarX parameter is the numerator of a sample aspect ratio (computed as sarX/sarY). The sarX parameter shall be immediately followed by the sample aspect ratio denominator sarY. sarX is an unsigned integer between 1 and 65535. + +##### 6.2.5.5.7 sarY + +The sarY parameter is the denominator of a sample aspect ratio. It is an unsigned integer between 1 and 65535. The values of sarX and sarY shall be relatively prime. + +##### 6.2.5.5.8 submodeMaxMBPS + +The submodeMaxMBPS parameter is the maximum macroblock processing rate, in units of 500 macroblocks per second. + +##### 6.2.5.5.9 submodeMaxStaticMBPS + +The submodeMaxStaticMBPS parameter is the static macroblock processing rate, under the assumption that all macroblocks are static macroblocks, in units of 500 macroblocks per second. + +##### **6.2.5.5.10 height** + +This is the height of the picture in samples. + +##### **6.2.5.5.11 maximumHeight** + +This is the largest height of the picture in samples (used in a setSubmodeRequest message). + +##### **6.2.5.5.12 minimumHeight** + +This is the smallest supported picture height in samples (used in a setSubmodeResponse message). + +##### **6.2.5.5.13 acknowledge** + +This parameter, if present, indicates a positive acknowledgment of a request. + +##### **6.2.5.5.14 reject** + +This parameter, if present, indicates a rejection of a request. + +##### **6.2.5.5.15 allowAnyHeight** + +This parameter, if present, indicates that any requested picture height will be positively acknowledged for the specified combination of SARs and PARs. + +#### **6.2.5.6 setSubmodeIndication** + +This message indicates the combinations of SARs and PARs that are available for the ITU-T H.264 video encoding on a specified video channel. These combinations shall be sent as a series of one or more groups, each group comprising a SAR and one or more PARs. The full set of combinations that are available is the union of the combinations of all the groups in the message. + +The SAR shall be signalled as either a single sar parameter or as a single sarX, sarY parameter pair. A sar parameter value of 255 in a group shall indicate that all SARs that can be carried on the channel are combined with the PARs for that group. + +The PARs shall be signalled as either a single par parameter or as a list of one or more parX, parY parameter pairs. The par parameter may indicate more than one PAR. The omission of par or parX, parY from a group shall indicate that all the SARs in that group are combined with all possible PARs. + +The presence of the allowAnyHeight parameter from a group shall indicate that all picture heights that can be carried on the channel are available for each SAR and PAR combination that is included in that group. + +The absence of the allowAnyHeight parameter from a group shall indicate that one or more unspecified picture heights are available for each SAR and PAR combination that is included in that group. Those heights may differ for each combination. + +When a video channel is opened to a device which signals support for the set submode procedure, the device transmitting the video channel shall send the setSubmodeIndication. The setSubmodeIndication message shall also be sent whenever the available combinations of SARs and PARs change. + +On ITU-T H.320 connections, setSubmodeIndication shall be sent periodically. + +**Table 6-4 – setSubmodeIndication syntax** + +| GenericParameter order | Parameter name | Required presence | | | +|------------------------|----------------|------------------------------------------------------------------|---------------------------------------------------------|--| +| 1 | channelID | Mandatory | | | +| 2 | sar | Either one sar or one sarX, sarY shall be present in each group. | This group of parameters may be present multiple times. | | +| | sarX | | | | +| | sarY | | | | +| 3 | par | Either one par or multiple parX, parY pairs may be present. | | | +| | parX | | | | +| | parY | | | | +| 4 | allowAnyHeight | allowAnyHeight may be present in each group. | | | + +##### 6.2.5.6.1 setSubmodeIndication examples (informative) + +This clause does not form an integral part of this Recommendation. + +For example: + +A setSubmodeIndication contains one group, with sar=255 and allowAnyHeight. + +This message indicates that the sender is capable of sending a picture of any size within its capability set with any sample aspect ratio and picture aspect ratio. + +For example: + +A setSubmodeIndication contains two groups. The first group has sar=1 and allowAnyHeight. The second group has sar=255, par=96. + +The first group indicates that the sender is capable of sending pictures with square samples at any PAR and any desired picture height. This is equivalent to saying that the sender is capable of sending pictures with square pixels of any size. + +The second group indicates that the sender is capable of sending pictures with any SAR as long as the overall picture aspect ratio is either 4:3 or 16:9. Since allowAnyHeight is not specified, only some picture sizes (perhaps only one size) are available for this group. + +A picture with a SAR of 1:1 and an aspect ratio of 4:3 is a member of both groups. Because one of the groups signals allowAnyHeight, such pictures are available at any size. + +For example: + +A setSubmodeIndication contains 4 groups. The first group has sar=1, par=120 and allowAnyHeight. The second group has sar=2 and par=64. The third group has sar=3 and par=64. The fourth group has sar=7 and par=64. + +The first group indicates the ability to send pictures with square samples at picture aspect ratios of 4:3, 16:9, 5:4 or 16:10. These pictures can be sent at any size. + +The second group indicates the ability to send pictures with the sample aspect ratio used for PAL with a picture aspect ratio of 4:3. Not all sizes are available, perhaps only QCIF and CIF. + +The third group indicates the ability to send pictures with the sample aspect ratio used for NTSC, with a picture aspect ratio of 4:3. Not all sizes are available, perhaps only QSIF and SIF. + +The last group indicates the ability to send pictures with the sample aspect ratio used for interlaced NTSC, with a picture aspect ratio of 4:3. Not all sizes are available, perhaps only 352×480. + +#### 6.2.5.7 setSubmodeRequest + +This message requests that the video encoding on the specified channel be changed to one of the submodes specified in the request. + +setSubmodeRequest shall include at least one of the following: SAR, PAR or picture height. It shall include at most one SAR, and at most one PAR, and at most one maximumHeight. It shall not include both maximumHeight and height. + +SAR, if present, shall be specified using either the sar parameter or a sarX, sarY pair. The sar parameter shall not signal the value of 255. + +PAR, if present, shall be specified using either the par parameter or a parX, parY pair. The par parameter shall only signal one PAR. + +The maximumHeight parameter, if present, shall specify that the set of submodes includes all picture heights less than or equal to the value carried by the parameter. + +One or more height parameters, if present, shall specify that the set of submodes includes the specific list of picture heights. The picture heights shall be listed in preference order, with the most desired height first. + +The submodeMaxMBPS parameter, if present, shall specify that the set of submodes is limited to modes in which the macroblock rate is less than or equal to the maximum number of macroblocks per second carried in the parameter value. + +The submodeStaticMaxMBPS parameter, if present, shall specify that the subset of submodes is limited to modes in which the static macroblock rate is less than or equal to the maximum number of static macroblocks per second carried in the parameter value. + +**Table 6-5 – setSubmodeRequest syntax** + +| GenericParameter order | Parameter name | Required presence | +|------------------------|----------------------|-----------------------------------------------------------------------------------| +| 1 | channelID | Mandatory | +| 2 | sar | Optional | +| | sarX | Either sar or sarX, sarY may be present. | +| | sarY | | +| 3 | par | Optional | +| | parX | Either par or parX, parY may be present. | +| | parY | | +| 4 | height | Optional | +| | maximumHeight | Either one or more height parameters or at most one maximumHeight may be present. | +| 5 | submodeMaxMBPS | Optional | +| 6 | submodeStaticMaxMBPS | Optional | + +##### 6.2.5.7.1 setSubmodeRequest examples (informative) + +This clause does not form an integral part of this Recommendation. + +For example: + +A device sends a setSubmodeRequest with par=64 and maximumHeight of 288. + +This request is satisfied by any submode with a picture aspect of 4:3, as long as the picture height does not exceed 288. Common intermediate format (CIF), standard interchange + +format (SIF) and quarter common intermediate format (QCIF) (among others) are all acceptable responses. + +For example: + +A device sends a setSubmodeRequest with par=64, and a height list of 288 and 144. + +This request is satisfied by any submode with a picture aspect ratio of 4:3, as long as the picture height is either 288 or 144 samples. CIF and QCIF are both acceptable responses, with CIF being preferred over QCIF. + +Since the SAR is omitted, there are other possible responses. For instance, the request is satisfied by a picture with square samples, a picture width of 384 and a picture height of 288. + +For example: + +A device sends a setSubmodeRequest with sar=1, par=32 and height=720. + +This request is only satisfied by a picture with a SAR of 1:1, a PAR of 16:9 and a picture size of 1280×720. + +In all cases, if the device receiving the request does not support a submode that satisfies the request, it rejects the request. + +#### 6.2.5.8 setSubmodeResponse + +The setSubmodeResponse message shall be sent in response to every received setSubmodeRequest message. + +The channelID parameter shall carry the same value as the channelID in the associated setSubmodeRequest. + +The setSubmodeResponse message shall not carry both the acknowledge and the reject parameter. + +##### 6.2.5.8.1 setSubmodeRequest acknowledge + +If the receiver of the setSubmodeRequest supports one or more submodes that satisfy the request on the specified channel, the setSubmodeResponse shall include the acknowledge parameter. The receiver shall select a submode from the set specified in the request. The SAR, PAR and picture height of the selected submode shall be sent in the setSubmodeResponse. + +An ITU-T H.264 video usability information (VUI) message signalling the SAR of the submode as specified in Annex E of [ITU-T H.264] shall be sent in the video bitstream. + +ITU-T H.245 receivers of the setSubmodeRequest should not close and reopen the video logical channel when switching to the new submode. + +Terminals may include the acknowledge parameter in their response even if multipoint mode symmetrize (MMS) according to [ITU-T H.243] is in effect, or **multipointModeCommand** according to [ITU-T H.245] is in effect. + +##### 6.2.5.8.2 setSubmodeRequest reject + +If the receiver of the setSubmodeRequest does not support any submodes that satisfy the request, the setSubmodeResponse shall include the reject parameter. The receiver shall not switch to a different submode. + +The response should include some indication of heights that are available with the requested SAR and PAR. + +Multiple instances of the height parameter may be present, containing heights that are available with the requested SAR and PAR + +If the setSubmodeRequest contained maximumHeight, a single instance of minimumHeight may be present, indicating the smallest available height that is available with the requested SAR and PAR. + +A setSubmodeResponse message shall not contain both minimumHeight and height. + +**Table 6-6 – setSubmodeResponse syntax** + +| GenericParameter order | Parameter name | Required presence | +|------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | channelID | Mandatory | +| 2 | acknowledge | Either acknowledge or reject shall be present. | +| | reject | | +| 3 | sar | Either sar or sarX, sarY shall be present if acknowledge is present, and shall contain the selected SAR.
sar, sarX and sarY shall not be present if reject is present. | +| | sarX | | +| | sarY | | +| 4 | par | Either par or parX, parY shall be present if acknowledge is present, and shall contain the selected PAR.
par, parX and parY shall not be present if reject is present. | +| | parX | | +| | parY | | +| 5 | height | If acknowledge is present, a single instance of height parameter shall be present, and shall contain the selected picture height.
If reject is present, height or minimumHeight may be present. | +| | minimumHeight | | + +##### 6.2.5.8.3 setSubmodeResponse examples (informative) + +This clause does not form an integral part of this Recommendation. + +For example: + +Device A sends a setSubmodeIndication containing one group, with sar=255 and allowAnyHeight. + +The receiver (device B) sends setSubmodeRequest sar=1 and height=480. + +Device A determines that the request can be satisfied by sending a 640x480 picture with a SAR of 1:1 and a PAR of 4:3. + +Device A sends a setSubmodeReponse of acknowledge, sar=1, par=64, height=480. + +For example: + +Device A sends a setSubmodeIndication containing two groups. The first group has sar=1 and allowAnyHeight. The second group has sar=255, par=96. + +The receiver (device B) sends setSubmodeRequest sar=1 and par=64 + +Device A determines that the request can be satisfied by sending either a 640×480 or a 1 024×768 picture with a SAR of 1:1 and a PAR of 4:3. Device A chooses to send the 1 024×768 picture. + +Device A sends a setSubmodeReponse of acknowledge, sar=1, par=96, height=768. + +For example: + +Device A sends a setSubmodeIndication containing two groups, one with sar=1 and par=64, the other with sar=2, par=64. + +The receiver (device B) sends setSubmodeRequest with sar=2 and par=64 and height=576. Device A determines that the request cannot be satisfied because the picture size is too large. It supports heights of 288 and 144 for this SAR and PAR combination. Device A sends a setSubmodeReponse of reject, sar=1, height=288, height=144. Device B sends a second setSubmodeRequest with sar=2, par=64, height=288. Device A sends a setSubmodeResponse of acknowledge, sar=2, par=64, height=288. + +For example: + +Device A sends a setSubmodeIndication containing two groups, one with sar=1, par=64, the other with sar=2, par=64. The receiver (device B) sends setSubmodeRequest with sar=2, par=64 and maximumHeight=576. Device A determines that it supports heights of 288 and 144 for this SAR and PAR combination. Device A sends a setSubmodeResponse of acknowledge, sar=2, par=64, height=288. + +#### 6.2.5.9 cancelSubmodeRequest + +The cancelSubmodeRequest message indicates that the video encoding on the specified channel may revert to sending any video mode allowed by applicable procedures. + +Each received cancelSubmodeRequest shall be acknowledged by a cancelSubmodeResponse. + +**Table 6-7 – cancelSubmodeRequest syntax** + +| GenericParameter order | Parameter name | Required presence | +|------------------------|----------------|-------------------| +| 1 | channelID | Mandatory | + +#### 6.2.5.10 cancelSubmodeResponse + +The cancelSubmodeResponse message indicates that the cancelSubmodeRequest message was received. + +**Table 6-8 – cancelSubmodeResponse syntax** + +| GenericParameter order | Parameter name | Required presence | +|------------------------|----------------|-------------------| +| 1 | channelID | Mandatory | + +### 6.2.6 Set scalable video coding (SVC) mode procedure + +This clause defines a procedure that may be used by ITU-T H.245 systems to negotiate the use of a particular ITU-T H.264 SVC scalability mode. Such a scalability mode consists of a particular operation point that is selected by a receiver, and determined after a sender has provided a description of its available scalable encoding structure(s). + +The sender provides a description of its scalable video coding structure, including the different available operation points, using the "sprop-scalability-info" parameter as defined in 7.1 of [IETF RFC 6190]. The "sprop-scalability-info" parameter is the base64 encoding of the scalability information SEI message defined in clause G.13.1.1 of [ITU-T H.264]. + +If the "sprop-scalability-info" is provided by a sender, a receiver can optionally select a particular operation point. If no such selection takes place, then the sender should transmit the full SVC stream. + +The use of this procedure in BAS-based systems is for further study. + +#### 6.2.6.1 SetSVCmode capability + +ITU-T H.245 systems may optionally support the set SVC mode procedure. + +In [ITU-T H.245], this capability shall be signalled in a generic capability message, as shown in Table 6-9. + +**Table 6-9 – ITU-T H.241 set SVC mode capability identifier** + +| Capability name | ITU-T H.241 set SVC mode capability | +|-----------------------------|----------------------------------------------------------------------------------------------------------| +| Capability identifier type | Standard | +| Capability Class | Video | +| Capability identifier value | {itu-t(0) recommendation(0) h(8) h241(241)
specificVideoCodecCapabilities(0) h264(0) set-SVCmode (3)} | +| maxBitRate | This field shall not be included. | +| collapsing | This field shall not be included. | +| nonCollapsing | This field shall not be included. | +| nonCollapsingRaw | This field shall not be included. | +| transport | This field shall not be included. | + +#### 6.2.6.2 Control and Indication messages + +C&I messages are used in this clause to indicate the scalability modes that are supported by the sender of the ITU-T H.264 SVC encoding for that specific encoding, to request a scalability mode of that sender, and to positively or negatively acknowledge such a request. + +The C&I messages defined in this clause shall not be used if video sent on the channel associated with the signalled channelID AMC is not encoded with ITU-T H.264 SVC. + +All C&I messages defined in this clause shall be carried as follows. + +#### 6.2.6.3 Signalling of messages for the set SVC mode procedure + +For ITU-T H.245, each message shall consist of a GenericRequest, GenericResponse, or Generic Indication according to Table 6-10 containing GenericMessage.messageIdentifier with the set SVC mode capability OID as defined in Table 6-9, and a subMessageIdentifier. Each particular subMessageIdentifier listed in Table 6-10 has an associated messageContent syntax given in the following clauses. + +#### 6.2.6.4 SetSVCmode messages + +Table 6-10 lists all messages defined in the SetSVCmode procedure. + +**Table 6-10 – Set SVCmode procedure messages** + +| subMessageIdentifier | Message name | Message type
(for ITU-T H.245) | +|----------------------|----------------------|-----------------------------------| +| 1 | setSVCmodeRequest | GenericRequest | +| 2 | setSVCmodeResponse | GenericResponse | +| 3 | setSVCmodeIndication | GenericIndication | + +For each message, the clauses below present a table indicating the message content and syntax. The sequence of GenericParameters in the messageContent shall be transmitted in the order given in each table. The parameter names given in each table correspond to those in Table 6-10 above. Parameters shall be sent as indicated in the "required presence" column of each table. + +#### 6.2.6.5 Generic parameters used in SetSVCmode messages + +Table 6-11 lists the GenericParameters used in all messageContent sequences in the SetSVCmode messages. + +**Table 6-11 – Set SVCmode message parameters** + +| Parameter identifier | Parameter name | Parameter type | Parameter value | +|----------------------|-------------------------|----------------|--------------------| +| 40 | channelID | unsignedMin | Integer (0..65535) | +| 43 | SSEI | octetString | | +| 44 | layers_not_present | octetString | | +| 45 | layer_dependency_change | octetString | | +| 46 | scalable_layer_id | unsignedMin | Integer (0..255) | + +##### 6.2.6.5.1 channelID + +On ITU-T H.245 systems, channelID shall be a logicalChannelNumber. + +##### 6.2.6.5.2 SSEI + +This value shall be identical to the value of the parameter "sprop-scalability-info" as defined in [IETF RFC 6190] (i.e., the base64 encoding of the scalability information SEI message defined in [ITU-T H.264] Annex G). It contains the scalability information SEI message of the ITU-T H.264 SVC video. + +##### 6.2.6.5.3 layers\_not\_present + +This value shall be equal to the base64 encoding of the layers\_not\_present SEI message defined in clause G.13.1.5 of [ITU-T H.264]. This message is used to indicate that NAL units of a particular subset of layers (identified by their layer\_id) from the set of layers identified in the associated SSEI are not present in the bitstream. + +##### 6.2.6.5.4 layer\_dependency\_change + +This value shall be equal to the base64 encoding of the layer\_dependency\_change SEI message defined in clause G.13.1.6 of [ITU-T H.264]. This message is used to indicate that the interdependencies between particular scalable layers indicated by the associated SSEI message are changed. + +##### 6.2.6.5.5 scalable\_layer\_id + +The scalable\_layer\_id parameter identifies a particular layer within the data structure provided by the SSEI parameter, and is identical to the "scalable-layer-id" parameter defined in [IETF RFC 6190]. + +#### 6.2.6.6 setSVCmodeIndication + +This message indicates the scalability information for the ITU-T H.264 SVC encoding on a specified video channel. If the sender has suspended transmission of layers of the SVC bitstream, then the optional parameter layers\_not\_present parameter shall be included as well. If the decoding dependency is different than what is described in the SSEI parameter, then the optional layer\_dependency\_change parameter shall be included as well. + +This message may be transmitted periodically to enable receivers to know the scalability structure after the connection is set up. + +**Table 6-12– setSVCmodeIndication syntax** + +| GenericParameter order | Parameter name | Required presence | +|-------------------------------|-------------------------|--------------------------| +| 1 | channelID | Mandatory | +| 2 | SSEI | Mandatory | +| 3 | layers_not_present | Optional | +| 4 | layer_dependency_change | Optional | + +#### **6.2.6.7 setSVCmodeRequest** + +This message requests that scalable layers of the video encoding on the specified channel be changed to the mode specified in the request. + +setSVCModeRequest shall include a single scalable\_layer\_id indication. + +The value of the scalable\_layer\_id parameter shall be equal to one of the layer\_id values contained in the SSEI parameter that has been communicated in the associated setSVCmodeIndication message. + +The value of the scalable\_layer\_id parameter shall be equal to one of the layer\_id values contained in the SSEI parameter that has been communicated in the associated setSVCmodeIndication message. + +**Table 6-13– setSVCmodeRequest syntax** + +| GenericParameter order | Parameter name | Required presence | +|-------------------------------|-----------------------|--------------------------| +| 1 | channelID | Mandatory | +| 2 | scalable_layer_id | Mandatory | + +#### **6.2.6.8 setSVCmodeResponse** + +The setSVCmodeResponse message shall be sent in response to every received setSVCmodeRequest message. + +The channelID and scalable\_layer\_id parameters shall carry the same value as the channelID and scalable\_layer\_id in the associated setSVCRequest. + +**Table 6-14– setSVCmodeResponse syntax** + +| GenericParameter order | Parameter name | Required presence | +|-------------------------------|-----------------------|--------------------------| +| 1 | channelID | Mandatory | +| 2 | scalable_layer_id | Mandatory | + +# **7 Transport of coded video in ITU-T H.300-series systems** + +## **7.1 Transport of Recommendation ITU-T H.264 video streams** + +Regardless of which ITU-T H.300-series system is in use – ([ITU-T H.310], [ITU-T H.320], [ITU-T H.321], [ITU-T H.322], [ITU-T H.323], or [ITU-T H.324]) – all ITU-T H.264 encoders should take the maximum transmission unit (MTU) size of IP networks into account when choosing the maximum length of ITU-T H.264 NAL Units, as ITU-T H.323 gateways may be used to transport these streams on IP networks. + +To be transported in a maximum-length RTP packet according to [ITU-T H.323], ITU-T H.264 NAL Units should be less than 64 000 bytes long. This value allows a substantial margin for packet header information. + +To avoid IP-layer packet fragmentation (which may increase header overhead and the probability of loss due to errors), ITU-T H.264 NAL Units should be substantially shorter than the MTU size of the network. For example, on an Ethernet network with a 1 472 byte MTU, a 1 200 byte NAL Unit allows for addition of considerable header overhead without exceeding the MTU size of the network. + +### **7.1.1 Parameter set transmission** + +ITU-T H.264 parameter set information shall be transmitted in-band to the ITU-T H.264 video stream (see Note in 7.4.1.2.1 of [ITU-T H.264]). + +Terminals sending ITU-T H.264 video shall transmit each sequence or picture parameter set at a time prior to its reference by any ITU-T H.264 slice. These parameter sets may be re-sent at any time for redundancy. + +NOTE – There is no requirement that parameter sets must be transmitted each time they are about to be referenced by an ITU-T H.264 slice. The transmission may take place at any time prior to the reference. Ordinarily, many ITU-T H.264 slices will refer to the same parameter set, with the parameter set being sent only once. + +### **7.1.2 Use of ITU-T H.264 in BAS-based systems** + +When carried in a BAS-signalling-based system, the ITU-T H.264 video shall make use of the byte stream format given in Annex B of [ITU-T H.264]. + +The resulting byte stream shall be transmitted using the framing and forward error correction method given in clause 5.4 of [ITU-T H.261]. This procedure is the same as that used for [ITU-T H.261] and [ITU-T H.263]. + +Terminals encoding ITU-T H.264 video may insert fill bits using the fill indicator (Fi) as described in clause 5.4.3 of [ITU-T H.261]. + +NOTE – Insertion of such fill may be useful, for example, to reduce the effective coded video data rate within the video channel to avoid exceeding an ITU-T H.264 decoder's maximum video bitrate (MaxBR) as given in Annex A of [ITU-T H.264]. + +### **7.1.3 Transport of ITU-T H.264 streams in ITU-T H.310 systems** + +In ITU-T H.310 systems, the ITU-T H.264 video shall make use of the byte stream format given in Annex B of [ITU-T H.264]. ITU-T H.264 shall be used without BCH error correction and without error correction framing. + +### **7.1.4 Transport of ITU-T H.264 streams in ITU-T H.323 systems** + +In ITU-T H.323 systems, ITU-T H.264 shall be used without BCH error correction and without error correction framing. ITU-T H.323 systems shall not make use of the byte stream format given in Annex B of [ITU-T H.264]. + +All ITU-T H.323 systems that support ITU-T H.264 shall support carriage of the ITU-T H.264 video stream according to Annex A, and shall signal this in their capability set by including `MediaPacketizationCapability.rtpPayload.Type.payloadDescriptor.oid`, with the OID having the value `{itu-t(0) recommendation(0) h(8) h241(241) specificVideoCodecCapabilities(0) h264(0) iPPacketization(0) h241AnnexA(0)}` and a capability class of Video. + +ITU-T H.323 systems that support ITU-T H.264 should also support the non-interleaved mode of [IETF RFC 6184] and may support the interleaved mode of [IETF RFC 6184], in addition to Annex A. + +ITU-T H.323 systems that support ITU-T H.264 Annex G profiles shall support the non-interleaved mode of [IETF RFC 6184]. Furthermore, ITU-T H.323 systems that support ITU-T H.264 Annex G profiles shall support carriage of the ITU-T H.264 SVC stream with the single-session transmission mode of [IETF RFC 6190]. The use of the multi-session transmission mode of [IETF RFC 6190] in ITU-T H.323 systems is for further study. + +The capability of using the non-interleaved mode of [IETF RFC 6184] shall be signalled by including a MediaPacketizationCapability.rtpPayloadType.payloadDescriptor.oid, with the OID having the value {itu-t(0) recommendation(0) h(8) h241(241) specificVideoCodecCapabilities(0) h264(0) iPpacketization(0) rfc6184NonInterleaved(1)} and a capability class of Video. The capability of using the interleaved mode of [IETF RFC 6184] shall be signalled by including a MediaPacketizationCapability.rtpPayloadType.payloadDescriptor.oid, with the OID having the value {itu-t(0) recommendation(0) h(8) h241(241) specificVideoCodecCapabilities(0) h264(0) iPpacketization(0) rfc6184Interleaved(2)} and a capability class of Video. + +NOTE 1 – Since the single NAL unit mode of [IETF RFC 6184] and Annex A are technically identical, the codepoints above permit the use of all packetization modes of [IETF RFC 6184]. + +A sender which signals one of these packetization modes in its Open Logical Channel message shall transmit video according to the corresponding mode of [IETF RFC 6184] or Annex A. + +In the interleaved mode of [IETF RFC 6184], senders and receivers need to have a common understanding of the required buffer sizes for the interleaving buffer. Unless signalled explicitly, these buffer sizes shall take the following values: + +- sprop-interleaving-depth 80 +- sprop-deint-buf-req 65 536 + +The explicit signalling of these parameters is for further study. + +NOTE 2 – See IETF RFC 6184 section 8.1 for a description of both parameters. The values given are sufficient to support macroblock-line interleaved packetization of video signals with 1 080 lines at 8 Mbit/s. See clause III.2.3.1 of [ITU-T H.263] for a discussion of macroblock-line interleaved packetization. + +### 7.1.5 Transport of ITU-T H.264 streams in ITU-T H.324 systems + +In ITU-T H.324 systems, ITU-T H.264 shall be used without BCH error correction and without error correction framing, and shall make use of the byte stream format given in Annex B of [ITU-T H.264]. + +ITU-T H.264 encoders shall align the Annex B of ITU-T H.264 start code prefix for the first NAL unit of each access unit with the start of an AL-SDU. + +### 7.1.6 Sample aspect ratios (informative) + +Transmission of the sample aspect ratio in the VUI parameters specified in Annex E of [ITU-T H.264] was not required in earlier versions of this Recommendation, and many older systems do not indicate the sample aspect ratio in the ITU-T H.264 video bitstream. + +In the absence of an ITU-T H.264 VUI parameter **aspect\_ratio\_idc** value in the received ITU-T H.264 bitstream, and in the case of an **aspect\_ratio\_idc** value equal to 0, the sample aspect ratio may be assumed to have a value according to Table 7-1 below: + +**Table 7-1 – Assumed sample aspect ratios** + +| Frame size
(luma width × luma height) | Sample aspect ratio | +|------------------------------------------|------------------------------------------------------------| +| 128 × 96 (SQCIF) | 12:11 | +| 176 × 144 (QCIF) | 12:11 | +| 352 × 288 (CIF) | 12:11 | +| 704 × 576 (4CIF) | 12:11 | +| 720 × 576 (625 ITU-R BT.601) | 12:11 | +| 352 × 576 (625 HHR) | 24:11 | +| 528 × 576 (625 3/4 HR) | 16:11 | +| 480 × 576 (625 2/3 HR) | 18:11 | +| 352 × 240 (525 SIF) | 10:11 | +| 704 × 480 (525 4SIF) | 10:11 | +| 720 × 480 (525 ITU-R BT.601) | 10:11 | +| 352 × 480 (525 HHR) | 20:11 | +| 528 × 480 (525 3/4 HR) | 40:33 | +| 480 × 480 (525 2/3 HR) | 15:11 | +| 320 × 240 (QVGA) | 1:1 | +| 640 × 480 (VGA) | 1:1 | +| 800 × 600 (SVGA) | 1:1 | +| 1 024 × 768 (XGA) | 1:1 | +| 1 280 × 1 024 (SXGA) | 1:1 | +| 1 600 × 1 200 (UXGA) | 1:1 | +| 1 280 × 720 (720 HD) | 1:1 | +| 1 920 × 1 080 (1080 HD) | 1:1 | +| 1 920 × 1 088 (1080 HD) | 1:1 | +| other | the value which will produce a picture aspect ratio of 4:3 | + +NOTE – All systems which send ITU-T H.264 video should indicate the sample aspect ratio in the VUI parameters specified in Annex E of [ITU-T H.264]. + +# 8 Capability exchange signalling + +## 8.1 General + +Terminals which display received video shall be capable of displaying any picture format and frame rate for which they signal the capability. The format used to display such received video streams is not required to match the exact format transmitted. + +NOTE – For example, a video conferencing system which decodes [ITU-T H.264] at a given Profile and Level must display any picture format and frame rate allowed by that Profile and Level. + +If during an ongoing connection a terminal which is transmitting video receives a changed capability set, the terminal shall adapt its video coding method to conform with all the limitations signalled in the received capability set. + +## 8.2 Signalling of ITU-T H.245 generic parameters in BAS-based systems + +This Recommendation signals a subset of ITU-T H.245 **GenericParameter** structures in BAS channel MBE messages. These messages shall be carried in BAS-based systems using the procedures of Annex A of [ITU-T H.239]. These procedures avoid emulation of the MBE BAS code. + +## 8.3 ITU-T H.264 capabilities + +### 8.3.1 General + +ITU-T H.300-series terminals may optionally support video according to [ITU-T H.264]. + +The ITU-T H.264 capability set is structured as a list of one or more ITU-T H.264 capabilities, each of which includes: + +- Profile (mandatory) +- Level (mandatory) +- Zero or more optional parameters. + +These capabilities indicate the ability to decode using one or more ITU-T H.264 Profiles. The exact syntax and semantics are given in the clauses below. In the case of ITU-T H.245-based systems, each capability is contained in a **GenericCapability** structure. For BAS-based systems, all capabilities are carried in a single MBE message. + +The bitrate made available for a video stream by an ITU-T H.300-series system may be less than the maximum video bitrate which decoders are required to support by Annex A of [ITU-T H.264]. Terminals are not required to decode video streams which they do not receive. + +#### 8.3.1.1 Optional parameters + +For each [ITU-T H.264] capability, optional parameters may be signalled. These parameters permit a terminal to signal that, in addition to meeting the support requirements for the signalled Profile and Level, the terminal has additional capabilities or constraints. + +For ITU-T H.264 SVC, the optional parameters are also used to indicate that one of the scalable profiles is used. This is performed via the AdditionalModesSupported parameter as explained below. + +Terminals shall not signal a set of optional parameters indicating the practical capability to fully support a given Level, without also signalling support for that Level. + +The optional parameters are: + +- 1) CustomMaxMBPS – If present, indicates that the decoder has a higher processing rate capability. +- 2) CustomMaxFS – If present, indicates that the decoder can decode larger picture (frame) sizes. +- 3) CustomMaxDPB – If present, indicates that the decoder has additional decoded picture buffer memory. +- 4) CustomMaxBRandCPB – If present, indicates that the decoder can decode a higher video bitrate and has a correspondingly larger coded picture buffer. +- 5) MaxStaticMBPS – If present, indicates the maximum number of macroblocks per second that the decoder could process in the hypothetical case that all macroblocks are static macroblocks (see clause 8.3.2.8). +- 6) max-rcmd-nal-unit-size – If present, indicates in bytes the maximum recommended NAL unit size. Encoders may exceed this size, but inefficiencies or an increased chance of loss due to errors might result (see clause 8.3.2.9). + +- 7) max-nal-unit-size – If present, indicates in bytes the maximum NAL unit size that the receiver can process. The encoder shall not exceed this size (see clause 8.3.2.10). +- 8) SampleAspectRatiosSupported – If present, indicates the range of supported sample aspect ratios (see clause 8.3.2.11). +- 9) AdditionalModesSupported – If present, indicates one or more additional ITU-T H.264 modes supported (see clause 8.3.2.12). +- 10) AdditionalDisplayCapabilities – If present, indicates one or more additional display capabilities (see clause 8.3.2.13). +- 11) MaxFPS – If present, indicates the maximum picture rate that can be efficiently received or the maximum picture rate that can be sent (see clause 8.3.2.14). + +If these parameters are present, the signalled values replace the MaxMBPS, MaxFS, MaxDPB, MaxBR, and MaxCPB values, respectively, in Table A.1 of [ITU-T H.264] for the given Profile and Level, and indicate that, in addition to fully conforming with the Profile and Level requirements, these additional capabilities are available at the decoder. + +These optional parameters permit, for example, support of $1\,024 \times 768 \times 3$ Hz while using Level 2 (CIF/30 Hz), a common mode for videoconferencing systems. + +NOTE – The use of these optional parameters to signal decoder capabilities does not alter the requirement of [ITU-T H.264] that the **level\_idc** syntax element, set by the encoder in the video bitstream, indicate an Annex A of [ITU-T H.264] Level with which the bitstream fully conforms. The use of these optional parameters permits the encoder to send bitstreams with a Level higher than the Level capability of the decoder, if the bitstream exceeds the decoder's Level capability only within the limits of these optional parameters. To maximize interoperability, encoders should set **level\_idc** to indicate the lowest Level of Annex A of [ITU-T H.264] that the bitstream fully conforms to. + +All ITU-T H.300-series systems which support ITU-T H.264 shall support Baseline Profile, Level 1, in addition to any other Profiles, Levels or optional parameters. + +### 8.3.2 ITU-T H.264 generic capabilities for ITU-T H.245 + +This clause defines the generic capabilities for ITU-T H.264 in the ITU-T H.245 signalling system. + +If a terminal has the capability to decode according to more than one ITU-T H.264 Profile with different Levels capabilities (for example, Baseline Profile at Level 3 and Extended Profile at Level 2) or with different optional parameters for each Profile, this may be signalled by a separate Generic Capability for each supported Profile. + +NOTE – Parameter identifier value 0 is not defined, and should not be defined in the future. This value is reserved so that it can be used in the equivalent BAS-signalling-based system MBE message as a demarcation between separate capabilities within the single MBE message, as defined in Annex A of [ITU-T H.239]. + +#### 8.3.2.1 ITU-T H.264 capability identifier + +See Table 8-1. + +**Table 8-1 – ITU-T H.264 capability identifier** + +| | | +|-----------------------------|---------------------------------------------------------------------------------------------------------| +| Capability name | ITU-T H.241 H.264 Video Capabilities | +| Capability identifier type | standard | +| Capability Class | Video | +| Capability identifier value | {itu-t(0) recommendation(0) h(8) 241 specificVideoCodecCapabilities(0) h264(0) generic-capabilities(1)} | + +**Table 8-1 – ITU-T H.264 capability identifier** + +| | | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxBitRate | This field shall be included, in units of 100 bit/s. This field represents the maximum bitrate of the ITU-T H.264 Type II bitstream as defined in Annex C of [ITU-T H.264]. | +| collapsing | This field shall contain the ITU-T H.264 Capability Parameters as given below. | +| nonCollapsing | This field shall not be included. | +| nonCollapsingRaw | This field shall not be included. | +| transport | This field shall not be included. | + +#### **8.3.2.2 ITU-T H.264 Profile parameter** + +See Table 8-2. + +**Table 8-2 – ITU-T H.264 capability parameter – Profile** + +| | | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | Profile | +| Parameter description |

This parameter is a Boolean array.

If bit 2 (value 64) is 1, this indicates the Baseline Profile.

If bit 3 (value 32) is 1, this indicates the Main Profile.

If bit 4 (value 16) is 1, this indicates the Extended Profile.

If bit 5 (value 8) is 1, this indicates the High Profile.

If bit 6 (value 4) is 1, this indicates the High 10 Profile.

If bit 7 (value 2) is 1, this indicates the High 4:2:2 Profile.

If bit 8 (value 1) is 1, this indicates the High 4:4:4 Profile.

All other bits are reserved, shall be set to 0, and shall be ignored by receivers.

In a capability, for each bit set to 1, this means that the terminal is capable of using the indicated Profile(s) using the Level and other optional parameters in this Generic Capability.

In an OpenLogicalChannel message, for each bit set to 1, this means that the logical channel contents obey all constraints of the indicated Profile(s).

NOTE 1 – Additional Profiles and Additional modes can be signalled in separate parameters – for example, in the AdditionalModesSupported parameter.

NOTE 2 – Bit 1 remains reserved since if the three high-order bits of this parameter are set, this could create an unintentional emulation of the MBE BAS code in [ITU-T H.230].

| +| Parameter identifier value | 41 | +| Parameter status | Mandatory.
This parameter shall appear exactly once in each Generic Capability. | +| Parameter type | booleanArray | +| Supersedes | This field shall not be included. | + +Each ITU-T H.264 Generic Capability shall include the Profile parameter. If the capability signals support only Profiles or Additional Modes, which are not included in this parameter, then all bits in this Profile parameter shall be set to 0. + +##### 8.3.2.2.1 ITU-T H.264 Profile parameter examples (informative) + +For example, support of the Baseline Profile at Level 3 would be signalled with the following parameters: + +- Profile = value 64 (Baseline: bit 2 set); +- Level = value 64 (Level 3, per Table 8-4). + +For example, support of the Baseline Profile at level 2 and RCDO at Level 4 would be signalled with two ITU-T H.264 Generic Capabilities, one with the parameters: + +- Profile = value 64 (Baseline: bit 2 set); +- Level = value 43 (Level 2, per Table 8-4). + +and the other with parameters: + +- Profile = value 0 (no bits set); +- Level = value 85 (Level 4, per Table 8-4); +- AdditionalModesSupported = 64 (RCDO: bit 2 set per Table 8-13). + +For example, support of either the High 10 Profile, the Main Profile, or RCDO, all at Level 2.2 would be signalled with the parameters: + +- Profile = value 36 (Main: bit 3 set, and High 10: bit 6 set); +- Level = value 57 (Level 2.2, per Table 8-4); +- AdditionalModesSupported = 64 (RCDO – bit 2 set per Table 8-13). + +#### 8.3.2.3 ITU-T H.264 Level parameter + +The Level parameter signals the ITU-T H.264 Level. + +**Table 8-3 – ITU-T H.264 capability parameter – Level** + +| Parameter name | Level | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter description | Signals a value according to Table 8-4, indicating the ITU-T H.264 Level. All other values are reserved and shall not be transmitted.
Terminals that receive this signal with a Level parameter value less than the lowest Level parameter value shown in Table 8-4, shall ignore this capability parameter.
NOTE – Such values are reserved for future use.
For all other received Level parameter values, the terminal shall interpret the signalled ITU-T H.264 Level number as the ITU-T H.264 Level number corresponding to the highest Level parameter value in Table 8-4 which is less than or equal to the received Level parameter value. | +| Parameter identifier value | 42 | +| Parameter status | Mandatory.
This parameter shall appear exactly once in each Generic Capability. | +| Parameter type | unsignedMin | +| Supersedes | This field shall not be included. | + +**Table 8-4 – Level parameter values** + +| Level parameter value | ITU-T H.264 Level number | +|-----------------------|--------------------------| +| 15 | 1 | +| 19 | 1b | +| 22 | 1.1 | +| 29 | 1.2 | +| 36 | 1.3 | +| 43 | 2 | +| 50 | 2.1 | +| 57 | 2.2 | +| 64 | 3 | +| 71 | 3.1 | +| 78 | 3.2 | +| 85 | 4 | +| 92 | 4.1 | +| 99 | 4.2 | +| 106 | 5 | +| 113 | 5.1 | +| 120 | 5.2 | + +NOTE 1 – Table 8-4 and this parameter description are constructed such that new ITU-T H.264 Levels defined in the future, which are strictly between or above existing Levels, may be inserted into Table 8-4 in the future. If new Levels are defined which do not meet these constraints, they may be inserted below the lowest existing Level. In that case, new rules for interpreting such Level parameter values will be needed. + +NOTE 2 – The MaxBR and MaxCBP units of Table A.1 of [ITU-T H.264] are considered as equal to 1 200 bit/s by implementers of [ITU-T H.310], [ITU-T H.320], [ITU-T H.323], and [ITU-T H.324], because these systems transport ITU-T H.264 Type II bitstreams as defined in Annex C of [ITU-T H.264]. + +#### 8.3.2.4 ITU-T H.264 CustomMaxMBPS processing rate parameter + +The optional CustomMaxMBPS parameter permits a decoder to signal that it is capable of decoding video at a higher rate than required by the signalled Level. Encoders may use this knowledge to, for example, send pictures of a given size at a higher frame rate. + +**Table 8-5 – ITU-T H.264 capability parameter – CustomMaxMBPS** + +| | | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | CustomMaxMBPS | +| Parameter description | CustomMaxMBPS is the maximum macroblock processing rate, in units of 500 macroblocks per second.
This optional parameter, when present, may be considered by the encoder to replace the MaxMBPS value in Table A.1 of [ITU-T H.264] for the signalled Level. The value of (CustomMaxMBPS × 500) shall not be less than the value MaxMBPS for the Level given in Table A.1 of [ITU-T H.264]. | +| Parameter identifier value | 3 | +| Parameter status | Optional.
This parameter shall appear at most once in each Generic Capability. | +| Parameter type | unsignedMin | +| Supersedes | This field shall not be included. | + +#### 8.3.2.5 ITU-T H.264 CustomMaxFS frame size parameter + +The optional CustomMaxFS parameter permits a decoder to signal that it is capable of decoding larger picture sizes than required by the signalled Level. Encoders may use this knowledge to, for example, send larger pictures at a proportionally lower frame rate. + +**Table 8-6 – ITU-T H.264 capability parameter – CustomMaxFS** + +| | | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | CustomMaxFS | +| Parameter description | CustomMaxFS is the maximum frame size, in units of 256 luma macroblocks.
This optional parameter, when present, shall be considered to replace the MaxFS value in Table A.1 of [ITU-T H.264] for the signalled Level. The value of $(\text{CustomMaxFS} \times 256)$ shall not be less than the value MaxFS for the Level given in Table A.1 of [ITU-T H.264]. | +| Parameter identifier value | 4 | +| Parameter status | Optional.
This parameter shall appear at most once in each Generic Capability. | +| Parameter type | unsignedMin | +| Supersedes | This field shall not be included. | + +#### 8.3.2.6 ITU-T H.264 CustomMaxDPB memory parameter + +The optional CustomMaxDPB parameter permits a decoder to signal that it has more than the minimum amount of decoded picture buffer memory required by the signalled Level. Encoders may use this knowledge to construct coded video streams with improved compression. + +A system which signals CustomMaxDPB shall be capable of storing the value of $(\text{CustomMaxDPB} \times 256/3)$ macroblocks in its decoded picture buffer. + +**Table 8-7 – ITU-T H.264 capability parameter – CustomMaxDPB** + +| | | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | CustomMaxDPB | +| Parameter description | CustomMaxDPB is the maximum decoded picture buffer size, in units of 256/3 macroblocks.
This optional parameter, when present, shall be considered to replace the MaxDpbMbs value in Table A.1 of [ITU-T H.264] for the signalled Level. The value of $(\text{CustomMaxDPB} \times 256/3)$ shall not be less than the value (MaxDpbMbs) for the Level given in Table A.1 of [ITU-T H.264]. | +| Parameter identifier value | 5 | +| Parameter status | Optional.
This parameter shall appear at most once in each Generic Capability. | +| Parameter type | unsignedMin | +| Supersedes | This field shall not be included. | + +#### 8.3.2.7 ITU-T H.264 CustomMaxBRandCPB bitrate and coded picture buffer size parameter + +The optional CustomMaxBRandCPB parameter permits a decoder to signal that it is capable of decoding video streams of higher bitrate, and that it has a correspondingly larger coded picture buffer, than required by the signalled Level. Encoders may use this knowledge to, for example, send higher bitrate video to achieve improved video quality. + +**Table 8-8 – ITU-T H.264 capability parameter – CustomMaxBRandCPB** + +| | | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | CustomMaxBRandCPB | +| Parameter description |

CustomMaxBRandCPB is the maximum video bitrate. The maximum coded picture buffer (CPB) size is derived from the maximum video bitrate.

The units for maximum video bitrate are 25 000 bit/s for the VCL HRD parameters and 30 000 bit/s for the NAL HRD parameters.

NOTE – For transport of ITU-T H.264 bitstreams in ITU-T H.310, ITU-T H.320, ITU-T H.323, and ITU-T H.324 the appropriate video bitrate unit is 30 000 bit/s, because these systems transport Type II ITU-T H.264 bitstreams as defined in Annex C of [ITU-T H.264]. This parameter does not use units of cpbBrVclFactor and cpbBrNALFactor, (see Table A.1 of [ITU-T H.264] and Table A.2 of [ITU-T H.264]).

The CPB size shall be derived as equal to the MaxCPB for the signalled Level (see Table A.1 of [ITU-T H.264]), multiplied by the ratio of the signalled maximum bitrate to the MaxBR for the signalled level.

For example, if a terminal signals Level 1.2 with CustomMaxBRandCPB equal to 62, this indicates a maximum video bitrate of 1.550 Mbit/s for VCL HRD parameters, a maximum video bitrate of 1.860 Mbit/s for NAL HRD parameters, and a CPB size of 4 036 458 bits

((62 \times 25\,000)/384\,000) \times 1\,000 \times 1\,000.

This optional parameter, when present, shall be considered to replace the MaxBR and MaxCPB values in Table A.1 of [ITU-T H.264] for the signalled Level. The bit rate signalled by the CustomMaxBRandCPB parameter shall not be less than the maximum bit rate given in the MaxBR column of Table A.1 of [ITU-T H.264], for the Level signalled.

| +| Parameter identifier value | 6 | +| Parameter status | Optional.
This parameter shall appear at most once in each Generic Capability. | +| Parameter type | unsignedMin | +| Supersedes | This field shall not be included. | + +#### 8.3.2.8 ITU-T H.264 MaxStaticMBPS processing rate parameter + +The optional MaxStaticMBPS parameter permits a decoder to signal that it is capable of decoding video containing static macroblocks at a higher rate than required by the signalled Level. Encoders may use this knowledge to, for example, send pictures of a given size at a higher frame rate. + +In the ITU-T H.264 context, static macroblocks are defined as macroblocks for which all of the following conditions are fulfilled: + +- 1) CodedBlockPatternLuma and CodedBlockPatternChroma, when assigned a value in ITU-T H.264, are both equal to 0; and +- 2) either of the following conditions are fulfilled: + - a) mb\_type is equal to P\_Skip or P\_L0\_16x16 and weighted\_pred\_flag is not equal to 1; or + - b) mb\_type is equal to B\_Skip, B\_Direct\_16x16, B\_L0\_16x16, or B\_L1\_16x16 and weighted\_bipred\_idc is not equal to 1; +- 3) only a single list X for X = 0 or 1 (List 0 or List 1) is used in the inter prediction process for the macroblock, within which the values of mvLX[0], mvLX[1], and refIdxLX are all equal to 0; and + +- 4) either of the following conditions are fulfilled: +- a) the macroblock is a frame macroblock and the reference index value 0 refers to the immediately-preceding frame or complementary field pair in decoding order and the immediately-preceding picture in decoding order is not a non-paired field; or + - b) the macroblock is a field macroblock and the reference index value 0 refers to the immediately-preceding field of the same parity in decoding order. + +NOTE – The conditions specified above result in a decoding process for macroblocks consisting of copying samples from the same position as the current macroblock in the preceding reference picture in decoding order. The conditions specified above also identify only those macroblocks for which at most one motion vector difference is present in the bitstream. + +All other macroblocks are non-static macroblocks. + +**Table 8-9 – ITU-T H.264 capability parameter – MaxStaticMBPS** + +| | | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | MaxStaticMBPS | +| Parameter description |

MaxStaticMBPS is the maximum number of static macroblocks per second the decoder can process under the assumption that all macroblocks are static macroblocks, in units of 500 macroblocks per second.

When this optional parameter is present the value of MaxMBPS in Table A.1 of [ITU-T H.264] for the signalled Level should be considered by the encoder to be equal to the result of the following procedure:

  1. 1) If the optional parameter CustomMaxMBPS is signalled, set a variable MaxMacroblocksPerSecond equal to the value (CustomMaxMBPS × 500). Otherwise, set MaxMacroblocksPerSecond equal to the value of MaxMBPS for the Level given in Table A.1 of [ITU-T H.264].
  2. 2) Set a variable Pnon-static to the proportion of non-static macroblocks in picture n.
  3. 3) Set a variable Pstatic to the proportion of static macroblocks in picture n.
  4. 4) The value of MaxMBPS in Table A.1 of [ITU-T H.264] for the signalled Level should be considered by the encoder to be equal to: \frac{1}{\frac{P_{non-static}}{MaxMacroblocksPerSecond} + \frac{P_{static}}{MaxStaticMBPS \times 500}}

    The encoder should recompute this value for each picture.

    The value of (MaxStaticMBPS × 500) shall not be less than the value MaxMBPS for the Level given in Table A.1 of [ITU-T H.264], and if CustomMaxMBPS is signalled, shall not be less than the value (CustomMaxMBPS × 500).

    The computed value of MaxMBPS should be used by the encoder to determine the minimum interval between picture n and picture n+1, as specified in the references to MaxMBPS in Annex A of [ITU-T H.264].

| +| Parameter identifier value | 7 | +| Parameter status | Optional.
This parameter shall appear at most once in each Generic Capability. | +| Parameter type | unsignedMin | +| Supersedes | This field shall not be included. | + +##### 8.3.2.8.1 Use of ITU-T H.264 MaxStaticMBPS example (informative) + +This clause does not form an integral part of this Recommendation. + +For example, suppose a Level 1.2 capable decoder (MaxMBPS = 6 000) with a signalled MaxStaticMBPS value of 120 (a processing rate of 60 000 static macroblocks per second) is receiving XGA video (1 024 × 768 luma samples per picture), which contains 3 072 luma macroblocks per picture, and that only a mouse cursor is moving in the video scene. (This example assumes the decoder has a CustomMaxFS value that permits this picture size.) + +Suppose further that encoding the mouse cursor region requires only 4 macroblocks in a particular picture, so all other macroblocks can be static macroblocks. The procedure described above yields a MaxMBPS of 59 305 macroblocks per second ( $1 / ((4 / 3\,072) / 6\,000) + (((3\,072 - 4) / 3\,072) / 60\,000)$ ). + +This would permit the encoder to generate the next picture after an interval of 51.8 ms ( $3\,072 / 59\,305$ ), corresponding to an instantaneous frame rate of 19.3 Hz ( $59\,305 / 3\,072$ ), compared to an interval of 512 ms ( $3\,072 / 6\,000$ ), corresponding to an instantaneous frame rate of only 2.0 Hz without the use of MaxStaticMBPS. + +##### 8.3.2.8.2 Determination of ITU-T H.264 MaxStaticMBPS value (informative) + +This clause does not form an integral part of this Recommendation. It provides informative guidance regarding considerations for the determination of the MaxStaticMBPS value for a given decoder implementation. + +Practical decoder implementations make use of a wide variety of hardware and software architectures, and there may be no single method of determining a decoder's value of MaxStaticMBPS that is appropriate in all cases; determination of this value is left to the implementer. + +One possible method is described here solely as an example: + +- 1) Given an implementation which can decode sequences containing only non-static macroblocks at a rate of $R_{decode}$ macroblocks per second. +- 2) An encoded test video sequence with a known number of macroblocks ( $N$ ), proportion of static macroblocks ( $P_{static}$ ), and of non-static macroblocks ( $P_{non-static} = 1 - P_{static}$ ) can be decoded, and the time required to decode either each picture or the entire sequence measured by experiment ( $T_{decode}$ in seconds). +- 3) The rate at which static macroblocks can be decoded (StaticMBPS) can be calculated by: + +$$\text{StaticMBPS} = P_{static} / (T_{decode} / N - P_{non-static} / R_{decode})$$ + +This procedure can be repeated with different test sequences containing different proportions of static and non-static macroblocks and different picture sizes. + +- 4) The values of StaticMBPS obtained can be plotted against varying values of $P_{static}$ and picture size tested, and interpolation applied between the test points. (Note that in many decoder implementation architectures, the plot of StaticMBPS versus picture size will form a curve.) +- 5) The lowest value of StaticMBPS obtained on the plots could then be used as the value of MaxStaticMBPS. + +In some decoder implementation architectures, the decoding rate is affected by a deblocking filter computation where static and non-static macroblocks are adjacent to each other. To take account of this factor, worst-case test patterns of static and non-static macroblocks can be used. + +#### 8.3.2.9 ITU-T H.264 max-rcmd-nal-unit-size + +The value of this parameter indicates the largest NAL unit size in bytes that the receiver can handle efficiently. The parameter value is a recommendation, not a strict upper boundary. The sender may create larger NAL units but implementers should consider that inefficiencies or an increased chance of loss due to errors might result. + +**Table 8-10 – ITU-T H.264 capability parameter – max-rcmd-nal-unit-size** + +| | | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | max-rcmd-nal-unit-size | +| Parameter description | The value of this parameter indicates the largest NAL unit size in bytes that the receiver is able to handle efficiently. The parameter may have values in the range of 0 to 4 294 967 295, inclusive. | +| Parameter identifier value | 8 | +| Parameter status | Optional.
This parameter shall appear at most once in each Generic Capability. | +| Parameter type | Integer | +| Supersedes | This field shall not be included. | + +#### 8.3.2.10 ITU-T H.264 max-nal-unit-size + +The value of this parameter indicates the largest NAL unit size in bytes that the receiver is able to handle at all. The sender shall not create NAL units larger than this size. + +In the absence of this signal, senders shall not create NAL units larger than 1 400 bytes when using the Interleaved or Non-Interleaved packetization modes. When operating in the Annex A packetization mode, senders should not create NAL units larger than 1 400 bytes. + +**Table 8-11 – ITU-T H.264 capability parameter – max-nal-unit-size** + +| | | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | max-nal-unit-size | +| Parameter description | The value of this parameter indicates the largest NAL unit size in bytes that the receiver can process. The parameter can have values in the range of 0 to 4 294 967 295, inclusive. | +| Parameter identifier value | 9 | +| Parameter status | Optional.
This parameter shall appear at most once in each Generic Capability. | +| Parameter type | unsigned32Min | +| Supersedes | This field shall not be included. | + +#### 8.3.2.11 ITU-T H.264 SampleAspectRatiosSupported capability + +In a receive capability, the value of this parameter indicates the range of sample aspect ratios that the receiver is able to display without geometric (shape) distortion. + +In an ITU-T H.245 **OpenLogicalChannel** message, the value of this parameter indicates the range of sample aspect ratios that the Logical Channel will ever contain. + +**Table 8-12 – ITU-T H.264 capability parameter – SampleAspectRatiosSupported** + +| | | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | SampleAspectRatiosSupported | +| Parameter description |

The value of this parameter indicates support of sample aspect ratios corresponding to ITU-T H.264 aspect_ratio_idc values in the range from 1 to N inclusive, where N is the value of this parameter (see Table E.1 of [ITU-T H.264]).

This parameter shall not take a value outside the range 1 to 254.

NOTE – Support of Table E.1 of ITU-T H.264 Extended_SAR (aspect_ratio_idc value 255) may be signalled using the AdditionalDisplayCapabilities parameter.

| +| Parameter identifier value | 10 | +| Parameter status |

Optional.

This parameter shall appear at most once in each Generic Capability.

| +| Parameter type | unsignedMin | +| Supersedes | This field shall not be included. | + +Terminals that signal this parameter: + +- a) shall not send pictures using a sample aspect ratio outside the range signalled by the receiver in the SampleAspectRatiosSupported capability parameter; and +- b) shall indicate in the VUI parameters specified in Annex E of [ITU-T H.264] the actual sample aspect ratio in any transmitted ITU-T H.264 video streams; and +- c) shall consider the sample aspect ratio as a part of the video mode when Multipoint Mode Symmetrize (MMS) according to [ITU-T H.243] is in effect, or **multipointModeCommand** according to [ITU-T H.245] is in effect; and +- d) shall signal a SampleAspectRatiosSupported value of 1 or greater in their receive capability set; and +- e) should signal a SampleAspectRatiosSupported value of 3 or greater in their receive capability set; and +- f) in the absence of a received SampleAspectRatiosSupported capability parameter, shall not send any pictures except for those with either: + - 1) a picture aspect ratio of 4:3; or, + - 2) a sample aspect ratio in the range of 10:11 to 12:11. + +NOTE 1 – The sample aspect ratio 12:11 is part of the definition of QCIF, CIF, and 4CIF format pictures. + +Terminals are not required to conform with b) above if they transmit a video stream derived from a source with a sample aspect ratio which is unknown. + +MCUs are not required to conform with a) and f) above if the SampleAspectRatiosSupported capabilities expressed by the connected receivers are not identical. + +NOTE 2 – In some multipoint conferences, a small minority of end points supports a more limited set of sample aspect ratios than the majority of end points. MCUs are not required to conform with a) and f) above, so that they are free in such cases to choose a video mode that is most appropriate for the majority of end points. In such cases, it should be noted that the provisions of clause 8.1 continue in force. + +#### 8.3.2.12 AdditionalModesSupported parameter + +The optional AdditionalModesSupported parameter permits a terminal to signal that it is capable of decoding using one or more additional video modes, aside from those defined by ITU-T H.264 Profiles. AdditionalModesSupported also permits a terminal to signal that it is capable of decoding one or more scalable profiles of ITU-T H.264 SVC. + +**Table 8-13 – ITU-T H.264 capability parameter – AdditionalModesSupported** + +| | | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | AdditionalModesSupported | +| Parameter description |

This parameter is a Boolean array.

If bit 2 (value 64) is 1, this indicates support of the Reduced Complexity Decoding Operation (RCDO) as specified in Annex B/H.241.

If bit 3 (value 32) is 1, this indicates the Scalable Baseline profile as specified in Annex G of [ITU-T H.264].

If bit 4 (value 16) is 1, this indicates the Scalable High profile as specified in Annex G of [ITU-T H.264] .

All other bits are reserved, shall be set to 0, and shall be ignored by receivers.

In a decoder capability, for each bit set to 1, this means that the terminal is capable of decoding the indicated mode(s) using the Level and other optional parameters in this Generic Capability.

In an OpenLogicalChannel message, for each bit set to 1, this means that the logical channel contents obey all constraints of the indicated mode(s).

NOTE 1 – If more ITU-T H.264 additional modes are defined in the future than the number of reserved bits can accommodate, additional modes could be signalled by allocating another parameter for more modes.

NOTE 2 – Bit 1 is reserved since, if the three high-order bits of this parameter are set, the procedures of Annex A of [ITU-T H.239] will produce an extra byte of output to avoid unintentional emulation of the MBE BAS code in [ITU-T H.230].

| +| Parameter identifier value | 11 | +| Parameter status | Optional.
This parameter shall appear at most once in each Generic Capability. | +| Parameter type | booleanArray | +| Supersedes | This field shall not be included. | + +NOTE – Some modes (for example, RCDO) are distinct from any Profile defined in [ITU-T H.264]. For the purposes of this Recommendation, such modes are signalled in this parameter as if they were independent Profiles. If a terminal has the capability to support one or more modes or Profiles with different Levels capabilities or with different optional parameters for each mode or Profile, this can be signalled by a separate Generic Capability for each supported Profile or mode. + +The bits of this parameter are used in the same way as the bits of the Profile parameter. In a capability, for each bit set to 1, this means that the terminal is capable of supporting the indicated mode(s) using the Level and other optional parameters in this Generic Capability. In an OpenLogicalChannel message, for each bit set to 1, this means that the logical channel contents obey all constraints of the indicated mode(s). + +For example, if a decoder is capable of supporting Baseline Profile at Level 3 and RCDO at Level 4, this shall be signalled with one capability with a Profile value of 64 (Baseline) and a Level value of 64 (Level 3), and another capability with a Profile value of 0 (no Profile), a Level value of 85 (Level 4), and an AdditionalModesSupported value of 64 (RCDO). + +#### 8.3.2.13 AdditionalDisplayCapabilities parameter + +The optional AdditionalDisplayCapabilities parameter permits a terminal to signal additional abilities to display decoded video. + +**Table 8-14 – ITU-T H.264 capability parameter – AdditionalDisplayCapabilities** + +| | | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | AdditionalDisplayCapabilities | +| Parameter description |

This parameter is a Boolean array.

If bit 2 (value 64) is 1, this indicates support of all sample aspect ratios which are expressible using the ITU-T H.264 aspect_ratio_idc value of 255 (Extended_SAR, see Table E.1 of [ITU-T H.264]). A terminal that sets this bit to 1 shall also signal SampleAspectRatiosSupported with a parameter value of 13 or greater.

All other bits are reserved, shall be set to 0, and shall be ignored by receivers.

NOTE – Bit 1 is reserved since if the three high-order bits of this parameter are set, the procedures of Annex A of [ITU-T H.239] will produce an extra byte of output to avoid unintentional emulation of the MBE BAS code in [ITU-T H.230].

| +| Parameter identifier value | 12 | +| Parameter status | Optional.
This parameter shall appear at most once in each Generic Capability. | +| Parameter type | booleanArray | +| Supersedes | This field shall not be included. | + +#### 8.3.2.14 ITU-T H.264 MaxFPS frame rate parameter + +The value of this parameter in a receive capability indicates the maximum picture frame rate that the receiver can efficiently handle. Any encoder that understands the parameter semantics shall constrain the frame rate to rates up to that specified. A receiver should have the ability to process video from a sender that does not understand this parameter. + +If the parameter is absent, the encoder is free to choose any value for the frame rate that satisfies the other parameters. + +When included in an **openLogicalChannel** message or a transmit capability, the value of this parameter indicates the maximum picture rate that shall be sent. For example, when encoding an NTSC 480p source, the value of MaxFPS in the **openLogicalChannel** message would be 5994 (59.94 pictures per second). When encoding an NTSC 480i source, the value of MaxFPS would be 2997 (29.97 pictures per second). + +**Table 8-14a – ITU-T H.264 capability parameter – MaxFPS** + +| | | +|----------------------------|-----------------------------------------------------------------------------------------------------------------| +| Parameter name | MaxFPS | +| Parameter description | MaxFPS is the maximum picture rate at which frames should be sent, in units of hundredths of frames per second. | +| Parameter identifier value | 13 | +| Parameter status | Optional | +| Parameter type | unsignedMin | +| Supersedes | This field shall not be included | + +### 8.3.3 ITU-T H.264 capabilities for BAS-based systems + +#### 8.3.3.1 ITU-T H.320 video algorithm hierarchy + +The ITU-T H.320 enhanced video algorithm hierarchy in Annex A of [ITU-T H.320] is not extended for ITU-T H.264. No relative level in the hierarchy is specified for ITU-T H.264 with regard to other video codecs. + +#### 8.3.3.2 ITU-T H.264 capabilities MBE message format + +For ITU-T H.264 operation, the capabilities exchange is handled by a multiple byte extension (MBE) message (see clause 2.2.3 of [ITU-T H.230]). This MBE message uses the type identification byte (see Table 2 of [ITU-T H.230]). A terminal shall signal the ITU-T H.264 capability by including within its capability set the message: + +$$\{ \text{Start-MBE} / N / \langle \text{H.264} \rangle / B_1 / \dots / B_{N-1} \}$$ + +The ITU-T H.264 capability MBE bytes $B_1$ through $B_{N-1}$ may contain one or more encoding or decoding capabilities for ITU-T H.264. + +Each capability, which corresponds to a single ITU-T H.245 **GenericCapability** message, consists of the mandatory Profile and Level parameters, and an optional set of zero or more **parameterIdentifier/parameterValue** pairs from the set of ITU-T H.264 generic capability parameters defined in clause 8.3.2. These pairs are carried in the format given in clause 8.2 above. + +Encoder capabilities are for further study. + +The first two bytes of each decoder capability within the MBE shall contain the ITU-T H.264 Profile parameter, followed by the ITU-T H.264 Level parameter, as defined in Tables 8-2 and 8-3. No parameter identifier is included in the MBE, as these mandatory parameters are identified by their position in the decoder capability string. + +Following the Profile and Level parameters, zero or more **parameterIdentifier/parameterValue** pairs containing the optional CustomMaxMBPS, CustomMaxFS, CustomMaxDPB, and CustomMaxBRandCPB parameters may be included, according to the syntax and semantics given for these parameters. The set of **parameterIdentifier/parameterValue** pairs may appear in any order within the capability. + +If the ITU-T H.264 capability MBE contains more than one capability, the second and succeeding capabilities within the MBE message shall be demarcated by a single byte of value zero immediately before the start of each succeeding capability. + +NOTE – This zero byte appears in the position where a Parameter ID would otherwise appear. Since the ITU-T H.264 generic capabilities do not define a parameter with a **parameterIdentifier** value of zero, no confusion results. + +Receivers shall ignore the value of any **parameterValue** following an undefined **parameterIdentifier**. + +Table 8-15 below gives an example of an MBE with a single decoder capability indicating Baseline Profile, Level 3.1, with a CustomMaxMBPS parameter of 246 000 macroblocks/second: + +**Table 8-15 – Baseline Profile example MBE** + +| MBE | Value | Description | +|---------------|--------------|----------------------------------------------------------| +| Byte 1 | Start-MBE | Start of MBE. From ITU-T H.230 | +| Byte 2 | 6 | Number of bytes to follow | +| Byte 3 | | Indicates ITU-T H.264 MBE. From ITU-T H.230 | +| Byte 4 | 64 | Profile parameter – indicates Baseline Profile | +| Byte 5 | 71 | Level parameter – indicates Level 3.1 | +| Byte 6 | 3 | Parameter ID – CustomMaxMBPS | +| Byte 7 | 172 | Lowest 6 bits of 492 (equals 246 000/500), ORed with 128 | +| Byte 8 | 7 | Remaining 7 bits of 492 | + +Table 8-16 gives an example ITU-T H.264 capability MBE for a system that supports two capabilities: + +- Baseline Profile, Level 2.2; and +- Main Profile, Level 2, with CustomMaxFS supporting 800 × 600 SVGA format and CustomMaxMBPS supporting this format at a rate of 10 frames per second. + +**Table 8-16 – Two Profile example MBE** + +| MBE | Value | Description | +|----------------|--------------|--------------------------------------------------------------------| +| Byte 1 | Start-MBE | Start of MBE. From ITU-T H.230 | +| Byte 2 | 10 | Number of bytes to follow | +| Byte 3 | | Indicates ITU-T H.264 MBE. From ITU-T H.230 | +| Byte 4 | 32 | Profile parameter – indicates Main Profile | +| Byte 5 | 43 | Level parameter – indicates Level 2 | +| Byte 6 | 4 | Parameter ID – CustomMaxFS | +| Byte 7 | 8 | Indicates 2 048 macroblock frame size (1 900 needed for 800 × 600) | +| Byte 8 | 3 | Parameter ID – CustomMaxMBPS | +| Byte 9 | 38 | Indicates 19 000 macroblocks/s processing rate. | +| Byte 10 | 0 | Demarcates start of new capability | +| Byte 11 | 64 | Profile parameter – indicates Baseline Profile. | +| Byte 12 | 57 | Level parameter – indicates Level 2.2 | + +# **Annex A** + +## **ITU-T H.264 transport for ITU-T H.323** + +(This annex forms an integral part of this Recommendation.) + +ITU-T H.323 terminals which support the transport of video according to [ITU-T H.264] shall support the single NAL unit mode of [IETF RFC 6184]. ITU-T H.323 terminals which support the transport of video according to ITU-T H.264 Annex G profiles shall support the non-interleaved mode of [IETF RFC 6184] and the single-session transmission mode of [IETF RFC 6190]. ITU-T H.323 terminals may additionally support other modes. + +NOTE – The single NAL unit mode of [IETF RFC 6184] is technically identical to the text contained in previous editions of this annex. + +# Annex B + +## Reduced-complexity decoding operation (RCDO) for ITU-T H.264 Baseline Profile bitstreams + +(This annex forms an integral part of this Recommendation.) + +## B.1 Scope + +This annex specifies a reduced-complexity decoding operation (RCDO) for use with ITU-T H.264 Baseline profile bitstreams. This annex also specifies a bitstream constraint associated with the RCDO, and a mechanism for signalling the RCDO within the bitstream that the bitstream conforms to the bitstream constraint, and that the decoder should apply the RCDO decoding process to the bitstream. It also specifies that a decoder is required to apply the RCDO decoding process when the use of RCDO has been negotiated using this Recommendation. + +## B.2 Definitions + +This annex defines the following terms: + +**B.2.1 RCDO bitstream:** An ITU-T H.264 bitstream that conforms to clause B.4. + +**B.2.2 RCDO SEI message:** An ITU-T H.264 user data unregistered SEI message as specified in Table B.1 that directly follows a sequence parameter set NAL unit. + +## B.3 General + +In this annex, reference is made to specific elements of [ITU-T H.264]. The modifications in this annex apply only to bitstreams that obey all constraints specified for the Baseline profile of [ITU-T H.264], in particular including clause A.2.1 of ITU-T H.264 (Baseline profile). For the purposes of Annex A of [ITU-T H.264], the Level requirements are the same for RCDO use as for non-RCDO use of the ITU-T H.264 Baseline profile. When RCDO use has been negotiated using this Recommendation, the decoder shall perform the decoding process specified as the RCDO decoding process in this annex. + +## B.4 RCDO bitstreams + +RCDO bitstreams shall: + +- conform to the Baseline profile of ITU-T H.264 (profile\_idc equal to 66) and to the additional constraint specified below in clause B.4.1; and +- include a user data unregistered SEI message according to clause D.1.6 of [ITU-T H.264] containing the values given in Table B.1 below. An RCDO SEI message shall follow immediately after each ITU-T H.264 sequence parameter set NAL unit. + +**Table B.1 – User data unregistered SEI message +indicating a bitstream encoded for RCDO** + +| | | +|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UUID_iso_iec_11578
(hexadecimal format) | a1f775a0bb0911daab1d0002a5d5c51b | +| Payload bytes | Exactly one payload byte shall follow. This byte shall contain the AdditionalModesSupported booleanArray according to Table 8-13. Bit 2 (value 64) of this BooleanArray shall be set equal to 1. | + +### B.4.1 Constraint on luma inter prediction block sizes to $8 \times 8$ samples or larger + +The value of sub\_mb\_type as specified in [ITU-T H.264], when applicable, shall always be equal to 0. + +## B.5 OpenLogicalChannel signalling + +In an ITU-T H.245 **OpenLogicalChannel** message, bit 2 of the AdditionalModesSupported parameter in Table 8-13 shall be equal to 1 and the Profile parameter shall be equal to 0. + +For the purpose of robustness to transmission errors, a decoder that is capable of using the RCDO decoding process should cross-check the presence or absence of the RCDO SEI message with the content of the OpenLogicalChannel message. When bit 2 of the AdditionalModesSupported parameter is equal to 1 and the RCDO SEI message is not detected by the decoder, a decoder should send a videoFastUpdatePicture message to the encoder to force retransmission of the RCDO SEI message. + +## B.6 Procedures + +When the use of RCDO has been negotiated using this Recommendation and the bitstream is a conforming RCDO bitstream (as specified in clause B.4 above), the RCDO decoding process, as specified in this clause, shall be applied by the decoder. To avoid accumulation of "drift" error in the decoded video sequence, the encoder should model the RCDO decoding process accurately during the encoding process. + +### B.6.1 Reduced-complexity interpolation for inter prediction in the RCDO decoding process + +The operations specified in clause 8.4.2.2 of [ITU-T H.264], "Fractional sample interpolation, process" shall be performed with the changes specified in this clause during operation of the RCDO decoding process. The modifications are as follows: + +- 1) Referencing clause 8.4.2.2 of [ITU-T H.264], the following modifications apply: + - frame\_num is an additional input to the process. + - (xFracc,yFracc) is in quarter sample units instead of one-eighth sample units. + - Rather than using Equations 8-227 through 8-230 of [ITU-T H.264], the following modified equations apply: + +$$xInt_c = ( x_{AL} / SubWidthC ) + ((mvCLX[ 0 ] + (frame\_num \& 1)) \gg 3 ) + x_c \quad (8-227)$$ + +$$yInt_c = ( y_{AL} / SubHeightC ) + ((mvCLX[ 1 ] + (frame\_num \& 1)) \gg 3 ) + y_c \quad (8-228)$$ + +$$xFrac_c = ((mvCLX[ 0 ] + (frame\_num \& 1)) \gg 1) \& 3 \quad (8-229)$$ + +$$yFrac_c = ((mvCLX[ 1 ] + (frame\_num \& 1)) \gg 1) \& 3 \quad (8-230)$$ + +- 2) Referencing 8.4.2.2.1 of [ITU-T H.264], the following modifications apply: + - The luma prediction values at half sample positions b and s are derived by applying a 6-tap filter with tap values ( 1, -5, 20, 20, -5, 1 ). + - The luma prediction values at half sample positions h and m are derived by applying a 4-tap filter with tap values ( -1, 5, 5, -1 ). + - Equations 8-241, 8-242, 8-245 and 8-246 to define b1, h1 and j1 in [ITU-T H.264] are not needed. + - Rather than using Equations 8-243, 8-244, 8-247, 8-248, 8-249, 8-254, 8-255, 8-256 and 8-257 of [ITU-T H.264], the following modified equations apply: + +$$b = \text{Clip1}_Y( (E - 5 * F + 20 * G + 20 * H - 5 * I + J + 6) \gg 5 ) \quad (8-243)$$ + +$$h = \text{Clip1}_Y( ( - C + 5 * G + 5 * M - R + 1 ) \gg 3 ) \quad (8-244)$$ + +$$j = ( H + M ) \gg 1 \quad (8-247)$$ + +$$s = \text{Clip1}_Y((K - 5 * L + 20 * M + 20 * N - 5 * P + Q + 6) \gg 5) \quad (8-248)$$ + +$$m = \text{Clip1}_Y((-D + 5 * H + 5 * N - S + 1) \gg 3) \quad (8-249)$$ + +$$f = (G + m + 1) \gg 1 \quad (8-254)$$ + +$$i = (M + b + 1) \gg 1 \quad (8-255)$$ + +$$k = (H + s + 1) \gg 1 \quad (8-256)$$ + +$$q = (N + h + 1) \gg 1 \quad (8-257)$$ + +- 3) Referencing 8.4.2.2.2 of [ITU-T H.264], the following modifications apply: +- Figure B.1 depicts the position of integer and fractional chroma sample positions. + +![Figure B.1: A 5x5 grid of blocks representing sample positions for quarter sample chroma interpolation. The grid is labeled with upper-case letters (A, B, C, D) for integer sample positions and lower-case letters (a, b, c, d, e, f, g, h, i, j, k, m, n, p, q, r, s) for fractional sample positions. The grid is arranged as follows: Row 1: A (shaded), a, b, c, B (shaded); Row 2: d, e, f, g, (empty); Row 3: h, i, j, k, m; Row 4: n, p, q, r, (empty); Row 5: C (shaded), (empty), s, (empty), D (shaded).](a93de4c3f80bd4a972ab65510b09b68d_img.jpg) + +Figure B.1: A 5x5 grid of blocks representing sample positions for quarter sample chroma interpolation. The grid is labeled with upper-case letters (A, B, C, D) for integer sample positions and lower-case letters (a, b, c, d, e, f, g, h, i, j, k, m, n, p, q, r, s) for fractional sample positions. The grid is arranged as follows: Row 1: A (shaded), a, b, c, B (shaded); Row 2: d, e, f, g, (empty); Row 3: h, i, j, k, m; Row 4: n, p, q, r, (empty); Row 5: C (shaded), (empty), s, (empty), D (shaded). + +**Figure B.1 – Integer sample positions (shaded blocks with upper-case letters) and fractional sample positions (un-shaded blocks with lower-case letters) for quarter sample chroma interpolation** + +- For further specification of integer and fractional chroma sample positions, Table 8-12 of [ITU-T H.264] also applies for assignment of chroma prediction sample $\text{predPartLX}_c[x_c, y_c]$ by replacing subscript $L$ by subscript $c$ , and by replacing $G$ with $A$ . +- To specify $\text{predPartLX}_c[x_c, y_c]$ , rather than using Equation 8-270 of [ITU-T H.264], the following expressions apply: + +$$b = (A + B) \gg 1$$ + +$$h = (A + C) \gg 1$$ + +$$j = (B + C) \gg 1$$ + +$$m = (B + D) \gg 1$$ + +$$s = (C + D) \gg 1$$ + +$$a = (A + b + 1) \gg 1$$ + +$$c = (B + b + 1) \gg 1$$ + +$$d = (A + h + 1) \gg 1$$ + +$$e = (b + h + 1) \gg 1$$ + +$$f = (A + m + 1) \gg 1$$ + +$$g = (b + m + 1) \gg 1$$ + +$$i = (C + b + 1) \gg 1$$ + +$$k = (B + s + 1) \gg 1$$ + +$$n = (C + h + 1) \gg 1$$ + +$$p = (h + s + 1) \gg 1$$ + +$$q = ( D + h + 1 ) \gg 1$$ + +$$r = ( m + s + 1 ) \gg 1$$ + +### B.6.2 Reduced-complexity deblocking filter in the RCDO decoding process + +During operation of the RCDO decoding process, rather than applying the deblocking filter as specified in 8.7 of [ITU-T H.264], "Deblocking filter process", the deblocking filter shall be applied as specified in this clause. The definitions of indexA and indexB are as specified in Equations 8-454 of [ITU-T H.264] and 8-455 of [ITU-T H.264]. + +#### B.6.2.1 Deblocking filter process + +A conditional filtering is applied to all $4 \times 4$ block edges of a picture, except edges at the boundary of the picture and any edges for which the deblocking filter process is disabled by disable\_deblocking\_filter\_idc, as specified below. This filtering process is performed on a macroblock basis after completion of the picture construction process prior to the deblocking filter process (as specified in 8.5.14 of [ITU-T H.264]) for the entire decoded picture, with all macroblocks in a picture processed in order of increasing macroblock address. + +The deblocking filter process is invoked for the luma and chroma components separately. For each macroblock and each component, vertical edges are filtered first, starting with the edge on the left-hand side of the macroblock proceeding through the edges toward the right-hand side of the macroblock in their geometrical order. Then horizontal edges are filtered, starting with the edge on the top of the macroblock proceeding through the edges toward the bottom of the macroblock in their geometrical order. + +Macroblocks of type I\_PCM are treated as Intra macroblocks with $qP_z = 0$ . + +NOTE – This is in accordance with the treatment of such macroblocks in the deblocking filtering process specified in [ITU-T H.264]. + +**Table B.2 – Value of $t_c$ and $\beta$ as a function of index** + +| | | | | | | | | | | | | | | | | | | | | +|---------|------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| index | 0-15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | +| $t_c$ | 0 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | +| $\beta$ | 0 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 20 | 22 | 24 | 26 | 28 | + +To obtain $t_c$ , use index = indexA. To obtain $\beta$ , use index = indexB. + +**Table B.3 (concluded) – Value of $t_c$ and $\beta$ as a function of index** + +| | | | | | | | | | | | | | | | | | | | +|---------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| index | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | +| $t_c$ | 3 | 4 | 4 | 4 | 5 | 5 | 6 | 6 | 7 | 8 | 9 | 9 | 11 | 12 | 13 | 13 | 16 | 18 | +| $\beta$ | 30 | 32 | 34 | 36 | 38 | 40 | 42 | 44 | 46 | 48 | 50 | 52 | 54 | 56 | 58 | 60 | 62 | 64 | + +To obtain $t_c$ , use index = indexA. To obtain $\beta$ , use index = indexB. + +#### B.6.2.2 Filtering process for luma samples + +Filtering of luma samples takes place within units of $8 \times 8$ luma samples. Figure B.2 illustrates how the $8 \times 8$ blocks are organized when filtering both across vertical and horizontal edges. + +![Diagram (a) showing the arrangement of 8x8 blocks when filtering across vertical edges. It consists of four 4x4 blocks labeled A, B, C, and D. Block A is top-left, B is bottom-left, C is top-right, and D is bottom-right. A bold vertical line separates blocks A and B from blocks C and D. Samples p_i_j are shown around the perimeter of block A, and q_i_j are shown around the perimeter of block C.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +Diagram (a) showing the arrangement of 8x8 blocks when filtering across vertical edges. It consists of four 4x4 blocks labeled A, B, C, and D. Block A is top-left, B is bottom-left, C is top-right, and D is bottom-right. A bold vertical line separates blocks A and B from blocks C and D. Samples p\_i\_j are shown around the perimeter of block A, and q\_i\_j are shown around the perimeter of block C. + +a) Filtering across vertical edges + +![Diagram (b) showing the arrangement of 8x8 blocks when filtering across horizontal edges. It consists of four 4x4 blocks labeled A, B, C, and D. Block A is top-left, B is top-right, C is bottom-left, and D is bottom-right. A bold horizontal line separates blocks A and B from blocks C and D. Samples p_i_j are shown around the perimeter of block A, and q_i_j are shown around the perimeter of block C.](ec3647789b5c38fb686f2a0833324e79_img.jpg) + +Diagram (b) showing the arrangement of 8x8 blocks when filtering across horizontal edges. It consists of four 4x4 blocks labeled A, B, C, and D. Block A is top-left, B is top-right, C is bottom-left, and D is bottom-right. A bold horizontal line separates blocks A and B from blocks C and D. Samples p\_i\_j are shown around the perimeter of block A, and q\_i\_j are shown around the perimeter of block C. + +b) Filtering across horizontal edges + +**Figure B.2 – Arrangement of $8 \times 8$ blocks when filtering across vertical or horizontal edges** + +Figure B.2 is interpreted as follows: + +- A, B, C and D are $4 \times 4$ blocks. +- $p_{n_i}$ and $q_{n_i}$ , $n = 0..3$ and $i = 0..7$ are samples within the $8 \times 8$ block. +- The bold line indicates a horizontal or vertical block edge across which deblocking filtering takes place. +- The $8 \times 8$ blocks are arranged such that the samples ( $p_{3_0}$ to $q_{3_0}$ ) or the samples ( $p_{3_7}$ to $q_{3_7}$ ) are at a macroblock boundary. + +The variable $d$ , as specified below, is used for deciding whether the samples within an $8 \times 8$ block are modified or not. Depending on the position of the block edge, the following applies: + +- If the block edge is part of a macroblock edge: + +$$d = | p_{1_2} - p_{0_2} | + | q_{0_2} - 2*q_{1_2} + q_{2_2} | + | p_{1_5} - p_{0_5} | + | q_{0_5} - 2*q_{1_5} + q_{2_5} |$$ +- Otherwise (the block edge is not part of a macroblock edge): + +$$d = | p_{2_2} - 2*p_{1_2} + p_{0_2} | + | q_{0_2} - 2*q_{1_2} + q_{2_2} | + | p_{2_5} - 2*p_{1_5} + p_{0_5} | + | q_{0_5} - 2*q_{1_5} + q_{2_5} |$$ + +A determination is made of whether or not to apply filtering across a block edge as follows: + +- The variable $filterBlockSize$ shall be equal to 1 if one or more of the following conditions are true: + - Block A is intra coded or Block C is intra coded. + - One or more of the blocks A, B, C and D contains non-zero transform coefficients. + - The absolute difference between the horizontal or vertical component of the motion vectors used for block A and block C is greater than or equal to 4 in units of quarter luma frame samples. + - Block A and block C are predicted from different reference frames. + +- Otherwise, the value of filterBlockEdge shall be equal to 0. +- If one or more of the following conditions are true, no filtering across a block edge takes place. + - disable\_deblocking\_filter\_idc for the slice containing block D is equal to 1. + - disable\_deblocking\_filter\_idc for the slice containing block D is equal to 2 and blocks B and D belong to different slices. + - $d \geq \beta$ . + - filterBlockEdge is equal to 0. +- Otherwise, filtering takes place as specified below. + +For block edges across which filtering is to be performed, all values $p_{n,i}$ , $q_{n,i}$ , with $n = 0, 1$ and $i = 0..7$ , are modified as follows. + +- If the block edge is not part of a macroblock edge: + +$$\Delta = \text{Clip3}(-t_c, t_c, ((q0_i + ((p2_i + q1_i) \gg 1)) \gg 1) - ((p0_i + ((q2_i + p1_i) \gg 1)) \gg 1))$$ +- Otherwise (the block edge is part of a macroblock edge): + +$$\Delta = \text{Clip3}(-t_c, t_c, ((q0_i + (q1_i \gg 1)) \gg 1) - ((p0_i + (q2_i \gg 1)) \gg 1))$$ + +When the filtering is applied, the filtered samples $p1_i$ , $p0_i$ , $q0_i$ , $q1_i$ are derived by: + +$$p0_i = \text{Clip1}_Y(p0_i + \Delta)$$ + +$$q0_i = \text{Clip1}_Y(q0_i - \Delta)$$ + +$$p1_i = \text{Clip1}_Y(p1_i + \Delta/2)$$ + +$$q1_i = \text{Clip1}_Y(q1_i - \Delta/2)$$ + +#### B.6.2.3 Filtering process for chroma samples + +The chroma filtering process takes place across an edge between two $4 \times 4$ chroma blocks. Figure B.3 illustrates how two such adjacent blocks are arranged when filtering both across vertical and horizontal edges. + +![Figure B.3 shows two diagrams illustrating the arrangement of two 4x4 chroma blocks (A and B) for filtering. Diagram (a) shows filtering across a vertical edge, where block A is on the left and block B is on the right. Diagram (b) shows filtering across a horizontal edge, where block A is on top and block B is on the bottom. Both diagrams show the pixel indices (p and q) used for filtering.](1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg) + +Figure B.3 consists of two parts, (a) and (b), illustrating the arrangement of two $4 \times 4$ chroma blocks, A and B, for filtering. + +**a) Filtering across a vertical edge** + +Block A is on the left and Block B is on the right. The columns of Block A are labeled $p3_0, p2_0, p1_0, p0_0$ (leftmost to rightmost). The columns of Block B are labeled $q0_0, q1_0, q2_0, q3_0$ (leftmost to rightmost). The rows are labeled $p3_1, p2_1, p1_1, p0_1$ (top to bottom) for both blocks. The vertical edge between them is the boundary between $p0_i$ and $q0_i$ columns. + +**b) Filtering across a horizontal edge** + +Block A is on top and Block B is on the bottom. The rows of Block A are labeled $p3_0, p3_1, p3_2, p3_3$ (top to bottom). The rows of Block B are labeled $q0_0, q1_0, q2_0, q3_0$ (top to bottom). The columns are labeled $p2_0, p2_1, p2_2, p2_3$ (leftmost to rightmost) for both blocks. The horizontal edge between them is the boundary between $p3_i$ and $q0_i$ rows. + +Figure B.3 shows two diagrams illustrating the arrangement of two 4x4 chroma blocks (A and B) for filtering. Diagram (a) shows filtering across a vertical edge, where block A is on the left and block B is on the right. Diagram (b) shows filtering across a horizontal edge, where block A is on top and block B is on the bottom. Both diagrams show the pixel indices (p and q) used for filtering. + +**Figure B.3 – Arrangement of two $4 \times 4$ chroma blocks when filtering across a vertical or horizontal edge** + +Figure B.3 is interpreted as follows: + +- A and B are $4 \times 4$ blocks of samples. +- $p_{n_i}$ and $q_{n_i}$ , $n = 0..3$ and $i = 0..3$ are samples within the two $4 \times 4$ blocks. +- The bold line indicates a horizontal or vertical block edge across which deblocking filtering takes place. + +A determination is made of whether or not to apply filtering across the edge between blocks A and B as follows: + +- If one or more of the following conditions are true, no filtering across the block edge takes place. + - disable\_deblocking\_filter\_idc for the slice containing block B is equal to 1. + - disable\_deblocking\_filter\_idc for the slice containing block B is equal to 2 and blocks A and B belong to different slices. + - Neither block A nor block B is coded using an intra prediction mode. +- Otherwise, filtering takes place for the block edge. + +For block edges where filtering takes place, all values $p_{0_i}$ , $q_{0_i}$ with $i = 0..3$ are modified in the following way: + +$$\Delta = \text{Clip3}(-t_c, t_c, (((q_{0_i} - p_{0_i}) \ll 2) + p_{1_i} - q_{1_i} + 4) \gg 3))$$ + +The filtered result samples $p_{0_i}$ , $q_{0_i}$ are derived by: + +$$p_{0_i} = \text{Clip1c}(p_{0_i} + \Delta)$$ + +$$q_{0_i} = \text{Clip1c}(q_{0_i} - \Delta)$$ + +# Appendix I + +## ASN.1 OIDs defined in this Recommendation + +(This appendix does not form an integral part of this Recommendation.) + +| OID | Clause reference | +|----------------------------------------------------------------------------------------------------------------------------------|------------------| +| {itu-t(0) recommendation(0) h(8) h241(241) specificVideoCodecCapabilities(0) h264(0) set-submode(2)} | 6.2.5.1 | +| {itu-t(0) recommendation(0) h(8) h241(241) specificVideoCodecCapabilities(0) h264(0) set-SVCmode (3)} | 6.2.6.1 | +| {itu-t(0) recommendation(0) h(8) h241(241) specificVideoCodecCapabilities(0) h264(0) iPacketization(0) h241AnnexA(0)} | 7.1.4 | +| {itu-t(0) recommendation(0) h(8) h241(241) specificVideoCodecCapabilities(0) h264(0) iPacketization(0) rfc6184NonInterleaved(1)} | 7.1.4 | +| {itu-t(0) recommendation(0) h(8) h241(241) specificVideoCodecCapabilities(0) h264(0) iPacketization(0) rfc6184Interleaved(2)} | 7.1.4 | +| {itu-t(0) recommendation(0) h(8) h241(241) specificVideoCodecCapabilities(0) h264(0) generic-capabilities(1)} | 8.3.2.1 | + +# Appendix II + +## Examples of the set submode procedure + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides informative guidance and examples illustrating the use of the set submode procedure defined in clause 6.2.5. + +The ITU-T H.264 capabilities defined by clause 8.3 usually allow more than one set of encoding parameters to be used by the video source. + +For instance, the capabilities specify the ability to receive a maximum picture size of CustomMaxFS macroblocks. The video source may choose to send any picture height and width combination that does not exceed that total. Although the receiver is required by this Recommendation to be capable of rendering these picture sizes, it is frequently desirable to negotiate further constraints on the picture size. For example, an MCU that can control the picture height and width sent from each terminal can create a more functional picture composition. + +There are four common cases where constraining the encoding with the set submode procedure is useful: + +- to optimize the picture aspect ratio for a specific display or a sub-picture in a composition +- to limit the picture frame rate to match the frame rate of a specific picture composition +- to eliminate the adverse effects of rescaling on the picture quality +- to improve bandwidth utilization by negotiating a picture size that does not exceed the limits of a display or the size of a sub-picture in a composition. + +The use of the set submode procedure is illustrated for each of these cases by the following clauses. + +## II.1 Optimization of the picture aspect ratio + +In this example, the video channel is constrained to carry a picture which has a specific picture aspect ratio. The sample aspect ratio and the picture size are not constrained. + +The video source indicates which SAR and PAR combinations can be carried on this video channel in a setSubmodeIndication message. + +The video receiver requests a specific PAR which is included in that indication by sending a setSubmodeRequest. + +The video source selects an image height and SAR that it can send using the requested PAR. + +The video source positively acknowledges the request, including the SAR, PAR and the image height by sending a setSubmodeResponse. It then switches to the new submode, sending the SAR in the ITU-T H.264 VUI message per Table E.1 of [ITU-T H.264]. + +- setSubmodeIndication: channelID, list of (SAR, list of (PAR), [allowAnyHeight]) +- ← setSubmodeRequest: channelID, PAR +- setSubmodeResponse: channelID, acknowledge, SAR, PAR, height + +## II.2 Limiting the picture frame rate + +The setSubmode procedure does not allow the picture frame rate to be directly constrained. However, it does allow macroblocks per second (submodeMaxMBPS) to be limited. Therefore, in order to limit frame rate, the video stream must be constrained to carry a picture of a specific size and also limited to a maximum macroblocks-per-second rate. This results in a constrained picture frame rate. + +First, the video source indicates which SAR and PAR combinations can be carried on this video channel by sending a setSubmodeIndication. + +The video receiver then requests a specific height, and a submodeMaxMBPS value that achieves the desired frame rate for the requested picture size by sending a setSubmodeRequest. It may also request any specific SAR and PAR combination that is included in the indication message. + +The video source positively acknowledges the request by sending a setSubmodeResponse that includes the SAR, PAR and the image height. It then switches to the new submode, sending the SAR in the ITU-T H.264 VUI message per Table E.1 of [ITU-T H.264]. + +- setSubmodeIndication: channelID, list of (SAR, list of (PAR), [allowAnyHeight]) +- ← setSubmodeRequest: channelID, SAR, PAR, height, submodeMaxMBPS +- setSubmodeResponse: channelID, acknowledge, SAR, PAR, height + +## II.3 Eliminating the adverse effects of picture rescaling + +In order to eliminate the adverse effects of scaling, the video channel is constrained to carry a picture of specific PAR, SAR and picture size. Three different examples are presented. The first example describes the case where the video source is capable of re-scaling its image to any requested size. The second and third examples describe cases where the video source does not have this capability. + +### II.3.1 Video source is capable of arbitrary scaling + +The video source first indicates which SAR and PAR combinations can be carried on this video channel by sending a setSubmodeIndication. + +The video receiver sends a setSubmodeRequest to request a specific SAR and PAR combination which is included in the indication. Since the selected SAR and PAR include the allowAnyHeight designation, the video receiver also requests a specific height. + +The video source positively acknowledges the request by sending a setSubmodeResponse that includes the SAR, PAR and the image height. It then switches to the new submode, sending the SAR in the ITU-T H.264 VUI message per Table E.1 of [ITU-T H.264]. + +- setSubmodeIndication: channelID, list of (SAR, list of (PAR), [allowAnyHeight]) +- ← setSubmodeRequest: channelID, SAR, PAR, height (SAR and PAR have allowAnyHeight set) +- setSubmodeResponse: channelID, acknowledge, SAR, PAR, height + +### II.3.2 Video source is not capable of arbitrary scaling + +The video source first indicates which SAR and PAR combinations can be carried on this video channel by sending a setSubmodeIndication. + +The video receiver requests a specific PAR and SAR combination which is included in the indication by sending a setSubmodeRequest. Since the selected PAR and SAR does not include the allowAnyHeight designation, the video receiver offers a list of acceptable heights, in preference order. + +The video source selects the first height on the list that it is capable of sending. + +The video source then positively acknowledges the request, including the PAR, SAR and the image height in its `setSubmodeResponse`. It then switches to the new submode, sending the SAR in the ITU-T H.264 VUI message per Table E.1 of [ITU-T H.264]. + +- `setSubmodeIndication`: `channelID`, list of (SAR, list of (PAR)) +- ← `setSubmodeRequest`: `channelID`, SAR, PAR, list of (height) +- `setSubmodeResponse`: `channelID`, acknowledge, SAR, PAR, height + +However, if the video source does not find a height in the request that it is capable of sending, it responds with a rejection in its `setSubmodeResponse`, which includes the list of heights it can send with the requested SAR and PAR combination. + +The video receiver then selects one of those specific heights and sends a new `setSubmodeRequest`. + +The video source then positively acknowledges the request, including the PAR, SAR and the image height in its `setSubmodeResponse`. It then switches to the new submode, sending the SAR in the ITU-T H.264 VUI message per Table E.1 of [ITU-T H.264]. + +- `setSubmodeIndication`: `channelID`, list of (SAR, list of (PAR)) +- ← `setSubmodeRequest`: `channelID`, SAR, PAR, list of (height) +- `setSubmodeResponse`: `channelID`, reject, list of (height) (requested heights were not supported) +- ← `setSubmodeRequest`: `channelID`, SAR, PAR, height +- `setSubmodeResponse`: `channelID`, acknowledge, PAR, SAR, height + +## II.4 Improving bandwidth utilization by limiting maximum picture size + +Reducing the picture size frequently improves the picture quality by reducing compression artefacts. It can also reduce the bandwidth required to send the picture. In this case, it is often useful to further constrain the video channel through the use of flow control. + +The video source sends a `setSubmodeIndication` which indicates which PAR and SAR combinations can be carried on this video channel. + +The video receiver then sends a `setSubmodeRequest` message choosing a specific PAR and SAR combination which is included in the indication, and also the maximum image height. + +The video source selects an image height that it is capable of sending that is less than or equal to the maximum. + +The video source then positively acknowledges the request, including the PAR, SAR and the image height in its `setSubmodeResponse` message. The image height is less than the requested maximum height. It then switches to the new submode, sending the SAR in the ITU-T H.264 VUI message per Table E.1 of [ITU-T H.264]. + +- `setSubmodeIndication`: `channelID`, list of (SAR, list of (PAR)) +- ← `setSubmodeRequest`: `channelID`, [SAR], [PAR], `maximumHeight` +- `setSubmodeResponse`: `channelID`, acknowledge, SAR, PAR, height + +If the smallest height that the video source can send exceeds the maximum height requested, the video source rejects the request, including the smallest height it can send in the reject message. + +The video receiver then sends a new `setSubmodeRequest` with a new maximum height that can be accommodated by the video source. + +The video source then positively acknowledges the second request, including the PAR, SAR and the image height in its `setSubmodeResponse`. It then switches to the new submode, sending the SAR in the ITU-T H.264 VUI message per Table E.1 of [ITU-T H.264]. + +Finally, the video receiver constrains the channel bandwidth using the ITU-T H.245 flowControlCommand + +- setSubmodeIndication: channelID, list of (SAR, list of (PAR)) +- ← setSubmodeRequest channelID, [SAR], [PAR], maximumHeight +- setSubmodeResponse: channelID, reject, minimumHeight (requested height was too large) +- ← setSubmodeRequest: channelID, [SAR], [PAR], maximumHeight +- setSubmodeResponse: channelID, acknowledge, SAR, PAR, height +- ← flowControlCommand: channelID, maximumBitRate + + + +# Bibliography + +[b-IETF RFC 4648] IETF RFC 4648 (2006), *The Base16, Base32, and Base64 Data Encodings*. + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/10b0dda884baae493ad958422d11b552_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/10b0dda884baae493ad958422d11b552_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaf9953922d5a635255bcdf14024752c85fef47a --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/10b0dda884baae493ad958422d11b552_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d61379553b2ceece908711eef9addf4018e64719158115c70f897042af8453f +size 46692 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7434b00f6be3b534d98741eb2236003404020b39 --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b31361e7711fd5b7ffc39f1bb039122aa02fb33fe6e4c0f0de4cbfa73521ef92 +size 39021 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e9477d3ebeb9391bae245cb8d9438df1f8e16db --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0c7f77dd00c900cba7ad0063cc6ef837da886debbb363497c6573316dcb0c97 +size 33435 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e07f4b11180f33f1201513ba0d2e2a16752f398d --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7da5e60706ad8a04b0418a4b17a845797f91fa55e3cb88c447c5e2b02635b20 +size 55266 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/30fe9e9487585118063341332e802e98_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/30fe9e9487585118063341332e802e98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8be65ffa3530a58e419db488147aaa7744f9197f --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/30fe9e9487585118063341332e802e98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:678290ce93ca371efed2775eed7d5d53c2235755f93300d1c515aab257161920 +size 31762 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..488c803b07464ac5705f196f94983b8d1eb1e202 --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8a2fa596a5b353be664586f232e75f63ebd2b0b208e1085c58a214a7d253a44 +size 31480 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40d2c4aced91b7ae879771245ebf45540afa85ad --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49e573dc56f7111513c06e7342de1ea15be591f91cb6b806738bbbd23f37a1f1 +size 169566 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d578996720fd72d0131efa716da39a61ee4e23f7 --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95aa358d6a3a47f53e11cd79f4a3dc4e4d75c64990eab7f1554f4219b04b87dd +size 137618 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9babbfab2164b2d463a46bd94a3f881011d87a6 --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5932ad2243dd42dc643f3a4e040069a769272cb405028fcab157d9cb24829fb6 +size 57560 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f12e872a3a78fe4ab368e9a78689fdb9e9fc338 --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e59313f20c32bdf70fb0d45a08985677be56ec3e7dbb3a64227a9426c5ed659d +size 208213 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbf8c0386d28b0f7006d5ef97f0449e4118ba139 --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80568a9d0f45cb4c18f57814d9fa5a0388d0889264636409d4b81bd5569f0ebd +size 167351 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5970643f9799fed21a8e2cdb08b2d87cd7c5509 --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5ee43f4506c2e292aaae72a7877bde04d574e609427c699c67b9046248ecb76 +size 37229 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85e4dd94d21109025e90a8905d5a8722945c041f --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00a4045eb66f733ddc765159c4a700b192403d900d0cabcb02796148d83dd13d +size 34063 diff --git a/marked/H/T-REC-H.242-200903-I_PDF-E/e42cc691d9c7c4d23e66b04472bb494e_img.jpg b/marked/H/T-REC-H.242-200903-I_PDF-E/e42cc691d9c7c4d23e66b04472bb494e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..422e45d32a8e324cdc2216ac0d99bdc6528f8c9b --- /dev/null +++ b/marked/H/T-REC-H.242-200903-I_PDF-E/e42cc691d9c7c4d23e66b04472bb494e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f979e0b69f800219b3e9efb84e812961c70d0c70615b13fbcfe7006cc61340cc +size 20841 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0117f4ab81a95b625e7610d6b67af7fe7b19f3a0 --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aec02602a063a2e4078b08ccd8ce3314be92f0de481374c2ad71ce6b4463871d +size 93251 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ae9a090bc50643fe1ed50d32c36eac50b037f0d --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:836e63fb2ebf9ef2ed10f0ef430abaf50e506751b9a563f93e3d25eeaa7a61a6 +size 8184 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f52768dae0c171abb06dfc9964506b2d9c50b92 --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42db39d4abaceb9d3befe88d35ae483680a15cc09499f5f4c3a3556624e1b887 +size 209396 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f47efc16d95ecb532b236e6dbf1d5ad119f8c8d9 --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c33fbe64c16c40d06f65050c617f9771376cfa7e1e237444807e0784562fce7 +size 20962 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b66510686bf982dcd3bd43f8afb0827e690783d1 --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fd67b9662eb6010db2c77d3a40ed9211977ddc1c969c39fb5a6a4e3ca0b220c +size 36010 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/731f533b0599c8e42a063f06e4332045_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/731f533b0599c8e42a063f06e4332045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5dbb6127b96b54be7e7b34e0189077f8cc85d5c --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/731f533b0599c8e42a063f06e4332045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c49b5aee58d90592034c0ec32a1e5068dc996238ea9890680cb771f61967b6df +size 17178 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b79651c3bca4123e623db554032a5b1f3850f7f --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:172c7825673c046e526ff2ec5db866b2647d76c72d9803e6d4dbbccf6d5a4bb0 +size 16510 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0e93bfc67e493cae25d47cf808919dcac87e5ee --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afce303d4f8ad1c6354d5770c1ce34be2186e70ec57e49bd72759701a6552056 +size 30542 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8429a0d3841b6e24d0f11e1aad745cc9009bfbb7 --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5752c58526bb580407f6cab25e06e0756a133f80bb77c26f88572359761fe71b +size 28337 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7b1aa0948e68ad536c9dc3b4b03586ff5116d1e --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d85f0ac55f66cae9182ef6aea0379c3fed098d6cf77abae3bddba54a3d3b6cd +size 31517 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed4b5890c9d7eecb24f451902e43659209acab05 --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c809451721eb5d6160c76436b04fb70efb7722f7678dc811b359b19b72bb702c +size 29929 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.244-199507-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e917eb2b4d8dabd287a5b79b5d755fa48fe3f54 --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:814a59b0329ff7d02423b7bf4e237d663611b9ce59ac76a8562d1ad789155873 +size 29463 diff --git a/marked/H/T-REC-H.244-199507-I_PDF-E/raw.md b/marked/H/T-REC-H.244-199507-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5ba4d1af91ae3e35c73f61e098acb1a2b0adb879 --- /dev/null +++ b/marked/H/T-REC-H.244-199507-I_PDF-E/raw.md @@ -0,0 +1,933 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**H.244** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/95) + +**TRANSMISSION OF NON-TELEPHONE SIGNALS** + +--- + +**SYNCHRONIZED AGGREGATION OF +MULTIPLE 64 OR 56 kbit/s CHANNELS** + +**ITU-T Recommendation H.244** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation H.244 was prepared by ITU-T Study Group 15 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 10th of July 1995. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | | Page | +|-------|----------------------------------------------------------------------------------------|-------------| +| 1 | Scope..... | 1 | +| 2 | Normative references ..... | 1 | +| 3 | Definitions and symbols..... | 1 | +| 3.1 | Definitions ..... | 1 | +| 3.2 | Symbols ..... | 2 | +| 4 | Abbreviations ..... | 3 | +| 5 | General ..... | 4 | +| 5.1 | Application of this Recommendation ..... | 4 | +| 5.1.1 | Intercommunication of Audiovisual equipments ..... | 4 | +| 5.1.2 | Intercommunication of non-audiovisual equipments – Case D ..... | 5 | +| 5.2 | Definition of the Modes of transmission on the MC side ..... | 5 | +| 5.3 | General description of the aggregation process ..... | 8 | +| 5.4 | CAU functionality ..... | 9 | +| 6 | Choice of H.244 or ISO aggregation..... | 10 | +| 7 | H.244 aggregation procedure ..... | 12 | +| 7.1 | Call control ..... | 12 | +| 7.1.1 | Initial channel..... | 12 | +| 7.1.2 | Additional channels ..... | 12 | +| 7.2 | Channel synchronisation..... | 12 | +| 7.3 | In-band procedure using H.221 BAS codes ..... | 12 | +| 7.3.1 | Control of transfer rate ..... | 13 | +| 7.3.2 | Determination of the transfer-rate capabilities to be transmitted on the MC side..... | 13 | +| 7.3.3 | Determination of the transfer-rate capabilities to be transmitted on the SC side ..... | 13 | +| 7.3.4 | Capability sets transmitted from a CAU ..... | 13 | +| 7.3.5 | Notification of change of N a ..... | 15 | +| 7.3.6 | Commands transmitted from a CAU..... | 15 | +| 7.4 | Transmission of user information by a CAU ..... | 16 | +| 8 | Initialisation, Mode/Rate changing and Fault recovery ..... | 16 | +| 8.1 | Initialisation ..... | 16 | +| 8.1.1 | Single-channel Side ..... | 17 | +| 8.1.2 | Multi-channel Side, initial channel ..... | 17 | +| 8.1.3 | Multi-channel Side, additional channels ..... | 17 | +| 8.2 | Change of transmission rate during a session ..... | 18 | +| 8.3 | Recovery from fault conditions ..... | 18 | +| 8.4 | Further mode changes ..... | 18 | +| 9 | ISO aggregation procedure ..... | 18 | +| | Appendix I – Examples of procedures ..... | 19 | +| | Appendix II – Example of SDL diagram for TAC initialisation ..... | 23 | +| | Appendix III – Comments on the modification of capsets and commands ..... | 24 | + + + +# SYNCHRONIZED AGGREGATION OF MULTIPLE 64 OR 56 kbit/s CHANNELS + +(Geneva, 1995) + +# 1 Scope + +This Recommendation provides for synchronisation and aggregation of multiple channels of 64 kbit/s or 56 kbit/s, each being with or without octet integrity and relative transmission delay in the range $\pm 1$ second. It is applicable to a wide range of user data transport up to 63 channels using ISO/IEC standard 13871, but special provision is made for audiovisual systems according to Recommendation H.221 [1], up to 24 channels; the aggregation may be network-based or associated with Customer-Premises Equipment. The available operating modes (B1, B2, B3, H2) provide options with/without transmission-management overhead and user-data rates at/less-than the exact multiples of 64/56 kbit/s. + +The number of aggregated channels may be varied dynamically during a session. Procedures are given for dealing with faults, including loss of channels and slip. + +Call control is not covered in this Recommendation. + +# 2 Normative references + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU Recommendation H.221 (1993), *Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices*. +- [2] ITU Recommendation H.242 (1993), *System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s*. +- [3] ITU Recommendation H.320 (1993), *Narrow-band visual telephone systems and terminal equipment*. +- [4] ISO/IEC CD 13871, *Digital Channel Aggregation*. +- [5] ITU Recommendation H.230 (1995), *Frame-synchronous control and indication signals for audiovisual systems*. + +# 3 Definitions and symbols + +## 3.1 Definitions + +For the purposes of this Recommendation, the following definitions apply: + +- 3.1.1 **H.244 aggregation:** Channel aggregation by the process described in clauses 7 and 8. +- 3.1.2 **ISO aggregation:** Channel aggregation by the process described in [4]. +- 3.1.3 **single channel equipment (SCE):** A terminal or other unit (such as a LAN interface) having an interface for a single bidirectional digital connection. +- 3.1.4 **multiple channel equipment (MCE):** A terminal or other unit (such as a LAN interface) having interface(s) for multiple bidirectional digital connections at 64 kbit/s each. + +- 3.1.5 channel aggregation unit (CAU):** A device having both multiple 64 kbit/s accesses and a single access at a higher bit rate. Reference in this Recommendation to ‐CAU‑ or ‐aggregator‑ shall mean equipment conforming to this Recommendation. +- 3.1.6 H.221 frame structure, H.221 framing:** Frame structure according to Recommendation H.221, as set out in [1]. +- 3.1.7 Capset:** Abbreviation for ‐Capability set‑ – see [2]. +- 3.1.8 user information:** The application data streams passing (in both directions) between CAU and SCE. (See Note 1.) +- 3.1.9 calling end:** The CAU or MCE which requests the first 64/56-channel connection of the whole session, resulting in the establishment of the ‐initial channel‑. If during fault-recovery procedures the initial channel is transferred to another connection, this does not affect the definition. (See Note 2.) +- 3.1.10 called end:** The CAU or MCE which accepts the first 64/56-channel connection request of the whole session, resulting in the establishment of the ‐initial channel‑. If during fault-recovery procedures the initial channel is transferred to another connection, this does not affect the definition. (See Note 2.) +- 3.1.11 TAC case:** In-band communication between SCE and CAU takes place using H.221 BAS codes – see clauses 7-8. +- 3.1.12 NoTAC case:** No in-band management communication between SCE and CAU takes place – the single channel is only a clear path for the data which will be wholly transmitted to the remote party; any communication between the terminal and the CAU is by means not specified in this Recommendation. +- 3.1.13 modes B1, B2, B3:** Modes of aggregation by the method of [4] – see 5.2. +- 3.1.14 mode H2:** Modes of aggregation by the method of clauses 7-8. +- 3.1.15 redundant command:** A BAS command which repeats, unchanged, a previously transmitted mode value which is still in force. +- 3.1.16 compatibility bits:** Bit 8 of the first sixteen octets in every time-slot of a single channel except Time-slot 1. +- 3.1.17 external setting:** This term is used to express operations outside the scope of this Recommendation which determine the behaviour of a CAU as to choice of option or timing of its action. + +### NOTES + +- 1 In the audiovisual cases, the application data stream includes the H.221 frame structure. +- 2 The significance of ‐calling‑ and ‐called‑ end-points is mentioned in 8.1.3. + +## 3.2 Symbols + +NOTE – For readability, the capability and command values listed in References [1] and [5] are referred to in this Recommendation by their names rather than codepoint byte values; the use of {*name*} for capabilities and [*name*] for commands serves to distinguish between these. + +- N** An integer, applied to 64/56-channels to define a parallel (un-aggregated) bitstream of rate $N \times 64$ kbit/s. +- n** An integer, applied to 64 kbit/s to define a serial (or otherwise aggregated) bitstream of rate $n * 64$ kbit/s. +- $N_a$** The number of active 64/56-channels between CAU and MCE or between two CAUs. +- $N_m$** The maximum number of 64/56-channels which can be accepted by a CAU transmitting the value $\{N_m \times B\}$ . +- $N'_m$** Used to denote the incoming value of $N_m$ from the remote CAU, or equivalent from an MCE. + +| | | +|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $N_d$ | The number of connections requested by the calling end, the lower of $N_m$ and $N_m^2$ . | +| $\{N \times 64k\}$ | Capabilities in the series {1B}, {2B}, {3B}.... corresponding to $N = 1, 2, 3 \dots$ (applies to Mode H2 only). | +| $\{n*64k\}$ | Capabilities in the series {64k}, {128k}, {192k}.... corresponding to $n = 1, 2, 3 \dots$ | +| $n_m$ | Such that $\{n_m*64k\}$ is the highest transfer-rate capability incoming from the SCE for which the continuous series of rate capabilities $\{(n_m - 1)*64k\}, \{(n_m - 2)*64k\}, \dots, \{2*64k\}$ is also present in the capset. | +| $[N \times 64]$ | Multiple-channel commands defined in [1]. | +| $[n*64k]$ | Single-channel commands defined in [1]. | +| [capex] | Command issued by a CAU (see 7.3.6.3) to an SCE to stimulate a capability exchange. | +| [AggIN]* | A double SBE symbol indicating the number n as determined by the process of 7.3.4.2; see the procedure described in clause 8 – see [5]. | +| {null} | Capability having no significance other than as a filler; only ever transmitted by a CAU, and therefore it identifies the capset as having last come from, or been forwarded by, a CAU; SCE must ignore any number of these in an incoming capset – see [1]. | +| {SM-comp} | Capability to transmit and receive user information without using any compatibility bits, setting these to 1 – see [1]. | +| [SM-comp] | User information is not contained in the compatibility bits (and shall not be sent in the compatibility bits in the reverse direction either) – see [1]. | +| S | Audible signal (to be defined), which would be recognised by a human user as a call progress tone (he would not hang up). | + +# 4 Abbreviations + +For the purposes of the Recommendation, the following abbreviations are used: + +| | | +|----------------------------|--------------------------------------| +| BAS | Bit-rate Allocation Signal – see [1] | +| CAU | Channel Aggregation Unit | +| FAS | Frame Alignment Signal – see [1] | +| H.221 | See 3.1 | +| MC (side) | Multiple Channel (side, of a CAU) | +| MCE | Multiple-Channel Equipment | +| NCA, NIA, NIC,
NID, NIS | See [5] | +| NoTAC | No Terminal-Aggregator Communication | +| SC (side) | Single Channel (side, of a CAU) | +| SCE | Single-Channel Equipment | +| SM-comp | Single-Multiple compatibility | +| TAC | Terminal-Aggregator Communication | +| UD | Unspecified Data | + +# 5 General + +## 5.1 Application of this Recommendation + +On the single-channel connections, which may be very short if the terminal and CAU are colocated, or much longer if a telecommunications link is involved, two options are provided for in this Recommendation: + +- no in-band management communication on the single channel, this being only a clear path for the data which will be wholly transmitted to the remote party; any communication between the terminal and the CAU is by means not specified in this Recommendation; this is referred to as the “NoTAC” case – No Terminal-Aggregator Communication and applies when “ISO aggregation” is used (see [4]); +- in-band communication as specified in this Recommendation, using the BAS codes defined in [1] and the procedures of [2]; this is referred to as the “TAC” case – Terminal-Aggregator Communication, and applies when “H.244 aggregation” is used (see clauses 7 and 8). + +### 5.1.1 Intercommunication of Audiovisual equipments + +For audiovisual terminals conforming to [1] and [2], this Recommendation provides for synchronisation and aggregation of up to 24 channels of 64 kbit/s or 56 kbit/s, each being with or without octet integrity and relative transmission delay in the range $\pm 1$ second. + +Provision is made for the following intercommunication Cases A-C. + +#### 5.1.1.1 Case A + +For interconnection of a single-channel (SCE) and a multiple-channel audiovisual end-point (MCE), both conforming to [1] and [2], only H.244 aggregation is permissible (see Figure 1); this involves only one CAU, which may be within the network or close to the single-channel end-point. + +![Diagram of Case A interconnection showing SCE connected to CAU via TAC, CAU connected to Switched digital network, and Switched digital network connected to MCE.](731f533b0599c8e42a063f06e4332045_img.jpg) + +The diagram illustrates the interconnection for Case A. On the left, a circle labeled 'SCE' is connected to a rectangle labeled 'CAU' by a double-headed arrow labeled 'TAC'. The 'CAU' is connected to an oval labeled 'Switched digital network' by four parallel horizontal lines. The 'Switched digital network' is connected to a hexagon-like shape labeled 'MCE' by four parallel horizontal lines. Below the 'MCE' is the technical reference text 'T1514940-94/d01'. + +Diagram of Case A interconnection showing SCE connected to CAU via TAC, CAU connected to Switched digital network, and Switched digital network connected to MCE. + +**FIGURE 1/H.244** + +#### 5.1.1.2 Case B + +This case provides for interconnection between two single-channel audiovisual end-points which see the aggregated link purely as a clear data channel; each has a CAU associated with it, but there is no in-band control communication between the end-point and its associated CAU (see Figure 2); this is the NoTAC approach. The system is exactly the same as for unspecified data applications (see 5.1.2); the CAU-ISDN-CAU combination provides a clear channel at one of the transfer rates specified in [1], and therefore shall use ISO aggregation, Mode B1 or B3 (see 5.2). + +![](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +graph LR + subgraph Left + SCE1((SCE)) -- "(NoTAC)" --- CAU1[CAU] + end + CAU1 === SDN((Switched +digital +network)) + SDN === CAU2[CAU] + subgraph Right + CAU2 --- SCE2((SCE)) + SCE2 -- "(NoTAC)" --- CAU2 + end + + %% Optional external communication lines + SCE1 -.-> Ext1[ ] + Ext1 -.-> SCE1 + SCE2 -.-> Ext2[ ] + Ext2 -.-> SCE2 + +``` + +Optional external communication + +T1514950-94/d02 + +FIGURE 2/H.244 + +#### 5.1.1.3 Case C + +This provides for interconnection of two single-channel end-points both conforming to [1] and [2] and capable of the H.244 aggregation operation described in clauses 7-8 (see Figure 3); this involves two CAUs, which may be within the network or close to the single-channel end-points. + +NOTE – It is not possible to use TAC at one end and NoTAC at the other – see clause 6. + +![](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +``` + +graph LR + SCE1((SCE)) <--> TAC1[TAC] <--> CAU1[CAU] + CAU1 === SDN((Switched +digital +network)) + SDN === CAU2[CAU] + CAU2 <--> TAC2[TAC] <--> SCE2((SCE)) + +``` + +T1514960-94/d03 + +FIGURE 3/H.244 + +### 5.1.2 Intercommunication of non-audiovisual equipments – Case D + +This Recommendation provides for synchronisation and aggregation of up to 63 channels of 64 kbit/s or 56 kbit/s, each being with or without octet integrity and relative transmission delay in the range $\pm 1$ second. It is applicable to a wide range of user information transport, including LAN-LAN interconnect, private circuit back-up, and other “unspecified data” applications. No in-band control communication takes place on the single-channel side. The equipments see the aggregated link purely as a clear data channel, and the structure or content of the data streams is of no concern to the aggregating equipment. + +ISO aggregation is appropriate (see Figure 2); the CAU-ISDN-CAU combination provides a clear channel at one of the transfer rates specified in [4] using Mode B1, B2 or B3 (see 5.2). + +## 5.2 Definition of the Modes of transmission on the MC side + +The four modes of transmission are defined below, the accompanying figures being given by way of example for the case of about 192 kbit/s on the SC side. + +**Mode B1** – The user information occupies an integral number of 64/56k channels (usually the N available and aligned channels); only unframed signals are transmitted (see Figure 4), alignment of the channels has previously been achieved using a framed mode, and it is assumed that no slip or other network fault has occurred since then. There are no management bits multiplexed into the stream on either MC or SC sides, and the total bit rates are equal; the Mode is therefore confined to NoTAC cases, and rate change is not possible. + +![Diagram of H.244 Figure 4 showing a CAU connected to a 192 kbit/s channel and three 64 kbit/s channels. The 192 kbit/s channel is divided into three equal parts. The three 64 kbit/s channels are also divided into three equal parts. The text 'T1514970-94/d04' is present below the right side.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates a CAU (Communication Authority Unit) connected to two sets of channels. On the left, a single large gray rectangle represents a 192 kbit/s channel, divided into three equal vertical sections. On the right, three separate gray rectangles represent three 64 kbit/s channels, each also divided into three equal vertical sections. The CAU is shown as a box with three lines connecting to the right side of the three 64 kbit/s channels. The text 'T1514970-94/d04' is located at the bottom right of the diagram. + +Diagram of H.244 Figure 4 showing a CAU connected to a 192 kbit/s channel and three 64 kbit/s channels. The 192 kbit/s channel is divided into three equal parts. The three 64 kbit/s channels are also divided into three equal parts. The text 'T1514970-94/d04' is present below the right side. + +FIGURE 4/H.244 + +Audiovisual signals according to [1] can be transmitted, but the H.221 framing plays no part in the aggregation process, and will appear at a random position within one of the B-channels as shown in black in Figure 5. + +![Diagram of H.244 Figure 5 showing a CAU connected to a 192 kbit/s channel and three 64 kbit/s channels. The 192 kbit/s channel has a small black rectangle in its first section. The three 64 kbit/s channels have small black rectangles in their second sections. The text 'T1514980-94/d05' is present below the right side.](e6df2733626a85205c1db682e6259c46_img.jpg) + +This diagram is similar to Figure 4 but shows the placement of audiovisual signals. On the left, the 192 kbit/s channel has a small black rectangle in its first section. On the right, the three 64 kbit/s channels have small black rectangles in their second sections. The CAU and channel divisions are the same as in Figure 4. The text 'T1514980-94/d05' is located at the bottom right of the diagram. + +Diagram of H.244 Figure 5 showing a CAU connected to a 192 kbit/s channel and three 64 kbit/s channels. The 192 kbit/s channel has a small black rectangle in its first section. The three 64 kbit/s channels have small black rectangles in their second sections. The text 'T1514980-94/d05' is present below the right side. + +FIGURE 5/H.244 + +**Mode B2** – Signals are transmitted with framing according to [4] (depicted as white in Figure 6), the user information rate being about 1.5% less than an integral multiple of 64/56 kbit/s due to the overhead of the frame structure. There is no provision for management bits on the SC side, so the use of this Mode is confined to the NoTAC case. + +![Diagram of Mode B3 showing a CAU connected to three channels. The total rate is (192-3x) kbit/s, with each channel carrying (64-x) kbit/s. Reference T1517240-94/d06.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +The diagram illustrates Mode B3. On the left, a box labeled 'CAU' has three output lines. Below it, a large grey rectangle contains a white box with the text '(192-3x) kbit/s'. To the right, a grid represents three channels. Each channel has a white header section at the top and a grey data section at the bottom. The data sections are labeled '(64-x) kbit/s'. Below the grid is the reference 'T1517240-94/d06'. + +Diagram of Mode B3 showing a CAU connected to three channels. The total rate is (192-3x) kbit/s, with each channel carrying (64-x) kbit/s. Reference T1517240-94/d06. + +FIGURE 6/H.244 + +**Mode B3** – Signals are transmitted with framing in all N channels according to [4], the user information rate being an integral multiple (such as $N - 1$ ) of 64/56 kbit/s; thus there is a management overhead of about 1.5% and generally some unused capacity, as illustrated in Figure 7. The exact bit positions occupied by user information are defined in [4]. + +![Diagram of Mode H2 showing a CAU connected to four channels. The first three carry (64-x) kbit/s each, and the fourth is unused capacity. Total rate is 192 kbit/s. Reference T1517250-94/d07.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates Mode H2. On the left, a box labeled 'CAU' has four output lines. Below it, a large grey rectangle is divided into three equal vertical sections, with a white box at the bottom labeled '192 kbit/s'. To the right, a grid represents four channels. The first three channels have a white header section and a grey data section labeled '(64-x) kbit/s'. The fourth channel is a solid black rectangle labeled 'Unused capacity'. Above the fourth channel is a white box labeled '(3x) kbit/s'. Below the grid is the reference 'T1517250-94/d07'. + +Diagram of Mode H2 showing a CAU connected to four channels. The first three carry (64-x) kbit/s each, and the fourth is unused capacity. Total rate is 192 kbit/s. Reference T1517250-94/d07. + +FIGURE 7/H.244 + +**Mode H2** – Only H.221-framed signals are transmitted (framing is shown as white in Figure 8), the user information rate being an integral number of 64/56k channels (usually the N available and aligned channels), including the FAS and BAS within this rate. On the MC side all channels are framed; on the SC side only the I-channel (Time-slot 1) carries H.221 framing, but the corresponding bits (shown with dashed outline) in the other time-slots shall be vacated, so that framing can be inserted at the CAU in the SC-to MC direction (and removed in the other): this is done under the [SM-comp] command. + +![Diagram of a Channel Aggregation Unit (CAU) showing two output modes. On the left, a single output stream is labeled '192 kbit/s'. On the right, three separate output streams are each labeled '64 kbit/s'. The CAU is represented by a box with one input line on the left and three output lines on the right, connecting to the two mode representations.](d4af765160d04ecef538e5066006dc77_img.jpg) + +Diagram of a Channel Aggregation Unit (CAU) showing two output modes. On the left, a single output stream is labeled '192 kbit/s'. On the right, three separate output streams are each labeled '64 kbit/s'. The CAU is represented by a box with one input line on the left and three output lines on the right, connecting to the two mode representations. + +FIGURE 8/H.244 + +### Mode properties + +The properties of the four modes are summarised in Table 1. “Dynamic rate change” refers to dynamic variation of the number N of aggregated channels during a session: rate changes within available connection capacity can normally be made in less than 40 ms for Modes H2, B3; when new connections must be added, the response depends on call set-up time; for Mode B1 interruption of the application is inevitable. + +TABLE 1/H.244 + +| | Mode B1 | Mode H2 | Mode B2 | Mode B3 | +|--------------------------------------------|---------|---------------------------------|----------------|---------| +| Aggregation overhead (% for 64k multiples) | None | 2.5% in the additional channels | 1.5% | 1.5625% | +| Dynamic rate changes | No | Yes | Yes | Yes | +| Exact multiples of 64/56 kbit/s | Yes | Yes (H.221-framed only) | No | Yes | +| Interworking with MCE (audiovisual) | No | Yes | Not applicable | No | + +The applicability of the Modes is summarised in Table 2. + +## 5.3 General description of the aggregation process + +The Channel Aggregation Unit (CAU) is a device having on the one side a single-channel port and on the other side a multiplicity of 64/56-channel ports. This Recommendation defines the behaviour of the CAU in respect of the input and output signals at the two sides. + +When new multiple channels are active, the CAU buffers the incoming signals in order to synchronise them, and then reads the user information to the SC side. In the reverse direction, the CAU takes the serial input into the SC side and loads it into those parallel channels which it knows to be in synchronism at the remote end. However, according to the two quite different conditions described at the beginning of 5.1, the CAU has two different processes, that is, depending on whether or not it is communicating in-band with the single-channel terminal; selection of the correct process is described in clause 6. + +TABLE 2/H.244 + +| Mode | AV/non-AV | Mode applicable when . . . . . | +|------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| B1 | Audiovisual | The remote end is not an MCE, and the remote CAU does not support Mode H2, and Mode B3 is considered too inefficient or is not available; bitstream treated as UD only; NoTAC case, so external means must be used to set bit rate | +| | Non-audiovisual | Exact multiple of 64/56 kbit/s required, absence of dynamic rate change tolerable, B3 considered too inefficient | +| B2 | Audiovisual | Not applicable – B2 does not provide suitable bit rates | +| | Non-audiovisual | Exact multiple of 64/56 kbit/s not essential, dynamic rate change desired | +| B3 | Audiovisual | The remote end is not an MCE, and the remote CAU does not support Mode H2; dynamic rate change more important than efficiency; bitstream treated as UD only; NoTAC case, so external means must be used to set bit rate | +| | Non-audiovisual | Exact multiple of 64/56 kbit/s required, dynamic rate change more important than efficiency | +| H2 | Audiovisual | Remote end is an MCE, or a CAU supporting Mode H2; TAC case, so no external control is needed | +| | Non-audiovisual | Not applicable (unless conformant to [1]) | + +H.244 aggregation is based on such communication (this applies only to H.320 audiovisual terminals): effectively the SCE communicates with the other terminal at the remote end of the connection in the normal way, by capability sets and commands; the CAU merely moderates this communication in order to assure satisfactory conditions on the multiple 64/56-channel section. The CAU informs the terminal about the upper limit of transmission rate, which depends on the number of channels available, or what the other end can accept, whichever is the lower; it does this by suitably modifying the capability sets exchanged. The synchronisation process is based on [1], which also provides for numbering of the channels. Negotiation of appropriate conditions is based on [2]; the capability sets emanating from the CAU define the range of signals that could be sent to it, while commands define the actual signal structure being transmitted from the CAU. See clauses 7-8. + +In ISO aggregation there is no in-band communication between the CAU and SCE, the CAU is totally responsible for its communication with the remote CAU, presenting on its SC side a clear digital channel at a specified bit rate, which can be used for any purpose whatsoever (including audiovisual systems). Here again the CAU must control the transmission rate from the terminal – this can be by clocking if the application rate can be varied in this way (and this does not apply to terminals conforming to [3]), or by other external signalling. In this (“NoTAC”) case, the synchronisation and communication processes are fully described in [4] – see clause 9. + +## 5.4 CAU functionality + +The CAU functionality can be summarised thus: + +- 1) All modes + - MC-to-SC direction: Synchronisation and aggregation of N incoming 64/56-channels into one outgoing single channel; SC-to-MC direction: partition of incoming user information onto N outgoing 64/56 kbit/s channels, with framing as appropriate. +- H2 mode + - Ignore the compatibility bits incoming on the SC side, putting FAS/BAS into the corresponding outgoing bits on the MC side; remove FAS/BAS in additional channels incoming on the MC side, putting Ones into the corresponding outgoing bits on the SC side. + +- | | | | +|----|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| 2) | All modes | Control the aggregated bit rate according to application requirements and the available MC capacity. | +| | H2 mode | Modify capability sets and commands to ensure correct operation of the system; detect changes to capacity requirements from incoming capability sets. | +| 3) | All modes | Detect fault conditions and take appropriate action. | +| 4) | All modes | (Optionally) transfer the call-control signalling between the ISDN and single-channel networks. | + +The action of the CAU is not completely specified, some matters being left to the choice of the implementer or service provider. For example, requests for channels will not all mature simultaneously, and it is a matter of choice whether each should be added in to the communication as soon as available (increasing the bit rate in a series of many steps), or alternatively held back until all or most are available (increasing the bit rate in one single step). + +# 6 Choice of H.244 or ISO aggregation + +The procedure at the start of the call is as depicted in the diagram of Figure 9 and described in the following subclauses. It is mandatory that all CAUs intended for use with audiovisual terminals conforming to [1] be able to operate in Mode H2. + +There are two alternatives for the choice between H.244 and ISO aggregation processes at each CAU: + +- 1) the CAU may be preset to perform H.244 or ISO aggregation only, according to the environment for which the CAU is intended; +- 2) if 1) has not been applied, a decision must be taken on the basis of incoming signals on both SC and MC sides, as described below. + +Reference is made to Figure 9. The CAU operation is essentially the same whether it is the originating (calling) end or the destination (called) end (the setting of Flag1 is for possible later use when the additional channels are to be requested, or in the procedure of [4]). + +**First**, three local conditions are tested, and if any of the three are not met then ISO aggregation (clause 9) is used. These conditions are: + +Condition 1: There has been no preset to specify ISO aggregation only; note that if the connected SCE is an H.320 terminal, then only modes B1 or B3 may be used – B2 does not provide valid bit rates; + +Condition 2: H.221 framing is detected, coming from the SCE; note that a timeout is involved here; + +Condition 3: The capset in that H.221 frame contains the value {SM-comp} and/or {6B-H0-comp}. + +Only under these three conditions is the H.221-framed signal forwarded from the SCE on the initial channel, otherwise the CAU generates the signal defined in 7.1 of ISO/IEC CD 13871 [4]. + +**Second**, the incoming signal is searched for H.221 framing and [4] signal. If a [4] signal is detected (see Note, Figure 9) ISO aggregation clause 9 is used – if previously following clauses 7-8 because the above three conditions were met, this means switching to [4] signals on the outgoing transmission. A timeout of 10 seconds is applied to the detection of [4] to allow for the possibility that clauses 7-8 is initially being followed at the remote end. **Only if the transmissions in both directions are H.221-framed and SCEs transmit the capability value {SM-comp} or {6B-H0-comp} does H.244 aggregation procedure apply.** + +### Failure states + +If no incoming framing, either of H.221 or [4] type, Failure State 1 is reached: it must be presumed that the remote end-point is neither a CAU nor an audiovisual MCE (in some applications, speech communication using PCM according to Recommendation G.711 may still be possible). + +![Flowchart for Recommendation H.244 (07/95) Figure 9/H.244 showing the logic for ISO aggregation and H.221 framing detection.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + + graph TD + Start([standby]) --> Connect{CONNECT +received} + Start --> ConnAck{CONN_ACK +received} + + subgraph Originating + Connect --> SetFlag0[Set Flag1 = 0] + end + + subgraph Destination + ConnAck --> SetFlag1[Set Flag1 = 1] + end + + SetFlag0 --> Cond1{ISO +aggregation +preset?} + SetFlag1 --> Cond1 + + Cond1 -- Yes --> Exit3((3)) + Cond1 -- No --> SearchH221[Search for H.221 framing +incoming on SC side] + + SearchH221 --> Cond2{H.221 framing +present?} + Cond2 -- No --> CondH244{H.244 +aggregation +preset?} + CondH244 -- No --> Exit3 + CondH244 -- Yes --> Fail3([failure +state 3]) + + Cond2 -- Yes --> LookSM[*Look for {SM-comp} from SCE] + LookSM --> Cond3{{SM-comp} +present*} + Cond3 -- No --> Exit3 + Cond3 -- Yes --> ForwardPCM[Forward framed PCM +from SC side to MC side +Capset_mod_1 (7.3.4.1)] + + ForwardPCM --> ExamineMC[Examine signals +incoming on MC side] + + ExamineMC --> Res1[Neither H.221 nor +ISO 13871 signals +detected within 10 s] --> Fail1([failure +state 1]) + ExamineMC --> Res2[H.221 framing +detected] --> Exit1((1)) + ExamineMC --> Res3[ISO 13871 signal +detected (Note)] --> SwitchISO[Switch transmitted +signal to ISO 13871] --> Exit2((2)) + + Exit3 --> SendISO[Send ISO 13871 +signal - clause 9] + SendISO --> ExamineMC2[Examine signals +incoming on MC side] + + ExamineMC2 --> Res4[ISO 13871 signal +detected (Note)] --> Exit2 + ExamineMC2 --> Res5[H.221 framing +detected] --> Cond4{Incoming +{SM-comp} +present*} + ExamineMC2 --> Res6[Neither H.221 no +ISO 13871 signals +detected within 10 s] --> Fail1_2([failure +state 1]) + + Cond4 -- No --> Fail1_2 + Cond4 -- Yes --> AwaitISO[Await incoming +change to ISO 13871 +signal structure] --> Fail2([failure +state 2]) + AwaitISO --> Exit2 + +``` + +**FIGURE 9/H.244** + +**Recommendation H.244 (07/95)** + +NOTE – Answering Endpoint initially transmits all Ones. + +Flag1 used in ISO 13871 aggregation to distinguish Calling/Answering Endpoints + +\*alternative: {6B-H0-comp} + +ISO 13871 aggregation selected in all other cases – clause 9 applies + +All conditions met for H.244 aggregation clauses 7, 8 apply + +T1520210-95/d09 + +Flowchart for Recommendation H.244 (07/95) Figure 9/H.244 showing the logic for ISO aggregation and H.221 framing detection. + +If one end is transmitting according to ISO aggregation operation (clause 9), one of the above three conditions not having been fulfilled, and the remote end is sending H.221 framing but without {SM-comp} or {6B-H0-comp}, Failure State 2 is reached, reflecting the technical impossibility of interconnecting to an MCE at the remote end. + +Failure State 3 is reached if the CAU is set to operate in the H2 mode but the connected SCE is not sending H.221 framing. + +The action to be taken on reaching any of the failure states is an implementation matter. The SBE symbol NII [1], indicating incompatible aggregators, may be used in appropriate fault conditions. + +# 7 H.244 aggregation procedure + +## 7.1 Call control + +The signalling for call control is outside the scope of this Recommendation: it is assumed that external signalling is available to set up the appropriate paths between the equipments – for example, the “D-channel” in the case of ISDN. Means are described in 8.1.3 for the in-band transfer of network address information where this is needed for call control. + +### 7.1.1 Initial channel + +The initial 64/56-channel is requested when communication has been established between the calling-end SCE and its CAU and any necessary checking has been carried out (for example, presence of {SM-comp} if required (see Note); presence of {n\*64k} with $n > 1$ ). During establishment of the initial channel, the value of $N_m$ is calculated from the SCE capset (see 7.3.2). + +NOTE – SCE terminals conforming to [3] should include the 6B-H0 compatibility mode; if this capability and {SM-comp} are both absent, the CAU shall adopt NoTAC working – see clause 6. + +### 7.1.2 Additional channels + +Additional-channel requests are made by a CAU when: + +- the total of channels already requested is less than the lower of $N_m$ and $N'_m$ , and (in dial-up cases) the CAU is the calling end. + +Additional channels may be dropped by a CAU when the total of channels already requested exceeds the lower of $N_m$ and $N'_m$ . + +## 7.2 Channel synchronisation + +On the multiple-channel side, CAUs shall always synchronise all connected channels (in the ISDN case, those for which CONNECT has been sent or received). The value of $N_a$ is determined according to the channels for which: + +- the incoming A-bit is set to zero; +- the channel numbers in BAS position (see Appendix I) form a continuous series from 1 to $N_a$ . + +## 7.3 In-band procedure using H.221 BAS codes + +In-band signalling shall follow [2] to ensure correct operation between the equipments. H.221 framing is used on all the multiple channels, and also on the single-channel side. All BAS commands are effective from the start of the following submultiframe, and remain in force until countermanded – see [2]. + +CAUs shall remain responsive to incoming H.221 framing throughout the call, on the MC side on all channels, and on the SC side. This means that when no framing is detected the equipment will nevertheless respond rapidly when the incoming signal is switched to a framed mode, and will also respond quickly (if required) to fault conditions. + +### 7.3.1 Control of transfer rate + +The main function of the CAU is to match the effective transfer rates on its two sides. To do this it must be able to control the user information which is sent to it: it does this in-band on the MC side, and in the TAC case on the SC side also. The in-band method is by means of the capability set (see [2]) which it transmits or forwards; this shall always contain transfer-rate capability values no higher than the available rate on the other side of the CAU. See Figure 10. + +*NOTE – Other in-band signalling between SCE and CAU is possible - this is outside the scope of this Recommendation, and should be treated in the same way as –out-of-band– signalling - see NoTAC case.* + +![Diagram of a CAU showing in-band information streams. A central box labeled 'CAU' has four arrows: (1) and (4) on the left, (2) and (3) on the right.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +graph LR + subgraph " " + direction LR + A[In-band information TAC case] -- "(1)" --> CAU[CAU] + CAU -- "(4)" --> A + CAU -- "(2)" --> B[In-band information initial B-channel] + B -- "(3)" --> CAU + end + style CAU stroke-width:2px,stroke:#000 + +``` + +T1517270-94/d10 + +Diagram of a CAU showing in-band information streams. A central box labeled 'CAU' has four arrows: (1) and (4) on the left, (2) and (3) on the right. + +FIGURE 10/H.244 + +### 7.3.2 Determination of the transfer-rate capabilities to be transmitted on the MC side + +Reference is made to the in-band streams (1) and (2) in Figure 10. + +Transfer-rate capabilities transmitted on the MC side (2) are decided on the basis of the capset received from the SCE (1). + +If $n_m > 1$ , an $\{N \times 64k\}$ type value, with $N = n_m$ shall be sent – this is required for communication with an MCE, and also provides for communication with an SCE with fallback to all lesser multiples of 64/56 kbit/s. + +If SCE-transmitted capset contains values of $\{n*64k\}$ for which $n$ is higher than $n_m$ , these also shall be included (see 7.3.4.2) for potential communication with another SCE, though fallback to lesser rates will be limited. + +### 7.3.3 Determination of the transfer-rate capabilities to be transmitted on the SC side + +Reference is made to the in-band streams (3) and (4) in Figure 10. + +Transfer-rate capabilities transmitted on the SC side (4) are decided on the basis of the capset received from the MC side (3) and the number of channels currently available, $N_a$ . + +The incoming capability set on the MC side contains a single transfer-rate value of $\{N'_m \times 64k\}$ type: this value shall be replaced by a $\{n*64k\}$ -type transfer-rate value, corresponding either to the incoming value (i.e. such that $n = N'_m$ ), or to the available number of channels (i.e. such that $n = N_a$ ), whichever is the lesser. In general, the highest $\{n*64k\}$ -type transfer-rate capability value transmitted from CAU on the SC side (4) is that which indicates the maximum bit rate that can be accepted, including both user information and management. + +### 7.3.4 Capability sets transmitted from a CAU + +Capsets are not generated by the CAU itself; they are generated only in the terminals, and forwarded, in both SC and MC directions, by the CAUs with modifications as described in 7.3.4.1 and 7.3.4.2 below. No changes in the length of a capset are made by a CAU, the value {null} being used to fill any unused positions. + +The capsets outgoing from CAUs shall not violate the rules set out in [2]; in particular, all capsets which follow one another in succession without intervening commands shall be identical. Thus when circumstances require that a new modification be made, this shall always be done on a new capset, which shall usually be stimulated by the procedure of 7.3.5. + +#### 7.3.4.1 Modification of SCE capset for forwarding towards MC side + +The CAU modifies the SCE capset changing the lowest transfer-rate capability value to $\{N_m \times 64k\}$ ; here $N_m$ is determined from 7.3.2 above, except that if the SCE capset has only one transfer-rate capability value $\{n*64k\}$ then this is sent unchanged (see Note 2 below). + +This may be understood with reference to the following examples: + +| Original transfer-rate capabilities | External setting | Modified transfer-rate capabilities | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------------------------| +| 512, 384, 320, 256, 192, 128, 64 | None | 512, 384, 320, 256, 192, 128, 6B | +| 384, 256, 192, 128, 64 | 6B | 384, 256, 192, 128, 4B (Note 1) | +| 384, 320, 256, 192, 128 | None | 384, 320, 256, 192, 6B | +| 384, 320, 256, 192, 128 | 4B | 384, 320, 256, 192, 4B | +| 384 | None | 384 (Note 2) | +| NOTES
1 6B cannot be used here since the rate 320 is absent from the list of original capabilities.
2 Refer to Appendix III for further comments on this exceptional provision. | | | + +Modification of the lowest transfer-rate capability guarantees that the transfer-rate capability for just 64 kbit/s, which is the same as 1B, is never present in the same set as a higher rate $\{N \times B\}$ -type. The remaining transfer rate and all other Capability codes are left unchanged. A remote MCE will receive the $\{N \times B\}$ -type and ignore the $\{n*64k\}$ -type values. The MCE will use the received A bits to determine the rate at which it can transmit data. + +#### 7.3.4.2 Modification of capset incoming from MC side for forwarding towards SCE + +The CAU modifies the capset incoming from the MC side according to 7.3.3. All values of transfer rate exceeding the capacity actually available on the multiple-channel link shall be replaced by the $\{\text{null}\}$ value; $\{\text{null}\}$ shall also be used to avoid any repetitions. If only five channels are active, and even though information (3) from the equipment connected at the multiple-channel side is that up to 6B (for example) would be acceptable, then the capset transmitted by the CAU in direction (4) shall contain the transfer rate values no higher than $\{320k\}$ . + +This is best understood with reference to the following examples: + +| Original transfer-rate capabilities | Available channels | Modified transfer-rate capabilities | +|-------------------------------------|--------------------|-------------------------------------| +| 512, 384, 320, 256, 192, 128, 6B | 6 | Null, 384, 320, 256, 192, 128, 6B | +| 384, 256, 192, 128, 4B | 3 | Null, null, 192, 128, null | +| 384, 256, 192, 128, 5B | 5 | Null, 256, 192, 128, 320 | + +### 7.3.5 Notification of change of $N_a$ + +When the number of available channels has been changed, this will be made known to the SCE by sending a new value of {n\*64k} capability, using the modification of 7.3.4.2. If a sequence of (identical) capsets is already being received on the MC side, then two steps shall be taken: + +- one complete set shall be replaced by redundant commands (since to comply with [2] a capset change may not be made without interposing at least one command); +- the next capset shall be modified according to 7.3.4.2, using the new value of $N_a$ . + +If there are no capsets incoming on the MC side, it is necessary to stimulate a capability exchange. + +This procedure is initiated by the CAU by sending [capex] to the SCE (7.3.6.3). + +NOTE – A terminal which has sent {6B-H0-comp} rather than {SM-comp} is unlikely to respond to [capex]; in this case the CAU may trigger the capability exchange by repeating the last capset it sent to the SCE. + +The SCE shall respond with a new capset, which is passed by the CAU towards the distant terminal with modification according to 7.3.4.1. + +If the distant terminal is an MCE, it shall respond with a new capset, which is conveyed to the SCE with modification by the CAU according to 7.3.4.2, reflecting the new value of $N_a$ . + +If the distant terminal is a CAU2 and SCE2, then the capset reaching SCE will have been modified by CAU2 according to 7.3.4.2, reflecting the new value of $N_a$ . + +SCE2 shall likewise respond with a new capset, which is conveyed to SCE1 with modification by CAU2 according to 7.3.4.1 and by CAU1 according to 7.3.4.2, also reflecting the new value of $N_a$ . + +### 7.3.6 Commands transmitted from a CAU + +In the TAC case, commands are not usually generated by the CAU itself, other than that certain substitutions shall be made, as detailed below; the remainder are generated only in the terminals. + +#### 7.3.6.1 Substitution of transfer rate commands + +When [n\*64k] from SCE is detected at the CAU, it is replaced by [N × 64k] with N = n for forwarding on MC side. + +When [N × 64k] from the MC side is detected at the CAU, it is replaced by [n\*64k] with N = n for forwarding to SCE. + +#### 7.3.6.2 Insertion and removal of [SM-comp] and [6B-H0-comp] + +When [SM-comp] or [6B-H0-comp] from SCE is detected at the CAU, it is replaced by repeating the latest command received from SCE, for forwarding on MC side. + +A redundant command from the MC side shall be replaced by the same value, [SM-comp] or [6B-H0-comp], for forwarding to SCE. For security, this process should be repeated from time to time during the communication, when convenient. + +#### 7.3.6.3 Insertion of [capex] + +When it is necessary to stimulate a capability exchange between two terminals, a redundant command from the MC side shall be replaced by [capex] for forwarding to the SCE; on receipt, a terminal which is able to recognise [capex] shall: + +- if it is transmitting a capset, complete that capset, followed by cap-mark and a valid command (see [2]); +- start a new capability exchange according to [2]. + +#### 7.3.6.4 Insertion of [AggIN]\* + +When it is necessary rapidly to notify the SCE of an unexpected drop in available capacity, four successive commands from the MC side shall be replaced by [AggIN]\* for forwarding to SCE. A terminal which is able to recognise [AggIN]\* shall make a mode switch to a lower transfer rate, consistent with the available multiple channels. (See Note 1 of 8.1.3.) + +## 7.4 Transmission of user information by a CAU + +Transmissions in both directions are governed by commands generated by the two terminals, except that on the MC side of a CAU the outgoing transfer rate is modified from the incoming value on the SC side according to 7.3.6, and on the SC side of a CAU the outgoing transfer rate is modified from the incoming value on the MC side, also according to 7.3.6. + +While a CAU has no connection made on one side, it transmits its locally-generated frame structure on the other side, in Mode 0F with audio S and any relevant command (such as [Recommendation G.711-A-law]) in the BAS position. + +As soon as both sides are connected, the signal from each side is routed directly through to the other with two modifications: + +- BAS values are modified according to 7.3.4 and 7.3.6; +- (optional) a fractional-frame buffer may be inserted to avoid the discontinuity arising when the locally-generated frame structure is replaced by that coming in on the other side. + +NOTE – Because of the dependent H.221 framing on the two sides of the CAU, there may be a need to interrupt the framing while doing the synchronisation of an additional channel. + +# 8 Initialisation, Mode/Rate changing and Fault recovery + +## 8.1 Initialisation + +The in-band procedures are the same for any CAU, whether it originates the request for the initial channel (calling end-point) or is the destination (called end-point). An additional example description of initialisation, with SDL figure, is given in Appendix II. + +**Summary** (see also examples in Appendix I): + +| Step | | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1. | SCE connected to CAU: CAU detects framing and {SM-comp} or {6B-H0-comp}, determines desired rate from transfer-rate capabilities from SCE | +| 2. | CAU makes/receives initial connection (which can be to/from another CAU or an MCE) | +| 3. | Seeks and finds H.221 framing on connected initial channel | +| 4. | Capability exchange takes place between the SCE and the remote equipment, the transfer rate values being modified by the CAU in both directions; audio from SCE is sent; audio incoming from MC side is passed on | +| 5. | Requests additional network addresses if necessary; then requests additional connections (see Note 1 in 8.1.3) | +| 6. | Synchronises additional channels when connected | +| 7. | The command [SM-comp] is sent to the SCE, to ensure voiding of “compatibility bits” later | +| 8. | The command [capex] is sent to the SCE, to stimulate another capability exchange | +| 9. | New cap-exchange, CAU now modifies to reflect the available multi-channel capacity | +| 10. | SCE performs a mode switch to the desired higher rate | + +### 8.1.1 Single-channel Side + +#### Incoming signal + +The CAU searches the incoming signal from the SCE for frame and multiframe alignment. If H.221 framing is absent, it is presumed that a non-audiovisual equipment is connected, and transmission of Mode 0F is discontinued (see clause 6). In the case of Outcome I (see [2]), the incoming capset is examined. The CAU derives the target number of B-channels $N_m$ from $n_m$ . If the capset does not also contain {SM-comp} or {6B-H0-comp}, then the call cannot proceed as a TAC case, but should be treated as NoTAC (see clause 6). + +#### Outgoing signal + +Until a suitable signal is available incoming on the MC side, the CAU may optionally transmit towards SCE an audible signal S in Mode 0F (local audio coding law) and any relevant command (such as [Recommendation G.711-A-law]) in the BAS position. When H.221-framed signals are received on the MC side, the whole signal from the MC side is forwarded towards SCE, the capsets being modified according to 7.3.4.2. At this stage the transfer rate is just 64 kbit/s. + +### 8.1.2 Multi-channel Side, initial channel + +The following process begins when the CAU is notified, by external signalling, that the first connection on the MC side is completed. + +#### Incoming signal + +The incoming signal is searched for H.221 framing; if H.221 framing is not found, the process continues as in clause 6. + +#### Outgoing signal + +Transmission shall be in H.221-framed Mode 0F with the signal from SCE, as follows. + +Receiving an H.221-framed signal from the SC side, the CAU forwards this same signal outwards from the MC side. If the signal contains (repeated) capsets, it modifies these according to 7.3.4.1; if it does not, then it sends [capex] towards the SCE to stimulate a capability exchange initiated by the SCE. + +Transmission continues to follow the initialisation procedure according to [2]. When Outcome I is reached, mode switching may take place, if desired, before the establishment of additional channels; however, such action is the responsibility of the terminals alone – the CAU merely modifies the commands according to 7.3.6. + +### 8.1.3 Multi-channel Side, additional channels + +A CAU (Note 1) may dial more channels after having detected framing on the initial channel and a capset incoming on the MC side. The total number $N_d$ of connections to be dialled is selected as follows. + +The capset incoming on the MC side contains a single value of type $\{N \times 64k\}$ , where $N = N'_m$ ; there may also be values of type $\{n \times 64k\}$ (indicating the presence of another CAU – such values are not transmitted by an MCE), the maximum value being $n = n'_{max}$ . + +The capset incoming on the SC side contains values of type $\{n \times 64k\}$ , the maximum value being $n = n_{max}$ ; the value of $N_m$ is also calculated (see 7.3.2). + +$N_d$ is the greater of $\{(the\ lesser\ of\ N_m, N'_m), (the\ lesser\ of\ n_{max}, n'_{max})\}$ . + +NOTE 1 – It is assumed in this Recommendation that additional connections may only be requested by the same unit that has obtained the initial connection; likewise the dropping of unwanted connections; however, since the in-band behaviour is not affected, there is no problem if some or all calls are made/dropped from the other endpoint. + +NOTE 2 – According to the properties of the network accessed, it may be necessary to insert a delay of up to 1 second between successive additional connection requests. + +Methods of obtaining network address information for additional channels are described in [2]. + +NOTE 3 – The use of SBE rather than MBE messages is preferred here, since the substitution of an MBE message into the BAS command stream from a terminal is much more difficult than substitution of an SBE. In general, the use of same or consecutive network addresses is strongly recommended. + +When the CAU is notified, by external signalling, that an additional connection is completed, it carries out framing and synchronisation according to [1], and assigns the channel a number (see Appendix I). Transmission of user information may be expanded onto the additional channels either: + +- a) one by one as they become synchronised and numbered; +- b) the target number of channels is reached (as determined from the incoming capset or external control); or +- c) an allowed time limit for reaching this target has expired. + +NOTE 4 – The choice of time limit is an implementation matter. + +At this point the CAU shall notify the SCE of the increased available capacity on the MC side; this it does by the procedure of 7.3.5. Subsequent mode switching is a matter for the terminals alone – the CAU merely modifies the commands according to 7.3.6. + +## 8.2 Change of transmission rate during a session + +Either terminal may switch its transmission to another mode within the ranges declared by the capability set received from the CAU, which is itself dependent on $N_a$ . If having made such a mode change, one or more channels are no longer required, the calling CAU may release them. + +An increase of $N_a$ may be necessary to accommodate the desired transmission; if the called CAU is not permitted to request additional channels, and so shall await that action by the calling CAU (see Note 1 of 8.1.3), this need shall first be communicated to the calling CAU in the same way as for the initial session set-up (see 7.3.2), and the calling CAU then requests the additional channels. The change of available capacity is notified to both terminals by the procedure of 7.3.5, and they then make the desired mode change(s). + +## 8.3 Recovery from fault conditions + +The onset of a fault may be recognised in a number of ways: by loss of frame synchronisation on an incoming channel; by an incoming A-bit set to 1; errored connections, from CRC4 checks; a high number of temporary loss-of-synchronisation events; others. The currently effective value of $N_a$ is determined from the incoming A-bits and channel numbers according to 7.2 (this may be delayed a short time to allow for the possibility of rapid restoration of normal conditions). + +The change of available capacity is notified rapidly by each CAU to its local SCE by sending the double SBE symbol [AggIN]\*, enabling them to switch immediately to a lower rate and enable the application to recover. + +NOTE – A terminal which has sent {6B-H0-comp} rather than {SM-comp} is unlikely to respond to [AggIN]\*; in this case the CAU shall repeat the last capset it sent to the SCE, except that the modification according to 7.3.4.2 now reflects the lower value of $N_a$ . + +## 8.4 Further mode changes + +When it is desired to switch on video and/or data transmission, the procedures of [2] are followed. No action is required by the CAU as long as no change of transfer rate is involved. Symmetry of transmission is, as always, a matter for terminal procedures, neither terminal being obliged by in-band management signals to conform to a transmission mode adopted by the other. The transfer rate is essentially under the control of the calling party. + +# 9 ISO aggregation procedure + +The ISO Aggregation Procedure is described in [4]. The frame structure is detailed in 5.2 of this Recommendation, and the initialisation in 7.1. + +# Appendix I + +## Examples of procedures + +(This appendix does not form an integral part of this Recommendation) + +#### **Case 1: Interconnection of two H.320 SCE-type terminals via two CAUs using Mode H2; the last additional connection is tardy in maturing; during the call, a reduction of capacity is requested.** + +NOTE – The values 13, 9, 7, 3 in the following are purely for example. + +SCE1 is the calling end, and the desired number of channels is specified as that giving the same capacity as the highest transfer rate in the SCE1 capset; the time limit for awaiting that number in the initial set-up phase is set at TIM. It is also specified that the SC side is to be active for user information as much as possible, including the period when only one channel is active. + +1. CAU1 makes the initial channel request when the connection from SCE1 to CAU1 is complete and H.221 framing from SCE1 is detected, or upon an external stimulus which also resets the “Sequence A” timer in the SCE. It transmits tone S in Mode 0U towards SCE1. + +NOTE – If CAU1 does not detect H.221 framing from SCE2 within {1 s?}, then it sends [4] framing to CAU2, and tone S is omitted. + +2. CAU2 receives SETUP from CAU1, and establishes contact with SCE2 (this may be a permanently active link, or require “waking up”); it then returns CONNECT to CAU1, and commences transmission of the framed signal from SCE2. It transmits tone S in Mode 0U towards SCE2. + +NOTE – If CAU2 does not detect H.221 framing from SCE2 within {1 s?}, then it sends [4] framing to CAU1. + +3. On receipt of CONNECT, CAU1 sends towards MC side the incoming signal from SC side, including capsets (repeated continuously) from SCE with modification according to 7.3.4.1 – in this case the {13\*64k} is modified to {13B}. +4. CAU1 detects H.221 framing from CAU2; the incoming capset is that from SCE2, repeated; this contains {9B}, which is lower than the {13B}; passes the incoming signal from the MC side on towards the SCE1, modifying the {9B} to {1B}, since only one channel is yet available. Likewise CAU2 detects H.221 framing from CAU1; the incoming capset is that from SCE1, repeated; it passes the incoming signal from the MC side on towards the SCE1, modifying the {13B} to {1B}. +5. Comparing the incoming {13\*64k} and {9B}, CAU1 calculates $N_d$ as “9”, and requests 8 additional connections, obtaining the remote addresses if necessary using the NCA-a procedure of [2]. +6. By expiry of TIM, CONNECT has been received from CAU2 in respect of 7 more channels; CAU1 adds buffering and numbering to these to achieve synchronism and returns A = 0 according to Recommendation H.221. CAU2 does likewise. CAU1 and CAU2 both look for a redundant command, and replace this with [SM-comp]. +7. When CAU1 receives A = 0 on initial and the seven available additional channels, it must stimulate another capability exchange, in order to be able to indicate the increase channel availability; therefore it sends [capex] to SCE1, which returns one capset + cap-mark. + +NOTE – An H.320 terminal which transmits {6B-H0-comp} rather than {SM-comp} may not recognise [capex]; in this case the CAU may send the previously transmitted capset from CAU2, which it would have stored for the purpose; however, such situations would be better avoided. + +8. CAU1 passes this on to CAU2 with usual modification (7.3.4.1), namely {13\*64k} >> {13B}. +9. CAU2 passes the capset on to SCE2, modifying the capset again according to 7.3.4.2, namely replacing one of the transfer-rate values with {512k}, the n\*64k value corresponding to the multiple-channel capacity actually now available. +10. SCE2 itself responds with its normal capset + cap-mark; CAU2 passes this back with modification as in 7.3.4.1. +11. CAU1 passes the capset on to SCE1, modifying the capset again according to 7.3.4.2, namely replacing one of the transfer-rate values with {512k}, the n\*64k value corresponding to the multiple-channel capacity actually now available. +12. Both SCEs are now in a position to mode switch to any framed rate up to [512k]. The CAUs must watch out for [SM-comp] coming from SCEs and replace it with a redundant command, and also for [n\*64k] commands, replacing them with [N × 64k]. +13. CONNECT is belatedly received by CAU1 from CAU2 in respect of last requested channel; it adds buffering and numbering to this to achieve synchronism and returns A = 0 according to Recommendation H.221. +14. Receives A = 0 on this last channel; same process as in 7-12 above, with 512k replaced by 576k. +15. At user request, SCE1 is instructed to drop three channels – namely down to 384k; SCE1 sends new capset containing { 128k, 192k, 256k, 320k, 384k} + cap-mark; the process continues from step 8. above. + +**Case 2: Interconnection of two H.320 terminals, one an MCE type, the other SCE working via a CAU;** the number of desired connections, etc., is as for Case 1. **The SCE is the calling end.** + +1. CAU makes the initial channel request when the connection from SCE to CAU is complete and H.221 framing from SCE is detected, or upon an external stimulus which also resets the “Sequence A” timer in the SCE. It transmits tone S in Mode 0U towards SCE. + +NOTE – If CAU does not detect H.221 framing from SCE2 within {1 s?}, then it sends [4] framing to MCE, and tone S is omitted; on later receipt of H.221 framing from MCE and this does not itself change to [4] framing within 2 s, a terminal-incompatibility fault condition is identified. + +2. MCE receives SETUP from CAU; it then returns CONNECT to CAU, and commences transmission of the framed signal. +3. On receipt of CONNECT, CAU sends towards MC side the incoming signal from SC side, including capsets (repeated continuously) from SCE with modification according to 7.3.4.1 – in this case the {13\*64k} is modified to {13B}. +4. CAU detects H.221 framing and capset is that from MCE, repeated; this contains {9B}, which is lower than the {13B}; passes the incoming signal from the MC side on towards the SCE, modifying the {9B} to {64k}, since only one channel is yet available. Likewise MCE detects H.221 framing from CAU; the incoming capset is that from SCE, repeated. +5. Comparing the incoming {13\*64k} and {9B}, CAU calculates $N_d$ as “9”, and requests 8 additional connections, obtaining the remote addresses if necessary using the NCA-a procedure of [2]. + +6. By expiry of TIM, CONNECT has been received from CAU2 in respect of 7 more channels; CAU adds buffering and numbering to these to achieve synchronism and returns A = 0 according to Recommendation H.221. CAU2 does likewise. CAU looks for a redundant command, and replaces this with [SM-comp]. +7. When CAU receives A = 0 on initial and the seven available additional channels, it must stimulate another capability exchange, in order to be able to indicate the increase channel availability; therefore it sends [capex] to SCE, which returns one capset + cap-mark. + +NOTE – An H.320 terminal which transmits {6B-H0-comp} rather than {SM-comp} may not recognise [capex]; in this case the CAU may send the previously transmitted capset from CAU2, which it would have stored for the purpose; however, such situations would be better avoided. + +8. CAU passes this on to MCE with usual modification (7.3.4.1), namely {13\*64k} >> {13B}. +9. (Deleted). +10. MCE itself responds with its normal capset + cap-mark. +11. CAU passes the capset on to SCE, modifying the capset again according to 7.3.4.2, namely replacing one of the transfer-rate values with {512k}, the n\*64k value corresponding to the multiple-channel capacity actually now available. +12. Both SCE and MCE are now in a position to mode switch to any framed rate up to [512k]. The CAUs must watch out for [SM-comp] coming from SCEs and replace it with a redundant command, and also for [n\*64k] commands, replacing them with [N × 64k]. +13. CONNECT is belatedly received by CAU from MCE in respect of last requested channel; it adds buffering and numbering to this to achieve synchronism and returns A = 0 according to Recommendation H.221. +14. Receives A = 0 on this last channel; same process as in 7-12 above, with 512k replaced by 576k. +15. At user request, SCE is instructed to drop three channels – namely down to 384k; SCE sends new capset containing {.....128k, 192k, 256k, 320k, 384k} + cap-mark; the process continues from step 8. above. + +**Case 3: Interconnection of two H.320 terminals, one an MCE type, the other SCE working via a CAU;** the number of desired connections, etc., is as for Case 1. **MCE is the calling end.** + +1. CAU sends the initial channel CONNECT when the connection from SCE to CAU is complete and H.221 framing from SCE is detected, or upon an external stimulus which also resets the “Sequence A” timer in the SCE. It transmits tone S in Mode 0U towards SCE. + +NOTE – If CAU does not detect H.221 framing from SCE2 within {1 s?}, then it sends [4] framing to MCE, and tone S is omitted; on later receipt of H.221 framing from MCE and this does not itself change to [4] framing within 2 s, a terminal-incompatibility fault condition is identified. + +2. MCE sends SETUP to CAU; when it then receives CONNECT from CAU, and commences transmission of the framed signal. +3. Having sent CONNECT, CAU sends towards MC side the incoming signal from SC side, including capsets (repeated continuously) from SCE with modification according to 7.3.4.1 – in this case the {13\*64k} is modified to {13B}. + +4. CAU detects H.221 framing and capset is that from MCE, repeated; this contains {9B}, which is lower than the {13B}; passes the incoming signal from the MC side on towards the SCE, modifying the {9B} to {64k}, since only one channel is yet available. Likewise MCE detects H.221 framing from CAU; the incoming capset is that from SCE, repeated. +5. Comparing the incoming {13B} and its own {9B}, MCE calculates $N_d$ as “9”, and requests 8 additional connections, obtaining the remote addresses if necessary using the NCA-a procedure of [2]. +6. By expiry of TIM, CONNECT has been sent to MCE in respect of 7 more channels; CAU adds buffering and numbering to these to achieve synchronism and returns $A = 0$ according to Recommendation H.221. CAU2 does likewise. CAU looks for a redundant command, and replaces this with [SM-comp]. +7. When CAU receives $A = 0$ on initial and the seven available additional channels, it must stimulate another capability exchange, in order to be able to indicate the increase channel availability; therefore it sends [capex] to SCE, which returns one capset + cap-mark. + +NOTE – An H.320 terminal which transmits {6B-H0-comp} rather than {SM-comp} may not recognise [capex]; in this case the CAU may send the previously transmitted capset from CAU2, which it would have stored for the purpose; however, such situations would be better avoided. + +8. CAU passes this on to MCE with usual modification (7.3.4.1), namely {13\*64k} >> {13B}. +9. (No action in Case 2). +10. MCE itself responds with its normal capset + cap-mark. +11. CAU passes the capset on to SCE, modifying the capset again according to 7.3.4.2, namely replacing one of the transfer-rate values with {512k}, the $n*64k$ value corresponding to the multiple-channel capacity actually now available. +12. Both SCE and MCE are now in a position to mode switch to any framed rate up to [512k]. The CAUs must watch out for [SM-comp] coming from SCEs and replace it with a redundant command, and also for [ $n*64k$ ] commands, replacing them with [ $N \times 64k$ ]. +13. CONNECT is belatedly received by CAU from MCE in respect of last requested channel; it adds buffering and numbering to this to achieve synchronism and returns $A = 0$ according to Recommendation H.221. +14. Receives $A = 0$ on this last channel; same process as in 7-12 above, with 512k replaced by 576k. +15. At user request, SCE is instructed to drop three channels – namely down to 384k; SCE sends new capset containing {.....128k, 192k, 256k, 320k, 384k} + cap-mark; the process continues from step 8 above. + +# Appendix II + +## Example of SDL diagram for TAC initialisation + +(This appendix does not form an integral part of this Recommendation) + +![SDL diagram for TAC initialisation flowchart](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` +graph TD; Start((1)) --> F1[Forward framed PCM from MC side to SC side Capset_mod_2]; F1 --> F2[Calculate N_d from both capsets Calc_N_d]; F2 --> D1{Flag 1 = 0?}; D1 -- Yes --> O1{{Request (N_d-1) more connections}}; D1 -- No --> F3[Set timer TT ~10 secs]; O1 --> F3; F3 --> O2{{single-channel operation}}; O2 --> O3{{additional channels}}; O3 --> D2{reached minimum number?}; D2 -- Yes --> D3{TT expired?}; D2 -- No --> F4[Set N_a = available number of channels]; D3 -- No --> F4; D3 -- Yes --> F4; F4 --> D4{capsets i/c from SCE?}; D4 -- Yes --> F5[remove one capset]; D4 -- No --> F6[Send [capex] to SCE]; F5 --> F7[Use new value of N_a in Capset_mod_2]; F6 --> F7; F7 --> F8[Apply rules of command modification, 7.3.6]; F8 --> O4{{Multiple-channel operation}}; +``` + +The flowchart illustrates the TAC initialisation process. It begins with a start symbol '1', followed by 'Forward framed PCM from MC side to SC side Capset\_mod\_2'. Then, 'Calculate Nd from both capsets Calc\_Nd'. A decision 'Flag 1 = 0?' follows. If 'Yes', it goes to 'Request (Nd-1) more connections' (a data store symbol). If 'No', it goes to 'Set timer TT ~10 secs'. Both paths lead to 'single-channel operation' (a state symbol). This is followed by 'additional channels' (a state symbol). A decision 'reached minimum number?' follows. If 'Yes', it goes to 'TT expired?' (a decision symbol). If 'No', it goes to 'Set Na = available number of channels'. If 'TT expired?' is 'Yes', it also goes to 'Set Na = available number of channels'. If 'No', it goes to 'Set Na = available number of channels'. From 'Set Na = available number of channels', a decision 'capsets i/c from SCE?' follows. If 'Yes', it goes to 'remove one capset' (a process symbol). If 'No', it goes to 'Send [capex] to SCE' (a process symbol). Both paths lead to 'Use new value of Na in Capset\_mod\_2' (a process symbol). This is followed by 'Apply rules of command modification, 7.3.6' (a process symbol). Finally, it reaches 'Multiple-channel operation' (a state symbol). + +SDL diagram for TAC initialisation flowchart + +T15 15040-94/d11 + +## TAC operation selected + +The incoming signal on the MC side is forwarded, with modification of its Capset according to the procedure Capset\_mod\_2 (see main text: $N_a$ is set at 1). At this point, only one 64 kbit/s connection is available, so all higher incoming transfer-rate capabilities must be replaced by {null}. + +If the CAU is sending a highest transfer-rate capability of $\{N_m \times B\}$ , resulting from Capset\_mod\_1, and is receiving $\{N'_m \times B\}$ from the remote end, then calc\_Nd gives the lower of $N_m$ and $N'_m$ . + +In Recommendation H.320 all the connections must be requested from the same end. If the network addresses are unknown, they may be obtained as described in the text (not shown here). + +When the additional connections have been made, they are synchronised (H.221 procedure) and when incoming A = 0 on each it is made available to the process defined here. + +However, it may not be desirable to increase the bit rate used for the H.320 application in many steps of 64 kbit/s, but rather wait in single-channel operation until a chosen minimum number of channels is available – for example, if 5 additional channels have been requested, it would be sensible to wait until at least 4 of these are available, but in any case not wait more than, say, 10 seconds. Such waiting is not mandatory – the “minimum” could be just 1. + +From this point, $N_a$ , hitherto set at 1, is increased to reflect the true number of available channels connected and synchronised. The rules for Capset\_mod\_2 still apply (see main text): essentially, the transfer rates passed to the SCE must be a continuous series 128, 192, 256... $n \times 64$ , where $n = N_a$ is equal to the number of 64k connections available. Since the capset must not be changed in length, the {null} value is used to fill gaps left by incoming values not passed on. + +Of course Capset\_mod\_2 needs capsets to operate on. If there is already a stream of (identical) capsets coming in on the MC side, then a complete set must be removed, replacing the BAS codes with valid commands (this is because, according to [2] concatenated capsets must be identical); then the next capset is modified using the changed value of $N_a$ . If there are currently no capsets, they must be stimulated by sending [capex] to the SCE (replacing a redundant command). The SCE will then send a capset, and the remote end must respond even if it is an MCE. + +The actual increase in operating bit rate is carried out by the two terminals – the CAU need do nothing about this, though it must apply the modification rules to the commands – see 7.3.6 in the main text. + +# Appendix III + +## Comments on the modification of capsets and commands + +(This appendix does not form an integral part of this Recommendation) + +Whereas the capset sent by a CAU on the MC side normally contains a single value from the series {1B, 2B, 3B....}, in the case where only one transfer rate capability $\{n \times 64\}$ has been received from the SCE then this value alone is forwarded; this exception provides for the case that two similar SCEs be connected via two CAUs. + +It should be noted that an SCE declaring only {384} will not interwork with a {6B} MCE via a CAU according to this Recommendation; if the CAU were to forward {6B} towards the MCE, this would falsely imply that the SCE had declared {384, 320, 256, 192, 128, 64}. An SCE which is intended for interworking with an MCE should possess all the transfer-rate caps in the $\{n \times 64\}$ series up to the maximum intended operating rate, as well as {SM-comp} and the ability to recognise and act upon [capex] and [AggIN]\*. + +NOTE – If a CAU is provided in a situation where its only use is to interconnect a {384 only} SCE with {6B}-type MCEs, then it could be programmed to modify {384} to {6B}, and to deal appropriately with the situation when 5 or fewer channels are available. It is clear that connection to another CAU may cause misoperation if the CAU is programmed in this way. + +There may be cases where the modification involves substitution by a two-byte capability or command. For example, the CAU modifies {512, H0, 320, 256, 192, 128, 1B} from the SCE to include {7 × 64}; this can be done by replacing the {512} value rather than {1B}. + +The CAU must (= “shall”) conform to Recommendation H.242 at all times: in particular, it must not cause a change (in content or even in order) in forwarded capsets without the insertion of a command – this may require the omission of a complete capset. \ No newline at end of file diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.1-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0c406296b0ca18353339c5689c01cc54fac3cc0e --- /dev/null +++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/raw.md @@ -0,0 +1,9482 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.1** + +(03/2013) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: Version 3** + +Recommendation ITU-T H.248.1 + +![ITU logo](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue, with "ITU" in a larger, bold font above it. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.248.1 + +# Gateway control protocol: Version 3 + +# Summary + +To achieve greater scalability, this Recommendation decomposes the ITU-T H.323 Gateway function defined in Recommendation ITU-T H.246 into functional subcomponents and specifies the protocols these components use to communicate. This allows implementations of ITU-T H.323 gateways to be highly scalable and encourages leverage of widely deployed Switched Circuit Network (SCN) capabilities such as SS7 switches. This also enables ITU-T H.323 gateways to be composed of components from multiple vendors distributed across multiple physical platforms. The purpose of this Recommendation is to add capabilities currently defined for ITU-T H.323 systems and is intended to provide new ways of performing operations already supported in ITU-T H.323. + +This revision contains a number of clarifications on: + +- Signal behaviour on new Streams; +- time based Statistics and their applicability to multi flow streams; +- the impact of the Mode property on Statistics; +- Event behaviour with respect to new Streams; +- ServiceChange version handling. + +# History + +| Edition | Recommendation | Approval | Study Group | +|---------|--------------------------------|------------|-------------| +| 1.0 | ITU-T H.248 | 2000-06-15 | 16 | +| 1.1 | ITU-T H.248.1 v1.1 | 2002-03-29 | 16 | +| 2.0 | ITU-T H.248.1 v2 | 2002-05-22 | 16 | +| 2.1 | ITU-T H.248.1 v2 (2002) Cor. 1 | 2004-03-15 | 16 | +| 3.0 | ITU-T H.248.1 v3 | 2005-09-13 | 16 | +| 3.1 | ITU-T H.248.1 v3 (2005) Amd. 1 | 2008-05-02 | 16 | +| 3.2 | ITU-T H.248.1 v3 (2005) Amd. 2 | 2009-12-14 | 16 | +| 4.0 | ITU-T H.248.1 v3 | 2013-03-16 | 16 | + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +# INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# Table of Contents + +###### Page + +| | | | +|------|----------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 4 | +| 3.1 | Terms defined elsewhere ..... | 4 | +| 3.2 | Terms defined in this Recommendation..... | 4 | +| 4 | Abbreviations and acronyms ..... | 5 | +| 5 | Conventions ..... | 7 | +| 5.1 | Key words to indicate requirement levels ..... | 7 | +| 5.2 | Connection endpoint naming conventions ..... | 7 | +| 6 | Connection model..... | 9 | +| 6.1 | Contexts ..... | 10 | +| 6.2 | Terminations..... | 11 | +| 6.3 | Wildcarding principles ..... | 17 | +| 7 | Commands ..... | 19 | +| 7.1 | Descriptors..... | 20 | +| 7.2 | Command application programming interface..... | 45 | +| 8 | Transactions..... | 60 | +| 8.1 | Common parameters..... | 62 | +| 8.2 | Transaction application programming interface..... | 62 | +| 8.3 | Messages..... | 64 | +| 9 | Transport..... | 65 | +| 9.1 | Ordering of commands ..... | 65 | +| 9.2 | Protection against restart avalanche ..... | 66 | +| 9.3 | Protection against Notify avalanche ..... | 67 | +| 10 | Security considerations ..... | 67 | +| 10.1 | Protection of protocol connections..... | 67 | +| 10.2 | Interim AH scheme..... | 67 | +| 10.3 | Protection of media connections ..... | 68 | +| 11 | MG-MGC control interface ..... | 68 | +| 11.1 | Multiple Virtual MGs ..... | 69 | +| 11.2 | Cold start ..... | 69 | +| 11.3 | Negotiation of protocol version..... | 70 | +| 11.4 | Failure of an MG ..... | 70 | +| 11.5 | Failure of an MGC..... | 70 | +| 11.6 | MGC-MG control association monitoring ..... | 71 | +| 11.7 | Compatibility ..... | 71 | +| 12 | Package definition ..... | 72 | + +| | Page | +|-----------------------------------------------------------------------|------| +| 12.1 Guidelines for defining packages ..... | 73 | +| 12.2 Guidelines to defining parameters to events and signals..... | 78 | +| 12.3 Identifiers..... | 78 | +| 12.4 Package registration..... | 79 | +| 13 Profile definition..... | 79 | +| 14 IANA ITU-T H.248 registrations ..... | 79 | +| 14.1 Package registration procedure..... | 79 | +| 14.2 Error code registration procedure..... | 81 | +| 14.3 ServiceChange reason registration procedures..... | 81 | +| 14.4 Profile registration procedures ..... | 82 | +| Annex A – Binary encoding of the protocol ..... | 83 | +| A.1 Coding of wildcards ..... | 83 | +| A.2 ASN.1 syntax specification ..... | 84 | +| A.3 DigitMaps and path names ..... | 101 | +| Annex B – Text encoding of the protocol..... | 103 | +| B.1 Coding of wildcards ..... | 103 | +| B.2 ABNF specification..... | 103 | +| B.3 Hexadecimal octet coding ..... | 118 | +| B.4 Hexadecimal octet sequence..... | 118 | +| Annex C – Tags for media stream properties ..... | 119 | +| C.1 General media attributes..... | 119 | +| C.2 Mux properties..... | 120 | +| C.3 General bearer properties ..... | 120 | +| C.4 General ATM properties..... | 121 | +| C.5 Frame relay..... | 123 | +| C.6 IP..... | 123 | +| C.7 ATM AAL 2 ..... | 124 | +| C.8 ATM AAL 1 ..... | 125 | +| C.9 Bearer capabilities ..... | 126 | +| C.10 AAL 5 properties..... | 134 | +| C.11 SDP equivalents..... | 134 | +| C.12 H.245 ..... | 135 | +| Annex D – Transport over IP..... | 136 | +| D.1 Transport over IP/UDP using Application Level Framing (ALF) ..... | 136 | +| D.2 Using TCP ..... | 139 | +| Annex E – Basic packages ..... | 141 | +| E.1 Generic ..... | 141 | +| E.2 Base Root Package ..... | 143 | +| E.3 Tone Generator Package..... | 147 | + +| | Page | +|-----------------------------------------------------------------|-------------| +| E.4 Tone Detection Package ..... | 148 | +| E.5 Basic DTMF Generator Package..... | 152 | +| E.6 DTMF Detection Package ..... | 153 | +| E.7 Call Progress Tones Generator Package..... | 156 | +| E.8 Call progress tones detection package..... | 157 | +| E.9 Analog Line Supervision Package..... | 158 | +| E.10 Basic Continuity Package..... | 161 | +| E.11 Network Package..... | 163 | +| E.12 RTP Package ..... | 167 | +| E.13 TDM Circuit Package..... | 171 | +| E.14 Segmentation Package..... | 172 | +| E.15 Notification Behaviour ..... | 175 | +| Annex F – ServiceChange Procedures..... | 180 | +| F.1 Introduction ..... | 180 | +| F.2 Control Association Definition..... | 182 | +| F.3 Events leading to ServiceChange Procedures ..... | 182 | +| F.4 ServiceChange Element Description ..... | 186 | +| F.5 Use of ServiceChange parameters..... | 188 | +| F.6 ServiceChange versus TerminationState ..... | 191 | +| Appendix I – Example call flows..... | 193 | +| I.1 Residential gateway to residential gateway call..... | 193 | +| Appendix II – ITU-T H.248 Package template..... | 202 | +| Appendix III – ITU-T H.248 profile definition template..... | 206 | +| Appendix IV – Practices on Statistics – Example use-cases ..... | 220 | +| IV.1 Introduction ..... | 220 | +| IV.2 Active statistics of a new termination ..... | 221 | +| IV.3 Activating and deactivating statistics ..... | 223 | +| IV.4 Resetting statistics ..... | 225 | +| IV.5 Reporting statistics ..... | 226 | +| IV.6 Reading statistics ..... | 227 | +| Bibliography..... | 231 | + + + +## Recommendation ITU-T H.248.1 + +# Gateway control protocol: Version 3 + +# 1 Scope + +This Recommendation defines the protocols used between elements of a physically decomposed multimedia gateway. There are no functional differences from a system view between a decomposed gateway, with distributed sub-components potentially on more than one physical device, and a monolithic gateway such as described in [ITU-T H.246]. This Recommendation does not define how gateways, multipoint control units or interactive voice response (IVR) units work. Instead it creates a general framework that is suitable for these applications. + +Packet network interfaces may include IP, ATM or possibly others. The interfaces will support a variety of switched circuit network (SCN) signalling systems, including tone signalling, ISDN, ISUP, QSIG and GSM. National variants of these signalling systems will be supported where applicable. + +Products claiming compliance with Version 1 of Recommendation ITU-T H.248.1 shall comply with all of the mandatory requirements of Recommendation ITU-T H.248.1 originally approved in 06/2000 and reissued in 03/2002. + +Products claiming compliance with Version 2 of Recommendation ITU-T H.248.1 shall comply with all of the mandatory requirements of Recommendation ITU-T H.248.1 originally approved in 05/2002 and updated in 03/2004. + +Products claiming compliance with this Recommendation shall comply with all of the mandatory requirements of Recommendation ITU-T H.248.1 approved in 03/2013. + +Products shall indicate the version of the protocol in use by using ServiceChangeVersion as '1' to refer to Recommendation ITU-T H.248.1 (03/2002), '2' to refer to Recommendation ITU-T H.248.1 including its Corrigendum 1 (03/2004), and '3' to refer to Recommendation ITU-T H.248.1 (09/2005 and 03/2013). + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T E.106] Recommendation ITU-T E.106 (2003), *International Emergency Preference Scheme (IEPS) for disaster relief operations*. +- [ITU-T E.107] Recommendation ITU-T E.107 (2007), *Emergency Telecommunications Service (ETS) and interconnection framework for national implementations of ETS*. +- [ITU-T H.225.0] Recommendation ITU-T H.225.0 (2009), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. + +- [ITU-T H.235.0] Recommendation ITU-T H.235.0 (2005), *H.323 Security: Framework for security in H-series (H.323 and other H.245-based) multimedia systems.* +- [ITU-T H.245] Recommendation ITU-T H.245 (2011), *Control protocol for multimedia communication.* +- [ITU-T H.246] Recommendation ITU-T H.246 (2006), *Interworking of H-series multimedia terminals with H-series multimedia terminals and voice/voiceband terminals on GSTN, ISDN and PLMN ISDN.* +- [ITU-T H.248.4] Recommendation ITU-T H.248.4 (2009), *Gateway control protocol: Transport over Stream Control Transmission Protocol (SCTP).* +- [ITU-T H.248.5] Recommendation ITU-T H.248.5 (2009), *Gateway control protocol: Transport over ATM.* +- [ITU-T H.248.8] Recommendation ITU-T H.248.8 (2013), *Gateway control protocol: Error code and service change reason description.* +- [ITU-T H.248.14] Recommendation ITU-T H.248.14 (2009), *Gateway control protocol: Inactivity timer package.* +- [ITU-T H.248.30] Recommendation ITU-T H.248.30 (2007), *Gateway control protocol: RTCP extended performance metrics packages.* +- [ITU-T H.323] Recommendation ITU-T H.323 (2009), *Packet-based multimedia communications systems.* +- [ITU-T I.363.1] Recommendation ITU-T I.363.1 (1996), *B-ISDN ATM Adaptation Layer specification: Type 1 AAL.* +- [ITU-T I.363.2] Recommendation ITU-T I.363.2 (2000), *B-ISDN ATM Adaptation Layer specification: Type 2 AAL.* +- [ITU-T I.363.5] Recommendation ITU-T I.363.5 (1996), *B-ISDN ATM Adaptation Layer specification: Type 5 AAL.* +- [ITU-T I.366.1] Recommendation ITU-T I.366.1 (1998), *Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2.* +- [ITU-T I.366.2] Recommendation ITU-T I.366.2 (2000), *AAL type 2 service specific convergence sublayer for narrow-band services, plus Corrigendum 1 (2002).* +- [ITU-T I.371] Recommendation ITU-T I.371 (2004), *Traffic control and congestion control in B-ISDN.* +- [ITU-T Q.763] Recommendation ITU-T Q.763 (1999), *Signalling System No. 7 – ISDN user part formats and codes, plus Amendment 3 (2004).* +- [ITU-T Q.765.5] Recommendation ITU-T Q.765.5 (2004), *Signalling System No. 7 – Application transport mechanism: Bearer Independent Call Control (BICC).* +- [ITU-T Q.931] Recommendation ITU-T Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control, plus Amendment 1 (2002): Extensions for the support of digital multiplexing equipment.* +- [ITU-T Q.2630.1] Recommendation ITU-T Q.2630.1 (1999), *AAL type 2 signalling protocol – Capability Set 1.* + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [ITU-T Q.2931] | Recommendation ITU-T Q.2931 (1995), Digital subscriber signalling system No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control , plus Amendment 4 (1999). | +| [ITU-T Q.2941.1] | Recommendation ITU-T Q.2941.1 (1997), Digital subscriber signalling system No. 2 – Generic identifier transport . | +| [ITU-T Q.2961.1] | Recommendation ITU-T Q.2961.1 (1995), Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional signalling capabilities to support traffic parameters for the tagging option and the sustainable call rate parameter set . | +| [ITU-T Q.2961.2] | Recommendation ITU-T Q.2961.2 (1997), Digital subscriber signalling system No. 2 – Additional traffic parameters: Support of ATM transfer capability in the broadband bearer capability information element , plus Corrigendum 1 (1999). | +| [ITU-T Q.2965.1] | Recommendation ITU-T Q.2965.1 (1999), Digital subscriber signalling system No. 2 – Support of Quality of Service classes , plus Amendment 1 (2000). | +| [ITU-T Q.2965.2] | Recommendation ITU-T Q.2965.2 (1999), Digital subscriber signalling system No. 2 – Signalling of individual Quality of Service parameters . | +| [ITU-T V.76] | Recommendation ITU-T V.76 (1996), Generic multiplexer using V.42 LAPM-based procedures , plus Corrigendum 1 (2005). | +| [ITU-T X.213] | Recommendation ITU-T X.213 (2001) ISO/IEC 8348:2002, Information technology – Open Systems Interconnection – Network service definition . | +| [ITU-T X.680] | Recommendation ITU-T X.680 (2008) ISO/IEC 8824-1:2008, Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation . | +| [ITU-T X.690] | Recommendation ITU-T X.690 (2008) ISO/IEC 8825-1:2008, Information Technology – ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) . | +| [ISO/IEC 10646] | ISO/IEC 10646 (2003), Information technology – Universal Multiple-Octet Coded character Set (UCS) . | +| [ATM Forum UNI 4.0] | Broadband Forum (1996), ATM User-Network Interface (UNI) Signalling Specification – Version 4.0 . | +| [IETF RFC 791] | IETF RFC 791 (1981), Internet protocol . | +| [IETF RFC 1006] | IETF RFC 1006 (1987), ISO Transport Service on top of the TCP, Version 3 . | +| [IETF RFC 2234] | IETF RFC 2234 (1997), Augmented BNF for Syntax Specifications: ABNF . | +| [IETF RFC 2327] | IETF RFC 2327 (1998), SDP: Session Description Protocol . | +| [IETF RFC 2373] | IETF RFC 2373 (1998), IP Version 6 Addressing Architecture . | +| [IETF RFC 2401] | IETF RFC 2401 (1998), Security Architecture for the Internet Protocol . | + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------| +| [IETF RFC 2402] | IETF RFC 2402 (1998), IP Authentication Header . | +| [IETF RFC 2406] | IETF RFC 2406 (1998), IP Encapsulating Security Payload (ESP) . | +| [IETF RFC 2409] | IETF RFC 2409 (1998), The Internet Key Exchange (IKE) . | +| [IETF RFC 2460] | IETF RFC 2460 (1998), Internet Protocol, Version 6 (IPv6) Specification . | +| [IETF RFC 3550] | IETF RFC 3550 (2003), RTP: A Transport Protocol for Real-Time Applications . | +| [IETF RFC 3551] | IETF RFC 3551 (2003), RTP Profile for Audio and Video Conferences with Minimal Control . | +| [IETF RFC 3556] | IETF RFC 3556 (2003), Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth . | +| [IETF RFC 5226] | IETF RFC 5226 (2008), Guidelines for Writing an IANA Considerations Section in RFCs . | +| [IETF RFC 5615] | IETF RFC 5615 (2009), H.248/MEGACO Registration Procedures . | + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 access gateway:** A type of gateway that provides a user-network interface (UNI) such as ISDN. + +**3.2.2 descriptor:** A syntactic element of the protocol that groups related properties. For instance, the properties of a media flow on the MG can be set by the MGC by including the appropriate descriptor in a command. + +**3.2.3 media gateway (MG):** The media gateway converts media provided in one type of network to the format required in another type of network. For example, an MG could terminate bearer channels from a switched circuit network (e.g., DS0s) and media streams from a packet network (e.g., RTP streams in an IP network). This gateway may be capable of processing audio, video and ITU-T T.120 alone or in any combination, and will be capable of full duplex media translations. The MG may also play audio/video messages and perform other IVR functions, or may perform media conferencing. + +**3.2.4 media gateway controller (MGC):** Controls the parts of the call state that pertain to connection control for media channels in an MG. + +**3.2.5 multipoint control unit (MCU):** An entity that controls the setup and coordination of a multi-user conference that typically includes processing of audio, video and data. + +**3.2.6 residential gateway:** A gateway that interworks an analogue line to a packet network. A residential gateway typically contains one or two analogue lines and is located at the customer premises. + +**3.2.7 SCN FAS signalling gateway:** This function contains the SCN signalling interface that terminates SS7, ISDN or other signalling links where the call control channel and bearer channels are collocated in the same physical span. + +**3.2.8 SCN NFAS signalling gateway:** This function contains the SCN signalling interface that terminates SS7 or other signalling links where the call control channels are separated from bearer channels. + +**3.2.9 stream:** Bidirectional media or control flow received/sent by a media gateway as part of a call or conference. + +**3.2.10 stream endpoint (SEP):** Relates to a stream associated to a Termination. A SEP is identified by the tuple of *StreamID* and *TerminationID* values. + +**3.2.11 stream endpoint pair (SEPP):** Two associated stream endpoints (SEP) of two Terminations within the same Context. The two SEPs share thus the same *StreamID* value. There is always a point-to-point topology for stream endpoint pair configurations (e.g., there is no further associated SEP on a third Termination, etc.). + +**3.2.12 trunk:** A communication channel between two switching systems such as a DS0 on a T1 or E1 line. + +**3.2.13 trunking gateway:** A gateway between SCN network and packet network that typically terminates a large number of digital circuits. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-----------------------------------------------------------| +| AAD | Average Acknowledgement Delay | +| AAL | ATM Adaptation Layer | +| ABNF | Augmented Backus-Naur Format | +| ADEV | Average Deviation | +| ALC | Automatic Level Control | +| ALF | Application Level Framing | +| AH | Authentication Header | +| ATM | Asynchronous Transfer Mode | +| BER | Basic Encoding Rules | +| C | Context | +| CAS | Channel Associated Signalling | +| DLSR | Delay since last SR | +| DNS | Domain Name System | +| DTMF | Dual Tone Multi-Frequency | +| ESP | Encapsulating Security Payload | +| FAS | Facility Associated Signalling | +| GSM | Global System for Mobile communications | +| GW | Gateway | +| IANA | Internet Assigned Numbers Authority (superseded by ICANN) | +| ICANN | Internet Corporation for Assigned Names and Numbers | +| ICV | Integrity Check Value | +| IEPS | International Emergency Preference Scheme | + +| | | +|---------|--------------------------------------| +| IKE | Internet Key Exchange | +| IP | Internet Protocol | +| IS | In-Service | +| ISUP | ISDN User Part | +| IVR | Interactive Voice Response | +| LD | Local Descriptor | +| LSR | Last SR timestamp | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MID | Message Identifier | +| MTP3 | Message Transfer Part 3 | +| MTU | Maximum Transmission Unit | +| MWD | Maximum Waiting Delay | +| NDA | Non Disclosure Agreement | +| NFAS | Non-Facility Associated Signalling | +| OoS | Out-of-Service | +| PRI | Primary Rate Interface | +| PSTN | Public Switched Telephone Network | +| QoS | Quality of Service | +| RD | Remote Descriptor | +| RR | Receiver Report | +| RSA | Rivest, Shamir and Adleman algorithm | +| RTCP | RTP Control Protocol | +| RTP | Real-time Transport Protocol | +| RTPD | Round-Trip Propagation Delay | +| Rx | Receive | +| SC | ServiceChange | +| SCN | Switched Circuit Network | +| SCTP | Stream Control Transmission Protocol | +| SDP | Session Description Protocol | +| SEP | Stream End Point | +| SEPP | Stream End Point Pair | +| SG | Signalling Gateway | +| SR | Sender Report | +| SS7 | Signalling System No. 7 | +| T, Term | Termination | +| TCP | Transmission Control Protocol | + +| | | +|-----|------------------------| +| Tx | Transmit | +| UDP | User Datagram Protocol | +| VBD | Voice Band Data | +| VMG | Virtual Media Gateway | + +# 5 Conventions + +## 5.1 Key words to indicate requirement levels + +In this Recommendation, "shall" refers to a mandatory requirement, while "should" refers to a suggested but optional feature or procedure. The term "may" refers to an optional course of action without expressing a preference. + +## 5.2 Connection endpoint naming conventions + +### 5.2.1 Generic concept + +There are basically four connection endpoints (concerning sources and sinks of traffic) in case of a bidirectional connection. ITU-T H.248 uses a specific terminology for naming these endpoints from the perspective of an ITU-T H.248 entity. Figure 1 provides a conceptual overview. The naming scheme is generic because it is technology-independent. + +![Figure 1: Connection endpoint naming conventions – Generic concept. The diagram shows a bidirectional connection between an ITU-T H.248 entity and a Peer entity. The ITU-T H.248 entity has two connection endpoints. The top endpoint is labeled 'Local destination' and the bottom endpoint is labeled 'Local source'. The Peer entity also has two connection endpoints. The top endpoint is labeled 'Remote source' and the bottom endpoint is labeled 'Remote destination'. Arrows indicate the direction of traffic flow: from the Local source to the Remote destination, and from the Remote source to the Local destination. A dashed arrow labeled 'Perspective' points to the ITU-T H.248 entity, indicating the viewpoint from which the naming is defined. The text 'H.248.1 v3(13)_F01' is in the bottom right corner.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +Figure 1: Connection endpoint naming conventions – Generic concept. The diagram shows a bidirectional connection between an ITU-T H.248 entity and a Peer entity. The ITU-T H.248 entity has two connection endpoints. The top endpoint is labeled 'Local destination' and the bottom endpoint is labeled 'Local source'. The Peer entity also has two connection endpoints. The top endpoint is labeled 'Remote source' and the bottom endpoint is labeled 'Remote destination'. Arrows indicate the direction of traffic flow: from the Local source to the Remote destination, and from the Remote source to the Local destination. A dashed arrow labeled 'Perspective' points to the ITU-T H.248 entity, indicating the viewpoint from which the naming is defined. The text 'H.248.1 v3(13)\_F01' is in the bottom right corner. + +**Figure 1 – Connection endpoint naming conventions – Generic concept** + +The geographical locations of the endpoints are termed as 'local' (also known as 'near-end') and as 'remote' (also known as 'far-end'). The traffic directions are termed as 'source' (also known as 'egress', 'outgoing', 'outbound', 'transmit', or 'Tx') and as 'destination' (also known as 'ingress', 'incoming', 'inbound', 'receive', or 'Rx'). + +### 5.2.2 Scope of Local and Remote Descriptors + +The Local and Remote Descriptors are defined in clause 7.1.8. Both descriptors have different connection endpoints in scope (see Figure 2). The Local Descriptor (LD) is related to the "local destination" endpoint, the Remote Descriptor (RD) is related to the "remote destination" endpoint. The media gateway is primarily responsible for the resources and configuration of the "local source" endpoint (NOTE – There are a few protocol elements which allow the MGC to control certain endpoint aspects). The "remote source" endpoint is completely out of scope of ITU-T H.248 entities. + +![Figure 2: Connection endpoint naming conventions – Scope of Local and Remote Descriptors. The diagram shows an ITU-T H.248 media gateway on the left and a Peer entity on the right connected by a Bidirectional packet-switched Bearer connection. The media gateway contains a Packet-switched bearer: connection endpoint with a green circle representing a traffic sink. Labels 'Local destination' and 'Local source' point to this green circle, while 'Remote source' and 'Remote destination' point to a white circle. The Peer entity contains another Packet-switched bearer: connection endpoint with a red circle representing a traffic source. Labels 'Local source' and 'Local destination' point to this red circle, while 'Remote source' and 'Remote destination' point to a white circle. A Stream descriptor box on the left contains 'Local descriptor' and 'Remote descriptor' with dashed lines connecting them to the green circle. A dashed arrow labeled 'Perspective' points from the media gateway towards the Peer entity. Reference H.248.1 v3(13)_F02 is shown at the bottom right.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 2: Connection endpoint naming conventions – Scope of Local and Remote Descriptors. The diagram shows an ITU-T H.248 media gateway on the left and a Peer entity on the right connected by a Bidirectional packet-switched Bearer connection. The media gateway contains a Packet-switched bearer: connection endpoint with a green circle representing a traffic sink. Labels 'Local destination' and 'Local source' point to this green circle, while 'Remote source' and 'Remote destination' point to a white circle. The Peer entity contains another Packet-switched bearer: connection endpoint with a red circle representing a traffic source. Labels 'Local source' and 'Local destination' point to this red circle, while 'Remote source' and 'Remote destination' point to a white circle. A Stream descriptor box on the left contains 'Local descriptor' and 'Remote descriptor' with dashed lines connecting them to the green circle. A dashed arrow labeled 'Perspective' points from the media gateway towards the Peer entity. Reference H.248.1 v3(13)\_F02 is shown at the bottom right. + +**Figure 2 – Connection endpoint naming conventions – Scope of Local and Remote Descriptors** + +Figure 2 underlines that just the traffic sink endpoints of ITU-T H.248 streams are controlled via the Local and Remote Descriptors. + +### 5.2.3 Concrete "connection" types + +An example shall illustrate the application of the naming conventions for a specific combination of a bearer technology and protocol layer. + +#### 5.2.3.1 Example "IP connection" + +Figure 3 shows an IP connection, e.g., behind an ITU-T H.248 IP stream or termination, or below an IP-based ITU-T H.248 control association. + +![Figure 3: Connection endpoint naming conventions – IP connection. The diagram shows an ITU-T H.248 media gateway on the left and a Peer entity (e.g., IP host, IP next hop, ITU-T H.248 MGC) on the right connected by a Bidirectional IP connection. The media gateway has two IP connection endpoints. The top endpoint has a green circle labeled LD(A) (Local destination) and a white circle labeled LS(A) (Local source). The bottom endpoint has a white circle labeled LS(A) (Local source) and a red circle labeled RD(A) (Remote destination). The Peer entity has two IP connection endpoints. The top endpoint has a white circle labeled RS(A) (Remote source) and a red circle labeled RD(A) (Remote destination). The bottom endpoint has a red circle labeled RD(A) (Remote destination) and a white circle labeled LS(A) (Local source). IP headers are shown above the top endpoints and below the bottom endpoints. The top IP header has DA (destination address) and SA (source address) fields. The bottom IP header has SA (source address) and DA (destination address) fields. Dashed lines with arrows connect the local and remote descriptors to the appropriate circles. A dashed arrow labeled 'Perspective' points from the media gateway towards the Peer entity. Reference H.248.1 v3(13)_F03 is shown at the bottom right. A legend at the bottom left defines: LD local destination, LS local source, RD remote destination, RS remote source, DA destination address, SA source address, and a circle representing L3 address.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +Figure 3: Connection endpoint naming conventions – IP connection. The diagram shows an ITU-T H.248 media gateway on the left and a Peer entity (e.g., IP host, IP next hop, ITU-T H.248 MGC) on the right connected by a Bidirectional IP connection. The media gateway has two IP connection endpoints. The top endpoint has a green circle labeled LD(A) (Local destination) and a white circle labeled LS(A) (Local source). The bottom endpoint has a white circle labeled LS(A) (Local source) and a red circle labeled RD(A) (Remote destination). The Peer entity has two IP connection endpoints. The top endpoint has a white circle labeled RS(A) (Remote source) and a red circle labeled RD(A) (Remote destination). The bottom endpoint has a red circle labeled RD(A) (Remote destination) and a white circle labeled LS(A) (Local source). IP headers are shown above the top endpoints and below the bottom endpoints. The top IP header has DA (destination address) and SA (source address) fields. The bottom IP header has SA (source address) and DA (destination address) fields. Dashed lines with arrows connect the local and remote descriptors to the appropriate circles. A dashed arrow labeled 'Perspective' points from the media gateway towards the Peer entity. Reference H.248.1 v3(13)\_F03 is shown at the bottom right. A legend at the bottom left defines: LD local destination, LS local source, RD remote destination, RS remote source, DA destination address, SA source address, and a circle representing L3 address. + +**Figure 3 – Connection endpoint naming conventions – IP connection** + +The two local or remote connection endpoints may be assigned to the same or different IP interfaces. They are then so called symmetrical or asymmetrical (connection) addresses. + +# 6 Connection model + +The connection model for the protocol describes the logical entities, or objects, within the Media Gateway that can be controlled by the Media Gateway Controller. The main abstractions used in the connection model are terminations and contexts. + +A *termination* sources and/or sinks one or more streams. In a multimedia conference, a termination can be multimedia and sources or sinks multiple media streams. The media stream parameters, as well as bearer parameters are encapsulated within the termination. + +A *context* is an association between a collection of terminations. There is a special type of context, the *NULL Context*, which contains all terminations that are not present in any other context and therefore not associated to any other termination. For instance, in a decomposed access gateway, all idle lines are represented by terminations in the NULL Context. + +Following is a graphical depiction of these concepts. The diagram of Figure 4 gives several examples and is not meant to be an all-inclusive illustration. The asterisk box in each of the contexts represents the logical association of terminations implied by the context. + +![Figure 4: Example of ITU-T H.248.1 connection model. The diagram shows a Media Gateway containing three Contexts and one Null context. Each Context contains a Termination (RTP stream), an asterisk box, and a Termination (SCN bearer channel). The Null context contains a Termination (SCN bearer channel). Arrows indicate connections between the Media Gateway and the external environment.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +The diagram illustrates the ITU-T H.248.1 connection model within a Media Gateway. The Media Gateway is represented by a large dashed rectangle. Inside, there are three Contexts and one Null context, each enclosed in dashed rectangles. Each Context contains a Termination (RTP stream), an asterisk box, and a Termination (SCN bearer channel). The Null context contains a Termination (SCN bearer channel). Arrows indicate connections between the Media Gateway and the external environment. + +Media gateway + +Context + +Termination + +RTP stream + +\* + +Termination + +SCN bearer channel + +Context + +Termination + +RTP stream + +\* + +Null context + +Termination + +SCN bearer channel + +Context + +Termination + +RTP stream + +\* + +Termination + +SCN bearer channel + +H.248.1 v3(13)\_F04 + +Figure 4: Example of ITU-T H.248.1 connection model. The diagram shows a Media Gateway containing three Contexts and one Null context. Each Context contains a Termination (RTP stream), an asterisk box, and a Termination (SCN bearer channel). The Null context contains a Termination (SCN bearer channel). Arrows indicate connections between the Media Gateway and the external environment. + +Figure 4 – Example of ITU-T H.248.1 connection model + +The example in Figure 5 shows an example of one way to accomplish a call-waiting scenario in a decomposed access gateway, illustrating the relocation of a termination between contexts. Terminations T1 and T2 belong to Context C1 in a two-way audio call. A second audio call is waiting for T1 from Termination T3. T3 is alone in Context C2. T1 accepts the call from T3, placing T2 on hold. This action results in T1 moving into Context C2, as shown in Figure 6. + +![Figure 5: Example call waiting scenario/alerting applied to T1. The diagram shows a Media gateway containing two contexts, Context C1 and Context C2. Context C1 contains Termination T2 (RTP stream), a mixing node (asterisk), and Termination T1 (SCN bearer channel). Context C2 contains a mixing node (asterisk) and Termination T3 (SCN bearer channel). Arrows indicate external connections to T2, T1, and T3.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Media gateway + +H.248.1 v3(13)\_F05 + +Figure 5: Example call waiting scenario/alerting applied to T1. The diagram shows a Media gateway containing two contexts, Context C1 and Context C2. Context C1 contains Termination T2 (RTP stream), a mixing node (asterisk), and Termination T1 (SCN bearer channel). Context C2 contains a mixing node (asterisk) and Termination T3 (SCN bearer channel). Arrows indicate external connections to T2, T1, and T3. + +**Figure 5 – Example call waiting scenario/alerting applied to T1** + +![Figure 6: Example call waiting scenario/answer by T1. This diagram is similar to Figure 5, but with a key difference: a diagonal line connects the mixing node in Context C2 to Termination T1 in Context C1, indicating that T1 is being answered by the call waiting scenario.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +Media gateway + +H.248.1 v3(13)\_F06 + +Figure 6: Example call waiting scenario/answer by T1. This diagram is similar to Figure 5, but with a key difference: a diagonal line connects the mixing node in Context C2 to Termination T1 in Context C1, indicating that T1 is being answered by the call waiting scenario. + +**Figure 6 – Example call waiting scenario/answer by T1** + +## 6.1 Contexts + +A context is an association between a number of terminations. The context describes the topology (who hears/sees whom) and the media mixing and/or switching parameters if more than two terminations are involved in the association. + +There is a special context called the *NULL Context*. It contains terminations that are not present in any other context and therefore not associated to any other termination. Terminations in the NULL Context can have their parameters examined or modified, and may have events detected on them. + +In general, an Add Command is used to add terminations to contexts. If the MGC does not specify an existing context to which the termination is to be added, the MG creates a new context. A termination may be removed from a context with a Subtract Command, and a termination may be moved from one context to another with a Move Command. A termination shall exist in only one context at a time. + +The maximum number of terminations in a context is an MG property. Media gateways that offer only point-to-point connectivity might allow at most two terminations per context. Media gateways that support multipoint conferences might allow three or more terminations per context. + +### 6.1.1 Context attributes and descriptors + +The attributes of contexts are: + +- ContextID. +- The Topology Descriptor (who hears/sees whom). + +The topology of a context describes the flow of media between the terminations within a context. In contrast, the Mode Property of a termination ("SendOnly"/"RecvOnly"/...) describes the flow of the media at the egress/ingress of the media gateway. + +- The priority indicator is used for a context in order to provide the MG with information about a certain precedence handling for a context. The MGC can also use the priority indicator to control autonomously the traffic precedence in the MG in a smooth way in certain situations (e.g., restart), when a lot of contexts must be handled simultaneously. Priority 0 is the lowest priority and a priority of 15 is the highest priority. +- An indicator for an emergency call is also provided to allow a preference handling in the MG. +- An indicator for an IEPS call is provided to allow the features and techniques of e.g., [ITU-T E.106] and [ITU-T E.107] to be achieved. See [b-ITU-T H-Sup.9] for more information. +- A ContextAttribute Descriptor that enables extra context attributes to be defined by using the packages extension mechanism (see clause 7.1.19). + +In general, if a context attribute is completely omitted from an ITU-T H.248 action, the attribute of the corresponding context retains its prior value. + +### 6.1.2 Creating, deleting and modifying contexts + +The protocol can be used to (implicitly) create contexts and modify the parameter values of existing contexts. The protocol has commands to add terminations to contexts, subtract them from contexts, and to move terminations between contexts. Contexts are deleted implicitly when the last remaining termination is subtracted or moved out. + +## 6.2 Terminations + +A termination is a logical entity on an MG that sources and/or sinks media and/or control streams. A termination is described by a number of characterizing properties, which are grouped in a set of descriptors that are included in commands. Terminations have unique identities (TerminationIDs), assigned by the MG at the time of their creation. + +Terminations representing physical entities have a semi-permanent existence. For example, a termination representing a TDM channel might exist for as long as it is provisioned in the gateway. Terminations representing ephemeral information flows, such as RTP flows, would usually exist only for the duration of their use. + +Ephemeral terminations are created by means of an Add Command. They are destroyed by means of a Subtract Command. In contrast, when a physical termination is Added to or Subtracted from a context, it is taken from or to the NULL Context, respectively. + +Terminations may have signals applied to them (see clause 7.1.11). Terminations may be programmed to detect events, the occurrence of which can trigger notification messages to the MGC, or action by the MG. Statistics may be accumulated on a termination. Statistics are reported to the MGC upon request (by means of the AuditValue Command, see clause 7.2.5) and when the termination ceases to exist or is returned to the NULL Context due to a Subtract Command. + +Multimedia gateways may process multiplexed media streams. For example, [b-ITU-T H.221] describes a frame structure for multiple media streams multiplexed on a number of digital 64 kbit/s + +channels. Such a case is handled in the connection model in the following way. For every bearer channel that carries part of the multiplexed streams, there is a physical or ephemeral "bearer termination". The bearer terminations that source/sink the digital channels are connected to a separate termination called the "multiplexing termination". The multiplexing termination is an ephemeral termination representing a frame-oriented session. The Multiplex Descriptor for this termination describes the multiplex used (e.g., [b-ITU-T H.221] for an [b-ITU-T H.320] session) and indicates the order in which the contained digital channels are assembled into a frame. + +Multiplexing terminations may be cascades (e.g., [b-ITU-T H.226] multiplex of digital channels feeding into a [b-ITU-T H.223] multiplex supporting an [b-ITU-T H.324] session). + +The individual media streams carried in the session are described by Stream Descriptors on the multiplexing termination. These media streams can be associated with streams sourced/sunk by terminations in the context other than the bearer terminations supporting the multiplexing termination. Each bearer termination supports only a single data stream. These data streams do not appear explicitly as streams on the multiplexing termination and they are hidden from the rest of the context. + +Figures 7, 8, and 9 illustrate typical applications of the multiplexing termination and Multiplex Descriptor. + +![Diagram illustrating a multiplexed termination scenario (Circuit-to-packet).](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +The diagram, labeled 'Context', shows three circuits (Circuit 1, Circuit 2, and Circuit 3) on the left. Each circuit is connected to a bearer termination (Ta, Tb, and Tc respectively). Each bearer termination outputs a '(Stream 0)'. These streams are fed into a central vertical block labeled 'Multiplex - H.2xx'. Above this block is a circle labeled 'Tmux'. To the right of the 'Tmux' circle are 'MuxDescriptor', 'Stream1', and 'Stream2'. A dashed line connects 'Stream2' to a label 'Multiplexing termination (ephemeral)'. The 'Multiplex - H.2xx' block outputs two streams: 'StreamID 1 (audio)' and 'StreamID 2 (video)'. These streams are fed into a circle labeled 'Td'. To the right of 'Td' are 'StreamID 1 (audio packets)' and 'StreamID 2 (video packets)'. At the bottom right of the diagram is the text 'H.248.1 v3(13)\_F07'. At the bottom left, an arrow points to the circuits with the text 'Audio, video, and control signals are carried in frames spanning the circuits'. + +Diagram illustrating a multiplexed termination scenario (Circuit-to-packet). + +**Figure 7 – Multiplexed termination scenario – Circuit-to-packet** + +![Figure 8: Multiplexed termination scenario – Circuit-to-circuit. This diagram shows a 'Context' box containing two multiplexers, 'Tmux 1' and 'Tmux 2', both labeled 'Multiplex - H.2xx'. On the left, three circuits (Circuit 1, Circuit 2, Circuit 3) are connected to terminations 'Ta', 'Tb', and 'Tc' respectively. Each termination is connected to 'Tmux 1' via a signal labeled '(S0)'. Above 'Tmux 1' is a descriptor: 'Tmux1 MuxDescriptor (Type, TID list = Ta, Tb, Tc) StreamID1, 2'. Inside the context, 'Tmux 1' outputs two streams: 'StreamID = 1 (audio)' and 'StreamID = 2 (video)'. These streams are connected to 'Tmux 2'. On the right, 'Tmux 2' outputs to terminations 'Td', 'Te', and 'Tf', which are then connected to Circuit 4, Circuit 5, and Circuit 6 respectively. Each output from 'Tmux 2' is also labeled '(S0)'. Above 'Tmux 2' is a descriptor: 'Tmux2 MuxDescriptor (Type, TID list = Td, Te, Tf) StreamID1, 2'. The diagram is labeled 'H.248.1 v3(13)_F08' at the bottom right.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 8: Multiplexed termination scenario – Circuit-to-circuit. This diagram shows a 'Context' box containing two multiplexers, 'Tmux 1' and 'Tmux 2', both labeled 'Multiplex - H.2xx'. On the left, three circuits (Circuit 1, Circuit 2, Circuit 3) are connected to terminations 'Ta', 'Tb', and 'Tc' respectively. Each termination is connected to 'Tmux 1' via a signal labeled '(S0)'. Above 'Tmux 1' is a descriptor: 'Tmux1 MuxDescriptor (Type, TID list = Ta, Tb, Tc) StreamID1, 2'. Inside the context, 'Tmux 1' outputs two streams: 'StreamID = 1 (audio)' and 'StreamID = 2 (video)'. These streams are connected to 'Tmux 2'. On the right, 'Tmux 2' outputs to terminations 'Td', 'Te', and 'Tf', which are then connected to Circuit 4, Circuit 5, and Circuit 6 respectively. Each output from 'Tmux 2' is also labeled '(S0)'. Above 'Tmux 2' is a descriptor: 'Tmux2 MuxDescriptor (Type, TID list = Td, Te, Tf) StreamID1, 2'. The diagram is labeled 'H.248.1 v3(13)\_F08' at the bottom right. + +**Figure 8 – Multiplexed termination scenario – Circuit-to-circuit** + +![Figure 9: Multiplexed termination scenario – Single-to-multiple terminations. This diagram shows a 'Context' box containing one multiplexer, 'Tmux 1', labeled 'Multiplex - H.2xx'. On the left, 'Circuit 1' is connected to termination 'Ta', which is connected to 'Tmux 1' via a signal labeled '(S0)'. Above 'Tmux 1' is a descriptor: 'Tmux1 MuxDescriptor (Type, TID list = Ta) StreamID1, 2'. Inside the context, 'Tmux 1' outputs two streams: 'StreamID = 1 (audio)' and 'StreamID = 2 (video)'. The 'audio' stream is connected to termination 'Tb' via a signal labeled '(S0)', which then outputs to 'Stream (audio packets)'. The 'video' stream is connected to termination 'Tc' via a signal labeled '(S0)', which then outputs to 'Stream (video packets)'. The diagram is labeled 'H.248.1 v3(13)_F09' at the bottom right.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +Figure 9: Multiplexed termination scenario – Single-to-multiple terminations. This diagram shows a 'Context' box containing one multiplexer, 'Tmux 1', labeled 'Multiplex - H.2xx'. On the left, 'Circuit 1' is connected to termination 'Ta', which is connected to 'Tmux 1' via a signal labeled '(S0)'. Above 'Tmux 1' is a descriptor: 'Tmux1 MuxDescriptor (Type, TID list = Ta) StreamID1, 2'. Inside the context, 'Tmux 1' outputs two streams: 'StreamID = 1 (audio)' and 'StreamID = 2 (video)'. The 'audio' stream is connected to termination 'Tb' via a signal labeled '(S0)', which then outputs to 'Stream (audio packets)'. The 'video' stream is connected to termination 'Tc' via a signal labeled '(S0)', which then outputs to 'Stream (video packets)'. The diagram is labeled 'H.248.1 v3(13)\_F09' at the bottom right. + +**Figure 9 – Multiplexed termination scenario – Single-to-multiple terminations** + +Unlike the multiplexing terminations described in the previous paragraph the multiplexed bearer termination, which represent multiplexed bearers such as ATM AAL Type 2 bearers, carry no media streams. They are present strictly for the purpose of modeling the creation and destruction of the actual bearer. When a new multiplexed bearer is to be created, an ephemeral termination is created in a context established for this purpose. When the termination is subtracted, the multiplexed bearer is destroyed. + +### 6.2.1 Termination dynamics + +The protocol can be used to create new terminations and to modify property values of existing terminations. These modifications include the possibility of adding or removing events and/or signals. The termination properties, and events and signals are described in the ensuing subclauses. An MGC can only release/modify terminations and the resources that the termination represents which are in the NULL Context or which have been previously seized via, e.g., the Add Command. + +### 6.2.2 TerminationIDs + +Terminations are referenced by a TerminationID, which is an arbitrary schema chosen by the MG. + +TerminationIDs of physical terminations are provisioned in the Media Gateway. The TerminationIDs may be chosen to have structure. For instance, a TerminationID may consist of trunk group and a trunk within the group. + +A wildcarding mechanism using two types of wildcards can be used with TerminationIDs. The two wildcards are ALL and CHOOSE. The former is used to address multiple terminations at once, while the latter is used to indicate to a media gateway that it must select a termination satisfying the partially specified TerminationID. This allows, for instance, that an MGC instructs an MG to choose a circuit within a trunk group. + +TerminationIDs can also be specified in a list. The use of TerminationIDList is recommended for cases where a hierarchical TerminationID structure is not possible and it is not desired to send individual commands for each TerminationID. Both Root and non-Root TerminationIDs should not be contained in a single TerminationIDList. + +### 6.2.3 Packages + +Different types of gateways may implement terminations that have widely differing characteristics. Variations in terminations are accommodated in the protocol by allowing terminations to have optional properties, events, signals and statistics implemented by MGs. + +In order to achieve MG/MGC interoperability, such options are grouped into packages, and typically a termination realizes a set of such packages. More information on definition of packages can be found in clause 12. An MGC can audit a termination to determine which packages it realizes. + +Properties, events, signals and statistics defined in packages, as well as parameters to them, are referenced by identifiers (IDs). Identifiers are scoped. For each package, PropertyIDs, EventIDs, SignalIDs, StatisticIDs and ParameterIDs have unique name spaces and the same identifier may be used in each of them. Two PropertyIDs in different packages may also have the same identifier, etc. + +To support a particular package the MG must recognize all properties, signals, events and statistics defined in the package. It must also support all signal and event parameters. If the functionality behind these properties, signals, events and statistics is not implemented, the MG shall not return a syntax error or unknown ID error for any of these elements but should return error 501 "Not implemented". + +The MG may support a subset of the values listed in a package for a particular property or parameter. If an unsupported value is specified by the MGC, the MG shall return error 501 "Not implemented". + +When packages are extended, the properties, events, signals and statistics defined in the base package can be referred to using either the extended package name or the base package name. For example, if Package A defines Event e1, and Package B extends Package A, then B/e1 is an event for a termination implementing Package B. By definition, the MG must also implement the base package, but it is optional to publish the base package as an allowed interface. If it does publish A, then A would be reported on the Packages Descriptor in AuditValue as well as B, and Event A/e1 would be available on a termination. If the MG does not publish A, then only B/e1 would be available. If published through AuditValue, A/e1 and B/e1 are the same event. + +For improved interoperability and backward compatibility, an MG may publish all packages supported by its terminations, including base packages from which extended packages are derived. An exception to this is in cases where the base packages are expressly defined as "Designed to be extended only". + +In the case that the MG publishes the base PackageIDs in response to a Packages Descriptor Audit, it will also respond to a wildcarded PackageID Audit with the PackageID of the ITU-T H.248 Package Element where the element was originally defined. + +In the case that the MG publishes only the extended PackageID in response to a Packages Descriptor Audit, the MG will respond to a wildcarded PackageID Audit using the extended ITU-T H.248 PackageIDs. + +NOTE – Whilst a Subtract request does not explicitly request an AuditValue.req of Statistics with a wildcarded PackageID, it is implicit in the command. Similarly, an audit of a complete descriptor is equivalent to an audit with a wildcarded PackageID. Thus, the procedure described above will be used in both cases. + +### 6.2.4 Termination properties and descriptors + +Terminations have properties. The properties have unique PropertyIDs. Most properties have default values, which are explicitly defined in this protocol specification or in a package (see clause 12) or set by provisioning. If not provisioned otherwise, the properties in all descriptors except TerminationState and LocalControl default to empty/"no value" when a termination is first created or returned to the NULL Context. When a termination is first created or returned to the NULL Context, this state represents an "idle" line, trunk or other entity. The default contents of the two exceptions are described in clauses 7.1.5 and 7.1.7. + +The provisioning of a property value in the MG will override any default value, be it supplied in this protocol specification or in a package. Therefore, if it is essential for the MGC to have full control over the property values of a termination, it should supply explicit values when adding the termination to a context. Alternatively, for a physical termination the MGC can determine any provisioned property values by auditing the termination while it is in the NULL Context. + +There are a number of common properties for terminations and properties specific to media streams. The common properties are also called the TerminationState properties. For each media stream, there are local properties and properties of the received and transmitted flows. + +Properties not included in the base protocol are defined in packages. These properties are referred to by a name consisting of the package name and a PropertyID. Most properties have default values described in the package description. Properties may be read-only or read/write. The possible values of a property may be audited, as can their current values. For properties that are read/write, the MGC can set their values. A property may be declared as "global" which has a single value shared by all terminations realizing the package. Related properties are grouped into descriptors for convenience. + +When a termination is added to a context, the value of its read/write properties can be set by including the appropriate descriptors as parameters to the Add Command. Similarly, a property of a termination in a context may have its value changed by the Modify Command. Properties may also have their values changed when a termination is moved from one context to another as a result of a Move Command. In some cases, descriptors are returned as output from a command. + +Setting properties on different terminations in the same context implicitly instructs the MG to perform certain functions. For example: if a [b-ITU-T G.711] codec is set on Termination A and a [b-ITU-T G.729] codec is set on Termination B, then the MG will activate a transcoding function as soon as a media flow is enabled between the two terminations (i.e., by setting the Mode Property to a state other than "Inactive" at each termination). + +NOTE – To avoid unnecessary activation of MG resources, the MGC should set the Mode Property to "Inactive" for a given termination and stream until the properties to be used for that stream have been determined. + +In general, if a descriptor is completely omitted from one of the aforementioned commands, the properties in that descriptor retain their prior values for the termination(s) upon which the command acts. On the other hand, if some read/write properties are omitted from a descriptor in a command (i.e., the descriptor is only partially specified), those properties will be reset to their default values for the termination(s) upon which the command acts, unless the package specifies other behaviour. For more details, see clause 7.1 dealing with the individual descriptors. + +The above behaviour applies equally to signals and events and their respective parameters. The provisioning of Events Descriptors would include the RequestID to use and any parameters of the included events. Any provisioning in the MG with respect to Events Descriptors should be duplicated in the MGC to avoid error responses to Notify Commands from the MG. + +The following table lists all of the possible descriptors and their use. Not all descriptors are legal as input or output parameters to every command. + +| Descriptor name | Description | +|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| Modem | Identifies modem type and properties when applicable. (Note) | +| Mux | Describes multiplex type for multimedia terminations (e.g., [b-ITU-T H.221], [b-ITU-T H.223], [ITU-T H.225.0]) and terminations forming the input mux. | +| Media | A list of media stream specifications (see clause 7.1.4). | +| TerminationState | Properties of a termination (which can be defined in packages) that are not stream specific. | +| Stream | A list of Remote/Local/LocalControl Descriptors for a single stream. | +| Local | Contains properties that specify the media flows that the MG receives from the remote entity. | +| Remote | Contains properties that specify the media flows that the MG sends to the remote entity. | +| LocalControl | Contains properties (which can be defined in packages) that are of interest between the MG and the MGC. | +| Events | Describes events to be detected by the MG and what to do when an event is detected. | +| EventBuffer | Describes events to be detected by the MG when event buffering is active. | +| Signals | Describes signals (see clause 7.1.11) applied to terminations. | +| Audit | In Audit commands, identifies which information is desired. | +| Packages | In AuditValue, returns a list of packages realized by the termination. | +| DigitMap | Defines patterns against which sequences of a specified set of events are to be matched so they can be reported as a group rather than singly. | +| ServiceChange | In ServiceChange, what, why ServiceChange occurred, etc. | +| ObservedEvents | In Notify or AuditValue, report of events observed. | +| Statistics | In Subtract and Audit, report of statistics kept on a termination or stream. | +| Topology | Specifies flow directions between terminations in a context. | +| ContextAttribute | Contains properties (which can be defined in packages) that affect the context as a whole. | +| Error | Contains an Error Code and optionally error text; it may occur in command replies and in Notify requests. | +| NOTE – Modem Descriptor has been deprecated in Recommendation ITU-T H.248.1 version 2 (05/2002). | | + +### 6.2.5 Root Termination + +Occasionally, a command must refer to the gateway as an entity in itself, rather than a termination within it. A special TerminationID, "Root" is reserved for this purpose. Packages may be defined on Root. Root thus may have properties, events, signals and statistics. Accordingly, the Root TerminationID may appear in: + +- a Modify Command – to change a property, send a signal or set an event; +- a Notify Command – to report an event; +- an AuditValue Command – to examine the values of properties and statistics implemented on Root; +- an AuditCapability Command – to determine what properties of Root are implemented; +- a ServiceChange – to declare the entire gateway in or out of service. + +Any other use of the Root TerminationID is an error. Error Code 410 ("Incorrect identifier") shall be returned in these cases. + +## 6.3 Wildcarding principles + +This clause specifies the behaviour for wildcarding ContextIDs and TerminationIDs that shall be applied to all commands. In processing these commands two forms of wildcarding must be considered: + +- 1) Context wildcarding; +- 2) Termination wildcarding. + +For the purposes of the wildcarding procedures, a TerminationIDList consisting of more than one TerminationID is considered a wildcarded TerminationID. When executing a transaction that contains wildcarded contexts and optionally wildcarded terminations, all commands in the transaction are executed in order for a particular instance of ContextID before moving to a subsequent ContextID instance. In the case that there are multiple commands in a transaction, only when the TerminationID (wildcarded or specific) specified in the first command matches a specific instance of a ContextID are subsequent commands in the transaction executed. If a TerminationID (wildcarded or specific) of the subsequent command(s) in that transaction does not match the specific ContextID instance, then Error Code 431 ("No TerminationID matched a wildcard") is returned and processing of subsequent instances of the wildcard ContextID are stopped unless the command that generated the error is marked optional. + +The execution of particular wildcard combinations is discussed below. + +### 6.3.1 ContextID specific with TerminationID wildcarded + +In the case where the ContextID is specific, when ALL is used in the TerminationID of a command, the effect is identical to repeating the command with each of the matching TerminationIDs. The use of ALL does not address the Root termination. Since each of these commands may generate a response, the size of the entire response may be large. Thus, if the wildcard matches more than one TerminationID in the context, all possible matches are attempted, with results reported for each one. If none of the terminations referenced by the wildcarded TerminationID are in the specific context, then Error Code 431 ("No TerminationID matched a wildcard") is returned. No errors are returned for individual terminations specified by the wildcarded TerminationID that are not in the specified context. + +For example: Assume that a gateway has four terminations: t1/1, t1/2, t2/1 and t2/2. Assume that Context 1 has t1/1 and t2/1 in it and that Context 2 has t1/2 and t2/2 in it. + +The command: + +Context=1 {Command=t1/\* {Descriptor/s}} + +returns: + +Context=1 {Command=t1/1 {Descriptor/s}} + +### 6.3.2 ContextID wildcarded (ALL) with TerminationID specific + +In the case where the ContextID is wildcarded (i.e., ContextID = ALL) and the TerminationID is fully specified, the effect is identical to a command specifying the non-NULL context that contains the specified termination. Thus, a search must be made to find the context and only one instance of the command is executed. No errors are reported for contexts that do not contain the specified termination. If the termination is not contained in any (non-NULL) context, then Error Code 435 ("TerminationID is not in specified context") is returned, though Error Code 431 ("No TerminationID matched a wildcard") may be returned in order to maintain backward compatibility. If there are no contexts other than NULL in existence, Error Code 411 ("The transaction refers to an unknown ContextID") is returned. Use of this form of action rather than one specifying the ContextID is discouraged but may be useful, for example in correcting conflicting state between MG and MGC. + +For example: Taking the above gateway configuration, the command: + +Context=\* {Command=t1/1 {Descriptor/s}} + +returns: + +Context=1 {Command=t1/1 {Descriptor/s}} + +### 6.3.3 ContextID wildcarded (ALL) with TerminationID wildcarded + +In the case where the ContextID is wildcarded (i.e., ContextID = ALL) and the TerminationID is wildcarded, the effect is identical to repeating the command with each of the TerminationIDs matching the wildcard for each non-NULL context that contains one or more of those matching TerminationIDs. Thus if the wildcard matches more than one TerminationID in the specific instance of the wildcarded ContextID, all possible matches are attempted, with results reported for each one. No errors are reported for contexts that do not contain a termination matching the wildcarded TerminationID. No errors are returned for individual terminations specified in the wildcarded TerminationID that are not in a specific instance of the wildcarded ContextID. If there are no matches to the wildcarded ContextID and TerminationID, then Error Code 431 ("No TerminationID matched a wildcard") is returned. + +For example: Taking the above gateway configuration, the command: + +Context=\* {Command=t1/\* {Descriptor/s}} + +returns: + +Context=1 {Command=t1/1 {Descriptor/s}} + +Context=2 {Command=t1/2 {Descriptor/s}} + +In the case that multiple commands are contained in a wildcarded TerminationID and/or wildcarded ContextID request, then if the first command does not match the first ContextID and TerminationID instance, then the subsequent command in the request will not be executed for that instance. + +### 6.3.4 Wildcarded responses + +If individual responses are not required, a wildcard response may be requested. In such a case, a single response is generated, which contains the UNION of all of the individual responses which otherwise would have been generated, with duplicate values suppressed. For instance, given Termination Ta with Properties p1=a, p2=b and Termination Tb with Properties p2=c, p3=d, a UNION response would consist of a wildcarded TerminationID and the sequence of Properties + +p1=a, p2=b,c and p3=d. Wildcard responses may be particularly useful in the Audit commands. If a wildcard UNION response is used in conjunction with a wildcarded context, then a single response is sent with the UNION of all the individual terminations referenced by the TerminationID. The response would contain Context=ALL, a wildcarded TerminationID and the sequence of properties. + +If an error occurs during the execution of a wildcarded request that specifies a wildcarded response, special handling is required to provide useful information about the error(s) while still maintaining a modest sized response. When a wildcarded response is requested, all instances (as specified above) of the command shall be executed even if one or more result in errors, but later commands in the transaction will not be executed (unless optional was specified). Multiple command responses shall be returned for the command that encountered the error. The first command response shall be the normal wildcard response containing the UNION of responses for those commands that succeeded. If none of them succeeded, the UNION shall be empty. Additional command responses for each TerminationID that failed shall be returned with the appropriate Error Descriptor. + +For example, the command: + +Context=\* {Command=t1/\* {Descriptor/s}} + +Response to an error: + +Context=\* {Command=t1/\* {Union response descriptors}}, + +Command=t1/3 {Error=errorcode}} + +The encoding of the wildcarding mechanism is detailed in Annexes A and B. + +# 7 Commands + +The protocol provides commands for manipulating the logical entities of the protocol connection model, contexts and terminations. Commands provide control at the finest level of granularity supported by the protocol. For example, commands exist to add terminations to a context, modify terminations, subtract terminations from a context, and audit properties of contexts or terminations. Commands provide for complete control of the properties of contexts and terminations. This includes specifying which events a termination is to report, which signals/actions are to be applied to a termination and specifying the topology of a context (who hears/sees whom). + +Most commands are for the specific use of the Media Gateway Controller as command initiator in controlling Media Gateways as command responders. The exceptions are the Notify and ServiceChange Commands: Notify is sent from Media Gateway to Media Gateway Controller, and ServiceChange may be sent by either entity. Below is an overview of the commands; they are explained in more detail in clause 7.2. + +- 1) Add: The Add Command adds a termination to a context. The Add Command on the first termination in a context is used to create a context. +- 2) Modify: The Modify Command modifies the properties, events and signals of a termination. +- 3) Subtract: The Subtract Command disconnects a termination from its context and returns statistics on the termination's participation in the context. The Subtract Command on the last termination in a context deletes the context. +- 4) Move: The Move Command atomically moves a termination to another context. +- 5) AuditValue: The AuditValue Command returns the current state of properties, events, signals and statistics of terminations. +- 6) AuditCapability: The AuditCapability Command returns all the possible values for termination properties, events and signals allowed by the Media Gateway. +- 7) Notify: The Notify Command allows the Media Gateway to inform the Media Gateway Controller of the occurrence of events in the Media Gateway. + +- 8) **ServiceChange:** The ServiceChange Command allows the Media Gateway to notify the Media Gateway Controller that a termination or group of terminations is about to be taken out of service or has just been returned to service. ServiceChange is also used by the MG to announce its availability to an MGC (registration), and to notify the MGC of impending or completed restart of the MG. The MGC may announce a handover to the MG by sending it a ServiceChange Command. The MGC may also use ServiceChange to instruct the MG to take a termination or group of terminations in or out of service. + +These commands are detailed in clauses 7.2.1 through 7.2.8. + +## 7.1 Descriptors + +The parameters to a command are termed descriptors. A descriptor consists of a name and a list of items. Some items may have values. Many commands share common descriptors. This subclause enumerates these descriptors. Descriptors may be returned as output from a command. Descriptors shall be returned in the order that they were received. In any such return of descriptor contents, an empty descriptor is represented by its name unaccompanied by any list. Parameters and parameter usage specific to a given command type are described in the subclause that describes the command. + +### 7.1.1 Specifying parameters + +Command parameters are structured into a number of descriptors. In general, the text format of descriptors is `DescriptorName={parm=value, parm=value...}`. + +Parameters may be fully specified, overspecified or underspecified: + +- 1) Fully specified parameters have a single, unambiguous value that the command initiator is instructing the command responder to use for the specified parameter. +- 2) Underspecified parameters, using the **CHOOSE** value, allow the command responder to choose any value it can support. +- 3) Overspecified parameters have a list of potential values. The list order specifies the command initiator's order of preference of selection. The command responder chooses one value from the offered list and returns that value to the command initiator. + +If a required descriptor other than the Audit Descriptor is unspecified (i.e., entirely absent) from a command, the previous values set in that descriptor for that termination, if any, are retained. In commands other than Subtract, a missing Audit Descriptor is equivalent to an empty Audit Descriptor. The behaviour of the MG with respect to unspecified parameters within a descriptor varies with the descriptor concerned, as indicated in succeeding subclauses. Whenever a parameter is underspecified or overspecified, the descriptor containing the value chosen by the responder is included as output from the command. + +Each command specifies the TerminationID the command operates on. This TerminationID may be "wildcarded". When the TerminationID of a command is wildcarded, the effect shall be as if the command was repeated with each of the TerminationIDs matched. + +### 7.1.2 Modem Descriptor + +The Modem Descriptor specifies the modem type and parameters, if any, required for use in, e.g., [b-ITU-T H.324] and text conversation. The descriptor includes the following modem types: ITU-T V.18, ITU-T V.22, ITU-T V.22 *bis*, ITU-T V.32, ITU-T V.32 *bis*, ITU-T V.34, ITU-T V.90, ITU-T V.91, Synchronous ISDN, and allows for extensions. By default, no Modem Descriptor is present in a termination. + +Use of the Modem Descriptor is deprecated in Recommendation ITU-T H.248.1 Version 2 (05/2002) and subsequent versions. This means that the Modem Descriptor shall not be included as part of transmitted content and, if received, shall either be ignored or processed at the option of the + +implementation. Modem type is to be specified as an attribute of data streams in the Local Descriptor and the Remote Descriptor. + +### 7.1.3 Multiplex Descriptor + +In multimedia calls, a number of media streams are carried on a (possibly different) number of bearers. The Multiplex Descriptor associates the media and the bearers. The descriptor includes the multiplex type: + +- H.221; +- H.223; +- H.226; +- V.76; +- $N \times 64K$ ; +- possible extensions, + +and a set of TerminationIDs representing the multiplexed bearers, in order. For example: + +Mux = H.221{MyT3/1/2, MyT3/2/13, MyT3/3/6, MyT3/21/22} + +The $N \times 64K$ multiplex type implements the $N \times 64K$ service (e.g., as defined by [ITU-T Q.931] Information Transfer Rate or [ITU-T Q.763] Transmission Medium Requirement). On the context side, it supports a single stream of wideband data. When a bearer termination is added implicitly to a context as a result of the creation of an $N \times 64K$ multiplexing termination, the Stream Descriptor for the bearer termination shall take on the same values as the Stream Descriptor defined for the multiplex termination, except that the bearer termination bandwidth shall be 64 kbit/s. + +### 7.1.4 Media Descriptor + +The Media Descriptor specifies the parameters for all the media streams. These parameters are structured into two descriptors: a TerminationState Descriptor, which specifies the properties of a termination that are not stream dependent, and one or more Stream Descriptors each of which describes a single media stream. + +A stream is identified by a StreamID. The StreamID shall be in the range of 1 to 65535. The StreamID is used to link the streams in a context that belong together. Multiple streams exiting a termination shall be synchronized with each other. Within the Stream Descriptor, there are up to four subsidiary descriptors: LocalControl, Local, Remote and Statistics. The relationship between these descriptors is thus: + +``` +Media Descriptor + TerminationState Descriptor + Stream Descriptor + LocalControl Descriptor + Local Descriptor + Remote Descriptor + Statistics Descriptor +``` + +As a convenience, the LocalControl, Local, Remote or Statistics Descriptors may be included in the Media Descriptor without an enclosing Stream Descriptor. In this case, the StreamID is assumed to be one. + +### 7.1.5 TerminationState Descriptor + +The TerminationState Descriptor contains the ServiceStates Property, the EventBufferControl Property and properties of a termination (defined in packages) that are not stream specific. + +The ServiceStates Property describes the overall state of the termination (not stream specific). A termination can be in one of the following states: "Test", "OutOfService", or "InService". The "Test" state indicates that the termination is being tested. The state "OutOfService" indicates that the termination cannot be used for traffic. The state "InService" indicates that a termination can be used or is being used for normal traffic. "InService" is the default state. + +Values assigned to properties may be simple values (integer/string/enumeration) or may be underspecified, where more than one value is supplied and the MG may make a choice: + +- Alternative values: multiple values in a list, one of which must be selected; +- Ranges: minimum and maximum values, a value between min and max must be selected, boundary values included; +- Greater Than/Less Than: value must be greater/less than specified value; +- CHOOSE Wildcard: the MG chooses from the allowed values for the property. + +The EventBufferControl Property specifies whether events are buffered following detection of an event in the Events Descriptor, or processed immediately. See 7.1.9 for details. + +#### 7.1.5.1 TerminationState properties + +##### 7.1.5.1.1 ServiceStates + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | ServiceStates | +| Description: | The value of this property indicates the current service state of the termination. | +| Type: | Enumeration | +| Possible values: | InService: The termination is in-service and functioning normally.
OutOfService: The termination is out-of-service and not available for traffic.
Test: The termination is undergoing testing. | +| Default: | InService | +| Defined in: | TerminationState | +| Characteristics: | Read/Write | + +##### 7.1.5.1.2 EventBufferControl + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | EventBufferControl | +| Description: | Specifies whether events are buffered following detection of an event in the Events Descriptor, or processed immediately. See clause 7.1.9. | +| Type: | Enumeration | +| Possible values: | LockStep: Events are buffered and processed per clause 7.1.9.
OFF: Events are processed immediately. | +| Default: | OFF | +| Defined in: | TerminationState | +| Characteristics: | Read/Write | + +### 7.1.6 Stream Descriptor + +A Stream Descriptor specifies the parameters of a single bidirectional stream. These parameters are structured into three descriptors: one that contains termination properties specific to a stream and one each for local and remote flows. The Stream Descriptor includes a StreamID which identifies the stream. Streams are created by specifying a new StreamID on one of the terminations in a context. A stream is deleted by setting empty Local and Remote Descriptors for the stream with ReserveGroup and ReserveValue in LocalControl set to "False" on all terminations in the context that previously supported that stream. + +StreamIDs are of local significance between MGC and MG and they are assigned by the MGC. Within a context, StreamID is a means by which to indicate which media flows are interconnected: streams with the same StreamID are connected. + +If a termination is moved from one context to another, the effect on the context to which the termination is moved is the same as in the case that a new termination were added with the same StreamIDs as the moved termination. + +### 7.1.7 LocalControl Descriptor + +#### a) Overview + +The LocalControl Descriptor contains the Mode Property, the ReserveGroup and ReserveValue Properties and properties of a termination (defined in packages) that are stream specific, and are of interest between the MG and the MGC. Values of properties may be specified as in clause 7.1.1. + +#### b) Mode Property (for directionality control) + +The allowed values for the Mode Property are "SendOnly", "RecvOnly", "SendRecv", "Inactive" and "LoopBack". "SendOnly", "RecvOnly" and "LoopBack" are with respect to the exterior of the context, so that, for example, a stream set to mode = "SendOnly" does not pass received media into the context. When a stream is set to "LoopBack" on a termination, media received (Local Descriptor) on the termination will be looped back to the sending side (Remote Descriptor) of the termination and no media is passed between that termination and other terminations in the context. The looped back media shall be sent according to the Remote Descriptor. The default value for the Mode Property is "Inactive". Signals and events are not affected by the Mode Property. Statistics may or may not be affected by the Mode property depending on the semantic of the statistic. For example: if the Mode was set to "SendOnly" and the Octet Received Statistic was set, then the statistic would not be affected. If the Octet Sent Statistic was set, then it would be affected by the mode. The LocalControl Mode Property takes precedence over any mode specified in the Local and Remote Descriptors. However, duplication and use of mode information in the SDP should be avoided. Due to the default of LocalControl Mode Property being "Inactive", if mode information was added to the Local and Remote Descriptor SDP and the LocalControl Mode was not explicitly sent, the effective mode would still be inactive. + +#### c) Reserve Properties (for resource handling control) + +The boolean-valued Reserve Properties, ReserveValue and ReserveGroup, of a termination indicate what the MG is expected to do when it receives a Local and/or Remote Descriptor. + +If the value of a Reserve Property is "True", the MG shall reserve resources for all alternatives specified in the Local and/or Remote Descriptors for which it currently has resources available. It shall respond with the alternatives for which it reserves resources. If it cannot support any of the alternatives, it shall respond with a reply to the MGC that contains empty Local and/or Remote Descriptors. If media begins to flow while more than a single alternative is reserved, media packets may be sent or received on any of the alternatives and must be processed, although only a single alternative may be active at any given time. + +If the value of a Reserve Property is False, the MG shall choose one of the alternatives specified in the Local Descriptor (if present) and one of the alternatives specified in the Remote Descriptor (if present). If the MG has not yet reserved resources to support the selected alternative, it shall reserve the resources. If, on the other hand, it already reserved resources for the termination addressed (because of a prior exchange with ReserveValue and/or ReserveGroup equal to "True"), it shall release any excess resources it reserved previously. Finally, the MG shall send a reply to the MGC containing the alternatives for the Local and/or Remote Descriptor that it selected. If the MG does not have sufficient resources to support any of the alternatives specified, it shall respond with Error Code 510 ("Insufficient resources"). + +The default value of ReserveValue and ReserveGroup is "False". More information on the use of the two Reserve Properties is provided in clause 7.1.8. + +#### **d) Descriptor usage** + +A new setting of the LocalControl Descriptor completely replaces the previous setting of that descriptor in the MG. Thus, to retain information from the previous setting, the MGC must include that information in the new setting. If the MGC wishes to delete some information from the existing descriptor, it merely resends the descriptor (in a Modify Command) with the unwanted information stripped out. + +NOTE – The Mode Property is also known as "StreamMode" in the encoding definitions in Annexes A and B. These terms are interchangeable within ITU-T H.248. + +#### **7.1.7.1 LocalControl Properties** + +##### **7.1.7.1.1 StreamMode** + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | StreamMode | +| Description: | The value of this property indicates the current service state of the termination. | +| Type: | Enumeration | +| Possible values: |

Inactive: The termination does not pass any media for the stream.

SendOnly: The termination passes media for the stream from the interior to the exterior of the context.

RecvOnly: The termination passes media for the stream from the exterior to the interior of the context.

SendRecv: The termination passes media for the stream both into and out of the context.

LoopBack: The termination loops received media for the stream back to the sender.

NOTE – The term "media" underlines that the StreamMode settings only affect the "media flow" component(s) of the ITU-T H.248 Stream, but not potential "control flow" component(s) (like, e.g., in case of an ITU-T H.248 Stream, carrying a RTP session with an RTP media flow and RTCP control component). It may be noted that the separation of media and control components is consistent with the SDP understanding of "media streams", see [b-IETF RFC 4566].

| +| Default: | Inactive | +| Defined in: | LocalControl | +| Characteristics: | Read/Write | + +##### 7.1.7.1.2 ReserveGroup + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | ReserveGroup | +| Description: |

Specifies whether the MG should reserve the resources to support a single media group or as many media groups as it can, as they are defined in the Local and Remote Descriptors. See clause 7.1.8.

NOTE – The term "media group" designates the content of the ASN.1 production "PropertyGroup" (see Annex A) in the binary encoding, or an individual SDP session description in the text encoding.

| +| Type: | Boolean | +| Possible values: |

True: The MG is to reserve all possible media groups indicated in the Local and Remote Descriptors.

False: The MG is to reserve a single media group from each of the Local and the Remote Descriptors according to the policies described in clause 7.1.8.

| +| Default: | False | +| Defined in: | LocalControl | +| Characteristics: | Read/Write | + +##### 7.1.7.1.3 ReserveValue + +| | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | ReserveValue | +| Description: |

Specifies whether the MG should reserve the resources to support a single set of property values (e.g., a single codec and its associated attributes) or as many such sets as it can, as they are defined in the Local and Remote Descriptors. See clause 7.1.8.

| +| Type: | Boolean | +| Possible values: |

True: The MG is to reserve resources to serve as many as possible of the sets of property values indicated in the selected media group (if ReserveGroup is False) or in each media group (if ReserveGroup is True) in the Local and Remote Descriptors.

False: The MG is to reserve a single set of property values from those indicated in the selected media group (if ReserveGroup is False) or in each media group (if ReserveGroup is True) in the Local and Remote Descriptors.

| + +NOTE – A single set of property values may consist of a single media type (e.g., audio or video) related media format complemented by a list of supplementary media formats. Supplementary media formats are for example: + +- Comfort noise ([b-IETF RFC 3389]), +- RTP Payload for DTMF digits, telephony tones and telephony signals ([b-IETF RFC 4733]), +- Voiceband data (VBD) services (according to [b-ITU-T V.152]), +- or other auxiliary media (e.g., inband signalling) associated to the main media flow. + +**Default:** False +**Defined in:** LocalControl +**Characteristics:** Read/Write + +### 7.1.8 Local and Remote Descriptors + +#### 7.1.8.1 Syntax for Local Descriptors and Remote Descriptors + +The MGC uses Local and Remote Descriptors to reserve and commit MG resources for media decoding and encoding for the given stream(s) and termination to which they apply. The MG includes these descriptors in its response to indicate what it is actually prepared to support. The MG shall include additional properties and their values in its response if these properties are mandatory yet not present in the requests made by the MGC (e.g., by specifying detailed video encoding parameters where the MGC only specified the payload type). + +To avoid ambiguity when requesting the MG to reserve and commit resources, the MGC should supply as much information as needed when using underspecification (i.e., CHOOSE) so that the MG can make an unambiguous selection. For example when using CHOOSE without specifying the required application type (e.g., "media name" in case of SDP encoding), further information may be needed (e.g., attribute lines in case of SDP encoding). + +Local refers to the media received by the MG and Remote refers to the media sent by the MG. + +##### 7.1.8.1.1 Specific syntax for ITU-T H.248 text encoding + +###### 7.1.8.1.1.1 Rules + +When text encoding the protocol, the descriptors consist of session descriptions as defined in SDP ([IETF RFC 2327]). In session descriptions sent from the MG to the MGC, the SDP must comply with [IETF RFC 2327]. In session descriptions sent from the MGC to the MG, the following exceptions to the syntax of [IETF RFC 2327] are allowed: + +- the "s = ", "t = " and "o = " lines are optional; +- the use of CHOOSE is allowed in place of a single parameter value; and +- the use of alternatives is allowed in place of a single parameter value. + +A Stream Descriptor specifies a single bidirectional media stream, a session description consists of a session-level section followed by a media-level section and so a single session description must not include more than one media description ("m = " line). A session description should not contain duplicate SDP lines on session-level and media-level. If duplication occurs the media level line takes precedence. + +A Stream Descriptor may contain additional session descriptions as alternatives. Each media stream for a termination must appear in distinct Stream Descriptors. When multiple session descriptions are provided in one descriptor, the "v = " lines are required as delimiters; otherwise they are optional in session descriptions sent to the MG. Implementations shall accept session descriptions that are fully conformant to [IETF RFC 2327] according to the above restrictions. + +If an MG does not understand the SDP provided, rather than ignoring that piece of SDP, an appropriate error response shall be provided. + +###### 7.1.8.1.1.2 Summary – ITU-T H.248 usage of SDP + +Figure 10 provides an overview of the structure of the ITU-T H.248 Media Descriptor. SDP is used, within the ITU-T H.248 Stream Descriptor, in the Local Descriptor (LD) and in the Remote Descriptor (RD). There are thus separate SDP specifications for ingress traffic (provided by the ITU-T H.248 LD) and egress traffic (provided by the ITU-T H.248 RD). The (SDP) media description within that SDP block is reflected in the LD and RD and determines the ITU-T H.248 media gateway behaviour. + +![Figure 10: Overview Structure of ITU-T H.248 Media Descriptor. The diagram shows the hierarchy of the Media Descriptor and its relationship to SDP specifications.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +The diagram illustrates the structure of the ITU-T H.248 Media Descriptor (in ITU-T H.248 commands) and its relationship to SDP specifications. + +**ITU-T H.248 Media Descriptor (in ITU-T H.248 commands)** + +- Part 1: TerminationState descriptor +- Part 2: Stream descriptor + - Part 2.1: LocalControl descriptor + - Part 2.2: Local Descriptor ("LD") + - SDP specification for *Ingress* Traffic + - ... + - Part 2.3: Remote Descriptor ("RD") + - SDP specification for *Egress* Traffic + - ... + - Part 2.4: Statistics Descriptor + +**Conceptual difference, but same objective! +ITU-T H.248 "Media Descriptor" vs SDP "Media Description"** + +**SDP specification** + +- Part 1: Session description (restricted in ITU-T H.248!) + - v = ... [used as 'separator element'] + - o = ... + - s = ... +- Part 2: Time description (restricted in ITU-T H.248!) + - t = ... +- Part 3: Media description + - c = ... + - m = ... + - b = ... + - k = \* ... + - a = ... + +Figure 10: Overview Structure of ITU-T H.248 Media Descriptor. The diagram shows the hierarchy of the Media Descriptor and its relationship to SDP specifications. + +NOTE – An ITU-T H.248 profile description (see sections 6.15 and 6.16 in Appendix III) may also provide information regarding the support of SDP lines. + +H.248.1 v3(13)\_F10 + +**Figure 10 – Overview Structure of ITU-T H.248 Media Descriptor +(ITU-T H.248 "Media Descriptor" vs SDP "Media Description")** + +##### 7.1.8.1.2 Specific syntax for ITU-T H.248 binary encoding + +When binary encoding the protocol, the descriptor consists of groups of properties (tag-value pairs) as specified in Annex C. Each such group may contain the parameters of a session description. + +#### 7.1.8.2 Semantics for Local Descriptor and Remote Descriptor + +Below, the semantics of the Local and Remote Descriptors are specified in detail. The specification consists of two parts. The first part specifies the interpretation of the contents of the descriptor. The second part specifies the actions the MG must take upon receiving the Local and Remote Descriptors. The actions to be taken by the MG depend on the values of the ReserveValue and ReserveGroup Properties of the LocalControl Descriptor. + +##### 7.1.8.2.1 Specification depth of Local Descriptor/Remote Descriptor content + +Either the Local or the Remote Descriptor or both may be: + +- unspecified (i.e., absent); +- empty; +- underspecified through use of CHOOSE in a property value; +- fully specified; or +- overspecified through presentation of multiple groups of properties and possibly multiple property values in one or more of these groups. + +##### 7.1.8.2.2 Interpretation of Local Descriptor/Remote Descriptor by the MG + +Where the descriptors have been passed from the MGC to the MG, they are interpreted according to the rules given in clause 7.1.1, with the following additional comments for clarification: + +- a) An unspecified Local or Remote Descriptor is considered to be a missing mandatory parameter. It requires the MG to use whatever was last specified for that descriptor. It is possible that there was no previously specified value, in which case the descriptor concerned is ignored in further processing of the command. +- b) An empty Local (Remote) Descriptor in a message from the MGC signifies a request to release any resources reserved for the media flow received (sent). +- c) If multiple groups of properties are present in a Local or Remote Descriptor or multiple values within a group, the order of preference is descending. +- d) Underspecified or overspecified properties within a group of properties sent by the MGC are requests for the MG to choose one or more values which it can support for each of those properties. In case of an overspecified property, the list of values is in descending order of preference. + +##### 7.1.8.2.3 Resource reservation rules for ReserveValue and ReserveGroup properties + +Subject to the above rules, subsequent action depends on the values of the ReserveValue and ReserveGroup Properties in LocalControl. + +###### 7.1.8.2.3.1 ReserveValue = "False" AND ReserveGroup = "True" + +If ReserveGroup is "True", the MG reserves the resources required to support as many as possible of the requested property group alternatives that it can currently support. + +###### 7.1.8.2.3.2 ReserveValue = "True" AND ReserveGroup = "False" + +If ReserveValue is "True", the MG reserves the resources required to support as many as possible of the requested property value alternatives that it can currently support. + +NOTE – If a Local or Remote Descriptor contains multiple groups of properties, and ReserveGroup is "True", then the MG is requested to reserve resources so that it can decode or encode the media stream according to any of the alternatives. For instance, if the Local Descriptor contains two groups of properties, one specifying packetized ITU-T G.711 A-law audio and the other ITU-T G.723.1 audio, the MG reserves resources so that it can decode one audio stream encoded in either ITU-T G.711 A-law format or ITU-T G.723.1 format. The MG does not have to reserve resources to decode two audio streams + +simultaneously, one encoded in ITU-T G.711 A-law and one in ITU-T G.723.1. The intention for the use of ReserveValue is analogous. + +###### **7.1.8.2.3.3      ReserveValue = "True" OR ReserveGroup = "True"** + +If ReserveGroup is "True" or ReserveValue is "True", then the following rules apply: + +- If the MG has insufficient resources to support all alternatives requested by the MGC, and the MGC requested resources in both Local and Remote, the MG should reserve resources to support at least one alternative each within Local and Remote. +- If the MG has insufficient resources to support at least one alternative within a Local (Remote) Descriptor received from the MGC, it shall return an empty Local (Remote) in response. +- In its response to the MGC, when the MGC included Local and Remote Descriptors, the MG shall include Local and Remote Descriptors for all groups of properties and property values it reserved resources for. If the MG is incapable of supporting at least one of the alternatives within the Local (Remote) Descriptor received from the MGC, it shall return an empty Local (Remote) Descriptor. +- If the Mode Property of the LocalControl Descriptor is "RecvOnly", "SendRecv", or "LoopBack", the MG must be prepared to receive media encoded according to any of the alternatives included in its response to the MGC. + +###### **7.1.8.2.3.4      ReserveValue = "False" AND ReserveGroup = "False"** + +If ReserveGroup is "False" and ReserveValue is "False", then the MG should apply the following rules to resolve Local and Remote to a single alternative each: + +- The MG chooses the first alternative in Local for which it is able to support at least one alternative in Remote. +- If the MG is unable to support at least one Local and one Remote alternative, it returns Error Code 510 ("Insufficient resources"). +- The MG returns its selected alternative in each of Local and Remote. + +NOTE – The above rules allow the MG to prioritize the selection of the same codec in both the Local and Remote Descriptors; however, it also permits the MG to choose different codecs in each descriptor. + +A new setting of a Local or Remote Descriptor completely replaces the previous setting of that descriptor in the MG. Thus, to retain information from the previous setting, the MGC must include that information in the new setting. If the MGC wishes to delete some information from the existing descriptor, it merely resends the descriptor (in a Modify Command) with the unwanted information stripped out. + +### **7.1.9      Events Descriptor** + +#### **7.1.9.1      Introduction to events** + +The Events Descriptor parameter contains a RequestID and a list of events that the Media Gateway is requested to detect and report. The RequestID is used to correlate the request with the notifications that it may trigger. Requested events include, for example, fax tones, continuity test results, and on-hook and off-hook transitions. The RequestID is omitted if the Events Descriptor is empty (i.e., no events are specified). + +#### **7.1.9.2      Specification, parameterization and identification of events** + +Each event in the descriptor contains the event name, an optional StreamID, an optional KeepActive flag, an optional NotifyBehaviour flag, an optional ResetEventsDescriptor flag and optional parameters. The event name consists of a PackageID (where the event is defined) and an EventID. The ALL wildcard may be used for the EventID, indicating that all events from the specified + +package have to be detected. The default StreamID is 0, indicating that the event to be detected is not related to a particular media stream. Where an MGC has previously requested a Termination-level Event (i.e., default) and the MGC subsequently creates an additional stream, in order for the existing event/s to be applied to the new stream the MGC should also apply the event/s via an EventsDescriptor on the new stream. + +Events can have parameters. This allows a single event description to have some variation in meaning without creating large numbers of individual events. Further event parameters are defined in the package. + +If a DigitMap completion event is present or implied in the Events Descriptor, the EventDM Parameter is used to carry either the name or the value of the associated DigitMap. See clause 7.1.14 for further details. + +#### **7.1.9.3 Reporting of detected events** + +When an event is processed against the contents of an active Events Descriptor and found to be present in that descriptor ("recognized"), the default action of the MG is to send a Notify Command to the MGC. Notification may be deferred if the event is absorbed into the current dial string of an active DigitMap (see clause 7.1.14). The sending of a Notify Command may be influenced by the NotifyBehaviour flag. Moreover, event recognition may cause currently active signals to stop, or may cause the current Events and/or Signals Descriptor to be replaced, as described at the end of this subclause. Unless the Events Descriptor is replaced by another Events Descriptor, it remains active after an event has been recognized. + +#### **7.1.9.4 Buffering (and deferred reporting) of detected events** + +##### **7.1.9.4.1 Event buffer concept** + +If the value of the EventBufferControl Property equals "LockStep", following detection of such an event, normal handling of events is suspended. Any event which is subsequently detected and occurs in the EventBuffer Descriptor is added to the end of the EventBuffer (a FIFO queue), along with the time that it was detected. The MG shall wait for a new Events Descriptor to be loaded. A new Events Descriptor can be loaded either as the result of receiving a command with a new Events Descriptor, or by activating an embedded Events Descriptor. + +If EventBufferControl equals "Off", the MG continues processing based on the active Events Descriptor. + +In the case of an embedded Events Descriptor being activated, the MG continues event processing based on the newly activated Events Descriptor. + +NOTE – For purposes of EventBuffer handling, activation of an embedded Events Descriptor is equivalent to receipt of a new Events Descriptor. + +##### **7.1.9.4.2 Event buffer control** + +When the MG receives a command with a new Events Descriptor, one or more events may have been buffered in the EventBuffer in the MG. The value of EventBufferControl, then determines how the MG treats such buffered events. + +###### *Case 1* + +If EventBufferControl equals "LockStep" and the MG receives a new Events Descriptor, it will check the FIFO EventBuffer and take the following actions: + +- 1) If the EventBuffer is empty, the MG waits for detection of events based on the new Events Descriptor. + +- 2) If the EventBuffer is non-empty, the MG processes the FIFO queue starting with the first event: + - a) If the event in the queue is in the events listed in the new Events Descriptor, the MG acts on the event and removes the event from the EventBuffer. The time stamp of the Notify shall be the time the event was actually detected. The MG then waits for a new Events Descriptor. While waiting for a new Events Descriptor, any events detected that appear in the EventBuffer Descriptor will be placed in the EventBuffer. When a new Events Descriptor is received, the event processing will repeat from step 1). + - b) If the event is not in the new Events Descriptor, the MG shall discard the event and repeat from step 1). + +###### *Case 2* + +If EventBufferControl equals "Off" and the MG receives a new Events Descriptor, it processes new events with the new Events Descriptor. + +If the MG receives a command instructing it to set the value of EventBufferControl to "Off", all events in the EventBuffer shall be discarded. + +The MG may report several events in a single transaction as long as this does not unnecessarily delay the reporting of individual events. + +For procedures regarding transmitting the Notify Command, refer to the appropriate annex or ITU-T H.248.x Recommendation for specific transport considerations. + +The default value of EventBufferControl is "Off". + +NOTE – Since the EventBufferControl Property is in the TerminationState Descriptor, the MG might receive a command that changes the EventBufferControl Property and does not include an Events Descriptor. + +#### **7.1.9.5 Interaction between events and signals** + +Normally, recognition of an event shall cause any active signals to stop. When KeepActive is specified in the event, the MG shall not interrupt any signals active on the termination on which the event is detected. + +#### **7.1.9.6 Shaping the events reporting traffic** + +The NotifyBehaviour flag may be used to indicate that the Notify Command is: + +- sent immediately (NotifyImmediate: this is the default); +- never sent (NeverNotify); +- or regulated (i.e., sent or suppressed) according to the MGC load (RegulatedNotify). + +See clause E.15 for more details on the use of NotifyBehaviour. When used with DigitMaps the notify behaviour occurs when the active DigitMap is completed. The Regulated Notify may have an alternate regulated embedded Events or Signals Descriptor associated with it. If a notification is regulated (i.e., suppressed), then this alternate regulated embedded descriptor shall be activated. If the Notify is not regulated, then the original embedded descriptor is triggered. If NotifyImmediate or NeverNotify is set, then any original embedded descriptor is triggered on detection of the event. + +#### **7.1.9.7 Resetting events** + +The result of encountering the ResetEventsDescriptor flag set against an event depends on whether or not the Events Descriptor containing the event is an embedded Events Descriptor. In the case of an embedded Events Descriptor the ResetEventsDescriptor flag causes the Events Descriptor for that termination to be reset to its state prior to when the embedded descriptor was activated (i.e., the last Events Descriptor explicitly set by a Modify Command or, if there has been no Modify Command since the termination was last reset by being put into the NULL Context, the + +MG-provisioned Events Descriptor). In the case of a non-embedded Events Descriptor the ResetEventsDescriptor flag causes the active Events Descriptor for that termination to be reset by re-activating any DigitMap completion event(s) that have been matched and deactivated. + +The ResetEventsDescriptor flag shall be set on physical terminations only. The ResetEventsDescriptor flag shall be acted on when the termination is in the NULL Context. If the ResetEventsDescriptor flag is encountered when the termination is out of the NULL Context, then it shall have no effect. + +#### **7.1.9.8 Hierarchical events and signals: embedded Events/Signals Descriptors** + +An event can include an embedded Signals Descriptor and/or an embedded Events Descriptor which, if present, replaces the current Signals/Events Descriptor when the event is recognized. It is possible, for example, to specify that the dial-tone signal be generated when an off-hook event is recognized, or that the dial-tone signal be stopped when a digit is recognized. A media gateway controller shall not send Events Descriptors with an event both marked KeepActive and containing an embedded Signals Descriptor. + +Only one level of embedding is permitted. An embedded Events Descriptor shall not contain another embedded Events Descriptor; an embedded Events Descriptor may contain an embedded Signals Descriptor. + +#### **7.1.9.9 Consecutive Events Descriptors** + +An Events Descriptor received by a media gateway replaces any previous Events Descriptor. Event notification in process shall complete, and events detected after the command containing the new Events Descriptor executes, shall be processed according to the new Events Descriptor. + +An empty Events Descriptor disables all event recognition and reporting. An empty EventBuffer Descriptor clears the EventBuffer and disables all event accumulation in "LockStep" mode: the only events reported will be those occurring while an Events Descriptor is active. If an empty Events Descriptor is activated while the termination is operating in "LockStep" mode, the EventBuffer is immediately cleared. + +### **7.1.10 EventBuffer Descriptor** + +The EventBuffer Descriptor contains a list of events, with their parameters if any, that the MG is requested to detect and buffer when EventBufferControl equals LockStep (see clause 7.1.9). + +### **7.1.11 Signals Descriptor** + +#### **7.1.11.1 Introduction to Signals** + +Signals are MG-generated media such as tones and announcements as well as bearer-related signals such as hookswitch. More complex signals may include a sequence of such simple signals interspersed with and conditioned upon the receipt and analysis of media or bearer-related signals. Examples include echoing of received data as in the Basic Continuity Package (clause E.10). Signals may also request preparation of media content for future signals. + +#### **7.1.11.2 Overview of Signals Descriptor** + +A Signals Descriptor is a parameter that contains the set of signals that the Media Gateway is asked to apply to a termination. A Signals Descriptor contains a number of signals and/or sequential signal lists. A Signals Descriptor may contain zero signals and sequential signal lists. Support of sequential signal lists is optional. + +#### 7.1.11.3 Specification and identification of signals + +Signals are defined in packages. Signals shall be named with a PackageID (in which the signal is defined) and a SignalID. No wildcard shall be used in the SignalID. Signals that occur in a Signals Descriptor have an optional StreamID parameter (default is 0, to indicate that the signal is not related to a particular media stream), an optional signal type (see below), an optional duration and possibly parameters defined in the package that defines the signal. This allows a single signal to have some variation in meaning, obviating the need to create large numbers of individual signals. + +#### 7.1.11.4 Stream-level signals + +In case the MGC does not specify the StreamID parameter (or sets the StreamID parameter value explicitly to 0) the Signals Descriptor shall be applied to all streams (including any existing Streams and any new Stream defined by the command containing the Signals Descriptor). + +Therefore, where an MGC has previously requested that a Signals Descriptor be applied to all streams in a termination and the MGC subsequently creates an additional stream, in order for the existing signals to be applied to the new stream, the MGC shall also apply the Signals Descriptor to the new stream. + +#### 7.1.11.5 Indication of signal completion + +The optional NotifyCompletion Parameter allows an MGC to indicate that it wishes to be notified when the signal finishes playout. The possible cases are that the signal timed out (or otherwise completed on its own), that it was interrupted by an event, that it completed a cycle/iteration of the signal, that it was halted when a Signals Descriptor was replaced, or that it stopped or never started for other reasons. If the NotifyCompletion Parameter is not included in a Signals Descriptor, notification is generated only if the signal stopped or was never started for other reasons. For reporting to occur, the Signal Completion Event (see clause E.1.2) must be enabled in the currently active Events Descriptor. The optional parameter "RequestID" may be associated with a particular instance of a SignalID where multiple signals of the same SignalID are requested. This allows the MGC to distinguish between different Signal Completion ObservedEvents for that particular instance of a signal. The RequestID parameter shall not be included if the NotifyCompletion Parameter is not present. + +#### 7.1.11.6 Duration of Signals + +The duration is an integer value that is expressed in hundredths of a second. + +#### 7.1.11.7 Types of Signals + +There are three types of signals: + +- OnOff (OO): the signal lasts until it is turned off either with an empty Signals Descriptor or with a replacement Signals Descriptor that removes the signal from the descriptor; +- TimeOut (TO): the signal lasts until it is turned off (as above) or a specific period of time elapses. The signal will remain in the Signals Descriptor until removed; +- Brief (BR): the signal will stop on its own unless a new Signals Descriptor is applied that causes it to stop; no timeout value is needed. The signal shall remain in the Signals Descriptor unless removed. Due to the brief nature of the signals, even if the new Signals Descriptor is empty or excludes the signal, the signal is not guaranteed to be stopped (or changes done by start cannot be undone) as it may have already completed playout. + +If a signal of default type other than TO has its type overridden to type TO in the Signals Descriptor, the duration parameter must be present. + +If the signal type is specified in a Signals Descriptor, it overrides the default signal type (see clause 12.1.4). It is not possible to change the semantics of a signal by overriding the signal type. If duration is specified for an on/off signal, it shall be ignored. + +#### 7.1.11.8 List of signals + +A sequential signal list consists of a SignalListID and a sequence of signals to be played sequentially. Only the trailing element of the sequence of signals in a sequential signal list may be an on/off signal. The duration of a sequential signal list is the sum of the durations of the signals it contains plus the sum of the intersignal delay timings specified as parameters to the signals. + +If an intersignal delay is specified for a signal that is not in a sequential signal list or is the last element in a sequential signal list, it shall be ignored and the signal shall be determined to have completed at the termination of the signal, prior to the application of the intersignal delay timing. The duration of a signal in a SignalList with an intersignal delay includes the intersignal delay timing. + +Multiple signals and sequential signal lists in the same Signals Descriptor shall be played simultaneously. + +#### 7.1.11.9 Directionality of signals + +Signals have directionality, which is identified by the direction parameter in the base syntax or by package defined direction parameters. The direction parameter can be used to indicate the direction that the tone is to be sent. External indicates that the tone is sent from the MG to an external point. Internal indicates that the tone is played into the Context to the other terminations. Bothway indicates both internal and external behaviour. + +Signals are defined as proceeding from the termination towards the exterior of the context unless otherwise specified. If the signal direction is specified in a Signals Descriptor, it overrides the default signal direction. For those signals which have a direction parameter, the base protocol direction parameter takes precedence over any package-defined direction parameter when both are specified. If the MGC specifies a direction for a signal with which the MG cannot comply, the MG shall return Error Code 501 ("Not implemented"). When the same signal is applied to multiple terminations within one transaction, the MG should consider using the same resource to generate these signals. + +#### 7.1.11.10 Stop of signal generation + +Production of a signal on a termination is stopped by application of a new Signals Descriptor, or detection of an event on the termination (see clause 7.1.9). + +#### 7.1.11.11 Consecutive Signals Descriptor + +A new Signals Descriptor replaces any existing Signals Descriptor. Any already started and not yet stopped signals applied to the termination not in the replacement descriptor (which may be empty) shall be stopped irrespective of the signal type, and new signals are applied, except as follows. Signals present in the replacement descriptor and containing the KeepActive flag shall be continued if they are currently playing and have not already completed. If a replacement Signals Descriptor contains a signal that is not currently playing and contains the KeepActive flag, that signal shall be ignored. If the replacement descriptor contains a sequential signal list with the same identifier as the existing descriptor, then: + +- the signal type and sequence of signals in the sequential signal list in the replacement descriptor shall be ignored; and +- the playing of the signals in the sequential signal list in the existing descriptor shall not be interrupted. + +### 7.1.12 Audit Descriptor + +The Audit Descriptor specifies what information is to be audited. The Audit Descriptor specifies the list of descriptors and/or individual properties to be returned. Audit may be used in any command to force the return of any descriptor containing the current values of its properties, events, signals and statistics even if that descriptor was not present in the command, or had no underspecified parameters. Possible items in the Audit Descriptor are: + +| | | +|--------------------------------------|------------------| +| Modem (Deprecated, see clause 7.1.2) | | +| Mux | | +| Events | | +| Media | | +| Signals | | +| ObservedEvents | | +| DigitMap | | +| Statistics | | +| Packages | | +| EventBuffer | | +| Individual Audit Items: | | +| Media Properties | DigitMaps | +| Events | Statistics | +| EventBuffer | Packages | +| Signals, SignalLists | ContextAttribute | + +The Audit Descriptor may be empty, in which case, no descriptors are returned. This is useful in the Subtract Command to inhibit return of statistics, especially when using wildcard. + +### 7.1.13 ServiceChange Descriptor + +The ServiceChange Descriptor contains the following parameters: + +- ServiceChangeMethod; +- ServiceChangeReason; +- ServiceChangeAddress; +- ServiceChangeDelay; +- ServiceChangeProfile; +- ServiceChangeVersion; +- ServiceChangeMGCID; +- TimeStamp; +- Extension; +- ServiceChangeInfo; +- ServiceChangeIncompleteFlag. + +See clause 7.2.8. + +### 7.1.14 DigitMap Descriptor + +#### 7.1.14.1 DigitMap definition, creation, modification and deletion + +A DigitMap is a dialling plan resident in the Media Gateway used for detecting and reporting digit events received on a termination. The DigitMap Descriptor contains a DigitMap name and the DigitMap to be assigned. A DigitMap may be preloaded into the MG by management action and referenced by name in an Events Descriptor, may be defined dynamically and subsequently referenced by name, or the actual digitmap itself may be specified in the Events Descriptor. It is permissible for a DigitMap completion event within an Events Descriptor to refer by name to a DigitMap which is defined by a DigitMap Descriptor within the same command, regardless of the transmitted order of the respective descriptors. + +DigitMaps defined in a DigitMap Descriptor can occur in any of the standard termination manipulation commands of the protocol. A DigitMap, once defined, can be used on all terminations specified by the (possibly wildcarded) TerminationID in such a command. DigitMaps defined on the Root Termination are global and can be used on every termination in the MG, provided that a DigitMap with the same name has not been defined on the given termination. When a DigitMap is defined dynamically in a DigitMap Descriptor: + +- A new DigitMap is created by specifying a name that is not yet defined. The value shall be present. +- A DigitMap value is updated by supplying a new value for a name that is already defined. Terminations presently using the DigitMap shall continue to use the old definition; subsequent Events Descriptors specifying the name, including any Events Descriptor in the command containing the DigitMap Descriptor, shall use the new one. +- A DigitMap is deleted by supplying an empty value for a name that is already defined. Terminations presently using the DigitMap shall continue to use the old definition. + +#### 7.1.14.2 DigitMap timers + +The collection of digits according to a DigitMap may be protected by three timers, viz. a start timer (T), short timer (S) and long timer (L). + +- 1) The start timer (T) is used prior to any digits being available for processing against the DigitMap. If the start timer is overridden with the value set to zero ( $T = 0$ ), then the start timer shall be disabled. This implies that the MG will wait indefinitely for digits. +- 2) If the Media Gateway can determine that at least one more digit is needed for a digit string to match any of the allowed patterns in the DigitMap, then the interdigit timer value should be set to a long (L) duration (e.g., 16 seconds). +- 3) If the digit string has matched one of the patterns in a DigitMap, but it is possible that more digits could be received which would cause a match with a different pattern, then instead of reporting the match immediately, the MG must apply the short timer (S) and wait for more digits. + +The timers are configurable parameters to a DigitMap. Default values of these timers should be provisioned on the MG, but can be overridden by values specified within the DigitMap. + +#### 7.1.14.3 DigitMap syntax + +The formal syntax of the DigitMap is described by the DigitMap rule in the formal syntax description of the protocol (see Annexes A and B). A DigitMap, according to this syntax, is defined either by a string or by a list of strings. Each string in the list is an alternative event sequence, specified either as a sequence of DigitMap symbols or as a regular expression of DigitMap symbols. These DigitMap symbols, the digits "0" through "9" and letters "A" through a maximum value depending on the signalling system concerned, but never exceeding "K", correspond to specified events within a package which has been designated in the Events Descriptor on the termination to + +which the DigitMap is being applied. (The mapping between events and DigitMap symbols is defined in the documentation for packages associated with channel-associated signalling systems such as DTMF, MF, or R2. Digits "0" through "9" must be mapped to the corresponding digit events within the signalling system concerned. Letters should be allocated in logical fashion, facilitating the use of range notation for alternative events.) + +The letter "x" is used as a wildcard, designating any event corresponding to symbols in the range "0"- "9". The string may also contain explicit ranges and, more generally, explicit sets of symbols, designating alternative events any one of which satisfies that position of the DigitMap. Finally, the dot symbol "." stands for zero or more repetitions of the event selector (event, range of events, set of alternative events, or wildcard) that precedes it. As a consequence of the third timing rule above, inter-event timing while matching a terminal dot symbol uses the short timer by default. + +In addition to these event symbols, the string may contain "S" and "L" inter-event timing specifiers and the "Z" duration modifier. "S" and "L" respectively indicate that the MG should use the short (S) timer or the long (L) timer for subsequent events, overriding the timing rules described above. If an explicit timing specifier is in effect in one alternative event sequence, but none is given in any other candidate alternative, the timer value set by the explicit timing specifier must be used. If all sequences with explicit timing controls are dropped from the candidate set, timing reverts to the default rules given above. If used inside a range notation, the S and L specifiers shall be ignored. Finally, if conflicting timing specifiers are in effect in different alternative sequences, the long timer shall be used. + +A "Z" designates a long duration event: placed in front of the symbol(s) designating the event(s) which satisfy a given digit position, it indicates that that position is satisfied only if the duration of the event exceeds the long-duration threshold. The value of this threshold is assumed to be provisioned in the MG, but, like the T, L, and S timers, can be overridden by specification within the DigitMap. If the Z specifier is not followed by a digit (0-9 or A-K), then the MG shall reject the digitmap as invalid procedure. When used in a range notation, the Z specifier applies solely to the immediately following digit. When used immediately prior to a range, the Z modifier applies to all digits in the range (thereby requiring a match in the range to be long duration). + +#### 7.1.14.4 DigitMap completion event + +A DigitMap is active while the Events Descriptor which invoked it is active and it has not completed. A DigitMap completes when: + +- a timer has expired; or +- an alternative event sequence has been matched and no other alternative event sequence in the DigitMap could be matched through detection of an additional event (unambiguous match); or +- an event has been detected such that a match to a complete alternative event sequence of the DigitMap will be impossible no matter what additional events are received. + +Upon completion, a DigitMap completion event, as defined in the package providing the events being mapped into the DigitMap, shall be generated. At that point, the DigitMap is deactivated. Subsequent events in the package are processed as follows: + +- If EventBufferControl is "LockStep", subsequent digit events are processed in the same way as any other events; +- If EventBufferControl is "OFF", if the active Events Descriptor did not change, and if individual digit events are not enabled within that descriptor, then digit buffering will be initiated. Buffering will continue until the buffering time specified in the original DigitMap completion event has expired or until the active Events Descriptor is replaced. + +The digit buffer shall take the logical form of a dial string which includes the digit characters as represented in the DigitMap, possibly preceded by 'Z'. The threshold value of tone duration used to identify long events shall be the same as that used with the most recently completed DigitMap. + +Buffering time defaults to zero (no buffering) unless explicitly set otherwise within the DigitMap completion event. If buffering ceases due to buffering timer expiry, the contents of the digit buffer are discarded. + +If buffering was stopped by a new Events Descriptor and that Events Descriptor contains a new DigitMap completion event from the same package as the previous one, any buffered digits are processed against the DigitMap as described below. Buffered digits not consumed by the new DigitMap are handled as if they had been observed after that map completed. + +If, instead, the new Events Descriptor enables the reporting of individual digit events, the entire set of buffered digits shall immediately be processed, the applicable events reported, and the buffer cleared. + +Finally, if the new Events Descriptor enables neither a DigitMap completion event nor the reporting of individual digit events from the package concerned, the buffer contents are discarded and buffering is terminated. + +#### 7.1.14.5 DigitMap procedures + +Pending completion, successive events shall be processed according to the following rules: + +- 1) The "current dial string", an internal variable, is initially empty. The set of candidate alternative event sequences includes all of the alternatives specified in the DigitMap. +- 2) At each step, if buffered digits are available, the oldest one (with possible accompanying long duration (Z) qualifier) is removed from the buffer and processing moves to the next step as if the digit event had just been observed. Otherwise a timer is set to wait for the next event, based either on the default timing rules given above, or on explicit timing specified in one or more alternative event sequences. If the timer expires and a member of the candidate set of alternatives is fully satisfied, a timeout completion with full match is reported. If the timer expires and part or none of any candidate alternative is satisfied, a timeout completion with partial match is reported. In either case, if the DigitMap completion event allows for detailed timeout reporting, the reported dial string will end with 'L', 'S', or 'T' as appropriate. +- 3) If an event is detected before the timer expires, it is mapped to a digit string symbol and provisionally added to the end of the current dial string. The duration of the event (long or not long) is noted if, and only if, this is relevant in the current symbol position (because at least one of the candidate alternative event sequences includes the "Z" modifier at this position in the sequence). +- 4) The current dial string is compared to the candidate alternative event sequences. If, and only if, a sequence expecting a long-duration event at this position is matched (i.e., the event had long duration and met the specification for this position), then any alternative event sequences not specifying a long duration event at this position are discarded, and the current dial string is modified by inserting a "Z" in front of the symbol representing the latest event. Any sequence expecting a long-duration event at this position, but not matching the observed event, is discarded from the candidate set. If alternative event sequences not specifying a long duration event in the given position remain in the candidate set after application of the above rules, the observed event duration is treated as irrelevant in assessing matches to them. + +- 5) If exactly one candidate remains and it has been fully matched, a completion event is generated indicating an unambiguous match. If no candidates remain, the latest event is removed from the current dial string and a completion event is generated indicating full match if one of the candidates from the previous step was fully satisfied before the latest event was detected or partial match otherwise. The event removed from the current dial string will then be reported as a separate event, buffered, or discarded according to the rules described in the previous clause. This statement is qualified as follows: + - a) The DigitMap completion event may specify that the removed event be reported as a parameter of the completion event. This occurs independently of subsequent processing of the digit event. + - b) The DigitMap completion event may specify that the extra digit should be discarded. In this case, it is discarded immediately. Any buffering or other processing applies only to subsequent events. +- 6) If no completion event is reported out of step 5), processing returns to step 2). + +#### 7.1.14.6 DigitMap activation + +A DigitMap is activated whenever a new Events Descriptor is applied to the termination or embedded Events Descriptor is activated, and that Events Descriptor contains a DigitMap completion event. The DigitMap completion event contains an EventDM field in the requested actions field. Each new activation of a DigitMap begins at step 1 of the above procedure, with a clear current dial string. Any previous contents of the current dial string from an earlier activation are lost. + +A DigitMap completion event that does not contain an EventDM field in its requested actions field is considered an error. Upon receipt of such an event in an Events Descriptor, an MG shall respond with an error response, including Error Code 457 ("Missing parameter in signal or event"). + +#### 7.1.14.7 Interaction of DigitMap and event processing + +While the DigitMap is activated, detection is enabled for all events defined in the package containing the specified DigitMap completion event. Normal event behaviour (e.g., stopping of signals unless the digit completion event has the KeepActive flag enabled) continues to apply for each such event detected, except that: + +- the events in the package containing the specified DigitMap completion event other than the completion event itself are not individually notified and have no side-effects unless separately enabled; and +- an event that triggers a partial match completion event is not recognized and therefore has no side effects until reprocessed following the recognition of the DigitMap completion event. Similarly buffered digit events are not recognized and have no side effects until processed. + +#### 7.1.14.8 Wildcards + +Note that if a package contains a DigitMap completion event, then an event specification consisting of the PackageID with a wildcarded EventID will activate a DigitMap; to that end, the event specification must include an EventDM field according to clause 7.1.14.6. If the package also contains the digit events themselves, this form of event specification will cause the individual events to be reported to the MGC as they are detected. + +#### 7.1.14.9 Example + +As an example, consider the following dial plan: + +| | | +|------------------------|------------------------------------------| +| 0 | Local operator | +| 00 | Long-distance operator | +| xxxx | Local extension number (starts with 1-7) | +| 8xxxxxxx | Local number | +| #xxxxxxx | Off-site extension | +| *xx | Star services | +| 91xxxxxxxxxxx | Long-distance number | +| 9011 + up to 15 digits | International number | + +If the DTMF detection package described in clause E.6 is used to collect the dialled digits, then the dialling plan shown above results in the following DigitMap: + +(0 | 00 | [1-7] xxx | 8xxxxxxx | Fxxxxxxx | Exx | 91xxxxxxxxxxx | 9011x.) + +### 7.1.15 Statistics Descriptor + +The Statistics Descriptor provides information describing the status and usage of a termination during its existence (ephemeral) or while it is outside the NULL context (physical). Statistics may be at a termination level or associated with a particular Stream Descriptor. By default, statistics occur at a termination level. If a stream is unable to support a statistic, Error Code 460 ("Unable to set statistic on stream") shall be returned. There is a set of standard statistics kept for each termination where appropriate (number of octets sent and received for example). By default, the particular statistics that are reported for a given termination are determined by the Packages realized by the termination. It is also possible, using the descriptor, to indicate what statistics are to be collected. The setting of a Statistics Descriptor overrides a previously set Statistics Descriptor. Thus, to maintain already set statistics, these shall be included in the new Statistics Descriptor and the statistic values shall not be reset. Statistics that have been removed from a Statistics Descriptor shall maintain their values until the termination is subtracted. However, if the particular statistic is reactivated by a subsequent Statistics Descriptor, the value shall be reset. An MGC may reactivate all statistics on a termination/stream by issuing a Statistics Descriptor with a single statistic with the PackageID and StatisticID wildcarded with "ALL". To reactivate all statistics in a given package on a termination/stream, a Statistics Descriptor with a single statistic with the PackageID specified and the StatisticID wildcarded with "ALL" is issued. The receipt of an empty descriptor means that no statistics shall be collected for the specified termination. + +By default, unless an empty Statistics Descriptor had earlier been used to indicate that no statistics are to be collected, termination and stream level statistics are reported when the termination ceases to exist or is returned to the NULL context due to a Subtract command. This default behaviour can also be overridden by including an empty Audit Descriptor in the Subtract Command. If a stream is removed according to clause 7.1.6, by default stream level statistics are not reported. An audit of the Statistics Descriptor in the stream must be performed before the stream is removed to collect the statistics. Statistics may also be returned from the AuditValue Command, or any Add/Move/Modify Command using the Audit Descriptor. + +Statistics are cumulative; reporting statistics does not reset them. The value of a Statistic at a termination level is the result of a meaningful superior function (like, for instance, sum or average) of the values as if it had been placed on all the streams in the termination. Such a superior function is dependent on the particular statistic type. Unless specified otherwise in the package that defines a particular statistic, the default behaviour is a sum of the values. Statistics are reset when a termination ceases to exist or is returned to the NULL Context due to a Subtract Command. + +For terminations not in the NULL Context, the MGC may send a Modify Command with a Statistics Descriptor to disable one or more statistics followed by a second Modify Command including a Statistics Descriptor to re-enable those statistics. As explained above, this has the effect of resetting the included statistics. By bundling the two commands together into the same action or transaction, the MGC can minimize the time during which statistics are not collected by the MG. An audit of the Statistics Descriptor via the Audit Descriptor in the Modify Command or a separate AuditValue Command must be performed before the included statistics are reactivated to collect their values. + +### 7.1.16 Packages Descriptor + +Used only with the AuditValue command, the Packages Descriptor returns a list of packages realized by the termination. + +### 7.1.17 ObservedEvents Descriptor + +ObservedEvents is supplied with the Notify Command to inform the MGC of which event(s) were detected. Used with the AuditValue Command, the ObservedEvents Descriptor returns events in the event buffer which have not been notified. ObservedEvents contains the RequestID of the Events Descriptor that triggered the notification, the event(s) detected, optionally the detection time(s) and any parameters of the observed event. Detection times are reported with a precision of hundredths of a second. + +The ObservedEvents Descriptor may contain the StreamID associated with the detected Event. If the MGC has set the Event on a termination level, the MG may or may not report the StreamID depending on the semantic of the event. If the MGC has set the Event on a particular stream then this StreamID shall be returned. + +### 7.1.18 Topology Descriptor + +#### 7.1.18.1 General + +A Topology Descriptor is used to specify flow directions between terminations in a context. Contrary to the descriptors in previous clauses, the Topology Descriptor applies to a context instead of a termination. The default topology of a context is that each termination's transmission is received by all other terminations. When a Termination is added to a Context, its default Topology is "bothway" to the other Terminations in the Context. If another Topology is required this shall be indicated in any updated Topology Descriptor. The Topology Descriptor is optional to implement. An MG that does not support Topology Descriptors, but receives a command containing one, returns Error Code 444 ("Unsupported or unknown descriptor"), and optionally includes a string containing the name of the unsupported descriptor ("Topology") in the error text in the Error Descriptor. + +The Topology Descriptor occurs before the commands in an action. It is possible to have an action containing only a Topology Descriptor, provided that the context to which the action applies already exists. + +#### 7.1.18.2 Structure (syntax) of the Topology Descriptor + +A Topology Descriptor consists of a sequence of associated terminations of the form (*T1*, *T2*, *association*[,*StreamID*]). *T1* and *T2* specify terminations within the context, possibly using the ALL or CHOOSE wildcard. If the optional StreamID field is used, the association applies only to the particular stream between *T1* and *T2* labelled by the StreamID. If the StreamID field is omitted, the topology applies to all streams in the termination. + +#### 7.1.18.3 Descriptor element "association" + +The *association* specifies how media flows between these two terminations as follows: + +- (*T1*, *T2*, Isolate) means that the terminations matching *T2* do not receive media from the terminations matching *T1*, nor vice versa. +- (*T1*, *T2*, Oneway) means that the terminations that match *T2* receive media from the terminations matching *T1*, but not vice versa. In this case, use of the ALL wildcard such that there are terminations that match either *T1* or *T2* *but not both* is allowed. +- (*T1*, *T2*, OnewayExternal) means the terminations that match *T2*, receive media sent externally by terminations matching *T1*, but not vice versa. In this case, use of the ALL wildcard for *T1* is not allowed. +- (*T1*, *T2*, OnewayBoth) means the terminations that match *T2*, receive media sent and received externally by terminations matching *T1*, but not vice versa. In this case, use of the ALL wildcard for *T1* and/or *T2* is not allowed. +- (*T1*, *T2*, Bothway) means that the terminations matching *T2* receive media from the terminations matching *T1*, and vice versa. In this case it is allowed to use wildcards such that there are terminations that match both *T1* and *T2*. However, if there is a termination that matches both, no loopback is introduced. + +#### 7.1.18.4 Wildcarding of TerminationID elements + +##### 7.1.18.4.1 Wildcard CHOOSE + +CHOOSE wildcards may be used in *T1* and *T2* as well, under the following restrictions: + +- the action (see clause 8) of which the Topology Descriptor is part contains an Add Command in which a CHOOSE wildcard is used; +- if a CHOOSE wildcard occurs in *T1* or *T2*, then a partial name (underspecified Termination ID) shall not be specified. + +The CHOOSE wildcard in a Topology Descriptor matches the TerminationID that the MG assigns in the first Add Command that uses a CHOOSE wildcard in the same action. An existing termination that matches *T1* or *T2* in the context to which a termination is added is connected to the newly added termination as specified by the Topology Descriptor. If a termination is not mentioned within a Topology Descriptor, any topology associated with it remains unchanged. If, however, a new termination is added into a context, its association with the other terminations within the context defaults to Bothway, unless a Topology Descriptor is given to change this (e.g., if *T3* is added to a context with *T1* and *T2* with topology (*T3*, *T1*, Oneway) it will be connected bothway to *T2*). + +##### 7.1.18.4.2 Wildcard ALL + +ALL wildcard may be used in *T1* or *T2* as well, under the following restrictions: + +- "all" excludes the other termination in the Topology Descriptor (this semantic is in line with clause 6.2.2). + +ALL wildcard may not be used for both *T1* and *T2* in a single descriptor with a one-way association. + +##### 7.1.18.4.3 Combination of Wildcard ALL and CHOOSE in a single Topology Descriptor + +ALL wildcard may be used in *T1* and CHOOSE wildcard may be used in *T2*, or vice versa. The chosen termination is then excluded from the "all" set of the remaining terminations. + +#### 7.1.18.5 Topologies on Stream-level + +If the topology is applied to one particular stream (*T1*, *T2*, association, StreamID), the topology of other streams between the terminations does not change. + +A Topology Descriptor shall not include a combination of associations between two terminations (*Ti*, *Tj*) with and without the optional StreamID field, to avoid undefined behaviour. For example (*T1*, *T2*, Bothway) and (*T1*, *T2*, Isolate, S1) shall not appear in the same descriptor. Upon receipt of such a Topology Descriptor, an MG shall respond with an error response, including Error Code 421 ("Unknown action or illegal combination of actions"). + +#### 7.1.18.6 Association types + +##### 7.1.18.6.1 "Oneway" + +A oneway connection must be implemented in such a way that the other terminations in the context are not aware of the change in topology. + +#### 7.1.18.7 Example topologies + +Figure 11, the table following it and Figure 12 following it show some examples of the effect of including Topology Descriptors in actions. In these examples it is assumed that the Topology Descriptors are applied in sequence. Figures 13 and 14 are stand-alone examples showing the specific effects of the OnewayExternal and OnewayBoth topology settings. + +![Figure 11: Example topologies. Six diagrams labeled Context 1, showing different network topologies between three nodes T1, T2, and T3. 1) No topology descriptors: all nodes are interconnected with bidirectional arrows. 2) T1, T2 isolate: T1 and T2 are isolated from each other, but both have bidirectional connections to T3. 3) T3, T2 oneway: T3 has a bidirectional connection to T1, and a unidirectional arrow points from T3 to T2. 4) T2, T3 oneway: T2 has a unidirectional arrow pointing to T3, and T3 has a bidirectional connection to T1. 5) T2, T3 bothway: T2 and T3 have bidirectional connections to each other, and T3 has a bidirectional connection to T1. 6) T1, T2 bothway: T1 and T2 have bidirectional connections to each other, and T2 has a bidirectional connection to T3.](78e846f2858d131dc5a4dcbabcca1e4d_img.jpg) + +Figure 11: Example topologies. Six diagrams labeled Context 1, showing different network topologies between three nodes T1, T2, and T3. 1) No topology descriptors: all nodes are interconnected with bidirectional arrows. 2) T1, T2 isolate: T1 and T2 are isolated from each other, but both have bidirectional connections to T3. 3) T3, T2 oneway: T3 has a bidirectional connection to T1, and a unidirectional arrow points from T3 to T2. 4) T2, T3 oneway: T2 has a unidirectional arrow pointing to T3, and T3 has a bidirectional connection to T1. 5) T2, T3 bothway: T2 and T3 have bidirectional connections to each other, and T3 has a bidirectional connection to T1. 6) T1, T2 bothway: T1 and T2 have bidirectional connections to each other, and T2 has a bidirectional connection to T3. + +NOTE – The direction of the arrow indicates the direction of flow. + +H.248.1 v3(13)\_F11 + +**Figure 11 – Example topologies** + +| Topology | Description | +|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | No Topology Descriptors
When no Topology Descriptors are included, all terminations have a bothway connection to all other terminations. | +| 2 | T1 , T2 Isolate
Removes the connection between T1 and T2 . T3 has a bothway connection with both T1 and T2 . T1 and T2 have bothway connections to T3 . | +| 3 | T3 , T2 Oneway
An oneway connection from T3 to T2 (i.e., T2 receives media flow from T3 ). A bothway connection between T1 and T3 . | + +| Topology | Description | +|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4 | T2, T3 Oneway
An oneway connection between T2 to T3 . T1 and T3 remain bothway connected | +| 5 | T2, T3 Bothway
T2 is bothway connected to T3 . This results in the same as Topology 2. | +| 6 | T1, T2 Bothway ( T2, T3 Bothway and T1, T3 Bothway may be implied or explicit). All terminations have a bothway connection to all other terminations. | + +![Figure 12: Example topology at stream level. Three sub-diagrams (a, b, c) showing three terminations T1, T2, and T3. (a) No topology descriptors: T1 and T3 are connected by a double-headed arrow labeled '1' and '2'. T2 is connected to T1 and T3 by single-headed arrows pointing to T2. (b) T1, T3, oneway, 2: T1 and T3 are connected by a double-headed arrow labeled '1' and '2'. T2 is connected to T1 and T3 by single-headed arrows pointing to T2. (c) T3, T1, oneway, 1: T1 and T3 are connected by a double-headed arrow labeled '1' and '2'. T2 is connected to T1 and T3 by single-headed arrows pointing to T2. The diagrams are labeled H.248.1 v3(13)_F12.](3c6151f296d5800335472b7dc00ce423_img.jpg) + +Figure 12: Example topology at stream level. Three sub-diagrams (a, b, c) showing three terminations T1, T2, and T3. (a) No topology descriptors: T1 and T3 are connected by a double-headed arrow labeled '1' and '2'. T2 is connected to T1 and T3 by single-headed arrows pointing to T2. (b) T1, T3, oneway, 2: T1 and T3 are connected by a double-headed arrow labeled '1' and '2'. T2 is connected to T1 and T3 by single-headed arrows pointing to T2. (c) T3, T1, oneway, 1: T1 and T3 are connected by a double-headed arrow labeled '1' and '2'. T2 is connected to T1 and T3 by single-headed arrows pointing to T2. The diagrams are labeled H.248.1 v3(13)\_F12. + +Figure 12 – Example topology at stream level + +![Figure 13: OnewayExternal contrasted with Oneway topology. The diagram shows a termination T1 on the left connected to a box containing T2, T3, and T4. T1 has a 'Oneway To T3' connection to T3 and a 'Onewayexternal To T4' connection to T4. T2 is connected to T1 by a double-headed arrow. T3 and T4 are connected to T1 by single-headed arrows pointing to T1. The diagram is labeled H.248.1 v3(13)_F13.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Topology +*T1, T2, bothway* +*T1, T3, oneway* +*T1, T4, onewayexternal* + +Figure 13: OnewayExternal contrasted with Oneway topology. The diagram shows a termination T1 on the left connected to a box containing T2, T3, and T4. T1 has a 'Oneway To T3' connection to T3 and a 'Onewayexternal To T4' connection to T4. T2 is connected to T1 by a double-headed arrow. T3 and T4 are connected to T1 by single-headed arrows pointing to T1. The diagram is labeled H.248.1 v3(13)\_F13. + +Figure 13 – OnewayExternal contrasted with Oneway topology + +![Figure 14: Operation of OnewayBoth topology. The diagram shows a termination T1 on the left connected to a box containing T2 and T3. T1 has a 'Onewayboth To T3' connection to T3, represented by a circle with a '+' sign. T2 is connected to T1 by a double-headed arrow. T3 is connected to T1 by a single-headed arrow pointing to T1. The diagram is labeled H.248.1 v3(13)_F14.](aeb2a26a07219661191294dba528067a_img.jpg) + +Topology +*T1, T2, bothway* +*T1, T3, onewayboth* + +Figure 14: Operation of OnewayBoth topology. The diagram shows a termination T1 on the left connected to a box containing T2 and T3. T1 has a 'Onewayboth To T3' connection to T3, represented by a circle with a '+' sign. T2 is connected to T1 by a double-headed arrow. T3 is connected to T1 by a single-headed arrow pointing to T1. The diagram is labeled H.248.1 v3(13)\_F14. + +Figure 14 – Operation of OnewayBoth topology + +### 7.1.19 ContextAttribute Descriptor + +A ContextAttribute Descriptor is used to specify properties (defined in packages) that apply to the context as a whole and is applied on a context rather than a termination. Termination properties are not valid in the ContextAttribute Descriptor. The ContextAttribute Descriptor occurs before the commands in an action. It is possible to have an action containing only a ContextAttribute + +Descriptor, provided that the indicated context already exists. Values of context properties may be underspecified as in clause 7.1.1. + +A new setting of the ContextAttribute Descriptor completely replaces the previous setting of that descriptor in the MG. Thus to retain information from the previous setting the MGC must include that information in the new setting. If the MGC wishes to delete some information from the existing descriptor, it merely resends the descriptor with the unwanted information stripped out. The inclusion of a ContextAudit or a ContextAttribute Descriptor in an action that contains only an AuditValue or AuditCapability Command does not constitute a new setting. + +The ContextIDList parameter is used to provide a compact list of ContextIDs. To request the use of the ContextIDList parameter in a reply, the ContextIDList parameter should be included in the corresponding request. + +### 7.1.20 Error Descriptor + +If a responder encounters an error when processing a transaction request, it must include an Error Descriptor in its response. A Notify request may contain an Error Descriptor as well. + +An Error Descriptor consists of an IANA-registered error code, optionally accompanied by an error text. [ITU-T H.248.8] contains a list of valid error codes and error descriptions. + +An Error Descriptor shall be specified at the "deepest level" that is semantically appropriate for the error being described and that is possible given any parsing problems with the original request. An Error Descriptor may refer to a syntactic construct other than where it appears. For example, Error Descriptor 422 ("Syntax Error in Action"), could appear within a command even though it refers to the larger construct, the action, and not the particular command within which it appears. + +If the error being described can be determined to be at a descriptor level, the Error Descriptor may be returned at the descriptor level. If this is the case, the Error Descriptor should be returned where the descriptor that generated an error would have been inserted in the response. + +## 7.2 Command application programming interface + +Following is an Application Programming Interface (API) describing the commands of the protocol. This API is shown to illustrate the commands and their parameters and is not intended to specify implementation (e.g., via use of blocking function calls). It describes the input parameters in parentheses after the command name and the return values in front of the command. This is only for descriptive purposes; the actual command syntax and encoding are specified in later subclauses. The order of parameters to commands is not fixed. Descriptors may appear as parameters to commands in any order. The descriptors shall be processed in the order in which they appear. + +Any reply to a command may contain an Error Descriptor; the API does not specifically show this. + +All parameters enclosed by square brackets ([ . . ]) are considered optional. + +### 7.2.1 Add + +The Add Command adds a termination to a context. + +TerminationIDList +[,MediaDescriptor] +[,ModemDescriptor] (\*) +[,MuxDescriptor] +[,EventsDescriptor] +[,SignalsDescriptor] +[,DigitMapDescriptor] +[,ObservedEventsDescriptor] + +``` + +[,EventBufferDescriptor] +[,StatisticsDescriptor] +[,PackagesDescriptor] +Add( TerminationIDList + [, MediaDescriptor] + [, ModemDescriptor] (*) + [, MuxDescriptor] + [, EventsDescriptor] + [, EventBufferDescriptor] + [, SignalsDescriptor] + [, DigitMapDescriptor] + [, AuditDescriptor] + [, StatisticsDescriptor] +) + +``` + +(\*) Modem Descriptor has been deprecated in Recommendation ITU-T H.248.1 version 2 (05/2002). + +The TerminationIDList specifies one or more terminations to be added to the context. The termination(s) is either created, or taken from the NULL Context. If a CHOOSE wildcard is used in the TerminationID, the selected TerminationID will be returned. ALL wildcards may be used in an Add, but such usage would be unusual. If the wildcard matches more than one TerminationID, all possible matches are attempted, with results reported for each one. The order of attempts when multiple TerminationIDs match is not specified. + +The optional Media Descriptor describes all media streams. + +The optional Mux Descriptor specifies a multiplexer if applicable. For convenience, if a Multiplex Descriptor is present in an Add Command and lists any terminations that are not currently in the context, such terminations are added to the context as if individual Add Commands listing the terminations were invoked. If an error occurs on such an implied Add, error 471 ("Implied Add for Multiplex failure") shall be returned and further processing of the command shall cease. + +The Events Descriptor parameter is optional. If present, it provides the list of events that should be detected on the termination. + +The EventBuffer Descriptor parameter is optional. If present, it provides the list of events that the MG is requested to detect and buffer when EventBufferControl equals LockStep. + +The Signals Descriptor parameter is optional. If present, it provides the list of signals that should be applied to the termination. + +The DigitMap Descriptor parameter is optional. If present, it defines a DigitMap definition that may be used in an Events Descriptor. + +The Audit Descriptor is optional. If present, the command will return the values of any descriptors/properties/signals/events/statistics specified in the Audit Descriptor. + +The Statistics Descriptor is optional. If present, it provides the statistics which the MGC wishes to be collected for the termination or stream. Each time the statistic is set, the statistic value is reset. + +All descriptors that can be modified could be returned by MG if a parameter was underspecified or overspecified. The ObservedEvents, Statistics, Packages and EventBuffer Descriptors are returned only if requested in the Audit Descriptor. + +Add shall not be used on a termination with a ServiceStates of "OutOfService". + +### 7.2.2 Modify + +The Modify Command modifies the properties of a termination. + +TerminationIDList + +[,MediaDescriptor] + +[,ModemDescriptor] (\*) + +[,MuxDescriptor] + +[,EventsDescriptor] + +[,SignalsDescriptor] + +[,DigitMapDescriptor] + +[,ObservedEventsDescriptor] + +[,EventBufferDescriptor] + +[,StatisticsDescriptor] + +[,PackagesDescriptor] + +Modify( TerminationIDList + +[, MediaDescriptor] + +[, ModemDescriptor] (\*) + +[, MuxDescriptor] + +[, EventsDescriptor] + +[, EventBufferDescriptor] + +[, SignalsDescriptor] + +[, DigitMapDescriptor] + +[, AuditDescriptor] + +[, StatisticsDescriptor] + +) + +(\*) Modem Descriptor has been deprecated in Recommendation ITU-T H.248.1 version 2 (05/2002). + +The TerminationIDList specifies the terminations to be modified. The TerminationID may be specific if a single termination in the context is to be modified. Use of wildcards in the TerminationID may be appropriate for some operations. If the wildcard matches more than one TerminationID, all possible matches are attempted, with results reported for each one. The order of attempts when multiple TerminationIDs match is not specified. The CHOOSE TerminationID is an error, as the Modify command may only be used on existing terminations. + +For convenience, if a Multiplex Descriptor is present in a Modify command, then: + +- if the new Multiplex Descriptor lists any terminations that are not currently in the context, such terminations are added to the context as if individual Add Commands listing the terminations were invoked; +- if any terminations listed previously in the Multiplex Descriptor are no longer present in the new Multiplex Descriptor, they are subtracted from the context as if individual Subtract commands listing the terminations were invoked. + +The remaining parameters to Modify are the same as those to Add. Possible return values are the same as those to Add. + +### 7.2.3 Subtract + +The Subtract Command disconnects a termination from its context and returns statistics on the termination's participation in the context. + +``` +TerminationIDList +[,MediaDescriptor] +[,ModemDescriptor] (*) +[,MuxDescriptor] +[,EventsDescriptor] +[,SignalsDescriptor] +[,DigitMapDescriptor] +[,ObservedEventsDescriptor] +[,EventBufferDescriptor] +[,StatisticsDescriptor] +[,PackagesDescriptor] + Subtract(TerminationIDList + [, AuditDescriptor] + ) +``` + +(\*) Modem Descriptor has been deprecated in Recommendation ITU-T H.248.1 version 2 (05/2002). + +TerminationIDList in the input parameters represents the termination(s) that is being subtracted. The TerminationID may be specific or may be a wildcard value indicating that all (or a set of related) terminations in the context of the Subtract Command are to be subtracted. If the wildcard matches more than one TerminationID, all possible matches are attempted, with results reported for each one. The order of attempts when multiple TerminationIDs match is not specified. + +The use of CHOOSE in the TerminationID is an error, as the Subtract command may only be used on existing terminations. + +ALL may be used as the ContextID as well as the TerminationID in a Subtract, which would have the effect of deleting all contexts, deleting all ephemeral terminations, and returning all physical terminations to NULL Context. Subtract of a termination from the NULL Context is not allowed. + +For convenience, if a multiplexing termination is the object of a Subtract command, then any bearer terminations listed in its Multiplex Descriptor are subtracted from the context as if individual Subtract commands listing the terminations were invoked. + +By default unless overridden, the Statistics Descriptor on both the termination and stream levels is returned to report information collected on the termination or terminations specified in the command. The information reported applies to the termination's or terminations' existence in the context from which it or they are being subtracted. + +The Audit Descriptor is optional. If present, the command will return only those items specified in the Audit Descriptor, which may be empty. If the Audit Descriptor is omitted, the Statistics Descriptor is returned, by default. Possible return values are the same as those to Add. + +When a provisioned termination is Subtracted from a context, its descriptor values shall revert to: + +- the default value, if specified for the descriptor and not overridden by provisioning; +- otherwise, the provisioned value. + +### 7.2.4 Move + +The Move Command moves a termination to another context from its current context in one atomic operation. The Move Command is the only command that refers to a termination in a context different from that to which the command is applied. The Move Command shall not be used to move terminations to or from the NULL Context. + +TerminationIDList + +[,MediaDescriptor] + +[,ModemDescriptor] (\*) + +[,MuxDescriptor] + +[,EventsDescriptor] + +[,SignalsDescriptor] + +[,DigitMapDescriptor] + +[,ObservedEventsDescriptor] + +[,EventBufferDescriptor] + +[,StatisticsDescriptor] + +[,PackagesDescriptor] + +Move( TerminationIDList + +[, MediaDescriptor] + +[, ModemDescriptor] (\*) + +[, MuxDescriptor] + +[, EventsDescriptor] + +[, EventBufferDescriptor] + +[, SignalsDescriptor] + +[, DigitMapDescriptor] + +[, AuditDescriptor] + +[, StatisticsDescriptor] + +) + +(\*) Modem Descriptor has been deprecated in Recommendation ITU-T H.248.1 version 2 (05/2002). + +The TerminationIDList specifies the termination(s) to be moved. TerminationIDs may be wildcarded, but CHOOSE shall not be used. If the wildcard matches more than one TerminationID, all possible matches are attempted, with results reported for each one. The order of attempts when multiple TerminationIDs match is not specified. The context to which the termination is moved is indicated by the target ContextID in the action. If the last remaining termination is moved out of a context, the context is deleted. + +The Move Command does not affect the properties/signals/events/statistics of the termination on which it operates, except those properties explicitly modified by descriptors included in the Move Command. As such unless the Signals Descriptor is modified the playout of signals continues. The Audit Descriptor with a Statistics Descriptor, for example, would return statistics on the termination just prior to the Move. Possible descriptors returned from Move are the same as for Add. + +For convenience, if a multiplexing termination is the object of a Move Command, then any bearer terminations listed in its Multiplex Descriptor are also moved as if individual Move Commands listing the terminations were invoked. + +Move shall not be used on a termination with a ServiceStates of "OutOfService". + +### 7.2.5 AuditValue + +The AuditValue Command returns the current values of properties, events, signals and statistics associated with terminations. An AuditValue may request the contents of a descriptor or of a single property, event, signal or statistic. AuditValue may be useful for maintaining termination synchronization between the MGC and MG. An AuditValue may request that the returned values be filtered based on specified selection criteria. + +TerminationIDList + +[,MediaDescriptor] + +[,ModemDescriptor] (\*) + +[,MuxDescriptor] + +[,EventsDescriptor] + +[,SignalsDescriptor] + +[,DigitMapDescriptor] + +[,ObservedEventsDescriptor] + +[,EventBufferDescriptor] + +[,StatisticsDescriptor] + +[,PackagesDescriptor] + +AuditValue(TerminationIDList, + +AuditDescriptor + +) + +(\*) Modem Descriptor has been deprecated in Recommendation ITU-T H.248.1 version 2 (05/2002). + +TerminationIDList specifies a sequence of TerminationIDs, which may be specific or wildcarded. If the wildcard matches more than one TerminationID, all possible matches are attempted, with results reported for each one. The order of attempts when multiple TerminationIDs match is not specified. If a wildcarded response is requested, only one command return is generated, with the contents containing the union of the values of all terminations matching the wildcard or list. This convention may reduce the volume of data required to audit a group of terminations. Use of CHOOSE is an error. + +Descriptors or individual properties, signals, events and statistics can be audited. The returned values can be filtered based on specified selection criteria. + +- An audit of a descriptor may be requested by identifying the desired descriptor in the Audit Descriptor with no further information. +- To audit an individual property in the Media Descriptor the relevant StreamID (optional), GroupID (optional) and PropertyID are included. The current value of the property is returned. GroupID is used in the case where the LocalControl Descriptor ReserveGroup flag is used. GroupID 1 corresponds to the first group (session description) reserved, GroupID 2 the next group, etc. +- To audit a signal, the relevant SignalListID and/or SignalID are provided. The StreamID and/or RequestID are optional. Only if the signal is active are the values of all the signal parameters returned including: the KeepActive indication, signal type, duration, signal completion indication and package defined properties. + +- To audit an event, the relevant StreamID (optional), EventID, RequestID (optional) are provided. The values of all the event parameters are returned including: event actions and packaged defined parameters. +- To audit a termination level statistic, the identity of the statistic is provided. To audit a stream level statistic, the relevant StreamID (optional), GroupID (optional) and the StatisticID is included in the Media Descriptor. The current value of the statistic is returned. The statistic is not reset. +- To audit a package, the identity and version of the package is provided. All properties, signals, events and statistics defined in that particular package are returned with their current value. +- To filter the audit return values, selection criteria are included in the audit request. It is possible to include multiple selection criteria. When multiple criteria are included, either an AND or an OR logic operation may also be included to indicate how the selection criteria are to be interpreted. If no logic operation is included, an AND logic operation is assumed. + +It is possible to audit multiple individual items in one request. + +If a descriptor audit is requested, the appropriate descriptors, with the current values for the termination, are returned from AuditValue. Values appearing in multiple instances of a descriptor are defined to be alternate values supported, with each parameter in a descriptor considered independent. + +ObservedEvents returns a list of events in the EventBuffer. If the ObservedEvents Descriptor is audited while a DigitMap is active, the returned ObservedEvents Descriptor also includes a DigitMap completion event that shows the current dial string but does not show a termination method. + +EventBuffer returns the set of events and associated parameter values currently enabled in the EventBuffer Descriptor. Packages Descriptor returns a list of packages realized by the termination. DigitMap Descriptor returns the name or value of the current DigitMap for the termination. DigitMap requested in an AuditValue command with TerminationID ALL returns all DigitMaps in the gateway. Statistics returns the current values of all statistics being kept at the termination level. An audit of the Media Descriptor will return any stream level statistics. Specifying an empty Audit Descriptor results in only the TerminationID being returned. This may be useful to get a list of TerminationIDs when used with wildcarding. Annexes A and B provide a special syntax for presenting such a list in condensed form, such that the AuditValue command tag does not have to be repeated for each TerminationID. + +AuditValue results depend on the context, viz. specific, NULL, or wildcarded. (Note that ContextID ALL does not include the NULL Context.) The TerminationID may be specific, or wildcarded. + +The following are examples of what is returned in case the context and/or the termination is wildcarded and a wildcarded response has been specified. + +Assume that the gateway has 4 terminations: t1/1, t1/2, t2/1 and t2/2. Assume that Terminations t1/\* have implemented Packages aaa and bbb and that Terminations t2/\* have implemented Packages ccc and ddd. Assume that Context 1 has t1/1 and t2/1 in it and that Context 2 has t1/2 and t2/2 in it. + +The command: + +Context=1 {AuditValue=t1/1 {Audit{Packages}}} + +returns: + +Context=1 {AuditValue=t1/1 {Packages{aaa,bbb}}} + +The command: + +Context=\* {AuditValue=t2/\* {Audit{Packages}}} + +returns: + +Context=1 {AuditValue=t2/1 {Packages {ccc,ddd}}}, + Context=2 {AuditValue=t2/2 {Packages {ccc,ddd}}} + +The command: + +Context=\* {W-AuditValue=t1/\* {Audit {Packages}}} + +returns: + +Context=\* {AuditValue=t1/\* {Packages {aaa,bbb}}} + +NOTE – A wildcard response may also be used for other commands such as Subtract. + +In the instance of a wildcarded context with Root, the MGC can indicate that it wants a compact list of ContextIDs, rather than having each context broken out into separate action replies. + +Assume that the gateway has 4 contexts: 1, 2, 3, 4, each containing two terminations (t1-t8). The following examples indicate how the MG would respond to the audit command: + +The command: + +Context=\* {AuditValue=Root {Audit {}}} + +returns: + +Context=1 {AuditValue=Context {\*}}, Context=2 {AuditValue=Context {\*}}, + Context=3 {AuditValue=Context {\*}}, Context=4 {AuditValue=Context {\*}} + +Or + +Context=1 {AuditValue=t1 {}, AuditValue=t2 {}}, Context=2 {AuditValue=t3 {}, AuditValue=t4 {}}, Context=3 {AuditValue=t5 {}, AuditValue=t6 {}}, Context=4 {AuditValue=t7 {}, AuditValue=t8 {}} + +The command: + +Context=\* {ContextAttr {ContextList={\*}}, AuditValue=Root {Audit {}}} + +returns: + +Context=\* {ContextAttr {ContextList={1,2,3,4}}, AuditValue=Root} + +The following illustrates other information that can be obtained with the AuditValue Command: + +| ContextID | TerminationID | Information obtained | +|-----------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Specific | Wildcard | Audit of matching terminations in a context | +| Specific | Specific | Audit of a single termination in a context | +| NULL | Root | Audit of Media Gateway state and events | +| NULL | Wildcard | Audit of all matching terminations in the NULL Context | +| NULL | Specific | Audit of a single termination outside of any context | +| ALL | Wildcard | Audit of all matching terminations not in NULL and the context to which they are associated | +| ALL | Root | List of all ContextIDs (the ContextID list may be returned either by using multiple action replies, each containing a ContextID from the list, or using the ContextIDList parameter. The method of response is determined by the presence of the ContextIDList parameter in the request.) | +| ALL | Specific | (Non-NULL) ContextID in which the termination currently exists | + +### 7.2.6 AuditCapability + +The AuditCapability Command returns the possible values of properties, events, signals and statistics associated with terminations. An AuditCapability may be requested for the contents of a descriptor or for a single property, event, signal or statistic. + +TerminationIDList + +[,MediaDescriptor] + +[,ModemDescriptor](\*) + +[,MuxDescriptor] + +[,EventsDescriptor] + +[,SignalsDescriptor] + +[,ObservedEventsDescriptor] + +[,EventBufferDescriptor] + +[,StatisticsDescriptor] + +AuditCapability(TerminationIDList, + +AuditDescriptor) + +(\*) Modem Descriptor has been deprecated in Recommendation ITU-T H.248.1 version 2 (05/2002). + +Descriptors or individual properties, signals, events and statistics can be audited. + +- An audit of an entire descriptor may be requested by identifying the desired descriptor in the Audit Descriptor with no further information. +- To audit an individual property in the Media Descriptor the relevant StreamID (optional) and PropertyID are included. A list of possible values of the property are returned. +- To audit a signal the relevant SignalListID and/or SignalID are provided. The StreamID and/or RequestID are optional. A list of possible values associated with each signal parameter is returned (including package defined properties). The KeepActive indication, signal type, duration and signal completion indication are not returned. +- To audit an event the relevant StreamID (optional), EventID, RequestID (optional) are provided. A list of possible values associated with each event parameter is returned (including event actions and package defined parameters). +- To audit a termination level statistic the identity of the statistic is provided. To audit a stream level statistic, the relevant StreamID (optional), GroupID (optional) and the StatisticID is included in the Media Descriptor. The possible values of the statistic are returned. The statistic is not reset. + +If a descriptor audit is requested, the appropriate descriptors, with the possible values for the termination, are returned from AuditCapability. Descriptors may be repeated where there are multiple possible values. + +If a wildcarded response is requested, only one command return is generated, with the contents containing the union of the values of all terminations in the list or matching the wildcard. This convention may reduce the volume of data required to audit a group of terminations. + +If a property, signal, event or statistic is audited, the appropriate properties, signals, events and statistics with the capabilities of the termination, are returned from AuditCapability. + +Interpretation of what capabilities are requested for various values of ContextID and TerminationID is the same as in AuditValue. + +For property and parameter values of type string, character or octet string, the MG shall return an empty value. For the text encoding, strings and characters return an empty quotedString construct, while octet strings return NULL (0x00). This behaviour may be overridden by the package definition. + +The Events Descriptor returns the list of possible events on the termination together with the list of all possible values for the Events Descriptor Parameters. EventBuffer Descriptor returns the same information as Events Descriptor. The Signals Descriptor returns the list of possible signals that could be applied to the termination, together with the list of all possible values for the signals' parameters. Statistics Descriptor returns the names of the statistics being kept on the termination. ObservedEvents Descriptor returns the names of active events on the termination. DigitMap and Packages are not legal in AuditCapability. + +The following illustrates other information that can be obtained with the AuditCapability Command: + +| ContextID | TerminationID | Information obtained | +|-----------|---------------|---------------------------------------------------------------------------------------------| +| Specific | Wildcard | Audit of matching terminations in a context | +| Specific | Specific | Audit of a single termination in a context | +| NULL | Root | Audit of MG state and events | +| NULL | Wildcard | Audit of all matching terminations in the NULL Context | +| NULL | Specific | Audit of a single termination outside of any context | +| ALL | Wildcard | Audit of all matching terminations not in NULL and the context to which they are associated | +| ALL | Root | Same as for AuditValue | +| ALL | Specific | Same as for AuditValue | + +### 7.2.7 Notify + +The Notify Command allows the Media Gateway to notify the Media Gateway Controller of events occurring within the Media Gateway. + +TerminationID + +``` +Notify(TerminationID, + ObservedEventsDescriptor, + [ErrorDescriptor]) +``` + +The TerminationID specifies the termination issuing the Notify Command. The TerminationID shall be a fully qualified name. + +The ObservedEvents Descriptor contains the RequestID and a list of events that the Media Gateway detected in the order that they were detected. Each event in the list is accompanied by parameters associated with the event and, optionally, an indication of the time that the event was detected. Procedures for sending Notify commands with RequestID equal to zero are for further study. + +Notify Commands with RequestID not equal to zero shall occur only as the result of detection of an event specified by an Events Descriptor which is active on the termination concerned. + +The RequestID returns the RequestID parameter of the Events Descriptor that triggered the Notify Command. It is used to correlate the notification with the request that triggered it. The events in the list must have been requested via the triggering Events Descriptor or embedded Events Descriptor unless the RequestID is zero (which is for further study). + +The Error Descriptor may be sent in the Notify Command as a result of Error 518 ("Event buffer full"). + +### 7.2.8 ServiceChange + +The ServiceChange Command allows the Media Gateway to notify the Media Gateway Controller that a termination, or group of terminations, is about to be taken out of service or has just been returned to service. The Media Gateway Controller may indicate that termination(s) shall be taken out of or returned to service. The Media Gateway may notify the MGC that the capability of a termination has changed. It also allows an MGC to hand over control of an MG to another MGC. + +TerminationIDList, + +[ServiceChangeDescriptor] + +ServiceChange(TerminationIDList, + +ServiceChangeDescriptor + +) + +The TerminationIDList specifies the termination(s) that are taken out of or returned to service. Wildcarding of termination names is permitted, with the exception that the CHOOSE mechanism shall not be used. Use of the "Root" TerminationID indicates a ServiceChange affecting the entire Media Gateway. + +NOTE – The use of TerminationIDList is not valid in the initial ITU-T H.248.1 Version 1 ServiceChange Command. + +#### 7.2.8.1 ServiceChange Descriptor contents + +The ServiceChange Descriptor contains the following parameters as required: + +- ServiceChangeMethod; +- ServiceChangeReason; +- ServiceChangeDelay; +- ServiceChangeAddress; +- ServiceChangeProfile; +- ServiceChangeVersion; +- ServiceChangeMgcID; +- TimeStamp; +- ExtensionParameter; +- ServiceChangeInfo; +- ServiceChangeIncompleteFlag. + +##### 7.2.8.1.1 ServiceChangeMethod + +The ServiceChangeMethod parameter specifies the type of ServiceChange that will or has occurred: + +- 1) Graceful: indicates that the specified terminations will be taken out of service after the specified ServiceChangeDelay; established connections are not yet affected, but the Media Gateway Controller should refrain from establishing new connections and should attempt to gracefully tear down existing connections on the termination(s) affected by the ServiceChange Command. The MG should set the termination's ServiceStates Property at the expiry of ServiceChangeDelay or the removal of the termination from an active context (whichever is first), to "OutOfService". + +- 2) **Forced:** indicates that the specified terminations were taken abruptly out of service and any established connections associated with them may be lost. For non-Root terminations, the MGC is responsible for cleaning up the context (if any) with which the failed termination is associated. At a minimum, the termination shall be subtracted from the context. The termination's ServiceStates Property should be "OutOfService". For the Root Termination, the MGC can assume that all connections are lost on the MG and thus can consider that all the terminations have been subtracted. +- 3) **Restart:** indicates that service will be restored on the specified terminations after expiration of the ServiceChangeDelay. The ServiceStates Property should be set to "InService" upon expiry of ServiceChangeDelay. Upon receipt of a ServiceChange Command on Root with ServiceChangeMethod Restart all terminations are assumed to be "InService". This includes physical and ephemeral terminations. Those terminations which are "OutOfService" may be reported by subsequent ServiceChange Commands with ServiceChangeMethod Forced. +- 4) **Disconnected:** always applied with the Root TerminationID, indicates that the MG lost communication with the MGC, but it was subsequently restored to the same MGC (possibly after trying other MGCs on a pre-provisioned list). Since MG state may have changed, the MGC may wish to use the Audit command to resynchronize its state with the MGs. +- 5) **Handoff:** sent from the MGC to the MG, this reason indicates that the MGC is going out of service and a new MGC association must be established. Sent from the MG to the MGC, this indicates that the MG is attempting to establish a new association in accordance with a Handoff received from the MGC with which it was previously associated. +- 6) **Failover:** sent from MG to MGC to indicate the primary MG is out of service and a secondary MG is taking over. This ServiceChange method is also sent from the MG to the MGC when the MG detects that MGC has failed. +- 7) Another value whose meaning is mutually understood between the MG and the MGC. + +##### 7.2.8.1.2 ServiceChangeReason + +The ServiceChangeReason parameter specifies the reason why the ServiceChange has or will occur. It consists of an alphanumeric token (IANA registered) and, optionally, an explanatory string. + +##### 7.2.8.1.3 ServiceChangeAddress and ServiceChangeMgcID + +The optional ServiceChangeAddress parameter specifies the address (e.g., IP port number for IP networks) to be used for subsequent communications. It can be specified in the input parameter descriptor or the returned result descriptor. + +The optional ServiceChangeMgcID parameter is of type Message Identifier (MID, see clause 8.3), the parameter format represents thus either an address (IP version 4 or 6 domain address, or broadband MTP3 address) or a name (IP domain name or a generic device name). In both cases, it is the parameter used for an unambiguous identification of an MGC entity (i.e., a primary or secondary MGC). + +NOTE 1 – There is the following difference between the name and address formats: the network address is routable, thus may be directly inserted as destination address in the signalling transport protocol data unit, whereas names require first a resolution into a routable address. The name-to-address resolution by the MG requires a local or remote DNS query request in case of the domain format, or a local mapping table in case of the device format. + +ServiceChangeAddress and ServiceChangeMgcID parameters must not both be present in the ServiceChange Descriptor or the ServiceChangeResult Descriptor. The ServiceChangeAddress provides an address to be used within the context of the association currently being negotiated, while the ServiceChangeMgcID provides an alternate address (see Note 2) where the MG should seek to establish another association. MGCs and MGs must be able to cope with the + +ServiceChangeAddress being either a full address or just a port number in the case of IP-based transports such as UDP, TCP or SCTP. + +NOTE 2 – In case of a name format, a previous name-to-address resolution is implied (see Note 1 above). + +##### 7.2.8.1.4 ServiceChangeDelay + +The optional ServiceChangeDelay parameter is expressed in seconds. If the delay is absent or set to zero, the delay value should be considered to be null. In the case of a "Graceful" ServiceChangeMethod, a null delay indicates that the Media Gateway Controller should wait for the natural removal of existing connections and should not establish new connections. For "Graceful" only, a null delay means the MG must not set ServiceStates "OutOfService" until the termination is in the NULL Context. + +##### 7.2.8.1.5 ServiceChangeProfile + +The optional ServiceChangeProfile parameter specifies the Profile (if any) of the protocol supported. The ServiceChangeProfile includes the version of the profile supported. In the absence of this parameter, the value "NoProfile" is assumed. + +##### 7.2.8.1.6 ServiceChangeVersion + +The optional ServiceChangeVersion parameter contains the protocol version and is used if protocol version negotiation occurs (see clause 11.3). + +##### 7.2.8.1.7 TimeStamp + +The optional TimeStamp parameter specifies the actual time as kept by the sender. As such, it is not necessarily absolute time according to, for example, a local time zone: it merely establishes an arbitrary starting time against which all future timestamps transmitted by a sender during this association shall be compared. It can be used by the responder to determine how its notion of time differs from that of its correspondent. TimeStamp is sent with a precision of hundredths of a second. + +##### 7.2.8.1.8 ExtensionParameter + +The optional Extension parameter may contain any value whose meaning is mutually understood by the MG and MGC. The value "X-SC" is reserved for the use of signalling ServiceChange parameters that have been added as a result of ITU-T H.248.1 version 3 (and subsequent versions). It is only used in the initial ITU-T H.248.1 version 1 coded ServiceChange Command from the MG to MGC when the ServiceChangeVersion is greater than or equal to 3. The structure of the value is defined by the following ABNF: + +$$\text{X-SC} = 1 * (\text{NAME EQUAL parmValue [COMMA]})$$ + +The value is encoded using the String type (see clause 12.1.2). NOTE – When multiple NAME EQUAL parmValue constructs are used, the COMMA shall be used to separate them. + +When adding new ServiceChange parameters it is recommended that a name/value be assigned if the parameter is to be sent in an initial ServiceChange. For example: + +**Name:** Strings of up to 64 characters, containing no spaces, starting with an alphabetic character and consisting of alphanumeric characters and/or digits, and possibly including the special character underscore ("\_"). + +**Type:** As per clause 12.1.2 "Properties". When using the "String" type, the values shall be compliant to the SafeChar syntax (see clause B.2). + +**Possible values:** As per clause 12.1.2 "Properties" + +##### 7.2.8.1.9 ServiceChangeInfo + +The optional ServiceChangeInfo parameter may contain the package/property/signal/event/statistic of the reason that caused the ServiceChange. + +##### 7.2.8.1.10 ServiceChangeIncompleteFlag + +This optional flag indicates that subsequent ServiceChange Commands will be sent from the MG to the MGC indicating the state of terminations. It is only used during MG registration or restart (ServiceChange on Root with ServiceChangeMethod Restart) when the MG wants to report the entire MG and termination state to the MGC. Upon reception of this flag, the MGC shall refrain from generating commands operating on terminations other than Root to the MG. After sending the ServiceChangeIncompleteFlag in the initial registration/restart command, the MG shall send it in all subsequent ServiceChange Commands until the MG has determined that it has reported the current state of the MG and its terminations. The flag shall then be removed from the last ServiceChange Command indicating the state of the MG or its terminations. Upon the reception of this ServiceChange without the ServiceChangeIncompleteFlag, the MGC may again generate commands to the MG. When this flag is sent in an initial ServiceChange (ITU-T H.248.1 Version 1) Command using the ServiceChange extension parameter "X-SC" the following is used: + +**Name:** SIC + +**Type:** Boolean + +**Possible values:** ON: Flag included + +NOTE – The value OFF is not required as subsequent commands will be ITU-T H.248.1 Version 3 encoded. + +##### 7.2.8.1.11 ServiceChange Command and Response + +A ServiceChange Command specifying the "Root" for the TerminationID and ServiceChangeMethod equal to Restart is a registration command by which a Media Gateway announces its existence to the Media Gateway Controller. The Media Gateway may register by specifying the Root TerminationID and ServiceChangeMethod equal to Failover when the MG detects MGC failures. A message containing a ServiceChange Command specifying the Root TerminationID and ServiceChangeMethod equal to Restart or Failover shall not contain other commands as these commands should use the new ServiceChangeAddress and negotiated protocol version. + +The Media Gateway is expected to be provisioned with the name of one primary and optionally some number of alternate Media Gateway Controllers. + +Acknowledgement of the ServiceChange Command completes the registration process, except when the MGC has returned an alternative ServiceChangeMgcID as described below. + +The MG may specify the transport ServiceChangeAddress to be used by the MGC for sending messages in the ServiceChangeAddress parameter in the input ServiceChange Descriptor. The MG may specify an address in the ServiceChangeAddress parameter of the ServiceChange request, and the MGC may also do so in the ServiceChange reply. In either case, the recipient must use the supplied address as the destination for all subsequent transaction requests within the association. At the same time, as indicated in clause 9, transaction replies and pending indications must be sent to the address from which the corresponding requests originated. This must be done even if it implies extra messaging because commands and responses cannot be packed together. + +The TimeStamp parameter shall be sent with a registration command and its response. + +At registration the MG may send the ServiceChangeIncompleteFlag if it has determined that the MG is in state "InService" but individual terminations may be in state "OutOfService". This is to prevent attempted seizure of out-of-service terminations. Subsequent ServiceChange Commands are used to report the "OutOfService" terminations. + +The Media Gateway Controller may return a ServiceChangeMgcID parameter that describes the Media Gateway Controller that should preferably be contacted for further service by the Media Gateway. In this case, the Media Gateway shall reissue the ServiceChange Command to the new Media Gateway Controller. The MGC specified in a ServiceChangeMgcID, if provided, shall be + +contacted before any further alternate MGCs. On a handoff message from MGC to MG, the ServiceChangeMgcID is the new MGC that will take over from the current MGC. + +The return from ServiceChange is empty except when the Root TerminationID is used. In that case, it includes the following parameters as required: + +- ServiceChangeAddress, if the responding MGC wishes to specify a new destination for messages from the MG for the remainder of the association; +- ServiceChangeMgcID, if the responding MGC does not wish to sustain an association with the MG; +- ServiceChangeProfile, if the responder wishes to negotiate the profile to be used for the association. The profile (name and version) is only returned in the reply in the case that the MGC cannot support the specified profiles in the ServiceChangeRequest. The returned reply shall indicate the profile and version supported or "NoProfile" if no profile is supported. Upon reception of a profile in the reply the MG may continue the relationship with the current MGC or contact secondary MGCs and establish a relationship with them. If the MGC returned a profile in the reply other than the one that was provided in the request the MG shall: + - a) issue a new ServiceChange Command with an agreed profile to confirm to the MGC that the MG has agreed with the profile; or + - b) consider the registration stage completed and await further commands from the MGC; the MGC will use the profile that it sent in the ServiceChange Reply; or + - c) initiate a control association with a different MGC using its original profile.NOTE – In order to ensure both the MGC and MG are using the same profile, option a) is encouraged. +- ServiceChangeVersion, if the responder wishes to negotiate the version of the protocol to be used for the association. + +ServiceChangeReasons are defined in [ITU-T H.248.8]. The list may be extended by an IANA registration as outlined in clause 14.3. + +### 7.2.9 Manipulating and auditing context attributes + +The commands of the protocol as discussed in the preceding subclauses apply to terminations. This clause specifies how contexts are manipulated and audited. + +An action may contain context manipulation and auditing instructions (see clause 8). + +An action request sent to an MG may include a request to audit attributes of a context. There are two types of audit: + +**Value Audit:** The MGC may audit a specific context to determine the current value of individual context properties. The MGC may determine the current values for all existing (non-NULL) contexts by specifying ContextID ALL in the Audit request. If context attributes are added, or have been modified by the same action as the Audit request, the value(s) returned shall be after the action has been applied. Context attributes can be used as selection criteria to filter the audit return values. It is possible to include multiple selection criteria. When multiple criteria are included, either an AND or an OR logic operation may also be included to indicate how the selection criteria are to be interpreted. If no logic operation is included, an AND logic operation is assumed. + +**Capabilities Audit:** The MGC may audit a specific context to determine the possible values that individual context properties can assume. The MGC may determine the possible values for the entire MG by specifying ContextID ALL in the audit request. + +The following illustrates information that can be obtained with a Context Audit: + +| ContextID | TerminationID | AuditValue | AuditCapability | +|-----------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| Specific | Not Applicable | Context property's value in the specified context. | Context property's possible values in the specified context. | +| NULL | Not Applicable | Not Allowed | Not Allowed | +| ALL | Not Applicable | Current values for all existing (non-NULL) contexts by specifying ContextID ALL in the Audit request.
A response for ContextID ALL is presented through an actionReply per context. | A response of ContextID ALL is returned with context property's possible values across the entire MG. | + +An action may also include a request to change the attributes of a context. + +The context properties that may be included in an action reply are used to return information to an MGC. This can be information requested by an audit of context attributes or details of the effect of manipulation of a context. + +If an MG receives an action that contains both a request to audit context attributes and a request to manipulate those attributes, the response shall include the values of the attributes after processing the manipulation request. + +### 7.2.10 Generic command syntax + +The protocol can be encoded in a binary format or in a text format. MGCs should support both encoding formats. MGs may support both formats. + +The protocol syntax for the binary format of the protocol is defined in Annex A. Annex C specifies the encoding of the Local and Remote Descriptors for use with the binary format. + +A complete ABNF of the text encoding of the protocol per [IETF RFC 2234] is given in Annex B. SDP is used as the encoding of the Local and Remote Descriptors for use with the text encoding as modified in clause 7.1.8. + +# 8 Transactions + +Commands between the Media Gateway Controller and the Media Gateway are grouped into transactions, each of which is identified by a TransactionID. Transactions consist of one or more actions. An action consists of a non-empty series of commands, context property modifications, or context property audits that are limited to operating within a single context. Consequently, each action typically specifies a ContextID. However, there are two circumstances where a specific ContextID is not provided with an action. One is the case of modification of a termination outside of a context. The other is where the controller requests the gateway to create a new context. Figure 15 is a graphic representation of the transaction, action and command relationships. + +![Diagram illustrating Transactions, actions and commands. The diagram shows three nested transaction boxes labeled TRANSACTIONx, CTXTID1, CTXTID2, and CTXTID3. CTXTID1 contains four commands: COMMAND1, COMMAND2, COMMAND3, and COMMAND4. CTXTID2 contains one command: COMMAND1. CTXTID3 contains three commands: COMMAND1, COMMAND2, and COMMAND3.](af6c3f383ddc0c142cdd7e186cc78199_img.jpg) + +``` + +graph TD + subgraph TRANSACTIONx + subgraph CTXTID1 + COMMAND1_1[COMMAND1] + COMMAND2_1[COMMAND2] + COMMAND3_1[COMMAND3] + COMMAND4_1[COMMAND4] + end + subgraph CTXTID2 + COMMAND1_2[COMMAND1] + end + subgraph CTXTID3 + COMMAND1_3[COMMAND1] + COMMAND2_3[COMMAND2] + COMMAND3_3[COMMAND3] + end + end + +``` + +Diagram illustrating Transactions, actions and commands. The diagram shows three nested transaction boxes labeled TRANSACTIONx, CTXTID1, CTXTID2, and CTXTID3. CTXTID1 contains four commands: COMMAND1, COMMAND2, COMMAND3, and COMMAND4. CTXTID2 contains one command: COMMAND1. CTXTID3 contains three commands: COMMAND1, COMMAND2, and COMMAND3. + +H.248.1 v3(13)\_F15 + +**Figure 15 – Transactions, actions and commands** + +Transactions are presented as TransactionRequests. Corresponding responses to a TransactionRequest are received in a single reply, possibly preceded by a number of TransactionPending messages (see clause 8.2.3). + +Transactions guarantee ordered command processing. That is, commands within a transaction are executed sequentially. Ordering of transactions is not guaranteed; transactions may be executed in any order, or simultaneously; however, TransactionReplies should be executed before TransactionRequests when both are contained in a message. + +At the first failing command in a transaction, processing of the remaining commands in that transaction stops. If a command contains a wildcarded TerminationID, the command is attempted with each of the actual TerminationIDs matching the wildcard. A response within the TransactionReply is included for each matching TerminationID, even if one or more instances generated an error. If the MG cannot return a TerminationID in response to a wildcarded termination then the original wildcard TerminationID should be returned. If any TerminationID matching a wildcard results in an error when executed, any commands following the wildcarded command are not attempted. + +Commands may be marked as "Optional" which can override this behaviour – if a command marked as Optional results in an error, subsequent commands in the transaction will be executed. If a command fails, the MG shall, as far as possible, restore the state that existed prior to the attempted execution of the command before continuing with command processing. + +A TransactionReply includes the results for all of the commands in the corresponding TransactionRequest. The TransactionReply includes the return values for the commands that were executed successfully, and the command and Error Descriptor for any command that failed. Command replies are returned in the order in which they appeared in the corresponding TransactionRequest. TransactionPending is used to periodically notify the receiver that a transaction has not completed yet, but is actively being processed. + +Applications should implement an application level timer per transaction. Expiration of the timer should cause a retransmission of the request. Receipt of a Reply should cancel the timer. Receipt of Pending should restart the timer. + +## 8.1 Common parameters + +### 8.1.1 Transaction identifiers + +Transactions are identified by a TransactionID, which is assigned by sender and is unique within the scope of the sender. A response containing an Error Descriptor to indicate that the TransactionID is missing in a request shall use a TransactionID of zero in the corresponding TransactionReply. + +### 8.1.2 Context identifiers + +Contexts are identified by a ContextID, which is assigned by the Media Gateway and is unique within the scope of the Media Gateway. The Media Gateway Controller shall use the ContextID supplied by the Media Gateway in all subsequent transactions relating to that context. The protocol makes reference to a distinguished value that may be used by the Media Gateway Controller when referring to a termination that is currently not associated with a context, namely the *NULL* ContextID. + +The CHOOSE wildcard is used to request that the Media Gateway create a new context. + +The MGC may use the ALL wildcard to address all contexts on the MG. The NULL Context is not included when the ALL wildcard is used. + +The MGC shall not use partially specified ContextIDs containing the CHOOSE or ALL wildcards. + +## 8.2 Transaction application programming interface + +Following is an Application Programming Interface (API) describing the transactions of the protocol. This API is shown to illustrate the transactions and their parameters and is not intended to specify implementation (e.g., via use of blocking function calls). It will describe the input parameters and return values expected to be used by the various transactions of the protocol from a very high level. Transaction syntax and encodings are specified in later subclauses. + +### 8.2.1 TransactionRequest + +The TransactionRequest is invoked by the sender. There is one transaction per request invocation. A request contains one or more actions, each of which specifies its target context. + +``` +TransactionRequest(TransactionID { + ContextID {Command ... Command}, + ... + ContextID {Command ... Command}}) +``` + +The TransactionID parameter must specify a value for later correlation with the TransactionReply or TransactionPending response from the receiver. + +The ContextID parameter must specify a value to pertain to all commands that follow up to either the next specification of a ContextID parameter or the end of the TransactionRequest, whichever comes first. + +The command parameter represents one of the commands mentioned in clause 7.2 ("Command application programming interface"). + +### 8.2.2 TransactionReply + +The TransactionReply is invoked by the receiver. There is one reply invocation per transaction. A reply contains one or more actions, each of which must specify its target context and one or more Responses per context. A reply may be segmented into multiple messages. The TransactionReply is invoked by the responder when it has processed the TransactionRequest. + +A TransactionRequest has been processed: + +- when all actions in that TransactionRequest have been processed; or +- when an error is encountered in processing that TransactionRequest, except when the error is in an optional command. + +If a message contains more TransactionRequests than the receiver can process, the receiver will return Error Descriptor 413 ("Number of transactions in message exceeds maximum"). + +A command has been processed when all descriptors in that command have been processed. + +A Signals Descriptor is considered to have been processed when it has been established that the descriptor is syntactically valid, the requested signals are supported and they have been queued to be applied. + +An Events Descriptor or EventBuffer Descriptor is considered to have been processed when it has been established that the descriptor is syntactically valid, the requested events can be observed, any embedded signals can be generated, any embedded events can be detected, and the MG has been brought into a state in which the events will be detected. + +``` +TransactionReply(TransactionID { + ContextID {Response ... Response}, + ... + ContextID {Response ... Response}}) +``` + +The TransactionID parameter must be the same as that of the corresponding TransactionRequest. + +The ContextID parameter must specify a value to pertain to all Responses for the action. The ContextID may be specific, ALL or NULL. + +Each of the Response parameters represents a return value as mentioned in clause 7.2 or an Error Descriptor if the command execution encountered an error. Commands after the point of failure are not processed and, therefore, Responses are not issued for them. + +An exception to this occurs if a command has been marked as optional in the TransactionRequest. If the optional command generates an error, the transaction still continues to execute, so the Reply would, in this case, have Responses after an Error. + +Clause 7.1.20 ("Error Descriptor") specifies the generation of Error Descriptors. The text below discusses several individual cases. + +If the receiver encounters an error in processing a ContextID but can parse the ContextID, the requested action response will consist of the ContextID and a single Error Descriptor, 422 ("Syntax Error in Action"). If the receiver cannot parse the ContextID, it will return a TransactionReply consisting of the TransactionID and a single Error Descriptor, 422 (Syntax Error in Action). + +If the receiver encounters an error such that it cannot determine a legal action, it will return a TransactionReply consisting of the TransactionID and a single Error Descriptor, 422 ("Syntax Error in Action"). If the end of an action cannot be reliably determined but one or more commands can be parsed, the receiver will process the commands and then send 422 ("Syntax Error in Action") as the last action for the transaction. If the receiver encounters an error such that it cannot determine a legal transaction, it will return a TransactionReply with a NULL TransactionID and a single Error Descriptor 403 ("Syntax Error in TransactionRequest"). + +If the end of a transaction cannot be reliably determined and one or more actions can be parsed, the receiver will process the actions and then return 403 ("Syntax Error in TransactionRequest") as the last action reply for the transaction. If no actions can be parsed, it will return 403 ("Syntax Error in TransactionRequest") as the only reply. + +If the TerminationID cannot be reliably determined, it will send 442 ("Syntax Error in Command") as the action reply. + +If the end of a command cannot be reliably determined, it will return 442 ("Syntax Error in Command") as the reply to the last action it can parse. + +### 8.2.3 TransactionPending + +The receiver invokes the TransactionPending. A TransactionPending indicates that the transaction is actively being processed, but has not been completed. It is used to prevent the sender from assuming the TransactionRequest was lost where the transaction will take some time to complete. + +TransactionPending(TransactionID { } ) + +The TransactionID parameter must be the same as that of the corresponding TransactionRequest. A property of the Root Termination (normalMGExecutionTime) is settable by the MGC to indicate the interval within which the MGC expects a response to any transaction from the MG (exclusive of network delay). Another property (normalMGCExecutionTime) is settable by the MGC to indicate the interval within which the MG should expect a response to any transaction from the MGC (exclusive of network delay). MGProvisionalResponseTimerValue indicates the time within which the MGC should expect a Pending Response from the MG if a transaction cannot be completed (initially set to normalMGExecutionTime plus network delay, but may be lowered). MGProvisionalResponseTimerValue has the corresponding meaning to the MG. Senders may receive more than one TransactionPending for a command. If a duplicate request is received when pending, the responder may send a duplicate pending immediately, or continue waiting for its timer to trigger another TransactionPending. + +A property of the Root Termination (MGOriginatedPendingLimit) is settable by the MGC to indicate the number of TransactionPendings that can be received from the MG. When the value expressed by this property is exceeded, the MG shall stop the transaction processing and send back a TransactionReply, otherwise the MGC can assume the transaction to be in error. + +Another property of the Root Termination (MGCOOriginatedPendingLimit) is settable by the MGC to indicate the number of TransactionPendings that can be received from the MGC. When the value expressed by this property is exceeded, the MGC shall stop the transaction processing and send back a TransactionReply otherwise the MG can assume the transaction to be in error. + +The xxxOriginatedPendingLimit (MGOriginatedPendingLimit or MGCOOriginatedPendingLimit) may be exceeded either because of long command processing or due to an error (e.g., a command caused a loop). In both cases, the receiver of the original TransactionRequest will issue a TransactionReply with an Error Descriptor as a response parameter in correspondence with either the offending long command or the command that caused the error. Further commands in the transaction shall not be processed. Error 506 (Number of TransactionPendings Exceeded) shall be used. + +NOTE – To prevent a situation where the xxxOriginatedPendingLimit (MGOriginatedPendingLimit or MGCOOriginatedPendingLimit) is exceeded due to an error and the receiver of the original TransactionRequest keeps sending TransactionPending, the receiver of the original TransactionRequest should implement a management protection mechanism in order to trigger the appropriate recovery actions. The sender of the original TransactionRequest may keep track of the number of received Pendings and initiate corrective actions. + +## 8.3 Messages + +Multiple transactions can be concatenated into a Message. Messages have a header, which includes the identity of the sender. The Message Identifier (MID) of a message is set to a provisioned name (e.g., domain address/domain name/device name) of the entity transmitting the message. Domain name is a suggested default. An ITU-T H.248.1 entity (MG/MGC) must consistently use the same MID in all messages it originates for the duration of control association with the peer (MGC/MG). + +Every message contains a version number identifying the version of the protocol the message conforms to. Versions consist of one or two digits, beginning with version 1. The current version of the protocol is version 3. + +The transactions in a message are treated independently. There is no order implied; there is no application or protocol acknowledgement of a message. A message is essentially a transport mechanism. For example, message X containing transaction requests A, B, and C may be responded to with message Y containing replies to A and C and message Z containing the reply to B. Likewise, message L containing request D and message M containing request E may be responded to with message N containing replies to both D and E. + +# 9 Transport + +The transport mechanism for the protocol should allow the reliable transport of transactions between an MGC and MG. The transport shall remain independent of what particular commands are being sent, and shall be applicable to all application states. There are several transports defined for the protocol, which are defined in annexes to this Recommendation and other ITU-T H.248 Subseries Recommendations (e.g., [ITU-T H.248.4] and [ITU-T H.248.5]). Additional transports may be defined as additional Recommendations in the ITU-T H.248 subseries Recommendations. For transport of the protocol over IP, MGCs shall implement both TCP and UDP/ALF; an MG shall implement TCP or UDP/ALF or both. + +The MG is provisioned with a name or address (such as a DNS name or IP address) of a primary and zero or more secondary MGCs (see clause 7.2.8) that is the address the MG uses to send messages to the MGC. If TCP or UDP is used as the protocol transport, and the port to which the initial ServiceChange request is to be sent is not otherwise known, that request should be sent to the default port number for the protocol. This port number is 2944 for text-encoded operation or 2945 for binary-encoded operation, for either UDP or TCP. The MGC receives the message containing the ServiceChange request from the MG and can determine the MG's address from it. As described in clause 7.2.8, either the MG or the MGC may supply an address in the ServiceChangeAddress parameter to which subsequent transaction requests must be addressed, but responses (including the response to the initial ServiceChange request) must always be sent back to the address which was the source of the corresponding request. For example, in IP networks, this is the source address in the IP header and the source port number in the TCP/UDP/SCTP header. + +## 9.1 Ordering of commands + +This Recommendation does not mandate that the underlying transport protocol guarantees the sequencing of transactions sent to an entity. This property tends to maximize the timeliness of actions, but it has a few drawbacks. For example: + +- Notify commands may be delayed and arrive at the MGC after the transmission of a new command changing the Events Descriptor. +- If a new command is transmitted before a previous one is acknowledged, there is no guarantee that prior command will be executed before the new one. + +Media Gateway Controllers that want to guarantee consistent operation of the Media Gateway may use the following rules. These rules are with respect to commands that are in different transactions. Commands that are in the same transaction are executed in order (see clause 8). + +- 1) When a Media Gateway handles several terminations, commands pertaining to the different terminations may be sent in parallel, for example following a model where each termination (or group of terminations) is controlled by its own process or its own thread. + +- 2) On a termination, there should normally be, at most, one outstanding command (Add or Modify or Move), unless the outstanding commands are in the same transaction. However, a Subtract command may be issued at any time. In consequence, a Media Gateway may sometimes receive a Modify command that applies to a previously subtracted termination. Such commands should be ignored, and an error code should be returned. +- 3) For transports that do not guarantee in-sequence delivery of messages (i.e., UDP), there should normally be, on a given termination, at most one outstanding Notify command at any time. +- 4) In some cases, an implicitly, or explicitly, wildcarded Subtract Command that applies to a group of terminations may step in front of a pending Add Command. The Media Gateway Controller should individually delete all terminations for which an Add Command was pending at the time of the global Subtract Command. Also, new Add Commands for terminations named by the wildcarding (or implied in a Multiplex Descriptor) should not be sent until the wildcarded Subtract Command is acknowledged. +- 5) AuditValue and AuditCapability are not subject to any sequencing. +- 6) ServiceChange shall always be the first command sent by an MG as defined by the restart procedure. Any other command or response must be delivered after this ServiceChange Command. + +These rules do not affect the command responder, which should always respond to commands. + +## 9.2 Protection against restart avalanche + +In the event that a large number of Media Gateways are powered on simultaneously, and they were to all initiate a ServiceChange transaction, the Media Gateway Controller would very likely be swamped, leading to message losses and network congestion during the critical period of service restoration. In order to prevent such avalanches, the following behaviour is suggested: + +- 1) When a Media Gateway is powered on, it should initiate a restart timer to a random value, uniformly distributed between zero and a maximum waiting delay (MWD). Care should be taken to avoid synchronicity of the random number generation between multiple Media Gateways that would use the same algorithm. +- 2) The Media Gateway should then wait for either the end of this timer or the detection of a local user activity, such as for example an off-hook transition on a residential Media Gateway. +- 3) When the timer elapses, or when an activity is detected, the Media Gateway should initiate the restart procedure. + +The restart procedure simply requires the MG to guarantee that the first message that the Media Gateway Controller sees from this MG is a ServiceChange message informing the Media Gateway Controller about the restart. + +NOTE – The value of MWD is a configuration parameter that depends on the type of the Media Gateway. The following reasoning may be used to determine the value of this delay on residential gateways. + +Media Gateway Controllers are typically dimensioned to handle the peak hour traffic load, during which, on average, 10% of the lines will be busy, placing calls whose average duration is typically three minutes. The processing of a call typically involves five to six Media Gateway Controller transactions between each Media Gateway and the Media Gateway Controller. This simple calculation shows that the Media Gateway Controller is expected to handle five to six transactions for each termination, every 30 minutes on average, or, to put it otherwise, about one transaction per termination every five to six minutes on average. This suggests that a reasonable value of MWD for a residential gateway would be 10 to 12 minutes. In the absence of explicit configuration, residential gateways should adopt a value of 600 seconds for MWD. + +The same reasoning suggests that the value of MWD should be much shorter for trunking gateways or for business gateways, because they handle a large number of terminations, and also because the usage rate of these terminations is much higher than 10% during the peak busy hour, a typical value being 60%. These terminations, during the peak hour, are thus expected to contribute about one transaction per minute to the Media Gateway Controller load. A reasonable algorithm is to make the value of MWD per "trunk" termination six times shorter than the MWD per residential gateway, and also inversely proportional to the number of terminations that are being restarted. For example, MWD should be set to 2.5 seconds for a gateway that handles a T1 line, or to 60 milliseconds for a gateway that handles a T3 line. + +## 9.3 Protection against Notify avalanche + +If a circumstance arises at an MG where a substantial number of notifications accumulate, either because of transmission difficulties or because the MG recognized a number of events in a short time period, the MG should send the notifications in a restricted manner until the backlog is cleared. + +# 10 Security considerations + +This clause covers security when using the protocol in an IP environment. + +## 10.1 Protection of protocol connections + +A security mechanism is clearly needed to prevent unauthorized entities from using the protocol defined in this Recommendation for setting up unauthorized calls or interfering with authorized calls. The security mechanism for the protocol when transported over IP networks is IPSec ([IETF RFC 2401] to [b-IETF RFC 2411]). + +The AH header [IETF RFC 2402] affords data origin authentication, connectionless integrity and optional anti-replay protection of messages passed between the MG and the MGC. The ESP header [IETF RFC 2406] provides confidentiality of messages, if desired. For instance, the ESP encryption service should be requested if the session descriptions are used to carry session keys, as defined in SDP. + +Implementations of the protocol defined in this Recommendation employing the ESP header shall comply with section 5 of [IETF RFC 2406], which defines a minimum set of algorithms for integrity checking and encryption. Similarly, implementations employing the AH header shall comply with section 5 of [IETF RFC 2402], which defines a minimum set of algorithms for integrity checking using manual keys. + +Implementations should use IKE [IETF RFC 2409] to permit more robust keying options. Implementations employing IKE should support authentication with RSA signatures and RSA public key encryption. + +## 10.2 Interim AH scheme + +Implementation of IPSec requires that the AH or ESP header be inserted immediately after the IP header. This cannot be easily done at the application level. Therefore, this presents a deployment problem for the protocol defined in this Recommendation where the underlying network implementation does not support IPSec. + +As an interim solution, an optional AH header is defined within the ITU-T H.248.1 protocol header. The header fields are exactly those of the SPI, SEQUENCE NUMBER and DATA fields as defined in [IETF RFC 2402]. The semantics of the header fields are the same as the "transport mode" of [IETF RFC 2402], except for the calculation of the Integrity Check Value (ICV). In IPSec, the ICV is calculated over the entire IP packet including the IP header. This prevents spoofing of the IP addresses. To retain the same functionality, the ICV calculation should be performed across all the transactions (concatenated) in the message prepended by a synthesized IP header consisting of a + +32-bit source IP address, a 32-bit destination address and a 16-bit UDP destination port encoded as 20 hex digits. When the interim AH mechanism is employed when TCP is the transport Layer, the UDP Port above becomes the TCP port, and all other operations are the same. + +Implementations of the ITU-T H.248.1 protocol shall implement IPSec where the underlying operating system and the transport network supports IPSec. Implementations of the protocol using IPv4 shall implement the interim AH scheme. However, this interim scheme shall not be used when the underlying network layer supports IPSec. IPv6 implementations are assumed to support IPSec and shall not use the interim AH scheme. + +All implementations of the interim AH mechanism shall comply with section 5 of [IETF RFC 2402] which defines a minimum set of algorithms for integrity checking using manual keys. + +The interim AH interim scheme does not provide protection against eavesdropping, thus forbidding third parties from monitoring the connections set up by a given termination. Also, it does not provide protection against replay attacks. These procedures do not necessarily protect against denial of service attacks by misbehaving MGs or misbehaving MGCs. However, they will provide an identification of these misbehaving entities, which should then be deprived of their authorization through maintenance procedures. + +## 10.3 Protection of media connections + +The protocol allows the MGC to provide MGs with "session keys" that can be used to encrypt the audio messages, protecting against eavesdropping. + +A specific problem of packet networks is "uncontrolled barge-in". This attack can be performed by directing media packets to the IP address and UDP port used by a connection. If no protection is implemented, the packets must be decompressed and the signals must be played on the "line side". + +A basic protection against this attack is to only accept packets from known sources, checking for example that the IP source address and UDP source port match the values announced in the Remote Descriptor. This has two inconveniences: it slows down connection establishment and it can be fooled by source spoofing: + +- To enable the address-based protection, the MGC must obtain the remote session description of the egress MG and pass it to the ingress MG. This requires at least one network round trip, and leaves us with a dilemma: allow the call to proceed without waiting for the round trip to complete and risk, for example, "clipping" a remote announcement, or wait for the full round trip and settle for slower call-set up procedures. +- Source spoofing is only effective if the attacker can obtain valid pairs of source destination addresses and ports, for example, by listening to a fraction of the traffic. To fight source spoofing, one could try to control all access points to the network. But this is in practice very hard to achieve. + +An alternative to checking the source address is to encrypt and authenticate the packets, using a secret key that is conveyed during the call set-up procedure. This will not slow down the call set-up, and provides strong protection against address spoofing. + +# 11 MG-MGC control interface + +The control association between MG and MGC is initiated at MG cold start, and announced by a ServiceChange message, but can be changed by subsequent events, such as failures or manual service events. + +NOTE – While the protocol does not have an explicit mechanism to support multiple MGCs controlling a physical MG, it has been designed to support the multiple logical MGs (within a single physical MG) that can be associated with different MGCs. + +## 11.1 Multiple Virtual MGs + +A physical Media Gateway may be partitioned into one or more Virtual MGs (VMGs). A Virtual MG consists of a set of statically partitioned physical terminations and/or sets of ephemeral terminations. A physical termination is controlled by one MGC. The model does not require that other resources be statically allocated, just terminations. The mechanism for allocating terminations to Virtual MGs is a management method outside the scope of this Recommendation. Each of the Virtual MGs appears to the MGC as a complete MG client. + +A physical MG may have only one network interface, which must be shared across Virtual MGs. In such a case, the packet/cell side termination is shared. It should be noted however, that in use, such interfaces require an ephemeral instance of the termination to be created per flow, and thus sharing the termination is straightforward. This mechanism does lead to a complication, namely that the MG must always know which of its controlling MGCs should be notified if an event occurs on the interface. + +In normal operation, the Virtual MG will be instructed by the MGC to create network flows (if it is the originating side), or to expect flow requests (if it is the terminating side), and no confusion will arise. However, if an unexpected event occurs, the Virtual MG must know what to do with respect to the physical resources it is controlling. + +If recovering from the event requires manipulation of a physical interface's state, only one MGC should do so. These issues are resolved by allowing any of the MGCs to create Events Descriptors to be notified of such events, but only one MGC can have read/write access to the physical interface properties; all other MGCs have read-only access. The management mechanism is used to designate which MGC has read/write capability, and is designated the Master MGC. + +Each Virtual MG has its own Root Termination. In most cases, the values for the properties of the Root Termination are independently settable by each MGC. Where there can only be one value, the parameter is read-only to all but the Master MGC. + +ServiceChange may only be applied to a termination or set of terminations partitioned to the Virtual MG or created (in the case of ephemeral terminations) by that Virtual MG. + +## 11.2 Cold start + +An MG is pre-provisioned by a management mechanism outside the scope of this Recommendation with a primary and (optionally) an ordered list of secondary MGCs. Upon a cold start of the MG, it will issue a ServiceChange Command with a "Restart" method, on the Root Termination to its primary MGC. If the MGC accepts the MG, it sends a TransactionReply not including a ServiceChangeMgcID parameter. If the MGC does not accept the MG's registration, it sends a TransactionReply, providing the address of an alternate MGC to be contacted by including a ServiceChangeMgcID parameter. + +If the MG receives a TransactionReply that includes a ServiceChangeMgcID parameter, it sends a ServiceChange to the MGC specified in the ServiceChangeMgcID. It continues this process until it gets a controlling MGC to accept its registration, or it fails to get a reply. Upon failure to obtain a reply, either from the primary MGC, or a designated successor, the MG tries its pre-provisioned secondary MGCs, in order. If the MG is unable to establish a control relationship with any MGC, it shall wait a random amount of time as described in clause 9.2 and then start contacting its primary, and if necessary, its secondary MGCs again. + +It is possible that the reply to a ServiceChange with Restart will be lost, and a command will be received by the MG prior to the receipt of the ServiceChange response. The MG shall issue Error Code 505 ("TransactionRequest Received before a ServiceChange Reply has been received"). + +## 11.3 Negotiation of protocol version + +A ServiceChange Command from an MG that registers with an MGC shall contain the version number of the protocol supported by the MG in the ServiceChangeVersion parameter. Upon receiving such a message, if the MGC supports only a lower version, then the MGC shall send a ServiceChange Reply with the lower version in the ServiceChangeVersion parameter and, thereafter, all the messages between MG and MGC shall be encoded and conform to the lower version of the protocol. If the MG is unable to comply, and it has established a transport connection to the MGC, it should close that connection. In any event, it should reject all subsequent requests from the MGC with Error Code 406 ("Version Not Supported"). + +Regardless of the version placed in the ServiceChangeVersion parameter, the message containing the initial ServiceChange request and response shall be encoded as a version 1 message. + +If the MGC only supports higher version(s) than the MG, it shall reject the association with Error Code 406 ("Version Not Supported"). + +If the MGC supports the version indicated by the MG, both the MGC and MG shall conform to that version in all subsequent messages after the ServiceChange Reply from the MGC. In this case it is optional for the MGC to return a version in the ServiceChange Reply. Any subsequent messaging that does not conform to the negotiated version shall be rejected with Error Code 406 ("Version Not Supported"). + +Protocol version negotiation may also occur at "Handoff" and "Failover" ServiceChanges. + +For rules regarding protocol extension see clause 11.7. + +## 11.4 Failure of an MG + +If an MG fails, but is capable of sending a message to the MGC, it sends a ServiceChange with an appropriate method (Graceful or Forced) and specifies the Root TerminationID. When it returns to service, it sends a ServiceChange with a "Restart" ServiceChangeMethod. + +Allowing the MGC to send duplicate messages to both MGs accommodates pairs of MGs that are capable of redundant failover of one of the MGs. Only the Working MG shall accept or reject transactions. Upon failover, the primary MG sends a ServiceChange Command with a "Failover" method and a "MG Impending Failure" reason. The MGC then uses the secondary MG as the active MG. When the error condition is repaired, the working MG can send a "ServiceChange" with a "Restart" ServiceChangeMethod. + +NOTE – Redundant failover MGs require a reliable transport, because the protocol provides no means for a secondary MG running ALF to acknowledge messages sent from the MGC. + +## 11.5 Failure of an MGC + +If the MG detects a failure of its controlling MGC, it attempts to contact the next MGC on its pre-provisioned list. It starts its attempts at the beginning (primary MGC), unless that was the MGC that failed, in which case it starts at its first secondary MGC. It sends a ServiceChange message with a "Failover" method and a "MGC Impending Failure" reason. If the MG is unable to establish a control relationship with any MGC, it shall wait a random amount of time as described in clause 9.2 and then start again contacting its primary, and (if necessary) its secondary MGCs. When contacting its previously controlling MGC, the MG sends the ServiceChange message with "Disconnected" method. + +In partial failure, or for manual maintenance reasons, an MGC may wish to direct its controlled MGs to use a different MGC. To do so, it sends a ServiceChange command to the MG with a "Handoff" method, and its designated replacement in ServiceChangeMgcID. If "Handoff" is supported, the MG shall send a ServiceChange message with a "Handoff" method and a "MGC directed change" reason to the designated MGC. If it fails to get a reply from the designated MGC, + +the MG shall behave as if its MGC failed, and start contacting secondary MGCs as specified in the previous paragraph. If the MG is unable to establish a control relationship with any MGC, it shall wait a random amount of time as described in clause 9.2 and then start contacting its primary, and if necessary, its secondary MGCs again. + +No recommendation is made on how the MGCs involved in the handoff maintain state information; this is considered to be out of scope of this Recommendation. The MGC and MG may take the following steps when handoff occurs. When the MGC initiates a handoff, the handover should be transparent to operations on the Media Gateway. Transactions can be executed in any order, and could be in progress when the ServiceChange is executed. Accordingly, commands in progress continue and replies to all commands from the original MGC must be sent to the transport address from which they were sent. If the service relationship with the sending MGC has ended, the replies should be discarded. The MG may receive outstanding transaction replies from the new MGC. No new messages shall be sent to the new MGC until the control association is established. Repeated transaction requests shall be directed to the new MGC. The MG shall maintain the state of all terminations and contexts. + +It is possible that the MGC could be implemented in such a way that a failed MGC is replaced by a working MGC where the identity of the new MGC is the same as the failed one. In such a case, the ServiceChangeMgcID would be specified with the previous value and the MG shall behave as if the value was changed, and send a ServiceChange message, as above. + +Pairs of MGCs that are capable of redundant failover can notify the controlled MGs of the failover by the above mechanism. + +## **11.6 MGC-MG control association monitoring** + +Monitoring the MGC-MG control association is essential for high availability networks. This may be realized by continuously checking the MGC-MG interconnection (link state). Many transports provide this functionality, so a mandatory protocol mechanism is unnecessary. + +For those transports that do not provide link state monitoring, this functionality can be achieved in the ITU-T H.248 protocol by utilizing the existing messaging. In the absence of any ITU-T H.248 messaging, the MGC may use an AuditValue Command on Root with an empty Audit Descriptor to detect the loss of communications with the MG. The MG can detect the communications loss itself through the use of the Inactivity Timer Package [ITU-T H.248.14]. + +## **11.7 Compatibility** + +### **11.7.1 Compatibility rules – forward and backward compatibility** + +ITU-T H.248 through its versioning and package extension capabilities allows forward compatibility. As per [b-ITU-T Q.1400] clause 12.3, forward compatibility mechanisms are defined as a scheme to enable a version of a protocol to communicate effectively with and interwork with future versions of the protocol. That is, a version of a protocol should not restrict future protocols from providing extra capabilities. + +When extending the ITU-T H.248 protocol backwards compatibility shall be maintained. As per [b-ITU-T Q.1400] clause 12.3 backward compatibility rules are defined as a scheme to ensure that nodes implementing future versions of the protocol will be able to send protocol messages of the previous version which will be understood and fully processed by the node supporting the previous version. That is, future versions of a protocol must allow earlier versions to operate with it and not reduce the earlier version's service level, i.e., a version 1 message with the version removed shall be able to be sent with a version 3 protocol with exactly the same meaning. + +The ITU-T H.248 specific backward compatibility rules that should be followed when extending the protocol (including packages and profiles) with new versions, are as follows: + +- 1) Existing protocol elements, i.e., procedures, parameters, descriptor, property, values, should not be changed unless a protocol error needs to be corrected or it becomes necessary to change the operation of the service that is being supported by the protocol. +- 2) The semantics of a command, a parameter, a descriptor, a property, or a value should not be changed. +- 3) Established rules for formatting and encoding messages and parameters should not be modified. +- 4) When information elements are found to be obsolete they can be marked as not used. However, the identifier for that information element will be marked as reserved. In that way it cannot be used in future versions. + +### **11.7.2 Compatibility mechanism** + +Protocol, package and profile versioning is integral part of the ITU-T H.248 architecture. The versioning of protocol elements together with the concept of the ITU-T H.248 control association permits effective compatibility mechanisms. + +#### **11.7.2.1 Aspect of ITU-T H.248 control association** + +Negotiated protocol capabilities are used for the lifetime of the ITU-T H.248 control association. An initial ServiceChange registration message is encoded as protocol version 1 (see clause 11.3); however, the final protocol version used is negotiated and may be subject of determination/negotiation of one or more profiles. + +#### **11.7.2.2 Capability change or service change on existing ITU-T H.248 control associations** + +A capability upgrade, leading to version negotiation procedures, may lead to a re-newing or re-establishment of the control association. This compatibility mechanism allows principally the replacement of version N protocol, package(s) and/or profile(s) by a lower or higher version N-K or N+M. + +# **12 Package definition** + +The primary mechanism for extension is by means of Packages. Packages define additional properties that may occur on terminations and contexts and events, signals and statistics that may occur on terminations. + +Packages and their versions are not generally related to the version of the protocol being used. If packages defined outside ITU-T H.248.1 have a dependence upon the syntax or features of a particular version of the protocol, they must explicitly state the minimum version of the protocol upon which they are dependent. + +Packages defined by IETF will appear in separate RFCs. + +Packages defined by ITU-T may appear in the relevant Recommendations (e.g., as in the ITU-T H.248 subseries of Recommendations). + +The package definition: + +- 1) should be a public document or a standard forum document, which can be referenced as the document that describes the package following the guideline above, should be specified. +- 2) The document shall specify the version of the Package that it describes. +- 3) The document should be available on a public web server and should have a stable URL. The site should provide a mechanism to provide comments and appropriate responses should be returned. + +## 12.1 Guidelines for defining packages + +Packages define properties, events, signals, and statistics. + +Packages may also define new error codes according to the guidelines given in clause 14.2. This is a matter of documentary convenience: the package documentation is submitted to IANA in support of the error code registration. If a package is modified, it is unnecessary to provide IANA with a new document reference in support of the error code unless the description of the error code itself is modified. + +Names of all such defined constructs shall consist of the PackageID (which uniquely identifies the package) and the ID of the item (which uniquely identifies the item in that package). In the text encoding the two shall be separated by a forward slash ("/") character. Example: tonegen/playtone is the text encoding to refer to the play tone signal in the tone generation package. + +A Package shall contain the following sections and keywords (indicated in bold). A template for defining packages is contained in Appendix II. + +### 12.1.1 Package + +Overall description of the package, specifying: + +**Package name:** only descriptive + +**Package ID:** is an identifier + +**Description:** is a description of the package + +**Version:** A new version of a package can only add additional properties, events, signals, statistics and new possible values for an existing parameter described in the original package. No deletions or modifications shall be allowed. A version is an integer in the range from 1 to 99. + +**Designed to be extended only** (Optional): Yes This indicates that the package has been expressly designed to be extended by others, not to be directly referenced. For example, the package may not have any function on its own or be nonsensical on its own. The MG shall not publish this PackageID when reporting packages. + +**Extends:** existing package Identifier and version. + +A package may extend an existing package. The version of the original package must be specified. When a package extends another package it shall only add additional properties, events, signals, statistics and new possible values for an existing parameter described in the original package. An extended package shall not redefine or overload an identifier defined in the original package and packages it may have extended (multiple levels of extension). Hence, if package B version 1 extends package A version 1, version 2 of B will not be able to extend the A version 2 if A version 2 defines a name already in B version 1. If the package does not extend another package, it shall specify "none". + +### 12.1.2 Properties + +Properties defined by the package, specifying: + +- Property name:** only descriptive +- Property ID:** is an identifier. +- Description:** is a description of the function of the property +- Type:** One of: +Boolean +String: UTF-8 string +Octet String: A number of octets. See Annex A and clause B.3 for encoding +Integer: 4-byte signed integer +Unsigned Integer: 4-octet unsigned integer +Double: 8-byte signed integer +Character: Unicode UTF-8 encoding of a single letter; could be more than one octet. +Enumeration: one of a list (NOTE) of possible unique values. Packages MUST define the text and binary encodings for each value in the enumeration. +Sub-list: a list of several values from a list (NOTE). The type of sub-list shall also be specified. The type shall be chosen from the types specified in this section (with the exception of sub-list). For example, Type: sub-list of enumeration. The encoding of sub-lists is specified in clauses A.2 and B.2. +NOTE – A Sub-list may contain a single list item. See clauses A.2 and B.2 for the encoding options. +- Possible values:** A package must specify either a specific set of values or a description of how values are determined. A package must also specify a default value or the default behaviour when the value is omitted from its descriptor. For example, a package may specify that procedures related to the property are suspended when its value is omitted. +- Default:** A default value (but not procedures) may be specified as provisionable. +- Defined in:** The ITU-T H.248.1 descriptor in which the property is defined. LocalControl is for stream-dependent properties. TerminationState is for stream-independent properties. ContextAttribute is for properties that affect the context as a whole, i.e., mixing properties. These are expected to be the most common cases, but it is possible for properties to be defined in other descriptors. Context properties must be defined in the ContextAttribute Descriptor. + +**Characteristics:** Read-Only or Read/Write, and (optionally), global: + Indicates whether a property is read-only, or read/write, and if it is global. If global is omitted, the property is not global. If a property is declared as global, the value of the property is shared by all terminations realizing the package. If a context property is declared as global, the property is shared by all contexts realizing the package. + +### 12.1.3 Events + +Events defined by the package, specifying: + +**Event name:** only descriptive +**Event ID:** is an identifier +**Description:** a description of the function of the event +**EventsDescriptor parameters:** Parameters used by the MGC to configure the event, and found in the Events Descriptor. See clause 12.2. If there are no parameters for the Events Descriptor, then "none" shall be specified. +**ObservedEvents Descriptor parameters:** Parameters returned to the MGC in Notify requests and in replies to command requests from the MGC that audit ObservedEvents Descriptor, and found in the ObservedEvents Descriptor. See clause 12.2. If there are no parameters for the ObservedEvents Descriptor, then "none" shall be specified. + +### 12.1.4 Signals + +Signals defined by the package, specifying: + +**Signal name:** only descriptive +**Signal ID:** is an identifier. SignalID is used in a Signals Descriptor +**Description:** a description of the function of the signal +**SignalType:** one of: + OO (OnOff) + TO (TimeOut) + BR (Brief) + NOTE – SignalType may be defined such that it is dependent on the value of one or more parameters. The package must specify a default signal type. If the default type is TO, the package must specify a default duration which may be provisioned. A default duration is meaningless for BR. +**Duration:** in hundredths of seconds +**Additional parameters:** see clause 12.2 + +### 12.1.5 Statistics + +Statistics defined by the package, specifying: + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic name: | only descriptive | +| Statistic ID: | is an identifier
StatisticID is used in a Statistics Descriptor | +| Description: | a description of the statistic | +| Type: | One of:
Boolean
String: UTF-8 string
Octet String: A number of octets. See Annex A and clause B.3 for encoding
Integer: 4-byte signed integer
Unsigned Integer: 4-octet unsigned integer
Double: 8-byte signed integer
Character: Unicode UTF-8 encoding of a single letter. Could be more than one octet.
Enumeration: One of a list (NOTE) of possible unique values. Packages MUST define the text and binary encodings for each value in the enumeration.
Sub-list: A list of several values from a list (NOTE). The type of sub-list shall also be specified. The type shall be chosen from the types specified in this section (with the exception of sub-list). For example, Type: sub-list of enumeration. The encoding of sub-lists is specified in Annex A and in clause B.2.
NOTE – A Sub-list may contain a single list item. See clauses A.2 and B.2 for the encoding options. | +| Possible values: | A package must indicate the unit of measure, e.g., milliseconds, packets, either here or along with the type above, as well as indicating any restriction on the range. | +| Level: | Specify if the statistic can be kept at the termination level, Stream level or either. | + +#### 12.1.5.1 Aspects of statistics transformation + +ITU-T H.248 statistics are generated by Media Gateways. Such statistics are either based on MG local measurements, that is, the MG is the measurement point, or the statistics are based on remote measurements from the MG perspective. The reported statistics by the MG could be transformed in some specific cases, e.g., by the served user of the statistics (see Figure 16). + +![Diagram illustrating the potential location of statistics transformation in an ITU-T H.248 architecture. The diagram shows three main components: a Remote network element (dashed box), a Media Gateway Controller (MGC), and an ITU-T H.248 Media Gateway (MG). The MGC contains a 'Statistics processing' block. The MG contains 'Generation of ITU-T H.248 statistic(s)' and 'Measurement Points (MP)'. A pink arrow labeled 'ITU-T H.248' points from the MG to the MGC. A dashed arrow points from the MGC to the Remote network element. A blue callout box labeled 'Potential transformation of statistics' with the reference 'H.248.1 v3(13)_F16' has arrows pointing to both the 'Statistics processing' block in the MGC and the dashed arrow between the MGC and the Remote network element.](caeb1637753f79f4cd005eda3768d1d5_img.jpg) + +Diagram illustrating the potential location of statistics transformation in an ITU-T H.248 architecture. The diagram shows three main components: a Remote network element (dashed box), a Media Gateway Controller (MGC), and an ITU-T H.248 Media Gateway (MG). The MGC contains a 'Statistics processing' block. The MG contains 'Generation of ITU-T H.248 statistic(s)' and 'Measurement Points (MP)'. A pink arrow labeled 'ITU-T H.248' points from the MG to the MGC. A dashed arrow points from the MGC to the Remote network element. A blue callout box labeled 'Potential transformation of statistics' with the reference 'H.248.1 v3(13)\_F16' has arrows pointing to both the 'Statistics processing' block in the MGC and the dashed arrow between the MGC and the Remote network element. + +**Figure 16 – Potential location of statistics transformation** + +Transformation of statistics is applicable to certain categories of statistics (e.g., statistics related to traffic-volume and traffic-rate metrics), and then only in very specific scenarios. Typically, transformation rules are only applied when a set of conditions is fulfilled. These conditions are generally proscribed by the bearer technology, protocol stack and other service aspects related to the ITU-T H.248 stream or termination. + +By defining statistics explicitly related to the layer or condition that is desired to be collected, post-collection transformation of statistics can be avoided. + +### 12.1.6 Error codes + +If the package does not define any error codes, this section may be omitted. Otherwise, it describes error codes defined by the package, specifying: + +- Error Code #:** The error code number. +- Name:** Name of the error +- Definition:** A description of the error code. +- Error text in the Error Descriptor:** A description of what text to return in the Error Descriptor. +- Comment:** Any further comments on the use of the error code. + +### 12.1.7 Procedures + +Additional guidance on the use of the package. + +## 12.2 Guidelines to defining parameters to events and signals + +- Parameter name:** only descriptive +- Parameter ID:** is an identifier. The textual ParameterID of parameters to events and signals shall not start with "EPA" and "SPA", respectively. The textual ParameterID shall also not be "ST", "Stream", "SY", "SignalType", "DR", "Duration", "NC", "NotifyCompletion", "KA", "KeepActive", "EB", "Embed", "DM", "DigitMap", "SPADI", "SPADirection", "SPARQ" or "SPARrequestID". +- Description:** a description of the function of the parameter. +- Type:** One of: +Boolean +String: UTF-8 octet string +Octet String: A number of octets. See Annex A and clause B.3 for encoding +Integer: 4-octet signed integer +Unsigned Integer: 4-octet unsigned integer +Double: 8-octet signed integer +Character: Unicode UTF-8 encoding of a single letter. Could be more than one octet. +Enumeration: one of a list of possible unique values. Packages MUST define the text and binary encodings for each value in the enumeration. +Sub-list: a list of several values from a list (not supported for statistics). The type of sub-list shall also be specified. The type shall be chosen from the types specified in this section (with the exception of sub-list). For example, Type: sub-list of enumeration. The encoding of sub-lists is specified in Annex A and clause B.2. +- Optional:** Yes/No +Describes if the parameter may be omitted from the signal or event. +- Possible values:** A package must specify either a specific set of values or a description of how values are determined. A package must also specify a default value or the default behaviour when the value is omitted from its descriptor. For example, a package may specify that procedures related to the parameter are suspended when its value is omitted. +- Default:** A default value (but not procedures) may be specified as provisionable. + +## 12.3 Identifiers + +Identifiers in text encoding shall be strings of up to 64 characters, containing no spaces, starting with an alphabetic character and consisting of alphanumeric characters and/or digits, and possibly including the special character underscore ("\_"). + +Identifiers in binary encoding are 2 octets long. + +Both text and binary values shall be specified for each identifier, including identifiers used as values in enumerated types. + +## 12.4 Package registration + +A package can be registered with IANA for interoperability reasons. See clause 14 for IANA considerations. + +# 13 Profile definition + +Profiles may be specified to further define how the ITU-T H.248.1 protocol is used and what functionality is supported by an MG. It only describes the capabilities of the MGC/MG ITU-T H.248 interface. The profile itself specifies what options associated with ITU-T H.248.1 have been used. For example: transport and packages used for an application. + +Any profile definition shall not extend the ITU-T H.248.1 protocol by, e.g., adding new syntactical elements, revision of semantics, or additional procedures (like, e.g., cross-package level procedures) in a profile. Possible profile procedures are thus given only by possible core protocol level (1) and package level (2) procedures. + +A profile is identified by a name (IANA registered) and a version. A name shall be a case-insensitive string up to 64 characters long. Version shall be 1 to 99. + +The profile itself is a document that indicates the options for a particular application. There is no set format for this document. The only mandatory element is that there should be a section indicating the Profile Name and Version and a summary of the profile. + +The two points below are the only mandatory sections of a profile: + +- Profile Identification: The name and version of the profile that is sent in the ServiceChange Command. +- Summary: A description of what the profile is. + +Appendix III contains a template for the definition of profiles. It should be used as the basis of a profile definition. + +# 14 IANA ITU-T H.248 registrations + +Registrations for ITU-T H.248 Packages, Error Codes, ServiceChangeReasons and Profile are requested from the IANA. [IETF RFC 5615] documents the procedures from an Expert reviewer and an IANA considerations perspective. This clause and its subclauses provide an outline to requesters of the information required and the procedures for public and private registrations. + +## 14.1 Package registration procedure + +Package requesters are encouraged to review their work against clause 12, "Package definition", and are encouraged to use the package definition template provided in Appendix II. + +The process for registering a public Package is deemed to be "specification required" as per [IETF RFC 5226]. As such, once the initial checks occur, Package requesters for public packages under development shall send the package text to IANA. They are also encouraged to send the package to the ITU-T Question/Study Group responsible for the ITU-T H.248 sub-series of Recommendations (Question 3 of ITU-T Study Group 16 at the time of writing) for review. Updated contact information can be found in the latest version of the ITU-T H.248 Sub-series Implementors' Guide. This should occur as soon as practicable after the rough draft of the definition is completed and at least before the package is approved, in order to ensure the package is consistent with ITU-T H.248 methodologies and package design principles. + +In order to register private Packages, a specification is not required but is encouraged. + +Package requesters are encouraged to request registration as early as practicable in the design process, to reserve a binary ID. Binary IDs shall be published in the document defining the package. + +Once the initial or final request for a Package registration is received by IANA, it will be forwarded to the Internet Engineering Steering Group (IESG) appointed Expert for review. During the review the input package and details will be compared to the Package template for completeness, as well as being compared against protocol syntax and procedures. It will be compared against existing work to see that it does not duplicate existing functionalities. It will be reviewed to see that any potential security issues are addressed. The Expert reviewer will then work towards a resolution of any issues with the Package requester. The IESG appointed Expert may complete the review in consultation with other ITU-T H.248 experts (i.e., Currently Question 3 of ITU-T Study Group 16 and via email to IETF Megaco email list). If the package is deemed suitable, the IESG appointed Expert shall issue a statement indicating approval, copied to IANA. + +The IESG Expert reviewer will ensure the following considerations are met to register a package with IANA: + +- 1) A unique string name, unique serial number and version number is registered for each package. The string name is used as the PackageID for text encoding. The serial number is used as the PackageID for binary encoding. Public packages MUST be given serial numbers in the range 0x0001 to 0x7fff. Private packages MUST be given serial numbers in the range 0x8000 to 0xffff. Serial number 0 is reserved. The unique string name and unique serial number MAY either be requested by the package requester or, if not requested, assigned by IANA. +- 2) The package requester shall provide a contact name, and an email and postal addresses for that contact. The contact information shall be updated by the defining organization, as necessary. +- 3) The public package requester shall provide a reference to a document that describes the package, which should be public: + - a) The document shall specify the version of the package that it describes. + - b) If the document is public, it should be located on a public web server and should have a stable URL. The site should provide a mechanism to provide comments, and appropriate responses should be returned. + - c) If the document is not public, it must be made available for review by the IESG appointed Expert (without requiring a non disclosure agreement (NDA)) at the time of the application. + +NOTE – The document does not have to be publicly available at the time of the registration request, however the document shall be provided and available for review by the IESG appointed Expert. Once approved by a standards body, the package should be publicly available, however the package may remain not public. + +For private packages a contact email address for the package registration shall be provided. + +- 4) Packages registered by other than recognized standards bodies shall have a minimum package name length of 8 characters. +- 5) Package names are allocated on a first come-first served basis if all other conditions are met. + +Status – "In Progress (IP)" indicates that the package has not been fully reviewed and approved; therefore, it may contain errors or may not be consistent with ITU-T H.248 principles. "Final" indicates that the Package has been reviewed and approved and is stable. New packages shall be registered with a status of "IP". Once the Package has been finalized (i.e., approved according to the procedures of the Package Requester's Organization) they should contact IANA in order to update the status to "Final". + +Once the IESG appointed Expert has determined that the registration is appropriate they will advise IANA to register the Package. + +IANA will assign a serial number to each package meeting the conditions of registration (except for an update of an existing package, which retains the serial number of the package it is updating), in consecutive order of registration. + +## **14.2 Error code registration procedure** + +Error code requesters shall send a request to IANA to register the error code. Documentation addressing the considerations below shall be provided (i.e., Specification required as per [IETF RFC 5226]). IANA shall then forward the request to the IESG appointed Expert for review. + +The following considerations shall be met to register an error code with IANA: + +- 1) An error number and a one-line (80-character maximum) string are registered for each error. +- 2) A complete description of the conditions under which the error is detected shall be included in a publicly available document. The description shall be sufficiently clear to differentiate the error from all other existing error codes. +- 3) The document should be available on a public web server and should have a stable URL. +- 4) Error numbers registered by recognized standards bodies shall have 3- or 4-character error numbers. +- 5) Error numbers registered by all other organizations or individuals shall have 4-character error numbers. +- 6) Only the organization or individual that originally defined it (or their successors or assigns) can modify an error number definition. + +If the modification leads to a change in the error code number, error code name or error string, the error code modifier shall send a request to IANA to register the update. This request shall be treated as a new error code request which will involve an Expert review. + +Once the IESG appointed Expert has determined that the registration is appropriate they will advise IANA to register the error code. + +## **14.3 ServiceChange reason registration procedures** + +ServiceChange reason requesters shall send a request to IANA to register the ServiceChange reason. Documentation addressing the considerations below shall be provided (i.e., Specification required as per [IETF RFC 5226]). IANA shall then forward the request to the IESG appointed Expert for review. + +The following considerations shall be met to register ServiceChange reason with IANA: + +- 1) A one-phrase, 80-character maximum, unique reason code is registered for each reason. +- 2) A complete description of the conditions under which the reason is used shall be included in a publicly available document. The description shall be sufficiently clear to differentiate the reason from all other existing reasons. +- 3) The document should be available on a public web server and should have a stable URL. + +Once the IESG appointed Expert has determined that the registration is appropriate they will advise IANA to register the ServiceChange reason. + +## **14.4 Profile registration procedures** + +Profile name requesters shall send a request to IANA to register the profile name. Documentation addressing the considerations below shall be provided. IANA shall then forward the request to the IESG appointed Expert for review. + +The following considerations shall be met to register a profile with IANA: + +- 1) A unique string name and version number (version may be omitted when the profile name contains a wildcard) is registered for each profile. +- 2) A contact name, email and postal addresses for that contact shall be specified. The contact information shall be updated by the defining organization as necessary. +- 3) Profiles registered by other than recognized standards bodies shall have a minimum profile name length of 6 characters. +- 4) Profile names containing a wildcard "\*" on the end of their names shall be accepted if the first 6 characters are fully specified. It is assumed that the organization that was issued with the profile name will manage the namespace associated with the wildcard. IANA shall not issue other profiles names within "name\*" range. + +All other profile names are first come-first served if all other conditions are met. + +Once the IESG appointed Expert has determined that the registration is appropriate they will advise IANA to register the profile. + +# Annex A + +## Binary encoding of the protocol + +(This annex forms an integral part of this Recommendation.) + +This annex specifies the syntax of messages using the notation defined in [ITU-T X.680], *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation*. Messages shall be encoded for transmission by applying the basic encoding rules specified in [ITU-T X.690], *Information Technology – ASN.1 Encoding Rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)*. + +## A.1 Coding of wildcards + +The use of wildcards ALL and CHOOSE is allowed in the protocol. This allows an MGC to partially specify TerminationIDs and to let the MG choose from the values that conform to the partial specification. TerminationIDs may encode a hierarchy of names. This hierarchy is provisioned. For instance, a TerminationID may consist of a trunk group, a trunk within the group and a circuit. Wildcarding must be possible at all levels. The following paragraphs explain how this is achieved. + +The ASN.1 description uses octet strings of up to 8 octets in length for TerminationIDs. This means that TerminationIDs consist of at most 64 bits. A fully specified TerminationID may be preceded by a sequence of wildcarding fields. A wildcarding field is one octet in length. Bit 7 (the most significant bit) of this octet specifies what type of wildcarding is invoked: if the bit value equals 1, then the ALL wildcard is used; if the bit value is 0, then the CHOOSE wildcard is used. Bit 6 of the wildcarding field specifies whether the wildcarding pertains to one level in the hierarchical naming scheme (bit value 0) or to the level of the hierarchy specified in the wildcarding field plus all lower levels (bit value 1). Bits 0 through 5 of the wildcarding field specify the bit position in the TerminationID at which the wildcarding starts. + +We illustrate this scheme with some examples. In these examples, the most significant bit in a string of bits appears on the left-hand side. + +Assume that TerminationIDs are three octets long and that each octet represents a level in a hierarchical naming scheme. A valid TerminationID is: + +00000001 00011110 01010101. + +Addressing ALL names with prefix 00000001 00011110 is done as follows: + +wildcarding field: 10000111 + +TerminationID: 00000001 00011110 xxxxxxxx. + +The values of the bits labelled "x" is irrelevant and shall be ignored by the receiver. + +Indicating to the receiver that it must choose a name with 00011110 as the second octet is done as follows: + +wildcarding fields: 00010111 followed by 00000111 + +TerminationID: xxxxxxxx 00011110 xxxxxxxx. + +The first wildcard field indicates a CHOOSE wildcard for the level in the naming hierarchy starting at bit 23, the highest level in our assumed naming scheme. The second wildcard field indicates a CHOOSE wildcard for the level in the naming hierarchy starting at bit 7, the lowest level in our assumed naming scheme. + +Finally, a CHOOSE-wildcarded name with the highest level of the name equal to 00000001 is specified as follows: + +wildcard field: 01001111 + +TerminationID: 0000001 xxxxxxxx xxxxxxxx. + +Bit value 1 at bit position 6 of the first octet of the wildcard field indicates that the wildcarding pertains to the specified level in the naming hierarchy and all lower levels. + +ContextIDs may also be wildcarded. In the case of ContextIDs, however, specifying partial names is not allowed. ContextID 0x0 shall be used to indicate the NULL Context, ContextID 0xFFFFFE shall be used to indicate a CHOOSE wildcard, and ContextID 0xFFFFFFFF shall be used to indicate an ALL wildcard. + +TerminationID 0xFFFFFFFFFFFFFFFF shall be used to indicate the Root Termination. + +## A.2 ASN.1 syntax specification + +This clause contains the ASN.1 specification of the ITU-T H.248.1 protocol syntax. + +NOTE 1 – In case a transport mechanism is used that employs application level framing, the definition of **Transaction** below changes. Refer to the annex or to the Recommendation of the ITU-T H.248.x subseries defining the transport mechanism for the definition that applies in that case. + +NOTE 2 – This syntax specification does not enforce all restrictions on element inclusions and values. Some additional restrictions are stated in comments and other restrictions appear in the text of this Recommendation. These additional restrictions are part of the protocol even though not enforced by this Recommendation. + +NOTE 3 – The ASN.1 module in this annex uses octet string types to encode values for property parameter, signal parameter and event parameter values and statistics. The actual types of these values vary and are specified in Annex C or the relevant package definition. + +A value is first BER-encoded based on its type using the table below. The result of this BER-encoding is then encoded as an ASN.1 octet string, "double wrapping" the value. The format specified in Annex C or the package relates to BER encoding according to the following table: + +| Type Specified in Package | ASN.1 BER Type | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------| +| String | IA5String or UTF8String (Note 4) | +| Integer (4-octet) | INTEGER | +| Double (8-octet signed int) | INTEGER (Note 3) | +| Character (UTF-8) (Note 1) | IA5String | +| Enumeration | ENUMERATED | +| Boolean | BOOLEAN | +| Unsigned Integer (Note 2) | INTEGER (Note 3) | +| Octet (String) | OCTET STRING | +| NOTE 1 – Can be more than one byte. | | +| NOTE 2 – Unsigned integer is referenced in Annex C. | | +| NOTE 3 – The BER encoding of INTEGER does not imply the use of 4 bytes. | | +| NOTE 4 – String should be encoded as IA5String when the contents are all ASCII characters, but as UTF8String if it contains any non-ASCII characters. | | + +See clause 8.7 of [ITU-T X.690], for the definition of the encoding of an octet string value. + +``` +MEDIA-GATEWAY-CONTROL {itu-t(0) recommendation(0) h(8) h248(248) modules(0) +media-gateway-control(0) version3(3)} +DEFINITIONS AUTOMATIC TAGS ::= +``` + +``` + +BEGIN +MegacoMessage ::= SEQUENCE +{ + authHeader AuthenticationHeader OPTIONAL, + mess Message +} + +AuthenticationHeader ::= SEQUENCE +{ + secParmIndex SecurityParmIndex, + seqNum SequenceNum, + ad AuthData +} + +SecurityParmIndex ::= OCTET STRING(SIZE(4)) +SequenceNum ::= OCTET STRING(SIZE(4)) +AuthData ::= OCTET STRING (SIZE (12..32)) +Message ::= SEQUENCE +{ + version INTEGER(0..99), + -- The version of the protocol defined here is equal to 3. + mId Mid, -- Name/address of message originator + messageBody CHOICE + { + messageError ErrorDescriptor, + transactions SEQUENCE OF Transaction + }, + ... +} + +Mid ::= CHOICE +{ + ip4Address IP4Address, + ip6Address IP6Address, + domainName DomainName, + deviceName PathName, + mtpAddress OCTET STRING(SIZE(2..4)), + -- Addressing structure of mtpAddress: + -- 25 - 15 0 + -- | PC | NI | + -- 24 - 14 bits 2 bits + -- NOTE - 14 bits are defined for international use. + -- Two national options exist where the point code is 16 or 24 bits. + -- To octet align the mtpAddress, the MSBs shall be encoded as 0s. + ... +} + +DomainName ::= SEQUENCE +{ + name IA5String, + -- The name starts with an alphanumeric digit followed by a sequence + -- of alphanumeric digits, hyphens and dots. No two dots shall occur + -- consecutively. + portNumber INTEGER(0..65535) OPTIONAL +} + +IP4Address ::= SEQUENCE +{ + address OCTET STRING (SIZE(4)), + portNumber INTEGER(0..65535) OPTIONAL +} + +IP6Address ::= SEQUENCE +{ + +``` + +``` + + address OCTET STRING (SIZE(16)), + portNumber INTEGER(0..65535) OPTIONAL + } + + PathName ::= IA5String(SIZE (1..64)) + -- See A.3 + + Transaction ::= CHOICE + { + transactionRequest TransactionRequest, + transactionPending TransactionPending, + transactionReply TransactionReply, + transactionResponseAck TransactionResponseAck, + -- use of response acks is dependent on underlying transport + ..., + segmentReply SegmentReply + } + + TransactionId ::= INTEGER(0..4294967295) -- 32-bit unsigned integer + + TransactionRequest ::= SEQUENCE + { + transactionId TransactionId, + actions SEQUENCE OF ActionRequest, + ... + } + + TransactionPending ::= SEQUENCE + { + transactionId TransactionId, + ... + } + + TransactionReply ::= SEQUENCE + { + transactionId TransactionId, + immAckRequired NULL OPTIONAL, + transactionResult CHOICE + { + transactionError ErrorDescriptor, + actionReplies SEQUENCE OF ActionReply + }, + ..., + segmentNumber SegmentNumber OPTIONAL, + segmentationComplete NULL OPTIONAL + } + + SegmentReply ::= SEQUENCE + { + transactionId TransactionId, + segmentNumber SegmentNumber, + segmentationComplete NULL OPTIONAL, + ... + } + + SegmentNumber ::= INTEGER(0..65535) + + TransactionResponseAck ::= SEQUENCE OF TransactionAck + TransactionAck ::= SEQUENCE + { + firstAck TransactionId, + lastAck TransactionId OPTIONAL + } + +``` + +``` + +ErrorDescriptor ::= SEQUENCE +{ + errorCode ErrorCode, + errorText ErrorText OPTIONAL +} + +ErrorCode ::= INTEGER(0..65535) +-- See clause 14 for IANA considerations with respect to error codes + +ErrorText ::= IA5String + +ContextID ::= INTEGER(0..4294967295) +-- Context NULL Value: 0 +-- Context CHOOSE Value: 4294967294 (0xFFFFFFFF) +-- Context ALL Value: 4294967295 (0xFFFFFFFF) + +ActionRequest ::= SEQUENCE +{ + contextId ContextID, + contextRequest ContextRequest OPTIONAL, + contextAttrAuditReq ContextAttrAuditRequest OPTIONAL, + commandRequests SEQUENCE OF CommandRequest +} + +ActionReply ::= SEQUENCE +{ + contextId ContextID, + errorDescriptor ErrorDescriptor OPTIONAL, + contextReply ContextRequest OPTIONAL, + commandReply SEQUENCE OF CommandReply +} + +ContextRequest ::= SEQUENCE +{ + priority INTEGER(0..15) OPTIONAL, + emergency BOOLEAN OPTIONAL, + topologyReq SEQUENCE OF TopologyRequest OPTIONAL, + ..., + iepscallind BOOLEAN OPTIONAL, + contextProp SEQUENCE OF PropertyParm OPTIONAL, + contextList SEQUENCE OF ContextID OPTIONAL +} +-- When returning a contextList, the contextId in the ActionReply construct will +-- return the contextId from the associated ActionRequest. + +ContextAttrAuditRequest ::= SEQUENCE +{ + topology NULL OPTIONAL, + emergency NULL OPTIONAL, + priority NULL OPTIONAL, + ..., + iepscallind NULL OPTIONAL, + contextPropAud SEQUENCE OF IndAudPropertyParm OPTIONAL, + selectpriority INTEGER(0..15) OPTIONAL, + -- to select given priority + selectemergency BOOLEAN OPTIONAL, + -- to select if emergency set/not set (T/F) + selectiepscallind BOOLEAN OPTIONAL, + -- to select if IEPS set/not set (T/F) + selectLogic SelectLogic OPTIONAL -- default is AND +} + +SelectLogic ::= CHOICE +{ + +``` + +``` + + andAUDITSelect NULL, -- all filter conditions satisfied + orAUDITSelect NULL, -- at least one filter condition satisfied + ... + } + + CommandRequest ::= SEQUENCE + { + command Command, + optional NULL OPTIONAL, + wildcardReturn NULL OPTIONAL, + ... + } + + Command ::= CHOICE + { + addReq AmmRequest, + moveReq AmmRequest, + modReq AmmRequest, + -- Add, Move, Modify requests have the same parameters + subtractReq SubtractRequest, + auditCapRequest AuditRequest, + auditValueRequest AuditRequest, + notifyReq NotifyRequest, + serviceChangeReq ServiceChangeRequest, + ... + } + + CommandReply ::= CHOICE + { + addReply AmmsReply, + moveReply AmmsReply, + modReply AmmsReply, + subtractReply AmmsReply, + -- Add, Move, Modify, Subtract replies have the same parameters + auditCapReply AuditReply, + auditValueReply AuditReply, + notifyReply NotifyReply, + serviceChangeReply ServiceChangeReply, + ... + } + + TopologyRequest ::= SEQUENCE + { + terminationFrom TerminationID, + terminationTo TerminationID, + topologyDirection ENUMERATED + { + bothway(0), + isolate(1), + oneway(2) + }, + ..., + streamID StreamID OPTIONAL, + topologyDirectionExtension ENUMERATED { + onewayexternal(0), + onewayboth(1), + ... + } OPTIONAL + } + + -- if present, topologyDirectionExtension takes precedence over + -- topologyDirection + + AmmRequest ::= SEQUENCE + { + terminationID TerminationIDList, + } + +``` + +``` + + descriptors SEQUENCE OF AmmDescriptor, + -- At most one descriptor of each type (see AmmDescriptor) + -- allowed in the sequence. + ... +} + +AmmDescriptor ::= CHOICE +{ + mediaDescriptor MediaDescriptor, + modemDescriptor ModemDescriptor, + muxDescriptor MuxDescriptor, + eventsDescriptor EventsDescriptor, + eventBufferDescriptor EventBufferDescriptor, + signalsDescriptor SignalsDescriptor, + digitMapDescriptor DigitMapDescriptor, + auditDescriptor AuditDescriptor, + ..., + statisticsDescriptor StatisticsDescriptor +} + +AmmsReply ::= SEQUENCE +{ + terminationID TerminationIDList, + terminationAudit TerminationAudit OPTIONAL, + ... +} + +SubtractRequest ::= SEQUENCE +{ + terminationID TerminationIDList, + auditDescriptor AuditDescriptor OPTIONAL, + ... +} + +AuditRequest ::= SEQUENCE +{ + terminationID TerminationID, + auditDescriptor AuditDescriptor, + ..., + terminationIDList TerminationIDList OPTIONAL +} +-- terminationID shall contain the first termination in the +-- list when using the terminationIDList construct in AuditRequest + +AuditReply ::= CHOICE +{ + contextAuditResult TerminationIDList, + error ErrorDescriptor, + auditResult AuditResult, + ..., + auditResultTermList TermListAuditResult +} + +AuditResult ::= SEQUENCE +{ + terminationID TerminationID, + terminationAuditResult TerminationAudit +} + +TermListAuditResult ::= SEQUENCE +{ + terminationIDList TerminationIDList, + terminationAuditResult TerminationAudit, + ... +} + +``` + +``` + +TerminationAudit ::= SEQUENCE OF AuditReturnParameter + +AuditReturnParameter ::= CHOICE +{ + errorDescriptor ErrorDescriptor, + mediaDescriptor MediaDescriptor, + modemDescriptor ModemDescriptor, + muxDescriptor MuxDescriptor, + eventsDescriptor EventsDescriptor, + eventBufferDescriptor EventBufferDescriptor, + signalsDescriptor SignalsDescriptor, + digitMapDescriptor DigitMapDescriptor, + observedEventsDescriptor ObservedEventsDescriptor, + statisticsDescriptor StatisticsDescriptor, + packagesDescriptor PackagesDescriptor, + emptyDescriptors AuditDescriptor, + ... +} + +AuditDescriptor ::= SEQUENCE +{ + auditToken BIT STRING + { + muxToken(0), + modemToken(1), + mediaToken(2), + eventsToken(3), + signalsToken(4), + digitMapToken(5), + statsToken(6), + observedEventsToken(7), + packagesToken(8), + eventBufferToken(9) + } OPTIONAL, + ..., + auditPropertyToken SEQUENCE OF IndAuditParameter OPTIONAL +} + +IndAuditParameter ::= CHOICE +{ + inaudmediaDescriptor IndAudMediaDescriptor, + inaudeventsDescriptor IndAudEventsDescriptor, + inaudeventBufferDescriptor IndAudEventBufferDescriptor, + inaudsignalsDescriptor IndAudSignalsDescriptor, + inauddigitMapDescriptor IndAudDigitMapDescriptor, + inaudstatisticsDescriptor IndAudStatisticsDescriptor, + inaudpackagesDescriptor IndAudPackagesDescriptor, + ... +} + +IndAudMediaDescriptor ::= SEQUENCE +{ + termStateDescr IndAudTerminationStateDescriptor OPTIONAL, + streams CHOICE + { + oneStream IndAudStreamParms, + multiStream SEQUENCE OF IndAudStreamDescriptor + } OPTIONAL, + ... +} + +IndAudStreamDescriptor ::= SEQUENCE +{ + +``` + +``` + + streamID StreamID, + streamParms IndAudStreamParms +} + +IndAudStreamParms ::= SEQUENCE +{ + localControlDescriptor IndAudLocalControlDescriptor OPTIONAL, + localDescriptor IndAudLocalRemoteDescriptor OPTIONAL, + remoteDescriptor IndAudLocalRemoteDescriptor OPTIONAL, + ..., + statisticsDescriptor IndAudStatisticsDescriptor OPTIONAL +} + +IndAudLocalControlDescriptor ::= SEQUENCE +{ + streamMode NULL OPTIONAL, + reserveValue NULL OPTIONAL, + reserveGroup NULL OPTIONAL, + propertyParms SEQUENCE OF IndAudPropertyParm OPTIONAL, + ..., + streamModeSel StreamMode OPTIONAL +} +-- must not have both streamMode and streamModeSel +-- if both are present only streamModeSel shall be honoured + +IndAudPropertyParm ::= SEQUENCE +{ + name PkgdName, + ..., + propertyParms PropertyParm OPTIONAL +} + +-- to select based on property values +-- AND/OR selection logic is specified at context level + +IndAudLocalRemoteDescriptor ::= SEQUENCE +{ + propGroupID INTEGER(0..65535) OPTIONAL, + propGrps IndAudPropertyGroup, + ... +} + +IndAudPropertyGroup ::= SEQUENCE OF IndAudPropertyParm + +IndAudTerminationStateDescriptor ::= SEQUENCE +{ + propertyParms SEQUENCE OF IndAudPropertyParm, + eventBufferControl NULL OPTIONAL, + serviceState NULL OPTIONAL, + ..., + serviceStateSel ServiceState OPTIONAL +} +-- must not have both serviceState and serviceStateSel +-- if both are present only serviceStateSel shall be honoured + +IndAudEventsDescriptor ::= SEQUENCE +{ + requestID RequestID OPTIONAL, + pkgdName PkgdName, + streamID StreamID OPTIONAL, + ... +} + +IndAudEventBufferDescriptor ::= SEQUENCE + +``` + +``` + +{ + eventName PkgdName, + streamID StreamID OPTIONAL, + ... +} + +IndAudSignalsDescriptor ::=CHOICE +{ + signal IndAudSignal, + seqSigList IndAudSeqSigList, + ... +} + +IndAudSeqSigList ::= SEQUENCE +{ + id INTEGER(0..65535), + signalList IndAudSignal OPTIONAL +} + +IndAudSignal ::= SEQUENCE +{ + signalName PkgdName, + streamID StreamID OPTIONAL, + ..., + signalRequestID RequestID OPTIONAL +} + +IndAudDigitMapDescriptor ::= SEQUENCE +{ + digitMapName DigitMapName OPTIONAL +} + +IndAudStatisticsDescriptor ::= SEQUENCE +{ + statName PkgdName +} + +IndAudPackagesDescriptor ::= SEQUENCE +{ + packageName Name, + packageVersion INTEGER(0..99), + ... +} + +NotifyRequest ::= SEQUENCE +{ + terminationID TerminationIDList, + observedEventsDescriptor ObservedEventsDescriptor, + errorDescriptor ErrorDescriptor OPTIONAL, + ... +} + +NotifyReply ::= SEQUENCE +{ + terminationID TerminationIDList, + errorDescriptor ErrorDescriptor OPTIONAL, + ... +} + +ObservedEventsDescriptor ::= SEQUENCE +{ + requestId RequestID, + observedEventLst SEQUENCE OF ObservedEvent +} + +ObservedEvent ::= SEQUENCE + +``` + +``` + +{ + eventName EventName, + streamID StreamID OPTIONAL, + eventParmList SEQUENCE OF EventParameter, + timeNotation TimeNotation OPTIONAL, + ... +} + +EventName ::= PkgdName + +EventParameter ::= SEQUENCE +{ + eventParameterName Name, + value Value, + -- For use of extraInfos see the comment related to PropertyParm + extraInfo CHOICE + { + relation Relation, + range BOOLEAN, + sublist BOOLEAN + } OPTIONAL, + ... +} + +ServiceChangeRequest ::= SEQUENCE +{ + terminationID TerminationIDList, + serviceChangeParms ServiceChangeParm, + ... +} + +ServiceChangeReply ::= SEQUENCE +{ + terminationID TerminationIDList, + serviceChangeResult ServiceChangeResult, + ... +} + +-- For ServiceChangeResult, no parameters are mandatory. Hence the +-- distinction between ServiceChangeParm and ServiceChangeResParm. +ServiceChangeResult ::= CHOICE +{ + errorDescriptor ErrorDescriptor, + serviceChangeResParms ServiceChangeResParm +} + +WildcardField ::= OCTET STRING(SIZE(1)) + +TerminationID ::= SEQUENCE +{ + wildcard SEQUENCE OF WildcardField, + id OCTET STRING(SIZE(1..8)), + ... +} + +-- See A.1 for explanation of wildcarding mechanism. +-- TerminationID 0xFFFFFFFFFFFFFFFF indicates the Root Termination. + +TerminationIDList ::= SEQUENCE OF TerminationID + +``` + +``` + +MediaDescriptor ::= SEQUENCE +{ + termStateDescr TerminationStateDescriptor OPTIONAL, + streams CHOICE + { + oneStream StreamParms, + multiStream SEQUENCE OF StreamDescriptor + } OPTIONAL, + ... +} + +StreamDescriptor ::= SEQUENCE +{ + streamID StreamID, + streamParms StreamParms +} + +StreamParms ::= SEQUENCE +{ + localControlDescriptor LocalControlDescriptor OPTIONAL, + localDescriptor LocalRemoteDescriptor OPTIONAL, + remoteDescriptor LocalRemoteDescriptor OPTIONAL, + ..., + statisticsDescriptor StatisticsDescriptor OPTIONAL +} + +LocalControlDescriptor ::= SEQUENCE +{ + streamMode StreamMode OPTIONAL, + reserveValue BOOLEAN OPTIONAL, + reserveGroup BOOLEAN OPTIONAL, + propertyParms SEQUENCE OF PropertyParm, + ... +} + +StreamMode ::= ENUMERATED +{ + sendOnly(0), + recvOnly(1), + sendRecv(2), + inactive(3), + loopBack(4), + ... +} + +-- In PropertyParm, value is a SEQUENCE OF octet string. When sent +-- by an MGC the interpretation is as follows: +-- empty sequence means CHOOSE +-- one element sequence specifies value +-- If the sublist field is not selected, a longer sequence means +-- "choose one of the values" (i.e., value1 or value2 etc., from a +-- collection of values. +-- If the sublist field is selected, +-- a sequence with more than one element encodes the value of a +-- list-valued property (i.e., a collection of values, value1 and value2 +-- and ...) +-- Note that when encoding a sub-list of length one, the sublist field +-- may be left unselected. +-- The relation field may only be selected if the value sequence +-- has length 1. It indicates that the MG has to choose a value +-- for the property. E.g., x > 3 (using the greaterThan +-- value for relation) instructs the MG to choose any value larger +-- than 3 for property x. + +``` + +``` + +-- The range field may only be selected if the value sequence +-- has length 2. It indicates that the MG has to choose a value +-- in the range between the first octet in the value sequence and +-- the trailing octet in the value sequence, including the +-- boundary values. +-- When sent by the MG, only responses to an AuditCapability request +-- may contain multiple values, a range, or a relation field. + +``` + +``` +PropertyParm ::= SEQUENCE +``` + +``` + +{ + name PkgdName, + value SEQUENCE OF OCTET STRING, + extraInfo CHOICE + { + relation Relation, + range BOOLEAN, + sublist BOOLEAN + } OPTIONAL, + ... +} + +``` + +``` +Name ::= OCTET STRING(SIZE(2)) +``` + +``` +PkgdName ::= OCTET STRING(SIZE(4)) +``` + +``` + +-- represents Package Name (2 octets) plus property, event, +-- signal names or StatisticsID. (2 octets) +-- To wildcard a package use 0xFFFF for first two octets, CHOOSE +-- is not allowed. To reference native property tag specified in +-- Annex C, use 0x0000 as first two octets. +-- To wildcard a PropertyID, EventID, SignalID, or StatisticsID, use +-- 0xFFFF for last two octets, CHOOSE is not allowed. +-- Wildcarding of Package Name is permitted only if PropertyID, +-- EventID, SignalID, or StatisticsID are also wildcarded. + +``` + +``` +Relation ::= ENUMERATED +``` + +``` + +{ + greaterThan(0), + smallerThan(1), + unequalTo(2), + ...} + +``` + +``` +LocalRemoteDescriptor ::= SEQUENCE +``` + +``` + +{ + propGrps SEQUENCE OF PropertyGroup, + ... +} + +``` + +``` +PropertyGroup ::= SEQUENCE OF PropertyParm +``` + +``` +TerminationStateDescriptor ::= SEQUENCE +``` + +``` + +{ + propertyParms SEQUENCE OF PropertyParm, + eventBufferControl EventBufferControl OPTIONAL, + serviceState ServiceState OPTIONAL, + ... +} + +``` + +``` +EventBufferControl ::= ENUMERATED +``` + +``` + +{ + off(0), + lockStep(1), + ... +} + +``` + +``` + +ServiceState ::= ENUMERATED +{ + test(0), + outOfSvc(1), + inSvc(2), + ... +} + +MuxDescriptor ::= SEQUENCE +{ + muxType MuxType, + termList SEQUENCE OF TerminationID, + nonStandardData NonStandardData OPTIONAL, + ... +} + +MuxType ::= ENUMERATED +{ + h221(0), + h223(1), + h226(2), + v76(3), + ..., + nx64k(4) +} + +StreamID ::= INTEGER(0..65535) -- 16-bit unsigned integer + +EventsDescriptor ::= SEQUENCE +{ + requestID RequestID OPTIONAL, + -- RequestID must be present if eventList + -- is non empty + eventList SEQUENCE OF RequestedEvent, + ... +} + +RequestedEvent ::= SEQUENCE +{ + pkgdName PkgdName, + streamID StreamID OPTIONAL, + eventAction RequestedActions OPTIONAL, + evParList SEQUENCE OF EventParameter, + ... +} + +RegulatedEmbeddedDescriptor ::= SEQUENCE +{ + secondEvent SecondEventsDescriptor OPTIONAL, + signalsDescriptor SignalsDescriptor OPTIONAL, + ... +} + +NotifyBehaviour ::= CHOICE +{ + notifyImmediate NULL, + notifyRegulated RegulatedEmbeddedDescriptor, + neverNotify NULL, + ... +} + +RequestedActions ::= SEQUENCE +{ + keepActive BOOLEAN OPTIONAL, + eventDM EventDM OPTIONAL, +} + +``` + +``` + + secondEvent SecondEventsDescriptor OPTIONAL, + signalsDescriptor SignalsDescriptor OPTIONAL, + ..., + notifyBehaviour NotifyBehaviour OPTIONAL, + resetEventsDescriptor NULL OPTIONAL + } + + EventDM ::= CHOICE + { + digitMapName DigitMapName, + digitMapValue DigitMapValue + } + + SecondEventsDescriptor ::= SEQUENCE + { + requestID RequestID OPTIONAL, + eventList SEQUENCE OF SecondRequestedEvent, + ... + } + + SecondRequestedEvent ::= SEQUENCE + { + pkgdName PkgdName, + streamID StreamID OPTIONAL, + eventAction SecondRequestedActions OPTIONAL, + evParList SEQUENCE OF EventParameter, + ... + } + + SecondRequestedActions ::= SEQUENCE + { + keepActive BOOLEAN OPTIONAL, + eventDM EventDM OPTIONAL, + signalsDescriptor SignalsDescriptor OPTIONAL, + ..., + notifyBehaviour NotifyBehaviour OPTIONAL, + resetEventsDescriptor NULL OPTIONAL + } + + EventBufferDescriptor ::= SEQUENCE OF EventSpec + + EventSpec ::= SEQUENCE + { + eventName EventName, + streamID StreamID OPTIONAL, + eventParList SEQUENCE OF EventParameter, + ... + } + + SignalsDescriptor ::= SEQUENCE OF SignalRequest + + SignalRequest ::= CHOICE + { + signal Signal, + seqSigList SeqSigList, + ... + } + + SeqSigList ::= SEQUENCE + { + id INTEGER(0..65535), + signalList SEQUENCE OF Signal + } + +``` + +``` + +Signal ::= SEQUENCE +{ + signalName SignalName, + streamID StreamID OPTIONAL, + sigType SignalType OPTIONAL, + duration INTEGER (0..65535) OPTIONAL, + notifyCompletion NotifyCompletion OPTIONAL, + keepActive BOOLEAN OPTIONAL, + sigParList SEQUENCE OF SigParameter, + ... + direction SignalDirection OPTIONAL, + requestID RequestID OPTIONAL, + intersigDelay INTEGER (0..65535) OPTIONAL +} + +SignalType ::= ENUMERATED +{ + brief(0), + onOff(1), + timeOut(2), + ... +} + +SignalDirection ::= ENUMERATED +{ + internal(0), + external(1), + both(2), + ... +} + +SignalName ::= PkgdName + +NotifyCompletion ::= BIT STRING +{ + onTimeout(0), onInterruptByEvent(1), + onInterruptByNewSignalDescr(2), otherReason(3), onIteration(4) +} + +SigParameter ::= SEQUENCE +{ + sigParameterName Name, + value Value, + -- For use of extraInfo see the comment related to PropertyParm + extraInfo CHOICE + { + relation Relation, + range BOOLEAN, + sublist BOOLEAN + } OPTIONAL, + ... +} + +-- For an AuditCapReply with all events, the RequestID shall be ALL. +-- ALL is represented by 0xffffffff. +RequestID ::= INTEGER(0..4294967295) -- 32-bit unsigned integer + +ModemDescriptor ::= SEQUENCE +{ + mtl SEQUENCE OF ModemType, + mpl SEQUENCE OF PropertyParm, + nonStandardData NonStandardData OPTIONAL +} + +``` + +``` + +ModemType ::= ENUMERATED +{ + v18(0), + v22(1), + v22bis(2), + v32(3), + v32bis(4), + v34(5), + v90(6), + v91(7), + synchISDN(8), + ... +} + +DigitMapDescriptor ::= SEQUENCE +{ + digitMapName DigitMapName OPTIONAL, + digitMapValue DigitMapValue OPTIONAL +} + +DigitMapName ::= Name + +DigitMapValue ::= SEQUENCE +{ + startTimer INTEGER(0..99) OPTIONAL, + shortTimer INTEGER(0..99) OPTIONAL, + longTimer INTEGER(0..99) OPTIONAL, + digitMapBody IA5String, + -- Units are seconds for start, short and long timers, and hundreds + -- of milliseconds for duration timer. Thus start, short, and long + -- range from 1 to 99 seconds and duration from 100 ms to 9.9 s + -- An exception is the start timer which may equal 0. + -- See A.3 for explanation of DigitMap syntax + ..., + durationTimer INTEGER (0..99) OPTIONAL +} + +ServiceChangeParm ::= SEQUENCE +{ + serviceChangeMethod ServiceChangeMethod, + serviceChangeAddress ServiceChangeAddress OPTIONAL, + serviceChangeVersion INTEGER(0..99) OPTIONAL, + serviceChangeProfile ServiceChangeProfile OPTIONAL, + serviceChangeReason Value, + -- A serviceChangeReason consists of a numeric reason code + -- and an optional text description. + -- The serviceChangeReason shall be a string consisting of + -- a decimal reason code, optionally followed by a single + -- space character and a textual description string. + -- This string is first BER-encoded as an IA5String. + -- The result of this BER-encoding is then encoded as + -- an ASN.1 OCTET STRING type, "double wrapping" the + -- value as was done for package elements. + serviceChangeDelay INTEGER(0..4294967295) OPTIONAL, + -- 32-bit unsigned integer + serviceChangeMgcId Mid OPTIONAL, + timeStamp TimeNotation OPTIONAL, + nonStandardData NonStandardData OPTIONAL, + ..., + serviceChangeInfo AuditDescriptor OPTIONAL, + serviceChangeIncompleteFlag NULL OPTIONAL +} + +ServiceChangeAddress ::= CHOICE + +``` + +``` + +{ + portNumber INTEGER(0..65535), -- TCP/UDP port number + ip4Address IP4Address, + ip6Address IP6Address, + domainName DomainName, + deviceName PathName, + mtpAddress OCTET STRING(SIZE(2..4)), + ... +} + +ServiceChangeResParm ::= SEQUENCE +{ + serviceChangeMgcId Mid OPTIONAL, + serviceChangeAddress ServiceChangeAddress OPTIONAL, + serviceChangeVersion INTEGER(0..99) OPTIONAL, + serviceChangeProfile ServiceChangeProfile OPTIONAL, + timestamp TimeNotation OPTIONAL, + ... +} + +ServiceChangeMethod ::= ENUMERATED +{ + failover(0), + forced(1), + graceful(2), + restart(3), + disconnected(4), + handOff(5), + ... +} + +ServiceChangeProfile ::= SEQUENCE +{ + profileName IA5String(SIZE (1..67)) + -- 64 characters for name, 1 for "/", 2 for version to match ABNF +} + +PackagesDescriptor ::= SEQUENCE OF PackagesItem + +PackagesItem ::= SEQUENCE +{ + packageName Name, + packageVersion INTEGER(0..99), + ... +} + +StatisticsDescriptor ::= SEQUENCE OF StatisticsParameter + +StatisticsParameter ::= SEQUENCE +{ + statName PkgdName, + statValue Value OPTIONAL +} +-- If statistic consists of a sub-lists there will be more than +-- one octetstring in statValue. + +NonStandardData ::= SEQUENCE +{ + nonStandardIdentifier NonStandardIdentifier, + data OCTET STRING +} + +``` + +``` + +NonStandardIdentifier ::= CHOICE +{ + object OBJECT IDENTIFIER, + h221NonStandard H221NonStandard, + experimental IA5String(SIZE(8)), + -- first two characters should be "X-" or "X+" + ... +} + +H221NonStandard ::= SEQUENCE +{ + t35CountryCode1 INTEGER(0..255), + t35CountryCode2 INTEGER(0..255), -- country, as per T.35 + t35Extension INTEGER(0..255), -- assigned nationally + manufacturerCode INTEGER(0..65535), -- assigned nationally + ... +} + +TimeNotation ::= SEQUENCE +{ + date IA5String(SIZE(8)), -- yyyyymmdd format + time IA5String(SIZE(8)) -- hhmmssss format + -- per ISO 8601:2004 +} + +Value ::= SEQUENCE OF OCTET STRING + +END + +``` + +## A.3 DigitMaps and path names + +From a syntactic viewpoint, DigitMaps are strings with syntactic restrictions imposed upon them. The syntax of valid DigitMaps is specified in ABNF [IETF RFC 2234]. The syntax for DigitMaps presented in this clause is for illustrative purposes only. The definition of digitMap in Annex B takes precedence in the case of differences between the two. + +``` + +digitMap = (digitString / LWSP "(" LWSP digitStringList LWSP + ")" LWSP) + +digitStringList = digitString *(LWSP "|" LWSP digitString) + +digitString = 1*(digitStringElement) + +digitStringElement = digitPosition [DOT] + +digitPosition = digitMapLetter / digitMapRange + +digitMapRange = ("x" / (LWSP "[" LWSP digitLetter LWSP "]" LWSP)) + +digitLetter = *((DIGIT "-" DIGIT) / digitMapLetter) + +digitMapLetter = DIGIT ;Basic event symbols + / %x41-4B / %x61-6B ; a-k, A-K + / "L" / "S" / "T" ;Inter-event timers + ; (long, short, start) + / "Z" ;Long duration modifier + +DOT = %x2E ; "." + +SP = %x20 ; space + +HTAB = %x09 ; horizontal tab + +CR = %x0D ; Carriage return + +``` + +``` + +LF = %x0A ; linefeed +LWSP = *(WSP / COMMENT / EOL) +EOL = (CR [LF] / LF) +WSP = SP / HTAB ; white space +SafeChar = DIGIT / ALPHA / "+" / "-" / "&" / + "!" / " " / "/" / "'" / "?" / "@"/ + "^" / "`" / "~" / "*" / "$" / "\" / + "(" / ")" / "%" / "|" / "." +RestChar = ";" / "[" / "]" / "{" / "}" / ":" / "," / "#" / + "<" / ">" / "=" +DIGIT = %x30-39 ; 0-9 +ALPHA = %x41-5A / %x61-7A ; A-Z / a-z + +``` + +A path name is also a string with syntactic restrictions imposed upon it. The ABNF production defining it is copied from Annex B. + +``` + +; Total length of pathNAME must not exceed 64 chars. +pathname = ["*"] NAME *("/" / "*" / ALPHA / DIGIT / "_" / "$" ) + ["@" pathDomainName ] + +; ABNF allows two or more consecutive "." although it is meaningless +; in a path domain name. +pathDomainName = (ALPHA / DIGIT / "*" ) *63(ALPHA / DIGIT / "-" / "*" / ".") +NAME = ALPHA *63(ALPHA / DIGIT / "_") + +``` + +# Annex B + +## Text encoding of the protocol + +(This annex forms an integral part of this Recommendation.) + +## B.1 Coding of wildcards + +In a text encoding of the protocol, while TerminationIDs are arbitrary, by judicious choice of names, the wildcard character, "\*" may be made more useful. When the wildcard character is encountered, it will "match" all TerminationIDs having the same previous and following characters (if appropriate). For example, if there were TerminationIDs of R13/3/1, R13/3/2 and R13/3/3, the TerminationID R13/3/\* would match all of them. There are some circumstances where all terminations must be referred to. The TerminationID "\*" suffices, and is referred to as ALL. The CHOOSE TerminationID "\$" may be used to signal to the MG that it has to create an ephemeral termination or select an idle physical termination. + +## B.2 ABNF specification + +The protocol syntax is presented in ABNF according to [IETF RFC 2234]. + +NOTE 1 – This syntax specification does not enforce all restrictions on element inclusions and values. Some additional restrictions are stated in comments and other restrictions appear in the text of this Recommendation. These additional restrictions are part of the protocol even though not enforced by this Recommendation. + +NOTE 2 – The syntax is context-dependent. For example, "Add" can be the AddToken or a NAME depending on the context in which it occurs. + +Everything in the ABNF and text encoding is case insensitive. This includes TerminationIDs, DigitMapIDs, etc. SDP is case sensitive as per [IETF RFC 2327]. + +``` +; NOTE - The ABNF in this section uses the VALUE construct (or lists of +; VALUE constructs) to encode various package element values (properties, +; signal parameters, etc.). The types of these values vary and are +; specified in the relevant package definition. Several such types are +; described in clause 12.2. +; +; The ABNF specification for VALUE allows a quotedString form or a +; collection of SafeChars. The encoding of package element values into +; ABNF VALUES is specified below. If a type's encoding allows characters +; other than SafeChars, the quotedString form must be used for all values +; of that type, even for specific values that consist only of SafeChars. +; +; String: A string must use the quotedString form of VALUE and can +; contain anything allowable in the quotedString form. +; +; Integer, Double, and Unsigned Integer: Decimal values can be encoded +; using characters 0-9. Hexadecimal values must be prefixed with '0x' +; and can use characters 0-9,a-f,A-F. An octal format is not supported. +; Negative integers start with '-' and must be Decimal. The SafeChar +; form of VALUE must be used. +; +; Character: A UTF-8 encoding of a single letter surrounded by double +; quotes. +; +; Enumeration: An enumeration must use the SafeChar form of VALUE +; and can contain anything allowable in the SafeChar form. +; +; Boolean: Boolean values are encoded as "on" and "off" and are +; case insensitive. The SafeChar form of VALUE must be used. +``` + +``` + +; +; OctetString: Where a package specifies the data type "OctetString" the +; hexadecimal form defined in B.3 shall be used. NOTE - The OctetString BNF +; is only for the carriage of SDP in the Local and Remote Descriptors. +; +; Sub-list: Sub-lists are encoded using the "sublist" branch of +; alternativeValue. A sub-list with a length of one may also be encoded +; simply as a single VALUE of the appropriate type. +; +; Future types: Any defined types must fit within +; the ABNF specification of VALUE. Specifically, if a type's encoding +; allows characters other than SafeChars, the quotedString form must +; be used for all values of that type, even for specific values that +; consist only of SafeChars. +; +; Note that there is no way to use the double quote character within +; a value. +; +; Note that SDP disallows whitespace at the beginning of a line, Megaco +; ABNF allows whitespace before the beginning of the SDP in the +; Local/Remote descriptor. Parsers should accept whitespace between the +; LBRKT following the Local/Remote token and the beginning of the SDP. + +megacoMessage = LWSP [authenticationHeader SEP] message + +authenticationHeader = AuthToken EQUAL SecurityParmIndex COLON + SequenceNum COLON AuthData + +SecurityParmIndex = "0x" 8 (HEXDIG) +SequenceNum = "0x" 8 (HEXDIG) +AuthData = "0x" 24*64 (HEXDIG) + +Message = MegacopToken SLASH Version SEP mId SEP messageBody +; The version of the protocol defined here is equal to 3. + +messageBody = (errorDescriptor / transactionList) + +transactionList = 1*(transactionRequest / transactionReply / + transactionPending / transactionResponseAck / + segmentReply) +;Use of response acks is dependent on underlying transport + +transactionPending = PendingToken EQUAL TransactionID LBRKT RBRKT + +transactionResponseAck = ResponseAckToken LBRKT transactionAck + *(COMMA transactionAck) RBRKT + +transactionAck = TransactionID / (TransactionID "-" TransactionID) + +transactionRequest = TransToken EQUAL TransactionID LBRKT + actionRequest *(COMMA actionRequest) RBRKT + +actionRequest = CtxToken EQUAL ContextID LBRKT ((contextRequest + [COMMA commandRequestList]) / + commandRequestList) RBRKT + +contextRequest = ((contextProperties [COMMA contextAudit]) + / contextAudit) + +contextProperties = contextProperty *(COMMA contextProperty) + +; at-most-once +; EmergencyOff to be used in MG to MGC direction only in ITU-T H.248.1 V1 and V2 +; EmergencyToken or EmergencyOffToken, but not both + +``` + +``` + +contextProperty = (topologyDescriptor / priority / EmergencyToken / + EmergencyOffToken / iepsValue / + contextAttrDescriptor) + +contextAudit = ContextAuditToken LBRKT (contextAuditProperties + *(COMMA contextAuditProperties)) / + indAudcontextAttrDescriptor RBRKT + +; at-most-once except contextAuditSelector +contextAuditProperties = (TopologyToken / EmergencyToken / + PriorityToken / IEPSToken / pkgdName / + contextAuditSelector) + +; at-most-once +contextAuditSelector = priority / emergencyValue / iepsValue / + contextAttrDescriptor / auditSelectLogic + +auditSelectLogic = [ AndAUDITselectToken / OrAUDITselectToken ] +; If empty, AND of selection conditions is assumed. + +indAudcontextAttrDescriptor + = ContextAttrToken LBRKT contextAuditProperties + *(COMMA contextAuditProperties) RBRKT + +; "O-" indicates an optional command +; "W-" indicates a wildcarded response to a command +commandRequestList = ["O-"] ["W-"] commandRequest *(COMMA ["O-"] + ["W-"] commandRequest) + +commandRequest = (ammRequest / subtractRequest / auditRequest / + notifyRequest / serviceChangeRequest) + +transactionReply = ReplyToken EQUAL TransactionID [SLASH segmentNumber + [SLASH SegmentationCompleteToken]] LBRKT + [ImmAckRequiredToken COMMA] + (errorDescriptor / actionReplyList) RBRKT + +segmentReply = MessageSegmentToken EQUAL TransactionID SLASH + segmentNumber [SLASH SegmentationCompleteToken] + +segmentNumber = UINT16 + +actionReplyList = actionReply *(COMMA actionReply) + +actionReply = CtxToken EQUAL ContextID [LBRKT (errorDescriptor / + commandReply / (commandReply COMMA + errorDescriptor)) RBRKT] + +commandReply = ((contextProperties [COMMA commandReplyList]) / + commandReplyList) + +commandReplyList = commandReplies *(COMMA commandReplies) + +commandReplies = (serviceChangeReply / auditReply / ammsReply / + notifyReply) + +;Add, Move and Modify have the same request parameters +ammRequest = (AddToken / MoveToken / ModifyToken) EQUAL + termIDList [LBRKT ammParameter *(COMMA + ammParameter) RBRKT] + +;at-most-once +ammParameter = (mediaDescriptor / modemDescriptor / muxDescriptor / + +``` + +``` + + eventsDescriptor / signalsDescriptor / + digitMapDescriptor / eventBufferDescriptor / + auditDescriptor / statisticsDescriptor) + +ammsReply = (AddToken / MoveToken / ModifyToken / SubtractToken) + EQUAL termIDList [LBRKT terminationAudit RBRKT] + +subtractRequest = SubtractToken EQUAL termIDList [LBRKT + auditDescriptor RBRKT] + +auditRequest = (AuditValueToken / AuditCapToken) EQUAL + termIDList LBRKT auditDescriptor RBRKT + +auditReply = (AuditValueToken / AuditCapToken) + (contextTerminationAudit / auditOther) + +auditOther = EQUAL termIDList [LBRKT terminationAudit RBRKT] + +terminationAudit = auditReturnParameter *(COMMA auditReturnParameter) + +contextTerminationAudit = EQUAL CtxToken (terminationIDList / LBRKT + errorDescriptor RBRKT) + +auditReturnParameter = (mediaDescriptor / modemDescriptor / muxDescriptor / + eventsDescriptor / signalsDescriptor / + digitMapDescriptor / observedEventsDescriptor / + eventBufferDescriptor / statisticsDescriptor / + packagesDescriptor / errorDescriptor / + auditReturnItem) + +auditReturnItem = (MuxToken / ModemToken / MediaToken / + DigitMapToken / StatsToken / ObservedEventsToken / + PackagesToken) + +auditDescriptor = AuditToken LBRKT [auditItem *(COMMA auditItem)] + RBRKT + +notifyRequest = NotifyToken EQUAL termIDList LBRKT + (observedEventsDescriptor [COMMA errorDescriptor]) + RBRKT + +notifyReply = NotifyToken EQUAL termIDList [LBRKT errorDescriptor + RBRKT] + +serviceChangeRequest = ServiceChangeToken EQUAL termIDList LBRKT + serviceChangeDescriptor RBRKT + +serviceChangeReply = ServiceChangeToken EQUAL termIDList [LBRKT + (errorDescriptor / serviceChangeReplyDescriptor) + RBRKT] + +errorDescriptor = ErrorToken EQUAL ErrorCode LBRKT [quotedString] + RBRKT + +ErrorCode = 1*4(DIGIT) ; could be extended + +TransactionID = UINT32 + +mId = ((domainAddress / domainName) [":" portNumber]) / + mtpAddress / deviceName + +; ABNF allows two or more consecutive "." although it is meaningless +; in a domain name. +domainName = "<" (ALPHA / DIGIT) *63(ALPHA / DIGIT / "-" / ".") + +``` + +``` + + ">" + +deviceName = pathNAME + +;The values 0x0, 0xFFFFFFFF and 0xFFFFFFFF are reserved. +; '-' is used for NULL context. '*' is ALL. '$' is CHOOSE. +ContextID = (UINT32 / "*" / "-" / "$") + +domainAddress = "[" (IPv4address / IPv6address) "]" + +; [IETF RFC 2373] contains the definition of IPv6 addresses. +IPv6address = hexpart [":" IPv4address] + +IPv4address = V4hex DOT V4hex DOT V4hex DOT V4hex + +V4hex = 1*3(DIGIT) ; "0".."255" + +; this production, while occurring in [IETF RFC 2373], is not referenced +; IPv6prefix = hexpart SLASH 1*2DIGIT + +hexpart = hexseq "::" [hexseq] / "::" [hexseq] / hexseq + +hexseq = hex4 *(":" hex4) + +hex4 = 1*4HEXDIG + +portNumber = UINT16 + +; Addressing structure of mtpAddress: +; 25 - 15 0 +; | PC | NI | +; 24 - 14 bits 2 bits +; NOTE - 14 bits are defined for international use. +; Two national options exist where the point code is 16 or 24 bits. +; To octet align the mtpAddress the MSBs shall be encoded as 0s. +; An octet shall be represented by 2 hex digits. +mtpAddress = MTPToken LBRKT 4*8 (HEXDIG) RBRKT + +termIDList = (TerminationID / LSBRKT TerminationID 1*(COMMA + TerminationID) RSBRKT) + +terminationIDList = LBRKT TerminationID *(COMMA TerminationID) RBRKT + +; Total length of pathNAME must not exceed 64 chars. +pathNAME = ["*"] NAME *("/" / "*" / ALPHA / DIGIT / "_" / "$") + ["@" pathDomainName] + +; ABNF allows two or more consecutive "." although it is meaningless +; in a path domain name. +pathDomainName = (ALPHA / DIGIT / "*") *63(ALPHA / DIGIT / "-" / + "*" / ".") + +; '*' is ALL. '$' is CHOOSE. +TerminationID = "ROOT" / pathNAME / "$" / "*" + +mediaDescriptor = MediaToken LBRKT mediaParm *(COMMA mediaParm) RBRKT + +; at-most one terminationStateDescriptor +; and either streamParm(s) or streamDescriptor(s) but not both +mediaParm = (streamParm / streamDescriptor / + terminationStateDescriptor) + +; at-most-once per item +streamParm = (localDescriptor / remoteDescriptor / + +``` + +``` + + localControlDescriptor / statisticsDescriptor) + +streamDescriptor = StreamToken EQUAL StreamID LBRKT streamParm *(COMMA + streamParm) RBRKT + +localControlDescriptor = LocalControlToken LBRKT localParm *(COMMA localParm) + RBRKT + +; at-most-once per item except for propertyParm +localParm = (streamMode / propertyParm / reservedValueMode / + reservedGroupMode) + +reservedValueMode = ReservedValueToken EQUAL ("ON" / "OFF") + +reservedGroupMode = ReservedGroupToken EQUAL ("ON" / "OFF") + +streamMode = ModeToken EQUAL streamModes + +streamModes = (SendonlyToken / RecvonlyToken / SendrecvToken / + InactiveToken / LoopbackToken) + +propertyParm = pkgdName parmValue + +; the (Safe)Char '$' means CHOOSE +; the (Safe)Char '*' means ALL +parmValue = (EQUAL alternativeValue / INEQUAL VALUE) + +alternativeValue = (VALUE + / LSRBRKT VALUE *(COMMA VALUE) RSRBRKT + ; sublist + / LBRKT VALUE *(COMMA VALUE) RBRKT + ; alternatives (i.e., A OR B OR ...) + / LSRBRKT VALUE COLON VALUE RSRBRKT + ; range + +; If the alternative or range branches are used, +; a sequence means "choose one of the values" (i.e., value1 or value2, etc. +; from a collection of values). +; If the sublist branch is used, +; a sequence with more than one element encodes the value of a +; list-valued property (i.e., a collection of values, value1 and +; value2 and ...). + +INEQUAL = LWSP (">" / "<" / "#") LWSP ; '#' means "not equal" + +LSRBRKT = LWSP "[" LWSP + +RSRBRKT = LWSP "]" LWSP + +; NOTE - The octet zero is not among the permitted characters in octet +; string. As the current definition is limited to SDP, and a zero octet +; would not be a legal character in SDP, this is not a concern. +localDescriptor = LocalToken LBRKT octetString RBRKT + +remoteDescriptor = RemoteToken LBRKT octetString RBRKT + +eventBufferDescriptor = EventBufferToken [LBRKT eventSpec*(COMMA eventSpec) + RBRKT] + +eventSpec = pkgdName [LBRKT eventSpecParameter *(COMMA + eventSpecParameter) RBRKT] + +eventSpecParameter = (eventStream / eventOther) + +``` + +``` + +eventBufferControl = BufferToken EQUAL eventBufferControlValue +eventBufferControlValue = ("OFF" / LockStepToken) + +terminationStateDescriptor + = TerminationStateToken LBRKT terminationStateParm + *(COMMA terminationStateParm) RBRKT + +; at-most-once per item except for propertyParm +terminationStateParm = (propertyParm / serviceStates / eventBufferControl) + +serviceStates = ServiceStatesToken EQUAL serviceStatesValue +serviceStatesValue = (TestToken / OutOfSvcToken / InSvcToken) + +muxDescriptor = MuxToken EQUAL MuxType terminationIDList + +MuxType = (H221Token / H223Token / H226Token / V76Token / + extensionParameter / Nx64kToken) + +StreamID = UINT16 + +pkgdName = (PackageName SLASH ItemID) ;specific item + / (PackageName SLASH "*") ;all items in package + / ("*" SLASH "*") ; all items supported by the MG + +PackageName = NAME + +ItemID = NAME + +eventsDescriptor = EventsToken [EQUAL RequestID LBRKT requestedEvent + *(COMMA requestedEvent) RBRKT] + +requestedEvent = pkgdName [LBRKT eventParameter *(COMMA + eventParameter) RBRKT] + +notifyRegulated = NotifyRegulatedToken [LBRKT (embedWithSig/ + embedNoSig) RBRKT] + +notifyBehaviour = NotifyImmediateToken / notifyRegulated / + NeverNotifyToken + +; at-most-once each of KeepActiveToken, notifyBehaviour, eventDM, +; ResetEventsDescriptor and eventStream +; at most one of either embedWithSig or embedNoSig but not both +; KeepActiveToken and embedWithSig must not both be present +eventParameter = (embedWithSig / embedNoSig / KeepActiveToken / + eventDM / eventStream / eventOther / + notifyBehaviour / ResetEventsDescriptorToken) + +embedWithSig = EmbedToken LBRKT signalsDescriptor [COMMA + embedFirst] RBRKT + +embedNoSig = EmbedToken LBRKT embedFirst RBRKT + +; at-most-once of each +embedFirst = EventsToken [EQUAL RequestID LBRKT + secondRequestedEvent *(COMMA secondRequestedEvent) + RBRKT] + +secondRequestedEvent = pkgdName [LBRKT secondEventParameter *(COMMA + secondEventParameter) RBRKT] + +; at-most-once each of embedSig, KeepActiveToken, notifyBehaviour, eventDM +; ResetEventsDescriptor or eventStream +; KeepActiveToken and embedSig must not both be present + +``` + +``` + +secondEventParameter = (embedSig / KeepActiveToken / eventDM / + eventStream / eventOther / notifyBehaviour / + ResetEventsDescriptorToken) + +embedSig = EmbedToken LBRKT signalsDescriptor RBRKT + +eventStream = StreamToken EQUAL StreamID + +eventOther = eventParameterName parmValue + +eventParameterName = NAME + +eventDM = DigitMapToken EQUAL((digitMapName) / (LBRKT + digitMapValue RBRKT)) + +signalsDescriptor = SignalsToken [LBRKT signalParm *(COMMA signalParm) + RBRKT] + +signalParm = signalList / signalRequest + +signalRequest = signalName [LBRKT sigParameter *(COMMA sigParameter) + RBRKT] + +signalList = SignalListToken EQUAL signalListId LBRKT + signalListParm *(COMMA signalListParm) RBRKT + +signalListId = UINT16 + +;exactly once signalType, at most once duration and every signal +;parameter +signalListParm = signalRequest + +signalName = pkgdName + +;at-most-once sigStream, at-most-once sigSignalType, +;at-most-once sigDuration, at-most-once sigDirection, +;at-most-once sigRequestID, at-most-once sigIntsigDelay +;every signalParameterName at most once +sigParameter = sigStream / sigSignalType / sigDuration / sigOther / + notifyCompletion / KeepActiveToken / + sigDirection / sigRequestID / sigIntsigDelay + +sigStream = StreamToken EQUAL StreamID + +sigOther = sigParameterName parmValue + +sigParameterName = NAME + +sigSignalType = SignalTypeToken EQUAL signalType + +signalType = (OnOffToken / TimeOutToken / BriefToken) + +sigDuration = DurationToken EQUAL UINT16 + +sigDirection = DirectionToken EQUAL direction + +direction = ExternalToken / InternalToken / BothToken + +sigRequestID = RequestIDToken EQUAL RequestID + +sigIntsigDelay = IntsigDelayToken EQUAL UINT16 + +notifyCompletion = NotifyCompletionToken EQUAL (LBRKT + notificationReason *(COMMA notificationReason) + +``` + +``` + +RBRKT) + +notificationReason = TimeOutToken / InterruptByEventToken / + InterruptByNewSignalsDescrToken / OtherReasonToken / + IterationToken + +observedEventsDescriptor = ObservedEventsToken EQUAL RequestID LBRKT + observedEvent *(COMMA observedEvent) RBRKT + +; time per event, because it might be buffered +observedEvent = [TimeStamp LWSP COLON] LWSP pkgdName [LBRKT + observedEventParameter *(COMMA + observedEventParameter) RBRKT] + +; at-most-once eventStream, every eventParameterName at most once +observedEventParameter = eventStream / eventOther + +; For an AuditCapReply with all events, the RequestID should be ALL. +RequestID = UINT32 / "*" + +modemDescriptor = ModemToken ((EQUAL modemType) / (LSBRKT modemType + *(COMMA modemType) RSBRKT)) [LBRKT propertyParm + *(COMMA propertyParm) RBRKT] + +; at-most-once except for extensionParameter +modemType = V32bisToken / V22bisToken / V18Token / V22Token / + V32Token / V34Token / V90Token / V91Token / + SynchISDNToken / extensionParameter + +digitMapDescriptor = DigitMapToken EQUAL ((LBRKT digitMapValue RBRKT) / + (digitMapName [LBRKT digitMapValue RBRKT])) + +digitMapName = NAME + +digitMapValue = ["T" COLON Timer COMMA] ["S" COLON Timer COMMA] ["L" + COLON Timer COMMA] ["Z" COLON Timer COMMA] digitMap + +Timer = 1*2DIGIT +; Units are seconds for T, S, and L timers, and hundreds of +; milliseconds for Z timer. Thus T, S, and L range from 1 to 99 +; seconds and Z from 100 ms to 9.9 s +; An exception is the start timer which may equal 0. +digitMap = (digitString / LWSP "(" LWSP digitStringList LWSP + ")" LWSP) + +digitStringList = digitString *(LWSP "|" LWSP digitString) + +digitString = 1*(digitStringElement) + +digitStringElement = digitPosition [DOT] + +digitPosition = digitMapLetter / digitMapRange + +digitMapRange = ("x" / (LWSP "[" LWSP digitLetter LWSP "]" LWSP)) + +digitLetter = *((DIGIT "-" DIGIT) / digitMapLetter) + +digitMapLetter = DIGIT ;Basic event symbols + / %x41-4B / %x61-6B ; a-k, A-K + / "L" / "S" / "T" ;Inter-event timers + ; (long, short, start) + / "Z" ;Long duration modifier + +``` + +``` + +; at-most-once, and DigitMapToken and PackagesToken are not allowed +; in AuditCapability command +auditItem = auditReturnItem / SignalsToken / EventBufferToken / + EventsToken / indAudterminationAudit + +indAudterminationAudit = indAudauditReturnParameter *(COMMA + indAudauditReturnParameter) + +indAudauditReturnParameter + = indAudmediaDescriptor / indAudeventsDescriptor / + indAudsignalsDescriptor / + indAuddigitMapDescriptor / + indAudeventBufferDescriptor / + indAudstatisticsDescriptor / + indAudpackagesDescriptor + +indAudmediaDescriptor = MediaToken LBRKT indAudmediaParm *(COMMA + indAudmediaParm) RBRKT + +; either streamParm or streamDescriptor but not both +indAudmediaParm = indAudstreamParm / indAudstreamDescriptor / + indAudterminationStateDescriptor + +; at-most-once +indAudstreamParm = (indAudlocalControlDescriptor / + indAudstatisticsDescriptor / + indAudremoteDescriptor / indAudlocalDescriptor ) + +indAudremoteDescriptor = RemoteToken LBRKT octetString RBRKT +indAudlocalDescriptor = LocalToken LBRKT octetString RBRKT + +indAudstreamDescriptor = StreamToken EQUAL StreamID LBRKT indAudstreamParm + RBRKT + +indAudlocalControlDescriptor + = LocalControlToken LBRKT indAudlocalParm + *(COMMA indAudlocalParm) RBRKT + +; at-most-once per item +indAudlocalParm = ModeToken [(EQUAL/INEQUAL) streamModes] / pkgdName / + propertyParm / ReservedValueToken / + ReservedGroupToken +; propertyparm and streamModes are used only to specify audit selection +; criteria. AND/OR selection logic is specified at context level. + +indAudterminationStateDescriptor + = TerminationStateToken LBRKT + indAudterminationStateParm RBRKT +; NOTE - There is an inconsistency between request and reply for individual +; audits. The request does not permit multiple parameters to be contained within +; a single TerminationState Token whereas the reply permits multiple parameters. + +indAudterminationStateParm + = pkgdName / propertyParm / ServiceStatesToken + [(EQUAL/INEQUAL) serviceStatesValue ] / BufferToken +; When values are included a Select operation is implied. +; AND/OR logic is specified at context level. + +indAudeventBufferDescriptor + = EventBufferToken LBRKT indAudeventSpec RBRKT + +indAudeventSpec = pkgdName [LBRKT indAudeventSpecParameter RBRKT] + +indAudeventSpecParameter= eventStream / eventParameterName + +``` + +``` + +indAudeventsDescriptor = EventsToken [EQUAL RequestID] LBRKT + indAudrequestedEvent RBRKT + +indAudrequestedEvent = pkgdName + +indAudsymbolsDescriptor = SymbolsToken LBRKT [indAudsymbolsParm] RBRKT + +indAudsymbolsParm = indAudsymbolsList / indAudsymbolsRequest + +indAudsymbolsRequest = signalName [LBRKT indAudsymbolsRequestParm + *(COMMA indAudsymbolsRequestParm) RBRKT] + +indAudsymbolsRequestParm = sigStream / sigRequestID + +indAudsymbolsList = SignalListToken EQUAL signalListId [LBRKT + indAudsymbolsListParm RBRKT] + +indAudsymbolsListParm = indAudsymbolsRequest + +indAddigitMapDescriptor= DigitMapToken EQUAL (digitMapName) + +indAudstatisticsDescriptor + = StatsToken LBRKT pkgdName RBRKT + +indAudpackagesDescriptor= PackagesToken LBRKT packagesItem RBRKT + +serviceChangeDescriptor = ServicesToken LBRKT serviceChangeParm *(COMMA + serviceChangeParm) RBRKT + +; each parameter at-most-once, except auditItem +; at most one of either serviceChangeAddress or serviceChangeMgcId but +; not both +; serviceChangeMethod and serviceChangeReason are REQUIRED +serviceChangeParm = serviceChangeMethod / serviceChangeReason / + serviceChangeDelay / serviceChangeAddress / + serviceChangeProfile / extension / TimeStamp / + serviceChangeMgcId / serviceChangeVersion / + ServiceChangeIncompleteToken / auditItem) + +serviceChangeReplyDescriptor + = ServicesToken LBRKT servChgReplyParm *(COMMA + servChgReplyParm) RBRKT + +; at-most-once. Version is REQUIRED on first ServiceChange response +; at most one of either serviceChangeAddress or serviceChangeMgcId but +; not both +servChgReplyParm = serviceChangeAddress / serviceChangeMgcId / + serviceChangeProfile / serviceChangeVersion / + TimeStamp + +serviceChangeMethod = MethodToken EQUAL (FailoverToken / ForcedToken / + GracefulToken / RestartToken / DisconnectedToken / + HandOffToken / extensionParameter) + +; A serviceChangeReason consists of a numeric reason code +; and an optional text description. +; A serviceChangeReason must be encoded using the quotedString +; form of VALUE. +; The quotedString shall contain a decimal reason code, +; optionally followed by a single space character and a +; textual description string. +serviceChangeReason = ReasonToken EQUAL VALUE + +``` + +``` + +serviceChangeDelay = DelayToken EQUAL UINT32 +serviceChangeAddress = ServiceChangeAddressToken EQUAL (mId / portNumber) +serviceChangeMgcId = MgcIdToken EQUAL mId +serviceChangeProfile = ProfileToken EQUAL NAME SLASH Version +serviceChangeVersion = VersionToken EQUAL Version +extension = extensionParameter parmValue +packagesDescriptor = PackagesToken LBRKT packagesItem *(COMMA + packagesItem) RBRKT +Version = 1*2(DIGIT) +packagesItem = NAME "-" UINT16 +TimeStamp = Date "T" Time ; per ISO 8601:2004 + +; Date = yyyymmdd +Date = 8(DIGIT) + +; Time = hhmmssss +Time = 8(DIGIT) + +statisticsDescriptor = StatsToken [LBRKT statisticsParameter *(COMMA + statisticsParameter) RBRKT] + +;at-most-once per item +statisticsParameter = pkgdName [EQUAL VALUE / + (LSBRKT VALUE *(COMMA VALUE) RSBRKT)] + +topologyDescriptor = TopologyToken LBRKT topologyTriple *(COMMA + topologyTriple) RBRKT + +topologyTriple = terminationA COMMA terminationB COMMA + topologyDirection [COMMA eventStream] + +terminationA = TerminationID +terminationB = TerminationID + +topologyDirection = BothwayToken / IsolateToken / OnewayToken / + OnewayExternalToken / OnewayBothToken + +priority = PriorityToken EQUAL UINT16 +iepsValue = IEPSToken EQUAL ("ON" / "OFF") + +emergencyValue = EmergencyValueToken EQUAL (EmergencyToken / + EmergencyOffToken) + +contextAttrDescriptor = ContextAttrToken LBRKT (contextIdList / + propertyParm *(COMMA propertyParm)) RBRKT + +; When using the contextIdList construct, the ContextID in the +; actionReply construct shall be the same as the ContextID in the +; associated actionRequest +contextIdList = ContextListToken EQUAL LBRKT ContextID + *(COMMA ContextID) RBRKT + +extensionParameter = "X" ("-" / "+") 1*6(ALPHA / DIGIT) + +``` + +``` + +; octetString is used to describe SDP defined in [IETF RFC 2327]. +; Caution should be taken if CRLF in RFC 2327 is used. +; To be safe, use EOL in this ABNF. +; Whenever "}" appears in SDP, it is escaped by "\", e.g., "\}" +octetString = *(nonEscapeChar) + +nonEscapeChar = ("}\" / %x01-7C / %x7E-FF) + +; NOTE - The double-quote character is not allowed in quotedString. +quotedString = DQUOTE *(SafeChar / EOL / %x80-FF / RestChar / WSP) +DQUOTE + +UINT16 = 1*5(DIGIT) ; %x0-FFFF + +UINT32 = 1*10(DIGIT) ; %x0-FFFFFFFF + +NAME = ALPHA *63(ALPHA / DIGIT / "_") + +VALUE = quotedString / 1*(SafeChar / %x80-FF) + +SafeChar = DIGIT / ALPHA / "+" / "-" / "&" / +"!" / " " / "/" / ":" / "?" / "@"/ +"^" / "`" / "~" / "*" / "$" / "\" / +"(" / ")" / "%" / "|" / "." + +EQUAL = LWSP %x3D LWSP ; "=" + +COLON = %x3A ; ":" + +LBRKT = LWSP %x7B LWSP ; "{" + +RBRKT = LWSP %x7D LWSP ; "}" + +COMMA = LWSP %x2C LWSP ; "," + +DOT = %x2E ; "." + +SLASH = %x2F ; "/" + +ALPHA = %x41-5A / %x61-7A ; A-Z / a-z + +DIGIT = %x30-39 ; 0-9 + +DQUOTE = %x22 ; " (Double Quote) + +HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F" + +SP = %x20 ; space + +HTAB = %x09 ; horizontal tab + +CR = %x0D ; Carriage return + +LF = %x0A ; linefeed + +LWSP = *(WSP / COMMENT / EOL) + +EOL = (CR [LF] / LF) + +WSP = SP / HTAB ; white space + +SEP = (WSP / EOL / COMMENT) LWSP + +``` + +``` + +COMMENT = ";" *(SafeChar/ RestChar / WSP / %x22) EOL + +RestChar = ";" / "[" / "]" / "{" / "}" / ":" / "," / "#" / + "<" / ">" / "=" + +; New Tokens added to sigParameter must take the format of SPA* +; * may be of any form i.e., SPAM +; New Tokens added to eventParameter must take the form of EPA* +; * may be of any form i.e., EPAD + +AddToken = ("Add" / "A") +AndAUDITSelectToken = ("ANDLgc") +AuditToken = ("Audit" / "AT") +AuditCapToken = ("AuditCapability" / "AC") +AuditValueToken = ("AuditValue" / "AV") +AuthToken = ("Authentication" / "AU") +BothToken = ("Both" / "B") +BothwayToken = ("Bothway" / "BW") +BriefToken = ("Brief" / "BR") +BufferToken = ("Buffer" / "BF") +CtxToken = ("Context" / "C") +ContextAuditToken = ("ContextAudit" / "CA") +ContextAttrToken = ("ContextAttr" / "CT") +ContextListToken = ("ContextList" / "CLT") +DigitMapToken = ("DigitMap" / "DM") +DirectionToken = ("SPADirection" / "SPADI") +DisconnectedToken = ("Disconnected" / "DC") +DelayToken = ("Delay" / "DL") +DurationToken = ("Duration" / "DR") +EmbedToken = ("Embed" / "EM") +EmergencyToken = ("Emergency" / "EG") +EmergencyOffToken = ("EmergencyOff" / "EGO") +EmergencyValueToken = ("EmergencyValue" / "EGV") +ErrorToken = ("Error" / "ER") +EventBufferToken = ("EventBuffer" / "EB") +EventsToken = ("Events" / "E") +ExternalToken = ("External" / "EX") +FailoverToken = ("Failover" / "FL") +ForcedToken = ("Forced" / "FO") +GracefulToken = ("Graceful" / "GR") +H221Token = ("H221") +H223Token = ("H223") +H226Token = ("H226") +HandOffToken = ("HandOff" / "HO") +IEPSToken = ("IEPSCall" / "IEPS") +ImmAckRequiredToken = ("ImmAckRequired" / "IA") +InactiveToken = ("Inactive" / "IN") +InternalToken = ("Internal" / "IT") +IntsigDelayToken = ("Intersignal" / "SPAIS") +IsolateToken = ("Isolate" / "IS") +InSvcToken = ("InService" / "IV") +InterruptByEventToken = ("IntByEvent" / "IBE") +InterruptByNewSignalsDescrToken = ("IntBySigDescr" / "IBS") +IterationToken = ("Iteration" / "IR") +KeepActiveToken = ("KeepActive" / "KA") +LocalToken = ("Local" / "L") +LocalControlToken = ("LocalControl" / "O") +LockStepToken = ("LockStep" / "SP") +LoopbackToken = ("Loopback" / "LB") +MediaToken = ("Media" / "M") +MegacopToken = ("MEGACO" / "!") +MessageSegmentToken = ("Segment" / "SM") +MethodToken = ("Method" / "MT") + +``` + +``` + +MgcIdToken = ("MgcIdToTry") / "MG" +ModeToken = ("Mode") / "MO" +ModifyToken = ("Modify") / "MF" +ModemToken = ("Modem") / "MD" +MoveToken = ("Move") / "MV" +MTPToken = ("MTP") / "MX" +MuxToken = ("Mux") / "MX" +NeverNotifyToken = ("NeverNotify") / "NBNN" +NotifyToken = ("Notify") / "N" +NotifyCompletionToken = ("NotifyCompletion") / "NC" +NotifyImmediateToken = ("ImmediateNotify") / "NBIN" +NotifyRegulatedToken = ("RegulatedNotify") / "NBRN" +Nx64kToken = ("Nx64Kservice") / "N64" +ObservedEventsToken = ("ObservedEvents") / "OE" +OnewayToken = ("Oneway") / "OW" +OnewayBothToken = ("OnewayBoth") / "OWB" +OnewayExternalToken = ("OnewayExternal") / "OWE" +OnOffToken = ("OnOff") / "OO" +OrAUDITselectToken = ("ORLgc") / "OR" +OtherReasonToken = ("OtherReason") / "OR" +OutOfSvcToken = ("OutOfService") / "OS" +PackagesToken = ("Packages") / "PG" +PendingToken = ("Pending") / "PN" +PriorityToken = ("Priority") / "PR" +ProfileToken = ("Profile") / "PF" +ReasonToken = ("Reason") / "RE" +ReconlyToken = ("ReceiveOnly") / "RC" +ReplyToken = ("Reply") / "P" +ResetEventsDescriptorToken = ("ResetEventsDescriptor") / "RSE" +RestartToken = ("Restart") / "RS" +RemoteToken = ("Remote") / "R" +RequestIDToken = ("SPARquestID") / "SPARQ" +ReservedGroupToken = ("ReservedGroup") / "RG" +ReservedValueToken = ("ReservedValue") / "RV" +SegmentationCompleteToken = ("END") / "&" +SendonlyToken = ("SendOnly") / "SO" +SendrecvToken = ("SendReceive") / "SR" +ServicesToken = ("Services") / "SV" +ServiceStatesToken = ("ServiceStates") / "SI" +ServiceChangeIncompleteToken = ("ServiceChangeInc") / "SIC" +ServiceChangeToken = ("ServiceChange") / "SC" +ServiceChangeAddressToken = ("ServiceChangeAddress") / "AD" +SignalListToken = ("SignalList") / "SL" +SignalsToken = ("Signals") / "SG" +SignalTypeToken = ("SignalType") / "SY" +StatsToken = ("Statistics") / "SA" +StreamToken = ("Stream") / "ST" +SubtractToken = ("Subtract") / "S" +SynchISDNToken = ("SynchISDN") / "SN" +TerminationStateToken = ("TerminationState") / "TS" +TestToken = ("Test") / "TE" +TimeoutToken = ("Timeout") / "TO" +TopologyToken = ("Topology") / "TP" +TransToken = ("Transaction") / "T" +ResponseAckToken = ("TransactionResponseAck") / "K" +V18Token = ("V18") / "V18" +V22Token = ("V22") / "V22" +V22bisToken = ("V22b") / "V22b" +V32Token = ("V32") / "V32" +V32bisToken = ("V32b") / "V32b" + +``` + +``` + +V34Token = ("V34") +V76Token = ("V76") +V90Token = ("V90") +V91Token = ("V91") +VersionToken = ("Version" / "V") + +``` + +## B.3 Hexadecimal octet coding + +Hexadecimal octet coding is a means for representing package elements of type Octet String as a string of hexadecimal digits, with two digits representing each octet. This octet encoding should be used when encoding values of type Octet String in the text version of the protocol. + +For each octet, the 8-bit sequence is encoded as two hexadecimal digits. Bit 0 is the first transmitted or left most; bit 7 is the last or right most. + +NOTE – This means that Bit 0 is the MSB of the original octet and Bit 7 is the LSB of the original octet, according to the common convention used to specify octet values. + +Bits 7-4 are encoded as the first hexadecimal digit, with Bit 7 as MSB of the first hexadecimal digit and Bit 4 as LSB of the first hexadecimal digit. Bits 3-0 are encoded as the second hexadecimal digit, with Bit 3 as MSB of the second hexadecimal digit and Bit 0 as LSB of the second hexadecimal digit. + +NOTE – The above encoding results in the reversal of bits from the original octet. + +Examples: + +| Octet bit pattern | Hexadecimal coding | +|-------------------------------------|--------------------| +| 00011011 | D8 | +| 11100100 | 27 | +| 10000011 10100010 11001000 00001001 | C1451390 | + +This encoding is not applicable to the octetString construct defined in clause B.2 + +## B.4 Hexadecimal octet sequence + +A hexadecimal octet sequence is an even number of hexadecimal digits, terminated by a character. + +# Annex C + +## Tags for media stream properties + +(This annex forms an integral part of this Recommendation.) + +Parameters for Local, Remote and LocalControl Descriptors are specified as tag-value pairs if binary encoding is used for the protocol. This annex contains the property names (PropertyID), the tags (Property tag), type of the property (Type) and the values (Value). Values presented in the Value field when the field contains references shall be regarded as "information". The reference contains the normative values. If a value field does not contain a reference, then the values in that field can be considered as "normative". + +Referencing of Annex C properties follows the PackageID/PropertyID structure; however Annex C is not in itself a package. Annex C is considered to have PackageID 0x0000 for binary encoding and "anxc" for text encoding. For text encoding of ITU-T H.248.1, Annex C shall only be used if the required property is either not defined by a package or not represented by SDP. The nesting of one Annex C property inside another is forbidden. + +Tags are given as hexadecimal numbers in this annex. When setting the value of a property, an MGC may underspecify the value according to one of the mechanisms specified in clause 7.1.1. + +It is optional to support the properties in this annex or any of its subclauses. For example, only three properties from clause C.3 and only five properties from clause C.8 might be implemented. + +For type "enumeration" the value is represented by the value in brackets, e.g., Send (0), Receive (1). Annex C properties with the types "N bits" or "M Octets" should be treated as octet strings when encoding the protocol. Properties with "N bit integer" shall be treated as an integers. "String" shall be treated as an IA5String when encoding the protocol. + +When a type is smaller than one octet, the value shall be stored in the low-order bits of an octet string of size one octet. 0-padding should be used for the remaining high-order bits. + +## C.1 General media attributes + +| PropertyID | Property tag | Type | Value | +|------------------|--------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Media | 1001 | Enumeration | Audio(0), Video(1), Data(2) | +| Transmissionmode | 1002 | Enumeration | Send(0), Receive(1), Send&Receive(2) | +| NumberofChannels | 1003 | Unsigned integer | 0-255 | +| Samplingrate | 1004 | Unsigned integer | 0-2 32 | +| Bitrate | 1005 | Integer | (0..4294967295)
NOTE – Units of 100 bit/s. | +| ACodec | 1006 | Octet string | Audio Codec Type:[ITU-T Q.765.5]
Non-ITU-T codecs are defined with the appropriate standards organization under a defined Organizational Identifier. | +| Samplepp | 1007 | Unsigned integer | Maximum samples or frames per packet:
0..65535 | +| Silencesupp | 1008 | Boolean | Silence Suppression: True/False | +| Encrypttype | 1009 | Octet string | [ITU-T H.245] | + +| PropertyID | Property tag | Type | Value | +|------------|--------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Encryptkey | 100A | Octet string size (0..65535) | Encryption key [ITU-T H.235.0] | +| Echocanc | 100B | | Not Used. See E.13 for an example of possible Echo Control Properties. | +| Gain | 100C | | Not Used. See E.13 for an available gain property. | +| Jitterbuff | 100D | Unsigned integer | Jitter buffer size in ms: 0..65535 | +| PropDelay | 100E | Unsigned integer | Propagation Delay: 0..65535
Maximum propagation delay in milliseconds for the bearer connection between two media gateways. The maximum delay will be dependent on the bearer technology. | +| RTPpayload | 100F | Integer | Payload type in RTP Profile for Audio and Video Conferences with Minimal Control [IETF RFC 1890] | +| Ptime | 1010 | Integer | Packetization Time
This gives the length of time in milliseconds represented by the media in a packet. [IETF RFC 2327] | + +## C.2 Mux properties + +| PropertyID | Property tag | Type | Value | +|------------|--------------|--------------|---------------------------------------------| +| H222 | 2001 | Octet string | H222LogicalChannelParameters [ITU-T H.245] | +| H223 | 2002 | Octet string | H223LogicalChannelParameters [ITU-T H.245] | +| V76 | 2003 | Octet string | V76LogicalChannelParameters [ITU-T H.245] | +| H2250 | 2004 | Octet string | H2250LogicalChannelParameters [ITU-T H.245] | + +## C.3 General bearer properties + +| PropertyID | Property tag | Type | Value | +|------------|--------------|-------------|------------------------------------------------------------------------------| +| Mediatx | 3001 | Enumeration | Media Transport Type
TDM Circuit(0), ATM(1), FR(2), Ipv4(3), Ipv6(4), ... | +| BIR | 3002 | 4 octets | Value depends on transport technology | +| NSAP | 3003 | 1-20 octets | See NSAP.
Annex A/[ITU-T X.213] | + +## C.4 General ATM properties + +| PropertyID | Property tag | Type | Value | +|------------|--------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AESA | 4001 | 20 octets | ATM End System Address | +| VPVC | 4002 | 4 octets:
VPCI in first
two least
significant
octets, VCI in
second two
octets | VPCI/VCI
Recommendation ITU-T Q.2931 | +| SC | 4003 | Enumeration | Service Category: CBR(0), nrt-VBR1(1),
nrt-VBR2(2), nrt-VBR3(3), rt-VBR1(4),
rt-VBR2(5), rt-VBR3(6), UBR1(7),
UBR2(8), ABR(9).
[ATM Forum UNI 4.0] | +| BCOB | 4004 | 5-bit integer | Broadband Bearer Class
[ITU-T Q.2961.2] | +| BBTC | 4005 | 7-bit integer | Broadband Transfer Capability
[ITU-T Q.2961.1] | +| ATC | 4006 | Enumeration | I.371 ATM Traffic Capability
DBR(0), SBR1(1), SBR2(2), SBR3(3),
ABT/IT(4), ABT/DT(5), ABR(6)
[ITU-T I.371] | +| STC | 4007 | 2 bits | Susceptibility to clipping:
Bits
2 1
0 0 not susceptible to clipping
0 1 susceptible to clipping
[ITU-T Q.2931] | +| UPCC | 4008 | 2 bits | User Plane Connection configuration:
Bits
2 1
0 0 point-to-point
0 1 point-to-multipoint
[ITU-T Q.2931] | +| PCR0 | 4009 | 24-bit integer | Peak Cell Rate (For CLP = 0)
[ITU-T Q.2931] | +| SCR0 | 400A | 24-bit integer | Sustainable Cell Rate (For CLP = 0)
[ITU-T Q.2961.1] | +| MBS0 | 400B | 24-bit integer | Maximum Burst Size (For CLP = 0)
[ITU-T Q.2961.1] | +| PCR1 | 400C | 24-bit integer | Peak Cell Rate (For CLP = 0 + 1)
[ITU-T Q.2931] | +| SCR1 | 400D | 24-bit integer | Sustainable Cell Rate (For CLP = 0 + 1)
[ITU-T Q.2961.1] | +| MBS1 | 400E | 24-bit integer | Maximum Burst Size (For CLP = 0 + 1)
[ITU-T Q.2961.1] | + +| PropertyID | Property tag | Type | Value | | | | | | | | | | | | | | | +|-------------------|--------------------------------------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------|---|--------------------------------------------------------------------|---|-----------|---|----------|---|----------|---|-----------|---|--------------------| +| BEI | 400F | Boolean | Best Effort Indicator
Value 1 indicates that BEI is to be included in the ATM signalling; value 0 indicates that BEI is not to be included in the ATM signalling.
[ATM Forum UNI 4.0] | | | | | | | | | | | | | | | +| TI | 4010 | Boolean | Tagging Indicator
Value 0 indicates that tagging is not allowed; value 1 indicates that tagging is requested.
[ITU-T Q.2961.1] | | | | | | | | | | | | | | | +| FD | 4011 | Boolean | Frame Discard
Value 0 indicates that no frame discard is allowed; value 1 indicates that frame discard is allowed.
[ATM Forum UNI 4.0] | | | | | | | | | | | | | | | +| A2PCDV | 4012 | 24-bit integer | Acceptable 2-point CDV
[ITU-T Q.2965.2] | | | | | | | | | | | | | | | +| C2PCDV | 4013 | 24-bit integer | Cumulative 2-point CDV
[ITU-T Q.2965.2] | | | | | | | | | | | | | | | +| APPCDV | 4014 | 24-bit integer | Acceptable P-P CDV
[ATM Forum UNI 4.0] | | | | | | | | | | | | | | | +| CPPCDV | 4015 | 24-bit integer | Cumulative P-P CDV
[ATM Forum UNI 4.0] | | | | | | | | | | | | | | | +| ACLR | 4016 | 8-bit integer | Acceptable Cell Loss Ratio
[ITU-T Q.2965.2], [ATM Forum UNI 4.0] | | | | | | | | | | | | | | | +| MEETD | 4017 | 16-bit integer | Maximum End-to-end transit delay
[ITU-T Q.2965.2], [ATM Forum UNI 4.0] | | | | | | | | | | | | | | | +| CEETD | 4018 | 16-bit integer | Cumulative End-to-end transit delay
[ITU-T Q.2965.2], [ATM Forum UNI 4.0] | | | | | | | | | | | | | | | +| QosClass | 4019 | Integer 0-5 | QoS Class
QoS Class Meaning
0 Default QoS associated with the ATC as defined in [ITU-T Q.2961.2]
1 Stringent
2 Tolerant
3 Bi-level
4 Unbounded
5 Stringent Bi-level
[ITU-T Q.2965.1] | QoS Class | Meaning | 0 | Default QoS associated with the ATC as defined in [ITU-T Q.2961.2] | 1 | Stringent | 2 | Tolerant | 3 | Bi-level | 4 | Unbounded | 5 | Stringent Bi-level | +| QoS Class | Meaning | | | | | | | | | | | | | | | | | +| 0 | Default QoS associated with the ATC as defined in [ITU-T Q.2961.2] | | | | | | | | | | | | | | | | | +| 1 | Stringent | | | | | | | | | | | | | | | | | +| 2 | Tolerant | | | | | | | | | | | | | | | | | +| 3 | Bi-level | | | | | | | | | | | | | | | | | +| 4 | Unbounded | | | | | | | | | | | | | | | | | +| 5 | Stringent Bi-level | | | | | | | | | | | | | | | | | + +| PropertyID | Property tag | Type | Value | +|------------|--------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AALtype | 401A | 1 octet | AAL Type
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 AAL for voice
0 0 0 0 0 0 0 1 AAL type 1
0 0 0 0 0 0 1 0 AAL type 2
0 0 0 0 0 0 1 1 AAL type 3/4
0 0 0 0 0 1 0 1 AAL type 5
0 0 0 1 0 0 0 0 user-defined AAL
[ITU-T Q.2931] | + +## C.5 Frame relay + +| PropertyID | Property tag | Type | Value | +|---------------------|--------------|------------------|-----------------------------------------------| +| DLCI | 5001 | Unsigned integer | Data link connection ID | +| CID | 5002 | Unsigned integer | sub-channel ID | +| SIDNoiselevel | 5003 | Unsigned integer | silence insertion descriptor | +| PrimaryPayload type | 5004 | Unsigned integer | Primary Payload Type
Covers FAX and codecs | + +## C.6 IP + +| PropertyID | Property tag | Type | Value | +|------------|--------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| IPv4 | 6001 | 32 bits
Ipv4Address | IPv4Address
[IETF RFC 791] | +| IPv6 | 6002 | 128 bits | IPv6 Address
[IETF RFC 2460] | +| Port | 6003 | Unsigned integer | 0..65535 | +| Porttype | 6004 | Enumerated | TCP(0), UDP(1), SCTP(2) | +| RtcpbwRS | 6005 | Integer | RS RTCP bandwidth modifier indicates the RTCP bandwidth allocated to active data senders (as defined by the RTP specification)
[IETF RFC 3556] | +| RtcpbwRR | 6006 | Integer | RR RTCP bandwidth modifier indicates the RTCP bandwidth allocated to other participants in the RTP session (i.e., receivers)
[IETF RFC 3556] | + +## C.7 ATM AAL 2 + +| PropertyID | Property tag | Type | Value | +|------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AESA | 7001 | 20 octets | AAL 2 service endpoint address as defined in the referenced Recommendation.
ESEA
NSEA
[ITU-T Q.2630.1] | +| BIR | See clause C.3 | 4 octets | Served user-generated reference as defined in the referenced Recommendation.
SUGR
[ITU-T Q.2630.1] | +| ALC | 7002 | 12 octets | AAL 2 link characteristics as defined in the referenced Recommendation.
Maximum/Average CPS-SDU bit rate;
Maximum/Average CPS-SDU size
[ITU-T Q.2630.1] | +| SSCS | 7003 | I.366.2:
Audio
(8 octets);
Multirate
(3 octets), or
I.366.1:
SAR-assured
(14 octets);
SAR-
unassured
(7 octets). | Service specific convergence sublayer information as defined in:
– [ITU-T Q.2630.1],
and used in:
– [ITU-T I.366.2]: Audio/Multirate;
– [ITU-T I.366.1]: SAR-assured/-
unassured.
[ITU-T Q.2630.1], [ITU-T I.366.1] and
[ITU-T I.366.2] | +| SUT | 7004 | 1..254 octets | Served user transport parameter as defined in the referenced Recommendation.
[ITU-T Q.2630.1] | +| TCI | 7005 | Boolean | Test connection indicator as defined in the referenced Recommendation.
[ITU-T Q.2630.1] | +| Timer_CU | 7006 | 32-bit integer | Timer-CU
Milliseconds to hold partially filled cell before sending. | +| MaxCPSSDU | 7007 | 8-bit integer | Maximum Common Part Sublayer Service Data Unit
[ITU-T Q.2630.1] | +| CID | 7008 | 8 bits | Subchannel ID: 0-255
[ITU-T I.363.2] | + +## C.8 ATM AAL 1 + +| PropertyID | Property tag | Type | Value | +|------------|-------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BIR | See table in clause C.3 | 4-29 octets | GIT (Generic Identifier Transport)
[ITU-T Q.2941.1] | +| AAL1ST | 8001 | 1 octet | AAL 1 Subtype
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 null
0 0 0 0 0 0 0 1 voiceband signal transport on 64 kbit/s
0 0 0 0 0 0 1 0 circuit transport
0 0 0 0 0 1 0 0 high-quality audio signal transport
0 0 0 0 0 1 0 1 video signal transport
[ITU-T Q.2931] | +| CBRR | 8002 | 1 octet | CBR Rate
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 1 64 kbit/s
0 0 0 0 0 1 0 0 1544 kbit/s
0 0 0 0 0 1 0 1 6312 kbit/s
0 0 0 0 0 1 1 0 32 064 kbit/s
0 0 0 0 0 1 1 1 44 736 kbit/s
0 0 0 0 1 0 0 0 97 728 kbit/s
0 0 0 1 0 0 0 0 2048 kbit/s
0 0 0 1 0 0 0 1 8448 kbit/s
0 0 0 1 0 0 1 0 34 368 kbit/s
0 0 0 1 0 0 1 1 139 264 kbit/s
0 1 0 0 0 0 0 0 $n \times 64$ kbit/s
0 1 0 0 0 0 0 1 $n \times 8$ kbit/s
[ITU-T Q.2931] | +| MULT | See table in clause C.9 | | Multiplier, or $n \times 64\text{k}/8\text{k}/300$
[ITU-T Q.2931] | +| SCRI | 8003 | 1 octet | Source Clock Frequency Recovery Method
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 null
0 0 0 0 0 0 0 1 SRTS
0 0 0 0 0 0 1 0 ACM
[ITU-T Q.2931] | +| ECM | 8004 | 1 octet | Error Correction Method
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 null
0 0 0 0 0 0 0 1 FEC – Loss
0 0 0 0 0 0 1 0 FEC – Delay
[ITU-T Q.2931] | + +| PropertyID | Property tag | Type | Value | +|------------|--------------|----------------|----------------------------------------------------------------------------------------| +| SDTB | 8005 | 16-bit integer | Structured Data Transfer Blocksize
Block size of SDT CBR service
[ITU-T I.363.1] | +| PFCI | 8006 | 8-bit integer | Partially filled cells identifier
1-47
[ITU-T I.363.1] | + +## C.9 Bearer capabilities + +The table entries referencing [ITU-T Q.931] refer to the encoding in the bearer capability information element of ITU-T Q.931, not to the low layer information element. + +| PropertyID | Property tag | Type | Value | +|------------|--------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TMR | 9001 | 1 octet | Transmission Medium Requirement [ITU-T Q.763]
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 speech
0 0 0 0 0 0 0 1 spare
0 0 0 0 0 0 1 0 64 kbit/s unrestricted
0 0 0 0 0 0 1 1 3.1 kHz audio
0 0 0 0 0 1 0 0 reserved for alternate speech
(service 2)/64 kbit/s
unrestricted (service 1)
0 0 0 0 0 1 0 1 reserved for alternate
64 kbit/s unrestricted
(service 1)/speech (service 2)
0 0 0 0 0 1 1 0 64 kbit/s preferred
0 0 0 0 0 1 1 1 2 × 64 kbit/s unrestricted
0 0 0 0 1 0 0 0 384 kbit/s unrestricted
0 0 0 0 1 0 0 1 1536 kbit/s unrestricted
0 0 0 0 1 0 1 0 1920 kbit/s unrestricted
0 0 0 0 1 0 1 1
through spare
0 0 0 0 1 1 1 1
0 0 0 1 0 0 0 0 3 × 64 kbit/s unrestricted
0 0 0 1 0 0 0 1 4 × 64 kbit/s unrestricted
0 0 0 1 0 0 1 0 5 × 64 kbit/s unrestricted
0 0 0 1 0 0 1 1 spare
0 0 0 1 0 1 0 0 7 × 64 kbit/s unrestricted
0 0 0 1 0 1 0 1 8 × 64 kbit/s unrestricted
0 0 0 1 0 1 1 0 9 × 64 kbit/s unrestricted
0 0 0 1 0 1 1 1 10 × 64 kbit/s unrestricted
0 0 0 1 1 0 0 0 11 × 64 kbit/s unrestricted
0 0 0 1 1 0 0 1 12 × 64 kbit/s unrestricted
0 0 0 1 1 0 1 0 13 × 64 kbit/s unrestricted
0 0 0 1 1 0 1 1 14 × 64 kbit/s unrestricted
0 0 0 1 1 1 0 0 15 × 64 kbit/s unrestricted
0 0 0 1 1 1 0 1 16 × 64 kbit/s unrestricted
0 0 0 1 1 1 1 0 17 × 64 kbit/s unrestricted
0 0 0 1 1 1 1 1 18 × 64 kbit/s unrestricted
0 0 1 0 0 0 0 0 19 × 64 kbit/s unrestricted | + +| PropertyID | Property tag | Type | Value | +|------------|--------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | 0 0 1 0 0 0 0 1 20 × 64 kbit/s unrestricted
0 0 1 0 0 0 1 0 21 × 64 kbit/s unrestricted
0 0 1 0 0 0 1 1 22 × 64 kbit/s unrestricted
0 0 1 0 0 1 0 0 23 × 64 kbit/s unrestricted
0 0 1 0 0 1 0 1 spare | +| | | | 0 0 1 0 0 1 1 0 25 × 64 kbit/s unrestricted
0 0 1 0 0 1 1 1 26 × 64 kbit/s unrestricted
0 0 1 0 1 0 0 0 27 × 64 kbit/s unrestricted
0 0 1 0 1 0 0 1 28 × 64 kbit/s unrestricted
0 0 1 0 1 0 1 0 29 × 64 kbit/s unrestricted
0 0 1 0 1 0 1 1
through spare
1 1 1 1 1 1 1 1
[ITU-T Q.763] | +| TMRSP | 9002 | 1 octet | Transmission Medium Requirement Subrate
0 unspecified
1 8 kbit/s
2 16 kbit/s
3 32 kbit/s | +| Contcheck | 9003 | Boolean | Continuity Check
0 continuity check not required on this circuit
1 continuity check required on this circuit
[ITU-T Q.763] | +| ITC | 9004 | 5 bits | Information Transfer Capability
Bits
5 4 3 2 1
0 0 0 0 0 Speech
0 1 0 0 0 Unrestricted digital information
0 1 0 0 1 Restricted digital information
1 0 0 0 0 3.1 kHz audio
1 0 0 0 1 Unrestricted digital information
with tones/announcements
1 1 0 0 0 Video
All other values are reserved.
[ITU-T Q.763] | +| TransMode | 9005 | 2 bits | Transfer Mode
Bits
2 1
0 0 Circuit mode
1 0 Packet mode
[ITU-T Q.931] | + +| PropertyID | Property tag | Type | Value | +|-------------|--------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TransRate | 9006 | 5 bits | Transfer Rate
Bits
5 4 3 2 1
0 0 0 0 0 This code shall be used for packet mode calls
1 0 0 0 0 64 kbit/s
1 0 0 0 1 2 × 64 kbit/s
1 0 0 1 1 384 kbit/s
1 0 1 0 1 1536 kbit/s
1 0 1 1 1 1920 kbit/s
1 1 0 0 0 Multirate (64 kbit/s base rate)
[ITU-T Q.931] | +| MULT | 9007 | 7 bits | Rate Multiplier
Any value from 2 to n (maximum number of B-channels)
[ITU-T Q.931] | +| layer1prot | 9008 | 5 bits | User Information Layer 1 Protocol
Bits
5 4 3 2 1
0 0 0 0 1 ITU-T standardized rate adaption V.110 and X.30.
0 0 0 1 0 Rec. ITU-T G.711 µ-law
0 0 0 1 1 Rec. ITU-T G.711 A-law
0 0 1 0 0 Rec. ITU-T G.726 32 kbit/s ADPCM and Rec. ITU-T I.460
0 0 1 0 1 Recs ITU-T H.221 and H.242
0 0 1 1 0 Recs ITU-T H.223 and H.245
0 0 1 1 1 Non-ITU-T standardized rate adaption.
0 1 0 0 0 ITU-T standardized rate adaption V.120.
0 1 0 0 1 ITU-T standardized rate adaption X.31 HDLC flag stuffing
All other values are reserved.
[ITU-T Q.931] | +| syncasync | 9009 | Boolean | Synchronous/Asynchronous
0 Synchronous data
1 Asynchronous data
[ITU-T Q.931] | +| negotiation | 900A | Boolean | Negotiation
0 In-band negotiation possible
1 In-band negotiation not possible
[ITU-T Q.931] | + +| PropertyID | Property tag | Type | Value | +|------------|--------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Userrate | 900B | 5 bits | User Rate
Bits
5 4 3 2 1
0 0 0 0 0 Rate is indicated by E-bits specified in Rec. ITU-T I.460 or may be negotiated in-band
0 0 0 0 1 0.6 kbit/s Recs ITU-T V.6 and X.1
0 0 0 1 0 1.2 kbit/s Rec. ITU-T V.6
0 0 0 1 1 2.4 kbit/s Recs ITU-T V.6 and X.1
0 0 1 0 0 3.6 kbit/s Rec. ITU-T V.6
0 0 1 0 1 4.8 kbit/s Recs ITU-T V.6 and X.1
0 0 1 1 0 7.2 kbit/s Rec. ITU-T V.6
0 0 1 1 1 8 kbit/s Rec. ITU-T I.460
0 1 0 0 0 9.6 kbit/s Recs ITU-T V.6 and X.1
0 1 0 0 1 14.4 kbit/s Rec. ITU-T V.6
0 1 0 1 0 16 kbit/s Rec. ITU-T I.460
0 1 0 1 1 19.2 kbit/s Rec. ITU-T V.6
0 1 1 0 0 32 kbit/s Rec. ITU-T I.460
0 1 1 0 1 38.4 kbit/s Rec. ITU-T V.110
0 1 1 1 0 48 kbit/s Recs ITU-T V.6 and X.1
0 1 1 1 1 56 kbit/s Rec. ITU-T V.6
1 0 0 1 0 57.6 kbit/s Rec. ITU-T V.14 extended
1 0 0 1 1 28.8 kbit/s Rec. ITU-T V.110
1 0 1 0 0 24 kbit/s Rec. ITU-T V.110
1 0 1 0 1 0.1345 kbit/s Rec. ITU-T X.1
1 0 1 1 0 0.100 kbit/s Rec. ITU-T X.1
1 0 1 1 1 0.075/1.2 kbit/s Recs ITU-T V.6 and X.1
1 1 0 0 0 1.2/0.075 kbit/s Recs ITU-T V.6 and X.1
1 1 0 0 1 0.050 kbit/s Recs ITU-T V.6 and X.1
1 1 0 1 0 0.075 kbit/s Recs ITU-T V.6 and X.1
1 1 0 1 1 0.110 kbit/s Recs ITU-T V.6 and X.1
1 1 1 0 0 0.150 kbit/s Recs ITU-T V.6 and X.1
1 1 1 0 1 0.200 kbit/s Recs ITU-T V.6 and X.1
1 1 1 1 0 0.300 kbit/s Recs ITU-T V.6 and X.1
1 1 1 1 1 12 kbit/s Rec. ITU-T V.6
All other values are reserved.
[ITU-T Q.931] | + +| PropertyID | Property tag | Type | Value | +|--------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| INTRATE | 900C | 2 bits | Intermediate Rate
Bits
2 1
0 0 Not used
0 1 8 kbit/s
1 0 16 kbit/s
1 1 32 kbit/s
[ITU-T Q.931] | +| nictx | 900D | Boolean | Network Independent Clock (NIC) on transmission
0 Not required to send data with network independent clock
1 Required to send data with network independent clock
[ITU-T Q.931] | +| nicrx | 900E | Boolean | Network independent clock (NIC) on reception
0 Cannot accept data with network independent clock
(i.e., sender does not support this optional procedure)
1 Can accept data with network independent clock
(i.e., sender does support this optional procedure)
[ITU-T Q.931] | +| flowconttx | 900F | Boolean | Flow Control on transmission (Tx)
0 Not required to send data with flow control mechanism
1 Required to send data with flow control mechanism
[ITU-T Q.931] | +| flowcontrx | 9010 | Boolean | Flow control on reception (Rx)
0 Cannot accept data with flow control mechanism
(i.e., sender does not support this optional procedure)
1 Can accept data with flow control mechanism (i.e., sender does support this optional procedure)
ITU-T Q.931] | +| rateadapthdr | 9011 | Boolean | Rate adaption header/no header
0 Rate adaption header not included
1 Rate adaption header included
[ITU-T Q.931] | + +| PropertyID | Property tag | Type | Value | +|------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| multiframe | 9012 | Boolean | Multiple frame establishment support in data link
0 Multiple frame establishment not supported. Only UI frames allowed
1 Multiple frame establishment supported [ITU-T Q.931] | +| OPMODE | 9013 | Boolean | Mode of operation
0 Bit transparent mode of operation
1 Protocol sensitive mode of operation [ITU-T Q.931] | +| llidnegot | 9014 | Boolean | Logical link identifier negotiation
0 Default, LLI = 256 only
1 Full protocol negotiation [ITU-T Q.931] | +| assign | 9015 | Boolean | Assignor/assignee
0 Message originator is "default assignee"
1 Message originator is "assignor only" [ITU-T Q.931] | +| inbandneg | 9016 | Boolean | In-band/out-band negotiation
0 Negotiation is done with USER INFORMATION messages on a temporary signalling connection
1 Negotiation is done in-band using logical link zero [ITU-T Q.931] | +| stopbits | 9017 | 2 bits | Number of stop bits
Bits
2 1
0 0 Not used
0 1 1 bit
1 0 1.5 bits
1 1 2 bits [ITU-T Q.931] | +| databits | 9018 | 2 bits | Number of data bits excluding parity bit if present
Bits
2 1
0 0 Not used
0 1 5 bits
1 0 7 bits
1 1 8 bits [ITU-T Q.931] | + +| PropertyID | Property tag | Type | Value | +|------------|--------------|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| parity | 9019 | 3 bits | Parity information
Bits
3 2 1
0 0 0 Odd
0 1 0 Even
0 1 1 None
1 0 0 Forced to 0
1 0 1 Forced to 1
All other values are reserved.
[ITU-T Q.931] | +| duplexmode | 901A | Boolean | Mode duplex
0 Half duplex
1 Full duplex
[ITU-T Q.931] | +| modem | 901B | 6 bits | Modem Type
Bits
6 5 4 3 2 1
0 0 0 0 0 0
through National use
0 0 0 1 0 1
0 1 0 0 0 1 Rec. ITU-T V.21
0 1 0 0 1 0 Rec. ITU-T V.22
0 1 0 0 1 1 Rec. ITU-T V.22 bis
0 1 0 1 0 0 Rec. ITU-T V.23
0 1 0 1 0 1 Rec. ITU-T V.26
0 1 1 0 0 1 Rec. ITU-T V.26 bis
0 1 0 1 1 1 Rec. ITU-T V.26 ter
0 1 1 0 0 0 Rec. ITU-T V.27
0 1 1 0 0 1 Rec. ITU-T V.27 bis
0 1 1 0 1 0 Rec. ITU-T V.27 ter
0 1 1 0 1 1 Rec. ITU-T V.29
0 1 1 1 0 1 Rec. ITU-T V.32
0 1 1 1 1 0 Rec. ITU-T V.34
1 0 0 0 0 0
through National use
1 0 1 1 1 1
1 1 0 0 0 0
through User specified
1 1 1 1 1 1
[ITU-T Q.931] | +| layer2prot | 901C | 5 bits | User information layer 2 protocol
Bits
5 4 3 2 1
0 0 0 1 0 Rec. ITU-T Q.921/L.441
0 0 1 1 0 Rec. ITU-T X.25, link layer
0 1 1 0 0 LAN logical link control
(ISO/IEC 8802-2)
All other values are reserved.
[ITU-T Q.931] | + +| PropertyID | Property tag | Type | Value | +|---------------|--------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| layer3prot | 901D | 5 bits | User information layer 3 protocol
Bits
5 4 3 2 1
0 0 0 1 0 Rec. ITU-T Q.931
0 0 1 1 0 Rec. ITU-T X.25, packet layer
0 1 0 1 1 ISO/IEC TR 9577 (Protocol identification in the network layer)
All other values are reserved.
[ITU-T Q.931] | +| addlayer3prot | 901E | Octet | Additional User Information layer 3 protocol
Bits      Bits
4 3 2 1 4 3 2 1
1 1 0 0    1 1 0 0 Internet Protocol
(RFC 791)
(ISO/IEC TR 9577)
1 1 0 0    1 1 1 1 Point-to-point Protocol
(RFC 1661)
[ITU-T Q.931] | +| DialledN | 901F | 30 octets | Dialled Number | +| DiallingN | 9020 | 30 octets | Dialling Number | +| ECHOCI | 9021 | | Not Used. See E.13 for an example of possible Echo Control Properties. | +| NCI | 9022 | 1 octet | Nature of Connection Indicators
Bits
2 1 Satellite Indicator
0 0 no satellite circuit in the connection
0 1 one satellite circuit in the connection
1 0 two satellite circuits in the connection
1 1 spare
Bits
4 3 Continuity check indicator
0 0 continuity check not required
0 1 continuity check required on this circuit
1 0 continuity check performed on a previous circuit
1 1 spare
Bit
5 Echo control device indicator
0 outgoing echo control device not included
1 outgoing echo control device included
Bits
8 7 6 Spare
[ITU-T Q.763] | +| USI | 9023 | Octet string | User Service Information
Clause 3.57/[ITU-T Q.763] | + +## C.10 AAL 5 properties + +| PropertyID | Property tag | Type | Value | +|------------|-------------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| FMSDU | A001 | 32-bit integer | Forward Maximum CPCS-SDU Size:
Maximum CPCS-SDU size sent in the direction from the calling user to the called user.
[ITU-T Q.2931] | +| BMSDU | A002 | 32-bit integer | Backwards Maximum CPCS-SDU Size:
Maximum CPCS-SDU size sent in the direction from the called user to the calling user.
[ITU-T Q.2931] | +| SSCS | See table in clause C.7 | See table in clause C.7 | See table in clause C.7
Additional values:
VPI/VCI | + +## C.11 SDP equivalents + +The SDP equivalents are subject to the SDP exceptions outlined in clause 7.1.8 for the text encoding of the protocol. For example, the CHOOSE wildcard is allowed to be used in the MGC to MG direction irrespective of the encoding (binary or text) of the protocol. + +| PropertyID | Property tag | Type | Value | +|------------|--------------|--------|-------------------------------------------------| +| SDP_V | B001 | String | Protocol Version
[IETF RFC 2327] | +| SDP_O | B002 | String | Owner/creator and session ID
[IETF RFC 2327] | +| SDP_S | B003 | String | Session name
[IETF RFC 2327] | +| SDP_I | B004 | String | Session identifier
[IETF RFC 2327] | +| SDP_U | B005 | String | URI of descriptor
[IETF RFC 2327] | +| SDC_E | B006 | String | email address
[IETF RFC 2327] | +| SDP_P | B007 | String | phone number
[IETF RFC 2327] | +| SDP_C | B008 | String | Connection information
[IETF RFC 2327] | +| SDP_B | B009 | String | Bandwidth Information
[IETF RFC 2327] | +| SDP_Z | B00A | String | Time zone adjustment
[IETF RFC 2327] | +| SDP_K | B00B | String | Encryption Key
[IETF RFC 2327] | + +| PropertyID | Property tag | Type | Value | +|------------|--------------|--------|-----------------------------------------------------------| +| SDP_A | B00C | String | Zero or more session attributes
[IETF RFC 2327] | +| SDP_T | B00D | String | Active Session Time
[IETF RFC 2327] | +| SDP_R | B00E | String | Zero or more repeat times
[IETF RFC 2327] | +| SDP_M | B00F | String | Media type, port, transport and format
[IETF RFC 2327] | + +## C.12 H.245 + +| PropertyID | Property tag | Type | Value | +|------------|--------------|--------------|-----------------------------------------------------------------------------------| +| OLC | C001 | Octet string | The value of ITU-T H.245
OpenLogicalChannel structure.
[ITU-T H.245] | +| OLCack | C002 | Octet string | The value of ITU-T H.245
OpenLogicalChannelAck structure.
[ITU-T H.245] | +| OLCcnf | C003 | Octet string | The value of ITU-T H.245
OpenLogicalChannelConfirm structure.
[ITU-T H.245] | +| OLCrej | C004 | Octet string | The value of ITU-T H.245
OpenLogicalChannelReject structure.
[ITU-T H.245] | +| CLC | C005 | Octet string | The value of ITU-T H.245
CloseLogicalChannel structure.
[ITU-T H.245] | +| CLCack | C006 | Octet string | The value of ITU-T H.245
CloseLogicalChannelAck structure.
[ITU-T H.245] | +| LCN | C007 | Integer | The value of ITU-T H.245 Local Channel
Number 0-65535.
[ITU-T H.245] | + +# Annex D + +## Transport over IP + +(This annex forms an integral part of this Recommendation.) + +## D.1 Transport over IP/UDP using Application Level Framing (ALF) + +Protocol messages defined in this Recommendation may be transmitted over UDP. When no port is provided by the peer (see clause 7.2.8), commands should be sent to the default port number: 2944 for text-encoded operation, or 2945 for binary-encoded operation. Responses must be sent to the address and port from which the corresponding commands were sent. + +ALF is a set of techniques that allows an application, as opposed to a stack, to affect how messages are sent to the other side. A typical ALF technique is to allow an application to change the order of messages sent when there is a queue after it has queued them. There is no formal specification for ALF. The procedures in clause D.1 contain a minimum suggested set of ALF behaviours. + +Implementors using IP/UDP with ALF should be aware of the restrictions of the MTU on the maximum message size. + +### D.1.1 Providing at-most-once functionality + +Messages carried over UDP may be subject to losses. In the absence of a timely response, commands are repeated. Most commands are not idempotent. The state of the MG would become unpredictable if, for example, Add Commands were executed several times. The transmission procedures shall thus provide an "At-Most-Once" functionality. + +Peer protocol entities are expected to keep in memory a list of the responses that they sent to recent transactions and a list of the transactions that are currently outstanding. The TransactionID of each incoming message is compared to the TransactionIDs of the recent responses sent to the same MID. If a match is found, the entity does not execute the transaction, but simply repeats the response. If no match is found, the message will be compared to the list of currently outstanding transactions. If a match is found in that list, indicating a duplicate transaction, the entity does not execute the transaction (see clause D.1.4 for procedures on sending TransactionPending). + +The procedure uses a long timer value, noted LONG-TIMER in the following. The timer should be set larger than the maximum duration of a transaction, which should take into account the maximum number of repetitions, the maximum value of the repetition timer and the maximum propagation delay of a packet in the network. A suggested value is 30 seconds. + +The copy of the responses may be destroyed either LONG-TIMER seconds after the response is issued, or when the entity receives a confirmation that the response has been received, through the "Response Acknowledgement parameter". For transactions that are acknowledged through this parameter, the entity shall keep a copy of the TransactionID for LONG-TIMER seconds after the response is issued, in order to detect and ignore duplicate copies of the transaction request that could be produced by the network. + +### D.1.2 Transaction identifiers and three-way handshake + +#### D.1.2.1 Transaction identifiers + +TransactionIDs are 32-bit integer numbers. A Media Gateway Controller may decide to use a specific number space for each of the MGs that they manage, or to use the same number space for all MGs that belong to some arbitrary group. MGCs may decide to share the load of managing a large MG between several independent processes. These processes will share the same transaction number space. There are multiple possible implementations of this sharing, such as having a centralized allocation of TransactionIDs, or pre-allocating non-overlapping ranges of identifiers to + +different processes. The implementations shall guarantee that unique TransactionIDs are allocated to all transactions that originate from a logical MGC (identical MID). MGs can simply detect duplicate transactions by looking at the TransactionID and MID only. + +#### D.1.2.2 Three-way handshake + +The TransactionResponseAcknowledgement parameter can be found in any message. It carries a set of "confirmed TransactionID ranges". Entities may choose to delete the copies of the responses to transactions whose ID is included in "confirmed TransactionID ranges" received in the transaction response messages. They should silently discard further commands when the TransactionID falls within these ranges. + +The "confirmed TransactionID ranges" values shall not be used if more than LONG-TIMER seconds have elapsed since the MG issued its last response to that MGC, or when an MG resumes operation. In this situation, transactions should be accepted and processed, without any test on the TransactionID. + +Messages that carry the "TransactionResponseAcknowledgement" parameter may be transmitted in any order. The entity shall retain the "confirmed TransactionID ranges" received for LONG-TIMER seconds. + +In the binary encoding, if only the `firstAck` is present in a response acknowledgement (see clause A.2), only one transaction is acknowledged. If both `firstAck` and `lastAck` are present, then the range of transactions from `firstAck` to `lastAck` is acknowledged. In the text encoding, a horizontal dash is used to indicate a range of transactions being acknowledged (see clause B.2). + +### D.1.3 Computing retransmission timers + +It is the responsibility of the requesting entity to provide suitable timeouts for all outstanding transactions, and to retry transactions when timeouts have been exceeded. Furthermore, when repeated transactions fail to be acknowledged, it is the responsibility of the requesting entity to seek redundant services and/or clear existing or pending connections. + +The specification purposely avoids specifying any value for the retransmission timers. These values are typically network-dependent. The retransmission timers should normally estimate the timer value by measuring the time spent between the sending of a command and the return of a response. Implementations shall ensure that the algorithm used to calculate retransmission timing performs an exponentially increasing backoff of the retransmission timeout for each retransmission or repetition after the first one. + +NOTE – One possibility is to use the algorithm implemented in TCP-IP, which uses two variables: + +- The average acknowledgement delay (AAD), estimated through an exponentially smoothed average of the observed delays. +- The average deviation (ADEV), estimated through an exponentially smoothed average of the absolute value of the difference between the observed delay and the current average. The retransmission timer, in TCP, is set to the sum of the average delay plus N times the average deviation. The maximum value of the timer should however be bounded for the protocol defined in this Recommendation, in order to guarantee that no repeated packet would be received by the gateways after LONG-TIMER seconds. A suggested maximum value is 4 seconds. + +After any retransmission, the entity should do the following: + +- It should double the estimated value of the average delay, AAD. +- It should compute a random value, uniformly distributed between 0.5 AAD and AAD. +- It should set the retransmission timer to the sum of that random value and N times the average deviation. + +This procedure has two effects. Because it includes an exponentially increasing component, it will automatically slow down the stream of messages in case of congestion. Because it includes a random component, it will break the potential synchronization between notifications triggered by the same external event. + +### **D.1.4 Provisional responses** + +Executing some transactions may require a long time. Long execution times may interact with the timer-based retransmission procedure. This may result either in an inordinate number of retransmissions, or in timer values that become too long to be efficient. Entities that can predict that a transaction will require a long execution time may send a provisional response, "TransactionPending". They should send this response if they receive a repetition of a transaction that is still being executed. + +Entities that receive a TransactionPending shall switch to a different repetition timer for repeating requests. Upon receipt of a final response following receipt of provisional responses, an immediate confirmation shall be sent, and normal repetition timers shall be used thereafter. An entity that sends a provisional response shall include the immAckRequired field in the ensuing final response, indicating that an immediate confirmation is expected. Receipt of a TransactionPending after receipt of a reply shall be ignored. + +### **D.1.5 Repeating requests, responses and acknowledgements** + +The protocol is organized as a set of transactions, each of which is composed of a request and a response, commonly referred to as an acknowledgement. The protocol messages, being carried over UDP, may be subject to losses. In the absence of a timely response, transactions are repeated. Entities are expected to keep in memory a list of the responses that they sent to recent transactions, i.e., a list of all the responses they sent over the last LONG-TIMER seconds, and a list of the transactions that are currently being executed. + +The repetition mechanism is used to guard against three types of possible errors: + +- transmission errors, when, for example, a packet is lost due to noise on a line, or congestion in a queue; +- component failure, when, for example, an interface to an entity becomes unavailable; +- entity failure, when, for example, an entire entity becomes unavailable. + +The entities should be able to derive from the past history an estimate of the packet loss rate due to transmission errors. In a properly configured system, this loss rate should be kept very low, typically less than 1%. If a Media Gateway Controller or a Media Gateway has to repeat a message more than a few times, it is legitimate to assume that something else than a transmission error is occurring. For example, given a loss rate of 1%, the probability that five consecutive transmission attempts fail is 1 in 100 billion, an event that should occur less than once every 10 days for a Media Gateway Controller that processes 1000 transactions per second. (Indeed, the number of repetitions that is considered excessive should be a function of the prevailing packet loss rate.) We should note that the "suspicion threshold", which we will call "Max1", is normally lower than the "disconnection threshold", which should be set to a larger value. + +A classic retransmission algorithm would simply count the number of successive repetitions, and conclude that the association is broken after retransmitting the packet an excessive number of times (typically between 7 and 11 times). In order to account for the possibility of an undetected or in-progress "failover", we modify the classic algorithm so that if the Media Gateway receives a valid ServiceChange message announcing a failover, it will start transmitting outstanding commands to that new MGC. Responses to commands are still transmitted to the source address of the command. + +In order to automatically adapt to network load, this Recommendation specifies exponentially increasing timers. If the initial timer is set to 200 milliseconds, the loss of a fifth retransmission will be detected after about 6 seconds. This is probably an acceptable waiting delay to detect a failover. The repetitions should continue after that delay not only in order to perhaps overcome a transient connectivity problem, but also in order to allow some more time for the execution of a failover (waiting a total delay of 30 seconds is probably acceptable). + +It is, however, important that the maximum delay of retransmissions be bounded. Prior to any retransmission, it should be checked that the time elapsed since the sending of the initial datagram is no greater than T-MAX. If more than T-MAX time has elapsed, the MG concludes that the MGC has failed, and that it begins its recovery process as described in clause 11.5. If the MG retries to connect to the current MGC, it shall use a ServiceChange with ServiceChangeMethod set to Disconnected so that the new MGC will be aware that the MG lost one or more transactions. The value T-MAX is related to the LONG-TIMER value: the LONG-TIMER value is obtained by adding to T-MAX the maximum propagation delay in the network. + +## **D.2 Using TCP** + +Protocol messages as defined in this Recommendation may be transmitted over TCP. When no port is specified by the other side (see clause 7.2.8) the commands should be sent to the default port. The defined protocol has messages as the unit of transfer, while TCP is a stream-oriented protocol. TPKT, according to [IETF RFC 1006], shall be used to delineate messages within the TCP stream. + +In a transaction-oriented protocol, there are still ways for transaction requests or responses to be lost. As such, it is recommended that entities using TCP transport implement application level timers for each request and each response, similar to those specified for application level framing over UDP. + +### **D.2.1 Providing the at-most-once functionality** + +Messages carried over TCP are not subject to transport losses, but loss of a transaction request or its reply may nonetheless be noted in real implementations. In the absence of a timely response, commands are repeated. Most commands are not idempotent. The state of the MG would become unpredictable if, for example, Add Commands were executed several times. + +To guard against such losses, it is recommended that entities follow the procedures in clause D.1.1. + +### **D.2.2 Transaction identifiers and three-way handshake** + +For the same reasons, it is possible that transaction replies may be lost even with a reliable delivery protocol such as TCP. It is recommended that entities follow the procedures in clause D.1.2.2. + +### **D.2.3 Computing retransmission timers** + +With reliable delivery, the incidence of loss of a transaction request or reply is expected to be very low. Therefore, only simple timer mechanisms are required. Exponential back-off algorithms should not be necessary, although they could be employed where, as in an MGC, the code to do so is already required since MGCs must implement ALF/UDP as well as TCP. + +### **D.2.4 Provisional responses** + +As with UDP, executing some transactions may require a long time. Entities that can predict that a transaction will require a long execution time may send a provisional response, "TransactionPending". They should send this response if they receive a repetition of a transaction that is still being executed. + +Entities that receive a TransactionPending shall switch to a longer repetition timer for that transaction. + +Entities shall retain transactions and replies until they are confirmed. The basic procedure of clause D.1.4 should be followed, but simple timer values should be sufficient. There is no need to send an immediate confirmation upon receipt of a final response. + +### **D.2.5 Ordering of commands** + +TCP provides ordered delivery of transactions. No special procedures are required. It should be noted that ALF/UDP allows the sending entity to modify its behaviour under congestion, and in particular, could reorder transactions when congestion is encountered. TCP could not achieve the same results. + +# Annex E + +## Basic packages + +(This annex forms an integral part of this Recommendation.) + +This annex contains definitions of some packages for use with this Recommendation. + +## E.1 Generic + +**Package name:** Generic +**Package ID:** g (0x0001) +**Description:** Generic package for commonly encountered items +**Version:** 2 +**Extends:** None +Version 2 of the Generic Package requires at least version 3 of the protocol. + +### E.1.1 Properties + +None. + +### E.1.2 Events + +#### E.1.2.1 Cause + +**Event name:** Cause +**Event ID:** cause (0x0001) +**Description:** Generic error event +**EventsDescriptor Parameters:** None +**ObservedEvents Descriptor Parameters:** + +##### General Cause + +**Parameter name:** General Cause +**Parameter ID:** Generalcause (0x0001) +**Description:** This parameter groups the failures into six groups, which the MGC may act upon. +**Type:** enumeration +**Optional:** No +**Possible values:** "NR" (0x0001): Normal Release +"UR" (0x0002): Unavailable Resources +"FT" (0x0003): Failure, Temporary +"FP" (0x0004): Failure, Permanent +"IW" (0x0005): Interworking Error +"UN" (0x0006): Unsupported +**Default:** None + +##### Failure Cause + +| | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Failure Cause | +| Parameter ID: | Failurecause (0x0002) | +| Description: | The Failure Cause is the value generated by the Released equipment, i.e., a released network connection. The concerned value is defined in the appropriate bearer control protocol. | +| Type: | OCTET STRING | +| Optional: | Yes | +| Possible values: | OCTET STRING | +| Default: | None | + +#### E.1.2.2 Signal Completion + +| | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Signal Completion | +| Event ID: | sc (0x0002) | +| Description: | Indicates the termination of a signal for which the NotifyCompletion parameter was set to enable reporting of a completion event. For further procedural description, see clauses 7.1.1, 7.1.11 and 7.2.7. | + +**EventsDescriptor Parameters:** None + +**ObservedEvents Descriptor Parameters:** + +##### Signal Identity + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Signal Identity | +| Parameter ID: | SigID (0x0001) | +| Description: | This parameter identifies the signal which has terminated. For a signal that is contained in a SignalList, the SignalListID parameter should also be returned indicating the appropriate list. | +| Type: | Binary:octet (string), Text:string | +| Optional: | No | +| Possible values: | a signal which has terminated. A signal shall be identified using the pkgdName syntax without wildcarding. | +| Default: | None | + +##### Termination Method + +| | | +|------------------------|-----------------------------------------------------| +| Parameter name: | Termination Method | +| Parameter ID: | Meth (0x0002) | +| Description: | Indicates the means by which the signal terminated. | +| Type: | Enumeration | +| Optional: | No | + +**Possible values:** "TO" (0x0001):Signal timed out or otherwise completed on its own +"EV" (0x0002): Interrupted by event +"SD" (0x0003): Halted by new Signals Descriptor +"NC" (0x0004): Not completed, other cause +"PI" (0x0005): First to penultimate iteration. For last iteration, use TO. + +**Default:** None + +##### **Signal List ID** + +**Parameter name:** Signal List ID + +**Parameter ID:** SLID (0x0003) + +**Description:** Indicates to which SignalList a signal belongs. The SignalListID is only returned in cases where the signal resides in a SignalList. + +**Type:** Integer + +**Optional:** Yes (only supported if signal lists are used) + +**Possible values:** 1-65535 + +**Default:** None + +##### **Request ID** + +**Parameter name:** Request ID + +**Parameter ID:** RID (0x0004) + +**Description:** Indicates to which NotifyCompletion request the SignalID is associated. + +**Type:** Integer + +**Optional:** Yes (only supported if signal lists are used) + +**Possible values:** 1-4294967295 + +**Default:** None + +### **E.1.3 Signals** + +None. + +### **E.1.4 Statistics** + +None. + +## **E.2 Base Root Package** + +**Package name:** Base Root Package + +**Package ID:** root (0x0002) + +**Description:** This package defines Gateway wide properties. + +**Version:** 2 + +**Extends:** None +Version 2 of the Base Root Package requires at least version 2 of the protocol. + +### E.2.1 Properties + +#### E.2.1.1 Maximum Number of Contexts + +**Property name:** MaxNrOfContexts +**Property ID:** maxNumberOfContexts (0x0001) +**Description:** The value of this property gives the maximum number of contexts that can exist at any time. The NULL Context is not included in this number. +The maximum number of contexts may be calculated by an MG in different ways, e.g., dependent on the number of connection models to be supported, dependent on applied stream, termination and/or context admission control functions, or specific, MG-internal QoS support mechanisms (e.g., best effort versus over-provisioning models), or other reasons. +The value of the property must be therefore interpreted as a best-case figure. Requests for additional contexts over and above this number may receive an error response. +**Type:** Double +**Possible values:** 1 and up +**Default:** Provisioned +**Defined in:** TerminationState +**Characteristics:** ReadOnly + +#### E.2.1.2 Maximum Terminations Per Context + +**Property name:** MaxTerminationsPerContext +**Property ID:** maxTerminationsPerContext (0x0002) +**Description:** The maximum number of allowed terminations in a context, see clause 6.1. This is not related to the capacity of the NULL Context. This is related to non-Root termination types (physical, ephemeral), including multiplexing terminations. +**Type:** Integer +**Possible values:** any positive integer +**Default:** Provisioned +**Defined in:** TerminationState +**Characteristics:** ReadOnly + +#### E.2.1.3 Normal MG Execution Time + +**Property name:** normalMGExecutionTime +**Property ID:** normalMGExecutionTime (0x0003) + +**Description:** Settable by the MGC to indicate the interval within which the MGC expects a response to any transaction from the MG (exclusive of network delay). + +**Type:** Integer + +**Possible values:** any positive integer; represents milliseconds + +**Default:** Provisioned + +**Defined in:** TerminationState + +**Characteristics:** Read/Write + +#### E.2.1.4 Normal MGC Execution Time + +**Property name:** normalMGCExecutionTime + +**Property ID:** normalMGCExecutionTime (0x0004) + +**Description:** Settable by the MGC to indicate the interval within which the MG should expect a response to any transaction from the MGC (exclusive of network delay). + +**Type:** Integer + +**Possible values:** any positive integer; represents milliseconds + +**Default:** Provisioned + +**Defined in:** TerminationState + +**Characteristics:** Read/Write + +#### E.2.1.5 MG Provisional Response Timer Value + +**Property name:** MGProvisionalResponseTimerValue + +**Property ID:** MGProvisionalResponseTimerValue (0x0005) + +**Description:** Indicates the time within which the MGC should expect a Pending Response from the MG if a transaction cannot be completed. Initially set to normalMGCExecutionTime plus network delay, but may be lowered. + +**Type:** Integer + +**Possible values:** any positive integer; represents milliseconds + +**Default:** Provisioned + +**Defined in:** TerminationState + +**Characteristics:** Read/Write + +#### E.2.1.6 MGC Provisional Response Timer Value + +**Property name:** MGCProvisionalResponseTimerValue + +**Property ID:** MGCProvisionalResponseTimerValue (0x0006) + +**Description:** Indicates the time within which the MG should expect a Pending Response from the MGC if a transaction cannot be completed. Initially set to normalMGCExecutionTime plus network delay, but may be lowered. + +**Type:** Integer + +**Possible values:** any positive integer; represents milliseconds +**Default:** Provisioned +**Defined in:** TerminationState +**Characteristics:** Read/Write + +#### **E.2.1.7 MGC Originated Pending Limit** + +**Property name:** MGCOriGINatedPendingLimit +**Property ID:** MGCOriGINatedPendingLimit (0x0007) +**Description:** Indicates the number of TransactionPendings that can be received from the MGC. Once this limit is exceeded, the MGC should issue a TransactionReply with Error 506 ("Number of TransactionPendings Exceeded"); otherwise, the MG can assume the transaction to be in error. +**Type:** Integer +**Possible values:** any positive integer +**Default:** Provisioned +**Defined in:** TerminationState +**Characteristics:** Read/Write + +#### **E.2.1.8 MG Originated Pending Limit** + +**Property name:** MGOriginatedPendingLimit +**Property ID:** MGOriginatedPendingLimit (0x0008) +**Description:** Indicates the number of TransactionPendings that can be received from the MG. Once this limit is exceeded, the MG should issue a TransactionReply with Error 506 ("Number of TransactionPendings Exceeded"); otherwise, the MGC can assume the transaction to be in error. +**Type:** Integer +**Possible values:** any positive integer +**Default:** Provisioned +**Defined in:** TerminationState +**Characteristics:** Read/Write + +### **E.2.2 Events** + +None. + +### **E.2.3 Signals** + +None. + +### **E.2.4 Statistics** + +None. + +### **E.2.5 Procedures** + +None. + +## E.3 Tone Generator Package + +| | | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | Tone Generator Package | +| Package ID: | tonegen (0x0003) | +| Description: | This package defines signals to generate audio tones. This package does not specify parameter values. It is intended to be extendable. Generally, tones are defined as an individual signal with a parameter, ind, representing "interdigit" time delay, and a tone ID to be used with playtone. A tone ID should be kept consistent with any tone generation for the same tone. MGs are expected to be provisioned with the characteristics of appropriate tones for the country in which the MG is located. | +| Version: | 2 | +| Designed to be extended only: | Yes | +| Extends: | None | + +### E.3.1 Properties + +None. + +### E.3.2 Events + +None. + +### E.3.3 Signals + +#### E.3.3.1 Play Tone + +| | | +|---------------------|----------------------------------------| +| Signal name: | Play Tone | +| Signal ID: | pt (0x0001) | +| Description: | Plays audio tone over an audio channel | +| Signal Type: | Brief | +| Duration: | Provisioned | + +##### Additional parameters: + +##### Tone ID list + +| | | +|-------------------------|-------------------------------------------------| +| Parameter name: | Tone ID List | +| Parameter ID: | tl (0x0001) | +| Description: | List of tones to be played in sequence. | +| Type: | Sublist of Enumeration | +| Optional: | No | +| Possible values: | The sublist shall contain one or more tone IDs. | +| Default: | None | + +##### Inter-signal duration + +| | | +|------------------------|-------------------------------------------------------| +| Parameter name: | Inter-signal duration | +| Parameter ID: | ind (0x0002) | +| Description: | Timeout between two consecutive tones in milliseconds | + +**Type:** Integer +**Optional:** Yes +**Possible values:** Any integer greater than or equal to 0 +**Default:** Provisioned + +##### **Tone Direction** + +**Parameter name:** Tone Direction +**Parameter ID:** btd (0x0003) +**Description:** Direction the tone should progress from the termination. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "EXT" (0x0001) External +                               "INT" (0x0002) Internal +                               "BOTH" (0x0003) Both +**Default:** External + +### **E.3.4 Statistics** + +None. + +### **E.3.5 Procedures** + +No tone IDs are specified in this package. Packages that extend this package can add possible values for tone ID as well as adding individual tone signals. + +## **E.4 Tone Detection Package** + +**Package name:** Tone Detection Package +**Package ID:** tonedet (0x0004) +**Description:** This package defines events for audio tone detection. Tones are selected by name (tone ID). MGs are expected to be provisioned with the characteristics of appropriate tones for the country in which the MG is located. + + This package does not specify parameter values. It is intended to be extendable. +**Version:** 1 +**Designed to be extended only:** Yes +**Extends:** None + +### **E.4.1 Properties** + +None. + +### **E.4.2 Events** + +#### **E.4.2.1 Start Tone Detected** + +**Event name:** Start tone detected +**Event ID:** std (0x0001) +**Description:** Detects the start of a tone. The characteristics of positive tone detection are implementation dependent. + +###### **EventsDescriptor Parameters:** + +##### **Tone ID List** + +**Parameter name:** Tone ID List +**Parameter ID:** tl (0x0001) +**Type:** Sublist of Enumeration +**Optional:** No +**Possible values:** The only tone ID defined in this package is "wild card" which is "\*" in text encoding and 0x0000 in binary. Extensions to this package would add possible values for tone ID. If tl is "wildcard", any tone ID is detected. +**Default:** None + +##### **ObservedEventsDescriptor Parameters:** + +###### **Tone ID** + +**Parameter name:** Tone ID +**Parameter ID:** tid (0x0003) +**Description:** The tone ID of the detected tone. +**Type:** Enumeration +**Optional:** No +**Possible values:** "wildcard" as defined above is the only value defined in this package. Extensions to this package would add additional possible values for tone ID. +**Default:** None + +#### **E.4.2.2 End Tone Detected** + +**Event name:** End tone detected +**Event ID:** etd (0x0002) +**Description:** Detects the end of a tone. + +##### **EventsDescriptor Parameters:** + +##### **Tone ID List** + +**Parameter name:** Tone ID List + +**Parameter ID:** tl (0x0001) +**Description:** A list of tone IDs to be detected. +**Type:** Sublist of enumeration +**Optional:** No +**Possible values:** The only tone id defined in this package is "wild card" which is "\*" in text encoding and 0x0000 in binary. Extensions to this package would add possible values for tone ID. If property tl is set to "wild card", any tone id is detected. +**Default:** None + +##### **ObservedEventsDescriptor Parameters:** + +##### **Tone ID** + +**Parameter name:** Tone ID +**Parameter ID:** tid (0x0003) +**Description:** The tone ID of the detected tone. +**Type:** Enumeration +**Optional:** No +**Possible values:** "wildcard" as defined above is the only value defined in this package. Extensions to this package would add possible values for tone ID. +**Default:** None + +##### **Duration** + +**Parameter name:** Duration +**Parameter ID:** dur (0x0002) +**Description:** This parameter contains the duration of the tone from first detection until it stopped. +**Type:** Integer +**Optional:** Yes +**Possible values:** Any positive integer in milliseconds +**Default:** None + +#### **E.4.2.3 Long Tone Detected** + +**Event name:** Long Tone Detected +**Event ID:** ltd (0x0003) +**Description:** Detects that a tone has been playing for at least a certain amount of time + +##### **EventsDescriptor Parameters:** + +##### **Tone ID List** + +**Parameter name:** Tone ID List + +**Parameter ID:** tl (0x0001) +**Description:** A list of tone IDs to be detected. +**Type:** Sublist of Enumeration +**Optional:** No +**Possible values:** "wildcard" as defined above is the only value defined in this package. Extensions to this package would add possible values for tone ID. +**Default:** None + +##### **Duration** + +**Parameter name:** Duration +**Parameter ID:** dur (0x0002) +**Description:** The duration to test against. +**Type:** Integer +**Optional:** Yes +**Possible values:** any positive integer, expressed in milliseconds +**Default:** Provisioned + +##### **ObservedEventsDescriptor Parameters:** + +##### **Tone ID** + +**Parameter name:** Tone ID +**Parameter ID:** tid (0x0003) +**Description:** The tone ID of the detected tone. +**Type:** Enumeration +**Optional:** No +**Possible values:** No possible values are specified in this package. Extensions to this package would add possible values for tone ID. +**Default:** None + +### **E.4.3 Signals** + +None. + +### **E.4.4 Statistics** + +None. + +### **E.4.5 Procedures** + +None. + +## **E.5 Basic DTMF Generator Package** + +**Package name:** Basic DTMF Generator Package +**Package ID:** dg (0x0005) +**Description:** This package defines the basic DTMF tones as signals and extends the allowed values of parameter tl of playtone in tonegen. +**Version:** 2 +**Extends:** tonegen version 2 + +### **E.5.1 Properties** + +None. + +### **E.5.2 Events** + +None. + +### **E.5.3 Signals** + +#### **E.5.3.1 DTMF Character 0** + +**Signal name:** DTMF Character 0 +**Signal ID:** d0 (0x0010) +**Description:** Generate DTMF 0 tone. The physical characteristic of DTMF 0 is defined in the gateway. +**Signal Type:** Brief +**Duration:** Provisioned +**Additional parameters:** + +##### **Tone Direction** + +**Parameter name:** Tone Direction +**Parameter ID:** btd (0x0001) +**Description:** Direction the tone should progress from the termination. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "EXT" (0x0001) External +"INT" (0x0002) Internal +"BOTH" (0x0003) Both +**Default:** External + +**Additional values:** d0 (0x0010) is defined as a tone ID for playtone. + +The other DTMF characters are specified in exactly the same way. A table with all signal names and SignalIDs is included. Note that each DTMF character is defined as both a signal and a tone ID, thus extending the basic tone generation package. Also note that DTMF SignalIDs are different from the names used in a DigitMap. + +| Signal name | SignalID/Tone ID | +|------------------|------------------| +| DTMF character 0 | d0 (0x0010) | +| DTMF character 1 | d1 (0x0011) | +| DTMF character 2 | d2 (0x0012) | +| DTMF character 3 | d3 (0x0013) | +| DTMF character 4 | d4 (0x0014) | +| DTMF character 5 | d5 (0x0015) | +| DTMF character 6 | d6 (0x0016) | +| DTMF character 7 | d7 (0x0017) | +| DTMF character 8 | d8 (0x0018) | +| DTMF character 9 | d9 (0x0019) | +| DTMF character * | ds (0x0020) | +| DTMF character # | do (0x0021) | +| DTMF character A | da (0x001a) | +| DTMF character B | db (0x001b) | +| DTMF character C | dc (0x001c) | +| DTMF character D | dd (0x001d) | + +### E.5.4 Statistics + +None. + +### E.5.5 Procedures + +None. + +## E.6 DTMF Detection Package + +**Package name:** DTMF Detection Package + +**Package ID:** dd (0x0006) + +**Description:** This package defines the basic DTMF tones detection. This package extends the possible values of tone ID in the Start Tone Detected, End Tone Detected and Long Tone Detected Events. + +Additional tone ID values are all tone IDs described in package dg (Basic DTMF Generator Package). + +The following table maps DTMF events to DigitMap symbols as described in clause 7.1.14. + +| DTMF | Event Symbol | +|------|--------------| +| d0 | "0" | +| d1 | "1" | +| d2 | "2" | +| d3 | "3" | +| d4 | "4" | +| d5 | "5" | +| d6 | "6" | +| d7 | "7" | +| d8 | "8" | +| d9 | "9" | +| da | "A" or "a" | +| db | "B" or "b" | +| dc | "C" or "c" | +| dd | "D" or "d" | +| ds | "E" or "e" | +| do | "F" or "f" | + +**Version:** 2 + +**Extends:** tonedet version 1 + +### E.6.1 Properties + +None. + +### E.6.2 Events + +#### E.6.2.1 DTMF Digits + +**Event name:** DTMF Digits + +**Event ID:** EventIDs are defined with the same names as the SignalIDs defined in the table found in clause E.5.3. + +**Description:** Generated when the MG detects a digit. + +**EventsDescriptor +Parameters:** None + +**ObservedEvents +Descriptor +Parameters:** None + +#### E.6.2.2 DigitMap Completion Event + +**Event name:** DigitMap Completion Event + +**Event ID:** ce (0x0004) + +**Description:** Generated when a DigitMap completes as described in clause 7.1.14. + +###### **EventsDescriptor** + +###### **Parameters:** + +###### **Unsuccessful Match Reporting** + +**Parameter name:** Unsuccessful Match Reporting +**Parameter ID:** umr (0x0001) +**Description:** The MGC may use this parameter to control whether the DigitMap Completion Event is generated in the event of an unsuccessful DigitMap match (i.e., match with method "Partial match" or "Full Match"). +**Type:** Boolean +**Optional:** Yes +**Possible values:** *On* Generate DigitMap Completion Event on unsuccessful match. +*Off* Do not generate a DigitMap Completion Event on an unsuccessful match. +**Default:** *On* + +##### **ObservedEventsDescriptor Parameters:** + +###### **DigitString** + +**Parameter name:** DigitString +**Parameter ID:** ds (0x0001) +**Description:** the portion of the current dial string as described in clause 7.1.14 which matched part or all of an alternative event sequence specified in the DigitMap. +**Type:** String of DigitMap symbols (possibly empty) returned as a quotedString +**Optional:** No +**Possible values:** a sequence of the characters "0" through "9", "A" through "F", and the long duration modifier "Z". +**Default:** None + +##### **Termination Method** + +**Parameter name:** Termination Method +**Parameter ID:** Meth (0x0003) +**Description:** indicates the reason for generation of the event. See the procedures in clause 7.1.14. +**Type:** Enumeration +**Optional:** No + +**Possible values:** "UM" (0x0001) Unambiguous match +"PM" (0x0002) Partial match, completion by timer expiry or unmatched event +"FM" (0x0003) Full match, completion by timer expiry or unmatched event + +**Default:** None + +### E.6.3 Signals + +None. + +### E.6.4 Statistics + +None. + +### E.6.5 Procedures + +DigitMap processing is activated only if an Events Descriptor is activated that contains a DigitMap completion event as defined in clause E.6.2 and that DigitMap completion event contains an EventDM field in the requested actions as defined in clause 7.1.9. Other parameters such as KeepActive or embedded Events or Signals Descriptors may also be present in the Events Descriptor and do not affect the activation of DigitMap processing. By default DigitMaps are processed according to the procedures of 7.1.14 and when the DigitMap has completed (see clause 7.1.14.4) it is notified to the MGC, and any embedded signals and embedded events are triggered. However, if the Unsuccessful Match Reporting is set to "*off*" and the DigitMap completion was triggered as a result of an unsuccessful match, then the DigitMap completion event is not notified to the MGC nor are embedded signals and/or embedded events triggered. The DigitMap however will be de-activated. + +## E.7 Call Progress Tones Generator Package + +**Package name:** Call Progress Tones Generator Package + +**Package ID:** cg 0x0007 + +**Description:** This package defines the basic call progress tones as signals and extends the allowed values of the tl parameter of playtone in tonegen. + +**Version:** 2 + +**Extends:** tonegen version 2 + +### E.7.1 Properties + +None. + +### E.7.2 Events + +None. + +### E.7.3 Signals + +#### E.7.3.1 Dial Tone + +**Signal name:** Dial Tone + +**Signal ID:** dt (0x0030) + +**Description:** Generate dial tone. The physical characteristic of dial tone is available in the gateway. + +**Signal Type:** TimeOut +**Duration:** Provisioned +**Additional parameters:** None +**Additional values:** dt (0x0030) is defined as a tone ID for playtone + +The other tones of this package are defined in exactly the same way. A table with all signal names and SignalIDs is included. Note that each tone is defined as both a signal and a tone ID, thus extending the basic tone generation package. + +| Signal name | SignalID/tone ID | +|---------------------------|------------------| +| Dial Tone | dt (0x0030) | +| Ringing Tone | rt (0x0031) | +| Busy Tone | bt (0x0032) | +| Congestion Tone | ct (0x0033) | +| Special Information Tone | sit (0x0034) | +| (Recording) Warning Tone | wt (0x0035) | +| Payphone Recognition Tone | prt (0x0036) | +| Call Waiting Tone | cw (0x0037) | +| Caller Waiting Tone | cr (0x0038) | + +### E.7.4 Statistics + +None. + +### E.7.5 Procedures + +NOTE – The required set of tone IDs corresponds to those defined in [b-ITU-T E.180]. See [b-ITU-T E.180] for definition of the meanings of these tones. + +## E.8 Call progress tones detection package + +**Package name:** Call Progress Tones Detection Package +**Package ID:** cd (0x0008) +**Description:** This package defines the basic call progress detection tones. This package extends the possible values of tone ID in the Start Tone Detected, End Tone Detected and Long Tone Detected Events. +**Additional values:** Tone ID values are defined for Start Tone Detected, End Tone Detected and Long Tone Detected with the same values as those in package cg (Call Progress Tones Generation Package). +The required set of tone IDs corresponds to [b-ITU-T E.180]. See [b-ITU-T E.180] for definition of the meanings of these tones. +**Version:** 1 +**Extends:** tonedet version 1 + +### E.8.1 Properties + +None. + +### E.8.2 Events + +Events are defined as in the Call Progress Tones Generator Package (cg) for the tones listed in the table of E.7.3. + +### E.8.3 Signals + +None. + +### E.8.4 Statistics + +None. + +### E.8.5 Procedures + +None. + +## E.9 Analog Line Supervision Package + +| | | +|----------------------|-------------------------------------------------------------| +| Package name: | Analog Line Supervision Package | +| Package ID: | al (0x0009) | +| Description: | This package defines events and signals for an analog line. | +| Version: | 1 | +| Extends: | None | + +### E.9.1 Properties + +None. + +### E.9.2 Events + +#### E.9.2.1 On-hook + +| | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | On-hook | +| Event ID: | on (0x0004) | +| Description: | Detects handset going on-hook. Whenever an Events Descriptor is activated that requests monitoring for an on-hook event and the line is already on-hook, then the MG shall behave according to the setting of the "strict" parameter. | + +##### EventsDescriptor Parameters: + +##### Strict Transition + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Strict Transition | +| Parameter ID: | strict (0x0001) | +| Description: | Indicates how the on-hook event is detected. | +| Type: | Enumeration | +| Optional: | Yes | +| Possible values: | "exact" (0x0000): Only an actual hook state transition to on-hook is to be recognized
"state" (0x0001): The event is to be recognized either if the hook state transition is detected or if the hook state is already on-hook
"failWrong" (0x0002): If the hook state is already on-hook, the command fails and an error is reported | +| Default: | Exact | + +##### ObservedEventsDescriptor Parameters: + +##### Initial State + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Initial State | +| Parameter ID: | init (0x0002) | +| Description: | The reason for reporting the on-hook transition. Only returned if the Strict Transition parameter is set to "state". | +| Type: | Boolean | +| Possible values: | "True" The line was already on-hook when the Events Descriptor containing this event was activated "False" An actual state transition to on-hook was detected. | +| Default: | None | + +#### E.9.2.2 Off-hook + +| | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Off-hook | +| Event ID: | of (0x0005) | +| Description: | Detects handset going off-hook. Whenever an Events Descriptor is activated that requests monitoring for an off-hook event and the line is already off-hook, then the MG shall behave according to the setting of the "strict" parameter. | + +##### EventsDescriptor Parameters: + +##### Strict Transition + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Strict Transition | +| Parameter ID: | strict (0x0001) | +| Description: | Indicates how the off-hook event is detected. | +| Type: | Enumeration | +| Possible values: | "exact" (0x0000) Only an actual hook state transition to off-hook is to be recognized "state" (0x0001) The event is to be recognized either if the hook state transition is detected or if the hook state is already off-hook "failWrong" (0x0002) If the hook state is already off-hook, the command fails and an error is reported | +| Default: | Exact | + +##### ObservedEventsDescriptor Parameters: + +##### Initial State + +| | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Initial State | +| Parameter ID: | init (0x0002) | +| Description: | The reason for reporting the off-hook transition. Only returned if the Strict Transition parameter is set to "state". | +| Type: | Boolean | +| Optional: | Yes | +| Possible values: | "True" The line was already off-hook when the Events | + +Descriptor containing this event was activated "False" An actual state transition to off-hook was detected. + +**Default:** None + +#### E.9.2.3 Flashhook + +**Event name:** Flashhook + +**Event ID:** fl (0x0006) + +**Description:** Detects handset flash. A flash occurs when an on-hook is followed by an off-hook between a minimum and maximum duration. + +##### EventsDescriptor Parameters: + +##### Minimum Duration + +**Parameter name:** Minimum Duration + +**Parameter ID:** mindur (0x0004) + +**Description:** The minimum time between an on-hook and an off-hook to be detected as a flash. + +**Type:** Integer + +**Optional:** Yes + +**Possible values:** Any positive integer in milliseconds + +**Default:** Provisioned. + +##### Maximum Duration + +**Parameter name:** Maximum Duration + +**Parameter ID:** maxdur (0x0005) + +**Description:** The maximum time between an on-hook and an off-hook to be detected as a flash. + +**Type:** Integer + +**Optional:** Yes + +**Possible values:** Any positive integer in milliseconds + +**Default:** Provisioned. + +**ObservedEventsDescriptor Parameters:** None + +### E.9.3 Signals + +#### E.9.3.1 Ring + +**Signal name:** Ring + +**Signal ID:** ri (0x0002) + +**Description:** Applies ringing on the line + +**Signal Type:** TimeOut + +**Duration:** Provisioned + +**Additional parameters:** + +**Cadence** + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Cadence | +| Parameter ID: | cad (0x0006) | +| Description: | Represents durations of alternating on and off segments, constituting a complete ringing cycle starting with an on. Restricted function MGs may ignore cadence values they are incapable of generating. | +| Type: | Sublist of Integer | +| Optional: | Yes | +| Possible values: | Any positive integer in milliseconds | +| Default: | Provisioned | +| Frequency | | +| Parameter name: | Frequency | +| Parameter ID: | freq (0x0007) | +| Description: | The frequency of the ringing. Restricted function MGs may ignore frequency values they are incapable of generating. | +| Type: | Integer | +| Optional: | Yes | +| Possible values: | Any positive integer in Hz | +| Default: | Provisioned. | + +### E.9.4 Statistics + +None. + +### E.9.5 Error codes + +| | | +|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Error Code #: | 540 | +| Name: | Unexpected initial hook state | +| Definition: | This error is generated when the MGC has tried to request a hook state transition event with the Strict Parameter set to "failWrong", and the hook state is already what the transition implies. | +| Error Text in the Error Descriptor: | – | +| Comment: | – | + +### E.9.6 Procedures + +If the MGC sets an Events Descriptor containing a hook state transition event (on-hook or off-hook) with the Strict (0x0001) Parameter set to "failWrong", and the hook state is already what the transition implies, the execution of the command containing that Events Descriptor fails. The MG shall include Error Code 540 ("Unexpected initial hook state") in its response. + +## E.10 Basic Continuity Package + +| | | +|----------------------|------------------------------------------------------------------| +| Package name: | Basic Continuity Package | +| Package ID: | ct (0x000a) | +| Description: | This package defines events and signals for continuity test. The | + +continuity test includes provision of either a loopback or transceiver functionality. + +**Version:** 1 +**Extends:** None + +### E.10.1 Properties + +None. + +### E.10.2 Events + +#### E.10.2.1 Continuity Test Completion + +**Event name:** Completion +**Event ID:** cmp (0x0005) +**Description:** This event detects the completion of a continuity test. +**EventsDescriptor Parameters:** None +**ObservedEventsDescriptor Parameters:** + +##### Continuity Test Result + +**Parameter name:** Result +**Parameter ID:** res (0x0008) +**Description:** Indicates the result of the continuity test. +**Type:** Enumeration +**Optional:** No +**Possible values:** "SUCCESS" (0x0001) Success "FAILURE" (0x0000) Failure +**Default:** None + +### E.10.3 Signals + +#### E.10.3.1 Continuity Test + +**Signal name:** Continuity Test +**Signal ID:** ct (0x0003) +**Discussion:** Initiates sending of continuity test tone on the termination to which it is applied. +**Signal Type:** TimeOut +**Default:** Provisioned +**Additional parameters:** None + +#### E.10.3.2 Respond to Continuity Test + +**Signal name:** Respond +**Signal ID:** rsp (0x0004) +**Description:** The signal is used to respond to a continuity test. See E.10.5 for further explanation. + +| | | +|-------------------------------|-------------| +| Signal Type: | On/Off | +| Default: | Provisioned | +| Additional parameters: | None | + +### E.10.4 Statistics + +None. + +### E.10.5 Procedures + +When an MGC wants to initiate a continuity test, it sends a command to the MG containing: + +- a Signals Descriptor with the ct Signal; and +- an Events Descriptor containing the cmp Event. + +Upon reception of a command containing the ct Signal and cmp Event, the MG initiates the continuity test tone for the specified termination. If the return tone is detected and any other required conditions are satisfied before the signal times out, the cmp Event shall be generated with the value of the result parameter equal to success. In all other cases, the cmp Event shall be generated with the value of the result parameter equal to failure. + +When an MGC wants the MG to respond to a continuity test, it sends a command to the MG containing a Signals Descriptor with the rsp Signal. Upon reception of a command with the rsp Signal, the MG either applies a loopback or (for 2-wire circuits) awaits reception of a continuity test tone. In the loopback case, any incoming information shall be reflected back as outgoing information. In the 2-wire case, any time the appropriate test tone is received, the appropriate response tone should be sent. The MGC determines when to remove the rsp Signal. + +When a continuity test is performed on a termination, no echo devices or codecs shall be active on that termination. The termination under test does not need to have its ServiceStates Property set to Test. + +Performing voice path assurance as part of continuity testing is provisioned by bilateral agreement between network operators. + +NOTE – Example tones and test procedure details are given in clauses 7 and 8/[b-ITU-T Q.724], 2.1.8/[b-ITU-T Q.764] and [b-ITU-T Q.1902.4]. + +## E.11 Network Package + +| | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | Network Package | +| Package ID: | nt (0x000b) | +| Description: | This package defines properties of network terminations independent of network type. This includes, but is not limited to, TDM, IP and ATM. | +| Version: | 1 | +| Extends: | None | + +### E.11.1 Properties + +#### E.11.1.1 Maximum Jitter Buffer + +| | | +|-----------------------|---------------------------------------------------------| +| Property name: | Maximum Jitter Buffer | +| Property ID: | jit (0x0007) | +| Description: | This property puts a maximum size on the jitter buffer. | + +**Type:** Integer +**Possible values:** Any positive integer in milliseconds. +**Default:** Provisioned +**Defined in:** LocalControl Descriptor +**Characteristics:** Read/Write + +### E.11.2 Events + +#### E.11.2.1 Network Failure + +**Event name:** Network Failure +**Event ID:** netfail (0x0005) +**Description:** The termination generates this event upon detection of a failure due to external or internal network reasons. + +**EventsDescriptor Parameters:** None + +**ObservedEventsDescriptor Parameters:** + +##### Cause + +**Parameter name:** Cause +**Parameter ID:** cs (0x0001) +**Description:** This parameter may be included with the failure event to provide diagnostic information on the reason of failure. +**Type:** String +**Optional:** Yes +**Possible values:** any text string +**Default:** None + +#### E.11.2.2 Quality Alert + +**Event name:** Quality Alert +**Event ID:** qualert (0x0006) +**Description:** This event allows the MG to indicate a loss of quality of the network connection. The MG may do this by measuring packet loss, inter-arrival jitter, propagation delay and then indicating this using a percentage of quality loss. + +**EventsDescriptor Parameters:** + +##### Threshold + +**Parameter name:** Threshold +**Parameter ID:** th (0x0001) +**Description:** threshold for percent of quality loss measured, calculated based on a provisioned method that could take into consideration packet loss, jitter, and delay for example. Event is triggered when calculation exceeds the threshold. +**Type:** Integer + +**Optional:** Yes +**Possible values:** 0 to 99 +**Default:** Provisioned + +##### **ObservedEventsDescriptor Parameters:** + +##### **Threshold** + +**Parameter name:** Threshold +**Parameter ID:** th (0x0001) +**Description:** percent of quality loss measured, calculated based on a provisioned method that could take into consideration packet loss, jitter, and delay for example. +**Type:** Integer +**Optional:** Yes +**Possible values:** 0 to 99 +**Default:** None + +### **E.11.3 Signals** + +None. + +### **E.11.4 Statistics** + +#### **E.11.4.1 Duration** + +**Statistic name:** Duration +**Statistics ID:** dur (0x0001) +**Description:** provides duration of time the termination has existed or been out of the NULL context. +**Type:** Double +**Possible values:** Any positive integer in milliseconds +**Level:** Either + +#### **E.11.4.2 Octets Sent** + +**Statistic name:** Octets Sent +**Statistic ID:** os (0x0002) +**Description:** Provides the number of octets sent from the termination or stream since the termination has existed or been out of the NULL Context. The octets represent the egress media flow excluding all transport overhead. At the termination level, it is equal to the sum of the egress flows over all streams. + For analogue transmission media, the octet count shall be set equal to zero. +**Type:** Double +**Possible values:** any 64-bit integer 0 and up +**Level:** Either + +#### **E.11.4.3 Octets Received** + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic name: | Octets Received | +| Statistic ID: | or (0x0003) | +| Type: | Double | +| Description: |

Provides the number of octets received on the termination or stream since the termination has existed or been out of the NULL Context. The octets represent the ingress media flow excluding all transport overhead. At the termination level, it is equal to the sum of the ingress flows over all streams.

For analogue transmission media, the octet count shall be set equal to zero.

| +| Possible values: | any 64-bit integer 0 and up | +| Level: | Either | + +### **E.11.5 Procedures** + +#### **E.11.5.1 Procedures for application of the Network Failure and Quality Alert events** + +The application of the two events defined by the package depends on: + +- the specific bearer type (e.g., TDM, Analog Line, RTP, IP, AAL 2, AAL 1, etc.); +- the underlying transmission layer technology (e.g., analog, PDH, SDH, SONET, xDSL, 802.3, 802.11, etc.); +- whether the event is associated with resources internal or external to the MG. + +##### **E.11.5.1.1 Common for both events** + +The application of either event requires an understanding between the MGC and the MG. If the MG and MGC lack a consistent view of their meaning, the MGC will not be able to act on them effectively. + +Explicit recommendations are beyond the scope of the ITU-T H.248.1 core protocol. The specific usage of these events should be rather specified in ITU-T H.248 Profile specifications. + +##### **E.11.5.1.2 Specific to event "Network Failure"** + +The Cause Parameter can be used to distinguish between different failure modes. The termination type also helps in the interpretation of the event. + +##### **E.11.5.1.3 Specific to event "Quality Alert"** + +The detection logic should be based on one or more performance metrics related to quality of service from which a value comparable to the Threshold Parameter may be derived. + +The details of the underlying measurement and estimation process (the QoS-related observation variables, the filter mechanisms, the update period lengths, etc.) may be specified in an ITU-T H.248 Profile. + +##### **E.11.5.1.4 Relationship to ServiceChange procedures** + +A Network Failure or Quality Alert Event may trigger a ServiceChange procedure on the termination(s) affected. The transition to OutOfService may be initiated by the MG or the MGC, depending on circumstances. + +##### E.11.5.1.5 Calculating the Octets Sent and Octets Received Statistics + +When calculating the *os* and *or* statistics, the transport overhead is to be excluded. This means that the network transport overhead is not included, but overhead for the transport protocol and application layer is included in the count. For example, in an IP network using UDP for the transport protocol, to calculate the *os* statistic, the overhead associated with layers 1-3 (IP and below) is excluded, but overhead for layers 4-7 (UDP and above) is included in the count. Figure E.1 illustrates the concept of an IP stack and various possibilities for the definition of transport overhead. For the *nt* package, option c is the correct definition. + +![Figure E.1: Possible transport overhead calculations for IP-based networks. The diagram shows a protocol stack with five layers: L1 (bottom), L2, L3: IP (Network protocol), L4: UDP, TCP, ... (Transport protocol), and Application level framing protocol (RTP, UDPTL, ...). Above the framing protocol is Application data (e.g., audio codec). Five vertical bars (a, b, c, d, e) show different ways to define transport overhead. Bar 'a' includes all layers above L1. Bar 'b' includes layers above L2. Bar 'c' includes layers above L3 (L4 and above). Bar 'd' includes layers above L4. Bar 'e' includes only the application data. A legend indicates that orange dotted areas represent 'Transport overhead' and green cross-hatched areas represent 'Reported traffic volume'.](9de1e2f286f8fee526dc87eafad60401_img.jpg) + +H.248.1 v3(13)\_FE.1 + +Figure E.1: Possible transport overhead calculations for IP-based networks. The diagram shows a protocol stack with five layers: L1 (bottom), L2, L3: IP (Network protocol), L4: UDP, TCP, ... (Transport protocol), and Application level framing protocol (RTP, UDPTL, ...). Above the framing protocol is Application data (e.g., audio codec). Five vertical bars (a, b, c, d, e) show different ways to define transport overhead. Bar 'a' includes all layers above L1. Bar 'b' includes layers above L2. Bar 'c' includes layers above L3 (L4 and above). Bar 'd' includes layers above L4. Bar 'e' includes only the application data. A legend indicates that orange dotted areas represent 'Transport overhead' and green cross-hatched areas represent 'Reported traffic volume'. + +Figure E.1 – Possible transport overhead calculations for IP-based networks + +## E.12 RTP Package + +| | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | RTP Package | +| Package ID: | rtp (0x000c) | +| Description: | This package is used to support packet-based multimedia data transfer by means of the Real-time Transport Protocol (RTP) [IETF RFC 3550]. | +| Version: | 2 | +| Extends: | nt version 1 | + +### E.12.1 Properties + +None. + +### E.12.2 Events + +#### E.12.2.1 Payload Transition + +| | | +|--------------------|--------------------| +| Event name: | Payload Transition | +| Event ID: | pltrans (0x0001) | + +**Description:** This event detects and notifies when there is a transition of the RTP payload format from one format to another. + +**EventsDescriptor Parameters:** None + +**ObservedEventsDescriptor Parameters:** + +##### **RTP Payload Type** + +**Parameter name:** rtppayload +**Parameter ID:** rtpptype (0x0001) +**Description:** The payload format to which the transition was made. +**Type:** Sublist of Enumeration +**Optional:** No +**Possible values:** The encoding method shall be specified by using one or several valid encoding names, as defined in the RTP AV Profile or registered with IANA. +**Default:** None + +### **E.12.3 Signals** + +None. + +### **E.12.4 Statistics** + +#### **E.12.4.1 Packets Sent** + +**Statistic name:** Packets Sent +**Statistic ID:** ps (0x0004) +**Description:** Provides the number of RTP packets sent from the termination or stream since the termination has existed or been out of the NULL Context and the statistic has been enabled. +**Type:** Double +**Possible values:** any 64-bit integer 0 and up +**Level:** Either + +#### **E.12.4.2 Packets Received** + +**Statistic name:** Packets Received +**Statistic ID:** pr (0x0005) +**Description:** Provides the number of RTP packets received on the termination or stream since the termination has existed or been out of the NULL Context and the statistic has been enabled. +**Type:** Double +**Possible values:** any 64-bit integer 0 and up +**Level:** Either + +#### **E.12.4.3 Packet Loss** + +**Statistic name:** Packet Loss +**Statistic ID:** pl (0x0006) + +**Description:** Describes the current rate of packet loss on an RTP stream, as defined in [IETF RFC 3550]. Packet loss is expressed as percentage value: number of packets lost in the interval between two reception reports, divided by the number of packets expected during that interval. + +**Type:** Double + +**Possible values:** a 32-bit whole number and a 32-bit fraction. + +The actual data type is a fixed point number, which is mapped on the ITU-T H.248 type "double". The whole number and the fractional part shall be interpreted as 32-bit integer each, thus the "double" type for rtp/pl shall be encoded as the concatenation of two integers. The fractional part must be therefore first converted into an integer, i.e., multiplied by $2^{32}$ . + +For example, given the percentage 23.625, to express this in the Packet Loss Statistic we perform the following steps: + +1. Convert the number to binary: $23.625_{10}$ equals $10111.101_2$ . +2. Multiply the binary number by $2^{32}$ . Note that multiplying a binary number by a power of two is the same as shifting it to the left the same number of places as the power of two by which it is being multiplied. $101111010000000000000000000000000000000000000000$ is the binary value of our statistic. +3. Convert the binary value to a decimal double: the statistic is reported as having value 101468602368. + +To return the statistic back to its fractional representation, the steps are reversed. Once the double is converted back to its binary form, the lower 32 bits represent the fraction and the rest are the whole number. From there, conversion back to a floating point number is fairly straightforward. + +Binary encoding shall be as described in clause A.2 for type "integer". + +**Level:** Either + +#### E.12.4.4 Jitter + +**Statistic name:** Jitter + +**Statistic ID:** jit (0x0007) + +**Description:** Requests the current value of the inter-arrival jitter on an RTP stream as defined in [IETF RFC 3550]. Jitter measures the variation in inter-arrival time for RTP data packets. + +**Type:** Double + +**Possible values:** any 64-bit integer 0 and up + +**Level:** Either + +#### E.12.4.5 Delay + +**Statistic name:** Delay + +| | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic ID: | delay (0x0008) | +| Description: |

Requests the current value (Note 1) of packet round-trip propagation delay (RTPD) expressed in timestamp units. The computation of RTPD may be based upon RTCP sender reports and receiver reports (Note 2).

NOTE 1 – The term "current value" mentioned in the description is the latest (most recently measured) RTPD.

NOTE 2 – The arrival of a new RTCP SR/RR packet leads to the computation of a new latest (most recently measured) RTPD value. This is based on the RTCP protocol elements "delay since last SR (DLSR)" and "last SR timestamp (LSR)" as well as the report block arrival time, according to section 6.4.1 of [IETF RFC 3550].

| +| Type: | Double | +| Possible values: | any 64-bit integer 0 and up | +| Level: | Either | + +#### E.12.4.6 Cumulative Packet Loss + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic name: | Cumulative Packet Loss | +| Statistic ID: | cpl (0x001c) | +| Description: |

Provides the total number of incoming packets that were lost since the statistic was enabled. This number is defined to be the number of packets expected less the number of packets actually received, where the number of packets received includes any which are late or duplicates. Thus, packets that arrive late are not counted as lost, and the loss may be negative if there are duplicates.

See [IETF RFC 3550] for further details.

| +| Type: | Double | +| Possible values: | Any value | +| Level: | Either | + +### E.12.5 Procedures + +#### E.12.5.1 Working with RTP + +When RTCP is associated with an RTP stream, RTCP shall remain unaffected by the ITU-T H.248.1 Mode Property in the LocalControl Descriptor. + +When RTCP is associated with an RTP stream and the MG receives an Empty Remote Descriptor for that stream, the MG shall stop the RTCP stream along with the corresponding RTP stream. + +Where the Payload Transition (*pltrans*) event is used, the codec currently used by the relevant Stream on the MG is the start codec. In the case where an MG has not selected a codec for use, it can be assumed that the initial codec is the first one listed in the Local Descriptor (e.g., SDP). Therefore, an MG receiving the *pltrans* event from the MGC should consider the first codec listed as the "start codec". If the MG chooses another codec, it should send a Notify.req with the *pltrans* observed event. + +#### E.12.5.2 Calculation of the Octets Sent and Octets Received Statistics + +Because the *os* and *or* statistics are inherited from the *nt* package, they must retain the same calculation for both packages. Therefore, these statistics are calculated as defined in the *nt* package, + +even when addressed in the *rtp* package. This means that the octet counts include all data from layer 4 and above, including UDP, RTP and the application data. + +#### E.12.5.3 Time-based statistics and applicability to multi-flow streams + +The time-based statistics *Jitter* and *Delay* are expressed in terms of RTP timestamp units, i.e., a relative time basis. This may lead to ambiguities in particular situations, e.g., when the MGC would enable multiple media formats, with different timestamp units, in a single RTP session. Such an RTP media flow on an ITU-T H.248 stream may be created by using a *ReserveValue* setting of 'True'. For example, the MGC could enable narrowband and wideband audio codec types "in parallel" on an RTP endpoint, which may lead to a mutual transmission of RTP packet sequences with different sample rates (and thus different timestamp units). The use of time-based statistics in multiflow streams may lead to undefined behaviour. It should be noted that behaviour may be defined by a profile specification. Therefore, where multi-flow streams are used, other statistics based on RTCP extended report (e.g., [b-IETF RFC 3611]) such as those defined in [ITU-T H.248.30] or other Recommendations subsequently defined should be used. + +NOTE – The correspondent metrics defined by RTCP extended reports are unambiguous due to absolute time. + +## E.13 TDM Circuit Package + +| | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | TDM Circuit Package | +| Package ID: | tdmc (0x000d) | +| Description: |

This package may be used by any termination that supports gain and echo control. It was originally intended for use on TDM circuits but may be more widely used.

New versions or extensions of this package should take non-TDM use into account.

| +| Version: | 1 | +| Extends: | Network Package version 1 | + +### E.13.1 Properties + +#### E.13.1.1 Echo Cancellation + +| | | +|-------------------------|----------------------------------------------------------------------------------| +| Property name: | Echo Cancellation | +| Property ID: | ec (0x0008) | +| Type: | Boolean | +| Possible values: | "True" (when the echo cancellation is requested) "False" (when it is turned off) | +| Default: | Provisioned | +| Defined in: | LocalControl Descriptor | +| Characteristics: | Read/Write | + +#### E.13.1.2 Gain Control + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Gain Control | +| Property ID: | gain (0x000a) | +| Description: |

Gain control, or usage of signal level adaptation and noise level reduction, is used to adapt the level of the outbound signal. However, it is necessary, for example for modem calls, to turn off

| + +this function. When the value is set to "automatic", the termination serves as an automatic level control (ALC) with a target level provisioned on the MG and the direction being outward. + +| | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type: | Integer | +| Possible values: | The gain control specifies the gain in decibels (positive or negative), with the maximum positive integer, 214748647 (0x7fffffff), reserved to represent "automatic". | +| Default: | Provisioned | +| Defined in: | LocalControl Descriptor | +| Characteristics: | Read/Write | + +### E.13.2 Events + +None. + +### E.13.3 Signals + +None. + +### E.13.4 Statistics + +None. + +### E.13.5 Procedures + +None. + +## E.14 Segmentation Package + +| | | +|----------------------|----------------------------------------------------------------------------------------------------------------------| +| Package name: | Segmentation Package | +| Package ID: | seg (0x00A3) | +| Description: | This package defines properties for use when performing ITU-T H.248-based segmentation on non-segmenting transports. | +| Version: | 1 | +| Extends: | root version 2. Version 2 of the Segmentation Package requires at least version 3 of the protocol. | + +### E.14.1 Properties + +#### E.14.1.1 MG Segmentation Timer Value + +| | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | MGSegmentationTimerValue | +| Property ID: | MGSegmentationTimerValue (0x0009) | +| Description: | Indicates the time within which the MGC should expect the reception of any outstanding message segments from the MG once the SegmentationCompleteToken is received. Initially set to MGProvisionalResponseTimerValue, but may be changed. | +| Type: | Integer | +| Possible values: | any positive integer in milliseconds | +| Default: | Provisioned | +| Defined in: | TerminationState | + +**Characteristics:** Read/Write + +#### **E.14.1.2 MGC Segmentation Timer Value** + +**Property name:** MGCSegmentationTimerValue + +**Property ID:** MGCSegmentationTimerValue (0x000A) + +**Description:** Indicates the time within which the MG should expect the reception of any outstanding message segments from the MGC once the SegmentationCompleteToken is received. Initially set to MGCProvisionalResponseTimerValue, but may be changed. + +**Type:** Integer + +**Possible values:** any positive integer in milliseconds + +**Default:** Provisioned + +**Defined in:** TerminationState + +**Characteristics:** Read/Write + +#### **E.14.1.3 MG Maximum PDU Size** + +**Property name:** MGMaxPDUSize + +**Property ID:** MGMaxPDUSize (0x000B) + +**Description:** Indicates the maximum size of the MG's incoming protocol data unit for the control association's transport protocol. The MGC should avoid building messages that exceed this size. + +**Type:** Integer + +**Possible values:** any positive integer in bytes + +**Default:** Provisioned + +**Defined in:** TerminationState + +**Characteristics:** ReadOnly + +#### **E.14.1.4 MGC Maximum PDU Size** + +**Property name:** MGCMaxPDUSize + +**Property ID:** MGCMaxPDUSize (0x000C) + +**Description:** Indicates the maximum size of the MGC's incoming protocol data unit for the control association's transport protocol. The MG should avoid building messages that exceed this size. + +**Type:** Integer + +**Possible values:** any positive integer in bytes + +**Default:** Provisioned + +**Defined in:** TerminationState + +**Characteristics:** Read/Write + +### **E.14.2 Events** + +None. + +### E.14.3 Signals + +None. + +### E.14.4 Statistics + +None. + +### E.14.5 Error Codes + +| | | +|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| Error Code #: | 459 | +| Name: | Segments not received | +| Definition: | This error indicates that the recipient of a segmented TransactionReply timed out waiting for all the segments to be delivered. | +| Error Text in the Error Descriptor: | The TransactionID followed by the missing segment numbers are included. | +| Comment: | – | + +### E.14.6 Procedures + +Because some transports do not automatically segment messages that exceed the maximum transmission unit of the transport, messages may end up being truncated. If the message in question contains multiple TransactionReplies, the sender should send each TransactionReply in a separate message. If there remain messages that exceed the MTU length, the sender may implement the following segmentation procedures for TransactionReplies. TransactionRequests shall not be segmented. + +When segmenting a transaction reply, the sender shall ensure that the message contains complete commands and/or actions. Each segment is indicated by additional segment information at the transaction level. Each segment shall use the same TransactionID, and shall not repeat commands or completed actions in subsequent segments. Each segment shall be numbered serially starting at 1 and continuing through the last segment, which is denoted by inclusion of the SegmentationCompleteToken. In all cases, the segmented messages shall be syntactically valid constructs. The receiver replies to each segment in turn, utilizing the segmentation response. Because the segments are complete messages in themselves, the receiving entity does not need to wait for further segments before processing any particular segment. + +Upon reception of the final segment, the receiver shall determine if it has received all the message segments. If it has, then the receiver shall respond with a TransactionResponseAcknowledgement. + +If the receiver has not received all the segments, it shall start a timer, and wait for any missing segments. The length of the timer shall be provisionable upon the receiver, but should be the same length as the ProvisionalResponseTimerValue (see clause E.2.1) of the other entity. If the missing segments do not arrive before the timer expires, the receiver shall reply with Error Code 459 ("Segments not received"). + +#### Example 1: + +``` +Sender: !/3 [12.34.56.78]:2944 P=1/1{C=1{AV=term1{...}, AV=term2{...}}} +Receiver: !/3 [12.34.56.79]:2944 SM=1/1 +Sender: !/3 [12.34.56.78]:2944 P=1/2{C=1{AV=term3{...}}, C=2{AV=term4{...}}} +Receiver: !/3 [12.34.56.79]:2944 SM=1/2 +Sender: !/3 [12.34.56.78]:2944 P=1/3/&{C=3{AV=term5{...}}} +Receiver: !/3 [12.34.56.79]:2944 SM=1/3/& +Receiver: !/3 [12.34.56.79]:2944 K={1} +``` + +#### Example 2: + +``` + +Sender: !/3 [12.34.56.78]:2944 P=6/1{C=1{AV=term1{...}, AV=term2{...}}} +Receiver: !/3 [12.34.56.79]:2944 SM=6/1 +Sender: !/3 [12.34.56.78]:2944 P=6/4/&{C=3{AV=term5{...}}} +Receiver: !/3 [12.34.56.79]:2944 SM=6/4/& +/* Segmentation Timer Expires */ +Receiver: !/3 [12.34.56.79]:2944 ER=459{"6, 2, 3"} + +``` + +## E.15 Notification Behaviour + +**Package name:** Notification Behaviour Package +**Package ID:** nb (0x009a) +**Description:** The package has functionality that enables the MG at the request of the MGC to regulate the sending of Notify Commands. This package has an interaction with the NotifyBehaviour flag described in clause 7.1.9. This version of the package describes regulation behaviour based upon a percentage regulation. Other types of regulation behaviour are for further study. +**Version:** 1 +**Extends:** None + Version 1 of the Notification Behaviour Package requires at least version 3 of the protocol. + +### E.15.1 Properties + +#### E.15.1.1 Notification Regulation + +**Property name:** Notification Regulation +**PropertyId:** notreg (0x0001) +**Description:** Indicates the percentage of notifications on the MG that should be suppressed. A value of 0% indicates no suppression. A value of 100% indicates all notifies should be suppressed. This property shall be defined only on the Root Termination. When "Regulated Notify" is sent on a particular event, the MG uses the Notification Regulation Property to determine the correct percentage of Notifies to regulate (i.e., suppress). +**Type:** Integer +**Possible values:** 0-100 +**Default:** None +**Defined in:** TerminationState +**Characteristics:** Read/Write + +### E.15.2 Events + +None. + +### E.15.3 Signals + +None. + +### E.15.4 Statistics + +None. + +### **E.15.5 Procedures** + +#### **E.15.5.1 NotifyBehaviour** + +The NotifyBehaviour mechanism allows the MGC to manage how it should receive Notify.request commands from the MG. + +##### **E.15.5.1.1 NeverNotify** + +There may be instances where the MGC may not be interested in receiving a Notify.request command. For example: when detection of the occurrence of this event is essential to trigger an embedded signal or event, but the MGC does not need to be informed. Setting NotifyBehaviour Parameter to "NeverNotify" on an event ensures that the detection of the event is not notified to the MGC; however, any embedded signals or events are executed. NeverNotify does not have any relation to the Notification Regulation Property (nb/notreg) and events so marked are not included in the regulation calculations. + +##### **E.15.5.1.2 NotifyImmediate** + +The MGC may want to be notified of important events such as an 'Emergency Call' event, even though some other events are being regulated. This is achieved by setting the NotifyBehaviour Parameter to "NotifyImmediate" for that particular event. This is the current default behaviour when events are detected. NotifyImmediate does not have any relation to the Notification Regulation Property (nb/notreg) and events so marked are not included in the regulation calculations. + +##### **E.15.5.1.3 RegulatedNotify** + +###### **E.15.5.1.3.1 Percentage Based Regulated Notify** + +When the NotifyBehaviour Parameter is set to "NotifyRegulated" on a particular event, the decision to send to the MGC a notification for any particular event occurrence is governed by the Notification Regulation (nb/notreg) Property on the Root Termination. The value of this property is determined and set by the MGC. For example, the regulation rate could correspond to the MGC congestion level. The MG will then be responsible for determining the correct percentage of Notify.Commands to be suppressed amongst the events that are marked as "NotifyRegulated" across the entire MG. + +The MG may implement any algorithm that achieves the set Notification Regulation percentage. The algorithm should be chosen so that the risk of synchronization between different MGs is minimized. A suggested algorithm is given below: + +For a given regulation percentage (e.g., 10%) the MG would do the following for events that had the RegulatedNotify flag: + +- 1) Suppress a number of notifications (e.g., Notification 1). +- 2) Accept a number of subsequent notifications until the NotificationRegulation percentage is reached (e.g., accept 9 Notifications). +- 3) Repeat steps 1 and 2 until the Regulation Percentage is modified. +- 4) To avoid problems with synchronization the MG should start in a random position in the suggested sequence above. + +If an event has the NotifyBehaviour Parameter set to "RegulatedNotify" and the Notification Regulation Property is set to zero, this will have the same effect as if the event was set to "ImmediateNotify", which is the default behaviour for event notification. + +The NotifyBehaviour mechanism should be used with caution to avoid incorrect states. For example, if the notification of an "off-hook" event is suppressed by the MG, then the MGC will not be able to provide the correct response (e.g., dial tone, congestion tone). This incorrect behaviour is avoided through the use of the embedded signal or embedded events mechanism to return an + +appropriate response without the MGC being involved at that time. The MGC may set both an embedded Signals or Events Descriptor to be triggered when an event marked "NotifyRegulated" is detected and accepted (i.e., notification not suppressed) and a separate regulated embedded Signals or Events Descriptor to be triggered when the event is detected and regulated (i.e., notification suppressed). + +NOTE – Even in the above case the MG is still unaware of what constitutes a call. It is simply performing a pre-programmed task rather than call control functionality. + +#### E.15.5.2 Example Scenario + +Given the scenario where an MGC and an MG are terminating analogue lines, the MGC/MG may exhibit different behaviour based on whether the MGC is in an overload state or not and whether the analogue line (ALN) is originating an emergency call or not. The different behaviours are shown in Table E.1 below: + +**Table E.1 – Potential MGC/MG Overload Behaviour** + +| MG Behaviour
Task: "Handling of analogue line call signalling (ALS)" = call control signalling traffic for POTS terminals (ALN; analogue line interfaces) | | 1) Call/Context Type | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Emergency call | Non-emergency call | +| 2) MGC Load State
NOTE – two-state model assumed. | Non-overload state (e.g.,) low, medium, high load) | I) MG:
Normal ALS processing with highest priority | II) MG:
Normal ALS processing with lower priority | +| | Overload state | III) MG:
Normal ALS processing
==> Call control
signalling forwarded to
MGC in "usual H.248
mode" | IV) MG:
Programmed local ALS
handling
==> MGC not involved
==> Call protocol
compliant rejected via
"congestion tone" | + +##### E.15.5.2.1 Quadrant I and II Behaviour + +No special NotifyBehaviour is required on the MG as the MGC is not in overload and can receive all messages (notifications) from the MG. However, once the MGC has determined the type of call, it may set a priority in the MG by using an appropriate Context Attribute (i.e., the priority indicator). + +##### E.15.5.2.2 Quadrant III and IV Behaviour + +When the MGC has determined it is in an overloaded state, it may send the following command to all or some selected group of the terminations in the NULL Context. + +``` +Example message: +Transaction=1234{ + Context = - { + Modify = aln/* { ; select terminations as desired + Events = 1234 { + al/of { + RegulatedNotify { + Embed { + Signals {cg/dt} , + ; If the off-hook is regulated apply dial tone. + Events = 1235 { + xdd/xce { +``` + +``` + + DigitMap = PriorityDialPlan1, + bc = 20, + mp = enhanced, + ImmediateNotify + }, +; If emergency generate notify to MGC + xdd/xce { + DigitMap = NonPriorityDialPlan1, + bc = 20, + mp = enhanced, + NeverNotify, + Embed{ + Signals {cg/ct} + } + }, +; If non-priority send congestion tone and never notify + al/on { + NeverNotify, + ResetEventsDescriptor + } +; If on-hook is detected then reset the EventsDescriptor +; and never notify + } + } + } + } +} + +``` + +NOTE – The context identity may be specific or NULL and the terminationID may be wildcarded or specific depending on how and when this behaviour is set on the MG. Use of Wildcard reply will limit the number of responses if the overload behaviour is loaded as the MGC goes into overload. + +### E.15.5.2.3 If the Notification Regulation Property is set to non-zero (overloaded state) + +The behaviour of the MG in the case that an off-hook is detected and it is regulated would be to: + +- suppress the notification of an off-hook to the MGC; +- apply dial tone; +- receive digits dialled by the subscriber; +- if it has been determined that the user has dialled an emergency number, always generate the notification of the match with the "priority dial plan"; +- if it has been determined that the user has dialled a non-priority number, always suppress the notification of the match with the "non-priority dial plan" and apply congestion tone; +- enable the detection of on-hook (with NeverNotify) which on the receipt of an on-hook would cause the Events Descriptor on the termination to be reset back to the state before embedding was activated (or the MG-provisioned Events Descriptor). + +### E.15.5.2.4 If the Notification Regulation Property is set equal to zero (non-overloaded state) + +The behaviour of the MG in the above case would be to: + +- send a notification of off-hook to the MGC. + +If the overload behaviour Events Descriptor is set using explicit Modify Commands from the MGC (as opposed to using MG provisioning), then whilst the MGC remains in the overloaded condition, the overload behaviour Events Descriptor will be reloaded for each termination as part of the clearing sequence of any call/call attempt notified to the MGC. + +178 Rec. ITU-T H.248.1 (03/2013) + +When the MGC overload condition has ceased, the MGC may reset terminations in the NULL Context back to default non-overload behaviour. Alternatively, the MGC should set the Notification Regulation property equal to zero. + +# Annex F + +# ServiceChange Procedures + +(This annex forms an integral part of this Recommendation.) + +## F.1 Introduction + +This annex describes the use of ServiceChange procedures when certain events occur on an MG or MGC. It serves to clarify the ServiceChange procedures as described in clauses 7.2.8 and 11. Where there are discrepancies between this annex and this Recommendation, the procedures of the main body of this Recommendation, take precedence over those described in this annex. + +The events leading to the sending of a ServiceChange Command described in this annex are: + +- 1) MG Registration – The MG registers with an MGC and a control association is established. +- 2) MG Re-Registration – The MG registers with an MGC after it has been requested to do so by an MGC. +- 3) MG Service Cancellation – The MG informs the MGC that terminations or the MG as a whole is to be taken Out-of-Service. +- 4) MG Service Restoration – The MG has recovered after failure and notifies the MGC. +- 5) MG Redundant Takeover – A secondary MG takes over in the instance of failure or maintenance of a primary MG. +- 6) MG Lost Communication – The MG informs the MGC that it had previously lost communication with the MGC but this communication has now been restored. +- 7) MG Capability Change – The MG informs the MGC that the capabilities of terminations or the MG as a whole has changed. +- 8) MGC Initiated MG Re-Registration – The MGC informs the MG that the MG should re-register with the same MGC or another MGC. +- 9) MGC Initiated Service Restoration – The MGC has recovered after failure and orders the MG to place the relevant terminations in an initial state. +- 10) MGC Initiated Service Cancellation – The MGC informs the MG that terminations or the MG as a whole is being taken OutOfService. +- 11) MGC Redundant Failover – The primary MGC is failing and directs the MG to register with a specific secondary MGC. + +Figure F.1 illustrates these ServiceChange triggering events, the entity in which the event appears and which event pairs are correlated. Figure F.2 shows a state model to which the MG and terminations on the MG will conform. + +![Diagram of trigger events for ServiceChange between an MGC and an MG.](29aa6165ccf449dee0b4335676fa7b1a_img.jpg) + +This diagram illustrates the trigger events for ServiceChange between a Media Gateway Controller (MGC) and a Media Gateway (MG). The MGC is shown at the top with 'Primary' and 'Secondary' components, and the MG is at the bottom with similar components. A vertical line labeled 'Control association' connects them. Numbered circles (1-11) represent specific events, with arrows indicating where the event occurs and dashed lines showing related mechanisms. + +MGC initiated: + +- 8 – MG re-registration +- 10 – MG service cancellation +- 9 – MG service restoration + +MG initiated: + +- 1 – MG registration +- 2 – MG re-registration +- 3 – MG service cancellation +- 4 – MG service restoration +- 5 – MG redundant takeover +- 6 – MG lost communication +- 7 – MG capability change +- 11 – MGC redundant failover + +**Legend:** + +- Indicates where the ServiceChange triggering event occurs +- - - Indicates related ServiceChange mechanisms + +H.248.1 v3(13)\_FF.1 + +Diagram of trigger events for ServiceChange between an MGC and an MG. + +**Figure F.1 – Trigger events for ServiceChange** + +![Simple ServiceChange state model diagram.](dbe4ffa9778863279b48b56fe097cd23_img.jpg) + +This state model diagram shows the transitions between three states: 'Out-of-service', 'In-service', and 'Test'. Transitions are labeled with specific ServiceChange types or commands. + +- Out-of-service to In-service:** + - Restart, Disconnected, Failover, Handoff + - Forced +- In-service to Out-of-service:** + - Forced, Graceful +- Out-of-service to Test:** + - Test (Modify command) + - Forced +- Test to Out-of-service:** + - Forced, Subtract +- In-service to Test:** + - Test (Modify command) + - Graceful +- Test to In-service:** + - Restart + - Graceful +- Internal Transitions (Self-loops):** + - Out-of-service:** Forced, Graceful + - In-service:** Restart, Disconnected, Failover, Handoff; Restart, Disconnected + - Test:** Graceful +- Graceful delay:** A dashed oval representing a mechanism that can be applied during 'Graceful' transitions between 'Out-of-service' and 'In-service' states. + +H.248.1 v3(13)\_FF.2 + +Simple ServiceChange state model diagram. + +**Figure F.2 – Simple ServiceChange state model** + +## F.2 Control Association Definition + +A control association is a communication relationship whereby an MGC is controlling an MG. A control association is instantiated via registration. The control association is terminated by the MG going OutOfService, being successfully handed off to an alternate MGC, or successfully failing over to an alternate MGC. An MG shall have at most one control association at any time except where a physical MG is split into one or more Virtual MGs. In the Virtual MG case, each Virtual MG shall have at most one control association. Only MGs may instantiate control associations. Control associations as defined here apply only within the context of media gateway control signalling. This definition should not be confused with that of control associations in the context of transport (TCP, UDP, etc.). + +The use of ServiceChange Commands on the Root Termination only affects the Virtual MG to which the Root Termination belongs. Other Virtual MGs on the same physical MG are unaffected. + +## F.3 Events leading to ServiceChange Procedures + +### F.3.1 MG Registration + +The MG may register in one of three ways: + +- Announce its initial presence, or "registration" by using the ServiceChangeMethod "Restart" with ServiceChangeReasons 901 ("Cold Boot") or 902 ("Warm Boot"), +- Indicate that it is changing its association via the ServiceChangeMethod "Failover" and ServiceChangeReason 909 ("MGC Impending Failure") or 908 ("MG Impending Failure"), +- Indicate that it was commanded to change its association via the ServiceChangeMethod "Handoff" and ServiceChangeReason 903 ("MGC Directed Change") (Clause F.3.11). + +Registration starts when the initial ServiceChange Command is sent from the MG to the MGC and completes when the command is replied by the MGC without an alternate address or an error and the ServiceChangeProfile is agreed between the MGC and MG. The control association is established upon completion of registration. Registration always occurs on the Root Termination. Any existing control association between the MGC and MG is terminated upon initiation of a new registration. All commands from the previous control association shall be ignored. + +ServiceChangeProfile is used by registration. See clause F.5.5 for details. + +ServiceChangeVersion is used by registration. See clause F.5.6 for details. + +### F.3.2 MG Re-Registration + +MG Re-registration occurs in two cases: + +- 1) When the MGC requests the MG to re-register (clause F.3.8). The MG shall then send a ServiceChange with ServiceChangeMethod "Handoff", ServiceChangeReason 903 ("MGC Directed Change") and the designated "ServiceChangeMgcID". +- 2) When the MGC initiates service restoration (clause F.3.9). The MG shall reregister by sending a ServiceChange with ServiceChangeMethod "Restart". + +The re-registration is complete when the command is replied by an MGC without an alternate address or an error and the ServiceChangeProfile is agreed between the MGC and MG. If no response is received from the primary MGC then the MG shall follow the procedures of clause F.3.1. ServiceChangeReasons 903 ("MGC Directed Change") or 909 ("MGC Impending Failure") are recommended. + +The control association is established upon completion of registration. Registration always occurs on the Root Termination. Any existing control association between the MGC and MG is terminated upon initiation of the re-registration. All commands from the previous control association shall be ignored. + +ServiceChangeProfile is used by re-registration. See clause F.5.5 for details. + +ServiceChangeVersion is used by re-registration. See clause F.5.6 for details. + +### **F.3.3 MG Service Cancellation** + +To place the MG "OutOfService", the MG sends a ServiceChange Command with a ServiceChangeMethod of "Forced" or "Graceful" on the Root Termination. See clause F.4.1.1 for details. + +To place a termination or group of terminations "OutOfService", the MG sends a ServiceChange with a ServiceChangeMethod of "Forced" or "Graceful" on the termination(s) in question. See clauses F.4.1.2 and F.4.1.3 for details. + +ServiceChangeDelay indicates the length of time before the service cancellation will occur. See clause F.5.3 for details. + +To cancel a previously issued (and acknowledged) Graceful for the entire MG, the MG sends a ServiceChange Command on the Root Termination with a ServiceChangeMethod of "Restart" and ServiceChangeReason 918, "Cancel Graceful". The MG shall remain InService, and all terminations previously set OutOfService are returned to service unless otherwise signalled by the MG. In the event that a Cancel Graceful is received after the Delay timer has expired, the MG shall be deemed to have re-registered, just as if it had sent a Cold Boot. + +To cancel a previously issued (and acknowledged) Graceful on a termination or group of terminations, the MG sends a ServiceChange with a ServiceChangeMethod of "Restart" and a ServiceChangeReason of "Cancel Graceful" on the termination(s) in question. The termination shall remain InService. In the event that the termination has already transitioned OutOfService, it shall be returned to service just as it would with any ServiceChange Restart. + +### **F.3.4 MG Service Restoration** + +The MG Service Restoration event occurs when an MG returns to service after a failure or maintenance action. + +When sent by the MG, the MG sends a ServiceChange Command to the MGC announcing that it has restarted or wishes to renegotiate the protocol version or ITU-T H.248 profile. ServiceChangeMethod "Restart" and ServiceChangeReason 900 ("Service Restored") are used in this case. The ServiceChangeReason will indicate what actions may need to be taken by the MGC. + +### **F.3.5 MG Redundant Takeover** + +There are two cases for MG redundant takeover: + +#### 1) Takeover initiated by Primary MG: + +When an MG is going OutOfService and wishes to relinquish processing to a designated secondary MG, it sends a ServiceChange Command to the MGC with ServiceChangeMethod "Failover" and a ServiceChangeReason of 908 ("MG Impending Failure"). The MGC will cease messaging to the primary MG and terminate the control association. The secondary MG shall then send a ServiceChange Command with ServiceChangeMethod "Restart" and a ServiceChangeReason of 900 ("Service Restored"). The MGC shall then establish a new control association with the secondary MG. + +#### 2) Takeover initiated by Secondary MG: + +When an optional secondary unit of an MG detects a maintenance or failure outage of the primary MG unit and the primary is unable to notify the MGC of the failure, the secondary MG shall send a ServiceChange Command to the MGC with ServiceChangeMethod "Failover" and a ServiceChangeReason of either 919 ("Warm Failover") or 920 ("Cold Failover"), as appropriate. The procedures of clause F.3.4 apply. + +The MGC shall ignore all attempts at redundant takeover by unknown MGs. The MGC must have knowledge, through provisioning or other means, that the secondary MG announcing takeover is associated with the failed primary MG and therefore has authorization to takeover for the primary MG. + +If the secondary MG is known and has the authority to takeover for the primary MG, the MGC shall attempt to communicate with the primary MG to determine if it still functions. This may be done via an empty AuditValue Command or other suitable method (see clause 11.5). If the primary MG answers, the MGC shall reject the failover attempt. If the primary MG fails to answer, the MGC shall assume that it has failed, and accept the warm or cold failover. When the MGC accepts the warm or cold failover, the control association with the primary MG is removed and a new control association with the secondary MG is established. + +### **F.3.6 MG Lost Communication** + +When the MG has detected a loss and subsequent re-establishment of communication with the MGC (Note 1), the MG sends a ServiceChange Command (Note 2) with a ServiceChangeMethod of "Disconnected" to the MGC in the current control association. If the MGC fails to respond, the MG then sends a ServiceChange Command with a ServiceChangeMethod of "Failover" and ServiceChangeReason 909 ("MGC Impending Failure") to each MGC in its list in turn until it has successfully established a new control association, or it has exhausted its list of MGCs. If the MGC does respond, the control association continues as if it were not interrupted. + +NOTE 1 – The two main causes for lost communications between the MGC and MG are 1) failures or short-term interruptions of the ITU-T H.248 transport connection, or 2) the primary MGC going "OutOfService". The MG will not necessarily be able to discriminate between the two, therefore the ServiceChange procedures are the same in both cases. + +NOTE 2 – The MG may send one or more ServiceChange Commands. The transmission of subsequent ServiceChange Commands may be timer-controlled. Multiple re-establishment attempts may help in situations with short-term failures, either of the transport connection or of the MGC, thereby avoiding the invocation of failover procedures when they are not warranted. + +If the MGC in the original control association replies to the ServiceChange Command, the control association continues without interruption, and all commands are processed as if there had been no loss of communication. Otherwise, the original control association is terminated when the MG sends a ServiceChange to a new MGC, and all commands from the previous control association are ignored. A new control association is established once the new MGC replies to the ServiceChange, completing the registration. + +If the MG exhausts its list of MGCs without successfully establishing a control association, the MG waits a random amount of time and then attempts registration with the MGCs in its list again, starting with the MGC from the original control association. The MG will send a ServiceChange with a ServiceChangeMethod of "Disconnected" to the MGC from the original control association each time the MG attempts to contact it. The MG sends a ServiceChange with a ServiceChangeMethod of "Failover" to all other MGCs. + +MGCs that receive ServiceChange Commands with a ServiceChangeMethod of "Disconnected" should audit the MG to determine if a state mismatch has occurred due to lost messaging. + +In these scenarios, ServiceChangeReason 900 ("Service Restored") is recommended, though particular scenarios may require different ServiceChangeReason codes. + +### **F.3.7 MG Capability Change** + +To announce a change in capabilities of the MG, the MG sends a ServiceChange with an appropriate ServiceChangeMethod and a ServiceChangeReason of 916 ("Packages Change") or 917 ("Capabilities Change"). The MGC should audit the MG to determine the new capabilities of the MG. For an inservice MG that sends a ServiceChange Command with ServiceChangeMethod + +"Restart", the control association continues uninterrupted through a capability change, and the MG is not considered to have undergone a system restart. + +### **F.3.8 MGC Initiated MG Re-Registration** + +The MGC may request the MG to re-register by issuing a ServiceChange Command on Root with ServiceChangeMethod "Handoff", ServiceChangeReason 903 ("MGC Directed Change") and its own ServiceChangeMgcID (that is, that of the current MGC). + +See clause F.3.2 for action taken by the MG. + +### **F.3.9 MGC Initiated Service Restoration** + +To request that the MG restart itself, the MGC sends a ServiceChange Command to the MG with ServiceChangeMethod "Restart" and an appropriate ServiceChangeReason such as 900 ("Service Restored") or 901 ("Cold Boot"). The MG must establish a new control association in accordance with clause F.3.2 using the indicated ServiceChangeReason. + +To restore service to a termination or group of terminations, the MGC sends a ServiceChange with ServiceChangeMethod "Restart" on the termination(s) in question. See clauses F.4.1.2 and F.4.1.3 for actions to be taken by the MGC. + +ServiceChangeDelay indicates the length of time before the service restoration will occur. See clause F.5.3 for details. + +### **F.3.10 MGC Initiated Service Cancellation** + +#### **F.3.10.1 Root Termination** + +To place the MG "OutOfService", the MGC sends a ServiceChange Command with a ServiceChangeMethod of "Forced" or "Graceful" on the Root Termination. Appropriate ServiceChangeReasons may include 905 ("Termination taken out of service"), among others. See clause F.4.1.1 for actions to be taken by the MGC. + +ServiceChangeDelay indicates the time period at the end of which the service cancellation will occur. See clause F.5.3 for details. + +To cancel a previously issued (and acknowledged) Graceful for the entire MG, the MGC sends a ServiceChange Command on the Root Termination with a ServiceChangeMethod of "Restart" and ServiceChangeReason 918 ("Cancel Graceful"). The MG shall remain InService, and all terminations previously set OutOfService are returned to service unless otherwise signalled by the MG. In the event that a Cancel Graceful is received after the Delay timer has expired, the MG shall report an Error Code 502 ("Not Ready") to the MGC. The MG will be required to re-register to return to service. + +#### **F.3.10.2 Physical Terminations** + +To place a termination or group of terminations "OutOfService", the MGC sends a ServiceChange Command with a ServiceChangeMethod of "Forced" or "Graceful" on the termination(s) in question. Appropriate ServiceChangeReasons may include 904 ("Termination malfunctioning"), 905 ("Termination taken out of service"), 906 ("Loss of lower layer connectivity"), or 907 ("Transmission failure"), among others. See clauses F.4.1.2 and F.4.1.3 for actions to be taken by the MGC. + +ServiceChangeDelay indicates the time period at the end of which the service cancellation will occur. See clause F.5.3 for details. + +To cancel a previously issued (and acknowledged) Graceful on a termination or group of terminations, the MG sends a ServiceChange with a ServiceChangeMethod of "Restart" and ServiceChangeReason 918 ("Cancel Graceful") on the termination(s) in question. The termination + +shall remain InService. In the event that the termination has already transitioned OutOfService, it shall be returned to service just as it would with any ServiceChange Restart. + +#### **F.3.10.3 Ephemeral Terminations** + +The MGC shall not use ServiceChange to cancel service to ephemeral terminations. Subtracting the termination from context is sufficient to eliminate the termination. + +### **F.3.11 MGC Redundant Failover** + +When the MGC in a control association encounters a maintenance or failure condition such that it must go OutOfService, it may direct the MG to a specific secondary MGC by sending a ServiceChange Command with a ServiceChangeMethod of "Handoff", a ServiceChangeReason of 903 ("MGC Directed Change") and the address of the new MGC in the ServiceChangeMgcID parameter. The control association is terminated upon the receipt of the command reply from the MG. The MG then sends a ServiceChange Command to the specified MGC with a ServiceChangeMethod of "Handoff" and a ServiceChangeReason of 903 ("MGC Directed Change"). A new control association is established upon receipt of the command reply from the MGC. + +In the event that the specified MGC rejects the handoff attempt or the MGC is unable to send a ServiceChange Command with ServiceChangeMethod Handoff due to failure, the MG shall revert to the procedures for lost communication outlined in clause F.3.6, starting with its provisioned primary. + +## **F.4 ServiceChange Element Description** + +### **F.4.1 ServiceChangeMethod** + +This clause describes the behaviour of the ServiceChangeMethod on the different termination types. This clause is organized into: + +- The Root Termination; +- Physical terminations; +- Ephemeral terminations. + +#### **F.4.1.1 ServiceChange Method Behaviour on the Root Termination** + +The ServiceChange Command on Root has different effects depending upon the ServiceChangeMethod. The results of each ServiceChangeMethod are described below: + +- 1) Restart – Sent by the MG to announce that it has restarted, wishes to renegotiate the protocol version, profile, or is announcing a capability change. The ServiceChangeReason indicates what actions may need to be taken by the MGC. When sent by the MGC, the MG shall restart itself using the indicated ServiceChangeReason. +- 2) Forced – When sent by the MG, the MG indicates that it is going OutOfService immediately. The control association is terminated by the MG upon receipt of the command reply from the MGC. When sent by the MGC, the MG shall take itself OutOfService, and terminate the control association after sending the command reply. Note that an MGC cannot bring an MG back into service, even though it may request it to go OutOfService. The MG initiates registration to the MGC to establish a new control association and indicate service restoration, just as it would for any other registration. ServiceChangeDelay has no effect on ServiceChangeMethod "Forced". +- 3) Graceful – When sent by the MG, it indicates that the MG is going OutOfService at the end of the ServiceChangeDelay period. The control association is terminated at the end of the ServiceChangeDelay period. When sent by the MGC, the MG shall take itself OutOfService and terminate the control association at the end of the ServiceChangeDelay + +period. Using a ServiceChangeDelay equal to zero or an absent ServiceChangeDelay indicates that the MG shall go OutOfService and terminate the control association when the last context is removed through subtraction of its terminations, and that the MGC shall not add new connections. The MG should set the Root Termination ServiceStates Property at the expiry of ServiceChangeDelay or the removal of all terminations from active contexts (whichever is first), to "OutOfService". To cancel a previously sent (and acknowledged) ServiceChange with ServiceChangeMethod of "Graceful", the entity initiating the ServiceChangeMethod Graceful sends a ServiceChange Command with ServiceChangeMethod Restart and the ServiceChangeReason 918 ("Cancel Graceful"). + +- 4) Failover – When sent by the MG to an MGC that is not in the current control association, the MG indicates that its current MGC has failed, and it is attempting to register with the recipient of the command. When sent by the MG to the MGC in the current control association, the primary MG indicates that a secondary MG has taken over for the failed primary. In either instance, the previous control association is terminated upon the sending of the ServiceChange Command, and the new control association is established between the MG and new MGC, or MGC and new MG upon receipt of the command reply. MGCs shall not send ServiceChange Commands with the ServiceChangeMethod "Failover". +- 5) Handoff – When sent by the MGC, the MGC indicates that the MG is being transferred to a new MGC. This terminates the current control association, upon receipt of the command reply. When sent from the MG to the MGC, this indicates that the MG is attempting to establish a new control association in accordance with a handoff command received from the MGC in its previous control association. When sent from the MG to the MGC, a handoff is a registration, and a new control association is established upon receipt of the command reply. The MG shall not use Handoff without being commanded to do so by an MGC. +- 6) Disconnected – When sent by the MG, it indicates that communication in the current control association had been lost, but is now re-established. The current control association is renewed. MGCs shall not send ServiceChange Commands with the ServiceChangeMethod "Disconnected". + +#### F.4.1.2 ServiceChange Method Behaviour on Physical Terminations + +While the MG is in an active control association, issuing the ServiceChange Command on a physical termination has different effects depending on the ServiceChangeMethod. The results of each method are described below: + +- 1) Restart – When sent by the MG, the MG announces that the termination(s) have restarted, or is announcing a capability change. The ServiceChangeReason indicates what actions may need to be taken by the MGC. When sent by the MGC, the MG shall restart the termination(s) using the indicated ServiceChangeReason. +- 2) Forced – When sent by the MG, it indicates that the termination is going OutOfService immediately. When sent by the MGC, the MG shall take the termination OutOfService immediately. In both cases, the ServiceStates parameter shall be set to "OutOfService" and the MGC is responsible for cleaning up any contexts or resources associated with the termination. ServiceChangeDelay has no effect on the ServiceChangeMethod "Forced". +- 3) Graceful – When sent by the MG, it indicates that the termination(s) is going OutOfService after the ServiceChangeDelay. When sent by the MGC, the MG shall take the termination(s) OutOfService at the end of the ServiceChangeDelay period. The ServiceStates Property shall be set to "OutOfService" upon expiry of the ServiceChangeDelay or when the termination(s) is removed from an active context (whichever is first) and the MGC is responsible for cleaning up any contexts or resources associated with the termination(s). Using a ServiceChangeDelay equal to zero or an absent ServiceChangeDelay indicates that the termination shall go OutOfService when it is + +removed from context through subtraction. Terminations already in the NULL Context shall go out of service immediately. The MGC shall not use the indicated termination(s) for connection until the Graceful is cancelled or the termination is brought back into service by a subsequent ServiceChange Command. To cancel a previously sent (and acknowledged) ServiceChange with ServiceChangeMethod of "Graceful", the entity initiating the Graceful sends a ServiceChange Command with ServiceChangeMethod "Restart" and the ServiceChangeReason 918 ("Cancel Graceful"). + +- 4) Failover – The ServiceChangeMethod "Failover" shall not be used with non-Root terminations. +- 5) Handoff – The ServiceChangeMethod "Handoff" shall not be used with non-Root terminations. +- 6) Disconnected – The ServiceChangeMethod "Disconnected" shall not be used with non-Root terminations. + +#### **F.4.1.3 ServiceChange Method Behaviour on Ephemeral Terminations** + +While the MG is in an active control association, issuing the ServiceChange Command on an ephemeral termination has different effects depending on the ServiceChangeMethod. The results of each method are described below: + +- 1) Restart – When sent by the MG, the MG announces that the termination(s) has restarted, or is announcing a capability change. The ServiceChangeReason indicates what actions may need to be taken by the MGC. The MGC shall not send ServiceChangeMethod "Restart" for ephemeral terminations. +- 2) Forced – When sent by the MG, it indicates that the termination(s) is going OutOfService immediately. The MGC is responsible for subtracting the termination. The MGC shall not send ServiceChangeMethod "Forced" for ephemeral terminations. ServiceChangeDelay has no effect on ServiceChangeMethod "Forced". +- 3) Graceful – When sent by the MG, it indicates that the termination(s) is going OutOfService at the end of the ServiceChangeDelay period. The MGC is responsible for subtracting the termination(s) at the expiry of the ServiceChangeDelay. The MGC shall not send ServiceChangeMethod "Graceful" for ephemeral terminations. Using a ServiceChangeDelay equal to zero indicates that the termination is going OutOfService immediately. The MG should set the termination's ServiceStates Property at the expiry of ServiceChangeDelay to "Out of Service". The MGC is responsible for subtracting the termination in either case. To cancel a previously sent (and acknowledged) ServiceChange with ServiceChangeMethod of "Graceful", the entity initiating the Graceful sends a ServiceChange Command with ServiceChangeMethod Restart and the ServiceChangeReason of 918 "Cancel Graceful". +- 4) Failover – The ServiceChangeMethod "Failover" shall not be used with non-Root terminations. +- 5) Handoff – The ServiceChangeMethod "Handoff" shall not be used with non-Root terminations. +- 6) Disconnected – The ServiceChangeMethod "Disconnected" shall not be used with non-Root terminations. + +## **F.5 Use of ServiceChange parameters** + +### **F.5.1 ServiceChangeMethod** + +See the usage outlined in clause F.4. + +### F.5.2 ServiceChangeReason + +ServiceChangeReasons allow the receiving party to alter its behaviour to fit a particular situation. For example, if an MG sent a ServiceChangeReason 901 ("Cold Boot") to the MGC when it Restarted, the MGC could assume that the MG had lost all its state and therefore it would not perform maintenance and audit tasks to assess and clean up the MG to a useable state. + +Table F.1 shows with which ServiceChangeMethods particular ServiceChangeReasons may be sent. + +**Table F.1 – ServiceChangeMethod and ServiceChangeReason mapping** + +| SC Reason | SC Method | | | | | | Description | +|-----------|-----------|----------------------|----------------------|----------------------|----------------------|-----------|----------------------------------| +| | Restart | Forced | Graceful | Disconnected | Failover | Handoff | | +| 900 | X | | | Root only
MG only | | | Service Restored | +| 901 | Root only | | | | | | Cold Boot | +| 902 | Root only | | | | | | Warm Boot | +| 903 | | | | | | Root only | MGC Directed Change | +| 904 | | X | X | | | | Term Malfunction | +| 905 | | X | X | | | | Term Taken OOS | +| 906 | | X | X | | | | Loss of lower layer connectivity | +| 907 | | X | X | | | | Transmission failure | +| 908 | | Root only
MG only | Root only
MG only | | Root only
MG only | | MG Impending Failure | +| 909 | | | | | Root only
MG only | | MGC Impending Failure | +| 910 | MG only | X | X | | | | Media Capability Failure | +| 911 | MG only | X | X | | | | Modem Capability Failure | +| 912 | MG only | X | X | | | | Mux Capability Failure | +| 913 | MG only | X | X | | | | Signal Capability Failure | +| 914 | MG only | X | X | | | | Event Capability Failure | +| 915 | | X | X | | | | State Loss | +| 916 | X | | | Root only
MG only | Root only
MG only | | Packages Change | + +**Table F.1 – ServiceChangeMethod and ServiceChangeReason mapping** + +| SC Reason | SC Method | | | | | | Description | +|-----------|-----------|--------|----------|----------------------|----------------------|---------|-------------------| +| | Restart | Forced | Graceful | Disconnected | Failover | Handoff | | +| 917 | X | | | Root only
MG only | Root only
MG only | | Capability Change | +| 918 | X | | | | | | Cancel Graceful | +| 919 | | | | | Root only
MG only | | Warm Failover | +| 920 | | | | | Root only
MG only | | Cold Failover | + +### F.5.3 ServiceChangeDelay + +The ServiceChangeDelay is used to provide a delay before the ServiceChange Command takes effect and the ServiceStates Property of the MG or termination(s) is changed. The ServiceChange Command is replied as if execution happened upon receipt of the message, but the MG or termination(s) does not actually change state until the ServiceChangeDelay expires. A ServiceChangeDelay equal to zero is equivalent to no ServiceChangeDelay, with the exception of its combined use with the ServiceChangeMethod "Graceful". See clause F.4 for the effects of ServiceChangeDelay on the various ServiceChangeMethods. + +### F.5.4 ServiceChangeAddress + +The use of the ServiceChangeAddress parameter is described in clause 7.2.8. If the parameter is present, it may only be used with ServiceChange Commands on the Root Termination, and any new transactions shall be sent to the new address and/or port number specified. Replies shall be sent back to the address from which the corresponding request came. + +### F.5.5 ServiceChangeProfile + +The ServiceChangeProfile parameter allows the MGC and MG to negotiate the ITU-T H.248 profile to be used in the control association. The MGC may still audit the MG to determine other supported MG capabilities. ServiceChangeProfile shall only be sent on registration or re-registration commands. + +### F.5.6 ServiceChangeVersion + +ServiceChangeVersion is used to negotiate the ITU-T H.248 protocol version to be used between the MGC and MG. ServiceChangeVersion is mandatory on initial registration, and should be sent on any other registration commands where protocol version negotiation is to take place. ServiceChangeVersion shall not be sent on non-registration commands. See clause F.3.1 for registration procedures. + +### F.5.7 ServiceChangeMgcID + +The use of the ServiceChangeMgcID parameter is described in clause 7.2.8, specifically clause 7.2.8.1.3. The MGC may send this parameter in a ServiceChange Command directed toward the Root Termination. Upon receipt during a registration attempt, the MG shall attempt registration with the MGC at the specified address (see Note). When received in a ServiceChange Handoff Command from the MG's primary MGC, the MG shall utilize the procedures outlined in clause 11.5. + +NOTE – In case of a name format, a name-to-address resolution is implied, see clause 7.2.8.1.3. + +The MGC should not use the ServiceChangeMgcID parameter in a ServiceChange Reply when responding to a ServiceChange Forced or Graceful Command with reason 908. + +The MGC may use the ServiceChangeMgcID parameter in a ServiceChange Reply when responding to a ServiceChange Disconnected with reason 900 (see also clause 8.4 of [b-ITU-T H-Sup.7]). + +### **F.5.8   TimeStamp** + +The use of the optional TimeStamp parameter is described in clause 7.2.8. The TimeStamp parameter has no effect on the execution of ServiceChange Commands, but may be of use to the receiver of the ServiceChange Command for other purposes, such as billing or timing coordination. + +## **F.6       ServiceChange versus TerminationState** + +The ServiceStates Property in the TerminationState Descriptor holds the current value of the state of the termination. ServiceStates may have three values: "InService", "OutOfService", and "Test". + +The MGC shall only use Modify Commands to set the ServiceStates Property to or from Test. All other Modifies of the ServiceStates Property are a violation of protocol, and shall receive Error Code 401 ("Protocol Error"). To change the state from "InService" to "OutOfService" or vice versa, the ServiceChange Command must be used. + +For terminations in the Test state, the MG shall only send ServiceChanges with a ServiceChangeMethod of "Forced" or "Graceful" to the MGC. Subsequent ServiceChange Commands may then set the termination's ServiceState Property to "InService". + +Receivers should make every reasonable attempt to accept ServiceChange Commands, but in some instances rejection of the command is warranted. For example, if an MG sent a ServiceChange Command to bring a termination into service, but the MGC does not have the resources allocated to service that termination due to lack of provisioning or other reason, then the MGC may reject the command. If the receiving entity rejects the ServiceChange Command, the state of the termination remains unchanged. The sender may choose to wait some length of time and try again, or wait for the receiver to attempt to alter the termination state. Requests to take a termination OutOfService should be honoured. + +Table F.2 shows which commands may be used to effect a state change on a termination. + +**Table F.2 – State transition commands and their effects** + +| Current State | New State | Command | MGC Allowed? | MG Allowed? | +|----------------------|------------------|----------------|-----------------------------|--------------------| +| InService | Test | ServiceChange | Not Possible | Not Possible | +| | | Modify | Yes | Not Possible | +| InService | OutOfService | ServiceChange | Yes, physical and Root only | Yes | +| | | Modify | No | Not Possible | +| OutOfService | InService | ServiceChange | Yes, but not on Root | Yes | +| | | Modify | No | Not Possible | +| OutOfService | Test | ServiceChange | Not Possible | Not Possible | +| | | Modify | Yes | Not Possible | +| Test | InService | ServiceChange | No | No | +| | | Modify | Yes | Not Possible | +| Test | OutOfService | ServiceChange | No | Yes | +| | | Modify | Yes | Not Possible | + +# Appendix I + +## Example call flows + +(This appendix does not form an integral part of this Recommendation.) + +All ITU-T H.248.1 implementors must read the normative part of this Recommendation carefully before implementing from it. No one should use the examples in this appendix as stand-alone explanations of how to create protocol messages. + +The examples in this appendix use SDP for encoding of the Local and Remote Descriptors. SDP is defined in [IETF RFC 2327]. If there is any discrepancy between the SDP in the examples and [IETF RFC 2327], the RFC should be consulted for verification. Audio profiles used are those defined in [IETF RFC 3551], and others registered with IANA. For example, ITU-T G.711 A-law is called PCMA in SDP, and is assigned profile 8. ITU-T G.723.1 is called G723 and is profile 4; ITU-T H.263 is called H263 and is profile 34. See also . + +## I.1 Residential gateway to residential gateway call + +This example scenario illustrates the use of the elements of the protocol to set up a Residential Gateway to Residential Gateway call over an IP-based network. For simplicity, this example assumes that both Residential Gateways involved in the call are controlled by the same Media Gateway Controller. + +### I.1.1 Programming residential GW analog line terminations for idle behaviour + +The following illustrates the API invocations from the Media Gateway Controller and Media Gateways to get the terminations in this scenario programmed for idle behaviour. Both the originating and terminating Media Gateways have idle analog line terminations programmed to look for call initiation events (i.e., offhook) by using the Modify Command with the appropriate parameters. The NULL Context is used to indicate that the terminations are not yet involved in a context. The Root Termination is used to indicate the entire MG instead of a termination within the MG. + +In this example, MG1 has the IP address 124.124.124.222, MG2 is 125.125.125.111, and the MGC is 123.123.123.4. The Megaco port is 55555 for all three. + +- 1) An MG registers with an MGC using the ServiceChange Command: + +MG1 to MGC: + +``` +MEGACO/1 [124.124.124.222] +Transaction = 9998 { + Context = - { + ServiceChange = ROOT {Services { + Method=Restart, Version=3, + ServiceChangeAddress=55555, Profile=ResGW/1} + } + } +} +``` + +- 2) The MGC sends a reply: + +MGC to MG1: + +``` +MEGACO/1 [123.123.123.4]:55555 +Reply = 9998 { + Context = - {ServiceChange = ROOT { + Services {ServiceChangeAddress=55555} } } +``` + +} + +- 3) The MGC programs a termination in the NULL Context. The TerminationID is A4444, the streamID is 1, the requestID in the Events Descriptor is 2222. The MID is the identifier of the sender of this message; in this case, it is the IP address and port [123.123.123.4]:55555. The Mode Property for this stream is set to Inactive. "al" is the analog line supervision package. The Local and Remote Descriptors are assumed to be provisioned. + +``` +MGC to MG1: +MEGACO/3 [123.123.123.4]:55555 +Transaction = 9999 { + Context = - { + Modify = A4444 { + Media { Stream = 1 { + LocalControl { + Mode = Inactive, + tdm/gain=2, ; in dB, + tdm/ec=on + }, + } + }, + Events = 2222 {al/of {strict=state}} + } +} +``` + +The dialplan script could have been loaded into the MG previously. Its function would be to wait for the off-hook, turn on dialtone and start collecting DTMF digits. However, in this example, we use the DigitMap, which is put into place after the off-hook is detected (step 5) below). + +Note that the embedded Events Descriptor could have been used to combine steps 3) and 4) with steps 8) and 9), eliminating steps 6) and 7). + +- 4) The MG1 accepts the Modify with this reply: + +``` +MG1 to MGC: +MEGACO/3 [124.124.124.222]:55555 +Reply = 9999 { + Context = - {Modify = A4444} +} +``` + +- 5) A similar exchange happens between MG2 and the MGC, resulting in an idle termination called A5555. + +### I.1.2 Collecting originator digits and initiating termination + +The following builds upon the previously shown conditions. It illustrates the transactions from the Media Gateway Controller and originating Media Gateway (MG1) to get the originating termination (A4444) through the stages of digit collection required to initiate a connection to the terminating Media Gateway (MG2). + +- 6) MG1 detects an off-hook event from User 1 and reports it to the Media Gateway Controller via the Notify Command. + +``` +MG1 to MGC: +MEGACO/3 [124.124.124.222]:55555 +Transaction = 10000 { + Context = - { + Notify = A4444 {ObservedEvents =2222 { + 19990729T22000000:al/of{init=OFF}}} + } +} +``` + +7) And the Notify is acknowledged. + +``` +MGC to MG1: +MEGACO/3 [123.123.123.4]:55555 +Reply = 10000 { + Context = - {Notify = A4444} +} +``` + +8) The MGC modifies the termination to play dial tone, to look for digits according to Dialplan0 and to look for the on-hook event now. + +``` +MGC to MG1: +MEGACO/3 [123.123.123.4]:55555 +Transaction = 10001 { + Context = - { + Modify = A4444 { + Events = 2223 { + al/on{strict=state}, dd/ce {DigitMap=Dialplan0} + }, + Signals {cg/dt}, + DigitMap= Dialplan0{ +(0| 00|[1-7]xxx|8xxxxxxx|Fxxxxxxx|Exx|91xxxxxxxxxxx|9011x.)} + } + } + } +} +``` + +9) And the Modify is acknowledged. + +``` +MG1 to MGC: +MEGACO/3 [124.124.124.222]:55555 +Reply = 10001 { + Context = - {Modify = A4444} +} +``` + +10) Next, digits are accumulated by MG1 as they are dialled by User 1. Dialtone is stopped upon detection of the first digit. When an appropriate match is made of collected digits against the currently programmed dialplan for A4444, another Notify is sent to the Media Gateway Controller. + +``` +MG1 to MGC: +MEGACO/3 [124.124.124.222]:55555 +Transaction = 10002 { + Context = - { + Notify = A4444 {ObservedEvents =2223 { + 19990729T22010001:dd/ce{ds="916135551212",Meth=UM}}} + } + } +} +``` + +11) And the Notify is acknowledged. + +``` +MGC to MG1: +MEGACO/3 [123.123.123.4]:55555 +Reply = 10002 { + Context = - {Notify = A4444} +} +``` + +12) The controller then analyses the digits and determines that a connection needs to be made from MG1 to MG2. Both the physical termination A4444, and an ephemeral termination are added to a new context in MG1. Mode is RecvOnly since Remote Descriptor values are not yet specified. Preferred codecs are in the MGC's preferred order of choice. + +``` +MGC to MG1: +MEGACO/3 [123.123.123.4]:55555 +Transaction = 10003 { +``` + +``` + +Context = $ { + Add = A4444 { LocalControl { + Mode = SendRecv } }, + Add = $ { + Media { + Stream = 1 { + LocalControl { + Mode = RecvOnly, + nt/jit=40 ; in ms + }, + Local { +v=0 +c=IN IP4 $ +m=audio $ RTP/AVP 4 +a=ptime:30 +v=0 +c=IN IP4 $ +m=audio $ RTP/AVP 0 + } + } + } + } +} + +``` + +NOTE – The MGC states its preferred parameter values as a series of SDP blocks in Local. The MG fills in the Local Descriptor in the Reply. + +13) MG1 acknowledges the new termination and fills in the Local IP address and UDP port. It also makes a choice for the codec based on the MGC preferences in Local. MG1 sets the RTP port to 2222. + +``` + +MEGACO/3 [124.124.124.222]:55555 +Reply = 10003 { + Context = 2000 { + Add = A4444, + Add=A4445{ + Media { + Stream = 1 { + Local { +v=0 +o=- 2890844526 2890842807 IN IP4 124.124.124.222 +s=- +c=IN IP4 124.124.124.222 +t= 0 0 +m=audio 2222 RTP/AVP 4 +a=ptime:30 + } ; RTP profile for G.723.1 is 4 + } + } + } + } +} + +``` + +14) The MGC will now associate A5555 with a new context on MG2, and establish an RTP Stream (i.e., A5556 will be assigned), SendRecv connection through to the originating user, User 1. The MGC also sets ring on A5555. + +``` + +MGC to MG2: +MEGACO/3 [123.123.123.4]:55555 +Transaction = 50003 { + Context = $ { + Add = A5555 { Media { + +``` + +196 **Rec. ITU-T H.248.1 (03/2013)** + +``` + + Stream = 1 { + LocalControl {Mode = SendRecv} }, + Events=1234{al/of{strict=state}}, + Signals {al/ri} + }, + Add = $ {Media { + Stream = 1 { + LocalControl { + Mode = SendRecv, + nt/jit=40 ; in ms + }, + Local { +v=0 +c=IN IP4 $ +m=audio $ RTP/AVP 4 +a=ptime:30 + }, + Remote { +v=0 +c=IN IP4 124.124.124.222 +m=audio 2222 RTP/AVP 4 +a=ptime:30 + } ; RTP profile for G.723.1 is 4 + } + } + } +} +} +} + +``` + +15) This is acknowledged. The stream port number is different from the control port number. In this case it is 1111 (in SDP). + +``` + +MG2 to MGC: +MEGACO/3 [125.125.125.111]:55555 +Reply = 50003 { + Context = 5000 { + Add = A5555, + Add = A5556{ + Media { + Stream = 1 { + Local { +v=0 +o=- 7736844526 7736842807 IN IP4 125.125.125.111 +s=- +c=IN IP4 125.125.125.111 +t= 0 0 +m=audio 1111 RTP/AVP 4 + } + } ; RTP profile for G.723.1 is 4 + } + } + } +} +} +} +} + +``` + +16) The above IPAddr and UDPport need to be given to MG1 now. + +``` + +MGC to MG1: +MEGACO/3 [123.123.123.4]:55555 +Transaction = 10005 { + Context = 2000 { + Modify = A4444 { + Signals {cg/rt} + }, + Modify = A4445 { + +``` + +``` + +Media { + Stream = 1 { + Remote { +v=0 +o=- 7736844526 7736842807 IN IP4 125.125.125.111 +s=- +c=IN IP4 125.125.125.111 +t= 0 0 +m=audio 1111 RTP/AVP 4 + } + } ; RTP profile for G.723.1 is 4 + } +} + +``` + +MG1 to MGC: + +``` + +MEGACO/3 [124.124.124.222]:55555 +Reply = 10005 { + Context = 2000 {Modify = A4444, Modify = A4445} +} + +``` + +- 17) The two gateways are now connected and User 1 hears the ringback. The MG2 now waits until User2 picks up the receiver and then the two-way call is established. + +From MG2 to MGC: + +``` + +MEGACO/3 [125.125.125.111]:55555 +Transaction = 50005 { + Context = 5000 { + Notify = A5555 {ObservedEvents =1234 { + 19990729T22020002:al/of{init=off}}} + } +} + +``` + +From MGC to MG2: + +``` + +MEGACO/3 [123.123.123.4]:55555 +Reply = 50005 { + Context = - {Notify = A5555} +} + +``` + +From MGC to MG2: + +``` + +MEGACO/3 [123.123.123.4]:55555 +Transaction = 50006 { + Context = 5000 { + Modify = A5555 { + Events = 1235 {al/on{strict=state}}, + Signals ; to turn off ringing + } + } +} + +``` + +From MG2 to MGC: + +``` + +MEGACO/3 [125.125.125.111]:55555 +Reply = 50006 { + Context = 5000 {Modify = A4445} +} + +``` + +- 18) Change mode on MG1 to SendRecv, and stop the ringback. + +MGC to MG1: + +``` + +MEGACO/3 [123.123.123.4]:55555 +Transaction = 10006 { + Context = 2000 { + Modify = A4445 { + Media { + Stream = 1 { + LocalControl { + Mode=SendRecv + } + } + } + } + }, + Modify = A4444 { + Signals + } +} +} + +``` + +from MG1 to MGC: + +``` + +MEGACO/3 [124.124.124.222]:55555 +Reply = 10006 { + Context = 2000 {Modify = A4445, Modify = A4444}} + +``` + +19) The MGC decides to Audit the RTP termination on MG2. + +``` + +MEGACO/3 [123.123.123.4]:55555 +Transaction = 50007 { + Context = 5000 {AuditValue = A5556{ + Audit{Media, DigitMap, Events, Signals, Packages, Statistics }} + } +} + +``` + +20) The MG2 replies. + +``` + +MEGACO/3 [125.125.125.111]:55555 +Reply = 50007 { + Context = 5000 { + AuditValue = A5556 { + Media { + TerminationState { ServiceStates = InService, + Buffer = OFF }, + Stream = 1 { + LocalControl { Mode = SendRecv, + nt/jit=40 }, + Local { +v=0 +o=- 7736844526 7736842807 IN IP4 125.125.125.111 +s=- +c=IN IP4 125.125.125.111 +t= 0 0 +m=audio 1111 RTP/AVP 4 +a=ptime:30 + }, + Remote { +v=0 +o=- 2890844526 2890842807 IN IP4 124.124.124.222 +s=- +c=IN IP4 124.124.124.222 +t= 0 0 +m=audio 2222 RTP/AVP 4 +a=ptime:30 + } } }, + DigitMap, + Events, + Signals, + } + } + } +} + +``` + +``` + + Packages {nt-1, rtp-1}, + Statistics { rtp/ps=1200, ; packets sent + nt/os=62300, ; octets sent + rtp/pr=700, ; packets received + nt/or=45100, ; octets received + rtp/pl=0.2, ; % packet loss + rtp/jit=20, + rtp/delay=40 } ; avg latency + } + } +} + +``` + +- 21) When the MGC receives an on-hook signal from one of the MGs, it brings down the call. In this example, the user at MG2 hangs up first. + +From MG2 to MGC: + +``` + +MEGACO/3 [125.125.125.111]:55555 +Transaction = 50008 { + Context = 5000 { + Notify = A5555 {ObservedEvents =1235 { + 19990729T24020002:al/on{init=off}} + } + } +} + +``` + +From MGC to MG2: + +``` + +MEGACO/3 [123.123.123.4]:55555 +Reply = 50008 { + Context = - {Notify = A5555} +} + +``` + +- 22) The MGC now sends both MGs a Subtract to take down the call. Only the Subtract Commands to MG2 are shown here. Each termination has its own set of statistics that it gathers. An MGC may not need to request both to be returned. A5555 is a physical termination, and A5556 is an RTP termination. + +From MGC to MG2: + +``` + +MEGACO/3 [123.123.123.4]:55555 +Transaction = 50009 { + Context = 5000 { + Subtract = A5555 {Audit{Statistics}}, + Subtract = A5556 {Audit{Statistics}} + } +} + +``` + +From MG2 to MGC: + +``` + +MEGACO/3 [125.125.125.111]:55555 +Reply = 50009 { + Context = 5000 { + Subtract = A5555 { + Statistics { + nt/os=45123, ; Octets Sent + nt/or=45123, ; Octets Received + nt/dur=40000 ; in milliseconds + } + }, + Subtract = A5556 { + Statistics { + +``` + +``` + + rtp/ps=1245, ; packets sent + nt/os=62345, ; octets sent + rtp/pr=780, ; packets received + nt/or=45123, ; octets received + rtp/pl=10, ; % packets lost + rtp/jit=27, + rtp/delay=48, ; average latency + nt/dur=38000 ; in millisecond + } +} +} +} + +``` + +- 23) The MGC now sets up both MG1 and MG2 to be ready to detect the next off-hook event. (See step 1). Note that this could be the default state of a termination in the NULL context, and if this were the case, no message need be sent from the MGC to the MG. Once a termination returns to the NULL context, it goes back to the default termination values for that termination. + +# Appendix II + +## ITU-T H.248 Package template + +(This appendix does not form an integral part of this Recommendation.) + +New and updated ITU-T H.248 packages should be defined using the following template. It is in an ITU Recommendation format. Editors from non-ITU organizations should, at a minimum, use the structures in clause 6 of the template. The ITU-T H.248 packages keywords are indicated in bold. Sections to be filled in are indicated by "< >". For detailed information on how to create a new package, see clause 12. + +NOTE – Package specific error codes require IANA registration. Error Code assignment shall follow the same rules as described in clause 4.1 of [ITU-T H.248.8], "*Assigning Error Codes*". + +## **Recommendation ITU-T H.248.** + +## **Gateway Control Protocol: Packages** + +### **1 Scope** + + + +## **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (), *Gateway Control Protocol: Version< x>*. + + + +### **3 Definitions** + +### **3.1 Terms defined elsewhere** + +This Recommendation uses the following terms defined elsewhere: + + / + +### **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + + / + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + + + +## 5 Conventions + + + +## 6 + +NOTE – The ID value of Packages, Properties, Events, Parameters, Signals, etc. are designated below by "textID" (a string representing its text ID) and by "0x???" (the ID hexadecimal representation). + +**Package name:** +**Package ID:** +**Description:** +**Version:** +**Extends:** + +### 6.1 Properties + +#### 6.1.1 + +**Property name:** +**Property ID:** +**Description:** +**Type:** +**Possible values:** +**Default:** +**Defined in:** +**Characteristics:** + +### 6.2 Events + +#### 6.2.1 + +**Event name:** +**Event ID:** +**Description:** + +##### 6.2.1.1 EventsDescriptor parameters + +###### 6.2.1.1.1 + +**Parameter name:** +**Parameter ID:** +**Description:** +**Type:** +**Optional:** +**Possible values:** +**Default:** + +##### 6.2.1.2 ObservedEventsDescriptor parameters + +###### 6.2.1.2.1 + +**Parameter name:** +**Parameter ID:** +**Description:** +**Type:** +**Optional:** +**Possible values:** +**Default:** + +### 6.3 Signals + +#### 6.3.1 + +**Signal name:** +**Signal ID:** +**Description:** +**Signal Type:** +**Duration:** + +##### 6.3.1.1 Additional parameters + +###### 6.3.1.1.1 + +**Parameter name:** +**Parameter ID:** +**Description:** +**Type:** +**Optional:** +**Possible values:** +**Default:** + +### 6.4 Statistics + +#### 6.4.1 + +**Statistic name:** +**Statistic ID:** +**Description:** +**Type:** +**Possible values:** +**Level:** + +### 6.5 Error Codes + +#### 6.5.1 + +**Error Code #:** + +**Name:** + +**Definition:** + +**Error text in the Error Descriptor:** + +**Comment:** + +### 6.6 Procedures + + + +# Appendix III + +## ITU-T H.248 profile definition template + +(This appendix does not form an integral part of this Recommendation.) + +New ITU-T H.248 profiles should be defined using the following profile template. It is in an ITU-T Recommendation format. Editors from non-ITU organizations should, at a minimum, use the structures in clause 6 below. If this template format is not used, then editors of profiles should ensure that the headings and points in this appendix are covered by their profile. + +## Support of profile elements + +The headings in the structure below represent items that may be considered as optional. For profile definitions, a certain ITU-T H.248.1 item may be unused despite being mandatory in ITU-T H.248.1; these items are also included in the structure below. Non-listed items are to be considered mandatory by the ITU-T H.248.1 protocol. In the profile template below, elements can be defined as "optional" or "mandatory". "Optional" means that it is optional for either the sender or the receiver to include the element in a message. + +The MGC may use the ITU-T H.248 packages audit mechanism to determine which of the optional packages are supported by the MG. + +Within each of the cited (mandatory and optional) packages, individual properties, signals, events or statistics are tagged as being optional or mandatory. The interpretation of this categorization in this profile is as follows:- + +- Any property, signal, event or statistic that is tagged as mandatory in a mandatory package must be supported by the MG. Such properties, signals, events and statistics may optionally be used by the MGC. +- Any property, signal, event or statistic that is tagged as mandatory in an optional package must be supported by the MG if the MG supports that optional package. As the MGC is the master, it determines when properties/signals/events and statistics are set on the MG and as such, properties, signals and events may optionally be used by the MGC. +- Any property, signal, event or statistic that is tagged as optional in a mandatory or optional package may be supported by the MG if the MG supports that package. Such properties, signals and events may optionally be used by the MGC. Should the MGC attempt to use such an unsupported optional property/signal/event/statistic, the MG shall respond with error code 501 (Not Implemented). If the MGC receives statistics that are not understood, then they are ignored. + +Where the cited properties, events, signals and statistics have associated parameters, such parameters are also tagged as being mandatory or optional. Where a parameter is designated in the Package description to be "Optional: No" the Profile definition shall not specify this parameter to be "Optional". The interpretation of this categorization in this profile is as follows: + +- any parameter that is tagged as mandatory may be included by the sending entity and must be supported by the receiving entity; +- any parameter that is tagged as optional may be included by the sending entity and may be supported by the receiving entity. If the receiving entity receives an optional element that it has not implemented as per clause 6.2.3, it should send Error Code 501 ("Not Implemented"). + +The editor should provide written description in each of the subclauses below if it furthers clarifies ITU-T H.248.1 behaviour. For example, if the Move Command (see clause 6.8.4) is limited to certain termination types, this should be indicated. + +Italics text is to be removed. + + in brackets is to be filled in. + +### **Recommendation ITU-T ** + +### **** + +### **1 Scope** + + + +### **2 References** + + + +### **3 Definitions** + +#### **3.1 Terms defined elsewhere** + +This Recommendation uses the following terms defined elsewhere: + + / + +### **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + + / + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations: + + + +### **5 Conventions** + + + +## **6 Profile description** + +### **6.1 Profile identification** + +| | | +|---------------|------------------------| +| Profile name: | | +| Version: | | + +*The name and version of the profile that is sent in the ServiceChange Command.* + +### **6.2 Summary** + + + +*A description of what the profile is.* + +### 6.3 Gateway Control Protocol version + + + +*The minimum ITU-T H.248 version required to support the profile. This should be based upon base syntax support and not an arbitrary version assignment. This is related to the ServiceChangeVersion in clause 6.8.8.* + +### 6.4 Connection model + + + +*A description of the allowed termination configurations in a context.* + +| | | +|------------------------------------------------------------|---------------------------------------------------------| +| Maximum number of contexts: | | +| Maximum number of terminations per context: | | +| Allowed termination type combinations in a context: | | + +### 6.5 Context attributes + +| Context attribute | Supported | Values supported | +|------------------------------------|------------------|-----------------------------------------------------------------| +| Topology | | See 6.7.8 | +| Priority Indicator | | <1-15> | +| Emergency Indicator | | NA | +| IEPS call indicator | | NA | +| ContextAttribute Descriptor | | If "Yes", see clause 6.8.9 for details of supported attributes. | +| ContextIDList Parameter | | NA | + +*Is the AND/OR Select operation Context Attribute supported?* + +| | | | +|---------------------------------|----------|---------------| +| AND/OR Context Attribute | | | +|---------------------------------|----------|---------------| + +### 6.6 Terminations + +#### 6.6.1 Termination names + + + +*Identify the termination identities associated with physical, ephemeral and multiplex terminations.* + +#### 6.6.2 Multiplexed terminations + +| | | +|------------------------------------------|----------| +| Multiplex terminations supported? | | +|------------------------------------------|----------| + +*If yes, then:* + +| | | +|---------------------------------------------------------------|---------------------------------------| +| Multiplex types supported: | < H.221, H.223, H.226, V.76, N × 64K> | +| Maximum number of terminations connected to multiplex: | | + +*Are multiplexed terminations used? If so, describe.* + +### 6.7 Descriptors + +#### 6.7.1 Stream Descriptor + +| | | | +|-------------------------------------------------------|-------------------|-----------| +| Maximum number of streams per termination type | | | +|-------------------------------------------------------|-------------------|-----------| + +*If more than 1:* + +| | | +|------------------------------|------------------------------------------------------------------------------------| +| Stream configuration: | | +|------------------------------|------------------------------------------------------------------------------------| + +##### 6.7.1.1 LocalControl Descriptor + +*Are the ReserveGroup and ReserveValue properties used?* + +| If not generic, list appropriate termination and stream types. | | Termination type | Stream type | +|-----------------------------------------------------------------------|----------|-------------------------|--------------------| +| ReserveGroup used: | | | | +| ReserveValue used: | | | | + +*Which StreamMode values are used?* + +| Termination type | Stream type | Allowed StreamMode values | +|-------------------------|--------------------|------------------------------------------| +| | | | + +#### 6.7.2 Events Descriptor + +*All events contained in this profile may be set on any termination/stream [with the following exceptions].* + +*NOTE – The text in [] is optional and only included if there are such exceptions.* + +| | | | | +|---------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------|---------------------------------------------------| +| Events settable on termination types and stream types: | | | | +| If yes | EventID | Termination type | Stream type | +| | | | | + +*Is EventBuffer Control used?* + +| | | +|----------------------------------|----------| +| EventBuffer Control used: | | +|----------------------------------|----------| + +*Is event KeepActive used?* + +| | | +|-----------------------------------|----------| +| KeepActive used on events: | | +|-----------------------------------|----------| + +*Is embedding in Events used?* + +| | | +|-------------------------------------------------|----------| +| Embedded events in an Events Descriptor: | | +|-------------------------------------------------|----------| + +| | | +|--------------------------------------------------|----------| +| Embedded signals in an Events Descriptor: | | +|--------------------------------------------------|----------| + +*Are Regulated EmbeddedEvents Supported?* + +| | | +|----------------------------------------------------|---------------------------------| +| Regulated Embedded events are triggered on: | | +|----------------------------------------------------|---------------------------------| + +*Is the ResetEventsDescriptor Flag used?* + +| | | +|------------------------------------------------|-------------------------------------| +| ResetEventsDescriptor used with events: | | +|------------------------------------------------|-------------------------------------| + +*What Notification Behaviour is supported?* + +| | | +|-------------------------|---------------------------------------------| +| NotifyImmediate: | | +| NotifyRegulated: | | +| NeverNotify: | | + +#### 6.7.3 EventBuffer Descriptor + +*Is this supported?* + +| | | | +|-------------------------------------|-----------------|--------------------------------------------------------------------------------------| +| EventBuffer Descriptor used: | | | +| If yes | EventIDs | | + +#### 6.7.4 Signals Descriptor + +*All signals contained in this profile may be set on any termination/stream [with the following exceptions].* + +*NOTE – The text in [] is optional and only included if there are such exceptions.* + +| | | | | +|-----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------------------------------------| +| The setting of signals is dependent on termination or streams types: |
NOTE – "No" means that all signals can be played on any termination or stream. If "Yes", any signal not listed below may be played on any termination or stream. | | | +| If yes | SignalID | Termination Type | Stream Type/ID | +| | | | | + +*Are signal lists supported? If supported, what is the maximum number of signals per list per termination/stream type supporting lists.* + +| | | | +|---------------------------------|----------------------------------------------------|------------| +| Signals Lists supported: | | | +| If yes | Termination Type Supporting Lists: | | +| | Stream Type Supporting lists: | | +| | Maximum number of signals to a signal list: | | +| | Intersignal delay parameter supported: | | + +*Is overriding signal type and duration supported?* + +| | | | +|--------------------------------------------|---------------------------------------------------------------------------------|----------------------------------| +| Signal type and duration supported: | | | +| If yes | SignalID | Type or duration override | +| | | | + +*Is Signal Direction supported?* + +| | | +|------------------------------------|----------| +| Signal Direction supported: | | +|------------------------------------|----------| + +*Is "notifyCompletion" supported? What types are supported? Is the RequestID used with "NotifyCompletion"?* + +| | | | +|---------------------------------------|-------------------------------------------------------------------------------|-------------------------------------| +| NotifyCompletion supported: | | | +| If yes | SignalID | Type of completion supported | +| | | | +| RequestID Parameter supported: | | | + +*Can multiple signals be played simultaneously?* + +| | | | +|---------------------------------------|-----------------------------------------------------|-------------------------------------------------------------------------------| +| Signals played simultaneously: | | | +| If yes | SignalIDs that can be played simultaneously: | | + +*Is "KeepActive" supported for signals?* + +| | | +|------------------------------------|----------| +| KeepActive used on signals: | | +|------------------------------------|----------| + +#### 6.7.5 DigitMap Descriptor + +*Are DigitMaps supported? If so describe the names, structures and timers.* + +| | | | | +|-----------------------------|----------------------|------------------|---------------| +| DigitMaps supported: | | | | +| If yes | DigitMap name | Structure | Timers | +| | | | | + +#### 6.7.6 Statistics Descriptor + +*Are statistics supported on terminations, streams or both?* + +| | | +|---------------------------------|---------------------------| +| Statistics supported on: | | +|---------------------------------|---------------------------| + +*Are statistics to be reported?* + +| | | | +|-----------------------------------------|-------------------------------|-----------------------------------------------------------------------------------| +| Statistics reported on Subtract: | | | +| If yes | StatisticIDs reported: | | + +#### 6.7.7 ObservedEvents Descriptor + +*Is the detection time supported?* + +| | | +|----------------------------------------|----------| +| Event detection time supported: | | +|----------------------------------------|----------| + +#### 6.7.8 Topology Descriptor + +*If used what are the allowed settings?* + +| | | +|------------------|--------------------------| +| Allowed triples: | <(T1, T2, oneway), etc.> | +|------------------|--------------------------| + +#### 6.7.9 Error Descriptor + +*Which ITU-T H.248.8 and package defined error codes are supported?* + +**Error Codes sent by the MGC:** + +| | | +|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| Supported ITU-T H.248.8 Error Codes: | | +| Supported Error Codes defined in packages: | For a list of error codes see clause 6.14.x
| + +**Error Codes sent by the MG:** + +| | | +|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| Supported ITU-T H.248.8 Error Codes: | | +| Supported Error Codes defined in packages: | For a list of error codes see clause 6.14.x
| + +#### 6.7.10 TerminationState Descriptor + +*What values of TerminationState are supported?* + +| | | +|----------------------------------------------|-------------------------------| +| TerminationState : ServiceStates | | +| TerminationState : EventBufferControl | | + +*For other package defined Termination State Properties see clause 6.14.* + +### 6.8 Command API + +*NOTE – It is assumed that an Error Descriptor may be returned in any command reply.* + +#### 6.8.1 Add + +*What descriptors can be used in an Add request?* + +| | | +|-----------------------------------------|-------------------------------------------------------------| +| Descriptors used by Add request: | | +|-----------------------------------------|-------------------------------------------------------------| + +*What descriptors can be used in an Add reply?* + +| | | +|---------------------------------------|-------------------------------------------------------------------------| +| Descriptors used by Add reply: | | +|---------------------------------------|-------------------------------------------------------------------------| + +#### 6.8.2 Modify + +*What descriptors can be used in a Modify request?* + +| | | +|--------------------------------------------|-------------------------------------------------------------| +| Descriptors used by Modify request: | | +|--------------------------------------------|-------------------------------------------------------------| + +*What descriptors can be used in a Modify reply?* + +| | | +|------------------------------------------|-------------------------------------------------------------| +| Descriptors used by Modify reply: | | +|------------------------------------------|-------------------------------------------------------------| + +#### 6.8.3 Subtract + +*Can an Audit Descriptor be used in a Subtract request?* + +| | | +|----------------------------------------------|---------| +| Descriptors used by Subtract request: | | +|----------------------------------------------|---------| + +*Can a Statistics Descriptor be used in a Subtract reply?* + +| | | +|--------------------------------------------|--------------| +| Descriptors used by Subtract reply: | | +|--------------------------------------------|--------------| + +#### 6.8.4 Move + +*Is the Move command used? Some context configurations may not use this.* + +| | | +|---------------------------|----------| +| Move command used: | | +|---------------------------|----------| + +*If used:* + +| | | +|------------------------------------------|-------------------------------------------------------------------------| +| Descriptors used by Move request: | | +| Descriptors used by Move reply: | | + +#### 6.8.5 AuditValue + +*Which descriptors and/or individual properties, signal, events or statistics can be audited?* + +| | | | +|---------------------------------|--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------| +| Audited Properties: | | | +| Audited Statistics: | | | +| Audited Signals: | | | +| Audited Events: | | | +| Packages Audit possible: | Can the Package Descriptor be audited?
| | + +#### 6.8.6 AuditCapability + +*Which descriptors and/or individual properties, signal, events or statistics can be audited?* + +| | | | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------| +| Audited Properties: | | | +| Audited Statistics: | | | +| Audited Signals: | | | +| Audited Events: | | | + +*Is scoped auditing possible?* + +| | | +|----------------------------------------------------------------------|-------------------------------| +| Audited Properties/ContextAttributes used for a scoped audit: | | +|----------------------------------------------------------------------|-------------------------------| + +#### 6.8.7 Notify + +*Which descriptors can be used in a Notify request?* + +| | | +|--------------------------------------------|-------------------------| +| Descriptors used by Notify request: | | +|--------------------------------------------|-------------------------| + +*What descriptors can be used in a Notify reply?* + +| | | +|------------------------------------------|---------| +| Descriptors used by Notify reply: | | +|------------------------------------------|---------| + +#### 6.8.8 ServiceChange + +*Which ServiceChangeMethods and Reasons are supported?* + +**ServiceChangeMethods and ServiceChangeReasons sent by MGC:** + +| ServiceChangeMethods supported: | ServiceChangeReasons supported: | +|-------------------------------------------------------------|----------------------------------------| +| | < 900-920 > | + +**ServiceChangeMethods and ServiceChangeReasons sent by MG:** + +| ServiceChangeMethods supported: | ServiceChangeReasons supported: | +|---------------------------------------------------------------------------|----------------------------------------| +| | < 900-920 > | + +*Is ServiceChangeAddress used?* + +| | | +|-----------------------------------|----------| +| ServiceChangeAddress used: | | +|-----------------------------------|----------| + +*Is ServiceChangeMgcId used?* + +| | | +|---------------------------------|----------| +| ServiceChangeMgcId used: | | +|---------------------------------|----------| + +*Is ServiceChangeDelay used?* + +| | | | +|---------------------------------|---------------------------|----------| +| ServiceChangeDelay used: | | | +| If yes | Valid time period: | <0-x> ms | + +*Is ServiceChangeIncomplete Flag used?* + +| | | +|--------------------------------------------|----------| +| ServiceChange Incomplete Flag used: | | +|--------------------------------------------|----------| + +*Which version of Recommendation ITU-T H.248.1 is used by ServiceChangeVersion? The lowest value here should be the minimum version defined in 6.3.* + +| | | +|----------------------------------------------|-----------| +| Version used in ServiceChangeVersion: | <1, 2, 3> | +|----------------------------------------------|-----------| + +*Is the ServiceChangeProfile parameter mandatory?* + +| | | +|----------------------------------------|----------| +| ServiceChangeProfile mandatory: | | +|----------------------------------------|----------| + +*Can multiple profiles be supported according to Recommendation ITU-T H.248.18?* + +| | | +|--------------------------------------------------------|----------| +| Profile negotiation as per Rec. ITU-T H.248.18: | | +|--------------------------------------------------------|----------| + +#### 6.8.9 Manipulating and auditing context attributes + +*Which Context Attributes may be manipulated and/or audited?* + +| | | +|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| Context Attributes manipulated: | | +| Context Attributes audited: | | + +## 6.9 Generic command syntax and encoding + +*Specifies what encodings are supported by the profile.* + +| | | +|---------------------------------------------------------------------|---------------------------------| +| Supported encodings: | | +| If binary encoding, is indefinite length encoding supported: | | + +## 6.10 Transactions + +*What is the maximum number of TransactionRequest/TransactionReplies per message?* + +| | | +|----------------------------------------------------------------------------------------------------------------------|-----------| +| Maximum number of TransactionRequests/TransactionReplies/TransactionResponseAcks/Segment Replies per message: | | +|----------------------------------------------------------------------------------------------------------------------|-----------| + +*What is the maximum number of commands per TransactionRequest?* + +| | | +|-----------------------------------------------------------|-----------| +| Maximum number of commands per TransactionRequest: | | +|-----------------------------------------------------------|-----------| + +*What is the maximum number of commands per TransactionReply?* + +| | | +|---------------------------------------------------------|-----------| +| Maximum number of commands per TransactionReply: | | +|---------------------------------------------------------|-----------| + +*Can commands be marked "Optional"? Describe.* + +| | | +|-----------------------------------------------|--------------------------------------------------------------------------------------| +| Commands able to be marked "Optional": | | +|-----------------------------------------------|--------------------------------------------------------------------------------------| + +*Can commands be marked for wildcarded response?* + +| | | +|---------------------------------------------------|--------------------------------------------------------------------------------------| +| Wildcarded responses may be requested for: | | +|---------------------------------------------------|--------------------------------------------------------------------------------------| + +*And/or, describe which commands and the procedures surrounding the use of wildcarded responses with those commands.* + +| | | +|----------------------------------------------------------|---------------------------------------------------------------| +| Procedures that make use of wildcarded responses: | | +|----------------------------------------------------------|---------------------------------------------------------------| + +*Specify the values of the transaction timers* + +| Transaction timer: | Value | +|------------------------------------------|----------------------------| +| normalMGExecutionTime | | +| normalMGCExecutionTime | | +| MGOriginatedPendingLimit | | +| MGCOriginatedPendingLimit | | +| MGProvisionalResponseTimerValue | | +| MGCPProvisionalResponseTimerValue | | + +## 6.11 Messages + +*MGC/MG Naming Conventions: MID addressing associated with the names of the MGC/MG.* + + + +*Indicate the maximum number of transactions per message (this table may be omitted if not significant)* + +| | | +|----------------------------------------------------|------------| +| Maximum number of transactions per message: | | +|----------------------------------------------------|------------| + +## 6.12 Transport + +Specifies what H.248 subseries transports are supported by the profile. + +| | | +|------------------------------|-------------------------------------------------| +| Supported transports: | | +|------------------------------|-------------------------------------------------| + +*Is segmentation supported and if so by which method?* + +| | | +|--------------------------------|-------------------------------------------------| +| Segmentation supported: | | +|--------------------------------|-------------------------------------------------| + +*Is control association monitoring (see clause 11.6) used and if so by which method?* + +| | | +|--------------------------------------------------|-------------------------------------------------------------------------| +| Control Association Monitoring supported: | | +|--------------------------------------------------|-------------------------------------------------------------------------| + +## 6.13 Security + +*Specifies the security mechanisms used.* + +| | | +|----------------------------|----------------------------------| +| Supported security: | | +|----------------------------|----------------------------------| + +### 6.14 Packages + +*Specifies the packages that are supported in this profile.* + +*Mandatory: specifies the packages that shall be supported in this profile.* + +| Mandatory packages: | | | | +|----------------------------|------------------|----------------|------------------------------------| +| Package name | PackageID | Version | Termination Types Supported | +| | | <1, 2, 3, ...> | | + +*Optional: specifies the packages that may be supported in the profile.* + +| Optional packages: | | | | | +|---------------------------|------------------|----------------|------------------------------|------------------------------------| +| Package name | PackageID | Version | Support dependent on: | Termination Types Supported | +| | | <1, 2, 3, ...> | | | + +#### Package usage information + +*This table specifies how the packages above will be used. For example:* + +- it lists whether the properties/signals/events/statistics are optional or mandatory;* +- if the value of the property/signal/event provisioned should be specified (e.g., names and number of cycles for an [b-ITU-T H.248.7] announcement);* + +*Specifies the values of properties which are specified as provisioned.* + +#### Package usage information + +#### 6.14.x + +| Properties | Mandatory/Optional | Used in command: | Supported values: | Provisioned value: | Termination/Stream Types Supported: | | | +|------------------------------------------------------------------------------|---------------------------------|--------------------------------------------------|--------------------------|------------------------------------|--------------------------------------------|--|--| +| | | | | | | | | +| Signals | Mandatory/Optional | Used in command: | | Duration provisioned value: | | | | +| | | | | | | | | +| | Signal parameters | Mandatory/Optional | Supported values: | Provisioned value: | | | | +| | | | | | | | | +| Events | Mandatory/Optional | Used in command: | | | | | | +| | | | | | | | | +| | Event parameters | Mandatory/Optional | Supported values: | Provisioned value: | | | | +| | | | | | | | | +| | ObservedEvent parameters | Mandatory/Optional | Supported values: | Provisioned value: | | | | +| | | | | | | | | +| Statistics | Mandatory/Optional | Used in command: | Supported values: | | Termination/Stream Types Supported: | | | +| | | | | | | | | +| Error Codes | Mandatory/Optional | | | | | | | +| | | | | | | | | + +*Additional restrictions may be tabulated as the user desires.* + +### 6.15 Mandatory support of SDP and Annex C information elements + +*Specifies what SDP attributes and Annex C information elements are to be supported.* + +| Supported Annex C and SDP information elements: | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------| +| Information Element | Annex C Support | SDP Support (Note) | +| | | | +| NOTE – Information elements very often map to various lines and their fields in SDP. The profile should specify which SDP lines and fields are mandatory to support.
Discuss in detail the usage scenarios of the mandatory information elements. | | | + +### 6.16 Optional support of SDP and Annex C information elements + +*Specifies what SDP attributes and Annex C information elements may be supported.* + +| Optional Annex C and SDP information elements: | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|------------------------------| +| Information Element | Annex C Support | SDP Support (Note) | Support Dependent on: | +| | | | | +| NOTE – Information elements very often map to various lines and their fields in SDP. The profile should specify which SDP lines and fields are mandatory to support.
Discuss in detail the usage scenarios of the mandatory information elements. | | | | + +### 6.17 Procedures + +*Specifies the procedures that are associated with the profile.* + +*It is recommended that the procedures take the following format:* + +#### 6.17.1 + +*When the procedure is required, the following is initiated.* + +An command is sent from the to the with the following information. + +< Insert information in an appropriate format. For example, the descriptors, property, signal, event, statistic names or an abstraction of the actual parameters in terms of information elements.> + +Upon reception of the command, the shall: + +- + +Upon completion of processing command (1) an command is sent from the to the with the following information. + +< Insert information in an appropriate format. For example, the descriptors, property, signal, event, statistic names or an abstraction of the actual parameters in terms of information elements.> + +# Appendix IV + +## Practices on Statistics – Example use-cases + +(This appendix does not form an integral part of this Recommendation.) + +All ITU-T H.248.1 implementers must read the normative part of this Recommendation carefully before implementing from it. The examples of this appendix should not be used as stand-alone explanations of how to create protocol messages. + +The examples in this appendix are in text-encoded ITU-T H.248. + +## IV.1 Introduction + +The Statistics Descriptor may contain, according to syntax specifications in Annexes A and B, either: + +- an empty list ("empty Statistics Descriptor"); +- a list of statistic names (each statistic name is given as PackageID/StatisticID); +- a list of statistic names, each accompanied by that statistic's value. + +The above syntactical definition and existing ITU-T H.248 semantics of the protocol allow a flexible use of the Statistics Descriptor. This appendix provides examples to illustrate some typical use cases. + +### IV.1.1 MGC operations + +The MGC may perform the following operations on MG processes related to the generation of ITU-T H.248 Statistics (see Figure IV.1): + +- Statistic data: + - 1) Read access on statistic objects (name/value combinations) + - a) read all statistics of a termination; + - b) read all statistics of a dedicated package associated to a termination; + - c) read of individual statistics of a termination. +- Statistic control: + - 2) Activate the collection of all statistics or a specific subset of statistics. + - 3) Deactivate the collection of all statistics or a specific subset of statistics. + - 4) Combine 3) and 2) in order to reset the value of all statistics or a specific subset of statistics. + +Each operation type results in the application of a single ITU-T H.248 descriptor type (here either the Audit Descriptor or the Statistics Descriptor), and a specific setting of the descriptor itself. + +![Diagram showing MGC operations on statistics. The diagram is divided into two main sections: MGC (top) and MG (bottom). The MGC section is further divided into 'Statistic control' and 'Statistic data'. 'Statistic control' includes 'Enable/Disable', 'Initialization (reset)', and 'Reporting configuration'. 'Statistic data' includes 'Read, (write)' and 'Reporting'. The MG section contains a 'Statistic' cylinder. Arrows show the flow of operations: 'Enable/Disable' and 'Initialization (reset)' point to the 'Statistic' cylinder. 'Reporting configuration' points to the 'Statistic' cylinder with a dashed line and a note 'Only ITU-T H.248.47'. 'Read, (write)' and 'Reporting' point to the 'Statistic' cylinder with dashed lines and notes 'Only ITU-T H.248.47'. The 'Statistic' cylinder points to the 'Reporting' operation. The diagram is labeled H.248.1 v3(13)_FIv.1.](7188dd653353235466aea783783e26c8_img.jpg) + +Diagram showing MGC operations on statistics. The diagram is divided into two main sections: MGC (top) and MG (bottom). The MGC section is further divided into 'Statistic control' and 'Statistic data'. 'Statistic control' includes 'Enable/Disable', 'Initialization (reset)', and 'Reporting configuration'. 'Statistic data' includes 'Read, (write)' and 'Reporting'. The MG section contains a 'Statistic' cylinder. Arrows show the flow of operations: 'Enable/Disable' and 'Initialization (reset)' point to the 'Statistic' cylinder. 'Reporting configuration' points to the 'Statistic' cylinder with a dashed line and a note 'Only ITU-T H.248.47'. 'Read, (write)' and 'Reporting' point to the 'Statistic' cylinder with dashed lines and notes 'Only ITU-T H.248.47'. The 'Statistic' cylinder points to the 'Reporting' operation. The diagram is labeled H.248.1 v3(13)\_FIv.1. + +**Figure IV.1 – Categories of MGC operations on statistics +(‘Reporting’ requires support of [b-ITU-T H.248.47])** + +#### IV.1.1.1 Dependency on ITU-T H.248.1 protocol version + +The control operations on statistics appearing in this appendix are realized with the Add, Modify, Move, and/or Subtract commands. These commands may include an Audit Descriptor under all ITU-T H.248.1 protocol versions. However, a Statistics Descriptor may only be used with an Add, Modify or Move command and only in ITU-T H.248.1 Version 3. + +#### IV.1.1.2 Relation to ITU-T H.248.47 + +The Statistic Conditional Reporting Package [b-ITU-T H.248.47] supports additional capabilities related to statistics (as indicated in Figure IV.1); namely a mechanism for real-time reporting of statistics. This mechanism is out of the scope of this appendix. + +### IV.1.2 Examples' background + +This example scenario illustrates the use of the protocol elements in conjunction with an ephemeral termination. The packages chosen for the examples are the network package (nt; clause E.11) and the rtp package (rtp; clause E.12). Note that the rtp package extends the network package. The example assumes that the MG has published both nt and rtp in its Packages Descriptor (see clause 6.2.3). + +For simplicity, we assume that no additional packages are supported by the MG in the example cases. + +## IV.2 Active statistics of a new termination + +The set of statistics that are collected by a termination once it is added to a Context is defined by the contents of the Statistics Descriptor appearing in the Add command (see clause 7.1.15: *"It is also possible, using the descriptor, to indicate what statistics are to be collected."*). + +### IV.2.1 Default initial active statistics + +If a termination's Add command does not include a Statistics Descriptor, all statistics supported by that new Termination will be collected (see clause 7.1.15: *"By default, the particular statistics that are reported for a given termination are determined by the Packages realized by the termination."*). Table IV.1 shows an example use case. + +**Table IV.1 – New termination with default active statistics** + +| ITU-T H.248 text encoding example | Result | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 31205 {
Context = 2005 {
Add = rtp/30/\$ {
Media{ ... }
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 31205 {
Context = 2005 {
Add = rtp/30/23 {
Media{ ... }
}
}
} | +| The Statistics Descriptor is omitted in this Add request of an ephemeral termination. All statistics supported by the termination are therefore collected. | | + +See also clause IV.2.3 for the explicit activation of all statistics. + +### **IV.2.2 Explicit initial active statistics** + +It is possible to explicitly define the set of statistics that a new termination should collect by listing these statistics in the Statistics Descriptor of the Add command. Any statistic not appearing in the Statistics Descriptor will not be collected; and its value will be kept at its initial (reset) value. + +Table IV.2 provides an example use-case for this behaviour. + +**Table IV.2 – Activating individual statistics on a new termination** + +| ITU-T H.248 text encoding example | Result | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 31205 {
Context = 2005 {
Add = rtp/30/\$ {
Media{ ... },
Statistics{       ; three statistics
rtp/pl,       ; RTP packet loss

rtp/delay,   ; RTP packet delay
nt/dur      ; NT session dur.
; NOTE 1
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 31205 {
Context = 2005 {
Add = rtp/30/23 {
Media{ ... }
; NOTE 2
}
}
} | +|

The Statistics Descriptor is included in this Add request of an ephemeral termination. The initial set of active statistics contains the "rtp/pl", "rtp/delay" and "nt/dur" statistics.

NOTE 1 – The rtp version 1 package extends the nt version 1 package. Therefore statistics defined by the nt package may also be referenced using the rtp PackageID; for example rtp/dur.

NOTE 2 – The reply does not repeat the Statistics Descriptor. The general principle is to avoid redundancy in replies, i.e., information sent by the MGC should not be replied again by the MG.

| | + +### **IV.2.3 Use-case: activating all statistics on a new termination** + +Including the wildcard "ALL/ALL" in the Statistics Descriptor of the Add command will result in all statistics being active on the new termination. See Table IV.3. + +NOTE – This use-case results in the same behaviour as omitting the Statistics Descriptor from the Add command. See clause IV.2.1. + +**Table IV.3 – Activating all statistics on a new termination** + +| ITU-T H.248 text encoding example | Result | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 31205 {
Context = 2005 {
Add = rtp/30/\$ {
Media{ ... },
Statistics{
*/*          ;ALL stats of ALL pkgs
}
}
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 31205 {
Context = 2005 {
Add = rtp/30/23 {
Media{ ... }
; NOTE 1
}
}
} | +| The Statistics Descriptor is included in this Add request of an ephemeral termination. Collection of all statistics is activated by a Statistics Descriptor including a single element: "All/All".
NOTE 1 – The reply does not repeat the Statistics Descriptor, even though a wildcard statistic name appeared in the request. The same principle described in Note 2 of Table IV.2 is applied.
NOTE 2 – The effect of this command is identical to that of the command outlined in Table IV.1. | | + +### **IV.2.4 Use-case: activating no statistics on a new termination** + +Including an empty Statistics Descriptor in an Add command will result in all statistics being inactive on the new termination. See Table IV.4. + +**Table IV.4 – Activating no statistics on a new termination** + +| ITU-T H.248 text encoding example | Result | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 31205 {
Context = 2005 {
Add = rtp/30/\$ {
Media{ ... },
Statistics    ; empty descriptor
}
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 31205 {
Context = 2005 {
Add = rtp/30/23 {
Media{ ... }
}
}
} | +| The Statistics Descriptor is empty. No statistics will be collected on the termination. | | + +## **IV.3 Activating and deactivating statistics** + +The set of statistics that an existing termination collects can be changed by including the Statistics Descriptor in a Modify command or a Move command. Table IV.5 provides an example use case. The example assumes that this Modify command follows the Add command appearing in Table IV.2. + +**Table IV.5 – Changing the active statistics** + +| ITU-T H.248 text encoding example | Result | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 31205 {
Context = 2005 {
Modify = rtp/30/23 {
Statistics{
nt/*, ; ALL NT statistics
rtp/ps, ; RTP packets sent
rtp/delay ; RTP packet delay
}
}
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 31205 {
Context = 2005 {
Modify = rtp/30/23
; NOTE
}
} | +| In this example the assumption is that statistics were previously activated according to Table IV.2; i.e., "rtp/pl", "rtp/delay" and "nt/dur" are active. The above Modify request results in:
1) keeping active of "nt/dur" and "rtp/delay";
2) activation of " nt/or" and " nt/os";
3) deactivation of "rtp/pl".
NOTE – The reply does not include the Statistics Descriptor, even though a wildcard statistic name appeared in the request. The same principle described in Note 2 of Table IV.2 is applied. | | + +### IV.3.1 Keeping a statistic active + +For a statistic already active to remain so, it must appear in the Statistics Descriptor of any Modify or Move command (see clause 7.1.15: "*... to maintain already set statistics, these shall be included in the new Statistics Descriptor and the statistic values shall not be reset*"). Table IV.5 illustrates this behaviour with the "nt/dur" and "rtp/delay" statistics. + +### IV.3.2 Activating a statistic + +A statistic appearing in the Statistics Descriptor of a Modify or Move command will be activated (or reactivated) if it was not active before that command. Upon activation, the value of such a statistic is reset to its initial value (see clause 7.1.15: "*... if the particular statistic is reactivated by a subsequent Statistics Descriptor, the value shall be reset*"). Table IV.5 illustrates this behaviour with the "nt/or" and "nt/os" statistics. + +### IV.3.3 Deactivating a statistic + +A statistic missing from the Statistics Descriptor of a Modify or Move command is deactivated and should no longer be collected by the termination. However, the value of this statistic is maintained and not reset (see clause 7.1.15: "*Statistics that have been removed from a Statistics Descriptor shall maintain their values until the termination is subtracted*"). The MGC may later read this value according to the procedures of clause IV.6. Table IV.5 illustrates this behaviour with the "rtp/pl" statistic. + +NOTE – Statistics are also automatically deactivated when a termination is destroyed or returned to the NULL context through a Subtract command. In this scenario however, the value of the statistics is reset and not maintained. See clause IV.4. + +### IV.3.4 Use-case: activating all statistics of an existing termination + +Including the wildcard "ALL/ALL" in the Statistics Descriptor of a Modify or Move command will result in all statistics being active after the command completes (see clause 7.1.15: "*An MGC may reactivate all statistics on a termination/stream by issuing a Statistics Descriptor with a single statistic with the PackageID and StatisticID wildcarded with "ALL". To reactivate all statistics in a* + +given package on a termination/stream, a *Statistics Descriptor with a single statistic with the PackageID specified and the StatisticID wildcarded with "ALL" is issued.*"). Each statistic will either be kept-active or activated; depending on its state before the command was executed. + +Table IV.6 shows an example of this procedure. The example assumes that this MODIFY command follows the MODIFY command appearing in Table IV.5. + +**Table IV.6 – Activate/keep active all statistics of an existing termination** + +| ITU-T H.248 text encoding example | Result | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 31209 {
Context = 2005 {
Modify = rtp/30/23 {
Statistics{
*/* ;ALL stats of ALL pkgs
}
}
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 31209 {
Context = 2005 {
Modify = rtp/30/23
}
} | +| All statistics are either activated or kept-active by a Statistics Descriptor including a statistic of "ALL/ALL".
In this example, the assumption is that statistics were previously activated according to Table IV.5; i.e., "nt/dur", "nt/os", "nt/or" and "rtp/pl" are active. The Modify request results in:
1) keeping active of "nt/dur", "nt/os", "nt/or" and "rtp/pl";
2) activation of "rtp/ps", "rtp/pr", "rtp/jit", and "rtp/delay". | | + +### IV.3.5 Use-case: deactivating all statistics of an existing termination + +Including an empty Statistics Descriptor in an Add, Modify or Move command will result in no statistics being active following the command. Table IV.7 shows an example of this procedure. + +**Table IV.7 – Deactivate all statistics of an existing termination** + +| ITU-T H.248 text encoding example | Result | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 31209 {
Context = 2005 {
Modify = rtp/30/23 {
Statistics ; empty descriptor
}
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 31209 {
Context = 2005 {
Modify = rtp/30/23
}
} | +| The Statistics Descriptor is empty. Following this command, no statistics will be collected on the termination. However, the value of all statistics will be retained.
NOTE – A reply to a subsequent Subtract command missing a Statistics Descriptor will not contain the termination's statistics. See clause IV.5. | | + +## IV.4 Resetting statistics + +The value of a statistic can be reset to its initial value by first deactivating it and then reactivating it. Two commands are therefore required to perform this operation. The two commands may be grouped into one transaction to ensure their ordering and minimize the time interval where the statistic is kept inactive. However, this does not guarantee that this interval will be of zero length; + +i.e., some statistical data may be lost during the time the statistic is inactive. Table IV.8 provides an example use-case for resetting statistics. + +Statistics are also reset when the termination is destroyed or returned to the NULL context by a Subtract command (see clause 7.1.15: "*Statistics are reset when a termination ceases to exist or is returned to the NULL Context due to a Subtract Command.*"). + +**Table IV.8 – Reset RTP statistics** + +| ITU-T H.248 text encoding example: | Result: | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 41225 {
Context = 2005 {
Modify = rtp/30/23 { ; 1st Command
Statistics {
nt/* ; ALL NT statistics
}
},
Modify = rtp/30/23 { ; 2nd Command
Statistics {
rtp/* ; ALL RTP statistics
}
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 41225 {
Context = 2005 {
Modify = rtp/30/23,
Modify = rtp/30/23
}
} | +| In this example the assumption is that all statistics of the nt package are active before the command. The transaction request contains two Modify requests, each containing a Statistics Descriptor. The first command deactivates all statistics other than those of the nt package. The statistics of the nt package are kept active. The second command activates all the statistics of the rtp package. Note that, as the rtp package extends the nt package, this includes all statistics of the nt package. Therefore, the second command will keep the nt statistics active. Following the execution of the two commands, the statistics of the rtp package will be active and their value reset. The statistics of the nt package are kept active through both commands. | | + +## IV.5 Reporting statistics + +Statistics are reported by the MG in the reply to a Subtract command, unless all statistics on the termination were previously deactivated (see clause 7.1.15: "*By default, unless an empty Statistics Descriptor had earlier been used to indicate that no statistics are to be collected, termination and stream level statistics are reported when the termination ceases to exist or is returned to the NULL Context due to a Subtract command.*"). + +An example is given by Table IV.9. + +**Table IV.9 – Default reporting of statistics** + +| ITU-T H.248 text encoding example | Result | +|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 37258 {
Context = 2005 {
Subtract = rtp/30/23
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 37258 {
Context = 2005 {
Subtract = rtp/30/23 {
Statistics {
nt/os=62345, ; octets sent
nt/or=45123, ; octets received
nt/dur=38000, ; in millisecond
rtp/ps=1245, ; packets sent
rtp/pr=780, ; packets received
rtp/pl=10, ; % packets lost
rtp/jit=27, ; jitter
rtp/delay=48, ; average latency
}
}
}
} | +| By default, statistics are reported in the reply to a Subtract command. | | + +### IV.5.1 Report suppression + +The reporting of statistics may be explicitly suppressed by the MGC by including an empty Audit Descriptor in the Subtract command. This behaviour is independent of whether any statistics are currently active on the termination (see clause 7.1.15: *"By default, .... This default behaviour can also be overridden by including an empty Audit Descriptor in the Subtract Command."* and clause 7.1.12: *"The Audit Descriptor may be empty, in which case, no descriptors are returned. This is useful in the Subtract Command to inhibit return of statistics, especially when using wildcard."*). + +Table IV.10 shows an example use case. + +**Table IV.10 – Explicit suppression of statistics reporting** + +| ITU-T H.248 text encoding example | Result | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 31225 {
Context = 2005 {
Subtract = rtp/30/23 {
Audit {} ; empty audit descriptor
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 31225 {
Context = 2005 {
Subtract = rtp/30/23
}
} | +| An empty Audit Descriptor in the Subtract request suppresses reporting of statistics. | | + +## IV.6 Reading statistics + +The MGC may read the value of the statistics at any time, by including an appropriate Audit Descriptor within an AuditValue, Add, Modify, Move or Subtract command (see clause 7.1.15: *"Statistics may also be returned from the AuditValue Command, or any Add/Move/Modify Command using the Audit Descriptor."*). Table IV.11 shows an example use case. + +NOTE 1 – Unless the reading of the statistics coincides with a need to change some of the termination's states, the use of the AuditValue command is most appropriate. + +NOTE 2 – Reading statistics in an Add command, while syntactically correct, has little practical value. + +**Table IV.11 – Explicit reading of statistics** + +| ITU-T H.248 text encoding example | Result | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 31225 {
Context = 2005 {
AuditValue = rtp/30/23 {
Audit{ ; Audit Descriptor with
Statistics ; Statistics Token
}
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 31225 {
Context = 2005 {
AuditValue = rtp/30/23 {
Statistics{
nt/os=62345, ; octets sent
nt/or=45123, ; octets received
nt/dur=38000, ; in millisecond
rtp/ps=1245, ; packets sent
rtp/pr=780, ; packets received
rtp/pl=10, ; % packets lost
rtp/jit=27, ; jitter
rtp/delay=48, ; average latency
}
}
}
} | +| An Audit Descriptor containing the Statistics Token in a command request triggers the reporting of statistics. | | + +### **IV.6.1 Read and activate/deactivate statistics** + +It is possible to use a single Add, Modify or Move command to both read the value of statistics and change the set of statistics that are collected. Such a command will include both an Audit Descriptor, as described under clause IV.6, and a Statistics Descriptor, as described under clause IV.3. + +The MG should perform the two operations (i.e., the statistics' reading and activation/deactivation) according to the order in which the descriptors appear within the command (see clause 7.2: *"Descriptors may appear as parameters to commands in any order. The descriptors shall be processed in the order in which they appear"*). Note that this ordering is meaningful only when a statistic is activated (as activating a statistic resets its value while deactivating it does not). + +Table IV.12 provides an example use case with a Modify command. + +NOTE – Unless the need to read and reset and change the statistics coincides with a need to move the termination between contexts, the use of a Modify command is most appropriate. + +**Table IV.12 – Read and deactivate statistics** + +| ITU-T H.248 text encoding example | Result | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 47397 {
Context = 2005 {
Modify = rtp/30/23 {
Audit {                    ; 1) Audit Descript.
Statistics ; with Statistics
},                            ; Token for 'read'
Statistics ; 2) empty Statist.
;                 Descriptor
}
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 47397 {
Context = 2005 {
Modify = rtp/30/23 {
Statistics {
nt/os=62345,           ; octets sent
nt/or=45123,           ; octets received
nt/dur=38000,          ; in millisecond
rtp/ps=1245,           ; packets sent
rtp/pr=780,             ; packets received
rtp/pl=10,              ; % packets lost
rtp/jit=27,             ; jitter
rtp/delay=48,          ; average latency
}
}
}
}
} | + +The Modify request contains an ordered list: first an Audit Descriptor containing a Statistics token; and second an empty Statistics Descriptor. The Audit Descriptor initiates the reading of all statistics, the subsequent Statistics Descriptor deactivates the collection of all statistics. +NOTE – As detailed under clause IV.3.3, the statistics are not reset when deactivated. A subsequent reading of the statistics will return identical values to the ones given above. + +### IV.6.2 Use-case: reading and resetting all statistics of a termination + +The MGC can combine the procedures of clauses IV.6.1 and IV.4 in order to: + +- 1) Read all statistics collected on a termination. +- 2) Instruct the MG to reset all statistics to their default value. +- 3) Instruct the MG to keep collecting all statistics. + +This is done by issuing a Move or Modify command that reads the values of all statistics and deactivates them, as described under clause IV.6.1; followed by a Modify command that activates all statistics, as described under clause IV.3.4. As explained under clause IV.4, the two commands should be grouped into a single transaction in order to ensure their ordering and to minimize the interval during which the statistics are kept inactive. However, no guarantee is given that this interval will be of zero length. + +Table IV.13 provides an example of this procedure. + +**Table IV.13 – Read and reset statistics** + +| ITU-T H.248 text encoding example | Result | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ITU-T H.248 request:
MEGACO/3 [11.9.19.65]:12345
Transaction = 58932 {
Context = 2005 {
Modify = rtp/30/23 {
Audit{ ; 1) Audit Descriptor
Statistics ; with Statistics
}, ; Token
Statistics ; 2) Empty Statistics
; Descriptor
},
Modify = rtp/30/23 {
Statistics {
*/* ;ALL stats of ALL pkgs
}
}
}
}
} | ITU-T H.248 reply:
MEGACO/3 [2.3.19.70]:6789
Reply = 58932 {
Context = 2005 {
Modify = rtp/30/23 {
Statistics{
nt/os=62345, ; octets sent
nt/or=45123, ; octets received
nt/dur=38000, ; duration
rtp/ps=1245, ; packets sent
rtp/pr=780, ; packets received
rtp/pl=10, ; % packets lost
rtp/jit=27, ; jitter
rtp/delay=48 ; average latency
}
},
Modify = rtp/30/23
}
} | +|

The first Modify request contains an ordered list: first an Audit Descriptor containing a Statistics token; and second an empty Statistics Descriptor. The Audit Descriptor initiates the reading of all statistics, the subsequent Statistics Descriptor deactivates the collection of all statistics.
The second Modify request contains a Statistics descriptor with an "ALL/ALL" statistic. This command resets and reactivates all statistics.

| | + +# Bibliography + +- [b-ITU-T E.180] Recommendation ITU-T E.180/Q.35 (1998), *Technical characteristics of tones for the telephone service.* +- [b-ITU-T G.711] Recommendation ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies.* +- [b-ITU-T G.729] Recommendation ITU-T G.729 (2012), *Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP).* +- [b-ITU-T H.221] Recommendation ITU-T H.221 (2009), *Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices.* +- [b-ITU-T H.223] Recommendation ITU-T H.223 (2001), *Multiplexing protocol for low bit rate multimedia communication.* +- [b-ITU-T H.226] Recommendation ITU-T H.226 (1998), *Channel aggregation protocol for multilink operation on circuit-switched networks.* +- [b-ITU-T H.248.7] Recommendation ITU-T H.248.7 (2004), *Gateway control protocol: Generic Announcement package.* +- [b-ITU-T H.248.47] Recommendation ITU-T H.248.47 (2008), *Gateway control protocol: Statistic conditional reporting package.* +- [b-ITU-T H.320] Recommendation ITU-T H.320 (2004), *Narrow-band visual telephone systems and terminal equipment.* +- [b-ITU-T H.324] Recommendation ITU-T H.324 (2009), *Terminal for low bit-rate multimedia communication.* +- [b-ITU-T H-Sup.7] ITU-T H-series Recommendations – Supplement 7 (2008), *Gateway control protocol: Establishment procedures for the H.248 MGC-MG control association.* +- [b-ITU-T H-Sup.9] ITU-T H-series Recommendations – Supplement 9 (2008), *Gateway control protocol: Operation of H.248 with H.225.0, SIP, and ISUP in support of emergency telecommunications service (ETS)/international emergency preference scheme (IEPS).* +- [b-ITU-T Q.724] Recommendation ITU-T Q.724 (1988), *Telephone user part signalling procedures, plus Amendment 1 (1993).* +- [b-ITU-T Q.764] Recommendation ITU-T Q.764 (1999), *Signalling System No. 7 – ISDN User Part signalling procedures, plus Amendment 3 (2004).* +- [b-ITU-T Q.1400] Recommendation ITU-T Q.1400 (1993), *Architecture framework for the development of signalling and OA&M protocols using OSI concepts.* +- [b-ITU-T Q.1902.4] Recommendation ITU-T Q.1902.4 (2001), *Bearer independent call control protocol (Capability Set 2): Basic call procedures, plus Amendment 2 (2004).* +- [b-ITU-T T.120] Recommendation ITU-T T.120 (2007), *Data protocols for multimedia conferencing.* +- [b-ITU-T V.152] Recommendation ITU-T V.152 (2010), *Procedures for supporting voice-band data over IP networks.* +- [b-IETF RFC 2411] IETF RFC 2411 (1998), *IP Security Document Roadmap.* + +- [b-IETF RFC 2805] IETF RFC 2805 (2000), *Media Gateway Control Protocol Architecture and Requirements*. +- [b-IETF RFC 3389] IETF RFC 3389 (2002), *Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)*. +- [b-IETF RFC 3611] IETF RFC 3611 (2003), *RTP Control Protocol Extended Reports (RTCP XR)*. +- [b-IETF RFC 4566] IETF RFC 4566 (2006), *SDP: Session Description Protocol*. +- [b-IETF RFC 4733] IETF RFC 4733 (2006), *RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.13-200203-I_PDF-E/raw.md b/marked/H/T-REC-H.248.13-200203-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..eee1f805b3567fc5b4d1a49e3edb72a7506cae2b --- /dev/null +++ b/marked/H/T-REC-H.248.13-200203-I_PDF-E/raw.md @@ -0,0 +1,273 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.13** + +(03/2002) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Quality Alert Ceasing +package** + +ITU-T Recommendation H.248.13 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| SYSTEMS AND TERMINAL EQUIPMENT FOR AUDIOVISUAL SERVICES | H.300–H.399 | +| SUPPLEMENTARY SERVICES FOR MULTIMEDIA | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.248.13** + +## **Gateway control protocol: Quality Alert Ceasing package** + +## **Summary** + +This Recommendation specifies an event used by a media gateway to indicate to the media gateway controller that a Quality Alert on a bearer has ceased. + +NOTE – This Recommendation has been renumbered. It was formerly known as ITU-T Rec. H.248, Annex M5. + +###### **Source** + +ITU-T Recommendation H.248.13 was prepared by ITU-T Study Group 16 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 March 2002. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|-----------------------------------------|---| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations..... | 1 | +| 5 | Quality Alert Ceasing package ..... | 1 | +| 5.1 | Properties ..... | 1 | +| 5.2 | Events ..... | 2 | +| 5.2.1 | Event name: Quality Alert Ceasing ..... | 2 | +| 5.3 | Signals ..... | 2 | +| 5.4 | Statistics..... | 2 | +| 5.5 | Procedures ..... | 2 | + + + +## ITU-T Recommendation H.248.13 + +## Gateway control protocol: Quality Alert Ceasing package + +## 1 Scope + +This Recommendation specifies an event used by a media gateway to indicate to the media gateway controller that a Quality Alert on a bearer has ceased. The package defined in this Recommendation extends a previously defined package. It contains an event to indicate Quality Alert Ceasing on a particular bearer. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation H.248.1 (2002), *Gateway Control Protocol*. + +## 3 Definitions + +See ITU-T Rec. H.248.1. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +MG Media Gateway + +MGC Media Gateway Controller + +# 5 Quality Alert Ceasing package + +PackageID: qac, 0x0037 + +Description: This package defines the Quality Alert Ceasing event, complementing the existing Quality Alert event defined within the Network Package E.11/H.248.1. + +Version: 1 + +Extends: nt (0x000b) version1 + +## 5.1 Properties + +None. + +## 5.2 Events + +#### 5.2.1 Event name: Quality Alert Ceasing + +EventID: qualertcease, 0x0004 + +Description: + +The termination generates this event upon detection of ceasing loss of quality alerts and a return to acceptable quality on the network connection. + +EventsDescriptor Parameters: + +Threshold + +ParameterId: th (0x0001) [optional] + +Description: + +This parameter specifies the alert threshold level where the MG shall consider that the quality of the stream is at an acceptable level. + +Type: integer + +Possible Values: + +threshold for percent of quality loss measured, calculated based on a provisioned method, that could take into consideration packet loss, jitter, and delay for example. + +ObservedEventsDescriptor Parameters: + +None. + +## 5.3 Signals + +None. + +## 5.4 Statistics + +None. + +## 5.5 Procedures + +The quality alert ceasing package builds on the existing quality alert event specified in the network package. The additional event specified in this package provides a mechanism to report when a specific network condition ceases. + +The MGC shall set this event on the termination of the bearer that it is interested in monitoring the quality on. + +The MG shall send this event in the case that: + +- it had previously notified the MGC of a Network Package Quality Alert event; and +- the quality of the bearer is now at an acceptable level, or less than the threshold level parameter if set with the qualertcease event and no quality alerts are outstanding. + +Figure 1 shows example quality alert procedures. The quality alert and alert ceasing events may also be contained in an Add.req or before the bearer is established. + +![Sequence diagram showing Quality Alert Ceasing procedures between MGC, MG1, and MG2. The diagram illustrates the interaction where MG1 monitors MG2 and notifies MGC of quality changes. MGC sends a Mod/Mov.req to MG1, which responds with Mod/Mov.reply. MG1 then sends Notify.ind messages to MGC as quality improves from 'Qos Loss Exceed Threshold 1' to 'Qos Loss is better than 1 and at a normal level.', with MGC responding with Notify.reply at each step.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +sequenceDiagram + participant MGC + participant MG1 + participant MG2 + + MG1->>MG2: Bearer Established + MGC->>MG1: Mod/Mov.req (Ctxt=1, Tid=b, Event( Qualert[Threshold1], Qualert[Threshold2], Qualert[Threshold3], Qualertcease)) + MG1-->>MGC: Mod/Mov.reply (Ctxt=1, Tid=b) + MG1->>MG2: Qos Loss Exceed Threshold 1 + MG1->>MGC: Notify.ind(Event(Qualert[Threshold1])) + MGC-->>MG1: Notify.reply + MG1->>MG2: Qos Loss Exceed Threshold 2 + MG1->>MGC: Notify.ind(Event(Qualert[Threshold2])) + MGC-->>MG1: Notify.reply + MG1->>MG2: QosLoss is better than 2 but still exceeds 1 + MG1->>MGC: Notify.ind(Event(Qualert[Threshold1])) + MGC-->>MG1: Notify.reply + MG1->>MG2: Qos Loss is better than 1 and at a normal level. + MG1->>MGC: Notify.ind(Event(Qualertcease)) + MGC-->>MG1: Notify.reply + +``` + +T1610330-02 + +Sequence diagram showing Quality Alert Ceasing procedures between MGC, MG1, and MG2. The diagram illustrates the interaction where MG1 monitors MG2 and notifies MGC of quality changes. MGC sends a Mod/Mov.req to MG1, which responds with Mod/Mov.reply. MG1 then sends Notify.ind messages to MGC as quality improves from 'Qos Loss Exceed Threshold 1' to 'Qos Loss is better than 1 and at a normal level.', with MGC responding with Notify.reply at each step. + +**Figure 1/H.248.13 – Quality Alert Ceasing procedures** + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.14-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.14-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/H/T-REC-H.248.14-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/H/T-REC-H.248.14-200903-I_PDF-E/raw.md b/marked/H/T-REC-H.248.14-200903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..12a13f4e87643b41099a4880f955bf38f6c6b885 --- /dev/null +++ b/marked/H/T-REC-H.248.14-200903-I_PDF-E/raw.md @@ -0,0 +1,297 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.14** + +(03/2009) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: Inactivity timer package** + +Recommendation ITU-T H.248.14 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.248.14 + +# Gateway control protocol: Inactivity timer package + +## Summary + +Recommendation ITU-T H.248.14 provides a package that allows a media gateway to detect the failure of its active media gateway controller through message inactivity. + +This revision provides the following clarifications for the inactivity timer package version 1: + +- the event inactivity timeout (*ito*) may be provisioned; +- the event parameter maximum inactivity time (*mit*) is an *optional* element; +- the event parameter maximum inactivity time (*mit*) has a *default* value, which may be *provisioned*. + +This revision also provides an example setting for the inactivity timer. + +## Source + +Recommendation ITU-T H.248.14 was approved on 16 March 2009 by ITU-T Study Group 16 (2009-2012) under Recommendation ITU-T A.8 procedures. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Inactivity timer package ..... | 2 | +| 6.1 Properties..... | 2 | +| 6.2 Events ..... | 2 | +| 6.3 Signals ..... | 2 | +| 6.4 Statistics..... | 3 | +| 6.5 Error codes..... | 3 | +| 6.6 Procedures ..... | 3 | + + + +## Recommendation ITU-T H.248.14 + +###### Gateway control protocol: Inactivity timer package + +# 1 Scope + +This package contains an event that can be implemented by a media gateway controller (MGC) and by a media gateway (MG) on its root termination. The purpose of the event is to allow the MG to detect periods of silence of H.248 messaging from the MGC. Once the period of silence exceeds the threshold provided in the event, the MGC is notified. + +This package allows MGs to: + +- 1) detect *MGC failure*; or/and +- 2) detect *failures or short-term interruptions of the H.248 transport connection* (see also Note 1 in clause F.3.6 of [ITU-T H.248.1]) + +through H.248 message silence. + +This revision provides the following clarifications for the inactivity timer package version 1: + +- the event inactivity timeout (*ito*) may be provisioned; +- the event parameter maximum inactivity time (*mit*) is an *optional* element; +- the event parameter maximum inactivity time (*mit*) has a *default* value, which may be *provisioned*. + +This revision also provides an example setting for the inactivity timer. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*, including its Amendment 1 (2008), *Corrections and clarifications*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +See [ITU-T H.248.1]. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +ALF Application Level Framing +MG Media Gateway + +# 5 Conventions + +None. + +# 6 Inactivity timer package + +**Package Name:** Inactivity timer package + +**Package ID:** it (0x0045) + +**Description:** This package provides support for MGs detecting the failure of MGCs by H.248 message silence and is only used on the ROOT termination. + +**Version:** 1 + +**Extends:** None + +## 6.1 Properties + +None. + +## 6.2 Events + +### 6.2.1 Inactivity timeout + +**Event Name:** Inactivity timeout + +**Event ID:** ito (0x0001) + +**Description:** Detects that inactivity timer has expired. A *mit* value of 0 disables inactivity timing. + +#### 6.2.1.1 EventDescriptor Parameters + +##### 6.2.1.1.1 Maximum inactivity time + +**Parameter Name:** Maximum inactivity time + +**Parameter ID:** mit (0x0001) + +**Description:** The *mit* parameter specifies the period of H.248 messaging silence, which the MG applies to the process of monitoring incoming H.248 messages. Whenever the period of silence is exceeded, the MG generates a Notify Request with the *it/ito* ObservedEvent. + +**Type:** Integer (in 10 millisecond steps) + +**Optional:** Yes (if default is provisioned) + +**Possible values:** 0..65535 (0, 10 ms, 20 ms, ... , to 655.35 seconds) + +**Default:** Provisioned + +#### 6.2.1.2 ObservedEventsDescriptor Parameters + +None. + +## 6.3 Signals + +None. + +## 6.4 Statistics + +None. + +## 6.5 Error codes + +None. + +## 6.6 Procedures + +### 6.6.1 Detection of *it* package support + +An MGC that supports this package may detect whether or not an MG supports the package by auditing an MG to determine the presence of the package. + +### 6.6.2 MGC-polling by MG (using the *it* package) + +An MGC may choose to set the inactivity timer event containing the maximum silence period or "maximum inactivity time" on the ROOT termination. The MGC should then ensure that the time between messages sent to that MG never exceeds this period. The MGC ensures this by sending any message as a test or keep-alive message (such as the empty Audit of ROOT) whenever no other message is needed within the period. + +### 6.6.3 MG-polling by MGC (using the audit mechanism) + +MGCs may test MGs using a test message (for example, an AuditValue command with an empty AuditDescriptor) without implementing this package or to test MGs that do not implement the package. + +### 6.6.4 Procedural details for the *it* package + +An MG that supports this package and receives the event will monitor incoming messages for periods of silence exceeding the maximum inactivity timer value. On the detection of the silence period, a Notify with the observed event is generated. + +NOTE – The detection of the silence period may be done by starting a timer with the specified timeout that resets to zero on the arrival of each message from MGC and reaches timeout only after the indicated inactivity period. Another approach for the MG would be to keep a "message received" Boolean flag, which should be associated to a normal timer and set to 1 when each message is received. When the timer expires and the Boolean flag is still 0, the MG would send the event Notice; if the Boolean flag is 1, the MG would set the Boolean flag to 0 and restart the timer. + +If the MGC has failed, the event will not receive a reply. If no reply is received, the MG will consider the MGC to have failed and will follow the procedures of clause 11.5 in [ITU-T H.248.1]. + +### 6.6.5 Provisioning of event *it/ito* + +The inactivity timeout event should be provisioned in both the MGC and MG in order to minimize H.248 signalling load at MGC restarts in networks where there are large numbers of MGs that implement the inactivity timer package. In addition, such a configuration allows the MG to detect an MGC failure occurring immediately after the registration process (i.e., before the MGC had a chance to explicitly modify the event). + +#### 6.6.5.1 Provisioning example + +The default value of parameter *mit* may be aligned with parameters of the ALF (application level framing) procedures when H.248 signalling uses IP transport according to Annex D of [ITU-T H.248.1]. In this case, it is recommended to provision a default value greater than ALF timer *T-MAX* setting (e.g., *mit* equal to 110% of *T-MAX*) in order to suspend possible *ito* event notifications before timer *T-MAX* expires. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.15-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.15-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.248.15-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.248.2-201303-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg b/marked/H/T-REC-H.248.2-201303-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef4b18df2a5487b84c11cf2656e6697e2673b296 --- /dev/null +++ b/marked/H/T-REC-H.248.2-201303-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1e79121e3174afb49a2fda45842e4d7f4ec1439149e2170baaf43fbb3f5cbc3 +size 100027 diff --git a/marked/H/T-REC-H.248.2-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.2-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ad98c6e45b6c52f074f0054407ca88a640d8f1d --- /dev/null +++ b/marked/H/T-REC-H.248.2-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58019f38be268f19eaa80c6d56d0f6b39d5741569a8f3ccc04117fa95d9c6465 +size 4016 diff --git a/marked/H/T-REC-H.248.2-201303-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/H/T-REC-H.248.2-201303-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9066c9578ee3747d890e5fcd851c92bcdea82c7 --- /dev/null +++ b/marked/H/T-REC-H.248.2-201303-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f358b3c394f5a38112c9089822ae2e0fd81789a065aa561ec930a72493b10ec +size 81171 diff --git a/marked/H/T-REC-H.248.2-201303-I_PDF-E/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/H/T-REC-H.248.2-201303-I_PDF-E/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b0fc4a09a9857d46f8325a6dd39867d5bbd3494 --- /dev/null +++ b/marked/H/T-REC-H.248.2-201303-I_PDF-E/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c329f47f8bc45ad9228089d3950b30aa66534e9f0fceea897bf464d0c12c5f6c +size 44427 diff --git a/marked/H/T-REC-H.248.2-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.2-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4d8cc3a0f2870d05f376dc2a4458ec4fb10c0ea0 --- /dev/null +++ b/marked/H/T-REC-H.248.2-201303-I_PDF-E/raw.md @@ -0,0 +1,2064 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.2** + +(03/2013) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Facsimile, text +conversation and call discrimination packages** + +Recommendation ITU-T H.248.2 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.248.2 + +## Gateway control protocol: Facsimile, text conversation and call discrimination packages + +## Summary + +Recommendation ITU-T H.248.2 defines packages that extend the applicability of the ITU-T H.248.1 Gateway Control Protocol Recommendation. Specifically, this Recommendation describes packages for fax, text telephone, call type discrimination and data call detection for use with the ITU-T H.248.1 Gateway Control Protocol. As defined in Recommendation ITU-T H.248.1, a "package" is an extension to ITU-T H.248.1 that supports specific behaviour. + +The packages are intended for control over gateway functions for transport of facsimile or text conversation between different network environments. Extensions can be made for other kinds of data transport. + +- **The Call Type Discrimination package** defines control and monitoring of a line for the signalling protocols used in the beginning of a session of data transmission for fax, text telephony or data. This package has been revised to enable the MG to autonomously determine the call type to be supported. +- **The Text Telephone package** defines control of a text telephone session in any of the modes supported by the automoding text telephone Recommendation, ITU-T V.18. +- **The Fax package** defines control of a fax transmission. +- **The Fax/Textphone/Modem Tones Detection package** defines control over a termination for detection of any signals from a fax, text telephone or data modem during a connection in voice mode. +- **The Text Conversation package** defines control over a real-time interactive text conversation session using a universal presentation format and transferred with a transport method from a multimedia protocol in any network environment. +- **The IP Fax package** defines control over facsimile transmission in a packet network. + +All the packages have been editorially modified to align with the ITU-T H.248.1 packages template. + +Amendment 1 (2007) to the 2005 revision provides an enhancement to the types of call that may be discriminated through in-band signalling. It groups existing call types into like types. It provides an explanation of when those types are used. Several new call types are added to the Discriminated Call Type event. The Call discrimination flows have been corrected with the correct events. + +This 2013 revision incorporates a correction to the example call flow in Appendix I. + +NOTE – This Recommendation has been renumbered. It was previously known as Recommendation ITU-T H.248, Annex F. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|-----------------------------|------------|-------------| +| 1.0 | ITU-T H.248 Annex F | 2000-11-17 | 16 | +| 1.0 | ITU-T H.248.2 | 2000-11-17 | 16 | +| 2.0 | ITU-T H.248.2 | 2005-01-08 | 16 | +| 2.1 | ITU-T H.248.2 (2005) Amd. 1 | 2007-01-13 | 16 | +| 3.0 | ITU-T H.248.2 | 2013-03-16 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|---------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | FAX/Textphone/Modem Tones Detection package ..... | 4 | +| 5.1 | Properties..... | 4 | +| 5.2 | Events ..... | 4 | +| 5.3 | Signals ..... | 5 | +| 5.4 | Statistics..... | 5 | +| 5.5 | Procedures ..... | 5 | +| 6 | Text Conversation package..... | 5 | +| 6.1 | Properties..... | 5 | +| 6.2 | Events ..... | 8 | +| 6.3 | Signals ..... | 9 | +| 6.4 | Statistics..... | 9 | +| 6.5 | Procedures ..... | 9 | +| 7 | Text Telephone package..... | 11 | +| 7.1 | Properties..... | 13 | +| 7.2 | Events ..... | 16 | +| 7.3 | Signals ..... | 17 | +| 7.4 | Statistics..... | 17 | +| 7.5 | Procedures ..... | 17 | +| 8 | Call Type Discrimination package ..... | 19 | +| 8.1 | Properties..... | 20 | +| 8.2 | Events ..... | 23 | +| 8.3 | Signals ..... | 27 | +| 8.4 | Statistics..... | 32 | +| 8.5 | Procedures ..... | 32 | +| 9 | Fax package ..... | 35 | +| 9.1 | Properties..... | 35 | +| 9.2 | Events ..... | 37 | +| 9.3 | Signals ..... | 37 | +| 9.4 | Statistics..... | 37 | +| 9.5 | Procedures ..... | 38 | +| 10 | IP Fax package..... | 39 | +| 10.1 | Properties..... | 39 | +| 10.2 | Events ..... | 42 | + +| | Page | +|---------------------------------------------|-------------| +| 10.3 Signals ..... | 42 | +| 10.4 Statistics..... | 43 | +| 10.5 Procedures ..... | 43 | +| Appendix I – Call discrimination flows..... | 45 | +| Bibliography..... | 47 | + +# Recommendation ITU-T H.248.2 + +## Gateway control protocol: Facsimile, text conversation and call discrimination packages + +# 1 Scope + +This Recommendation describes packages for the ITU-T H.248.1 gateway protocol related to data or telematic services. With terminations implementing these packages, a gateway is expected to handle initial modem negotiations, and the communication in voice, fax and text telephone call types. It contains: + +- Package "ftmd" for general detection of signals on a fixed telephone line indicating a possible request to enter some data-related mode; +- Package "ctyp" for general call discrimination to sort out if a call should be handled as voice, fax, text telephone or modem data, and perform the initial negotiation; +- Package "txp" for communicating with text telephones in the telephone network; +- Package "fax" for communication with facsimile in the telephone network; +- Package "txc" for general text conversation in other environments; +- Package "ipfax" for fax transmission in IP networks. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.224] Recommendation ITU-T H.224 (2005), *A real time control protocol for simplex applications using the H.221 LSD/HSD/MLP channels*, plus Cor.1 (2007). +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*. +- [ITU-T H.320] Recommendation ITU-T H.320 (2004), *Narrow-band visual telephone systems and terminal equipment*. +- [ITU-T H.323] Recommendation ITU-T H.323 (2009), *Packet-based multimedia communications systems*. +- [ITU-T H.324] Recommendation ITU-T H.324 (2009), *Terminal for low bit-rate multimedia communication*. +- [ITU-T T.30] Recommendation ITU-T T.30 (2005), *Procedures for document facsimile transmission in the general switched telephone network*, plus Amd.1 (2007). +- [ITU-T T.37] Recommendation ITU-T T.37 (1998), *Procedures for the transfer of facsimile data via store-and-forward on the Internet*, plus Amendments 1 (1999), 2 (2001) and 3 (2002). +- [ITU-T T.38] Recommendation ITU-T T.38 (2010), *Procedures for real-time Group 3 facsimile communication over IP networks*, plus Erratum 1 (2013). + +- [ITU-T T.50] Recommendation ITU-T T.50 (1992), *International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) – Information technology – 7-bit coded character set for information interchange.* +- [ITU-T T.134] Recommendation ITU-T T.134 (1998), *Text chat application entity.* +- [ITU-T T.140] Recommendation ITU-T T.140 (1998)/Add. 1 (2000), *Protocol for multimedia application text conversation.* +- [ITU-T V.8] Recommendation ITU-T V.8 (2000), *Procedures for starting sessions of data transmission over the public switched telephone network.* +- [ITU-T V.8 bis] Recommendation ITU-T V.8 bis (2000), *Procedures for the identification and selection of common modes of operation between data circuit-terminating equipments (DCEs) and between data terminal equipments (DTEs) over the public switched telephone network and on leased point-to-point telephone-type circuits.* +- [ITU-T V.17] Recommendation ITU-T V.17 (1991), *A 2-wire modem for facsimile applications with rates up to 14 400 bit/s, plus Corrigendum 1 (1998).* +- [ITU-T V.18] Recommendation ITU-T V.18 (2000), *Operational and interworking requirements for DCEs operating in the text telephone mode, plus Amendment 1 (2002).* +- [ITU-T V.21] Recommendation ITU-T V.21 (1988), *300 bits per second duplex modem standardized for use in the general switched telephone network.* +- [ITU-T V.23] Recommendation ITU-T V.23 (1988), *600/1200-baud modem standardized for use in the general switched telephone network.* +- [ITU-T V.25] Recommendation ITU-T V.25 (1996), *Automatic answering equipment and general procedures for automatic calling equipment on the general switched telephone network including procedures for disabling of echo control devices for both manually and automatically established calls, plus Corrigendum 1 (2001).* +- [ITU-T V.27 ter] Recommendation ITU-T V.27 ter (1988), *4800/2400 bits per second modem standardized for use in the general switched telephone network.* +- [ITU-T V.34] Recommendation ITU-T V.34 (1998), *A modem operating at signalling rates of up to 33 600 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits.* +- [ITU-T V.61] Recommendation ITU-T V.61 (1996), *A simultaneous voice plus data modem, operating at a voice plus data signalling rate of 4800 bit/s, with optional automatic switching to data-only signalling rates of up to 14 400 bit/s, for use on the General Switched Telephone Network and on leased point-to-point 2-wire telephone type circuits.* +- [ITU-T V.90] Recommendation ITU-T V.90 (1998), *A digital modem and analogue modem pair for use on the Public Switched Telephone Network (PSTN) at data signalling rates of up to 56 000 bit/s downstream and up to 33 600 bit/s upstream.* +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications.* +- [IETF RFC 4103] IETF RFC 4103 (2005), *RTP Payload for Text Conversation.* + +[ISO/IEC 10646-1] ISO/IEC 10646-1:2000, *Information technology – Universal Multiple-Octet Coded Character Set (UCS) – Part 1: Architecture and Basic Multilingual Plane*. + +## 3 Definitions + +This Recommendation defines the following terms: + +**3.1 hexadecimal octet coding:** Hexadecimal octet coding is a means for representing a string of octets as a string of hexadecimal digits, with two digits representing each octet. + +Each octet is issued by the DTE or DCE in the same time sequence as transmitted on the GSTN line, with no intervening characters. + +For each octet, the 8-bit sequence is encoded as two hexadecimal digits. Bit 0 is the first transmitted; bit 7 is the last. + +Bits 7-4 are encoded as the first hexadecimal digit, with bit 7 as MSB and bit 4 as LSB. Bits 3-0 are encoded as the second hexadecimal digit, with bit 3 as MSB and bit 0 as LSB. + +### Examples: + +| Octet bit pattern (time order as specified in Recs ITU-T V.8 and ITU-T V.8 bis) | Hexadecimal coding | ITU-T T.50 codes | +|---------------------------------------------------------------------------------|--------------------|----------------------------------------| +| 00011011 | D8 | 4/4, 3/8 | +| 11100100 | 27 | 3/2, 3/7 | +| 10000011 10100010 11001000 00001001 | C1451390 | 4/3, 3/1, 3/4, 3/5, 3/1, 3/3, 3/9, 3/0 | + +**3.2 hexadecimal octet sequence:** A hexadecimal octet sequence is an even number of hexadecimal digits, terminated by a (ITU-T T.50 0/13) character. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------| +| CR | Carriage Return | +| DCE | Data Circuit-terminating Equipment | +| DTE | Data Terminal Equipment | +| DTMF | Dual Tone Multi Frequency | +| EDT | European Deaf Telephone | +| FAX | Facsimile | +| FCS | Frame Check Sequence | +| GSTN | General Switched Telephone Network | +| ID | Identity | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| LSB | Least Significant Bit | +| MG | Media Gateway | +| MGC | Media Gateway Controller | + +MIME Multipurpose Internet Mail Extension + MSB Most Significant Bit + PSTN Public Switched Telephone Network + RTP Real-time Transfer Protocol + SDP Session Description Protocol + SIP Session Initiation Protocol + TCP Transmission Control Protocol + +## 5 FAX/Textphone/Modem Tones Detection package + +**Package name:** FAX/Textphone/Modem Tones Detection package +**Package ID:** ftmd (0x000E) +**Description:** This package defines an event to detect the presence of data traffic (fax, textphone or modem) on a line. The main intention of this event may be used to effect the compression option on the line so that an audio codec capable of transmitting modem signals can be invoked to handle the connection when needed. This Package extends the possible values of tone id in the "start tone detected" event. Note that there is no discrimination between tones from this package. If discrimination is desired, the Call Type Discrimination package should be invoked. +**Version:** 1 +**Extends:** tonedet version 1 + +### 5.1 Properties + +None. + +### 5.2 Events + +Events are defined as for the Tone Detection package (see [ITU-T H.248.1]). + +#### 5.2.1 Additional tone id value + +Tone Id: dtfm (0x0039) + +This tone id is generated when any of the following tones are detected. + +| "Tone" | Description | Applicable to | +|----------|-----------------------------------------------------------------------------------------------|---------------| +| CNG | an ITU-T T.30 fax calling | Fax | +| V21flag | an ITU-T V.21 tone and flags | Fax | +| CIV18 | an ITU-T V.8 CI with ITU-T V.18 call function | Textphone | +| XCI | an ITU-T V.18 XCI | Textphone | +| V18txp | an ITU-T V.18 "txp" | Textphone | +| Belltone | a Bell 103 carrier, either the high or the low frequency channel (as defined in [ITU-T V.18]) | Textphone | +| Baudot | a Baudot initial tone and character (as defined in [ITU-T V.18]) | Textphone | +| Edt | an EDT initial tone and character (as defined in [ITU-T V.18]) | Textphone | +| Ctm | a CTM signal was detected (as defined in [b-3GPP TS 26.226]) | Textphone | + +| "Tone" | Description | Applicable to | +|---------------|---------------------------------------------------------------------|--------------------| +| CIdata | an ITU-T V.8 CI with any data call function | Data | +| CT | an ITU-T V.25 calling tone | Text and data | +| CIfax | an ITU-T V.8 CI with facsimile call function | Fax | +| V21tone | an ITU-T V.21 carrier, either the high or the low frequency channel | Text and data | +| V23tone | an ITU-T V.23 carrier, either the high or the low frequency channel | Text and data | +| V8 bis | an ITU-T V.8 bis modem handshaking signal | Fax, text and data | +| ANS | ITU-T V.25 ANS, equivalent to T.30 CED from answering terminal | Fax, text and data | +| ANSAM | ITU-T V.8 ANSam | Fax, text and data | + +## 5.3 Signals + +None. + +## 5.4 Statistics + +None. + +### 5.5 Procedures + +None. + +## 6 Text Conversation package + +**Package name:** Text Conversation + +**Package ID:** txc (0x000F) + +**Description:** The Text Conversation package is intended for enabling real-time text conversation between terminals in different networks or multimedia environments. This package includes the mechanisms needed to transport ITU-T T.140 text conversation streams in multimedia environments. The transport mechanism will be different for each environment where the package is used. + +**Version:** 1 + +**Extends:** None + +### 6.1 Properties + +#### 6.1.1 Text Buffering Time + +**Property name:** Text Buffering Time + +**Property ID:** bufftime (0x0001) + +**Description:** This property indicates the time in ms that ITU-T T.140 data shall be collected before transmission in order to minimize text overhead. In low bit rate IP networks, a value of 300 ms is recommended. In environments with low overhead or high bit rates, this property should have the value 0, enabling immediate transmission of entered characters. + +**Type:** Integer + +**Possible values:** 0-500 + +**Default:** Provisioned +**Defined in:** LocalControl +**Characteristics:** Read/Write + +#### 6.1.2 Text Termination Connection State + +**Property name:** Text Termination Connection State +**Property ID:** connstate (0x0002) +**Description:** The connection state property is used to register text capability, request a text connection, and reflect details of the achieved text connection. For transport methods having separate channel control procedures, managed by the MGC, only a subset of the values is used:Idle, Prepare, Connected. +**Type:** Enumeration +**Possible values:** + +| | | | +|-----------|----------|-------------------------------------------------------------------------------------------------------------| +| Idle | (0x0001) | For no connection efforts | +| Prepare | (0x0002) | For being known in the termination and ready to accept (the text capability is offered in session requests) | +| Initiate | (0x0003) | For taking the initiative to establish a text connection opening a text channel | +| Accept | (0x0004) | For accepting an incoming request for a text session | +| Deny | (0x0005) | For denying an incoming text connect request | +| Connected | (0x0006) | For established connection in text mode | + + +**Default:** Idle (0x0001) +**Defined in:** TerminationState +**Characteristics:** Read/Write + +#### 6.1.3 Text User Identity + +**Property name:** Text User Identity +**Property ID:** txuserid (0x0003) +**Description:** This parameter holds the optional remote User Identity parameter of an ITU-T T.140 text conversation session, retrieved from the session. +**Type:** String +**Possible values:** String of up to 64 characters in Unicode UTF-8 +**Default:** None +**Defined in:** LocalControl +**Characteristics:** Read/Write + +#### 6.1.4 Text Transport + +| | | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| Property name: | Text Transport | | +| Property ID: | trpt (0x0004) | | +| Description: | The Transport parameter reflects the transport mechanism selected for the Text Conversation termination. When the media description has the full capability of describing sessions including the transport mechanism, this parameter is implied by the media descriptor. | | +| Type: | Enumeration | | +| Possible values: | H224 | (0x0001) For ITU-T H.224 Client ID = 2 in [ITU-T H.320] | +| | AL1 | (0x0002) For AL1 in [ITU-T H.324] | +| | TCP | (0x0003) For TCP as in Annex G of [ITU-T H.323] | +| | RTP/T.140 | (0x0004) For RTP with ITU-T T.140 as in Annex G of [ITU-T H.323] or IETF SIP | +| | RTP/RED/T.140 | (0x0005) For RTP with ITU-T T.140 and redundancy coding RED as in Annex G of [ITU-T H.323] or IETF SIP | +| | T.134 | (0x0006) For ITU-T T.134 in the ITU-T T.120 environment | +| | Unassigned | (0x0007) When no transport protocol is assigned | +| Default: | Unassigned (0x0007) | | +| Defined in: | LocalControl | | +| Characteristics: | Read/Write | | + +#### 6.1.5 Text Protocol Version + +| | | | +|-------------------------|---------------------------------------------------------------------------|--| +| Property name: | Text Protocol Version | | +| Property ID: | TextProto (0x0005) | | +| Description: | The version of the ITU-T T.140 protocol used in the connection. | | +| Type: | Integer | | +| Possible values: | Any integer corresponding to an ITU-T T.140 version number. (Currently 1) | | +| Default: | 1 | | +| Defined in: | LocalControl | | +| Characteristics: | Read/Write | | + +#### 6.1.6 Redundancy Level + +| | | | +|-----------------------|------------------|--| +| Property name: | Redundancy Level | | +| Property ID: | red (0x0006) | | + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Description: | The number of generations to use in RTP redundancy coding including the Primary. | +| Type: | Integer | +| Possible values: | 0-6
0 = use default or automatic decision on redundancy level
1 = use no redundancy
2-6 = use specified number of generations of data | +| Default: | 0 | +| Defined in: | LocalControl | +| Characteristics: | Read/Write | + +#### 6.1.7 Txc Request Timer + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Txc Request Timer | +| Property ID: | txctim (0x0007) | +| Description: | The txctim property is a timer value in tenths of seconds for the requested operation. If the requested operation is not completed within this time, the state is returned to Idle and the result reported in the connchange event. An initial timer value of 0 indicates that no timer control is requested. | +| Type: | integer | +| Possible values: | 0-6000 | +| Default: | 0 | +| Defined in: | LocalControl | +| Characteristics: | Read/Write | + +### 6.2 Events + +#### 6.2.1 Connection State Change + +| | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Connection State Change | +| Event ID: | connchange (0x0001) | +| Description: | This event will occur when the text connection state for the termination has changed. Its parameter is the new contents of the Connection State property. If a request timed out, the state is returned to Idle. | + +##### 6.2.1.1 EventDescriptor parameters + +None. + +##### 6.2.1.2 ObservedEventDescriptor parameters + +###### 6.2.1.2.1 Connection Change + +| | | +|------------------------|----------------------------------------| +| Parameter name: | Connection Change | +| Parameter ID: | connchnge (0x0001) | +| Description: | Indicates the current connection state | + +| | | +|------------------------|---------------------------| +| Type: | Enumeration | +| Optional: | No | +| Possible value: | As property txc/connstate | +| Default: | None | + +### 6.3 Signals + +None. + +### 6.4 Statistics + +#### 6.4.1 Characters Transferred + +| | | +|-------------------------|-------------------------------------------------------------------------| +| Statistic name: | Characters Transferred | +| Statistics ID: | chartrans (0x0001) | +| Description: | Number of bytes of ITU-T T.140 data transferred through the termination | +| Type: | Integer | +| Possible values: | 0 and up | +| Level: | Termination | + +#### 6.4.2 Packets Lost + +| | | +|-------------------------|----------------------------------------------------------------------------------------| +| Statistic name: | Packets Lost | +| Statistics ID: | packlost (0x0002) | +| Description: | Number of ITU-T T.140 packets lost as counted by the receiving ITU-T T.140 termination | +| Type: | integer | +| Possible values: | 0 and up | +| Level: | Termination | + +### 6.5 Procedures + +The following are standard transport mechanisms for text conversation in different environments. + +- In ITU-T H.320: ITU-T H.224 with Client ID = 2; +- In ITU-T H.324: AL1 channel connected with ITU-T H.245 procedures; +- In ITU-T T.120: ITU-T T.134 transport in ITU-T T.125 communication channel environment; +- In ITU-T H.323: RTP/T.140 or TCP as selected with ITU-T H.245 messages; +- In IETF SIP: RTP/T.140 as initiated with SDP. + +NOTE – ITU-T T.140 text media is also used together with ITU-T V.18 modems for text telephony; this is specified in a separate package: Text\_Telephone (txp). + +The Text Conversation package is intended to be added to a multimedia termination, handling appropriate multiplexing and control. + +#### 6.5.1 Function + +A termination with Text Conversation adds capability declaration for a text conversation channel in the call set-up according to procedures defined for each environment. When matching capabilities exist, an ITU-T T.140 channel can be established according to the transport protocol used in the current environment. ITU-T T.140 text stream contents received from one termination are transferred for transmission to other ITU-T T.140 capable terminations in the context. The ITU-T T.140 contents may be buffered for a short moment for possible collection of more text in the same transmission according to the buffer time property. + +#### 6.5.2 Informative description + +Real-time text conversation allows telecom users to carry out a written conversation. The presentation and coding aspects of standardized text conversation are defined in [ITU-T T.140]. Text is transmitted character by character (or in small blocks) so that the users experience a close interaction. The text and basic editing control is ISO/IEC 10646-1, UTF-8 coded. Figure 1 gives an example of how a text conversation can be displayed to the user. + +| ANNE | EVE | +|------------------------------------------------------------|----------------------------------------------------------------------------| +| Hi, this is Anne. | Oh, hello Anne, I am glad you are calling!
It's been long since we met! | +| Yes, have you heard that I will come to Paris in November? | No, that's new to me. What brings you here? | + +**Figure 1 – Possible display of a one-to-one text conversation** + +For each transport environment, a suitable transport protocol must be selected to carry the text. Currently defined and recommended transport environments for ITU-T T.140 text media streams that can be supported by this package are: + +- 1) packet networks, where the procedures described in Annex G of [ITU-T H.323] can be used for setting up and conducting text conversation sessions, using TCP or RTP/T.140 for the transport of ITU-T T.140; +- 2) packet networks, where the IETF Session Initiation Protocol (SIP) can be used for setting up and conducting text conversation sessions using RTP/T.140 for the transport of ITU-T T.140; +- 3) the ITU-T H.324 multimedia environment in PSTN, ISDN and Mobile networks, where an AL1 channel connected by ITU-T H.245 procedures is used for ITU-T T.140; +- 4) the ITU-T H.320 multimedia environment, where an ITU-T H.224 channel with Client ID = 2 is specified for transport of ITU-T T.140; +- 5) the ITU-T T.120 data conferencing environment, that can be used alone, or in conjunction with any of the environments above, where ITU-T T.134 specifies the application entity and ITU-T T.125 the data channel for ITU-T T.140. + +A separate Text Telephone package (txp) supports text telephony in the PSTN using the ITU-T V.18 modem in native and legacy modes, and ITU-T T.140 for communication with terminations using this package. + +Interworking between these forms of Text Conversation can be achieved through the use of gateways with packages defined here. + +#### 6.5.3 Total Conversation + +Most text conversation transport environments are part of multimedia communication systems. With the introduction of text, they enable conversation in video, text and voice simultaneously, called Total Conversation. The total set of communication modes that people tend to use locally can be offered on a distance through Total Conversation. Since the text part is built on the unified presentation level T.140, the task to arrange interoperability of Total Conversation in different network environments through a gateway is simplified. + +Video is optional in the multimedia systems. Therefore, compatible text-and-voice conversation can also be established within the same framework. + +#### 6.5.4 Descriptor to use for text conversation + +One descriptor value is of specific interest for the Text Conversation and Text Telephone packages. That is the text conversation media stream. It is described here for information. + +### Text conversation stream + +This descriptor is used for the text conversation stream, according to [ITU-T T.140]. [ITU-T T.140] gives a general presentation level description for a termination supporting real-time text conversation. The text and basic editing control is UTF-8 coded. For each transport environment, a suitable transport protocol must be selected to carry the text. + +T.140 is a registered MIME text stream name, which can be specified to be used as it is or in RTP embedding of [IETF RFC 4103]. + +## 7 Text Telephone package + +| | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | Text Telephone package | +| Package ID: | txp (0x0010) | +| Description: | The Text Telephone package is used on a line termination in a Media Gateway, to handle text telephone calls. It includes ITU-T V.18 text telephone modem functionality that adapts to different legacy text telephone systems in the PSTN as well as it provides communication with ITU-T V.18-equipped text telephones. The text media stream is UTF-8 coded with a few editing functions as specified in [ITU-T T.140]. The Text Telephone package is intended to be operated together with the Call Type Discrimination package (ctyp) to perform ITU-T V.18 automoding functions. | +| Version: | 1 | +| Extends: | None | + +### Text telephony + +Text telephony offers a real-time conversation in text between two parties. It may be combined with voice conversation. Text telephony in PSTN existed in at least six incompatible legacy modes before the automoding modem Recommendation for text telephony ITU-T V.18 was introduced by [ITU-T V.18]. It is suitable for use in PSTN text telephones, as well as in gateways for connection to the PSTN text telephones. When connected, it can operate in one of its native ITU-T V.18 modes, or in any of the six legacy modes described in [ITU-T V.18] annexes. The legacy modes are Baudot, EDT, DTMF, V.21, Minitel and Bell 103. The mode detection and adjustment of the transmission to the selected mode is automatic. + +The native modes use [ITU-T T.140] for the text coding and control and [ITU-T V.21] or optionally [ITU-T V.61] for the modulation. The legacy modes use different character coding schemes, but + +when used in a gateway, the text stream to and from the textphone termination is ITU-T T.140 coded for all modes. The text telephone package described here includes character conversion, filtering and other adaptation needed for conversation with the legacy mode text telephones. + +### Carrier modes and carrierless modes + +Three of the legacy textphone modes are carrierless. This means that they do not send any signal at all when there are no characters to transmit. Three legacy modes and the native ITU-T V.18 modes use a carrier tone transmitted as long as the connection is maintained. If the carrier stops, it is detected but the line is not disconnected because this is normal behaviour when transferring call or when alternating between voice and text usage. + +### Text Telephone package considerations above the ITU-T V.18 modem level + +[ITU-T V.18] only specifies an automoding modem and the requirement to use ITU-T T.140 when ITU-T V.18 native mode is achieved in a connection. When used in a gateway, there are some general issues that must be handled above the ITU-T V.18 level. + +### Character set + +The legacy modes have limited character sets. For all legacy modes, appropriate character conversion, filtering and control interception are included in the package functionality, so that the communication with other ITU-T T.140 text terminations in the context is equalized to an ITU-T T.140 text stream. + +### Embedded termination functionality + +There is no need to open all details of the use of ITU-T V.18 and ITU-T T.140 to be accessible from the MGC in a gateway. ITU-T V.18, ITU-T T.140, character conversion methods and other automated methods are therefore combined in the Text Telephone package that can be added to suitable terminations of a gateway. Figure 2 describes the Text Telephone package components. + +![Figure 2 – Text Telephone package functional view. This block diagram shows the functional components of a Text Telephone package. At the top, a 'Text stream' enters a box labeled 'ITU-T T.140'. Below this box, the path splits into two parallel boxes: 'Transparent text transmission for native ITU-T V.18 modes' and 'ITU-T T.140 conversion for legacy textphone modes'. Both of these boxes lead to a single box labeled 'ITU-T V.18 modem'. From the 'ITU-T V.18 modem', an 'Audio stream' is shown as 'Simultaneous audio'. Below the modem is a decision diamond. One path from the diamond is labeled 'Alternating audio' and leads to an 'Audio stream' line. The other path from the diamond leads to a 'Line interface'. A vertical 'Control' line on the left has arrows pointing to the 'ITU-T T.140' box, the 'Transparent text transmission' box, the 'ITU-T V.18 modem', and the decision diamond. A label 'H.248.2(13)_F02' is in the bottom right corner of the diagram area.](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +Figure 2 – Text Telephone package functional view. This block diagram shows the functional components of a Text Telephone package. At the top, a 'Text stream' enters a box labeled 'ITU-T T.140'. Below this box, the path splits into two parallel boxes: 'Transparent text transmission for native ITU-T V.18 modes' and 'ITU-T T.140 conversion for legacy textphone modes'. Both of these boxes lead to a single box labeled 'ITU-T V.18 modem'. From the 'ITU-T V.18 modem', an 'Audio stream' is shown as 'Simultaneous audio'. Below the modem is a decision diamond. One path from the diamond is labeled 'Alternating audio' and leads to an 'Audio stream' line. The other path from the diamond leads to a 'Line interface'. A vertical 'Control' line on the left has arrows pointing to the 'ITU-T T.140' box, the 'Transparent text transmission' box, the 'ITU-T V.18 modem', and the decision diamond. A label 'H.248.2(13)\_F02' is in the bottom right corner of the diagram area. + +Figure 2 – Text Telephone package functional view + +### 7.1 Properties + +#### 7.1.1 Conversation mode + +| | | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| Property name: | Conversation mode | | +| Property ID: | convmode (0x0001) | | +| Description: |

The behaviour of the termination is influenced by this property. By setting the property to a selection of the possible values, the number of ways that the conversation can be conducted can be defined. After connection the property contains the actual conversation mode used in the call.

The basic text-only mode shall always be supported.

The alternating text and voice mode is most often used to enable one user to speak and read and the other to listen and type. It is used because there was no technology support for simultaneous voice and text when text telephony was introduced. It is only supported for compatibility with the legacy mode text telephone habits.

The simultaneous text and voice mode enables the users to communicate in any combination and order of the two media. No legacy mode terminals operate in this mode. ITU-T V.18-equipped terminals with ITU-T V.61 modulation can operate in this mode.

| | +| Type: | Sub-list of Enumeration | | +| Possible values: | Text-only (0x0001) | Basic text-only mode, not possible to combine with voice | +| | Alternating (0x0002) | Text and voice may be alternating | +| | Simultaneous (0x0003) | Simultaneous text and voice mode | +| Default: | Provisioned | | +| Defined in: | Termination state | | +| Characteristics: | Read/Write | | + +#### 7.1.2 Communication Mode + +| | | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| Property name: | Communication Mode | | +| Property ID: | commode (0x0002) | | +| Description: |

This property indicates what modulation and mode the ITU-T V.18 modem is operating in, reflecting what type of text telephone it is in connection with. For an explanation of the different modes, see [ITU-T V.18].

If a specific mode of operation is wanted, this property is set before the text connection is made.

Normally it is set with the outcome of the ITU-T V.18 automoding procedure performed with the Call Type Discrimination package.

When a legacy mode textphone signal is detected by the Call Type Discrimination package, the connection result is only reported, but ITU-T V.18 does not transmit any signal until ordered to do so by setting this property or when probing is invoked.

| | +| Type: | Enumeration | | +| Possible values: | V18-V21Hi (0x0001) | Native ITU-T V.18 mode transmitting on the high channel for text only or text | + +| | | | +|-------------------------|----------|--------------------------------------------------------------------------------------------------------| +| | | and voice alternatively | +| V18-V21Lo | (0x0002) | Native ITU-T V.18 mode transmitting on the low channel for text only or text and voice alternatively | +| V18-V61C | (0x0003) | Native ITU-T V.18 mode for text and voice simultaneously, transmitting in the caller's channel | +| V18-V61A | (0x0004) | Native ITU-T V.18 mode for text and voice simultaneously, transmitting in the answering part's channel | +| V21Hi | (0x0005) | Legacy ITU-T V.21 mode transmitting on the high channel | +| V21Lo | (0x0006) | Legacy ITU-T V.21 mode transmitting on the low channel | +| DTMF | (0x0007) | DTMF text telephone mode | +| EDT | (0x0008) | EDT ("European Deaf Telephone") | +| Baudot 45 | (0x0009) | Baudot 45.45 bit/s | +| Baudot 47 | (0x000A) | Baudot undetermined bit rate | +| Baudot 50 | (0x000B) | Baudot 50 bit/s | +| V23Hi | (0x000C) | ITU-T V.23 modulation and Minitel coding transmitting on the high channel | +| V23Lo | (0x000D) | ITU-T V.23 modulation and Minitel coding, transmitting on the low channel | +| BellHi | (0x000E) | Bell 103, transmitting on the high channel | +| BellLo | (0x000F) | Bell 103, transmitting on the low channel | +| None | (0x0010) | No mode achieved | +| Default: | | "None" (0x0010) | +| Defined in: | | LocalControl | +| Characteristics: | | Read/Write | + +#### 7.1.3 Connection Mode + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Connection Mode | +| Property ID: | connmode (0x0003) | +| Description: |

This property indicates in what connection phase and mode the ITU-T V.18 modem is operating. A connection effort is initiated by setting this property to connecting, with the desired mode in the Communication Mode property.

An ITU-T V.18 modem can be controlled to operate in one of a set of modes for seeking contact with a counterpart. The modes available are listed as values of this property. Determination of the mode is made by the ctyp package, possibly combined with the probing action of that package.

Once connected, the termination operates in the selected mode until the text connection is lost or it is ordered to disconnect. If text

| + +connection is lost for a certain time, the automoding procedure can be restarted through the ctyp package, or the modem can stay in the achieved mode trying to reconnect. + +The ctyp package may be used on a connected voice line to detect if the remote user wants to enter text mode. It must be noted that for some of the legacy modes (EDT, DTMF and Baudot), the user has to push some keys on the textphone to make the connection when ITU-T V.18 is set in the automode monitor mode. This is slightly unusual for a textphone user, who normally waits for the answering side to start the conversation. Therefore, the explicit automoding modes should be used when possible, probing as answering and sending ITU-T V.18 signals as calling. + +If a connection request fails, the property returns to Idle state. If the connection request succeeds, the property changes value to Connected. + +| | | | +|-------------------------|-------------------|------------------------------------------------------------------------------------------------| +| Type: | Enumeration | | +| Possible values: | Idle | (0x0001) No connection established and no efforts to connect | +| | Connecting | (0x0002) For request of the native or legacy mode indicated in the Communication Mode property | +| | Connected | (0x0003) Connection established in one of the communication modes | +| Default: | Idle (0x0001) | | +| Defined in: | Termination State | | +| Characteristics: | Read/Write | | + +#### 7.1.4 Action at Loss of Connection + +| | | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| Property name: | Action at Loss of Connection | | +| Property ID: | lossconnection (0x0006) | | +| Description: | This property tells how the ITU-T V.18 modem handles loss of text connection. When "Keep" is selected, the conversation is optimized for the alternating text-voice mode. When "Return" is selected, the communication is optimized for call forwarding between different types of text telephones. For that case, ctyp must be invoked for reconnection. | | +| Type: | Enumeration | | +| Possible values: | Keep | (0x0001) Keep selected communication mode | +| | Return | (0x0002) Return to automoding | +| Default: | Provisioned | | +| Defined in: | Termination State | | +| Characteristics: | Read/Write | | + +#### 7.1.5 V18 Options + +| | | | +|-----------------------|-------------|--| +| Property name: | V18 Options | | +|-----------------------|-------------|--| + +| | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------| +| Property ID: | v18opt (0x0007) | +| Description: | This property indicates what optional capabilities the ITU-T V.18 modem implementation has and is allowed to use. | +| Type: | Sub-list of Enumeration | +| Possible values: | V.61 capability (0x0001) Indicates the ability to use V.61 modulation | +| Default: | None | +| Defined in: | Termination state | +| Characteristics: | Read/Write | + +#### 7.1.6 Character Set + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Character Set | +| Property ID: | characterset (0x0008) | +| Description: |

The legacy modes have limited character sets. For all legacy modes, appropriate character conversion, filtering and control interception is included in the package functionality, so that the communication with other ITU-T T.140 text terminations in the context is equalized to an ITU-T T.140 text stream. For a user-friendly conversion of received national characters in the limited character sets to ISO/IEC 10646-1 used in ITU-T T.140, there is a need to specify what national translation table to use. This is valid for EDT, DTMF, ITU-T V.21 and Baudot modes. The character set parameter is the registered ISO code for the national variant of the ITU-T T.50 character set used. Default is:

  • – German for EDT;
  • – Danish for DTMF (suitable also for the Netherlands);
  • – Swedish/Finnish for ITU-T V.21 (suitable also for the United Kingdom);
  • – International Reference Version for Baudot.

Example: In Norway, the letter "Æ" (A and E together) is used in the same location of the 7-bit character table as used for letter "Å" (A with umlaut) in Finland and Sweden. The international reference version has the character "[" (left bracket) in the same position. In ITU-T T.140, these characters have unique positions.

| +| Type: | String | +| Possible values: | ISO registered name for a character set | +| Default: | Provisioned | +| Defined in: | Termination State | +| Characteristics: | Read/Write | + +### 7.2 Events + +#### 7.2.1 Connection Mode Changed + +| | | +|--------------------|-------------------------| +| Event name: | Connection Mode Changed | +|--------------------|-------------------------| + +**Event ID:** connchng (0x0001) + +**Description:** This event reports the change of communication mode, as a result of a connection effort, or a disconnection. + +#### 7.2.1.1 EventDescriptor parameters + +None. + +#### 7.2.1.2 ObservedEventDescriptor parameters + +Same as the property txp/commode. + +### 7.3 Signals + +None. + +### 7.4 Statistics + +#### 7.4.1 Number of Characters Transferred + +**Statistic name:** Number of Characters Transferred + +**Statistics ID:** chartrans (0x0001) + +**Description:** Number of bytes of ITU-T T.140 data transferred (sent and received) + +**Type:** Integer + +**Possible values:** 0 or more characters + +**Level:** Termination + +#### 7.4.2 Number of Alternating Turns + +**Statistic name:** Number of Alternating Turns + +**Statistics ID:** alturns (0x0002) + +**Description:** Number of alternating turns when using alternating conversation mode + +**Type:** Integer + +**Possible values:** 0 or more turns + +**Level:** Termination + +### 7.5 Procedures + +#### 7.5.1 Basic operation + +After line connection, the termination where the Text Telephone package is implemented should be requested to try a text telephone connection using the functionality of the Call Type Discrimination package for the modem signalling according to [ITU-T V.18] in a selected mode. Once the connection is established, the Text Telephone package is used for the text communication in the established mode. + +After connection in text mode, the result is a gateway context with one textphone termination and one voice line termination connected to the same line. In the same context, the normal case is to have other terminations with audio and text conversation media. + +In the simplest text-only case, the audio streams are not used and may be released. + +Text received through the ITU-T V.18 modem is converted if necessary to ITU-T T.140. It is embedded in the RTP/T.140 format according to the rules in [ITU-T T.140] and [IETF RFC 4103], specifying RTP/T.140. Text received from other text conversation terminations is transmitted through the text telephone termination after extraction from the RTP packets. This process continues until any end disconnects. + +#### **7.5.2 Informative description** + +Two descriptor values are of specific interest for the Text Telephone package. These are: the text conversation media stream, and the ITU-T V.18 modem. The text conversation media stream is described in the Text Conversation package. The ITU-T V.18 modem descriptor is described in clause 7.5.3 for information. + +#### **7.5.3 ITU-T V.18 modem** + +The ITU-T V.18 modem type is intended for communication with text telephones in the PSTN. Its operational modes are implemented in the textphone package. The logic for setting and detecting the mode according to [ITU-T V.18] is handled by the ctyp package. Some properties of the Text Telephone package and the Call Type Discrimination package directly reflect parameters for control of the ITU-T V.18 modem. ITU-T V.18 modem implementations may have different capabilities reflected in the property values. + +An ITU-T V.18 modem may be operated in automode monitor mode, when it listens on a voice line for text telephone signals. This mode can be used to detect that the user wishes to transit from voice to text during a voice call. That is done entirely with the ctyp package. + +Alternatively, an ITU-T V.18 modem may be operated in modes where it actively tries to establish a text telephone connection. The procedure includes transmission of text telephone-specific signals on the line. For calling modems, it is done by the CI signal in the ctyp package. For an answering modem, it is done with the ctyp package combined with probing from the textphone package by setting the commode property to the probing mode. + +When the mode is discriminated, the commode property should be set to request communication in that mode. + +After successful connection in a text telephone mode, the text session is conducted in the specific mode as controlled with the commode property, and the text stream is made available in ITU-T T.140 format for other text terminations in the context. + +The Text Telephone package only contains the text connection and text media aspects of the termination. It is supposed to be combined with appropriate call control packages, line interface packages and voice channel packages. + +#### **7.5.4 Operation with alternating text and voice mode** + +If the involved gateways have the alternating text and voice capability, the following procedure can be applied to give the users a possibility to go back and forth between using text and voice. Between the terminals in the context, two streams are members of the context during the call, the text stream and the audio stream. The procedure is slightly dependent on the terminal type as described in the following clause. + +#### **7.5.5 Alternating text and voice mode with legacy, carrierless textphones** + +For the carrierless types Baudot, DTMF and EDT the following way to operate should be used: When ITU-T V.18 detects text, the textphone termination stops feeding the audio stream into the audio stream of the context, and instead inserts the detected and ITU-T T.140 converted characters into the text stream. This mode is continued as long as characters keep coming from the PSTN textphone. + +When no more characters arrive, and no textphone signal is received within one second, the audio channel is again fed to the Audio-stream channel. If new text comes from the ITU-T V.18 side, the process is repeated. + +It is important that the implementation of ITU-T V.18 can retrieve characters from the first detected text telephone signals after each mode shift. The leading tones before the characters can be as short as 150 ms. + +If text is received from the context through the Text stream when ITU-T V.18 is not actively receiving text, the voice path is muted, and the characters are sent to the ITU-T V.18 modem for transmission. When all text is transmitted and no more is received for two seconds, the audio channels are enabled again. + +Since the carrierless systems are one-way alternate transmission systems, transmission of characters is possible only in one direction at a time. Once started, reception is given priority. + +In the Context, two-way simultaneous transmission is possible. Therefore, characters received from the context while ITU-T V.18 is busy receiving should be buffered (up to a reasonable limit). + +After the initial connections, all these actions are automatic and are handled within the textphone termination. + +#### 7.5.6 Alternating voice and text conversation in carrier mode + +After a carrier mode text connection is established, loss of carrier can be taken as the indication that the audio stream shall be connected with audio interface of the line. When the remote end is an ITU-T V.21, Bell or ITU-T V.18 device, the text communication can be full duplex, so the gateway can just let the text streams flow between the terminations. + +When carrier reappears, or text is received through the text system, the audio stream shall be muted, and text transmission noted. + +Minitel does not support any voice interworking mode. + +#### 7.5.7 Simultaneous voice and text mode + +In case the simultaneous voice and text method is enabled, the handling of the voice and text channels is trivial. Once connected, the text stream can stay connected with the remote text stream all the time to serve a two-way simultaneous text conversation, and the audio channel can be connected with the remote audio stream to support a two-way simultaneous audio channel. This mode can be supported by ITU-T V.18 with ITU-T V.61 modulation. + +## 8 Call Type Discrimination package + +**Package name:** Call Type Discrimination Package + +**Package ID:** ctyp (0x0011) + +**Description:** This package monitors the termination for signals indicating presence of an ITU-T T.30 telefax terminal, an ITU-T V.18 or legacy mode text telephone or data modem. In cooperation with the MGC and the remote MG or endpoint, it can perform exchange of signals until the call type is determined and an appropriate mode for the call can be established. + +The package contains modem negotiation functions of Recommendations [ITU-T V.25], [ITU-T V.8], [ITU-T V.8 *bis*], [ITU-T V.18] and [ITU-T T.30]. + +**Version:** 3 + +**Extends:** None + +### 8.1 Properties + +#### 8.1.1 Call Types + +**Property name:** Call Types + +**Property ID:** calltyp (0x0001) + +**Description:** The Call Types property selects the types of calls for which the termination is monitored. Note that the connection is, by default, regarded to be capable of handling audio and therefore no specific value is included for that. + +**Type:** Sub-list of Enumeration + +**Possible values:** FAX (0x0001) + +TEXT (0x0002) + +DATA (0x0003) + +**Default:** None + +**Defined in:** Termination State + +**Characteristics:** Read/Write + +#### 8.1.2 Text Call Types + +**Property name:** Text Call Types + +**Property ID:** ttyp (0x0002) + +**Description:** This parameter indicates for what text telephone modes the termination is monitored, used in TEXT mode. + +**Type:** Sub-list of Enumeration + +**Possible values:** V21 (0x0001) + +DTMF (0x0002) + +Baudot45 (0x0003) + +Baudot50 (0x0004) + +Bell (0x0005) + +EDT (0x0006) + +Minitel (0x0007) + +V18 (0x0008) + +CTM (0x0009) + +**Default:** None + +**Defined in:** Termination State + +**Characteristics:** Read/Write + +#### 8.1.3 V8bis Support + +**Property name:** V8bis Support + +**Property ID:** v8bsup (0x0003) + +**Description:** Support of the ITU-T V.8 *bis* modem negotiating procedure is + +optional. The V8bis support property indicates if ITU-T V.8 *bis* is supported. It can be used in TEXT, FAX and DATA modes. + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------| +| Type: | Boolean | +| Possible values: | True    ITU-T V.8 bis is supported by the package
False    ITU-T V.8 bis is not supported by the package | +| Default: | Provisioned | +| Defined in: | Termination State | +| Characteristics: | Read | + +#### 8.1.4 Probe Message + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Probe Message | +| Property ID: | probemsg (0x0004) | +| Description: |

This property holds a short string that the termination transmits as a stimulating probe message for the carrierless communication modes in the answering modes. The far end user will see this message when it is transmitted in the mode matching the counterpart's textphone, and type a response back, enabling the ITU-T V.18 modem to detect the type of carrierless text telephone in the connection.

When issued, it is automatically followed by "GA" in Baudot probing, and with "+" in EDT and DTMF probing to reflect the turntaking signal habit in the different user communities. The string could be customized to briefly inform the called user about what service that is reached.

| + +Note that the string is not issued in the carrier modes. + +| | | +|-------------------------|----------------------------------------------| +| Type: | String | +| Possible values: | Any string, not more than 20 characters long | +| Default: | Empty String ("") | +| Defined in: | Termination State | +| Characteristics: | Read/Write | + +#### 8.1.5 Probe Order + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Probe Order | +| Property ID: | probeorder (0x0005) | +| Description: |

This property holds an indication on what modes to probe for, and the order the probes will be transmitted. Probing is a time-consuming procedure and it is important that the most likely modes are probed first. The order to select depends on whether or not any legacy mode textphones are on the market in the area where the gateway is installed. An optimized order can be composed by enumerating the desired specific type indicators. Note that leaving out a type from probing may cause connection problems for connection with textphones of that type.

| +| Type: | Sub-List of Enumeration | + +**Possible values:** (For recommended orders, see [ITU-T V.18].) + Any combination of one to six of the type indicators: + +- V21 (0x0001) +- DTMF (0x0002) +- Baudot (0x0003) +- EDT (0x0004) +- MINITEL (0x0005) +- BELL (0x0006) + +in any desired order + +**Default:** Provisioned + +**Defined in:** Termination state + +**Characteristics:** Read/Write + +#### 8.1.6 Phase Reversal Detect + +**Property name:** Phase Reversal Detect + +**Property ID:** phrevdet (0x0006) + +**Description:** This property indicates support of detection of the phase reversals within ANS or ANSam signals. If this property has the value "False", ANS with phase reversals (ANSBAR) will be reported as ANS and ANSam with phase reversals (ANSAMBAR) will be reported as ANSam in the dtone event. + +**Type:** Boolean + +**Possible values:** True Phase reversal detection is supported by the termination. + False Phase reversal detection is not supported by the termination. + +**Default:** Provisioned + +**Defined in:** Termination State + +**Characteristics:** Read + +#### 8.1.7 MG Responsible for Call Discrimination Signalling + +**Property name:** MG Responsible for Call Discrimination Signalling + +**Property ID:** MGCallSig (0x0007) + +**Description:** This property indicates whether the MGC or MG is responsible for initiating the Call Discrimination Signalling. + +**Type:** Boolean + +**Possible values:** True Indicates that the MG is responsible for Call Discrimination Signalling, i.e., ANS, ANSam. The signals defined in clause 7.3 are not sent from the MGC to order messages, the MG autonomously determines when to send the appropriate messages. + False Indicates that the MGC is responsible for initiating Messages for Call Discrimination. The signals defined in clause 7.3 apply. + +**Default:** Provisioned +**Defined in:** Termination State +**Characteristics:** Read/Write + +### 8.2 Events + +#### 8.2.1 Discriminating Tone Detected + +**Event name:** Discriminating Tone Detected +**Event ID:** dtone (0x0001) +**Description:** This event indicates that a signal valid for detection and discrimination of mode was detected. The signal name is given as a parameter. Further logic is needed in some cases to discriminate the call type from this information. The ITU-T V.8 *bis* related parameters are returned only when ITU-T V.8 *bis* is supported. Xxx Note that some textphones operate with DTMF tones. This package decodes initial DTMF signals according to the specification for text telephones in ITU-T V.18. DTMF detection may be indicated also from the "dd" package if that is active. + +##### 8.2.1.1 EventsDescriptor parameters + +None. + +##### 8.2.1.2 ObservedEventDescriptor parameters + +###### 8.2.1.2.1 Discriminating Tone Type + +**Parameter name:** Discriminating Tone Type +**Parameter ID:** dtt (0x0001) +**Description:** Indicates the call type associated with the discriminating tone. +**Type:** Enumeration +**Optional:** No +**Possible values:** + +| | | | +|-----------------|----------|---------------------------------------------| +| For FAX | | | +| CNG | (0x0001) | A T.30 fax calling tone | +| V21flag | (0x0002) | V21 tone and flags for fax answering | +| For TEXT | | | +| XCI | (0x0003) | An ITU-T V.18 XCI | +| V18txp1 | (0x0004) | An ITU-T V.18 txp signal in channel V.21(1) | +| V18txp2 | (0x0005) | An ITU-T V.18 txp signal in channel V.21(2) | +| BellHi | (0x0006) | A Bell 103 carrier on the high channel | +| BellLo | (0x0007) | A Bell 103 low channel | +| Baudot45 | (0x0008) | A Baudot45 initial carrier and characters | +| Baudot50 | (0x0009) | A Baudot50 initial carrier and characters | + +| | | | +|-------------------------------------|----------|-------------------------------------------------------------------------------------------------| +| Edt | (0x000A) | An EDT initial tone and characters | +| DTMF | (0x000B) | DTMF signals | +| CTM | (0x001C) | CTM signals | +| For DATA | | | +| Sig | (0x000C) | Modulation signal from a mode only used for data, i.e., not ITU-T V.21, ITU-T V.23 nor Bell 103 | +| Common to TEXT and DATA | | | +| CT | (0x000D) | An ITU-T V.25 calling tone | +| V21hi | (0x000E) | An ITU-T V.21 carrier on the higher frequency channel | +| V21lo | (0x000F) | An ITU-T V.21 carrier on the low frequency channel | +| V23hi | (0x0010) | An ITU-T V.23 high carrier | +| V23lo | (0x0011) | An ITU-T V.23 low carrier | +| CI | (0x0012) | An ITU-T V.8 CI with contents in "dtvalue" | +| Common to FAX, TEXT and DATA | | | +| ANS | (0x0013) | ITU-T V.25 ANS, equivalent to T.30 CED from answering terminal | +| ANSbar | (0x0014) | ITU-T V.25 ANS with phase reversals | +| ANSAM | (0x0015) | ITU-T V.8 ANSam | +| ANSAMbar | (0x0016) | ITU-T V.8 ANSam with phase reversals | +| CM | (0x0017) | ITU-T V.8 CM with contents in "dtvalue" | +| CJ | (0x0018) | ITU-T V.8 CJ | +| JM | (0x0019) | ITU-T V.8 JM with contents in "dtvalue" | +| ENDOFSIG | (0x001A) | End of reported signal detected reported for continuous or repeated signals | +| V8BIS | (0x001B) | ITU-T V.8 bis signal, with signal type in parameter V8bistype and value in "dtvalue" | + +**Default:** None + +###### 8.2.1.2.2 Discriminating Tone Value + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------| +| Parameter name: | Discriminating Tone Value | +| Parameter ID: | dtvalue (0x0002) | +| Description: | Indicates the data (if any) associated with the discriminating call tone. | +| Type: | String | +| Optional: | Yes | +| Possible values: | When used for ITU-T V.8 and ITU-T V.8 bis related messages, the following coding rules apply: | + +If an ITU-T V.8 *bis* message is detected without a preceding ITU-T V.8 *bis* signal, the preamble is reported as a 0 value. + +The contents of valid ITU-T V.8 *bis* message(s), if detected, are reported using hexadecimal octet coded string(s) (see clause 3.1). Flag detection and consumption, flag transparency 0-bit deletion and FCS checking are performed by the MG. The MG shall not report invalid messages (e.g., bad FCS). If two consecutive messages are detected but the first is invalid, the MG shall indicate this with a comma in front of the second message (e.g., <2nd message>). Two concatenated V.8 *bis* messages are reported with two consecutive indications. + +**Default:** None + +###### 8.2.1.2.3 V.8bis Type + +**Parameter name:** V8bis Type + +**Parameter ID:** v8bist (0x0004) + +**Description:** A detected ITU-T V.8 *bis* signal. ITU-T V.8 *bis* can be used for all modes. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** + +| | | | +|------|----------|-------------------------------------------------------------| +| ESi | (0x0001) | ITU-T V.8 bis signal ESi | +| ESr | (0x0002) | ITU-T V.8 bis signal ESr | +| MRe | (0x0003) | ITU-T V.8 bis signal MRe | +| MRdi | (0x0004) | ITU-T V.8 bis signal MRd from initiator | +| MRdr | (0x0005) | ITU-T V.8 bis signal MRd from responder | +| CRe | (0x0006) | ITU-T V.8 bis signal CRe | +| CRdi | (0x0007) | ITU-T V.8 bis signal CRd from initiator | +| CRdr | (0x0008) | ITU-T V.8 bis signal CRd from responder | +| MS | (0x0009) | ITU-T V.8 bis message MS with contents in "dtvalue" | +| CL | (0x000A) | ITU-T V.8 bis message CL with contents in "dtvalue" | +| CLR | (0x000B) | ITU-T V.8 bis message CLR with contents in "dtvalue" | +| ACK | (0x000C) | ITU-T V.8 bis message ACK with contents in "dtvalue" | +| NAK | (0x000D) | ITU-T V.8 bis message NAK with contents in "dtvalue" | + +**Default:** None + +#### 8.2.2 Call Type Discrimination Result + +**Event name:** Call Type Discrimination Result + +**Event ID:** calldisres (0x0002) + +**Description:** This event indicates that the MG has completed the Call Type discrimination process and has determined that a particular call type is supported. + +#### 8.2.2.1 EventsDescriptor parameters + +None. + +#### 8.2.2.2 ObservedEventDescriptor parameters + +###### 8.2.2.2.1 Discriminated Call Type + +| | | | | +|-------------------------|-------------------------|----------|------------------------------------------------------------------------------------------------| +| Parameter name: | Discriminated Call Type | | | +| Parameter ID: | dct (0x0001) | | | +| Type: | Enumeration | | | +| Optional: | No | | | +| Possible values: | Audio | (0x0000) | Default Audio negotiated | +| | For FAX | | | +| | T30 | (0x0001) | An ITU-T T.30 PSTN FAX call without ECM | +| | T30ECM | (0x0002) | An ITU-T T.30 PSTN FAX call with ECM (non-V.34) | +| | T30V34 | (0x0003) | An ITU-T T.30 PSTN FAX call with ITU-T V.34 (half-duplex) | +| | T38UDPTL | (0x0004) | An ITU-T T.38 FAX call using UDPTL | +| | T38TCP | (0x0005) | An ITU-T T.38 FAX call using TCP | +| | T37 | (0x0006) | An ITU-T T.37 FAX call | +| | FAXAUDIO | (0x0007) | For audio codec (e.g., ITU-T G.711 over RTP) | +| | | | This value is only used when the MG can determine that FAX is being used over the audio codec. | +| | For TEXT | | | +| | V18txp1 | (0x0008) | An ITU-T V.18 TEXT call carried in channel V.21(1) | +| | V18txp2 | (0x0009) | An ITU-T V.18 TEXT call carried in channel V.21(2) | +| | Baudot45 | (0x000C) | A Baudot45 TEXT call | +| | Baudot50 | (0x000D) | A Baudot50 TEXT call | +| | Edt | (0x000E) | An EDT TEXT call | +| | DTMF | (0x000F) | DTMF TEXT call | +| | CTM | (0x0014) | A CTM TEXT call | +| | TEXTAUDIO | (0x0021) | For audio codec (e.g., G.711 over | + +| | | | +|------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | RTP) | +| | | This value is only used when the MG can determine that TEXT is being used over the audio codec. | +| Minitel | (0x0024) | A Minitel TEXT call | +| | | This value is only used when the MG can determine that TEXT is being used over ITU-T V.23. | +| For Modem | | | +| BellHi | (0x000A) | A Bell 103 MODEM call on the high channel | +| BellLo | (0x000B) | A Bell 103 MODEM call on the low channel | +| V8 | (0x0015) | An ITU-T V.8 MODEM call | +| V8bis | (0x0016) | An ITU-T V.8 bis MODEM call
NOTE – V8/V8 bis is used to negotiate the modem type. Implementers are encouraged to use the actual modem types: ITU-T V.34, ITU-T V.61, ITU-T V.90, ITU-T V.91 and ITU-T V.92 where possible. | +| V21hi | (0x0010) | An ITU-T V.21 Modem call on the higher channel | +| V21lo | (0x0011) | An ITU-T V.21 Modem call on the low channel | +| V23hi | (0x0012) | An ITU-T V.23 Modem call on the high carrier | +| V23lo | (0x0013) | An ITU-T V.23 Modem call on the low carrier | +| MODEMAUDIO | (0x0022) | For audio codec (e.g., ITU-T G.711 over RTP)
This value is only used when the MG can determine that MODEM is being used over the audio codec. | +| V150MODEM | (0x0023) | For ITU-T V.150 modem relay | +| Default: | Audio (0x0000) | | + +### 8.3 Signals + +#### 8.3.1 V8 Signal + +| | | +|---------------------|----------------------------------------------------| +| Signal name: | V8 Signal | +| Signal ID: | v8sig (0x0001) | +| Description: | Indicates to the MG the type of V8 Signal to send. | + +**Signal type:** TO +**Duration:** Default provisioned in MG. The MGC may override this default by providing a duration. + +##### 8.3.1.1 Additional parameters + +###### 8.3.1.1.1 V.8 Signal Type + +**Parameter name:** V.8 Signal Type +**Parameter ID:** v8styp (0x0001) +**Description:** The type of ITU-T V.8 signal to send. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** CM (0x0001) +CJ (0x0002) +JM (0x0003) +CI (0x0004) +v8nosig (0x0005) Not used (reserved) +NOTE – The normal ITU-T H.248 signal replacement procedures are used to turn off a signal and shall be used. +**Default:** Provisioned + +###### 8.3.1.1.2 V.8 Signal Contents + +**Parameter name:** V8Sig Cont +**Parameter ID:** v8scont (0x0002) +**Description:** The ITU-T V.8 signals carry data for call type and modulation modes. These parameters can be supplied through the v8cont parameter. [ITU-T V.8] can be used for FAX, TEXT and DATA modes. +**Type:** String +**Optional:** Yes +**Possible values:** Allowed contents of the signals, coded as hexadecimal octet coded string +**Default:** Empty String ("") + +###### 8.3.1.1.3 V.18 XCI Enable + +**Parameter name:** V18 XCI Enable +**Parameter ID:** v18xcien (0x0003) +**Description:** XCI can be sent intermixed with CI transmission as specified in [ITU-T V.18] to stimulate plain Minitel terminals to respond as text telephones. Used in TEXT mode. +**Type:** Boolean +**Optional:** Yes + +**Possible values:** True XCI transmission enabled during ITU-T V.18 CI transmission + False XCI transmission disabled + +**Default:** True + +#### 8.3.2 Answer Signal + +**Signal name:** Answer Signal + +**Signal ID:** ans (0x0002) + +**Description:** The MGC uses this signal to order the MG to provide an answer signal. + +**Signal type:** TO + +**Duration:** Default provisioned in MG. The MGC may override this default by providing a duration. + +#### 8.3.2.1 Additional parameters + +###### 8.3.2.1.1 Answer Type + +**Parameter name:** ANS Type + +**Parameter ID:** AnsType (0x0001) + +**Description:** The type of answer signal to be sent. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** + +| | | | +|----------|----------|--------------------------------------------------------------------| +| ANS | (0x0001) | ITU-T V.25 ANS (equivalent to ITU-T T.30 CED) for all modes | +| ANSBAR | (0x0002) | ITU-T V.25 ANS with phase reversals for all modes | +| ANSAM | (0x0003) | ITU-T V.8 ANSam for all modes | +| ANSAMBAR | (0x0004) | ITU-T V.8 ANSam with phase reversals for all modes | +| V18txp1 | (0x0005) | An ITU-T V.18 txp signal played in ITU-T V.21 channel (1) for TEXT | +| V18txp2 | (0x0006) | An ITU-T V.18 txp signal played in ITU-T V.21 channel (2) for TEXT | +| ansnosig | (0x0007) | Not used (Reserved) | + +NOTE – The normal ITU-T H.248 signal replacement procedures are used to turn off a signal and shall be used. + +**Default:** Provisioned + +#### 8.3.3 Calling Signal + +**Signal name:** Calling Signal + +**Signal ID:** callsig (0x0003) + +**Description:** The MGC uses this signal to order the MG to provide a calling signal. + +**Signal Type:** TO +**Duration:** Default provisioned in MG. The MGC may override this default by providing a duration. + +#### 8.3.3.1 Additional parameters + +###### 8.3.3.1.1 Call Signal Name + +**Parameter name:** Call Signal Name +**Parameter ID:** csn (0x0001) +**Description:** Indicates the type of calling tone to be sent. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** +CT (0x0001) ITU-T V.25 calling tone used for TEXT and DATA +CNG (0x0002) ITU-T T.30 calling tone used for FAX with defined cadence +callnosig (0x0003) Not Used (Reserved) +NOTE – The normal ITU-T H.248 signal replacement procedures are used to turn off a signal and shall be used. +**Default:** Provisioned + +#### 8.3.4 V8bisSignal + +**Signal name:** V8bis Signal +**Signal ID:** v8bs (0x0004) +**Description:** The MGC uses this signal to order the MG to provide an ITU-T V.8 *bis* signal. +**Signal type:** BR +**Duration:** Default provisioned in MG. The MGC may override this default by providing a duration. + +##### 8.3.4.1 Additional parameters + +###### 8.3.4.1.1 V.8bis signal name + +**Parameter name:** V8bisSigname +**Parameter ID:** V8bsn (0x0001) +**Description:** ITU-T V.8 *bis* signals can be used in all modes. Some ITU-T V.8 *bis* signals contain data messages, supplied in V8bisSigContents. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** +ESi (0x0001) ITU-T V.8 *bis* signal ESi +ESr (0x0002) ITU-T V.8 *bis* signal ESr +MRe (0x0003) ITU-T V.8 *bis* signal MRe +MRdi (0x0004) ITU-T V.8 *bis* signal MRd from initiator + +| | | | +|-------|----------|---------------------------------------------------------------| +| MRdrh | (0x0005) | ITU-T V.8 bis signal MRd from responder on high power | +| CRel | (0x0006) | ITU-T V.8 bis signal CRe on low power | +| CRdi | (0x0007) | ITU-T V.8 bis signal CRd from initiator | +| CRdr | (0x0008) | ITU-T V.8 bis signal CRd from responder | +| MS | (0x0009) | ITU-T V.8 bis message MS with contents in signalvalue | +| CL | (0x000A) | ITU-T V.8 bis message CL with contents in signalvalue | +| CLR | (0x000B) | ITU-T V.8 bis message CLR with contents in signalvalue | +| ACK | (0x000C) | ITU-T V.8 bis message ACK with contents in signalvalue | +| NAK | (0x000D) | ITU-T V.8 bis message NAK with contents in signalvalue | +| MRdrl | (0x000E) | ITU-T V.8 bis signal MRd from responder on low power | +| CReh | (0x000F) | ITU-T V.8 bis signal CRe on high power | + +**Default:** Provisioned + +###### 8.3.4.1.2 V.8bis Signal Contents + +**Parameter name:** V8bis Signal Contents + +**Parameter ID:** V8bscont (0x0002) + +**Description:** Some of the ITU-T V.8 *bis* signals are messages. Their contents can be defined with the V8bscont parameter. + +ITU-T V.8 *bis* can be used in TEXT, FAX and DATA modes. + +The transmitted ITU-T V.8 *bis* message frame(s) is specified as hexadecimal octet coded string (see clause 3.1). Additional messages are delimited by comma characters. Flag generation, flag transparency 0-bit insertion and FCS generation are performed by the MG. If no data is provided by the MGC, no ITU-T V.21 carrier is generated beyond that used in segment 2. For two concatenated messages, the MG shall insert the required preamble between the first and second messages. + +**Type:** String + +**Optional:** Yes + +**Possible values:** Valid contents for the ITU-T V.8 *bis* signals + +**Default:** Empty string ("") + +#### 8.3.5 V18 Probe + +**Signal name:** V18 Probe + +**Signal ID:** v18prob (0x0005) + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Description: | This signal transmits the v18 probes in order to stimulate possible text telephones to transmit connect establishing signals. The probes are sent according to the specification in [ITU-T V.18]. For carrierless probes, the string in the "probemsg" property is transmitted. The probes are sent in the order specified in the property "probeorder". | +| Signal type: | BR | +| Duration: | Default provisioned in MG. The MGC may override this default by providing a duration. | + +#### 8.3.5.1 Additional parameters + +None. + +### 8.4 Statistics + +None. + +### 8.5 Procedures + +The Call Type Discrimination package is invoked for cases when the network connection is established and the call may enter one of the types of voice, fax, text telephone and modem. The package contains functionality to support the decision and connection processes. Once discriminated and the modem handshaking completed, an appropriate specific call type package should be invoked to complete the connection establishment on the modulation level and perform the session. + +When used for active modem negotiation, by means of commands from the MGC, the termination shall be made to operate according to the Recommendations for modem negotiation: [ITU-T V.25], [ITU-T V.8], [ITU-T V.8 *bis*], [ITU-T V.18] and [ITU-T T.30]. For probing according to [ITU-T V.18] during the negotiating process, the probing mechanism may be applied as defined in this package by turning the signal V18prob ON. + +The package may also be used for monitoring and reporting on data activity on the termination. + +#### 8.5.1 Informative description + +If the desired call type is known from the beginning, the Call Type Discrimination package should be invoked in order to actively try to establish a connection by sending out stimulating signals. By contrast, this package is also used to monitor the line to detect signals which are to be relayed to the Media Gateway Controller as input to a discrimination decision. Either the MGC or the MG may be assigned to perform the bearer level call discrimination signalling. In principle, when tones are reported to the MGC as events by an MG, the MG should avoid passing these tones via the media stream where possible, to reduce the possibility of unwanted duplicate tones (the MGC may subsequently order the MG to send these tones). Since the Call Type Discrimination package can be invoked to initially only monitor the line, it can be invoked on lines where voice calls are the most common mode of operation. There may be situations where this passive way of working results in less efficient or less reliable connection in fax/text/data mode. + +#### 8.5.2 Operation + +The package is activated on a termination of a line in an outgoing or incoming call where fax, text or data mode may be wanted. The properties are set to the enabled call types. + +#### 8.5.3 Operation for incoming calls + +The call is answered, the destination is evaluated, and the remote call initiated using packages and gateway functions outside the scope of this package. + +The MGC may order stimulating signals defined in this package to be sent on the line. + +The line is monitored for signals for the selected modes as defined in the "dtone" event descriptor. + +The MGC is expected to evaluate call type indications of all types; registered type of the destination, offered capabilities of the endpoint, invoked connection efforts of specific types from the endpoint. It can then use these call level indications to request the MG to further evaluate the call types. The MGC can then use the bearer level discriminating events from the MG to determine which call type should be used. + +As soon as the modem handshaking is complete, and a condition is reached that is valid for only one call type, a package for handling that call type should be invoked by the MGC, thus placing the MG into the desired mode of operation. + +The package contains components for conducting a negotiation procedure according to the different connection procedures defined in [ITU-T V.25], [ITU-T V.8], [ITU-T V.8 *bis*], [ITU-T T.30], [ITU-T T.38] and [ITU-T V.18]. (ITU-T V.8 *bis* support is optional and its availability can be interrogated through the property V8bissupport.) + +#### 8.5.4 Operation for transit calls, coming from and going to the switched network + +If no fax/text/data indication is present in the incoming call, the outgoing call is placed in voice mode, with the Call Type Discrimination package active. + +If the MGC is responsible for call discrimination signalling and if a valid tone is detected, it is reported to the MGC as an event. By actions of the MGC, it can then request the MG to signal to play the tone at the other end. The process continues according to the rules of the connection procedures until the call type can be determined and the mode of operation can be established. + +If the MG is responsible for call discrimination signalling then it shall perform the call type discrimination signalling itself and report the discriminated call type to the MGC via a notified event. + +#### 8.5.5 Operation for calls having one endpoint in the packet network + +If no fax/text/data indication is present in the incoming call, the outgoing call in the packet network is placed in voice mode. + +If a request to open a text channel, a fax channel or a data channel is made from the packet endpoint, the corresponding call type is tried on the switched network connection. + +If a signal indicating presence of a fax, textphone or a modem is received from the circuit switched network, and the call type can be evaluated, a corresponding channel is requested to the remote packet endpoint. If that request is acknowledged, the connection in the fax/text/data mode is completed on the switched side. + +If the call type cannot be evaluated, further signal exchange is performed on the switched interface until the call type is determined, and then the channel establishment continues on the packet side. + +#### 8.5.6 Cases when the call type cannot be determined from the signals + +For cases when the call type cannot be determined by the signal exchange, a decision must be taken by other means, or a transparent transport can be selected. + +The other means to make the decision may be a number analysis and comparison to registered user preferences or network defaults. + +Cases when the decision is not possible by signal analysis but need to be taken by external means: + +- ITU-T V.21: Used both for text telephony and for credit card transactions. The decision is recommended to be based on regional preferences and registering preference for data per destination number in regions where the default preference is for text telephony. +- ITU-T V.23: Used both for Minitel-based text telephones and for the Minitel information retrieval system. The conflict is only when an answering endpoint transmits the v23hi signal. A transparent data transport is recommended for this case. + +#### 8.5.7 Scenarios and call flows + +Signal sequence scenarios can be derived from the different connection protocols, with ITU-T T.38 being the main protocol for fax, ITU-T V.18 for text telephony and V.8/V.25 for data. + +The typical fax scenario is discriminated when CNG is detected from the calling end and a corresponding CED (ANS) and/or V.21 flags are detected at the answering end. For instances when either a CNG or ANS is not reported to the MGC, V.21 flags detection is sufficient for fax discrimination. Alternatively, an ITU-T V.8 CM or JM signal with a fax call type may be detected at either end. + +The text telephone scenario is discriminated when a text telephone call type is detected in ITU-T V.8, a text telephone function is negotiated in ITU-T V.8 *bis*, or a signal valid for text-only is detected. + +The data scenario is discriminated when a data call type is detected in V.8, a data function is negotiated in V.8 *bis*, or a data mode (not text) is entered by any part. + +In all cases, the handshaking protocol should be completed using the Call Type Discrimination package, before entering the selected data mode. + +Appendix I shows an example call establishment and discrimination flow for the MGC controlled case and the MG controlled case. + +#### 8.5.8 Initial characters + +For carrierless text telephones of the Baudot, EDT and DTMF types, the text transmission itself is needed for mode determination, and therefore the characters received during determination shall be stored. They shall be made available by local actions in the MG to be used by the txp package as initially received text for a seamless takeover of a connection. + +#### 8.5.9 Time-critical handling + +The default way of handling connection requests should be to propagate the connection request to the remote endpoint, and verify capabilities before positively responding to an incoming connection request for fax, text or data mode. It can, however, be very time-consuming to verify the endpoint capabilities and connect appropriate channels. The caller may time out between detection of off-hook and receiving a positive signal. Similar time-critical steps exist in the ITU-T V.8, ITU-T V.8 *bis*, ITU-T V.18, ITU-T T.30 and ITU-T V.25 procedures. The MGC must take action to compromise between the risk of one party timing out because of long waiting for a signal, and the risk of connecting a fax/text/data call before the capabilities of the endpoints are verified and the appropriate channels connected. One possible way to handle this risk is to define default actions to take before any party in the call times out. The ctyp package gives the MGC all necessary control to handle the connection process including such actions. + +For time-critical applications, the MGC may indicate to the MG through the *ctyp/MGCallSig* property that the MG shall be responsible for the Call Discrimination signalling. The result of the discrimination process is communicated to the MGC through the *ctype/callidisres* event. This method saves multiple MGC/MG signalling round-trip times during the MGC control of the modem tones. + +## 9 Fax package + +**Package name:** Fax +**Package ID:** fax (0x0012) +**Description:** The fax package is intended for enabling fax communication between terminals/applications in different networks or messaging environments. This package includes the mechanisms needed to identify ITU-T T.30 fax sessions (signals and data). +**Version:** 1 +**Extends:** None + +### 9.1 Properties + +#### 9.1.1 Fax Connection State + +**Property name:** Fax Connection State +**Property ID:** faxstate (0x0001) +**Description:** After successful Phase A connection with the ctyp package, the connection state property is used to request a fax connection. When placing a termination into a fax mode, the initial state shall be set to "Negotiating". +When this property is interrogated, it shall reflect the state of the achieved fax connection. A connection effort can be cancelled by setting the faxstate property to Idle. +**Type:** Enumeration +**Possible values:** + +| | | | +|---------------|----------|----------------------------------------------------------| +| Idle | (0x0001) | No connection efforts | +| Prepare | (0x0002) | Known in the termination and ready to accept connections | +| Negotiating | (0x0003) | Taking the initiative to establish a fax connection | +| TrainR | (0x0004) | Fax Phase B or later training as Receiver | +| TrainT | (0x0005) | Fax Phase B or later training as Transmitting | +| Connected | (0x0006) | Completed connection | +| EOP | (0x0007) | Procedures Complete | +| ProcInterrupt | (0x0008) | Procedure Interrupt Processing | +| Disconnect | (0x0009) | Premature Disconnect | + + +**Default:** Idle (0x0001) +**Characteristics:** Read/Write +**Defined in:** Termination State + +#### 9.1.2 Transmission Speed + +**Property name:** Transmission Speed +**Property ID:** trspd (0x0002) + +**Description:** The Transport parameter reflects the transmission speed seen at the analogue interface for the fax relay or the transmission speed used by the FAX termination (ITU-T T.30 PSTN). + +**Type:** Integer + +**Possible values:** 1200-33600 + +**Default:** Provisioned + +**Defined in:** Termination State + +**Characteristics:** Read/Write + +#### 9.1.3 PSTN Interface + +**Property name:** PSTN Interface + +**Property ID:** pstnif (0x0003) + +**Description:** The PSTN Interface parameter reflects the interface used to connect to a physical FAX machine. + +**Type:** Enumeration + +**Possible values:** + +| | | | +|--------|----------|----------------| +| NA | (0x0001) | Not applicable | +| V17 | (0x0002) | | +| V27TER | (0x0003) | | +| V29 | (0x0004) | | +| V21 | (0x0005) | | +| V34 | (0x0006) | | + +**Default:** Provisioned + +**Defined in:** Termination State + +**Characteristics:** Read/Write + +#### 9.1.4 Fax Transport + +**Property name:** Fax Transport + +**Property ID:** frpt (0x0004) + +**Description:** The Transport parameter reflects the transport mechanism selected for the fax termination. + +**Type:** Enumeration + +**Possible values:** + +| | | | +|--------|----------|------------------------------------------------------| +| T30 | (0x0001) | For ITU-T T.30 PSTN sessions without ECM | +| T30ECM | (0x0002) | For ITU-T T.30 PSTN sessions with ECM (non-V.34) | +| T30V34 | (0x0003) | For ITU-T T.30 PSTN sessions with V.34 (half-duplex) | + +**Default:** Provisioned + +**Characteristics:** Read/Write + +**Defined in:** Termination State + +## 9.2 Events + +#### 9.2.1 Fax Connection State Change + +**Event name:** Fax Connection State Change +**Event ID:** faxconnchange (0x0001) +**Description:** This event will occur when the fax connection state for the termination has changed. Its parameter is the new Fax Connection State. A connection effort that timed out returns the termination to the Idle state. + +#### 9.2.1.1 EventDescriptor parameters + +None. + +#### 9.2.1.2 ObservedEventDescriptor parameters + +###### 9.2.1.2.1 Fax Connection Change + +**Parameter name:** Fax Connection Change +**Parameter ID:** faxconnchng (0x0001) +**Type:** Enumeration +**Optional:** No +**Possible values:** + +| | | | +|---------------|----------|----------------------------------------------------------| +| Idle | (0x0001) | No connection efforts | +| Prepare | (0x0002) | Known in the termination and ready to accept connections | +| Negotiating | (0x0003) | Taking the initiative to establish a fax connection | +| TrainR | (0x0004) | Fax Phase B or later training as Receiver | +| TrainT | (0x0005) | Fax Phase B or later training as Transmitting | +| Connected | (0x0006) | Completed connection | +| EOP | (0x0007) | Procedures Complete | +| ProcInterrupt | (0x0008) | Procedure Interrupt Processing | +| EOF | (0x0009) | End of fax session, call terminating | +| PI | (0x000A) | Priority Interrupt; Switch to Voice | +| Disconnect | (0x000B) | Premature Disconnect | + +**Default:** Idle (0x0001) + +### 9.3 Signals + +None. + +### 9.4 Statistics + +#### 9.4.1 Number of Pages Transferred + +**Signal name:** Number of Pages Transferred +**Statistics ID:** pagestrans (0x0001) + +| | | +|-------------------------|------------------------------------------------------------------------| +| Description: | Number of pages of fax image data transferred through the termination. | +| Type: | Integer | +| Possible values: | 0 or more pages | +| Level: | Termination | + +### 9.4.2 Train Downs + +| | | +|-------------------------|-------------------------------------------------------| +| Statistic name: | Train Downs | +| Statistics ID: | traindowns (0x0002) | +| Description: | Number of times FAX trained down during transmission. | +| Type: | Integer | +| Possible values: | 0 or more train downs | +| Level: | Termination | + +### 9.5 Procedures + +The following are standard transport mechanisms for fax in different environments. + +- In ITU-T T.30: Use ITU-T T.30 procedures with and without ECM. +- In ITU-T T.30 Annexes C and F: Use ITU-T T.30 procedures selected via [ITU-T V.8] (used for ITU-T V.34 fax). + +#### 9.5.1 Function + +A termination with Fax provides a method for transfer of fax pages preceded by negotiations in the call set-up according to procedures defined for each environment. When matching capabilities exist, the appropriate sessions can be established in order to transfer pages of image or binary data. + +Real-time fax allows telecom users to transfer fax pages in real-time. The procedural aspects of GSTN fax are defined in [ITU-T T.30]. The compression methods used in transporting fax images are defined in [ITU-T T.4], [ITU-T T.6], [ITU-T T.81], [ITU-T T.82], [ITU-T T.85] and [ITU-T T.44]. In traditional ITU-T T.30 without error correction, images are transferred in a stream one page at a time. In ITU-T T.30 with error correction, images are transferred in blocks that are also known as partial pages. Numerous examples of fax sessions are contained in Appendix IV of [ITU-T T.30]. + +- For each transport environment, a suitable transport protocol must be selected to carry the image. Currently defined and recommended transport environments for ITU-T T.30 media streams that can be supported by this package are GSTN networks, where the procedures are defined in [ITU-T T.30], [ITU-T T.30] Annex A (for error correction), [ITU-T T.30] Annex C (duplex protocol) and [ITU-T T.30] Annex F (half duplex ITU-T V.34 protocol). + +#### 9.5.2 Process of adding Fax-capable terminations + +The MGs are responsible for detecting fax tones and relaying the related events to the MGC. The MGC should conduct Call Discrimination as defined within the Call Type Discrimination package in order to determine whether a fax or other mode is applicable. The MGC may choose to skip this if the MG is not capable of the Call Type Discrimination package. Once the MGC evaluates the tones and determines that the incoming call is fax, the MGC shall execute appropriate Modify commands to place the termination into a "Negotiating" state. + +### 9.5.3 Process of ending a fax call + +The MGs are responsible for detecting events that would cause the interruption of a fax call. The MGC is responsible for making the determination if this switch can be made and instruct the MGs to switch. It is also responsible for switching it back to fax. + +The MGC should receive indication that the fax call ends from the MG before receiving typical call termination indications. + +# 10 IP Fax package + +| | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | IPFax | +| Package ID: | ipfax (0x0013) | +| Description: | The Fax package is intended for enabling real-time or store-and-forward fax communication between terminals/applications in different networks or messaging environments. This package includes the mechanisms needed to transport ITU-T T.30 fax sessions (signals and data) in a real-time IP environment. The transport mechanism will be different for each environment where the package is used. | +| Version: | 2 | +| Extends: | None | + +## 10.1 Properties + +#### 10.1.1 Fax Connection State + +| | | | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------------------------------------------------| +| Property name: | Fax Connection State | | | +| Property ID: | faxstate (0x0001) | | | +| Description: | After successful Phase A connection with the ctyp package, the connection state property is used to request a fax connection. When placing a termination into a fax mode, the initial state shall be set to "Negotiating". When this property is interrogated, it shall reflect the state of the achieved fax connection. | | | +| Type: | Enumeration | | | +| Possible values: | Idle | (0x0001) | No connection efforts | +| | Prepare | (0x0002) | Known in the termination and ready to accept connections | +| | Negotiating | (0x0003) | Taking the initiative to establish a fax connection | +| | TrainR | (0x0004) | Fax Phase B or later training as Receiver | +| | TrainT | (0x0005) | Fax Phase B or later training as Transmitter | +| | Connected | (0x0006) | For completed connection | +| | EOP | (0x0007) | Procedures Complete | +| | ProcInterrupt | (0x0008) | Procedure Interrupt Processing | +| | Disconnect | (0x0009) | Premature Disconnect | + +**Default:** Idle (0x0001) +**Characteristics:** Read/Write +**Defined in:** Termination State + +#### 10.1.2 Transmission Speed + +**Property name:** Transmission Speed +**Property ID:** trspd (0x0002) +**Description:** The Transport property reflects the transmission speed seen at the IP interface for the fax relay. A value of zero (0) indicates that there is no speed set. +**Type:** Integer +**Possible values:** 0-33600 +**Default:** 0 +**Characteristics:** Read/Write +**Defined in:** Termination State + +### 10.1.3 T.38 Capabilities + +**Property name:** T.38 Capabilities +**Property ID:** T38Capabilities (0x0003) +**Description:** These capabilities describe the ITU-T T.38 fax termination. They are defined in Annex B of [ITU-T T.38]. Their SDP equivalents are defined in Annex D of [ITU-T T.38]. +**Type:** Sub-list of Enumeration +**Possible values:** +    FaxFillBitRemoval (0x0001) Indication of fill bit removal +    FaxTranscodingMMR (0x0002) For MMR transcoding availability +    FaxTranscodingJBIG (0x0003) For JBIG transcoding availability +    UDPFEC (0x0004) UDP Forward Error Correction +    UDPRedundancy (0x0005) UDP Redundancy Error Correction +**Default:** Provisioned +**Characteristics:** Read/Write +**Defined in:** Termination State + +### 10.1.4 T.38 Maximum Buffer Size + +**Property name:** T.38 Maximum Buffer Size +**Property ID:** T38MaxBufferSize (0x0004) +**Description:** This capability describes the ITU-T T.38 fax termination. They are defined in Annex B of [ITU-T T.38]. Their SDP equivalents are defined in Annex D of [ITU-T T.38]. +**Type:** Integer + +**Possible values:** 0-32765 +**Default:** Provisioned +**Characteristics:** Read/Write +**Defined in:** Termination State + +### 10.1.5 T.38 Maximum Datagram Size + +**Property name:** T.38 Maximum Datagram Size +**Property ID:** T38MaxDatagramSize (0x0005) +**Description:** This capability describes the T.38 fax termination. They are defined in Annex B of [ITU-T T.38]. Their SDP equivalents are defined in Annex D of [ITU-T T.38]. +**Type:** Integer +**Possible values:** 0-32765 +**Default:** Provisioned +**Characteristics:** Read/Write +**Defined in:** Termination State + +### 10.1.6 T.38 Version + +**Property name:** T.38 Version +**Property ID:** T38Version (0x0006) +**Description:** This is the ITU-T T.38 version number. +**Type:** Integer +**Possible values:** 0-32765 +**Default:** Provisioned +**Characteristics:** Read/Write +**Defined in:** Termination State + +#### 10.1.7 IP Fax Transport + +**Property name:** IP Fax Transport +**Property ID:** ipftrpt (0x0007) +**Description:** The IP Fax Transport parameter reflects the transport mechanism selected for the fax termination. +**Type:** Enumeration +**Possible values:** T38UDPTL (0x0001) For ITU-T T.38 using UDPTL +T38TCP (0x0002) For ITU-T T.38 using TCP +T37 (0x0003) For ITU-T T.37 +AUDIO (0x0004) For audio codec (e.g., ITU-T G.711 over RTP) +**Default:** Provisioned +**Characteristics:** Read/Write + +**Defined in:** Termination State + +### 10.2 Events + +#### 10.2.1 Fax Connection State Change + +**Event name:** Fax Connection State Change + +**Event ID:** faxconnchange (0x0001) + +**Description:** This event will occur when the fax connection state for the termination has changed. Its parameter reflects the new state. If a connection effort times out, it is reported in this event, with the faxconnchng parameter set to Idle. + +#### 10.2.1.1 EventDescriptor parameters + +None. + +#### 10.2.1.2 ObservedEventDescriptor parameters + +###### 10.2.1.2.1 Fax Connection Change + +**Parameter name:** Fax Connection Change + +**Parameter ID:** faxconnchng (0x0001) + +**Description:** Indicates the state of the fax connection + +**Type:** Enumeration + +**Optional:** No + +**Possible values:** + +| | | | +|---------------|----------|----------------------------------------------------------| +| Idle | (0x0001) | No connection efforts | +| Prepare | (0x0002) | Known in the termination and ready to accept connections | +| Negotiating | (0x0003) | Taking the initiative to establish a fax connection | +| TrainR | (0x0004) | Fax Phase B or later training as Receiver | +| TrainT | (0x0005) | Fax Phase B or later training as Transmitter | +| Connected | (0x0006) | For completed connection | +| EOP | (0x0007) | Procedures Complete | +| ProcInterrupt | (0x0008) | Procedure Interrupt Processing | +| EOF | (0x0009) | end of fax session, call terminating | +| PI | (0x000A) | Priority Interrupt; Switch to Voice | +| Disconnect | (0x000B) | Premature Disconnect | + +**Default:** Idle (0x0001) + +## 10.3 Signals + +None. + +### 10.4 Statistics + +#### 10.4.1 Pages Transferred + +| | | +|-------------------------|-----------------------------------------------------------------------| +| Statistic name: | Pages Transferred | +| Statistics ID: | pagestrans (0x0001) | +| Description: | Number of pages of fax image data transferred through the termination | +| Type: | Integer | +| Possible values: | 0 or more pages | +| Level: | Termination | + +#### 10.4.2 Train Downs + +| | | +|-------------------------|------------------------------------------------------| +| Statistic name: | Train Downs | +| Statistics ID: | traindowns (0x0002) | +| Description: | Number of times FAX trained down during transmission | +| Type: | Integer | +| Possible values: | 0 or more train downs | +| Level: | Termination | + +### 10.5 Procedures + +The following are standard transport mechanisms for fax in different environments. + +- In Annex B of [ITU-T T.38]: UDPTL or TCP in ITU-T T.38 fax-only communication channel environment. +- In Annex D of [ITU-T H.323]: UDPTL or TCP as selected with H.245 messages. +- In Annex D of [ITU-T T.38] (SIP): UDPTL or TCP as initiated with SDP. +- In Annex E of [ITU-T T.38]: UDPTL or TCP as initiated with ITU-T H.248. +- In [ITU-T T.37]: SMTP (MIME)/TCP. + +#### 10.5.1 Function + +A termination with Fax provides a method for transfer of fax pages preceded by negotiations in the call set-up according to procedures defined for each environment. When matching capabilities exist, the appropriate sessions can be established in order to transfer pages of image or binary data. + +Real-time fax allows telecom users to transfer fax pages in real-time. For each transport environment, a suitable transport protocol must be selected to carry the image. Currently defined and recommended transport environments for ITU-T T.30 media streams that can be supported by this package are: + +- 1) packet networks, where the procedures described in Annex B of [ITU-T T.38] can be used for setting up and conducting fax sessions, using TCP or UDPTL for the transport of ITU-T T.30 signals and data; +- 2) packet networks, where the procedures described in Annex D of [ITU-T H.323] can be used for setting up and conducting fax and voice sessions, using TCP or UDPTL as negotiated via ITU-T H.245; +- 3) packet networks, where the IETF Session Initiation Protocol (SIP) can be used for setting up and conducting fax sessions as defined in Annex D of [ITU-T T.38] using UDPTL or TCP for the transport of T.30 signals and data; + +- 4) packet networks, where ITU-T H.248 can be used for setting up and conducting fax sessions as defined in Annex E of [ITU-T T.38] using UDPTL or TCP for the transport of ITU-T T.30 signals and data; +- 5) packet networks, where the packets of ITU-T G.711 coded data (with ITU-T T.30 signals and data embedded) can be transported via RTP. + +The Extended Simple Mail Transport Protocol messaging environment over packet, that can be used alone or in conjunction with any of the environments above, where [ITU-T T.37] specifies the methods for transporting image/tiff files using the same compression methods as specified for use in [ITU-T T.30]. For information it can be noted that [b-IETF RFC 2301], [b-IETF RFC 3302], [b-IETF RFC 3191], [b-IETF RFC 3192] and [b-IETF RFC 2305] and [b-IETF RFC 2530], [b-IETF RFC 2879] and [b-IETF RFC 2532] specify these transport mechanisms. + +Interworking between these forms of fax can be achieved through the use of gateways with packages defined here. + +#### 10.5.2 Process of adding IP fax-capable terminations + +The MGs are responsible for detecting fax tones and relaying the related events to the MGC. The MGC should conduct Call Discrimination as defined within the Call Type Discrimination package in order to determine whether a fax or other mode is applicable. The MGC may choose to skip this if the MG is not capable of the Call Type Discrimination package. Once the MGC evaluates the tones and determines that the incoming call is fax, the MGC shall execute appropriate Modify commands to place the IP fax-capable termination into a "Negotiating" state. + +#### 10.5.3 Process of ending a fax call + +The MGs are responsible for detecting events that would cause the interruption of a fax call. The MGC is responsible for making the determination if this switch can be made, and instruct the MGs to switch. It is also responsible for switching it back to fax. + +The MGC should receive indication that the fax call ends from the MG before receiving typical call termination indications. + +#### 10.5.4 Informative example + +One possible instruction from an MGC to an MG to modify an existing context to an ITU-T T.38 media stream: + +``` +MGC to MG: +MEGACO/1.0 [123.123.123.4]:55555 +Transaction = 14 { + Context = 2000 { + Modify = RTP/1 { + Media { + Stream = 1 { + Local { +v=0 +c=IN IP4 124.124.124.222 +m=image 1111 udptl t38 +a=T38FaxRateManagement:transferredTCF +a=T38UdpEC:t38UDP FEC + } + } + } + } + } +} +``` + +# Appendix I + +## Call discrimination flows + +(This appendix does not form an integral part of this Recommendation.) + +This appendix details example call flows in Figures I.1 and I.2 for Call Establishment and discrimination. It details call controlling signalling, ITU-T H.248 and bearer and in-band signalling interactions. + +![Sequence diagram for MGC controlled call discrimination showing interactions between Modem1, MGC1, MG1 T1, MG1 T2, MG2 T3, MG2 T4, MGC2, and Modem2.](08f6ace0c83e7394657fa372b47aec04_img.jpg) + +``` + +sequenceDiagram + participant Modem1 + participant MGC1 + participant MG1_T1 as MG1 T1 + participant MG1_T2 as MG1 T2 + participant MG2_T3 as MG2 T3 + participant MG2_T4 as MG2 T4 + participant MGC2 + participant Modem2 + + Note left of Modem1: (1) IAM + Modem1->>MGC1: + MGC1->>MG1_T1: (2) ADD.req(T1,ctyp/calltype,event[ctypedtone]) + MG1_T1-->>MGC1: (3) ADD.resp(T1) + MGC1->>MG1_T2: (4) ADD.req(T2,V150 SDP,ctyp/calltype) + MG1_T2-->>MGC1: (5) ADD.resp(T2) + MGC1->>MGC2: (6) Setup + MGC2->>MG2_T3: (7) ADD.req(T3, V150 SDP,ctyp/calltype) + MG2_T3-->>MGC2: (8) ADD.resp(T3) + MGC2->>MG2_T4: (9) ADD.req(T4,ctyp/calltype,event[ctyp/dtone]) + MG2_T4-->>MGC2: (10) ADD.resp(T4) + MGC2->>Modem2: (11) IAM + Modem2-->>MGC2: + MGC2->>MGC1: (12) Alerting + MGC1-->>Modem1: + MGC1->>Modem1: (13) Connect + Modem2->>MG2_T4: (14) AT + MG2_T4->>MGC2: (15) Notify.req(ctype/dtone=modem type) + MGC2-->>MG2_T4: (16) Notify.ack + MG2_T4->>MG2_T3: (17) MOD.req(T3,signal=ctyp/SendANS) + MG2_T3-->>MG2_T4: (19) MOD.resp(T3) + MG2_T3->>MG1_T2: (18) SSE:VBD(AT) + MG1_T2-->>MG2_T3: (21) SSE:VBD' + MG1_T2->>MGC1: (20) Notify.req(T2,ctyp/dtone=modem) + MGC1-->>MG1_T2: (22) Notify.resp(T2) + MGC1->>MG1_T1: (23) MOD.req(T1,signal=ctyp/sendANS) + MG1_T1-->>MGC1: (24) MOD.resp(T1) + MGC1->>Modem1: (25) AT + +``` + +H.248.2(13)\_FI.1 + +Sequence diagram for MGC controlled call discrimination showing interactions between Modem1, MGC1, MG1 T1, MG1 T2, MG2 T3, MG2 T4, MGC2, and Modem2. + +Figure I.1 – MGC controlled call discrimination + +![Sequence diagram for MG controlled call discrimination. Lifelines: Modem1, MGC1, MG1 T1, MG1 T2, MG2 T3, MG2 T4, MGC2, Modem2. The diagram shows a call setup process where Modem1 sends an IAM to MGC1, which then uses ADD.req messages to T1, T2, T3, and T4. Responses are returned through the MGs to MGC1, which then sets up the call via MGC2 to Modem2. Subsequent signaling includes Alerting, Connect, AT, and Notify messages between the modems and the MGs.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +``` + +sequenceDiagram + participant Modem1 + participant MGC1 + participant MG1_T1 as MG1 T1 + participant MG1_T2 as MG1 T2 + participant MG2_T3 as MG2 T3 + participant MG2_T4 as MG2 T4 + participant MGC2 + participant Modem2 + + Modem1->>MGC1: (1) IAM + MGC1->>MG1_T1: (2) ADD.req(T1,ctyp/calltype,ctyp/MGCallSig,event[ctyp/calldisres]) + MG1_T1-->>MGC1: (3) ADD.resp(T1) + MGC1->>MG1_T2: (4) ADD.req(T2,V150 SDP,ctyp/calltype) + MG1_T2-->>MGC1: (5) ADD.resp(T2) + MGC1->>MGC2: (6) Setup + MGC2->>MG2_T3: (7) ADD.req(T3, V150 SDP,ctyp/calltype) + MG2_T3-->>MGC2: (8) ADD.resp(T3) + MGC2->>MG2_T4: (9) ADD.req(T4,ctyp/calltype, ctyp/MGCallSig, event[ctyp/calldisres]) + MG2_T4-->>MGC2: (10) ADD.resp(T4) + MGC2->>Modem2: (11) IAM + Modem2->>Modem1: (12) Alerting + Modem2->>Modem1: (13) Connect + Modem2->>MG2_T4: (14) AT + MG2_T4-->MG1_T1: (15) SSE:VBD(AT) + MG1_T1->>Modem1: (16) AT + MG1_T1-->MG2_T4: (17) SSE:VBD' + MG2_T4->>MGC2: (18) Notify.req(T4,ctyp/calldisres=modem type) + MGC2-->>MG2_T4: (19) Notify.ack(T4) + MG1_T1->>MGC1: (20) Notify.req(T1,ctyp/calldisres=modem type) + MGC1-->>MG1_T1: (21) Notify.ack(T1) + +``` + +H.248.2(Amd2)\_Fl.2 + +Sequence diagram for MG controlled call discrimination. Lifelines: Modem1, MGC1, MG1 T1, MG1 T2, MG2 T3, MG2 T4, MGC2, Modem2. The diagram shows a call setup process where Modem1 sends an IAM to MGC1, which then uses ADD.req messages to T1, T2, T3, and T4. Responses are returned through the MGs to MGC1, which then sets up the call via MGC2 to Modem2. Subsequent signaling includes Alerting, Connect, AT, and Notify messages between the modems and the MGs. + +**Figure I.2 – MG controlled call discrimination** + +## Bibliography + +- [b-IETF RFC 2301] IETF RFC 2301 (1998), *File Format for Internet Fax*. +- [b-IETF RFC 2305] IETF RFC 2305 (1998), *A Simple Mode of Facsimile Using Internet Mail*. +- [b-IETF RFC 2530] IETF RFC 2530 (1999), *Indicating Supported Media Features Using Extensions to DSN and MDN*. +- [b-IETF RFC 2532] IETF RFC 2532 (1999), *Extended Facsimile Using Internet Mail*. +- [b-IETF RFC 2879] IETF RFC 2879 (2000), *Content Feature Schema for Internet Fax (V2)*. +- [b-IETF RFC 3191] IETF RFC 3191 (2001), *Minimal GSTN address format in Internet Mail*. +- [b-IETF RFC 3192] IETF RFC 3192 (2001), *Minimal FAX address format in Internet Mail*. +- [b-IETF RFC 3302] IETF RFC 3302 (2002), *Tag Image File Format (TIFF) – Image/tiff MIME Sub-type Registration*. +- [b-3GPP TS 26.226] 3GPP TS 26.226 (2000), *3GPP cellular text telephone modem; General description*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.20-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.20-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2f54660e2ca42f1f9e1ea3e8e28dee52651981c2 --- /dev/null +++ b/marked/H/T-REC-H.248.20-201303-I_PDF-E/raw.md @@ -0,0 +1,376 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.20** + +(03/2013) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: The use of Local and +Remote Descriptors with ITU-T H.221 and +ITU-T H.223 multiplexing** + +Recommendation ITU-T H.248.20 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T H.248.20** + +## **Gateway control protocol: The use of Local and Remote Descriptors with ITU-T H.221 and ITU-T H.223 multiplexing** + +## **Summary** + +Recommendation ITU-T H.248.20 defines how the Local and Remote Descriptors are used within ITU-T H.248, ITU-T H.221 and ITU-T H.223 multiplexing (MUX) terminations to associate demultiplexed streams (logical channels) with ITU-T H.248.1 streams. + +This revision incorporates updates the allowed media values to align with the latest version of the Session Description Protocol (SDP). + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.248.20 | 2002-11-29 | 16 | +| 2.0 | ITU-T H.248.20 | 2013-03-16 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Logical channel parameters within the MUX termination ..... | 2 | +| 5.1 Text encoding ..... | 2 | +| 5.2 Binary encoding..... | 3 | +| 6 Example ..... | 3 | +| 6.1 Context model ..... | 4 | +| 6.2 The media descriptor for the TDM termination ..... | 4 | +| 6.3 The multiplex descriptor for the MUX termination ..... | 4 | +| 6.4 The media descriptor for the MUX termination..... | 4 | +| 6.5 The media descriptor for the RTP termination..... | 5 | + + + +## Recommendation ITU-T H.248.20 + +## Gateway control protocol: The use of Local and Remote Descriptors with ITU-T H.221 and ITU-T H.223 multiplexing + +## 1 Scope + +This Recommendation defines how ITU-T H.248.1 Local and Remote Descriptors are coded in the case of the use of ITU-T H.221 and ITU-T H.223 multiplexes. Figure 1 shows the scope of this Recommendation. + +![Diagram illustrating the scope of the Recommendation. A Media gateway contains a Circuit termination, a Multiplex termination (H.221/H.223), and a Packet termination. The Multiplex termination is connected to Stream 1, Stream 2, and Stream 3. The Packet termination is connected to Stream 2 and Stream 3. The Circuit termination is connected to Stream 1. The Multiplex termination is connected to the Packet termination via a dashed line labeled 'Context'. The scope of the Recommendation is indicated by a dashed box around the Multiplex termination and the Packet termination. The label 'Logical channel numbers' points to the streams. The diagram is labeled H.248.20_F01.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +The diagram shows a 'Media gateway' box containing three main components: 'Circuit termination' (an oval on the left), 'Multiplex termination' (an oval at the top center), and 'Packet termination' (an oval on the right). 'Stream 1' is a vertical line connecting the 'Circuit termination' and the 'Multiplex termination'. 'Stream 2' and 'Stream 3' are vertical lines connecting the 'Multiplex termination' and the 'Packet termination'. A dashed line labeled 'Context' runs horizontally between the 'Circuit termination' and the 'Packet termination', passing through the 'Multiplex termination'. A dashed box labeled 'Scope of Recommendation' encloses the 'Multiplex termination' and the 'Packet termination'. An arrow labeled 'H.221/H.223' points to the 'Multiplex termination'. An arrow labeled 'Logical channel numbers' points to 'Stream 2' and 'Stream 3'. The diagram is labeled 'H.248.20\_F01' at the bottom right. + +Diagram illustrating the scope of the Recommendation. A Media gateway contains a Circuit termination, a Multiplex termination (H.221/H.223), and a Packet termination. The Multiplex termination is connected to Stream 1, Stream 2, and Stream 3. The Packet termination is connected to Stream 2 and Stream 3. The Circuit termination is connected to Stream 1. The Multiplex termination is connected to the Packet termination via a dashed line labeled 'Context'. The scope of the Recommendation is indicated by a dashed box around the Multiplex termination and the Packet termination. The label 'Logical channel numbers' points to the streams. The diagram is labeled H.248.20\_F01. + +Figure 1 – Scope of this Recommendation + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.221] Recommendation ITU-T H.221 (2009), *Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices*. +- [ITU-T H.223] Recommendation ITU-T H.223 (2001), *Multiplexing protocol for low bit rate multimedia communication*. +- [ITU-T H.245] Recommendation ITU-T H.245 (2011), *Control protocol for multimedia communication*. +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*. +- [ITU-T H.324] Recommendation ITU-T H.324 (2009), *Terminal for low bit-rate multimedia communication*. +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. + +## 3 Definitions + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|------------------------------| +| ABNF | Augmented Backus-Naur Form | +| LCN | Logical Channel Number | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MUX | Multiplex | +| PER | Packed Encoding Rules | +| RTP | Real-time Transport Protocol | +| SDP | Session Description Protocol | +| TDM | Time Division Multiplex | + +## 5 Logical channel parameters within the MUX termination + +Every demultiplexed [ITU-T H.221] and [ITU-T H.223] media stream is associated with an [ITU-T H.248.1] Stream. For each ITU-T H.248.1 stream, a Stream Descriptor is defined within the MUX termination. The Logical Channel Number (LCN) values for the ITU-T H.221 and ITU-T H.223 media streams are defined in the Local and Remote Descriptors. Which descriptor is used depends on the media direction of the logical channel defined by a specific LCN (different LCN values may be used in each media direction of the logical channel). The Local Descriptor defines the media flowing in to the multiplexer, and the value in the Remote Descriptor defines the media flowing out from the multiplexer. If either descriptor is not defined, the media stream flow is not activated for the specific direction. A descriptor MAY be added later during the session (using the ITU-T H.248.1 Modify command) or the media stream is unidirectional. If the ITU-T H.221 and ITU-T H.223 media stream is bidirectional, both the Local and Remote Descriptors MUST be defined, even if the LCN value, codecs etc. are the same in both media stream directions. For the ITU-T H.248.1 Stream associated with the ITU-T H.245 control stream (LCN 0), only the Local Descriptor (e.g., if the control stream is not associated with an ITU-T H.248.1 Stream which also is defined elsewhere within the Context) may be used, even if the control stream is bidirectional. + +If the demultiplexed streams are forwarded to a packet network (e.g., IP network, transported using the Real-time Transport Protocol (RTP), the payload types, etc. (i.e., for the IP port) are defined within the ephemeral packet termination. The payload type values may, or may not, be the same within the multiplexed ITU-T H.221 and ITU-T H.223 stream and within the demultiplexed packet streams. + +### 5.1 Text encoding + +According to [ITU-T H.248.1], the stream Local and Remote Descriptors contain SDP. As such, SDP is required to describe how the stream maps to an ITU-T H.245 Logical Channel Number. The use of SDP for the ITU-T H.245 control stream is optional, since the LCN value MUST be 0 by default. The clauses below describe the necessary SDP syntax and values to describe this mapping for the ITU-T H.221 and ITU-T H.223 Multiplex termination. + +#### 5.1.1 "c=line" Line for H.221 and H.223 MUX termination + +The syntax of the connection field: + +**connection-field = "c=" nettype SP addrtype SP connection-address CRLF** + +The value of nettype is "H221" or "H223". The value of addrtype is "-". + +The value of connection-address is irrelevant, so any value which is allowed according to the ABNF rules can be used. This Recommendation uses the "-" value. + +#### 5.1.2 "m=line" Line for ITU-T H.221 and ITU-T H.223 MUX termination + +The syntax of the media field: + +**media-field = "m=" media SP port ["/" integer] SP proto 1\*(SP fmt) CRLF** + +The possible media values for media are "audio", "video", "data" and "application", depending on the media type within the specific ITU-T H.248.1 Stream. Value "application" is used if a Stream is defined for the demultiplexed ITU-T H.245 messages. + +NOTE – Some older applications may use the value "control". To aid interoperability MGs should be able to recognize "control". + +The value of port defines the ITU-T H.221 and ITU-T H.223 Logical Channel Number (LCN) associated with the ITU-T H.248.1 stream defined in the Local or Remote Descriptor (depending on the media flow direction) for that specific ITU-T H.248.1 stream. + +The use of the optional "/" integer parameter in the ITU-T H.221 and ITU-T H.223 MUX Termination, defining number of ports, is not defined by this Recommendation. + +The use of a media field for the demultiplexed control stream (ITU-T H.245 messages in an ITU-T H.324 network) is optional. Its use depends on whether the ITU-T H.245 messages are "transported" to specific termination(s) within the ITU-T H.248.1 Context, or if they are terminated at the MUX termination and then transported elsewhere using other mechanisms (e.g., as ITU-T H.248.1 Events). If a media field for the control stream is used, the value of port MUST be zero (the LCN value for the ITU-T H.245 control channel). + +The value of proto is "H221" or "H223". + +The fmt value defines the payload type used to encode the specific media within the multiplexed ITU-T H.223 stream. If the media is "control", the value of fmt is "H245". + +### 5.2 Binary encoding + +The Logical Channel Number is indicated through the use of Annex C/H.248.1 property "LCN" C007. A value of 0 indicates that the stream is an ITU-T H.245 control stream. The multiplex value of "H221" or "H223" shall indicate that non-zero ITU-T H.245 LCN values are multiplexed ITU-T H.221 and ITU-T H.223 streams. + +## 6 Example + +The following example describes a connection using the text encoding, where a multiplexed ITU-T H.223 stream, transported on a TDM bearer in a network using Annex C of [ITU-T H.324] ("H.324M"), is demultiplexed in the MG. The demultiplexed media streams are then transported on an IP network using separate RTP connections for each media. The ITU-T H.248.1 Context includes three terminations; one TDM termination, one MUX termination and one RTP termination. + +Three ITU-T H.248 Streams are used in the example: One for the multiplexed ITU-T H.223 stream (StreamID = 1), one for the demultiplexed audio stream (StreamID = 2) and one for the demultiplexed video stream (StreamID = 3). + +NOTE – Only the SDP parameters affected by this Recommendation are included in the examples. + +### 6.1 Context model + +Figure 2 shows the Context model used in the example. + +NOTE – ITU-T H.248.1 Stream 4 described in clause 6.4 is not shown in the picture since it is not associated with another termination in this example. It is used "internally" within the MUX Termination. + +![Diagram of the Context model. A 'Media gateway' box contains a dashed 'Context' box. Inside the Context box are 'TermTDM' and 'TermMUX' terminations. Outside the Context box is 'TermRTP'. 'Stream 1' connects 'TermTDM' to 'TermMUX'. 'Stream 2' and 'Stream 3' connect 'TermMUX' to 'TermRTP'. External lines connect 'TermTDM' and 'TermRTP' to the outside of the Media gateway. The label 'H.248.20_F02' is at the bottom right.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Diagram of the Context model. A 'Media gateway' box contains a dashed 'Context' box. Inside the Context box are 'TermTDM' and 'TermMUX' terminations. Outside the Context box is 'TermRTP'. 'Stream 1' connects 'TermTDM' to 'TermMUX'. 'Stream 2' and 'Stream 3' connect 'TermMUX' to 'TermRTP'. External lines connect 'TermTDM' and 'TermRTP' to the outside of the Media gateway. The label 'H.248.20\_F02' is at the bottom right. + +Figure 2 – Example context model + +### 6.2 The media descriptor for the TDM termination + +``` +TID= MyTDM/7/1 +Media = { + Stream = 1 { + Local, Remote, and LocalControl Descriptors + } +} +``` + +### 6.3 The multiplex descriptor for the MUX termination + +``` +Mux = H.223 {MyTDM/7/1} +``` + +### 6.4 The media descriptor for the MUX termination + +The payload type in the SDP m= lines defines the codec used for that specific stream received in the multiplexed TDM stream. + +``` +Media = { + Stream = 1 { + LocalControl = { + H.324 properties etc... + } + }, + Stream = 2 { + Local = { + v=0 + c=H223 - - + m=audio 1 H223 4 ;codec G.723.1, LCN 1 + }, + Remote = { + v=0 + c=H223 - - + m=audio 2 H223 4 ;codec G.723.1, LCN 2 + } + }, + Stream = 3 { + ;demultiplexed audio stream + }, + ;demultiplexed video stream +} +``` + +``` + + Local = { + v=0 + c=H223 - - + m=video 3 H223 34 ;codec H.263, LCN 3 + }, + Remote = { + v=0 + c=H223 - - + m=video 4 H223 34 ;codec H.263, LCN 4 + } + }, + Stream = 4 { ;demultiplexed H.245 stream + Local = { + v=0 + c=H223 - - + m=control 0 H223 H245 + } + } +} + +``` + +### 6.5 The media descriptor for the RTP termination + +The ITU-T H.245 Stream identifier values for the audio and video streams are identical to the values used in the MUX Termination. This way the streams are connected to each other within the Context, as defined in [ITU-T H.248.1]. + +``` + +Media = { + Stream = 2 { ;audio stream + Local = { + v=0 + c=IN IP4 192.133.124.134 + m=audio 20000 RTP/AVT 4 ;codec G.723.1 + }, + Remote = { + v=0 + c=IN IP4 186.156.231.198 + m=audio 23000 RTP/AVT 4 ;codec G.723.1 + } + }, + Stream = 3 { ;video stream + Local = { + v=0 + c=IN IP4 192.133.124.134 + m=video 20002 RTP/AVT 34 ;codec H.263 + }, + Remote = { + v=0 + c=IN IP4 186.156.231.198 + m=video 23002 RTP/AVT 34 ;codec H.263 + } + } +} + +``` + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.24-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.248.24-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/H/T-REC-H.248.24-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/H/T-REC-H.248.24-200307-I_PDF-E/raw.md b/marked/H/T-REC-H.248.24-200307-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..41f5d10f246786cda0f5420e85bd80eb9e5de884 --- /dev/null +++ b/marked/H/T-REC-H.248.24-200307-I_PDF-E/raw.md @@ -0,0 +1,361 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.24** + +(07/2003) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Multi-frequency tone +generation and detection packages** + +ITU-T Recommendation H.248.24 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| SYSTEMS AND TERMINAL EQUIPMENT FOR AUDIOVISUAL SERVICES | H.300–H.399 | +| SUPPLEMENTARY SERVICES FOR MULTIMEDIA | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation H.248.24** + +# **Gateway control protocol: Multi-frequency tone generation and detection package** + +## **Summary** + +This Recommendation defines two packages that provide multi-frequency tone generation and detection capabilities for H.248. + +###### **Source** + +ITU-T Recommendation H.248.24 was approved by ITU-T Study Group 16 (2001-2004) under ITU-T Recommendation A.8 procedure on 14 July 2003. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2003 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 2.1 Normative Reference..... | 1 | +| 2.2 Informative References ..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations..... | 1 | +| 5 Multi-frequency tone generation package ..... | 1 | +| 5.1 Properties..... | 1 | +| 5.2 Events ..... | 2 | +| 5.3 Signals ..... | 2 | +| 5.4 Statistics..... | 2 | +| 5.5 Procedures ..... | 2 | +| 6 Multi-frequency tone detection package ..... | 3 | +| 6.1 Properties..... | 3 | +| 6.2 Events ..... | 3 | +| 6.3 Signals ..... | 4 | +| 6.4 Statistics..... | 4 | +| 6.5 Procedures ..... | 4 | + + + +## Gateway control protocol: Multi-frequency tone generation and detection packages + +# 1 Scope + +This Recommendation defines two packages that provide multi-frequency tone generation and detection capabilities for H.248. The support of these packages is optional. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +## 2.1 Normative Reference + +- ITU-T Recommendation H.248.1 (2002), *Gateway Control Protocol: Version 2*. + +## 2.2 Informative References + +- ITU-T Recommendation Q.320 (1988), *Signal code for register signalling*. +- ITU-T Recommendation Q.441 (1988), *Signalling Code*. + +# 3 Definitions + +None. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-----|--------------------------| +| MF | Multi-Frequency | +| MG | Media Gateway | +| MGC | Media Gateway Controller | + +# 5 Multi-frequency tone generation package + +PackageID: mfg (0x003d) + +Version: 1 + +Extends: tonegen (0x0003) version 1 + +This package defines the basic MF tones as signals and extends the allowed values of parameter tl of playtone in tonegen. + +## 5.1 Properties + +None. + +## 5.2 Events + +None. + +### 5.3 Signals + +#### 5.3.1 MF signal code 0 + +SignalID: mf0 (0x0050) + +Generate MF signal code 0. The characteristics of the MF signal code, including frequencies and durations, are provisioned on the MG. + +Signal Type: Brief + +Duration: Provisioned + +Additional parameters: None + +Additional Values: + +mf0 (0x0050) is defined as a toneid for playtone. + +The other MF signal codes are specified in exactly the same way. A table with all signal names and signal Ids is included below. Note that each mf signal code is defined as both a signal and a toneid, thus extending the basic tone generation package. Also note that mf signal Ids are different from the names used in a digit map. + +| Signal Name | Signal ID/tone id | +|----------------------|-------------------| +| mf signal code 0 | mf0 (0x0050) | +| mf signal code 1 | mf1 (0x0051) | +| mf signal code 2 | mf2 (0x0052) | +| mf signal code 3 | mf3 (0x0053) | +| mf signal code 4 | mf4 (0x0054) | +| mf signal code 5 | mf5 (0x0055) | +| mf signal code 6 | mf6 (0x0056) | +| mf signal code 7 | mf7 (0x0057) | +| mf signal code 8 | mf8 (0x0058) | +| mf signal code 9 | mf9 (0x0059) | +| mf signal code KP | mfa (0x005a) | +| mf signal code KP' | mfb (0x005b) | +| mf signal code KP" | mfc (0x005c) | +| mf signal code KP''' | mfd (0x005d) | +| mf signal code ST | mfe (0x005e) | +| mf signal code ST' | mff (0x005f) | +| mf signal code ST" | mfg (0x0060) | +| mf signal code ST''' | mfh (0x0061) | + +## 5.4 Statistics + +None. + +## 5.5 Procedures + +None. + +## 6 Multi-frequency tone detection package + +PackageID: mfd (0x003e) + +Version: 1 + +Extends: tonedet (0x0004) version 1 + +This package defines the events required for basic MF tone detection. This package extends the possible values of tone id in the "start tone detected", "end tone detected" and "long tone detected" events. + +## 6.1 Properties + +None. + +### 6.2 Events + +### 6.2.1 MF signal code 0 + +EventID: mf0 (0x0050) + +Detect MF signal code 0. The characteristics of the MF signal code, including frequencies and durations, are provisioned on the MG. + +EventsDescriptor Parameters: None + +ObservedEventsDescriptor Parameters: None + +Additional Values: + +The events for the other MF signal codes are specified in exactly the same way. A table with all event names, event Ids and digit map symbols is included below. The event Ids are defined with same names as the signal Ids in package mfg. The additional tone id values are the same tone id values defined in package mfg. + +| Signal Name | Signal ID/tone id | Digitmap Symbol | +|----------------------|-------------------|-----------------| +| mf signal code 0 | mf0 (0x0050) | '0' | +| mf signal code 1 | mf1 (0x0051) | '1' | +| mf signal code 2 | mf2 (0x0052) | '2' | +| mf signal code 3 | mf3 (0x0053) | '3' | +| mf signal code 4 | mf4 (0x0054) | '4' | +| mf signal code 5 | mf5 (0x0055) | '5' | +| mf signal code 6 | mf6 (0x0056) | '6' | +| mf signal code 7 | mf7 (0x0057) | '7' | +| mf signal code 8 | mf8 (0x0058) | '8' | +| mf signal code 9 | mf9 (0x0059) | '9' | +| mf signal code KP | mfa (0x005a) | 'A' or 'a' | +| mf signal code KP' | mfb (0x005b) | 'B' or 'b' | +| mf signal code KP" | mfc (0x005c) | 'C' or 'c' | +| mf signal code KP''' | mfd (0x005d) | 'D' or 'd' | +| mf signal code ST | mfe (0x005e) | 'E' or 'e' | +| mf signal code ST' | mff (0x005f) | 'F' or 'f' | +| mf signal code ST" | mfg (0x0060) | 'G' or 'g' | +| mf signal code ST''' | mfh (0x0061) | 'H' or 'h' | + +### 6.2.2 Digitmap completion event + +EventID: ce (0x0004) + +Generated when a digit map completes. + +EventsDescriptor parameters: + +Digit map processing is activated only if a digit map parameter is present, specifying a digit map by name or by value. + +ObservedEventsDescriptor parameters: + +#### *Digit String* + +ParameterID: ds (0x0001) + +Type: string + +Possible values: + +A sequence of characters '0' through '9', 'A' through 'H', and the long duration modifier 'Z', and the interdigit threshold timers 'T', 'S' and 'L'. + +Description: + +The collected address string which matched part or all of an alternative event sequence specified in the digit map. + +##### *Termination Method* + +ParameterID: meth (0x0002) + +Type: enumeration + +Possible values: + +"UM" (0x0001) Unambiguous match + +"PM" (0x0002) Partial match, completion by timer expiry or unmatched event + +"FM" (0x0003) Full match, completion by timer expiry or unmatched event + +Description: + +Indicates the reason for generation of the event. + +### 6.3 Signals + +None. + +## 6.4 Statistics + +None. + +## 6.5 Procedures + +None. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.25-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.25-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dc0816f505254a89a53ae9804ab7d2be23315517 --- /dev/null +++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/raw.md @@ -0,0 +1,1177 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.25** + +(03/2013) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: Basic CAS packages** + +Recommendation ITU-T H.248.25 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +### Recommendation ITU-T H.248.25 + +# Gateway control protocol: Basic CAS packages + +## Summary + +Recommendation ITU-T H.248.25 defines basic channel associated signalling (CAS) and R1 packages and supplemental CAS packages that, in association with the ITU-T H.248 Protocol, can be used to control a media gateway (MG) from an external media gateway controller (MGC). + +This revision adds a new read-only property containing the current CAS state of the termination, to allow the MGC to resynchronize itself in the event it loses track of this state. + +This revision incorporates an update to the optionality of the "Pulse off" and "Pulse On" events. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|------------------------------|------------|-------------| +| 1.0 | ITU-T H.248.25 | 2003-07-14 | 16 | +| 1.1 | ITU-T H.248.25 (2003) Cor. 1 | 2004-03-15 | 16 | +| 2.0 | ITU-T H.248.25 | 2007-01-13 | 16 | +| 3.0 | ITU-T H.248.25 | 2013-03-16 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Assumptions and partitioning..... | 2 | +| 6 Basic CAS package..... | 2 | +| 6.1 Properties..... | 2 | +| 6.2 Events ..... | 3 | +| 6.3 Signals ..... | 5 | +| 6.4 Statistics..... | 6 | +| 6.5 Procedures ..... | 7 | +| 7 Basic CAS addressing package ..... | 8 | +| 7.1 Properties..... | 8 | +| 7.2 Events ..... | 8 | +| 7.3 Signals ..... | 10 | +| 7.4 Statistics..... | 11 | +| 7.5 Procedures ..... | 11 | +| 8 Robbed bit signalling package..... | 11 | +| 8.1 Properties..... | 11 | +| 8.2 Events ..... | 12 | +| 8.3 Signals ..... | 14 | +| 8.4 Statistics..... | 14 | +| 8.5 Procedures ..... | 14 | +| 9 Operator services and emergency services package..... | 14 | +| 9.1 Properties..... | 15 | +| 9.2 Events ..... | 15 | +| 9.3 Signals ..... | 15 | +| 9.4 Statistics..... | 15 | +| 9.5 Procedures ..... | 15 | +| 10 Operator services extension package..... | 15 | +| 10.1 Properties..... | 16 | +| 10.2 Events ..... | 16 | +| 10.3 Signals ..... | 17 | +| 10.4 Statistics..... | 18 | +| 10.5 Procedures ..... | 19 | + +| | Page | +|----------------------------------------------------------------------------------------------------------------------------|-------------| +| Appendix I – Call flows ..... | 20 | +| I.1    Basic single-stage MF or DTMF wink start or immediate start ..... | 20 | +| I.2    EAOSS termination – Telephone company operator services call ..... | 21 | +| I.3    EAOSS termination – IC/INC operator services call indirect through an
access tandem (Overlap outpulsing)..... | 22 | +| I.4    EAOSS termination – IC/INC operator services call indirect through an
access tandem (No overlap outpulsing)..... | 23 | +| I.5    EAOSS termination – IC/INC "National" operator direct to the IC/INC
(Overlap outpulsing)..... | 24 | +| I.6    EAOSS termination – IC/INC "National" operator direct to the IC/INC
(No overlap outpulsing)..... | 24 | +| I.7    EAOSS origination – Telephone operating company serves the call..... | 25 | + +# Gateway control protocol: Basic CAS packages + +# 1 Scope + +The basic channel associated signalling (CAS) package provides a baseline package. Basic CAS defines abstract events and signals that are common to all CAS protocols. For some protocols, basic CAS provides all of the functionality required to satisfy the line interface, such as North American single-stage dialling applications or R1 signalling. For other protocols, basic CAS provides a baseline package for which additional protocol specific extension packages can be defined. Further line signals and events required for international signalling protocols can be provided through extension packages. + +The basic CAS addressing package extends the basic CAS package to add the signals and events required for basic addressing. This would satisfy addressing functionality for many protocols such as North American single-stage dialling applications or R1 signalling. + +The robbed bit signalling (RBS) package, operator services and emergency services package and the operator services extension package can be used to provide functionality required in addition to the basic CAS package. + +The support of these packages is optional. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway Control Protocol: Version 3*. + +# 3 Definitions + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-------------------------------| +| CAS | Channel Associated Signalling | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| RBS | Robbed Bit Signalling | +| TS | Time Slot | + +# 5 Assumptions and partitioning + +The termination the MGC addresses is the channel. With TS16, the MG associates the line signal with the appropriate channel. + +For some applications, the basic CAS package provides all of the functionality needed to satisfy the interface. In other cases (e.g., operator services), additional supplementary packages may be needed to meet the complete interface requirements. This Recommendation includes three supplementary packages which may be used to provide additional functionality required by some interfaces: + +- The robbed bit signalling package provides basic RBS supervisory signalling that is required in addition to the basic CAS package. +- The operator services and emergency services package provides supervisory signalling that is specific to North American operator services and emergency services. +- The operator services extension package provides supervisory signalling that is specific to North American operator services and is required in addition to the operator services and emergency services package. + +# 6 Basic CAS package + +| | | +|----------------------|-----------------------------------------------------------------------------------------------------| +| Package name: | Basic CAS package | +| Package ID: | bcas (0x003f) | +| Description: | This package provides basic event and signal handling for terminations that support CAS signalling. | +| Version: | 2 | +| Extends: | None | + +## 6.1 Properties + +### 6.1.1 CAS near-end line state + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | CAS near-end line state | +| Property ID: | nels (0x0002) | +| Description: | Specifies the current CAS near-end line state of the termination by reflecting the last applied line signal. | +| Type: | Enumeration | +| Possible values: | Idle (0x01)            The CAS termination near-end is in the idle state
Seize (0x02)            The CAS termination near-end is in the seize state
SeizeAck (0x03) The CAS termination near-end is in the seize acknowledge state
Answer (0x04)    The CAS termination near-end is in the answer state | +| Default: | The last applied line signal. If no line signal has been applied by the MGC, Idle. | +| Defined in: | TerminationState Descriptor | +| Characteristics: | ReadOnly | + +### 6.1.2 CAS far-end line state + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | CAS far-end line state | +| Property ID: | fels (0x0003) | +| Description: | Specifies the current CAS far-end line state of the termination by reflecting the last detected line event. | +| Type: | Enumeration | +| Possible values: | Idle (0x01)      The CAS termination far-end is in the idle state
Seize (0x02)      The CAS termination far-end is in the seize state
SeizeAck (0x03) The CAS termination far-end is in the seize acknowledge state
Answer (0x04)    The CAS termination far-end is in the answer state | +| Default: | The last detected line event. If no line event has been detected by the MG, Idle. | +| Defined In: | TerminationState Descriptor | +| Characteristics: | ReadOnly | + +## 6.2 Events + +### 6.2.1 Seizure + +| | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Seizure | +| Event ID: | sz (0x0001) | +| Description: | Seizure event shall be reported when an incoming "Seizing" signal occurs on the termination. The event is reported by the MG if either the timed transition to this line signal is detected or the line signal already exists. The line signal condition against which the "Seizing" signal is verified is provisioned in the MG. | + +#### 6.2.1.1 EventsDescriptor parameters + +None. + +#### 6.2.1.2 ObservedEventsDescriptor parameters + +None. + +### 6.2.2 Seize acknowledge + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Seize acknowledge | +| Event ID: | sza (0x0002) | +| Description: | The Seize Acknowledge event shall be reported when an incoming "Seize Acknowledge" signal occurs on the termination. This event also acts as a start dial notification, indicating that out-pulsing should begin. For R1 interfaces, the event is reported when the "start dialling"/"proceed to send" signal occurs. For wink start trunks, the "Seize Acknowledge" event is reported when the trailing edge of the wink-start signal occurs. For immediate start trunks, the "Seize Acknowledge" event is provided by the media gateway as an immediate response to the request for that event from the MGC. | + +#### 6.2.2.1 EventsDescriptor parameters + +None. + +#### 6.2.2.2 ObservedEventsDescriptor parameters + +None. + +### 6.2.3 Answer + +**Event name:** Answer +**Event ID:** ans (0x0003) +**Description:** The Answer event shall be reported when an incoming line signal "Answer" occurs on the termination. The event is reported by the MG if either the timed transition to this line signal is detected or the line signal already exists. The line signal condition against which the "Answer" signal is verified is provisioned in the MG. + +#### 6.2.3.1 EventsDescriptor parameters + +None. + +#### 6.2.3.2 ObservedEventsDescriptor parameters + +None. + +### 6.2.4 Idle + +**Event name:** Idle +**Event ID:** idle (0x0004) +**Description:** This event applies to an incoming interface and is reported when a "Clear" or "Idle" line signal occurs on the termination. For an R1 interface, the Idle event shall be reported when an "Idle" line signal occurs on the termination. For robbed bit signalling digital interfaces, it corresponds to an "on-hook" indication on the termination. The event is reported by the MG if either the timed transition to this line signal is detected or the line signal already exists. The condition against which the signal is verified is provisioned in the MG. + +#### 6.2.4.1 EventsDescriptor parameters + +##### 6.2.4.1.1 Idle guard timing + +**Parameter name:** Idle guard timing +**Parameter ID:** idlgt (0x0001) +**Description:** Specifies whether the MG shall start an idle guard timer for the receipt of the "Idle" signal. If the idle guard timer expires prior to the detection of idle signal and the CAS Failure event is active, the MG shall report a CAS Failure event with a "IDLTO" error. The timer value is provisioned on the MG. +**Type:** Boolean +**Optional:** Yes +**Possible values:** On when the idle guard timing is requested +Off when the idle guard timing is turned off. + +**Default:** Off + +#### 6.2.4.2 ObservedEventsDescriptor parameters + +None. + +### 6.2.5 CAS failure + +**Event name:** CAS failure + +**Event ID:** casf (0x0005) + +**Description:** Reports general CAS failures associated with this package. + +#### 6.2.5.1 EventsDescriptor parameters + +None. + +#### 6.2.5.2 ObservedEventsDescriptor parameters + +##### 6.2.5.2.1 Error code + +**Parameter name:** Error code + +**Parameter ID:** ec (0x0001) + +**Description:** Describes the reasons for CAS failures encountered at an MG. The MGC may take corrective actions upon receiving one of these error codes (clear the call, reattempt on new trunk, etc.). "ULS" is reported when the MG encounters a line signal on the CAS trunk other than the one expected for the current state of the trunk. "LTO" is reported when a timeout occurs locally on the MG while waiting for a line signal on the CAS trunk. "SME" is reported when the MG encounters an internal CAS protocol or processing error. "IDLTO" is reported when the idle guard timer expires on the MG while waiting for the idle line signal on the trunk. + +**Type:** Enumeration + +**Optional:** No + +**Possible values:** ULS (0x0001) Unexpected line signal +LTO (0x0002) Line signal timeout +SME (0x0004) Protocol State machine malfunction +IDLTO (0x0005) Idle Guard Timeout + +**Default:** None + +## 6.3 Signals + +### 6.3.1 Seize + +**Signal name:** Seize + +**Signal ID:** sz (0x0001) + +**Description:** Applies a "Seizing" signal on the termination. The signal that is actually sent on the physical termination is provisioned in the MG. + +**Signal type:** Brief + +**Duration:** Not applicable (See "Signal Procedures".) + +#### 6.3.1.1 Additional parameters + +None. + +### 6.3.2 Seize acknowledge + +**Signal name:** Seize acknowledge +**Signal ID:** sza (0x0002) +**Description:** Applies a "Seize Acknowledge" signal on the termination. The signal that is actually sent on the physical termination is provisioned in the MG. +**Signal type:** Brief +**Duration:** Not applicable (See "Signal Procedures".) + +#### 6.3.2.1 Additional parameters + +None. + +### 6.3.3 Answer + +**Signal name:** Answer +**Signal ID:** ans (0x0003) +**Description:** Applies an "Answer" signal on the termination. The signal that is actually sent on the physical termination is provisioned in the MG. +**Signal type:** Brief +**Duration:** Not applicable (See "Signal Procedures".) + +#### 6.3.3.1 Additional parameters + +None. + +### 6.3.4 Idle + +**Signal name:** Idle +**Signal ID:** idle (0x0004) +**Description:** This signal applies to an outgoing interface and is used to idle a trunk. This signal is used as a clear signal in some variants to clear down a call either in the forward or backward direction. The signal that is actually sent on the physical termination is provisioned in the MG. +**Signal type:** Brief +**Duration:** Not applicable (See "Signal Procedures".) + +#### 6.3.4.1 Additional parameters + +None. + +## 6.4 Statistics + +None. + +## 6.5 Procedures + +### 6.5.1 Glare procedures + +MGs shall have a configurable glare information element on a per-DS0 basis that can be set to indicate whether the MG is the controlling or non-controlling "switch". + +In the case of PBX interconnect, PBXs are either preconfigured or can be configured to behave as non-controlling switches. In this case, if they see an off-hook that exceeds the allowable wink length, they will attach a receiver, go on-hook and await digits for a new call. The PBX will, in addition, retry its original call on another trunk. + +In the case where the DS0 is configured for the non-controlling switch, the MG will indicate a glare occurrence by reporting a seizure event to the MGC. Upon receipt of the seizure event, the MGC begins procedures to release the outgoing call attempt and begins procedures to process the incoming call attempt. + +If the MG is a controlling switch, when glare is detected, the MG will wait for a timeout value (default value of 4 seconds) until the incoming off-hook changes to an on-hook state, at which time it will start out-pulsing in the normal manner. If the timeout occurs before the state change to on-hook occurs, the far end has refused to back down. This may occur if both ends of the interface are provisioned as the controlling switch. In this case, when the timeout occurs, the MG reports the seizure event to the MGC. The MGC, upon receipt of the notify with seizure event, begins procedures to back down on the outgoing call attempt and begins procedures to process the incoming call attempt. + +It is possible for internal glare to occur between the MGC and the MG. With internal glare, the MG detects a seizure event on the DS0, signals a seize acknowledge and reports the seizure event to the MGC. At the same time, the MG reports the seizure event to the MGC, the MGC sends a request to the MG to signal a seizure on the DS0. In this case, the start dial has already been signalled by the MG in response to the incoming seizure. Therefore, the MGC must back down on the outgoing call attempt. The MG, upon receipt of the modify request to signal a seizure, recognizes internal glare has occurred and takes no action on the modify request. The MGC, upon receipt of the notify with seizure event, recognizes internal glare has occurred and begins procedures to back down on the outgoing call attempt and begins procedures to process the incoming call attempt. + +### 6.5.2 Timestamp procedures + +Inclusion of a timestamp in the ObservedEvents descriptor is mandatory for the basic CAS package. The timestamp reflects the detection time for the event and may be used by services (e.g., automatic message accounting) on the MGC. + +### 6.5.3 Signal procedures + +A line signal must always be present on a CAS interface. Therefore, the Seizure, Answer, Seize Acknowledge and Idle signals shall be considered to be state changes in the line signal state, rather than as persistent signals in themselves. The state change shall be considered to be completed instantaneously by the MG. Consequently, there is no active signal to be terminated by any subsequent event detection. + +The MG shall maintain the existing line signal state on a CAS interface until such time as the MGC sends a new line signal to the MG to change state. + +### 6.5.4 Property procedures + +The nels property shall reflect the most recently successfully applied line signal from the MGC. As per the requirements in clause 6.5.3, the line signal shall not change without explicit instruction from the MGC and therefore the nels property shall also require explicit signal application in order to alter its value. If the MGC has not applied a signal to this termination, then the value is Idle. + +The fels property shall reflect the most recent line event detected by the MG. The property shall be updated upon detection of the event, and shall not depend upon the success or failure of the reporting of the event to the MGC. If the MG has not detected an event, then the value is Idle. + +Note that the default value for the properties are defined as the last applied signal or detected event. This has the effect of negating the "reset" of the properties due to a Subtract Command, by making the MG reset the property to its current value. This is necessary to provide continuity for the properties and to align the values to the actual working of the CAS interface. + +# 7 Basic CAS addressing package + +| | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | Basic CAS addressing package | +| Package ID: | bcasaddr (0x006d) | +| Description: | This package defines events and signals that are specific to Basic CAS Addressing and are required in addition to the base CAS functionality provided by the bcas package. | +| Version: | 1 | +| Extends: | bcas version 1 | + +## 7.1 Properties + +None. + +## 7.2 Events + +### 7.2.1 Address + +| | | +|---------------------|---------------------------------------------------------------------------------------------------| +| Event name: | Address | +| Event ID: | addr (0x0006) | +| Description: | Reports the collected address parameter and termination method for the digits received by the MG. | + +#### 7.2.1.1 EventsDescriptor parameters + +##### 7.2.1.1.1 Address coding + +| | | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Address coding | +| Parameter ID: | ac (0x0001) | +| Description: | Specifies the possible coding options of incoming Digit events as tones and/or DC pulses. The default value is the value(s) provisioned as an attribute of the circuit associated with the signal. | +| Type: | Sublist of enumeration | +| Optional: | Yes | + +| | | | +|-------------------------|---------------|---------------------------| +| Possible values: | MF (0x0001) | Multifrequency | +| | DTMF (0x0002) | Dual-tone Multi-frequency | +| | DP (0x0003) | Dial Pulse | +| Default: | Provisioned | | + +#### 7.2.1.2 ObservedEventsDescriptor parameters + +##### 7.2.1.2.1 Digit string + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Digit string | +| Parameter ID: | ds (0x0001) | +| Description: | The string of collected digits that matched all or part of the sequence specified in the digit map. | +| Type: | String | +| Optional: | No | +| Possible values: | A sequence of the characters '0' through '9' as well as 'A' through 'H'. 'A' through 'H' are used for MF signalling: refer to the symbols defined for the digit map in the MF Tone Detection package. 'A' through 'F' are used for DTMF signalling – refer to the symbols defined for the digit map in the DTMF Detection package. | +| Default: | None | + +##### 7.2.1.2.2 Termination method + +| | | +|-------------------------|--------------------------------------------------------------------------------------| +| Parameter name: | Termination method | +| Parameter ID: | meth (0x0002) | +| Description: | Indicates the reason for the generation of the Address event. | +| Type: | Enumeration | +| Optional: | No | +| Possible values: | UM (0x0001) Unambiguous Match
PM (0x0002) Partial Match
FM (0x0003) Full Match | +| Default: | None | + +### 7.2.2 CAS failure + +| | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| EventID: | casf (0x0005) | +| Description: | Extends the bcas casf event to handle general failure or abnormal line and register signalling conditions associated with this package. | + +#### 7.2.2.1 EventsDescriptor parameters + +None. + +#### 7.2.2.2 ObservedEventsDescriptor parameters + +##### 7.2.2.2.1 Error code + +| | | +|------------------------|------------| +| Parameter name: | Error code | +|------------------------|------------| + +| | | +|-------------------------|----------------------------------------------------------------------------------| +| Parameter ID: | ec (0x0001) | +| Description: | Describes the failure reason. | +| Type: | Enumeration | +| Optional: | No | +| Possible values: | RTO (0x0003) Register Signalling Timeout
ADR (0x0006) Error during outpulsing | +| Default: | None | + +## 7.3 Signals + +### 7.3.1 Address + +| | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Signal name: | Address | +| SignalID: | addr (0x0005) | +| Description: | Applies the address signals in the form of DTMF, dial-pulse or MF-tones on the trunk. The actual frequency, cadence, duration and amplitude values for the multi-frequency tones that convey the address information are provisioned in the MG. | +| Signal type: | Brief | +| Duration: | Provisioned | + +#### 7.3.1.1 Additional parameters + +##### 7.3.1.1.1 Digit string + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Digit string | +| Parameter ID: | ds (0x0001) | +| Description: | The digit string that needs to be sent as address signals. | +| Type: | String | +| Optional: | No | +| Possible values: | A sequence of the characters '0' through '9' as well as 'A' through 'H' ('A' through 'H' used for MF signalling; refer to the symbols defined for the digit map in the MF Tone Detection package). | +| Default: | None | + +##### 7.3.1.1.2 Address delay + +| | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Address delay | +| Parameter ID: | ad (0x0002) | +| Description: | Specifies a timed delay that is applied prior to the signalling address being outpulsed. The address delay is optional. If the address delay parameter is not provided, the MG uses the provisioned value by default. | +| Type: | Integer | +| Optional: | Yes | +| Possible values: | 0 and up in milliseconds | + +**Default:** Provisioned + +##### 7.3.1.1.3 Address coding + +**Parameter name:** Address coding + +**Parameter ID:** ac (0x0003) + +**Description:** Specifies the coding of Digit String parameter in tones or DC pulses. Address Coding is optional; if not provided, the MG uses the value provisioned as an attribute of the circuit associated with the signal. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** DTMF (0x0001) DTMF Digits +MF (0x0002) MF Digits +DP (0x0003) Dial Pulse Digits + +**Default:** Provisioned + +## 7.4 Statistics + +None. + +## 7.5 Procedures + +None. + +# 8 Robbed bit signalling package + +**Package name:** Robbed bit signalling package + +**Package ID:** rbs (0x0040) + +**Version:** 1 + +**Extends:** None + +**Description:** This package defines events and signals that are specific to robbed bit signalling and are required in addition to the base CAS functionality provided by the bcas package. + +## 8.1 Properties + +### 8.1.1 Pulse generation duration + +**Property name:** Pulse generation duration + +**Property ID:** psgen (0x0001) + +**Description:** Specifies the duration for a pulse signal. + +**Type:** Integer + +**Possible values:** Any non-negative integral number of milliseconds + +**Defined in:** TerminationState descriptor + +**Characteristics:** Read/Write + +### 8.1.2 Minimum pulse detection duration + +**Property name:** Minimum pulse detection duration +**Property ID:** minpsdet (0x0002) +**Description:** Specifies the minimum duration for detecting a pulse. +**Type:** Integer +**Possible values:** Any non-negative integral number of milliseconds +**Defined in:** TerminationState descriptor +**Characteristics:** Read/Write + +### 8.1.3 Maximum pulse detection duration + +**Property name:** Maximum pulse detection duration +**Property ID:** maxpsdet (0x0003) +**Description:** Specifies the maximum duration for detecting a pulse. +**Type:** Integer +**Possible values:** Any non-negative integral number of milliseconds +**Defined in:** TerminationState descriptor +**Characteristics:** Read/Write + +## 8.2 Events + +### 8.2.1 Pulse off + +**Event name:** Pulse off +**Event ID:** psoff (0x0001) +**Description:** The MG detects and reports a timed transition from on-hook to off-hook (leading edge) to on-hook (trailing edge). The parameter "pulse timeout" can be optionally included to specify a timeout for the receipt of the pulse. The default value for the timer is provisioned in the MG. The minimum and maximum duration of the pulse are defined by the minimum pulse detection duration and maximum pulse detection duration properties respectively. + +#### 8.2.1.1 EventsDescriptor parameters + +##### 8.2.1.1.1 Pulse timeout + +**Parameter name:** Pulse timeout +**Parameter ID:** psto (0x0001) +**Type:** Integer +**Optional:** Yes +**Possible values:** Any non-negative integral number of milliseconds +**Description:** Specifies the timer for the receipt of the pulse. A value of 0 indicates a timer should not be applied. +**Default:** Provisioned + +#### 8.2.1.2 ObservedEventsDescriptor parameters + +None. + +### 8.2.2 Pulse on + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Pulse on | +| EventID: | pson (0x0002) | +| Description: | The MG detects and reports a timed transition from off-hook to on-hook (leading edge) to off-hook (trailing edge). The parameter "pulse timeout" can be optionally included to specify a timeout for the receipt of the pulse. The default value for the timer is provisioned in the MG. The minimum and maximum duration of the pulse are defined by the minimum pulse detection duration and maximum pulse detection duration properties respectively. | + +#### 8.2.2.1 EventsDescriptor parameters + +##### 8.2.2.1.1 Pulse timeout + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------| +| Parameter name: | Pulse timeout | +| Parameter ID: | psto (0x0001) | +| Description: | Specifies the timer for the receipt of the pulse. A value of 0 indicates a timer should not be applied. | +| Type: | Integer | +| Optional: | Yes | +| Possible values: | Any non-negative integral number of milliseconds | +| Default: | Provisioned | + +##### 8.2.2.1.2 ObservedEventsDescriptor parameters + +None. + +### 8.2.3 RBS failure + +| | | +|---------------------|--------------------------------------------------------| +| Event name: | RBS failure | +| Event ID: | rbsfail (0x0003) | +| Description: | Reports a failure condition when a RBS failure occurs. | + +#### 8.2.3.1 EventsDescriptor parameters + +None. + +#### 8.2.3.2 ObservedEventsDescriptor parameters + +##### 8.2.3.2.1 Error code + +| | | +|-------------------------|-------------------------------------------------| +| Parameter name: | Error code | +| Parameter ID: | ec (0x0001) | +| Description: | Describes the RBS failure reason. | +| Type: | Enumeration | +| Optional: | No | +| Possible values: | PSTO (0x0001) Timeout waiting for a pulse event | + +**Default:** None + +## 8.3 Signals + +### 8.3.1 Pulse off-hook + +**Signal name:** Pulse off-hook + +**Signal ID:** psoff (0x0001) + +**Description:** The MG signals a timed transition from on-hook to off-hook (leading edge) to on-hook (trailing edge). + +**Signal type:** Brief + +**Duration:** Defined by pulse generation duration property. + +#### 8.3.1.1 Additional parameters + +None. + +### 8.3.2 Pulse on-hook + +**Signal name:** Pulse on-hook + +**Signal ID:** pson (0x0002) + +**Description:** The MG signals a timed transition from off-hook to on-hook (leading edge) to off-hook (trailing edge). + +**Signal type:** Brief + +**Duration:** Defined by pulse generation duration property. + +#### 8.3.2.1 Additional parameters + +None. + +## 8.4 Statistics + +None. + +## 8.5 Procedures + +### 8.5.1 Timestamp procedures + +Inclusion of a timestamp in the ObservedEvents descriptor is mandatory for the RBS package. The timestamp reflects the detection time for the event and may be used by services (e.g., automatic message accounting) on the MGC. + +# 9 Operator services and emergency services package + +**Package name:** Operator services and emergency services package + +**Package ID:** oses (0x0041) + +**Description:** This package defines the CAS events and signals that are required for North American operator services and North American emergency services signalling. + +**Version:** 1 + +**Extends:** None + +## 9.1 Properties + +None. + +## 9.2 Events + +### 9.2.1 Ringback + +**Event name:** Ringback +**Event ID:** rgbk (0x0001) +**Description:** The ringback event is reported when a ringback signal is detected. The type of ringback signal and characteristics of the ringback signal are provisioned in the MG. + +#### 9.2.1.1 EventsDescriptor parameters + +None. + +#### 9.2.1.2 ObservedEventsDescriptor parameters + +None. + +## 9.3 Signals + +### 9.3.1 Ringback + +**Signal name:** Ringback +**Signal ID:** rgbk (0x0001) +**Description:** Applies a ringback signal on the termination. The type of ringback signal and characteristics of the ringback signal are provisioned on the MG. +**Signal type:** Brief +**Duration:** Provisioned + +#### 9.3.1.1 Additional parameters + +None. + +## 9.4 Statistics + +None. + +## 9.5 Procedures + +None. + +# 10 Operator services extension package + +**Package name:** Operator services extension package +**Package ID:** osext (0x0042) +**Description:** This package defines the CAS events and signals that are specific to North American operator services signalling and are required in addition to the events and signals defined in the operator services and emergency services package. +**Version:** 1 + +**Extends:**                   oses version 1 + +## **10.1 Properties** + +None. + +## **10.2 Events** + +### **10.2.1 Recall** + +**Event name:**           Recall + +**Event ID:**               rcl (0x0002) + +**Description:**       The recall event is reported when a recall signal is detected on a termination. The recall signal is a timed transition from off-hook to on-hook (leading edge) to off-hook (trailing edge). The duration of the timed transition is provisioned on the MG. + +#### **10.2.1.1 EventsDescriptor parameters** + +None. + +#### **10.2.1.2 ObservedEventsDescriptor parameters** + +None. + +### **10.2.2 Coin collect** + +**Event name:**           Coin collect + +**Event ID:**               cc (0x0003) + +**Description:**       The coin collect event is reported when a coin collect signal is detected on a termination. The type of coin collect signal and characteristics of the coin collect signal are provisioned on the MG. + +#### **10.2.2.1 EventsDescriptor parameters** + +None. + +#### **10.2.2.2 ObservedEventsDescriptor parameters** + +None. + +### **10.2.3 Coin return** + +**Event name:**           Coin return + +**Event ID:**               cr (0x0004) + +**Description:**       The coin return event is reported when a coin return signal is detected on a termination. The type of coin return signal and characteristics of the coin return signal are provisioned on the MG. + +#### **10.2.3.1 EventsDescriptor parameters** + +None. + +#### **10.2.3.2 ObservedEventsDescriptor parameters** + +None. + +### 10.2.4 Operator attached + +**Event name:** Operator attached +**Event ID:** oa (0x0005) +**Description:** The operator attached event is reported when an operator attached signal is detected on a termination. The type of operator attached signal and characteristics of the operator attached signal are provisioned on the MG. + +#### 10.2.4.1 EventsDescriptor parameters + +None. + +#### 10.2.4.2 ObservedEventsDescriptor parameters + +None. + +### 10.2.5 Operator released + +**Event name:** Operator released +**Event ID:** or (0x0006) +**Description:** The operator released event is reported when an operator released signal is detected on a termination. The type of operator released signal and characteristics of the operator released signal are provisioned on the MG. + +#### 10.2.5.1 EventsDescriptor parameters + +None. + +#### 10.2.5.2 ObservedEventsDescriptor parameters + +None. + +## 10.3 Signals + +### 10.3.1 Recall + +**Signal name:** Recall +**Signal ID:** rcl (0x0002) +**Description:** Applies a timed transition from off-hook to on-hook (leading edge) to off-hook (trailing edge). +**Signal type:** Brief +**Duration:** Provisioned + +#### 10.3.1.1 Additional parameters + +None. + +### 10.3.2 Coin collect + +**Signal name:** Coin collect +**Signal ID:** cc (0x0003) +**Description:** Applies a coin collect signal on the termination. The type of coin collect signal and characteristics of the coin collect signal are provisioned on the MG. + +**Signal type:** Brief +**Duration:** Provisioned + +#### 10.3.2.1 Additional parameters + +None. + +### 10.3.3 Coin return + +**Signal name:** Coin return +**Signal ID:** cr (0x0004) +**Description:** Applies a coin return signal on the termination. The type of coin return signal and characteristics of the coin return signal are provisioned on the MG. +**Signal type:** Brief +**Duration:** Provisioned + +#### 10.3.3.1 Additional parameters + +None. + +### 10.3.4 Operator attached + +**Signal name:** Operator attached +**Signal ID:** oa (0x0005) +**Description:** Applies an operator attached signal on the termination. The type of operator attached signal and characteristics of the operator attached signal are provisioned on the MG. +**Signal type:** Brief +**Duration:** Provisioned + +#### 10.3.4.1 Additional parameters + +None. + +### 10.3.5 Operator released + +**Signal name:** Operator released +**Signal ID:** or (0x0006) +**Description:** Applies an operator released signal on the termination. The type of operator released signal and characteristics of the operator released signal are provisioned on the MG. +**Signal type:** Brief +**Duration:** Provisioned + +#### 10.3.5.1 Additional parameters + +None. + +## 10.4 Statistics + +None. + +## **10.5 Procedures** + +None. + +# Appendix I + +## Call flows + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Basic single-stage MF or DTMF wink start or immediate start + +Origination: + +![](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +| PSTN/PBX | MG | MGC | +|-------------------------------------------------------------------------------------------------|----|---------------------------------| +| Start with a request to be notified of seizure and report digits (digit map referenced). | | | +| | | ←request— | +| —seize→ | | —"bcas/sz"—→ | +| ←seize ack and start dialling— | | ←"bcas/sza"— | +| —digits→ | | —"mfd/ce"—→
digits available | +| Later, when the other end answers: | | | +| ←off-hook— | | ←"bcas/ans"— | + +Termination: + +![](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +| MGC | MG | PSTN/PBX | +|--------------------------------------------------------------------------------------------------------------------|----|-----------------------------------------------| +| Start with embedded request to do "sz" and if start dialling ("sza") occurs automatically outpulse address: | | | +| —embedded request→ | | —Seizure→ | +| ←"bcas/sza"— | | ←wink/delay dial followed by proceed to send— | +| The MG has a reflex action to doing a seizure with request for "sza": | | | +| | | —digits→ | +| NOTE – Digits outpulsed automatically because of the embedded request. | | | + +## I.2 EAOSS termination – Telephone company operator services call + +The following call flow also applies to operator services signalling interfaces defined prior to exchange access operator services signalling (EAOSS). + +![](a149b400127a3e3e50b3c98d27c5935c_img.jpg) + +| MGC | MG | PSTN/PBX | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------| +| Start with a request to seize and report the start dialling event. Option – can use an embedded request for the first set of address digits. | | | +| —request→ | | —Seizure→ | +| ←"bcas/sza"← | | ←wink← | +| Send a request to signal the first stage of digits (i.e., called) and look for an answer. Signal Completion event can be (optionally) used to indicate when outpulsing is complete. | | | +| —signal addr1→ | | —addr1→ | +| ←"g/sc"← | | | +| ←"bcas/ans"← | | ←off-hook← | +| Send a request to signal the second stage of digits (i.e., ANI). Signal completion event is used to indicate when outpulsing is complete. | | | +| —signal addr2→ | | —addr2→ | +| ←"g/sc"← | | | + +## I.3 EAOSS termination – IC/INC operator services call indirect through an access tandem (Overlap outpulsing) + +The following call flow also applies to Feature Group D (FGD) signalling with the exception of an acknowledgment wink in place of the off-hook hold request. + +![](b235edb1dbe659e2782c9a0e47775ca4_img.jpg) + +| MGC | MG | PSTN/PBX | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------| +| Start with a request to seize and report the start dialling event. Option – can use an embedded request for the first set of address digits. | | | +| —request→ | | —Seizure→ | +| ←"bcas/sza"← | | ←wink← | +| Send a request to signal the first stage of digits (i.e., called) and look for a wink (i.e., a pulse). The first stage of digits consists of KP0ZZXXXXST/STP (national) or KP1N'XXXXCCCST/STP (international). | | | +| —signal addr1→ | | —addr1→ | +| ←"rbs/psoff"← | | ←off-hook← | +| Send a request to signal the second stage of digits (i.e., ANI). Signal completion event is used to indicate when outpulsing is complete, which supports overlap outpulsing. | | | +| —signal addr2→ | | —addr2→ | +| ←"g/sc"← | | | +| Send a request to signal the third stage of digits (i.e., called) and look for an acknowledgment wink or an off-hook request for hold. | | | +| —signal addr3→ | | —addr3→ | +| ←"rbs/psoff"← | | ←wink← | +| | OR | | +| ←"bcas/ans"← | | ←off-hook← | +| Timeouts for the receipt of the winks are specified using parameter psto. The minimum and maximum durations of the winks are specified using the minpsdet and maxpsdet properties. | | | + +## I.4 EAOSS termination – IC/INC operator services call indirect through an access tandem (No overlap outpulsing) + +This call flow is an optimization of the previous call flow when overlap outpulsing is not required. + +![](dcb5711d118ae6753b0e12f86eda37db_img.jpg) + +| MGC | MG | PSTN/PBX | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------| +| Start with a request to seize and report the start dialling event.
This call flow includes an embedded request to signal the first set of address digits (i.e., KP0ZZXXXST/STP for national or KP1N'XXXXCCST/STP for international) and report an event of wink (i.e., a pulse). | | | +| —request→ | | —Seizure→ | +| ←"bcas/sza"← | | ←wink← | +| | | —addr1→ | +| ←"rbs/psoff"← | | ←off-hook← | +| Send a request to signal the second stage of digits (i.e., ANI) and third (i.e., called) stages of digits. Additionally, look for the acknowledgment wink or off-hook hold request. | | | +| —signal addr2/3→ | | —addr2→ | +| | | —addr3→ | +| ←"rbs/psoff"← | | ←wink← | +| | OR | | +| ←"bcas/ans"← | | ←off-hook← | +| Timeouts for the receipt of the winks are specified using parameter psto. The minimum and maximum durations of the winks are specified using the minpsdet and maxpsdet properties. | | | + +## I.5 EAOSS termination – IC/INC "National" operator direct to the IC/INC (Overlap outpulsing) + +![](5414f65867392f05ba0063b208eeb5e1_img.jpg) + +| MGC | MG | PSTN/PBX | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------| +| Start with a request to seize and report the start dialling event. Option – can use an embedded request for the first set of address digits. | | | +| —request→ | | —Seizure→ | +| ←"bcas/sza"— | | ←wink— | +| Send a request to signal the first stage of digits (i.e., ANI). Signal Completion event is used to indicate when outpulsing is complete, which supports overlap outpulsing. | | | +| —signal addr1→ | | —addr1→ | +| ←"g/sc"— | | | +| Send a request to signal the second stage of digits (i.e., called) and look for the acknowledgment wink or off-hook hold request. | | | +| —signal addr2→ | | —addr2→ | +| | | —addr3→ | +| ←"rbs/psoff"— | | ←wink— | +| | OR | | +| ←"bcas/ans"— | | ←off-hook— | +| Timeouts for the receipt of the wink are specified using parameter psto. The minimum and maximum durations of the wink are specified using the minpsdet and maxpsdet properties. | | | + +## I.6 EAOSS termination – IC/INC "National" operator direct to the IC/INC (No overlap outpulsing) + +This call flow is an optimization of the previous call flow when overlap outpulsing is not required. + +![](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +| MGC | MG | PSTN/PBX | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------| +| Start with a request to seize and report the start dialling event. Include an embedded request with a signal list and look for an event of wink or offhook. | | | +| —request→ | | —Seizure→ | +| ←"bcas/sza"— | | ←wink— | +| | | —addr1→ | +| | | —addr2→ | +| ←"rbs/psoff"— | | ←wink— | +| | OR | | +| ←"bcas/ans"— | | ←off-hook— | +| Timeouts for the receipt of the wink are specified using parameter psto. The minimum and maximum durations of the wink are specified using the minpsdet and maxpsdet properties. | | | + +## I.7 EAOSS origination – Telephone operating company serves the call + +In this call flow, the MGC is the telephone operating company switch that is providing operator services. The call originates from a PSTN EO and terminates to the MGC for operator handling. Following operator handling, the call completes to the packet network (not shown). + +![](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) + +| PSTN/PBX | MG | MGC | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-------------| +| Start with a request to be notified of seizure and report digits (digit map referenced). | | | +| | | ←request— | +| —seize→ | | —"bcas/sz"→ | +| ←wink— | | | +| —addr1→ | | —"mfd/ce"→ | +| Based on the digits received (i.e., KP0ZZXXXXST/STP, KP1N'XXXXCCCST/STP) and the resulting translation, the MGC determines the call should be served. Send a request to signal a wink and report the next set of digits (i.e., ANI). | | | +| | | ←request— | +| ←wink— | | | +| —addr2→ | | —"mfd/ce"→ | +| Send a request to report the next set of digits and signal an acknowledgment wink or off-hook in place of the acknowledgment wink (i.e., if MGC data indicates hold should be applied for this IC). | | | +| | | ←request— | +| —addr3→ | | —"mfd/ce"→ | +| ←wink— | | | +| OR | | | +| ←off-hook— | | | + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.26-201303-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/H/T-REC-H.248.26-201303-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2b1ff77fd3b898edeede3bff888843855360cea --- /dev/null +++ b/marked/H/T-REC-H.248.26-201303-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ba4100f23d3c567bf21ab25b20b09fbe268340f164821c3c44fde0cfa4c81a8 +size 15956 diff --git a/marked/H/T-REC-H.248.26-201303-I_PDF-E/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg b/marked/H/T-REC-H.248.26-201303-I_PDF-E/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25bb01f89829563516a2b6626c8c1b50af796395 --- /dev/null +++ b/marked/H/T-REC-H.248.26-201303-I_PDF-E/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:608cd485deec7058c1e6e870f6ee859665bd421022a36b6b0a18e29803a6b0b7 +size 21139 diff --git a/marked/H/T-REC-H.248.26-201303-I_PDF-E/7978d5099076a93ea7969446444502f8_img.jpg b/marked/H/T-REC-H.248.26-201303-I_PDF-E/7978d5099076a93ea7969446444502f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ee77efb9d4cc7ef19cc2358cb29c641aaac3e56 --- /dev/null +++ b/marked/H/T-REC-H.248.26-201303-I_PDF-E/7978d5099076a93ea7969446444502f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:607aea2bd45481190309b40eb6fb6c079ddf4ce54713cab7ce5ba2e3c1450c1b +size 15980 diff --git a/marked/H/T-REC-H.248.26-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.248.26-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.248.26-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.248.26-201303-I_PDF-E/c6caafc29a33844653a0e827c8666204_img.jpg b/marked/H/T-REC-H.248.26-201303-I_PDF-E/c6caafc29a33844653a0e827c8666204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efe0997c88e54bda01e3be291ee4c96d222a6a2b --- /dev/null +++ b/marked/H/T-REC-H.248.26-201303-I_PDF-E/c6caafc29a33844653a0e827c8666204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d1d5e919c63965583783cc8a643a41976d13facd040bd8ec3d44a222ca5edb7 +size 10560 diff --git a/marked/H/T-REC-H.248.26-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.26-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..12217ee8ba5d18464a53c8c6e76be4c07c5f4fe3 --- /dev/null +++ b/marked/H/T-REC-H.248.26-201303-I_PDF-E/raw.md @@ -0,0 +1,1072 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.26** + +(03/2013) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Enhanced analogue +lines packages** + +Recommendation ITU-T H.248.26 + +# **ITU-T H-SERIES RECOMMENDATIONS** **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|-------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.248.26 + +# Gateway control protocol: Enhanced analogue lines packages + +## Summary + +Recommendation ITU-T H.248.26 defines several packages that provide support for extended line supervision and metering analogue lines capabilities for Recommendation ITU-T H.248.1. This version adds a phased metering signal suitable for use with complex metering scenarios that are beyond the capability of the metering signals already present in the package. It also introduces a new package to perform metering pulse detection by media gateways, and updates all the packages in this Recommendation to conform to the new packages template. + +This revision incorporates updates to the default behaviour of the "Pulse Repetition Interval", "Burst Pulse Count" and "Pulse Repetition Interval" parameters. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|------------------------------|------------|-------------| +| 1.0 | ITU-T H.248.26 | 2003-07-14 | 16 | +| 1.1 | ITU-T H.248.26 (2003) Cor. 1 | 2004-03-15 | 16 | +| 1.2 | ITU-T H.248.26 (2003) Amd. 1 | 2005-01-08 | 16 | +| 2.0 | ITU-T H.248.26 | 2005-01-08 | 16 | +| 3.0 | ITU-T H.248.26 | 2013-03-16 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Extended Analogue Line Supervision package ..... | 3 | +| 5.1 Properties..... | 3 | +| 5.2 Events ..... | 3 | +| 5.3 Signals ..... | 3 | +| 5.4 Statistics..... | 3 | +| 5.5 Procedures ..... | 4 | +| 6 Automatic Metering package..... | 4 | +| 6.1 Properties..... | 4 | +| 6.2 Events ..... | 4 | +| 6.3 Signals ..... | 5 | +| 6.4 Statistics..... | 9 | +| 6.5 Procedures ..... | 9 | +| 7 Metering Pulse Detection package ..... | 18 | +| 7.1 Properties..... | 18 | +| 7.2 Events ..... | 18 | +| 7.3 Signals ..... | 20 | +| 7.4 Statistics..... | 20 | +| 7.5 Error code ..... | 21 | +| 7.6 Procedures ..... | 21 | +| Bibliography..... | 24 | + + + +## Gateway control protocol: Enhanced analogue lines packages + +# 1 Scope + +The Analogue Line Supervision package defined in Annex E of [ITU-T H.248.1] supports basic telephony services, using on-hook and off-hook events, and a ringing signal. Some telephony services delivered over analogue line terminations have additional supervisory signalling requirements that are not met by the Analogue Line Supervision package. The packages defined in this Recommendation are intended to meet the needs of the following supervisory signalling functions: + +- *Line-side answer supervision*: This function provides a positive notification to a calling line that the called line has answered. This notification may be used by customer premises equipment, for example, to begin timing the call for local billing or charging purposes. +- *Network disconnect*: Many switching systems provide this signal following the termination of an active call if a party remains off-hook for some period of time following the other party going on-hook. The network disconnect notification may be used by customer premises equipment to release resources associated with the call. +- *Metering pulses*: Metering services provide subscribers with real-time information about charging of calls in progress. These services make use of customer premises equipment that shows a count of "units" consumed by chargeable calls, where each unit has a fixed monetary value. To increment the counter in the metering equipment, the switching system sends certain kinds of pulses over the line, either during the call or immediately following termination of the call. These pulses typically consist of short bursts of 12-kHz or 16-kHz tones, although other types of metering pulse such as brief periods of polarity reversal or 50-Hz tones are also seen. + +To meet these needs, two supplemental packages are introduced: + +- The Extended Analogue Line Supervision package is defined as an extension of the Basic Analogue Line Supervision package, and includes two new signals: Line-Side Answer Supervision and Network Disconnect. This package provides support for all the Loop-Start supervisory signalling requirements identified by [b-Telcordia GR-506-CORE]. +- The Automatic Metering package provides a means to apply metering pulses on an analogue line termination. The package includes: + - signals requesting the automatic application of pulses at fixed intervals as well as the application of pulse bursts; + - statistics that may be used to track the actual number of pulses applied; and + - an event that may be used to trigger periodic reporting of the count of pulses applied. + +This Recommendation introduces a phased metering signal suitable for use with complex metering scenarios. It also introduces a new metering detection package that can be used to instruct the MG to detect and report metering pulses generated by a network peer. + +The support of these packages is optional. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway Control Protocol: Version 3*. + +## 3 Definitions + +This Recommendation defines the following terms: + +- 3.1 **add-on charge:** An optional one-time charge incurred mid-call. +- 3.2 **charge interval:** The frequency at which charges are incurred. Some metering models do not accommodate this parameter. +- 3.3 **charge rate:** The rate at which currency charges are applied in a call in currency per second. +- 3.4 **phase duration:** The length of a phase. Phase duration may be finite or infinite. +- 3.5 **pulse count:** The count of the number of pulses which are to be applied. +- 3.6 **pulse count per charge interval:** The pulse count for a specific charge interval, calculated as the product of Tariff Pulse Rate and Charge Interval ( $PCCI = TPR \times CI$ ). +- 3.7 **pulse repetition interval:** See definition in clause 6.3.1.1.2. +- 3.8 **set-up charge:** An optional one-time charge for call set-up. +- 3.9 **tariff pulse rate:** The rate (pulses per second) at which pulses are applied as derived from the tariff rate data and pulse conversion data specified by the service provider. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +- CI Charge Interval +- MG Media Gateway +- MGC Media Gateway Controller +- PC Pulse Count +- PCCI Pulse Count per Charge Interval +- PD Phase Duration +- PRI Pulse Repetition Interval +- TPR Tariff Pulse Rate + +# 5 Extended Analogue Line Supervision package + +**Package Name:** Extended Analogue Line Supervision package +**Package ID:** xal (0x0043) +**Description:** This package defines events and signals necessary to support analogue telephony services where line-side answer supervision and/or network disconnect capabilities are required. +**Version:** 1 +**Extends:** al (0x0009) version 1 + +## 5.1 Properties + +None. + +## 5.2 Events + +None. + +## 5.3 Signals + +### 5.3.1 Line-side Answer Supervision + +**Signal name:** Line-side Answer Supervision +**Signal ID:** las (0x0003) +**Description:** Indicates that the called party has answered. The signal that is sent on the line is provisioned in the MG. Typically this signal involves a reversal of polarity of the current feed on the line. +**Signal type:** On/Off +**Duration:** Not applicable + +##### 5.3.1.1 Additional parameters + +None. + +### 5.3.2 Network Disconnect + +**Signal name:** Network Disconnect +**Signal ID:** nd (0x0004) +**Description:** Indicates that the far-end party has disconnected. The signal that is sent on the line is provisioned in the MG. Typically this signal involves a brief removal of the dc voltage on the line. +**Signal type:** Brief +**Duration:** Provisioned + +#### 5.3.2.1 Additional parameters + +None. + +## 5.4 Statistics + +None. + +## 5.5 Procedures + +The Network Disconnect signal is typically used when a called or calling party remains off-hook after the other party has hung up. In these circumstances, some telephony services provide dial tone to the off-hook phone after a period of several seconds has elapsed. The Network Disconnect signal would normally be applied just prior to the re-application of dial tone on the line. + +# 6 Automatic Metering package + +| | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package Name: | Automatic Metering package | +| Package ID: | amet (0x0044) | +| Description: | This package supports the automated application of repetitive metering pulses to an analogue line termination. It provides a facility whereby the actual number of metering pulses applied to the termination can be periodically reported to the MGC for verification purposes. | +| Version: | 2 | +| Extends: | None | + +## 6.1 Properties + +None. + +## 6.2 Events + +### 6.2.1 Periodic Report + +| | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Periodic Report | +| Event ID: | pr (0x0001) | +| Description: |

This event is used in conjunction with the "Enable Metering" and "Metering Pulse Burst" signals defined in this package. It is detected when the value of the "pulse count since last report" statistic reaches the value specified in the "report period" parameter.

This event does not have any parameters for the observed event descriptor since it will be reported only when "pulse count since last report" is equal to "report period", which is a value already known to the MGC.

This event is not detected when the application of signals is stopped due to a MG failure, a customer line state event (e.g., on-hook), or by an explicit command from the MGC. The MGC needs to read the value of the statistic "pulse count since last report" in those cases, using an AuditValue command.

| + +#### 6.2.1.1 EventsDescriptor parameters + +###### 6.2.1.1.1 Report Period + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Report Period | +| Parameter ID: | rp (0x0001) | +| Description: | This parameter specifies the period of metering reports in terms of pulse counts. There is no default value for this parameter, and it must be specified with a non-zero value. | + +| | | +|-------------------------|-------------------------------| +| Type: | Integer | +| Optional: | No | +| Possible values: | Any positive number of pulses | +| Default: | None | + +#### 6.2.1.2 ObservedEventsDescriptor parameters + +None. + +## 6.3 Signals + +### 6.3.1 Enable Metering + +| | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Signal name: | Enable Metering | +| Signal ID: | em (0x0001) | +| Description: | This signal starts the automatic generation of metering pulses on the termination. The type and duration of the pulses to be applied are provisioned in the MG. | +| Signal type: | On/Off | +| Duration: | Not applicable | + +#### 6.3.1.1 Additional parameters + +###### 6.3.1.1.1 Pulse Count + +| | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Pulse Count | +| Parameter ID: | pc (0x0001) | +| Description: | This parameter specifies the number of metering pulses to be applied to the termination. If the value of this parameter is zero, or if no value is supplied for this parameter, then the repetitive application of metering pulses shall continue until stopped by other mechanisms (for example, the detection of an event, or the replacement of the Signals Descriptor). | +| Type: | Integer | +| Optional: | Yes | +| Possible values: | A non-negative number of pulses | +| Default: | 0 | + +###### 6.3.1.1.2 Pulse Repetition Interval + +| | | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Pulse Repetition Interval | +| Parameter ID: | pri (0x0002) | +| Description: | This parameter specifies the interval over which the pulses specified in the pulse count should be issued, or, if the pulse count is 0 or not present, the interval between pulses, in milliseconds. For a specified non-zero pulse count, it represents the time over which the pulses should occur. It is up to the MG to perform the appropriate calculations to determine the pulse interval. For a zero or unspecified pulse count, it represents the time that should elapse between the leading edge of a pulse and the leading edge of the succeeding pulse. | + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------| +| | There is no default value for this parameter, and the MGC should always provide a positive non-zero value. | +| Type: | Integer | +| Optional: | No | +| Possible values: | 1 or more milliseconds | +| Default: | None | + +#### 6.3.2 Metering Pulse Burst + +| | | +|---------------------|---------------------------------------------------------------------------------| +| Signal name: | Metering Pulse Burst | +| Signal ID: | mpb (0x0002) | +| Description: | This signal causes a burst of metering pulses to be applied to the termination. | +| Signal type: | Brief | +| Duration: | Variable | + +#### 6.3.2.1 Additional parameters + +###### 6.3.2.1.1 Burst Pulse Count + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Burst Pulse Count | +| Parameter ID: | bpc (0x0001) | +| Description: | This parameter specifies the number of metering pulses to be applied as a burst on the line. The type and duration for the metering pulses comprising the burst are provisioned in the MG. The pulse repetition interval is provisioned in the MG but may be overridden through use of the pri parameter. | +| Type: | Integer | +| Optional: | Yes | +| Possible values: | 1 or more pulses | +| Default: | 1 | + +##### 6.3.2.1.2 Pulse Repetition Interval + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Pulse Repetition Interval | +| Parameter ID: | pri (0x0002) | +| Description: | This parameter allows the MGC to override the provisioned interval from the leading edge of a metering pulse to the leading edge of the next metering pulse in this burst. | +| Type: | Integer | +| Optional: | Yes | +| Possible values: | 1 or more milliseconds | +| Default: | Provisioned. | + +#### 6.3.3 Phased Metering + +**Signal name:** Phased Metering +**Signal ID:** phsm (0x0003) +**Description:** This signal allows phased metering pulses to be applied by the MG. +**Signal type:** Brief +**Duration:** Variable, based on number and length of metering phases specified. + +#### 6.3.3.1 Additional parameters + +###### 6.3.3.1.1 Pulse Repetition Interval + +**Parameter name:** Pulse Repetition Interval +**Parameter ID:** pri (0x0001) +**Description:** Interval from the leading edge of a metering pulse to the leading edge of the next metering pulse. +**Type:** Sublist of Integer +**Optional:** No +**Possible values:** Non-negative number of milliseconds +**Default:** None + +##### 6.3.3.1.2 Maximum Pulse Count per Charge Interval (PCCI) + +**Parameter name:** Max PCCI +**Parameter ID:** pcx (0x0002) +**Description:** The maximum number of pulses that will be applied during a given charge interval. +**Type:** Sublist of Integer +**Optional:** No +**Possible values:** Non-negative number of pulses +**Default:** None + +##### 6.3.3.1.3 Repetitions of Max PCCI + +**Parameter name:** Repetitions of Max PCCI +**Parameter ID:** repx (0x0003) +**Description:** The number of charge intervals in which to apply the number of pulses specified by the pcx parameter. +**Type:** Sublist of Integer +**Optional:** No +**Possible values:** Non-negative number of intervals +**Default:** None + +##### 6.3.3.1.4 Minimum pulse count per charge interval (PCCI) + +**Parameter name:** Min PCCI +**Parameter ID:** pcn (0x0004) +**Description:** The minimum number of pulses that will be applied during a given charge interval. +**Type:** Sublist of Integer +**Optional:** No +**Possible values:** Non-negative number of pulses +**Default:** None + +###### 6.3.3.1.5 Repetitions of Min PCCI + +**Parameter name:** Repetitions of Min PCCI +**Parameter ID:** repn (0x0005) +**Description:** The number of charge intervals in which to apply the number of pulses specified by the pcn parameter. +**Type:** Sublist of Integer +**Optional:** No +**Possible values:** Non-negative number of intervals +**Default:** None + +##### 6.3.3.1.6 Charge Interval + +**Parameter name:** Charge Interval +**Parameter ID:** ci (0x0006) +**Description:** The frequency at which charges are incurred, in seconds. +**Type:** Sublist of Integer +**Optional:** No +**Possible values:** Non-negative number of seconds +**Default:** None + +###### 6.3.3.1.7 Phase Duration + +**Parameter name:** Phase Duration +**Parameter ID:** pd (0x0007) +**Description:** The duration of the metering phase, in seconds. +**Type:** Sublist of Integer +**Optional:** No +**Possible values:** Non-negative number of seconds +**Default:** None + +### 6.4 Statistics + +### 6.4.1 Current Pulse Count + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic name: | Current Pulse Count | +| Statistic ID: | cpc (0x0001) | +| Description: | This statistic represents the total number of metering pulses that have been applied on an analogue line termination since the last time its value was reset to zero by means of the "enable metering" signal defined in this package. | +| Type: | Integer | +| Possible values: | A non-negative number of pulses | +| Level: | Termination | + +### 6.4.2 Pulse Count since Last Report + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic name: | Pulse Count since Last Report | +| Statistic ID: | pcslr (0x0002) | +| Description: | This statistic represents the number of metering pulses that have been applied on an analogue line termination since the last meter report event, or since the last time its value was reset to zero by means of the "enable metering" signal defined in this package. The recognition of the periodic report event and generation of a corresponding notification resets the value of this statistic to zero. | +| Type: | Integer | +| Possible values: | Non-negative number of pulses | +| Level: | Termination | + +### 6.5 Procedures + +### 6.5.1 Applying metering pulses + +On receiving a SignalsDescriptor containing the signal em, an MG shall set the values of the statistics cpc and pcslr to zero. The MG shall apply the first metering pulse to the termination immediately, and then apply subsequent metering pulses at intervals as determined by the specified value of the pulse repetition interval parameter pri. If the pulse count is greater than 0, then the MG shall determine the appropriate interval between pulses by dividing the pulse repetition interval value by the pulse count. In the event that the interval determined is not integral, then it is the responsibility of the MG to adjust the individual intervals to avoid long-term rounding errors. If the pulse count is zero, or not present, then the MG shall issue a new pulse at intervals equal to the pulse repetition interval. + +The MG shall increment by one the values of the pulse count statistics cpc and pcslr for each metering pulse that is applied to the termination, regardless of whether the pulse was generated as a result of the em signal or as a result of the mpb signal. + +If the value of the parameter pc associated with the signal em is non-zero, then the repetitive application of metering pulses should be continued until the number of pulses sent, excluding any pulses due to concurrent mpb signals, is equal to the value of the parameter pc. In this case, the MGC should include a SignalType parameter in the Signals Descriptor, specifying the signal type Brief, to override the OnOff signal type for the signal em. + +If the value of the parameter pc is zero, or if this parameter is not supplied by the MGC, then the repetitive application of metering pulses should continue until the signal is halted in any of the normal ways. Any pulses applied due to a concurrent mpb signal shall be applied for the em signal in addition to the required repetitive pulses. + +If following the application of any metering pulse (regardless of whether it was generated as a result of the signal em or as a result of the signal mbp), the EventsDescriptor contains the event pr, and if the value of pcsr is equal to the value of the EventsDescriptor parameter rp, then the pr event shall be notified, and the value of the statistic pcsr shall be reset to zero. The detection of the event pr shall not cause the termination of the signal em or the signal mbp, even if the KeepActive flag is not set for the pr event. + +The repetition rate for the application of metering pulses to the termination may be changed during a call by writing a new SignalsDescriptor containing the signal em, specifying a new value of the pulse repetition interval parameter pri. In this case, the SignalsDescriptor should contain a KeepActive flag for the signal em, and the MG should transition to the new pulse repetition interval after the next metering pulse has been applied. + +A metering pulse burst may be applied while a metered call is in progress, for example, to take account of a chargeable mid-call action by the subscriber. In this case, the MGC should send a new SignalsDescriptor that contains the em signal with a KeepActive flag, together with the mpb signal. The MG should continue to apply metering pulses at the repetition interval specified by the pri parameter of the em signal, while in addition applying the metering pulse burst. The MG should ensure that the pulses comprising the pulse burst are applied in such a manner as not to interfere with the pulses comprising the repetitive background metering, respecting any minimum inter-pulse interval that may be needed to ensure proper recognition of pulses by customer premises equipment. + +When an MG is generating metering pulses as a result of an active em signal, and receives a new SignalsDescriptor containing an em signal with a KeepActive flag, it shall not reset the values of the statistics cpc and pcsr to zero. + +The detection of an event such as on-hook while a metering pulse is being applied to a termination should not cause truncation of the pulse. Once a pulse has started to be applied, the application of the pulse should continue for the full duration provisioned in the MG. + +### 6.5.2 Specification of full tariff description in a single message + +It is important to maximize accuracy of the metering by minimizing messaging and latency in the network. One of the primary ways to achieve this is communication of the entire call tariff model in a single message from the MGC to the MG. + +By signalling the key parameters as sub-lists, each phase of the call is represented through a discrete signal element. In order for the MG to be able to determine how to handle each element, the Phase Duration must be included as a parameter. + +The mpb signal may be used to describe the one-time set-up charge if applicable. Also, if a one time add-on charge is incurred during the call, a new signal must be sent to the MG to handle the charge. (Set-up and add-on charges are described further in clause 6.5.3). In this manner, the entire call tariff model can be expressed by a single message as follows: + +``` +SG{amet/mpb{bpc=Setup Charges,pri=Pulse Interval}, + amet/phsm{pri=[Phase1,Phase2,...,PhaseN], + pcx=[Phase1,Phase2,...,PhaseN], + repx=[Phase1,Phase2,...,PhaseN], + pcn=[Phase1,Phase2,...,PhaseN], + repn=[Phase1,Phase2,...,PhaseN], +``` + +``` + +ci=[Phase1, Phase2, ..., PhaseN] , +pd=[Phase1, Phase2, ..., PhaseN] } } + +``` + +A tariff rate changeover event can cause the MGC to send a new tariff rate descriptor to the MG, replacing the previous descriptor. + +### 6.5.3 Set-up and add-on charges + +#### 6.5.3.1 Using pulse bursts + +The preferred method for handling one time charges (set-up or add-on) is to instruct the MG to apply a pulse burst in conjunction with the existing tariff model. The MG would then pulse at maximum rate until it had recovered the one-time charge and had caught back up with the application of the tariff rate. + +For a set-up charge equivalent to five pulses for example, the resulting tariff descriptor would be: + +``` + +SG{amet/mpb{bpc=5,pri=3}, + amet/phsm{pri=[Phase1, Phase2, ..., PhaseN] , + pcx=[Phase1, Phase2, ..., PhaseN] , + repx=[Phase1, Phase2, ..., PhaseN] , + pcn=[Phase1, Phase2, ..., PhaseN] , + repn=[Phase1, Phase2, ..., PhaseN] , + ci=[Phase1, Phase2, ..., PhaseN] , + pd=[Phase1, Phase2, ..., PhaseN] } } + +``` + +For add-on charges, a new signal list element is added to the Signals Descriptor and the original tariff model is retained via the use of KeepActive. That is, the MG must be instructed to continue to process the original Tariff Rate Signal List but to also process the add-on charge signal. As with the set-up charge description above, the MG must pulse at maximum rate to recover the add-on charge and "catch up" to the application of the original regular tariff rate. + +``` + +SG{amet/mpb{bpc=8,pri=3}, ;Add-on Charge + amet/phsm{pri=[Phase1, Phase2, ..., PhaseN] , ;Original tariff + pcx=[Phase1, Phase2, ..., PhaseN] , + repx=[Phase1, Phase2, ..., PhaseN] , + pcn=[Phase1, Phase2, ..., PhaseN] , + repn=[Phase1, Phase2, ..., PhaseN] , + ci=[Phase1, Phase2, ..., PhaseN] , + pd=[Phase1, Phase2, ..., PhaseN] , + KA} } + +``` + +It may be important for the MG to report to the MGC when it has completed pulsing the add-on charges to help the MGC handle any case where additional add-on charges are incurred following the initial add-on charge. This can be accomplished through use of the Signal Completion event in the generic package (see Annex E.1/H.248.1). + +#### 6.5.3.2 Combining the extra charge with the regular tariff + +An alternative option for handling one-time charges is to combine them with the regular tariff signalling in such a way as to produce a new virtual phase. These virtual phases and regular call phases are generically referred to as pulse windows for purpose of describing this mechanism. + +Handling a set-up charge in this model for example would produce a tariff descriptor as follows: + +``` +SG{amet/phsm{pri=[Phase1a, Phase1b, Phase2, ..., PhaseN] , + pcx=[Phase1a, Phase1b, Phase2, ..., PhaseN] , + repx=[Phase1a, Phase1b, Phase2, ..., PhaseN] , + pcn=[Phase1a, Phase1b, Phase2, ..., PhaseN] , + repn=[Phase1a, Phase1b, Phase2, ..., PhaseN] , + ci=[Phase1a, Phase1b, Phase2, ..., PhaseN] , + pd=[Phase1a, Phase1b, Phase2, ..., PhaseN] } } +``` + +Phase 1a is the set-up charge combined with the affected portion of the first phase and phase 1b is the balance of the first phase once the set-up metering has completed. + +Add-on charges are handled similarly. If a one-time add-on charge is required, the MGC will recalculate the remainder of the call tariff, creating additional pulse windows as needed. + +This alternative option is as accurate as the preferred option for handling set-up charges, but loses accuracy for add-on charges as the MGC is forced to recalculate the tariff descriptor mid-call based upon its view of where the MG has progressed in the current tariff metering. + +#### 6.5.4 Handling fractional pulse counts + +The tariff pulse rate (TPR), which defines the number of pulses per second required to meet the tariff for a particular call phase, along with the charge interval (CI) is used to calculate the number of pulses required to be signalled during a charge interval (PCCI). In some cases, this can produce a fractional pulse count. Solutions that compensate for this in the MGC result in increased messaging, added latency and consequently reduced accuracy. + +Since a fraction of a pulse cannot be signalled by standard metering equipment, the MGC needs to convert each metering phase into discrete components which will describe how many actual pulses to generate across the charge intervals to obtain as much metering accuracy as possible across the phase. + +Each component of the metering phase consists of a pulse count for the charge interval (PCCI) and a number of repetitions (Rep), which we will represent as {PCCI Rep}. It can be shown that two discrete components are all that is required to break the PCCI value into parts which will produce the most accurate metering result for the phase. The pulse counts for each component are calculated by multiplying TPR by CI, and then rounding up and truncating the result, respectively. For example, if $TPR \times CI = 4.3$ , then the Pulse Count for one of the components will be 5, and the other will be 4. The expression to represent the PCCI value is then: + +$$\{PCCI_{max} Rep_{max}\} \{PCCI_{min} Rep_{min}\}$$ + +The algorithm for calculating the values of $Rep_{max}$ and $Rep_{min}$ will be discussed in clause 6.5.4.3. + +#### 6.5.4.1 Mapping discrete representations into a pulse map + +Having determined the number of pulses for $PCCI_{max}$ and $PCCI_{min}$ for one charge interval in a phase, further consideration must be given to the different permutations for how the charge intervals should be ordered to achieve the pulsing required to meet the tariff. + +As shown in clause 6.5.4.2, a PCCI value of 2.3333 for 10 charge intervals in a phase can be represented by the expression {3 3} {2 7}. This means that the MG must send three pulses for three charge intervals during the phase and two pulses for seven charge intervals during the phase. Many permutations exist for this scenario. Examples include: + +{3, 3, 3, 2, 2, 2, 2, 2, 2, 2} + +{3, 2, 3, 2, 3, 2, 2, 2, 2, 2} + +{2, 2, 2, 2, 2, 2, 2, 3, 3, 3} + +{3, 3, 2, 3, 2, 2, 2, 2, 2, 2} + +An almost infinite number of pulse map patterns could be defined. Three examples of pre-defined pulse map patterns are as described in Table 1. + +**Table 1 – Pre-defined pulse map patterns** + +| Pulse map pattern name | Pulse map example | Comment | +|------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Max Loaded | {X, X, X, N, N, N, ...} | Pulse at the PCCImax rate until the Repmax count is met, and then pulse at PCCImin to the end of the phase. For very high fractions this option reduces the likelihood of underpulsing. As the fraction decreases, however, this method may overpulse. | +| Interleaved | {X, N, X, N, X, ...} | For fractions of 0.5, this is the most accurate pulse map possible. | +| Min Loaded | {N, N, N, X, X, X, ...} | Pulse at the PCCImin rate until Repmin count is met, and then pulse at PCCImax to the end of the phase. For very low fractions, this option reduces the likelihood of overpulsing. As the fraction increases, however, this method may underpulse. | + +The most accurate model for the map is to dynamically define it in such a way as to interleave PCCImax and PCCImin using the ratio of Repmax to Repmin as a template. PCCImax should always be chosen as the lead value as it is in the best interest of the service provider to slightly over-pulse as opposed to under-pulse. + +Example 1: {3 7} {2 3} + +Repmax/Repmin = 2.333. Rounding, we get two PCCImax for every one PCCImin, leading to this pulse map pattern: + +{3 3 2 3 3 2 3 3 2 3} + +Example 2: {3 3} {2 7} + +In this case, since Repmin > Repmax, we get two PCCImin for every one PCCImax: + +{3 2 2 3 2 2 3 2 2 3} + +Example 3: {24 2} {23 5} + +Repmin/Repmax = 2.5. Since the MG should err on the side of PCCImax, truncate to two PCCImin for every PCCImax rather than rounding to three PCCImin for each PCCImax: + +{24 23 23 24 23 23 23} + +As discussed in clause 6.5.4.2 below, the actual pulse map may contain a variable number of elements. In some cases, the pulse map will contain fewer elements than the number of charge + +intervals in the phase. In this case, the MG shall repeatedly iterate over the pulse map for the duration of the phase. + +### 6.5.4.2 Determining the number of elements in the pulse map + +The determined value of the number of elements in the map, NumElementsPerPulseMap, is a function of the number of charge intervals in the phase and the phase duration. If the phase duration is finite, the number of charge intervals that make up the phase determines the parameter sublist length. In the case where the phase is of infinite duration however, the number of elements in the pulse map is set to a value which can most accurately compensate for a fractional PCCI value. + +Consider a PCCI value of 8.3333. This results in a pulse map that will produce nine pulses in some charge intervals and eight pulses in other charge intervals. + +A pulse map with ten elements, which is repeated indefinitely, will produce very accurate results throughout the phase. The PCCI expression becomes {9 3} {8 7} with a resultant pulse map pattern of: + +{9 8 8 9 8 8 9 8 8 8} + +A pulse map with 100 elements will produce: + +{9 33} {8 67} or {9 8 8 9 8 8 9 8 8 9 8 8 9 8 8 ...} + +This is only slightly more accurate than the ten element pulse map. + +As the PCCI value decreases, a map with 100 elements becomes significantly more accurate than a map with ten elements. For most reasonable tariffs, however, modelling shows that using ten elements will produce very accurate results. + +Consider a scenario where the MG must send one pulse in twenty minutes. Assume also that CI equals 60. The TPR for one pulse in 20 minutes is 0.00083333. The resulting PCCI is 0.05. + +If the map were to use ten elements, there would result a repeated pattern of: + +{1 1} {0 9} = {1 0 0 0 0 0 0 0 0 0} + +There would be one pulse every time the list was repeated. Since CI equals 60 s, this means one pulse in every $60 \times 10 = 10$ minutes which is a rate of two pulses in 20 minutes or double the TPR of one pulse in 20 minutes. + +If on the other hand the map used 100 elements, the resultant pattern would be: + +{1 5} {0 95} = {1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 ...} + +This produces the expected result of one pulse in 20 minutes. + +#### 6.5.4.2.1 The reciprocal model for handling low TPR + +A very low PCCI/TPR is only really possible for very long phases or charge intervals – most likely the final phase of a call. An alternative method for dealing with this scenario is to define a pseudo charge interval which is merely the reciprocal of the TPR. That is, if there is a very small pulse/second value, the reciprocal will tell us how often we should generate one pulse. For the case described above where TPR equals 0.00083333 pulses/second, 1/TPR equals 6000 seconds/pulse, the reciprocal model will produce: + +{1 1} {0 0} CI = 6000, PD = infinite + +This would produce one pulse every 20 minutes. + +Unfortunately, it is difficult to select the value of PCCI at which point to switch from the pulse map method to the reciprocal method. The MGC should use the pulse map method with the number of elements set to 100 for infinite phase durations. + +14 Rec. ITU-T H.248.26 (03/2013) + +#### 6.5.4.3 Calculating Repmax and Repmin + +The number of elements in the pulse map, NumElementsPerPulseMap is determined as described above. + +$$\text{NumElementsPerPulseMap} = f(\text{NumChgIntPerPhase}, \text{PhaseDuration})$$ + +Repmax is then calculated using the fractional part of PCCI and the NumElementsPerPulseMap as follows: + +$$\text{Repmax} = \text{ROUND}(\text{NumElementsPerPulseMap} \times \text{FractionalPart}(\text{PCCI}))$$ + +and: + +$$\text{Repmin} = \text{NumElementsPerPulseMap} - \text{Repmax}$$ + +For example, if PCCI equals 2.33333, and there are 10 elements in the pulse map, then PCCImax equals 3, PCCImin equals 2 and: + +$$\text{Repmax} = \text{ROUND}(10 \times 0.33333) = \text{ROUND}(3.33) = 3$$ + +Thus, the discrete expression representing PCCI equals 2.333 and NumElementsPerPulseMap equals 10 is: + +$$\{3\ 3\} \{2\ 7\}$$ + +Using the Interleaved method for expressing the pulse map means that the MG should pulse the following: + +$$\{3\ 2\ 2\ 3\ 2\ 2\ 3\ 2\ 2\ 2\}$$ + +As an additional example, consider the case where PCCI equals 2.3333 and there are seven charge intervals in the phase. This means that NumElementsPerPulseMap equals seven. The resultant discrete expression is: + +$$\{3\ 2\} \{2\ 5\}$$ + +and the pulse map is: + +$$\{3\ 2\ 2\ 3\ 2\ 2\ 2\}$$ + +As another example, PCCI = 4.3 and the Phase Duration is infinite. In this case, the NumElementsPerPulseMap equals 10. This is expressed as {5 3} {4 7} which results in a pulse map of: + +$$\{5\ 4\ 4\ 5\ 4\ 4\ 5\ 4\ 4\ 4\}$$ + +If the subscriber disconnects after 17 charge intervals have passed, the MG will have begun repeating the pattern and will have pulsed a map of: + +$$\{5\ 4\ 4\ 5\ 4\ 4\ 5\ 4\ 4\ 4\ 5\ 4\ 4\ 5\ 4\ 4\ 5\}$$ + +#### 6.5.4.4 Handling odd charge interval values + +The previous clause assumed that a phase is evenly divided into a number of charge intervals. That is, the phase duration is evenly divisible by the number of charge intervals. It is possible that a provider may define tariff models where the phase duration is not evenly divided into charge intervals as illustrated in Figure 1. + +![Figure 1: A timeline diagram illustrating a phase duration (PD) that is not evenly divided into charge intervals (CI). The diagram shows a horizontal line representing time. A bracket labeled 'Charge Interval (CI)' spans a portion of the line. A larger bracket labeled 'Phase Duration (PD)' spans a longer portion of the line, starting at the same point as the CI bracket but ending at a different point, indicating that the PD is not a multiple of the CI.](c6caafc29a33844653a0e827c8666204_img.jpg) + +The diagram shows a horizontal timeline. A bracket labeled 'Charge Interval (CI)' spans a segment of the timeline. A larger bracket labeled 'Phase Duration (PD)' starts at the same point as the CI bracket but ends at a different point, indicating that the PD is not a multiple of the CI. + +Figure 1: A timeline diagram illustrating a phase duration (PD) that is not evenly divided into charge intervals (CI). The diagram shows a horizontal line representing time. A bracket labeled 'Charge Interval (CI)' spans a portion of the line. A larger bracket labeled 'Phase Duration (PD)' spans a longer portion of the line, starting at the same point as the CI bracket but ending at a different point, indicating that the PD is not a multiple of the CI. + +Figure 1 – Phase duration not evenly divided in charge intervals + +There are two possible methods for handling this case, each producing very different results. The preferable method is dependent upon the best interpretation of the service provider's intentions. + +##### 6.5.4.4.1 Phase pulse count priority metering + +The MGC should use this method if it is most important to accurately pulse the total number of pulses expected to be produced over the entire phase as calculated by $TPR \times PD$ , regardless of the number of charge intervals which may be encountered. + +First, the phase will be broken into two pulse windows as illustrated in Figure 2. The first pulse window will consist of the set of whole charge intervals which can fit within the phase duration. The second pulse window will deal with the remainder. + +![Figure 2: Dividing the phase into pulse windows. The diagram shows a horizontal timeline representing a phase. A red bracket at the bottom is labeled 'Phase Duration (PD)'. Above the timeline, a black bracket labeled 'Pulse Window 1' covers the first part, and another black bracket labeled 'Pulse Window 2' covers the remaining part. A smaller black bracket labeled 'Charge Interval (CI)' is shown within Pulse Window 1, indicating its duration.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +Figure 2: Dividing the phase into pulse windows. The diagram shows a horizontal timeline representing a phase. A red bracket at the bottom is labeled 'Phase Duration (PD)'. Above the timeline, a black bracket labeled 'Pulse Window 1' covers the first part, and another black bracket labeled 'Pulse Window 2' covers the remaining part. A smaller black bracket labeled 'Charge Interval (CI)' is shown within Pulse Window 1, indicating its duration. + +**Figure 2 – Dividing the phase into pulse windows** + +Using the formulae defined in clause 6.5.4.3, a pulse map for the first pulse window is easily created by merely truncating the value of NumElementsPerPulseMap. That is, NumElementsPerPulseMap equals $TRUNC(MIN(10, NumChgIntPerPhase))$ . + +The pulses to be sent during the second pulse window are determined by rounding up the difference between the number of pulses required to be sent over the entire phase and the number sent in the first pulse window. + +Consider for example, a tariff model with a Phase Duration equal to 180, a Charge Interval equal to 25 and a Tariff Pulse Rate equal to 0.093333. In this case we have: + +$$\begin{aligned} PCCI &= TPR \times CI \\ &= 0.093333 \times 25 \\ &= 2.333333 \end{aligned}$$ + +$$PCCI_{max} = 3, PCCI_{min} = 2$$ + +$$\begin{aligned} NumChgIntPerPhase &= PhaseDuration/ChargeInterval \\ &= 180/25 \\ &= 7.2 \end{aligned}$$ + +$$\begin{aligned} NumElementsPerPulseMap &= TRUNC(MIN(10, NumChgIntPerPhase)) \\ &= 7 \end{aligned}$$ + +$$\begin{aligned} Repmax &= ROUND(NumElementsPerPulseMap \times FractionalPart(PCCI)) \\ &= ROUND(7 \times FractionalPart(.3)) \\ &= ROUND(2.1) \\ &= 2 \end{aligned}$$ + +$$\begin{aligned} Repmin &= NumElementsPerPulseMap - Repmax \\ &= 5 \end{aligned}$$ + +$$Pulse\ Map\ for\ Pulse\ Window\ 1 = \{3\ 2\} \{2\ 5\}$$ + +$$\begin{aligned} + \text{Total Pulses in Pulse Window 1} &= (\text{PCCImax} \times \text{Repmax}) + (\text{PCCImin} \times \text{Repmin}) \\ + &= (3 \times 2) + (2 \times 5) \\ + &= 16 \\ + \text{Total Pulses Required in Phase} &= \text{NumChgIntPerPhase} \times \text{PCCI} \\ + &= 7.2 \times 2.333333 \\ + &= 16.8 \\ + \text{Total Pulses for Pulse Window 2} &= \text{ROUND}(16.8 - 16) \\ + &= 1 + \end{aligned}$$ + +**Pulse Map for Pulse Window 2** = {1 1} {0 0} + +**Total Pulses Sent for Entire Phase** = 17 + +In this example, the phase was over-pulsed by 0.2 pulses. This is as accurate as the metering application can possibly be made. This example is illustrated in Figure 3: + +![Figure 3: Phase pulse count priority metering diagram. A horizontal timeline shows a 'Phase Duration (PD)' from a red vertical line to another red vertical line. Above the timeline, 'Pulse Window 1' is indicated by a bracket over the first seven groups of pulses, and 'Pulse Window 2' is indicated by a bracket over the eighth group. Below the timeline, a 'Charge Interval (CI)' is indicated by a bracket under the first group of pulses. The groups of pulses consist of 3, 2, 3, 3, 2, 2, 2, and 1 pulses respectively. A small label 'H.248.26_F3' is in the bottom right corner.](50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg) + +Figure 3: Phase pulse count priority metering diagram. A horizontal timeline shows a 'Phase Duration (PD)' from a red vertical line to another red vertical line. Above the timeline, 'Pulse Window 1' is indicated by a bracket over the first seven groups of pulses, and 'Pulse Window 2' is indicated by a bracket over the eighth group. Below the timeline, a 'Charge Interval (CI)' is indicated by a bracket under the first group of pulses. The groups of pulses consist of 3, 2, 3, 3, 2, 2, 2, and 1 pulses respectively. A small label 'H.248.26\_F3' is in the bottom right corner. + +**Figure 3 – Phase pulse count priority metering** + +##### 6.5.4.4.2 Charge interval priority metering + +The MGC should use this method if the objective is to always apply charges at the beginning of a charge interval regardless as to how much of the actual interval can fit within the remainder of the phase. + +In this case, the pulse map is allowed to repeat such that as many pulses as possible are sent for the start of the new charge interval. Using the example of the previous clause, sixteen pulses are still pulsed for the first seven charge intervals: + +**Pulse Map** = {3 2} {2 5} + +$$\begin{aligned} + \text{Total Pulses in first 7 charge intervals} &= (\text{PCCImax} \times \text{Repmax}) + (\text{PCCImin} \times \text{Repmin}) \\ + &= (3 \times 2) + (2 \times 5) \\ + &= 16 + \end{aligned}$$ + +An eighth charge interval will begin and the MG shall move back to the beginning of the pulse map and send an additional 3 pulses. The phase will then complete in 5 seconds and a total of 19 pulses will have been sent across the phase despite the fact that $\text{TPR} \times \text{PD} = 16.8$ pulses were calculated for this phase. This example is illustrated in Figure 4. + +![Figure 4: Charge interval loaded metering diagram. A horizontal timeline shows a 'Phase Duration (PD)' from a red vertical line to another red vertical line. Below the timeline, a 'Charge Interval (CI)' is indicated by a bracket under the first group of pulses. The groups of pulses consist of 3, 2, 3, 3, 2, 2, 2, and 3 pulses respectively. A small label 'H.248.26_F4' is in the bottom right corner.](7978d5099076a93ea7969446444502f8_img.jpg) + +Figure 4: Charge interval loaded metering diagram. A horizontal timeline shows a 'Phase Duration (PD)' from a red vertical line to another red vertical line. Below the timeline, a 'Charge Interval (CI)' is indicated by a bracket under the first group of pulses. The groups of pulses consist of 3, 2, 3, 3, 2, 2, 2, and 3 pulses respectively. A small label 'H.248.26\_F4' is in the bottom right corner. + +**Figure 4 – Charge interval loaded metering** + +# 7 Metering Pulse Detection package + +| | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | Metering Pulse Detection package | +| Package ID: | metd (0x0096) | +| Description: | This package supports detection of metering pulses on analogue or digital line terminations. It provides a facility whereby the actual number of metering pulses detected on the termination can be periodically reported to the MGC. | +| Version: | 1 | +| Extends: | None | + +## 7.1 Properties + +### 7.1.1 Last Repetition Interval + +| | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Last Repetition Interval | +| Property ID: | lri (0x0001) | +| Description: | Contains the time interval between the last two pulses detected. | +| Type: | Integer | +| Possible values: | A positive integer number specifies the interval in milliseconds between the last two detected metering pulses. -1 specifies that no pulses have been detected. 0 specifies that the interval-recording mechanism is armed. That is, a pulse was detected and the timestamp of the last pulse was recorded, but a subsequent pulse has not been detected. | +| Default: | -1 | +| Defined in: | TerminationState Descriptor | +| Characteristics: | ReadOnly | + +## 7.2 Events + +### 7.2.1 Periodic Report + +| | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Periodic Report | +| Event ID: | pr (0x0001) | +| Description: |

This event is detected when the value of the "Pulse Count since Last Report" statistic reaches the value specified in the "Report Period" parameter. This event is not detected while the incoming metering pulses are stopped. The MGC may audit the Statistics Descriptor in order to read the value of the statistic "Pulse Count since Last Report".

Requesting this event enables metering pulse detection.

| + +#### 7.2.1.1 EventsDescriptor parameters + +###### 7.2.1.1.1 Report Period + +| | | +|------------------------|---------------| +| Parameter name: | Report Period | +| Parameter ID: | rp (0x0001) | + +**Description:** This parameter specifies the period of metering reports in terms of pulse counts. + +**Type:** Integer + +**Optional:** Yes + +**Possible values:** 1 or more pulses + +**Default:** 1 + +#### 7.2.1.2 ObservedEventsDescriptor parameters + +None. + +### 7.2.2 Repetition Interval Changed + +**Event name:** Repetition Interval Changed + +**EventID:** ric (0x0002) + +**Description:** This event is generated when MG changes the "Last Repetition Interval" property value. Requesting this event enables metering pulse detection. + +#### 7.2.2.1 EventsDescriptor parameters + +###### 7.2.2.1.1 Repetition Interval Threshold + +**Parameter name:** Repetition Interval Threshold + +**Parameter ID:** rit (0x0001) + +**Description:** This parameter sets the time deviation threshold from the current value of the "Last Repetition Interval" property in order to trigger the event. That is, if the time between two consecutive metering pulses changes more than the value specified in this parameter, the event will be detected. + +**Type:** Integer + +**Optional:** Yes + +**Possible values:** Any non-negative integer in milliseconds + +**Default:** Provisioned + +#### 7.2.2.2 ObservedEventsDescriptor parameters + +###### 7.2.2.2.1 New Repetition Interval + +**Parameter name:** New Repetition Interval + +**Parameter ID:** nri (0x0002) + +**Description:** This parameter reports the new value of the "Last Repetition Interval" property. + +**Type:** Integer + +**Optional:** No + +**Possible values:** A positive integer number specifies interval in milliseconds between last two detected metering pulses. 0 specifies that interval-recording mechanism is armed, that is first metering pulse is detected, or metering pulse was not detected within previous "Last Repetition Interval" value. -1 specifies that no pulses have been detected. + +**Default:** None + +##### 7.2.2.2.2 Pulse Count since Last Repetition Interval Changed + +**Parameter name:** Pulse Count since Last Repetition Interval Changed + +**Parameter ID:** pcsrlc (0x0003) + +**Type:** Integer + +**Optional:** Yes + +**Possible values:** Any non-negative integer + +**Description:** This parameter reports the number of metering pulses that have been detected on a termination since the last "Repetition Interval Changed" event. 0 specifies that no metering pulse was detected within previous "Last Repetition Interval"" value. + +**Default:** 0 + +## 7.3 Signals + +None. + +## 7.4 Statistics + +### 7.4.1 Current Pulse Count + +**Statistic name:** Current Pulse Count + +**Statistic ID:** cpc (0x0001) + +**Description:** This statistic represents the total number of metering pulses that have been detected on a termination since the last time its value was reset to zero by means of "enabling "metering pulse detection" defined in this package. + +**Type:** Integer + +**Possible values:** Non-negative number of pulses + +**Level:** Termination + +### 7.4.2 Pulse Count since Last Report + +**Statistic name:** Pulse Count since Last Report + +**Statistic ID:** pcsrlr (0x0002) + +**Description:** This statistic represents the number of metering pulses that have been detected on a termination since the last "Periodic Report", or "Repetition Interval Changed" events, or since the last time its value was reset to zero by means of enabling metering pulse detection as stated in this package. The recognition of the "Periodic Report", or "Repetition Interval Changed" events and generation of a corresponding notification resets the value of this statistic to zero. + +**Type:** Integer +**Possible values:** Non-negative number of pulses +**Level:** Termination + +## 7.5 Error code + +### 7.5.1 Invalid Combination of Metering Detection Events + +**Error code #:** 459 +**Name:** Invalid Combination of Metering Detection Events +**Definition:** The command was disregarded because the Events Descriptor contained more than one metering detection event. +**Error Text in the error Descriptor:** – +**Comment:** – + +## 7.6 Procedures + +### 7.6.1 General procedures + +The setting of an Events Descriptor containing either event in this package on a termination enables "metering pulse detection". An Events Descriptor without one of the events defined in this package disables "metering pulse detection". + +Because a new Events Descriptor completely replaces a previously set descriptor, in order not to disrupt currently enabled "metering pulse detection" on a termination, the MG must act according to the following procedure: + +If metering pulse detection is enabled on a termination and the MG receives a new Events Descriptor with exactly the same request (e.g., both events and parameters) to enable metering pulse detection, it must not disrupt the current metering pulse detection. If the MGC needs to restart metering pulse detection with the same event and parameters as are currently active on a termination, it first has to disable metering pulse detection by sending an Events Descriptor which either does not contain any events from this package, or contains an event or event parameters which differ from currently active metering pulse detection event and parameters. + +### 7.6.2 KeepActive and EventBufferControl procedures + +Care should be taken to specify the KeepActive flag when necessary to ensure that notification of metering pulse detection event does not interrupt currently active signals. EventBufferControl should be set to off, as metering pulse detection events are periodic in nature (that is once set, they potentially result in multiple notifications). + +### 7.6.3 Timestamp procedures + +Because the time detected and/or the time interval between pulses are potential attributes of incoming metering pulses, inclusion of a timestamp in the ObservedEvents Descriptor is mandatory for metering pulse detection events. + +### 7.6.4 Properties procedures + +When placing terminations in-service, or when enabling metering pulse detection on a termination using the "Repetition Interval Changed" (ric) event or when disabling currently active "metering pulse detection" which was enabled using ric event, the MG shall reset value of the "Last Repetition Interval" (lri) property to -1. This indicates that no pulses were detected, or metering pulse + +detection is not enabled. Furthermore, the MG only updates the value of the lri property to values other than $-1$ if metering pulse detection is enabled using the ric event. + +### 7.6.5 Statistics procedures + +When enabling metering pulse detection on a termination, the MG shall reset the values of the statistics "Current Pulse Count" (cpc) and "Pulse Count since Last Report" (pcslr) to zero. + +Once metering pulse detection is enabled on a termination, the MG shall increment by one the values of the cpc and pcslr statistics for each metering pulse that is detected on the termination, regardless of the metering pulse detection method used. + +On each metering pulse detection notification event the MG sends, it shall reset the value of the pcslr statistic to zero. + +#### 7.6.6 Metering pulse detection methods and procedures + +The "Periodic Report" (pr) event is used in networks where metering pulses are expected to come irregularly, or only a number of metering pulses is required to be detected. In most network configurations, a MGC controlling a MG which receives metering pulses is the "end receiver" of metering pulses. In these networks, the MGC only needs to know the number of metering pulses received by the MG and thus the MGC might choose to use the pr event for metering pulse detection. + +The "Repetition Interval Changed" (ric) event is used in networks where metering pulses are expected to come on a regular basis with roughly the same periodic interval between metering pulses. Typically in this case, the controlling MGC is not the "end receiver" of the metering pulses but rather a metering pulse "proxy". An example of one such configuration would be a R2 to R2 gateway where the incoming R2 exchange MGC has to proxy the metering pulses to the outgoing R2 exchange MGC. Usage of the ric event provides an optimized metering pulse detection method for such configurations. This method minimizes signalling traffic between the MG and MGC associated with metering pulse detection. + +It is up to the MGC to choose either metering method. The MGC shall not activate both the tpr and ric events at the same time on a single termination. If the MG receives an Events Descriptor which contains both the pr and ric events, it shall fail the command with error code 459. + +#### 7.6.6.1 Usage of "Repetition Interval Changed" (ric) event + +Upon receipt of an Events Descriptor which contains the ric event, the MG shall enable metering pulse detection. + +###### 7.6.6.1.1 Incoming metering pulses start + +When the first metering pulse is detected, the MG shall set the value of the "Last Repetition Interval" (lri) property to 0. At the same time, the ric event shall be notified with nri set to 0 and pcslric set to 1 to indicate that the first metering pulse is detected and the interval-recording mechanism is armed (e.g., the time stamp of first pulse is recorded). + +Upon detection of the second metering pulse, the MG shall calculate the repetition interval value, update the lri property with that value and send the ric event notification with nri set to the new value of the lri property, and pcslric set to 1. + +The MG shall monitor the termination for metering pulse repetition interval changes. If a change occurs and it does not fall within the current value of the "Repetition Interval Threshold" (rit), the lri property shall be updated with the new value and the ric event shall be notified with the appropriate parameters as indicated in clauses 7.6.6.1.2 and 7.6.6.1.3. + +##### **7.6.6.1.2 Incoming metering pulse repetition interval decreased** + +If the next metering pulse is detected before the minimum expected timeout period has expired (e.g., $lri - rit$ ), the MG shall update the $lri$ property value to the new value and send the $ric$ event notification, with $nri$ set to the new $lri$ value and $pcslric$ set to the current value of the $pcslr$ statistic, to indicate that the repetition interval just decreased. + +##### **7.6.6.1.3 Incoming metering pulses stop, or repetition interval increased** + +If the next metering pulse is not detected within the maximum expected timeout (e.g., $lri + rit$ ), the MG shall set the $lri$ property value to 0 and send the $ric$ event notification with $nri$ set to 0 and $pcslric$ set to the current value of the $pcslr$ statistic, to indicate that the interval-recording mechanism is re-armed due to the stoppage of incoming metering pulses or the increase of the repetition interval. The MG shall retain the timestamp of the last detected incoming metering pulse and then follow the procedures as described in clause 7.6.6.1.1. + +# Bibliography + +[b-Telcordia GR-506-CORE] Telcordia GR-506-CORE (2011), *Signaling for Analog Interfaces*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|----------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b0d567d14aa49119a893937aae6e931e10a36b3 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36fb6fc1c6e11ffb751340e33f618d2c73239268a191e75ab0101f48efa12e14 +size 201274 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f3687d002e0d3bfa47e7749617f7e3adfe34443 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cddde4a615103dc8cf0d3f89f5e051584c4366ec4d6141994a369cb6f34b1ff +size 57795 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..008d67e2b500ea66ef8a96901aed227e2d14b938 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96719a4fe920ddc5639b00a254d5ae1deca9d80141ae46284969c44ee310808c +size 143506 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef62cc076a0c27be1441f228b89bb7932aa87253 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39bba51f151053edfe15a75610dbd669506ee216d8536b667e36625aab0ed030 +size 86703 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1681cc7fd504e34c7cad54b8f0d673f0d49aa82d --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d190dfe274c2b1c2e85c020aaf459bc94bb1eb13eb91759b95fcb719ba68c597 +size 174274 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62c5c92f13a14d40650d6cfd7b59ef94b9dfffab --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ca5ea79303bcee8b2f9bdf76f6bb04acbef361114d3b8a3e19a10716aa9f0a5 +size 85211 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34b1cdfa7307856e68abc491792f809cee7cc9b1 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e16f69d6f47b152d92a2e9e1fa5dc1d216019efeeeb6a9c79ab2ffd28be8a21 +size 51452 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dacf070a435d8854005e8c2f2e932e039aede367 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35b8874ef15daaadfd2fc2ac5bf0011961bcac76965162d3674024dce876fe7d +size 161499 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/8a9f4764511ce90622893ec65c065eeb_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/8a9f4764511ce90622893ec65c065eeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68f3d994c7514747a597a863bdec88a3ae132697 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/8a9f4764511ce90622893ec65c065eeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b680a2bf3cf7dd19ad32ba824c4fb283dcb2de8f1c272280ac42ccbbb74a17c8 +size 120728 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c707b24973b36a7f886b8508a938d84598bcafa --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:330930b930f7b7a26dd33ee02731e6b2cfc1ce6eb4673607a6621d74ec10d0ad +size 161322 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8271c14798577c2d2672ad82aab6f081fd2c58f1 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4db440a7f4fc4a4dc512933a95b810d2fdaa6d7b4abe33f77a55a42c358914b +size 95857 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f285405b7303af96871d6f30d4b6ccc8a400bde --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:158b54d459f3c84632b43e57deade1f549225e51dbe8e7e91f3443111eacb1b9 +size 167210 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d751777a36a492372a9e2477013a0a1504bfe978 --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afa78e87a1d9c6bd516249c4b2e79e2726e612a52eb6df099bbeb5b6baa89391 +size 192773 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/marked/H/T-REC-H.248.29-201303-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..698a59de8c6d1fdbf90a4e5d78c7a1cf9446279d --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5263b951547c0d7ad284cb235d8a047f1b2eb9ec1902aa0fa1d4b7ea0d98a51 +size 36986 diff --git a/marked/H/T-REC-H.248.29-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.29-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f8d7744ba77e7a178d5327969ff65976356cb35a --- /dev/null +++ b/marked/H/T-REC-H.248.29-201303-I_PDF-E/raw.md @@ -0,0 +1,2463 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.29** + +(03/2013) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: International CAS +compelled register signalling packages** + +Recommendation ITU-T H.248.29 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Gateway control protocol: International CAS compelled register signalling packages + +## Summary + +The packages in Recommendation ITU-T H.248.29 provide ITU-T H.248 support for channel associated signalling (CAS) compelled register signalling. This can be used for R2, although the packages are generic so that they can also be used for other non-R2 compelled schemes. This Recommendation proposes methods to support: + +- standard *en bloc* compelling; +- overlap compelling; +- the ability to enable end-to-end compelled signalling. + +This Recommendation provides only the capabilities of compelled register signalling and it is expected that a system would need to implement the bcas, icas and casblk packages for the line signalling components of any CAS protocol. + +Three packages are defined in Annex A: + +- icasc which provides standard *en bloc* compelling; +- icasco which extends icasc and provides overlap compelling in addition to *en bloc*; +- icasce which extends icasco and provides the ability to enable end-to-end signalling in addition to *en bloc* and overlap. + +Annex B defines an alternative package for support of these functions, called icascgen. This package defines a generic register signalling, which may be used for national variants of Signalling System R2. This kind of interregister signalling is a compelled multifrequency code system. The package is suitable for ITU-T Signalling System R2, although it is defined in a generic way. Thus it can also be used exclusively, or in addition to the packages defined in Annex A. The proposed package comprises following compelled address transfer modes: + +- generic standard *en bloc* compelling; and +- overlap procedures. + +NOTE – The ability to enable end-to-end compelled signalling utilizing Annex B is for further study. + +Annex B introduces the concepts of Detection Events Map and Generation Signals Map, which are very similar to ITU-T H.248 Digit Map usage. + +This revision incorporates a new parameter to indicate whether the Generic Digit information Event is generated in the event of an unsuccessful events map match. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|------------------------------|------------|-------------| +| 1.0 | ITU-T H.248.29 | 2005-01-08 | 16 | +| 1.1 | ITU-T H.248.29 (2005) Cor. 1 | 2007-08-29 | 16 | +| 2.0 | ITU-T H.248.29 | 2013-03-16 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 ITU-T H.248 package approaches for compelled CAS..... | 3 | +| 5.1 System operation modes..... | 3 | +| 5.2 Reasons and criteria..... | 3 | +| 5.3 Motivation for two package approaches..... | 3 | +| Annex A – International CAS compelled register signalling packages..... | 5 | +| A.1 International CAS Compelled Package..... | 5 | +| A.2 International CAS Compelled with Overlap Package..... | 20 | +| A.3 International CAS Compelled with End-to-End Package ..... | 26 | +| Annex B – Generic CAS compelled register signalling package ..... | 31 | +| B.1 Generic CAS Compelled Register Signalling Package..... | 31 | +| B.2 ABNF encoding..... | 49 | +| Appendix I – Timing aspects ..... | 50 | +| Appendix II – Survey of ITU-T H.248 packages for CAS ..... | 52 | +| Bibliography..... | 54 | + + + +## Gateway control protocol: International CAS compelled register signalling packages + +# 1 Scope + +These packages are intended for use in analogue (one-way operation) or digital transmission systems (one-way or both-ways operations). The MGC should be unaware of the transmission details at the physical layer. The MG is therefore assumed to be provisioned with the actual signalling frequencies for interregister signalling (for example 2-out-of-n inband multifrequency code with forward and backward compelled signalling for R2) along with their properties such as amplitude, tone duration, cadence, etc. and also their logical significance. Any timers that dictate the interregister compelling actions are also assumed to be provisioned in the MG. + +NOTE – Annex B specifies additional termination properties allowing the definition of some SSR2 timers. + +Support for any of these packages is optional. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*. +- [ITU-T H.248.16] Recommendation ITU-T H.248.16 (2013), *Gateway control protocol: Enhanced digit collection packages and procedures*. +- [ITU-T H.248.25] Recommendation ITU-T H.248.25 (2013), *Gateway control protocol: Basic CAS packages*. +- [ITU-T H.248.28] Recommendation ITU-T H.248.28 (2007), *Gateway control protocol: International CAS packages*. +- [ITU-T Q.400] Recommendation ITU-T Q.400-Q.490 (1988), *Specifications of Signalling System R2*. +- [ITU-T Q-Sup.7] ITU-T Q-series Recommendations – Supplement 7 (1988), *Semi-compelled and non-compelled multifrequency interregister signalling for national satellite applications based on System R2 interregister signalling*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 backward signal:** A signal, used for the establishment, release or other control of a connection, sent in the opposite direction to call set-up. + +**3.2 compelled signalling:** A signalling method in which the signal to be transmitted is applied continuously until acknowledged or until a timeout occurs. Upon recognition of the initial signal, the acknowledgement signal is applied continuously until the cessation of the initial signal or until a timeout occurs. The cessation of the acknowledgement signal may provoke the beginning of the + +next subsequent compelled cycle. In addition to the acknowledgement, the acknowledgement signal may carry other signalling information (e.g., concerning the next cycle). + +**3.3 *en bloc* signalling:** A signalling method in which the address digits are assembled into one block for onward transmission, the block containing all of the address information necessary to route the call to its destination. + +**3.4 end-to-end signalling:** A signalling method in which signals are transmitted from one end of a multi-link connection to the other end where processing of these signals is required. + +**3.5 forward signal:** A signal, used for the establishment, release or other control of a connection sent in the same direction as call set-up. + +**3.6 interregister signalling:** Signalling System R2: Interregister signals are of the multifrequency type using a 2-out-of-6 in-band code in both directions. The multifrequency combinations are sent and received by multifrequency signalling equipment which is assumed to be associated with the registers used to control the switching equipment at both ends of the inter-exchange link. + +**3.7 KP (start-of-pulsing) signal** (sent in the forward direction): This register signal is sent subsequent to the recognition of a start-dialling signal and is used to prepare the incoming multifrequency register for the receipt of subsequent interregister signals. + +**3.8 line signalling:** A signalling method in which signals are transmitted between equipment which terminate and continuously monitor part or all of the traffic circuit. + +**3.9 overlap address signalling:** A signalling method in which the onward transmission of address signals from a switching centre may commence before the reception of all the address signals over the preceding link has been completed. + +**3.10 register:** The apparatus, in an automatic system, which receives the dialled impulses and controls the subsequent switching operations. + +**3.11 register function:** The functions of receiving, storing, analysing and possibly translating and transmitting address information and other information for the purpose of controlling the setting-up of a call. + +**3.12 register signalling:** Signalling System R1: Link-by-link multifrequency (MF) in-band pulse signalling is used for the transmission of address information. The signalling frequencies are 700 Hz to 1700 Hz, in 200 Hz steps, and combinations of two, and two only, determine the signal. The address information is preceded by a KP signal (start-of-pulsing) and terminated by an ST signal (end-of-pulsing). Either *en bloc*, *en bloc* overlap or overlap sending may apply. This register signalling arrangement is used extensively with other in-band and out-of-band line signalling systems. + +**3.13 ST (end-of-pulsing) signal** (sent in the forward direction): This register signal is sent to indicate that there are no more address signals to follow. The signal is always sent in semi-automatic as well as automatic working. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-------------------------------| +| CAS | Channel Associated Signalling | +| IC | Incoming | +| MC | Multifrequency Combination | +| MF | Multifrequency | +| MG | Media Gateway | + +| | | +|------|--------------------------| +| MGC | Media Gateway Controller | +| NGN | Next Generation Network | +| OG | Outgoing | +| SSR2 | Signalling System R2 | + +# 5 ITU-T H.248 package approaches for compelled CAS + +This Recommendation takes into account that there are various NGN evolution scenarios for legacy compelled CAS equipment. Thus, it supports different modes of operation. + +## 5.1 System operation modes + +This Recommendation defines two operation modes of the ITU-T H.248 interface for support of international compelled CAS register signalling systems (see Appendix II for a complete CAS system overview). The first design is more "MG centric" and covered in Annex A. The second approach in Annex B may be correspondingly called "MGC centric". + +The background is a slightly different functional partitioning concept with respect to control and CAS signalling handling. "MGC centric" means that the full handling is more or less located in the ITU-T H.248 media gateway controller. In the "MG centric" approach, the ITU-T H.248 media gateway provides local handling, for instance in order to offload the MGC. + +Annexes A and B are basically functionally equivalent. Of course, both halves of an associated MGC-MG pair must be operated in the same mode. It is further anticipated that an MGC is either operated in Annex A or Annex B mode, but not supporting both operation modes in parallel. This is due to the underlying functional partitioning approach. + +The ITU-T H.248.29 operation mode on the media gateway side is determined by the corresponding MGC node. + +## 5.2 Reasons and criteria + +There are a number of different possible approaches for partitioning the functional responsibility between the media gateway controller and the media gateway. Partitioning criteria are dependent upon the system or network architecture and may consider the following: the number of interactions between the MGC and MG, timing considerations, the abstraction level of the ITU-T H.248 interface, signalling complexity, coverage of compelled CAS address transfer modes, coverage of existing CAS systems, reusability of control logic, recognition of existing CAS equipment, recognition of /market/region/country specific CAS variants or recognition of customized design extensions (CDE) in general. + +It shall be noted that this list is unweighted and not exhaustive. Deciding upon an ITU-T H.248.29 operation mode according to Annex A or Annex B may be the natural result of an evaluation of a specific subset of these types of criteria. + +## 5.3 Motivation for two package approaches + +Channel associated signalling (CAS) has been successfully deployed in private and public telecommunication networks for more than a half-century, since the introduction of electromechanical and stored-program controlled circuit switching techniques. This historical situation and background is the prime reason why it is not easy to define a straightforward interconnection model between ITU-T H.248 media gateways for next generation networks (NGN) and the broad spectrum of CAS standards and variants in use. + +The two operation modes of ITU-T H.248.29 originate in different partitioning principles of the control architecture in legacy synchronous transfer mode (STM) switches. The decomposition principles may be diverse, particularly for compelled CAS capable switching systems. ITU-T H.248.29 recognizes the fact of this installed legacy switching base and offers seamless evolution paths toward NGN by applying either Annex A or B. + +## Annex A + +## International CAS compelled register signalling packages + +(This annex forms an integral part of this Recommendation.) + +### A.1 International CAS Compelled Package + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | ICAS Compelled Package | +| Package ID: | icasc (0x007d) | +| Description: | This package defines ITU-T H.248 methods to support channel associated signalling (CAS) compelled standard en bloc register signalling. | +| Version: | 1 | +| Extends: | None | + +#### A.1.1 Properties + +##### A.1.1.1 Source Number Length + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Source Number Length | +| Property ID: | snl (0x0001) | +| Description: | Indicates that the calling party digits are to be collected by the MG up to a maximum length as specified by this parameter value. | +| Type: | Integer | +| Possible values: | Non-negative number of digits; 0 indicates no defined maximum length. | +| Default: | Provisioned | +| Defined in: | TerminationState | +| Characteristics: | Read/Write | + +##### A.1.1.2 Compelling Sequence Keepalive Time + +| | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Compelling Sequence Keepalive Time | +| Property ID: | cskt (0x0002) | +| Description: | Specifies the time duration for which the incoming MG may keep alive the compelling sequence waiting for the called party reachability status information (or alternative compelled sequence completion signal) from the MGC. | +| Type: | Integer | +| Possible values: | Non-negative number of milliseconds | +| Default: | Provisioned | +| Defined in: | TerminationState | +| Characteristics: | Read | + +#### A.1.2 Events + +##### A.1.2.1 Address + +| | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Address | +| Event ID: | addr (0x0001) | +| Description: | Reports the address parameters collected through compelled register signalling. The Event supports en bloc compelled register signalling. The MG will perform standard en bloc compelled register signalling, with all the relevant information (di, si, sc, etc.) being collected and then Notified at the end as a single ObservedEvent. After receiving the first incoming digit, the information collected and the order of collecting the information is determined by local MG provisioning. | + +###### A.1.2.1.1 EventsDescriptor parameters + +A DigitMap (as defined in clause 7.1.14 of [ITU-T H.248.1]) parameter activated for collection of destination number, by specifying a digitmap by name (previously configured) or by value. Where such a digitmap is missing, destination number shall be collected until end-of-digit signal is detected. + +##### A.1.2.1.2 ObservedEventsDescriptor parameters + +###### A.1.2.1.2.1 Destination Number + +| | | +|-------------------------|-------------------------------------------------------------------------------------------| +| Parameter name: | Destination Number | +| Parameter ID: | di (0x0001) | +| Description: | The called party number digit string collected through the compelled register signalling. | +| Type: | String | +| Optional: | No | +| Possible values: | A sequence of the characters '0' through '9'. | +| Default: | None | + +###### A.1.2.1.2.2 Destination Number Termination Method + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Destination Number Termination Method | +| Parameter ID: | dimeth (0x0002) | +| Description: | Indicates the reason for the generation of the Destination Number parameter. When a digitmap is present in the EventsDescriptor, this is a mandatory ObservedEventsDescriptor parameter. When a digitmap is absent from the EventsDescriptor, this parameter shall be absent from the ObservedEvents Descriptor. | +| Type: | Enumeration | +| Optional: | Yes | +| Possible values: | "UM" (0x0001) Unambiguous Match
"PM" (0x0002) Partial Match | +| Default: | None | + +###### A.1.2.1.2.3 Source Number + +**Parameter name:** Source Number +**Parameter ID:** si (0x0003) +**Description:** The calling party number digit string, that is collected during compelled register signalling. +**Type:** String +**Optional:** Yes +**Possible values:** A sequence of the characters '0' through '9'. +**Default:** None + +###### A.1.2.1.2.4 Source Number Termination Method + +**Parameter name:** Source Number Termination Method +**Parameter ID:** simeth (0x0004) +**Description:** If the Source Number parameter is reported, this parameter indicates the method of its termination. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "EP" (0x0001) End of Pulsing +"ML" (0x0002) Maximum Length +"TO" (0x0003) Timeout +**Default:** None + +###### A.1.2.1.2.5 Calling Subscriber Category 1 + +**Parameter name:** Calling Subscriber Category 1 +**Parameter ID:** sc1 (0x0005) +**Description:** The Calling Party subscriber's category, as collected through compelled register signalling delivered in response to category request A-3. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "NNPS" (0x0001) Non-priority subscriber (National Working) +"NPRS" (0x0002) Priority subscriber (National Working) +"NMNT" (0x0003) Maintenance equipment (National working) +"NOPR" (0x0004) Operator call (National Working) +"NDT" (0x0005) Data transmission (National working) +"ISOPR" (0x0006) Subscriber or operator without forward transfer facility (International working) +"IOPRF" (0x0007) Operator with forward transfer facility (International working) +"IDT" (0x0008) Data transmission (International working) +"IPRS" (0x0009) Priority subscriber (International working) +"NSMTR" (0x000a) Subscriber with meter (National working) +"SIDD" (0x000b) Subscriber with IDD +"NATL1" (0x000c) Spare for National Use (equivalent to II-4) + +"NATL2" (0x000d) Spare for National Use (equivalent to II-11) + "NATL3" (0x000e) Spare for National Use (equivalent to II-12) + "NATL4" (0x000f) Spare for National Use (equivalent to II-13) + "NATL5" (0x0010) Spare for National Use (equivalent to II-14) + "NATL6" (0x0011) Spare for National Use (equivalent to II-15) + +**Default:** None + +###### A.1.2.1.2.6 Echo Suppression + +**Parameter name:** Echo Suppression +**Parameter ID:** es (0x0006) +**Description:** Control information on echo suppressors. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "OGRQ" (0x0001) Call requires echo suppressors and outgoing half-echo suppressor has to be inserted + "NRQ" (0x0002) Call may not require any echo suppressor + "OGINS" (0x0003) Call requires echo suppressors and outgoing half-echo suppressor has already been inserted + "ICRQ" (0x0004) Call requires incoming echo suppressors to be inserted +**Default:** None + +###### A.1.2.1.2.7 Country Code + +**Parameter name:** Country Code +**Parameter ID:** cc (0x0007) +**Description:** If present, conveys the country code (and possibly the area code) information digits collected as a part of the compelled register signalling in international working. +**Type:** String +**Optional:** Yes +**Possible values:** A sequence of the characters '0' through '9'. +**Default:** None + +###### A.1.2.1.2.8 Discriminating Indicator + +**Parameter name:** Discriminating Indicator +**Parameter ID:** disc (0x0008) +**Description:** For automatic working, this will specify that a discriminating digit is used. For semi-automatic working, this will specify the service language (Language digit) to be used by the operator. For international working this may serve as a test call indicator. +**Type:** Enumeration +**Optional:** Yes + +**Possible values:** "DISC" (0x0001) Discriminating digit for automatic working + "FR" (0x0002) Language digit French + "EN" (0x0003) Language digit English + "GR" (0x0004) Language digit German + "RU" (0x0005) Language digit Russian + "SP" (0x0006) Language digit Spanish + "OT1" (0x0007) Language digit Other (as indicated by I-6 pulse) + "OT2" (0x0008) Language digit Other (as indicated by I-7 pulse) + "OT3" (0x0009) Language digit Other (as indicated by I-8 pulse) + "OT4" (0x000a) Language digit Other (as indicated by I-9 pulse) + "TCI" (0x000b) Call by automatic test equipment + +**Default:** None + +###### A.1.2.1.2.9 Nature of Circuit + +**Parameter name:** Nature of Circuit + +**Parameter ID:** noc (0x0009) + +**Description:** Reports if satellite links are included in circuits involved with the connection. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** "SATINC" (0x0001) Satellite link included + "SATNOINC" (0x0002) Satellite link not included + +**Default:** None + +###### A.1.2.1.2.10 Access Indicator + +**Parameter name:** Access Indicator + +**Parameter ID:** ai (0x000a) + +**Description:** If present, indicates that the call must be routed to the indicated position. In the case of "TST", test equipment address digits are conveyed in the destination number parameter. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** "INC" (0x0001) Incoming Operator + "DEL" (0x0002) Delay Operator + "TST" (0x0003) Test Equipment + +**Default:** None + +###### A.1.2.1.2.11 Calling Subscriber Category 2 + +**Parameter name:** Calling Subscriber Category 2 + +**Parameter ID:** sc2 (0x000b) + +**Description:** The Calling Party subscriber's category, as collected through compelled register signalling delivered in response to category request A-5. This category is occasionally known as the Billing category. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** + +| | | +|------------------|----------------------------------------------------------------------------------| +| "NNPS" (0x0001) | Non-priority subscriber (National Working) | +| "NPRS" (0x0002) | Priority subscriber (National Working) | +| "NMNT" (0x0003) | Maintenance equipment (National working) | +| "NOPR" (0x0004) | Operator call (National Working) | +| "NDT" (0x0005) | Data transmission (National working) | +| "ISOPR" (0x0006) | Subscriber or operator without forward transfer facility (International working) | +| "IOPRF" (0x0007) | Operator with forward transfer facility (International working) | +| "IDT" (0x0008) | Data transmission (International working) | +| "IPRS" (0x0009) | Priority subscriber (International working) | +| "NSMTR" (0x000a) | Subscriber with meter (National working) | +| "SIDD" (0x000b) | Subscriber with IDD | +| "NATL1" (0x000c) | Spare for National Use (equivalent to II-4) | +| "NATL2" (0x000d) | Spare for National Use (equivalent to II-11) | +| "NATL3" (0x000e) | Spare for National Use (equivalent to II-12) | +| "NATL4" (0x000f) | Spare for National Use (equivalent to II-13) | +| "NATL5" (0x0010) | Spare for National Use (equivalent to II-14) | +| "NATL6" (0x0011) | Spare for National Use (equivalent to II-15) | + +**Default:** None + +##### A.1.2.2 CAS Failure Event + +**Event name:** CAS Failure Event + +**Event ID:** casf (0x0002) + +**Description:** This event handles failure or abnormal register signalling conditions associated with this package. + +###### A.1.2.2.1 EventsDescriptor parameters + +None. + +###### A.1.2.2.2 ObservedEventsDescriptor parameters + +###### A.1.2.2.2.1 Error Code + +**Parameter name:** Error Code + +**Parameter ID:** ec (0x0001) + +**Description:** Describes the failure reason. + +**Type:** Enumeration + +**Optional:** No + +**Possible values:** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------| +| "RTO" (0x0001) | Register Signalling Timeout | +| "ADR" (0x0002) | Error during outpulsing | +| "ERR" (0x0003) | Error in compelling sequence with peer signalling entity. | +| "INC" (0x0004) | Information signalled by the MGC is incomplete, and the compelling sequence at the outgoing MG cannot continue. | +| "CSKT" (0x0005) | The Compelling Sequence Keepalive Timer has expired. | + +"SME" (0x0006) CAS protocol state machine error + +**Default:** None + +##### A.1.2.3 Called Party Reachability Status + +**Event name:** Called Party Reachability Status + +**Event ID:** cprs (0x0003) + +**Description:** Reports the line status of the called subscriber in order to terminate compelling. + +###### A.1.2.3.1 EventsDescriptor parameters + +None. + +###### A.1.2.3.2 ObservedEventsDescriptor parameters + +###### A.1.2.3.2.1 Subscriber Line Condition + +**Parameter name:** Subscriber Line Condition + +**Parameter ID:** lsts (0x0001) + +**Description:** Conveys the line condition of the subscriber. + +**Type:** Enumeration + +**Optional:** No + +**Possible values:** + +| | | +|-------------------|-------------------------------------------------| +| "UN" (0x0001) | Unallocated number | +| "SLB" (0x0002) | Subscriber line busy | +| "SLFC" (0x0003) | Subscriber line free, charge | +| "SLFNOC" (0x0004) | Subscriber line free, no charge | +| "SOO" (0x0005) | Subscriber out of order | +| "SIT" (0x0006) | Send special information tone | +| "NK" (0x0007) | Subscriber status not known, set-up speech path | +| "NATL1" (0x0008) | Spare for National Use (equivalent to B-1) | +| "NATL2" (0x0009) | Spare for National Use (equivalent to B-9) | +| "NATL3" (0x000a) | Spare for National Use (equivalent to B-10) | +| "NATL4" (0x000b) | Spare for National Use (equivalent to B-11) | +| "NATL5" (0x000c) | Spare for National Use (equivalent to B-12) | +| "NATL6" (0x000d) | Spare for National Use (equivalent to B-13) | +| "NATL7" (0x000e) | Spare for National Use (equivalent to B-14) | +| "NATL8" (0x000f) | Spare for National Use (equivalent to B-15) | + +**Default:** None + +##### A.1.2.4 Congestion + +**Event name:** Congestion + +**Event ID:** cng (0x0004) + +**Description:** Reports the register signal indicating network congestion at the far end. + +###### A.1.2.4.1 EventsDescriptor parameters + +None. + +###### **A.1.2.4.2 ObservedEventsDescriptor parameters** + +###### **A.1.2.4.2.1 Location** + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------| +| Parameter name: | Location | +| Parameter ID: | loc (0x0001) | +| Description: | Conveys the location of the congestion. | +| Type: | Enumeration | +| Optional: | Yes | +| Possible values: | "NATL" (0x0001) Congestion at national level
"INTL" (0x0002) Congestion at international level | +| Default: | NATL | + +#### **A.1.3 Signals** + +##### **A.1.3.1 Address** + +| | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Signal name: | Address | +| Signal ID: | addr (0x0001) | +| Description: | This is a composite signal that supplies all the necessary address parameters to start the compelling register signalling from the outgoing MG. The MG shall transmit only the information that is relevant to the compelling action configured at the MG and requested by the compelling peer. | +| Signal type: | TimeOut | +| Duration: | Depends on parameters supplied | + +###### **A.1.3.1.1 Additional parameters** + +###### **A.1.3.1.1.1 Destination Number** + +| | | +|-------------------------|-----------------------------------------------| +| Parameter name: | Destination Number | +| Parameter ID: | di (0x0001) | +| Description: | The called party number digits. | +| Type: | String | +| Optional: | No | +| Possible values: | A sequence of the characters '0' through '9'. | +| Default: | None | + +###### **A.1.3.1.1.2 Source Number** + +| | | +|-------------------------|-----------------------------------------------| +| Parameter name: | Source Number | +| Parameter ID: | si (0x0002) | +| Description: | The calling party number digits. | +| Type: | String | +| Optional: | Yes | +| Possible values: | A sequence of the characters '0' through '9'. | + +**Default:** Empty ("") + +###### A.1.3.1.1.3 Calling Subscriber Category 1 + +**Parameter name:** Calling Subscriber Category 1 + +**Parameter ID:** sc1 (0x0003) + +**Description:** The Calling Party subscriber's category, as collected through compelled register signalling delivered in response to category request A-3. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** + +| | | +|------------------|----------------------------------------------------------------------------------| +| "NNPS" (0x0001) | Non-priority subscriber (National Working) | +| "NPRS" (0x0002) | Priority subscriber (National Working) | +| "NMNT" (0x0003) | Maintenance equipment (National working) | +| "NOPR" (0x0004) | Operator call (National Working) | +| "NDT" (0x0005) | Data transmission (National working) | +| "ISOPR" (0x0006) | Subscriber or operator without forward transfer facility (International working) | +| "IOPRF" (0x0007) | Operator with forward transfer facility (International working) | +| "IDT" (0x0008) | Data transmission (International working) | +| "IPRS" (0x0009) | Priority subscriber (International working) | +| "NSMTR" (0x000a) | Subscriber with meter (National working) | +| "SIDD" (0x000b) | Subscriber with IDD | +| "NATL1" (0x000c) | Spare for National Use (equivalent to II-4) | +| "NATL2" (0x000d) | Spare for National Use (equivalent to II-11) | +| "NATL3" (0x000e) | Spare for National Use (equivalent to II-12) | +| "NATL4" (0x000f) | Spare for National Use (equivalent to II-13) | +| "NATL5" (0x0010) | Spare for National Use (equivalent to II-14) | +| "NATL6" (0x0011) | Spare for National Use (equivalent to II-15) | + +**Default:** None + +###### A.1.3.1.1.4 Echo Suppression + +**Parameter name:** Echo Suppression + +**Parameter ID:** es (0x0004) + +**Description:** Control information on echo suppressors. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** + +| | | +|------------------|--------------------------------------------------------------------------------------------| +| "OGRQ" (0x0001) | Call requires echo suppressors and outgoing half-echo suppressor has to be inserted | +| "NRQ" (0x0002) | Call may not require any echo suppressor | +| "OGINS" (0x0003) | Call requires echo suppressors and outgoing half-echo suppressor has already been inserted | +| "ICRQ" (0x0004) | Call requires incoming echo suppressors to be inserted | + +**Default:** None + +###### A.1.3.1.1.5 Country Code + +**Parameter name:** Country Code +**Parameter ID:** cc (0x0005) +**Description:** If present, conveys the country code (and possibly the area code) information digits. +**Type:** String +**Optional:** Yes +**Possible values:** A sequence of the characters '0' through '9'. +**Default:** None + +###### A.1.3.1.1.6 Discriminating Indicator + +**Parameter name:** Discriminating Indicator +**Parameter ID:** disc (0x0006) +**Description:** For automatic working, this will specify that a discriminating digit is used. For semi-automatic working, this will specify the service language (Language digit) to be used by the operator. For international working this may serve as a test call indicator, as well. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** +"DISC" (0x0001) Discriminating digit for automatic working +"FR" (0x0002) Language digit French +"EN" (0x0003) Language digit English +"GR" (0x0004) Language digit German +"RU" (0x0005) Language digit Russian +"SP" (0x0006) Language digit Spanish +"OT1" (0x0007) Language digit Other (as indicated by I-6 pulse) +"OT2" (0x0008) Language digit Other (as indicated by I-7 pulse) +"OT3" (0x0009) Language digit Other (as indicated by I-8 pulse) +"OT4" (0x000a) Language digit Other (as indicated by I-9 pulse) +"TCI" (0x000b) Call by automatic test equipment +**Default:** None + +###### A.1.3.1.1.7 Nature of Circuit + +**Parameter name:** Nature of Circuit +**Parameter ID:** noc (0x0007) +**Description:** Reports if satellite links are included in circuits involved with the connection. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** +"SATINC" (0x0001) Satellite link included +"SATNOINC" (0x0002) Satellite link not included +**Default:** None + +###### A.1.3.1.1.8 Access Indicator + +**Parameter name:** Access Indicator +**Parameter ID:** ai (0x0008) +**Description:** If present, indicates that call must be routed to the indicated position. In the case of "TST", test equipment address digits are conveyed in destination number parameter. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "INC" (0x0001) Incoming Operator +"DEL" (0x0002) Delay Operator +"TST" (0x0003) Test Equipment +**Default:** None + +###### A.1.3.1.1.9 Calling Subscriber Category 2 + +**Parameter name:** Calling Subscriber Category 2 +**Parameter ID:** sc2 (0x0009) +**Description:** The Calling Party subscriber's category, as collected through compelled register signalling delivered in response to category request A-5. This category is occasionally known as the Billing category. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "NNPS" (0x0001) Non-priority subscriber (National Working) +"NPRS" (0x0002) Priority subscriber (National Working) +"NMNT" (0x0003) Maintenance equipment (National working) +"NOPR" (0x0004) Operator call (National Working) +"NDT" (0x0005) Data transmission (National working) +"ISOPR" (0x0006) Subscriber or operator without forward transfer facility (International working) +"IOPRF" (0x0007) Operator with forward transfer facility (International working) +"IDT" (0x0008) Data transmission (International working) +"IPRS" (0x0009) Priority subscriber (International working) +"NSMTR" (0x000a) Subscriber with meter (National working) +"SIDD" (0x000b) Subscriber with IDD +"NATL1" (0x000c) Spare for National Use (equivalent to II-4) +"NATL2" (0x000d) Spare for National Use (equivalent to II-11) +"NATL3" (0x000e) Spare for National Use (equivalent to II-12) +"NATL4" (0x000f) Spare for National Use (equivalent to II-13) +"NATL5" (0x0010) Spare for National Use (equivalent to II-14) +"NATL6" (0x0011) Spare for National Use (equivalent to II-15) +**Default:** None + +##### A.1.3.2 Called Party Reachability Status + +**Signal name:** Called Party Reachability Status +**Signal ID:** cprs (0x0002) + +**Description:** Applies the called subscriber line status information signal to terminate compelling. + +**Signal type:** TimeOut + +**Duration:** Provisioned + +###### A.1.3.2.1 Additional parameters + +###### A.1.3.2.1.1 Subscriber Line Condition + +**Parameter name:** Subscriber Line Condition + +**Parameter ID:** lsts (0x0001) + +**Description:** Conveys the line condition of the subscriber. + +**Type:** Enumeration + +**Optional:** No + +**Possible values:** + +| | | +|-------------------|-------------------------------------------------| +| "UN" (0x0001) | Unallocated number | +| "SLB" (0x0002) | Subscriber line busy | +| "SLFC" (0x0003) | Subscriber line free, charge | +| "SLFNOC" (0x0004) | Subscriber line free, no charge | +| "SOO" (0x0005) | Subscriber out of order | +| "SIT" (0x0006) | Send special information tone | +| "NK" (0x0007) | Subscriber status not known, set-up speech path | +| "NATL1" (0x0008) | Spare for National Use (equivalent to B-1) | +| "NATL2" (0x0009) | Spare for National Use (equivalent to B-9) | +| "NATL3" (0x000a) | Spare for National Use (equivalent to B-10) | +| "NATL4" (0x000b) | Spare for National Use (equivalent to B-11) | +| "NATL5" (0x000c) | Spare for National Use (equivalent to B-12) | +| "NATL6" (0x000d) | Spare for National Use (equivalent to B-13) | +| "NATL7" (0x000e) | Spare for National Use (equivalent to B-14) | +| "NATL8" (0x000f) | Spare for National Use (equivalent to B-15) | + +**Default:** None + +##### A.1.3.3 Congestion + +**Signal name:** Congestion + +**Signal ID:** cng (0x0003) + +**Description:** Applies the indication to alert the far-end that congestion has occurred at the near-end. + +**Signal type:** Timeout + +**Duration:** Provisioned + +###### A.1.3.3.1 Additional parameters + +###### A.1.3.3.1.1 Location + +**Parameter name:** Location + +**Parameter ID:** loc (0x0001) + +**Description:** Conveys the location of the congestion. + +**Type:** Enumeration + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------| +| Optional: | Yes | +| Possible values: | "NATL" (0x0001) Congestion at national level
"INTL" (0x0002) Congestion at international level | +| Default: | Provisioned | + +#### A.1.4 Statistics + +None. + +#### A.1.5 Procedures + +##### A.1.5.1 Compelled signalling + +Compelled register signalling is a two-way process – it is not possible to simultaneously support an address signal and an address event. Furthermore, as the sequence of outpulsed data is under the control of the remote signalling peer, it is meaningless to update the address signal (or event) while a current address signal (or event) is ongoing. Therefore, attempts to apply simultaneous address signals or simultaneous address events on a termination, or attempts to update an address signal or event shall be rejected with error code 512, "Media Gateway unequipped to detect requested event" or 513, "Media Gateway unequipped to generate requested signals" as appropriate. + +Termination of the address signal or cancellation of the address event (e.g., by sending EventsDescriptor and/or SignalsDescriptor without icasc/addr, or through detection of another event when the KeepActive parameter is not present on that event) shall cause register signals to be immediately disasserted. + +##### A.1.5.2 General procedures + +The MG may be connected to a peer compelled CAS switch for compelled signalling, a peer MG for media transport and a MGC for exchanging signalling information using ITU-T H.248 with this package. + +This package uses the following conventions for incoming/outgoing MG: + +- Incoming MG: The peer R2 exchange initiates the call signalling towards the MG. +- Outgoing MG: The MG initiates the call signalling towards the peer R2 exchange. + +An incoming MG might not be provisioned to recognize the "end of pulsing" compelled forward register signal. Therefore, the incoming MG shall detect the end of digit information in called party number based on a MGC supplied digitmap. This also takes care of situations where identification of the end of digit sequence is achieved through length determination or timeout mechanisms. The calling party number shall be compelled until the maximum length of the calling party number is achieved, the end of pulsing is encountered or a timeout occurs. The maximum length is provisioned in the MG, and may be altered by the MGC via the snl parameter. + +The MG shall be provisioned with a list of possible country codes. The MG shall compel the country code digits based upon this provisioned information. + +##### A.1.5.3 Incoming *en bloc* compelled register signalling + +An example of incoming *en bloc* compelled register signalling is given in Figure A.1. + +![Sequence diagram showing incoming en bloc compelled register signalling between Exchange, MG, and MGC.](366a77fdefb0097b3289b4a011911390_img.jpg) + +``` + +sequenceDiagram + participant Exchange + participant MG + participant MGC + + Note right of MG: MG is provisioned to collect calling party category after called party number + Note right of MG: MG is provisioned to collect calling party number after calling party category + + Exchange->>MG: seizing + MG->>MGC: Modify Events{bcas/sz, icas/casf} + MGC->>MG: Notify ObservedEvents{bcas/sz} + MGC->>MG: Modify Signals{bcas/sza}, Events{icasc/casf, icasc/addr} + MG->>Exchange: seize ack + Exchange->>MG: 1st digit = 9 + MG->>Exchange: send next (called party) digit + Exchange->>MG: 2nd digit = 8 + MG->>Exchange: send next (called party) digit + Exchange->>MG: 3rd digit = 7 + MG->>Exchange: send next (called party) digit + Exchange->>MG: 4th digit = 6 + MG->>Exchange: send next (called party) digit + Exchange->>MG: end of digits + MG->>Exchange: send calling party category + Exchange->>MG: calling party category = NNPS + MG->>Exchange: send calling party number + Exchange->>MG: 1st digit = 4 + MG->>Exchange: send next calling party digit + Exchange->>MG: 2nd digit = 0 + MG->>Exchange: send next calling party digit + Exchange->>MG: 3rd digit = 3 + MG->>Exchange: send next calling party digit + Exchange->>MG: end of digits + MG->>MGC: Notify ObservedEvents{icasc/addr {di=9876, sc=NNPS, si=403, simeth=EP}} + MGC->>MG: Modify Signals{icasc/cprs{SLFC}} + MG->>Exchange: called subscriber status = SLFC + +``` + +The diagram illustrates the interaction for incoming *en bloc* compelled register signalling. It involves three lifelines: Exchange, MG, and MGC. The process begins with the Exchange sending a 'seizing' signal to the MG. The MG then sends a 'Modify Events{bcas/sz, icas/casf}' message to the MGC, which responds with 'Notify ObservedEvents{bcas/sz}'. The MGC then sends 'Modify Signals{bcas/sza}, Events{icasc/casf, icasc/addr}' to the MG. The MG sends a 'seize ack' back to the Exchange. The Exchange then sends the first digit '9', and the MG responds with 'send next (called party) digit'. This continues with '2nd digit = 8', 'send next (called party) digit', '3rd digit = 7', 'send next (called party) digit', '4th digit = 6', 'send next (called party) digit', and 'end of digits'. The MG then sends 'send calling party category' to the Exchange, which responds with 'calling party category = NNPS'. The MG then sends 'send calling party number' to the Exchange. The Exchange sends '1st digit = 4', and the MG responds with 'send next calling party digit'. This continues with '2nd digit = 0', 'send next calling party digit', '3rd digit = 3', 'send next calling party digit', and 'end of digits'. The MG then sends 'Notify ObservedEvents{icasc/addr {di=9876, sc=NNPS, si=403, simeth=EP}}' to the MGC, which responds with 'Modify Signals{icasc/cprs{SLFC}}'. Finally, the MG sends 'called subscriber status = SLFC' to the Exchange. Two callouts indicate that the MG is provisioned to collect the calling party category after the called party number, and the calling party number after the calling party category. + +Sequence diagram showing incoming en bloc compelled register signalling between Exchange, MG, and MGC. + +NOTE – Transaction replies are not shown for clarity. + +H.248.29\_FA.1 + +**Figure A.1 – Incoming *en bloc* compelled register signalling example** + +*En bloc* compelled register signalling is triggered by the MGC by sending the *icasc/addr* event in an Events Descriptor. The MG autonomously takes control of the compelling sequence and collects all the information, sending a single Notify message when completed. The completion of the compelling sequence will depend on the configuration of the MG and consequent actions by the MGC (see below). + +Compelling action starts by the peer signalling entity sending a forward signal. This may be the first digit of called party number or the Country Code Indicator. + +The incoming MG shall collect called party number digits using the digit map specified by the MGC, in accordance with digit map completion event rules of [ITU-T H.248.1] and the "end of pulsing" register signal. + +During called party number compelling when the MG determines that an unambiguous match has been found with an alternative in the digit map, the MG shall report the collected digits with the Destination Number Termination Method set to "Unambiguous Match". This matching criterion may coincide with the reception of the "end of pulsing" signal. In the absence of a digitmap this "end of pulsing" register signal shall determine the unambiguous termination condition of the accumulated digits. + +Digit collection may terminate due to completion by timer expiry or the reception of "end of pulsing" signal when an alternative in the digit map has partially matched. In this instance, the MG shall report the collected digits with the Destination Number Termination Method set to "Partial Match". + +The MG shall collect calling party number digit string until any of the following events occur: + +- Reception of end-of-pulsing signal. The MG shall report all the collected calling party digits with the Source Number Termination Method set to "End of Pulsing". +- Collection of the maximum number of digits for the calling party number, as specified by the snl parameter. The MG shall report all the collected calling party digits with the Source Number Termination Method set to "Maximum Length". +- A digit timeout occurs, in accordance with a value provisioned at the MG. The timer is started the moment calling party number compelling starts. The MG shall report all the collected calling party digits with the Source Number Termination Method set to "Timeout". + +If connected to an international trunk where exchange of country code may occur, then the MG shall be locally provisioned with the list of country codes. Based on this, the incoming MG may terminate the compelling of the country code digits. + +Following detection of the end of each address parameter, the MG sends a backward compelled register signal to request the next group of information (e.g., calling party category) based on MG provisioned ordering. + +Following completion of compelling of all necessary address parameters based on MG provisioning, the MG shall notify the MGC and shall wait for a signal to terminate the compelling sequence from the MGC, e.g., icasc/cprs or icasc/cng backwards signal response. The MG shall wait for a timeout equal to the value of the cskt property. If the timer expires without the receipt of a signal – immediately if cskt is set to 0 – the MG shall terminate compelling with a suitable backwards register signal. + +The following conditions during impulse shall be deemed to be CAS failure conditions. The MG shall report the icasc/casf event with ec equal to "ERR" when any of the following occurs: + +- an initial digit timeout (timeout based on local provisioning); +- failure of the signalling peer to disassert the transmitted signal in response to the response digit (timeout based on local provisioning); +- an inter-digit timeout (timeout based on local provisioning); +- an unexpected signal. + +When the Compelling Sequence Keepalive Timer expires, the MG shall report the icasc/casf event with ec equal to "CSKT". + +##### **A.1.5.4 Outgoing *en bloc* compelled register signalling** + +After receiving the icasc/addr signal and if the Country Code parameter is present, the termination shall outpulse the echo suppression parameter followed by the Country Code Indicator; otherwise, the termination shall outpulse the first digit of the di string. Thereafter the termination shall respond to the signals requested by its signalling peer. + +When a new parameter is requested for which a termination has no data, the signal shall be deemed to have failed. At this time g/sc event shall be sent, if requested as part of the signal request, with the Not Completed termination method. It will be the responsibility of the incoming signalling peer to recover the compelled signalling phase or close down the call. MGs may provide provisioned default values for parameters. Specified parameters of the address signal shall override the provisioned values. + +Upon receipt of the backwards "Called Party Reachability Status" register signal (or an alternative signal indicating the end of compelling) from its signalling peer, the signal is deemed to be complete. At this time g/sc event shall be sent, if requested as part of the signal request, with the Timeout termination method. + +If the signalling peer does not respond to a transmitted signal within the provisioned timeout, or the response is not disasserted after the transmitted signal is disasserted within the provisioned timeout, or the signalling peer sends an unexpected backwards signal, then the signal is deemed to have failed to complete. At this time g/sc event shall be sent, if requested as part of the signal request, with the Not Completed termination method. + +### A.2 International CAS Compelled with Overlap Package + +| | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Package name: | ICAS Compelled with Overlap Package | +| Package ID: | icasco (0x007e) | +| Description: | This package defines ITU-T H.248 methods to support channel associated signalling (CAS) compelled overlap register signalling. | +| Version: | 1 | +| Extends: | icase version 1 | + +#### A.2.1 Properties + +None. + +#### A.2.2 Events + +##### A.2.2.1 Address + +| | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Address | +| Event ID: | addr (0x0001) | +| Description: | Reports the address parameters collected through compelled register signalling. This event extends the icase/addr event to support overlap compelled register signalling in addition to en bloc compelled signalling. | + +###### A.2.2.1.1 EventsDescriptor parameters + +###### A.2.2.1.1.1 Compelling Sequence + +| | | +|------------------------|----------------------------------------------------------------------------------------------| +| Parameter name: | Compelling Sequence | +| Parameter ID: | seq (0x0001) | +| Description: | Defines the order in which compelled information is collected. See the procedures for usage. | +| Type: | String | +| Optional: | Yes | + +**Possible values:** See the procedures for the syntax of this parameter. + +**Default:** Empty ("") + +###### A.2.2.1.2 ObservedEventsDescriptor parameters + +None. + +##### A.2.2.2 Request Backwards + +**Event name:** Request Backwards + +**Event ID:** reqback (0x0005) + +**Description:** Reports that the terminating signalling peer has requested a category that is not present as part of current addr signal via the backwards signalling channel. + +###### A.2.2.2.1 EventsDescriptor parameters + +None. + +###### A.2.2.2.2 ObservedEventsDescriptor parameters + +###### A.2.2.2.2.1 Category + +**Parameter name:** Category + +**Parameter ID:** cat (0x0001) + +**Type:** Enumeration + +**Optional:** No + +**Possible values:** + +| | | +|-----------------|--------------------------------------| +| "SI" (0x0001) | Collect source number | +| "SC1" (0x0002) | Collect calling subscriber category | +| "CC" (0x0003) | Collect country code | +| "ES" (0x0004) | Collect echo suppression information | +| "DISC" (0x0005) | Collect discriminating indicator | +| "NOC" (0x0006) | Collect nature of circuit | +| "AI" (0x0007) | Collect access indicator | +| "SC2" (0x0008) | Collect billing category | + +**Default:** None + +#### A.2.3 Signals + +##### A.2.3.1 Address + +**Signal name:** Address + +**Signal ID:** addr (0x0001) + +**Description:** This extends the icasc/addr signal with a parameter value extension to the di parameter. + +**Signal type:** TimeOut + +**Duration:** Depends on parameters supplied + +###### A.2.3.1.1 Additional parameters + +###### A.2.3.1.1.1 Destination Number + +**Parameter name:** Destination Number + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter ID: | di (0x0001) | +| Description: | The called party number digits. | +| Type: | String | +| Optional: | No | +| Possible values: | A sequence of the characters '0' through '9' and 'F'. The end-of-digit character is explicit ('F') and will only be sent if the next digit is requested after the last 0-9 digit has been sent and the character is present in the string. | +| Default: | None | + +##### A.2.3.2 Delta Address + +| | | +|---------------------|-------------------------------------------------------------------------------------| +| Signal name: | Delta Address | +| Signal ID: | delta (0x0004) | +| Description: | This signal provides a mechanism to add parameters to a current icasco/addr signal. | +| Signal type: | Brief | +| Duration: | Variable | + +###### A.2.3.2.1 Additional parameters + +This signal may have all the same parameters as the icasco/addr signal. + +#### A.2.4 Statistics + +None. + +#### A.2.5 Procedures + +##### A.2.5.1 Compelling sequence syntax and usage + +If the seq parameter is empty (i.e., seq=""), then the MG will perform standard *en bloc* compelled register signalling, with all the relevant information (di, si, sc, etc.) being collected and then notified at the end as a single ObservedEvent. The information collected and its order is determined by MG provisioning. + +If the seq parameter is provided, then the MGC is able to specify in which order the information (di, si, sc, etc.) is collected. The MGC can also request that particular information elements be returned as they are collected. These behaviours are used to support overlap compelled register signalling. + +The seq parameter is a text string consisting of information elements separated by the forward slash '/' character. The list of possible information elements are: + +- di – collect destination number. The di token may be followed by a previously or concurrently defined digitmap name enclosed in normal parentheses "di(digitMapName)", or a digitmap enclosed first in brackets, and then in parentheses "di({digitMapValue})". This digitmap is used to collect the destination number. The digitMapName and digitMapValue shall comply with the ITU-T H.248.1 ABNF definition. If the di token does not include a DigitMap name or value, then the digit map defined within the EventsDescriptor is used. If a digit map is neither provided within the di portion of this parameter nor as an EventDM parameter, then digits are collected until the end of pulsing digit is received. Once the digitmap completes, or the end of pulsing digit is received, the di information shall be reported. +- si – collect source number + +- sc1 – collect calling subscriber category +- cc – country code +- es – collect echo suppression information +- disc – collect discriminating indicator +- noc – collect nature of circuit +- ai – access indicator +- sc2 – collect billing category +- N – report all unreported collected information. This is not required after the last token because a Notify will be sent upon completion of information collection. This token is used for overlap compelled register signalling to allow intermediate results to be reported to the MGC. + +The di information element and the N report request may appear multiple times. The other information elements may only appear once any given seq parameter. + +An example Events descriptor (with related DigitMap descriptors) is: + Events{icasco/addr{seq="di(dm1)/sc/si/N/di(dm2)"}} ,DigitMap=dm1{xxx} ,DigitMap=dm2{x.F} . + +##### A.2.5.2 Incoming overlap compelled register signalling + +An example of overlap compelled register signalling is given in Figure A.2. + +![Sequence diagram showing incoming overlap compelled register signalling between Exchange, MG, and MGC. The diagram illustrates the flow of messages for seizing, digit collection, and notification. Callers: MG, MGC. Receiver: Exchange. Sequence: 1. MG sends 'seizing' to Exchange. 2. MGC sends 'Modify Events' to MG. 3. MG sends 'Notify ObservedEvents' to MGC. 4. MGC sends 'Modify Signals' to MG. 5. MG sends 'seize ack' to Exchange. 6. Exchange sends '1st digit = 9' to MG. 7. Exchange sends 'send next (called party) digit' to MG. 8. Exchange sends '2nd digit = 8' to MG. 9. MG sends 'Notify ObservedEvents' to MGC. 10. Exchange sends 'send calling party category' to MG. 11. Exchange sends 'calling party category = NNPS' to MG. 12. Exchange sends 'send calling party number' to MG. 13. Exchange sends '1st digit = 4' to MG. 14. Exchange sends 'send next calling party digit' to MG. 15. Exchange sends '2nd digit = 0' to MG. 16. Exchange sends 'send next calling party digit' to MG. 17. Exchange sends '3rd digit = 3' to MG. 18. Exchange sends 'send next calling party digit' to MG. 19. Exchange sends 'end of digits' to MG. 20. MG sends 'Notify ObservedEvents' to MGC. 21. Exchange sends 'send next called party digit' to MG. 22. Exchange sends '3rd digit = 7' to MG. 23. Exchange sends 'send next called party digit' to MG. 24. Exchange sends '4th digit = 6' to MG. 25. Exchange sends 'send next called party digit' to MG. 26. Exchange sends 'end of digits' to MG. 27. MG sends 'Notify ObservedEvents' to MGC. 28. MGC sends 'Modify Signals' to MG. 29. Exchange sends 'called subscriber status = SLFC' to MG. Callouts: 'seq parameter dictates that Notify is sent and that calling party category and number is to be collected next.' (pointing to step 9), 'seq parameter dictates that Notify is sent and that remaining called party digits are to be collected next' (pointing to step 20), 'The last element in seq parameter is Notified.' (pointing to step 27).](fa01531ea2c45beeb4036005da3037a4_img.jpg) + +Sequence diagram showing incoming overlap compelled register signalling between Exchange, MG, and MGC. The diagram illustrates the flow of messages for seizing, digit collection, and notification. Callers: MG, MGC. Receiver: Exchange. Sequence: 1. MG sends 'seizing' to Exchange. 2. MGC sends 'Modify Events' to MG. 3. MG sends 'Notify ObservedEvents' to MGC. 4. MGC sends 'Modify Signals' to MG. 5. MG sends 'seize ack' to Exchange. 6. Exchange sends '1st digit = 9' to MG. 7. Exchange sends 'send next (called party) digit' to MG. 8. Exchange sends '2nd digit = 8' to MG. 9. MG sends 'Notify ObservedEvents' to MGC. 10. Exchange sends 'send calling party category' to MG. 11. Exchange sends 'calling party category = NNPS' to MG. 12. Exchange sends 'send calling party number' to MG. 13. Exchange sends '1st digit = 4' to MG. 14. Exchange sends 'send next calling party digit' to MG. 15. Exchange sends '2nd digit = 0' to MG. 16. Exchange sends 'send next calling party digit' to MG. 17. Exchange sends '3rd digit = 3' to MG. 18. Exchange sends 'send next calling party digit' to MG. 19. Exchange sends 'end of digits' to MG. 20. MG sends 'Notify ObservedEvents' to MGC. 21. Exchange sends 'send next called party digit' to MG. 22. Exchange sends '3rd digit = 7' to MG. 23. Exchange sends 'send next called party digit' to MG. 24. Exchange sends '4th digit = 6' to MG. 25. Exchange sends 'send next called party digit' to MG. 26. Exchange sends 'end of digits' to MG. 27. MG sends 'Notify ObservedEvents' to MGC. 28. MGC sends 'Modify Signals' to MG. 29. Exchange sends 'called subscriber status = SLFC' to MG. Callouts: 'seq parameter dictates that Notify is sent and that calling party category and number is to be collected next.' (pointing to step 9), 'seq parameter dictates that Notify is sent and that remaining called party digits are to be collected next' (pointing to step 20), 'The last element in seq parameter is Notified.' (pointing to step 27). + +NOTE – ITU-T H.248 responses are not shown for clarity. + +H.248.29(13)\_FA.2 + +**Figure A.2 – Incoming overlap compelled register signalling example** + +Overlap for a compelled sequence entails breaking the collected information into separate ObservedEvents reported to the MGC. The MG behaviour is similar to *en bloc* with two key differences: + +- The MG requests compelled register information (e.g., called party, calling party category, calling party number, etc.) from the exchange in the order indicated by the MGC in the request message. Order is not driven by MG provisioning. +- The MG sends Notify commands during the compelling sequence as indicated by the MGC in the seq parameter. + +The MGC performs overlap compelled register signalling by sending an icasco/addr event with the new seq parameter. The order of information elements (e.g., called party, calling party category, calling party number, etc.) in the seq parameter specifies the order in which compelled information is collected. + +If an information element in the seq parameter is followed by "N", then a Notify command with all the collected information since the last Notify shall be sent to the MGC once the information element is collected. The di information elements and the last information element in the seq parameter are always notified, regardless of whether they are followed by "N" or not. + +The collection of called party number (di) can be split into many parts, each part having its own digitmap. For example, a MGC may request to be notified of the first few called-party digits ("di({xxx})"), followed by other information (for example, calling party category and number), and then followed by the remaining called-party digits ("di({x.F})") and other information. + +##### **A.2.5.3 Outgoing overlap compelled register signalling** + +Overlap compelling differs from *en bloc* compelling in that the address parameters may be updated during the compelling exchange. Therefore, the MGC shall be permitted to add new parameters, using the icasco/delta signal while a previous icasco/addr signal is still being signalled, as long as that original icasco/addr signal is kept active using the "KA" parameter. Such address parameters may have been requested by the MG by notification of the reqlback event. New address parameters (apart from the di parameter) may be provided in their entirety in the original signal, or in any subsequent Signals descriptor. The di parameter may be provided in instalments in any address signal, where subsequent values append to the existing value. + +The "F" character terminating a di string when applied in icasco/addr signal is not implicit. If the current di string is being compelled and the last explicit digit (0-9) has been sent and the incoming peer requests "next digit", the outgoing termination will wait for further digits to be supplied as part of a subsequent icasco/delta signal. Any di parameters in such an icasco/delta signal will be appended to the value of the current di parameter. If the MG is waiting for further di digits as part of the compelling sequence, then the MG shall play out the first digit of the latest di parameter instalment immediately when it is received. + +Other Address parameters (apart from di) may be provided in subsequent messages. As these parameters do not append to previously signalled parameters and there can be no guarantee as to where in the compelling sequence, such a message may arrive (such a parameter could arrive part way through the compelling of the previous value), such parameters are valid once per-parameter type within a compelled sequence. For example, if the "es" parameter is received in the first icasco/addr signal, instances of "es" in subsequent icasco/delta messages will be ignored. + +As icasco/delta is a signal that amends the current icasco/addr signal, transmission of a SignalsDescriptor with a delta signal and without a concurrent icasco/addr {...., KA} signal is meaningless and shall be NACKed or ignored. Receipt of a delta signal concurrent with icasco/addr {...., KA} signals after completion of addr signal causes the delta signal to be discarded along with icasco/addr signal. Multiple delta signals may be sent (with appropriate KA parm) – where these contain instalments to the di parameter, these will be appended in the order they are inserted in the SignalsDescriptor. + +An example is given in Figure A.3 below. + +![Sequence diagram showing outgoing overlap compelled register signalling between MGC, MG, and Exchange. The diagram illustrates the interaction for setting up a call, including signal modifications, digit sending, and calling party category exchange.](d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg) + +``` + +sequenceDiagram + participant MGC + participant MG + participant Exchange + + Note left of MGC: Initial state + MGC->>MG: Modify Signals {bcas/sz}, Events {bcas/sza} + MG->>Exchange: seizing + Exchange-->>MG: seize ack + MG-->>MGC: Notify ObservedEvents {bcas/sza} + + Note left of MGC: Pause + MGC->>MG: Modify Signals {icasco/addr {di=12}} + MG->>Exchange: 1st digit = 1 + Exchange-->>MG: send next digit + MG->>Exchange: 2nd digit = 2 + Exchange-->>MG: send next digit + + Note left of MGC: Pause + MGC->>MG: Modify Signals {icasco/delta {di=34#,si=9876}} + MG->>Exchange: 3rd digit = 3 + Exchange-->>MG: send next digit + MG->>Exchange: 4th digit = 4 + Exchange-->>MG: send next digit + MG->>Exchange: end of digits + Exchange-->>MG: send calling party category + + Note left of MGC: Pause + MGC->>MG: Modify Signals {icasco/addr {sc = NNPS}} + MG->>Exchange: calling party category = NNPS + Exchange-->>MG: etc. + +``` + +H.248.29(07)\_FA3 + +Sequence diagram showing outgoing overlap compelled register signalling between MGC, MG, and Exchange. The diagram illustrates the interaction for setting up a call, including signal modifications, digit sending, and calling party category exchange. + +**Figure A.3 – Outgoing overlap compelled register signalling example** + +### A.3 International CAS Compelled with End-to-End Package + +| | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Package name: | ICAS Compelled with End-to-End Package | +| Package ID: | icasce (0x007f) | +| Description: | This package defines ITU-T H.248 methods to support channel associated signalling (CAS) compelled end-end register signalling. | +| Version: | 1 | +| Extends: | icasco version 1 | + +#### A.3.1 Properties + +None. + +#### A.3.2 Events + +None. + +#### A.3.3 Signals + +##### A.3.3.1 Compelled Backward Register Signalling + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Signal name: | Compelled Backward Register Signalling | +| Signal ID: | back (0x0005) | +| Description: | This signal provides a further choice of backwards signals to terminate a compelling sequence that allows the incoming MG to request the peer outgoing signalling entity to repeat part or all of the register signalling. See the procedures for usage information. | +| Signal type: | Timeout | +| Duration: | Variable depending on compelling peer. | + +###### A.3.3.1.1 Additional parameters + +###### A.3.3.1.1.1 Signal Type + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Signal Type | +| Parameter ID: | sig (0x0001) | +| Description: | This parameter specifies the backward compelled signal that should be sent. | +| Type: | Enumeration | +| Optional: | No | +| Possible values: | "LB1" (0x0001) Last but one
"LB2" (0x0002) Last but two
"LB3" (0x0003) Last but three
"NATL1" (0x0004) Spare for National Use (equivalent to A-9)
"NATL2" (0x0005) Spare for National Use (equivalent to A-10) | +| Default: | None | + +#### A.3.4 Statistics + +None. + +#### A.3.5 Procedures + +##### A.3.5.1 Usage of the back signal + +The back signal is used when the end-to-end signalling phase is being entered. This may be sent when the incoming MG has collected all or part of the dialled number, has notified the MGC and is currently waiting with the Compelling Sequence Keepalive Timer (cskt) running. In this case, it is likely that the incoming MG, as part of a distributed switch, has established an end-to-end connection through to a peer MG which itself is connected to an incoming port on a CAS switch running compelled signalling. + +Receipt by the incoming MG of a message with a "back" signal and an empty Events Descriptor causes the active addr event to be terminated and the back signal to be applied. + +The icasce/back signal is completed when the MG detects that the current forward signal (from the compelling peer) has been removed. The MGC may request NotifyCompletion Timeout on the back signal and request the g/sc event so that it is notified when this happens. This is used as a way to let the MGC know when it is suitable to use end-to-end signalling. + +If the icasce/back signal is received while the MG is not running the Compelling Sequence Keepalive Timer, then the MG will treat the signal as if it had instantaneously completed and will not modify the compelled register signalling. + +##### A.3.5.2 End-to-end (E2E) compelled register signalling + +An example of end-to-end (E2E) compelled register signalling procedures where the MGC decides not to use E2E signalling is shown in Figure A.4. + +![Sequence diagram showing the interaction between Exchange, MG, and MGC. The Exchange sends a 'seizing' signal to the MG. The MG sends 'Modify Events{bcas/sz, icas/casf}' and 'Notify ObservedEvents{bcas/sz}' to the MGC. The MGC responds with 'Modify Signals{bcas/sza}, Events{icas/cf, icasco/casf, icasce/addr{seq=di, DigitMap={xx}}}' to the MG. The MG sends a 'seize ack' to the Exchange. The Exchange then sends digits: '1st digit = 4', '2nd digit = 3'. A callout box states 'MGC decides NOT to go E2E based on di=43'. The MG sends 'Notify ObservedEvents{icasce/addr{di=43, dimeth=UM}}' to the MGC. The MGC responds with 'Modify Events{icas/cf, icasco/casf, icasce/addr{seq=di/sc/si, DigitMap={x.F}}}'. A callout box from the MG to the Exchange states 'Backward signal is not immediately sent due to cskt not equal 0'. Another callout box explains that on receiving a new icasce/addr event, the MG sends the backward signal and then performs en bloc procedure. The Exchange continues with digits 3 through 6 and 'end of digits'. The MG sends 'send calling party category' to the Exchange, which responds with 'calling party category = NNPS'. The MG sends 'send calling party number' to the Exchange, which responds with digits 1 through 3 and 'end of digits'. The MG sends 'Notify ObservedEvents{icasce/addr{di=9876, dimeth=PM, sc=NNPS, si=403, simeth=EP}}' to the MGC. The MGC responds with 'Modify Signals{icas/cprs{SLFC}}' to the MG. Finally, the MG sends 'called subscriber status = SLFC' to the Exchange.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant Exchange + participant MG + participant MGC + + Exchange->>MG: seizing + MG->>MGC: Modify Events{bcas/sz, icas/casf} + MG->>MGC: Notify ObservedEvents{bcas/sz} + MGC->>MG: Modify Signals{bcas/sza}, Events{icas/cf, icasco/casf, icasce/addr{seq=di, DigitMap={xx}}} + MG->>Exchange: seize ack + Exchange->>MG: 1st digit = 4 + MG->>Exchange: send next (called party) digit + Note right of MG: MGC decides NOT to go E2E based on di=43 + Exchange->>MG: 2nd digit = 3 + MG->>MGC: Notify ObservedEvents{icasce/addr{di=43, dimeth=UM}} + Note left of MG: Backward signal is not immediately sent due to cskt not equal 0 + MGC->>MG: Modify Events{icas/cf, icasco/casf, icasce/addr{seq=di/sc/si, DigitMap={x.F}}} + MG->>Exchange: send next (called party) digit + Note right of MG: On receiving a new icasce/addr event, the MG sends the backward signal and then performs en bloc procedure (in this example). (NOTE – Alternatively, the MGC may request overlap procedure.) + Exchange->>MG: 3rd digit = 9 + MG->>Exchange: send next (called party) digit + Exchange->>MG: 4th digit = 8 + MG->>Exchange: send next (called party) digit + Exchange->>MG: 5th digit = 7 + MG->>Exchange: send next (called party) digit + Exchange->>MG: 6th digit = 6 + MG->>Exchange: send next (called party) digit + Exchange->>MG: end of digits + MG->>Exchange: send calling party category + Exchange->>MG: calling party category = NNPS + MG->>Exchange: send calling party number + Exchange->>MG: 1st digit = 4 + MG->>Exchange: send next calling party digit + Exchange->>MG: 2nd digit = 0 + MG->>Exchange: send next calling party digit + Exchange->>MG: 3rd digit = 3 + MG->>Exchange: send next calling party digit + Exchange->>MG: end of digits + MG->>MGC: Notify ObservedEvents{icasce/addr{di=9876, dimeth=PM, sc=NNPS, si=403, simeth=EP}} + MGC->>MG: Modify Signals{icas/cprs{SLFC}} + MG->>Exchange: called subscriber status = SLFC + +``` + +Sequence diagram showing the interaction between Exchange, MG, and MGC. The Exchange sends a 'seizing' signal to the MG. The MG sends 'Modify Events{bcas/sz, icas/casf}' and 'Notify ObservedEvents{bcas/sz}' to the MGC. The MGC responds with 'Modify Signals{bcas/sza}, Events{icas/cf, icasco/casf, icasce/addr{seq=di, DigitMap={xx}}}' to the MG. The MG sends a 'seize ack' to the Exchange. The Exchange then sends digits: '1st digit = 4', '2nd digit = 3'. A callout box states 'MGC decides NOT to go E2E based on di=43'. The MG sends 'Notify ObservedEvents{icasce/addr{di=43, dimeth=UM}}' to the MGC. The MGC responds with 'Modify Events{icas/cf, icasco/casf, icasce/addr{seq=di/sc/si, DigitMap={x.F}}}'. A callout box from the MG to the Exchange states 'Backward signal is not immediately sent due to cskt not equal 0'. Another callout box explains that on receiving a new icasce/addr event, the MG sends the backward signal and then performs en bloc procedure. The Exchange continues with digits 3 through 6 and 'end of digits'. The MG sends 'send calling party category' to the Exchange, which responds with 'calling party category = NNPS'. The MG sends 'send calling party number' to the Exchange, which responds with digits 1 through 3 and 'end of digits'. The MG sends 'Notify ObservedEvents{icasce/addr{di=9876, dimeth=PM, sc=NNPS, si=403, simeth=EP}}' to the MGC. The MGC responds with 'Modify Signals{icas/cprs{SLFC}}' to the MG. Finally, the MG sends 'called subscriber status = SLFC' to the Exchange. + +**Figure A.4 – Example where MGC decides NOT to use end-to-end signalling** + +An example of end-to-end (E2E) compelled register signalling procedures where MGC decides to use E2E signalling is shown in Figure A.5. + +![Sequence diagram showing E2E compelled register signalling between Exchange, MG, MGC, and peer MG. The diagram includes messages like seizing, seize ack, 1st digit = 6, send next (called party) digit, 2nd digit = 1, and various MGC/ MG commands. Callouts explain the logic, such as 'MGC decides to go E2E based on di=61' and 'When the current forward signal is stopped, the MG notifies signal completion.'](85e2327652d513a7fee8fdbf97ad06f1_img.jpg) + +The sequence diagram illustrates the interaction for E2E compelled register signalling. The lifelines are Exchange, MG, MGC, and peer MG. The process starts with the Exchange sending a 'seizing' message to the MG. The MG responds with 'Notify ObservedEvents{bcas/sz}' to the MGC. The MGC replies with 'Modify Signals{icas/sza}, Events{icas/cf,icasce/casf, icasce/addr{seq=di, DigitMap={xx}}}' to the MG. The MG sends a 'seize ack' back to the Exchange. The Exchange then sends '1st digit = 6' and 'send next (called party) digit' to the MG. A callout indicates 'MGC decides to go E2E based on di=61'. The MG sends '2nd digit = 1' to the Exchange. Another callout notes 'Backward signal is not immediately sent due to cskt not equal 0'. The MG then sends 'Notify ObservedEvents{icasce/addr{di=61, dimeth=UM}}' to the MGC. The MGC responds with 'Modify Signals{icasce/back{sig=first, NotifyCompletion={TimeOut}}}, Events{g/sc, icas/cf, icasce/casf}' to the MG. The MG sends 'send first (called party) digit' to the Exchange. A callout states 'On receiving the icasce/back signal, the MG sends the requested backward signal.' and 'When the current forward signal is stopped, the MG notifies signal completion.' The MG then sends 'Notify ObservedEvents{g/sc{SigID=icasce/back, simeth=TO}}' to the MGC. The MGC sends a message to the peer MG. A callout explains 'MGC sends appropriate commands to establish a packet connection between two MGs. (NOTE – part of the set-up may have been done previously.)'. The Exchange sends '1st digit = 6', 'send next (called party) digit', '2nd digit = 1', and 'send next (called party) digit' to the MG. The MG forwards these through a 'Packet network' to the peer MG. The diagram ends with 'etc., etc.'. + +Sequence diagram showing E2E compelled register signalling between Exchange, MG, MGC, and peer MG. The diagram includes messages like seizing, seize ack, 1st digit = 6, send next (called party) digit, 2nd digit = 1, and various MGC/ MG commands. Callouts explain the logic, such as 'MGC decides to go E2E based on di=61' and 'When the current forward signal is stopped, the MG notifies signal completion.' + +H.248.29(13)\_FA.5 + +NOTE – ITU-T H.248 responses are not shown for clarity. + +**Figure A.5 – Example where MGC decides to use end-to-end signalling** + +If the TDM-termination is E2E capable, then the MGC sends an initial request for called party number with a preliminary digitmap to collect the first relevant part of the address. The initial request consists of an icasce/addr (or icasco/addr) command using di within the seq parameter. The cskt property is set to a suitable non-zero value. This forces the MG to wait in a pending state for the next MGC message with cskt active. An example Events descriptor is: Events {icasce/addr {seq="di{xxx}"}} OR Events {icasce/addr {seq="di(dm1)"}, DigitMap=dm1 {xxx}}. + +If the MGC decides not to use E2E signalling, the MGC sends a new icasce/addr event (either *en bloc* or overlap) to reactivate the compelled register signalling. Note that unlike the icasce/addr or icasco/addr events, the icasce/addr event may be received when the previous addr event is active and cskt is active. Since cskt is active, the MG sends an appropriate backward compelled register response as the next listed seq parameter information element to continue the compelled cycle. + +If the MGC decides to use E2E signalling, the MGC sends an icasce/back signal, with its parameter set to the appropriate backward register compelled signal (1st digit, last but 1, etc.). The MGC may also request signal completion (Timeout) and the g/sc event. Upon receipt of the MGC request, the MG will exit the pending state and send the requested backward register compelled signal. When the current forward register compelled digit stops, the MG notifies that the icasce/back signal is complete. The MGC may then request a connection between the MG and a peer-MG so that the two MGs can pass-through compelled register signalling without MGC interaction. + +NOTE – The actual connection may be established earlier to minimize delay; however, the termination Mode property would be set to inactive. Therefore, this step may simply set the Mode property to SendReceive. + +# Annex B + +## Generic CAS compelled register signalling package + +(This annex forms an integral part of this Recommendation.) + +The icascgen package covers register signalling only. Any termination supporting the icascgen package must also support the icas package [ITU-T H.248.28] or another package covering the corresponding line signalling part of the underlying CAS system (for instance, SSR2). + +![Diagram illustrating the scope of the icascgen package. A dashed box labeled 'Signalling System R2' contains a 'Switching system' on the left and a 'Media Gateway Controller (MGC)' on the right. The 'Switching system' contains a 'Register signalling' block. The 'MGC' contains a 'Gateway control protocol ITU-T H.248.1' block. A solid line labeled 'analog or digital transmission' connects the 'Register signalling' block to a 'Media Gateway (MG)' on the right. The 'MG' also contains a 'Gateway control protocol ITU-T H.248.1' block. A dashed line connects the 'MGC' to the 'MG'. An arrow points from the 'MG' to a box labeled 'ITU-T H.248.29 Annex B icascgen Generic CAS register signalling package'.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +The diagram shows a 'Signalling System R2' (dashed box) containing a 'Switching system' and a 'Media Gateway Controller (MGC)'. The 'Switching system' has a 'Register signalling' block. The 'MGC' has a 'Gateway control protocol ITU-T H.248.1' block. A solid line labeled 'analog or digital transmission' connects the 'Register signalling' block to a 'Media Gateway (MG)' on the right. The 'MG' also has a 'Gateway control protocol ITU-T H.248.1' block. A dashed line connects the 'MGC' to the 'MG'. An arrow points from the 'MG' to a box labeled 'ITU-T H.248.29 Annex B icascgen Generic CAS register signalling package'. The text 'H.248.29(13)\_FB.1' is at the bottom right. + +Diagram illustrating the scope of the icascgen package. A dashed box labeled 'Signalling System R2' contains a 'Switching system' on the left and a 'Media Gateway Controller (MGC)' on the right. The 'Switching system' contains a 'Register signalling' block. The 'MGC' contains a 'Gateway control protocol ITU-T H.248.1' block. A solid line labeled 'analog or digital transmission' connects the 'Register signalling' block to a 'Media Gateway (MG)' on the right. The 'MG' also contains a 'Gateway control protocol ITU-T H.248.1' block. A dashed line connects the 'MGC' to the 'MG'. An arrow points from the 'MG' to a box labeled 'ITU-T H.248.29 Annex B icascgen Generic CAS register signalling package'. + +Figure B.1 – Scope of "icascgen" + +Package icascgen comprises the two compelled address transfer modes of generic standard *en bloc* compelling and overlap procedures. Both modes are applied between two peer register nodes. This scope is outlined in Figure B.1. The ITU-T H.248.29 capable H.248 MG has an embedded "register" function and is peering a "register signalling" operated switching system. + +The third compelled address transfer mode of end-to-end compelled signalling has a more extended view. This specific mode is out of scope of the icascgen package. + +### B.1 Generic CAS Compelled Register Signalling Package + +| | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | Generic CAS Compelled Register Signalling Package | +| Package ID: | icascgen (0x0094) | +| Description: |

This package defines ITU-T H.248 methods to support a generic channel associated signalling (CAS) compelled standard register signalling. The term "standard" refers to standardized CAS systems and means "address transfer modes" like en bloc transfer or overlap signalling.

Version 2 of the package introduces a new parameter to indicate whether the Generic Digit information Event is generated in the event of an unsuccessful events map match.

| +| Version: | 2 | +| Extends: | None | + +#### B.1.1 Properties + +##### B.1.1.1 Detection Open Numbering Length + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Detection Open Numbering Length | +| Property ID: | donl (0x0001) | +| Description: |

Indicates that the digits are to be collected by the MG up to a maximum length as specified by this parameter value. Value "0" indicates no defined maximum length. For concatenated SSR2 Events and SSR2 Signals Map, this applies to the open numbering parts only ("."). Exceeding this threshold causes an error reported via the failure event defined by icascgenf. It must be set high enough, so that this maximum is never reached in normal circumstances.

NOTE – This property is used to protect the "x." parts of SSR2 Events Maps against endless number collection.

| +| Type: | Integer | +| Possible values: | Non-negative number of digits | +| Default: | Provisioned | +| Defined In: | TerminationState | +| Characteristics: | Read/Write | + +##### B.1.1.2 Compelling Mode + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Compelling Mode | +| Property ID: | cmode (0x0002) | +| Description: |

Specifies the register signalling mode used. The operation mode could be fully-compelled as specified in [ITU-T Q.441] and [ITU-T Q.442], or as semi- or non-compelled as specified in [ITU-T Q-Sup.7].

| +| Type: | Enumeration | +| Possible values: | "CO" (0x0001) Fully-Compelled
"SC" (0x0002) Semi-Compelled
"NC" (0x0003) Non-Compelled | +| Default: | Provisioned | +| Defined In: | TerminationState | +| Characteristics: | Read | + +##### B.1.1.3 Register Signalling Direction + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Register Signalling Direction | +| Property ID: | rsdir (0x0003) | +| Description: |

Specifies whether the termination is used as an incoming or outgoing register signalling interface in case the line signalling is configured as bothway. This can be changed on a call by call basis for this termination. It must not be changed during a register signalling session.

| +| Type: | Enumeration | + +**Possible values:** "IC" (0x0001) Incoming +"OG" (0x0002) Outgoing + +**Default:** Provisioned + +**Defined In:** TerminationState + +**Characteristics:** Read/Write + +##### **B.1.1.4 Incoming Non-Recognition Time** + +**Property name:** Incoming Non-Recognition Time + +**Property ID:** inrt (0x0004) + +**Description:** Determines the time during which the MG does not recognize SSR2 register signals in the pulsed backward signal case [ITU-T Q.442]. After timeout, a normal compelled cycle treatment is done. + +**Type:** Integer + +**Possible values:** Positive number of milliseconds + +**Default:** 300 + +**Defined In:** TerminationState + +**Characteristics:** Read/Write + +##### **B.1.1.5 Incoming Keep Alive Timer** + +**Property name:** Incoming Keep Alive Timer + +**Property ID:** ikat (0x0005) + +**Description:** Determines the timeout for compelled keep alive (see Figure B.2). It is used as the maximum timeout value for signals sent from the incoming SSR2 interface. + +**Type:** Integer + +**Possible values:** Positive number of milliseconds + +**Default:** 300 + +**Defined In:** TerminationState + +**Characteristics:** Read/Write + +##### **B.1.1.6 Outgoing Keep Alive Timer** + +**Property name:** Outgoing Keep Alive Timer + +**Property ID:** okat (0x0006) + +**Description:** Determines the timeout for compelled keep alive. It is used as the maximum timeout value while waiting for an acknowledge event (see Figure I.1). + +**Type:** Integer + +**Possible values:** Positive number of milliseconds + +**Default:** 300 + +**Defined In:** TerminationState + +**Characteristics:** Read/Write + +##### B.1.1.7 Outgoing End of Compelled Cycle Timer + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------| +| Property name: | Outgoing End of Compelled Cycle Timer | +| Property ID: | oect (0x0007) | +| Description: | Determines the timeout for outgoing register signalling awaiting the end of a backward SSR2 signal (see Figure B.2). | +| Type: | Integer | +| Possible values: | Positive number of milliseconds | +| Default: | 80 | +| Defined In: | TerminationState | +| Characteristics: | Read/Write | + +#### B.1.2 Events + +##### B.1.2.1 Multifrequency Combination Event + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | Multifrequency Combination Event | +| Event ID: | mc1 (0x0001) | +| Description: | Detects and reports the multifrequency combination (MC) signal codepoint 1. The characteristics of the MF signal code, including frequencies and durations, are provisioned on the MG. | + +###### B.1.2.1.1 EventsDescriptor parameters + +None. + +###### B.1.2.1.2 ObservedEventsDescriptor parameters + +None. + +###### B.1.2.1.3 Additional values + +The events for the other MC code events are specified in exactly the same way. Table B.1 shows all event names, Event IDs and SSR2 Events Map symbols. The event identifiers are defined with the same names as the SSR2 signalling codepoints in [ITU-T Q.442]. + +**Table B.1 – Event IDs (for SSR2)** + +| Combination number as specified in [ITU-T Q.441] | Event ID | SSR2 events map string ID | Remark | +|--------------------------------------------------|---------------|---------------------------|--------| +| 1 | mc1 (0x0001) | "1" | | +| 2 | mc2 (0x0002) | "2" | | +| 3 | mc3 (0x0003) | "3" | | +| 4 | mc4 (0x0004) | "4" | | +| 5 | mc5 (0x0005) | "5" | | +| 6 | mc6 (0x0006) | "6" | | +| 7 | mc7 (0x0007) | "7" | | +| 8 | mc8 (0x0008) | "8" | | +| 9 | mc9 (0x0009) | "9" | | +| 10 | mc10 (0x000a) | "0" | | + +**Table B.1 – Event IDs (for SSR2)** + +| Combination number as specified in [ITU-T Q.441] | Event ID | SSR2 events map string ID | Remark | +|--------------------------------------------------|---------------|---------------------------|-----------------------| +| | | "A" or "a" | Reserved | +| 11 | mc11 (0x000b) | "B" or "b" | | +| 12 | mc12 (0x000c) | "C" or "c" | | +| 13 | mc13 (0x000d) | "D" or "d" | | +| 14 | mc14 (0x000e) | "E" or "e" | | +| 15 | mc15 (0x000f) | "F" or "f" | "End of Digit" symbol | +| | | "G" or "g" | Reserved | +| | | ... | ... | +| | | "K" or "k" | Reserved | + +##### B.1.2.2 Generic Digit Information + +**Event name:** Generic Digit Information + +**Event ID:** gdi (0x0010) + +**Description:** Generic Digit Information reports the detected MF tones collected through compelled register signalling. The gdi event supports *en bloc* and overlap compelled register signalling. + +###### B.1.2.2.1 EventsDescriptor parameters + +###### B.1.2.2.1.1 Detection Events Map + +**Parameter name:** Detection Events Map + +**Parameter ID:** dem (0x0001) + +**Description:** Detection Events Map parameter is activated for collection of register signals. When a Detection Events Map is missing, the received events are reported event by event. + +**Type:** String + +**Optional:** Yes + +**Possible values:** A detected sequence of the characters '0' through '9' and 'B-F', 'x', '.' and the interdigit threshold timers 'T', 'S' and 'L'. In addition, it can also contain '<' and '>' indicating the used backward acknowledge signal. ABNF Syntax is specified in clause B.2.2. + +NOTE 1 – The SSR2 Events Map is a specific Detection Events Map for Signalling System R2 codepoints. + +NOTE 2 – "x" represents any character in the range of "0" through "9". + +**Default:** None + +###### B.1.2.2.1.2 Unsuccessful Match Reporting + +**Parameter name:** Unsuccessful Match Reporting + +**Parameter ID:** umr (0x0002) + +**Description:** The MGC may use this parameter to control whether the Generic Digit Information Event is generated in the event of an unsuccessful events map match (i.e., match with method "Partial match, unmatched event" or "Partial Match, timer expired"). + +**Type:** Boolean + +**Optional:** Yes + +**Possible values:** +*On:* Generate a Generic Digit Information Event on unsuccessful match. +*Off:* Do not generate a Generic Digit Information Event on an unsuccessful match. + +**Default:** *On* + +###### **B.1.2.2.2 ObservedEventsDescriptor parameters** + +###### **B.1.2.2.2.1 Detection Event String** + +**Parameter name:** Detection Event String + +**Parameter ID:** des (0x0002) + +**Description:** Detection Event String is the collected events string, which matches part or all of an alternative event sequence specified in the Detection Events map. The ABNF Syntax for an SSR2 Event String is specified in clause B.2.3. + +**Type:** String + +**Optional:** No + +**Possible values:** +A detected sequence of the characters '0' through '9' and 'B-F'. In addition, it may also contain '<' and '>' indicating the used backward acknowledge signal deviating from the default backward signal MC1. +NOTE – The SSR2 Event String is a specific Detection Event String for Signalling System R2 codepoints. + +**Default:** None + +###### **B.1.2.2.2.2 Number Termination Method** + +**Parameter name:** Number Termination Method + +**Parameter ID:** meth (0x0003) + +**Description:** Indicates the reason for the generation of the Detection Event String parameter. When a Detection Events Map is present in the EventsDescriptor, this is a mandatory ObservedEventsDescriptor parameter. When a Detection Events Map is absent from the EventsDescriptor, this parameter is also absent. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** + +| | | | +|-------|----------|--------------------------------| +| "UM" | (0x0001) | Unambiguous Match | +| "PM" | (0x0002) | Partial Match, unmatched event | +| "FM" | (0x0003) | Full Match, unmatched event | +| "PMT" | (0x0004) | Partial Match, timer expired | +| "FMT" | (0x0005) | Full Match, timer expired | + +**Default:** None + +##### B.1.2.3 Signal Completion + +**Event name:** Signal Completion + +NOTE – The term "signal" in the context of this clause means for instance an "SSR2 Signal", which correlates here with "ITU-T H.248 Event". + +**Event ID:** sc (0x0011) + +**Description:** Indicates the termination of a signal for which the notifyCompletion parameter was set to enable reporting of a completion event. For further procedural description, see clauses 7.1.1, 7.1.17 and 7.2.7 of [ITU-T H.248.1]. + +###### B.1.2.3.1 EventsDescriptor parameters + +###### B.1.2.3.1.1 Signalling Completion Reference + +**Parameter name:** Signalling Completion Reference + +**Parameter ID:** scref (0x0001) + +**Description:** The Reference String generated by the MGC, which will be copied by the MG to the ObservedEvents Descriptor for reference. + +**Type:** String + +**Optional:** Yes + +**Possible values:** Any string value + +**Default:** None + +###### B.1.2.3.2 ObservedEvents Descriptor parameters + +###### B.1.2.3.2.1 Generated Signal String + +**Parameter name:** Generated Signal String + +**Parameter ID:** gss (0x0002) + +**Description:** This parameter identifies the signal which has been sent. For a signal that is contained in a Generation Signals Map, the delivered signals are indicated in form of a list. + +**Type:** String + +**Optional:** No + +**Possible values:** A signal which has terminated. A signal shall be identified using the pkgdName syntax without wildcarding. In case a Generation Signals Map is used, the gss parameter contains the Generation Signals Map from beginning until the last sent out signal. ABNF Syntax for an SSR2 Signals Map is specified in clause B.2.1 without using the alternatives. + +**Default:** None + +###### B.1.2.3.2.2 Termination Method + +**Parameter name:** Termination Method + +**Parameter ID:** Meth (0x0003) + +**Description:** Indicates the means by which the signal terminated. + +| | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type: | Enumeration | +| Optional: | No | +| Possible values: | "NT" (0x0001) Normal termination, completed on its own
"EV" (0x0002) Interrupted by event (unexpected backward signal)
"SD" (0x0003) Halted by new Signals Descriptor
"NC" (0x0004) Not completed, other cause | +| Default: | None | + +###### B.1.2.3.2.3 Signalling Completion Reference + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Signalling Completion Reference | +| Parameter ID: | scref (0x0004) | +| Description: | The Reference String sent by the MGC in the Events Descriptor, which is copied by the MG to this parameter for reference. | +| Type: | String | +| Optional: | No | +| Possible values: | The string contained in the original request. In case scref is not specified in the Events Descriptor, the scref is generated from gsm as specified in the original request. | +| Syntax: | scref=" gsm-value "; e.g., gsm="123<6>7777" is referenced as scref="123<6>7777" | +| Default: | None | + +##### B.1.2.4 CAS Failure + +| | | +|---------------------|-----------------------------------------------------------------------------------------------------| +| Event name: | CAS Failure | +| Event ID: | icascgenf (0x0012) | +| Description: | This event handles failure or abnormal register signalling conditions associated with this package. | + +###### B.1.2.4.1 EventsDescriptor parameters + +None. + +###### B.1.2.4.2 ObservedEventsDescriptor parameters + +###### B.1.2.4.2.1 Error Code + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Error Code | +| Parameter ID: | ec (0x0001) | +| Description: | Indicates the error that occurred. | +| Type: | Enumeration | +| Optional: | No | +| Possible values: | "ERR" (0x0001) Error in compelling sequence with peer signalling entity.
"NOL" (0x0002) Number overlenth (donl exceeded).
"TO" (0x0003) Compelled time out condition due to expiry of one of the timers ikat, okat, or oect. | + +**Default:** None + +#### B.1.3 Signals + +##### B.1.3.1 Multifrequency Combination 1 + +**Signal name:** Multifrequency Combination 1 + +**Signal ID:** mc1 (0x0001) + +**Description:** It generates multifrequency combination (MC) signal code 1. The characteristics of the MF signal code, including frequencies and durations, are provisioned on the MG. The duration time must be set much higher than the longest maximum timers (ikat, okat, oect) to guarantee compelled cycles. + +The other MC signal codes are specified in exactly the same way. Table B.2 below indicates all signal IDs. + +**Signal type:** Brief + +**Duration:** Provisioned + +**Table B.2 – Signal IDs** + +| | Combination number as specified in [ITU-T Q.441] | Signal ID/tone ID | SSR2 Signals Map string IDs | +|--|--------------------------------------------------|-------------------|-----------------------------| +| | 1 | mc1 (0x0001) | "1" | +| | 2 | mc2 (0x0002) | "2" | +| | 3 | mc3 (0x0003) | "3" | +| | 4 | mc4 (0x0004) | "4" | +| | 5 | mc5 (0x0005) | "5" | +| | 6 | mc6 (0x0006) | "6" | +| | 7 | mc7 (0x0007) | "7" | +| | 8 | mc8 (0x0008) | "8" | +| | 9 | mc9 (0x0009) | "9" | +| | 10 | mc10 (0x000a) | "0" | +| | 11 | mc11 (0x000b) | "B" or "b" | +| | 12 | mc12 (0x000c) | "C" or "c" | +| | 13 | mc13 (0x000d) | "D" or "d" | +| | 14 | mc14 (0x000e) | "E" or "e" | +| | 15 | mc15 (0x000f) | "F" or "f" | + +###### B.1.3.1.1 Additional parameters + +###### B.1.3.1.1.1 Exceptional SSR2 treatment + +**Parameter name:** Exceptional SSR2 Treatment + +**Parameter ID:** er2t (0x0001) + +**Description:** Used to alter the normal compelling mode behaviour for special compelling modes. Absence of this parameter indicates that normal compelling behaviour is used. + +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "PwP" (0x0001) Pulsed backward signal with pause. +**Default:** Empty (no special treatment) + +##### B.1.3.2 Generic Digit Information + +**Signal name:** Generic Digit Information +**Signal ID:** gdi (0x0010) +**Description:** Generic Digit Information is a composite signal that supplies all the necessary signals to start the compelling register signalling at the outgoing MG. +**Signal type:** Brief +**Duration:** Depends on parameters supplied + +###### B.1.3.2.1 Additional parameters + +###### B.1.3.2.1.1 Generation Signals Map + +**Parameter name:** Generation Signals Map +**Parameter ID:** gsm (0x0001) +**Description:** The generic signal to be sent. +**Type:** String +**Optional:** No +**Possible values:** A sequence of the characters "0" through "9", "B" through "F" as a quoted string. In addition it can also contain '<' and '>' indicating the expected backward signal. The ABNF syntax for an SSR2 Signals Map is specified in clause B.2.1. +NOTE – The SSR2 Signals Map is a specific Generation Signals Map for Signalling System R2 codepoints. +**Default:** None + +#### B.1.4 Statistics + +None. + +#### B.1.5 Procedures + +The following clauses are specific to Signalling System R2. + +##### B.1.5.1 Relation with Signalling System R2 + +For an outgoing SSR2 link on a MG, the MGC provides the MG with the signal information to be sent to the peer SSR2 node. For an incoming SSR2 link, the MGC provides the MG with the information that the MGC requests from the previous remote SSR2 peer node. + +Termination of the address signal or cancellation of the address event (e.g., by sending Events Descriptor and/or Signals Descriptor without icascgen/gdi, or through detection of another line signalling event) shall cause register signals to be immediately removed and may be notified to MGC. + +##### **B.1.5.2 General procedures** + +The MG can be connected to a peer compelled CAS switching system, a peer MG for media transport, and a MGC for exchanging signalling information using ITU-T H.248 with this package. + +This package uses the following convention for incoming/outgoing MG: + +- Incoming MG: the peer SSR2 exchange initiates the call signalling towards the MG. +- Outgoing MG: the MG initiates the call signalling towards the peer SSR2 exchange. + +In general, the incoming/outgoing MG SSR2 interface can treat each event/signal separately by using a normal Events or Signals Descriptor. (For instance, refer to Figure B.2 for one cycle.) + +###### **B.1.5.2.1 Signal and Event Maps** + +The Generation Signals Map or Detection Events Map shall be applied whenever possible. + +The incoming MG shall detect the end of generic register events based upon a MGC supplied Detection Events Map. This also takes care of situations where identification of the end of Detection Events Map is achieved through length determination or timeout mechanisms. The Detection Events Maps shall be processed until the maximum length of the generic number is achieved, the "end-of-digit" is encountered or a timeout occurs. The maximum length is provisioned in the MG, and may be altered by the MGC via parameter donl (Detection Open Numbering Length). + +The outgoing MG is instructed with a MGC-supplied Generation Signals Map to start or continue with the next section of compelled cycles. + +###### **B.1.5.2.2 Relation with other CAS packages** + +The relation of icascgen to other CAS packages is illustrated in Appendix II. + +##### **B.1.5.3 Handling of events** + +For register signalling, events may be specified on an event by event basis. But this is not the recommended approach, since it will be difficult to meet timing and congestion restrictions (see [ITU-T Q.457] and [ITU-T Q.458]). Therefore, the use of a map-based approach is recommended. The register signalling interface is principally used in the following manner: + +- event by event; or +- consecutive events by using Detection Events Maps (section by section); or +- consecutive events by using Detection Events Maps with alternatives (for a complete sequence). + +###### **B.1.5.3.1 SSR2 events map syntax** + +The Detection Events Map (dem) parameter contained in the EventsDescriptor uses the events IDs as specified in Table B.1. Timer symbols T, S and L may be used as well. Timer T is used to specify the maximum time the MG may wait for a first register signal after the bearer connection has been seized. + +Additionally, for each SSR2 multifrequency combination (MC) in this map, the MGC may instruct the MG to use another SSR2 backward signal enclosed with "<>". + +NOTE – Using "<>" should allow the use of existing H.248 protocol parsers without any modification. + +Example: dem="123<3>" + +MC1 is used as the default backward signal until specified otherwise within the SSR2 Events Map. In order to use an alternative SSR2 backward signal from the beginning of the Events Map, it is permitted to begin an SSR2 Events Map with an "<>" enclosed backward signal codepoint. + +Symbols '<' and '>' are used in the ObservedEventsDescriptor to separate consecutive register information which is used by the MGC to recognize used alternatives. + +###### *Example 1: Detection Events Map usage* + +MGC request: + +Events = {icascg/gdi{ dem="xx<6>[1-2]<1>x.F<3>[12568]" } } + +After two digits, the MG sends a backward signal '6' requesting, e.g., a Calling Party Category (see [ITU-T Q.400]) followed by Calling Party Number, etc. The collected MCs are reported to the MGC by using the different backwards signals as separators. + +MG response: + +Observed Events = {icascg/gdi{des="77<6>2<1>555555F<3>8"}} to the MGC. + +###### *Example 2:* + +MGC request: + +Events = {icascg/gdi{dem="xx<6>[1-2]<1>x.<3>[12568]" } } + +MG response: + +The Notify sends the following information to MGC: + +Observed Events = {icascg/gdi{des="77<6>2<1>77777<3>8"}} to the MGC. + +###### **B.1.5.3.2 General handling of incoming register signalling** + +The Detection Events Map of this package is used exclusively for the incoming register signalling case. + +###### **B.1.5.3.3 General handling of outgoing register signalling** + +The Signal Descriptor covers all events within a sequence of a Generation Signals Map. All remaining events described in Events Descriptor not covered by the Signal Descriptor are included in the Events Descriptor. + +##### **B.1.5.4 Handling of signals** + +Register signalling signals can be specified on a signal by signal basis. But this is not recommended, since it will be difficult to meet the timing and congestion restrictions (see [ITU-T Q.457] and [ITU-T Q.458]). Therefore the use of SSR2 Signals Maps is recommended. The register signalling interface is used in following manner: + +- signal by signal; or +- concatenated signals by using SSR2 Signals Maps (section by section); or +- concatenated signals by using SSR2 Signals Maps with alternatives (for a complete sequence). + +###### **B.1.5.4.1 SSR2 signals map syntax** + +The gsm parameter contained in the Signals Descriptor uses the signal IDs specified in Table B.2 formatted as a String. If not otherwise specified, the MG sends the specified signals in the compelled sequence awaiting the default backward signal MC1. + +The expected backward signal can be changed within an SSR2 Signals Map by specifying a new expected backward acknowledge signal enclosed with symbols "< >", which is valid for the remaining SSR2 Signals Map or next compelling sequence. + +NOTE – Using "< >" should allow the use of existing ITU-T H.248 protocol parsers without any modification. + +*Example 1:* + +MGC request: + +Signals{icascgen/gdi{gsm="77<6>2<1>555555F<3>8"}}} + +SSR2 Signals Maps alternatives can also be used, similar to SSR2 Events Maps. + +*Example 2:* + +MGC request: + +Signals{icascgen/gdi{gsm="12(<1>34567 | <6>2<1>555555F<3>34567 )"}}} + +With the SSR2 Signals Map, it is possible to specify a complete outgoing signal sequence without any notification to the MGC. Alternative branches within the Generation Signals Map are selected based on the received backward signals (<1> or <6> in this example). + +###### **B.1.5.4.2 General handling of incoming register signalling** + +The signals for a compelled incoming register signalling sequence are processed by the Events Descriptor. The Signals Descriptor is used only: + +- In the signal by signal case to send the next backward SSR2 signal. +- In other cases to send the next backwards SSR2 signal and continue further treatment of the next compelling sequence with information contained in Detection Events Map (dem). + +Incoming compelled register signalling is triggered by the MGC by sending an Events Descriptor with the icasgen/gdi event. The MG autonomously takes control of the compelling sequence as long as the peer responses are covered by the specified SSR2 Events Map and collects all the information, sending a single Notify message when it has been completed. + +The compelling action starts by the peer signalling entity by sending a forward signal. In this package, the MG does not know whether it is a Called Party Number or the Country Code Indicator. The meaning of the Detection Events Map is only known by the MGC. + +The incoming MG shall collect generic events using the Detection Events Map specified by the MGC and the "End of Digit" register signal as specified by a SSR2 Events Map. In the absence of an SSR2 Detection Events Map, the events are notified on an event by event basis to the MGC. + +During a generic number compelling sequence, when the MG determines that an unambiguous match has been found with an alternative in the SSR2 Events map, the MG shall report the collected events with the Generic Number Termination Method set to "Unambiguous Match". This matching criterion may coincide with the reception of the "End of Digit" signal. + +Digit collection may terminate due to a timer expiry or the reception of "End of Digit" signal when an alternative in the SSR2 Events Map has partially matched. In this instance, the MG shall report the collected SSR2 events with the Destination Number Termination Method set to "Partial Match". Similarly, SSR2 events collection may terminate due to a timer expiry or the reception of "End of Digit" signal after one of the alternative in the SSR2 Events Map has fully matched, the MG shall report all the collected SSR2 events with the "Method" codepoint set to "Full Match". + +The MG shall collect a string of MCs until any of the following events occur: + +- The reception of the "End-of-Digit" signal, if specified in an SSR2 Events Map. The MG shall report the complete string with the "End of Digit" representation ("F") included. Other "End of Digit" symbols may also be possible in non-SSR2 signalling systems. + +- The collection of more than the maximum number of digits (for instance for the called party number), as specified by the *donl* parameter. The MG shall report the "NOL" CAS Failure event. +- A digit timeout occurs, in accordance with a value provisioned at the MG. The timer is started the moment generic number compelling starts. The T, S and L timers will be used. The MG shall report all the Detection Events String with the method set to "PMT" or "FMT". + +Normally, the last received digit is never answered by a backward signal unless the MG is instructed by the MGC via an embedded Signals Descriptor to do so. + +The MGC is responsible to instruct the MG in an adequate manner, either via another Modify or via an embedded Signals or Events Descriptor, on how to proceed with the compelled cycle. + +Some SSR2 interfaces require maximum time allowed between the seizure of a line and the first register signal. In this case especially, the 'T' timer can be used on incoming side. + +###### **B.1.5.4.3 General handling of outgoing register signalling** + +SSR2 Signals Map of this package is used exclusively for the outgoing register signalling case. + +An outgoing compelled register signalling sequence is started with sending the first MC to the remote peer system. The MG does not know the meaning of the sent Generic Digit Information, the interpretation is only known to the MGC. + +Normally the compelling action starts after receiving a signal or a SSR2 Signals Map from MGC. In case a previous compelled cycle is not finished yet (i.e., timer *oect* is still running), the signals respectively the SSR2 Signals Map processing, shall be delayed. + +When a single signal is sent, the backward signal is notified according to the Events Descriptor. "Completion" is notified towards the MGC immediately after the SSR2 signal is transmitted. This applies also to the last signal contained in a SSR2 Signals Map. + +When a SSR2 Signals Map is used, the MG continues the next compelled cycle, as long as the received backward signal matches the specified backward signal. If the received backward signal does not match the expected backward signal within a SSR2 Signals Map, and the signal completion event was specified in the Events Descriptor, a signal completion notification is reported to the MGC with list of already sent out SSR2 signals and the received backward signal according to the Events Descriptor. This enables the MGC to resume the remaining SSR2 signals in a later phase. If signal completion is not used, a CAS failure with error code "ERR" is reported to MGC. + +In general the following shall be applied: + +- If SSR2 Signals Map list is not fully sent out and a backward signal is received not matching the currently expected backward SSR2 signal, a signal completion event with Method equal to "EV" is notified to the MGC if signalling completion was specified in the Events Descriptor. Otherwise a CAS failure with error code "ERR" is reported to indicate that the compelled sequence cannot continue. +- When SSR2 Signals Map list is fully sent out, then the normal Events Descriptor handling applies. + +The MGC instructs the MG with the generic MC information to be sent next. + +In case of strong timing requirements between seizing of a line and the first register signal applies, the use of an embedded Signals Descriptor is recommended, when the seizure of the line is requested. + +##### B.1.5.5 Incoming *en bloc* compelled register signalling + +An example of incoming *en bloc* compelled register signalling is given in Figure B.2. + +![Sequence diagram for incoming en bloc compelled register signalling (Figure B.2).](fe25bbee6685ab20f50ffc80c3feddd8_img.jpg) + +Sequence diagram illustrating incoming *en bloc* compelled register signalling. The diagram shows three lifelines: SSR2 exchange, MG, and MGC. The interaction starts with MGC sending an F1: Modify signal to MG. The MG then sends a series of forward signals (F2: I-1, F4: I-2, F6: I-3) to the SSR2 exchange, and backward signals (F3: A-1, F5: A-1) back to the MGC. Finally, the MG sends an F7: Notify signal to the MGC, which includes the observed event {icascgen/gdi {des="123"}}. + +``` +sequenceDiagram + participant MGC + participant MG + participant SSR2 exchange + Note right of MGC: H.248.29(13)_FB.2 + MGC->>MG: F1: Modify +Events {icas/cf,icascgenf, +icascgen/gdi {dem="xxx"}} + MG->>SSR2 exchange: F2: I-1 + SSR2 exchange-->>MGC: F3: A-1 + MG->>SSR2 exchange: F4: I-2 + SSR2 exchange-->>MGC: F5: A-1 + MG->>SSR2 exchange: F6: I-3 + MG->>MGC: F7: Notify +ObservedEvents {icascgen/gdi {des="123"}} + Note left of MG: NOTE 1 – Transaction replies are not shown for clarity. +NOTE 2 – SSR2 interregister signalling codepoints shown are Group I Forward Signals defined in Table 6 of [ITU-T Q.441], +and Group A Backward Signals defined in Table 8 of [ITU-T Q.441]. +``` + +Sequence diagram for incoming en bloc compelled register signalling (Figure B.2). + +NOTE 1 – Transaction replies are not shown for clarity. + +NOTE 2 – SSR2 interregister signalling codepoints shown are Group I Forward Signals defined in Table 6 of [ITU-T Q.441], and Group A Backward Signals defined in Table 8 of [ITU-T Q.441]. + +**Figure B.2 – Incoming generic *en bloc* compelled register signalling example** + +##### B.1.5.6 Outgoing *en bloc* compelled register signalling + +An example of outgoing *en bloc* compelled register signalling is given in Figure B.3. + +![Sequence diagram for outgoing en bloc compelled register signalling (Figure B.3).](78e846f2858d131dc5a4dcbabcca1e4d_img.jpg) + +Sequence diagram illustrating outgoing *en bloc* compelled register signalling. The diagram shows three lifelines: MGC, MG, and SSR2 exchange. The interaction starts with MGC sending an F1: Modify signal to MG. The MG then sends a series of forward signals (F2: I-1, F4: I-2, F6: I-3, F8: I-4) to the SSR2 exchange, and backward signals (F3: A-1, F5: A-1, F7: A-1, F9: A-6) back to the MGC. Finally, the MG sends an F10: Notify signal to the MGC, which includes the observed event {icascgen/gdi {des="6"}}. + +``` +sequenceDiagram + participant MGC + participant MG + participant SSR2 exchange + Note right of SSR2 exchange: H.248.29(13)_FB.3 + MGC->>MG: F1: Modify +Signal { icascgen/gdi {gsm="1234"} } +Events {icasf, icascgenf,icascgen/gdi} + MG->>SSR2 exchange: F2: I-1 + SSR2 exchange-->>MGC: F3: A-1 + MG->>SSR2 exchange: F4: I-2 + SSR2 exchange-->>MGC: F5: A-1 + MG->>SSR2 exchange: F6: I-3 + SSR2 exchange-->>MGC: F7: A-1 + MG->>SSR2 exchange: F8: I-4 + SSR2 exchange-->>MGC: F9: A-6 + MG->>MGC: F10: Notify +ObservedEvents { +icascgen/gdi {des="6"}} } +``` + +Sequence diagram for outgoing en bloc compelled register signalling (Figure B.3). + +NOTE – SSR2 interregister signalling codepoints shown are Group I Forward Signals defined in Table 6 of [ITU-T Q.441], and Group A Backward Signals defined in Table 8 of [ITU-T Q.441]. + +**Figure B.3 – Outgoing generic *en bloc* compelled register signalling (one section)** + +#### B.1.6 Support for overlap signalling + +##### B.1.6.1 Incoming + +Figure B.4 shows an example of an incoming overlap sequence. + +![Sequence diagram showing incoming overlap signalling between SSR2 Exchange, MG, and MGC.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +The diagram illustrates the interaction between three entities: SSR2 Exchange, MG, and MGC. The sequence of messages is as follows: + +- The MG sends an **F1: Modify** message to the MGC. The message includes **Events { icas/cf, icascgen/gdi { dem="xxx" } }** and a note: **MGC requests number of digits needed for 1st stage routing**. +- The MG sends an **F2: I-1** message to the SSR2 Exchange. +- The SSR2 Exchange responds with **F3: A-1**. +- The MG sends an **F4: I-2** message to the SSR2 Exchange. +- The SSR2 Exchange responds with **F5: A-1**. +- The MG sends an **F6: I-3** message to the SSR2 Exchange. +- The MG sends an **F7: Notify** message to the MGC. The message includes **ObservedEvents { icascgen/gdi { des="123" } }**. +- The MG sends an **F8: Modify** message to the MGC. The message includes **Signal icascgen/gdi { gsm="1" }** and **Events { icas/cf, icascgen/gdi { dem="x.F" } }**. +- The SSR2 Exchange sends **F9: A-1** to the MG. +- The MG sends **F10: I-4** to the SSR2 Exchange. +- The SSR2 Exchange responds with **F11: A-1**. +- The MG sends **F12: I-5** to the SSR2 Exchange. +- The SSR2 Exchange responds with **F13: A-1**. +- A break in the sequence is indicated by **....** +- The MG sends **F14: I-F** to the SSR2 Exchange. +- The MG sends an **F15: Notify** message to the MGC. The message includes **ObservedEvents { icascgen/gdi { des="45.F" } }**. + +H.248.29(13)\_FB.4 + +Sequence diagram showing incoming overlap signalling between SSR2 Exchange, MG, and MGC. + +NOTE – SSR2 interregister signalling codepoints shown are Group I Forward Signals defined in Table 6 of [ITU-T Q.441], and Group A Backward Signals defined in Table 8 of [ITU-T Q.441]. + +**Figure B.4 – Incoming section by section** + +An example of complex incoming overlap compelled register signalling is given in Figure B.5: + +![Sequence diagram showing complex incoming overlap compelled register signalling between SSR2 Exchange, MG, and MGC. The diagram is divided into four phases: initial setup, Group II and C reception, C-1 switch back to CdPN N+1 digit reception, and line status. Messages include F1 (Modify), F2 (Seizing), F3 (Notify), F4 (Modify), F5 (Seizure acknowledge), F6 (I-1), F7 (A-1), F8 (I-2), F9 (Notify), F10 (Modify), F11 (A-6), F12 (II-2 Category Subscriber), F13 (Notify), F14 (Modify), F15 (C-1), F16 (III-9), F17 (C-1), F18 (III-15 end of identification), F19 (Notify), F20 (Modify), F21 (C-1), F22 (I-3), F23 (A-1), F24 (I-F), F25 (Notify), F26 (Modify), F27 (A-3), F28 (II-2), F29 (Notify), F30 (Modify), and F31 (B-1).](fc02903382cebe6fc11e4c0d74b5313f_img.jpg) + +The sequence diagram illustrates the interaction between three entities: **SSR2 Exchange**, **MG**, and **MGC**. + +- Initial Setup:** + - MGC sends **F1: Modify** to MG, containing **Events {bcas/sz, icas/casf}**. + - MG sends **F2: Seizing** (dashed line) to SSR2 Exchange. + - MG sends **F3: Notify** to MGC, containing **ObservedEvents {bcas/sz}**. + - MG sends **F4: Modify** to MGC, containing **Signals {bcas/sza}** and **Events {icas/cf, icascgf, icascg/gdi {dem="xx"}}**. + - SSR2 Exchange sends **F5: Seizure acknowledge** (dashed line) to MG. + - MG sends **F6: I-1**, **F7: A-1**, and **F8: I-2** to SSR2 Exchange. + - MG sends **F9: Notify** to MGC, containing **ObservedEvents {icascg/gdi {des="12"}}**. +- send group II and change to group C reception:** + - MG sends **F10: Modify** to MGC, containing **Signals {icascg/gdi {gsm="6"}}** and **Events {icascg/gdi}**. + - SSR2 Exchange sends **F11: A-6** and **F12: II-2 Category Subscriber** to MG. + - MG sends **F13: Notify** to MGC, containing **ObservedEvents {icascg/gdi {des="2"}}**. + - MG sends **F14: Modify** to MGC, containing **Signals {icascg/gdi {gsm="1"}}** and **Events {icascg/gdi {dem="x.F"}}**. + - SSR2 Exchange sends **F15: C-1** and **F16: III-9** to MG. A note indicates: "using implicit R2 Event Map=x.F using symbols range 0,1,...9 and F". + - SSR2 Exchange sends **F17: C-1** and **F18: III-15 (end of identification)** to MG. + - MG sends **F19: Notify** to MGC, containing **ObservedEvents {icascg/gdi {des="9..F"}}**. +- C-1 switches back to CdPN N+1 digit reception group I and group A reception:** + - MG sends **F20: Modify** to MGC, containing **Signals {icascg/gdi {gsm="1"}}** and **Events {icas/casf, icascg/gdi {dem="x.F"}}**. + - SSR2 Exchange sends **F21: C-1**, **F22: I-3**, and **F23: A-1** to MG. + - MG sends **F24: I-F** to SSR2 Exchange. + - MG sends **F25: Notify** to MGC, containing **ObservedEvents {icascg/gdi {des="3..F"}}**. + - MG sends **F26: Modify** to MGC, containing **Signals {icascg/gdi {gsm="3"}}** and **Events {icascg/gdi}**. + - SSR2 Exchange sends **F27: A-3** and **F28: II-2** to MG. + - MG sends **F29: Notify** to MGC, containing **ObservedEvents {icascg/gdi {des="x"}}**. +- line status:** + - MG sends **F30: Modify** to MGC, containing **Signals {icascg/gdi {gsm="1"}}**. + - SSR2 Exchange sends **F31: B-1** to MG. + +Sequence diagram showing complex incoming overlap compelled register signalling between SSR2 Exchange, MG, and MGC. The diagram is divided into four phases: initial setup, Group II and C reception, C-1 switch back to CdPN N+1 digit reception, and line status. Messages include F1 (Modify), F2 (Seizing), F3 (Notify), F4 (Modify), F5 (Seizure acknowledge), F6 (I-1), F7 (A-1), F8 (I-2), F9 (Notify), F10 (Modify), F11 (A-6), F12 (II-2 Category Subscriber), F13 (Notify), F14 (Modify), F15 (C-1), F16 (III-9), F17 (C-1), F18 (III-15 end of identification), F19 (Notify), F20 (Modify), F21 (C-1), F22 (I-3), F23 (A-1), F24 (I-F), F25 (Notify), F26 (Modify), F27 (A-3), F28 (II-2), F29 (Notify), F30 (Modify), and F31 (B-1). + +NOTE – SSR2 interregister signalling codepoints used here are Group II Forward Signals defined in Table 7 of [ITU-T Q.441], Group III Forward Signals and Group C Backward Signals to show an example of national extensions. The exact definitions of these codepoints are not relevant here. + +H.248.29(13) FB.5 + +**Figure B.5 – Incoming overlap compelled register signalling** + +##### B.1.6.2 Outgoing + +Figure B.6 shows an example of an outgoing overlap sequence. + +![Sequence diagram showing outgoing section by section signalling between MGC, MG, and SSR2 exchange. The sequence starts with F1: Modify from MGC to MG, followed by a series of forward (F2, F4, F6, F10, F12, F14, F16) and backward (F3, F5, F7, F11, F13, F15, F17) signals between MG and SSR2 exchange. Notifications (F8, F18) are sent from MG to MGC.](640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg) + +``` + +sequenceDiagram + participant MGC + participant MG + participant SSR2 exchange + + Note right of MGC: F1: Modify +Signal icascgen/gdi {gsm="123"} +Events {icasf, icascgenf, icascgen/gdi} + MGC->>MG: F1: Modify +Signal icascgen/gdi {gsm="123"} +Events {icasf, icascgenf, icascgen/gdi} + MG->>SSR2 exchange: F2: I-1 + SSR2 exchange-->>MG: F3: A-1 + MG->>SSR2 exchange: F4: I-2 + SSR2 exchange-->>MG: F5: A-1 + MG->>SSR2 exchange: F6: I-3 + SSR2 exchange-->>MG: F7: A-1 + MG-->>MGC: F8: Notify +ObservedEvents {icascgen/gdi{dem="1"}} + Note right of MGC: F9: Modify +Signal icascgen/gdi {gsm="456F"} +Events {icasf, icascgenf, icascgen/gdi} + MGC->>MG: F9: Modify +Signal icascgen/gdi {gsm="456F"} +Events {icasf, icascgenf, icascgen/gdi} + MG->>SSR2 exchange: F10: I-4 + SSR2 exchange-->>MG: F11: A-1 + MG->>SSR2 exchange: F12: I-5 + SSR2 exchange-->>MG: F13: A-1 + MG->>SSR2 exchange: F14: I-6 + SSR2 exchange-->>MG: F15: A-1 + MG->>SSR2 exchange: F16: I-F + SSR2 exchange-->>MG: F17: A-x + MG-->>MGC: F18: Notify +ObservedEvents {icascgen/gdi{des="x"}} + +``` + +H.248.29(13)\_FB.6 + +Sequence diagram showing outgoing section by section signalling between MGC, MG, and SSR2 exchange. The sequence starts with F1: Modify from MGC to MG, followed by a series of forward (F2, F4, F6, F10, F12, F14, F16) and backward (F3, F5, F7, F11, F13, F15, F17) signals between MG and SSR2 exchange. Notifications (F8, F18) are sent from MG to MGC. + +NOTE – SSR2 interregister signalling codepoints shown are Group I Forward Signals defined in Table 6 of [ITU-T Q.441], and Group A Backward Signals defined in Table 8 of [ITU-T Q.441]. + +**Figure B.6 – Outgoing section by section signalling** + +If the outgoing MGC cannot deliver the complete SSR2 Signals Map, it shall use the service completion event mechanism. By using this, the MGC receives a notification, which is used to start the next compelling sequence. + +#### B.1.7 Pulsed backward SSR2 signal without receiving a forward SSR2 signal + +If the previous SSR2 system cannot provide the next SSR2 signal, the incoming SSR2 system updates its last backward signal by sending a new pulsed backward signal. The MGC shall indicate this exceptional case with the "er2t" set to "PwP" in the Signals Descriptor. The MG is responsible for ensuring the minimum inactivity on the SSR2 interface before sending out the requested pulsed backward signal. The MG starts a non-recognition timer when activating the pulsed SSR2 backward signal. While this non-recognition timer is running, all incoming MC signals are ignored. After expiration of this timer, the normal compelled cycle treatment applies. + +This scenario is illustrated in Appendix I. + +#### B.1.8 End-to-end SSR2 register signalling + +For further study. + +NOTE – One question is whether the end-to-end case is needed in a NGN network as it is used only in national segments and these are evolving towards becoming NGN networks in the future. + +### B.2 ABNF encoding + +The syntax for the new introduced map types is presented in ABNF according to [b-IETF RFC 2234]. + +#### B.2.1 SSR2 signals map syntax + +``` +r2sigMapValue = r2signalMap +r2sigMap = 1* (r2sigMapLetter) *(r2sigStrList) +r2sigStrList = r2sigStr / ( "(" r2sigStr *( LWSP "|" LWSP r2sigStr ) ")" ) +r2sigStr = r2sigBackAckPos 1*(r2sigMapLetter) *(r2sigStrList) +r2sigBackAckPos = LWSP "<" r2sigMapLetter ">" LWSP +r2sigMapLetter = DIGIT ;Basic R2 signal symbols + / %x42-46 / %x62-66 ; b-f, B-F +``` + +#### B.2.2 SSR2 events map syntax + +``` +r2eventMapValue = ["T" COLON Timer COMMA] ["S" COLON Timer COMMA] + ["L" COLON Timer COMMA] r2evtMap +r2evtMap = (r2evtStr / + LWSP "(" LWSP r2evtStrList LWSP ")" LWSP) +r2evtStrList = r2evtStr *( LWSP "|" LWSP r2evtStr ) +r2evtStr = 1*( r2eventStrElement) +r2evtStrElement = ((r2evtDigitPos [DOT]) / r2evtBackAckPos) +r2evtBackAckPos = LWSP "<" r2digitMapLetter ">" LWSP +r2evtDigitPos = r2digitMapLetter / r2digitMapRange +r2evtDigitMapRange = ("x" / (LWSP "[" LWSP r2digitLetter LWSP "]" LWSP)) +r2evtDigitLetter = *((DIGIT "-" DIGIT) / r2digitMapLetter) +r2evtDigitMapLetter = DIGIT ;Basic event symbols + / %x42-46 / %x62-66 ; b-f, B-F + / "L" / "S" ;Inter-event timers (long, short) +``` + +#### B.2.3 SSR2 event string syntax + +``` +r2detEvtString = *(r2detEventStringElement) +r2detEvtStringElement = r2detEvtLetter [r2evtBackAckPos] +r2detEvtLetter = DIGIT + / %x42-46 ; b-f + / %x62-66 ; B-F +``` + +; r2evtBackAckPos already defined as part of r2eventMapValue + +# Appendix I + +## Timing aspects + +(This appendix does not form an integral part of this Recommendation.) + +Timing Specifications for Signalling System R2 are detailed in clause 4.5.2 of [ITU-T Q.457]. Figure I.1 shows the relation to the ITU-T H.248 MG timers. + +![Figure I.1: Time sequence of a complete compelled signalling cycle. The diagram shows the interaction between an Outgoing R2 register and an Incoming R2 register. It details the timing of various signals, including multifrequency combinations, notifications to the MGC, and keep-alive timers. A legend defines the timing parameters: T_PF (transmission delay forwards), T_PB (transmission delay backwards), T_0 (operating times), T_R (release times), T_int (internal operation times), and T_S (starting, stopping mc tones). A table provides total time (T) ranges for terrestrial, satellite, and MGs.](c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg) + +Outgoing R2 register + +Incoming R2 register + +Modify { Signal, Event Descriptor } to MG + +Sending of forward multifrequency combination + +Receiving of forward multifrequency combination + +Notify received to MGC + +MG: Outgoing keep-alive timer + +Notify received to MGC + +Outgoing end of cycle keep-alive timer + +Receiving of backward multifrequency combination + +Sending of backward multifrequency combination + +MG: Incoming keep-alive timer timeout triggers icasngenf + +Total time (T) + +- terrestrial: $120 \leq T \leq 200$ ms +- satellite: $1080 \leq T \leq 1440$ ms +- MGs: $160 \leq T \leq 240$ ms (estimated) + +$T_{PF}$ transmission delay forwards + +$T_{PB}$ transmission delay backwards + +$T_0$ operating times (ITU-T Q.451) + +$T_R$ release times (ITU-T Q.451) + +$T_{int}$ internal operation times (ITU-T Q.451) + +$T_S$ starting, stopping mc tones + +T Duration of a compelled signalling cycle + +H.248.29(13)\_Fl.1 + +Figure I.1: Time sequence of a complete compelled signalling cycle. The diagram shows the interaction between an Outgoing R2 register and an Incoming R2 register. It details the timing of various signals, including multifrequency combinations, notifications to the MGC, and keep-alive timers. A legend defines the timing parameters: T\_PF (transmission delay forwards), T\_PB (transmission delay backwards), T\_0 (operating times), T\_R (release times), T\_int (internal operation times), and T\_S (starting, stopping mc tones). A table provides total time (T) ranges for terrestrial, satellite, and MGs. + +**Figure I.1 – Time sequence of a complete compelled signalling cycle (based on [ITU-T Q.457])** + +The following signalling performance recommendation is derived from [ITU-T Q.457]: "The signalling rates would be between approximately 8 and 5 signalling cycles per second for terrestrial circuits". + +![Figure I.2 – Time sequence of a pulsed transmission signal based on [ITU-T Q-Sup.7]. The diagram consists of two parts, (a) and (b), showing signal timing between an Outgoing register and an Incoming register. Part (a) shows a standard pulse transmission of signal A-3. Part (b) shows a pulse transmission of signal A-3 when a delayed forward signal appears, leading to a 'not recognized!!' state in the incoming register.](8a9f4764511ce90622893ec65c065eeb_img.jpg) + +**Part (a): Pulse transmission of signal A-3 (from Figure 14 of ITU-T Q.442)** + +- Outgoing register:** + - Notify sent to MGC (dashed arrow pointing left) + - Group II signal (solid vertical line) + - Modify {Signal, Event Descriptor} to MG (dashed arrow pointing right) +- Incoming register:** + - Last backward signal of a compelled sequence (e.g., A-1) (solid vertical line) + - Time interval $> 100 \text{ ms}$ between last backward signal and Pulse signal A-3 + - Pulse signal A-3 (solid vertical line) + - Time interval $150 \pm 50 \text{ ms}$ for Pulse signal A-3 + - No forward signals can be recognized for $300 \pm 100 \text{ ms}$ ( $900 \pm 180 \text{ ms}$ ) + - Group B signal (solid vertical line) + +**Part (b): Pulse transmission of signal A-3 when delayed forward signal appears (from Figure 15 of ITU-T Q.442)** + +- Outgoing register:** + - Normal compelled cycle (solid vertical line) + - Group II signal (solid vertical line) + - Modify (dashed arrow pointing right) + - Delayed forward signal (dashed arrow pointing right) + - Notify (dashed arrow pointing right) +- Incoming register:** + - Last backward signal of a compelled sequence (e.g., A-1) (solid vertical line) + - Time interval $> 100 \text{ ms}$ between last backward signal and Pulse signal A-3 + - Pulse signal A-3 (solid vertical line) + - Time interval $150 \pm 50 \text{ ms}$ for Pulse signal A-3 + - non-recognition time (dashed arrow pointing right) + - No forward signals can be recognized for $300 \pm 100 \text{ ms}$ ( $900 \pm 180 \text{ ms}$ ) + - Group B signal (solid vertical line) + - Pause min 100 ms (dashed arrow pointing right) + - Modify (dashed arrow pointing right) + - not recognized!! (text box) + +**Legend:** + +- Sending (thick vertical line) +- Receiving (thin vertical line) + +H.248.29(13)\_FI.2 + +Figure I.2 – Time sequence of a pulsed transmission signal based on [ITU-T Q-Sup.7]. The diagram consists of two parts, (a) and (b), showing signal timing between an Outgoing register and an Incoming register. Part (a) shows a standard pulse transmission of signal A-3. Part (b) shows a pulse transmission of signal A-3 when a delayed forward signal appears, leading to a 'not recognized!!' state in the incoming register. + +**Figure I.2 – Time sequence of a pulsed transmission signal based on [ITU-T Q-Sup.7]** + +# Appendix II + +## Survey of ITU-T H.248 packages for CAS + +(This appendix does not form an integral part of this Recommendation.) + +Channel associated signalling (CAS) interface handling, in contrast to common channel signalling (CCS) interfaces, is under direct responsibility of ITU-T H.248 media gateways. This responsibility includes handling of analogue line signalling (ALS). Figure II.1 provides an overview and genealogy of ITU-T H.248 packages for CAS and ALS processing. + +NOTE – The overview reflects the situation at time of publication. + +ITU-T H.248 Packages for CAS are covered by [ITU-T H.248.25], [ITU-T H.248.28] and ITU-T H.248.29. Analogue or digital trunk CAS-based MG interfaces are instantiated via [ITU-T H.248.25] ("two-wire" interfaces) and [ITU-T H.248.28] ("four-wire" interfaces). ITU-T H.248.29 complements the CAS functionalities with packages for support of register-based CAS systems with compelled signalling capabilities. + +Figure II.1 outlines the two operation modes of ITU-T H.248.29: Annex A with three sequenced packages icasc, icasco, and icasce; and alternatively Annex B with the package icascgen. + +![Survey of ITU-T H.248 packages for CAS (incl. ALS) interfaces diagram](51d4540605fdfa2c090638305022143b_img.jpg) + +The diagram illustrates the relationship between various ITU-T H.248 packages for CAS (incl. ALS) interfaces, categorized into 'Terminal signaling' and 'Private branch exchange and public exchange signaling'. + +**Legend:** + +- inheritance: Package extension (solid line with open arrowhead) +- Package used in addition with (solid line with filled circle) +- Package may be used together with (dashed line with open arrowhead) + +**Terminal signaling:** + +- ITU-T H.248.1 Annex E.9:** + - al: Analogue line supervision Package +- ITU-T H.248.26:** + - xal: Enhanced analogue line supervision Package [->GR-506CORE] (extends al) + - amet: Automatic metering package +- ITU-T H.248.34:** + - stimul: Stimulus analogue line signalling Package + +**Private branch exchange and public exchange signaling:** + +- ITU-T H.248.25:** + - bcas: Basic CAS package + - bcasaddr: Basic CAS addressing package (extends bcas) + - rbs: Robbed bit signalling package (used in addition with bcas) + - oses: Operator services and emergency services package (used in addition with bcas) +- ITU-T H.248.28:** + - icas: International CAS package (extends bcas) + - casblk: CAS blocking package +- ITU-T H.248.29 Annex A:** + - icasce: International CAS compelled with end-to-end package (extends icasco) + - icasco: International CAS compelled with overlap package (extends icasce) + - icase: International CAS compelled package (extends icasco) +- ITU-T H.248.29 Annex B:** + - icasgen: Generic CAS compelled register signalling package + +Survey of ITU-T H.248 packages for CAS (incl. ALS) interfaces diagram + +Figure II.1 – Survey of ITU-T H.248 packages for CAS (incl. ALS) interfaces + +## Bibliography + +[b-IETF RFC 2234] IETF RFC 2234 (1997), *Augmented BNF for Syntax Specifications: ABNF*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.3-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.3-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..02f8ac20963ba197a27ee35cc6dbc29661b75c4c --- /dev/null +++ b/marked/H/T-REC-H.248.3-201303-I_PDF-E/raw.md @@ -0,0 +1,907 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.3** + +(03/2013) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: User interface elements and actions packages** + +Recommendation ITU-T H.248.3 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.248.3 + +# Gateway control protocol: User interface elements and actions packages + +## Summary + +The packages in Recommendation ITU-T H.248.3 define a framework for specifying capabilities associated with user interface elements, such as text display, keys, dynamically labelled keys, indicators and alphanumeric input. In addition, specific extension packages for telephone keypads and telephone function keys are defined. + +This Revision incorporates corrections to the Set Indicator signal "State" and "Indicator description" parameters. + +NOTE – This Recommendation has been renumbered. It was previously known as Recommendation ITU-T H.248, Annex G. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|-----------------------------|------------|-------------| +| 1.0 | ITU-T H.248 Annex G | 2000-11-17 | 16 | +| 1.0 | ITU-T H.248.3 | 2000-11-17 | 16 | +| 1.2 | ITU-T H.248.3 (2000) Cor. 1 | 2004-03-15 | 16 | +| 2.0 | ITU-T H.248.3 | 2013-03-16 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Display Package ..... | 1 | +| 3.1 Properties..... | 1 | +| 3.2 Events ..... | 3 | +| 3.3 Signals ..... | 3 | +| 3.4 Statistics..... | 4 | +| 3.5 Procedures ..... | 4 | +| 4 Key package..... | 5 | +| 4.1 Properties..... | 5 | +| 4.2 Events ..... | 5 | +| 4.3 Signals ..... | 6 | +| 4.4 Statistics..... | 6 | +| 4.5 Procedures ..... | 6 | +| 5 Keypad package..... | 7 | +| 5.1 Properties..... | 7 | +| 5.2 Events ..... | 7 | +| 5.3 Signals ..... | 8 | +| 5.4 Procedures ..... | 8 | +| 6 Label Key package ..... | 9 | +| 6.1 Properties..... | 9 | +| 6.2 Events ..... | 9 | +| 6.3 Signals ..... | 9 | +| 6.4 Procedures ..... | 9 | +| 7 Function Key package ..... | 10 | +| 7.1 Procedures ..... | 10 | +| 8 Indicator package..... | 11 | +| 8.1 Properties..... | 11 | +| 8.2 Events ..... | 11 | +| 8.3 Signals ..... | 11 | +| 8.4 Statistics..... | 12 | +| 8.5 Procedures ..... | 12 | +| 9 Soft Keypackage..... | 13 | +| 9.1 Properties..... | 13 | +| 9.2 Signals ..... | 14 | +| 9.3 Procedures ..... | 14 | + +| | Page | +|---------------------------------|-------------| +| 10 Ancillary Input package..... | 15 | +| 10.1 Properties..... | 15 | +| 10.2 Events ..... | 15 | +| 10.3 Signals ..... | 15 | +| 10.4 Statistics..... | 15 | +| 10.5 Procedures ..... | 15 | + +# Recommendation ITU-T H.248.3 + +# Gateway control protocol: User interface elements and actions packages + +# 1 Scope + +This Recommendation defines a package that extends the applicability of the ITU-T H.248.1 Gateway control protocol. Specifically, the packages in Recommendation ITU-T H.248.3 define a framework for specifying capabilities associated with user interface elements, such as text display, keys, dynamically labelled keys, indicators and alphanumeric input. In addition, specific extension packages for telephone keypads and telephone function keys are defined. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*. + +[ISO/IEC 10646] ISO/IEC 10646:2012, *Information technology – Universal Coded Character Set (UCS) and its Amendment 1 (2013)*. + +# 3 Display Package + +**Package name:** Display Package + +**Package ID:** dis (0x0014) + +**Version:** 1 + +**Extends:** None. + +**Description:** This package defines properties and signals associated with text display user interface elements. See Procedures for details of operation. + +## 3.1 Properties + +### 3.1.1 Number of rows + +**Property name:** Number of rows + +**Property ID:** nrows (0x0001) + +**Description:** Maximum number of rows on the display. + +**Type:** integer + +**Possible values:** Zero upwards + +**Default:** None + +**Defined in:** TerminationState. + +**Characteristics:** ReadOnly. + +### 3.1.2 Number of columns + +| | | +|-------------------------|-------------------------------------------| +| Property name: | Number of columns | +| Property ID: | ncols (0x0002) | +| Description: | Maximum number of columns on the display. | +| Type: | integer | +| Possible values: | Zero upwards | +| Default: | None | +| Defined in: | TerminationState | +| Characteristics: | ReadOnly | + +### 3.1.3 Supported unicode code pages + +| | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Supported unicode code pages | +| Property ID: | cdpgs (0x0003) | +| Description: | A list of supported unicode pages. | +| Type: | list of enumerated type | +| Possible values: | See example below | +| Default: | None | +| Defined in: | TerminationState | +| Characteristics: | ReadOnly. | +| Example: |

If the text display element supports U+2500 → U+25ff, U+2600 → U+26ff and U+2700 → U+277f, this property would return "250, 258, 260, 268, 270" in cdpgs.

Unicode page U+0000 → U+00ff shall be supported in all implementations.

| + +### 3.1.4 Cursor row position + +| | | +|-------------------------|---------------------------------------------------------| +| Property name: | Cursor row position | +| Property ID: | cr (0x0004) | +| Description: | This property indicates the row position of the cursor. | +| Type: | integer | +| Possible values: | 0 upwards | +| Default: | None | +| Defined in: | TerminationState | +| Characteristics: | Read/Write | + +### 3.1.5 Cursor column position + +| | | +|-----------------------|------------------------------------------------------------| +| Property name: | Cursor column position | +| Property ID: | cc (0x0005) | +| Description: | This property indicates the column position of the cursor. | +| Type: | integer | + +**Possible values:** 0 upwards +**Default:** None +**Defined in:** TerminationState +**Characteristics:** Read/Write + +NOTE – Row and column numbering begin at 0. A display's origin is row 0, column 0. The origin is at the top left corner. + +### 3.2 Events + +None. + +### 3.3 Signals + +#### 3.3.1 Display + +**Signal name:** Display +**Signal ID:** di (0x0001) +**Description:** Display text. +**Signal type:** Brief +**Duration:** Not applicable. + +##### 3.3.1.1 Additional Parameters + +###### 3.3.1.1.1 Row + +**Parameter name:** Row +**Parameter ID:** r (0x0001) +**Description:** Insertion point row, relative to 0,0. Default is current cursor position. +**Type:** Integer +**Optional:** Yes +**Possible values:** 0 upwards. +**Default:** Current cursor row position. + +###### 3.3.1.1.2 Column + +**Parameter name:** Column +**Parameter ID:** c (0x0002) +**Description:** Insertion point column, relative to 0,0 +**Type:** Integer +**Optional:** Yes +**Possible values:** 0 upwards. +**Default:** Current cursor column position. + +###### 3.3.1.1.3 String + +**Parameter name:** String +**Parameter ID:** star (0x0003) +**Description:** This parameter indicates the text string to be displayed. + +| | | +|-------------------------|---------------------------------------| +| Type: | String | +| Optional: | Yes | +| Possible values: | Any string. | +| Default: | Empty string (moves cursor position). | + +###### 3.3.1.1.4 Attribute + +| | | +|-------------------------|---------------------------------------------------------------------| +| Parameter name: | Attribute | +| Parameter ID: | a (0x0004) | +| Description: | The parameter assigns an attribute to the displayed text. | +| Type: | enumerated or list of enumerated. | +| Optional: | Yes | +| Possible values: | plain (0x0001), blink (0x0002), invert (0x0003), underline (0x0004) | +| Default: | Plain | + +### 3.3.2 Clear Display + +| | | +|---------------------|---------------------------------------------------------------------------------------------------------------| +| Signal name: | Clear Display | +| Signal ID: | cld (0x0002) | +| Description: | This signal clears the entire display and resets the current cursor position to the origin (row 0, column 0). | +| Signal type: | Brief | +| Duration: | Not applicable. | + +#### 3.3.2.1 Additional parameters + +None. + +## 3.4 Statistics + +None. + +## 3.5 Procedures + +Unicode is supported to provide for multiple languages. The Unicode Standard, Version 2.0 or [ISO/IEC 10646] shall be the definitive standard intended when the term Unicode is used within the context of this Recommendation. All text display elements shall at least support the Unicode pages U+0000 → U+00ff as the basic character set. All text strings shall be encoded using UTF-8 as defined in [ISO/IEC 10646]. + +In the Display signal, text will be inserted beginning at the row and column given in the signal parameters, relative to 0,0. If no row and column parameters are given, the text will be inserted starting at the current cursor position. The current cursor position will always be advanced to the position immediately after the last character inserted. + +Carriage return is supported in-string, and moves the text input to the beginning of the next line, clearing the remainder (if any) of the current line. + +Text wrapping is not provided. A string will not word wrap to the next row. If a string cannot fit into the current row, it will be truncated without warning. + +The attribute parameter applies to all characters contained in the current signal. If no attribute is provided, plain text will be displayed. For example, to turn on an attribute in the middle of a string, one would send a signal with a beginning sub-string of plain text, follow by a signal with the desired attribute(s) for the middle sub-string, and finishing with the signal containing the remaining sub-string of plain text. + +# 4 Key package + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | Key | +| Package ID: | key (0x0015) | +| Description: |

This package defines the basic behaviour of key user interface elements. Specific key IDs are selected by name (keyid) from the list of keys. This package does not specify parameter values for keys.

Intended to be extended by other packages which have key behaviour.

| +| Version: | 1 | +| Extends: | None | + +## 4.1 Properties + +None. + +### 4.2 Events + +### 4.2.1 Keydown + +| | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | keydown | +| Event ID: | kd (0x0001) | +| Description: | Detects key was pressed. If the key is already pressed when the keydown event is activated, the keydown event is reported as if keypress had just occurred. | + +##### 4.2.1.1 EventDescriptor parameters + +None. + +##### 4.2.1.2 ObservedEventDescriptor parameter + +###### 4.2.1.2.1 Key Identity + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------| +| Parameter name: | Key Identity | +| Parameter ID: | keyid (0x0001) | +| Description: | This parameter indicates the identity of the key that was pressed. | +| Type: | Enumeration | +| Optional: | No | +| Possible values: | No values are specified in this package. Extensions to this package add possible values for keyid. | +| Default: | None | + +#### 4.2.2 Keyup + +**Event name:** keyup +**Event ID:** ku (0x0002) +**Description:** Detects key up. + +##### 4.2.2.1 EventDescriptor parameters + +None. + +##### 4.2.2.2 ObservedEventDescriptor parameter + +###### 4.2.2.2.1 Key Identity + +**Parameter name:** Key Identity +**Parameter ID:** keyid (0x0001) +**Description:** This parameter indicates the identity of the key that was released. +**Type:** Enumeration +**Optional:** No +**Possible values:** No possible values are specified in this package. Extensions to this package would add possible values for keyid. +**Default:** None + +###### 4.2.2.2.2 Duration + +**Parameter name:** Duration +**Parameter ID:** duration (0x0002) +**Description:** Key press duration (key down to key up). +**Type:** Integer +**Optional:** No +**Possible values:** 0 upwards in milliseconds +**Default:** None + +### 4.3 Signals + +None. + +## 4.4 Statistics + +None. + +## 4.5 Procedures + +None. + +## 5 Keypad package + +**Package name:** Keypad + +**Package ID:** kp (0x0016) + +**Description:** This package defines the keypad user interface element. The keypad package is used to represent a standard 10 digit key pad plus the '\*', '#', A, B, C and D keys. Keypad may be used in conjunction with digit maps, similar to dtmf tone detection package. + +Additional Keyid values, and mapping to DigitMap symbols (as described in clause 7.1.14 of [ITU-T H.248.1]): + +| Name | Description | DigitMap Symbol | +|-------------|----------------|-----------------| +| k0 (0x0001) | Keypad digit 0 | '0' | +| k1 (0x0002) | Keypad digit 1 | '1' | +| k2 (0x0003) | Keypad digit 2 | '2' | +| k3 (0x0004) | Keypad digit 3 | '3' | +| k4 (0x0005) | Keypad digit 4 | '4' | +| k5 (0x0006) | Keypad digit 5 | '5' | +| k6 (0x0007) | Keypad digit 6 | '6' | +| k7 (0x0008) | Keypad digit 7 | | +| k8 (0x0009) | Keypad digit 8 | '8' | +| k9 (0x000a) | Keypad digit 9 | '9' | +| ks (0x000b) | Keypad digit * | 'E' or 'e' | +| ko (0x000c) | Keypad digit # | 'F' or 'f' | +| kA (0x000d) | Keypad digit A | 'A' or 'a' | +| kB (0x000e) | Keypad digit B | 'B' or 'b' | +| kC (0x000f) | Keypad digit C | 'C' or 'c' | +| kD (0x0010) | Keypad digit D | 'D' or 'd' | + +**Version:** 1 + +**Extends:** key version 1 + +## 5.1 Properties + +None. + +### 5.2 Events + +### 5.2.1 DigitMap Completion Event + +**Event name:** DigitMap Completion Event + +**Event ID:** ce (0x0003) + +**Description:** Generated when a digit map completes as described in clause 7.1.14 of [ITU-T H.248.1]. Form of this event is identical to its definition in DTMF Detection Package (dd), clause E.6.2 of [ITU-T H.248.1]. + +##### 5.2.1.1 EventsDescriptor parameters + +Digit map processing is activated only if a digit map parameter is present, specifying a digit map by name or by value. Other parameters such as a KeepActive flag or embedded Events or Signals Descriptors may be present. + +##### 5.2.1.2 ObservedEventsDescriptor parameters + +###### 5.2.1.2.1 DigitString + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | DigitString | +| Parameter ID: | ds (0x0001) | +| Description: | The portion of the current dial string as described in clause 7.1.14 of [ITU-T H.248.1] which matched part or all of an alternative event sequence specified in the digit map. | +| Type: | String of digit map symbols (possibly empty) returned as a quotedString. | +| Optional: | No | +| Possible values: | A sequence of the characters "0" through "9", "A" through "F", and the long duration modifier "Z". | +| Default: | None | + +###### 5.2.1.2.2 Termination Method + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Termination Method | +| Parameter ID: | meth (0x0003) | +| Description: | indicates the reason for generation of the event. See the procedures in clause 7.1.14 of [ITU-T H.248.1]. | +| Type: | Enumeration | +| Optional: | No | +| Possible values: | "UM" (0x0001) Unambiguous match
"PM" (0x0002) Partial match, completion by timer expiry or unmatched event
"FM" (0x0003) Full match, completion by timer expiry or unmatched event | +| Default: | None | + +## 5.3 Signals + +None. + +## 5.4 Procedures + +None. + +# 6 Label Key package + +**Package name:** Label Key + +**Package ID:** labelkey (0x0017) + +**Description:** This package defines the basic behaviour of labelled key user interface elements. Key labels may be used, for example, to provide information to the MGC regarding preconfigured telephone key assignments, allowing telephone moves and changes outside the initial administrative domain without requiring reconfiguration of keys. May also be used to provide static label information on the telephone user interface, identifying key function to the user without the need for manual labelling. + +Specific keys are addressed by name (keyid) from the list of keys. This package does not specify parameter values for keys. + +Intended to be extended by other packages which have key behaviour. + +**Version:** 1 + +**Extends:** key version 1 + +## 6.1 Properties + +### 6.1.1 Key List + +**Property name:** Key List + +**Property ID:** keylist (0x0001) + +**Description:** Keylist property allows auditing and setting of keyid/label mapping. Label size is also given. This package defines syntax only; no specific keys are defined. See derived packages for the actual keyid lists. + +**Type:** String + +**Possible values:** String using the following format { {keyid, label, label\_size}, ... } + +**Default:** None + +**Defined in:** TerminationState + +**Characteristics:** Read/Write + +## 6.2 Events + +None. + +## 6.3 Signals + +None. + +## 6.4 Procedures + +None. + +## 7 Function Key package + +**Package name:** Function Key + +**Package ID:** kf (0x0018) + +**Description:** Common telephone function keys are defined in this package. This allows, for example, line keys and other function keys to be implemented without specific knowledge of the physical layout of the telephone. + +Additional keyid values in keyup and keydown events and keylist property: + +| Name | Description | +|---------------------------|---------------------------------| +| kh (0x0011) | Hookswitch | +| kl (0x0012) | Hold | +| kc (0x0013) | Conference | +| kt (0x0014) | Transfer | +| l001-l999 (0x0015-0x03fb) | Set of line keys | +| f001-f999 (0x03fc-0x07e2) | Set of assignable function keys | + +**Version:** 1 + +**Extends:** labelkey version 1 + +## 7.1 Procedures + +Function Keys may have well-known names (keyid) associated with function, for example "hookswitch", "hold", etc. These well known names identify the purpose of the particular key on the actual device. Function Keys may also be assigned a label identifier by the MGC. This approach avoids assumptions and/or the requirement for application level knowledge of device-specific configuration of the physical resources to derive intended function of keys. + +Function Keys can be correlated with physically associated Indicators using Function Key keyid and Indicator indid. If the IDs are identical, the MGC application can safely assume that the key and indicator are physically (or otherwise) associated on the actual device. Again, this avoids assumptions and/or the requirement for application level knowledge of device-specific layout of the physical resources. See also the Indicator package (ind). + +NOTE – The key sense of hookswitch (keyid = kh) is a special case. Key up indicates the hookswitch is depressed (i.e., handset is nominally on hook). Key down indicates the hookswitch is lifted (i.e., handset is nominally off hook). This allows for sensible use of the duration parameter in the keyup event which will normally give the duration the handset was off-hook. + +# 8 Indicator package + +**Package name:** Indicator + +**Package ID:** ind (0x0019) + +**Description:** This package defines the basic behaviour of indicator user interface elements. Specific indicators are addressed by name (indid) from the list of indicators. Indicators may have well-known names (indid) associated with function, for example "message waiting", "hold", "line active", etc. This allows, for example, indicators to be implemented without specific knowledge of the physical layout of the telephone. + +Intended to be possible to extend by other packages which have indicator behaviour. + +**Version:** 1 + +**Extends:** None + +## 8.1 Properties + +### 8.1.1 Indicator List + +**Property name:** Indicator List + +**Property ID:** indlist (0x0001) + +**Description:** Indicator List property allows auditing and setting of indid/label mapping. Label size is also given. This package defines syntax only; no specific indicators are defined. See derived packages for the actual indid lists. + +**Type:** String + +**Possible values:** String using the following format: {{indid, label, label\_size}, ...} + +**Default:** None + +**Defined in:** TerminationState. + +**Characteristics:** Read/Write + +## 8.2 Events + +None. + +## 8.3 Signals + +### 8.3.1 Set Indicator + +**Signal name:** SetIndicator + +**Signal ID:** is (0x0001) + +**Description:** The signal sets the indicator state. + +**Signal type:** Brief + +**Duration:** Not applicable (See "Signal Procedures"). + +##### 8.3.1.1 Additional parameters + +###### 8.3.1.1.1 Indicator description + +**Parameter name:** Indicator description + +**Parameter ID:** Indid (0x0001) + +**Description:** This parameter specifies the indicator to be set. + +**Type:** Enumeration + +**Optional:** No + +**Possible values:** + +| Name | Description | +|---------------------------|---------------------------------------| +| off(0x0000) | Off | +| il (0x0001) | Hold | +| ic (0x0002) | Conference | +| l001-l999 (0x0003-0x03e9) | Set of line indicators | +| f001-f999 (0x03fa-0x07e0) | Set of assignable function indicators | +| ir (0x07e1) | Ringer/Alerter indication | +| im (0x07e2) | Message waiting indicator | + +NOTE – Values 0x03ea to 0x03f9 are reserved. + +**Default:** None + +###### 8.3.1.1.2 State + +**Parameter name:** State + +**Parameter ID:** state (0x0002) + +**Description:** This parameter specifies the state of the associated indicator. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** on (0x0001) +off (0x0002) +blink (0x0003) +fast\_blink (0x0004) +slow\_blink (0x0005). + +**Default:** off + +## 8.4 Statistics + +None. + +## 8.5 Procedures + +### 8.5.1 General + +Indicators can be co-related with physically associated Function Keys using Indicator indid and Function Key keyid. If the IDs are identical, the MGC application can safely assume that the key and indicator are physically (or otherwise) associated on the actual device. This avoids assumptions and/or the requirement for application level knowledge of device-specific layout of the physical resources. See also the Function Keys package (kf in clause 7). + +### 8.5.2 Signal procedures + +Each addressed indicator always has a certain state. The *SetIndicator* signal shall therefore be considered to control state changes rather than as persistent signal associated with a period of time of length greater than zero. + +## 9 Soft Keypackage + +**Package name:** Soft Key + +**Package ID:** ks (0x001a) + +**Description:** Softkeys are a combination of a Function Key and a display user interface element, sharing some behaviour of each. Softkeys are intended to be dynamically updated by the MGC, based on the current state and context of the application controlling the MG. Since the display aspect and the key aspect are explicitly bound together, this avoids assumptions and/or the requirement for application level knowledge of device-specific layout of the physical resources. + +See Procedures for details. + +**Version:** 1 + +**Extends:** labelkey version 1 + +## 9.1 Properties + +### 9.1.1 Number of soft keys + +**Property name:** Number of softkeys + +**Property ID:** nskeys (0x0002) + +**Description:** Maximum number of individual softkeys. + +**Type:** Integer + +**Possible values:** 0 upwards + +**Default:** None + +**Defined in:** TerminationState + +**Characteristics:** ReadOnly + +### 9.1.2 Display size + +**Property name:** Display size + +**Property ID:** sz (0x0003) + +**Description:** Maximum number of characters that can be displayed in each softkey. + +**Type:** Integer + +**Possible values:** 0 upwards + +**Default:** None + +**Defined in:** TerminationState + +**Characteristics:** ReadOnly + +### 9.1.3 Supported Unicode code pages + +| | | +|-------------------------|-----------------------------------| +| Property name: | Supported Unicode code pages | +| Property ID: | cdpgs (0x0004) | +| Description: | a list of supported Unicode pages | +| Type: | list of enumerated type | +| Possible values: | See procedures. | +| Default: | None | +| Characteristics: | ReadOnly | +| Defined in: | TerminationState | + +## 9.2 Signals + +| | | +|---------------------|--------------------------------------| +| Signal name: | SetDisplay | +| SignalID: | sd (0x0001) | +| Description: | Set softkey dynamic display content. | + +### 9.2.1 Additional parameters + +#### 9.2.1.1 Keyid + +| | | +|-------------------------|-------------------------------------------------------| +| Parameter Name: | keyed | +| Parameter ID: | k (0x0001) | +| Description: | This parameter indicates the identity of the softkey. | +| Type: | Enumeration | +| Optional: | No | +| Possible values: | sk1-sk999 (0x0001-0x03e7) | +| Default: | None | + +#### 9.2.1.2 Display Content + +| | | +|-------------------------|-----------------| +| Parameter name: | displayContent | +| Parameter ID: | d (0x0002) | +| Description: | | +| Type: | String | +| Optional: | No | +| Possible values: | See procedures. | +| Default: | None | + +## 9.3 Procedures + +The display aspect is a subset of the Display (dis) package. Unicode is supported to provide for multiple languages (see [ISO/IEC 10646]), and all SoftKey elements shall at least support the Unicode pages U+0000 → U+00ff as the basic character set. All text strings shall be encoded using UTF-8. If a string cannot fit into the display area, it will be truncated without warning. + +The key aspect, including Events and labelling, derives directly from Label Key and Key packages. Softkey identifiers (keyid) are indexed 1, 2...N. N (nskeys) is the maximum number of softkeys supported by the MG implementation. Refer to the Label Key (labelkey) and Key (key) packages for further details. + +# 10 Ancillary Input package + +| | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | Ancillary Input | +| Package ID: | anci (0x001b) | +| Description: | The ancillary input package is used to enter user alphanumeric information such as text input or scan data, which is forwarded to the MGC for processing. The information is presented as a Unicode character encoded in UTF-8 format (see [ISO/IEC 10646]). | +| Version: | 1 | +| Extends: | None | + +## 10.1 Properties + +None. + +## 10.2 Events + +| | | +|---------------------|-----------------------------| +| Event name: | Character input | +| Event ID: | ch (0x0001) | +| Description: | A character has been input. | + +### 10.2.1 EventDescriptor parameters + +None. + +### 10.2.2 ObservedEventDescriptor parameters + +#### 10.2.2.1 Identity + +| | | +|-------------------------|-----------------------------------------| +| Parameter Name: | Id | +| Parameter ID: | id (0x0001) | +| Description: | Indicates the character that was input. | +| Type: | character | +| Optional: | No | +| Possible values: | (UTF-8 character) | +| Default: | None | + +## 10.3 Signals + +None. + +## 10.4 Statistics + +None. + +## 10.5 Procedures + +None. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.30-200701-I_PDF-E/raw.md b/marked/H/T-REC-H.248.30-200701-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5cb1f379ea2b47d1ec7eaf36780b95c28d78e963 --- /dev/null +++ b/marked/H/T-REC-H.248.30-200701-I_PDF-E/raw.md @@ -0,0 +1,743 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.30** + +(01/2007) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: RTCP extended performance metrics packages** + +ITU-T Recommendation H.248.30 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation H.248.30** + +# **Gateway control protocol: RTCP extended performance metrics packages** + +## **Summary** + +This Recommendation defines a package that provides RFC 3611's RTP Control Protocol Reporting Extensions (RTCP XR) metrics reporting capabilities for ITU-T Rec. H.248 that provide more detailed insight into call quality and causes of degradation than basic RTCP statistics. + +Edition 2 adds a new package and modifies the existing package to allow the support of reporting RTCP XR statistics from both directions of a bidirectional RTP session controlled through RTCP. + +###### **Source** + +ITU-T Recommendation H.248.30 was approved on 13 January 2007 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2007 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +###### Page + +| | | | +|-----|---------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations..... | 1 | +| 5 | RTCP XR Base Package..... | 2 | +| 5.1 | Properties ..... | 2 | +| 5.2 | Events ..... | 2 | +| 5.3 | Signals ..... | 2 | +| 5.4 | Statistics..... | 2 | +| 5.5 | Procedures ..... | 5 | +| 6 | RTCP XR Burst Metrics Package..... | 5 | +| 6.1 | Properties ..... | 5 | +| 6.2 | Events ..... | 5 | +| 6.3 | Signals ..... | 6 | +| 6.4 | Statistics..... | 6 | +| 6.5 | Procedures ..... | 7 | +| 7 | Received RTCP XR Package..... | 7 | +| 7.1 | Properties ..... | 7 | +| 7.2 | Events ..... | 8 | +| 7.3 | Signals ..... | 8 | +| 7.4 | Statistics..... | 8 | +| 7.5 | Procedures ..... | 10 | +| 8 | Received RTCP XR Burst Metrics Package..... | 10 | +| 8.1 | Properties ..... | 11 | +| 8.2 | Events ..... | 11 | +| 8.3 | Signals ..... | 11 | +| 8.4 | Statistics..... | 11 | +| 8.5 | Procedures ..... | 12 | + + + +# Gateway control protocol: RTCP extended performance metrics packages + +# 1 Scope + +This Recommendation describes a set of Extended Performance Metrics for Voice over IP QoS reporting that provide more detailed insight into call quality and causes of degradation than basic RTCP statistics. The metrics described in this Recommendation are consistent with those described in the RTCP XR Voice over IP Metrics Payload described in IETF RFC 3611. + +This edition 2 adds the capability to report this information bidirectionally. This enhancement allows for detailed insight over the entire topology of the stream in question, rather than just the outbound direction from the point of view of the termination. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation G.107 (2005), *The E-Model, a computational model for use in transmission planning*. +- ITU-T Recommendation G.108 (1999), *Application of the E-model: A planning guide*. +- ITU-T Recommendation H.248.1 (2005), *Gateway control protocol: Version 3*. +- IETF RFC 3611 (2003), *RTP Control Protocol Extended Reports (RTCP XR)*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 burst:** A period during which a high proportion of packets are either lost or discarded due to late arrival. + +**3.2 gap:** A period of low packet losses and/or discards. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|---------|-----------------------------------------------| +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MOSCQ | Mean Opinion Score for Conversational Quality | +| MOSLQ | Mean Opinion Score for Listening Quality | +| RTCP | RTP Control Protocol | +| RTCP XR | RTCP Extended Reports | +| RTP | Real-time Transfer Protocol | + +# 5 RTCP XR Base Package + +Package Name: RTCP XR Base Package +PackageID: rtpxr (0x0080) +Description: This package defines properties and statistics to report extended quality of service metrics generated on the near-end termination for transmission toward the far end of the RTCP session. +Version: 1 +Extends: rtp version 1 + +## 5.1 Properties + +### 5.1.1 Packet Loss Concealment Type + +Property Name: Packet Loss Concealment Type +PropertyID: plc (0x0001) +Description: The type of packet loss concealment algorithm in use. +Type: Enumeration +Possible Values: U (0x0001) Unspecified +D (0x0002) Disabled – Silence insertion is being used. +S (0x0003) Standard. +E (0x0004) Enhanced. +Default: U +Defined in: LocalControl Descriptor +Characteristics: Read/Write + +## 5.2 Events + +None + +## 5.3 Signals + +None + +## 5.4 Statistics + +### 5.4.1 Network Packet Loss Rate + +Statistic Name: Network Packet Loss Rate +StatisticID: nplr (0x0009) +Description: The proportion of packets lost since the start of transmission expressed as an 8-bit binary fraction obtained by dividing the number of packets lost in the transmission path by the total number of packets expected and multiplying this value by 256 and taking the integer part. Thus a value of 0 would correspond to a packet loss rate of zero and a value of 64 would correspond to a packet loss rate of 0.25 (corresponding to 25 per cent). +Type: Integer +Possible values: Any value greater than or equal to 0 + +### **5.4.2 Jitter Buffer Discard Rate** + +Statistic Name: Jitter Buffer Discard Rate +StatisticID: jdr (0x000a) +Description: The proportion of packets discarded by the receiving jitter buffer since the start of transmission expressed as an 8-bit binary fraction obtained by dividing the number of packets discarded by the total number of packets expected and multiplying this value by 256 and taking the integer part. +Type: Integer +Possible values: Any value greater than or equal to 0 +Level: Either + +### **5.4.3 RTCP Round-Trip Delay** + +Statistic Name: RTCP Round-Trip Delay +StatisticID: rtd (0x000b) +Description: The round-trip delay between the RTP interfaces on the local and remote MGs. +Type: Integer +Possible values: Any value greater than or equal to 0 in milliseconds +Level: Either + +### **5.4.4 End System Delay** + +Statistic Name: End System Delay +StatisticID: esd (0x000c) +Description: The end system delay, comprising encode, decode and jitter buffer delay. This may be combined with the RTCP Round-Trip Delay to estimate the overall Voice over IP segment round-trip delay. +Type: Integer +Possible values: Any value greater than or equal to 0 in milliseconds +Level: Either + +### **5.4.5 Signal Level** + +Statistic Name: Signal Level +StatisticID: sl (0x000d) +Description: The ratio of the signal level to a 0 dBm0 reference. +Type: Integer +Possible values: Any value in dB +Level: Either + +### **5.4.6 Noise Level** + +Statistic Name: Noise Level +StatisticID: nl (0x000e) +Description: The ratio of the silent period background noise level to a 0 dBm0 reference. + +Type: Integer +Possible values: Any value less than or equal to 0 in dB +Level: Either + +### **5.4.7 Residual Echo Return Loss** + +Statistic Name: Residual Echo Return Loss +StatisticID: rerl (0x000f) +Description: The echo return loss after the effects of echo cancellation. +Type: Integer +Possible values: Any value greater than or equal to 0 in dB. +Level: Either + +### **5.4.8 R Factor** + +Statistic Name: R Factor +StatisticID: ns (0x0010) +Description: A value representing the receiving end call quality of the RTP stream terminated by this termination, calculated per ITU-T Rec. G.107. Table 1/G.108 provides interpretive information about the value of the R factor. +Type: Integer +Possible values: Any value between 0 and 100 +Level: Either + +### **5.4.9 External R Factor** + +Statistic Name: External R Factor +StatisticID: xns (0x0011) +Description: A value representing the effects of any call segment carried over a network segment external to the RTP stream terminated by this termination, calculated per ITU-T Rec. G.107. Table 1/G.108 provides interpretive information about the value of the R factor. +Type: Integer +Possible values: Any value between 0 and 100 +Level: Either + +### **5.4.10 Estimated MOSLQ** + +Statistic Name: Estimated MOSLQ +StatisticID: lq (0x0012) +Description: An estimated receiving end Listening Quality MOS, calculated per ITU-T Rec. G.107 and multiplied by 10 as described in IETF RFC 3611. +Type: Integer +Possible values: Any value between 10 to 50 +Level: Either + +### **5.4.11 Estimated MOSCQ** + +Statistic Name: Estimated MOSCQ +StatisticID: cq (0x0013) +Description: An estimated receiving end Conversational Quality MOS, calculated per ITU-T Rec. G.107 and multiplied by 10 as described by IETF RFC 3611. +Type: Integer +Possible values: Any value between 10 and 50 +Level: Either + +## **5.5 Procedures** + +None + +# **6 RTCP XR Burst Metrics Package** + +Package Name: RTCP XR Burst Metrics Package +PackageID: xrbm (0x0081) +Description: This package defines properties and statistics for reporting burst metrics generated on the near-end termination for transmission toward the far end of the RTCP session. +Version: 1 +Extends: rtcpXR version 1 + +## **6.1 Properties** + +### **6.1.1 Minimum Gap Threshold** + +Property Name: Minimum Gap Threshold +PropertyID: gmin (0x0002) +Description: A parameter used to define bursts. This is by default set to 16, which sets the threshold packet loss rate between bursts and gaps to approximately 6%. See the procedures for how to use Gmin to determine a burst. Gmin shall not be altered once the RTP stream is established. Attempts to do so should result in the MG returning error xxx. +Type: Integer +Possible values: Any positive integral value +Default: 16 +Defined in: LocalControl Descriptor +Characteristics: Read/Write + +## **6.2 Events** + +None + +## **6.3 Signals** + +None + +## 6.4 Statistics + +### 6.4.1 Burst Loss Density + +Statistic Name: Burst Loss Density + +StatisticID: bld (0x0014) + +Description: The average proportion of packets both lost and discarded during burst periods expressed as an 8-bit binary fraction. This is obtained by dividing the sum of the number of packets lost in the transmission path and discarded by the jitter buffer during burst periods by the total number of packets expected during burst periods, multiplying this value by 256 and taking the integer part. + +A burst is a period during which a high proportion of packets are either lost in transit or discarded due to late arrival. In general, a burst is likely to result in audible degradation to call quality. + +Type: Integer + +Possible values: Any integral value greater than or equal to 0 + +Level: Either + +### 6.4.2 Burst Duration + +Statistic Name: Burst Duration + +StatisticID: bd (0x0015) + +Description: The average length of burst periods. + +Type: Integer + +Possible values: Any integral number of milliseconds greater than or equal to 0 + +Level: Either + +### 6.4.3 Gap Loss Density + +Statistic Name: Gap Loss Density + +StatisticID: gld (0x0016) + +Description: The average proportion of packets lost and discarded during gap periods expressed as an 8-bit binary fraction. This is obtained by dividing the sum of the number of packets lost in the transmission path and discarded by the jitter buffer during gap periods by the total number of packets expected during gap periods, multiplying this value by 256 and taking the integer part. + +Type: Integer + +Possible values: Any integral value greater than or equal to 0 + +Level: Either + +### 6.4.4 Gap Duration + +Statistic Name: Gap Duration + +StatisticID: gd (0x0017) + +Description: The average length of gap periods. + +Type: Integer + +Possible values: Any integral number of milliseconds greater than or equal to 0 + +Level:                    Either + +## 6.5    Procedures + +For the purposes of calculating the statistics above, a burst is defined as the longest sequence that: + +- a)    starts with a lost or discarded packet; +- b)    does not contain any occurrences of consecutive received (and not discarded) packets numbering greater than or equal to the Gmin property value; and +- c)    ends with a lost or discarded packet. + +A gap is defined as any of the following: + +- a)    the period from the start of an RTP session to the receipt time of the last received packet before the first burst; +- b)    the period from the end of the last burst to either the time of the report or the end of the RTP session, whichever comes first; or +- c)    the period of time between two bursts. + +# 7    Received RTCP XR Package + +Package Name:    Received RTCP XR Package + +PackageID:        recrtcpxr (0x00b0) + +Description:      This package defines properties and statistics to report extended quality of service metrics received from the far end of the RTCP session. + +Version:            1 + +Extends:          rtp version 1 + +## 7.1    Properties + +### 7.1.1    Packet Loss Concealment Type + +Property Name:    Packet Loss Concealment Type + +PropertyID:        plc (0x0001) + +Description:      The type of packet loss concealment algorithm in use. + +Type:                Enumeration + +Possible Values:    U (0x0001)    Unspecified +                              D (0x0002)    Disabled – Silence insertion is being used. +                              S (0x0003)    Standard +                              E (0x0004)    Enhanced + +Default:              U + +Defined in:          LocalControl Descriptor + +Characteristics:    Read/Write + +## 7.2    Events + +None + +## 7.3 Signals + +None + +## 7.4 Statistics + +### 7.4.1 Network Packet Loss Rate + +Statistic Name: Network Packet Loss Rate + +StatisticID: nplr (0x0009) + +Description: The proportion of packets lost since the start of transmission expressed as an 8-bit binary fraction obtained by dividing the number of packets lost in the transmission path by the total number of packets expected and multiplying this value by 256 and taking the integer part. Thus a value of 0 would correspond to a packet loss rate of zero and a value of 64 would correspond to a packet loss rate of 0.25 (corresponding to 25 per cent). + +Type: Integer + +Possible values: Any value greater than or equal to 0 + +Level: Either + +### 7.4.2 Jitter Buffer Discard Rate + +Statistic Name: Jitter Buffer Discard Rate + +StatisticID: jdr (0x000a) + +Description: The proportion of packets discarded by the receiving jitter buffer since the start of transmission expressed as an 8-bit binary fraction obtained by dividing the number of packets discarded by the total number of packets expected and multiplying this value by 256 and taking the integer part. + +Type: Integer + +Possible values: Any value greater than or equal to 0 + +Level: Either + +### 7.4.3 RTCP Round-Trip Delay + +Statistic Name: RTCP Round-Trip Delay + +StatisticID: rtd (0x000b) + +Description: The round-trip delay between the RTP interfaces on the local and remote MGs. + +Type: Integer + +Possible values: Any value greater than or equal to 0 in milliseconds + +Level: Either + +### 7.4.4 End System Delay + +Statistic Name: End System Delay + +StatisticID: esd (0x000c) + +Description: The end system delay, comprising encode, decode and jitter buffer delay. This may be combined with the RTCP Round-Trip Delay to estimate the overall Voice over IP segment round-trip delay. + +Type: Integer + +Possible values: Any value greater than or equal to 0 in milliseconds + +Level: Either + +### **7.4.5 Signal Level** + +Statistic Name: Signal Level + +StatisticID: sl (0x000d) + +Description: The ratio of the signal level to a 0 dBm0 reference. + +Type: Integer + +Possible values: Any value in dB + +Level: Either + +### **7.4.6 Noise Level** + +Statistic Name: Noise Level + +StatisticID: nl (0x000e) + +Description: The ratio of the silent period background noise level to a 0 dBm0 reference. + +Type: Integer + +Possible values: Any value less than or equal to 0 in dB + +Level: Either + +### **7.4.7 Residual Echo Return Loss** + +Statistic Name: Residual Echo Return Loss + +StatisticID: rerl (0x000f) + +Description: The echo return loss after the effects of echo cancellation. + +Type: Integer + +Possible values: Any value greater than or equal to 0 in dB. + +Level: Either + +### **7.4.8 R Factor** + +Statistic Name: R Factor + +StatisticID: ns (0x0010) + +Description: A value representing the receiving end call quality of the RTP stream terminated by this termination, calculated per ITU-T Rec. G.107. Table 1/G.108 provides interpretive information about the value of the R factor. + +Type: Integer + +Possible values: Any value between 0 and 100 + +Level: Either + +### **7.4.9 External R Factor** + +Statistic Name: External R Factor + +StatisticID: xns (0x0011) + +**Description:** A value representing the effects of any call segment carried over a network segment external to the RTP stream terminated by this termination, calculated per ITU-T Rec. G.107. Table 1/G.108 provides interpretive information about the value of the R factor. + +**Type:** Integer + +**Possible values:** Any value between 0 and 100 + +**Level:** Either + +### **7.4.10 Estimated MOSLQ** + +**Statistic Name:** Estimated MOSLQ + +**StatisticID:** lq (0x0012) + +**Description:** An estimated receiving end Listening Quality MOS, calculated per ITU-T Rec. G.107 and multiplied by 10 as described in IETF RFC 3611. + +**Type:** Integer + +**Possible values:** Any value between 10 to 50 + +**Level:** Either + +### **7.4.11 Estimated MOSCQ** + +**Statistic Name:** Estimated MOSCQ + +**StatisticID:** cq (0x0013) + +**Description:** An estimated receiving end Conversational Quality MOS, calculated per ITU-T Rec. G.107 and multiplied by 10 as described by IETF RFC 3611. + +**Type:** Integer + +**Possible values:** Any value between 10 and 50 + +**Level:** Either + +## **7.5 Procedures** + +None + +# **8 Received RTCP XR Burst Metrics Package** + +**Package Name:** Received RTCP XR Burst Metrics Package + +**PackageID:** recxrbm (0x00b1) + +**Description:** This package defines properties and statistics for reporting burst metrics received from the far end of the RTCP session. + +**Version:** 1 + +**Extends:** recrtcpXR version 1 + +## **8.1 Properties** + +### **8.1.1 Minimum Gap Threshold** + +**Property Name:** Minimum Gap Threshold + +**PropertyID:** gmin (0x0002) + +**Description:** Parameter used to define bursts. This is by default set to 16, which sets the threshold packet loss rate between bursts and gaps to approximately 6%. See the procedures for how to use Gmin to determine a burst. Gmin shall not be altered once the RTP stream is established. Attempts to do so should result in the MG returning error xxx. + +**Type:** Integer + +**Possible values:** Any positive integral value + +**Default:** 16 + +**Defined in:** LocalControl Descriptor + +**Characteristics:** Read/Write + +## **8.2 Events** + +None + +## **8.3 Signals** + +None + +## **8.4 Statistics** + +### **8.4.1 Burst Loss Density** + +**Statistic Name:** Burst Loss Density + +**StatisticID:** bld (0x0014) + +**Description:** The average proportion of packets both lost and discarded during burst periods expressed as an 8-bit binary fraction. This is obtained by dividing the sum of the number of packets lost in the transmission path and discarded by the jitter buffer during burst periods by the total number of packets expected during burst periods, multiplying this value by 256 and taking the integer part. + +A burst is a period during which a high proportion of packets are either lost in transit or discarded due to late arrival. In general, a burst is likely to result in audible degradation to call quality. + +**Type:** Integer + +**Possible values:** Any integral value greater than or equal to 0 + +**Level:** Either + +### **8.4.2 Burst Duration** + +**Statistic Name:** Burst Duration + +**StatisticID:** bd (0x0015) + +**Description:** The average length of burst periods. + +**Type:** Integer + +**Possible values:** Any integral number of milliseconds greater than or equal to 0 + +**Level:** Either + +### **8.4.3 Gap Loss Density** + +**Statistic Name:** Gap Loss Density + +StatisticID: gld (0x0016) +Description: The average proportion of packets lost and discarded during gap periods expressed as an 8-bit binary fraction. This is obtained by dividing the sum of the number of packets lost in the transmission path and discarded by the jitter buffer during gap periods by the total number of packets expected during gap periods, multiplying this value by 256 and taking the integer part. +Type: Integer +Possible values: Any integral value greater than or equal to 0 +Level: Either + +### 8.4.4 Gap Duration + +Statistic Name: Gap Duration +StatisticID: gd (0x0017) +Description: The average length of gap periods. +Type: Integer +Possible values: Any integral number of milliseconds greater than or equal to 0 +Level: Either + +## 8.5 Procedures + +For the purposes of calculating the statistics above, a burst is defined as the longest sequence that: + +- a) starts with a lost or discarded packet; +- b) does not contain any occurrences of consecutive received (and not discarded) packets numbering greater than or equal to the Gmin property value; and +- c) ends with a lost or discarded packet. + +A gap is defined as any of the following: + +- a) the period from the start of an RTP session to the receipt time of the last received packet before the first burst; +- b) the period from the end of the last burst to either the time of the report or the end of the RTP session, whichever comes first; or +- c) the period of time between two bursts. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.31-200404-I_PDF-E/raw.md b/marked/H/T-REC-H.248.31-200404-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..921eb96b320dc0da73e6f3d5069c9cae7f1683de --- /dev/null +++ b/marked/H/T-REC-H.248.31-200404-I_PDF-E/raw.md @@ -0,0 +1,397 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.31** + +(04/2004) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Adaptive jitter buffer +package** + +ITU-T Recommendation H.248.31 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Gateway control protocol: Adaptive jitter buffer package + +## Summary + +This Recommendation defines a package that allows the media gateway controller (MGC) to specify the nominal value and the minimum value of the adaptive jitter buffer on the media gateway (MG). This package allows the MGC to specify adaptive jitter buffer value settings on a particular stream at any time throughout a call, and it allows the MGC to enable or disable the use of a jitter buffer. In addition, the package contains a set of jitter buffer metrics that are consistent with those described in IETF RFC 3611, RTP Control Protocol Extended Reports (RTCP XR). These jitter buffer metrics may be used, for example, with voice over IP, video, and audio. The package should be used in combination with the base network package that defines the maximum value for the jitter buffer. An adaptive jitter buffer (AJB) is characterized by these minimum, maximum, and nominal values. + +The AJB functions in a MG to smooth the play out of packets arriving at the MG. As the packet arrival delay varies during the course of the transmission, the jitter buffer adapts using the minimum, maximum, and nominal values to control the adaptation. Real time media requirements are stringent and, for that reason, it is important to set the jitter buffer values to their optimal setting as early on the call as possible since a jitter buffer that is too large will introduce unnecessary bearer delay, which has a negative impact on real time media quality, and a jitter buffer that is too small will prevent a smooth play out (packet loss, another negative impact). The proper jitter buffer size is the balance between delay and packet loss. The distortion that the media receiver would otherwise observe is eliminated with the AJB. + +###### Source + +ITU-T Recommendation H.248.31 was approved on 22 April 2004 by ITU-T Study Group 16 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations..... | 1 | +| 5 Conventions ..... | 2 | +| 5.1 Convention for Termination Identifiers in this Recommendation ..... | 2 | +| 5.2 Convention for Context Identifiers in this Recommendation..... | 2 | +| 6 Adaptive Jitter Buffer Package..... | 2 | +| 6.1 Properties..... | 2 | +| 6.2 Events ..... | 4 | +| 6.3 Signals ..... | 4 | +| 6.4 Statistics..... | 4 | +| 6.5 Procedures ..... | 4 | + + + +# Gateway control protocol: Adaptive jitter buffer package + +# 1 Scope + +This Recommendation defines a package that allows the media gateway controller (MGC) to specify the nominal value and the minimum value of the adaptive jitter buffer on the media gateway (MG). This package allows the MGC to specify adaptive jitter buffer value settings on a particular stream at any time throughout a call, and it allows the MGC to enable or disable the use of a jitter buffer. In addition, the package contains a set of jitter buffer metrics that are consistent with those described in IETF RFC 3611, RTP Control Protocol Extended Reports (RTCP XR). These jitter buffer metrics may be used, for example, with voice over IP, video, and audio. The package should be used in combination with the base network package that defines the maximum value for the jitter buffer. An adaptive jitter buffer (AJB) is characterized by these minimum, maximum, and nominal values. + +The MGC will be able to determine more meaningful values for the adaptive jitter buffer as in a majority of cases the MGC will have the knowledge of: the network architecture, the number of contexts involved in a single call, the packet networks between contexts in a call, the characteristics of the packet delay variations, etc. This, in turn, will optimize the real time media quality and end-to-end delay of a call. Each packet can encounter a different amount of delay when traversing from end-to-end. Although the variation is somewhat random, its variance depends on the network topology. For example, the greater the number of hops and the longer the distance required to make the packet transmission, the more delay is expected to get through the network and the more variance in the delay. If the MGC has knowledge of the network topology, it can adjust the jitter buffer parameters accordingly. In the case of multiple MGCs being involved in an end-to-end call, each individual MGC will be responsible for determining the appropriate jitter buffer value(s) based on its own knowledge. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.248.1 (2002), *Gateway control protocol: Version 2*. +- IETF RFC 3611 (2003), *RTP Control Protocol Extended Reports (RTCP XR)*. + +# 3 Definitions + +N/A + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-----|------------------------| +| AJB | Adaptive Jitter Buffer | +| EPH | Ephemeral | + +| | | +|---------|-----------------------------------| +| IP | Internet Protocol | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| RTCP | RTP Control Protocol | +| RTCP XR | RTCP Extended Reports | +| RTP | Real-time Transfer Protocol | +| TDM | Time Division Multiplex (Network) | +| VoIP | Voice over IP | + +## 5 Conventions + +### 5.1 Convention for Termination Identifiers in this Recommendation + +Ex: This refers to an Ephemeral Termination Identifier. + +Tx: This refers to a TDM (Physical) Termination Identifier. + +Where "x" is an alphanumeric value (e.g., O (originating), T (terminating), s (send), r (receive), s2, r2, 1, 2, 3). + +These are set to distinguish the different terminations within the diagram. + +### 5.2 Convention for Context Identifiers in this Recommendation + +Cy: This refers to an H.248 Context Identifier. + +Where "y" is an alphanumeric value. + +# 6 Adaptive Jitter Buffer Package + +PackageID: ajb (0x007a) + +Version: 1 + +Extends: nt (0x000b) version 1 + +This package extends the base Network Package and allows the media gateway controller (MGC) to specify the nominal value and the minimum value of the adaptive jitter buffer on a stream in the media gateway (MG). The package also provides the ability to enable/disable a jitter buffer, and it defines properties to report extended jitter buffer metrics. + +### 6.1 Properties + +#### 6.1.1 Minimum Jitter Buffer + +PropertyID: jitmin (0x0008) + +Description: + +This property sets the minimum size of the adaptive jitter buffer. + +Type: Integer + +Possible Values: Any integral number of milliseconds greater than or equal to zero + +Defined In: LocalControlDescriptor + +Characteristics: Read/Write + +#### 6.1.2 Nominal Jitter Buffer + +PropertyID: jitnom (0x0009) + +Description: + +This property sets the nominal size of the adaptive jitter buffer. + +Type: Integer + +Possible Values: Any integral number of milliseconds greater than or equal to zero. + +Defined In: LocalControlDescriptor + +Characteristics: Read/Write + +#### 6.1.3 Enable Jitter Buffer + +PropertyID: enabjb (0x000a) + +Description: + +It enables/disables a jitter buffer. The type of jitter buffer enabled is indicated with *Jitter Buffer Type (0x000b)*. If disabled, no jitter buffer is inserted. + +Type: Boolean + +Possible values: on/off + +Defined In: LocalControlDescriptor + +Characteristics: Read/Write + +#### 6.1.4 Jitter Buffer Type + +PropertyID: type (0x000b) + +Description: + +Indicates the jitter buffer type. When the jitter buffer is adaptive, then its size is being dynamically adjusted to deal with varying levels of jitter. When non-adaptive, the jitter buffer size is maintained at a fixed level. + +Type: Enumeration + +Possible values: "NO" (0x0000) No Jitter Buffer (Default) + +"N" (0x0001) Non-adaptive + +"A" (0x0002) Adaptive + +Defined In: LocalControlDescriptor + +Characteristics: Read/Write + +#### 6.1.5 Current Jitter Buffer + +PropertyID: jitcur (0x000c) + +Description: + +This property is used to obtain the current jitter buffer size at the media gateway. + +Type: Integer + +Possible Values: Any integral number of milliseconds greater than or equal to zero + +Defined In: LocalControlDescriptor + +Characteristics: Read Only + +#### 6.1.6 Adaptation Rate + +PropertyID: ar (0x000d) + +Description: + +The adaptation rate for the adaptive jitter buffer. This is defined as the time taken in milliseconds adjusting to a step from 30 ms to 100 ms in peak-to-peak jitter divided by twice the frame size in milliseconds. This property does not apply to non-adaptive jitter buffers and shall be 0 if the jitter buffer type is set to non-adaptive. + +Type: Integer + +Possible values: Any integral number greater than or equal to zero + +Defined In: LocalControlDescriptor + +Characteristics: Read Only + +## 6.2 Events + +None. + +## 6.3 Signals + +None. + +## 6.4 Statistics + +None. + +### 6.5 Procedures + +A jitter buffer is inserted to smooth out the delay variance that real time media packets may experience through packet transport network(s). Large jitter buffers enable a GW to tolerate longer delay variance and minimize packet loss introduced by delay. However, larger jitter buffers also introduce bearer delay, which has a negative impact on real time media quality. Therefore, it is important to optimize the insertion of jitter buffers. The nominal value is a default system value that is used at the beginning of a call. In the case of adaptive jitter buffers, the media gateway will adjust the size of the jitter buffer dynamically during the call based on the packet delay variation. To optimize the delay and packet loss, it is necessary to specify the minimum, maximum, and/or nominal values of the adaptive jitter buffer based on the known network topology of each individual call. + +The absolute maximum jitter buffer size and the absolute minimum jitter buffer size capabilities of the media gateway may be obtained through use of AuditCapabilities of the maximum jitter buffer property *jit* (0x0007) and the minimum jitter buffer property *jitmin* (0x0008). The current jitter buffer size in use may be obtained through use of AuditValue of the current jitter buffer property *jitcur* (0x000c). AuditValue of the maximum jitter buffer property *jit* (0x0007) and the minimum jitter buffer property *jitmin* (0x0008) will provide the current maximum and minimum jitter buffer size values. + +When this package is implemented, the MGC is able to, on a per stream basis: + +- enable or disable the use of a jitter buffer; +- specify the type of jitter buffer to be enabled; +- for an adaptive jitter buffer, set the minimum and nominal jitter buffer values along with the maximum jitter buffer value (as described in the Network Package); +- for a static jitter buffer, the existing maximum jitter buffer property *jit* (as described in the Network Package) is used to set the jitter buffer value; and + +- audit the MGW for VoIP jitter buffer metrics. + +The initial jitter buffer values may be set on a stream. In the case of adaptive jitter buffers, the MG would then *adapt* the jitter buffer based on buffer occupancy, packet arrival time, etc. Additionally the MGC has the flexibility to change these values during the course of the call if it deemed this as a beneficial to the whole system. + +The MGC has knowledge of the different contexts involved in a single call. Given this knowledge, along with other information such as the network architecture, etc., the MGC is able to set more meaningful values for the involved jitter buffers. + +For example, when a call involves two contexts on the same MG (as shown in Figure 1), the jitter buffers will be set with lower minimum, maximum and nominal values than a call that involves two contexts, each in a separate MG (as shown in Figure 2). + +![Diagram of Figure 1/H.248.31 – Two contexts in a single MG. A Media gateway controller is connected to MG A. MG A contains two contexts, Context C1 and Context C2. Context C1 consists of a TDM and an EPH connected by a double-headed arrow, with termination IDs T_O and E_O. Context C2 consists of a TDM and an EPH connected by a double-headed arrow, with termination IDs T_T and E_T. The entire MG A is enclosed in a dashed yellow oval. The diagram is labeled H.248.31_F01.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +Diagram of Figure 1/H.248.31 – Two contexts in a single MG. A Media gateway controller is connected to MG A. MG A contains two contexts, Context C1 and Context C2. Context C1 consists of a TDM and an EPH connected by a double-headed arrow, with termination IDs T\_O and E\_O. Context C2 consists of a TDM and an EPH connected by a double-headed arrow, with termination IDs T\_T and E\_T. The entire MG A is enclosed in a dashed yellow oval. The diagram is labeled H.248.31\_F01. + +T\_O, T\_T, E\_O, E\_T are Termination IDs + +**Figure 1/H.248.31 – Two contexts in a single MG** + +![Diagram of Figure 2/H.248.31 – Two contexts in separate MGs. A Media gateway controller is connected to MG A and MG B. MG A contains Context C1, which consists of a TDM and an EPH connected by a double-headed arrow, with termination IDs T_O and E_O. MG B contains Context C2, which consists of an EPH and a TDM connected by a double-headed arrow, with termination IDs E_T and T_T. MG A and MG B are connected via a cloud labeled 'Packet network'. Each MG is enclosed in a dashed yellow oval. The diagram is labeled H.248.31_F02.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +Diagram of Figure 2/H.248.31 – Two contexts in separate MGs. A Media gateway controller is connected to MG A and MG B. MG A contains Context C1, which consists of a TDM and an EPH connected by a double-headed arrow, with termination IDs T\_O and E\_O. MG B contains Context C2, which consists of an EPH and a TDM connected by a double-headed arrow, with termination IDs E\_T and T\_T. MG A and MG B are connected via a cloud labeled 'Packet network'. Each MG is enclosed in a dashed yellow oval. The diagram is labeled H.248.31\_F02. + +T\_O, T\_T, E\_O, E\_T are Termination IDs + +**Figure 2/H.248.31 – Two contexts in separate MGs** + +If a call traverses more than two MGs (refer to Figure 3), it might be desired to have different jitter buffer values (min/nominal/max) at each of the MGs depending on, for example, whether most of the jitter buffer is decided to be inserted at the end MGs (MG A and MG C), or if alternatively additional jitter buffer insertion is desired in the 'middle' MG (MG B). In this particular case, the + +MGC is the only network element capable of knowing that more than two MGs are involved in a call and, therefore, it is the only intelligent element in the network that will be able to set different jitter buffer sizes in the appropriate contexts. Additionally, the jitter buffer values will also depend on the delay variance introduced by the packet network that is being traversed. + +![Diagram of a call traversing three Media Gateways (MGs) controlled by a Media Gateway Controller (MGC).](007b053fe94a8348f75128a584503fd0_img.jpg) + +The diagram illustrates a call path through three Media Gateways (MGs): MG A, MG B, and MG C, all managed by a central Media gateway controller. The call originates from a TDM termination (T\_O) in MG A, which is part of Context C1. It then passes through an EPH (E\_O) in MG A to a Packet network. From the Packet network, it enters MG B through an EPH (E\_1), part of Context C2. It then passes through another EPH (E\_2) in MG B to another Packet network. From this second Packet network, it enters MG C through an EPH (E\_3), part of Context C3. Finally, it reaches a TDM termination (T\_T) in MG C. The EPHs in each MG are grouped by dashed yellow ovals. The label 'H.248.31\_F03' is present at the bottom right of MG C. + +Diagram of a call traversing three Media Gateways (MGs) controlled by a Media Gateway Controller (MGC). + +T\_O, E\_O, E\_1, E\_2, E\_3, T\_T are Termination IDs + +**Figure 3/H.248.31 – Call traversing three MGs** + +The insertion of jitter buffer would be on a per stream basis. A termination may have more than one stream, so a context may be a multi-stream context. Multiple terminations in a context (refer to Figure 4), and the streams associated with each termination, might require different jitter buffer settings depending on the end-to-end path in which that termination is involved in as well as the jitter buffers already present in that path. + +![Diagram of call traversing multiple MGs with a central MG having multiple terminations in a context. A Media gateway controller is at the top, connected by dashed lines to MG A, MG B, and MG C. MG A contains Context C1, Context C2, and Context C3. Context C1 has TDM and EPH terminations (T_O, E_O). Context C2 has EPH terminations (E_s, E_r). Context C3 has EPH and TDM terminations (E_r2, T_r). MG B contains Context C2 with EPH and TDM terminations (E_T, T_T). MG C contains Context C4 with TDM and EPH terminations (T_s, E_s2). Packet networks connect the MGs.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +The diagram illustrates a call path through multiple Media Gateways (MGs) controlled by a central Media gateway controller. MG A is the central hub, containing three contexts: Context C1, Context C2, and Context C3. Context C1 includes TDM and EPH terminations labeled T\_O and E\_O. Context C2 includes EPH terminations labeled E\_s and E\_r. Context C3 includes an EPH termination labeled E\_r2 and a TDM termination labeled T\_r. MG B, on the right, contains Context C2 with EPH (E\_T) and TDM (T\_T) terminations. MG C, on the left, contains Context C4 with TDM (T\_s) and EPH (E\_s2) terminations. Packet networks are shown connecting MG C to MG A and MG A to MG B. The label H.248.31\_F04 is present near MG B. + +Diagram of call traversing multiple MGs with a central MG having multiple terminations in a context. A Media gateway controller is at the top, connected by dashed lines to MG A, MG B, and MG C. MG A contains Context C1, Context C2, and Context C3. Context C1 has TDM and EPH terminations (T\_O, E\_O). Context C2 has EPH terminations (E\_s, E\_r). Context C3 has EPH and TDM terminations (E\_r2, T\_r). MG B contains Context C2 with EPH and TDM terminations (E\_T, T\_T). MG C contains Context C4 with TDM and EPH terminations (T\_s, E\_s2). Packet networks connect the MGs. + +T\_O, T\_T, T\_r, T\_s, E\_s, E\_s2, E\_r, E\_r2, E\_O, E\_T are Termination IDs + +**Figure 4/H.248.31 – Call traversing multiple MGs, with an MG having multiple terminations in a context** + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.32-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.32-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6519357069a7f363f9ea4e0901fac519467205d3 --- /dev/null +++ b/marked/H/T-REC-H.248.32-201303-I_PDF-E/raw.md @@ -0,0 +1,344 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.32** + +(03/2013) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Detailed congestion +reporting package** + +Recommendation ITU-T H.248.32 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.248.32 + +# Gateway control protocol: Detailed congestion reporting package + +## Summary + +This Recommendation defines a package that allows the media gateway (MG) to report the current state of its resource usage to the media gateway controller (MGC). The MGC can, according to its own capabilities, customize the set of resources reported as well as when the reports are provided. The resources that can be reported may be in the form of general resources and/or individual resources, and can represent either hardware or software resources. Based on the resource usage report received from the MG, the MGC may take corrective action to improve the efficiency of the whole system (e.g., re-route calls, reduce possible message intensive audits, throttle calls, etc.). + +In general, the precise definition of the following resources is left to implementation. The resources whose usage may be reported with this package include: + +- General Resources of the MG. This includes any resource that impacts the operation of the MG. For example, combined resources including memory and processor occupancy could be reported using this resource type. +- Digital Signal Processor (DSP) resources. These are resources that provide a variety of functionality for various packetized voice formats, echo cancellation, voice activity detection (VAD), comfort noise generation (CNG), jitter removal, tone generation/detection, etc. +- Internet Protocol (IP) resources that transport packets on an IP packet network. For example, this resource could describe the hardware used to provide terminations with the media address type of IPv4 or IPv6. +- Asynchronous Transfer Mode (ATM) resources that transport packets on an ATM packet network. For example, this resource could describe the hardware used to provide terminations with the media network type of ATM. +- Other resources mutually recognized by the MG and MGC. These resources are referred to as **extension resources** within this Recommendation. + +The MGC can customize the reporting of the MG's resource usage. The MGC can enable reporting for only those resources upon which it is capable of taking meaningful action. The MGC can also determine at what threshold level(s) the MG sends reports. The threshold levels are specified as a percentage of the resource used. The number of levels reported is also selectable. + +The reporting of different resource shortages will allow the MGC to take different preventive actions. + +This revision incorporates a correction to the Extension Resource text identities. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.248.32 | 2005-01-08 | 16 | +| 2.0 | ITU-T H.248.32 | 2013-03-16 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations..... | 1 | +| 5 Detailed congestion reporting package..... | 2 | +| 5.1 Properties..... | 2 | +| 5.2 Events ..... | 3 | +| 5.3 Signals ..... | 4 | +| 5.4 Statistics..... | 4 | +| 5.5 Error codes..... | 4 | +| 5.6 Procedures ..... | 4 | + + + +# Recommendation ITU-T H.248.32 + +## Gateway control protocol: Detailed congestion reporting package + +## 1 Scope + +This Recommendation defines a package that allows the media gateway (MG) to report its resource usage to the media gateway controller (MGC), and based on that report, the MGC may take corrective action to improve the efficiency of the whole system. The specific preventive action that the MGC takes in response to receiving a resource usage report is beyond the scope of this Recommendation. The support of this Recommendation is optional. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*. + +# 3 Definitions + +This Recommendation defines the following term: + +**3.1 extension resources:** Extension resources provide a way to extend this package. They represent media gateway resources, beyond those explicitly listed in this package, whose meanings are mutually understood (or recognized) by both the MG and the MGC. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|------------------------------| +| ATM | Asynchronous Transfer Mode | +| CNG | Comfort Noise Generation | +| CPU | Central Processing Unit | +| DSP | Digital Signal Processor | +| IP | Internet Protocol | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| VAD | Voice Activity Detection | +| VMG | Virtual Media Gateway | +| VoATM | Voice Over ATM | +| VoIP | Voice Over Internet Protocol | + +# 5 Detailed congestion reporting package + +**Package name:** Detailed Congestion Reporting +**Package ID:** dcr (0x0092) +**Description:** This package allows the MG to report its resource usage and the MGC based on that report to treat different types of calls differently and potentially re-route calls. This package is realized on the ROOT termination. +**Version:** 1 +**Extends:** None + +## 5.1 Properties + +### 5.1.1 Resources definitions + +**Property name:** General Resources +**Property ID:** gen (0x0001) +**Description:** Current usage level for general resources +**Type:** Integer +**Possible values:** Non negative percentage +**Default:** None +**Defined in:** TerminationState +**Characteristics:** Read + +The other properties of this package are defined in exactly the same way. Table 1 includes parameter names and parameter IDs. Note that each resource is defined as both a parameter and an enumeration. + +**Table 1 – Resource names** + +| Resource name | PropertyID/enumerationvalue | | +|-----------------------|------------------------------------|--------------------------| +| | Text identifier | Binary identifier | +| General resources | gen | 0x0001 | +| DSP resources | dsp | 0x0002 | +| IP resources | ip | 0x0003 | +| ATM resources | atm | 0x0004 | +| Reserved | | 0x0005 – 0x0020 | +| Extension resource 1 | ext1 | 0x0021 | +| Extension resource 2 | ext2 | 0x0022 | +| | ... | | +| Extension resource 32 | ext32 | 0x0040 | + +## 5.2 Events + +### 5.2.1 Congestion report + +**Event name:** Resource utilization reporting event +**Event ID:** conrep (0x0001) +**Description:** This event reports the current state of resource utilization within the media gateway. The event is reported either when a threshold is crossed or periodically. Periodic reporting may be provided in the absence of any change in threshold level if the optional report interval is specified. + +#### 5.2.1.1 EventsDescriptor parameters + +##### 5.2.1.1.1 Resource name + +**Parameter name:** Resource Name +**Parameter ID:** eresname (0x0001) +**Description:** The names of the resources that are to be reported using this request ID. +**Type:** Sub-list of Enumeration +**Optional:** No +**Possible values:** See Table 1 +**Default:** None + +##### 5.2.1.1.2 Reporting thresholds + +**Parameter name:** Reporting Thresholds +**Parameter ID:** rptthresh (0x0002) +**Description:** Sets the reporting thresholds for the resources listed in eresname. The reporting thresholds are specified as a percentage. The list of thresholds consists of a concatenation of thresholds for each resource. Each resource shall begin with a threshold of 0, indicating that a new resource is being specified. For example, the integer list "0 90 95 0 50 60 70" defines two sets of thresholds that correspond to the first two resources named in eresname: the first being 90% and 95%, and the second being 50%, 60% and 70%. If only a single set of thresholds is specified, then it applies to all the resources listed in eresname. +**Type:** Sub-list of integer +**Optional:** No +**Possible values:** Non negative percentage +**Default:** None + +##### 5.2.1.1.3 Report interval + +**Parameter name:** Report Interval +**Property ID:** rptint (0x0003) +**Description:** The periodic reporting interval in seconds for the resource usage information. A setting of 0 means that no periodic reporting is done. + +Periodic reporting is done in the absence of any change in threshold level. + +**Type:** Integer + +**Optional:** Yes + +**Possible values:** Non negative number of seconds + +**Default:** 0 + +#### 5.2.1.2 ObservedEventsDescriptor parameters + +##### 5.2.1.2.1 Resource name + +**Parameter name:** Resource Name + +**Parameter ID:** oeresname (0x0001) + +**Description:** The names of the resources that are being reported. + +**Type:** Sub-list of Enumeration + +**Optional:** No + +**Possible values:** See Table 1 + +**Default:** None + +##### 5.2.1.2.2 Resource usage + +**Parameter name:** Resource Usage + +**ParameterID:** resuse (0x0002) + +**Description:** The current usage level of the resources listed in oeresname. + +**Type:** Sub-list of Integer + +**Optional:** No + +**Possible values:** Non negative percentage + +**Default:** None + +## 5.3 Signals + +None. + +## 5.4 Statistics + +None. + +## 5.5 Error codes + +None. + +## 5.6 Procedures + +When this package is implemented, the MGC may enable events to report general resource utilization within the MG (for example, CPU utilization) and/or individual resource utilization within the MG (for example, IP/ATM resources, DSP resources, etc.). + +The MGC can also direct the MG, through the specification of a list of threshold levels, at what percentage values to report the resource usage. The threshold levels can be set individually for each resource. It is left to the MG to determine the meaning of general, DSP, IP and ATM resources used for calculating the level of the percentage used. For example, the MGC could request that the MG + + + + + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.33-200501-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.248.33-200501-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec9f2a57754ac08d5a057bce1536f8f84493c042 --- /dev/null +++ b/marked/H/T-REC-H.248.33-200501-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4575e49c8a5a1330eb904f2228171faeac6d5abfc58443cbfa6451f5518bd29 +size 5897 diff --git a/marked/H/T-REC-H.248.33-200501-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.248.33-200501-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9013c98ec21124d521267612ecd08d8780155acf --- /dev/null +++ b/marked/H/T-REC-H.248.33-200501-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:833b7c297a234d371ef9b21ec6a6bf772ff190b053f82ff17e2ac7abb76cf322 +size 105044 diff --git a/marked/H/T-REC-H.248.37-200806-I_PDF-E/raw.md b/marked/H/T-REC-H.248.37-200806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6afb54202c2b63b3e5f398c922206a13409b6aae --- /dev/null +++ b/marked/H/T-REC-H.248.37-200806-I_PDF-E/raw.md @@ -0,0 +1,902 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.37** + +(06/2008) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: IP NAPT traversal +package** + +Recommendation ITU-T H.248.37 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T H.248.37** + +# **Gateway control protocol: IP NAPT traversal package** + +## **Summary** + +Session border controllers (SBCs) are an important part of the Internet infrastructure. Some of these session border controllers are being split into media gateway controller (MGC) and media gateway (MG) components. One important function of an SBC is to perform network address and port translation (NAPT). This Recommendation allows the MGC to instruct an MG to latch to an address provided by an incoming Internet protocol (IP) application data stream rather than the address provided by the call/bearer control. This enables the MG to open a pinhole for data flow. + +This revision of Recommendation ITU-T H.248.37 adds clarifications for latch and re-latch behaviour and new packages for address reporting and statistics. + +## **Source** + +Recommendation ITU-T H.248.37 was approved on 13 June 2008 by ITU-T Study Group 16 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 1.1 Adaptation on new or changes of remote source address information..... | 1 | +| 1.2 Reporting of new or detected changes of remote address information ..... | 3 | +| 1.3 Counting the packets dropped based on implicit filtering..... | 4 | +| 2 References..... | 4 | +| 3 Definitions ..... | 4 | +| 3.1 Terms defined elsewhere ..... | 4 | +| 3.2 Terms defined in this Recommendation..... | 4 | +| 4 Abbreviations and acronyms ..... | 4 | +| 5 Conventions ..... | 5 | +| 6 IP NAPT traversal package ..... | 5 | +| 6.1 Properties ..... | 6 | +| 6.2 Events ..... | 6 | +| 6.3 Signals ..... | 6 | +| 6.4 Statistics..... | 6 | +| 6.5 Error codes..... | 6 | +| 6.6 Procedures ..... | 7 | +| 7 Address reporting package ..... | 12 | +| 7.1 Properties ..... | 12 | +| 7.2 Events ..... | 12 | +| 7.3 Signals ..... | 14 | +| 7.4 Statistics..... | 14 | +| 7.5 Procedures ..... | 14 | +| 8 Latch statistics package ..... | 15 | +| 8.1 Properties ..... | 15 | +| 8.2 Events ..... | 15 | +| 8.3 Signals ..... | 16 | +| 8.4 Statistics..... | 16 | +| 8.5 Error codes..... | 16 | +| 8.6 Procedures ..... | 16 | +| Appendix I – Temporary interruptions of IP connection..... | 17 | + + + +# Recommendation ITU-T H.248.37 + +## Gateway control protocol: IP NAPT traversal package + +# 1 Scope + +This Recommendation allows a media gateway controller to control Internet protocol (IP) network address and port translation (NAPT) traversal. + +## 1.1 Adaptation on new or changes of remote source address information + +The use of IP NAPT traversal (see clause 6) is especially useful in session border controllers (SBCs) where media traversal is required. + +Figure 1 illustrates a model for NAT traversal processing. The media gateway (MG) latches or re-latches, respectively, using the incoming H.248 stream (see termination T1). The peer IP connection endpoint is behind a NA(P)T device. + +![Figure 1 – Model for NAPT traversal processing. The diagram shows a Media Gateway Controller (MGC) connected to a Media Gateway (MG) via an H.248 Gateway Control Protocol. The MG has two terminations, T1 and T2. T1 is connected to an IP Domain 1 (e.g., public/global/external network) and T2 is connected to an IP or non-IP network. The MG contains IP Rx.MG and IP Tx.MG components. The IP Domain 1 contains a NAPT Device with components IP Tx., NAT.1, IP Rx., NAT.1, IP Tx., NAT.2, and IP Rx., NAT.2. The NAPT Device is connected to an IP Domain 2 (e.g., private/local/internal network). The IP Domain 2 contains an IP Connection Endpoint with components IP Tx.Host and IP Rx.Host. The diagram illustrates the flow of H.248 streams: Incoming Stream (DA = A1, SA = A2') from the IP Domain 1 to the MG, and Outgoing Stream (DA = A2', SA = A1) from the MG to the IP Domain 1. The NAPT Device translates these streams: Incoming Stream (DA = A2, SA = A1) from the IP Domain 2 to the MG, and Outgoing Stream (DA = A1, SA = A2) from the MG to the IP Domain 2. A note indicates that information exchange between the MGC and the other entities is out of scope. Another note states that one to N interim NA(P)T devices are modeled by a single entity.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) + +Media Gateway Controller (MGC) + +H.248 Gateway Control Protocol + +IP or non-IP network + +Media Gateway + +T2 T1 + +IP Rx.MG + +IP Tx.MG + +A1 + +IP Domain 1 + +e.g. public/global/external network (see clause 3.6/H.248.43) + +Incoming Stream: +DA = A1 +SA = A2' + +Outgoing Stream: +DA = A2' +SA = A1 + +NAPT Device + +IP Tx., NAT.1 + +IP Rx., NAT.1 + +IP Tx., NAT.2 + +IP Rx., NAT.2 + +A2' + +A1' + +IP Domain 2 + +e.g. private/local/internal network (see clause 3.5/H.248.43) + +IP Connection Endpoint + +IP Tx.Host + +IP Rx.Host + +A2 + +Incoming Stream: +DA = A2 +SA = A1 + +Outgoing Stream: +DA = A1 +SA = A2 + +Information exchange (if at all) between these entities is out of scope of this Recommendation. + +Note: One to N interim NA(P)T devices are modeled by a single entity. + +Figure 1 – Model for NAPT traversal processing. The diagram shows a Media Gateway Controller (MGC) connected to a Media Gateway (MG) via an H.248 Gateway Control Protocol. The MG has two terminations, T1 and T2. T1 is connected to an IP Domain 1 (e.g., public/global/external network) and T2 is connected to an IP or non-IP network. The MG contains IP Rx.MG and IP Tx.MG components. The IP Domain 1 contains a NAPT Device with components IP Tx., NAT.1, IP Rx., NAT.1, IP Tx., NAT.2, and IP Rx., NAT.2. The NAPT Device is connected to an IP Domain 2 (e.g., private/local/internal network). The IP Domain 2 contains an IP Connection Endpoint with components IP Tx.Host and IP Rx.Host. The diagram illustrates the flow of H.248 streams: Incoming Stream (DA = A1, SA = A2') from the IP Domain 1 to the MG, and Outgoing Stream (DA = A2', SA = A1) from the MG to the IP Domain 1. The NAPT Device translates these streams: Incoming Stream (DA = A2, SA = A1) from the IP Domain 2 to the MG, and Outgoing Stream (DA = A1, SA = A2) from the MG to the IP Domain 2. A note indicates that information exchange between the MGC and the other entities is out of scope. Another note states that one to N interim NA(P)T devices are modeled by a single entity. + +NOTE – The single H.248 stream at Termination T1 relates to the two IP flows of the bidirectional IP connection. + +Figure 1 – Model for NAPT traversal processing + +The network assumptions for H.248.37 are as follows: + +### [Assumption 1] IP host equipment + +In scope are translated transport addresses A2 to A2' by interim NAT devices. + +### [Assumption 2] Symmetry assumption for remote address A2 + +The remote IP connection endpoint is using symmetrical addresses (e.g., Figure 1: the network address and port values of $IP_{Tx,Host}$ and $IP_{Rx,Host}$ are identical). This symmetry condition is valid both for latching and address reporting. + +#### [Assumption 3] Dynamic of address changes + +The IP host does not change the transport address A2 during the lifetime of the IP transport connection. The host transport address A2 will be thus static and also not change during the lifetime of the H.248 stream/termination. + +NOTE 1 – IP host equipment with autonomous source port changes (e.g., due to security reasons) for the same transport connection (i.e., same application data stream) are therefore not considered here. In this context "autonomous" means that changes will not lead to any correspondent session control protocol (e.g., SIP) activity. + +#### [Assumption 4] MGC awareness concerning address changes + +An MGC using the *ipnapt* package is "aware" that there is a need for NAPT traversal support for the H.248 stream/termination. For this package, the MGC may not be aware of a) the translated transport address A2' by the NAPT device (Note 2), or b) the transport address changes by the IP endpoint after connection establishment. A consequence of this assumption is the fact that possible source address/port filtering by the MG is related to a static transport address A2, e.g., such a filter may not be autonomously adapted by the MG. + +NOTE 2 – This function is in the particular scope of the *adr* package (see clause 7). + +#### [Assumption 5] Validity of source endpoint address + +The MG is not aware of whether the source transport address (before or after latching) of the incoming stream represents a "valid" address (in the scope of that session). + +NOTE 3 – The MGC could check, based on the *adr* package, whether the latched source transport address is valid or unknown. + +The latch/re-latch process could be extended, e.g., by additional consideration of given destination transport address information (in the case that the MGC is unsure about a valid endpoint). Such a capability is for further study. + +NOTE 4 – There is a possible security problem. The use case of intentionally injected IP packets by an attacker with "his" source transport address may not be detected by the MG (in the scope of this Recommendation). + +#### [Assumption 6] MG awareness concerning transport protocol type + +The MG may be aware of or be agnostic of the *transport-protocol type* of the H.248 stream. This may depend, e.g., in case of IP-to-IP MGs on the configured interworking mode (see, e.g., clause 3.2.6 of [b-ITU-T Q.3303.2]). Nevertheless, the *ipnapt* package may be used for any type of transport protocol (e.g., UDP, TCP, SCTP, DCCP). + +#### [Assumption 7] IP connection establishment + +This may be relevant for *connection-oriented* IP transport protocols (such as TCP, SCTP, DCCP). The IP connection may be either "internally initiated" (the IP host in the internal network domain, i.e., relates to an "outgoing call") or "externally initiated" ("incoming call"). + +#### [Assumption 8] MGC/MG awareness concerning UNSAF processes + +This Recommendation is not related to unilateral self-address fixing (UNSAF; see [b-IETF RFC 3424] mechanisms like, e.g., STUN [b-IETF RFC 3489] or Teredo [b-IETF RFC 4380]). Support of UNSAF is FFS, e.g., in the future + +Recommendation ITU-T H.248.50 (UNSAF support could be, e.g., the support of UNSAF client or server functions by H.248 entities). + +The mechanism defined in this Recommendation is applicable to any IP data stream. It can be used for any type of UDP or TCP-based application-level framing protocol, for example: RTP/RTCP, T.38, MSRP, HTTP. + +### 1.1.1 Applicability statements (for IP NAPT traversal package) + +The IP NAPT traversal package version 1 supports: + +- the detection of the *used* remote source address/port and correspondent usage as destination address/port towards remote side, whereby the MGC enables LATCH mode; +- the detection of a *single* remote source address/port *change* and correspondent adaptation of the used destination address/port towards remote side, whereby the MGC must trigger each individual expected change via RELATCH mode; +- the implicit filtering of incoming packets so that only packets matching the detected address/port are admitted for further processing. + +The IP NAPT traversal package version 1 does *not* support + +- the *autonomous* detection of a *multiple* remote source address/port *changes* and correspondent adaptation of the used destination address/port towards remote side; + +NOTE 1 – Such a capability could be addressed by a new parameter for the latch signal. This is for further study. + +NOTE 2 – A potential use case could be a continuous re-latching mode for VoIP terminals, which apply frequent IP port changes (e.g., due to security reasons) during the lifetime of the bearer connection. + +- the automatic adaptation of any filtering rules created by other packages. + +### 1.1.2 Applicability statements concerning IP versions + +The packages of this Recommendation, the IP NAPT traversal package version 1, the address reporting package version 1, and the statistics package for discarded packets due to latching version 1, are all applicable for IPv4 and IPv6 protocol versions. + +### 1.1.3 Relation between packet filters and address latching + +For a particular termination/stream where latching is enabled, there may be an interaction between packet filters described in other Recommendations and the latching functionality described in this package. Such filters are, for instance, defined by [b-ITU-T H.248.43] (Note). In particular, the scope here is filter types with address-based policy rules. The conditions of such a filter type are based on a specific address/port value or a specific range of addresses/ports. If a filtering condition is specified for the incoming stream, the filtering is applied before latching, i.e., only packets that are permitted according to the filtering condition are considered for latching or re-latching. + +NOTE – Filters are typically strictly controlled by the MGC, e.g., SIP/SDP-signalled source filtering according to [b-IETF RFC 4570] would be first processed at the MGC level and, e.g., translated into a correspondent H.248.43 signalling. The transfer of RFC 4570 SDP "a=source-filter" attribute from the SIP/SDP to the H.248/SDP interface is possible in principle, but is not in scope of this Recommendation and [b-ITU-T H.248.43]. + +The relation between address latching and implicit packet filtering is described in clause 6.6.7. + +## 1.2 Reporting of new or detected changes of remote address information + +The address reporting package (see clause 7) may be optionally used in addition to the IP NAPT traversal package. The usage of this capability could be beneficial for the MGC in order to get the following information: + +- 1) *when* the event of address information changes occurred, if at all, i.e., when the MG successfully latched or re-latched respectively; or +- 2) *what* is the new address information; or +- 3) *both* (when and what). + +## 1.3 Counting the packets dropped based on implicit filtering + +The statistics package for discarded packets due to latching (see clause 8) may be optionally used with the IP NAPT traversal package. This package enables the MGC to retrieve the number of packets that were dropped based on the implicit filtering performed by the IP NAPT traversal package. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **network address translator:** [b-IETF RFC 2663]. +- 3.1.2 **symmetric NAT:** [b-IETF RFC 3489]. +- 3.1.3 **source filtering or ingress filtering:** [b-IETF RFC 3704]. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 latching:** Describes the process of an IP application endpoint (e.g., RTP) ignoring the remote IP address and port received from application session (endpoint) signalling (e.g., SIP/SDP, H.248/SDP, Q.1970, H.323) and returning the IP application data to the source IP address and port from the incoming data. + +**3.2.2 latching modes:** this Recommendation uses: "OFF mode" briefly for a latching signal attributed with parameter "napt = OFF"; "LATCH mode" briefly for a latching signal attributed with parameter "napt = LATCH", and "RELATCH mode" briefly for a latching signal attributed with parameter "napt = RELATCH". + +**3.2.3 pinhole:** A configuration of two associated H.248 IP terminations within the same context, which allows/prohibits unidirectional forwarding of IP packets under specified conditions (e.g., address tuple). + +NOTE – A pinhole may also be referred to as a "gate". + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------------------| +| CPE | Customer Premises Equipment | +| DA | Destination Address | +| DCCP | Datagram Congestion Control Protocol | +| DNS | Domain Name System | +| DP | Destination Port | +| FoIP | Facsimile-over-Internet Protocol | +| HTTP | Hypertext Transfer Protocol | +| IP | Internet Protocol | +| LD | Local Descriptor | +| MG | Media Gateway | +| MSRP | Message Session Relay Protocol | +| NAPT | Network Address and Port Translation | +| NAT | Network Address Translation | +| RD | Remote Descriptor | +| RTCP | Real-time Transport Control Protocol | +| RTP | Real-Time Protocol | +| RTSP | Real-Time Streaming Protocol | +| SA | Source Address | +| SBC | Session Border Controller | +| SCTP | Stream Control Transmission Protocol | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| SP | Source Port | +| STUN | Simple Traversal of User Datagram Protocol | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | +| UNSAF | UNilateral Self-Address Fixing | +| VoIP | Voice-over-IP | + +# 5 Conventions + +None. + +# 6 IP NAPT traversal package + +| | | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | IP NAPT Traversal Package | +| Package ID: | ipnapt (0x0099) | +| Description: | This package enables the MGC to instruct the MG to perform latching on a H.248 termination/stream for the purposes of IP NAPT traversal. | +| Version: | 1 | + +Extends: None + +## 6.1 Properties + +None. + +## 6.2 Events + +None. + +## 6.3 Signals + +### 6.3.1 Latch + +Signal Name: Latching + +Signal ID: latch (0x0001) + +Description: This signal orders NAPT traversal processing. + +Signal type: Brief + +The signal type may be basically overwritten in H.248 by the MGC, see clause 7.1.11 of [ITU-T H.248.1]: "*If the signal type is specified in a Signals Descriptor, it overrides the default signal type (see 12.1.4).*" Changing the signal type to timeout or on/off has only the effect of limiting the interval of time over which latching may occur. It does not result in multiple latching occurrences. + +Duration: Not applicable + +#### 6.3.1.1 Additional parameters + +##### 6.3.1.1.1 NAT processing + +Parameter name: NAPT Traversal Processing + +Parameter ID: napt (0x0001) + +Description: Instructs the MG to apply latching to the application data flows association with the termination/stream. In cases where multiple flows are associated with the H.248 stream (e.g., RTP and RTCP), the property is applied to all flows. The way of indicating multi-flow usage is out of the scope of this package. + +Type: Enumeration + +Optional: No + +Possible values: OFF [0x0000] + +LATCH [0x0001] + +RELATCH [0x0002] + +Default: OFF + +## 6.4 Statistics + +None. + +NOTE – See clause 8 concerning statistics for discarded packets due to latching. + +## 6.5 Error codes + +None. + +## 6.6 Procedures + +The NAT traversal processing signal allows the MG to be configured to support media flows that have passed through an unknown number of CPE or network-based NAT devices. + +### 6.6.1 NAPT traversal processing: 'OFF' mode + +When the NAPT processing signal *latch* with the parameter *napt* equal to OFF is sent to a termination/stream (see clause 6.6.4 for the case when the signal is NOT sent), then per default H.248.1 behaviour, the MG will use the IP address and port defined in the RemoteDescriptor for that termination/stream for sending application data. Figure 2 illustrates this behaviour. + +![Diagram illustrating NAT traversal processing OFF behaviour. A Media Gateway (MG) contains a Termination. An Incoming Stream from CPE_1 has Source Address CPE_1 and Destination Address MG_A. An Outgoing Stream to CPE_2 has Source Address MG_A and Destination Address CPE_2. The Local Descriptor points to Local Address MG_A. The Remote Descriptor points to Remote Address CPE_2. Dashed arrows show the mapping from descriptors to stream addresses.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +The diagram shows a Media Gateway (MG) with a Termination. An Incoming Stream from CPE\_1 has Source Address CPE\_1 and Destination Address MG\_A. An Outgoing Stream to CPE\_2 has Source Address MG\_A and Destination Address CPE\_2. The Local Descriptor points to Local Address MG\_A. The Remote Descriptor points to Remote Address CPE\_2. Dashed arrows show the mapping from descriptors to stream addresses. + +``` +graph TD + subgraph MG [Media Gateway (MG)] + T((Termination)) + LD[Local Descriptor] --> LA[Local Address = MG_A] + RD[Remote Descriptor] --> RA[Remote Address = CPE_2] + end + CPE1[CPE_1] -- "Incoming Stream
Source Address = CPE_1
Destination Address = MG_A" --> T + T -- "Outgoing Stream
Source Address = MG_A
Destination Address = CPE_2" --> CPE2[CPE_2] + LA -.-> CPE1 + RA -.-> CPE2 +``` + +Diagram illustrating NAT traversal processing OFF behaviour. A Media Gateway (MG) contains a Termination. An Incoming Stream from CPE\_1 has Source Address CPE\_1 and Destination Address MG\_A. An Outgoing Stream to CPE\_2 has Source Address MG\_A and Destination Address CPE\_2. The Local Descriptor points to Local Address MG\_A. The Remote Descriptor points to Remote Address CPE\_2. Dashed arrows show the mapping from descriptors to stream addresses. + +Figure 2 – NAT traversal processing OFF behaviour + +#### 6.6.1.1 Signal completion + +The 'latch' signal completes immediately. + +### 6.6.2 NAPT traversal processing: "LATCH" mode + +When the NAPT processing signal *latch* with the parameter *napt* equal to LATCH is sent to a termination/stream, this results in the MG ignoring the addresses received in the RemoteDescriptor. Instead, the MG will use the source address and source port from the incoming media stream (i.e., from the external device) as the destination address and destination port of the outgoing application data. Figure 3 illustrates this behaviour. + +![Diagram illustrating NAT traversal processing LATCH behaviour. A Media Gateway (MG) with a 'Termination' block is shown. An 'Incoming Stream' from 'CPE_1' has 'Source Address' and 'Destination Address = MG_A'. A dashed arrow points from this stream to a 'Local Descriptor' box containing 'Local Address = MG_A'. An 'Outgoing Stream' from the 'Termination' block has 'Source Address = MG_A' and 'Destination Address = CPE_1'. A dashed arrow points from this stream to a 'Remote Descriptor' box containing 'Remote Address = CPE_2', which is crossed out with an 'X'.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Diagram illustrating NAT traversal processing LATCH behaviour. A Media Gateway (MG) with a 'Termination' block is shown. An 'Incoming Stream' from 'CPE\_1' has 'Source Address' and 'Destination Address = MG\_A'. A dashed arrow points from this stream to a 'Local Descriptor' box containing 'Local Address = MG\_A'. An 'Outgoing Stream' from the 'Termination' block has 'Source Address = MG\_A' and 'Destination Address = CPE\_1'. A dashed arrow points from this stream to a 'Remote Descriptor' box containing 'Remote Address = CPE\_2', which is crossed out with an 'X'. + +**Figure 3 – NAT traversal processing LATCH behaviour** + +Latching is applicable only to the very first IP packet arrival event. The source address information of IP packets received afterwards will not be used for latching. After latching, packets received from any source address and port combination other than the latched one will be discarded and possibly counted; see clauses 6.6.7 and 8. + +#### 6.6.2.1 Packet sending process + +##### 6.6.2.1.1 SendOnly or SendReceive enabled before latching + +The IP termination is in 'OFF' mode before entering the 'LATCH' mode (due to default signal parameter value or signal parameter value set to "OFF"). In case of StreamMode settings set to SendOnly or SendReceive, packets will immediately be sent dependent on the availability of destination address information (IP DA, IP DP) according to the procedures of clause 6.6.1. + +##### 6.6.2.1.2 RecvOnly or Inactive before latching + +In all cases here, the initial StreamMode is "RecvOnly" or "Inactive". + +There are the following possibilities: + +- Underspecified RD without initial remote destination address information, but all other descriptor elements are available: + +Initially, no packets will be sent because the destination address information is not available and because they are restricted by the StreamMode settings. The first packet arrival event after enabling 'LATCH' will allow packet sending (dependent on StreamMode settings). + +- Still missing RD: + +Theoretically, there could already be IP packets sent after the first packet arrival event after enabling 'LATCH' (given that StreamMode settings have changed for sending). But this is questionable in practice due to potentially "meaningless IP packets" (e.g., still-missing correct media field, format list, etc.). + +Therefore, the packet sending process should be tightly coupled with the RD, i.e., the availability of all required information elements. + +- Initial signalled remote destination address information (in RD): + +The packet sending process will not be started as long as the initial StreamMode settings are not changed to a value of SendOnly or SendReceive. Nevertheless, the first packet + +arrival event after enabling 'LATCH' will overwrite the remote destination address (as received by the RD) with the latched address, independent of whether the H.248 signalled address information is equal to or unequal to the latched address information. + +#### 6.6.2.2 Signal completion + +A single H.248 stream of an H.248 IP termination may carry "multiple traffic flows", with the consequence of, e.g., multiple IP ports reserved, allocated and used. This scenario may be called "*multiple IP transport addresses per H.248 stream*", or briefly "multiple-flows-per-stream". There are thus two use cases concerning signal completion in 'LATCH' mode. + +##### 6.6.2.2.1 Single flow affected by signal + +For a termination/stream that contains a single flow, the 'latch' signal starts with its activation and completes with the *first packet arrival event*, i.e., independent of the StreamMode setting. The *signal completion termination method* shall indicate "TO" (see clause E.1.2.2 in [ITU-T H.248.1]) because the 'latch' signal completes on its own. + +##### 6.6.2.2.2 Multiple flows affected by signal + +For a termination/stream that contains multiple flows, the 'latch' signal starts with its activation and completes when *all flows* have experienced their first packet arrival events. The *signal completion termination method* shall indicate "TO". Where a notification completion is needed for each flow the MGC should set the *NotifyCompletion* parameter to "onIteration". + +### 6.6.3 NAT traversal processing: 'RELATCH' mode + +When the NAT traversal processing signal *latch* with the parameter *napt* equal to RELATCH is sent to a termination/stream, then the MG will perform a similar process to the latching process described in clause 6.6.2. The difference is that the MG will check for a *change* of source IP address/port on the *incoming* media stream. If/when a new source IP address and/or port are detected, they will then be used as the destination address and port for future outgoing packets. After re-latching, packets received from any source address and port combination other than the latched one will be discarded and possibly counted; see clauses 6.6.7 and 8. Note that packets arriving from the old source address and port fall under this condition and will also be discarded. + +The packet sending process in 'RELATCH' mode, before and after successful re-latching, has again the two dependencies on: + +- available destination address information (IP DA, IP DP), and +NOTE – Information is implicitly available after re-latching and may be available before the re-latching event, dependent on RD settings. +- StreamMode settings. + +See clause 6.6.2.1 for further details. + +Application of 'RELATCH' mode does not imply a previous 'LATCH' mode. New IP terminations may therefore be initially enabled with the 'RELATCH' mode by the ADD.request command. + +#### 6.6.3.1 Signal completion + +There are again two use cases concerning signal completion (see also 'LATCH' mode). + +##### 6.6.3.1.1 Single flow affected by signal + +Re-latching is limited to the first IP packet arrival event, whereby the received packet has different source address information to the current source address information in use. The 'brief' signal is consequently 'active' as long as no source address differences are detected. + +##### 6.6.3.1.2 Multiple flows affected by signal + +For a termination/stream that contains multiple flows, the 'relatch' signal starts with its activation and completes when *all flows* have experienced their first packet arrival events with different source address information. The 'brief' signal is consequently 'active' *on an individual flow* as long as no source address differences could be detected. + +Where a notification completion is needed for each flow, the MGC should set the *NotifyCompletion* parameter to "*onIteration*". + +### 6.6.4 A signal descriptor missing the *ipnapt/latch* signal + +The MGC may, when modifying a stream, send a signals descriptor without the *ipnapt/latch* signal. Such a modification will stop any currently active *ipnapt/latch* signal (i.e., the MG will not update the destination of sent packets based on received ones). However it will not cause any change to the destination towards which packets are currently being sent. If, before this modification, the MG was sending packets towards a latched address; it will continue doing so. This is a major difference between a missing *ipnapt/latch* signal; and an *ipnapt/latch* signal with *latch=OFF* (see clause 6.6.1). + +### 6.6.5 Usage of signal 'latch' together with event 'signal completion' + +The signal completion event *g/sc* is defined in clause E.1.2.2 of [ITU-T H.248.1]. This event may be applied together with signal 'latch', but is meaningless in 'OFF' mode. + +#### 6.6.5.1 Recommendations for 'LATCH' and 'RELATCH' mode + +The generic event *g/sc*, associated to signal *latch*: + +- could be useful for MGCs which are interested in successful (or unsuccessful) latching occurrences; +- is basically not required for the application of *ipnapt* package; +- if requested by the MGC, the signal completion event would be returned when packets are received according to the latching process (e.g., MG detects a packet coming from a different address for the particular stream). The signal completion event would be returned irrespective of the address in the RD. + +Details concerning the time when the *latch* signal completes are given in clauses 6.6.2.2 and 6.6.3.1. The MGC may ask for the address information that the MG is using as a result of the latch process by usage of the *adr* package, see clause 7. + +### 6.6.6 Usage of signal 'latch' together with signal parameter 'KeepActive' + +The *KeepActive* flag could be principally combined with signal *latch* (in new signals descriptor), see clause 7.1.11 of [ITU-T H.248.1]. The *KeepActive* flag is required to support the following use case. + +The MGC starts the (re-)latching process by including the signal *latch* within the signals descriptor. If, later on, the MGC modifies the ephemeral termination signals descriptor, the MGC has to keep the signal *latch* within the signals descriptor (*in order to avoid the signal being stopped if it had not completed*) (see procedure according to clause 6.6.4) and to add the *KeepActive* flag to avoid that the signal *latch* is activated again. + +It has to be noted that the use of the *KeepActive* flag is only needed if the MGC has not received the *g/sc* or *adr/rtac* events from the MG at the time of sending a new signals descriptor. If latching has been performed, and the event was received by the MGC, there is no need to include the signal again in the signals descriptor as it will not fall back to the initial RD settings. + +### 6.6.7 Packet filtering guidelines + +#### 6.6.7.1 Implicit filtering + +After a flow has undergone latching, the latching function will implicitly filter incoming packets based on the results of the latching process. Only packets whose source address and port match the latched ones will be admitted for further processing. + +The MG shall stop applying the above implicit filtering once the MGC activates an *ipnapt/latch* signal that affects the flow (regardless of the latching mode). If, due to this new signal, the flow latches again, implicit filtering is then re-activated and only packets matching the newly latched address and port are admitted. + +Consider, for example, a single-flow stream on which the MGC activates the *ipnapt/latch* signal using the LATCH mode. If the first packet received on that stream arrives from 128.64.32.4:5004, the flow will latch to this transport address. From that point on, the latching function will only admit packets arriving from this address and port for further processing. This implicit filtering will stop once the MGC again activates the *ipnapt/latch* signal on the stream. + +#### 6.6.7.2 Statistics for discarded packets + +There is an extension package with an explicit statistic for counting discarded packets due to latching, see clause 8. + +#### 6.6.7.3 Interaction with explicit filtering rules + +Explicit packet filtering rules (defined by other packages) may be applied to a flow on which latching is enabled. Such filters are defined, for instance, by [b-ITU-T H.248.43]. + +In order to determine the behaviour of an MG with regard to the processing of incoming packets, the following principles should be followed: + +- Any filter conditions based on protocol elements at layer 4 or below shall be applied *before* the packet is processed by the latching function. +- Any filter conditions including protocol elements residing above layer 4 shall be applied *after* the packet is processed by the latching function. + +Note that the above rules mean that all filtering properties defined by [b-ITU-T H.248.43], with the exception of upper layer protocol type mask, shall be applied before the latching function. + +For example, consider a single-flow stream on which latching is enabled and whose H.248.43 *gm/sam* property is set to allow the range of IP addresses defined by *gm/sam*="[128.64.32.0]/24". Latching will only occur on the first packet received from that specific range. A packet arriving from an address outside this range (e.g., 128.76.19.4) will be dropped by the filter before being processed by the latching function; and therefore will not cause the flow to latch. + +Only packets matching the explicit filtering rules will be processed by the latching function. Therefore, the address allowed by the latching function's implicit filter (according to clause 6.6.7.1) will always be allowed by the explicit filtering rules as well. + +#### 6.6.7.4 Update of explicit filtering rules + +Theoretically, the MG might be able to autonomously update the explicit filtering rules using the information of the implicit filtering described in clause 6.6.7.1. However, the current version of the *ipnapt* package does *not* support any method allowing the MG to do so. There is consequently no direct interaction between the *ipnapt* package and any package used for defining explicit filtering rules. + +# 7 Address reporting package + +Package name: Address Reporting Package + +Package ID: adr (0x00ac) – value allocated by IANA. + +Description: This package may be applied together with the *ipnapt* package for IP address latching. This package defines complementary event and property, which allows the MG to report the detected new remote network address and port, i.e., the remote transport address. + +NOTE – The remote IP network element might be: a) a remote IP connection endpoint; or b) a remote NA(P)T device, see also Figure 1. The transport addresses of the remote source and remote destination endpoints are symmetrical in case b, which must not be the case for a. This package specification uses the network model of b, also because *adr* is an extension package of the *ipnapt* base package (see also assumption 2 in clause 1.1). + +Version: 1 + +Extends: *ipnapt*, <0x0099> version 1 + +## 7.1 Properties + +### 7.1.1 Current remote transport address value + +Property name: Current Remote Transport Address Value + +Property ID: crta (0x0001) + +Description: This property provides the current value with regard to the remote IP address and port used, for the particular IP flow within an H.248 stream. The value is either still unknown, or given as a result of latching or re-latching. + +The property could be useful for auditing purposes of the MGC. + +NOTE – This protocol element is complementary to the observed events parameter. An MGC may use this property without subscribing for event *adr/rtac*, or may just use the event and not the property, or may use both. + +Type: Sub-list of String + +The sub-list contains exactly one element for every flow included in the H.248 stream. Each element is formatted according to the *nrta* ObservedEventsDescriptor parameter of the *rtac* event (see clause 7.2.1.2.1). + +Possible values: See clause 7.2.1.2.1 + +Default: None + +Defined in: LocalControl + +Characteristics: ReadOnly + +## 7.2 Events + +### 7.2.1 Remote transport address change + +Event name: Remote Transport Address Change + +Event ID: *rtac* (0x0003) + +Description: This event will occur when the remote transport address for the termination has changed. Its parameter is the new detected (latched) network address and transport port information. + +NOTE – IP transport address is comprised of the 2-tuple of network address and transport port. + +#### 7.2.1.1 EventsDescriptor parameters + +None. + +#### 7.2.1.2 ObservedEventsDescriptor parameters + +##### 7.2.1.2.1 Detected address/port + +Parameter name: New Remote Transport Address + +Parameter ID: nrta (0x0001) + +Description: Indicates the current connection state with regard to the remote IP address port used. + +Type: String + +Optional: No + +Possible values: A string having the format of: + +groupID "|" flowType "|" connectionAddress ":" port + +Where: + +- "|" and ":" are literals functioning as separators +- groupID is + - semantic: the H.248 group number (if ReserveGroup is used), otherwise this element is equal to 1. + - syntax: as per UINT16 in clause B.2 of [ITU-T H.248.1]. +- flowType is + - semantic: a numeric identifier of the flow within the stream. + - a) For a stream that contains a single flow, the flowType is equal to 1. + - b) For a stream that contains both RTP and RTCP, the RTP flow has a flowType of 1; and the RTCP flow has a flowType of 2. + - c) For streams that contain a different combination of flows, the mapping between these flows may be provisioned in the MGC and MG. + - syntax: as per UINT16 in clause B.2 of [ITU-T H.248.1]; Integer. +- connectionAddress is + - semantic: the 32-bit or 128-bit address in the IPv4 or IPv6 header of the received IP packet. + +NOTE – The IP version is implicitly given by the value encoding. + - syntax: as per domainAddress in clause B.2 of [ITU-T H.248.1]. + +- port is + - semantic: the 16-bit source port number in the layer 4 header of the received IP packet, possible values are thus 0 to 65535. + - syntax: as per portNumber (i.e., UINT16) in clause B.2 of [ITU-T H.248.1]. + +**Default:** None + +## 7.3 Signals + +None. + +## 7.4 Statistics + +None. + +## 7.5 Procedures + +### 7.5.1 Termination type check + +The event *rtac* is only applicable for ephemeral terminations with either IP version 4 (IPv4) or IP version 6 (IPv6) protocol versions. Any event arming attempt by the MGC for a different termination type shall be replied by the MG with an error code #440 (unsupported or unknown package). + +### 7.5.2 Reporting address changes + +The MGC may activate the address reporting capability by enabling the *rtac* event. This is typically done together (i.e., in the same command request) with the activation of latching or re-latching through the *ipnapt/latch* signal. + +If the *rtac* event is active, the MG will generate a separate notification towards the MGC each time a single flow successfully latches or re-latches. For each such event, the *nrta* ObservedEventsDescriptor parameter includes information about the newly latched address. If an H.248 stream contains more than one flow, this behaviour will lead to more than one notification being sent on that stream following a single activation of the *ipnapt/latch* signal. In the general case, these notifications will be sent in different notify requests, as each flow may latch at a different point in time. + +#### 7.5.2.1 Associating the *rtac* event to a stream + +For the information provided by the *rtac* event to be meaningful, the MGC must be able to associate it with a specific H.248 stream. Therefore, the MG shall include in every *rtac* notification the standard StreamID ObservedEventDescriptor parameter. This is done regardless of whether the *rtac* event was armed on a specific stream or on the complete termination. + +#### 7.5.2.2 Encoding examples + +##### 7.5.2.2.1 Text encoding + +Example 1 – Single, IPv4, non-RTP flow in an H.248 stream: + +``` +adr/rtac{nrta="1|1|[11.9.19.65]:2000", Stream=1} +``` + +Example 2 – Single, IPv6, non-RTP flow in an H.248 stream: + +``` +adr/rtac{nrta="1|1|[1965:9:11:800:200C:417A]:1234", Stream=3} +``` + +Example 3 – IPv4, RTP and RTCP flows in an H.248 stream: + +``` +adr/rtac{nrta="1|1|[10.10.10.65]:2000", Stream=2}, ; RTP +adr/rtac{nrta="1|2|[10.10.10.65]:2001", Stream=2} ; RTCP +``` + +Example 4 – Two streams, each containing IPv6 RTP and RTCP flows and a third stream containing an IPv6 non-RTP flow (one stream for 'audio', one for 'video', and one for 'video control'): + +``` +adr/rtac{nrta="1|1|[8002::1]:28740", Stream=1}, ; RTP for audio +adr/rtac{nrta="1|2|[8002::1]:28741", Stream=1}, ; RTCP for audio +adr/rtac{nrta="1|1|[8002::1]:28768", Stream=2}, ; RTP for video +adr/rtac{nrta="1|2|[8002::1]:28769", Stream=2}, ; RTCP for video +adr/rtac{nrta="1|1|[8002::1]:28770", Stream=3} ; RTSP for video +``` + +##### 7.5.2.2.2 Binary encoding + +None. + +### 7.5.3 Auditing current available remote source transport address values + +The remote addresses that are used by the different flows as a result of latching can be audited through the *crta* property. The value of this property is a list containing exactly one item for every flow of the relevant H.248 stream. Each of these items is a string using the syntax of the *nrta* parameter of the *rtac* event. + +Once latching has occurred on a specific flow, the relevant *crta* item will contain the latched remote transport address (i.e., the item will be identical to the *nrta* parameter that would have appeared in the *rtac* notification following the latching). + +If the *crta* property is audited before a flow has latched, or after an *ipnapt/latch* with *napt* equal to OFF was applied to the flow, the relevant item will contain the following information: + +- *connectionAddress* is all zeroes: 0.0.0.0 for IPv4 and 0::0 for IPv6. +- *port* is zero. + +NOTE – IPv6 address 0::0 is defined in [b-IETF RFC 4291] as the unspecified address, and may not be assigned to an IPv6 node. Therefore, this value can represent an unknown address. IPv4 address 0.0.0.0, while not formally defined as the unspecified address, is non-routable according to [b-IETF RFC 1812]. Therefore, this value can represent an unknown address. + +# 8 Latch statistics package + +Package name: Latch statistics package + +Package ID: lstat (0x00E4) + +Description: This package complements the IP NAPT traversal package to enable the recording of discarded packets due to implicit filtering by the latching function. + +Version: 1 + +Extends: *ipnapt* version 1 + +## 8.1 Properties + +None. + +## 8.2 Events + +None. + +## **8.3 Signals** + +None. + +## **8.4 Statistics** + +### **8.4.1 Discarded packets due to latching** + +Statistic name: Discarded Packets + +Statistic ID: dp (0x0001) + +Description: Contains the number of discarded packets due to implicit filtering by the latching function. + +Type: Double (unit is "packets") + +Possible values: Any positive number including zero + +Level: Stream (or termination) + +## **8.5 Error codes** + +None. + +## **8.6 Procedures** + +The statistic is used for recording the number of discarded packets due to implicit filtering of the latching function. See also clause 6.6.7.2. + +# **Appendix I** + +## **Temporary interruptions of IP connection** + +(This appendix does not form an integral part of this Recommendation) + +Modes "LATCH" and "RELATCH" will be applied for the local IP terminations due to unknown or changing source address and/or source port of the remote IP side. Such changes of IP addresses may lead to temporary interruptions of the IP bearer connection. There is a short-term period, starting with the event of an address change at the remote side, the corresponding MGC control for enabling LATCH/RELATCH mode, till the adaptation of the MG for the new remote address. + +There could be consequently a short series of egress IP packets with the old or incorrect address, which may not reach the remote side. Quantitative performance estimations concerning the duration of connection interruption are out of scope of this Recommendation. + +# Bibliography + +- [b-ITU-T H.248.43] Recommendation ITU-T H.248.43 (2008), *Gateway control protocol: Packages for gate management and gate control*. +- [b-ITU-T H.323] Recommendation ITU-T H.323 (2006), *Packet-based multimedia communications systems*. +- [b-ITU-T Q.1970] Recommendation ITU-T Q.1970 (2006), *BICC IP bearer control protocol*. +- [b-ITU-T Q.3303.2] Recommendation ITU-T Q.3303.2 (2007), *Resource control protocol No. 3 – Protocol at the interface between a Policy Decision Physical Entity (PD-PE) and a Policy Enforcement Physical Entity (PE-PE) (Rw interface): H.248 alternative*. +- [b-ITU-T T.38] Recommendation ITU-T T.38 (2007), *Procedures for real-time Group 3 facsimile communication over IP networks*. +- [b-IETF RFC 1812] IETF RFC 1812 (1995), *Requirements for IP Version 4 Routers*. +<> +- [b-IETF RFC 2663] IETF RFC 2663 (1999), *IP Network Address Translator (NAT) Terminology and Considerations*. +<> +- [b-IETF RFC 3424] IETF RFC 3424 (2002), *IAB Considerations for UNilateral Self-Address Fixing (UNSAF) Across Network Address Translation*. +<> +- [b-IETF RFC 3489] IETF RFC 3489 (2003), *STUN – Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)*. +<> +- [b-IETF RFC 3704] IETF RFC 3704 (2004), *Ingress Filtering for Multihomed Networks*. +<> +- [b-IETF RFC 4291] IETF RFC 4291 (2006), *IP Version 6 Addressing Architecture*. +<> +- [b-IETF RFC 4380] IETF RFC 4380 (2006), *Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)*. +<> +- [b-IETF RFC 4570] IETF RFC 4570 (2006), *Session Description Protocol (SDP) Source Filters*. +<> + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.41-201511-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.248.41-201511-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7 --- /dev/null +++ b/marked/H/T-REC-H.248.41-201511-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055 +size 6859 diff --git a/marked/H/T-REC-H.248.41-201511-I_PDF-E/raw.md b/marked/H/T-REC-H.248.41-201511-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7a705640645248501b36cd45fcafc493bf4ef63f --- /dev/null +++ b/marked/H/T-REC-H.248.41-201511-I_PDF-E/raw.md @@ -0,0 +1,416 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.41** + +(11/2015) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: IP domain connection +package** + +Recommendation ITU-T H.248.41 + +**ITU-T** + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "ITU" is written in a large, bold, blue font, and below it, "International Telecommunication Union" is written in a smaller, blue font. + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'. + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.248.41 + +## Gateway control protocol: IP domain connection package + +## Summary + +Recommendation ITU-T H.248.41 defines certain parameters and mechanisms for supporting the interconnection of a packet network with another network. It is only applicable to the IP-based ITU-T H.248 termination and provides such information as the IP Realm Identifier used to indicate to which packet network the media represented by the termination belongs. + +Amendment 1 to the first edition introduced mechanisms that allow the media gateway controller to discover the IP realms that are available at the media gateway at a certain time. It also introduced a length limitation in the IP realm property. + +The second edition removed the package extension in the IP Realm Availability package in order to resolve a property identity conflict. + +This revision revises the IP domain connection package to allow multiple realms to be specified in the IP Realm Identifier property. This allows the usage of the property when the ReserveGroup/ReserveValue mechanism is used to specify different transports. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.248.41 | 2006-05-29 | 16 | 11.1002/1000/8820 | +| 1.1 | ITU-T H.248.41 (2006) Amd. 1 | 2008-06-13 | 16 | 11.1002/1000/9477 | +| 2.0 | ITU-T H.248.41 | 2013-03-16 | 16 | 11.1002/1000/11860 | +| 3.0 | ITU-T H.248.41 | 2015-11-29 | 16 | 11.1002/1000/12626 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 1.1 Specifying the IP realm of an ITU-T H.248 stream ..... | 1 | +| 1.2 Auditing the MG supported realms and their availability ..... | 1 | +| 2 References..... | 1 | +| 3 Terms and definitions ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 IP Domain Connection Package ..... | 2 | +| 5.1 Properties ..... | 2 | +| 5.2 Events ..... | 3 | +| 5.3 Signals ..... | 3 | +| 5.4 Statistics..... | 3 | +| 5.5 Error Codes..... | 3 | +| 5.6 Procedures ..... | 3 | +| 6 IP Realm Availability package ..... | 4 | +| 6.1 Properties..... | 4 | +| 6.2 Events ..... | 4 | +| 6.3 Signals ..... | 5 | +| 6.4 Statistics..... | 5 | +| 6.5 Error codes..... | 5 | +| 6.6 Procedures ..... | 5 | + + + +# Recommendation ITU-T H.248.41 + +## Gateway control protocol: IP domain connection package + +# 1 Scope + +This Recommendation defines packages and mechanisms for supporting the interconnection of a packet network with another network. The packages defined by this Recommendation are only applicable to IP-based ITU-T H.248 terminations. The packages are therefore applicable for: + +- IP-to-IP ITU-T H.248 media gateways, and +- IP-to-non-IP ITU-T H.248 media gateways. + +## 1.1 Specifying the IP realm of an ITU-T H.248 stream + +The media gateway controller (MGC) may specify the IP realm/s that a stream of a particular ITU-T H.248 termination belongs to. This is accomplished through the IP Realm Identifier property of the IP Domain Connection package. + +## 1.2 Auditing the MG supported realms and their availability + +### 1.2.1 Auditing all supported realms + +The MGC can audit the realms supported by the MG (i.e., all realms that the MG is aware of) by using an AuditCapabilities on the IP Realm Identifier property of the IP Domain Connection package. + +### 1.2.2 Understanding the availability of realms + +The IP Realm Availability package extends the IP Domain Connection package. Through an AuditValue of this package's Available Realms property, the MGC is able to learn which of the supported realms is currently available (i.e., over which realms the MG can currently send and receive traffic). Similarly, the MGC may request to be notified of changes to the list of available realms through the Available Realms Changed event of the same package. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*. + +[IETF RFC 1123] IETF RFC 1123 (1989), *Requirements for Internet Hosts – Application and Support*. + +<> + +[IETF RFC 2663] IETF RFC 2663 (1999), *IP Network Address Translator (NAT) Terminology and Considerations*. + +<> + +# 3 Terms and definitions + +This Recommendation defines the following terms: + +**3.1 IP address realm or IP realm:** Is defined in [IETF RFC 2663], clause 2.1, as a network domain in which the network addresses are uniquely assigned to entities such that datagrams can be routed to them. Routing protocols used within the network domain are responsible for finding routes to entities given their network addresses. + +**3.2 realm availability** (from MG perspective): Realm availability means connectivity on the IP layer to a particular realm. Connectivity implies that the MG joins the realm (i.e., network address(es) from that realm are used for ITU-T H.248 IP stream/terminations) and that at least one IP route is available towards another IP node (e.g., IP router, IP host, ITU-T H.248 media gateway) of that realm. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|------------------------------| +| IP | Internet Protocol | +| IPv4 | Internet Protocol Version 4 | +| IPv6 | Internet Protocol Version 6 | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| SDP | Session Description Protocol | + +# 5 IP Domain Connection Package + +| | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | IP Domain Connection Package | +| Package ID: | ipdc (0x009d) | +| Description: | This package defines certain parameters and mechanisms for supporting the interconnection of a packet network with another network. | +| Version: | 2 | +| Extends: | None | + +## 5.1 Properties + +### 5.1.1 IP Realm Identifier + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------| +| Property name: | IP Realm Identifier | +| Property ID: | realm (0x0001) | +| Description: | This property is used to indicate to which packet network the media represented by the termination belongs. | +| Type: | Sub-list of String | + +**Possible values:** String + +Length limitation: Where the IP Realm Identifier property uses a domain name format, it shall handle domain names of up to 63 characters and should handle domain names of up to 255 characters in accordance with clause 2.1 of [IETF RFC 1123]. + +There shall be a maximum of two values in the sub-list. + +NOTE 1 – When there are two values, then the two IP realms use different IP versions. + +**Default:** Provisioned between the MGC and the MG. + +**Defined in:** LocalControl + +NOTE 2 – When there are two values, then the H.248 Stream Descriptor also contains two ITU-T H.248 media groups (clause 7.1.7.1.2 of [ITU-T H.248.1]). The media group SDP "c="-line element provides the binding between IP realm identifier and associated ITU-T H.248 media group. + +**Characteristics:** Read/Write + +## 5.2 Events + +None. + +## 5.3 Signals + +None. + +## 5.4 Statistics + +None. + +## 5.5 Error Codes + +None. + +## 5.6 Procedures + +The value of the IP Realm Identifier property is a string, which may be in a domain name format, e.g., "mynet.net", or any other string format. In case the MGC uses an *ipdc/realm* property exceeding the above defined length limitation, the MG shall reply with an error descriptor using error code #449: "Unsupported or Unknown Parameter or Property Value". + +Typically an ITU-T H.248 stream belongs to a single IPv4 or IPv6 domain and thus a single IP realm value is used. However, in some scenarios an ITU-T H.248 Stream may belong to both IPv4 and IPv6 domains. In this case, multiple media connection addresses and ports are specified through the use of the ITU-T H.248 *ReserveValue/ReserveGroup* mechanism. Multiple IP realm values are specified in the *ipdc/realm* property in the order of the reserved values/reserved groups. I.e., if the first group contains an IPv6 address and the second contains an IPv4 address then the first value in the *ipdc/realm* property will relate to IPv6 and the second value will relate to IPv4. + +The IP Realm Identifier should be provisioned between the MGC and the MG. Each of the different IP realms possibly interconnecting with an MG should have a different identifier. The MGC and the MG can provision a default IP realm and configure it on the MG. If the MGC sends a command to the MG to create an IP-based ITU-T H.248 termination without the IP Realm Identifier property, the MG will consider it as indicating the default realm. + +If the value of the IP Realm Identifier property sent by the MGC cannot be recognized by the MG, the MG will fail to create the IP-based ITU-T H.248 termination and return the corresponding error code to the MGC, e.g., 449 (Unsupported or Unknown Parameter or Property Value). + +Performing an AuditCapabilities of the *ipdc/realm* property on the root termination returns all realms defined in the MG, being available or not. Performing an AuditValue of the *ipdc/realm* property on an IP termination returns the IP realm that the termination is currently connected to. + +# 6 IP Realm Availability package + +| | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------| +| Package name: | IP Realm Availability | +| Package ID: | ipra (0x00e0) | +| Description: | This package defines a new root property and a new root event to enable a discovery mechanism for IP realm availability. | +| Version: | 1 | +| Extends: | None. | + +## 6.1 Properties + +### 6.1.1 Available Realms + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Available Realms | +| Property ID: | ar (0x0001) | +| Description: | This property lists the IP realms which are currently available for usage on request by the MGC. It is applicable on Root terminations only. | +| Type: | Sub-list of String | +| Possible values: | Strings mutually understood by MG and MGC and which are also addressable through the ipdc/realm property. | +| Default: | None | +| Defined in: | TerminationState | +| Characteristics: | ReadOnly | + +## 6.2 Events + +### 6.2.1 Available Realms Changed + +| | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------| +| Event name: | Available Realms Changed | +| Event ID: | arc (0x0001) | +| Description: | This event indicates that the availability of realms in the MG has changed. It is applicable on Root terminations only. | + +#### 6.2.1.1 EventsDescriptor parameters + +None. + +#### 6.2.1.2 ObservedEventsDescriptor parameters + +##### 6.2.1.2.1 Newly Available Realms + +| | | +|------------------------|------------------------| +| Parameter name: | Newly Available Realms | +| Parameter ID: | nar (0x0001) | + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------| +| Description: | This parameter gives the list of realms that were previously unavailable and are now available. | +| Type: | Sub-list of String | +| Optional: | Yes | +| Possible values: | Strings mutually understood by MG and MGC and which are also addressable through the ipdc/realm property. | +| Default: | None | + +##### 6.2.1.2.2 Newly Unavailable Realms + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Newly Unavailable Realms | +| Parameter ID: | nur (0x0002) | +| Description: | This parameter gives the list of realms that were previously available and are now unavailable. | +| Type: | Sub-list of String | +| Optional: | Yes | +| Possible values: | Strings mutually understood by MG and MGC and which are also addressable through the ipdc/realm property. | +| Default: | None | + +## 6.3 Signals + +None. + +## 6.4 Statistics + +None. + +## 6.5 Error codes + +None. + +## 6.6 Procedures + +### 6.6.1 Auditing available realms + +For MGs supporting the package, an MGC can discover the available realms in an MG by auditing the root property "Available realms" (*ipra/ar*) with the AuditValue command. The audit can be performed after Control Association (re-)establishment and provides the information about available realms. + +An MGC that wishes to discover all realms defined in the MG should perform an AuditCapabilities of the *ipdc/realm* property on the root termination. An AuditCapabilities of the *ipra/ar* property should be avoided since in theory it would return all possible subsets of the set of realms defined in the MG, as each subset is a possible value of the *ipra/ar* property. An MG receiving an AuditCapabilities command on the *ipra/ar* property may send an error reply, e.g., 501 "Not implemented". + +### 6.6.2 Notification of realm changes + +To enable an MG to inform an MGC about changes to the set of available realms, the MGC may arm the "Available Realms Changed" event (*ipra/arc*) on root. This allows the MG to dynamically inform + +the MGC about changes which occur in the set of available realms, e.g., due to management actions or network interruptions. + +Each "Available Realms Changed" notification may include two ObservedEvents parameters: + +- "Newly Available Realms", which lists the realms that have become available. +- "Newly Unavailable Realms", which lists the realms that have become unavailable. + +Each of these parameters may be omitted only if the relevant list is empty (hence, an *ipra/arc* notification must always include at least one parameter). The change reported by these two lists relates to the realms' availability at the time of the last *ipra/arc* notification or the time when the *ipra/arc* event was last armed (whichever is later). + +The MGC must know the realms initially available in order for it to make use of the information provided by the *ipra/arc* event. A possible way of doing so is by auditing the current value of the *ipra/ar* property using the same Modify request that arms the *ipra/arc* event. + + + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.44-200701-I_PDF-E/raw.md b/marked/H/T-REC-H.248.44-200701-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b383c093bbbbbf9d5d87e505d77585fc1d945da0 --- /dev/null +++ b/marked/H/T-REC-H.248.44-200701-I_PDF-E/raw.md @@ -0,0 +1,309 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.44** + +(01/2007) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Multi-level +precedence and pre-emption package** + +ITU-T Recommendation H.248.44 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Gateway control protocol: Multi-level precedence and pre-emption package** + +## **Summary** + +This Recommendation defines a package to provide signals and procedures necessary to realize multi-level precedence and pre-emption applications under H.248. While bandwidth and overload control, as well as judicious use of the Priority and Emergency ContextAttributes go a long way toward achieving these goals, existing systems also utilize tonal signals to inform end-users about the nature of the traffic, whether their current call is being pre-empted and whether or not their origination is being treated as priority traffic. These systems find a wide range of applications, including military command and control, government priority traffic and many disaster recovery and relief efforts. Priority traffic control and pre-emption are especially important in the time span immediately following a disaster when communications resources may be scarce. + +###### **Source** + +ITU-T Recommendation H.248.44 was approved on 13 January 2007 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2007 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|--------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations..... | 1 | +| 5 Conventions ..... | 1 | +| 6 Multi-level Precedence and Pre-emption Package ..... | 1 | +| 6.1 Properties..... | 2 | +| 6.2 Events ..... | 2 | +| 6.3 Signals ..... | 2 | +| 6.4 Statistics..... | 3 | +| 6.5 Procedures ..... | 3 | +| Bibliography..... | 6 | + + + +# ITU-T Recommendation H.248.44 + +# Gateway control protocol: Multi-level precedence and pre-emption package + +# 1 Scope + +This Recommendation defines a package that provides signals for use with precedence features, such as those used by military, government and disaster recovery applications. The support of this package is optional. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] ITU-T Recommendation H.248.1 (2005), *Gateway control protocol: Version 3*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 precedence:** The assignment of a priority level to a call. + +**3.2 pre-emption:** The seizing of resources which are in use by a call of a lower precedence by a higher level precedence call in the absence of idle resources. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +eMLPP enhanced Multi-level Precedence and Pre-emption Service + +IEPS International Emergency Preference Scheme + +MG Media Gateway + +MGC Media Gateway Controller + +MLPP Multi-level Precedence and Pre-emption + +# 5 Conventions + +*None.* + +# 6 Multi-level Precedence and Pre-emption Package + +Package Name: Multi-level Precedence and Pre-emption Package + +Package ID: prectn (0x009f) + +Description: This package defines signals and procedures for use with precedence and pre-emption features, such as those used by military, government and disaster recovery applications. + +Version: 1 + +Extends: None + +## 6.1 Properties + +*None.* + +## 6.2 Events + +*None.* + +## 6.3 Signals + +### 6.3.1 Preset Conference Notification Tone + +Signal Name: Preset Conference Notification Tone + +Signal ID: preconf (0x0001) + +Description: Generate preset conference notification tone, indicating that some conferees have not yet entered the conference. The physical characteristic of preset conference notification tone is available in the gateway. + +Signal Type: Brief + +Duration: Provisioned + +Additional parameters: None + +### 6.3.2 Preset Conference Precedence Notification Tone + +Signal Name: Preset Conference Precedence Notification Tone + +Signal ID: pcprec (0x0002) + +Description: Generate preset conference precedence notification tone, which is a provisionable alternative to the preset conference notification tone. The physical characteristic of preset conference precedence notification tone is available in the gateway. + +Signal Type: Brief + +Duration: Provisioned + +Additional parameters: None + +### 6.3.3 Precedence ringing tone + +Signal Name: Precedence Ringing Tone + +Signal ID: precrt (0x0003) + +Description: Generate precedence ringing tone, indicating that the call has importance above that of normal calls. The physical characteristic of precedence ringing tone is available in the gateway. + +Signal Type: TimeOut + +Duration: Provisioned + +Additional parameters: None + +### 6.3.4 Pre-emption tone + +Signal Name: Pre-emption Tone +Signal ID: preempt (0x0004) +Description: Generate pre-emption tone, indicating that the call is being pre-empted for traffic of higher importance. The physical characteristic of pre-emption tone is available in the gateway. +Signal Type: Brief +Duration: Provisioned +Additional parameters: None + +## 6.4 Statistics + +*None.* + +## 6.5 Procedures + +[ITU-T H.248.1] defines the Priority ContextAttribute as an integer taking a value 0-15, with 15 being the highest and 0 being the lowest priority. It also defines two ContextAttributes, Emergency and IEPS, which allow the MGC to mark a context as being used for the purposes of emergency or IEPS calls, respectively. + +To date, there has been no formal definition of what a particular priority value means, or what the impact of the Emergency or IEPS ContextAttributes are on the priority value. [ITU-T H.248.11] makes use of priority to help in ameliorating overflow at the MG, but no indication as to what a particular priority value really means has been documented. + +In the function of MLPP, particular calls are defined as being more important than other calls and are designated with named levels. These vary from network to network and from application to application. Table 1 provides several defined priority schemas. This does not imply any linkage between different schemas and is only provided as an informal survey of different priority schemas and their definitions. Please see the appropriate definition specifications to determine interaction requirements for a particular schema. + +**Table 1 – Existing priority schemas and algorithms** + +| Priority | DSN/I.255.3 | DRSN | Q.735.3 | ETS | WPS | eMLPP | +|-----------------------------------------------------------------------------------------------------------------------------|----------------|----------------------------------|-------------|------------------|------------------|------------| +| Highest
downward arrow
Lowest | Flash-Override | Flash-Override-Override (Note 1) | 0 | 0 | 0 | A (Note 2) | +| | Flash | Flash-Override | 1 | 1 | 1 | B (Note 2) | +| | Immediate | Flash | 2 | 2 | 2 | 0 | +| | Priority | Immediate | 3 | 3 | 3 | 1 | +| | Routine | Priority | 4 | 4 | 4 | 2 | +| | | Routine | | | | 3 | +| | | | | | | 4 | +| MLPP policy | Pre-emption | Pre-emption | Pre-emption | Priority Queuing | Priority Queuing | Both | + +NOTE 1 – Flash-Override-Override displaces existing calls, but once established becomes a Flash-Override call for the purposes of future pre-emptive calls. + NOTE 2 – A and B are only used on the local switch. For interswitch calls, A and B are treated as 0. + +In addition to these, one has to consider the possibility that a provider has defined a "less-than-routine" call service level. This could be a lesser guaranteed level of service in exchange for reduced tariffs, for example. While not common in the PSTN today, it is possible in H.248 networks and has to be considered in the scope of the priority discussion overall. + +In order to account for all these schemas, it is difficult to classify a particular schema as more or less important as another schema. Largely, these schemas operate on different networks (military or government networks, as opposed to the PSTN for example) and there is no need to identify how a particular schema aligns with another schema. + +In terms of H.248, pre-emption is the act of forcibly removing terminations in order to free up facilities for another higher-precedence call. This allows the seizing of call/bearer resources which are in use by a call of a lower precedence by a higher level precedence call in the absence of idle resources. + +Ultimately, the decision that a particular call is more important than another is the domain of the MGC. The Priority, IEPS and Emergency ContextAttributes are useful in allowing the MG to decide which calls to accept and which to reject in the case of overload control. Further, it allows the MG to perform dynamic resource allocation to ensure that a particular portion of its resources are available to handle higher priority calls that may come later. The priority designation and MLPP functionality are handled completely within the MGC, and any indication to the MG is secondary to the actual execution of the MLPP functions. + +As indicated in Table 1, there are two common algorithms, namely, pre-emption and priority queuing. It is conceivable that both algorithms could be present in the same network. The algorithms are presented here for informational purposes: + +### **Pre-emption** + +Schemas using a pre-emption policy may disrupt an existing call to make room for a higher-priority incoming call. Since calls may require different amounts of bandwidth or a different number of circuits, a single higher-priority call may displace more than one lower-priority call. + +### **Priority queuing** + +In a priority queuing policy, calls that find no available resources are queued to the queue assigned to the priority value. Unless otherwise specified, calls are queued in first-come, first-served order. Each priority value may have its own queue, or several priority values may share a single queue. If a resource becomes available, the MGC reattempts the call from the highest-priority non-empty queue according to the queue service policy. For first-come, first-served policies, the call from that queue that has been waiting the longest is served. Each queue can hold a finite number of pending calls. If the per-priority-value queue for newly arriving calls is full, the MGC may deny handling for the call immediately. + +In addition, a priority queuing policy may impose a waiting time-limit for each priority class, whereby setup times that exceed a specified waiting time are ejected from the queue and the call is deemed to have failed. + +Finally, the MGC may impose a global queue size limit summed across all queues and drop waiting lower-priority calls attempts. This does not imply pre-emption, since the call was not previously established. + +## Bibliography + +- [b-ITU-T H.460.14] ITU-T Recommendation H.460.14 (2004), *Support for Multi-Level Precedence and Preemption (MLPP) within H.323 systems.* +- [b-ITU-T I.255.3] ITU-T Recommendation I.255.3 (1990), *Community of interest supplementary services: Multi-level precedence and preemption service (MLPP).* +- [b-ITU-T Q.735.3] ITU-T Recommendation Q.735.3 (1993), *Stage 3 description for community of interest supplementary services using Signalling System No. 7: Multi-level precedence and preemption.* +- [b-ETSI TS 124.067] ETSI TS 124.067 (2005), *Enhanced Multi-Level Precedence and Preemption service (eMLPP) – Stage 3.* +- [b-IETF RFC 4411] IETF RFC 4411 (2006), *Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events.* +- [b-IETF RFC 4412] IETF RFC 4412 (2006), *Communications Resource Priority for the Session Initiation Protocol (SIP).* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.45-200605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.45-200605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/H/T-REC-H.248.45-200605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/H/T-REC-H.248.45-200605-I_PDF-E/65550960f5c5afd9d27706aaeddb0638_img.jpg b/marked/H/T-REC-H.248.45-200605-I_PDF-E/65550960f5c5afd9d27706aaeddb0638_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a4dafb8266744e51a2653990fc2e24d3b077c33 --- /dev/null +++ b/marked/H/T-REC-H.248.45-200605-I_PDF-E/65550960f5c5afd9d27706aaeddb0638_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fea8b9d315c6596b93ac32c02dac8ae1bf806950e7abf2d560d4b7a6136f5a72 +size 34548 diff --git a/marked/H/T-REC-H.248.46-200701-I_PDF-E/raw.md b/marked/H/T-REC-H.248.46-200701-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0eab625b94fdd6f4d2c12842e2201e5a44efd1bd --- /dev/null +++ b/marked/H/T-REC-H.248.46-200701-I_PDF-E/raw.md @@ -0,0 +1,395 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.46** + +(01/2007) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Connection capability +control package** + +ITU-T Recommendation H.248.46 + +**ITU-T** + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a blue globe with white latitude and longitude lines, with a red lightning bolt striking across it from the bottom left to the top right. The letters "ITU" are superimposed in blue on the globe. To the right of the globe, the text "International Telecommunication Union" is written in blue. + +ITU logo + +**International +Telecommunication +Union** + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.248.46** + +# **Gateway control protocol: Connection capability control package** + +## **Summary** + +MGCs and MGs employ different methods to control the MG internal connections. An MG may save transcoding resources by autonomously connecting the terminations in the same MG but different contexts directly to each other. However, in some special applications (e.g., test) this autonomous behaviour may not be desired. Not all MGs support this autonomous behaviour, nor do they all support terminations being connected internally. Such a mix of behaviour leads to interoperability issues. + +This Recommendation contains a H.248 package to determine the MG internal connection capability and to set the appropriate MG internal connection behaviour where necessary. + +## **Source** + +ITU-T Recommendation H.248.46 was approved on 13 January 2007 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2007 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 3 | +| 3 Definitions ..... | 3 | +| 3.1 Terms defined elsewhere ..... | 3 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 4 | +| 5 Convention..... | 4 | +| 6 Termination connection model package..... | 4 | +| 6.1 Properties..... | 4 | +| 6.2 Events ..... | 5 | +| 6.3 Signals ..... | 5 | +| 6.4 Statistics..... | 5 | +| 6.5 Error codes..... | 5 | +| 6.6 Procedures ..... | 6 | +| Bibliography..... | 9 | + + + +# **Gateway control protocol: Connection capability control package** + +# **1 Scope** + +This Recommendation defines a package that allows a MGC to determine and control whether the MG allows the application of optimization mechanisms with regard to efficiency maximization of MG data-path resources, and/or optimization of QoS/performance metrics (e.g., MG transfer delay, speech quality, etc.), to the MG internal connection. + +Dedicated MGC implementations may not resolve cascaded contexts, therefore would benefit from using this package to determine if MGs are capable of this behaviour. MG may then simplify the internal connection of intentionally created and connected contexts in series under strict control of the MGC. + +The data path is the path that data flows from the ingress side to the egress side of the user plane which connects the two participants of a call. It is the MG's physical implementation of the abstract H.248 connection model. When the ingress and the egress are on the same MG, it is known as the "Internal connection". + +This is illustrated in a 2-termination single context configuration, where termination A is a TDM termination with G.711 encoded and termination B is an IP/RTP termination G.723.1 encoded; the data path may include the following steps: + +- 1) E1/T1 decoding (media stream taken from correct timeslot); +- 2) Transport conversion (e.g., TDM to packet); +- 3) G.711 decoding; +- 4) G.723.1 encoding; +- 5) RTP encoding; +- 6) IP packetization; +- 7) IP packet routing. + +Such a configuration results when a TDM call is received on a MGC/MG and the destination of the call is on another MGC/MG, and the connection between these is IP based. + +However, the data path in a MG is not constrained to a single context/termination configuration. If for example the TDM call is received and the destination (also TDM) of the call is on the same MG (a separate MGC may control this), then the data path will be extended as such: + +- 1) E1/T1 decoding (media stream taken from correct timeslot); +- 2) Transport conversion (e.g., TDM to packet); +- 3) G.711 decoding; +- 4) G.723.1 encoding; +- 5) RTP encoding; +- 6) IP packetization; +- 7) IP packet routing; +- 8) IP packet reception; +- 9) IP un-packetization; +- 10) RTP decoding; +- 11) G.723.1 decoding; + +- 12) G.711 encoding; +- 13) Transport conversion (e.g., packet to TDM); +- 14) E1/T1 encoding (media stream sent to correct timeslot). + +The additional steps (8-14) are largely the inverse of the previous steps (1-7) and as such cancel each other out. In order to optimize the data path, the MG could perform step (1) and (14) and successfully have media flow between the originator and the destination of the call. + +For each of these steps, the MG may have an internal means of addressing the function that performs the appropriate step. This is NOT the same address as any of those used by the H.248 connection model, but will be derived from the model. The MG can use these internal addresses to perform optimizations. The MG-internal connection optimization may be based on connection information given by termination/context data and/or other internal resource usage data, but do not require call related information like call control information from analog line signalling (Annex E.9 of [ITU-T H.248.1]) or channel associated signalling ([ITU-T H.248.25], [ITU-T H.248.28], [ITU-T H.248.29]) or DCME signalling ([ITU-T H.248.42]) or detected Digit strings (in case of enabled DigitMaps). That means for instance, MG-internal connection optimization is not using address information from call/session control signalling. However, it is not in the scope of this Recommendation to describe how the MG-internal data path is addressed or how this is derived from the H.248 connection model as these are MG implementation/hardware specific. + +As the H.248 connection model does not directly operate on the data path but by abstraction, the MG is responsible for determining the optimization mechanisms that may be applied to the data path. As such this package is also applicable for terminations with associated bearer control protocols (BCP) like Q.2630.x signalling for AAL2 terminations or [ITU-T Q.1970]/[ITU-T Q.1990] for IP terminations. (Termination-associated) BCPs could for instance delay internal connection optimizations, but this package may be in general also applied for such kind of terminations. + +In order to facilitate data-path optimization, this Recommendation defines a H.248 package in order to determine the MG internal connection capability and to set the appropriate MG internal connection behaviour (Notes 1 and 2). Whilst the properties of the package may apply to all termination types, the optimizations that can be performed are data-path dependent. + +NOTE 1 – Only MG-internal connections are considered. That means that the only MG external connections loops that can be realized internally to the MG are optimized. Example of MG external connections loop: Context Cid1 with Tid1(type 'S') and Tid2(type 'IP') and 2nd context Cid2 with Tid3(type 'IP') and Tid4(type 'S'), and IP source/destinations addresses of Tid2 and Tid3 are so, that there would be an IP bearer connection between Tid2 and Tid3. + +NOTE 2 – There are specific connection models with explicit internal terminations, e.g., cascaded context model according to clause 13.7.5 of [b-ETSI TS 123 205]. There are consequently MG internal connections established (there are three in the Multi-Party supplementary service example of [b-ETSI TS 123 205]). Such specific context models could benefit from this package, i.e., are also in the scope of this Recommendation. + +This package may be used by physical MGs (PMG) which utilize the VMG concept. According to H.248.1 procedures, there is one control association between a MGC and VMG; thus the use of the package is for a single VMG instance. However there may be multiple MGCs controlling VMGs in a single PMG. In case of multiple VMGs, there may be a superior instance on the PMG level having knowledge about resource information and usage of all VMGs (instantiated on PMG). Such a function would be then associated with this package, but the function itself is out of scope of this Recommendation. In this case, data-path optimizations may occur across VMGs according to the internal connection capability and internal connection behaviour properties associated with each of the VMGs. For example, if a PMG discovers that a data path occurs across two of its VMGs and their associated contexts and these contexts are allowed to be optimized, then the PMG may optimize the path across both VMGs. However, if the contexts on one of the VMGs were marked that optimizations were not allowed then, only the path on the other VMG may be optimized. + +Parallel operation of multiple profiles per PMG or VMG, with different support of this package in each profile, is principally possible, but MAY affect the degree of application of this package. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] ITU-T Recommendation H.248.1 (2005), *Gateway control protocol: Version 3*. +- [ITU-T H.248.25] ITU-T Recommendation H.248.25 (2007), *Gateway control protocol: Basic CAS packages*. +- [ITU-T H.248.28] ITU-T Recommendation H.248.28 (2007), *Gateway control protocol: International CAS packages*. +- [ITU-T H.248.29] ITU-T Recommendation H.248.29 (2005), *Gateway control protocol: International CAS compelled register signalling packages*. +- [ITU-T H.248.42] ITU-T Recommendation H.248.42 (2006), *Gateway control protocol: DCME interworking package*. +- [ITU-T Q.1970] ITU-T Recommendation Q.1970 (2006), *BICC IP bearer control protocol*. +- [ITU-T Q.1990] ITU-T Recommendation Q.1990 (2001), *BICC bearer control tunnelling protocol*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **ADD.req** [ITU-T H.248.1]: H.248.1 Add command request +- 3.1.2 **MOD.req** [ITU-T H.248.1]: H.248.1 Modify command request +- 3.1.3 **MOV.req** [ITU-T H.248.1]: H.248.1 Move command request +- 3.1.4 **AuditCapability.req** [ITU-T H.248.1]: H.248.1 AuditCapability command request +- 3.1.5 **AuditCapability.rep** [ITU-T H.248.1]: H.248.1 AuditCapability command reply + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +- 3.2.1 **internal connection**: The direct collection/linkage of resources in a MG between the ingress and the egress of a user plane data which connects the two participants of a call. An "internal connection" is there the intra-MG connection segment from an end-to-end (user plane) connection perspective. +- 3.2.2 **autonomous behaviour**: The ability of a MG to perform media/data path optimization for H.248 connections without the MGC performing optimizations of the media/data path through manipulation of the MG-internal H.248 connection configuration. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|----------------------------------------------------------| +| AAL2 | Asynchronous Transfer Mode (ATM) Adaptation Layer type 2 | +| BCP | Bearer Control Protocol | +| Cid | Context Identifier | +| DCME | Digital Circuit Multiplication Equipment | +| DTMF | Dual-Tone Multi-Frequency | +| E1 | Electrical interface signal, Level 1, (2.048 Mbit/s) | +| IP | Internet Protocol | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| PMG | Physical Media Gateway | +| QoS | Quality of Service | +| RTP | Real-time Transport Protocol | +| T1 | Digital Signal Level 1 at 1544 kbit/s | +| TDM | Time Division Multiplexing | +| Tid | Termination Identifier | +| VMG | Virtual Media Gateway | + +# 5 Convention + +None. + +# 6 Termination connection model package + +| | | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | Connection capability control package | +| Package ID: | ccc, 0x00ad | +| Description: | This package defines properties for determining the internal connection capability on a particular MG. Once the connection capability is determined, the MGC may utilize the appropriate control method. | +| Version: | 1 | +| Extends: | None | + +## 6.1 Properties + +### 6.1.1 Connection capability + +| | | +|----------------|------------------------------------------------------------------| +| Property name: | Connection capability | +| Property ID: | cc, 0x0001 | +| Description: | This property indicates the MG's internal connection capability. | +| Type: | Enumeration | + +Possible values:    "*Controlled*" which indicates the internal connection is determined and controlled by the MGC. +                          "*Autonomous*" which indicates the internal connection is determined and controlled by the MG. +                          "*Invalid*" which indicates the internal connection is non-supported by the MG. +Default:                Provisioned +Defined in:            TerminationState and only for Root Termination +Characteristics:    ReadOnly + +### **6.1.2   Enable autonomy** + +Property name:    Enable autonomy +Property ID:           ea, 0x0002 +Description:           Where autonomous internal connection is supported by the MG, this property enables or disables this autonomous capability. +Type:                      Boolean +Possible values:    "*On*" which to enable the autonomous internal connection capability. +                          "*Off*" which to disable the autonomous internal connection capability. +Default:                "*On*" +Defined in:            ContextAttribute +                          NOTE – The property is defined on context level in order to respect different call types. +Characteristics:    Read/Write + +## **6.2    Events** + +None. + +## **6.3    Signals** + +None. + +## **6.4    Statistics** + +None. + +## **6.5    Error codes** + +None. + +## 6.6 Procedures + +### 6.6.1 General + +When a 2-party-call is routed through a network at each MGC, the call is routed through a context with two terminations created in the corresponding MG. This can result in chains of MGs (contexts) being connected. However, situations exist where one PMG may contain two or more contexts involved in the call. This may lead to various MG internal connection architectures. For example: + +- 1) **Controlled model:** The MGC determines that the caller side and the callee side are in the same MG and directly requests the MG to add the two terminations into one context, as follows: + +![Diagram of the Controlled model showing the MGC and MG components and their interaction.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +The diagram illustrates the Controlled model. On the left, a box labeled 'MGC' contains an oval context 'C1' with two circular terminations 'Ta' and 'Tb' connected by a double-headed arrow. A large arrow points to the right, where a box labeled 'MG' contains the same context 'C1' with terminations 'Ta' and 'Tb'. Below the MG box, a 'Caller' box has an arrow pointing to 'Ta', and a 'Callee' box has an arrow pointing to 'Tb'. A small label 'H.248.46(01-07)\_F01' is at the bottom right. + +Diagram of the Controlled model showing the MGC and MG components and their interaction. + +**Figure 1 – Controlled model** + +- 2) **Autonomous model:** The MGC does not determine whether the caller side and the callee side are in the same MG. The MGC requests the MG to create a context for caller and the callee respectively, i.e., two contexts (one per call leg) and each context contains two terminations. The MG then determines that these two contexts are in the same MG and directly connects the two subscriber terminations (caller side and callee side), as follows: + +![Diagram of the Autonomous model showing the MGC and MG components and their interaction.](853f59c89931a666c07903b31d098277_img.jpg) + +The diagram illustrates the Autonomous model. On the left, a box labeled 'MGC' contains two ovals: context 'C1' with terminations 'Ta' and 'Ta'', and context 'C2' with terminations 'Tb'' and 'Tb'. Arrows show 'Ta' connecting to 'Caller' and 'Tb' connecting to 'Callee' outside the MGC box. A large arrow points to the right, where a box labeled 'MG' contains both contexts 'C1' and 'C2'. Inside the MG, the 'Caller' box connects to 'Ta' and the 'Callee' box connects to 'Tb'. A direct double-headed arrow connects 'Ta'' in 'C1' to 'Tb'' in 'C2'. A small label 'H.248.46(01-07)\_F02' is at the bottom right. + +Diagram of the Autonomous model showing the MGC and MG components and their interaction. + +**Figure 2 – Autonomous model** + +- 3) **Invalid model:** The MG cannot support the direct connection in a MG between the ingress and the egress of a user plane data which connects the two participants of a call (i.e., internal connection). In Figure 2, the data flowing between 'Ta'' and 'Tb'' would be routed externally to the MG. The MG would send the data and then later receive the data. + +To determine the connection model that a MG supports, the MGC should perform a H.248 AuditCapability.req command on the MG's root termination, with property *connection capability* (cc) to determine the internal connection capabilities. It is expected that the MG will be provisioned with the internal connection capabilities it supports. The reply is given in an AuditCapability.rep. The MG may return both "*Controlled*" and/or "*Autonomous*" if the internal connection is supported, or "*Invalid*" if the internal connection is non-supported. The value "*Invalid*" shall not be returned in combination with "*Controlled*" or "*Autonomous*" (or both). + +Based on the results of this audit, the MGC should consider this information and the application requirements and then decide which connection model it shall use. For example, for a test call where measurements are being taken, it may be decided not to optimize the internal connection, in times of high MG resource utilization the MGC may decide to optimize internal connections and for legal intercept calls, optimization may be turned off. If the MGC takes advantage of the Autonomous model, it may subsequently decide on a per call basis to disable the MG's autonomous internal connection capability. If the MGC wishes to disable the autonomous connection capability, it shall send the *enable autonomy* (ea) property to the MG indicating "*Off*" in an ADD.req, MOD.req or MOV.req. This will have the effect of turning off the autonomous internal connection capability when providing for such special applications as loop-back test. + +### 6.6.2 Statistic descriptor interaction + +The use of statistics should be an input into the MG decision to optimize the data path. For example: + +In the case of connecting Context 1 {Termination A(TDM[b-ITU-T G.711]), Termination B (IP[b-ITU-T G.723.1])} to Context 2 { Termination C(IP[b-ITU-T G.723.1]), Termination D(TDM[b-ITU-T G.711])}. + +If the Network package statistics were placed on the TDM terminations, the MG could still optimize the data path by effectively removing the IP segments. However, in the case that the RTP statistics were requested for the IP terminations, then the data path MAY not be fully optimized. MAY is used as for instance when the MG could be intelligent enough not to perform transcoding between G.723.1 and G.711 but use RTP to transfer packets. Another solution MAY be that the MGC could accept the RTP statistics unchanged or ineffectual if the MG removes the IP segments. + +The general rule is if the MG cannot provide the statistic values, then the data path resource should not be optimized. If the MGC does require no optimization, then the *enable autonomy* (ea) property shall be set to "*Off*". + +### 6.6.3 Event descriptor interaction + +The setting of events should be an input into the MG decision to optimize the data path. The general rule is that the resource used to detect a set event should not be optimized out of the data path. There are exceptions where due to a data-path optimization a set event becomes superfluous, in these cases the event may be optimized out of the data path. + +For example: Given a TDM1-RTP1-RTP2-TDM2 connection scenario. If the Quality Alert Event (clause E.11.2.2 of [ITU-T H.248.1]) is set on RTP1, then the data path for RTP1 and RTP2 may be optimized because if the RTP segment is removed the Quality Alert Event would never be reported because there would never be a low quality connection. However, if DTMF tone detection (clause E.6 of [ITU-T H.248.1]) is set on RTP1, then the data path could not be optimized because the MGC would be expecting the MG to detect DTMF digits and if this was optimized out then digits sent from the RTP2/TDM2 would be missed. + +If the MGC does require no optimization, then the *enable autonomy* (ea) property shall be set to "*Off*". + +### 6.6.4 Topology descriptor interaction + +The package may be in principle also applied for contexts using the topology descriptor. When the MGC performs a topology request, it shall also set *enable autonomy (ea)* property to "Off". This is to minimize data-path optimization interactions. + +### 6.6.5 Command interaction + +If the data path has been optimized, a subsequent Modify or Move command may introduce a new resource that may need to be included into the data path. In this case, the MG should determine whether the optimized data path can be retained with this new resource or an "un-optimized" path needs to be created in order to be inserted. A Modify or Move command may also remove a resource from the data path. Again the MG should determine whether the removal of the resource affects the data path. For instance: if the resource has already been optimized out then there may be no impact; however, in some cases such as the removal of a termination may remove resources already optimized but it also removes a connection. In the case of a Move command optimization should be applied to the new context according to the *enable autonomy (ea)* property. + +# Bibliography + +- [b-ITU-T G.711] ITU-T Recommendation G.711 (1988), *Pulse code modulation (PCM) of voice frequencies*. +- [b-ITU-T G.723.1] ITU-T Recommendation G.723.1 (2006), *Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s*. +- [b-ETSI TS 123 205] ETSI TS 123 205 v6.7.0 Release 6 (2006), *Technical Specification Group Core Network; Bearer Independent CS Core Network; Stage 2*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.47-200807-I_PDF-E/raw.md b/marked/H/T-REC-H.248.47-200807-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..56075ad7afbb94fada7a8c9fafdc85127acbec84 --- /dev/null +++ b/marked/H/T-REC-H.248.47-200807-I_PDF-E/raw.md @@ -0,0 +1,523 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.47** + +(07/2008) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Statistic conditional +reporting package** + +Recommendation ITU-T H.248.47 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global communication. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T H.248.47** + +# **Gateway control protocol: Statistic conditional reporting package** + +## **Summary** + +Recommendation ITU-T H.248.47 defines a H.248 package with a generic method of reporting when statistics meet a pre-defined condition. Enabling the reporting of statistics allows the media gateway controller (MGC) to better manage resources, particularly in the areas of charging and quality of service. + +This version of this Recommendation allows an MGC to control whether a timestamp is reported with the detection of the events in this package. It also extends the reporting conditions with value-based metric conditions. + +###### **Source** + +Recommendation ITU-T H.248.47 was approved on 22 July 2008 by ITU-T Study Group 16 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|-----|-----------------------------------------------|---| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations..... | 1 | +| 5 | Conventions ..... | 1 | +| 6 | Statistic Conditional Reporting Package ..... | 2 | +| 6.1 | Properties..... | 2 | +| 6.2 | Events ..... | 2 | +| 6.3 | Signals ..... | 6 | +| 6.4 | Statistics..... | 6 | +| 6.5 | Error Codes..... | 6 | +| 6.6 | Procedures ..... | 6 | + + + +# Recommendation ITU-T H.248.47 + +## Gateway control protocol: Statistic conditional reporting package + +# 1 Scope + +This package defines a generic method of reporting when statistics meet a pre-defined condition. By enabling the reporting of statistics, it allows the MGC to better manage resources, particularly in the areas of charging and quality of service. Furthermore, it allows an MGC to control event timestamp reporting. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*. + +[ITU-T H.248.30] Recommendation ITU-T H.248.30 (2007), *Gateway control protocol: RTCP extended performance metrics packages*. + +[ITU-T H.248.59] Recommendation ITU-T H.248.59 (2007), *Gateway control protocol: Event timestamp notification package*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 ADD.req:** Add command request (see [ITU-T H.248.1]). + +**3.2 MOD.req:** Modify command request (see [ITU-T H.248.1]). + +**3.3 MOV.req:** Move command request (see [ITU-T H.248.1]). + +**3.4 NOTIFY.req:** Notify command request (see [ITU-T H.248.1]). + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +MG Media Gateway + +MGC Media Gateway Controller + +# 5 Conventions + +None. + +# 6 Statistic conditional reporting package + +Package name: Statistic Conditional Reporting package +Package ID: scr, 0x00ae +Description: This package defines a mechanism for supporting the real-time reporting of specific statistics based on a particular condition. The term "real-time" means that the MG should immediately notify the MGC when the conditions are met (see clause 6.6.2). +Version: 2 +Extends: None + +## 6.1 Properties + +None. + +## 6.2 Events + +### 6.2.1 Conditional reporting + +Event name: Conditional Reporting +Event ID: cr, 0x0001 +Description: This event indicates the identifier of the statistic specified to be reported when it matches a given condition trigger. + +#### 6.2.1.1 EventsDescriptor parameters + +###### 6.2.1.1.1 Statistic identifier + +Parameter name: Statistic Identifier +Parameter ID: si, 0x0001 +Description: This parameter indicates the statistic specified to be reported. +Type: Binary: octet (string), Text: string +Optional: No +Possible values: Any valid H.248 PackageID/StatisticID pair. +Formatted according to the pkgdName syntax. +Default: None + +###### 6.2.1.1.2 Duration + +Parameter name: Duration +Parameter ID: dur, 0x0002 +Description: This parameter indicates the time span over which the statistic should be monitored, and in which other conditions may trigger a report of the statistic. +Type: Double +Optional: Yes +Possible values: 1 or more seconds +Default: None + +##### **6.2.1.1.3 Period** + +Parameter name: Period +Parameter ID: per, 0x0003 +Description: This parameter indicates the time interval from one statistic report trigger to the next. +Type: Double +Optional: Yes +Possible values: 1 or more seconds +Default: None + +##### **6.2.1.1.4 Maximum** + +Parameter name: Maximum +Parameter ID: max, 0x0004 +Description: This parameter indicates the top threshold to trigger the statistic reporting. When this parameter is crossed in the upward direction, the statistic reporting is triggered. +Type: Double +Optional: Yes +Possible values: Values according to the statistic to be reported. +Default: None + +###### **6.2.1.1.5 Minimum** + +Parameter name: Minimum +Parameter ID: min, 0x0005 +Description: This parameter indicates the bottom threshold to trigger the statistic reporting. When this parameter is crossed in the downward direction, the statistic reporting is triggered. +Type: Double +Optional: Yes +Possible values: Values according to the statistic to be reported. +Default: None + +##### **6.2.1.1.6 Normal** + +Parameter name: Normal +Parameter ID: nor, 0x0006 +Description: This parameter indicates when the statistic passes through the minimum or maximum threshold into the normal range. +Type: Boolean +Optional: Yes +Possible values: On/off +Default: None + +##### 6.2.1.1.7 Request timestamp + +Parameter name: Request timestamp +Parameter ID: rt, 0x0007 +Description: This parameter indicates whether or not an Event Timestamp with the detection time shall be included with the notification of the event. This provides similar functionality as [ITU-T H.248.59]. +Type: Enumeration +Optional: Yes +Possible values:    "*requested*"    The timestamp is requested (i.e., included). +                          "*suppressed*"   The timestamp is suppressed (i.e., excluded). +                          "*autonomous*" Determined by the MG itself. +Default:            "*autonomous*" + +##### 6.2.1.1.8 Value type + +Parameter name: Value Type +Parameter ID: typ, 0x0008 +Description: This parameter indicates the target value based on a mathematical keyword which is combined with the *Deviation*, *Compliance*, *Direction*, *Duration* and/or *Period* parameters to determine if reporting is required. The MG uses the keyword to calculate the actual statistical value. +Type: Enumeration +Optional: Yes +Possible values:   *ini*           indicates the initial value of the statistic. +                          *ave*           indicates the average value of the statistic. +                          *max*           indicates the maximal value of the statistic. +                          *min*           indicates the minimal value of the statistic. +                          *gen*           indicates the general value of the statistic. +NOTE 1 – The above enumerations relate to values not the similarly-named properties. +Default:            *gen* +NOTE 2 – The value "gen" indicates that the *Target Value* parameter is used to provide a value. + +##### 6.2.1.1.9 Target value + +Parameter name: Target Value +Parameter ID: val, 0x0009 +Description: This parameter indicates the MGC supplied actual statistic value which is combined with the *Deviation*, *Compliance*, *Direction*, *Duration* and/or *Period* parameters to determine if reporting is required. +Type: Double +Optional: Yes + +Possible values: Values according to the statistic to be reported. + +Default: Provisioned + +##### 6.2.1.1.10 Deviation + +Parameter name: Deviation + +Parameter ID: dev, 0x000a + +Description: This parameter indicates whether the statistic should be reported when it deviates from a target value. This may be further based on a percentage relative to the target value. The *Direction* parameter indicates whether the deviation is reported in the positive, negative or both directions. + +Type: String + +Optional: Yes + +Possible values: Any percentage, especially 0 for any degree of deviation. + +Default: None + +##### 6.2.1.1.11 Compliance + +Parameter name: Compliance + +Parameter ID: com, 0x000b + +Description: This parameter indicates whether the statistic should be reported when it returns to a target value. This may be further based on a percentage relative to the target value. The *Direction* parameter indicates whether the compliance is reported in the positive, negative or both directions. + +Type: String + +Optional: Yes + +Possible values: Any percentage, especially 0 for just completed compliance. + +Default: None + +###### 6.2.1.1.12 Direction + +Parameter name: Direction + +Parameter ID: dir, 0x000c + +Description: This parameter is used with the *Deviation* and/or *Compliance* parameters to indicate the direction the statistic should be reported when it deviates from or returns to the value specified by the *Value Type* or *Target Value* parameters. + +Type: Enumeration + +Optional: Yes + +Possible values: *up* indicates the positive direction. + +*down* indicates the negative direction. + +*bi* indicates the positive and negative directions. + +Default: "*bi*", however, see bullet f) in clause 6.6.1 for an exception. + +#### 6.2.1.2 ObservedEventsDescriptor parameters + +###### 6.2.1.2.1 Statistic identifier + +Parameter name: Statistic Identifier +Parameter ID: si, 0x0001 +Description: This parameter indicates the statistic specified that is reported. +Type: Binary: octet (string), Text: string +Optional: No +Possible values: Any valid H.248 PackageID/StatisticID pair. +Formatted according to the pkgdName syntax. +Default: None + +###### 6.2.1.2.2 Value + +Parameter name: Value +Parameter ID: val, 0x0002 +Description: This parameter indicates the current value of the statistic. +Type: Double +Optional: No +Possible values: Values according to the statistic to be reported. +Default: None + +## 6.3 Signals + +None. + +## 6.4 Statistics + +None. + +## 6.5 Error codes + +None. + +## 6.6 Procedures + +### 6.6.1 General + +To request an MG to provide real-time reporting of a particular statistic, the MGC shall set the Conditional Reporting (*cr*) event on the MG via an ADD.req, MOD.req or MOV.req with the Statistic Identifier (*si*) parameter set to the required statistic. A single event shall be set for each statistic required to be reported. + +In addition to the Statistic Identifier parameter, the MGC shall set at least one of the report conditions indicated by the parameters including Duration (*dur*), Period (*per*), Maximum (*max*), Minimum (*min*), Normal (*nor*), Value Type (*typ*), Target Value (*val*), Deviation (*dev*), Compliance (*com*) and Direction (*dir*). + +If the MGC sets non-sensical parameters (e.g., a *dev* or *com* parameter without a *typ* or *val* parameter) the MG shall respond with error codes 472 "Required information missing" or 473 "Conflicting property values". + +The usage of report condition setting parameters such as *dur*, *per*, *nor*, *max*, *min*, *typ*, *val*, *dev*, *com* and *dir* may be individual or together according to the following rules: + +- a) If the *dur* parameter exists independently, the statistic shall be reported at the expiry of the *dur* parameter. +- b) If the *per* parameter exists independently without the *dur* parameter, the statistic shall be reported every time at the expiry of the *per* parameter. +- c) If the *max*, *min* or *nor* parameters exist independently without the *dur* parameter, the statistic shall be reported every time the value exceeds the top threshold indicated by the *max* parameter, exceeds the bottom threshold indicated by the *min* parameter, or crosses back through the top or bottom threshold into the normal range if the *nor* parameter is set to "on". The *nor* parameter shall only be set with the *max* and/or *min* parameters. +- d) If the *typ*, *val*, *dev*, *com* or *dir* parameters exist independently without the *dur* parameter, the statistic shall be reported when it deviates from or returns to a target value which could be the initial, average, maximal, minimal value indicated by the *typ* parameter or any general value indicated by the *val* parameter, in a certain percentage indicated by the *dev* or *com* parameter and a certain direction indicated by the *dir* parameter. The *dev* or *com* parameter shall only be set with the *typ* and/or *val* parameters. The *dir* parameter shall only be set with the *dev*, *com* and/or *nor* parameters. +- e) The *dir* parameter has no effect on the *max* or *min* parameters, however if the *nor* parameter is set to "on" and the *dir* parameter is also set then it will affect whether the statistic shall be reported when it returns through the top, bottom or both thresholds. +- f) If the *typ* parameter is set to "max" then the *dev* parameter shall only be set with a *dir* parameter set to "down" and the *com* parameter shall only be set with a *dir* parameter set to "up". If the *typ* parameter is set to "min" then the *dev* parameter shall only be set with a *dir* parameter set to "up" and the *com* parameter shall only be set with a *dir* parameter set to "down". +- g) If the *per* parameter exists together with the *dur* parameter, then rule b) shall be applied only during the time of the *dur* parameter. +- h) If the *max*, *min* or *nor* parameters exist with the *dur* parameter, then rule c) shall be applied only during the time of the *dur* parameter. +- i) If the *typ*, *val*, *dev*, *com* or *dir* parameters exist with the *dur* parameter, the rule d) shall be applied only during the time of the *dur* parameter. +- j) The existence of the *per* and the *max*, *min*, *nor*, *typ*, *val*, *dev*, *com* or *dir* parameters are generally independent and shall not be considered together. + +When the MG detects that the above report conditions are met, it shall send a NOTIFY.req to the MGC indicating the Statistic Identity (*si*) and the Value (*val*) of the statistic. The value of the statistic is not reset upon reporting of the value of the statistic. + +For example: + +- If the MGC wanted to determine when the Gap Duration (see 6.4.4 of [ITU-T H.248.30]) exceeds a range of 200-1500 ms, the MGC would issue a MOD.req with the Conditional Reporting (*cr*) event with parameter Statistic Identity (*si*) equal to *xrbm/gd*, parameter Minimum (*min*) equal to 200 and parameter Maximum (*max*) equal to 1500. +- When the MG detects that the *xrbm/gd* statistic exceeds either the Minimum (*min*) or Maximum (*max*) parameter, then it issues a NOTIFY.req containing a Conditional Reporting (*cr*) ObservedEvent with the Statistic Identity (*si*) parameter equal to *xrbm/gd* and the Value (*val*) parameter indicating the value of the statistic. + +### 6.6.2 Guidelines on real-time reporting + +The rationale behind "real-time reporting" is the fact that there could be many different types of served user instances for statistic reports processing, either physically located at the MGC or remote entities, which may lead to slight differences concerning the real-time time-scale. Recommendations are given by the clauses below. The required behaviour in a specific environment could be defined, e.g., in an H.248 profile specification. + +The inclusion of a timestamp with the detection time in a notification of an event may be either requested or suppressed explicitly through the use of the *rt* parameter. If an MG cannot provide a timestamp for the event requested through an Add, Move or Modify command it shall respond with error code 543 "MGC requested event detection timestamp not supported". + +If the setting of the *rt* parameter is in conflict with the setting of the *etn/rt* property [ITU-T H.248.59], the MG shall respond with error code 473 "Conflicting property values". + +#### 6.6.2.1 Reporting without timestamp + +The MG must immediately notify the MGC when the conditions are met. The immediate transfer of statistic reports from MG to MGC is subject only to the normal transmission delays and those imposed by the H.248 message encoding/decoding processes. + +#### 6.6.2.2 Time-stamped reporting + +The MG must immediately notify the MGC when the conditions are met. The MG must insert parameter "detection time" (timestamp) in the ObservedEvents descriptor (see clause 7.1.17 of [ITU-T H.248.1]): "*detection times are reported with a precision of hundredths of a second*"). The timestamp may be that used for a "precise" time-correlation with regard to the granularity of the period (per) parameter. + +### 6.6.3 Condition calculation + +At each sample interval, the MG shall obtain the current sample value of the indicated statistic. This sample value will be replaced by a newer sample value and becomes the previous sample value at the next sample interval. For simplification, the clauses below cite them in "current value" and "previous value". + +#### 6.6.3.1 Duration + +Upon the setting of the *scr/cr* event with the *dur* parameter, the duration timer starts at zero second and counts to the number of seconds given by the value of this parameter. + +#### 6.6.3.2 Period + +Upon the setting of the *scr/cr* event with the *per* parameter, the period timer starts at zero second and counts to the number of seconds given by the value of this parameter. The period timer is reset to zero at each expiry and initialized for the next period count. + +#### 6.6.3.3 Maximum + +The Maximum is provided by the MGC. At each sample interval, the MG shall compare the current value of the indicated statistic with the previous value and the Maximum provided in the *max* parameter to determine when to report the event. If the current value is greater than the previous value and the maximum, and if the event has not already been reported, then the event with the current value of the statistic shall be reported. + +#### 6.6.3.4 Minimum + +The Minimum is provided by the MGC. At each sample interval, the MG shall compare the current value of the indicated statistic with the previous value and the Minimum provided in the *min* parameter to determine when to report the event. If the current value is less than the previous value + +and the Minimum, and if the event has not already been reported, then the event with the current value of the statistic shall be reported. + +#### 6.6.3.5 Normal + +The "normal range" is defined to be greater than the *min* parameter and less than the *max* parameter. When the *nor* parameter is set to "on", the MG calculates the "normal range". At each sample interval, the MG shall compare the current value of the indicated statistic with the previous value and the "normal range". If the current value is inside the "normal range" and the previous value is outside the "normal range" then the event with the current value of the statistic shall be reported. + +#### 6.6.3.6 Value type + +The initial, average, maximal or minimal value indicated by the *typ* parameter depends on the MG instead of the MGC. It is used in conjunction with the *dev* or *com* condition, e.g., the MG may provision these values on demand. + +The MG may use the time of the reception of the *scr/cr* event as the initial time for calculations for the indicated statistics. The current value of the indicated statistic at the time of setting the *scr/cr* event is regarded as the initial value. At each sample interval, the average, maximal or minimal value is calculated again based on the current value and previous value of the indicated statistic and the time offset from this initial time. + +Alternatively, the MG may provision the initial, average, maximal or minimal value for a specific statistic according to its native characters or specific administration requirement. + +#### 6.6.3.7 Target value + +The general value is provided by the MGC. It is used in conjunction with the *dev* or *com* condition. + +#### 6.6.3.8 Deviation + +Upon the setting of the *scr/cr* with the *dev* parameter, the MG shall calculate the positive and negative offset range based on the supplied percentage and the target value. At each sample interval, the MG shall compare the current value of the indicated statistic with the previous value and the offset range. If the previous value was inside the offset range and the current value is outside the offset range, the MG shall then use the *dir* parameter to determine if the event with the current value of the statistic is reported. + +#### 6.6.3.9 Compliance + +Upon the setting of the *scr/cr* with the *com* parameter, the MG shall calculate the positive and negative offset range based on the supplied percentage and the target value. At each sample interval, the MG shall compare the current value of the indicated statistic with the previous value and the offset range. If the previous value was outside the offset range and the current value is inside the offset range, the MG shall then use the *dir* parameter to determine if the event with the current value of the statistic is reported. + +#### 6.6.3.10 Direction + +This condition shall be used in conjunction with the *dev*, *com* or *nor* condition. + +### 6.6.4 Usage example + +The examples below indicate the behaviour of the MG when the Conditional Reporting (*cr*) event is set with the parameters indicated below, given a statistic with values from a minimum of -150 to a maximum of 250, average 50, initial 0. Parameter settings of: + +- 1) (*dur*=180) means the statistic should be reported after 180 s. +- 2) (*per*=30) means the statistic should be reported every 30 s. + +- 3) *(dur=150,per=10)* means the statistic should be reported every 10 s during a 150 s time span. +- 4) *(min=-100,max=200,nor=ON)* means the statistic should be reported when it downward exceeds its bottom threshold value -100 or upward exceeds its top threshold value 200 or enters back into the value zone between -100 and 200. +- 5) *(min=-88,max=99,nor=ON,dir=up)* means the statistic should be reported when it downward exceeds its bottom threshold value -88 or upward exceeds its top threshold value 99. If the statistic value has downward exceeded the bottom threshold value of -88 then the statistic should be reported when it enters back into the value zone between -88 and 99. +- 6) *(min=-88,max=99,nor=ON,dir=down)* means the statistic should be reported when it downward exceeds its bottom threshold value -88 or upward exceeds its top threshold value 99. If the statistic value has upward exceeded the top threshold value of 99 then the statistic should be reported when it enters back into the value zone between -88 and 99. +- 7) *(dur=150,min=-30,max=30)* means the statistic should be reported when it downward exceeds its bottom threshold value -30 or upward exceeds its top threshold value 30 during a 150 s time span. +- 8) *(typ=ini,dev=0,com=0)* means the statistic should be reported when it deviates from or returns to its initial value which may be known by the MG but not the MGC. +- 9) *(typ=ave,dev=50,com=30)* means the statistic should be reported when it deviates from $\pm 50\%$ or returns to $\pm 30\%$ of its average value which may be known by the MG but not the MGC. +- 10) *(typ=max,com=5,dir=up)* means the statistic should be reported when it upward returns to 5% of its maximal value which may be known by the MG but not the MGC. +- 11) *(typ=min,com=3,dir=down)* means the statistic should be reported when it downward returns to 3% of its minimal value which may be known by the MG but not the MGC. +- 12) *(dur=150,val=123,dev=8)* means the statistic should be reported when it deviates from $\pm 8\%$ of the value 123 during a 150 s time span. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.48-201202-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/H/T-REC-H.248.48-201202-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdda357ad1a4babc7ec2f1e03ddac56eb4dd9cbc --- /dev/null +++ b/marked/H/T-REC-H.248.48-201202-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f772e4dcd2212542731341861d6eab7cbfe4deb181f52bdff46f710200ee644e +size 57694 diff --git a/marked/H/T-REC-H.248.48-201202-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/H/T-REC-H.248.48-201202-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..022c7f4cb1be8f3a456416d9a34b5defcc5b813f --- /dev/null +++ b/marked/H/T-REC-H.248.48-201202-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c81bacba6b6958022c7ad39d6cdc4c003ebf6c4338991f00d7351e40c8d721e +size 143009 diff --git a/marked/H/T-REC-H.248.48-201202-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.248.48-201202-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.248.48-201202-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.248.48-201202-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.248.48-201202-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..574b894b3895edd836d83a96e85c4e0c78ca9810 --- /dev/null +++ b/marked/H/T-REC-H.248.48-201202-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ed84b6620e3a53f728a90301e4f09af411ea2594022e05f301ff0adfd368707 +size 116998 diff --git a/marked/H/T-REC-H.248.48-201202-I_PDF-E/raw.md b/marked/H/T-REC-H.248.48-201202-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f0680d4b950d1462cfa33c8cad4e5da27ffdf4f3 --- /dev/null +++ b/marked/H/T-REC-H.248.48-201202-I_PDF-E/raw.md @@ -0,0 +1,593 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.48** + +(02/2012) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: RTCP XR block +reporting package** + +Recommendation ITU-T H.248.48 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T H.248.48** + +# **Gateway control protocol: RTCP XR block reporting package** + +## **Summary** + +Recommendation ITU-T H.248.48 defines packages which allow media gateways (MGs) to report media transmission quality and call quality to media gateway controllers (MGCs) using metrics defined in a series of Real-time Transport Protocol Control Protocol (RTCP) extended report (XR) blocks (see IETF RFC 3611). + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.248.48 | 2012-02-13 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2012 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 3 | +| 6 RTCP XR Block Reporting Package..... | 4 | +| 6.1 Properties..... | 4 | +| 6.2 Events ..... | 6 | +| 6.3 Signals ..... | 6 | +| 6.4 Statistics..... | 6 | +| 6.5 Error codes..... | 7 | +| 6.6 Procedures ..... | 8 | +| Bibliography..... | 15 | + + + +## Gateway control protocol: RTCP XR block reporting package + +# 1 Scope + +This Recommendation defines packages which allow media gateways (MGs) to report media transmission quality and call quality to media gateway controllers (MGCs) using metrics defined in a series of Real-time Transport Protocol Control Protocol (RTCP) extended report (XR) blocks standardized by IETF [IETF RFC 3611]. The Recommendation is applicable to MGs which have at least one interface which uses the Real-time Transport Protocol (RTP) [IETF RFC 3550]. + +The RTCP XR metrics family may be applied to unicast bidirectional RTP sessions including zero or more RTP translators as well as two RTP end systems. + +NOTE – These models (including the RTP mixer) are the high-level RTP system models according to [IETF RFC 3550]. [b-IETF RFC 5117] is an extension and provides RTP topology models at a more detailed level. All these models are applicable in principle to ITU-T H.248.48 because an ITU-T H.248 IP stream or termination point may be a node of such an RTP topology. The particular RTP topology may in principle affect the processing of the report. + +For instance, the RTP translator model is divided into an "RTP transport translator" and an "RTP media translator" model. The first one is media-agnostic, the second one is media-aware. The individual modes have a different impact on RTCP packet types and/or report information. + +For such RTP sessions, an MG may receive the RTCP XR metrics family reports from one or more of the other RTP systems involved in the RTP session, up to a possible maximum of all the RTP systems other than itself. + +The package in [ITU-T H.248.48] uses a sub-list of Octet String to permit transfer of a variable number of the RTCP XR metrics family reports in an ITU-T H.248 Statistics descriptor. Each Octet String contains all the data from a single RTCP XR packet, which contains measurements made at one RTP system of one or more streams originating at another RTP system (or systems). The RTCP XR packet contains the synchronization source (SSRC) [IETF RFC 3550] of the RTP system which made the measurement, and an SSRC for each RTP system which originated a measured stream. This enables the MGC (or other entity observing the report) to determine the section of the RTP session to which the report applies. + +Through the use of ITU-T H.248 Properties, this package allows the MGC to control the following aspects of MG behaviour: + +- the reporting of a specified set of Report Blocks, measured locally at the MG, towards the MGC as ITU-T H.248 Statistics. +- the collection of RTCP XR packets incoming to the MG for reporting towards the MGC as ITU-T H.248 Statistics. No more than one RTCP XR packet is to be stored for each unique tuple of the Originating Point and Measurement Point. An existing stored packet is overwritten by the next packet to arrive for the same tuple. +- the forwarding of RTCP XR packets by RTP translators, including whether RTP translators forward packets which were generated by other RTP translators. + +The RTCP XR family is intended to be extensible and it is the intention that this package will not require modification if RTCP XR is extended. Hence property values which control the RTCP XR blocks which are to be reported by the MG are defined by reference to Session Description Protocol (SDP) syntactical elements standardized additively in [IETF RFC 3611] and in RTCP XR. As new RTCP XR blocks are defined, allowable property values are implicitly extended with the SDP defined for the new block. + +In addition, the MGC may control the sending of a specified set of RTCP XR report blocks (alongside RTP media) by an MG which is an RTP system (end system, mixer or translator), by addition to the remote descriptor of the same standardized SDP attribute, in "a=rtcp-xr:" lines. + +The new statistic *xrbr/xrpkt* may be sent by the MG to the MGC in an ITU-T H.248 response to an Audit or Subtract command, in a similar manner to other ITU-T H.248 Statistics. It may also be sent by the MG in parameter *scr/val* in an Observed Event of the Statistic Conditional Reporting Package [b-ITU-T H.248.47]. No immediate ITU-T H.248 action is initiated by the arrival of RTCP XR packets at the MG, but (depending on the value of *xrbr/scpo*) the incoming packet may be stored for future reporting. If a packet is stored, it overwrites any previously-stored packet having the same tuple of Originating Point and Measurement Point. + +The MGC may reset the values of locally-measured metrics within reports in the Statistic Descriptor. It is not possible to reset the values of metrics received in RTCP metrics family reports from remote systems. + +Detailed descriptions of RTCP XR metrics are not repeated here; refer to [IETF RFC 3611]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation + +[ITU-T H.248.1 Amd.2] Recommendation ITU-T H.248.1 Amd.2 (2009), *Gateway control protocol: Version 3: Corrections and clarifications*. + +[IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. + +[IETF RFC 3611] IETF RFC 3611 (2003), *RTP Control Protocol Extended Reports (RTCP XR)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 CNAME** [IETF RFC 3550]: Canonical Name, a persistent transport-level identifier for a RTP source. + +**3.1.2 measurement point (MP)** [b-ITU-T M.2301]: The physical or logical point at which measurements can be made and to which the data obtained is related. In the context of this Recommendation, the RTP system which receives one or more streams of RTP packets, makes measurements on the streams, and may generate RTCP XR packets containing the resulting metrics for transmission towards other RTP systems. The MG may be a Measurement Point. The SSRC of the Measurement Point is present in the RTCP XR header of an RTCP XR packet, see clause 2 of [IETF RFC 3611]. + +**3.1.3 RTCP XR** [IETF RFC 3611]: RTCP Extended Reports. RFC 3611 defines both an extensible scheme for definition of new "blocks" to contain metrics, and the first set of seven blocks which use this scheme. + +**3.1.4 SDES** [IETF RFC 3550]: Source Description RTCP packet containing Source Description items including CNAME. + +**3.1.5 SSRC** [IETF RFC 3550]: Synchronization Source identifier. + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 filtering point (FP)**: Point at which the RTCP traffic is policed. The conditions of the FP policy rules here are typically based on RTP/RTCP information elements. The MGC may set policy on the MG to control this filtering, via the property *xrbr/sfpo*. The actions of FP policy rules are described in clause 6.1.2 below. + +**3.2.2 originating point (OP)**: The RTP system which originates a stream of RTP packets. For this package, the Originating Point is a synchronization source for the RTP packets according to [IETF RFC 3550], and hence must be an RTP end system or RTP mixer. + +**3.2.3 reporting point (RP)**: An MG which implements the current package, defined as the device which sends suitably coded RTCP XR reports as an ITU-T H.248 Statistic towards the MGC. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------| +| CNAME | Canonical Name | +| FP | Filtering Point | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MP | Measurement Point | +| OP | Originating Point | +| QoS | Quality of Service | +| RP | Reporting Point | +| RR | (RTCP) Receiver Report | +| RTCP | RTP Control Protocol | +| RTP | Real-time Transport Protocol | +| SDES | Source Description | +| SDP | Session Description Protocol | +| SR | (RTCP) Sender Report | +| SSRC | Synchronization Source | +| VoIP | Voice over Internet Protocol | +| XR | (RTCP) Extended Report | + +# **5 Conventions** + +None. + +# 6 RTCP XR Block Reporting Package + +Package name: RTCP XR Block Reporting Package +Package ID: xrbr (0x00af) +Description: Package for collection of metrics data for RTCP XR report blocks using the RTCP XR metrics architecture, and for control of gateway behaviour with respect to generation, forwarding, and collection of these report blocks. +Version: 1 +Extends: None + +## 6.1 Properties + +### 6.1.1 Select Remote Measurement Packets for Reporting by Origination + +Property name: Select Remote Measurement Packets for Reporting by Origination +Property ID: scpo (0x0001) +Description: Selects which RTCP XR packets arriving at the MG are collected in the Statistics Descriptor and sent to the MGC. Packets are selected based on the type of RTP system which originated them. The two possibilities that may be distinguished at the MG are packets from an RTP translator (not a synchronization source for RTP), or packets that are from either an RTP end system or an RTP mixer (both of which are synchronization sources for RTP). An RTCP XR packet from an RTP end system may be recognized because it has a sender SSRC in the RTCP XR header that is identical to an SSRC that appears in RTP media packets received at the same ephemeral termination. An RTCP XR packet from an RTP translator may be recognized because it has a sender SSRC in the RTCP XR header that is not identical to an SSRC that appears in any RTP media packet received at the same ephemeral termination. Local measurements to be sent as RTCP XR metrics blocks to the MGC are specified by property *xrbr/srb* (see clause 6.1.3 below) and are not affected by *xrbr/scpo*. + +This package does not provide any means to restrict the set of RTCP XR block types reported to the MGC from RTCP XR packets incoming to the MG. Selection by this property is at the granularity of a complete RTCP XR packet. + +Type: Sub-list of enumeration +Possible values: The sub-list contains one or two of the following: +N (0x0001): Select no packets for forwarding to remote RTP entities +E (0x0002): Select packets from an RTP end system or RTP mixer +T (0x0003): Select packets from an RTP translator +If enumeration value N is selected, it must be the only value present. If N is not present, the list may hold E alone, T alone, or both E and T together. +Default: N +Defined in: LocalControl + +Characteristics: Read/Write + +### 6.1.2 Select Forwarded Packets by Origination + +Property name: Select Forwarded Packets by Origination + +Property ID: sfpo (0x0002) + +Description: Selects which RTCP XR packets arriving at the MG are forwarded in RTCP towards other RTP systems involved in the RTP session. Packets are selected based on the type of RTP system which originated them. The two possibilities that may be distinguished at the MG are packets from an RTP translator (not a synchronization source for RTP), or packets that are from either an RTP end system or RTP mixer (both of which are synchronization sources for RTP). This property is primarily applicable to RTP translators, because it would not be usual for an RTP end system or RTP mixer to forward a received RTCP packet. An RTCP XR packet from an RTP end system or RTP mixer may be recognized because it has a sender SSRC in the RTCP XR header that is identical to an SSRC which appears in RTP media packets received at the same ephemeral termination. An RTCP XR packet from an RTP translator may be recognized because it has a sender SSRC in the RTCP XR header that is not identical to an SSRC that appears in any RTP media packet received at the same ephemeral termination. + +This package does not provide any means to restrict the set of RTCP XR block types forwarded from RTCP XR packets incoming to the MG. Selection by this property is at the granularity of a complete RTCP XR packet. + +If a packet is forwarded, the forwarded packet should comply with the guidance on RTCP processing in translators, see clause 7.2 of [IETF RFC 3550]. + +Type: Sub-list of enumeration + +Possible values: The sub-list contains one or two of the following: + +N (0x0001): Select no packets for forwarding to the MGC + +E (0x0002): Select packets from an RTP end system or RTP mixer + +T (0x0003): Select packets from an RTP translator + +If enumeration value N is selected, it must be the only value present. If N is not present, the list may hold E alone, T alone, or both E and T together. + +Default: E + +Defined in: LocalControl + +Characteristics: Read/Write + +### 6.1.3 Select Local Measurement Blocks for Reporting + +Property name: Select Local Measurement Blocks for Reporting + +Property ID: srb (0x0003) + +**Description:** Selects which locally-measured RTCP XR block types are reported by the MG to the MGC. Each string element of the sub-list relates to the reporting of a single metrics block type. Locally measured RTCP XR block types may also be generated by the MG towards other RTP systems alongside RTP media. The block types to be generated as RTCP towards other RTP systems may also be controlled via ITU-T H.248. This control is implemented by including SDP "a=rtcp-xr:" lines in the remote descriptor for the stream or termination, as described in clause 6.6.5 below. + +**Type:** Sub-list of String (SDP coding) + +**Possible values:** The syntax of each string element of this property is the SDP defined in the IETF document (e.g. RFC, draft) describing the block type. For example, to specify generation of the Packet Delay Variation block and the Concealed Seconds block, the sub-list could be: + +`["pkt-dly-var, 2, npc=100.0, ppc=100.0", "conc-sec=50"]` + +This indicates that the packet delay variation and concealed seconds blocks are to be created and reported to the MGC. + +The sub-list may be empty to indicate that no blocks are to be reported to the MGC. + +**Default:** Null + +**Defined in:** LocalControl + +**Characteristics:** Read/Write + +## **6.2 Events** + +None. + +## **6.3 Signals** + +None. + +## **6.4 Statistics** + +### **6.4.1 RTCP XR packets** + +**Statistic name:** RTCP XR packets + +**Statistic ID:** xrpkt (0x0001) + +**Description:** Each Octet String in the sub-list codes a complete RTCP XR packet, including the RTCP XR header defined in clause 2 of [IETF RFC 3611] and all the RTCP XR report blocks (see below for behaviour in cases where other RTCP XR block types are also present). "Packet" is used here in the sense of clause 6.1 of [IETF RFC 3550]. There are usually multiple RTCP packets within a UDP datagram containing RTCP, including either an (RTCP) sender report (SR) or (RTCP) receiver report (RR), a source description (SDES), and possibly others including the RTCP XR packet that is the subject of this Statistic. Each such packet type is defined by a unique 8-bit packet type field, which is 207 for RTCP XR. + +Not all RTCP XR packets sent or received by the MG are necessarily + +forwarded to the MGC in this Statistic. The selection of packets is controlled by the Properties *xrbr/scpo* and *xrbr/srb* described above and in clauses below describing procedures. + +Cases are likely to occur in practice where the RTCP XR packet contains RTCP XR block types defined before standardization of the Measurement Identifier block type, as well as RTCP XR block types belonging to the new family of metrics blocks that use the Measurement Identifier block type. An important example is the series of seven RTCP XR block types defined in [IETF RFC 3611] itself, which may be reported using the packages defined in [b-ITU-T H.248.30]. If such a case occurs, the MG encodes the entire RTCP XR packet containing both old- and new-style blocks for transmission to the MGC. The MGC may also request statistics defined in packages of [b-ITU-T H.248.30]. If it does, the data from blocks defined in [IETF RFC 3611] will be duplicated in the Audit response or Subtract response, though in different statistics having different formats. If the MGC does not request statistics of [b-ITU-T H.248.30], it may parse the data in statistic *xrbr/xrpkt* to obtain data corresponding to blocks defined in [IETF RFC 3611], and present in RTCP incoming to the MG. However it will not obtain any data corresponding to blocks defined in [IETF RFC 3611] and measured locally at the MG, because these are not encoded in the statistic *xrbr/xrpkt*. + +RTCP XR packets are binary data. They are coded for transmission as an Octet String type as described in clause A.2 of [ITU-T H.248.1 Amd.2] for the binary encoding of the protocol, or using the Hexadecimal Octet Coding described in clause B.3 of [ITU-T H.248.1 Amd.2] for the text encoding of the protocol. See clause 6.6.11 below for an example of coding a packet according to the method of clause B.3 of [ITU-T H.248.1 Amd.2]. + +| | | +|------------------|---------------------------------------------------------------------------------------------------------------| +| Type: | Sub-list of Octet String | +| Possible values: | Sub-list of Octet String or Hexadecimal Octet Coding of binary data. | +| Level: | Stream. If a Termination has only one Stream then xrbr/xrpkt may be reported at the Termination level. | + +## 6.5 Error codes + +### 6.5.1 Unsupported measurement block type + +| | | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Error Code #: | 485 | +| Name: | Unsupported measurement block type | +| Definition: | The MGC has requested the MG either to report to the MGC, or to send to another RTP system, an RTCP XR measurement block type which it does not support. | +| Error text in the Error Descriptor: | The SDP text from the property xrbr/srb or from the remote descriptor describing the unsupported block. | +| Comment: | None | + +### 6.5.2 Unsupported block parameter value + +| | | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Error Code #: | 486 | +| Name: | Unsupported block parameter value | +| Definition: | The MGC has requested the MG either to report to the MGC, or to send to another RTP system, a parameterised RTCP XR measurement block type. The MG supports the block type only for certain values of the parameters. The MG does not support the block type for the parameter value specified. | +| Error text in the Error Descriptor: | The SDP text from the property xrbr/srb or from the remote descriptor describing the unsupported block. | +| Comment: | None | + +### 6.5.3 Inconsistent block type parameters + +| | | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Error Code #: | 487 | +| Name: | Inconsistent block type parameters | +| Definition: | The MGC has requested the MG to report a parameterized block type to the MGC, and to send the same block type to another RTP system, but the parameters specified in the two cases are different and cannot be supported simultaneously. | +| Error text in the Error Descriptor: | The SDP text from the property xrbr/srb or from the remote descriptor describing the unsupported block (whichever is received later at the MG). | +| Comment: | None | + +## 6.6 Procedures + +### 6.6.1 Overview + +The primary role of the MG in connection with this package is to act as a reporting point. In this role it may code transmitted and received RTCP XR packets in the statistic *xrbr/xrpkt* of the package, and to send this statistic to the MGC. Support of this primary role usually requires making local measurements on incoming packet streams. + +Here, a transmitted RTCP XR packet is one containing metrics measured at the MG on packet streams incoming to the MG. Packets of this type may be physically transmitted by the MG, as part of an RTCP packet sent towards other RTP systems participating in the RTP session [IETF RFC 3550]. However, it is also possible for the MG to make measurements on the incoming packet stream and format them into RTCP XR blocks in an RTCP XR packet which, though it is not transmitted in RTCP, is coded and sent towards the MGC as one of the Octet String elements of statistic *xrbr/xrpkt*. These local measurements are sent to the MGC using the same format as that used when the MG forwards to the MGC reports received in RTCP from other RTP systems of the RTP session. + +#### 6.6.1.1 Application of RTCP Source Description Package + +It is assumed that, if the MG uses the current package to send RTCP XR metrics blocks to the MGC, it will always use the RTCP Source Description (*rtcpsdes*) package in [b-ITU-T H.248.71] to send information linking all the SSRC (Synchronization Source identifiers) to the corresponding canonical names (CNAMEs). + +### 6.6.2 Example RTP session and RTCP XR metrics blocks + +Figure 1 shows an example RTP session with two RTP end systems with CNAMEs *gw1.t1.com* and *gw7.t2.com*, and an RTP translator with CNAME *sbc3.t1.com*. Both RTP end systems generate RTCP XR blocks for Voice over Internet Protocol (VoIP) metrics (clause 4.7 of [IETF RFC 3611]) and packet receipt time (clause 4.4 of [IETF RFC 3611]), and send them towards other RTP systems participating in the RTP session. In addition, the RTP translator generates RTCP XR blocks for VoIP metrics for both incoming streams (one from each RTP end system of the session), and sends them to other participants in the RTP session. All RTP systems allocate synchronization source identifiers for themselves, unique within the scope of the RTP session. When this example is used below, we assume that the RTP end system *gw1.t1.com* is the MG. Other RTP systems may be controlled by ITU-T H.248. + +![Diagram of an RTP session showing RTCP packets at the RTP interface. It features three main components: an RTP end system (gw1.t1.com), an RTP translator (sbc3.t1.com), and another RTP end system (gw7.t2.com). Below each component is a detailed view of the RTCP packets it sends or receives. The left end system (A) sends SR, SDES, and XR packets. The translator (X) receives SR and XR from the left, adds its own SDES and XR, and forwards them. The right end system (B) receives SR and XR from the translator, adds its own SDES and XR, and forwards them. The packets are color-coded: SR (light blue), SDES (light green), XR (light orange), and VOIP metrics (light yellow).](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +The diagram illustrates the flow of RTCP packets in an RTP session involving two end systems and one translator. The components and their packet contents are as follows: + +- A: RTP end system gw1.t1.com (7975DEBA)** + - SR PT = 200** (sender = 7975DEBA) + - SR body** (source\_1 = 8CF602B2) + - SDES PT = 202** + - SSRC = 7975DEBA**, **CNAME = gw1.t1.com** + - XR PT = 207** (SSRC = 7975DEBA) + - VOIP metrics** (SSRC = 8CF602B2) + - Packet receipt time** (SSRC = 8CF602B2) +- X: RTP translator sbc3.t1.com (D6F3AF0F)** + - RR PT = 201** (sender = D6F3AF0F) + - RR body** (source\_1 = 8CF602B2, source\_2 = 7975DEBA) + - SDES PT = 202** + - SSRC = D6F3AF0F**, **CNAME = sbc3.t1.com** + - XR PT = 207** (SSRC = D6F3AF0F) + - VOIP metrics** (SSRC = 8CF602B2) + - VOIP metrics** (SSRC = 7975DEBA) +- B: RTP end system gw7.t2.com (8CF602B2)** + - SR PT = 200** (sender = 8CF602B2) + - SR body** (source\_1 = 7975DEBA) + - SDES PT = 202** + - SSRC = 8CF602B2**, **CNAME = gw7.t2.com** + - XR PT = 207** (SSRC = 8CF602B2) + - VOIP metrics** (SSRC = 7975DEBA) + - Packet receipt time** (SSRC = 7975DEBA) + +H.248.48(12)\_F01 + +Diagram of an RTP session showing RTCP packets at the RTP interface. It features three main components: an RTP end system (gw1.t1.com), an RTP translator (sbc3.t1.com), and another RTP end system (gw7.t2.com). Below each component is a detailed view of the RTCP packets it sends or receives. The left end system (A) sends SR, SDES, and XR packets. The translator (X) receives SR and XR from the left, adds its own SDES and XR, and forwards them. The right end system (B) receives SR and XR from the translator, adds its own SDES and XR, and forwards them. The packets are color-coded: SR (light blue), SDES (light green), XR (light orange), and VOIP metrics (light yellow). + +**Figure 1 – An example RTP session showing RTCP packets at the RTP interface (ITU-T H.248 reporting MG is the left-hand RTP end system gw1.t1.com)** + +Figure 2 provides an overview of the coding of the resulting RTCP XR packets (those either reported or collected at the MG) into the statistic *xrbr/xrpkt* of the package. It also shows that the resulting CNAME-SSRC "database" is coded into statistics of the RTCP source description package *rtcpsdes* [b-ITU-T H.248.71], so that the MGC may interpret the SSRCs present in the coded RTCP XR headers within *xrbr/xrpkt*. + +Coding of a complete RTCP XR packet is shown in detail in clause 6.6.11 below. + +![Diagram illustrating the ITU-T H.248 Reporting point for coding RTCP XR packets and the CNAME database. The diagram shows the structure of RTCP packets (SR, XR, RR) and their encoding into an xrbr/xrpkt list. The CNAME database contains entries for SSRCs 7975DEBA, D6F3AF0F, and 8CF602B2. Arrows indicate the flow of data from the database and packet structures to the final encoding.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +The diagram illustrates the coding of RTCP XR packets and the CNAME database. At the top, the CNAME database contains three entries: SSRC = 7975DEBA (CNAME = gw1.t1.com), SSRC = D6F3AF0F (CNAME = sbc3.t1.com), and SSRC = 8CF602B2 (CNAME = gw7.t2.com). These are sent using the *rtcpsdes* package. Below, the *xrbr/xrpkt* list contains three entries: "01F300289EAE7B5D.", "01F300F86BCFF5F0.", and "01F30028316F404D.". The middle section shows the structure of RTCP packets: SR PT = 200 (sender = 7975DEBA), SR body (source\_1 = 8CF602B2), XR PT = 207 (SSRC = 7975DEBA), VOIP metrics (SSRC = 8CF602B2), and Packet receipt time (SSRC = 8CF602B2). The right section shows the encoding per Clause B.3 of ITU-T H.248.1, which includes RR PT = 201 (sender = D6F3AF0F), RR body (source\_1 = 8CF602B2, source\_2 = 7975DEBA), XR PT = 207 (SSRC = D6F3AF0F), VOIP metrics (SSRC = 8CF602B2), and VOIP metrics (SSRC = 7975DEBA). The bottom section shows the final encoding per Clause B.3 of ITU-T H.248.1, which includes SR PT = 200 (sender = 8CF602B2), SR body (source\_1 = 7975DEBA), XR PT = 207 (SSRC = 8CF602B2), VOIP metrics (SSRC = 7975DEBA), and Packet receipt time (SSRC = 7975DEBA). The label H.248.48(12)\_F02 is at the bottom right. + +Diagram illustrating the ITU-T H.248 Reporting point for coding RTCP XR packets and the CNAME database. The diagram shows the structure of RTCP packets (SR, XR, RR) and their encoding into an xrbr/xrpkt list. The CNAME database contains entries for SSRCs 7975DEBA, D6F3AF0F, and 8CF602B2. Arrows indicate the flow of data from the database and packet structures to the final encoding. + +**Figure 2 – ITU-T H.248 Reporting point – Coding RTCP XR packets and the CNAME database** + +### 6.6.3 Controlling the measurements to be made at the MG + +Where an MG makes measurements and creates an RTCP XR packet that may either be sent in RTCP to other RTP systems, or be sent as an element of a statistic *xrbr/xrpkt* to the MG, or both, it is necessary to control the measurements to be made by the MG. + +Property *xrbr/srb* ("Select Local Measurement Blocks for Reporting") specifies the metrics blocks to be reported by the MG to the MGC, which must therefore be populated with measurements made locally on RTP streams at the MG. Procedures for the use of property *xrbr/srb* are described in more detail in clause 6.6.4 below. + +If the MG does not support a requested block type, it returns error 485, "*Unsupported measurement block type*". If the MG supports a parameterised block type for certain values of the parameters defining the block, but not for the parameter values specified in the request, it returns error 486 "*Unsupported block parameter value*". + +The MG may also make measurements to populate metrics blocks that are sent as RTCP XR packets (alongside the RTP media packets) to other RTP systems participating in the RTP session. This function is controlled by lines in the SDP within the remote descriptor for the appropriate ephemeral termination, and is described in more detail in clause 6.6.5 below. + +Because the MG may send RTCP XR metrics blocks both towards its MGC in the statistic *xrbr/xrpkt* of this package, and towards other RTP systems of the RTP session as RTCP XR packets alongside RTP media, the MG must make sufficient measurements to populate both sets of metrics blocks. The set of metrics blocks that must be populated by the MG is the set union of those specified in property *xrbr/srb* for reporting to the MGC, and those specified with SDP in the remote descriptor for reporting in RTCP XR to other RTP systems. The MG should make the necessary measurements to populate the specified metrics blocks in this set union. + +Because metrics blocks for local measurement are specified independently in *xrbr/srb* and in the remote descriptor, it is possible to specify the same metrics block in the two places, but with different parameters in those cases where the metrics block has optional features controlled by SDP. Some syntactically permitted combinations may exceed the capability of the MG. The MGC should ensure that the union of requests for metrics blocks specified by property *xrbr/srb* and of requests for metrics blocks specified by SDP in the remote descriptor are within the capability of the MG. + +If the MG does not support the combination of blocks specified jointly in property *xrbr/srb* and the remote descriptor, it returns error 487 "*Inconsistent block type parameters*" in response to the request which reveals the inconsistency. + +### 6.6.4 Specifying metrics blocks measured at the MG and reported to the MGC + +Property *xrbr/srb* (Select Local Measurement Blocks for Reporting) specifies the RTCP XR metrics blocks to be populated at the MG based on its measurements on incoming RTP streams, and reported to the MGC. + +The syntax of *xrbr/srb* is a sub-list of OctetString, where each OctetString is an instance of the block-specific SDP defined in the specification which describes the required block. + +For example, in order to send the RTCP XR [IETF RFC 3611] blocks for run length encoding of reports, VoIP metrics, and receiver reference time report to the MGC. Property *xrbr/srb* would be set to: + +``` +["pkt-loss-rle=100", "voip-metrics", "rcvr-rtt=all:100"] +``` + +The numerical values are parameters used to control the collection of statistics by the MG. Their use is described in [IETF RFC 3611]. + +### 6.6.5 Specifying metrics blocks measured at the MG and sent to peer RTP systems + +In the text encoding of the protocol, metrics blocks to be sent in RTCP XR packets alongside media towards other RTP systems are specified in an "a=rtcp-xr:" line of the SDP media description in the remote descriptor, where the text following the "a=rtcp-xr:" element is the syntax element *xr-format* defined additively in [IETF RFC 3611]. + +If the MG does not support a requested block type, it returns error 485, "*Unsupported measurement block type*". If the MG supports a parameterised block type for certain values of the parameters defining the block, but not for the parameter values specified in the request, it returns error 486 "*Unsupported block parameter value*". + +If the MG does not support the combination of blocks specified jointly in property *xrbr/srb* and the remote descriptor, it returns error 487 "*Inconsistent block type parameters*" in response to the request which reveals the inconsistency. + +### 6.6.6 Specifying the collection of received RTCP XR packets for the MGC + +An RTCP XR packet received at the MG from another RTP system participating in the RTP session, and containing RTCP XR blocks, may be coded into the statistic *xrbr/xrpkt* and sent to the MGC. The property *xrbr/scpo* (Select Remote Measurement Packets for Reporting by Origination) allows the MGC to select which RTCP XR packets are collected by the MG and sent to the MGC. property *xrbr/scpo* specifies whether the MG collects RTCP XR packets which it receives from + +RTP end systems and RTP mixers, and whether the MG collects RTCP XR packets which it receives from RTCP translators. The property is a sub-list of enumeration, so it is possible to specify the collection of neither type of report (an empty sub-list), either type, or both types. + +RTCP XR packets are recognized as from RTP end systems because the SSRC in the RTCP XR header is identical to an SSRC in an RTP packet received at the same ephemeral termination. RTCP XR packets are recognized as from RTP translators because the SSRC in the RTCP XR header is not identical to an SSRC in any RTP packet received at the same ephemeral termination. + +In the example above, the MG collects packets from its peer RTP end system and from an RTP translator, as well as reporting the RTCP XR packet containing its own measurements. Hence property *xrbr/scpo* is set to + +[E, T] . + +The transmission to the MGC of metrics blocks containing the MG's local measurements is controlled by property *xrbr/srb* and not by property *xrbr/scpo*. + +### 6.6.7 Specifying the forwarding of RTCP XR packets to other RTP systems + +An RTCP XR packet received at the MG from another RTP system participating in the RTP session, and containing RTCP XR blocks, may be forwarded by the MG in RTCP towards other RTP systems participating in the RTP session. The property *xrbr/sfpo* (Select Forwarded Packets by Origination) allows the MGC to select which RTCP XR packets are forwarded by the MG. Property *xrbr/sfpo* specifies whether the MG forwards RTCP XR packets which it receives from RTP end systems and RTP mixers, and separately whether the MG forwards RTCP XR packets which it receives from RTCP translators. The property is a sub-list of enumeration. It is possible to specify the forwarding of "neither type of report", "either type" or "both types". + +In the example above, the MG is an RTP end system and does not forward RTCP packets. However the RTP translator *sbc3.tl.com* forwards RTCP XR packets from RTP end systems, but not from other translators. If *sbc3.tl.com* were controlled by ITU-T H.248, then property *xrbr/sfpo* would be set to + +[E] . + +RTP translator *sbc3.tl.com* also generates RTCP XR packets based on its own measurements. As an informative example, if controlled by ITU-T H.248 its MGC would provide the following SDP line in remote descriptors to cause each termination to measure, and send in RTCP XR [IETF RFC 3611], VoIP metrics and receiver reference time blocks: + +``` +a=rtcp-xr:voip-metrics rcvr-rtt=all +``` + +An ITU-T H.248-controlled RTP translator may, of course, also report statistics to its MGC, and procedures for this are identical to those discussed above for the case of the RTP end system. + +### 6.6.8 Audit and reset of statistics + +An MGC may retrieve statistics *xrbr/xrpkt* by standard ITU-T H.248 methods using Subtract or AuditValue commands. For statistic *xrbr/xrpkt*, an AuditValue or Subtract will cause the most recently received RTCP XR packets from remote RTP systems to be returned, if selected by property *xrbr/scpo*. These received packets may several seconds old even if RTCP is sent frequently by the peer RTP systems. However for the MG's locally-measured metrics blocks, an AuditValue or Subtract shall sample the most recent values of the local measurements. This requires the MG to create an RTCP XR packet with metrics blocks (according to *xrbr/srb*) containing these most recent measurements, triggered on demand by the AuditValue or Subtract request. + +An MGC may suspend collection of locally-measured RTCP XR metrics with block-level granularity by sending a modified property *xrbr/srb* that does not include the block or blocks. The suspended block(s) maintain their value until Subtract, unless a further modified value of *xrbr/srb* is sent which includes a previously-suspended block or blocks. If this occurs the statistic is reset and re-enabled. See also *Practices on Statistics* in Appendix IV of [ITU-T H.248.1 Amd.2]. + +A use case for auditing statistics values (via AuditValue) and reset arises as follows. An MGC may modify an ephemeral termination during its lifetime with changed (remote destination connection) endpoint information in the remote descriptor such that it receives RTP packets from a different source, and in this case the MGC may audit and reset statistics near the time of modification so that the MGC has independent statistics for the RTP data received from the two sources. + +However, it may be undesirable to reset values of metrics that are measured locally and sent to remote RTP systems, because the remote RTP system may be unaware of the reset action and may infer false information about the quality of the IP transport connection between the RTP systems. Because RTCP XR tags metrics blocks with the synchronization source (SSRC) identifier for the source of the measured packets, it is not normally necessary to reset statistics on a termination when a termination is modified to receive packets from another source. However, this requires the MG to maintain (typically until Subtract) statistics for RTP sources which are no longer active. + +There is a known use case where the MGC may not be aware that the remote RTP source has changed and therefore may not be able to use an audit-and-reset sequence to ensure separation of metrics related to the two sources. This arises when an MG receives RTP packets from a border device (RTP translator) performing network address and port translation. An RTP session re-arrangement may take place on the far side of the border device, causing the MG to receive packets sourced by a different RTP system, without any MGC involvement or change in the MG's remote descriptor for the termination. However, the SSRC in received RTP media packets will change (it is not modified by a border device which is an RTP translator). In this case, MG awareness of SSRC and maintenance of per-SSRC metrics is the only reliable method of separating packet metrics relevant to the two (or more) remote RTP sources beyond the border device. + +### 6.6.9 MGC Procedure to determine the type of an RTP system + +It is assumed that the MGC and MG use the RTCP source description package *rtcpsdes* [b-ITU-T H.248.71] so that the MGC is able to translate dynamically-assigned SSRC identifiers in RTCP XR report blocks into the stable canonical names of the RTP systems involved in the RTP session. SSRC and CNAME data items provided in package *rtcpsdes* are identified by the MG as belonging either to the MG, to a remote RTP end system, or to a remote RTP translator. + +### 6.6.10 Use of cumulative and interval reports + +The RTCP XR reports all have two variants, interval (accumulated only since the last report, per source SSRC) and cumulative (accumulated over the lifetime of the RTP session to date, per source SSRC). + +Usually the cumulative report is a better match to typical ITU-T H.248 use cases where the MGC receives a report only on Subtract, and it is desirable that this report should contain information about the whole lifetime of the RTP session rather than only about the last few seconds before the Subtract. + +### 6.6.11 Coding example for a complete RTCP XR packet + +The following example shows the text coding of a complete RTCP XR packet containing: + +- an RTCP XR header and +- Receiver Reference Time Report block (see clause 4.4 of [IETF RFC 3611]), + +These are encoded according to the text encoding of Octet String described in clause B.3 of [ITU-T H.248.1 Amd.2]. The structure of this packet is shown in Figure 3, together with the hexadecimal values assumed in this coding example. + +The packet shown in Figure 3 below is coded according to the text encoding rules as the following string of length 40 characters for transmission as one of the Octet String elements of statistic *xrbr/xrpkt* across the ITU-T H.248 interface: + +"01F300B09EAE7B5D20000040000000004B0A9F08" + +![Diagram showing the structure of an RTCP XR packet at the RTP interface. It includes a header with Version (V=2), Packet (P), Reserved, PT=XR=207, and Length. The SSRC is 79 75 DE BA. The first report block has BT=4, a 0 separator, Reserved, and Block length=2. It includes NTP timestamps (most and least significant words) with values 00 00 00 00 and D2 50 F9 10. Hexadecimal values for each field are listed on the right.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------|---|----------|---|---|---------------|---|---|---|------------------|--------|---|---|---|---|---|---|---|---|---|----|----|----|----|----|---|---|---|---|---|---|---|--| +| 0 | | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | | | | | | | | +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | | +| V = 2 | P | Reserved | | | PT = XR = 207 | | | | | Length | | | | | | | | | | 80 | CF | 00 | 0D | | | | | | | | | | +| SSRC | | | | | | | | | | | | | | | | | | | | 79 | 75 | DE | BA | | | | | | | | | | +| BT = 4 | | | | 0 | Reserved | | | | Block length = 2 | | | | | | | | | | | | 04 | 00 | 00 | 02 | | | | | | | | | +| NTP timestamp, most significant word | | | | | | | | | | | | | | | | | | | | 00 | 00 | 00 | 00 | | | | | | | | | | +| NTP timestamp, least significant word | | | | | | | | | | | | | | | | | | | | D2 | 50 | F9 | 10 | | | | | | | | | | + +H.248.48(12)\_F03 + +Diagram showing the structure of an RTCP XR packet at the RTP interface. It includes a header with Version (V=2), Packet (P), Reserved, PT=XR=207, and Length. The SSRC is 79 75 DE BA. The first report block has BT=4, a 0 separator, Reserved, and Block length=2. It includes NTP timestamps (most and least significant words) with values 00 00 00 00 and D2 50 F9 10. Hexadecimal values for each field are listed on the right. + +**Figure 3 – Structure of an RTCP XR packet at the RTP interface** + +# Bibliography + +- [b-ITU-T H.248.30] Recommendation ITU-T H.248.30 (2007), *Gateway control protocol: RTCP extended performance metrics packages*. +- [b-ITU-T H.248.47] Recommendation ITU-T H.248.47 (2007), *Gateway control protocol: Statistic conditional reporting package*. +- [b-ITU-T H.248.71] Recommendation ITU-T H.248.71 (2010), *Gateway control protocol: RTCP support packages*. +- [b-ITU-T M.2301] Recommendation ITU-T M.2301 (2002), *Performance objectives and procedures for provisioning and maintenance of IP-based networks*. +- [b-IANA RTCP XR] IANA Registry of RTCP XR Block Types at +<> +- [b-IETF RFC 5117] IETF RFC 5117 (2007), *RTP Topologies*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.49-200708-I_PDF-E/raw.md b/marked/H/T-REC-H.248.49-200708-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c4566f9e6866a86e86b9313612362f0d6aa8379f --- /dev/null +++ b/marked/H/T-REC-H.248.49-200708-I_PDF-E/raw.md @@ -0,0 +1,799 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.49** + +(08/2007) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Session description +protocol RFC and capabilities packages** + +ITU-T Recommendation H.248.49 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Gateway control protocol: Session description protocol RFC and capabilities packages** + +## **Summary** + +ITU-T Recommendation H.248.1 uses the session description protocol (SDP) to convey information in the local and remote descriptors of the text encoding of the protocol. Typically this SDP has been based on the use of IETF RFC 2327. New variants of SDP have been developed which contain some incompatibilities with IETF RFC 2327. ITU-T Recommendation H.248.49 allows a media gateway controller to firstly determine which SDP IETF RFC the media gateway is compliant to, as well as being able to determine the SDP capabilities. This allows greater interoperability between the media gateway controller and media gateway. + +###### **Source** + +ITU-T Recommendation H.248.49 was approved on 29 August 2007 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Terms and definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Session Description Protocol RFC Package ..... | 2 | +| 6.1 Properties..... | 3 | +| 6.2 Events ..... | 3 | +| 6.3 Signals ..... | 3 | +| 6.4 Statistics..... | 3 | +| 6.5 Error codes..... | 3 | +| 6.6 Procedures ..... | 3 | +| 7 Session description protocol capabilities package..... | 5 | +| 7.1 Properties..... | 5 | +| 7.2 Events ..... | 10 | +| 7.3 Signals ..... | 10 | +| 7.4 Statistics..... | 10 | +| 7.5 Error codes..... | 10 | +| 7.6 Procedures ..... | 11 | +| Appendix I – Comparison of SDP variants between RFC 4566 and RFC 2327 ..... | 12 | +| I.1 Introduction ..... | 12 | +| I.2 RFC 4566 versus RFC 2327 ..... | 13 | +| I.3 Specific impact on H.248/SDP..... | 20 | + + + +# **Gateway control protocol: Session description protocol RFC and capabilities packages** + +# **1 Scope** + +When the text encoding of [ITU-T H.248.1] is used, local descriptors (LD) and remote descriptors (RD) consisting of "session" descriptions are based on the session description protocol (SDP) (clause 7.1.8 of [ITU-T H.248.1]). As a result, SDP information elements are embedded in the H.248 protocol syntax. The encoder/decoder for H.248 Messages for Annex B of [ITU-T H.248.1] text mode therefore comprises of an SDP encoder/decoder in addition to the basic H.248 encoder/decoder. + +There are multiple versions of H.248.1, and multiple variants of SDP [IETF RFC 2327], and [IETF RFC 4566]. H.248 versions and SDP variants are orthogonal in the sense, that principally any H.248 version could be operated with any SDP variant. However, there are dependencies due to the history concerning the different timelines of H.248.1 and SDP developments, e.g.,: + +- H.248.1 Version 1 (03/2002) is based on SDP [IETF RFC 2327]; +- H.248.1 Version 2 (05/2002) is based on SDP [IETF RFC 2327]; or +- H.248.1 Version 3 (09/2005) is based on SDP [IETF RFC 2327]. + +The protocol versioning of H.248 and SDP, as well as backward compatibility, requires a negotiation mechanism to select a common H.248 protocol version as well as a common SDP RFC for the text-based encoding of LD and RD on MGC and MG side. Whereas H.248 protocol version negotiation is already supported by H.248 ServiceChange elements, an explicit mechanism is still missing for SDP version determination. + +This Recommendation enables a media gateway controller to determine which SDP RFC a media gateway supports. Once the SDP RFC has been determined the media gateway controller can then indicate to the media gateway which SDP RFC version it will use. + +SDP based on [IETF RFC 4566] may be of use when a media gateway controller is already using [IETF RFC 4566] in its call/session control protocols. + +By setting a particular SDP RFC version, the MG will behave as if all references in H.248.1 to the use of [IETF RFC 2327] have been replaced by that particular version of SDP RFC. + +In order for media gateway controllers and media gateways to be backward compatible, they shall support [IETF RFC 2327] even if a new SDP RFC is also supported. + +In addition to providing a capability to determine the supported SDP RFC, this Recommendation provides the capability to determine which SDP parameters the MG supports. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] ITU-T Recommendation H.248.1 (2005), *Gateway control protocol: Version 3*. + +- [IETF RFC 2327] IETF RFC 2327 (1998), *SDP: Session Description Protocol*. +[IETF RFC 3266] IETF RFC 3266 (2002), *Support for IPv6 in Session Description Protocol (SDP)*. +[IETF RFC 4566] IETF RFC 4566 (2006), *SDP: Session Description Protocol*. + +# 3 Terms and definitions + +## 3.1 Terms defined elsewhere + +*None.* + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 AuditCapabilities.req:** H.248.1 AuditCapabilities command request. + +**3.2.2 AuditValue.req:** H.248.1 AuditValue command request. + +**3.2.3 SDP RFC:** The IETF RFCs for SDP specifications are **not** explicitly denoted as "protocol versions" (Note 1). The H.248.49 property "SDP RFC" shall be related to the definition. + +NOTE 1 – The SDP "v=" line is aimed at signalling the SDP protocol version. Nevertheless, all existing SDP RFCs [IETF RFC 2327] and [IETF RFC 3266] define protocol version 0 (see clause 5.1 in [IETF RFC 4566]: "The "v=" field gives the version of the Session Description Protocol. This memo defines version 0. There is no minor version number.") + +NOTE 2 – The SDP "o=" line contains the "version number of the session description" (field ). This session version should not be confused with the SDP or H.248.1 protocol version. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|------------------------------| +| LD | Local Descriptor | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| RD | Remote Descriptor | +| SDP | Session Description Protocol | + +# 5 Conventions + +*None.* + +# 6 Session Description Protocol RFC Package + +Package Name: Session Description Protocol RFC + +PackageID: sdpr (0x00bb) + +Description: This package allows the MGC to determine which SDP RFCs the MG supports. It also allows the MGC to choose and indicate to the MG which SDP RFC both the MG and the MGC can support and shall use for the control association. + +Version: 1 + +Extends: None + +## 6.1 Properties + +### 6.1.1 SDP RFC + +Property Name: SDP RFC +PropertyID: RFC (0x0001) +Description: This property indicates the supported SDP RFC. +Type: Integer +Possible values: The IETF RFC number that defines the SDP RFC. +E.g., +2327 for RFC 2327 +3266 for RFC 3266 +NOTE – Support of RFC 3266 implies support of RFC 2327 also. +4566 for RFC 4566 +Default: 2327 +Defined in: TerminationState (Root Termination only) +Characteristics: Read/Write + +## 6.2 Events + +*None.* + +## 6.3 Signals + +*None.* + +## 6.4 Statistics + +*None.* + +## 6.5 Error codes + +### 6.5.1 Invalid SDP Syntax + +Error Code #: 474 +Name: Invalid SDP Syntax +Definition: The SDP received by the MG contains invalid or unexpected syntax according to the expected SDP RFC syntax. +Error Text in the Error Descriptor: None +Comment: The command is disregarded. + +## 6.6 Procedures + +### 6.6.1 Version determination and specification + +As a general rule, upon establishment of a new H.248 control association and before the MGC has modified the MG's Root termination LocalControl descriptor property *sdpr/RFC*, both the MGC and the MG should implicitly assume that the default SDP [IETF RFC 2327] is used within this H.248 control association where [ITU-T H.248.1] version 1, 2 or 3 is used. However, this default may change if a H.248 profile is negotiated. + +If the MGC wants to modify the SDP RFC to be used within this H.248 control association, it should first send an AuditCapability request for the Root termination with an Audit descriptor containing the LocalControl *sdpr/RFC* property, e.g., + +``` +AuditCapability = ROOT { + Audit { + Media { + LocalControl { + sdpr/RFC + } + } + } +} +``` + +The MG's reply would then contain a list of all possible SDP RFC values the MG supports according to clause 7.2.6 of [ITU-T H.248.1]. + +The MGC may then issue a Modify request for the Root termination containing a LocalControl descriptor including the *sdpr/RFC* property with a single property value which should be equal to one of the values contained in the list the MG returned in the AuditCapability response. If the MG supports the requested SDP RFC, according to standard [ITU-T H.248.1] rules, it answers positively to the Modify request. + +From this point in time onwards, the SDP exchanged between MGC and MG in local and remote descriptors is understood to comply to the SDP RFC set by the MGC in the Modify command on the Root termination. This is applicable to both text and binary implementations as binary implementations may use Annex C of [ITU-T H.248.1] SDP properties. + +It is not recommended to change the Root termination property *sdpr/RFC* after the first call-related H.248 context had been created within the newly established H.248 control association. The MGC should only modify the *sdpr/RFC* property of the Root termination immediately after any ServiceChange procedure resulting in the setting or negotiation of the H.248.1 version and before the first local or remote descriptor is being exchanged between MGC and MG. If terminations are already instantiated at the setting of the *sdpr/RFC* property, the MGC and MG shall use the new SDP RFC for these terminations. If mismatches occur between the old and new SDP RFCs for these terminations for subsequent signalling altering the local and remote descriptors, then error code 474 "Invalid SDP Syntax" should be used. + +### 6.6.2 Unsuccessful root property modification + +If the MG receives a Modify request for the Root termination containing an unsupported *sdpr/RFC* SDP RFC value, it should answer with error code 449 "Unsupported or Unknown Parameter or Property value". In this case, the value of the *sdpr/RFC* property remains unchanged and the previously used SDP RFC syntax continues to be used. + +### 6.6.3 Unsuccessful LD or RD descriptor modification + +If the MG receives a Modify request to modify the LD or RD encoded according to a non-set SDP RFC value, it should answer with error code 474 "Invalid SDP Syntax". + +# 7 Session description protocol capabilities package + +Package Name: Session Description Protocol Capabilities Package + +PackageID: sdpc (0x00bc) + +Description: This package allows the MGC to determine which SDP capabilities are supported on the MG. The IANA SDP parameters registry provides a list of parameters that may be implemented on a MG. By auditing the properties respectively corresponding to these parameters, the MGC can determine the parameters and their values that it can use. + +The support of parameters associated with the following registries can be determined: + +- proto +- bwttype +- nettype +- addrttype +- enckey +- att-field (session level) +- att-field (both session and media level) +- att-field (media level only) +- att-field (unknown level) +- content +- group SDP attribute +- rtcp-fb attribute +- ack and nack +- RTSP Key management + +Where parameters include the SLASH "/", these instances should be replaced with a "\" in order to meet the ABNF syntax rules for the VALUE construct. + +Version: 1 + +Extends: None + +## 7.1 Properties + +### 7.1.1 Proto Registry + +Property Name: Proto Registry + +PropertyID: proto (0x0001) + +Description: This property represents the values that can be associated with the type "proto". + +Type: Sub-list of String + +Possible values: As per the "SDP name" values associated with the "proto" registry at . + +E.g., RTP\AVP + +Default: Provisioned + +Defined in: TerminationState + +Characteristics: Read-only + +### 7.1.2 Bwtype Registry + +Property Name: Bwtype Registry +PropertyID: bwtype (0x0002) +Description: This property represents the values that can be associated with the type "bwtype". +Type: Sub-list of String +Possible values: As per the "SDP name" values associated with the "bwtype" registry at . +E.g., CT +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### 7.1.3 Nettype Registry + +Property Name: Nettype Registry +PropertyID: nettype (0x0003) +Description: This property represents the values that can be associated with the type "nettype". +Type: Sub-list of String +Possible values: As per the "SDP name" values associated with the "Nettype" registry at . +E.g., IN +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### 7.1.4 Addrtype Registry + +Property Name: Addrtype Registry +PropertyID: addrtype (0x0004) +Description: This property represents the values that can be associated with the type "addrtype". +Type: Sub-list of String +Possible values: As per the "SDP name" values associated with the "addrtype" registry at . +E.g., IP4 +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### 7.1.5 Enckey Registry + +Property Name: Enckey Registry +PropertyID: enckey (0x0005) +Description: This property represents the values that can be associated with the type "enckey". +Type: Sub-list of String +Possible values: As per the "SDP name" values associated with the "enckey" registry at . +E.g., clear +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### 7.1.6 Att-field (session level) Registry + +Property Name: Att-field (session level) +PropertyID: attsess (0x0006) +Description: This property represents the values that can be associated with the type "att-field (session level)". +Type: Sub-list of String +Possible values: As per the "SDP name" values associated with the "att-field (session level)" registry at . +E.g., cat +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### 7.1.7 Att-field (both session and media level) Registry + +Property Name: Att-field (session and media level) +PropertyID: attsessmed (0x0007) +Description: This property represents the values that can be associated with the type "att-field (session and media level)". +Type: Sub-list of String +Possible values: As per the "SDP name" values associated with the "att-field (session and media level)" registry at . +E.g., lang +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +#### **7.1.8 Att-field (media level only) Registry** + +Property Name: Att-field (media level only) +PropertyID: attmed (0x0008) +Description: This property represents the values that can be associated with the type "att-field (media level only)". +Type: Sub-list of String +Possible values: As per the "SDP name" values associated with the "att-field (media level only)" registry at . +E.g., ptime +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +#### **7.1.9 Att-field (unknown level) Registry** + +Property Name: Att-field (unknown level) +PropertyID: attunk (0x0009) +Description: This property represents the values that can be associated with the type "att-field (unknown level)". +Type: Sub-list of String +Possible values: As per the "SDP name" values associated with the "att-field (unknown level)" registry at . +E.g., eecid +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### **7.1.10 Content Registry** + +Property Name: Content Registry +PropertyID: content (0x000a) +Description: This property represents the values that can be associated with the type content. +Type: Sub-list of String +Possible values: As per the "SDP name" values associated with the "content" registry at . +E.g., slides +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +#### 7.1.11 Group SDP Attribute Registry + +Property Name: Group SDP Attribute Registry +PropertyID: group (0x000b) +Description: This property represents the values that can be associated with the "group" SDP attribute. +Type: Sub-list of String +Possible values: As per the "Token" values associated with the "group" SDP attribute registry at . +E.g., FID +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### 7.1.12 RTCP-FB Attributes Values + +Property Name: RTCP-FB Attributes Values +PropertyID: rtpfbval (0x000c) +Description: This property represents the values that can be associated with the "rtcp-fb" attribute. +Type: Sub-list of String +Possible values: As per the "Value Name" values associated with the "rtcp-fb attribute value" registry at . +E.g., trr-int +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### 7.1.13 "ack" Attributes Values + +Property Name: "ack" Attributes Values +PropertyID: ackval (0x000d) +Description: This property represents the values that can be associated with the "ack" attribute. +Type: Sub-list of String +Possible values: As per the "Value Name" values associated with the "ack attribute value" registry at . +E.g., rpsi +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### 7.1.14 "nack" Attributes Values + +Property Name: "nack" Attributes Values +PropertyID: nackval (0x000e) +Description: This property represents the values that can be associated with the "nack" attribute. +Type: Sub-list of String +Possible values: As per the "Value Name" values associated with the "nack attribute value" registry at ). +E.g., sli +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +### 7.1.15 SDP/RTSP Key management protocol identifier values + +Property Name: SDP/RTSP Key management protocol identifier values +PropertyID: kmpidval (0x000f) +Description: This property represents the values that can be associated with the "SDP/RTSP Key management protocol identifiers". +Type: Sub-list of String +Possible values: As per the "Value Name" values associated with the "SDP/RTSP Key management protocol identifiers" registry at . +E.g., mikey +Default: Provisioned +Defined in: TerminationState +Characteristics: Read-only + +## 7.2 Events + +*None.* + +## 7.3 Signals + +*None.* + +## 7.4 Statistics + +*None.* + +## 7.5 Error codes + +As per clause 6.5.1. + +## 7.6 Procedures + +Auditing of the local and remote descriptors to determine SDP capabilities may return varying results depending on the implementation. + +In order to determine which SDP capabilities are supported on a MG in a standardized way, the MGC should perform an AuditValue.req on the properties defined in this package. A wildcarded AuditValue.req on the package may be used to determine all SDP capabilities, e.g., "*sdpc/\**". + +The parameters and their values that may be returned are defined in the IANA SDP parameter registry. + +As a result of the AuditValue.req, the MG should return the values supported by it. Where multiple values are supported, these shall be returned as a sub-list. If the MG cannot support a SDP parameter corresponding to a property audit by the MGC, the MG should return empty value for the property to the MGC. + +# Appendix I + +## Comparison of SDP variants between RFC 4566 and RFC 2327 + +(This appendix does not form an integral part of this Recommendation) + +This appendix provides a comparison between the two core RFCs for SDP. + +## I.1 Introduction + +Local descriptor (LD) and remote descriptor (RD) consisting of "session" descriptions are based on the session description protocol (SDP) when *text encoding* is used for the H.248 gateway control protocol (see clause 7.1.8 of [ITU-T H.248.1]). SDP information elements are as a consequence embedded in the H.248 protocol syntax. The "*text codec*" for H.248 Messages (i.e., the encoder/decoder for Annex B of [ITU-T H.248.1] text mode) comprises therefore an SDP encoder/decoder in addition to the basic H.248 encoder/decoder. + +The core SDP is specified in [IETF RFC 4566], which obsoletes [IETF RFC 2327]. There are many additional RFCs available, which extend SDP. Figure I.1 illustrates the purpose of this Appendix and indicates *only some* other SDP RFCs, which may be of particular importance for H.248/SDP implementations. + +SDP evolution (1998-2006): + +![Diagram showing SDP evolution from 1998 to 2006. It tracks the development of SDP from RFC 2327 to RFC 4566, showing various extensions and their relevance to H.248/SDP.](51db757d054ce1ce83c436a3578b56ca_img.jpg) + +The diagram illustrates the evolution of SDP (Session Description Protocol) from 1998 to 2006. It shows the progression from the initial RFC 2327 to the current RFC 4566, with various extensions and their relevance to H.248/SDP. + +**SDP Evolution (1998-2006):** + +- IETF RFC 2327** (SDP: Session description protocol 04/1998) is the starting point. It is extended by **IETF RFC 3108** (Conventions for the use of the SDP for ATM bearer connections 05/2001). +- IETF RFC 3108** has many elements applicable for H.248 ephemeral terminations in general (e.g., IP). +- IETF RFC 3266** (Support for IPv6 in SDP 06/2002) is an extension of RFC 2327. +- IETF RFC 4566** (SDP: Session description protocol 07/2006) obsoletes RFCs 2327 and 3266. It is the primary focus of this appendix. +- IETF RFC 4567** (Key management extensions for SDP and RTSP 07/2006) and **IETF RFC 4568** (SDP Security descriptions for media streams 07/2006) are extensions of RFC 4566. A recommendation for the "k=" line is made for RFC 4568. +- Further SDP extensions (relevant for H.248/SDP):** + - IETF RFC 3605** (RTCP attribute in SDP 10/2003) + - IETF RFC 3890** (A transport independent bandwidth modifier for the SDP 09/2004) + - IETF RFC 4570** (SDP Source filters 07/2006) + - others... + +**Prime scope of this Appendix:** RFC 4566 obsoletes RFCs 2327 and 3266. + +**should be compliant (?):** This label indicates that RFC 3108, RFC 4567, and RFC 4568 should be compliant with the core SDP. + +**Recommendation for "k=" line:** This label indicates a recommendation for the "k=" line in RFC 4568. + +H248.49(07)F\_I\_01 + +Diagram showing SDP evolution from 1998 to 2006. It tracks the development of SDP from RFC 2327 to RFC 4566, showing various extensions and their relevance to H.248/SDP. + +Figure I.1 – SDP evolution and primary scope of this appendix + +The differences between [IETF RFC 4566] and [IETF RFC 2327] are listed in clause I.2. Specific conclusions for H.248/SDP implementations are summarized in clause I.3. + +### I.1.1 Warning + +The analysis of this appendix is based on a reverse engineering activity. The list of identified differences might be therefore incomplete. Implementers are also encouraged to check the latest maintenance updates (IETF RFC Errata): + +- IETF RFC 2327: see +- IETF RFC 4566: see + +## I.2 RFC 4566 versus RFC 2327 + +Protocol syntax and semantics are compared below. + +### I.2.1 SDP line specification (RFC 4566, clause 5) + +This clause compares the SDP "=" structures. Only different specifications are listed here. + +#### I.2.1.1 RFC 4566, clause 5.2: Origin, "o=" line + +**Table I.1 – RFC 4566 versus RFC 2327 – SDP specification – "o=" line** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| 1. | o=




| o=




| No.

Description is different, but SDP grammar is identical (see clause I.2.4). | + +#### I.2.1.2 RFC 4566, clause 5.6: Email Address and Phone Number, "e=" and "p=" lines + +**Table I.2 – RFC 4566 versus RFC 2327 – SDP specification – "e=" and "p=" lines** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 2. | Inclusion of an email address or phone number is OPTIONAL.

Note that the previous version of SDP specified that either an email field or a phone field MUST be specified, but this was widely ignored. The change brings the specification into line with common usage. | Either an email field or a phone field MUST be specified. | Yes.

A RFC 4566 implementation peering a RFC 2327 implementation should include either a "e=" or a "p=" line when considering strict backward compatibility. | + +##### I.2.1.3 RFC 4566, clause 5.7: Connection Data, "c=" line + +**Table I.3 – RFC 4566 versus RFC 2327 – SDP specification – "c=" line** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|----------------------------------------------------|------------------------------------------------------------|---------------------------------------------------------------------------------------| +| 3. | c=

| c=

| No.

Description is different, but SDP grammar is identical (see clause I.2.4). | + +##### I.2.1.4 RFC 4566, clause 5.8: Bandwidth, "b=" line + +**Table I.4 – RFC 4566 versus RFC 2327 – SDP specification – "b=" line** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|----------------------------|------------------------------------|---------------------------------------------------------------------------------------| +| 4. | b=:
| b=:
| No.

Description is different, but SDP grammar is identical (see clause I.2.4). | + +##### I.2.1.5 RFC 4566, clause 5.10: Repeat times, "r=" line + +**Table I.5 – RFC 4566 versus RFC 2327 – SDP specification – "r=" line** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| 5. | r=

| r=

| No.

Description is different, but SDP grammar is identical (see clause I.2.4). | + +#### I.2.1.6 RFC 4566, clause 5.12: Encryption Keys, "k=" line + +**Table I.6 – RFC 4566 versus RFC 2327 – SDP specification – "k=" line** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6. | MAY be used to convey encryption keys.

A simple mechanism for key exchange is provided by the key field ("k="), although this is primarily supported for compatibility with older implementations and its use is NOT RECOMMENDED. Work is in progress to define new key exchange mechanisms for use with SDP RFC 4567 and RFC 4568, and it is expected that new applications will use those mechanisms. | Entirely supported. | Yes.

A RFC 4566 implementation peering a RFC 2327 implementation may have to include an RFC 2327 compliant "k=" line when considering strict backward compatibility. | + +#### I.2.1.7 RFC 4566, clause 5.14: Media descriptions, "m=" line + +**Table I.7 – RFC 4566 versus RFC 2327 – SDP specification – "m=" line** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|-----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7. | m=



... | m=


| No.

Description is different, but SDP grammar is identical (see clause I.2.4). | +| 8. | Supported media types:
"audio",
"video",
"text",
"application",
"message",
-
- | Supported media types:
"audio",
"video",
-
"application",
-
"data",
"control" |

No.
No.
Yes, backward compatibility.
No.
Yes, backward compatibility.
Yes, forward compatibility.
Yes, forward compatibility. | + +### I.2.2 SDP attribute specification (RFC 4566, clause 6) + +##### I.2.2.1 RFC 4566, "a=" attribute + +The ABNF syntax of [IETF RFC 2327] does not support the use of "-" in an attribute name however despite stating that attribute names must be in the US-ASCII subset of ISO/IEC 10646/UTF-8. The ABNF syntax of [IETF RFC 4566] was updated to support the inclusion of "-" to address this inconsistency. Therefore, the use of attribute names containing "-" is problematic for RFC 2327 implementations as several examples of attribute names containing "-" were registered prior to the definition of [IETF RFC 4566]. RFC 2327 implementers may consider exceptions when parsing an "a=" where attribute names containing "-" are involved. + +Beyond the addition of "-" in attribute names, the RFC 4566 ABNF "token" syntax defines additional characters (see item 22 in clause I.2.4.2) that would also pose similar problems. + +##### I.2.2.2 RFC 4566, clause 6: "a=fmtp" attribute + +**Table I.8 – RFC 4566 versus RFC 2327 – SDP specification – "a=fmtp" attribute** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|----------------------------------------------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 9. | a=fmtp: | a=fmtp: | Yes. RFC 4566 clarified the use as following: "At most one instance of this attribute is allowed for each format." This was added to maintain the mapping to media type parameters.

Implementers should be aware that there are uses which leverage multiple instances of the "a=fmtp" SDP attribute per media format, e.g., RFC 3189. | + +##### I.2.2.3 RFC 4566, clause 6: "a=maxptime" attribute + +**Table I.9 – RFC 4566 versus RFC 2327 – +SDP specification – "a=maxptime" attribute** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|--------------------------------------|----------|-------------------------------| +| 10. | a=maxptime:
| – | Yes, not backward compatible. | + +#### I.2.2.4 RFC 4566, clause 6: "a=inactive" attribute + +**Table I.10 – RFC 4566 versus RFC 2327 – SDP specification – "a=inactive" attribute** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|------------|----------|-------------------------------| +| 11. | a=inactive | – | Yes, not backward compatible. | + +#### I.2.2.5 RFC 4566, clause 6: "a=orient" attribute + +**Table I.11 – RFC 4566 versus RFC 2327 – SDP specification – "a=orient" attribute** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|----------------------------|---------------------------------------|--------------------------------------------------------------------------------| +| 12. | a=orient:
| a=orient:
| No. Description is different, but SDP grammar is identical (see clause I.2.4). | + +### I.2.3 Experimental parameters in some SDP lines + +The RFC 2327 "x-" prefix notation for experimental parameters is disallowed or deprecated in [IETF RFC 4566]. This affects the following SDP lines or attributes, which had an "x-" support in [IETF RFC 2327]. + +**Table I.12 – RFC 4566 versus RFC 2327 – +SDP specification – SDP lines with experimental parameters** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| 13. | "b=" line: "X-" for

Use of the "X-" prefix is NOT RECOMMENDED. | "b=" line: "X-" for

Use of the "X-" prefix is principally allowed. | No backward compatibility issue. Forward compatibility should be also no issue because RFC 4566 parser MUST ignore "unknown" modifiers. | +| 14. | "a=" line: "X-" not allowed

If an attribute is received that is not understood, it MUST be ignored by the receiver. | "a=" line: "X-" allowed

Unregistered attributes should begin with "X-" to prevent inadvertent collision with registered attributes. In either case, if an attribute is received that is not understood, it should simply be ignored by the receiver. | ditto | + +**Table I.12 – RFC 4566 versus RFC 2327 – +SDP specification – SDP lines with experimental parameters** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| +| 15. | "a=rtpmap" attribute:
"X-" not allowed. | "a=rtpmap" attribute:
"X-" allowed.

Experimental encoding
formats can also be specified
using rtpmap. RTP formats
that are not registered as
standard format names must
be preceded by "X-". | No backward compatibility
issue, but forward
compatibility problem. | + +### **I.2.4 SDP grammar (RFC 4566, clause 10)** + +The SDP grammar was revised. There are two types of changes: + +- Renaming of tokens; +- Extension of grammar. + +Both changes are not backward compatible (BC) in different manners. Token renaming requires a local adaptation of the "SDP served user instance" concerning an aligned token naming scheme. Grammar extensions are principally not interoperable between different SDP variants. + +#### I.2.4.1 Token renamings + +See Table I.13. + +**Table I.13 – RFC 4566 versus RFC 2327 – SDP grammar – Token renamings** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| 16. | session-description = proto-version
origin-field
session-name-field
information-field
uri-field
email-fields
phone-fields
connection-field
bandwidth-fields
time-fields
key-field
attribute-fields
media-descriptions | announcement = proto-version
origin-field
session-name-field
information-field
uri-field
email-fields
phone-fields
connection-field
bandwidth-fields
time-fields
key-field
attribute-fields
media-descriptions | Token renaming | +| 17. | origin-field = %x6f "=" username
SP sess-id SP sess-version SP
nettype SP addrtype SP unicast-
address CRLF | origin-field = "o=" username space
sess-id space sess-version space
nettype space addrtype space addr
CRLF | Token renaming | +| 18. | connection-address = multicast-
address / unicast-address | connection-address = multicast-
address addr | Token renaming | +| 19. | email-address = address-and-
comment / dispname-and-address /
addr-spec

address-and-comment = addr-spec
1*SP "(" 1*email-safe ")"

dispname-and-address = 1*email-
safe 1*SP "<" addr-spec ">" | email-address = email email
"(" email-safe ")" email-safe "<"
email ">"

email = ;defined in RFC 822 | Token renaming | +| 20. | "k=" line:

The "key-data" token (RFC 2327) was replaced by the "text" and "base64" token in RFC 4566. | | Token renaming | +| 21. | Others: TBD. | | | + +#### I.2.4.2 Grammar extensions + +See Table I.14. + +**Table I.14 – RFC 4566 versus RFC 2327 – SDP grammar – Grammar extensions** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| 22. | ; Generic for other address families

extn-addr = non-ws-string
NOTE – This extension is applicable for unicast and multicast addresses. | Not defined | Grammar extension | +| 23. | The " token " (RFC 4566) corresponds to " alpha-numeric " (RFC 2327) field. The grammar or " token " was extended to a superset of " alpha-numeric ":

token = 1*(token-char)
token-char = %x21 / %x23-27 / %x2A-2B / %x2D-2E / %x30-39 / %x41-5A / %x5E-7E | alpha-numeric = ALPHA DIGIT
DIGIT = "0" POS-DIGIT
POS-DIGIT = "1" "2" "3" "4" "5" "6" "7" "8" "9"
ALPHA = "a" "b" "c" "d" "e" "f" "g" "h" "i" "j" "k" "l" "m" "n" "o" "p" "q" "r" "s" "t" "u" "v" "w" "x" "y" "z" "A" "B" "C" "D" "E" "F" "G" "H" "I" "J" "K" "L" "M" "N" "O" "P" "Q" "R" "S" "T" "U" "V" "W" "X" "Y" "Z" | | +| | Result:
Additional grammar of " token ":
%x21 / %x23-27 / %x2A-2B / %x2D-2E / %x5E-60 / %x7B-7E
i.e., the ASCII characters:
"!", "#", "\$", "%", "&", "'", "*", "+", "-", ".", "^", "_", "`", "{", " ", "}", "~".
The " Token " is used in RFC 4566 SDP fields:
(a) nettype , (b) addrtype , (c) bwtype , (d) att-field , (e) media , (f) fmt , and (g) proto . | | | +| 24. | Others: TBD . | | | + +#### I.2.4.3 Summary of impacted SDP lines + +The above changes may affect the following SDP lines, see Table I.15. + +**Table I.15 – RFC 4566 versus RFC 2327 – Summary of impacted SDP lines** + +| Item | RFC 4566 | Change | +|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| 25. | Session description
v= (protocol version)
o= (originator and session identifier)
s= (session name)
i=* (session information)
u=* (URI of description)
e=* (email address)
p=* (phone number)
c=* (connection information)
b=* (zero or more bandwidth information lines)
z=* (time zone adjustments)
k=* (encryption key)
a=* (zero or more session attribute lines) |
No
No
No
No
No
Yes
No
No
No
No
Yes
Yes | +| 26. | Time description
t= (time the session is active)
r=* (zero or more repeat times) |
No
No | +| 27. | Media description, if present
m= (media name and transport address)
i=* (media title)
c=* (connection information -- optional if included at session level)
b=* (zero or more bandwidth information lines)
k=* (encryption key)
a=* (zero or more media attribute lines) |
Yes
No
No
No
Yes
Yes | + +#### I.2.4.4 Grammar baseline + +See Table I.16. + +**Table I.16 – RFC 4566 versus RFC 2327 – ABNF usage** + +| Item | RFC 4566 | RFC 2327 | Impact? | +|------|----------------------------|----------------------------|---------| +| 28. | ABNF according to RFC 4234 | ABNF according to RFC 2234 | None. | + +This table is for information only. The underlying ABNF syntax does not have any implication on SDP implementations. + +## I.3 Specific impact on H.248/SDP + +All identified changes in the SDP specification may principally affect H.248/SDP interfaces. Particular attention should be given to the two SDP lines for *media name and transport address* ("m=") and *media attribute* ("a=") specifications. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.5-200912-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.248.5-200912-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8073c3055abc7731de1ae66c36e362f11443a0c --- /dev/null +++ b/marked/H/T-REC-H.248.5-200912-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b4de5adc1d3cdb5e156cd79f5bd52f6701f25e443a1f8d3f0d1dce155ed63f9 +size 7472 diff --git a/marked/H/T-REC-H.248.50-201607-I_PDF-E/raw.md b/marked/H/T-REC-H.248.50-201607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f350fbf777f68565e915fe4ddeb00300d252bce1 --- /dev/null +++ b/marked/H/T-REC-H.248.50-201607-I_PDF-E/raw.md @@ -0,0 +1,2717 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.50** + +(07/2016) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: NAT traversal toolkit +packages** + +Recommendation ITU-T H.248.50 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Revised Recommendation ITU-T H.248.50 + +# Gateway control protocol: NAT traversal toolkit packages + +## Summary + +Recommendation ITU-T H.248.50 contains a series of ITU-T H.248 packages that enable various network address translator (NAT) traversal techniques to be employed in order to facilitate media flow between networks or user equipment and network-side located media gateways. Any of these packages may be utilized in any order to gather and map addresses, as well as maintain connectivity with and through NATs. + +This revision of Recommendation ITU-T H.248.50 adds clarifications and further capabilities, such as: + +- a new ITU-T H.248 session traversal utilities for NAT (STUN) consent freshness package; +- package-independent ITU-T H.248 procedures for specific NAT traversal use cases; +- interactive connectivity establishment (ICE) variants (full vs ICE lite; user equipment (UE)-embedded vs gateway-embedded ICE clients; vanilla vs trickle ICE; ICE for user datagram protocol (UDP) vs ICE for TCP; ICE for single-homed vs multi-homed host entities); and +- updates to keep alive support. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.248.50 | 2010-09-13 | 16 | 11.1002/1000/10984 | +| 1.1 | ITU-T H.248.50 (2010) Cor. 1 | 2012-02-13 | 16 | 11.1002/1000/11542 | +| 2.0 | ITU-T H.248.50 | 2016-07-14 | 16 | 11.1002/1000/12919 | + +## Keywords + +FW, Gateway, ITU-T H.248, ICE, NAT, STUN, TURN. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|-------------|----------------------------------------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 1.1 | Relation to other ITU-T H.248 related NAT traversal mechanisms ..... | 2 | +| 2 | References..... | 3 | +| 3 | Definitions ..... | 4 | +| 3.1 | Terms defined elsewhere ..... | 4 | +| 3.2 | Terms defined in this Recommendation..... | 4 | +| 4 | Abbreviations and acronyms ..... | 5 | +| 5 | Conventions ..... | 6 | +| 6 | Toolkit usage ..... | 6 | +| 6.1 | ITU-T H.248.50 usage in different network models ..... | 6 | +| 6.2 | Overview of toolkit NAT traversal techniques ..... | 13 | +| 6.3 | ITU-T H.248 call/bearer separation, connection model and IP addresses
for ephemeral terminations..... | 13 | +| 6.4 | Specific SDP information elements..... | 14 | +| 6.5 | Overview of NAT traversal support mechanisms (by ITU-T H.248
entities) ..... | 15 | +| 7 | STUN and TURN support ..... | 16 | +| 7.1 | STUN base package ..... | 16 | +| 7.2 | MG STUN client package ..... | 18 | +| 7.3 | MG TURN client package..... | 21 | +| 7.4 | MGC STUN client package..... | 25 | +| 7.5 | STUN information package..... | 27 | +| 8 | ICE support..... | 29 | +| 8.1 | MG act-as STUN server package ..... | 31 | +| 8.2 | Originate STUN continuity check package..... | 33 | +| 8.3 | STUN consent freshness package ..... | 39 | +| 9 | Keep-alive and pinhole support..... | 43 | +| 9.1 | MGC-originated STUN request package ..... | 43 | +| 9.2 | Keep alive request package ..... | 45 | +| 10 | Package-independent NAT-T procedures..... | 47 | +| 10.1 | Support for MG terminated STUN-based connectivity checks..... | 47 | +| Appendix I | – Example signalling scenarios for package-independent NAT-T procedures ... | 50 | +| I.1 | Example #1: ICE/STUN support by ITU-T H.248 IP access gateways..... | 50 | +| Appendix II | – ICE for TCP..... | 53 | +| II.1 | Introduction ..... | 53 | +| II.2 | MG bearer interface: protocol stack ..... | 53 | +| II.2 | Bearer establishment ..... | 53 | +| II.3 | TCP address candidates ..... | 53 | + +| | Page | +|-----------------------------------------------------------------------|------| +| Appendix III – ICE mode support by gateway-embedded ICE agents..... | 55 | +| III.1    Background..... | 55 | +| III.2    Main differences between ICE-full and ICE-lite..... | 55 | +| Appendix IV – ICE extensions: "Trickle ICE" ..... | 58 | +| IV.1    Introduction ..... | 58 | +| IV.2    Impact of trickle ICE on ITU-T H.248.50-defined packages..... | 59 | +| IV.3    Example signalling flows for trickle ICE..... | 59 | +| IV.4    Summary..... | 59 | +| Appendix V – ICE multihomed and IPv4/IPv6 dual stack fairness..... | 60 | +| V.1    Introduction ..... | 60 | +| V.2    Impact on ITU-T H.248 gateways with ICE support? ..... | 60 | +| Appendix VI – ICE restarts..... | 61 | +| VI.1    Introduction ..... | 61 | +| VI.2    ICE restart procedures ..... | 61 | +| VI.2    Impact on ITU-T H.248 gateways with ICE support? ..... | 61 | +| Bibliography..... | 62 | + +# Gateway control protocol: NAT traversal toolkit packages + +# 1 Scope + +This Recommendation describes packages to enable various network address translator (NAT) traversal techniques to be employed in order to facilitate media flow between networks. The media gateway controller (MGC) may utilize any of the packages in any order to gather addresses, map them and then maintain connectivity with and through NATs. + +The packages described in this Recommendation allow an ITU-T H.248 MGC and media gateway (MG) to use the techniques defined by: + +- simple session traversal utilities for NAT (STUN) reflexive address mapping as defined in [IETF RFC 3489] and [IETF RFC 5389]; +- relayed address mapping using the traversal using relays around NAT (TURN) techniques as described in [IETF RFC 5766]; +- comprehensive NAT traversal interactive connectivity establishment (ICE) techniques as described in [IETF RFC 5389]. + +In order to maintain backward compatibility, packages have been produced for both STUN as defined by [IETF RFC 3489] and by [IETF RFC 5389]. + +Throughout this Recommendation it is assumed that the media gateway performs STUN server discovery through the use of domain name system (DNS) lookup. + +Figure 1 summarizes the various packages as defined by the initial Recommendation. Every package is self-contained and does not use the extension principle. + +![Figure 1 – Landscape of NAT traversal toolkit packages, categorized into three application areas (status of ITU-T H.248.50 (09/2010))](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +The diagram illustrates the landscape of NAT traversal toolkit packages, categorized into three application areas: + +- (1) STUN and TURN support**: + - STUN:** + - stunb/1**: STUN base package + - stuni/1**: STUN information package + - mgstunc/1**: MG STUN client package + - mgcestunc/1**: MGC STUN client package + - TURN:** + - mgturnc/1**: MG TURN client package +- (2) ICE support**: + - mgstuns/1**: MG act-as STUN server package + - ostunc/1**: Originate STUN continuity check package +- (3) Keep-alive and pinhole support**: + - mgcostunr/1**: MGC originated STUN request package + - kar/1**: Keepalive request package + +H.248.50(10)\_F01 + +Figure 1 – Landscape of NAT traversal toolkit packages, categorized into three application areas (status of ITU-T H.248.50 (09/2010)) + +**Figure 1 – Landscape of NAT traversal toolkit packages, categorized into three application areas (status of ITU-T H.248.50 (09/2010))** + +ITU-T H.248.50 (07/2016) adds clarifications and further capabilities, such as: + +- a new ITU-T H.248 *STUN consent freshness* package; +- package-independent ITU-T H.248 procedures for specific NAT traversal use cases; +- ICE variants (full vs ICE lite; user equipment (UE)-embedded vs gateway-embedded ICE clients; vanilla vs trickle ICE; ICE for user datagram protocol (UDP) vs ICE for TCP; ICE for single-homed vs multi-homed host entities); +- updates to keep alive support; and +- clarifies support of "ICE restart" procedures. + +## 1.1 Relation to other ITU-T H.248 related NAT traversal mechanisms + +The following covers the applicability of this Recommendation versus other ITU-T H.248 supported NAT-T mechanisms: + +- Transport protocol generic NAT-T method "media latching" [ITU-T H.248.37]: this is an orthogonal mechanism and may be used in combination with this Recommendation; some of the mechanisms in this Recommendation make "media latching" unnecessary. + +NOTE – There is also a bearer plane latching process in the context of ICE, see clause 10.1.5 "STUN-specific media latching". The difference between both latching variants is illustrated in Appendix I. It is further noted that the IETF "media latching" function of [b-IETF RFC 7362] is synonymous to "H.248.37 latching" (because it makes the assumption that ICE/STUN/TURN is not applied for NAT traversal). + +- Transport protocol specific NAT-T method "TCP merge mode" [b-ITU-T H.248.84]: this represents a TCP simultaneous open from an end-to-end perspective, which is, if applicable, used before any "ICE for TCP" procedures are selected. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*. +- [ITU-T H.248.14] Recommendation ITU-T H.248.14 (2009), *Gateway control protocol: Inactivity timer package*. +- [ITU-T H.248.37] Recommendation ITU-T H.248.37 (2008), *Gateway control protocol: IP NAPT traversal package*. +- [ITU-T H.248.40] Recommendation ITU-T H.248.40 (2013), *Gateway control protocol: Application data inactivity detection package*. +- [ITU-T H.248.90] Recommendation ITU-T H.248.90 (2014), *Gateway control protocol: ITU-T H.248 packages for control of transport security using transport layer security (TLS)*. +- [ITU-T H.248.97] Recommendation ITU-T H.248.97 (2016), *Gateway Control Protocol: ITU-T H.248 support for control of SCTP bearer connections*. [IETF RFC 3489] IETF RFC 3489 (2003), *STUN – Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)*. +- [IETF RFC 3556] IETF RFC 3556 (2003), *Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth*. +- [IETF RFC 3605] IETF RFC 3605 (2003), *Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)*. +- [IETF RFC 4566] IETF RFC 4566 (2006), *SDP: Session Description Protocol*. +- [IETF RFC 4787] IETF RFC 4787 (2007), *Network Address Translation (NAT) Behavioral Requirements for Unicast UDP*. +- [IETF RFC 5245] IETF RFC 5245 (2010), *Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols*. +- [IETF RFC 5389] IETF RFC 5389 (2008), *Session Traversal Utilities for NAT (STUN)*. +- [IETF RFC 5766] IETF RFC 5766 (2010), *Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)*. +- [IETF RFC 5780] IETF RFC 5780 (2010), *NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)*. +- [IETF RFC 6544] IETF RFC 6544 (2012), *TCP Candidates with Interactive Connectivity Establishment (ICE)*. +- [IETF RFC 6888] IETF RFC 6888 (2013), *Common Requirements for Carrier-Grade NATs (CGNs)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 full trickle ICE mode** [b-IETF trickle-ice]: Regular mode of operation for *trickle ICE* agents, used in opposition to the *half trickle mode* of operation. + +**3.1.2 half trickle ICE mode** [b-IETF trickle-ice]: A *trickle ICE* mode of operation where the *offerer* gathers its first generation of candidates strictly before creating and sending the offer. Once sent, that offer can be processed by *vanilla ICE* agents and does not require support for [b-IETF trickle-ice]. It also allows *trickle ICE* capable *answerers* to still gather candidates and perform connectivity checks in a non-blocking way, thus roughly offering "half" the advantages of trickle ICE. The mechanism is mostly meant for use in cases where support for trickle ICE cannot be confirmed prior to sending a first offer. + +**3.1.3 NAT traversal** [b-ITU-T Y.2111]: The operation of adapting the IP addresses so that the packets in the media flow can pass through a far-end (remote) NAT. + +**3.1.4 network address translation** [b-ITU-T Y.2111]: The operation by which IP addresses are translated (mapped) from one address domain to another address domain. + +**3.1.5 pinhole** [ITU-T H.248.37]: A configuration of two associated H.248 IP terminations within the same context, which allows/prohibits unidirectional forwarding of IP packets under specified conditions (e.g., address tuple). + +**3.1.6 STUN agent** [IETF RFC 5389]: An entity that implements the STUN protocol. The entity can be either a *STUN client* or a *STUN server*. + +**3.1.7 STUN client** [IETF RFC 5389]: An entity that sends STUN requests and receives STUN responses. A *STUN client* can also send indications. + +**3.1.8 STUN consent freshness** [IETF RFC 7675]: Maintaining and renewing *consent* over time. *Consent* relates to the mechanism of obtaining permission from the remote endpoint to send non-ICE traffic to a remote transport address. Consent is obtained using ICE. Note that this is an application-level consent; no human intervention is involved. + +**3.1.9 STUN server** [IETF RFC 5389]: An entity that receives STUN requests and sends STUN responses. A *STUN server* can also send indications. + +**3.1.10 symmetric NAT** [IETF RFC 3489]: A symmetric NAT is one where all requests from the same internal IP address and port, to a specific destination IP address and port, are mapped to the same external IP address and port. + +**3.1.11 vanilla ICE** [b-IETF trickle-ice]: The Interactive Connectivity Establishment protocol as defined in [IETF RFC 5245]. + +## 3.2 Terms defined in this Recommendation + +**3.2.1 ICE-full** (mode, implementation): The ICE protocol capability set that performs the complete set of ICE requirements according to section 4.1 of [IETF RFC 5245]. + +NOTE – This definition is based on section 3 of [IETF RFC 5245]: "*Full: An ICE implementation that performs the complete set of functionality defined by this specification.*" The RFC uses the term "full ICE" to reference this functionality. + +**3.2.2 ICE-lite** (mode, implementation): The ICE protocol capability set that performs the subset of ICE requirements according to section 4.2 of [IETF RFC 5245]. + +NOTE – This definition is based on section 3 of [IETF RFC 5245]: *"Lite: An ICE implementation that omits certain functions, implementing only as much as is necessary for a peer implementation that is full to gain the benefits of ICE. Lite implementations do not maintain any of the state machines and do not generate connectivity checks."* + +**3.2.3 trickle ICE**: The extended ICE protocol capabilities, beyond *vanilla ICE*, as defined in [b-IETF trickle-ice]. Trickle ICE includes half trickle and full trickle ICE modes. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|----------------------------------------------------| +| L4 | (Protocol) Layer 4 (= IP transport protocol layer) | +| L4+ | Upper Layers versus L4 | +| ABNF | Augmented Backus-Naur Form | +| B2BIH | Back-to-Back IP Host | +| B2BUA | Back-to-Back User Agent | +| CRLF | Carriage-Return and Line-Feed (sequences) | +| DCCP | Datagram Congestion Control Protocol | +| DNS | Domain Name System | +| DTLS | Datagram Transport Layer Security | +| FW | FireWall | +| GFO | Gateway Free Operation | +| ICE | Interactive Connectivity Establishment | +| IMS | IP Multimedia Subsystem | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| IUA | ISDN User Adaptation | +| LD | Local Descriptor | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| NAT | Network Address Translation (or Translator) | +| NAT-T | Network Address Translation and Traversal | +| O/A | Offer/Answer | +| PES | PSTN/ISDN Emulation Subsystem | +| PSTN | Public Switched Telephone Network | +| RD | Remote Descriptor | +| RMG | Residential Media Gateway | +| RMGC | Residential Media Gateway Controller | +| RTCP | RTP Control Protocol | + +| | | +|--------|----------------------------------------| +| RTO | Retransmission TimeOut [IETF RFC 5389] | +| RTP | Real Time Protocol | +| SCTP | Stream Control Transmission Protocol | +| SDP | Session Description Protocol | +| SEP | Stream Endpoint | +| SIP | Session Initiation Protocol | +| SRTP | Secure RTP | +| STUN | Session Traversal Utilities for NAT | +| TCP | Transmission Control Protocol | +| TLS | Transport Layer Security | +| TURN | Traversal Using Relays around NAT | +| UDP | User Datagram Protocol | +| UA | User Agent | +| UE | User Equipment | +| UNSAF | UNilateral Self-Address Fixing | +| VPN | Virtual Private Network | +| WebRTC | Web Real-Time Communication | + +# 5 Conventions + +None. + +# 6 Toolkit usage + +## 6.1 ITU-T H.248.50 usage in different network models + +The ITU-T H.248 packages of this Recommendation may be applied in various network configurations. The clauses below illustrate some main scenarios. + +### 6.1.1 ITU-T H.248 MGC/MG as interim nodes in the end-to-end path between user equipment (with STUN client/server and/or ICE support) + +The NAT traversal support protocols: STUN, TURN and ICE are IP application protocols. They are fundamentally deployed in IP hosts (behind NAT device(s)) and IP network servers. The IP host function is located in the user equipment (UE) in Figure 2. The end-to-end IP bearer-path goes through an ITU-T H.248 MG (with an ITU-T H.248 IP-IP Context). There may be multiple NAT devices in the IP bearer-path (and IP signalling path(s)). Figure 2 shows an example with four IP realms, separated by two standalone NAT devices. The third NAT function is provided by the ITU-T H.248 MG. + +NOTE – The MG-internal NAT function is realized by the so-called back-to-back IP host (B2BIH) mode. + +![Figure 2: Network model – ITU-T H.248 MGC/MG as interim nodes in the end-to-end path between user equipment (with STUN client/server and/or ICE support).](af7916c89a458fdab6c3f443217388ae_img.jpg) + +The diagram illustrates a network architecture for ITU-T H.248. At the top, a dashed box labeled 'Call/session control' contains a 'Media gateway controller (MGC)' and 'ICE/STUN/TURN support'. Below this, a dashed oval labeled 'Scope of this Recommendation' is positioned. A solid line labeled 'ITU-T H.248 Gateway control protocol' connects the MGC to a central 'ITU-T H.248 media gateway' box. This box contains 'ICE/STUN/TURN support' and a 'Context' section with two 'IP' nodes. To the left of the media gateway is 'IP realm x2', which contains a 'STUN/TURN media relay' and is connected to a 'STUN/TURN server' at the bottom. To the right of the media gateway is 'IP realm x3'. Further right are 'NAT/FW', 'IP realm x4', and 'User equipment Remote side' which contains 'ICE support' and 'STUN/TURN client/server'. On the far left, 'User equipment' contains 'ICE support' and 'STUN/TURN client/server', connected to 'IP realm x1', which is followed by 'NAT/FW' and then 'IP realm x2'. A legend at the bottom defines the line types: solid for IP bearer (RTP), dashed for Call/session control (SIP), long-dashed for STUN/TURN traffic, and dash-dot for Gateway control (ITU-T H.248). + +Figure 2: Network model – ITU-T H.248 MGC/MG as interim nodes in the end-to-end path between user equipment (with STUN client/server and/or ICE support). + +NOTE 1 – IP realms: x3 = x4 possible. + +NOTE 2 – IP realms: if x3 ≠ x4, then MG-embedded NAT. + +H.248.50(10)\_F02 + +**Figure 2 – Network model – ITU-T H.248 MGC/MG as interim nodes in the end-to-end path between user equipment (with STUN client/server and/or ICE support)** + +The ITU-T H.248 gateway (MGC and MG entity) may be requested to support particular STUN/TURN/ICE scenarios. For instance, the ITU-T H.248 gateway may be requested to act in a "proxy role" of the STUN client function (e.g., in case that the MG and UE would be both located in the same IP realm and when the UE could not provide the STUN client function itself). + +It may be noted that the relation between the assist protocols (STUN, TURN and ICE) and the call/session control protocol (like session initiation protocol (SIP)) may vary between a loose and a tighter coupling mode, e.g., some examples with regard to the time relation: + +- timely tightly coupled: e.g., the ICE address gathering phase and subsequent SIP INVITE phase (before connectivity check phase); +- timely loosely coupled: e.g., the STUN keep pinhole open mechanism and NAT pinhole timer settings (which may vary between 30 seconds and the timescale of minutes and hours); +- timely de-coupled: e.g., the basic STUN mechanism for analysing the mode of operation(s) of the installed base of NAT devices. + +The function of the last bullet item may be decoupled from call/session control phases and done in advance (because network topology and NAT behaviour changes rather slowly). The ITU-T H.248 gateway may be used for a NAT traversal support function on each time-scale. + +### 6.1.2 ITU-T H.248 MGC/MG emulates a user agent (with STUN client/server and/or ICE support) + +The evolution from the legacy public switched telephone network/integrated services digital network (PSTN/ISDN) to IP-based networks like the PSTN emulation subsystem (PES) or the IP multimedia + +subsystem (IMS) may lead to a network model as depicted in Figure 3. The ITU-T H.248 gateway may be located at the border between the circuit-switched and IP networks. The ITU-T H.248 gateway may be requested to emulate the behaviour of IP user equipment with regard to the NAT traversal support function. + +![Figure 3: Network model – ITU-T H.248 MGC/MG emulates a user agent (with STUN client/server and/or ICE support). The diagram shows a PSTN/ISDN network connected to an ITU-T H.248 media gateway (MG) which emulates a user agent. The MG is connected to a Call/session control (MGC) via an ITU-T H.248 Gateway control protocol. The MGC contains a Media gateway controller (MGC) and ICE/STUN/TURN support. The MG contains ICE/STUN/TURN support, Context, and Physical IP. The MG is connected to an IP realm (x1) via a NAT/FW. The IP realm (x1) is connected to an IP realm (x2) via a NAT/FW. The IP realm (x2) contains a STUN/TURN media relay. The IP realm (x2) is connected to an IP realm (x3) via a NAT/FW. The IP realm (x3) contains a STUN/TURN server. The IP realm (x3) is connected to User equipment (Local or remote side) via a NAT/FW. The User equipment contains ICE support and STUN/TURN client/server. A dashed line indicates the scope of this Recommendation, covering the MG, MGC, and the first NAT/FW.](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg) + +ITU-T H.248 entities emulating "UE" STUN/TURN client/server + +Scope of this Recommendation + +ITU-T H.248 Gateway control protocol + +Call/session control + +Media gateway controller (MGC) + +ICE/STUN/TURN support + +PSTN/ISDN + +Context + +Physical IP + +ITU-T H.248 media gateway + +IP realm x1 + +NAT/FW + +IP realm x2 + +STUN/TURN media relay + +STUN/TURN server + +NAT/FW + +IP realm x3 + +ICE support + +STUN/TURN client/server + +User equipment + +Local or remote side + +Legend: + +- IP bearer connection (e.g., RTP) +- Call/session control (e.g., SIP) +- STUN/TURN traffic +- Gateway control (ITU-T H.248) + +NOTE 1 – IP realms: x1 = x2 possible. +NOTE 2 – IP realm: x2 $\Rightarrow$ typically public address realm. + +H.248.50(10)\_F03 + +Figure 3: Network model – ITU-T H.248 MGC/MG emulates a user agent (with STUN client/server and/or ICE support). The diagram shows a PSTN/ISDN network connected to an ITU-T H.248 media gateway (MG) which emulates a user agent. The MG is connected to a Call/session control (MGC) via an ITU-T H.248 Gateway control protocol. The MGC contains a Media gateway controller (MGC) and ICE/STUN/TURN support. The MG contains ICE/STUN/TURN support, Context, and Physical IP. The MG is connected to an IP realm (x1) via a NAT/FW. The IP realm (x1) is connected to an IP realm (x2) via a NAT/FW. The IP realm (x2) contains a STUN/TURN media relay. The IP realm (x2) is connected to an IP realm (x3) via a NAT/FW. The IP realm (x3) contains a STUN/TURN server. The IP realm (x3) is connected to User equipment (Local or remote side) via a NAT/FW. The User equipment contains ICE support and STUN/TURN client/server. A dashed line indicates the scope of this Recommendation, covering the MG, MGC, and the first NAT/FW. + +**Figure 3 – Network model – ITU-T H.248 MGC/MG emulates a user agent (with STUN client/server and/or ICE support)** + +It may be noted that the TURN media relay function is outside of the ITU-T H.248 gateway and provided by a separate network server in the previous two examples. + +#### 6.1.2.1 Scenario when MG and MGC located in different IP realms + +Where the MGC and MG are in different IP realms, the ITU-T H.248 signalling and media flows may traverse the same NAT/firewall (FW) (see also Figure 4, using the example of a residential media gateway (RMG)). The techniques described in this Recommendation may be used for media flow NAT/FW traversal. Signalling (call/session) NAT traversal is generally not in the scope of this Recommendation, however ITU-T H.248 NAT traversal may benefit from the use of ITU-T H.248-based peer-to-peer polling mechanisms (like e.g., [ITU-T H.248.14] or empty audits on ITU-T H.248 level, or e.g., stream control transmission protocol (SCTP) indications on transport connection level) in order to maintain NAT bindings. Opening of the NAT binding for ITU-T H.248 traffic would be subject of the initial ServiceChange messages for MG registration. + +![Figure 4: Network model – Scenario when MG and MGC are located in different IP realms – Keep-alive and pinhole support. The diagram shows a PSTN/ISDN network connected to an ITU-T H.248 residential media gateway (RMG) which emulates 'user equipment'. The RMG is connected to an internal IP network (IP realm x1) via a NAT/FW device. The NAT/FW device is connected to an external IP network (IP realm x2). In the external IP network, there is an ITU-T H.248 border media gateway (BMG) connected to an external IP network. The RMG contains a 'Signalling keep-alive and pinhole support' block, a 'Media keep-alive and pinhole support' block, a 'Context' block, and a 'Physical' block. The BMG contains a 'Keep-alive and pinhole support' block, a 'Context' block, and a 'Physical' block. The NAT/FW device contains a 'Call/session control' block, a 'Residential media gateway controller (RMGC)' block, and a 'Keep-alive and pinhole support' block. The RMGC contains a 'Keep-alive and pinhole support' block. The diagram also shows various traffic types: ITU-T H.248 gateway control traffic, PSTN call control signalling via ITU-T H.248, ISDN call control signalling via IUA/SCTP/IP, IP bearer connection (e.g., RTP), STUN/TURN traffic, Call/session control (e.g., SIP), and Gateway control (ITU-T H.248). The diagram also indicates 'Out of the scope of this Recommendation' and 'Scope of this Recommendation'.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +a) ITU-T H.248 gateway control traffic +b) PSTN call control signalling via ITU-T H.248 +c) ISDN call control signalling via IUA/SCTP/IP + +Out of the scope of this Recommendation + +ITU-T H.248 + +Gateway control protocol + +Keep-alive and pinhole support + +Context + +IP IP + +ITU-T H.248 border media gateway + +Example + +Call/session control + +Residential media gateway controller (RMGC) + +Keep-alive and pinhole support + +"Signalling pinhole" + +"Media pinhole" + +NAT/FW + +IP realm x2 + +IP bearer connection (e.g., RTP) + +STUN/TURN traffic + +Call/session control (e.g., SIP) + +Gateway control (ITU-T H.248) + +Signalling keep-alive and pinhole support + +Media keep-alive and pinhole support + +Context + +Physical IP + +ITU-T H.248 residential media gateway + +ITU-T H.248 RMG emulates "user equipment" + +Scope of this Recommendation + +IP realm x1 + +PSTN/ISDN + +Internal IP network + +External IP network + +H.248.50(10)\_F04 + +Figure 4: Network model – Scenario when MG and MGC are located in different IP realms – Keep-alive and pinhole support. The diagram shows a PSTN/ISDN network connected to an ITU-T H.248 residential media gateway (RMG) which emulates 'user equipment'. The RMG is connected to an internal IP network (IP realm x1) via a NAT/FW device. The NAT/FW device is connected to an external IP network (IP realm x2). In the external IP network, there is an ITU-T H.248 border media gateway (BMG) connected to an external IP network. The RMG contains a 'Signalling keep-alive and pinhole support' block, a 'Media keep-alive and pinhole support' block, a 'Context' block, and a 'Physical' block. The BMG contains a 'Keep-alive and pinhole support' block, a 'Context' block, and a 'Physical' block. The NAT/FW device contains a 'Call/session control' block, a 'Residential media gateway controller (RMGC)' block, and a 'Keep-alive and pinhole support' block. The RMGC contains a 'Keep-alive and pinhole support' block. The diagram also shows various traffic types: ITU-T H.248 gateway control traffic, PSTN call control signalling via ITU-T H.248, ISDN call control signalling via IUA/SCTP/IP, IP bearer connection (e.g., RTP), STUN/TURN traffic, Call/session control (e.g., SIP), and Gateway control (ITU-T H.248). The diagram also indicates 'Out of the scope of this Recommendation' and 'Scope of this Recommendation'. + +**Figure 4 – Network model – Scenario when MG and MGC are located in different IP realms – Keep-alive and pinhole support** + +Keep "pinhole open" mechanisms for media IP flows are in scope of this Recommendation. Keep "pinhole open" mechanisms for signalling IP flows are out of scope of this Recommendation; such methods may be e.g., addressed by correspondent ITU-T H.248 profile specifications for such ITU-T H.248 gateways. + +### 6.1.3 ITU-T H.248 MGC/MG provides STUN/TURN server functionality + +The STUN/TURN server function could be principally embedded in a MG, MGC or gateway (MGC/MG tandem), see Figure 5. + +![Figure 5: Network model – ITU-T H.248 MGC/MG provides STUN/TURN server functionality. The diagram shows a central ITU-T H.248 Gateway control protocol connected to a Call/session control block (containing Media gateway controller (MGC), ICE/STUN/TURN support, and STUN/TURN server). This is connected to an ITU-T H.248 media gateway (containing STUN/TURN server, ICE/STUN/TURN support, Context, and IP). The media gateway is connected to four IP realms (x1, x2, x3, x4) via NAT/FW devices. User equipment (UE) with ICE support and STUN/TURN client/server is connected to IP realm x1 and IP realm x4. A STUN/TURN media relay is connected to IP realm x2. A dashed line indicates the 'Scope of this Recommendation' covering the Call/session control and the ITU-T H.248 media gateway.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 5: Network model – ITU-T H.248 MGC/MG provides STUN/TURN server functionality. The diagram shows a central ITU-T H.248 Gateway control protocol connected to a Call/session control block (containing Media gateway controller (MGC), ICE/STUN/TURN support, and STUN/TURN server). This is connected to an ITU-T H.248 media gateway (containing STUN/TURN server, ICE/STUN/TURN support, Context, and IP). The media gateway is connected to four IP realms (x1, x2, x3, x4) via NAT/FW devices. User equipment (UE) with ICE support and STUN/TURN client/server is connected to IP realm x1 and IP realm x4. A STUN/TURN media relay is connected to IP realm x2. A dashed line indicates the 'Scope of this Recommendation' covering the Call/session control and the ITU-T H.248 media gateway. + +——— IP bearer connection (e.g., RTP)      ——— STUN/TURN traffic + - - - - Call/session control (e.g., SIP)      ——— Gateway control (ITU-T H.248) + +NOTE 1 – IP realms: x3 = x4 possible. + +NOTE 2 – IP realms: if x3 ≠ x4, then MG-embedded NAT. + +H.248.50(10)\_F05 + +**Figure 5 – Network model – ITU-T H.248 MGC/MG provides STUN/TURN server functionality** + +The STUN server function requires the processing of incoming STUN Binding Request messages and the reply by correspondent STUN Binding Response messages. In case of NAT devices in "symmetric NAT" mode, additional support by TURN is required. The TURN server function requires the processing of TURN messages (Allocate Request, Allocate Response and Send Request). + +The STUN server and TURN server functions may be provided by an ITU-T H.248 gateway on a MG or MGC level (as indicated in Figure 5). However, the TURN media relay function should be out of scope of MGC nodes (see clause 6.1.4). + +The advantage of a STUN/TURN server at MGC level is the close location to call/session control. For instance, it may be beneficial to have information available concerning interim NAT devices and their behaviour, NAT binding lifetime information (e.g., a TURN attribute) or IP address usage. A close location of possible SIP server function (like a SIP proxy, application level gateway or back-to-back user agent (B2BUA) function) and STUN/TURN servers may also be beneficial. + +The advantage of a STUN/TURN server at MG level may be e.g., driven by a functional sharing performance model for off-loading the MGC node from STUN/TURN message processing functions, or e.g., the coupling of a TURN server and TURN media relay in an ITU-T H.248 MG node. + +### 6.1.4 ITU-T H.248 MG provides TURN media relay functionality + +The TURN media relay function may be embedded in a MG itself, see Figure 6. The TURN media relay function is inserted in the end-to-end IP bearer-path. The decision for routing the IP bearer connection over a TURN media relay is either already known before call/session establishment, or done during that phase due to a call/session-driven STUN process. The TURN media relay function may require substantial resources for processing and forwarding IP bearer path packets. This is the primary reason for excluding such a function from MGC entities. + +There are on the other side many good reasons for combining the TURN media relay function and ITU-T H.248 MG function. For example, this is because the MG may inherently provide the TURN media relay NAT function, or because of a "simpler" IP bearer-path routing process, or due to QoS reasons (e.g., the native TURN media relay provides only coarse support for bearer-path resource reservation by the single attribute "Bandwidth", but is lacking support for session-dependent policing functions per se), or the ability of the MGC to access TURN media relay server information. + +![Figure 6: Network model – ITU-T H.248 MG provides TURN media relay functionality. The diagram shows a central ITU-T H.248 media gateway (MG) connected to a Call/session control (MGC) and a STUN/TURN server. The MG is connected to four IP realms (x1, x2, x3, x4) via NAT/FW devices. User equipment (UE) is connected to IP realm x1, and Remote side UE is connected to IP realm x4. The MG contains an ICE/STUN/TURN support block, a Context block, an IP block, and an STUN/TURN media relay block. The scope of the recommendation is indicated by a dashed line around the MG and its connected realms.](8307f6b04df072c9332f9987e034272c_img.jpg) + +The diagram illustrates a network model where an ITU-T H.248 media gateway (MG) provides TURN media relay functionality. At the top, a 'Call/session control' block contains a 'Media gateway controller (MGC)' and 'ICE/STUN/TURN support'. This is connected via a dashed line to a central 'ITU-T H.248 Gateway control protocol' block. Below this, a dashed oval labeled 'Scope of this Recommendation' encompasses the MG. The MG itself contains 'ICE/STUN/TURN support', a 'Context' block, an 'IP' block, 'STUN/TURN media relay', and 'ITU-T H.248 media gateway'. A 'STUN/TURN server' is connected to the bottom of the MG. The MG is connected to four 'IP realm' clouds (labeled x1, x2, x3, x4) through 'NAT/FW' devices. On the left, 'User equipment' with 'ICE support' and 'STUN/TURN client/server' connects to IP realm x1. On the right, 'Remote side' user equipment with similar support connects to IP realm x4. A legend at the bottom defines the line types: solid for IP bearer connections (e.g., RTP), dashed for call/session control (e.g., SIP), long-dashed for STUN/TURN traffic, and dash-dot for Gateway control (ITU-T H.248). + +Figure 6: Network model – ITU-T H.248 MG provides TURN media relay functionality. The diagram shows a central ITU-T H.248 media gateway (MG) connected to a Call/session control (MGC) and a STUN/TURN server. The MG is connected to four IP realms (x1, x2, x3, x4) via NAT/FW devices. User equipment (UE) is connected to IP realm x1, and Remote side UE is connected to IP realm x4. The MG contains an ICE/STUN/TURN support block, a Context block, an IP block, and an STUN/TURN media relay block. The scope of the recommendation is indicated by a dashed line around the MG and its connected realms. + +NOTE 1 – IP realms: x3 = x4 possible. + +NOTE 2 – IP realms: if x3 ≠ x4, then MG-embedded NAT. + +H.248.50(10)\_F06 + +**Figure 6 – Network model – ITU-T H.248 MG provides TURN media relay functionality** + +### 6.1.5 "STUN server" capability + +A network domain may provide one or multiple STUN server(s). A STUN server may be realized as a non-ITU-T H.248 network element or as ITU-T H.248 entity-embedded STUN server functions (in context of this Recommendation). For instance, the STUN agent provided by the MG is then called "MG act-as STUN server" function. + +The STUN service(s) may be provided by a single or multiple STUN servers; typically, dependent on the network configuration and/or STUN application. + +The internal modeling of the STUN protocol in "service categories" (protocol functions) is difficult; however, STUN server functions could be classified in *call-independent* and *call-dependent* + +categories. It should be noted that such a classification scheme is not useful in general, but suitable in the context of ITU-T H.248 gateways. + +The call-dependent category relates to the ICE connectivity check and has to be performed by the entity in the call/session control path that terminates ICE, either the ICE end point located in a terminal or a gateway, (e.g., a session border gateway). Providing a single STUN server in the network domain thus implies that call control signalling corresponding to all call/sessions using ICE has to be routed through that gateway (such as in Figure 5), unless the end point itself provides the server functionality. + +An example of STUN server function distributions for STUN application 'ICE' according to the network model in Figure 2 (see also description of the scenario in clause 6.1.1 or Appendix I.1): + +A stand-alone "STUN server" is involved during the STUN-based address gathering phase. And the ITU-T H.248 MG as "STUN server" is involved during the STUN-based connectivity check phase. The first STUN server function is "call-independent" because it actually occurs before any call control signalling (from MGC perspective), and the second STUN server function is "call-dependent" because associated with call control signalling. + +The STUN server involved during STUN-based address gathering phase could also be provided by an ITU-T H.248 MG entity (such as in case of Figure 5). + +### **6.1.6 ICE capability set: ICE full vs ICE lite** + +ICE allows two explicit modes of operations, where "ICE full" represents the complete capability set and "ICE lite" a subset of "ICE full". [IETF RFC 5245] defines an explicit signalling element (session description protocol (SDP) "a=ice-lite" attribute) for ICE mode support indication. The omission / inclusion of this SDP attribute in SIP signalling indicates ICE full / lite support. However, [IETF RFC 5245] does not provide a detailed description of the behaviour of the ICE lite mode; the information is rather distributed across the entire ICE RFC. + +NOTE – The rationale behind this is the expectation that ICE lite is only a temporary implementation step which should evolve to ICE full support. This assumption might be valid for terminal-embedded ICE agents, but not necessarily valid for gateway-embedded ICE support as in scope of this Recommendation. + +Appendix III describes the differences between the two ICE modes at the level of detail of interest to ITU-T H.248 gateways. + +### **6.1.7 Principal network models concerning location of ICE endpoints** + +ICE represents a single algorithm, distributed over two ICE agents in a network. There are two main models concerning the mapping of the two ICE agents to the network topology (Table 1): + +This aspect should be taken into account when looking at the use cases in clauses 6.1.1 to 6.1.4. + +**Table 1 – Network models concerning location of ICE endpoints** + +| Model | Characteristics | Comments | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Terminal-to-terminal (peer-to-peer) | Both ICE endpoints are located in terminal embedded IP host entities | This is the base model of IETF for the design of ICE. All IETF "ICE RFCs" use this model. | +| Terminal-to-network |

One ICE endpoint is located in IP network infrastructure equipment, such as an ITU-T H.248 IP-to-IP media gateway (acting as B2BIH or IP router) within the end-to-end IP media path.

This leads to following consequences:

  • • The end-to-end IP media path is divided (by the ITU-T H.248 MG) in two segments:
    1. 1) "ICE segment"; and
    2. 2) "another non-ICE based segment".
  • • Special case: both segments use an ICE-based NAT traversal independent of each other.
| Major difference to the IETF base model: the MG might not be "located behind a NAT" (from the perspective of ICE), and thus be always reachable ("full IP connectivity without ICE-based NAT traversal support"). | + +## 6.2 Overview of toolkit NAT traversal techniques + +This Recommendation describes the various mechanisms used in order to secure media flow traversal of networks where NATs are used. In essence, the packages described provide a toolkit for the MGC to use in order to: gather a list of potential NAT mapped address (address gathering), check connectivity associated with those addresses, and maintain the connectivity associated with those addresses. The Recommendation is structured around the various techniques that have been defined: + +- 1) STUN usage according to [IETF RFC 3489]; +- 2) STUN usage according to [IETF RFC 5389]; +- 3) TURN usage according to [IETF RFC 5766]; +- 4) ICE techniques according to [IETF RFC 5245]. + +NOTE – At the time of publication of this Recommendation, this RFC was being updated by [b-IETF RFC 5245bis] and [b-IETF ice-sip-sdp]. These updates are out of scope of this Recommendation. + +- 5) Other techniques used to maintain connectivity. + +These techniques have typically not considered the scenario where the media flows are initiated from a split MGC and MG. + +## 6.3 ITU-T H.248 call/bearer separation, connection model and IP addresses for ephemeral terminations + +The splitting of the so-called "user agent" functionality into a control and media components means that there needs to be coordination between the two components. As the MGC usually constructs call and session control messages, it must be able to request information from the MG in order to build these messages. For instance, it would need address and media information to place in an SDP offer. + +Media gateways typically support several different source/destination IP address/port combinations per peer-to-peer media connection. This may be due to different media (e.g., audio or video), different single media capabilities (codec A versus codec B) and to handle events (e.g., real time protocol (RTP) control protocol (RTCP)). These capability sets may be advertised to a remote party which selects the appropriate media set to use. In order for media connectivity to be successful for any of the sets, any media stream that encounters a NAT should have its address mapped. At a call/session + +level, a correlation is given between the local "native" IP address/ports of the MG and the mapped addresses. Such a scheme is detailed in section 4.3 of [IETF RFC 5245]. The use of ITU-T H.248 between a MGC and MG introduces a connection model that needs to be considered when correlating local "native" addresses and mapped addresses using ICE techniques. Furthermore, some NAT traversal techniques do not use ICE, thus this particular candidate scheme is not appropriate for them. + +As such in this Recommendation, where ICE is not used, the correlation is in the form of an ordered list of values, where: + +The first position on the list corresponds to the first address in the first group associated with a particular stream. The second position is associated with either a second address in the first group or, if there are no further addresses, it is associated with the first address in the second group. The parameter "Address Correlation" in the Base STUN package describes the mapping between the list position and the place in the Local Descriptor (LD). + +## 6.4 Specific SDP information elements + +### 6.4.1 SDP for vanilla ICE + +#### 6.4.1.1 UDP-based address candidates + +Where ICE is used, the SDP CANDIDATE attribute [IETF RFC 5245] is used. + +The so-called "candidate scheme" does not alter the actual media flows. That is, a MG will use the source address in the Local Descriptor to send from, and the destination address in the Remote Descriptor (RD) to send to. In the text encoding, this is the SDP connection address (c=) and media (m=) lines. Therefore, if the MGC chooses a candidate other than the local address, this shall be reflected in the Local and Remote Descriptors. This may have implications on how the media is sent. For example, if this address is a relay address, then the data may have to be sent using TURN send indications. + +#### 6.4.1.2 TCP-based address candidates + +Where ICE is used for TCP [IETF RFC 6544] (see also Appendix II), the SDP CANDIDATE attribute from [IETF RFC 5245] is used with its grammar extended according to section 4.5 of [IETF RFC 6544]. + +### 6.4.2 SDP for extended ICE + +#### 6.4.2.1 Trickle ICE + +Appendix IV provides some background information on trickle ICE, from the perspective of ITU-T H.248 gateways. + +Where *trickle ICE* is used, the SIP-based call control signalling (according to [b-IETF trickle-ice] and [b-IETF trickle-sip]) uses the following signalling extensions in brief: + +1. start of call establishment phase: indication of trickle ICE support via SDP attribute "a=ice-options:trickle"; +2. trickling phase: signalling of candidate updates via SIP INFO messages; and +3. stop of trickling phase: announcing end of candidates via SDP attribute " a=end-of-candidates". + +The three trickle ICE phases affect the ITU-T H.248 MGCs' SIP-based call control signalling interface only. There are not necessarily correspondent impacts on the ITU-T H.248 gateway control signalling. This seems to be rather conditional, dependent on the network configuration and IP bearer path routes. A detailed analysis of trickle ICE is for further studies. + +## 6.5 Overview of NAT traversal support mechanisms (by ITU-T H.248 entities) + +### 6.5.1 Address latching support + +Legacy "media latching" as introduced for network infrastructures without ICE/STUN/TURN (see also [b-IETF RFC 7362]) is covered in the scope of [ITU-T H.248.37]. Clause 10.1.5 describes a STUN-specific media latching function in the context of ICE, which effectively leads to the same autonomous adaptation of IP transport addresses behaviour in the IP bearer plane. + +### 6.5.2 Basic STUN/TURN support (ICE-less) + +See clause 7. + +### 6.5.3 ICE-controlled STUN/TURN + +See clause 8. The ICE methodology defines a "superior" protocol that uses the STUN/TURN mechanism and other protocols. The use of ICE is also tightly coupled with SIP and in particular with SIP/SDP offer/answer (O/A) procedures. ICE is executed between a pair of ICE agents. There are two device types concerning the embodiment of ICE agents with respect to their location in the IP network infrastructure: + +- terminal-embedded ICE agent: user equipment with ICE agent function and SIP UA function; +- gateway-embedded ICE agent: a decomposed ITU-T H.248 gateway provides the ICE agent function in a distributed manner (with the SIP signalling function located at MGC level). + +This clause describes the ICE process from the perspective of a generic ICE agent, i.e., it does not differentiate between the above two embodiments (but indicates possible ITU-T H.248 impacts for the gateway-provided ICE agent). + +The execution of ICE may be basically divided into several consecutive phases: + +- 1) Gather addresses + - Purpose: Address gathering. + - This phase may be based on STUN and/or TURN procedures as required. + - Used ITU-T H.248.50 packages: None. +- 2) Prioritizing addresses + - Purpose: optimize final IP bearer path (routing). + - Function provided either by + - a) MG, in case of a MGC request via SDP CANDIDATE attribute (MG needs to provide then the STUN server discovery, see clause 8); or + - b) MGC, in its capacity as "ICE endpoint" and SDP O/A processing; or + - c) external (SIP) server, in case of a network deployment model where the address gathering and prioritization functions are provided by non-ITU-T H.248 entities; + - Used ITU-T H.248.50 packages: SDP "a=candidate:" attribute and *ostuncc* package (because the STUN connectivity checks result in priority value assignments). + - Address prioritization rules: The basic rules for address prioritization are described in section 4.1.2.1 of [IETF RFC 5245]. The purpose of ICE multihomed and IPv4/IPv6 dual stack fairness support may require other prioritization algorithms, see [b-IETF ice-dualstack] and Appendix V. The applicable prioritization rules should be explicitly part of an ITU-T H.248 profile specification in case that an ITU-T H.248 entity is responsible for that ICE function. +- 3) Call/session control signalling: generate SDP Offer (for SIP signalling) + - Purpose: generate SDP Offer content (if originating side). + +- Multiple SDP attributes may be involved: the basic ICE protocol introduces seven ICE-specific SDP attributes (see [IETF RFC 5245]). + +NOTE 1 – The values of media-level ICE SDP attributes could be requested from the MGC and provided by the MG, whenever the MG is involved in the resource management of such information. + +- Used ITU-T H.248.50 packages: None (due to application control protocol related function). +- 4) Call/session control signalling: Negotiations – Offering and Answering (initiate and accept SIP messages) + - Purpose: Address advertisement. + - This phase is typically related to the initiation of a SIP INVITE (thus, out of scope of this Recommendation). + +NOTE 2 – The peer user (called party, invited party) may also start a correspondent "address gathering" procedure (based on STUN and/or TURN as required). These remote procedures would not be visible for the local MGC/MG entities. + +- The peer (SIP) user may reply with a SIP OK (thus, out of scope of this Recommendation). +- Used ITU-T H.248.50 packages: None (due to application control protocol related function). +- 5) Connectivity checks + - This phase is again based on STUN and/or TURN procedures as required. + - The connectivity checks are based on the same 4-tuple(s) as (later) used for the ITU-T H.248 stream. + - The STUN/TURN messages may be thus multiplexed into the RTP/RTCP packet flow of the checked ITU-T H.248 stream (of an ITU-T H.248 RTP termination). + - Used ITU-T H.248.50 packages: mgastuns, ostunc. +- 6) Completing ICE procedures + - One agent assumes ICE *controlling* role, other agent assumes ICE *controlled* role. + - Table III.1, table section 6 lists additional functions as part of the ICE completion phase. + - Used ITU-T H.248.50 packages: None or indirectly because ICE completion is subject of call control signalling between the two ICE endpoints. + +NOTE 3 – The ICE completion process could result in the conclusion that the routed IP bearer path could possibly finally bypass the MG instance, which was initially involved in the above ICE procedural steps. The initially created ITU-T H.248 Context would be then obsolete from an ICE perspective, which could result in MGC performing either of the following actions: + +- the deallocation of the MG (which may be termed as gateway free operation (GFO)), or + - the ITU-T H.248 stream is enabled for a transparent forwarding mode of operation. +- 7) Bearer connection: check/selection of media streams + - Used ITU-T H.248.50 packages: None. + +The outlined, high level ICE process is not detailed concerning possible differences from ICE mode perspective. The ICE mode impact on gateway-embedded ICE agents is described in Appendix III. + +# 7 STUN and TURN support + +The packages defined in this clause allow the use of STUN and TURN techniques without the need for support of ICE and associated SDP, e.g., Candidates are not used. + +## 7.1 STUN base package + +**Package name:** STUN Base +**Package ID:** stunb (0x00bd) + +**Description:** This package describes the mapping between transport addresses defined in the ITU-T H.248 Local Descriptor and the list position when used for STUN purposes. + +**Version:** 1 + +**Extends:** None + +### 7.1.1 Properties + +#### 7.1.1.1 Address correlations + +**Property name:** Address Correlation + +**Property ID:** ac (0x0001) + +**Description:** This property details the list position of each IP Address in the ITU-T H.248 Local Descriptor. This package may be used by the MGC to determine the mapping between local IP addresses and list positions for STUN processing purposes. + +NOTE – It is not mandatory to implement this package as the MGC may determine the list positions given the logic below. However it provides a mechanism in order to check the list positions. + +**Type:** List of String + +**Possible values:** Each element in the list of string SHALL be type **AddressCorrelation** according to the following augmented Backus-Naur form (ABNF): + +``` +AddressCorrelation = Listposition "|" + Groupnumber "|" Instance "|" ComponentID +``` + +Where: + +*List position* is an integer. The first position of the list shall be 1 and sequentially rising by one. + +*Groupnumber* is an integer and is the ITU-T H.248 group number. + +*Instance* is an integer. The first instance of a media format (as per section 5.14 of [IETF RFC 4566]) field in "m=" line in a particular group shall be 1. For each subsequent media format the instance shall be incremented by one. + +*ComponentID* is the identifier of a component. A component is a piece of a media flow requiring a single transport address. For RTP-based media flows, the RTP itself has a component ID of 1, and RTCP has a component ID of 2. For non RTP-based media flow, the component ID is 1. + +The list SHALL contain an element for each IP address in the Local Descriptor. + +For example, the values: + +``` +"1|1|1|1" +"2|1|1|2" +"3|1|2|1" +"4|1|2|2" +"5|2|1|1" +"6|2|1|2" +``` + +Would relate to the following SDP in the Local Descriptor: + +``` +v=0 +c=IN IP4 192.168.1.100 +m=audio 10000 RTP/AVP 4 18 +v=0 +c=IN IP4 192.168.1.200 +m=audio 20000 RTP/AVP 0 +``` + +The values of ReserveValue and ReserveGroup are "on". + +**Default:** Empty String if no IP addresses are present in the Local Descriptor. +**Defined in:** LocalControl +**Characteristics:** ReadOnly + +### 7.1.2 Events + +None. + +### 7.1.3 Signals + +None. + +### 7.1.4 Statistics + +None. + +### 7.1.5 Error codes + +None. + +### 7.1.6 Procedures + +In order for the MGC to determine in a timely manner the correlation between local IP address and the STUN processing list positions, the MGC shall perform a CHOOSE (\$) on the "*stunb/ac*" property whenever an IP address is added/changed/deleted to/from the ITU-T H.248 Local Descriptor on a particular Stream/Termination. + +## 7.2 MG STUN client package + +**Package name:** MG STUN Client +**Package ID:** mgstunc (0x00be) +**Description:** This package enables an MGC to determine the mapped IP address and port that will be routed back to the media component that sent the request. This package applies to both [IETF RFC 3489] and [IETF RFC 5389]. +**Version:** 1 +**Extends:** None + +### 7.2.1 Properties + +#### 7.2.1.1 STUN address + +**Property name:** STUN Address +**Property ID:** stuna (0x0001) +**Description:** This property indicates that the MG shall return a STUN mapped IP address and port for each local address indicated. The MGC may send + +this STUN mapped IP address and port to the peer as its remote IP address and port. + +NOTE – Implementors should be aware that each STUN message to a STUN server may imply a 9.5-second delay (see section 9.1 of [IETF RFC 3489]). This may impact the time in which an ITU-T H.248 command reply can be sent to the MGC. In cases where the STUN delay is excessive the use of TransactionPending is encouraged. + +**Type:** List of String + +**Possible values:** In an ITU-T H.248 command request: + +Each element in the list of string SHALL be of type **StunAddressReq** in ABNF format: + +``` +StunAddressReq = "L"/("B"[COLON Stun-Transport-type])/ +("S"[COLON Stun-Transport-type]) +Stun-Transport-type = "UDP"/"TCP"/"TLS" +``` + +Where: + +"L": Local Address – Do not perform STUN address mapping for the address in this position. + +"B": Binding Request – Perform a STUN binding request on the address in this list position. STUN clients can communicate with a TURN server using UDP, TCP, or TLS over TCP. + +"S": Shared Secret/Binding Request – Perform Shared Secret STUN messages before performing a STUN binding request on the address in this list position. The value of *STUN-TRANSPORT-TYPE* is "UDP", "TCP" or "TLS". These values are for "Binding Requests". "Shared Secret Requests" are always sent over TLS. + +In an ITU-T H.248 command reply: + +Each element of the string SHALL be of type **StunAddressReply** in ABNF format: + +``` +StunAddressReply = (IP4-address COLON PortNumber)/ (IP6- +address COLON PortNumber)/EToken [COLON ErrorCode] +PortNumber = UINT16 +EToken = "E" +ErrorCode = 1*3(DIGIT); could be extended +``` + +The ABNF syntax of IP4-address and IP6-address is defined in [IETF RFC 4566]. + +The MG may reply with an IP4 or IP6 address, for example "192.168.1.10:10000" and "FF1E:03AD::7F2E:172A:1E24:20000", + +or reply with an error information in which the Class and Number of the error (see section 11.2.9 of [IETF RFC 3489] or section 15.6 of [IETF RFC 5389]) is included. + +**Default:** Empty List + +**Defined in:** LocalControl + +**Characteristics:** Read/Write + +#### 7.2.1.2 NAT lifetime + +**Property name:** NAT Lifetime + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property ID: | natl (0x0002) | +| Description: | This property requests the MG to return the NAT binding lifetime associated with the transport address at a particular list position. | +| Type: | List of String | +| Possible values: |

In an ITU-T H.248 command request:

Each element may be one of the following characters:

T: "Time Request";

N: "No time request".

In an ITU-T H.248 command reply:

An integer (in string form) representing a Lifetime value,

Or:

E: "Error in list position", followed by the Class and Number of the error (section 11.2.9 of [IETF RFC 3489] or section 15.6 of [IETF RFC 5389]) is included in the response.

| +| Default: | Empty List | +| Defined in: | LocalControl | +| Characteristics: | Read/Write | + +#### 7.2.1.3 RTO value + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Retransmission timeout (RTO) Value | +| Description: | This property requests the MG to set the initial retransmission timer RTO interval as defined in section 7.2.1 of [IETF RFC 5389]. | +| Property ID: | rto (0x0003) | +| Type: | Integer | +| Possible values: | 1 ms to 600000 ms (10 minutes) | +| Default: | 100 ms | +| Defined in: | LocalControl | +| Characteristics: | Read/Write | + +### 7.2.2 Events + +None. + +### 7.2.3 Signals + +None. + +### 7.2.4 Statistics + +None. + +### 7.2.5 Error codes + +None. + +### 7.2.6 Procedures + +To determine a STUN mapped address, the MGC shall issue an ITU-T H.248 Add/Modify/Move.req command containing the "*stuna*" property on the relevant termination/stream. If the MG wants to modify the value of RTO, the "*rto*" property should also be set on the relevant termination/stream. The MGC shall include a value in each position of list of string for each element described in the "*stunb/ac*" property. + +For list positions designated with the value "*L*", the MG shall simply return an empty string for that position of the list. + +For list positions designated with the value "*B*", the MG shall perform a STUN binding request messaging. If the binding request is successful, the MG shall return the mapped address in the list position of the reply. If the binding request is unsuccessful, then the STUN error shall be returned in the list position. + +For list positions designated with the value "*S*", the MG shall perform a STUN Shared Secret request before issuing binding request messaging. The MG may perform a single Shared Secret request for all binding requests or issue multiple Shared Secret requests. STUN server implementations based on [IETF RFC 3489] do not support Shared Secret requests. + +If the MGC wishes to reset the mappings, then it shall resend the parameter in an ITU-T H.248 request indicating "*L*", "*B*" or "*S*". + +If the MGC wishes to receive the period of the binding lifetime with a NAT for an address it shall issue a "*natl*" property requesting "*T*" for each list element it wants a lifetime for and "*N*" for each element it does not want the time for. On receipt of the request, the MG will determine if a binding lifetime has been determined for a particular address. It will return the binding lifetime value if received from the NAT otherwise it will return "0". It is recommended that the "*natl*" property be included after the "*stuna*" property to maximize the possibility that a binding lifetime period is returned. + +If the peer side returns error code 300 (Try Alternate), the transport address of the alternate server is in the ALTERNATE-SERVER attribute. The MG should use this transport address to resend the same request message to the alternate server. If the MG cannot send or the request still fails, the MG should indicate the error code to the MGC. + +STUN server implementations based on [IETF RFC 3489] may not return a binding lifetime. The STUN information package should be used in this case. + +## 7.3 MG TURN client package + +| | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | MG TURN Client | +| Package ID: | mgturnc (0x00bf) | +| Description: | This package enables an MGC to determine the mapped IP address and port used for data relaying through a TURN server. It enables the procedures defined by [IETF RFC 5766] to operate in a split MGC/MG environment. | +| Version: | 1 | +| Extends: | None | + +### 7.3.1 Properties + +#### 7.3.1.1 TURN address + +| | | +|-----------------------|----------------| +| Property name: | TURN Address | +| Property ID: | turna (0x0001) | + +**Description:** This property requests a particular local transport address and port that the MG performs a TURN allocate request on with a remote TURN server in order to reserve an address. As per section 6 of [IETF RFC 5766] the MGC may send this particular local transport address and port to the peer as its remote IP address and port. + +**Type:** List of String + +**Possible values:** In an ITU-T H.248 command request: + Each element in the list of string SHALL be of type **TurnAddressReq** in ABNF format: + +``` + +TurnAddressReq = ("A" + [RequestedProps] [TurnTransportType] + [Lifetime] [ChannelSend]) / "N" +RequestedProps = SP "rp" COLON ReqP +TurnTransportType = SP "ttp" COLON TurnTranT +Lifetime = SP "l" COLON LifeT +ChannelSend = SP "c" COLON Channels +ReqP = 3* BinChar +BinChar = "0"/"1" +TurnTranT = "UDP"/"TCP"/"TLS" +LifeT = UINT32 +Channels = "SEND"/"CHANNEL" + +``` + +"A": Allocate Request – Perform a TURN Allocation request on the address in this list position. The REQUESTED-PROPS attribute may be indicated at the same time. The value of REQUESTED-PROPS is "000" to "111". The value of TURN-TRANSPORT-TYPE is "UDP", "TCP" or "TLS". LIFETIME is the value of the LIFETIME attribute. The value of ChannelS is "SEND" or "CHANNEL". This flag is used to request the MG to send application data using ChannelData messages or using Send and Data indications. + +"N": No change – Do not perform TURN address mapping for the address in this position. + +In an ITU-T H.248 command reply: + +Each element of the string contains a relay address, reflexive address and LIFETIME. Each element in the list of string SHALL be of type **TurnAddressReply** in ABNF format: + +``` + +TurnAddressReply = ((IP4RelayAddr SP IP4ReflexiveAddr +/ (IP6RelayAddr SP IP6ReflexiveAddr) SP LifeT ) / (EToken +[COLON ErrorCode]) +IP4RelayAddr = IP4-address COLON PortNumber +IP4ReflexiveAddr = IP4-address COLON PortNumber +IP6RelayAddr = IP6-address COLON PortNumber +IP6ReflexiveAddr = IP6-address COLON PortNumber +PortNumber = UINT16 +LifeT = UINT32 +EToken = "E" + +``` + +The ABNF syntax of IP4-address and IP6-address is defined in [IETF RFC 4566]. + +The MG may reply with the relay address, reflex address and the value of LIFETIME attribute, for example "192.168.1.10:10000 192.168.2.100:20000 11000" and "FF1E:03AD::7F2E:172A:1E24:20000 FF1E:03AD::7F2E:2AB3:9AA8:20000 30000". Or it may reply with an error indication in which the class and number of the error (see section 11.2.9 of [IETF RFC 3489] or section 15.6 of [IETF RFC 5389]) is included. + +**Default:** Empty List +**Defined in:** LocalControl +**Characteristics:** Read/Write + +#### 7.3.1.2 TURN refresh + +**Property name:** TURN Refresh + +**Property ID:** turnr (0x0002) + +**Description:** This property requests for a particular local transport address and port that the MG perform a TURN refresh request with a remote TURN server in order to keep the allocation and change the bandwidth or lifetime. As per section 7 of [IETF RFC 5766], a Refresh transaction can be used to either (a) refresh an existing allocation and update its time-to-expire, or (b) delete an existing allocation. MG should send periodic refresh request for each local transport address and port automatically. The MGC may request the MG to send a special refresh request to change bandwidth or lifetime via this property. + +**Type:** List of String + +**Possible values:** In an ITU-T H.248 command request: +Each element in the list of string SHALL be of type **RefreshReq** in ABNF format: + +**RefreshReq** = ("R" [COLON **LifeT**]) / "N" +**LifeT** = **UINT16** + +"R": Refresh Request – Perform a TURN refresh request on the address in this list position. Lifetime contains the value of the LIFETIME attribute. If the value of LIFETIME attribute is zero, this will cause the IP termination to remove the allocation, and all associated permissions and channel numbers. If a value for lifetime is not included a default lifetime as per [IETF RFC 5766] shall be assumed. + +"N": No change – Do not perform TURN refresh request for the address in this position. + +In an ITU-T H.248 command reply: + +Each element of the string may be LIFETIME. Each element in the list of string SHALL be of type **RefreshReply** in ABNF format: + +**RefreshReply** = **LifeT**/ **EToken** [:**ErrorCode**] + +Lifetime contains the value of the LIFETIME attribute. As per section 7.2 of [IETF RFC 5766], in a successful response, the + +LIFETIME attribute indicates the amount of additional time (the number of seconds after the response is received) that the allocation will live without being refreshed. + +Or reply with an error information in which the Class and Number of the error (see section 11.2.9 of [IETF RFC 3489] or section 15.6 of [IETF RFC 5389]) is included. + +**Default:** Empty List +**Defined in:** LocalControl +**Characteristics:** Read/Write + +#### 7.3.1.3 NAT lifetime + +**Property name:** NAT Lifetime +**Property ID:** natl (0x0003) +**Description:** This property requests the MG to return the NAT binding lifetime associated with the transport address at a particular list position. +**Type:** List of String +**Possible values:** In an ITU-T H.248 command request: +Each element may be one of the following characters: +*T*: "Time Request"; +*N*: "No time request". +In an ITU-T H.248 command reply: +A string based integer representing a Lifetime value, +Or: +*E*: "Error in list position", followed by the class and number of the error (section 11.2.9 of [IETF RFC 3489]) is included in the response. +**Default:** Empty List +**Defined in:** LocalControl +**Characteristics:** Read/Write + +### 7.3.2 Events + +None. + +### 7.3.3 Signals + +None. + +### 7.3.4 Statistics + +None. + +### 7.3.5 Error codes + +None. + +### 7.3.6 Procedures + +To determine a TURN relayed address, the MGC shall issue an ITU-T H.248Add/Modify/Move.req command containing the "*turna*" property on the relevant termination/stream. The MGC shall include a value in each position of list of string for each element described in the "*stunb/ac*" property. + +For list positions designated with the value "*N*", the MG shall simply return an empty string for that position of the list. + +For list positions designated with the value "*A*", the MG shall perform a TURN allocate request messaging. If the allocate request is successful the MG shall return the relayed address, reflex address and the value of LIFETIME attribute in the list position of the reply. The following attributes may be derived from the "*turna*" property: + +- EVEN-PORT, section 14.6 of [IETF RFC 5766]; +- LIFETIME, section 14.2 of [IETF RFC 5766]. + +Communication between the TURN client and the TURN server can run over UDP, TCP or TLS. "*TurnTransportType*" in the syntax of the "*turna*" property is used to indicate the desired transport type. + +When the TURN client has data to send to a peer, it may use either a ChannelData message or a Send indication. "*ChannelSend*" in the syntax of the "*turna*" property is used to indicate which method should be used. + +If the allocate request is unsuccessful then the TURN error shall be returned in the list position. + +If the MGC wishes to reset the mappings, then it shall resend the "*turna*" property in an ITU-T H.248 request indicating "*N*" or "*A*". + +To refresh an existing allocation and update its time-to-expire, or to delete an existing allocation, the MGC shall issue a Modify/Move.req command containing the "*turnr*" property on the relevant termination/stream. + +For list positions designated with the value "*R*" the MG shall perform TURN refresh request messaging. If the MGC wishes the TURN server to set the time-to-expire timer to something other than the default lifetime, the MGC indicates to the MG to include a LIFETIME attribute with the requested value. If the value of the LIFETIME attribute is 0, the TURN server immediately deletes the allocation. If the refresh request is successful, the MG shall return the LIFETIME attribute in the list position of the reply. If the refresh request is unsuccessful then the TURN error shall be returned in the list position. + +## 7.4 MGC STUN client package + +| | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | MGC STUN Client | +| Package ID: | mgcstunc (0x00c0) | +| Description: |

This package enables an MGC to determine the STUN mapped IP address and port for a particular media component. This package allows the STUN client to remain at the MGC level rather than being implemented in the MG.

NOTE – This package has been included for backward compatibility reasons.

| +| Version: | 1 | +| Extends: | None | + +### 7.4.1 Properties + +None. + +### 7.4.2 Events + +None. + +### 7.4.3 Signals + +#### 7.4.3.1 MGC initiated STUN request + +| | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Signal name: | MGC Initiated STUN Request | +| Signal ID: | mgcistunr (0x0001) | +| Description: |

The MGC shall send a signal for each media component address whose address is to be mapped. These signals may occur in the same ITU-T H.248 message.

The STUN response messages are not used in this case. It is used to fulfil the case described in section 10.3 of [IETF RFC 3489].

| +| Signal type: | Brief | +| Duration: | Not applicable | + +##### 7.4.3.1.1 Binding request message + +| | | +|-------------------------|-------------------------------------------------------------------| +| Parameter name: | Binding Request Message | +| Parameter ID: | brm (0x0001) | +| Description: | This parameter contains the MGC constructed STUN request message. | +| Type: | Octet String | +| Optional: | No | +| Possible values: | Any valid STUN request message. | +| Default: | None | + +##### 7.4.3.1.2 Transport address + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------| +| Parameter name: | Transport Address | +| Parameter ID: | ta (0x0002) | +| Description: | This parameter indicates the IP address of the media component that is to have its address STUN mapped. | +| Type: | Integer | +| Optional: | No | +| Possible values: | Any valid list position from the "stunb/ac" parameter. | +| Default: | None | + +### 7.4.4 Statistics + +None. + +### 7.4.5 Error codes + +None. + +### 7.4.6 Procedures + +The MGC provides the STUN message contents, STUN server address and media address to the MG which will send a packet from the media address containing the STUN message contents to the STUN + +server address. The response will be provided to the MGC, thus any protocol or error handling can remain at the MGC level. This package enables the scenario described in section 10.3 of [IETF RFC 3489]. + +## 7.5 STUN information package + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | STUN Information | +| Package ID: | stuni (0x00c1) | +| Description: | This package enables an MGC to determine the type of NAT the MG is behind and the binding lifetime associated with the STUN server. Signals and events may be applied to the Root Termination. | +| Version: | 1 | +| Extends: | None | + +### 7.5.1 Properties + +None + +### 7.5.2 Events + +#### 7.5.2.1 NAT type determination + +| | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Event name: | NAT Type Determination | +| Event ID: | nattd (0x0001) | +| Description: | This event detects the end of the NAT Type determination procedure (initiated by a NAT Determination signal) and returns the detected type. | + +##### 7.5.2.1.1 EventsDescriptor parameters + +None + +##### 7.5.2.1.2 ObservedEventsDescriptor parameters + +###### 7.5.2.1.2.1 NAT type + +| | | +|------------------------|----------------------------------------------------------------------------| +| Parameter name: | NAT Type | +| Parameter ID: | natt (0x0001) | +| Description: | The determined NAT type (scenario) as per section 10.1 of [IETF RFC 3489]. | + +NOTE - The original STUN protocol [IETF RFC 3489] was obsoleted by [IETF RFC 5389]. The original NAT type discovery process as per section 10.1 of [IETF RFC 3489] was moved to a self-contained specification [IETF RFC 5780]. Section 4 of [IETF RFC 5780] describes the NAT type discovery process using NAT type naming according to [IETF RFC 4787]. [IETF RFC 6888] also uses the NAT type naming according to [IETF RFC 4787]. + +| | | +|-------------------------|--------------------------------------------------------------------| +| Type: | Enumeration | +| Optional: | No | +| Possible values: | 0x0000: On the open Internet;
0x0001: Firewall that blocks UDP; | + +0x0002: Firewall that allows UDP out, and responses have to come back to the source of the request (like a symmetric NAT, but no translation). A symmetric UDP Firewall; + +0x0003: Full-cone NAT; + +0x0004: Symmetric NAT; + +0x0005: Restricted cone NAT; + +0x0006: Restricted port cone NAT. + +**Default:** None + +#### 7.5.2.2 Binding lifetime determination + +**Event name:** Binding Lifetime Determination + +**Event ID:** bld (0x0002) + +**Description:** This event detects the end of the Binding Lifetime determination procedure (initiated by a Binding Lifetime Determination signal) and returns the time period of the binding. + +##### 7.5.2.2.1 EventsDescriptor parameters + +None. + +##### 7.5.2.2.2 ObservedEventsDescriptor parameters + +###### 7.5.2.2.2.1 Binding lifetime + +**Parameter name:** Binding Lifetime + +**Parameter ID:** bl (0x0001) + +**Description:** The period of the life of the binding. + +**Type:** Integer + +**Optional:** No + +**Possible values:** 0-3600 seconds + +**Default:** None + +### 7.5.3 Signals + +#### 7.5.3.1 NAT type determination + +**Signal name:** NAT Type Determination + +**Signal ID:** nattd (0x0001) + +**Description:** This signal instructs the MG to detect the type of NAT that a particular media component IP address is behind. + +**Signal type:** Brief + +**Duration:** NA + +##### 7.5.3.1.1 Additional parameters + +###### 7.5.3.1.1.1 Transport address + +**Parameter name:** Transport Address + +**Parameter ID:** ta (0x0001) + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------| +| Description: | This parameter indicates the IP address of the media component that is to have its address STUN mapped. | +| Type: | Integer | +| Optional: | No | +| Possible values: | Any valid list position from the " stunb/ac " parameter. | +| Default: | None | + +#### 7.5.3.2 Binding lifetime determination + +| | | +|---------------------|---------------------------------------------------------------------------| +| Signal name: | Binding Lifetime Determination | +| Signal ID: | bld (0x0002) | +| Description: | This signal instructs the MG to detect the binding lifetime with the NAT. | +| Signal type: | Brief | +| Duration: | NA | + +##### 7.5.3.2.1 Additional parameters + +###### 7.5.3.2.1.1 Transport address + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------| +| Parameter name: | Transport Address | +| Parameter ID: | ta (0x0001) | +| Description: | This parameter indicates the IP address of the media component that is to have its address STUN mapped. | +| Type: | Integer | +| Optional: | No | +| Possible values: | Any valid list position from the " stunb/ac " parameter. | +| Default: | None | + +### 7.5.4 Statistics + +None. + +### 7.5.5 Error codes + +None. + +### 7.5.6 Procedures + +#### 7.5.6.1 NAT behaviour discovery as defined for original STUN protocol + +This package is used to support the procedures as outlined in section 10 of [IETF RFC 3489]. + +#### 7.5.6.2 NAT behaviour discovery as defined for updated STUN protocol + +This package could be also used to support the procedures according to [IETF RFC 5780]. + +# 8 ICE support + +The support of ICE implies that the SDP CANDIDATE attribute is supported. This can facilitate address gathering and description of candidates. However, due to the nature of the ITU-T H.248 connection model, several procedural changes are required. + +The text below is structured based on the various ICE protocol phases, relevant SDP attributes and their SDP Offer/Answer representation in call control signalling like SIP. Thus, the reader should be familiar with the original ICE RFC [IETF RFC 5245]. + +## Address gathering + +The MGC may request an MG to perform address discovery through the use of the wildcarding mechanism on the CANDIDATE attribute. In this case the MG is responsible for STUN server discovery. Fully specifying the CANDIDATE attribute will not result in any action. The candidate-attribute is specified by the following ABNF [IETF RFC 5245]: + +``` +candidate-attribute = "candidate" ":" foundation SP component-id SP + transport SP + priority SP + connection-address SP ;from [IETF RFC 4566] + port ;port from [IETF RFC 4566] + SP cand-type + [SP rel-addr] + [SP rel-port] + *(SP extension-att-name SP + extension-att-value) +``` + +NOTE 1 – Section 4.5 of [IETF RFC 6544] defines an extended ABNF grammar for the SDP "a=candidate:" attribute for TCP. + +NOTE 2 – *Trickle ICE* reuses above *vanilla ICE* syntax for the SDP "a=candidate:" attribute (see section 9.2 [b-IETF ice-trickle]). + +NOTE 3 – The priority value is the result of a particular address prioritization algorithm (see section 4.1.2.1 of [IETF RFC 5245] for basic rules and [b-IETF ice-dualstack] for guidelines related to ICE multihomed and IPv4/IPv6 dual stack fairness). + +The MGC shall either include values for, or wildcard mandatory fields. Including values provides a way of narrowing down the selection. For example: + +- If the MGC wanted a particular candidate type it could specify: + +``` +a=candidate:1 1 UDP $ $ typ host +a=candidate:2 1 UDP $ $ srflx raddr $ rport $ +``` + +- and the host address and server reflexive address would be returned. +- If the MGC wanted all candidate types it could specify: + +``` +a=candidate:$ $ $ $ $ $ typ * +``` + +- and the local, server reflexive address and relay addresses would be returned. + +If a request results in multiple candidates, then these shall be returned in multiple "a=" lines. + +As per section 4.3 of [IETF RFC 5245], if the MG utilizes RTCP, the MGC and MG MUST encode the RTCP candidate using the "a=rtcp" attribute as defined in [IETF RFC 3605]. If RTCP is not in use, the MGC and MG MUST signal that by using "b=RS:0" and "b=RR:0" as defined in [IETF RFC 3556]. + +If the MGC requires a MG to allocate a port for RTCP, the MGC will send the required information to request an RTCP port (e.g., "a=" line in SDP, a=rtcp \$). + +A further complication is provided by the selection of the "In-Use candidate" in the SDP media (m=) and connection (c=) lines. In the ITU-T H.248 Local Descriptor this is a local transport address in the MG. Whereas in ICE this may be another address. Therefore, in order to construct an SDP offer, the MGC shall determine the "In-Use candidate" from the CANDIDATE attributes returned in the response. + +The *remote-candidate-att* is related to the SDP (SIP) offer and provides the identity of the remote candidates that the offerer wishes the answerer to use in its answers. It is assumed that the MGC (acting as the offerer) will populate this attribute based on candidate information from the MG. + +Similarly, the ICE SDP "*ice-pwd-att*" attribute may be wildcarded or provided. + +If the MGC asks for candidates, it should provide or ask for credentials in order for the MG to be able to perform the necessary signalling. + +If MGC provides credentials, the MGC will send the required "*a=*" lines in SDP. For example: + +``` +a=ice-pwd:asd88fgpdd777uzjYhagZg +a=ice-ufrag:8hhY +``` + +If the MGC asks the MG to provide the credentials, the MGC will send the required "*a=*" lines in SDP. For example: + +``` +a=ice-pwd:$ +a=ice-ufrag:$ +``` + +If MGC does not supply the necessary "*a=*" lines in SDP, the MG may determine these credentials and return them to the MGC in a reply message. This is in order for the MG to be able to send a correct STUN message. + +The use of the "*a=ice-lite*" attribute indicates whether or not the agent implements a lite version of ICE (see also clause 6.1.6 and Appendix III). As the agent resides in the MG this information needs to be provided to the MGC in order for the information to be communicated to a peer. Given the structure of the "*a=ice-lite*" attribute the MGC is unable to perform a CHOOSE wildcard operation on the attribute. As such where the MG implements a "lite" version of ICE it shall include the "*a=ice-lite*" attribute in any command response containing the candidate attribute. + +Where a binary encoding of ITU-T H.248 is used, the ICE-related attributes may be realized through the use of [ITU-T H.248.1] Annex C.11 properties. In order to facilitate multiple values the "sub-list of" form should be used. + +## Connectivity checking + +In order for an MG to perform some ICE operations, the remote candidate list is required. This remote candidate list can be provided to the MG in the form of candidate attributes being placed in the appropriate RDs. The MGC may be required to reformat the SDP answer/offer received (i.e., via SIP) in order for it to be applicable to ITU-T H.248 structures. The setting of the candidate attributes in the RD will not in itself generate any ICE operation such as Connectivity Checking or keep alive mechanisms. ITU-T H.248 packages are used to trigger these operations. + +## 8.1 MG act-as STUN server package + +| | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | MG Act-as STUN Server | +| Package ID: | mgastuns (0x00c2) | +| Description: | This package enables an MGC to request that a particular address on an MG act as a STUN server in order to process, receive binding requests and return STUN binding responses. The purpose of the package is to enable the procedures defined in section 7.2 of [IETF RFC 5389]. | +| Version: | 1 | +| Extends: | None | + +### 8.1.1 Properties + +#### 8.1.1.1 Act-as STUN server + +| | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Act-as STUN Server | +| Property ID: | astuns (0x0001) | +| Description: | This property requests for a particular local transport address that the MG be prepared to receive STUN binding requests for the purpose of connectivity checking. | +| Type: | List of String | +| Possible values: |

In an ITU-T H.248 command request:

Each element in the list of string SHALL be of type MGActServer in ABNF format:

MGActServer = GroupID " " Foundation " " Component-id
 " RequestType
GroupID = UINT16
Foundation = UINT16
Component-id = UINT16
RequestType = "N"/"S"

GroupId is as per UINT16 in clause B.2 of [ITU-T H.248.1].

Component-id is as per <component-id> in section 15.1 of [IETF RFC 5245].

Foundation is as per <foundation> in section 15.1 of [IETF RFC 5245].

RequestType is:

N ("No request"): do not process STUN requests;

S ("STUN Server"): act as a STUN server receiving binding requests.

| +| Default: | "STUN Server" | +| Defined in: | LocalControl | +| Characteristics: | Read/Write | + +### 8.1.2 Events + +None. + +### 8.1.3 Signals + +None. + +### 8.1.4 Statistics + +None. + +### 8.1.5 Error codes + +None. + +### 8.1.6 Procedures + +To request the MG to act as a STUN server, the MGC should issue an ITU-T H.248 Add/Modify/Move.req command containing the "*astuns*" property on the relevant Termination/Stream. + +## 8.2 Originate STUN continuity check package + +**Package name:** Originate STUN Continuity Check +**Package ID:** ostuncc (0x00c3) +**Description:** This package enables an MGC to initiate a STUN continuity check binding request process at MG level. The purpose of the package is to enable the procedures defined in section 7 of [IETF RFC 5389]. +Version 1 supported UDP, version 2 of this package indicates in addition the support of TCP. +**Version:** 2 +**Extends:** None + +### 8.2.1 Properties + +#### 8.2.1.1 Host candidate realm + +**Property name:** Host Candidate Realm +**Property ID:** hcr (0x0001) +**Description:** This property indicates the realm the MG allocates IP address and port for host candidate. As per section 1 of [IETF RFC 5245], because ICE exchanges a multiplicity of IP addresses and ports for each media stream, it also allows for address selection for multi-homed and dual-stack hosts. As per section 4.1.1.1 of [IETF RFC 5245], host candidates are obtained by binding to ports (typically ephemeral) on an IP address attached to an interface (physical or virtual, including VPN interfaces) on the host. The information of host candidate is described in local SDP. If MGC requires the MG to gather more than one host candidate via local SDP, it uses this property to indicate to the MG to gather each of those host candidates in the indicated IP realm or VPN. +The property is applicable for UDP- and TCP-related ICE because the UDP- and TCP-specific syntax elements of the SDP "a=candidate:" attributes is not part of the property value syntax. +**Type:** List of String +**Possible values:** Each element in the list of string SHALL be of type `HostCandRealm` in ABNF format: + +``` +HostCandRealm = GroupID "|" Foundation "|" Component-id +"|" Realm +GroupID = UINT16 +Foundation = UINT16 +Component-id = UINT16 +Realm = ALPHA 0*63(ALPHA/ DIGIT) +ALPHA = %x41-5A / %x61-7A ; A-Z / a-z +DIGIT = %x30-39; 0-9 +``` + +Where: + +GroupId is as per UINT16 in clause B.2 of [ITU-T H.248.1]. + +Component-id is as per in section 15.1 of [IETF RFC 5245]. + +Foundation is as per in section 15.1 of [IETF RFC 5245]. + +Realm is a string used to discriminate overlapping IP address spaces. It is the identifier of the IP domain or VPN. + +e.g., + +"1|1|1|realm1", "1|2|1|realm2" + +And MGC sends such a local SDP to a MG (here an ICE for UDP example): + +``` +v=0 +c=IN IP4 $ +a=ice-pwd:YH75Fviy6338Vbrhrlp8Yh +a=ice-uf rag:9uB6 +m=audio $ RTP/AVP 0 +a=candidate:1 1 UDP 2130706431 $ $ typ host +a=candidate:2 1 UDP 2113929215 $ $ typ host +``` + +The MG should gather two host candidates. The first one is in IP realm "realm1" and the second one is in IP realm "realm2". + +**Default:** None +**Defined in:** LocalControl +**Characteristics:** Read/Write + +### 8.2.2 Events + +#### 8.2.2.1 Connectivity check result + +**Event name:** Connectivity Check Result +**Event ID:** ccr (0x0001) +**Description:** This event returns the result of an ICE connectivity check. + +##### 8.2.2.1.1 EventsDescriptor parameters + +None. + +##### 8.2.2.1.2 ObservedEventsDescriptor parameters + +###### 8.2.2.1.2.1 Candidate/transport pair + +**Parameter name:** Candidate/Transport Pair +**Parameter ID:** ctp (0x0001) +**Description:** The list of the successful candidate/transport pairs. +The Event parameter is applicable for UDP- and TCP-related ICE because the reported IP transport address value(s) is/are layer 4 (L4) protocol agnostic. +**Type:** List of String +**Optional:** No +**Possible values:** Each element in the list of string SHALL be of type **CandPair** in ABNF format: + +``` +CandPair = StreamID "|" GroupID "|" Foundation-l "|" +``` + +``` + +Foundation-r "|" Component-id [Lp-connection- +address] [Rp-connection-address] [Rc] +StreamID = UINT16 +GroupID = UINT16 +Foundation-l = UINT16 +Foundation-r = UINT16 +Component-id = UINT16 +Lp-connection-address = "|lp-" Connection-address COLON +PortNumber +Rp-connection-address = "|rp-" Connection-address COLON +PortNumber +Connection-address = IP4-address +Rc = "|RC" +PortNumber = UINT16 + +``` + +The ABNF syntax of IP4-address is defined in [IETF RFC 4566]. + +Where: + +StreamID is as per StreamId in clause B.2 of [ITU-T H.248.1]. + +GroupID is as per UINT16 in clause B.2 of [ITU-T H.248.1]. + +Foundation-l (Local Foundation) is as per in section 15.1 of [IETF RFC 5245]. + +Foundation-r (Remote Foundation) is as per in section 15.1 of [IETF RFC 5245]. + +Component-id is as per in section 15.1 of [IETF RFC 5245]. + +Lp (Local) Peer reflexive candidate as described in section 7.1.3.2 of [IETF RFC 5245]. + +Rp Peer reflexive remote candidate as described in section 7.2.1.3 of [IETF RFC 5245]. + +Rc (Role Change) is a flag to indicate that the control role has changed (i.e., controlled or controlling). Control role is described in section 7.2.1.1 of [IETF RFC 5245]. + +e.g., + +``` +"1|2|3|4|1|lp-202.2.3.4:1000" +``` + +Means that StreamID is 1, GroupID is 2, Local Foundation is 3, Remote Foundation is 4, Component-id is 1, and there is a local peer reflexive candidate in this candidate pair. The IP address of this local peer reflexive candidate is 202.2.3.4, and the port is 1000. + +**Default:** None + +#### 8.2.2.2 New peer reflexive candidate + +**Event name:** New Peer Reflexive Candidate + +**Event ID:** nprc (0x0002) + +**Description:** This event indicates that a new peer reflexive candidate was discovered during a connectivity check. + +##### 8.2.2.2.1 EventsDescriptor parameters + +None. + +##### 8.2.2.2.2 ObservedEventsDescriptor parameters + +###### 8.2.2.2.2.1 Candidate + +**Parameter name:** Candidate +**Parameter ID:** can (0x0001) +**Description:** A list of the newly discovered peer reflexive candidates. +The Event parameter is applicable for UDP- and TCP-related ICE because the reported IP transport address value(s) is/are L4 protocol agnostic. +**Type:** Sub-list of String +**Optional:** No +**Possible values:** Each element in the list of string SHALL be of type **peerCand** in ABNF format: + +``` +peerCand = StreamID "|" GroupID "|" Foundation "|" + Component-id "|" Connection-address COLON + PortNumber +StreamID = UINT16 +GroupID = UINT16 +Foundation = UINT16 +Component-id = UINT16 +Connection-address = IP4-address +PortNumber = UINT16 +``` + +The ABNF syntax of IP4-address is defined in [IETF RFC 4566]. + +Where: + +StreamID is as per StreamId in clause B.2 of [ITU-T H.248.1]. + +GroupID is as per UINT16 in clause B.2 of [ITU-T H.248.1]. + +Foundation is as per in section 15.1 of [IETF RFC 5245]. + +Component-id is as per in section 15.1 of [IETF RFC 5245]. + +A newly discovered peer reflexive candidate as described in section 7.1.3 of [IETF RFC 5245]. + +e.g., + +``` +"1|2|3|4|202.2.3.4:1000" +``` + +Means that the StreamID is 1, GroupID is 2, Foundation is 3, Component-id is 4, and a new peer reflexive candidate was discovered. The IP address of this peer reflexive candidate is 202.2.3.4, and the port is 1000. + +**Default:** None + +### 8.2.3 Signals + +#### 8.2.3.1 Send connectivity check + +**Signal name:** Send Connectivity Check +**Signal ID:** scc (0x0001) + +| | | +|---------------------|----------------------------------------------------------------------------------------------------| +| Description: | This signal initiates connectivity checking procedures as defined in section 7 of [IETF RFC 5245]. | +| Signal type: | Brief | +| Duration: | NA | + +##### 8.2.3.1.1 Additional parameters + +###### 8.2.3.1.1.1 Control + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------| +| Parameter name: | Control | +| Parameter ID: | cntrl (0x0001) | +| Description: | This parameter indicates the controlling role defined in section 7.1.2.2 of [IETF RFC 5245]. | +| Type: | Enumeration | +| Optional: | Yes | +| Possible values: | Controlling (0x0001): MG acts as controlling role
Controlled (0x0002): MG acts as controlled role | +| Default: | Controlling | +| Characteristics: | Read | + +#### 8.2.3.2 Send additional connectivity check + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Signal name: | Send Additional Connectivity Check | +| Signal ID: | sacc (0x0002) | +| Description: | This signal instructs a MG to initiate additional ICE connectivity check procedures in the case additional candidate/transport address pairs are identified. The MG shall use the CANDIDATE attributes in both the Local and Remote Descriptors to determine the candidate/transport address pairs to use for the connectivity check. The MG shall resume and only perform checks not already performed. | +| Signal type: | Brief | +| Duration: | NA | + +##### 8.2.3.2.1 Additional parameters + +###### 8.2.3.2.1.1 Control + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------| +| Parameter name: | Control | +| Parameter ID: | cntrl (0x0001) | +| Description: | This parameter indicates the controlling role defined in section 7.1.2.2 of [IETF RFC 5245]. | +| Type: | Enumeration | +| Possible values: | Controlling (0x0001): MG acts as controlling role
Controlled (0x0002): MG acts as controlled role | +| Default: | Controlling | +| Characteristics: | Read | + +### 8.2.4 Statistics + +None. + +### 8.2.5 Error codes + +None. + +### 8.2.6 Procedures + +#### 8.2.6.1 IP transport protocol indication + +STUN connectivity check procedures for UDP (section 7 of [IETF RFC 5245]) and TCP (section 7 of [IETF RFC 6544]) are largely overlapping, but there are also some L4 protocol specific aspects. Hence, the MG must know the specific STUN-over-L4 protocol layering. + +NOTE – The following related item is for further studies: + +- When L4-specific STUN connectivity checks are executed in L4-specific ITU-T H.248 streams, then there is no semantic problem due to the explicit L4 protocol indication in the ITU-T H.248 Stream Descriptor (i.e., the LD and/or RD). However, the situation in ICE/STUN based NAT-T is rather the opposite: there is a 1:1 mapping of ALL STUN connectivity checks to either (see ITU-T H.248 stream grouping model according to [ITU-T H.248.97]): + - a) a single ITU-T H.248 component stream; or + - b) a single ITU-T H.248 (de-)aggregation stream. +- There might be a gap concerning the indication of the specific L4 protocol type in an appropriate ITU-T H.248 signalling element. +- Furthermore, there are protocol stack cases: + - a) application specific layering such as "SCTP-over-DTLS-over-L4"; and + - b) generic layering "X-over-L4" cases. Leading to the basic question whether the ITU-T H.248.50 NAT-T toolkit should become "L4+ aware" or remain purely "L4+ agnostic" (as currently the case)? + +#### 8.2.6.2 Connectivity check procedures for UDP + +When the "Send Connectivity Check" (*scc*) Signal is sent, the MGC should initiate the STUN continuity check procedures as outlined in section 7 of [IETF RFC 5245]. As the ICE agent functionality is split between a MGC and MG and the MG is responsible for sending the connectivity checks, the agent role (controlled or controlling, see section 5.2 of [IETF RFC 5245]) should be provided. In order for the MGC to obtain the result of the connectivity check, it shall set the "Connectivity Check Result" (*ccr*) event. + +The usage of the "Send Connectivity Check" Signal shall clear the results of any previous connectivity checking on the Termination/Stream. + +If the *ccr* Event is set and the *scc* Signal is received, the MG shall apply the procedures of section 7.1.2 of [IETF RFC 5245] to form and prioritize a checklist. + +NOTE 1 – The calculation of the priority value basically follows section 4.1.2.1 of [IETF RFC 5245], though, there might be other policies such as [b-IETF ice-dualstack]. + +Once the procedures of section 7.1.3 of [IETF RFC 5245] have been completed, the MG shall then notify the MGC of the result. The MG shall deem the procedures of section 5.8 of [IETF RFC 5245] completed once all checks have reached the state "succeeded" or "failed". In order to uniquely identify the checks on the termination, the MG shall provide the StreamID, GroupID, foundation of the local candidate, foundation of the remote candidate and the component-id. If the control role of this candidate pair changes, an optional flag "Rc" is included in the end. The MG shall maintain the results + +of the checking for the lifetime of the Termination/Stream or until they are cleared by a subsequent "Send Connectivity Check" signal. + +Where there is only one stream or group the respective ids default to 1. + +If there are no successful candidate pairs for one of the particular component-ids in the list, then the connectivity check for that component-id has failed. + +If there are more than one successful candidate pairs for a particular component-id in the list, only the candidate pair having the highest priority will be reported. The "Sub-list of" shall be in the same order as the checklist in order to maintain relative priority. + +Depending on its connection role, "controlled" or "controlling", the MGC may use the result in the ObservedEventsDescriptor parameter *ccr/ctp* to determine which transport pair to use for the media connection. + +If a new peer reflexive candidate is discovered as per the procedure in section 7.1.3.2.1 of [IETF RFC 5245], and if the "New Peer Reflexive Candidate" (*nprc*) Event is set, the MG will notify the MGC with the new peer reflexive candidate. In order to identify this peer reflexive candidate, the MG shall provide the StreamID, GroupID, Foundation, Component-id and the transport IP address and port number of this peer reflexive candidate. If the MGC requires that the peer reflexive candidate be paired with other remote candidates besides the one in the valid pair that will be generated, the MGC may generate an updated offer which includes the peer reflexive candidate. This will cause it to be paired with all other remote candidates. The list of the candidate pairs is updated in this case. + +When a new peer reflexive candidate is discovered, the Connectivity Checks procedure continues. If the MGC updates the local candidates via the SDP in the ITU-T H.248 message, the MG will continue with any connectivity checks that are still in progress. It will not perform checks on the new candidates. The MGC shall send the "Send Additional Connectivity Check" (*sacc*) Signal to perform checking of the new candidates. + +In some kinds of conditions, where the list of the connectivity check candidate pairs is changed (i.e., a new stream is added, an existing stream is modified or a new peer reflexive candidate is discovered) additional connectivity check procedures may be initiated. The MGC may send the "Send Additional Connectivity Check" Signal to initiate a connectivity check procedure on any candidate/transport pair not previously checked. In this procedure, the MG shall only perform checks not already performed. Another example is where a new stream is added after the connectivity checks for the existing stream have finished. In this case, the additional connectivity checks will only check the candidate pairs of the newly added stream. + +#### 8.2.6.3 Connectivity check procedures for TCP + +This package may also be applied for TCP; the procedures of previous clause 8.2.6.2 are applicable under consideration of TCP specific aspects according to section 7 of [IETF RFC 6544]. + +## 8.3 STUN consent freshness package + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | STUN Consent Freshness | +| Package ID: | stnconfres (0x0120) | +| Description: | This package allows an MGC to request an MG to perform the STUN usage for Consent procedures described in [IETF RFC 7675]. This allows the MG to send STUN binding requests and receive STUN binding responses in order to determine whether application data may be sent on the Stream. | +| Version: | 1 | +| Extends: | None | + +### 8.3.1 Properties + +None. + +### 8.3.2 Events + +#### 8.3.2.1 Consent State + +**Event name:** Consent State +**Event ID:** constate (0x0001) +**Description:** This event allows a MG to indicate to the MGC whether consent has been granted or not for a particular stream. It is only reported if the state changes between "granted" and "not granted" (i.e. revoked) states and vice versa. In consent "not granted" state application data stops flowing. In consent "granted" state application data flows. + +##### 8.3.2.1.1 EventsDescriptor parameters + +###### 8.3.2.1.1.1 Request States + +**Parameter name:** Request States +**Parameter ID:** reqstate (0x0001) +**Description:** The parameter allows the MGC to request notification of a change to "granted" and/or "not granted" state. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** G Notify a transition to state "granted". +N Notify a transition to state "not granted". +B Notify a transition to state "granted" or "not granted". +**Default:** B + +##### 8.3.2.1.2 ObservedEventsDescriptor parameters + +###### 8.3.2.1.2.1 State + +**Parameter name:** State +**Parameter ID:** state (0x0001) +**Description:** This parameter indicates the consent state that the transport has transitioned to. +**Type:** Enumeration +**Optional:** No +**Possible values:** G Consent has been granted and application data is flowing. +N Consent is not granted and application data is not flowing. +**Default:** None + +#### 8.3.2.2 STUN Consent Request Failure + +**Event name:** STUN Consent Request Failure +**Event ID:** confail (0x0002) + +**Description:** This event allows a MG to indicate to the MGC when a response to a STUN binding request indicating the failure to renew consent. + +##### 8.3.2.2.1 EventsDescriptor parameters + +None. + +##### 8.3.2.2.2 ObservedEventsDescriptor parameters + +None. + +### 8.3.3 Signals + +#### 8.3.3.1 Consent Test + +**Signal name:** Consent Test +**Signal ID:** contst (0x0001) +**Description:** This signal initiates the combined consent freshness test using STUN request/response procedures as outlined in section 5.1 of [IETF RFC 7675]. +**Signal Type:** On/Off +**Duration:** Not applicable. + +##### 8.3.3.1.1 Additional parameters + +###### 8.3.3.1.1.1 Test Interval + +**Parameter name:** Test Interval +**Parameter ID:** tstint (0x0001) +**Description:** This parameter indicates the consent check interval as defined by section 5.1 of [IETF RFC 7675]. The MG sends consent checks at random intervals between 0.8N and 1.2N. +**Type:** Integer +**Optional:** Yes +**Possible values:** 4000 ms upwards +NOTE – The typical test interval is at the time scale of seconds and tens of seconds. Small interval sizes are not recommended due to significant messaging and processing overhead that this would introduce. +**Default:** 5000 ms + +### 8.3.4 Statistics + +None. + +### 8.3.5 Error codes + +None. + +### 8.3.6 Procedures + +#### 8.3.6.1 STUN Consent Freshness initiation + +To initiate the STUN consent freshness procedures from [IETF RFC 7675] the MGC shall send the "Consent Test" (*stnconfres/contst*) Signal on the ITU-T H.248 stream where the consent is required. The *stnconfres/contst* Signal should be sent prior to or in the same ITU-T H.248 command as any + +signals initiating ICE connectivity checking to ensure that consent is granted as a result of successful initial ICE procedures. + +On reception of the *stnconfres/contst* Signal the MG shall initiate the consent procedures in section 5.1 of [IETF RFC 7675]. As described the MG must not send application data (e.g., RTP, RTCP, SCTP, datagram transport layer security (DTLS)), over any transport protocol (e.g., UDP, TCP) on an ICE-initiated connection unless the receiving endpoint consents to receive the data. After a successful ICE connectivity check on a particular transport address, subsequent consent shall be obtained following the procedures described [IETF RFC 7675]. The MG shall send a STUN binding request consent check at the random interval indicated by the "Test Interval" (*tstint*) parameter in order to maintain consent. + +When consent is granted the MG may send application data on the Stream. The granting of consent does not override other methods for controlling the flow of application or transport related data such as the Local Control StreamMode property [ITU-T H.248.1]. + +In order to be notified about the consent state the MGC should set the "Consent State" (*stnconfres/contst*) Event with the required states on the applicable Stream. As the Event indicates state transitions, the MGC should set the Event when sending the *stnconfres/contst* Signal to ensure the initial transition from consent "not-granted" (i.e. the default state before the completion of ICE connectivity check when the *stnconfres/contst* Signal is active) to a granted state after initial consent checking is reported. + +The state transitions to a consent "granted" state on receipt of a valid STUN binding response. The state transitions to a consent "not-granted" state when a valid STUN binding response corresponding to one of the STUN requests sent in the last 30 seconds has not been received from the remote peer's Transport Address or the MG detects an immediate revocation of consent via one of the methods in section 4.2 of [IETF RFC 7675]. A MGC may also be notified of the revocation of consent based on the detection of Events related to a closure of the transport connection, i.e., a TLS *BNCChange* Event indicating "bearer release" [ITU-T H.248.90]. + +#### 8.3.6.2 STUN consent request failure + +In order to be notified of a failed STUN consent refresh the MGC shall set the "STUN Consent Request Failure" (*stnconfres/confail*) Event on the applicable Stream. When the MG detects a failure of a STUN consent refresh to renew the consent it shall send a Notify.Req with the *stnconfres/confail* ObservedEvent. The MGC may then decide to continue to allow the MG to send STUN consent refreshes, or stop STUN consent refreshes or to take another action as appropriate. + +#### 8.3.6.3 STUN Consent Freshness deactivation + +To stop sending STUN consent requests the MGC should turn the *stnconfres/contst* Signal "off" by removing it from the applicable stream via a Modify.req command. On reception of the Signal the MG shall stop sending STUN consent refreshes. If any of the *stnconfres* Package Events are active on the Stream, then the MG shall stop sending application data at the expiry of the consent period. If no *stnconfres* Package Signals or Events are active on the Stream, then the STUN consent refresh procedures are no longer applicable to the Stream and application data may flow. + +#### 8.3.6.4 STUN Consent Freshness response + +In order for a MG to respond to STUN binding requests used for consent refresh the MGC shall use the "MG act-as STUN server" package (clause 8.1). + +#### 8.3.6.5 Connection liveness + +If the STUN consent freshness mechanism is used, no additional keepalives are needed to maintain liveness. E.g., such as those initiated through the use of the "Keep alive request" package (see clause 9.2). + +Keepalives can be initiated through the use of the "Keep alive request" package (clause 9.2). + +# 9 Keep-alive and pinhole support + +The packages in this clause provide a means of opening a pinhole through a NAT and to maintain a binding with the NAT. It does not rely on ICE techniques. + +## 9.1 MGC-originated STUN request package + +**Package name:** MGC Originated STUN Request + +**Package ID:** mgcostunr (0x00c4) + +NOTE 1 – Section 10 of [IETF RFC 5245] makes use of this mechanism. + +**Description:** The MGC may also periodically request the MG to send a STUN request in order to keep the binding with the NAT "alive". This should be done before the expiry of the keep-alive period. + +NOTE 2 – This package is an exception to the rule in the scope that the MG determines the address to which a Binding Request is sent. + +NOTE 3 – The package deals with IP address information, which is direction specific (source and destination) from an IP host perspective. The package description qualifies the source and destination specific parts, however, there is basically the assumption of address symmetry (i.e., the *local source address* is equal to the *local destination address*, and the same for remote addresses). + +**Version:** 1 + +**Extends:** None + +### 9.1.1 Properties + +None + +### 9.1.2 Events + +#### 9.1.2.1 STUN binding request failure + +**Event name:** STUN Binding Request Failure + +**Event ID:** fail (0x0001) + +**Description:** This event is triggered if a STUN binding request has failed. + +##### 9.1.2.1.1 EventsDescriptor parameters + +###### 9.1.2.1.1.1 From address + +**Parameter name:** From Address + +**Parameter ID:** fa (0x0001) + +**Type:** List of String + +**Optional:** No + +**Possible values:** "Y" (Yes): Failure reporting is required for this list position. +"N" (No): Failure reporting is not required for this list position. + +##### 9.1.2.1.2 ObservedEventsDescriptor parameters + +###### 9.1.2.1.2.1 Failure + +**Parameter name:** Failure + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter ID: | fail (0x0001) | +| Description: | This parameter contains the reason for the failure. | +| Type: | String | +| Optional: | No | +| Possible values: |

If the response of STUN binding request is "time out", error code 1000 follows the <list position>.

If the mapping address in the response of STUN binding request changes, error code 1001 and the new mapping address follows <list position>. The format is "<list position>:IP address ":" port. e.g., "1:202.1.2.3:1000"

| +| Default: | None | + +### 9.1.3 Signals + +#### 9.1.3.1 Send STUN request + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Signal name: | Send STUN Request | +| Signal ID: | stunr (0x0001) | +| Description: | This signal instructs a MG to send a binding request from the local source address to the remote destination address as contained in the RD. | +| Signal type: | Brief | +| Duration: | NA | + +##### 9.1.3.1.1 From address + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | From Address | +| Parameter ID: | fa (0x0001) | +| Description: | This parameter contains the local source addresses where the binding request should be sent from, to the corresponding remote destination address. | +| Type: | List of String | +| Optional: | No | +| Possible values: | N ("No Request"): do not perform a STUN binding request from the local source address. | +| Default: | None | + +##### 9.1.3.1.2 Retransmission time interval + +| | | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Retransmission Time Interval | +| Parameter ID: | rti (0x0002) | +| Description: | This parameter contains the initial retransmission time interval for the STUN request, as RTO defined in section 7.2.1 of [IETF RFC 5389]. | +| Type: | Integer | +| Optional: | Yes | + +**Possible values:** 1 ms to 600000 ms (10 minutes) + +**Default:** 100 ms + +### 9.1.4 Statistics + +None. + +### 9.1.5 Error codes + +None. + +### 9.1.6 Procedures + +The MGC should trigger the MG to initiate a STUN binding request to the remote address when it suspects that the local address is behind a restricted cone NAT. This will have the effect of opening a pinhole, allowing the remote end to send packets to the local end. If the MGC initiates a STUN binding request to the remote address, it can keep NAT bindings active. If there are no packets sent between the local and remote address pairs being used for media for *Tr* seconds (where packets include media and previous keep-alives; variable *Tr* refers to Signal parameter value *mgcostunr/sstunr/rti*), the MG MUST generate a keep-alive on that pair. To detect STUN binding request failures the *fail* Event should be set. + +This procedure is distinct from the ICE -related STUN continuity check procedures. + +## 9.2 Keep alive request package + +**Package name:** Keep Alive Request + +**Package ID:** kar (0x00c5) + +**Description:** This package enables the MGC to request the MG to send a packet in order to open a pinhole through a server or to maintain a NAT binding. This packet goes through the same way as the media flows. For example it allows the techniques as defined in section 10 of [IETF RFC 5245]. + +NOTE – This package is an exception to the rule in the scope that the MG determines the address to which a Binding Request is sent. + +**Version:** 1 + +**Extends:** None + +### 9.2.1 Properties + +None. + +### 9.2.2 Events + +None + +### 9.2.3 Signals + +#### 9.2.3.1 Send keepalive packet + +**Signal name:** Send Keepalive Packet + +**Signal ID:** skap (0x0001) + +**Description:** This signal instructs a MG to send a keepalive packet from the local source address to the remote destination address contained in the RD. + +**Signal type:** Brief + +**Duration:** NA + +##### 9.2.3.1.1 From address + +**Parameter name:** From Address + +**Parameter ID:** fa (0x0001) + +**Description:** This parameter contains the local source addresses where the keepalive packet should be sent from, to the corresponding remote destination address. The MGC shall include a value in each position of the list of string for each element as described in the "*stunb/ac*" property (see clause 7.1.1.1). + +**Type:** List of String + +**Optional:** No + +**Possible values:** "Send" (*S*): send a keepalive packet from the local address. +"Not Send" (*N*): do not send a keepalive packet from the local address. + +**Default:** None + +##### 9.2.3.1.2 Keep alive transmission interval + +**Parameter name:** Keep Alive Transmission Interval + +**Parameter ID:** ti (0x0002) + +**Description:** This parameter contains the transmission time interval for sending the keepalive packet. The value of this parameter corresponds to the Tr timer from [IETF RFC 5245]. + +**Type:** Integer + +**Optional:** Yes + +**Possible values:** 15000 ms or more + +**Default:** 15000 ms (15 seconds), unless provisioned otherwise. + +##### 9.2.3.1.3 Keep alive packet type + +**Parameter name:** Keep Alive Packet Type + +**Parameter ID:** kapt (0x0003) + +**Description:** This parameter indicates the type of keep alive packet type. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** et (0x0000): Transport (i.e., UDP, datagram congestion control protocol (DCCP)) packet of 0-byte; +rm (0x0001): RTCP packets multiplexed with RTP packets; +sbi (0x0002): STUN binding indication; +cn (0x0003): RTP packet with comfort noise payload; +no (0x0004): Reserved for RTP packet with No-Op payload (see [b-IETF no-op]); +iv (0x0005): RTP packet with incorrect version number; + +up (0x0006): RTP packet with unknown payload type. + +NOTE – Value no (0x0004) is reserved for a future payload type. + +**Default:** up (0x0006): RTP packet with unknown payload type + +### 9.2.4 Statistics + +None. + +### 9.2.5 Error codes + +None. + +### 9.2.6 Procedures + +#### 9.2.6.1 MGC stimuli for IP bearer path keep-alive requests + +The IP bearer path related keep-alive functions are part of overall NAT traversal solutions. The MGC may trigger keep-alive procedures due to: + +- local policy (provisioned policy, e.g., in case that all calls of an IP network domain require keep-alive support); or/and +- call-individual requests (and parameterization) by application control protocol signalling (see e.g., [b-IETF RFC 6223], [b-IETF RFC 5626], [b-IETF rkeep]). + +**Example:** A SIP network with usage of [b-IETF RFC 6223]: the MGC could (inter alia) derive the Signal parameters "Keep Alive Transmission Interval" (*kar/skap/ti*) and "Keep Alive Packet Type" (*kar/skap/kapt*) from SIP signalling. + +#### 9.2.6.2 Triggering keep-alive at MG by MGC + +In order to open or maintain a NAT binding, the MGC should send the "Send Keepalive" (*skap*) signal to the MG to initiate sending a keep-alive packet to the remote address. This will have the effect of opening a pinhole (or keeping a NAT binding open) allowing the remote end to send packets to the local end. The "Keep Alive Transmission Interval" (*ti*) parameter is used in order for the MG to autonomously send a keep-alive packet when no packets have been detected for the address for time interval *Tr*. + +Where a MGC utilizes a "Send Keepalive Packet" request signal with the "RTP packet with unknown payload type", it may be required to communicate this to a peer MGC via the call control signalling embedded SDP. An MGC on reception of this SDP attribute should then set this SDP attribute in the Remote Descriptor of the applicable MG Termination/Stream. It indicates to the MG that the remote end will utilize a keep-alive using an RTP packet with an unknown payload type. + +# 10 Package-independent NAT-T procedures + +## 10.1 Support for MG terminated STUN-based connectivity checks + +### 10.1.1 Overview + +STUN-based connectivity checks can be originated or terminated by the MG. Clause 8.2 defines support for MG originated STUN connectivity checks. This clause covers network scenarios where the MG is requested to terminate the STUN-based connectivity check procedure of STUN application ICE (e.g., model according Figure 2). Appendix I.1 illustrates an example use case in more detail. + +NOTE – A MG which only supports termination of STUN-based connectivity check procedures necessarily only supports ICE-lite. + +### 10.1.2 Required MG support functions + +The MG is required to support: + +- the STUN protocol [IETF RFC 5389] at the IP bearer interface of the MG (clause 10.1.3); +- the signalled credentials (for the bearer plane STUN-based connectivity checks) in ITU-T H.248 (clause 10.1.4); +- the ICE conclusion process (including media latching) (clause 10.1.5); and optionally +- reporting of latched addresses to the MGC (clause 10.1.5). + +### 10.1.3 Indication of bearer type "STUN/L4/IP" + +The MGC may indicate a STUN-enabled termination/stream endpoint by ICE-specific SDP in the LD/RD (see next clause). + +### 10.1.4 Signalling of credentials + +#### 10.1.4.1 General behaviour + +The motivation for credentials is described in sections 2.5 and 7 in [IETF RFC 5245], e.g., + +- *Each STUN connectivity check is covered by a message authentication code (MAC) computed using a key exchanged in the signaling channel. This MAC provides message integrity and data origin authentication, thus stopping an attacker from forging or modifying connectivity check messages.* + +The two ICE-specific SDP attributes "ice-pwd" and "ice-ufrag" are used for that purpose. The MGC shall signal these SDP elements to the MG. + +NOTE – See also section 7.1.2.3 of [IETF RFC 5245], which specifies that STUN's "short-term credentials" need to be used by ICE, and section 10.1 of [IETF RFC 5245], which defines this short-term credential mechanism, and which explains why username and password need to be exchanged via the signalling channel. + +#### 10.1.4.2 Detailed ITU-T H.248 signalling of credentials + +The usage of credentials in the ITU-T H.248 Local Descriptor and Remote Descriptor, in the direction from MGC to MG (command request) and vice versa (command reply), depends on the applied ICE protocol variant, and whether the resource management of ICE credential is provided by the MGC or MG, is summarized in Table 2: + +**Table 2 – Usage of SDP-defined credentials in ITU-T H.248 LD and RD** + +| No. | Resourcemanager | ICE variant | SDP attributes (credentials) | MGC-to-MG (request) | | MG-to-MGC (reply) | | +|-----|-----------------|-------------|--------------------------------|---------------------|------------|-------------------|----------| +| | | | | LD | RD | LD | RD | +| 1.1 | MG (Note1) | ICE-lite | "a=ice-ufrag:"
"a=ice-pwd:" | Yes
Yes | No
No | Yes
Yes | No
No | +| 1.2 | | full ICE | "a=ice-ufrag:"
"a=ice-pwd:" | Yes
Yes | Yes
Yes | Yes
Yes | No
No | +| 2.1 | MGC (Note 2) | ICE-lite | "a=ice-ufrag:"
"a=ice-pwd:" | Yes
Yes | No
No | O
O | No
No | +| 2.2 | | full ICE | "a=ice-ufrag:"
"a=ice-pwd:" | Yes
Yes | Yes
Yes | O
O | No
No | + +NOTE 1 – SDP would be wildcarded CHOOSE in case of MG level resource management. + +NOTE 2 – To the optional (O) tag in the MG reply column: The MGC chooses ICE *ufrag* and *passwd* values and sends them to the MG in the requested Local Descriptor. If the MGC locally stores these values, then the MG is not required to reply them back to the MGC. Thus it may be optional for the MG to reply *ice-ufrag* and *ice-pwd* values to MGC. + +### **10.1.5 ICE conclusion process (STUN-specific media latching)** + +The STUN connectivity check procedure provides an explicit indication to the MG about the existence of a remote NAT device in the IP bearer path, leading to the conclusion to perform latching. + +NOTE – Background: this requirement relates to the *ICE conclusion process* as described in section 8 of [IETF RFC 5245]. This conclusion process depends on the supported ICE variant and, in case of full-ICE, on the ICE role (controlling or controlled). + +The MG shall autonomously perform the ICE conclusion process which implies such STUN-specific latching, i.e., without any explicit indication by the MGC (as in case of [ITU-T H.248.37] stimulated latching). See also example in Appendix I.1. + +The MGC may subscribe for optional address reporting (according to clause 7 of [ITU-T H.248.37]). + +# Appendix I + +## Example signalling scenarios for package-independent NAT-T procedures + +(This appendix does not form an integral part of this Recommendation) + +## I.1 Example #1: ICE/STUN support by ITU-T H.248 IP access gateways + +### I.1.1 Network model + +Figure I.1 illustrates a "half call" model, which is consistent with the network model of clause 6.1.1. An ITU-T H.248 IP-IP gateway is located between access and core network level. It's a widespread model for many IP-based network access technologies. + +![Figure I.1 – Network model for ITU-T H.248 IP access gateways. The diagram shows a 'half call' model where an ITU-T H.248 IP-IP gateway is located between the access and core network levels. The User Equipment (UE) contains an Outbound support (STUN client) and an ICE support (STUN client/server). The NAT/FW is between the UE and the access network. The access network contains a STUN/TURN media relay and a STUN/TURN server. The core network contains an ITU-T H.248 gateway with an ICE/STUN support and a Media gateway. The Call/session control (SIP) is handled by an ICES/TUN function and an MGC. The Media is handled by the Media gateway. The diagram illustrates seven signalling steps: I) STUN gathering address candidates (STUN binding request/response), II) Call/session control signalling (SIP INVITE[SDP O/A with ICE credentials]), III) ITU-T H.248 context creation (ADD.req[with SDP-based ICE credentials]), IV) STUN connectivity checks (STUN binding request/response), V) ITU-T H.248 MG: STUN authentication, VI) ITU-T H.248 MG: STUN-specific latching, and VII) Optional address reporting (ITU-T H.248.37 adr package). A note indicates that the STUN/TURN server could be also located at core network level (see also Figure 2).](408c4798ea60469e0728a7cbbd598668_img.jpg) + +UE + +Outbound support +STUN client + +ICE support +STUN client/server + +NAT/FW + +Call/session control (SIP) + +ICES/TUN function + +Call/session control + +MGC + +ITU-T H.248 gateway control protocol + +ICE/STUN support + +Media gateway + +Media + +STUN/TURN media relay + +STUN/TURN server + +Access network + +Core network + +I) STUN gathering address candidates +STUN binding request/response + +II) Call/session control signalling +SIP INVITE[SDP O/A with ICE credentials] + +III) ITU-T H.248 context creation +ADD.req[with SDP-based ICE credentials] + +IV) STUN connectivity checks +STUN binding request/response + +V) ITU-T H.248 MG: STUN authentication + +VI) ITU-T H.248 MG: STUN-specific latching + +VII) Optional address reporting +(ITU-T H.248.37 adr package) + +NOTE –The STUN/TURN server could be also located at core network level (see also Figure 2). + +H.248.50(16)\_FI.1 + +Figure I.1 – Network model for ITU-T H.248 IP access gateways. The diagram shows a 'half call' model where an ITU-T H.248 IP-IP gateway is located between the access and core network levels. The User Equipment (UE) contains an Outbound support (STUN client) and an ICE support (STUN client/server). The NAT/FW is between the UE and the access network. The access network contains a STUN/TURN media relay and a STUN/TURN server. The core network contains an ITU-T H.248 gateway with an ICE/STUN support and a Media gateway. The Call/session control (SIP) is handled by an ICES/TUN function and an MGC. The Media is handled by the Media gateway. The diagram illustrates seven signalling steps: I) STUN gathering address candidates (STUN binding request/response), II) Call/session control signalling (SIP INVITE[SDP O/A with ICE credentials]), III) ITU-T H.248 context creation (ADD.req[with SDP-based ICE credentials]), IV) STUN connectivity checks (STUN binding request/response), V) ITU-T H.248 MG: STUN authentication, VI) ITU-T H.248 MG: STUN-specific latching, and VII) Optional address reporting (ITU-T H.248.37 adr package). A note indicates that the STUN/TURN server could be also located at core network level (see also Figure 2). + +**Figure I.1 – Network model for ITU-T H.248 IP access gateways +(derived from Figure 2 with scope on half call only)** + +The user equipment (UE) provides ICE-controlled STUN/TURN procedures according to clause 6.5.3. + +### I.1.2 Example signalling at SIP and ITU-T H.248 interfaces + +Figure I.1 highlights the most important phases during the establishment of an outgoing call. The communication between the UE and STUN/TURN server as well as the UE and SIP servers is out of scope of this appendix. Only some significant SIP/SDP is indicated here. + +The UE starts to gather addresses by contacting a STUN server (phase I; the UE receives the outgoing address of the NAT/FW (so called *server reflexive address*) by the STUN binding request/response cycle). After the *address prioritization* step (by the UE), an outgoing SIP message inclusive of an SDP offer is sent (phase II) with the purpose of advertisement of the candidate address(es). Table I.1 indicates the significant SDP for ICE. + +**Table I.1 – Example command encoding– (SIP) SDP Offer** + +| (SIP) SDP encoding | Comments | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
v=0 o=... s=... t=... m=audio <UE_A_port_audio_rtp> RTP/AVP ... c=IN IP6 <UE_A_IP_addr_audio_rtp> ... a=candidate:... a=ice-ufrag:<UE_A_ice_ufrag_audio> a=ice-pwd:<UE_A_ice_pwd_audio> ...
|

Two type of ICE-related SDP information:

  1. 1. Address advertisement ("candidate(s)")
  2. 2. Authentication and message-integrity mechanisms for STUN
| + +The IP bearer path is routed through the MG. The subsequent STUN based connectivity checks will be therefore processed by the MG. The MGC prepares the MG correspondingly (phase III) by creating a Context and stream endpoint (SEP). The SEP requires the information for STUN authentication, see Table I.2. + +**Table I.2 – Example command encoding – MGC request** + +| ITU-T H.248 encoding (shortened command) | Comments | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
MGC to MG: MEGACO/3 [11.9.19.65]:55555 Transaction = 1 {   Context = \$ {     Add = ip/\$/\$/\$ {       Media {         Stream = 1 {           LocalControl {             ipdc/realm = <access realm>,             Mode = Inactive,             ...           },           Local {             v=0             c=IN IP6 \$             m=audio \$ RTP/AVP -             a=ice-ufrag:<IP_A_ice_ufrag_audio> ; (Note 1)             a=ice-pwd:<IP_A_ice_pwd_audio> ; (Note 1)           },           Remote {             v=0             c=IN IP6 <UE_A_IP_addr_audio_rtp>             m=audio <UE_A_port_audio_rtp> RTP/AVP -             a=ice-ufrag:<UE_A_ice_ufrag_audio>             a=ice-pwd:<UE_A_ice_pwd_audio>           }         }       }     }   } } ...
|

NOTE 1 – Or wildcard CHOOSE in case of MG level management of resources "ICE username fragment" and "ICE password" (see also Table 2 in clause 10.1.4.2):

a=ice-ufrag: \$ a=ice-pwd:\$
| + +A possible example MG reply is indicated in Table I.3. + +**Table I.3 – Example command encoding– MG reply** + +| ITU-T H.248 encoding (shortened command) | Comments | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 MG to MGC: MEGACO/3 [125.125.125.111]:55555 Reply = 1 {   Context = <C1> {     Add = <IP_A> {       Media {         Stream = 1 {           Local {             v=0             c=IN IP6 <IP_A_IP_addr_audio>             m=audio <IP_A_port_audio_rtp> RTP/AVP -             a=ice-ufrag:<IP_A_ice_ufrag_audio>             ; ice-pwd attribute might not be returned as             MG does not perform STUN binding request authentication             initially (Note 1)           }           ...         },         Remote {           v=0           c=IN IP6 <UE_A_IP_addr>           m=audio <UE_A_port_audio_rtp> RTP/AVP -           a=ice-ufrag:<UE_A_ice_ufrag_audio>           a=ice-pwd:<UE_A_ice_pwd_audio>         },       }     }   } }
|

NOTE 1 – The "a=ice-pwd" value in this SEP's Local Descriptor is used by the UE when generating STUN binding requests (section 7.1.2.3 of [IETF RFC 5245], e.g., with agent "L = UE" and with agent "R = MG"). This SEP then, when receiving such STUN binding requests (thus as STUN server) needs to use it's own password (in the Local Descriptor) to check the received STUN binding request's validity (section 7.2 of [IETF RFC 5245] and section 10.1.2 of [IETF RFC 5389]).

Therefore, the "a=ice-pwd" attribute in the Local Descriptor is actually needed. But, if the MG is an ICE-lite endpoint, it may ignore the "a=ice-pwd" attribute in the RD, because in this case it never generates and sends STUN binding requests itself (see also Table 2 in clause 10.1.4.2).

| + +The MG monitors the IP bearer path and terminates STUN connectivity checks (phase V). The learnt addresses are used for latching, i.e., the adaption of the remote destination address (phase VI). + +This kind of latching (as part of the "ICE conclusion process") is called (here) STUN-specific latching, similar to ITU-T H.248.37-stimulated latching. Both belong conceptionally to the overall function of "media latching" (as a kind of NAT traversal mechanism), but differ from ITU-T H.248 perspective. + +NOTE – The difference: + +- "ITU-T H.248.37 latching": explicitly triggered latching via an ITU-T H.248 Signal; +- "STUN-specific latching" (i.e., MG autonomously performs the ICE conclusion process (which incorporates latching of the peer's transport address, chosen by the controlling side)): implicitly triggered latching via "ICE/STUN" specific SDP. + +The MGC could enable the address reporting capability (according to [ITU-T H.248.37]), which is normally not required for the progress of the call establishment process. + +# Appendix II + +## ICE for TCP + +(This appendix does not form an integral part of this Recommendation.) + +## II.1 Introduction + +The purpose of this appendix is to highlight major differences of *ICE for TCP* vs the original *ICE for UDP*. Only aspects relevant for ITU-T H.248 entities are indicated. Communication service specific aspects of ICE are out of scope of this Recommendation. + +NOTE – For instance, the *Web Real-Time Communication* (WebRTC) service imposes a given protocol stack layering {DTLS|SRTP-over-UDP|TCP-over-IP} (see [b-IETF rtcweb-transport]), which leads e.g., to the layering of a single DTLS connection over UDP or TCP. Hence, there is a tight coupling between DTLS usage and ICE/STUN for UDP and TCP. + +## II.2 MG bearer interface: protocol stack + +The "ICE for TCP" protocol stack (Figure II.1) is defined in section 3 of [IETF RFC 6544]: + +![Figure II.1 – ICE for TCP – protocol stack (MG bearer interface). The diagram shows two protocol stack diagrams, (a) and (b), illustrating the layers for ICE for TCP. Both stacks start with 'Application protocol' at the top. In (a), 'With (D) TLS transport security', the stack is: Application protocol -> RTP / non-RTP -> STUN | TLS | DTLS -> RFC 4571 framing protocol ('32-bit Shim header') -> TCP -> IPv4 | IPv6 -> Lower layers. In (b), 'Without (D) TLS', the stack is: Application protocol -> non-RTP -> STUN | RTP -> RFC 4571 framing protocol ('32-bit Shim header') -> TCP -> IPv4 | IPv6 -> Lower layers.](91b12db3c85bbf466ad27eb3665a1b06_img.jpg) + +The diagram illustrates two protocol stack configurations for the MG bearer interface. Both stacks share a common base of Lower layers, IPv4 | IPv6, TCP, and RFC 4571 framing protocol ("32-bit Shim header"). + +**a) With (D) TLS transport security:** The stack from top to bottom is: Application protocol, which branches into RTP and non-RTP; STUN | TLS | DTLS; RFC 4571 framing protocol ("32-bit Shim header"); TCP; IPv4 | IPv6; and Lower layers. + +**b) Without (D) TLS:** The stack from top to bottom is: Application protocol, which branches into non-RTP; STUN | RTP; RFC 4571 framing protocol ("32-bit Shim header"); TCP; IPv4 | IPv6; and Lower layers. + +Figure II.1 – ICE for TCP – protocol stack (MG bearer interface). The diagram shows two protocol stack diagrams, (a) and (b), illustrating the layers for ICE for TCP. Both stacks start with 'Application protocol' at the top. In (a), 'With (D) TLS transport security', the stack is: Application protocol -> RTP / non-RTP -> STUN | TLS | DTLS -> RFC 4571 framing protocol ('32-bit Shim header') -> TCP -> IPv4 | IPv6 -> Lower layers. In (b), 'Without (D) TLS', the stack is: Application protocol -> non-RTP -> STUN | RTP -> RFC 4571 framing protocol ('32-bit Shim header') -> TCP -> IPv4 | IPv6 -> Lower layers. + +Figure II.1 – ICE for TCP – protocol stack (MG bearer interface) + +The framing protocol (according to [b-IETF RFC 4571]) on top of TCP is mandatory. The transport level security protocols are optional. The option of using an UDP tunnel for TCP (section 5.4 of [IETF RFC 6544], "UDP-Tunneled Candidates") is not indicated in Figure II.1. + +## II.2 Bearer establishment + +The STUN procedures (address gathering, connectivity checks, etc.) are executed over TCP bearer connection(s). The MG-side TCP-enabled ITU-T H.248 stream endpoints are controlled according to [b-ITU-T H.248.84] or/and [b-ITU-T H.248.89]. Additional (D)TLS transport level security may require support of [ITU-T H.248.90] or [b-ITU-T H.248.93], dependent on how far the MG is involved in (D)TLS traffic processing. + +## II.3 TCP address candidates + +The UDP-candidate types [IETF RFC 5245], + +``` +candidate-types = "host" / "srflx" / "prflx" / "relay" / token +``` + +are further qualified by an extension type in case of ICE for TCP [IETF RFC 6244]: + +``` +tcp-type = "active" / "passive" / "so" +``` + +which is important concerning the direction of TCP bearer establishment (from MG perspective). Table II.1 summarizes the semantic of the TCP extension types: + +**Table II.1 – Type extensions for TCP-based candidates** + +| Type extension for candidates | Semantic | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| active | An active candidate is one for which the agent will attempt to open an outbound connection but will not receive incoming connection requests. | +| passive | A passive candidate is one for which the agent will receive incoming connection attempts but not attempt a connection. | +| simultaneous-open (S-O) | An S-O candidate is one for which the agent will attempt to open a connection simultaneously with its peer. | + +This leads to the following TCP candidate type variations (Table II.2): + +**Table II.2 – TCP candidate options** + +| Main candidate types | Variations | +|----------------------|--------------------------------------------------------------------------------------------------------------| +| host | {active passive simultaneous-open} host candidate. | +| server reflexive | {active passive simultaneous-open} server reflexive candidate. | +| peer reflexive | {active passive simultaneous-open} peer reflexive candidate. | +| relayed | {active passive simultaneous-open} relayed candidate. | +| NAT-assisted | SDP encoded as "server reflexive", but with higher priority value. | +| UDP-tunneled | The "TCP(IP) packet over UDP" tunnel leads to "ICE for UDP". SDP encoded as "relayed" or "server reflexive". | + +Example SDP grammar (ICE for TCP): + +``` +a=candidate:<> <> TCP <> <> typ host tcptype active +a=candidate:<> <> TCP <> <> typ host tcptype passive +a=candidate:<> <> TCP <> <> typ host tcptype so +a=candidate:<> <> TCP <> <> typ srflx raddr <> rport <> tcptype active +a=candidate:<> <> TCP <> <> typ srflx raddr <> rport <> tcptype passive +a=candidate:<> <> TCP <> <> typ srflx raddr <> rport <> tcptype so +a=candidate:<> <> TCP <> <> typ prflx raddr <> rport <> tcptype active +a=candidate:<> <> TCP <> <> typ prflx raddr <> rport <> tcptype passive +a=candidate:<> <> TCP <> <> typ prflx raddr <> rport <> tcptype so +a=candidate:<> <> TCP <> <> typ relay raddr <> rport <> tcptype active +a=candidate:<> <> TCP <> <> typ relay raddr <> rport <> tcptype passive +a=candidate:<> <> TCP <> <> typ relay raddr <> rport <> tcptype so +``` + +# Appendix III + +## ICE mode support by gateway-embedded ICE agents + +(This appendix does not form an integral part of this Recommendation.) + +## III.1 Background + +The differences between ICE modes have to be extracted from [IETF RFC 5245] due to lack of an explicit description for an "ICE lite" capability set. Complementary ICE documentation provides only a very high level description, such as the following expired IETF draft [b-IETF ice-lite]: + +``` +"A Lite Ice Implementation (LII) behaves much like a normal ICE implementation, with three major differences: +o It only gathers candidate addresses from its own interfaces. +o It cannot be a controlling endpoint. +o It does not generate checks but only responds to periodic checks from other endpoints." +``` + +## III.2 Main differences between ICE-full and ICE-lite + +The following Table III.1 provides an attempt to indicate the differences at a lower level, applicable for ICE implementations by ITU-T H.248 entities. Whenever there is a discrepancy between the information in this appendix and [IETF RFC 5245], the IETF RFC takes precedence. It should be noted that this Table provides some abstraction. Further differences could be identified when looking at a more detailed protocol level. + +**Table III.1 – High-level comparison of ICE modes** + +| | Capability | Full mode | Lite mode | Comment | +|----------|------------------------------------------------|-----------------|-----------------|----------------------------------------------------------------| +| 1 | Gathering Candidates: | | | | +| 1.1 | Host candidates | Yes | Yes
(Note 1) | "no real candidate gathering (because STUN/TURN not required)" | +| 1.2 | Server reflexive candidates | Yes | No | STUN/TURN based | +| 1.3 | Relayed candidates | Yes | No | TURN based | +| 1.4 | Peer reflexive candidates | Yes | No | Possible result of connectivity checks | +| 1.5 | TCP-specific candidates: | | | [IETF RFC 6544] | +| 1.5.1 | NAT-assisted candidates (TCP) | Yes | No | [IETF RFC 6544] | +| 1.5.2 | UDP-tunneled candidates (TCP) | Yes | No | [IETF RFC 6544] | +| 2 | Prioritizing Candidates | | | | +| 2.1 | Priority assignment | Yes | Yes | | +| 2.2 | Robust IP address selection (V4 / V6) | Yes
(Note 2) | No | | +| 3 | SIP: generate SDP Offer (or SDP Answer) | | | | +| 3.1 | Choosing default candidates | Yes | Yes | | +| 3.2 | Insert SDP attribute "a=ice-lite" | N.A. | Yes | | + +**Table III.1 – High-level comparison of ICE modes** + +| | Capability | Full mode | Lite mode | Comment | +|-----------|-------------------------------------------------------------------------|-----------------|----------------|----------------------------------------| +| 4 | SIP: negotiation based SDP O/A | | | | +| 4.1 | eliminating redundant candidates | Yes | No | | +| 4.2 | forming check lists (when Offer received) | Yes | No | | +| 5 | Connectivity checks | | | | +| 5.1 | Initiator role of connectivity checks
i.e., STUN role: "STUN client" | Yes | No | | +| 5.2 | Responder role of connectivity checks
i.e., STUN role: "STUN server" | Yes | Yes | | +| 6 | Completing ICE procedures: | | | | +| 6.1 | Agent role "ICE controlling" | Yes | No
(Note 3) | | +| 6.2 | Agent role "ICE controlled" | Yes | Yes | | +| 6.3 | Role conflict detection & repair | Yes | No | | +| 6.4 | Nominating pairs (regular, aggressive) | Yes | No | | +| 6.5 | Updating state of candidate pairs | Yes | No | | +| 6.6 | Updating state of check lists | Yes | No | | +| 6.7 | Freeing candidates | Yes | Yes | | +| 7 | Media handling: | | | | +| 7.1 | Unconditional start of media sent | Yes | No | [IETF RFC 5245],
section 11.1 | +| 8 | Interoperability / Extensibility: | | | | +| 8.1 | Interoperate with full mode | Yes | Yes | | +| 8.2 | Interoperate with lite mode | Yes | No | Lite-to-lite =
conditional (Note 4) | +| 8.3 | Support of ICE extensions | Yes | No | | +| 9 | Performance: | | | | +| 9.1 | Call setup time (minimal) | Yes
(Note 5) | No | Aggressive vs
regular nomination | +| 10 | Security: | | | | +| 10.1 | Security benefits (unrelated to NAT-T) | Yes | No | see Appendix A in
[IETF RFC 5245] | + +**Table III.1 – High-level comparison of ICE modes** + +| | Capability | Full mode | Lite mode | Comment | +|-----------|-------------------------------------------|-----------|----------------|---------| +| 11 | IP network architecture evolution: | | | | +| 11.1 | Deployment stability | Yes | No
(Note 6) | | + +NOTE 1 – A lite implementation does not gather candidates; it includes only host candidates for any media stream. + +NOTE 2 – See Lite (single IPv4 host address, multiple IPv6 addresses; IPv6 connectivity preferred in general (future safe)); References: [IETF RFC 5245], Appendix A "Lite and Full Implementations" and [b-IETF RFC 6724]. + +NOTE 3 – [IETF RFC 5245], section 5.2: *"For a lite implementation, being the controlling agent means selecting a candidate pair based on the ones in the offer and answer (for IPv4, there is only ever one pair), and then generating an updated offer reflecting that selection, when needed (it is never needed for an IPv4-only host)."* + +NOTE 4 – Lite-to-lite represents a theoretical NAT-less end-to-end path, i.e., there would be no NAT traversal required, hence also no ICE required. + +NOTE 5 – [IETF RFC 5245]: *"A full implementation will reduce call setup times, since ICE's aggressive mode can be used."* + +NOTE 6 – [IETF RFC 5245]: *"it is often the case that a device that finds itself with a public address today will be placed in a network tomorrow where it will be behind a NAT. It is difficult to definitively know, over the lifetime of a device or product, that it will always be used on the public Internet. Full implementation provides assurance that communications will always work."* + +The identified capabilities should cover the major aspects. A precise differentiation between both ICE modes would require a formal specification of the complete ICE protocol logic ("which does not exist, neither in IETF nor in other SDOs"). However, in scope of this Recommendation, it should be sufficient to identify ICE mode differences at the level of ITU-T H.248 protocol and procedural specification. + +NOTE – Following related items are for further studies: + +The remote "ICE agent" could basically provide the same or a different ICE capability set, which raises the question about the principle impact on the MGC or/and MG behaviour? + +# Appendix IV + +## ICE extensions: "Trickle ICE" + +(This appendix does not form an integral part of this Recommendation.) + +## IV.1 Introduction + +Table IV.1 provides a brief summary of trickle ICE. The information is still preliminary due to the status of the underlying ICE specifications in IETF. + +**Table IV.1 – Summary "trickle ICE from perspective of ITU-T H.248 gateways"** + +| | | +|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| References: | See:
– [b-IETF trickle-ice]: basic ICE protocol procedures and SDP extensions;
– [b-IETF trickle-sip]: trickle ICE support via SIP. | +| Motivation: | – The basic issue with vanilla ICE : process of candidate gathering, prioritization and final selection is that it may significantly delay communication establishment (" relatively lengthy session establishment times and degraded user experience "). Such delays negatively impact primarily realtime conversation services.
– Trickle ICE : provides an alternative mode by incremental exchange of candidates early during the call establishment process.
– ICE agent: additional function "candidate harvester". | +| Principal impact on main body of this Recommendation: | – Yes: trickle ICE is not backward compatible to vanilla ICE , hence both ICE agents (and one is residing in the ITU-T H.248 MG) needs firstly to check trickle ICE support or not.
– There are again the two variants of half trickle and full trickle ICE modes. Such asymmetrical options leading to a number of real life combinations between the ITU-T H.248 MG and remote ICE clients (modes of ICE client is either "vanilla", "half trickle" or "full trickle").
– The "trickle ICE" capability declaration and negotiation, as well as fallback process is delegated to the IP signalling plane, i.e.,
a) the SIP-based MGC call control interface (see clause 6.4.2.1), and
b) the ITU-T H.248 gateway control interface (for further studies).
Concrete changes are not yet implemented in the ITU-T H.248 capabilities as defined by this Recommendation. | + +The purpose of this appendix is to illustrate signalling flows with trickle ICE in order to highlight principle impacts on ITU-T H.248 gateway control. The considered use cases should cover the following aspects: + +- comparison of signalling scenarios with trickle ICE only and combined trickle/vanilla ICE modes in order to separate trickle ICE specific information at call control signalling level from the remaining signalling part, which is finally visible at the ITU-T H.248 interface at all; +- check impact of trickle ICE on all existing ITU-T H.248 packages as defined by this Recommendation; +- verify possible impact of trickle ICE on the package-less procedures according to clause 10. + +The discussion of concrete signalling examples is for further studies. + +## IV.2 Impact of trickle ICE on ITU-T H.248.50-defined packages + +For further studies. + +**Table IV.2 – Summary "impact of trickle ICE on ITU-T H.248.50-defined packages"** + +| Package | Comments | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| STUN base package ( stun ) (clause 7.1) | No impact. The address mapping principles as introduced for vanilla ICE should be identical to trickle ICE. | +| STUN information package ( stuni ) (clause 7.5) | No impact because the NAT type related information is orthogonal to ICE procedures. | +| MG STUN client package ( mgstunc ) (clause 7.2) | For further studies. | +| MGC STUN client package ( mgcstunc ) (clause 7.4) | No impact due to MGC-embedded STUN client function, which is not exposed at the ITU-T H.248 interface. | +| STUN consent freshness package ( stun ) (clause 8.3) | No impact due to the assumption that STUN consent freshness procedures will be requested at a "later point in time" of the call phase, i.e., some time after the "end of address gathering" was already announced | +| MG TURN client package ( mgstunc ) (clause 7.3) | No impact. | +| MG act-as STUN server package ( mgastuns ) (clause 8.1) | No impact because the ITU-T H.248-related STUN server assignment is orthogonal to ICE procedures. | +| Originate STUN continuity check package ( ostuncc ) (clause 8.2) | No impact because STUN continuity checks are a follow-up activity, after the ICE related address gathering phase. There might be additional STUN continuity checks requested (by the MGC from the MG) after an ITU-T H.248 stream is already used for application data transfer. | +| MGC-originated STUN request package ( mgcostunr ) (clause 9.1) | No impact because keep alive mechanism is orthogonal to ICE procedures. Dynamic view: any keep alive activities occur after the ICE based address gathering phase. | +| Keep alive request package ( mgastuns ) (clause 9.2) | No impact because keep alive mechanism is orthogonal to ICE procedures. Dynamic view: any keep alive activities occur after the ICE based address gathering phase. | + +## IV.3 Example signalling flows for trickle ICE + +For further studies. + +## IV.4 Summary + +Trickle ICE allows to improve the critical establishment phase which is of key interest of realtime communication services. It is expected that trickle ICE will be subsequently supported and deployed by ICE endpoint implementations. Support of trickle ICE should be revisited by a future release of this Recommendation. + +# Appendix V + +## ICE multihomed and IPv4/IPv6 dual stack fairness + +(This appendix does not form an integral part of this Recommendation.) + +## V.1 Introduction + +ICE clients could reside in IP host entities with multiple IP interfaces, called multihomed IP hosts. This is the default for ITU-T H.248 IP media gateways when used for network interconnections or/and serving a large number of parallel IP bearer connections. [b-IETF ice-dualstack] describes impact and guidelines for such type of ICE clients. + +## V.2 Impact on ITU-T H.248 gateways with ICE support? + +Support of [b-IETF ice-dualstack] results in *algorithmic changes only* within an ICE entity, but there are *no* syntactical ICE protocol extensions. The technology could be basically supported by the "ITU-T H.248.50 toolkit". There would be changes at all places where the ICE "address prioritization" step is touched, see clauses 6.5.3 and 8. + +The MGC or MG could be in charge of the ICE "address prioritization" step, dependent on the underlying network solution related to ICE. When that task is in the MG, then the MG needs to know which algorithm concerning the calculation of priority values is used. This Recommendation does not make any assumptions here. Such information could be e.g., part of an ITU-T H.248 profile specification, also due to the fact that information about the address prioritization algorithm is out of scope of call control signalling (rather a network operator policy). + +# Appendix VI + +## ICE restarts + +(This appendix does not form an integral part of this Recommendation.) + +## VI.1 Introduction + +At any time during an active communication service, either communication party (ICE endpoints) could restart the process of ICE negotiation. Support of ICE restarts is a basic capability of ICE [IETF RFC 5245]. The possible impact on ITU-T H.248.50-enabled ITU-T H.248 gateways is not yet studied, thus, the present Release of this Recommendation does not yet provide guidelines and specifications for ICE restart procedures. + +The purpose of this appendix is to provide a high-level analysis and summary on this particular ICE feature. + +## VI.2 ICE restart procedures + +The starting point is an active call with an active IP bearer connection(s), i.e., there are one or multiple IP transport connections which are all "alive", thus providing a full end-to-end transport connectivity service. ICE restarts might be categorized in three phases: + +Phase 1 – possible events which may trigger an ICE restart: + +- IP user plane: events related to the conditions of existing connectivity; +- IP signalling plane: events related to call control signalling information (such as an incoming SDP offer with ICE information in case of SIP); +- application and/or call control logic: events related to supplementary services, application control logic (e.g., browser-embedded scripts for updating the application runtime environment, application protocols which explicitly updated transport connectivity, or supplementary service which impact bearer plane routes). + +Phase 2 – IP signalling plane: + +- call control level ICE restart procedures could be initiated (such as sections 9.1.1.1, 9.2.1.1 and 9.3.1.1 in [IETF RFC 5245] in case of SIP/SDP). + +Phase 3 – IP user plane: + +- the usual connectivity checks of new, alternative IP transport connections; +- if successful, possibly switchover from existing to new IP transport connection; +- if not, possibly release of the call. + +Above three phases reflect the general, high-level scenario in case of ICE restarts. The call association continues, the application data flows continues as well, and the IP transport connection level could provide an uninterrupted transport service at best or a temporary interruption in the range of a loss of a burst of some IP packets. + +## VI.2 Impact on ITU-T H.248 gateways with ICE support? + +There is an impact on ITU-T H.248 gateways in case of ICE restarts. All three ICE restart phases affect the MGC or MG entity or both. + +Which ones and how the ITU-T H.248 packages of this Recommendations would be impacted is for further studies. + +# Bibliography + +- [b-ITU-T H.248.84] Recommendation ITU-T H.248.84 (2012), *Gateway control protocol: NAT-traversal for peer-to-peer services*. +- [b-ITU-T H.248.89] Recommendation ITU-T H.248.89 (2014), *Gateway control protocol: TCP support packages*. +- [b-ITU-T H.248.93] Recommendation ITU-T H.248.93 (2014), *Gateway control protocol: H.248 packages for control of transport security using DTLS*. +- [b-ITU-T Y.2111] Recommendation ITU-T Y.2111 (2008), *Resource and admission control functions in next generation networks*. +- [b-IETF RFC 4571] IETF RFC 4571 (2006), *Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented Transport*. +<> +- [b-IETF RFC 5245bis] IETF draft-ietf-ice-rfc5245bis (2015), *Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal*. +<> +- [b-IETF RFC 5626] IETF RFC 5626 (2009), *Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)*. +<> +NOTE – Two keep-alive techniques: CRLF keep-alive technique for TCP and SCTP, and STUN keep-alive technique for UDP. +- [b-IETF RFC 6223] IETF RFC 6223 (2011), *Indication of Support for Keep-Alive*. +<> +- [b-IETF RFC 6724] IETF RFC 6724 (2012), *Default Address Selection for Internet Protocol Version 6 (IPv6)*. +<> +- [b-IETF RFC 7362] IETF RFC 7362 (2014), *Latching: Hosted NAT Traversal (HNT) for Media in Real-Time Communication*. +<> +- [b-IETF ice-dualstack] IETF draft-ietf-ice-dualstack-fairness (2016), *ICE Multihomed and IPv4/IPv6 Dual Stack Fairness*. +<> +- [b-IETF ice-lite] IETF draft-rescorla-mmusic-ice-lite (2007), *Implementing Interactive Connectivity Establishment (ICE) in Lite Mode*. +<> +- [b-IETF ice-sip-sdp] IETF draft-ietf-mmusic-ice-sip-sdp (2009), *Using Interactive Connectivity Establishment (ICE) with Session Description Protocol (SDP) offer/answer and Session Initiation Protocol (SIP)*. +<> +- [b-IETF no-op] IETF draft-ietf-avt-rtp-no-op (2007), *A No-Op Payload Format for RTP*. +<> +- [b-IETF rkeep] IETF draft-holmberg-sipcore-rkeep (2014), *Indication of support for reverse keep-alive*. +<> + +- [b-IETF rtcweb-transports] IETF draft-ietf-rtcweb-transports (2016), *Transports for WebRTC*. +<> +- [b-IETF trickle-ice] IETF draft-ietf-ice-trickle (2015), *Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol*. +<> +- [b-IETF trickle-sip] IETF draft-ietf-mmusic-trickle-ice-sip (2015), *A Session Initiation Protocol (SIP) usage for Trickle ICE*. +<> + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.52-200806-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.52-200806-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/H/T-REC-H.248.52-200806-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/H/T-REC-H.248.52-200806-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/H/T-REC-H.248.52-200806-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc7bb1eaa63e825f62a593131a674fe67edc63dd --- /dev/null +++ b/marked/H/T-REC-H.248.52-200806-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:178cb21b9ab648969bcb51114e31343bc8b4596b0ffaedb77da38b56ae47c300 +size 100660 diff --git a/marked/H/T-REC-H.248.52-200806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.248.52-200806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08b6bbbdcd7643020f6bced5db73d8e2dea4b9a7 --- /dev/null +++ b/marked/H/T-REC-H.248.52-200806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfa342ebb96ba7457e8f09db8bdaa907f814460655945a9f25eaab236a1838d7 +size 83054 diff --git a/marked/H/T-REC-H.248.52-200806-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/H/T-REC-H.248.52-200806-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82fe16191b6394f5608a90c31e5500151b03390a --- /dev/null +++ b/marked/H/T-REC-H.248.52-200806-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9707846939e210848b4bfee6977c24d46f57c754db89a6e979a02996a31b091 +size 49108 diff --git a/marked/H/T-REC-H.248.52-200806-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.248.52-200806-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaff5610fa936f70503fbb43e41214d7e97251c5 --- /dev/null +++ b/marked/H/T-REC-H.248.52-200806-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d8917907f2923a456806908ff208d941f0431714cde2b2e344a6628871d218d +size 48059 diff --git a/marked/H/T-REC-H.248.52-200806-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/H/T-REC-H.248.52-200806-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adcb04cdfc7e13d164ee16eb654c21182ad354f0 --- /dev/null +++ b/marked/H/T-REC-H.248.52-200806-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88fd2fb53a3581a1406ee3329bf3cc7cd6cf4d18d83144592666d56d30be8be1 +size 45608 diff --git a/marked/H/T-REC-H.248.52-200806-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.248.52-200806-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9539f1d2160346149b2b5f343441394969ff1d44 --- /dev/null +++ b/marked/H/T-REC-H.248.52-200806-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83627c0fde4a2f7972a0d40ebfdf4e19403add79ff2bcf815e458a42534b415b +size 63229 diff --git a/marked/H/T-REC-H.248.52-200806-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/H/T-REC-H.248.52-200806-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2dc46313fe1886f8ce9f046ee4953cfe3556510 --- /dev/null +++ b/marked/H/T-REC-H.248.52-200806-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed0fc37fa74610d1c4aa9d5de02a740907c0e9ae34f26ed962e3ffacd62a1b7a +size 46401 diff --git a/marked/H/T-REC-H.248.52-200806-I_PDF-E/raw.md b/marked/H/T-REC-H.248.52-200806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..49f3e8fb11d675d180625e561f5ccce75c98fe7e --- /dev/null +++ b/marked/H/T-REC-H.248.52-200806-I_PDF-E/raw.md @@ -0,0 +1,890 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.52** + +(06/2008) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: QoS support packages** + +Recommendation ITU-T H.248.52 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.248.52 + +# Gateway control protocol: QoS support packages + +## Summary + +Recommendation ITU-T H.248.52 provides H.248 packages for different quality of service (QoS) support mechanisms. The QoS class package may be used in various areas with relations to QoS, e.g., media gateway level admission control functions. The Differentiated Services package is specifically designed to support QoS marking for IPv4- or IPv6-based H.248 streams/terminations, but limited to the 6-bit DiffServ field within the IP header. The General IP Header QoS Octet package allows QoS marking and modification of the entire 8-bit field, related to QoS protocol control information elements in IPv4 and IPv6 packet headers. + +Amendment 1 (03/2009), which is integrated in this edition, defines a new version of the *Differentiated Services* package, which clarifies the procedures for copying DSCP values from ingress packets to egress ones. + +###### Source + +Recommendation ITU-T H.248.52 was approved on 13 June 2008 by ITU-T Study Group 16 (2005-2008) under the Recommendation ITU-T A.8 procedure. This edition includes the Amendment approved on 16 March 2009 by ITU-T Study Group 16 (2009-2012) under the Recommendation ITU-T A-8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | | Page | +|-----|---------------------------------------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 1.1 | Typical application of the QoS class package ..... | 1 | +| 1.2 | Typical application of the Differentiated Services and General IP Header
QoS Octet packages..... | 2 | +| 1.3 | Avoidance of interaction between the Differentiated Services and General
IP Header QoS Octet packages..... | 2 | +| 2 | References..... | 2 | +| 3 | Terms and definitions ..... | 3 | +| 3.1 | Terms defined elsewhere ..... | 3 | +| 3.2 | Terms defined in this Recommendation..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | QoS class package ..... | 4 | +| 6.1 | Properties..... | 4 | +| 6.2 | Events ..... | 4 | +| 6.3 | Signals ..... | 5 | +| 6.4 | Statistics..... | 5 | +| 6.5 | Error Codes..... | 5 | +| 6.6 | Procedures ..... | 5 | +| 7 | Differentiated Services package ..... | 6 | +| 7.1 | Properties..... | 7 | +| 7.2 | Events ..... | 7 | +| 7.3 | Signals ..... | 7 | +| 7.4 | Statistics..... | 8 | +| 7.5 | Error Codes..... | 8 | +| 7.6 | Procedures ..... | 8 | +| 8 | General IP Header QoS Octet package..... | 12 | +| 8.1 | Properties..... | 13 | +| 8.2 | Events ..... | 14 | +| 8.3 | Signals ..... | 14 | +| 8.4 | Statistics..... | 14 | +| 8.5 | Error codes..... | 14 | +| 8.6 | Procedures ..... | 14 | +| | Appendix I – QoS class codepoint mapping on Y.1541 QoS classes..... | 15 | +| | Appendix II – Relation of QoS class package with differentiated services package..... | 16 | +| | Appendix III – Relation of QoS class package with H.248 context attribute "priority" ..... | 17 | + +| | | +|--------------------------------------------------------------------------------------------------|----| +| Appendix IV – Some examples for QoS marking with the H.248 differentiated services package ..... | 18 | +| IV.1 Introduction ..... | 18 | +| IV.2 ToS marking ..... | 18 | +| IV.3 DSCP Marking ..... | 18 | +| IV.4 Remarks ..... | 20 | +| Bibliography..... | 21 | + +# Gateway control protocol: QoS support packages + +# 1 Scope + +This Recommendation provides H.248 packages for different quality of service (QoS) support mechanisms. + +The QoS class package (clause 6) defines a single property for signalling a QoS class codepoint. Such a codepoint may be correlated with a set of network performance parameters. Such parameters may be used in the area of transport resource management or admission control. + +The Differentiated Services package (clause 7) defines a property to control the 6-bit differentiated services (DS) field of the IP header, as defined in [IETF RFC 2474]. The media gateway controller (MGC) can set the quality of service (QoS) for egress media flows without having to provision the media gateway (MG) with a default differentiated service code point (DSCP) value. + +Thus both packages have a slightly different scope as described in the clauses below (see also Appendix II). + +The General IP Header QoS Octet package (clause 8) provides an extended capability, in comparison to the Differentiated Services package, in order to address the entire 8-bit field, and enable modification of individual bits. + +## 1.1 Typical application of the QoS class package + +This package is only relevant for ephemeral terminations, i.e., packet-switched bearer technologies. Any packet-based bearer connection traverses a set of packet nodes in the network. Even within an MG, a bearer may traverse a number of queuing points. To set up a bearer, generally resources must be reserved at each transport path/interface and/or MG-internally (see Note 1). The availability check, selection and allocation of resources are related to admission control (AC) functions (see Note 2), e.g., there could be admission control functions in an MG on the level of contexts (CoAC), terminations (TeAC) or even streams (StAC). + +NOTE 1 – This may depend on how the network capacity and/or MG capacity is engineered, e.g., the MG external network interfaces may be "over-provisioned", operated in a "best effort" manner, or strict deterministic resource allocation schemes, etc. Similar resource management models may be applied internally to the MG. + +NOTE 2 – The concept is very similar to the connection admission control (CAC) concept defined for B-ISDN/ATM [b-ITU-T I.371]. + +Any admission control function is motivated by QoS support and determines the admissibility of a new bearer (i.e., H.248 context, termination and/or stream; see Note 3) by checking the availability of various resources. Network performance parameters may be part of such an AC function and thus could be described by this package. + +NOTE 3 – This may depend in particular on the H.248 connection model (e.g., IP-to-IP context), or single/multiple H.248 streams per termination, etc. + +It has to be noted that the area of admission control is just one possible application of the QoS class package. The diversity of potential applications (see Note 4) is much broader due to the definition of the *qos* package property. The particular application should be defined in a profile specification. + +NOTE 4 – Further applications are, e.g., support of path-coupled QoS signalling, or support of pushing/pulling QoS-specific policies, or even support of QoS marking. + +## 1.2 Typical application of the Differentiated Services and General IP Header QoS Octet packages + +"Packet marking" (also known as "QoS marking") is a QoS building block for support of quality of service in packet networks (see clause 8.4 of [ITU-T Y.1291]). This function involves assigning a value to a designated IP header field in IP networks. QoS marking in IP domains is the primary scope of the *ds* and *gih* packages and includes marking of: + +- IPv4 Type-of-Service (ToS) field ([b-IETF RFC 1349]); +- IPv4 Explicit Congestion Notification (ECN) field ([b-IETF RFC 3168]); +- IPv4 ToS together with ECN; +- IPv4 Differentiated Services (DS) field ([IETF RFC 2474]); +- IPv6 Traffic Class field ([b-IETF RFC 2460]); or +- IPv6 Differentiated Services (DS) field ([IETF RFC 2474]). + +The *ds* package is predestined for DS codepoint (DSCP) marking, but is also applicable for non-DS IP domains. + +The function of QoS marking is illustrated by examples in Appendix IV. The *ds* package is furthermore applicable for controlling DS conditioning functions and per-hop behaviour (PHB). + +## 1.3 Avoidance of interaction between the Differentiated Services and General IP Header QoS Octet packages + +The two properties *ds/dscp* and *gih/iqo* overlap at a common 6-bit field in the IP header. Any parallel application of both properties to the same H.248 stream may thus lead to contradictory semantics. It is therefore recommended to use only one property per stream, and not both. Where both will result in a conflict, error code #473 ("*Conflicting property values*") is returned. + +Likewise, parallel application of the *ds/tb* and *the gih/tm* properties to the same H.248 stream may lead to contradictory semantics. It is also recommended to use only one of these two properties per stream, and not both. Where both will result in a conflict, error code #473 "*Conflicting property values*" is returned. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*. + +[ITU-T H.248.15] Recommendation ITU-T H.248.15 (2002), *Gateway control protocol: SDP H.248 package attribute*. + +[ITU-T Y.1291] Recommendation ITU-T Y.1291 (2004), *An architectural framework for support of Quality of Service in packet networks*. + +[IETF RFC 2474] IETF RFC 2474 (1998), *Definition of the Differentiated Services Field (DS field) in the IPv4 and IPv6 Headers*. + +<> + +# **3 Terms and definitions** + +## **3.1 Terms defined elsewhere** + +None. + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following term: + +**3.2.1 QoS class:** QoS refers to a set of (network) performance parameters. Such a set could, for instance, constitute the traffic contract between the subscriber equipment and the network. Examples of such performance parameters include: packet loss ratio, packet transfer delay, and packet delay variation tolerance. The parameters are used to define distinct QoS classes. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|-----------------------------------------------| +| AC | Admission Control | +| ATM | Asynchronous Transfer Mode | +| BCAC | Bearer Connection Admission Control | +| BCP | Bearer Control Protocol | +| B-ISDN | Broadband Integrated Services Digital Network | +| CAC | Connection Admission Control | +| CES | Circuit Emulation Service | +| CoAC | Context Admission Control | +| CoS | Class of Service | +| CU | Currently Unused (DiffServ) | +| DiffServ | Differentiated Services | +| DS | Differentiated Services | +| DSCP | Differentiated Services Code Point | +| ECN | Explicit Congestion Notification | +| ER | Edge Router | +| IP | Internet Protocol | +| IPDV | Internet Protocol packet Delay Variation | +| IPER | Internet Protocol packet Error Ratio | +| IPLR | Internet Protocol packet Loss Ratio | +| IPRR | Internet Protocol packet Reordering Ratio | +| IPTD | Internet Protocol packet Transfer Delay | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MLPP | Multi-Level Precedence and Preemption | +| NGN | Next Generation Network | + +| | | +|------|------------------------------------------| +| PHB | Per-Hop Behaviour | +| QoS | Quality of Service | +| RACF | Resource and Admission Control Functions | +| SDO | Standards Development Organization | +| SDP | Session Description Protocol | +| StAC | Stream Admission Control | +| TeAC | Termination Admission Control | +| TC | Traffic Class (IPv6) | +| ToS | Type of Service | +| VPN | Virtual Private Network | + +# 5 Conventions + +None. + +# 6 QoS class package + +**Package name:** QoS class package +**Package ID:** qos (0x00c7) +**Description:** This package defines a property for signalling QoS class codepoints. +**Version:** 1 +**Extends:** None + +## 6.1 Properties + +### 6.1.1 Class of Service + +**Property name:** Class of Service +**Property ID:** class (0x0001) +**Description:** There is a database of QoS classes provisioned in the MG. A specific QoS class comprises a set of parameter/value pairs. This property corresponds to an index for such a database. +**Type:** Integer +**Possible values:** 0 to 63 +NOTE – [b-ITU-T Y.1541] recommends planning for at least eight classes. The code space for Y.1541 classes is sufficient to accommodate sixty-four class designations. +**Default:** 0 +**Defined in:** Local, Remote +NOTE – Local and remote descriptor level support implies the usage of the SDP H.248 package attribute in text encoding mode, according to [ITU-T H.248.15]. +**Characteristics:** Read/write + +## 6.2 Events + +None. + +## 6.3 Signals + +None. + +## 6.4 Statistics + +None. + +## 6.5 Error Codes + +None. + +In a case where the MGC requests a QoS class that is not supported by the MG, it is recommended that the MG replies with error code #449 "*Unsupported or unknown parameter or property value*". + +This error may occur either due to a) an invalid property value; or b) a valid property value, but the property value is outside of the range of supported QoS classes; or c) a valid QoS class, but associated network performance parameters are not yet provisioned in the MG. + +## 6.6 Procedures + +### 6.6.1 Resource and admission control procedures in NGN architectures + +High-level procedures are defined by some NGN architectures, for instance as part of resource and admission control functions (e.g., the RACF defined by [b-ITU-T Y.2012]). For example, [b-ITU-T Y.2111] defines procedures for reference point *Rw*. + +NOTE – This Recommendation could be applied for a H.248-based *Rw* signalling protocol according to [b-ITU-T Q.3303.2]. + +### 6.6.2 QoS class codepoint mapping on network performance parameters + +The QoS class codepoint is a pointer to a set of network performance parameter/value pairs, which are stored in the MG. The definition of such parameter sets, as well as the configuration of parameter values, is out of scope of this Recommendation. Appendix I describes such a codepoint mapping for the example of QoS classes as defined by [b-ITU-T Y.1541]. + +The indicated network performance parameters may then be used by the MG for the functions as described in the subsequent clauses. + +### 6.6.3 Application of network performance parameters in an MG + +#### 6.6.3.1 Transport resource management + +Network performance parameters may be used by MG resource management as additional information. The resource management could first use the QoS class codepoint for the selection of specific node mechanisms (see, e.g., Table 2 of [b-ITU-T Y.1541]). + +#### 6.6.3.2 Admission control + +The general application of network performance parameters is their usage in the perspective of admission control functions by the MG, such as context admission control (CoAC), termination admission control (TeAC) and/or stream admission control (StAC). + +NOTE – There could be an additional bearer connection admission control (BCAC) in a case where the MG is terminating a bearer control protocol (BCP, e.g., [b-ITU-T Q.1970]). + +The admission control function(s) determines the admissibility of a new context/termination/stream into the MG (and correspondent bearer connection in the network) by the availability of various MG resources. + +The nodal (and network) efficiency thus depends on how well the CoAC/TeAC/StAC function models the traffic and queuing behaviour of the underlying congestion point(s). CoAC/TeAC/StAC + +functions could apply deterministic or statistical multiplexing models, depending on the specific MG resource component types behind a context and its terminations. An efficient admission control should try to achieve as much statistical gain as possible without risking a congestion condition that would impair QoS. + +The (statistical) gain, or economy of scale effect, particularly in the case of ephemeral terminations (such as IP) is generally a function of: + +- buffer size; +- traffic characteristics (e.g., explicit traffic parameters according to [b-ITU-T H.248.53] *tman* properties or SDP "b=" line, or implicit traffic parameters derived from SDP "m=" and "a=" lines); and +- QoS objectives (as indicated by H.248.52 QoS class codepoints). + +Admission control functions, which take into account QoS objectives, should consider one or more network performance parameters. + +Algorithms for admission control functions (such as CoAC, TeAC or StAC) are typically not specified by SDOs, and are thus out of scope of this Recommendation. + +#### 6.6.3.3 Rejection of resource requests/modifications + +Admission control (AC) functions may be triggered by ADD requests or MODIFY requests which signal the *qos/class* property. The result of the AC is either acceptance or rejection of the request. Acceptance relates to a positive reply command, whereas rejection would be expressed by an appropriated H.248 error code (e.g., #510 "*Insufficient resources*" or #526 "*Insufficient bandwidth*"). + +A request rejection need not be based solely on QoS objectives. Rejection may be based on the signalled traffic characteristics. For instance, a stream admission control (StAC) function could reject the addition of a further stream to a termination in case of an unsupported media parameter (e.g., codec type). + +### 6.6.4 IP terminations using both the *ds* and *qos* packages + +The properties of both packages could be applied together (see also Appendix II) for the same H.248 IP stream or termination. + +For example, the *qos/class* property may be part of an admission control function (see clause 6.6.3) deciding whether a Context/Termination/Stream is accepted. The *ds/dscp* property is then used for the QoS marking of any IP packet flows that were admitted. + +Particular use cases are out of scope of this Recommendation because such a particular network scenario is mainly related to the specific DS PHB, the specific role of the MG in the DS domain (see Appendix IV), and the specific semantic of the QoS class property. + +# 7 Differentiated Services package + +**Package name:** Differentiated Services package + +**Package ID:** ds (0x008b) + +**Description:** This package enables the setting of the differentiated services (DS) field in the header of IP packets. + +**Version:** 2 + +**Extends:** None + +## 7.1 Properties + +### 7.1.1 Differentiated Services Code Point + +**Property name:** Differentiated Services Code Point +**Property ID:** dscp (0x0001) +**Description:** This property corresponds to the 6-bit differentiated services code point field of the IP header, as defined in [IETF RFC 2474]. +**Type:** Octet String +**Possible values:** The value represents any 8-bit value encoded as an octet string of two hexadecimal digits. Only the 6 most significant bits are significant (e.g., in the following binary representation the xx are neglected 0000 00xx), implying a range of 64 DSCP values. See clause 7.6.3 for encoding examples. +**Default:** Provisioned +**Defined in:** Local Control +**Characteristics:** Read/Write + +### 7.1.2 Tagging Behaviour + +**Property Name:** Tagging Behaviour +**Property ID:** tb (0x0002) +**Description:** This property controls whether the MG sets a specific DSCP value on egress packets, or copies the DSCP of the ingress packet to the egress one. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "MARK" (0x0000) +Mark the packet with the DSCP value given by the *ds/dscp* property +"COPY" (0x0001) +Copy the DSCP of the ingress packet to the egress one +NOTE – Applying a specific DSCP value (the "MARK" value), is beneficial for use cases (IV.2), (IV.3.1) and (IV.3.2), but may not be required by use cases (IV.3.3) and (IV.3.4). To generalize, setting a specific DSCP value is most applicable for IP-to-IP MGs in "Back-to-Back IP Host (B2BIH)" mode of operation, because this implies a full termination of the IP stack. Copying the DSCP of the ingress packet to the egress (the "COPY" value) can be applicable for IP-to-IP MGs in "transport protocol agnostic", "IP forwarding" or "IP router" modes of operation. +**Default:** "MARK"; unless provisioned otherwise +**Defined in:** Local Control +**Characteristics:** Read/Write + +## 7.2 Events + +None. + +## 7.3 Signals + +None. + +## 7.4 Statistics + +None. + +## 7.5 Error Codes + +None. + +## 7.6 Procedures + +### 7.6.1 General + +#### 7.6.1.1 Setting a specific DSCP value + +The MGC may apply different DSCP values to the IP packets of different media flows. This can be used, for example, to apply different service levels to different types of streams (audio, video and data) or to differentiate between the service levels given to different subscribers based on their pre-negotiated terms. Similarly, DSCP values may be set according to service-agreement between operators. + +When the value of the *ds/tb* property is "MARK" (the default), the MG uses the *ds/dscp* property as the DSCP value of packets *leaving* the termination. The value of *ds/dscp* is also used to derive an internal PHB that the MF applies to the packets before they are sent. Note that the ingress media flow is not checked against the value of *ds/dscp* – the property affects the egress media flow only. + +If the *ds/dscp* property is not set by the MGC, the MG shall use a provisioned default value. The default value may be unique for the whole MG or be dependent on pre-defined criteria such as the egress interface or the media type. + +#### 7.6.1.2 Copying DSCP values from the ingress to the egress + +In certain scenarios, every egress packet can be readily associated with a single, specific ingress packet. When operating under such a scenario, the MGC may wish to use the DSCP value of the incoming packet for that of the outgoing one. + +To copy the DSCP values of the ingress packets to packets leaving an H.248 stream, the MGC sets the value of the *ds/tb* property to "COPY" (the value assigned to the *ds/dscp* property is then ignored). The MG should, as far as possible, apply the same PHB as if a DSCP value identical to that of the ingress packet had been set by explicit use of the *ds/dscp* property. + +Figure 1 provides a graphical representation of this behaviour. Note that the figure presents the simplest case of a context containing only two terminations; however the behaviour can be applied to any number of terminations in a context: + +![Diagram illustrating the copying of DSCP values from ingress to egress side within an IP-to-IP H.248 Context. A packet arrives on Ta (S1) with DSCP X. The DSCP is copied from ingress to egress. A corresponding packet is sent from Tb (S1) with DSCP X. The Tb(S1) LocalControl property is set to ds/tb = COPY and ds/dscp = ??.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +The diagram shows an 'IP-to-IP H.248 Context' containing two nodes, 'Ta (S1)' and 'Tb (S1)', connected by an 'Interworking Function'. A packet arrives at 'Ta (S1)' with DSCP X. A blue curved arrow indicates the DSCP value is copied from the ingress side to the egress side. A corresponding packet is sent from 'Tb (S1)' with DSCP X. Below the context, a box for 'Tb(S1): LocalControl:' shows 'ds/tb = COPY' and 'ds/dscp = ??'. The text 'DSCP copied from ingress to egress' is written in blue above the context box. + +Diagram illustrating the copying of DSCP values from ingress to egress side within an IP-to-IP H.248 Context. A packet arrives on Ta (S1) with DSCP X. The DSCP is copied from ingress to egress. A corresponding packet is sent from Tb (S1) with DSCP X. The Tb(S1) LocalControl property is set to ds/tb = COPY and ds/dscp = ??. + +**Figure 1 – Copying DSCP values from ingress to egress side** + +If the egress packet cannot be associated with an ingress packet (e.g., an internally generated announcement), the value of the *ds/tm* property is irrelevant. The DSCP value shall be derived from the *ds/dscp* property, as if *ds/tm* was set to "MARK". + +#### 7.6.1.3 Backward compatibility with version 1 + +Version 1 of this package did not support the Tagging Behaviour property; however it did allow a similar default behaviour. That version used the following definition for the default value of the *ds/dscp* property: + +***Default: Provisioned, or copy the value received in the ingress packet*** + +This sub-clause deals with how a MG may provide a similar default behaviour while maintaining backward compatibility with a MGC that only supports version 1 of the package. + +- Apply, by default, a specific DSCP value. + +This behaviour can be achieved by provisioning the default value of *ds/tb* to "MARK" and the default value of *ds/dscp* to the required value. + +- Copy, by default, the value received in the ingress packet + +Simply provisioning the default value of *ds/tb* to "COPY" will break interoperability with any version 1 MGC; as such a MGC will not be able to set any specific DSCP value. A more complicated default behaviour is necessary: The default value of *ds/tb* is set to "COPY" if the MGC does not specify a value for the *ds/dscp* property; and to "MARK" otherwise. + +NOTE – Version 1 of the package did not provide any means to encode, in an AuditValue reply, a *ds/dscp* value that indicates that DSCP is copied from ingress packets to egress ones. MGs implementing that version of the package had to rely on some pre-agreement with the MGC about how such behaviour is reported in AuditValue replies. Interoperability with version 1 of the package may therefore be further complicated by the need to support such existing pre-agreements. + +### 7.6.2 Specifics with regard to IP versions and ToS/DS octets + +#### 7.6.2.1 Overview + +The *ds/dscp* property is used to modify bits of an octet in the IP header. This operation of "packet marking" relates to either the IPv4 ToS octet, the IPv4 DS octet, the IPv6 TC octet or the IPv6 DS octet (see Figure 2). + +![Figure 2: Specifics with regard to IP versions and ToS/DS octets. The diagram shows five octet structures: H.248 dscp Property, IPv4 ToS Octet, IPv4 DS Octet, IPv6 TC Octet, and IPv6 DS Octet. Each octet is shown as a row of 8 bits (0-7). The H.248 dscp Property has bits 0-5 as significant (yellow) and 6-7 as ignored (blue). The IPv4 ToS Octet has bits 0-2 as 3-bit precedence (blue), 3-6 as 4-bit Type of Service (ToS) (yellow), and 7 as unused (blue). The IPv4 DS Octet has bits 0-5 as 6-bit DSCP (yellow) and 6-7 as unused (2-bit CU) (blue). The IPv6 TC Octet has all 8 bits as 8-bit Traffic Class (yellow). The IPv6 DS Octet has bits 0-5 as 6-bit DSCP (yellow) and 6-7 as unused (2-bit CU) (blue).](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 2: Specifics with regard to IP versions and ToS/DS octets. The diagram shows five octet structures: H.248 dscp Property, IPv4 ToS Octet, IPv4 DS Octet, IPv6 TC Octet, and IPv6 DS Octet. Each octet is shown as a row of 8 bits (0-7). The H.248 dscp Property has bits 0-5 as significant (yellow) and 6-7 as ignored (blue). The IPv4 ToS Octet has bits 0-2 as 3-bit precedence (blue), 3-6 as 4-bit Type of Service (ToS) (yellow), and 7 as unused (blue). The IPv4 DS Octet has bits 0-5 as 6-bit DSCP (yellow) and 6-7 as unused (2-bit CU) (blue). The IPv6 TC Octet has all 8 bits as 8-bit Traffic Class (yellow). The IPv6 DS Octet has bits 0-5 as 6-bit DSCP (yellow) and 6-7 as unused (2-bit CU) (blue). + +NOTE – The decimal values 0 to 7 are used for numbering the bit positions. The number is not related to the weight of the bit below. The MSB/LSB order is defined by IETF RFCs for the IP header elements. + +**Figure 2 – Specifics with regard to IP versions and ToS/DS octets** + +It has to be noted that, for an H.248 IP termination, the H.248 MG is fundamentally: + +- Aware of the IP version (due to the SDP "c=" line); but +- Respectively agnostic concerning ToS versus DS type octet (in case of IPv4) or TC versus DS type octet (in case of IPv6). + +The MG must therefore map the significant *ds/dscp* property bits to the correct bit positions on the corresponding bits of the IP header. See clause 7.6.3 for encoding examples. + +#### 7.6.2.2 IPv4 type of service octet + +The first three bits of the six significant bits of the *ds/dscp* property are mapped on the 3-bit precedence field. The precedence field is generally unused, i.e., does not affect packet forwarding + +processes. The DiffServ header definition rules provide further background about the potential use of this field (see clause 4.2 of [IETF RFC 2474]). + +The next three bits of the six significant bits of the *ds/dscp* property are mapped on the first three bits of the 4-bit ToS field. The corresponding limitation is rather small in practice due to the assigned ToS values (see [www.iana.org/assignments/ip-parameters](http://www.iana.org/assignments/ip-parameters)). + +There are six assigned ToS values by IANA and the *dscp* property mapping would allow the support of five ToS classes (NOTE), which is typically enough in an IPv4 ToS aware environment. + +NOTE – It is impossible to differentiate between the "Default" and "Minimize Monetary Cost" TOS classes using the properties of the *ds* package. + +#### 7.6.2.3 IPv4 differentiated services octet + +The six significant bits of the *ds/dscp* property are mapped on the 6-bit DSCP. The bits of the 2-bit CU field are not modified. + +#### 7.6.2.4 IPv6 traffic class octet + +The six significant bits of the *ds/dscp* property are mapped on the first six bits of the 8-bit traffic class. The remaining two bits of the 8-bit traffic class field are not modified. + +#### 7.6.2.5 IPv6 differentiated services octet + +The six significant bits of the *ds/dscp* property are mapped on the 6-bit DSCP. The bits of the 2-bit CU field are not modified. + +#### 7.6.2.6 Others + +The historical definitions for the IPv4 TOS octet are summarized in clause 22 of [b-IETF RFC 3168]. That RFC also introduces the ECN semantic. The ECN field cannot be controlled by this version of the *ds* package. See also clause 8. + +### 7.6.3 Encoding of ds/dscp property – Examples + +#### 7.6.3.1 Text encoding + +The 8-bit binary value of the *ds/dscp* property represents a single octet, which must be encoded using two hexadecimal digits (see clause 12.1.2 of [ITU-T H.248.1]) according to clause B.3 of [ITU-T H.248.1]. + +Example: + +1) The DSCP value to be encoded shall be the hexadecimal 2E (binary 101110). + +2) IP header octet, bit representation: 1011 10xx. + +NOTE – The MSB-to-LSB order in this example is from left to right (see [IETF RFC 2474]) according to bitfield definitions for IP header elements. + +3) Hexadecimal encoding of this octet bit pattern: There are four possibilities due to the two "don't care" bits: + +- a) 1D (for binary 1011 1000). +- b) 9D (for binary 1011 1001). +- c) 5D (for binary 1011 1010). +- d) DD (for binary 1011 1011). + +All four hexadecimal values are equivalent, and lead to the same DSCP value being applied to the packets (see also Figure 2). + +#### 7.6.3.2 Binary encoding + +No example. + +### 7.6.4 Usage guidelines for DiffServ service classes + +Values for the *ds/dscp* property may be derived by the MGC either directly from call/session/QoS control signalling protocols, or based on configuration guidelines. The DiffServ codepoint is defined in a hierarchical manner, divided in multiple codepoint spaces (see [IETF RFC 2474] and IANA concerning codepoint pools). + +#### 7.6.4.1 Call/session/QoS-controlled DSCP codepoints + +The MGC may directly forward the DSCP values to the MG, or may translate them based on a local policy. + +#### 7.6.4.2 Configuration guidelines for DiffServ service classes + +In some cases [b-IETF RFC 4594] may be used as a configuration framework, – e.g., MG as ToS pre-marker (see clause IV.2) or MG as DS pre-marker (see clause IV.3.1). + +##### 7.6.4.2.1 General + +Of particular interest may be the: + +- telephony service class (see clause 4.1 of [b-IETF RFC 4594]); +- multimedia conferencing service class (see clause 4.3 of [b-IETF RFC 4594]); +- real-time interactive service class (see clause 4.4 of [b-IETF RFC 4594]); or +- multimedia streaming service class (see clause 4.5 of [b-IETF RFC 4594]). + +##### 7.6.4.2.2 Voice-only environment + +There may be network deployments with voice-only traffic. The MG then serves only the telephony service class, which from the IP network perspective according to [b-IETF RFC 4594] is usually comprised of: + +- voice over IP (G.711, G.729 and other codecs); +- voiceband data over IP (fax/modem, data/modem, text/modem) in: + - pass-through mode, i.e., V.152 VBD over IP; or + - packet relay mode like T.38 fax over IP, V.150.1 modem over IP or V.151 text over IP; +- circuit emulation over IP (e.g., 1 x 64 kbit/s clearmode) see [b-IETF RFC 4040], virtual wire, etc.; +- IP virtual private network (VPN) service that specifies single-rate, mean network delay that is slightly longer than network propagation delay, very low jitter and very low packet loss. + +DSCP marking could distinguish between circuit emulation services (CES) and non-CES services, and/or VPN and non-VPN services. + +# 8 General IP Header QoS Octet package + +**Package name:** General IP Header QoS Octet package + +**Package ID:** gih (0x00e1) + +**Description:** This package enables the setting and modification of the "QoS octet" field in the header of IP version 4 and version 6 packets. Major differences from the *ds* package are: + +- a) coverage of the entire 8-bit space instead of just 6 bits; and + +b) modification of individual bits instead of a full setting (tagging or marking). + +**Version:** 1 +**Extends:** None + +## 8.1 Properties + +### 8.1.1 IP QoS Octet + +**Property name:** IP QoS Octet + +**Property ID:** iqo (0x0001) + +**Description:** This property corresponds in general to an 8-bit field in the IP header (IPv4 ToS octet, IPv4 DS octet, IPv6 TC octet or the IPv6 DS octet), which may be related to, e.g., the 6-bit differentiated services field of the IP header, as defined in [IETF RFC 2474]. + +**Type:** Integer + +**Possible values:** 0-255 + +**Default:** None. + +**Defined in:** LocalControl, Remote + +NOTE 1 – Remote descriptor level support implies the usage of the SDP H.248 package attribute in text encoding mode, according to [ITU-T H.248.15]. + +NOTE 2 – The property can be defined in the LocalControl Descriptor, as this maintains parity with (and eases migration from) the Differentiated-Services package. It can also be defined in the Remote Descriptor as it relates to packets leaving the MG. However these two placement options represent *one* instance of the property (i.e. the property cannot have different values in the different descriptors). Any command that assigns different values to the two placement options shall be rejected by the MG using error code #473 ("*Conflicting Property Values*"). + +**Characteristics:** Read/write + +### 8.1.2 Tagging mask + +**Property name:** Tagging mask + +**Property ID:** tm (0x0002) + +**Description:** This property defines an 8-bit mask, which is applied together with the *gih/iqo* property on the IP header. A bit in that IP header octet (IPv4 ToS octet, IPv4 DS octet, IPv6 TC octet or the IPv6 DS octet) is modified (according to the *iqo* value) when the corresponding *tm* bit is "1", and not modified when the corresponding *tm* bit is "0". + +**Type:** Integer + +**Possible values:** 0-255 + +NOTE 1 – Specifying both *ds/tb* and *gih/tm* on the same stream is not recommended and can cause conflicting semantics. The following table lists the possible combinations of *ds/tb* and *gih/tm* values that do *not* lead to a conflict: + +| ds/tb | gih/tm | +|--------------|------------------------| +| MARK | 0xFC, 0xFD, 0xFE, 0xFF | +| COPY | 0x00, 0x01, 0x02, 0x03 | + +**Default:** None. + +**Defined in:** LocalControl, Remote + +NOTE 2 – See notes in clause 8.1.1 regarding the use of the different descriptors. + +**Characteristics:** Read/write + +## **8.2 Events** + +None. + +## **8.3 Signals** + +None. + +## **8.4 Statistics** + +None. + +## **8.5 Error codes** + +None. + +## **8.6 Procedures** + +### **8.6.1 General** + +See clause 7.6.1 in *ds* version 2 package. + +### **8.6.2 Specifics with regard to IP versions and ToS/DS octets** + +See clause 7.6.2 in *ds* version 2 package. The mapping of the *ds/dscp* property to the IP header octet is now extended from six to eight bits. + +Furthermore, there is an additional semantic defined. + +#### **8.6.2.1 IP header with ECN usage** + +The historical definition for the IPv4 ToS octet is summarized in clause 22 of [b-IETF RFC 3168]. That RFC also introduces the ECN semantic. The ECN field can be controlled by this package. + +### **8.6.3 Usage guidelines for DiffServ service classes** + +See clause 7.6.3 in *ds* version 2 package. + +### **8.6.4 Modification of individual bits: Applications with the tagging mask** + +Tagging masks may be useful when the codepoint space is organized in a hierarchical manner, i.e., when only sub-fields are modified. Another application is the DiffServ re-marking function (see clause IV.3.3) for a particular codepoint pool. + +# Appendix I + +## QoS class codepoint mapping on Y.1541 QoS classes + +(This appendix does not form an integral part of this Recommendation) + +Below are the network QoS classes summarized as defined by [b-ITU-T Y.1541]. See clause 5.3 of [b-ITU-T Y.1541] for details. + +**Table I.1 – IP network QoS class definitions and network performance objectives** + +| Network performance parameter | Nature of network performance objective | QoS classes | | | | | | +|-------------------------------|--------------------------------------------------------------------------|--------------------|--------------------|--------------------|--------------------|--------------------|---------------------| +| | | Class 0 | Class 1 | Class 2 | Class 3 | Class 4 | Class 5 unspecified | +| IPTD | Upper bound on the mean IPTD | 100 ms | 400 ms | 100 ms | 400 ms | 1 s | U | +| IPDV | Upper bound on the $1 - 10^{-3}$ quantile of IPTD minus the minimum IPTD | 50 ms | 50 ms | U | U | U | U | +| IPLR | Upper bound on the packet loss probability | $1 \times 10^{-3}$ | $1 \times 10^{-3}$ | $1 \times 10^{-3}$ | $1 \times 10^{-3}$ | $1 \times 10^{-3}$ | U | +| IPER | Upper bound | $1 \times 10^{-4}$ | | | | | U | + +NOTE – See Tables 1 and 3 in [b-ITU-T Y.1541]. + +**Table I.2 – Provisional IP network QoS class definitions and network performance objectives** + +| Network performance parameter | Nature of network performance objective | QoS classes | | +|-------------------------------|--------------------------------------------------------------------------|--------------------|---------| +| | | Class 6 | Class 7 | +| IPTD | Upper bound on the mean IPTD | 100 ms | 400 ms | +| IPDV | Upper bound on the $1 - 10^{-5}$ quantile of IPTD minus the minimum IPTD | 50 ms | | +| IPLR | Upper bound on the packet loss ratio | $1 \times 10^{-5}$ | | +| IPER | Upper bound | $1 \times 10^{-6}$ | | +| IPRR | Upper bound | $1 \times 10^{-6}$ | | + +NOTE – See Tables 1 and 3 in [b-ITU-T Y.1541]. + +The *class* property relates to the Y.1541 QoS class, i.e., a property value equal to *i* corresponds to class *i* (e.g., value range 0 to 7 in case of this appendix). + +# Appendix II + +## Relation of QoS class package with differentiated services package + +(This appendix does not form an integral part of this Recommendation) + +The differentiated services package (see clause 7) is designed for H.248 terminations following the QoS architecture as defined by [IETF RFC 2474]. The *ds/dscp* property is related to the DiffServ field in the IPv4 and IPv6 headers, but is also applicable for the IPv4 service-marking model using the type of service (ToS; see [b-IETF RFC 1349]) attribute. + +The *ds/dscp* property could be used for: + +- QoS marking (e.g., "DiffServ marker" or "DiffServ pre-marker"; see also Appendix IV), i.e., setting or modifying the corresponding information field in the IP header. The H.248 MG could provide the role of a pre-marker (see [b-IETF RFC 2475]); or/and +- indication of conditioning functions and per-hop behaviours (PHBs). The H.248 MG could provide the role of a DiffServ router (e.g., first-hop, interior or egress router role). + +The *ds/dscp* property is a codepoint for (DiffServ) "class of service" selection ("*dscp* is a class selector") in both cases, thus similar to the *class* property of the QoS class package. Although some may argue that both properties are synonymous, in practice, they have subtle distinctions: + +- Operative concept: +(DiffServ) CoS implies that services can be categorized into separate classes, which can, in turn, be handled individually. The function behind the *ds/dscp* property is therefore performed on each IP packet per H.248 termination ("active bearer connection"). Whereas the QoS class concept is more related to traffic contracts and transfer capabilities, which result typically in admission control and resource management functions, which are performed during bearer connection establishment phase ("ADD request for an ephemeral termination"). +- Combined mode: +There are use cases with DS codepoint indications together with QoS class codepoint signalling. For instance, the H.248 MG is a DS domain external node (e.g., peering a DiffServ edge router, (DS ER)), but provides the DiffServ pre-marker function, and the IP domain between the DS ER and MG supports QoS classes according to [b-ITU-T Y.1541]. Another example is indicated in Table VI.1 of [b-ITU-T Y.1541] (association of Y.1541 QoS classes with Y.1221 transfer capabilities and differentiated services PHBs). Such applications require the support of the properties of both packages. + +# Appendix III + +## Relation of QoS class package with H.248 context attribute "priority" + +(This appendix does not form an integral part of this Recommendation) + +The H.248 context attribute *priority* (see clause 6.1.1 of [ITU-T H.248.1]) shall not be *re-used* as a codepoint for QoS class signalling, and it therefore does not replace the functionality of the QoS class package. + +# Appendix IV + +## Some examples for QoS marking with the H.248 differentiated services package + +(This appendix does not form an integral part of this Recommendation) + +## IV.1 Introduction + +This appendix illustrates some examples for QoS marking in DS and non-DS networks. The H.248 MG acts in different roles in the various examples. + +## IV.2 ToS marking + +An IPv4 router should comply with [b-IETF RFC 1812], which implies a ToS-dependent IP forwarding process (see clause 5.3.2 of [b-IETF RFC 1812]). Figure IV.1 shows an IPv4 network with ToS-aware IP routers. The H.248 MG acts as a "ToS pre-marker" in the example. The IP next-hop is then typically a ToS-aware IP edge router. + +![Diagram illustrating the H.248 MG as a 'ToS pre-marker' in an IPv4 network.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +The diagram shows a Media Gateway Controller (MGC) connected to an H.248 IP Termination within a Media Gateway (MG). The MGC sends H.248 signaling to the termination. The H.248 IP Termination is connected to a ToS-aware Edge Router, which is part of a ToS Domain. The ToS-aware Edge Router is connected to two ToS-aware Core Routers, also within the ToS Domain. The ToS-aware Edge Router is also connected to an IPv4 network. The H.248 IP Termination sends QoS Marking to the ToS-aware Edge Router. A legend indicates that the H.248 MG acts as a "ToS Pre-Marker". + +Diagram illustrating the H.248 MG as a 'ToS pre-marker' in an IPv4 network. + +Figure IV.1 – H.248 MG as "ToS pre-marker" + +Differentiated services are not used in this example. + +## IV.3 DSCP Marking + +An H.248 MG with IP terminations could participate in various roles in DiffServ networks. Some possible examples are illustrated. This list is not exhaustive. + +### IV.3.1 H.248 MG as "DS pre-marker" + +The H.248 MG could act as "DS pre-marker" for a subsequent DS edge router (DS ER), see Figure IV.2. The DS ER bounds the DS domain, thus also called a DS boundary node (see [b-IETF RFC 2475]). + +![Diagram of H.248 MG as 'DS Pre-Marker'](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +The diagram illustrates the H.248 MG acting as a "DS Pre-Marker". At the top left, a dashed box contains the text "H.248 MG as 'DS Pre-Marker'". Below it, a cloud labeled "Circuit-switched network" is connected to a "Media Gateway (MG)" via a line labeled "H.248 physical Termination". The MG has a component labeled "H.248 IP Termination". Above the MG, a "Media Gateway Controller (MGC)" is connected via a red line labeled "H.248". To the right of the MG, an "IP network" cloud is connected, with an arrow labeled "QoS Marking" pointing from the MG's IP termination into it. Further right, a "DiffServ Edge Router (DSER)" is connected to the IP network and to a "DS Domain" cloud. A dashed line connects the DSER to the DS Domain cloud. + +Diagram of H.248 MG as 'DS Pre-Marker' + +**Figure IV.2 – H.248 MG as "DS pre-marker"** + +The function of packet "pre-mark" is defined as "to set the DS codepoint of a packet prior to entry into a downstream DS domain" ([b-IETF RFC 2475]). The H.248 MG is located prior to the DS domain. + +### IV.3.2 H.248 MG as "DS boundary node" + +An IP edge router function may be embedded in the same physical entity as the H.248 MG function. Figure IV.3 illustrates such an example with an embedded DS ER. The H.248 MG acts as a "DS boundary node". + +![Diagram of H.248 MG as 'DS boundary node'](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +The diagram illustrates the H.248 MG acting as a "DS boundary node". At the top left, a dashed box contains the text "H.248 MG as 'DS Edge Router (DSER)' [= DS Boundary Node]". Below it, a cloud labeled "Circuit-switched network" is connected to a "Media Gateway (MG)" via a line labeled "H.248 physical Termination". The MG has a component labeled "H.248 IP Termination". Above the MG, a "Media Gateway Controller (MGC)" is connected via a red line labeled "H.248". To the right of the MG, a "DS Domain" cloud is connected directly via a dashed line from the MG's IP termination, bypassing an intermediate IP network cloud. + +Diagram of H.248 MG as 'DS boundary node' + +**Figure IV.3 – H.248 MG as "DS boundary node"** + +The specific boundary node role in this example is the "DS ingress node" ([b-IETF RFC 2475]: "a DS boundary node in its role in handling traffic as it enters a DS domain"). + +### IV.3.3 H.248 MG between two DS domains + +An H.248 IP-to-IP MG may be located between two DS domains. Figure IV.4 shows an example of a DS region (see [b-IETF RFC 2475]), which covers two DS domains "A" and "B". Both DS domains may use different DSCP value ranges. The MG could then for instance provide (MGC-controlled) DSCP value translation. + +![Figure IV.4: H.248 MG as 'DSCP translator' between two DS domains with different DSCP usage. The diagram shows a 'DS Region' containing 'DS Domain A' and 'DS Domain B'. 'DS Domain A' is connected to a 'DS Boundary Node', which is connected to an 'IP network'. This 'IP network' has 'QoS Marking (egress flow)' and 'Ingress flow' labels. The 'IP network' is connected to a 'Media Gateway (MG)' which has 'H.248 IP Terminations'. The 'MG' is connected to another 'IP network' with 'Ingress flow' and 'QoS Marking (egress flow)' labels. This second 'IP network' is connected to a 'DS Boundary Node', which is connected to 'DS Domain B'. A 'Media Gateway Controller (MGC)' is connected to the 'MG' via an 'H.248' line. A dashed box at the top left contains the text 'H.248 MG between two DS Domains'.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +Figure IV.4: H.248 MG as 'DSCP translator' between two DS domains with different DSCP usage. The diagram shows a 'DS Region' containing 'DS Domain A' and 'DS Domain B'. 'DS Domain A' is connected to a 'DS Boundary Node', which is connected to an 'IP network'. This 'IP network' has 'QoS Marking (egress flow)' and 'Ingress flow' labels. The 'IP network' is connected to a 'Media Gateway (MG)' which has 'H.248 IP Terminations'. The 'MG' is connected to another 'IP network' with 'Ingress flow' and 'QoS Marking (egress flow)' labels. This second 'IP network' is connected to a 'DS Boundary Node', which is connected to 'DS Domain B'. A 'Media Gateway Controller (MGC)' is connected to the 'MG' via an 'H.248' line. A dashed box at the top left contains the text 'H.248 MG between two DS Domains'. + +**Figure IV.4 – H.248 MG as "DSCP translator" between two DS domains with different DSCP usage** + +Such a function is also known as packet "re-mark" ([IETF RFC 2475]: "to change the DS codepoint of a packet, usually performed by a marker in accordance with a [traffic conditioning agreement] TCA"). + +### IV.3.4 H.248 MG as "DS Interior Node" + +A very common example is the location of an H.248 IP-to-IP MG within a single DS domain. The MG may then act as DS interior node, see Figure IV.5. The per-hop behaviour (PHB) of the DS interior node is then influenced by the MGC via *ds/dscp* property settings. + +![Figure IV.5: H.248 MG providing 'DS PHB'. The diagram shows a 'DS Domain' containing a 'DS Boundary Node', a 'DS Interior Node', a 'Media Gateway (MG)' with 'H.248 IP Terminations', another 'DS Interior Node', and a 'DS Boundary Node'. The 'MG' is connected to the 'DS Interior Node' on its left and the 'DS Interior Node' on its right. A 'Media Gateway Controller (MGC)' is connected to the 'MG' via an 'H.248' line. A dashed box at the top left contains the text 'H.248 MG as DS Interior Node'.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +Figure IV.5: H.248 MG providing 'DS PHB'. The diagram shows a 'DS Domain' containing a 'DS Boundary Node', a 'DS Interior Node', a 'Media Gateway (MG)' with 'H.248 IP Terminations', another 'DS Interior Node', and a 'DS Boundary Node'. The 'MG' is connected to the 'DS Interior Node' on its left and the 'DS Interior Node' on its right. A 'Media Gateway Controller (MGC)' is connected to the 'MG' via an 'H.248' line. A dashed box at the top left contains the text 'H.248 MG as DS Interior Node'. + +**Figure IV.5 – H.248 MG providing "DS PHB"** + +## IV.4 Remarks + +A comprehensive description of all relevant network details is beyond the scope of this Recommendation. Further information on network details should be sought from the corresponding standardization documents with regard to NGN architectures, IPv4/v6 network architectures and, in particular, DiffServ architectures. + +# Bibliography + +- [b-ITU-T H.248.53] Recommendation ITU-T H.248.53 (2008), *Gateway Control Protocol: Traffic Management Packages*. +- [b-ITU-T I.371] Recommendation ITU-T I.371 (2004), *Traffic control and congestion control in B-ISDN*. +- [b-ITU-T Q.1970] Recommendation ITU-T Q.1970 (2006), *BICC IP Bearer control protocol*. +- [b-ITU-T Q.3303.2] Recommendation ITU-T Q.3303.2 (2007), *Resource Control Protocol No. 3 – Protocol at the interface between a Policy Decision Physical Entity (PD-PE) and a Policy Enforcement Physical Entity (PE-PE) (Rw interface): H.248 alternative*. +- [b-ITU-T Y.1541] Recommendation ITU-T Y.1541 (2006), *Network performance objectives for IP-based services*. +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*. +- [b-ITU-T Y.2111] Recommendation ITU-T Y.2111 (2006), *Resource and admission control functions in Next Generation Networks*. +- [b-IETF RFC 1349] IETF RFC 1349 (1992), *Type of Service in the Internet Protocol Suite*. +<> +- [b-IETF RFC 1812] IETF RFC 1812 (1995), *Requirements for IP Version 4 Routers*. +<> +- [b-IETF RFC 2460] IETF RFC 2460 (1998), *Internet Protocol, Version 6 (IPv6) Specification*. +<> +- [b-IETF RFC 2475] IETF RFC 2475 (1998), *An Architecture for Differentiated Services*. +<> +- [b-IETF RFC 3168] IETF RFC 3168 (2001), *The Addition of Explicit Congestion Notification (ECN) to IP* (NOTE – This RFC obsoletes RFC 2481). +<> +- [b-IETF RFC 3260] IETF RFC 3260 (2002), *New Terminology and Clarifications for Diffserv* (NOTE – This RFC updates RFC 2475). +<> +- [b-IETF RFC 4040] IETF RFC 4040 (2005), *RTP Payload Format for a 64 kbit/s Transparent Call*. +<> +- [b-IETF RFC 4594] IETF RFC 4594 (2006), *Configuration Guidelines for DiffServ Service Classes*. +<> + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.54-200708-I_PDF-E/raw.md b/marked/H/T-REC-H.248.54-200708-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ee5569b9e6eb9a65ceb28b61df7895413d60a24b --- /dev/null +++ b/marked/H/T-REC-H.248.54-200708-I_PDF-E/raw.md @@ -0,0 +1,352 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.54** + +(08/2007) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: MPLS support +package** + +ITU-T Recommendation H.248.54 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.248.54** + +# **Gateway control protocol: MPLS support package** + +## **Summary** + +An H.248 media gateway may be connected to multiprotocol label switching (MPLS) domains in various ways. ITU-T Recommendation H.248.54 defines an H.248 package that allows H.248 streams or terminations to bind to MPLS label switched paths. + +###### **Source** + +ITU-T Recommendation H.248.54 was approved on 29 August 2007 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|----------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 1.1 General MPLS networks ..... | 2 | +| 1.2 PSTN/ISDN evolution to NGN ..... | 2 | +| 1.3 ITU-T NGN Release 1 ..... | 2 | +| 1.4 Relation to "RACF for MPLS based (core) networks" ..... | 2 | +| 2 References..... | 2 | +| 3 Definitions ..... | 3 | +| 3.1 Terms defined elsewhere ..... | 3 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 3 | +| 6 MPLS package..... | 4 | +| 6.1 Properties ..... | 4 | +| 6.2 Events ..... | 4 | +| 6.3 Signals ..... | 4 | +| 6.4 Statistics..... | 4 | +| 6.5 Error codes..... | 4 | +| 6.6 Procedures ..... | 4 | +| Appendix I – Some examples for MPLS network architectures..... | 5 | +| I.1 Introduction ..... | 5 | +| I.2 H.248 MG as a MPLS edge node ..... | 5 | +| I.3 LSPs as aggregates for MG-to-MG traffic ..... | 6 | +| Bibliography..... | 7 | + + + +###### Gateway control protocol: MPLS support package + +# 1 Scope + +An H.248 media gateway (MG) may be connected to multiprotocol label switching (MPLS) domains in various ways. The connection is typically realized via H.248 IP terminations, but there could also be other types of H.248 ephemeral terminations due to the nature of the MPLS protocol architecture. A basic MPLS building block is the so-called "Label Switched Path" (LSP), see [IETF RFC 3031]. The LSP binds MPLS domains and H.248 MGs because LSPs are associated with H.248 ephemeral terminations. This is the basic application of the H.248 *mpls* package. + +The concept of LSP is very extensive, leading to a variety of scenarios involving LSP usage. Some examples are, most notably: + +- LSP establishment and release: + - signalled LSP establishment and release via a label distribution protocol (LDP); + - provisioned LSP. + +NOTE 1 – The *mpls* package is applicable for provisioned LSPs. The support of signalled LSPs is for further study. + +- Hierarchical LSPs: + - relates to the MPLS label stack (see property *stack*; label stacking introduces hierarchy). + +NOTE 2 – The *mpls* package supports "any" legal MPLS label stack size. + +- LSPs used for traffic engineering: + - basic LSPs (according to [IETF RFC 3031]) are not "traffic engineered", e.g., transport characteristics are not explicitly assigned, however: + - LSPs may be used for "traffic engineering" support (see [IETF RFC 2702]). + +NOTE 3 – The dimension of traffic engineering is not addressed by the *mpls* package version 1 as such, but the package permits traffic engineered LSPs. Traffic engineered LSPs are under the responsibility of MG provisioning. The support of signalled, traffic engineered LSPs is for further study and requires the handling of the LSP control protocol (e.g., CR-LDP, RSVP-TE; see [IETF RFC 2702] and [IETF RFC 3468]) by the MGC and/or MG. + +- LSP mapping on H.248 streams and terminations: + +The following relations are applicable for LSP, H.248 stream and termination mapping: + +- 1:1:1 relation between a H.248 stream of an ephemeral termination and LSP; +- N:1:1 relation between H.248 streams, ephemeral termination and LSP; +- N:M:1 relation between H.248 streams, ephemeral terminations and LSP. + +NOTE 4 – The *mpls* package supports the above mapping schemes. + +- LSP termination: + - an H.248 MG could terminate an LSP, in which case the MG acts as an MPLS edge node (more details are outlined in Appendix I); + - an H.248 MG could also provide a LSP traffic forwarding function. The LSP would then involve a single H.248 context with two ephemeral terminations. + +NOTE 5 – The first case is supported. The second case does not require the capabilities of the *mpls* package. + +The *mpls* package may be used in various network environments. Several environments are described below. The function of the *mpls* package is further illustrated by examples in Appendix I. + +## 1.1 General MPLS networks + +[IETF RFC 3031] describes different MPLS node functions. Using this H.248 package, a H.248 MG could provide the *MPLS edge node* function. Further details are outlined in clause I.2. + +## 1.2 PSTN/ISDN evolution to NGN + +[ITU-T Y.2261] describes, amongst other things, core network evolution scenarios towards NGN. In these scenarios, the packet-switched network infrastructure could be MPLS-based. In this particular network evolution scenario, many H.248 MGs are interconnected in the transport domain. This is especially so for the call server-based evolution scenarios to NGN (see clause I.1.1 of [ITU-T Y.2261], see also [ITU-T Y.2271]). Appendix I indicates how the *mpls* package could be used in such NGN use cases. + +## 1.3 ITU-T NGN Release 1 + +MPLS is considered as one of the transport technologies by NGN Release 1 (see clause 5.2 of [ITU-T Y.2111]). The policy enforcement physical entity (PE-PE) may control an entire MPLS domain, or theoretically may also be an element within an MPLS domain. The PE functional entity (PE-FE) may be physically realized in an H.248 MG. In this case, the H.248 protocol may be profiled by the so-called "H.248 Rw profile" (according to [ITU-T Q.3303.2]). The *mpls* package could then be used dependent on specific MPLS deployment scenarios (see above). + +## 1.4 Relation to "RACF for MPLS based (core) networks" + +For further description of MPLS in the NGN RACF, see the ITU-T Y-series of Recommendations. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] ITU-T Recommendation H.248.1 (2005), *Gateway control protocol: Version 3*. +- [ITU-T Q.3303.2] ITU-T Recommendation Q.3303.2 (2007), *Resource control protocol No. 3 – Protocol at the interface between a Policy Decision Physical Entity (PD-PE) and a Policy Enforcement Physical Entity (PE-PE) (Rw interface): H.248 alternative*. +- [ITU-T Y.2111] ITU-T Recommendation Y.2111 (2006), *Resource and admission control functions in Next Generation Networks*. +- [ITU-T Y.2261] ITU-T Recommendation Y.2261 (2006), *PSTN/ISDN evolution to NGN*. +- [ITU-T Y.2271] ITU-T Recommendation Y.2271 (2006), *Call server-based PSTN/ISDN emulation*. +- [IETF RFC 2702] IETF RFC 2702 (1999), *Requirements for Traffic Engineering Over MPLS*. + +[IETF RFC 3031] IETF RFC 3031 (2001), *Multiprotocol Label Switching Architecture*. + +[IETF RFC 3468] IETF RFC 3468 (2003), *The Multiprotocol Label Switching (MPLS) Working Group decision on MPLS signaling protocols*. + +# **3 Definitions** + +## **3.1 Terms defined elsewhere** + +*None.* + +## **3.2 Terms defined in this Recommendation** + +*None.* + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|------------------------------------------------------| +| AMG | Access MG | +| CR-LDP | Constraint-based Routing Label Distribution Protocol | +| FEC | Forwarding Equivalence Class | +| LDP | Label Distribution Protocol | +| LER | Label Edge Router | +| LSP | Label Switched Path | +| LSR | Label Switching Router | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MPLS | MultiProtocol Label Switching | +| NGN | Next Generation Network | +| PE-FE | Policy Enforcement Functional Entity | +| PE-PE | Policy Enforcement Physical Entity | +| RACF | Resource Admission Control Function | +| RSVP-TE | Resource Reservation Protocol – Traffic Engineering | +| TMG | Trunking MG | + +# **5 Conventions** + +*None.* + +# 6 MPLS package + +Package Name: MPLS package +PackageID: mpls (0x0090) – value allocated by IANA. +Description: This package enables a specific MPLS label stack to be passed to the MG to be applied to the given termination/stream. The first entry in the list is the top of the label stack and the last entry is the bottom of the label stack. +Version: 1 +Extends: None + +## 6.1 Properties + +### 6.1.1 MPLS Label Stack + +Property Name: MPLS Label Stack +PropertyID: stack (0x0001) +Description: This property corresponds to a stack of MPLS labels +Type: Sub-list of integer +Possible values: Any legal MPLS label +Default: Provisioned +Defined in: Local Control +Characteristics: Read/Write + +## 6.2 Events + +*None.* + +## 6.3 Signals + +*None.* + +## 6.4 Statistics + +*None.* + +## 6.5 Error codes + +*None.* + +## 6.6 Procedures + +### 6.6.1 Label assignment + +Label assignment relates to the binding of a particular label to a H.248 stream of an ephemeral termination. This property can be applied to ephemeral terminations, which use an MPLS encapsulation. The MG prepends the label stack onto the MPLS packets (so-called "labelled packet", see clause 3.3 of [IETF RFC 3031]) before sending them out of the context. + +# Appendix I + +## Some examples for MPLS network architectures + +(This appendix does not form an integral part of this Recommendation) + +## I.1 Introduction + +This appendix illustrates some examples of MG involvement in MPLS network architectures. + +## I.2 H.248 MG as a MPLS edge node + +The H.248 MG may be connected to MPLS domains in various ways. In this case, the MG acts as a *MPLS edge node* (see [IETF RFC 3031]), see Figure I.1. Subsequent MPLS nodes within the MPLS domain could be, for instance, MPLS label switching routers (LSR), i.e., the H.248 MG would then peer with one or multiple LSRs. Another example is a peering configuration of the H.248 MG with a label switched hop. + +![Diagram of H.248 MG as MPLS edge node](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +The diagram illustrates the H.248 MG acting as an MPLS edge node. At the top, a dashed box labeled "H.248 MG as 'MPLS edge node'" is connected to a "Media gateway controller (MGC)". The MGC is connected to a central "Media gateway (MG)" box via an H.248 stream. The MG box contains two termination points: an "H.248 physical termination" on the left, which connects to a "Circuit-switched network" cloud, and an "H.248 ephemeral termination" on the right, which connects to an "MPLS domain" cloud via an "LSP" (Label Switched Path). The diagram is labeled H248.54(07)\_FI-1. + +Diagram of H.248 MG as MPLS edge node + +Figure I.1 – H.248 MG as MPLS edge node + +The H.248 MG as *MPLS edge node* generally provides both the *MPLS ingress node* and the *MPLS egress node* functions in case of services with bidirectional communication. The LSPs of the MPLS domain, which are terminated at the H.248 MGs, may be provisioned. Other LSPs in the MPLS domain could be dynamically controlled (signalled). + +The MGC binds a particular H.248 stream/termination to a LSP. + +## I.3 LSPs as aggregates for MG-to-MG traffic + +Aggregation is a basic MPLS concept, see clause 3.20 of [IETF RFC 3031]. Such aggregates could be used for MG-to-MG traffic (Figure I.2, Note 1). The relation of a label to an aggregate is detailed in [IETF RFC 3031]. The MGC binds (Figure I.2, Note 2) a H.248 stream/termination to an aggregate via the *stack* property. + +![Diagram of an MPLS domain with four MG (Media Gateway) nodes connected by LSPs.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +The diagram shows a cloud labeled "MPLS domain". Inside the cloud, there are four rectangular boxes, each labeled "MG". These boxes are interconnected by solid lines labeled "LSPs". One MG at the top is connected to three other MGs (left, bottom, and right). The other three MGs are also interconnected with each other, forming a mesh-like topology within the domain. The label "H248.54(07)\_FI-2" is located to the right of the cloud. + +Diagram of an MPLS domain with four MG (Media Gateway) nodes connected by LSPs. + +NOTE 1 – One example could be the interconnection of MGs by an MPLS infrastructure in NGN PSTN emulation subsystems (PES) core networks. [ITU-T Y.2261] depicts two PES scenarios based on (a) TMGs only and (b) TMGs and AMGs. + +NOTE 2 – Label binding means the indication of dedicated forwarding equivalence class (FEC). The meaning of the FEC as such is transparent to the MG in this example, because of the "MPLS ingress role" of the MG. The "binding action" by the MGC is a result of the "route selection", see clause 3.21 of [IETF RFC 3031]. Typically "explicit routing" is then used. + +**Figure I.2 – LSPs used for aggregated MG-to-MG traffic** + +# Bibliography + +- [b-ETSI TS 102 333] ETSI TS 102 333 v1.2.0 (2008), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Annex F, Gate control protocol: MPLS package.* + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/raw.md b/marked/H/T-REC-H.248.55-200806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c9dfe67e8806d65f9575a657d1dc4510477b8e3e --- /dev/null +++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/raw.md @@ -0,0 +1,879 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.55** + +(06/2008) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Generic pull mode +package** + +Recommendation ITU-T H.248.55 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global communication. The text "ITU" is prominently displayed in blue, with "International Telecommunication Union" written in smaller blue text to the right. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T H.248.55** + +## **Gateway control protocol: Generic pull mode package** + +## **Summary** + +H.248 represents a resource control protocol concerning the control of media gateway-level resources. There are two major categories concerning resource control strategies: push mode and pull mode. Push mode is an inherent architectural characteristic of the H.248 master-slave model, where the master entity MGC is pushing the slave entity MG into a particular mode. Pull mode is also supported by the H.248 protocol architecture, but requires additional protocol elements to control a particular pull mode scenario. Recommendation ITU-T H.248.55 defines a generic set of such capabilities. + +###### **Source** + +Recommendation ITU-T H.248.55 was approved on 13 June 2008 by ITU-T Study Group 16 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Terms and Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Resource control framework..... | 2 | +| 6.1 Background..... | 2 | +| 6.2 Resource control mechanisms ..... | 3 | +| 6.3 Summary..... | 8 | +| 7 Generic pull mode package ..... | 9 | +| 7.1 Properties..... | 9 | +| 7.2 Events ..... | 10 | +| 7.3 Signals ..... | 12 | +| 7.4 Statistics..... | 12 | +| 7.5 Error codes..... | 12 | +| 7.6 Procedures ..... | 12 | +| 8 Resource control scenarios ..... | 16 | +| 8.1 Introduction ..... | 16 | +| 8.2 Push mode ..... | 16 | +| 8.3 Context-created MG pull mode ..... | 17 | +| 8.4 Context-less MG pull mode..... | 19 | +| Bibliography..... | 21 | + + + +# Recommendation ITU-T H.248.55 + +## Gateway control protocol: Generic pull mode package + +# 1 Scope + +There are various resource control mechanisms used in next generation networks (NGNs) such as those described in [ITU-T Y.2111]. A policy control mechanism (such as QoS resource control) is described by this Recommendation. The mechanism itself may result in different control scenarios that are primarily dependent on dedicated user and customer premises equipment (UE, CPE) types. This Recommendation describes how H.248 entities behave in such a network environment, and defines an H.248 package, which may be used in a specific resource control scenario. + +Clause 6 provides a background on resource and admission control functions (RACFs) and discusses the resource control modes. The clause then focuses on the "pull mode" of resource control and provides a mapping of the RACF functions and flows of this mode to the H.248 architecture. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*. +- [ITU-T H.248.13] Recommendation ITU-T H.248.13 (2002), *Gateway control protocol: Quality Alert Ceasing package*. +- [ITU-T H.248.14] Recommendation ITU-T H.248.14 (2002), *Gateway control protocol: Inactivity timer package*. +- [ITU-T H.248.36] Recommendation ITU-T H.248.36 (2005), *Gateway control protocol: Hanging Termination Detection package*. +- [ITU-T H.248.40] Recommendation ITU-T H.248.40 (2007), *Gateway control protocol: Application data inactivity detection package*. +- [ITU-T Y.2111] Recommendation ITU-T Y.2111 (2006), *Resource and admission control functions in next generation networks*. + +# 3 Terms and definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 path-coupled QoS signalling:** [ITU-T Y.2111]: A mode of signalling where the signalling messages follow a path that is tied to the data packets. Signalling messages are routed only through nodes that are in the data path. + +**3.1.2 pull mode** [ITU-T Y.2111]: Defined in clause 6.1.2 of [ITU-T Y.2111], "Scenario 2: Pull mode QoS resource control scenario". + +**3.1.3 push mode** [ITU-T Y.2111]: Defined in clause 6.1.2 of [ITU-T Y.2111], "Scenario 1: Push mode QoS resource control scenario". + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following term: + +**3.2.1 authorization token:** A piece of information, either clear or encrypted, which can be used to validate a request for specific resources. This information is used as a unique identifier in policy pull mode. The token is generated by the MGC and may be sent back by the MG to the MGC for the re-authorization of the resource request in the pull mode. + +NOTE – The authorization token may or may not use H.248 information elements. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +ATM Asynchronous Transfer Mode +CPE Customer Premises Equipment +IP Internet Protocol +MG Media Gateway +MGC Media Gateway Controller +MID Message Identifier +NACF Network Attachment Control Function +NGN Next Generation Network +PD-E Policy Decision Entity +PE-E Policy Enforcement Entity +PSTN Public Switched Telecommunications Network +QoS Quality of Service +RACF Resource and Admission Control Function +SCF Service Control Functions +UE User Equipment +VMG Virtual Media Gateway + +# **5 Conventions** + +None. + +# **6 Resource control framework** + +## **6.1 Background** + +Figure 1 provides a simplified model of RACFs in next generation networks. The RACF is aimed at providing real-time application-driven and policy-based transport resource management for a wide range of services and for a variety of transport technologies. See [ITU-T Y.2111] for a detailed description of the RACF subsystem within an NGN. + +![Figure 1: Simplified model of a NGN architecture – Relationship to this Recommendation. The diagram shows a 'RACF within the NGN architecture' box containing SCF, NACF, RACF, UE, and Transport Functions. SCF is connected to RACF. NACF is connected to RACF. UE is connected to Transport Functions. RACF is connected to PD-E (Policy Decision Entity) and PE-E (Policy Enforcement Entity). PD-E is connected to MGC (Media Gateway Controller). PE-E is connected to MG (Media Gateway). Dashed lines indicate application signalling (e.g., call/session control protocol) from SCF to UE, RACF to PD-E, and RACF to PE-E. Solid lines indicate RACF control from RACF to PD-E and RACF to PE-E. Dotted lines indicate transport/path-coupled QoS signalling from Transport Functions to PD-E and Transport Functions to PE-E. Thick solid lines indicate bearer connections (IP) from UE to Transport Functions and from PD-E to PE-E. Annotations 'Scope of this Recommendation' and 'H.248 in this Recommendation' are present near PD-E and PE-E. A legend defines the entities and line types.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +**Legend:** + +- NACF Network Attachment Control Functions +- RACF Resource and Admission Control Functions +- PD-E Policy Decision Entity +- PE-E Policy Enforcement Entity +- SCF Service Control Functions +- UE User Equipment + +**Line Types:** + +- Application signalling (e.g. call/session control protocol) +- \_\_\_\_\_ RACF control +- ..... Transport/Path-coupled QoS signalling +- \_\_\_\_\_ Bearer connection (IP) + +Figure 1: Simplified model of a NGN architecture – Relationship to this Recommendation. The diagram shows a 'RACF within the NGN architecture' box containing SCF, NACF, RACF, UE, and Transport Functions. SCF is connected to RACF. NACF is connected to RACF. UE is connected to Transport Functions. RACF is connected to PD-E (Policy Decision Entity) and PE-E (Policy Enforcement Entity). PD-E is connected to MGC (Media Gateway Controller). PE-E is connected to MG (Media Gateway). Dashed lines indicate application signalling (e.g., call/session control protocol) from SCF to UE, RACF to PD-E, and RACF to PE-E. Solid lines indicate RACF control from RACF to PD-E and RACF to PE-E. Dotted lines indicate transport/path-coupled QoS signalling from Transport Functions to PD-E and Transport Functions to PE-E. Thick solid lines indicate bearer connections (IP) from UE to Transport Functions and from PD-E to PE-E. Annotations 'Scope of this Recommendation' and 'H.248 in this Recommendation' are present near PD-E and PE-E. A legend defines the entities and line types. + +**Figure 1 – Simplified model of a NGN architecture – Relationship to this Recommendation** + +The policy decision entity (PD-E) and policy enforcement entity (PE-E) are elements of this network architecture and in scope of this Recommendation because both could be mapped to H.248 entities (see [b-ITU-T Q.3300] and [b-ITU-T Q.3303.0]). + +## 6.2 Resource control mechanisms + +The RACF should support different *resource control modes* in order to handle different types of user equipment (UE), customer premises equipment (CPE) and/or transport QoS capabilities (see clause 6 of [ITU-T Y.2111]). This clause describes those control modes and their relationship to this Recommendation. + +### 6.2.1 Push versus pull mode + +There are two basic *resource control modes* (see clause 6.1.1 of [ITU-T Y.2111]): + +- 1) Push mode: The RACF makes the authorization and resource control decision based on policy rules and autonomously instructs the transport functions to enforce the policy decision. +- 2) Pull mode: The RACF makes the authorization decision based on policy rules and, *upon the request* of the transport functions, re-authorizes the resource request and responds with the final policy decision for enforcement. + +The correspondent high-level resource control scenarios are summarized by Figure 2. The detailed signalling and control phases are not relevant for this Recommendation (they are outlined in [ITU-T Y.2111]). For information regarding messages associated with each of the numbered flows below see [b-ITU-T Q-Sup.59]. + +![Figure 2: High-level resource control and policy enforcement – Principles of push and pull mode. The diagram is split into two panels: 'Push mode (1)' on the left and 'Pull mode (2)' on the right. Both panels show five functional blocks: UE (User Equipment), Transport Functions, RACF (Resource and Admission Control Functions), NACF (Network Attachment Control Functions), and SCF (Service Control Functions). In 'Push mode (1)', the UE is connected to Transport Functions, which are connected to RACF. RACF is connected to NACF and SCF. SCF is connected to the UE via a dashed application signalling line. Arrows 1-8 show the flow of control and policy. In 'Pull mode (2)', the UE is connected to Transport Functions, which are connected to RACF. RACF is connected to NACF and SCF. SCF is connected to the UE via a dashed application signalling line. Arrows 1-10 show the flow of control, policy, and tokens. A legend at the bottom left defines the line types: dashed for application signalling, solid for RACF control, dotted for transport/path-coupled QoS signalling, and thick solid for bearer connection (IP).](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +**Push mode (1)** + +**Pull mode (2)** + +**Legend:** + +- NACF Network Attachment Control Functions +- RACF Resource and Admission Control Functions +- SCF Service Control Functions +- UE User Equipment + +----- Application signalling (e.g. call/session control protocol) + +——— RACF control + +..... Transport/Path-coupled QoS signalling + +——— Bearer connection (IP) + +Figure 2: High-level resource control and policy enforcement – Principles of push and pull mode. The diagram is split into two panels: 'Push mode (1)' on the left and 'Pull mode (2)' on the right. Both panels show five functional blocks: UE (User Equipment), Transport Functions, RACF (Resource and Admission Control Functions), NACF (Network Attachment Control Functions), and SCF (Service Control Functions). In 'Push mode (1)', the UE is connected to Transport Functions, which are connected to RACF. RACF is connected to NACF and SCF. SCF is connected to the UE via a dashed application signalling line. Arrows 1-8 show the flow of control and policy. In 'Pull mode (2)', the UE is connected to Transport Functions, which are connected to RACF. RACF is connected to NACF and SCF. SCF is connected to the UE via a dashed application signalling line. Arrows 1-10 show the flow of control, policy, and tokens. A legend at the bottom left defines the line types: dashed for application signalling, solid for RACF control, dotted for transport/path-coupled QoS signalling, and thick solid for bearer connection (IP). + +**Figure 2 – High-level resource control and policy enforcement – +Principles of push and pull mode** + +From the perspective of this Recommendation, the main difference between these resource control modes is related to the binding mechanism, between a call/session and associated bearer connection(s) and media flows, i.e., H.248 streams/terminations. This relates to a *correlation identifier* (between service and transport stratum in general NGN terms), which is called *authorization token* (briefly token) in case of RACF. + +Pull mode requires the signalling of such a token between the network and the UE/CPE, but not in push mode. This Recommendation describes the pull mode operation. Push mode is already supported by H.248 as such, thus it is out of scope of this Recommendation. + +### 6.2.2 Pull mode variants – Different token generation mechanisms + +The MGC (PD-E) is involved in the generation of the token. There are multiple possibilities concerning the management of tokens by the MGC. Two possible variants providing representative examples concerning used H.248 capabilities from this Recommendation are depicted by Figure 3. Further variants are not excluded. + +![Figure 3: Pull mode variants – Different token generation mechanisms. The diagram consists of two side-by-side call flow diagrams, (2.a) and (2.b), showing interactions between UE, Transport Functions, RACF, NACF, and SCF. Variant (2.a) shows PD-E-initiated token generation, while (2.b) shows SCF-triggered token generation. A legend at the bottom left defines the entities and line types.](e9314c83043183351ed74908e9bf2f90_img.jpg) + +**Pull mode (2.a):** +**PD-E-initiated Token generation** + +**Pull mode (2.b):** +**SCF-triggered Token generation** + +**Legend:** + +- NACF Network Attachment Control Functions +- PD-E Policy Decision Entity +- RACF Resource and Admission Control Functions +- SCF Service Control Functions +- UE User Equipment + +**Line Types:** + +- Application signalling (e.g. call/session control protocol) +- RACF control +- ..... Transport/Path-coupled QoS signalling +- Bearer connection (IP) + +Figure 3: Pull mode variants – Different token generation mechanisms. The diagram consists of two side-by-side call flow diagrams, (2.a) and (2.b), showing interactions between UE, Transport Functions, RACF, NACF, and SCF. Variant (2.a) shows PD-E-initiated token generation, while (2.b) shows SCF-triggered token generation. A legend at the bottom left defines the entities and line types. + +Figure 3 – Pull mode variants – Different token generation mechanisms + +Common to the pull mode variants is the generation of a token by "RACF" and the sending of that token to the UE via the SCF in steps 5 and 6 in Figure 3. See following sub-clauses for more signalling details. + +#### 6.2.2.1 Abstracted model with H.248 entities + +This Recommendation defines a H.248-based interface between policy decision and policy enforcement entities. The two different token principles for pull mode are mapped on the H.248 connection model. Figure 4 illustrates such a model with the focus on pull mode only, i.e., path-coupled (QoS) signalling protocol is depicted in the drawing. + +![Figure 4: Pull mode variants – Simplified model with H.248 entities as policy decision and policy enforcement entities. The diagram shows three main components: SCF (Service/Call/Session control), RACF & NACF (Policy Decision Entity), and User Equipment. The SCF is connected to the Policy Decision Entity via a dashed line labeled 'Application signalling'. The Policy Decision Entity contains a Media Gateway Controller (MGC) and an H.248 Gateway control protocol. The User Equipment contains a Call/session control protocol, QoS control protocol, and Media/Bearer endpoint. A cloud labeled 'Transport/Path-coupled QoS signalling' is connected to the User Equipment and the Policy Decision Entity. A solid line labeled 'Bearer connection (IP)' connects the User Equipment to the Policy Enforcement Entity. The Policy Enforcement Entity contains a ROOT H.248 Gateway control protocol, QoS control protocol, Context, and IP. The ROOT H.248 Gateway control protocol is connected to the H.248 Gateway control protocol in the Policy Decision Entity via a solid line labeled 'H.248'. The Context is connected to the IP in the Policy Enforcement Entity via a solid line. The IP is connected to the Media/Bearer endpoint in the User Equipment via a solid line labeled 'Bearer connection (IP)'.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +Figure 4: Pull mode variants – Simplified model with H.248 entities as policy decision and policy enforcement entities. The diagram shows three main components: SCF (Service/Call/Session control), RACF & NACF (Policy Decision Entity), and User Equipment. The SCF is connected to the Policy Decision Entity via a dashed line labeled 'Application signalling'. The Policy Decision Entity contains a Media Gateway Controller (MGC) and an H.248 Gateway control protocol. The User Equipment contains a Call/session control protocol, QoS control protocol, and Media/Bearer endpoint. A cloud labeled 'Transport/Path-coupled QoS signalling' is connected to the User Equipment and the Policy Decision Entity. A solid line labeled 'Bearer connection (IP)' connects the User Equipment to the Policy Enforcement Entity. The Policy Enforcement Entity contains a ROOT H.248 Gateway control protocol, QoS control protocol, Context, and IP. The ROOT H.248 Gateway control protocol is connected to the H.248 Gateway control protocol in the Policy Decision Entity via a solid line labeled 'H.248'. The Context is connected to the IP in the Policy Enforcement Entity via a solid line. The IP is connected to the Media/Bearer endpoint in the User Equipment via a solid line labeled 'Bearer connection (IP)'. + +**Figure 4 – Pull mode variants – Simplified model with H.248 entities as policy decision and policy enforcement entities** + +Figure 4 shows only a "half call" model. The two different token principles (in pull mode) use the same H.248 package, the event is associated with different H.248 termination types (root versus non-root), see the next subclauses. + +#### 6.2.2.2 Context-created MG pull mode (PD-E-initiated token generation) + +In this mode, a context has been created with a termination that has an event to detect an incoming resource reservation request. The MGC (PD-E) has to initiate the token generation between steps 2 and 5, or even already before step 2 (see Figure 3). The token generation involves the MG, and the token itself contains H.248 information elements. This token generation mode relates to an advertisement of the token between MGC (PD-E) and MG (PE-E), i.e., the token must be already known by the MG before step 7. + +Figure 5 illustrates the resource reservation request notification process, starting with an incoming (QoS) resource reservation request leading to the event notification towards the MGC. + +![Figure 5: Pull mode variants – Resource reservation request notification process in case of the context-created MG pull mode. The diagram shows the interaction between User Equipment (UE), Media Gateway (MG), Media Gateway Controller (MGC), and Service/Call/Session control (SCF).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates the resource reservation request notification process in the context-created MG pull mode. It is divided into three main functional layers: + +- SCF (Service/Call/Session control):** Located at the top, it contains a 'Service/Call/Session control' block. It receives 'Application signalling' from the User Equipment and has a dashed connection to the Policy Decision Entity. +- RACF & NACF:** The middle layer contains the 'Policy Decision Entity', which includes the 'Media Gateway Controller (MGC)' and the 'H.248 Gateway control protocol'. +- User Equipment:** Located at the bottom left, it contains 'Call/session control protocol', 'QoS control protocol', and 'Media/Bearer endpoint' blocks. +- H.248 Media Gateway (Policy Enforcement Entity):** Located at the bottom right, it contains 'ROOT', 'H.248 Gateway control protocol', 'QoS control protocol', and 'Context C1' (with terminations T1 and T2). It also includes the 'H.248 Media Gateway' and 'Policy Enforcement Entity' blocks. + +The process flow is as follows: + +- The User Equipment sends a 'QoS resource reservation request' (indicated by a clock icon) to the 'QoS control protocol' block within the User Equipment. +- The 'QoS control protocol' block in the User Equipment sends a notification to the 'ROOT' block in the H.248 Media Gateway. +- The 'ROOT' block in the H.248 Media Gateway sends a notification message 'a) NOTIFY.req(NULL/ROOT, Event=rdrr(🕒))' to the 'H.248 Gateway control protocol' block in the MGC. +- The 'H.248 Gateway control protocol' block in the MGC then initiates 'Application signalling' (indicated by a dashed curved arrow) towards the 'Service/Call/Session control' block in the SCF. + +Figure 5: Pull mode variants – Resource reservation request notification process in case of the context-created MG pull mode. The diagram shows the interaction between User Equipment (UE), Media Gateway (MG), Media Gateway Controller (MGC), and Service/Call/Session control (SCF). + +**Figure 5 – Pull mode variants – Resource reservation request notification process in case of the context-created MG pull mode** + +This pull mode variant is called "context-created MG pull mode" because there was already a call/bearer context created (in the MG and MGC) before the MG detects the event (via the created non-root termination in the context). See also clause 8.3 for more details. + +#### 6.2.2.3 Context-less MG pull mode (SCF-triggered token generation) + +In this mode, no context has been created. In order to detect an incoming resource reservation request, an event is set on the root termination. The MGC (PD-E) does not advertise the token towards MG (PE-E) before a path-coupled (QoS) signalling message (step 7) is received by the MG (see Figure 3). + +Figure 6 illustrates the resource reservation request notification process, starting with an incoming (QoS) resource reservation request leading to the event notification toward the MGC. + +![Figure 6: Pull mode variants – Resource reservation request notification process in case of the context-less MG pull mode. The diagram shows the interaction between User Equipment (UE) and the Media Gateway (MG) to notify the Media Gateway Controller (MGC).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates the following components and interactions: + +- SCF (Service/Call/Session control):** Located at the top, it is connected to the RACF & NACF layer via a dashed line labeled "Application signalling". +- RACF & NACF (Policy Decision Entity):** Contains the **Media Gateway Controller (MGC)** and the **H.248 Gateway control protocol**. It is connected to the MG via an H.248 interface. +- User Equipment (UE):** Located at the bottom left, it contains three stacked boxes: **Call/session control protocol**, **QoS control protocol**, and **Media/Bearer endpoint**. A "QoS resource reservation request" (indicated by a clock icon) is sent from the QoS control protocol to the MG. +- H.248 Media Gateway (Policy Enforcement Entity):** Located at the bottom right, it contains a **ROOT** termination (indicated by a circle icon) and **Context C1**. Context C1 includes two terminations, **T1=IP/...** and **T2=IP/...**. The MG also contains **QoS control protocol** boxes. An arrow points from the ROOT termination to the MGC, labeled "b) NOTIFY.req(C1/T1, Event=rdrr( ))" (where "rdrr" is accompanied by a clock icon). + +Figure 6: Pull mode variants – Resource reservation request notification process in case of the context-less MG pull mode. The diagram shows the interaction between User Equipment (UE) and the Media Gateway (MG) to notify the Media Gateway Controller (MGC). + +**Figure 6 – Pull mode variants – Resource reservation request notification process in case of the context-less MG pull mode** + +This pull mode variant is called "context-less MG pull mode" because there is not yet any bearer context created (in the MG) when the MG detects the event (via the root termination). See also clause 8.4 for more details. + +## 6.3 Summary + +The various resource control variants are summarized by Table 1. The correspondent, high-level resource control scenarios at the H.248 interface are outlined in clause 8. + +**Table 1 – Summary of push/pull modes and correspondent H.248 support mechanisms** + +| Mode for policy enforcement | | Token generation | Possible token format/type (Note) | Specific H.248 support mechanisms | +|-----------------------------|----------------------------------------------------|---------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Push mode | – | None required. | None required. | +| 2.a | Pull mode
(Context-created MG pull mode) | PD-E-initiated token generation | H.248 TerminationID, or H.248 ContextID, or H.248 RequestID, or others | The plm package (see clause 7) according to this Recommendation. Event plm/rdrr is associated with a non-root termination. | +| 2.b | Pull mode
(Context-less MG pull mode) | SCF-triggered token generation | e.g., String | The plm package (see clause 7) according to this Recommendation. Event plm/rdrr is associated with the root termination. | + +NOTE – There are multiple possibilities with regard to the syntax and encoding of the authorization token (see also clause 3.2.1) + +In scope of this Recommendation are policy decision/enforcement mechanisms at the H.248 interface. The pushed/pulled policy rules could be related in particular to QoS and network border control, but are applicable for other policy rules in general due to H.248 principles and the generic design *plm* package by this Recommendation. + +# 7 Generic pull mode package + +Package name: Generic Pull Mode Package + +Package ID: *plm* (0x00ca) + +Description: This package defines a number of events to support pull mode QoS resource control. + +This package is generic in the sense that the package is agnostic concerning "path-coupled QoS signalling protocols". The support of such specific horizontal QoS signalling protocols may be addressed by extension package(s). + +Version: 1 + +Extends: None + +## 7.1 Properties + +### 7.1.1 Path-coupled request domains under MGC ownership + +Property name: Path coupled request domains under MGC ownership + +Property ID: *rdmo* (0x0001) + +Description: This root-only property enables an MGC to indicate from which domains path-coupled QoS requests shall be notified to it through the *rdrr* event. For this property "domain" is the source network whose messages a VMG/MGC serves. + +It only applies when the *rdrr* event is set on the root termination. + +Type: Sub-list of String + +Possible values: May be in a domain name or address format, i.e., *domainAddress / domainName* (Annex B of [ITU-T H.248.1]), e.g., "mynet.net", or any other string format. Where wildcarding is needed in the value "\*" shall be used. + +Default: Provisioned +Defined in: TerminationState only on the root termination. +Characteristics: Read/write + +## 7.2 Events + +### 7.2.1 Decision request for QoS resource reservation + +Event name: Decision Request for QoS Resource Reservation +Event ID: *rdrr* (0x0001) +Description: This event is used to detect a resource reservation request for creating a media stream. This request is from an UE/CPE and/or transport network elements to the MG, via dedicated path-coupled QoS signalling. Once detected by the MG, it will notify the MGC of this event to request a resource decision, which the MGC will then provide based on the service requirement and resource condition. +This event shall be applied to the **root termination** or to **ephemeral terminations** only. + +#### 7.2.1.1 EventDescriptor parameters + +##### 7.2.1.1.1 Bearer request address value + +Parameter name: Bearer Request Address Value +Parameter ID: *brav* (0x0001) +Description: This root termination-only parameter provides the address value with regard to the IP address of the MG which is used to receive resource reservation requests in the context-less MG pull mode. +NOTE – This parameter should be included when the *rdrr* event is applied to the root termination of the MG. +Type: Sub-List of String +Optional: Yes +Possible values: IP version 4 address or IP version 6 address. +Encoded as per IP4Address or IP6Address (both excluding the optional port) in Annex A of [ITU-T H.248.1] or IPv6address or IPv4address in Annex B of [ITU-T H.248.1]. +Default: Provisioned. + +##### 7.2.1.1.2 Bearer request port value + +Parameter name: Bearer Request Port Value +Parameter ID: *brpv* (0x0002) +Description: This root termination-only parameter provides the port value with regard to the IP address of the MG which is used to receive resource reservation requests in the context-less MG pull mode. +NOTE – This parameter should be included when the *rdrr* event is applied to the root termination of the MG. +Type: Sub-List of String +Optional: Yes + +Possible values: 0 to 65535 + +Default: Provisioned + +#### 7.2.1.2 ObservedEventsDescriptor parameters + +##### 7.2.1.2.1 Authorization token + +Parameter name: Authorization token + +Parameter ID: authtok (0x0001) + +Description: This is the session authorization token contained in the QoS request received by the MG via dedicated path-coupled QoS signalling (see clause 9.1.2.1.1 of [ITU-T Y.2111]). Whenever this parameter is reported by the MG, the MGC may use it to re-authorize the resource request and respond with the final policy decision to the MG for enforcement. + +Type: Octet String + +Optional: No + +NOTE 1 – The *authtok* parameter is considered to be mandatory. At the time the resource decision request (Figure 13 of [ITU-T Y.2111], message 2) is received by the MG, the bearer path is not yet established. A H.248 call context with a single (ephemeral) termination may or may not yet be created. + +Possible values: Any octet string + +NOTE 2 – The string length is not limited since the octet string is only forwarded to the MGC and does not have to be stored by the MG. + +Default: None + +### 7.2.2 Decision request for QoS resource modification + +Event name: Decision Request for QoS Resource Modification + +Event ID: rdrm (0x0002) + +Description: This event is used to detect a resource modification request for adjusting a media stream. This request is from a UE/CPE and/or transport network elements to the MG via dedicated path-coupled QoS signalling. Once detected by the MG, it will notify the MGC of this event to request resource decision, where the MGC will then provide resource decision based on the service requirement and resource condition. This event shall be applied to **ephemeral terminations** only. + +#### 7.2.2.1 EventDescriptor parameters + +None. + +#### 7.2.2.2 ObservedEventsDescriptor parameters + +##### 7.2.2.2.1 Authorization token + +As per clause 7.2.1.2.1. + +### 7.2.3 Decision request for QoS resource release + +Event name: Decision Request for QoS Resource Release + +Event ID: rdrl (0x0003) + +Description: This event is used to detect a resource request for ceasing a media stream. This request is from a UE/CPE and/or transport network elements to the MG via dedicated path-coupled QoS signalling. Once detected by the MG, it will notify the MGC of this event to request resource decision. This event shall be applied to **ephemeral terminations** only. + +#### 7.2.3.1 EventDescriptor parameters + +None. + +#### 7.2.3.2 ObservedEventsDescriptor parameters + +As per clause 7.2.1.2.1. + +## 7.3 Signals + +None. + +## 7.4 Statistics + +None. + +## 7.5 Error codes + +None. + +## 7.6 Procedures + +### 7.6.1 Enable/disable pull mode + +Pull mode is implicitly enabled for the context-less mode as soon as an *rdrr* event is set on a root termination. Pull mode is implicitly enabled for the context-created mode as soon as an *rdrr* event is set on an ephemeral termination. + +The setting of the *rdrr* event on root and ephemeral terminations is independent as it will be the remote end-point or the MGC that will determine on which address signalling will be received/sent. + +When the *rdrr* event is set to the root termination of the MG, the *brav* and *brpv* parameters should be also included in order to specify or determine the signalling address on which the resource reservation signalling will be received/sent. If the values of those parameters are set to '\$' by the MGC, the MG will then provide the IP address and port in the response. The IP address and port shall be released when the corresponding *rdrr* event is disabled. + +### 7.6.2 Pull mode together with push mode + +Pull mode and push mode may be applied together on the same MG. There are no interactions between the two modes of operation. + +### 7.6.3 QoS control procedures in pull mode + +To invoke the QoS resource reservation for a given flow (see clause 9.1.2 of [ITU-T Y.2111]), the MG receives a 'QoS request' over dedicated path-coupled QoS signalling. See also clause 8. + +#### 7.6.3.1 QoS resource reservation procedure + +The basic procedure of CPE-requested QoS resource reservation procedure is illustrated in Figure 7. The procedure is invoked by a dedicated path-coupled QoS signalling message from the CPE for a given flow. + +![Sequence diagram of the CPE-requested QoS resource reservation procedure. Lifelines: CPE, PE-FE, PD-FE, TRC-FE, SCF. The process involves a trigger at PE-FE, a resource decision request to PD-FE, an optional resource action request/response to SCF, a policy decision at PD-FE, an optional resource initiation request/response to TRC-FE, a final admission decision at PD-FE, and a resource decision response back to PE-FE. Path-coupled QoS signalling is shown between CPE and PE-FE at the start and end.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +sequenceDiagram + participant CPE + participant PE-FE + participant PD-FE + participant TRC-FE + participant SCF + + CPE->>PE-FE: Path-coupled QoS signalling + Note right of PE-FE: 1. Trigger + PE-FE->>PD-FE: 2. Resource decision request + PD-FE-->>SCF: 3. Resource action request/response + Note right of PD-FE: 4. Policy decision + PD-FE-->>TRC-FE: 5. Resource initiation request/response (availability check) + Note right of PD-FE: 6. Final admission decision + PD-FE->>PE-FE: 7. Resource decision response + PE-FE->>CPE: Path-coupled QoS signalling + +``` + +----> Optional      —————> Mandatory + +H.248.55(08)\_F07 + +Sequence diagram of the CPE-requested QoS resource reservation procedure. Lifelines: CPE, PE-FE, PD-FE, TRC-FE, SCF. The process involves a trigger at PE-FE, a resource decision request to PD-FE, an optional resource action request/response to SCF, a policy decision at PD-FE, an optional resource initiation request/response to TRC-FE, a final admission decision at PD-FE, and a resource decision response back to PE-FE. Path-coupled QoS signalling is shown between CPE and PE-FE at the start and end. + +**Figure 7 – CPE-requested QoS resource reservation procedure +(Copy of Figure 13 of [ITU-T Y.2111])** + +NOTE (Figures 7, 8 and 9) – the transport resource control functional entity (TRC-FE) is out of scope of this Recommendation. The functional entities "PE-FE" and "PD-FE" of [ITU-T Y.2111] are relating to the H.248 entities "PE-E" and "PD-E" in this Recommendation. + +The individual signalling steps are described in clause 9.1.2.1.1 of [ITU-T Y.2111]. + +#### 7.6.3.2 QoS resource modification procedure + +The CPE-requested QoS resource modification procedure illustrated in Figure 8 is invoked by a resource decision request. + +![Sequence diagram for CPE-requested QoS resource modification procedure. Lifelines: CPE, PE-FE, PD-FE, TRC-FE, SCF. The process involves a trigger at PE-FE, a resource decision request to PD-FE, a resource action request/response to SCF, a policy decision at PD-FE, a resource modification request/response to TRC-FE, a final admission decision at PD-FE, and a resource decision response back to PE-FE. Path-coupled QoS signalling is shown between CPE and PE-FE at the beginning and end.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +sequenceDiagram + participant CPE + participant PE-FE + participant PD-FE + participant TRC-FE + participant SCF + Note right of PE-FE: 1. Trigger + PE-FE->>PD-FE: 2. Resource decision request (modification) + PD-FE-->>SCF: 3. Resource action request/response + Note right of PD-FE: 4. Policy decision + PD-FE->>TRC-FE: 5. Resource modification request/response (availability check) + Note right of PD-FE: 6. Final admission decision + PD-FE->>PE-FE: 7. Resource decision response + Note left of PE-FE: Path-coupled QoS signalling + Note right of SCF: H.248.55(08)_F08 + +``` + +Sequence diagram for CPE-requested QoS resource modification procedure. Lifelines: CPE, PE-FE, PD-FE, TRC-FE, SCF. The process involves a trigger at PE-FE, a resource decision request to PD-FE, a resource action request/response to SCF, a policy decision at PD-FE, a resource modification request/response to TRC-FE, a final admission decision at PD-FE, and a resource decision response back to PE-FE. Path-coupled QoS signalling is shown between CPE and PE-FE at the beginning and end. + +**Figure 8 – CPE-requested QoS resource modification procedure +(copy of Figure 16 of [ITU-T Y.2111])** + +The individual signalling steps are described in clause 9.1.2.1.2 of [ITU-T Y.2111]. + +#### 7.6.3.3 QoS resource release procedure + +The CPE-requested QoS resource release procedure illustrated in Figure 9 is invoked by a resource notification from the PE-FE for a given flow. + +![Sequence diagram for CPE-requested QoS resource release procedure. Lifelines: CPE, PE-FE, PD-FE, TRC-FE, SCF. The process involves a trigger at PE-FE, a resource notification to PD-FE, a resource release request/response to TRC-FE, and a resource release indication to SCF. Path-coupled QoS signalling is shown between CPE and PE-FE at the beginning.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +``` + +sequenceDiagram + participant CPE + participant PE-FE + participant PD-FE + participant TRC-FE + participant SCF + Note right of PE-FE: 1. Trigger + PE-FE->>PD-FE: 2. Resource notification + PD-FE->>TRC-FE: 3. Resource release request/response + PD-FE->>SCF: 4. Resource release indication + Note left of PE-FE: Path-coupled QoS signalling + Note right of SCF: H.248.55(08)_F09 + +``` + +Sequence diagram for CPE-requested QoS resource release procedure. Lifelines: CPE, PE-FE, PD-FE, TRC-FE, SCF. The process involves a trigger at PE-FE, a resource notification to PD-FE, a resource release request/response to TRC-FE, and a resource release indication to SCF. Path-coupled QoS signalling is shown between CPE and PE-FE at the beginning. + +**Figure 9 – CPE-requested QoS resource release procedure +(copy of Figure 19 of [ITU-T Y.2111])** + +The individual signalling steps are described in clause 9.1.2.1.5 of [ITU-T Y.2111]. + +### 7.6.4 Interaction with path-coupled QoS signalling + +There is no direct interaction between (horizontal) path-coupled QoS signalling and (vertical) H.248 signalling (for the application of this package) other than that path-coupled QoS signalling may trigger H.248 event reporting. The two directions of path-coupled QoS signalling are described in more detail: + +- Incoming request from path-coupled QoS signalling to MG: + - Specific request triggers the correspondent H.248 event, i.e., either *plm/rdr*, *plm/rdm* or *plm/rdl*. + - Relevant information elements of the request will be mapped to the correspondent H.248 *ObservedEventsDescriptor* parameter. +- Outgoing path-coupled QoS signalling from MG: + - There is generally no interaction due to processing of events as defined by this package. That means that the NOTIFY.reply command from the MGC back to the MG will not necessarily trigger path-coupled QoS signalling. + - Other usual H.248 commands for ephemeral terminations (such as ADD.request, MODIFY.request, SUBTRACT.request) could lead to triggers for path-coupled QoS signalling, but such types of interaction is out of scope of this Recommendation. + +The procedures between (horizontal) path-coupled QoS signalling and (vertical) H.248 signalling are therefore considered to be loosely coupled. + +### 7.6.5 Identifying a VMG and/or MGC from a path-coupled QoS request + +Whilst a physical MG may terminate path-coupled QoS requests at a single address/port, when VMGs are used there is a problem for the MG to identify the correct instance of VMG to use to send a notify command to when the *rdr* event is detected. As there is a one-to-one relationship between a VMG and MGC (from an MG perspective), the MG also has a problem to determine which MGC to send the event to. The following behaviour is possible with regard to the authentication token when a path-coupled QoS request is received: + +- 1) The MG receives the authentication token and it is able to read the token and it contains the address of the MGC. +- 2) The MG receives the authentication token and it is able to read the token but it does not reveal any information on which VMG/MGC to use. +- 3) The MG receives the authentication token but it is unable to read the token (i.e., it is token-agnostic). +- 4) The authentication token is absent from the path-coupled QoS request. + +In situations 2, 3, 4, where the authentication token cannot reveal VMG/MGC selection information, a VMG may examine the source of the path-coupled QoS signalling and compare it to the *rdmo* property to determine the correct VMG/MGC. These situations are applicable to both context-created and context-less pull scenarios where VMGs are used. + +In situation 1, where the authentication token may reveal the correct MGC to use (e.g., mapping to the H.248 MID), the physical MG may still be unable to determine the correct VMG instance, as the MGC may control several VMGs. A VMG may then use to *rdmo* property to determine if it is the correct VMG for this instance. + +If the MGC has set the *rdmo* property, the MG/VMG shall compare the source of the path-coupled QoS signalling and the domain information from the property. If the source of the path-coupled QoS signalling is part of the domain indicated in the *rdmo* property and the *rdr* event is set on the Root Termination of the MG, a NOTIFY.req shall be generated to that MGC. If the source of the path-coupled QoS signalling is not part of the domain no event shall be generated. + +If the MGC has not set the *rdmo* property, then the MG/VMG shall use other means to determine to which MGC an *rdrr* event notification is sent. + +For optimal usage, all MGCs connected to an MG should set the *rdmo* property in order to correctly identify the MGC that should receive the *rdrr* event notifications. In the case where a physical MG has VMGs with the *rdmo* property both set and unset, the set properties shall take precedence. The setting of the *rdmo* property and *rdrr* event should occur at the establishment of the control association between the MGC and VMG (MGs), or via provisioning. + +### 7.6.6 Failure handling in pull mode + +There is no special failure handling in pull mode. Failure handling is generally based on ServiceChange procedures (see Annex F of [ITU-T H.248.1]) or usual H.248 error handling. Specific failure types may be addressed by dedicated H.248 protocol elements, such as, e.g., clause E.11.2 of [ITU-T H.248.1], [ITU-T H.248.13], [ITU-T H.248.14], [ITU-T H.248.36] or [ITU-T H.248.40]. This is out of scope of this package definition. + +# 8 Resource control scenarios + +## 8.1 Introduction + +Resource control in networks (as in NGN RACF) is related to different operations, such as: + +- 1) resource authorization; +- 2) resource reservation; +- 3) resource commitment; +- 4) resource modification(s); +- 5) resource de-activation; +- 6) resource release; + +There are many descriptions of how one or multiple resource control operations may be mapped on signalling flows (e.g., see [ITU-T Y.2111]). + +Thus, the described resource control scenarios in this clause are examples. The figures use pseudo code for the H.248 signalling elements. + +## 8.2 Push mode + +Figure 10 shows a typical flow with pseudo code for push mode. This clause and example is only for completeness; no capabilities from this Recommendation are required. + +![Sequence diagram illustrating the Push mode for resource reservation and commitment between a Police Decision Entity (MGC) and a Police Enforcement Entity (MG).](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +The diagram shows the interaction between the **Police Decision Entity (MGC)** and the **Police Enforcement Entity (MG)** for resource reservation and commitment in push mode. + +**Sequence of events:** + +- 1. Policy decision, resource reservation** (MGC internal step) +- ADD.request** (MGC to MG) with parameters `(Context=$; Termination=$)`. A blue starburst labeled **Policy** is shown near the MGC. +- NOTE - The push mode does not require any events for MG-requested policy rules (because there is not any relation to potential path-coupled QoS signalling).** (indicated by a dashed arrow from the MG) +- 2. Resource commitment** (MG internal step) +- ADD.reply** (MG to MGC) with parameters `(Context=x; Termination=IP/y)` + +**Scenario may continue with** + +- possible further resource modifications, +- possible resource de-activation, till +- resource release. + +**NOTE - Only the 1st H.248 Termination and Stream is shown. There are at least two H.248 Terminations per Context, and/or there could be multiple H.248 Streams per Termination.** + +Sequence diagram illustrating the Push mode for resource reservation and commitment between a Police Decision Entity (MGC) and a Police Enforcement Entity (MG). + +**Figure 10 – Push mode – Phase of resource reservation and commitment** + +## 8.3 Context-created MG pull mode + +Figure 11 illustrates a typical flow with pseudo code for the context-created pull mode variant. The purpose of the first ADD request/reply scenario is the creation of a context including an H.248 IP termination and enabled *plm* package events. The ADD.request command may include only the absolute minimum of H.248 information elements, e.g., may not contain the LocalControl, local and/or remote descriptor. Thus, the created H.248 IP stream/termination may be completely underspecified. + +The crucial difference in comparison to the context-less pull mode is the fact that the used token is based on H.248 information elements related to the created context. + +The incoming (QoS) signalling message (step 6) carries the token. The token is then relayed by the MG toward the MGC via the correlated H.248 Context via the event *plm/rdrr* associated with the Stream/Termination. + +![Sequence diagram showing the interaction between a Police Decision Entity (MGC) and a Police Enforcement Entity (MG) for context-created pull mode resource reservation. The process involves ADD.request, ADD.reply, NOTIFY.request, NOTIFY.reply, MODIFY.request, and MODIFY.reply messages. A note indicates that the token in the NOTIFY.request message correlates with the H.248 Context and Stream. A final note states that steps 7 and 8 are the usual policy decision and enforcement phases.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +**Sequence Diagram: Context-created pull mode – Phases of resource reservation and commitment** + +**Entities:** Police Decision Entity (MGC), Police Enforcement Entity (MG) + +**Sequence of Messages:** + +- 1. Generate Token, 2. Arm Event(s)** (MGC internal steps) +- ADD.request** (MGC to MG): *(Context=\$; Termination=\$; Events=plm/{rdrr,rdm,rdrl})* +- 3. Context x created, 4. Termination IP/y created & Events enabled** (MG internal steps) +- ADD.reply** (MG to MGC): *(Context=x; Termination=IP/y)* +- 5. Token = Identifier of Context, Termination or Event** (MGC internal step, marked with a red 'T' icon) +- 6. Trigger (= incoming QoS reservation resource request)** (MG internal step, marked with a red 'T' icon). A note indicates: *The token of the incoming QoS reservation resource request message allows the correlation with the prepared H.248 Context and the relevant H.248 Stream.* +- NOTIFY.request** (MG to MGC): *(Context=x; Termination=IP/y; Events=plm/rdrr(Token))* (marked with a red 'T' icon) +- NOTIFY.reply** (MGC to MG): *(...)* +- 7. Policy decision** (MGC internal step) +- MODIFY.request** (MGC to MG): *(Context=x; Termination=IP/y; "policy rules")* (marked with a blue 'Policy' icon) +- 8. Policy enforcement** (MG internal step) +- MODIFY.reply** (MG to MGC): *(...)* + +**Scenario may continue with:** + +- possible further resource modifications, +- possible resource de-activation, till +- resource release. + +**NOTE - Only the 1st H.248 Termination and Stream is shown. There are at least two H.248 Terminations per Context, and/or there could be multiple H.248 Streams per Termination.** + +Sequence diagram showing the interaction between a Police Decision Entity (MGC) and a Police Enforcement Entity (MG) for context-created pull mode resource reservation. The process involves ADD.request, ADD.reply, NOTIFY.request, NOTIFY.reply, MODIFY.request, and MODIFY.reply messages. A note indicates that the token in the NOTIFY.request message correlates with the H.248 Context and Stream. A final note states that steps 7 and 8 are the usual policy decision and enforcement phases. + +**Figure 11 – Context-created pull mode – Phases of resource reservation and commitment** + +Steps 7 and 8 are the usual policy decision and enforcement phases. + +## 8.4 Context-less MG pull mode + +There are two basic procedures related to this pull mode variant. + +### 8.4.1 Session/call-independent procedure: Enabling for MG-level resource reservation request events + +The event for (QoS) resource reservation requests is enabled at the MG-level. Figure 12 shows an example flow with pseudo code, highlighting the H.248.55-specific protocol elements. + +![Sequence diagram showing the interaction between a Police Decision Entity (MGC) and a Police Enforcement Entity (MG) to enable resource reservation request events.](e354b57563dae469c00b412b2abdf765_img.jpg) + +The diagram illustrates a sequence of interactions between two entities: **Police Decision Entity (MGC)** and **Police Enforcement Entity (MG)**. + +- Step 1:** On the MGC side, a box labeled "1. Arm Event for 'resource reservation requests' on MG-level" is shown. An arrow labeled **MODIFY.request** points from the MGC to the MG. Below this arrow, the parameters are specified: `(Context=-; Termination=ROOT; Event=plm/rdrr(brav=$,brpv=$))`. +- Step 2:** On the MG side, a box labeled "2. Event enabled for 'Context-less' pull mode triggers" is shown. An arrow labeled **MODIFY.reply** points from the MG back to the MGC, with an ellipsis `(...)` below it. + +**NOTE - The event could be alternatively provisioned instead of a H.248 signaling procedure.** + +Sequence diagram showing the interaction between a Police Decision Entity (MGC) and a Police Enforcement Entity (MG) to enable resource reservation request events. + +**Figure 12 – Context-less pull mode – Enabling for MG-level resource reservation request events** + +Only the event *plm/rdrr* is associated with the root termination. + +NOTE – There are many commonalities (from an H.248 perspective), concerning the handling of incoming bearer-level signalling events, between path-coupled QoS signalling protocols and PSTN analogue line signalling, channel-associated signalling or bearer control protocols (such as AAL2 Q.2630 signalling or ATM signalling). The similarities are in the areas of events, correlation elements between bearer and signalled information elements or procedures. + +### 8.4.2 Session/call-dependent procedures: Notification of context-related resource reservation request events + +Figure 13 shows the session scenario, starting with an incoming (QoS) resource reservation request. The (QoS) signalling message carries the token, which is then relayed by the MG towards the MGC via the root termination event *plm/rdrr*. + +![Sequence diagram showing the interaction between a Police Decision Entity (MGC) and a Police Enforcement Entity (MG) for context-less pull mode. The process involves a trigger, notification, policy decision, and resource commitment.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +``` + +sequenceDiagram + participant MGC as Police Decision Entity (MGC) + participant MG as Police Enforcement Entity (MG) + Note right of MG: 1. Trigger (= incoming QoS reservation resource request) + MG->>MGC: NOTIFY.request +(Context=-; Termination=ROOT; +Event=plm/rdrr(Token)) + Note right of MGC: 2. Policy decision, resource reservation + MGC->>MG: ADD.request +(Context=$; Termination=$; +Events=plm/{rdm,rdl}) + Note right of MG: 3. Resource commitment + MG->>MGC: ADD.reply +(Context=x; Termination=IP/y) + +``` + +**Scenario may continue with** + +- possible further resource modifications, +- possible resource de-activation, till +- resource release. + +**NOTE - Only the 1st H.248 Termination and Stream is shown. There are at least two H.248 Terminations per Context, and/or there could be multiple H.248 Streams per Termination.** + +Sequence diagram showing the interaction between a Police Decision Entity (MGC) and a Police Enforcement Entity (MG) for context-less pull mode. The process involves a trigger, notification, policy decision, and resource commitment. + +**Figure 13 – Context-less pull mode – Notification of context-related resource reservation request events** + +The subsequent ADD.request then leads to the creation of a context and IP termination, as well as the setting of the two other *plm* events *rdm* and *rdl*. + +## Bibliography + +- [b-ITU-T Q.3300] Recommendation ITU-T Q.3300 (2008), *Architectural framework for the Q.33xx series of Recommendations*. +- [b-ITU-T Q.3303.0] Recommendation ITU-T Q.3303.0 (2007), *Resource control protocol No. 3 – Protocols at the Rw interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE): Overview*. +- [b-ITU-T Y.2121] Recommendation ITU-T Y.2121 (2008), *Requirements for the support of flow-state-aware transport technology in NGN*. +- [b-ITU-T Q.2630.x] Recommendation ITU-T Q.2630.x-series (in force), *AAL type 2 signalling protocol – Capability Sets 1, 2 and 3*. +- [b-ITU-T Q-Sup.59] ITU-T Q-series Recommendations – Supplement 59 (2008), *Signalling flows and parameter mapping for resource control*. +- [b-IETF RFC 2205] IETF RFC 2205 (1997), *Resource ReSerVation Protocol (RSVP) – Version 1 Functional Specification*. +<> +- [b-IETF RFC 2748] IETF RFC 2748 (2000), *The COPS (Common Open Policy Service) Protocol*. +<> +- [b-IETF RFC 2749] IETF RFC 2749 (2000), *COPS usage for RSVP*. +<> +- [b-IETF RFC 2750] IETF RFC 2750 (2000), *RSVP Extensions for Policy Control*. +<> +- [b-IETF RFC 3084] IETF RFC 3084 (2001), *COPS Usage for Policy Provisioning (COPS-PR)*. +<> +- [b-IETF RFC 3313] IETF RFC 3313 (2003), *Private Session Initiation Protocol (SIP) Extensions for Media Authorization*. +<> +- [b-IETF RFC 3520] IETF RFC 3520 (2003), *Session Authorization Policy Element*. +<> +- [b-IETF RFC 3521] IETF RFC 3521 (2003), *Framework for Session Set-up with Media Authorization*. +<> + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.56-200708-I_PDF-E/raw.md b/marked/H/T-REC-H.248.56-200708-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1c09a0f042dca3405a808008a3f8edac29fdad41 --- /dev/null +++ b/marked/H/T-REC-H.248.56-200708-I_PDF-E/raw.md @@ -0,0 +1,344 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.56** + +(08/2007) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: Packages for virtual private network support** + +ITU-T Recommendation H.248.56 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.248.56** + +# **Gateway control protocol: Packages for virtual private network support** + +## **Summary** + +ITU-T Recommendation H.248.56 defines H.248 packages for virtual private network (VPN) support and focuses on Ethernet-based virtual local area networks, representing a network-based layer 2 VPN type. + +###### **Source** + +ITU-T Recommendation H.248.56 was approved on 29 August 2007 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 1.1 General ..... | 1 | +| 1.2 NB layer 2 VPN..... | 2 | +| 1.3 NB layer 3 VPN..... | 2 | +| 2 References..... | 2 | +| 3 Definitions ..... | 3 | +| 3.1 Terms defined elsewhere..... | 3 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 4 | +| 6 VLAN package for Ethernet VLANs ..... | 4 | +| 6.1 Properties..... | 4 | +| 6.2 Events ..... | 5 | +| 6.3 Signals ..... | 5 | +| 6.4 Statistics..... | 5 | +| 6.5 Error Codes..... | 5 | +| 6.6 Procedures ..... | 5 | +| Bibliography..... | 7 | + + + +# **Gateway control protocol: Packages for virtual private network support** + +# **1 Scope** + +## **1.1 General** + +H.248 media gateways (MG) may be located at the boundary of virtual private networks (VPNs). At this connection point, H.248 ephemeral terminations would be involved in VPN services. In order to bound the scope from a H.248 point of view, the separation in client/server VPNs is detailed in [ITU-T Y.1314], [ITU-T Y.1311]: + +- Client/server VPNs have a two-layer hierarchy in which a VPN server layer network is used to support one or more VPN client layer networks. [ITU-T Y.1311] describes client/server VPNs in terms of VPN service types and VPN transport types, where the term VPN service type refers to the VPN client layer and the term VPN transport type refers to the VPN server layer. The different VPN service (client) and transport (server) types are classified in [ITU-T Y.1311] as described below in Table 1. + +**Table 1 – Y.1311 service types** + +| Service type | Description | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Layer 1 | Provides a physical layer service between customer sites belonging to the same VPN. Connections can be based on physical ports, optical wavelengths, SDH/SONET VCs, frequency channels, or timeslots. | +| Layer 2 | Provides a data link layer service between customer nodes belonging to the VPN. Forwarding of user data packets is based on information in the packets' data link layer headers (e.g., DLCI, ATM VCI/VPI, or MAC addresses). | +| Layer 3 | Provides a network layer service between customer nodes belonging to the VPN. Forwarding of user data packets based on information in the layer 3 header (e.g., IPv4 or IPv6 destination address). | + +In scope of H.248.56 are network-based VPNs (NB VPN) only, and only virtual transport networks because the H.248 MG is only involved in the network transport infrastructure. The types of VPNs could be further limited to layer 2 and layer 3 VPNs (L2VPN, L3VPN) only. This is because the bearer connection endpoint behind H.248 ephemeral terminations is basically a bearer technology from layer 2/3. + +VPN support for H.248 physical terminations is in principle possible with H.248 (see, e.g., ITU-T Rec. H.248.21), but out of scope of this Recommendation because e.g., there is not any explicit VPN-ID on bearer level. + +The edge of a VPN could be further distributed in customer edge (CE) and provider edge (PE) VPN network elements, see clause 5.2.1 of [ITU-T Y.1311] (or [ITU-T G.8011.2/Y.1307.2] for Ethernet-based VPNs). The H.248 MG may provide a "customer" edge VPN function, but also a collapsed CE/PE VPN edge function. + +## 1.2 NB layer 2 VPN + +### 1.2.1 Ethernet VLAN + +This Recommendation supports Ethernet VLANs as NB layer 2 VPN type by the H.248 *vlan* package (see clause 6). Clause 6.3 of [ITU-T Y.1314] provides an overview about Ethernet VLANs: + +- [IEEE 802.1Q] defines the operation of virtual LAN (VLAN) bridges that permit the definition, operation and administration of virtual LAN topologies within a bridged LAN infrastructure. VLANs allow end-stations (*here H.248 MGs*) on multiple physical LAN segments to communicate as if they were connected to the same LAN segment. End users (*here H.248 MGs*) and hubs/switches can be moved to different VLANs by changing the VLAN configuration on the port/interface on the 802.1Q-compliant switching device that the end-station or hub/switch connects to. +- Traffic separation for frames belonging to different VLANs across a shared infrastructure is achieved by inserting a tag with a VLAN identifier (VID) into each frame. A VID must be assigned for each VLAN (1 to 4096) and must be globally unique within the same physical infrastructure. One of the drawbacks to this approach is that customers also use VLANs within their own network, which introduces VID allocation and limitation issues. To solve this problem, a second IEEE 802.1Q-tag can be appended to customer IEEE 802.1Q-tagged packets that enter the providers' network (Q-in-Q as defined in [IEEE 802.1ad]). This separates the providers' VLAN space from the customers' VLAN space and allows customers to use whatever VIDs they want. + +NOTE – Another option is to use a MAC-in-MAC approach (as defined in [IEEE 802.1ah]), in which a provider appends a second Ethernet header to the customers' packet. However, this option creates a client/server VPN rather than a peer-level VPN because the customers' frame is encapsulated inside a provider frame. + +The *tags* property of the H.248 *vlan* package is a VPN-ID (called the VLAN identifier, VID; see clause 6.1.1) and is used to assign an H.248 stream of an Ethernet-based ephemeral termination to a particular VLAN. + +#### 1.2.1.1 Ethernet VLAN with traffic management extension + +[IEEE 802.1p] is an extension of [IEEE 802.1Q]. [IEEE 802.1Q] specifies a tag that appends to an Ethernet MAC frame. The VLAN tag has two parts: The VLAN ID (12 bits) and prioritization (3 bits). The prioritization field was not defined and used in the 802.1Q VLAN standard. [IEEE 802.1p] defines this prioritization field. [IEEE 802.1p] establishes eight levels of priority. + +The H.248 *vlan* package addresses [IEEE 802.1p] and [IEEE 802.1Q] by dedicated properties, see clause 6.1.1 and 6.1.2 respectively. + +### 1.2.2 Other NB layer 2 VPNs + +For further study. + +## 1.3 NB layer 3 VPN + +Support for NB L3 VPNs, e.g., like NB IP VPNs, is for further study. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the + +currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.8011.2] ITU-T Recommendation G.8011.2/Y.1307.2 (2005), *Ethernet virtual private line service*. +- [ITU-T H.248.1] ITU-T Recommendation H.248.1 (2005), *Gateway control protocol: Version 3*. +- [ITU-T Y.1311] ITU-T Recommendation Y.1311 (2002), *Network-based VPNs – Generic architecture and service requirements*. +- [ITU-T Y.1314] ITU-T Recommendation Y.1314 (2005), *Virtual private network functional decomposition*. +- [IEEE 802.1ad] IEEE 802.1ad (2005), *IEEE Standard for local and metropolitan area networks – Virtual Bridged Local Area Networks – Amendment 4: Provider Bridges*. +- [IEEE 802.1D] IEEE 802.1D (2004), *IEEE Standard for local and metropolitan area networks – Media Access Control (MAC) Bridges*. +- [IEEE 802.1p] IEEE 802.1p (2004), *LAN Layer 2 QoS/CoS Protocol For Traffic Prioritization* (see clause "Introduction" in [IEEE 802.1Q] on "Relationship between IEEE 802.1D and IEEE 802.1Q"). +- [IEEE 802.1Q] IEEE 802.1Q (2005), *IEEE Standard for local and metropolitan area networks – Virtual bridged local area networks*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere. + +- 3.1.1 NB layer 2 VPN:** See clause 3.3 of [ITU-T Y.1311]. +- 3.1.2 NB layer 3 VPN:** See clause 3.4 of [ITU-T Y.1311]. +- 3.1.3 NB IP VPN:** See clause 3.4.1 of [ITU-T Y.1311]. +- 3.1.4 virtual services network (VSN):** See clause 3.5 of [ITU-T Y.1311]. +- 3.1.5 virtual transport network:** See clause 3.6 of [ITU-T Y.1311]. + +## 3.2 Terms defined in this Recommendation + +*None.* + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +- | | | +|-----|----------------------------| +| CE | Customer Edge | +| EPL | Ethernet Private Line | +| ETH | Ethernet MAC layer network | +| LAN | Local Area Network | +| MAC | Medium Access Control | +| MG | Media Gateway | + +| | | +|--------|----------------------------------------------| +| MGC | Media Gateway Controller | +| NB | Network Based | +| PE | Provider Edge | +| PPVPN | Provider Provisioned Virtual Private Network | +| TCI | Tag Control Information | +| VID | VLAN Identifier | +| VLAN | Virtual Local Area Network | +| VPN | Virtual Private Network | +| VPN-ID | VPN Identifier | +| VSN | Virtual Service Network | +| VTN | Virtual Transport Network | + +# 5 Conventions + +*None.* + +# 6 VLAN package for Ethernet VLANs + +| | | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | VLAN package | +| PackageID: | vlan (0x0091) – value allocated by IANA. | +| Description: | This package enables up to two layer 2 VLAN tags (for "virtual LAN" support in [IEEE 802.1Q] and, additionally, support of "provider VLAN" based on "Q in Q" VLAN stacking in [IEEE 802.1ad]) to be passed to the MG. It also allows a layer 2 priority value (according to [IEEE 802.1p]) to be applied to the given Ethernet-based ephemeral termination. | +| Version: | 1 | +| Extends: | None | + +## 6.1 Properties + +### 6.1.1 VLAN tags + +| | | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | VLAN tags | +| PropertyID: | tags (0x0001) | +| Description: | This property corresponds to one or two VLAN tags. Where two VLAN tags are included, tag stacking (.1q in .1q) shall be implemented. The first tag in the Ethernet frame shall be set to the value of the first tag in the list. Each property list entry relates to a 12-bit VLAN identifier (VID). The VID is part of the IEEE 802.1Q tag control information (TCI) field. | +| Type: | Sublist of integer | +| Possible values: | 0 to 4096 | +| Default: | None (see also clause 6.6.5). | +| Defined in: | Local control | +| Characteristics: | Read/write | + +### 6.1.2 Ethernet priority + +| | | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Property name: | Ethernet priority | +| PropertyID: | pri (0x0002) | +| Description: | This property identifies the priority of each VLAN tag. The first priority corresponds to the first VLAN tag, the second priority corresponds to the second VLAN tag. | +| Type: | Sublist of integer | +| Possible values: | 0 to 7 | +| Default: | None (see also clause 6.6.5). | +| Defined in: | Local control | +| Characteristics: | Read/write | + +## 6.2 Events + +*None.* + +## 6.3 Signals + +*None.* + +## 6.4 Statistics + +*None.* + +## 6.5 Error Codes + +*None.* + +## 6.6 Procedures + +This package can be applied to ephemeral terminations where the MG is using an Ethernet encapsulation on the interface (compliant to [IEEE 802.1p], [IEEE 802.1Q] and [IEEE 802.1ad]). For terminations where the properties are set, the MG adds the given VLAN tag(s) and priorities to the Ethernet encapsulated media flow prior to sending it out of the context. + +### 6.6.1 VPN identification + +The MGC indicates a dedicated VLAN by signalling a correspondent *tags* value to the MG. A provisioned default value could be beneficial in case of a single VLAN, used for all Ethernet interfaces of the MG. + +### 6.6.2 QoS marking + +The MGC marks the priority of all egress Ethernet frames of an ephemeral termination by signalling a correspondent *priority* value to the MG. + +NOTE – The function of QoS marking is possible for many packet-switched bearer technologies (see also *ds* package). + +### 6.6.3 Coupling of both functions + +The functions of VLAN tagging and priority setting are decoupled and may be independently applied. + +### 6.6.4 Unsuccessful scenarios + +This clause is relevant only when both package properties are used. + +The Ethernet is either used as a flat or as a stacked VLAN. The sublist of possible values of both properties has then either one or two list items. The size of both sublists must be the same. Different sublist sizes identify an incorrect signalling of the property values. The MG shall reply with error code #454 ("No such parameter value in this package") in such a case. + +### **6.6.5 Default values for properties** + +There are no default property values defined by this Recommendation. The primary reason is that a single MG could be connected to multiple VLANs, and every individual VLAN may use a different value range for VLAN tags and/or priorities. + +# Bibliography + +- [b-IETF RFC 2764] IETF RFC 2764 (2000), *A Framework for IP Based Virtual Private Networks.* +- [b-ETSI TS 102 333] ETSI TS 102 333 (2004), *Gate control protocol.* + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.57-201410-I_PDF-E/raw.md b/marked/H/T-REC-H.248.57-201410-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..54e70089843eefddb4ccfdad68ca01db8cce77d7 --- /dev/null +++ b/marked/H/T-REC-H.248.57-201410-I_PDF-E/raw.md @@ -0,0 +1,621 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.57** + +(10/2014) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: RTP control protocol +package** + +Recommendation ITU-T H.248.57 + +ITU-T + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "ITU" is written in a large, bold, blue font, and below it, "International Telecommunication Union" is written in a smaller, blue font. + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'. + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.248.57 + +## Gateway control protocol: RTP control protocol package + +## Summary + +Recommendation ITU-T H.248.57 defines an ITU-T H.248 package for ephemeral terminations with real-time transport protocol-based streams and allows the media gateway controller to control the *handling* of real-time transport protocol control protocol (RTCP) traffic within the ITU-T H.248 stream. RTCP handling comprises functions such as the indication of whether an RTCP flow is used, resource management functions for specific RTCP resources and the allocation scheme of transport port values. + +This revision supports additional RTCP port allocation rules in the context of real-time transport protocol (RTP) transport multiplexing. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.248.57 | 2008-06-13 | 16 | 11.1002/1000/9483 | +| 2.0 | ITU-T H.248.57 | 2013-03-16 | 16 | 11.1002/1000/11861 | +| 3.0 | ITU-T H.248.57 | 2014-10-14 | 16 | 11.1002/1000/12239 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2015 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 1.1 | Overview ..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 3 | +| 6 | RTCP Handling Package ..... | 3 | +| 6.1 | Properties ..... | 3 | +| 6.2 | Events ..... | 4 | +| 6.3 | Signals ..... | 4 | +| 6.4 | Statistics..... | 4 | +| 6.5 | Error codes..... | 4 | +| 6.6 | Procedures ..... | 4 | +| 7 | Additional support of RTP transport multiplexing..... | 8 | +| 7.1 | Introduction ..... | 8 | +| 7.2 | Backward compatibility..... | 8 | +| 7.3 | Summary of rules according to IETF RFC 3550, IETF RFC 3605 and IETF RFC 5671 ..... | 9 | +| Annex A | – ITU-T H.248 profiles with and without support of RTCP Handling Package ..... | 16 | +| A.1 | Background..... | 16 | +| A.2 | ITU-T H.248 profiles without support of RTCP Handling Package..... | 16 | +| A.3 | ITU-T H.248 profiles with support of RTCP Handling Package..... | 16 | +| | Bibliography..... | 17 | + + + +# Recommendation ITU-T H.248.57 + +## Gateway control protocol: RTP control protocol package + +# 1 Scope + +This Recommendation contains functionality to describe the use of the real-time transport protocol control protocol (RTCP) in ITU-T H.248-controlled media gateways. RTCP is used, for example, to monitor the quality of service and to convey information about the participants in an on-going real-time transport protocol (RTP) session. + +[ITU-T H.248.1] assumes that when an RTP stream is specified in a local or remote descriptor, that an RTCP flow may be established according to the rules defined in section 11 of [IETF RFC 3550]. Additional ITU-T H.248/RTCP behaviour is defined in clause E.12.5 of [ITU-T H.248.1]. However, some media gateways may not instantiate an RTCP flow. For interoperability and for some applications such as firewall and network address translation (NAT), it is important for the media gateway controller (MGC) to be certain of the media gateway (MG) behaviour with respect to port allocation for RTCP. The "RTCP Handling Package" defined in this Recommendation provides a property to control this RTCP flow allocation. + +This revision supports additional RTCP port allocation rules in context of RTP transport multiplexing. + +## 1.1 Overview + +RTCP *handling* may comprise the following seven functions: + +- 1) Indication of the *existence* of an RTCP flow of an RTP session (RTP with or without RTCP). +- 2) Indication of *endpoint identifiers* on *RTP level* that are relevant for both RTP and RTCP (e.g., synchronization source (SSRC)). + +In addition, if an RTCP flow exists: + +- 3) Resource management of *endpoint identifiers* on *layer 4* (UDP ports; i.e., reservation, allocation and indication of a specific allocation rule) for RTCP flows. +- 4) Resource management of *endpoint identifiers* on *RTP level* (e.g., CNAME) for RTCP flows. +- 5) Resource management of *other resources* required for RTCP flows (e.g., reservation and allocation of transport capacity). +- 6) Indication of *specific modes of operation* for RTCP (e.g., layer 4 multiplexing of RTP and RTCP flows, or multiplexing mode of RTCP reports in a single RTCP packet). + +Orthogonal to the above functions: + +- 7) Mapping *scheme* of RTP and RTCP flows on ITU-T H.248 streams. + +This Recommendation deals with functions one and three only. Other functions are out of the scope of this Recommendation. + +In addition, this Recommendation assumes that regarding function seven, RTP and RTCP flows are always mapped into a single ITU-T H.248 stream. Other mapping schemes are out of the scope of this Recommendation and may make this Recommendation's procedures irrelevant. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*. +<> +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +<> +- [IETF RFC 3605] IETF RFC 3605 (2003), *Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)*. +<> +- [IETF RFC 4566] IETF RFC 4566 (2006), *SDP: Session Description Protocol*. +<> +- [IETF RFC 5761] IETF RFC 5761 (04/2010), *Multiplexing RTP Data and Control Packets on a Single Port*. +<> + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 RTCP flow:** The sending and reception of RTCP packets as described by section 6 of [IETF RFC 3550]. The RTCP flow relates to an "(ITU-T H.248) *control flow*" (see clause 3.2.9 of [ITU-T H.248.1]). + +NOTE – An RTCP flow comprises all RTCP traffic on an RTP session. An RTCP flow may be further separated into RTCP sub-flows due to different RTCP report types. An RTCP sub-flow is identified by a specific RTCP packet type codepoint. + +**3.2.2 RTP flow:** The sending and reception of RTP packets of an *RTP session*. The RTP flow relates to an "ITU-T H.248 *media flow*" (see [ITU-T H.248.1]). + +**3.2.3 RTP/RTCP transport multiplexing:** A single IP transport (L4) port for RTP and RTCP packets. + +NOTE – This term may be also referred to as "RTP transport multiplexing". + +**3.2.4 RTP session:** An RTP session comprises a single RTP flow and an optional RTCP flow. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------------------| +| AVP | Audio Visual Profile | +| ISDN | Integrated Services Digital Network | +| LD | Local Descriptor | +| LS | Local Source | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| NAT | Network Address Translation | +| PSTN | Public Switched Telephone Network | +| RD | Remote Descriptor | +| RS | Remote Source | +| RTCP | Real-time Transport protocol Control Protocol | +| RTP | Real-time Transport Protocol | +| SDP | Session Description Protocol | +| SSRC | Synchronization Source | + +# 5 Conventions + +None. + +# 6 RTCP Handling Package + +| | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | RTCP Handling Package | +| Package ID: | rtpch (0x00b5) | +| Description: | This package allows the MGC to indicate to the MG per stream whether or not to establish an RTCP control flow when an RTP media flow (e.g., for RTP profiles such as RTP/AVP, etc.) is created. | +| Version: | 1 | +| Extends: | None. | + +## 6.1 Properties + +### 6.1.1 RTCP Allocation Specific Behaviour + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------| +| Property name: | RTCP Allocation Specific Behaviour | +| Property ID: | rsb (0x0009) | +| Description: | This property indicates whether or not an RTCP flow and an associated port is automatically associated with an RTP flow. | +| Type: | Boolean | +| Possible values: | ON (an RTCP flow shall be allocated or de-allocated automatically with the creation or deletion of the RTP flow); | + +| | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------| +| | OFF (an RTCP flow shall not be allocated or de-allocated automatically with the creation or deletion of the RTP flow) | +| Default: | Provisioned | +| Defined in: | Local control | +| Characteristics: | Read/Write | + +## 6.2 Events + +None. + +## 6.3 Signals + +None. + +## 6.4 Statistics + +None. + +## 6.5 Error codes + +None. + +## 6.6 Procedures + +### 6.6.1 Reservation and allocation of layer 4 ports for RTP and RTCP + +The port number allocation rules, as defined by [IETF RFC 3550], are used as the starting point. + +#### 6.6.1.1 Overview – Four RTCP transport addresses + +Figure 1 shows a bidirectional RTP session with RTCP in each direction: there are thus four traffic flows. The RTP-based media flow and RTCP-based control flow sharing the same IP addresses (see Note regarding possible exceptions), but using normally different layer 4 (L4) (UDP) ports. These four RTCP ports are shown in Figure 1. + +NOTE – The session description protocol (SDP) attribute "a=rtcp:" also allows the explicit specification of an IP network address in addition to the layer 4 port. This may then lead to different IP addresses for RTP and RTCP flows. Figure 1 illustrates the particular case of identical IP addresses. + +![Diagram illustrating connection endpoint naming conventions for a bidirectional RTP/RTCP session between an H.248 media gateway and a peer entity. The diagram shows four types of endpoints: Local destination (LD), Local source (LS), Remote source (RS), and Remote destination (RD). Each endpoint is represented by a circle (L3 address) and a diamond (L4 port). Arrows indicate the flow of control (RTCP) and media (RTP) between these endpoints. A legend at the bottom defines the naming conventions and symbols used.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +The diagram shows the naming conventions for connection endpoints in a bidirectional RTP/RTCP session. It is divided into two main sections: the H.248 media gateway (left) and the Peer entity (right, e.g., RTP end system, RTP translator, RTP mixer). The media gateway contains four types of endpoints: Local Destination (LD), Local Source (LS), Remote Source (RS), and Remote Destination (RD). Each endpoint is represented by a circle (L3 address) and a diamond (L4 port). Arrows indicate the flow of control (RTCP) and media (RTP) between these endpoints. A legend at the bottom defines the naming conventions and symbols used. + +**Names:** + +- LD Local Destination +- LS Local Source +- RD Remote Destination +- RS Remote Source + +**Addresses:** + +- DA Destination Address +- DP Destination Port +- SA Source Address +- SP Source Port + +**Symbols:** + +- Circle: L3 address +- Diamond: L4 port + +Diagram illustrating connection endpoint naming conventions for a bidirectional RTP/RTCP session between an H.248 media gateway and a peer entity. The diagram shows four types of endpoints: Local destination (LD), Local source (LS), Remote source (RS), and Remote destination (RD). Each endpoint is represented by a circle (L3 address) and a diamond (L4 port). Arrows indicate the flow of control (RTCP) and media (RTP) between these endpoints. A legend at the bottom defines the naming conventions and symbols used. + +**Figure 1 – Connection endpoint naming conventions – the four RTCP ports of a bidirectional RTP/RTCP session** + +#### 6.6.1.2 Specific behaviour "activated" + +If the MGC sets the `rtcph/rsb` property to "ON", when the MG is requested to allocate/de-allocate a local destination port for an RTP stream, a consecutive port for the reception of the associated RTCP flow is automatically allocated/de-allocated. + +#### 6.6.1.3 Specific behaviour "deactivated" + +If the MGC sets the `rtcph/rsb` property to "OFF", then only a single port is allocated to the RTP stream and no RTCP flow is assumed to exist for the stream. + +#### 6.6.1.4 Precedence of `rtcph/rsb` property over other port allocation mechanisms + +The setting of the `rtcph/rsb` property in general takes precedence over any values set in the local and remote descriptors with regard to port allocation for RTP streams. However, there is one exception: if the `rtcph/rsb` property is set to ON and a specific RTCP transport address is provided in the local and/or remote descriptor, e.g., using SDP `"a=rtcp:"` attribute as defined in [IETF RFC 3605], the RTCP packets should use the transport addresses indicated by the local/remote descriptors. + +##### 6.6.1.4.1 Notes to SDP attribute `"a=rtcp"` + +Within the scope of this Recommendation, it is noted that: + +- the SDP attribute `"a=rtcp:"` also allows the explicit specification of an IP network address in addition to the layer 4 port; and that, +- this SDP attribute may also principally be used in the ITU-T H.248 local descriptor (LD) in addition to its usage in the ITU-T H.248 remote descriptor (RD). + +Note that both the IP address and the port number appearing in the "a=rtcp:" attribute may be underspecified. When this is the case, the MG is free to allocate any transport address to the RTCP flow (i.e., not necessarily using the same IP address as the RTP flow). + +#### 6.6.1.5 Summary of basic rules according to IETF RFC 3550 and IETF RFC 3605 + +Table 1 provides a summary of the port allocation rules for RTCP. + +**Table 1 – Allocation rules for RTCP ports with IETF RFC 3550 +(with and without IETF RFC 3605 attribute)** + +| ITU-T H.248 property value | "a=rtcp" sent to MG? | Local endpoints | | Remote endpoints | | +|----------------------------|----------------------|--------------------------------------------------------------|----------------------------|---------------------------------------------------------------|--------------| +| | | LD(A, P) | LS(A, P) | RD(A, P) | RS(A, P) | +| rsb = "ON" | No | Consecutive port to the one indicated by the local descript. | MG (Note 1) | Consecutive port to the one indicated by the remote descript. | Out of scope | +| | Yes in H.248 LD | "a=rtcp" port | MG (Note 1) | – | – | +| | Yes in H.248 RD | – | – | "a=rtcp:" port | Out of scope | +| rsb = "OFF" | No | No port allocated | No port allocated | No port allocated | Out of scope | +| | Yes in H.248 LD | No port allocated (Note 2) | No port allocated (Note 2) | No port allocated (Note 2) | Out of scope | +| | Yes in H.248 RD | No port allocated (Note 2) | No port allocated (Note 2) | No port allocated (Note 2) | Out of scope | + +NOTE 1 – The management of LS(A) and LS(P) resources is under control of the MG. The MG shall apply the "consecutive" port allocation rule. +NOTE 2 – This is a semantic contradiction, however the MG shall ignore the "a=rtcp:" attribute. + +#### 6.6.1.6 Additional rules due to "number of port" qualifier according to IETF RFC 4566 + +[IETF RFC 4566] defines the "number of port" qualifier for the SDP "m=" line used to specify multiple transport ports. The RTCP port allocation rules (see Note) are also provided by [IETF RFC 4566] in the case of RTP-based media. The "number of port" qualifier indicates the number of RTP/RTCP flow pairs for a single ITU-T H.248 stream. + +NOTE – Section 5.14 of [IETF RFC 4566] states that "In such a case, the ports used depend on the transport protocol. For RTP, the default is that only the even-numbered ports are used for data with the corresponding one-higher odd ports used for the RTCP belonging to the RTP session, and the denoting the number of RTP sessions " ... " If non-contiguous ports are required, they must be signalled using a separate attribute (for example, "a=rtcp:" as defined in ...)" + +RTCP port values shall thus be odd numbers, also in case of "a=rtcp" usage. This Recommendation does suppose a single SDP "a=rtcp" attribute per SDP media description ("m=" line) when [IETF RFC 3605] is used. + +Table 2 provides a summary of these rules in conjunction with the rsb property. + +**Table 2 – Allocation rules for RTCP ports for RTP applications using SDP "number of port" qualifier** + +| ITU-T H.248 property value | "a=rtcp" sent to MG? | Local endpoints | | Remote endpoints | | +|----------------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| | | LD(A, P) | LS(A, P) | RD(A, P) | RS(A, P) | +| rsb = "ON" | No | Consecutive port to the one indicated by the local descript. (for the first pair) plus rule "contiguous (odd) for each further RTP/RTCP pair" | See Table 1 | Consecutive port to the one indicated by the remote descript. (for the first pair) plus rule "contiguous (odd) for each further RTP/RTCP pair" | See Table 1 | +| | Yes in H.248 LD | "a=rtcp:" port (for the first RTP/RTCP pair) plus rule "contiguous (odd) for each further RTP/RTCP pair" (Note 1) | See Table 1 | – | – | +| | Yes in H.248 RD | – | – | "a=rtcp:" port (for the first RTP/RTCP pair) plus rule "contiguous (odd) for each further RTP/RTCP pair" (Note 2) | See Table 1 | +| rsb = "OFF" | No | See Table 1 | See Table 1 | See Table 1 | See Table 1 | +| | Yes in H.248 LD | See Table 1 | See Table 1 | See Table 1 | See Table 1 | +| | Yes in H.248 RD | See Table 1 | See Table 1 | See Table 1 | See Table 1 | + +NOTE 1 – If both 'number of ports' and "a=rtcp:" are indicated in the LD, the RTCP port of the first pair is allocated according to the "a=rtcp:" and the RTP port of the next pair takes the one-higher value to the RTCP port of the last pair. The RTCP port of the next pair takes the consecutive higher number to the RTP port. + +NOTE 2 – If both 'number of ports' and "a=rtcp:" are indicated in the RD, the RTCP port of the first pair is allocated according to the "a=rtcp:" and the RTP port of the next pair takes the one-higher value to the RTCP port of the last pair. The RTCP port of the next pair takes the consecutive higher number to the RTP port. + +### 6.6.2 RTP sessions with or without an RTCP flow (existence of RTCP flow) + +RTCP is fundamentally optional for RTP. + +#### 6.6.2.1 Indication of the existence of RTCP per ITU-T H.248 stream or termination + +As the use of RTCP is optional, the default behaviour of an MG as to the use of RTCP flows is not described in [ITU-T H.248.1]. The default behaviour could be, e.g., defined in an ITU-T H.248 profile specification (see, e.g., template clauses for connection model, stream descriptor or SDP information elements in Appendix III of [ITU-T H.248.1]). + +The usage protocol elements (e.g., such as the ITU-T H.248 *rtcp/rsb* property, or ITU-T H.248 statistics on RTCP basis, or RTCP-specific SDP information elements according to [b-IETF RFC 3556], [IETF RFC 3605] or [b-IETF RFC 3890]) in ITU-T H.248 commands, which provide an indication of RTCP, shall overrule the default behaviour. + +#### **6.6.2.2 RTCP-less RTP sessions** + +No UDP port (or other resources) for RTCP will be reserved. + +#### **6.6.2.3 RTP sessions with RTCP** + +Handling of RTCP shall follow the guidelines of this Recommendation. + +### **6.6.3 Mapping of RTP and RTCP flows on ITU-T H.248 streams** + +#### **6.6.3.1 Mapping schemes** + +##### **6.6.3.1.1 Single ITU-T H.248 stream for RTP and RTCP** + +The default assumption is that an RTP/RTCP session is mapped on a single ITU-T H.248 stream. + +NOTE – This is based on clause E.12 of [ITU-T H.248.1] (in case of usage for ITU-T H.248 RTP terminations) and the reference on RTP profile "RTP/AVP" according to [IETF RFC 3550]. The default media description (e.g., by SDP information elements) for media types/formats for media transport "RTP/AVP" does not explicitly specify RTCP. RTCP is implicitly part of the same ITU-T H.248 stream as for RTP per default. + +##### **6.6.3.1.2 Individual ITU-T H.248 streams for RTP and RTCP** + +An individual ITU-T H.248 stream, solely for RTCP traffic, could be used in principle. Although, it is so far not possible to provide sufficient information within the ITU-T H.248 stream descriptor for "comprehensive" specification of RTCP flows. + +Such an individual ITU-T H.248 stream could be characterized by the 2-tuples of IP address and port (which is not really specific for RTCP). + +#### **6.6.3.2 Mapping control** + +Mapping control is subject of the usage and capabilities of the ITU-T H.248 stream descriptor. There are no protocol means presently available for the individual stream mapping mode. + +The *rtcp/rsb* property shall not be used to influence the mapping between RTP and RTCP flows on ITU-T H.248 streams. + +# **7 Additional support of RTP transport multiplexing** + +## **7.1 Introduction** + +The use of RTP transport multiplexing is indicated by the MGC towards the MG via the SDP attribute "*a=rtcp-mux*" [IETF RFC 5761] in the ITU-T H.248 LD and/or RD. RTP transport multiplexing may be used in addition to the existing capabilities of the RTCP Handling Package (see clause 6). + +## **7.2 Backward compatibility** + +In order to ensure backward compatibility in ITU-T H.248 profiles with existing support of the RTCP Handling Package, possible interactions between RTCP port allocation rules according to [IETF RFC 3550], [IETF RFC 3605] and [IETF RFC 5761] must be considered. + +Table 3 below provides a summary of all rules for interaction resolution. + +**Table 3 – Overview of applied rules for resolving interaction issues** + +| Interaction resolution rule | | Comment | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------| +| R0 | If ITU-T H.248 " rtcph/rsb " property value 'OFF', then the SDP attribute " a=rtcp " sent by the MGC shall be ignored by the MG. | Existing rule, see Note 2/Table 1 | +| R1 | If " rtcph/rsb " is omitted, then the provisioned default value applies, which either is value "ON" or "OFF". | See Annex A for more information. | +| R2 | SDP attribute " a=rtcp-mux " modifies ITU-T H.248 " rtcph/rsb " property to value 'ON'. | If not, RTCP transport multiplexing couldn't be supported. | +| R3 | SDP attribute " a=rtcp-mux " overrules SDP attribute " a=rtcp ". | In line with [IETF RFC 5761]. | +| R4 | If ITU-T H.248 " rtcph/rsb " property value 'OFF' overrules SDP attribute " a=rtcp-mux ", i.e., then the SDP attribute " a=rtcp-mux " sent by the MGC shall be ignored by the MG. | In order to preserve basic rtcph semantics. | + +## 7.3 Summary of rules according to IETF RFC 3550, IETF RFC 3605 and IETF RFC 5671 + +The rules according to [IETF RFC 3550], [IETF RFC 3605] and [IETF RFC 5671] are distributed over the five tables, Tables 4-a to 4-e. and can be summarized as follows, for quick reference: + +- Table 4-a: combinations of "*a=rtcp-mux*" and *rsb* = "ON" without "*a=rtcp*"; +- Table 4-b: combinations of "*a=rtcp-mux*" and *rsb* = "ON" with "*a=rtcp*" in ITU-T H.248 LD; +- Table 4-c: combinations of "*a=rtcp-mux*" and *rsb* = "ON" with "*a=rtcp*" in ITU-T H.248 RD; +- Table 4-d: combinations of "*a=rtcp-mux*" and *rsb* = "ON" with "*a=rtcp*" in ITU-T H.248 LD and RD; +- Table 4-e: all combinations with *rsb* = "OFF". + +**Table 4-a – Rules according to IETF RFC 3550, IETF RFC 3605 and IETF RFC 5671 – Part 1/5** + +| H.248 rsb property value | "a=rtcp" sent to MG? | "a=rtcp-mux" sent to MG? | Local endpoints | | Remote endpoints | | +|--------------------------|----------------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| | | | LD(A, P) | LS(A, P) | RD(A, P) | RS(A, P) | +| omitted | | | If rtcp/rtcp-mux is omitted, then the provisioned default value applies, which is either "ON" or "OFF". Thus, then corresponding rows below apply. | | | | +| rsb = "ON" | No | No | Consecutive port to the one indicated by the local descript. m-line,
$LD(A)_{RTCP} = LD(A)_{RTP}$
$LD(P)_{RTCP} = LD(P)_{RTP} + 1$ | MG (Note 1), where
$LS(A)_{RTCP} = LS(A)_{RTP}$
$LS(P)_{RTCP} = LS(P)_{RTP} + 1$
Typically also:
$LS(A,P)_{RTP} = LD(A,P)_{RTP}$
$LS(A,P)_{RTCP} = LD(A,P)_{RTCP}$ | Consecutive port to the one indicated by the remote descript. m-line,
$RD(A)_{RTCP} = RD(A)_{RTP}$
$RD(P)_{RTCP} = RD(P)_{RTP} + 1$ | Out of scope | +| | | Yes in H.248 LD | $LD(A,P)_{RTCP} = LD(A,P)_{RTP}$ | MG (Note 1), where
$LS(A,P)_{RTCP} = LS(A,P)_{RTP}$
Typically also:
$LS(A,P)_{RTCP} = LD(A,P)_{RTCP}$
$= LD(A,P)_{RTP} = LS(A,P)_{RTP}$ | Consecutive port to the one indicated by the remote descript. m-line,
$RD(A)_{RTCP} = RD(A)_{RTP}$
$RD(P)_{RTCP} = RD(P)_{RTP} + 1$ | Out of scope | +| | | Yes in H.248 RD | $LD(A)_{RTCP} = LD(A)_{RTP}$
$LD(P)_{RTCP} = LD(P)_{RTP} + 1$ | MG (Note 1), where
$LS(A)_{RTCP} = LS(A)_{RTP}$
$LS(P)_{RTCP} = LS(P)_{RTP} + 1$
Typically also:
$LS(A,P)_{RTP} = LD(A,P)_{RTP}$
$LS(A,P)_{RTCP} = LD(A,P)_{RTCP}$ | $RD(A,P)_{RTCP} = RD(A,P)_{RTP}$ | Out of scope | +| | | Yes in H.248 LD & RD | $LD(A,P)_{RTCP} = LD(A,P)_{RTP}$ | MG (Note 1), where
$LS(A,P)_{RTCP} = LS(A,P)_{RTP}$
Typically also:
$LS(A,P)_{RTCP} = LD(A,P)_{RTCP}$
$= LD(A,P)_{RTP} = LS(A,P)_{RTP}$ | $RD(A,P)_{RTCP} = RD(A,P)_{RTP}$ | Out of scope | + +**Table 4-b – Rules according to IETF RFC 3550, IETF RFC 3605 and IETF RFC 5671 – Part 2/5** + +| H.248 rsb property value | "a=rtp" sent to MG? | "a=rtp-mux" sent to MG? | Local endpoints | | Remote endpoints | | +|--------------------------|---------------------|-------------------------|-----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------| +| | | | LD(A, P) | LS(A, P) | RD(A, P) | RS(A, P) | +| rsb = "ON" | Yes in H.248 LD | No | LD(A) RTCP = LD(A) RTP
LD(P) RTCP = "a=rtp" value | MG (Note 1), where
LS(A) RTCP = LS(A) RTP
Typically also:
LS(A,P) RTCP =
LD(A,P) RTCP | RD(A) RTCP = RD(A) RTP
RD(P) RTCP = RD(P) RTP + 1 | Out of scope | +| | | Yes in H.248 LD | LD(A,P) RTCP = LD(A,P) RTP
(rule R2 ("a=rtp-mux" overrules "a=rtp")) | MG (Note 1), where
LS(A,P) RTCP = LS(A,P) RTP
Typically also:
LS(A,P) RTCP =
LD(A,P) RTCP = LD(A,P) RTP
= LS(A,P) RTP | RD(A) RTCP = RD(A) RTP
RD(P) RTCP = RD(P) RTP + 1 | Out of scope | +| | | Yes in H.248 RD | LD(A) RTCP = LD(A) RTP
LD(P) RTCP = "a=rtp" value | MG (Note 1), where
LS(A) RTCP = LS(A) RTP
Typically also:
LS(P) RTCP = "a=rtp" port
LS(A,P) RTCP =
LD(A,P) RTCP | RD(A,P) RTCP = RD(A,P) RTP | Out of scope | +| | | Yes in H.248 LD & RD | LD(A,P) RTCP = LD(A,P) RTP
(rule R2 ("a=rtp-mux" overrules "a=rtp")) | MG (Note 1), where
LS(A,P) RTCP = LS(A,P) RTP
Typically also:
LS(A,P) RTCP =
LD(A,P) RTCP = LD(A,P) RTP
= LS(A,P) RTP | RD(A,P) RTCP = RD(A,P) RTP | Out of scope | + +**Table 4-c – Rules according to IETF RFC 3550, IETF RFC 3605 and IETF RFC 5671 – Part 3/5** + +| H.248 rsb property value | "a=rtcp" sent to MG? | "a=rtcp-mux" sent to MG? | Local endpoints | | Remote endpoints | | +|--------------------------|----------------------|--------------------------|--------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------| +| | | | LD(A, P) | LS(A, P) | RD(A, P) | RS(A, P) | +| rsb = "ON" | Yes in H.248 RD | No | LD(A) RTCP = LD(A) RTP
LD(P) RTCP = LD(P) RTP + 1 | MG (Note 1), where
LS(A) RTCP = LS(A) RTP
LS(P) RTCP = LS(P) RTP + 1
Typically also:
LS(A,P) RTP = LD(A,P) RTP
LS(A,P) RTCP = LD(A,P) RTCP | RD(A) RTCP = RD(A) RTP
RD(P) RTCP = "a=rtcp:" port | Out of scope | +| | | Yes in H.248 LD | LD(A,P) RTCP = LD(A,P) RTP | MG (Note 1), where
LS(A,P) RTCP = LS(A,P) RTP
Typically also:
LS(A,P) RTCP = LD(A,P) RTCP
LS(A,P) RTCP = LS(A,P) RTP | RD(A) RTCP = RD(A) RTP
RD(P) RTCP = "a=rtcp:" port | Out of scope | +| | | Yes in H.248 RD | LD(A) RTCP = LD(A) RTP
LD(P) RTCP = LD(P) RTP + 1 | MG (Note 1), where
LS(A) RTCP = LS(A) RTP
LS(P) RTCP = LS(P) RTP + 1
Typically also:
LS(A,P) RTP = LD(A,P) RTP
LS(A,P) RTCP = LD(A,P) RTCP | RD(A,P) RTCP = RD(A,P) RTP
(rule R2 ("a=rtcp-mux" overrules "a=rtcp")) | Out of scope | +| | | Yes in H.248 LD & RD | LD(A,P) RTCP = LD(A,P) RTP | MG (Note 1), where
LS(A,P) RTCP = LS(A,P) RTP
Typically also:
LS(A,P) RTCP = LD(A,P) RTCP
LS(A,P) RTCP = LS(A,P) RTP | RD(A,P) RTCP = RD(A,P) RTP
(rule R2 ("a=rtcp-mux" overrules "a=rtcp")) | Out of scope | + +**Table 4-d – Rules according to IETF RFC 3550, IETF RFC 3605 and IETF RFC 5671 – Part 4/5** + +| H.248 rsb property value | "a=rtp" sent to MG? | "a=rtcp-mux" sent to MG? | Local endpoints | | Remote endpoints | | +|--------------------------|----------------------|--------------------------|-------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------| +| | | | LD(A, P) | LS(A, P) | RD(A, P) | RS(A, P) | +| rsb = "ON" | Yes in H.248 LD & RD | No | LD(A) RTCP = LD(A) RTP
LD(P) RTCP = "a=rtcp:" port | MG (Note 1), where
LS(A) RTCP = LS(A) RTP
Typically also:
LS(A,P) RTCP =
LD(A,P) RTCP | RD(A) RTCP = RD(A) RTP
RD(P) RTCP = "a=rtcp:" port | Out of scope | +| | | Yes in H.248 LD | LD(A,P) RTCP = LD(A,P) RTP
(rule R2 ("a=rtcp-mux" overrules "a=rtcp")) | MG (Note 1), where
LS(A,P) RTCP = LS(A,P) RTP
Typically also:
LS(A,P) RTCP =
LD(A,P) RTCP = LD(A,P) RTP
= LS(A,P) RTP | RD(A) RTCP = RD(A) RTP
RD(P) RTCP = "a=rtcp:" port | Out of scope | +| | | Yes in H.248 RD | LD(A) RTCP = LD(A) RTP
LD(P) RTCP = "a=rtcp:" port | MG (Note 1), where
LS(A) RTCP = LS(A) RTP
Typically also:
LS(A,P) RTCP =
LD(A,P) RTCP | RD(A,P) RTCP = RD(A,P) RTP
(rule R2 ("a=rtcp-mux" overrules "a=rtcp")) | Out of scope | +| | | Yes in H.248 LD & RD | LD(A,P) RTCP = LD(A,P) RTP
(rule R2 ("a=rtcp-mux" overrules "a=rtcp")) | MG (Note 1), where
LS(A,P) RTCP = LS(A,P) RTP
Typically also:
LS(A,P) RTCP =
LD(A,P) RTCP = LD(A,P) RTP
= LS(A,P) RTP | RD(A,P) RTCP = RD(A,P) RTP
(rule R2 ("a=rtcp-mux" overrules "a=rtcp")) | Out of scope | + +**Table 4-e – Rules according to IETF RFC 3550, IETF RFC 3605 and IETF RFC 5671 – Part 5/5** + +| H.248 rsb property value | "a=rtpc" sent to MG? | "a=rtcp-mux" sent to MG? | Local endpoints | | Remote endpoints | | +|--------------------------|----------------------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------| +| | | | LD(A, P) | LS(A, P) | RD(A, P) | RS(A, P) | +| rsb = "OFF" | No | No | No port allocated | No port allocated | No port allocated | Out of scope | +| | | Yes in H.248 LD | No port allocated (Note 3) | No port allocated (Note 3) | No port allocated (Note 3) | Out of scope | +| | | Yes in H.248 RD | No port allocated (Note 3) | No port allocated (Note 3) | No port allocated (Note 3) | Out of scope | +| | | Yes in H.248 LD & RD | No port allocated (Note 3) | No port allocated (Note 3) | No port allocated (Note 3) | Out of scope | +| | Yes in H.248 LD | No | No port allocated (Note 2) | No port allocated (Note 2) | No port allocated (Note 2) | Out of scope | +| | | Yes in H.248 LD | No RTCP control flow at all, thus:
No port allocated (Note 3)
(rule R2 ("rsb=OFF" overrules SDP attribute "a=rtcp-mux")) | No port allocated (Note 3) | No port allocated (Note 2) | Out of scope | +| | | Yes in H.248 RD | No port allocated (Note 2) | No port allocated (Note 2) | No port allocated (Note 3) | Out of scope | +| | | Yes in H.248 LD & RD | No port allocated (Notes 2, 3) | No port allocated (Notes 2, 3) | No port allocated (Note 3) | | +| | Yes in H.248 RD | No | No port allocated | No port allocated | No port allocated (Note 2) | Out of scope | +| | | Yes in H.248 LD | No port allocated (Note 3) | No port allocated (Note 3) | No port allocated (Note 2) | Out of scope | +| | | Yes in H.248 RD | No port allocated | No port allocated | No RTCP control flow at all, thus:
No port allocated (Notes 2, 3) (rule R2 ("rsb=OFF" overrules SDP attribute "a=rtcp-mux")) | Out of scope | +| | | Yes in H.248 LD & RD | No port allocated (Note 3) | No port allocated (Note 3) | No port allocated (Notes 2, 3) | Out of scope | + +**Table 4-e – Rules according to IETF RFC 3550, IETF RFC 3605 and IETF RFC 5671 – Part 5/5** + +| H.248 rsb property value | "a=rtp" sent to MG? | "a=rtp-mux" sent to MG? | Local endpoints | | Remote endpoints | | +|--------------------------|----------------------|-------------------------|--------------------------------|--------------------------------|--------------------------------|--------------| +| | | | LD(A, P) | LS(A, P) | RD(A, P) | RS(A, P) | +| | Yes in H.248 LD & RD | No | No port allocated (Note 2) | No port allocated (Note 2) | No port allocated (Note 2) | Out of scope | +| | | Yes in H.248 LD | No port allocated (Notes 2, 3) | No port allocated (Notes 2, 3) | No port allocated (Note 2) | Out of scope | +| | | Yes in H.248 RD | No port allocated (Note 2) | No port allocated (Note 2) | No port allocated (Notes 2, 3) | Out of scope | +| | | Yes in H.248 LD & RD | No port allocated (Notes 2, 3) | No port allocated (Notes 2, 3) | No port allocated (Notes 2, 3) | Out of scope | + +Common notes for Tables 4-a to 4-e: + +NOTE 1 –The management of LS(A) and LS(P) resources is under control of the media gateway unless the MGC explicitly adds "gm/esas = ON" and/or "gm/lsps = ON" and signals corresponding local source address and/or port. + +In such a case there might be an inconsistency if "a=rtp:x" is present in the LD and if "gm/esps = ON" and "gm/lsp=y" with "x ≠ y" are present in LocalControl. This potential inconsistency is not further investigated in this Recommendation. + +NOTE 2 – This is a semantic contradiction, however the MG shall ignore the "a=rtp:" attribute. + +NOTE 3 – This is a semantic contradiction, however the MG shall ignore the "a=rtp-mux" attribute. + +# Annex A + +## ITU-T H.248 profiles with and without support of RTCP Handling Package + +(This annex forms an integral part of this Recommendation.) + +## A.1 Background + +There are ITU-T H.248 profiles with and without support of the *RTCP Handling Package* for ITU-T H.248 media gateways with RTP bearer traffic. Only such MG types are in scope of this Recommendation. + +## A.2 ITU-T H.248 profiles without support of RTCP Handling Package + +Historically, all ITU-T H.248 profiles related to MG types with scope on "physical-to-RTP" interworking – such as public switched telephone network (PSTN)/integrated services digital network (ISDN) residential, access and trunking gateways – were defined without usage of the *RTCP Handling Package*. An RTCP port was always and implicitly allocated based on the "N+1" rule, independent whether RTCP was finally used or not. + +However, the *RTCP Handling Package* could also be added to such ITU-T H.248 profiles, as well as SDP elements for RTCP port allocation control. + +This Recommendation takes into account such kind of possible profile upgrade scenarios. + +## A.3 ITU-T H.248 profiles with support of RTCP Handling Package + +The *RTCP Handling Package* was produced when the first ITU-T H.248 profiles for IP-IP MGs were defined. These MGs support multiple modes of operation concerning bearer traffic handling, particularly the so-called media-agnostic (RTP unaware) mode which created the demand for an explicit signalling element concerning the reservation and allocation of two IP transport connection endpoints for the two flow components of the ITU-T H.248 stream. + +This Recommendation takes into account these types of possible profile upgrade scenarios. + +# Bibliography + +- [b-IETF RFC 3551] IETF RFC 3551 (2003), *RTP Profile for Audio and Video Conferences with Minimal Control*. +<> +- [b-IETF RFC 3556] IETF RFC 3556 (2003), *Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth*. +<> +- [b-IETF RFC 3890] IETF RFC 3890 (2004), *A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)*. +<> + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.63-200903-I_PDF-E/raw.md b/marked/H/T-REC-H.248.63-200903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..772d37ec68c1a5e9cfbb50757ab7bea95464a83c --- /dev/null +++ b/marked/H/T-REC-H.248.63-200903-I_PDF-E/raw.md @@ -0,0 +1,584 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.63** + +(03/2009) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: Resource management packages** + +Recommendation ITU-T H.248.63 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T H.248.63** + +# **Gateway control protocol: Resource management packages** + +## **Summary** + +Recommendation ITU-T H.248.63 contains packages that allow a media gateway controller (MGC) and media gateway (MG) to work together to allow a MG to manage its resources in the most efficient manner possible. It allows the MGC to indicate which resources may be used in the Context and whether the use of certain resources will change or not for the life of the Termination/Stream. The MG can then use this information to optimize the allocation and use of resources. + +## **Source** + +Recommendation ITU-T H.248.63 was approved on 16 March 2009 by ITU-T Study Group 16 (2009-2012) under Recommendation ITU-T A.8 procedures. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|----------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Resource management interactions ..... | 2 | +| 6.1 Interaction with related H.248 Recommendations ..... | 3 | +| 7 Resource management rules package ..... | 4 | +| 7.1 Properties..... | 5 | +| 7.2 Events ..... | 5 | +| 7.3 Signals ..... | 6 | +| 7.4 Statistics..... | 6 | +| 7.5 Error codes..... | 6 | +| 7.6 Procedures ..... | 6 | +| 8 Resource management configuration package ..... | 7 | +| 8.1 Properties..... | 7 | +| 8.2 Events ..... | 8 | +| 8.3 Signals ..... | 8 | +| 8.4 Statistics..... | 8 | +| 8.5 Error codes..... | 8 | +| 8.6 Procedures ..... | 8 | +| 9 Abstract resource management package..... | 9 | +| 9.1 Properties..... | 9 | +| 9.2 Events ..... | 10 | +| 9.3 Signals ..... | 10 | +| 9.4 Statistics..... | 10 | +| 9.5 Error Codes..... | 10 | +| 9.6 Procedures ..... | 10 | +| Bibliography..... | 12 | + + + +# Gateway control protocol: Resource management packages + +# 1 Scope + +This Recommendation contains packages that allow a media gateway controller (MGC) and a media gateway (MG) to work together to allow the MG to manage its resources in the most efficient manner possible. Three approaches are defined: rules-based, configuration, and abstract. + +In the rules-based approach, the MG expects the MGC to behave in a particular manner in order to manage resources. For example, the MG may expect that, for optimal resource allocation, once a stream is assigned to a particular media (e.g., audio), it will not change it to another media (e.g., video). + +In the configuration approach, the MGC indicates the expected characteristics of the Context in terms of the actual resources required. This could be a number of a particular type of Termination. For example, the MGC could indicate that for a particular Context, it may have up to five receive-only Terminations. + +An "abstract" approach is also provided, whereby the MGC indicates a specific resource management requirement via a single codepoint which then relates directly to a particular H.248 configuration. For example, the MGC could indicate "conference listener" and this would then map directly to a send-only Termination configuration and to a particular type of audio codec. + +The description of MG internal resource structures is out of scope of this Recommendation. + +This Recommendation assumes that the MGC is responsible for determining for how long the resources are reserved, and thus is responsible for requesting and clearing the resources. This is in keeping with the H.248 LocalControl descriptor ReserveGroup/ReserveValue functionality. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway Control Protocol: Version 3*. +- [ITU-T H.248.19] Recommendation ITU-T H.248.19 (2004), *Gateway control protocol: Decomposed multipoint control unit, audio, video and data conferencing packages*. +- [ITU-T H.248.32] Recommendation ITU-T H.248.32 (2005), *Gateway control protocol: Detailed congestion reporting package*. +- [ITU-T H.248.39] Recommendation ITU-T H.248.39 (2006), *Gateway control protocol: H.248 SDP parameter identification and wildcarding*. +- [ITU-T H.248.46] Recommendation ITU-T H.248.46 (2007), *Gateway control protocol: Connection capability control package*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 MG resource:** This is a generic term that describes physical or logical entities in a MG used by the MG to perform a certain function. These resources could be but are not limited to processor resources, memory resources, system resources, and digital signal processor resources. + +**3.2.2 resource management rule:** This is a generic term to describe a set of procedures/H.248 actions that a MG expects a MGC to adopt in order to optimize resources. The terms "rule" or "rules" are used in this Recommendation to mean "Resource Management Rule". + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------| +| ABNF | Augmented Backus-Naur Form | +| AMR | Adaptive Multi-Rate | +| ASN.1 | Abstract Syntax Notation One | +| BHCoA | Busy Hour Context Attempts | +| Cxt | Context | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| Tid | Termination Identifier | + +# 5 Conventions + +None. + +# 6 Resource management interactions + +A MG only has a finite set of resources that may be committed in order to satisfy requests from its MGC. In some instances, the use of resource management mechanisms provides a means for the MG to optimize how it assigns and uses resources. How the MG actually assigns physical resources at the time of the request may result in poor performance as resources are being held without being used. This may limit the number of MGC requests that can be satisfied. In some usage scenarios, the resource availability may be reduced if implementations reserve resources in advance of their use in order to ensure they are available for a given call. This would particularly occur where such resources are dimensioned based on a pooling or timeshare concept. Therefore, the balance between reservation and availability should also be considered. As such, the use of the packages in this Recommendation does not negate the need for correct network dimensioning. When dimensioning a network, the type of calls and their percentage of the overall traffic need to be taken into account. However, the proper usage of the packages in this Recommendation leads to better resource availability allowing certain services to be more reliable. + +In packages using a rules-based approach (i.e., Resource Management Rules package, *rmr*) in conjunction with network dimensioning, the MG can optimize its resource allocation/usage according to the specified rule. + +In packages using a configuration approach (i.e., Resource Management Configuration package, *rmc*), the MG receives an indication of what resources are likely to be used for a particular Context. When combined with dimensioning, it allows the MG to optimize the resource availability pools. The configuration approach can be applied at any time during call establishment. Thus, the configuration applied may be based on a particular service. Indicating resources at call establishment is unlikely to have a detrimental effect on available resources because, if there are any unused resources, they may be cleared when the call/session reaches a steady state. In cases where the steady state may be determined and the resources may be freed, if used correctly, the packages will have little detrimental effect on pooling or dimensioning, and will enhance resource availability for a particular connection. In other cases, the use of the packages needs to be considered against potential pooling or dimensioning issues as it may lead to an increase in the utilization of the resources. + +In packages using an abstraction approach (i.e., Abstract Resource Management package, *arm*), an indication is used to describe a general set of behaviour. This is used to allow the MG to optimize resources based on a certain service need. Given that [ITU-T H.248.1] already permits a level of detachment from the MGC call level service description and of the implementation of resources in the MG, the abstraction codepoints are accompanied by a "Resource mapping Description" and "Procedures" to ensure that the usage is clear. + +The packages in this Recommendation assume the MG uses the information in the packages to optimize its resource allocation and processing. It is assumed that the MG will only commit physical resources when descriptors of the H.248 commands indicate so. As a result, Context priority handling procedures should not be modified as a result of the packages in this Recommendation. + +## 6.1 Interaction with related H.248 Recommendations + +### 6.1.1 Core gateway control protocol (H.248.1) + +The [ITU-T H.248.1] protocol has resource reservation capabilities defined in its core behaviour. The "Reserve Value" and "Reserve Group" properties of the LocalControl Descriptor allow a MGC to request a MG to reserve resources for all alternatives specified in the Local and/or Remote Descriptors for which it currently has resources available. This allows an MGC during call establishment to reserve resources in order to negotiate the media properties and then later remove the unnecessary resources once the call reaches steady state. Likewise, the Resource Management Configuration (*rmc*) package allows the MGC to reserve resources (in addition to Local and Remote resources) which may then be later released if they are unnecessary when the call reaches steady state. + +### 6.1.2 Decomposed multipoint control unit, audio, video and data conferencing (H.248.19) + +[ITU-T H.248.19] currently describes the interface between the MGC and the MG in a decomposed multipoint control unit which largely provides conferencing services. There is currently no discussion in [ITU-T H.248.19] regarding resource management. However, there exists scope for optimizing resource usage for conferencing scenarios. + +Conference resources can be reserved at conference booking in order to enhance the availability of resources for the participants. For example, the ASCI Group Call package [b-3GPP TS 29.232] allows the reservation of a number of conference Terminations. Further description of the resources may be achieved through the Resource Management Configuration (*rmc*) package. + +MG resource allocations may also be optimized through the prior knowledge of the characteristics of a Termination. For example, if the MG is aware that a Termination will only represent a "Listenonly" (see clause 9.6.1) participant through the Abstract Resource Management (*arm*) package, at conference establishment it can assign resources to a "send" direction, thus leaving the resources that would be associated with the "receive" direction free to be used elsewhere in the MG. + +If the indication of resource optimization prior to resource allocation is not possible (i.e., upon allocation through an H.248 Add, Modify or Move command), then the Resource Management Rules (*rmr*) package may be used at the allocation to allow the MG perform any potential optimizations. For example, if the MGC adds a Termination with an Audio Stream with the "Constant Media" codepoint set, then the MG knows it will not need to assign resources that are capable of video for the life of the Context/Termination. + +### 6.1.3 Detailed congestion reporting (H.248.32) + +[ITU-T H.248.32] allows for the reporting of resource usage through an abstraction approach. In using the abstraction approach, the MG must determine the relationship between the states of the physical resources and the percentage value of the abstraction codepoint. Through Congestion reports (see clause 5.2.1 of [ITU-T H.248.32]), the MGC learns of the resource usage. As such, the MGC must convert the abstract codepoint into an action at the call/service level to manage the congestion condition; it may utilize the *arm* and *rmr* packages of this Recommendation in order to optimize the MG resource allocation, thus allowing more calls/services for the available MG capacity. The MGC may also utilize the *rmc* package in order to reserve resources for important conferences/calls to maximize their success when the MG is congested. + +### 6.1.4 Connection capability control (H.248.46) + +H.248 allows an MG to save transcoding resources by autonomously connecting the Terminations in the same MG but different Contexts directly to each other. [ITU-T H.248.46] enables a MGC to determine if the MG has this capability and to control whether this capability is used. If the MG supports this autonomous connection capability, it also supports resource optimization. Where both autonomous connection capability and this Recommendation are used on a MG, then it should consider the setting of the packages of this Recommendation as part of the determination to use autonomous connection capability. + +Consider the following example. A MGC creates on a MG two Contexts with two Terminations in each (i.e., Cxt1 has Tid1 and Tid2, Cxt2 has Tid3 and Tid4). Terminations Tid2 and Tid3 have addresses which indicate that internal connection is possible. Tid1 has a G.711 codec, Tid2 and Tid3 have an AMR codec and Tid4 has a G.711 codec. The MG may use its autonomous connection capability to effectively remove Tid2 and Tid3 and remove a transcoding stage. However, due to the nature of H.248, it must be prepared to re-insert a transcoding stage if the encoding of Tid1 or Tid4 change, irrespective of whether the change actually takes place. With the Resource Management Rules (*rmr*) package, the MG would not have to be prepared to change the transcoding resources. + +### 6.1.5 Control load quantum for decomposed gateways (H-series Supplement 6) + +Load is placed on a MG when a Context is created. [b-ITU-T H-Sup.6] describes load control metrics for H.248 systems and introduces the concept of busy hour context attempts (BHCoA). It discusses how resource holding times affect load that may be placed on a MG. By using the packages in this Recommendation, the MG may describe the usage of resources at Context allocation time. + +# 7 Resource management rules package + +**Package Name:** Resource management rules + +**Package ID:** *rmr* (0x00cd) + +**Description:** This package enables the MGC to discover the rules that, when followed, allow the MG to manage the usage of its resources in a particular way, e.g., optimize its resources. If the MGC can comply with these rules, it can then indicate + +which rules it will use. The MG can then be certain of particular MGC behaviour and can manage its resources accordingly. + +Specific rules are defined as separate properties as this allows the property value to provide more information to describe the rule to the MG. The properties indicate rules that will lead to resources being managed on a MG in a particular way, e.g., an optimization of resources on the MG. These rules may be applied to the MG on a whole or on a particular Termination. + +**Version:** 1 + +**Extends:** None + +## 7.1 Properties + +### 7.1.1 Constant media + +**Property Name:** Constant media + +**Property ID:** cm (0x0001) + +**Description:** This rule indicates that once a media type (audio, video, image, data) has been set for a particular H.248 Stream, it will not change to another media type whilst the Termination remains in the Context. + +**Type:** Enumeration + +**Possible values:** MC (0x0000) Media stream type may change +MNC (0x0001) Media stream type shall not change + +**Default:** MC (0x0000) + +**Defined in:** LocalControl + +**Characteristics:** Read/Write + +### 7.1.2 Constant property value + +**Property Name:** Constant property value + +**Property ID:** cpv (0x0002) + +**Description:** This rule indicates that a particular Property value is constant after it has been assigned. The value will not change again for the life of the Termination/Stream. + +**Type:** Sub-List of String + +**Possible values:** Each String having the format `constprop` according to the following ABNF: + +``` +constprop = resource ; See 8.1.1 for a definition of + ; resource +``` + +**Default:** Empty String (All resources are variable) + +**Defined in:** Termination State or LocalControl + +**Characteristics:** Read/Write + +## 7.2 Events + +None. + +## 7.3 Signals + +None. + +## 7.4 Statistics + +None. + +## 7.5 Error codes + +### 7.5.1 Behaviour contradicts resource rule + +**Error Code #:** 478 + +**Name:** Behaviour contradicts resource rule + +**Definition:** This error indicates that the MGC has performed an H.248 action that contravenes the agreed resource management rule behaviour defined in H.248.63. The action is disregarded. + +**Error Text in the Error Descriptor:** The PropertyID of the rule that is contravened. E.g., "0x0001" or "cm". + +**Comment:** None + +## 7.6 Procedures + +The MGC should perform an AuditCapabilities command on the properties defining the rules to determine the resource management rules that are supported on the MG. If the MGC can support any of these rules, it shall set the corresponding property to the values that it supports. From that point onward, the MG shall expect the MGC to operate in this manner. If the actions received by the MG from the MGC contravene these rules, then the MG shall return an error code 478 "Behaviour contradicts resource rule". + +The behaviour associated with each rule is described in the subclauses below. + +### 7.6.1 Constant media (cm, 0x0001) + +This rule indicates that, once a media type (audio, video, image, or data) has been set for a particular H.248 Stream, it will not change to another media type whilst the Termination remains in the Context. The format or other characteristics of the media stream may however change. This property does not affect the coding of media (for example, if the stream is an audio stream, it shall not change to a video stream; however, the codec used may change). As the MGC is aware of the service capabilities, this property is applicable to all Termination types (for example, for an IP Termination, this property may relate to the "SDP media type parameter in an m= line"; for a TDM Termination, it may relate to the Transmission Medium Requirement information element, etc.). As such, this property is technology/description independent. Once the constant media property has been set to indicate that the media type for the Termination/Stream will not change, if the MGC then requests to modify the value to indicate that it "may change", then the MG shall respond with error code "542 – Command is not allowed on this Termination". + +### 7.6.2 Constant property value (cpv, 0x0002) + +The default behaviour of H.248 is that any of the properties associated with a Termination/Stream may be modified by a MGC at any time. This rule allows the indication that the value of certain properties once set will remain constant whilst the Termination remains in the Context or whilst the Stream exists. When the property is set in the TerminationState descriptor, it only applies to properties set in that descriptor. When set in the LocalControl descriptor, it applies to properties for that particular Stream. The Constant Property Value (*rmr/cpv*) property should be set before or at the time that the associated property is set. This allows the MG to optimize its resources around the + +fact that the property will not change. Once a property has been added to the *rmr/cpv* sub-list and is set on the Termination/Stream, it shall not be removed from the *rmr/cpv* sub-list on the Termination/Stream until Termination Subtraction or the removal of the Stream. If the MGC attempts to remove the property from the *rmr/cpv* sub-list, the MG shall respond with error code "542 – Command is not allowed on this Termination". + +# 8 Resource management configuration package + +**Package Name:** Resource management configuration + +**Package ID:** rmc (0x00ce) + +**Description:** This package allows a MGC to describe to the MG which resources are expected to be used in a Context. The resources are described in a manner consistent with the H.248 connection model. That is, the overall resource picture of a particular Context is described through the use of setting characteristics on Terminations and Streams. + +**Version:** 1 + +**Extends:** None + +## 8.1 Properties + +### 8.1.1 Resource description + +**Property Name:** Resource description + +**Property ID:** rd (0x0001) + +**Description:** This property allows the MGC to describe the resources that will be used in the Context. This is achieved by describing the resources on a Termination basis. + +**Type:** ABNF: Sub-list of String, ASN.1: Sub-list of Octet String + +**Possible values:** The value of each instance of the string is given by the following: + +For both Text and Binary encoding ABNF: + +``` +rd = [number COLON resource *(COMMA resource)] +number = UINT16 +resource = termstate / localcont / localremote +termstate = TerminationStateToken COLON packageitems +localcont = LocalControlToken COLON ( packageitems / +streamMode ) +localremote = (MediaToken / StreamToken / LocalToken / +RemoteToken) COLON (packageitems / sdp) +packageitems = propertyParm *(COMMA propertyParm) +sdp = "SDP(" OCTETSTRING ")" +; sdp & packageitems are deemed equivalent as sdp +; may contain multiple parameters, +``` + +The "quotedstring" form of value should be used. + +An empty string indicates that there is no initial or further resource description. + +Binary equivalents for the package name, property name and values may be used. The package name and property name shall drop the leading zero (0) from the hexadecimal notation in order to match the NAME syntax, i.e., x0000/x1001=2. + +**Default:** Empty String + +**Defined in:** ContextAttribute + +**Characteristics:** Read/Write + +## **8.2 Events** + +None. + +## **8.3 Signals** + +None. + +## **8.4 Statistics** + +None. + +## **8.5 Error codes** + +None. + +## **8.6 Procedures** + +### **8.6.1 Resource description** + +This property may be used to describe the resources that will be used by the H.248 Context. This is not the same as adding the Terminations through H.248 commands. The resources are only utilized when the appropriate descriptors are set on the Terminations. + +The resources are described in a manner consistent with the H.248 connection model. That is, each Termination describes the characteristics at the input and output of the Context. The MG then builds its own resource picture based on the description. + +The MGC may indicate one or more resources and may couple these resources to build dependencies between them. Dependent resources shall share the same value instance. The MGC may use a higher level construct as a form of wildcarding. The reference to a Stream means that the resource applies to both the local and remote sides. The use of Media means that the resources apply to both the local and remote sides of all streams. CHOOSE may be used in the place of a value when the MGC does not care about the value. Wildcarding of package names and property names shall not be used. Wildcarding of SDP shall follow the guidelines outlined in [ITU-T H.248.39]. + +### **8.6.2 Resource allocation and clearing** + +As discussed in clause 6, the resource management configuration package is typically used when a Context is first created (i.e., at call/session establishment). The MGC determines from the required service what resources are likely to be used in the MG and sets these in the resource description (*rmc/rd*) property. The MG can then use this information to allocate resources in an efficient manner. + +For example, the MGC may determine that the Context creation is as a result of a dial in audio conference with eight ports. The MG can then pre-assign a conferencing device to the Context rather than assigning a connection for a normal two-party call. As each extra participant dials in, the MGC then requests a Termination/Stream using the normal H.248 mechanisms. The *rmc/rd* property does not need to be changed as resources are allocated by the MGC/MG. + +The MGC may change the value of the *rmc/rd* property after the initial Context allocation; however, it is up to the MG whether any action is taken based on this setting. A MG is likely to take action if it determines that the information is useful for any other resource optimization. + +Once the MGC has determined that the Call/Service is in steady state, it should remove the *rmc/rd* property in order to indicate to the MG that the expected resources have been used. The MG may + +then use this fact and the actual resources allocated to determine if it can clear any unallocated pre-assigned resources. + +NOTE 1 – The use of rmc/rd for resource allocation/clearing is as a guide to the MG for initial resource allocation. The MGC, based on further services/interactions, may need to alter the resources at a later stage. + +NOTE 2 – The resources for an eight port audio conference may also be reserved by allocating eight terminations to a Context in a single transaction. However, this means that the MG must allocate resources for each of these terminations, even though they may not be used. In order to determine optimal resource allocation, the MG must parse the transaction as a whole, rather than deal with each command individually. + +### 8.6.3 Usage examples + +**Example 1:** The MG can expect three audio Terminations using text encoding. The value would be set: + +``` +rmc/rd="3:stream:SDP(v=0 + c=$ $ $ + m=audio $ $ $) " +``` + +**Example 2:** The MG can expect three audio Terminations, two with video and one audio-only using text encoding. The value would be set: + +``` +rmc/rd="1:stream:SDP(v=0 + c=$ $ $ + m=audio $ $ $) ", +"2:stream:SDP(v=0 + c=$ $ $ + m=audio $ $ $), +stream:SDP(v=0 + c=$ $ $ + m=video $ $ $) " +``` + +**Example 3:** The MG can expect ten listening-only Terminations and two speaking and listening in the Context, with the binary package ID and values used. The value would be set: + +``` +rmc/rd="10:stream:x0000/x1001=0, + Localcontrol:SendOnly", +"2:stream:x0000/x1001=0, + Localcontrol:SendRecv" +``` + +# 9 Abstract resource management package + +**Package Name:** Abstract resource management + +**Package ID:** arm (0x00cf) + +**Description:** This package allows a MGC to manage a set of resources via the use of a single codepoint which references a set of MG resources and particular management behaviour. + +**Version:** 1 + +**Extends:** None + +## 9.1 Properties + +### 9.1.1 Resource description + +**Property Name:** Resource description + +**Property ID:** rd (0x0001) + +**Description:** This property allows the MGC to associate an abstract resource description with a certain resource and management action on a Termination. It also allows the MGC to provide extra information that may be necessary to map the abstract resource name to actual MG resources. + +**Type:** Sub-list of String + +**Possible values:** The value of each instance of the string is given by the following ABNF: + +rd = NAME [COLON \*(SafeChar/EOL /%x80-FF/ RestChar/WSP)] + +How the "NAME" and OCTETSTRING data maps to specific resources shall be described in the procedures section of this package or any extension package and should be documented as follows: + +#### **x.x.x Abstract Resource Heading** + +**Name:** ** + +**Extra data:** ** + +**Resource mapping description:** ** + +**Procedures:** ** + +**Default:** None + +**Defined in:** TerminationState or LocalControl + +**Characteristics:** Read/Write + +## **9.2 Events** + +None. + +## **9.3 Signals** + +None. + +## **9.4 Statistics** + +None. + +## **9.5 Error Codes** + +None. + +## **9.6 Procedures** + +If the MGC wants to utilize the abstract resource concept to indicate the MG to allocate/reserve resource, it shall set the *arm/rd* property with the abstract resource names and possible extra information/data described in the subclause below. The MG shall then map the abstract resource name to a set of associated actual MG resources which will be allocated/reserved. Where multiple abstract resources are requested, the MG should consider the resources to be cumulative unless specified otherwise. + +The abstract resource shall be defined before being used. This definition includes its name, the possible extra information/data that may be necessary to do mapping, the identifiers of the + +associated actual MG resources, and the procedures of the management behaviour on these resources. The extra information/data may be used to adjust (i.e., increase, reduce or modify) the resource, based on the set of the associated actual MG resource. When an abstract resource is defined, any potential interaction problems with previously defined resources should be documented. + +The MGC may cancel the previous abstract behaviour setting by removing the string instance that defined the behaviour from the *arm/rd* property. + +### **9.6.1 ListenOnly Termination participant** + +**Name:** Listenonly + +**Extra Data:** None + +**Resource mapping description:** Maps to the fact that the Stream associated with the Termination will only have a local control stream mode of "SendOnly" or "Inactive" + +**Procedures:** When the MGC adds a Termination to a Context with this value, it shall optimize its resources recognizing the fact that the stream mode of the Termination will never be set to "SendRecv" or "RecvOnly", whilst the Termination remains in the Context. If the MGC tries to set the Termination to "SendRecv" or "RecvOnly", the MG should reply with error code 449 "Unsupported or unknown parameter or property value". + +# Bibliography + +- [b-ITU-T H-Sup.6] ITU-T H-series Recommendations – Supplement 6 (2006), *Control load quantum for decomposed gateways*. +- [b-3GPP TS 29.232] 3GPP Technical Specification 29.232 v7.5.0 (2007-03), *Media Gateway Controller (MGC) – Media Gateway (MGW) interface; Stage 3 (Release 7)*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1026f1ff6093e7a9b29b000e02f08ed575775c7 --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9a6bc47d67936de7503d466d8581599a721b6ef61b883adc393d3b90cd68668 +size 69740 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09e60735c51b9cb433463ac8a1cccfd1382ba060 --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0cc6db038cb97cc9f700a1b3843daeb56670ad4cb91791072b819074de8fa8c +size 73351 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d9c2afd8ee4bce2c714b1f44c1a6b0bfb5dbfff --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a430514111b6140f55fb821ff9d4735d457549ca5dc607d8495a3dd29672c497 +size 78971 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..894e3570bb995f58521147d2e46d57a82f39d4ae --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82f6756183f2af693fb3907f313ac6395eaaeb3d40e58e211c6dcc134458df9a +size 64452 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d159d955fbfcc18cfe0661b5f80d2814d3f1edba --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea59f083eaf46565d897e86f49078537b08e7989f23812b4510280804eb348d0 +size 126864 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6a353c71b1c51d34c9fc68de35d92855b43a6fa --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eda49f1d4994fb26431619ac935ca7c0c02b2e44c5d4257046652b8f6be472a6 +size 57212 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2c00d35ff6cf3a7ec644dd514e873f874973883 --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29d454efdebb52fb043d8c6724f2ba824fa0538d421ab471bd0939cc8cfba224 +size 111960 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62a2e98629da5a6328a0ac2bd6ddfe35692322ae --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:704894a92b416ba01d0084281c9f236cf8f10581b6beb515db7a33ac54f5b95d +size 6625 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4614e0f0784ba300b07aa8d49fc5332c98e625c --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fc9eb16ee3660e82d463da0a2938e4843b8dcc907ea05bebd516725ccfb48ce +size 55840 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20eb3016b768b1c133367c678d6d9c7e65ec2b94 --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08e7c1c9de2ec4e39c0bd160334efca7903cd1956d5af5a261dc7fd21fdef097 +size 43112 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f210256c522585ec9fcb62764b49a08ec9076095 --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a72a4ea543d9c8bbc0c805e9c4f0aa8b1bb6cc35d0accff6ca83039e899b805 +size 100927 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/b6ad8b32179842fca5ad086cf22b03eb_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/b6ad8b32179842fca5ad086cf22b03eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..642bc5fe46ce0c474f11401524a24914780bc210 --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/b6ad8b32179842fca5ad086cf22b03eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c2fbbf469576a0959287a67683af65aec692ca329f908be589226bc4463e92d +size 55066 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d62ab7bceb3857c7dc1cb9b79138058202e84184 --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d6ef033ea8647181422f6d1adb615fd1bfc7911450889ed87fa05e7c93c4ab9 +size 97785 diff --git a/marked/H/T-REC-H.248.64-201303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.248.64-201303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18b720015aa6dc5a0fa728f0c47c9abce191f237 --- /dev/null +++ b/marked/H/T-REC-H.248.64-201303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2abfe673d198aa26d539b961cd174212ce0c8bad97097d3b45f4f96c3e8ef555 +size 61673 diff --git a/marked/H/T-REC-H.248.65-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.65-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/H/T-REC-H.248.65-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/H/T-REC-H.248.65-200903-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.248.65-200903-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1bad07adebce7de7caa69c84cf3759f1dd887ed --- /dev/null +++ b/marked/H/T-REC-H.248.65-200903-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2dd7200f9e866cd112d2ef651c27f1a06510ca11359f98489efe6ee30860145 +size 109918 diff --git a/marked/H/T-REC-H.248.65-200903-I_PDF-E/raw.md b/marked/H/T-REC-H.248.65-200903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d34c8cd4185fb4bcfc5dad7c395b64e389e25d1b --- /dev/null +++ b/marked/H/T-REC-H.248.65-200903-I_PDF-E/raw.md @@ -0,0 +1,1102 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.65** + +(03/2009) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: Support of the resource reservation protocol** + +Recommendation ITU-T H.248.65 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.248.65 + +# Gateway control protocol: Support of the resource reservation protocol + +## Summary + +Recommendation ITU-T H.248.65 provides an ITU-T H.248 package for the support of the resource reservation protocol (RSVP). The protocol capabilities are tightly coupled with the pull mode defined in Recommendation ITU-T H.248.55. The *RSVP extension* package complements the *generic pull mode* package by providing additional capabilities for the specific path-coupled QoS/resource control protocol RSVP. This package allows the ITU-T H.248 entities to make the resource reservation, i.e., set up the bearer path with the desired QoS. Based on this package, the MGC and the MG are able to initiate/terminate the RSVP messages. + +## Source + +Recommendation ITU-T H.248.65 was approved on 16 March 2009 by ITU-T Study Group 16 (2009-2012) under Recommendation ITU-T A.8 procedures. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 RSVP extension package..... | 3 | +| 6.1 Properties..... | 3 | +| 6.2 Events ..... | 3 | +| 6.3 Signals ..... | 11 | +| 6.4 Statistics..... | 15 | +| 6.5 Error codes..... | 15 | +| 6.6 Procedures ..... | 15 | + + + +# Gateway control protocol: Support of the resource reservation protocol + +# 1 Scope + +[ITU-T H.248.55] provides a *generic package* (as *base package*) for pull mode support. Such a capability is, for instance, required for bearer/media path-coupled QoS control protocols, like the resource reservation protocol (RSVP) according to [IETF RFC 2205]. + +This *extension package* describes the RSVP-specific procedures and enables the ITU-T H.248 entities to support an RSVP mechanism, which includes the initiation/termination of RSVP messages. This package provides a means of resource reservation, by which the MGC and the MG are able to set up the bearer path with the desired QoS. + +[IETF RFC 2205] defines several RSVP message types. In addition to the two fundamental types: (Path and Resv), there are also teardown messages (PathTear and ResvTear), error messages (PathErr and ResvErr) and a confirm message (ResvConf). This Recommendation introduces a generic method for the MGC and the MG to deal with these above messages to support RSVP. + +The ITU-T H.248 media gateway acts as an RSVP-aware policy enforcement point (PEP) when processing RSVP messages. The ITU-T H.248 MGC acts as an RSVP-aware policy decision point (PDP), it is the MGC that determines when to send the RSVP messages. On reception of incoming RSVP messages, the MG reports the related events to the MGC for its resource policy decision. + +As such, the packages in this Recommendation allow the support of the functionality outlined by the application/RSVP interface (clause 3.11.1 of [IETF RFC 2205]). + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3; Amendment 1* (2008). +- [ITU-T H.248.55] Recommendation ITU-T H.248.55 (2008), *Gateway control protocol: Generic pull mode package*. +- [ITU-T Y.2111] Recommendation ITU-T Y.2111 (2006), *Resource and admission control functions in Next Generation Networks*. +- [IETF RFC 2205] IETF RFC 2205 (1997), *Resource ReSerVation Protocol (RSVP) – Version 1 Functional Specification*. +- [IETF RFC 2210] IETF RFC 2210 (1997), *The Use of RSVP with IETF Integrated Services*. +- [IETF RFC 2750] IETF RFC 2750 (2000), *RSVP Extensions for Policy Control*. +- [IETF RFC 3182] IETF RFC 3182 (2001), *Identity Representation for RSVP*. +- [IETF RFC 3520] IETF RFC 3520 (2003), *Session Authorization Policy Element*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 ADSPEC:** An object of a RSVP message, defined in Appendix A "Object Definitions" of [IETF RFC 2205], "Carries OPWA data, in a Path message"; see also its detailed format in clause 3.3 "RSVP ADSPEC Object" of [IETF RFC 2210]. + +**3.1.2 ERROR\_SPEC:** An object of a RSVP message, defined in Appendix A of [IETF RFC 2205], "Specifies an error in a PathErr, ResvErr, or a confirmation in a ResvConf message". + +**3.1.3 FILTER\_SPEC:** An object of a RSVP message, defined in Appendix A of [IETF RFC 2205], "Defines a subset of session data packets that should receive the desired QoS (specified by a FLOWSPEC object), in a Resv message". + +**3.1.4 POLICY\_DATA:** An object of a RSVP message, defined in Appendix A of [IETF RFC 2205], "Carries information that will allow a local policy module to decide whether an associated reservation is administratively permitted. It may appear in Path, Resv, PathErr, or ResvErr message". + +**3.1.5 FLOWSPEC:** An object of a RSVP message, defined in Appendix A of [IETF RFC 2205], "Defines a desired QoS, in a Resv message"; see also its detailed format in clause 3.2 "RSVP FLOWSPEC Object" of [IETF RFC 2210]. + +**3.1.6 SENDER\_TSPEC:** An object of a RSVP message, defined in Appendix A of [IETF RFC 2205], "Defines the traffic characteristics of a sender's data flow"; see also its detailed format in clause 3.1 "RSVP SENDER\_TSPEC Object" of [IETF RFC 2210]. + +**3.1.7 SESSION:** An object of a RSVP message, defined in Appendix A of [IETF RFC 2205], "Contains the IP destination address (DestAddress), the IP protocol id, and some form of generalized destination port, to define a specific session for the other objects that follow. It is required in every RSVP message". + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +| | | +|------|-------------------------------| +| IP | Internet Protocol | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| PDP | Policy Decision Point | +| PEP | Policy Enforcement Point | +| QoS | Quality of Service | +| RSVP | Resource ReSerVation Protocol | +| SIP | Session Initiation Protocol | + +TTL Time to Live + +# 5 Conventions + +None. + +# 6 RSVP extension package + +**Package Name:** RSVP extension package + +**Package ID:** rsvp (0x00d2) + +**Description:** This package complements the generic pull mode package by providing additional capabilities for the specific path-coupled QoS/resource control protocol RSVP [IETF RFC 2205]. This package allows the ITU-T H.248 entities to make the resource reservation, i.e., set up the bearer path with the desired QoS. Based on this package, the MGC and the MG are able to initiate/terminate the RSVP messages. + +**Version:** 1 + +**Extends:** Generic pull mode package (*plm*) version 1 [ITU-T H.248.55]. + +## 6.1 Properties + +None. + +## 6.2 Events + +### 6.2.1 Path Received + +**Event Name:** Path Received + +**Event ID:** pathr (0x0004) + +**Description:** This event enables the MGC to be notified when the first RSVP Path message is received by the MG, or if the path state is changed by later Path messages. The parameters are related to RSVP information elements contained in the received message. + +This event shall be applied to the **Root termination** or to **ephemeral terminations** only. + +#### 6.2.1.1 EventDescriptor Parameters + +None. + +#### 6.2.1.2 ObservedEventsDescriptor Parameters + +##### 6.2.1.2.1 Session ID + +**Parameter Name:** Session ID + +**Parameter ID:** session (0x0001) + +**Description:** This parameter relates to RSVP object "SESSION". + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.2.1.2.2 Sender TSpec + +**Parameter Name:** Sender TSpec +**Parameter ID:** stspec (0x0002) +**Description:** This parameter relates to RSVP object "SENDER\_TSPEC". +**Type:** Octet String +**Optional:** Yes +**Possible values:** A sequence of octets +**Default:** None + +##### 6.2.1.2.3 Ad Spec + +**Parameter Name:** Ad Spec +**Parameter ID:** adspec (0x0003) +**Description:** This parameter relates to RSVP object "ADSPEC". +**Type:** Octet String +**Optional:** Yes +**Possible values:** A sequence of octets +**Default:** None + +##### 6.2.1.2.4 Policy Data + +**Parameter Name:** Policy Data +**Parameter ID:** policy (0x0004) +**Description:** This parameter relates to RSVP object "POLICY\_DATA". +**Type:** Octet String +**Optional:** Yes +**Possible values:** A sequence of octets +**Default:** None + +### 6.2.2 Resv Received + +**Event Name:** Resv Received +**Event ID:** resvr (0x0005) +**Description:** This event enables the MGC to be notified when the first RSVP Resv message is received by the MG, or if the reservation state is changed by later Resv messages. The parameters are related to RSVP information elements contained in the received message. + +This event shall be applied to the **Root termination** or to **ephemeral terminations** only. + +#### 6.2.2.1 EventDescriptor Parameters + +None. + +#### **6.2.2.2 ObservedEventsDescriptor Parameters** + +##### **6.2.2.2.1 Session ID** + +**Parameter Name:** Session ID + +**Parameter ID:** session (0x0001) + +**Description:** This parameter relates to RSVP object "SESSION". + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +##### **6.2.2.2.2 Style** + +**Parameter Name:** Style + +**Parameter ID:** style (0x0002) + +**Description:** This parameter represents the reservation style. + +**Type:** Enumeration + +**Optional:** No + +**Possible values:** "FF" (0x0001) Fixed-Filter +"SE" (0x0002) Shared-Explicit +"WF" (0x0003) Wildcard-Filter + +**Default:** None + +##### **6.2.2.2.3 Flow Spec** + +**Parameter Name:** Flow Spec + +**Parameter ID:** flowspec (0x0003) + +**Description:** This parameter relates to RSVP object "FLOWSPEC". It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +##### **6.2.2.2.4 Filter Spec** + +**Parameter Name:** Filter Spec + +**Parameter ID:** filterspec (0x0004) + +**Description:** This parameter relates to RSVP object "FILTER\_SPEC". It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.2.2.2.5 Policy Data + +**Parameter Name:** Policy Data + +**Parameter ID:** policy (0x0005) + +**Description:** This parameter relates to RSVP object "POLICY\_DATA". It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +### 6.2.3 Path Error + +**Event Name:** Path Error + +**Event ID:** patherr (0x0006) + +**Description:** This event indicates a RSVP PathErr message has been received by the MG. The parameters are related to RSVP information elements contained in the received message. + +This event shall be applied to the **Root termination** or to **ephemeral terminations** only. + +#### 6.2.3.1 EventDescriptor Parameters + +None. + +#### 6.2.3.2 ObservedEventsDescriptor Parameters + +##### 6.2.3.2.1 Session ID + +**Parameter Name:** Session ID + +**Parameter ID:** session (0x0001) + +**Description:** This parameter relates to RSVP object "SESSION". + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.2.3.2.2 Error Spec + +**Parameter Name:** Error Spec + +**Parameter ID:** errspec (0x0002) + +**Description:** This parameter relates to RSVP object "ERROR\_SPEC". + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.2.3.2.3 Policy Data + +**Parameter Name:** Policy Data + +**Parameter ID:** policy (0x0003) + +**Description:** This parameter relates to RSVP object "POLICY\_DATA" from the failed Path message. It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +### 6.2.4 Resv Error + +**Event Name:** Resv Error + +**Event ID:** resverr (0x0007) + +**Description:** This event indicates a RSVP ResvErr message has been received by the MG. The parameters are related to RSVP information elements contained in the received message. + +This event shall be applied to the **Root termination** or to **ephemeral terminations** only. + +#### 6.2.4.1 EventDescriptor Parameters + +None. + +#### 6.2.4.2 ObservedEventsDescriptor Parameters + +##### 6.2.4.2.1 Session ID + +**Parameter Name:** Session ID + +**Parameter ID:** session (0x0001) + +**Description:** This parameter relates to RSVP object "SESSION". + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.2.4.2.2 Error Specification + +**Parameter Name:** Error Specification + +**Parameter ID:** errspec (0x0002) + +**Description:** This parameter relates to RSVP object "ERROR\_SPEC". + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.2.4.2.3 Flow Spec + +**Parameter Name:** Flow Spec + +**Parameter ID:** flowspec (0x0003) + +**Description:** This parameter relates to RSVP object "FLOWSPEC". It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.2.4.2.4 Filter Spec + +**Parameter Name:** Filter Spec + +**Parameter ID:** filterspec (0x0004) + +**Description:** This parameter relates to RSVP object "FILTER\_SPEC". It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.2.4.2.5 Policy Data + +**Parameter Name:** Policy Data + +**Parameter ID:** policy (0x0005) + +**Description:** This parameter relates to RSVP object "POLICY\_DATA". It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +### 6.2.5 Resv Confirm + +**Event Name:** Resv Confirm + +**Event ID:** resvconf (0x0008) + +**Description:** This event indicates a RSVP ResvConf message has been received by the MG. The parameters are related to RSVP information elements contained in the received message. + +This event shall be applied to the **Root termination** or to **ephemeral terminations** only. + +#### 6.2.5.1 EventDescriptor Parameters + +None. + +#### **6.2.5.2 ObservedEventsDescriptor Parameters** + +##### **6.2.5.2.1 Session ID** + +**Parameter Name:** Session ID + +**Parameter ID:** session (0x0001) + +**Description:** This parameter relates to RSVP object "SESSION". + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +##### **6.2.5.2.2 Style** + +**Parameter Name:** Style + +**Parameter ID:** style (0x0002) + +**Description:** This parameter represents the reservation style of the RSVP session. + +**Type:** Enumeration + +**Optional:** No + +**Possible values:** "FF" (0x0001) Fixed-Filter +"SE" (0x0002) Shared-Explicit +"WF" (0x0003) Wildcard-Filter + +**Default:** None + +##### **6.2.5.2.3 Flow Spec** + +**Parameter Name:** Flow Spec + +**Parameter ID:** flowspec (0x0003) + +**Description:** This parameter relates to RSVP object "FLOWSPEC". It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +##### **6.2.5.2.4 Filter Spec** + +**Parameter Name:** Filter Spec + +**Parameter ID:** filterspec (0x0004) + +**Description:** This parameter relates to RSVP object "FILTER\_SPEC". It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.2.5.2.5 Policy Data + +**Parameter Name:** Policy Data + +**Parameter ID:** policy (0x0005) + +**Description:** This parameter relates to RSVP object "POLICY\_DATA". It is reported if contained in the received message. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +### 6.2.6 RSVP Teardown + +**Event Name:** RSVP Teardown + +**Event ID:** teardown (0x0009) + +**Description:** This event enables the MGC to be notified when the RSVP teardown message has been received. + +#### 6.2.6.1 EventDescriptor Parameters + +None. + +#### 6.2.6.2 ObservedEventsDescriptor Parameters + +##### 6.2.6.2.1 Session ID + +**Parameter Name:** Session ID + +**Parameter ID:** session (0x0001) + +**Description:** This parameter relates to RSVP object "SESSION", to identify the session that needs to be released. + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +### 6.2.7 State Expiration + +**Event Name:** State Expiration + +**Event ID:** se (0x000a) + +**Description:** This event is used to detect the state expiration of the RSVP sessions. The state of the RSVP session in the MG will expire if not refreshed within a specified amount of time. Once the session state expires, the MG shall report this event to the MGC. + +#### 6.2.7.1 EventDescriptor Parameters + +##### 6.2.7.1.1 State Expiration Interval + +**Parameter Name:** State Expiration Interval + +**Parameter ID:** sei (0x0001) + +**Description:** This parameter provides the state cleanup timeout value of the RSVP session. The state of the session expires if no matching refresh RSVP messages arrive at a state expiration interval. If a RSVP refresh message arrives, the timer is reset. + +**Type:** Integer + +**Optional:** Yes + +**Possible values:** Any positive integer in milliseconds. See section 3.7 of [IETF RFC 2205] for more information regarding the setting of this parameter. + +**Default:** Provisioned + +#### 6.2.7.2 ObservedEventsDescriptor Parameters + +##### 6.2.7.2.1 Session ID + +**Parameter Name:** Session ID + +**Parameter ID:** session (0x0001) + +**Description:** This parameter relates to RSVP object "SESSION", to identify the session whose state expires. + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +## 6.3 Signals + +### 6.3.1 Send Path + +**Signal Name:** Send Path + +**Signal ID:** path (0x0001) + +**Description:** This signal triggers the MG to send a RSVP Path message (messages in case of a refresh) for the resource reservation session. + +**Signal Type:** On/Off + +**Default:** Provisioned + +#### 6.3.1.1 Additional parameters + +##### 6.3.1.1.1 Session ID + +**Parameter Name:** Session ID + +**Parameter ID:** session (0x0001) + +**Description:** This parameter relates to RSVP object "SESSION". + +**Type:** Octet String + +**Optional:** No + +**Possible values:** A sequence of octets + +**Default:** None + +##### 6.3.1.1.2 Sender TSpec + +**Parameter Name:** Sender TSpec + +**Parameter ID:**        stspect (0x0002) +**Description:**        This parameter relates to RSVP object "SENDER\_TSPECT". +**Type:**                  Octet String +**Optional:**            Yes +**Possible values:**   A sequence of octets +**Default:**              None + +##### 6.3.1.1.3 Ad Spec + +**Parameter Name:** Ad Spec +**Parameter ID:**        adspec (0x0003) +**Description:**        This parameter relates to RSVP object "ADSPECT". +**Type:**                  Octet String +**Optional:**            Yes +**Possible values:**   A sequence of octets +**Default:**              None + +##### 6.3.1.1.4 Policy Data + +**Parameter Name:** Policy Data +**Parameter ID:**        policy (0x0004) +**Description:**        This parameter relates to RSVP object "POLICY\_DATA". +**Type:**                  Octet String +**Optional:**            Yes +**Possible values:**   A sequence of octets +**Default:**              None + +##### 6.3.1.1.5 Data TTL + +**Parameter Name:** Data TTL +**Parameter ID:**        dttl (0x0005) +**Description:**        This parameter indicates the IP Time-To-Live value that is associated with the data packets. +**Type:**                  Integer +**Optional:**            Yes +**Possible values:**   Any positive integer +**Default:**              Provisioned + +##### 6.3.1.1.6 Time Value + +**Parameter Name:** Time Value +**Parameter ID:**        time (0x0006) +**Description:**        This parameter indicates the refresh period of the path messages. +**Type:**                  Integer + +**Optional:** Yes +**Possible values:** Any positive integer; represents milliseconds +**Default:** Provisioned + +### 6.3.2 Send Resv + +**Signal Name:** Send Resv +**Signal ID:** resv (0x0002) +**Description:** This signal triggers the MG to send a RSVP Resv message (messages in case of a refresh) for the resource reservation session. +**Signal Type:** On/Off +**Default:** Provisioned + +#### 6.3.2.1 Additional parameters + +##### 6.3.2.1.1 Session ID + +**Parameter Name:** Session ID +**Parameter ID:** session (0x0001) +**Description:** This parameter relates to RSVP object "SESSION". +**Type:** Octet String +**Optional:** No +**Possible values:** A sequence of octets +**Default:** None + +##### 6.3.2.1.2 Style + +**Parameter Name:** Style +**Parameter ID:** style (0x0002) +**Description:** This parameter represents the reservation style of the RSVP session. +**Type:** Enumeration +**Optional:** No +**Possible values:** "FF" (0x0001) Fixed-Filter +"SE" (0x0002) Shared-Explicit +"WF" (0x0003) Wildcard-Filter +**Default:** Provisioned + +##### 6.3.2.1.3 Flow Spec + +**Parameter Name:** Flow Spec +**Parameter ID:** flowspec (0x0003) +**Description:** This parameter relates to RSVP object "FLOWSPEC", which depends upon the value of the 'Style'. +**Type:** Octet String +**Optional:** Yes +**Possible values:** A sequence of octets + +**Default:** None + +##### **6.3.2.1.4 Filter Spec** + +**Parameter Name:** Filter Spec + +**Parameter ID:** filterspec (0x0004) + +**Description:** This parameter relates to RSVP object "FILTER\_SPEC", which depends upon the value of the 'Style'. + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +##### **6.3.2.1.5 Policy Data** + +**Parameter Name:** Policy Data + +**Parameter ID:** policy (0x0005) + +**Description:** This parameter relates to RSVP object "POLICY\_DATA". + +**Type:** Octet String + +**Optional:** Yes + +**Possible values:** A sequence of octets + +**Default:** None + +##### **6.3.2.1.6 Confirm Flag** + +**Parameter Name:** Confirm Flag + +**Parameter ID:** confirm (0x0006) + +**Description:** This parameter indicates if a reservation confirmation is desired. + +**Type:** Boolean + +**Optional:** Yes + +**Possible values:** ON: confirmation is required +OFF: confirmation is not required + +**Default:** Provisioned + +##### **6.3.2.1.7 Time Value** + +**Parameter Name:** Time Value + +**Parameter ID:** time (0x0007) + +**Description:** This parameter indicates the refresh period of the resv messages. + +**Type:** Integer + +**Optional:** Yes + +**Possible values:** Any positive integer; represents milliseconds + +**Default:** Provisioned + +### 6.3.3 RSVP Release + +**Signal Name:** RSVP Release +**Signal ID:** release (0x0003) +**Description:** This signal triggers the MG to send an appropriate RSVP Teardown message for the resource reservation session. +**Signal Type:** Brief +**Duration:** Not applicable to Brief signals + +#### 6.3.3.1 Additional parameters + +##### 6.3.3.1.1 Session ID + +**Parameter Name:** Session ID +**Parameter ID:** session (0x0001) +**Description:** This parameter relates to RSVP object "SESSION". +**Type:** Octet String +**Optional:** No +**Possible values:** A sequence of octets +**Default:** None + +##### 6.3.3.1.2 Message Type + +**Parameter Name:** Message Type +**Parameter ID:** mtype (0x0002) +**Description:** This parameter represents the type of the Teardown message. +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "PathTear" (0x0001) +"ResvTear" (0x0002) +**Default:** None + +## 6.4 Statistics + +None. + +## 6.5 Error codes + +None. + +## 6.6 Procedures + +### 6.6.1 RSVP processing ways in the RSVP-aware ITU-T H.248 MG + +There are different possible ways of RSVP processing in an ITU-T H.248 MG, a *termination* way, a *snooping* way or a *proxy* way (see, e.g., Figure 15 of [ITU-T Y.2111] "Three possible QoS signalling processing ways at the PE-FE"). The particular RSVP processing shall *not* impact the ITU-T H.248 procedures as such. + +### 6.6.2 RSVP messages processing + +RSVP makes resource reservations for unidirectional data flows, so in the normal bidirectional cases, the MGC and the MG need to maintain two separate RSVP sessions. The MG plays different roles in the two sessions, i.e., sender and receiver of the two unidirectional data flows. + +#### 6.6.2.1 MG at the receiver side + +When the MGC and the MG act as a receiver of the data flow, the MG receives RSVP Path messages sent by the sender and sends RSVP reservation request (Resv) messages upstream towards the sender. + +Based on the first received Path message, the MG creates the path state for the session and reports the request event (*rsvp/pathr*) to the MGC via the Notify Command. This is similar to the policy pull procedures. The MGC makes the resource reservation decision based on the reported event and relevant parameters, after which the MGC instructs the MG to set up the bearer path with a desired QoS. This can be achieved by sending the *rsvp/resv* signal via a MODIFY Command, which triggers the MG to send an RSVP Resv message for the resource reservation session. RSVP takes a "soft state" approach to managing the reservation state, the 'Time Value' parameter within this signal indicates the refresh period of the resv messages. If there is no update *rsvp/resv* or *rsvp/release* signal sent from the MGC, the MG should resend the resv messages automatically after every refresh period. For the incoming direction, the MG may receive refresh Path messages including duplicated ones and updated ones. Only the update Path message would modify the path state of the session and trigger the notification of the *rsvp/pathr* event. + +The MG is also required to be aware of the other types of RSVP messages. This is achieved by the MGC setting the appropriate events on the MG. When an RSVP ResvErr message is received, the MG should notify the *rsvp/resverr* event to the MGC. Furthermore, if the Confirm Flag parameter is set to 'ON' in the *rsvp/resv* signal, the MG would receive the RSVP ResvConf message after the reservation request is accepted by the bearer path. The MG should then notify the *rsvp/resvconf* event to the MGC based on the ResvConf message it received. The MG may also receive the explicit teardown message PathTear, at that time, the MG deletes the path state that is saved for the session and triggers a *rsvp/teardown* event notification. + +When the MGC wants to release the RSVP session (according to the policy decision for the bearer path), the MGC sends the *rsvp/release* signal to the MG via ITU-T H.248 Commands, which triggers the MG to send a RSVP ResvTear message. + +#### 6.6.2.2 MG at the sender side + +In the case where the MGC and the MG act as a sender of the data flow, the MGC controls the MG in order to maintain an RSVP session. The MG would then construct the appropriate RSVP messages and send them to the receivers. + +The initiation of the RSVP session can be achieved by sending the *rsvp/path* signal to the MG. This would trigger the MG to send out a RSVP Path message, which is used to create the bearer path between the MG and the data flow receivers. The 'Time Value' parameter within this signal indicates the refresh period of the path messages. If there is no update *rsvp/path* or *rsvp/release* signal received for the RSVP session, the MG should resend the path message automatically after every refresh period to maintain the path state on the bearer path. + +The MG should be aware of the reception of the other types of RSVP messages. This is achieved by the MGC setting the appropriate events on the MG. When the very first RSVP Resv message is received, the MG creates the reservation state for the session and reports the *rsvp/resvr* event with the relevant parameters to the MGC via the Notify Command. After that, only the update Resv message received by the MG would modify the reservation state of the session and trigger the notification of the *rsvp/resvr* event. An RSVP PathErr message should trigger the notification of the *rsvp/patherr* event to the MGC. The MG may also receive the explicit teardown message ResvTear, + +at that time, the MG deletes the reservation state that is saved for the session and triggers a *rsvp/teardown* event notification. + +When the MGC wants to stop the data flow, the MGC sends the *rsvp/release* signal to the MG via ITU-T H.248 Commands, which triggers the MG to send an RSVP PathTear message to the receiver. + +#### **6.6.2.3 RSVP session state maintenance** + +RSVP takes a soft state approach for managing the session state along the bearer path. When the MG acts as a sender or a receiver in a RSVP session, the session state (path state and reservation state) is also created and maintained in the MG. This session state is periodically refreshed by the Path and Resv messages, including the duplicated messages and updated messages that carry the same Session ID. + +If no matching refresh message arrives before the expiration of a "cleanup timeout" interval, the session state expires. For example, when the MG acts as a sender of the data flow, there is no Resv message received by the MG at the time interval; when the MG acts as a receiver of the data flow, there is no Path message received by the MG at the time interval. In these cases, the related RSVP sessions are expired. + +To enable the notification of the state expiration to be sent, the event *rsvp/se* with the *sei* parameter is set by the MGC on the applicable termination. This parameter sets the time period between the last RSVP refresh message received and the generation of the *rsvp/se* event. This timer is reset by any refresh message for the indicated RSVP session. The MG can detect whether the session state has expired based on this timer parameter which specifies the cleanup timeout interval. If the session state expires, the MG should notify the *rsvp/se* event to the MGC. + +On receipt of the state expiration event, the MGC makes a resource decision and may then release the related session. + +### **6.6.3 Encapsulation of the authorization token** + +#### **6.6.3.1 Overview of relevant RSVP-related RFCs** + +RSVP is a purpose-designed resource reservation control protocol. This Recommendation only considers the aspect of policy control, which is just a small subset capability of the entire RSVP. Figure 1 provides an overview of relevant RSVPs. + +![Flowchart showing the landscape of important RSVP-related RFCs. It starts with IETF RFC 2205 (Resource ReSerVation Protocol - Version 1) which provides a placeholder for the POLICY_DATA object. This leads to IETF RFC 2750 (RSVP Extensions for Policy Control) which defines the base format for the POLICY_DATA object. This leads to IETF RFC 3182 (Identity Representation for RSVP) which defines the authentication policy element (AUTH_DATA) encapsulated in the POLICY_DATA object. This leads to IETF RFC 3520 (Session Authorization Policy Element) which defines the session authorization policy element (AUTH_SESSION) encapsulated in the POLICY_DATA object. IETF RFC 3521 (Framework for Session Set-up with Media Authorization) defines a framework and illustrates the media authorization concepts using SIP for session signalling, RSVP for resource reservation, and also points to IETF RFC 3520.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +RSVP - Main RFCs for Policy Control + +``` + +graph TD + RFC2205["IETF RFC 2205 +Resource ReSerVation +Protocol - Version 1 +09/1997"] -- "provides placeholder +for POLICY_DATA object +(the 'policy data' element +for policy control)" --> RFC2750["IETF RFC 2750 +RSVP Extensions +for Policy Control +01/2000"] + RFC2750 -- "defines base format +for POLICY_DATA object" --> RFC3182["IETF RFC 3182 +Identity Representation +for RSVP +10/2001"] + RFC3182 -- "defines the authentication +policy element (AUTH_DATA) +encapsulated in the +POLICY_DATA object" --> RFC3520["IETF RFC 3520 +Session Authorization +Policy Element +04/2003"] + RFC3521["IETF RFC 3521 +Framework for Session +Set-up with Media +Authorization +04/2003"] -- "defines a framework; +illustrates the media authorization +concepts using SIP for session signalling, +RSVP for resource reservation" --> RFC3520 + RFC3520 -- "defines session authorization +policy element (AUTH_SESSION) +encapsulated in the POLICY_DATA +object" --> RFC3520 + +``` + +Flowchart showing the landscape of important RSVP-related RFCs. It starts with IETF RFC 2205 (Resource ReSerVation Protocol - Version 1) which provides a placeholder for the POLICY\_DATA object. This leads to IETF RFC 2750 (RSVP Extensions for Policy Control) which defines the base format for the POLICY\_DATA object. This leads to IETF RFC 3182 (Identity Representation for RSVP) which defines the authentication policy element (AUTH\_DATA) encapsulated in the POLICY\_DATA object. This leads to IETF RFC 3520 (Session Authorization Policy Element) which defines the session authorization policy element (AUTH\_SESSION) encapsulated in the POLICY\_DATA object. IETF RFC 3521 (Framework for Session Set-up with Media Authorization) defines a framework and illustrates the media authorization concepts using SIP for session signalling, RSVP for resource reservation, and also points to IETF RFC 3520. + +**Figure 1 – RSVP – Landscape of important RSVP-related RFCs, relevant for policy control** + +RSVP messages in general carry a *set of objects*. The POLICY\_DATA object is the relevant one from a policy control point of view. This object may contain an authorization token (see clause 3.2.1 in [ITU-T H.248.55]). + +#### 6.6.3.2 Encapsulation procedure: forwarding the authorization token from RSVP to ITU-T H.248 + +The POLICY\_DATA object may carry different information elements. The AUTH\_DATA element [IETF RFC 3182] and AUTH\_SESSION element [IETF RFC 3520] are just two examples; there may also be other types of policy data. However, the specific content shall be transparent for the MG and is thus not relevant in the scope of pull mode packages. + +The RSVP POLICY\_DATA objects are to be forwarded as is, without any modification. This means that the MG transparently encapsulates the POLICY\_DATA object into the ObservedEventsDescriptor parameter *authok* of the *plm* events *rdrr*, *rdrm* and *rdrl*. The particular ITU-T H.248 event depends on the RSVP message type (see next clause). + +### 6.6.4 RSVP message to ITU-T H.248 event mapping + +There are seven basic RSVP message types defined by [IETF RFC 2205]. Further RSVP message types are defined by extension specifications. Just four RSVP message types are relevant for *successful* policy control, see Tables 1 and 2. + +**Table 1 – RSVP message to ITU-T H.248 event mapping when the MG acts as data receiver** + +| RSVP message type | may trigger | H.248.55 event type | H.248.65 event type | Comment | +|-------------------|-------------|---------------------|----------------------|--------------------------| +| Path | → | plm/rdrr | rsvp/pathr | Reservation | +| Path(update) | → | plm/rdrm | rsvp/pathr | Modification | +| Resv | – | – | – | Not applicable | +| PathTear | → | plm/rdrl | rsvp/teardown | Release | +| ResvTear | – | – | – | Not applicable | +| PathErr | – | – | – | Not applicable | +| ResvErr | → | – | rsvp/resverr | Error | +| ResvConf | → | – | rsvp/resvconf | Reservation confirmation | + +**Table 2 – RSVP message to ITU-T H.248 event mapping when the MG acts as data sender** + +| RSVP message type | may trigger | H.248.55 event type | H.248.65 event type | Comment | +|-------------------|-------------|---------------------|----------------------|----------------| +| Path | – | – | – | Not applicable | +| Resv | → | plm/rdrr | rsvp/resvr | Reservation | +| Resv(update) | → | plm/rdrm | rsvp/resvr | Modification | +| PathTear | – | – | – | Not applicable | +| ResvTear | → | plm/rdrl | rsvp/teardown | Release | +| PathErr | → | – | rsvp/patherr | Error | +| ResvErr | – | – | – | Not applicable | +| ResvConf | – | – | – | Not applicable | + +When the MGC and the MG act as a receiver of the data flow, the MG receives Path messages and sends out Resv messages. The first Path message initiating the RSVP session can be considered as a trigger of the reservation. The following refresh Path messages, if they contain updated information, can be treated as a session modification. The PathTear message is the explicit way to tear down the session, it may trigger the *plm/rdrl* event. In this case, Resv and ResvTear messages are sent with the instructions specified by the MGC. They do not trigger any events on the MG. See Table 1 above for the detailed mappings. + +When the MGC and the MG act as a sender of the data flow, the MG sends Path messages and receives Resv messages. The first Resv message makes the reservation which may then trigger the *plm/rdrr* event. The following refresh Resv messages, if they contain updated information, can be treated as a session modification. The ResvTear message is the explicit way to tear down the session, it may trigger the *plm/rdrl* event. In this case, Path and PathTear messages are sent with the instructions specified by the MGC. They do not trigger any events on the MG. See Table 2 above for the detailed mappings. + +### 6.6.5 ITU-T H.248 reporting of RSVP flow specifications + +The RSVP flow specification specifies the desired QoS of the session and it may provide additional information for policy control. This information is always carried in a RSVP Resv message. When the MG acts as a sender of the data flow, the PDP (MGC) may subscribe to the *rsvp/resvr* event. The PEP (MG) shall then report the flow specification when the correspondent RSVP message is carrying a FLOWSPEC object (besides the POLICY\_DATA object). + + + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.66-201604-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/H/T-REC-H.248.66-201604-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ebbe203f4ad54db18e9005e2f037ea51c672277 --- /dev/null +++ b/marked/H/T-REC-H.248.66-201604-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:312e320a77656045c274ba104b0bd86ccd8146530c93985198e6eda41752a12d +size 15125 diff --git a/marked/H/T-REC-H.248.66-201604-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.248.66-201604-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/H/T-REC-H.248.66-201604-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/H/T-REC-H.248.66-201604-I_PDF-E/2c38051409fe1c92ed774b445a768886_img.jpg b/marked/H/T-REC-H.248.66-201604-I_PDF-E/2c38051409fe1c92ed774b445a768886_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de656bca5bd5bdb870d277c1f28c45cc164ba16f --- /dev/null +++ b/marked/H/T-REC-H.248.66-201604-I_PDF-E/2c38051409fe1c92ed774b445a768886_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfe3c84dfe7c9fb8812660e48139e714d897d9a8ed6c2595cc968231454fddc2 +size 29333 diff --git a/marked/H/T-REC-H.248.70-200903-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/H/T-REC-H.248.70-200903-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef3ceca0671351626d4f142fcb9b2960ab85312d --- /dev/null +++ b/marked/H/T-REC-H.248.70-200903-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6405299096f42c7a32ec4433974f1d8318e3128845f32a1cb9d8cf2ebd87cb02 +size 21513 diff --git a/marked/H/T-REC-H.248.70-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.70-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/H/T-REC-H.248.70-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/H/T-REC-H.248.70-200903-I_PDF-E/raw.md b/marked/H/T-REC-H.248.70-200903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ca2d78c7562d078499666d85d81ff53cd7e0cc2f --- /dev/null +++ b/marked/H/T-REC-H.248.70-200903-I_PDF-E/raw.md @@ -0,0 +1,467 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.70** + +(03/2009) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: Dialling method information packages** + +Recommendation ITU-T H.248.70 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +### **Recommendation ITU-T H.248.70** + +# **Gateway control protocol: Dialling method information packages** + +## **Summary** + +Recommendation ITU-T H.248.70 defines three packages: dmi, xdmi and edmi, that extend the dd, xdd and edd packages, respectively. The new packages support a mechanism to provide information to the MGC regarding the dialling method (DTMF or decadic pulses) associated with the detected digit or digitmap. + +## **Source** + +Recommendation ITU-T H.248.70 was approved on 16 March 2009 by ITU-T Study Group 16 (2009-2012) under Recommendation ITU-T A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | Page | +|-------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Dialling method information package ..... | 2 | +| 6.1 Properties..... | 2 | +| 6.2 Events ..... | 3 | +| 6.3 Signals ..... | 3 | +| 6.4 Statistics..... | 3 | +| 6.5 Error Codes..... | 3 | +| 6.6 Procedures ..... | 4 | +| 7 Dial method information package for extended digitmap detection ..... | 4 | +| 7.1 Properties..... | 4 | +| 7.2 Events ..... | 4 | +| 7.3 Signals ..... | 5 | +| 7.4 Statistics..... | 5 | +| 7.5 Error Codes..... | 5 | +| 7.6 Procedures ..... | 5 | +| 8 Dial method information package for enhanced digitmap detection..... | 5 | +| 8.1 Properties..... | 6 | +| 8.2 Events ..... | 6 | +| 8.3 Signals ..... | 6 | +| 8.4 Statistics..... | 7 | +| 8.5 Error Codes..... | 7 | +| 8.6 Procedures ..... | 7 | +| Bibliography..... | 8 | + + + +# Gateway control protocol: Dialling method information packages + +# 1 Scope + +This Recommendation defines three packages: dmi, xdmi and edmi, that extend the dd, xdd and edd packages, respectively. The new packages support a mechanism to provide information to the MGC regarding the dialling method (DTMF or decadic pulses) associated with the detected digit or digitmap. + +The DTMF detection packages dd, xdd and edd are commonly used to not only detect DTMF digits but also decadic pulsed (i.e., loop disconnect) digits. + +Figure 1 shows an interworking scenario between legacy terminals and an H.323 network [b-ITU-T H.323]. + +![Diagram showing interworking between legacy equipment and an H.323 network. A box labeled 'Legacy User Equipment (terminals, PBXs)' is connected to a box labeled 'AGW'. The 'AGW' is connected to a cloud labeled 'H.323'. Above the 'AGW' is a box labeled 'MGC', which is connected to the 'AGW' and has a dashed line connection to the 'H.323' cloud.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) + +``` +graph LR; LUE[Legacy User Equipment (terminals, PBXs)] --- AGW[AGW]; AGW --- H323((H.323)); MGC[MGC] --- AGW; MGC -.- H323; +``` + +Diagram showing interworking between legacy equipment and an H.323 network. A box labeled 'Legacy User Equipment (terminals, PBXs)' is connected to a box labeled 'AGW'. The 'AGW' is connected to a cloud labeled 'H.323'. Above the 'AGW' is a box labeled 'MGC', which is connected to the 'AGW' and has a dashed line connection to the 'H.323' cloud. + +**Figure 1 – Interworking between legacy equipment and a H.323 network [b-ITU-T H.323]** + +In the scenario of Figure 1, when a call is established and has reached the speech phase, the media gateway controller (MGC) may order the access gateway (AGW) to start DTMF detection (e.g., due to a H.323 application). This is in order to transfer "in-band" digits to the H.323 network. Digits can be conveyed in the control plane toward the H.323 network via the H.245 UserInputIndication message [b-ITU-T H.245]. + +In some scenarios, the dialling method by which the detected digit was generated is of relevance to the MGC. + +For example: + +If a DTMF digit 1 is received, the MG will report it correctly (i.e., with the dd/d1 event). + +However, if loop disconnect (LD) dialling is used on the line, a problem may occur if the PSTN user signals a REGISTER RECALL pulsed signal to initiate an enquiry call. In some markets, the duration of the REGISTER RECALL pulsed signal overlaps with that of LD digit 1. Therefore, the AGW would report the signal as being "Digit 1" rather than RECALL/HOOKFLASH which results in incorrect call behaviour. + +This Recommendation defines extension packages that allow a MGC to determine the dialling method associated with a detected digit. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*. + +[ITU-T H.248.16] Recommendation ITU-T H.248.16 (2002), *Gateway control protocol: Enhanced digit collection packages and procedures*. + +# 3 Definitions + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------------------| +| AGW | Access Gateway | +| DTMF | Dual-Tone Multi-Frequency | +| LD | Loop Disconnect | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| PBX | Private Branch Exchange | +| PSTN | Public Switched Telecommunications Network | + +# 5 Conventions + +None. + +# 6 Dialling method information package + +**Package Name:** Digit Dialling Method Information + +**Package ID:** dmi (0x00f2) + +**Description:** This package defines an event parameter that may be used by all DTMF Detection Package events [ITU-T H.248.1]. This parameter allows the MGC to determine whether a detected digit reported by the MG was generated with DTMF or with decadic pulses (i.e., loop disconnect). + +**Version:** 1 + +**Extends:** dd (0x0006) version 2 + +## 6.1 Properties + +None. + +## 6.2 Events + +This package does not define any new event. The event parameter defined in this package can be used with any of the events of the base package i.e., *dmi/std*, *dmi/etd*, *dmi/ltd*, *dmi/d0*, *dmi/d1*, *dmi/d2*, *dmi/d3*, *dmi/d4*, *dmi/d5*, *dmi/d6*, *dmi/d7*, *dmi/d8*, *dmi/d9*, *dmi/da*, *dmi/db*, *dmi/dc*, *dmi/dd*, *dmi/ds*, *dmi/do*, *dmi/ce*. + +### 6.2.1 EventsDescriptor parameters + +#### 6.2.1.1 Dialling method required + +**Parameter Name:** Dialling Method Required + +**Parameter ID:** dmr (0x00a0) + +**Description:** Indicates that the MGC requires to be informed of the dialling type associated with the digits to be reported. + +**Type:** Boolean + +**Optional:** Yes + +**Possible values:** "ON": Report dialling method. +"OFF": Do not report dialling method. + +**Default:** "OFF" + +### 6.2.2 ObservedEventsDescriptor parameters + +#### 6.2.2.1 Dialling method + +**Parameter Name:** Dialling Method + +**Parameter ID:** dm (0x00a0) + +**Description:** Indicates the dialling method associated with the reported dialled digits. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** "DTMF" (0x0001) Digit was generated with DTMF. +"LD" (0x0002) Digit was generated with decadic pulses (i.e., loop disconnect). + +**Default:** "DTMF" + +## 6.3 Signals + +None. + +## 6.4 Statistics + +None. + +## 6.5 Error Codes + +None. + +## 6.6 Procedures + +If the MGC wishes to be informed of the dialling method, it shall include the *Dialling Method Required* event parameter set to ON in any of the following events: + +*dmi/std, dmi/etd, dmi/ltd, dmi/d0, dmi/d1, dmi/d2, dmi/d3, dmi/d4, dmi/d5, dmi/d6, dmi/d7, dmi/d8, dmi/d9, dmi/da, dmi/db, dmi/dc, dmi/dd, dmi/ds, dmi/do, dmi/ce.* + +If this event parameter is set to ON and the digit was dialled with decadic pulses, the MG shall include the *Dialling Method* parameter when notifying the event to the MGC. If the *Dialling Method Required* event parameter is set to ON and the digit was dialled with DTMF, the MG does not need to, but is allowed to, include the *Dialling Method* parameter when notifying the event to the MGC. If the *Dialling Method Required* event parameter is set to OFF or is not included, the MG shall not include the *Dialling Method* parameter when notifying the event to the MGC, regardless of which method the digit was dialled with. + +On being informed of the type of digit transmission/detection, the MGC can correctly interpret the received digit based on the current call state. + +# 7 Dial method information package for extended digitmap detection + +**Package Name:** Digit Dialling Method Information for Extended Digitmap Detection + +**Package ID:** xdmi (0x00f3) + +**Description:** This package defines an event parameter that may be used by all the extended DTMF detection package events [ITU-T H.248.16]. This parameter allows the MGC to determine whether a detected digit reported by the MG was generated with DTMF or with decadic pulses (i.e., loop disconnect). + +**Version:** 1 + +**Extends:** xdd (0x0052) version 1 + +## 7.1 Properties + +None. + +## 7.2 Events + +This package does not define any new event. The event parameter defined in this package can be used with any of the events of the base package, i.e., *xdmi/std, xdmi/etd, xdmi/ltd, xdmi/d0, xdmi/d1, xdmi/d2, xdmi/d3, xdmi/d4, xdmi/d5, xdmi/d6, xdmi/d7, xdmi/d8, xdmi/d9, xdmi/da, xdmi/db, xdmi/dc, xdmi/dd, xdmi/ds, xdmi/do, xdmi/ce, xdmi/xce.* + +### 7.2.1 EventsDescriptor parameters + +#### 7.2.1.1 Dialling method required + +**Parameter Name:** Dialling Method Required + +**Parameter ID:** dmr (0x00a0) + +**Description:** Indicates that the MGC requires to be informed of the dialling method associated with the digits to be reported. + +**Type:** Boolean + +**Optional:** Yes + +**Possible values:** "ON": Report dialling method. +"OFF": Do not report dialling method. + +**Default:** "OFF" + +### 7.2.2 ObservedEventsDescriptor parameters + +#### 7.2.2.1 Dialling method + +**Parameter Name:** Dialling Method + +**Parameter ID:** dm (0x00a0) + +**Description:** Indicates the dialling method associated with the reported dialled digits. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** "DTMF" (0x0001) Digit was generated with DTMF. +"LD" (0x0002) Digit was generated with decadic pulses (i.e., loop disconnect). + +**Default:** "DTMF" + +## 7.3 Signals + +None. + +## 7.4 Statistics + +None. + +## 7.5 Error Codes + +None. + +## 7.6 Procedures + +If the MGC wishes to be informed of the dialling method, it shall include the *Dialling Method Required* event parameter set to ON in any of the following events: + +*xdm/std, xdm/etd, xdm/ltl, xdm/d0, xdm/d1, xdm/d2, xdm/d3, xdm/d4, xdm/d5, xdm/d6, xdm/d7, xdm/d8, xdm/d9, xdm/da, xdm/db, xdm/dc, xdm/dd, xdm/ds, xdm/do, xdm/ce, xdm/xce.* + +If this event parameter is set to ON and the digit was dialled with decadic pulses, the MG shall include the *Dialling Method* parameter when notifying the event to the MGC. If the *Dialling Method Required* event parameter is set to ON and the digit was dialled with DTMF, the MG does not need to, but is allowed to, include the *Dialling Method* parameter when notifying the event to the MGC. If the *Dialling Method Required* event parameter is set to OFF or is not included, the MG shall not include the *Dialling Method* parameter when notifying the event to the MGC, regardless of which method the digit was dialled with. + +On being informed of the type of digit transmission/detection, the MGC can correctly interpret the received digit based on the current call state. + +# 8 Dial method information package for enhanced digitmap detection + +**Package Name:** Digit Dialling Method Information for Enhanced Digitmap Detection + +**Package ID:** edmi (0x00f4) + +**Description:** This package defines an event parameter that may be used by all the enhanced DTMF detection package events [ITU-T H.248.16]. This parameter allows the MGC to determine whether a detected digit reported by the MG was generated with DTMF or with decadic pulses, i.e., loop disconnect. + +**Version:** 1 + +**Extends:** edd (0x0066) version 1 + +## 8.1 Properties + +None. + +## 8.2 Events + +This package does not define any new event. The event parameter defined in this package can be used with any of the events of the base package i.e., *edmi/std*, *edmi/etd*, *edmi/ltd*, *edmi/d0*, *edmi/d1*, *edmi/d2*, *edmi/d3*, *edmi/d4*, *edmi/d5*, *edmi/d6*, *edmi/d7*, *edmi/d8*, *edmi/d9*, *edmi/da*, *edmi/db*, *edmi/dc*, *edmi/dd*, *edmi/ds*, *edmi/do*, *edmi/ce*, *edmi/xce*, *edmi/mce*. + +### 8.2.1 EventsDescriptor parameters + +#### 8.2.1.1 Dialling method required + +**Parameter Name:** Dialling Method Required + +**Parameter ID:** dmr (0x00a0) + +**Description:** Indicates that the MGC requires to be informed of the dialling method associated with the digits to be reported. + +**Type:** Boolean + +**Optional:** Yes + +**Possible values:** "ON": Report dialling method. +"OFF": Do not report dialling method. + +**Default:** "OFF" + +### 8.2.2 ObservedEventsDescriptor parameters + +#### 8.2.2.1 Dialling method + +**Parameter Name:** Dialling Method + +**Parameter ID:** dm (0x00a0) + +**Description:** Indicates the type of dialled digits that are being reported. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** "DTMF" (0x0001) Digit was generated with DTMF. +"LD" (0x0002) Digit was generated with decadic pulses (i.e., loop disconnect). + +**Default:** "DTMF" + +## 8.3 Signals + +None. + +## 8.4 Statistics + +None. + +## 8.5 Error Codes + +None. + +## 8.6 Procedures + +If the MGC wishes to be informed of the dialling method, it shall include the *Dialling Method Required* event parameter set to ON in any of the following events: + +*edmi/std, edmi/etd, edmi/ltd, edmi/d0, edmi/d1, edmi/d2, edmi/d3, edmi/d4, edmi/d5, edmi/d6, edmi/d7, edmi/d8, edmi/d9, edmi/da, edmi/db, edmi/dc, edmi/dd, edmi/ds, edmi/do, edmi/ce, edmi/xce, edmi/mce.* + +If this event parameter is set to ON and the digit was dialled with decadic pulses, the MG shall include the *Dialling Method* parameter when notifying the event to the MGC. If the *Dialling Method Required* event parameter is set to ON and the digit was dialled with DTMF, the MG does not need to, but is allowed to, include the *Dialling Method* parameter when notifying the event to the MGC. If the *Dialling Method Required* event parameter is set to OFF or is not included, the MG shall not include the *Dialling Method* parameter when notifying the event to the MGC, regardless of which method the digit was dialled with. + +On being informed of the type of digit transmission/detection, the MGC can correctly interpret the received digit based on the current call state. + +# Bibliography + +- [b-ITU-T H.245] Recommendation ITU-T H.245 (2008), *Control protocol for multimedia communication.* +- [b-ITU-T H.323] Recommendation ITU-T H.323 (2006), *Packet-based Multimedia communication systems.* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.71-201002-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.248.71-201002-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5d2507eae6a823ad77a86e0410262772cc9dd0f --- /dev/null +++ b/marked/H/T-REC-H.248.71-201002-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ea88d57dc0057c0e037d958dc06c9fa64ced0ab4c581b93c110ce18241897e0 +size 55644 diff --git a/marked/H/T-REC-H.248.71-201002-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.248.71-201002-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8a2ff0b6fb514898a0f075058679b07a6320189 --- /dev/null +++ b/marked/H/T-REC-H.248.71-201002-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2eeaadb146a85afb2ebe945c27b37c5476f906a68c6f84d60579566d3396d1e +size 7496 diff --git a/marked/H/T-REC-H.248.71-201002-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.248.71-201002-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69bbecd70f1bf25c5a196e642f2f51c212280e13 --- /dev/null +++ b/marked/H/T-REC-H.248.71-201002-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49d25e9cc5aced893573b0784f1fae16f9f31bb526069105d295a1c36bb4d646 +size 50601 diff --git a/marked/H/T-REC-H.248.71-201002-I_PDF-E/raw.md b/marked/H/T-REC-H.248.71-201002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..79ad25a84f414bd2e0297d2c0a93ce63719c93f1 --- /dev/null +++ b/marked/H/T-REC-H.248.71-201002-I_PDF-E/raw.md @@ -0,0 +1,772 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.71** + +(02/2010) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +# --- **Gateway control protocol: RTCP support packages** + +Recommendation ITU-T H.248.71 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, and the text "ITU International Telecommunication Union" to the right. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.248.71 + +# Gateway control protocol: RTCP support packages + +## Summary + +Recommendation ITU-T H.248.71 defines three ITU-T H.248 packages that relate to the real-time control protocol (RTCP). The RTCP Source Description package, the Received RTCP package, and the RTCP Feedback Message package allow the media gateway controller (MGC) to monitor and control RTCP flows that are terminated by (or that pass through) a media gateway (MG). + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.248.71 | 2010-02-13 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | | +|-----|-------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | RTCP source description package ..... | 3 | +| 6.1 | Properties..... | 3 | +| 6.2 | Events ..... | 3 | +| 6.3 | Signals ..... | 3 | +| 6.4 | Statistics..... | 3 | +| 6.5 | Error codes..... | 4 | +| 6.6 | Procedures ..... | 5 | +| 7 | Received RTCP package ..... | 6 | +| 7.1 | Properties..... | 6 | +| 7.2 | Events ..... | 6 | +| 7.3 | Signals ..... | 6 | +| 7.4 | Statistics..... | 6 | +| 7.5 | Error codes..... | 8 | +| 7.6 | Procedures ..... | 8 | +| 8 | RTCP feedback message package ..... | 12 | +| 8.1 | Properties..... | 12 | +| 8.2 | Events ..... | 12 | +| 8.3 | Signals ..... | 14 | +| 8.4 | Statistics..... | 15 | +| 8.5 | Error codes..... | 15 | +| 8.6 | Procedures ..... | 15 | + + + +# Gateway control protocol: RTCP support packages + +# 1 Scope + +This Recommendation defines several ITU-T H.248 packages that relate to RTCP flows that terminate at or pass through the MG. + +The *RTCP Source Description* package maps information appearing in sent and received RTCP Source Description (SDES) packets into ITU-T H.248 statistics. Auditing these statistics allows the MGC to gain a better understanding of the RTP end-systems and intermediate systems that participate in an RTP session. + +The *Received RTCP* package maps information appearing in received RTCP Sender Report and Receiver Report packets into ITU-T H.248 statistics. By auditing these statistics, the MGC can collect performance and QoS metrics, measured by the remote participants of the RTP session. + +The *RTCP Feedback Message* package allows the MGC to be notified when the MG receives RTCP feedback messages, and to instruct the MG to send such messages. RTCP feedback messages are used by RTP Audio Visual Profiles with feedback extensions (see [IETF RFC 4585]). + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*, including its Amendment 2 (2009). +- [ITU-T M.2301] Recommendation ITU-T M.2301 (2002), *Performance objectives and procedures for provisioning and maintenance of IP-based networks*. +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- [IETF RFC 3629] IETF RFC 3629 (2003), *UTF-8, a transformation format of ISO 10646*. +- [IETF RFC 4585] IETF RFC 4585 (2006), *Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)*. +- [IETF RFC 5104] IETF RFC 5104 (2008), *Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +**3.1.1 RTP end-system** [IETF RFC 3550]: An application that generates the content to be sent in RTP packets and/or consumes the content of received RTP packets. + +**3.1.2 RTP mixer** [IETF RFC 3550]: An intermediate system that receives RTP packets from one or more sources, possibly changes the data format, combines the packets in some manner and then forwards a new RTP packet. All RTP packets originating from a mixer are identified as having the mixer as their synchronization source. + +**3.1.3 RTP translator** [IETF RFC 3550]: An intermediate system that forwards RTP packets with their synchronization source identifier intact. Examples of translators include devices that convert encodings without mixing, replicators from multicast to unicast, and application-level filters in firewalls. + +NOTE – The RTP translator concept is further refined in [b-IETF RFC 5117] into "RTP transport translator" and "RTP media translator". For the purposes of this Recommendation, there is no difference between the two. + +## **3.2 Terms defined in this Recommendation** + +**3.2.1 measurement point (MP)** (adapted from [ITU-T M.2301]): An MP is the physical or logical point at which measurements can be made and to which the data obtained is related. In the context of RTP and RTCP, any source of RTCP packets is a measurement point. Its measurement data is based on the RTP and RTCP traffic sent and received at that element. + +**3.2.2 reporting point (RP)**: This is the point at which the measurement data is reported to another network element. In the context of RTP and RTCP, any source of RTCP packets is a reporting point, where the measurement data is reported through RTCP. In addition, any ITU-T H.248 MG is a reporting point, when reporting various measurement data through ITU-T H.248 statistics. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------| +| ABNF | Augmented Backus-Naur Form | +| AVPF | Audio Visual Profile with Feedback | +| CNAME | Canonical Name | +| FB | Feedback | +| FCI | Feedback Control Information | +| FMT | Feedback Message Type | +| IANA | Internet Addressing and Numbers Authority | +| IP | Internet Protocol | +| LSB | Least Significant Bit | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MP | Measurement Point | +| NAT | Network Address Translation | +| PLI | Picture Loss Indication | +| PSFB | Payload Specific Feedback | +| PT | RTCP control Packet Type | +| RP | Reporting Point | + +| | | +|-------|-------------------------------------------------| +| QoS | Quality of Service | +| RR | RTCP Receiver Report | +| RTP | Real-time Transport Protocol | +| RTCP | RTP Control Protocol | +| RTPFB | Transport layer (RTP) Feedback | +| SDES | Source Description | +| SDP | Session Description Protocol | +| SR | RTCP Sender Report | +| SSRC | Synchronization Source | +| TMMBR | Temporary Maximum Media stream Bit-rate Request | + +# 5 Conventions + +None. + +# 6 RTCP source description package + +Package name: RTCP Source Description Package + +Package ID: rtpsd (0x0104) + +Description: This package defines statistics regarding the information appearing in source description (SDES) RTCP packets, as defined in [IETF RFC 3550]. The statistics detail both information generated locally at the MG and information learnt from remote systems participating in the RTP session. + +Version: 1 + +Extends: None. + +## 6.1 Properties + +None. + +## 6.2 Events + +None. + +## 6.3 Signals + +None. + +## 6.4 Statistics + +### 6.4.1 Local synchronization source + +Statistic name: Local Synchronization Source + +Statistic ID: lssrc (0x0001) + +Description: The RTP synchronization source (SSRC) used by the MG in the RTP and RTCP packets it sends. + +Type: Unsigned Integer + +Possible values: Any +Level: Stream + +### 6.4.2 Remote synchronization source + +Statistic name: Remote Synchronization Source +Statistic ID: rssrc (0x0002) +Description: The RTP synchronization source (SSRC) appearing in RTCP packets received from remote RTP systems (end-systems, mixers or translators). Note that a single RTP session may have more than one remote system (e.g., in multicast sessions). +Type: Sub-list of Unsigned Integer. Each element in the sub-list represents the SSRC of one remote system. +Possible values: Any. If the MG does not yet know the SSRC of any remote system (e.g., because no RTCP packets were yet received), this statistic shall include a single element that is set to zero. +Level: Stream + +### 6.4.3 Local canonical name + +Statistic name: Local Canonical Name +Statistic ID: lename (0x0003) +Description: The canonical name (CNAME) appearing in RTCP SDES packets generated by the MG. +Type: String +Possible values: Any. See clause 6.6.4 for the text encoding of special octets. +Level: Stream + +### 6.4.4 Remote canonical name + +Statistic name: Remote Canonical Name +Statistic ID: rcname (0x0004) +Description: The canonical name (CNAME) appearing in SDES packets received from remote RTP systems (end-systems, mixers or translators). +Type: Sub-list of String. Each element in the Sub-list encodes the CNAME of one remote system. The order of the *rcname* elements shall match the order of the *rssrc* elements. Therefore the *i*-th elements of the *rcname* and *rssrc* statistics contain, respectively, the CNAME and SSRC of one remote system. +Possible values: Any. If the CNAME of a certain system is not yet known, the appropriate sub-list element shall be encoded as a string containing a single minus character (i.e., "-"). See clause 6.6.4 for the text encoding of special octets. +Level: Stream + +## 6.5 Error codes + +None. + +## 6.6 Procedures + +### 6.6.1 Locally generated values + +Some of the statistics of this package (*lssrc* and *lcname*) contain RTCP field values generated by the MG. These statistics shall be available even if the MG is not sending RTCP traffic (e.g., due to other ITU-T H.248 parameters or local configuration). In such a case, the statistics shall include the values that would have been used had the MG sent RTCP traffic. + +### 6.6.2 Received values + +If the *rssrc* and the *rcname* statistics are set on the MG, it populates the statistics relating to remote end-systems and translators based on RTCP packets it receives. Specifically: + +- 1) When the MG receives an RTCP packet, it shall ensure that the SSRC of the packet's sender (i.e., the SSRC appearing in the RTCP header) appears *in the rssrc* statistic, adding it if necessary. +- 2) When the MG receives an SDES RTCP packet, it examines each of that packet's chunks. If the chunk relates to the system that sent the RTCP packet (i.e., if the SSRC appearing in the chunk is identical to the SSRC of the sender), the MG will use that chunk's CNAME item to update the *rcname* statistic. + +This procedure ensures that, in the case of a mixer, the MG will record only the CNAME of the mixer itself, and not the CNAMEs of any of the contributing sources. + +NOTE – It is possible for the MGC to set only one of these statistics on a stream. However such a configuration is of questionable usefulness. + +#### 6.6.2.1 Indicating missing values + +Before the MG receives any RTCP packets from a remote system, the values of the *rssrc* and *rcname* statistics are [0] and ["-"] respectively. The MGC shall interpret this specific combination of values as indicating that no information is available regarding any remote system. + +### 6.6.3 Pruning stale values + +The MG should make sure that values that no longer represent the state of the RTP session are cleared from the statistics. For example: + +- 1) When the MG detects that another system has changed its SSRC, it should remove the values relating to the old SSRC from the statistics. How the MG detects such SSRC changes is implementation-dependent. +- 2) When the MG decides that an SSRC has timed out (e.g., according to the procedures of clause 6.3.5 of [IETF RFC 3550]), it should remove the values relating to that SSRC from the statistics. +- 3) When the MG receives a BYE RTCP packet, it should wait for some interval and then remove the values relating to the packet's SSRC from the statistics. Waiting for a time interval before removing the values is required in order to prevent a race condition where, at the end of a call, the statistics are cleared just before the ITU-T H.248 termination is subtracted (and the statistics are audited). + +### 6.6.4 Encoding UTF-8 strings into ITU-T H.248 strings + +CNAME items appearing in RTCP SDES packets are encoded as a UTF-8 string, according to [IETF RFC 3629]. The *lcname* and *rcname* statistics report such CNAME values, using String as the statistics' type. + +According to clause 12.1.5 of [ITU-T H.248.1], the String statistic type uses the UTF-8 encoding. Therefore, the octets of the CNAME item can be directly copied from the RTCP packet into the statistics. A problem arises, however, when the ITU-T H.248 protocol is using text encoding, as several octet values that are legal in UTF-8 cannot appear in the quotedString ABNF form that is used for the String type (see clause B.2 of [ITU-T H.248.1]). + +The hexadecimal octet values that cannot appear in the quotedString form are listed below: + +00-08 +0b-0c +0e-1f +22 +7f + +Each of these octets represents a single character from the US-ASCII range of UTF-8. Only octet 22 represents a printable character (double-quotes); therefore this is the only octet that can reasonably appear within a CNAME. + +When an MG needs to encode such an octet within one of this package's statistics, it shall convert it to the following octet triplet: + +%xx + +where xx are the hexadecimal digits representing the octet. Note that such an encoding introduces an ambiguity when the "%" character (hexadecimal 25) needs to be encoded. Therefore this character shall also be encoded using the following octet triplet: + +%25 + +# 7 Received RTCP package + +Package name: Received RTCP Package +Package ID: recrtcp (0x00f5) +Description: This package defines statistics that detail information received from the remote systems of an RTCP flow. +Version: 1 +Extends: None. + +## 7.1 Properties + +None. + +## 7.2 Events + +None. + +## 7.3 Signals + +None. + +## 7.4 Statistics + +### 7.4.1 Remote packets sent + +Statistic name: Remote Packets Sent +Statistic ID: rps (0x0001) + +Description: The total number of RTP data packets transmitted by the remote systems since starting transmission; calculated based on the Sender's Packet Count field of received SRs. + +Type: Sub-list of Double + +Possible values: Any non-negative value. + +Level: Termination or Stream + +### 7.4.2 Remote octets sent + +Statistic name: Remote Octets Sent + +Statistic ID: ros (0x0002) + +Description: The total number of payload octets (i.e., not including RTP header or padding) transmitted in RTP data packets by the remote systems since starting transmission; calculated based on the Sender's Octet Count field of received SRs. + +Type: Sub-list of Double + +Possible values: Any non-negative value. + +Level: Termination or Stream + +### 7.4.3 Remote packet loss + +Statistic name: Remote Packet Loss + +Statistic ID: rpl (0x0003) + +Description: The fraction of RTP data packets that each remote system lost between sending the one-before-last and the last SR or RR; as reported in the Fraction Lost field of received SRs/RRs. The fraction is expressed as a percentage value, using a fixed-point notation; a 32-bit whole part and a 32-bit fraction (see also clause E.12.4.3 of [ITU-T H.248.1]). If the loss is negative due to duplicates, the remote packet loss is set to zero. + +NOTE 1 – This statistic is not cumulative, and represents only the loss measured by each remote system between the times when it has sent its last two SRs/RRs. The MGC may periodically audit this statistic, either by issuing AuditValue commands or through the procedures of the Statistic Conditional Reporting package (see [b-ITU-T H.248.47]). + +NOTE 2 – In SR and RR reports, the Fraction Lost field is expressed as an 8-bit fixed point fraction with no whole part. Converting this value to the encoding of the *rpl* statistic amounts to multiplying the value appearing in the SR/RR by a factor of $100 \times 2^{24}$ . + +Type: Sub-list of Double. + +Possible values: A 32-bit whole number and a 32-bit fraction, so that the resulting number is in the range of 0-100. + +Level: Termination or Stream. + +### 7.4.4 Remote cumulative packet loss + +Statistic name: Remote Cumulative Packet Loss + +Statistic ID: repl (0x0004) + +**Description:** The total number of RTP data packets that each remote system lost since the beginning of reception; calculated based on the Cumulative Number of Packets Lost field of received SRs/RRs. This number is defined to be the number of packets expected less the number of packets actually received, where the number of packets received includes any which are late or duplicates. Thus, packets that arrive late are not counted as lost, and the loss may be negative if there are duplicates. If the loss is negative the remote cumulative packet loss is set to zero. + +**Type:** Sub-list of Double + +**Possible values:** Any non-negative value. + +**Level:** Termination or Stream + +### **7.4.5 Remote jitter** + +**Statistic name:** Remote Jitter + +**Statistic ID:** rjit (0x0005) + +**Description:** An estimate of the statistical variance of the RTP data packet inter-arrival time measured by each remote system; as reported in received SRs/RRs. The inter-arrival jitter is measured in the units of the RTP timestamp and defined to be the mean deviation (smoothed absolute value) of the difference in packet spacing at the receiver compared to the sender for a pair of packets (see also clause A.8 of [IETF RFC 3550]). + +NOTE – This statistic is not cumulative, and represents only the momentary jitter measured by each remote system at the time that it has sent its last SR/RR. The MGC may periodically audit this statistic, either by issuing AuditValue commands or through the procedures of the Statistic Conditional Reporting package (see [b-ITU-T H.248.47]). + +**Type:** Unsigned Integer + +**Possible values:** Any + +**Level:** Termination or Stream + +## **7.5 Error codes** + +None. + +## **7.6 Procedures** + +### **7.6.1 Principle of operation** + +The Received RTCP package can only be implemented by ITU-T H.248 streams that contain an incoming RTCP flow. Such a stream could be, for example, a stream representing the combination of an RTP flow and its RTCP flow; or a stream representing the RTCP flow only. + +An overview of the principle behind the package is given in Figure 1. + +A measurement point exists at the remote end of an RTP session, where performance and QoS metrics are maintained regarding the sent and received RTP and RTCP traffic. These metrics are then relayed to the MG through an RTCP reporting point. + +The MG collects the metrics relayed through RTCP, and reports them to the MGC through the statistics of the Received RTCP package. + +![Diagram illustrating the operation of the Received RTCP package. It shows three main components: MGC (Media Gateway Controller), Media Gateway, and Remote RTP Endpoint. The MGC is connected to the Media Gateway via a dashed line labeled 'rtrtcp statistics' and a solid line labeled 'H.248'. The Media Gateway contains a circle labeled 'RP (H.248)'. The Remote RTP Endpoint contains two circles: 'RP (RTCP)' and 'MP (RTP)'. A solid arrow labeled 'RTCP Flow' points from the 'RP (RTCP)' circle in the Remote RTP Endpoint to the 'RP (H.248)' circle in the Media Gateway. A solid arrow labeled 'RTP Flow' points from the 'MP (RTP)' circle in the Remote RTP Endpoint to the Media Gateway. A dashed curved arrow points from the 'RP (RTCP)' circle to the 'MP (RTP)' circle within the Remote RTP Endpoint.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Diagram illustrating the operation of the Received RTCP package. It shows three main components: MGC (Media Gateway Controller), Media Gateway, and Remote RTP Endpoint. The MGC is connected to the Media Gateway via a dashed line labeled 'rtrtcp statistics' and a solid line labeled 'H.248'. The Media Gateway contains a circle labeled 'RP (H.248)'. The Remote RTP Endpoint contains two circles: 'RP (RTCP)' and 'MP (RTP)'. A solid arrow labeled 'RTCP Flow' points from the 'RP (RTCP)' circle in the Remote RTP Endpoint to the 'RP (H.248)' circle in the Media Gateway. A solid arrow labeled 'RTP Flow' points from the 'MP (RTP)' circle in the Remote RTP Endpoint to the Media Gateway. A dashed curved arrow points from the 'RP (RTCP)' circle to the 'MP (RTP)' circle within the Remote RTP Endpoint. + +**Figure 1 – An overview of the Received RTCP package's operation** + +Note that the Received RTCP package does not assume that the MG is the originator of the RTP flow, nor does it assume that it is the final destination of the RTCP flow. In many cases (for example, an IP-to-IP MG providing NAT services), the MG simply relays the RTP/RTCP traffic, while the RTP source is a different network device lying "behind" the MG. + +#### 7.6.1.1 Correspondence with the RTP and network packages + +There is a strong correspondence between the statistics of the Received RTCP package and the statistics of the RTP and Network packages (see [ITU-T H.248.1]). The difference is that the Received RTCP package reports metrics that are measured by remote systems and relayed to the MG through RTCP, while the RTP and Network packages report metrics measured locally at the MG. + +The measurement point and reporting point involved in the statistics of the RTP and Network packages are highlighted in Figure 2. + +![Diagram illustrating the operation of statistics of the RTP and Network packages. It shows three main components: MGC (Media Gateway Controller), Media Gateway, and Remote RTP Endpoint. The MGC is connected to the Media Gateway via a dashed double-headed arrow labeled 'nt and rtp statistics' and a solid double-headed arrow labeled 'H.248'. The Media Gateway contains two sub-components: RP (H.248) and MP (RTP). The RP is connected to the MGC. The MP is connected to the Remote RTP Endpoint via a solid double-headed arrow labeled 'RTP Flow'. A dashed arrow points from the MP to the RP.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Diagram illustrating the operation of statistics of the RTP and Network packages. It shows three main components: MGC (Media Gateway Controller), Media Gateway, and Remote RTP Endpoint. The MGC is connected to the Media Gateway via a dashed double-headed arrow labeled 'nt and rtp statistics' and a solid double-headed arrow labeled 'H.248'. The Media Gateway contains two sub-components: RP (H.248) and MP (RTP). The RP is connected to the MGC. The MP is connected to the Remote RTP Endpoint via a solid double-headed arrow labeled 'RTP Flow'. A dashed arrow points from the MP to the RP. + +**Figure 2 – The operation of statistics of the RTP and Network packages** + +To highlight this similarity, the statistics of the Received RTCP package use the same names as the corresponding statistics of the RTP and Network packages. A "Remote" prefix is added to each statistic of the Received RTCP package, to emphasize that the measurement point is at the remote system. + +### 7.6.2 Collection of received RTCP statistics + +ITU-T H.248 terminations where the statistics defined in this package are set shall record the values appearing in certain fields of RTCP Sender Reports and Receiver Reports received from remote end-systems intermediate-systems (i.e., mixers and translators). These values are then used to calculate the statistics of this package. The MG shall ensure that the value of cumulative statistics (i.e., *rps*, *ros* and *rcpl*) will remain correct even if the corresponding RTCP field has wrapped around (due to the limited number of bits in the RTCP packet). For example, if the remote system has sent $2^{32}+x$ octets, the Sender Octet's Count field of the RTCP SR will wrap-around to $x$ , however the value of the *Remote Octets Sent* statistic would still represent the true number of sent octets (i.e., $2^{32}+x$ ). + +NOTE – For the MG to be able to calculate the correct value of the statistics, it must assume that several RTCP reports are received between any two consecutive wrap-around events. The MG cannot be aware (and therefore cannot maintain the correct statistic value) if multiple wrap-around events of a single field happened between two consecutive reports. A sample algorithm for detecting wrap-around events (through the RTP sequence number) is given in clause A.1 of [IETF RFC 3550]. + +If no appropriate RTCP report was yet received, the value of each statistic shall be set to zero. + +### 7.6.3 RTP flows with a single remote system + +Simple RTP sessions are unicast ones, involving only two RTP end-systems or mixers. In use cases involving such sessions, the Received RTCP package can be used on its own. Each statistic then includes only a single value (i.e., a sub-list of length one), representing the metric reported by the + +remote-end of the RTP session. The MG updates this value following any RTCP SR/RR received from that remote-end. + +### 7.6.4 RTP flows with multiple remote systems + +Some RTP sessions involve more than one remote RTP system. Two examples for such sessions are multicast RTP sessions and RTP sessions that involve quality monitoring RTP translators. In such scenarios, the MG will receive RTCP Sender and/or Receiver Reports from each of these remote systems. In addition, these reports may include report-blocks concerning the RTP packets sent by other senders in the session. + +When the session includes multiple remote systems, the Received RTCP package must be used in conjunction with the RTCP Source Description Package (*rtcpsdes*). *Rtcpsdes Remote Synchronization Source (rtcpsdes/rssrc)* statistic shall be set on any stream that collects any *recrtcp* statistic. Trying to set a *recrtcp* statistic without setting *rtcpsdes/rssrc* shall be rejected using error #472 (Required information missing). + +Each of this package's statistic shall include a list of values, where the *i*-th position in the list corresponds to reports sent by the system represented by the *i* position of the *rtcpsdes/rssrc* statistic. When calculating the statistics of this package, the MG shall only use report blocks concerning RTP packets sent by the MG (i.e., report blocks whose SSRC matches the SSRC used by the MG). Any other report blocks must be ignored. + +As an example, consider an RTP session with three end-systems: + +- 1) The MG, which is a sender and uses SSRC 123. +- 2) Sender A, which uses SSRC 456. +- 3) Receiver B, which uses SSRC 789. + +The MG's *Remote End-System's Synchronization Source* will include the SSRCs of both remote end-systems: + +``` +rtcpsdes/rssrc = [456, 789] +``` + +Each of these package's statistics will also have two values, for example: + +``` +recrtcp/rcpl = [293, 19] +``` + +The first value (293) is based on the Sender Reports sent by A. The second value (19) is based on the Receiver Reports sent by B. + +Each Receiver Report sent by B will include two report-blocks (because there are two senders in the session): one having an SSRC of 123 (dealing with the MG's RTP packets) and one having an SSRC of 456 (dealing with A's RTP packets). The statistics of this package will be based only on the report block dealing with the MG's packets. + +### 7.6.5 Sender-only statistics + +Two statistics of this package, the *Remote Packets Sent (rps)* and *Remote Octets Sent (ros)* are based on Sender Report packets. If no SRs were received from a remote system for the complete duration of the RTP session, these statistics shall be set to zero. If, however, a remote system alternates between sending Sender Reports and Receiver Reports, the reception of an RR shall not reset these statistics to zero. Instead, their value calculated based on the last SR received shall be maintained. + +NOTE – A zero value of the *rps* and *ros* statistics can be used by the MGC to detect remote systems that never send RTP packets (e.g., "pure" receiver end-systems or quality-monitoring RTP translators). + +### 7.6.6 Termination level statistics + +The statistics of this package can be collected both at the stream level and at the termination level. When collected at the termination level, the statistic contains a single value representing the aggregate over all ITU-T H.248 streams and all remote systems. + +Most of these package's statistics are cumulative (see clause 7.1.15 of [ITU-T H.248.1]), and shall be aggregated by summing them. The aggregation of the non-cumulative statistics (*Remote Packet Loss* and *Remote Jitter*) is for future study, and outside the scope of this Recommendation. Some possibilities are to use the average value, a weighted average value or the maximal value among all the remote systems. + +# 8 RTCP feedback message package + +Package name: RTCP Feedback Package + +Package ID: rtpfb (0x00f6) + +Description: This package allows the MGC and MG to coordinate the reception and sending of RTCP Feedback messages. The RTCP Feedback mechanism is defined in [IETF RFC 4585], which defines several types of messages and allows further extension by other specifications (e.g., [IETF RFC 5104]). + +This package contains signals and events that allow a MGC to request an MG to notify it when a particular RTCP feedback message is detected. It also allows the MGC to trigger the MG to send a particular feedback message. + +This is particularly useful in interworking scenarios where a MG bearer level indication must be mapped to a MGC control level indication. One such interworking scenario is between the ITU-T H.245 messages sent by a [b-ITU-T H.324] terminal and the corresponding RTCP messages used by terminals at an RTP-based network. + +Version: 1 + +Extends: None. + +## 8.1 Properties + +None. + +## 8.2 Events + +### 8.2.1 RTCP feedback message detection + +Event name: RTCP Feedback Message Detection + +Event ID: det (0x0001) + +Description: This event is used to receive RTCP Feedback information regarding a media stream. + +#### 8.2.1.1 EventsDescriptor parameters + +##### 8.2.1.1.1 Feedback message type + +Parameter name: Feedback Message Type + +Parameter ID: type (0x0001) + +**Description:** This parameter specifies which RTCP feedback message types are to be detected by the MG and reported to the MGC. This is achieved by indicating the control packet type (PT) and the feedback message type (FMT). The control packet type can either be transport layer feedback (RTPFB) or payload specific feedback (PSFB). + +**Type:** Sub-list of String + +**Optional:** No + +**Possible values:** The sub-list contains one or several bit pattern(s) each with two bytes, encoded as a hexadecimal value. Bit 0 is the most significant bit. + Bits 0-7 represent the FMT. + Bits 8-15 represent the PT. A value of 205 indicates a transport layer FB message. A value of 206 indicates a payload-specific FB message. + See the IANA registry for PT values and FMT values for both the RTPFB and PSFB control packet types, . + For example, to detect the payload specific (payload type value 206) AVPF Picture Loss Indication (PLI) (FMT=1) feedback message, hexadecimal value 0x01CE is used. + For example, to detect the transport specific (payload type value 205) AVPF Temporary Maximum Media stream Bit-rate Request (TMMBR) (FMT=3) feedback message, hexadecimal value 0x03CD is used. + +**Default:** None. + +#### 8.2.1.2 ObservedEventsDescriptor parameters + +NOTE – Whilst the RTCP Feedback mechanism supports various types of messages, only those messages and information that are deemed relevant to a MGC are specified below. + +##### 8.2.1.2.1 Update picture + +**Parameter name:** Update Picture + +**Parameter ID:** upic (0x0001) + +**Description:** This is used to indicate that a picture loss indication (i.e., indicated by a PLI RTCP Feedback message) has been received from the remote end and that the picture may need to be updated. + +**Type:** Enumeration + +**Optional:** Yes + +**Possible values:** "PLI" + (0x0001) Picture Loss Indication + +**Default:** None. + +##### 8.2.1.2.2 Max bitrate + +**Parameter name:** Max Bitrate + +**Parameter ID:** mbr (0x0002) + +**Description:** This is used to indicate that the MG has received a maximum media stream bit rate (i.e., as indicated by a TMMBR RTCP Feedback message) from the remote end. The bandwidth is calculated by the MG based on the bandwidth as indicated in the RTCP TMMBR message excluding any overhead indicated in the RTCP TMMBR message. + +The MG shall issue a *rtcpfb/det* notification with a *mbr* parameter only if the received RTCP TMMBR message contains a FCI related to the SSRC used by the MG. Only the bandwidth appearing in that FCI is reported. + +**Type:** Double +**Optional:** Yes +**Possible values:** 0 upwards in units of bits per second +**Default:** None. + +## 8.3 Signals + +### 8.3.1 Feedback message sending + +**Signal name:** Feedback Message Sending +**Signal ID:** fbmesssend (0x0001) +**Description:** This signal allows the MGC to provide feedback information to the MG that is relevant to a particular media session. Based on the information a MG will send an appropriate RTCP feedback message to the remote end. +**Signal type:** Brief +**Duration:** Not applicable + +#### 8.3.1.1 Additional parameters + +NOTE – Whilst the RTCP feedback mechanism supports various types of messages, only those messages and information that are deemed relevant to a MGC are specified below. + +##### 8.3.1.1.1 Update picture + +**Parameter name:** Update Picture +**Parameter ID:** upic (0x0001) +**Description:** This is used by the MGC to indicate to the MG that it shall send an indication to the remote end that a picture update is needed (i.e., the MG shall send a PLI RTCP Feedback message). +**Type:** Enumeration +**Optional:** Yes +**Possible values:** "PLI" (0x0001): Picture Loss Indication +**Default:** None. + +##### 8.3.1.1.2 Max bitrate + +**Parameter name:** Max Bitrate +**Parameter ID:** mbr (0x0002) + +Description: This is used by the MGC to indicate to the MG that it shall send an indication to the remote end with a maximum bit rate for the media stream (i.e., the MG shall send a TMMBR RTCP feedback message using indicated rate to calculate the contents of the feedback message). + +Type: Double + +Optional: Yes + +Possible values: 0 upwards in units of bits per second + +Default: None. + +## 8.4 Statistics + +None. + +## 8.5 Error codes + +None. + +## 8.6 Procedures + +### 8.6.1 General + +Media gateways may be required to support RTCP feedback messages. The support of RTCP-based feedback messages is signalled through the SDP protocol field indicating the support of the "Extended RTP Profile with RTCP based Feedback (RTP/AVPF)". Furthermore, which feedback messages are supported is indicated through the SDP attribute "RTCP Feedback parameter (frcpfb)". See [IETF RFC 4585] for more information regarding their usage. + +As such, this package does not itself indicate support of a particular RTP profile or RTCP feedback message set. This must be done through the Local and Remote descriptors. + +This package allows the MGC to request to be notified of the reception of certain RTCP feedback messages and allows the MGC to request certain RTCP feedback messages to be sent. + +### 8.6.2 Feedback message reception and notification + +For an MGC to be notified of a particular feedback message, it shall set the *RTCP Feedback Message Detection (rtcpfb/det)* event on an applicable termination/stream on the MG. The event should be set at a stream level in order to uniquely identify the media stream to which the RTCP feedback message belongs. The MGC shall indicate the payload type and feedback message type of the RTCP Feedback messages for which it requires to be notified. + +Once the event is set, when the MG receives a RTCP feedback message that matches one of those indicated in the event, a Notify request command is sent to the MGC. This Notify message shall contain an ObservedEvent parameter related to the RTCP feedback message information that was detected. If a compound RTCP message is received with multiple RTCP feedback messages, an ObservedEvent notification is generated for each one. + +On reception of the Notify message, the MGC may then use the ObservedEvent parameters to determine what further action needs to be taken. + +### 8.6.3 Feedback message sending + +Certain information may be received by the MGC that may be relevant to a media stream. As a result, the MGC may require information to be sent to a receiver through the bearer path (i.e., via RTCP feedback messages). In order to achieve this, the MGC shall use the *Feedback Message Sending (rtcpfb/fbmesssend)* signal on the applicable Termination/Stream. The signal should be sent at a stream level to unambiguously identify the correct media stream. The MGC shall use the + +appropriate signal parameter (e.g., Update Picture or Max Bit Rate) to indicate the information that needs to be sent. The MG shall derive from this information which RTCP Feedback message type needs to be sent. + +On reception of the *rtcpfb/fbmesssend* signal, the MG shall use the signal parameters to construct a valid RTCP feedback message according to [IETF RFC 4585] or an appropriate extension RFC. If the MG is unable to construct or send the RTCP feedback message, it shall return error code #513 (Media gateway unequipped to generate requested signals). + +### 8.6.4 Example + +The *rtcpfb* package may be used by MGC/MGs in scenarios for interworking between H.324/H.324 Annex C ("H.324M") and RTP-based packet switched networks. In this case, an MGC would initiate/terminate ITU-T H.245 signalling and the MG would initiate/terminate RTCP signalling. As the MGC is the master, it is assumed that it determines what information will be interworked between ITU-T H.245 and RTCP. + +As such, it determines that the [b-ITU-T H.245] *videoFastUpdatePicture* and Flow Control Commands will need to be interworked with RTCP. The equivalent RTCP feedback messages are Picture Loss Indication (PLI, see [IETF RFC 4585]) and Temporary Maximum Media Stream Bit Rate Request (TMMBR, see [IETF RFC 5104]), respectively. + +An MGC will receive the ITU-T H.245 messages directly, however it will need to receive the information from the RTCP feedback messages from the MG. In order for it to receive the messages, it sends the following: + +``` +MGC to MG1: +MEGACO/3 [123.123.123.4]:55555 +Transaction = 9999 { + Context = 1 { + Modify = A4444 { + Events = 2222 {rtcpfb/det {ST=2,type=[0x001CE,0x03CD]}} + } + } +} +``` + +If the MG then receives a PLI RTCP feedback message, it shall generate a notification to the MGC using the following command: + +``` +MG1 to MGC: +MEGACO/3 [124.124.124.222]:55555 +Transaction = 10000 { + Context = 1 { + Notify = A4444 {ObservedEvents =2222 { + 19990729T22000000:rtcpfb/det{ST=2,upic="PLI"}}} + } + } +} +``` + +On reception of the *Notify* command, the MGC may generate an ITU-T H.245 *videoFastUpdatePicture* command. + +# Bibliography + +- [b-ITU-T H.245] Recommendation ITU-T H.245 (2008), *Control protocol for multimedia communication*. +- [b-ITU-T H.248.47] Recommendation ITU-T H.248.47 (2007), *Gateway control protocol: Statistic conditional reporting package*. +- [b-ITU-T H.324] Recommendation ITU-T H.324 (2009), *Terminal for low bit-rate multimedia communication*. +- [b-IETF RFC 5117] IETF RFC 5117 (2008), *RTP Topologies*. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.73-201009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.73-201009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04ed0575fb17e6faeb57d9d81b58c3b85f7e21df --- /dev/null +++ b/marked/H/T-REC-H.248.73-201009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3223bb567d6cdfacad7ced972fc4eab63d7b0659969b11a4801458bec7649f19 +size 3852 diff --git a/marked/H/T-REC-H.248.73-201009-I_PDF-E/raw.md b/marked/H/T-REC-H.248.73-201009-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..828c85300f0da35c17dd817f873be462a5586acb --- /dev/null +++ b/marked/H/T-REC-H.248.73-201009-I_PDF-E/raw.md @@ -0,0 +1,548 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.73** + +(09/2010) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: Packages for media +server control markup language and ITU-T H.248 +interworking** + +Recommendation ITU-T H.248.73 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T H.248.73** + +# **Gateway control protocol: Packages for media server control markup language and ITU-T H.248 interworking** + +## **Summary** + +Recommendation ITU-T H.248.73 provides guidance on mapping media server control markup language (MSCML) functions to ITU-T H.248 protocol information elements, packages and procedures. It further defines a package to enable gain control (fixed and automatic) on incoming and outgoing media streams. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.248.73 | 2010-09-13 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 MSCML and ITU-T H.248 interworking ..... | 2 | +| 6.1 Advanced conferencing ..... | 2 | +| 6.2 Interactive voice response (IVR)..... | 4 | +| 6.3 Call leg events ..... | 6 | +| 6.4 Managing content ..... | 6 | +| 6.5 Fax processing ..... | 6 | +| 6.6 MSCML response attributes and elements..... | 6 | +| 7 TDM Gain Control Package ..... | 7 | +| 7.1 Properties..... | 7 | +| 7.2 Events ..... | 8 | +| 7.3 Signals ..... | 8 | +| 7.4 Statistics..... | 8 | +| 7.5 Error codes..... | 9 | +| 7.6 Procedures ..... | 9 | + + + +## Gateway control protocol: Packages for media server control markup language and ITU-T H.248 interworking + +# 1 Scope + +The media server control markup language (MSCML) is a markup language used in conjunction with session initiation protocol (SIP) to provide advanced conferencing and interactive voice response (IVR) functions. If used with a decomposed media server, MSCML is terminated at the media gateway controller (MGC) level as it is associated with SIP. Where the decomposed media server uses ITU-T H.248, MSCML requests need to be translated into the applicable ITU-T H.248 functionality. This Recommendation provides guidance on mapping MSCML functions to ITU-T H.248 protocol information elements, packages and procedures. + +Furthermore, this Recommendation defines a package to enable gain control (fixed and automatic) on incoming and outgoing streams. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.169] Recommendation ITU-T G.169 (1999), *Automatic level control devices*. +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*. +- [ITU-T H.248.2] Recommendation ITU-T H.248.2 (2005), *Gateway control protocol: Facsimile, text conversation and call discrimination packages*. +- [ITU-T H.248.9] Recommendation ITU-T H.248.9 (2009), *Gateway control protocol: Advanced media server packages*. +- [ITU-T H.248.19] Recommendation ITU-T H.248.19 (2004), *Gateway control protocol: Decomposed multipoint control unit, audio, video and data conferencing packages*, plus Amendment 2 (2009), *Floor control enhancements*. +- [ITU-T H.248.63] Recommendation ITU-T H.248.63 (2009), *Gateway control protocol: Resource management packages*. +- [ITU-T H.248.68] Recommendation ITU-T H.248.68 (2009), *Gateway control protocol: Package for removal of digits and tones*. +- [IETF RFC 3108] IETF RFC 3108 (2001), *Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections*. +- [IETF RFC 5022] IETF RFC 5022 (2007), *Media Server Control Markup Language (MSCML) and Protocol*. + +# **3 Definitions** + +## **3.1 Terms defined elsewhere** + +None. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------------| +| DTMF | Dual Tone Multi-Frequency | +| IVR | Interactive Voice Response | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MSCML | Media Server Control Markup Language | +| SIP | Session Initiation Protocol | +| TDM | Time Division Multiplex | + +# **5 Conventions** + +None. + +# **6 MSCML and ITU-T H.248 interworking** + +This clause shows how the MSCML functions are mapped to the ITU-T H.248 elements. It contains an analysis of the functions provided by [IETF RFC 5022] and indicates how these are supported by the ITU-T H.248 sub-series of Recommendations. + +## **6.1 Advanced conferencing** + +### **6.1.1 Conference model** + +See clause 5.1 of [IETF RFC 5022] for details. + +ITU-T H.248 natively supports conferencing as part of its connection model. Requests for creating, modifying and deleting conference legs are translated to the appropriate ITU-T H.248 commands. + +### **6.1.2 Configure Conference Request ** + +See clause 5.2 of [IETF RFC 5022] for details. + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reservedtalkers: | A MGC may request Terminations for the number of talkers. The "Resource Management Configuration Package" defined in [ITU-T H.248.63] also allows the MGC to indicate the number of speaking and listening Terminations. See Example 3 in clause 8.6.3 of [ITU-T H.248.63]. | +| Reserveconfmedia: | A MGC may audit a MG to determine if the MG supports signals/events/packages for recording and/or playout. | + +### 6.1.3 Configure Leg Request + +See clause 5.3 of [IETF RFC 5022] for details. + +A MGC may manipulate the configuration of a conference leg by manipulating the appropriate ITU-T H.248 Descriptors on the applicable Termination. + +Attributes of : + +| | | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type: | In ITU-T H.248, this is represented by the "Mode" property, see clause 7.1.7 of [ITU-T H.248.1]. | +| Dtmfclamp: | This functionality may be implemented via [ITU-T H.248.68]. | +| Toneclamp: | This functionality may be implemented via [ITU-T H.248.68]. | +| Mixmode: | These mix modes can be achieved via the Topology Descriptor (clause 7.1.18 of [ITU-T H.248.1]). The exception is "preferred". The "Preferred Mix" package in [ITU-T H.248.19] allows the MGC to indicate "mix 10 loudest speakers + this one". | +| Inputgain, outputgain: |

Clause E.13 of [ITU-T H.248.1] defines a gain control parameter. This contains the ability to set the gain to a specific value or to auto for an outbound stream (e.g., via LocalControl). The specification of the gain per direction (incoming/outgoing) and the "startlevel", "targetlevel" and "silencethreshold" is achieved through the use of the "TDM Gain Control" package defined in this Recommendation.

Clause 5.6.3.4 of [IETF RFC 3108] specifies the "Gain Control" (a=gc) attribute. This allows for directional based gain control as well as automatic gain control. However, it also does not allow the specification of the "startlevel", "targetlevel" and "silencethreshold".

| +| Configure_team: | ITU-T H.248 supports this via its connection model. | +| Subscribe: | ITU-T H.248 supports this natively via its event mechanism. | + +### 6.1.4 Terminating a conference + +ITU-T H.248 supports this via the Subtract command. + +### 6.1.5 Conference manipulation + +See clause 5.5 of [IETF RFC 5022] for details. + +ITU-T H.248 supports this via Add, Modify and Move commands. + +### 6.1.6 Video conferencing + +See clause 5.6 of [IETF RFC 5022] for details. + +ITU-T H.248 supports this via properties in [ITU-T H.248.19]. + +### 6.1.7 Conference events + +See clause 5.7 of [IETF RFC 5022] for details. + +The "Speaker reporting" package in [ITU-T H.248.19] enables active talker reporting with an interval as well as the reporting of the speakers. As the MG has no concept of the call, the MGC is responsible for mapping the TerminationID to the talker called element. + +### 6.1.8 Conferencing with personalized mixes + +See clause 5.8 of [IETF RFC 5022] for details. + +**Configure\_team:** This is natively supported through the use of the ITU-T H.248 connection model as well as the Topology Descriptor. As mentioned, the default mix behaviour is that active talkers do not hear themselves. In order for an active talker to hear himself or herself in the mix, the "Include Participant in Mix Package" clause 11.5 of [ITU-T H.248.19] can be used. + +## 6.2 Interactive voice response (IVR) + +### 6.2.1 Specifying prompt content + +See clause 6.1 of [IETF RFC 5022] for details. + +In general, IVR is supported by functionality in [ITU-T H.248.9]. + +For the support of the prompt attributes: + +**Baseurl:** See clause 6 of [ITU-T H.248.9] for more information. + +**Delay:** Supported via the "Interval" parameter of the Play signal in the "Advanced audio server base" package in [ITU-T H.248.9]. + +**Duration:** Supported via the Signal Type "on/off" or "timeout" (see 7.1.11 of [ITU-T H.248.1]) with an associated time value. + +**Gain:** Supported by the Absolute Volume parameter in the "Advanced audio Server base" package in [ITU-T H.248.9]. + +**Gaindelta:** Supported via the "Volume" parameter of the Play signal in the "Advanced audio server base" package in [ITU-T H.248.9]. + +**Rate:** Supported via the "Speed" parameter of the Play signal in the "Advanced audio server base" package in [ITU-T H.248.9]. + +**Ratedelta:** NOTE – The support via a "Playback Relative Scale Adjustment" package is for further study. + +**Locale:** Supported via the use of variables. See clause 6 of [ITU-T H.248.9]. + +**Offset:** Supported by the Play signal in the "Advanced audio server base" package, the Record signal in the "AAS recording" package and the "Multimedia recording" package in [ITU-T H.248.9]. + +**Repeat:** Supported via the "Iterations" parameter of the Play signal in the "Advanced audio server base" package in [ITU-T H.248.9]. + +**Stoponerror:** The default behaviour is for an MG to generate an error response if there is a problem. The MGC may wish to retry or request further announcements. In this way, it can apply the logic associated with this. + +The audio element also has a number of attributes. The above mappings also apply. The variable attributes are achieved through the use of ITU-T H.248.9 variables as described in clause 6 of [ITU-T H.248.9]. + +### 6.2.2 Multimedia processing for IVR + +See clause 6.2 of [IETF RFC 5022] for details. + +See [ITU-T H.248.9] for multimedia support. + +### 6.2.3 Playing announcements + +See clause 6.3 of [IETF RFC 5022] for details. + +Supported by the "Advanced audio server base" package in [ITU-T H.248.9]. + +### 6.2.4 Prompt and collect + +See clause 6.4 of [IETF RFC 5022] for details. + +Supported by the "AAS Digit Collection" package in [ITU-T H.248.9]. + +### 6.2.5 Prompt and record + +See clause 6.5 of [IETF RFC 5022] for details. + +Supported by the "AAS Recording" package in [ITU-T H.248.9]. + +#### 6.2.5.1 Prompt phase + +The prompt URL is supported by the "InitialPrompt" parameter in [ITU-T H.248.9]. + +- Barge: Digit collection may be achieved through the use of digit maps. The "restart", "Reinput", "Return key" and "Endinputkey" parameters may be used to indicate what effect user input will have on the announcement/recording. +- Cleardigits: [ITU-T H.248.1] contains the EventBuffer descriptor that may be used to buffer DTMF collection. +- Escapekey: Supported through the use of the [ITU-T H.248.9] "ReturnKey" parameter. + +#### 6.2.5.2 Record phase + +- Recurl: Supported through the use of the "RecordingIdentifier" parameter in [ITU-T H.248.9]. +- Recencoding: Supported through the use of the "RecordingIdentifier" in [ITU-T H.248.9]. The encoding forms part of the segment identifier. +- Mode: Supported through the use of the "Storage Mode" parameter in the "AAS Recording" package and the "Multimedia recording" package in [ITU-T H.248.9]. +- Beep: Not explicitly supported by [ITU-T H.248.9]; however, the playout of beep tone may form part of the Initial Prompt. +- Initsilence: Supported through the use of the "Pre-speech Timer" parameter in [ITU-T H.248.9]. The values "immediate" and "infinite" may be mapped to an appropriately short or long time value. +- Endsilence: Supported through the use of the "Post-speech Timer" parameter in [ITU-T H.248.9]. The values "immediate" and "infinite" may be mapped to an appropriately short or long time value. +- Recstopmask: Supported through the use of the "EndInputKey" parameter in [ITU-T H.248.9]. + +### 6.2.6 Stop request + +See clause 6.6 of [IETF RFC 5022] for details. + +The ending of interactive voice response is supported natively in the ITU-T H.248 protocol via the normal signal termination mechanisms. + +## 6.3 Call leg events + +### 6.3.1 Keypress events + +See clause 7.1 of [IETF RFC 5022] for details. + +This is supported by [ITU-T H.248.1] in the Tone Detection packages, with the exception of an explicit "Interdigit time". The MGC however may determine the interdigit time by examining the timestamp associated with the ObservedEvents reporting the detected DTMF digits. + +### 6.3.2 Signal events + +This is supported by [ITU-T H.248.1] in the "Tone Generator" and "Tone Detection" packages. + +## 6.4 Managing content + +See clause 8 of [IETF RFC 5022] for details. + +See clauses 10 and 11 of [ITU-T H.248.9] which allow a MGC to manage the content on a MG. + +## 6.5 Fax processing + +See clause 9 of [IETF RFC 5022] for details. + +Whilst fax is supported via [ITU-T H.248.2], there is no support in ITU-T H.248 for the MG to generate or record a fax. + +## 6.6 MSCML response attributes and elements + +See clause 10 of [IETF RFC 5022] for details. + +See above for an analysis of how base elements are supported. + +### 6.6.1 Response attributes and elements for + +See clause 10.3 of [IETF RFC 5022] for details. + +The MGC is responsible for mapping team information to ITU-T H.248 connection model concepts. + +### 6.6.2 Response attributes and elements for + +See clause 10.4 of [IETF RFC 5022] for details. + +Response attributes are supported in the following ways: + +| | | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reason: | Supported by the Audio Operation Failure event in [ITU-T H.248.9]. | +| Play duration, Play offset: | The [ITU-T H.248.9] "Advanced Audio Server Base Package", "AAS Digit Collection Package", "AAS Recording Package", "Multimedia Play Package" and "Multimedia Recording Package" have parameters that allow the "Play Duration" and "Play Offset" to be returned on signal completion (either successful or on error). | + +#### 6.6.2.1 Reporting content retrieval errors + +See clause 10.4.1 of [IETF RFC 5022] for details. + +Only the "code" response attribute is directly supported. The MGC may map the ITU-T H.248 error code to the MSCML code and provide the text. + +### 6.6.3 Response attributes and elements for + +See clause 10.5 of [IETF RFC 5022] for details. + +Response attributes are supported in the following ways: + +| | | +|---------|----------------------------------------------------------------------| +| Reason: | Supported by the "Audio Operation Failure" event in [ITU-T H.248.9]. | +|---------|----------------------------------------------------------------------| + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------| +| Play duration: | Supported by the "PlayCollect Success" event in clause 9.2.2 of [ITU-T H.248.9]. | +| Play offset: | Supported by the "Offset" parameter in the "Playout Completion Event" in the Advanced audio server base package in [ITU-T H.248.9]. | +| Digits: | Supported by the "PlayCollect Success" event in clause 9.2.2 of [ITU-T H.248.9]. | +| Name: | Not relevant as ITU-T H.248 grammar applies. | + +### 6.6.4 Response attributes and elements for + +See clause 10.6 of [IETF RFC 5022] for details. + +Response attributes are supported in the following ways: + +| | | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Reason: | Supported by the Audio Operation Failure event. | +| Play duration: | Supported by the "PlayRecord Success" event in clause 10.2.2 of [ITU-T H.248.9]. | +| Play offset: | Supported by the "Offset" parameter in the "Playout Completion Event" in the "Advanced audio server base" package in [ITU-T H.248.9]. | +| Digits: | Supported by the "End Key" parameter in the "PlayRecord Success Event" in the "AAS recording" package in [ITU-T H.248.9]. | +| Reclength: | Supported by the "Recording Length" parameter in the "PlayRecord Success Event" in the "AAS recording" package in [ITU-T H.248.9]. | +| Recduration: | Supported by the "Recording Duration" parameter in clause 10.2.2.2.5 of [ITU-T H.248.9]. | + +### 6.6.5 Response attributes and elements for + +See clause 10.7 of [IETF RFC 5022] for details. + +This is supported by normal ITU-T H.248 error response mechanisms. + +### 6.6.6 Response attributes and elements for and + +See clause 10.8 of [IETF RFC 5022] for details. + +Fax play and record are currently not supported by [ITU-T H.248.9]. + +# 7 TDM Gain Control Package + +| | | +|---------------|-------------------------------------------------------------------------------------| +| Package Name: | TDM Gain Control Package | +| Package ID: | tgc (0x00f9) | +| Description: | This package provides the MGC and the MG the enhanced gain control functionalities. | +| Version: | 1 | +| Extends: | TDM Circuit Package version 1 | + +## 7.1 Properties + +### 7.1.1 Incoming Gain Control + +| | | +|----------------|-----------------------| +| Property Name: | Incoming Gain Control | +| Property ID: | ingain (0x000b) | + +Description: As per clause E.13.1.2 of [ITU-T H.248.1], except that it is used to adapt the level of the inbound signal. + +Type: Integer + +Possible values: As per clause E.13.1.2 of [ITU-T H.248.1] + +Default: Provisioned + +Defined in: LocalControl Descriptor + +Characteristics: Read/Write + +### **7.1.2 Outgoing Automatic Gain Parameters** + +Property Name: Outgoing Automatic Gain Parameters + +Property ID: oagp (0x000c) + +Description: This property allows the MGC to provide further information to the MG regarding automatic gain control for an outgoing signal/media. + +Type: Sub-list of Integer + +Possible values: The sub-list of Integer shall be of length three. The first instance of the sub-list represents the "Start level", the second instance represents the "Target level" and the third instance represents the "Silence Threshold". Each instance contains an integer value representing a level in decibels. + +Default: Provisioned + +Defined in: LocalControl Descriptor + +Characteristics: Read/Write + +### **7.1.3 Incoming Automatic Gain Parameters** + +Property Name: Incoming Automatic Gain Parameters + +Property ID: iagp (0x000d) + +Description: This property allows the MGC to provide further information to the MG regarding automatic gain control for an incoming signal/media. + +Type: Sub-list of Integer + +Possible values: As per clause 7.1.2 + +Default: Provisioned + +Defined in: LocalControl Descriptor + +Characteristics: Read/Write + +## **7.2 Events** + +None. + +## **7.3 Signals** + +None. + +## **7.4 Statistics** + +None. + +## 7.5 Error codes + +None. + +## 7.6 Procedures + +In order to control the gain on an incoming signal/media, the MGC may set the "Incoming Gain Control" (*tgc/ingain*) property. For the outbound signal/media, it may set the "Gain Control" (*tdm/gain*) property. The MGC may set these properties to a fixed value or to indicate automatic gain. Where automatic gain is indicated, further information may be provided to the MG through the use of the "Outgoing Automatic Gain Parameters" (*tgc/oagp*) and/or "Incoming Automatic Gain Parameters" (*tgc/iagp*) properties. These parameters provide extra information to the MG in order to provide a more accurate and timely automatic level control. If set, these properties shall be included in the same command as the one that indicates automatic gain for the particular direction. If set separately, error code 472 "*Required Information Missing*" shall be returned. + +[ITU-T G.169] contains information regarding automatic level control devices. Start level (otherwise known as "initial gain"), target level and silence threshold (otherwise known as "threshold level") and how they apply to automatic level control are discussed in that Recommendation. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.74-201604-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.248.74-201604-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7 --- /dev/null +++ b/marked/H/T-REC-H.248.74-201604-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055 +size 6859 diff --git a/marked/H/T-REC-H.248.83-201202-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.83-201202-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ad98c6e45b6c52f074f0054407ca88a640d8f1d --- /dev/null +++ b/marked/H/T-REC-H.248.83-201202-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58019f38be268f19eaa80c6d56d0f6b39d5741569a8f3ccc04117fa95d9c6465 +size 4016 diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d455957d7ed2e82ac2c6b458011e2985c2ce034 --- /dev/null +++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b956d50bc4d41a22f90ae49362927abd5a549366e49aaa851972e2112902defb +size 71891 diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b11c8474cf82e19899fd82c6e1cfe50b087a269c --- /dev/null +++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8a380ee4b34ef5090103bce2e5213644f53fd9c6c798cbf5140acfadea033a7 +size 96563 diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b286089f05e42b4af0c85fa834bb02f73a446616 --- /dev/null +++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fce402c1e36546cfa0de3825ca3ed9d428ad8c12f9500de000b5cf72cfb8a21 +size 234151 diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7634c98ac899b3c5bc766d8db125ea3b320c523 --- /dev/null +++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:346a1bfd5389309d6cb9c6e59f4e19f7e4ddd3ca9296380e7f962ec4bf0104fa +size 170572 diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47b78d16475d370916e5501534299d89a131f096 --- /dev/null +++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a912e0aec97ea60714f914529b77aa046245e6c7f7b4167cad65c1c91aa146e4 +size 179487 diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33da2b09ce612690f9765522dd30a9816a732821 --- /dev/null +++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bb0ee77549d86b038d762775c4b30cab8db2784b2058e2e3c64408db0a14b21 +size 108173 diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e52bf04df4b407a6f28babb84d7a6a6d97941784 --- /dev/null +++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:477167d3436a3e9e6edcb51db3f403386097afe91196a1edc7b8f6531f7918a4 +size 98475 diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/raw.md b/marked/H/T-REC-H.248.84-201207-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a25ad95158fffa6cf0646a01012c2071239d9154 --- /dev/null +++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/raw.md @@ -0,0 +1,2134 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.248.84** + +(07/2012) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Communication +procedures + +--- + +**Gateway control protocol: NAT traversal for +peer-to-peer services** + +Recommendation ITU-T H.248.84 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T H.248.84** + +# **Gateway control protocol: NAT traversal for peer-to-peer services** + +## **Summary** + +Session border controllers (SBCs) are an important part of the Internet infrastructure. Some of these session border controllers are split into media gateway controller (MGC) and media gateway (MG) components. One important function of an SBC is to perform traversal support for remote network address/port translation (NAT) devices in the IP communication path. Recommendation ITU-T H.248.84 defines an additional tool for NAT traversal for peer-to-peer (P2P) services and an initial focus on TCP-based applications. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.248.84 | 2012-07-22 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 1.1 Problem statement ..... | 1 | +| 1.2 Example network applications ..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations..... | 3 | +| 5 Conventions ..... | 4 | +| 5.1 Conventions concerning the ITU-T H.248 gateway control protocol ..... | 4 | +| 5.2 Conventions concerning the TCP bearer protocol..... | 5 | +| 5.3 Conventions concerning the SIP Call control protocol ..... | 5 | +| 6 NAT-traversal for peer-to-peer services..... | 5 | +| 6.1 Overview ..... | 5 | +| 6.2 Protocol dependencies ..... | 7 | +| 7 Example use cases ..... | 7 | +| 7.1 TCP bearer path with SIP signalling path ..... | 7 | +| 8 NAT-traversal peer-to-peer package ..... | 9 | +| 8.1 Properties..... | 9 | +| 8.2 Events ..... | 9 | +| 8.3 Signals ..... | 10 | +| 8.4 Statistics..... | 10 | +| 8.5 Error codes..... | 10 | +| 8.6 Procedures ..... | 10 | +| 9 TCP hole punching package ..... | 10 | +| 9.1 Properties..... | 11 | +| 9.2 Events ..... | 11 | +| 9.3 Signals ..... | 12 | +| 9.4 Statistics..... | 12 | +| 9.5 Error codes..... | 13 | +| 9.6 Procedures ..... | 13 | +| 10 TCP traffic volume metrics package ..... | 13 | +| 10.1 Properties..... | 13 | +| 10.2 Events ..... | 13 | +| 10.3 Signals ..... | 13 | + +| | Page | | +|------------|------------------------------------------------------------------------------------------------------------------|----| +| 10.4 | Statistics..... | 14 | +| 10.5 | Error codes..... | 15 | +| 10.6 | Procedures ..... | 15 | +| 11 | TCP connection control metrics package ..... | 15 | +| 11.1 | Properties..... | 15 | +| 11.2 | Events ..... | 16 | +| 11.3 | Signals ..... | 16 | +| 11.4 | Statistics..... | 16 | +| 11.5 | Error codes..... | 17 | +| 11.6 | Procedures ..... | 17 | +| 12 | TCP connection quality metrics package ..... | 17 | +| 12.1 | Properties..... | 17 | +| 12.2 | Events ..... | 18 | +| 12.3 | Signals ..... | 18 | +| 12.4 | Statistics..... | 18 | +| 12.5 | Error codes..... | 18 | +| 12.6 | Procedures ..... | 19 | +| 13 | Package-independent procedures for NAT-T with TCP bearers ..... | 19 | +| 13.1 | TCP mode of operation: decision baseline in MGC..... | 19 | +| 13.2 | TCP mode of operation: control principle at ITU-T H.248 interface..... | 19 | +| 13.3 | Supported connection model ..... | 19 | +| 13.4 | Indication of IP transport protocol 'TCP'..... | 20 | +| 13.5 | Indication of 'TCP mode' for ITU-T H.248 MG ..... | 20 | +| 13.6 | TCP connection reuse..... | 21 | +| 13.7 | TCP connection establishment phase – Handling of TCP Protocol Control
Information by the ITU-T H.248 MG ..... | 21 | +| 13.8 | Unsuccessful NAT-T scenarios ..... | 22 | +| 13.9 | Impact of transport protocol encryption ..... | 22 | +| 13.10 | Interactions with NAT-T method latching/relatching ..... | 23 | +| 13.11 | Possible interactions with enabled filters for TCP traffic ..... | 23 | +| 14 | Package-independent, bearer-independent procedures for NAT-T ..... | 23 | +| 14.1 | Relations to latching/relatching based NAT traversal support..... | 23 | +| 14.2 | Interaction with L4 filters ..... | 23 | +| Appendix I | – Example signalling scenarios..... | 25 | +| I.1 | Example signalling for use case "TCP bearer path with SIP signalling
path"..... | 25 | + +| | Page | +|----------------------------------------------------------------------------------------|-------------| +| Appendix II – TCP Functions versus ITU-T H.248 TCP modes of operation ..... | 32 | +| II.1    Purpose and scope ..... | 32 | +| II.2    Overview ..... | 32 | +| II.3    Tables of TCP functions versus ITU-T H.248 TCP modes of operation ..... | 33 | +| II.4    Relation between TCP proxy and TCP merge mode..... | 38 | +| Appendix III – TCP mode control – SDP "a=setup" clarification due to b-IETF RFC 6135.. | 40 | +| Appendix IV – Generic NAT traversal models ..... | 41 | +| IV.1    ITU-T H.248 gateways in SIP environments and remote NAT devices ..... | 41 | +| IV.2    Basic types of remote NAT devices ..... | 42 | +| IV.3    Local NAT function by ITU-T H.248 MG and end-to-end consideration ..... | 43 | +| Appendix V – Illustration of performance measurements ..... | 46 | +| V.1    Statistic "TCP connection establishment delay (in TCP merge mode)" ..... | 46 | +| V.2    Statistic "TCP round-trip time during connection establishment phase" ..... | 47 | +| Bibliography..... | 50 | + + + +# Gateway control protocol: NAT traversal for peer-to-peer services + +# 1 Scope + +NAT traversal (NAT-T) support by ITU-T H.248 media gateways (MG) is an established capability for such network elements positioned in the IP infrastructure of next generation networks (NGN) and IP multimedia subsystem (IMS) networks. In [ITU-T H.248] there are several methods for NAT-T, for example: + +- [ITU-T H.248.37] IP NAPT traversal package; and +- [ITU-T H.248.50] NAT traversal toolkit packages. + +However, these do not define any methods for NAT-T in peer-to-peer (P2P) services, i.e., for ITU-T H.248 MGs located within the end-to-end P2P IP path providing NAT traversal support for remote NAT devices (also located in the P2P IP path). + +In scope of this Recommendation are NAT-T techniques as detailed by [b-IETF RFC 5128]. + +## 1.1 Problem statement + +The problem of providing NAT-T in P2P is described in [b-IETF RFC 5128]. However, this IETF RFC does not consider scenarios where ITU-T H.248 gateways may be located in the end-to-end IP paths of a P2P service. + +The ITU-T H.248 MG may provide help for NAT-T, e.g., by + +- the capability of reporting observed IP transport addresses according to the [ITU-T H.248.37] *address reporting* package; or/and +- a bearer-level application level gateway (ALG) function according to [ITU-T H.248.78]. + +However, the usage of either or both is conditional, dependent on: network architecture, IP applications, protocol awareness by ITU-T H.248 MG, remote NAT behaviour, etc. + +It should also be noted that a bearer-level application layer gateway (ALG) itself may not be sufficient for NAT-T scenarios in scope of this Recommendation. + +The bearer-level ALG might be a beneficial and effective NAT-T support function. However this Recommendation provides NAT-T methods for scenarios without the usage of [ITU-T H.248.78]. This is in order to respect the principle of "network unawareness" (i.e., "L4 payload agnostic") concerning the (bearer-level) IP application protocol in P2P scenarios. + +## 1.2 Example network applications + +Example network applications are for instance, ITU-T H.248 gateways located between different IP networks (so called ITU-T H.248 border gateways) which support over-layered peer-to-peer services. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3, including Amendment 2 (12/2009)*. +- [ITU-T H.248.37] Recommendation ITU-T H.248.37 (2008), *Gateway control protocol: IP NAT traversal package*. +- [ITU-T H.248.40] Recommendation ITU-T H.248.40 (2007), *Gateway control protocol: Application data inactivity detection package*. +- [ITU-T H.248.50] Recommendation ITU-T H.248.50 (2010), *Gateway control protocol: NAT traversal toolkit packages*. +- [ITU-T H.248.69] Recommendation ITU-T H.248.69 (2009), *Gateway control protocol: Packages for interworking between MSRP and H.248*. +- [ITU-T H.248.78] Recommendation ITU-T H.248.78 (2010), *Gateway control protocol: Bearer-level application level gateway*. +- [ETSI TS 123 228] ETSI TS 123 228 V10.7.0 (2012-01), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 10.7.0 Release 10)*. +- [IETF RFC 793] IETF RFC 793 (1981), *Transmission Control Protocol*. +- [IETF RFC 4145] IETF RFC 4145 (2005), *TCP-Based Media Transport in the Session Description Protocol (SDP)*. +- [IETF RFC 4975] IETF RFC 4975 (2007), *The Message Session Relay Protocol (MSRP)*. +- [IETF RFC 5382] IETF RFC 5382 (2008), *NAT Behavioral Requirements for TCP*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 application level gateway (ALG)** [ETSI TS 123 228]: An application specific functional entity that allows communication between disparate address realms or IP versions, e.g., an IPv6 node to communicate with an IPv4 node and vice versa, when certain applications carry network addresses in the payloads like SIP/SDP. NA(P)T-PT or NA(P)T is application unaware whereas ALGs are application specific translation entities that allow a host running an application to communicate transparently with another host running the same application but in a different IP version or IP address realm. + +NOTE – This definition originates from the first ALG description in clause 2.9 of [b-IETF RFC 2663]. + +**3.1.2 transport (TCP) relay (translator) mode** [b-ETSI TR 183 068]: Transparent forwarding of TCP packets in terms of stateless behaviour concerning the TCP connection state machine + +NOTE – The term transport relay translator (TRT) mode is based on [b-IETF RFC 3142], which describes the IP version translation for transport protocol aware IP nodes. + +**3.1.3 transport (TCP) proxy (translator) mode** (also known as back-to-back TCP endpoint (B2BTE) mode) [b-ETSI TR 183 068]: Stateful forwarding of TCP packets in terms of full protocol termination. The end-to-end TCP connection is partitioned in two TCP connection legs by the BGF. Each ITU-T H.248 Stream endpoint provides a stateful TCP connection state machine. + +NOTE 1 – The term proxy mode is similar as used for HTTP proxy, FTP proxy, SIP proxy, etc. + +NOTE 2 – The term BGF relates to an ITU-T H.248 (IP, IP) media gateway in this Recommendation. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 hole punching:** A method of dedicated network address translator (NAT) to allow appropriately designed peer-to-peer applications to create a path through the NAT device(s) en-route and establish direct connectivity with each other, even when both communicating hosts lie behind NAT devices. The notion of "hole" relates to an IP transport connection address. + +NOTE – This transport protocol independent definition originates from [b-IETF RFC 5128]. + +**3.2.2 P2P services:** In the context of the present document, peer-to-peer services are characterized by the fact that the network is transparent to the application protocol in the user plane and the application protocol in the control plane is merely used for establishing an IP bearer in order to provide end-to-end connectivity. + +**3.2.3 TCP hole punching:** Hole punching for the TCP transport protocol (see clause 3.4 of [b-IETF RFC 5128]). + +NOTE – The method for TCP hole punching is also known as "Simultaneous TCP Open". + +**3.2.4 TCP merge mode:** The capability of resolving two, separate TCP connection establishment procedures (due to a network-side triggered "Simultaneous TCP Open" situation) towards a single end-to-end TCP connection. The TCP merge capability is located between the two TCP endpoints. + +**3.2.5 TCP packet:** IP datagram (also known as IP packet) carrying a (single) TCP segment in the payload. + +NOTE – Such a L4/L3 PDU is also known as TCP/IP packet (briefly TCP packet). + +**3.2.6 UDP hole punching:** Hole punching for the UDP transport protocol (see clause 3.3 of [b-IETF RFC 5128]). + +# 4 Abbreviations + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-----------------------------------| +| ALG | Application Level Gateway | +| B2BTE | Back-to-Back TCP Endpoint | +| BGF | Border Gateway Function | +| FTP | File Transfer Protocol | +| ICMP | Internet Control Message Protocol | +| IMS | IP Multimedia Subsystem | +| IP | Internet Protocol | +| IPv4 | Internet Protocol version 4 | + +| | | +|-------|--------------------------------------| +| IPv6 | Internet Protocol version 6 | +| HTTP | Hyper-Text Transfer Protocol | +| L3 | OSI model Layer 3 | +| L4 | OSI model Layer 4 | +| L4+ | Above OSI model Layer 4 | +| LD | Local Descriptor | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MSRP | Message Sending Relay Protocol | +| NAPT | Network Address and Port Translation | +| NAT | Network Address Translation | +| NAT-T | NAT Traversal | +| NGN | Next Generation Network | +| NPT | Network Prefix Translation (IPv6) | +| P2P | Peer-to-Peer | +| PDU | Protocol Data Unit | +| RD | Remote Descriptor | +| RTT | Round Trip Time | +| SBC | Session Border Controller | +| SBG | Session Border Gateway | +| SDP | Session Description Protocol | +| SEP | Stream Endpoint | +| SIP | Session Initiation Protocol | +| TCP | Transmission Control Protocol | +| TLS | Transport Layer Security | +| TRT | Transport Relay Translator | +| UDP | User Datagram Protocol | + +# 5 Conventions + +## 5.1 Conventions concerning the ITU-T H.248 gateway control protocol + +Elements of the ITU-T H.248 protocol model, e.g., Context, Termination, Stream, Event are represented using the first letter capitalized. Property, Event, Signal and Parameter identities are given in *italics*. + +The suffix ".req" added to an ITU-T H.248 command name stands for a command request, while the suffix ".rep" stands for a command reply. For example "Notify.req" represents a Notify Request. + +## 5.2 Conventions concerning the TCP bearer protocol + +The TCP protocol provides some flags in the TCP header, primarily used for TCP connection control. The following flags are used in this Recommendation: + +- SYN: Synchronize sequence numbers to initiate a connection. +- ACK: The acknowledgement number is valid. +- RST: Reset the connection. +- FIN: The sender finished sending data. + +Further conventions are: + +- SN: Sequence number (field in TCP header). +- AN: Acknowledgement number (field in TCP header). +- ISN: Initial SN value. + +Example: The notation "SYN(SN = $x_1$ ), ACK(AN = $y_2$ )" denotes a TCP packet for TCP connection control with an set SYN flag (for connection establishment purposes) and a sequence number value $x_1$ , plus the indication of a valid acknowledgement number with value $y_2$ . + +## 5.3 Conventions concerning the SIP Call control protocol + +The following conventions are used (concerning NAT-T) in the example signalling flows: + +X w SDP(Y:Z)                      SIP message type X with embedded SDP and the IP network address Y and port Z in the SDP media description. + +SDP media description [...] Important elements in the media description part of SDP Offer/Answer. + +# 6 NAT-traversal for peer-to-peer services + +## 6.1 Overview + +This Recommendation considers a simplified abstracted end-to-end scenario for NAT traversal for P2P services as shown in Figure 1. The use of a simplified notion of peer-to-peer is characterized by the facts that concern: + +**IP bearer path:** The IP application protocol is completely located in user equipment ("the IP host entities labelled as *peer* in Figure 1"), i.e., without any network side support by e.g., a server; + +**IP signalling path:** The IP application control protocol provides primarily only a session establishment service for the IP bearer in order to provide end-to-end connectivity. + +![Figure 1: Abstracted end-to-end model for NAT traversal support in peer-to-peer scenarios. The diagram shows a sequence of domains: (Home) Domain X, Domain A, Domain Z, Domain B, and (Home) Domain Y. In Domain X, a Peer (IP Host) X is connected to a NAT_X device. In Domain A, there is a SIP server/MGC and an IP-IP MG_A. In Domain Z, there is a SIP server/MGC and an IP-IP MG_B. In Domain B, there is a SIP server/MGC and an IP-IP MG_B. In Domain Y, a Peer (IP Host) Y is connected to a NAT_Y device. The diagram illustrates three types of paths: IP signalling path (solid red line), IP bearer path (dashed green line), and Gateway control (solid blue line labeled ITU-T H.248). A 'Decomposed session border gateway' is indicated between Domain A and Domain Z. The diagram is labeled H.248.84(12)_F01.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Legend: + +- IP signalling path (e.g., SIP) +- - - IP bearer path (e.g., TCP) +- Gateway control (here: ITU-T H.248) + +Figure 1: Abstracted end-to-end model for NAT traversal support in peer-to-peer scenarios. The diagram shows a sequence of domains: (Home) Domain X, Domain A, Domain Z, Domain B, and (Home) Domain Y. In Domain X, a Peer (IP Host) X is connected to a NAT\_X device. In Domain A, there is a SIP server/MGC and an IP-IP MG\_A. In Domain Z, there is a SIP server/MGC and an IP-IP MG\_B. In Domain B, there is a SIP server/MGC and an IP-IP MG\_B. In Domain Y, a Peer (IP Host) Y is connected to a NAT\_Y device. The diagram illustrates three types of paths: IP signalling path (solid red line), IP bearer path (dashed green line), and Gateway control (solid blue line labeled ITU-T H.248). A 'Decomposed session border gateway' is indicated between Domain A and Domain Z. The diagram is labeled H.248.84(12)\_F01. + +**Figure 1 – Abstracted end-to-end model for NAT traversal support in peer-to-peer scenarios** + +The following key characteristics may be identified from a NAT traversal perspective: + +1. The peer nodes (X and Y) are located in home domains with NAT devices and a NAPT function (for IPv4). For IPv6 it may be different, e.g., using the variant of network prefix translation only (abbreviated as NPTv6, see [b-IETF RFC 6296]); + +NOTE 1 – There are many different NA(P)T behaviours defined, which represent different NAT device types. Specific NAT behaviour was originally not defined, thus present classification schemes are mainly based on "reverse engineering" methods. The IETF RFC "*IP Network Address Translator (NAT) Terminology and Considerations*" [b-IETF RFC 2663] provides a first categorization attempt. + +The proposed terminology of [b-IETF RFC 2663] has been replaced, primarily by [b-IETF RFC 4787]. This later terminology is widely accepted. + +For instance, the NAT-T study in clause 4.3.1 of [b-ETSI TR 187 008] is based on that scheme. + +2. Multiple IP domains are interconnected by using e.g., so-called session border gateways (SBG; also known as session border controller, SBC)1. For the purposes of this Recommendation SBGs are decomposed according to the ITU-T H.248 model; + +NOTE 2 – These are ITU-T H.248 (IP, IP) media gateways. Correspondent ITU-T H.248 profiles are e.g., defined by some SDOs, which typically use SDO-specific names for the network elements (or functions). The terminology aspect is not relevant here. + +3. The specific translation behaviour of the remote NAT devices (NATX, NATY) is unknown (see also above notes); +4. The IP signalling path, carrying the IP application control protocol (e.g., SIP, but also others), is routed via the "MGC entities"; +5. The MGC entities are able to "derive some information for control of local NAT-T support" from the IP application control protocol traffic. + +NOTE 3 – Figure 1 shows an end-to-end scenario with two SBGs, however, the case with just a single SBG (and without domain Z) is also in scope. + +1 Such an entity is e.g., indicated in Supplement 1 to [b-ITU T Y.2012], *Session/border control (S/BC) functions*. + +## 6.2 Protocol dependencies + +The scenario in Figure 1 is generic concerning the protocols used above the IP layer by the peer nodes. Network side NAT-T support for such generic situations may not be excluded for particular use cases. However, it is expected that the NAT-T support function depends on the higher layer IP protocols used (Note) in the network bearer and/or signalling plane. Such use cases are within the scope of clause 7. + +NOTE – At least L4 awareness seems to be a basic requirement (i.e., the indication of the IP transport protocol type by the MGC to MG as bearer information) due to L4 port. + +# 7 Example use cases + +## 7.1 TCP bearer path with SIP signalling path + +SIP-controlled TCP connections are characterized by the following aspects: + +- Bearer type: TCP; +- Call/session control signalling: SIP with SDP Offer/Answer and SDP support for TCP connection control (based on [IETF RFC 4145]); +- ITU-T H.248 MG type: (IP, IP) connection model; +- Multiple ITU-T H.248 MGs in series as intermediate devices in the end-to-end TCP path; +- NAT traversal support function (by ITU-T H.248 MG's): support of "TCP simultaneously open" (see the "TCP hole punching" method in [b-IETF RFC 5128]); +- Location of merge point for the two "TCP connection establishment requests" (in case of TCP simultaneous open) in a TCP in-path ITU-T H.248 MG. + +The use case is summarized in Figure 2: + +- Multiple, k-1 MGs in the end-to-end TCP path; +- Each (IP, IP) MG may or may not provide a local NA(P)T function (NAT-full vs NAT-less); +- If all MGs operate in NAT-full mode there are k IP network domains (labelled as $D_i$ with $i = [1, k]$ ); +- The two TCP endpoints are part of the peer entities ( $Peer_X, Peer_Y$ ); +- The peer entities are located behind remote NAT devices (from ITU-T H.248 MG perspective), labelled as $NAT_X$ and $NAT_Y$ ; + +Clause I.1 provides an example signalling flow based on the above use case. + +![Reference model diagram for TCP bearer and SIP signalling path with multiple MGs. The diagram shows a path from (Home) Domain X through multiple domains (D1, D2, D3, ..., Dk-1, Dk) to (Home) Domain Y. Each domain contains a SIP server (MGC) and an ITU-T H.248 border router/gateway (MG) with a TCP mode. The path involves SIP signalling and TCP bearers passing through NATs and MGs. Labels include Peer_x, NAT_x, MG1, MG2, ..., MGk-1, NAT_y, Peer_y, and H.248.84(12)_F02. A dashed box labeled 'NAT-full or NAT-less' is shown below the first NAT.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +The diagram illustrates a network architecture for TCP bearer and SIP signalling. It starts with (Home) Domain X on the left, containing an IP host with a SIP user agent and TCP endpoint (Peerx) connected to a NAT (NATx). The NAT connects to Domain D1, which contains an ITU-T H.248 border router/gateway (MG1) with a TCP mode. A SIP server (MGC1) is also in Domain D1. The path continues through Domain D2 (MG2, MGC2) and then through an ellipsis to Domain Dk-1 (MGk-1, MGCk-1). Domain Dk follows, containing a NAT (NATy) which connects to (Home) Domain Y. Domain Y contains an IP host with a SIP user agent and TCP endpoint (Peery). SIP signalling is shown between the SIP user agents and the SIP servers. TCP bearers are shown passing through the NATs and the ITU-T H.248 border routers/gateways. A dashed box labeled 'NAT-full or NAT-less' is shown below the first NAT. The label 'H.248.84(12)\_F02' is at the bottom right. + +Reference model diagram for TCP bearer and SIP signalling path with multiple MGs. The diagram shows a path from (Home) Domain X through multiple domains (D1, D2, D3, ..., Dk-1, Dk) to (Home) Domain Y. Each domain contains a SIP server (MGC) and an ITU-T H.248 border router/gateway (MG) with a TCP mode. The path involves SIP signalling and TCP bearers passing through NATs and MGs. Labels include Peer\_x, NAT\_x, MG1, MG2, ..., MGk-1, NAT\_y, Peer\_y, and H.248.84(12)\_F02. A dashed box labeled 'NAT-full or NAT-less' is shown below the first NAT. + +NAT Network address (and port) translator + SIP Session initiation protocol + TCP Transmission control protocol + +**Figure 2 – Reference model for the example of TCP bearer and SIP signalling path with multiple, k-1 MGs in the end-to-end TCP path** + +# 8 NAT-traversal peer-to-peer package + +Package name: NAT-traversal peer-to-peer package + +Package ID: nattp2p (0x010d) + +Description: This package provides support for the traversal of remote NAT devices in addition to the NAT-T tools defined by [ITU-T H.248.37] and [ITU-T H.248.50]. The NAT-T support here is independent of specific IP transport protocols. + +Version: 1 + +Extends: None + +## 8.1 Properties + +None. + +## 8.2 Events + +### 8.2.1 Remote NAT device reaction on network layer + +Event name: Remote NAT device reaction on network layer + +Event ID: rnatip (0x0001) + +Description: This Event indicates the reaction of a remote NAT device after the Termination/Stream was created for bearer traffic transmission. + +This Event is typically only enabled during the establishment phase of the end-to-end IP bearer-path, i.e., the time period of successful or unsuccessful NAT-T. + +This Event is not used in the context of keep-alive procedures. These procedures are another means for NAT-T support, and are primarily applied during the communication phase. + +The result of setting this Event may assist in concluding: + +- whether NAT-T was successful or not, +- the possible NAT device type with regards to NAT behaviour, or +- possible follow-up actions by the MG (e.g., sending ICMP messages in the IP bearer-path). + +The ObservedEvent shall indicate possible unsuccessful traversal scenarios of the remote NAT device. + +#### 8.2.1.1 EventsDescriptor parameters + +##### 8.2.1.1.1 Maximum duration of observation + +Parameter name: Maximum duration of observation + +Parameter ID: maxdur, (0x0001) + +Description: The time period for the MG to observe the IP bearer path in the incoming direction after the event is enabled. + +Type: Integer + +Optional: Yes + +Possible values: Any positive integer in milliseconds + +Default: Provisioned + +#### 8.2.1.2 ObservedEventsDescriptor parameters + +##### 8.2.1.2.1 Reply by remote NAT device + +Parameter name: Reply by remote NAT device + +Parameter ID: rep (0x0001) + +Description: This parameter indicates possible unsuccessful traversal scenarios of the remote NAT device, given by a received ICMP message by the MG. + +Type: Enumeration + +Optional: No + +Possible values: ICMP (0x0001): ICMP *Destination Unreachable* (Type 3, Code -) + +Default: None. + +## 8.3 Signals + +None. + +## 8.4 Statistics + +None. + +## 8.5 Error codes + +None. + +## 8.6 Procedures + +Appendix IV indicates high level scenarios of possible environments which could benefit from *nattp2p* package support. + +### 8.6.1 Observation of remote NAT device types by monitoring incoming ICMP + +Remote NAT devices, located in the IP bearer path, would typically reply with an ICMP message in case of unsuccessful creation of NAT bindings. If this ICMP message is received within the maximum duration of observation time the ObservedEvent is triggered. + +# 9 TCP hole punching package + +Package name: TCP hole punching package + +Package ID: tcphp (0x010e) + +Description: This package defines procedures for the NAT-T method "TCP hole punching", as required for SDP-controlled TCP-based peer-to-peer sessions (if NAT traversal support is provided by ITU-T H.248 gateways). + +Events and Statistics are defined which may be beneficial for the evaluation of successful and unsuccessful NAT-T scenarios. + +Version: 1 + +Extends: None + +## 9.1 Properties + +None. + +## 9.2 Events + +### 9.2.1 Remote NAT device reaction + +Event name: Remote NAT device reaction + +Event ID: rnat (0x0001) + +Description: This Event indicates the reaction of a remote NAT device when the MG has sent a TCP SYN packet. The event shall be set at Stream level. + +The observed reaction may allow to assist in concluding the possible NAT device type with regards to NAT behaviour for TCP according to [IETF RFC 5382], especially whether REQ-4 in clause 8 of [IETF RFC 5382] is supported. + +The ObservedEvent shall indicate possible unsuccessful traversal scenarios of the remote NAT device. + +#### 9.2.1.1 EventsDescriptor parameters + +##### 9.2.1.1.1 Maximum duration of observation + +Parameter name: Maximum duration of observation + +Parameter ID: maxdur, (0x0001) + +Description: The time period for the MG to observe the IP bearer path in the incoming direction after sending a TCP SYN packet. + +Type: Integer + +Optional: Yes + +Possible values: Any positive integer in milliseconds + +Default: Provisioned + +#### 9.2.1.2 ObservedEventsDescriptor parameters + +##### 9.2.1.2.1 Reply by remote NAT device + +Parameter name: Reply by remote NAT device + +Parameter ID: rep (0x0001) + +Description: This parameter indicates possible unsuccessful traversal scenarios of the remote NAT device, given by a received TCP RST packet or an ICMP message by the MG. + +Type: Enumeration + +Optional: No + +Possible values: RST (0x0001): TCP RST packet. + +ICMP (0x0002): ICMP *Port Unreachable error* (Type 3, Code 3) + +Default: None. + +### **9.2.2 Remote TCP connection termination detected** + +Event name: Remote TCP connection termination detected +Event ID: rrel (0x0002) +Description: This Event indicates the detection of an incoming received TCP FIN packet. The event shall be set at Stream level. +This Event indicates that the remote TCP endpoint initiated TCP's *half-close* procedure, as part of the overall TCP connection termination. +This Event may be useful in successful and unsuccessful call scenarios. + +#### **9.2.2.1 EventsDescriptor parameters** + +None. + +#### **9.2.2.2 ObservedEventsDescriptor parameters** + +None. + +## **9.3 Signals** + +None. + +## **9.4 Statistics** + +### **9.4.1 Number of received TCP segments with set RST flag** + +Statistic name: Number of received TCP segments with set RST flag +Statistic ID: rstrx (0x0001) +Description: This Statistic counts the number of received TCP segments with the RST flag set. The Statistic is related to external TCP segments and not to Context-internal TCP segments, as possibly received from the peering ITU-T H.248 Stream endpoint (SEP) within a Context. Such a statistic may be useful in case of the evaluation of unsuccessful NAT traversal scenarios. +Type: Double +Possible values: Any non-negative value +Level: Either + +### **9.4.2 Number of received TCP segments with set SYN flag** + +Statistic name: Number of received TCP segments with set SYN flag +Statistic ID: synrx (0x0002) +Description: This Statistic counts the number of received TCP segments with the SYN flag set. The statistic is related to external TCP segments and not to Context-internal TCP segments, as possibly received from the peering ITU-T H.248 Stream endpoint (SEP). Such a statistic may be useful in case of the evaluation of unsuccessful NAT traversal scenarios. +Type: Double +Possible values: Any non-negative value +Level: Either + +## 9.5 Error codes + +None. + +## 9.6 Procedures + +### 9.6.1 Observation of remote NAT device types + +The concrete behaviour of remote NAT devices, located in the IP bearer path, is typically unknown in many deployment scenarios. In order to improve traversal for packets from remote NAT devices, the MGC may enable the *rnat* Event. + +The detection and notification of this Event by the MG to the MGC may be useful information for use with different NAT traversal strategies (these strategies are out of scope of this Recommendation). + +### 9.6.2 Observation of TCP connection termination + +The MGC may enable Event *rrel* in order to observe the initiation of TCP connection release activities by the remote TCP endpoint (as associated with the local SEP). + +The notification of this Event by the MG to the MGC: + +- During call establishment (or modification), phases could be an indicator for unsuccessful P2P service delivery; +- During call release, phases could be used for a synchronized release of call and bearer level resources (MGC and MG). + +# 10 TCP traffic volume metrics package + +Package name: TCP traffic volume metrics package + +Package ID: tcptv (0x010f) + +Description: This package is used to support explicit octet and packet count statistics for the TCP bearer protocol. The statistics are applicable for all TCP modes of operation, as long as the MG is aware that the ITU-T H.248 Stream carries TCP traffic. + +Version: 1 + +Extends: None. + +## 10.1 Properties + +None. + +## 10.2 Events + +None. + +## 10.3 Signals + +None. + +## 10.4 Statistics + +### 10.4.1 TCP Octets Sent + +| | | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic name: | TCP Octets Sent | +| Statistic ID: | tcpos (0x0001) | +| Description: |

This Statistic provides the number of octets sent from the Termination or Stream since the Termination or Stream has existed and the Statistic has been set. The octets represent the egress TCP packets of all TCP flows of an ITU-T H.248 Stream.

It is the total number of octets (i.e., including TCP header) transmitted in TCP packets. At the Termination level, it is equal to the sum of the egress TCP flows over all Streams.

| +| Type: | Double | +| Possible values: | Any 64-bit integer 0 and up | +| Level: | Either | + +### 10.4.2 TCP Octets Received + +| | | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic name: | TCP Octets Received | +| Statistic ID: | tcpor (0x0002) | +| Type: | Double | +| Description: |

This Statistic provides the number of octets received on the Termination or Stream since the Termination or Stream has existed and the Statistic has been set. The octets represent the ingress TCP packets of all TCP flows of an ITU-T H.248 Stream.

It is the total number of octets (i.e., including TCP header) received in TCP packets. At the Termination level, it is equal to the sum of the ingress TCP flows over all Streams.

| +| Possible values: | Any 64-bit integer 0 and up | +| Level: | Either | + +### 10.4.3 TCP Packets Sent + +| | | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic name: | TCP Packets Sent | +| Statistic ID: | tcpps (0x0003) | +| Description: |

This Statistic provides the number of packets sent from the Termination or Stream since the Statistic has been set. The packets represent the egress TCP packets of all TCP flows of an ITU-T H.248 Stream.

It is the total number of TCP packets, inclusive of TCP connection establishment, data transfer and connection release phases. At the Termination level, it is equal to the sum of the egress TCP flows over all Streams.

| +| Type: | Double | +| Possible values: | Any 64-bit integer 0 and up | +| Level: | Either | + +### 10.4.4 TCP Packets Received + +| | | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Statistic name: | TCP Packets Received | +| Statistic ID: | tcppr (0x0004) | +| Type: | Double | +| Description: |

Provides the number of packets received on the Termination or Stream since the statistic has been set. The packets represent the ingress TCP packets of all TCP flows of an ITU-T H.248 Stream.

It is the total number of TCP packets, inclusive of TCP connection establishment, data transfer and connection release phases. At the Termination level, it is equal to the sum of the ingress TCP flows over all Streams.

| +| Possible values: | Any 64-bit integer 0 and up | +| Level: | Either | + +## 10.5 Error codes + +None. + +## 10.6 Procedures + +### 10.6.1 Ingress TCP traffic – Statistic "TCP Packets Received" + +Every incoming TCP packet *successfully delivered* to its ITU-T H.248 Context and ITU-T H.248 TCP Stream/Termination is counted by Statistic *tcptv/tcppr*. + +### 10.6.2 Ingress TCP traffic – Statistic "TCP Octets Received" + +The measurement represents the volume of all *TCP flows* of an ITU-T H.248 Stream, i.e., across all received TCP packets according to Statistic *tcptv/tcpor*. + +### 10.6.3 Egress TCP traffic – Statistic "TCP Packets Sent" + +Every outgoing TCP packet, sent from an ITU-T H.248 TCP Stream/Termination, is counted by Statistic *tcptv/tcpss*. + +### 10.6.4 Egress TCP traffic – Statistic "TCP Octets Sent" + +The measurement represents the volume of all *TCP flows* of an ITU-T H.248 Stream, i.e., across all sent TCP packets according to Statistic *tcptv/tcpos*. + +# 11 TCP connection control metrics package + +| | | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | TCP connection control metrics package | +| Package ID: | tcpccm (0x0110) | +| Description: | This package defines three statistics related to the observation of TCP connection establishment, which is generally a performance indication of successful NAT traversal support, based on the TCP merge mode. | +| Version: | 1 | +| Extends: | None. | + +## 11.1 Properties + +None. + +## 11.2 Events + +None. + +## 11.3 Signals + +None. + +## 11.4 Statistics + +### 11.4.1 TCP connection establishment delay (in TCP merge mode) + +Statistic name: TCP connection establishment delay (in TCP merge mode) + +Statistic ID: tcpest (0x0001) + +Description: This is a Stream level Statistic for a connection model of two associated Stream endpoints (SEP) for an end-to-end TCP connection (see also clause 13.3). The performance metric relates to the time in milliseconds from reception of the ITU-T H.248 command request for the 2nd SEP till the received or sent TCP ACK packets at both SEPs for successful connection establishment. + +NOTE 1 – This statistic is thus related to reference events at the MG ITU-T H.248 interface and MG 'TCP' bearer interface. + +Type: Double + +Possible values: Any 64-bit integer 0 and up + +Level: Stream + +NOTE 2 – It should be noted that the 'Stream' level is related to a particular Stream endpoint, see clause V.1 for an example illustration. It would be hence sufficient to keep just one statistic, e.g., statistic *tcpest* enabled at one termination and disabled at the other associated termination. The activation and deactivation of individual statistics is described in clauses IV.3.2 and IV.3.3 of [ITU-T H.248.1]. + +### 11.4.2 Sent TCP connection establishment attempts + +Statistic name: Sent TCP connection establishment attempts + +Statistic ID: tcpsyntx (0x0002) + +Type: Double + +Description: This is a Stream endpoint specific statistic, counting the number of outgoing SYN segments (i.e., a TCP packet with a set SYN flag). Such a performance parameter provides a measure how many times remote TCP node tries to establish a TCP connection. + +Possible values: Any 64-bit integer 0 and up + +Level: Stream + +### 11.4.3 Received TCP connection establishment attempts + +Statistic name: Received TCP connection establishment attempts + +Statistic ID: tcpsynrx (0x0003) + +Type: Double + +| | | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Description: | This is a Stream endpoint specific Statistic, counting the number of incoming SYN segments (i.e., a TCP packet with a set SYN flag). Such a performance parameter provides a measure how many times remote TCP node tries to establish a TCP connection. | +| Possible values: | Any 64-bit integer 0 and up | +| Level: | Stream | + +## 11.5 Error codes + +None. + +## 11.6 Procedures + +### 11.6.1 TCP connection establishment delay from perspective of ITU-T H.248 entities + +Statistic *tcpccm/tcpest* may be useful for measuring the latency between a call control initiated TCP merge mode and a finally successful established end-to-end TCP bearer connection. Unusually high values could be an indicator e.g.: + +- multiple TCP connection establishment reattempts (Note: captured also by counter-based statistics *tcpsynrx*), which may be caused by traversal attempts for remote NAT devices; or +- long distance end-to-end TCP connections. + +Clause 6.1.1 of [b-ITU-T Y.1560] also defines a performance parameter for TCP connection establishment delay. However, this has an end-to-end perspective related to measurement points (MP) located at TCP endpoint side, thus the far-end from "middlebox" (e.g., ITU-T H.248 MG) point of view. In contrast Statistic *tcpccm/tcpest* may be produced solely based on MG-local measurements. + +### 11.6.2 TCP connection establishment attempts from perspective of ITU-T H.248 entities + +Statistics *tcpccm/tcpsynrx* and *tcpccm/tcpsyntx* may be useful for counting the number of connection establishment attempts. The values of correspondent statistics at SEPs $T_a/S_i$ and $T_b/S_i$ (see clause 13.3), e.g., *tcpccm/tcpsynrx* at SEP $T_a/S_i$ and *tcpccm/tcpsyntx* at SEP $T_b/S_i$ , must not be necessarily the same. For instance, TCP SYN segments could be internally dropped, dependent on the particular MG strategy for "TCP merge" mode. + +# 12 TCP connection quality metrics package + +| | | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name: | TCP connection quality metrics package | +| Package ID: | tcpqcm (0x0111) | +| Description: |

This package defines and discusses Statistics related to the observation of TCP round-trip time (RTT) performance parameters, from the specific perspective of an ITU-T H.248 MG, rather than the usual observation by a TCP endpoint in user equipment.

The ITU-T H.248 Statistic(s) are consistent with the [IETF RFC 793] RTT measurement concept and may be useful for packet transfer delay observations.

| +| Version: | 1 | +| Extends: | None. | + +## 12.1 Properties + +None. + +## 12.2 Events + +None. + +## 12.3 Signals + +None. + +## 12.4 Statistics + +### 12.4.1 TCP round-trip time during connection establishment phase + +Statistic name: TCP round-trip time during connection establishment phase + +Statistic ID: tcprtttest (0x0001) + +Type: Double + +Description: The TCP round-trip time (RTT) is defined by clause 3.7 of [IETF RFC 793] as: + +*"Measure the elapsed time between sending a data octet with a particular sequence number and receiving an acknowledgement that covers that sequence number (segments sent do not have to match segments received). This measured elapsed time is the Round Trip Time (RTT)."* + +NOTE – The RTT measurement principle is also detailed in clause on "TCP Timeout and Retransmission" in [b-TCP/IP Vol.1]). + +This ITU-T H.248 Statistic may be: + +1. a sample value in case of a single two-way handshake of SYN and ACK related TCP packets, or +2. based on a smoothed RTT estimator (according to [IETF RFC 793]) in case of multiple SYN/ACK cycles. + +The time unit is milliseconds. + +This Statistic is related to a particular ITU-T H.248 Stream endpoint. The reference events for this Statistic are related to the MG external TCP interface (i.e., outgoing TCP SYN and incoming TCP ACK packets). The observed TCP RTT consequently represents a virtual RTT figure (for something like a "half TCP connection") and should not be confused with the RTT for the end-to-end TCP connection (as e.g., perceived by peer *X* or *Y* in Figure 2). See also clause V.2. + +Possible values: Any 64-bit integer 0 and up + +Level: Either + +### 12.4.2 TCP round-trip time during TCP connection lifetime + +Such a Statistic requires the monitoring of all SN and AN values of all incoming and outgoing TCP packets over the lifetime of a TCP connection. The permanent monitoring of SN and AN numbers would be a native function in a TCP proxy mode, but fairly costly in TCP relay and TCP merge mode. The definition of such a statistic is for further studies. + +## 12.5 Error codes + +None. + +## 12.6 Procedures + +### 12.6.1 TCP round-trip time during connection establishment phase + +Statistic *tcpqcm/tcprttest* may be useful for measuring the time between sent TCP octets and their correspondent acknowledgment, from perspective of the ITU-T H.248 MG. This is a pure IP bearer-path related measurement, therefore slightly different to the time-based statistics from clause 11. + +This Statistic is a key performance indicator concerning IP network conditions. + +# 13 Package-independent procedures for NAT-T with TCP bearers + +## 13.1 TCP mode of operation: decision baseline in MGC + +The MGC is responsible for the assigned TCP mode of operation. The decision itself is out of scope of ITU-T H.248 signalling and is rather expected to be subject of call-level signalling, local policies, configuration management, or/and other items. + +## 13.2 TCP mode of operation: control principle at ITU-T H.248 interface + +This Recommendation does not define any new ITU-T H.248 Properties for controlling the *TCP mode* of operation of an (IP, IP) context. The control approach is rather to use existing properties such as SDP elements according to [IETF RFC 4145] within the ITU-T H.248 Descriptors for each stream endpoint (SEP) configuration. + +## 13.3 Supported connection model + +Only connection models of type (IP, IP) are applicable for this Recommendation (because TCP supports only unicast communication topologies). This implies an IP-based ITU-T H.248 Stream for TCP traffic. As a result of the connection model there are two stream endpoints (SEP), denoted by the example identifiers $T_a/S_i$ and $T_b/S_i$ (as TerminationID/StreamID) in Figure 3. + +![Diagram of the ITU-T H.248 connection model (IP, IP). A grey box labeled 'ITU-T H.248 context C_z' contains two 'Termination' boxes, 'Termination "T_a"' and 'Termination "T_b"'. Each termination box contains a 'SEP' (Stream Endpoint) icon, which is a circle with two arrows pointing in opposite directions, labeled 'S_i'. A dashed line with arrows at both ends connects the two SEPs, representing a bidirectional TCP connection. The text 'TCP packet flows of a single TCP connection' is written below the dashed line. The diagram is labeled 'H.248.84(12)_F03' in the bottom right corner.](82b40cb8b2a5ac361973859400fa128a_img.jpg) + +ITU-T H.248 connection model: (IP, IP) + +ITU-T H.248 context $C_z$ + +Termination "Ta" + +SEP + +$S_i$ + +Termination "Tb" + +SEP + +$S_i$ + +TCP packet flows of a single TCP connection + +H.248.84(12)\_F03 + +Diagram of the ITU-T H.248 connection model (IP, IP). A grey box labeled 'ITU-T H.248 context C\_z' contains two 'Termination' boxes, 'Termination "T\_a"' and 'Termination "T\_b"'. Each termination box contains a 'SEP' (Stream Endpoint) icon, which is a circle with two arrows pointing in opposite directions, labeled 'S\_i'. A dashed line with arrows at both ends connects the two SEPs, representing a bidirectional TCP connection. The text 'TCP packet flows of a single TCP connection' is written below the dashed line. The diagram is labeled 'H.248.84(12)\_F03' in the bottom right corner. + +NOTE – A TCP connection is inherently bidirectional (opposed to, e.g., UDP) due to the connection-oriented property. + +**Figure 3 – Supported ITU-T H.248 connection model** + +There may be a single or multiple Streams per Termination. The TCP mode of operation is a Stream level characteristic. + +### 13.3.1 Comment to connection models with more than two IP terminations + +There are also connection models with more than two TCP/IP terminations, e.g., in cases of an MG providing a MSRP [IETF RFC 4975] switch function according to [ITU-T H.248.69]. Such a connection model is characterized by an application function on top of multiple, interconnected TCP endpoints (realized as ITU-T H.248 TCP SEPs). This would be a kind of TCP proxy mode ("an application aware TCP proxy"), but neither a TCP relay nor TCP merge mode. + +Some observations: + +- If TCP simultaneous open would be applied as the NAT-T method, then the MG would have to provide a TCP endpoint role. The MGC would then trigger TCP connection establishment as e.g., described in clause 6.2 of [ITU-T H.248.69]. +- The TCP performance parameters might be different, following existing TCP endpoint metrics, rather than the ones of clauses 11 and 12. + +## 13.4 Indication of IP transport protocol 'TCP' + +The ITU-T H.248 Stream protocol stack is generalised by *X/TCP/IP*. The IP protocol versions of both associated SEPs may be equal or different. The two modes TCP relay and TCP merge may be agnostic to the carried IP application protocol *X*. Such a Context setting is sometimes also called a "transport protocol type aware, application agnostic" (or "L4+ agnostic") stream configuration. + +For any TCP mode of operation, the L4 protocol element in LD and RD must indicate 'TCP' as transport protocol (e.g., there are multiple possible values in ITU-T H.248 text encoding, see [b-IANA SDP]). The MGC shall signal the same transport protocol indication in the 4-tuple {Ta(LD), Ta(RD), Tb(LD), Tb(RD)} of a particular ITU-T H.248 Stream. + +NOTE 1 – ITU-T H.248 text encoding: the value 'TCP' would be an application agnostic indication, and values like 'TCP/...' would be examples for application awareness: e.g., 'TCP/BFCP', 'TCP/MSRP'. + +NOTE 2 – ITU-T H.248 text encoding: the value setting of the "m=" line field is basically out of scope of this Recommendation, see also clause 13.5.2. + +## 13.5 Indication of 'TCP mode' for ITU-T H.248 MG + +### 13.5.1 Via SDP attribute "a=setup:" + +The MGC shall use the SDP attribute "a=setup:" (see [IETF RFC 4145]) for the TCP mode assignment of a particular Stream. Table 1 defines the allowed roles (i.e., SDP a=setup: role value settings), given by the 4-tuple {Ta(LD), Ta(RD), Tb(LD), Tb(RD)}. + +**Table 1 – Indication of 'TCP mode' by MGC to MG – SDP value combinations** + +| ITU-T H.248 SEP | | SDP attribute | TCP relay mode | TCP merge mode | TCP proxy mode | +|-----------------|----|---------------|----------------|----------------|----------------| +| Ta | LD | a=setup: | not sent | 'passive' | 'actpass' | +| | RD | a=setup: | not sent | not sent | 'actpass' | +| Tb | LD | a=setup: | not sent | 'passive' | 'actpass' | +| | RD | a=setup: | not sent | not sent | 'actpass' | + +NOTE 1 – The semantic of "not sent" means that the MGC shall not include this SDP attribute in the ITU-T H.248 Descriptor, despite the fact whether it is used on call signalling level. +NOTE 2 – The TCP proxy mode is not subject of the specified NAT-T mechanisms by this Recommendation. + +The MG shall reply with error code 449 in case of incorrect value settings. + +When the MG is able to derive a particular TCP mode (according to Table 1), then the MG may cross-check whether the four values in the "transport protocol 4-tuple" (according to clause 13.4) are identical. The MG shall reply with error code 473 in case of incorrect or missing value settings in respective "m=" line fields (which includes value '-'). + +### **13.5.2 Consideration of SDP "m=" line field 'media type' due to backward compatibility reasons** + +The TCP mode assignment method is already unambiguous solely on the basis of the "a=setup:" attribute. If this Recommendation would be applied in the Context of an evolution of ETSI TISPAN ITU-T H.248 "Ia" profile [b-ETSI TS 183 018], then the TCP mode assignment recommendations according to clause I.4.1.1 of [b-ETSI TR 183 068] would be beneficial. The TCP mode assignment guidelines are based on the SDP "m=" line field 'media type' and were introduced for the differentiation between TCP relay and TCP proxy mode. + +## **13.6 TCP connection reuse** + +[IETF RFC 4145] allows an indication during session initiation whether a new or existing TCP connection may be used. This is only related to call/session control signalling and thus the MGC shall not use the SDP attribute "a=connection:" (see [IETF RFC 4145]) for TCP mode assignment signalling toward the MG (see also Appendix III). + +The MG may reply with error code 446 in case of received LD/RD with SDP attribute "a=connection:". + +## **13.7 TCP connection establishment phase – Handling of TCP Protocol Control Information by the ITU-T H.248 MG** + +The IP packet payload carries a single TCP segment, which again consists of TCP header and application data information as the payload. Some flags within the TCP header are in scope of this Recommendation. + +### **13.7.1 TCP bearer traffic in general** + +The MG shall check the 8-bit protocol value in the IP header for TCP traffic (value '17'). The handling of detected non-TCP IP packets is out of scope of this Recommendation. + +### **13.7.2 MG behaviour in TCP relay mode** + +The MG shall be basically agnostic to all TCP header elements. + +NOTE – The application of a local NAPT function may require the update of TCP checksum information. + +### **13.7.3 MG behaviour in TCP merge mode** + +#### **13.7.3.1 Basic capabilities** + +The MG must provide: + +- a detection and modification capability for flag settings for SYN, ACK, RST and FIN; +- a detection and modification capability for numbers SN and AN; and +- state machine(s) for saving the status of ITU-T H.248 Stream endpoints and Context during TCP connection establishment and release. + +The detection and modification capability is required for external and internal TCP segments, from a SEP perspective. + +A detailed specification of a state machine is out of scope of this Recommendation, though such a state machine could be expected to be a subset of the regular TCP state machine (see Figure 6 "TCP Connection State Diagram" in [IETF RFC 793]). + +#### 13.7.3.2 Merge procedure + +Example merge procedures are illustrated in Figures I.3 and I.4. The ITU-T H.248 Stream is initially prepared for TCP merge mode by the MGC (see clause 13.5) before any bearer traffic is received. + +Both SEPs are initially "passive open", i.e., awaiting the reception of a TCP SYN segment, from external or internal side. More details are provided in Appendix I. + +NOTE – Both TCP endpoints act initially as TCP clients in case of "Simultaneous TCP Open". The network element (here: ITU-T H.248 MG) in TCP merge mode plays thus the TCP server role towards both TCP clients. Such kind of role masquerading is also known as "TCP spoofing". + +## 13.8 Unsuccessful NAT-T scenarios + +### 13.8.1 Packet loss by IP network + +Loss of TCP/IP packets is detected by the TCP endpoints, which then leads to retransmission of the packets. + +NOTE – Such a basic TCP endpoint behaviour is also relevant for TCP proxy mode. + +### 13.8.2 Blocking of TCP/IP packets by remote NAT devices + +A remote NAT device (e.g., entities NATX or NATY in Figure 2) may block TCP/IP packets. The ITU-T H.248 application data inactivity package [ITU-T H.248.40] may be used for detection of such deadlock situations. + +### 13.8.3 Rejection of TCP SYN segments by remote NAT devices + +Remote NAT devices could reject a TCP SYN with a TCP RST (see clause 3.4 of [b-IETF RFC 5128]). The MG shall update Statistic *tcphp/rstrx* when detecting an incoming TCP RST from external side. Such a Statistic could be beneficial for offline analysis of unsuccessful NAT traversal scenarios (see also clause 9.6.1). + +### 13.8.4 Expiration of TCP protocol timers + +The TCP connection establishment is the crucial phase from NAT-T point of view. There are two active timers in a TCP protocol endpoint during the establishment phase [b-TCP/IP Vol.2]: the connection-establishment timer (for controlling the maximum duration of the establishment phase) and retransmission timer (for determination of the increasing inter-arrival times between establishment re-attempts). + +Following conclusions are derived under the assumption of typical TCP timer settings: + +- The successful establishment of an end-to-end TCP connection may last up to 75 seconds; the MGC may take this timing into consideration in order to avoid an early release of MG Context resources; +- There could be up to three incoming TCP SYN packets; which should be taken into account by the MG in TCP merge mode (see e.g., clause I.1.3). + +## 13.9 Impact of transport protocol encryption + +The most widely-used protocol for transport security operates just above the transport layer, and is called transport layer security (TLS). Prerequisite for the operation of TLS implies a successfully established TCP connection. Thus, there will be initially TCP packets in native, unencrypted format, during the initial TCP connection establishment phase. Hence, the use of TLS does not + +prevent activating the TCP relay and TCP merge modes. However, the TCP merge mode may prevent end-to-end establishment of a TLS session (e.g., when [b-IETF RFC 4572] is used to negotiate the role of the TCP connection and TLS session initiators) unless specific assumptions are made with respect to the coordination and control of the initial NAT-T phase and the subsequent TLS session establishment phase. This aspect is out of scope of this Recommendation. + +## **13.10 Interactions with NAT-T method latching/relatching** + +No interactions between the [ITU-T H.248.37] defined NAT-T method and this Recommendation are identified. See also package-independent procedure in clause 14.1. + +## **13.11 Possible interactions with enabled filters for TCP traffic** + +Possible interactions with TCP filters should be considered. See also package-independent procedures in clause 14.2. + +# **14 Package-independent, bearer-independent procedures for NAT-T** + +This clause discusses ITU-T H.248 session-/call-dependent procedures which are independent of any ITU-T H.248 package defined by this Recommendation. Such procedures may be applicable when packages defined by this Recommendation are used with other functionality, particularly other packet processing capabilities (like e.g., filtering), other NAT-T methods, etc. + +These procedures may be referred or used by ITU-T H.248 profile specifications for ITU-T H.248 IP-to-IP gateway types. + +## **14.1 Relations to latching/relatching based NAT traversal support** + +The MGC may not know the correct remote destination IP transport address information; therefore it should activate latching or relatching on the MG according to [ITU-T H.248.37]. Such an additional NAT-T method is independent of the IP transport protocol used, and also independent of the specific L4 processing mode used by the MG (like e.g., TCP relay or TCP merge mode in case of TCP). + +The relatch mode may be more effective in IP transport connection establishment scenarios where the IP terminal or/and remote NAT device changes the L4 port value multiple times (e.g., due to connection establishment reattempts). + +## **14.2 Interaction with L4 filters** + +The NAT-T methods in scope of this Recommendation rely on the complete end-to-end flow of L4-PDUs, at least during the initial IP transport connection establishment phase and NAT-T attempts. Any enabled L4 filter which impacts the L4-PDUs may thwart the NAT-T support function(s). + +### **Example 1:** + +MG1 may be located at the network edge, assigned as TCP relay and enabled for a filter on IP transport addresses (remote or destination). The value range of excluded addresses as specified by the filters could overlap with the IP transport addresses as selected by the TCP endpoints or as translated by remote NAT device(s). This would then prevent successful NAT-T by another MG2 in TCP merge mode. + +Such a deadlock situation could be avoided by "fine tuning" filters after successful establishment of the end-to-end IP bearer path, by e.g., the analysis of the final remote IP transport addresses used via the [ITU-T H.248.37] address reporting capability. + +### **Example 2:** + +A security policy rule may define a filter on TCP header flags (see e.g., clause 9 of [b-ITU-T H.248.79]), which could lead to the blocking of e.g., TCP SYN segments. + +# Appendix I + +## Example signalling scenarios + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides example signalling for use cases introduced in clause 7. + +## I.1 Example signalling for use case "TCP bearer path with SIP signalling path" + +### I.1.1 Overall picture + +This use case is presented in clause 7.1. Figure I.1 outlines a possible example overall scenario, covering the simplified SIP session establishment, indicating some ITU-T H.248 signalling, showing the TCP connection establishment based on simultaneous TCP open, and finally the IP application data transfer (for the generic *XoTCP* application protocol). + +ITU-T H.248 gateway signalling is triggered during the call control signalling phase for session establishment: in Figure I.1 by the capability declaration and negotiation signalling by SDP Offer/Answer procedures on SIP level. + +The following TCP modes are assigned by the MGCs to the MG: MG#A in *TCP relay* mode and MG#B in *TCP merge* mode. It may be noted to Figure I.1 that ITU-T H.248 entity MG#B, which is initially operated in *TCP merge* mode, may be later modified to *TCP relay* mode. Thus, the TCP merge mode is essentially only active during the "hole punching" phase(s). + +The two TCP packets (16 and 17) show the TCP SYN segments due to the triggered TCP simultaneous open. + +The example ITU-T H.248 signalling for TCP mode assignment is further detailed in clause I.1.2. The example TCP bearer traffic during TCP connection established is further detailed in clause I.1.3. + +### I.1.2 ITU-T H.248 signalling for TCP mode assignment + +#### I.1.2.1 TCP merge mode + +Example ITU-T H.248 signalling for TCP merge mode assignment is illustrated in Figure I.2. The MG provides also a local NAPT function, therefore the indication of IP transport address values. + +Some notes to the signalling flow (Figure I.2): + +The incoming SDP Offer at SIP level (1) triggers two ITU-T H.248 ADD.req commands (2, 5), leading to a Context creation with Terminations Ta and Tb; + +- The MG is aware of IP transport protocol 'TCP' due to the LD-/RD-settings (in 2, 5) according to Table 1; +- The MG is enabled for 'TCP merge mode' due to the SDP "a=setup:" usage in LD-/RD-settings (in 2, 5) according to Table 2; +- After successful creation of second Termination (7), the SIP server/MGC modifies the SDP Offer (8) and forwards the SIP message (9); +- The returned SDP Answer (10) confirms the TCP setup method and provides the remote IP transport endpoint information; +- which is subsequently signalled to the MG (11) via MOD.req command. + +The MG is now successfully prepared for TCP merge mode and awaits incoming TCP SYN packets from the IP bearer path (see clause I.1.3). + +![Sequence diagram showing SIP and XOTCP signaling across multiple domains (X, A, Z, B, Y) involving UEs, NATs, MGs, and MGCs. The diagram illustrates the interaction for a 'TCP bearer path with SIP signalling path' use case.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +The diagram illustrates the signaling process for a "TCP bearer path with SIP signalling path" across five domains: Domain #X, Domain #A, Domain #Z, Domain #B, and Domain #Y. + +**Participants:** + +- Domain #X:** UE#A, NAT#X +- Domain #A:** MG#A, MGC#A +- Domain #Z:** (Empty) +- Domain #B:** MGC#B, MG#B +- Domain #Y:** NAT#Y, UE#B + +**IP Address and Port Information:** + +- UE#A: (A1:A1) +- NAT#X: (A1':A1') +- MG#A: (B1:B1)(B1':B1') +- MG#B: (B2':B2')(B2:B2) +- NAT#Y: A2':A2' +- UE#B: A2:A2 + +**Signaling Phases:** + +- SIP Signaling:** + - UE#A sends an **INVITE w SDP (A1:A1)** to MGC#A via NAT#X. NAT#X sets **a = setup: active**. + - MGC#A sends an **ADD w SDP (B1:B1)** to MGC#B. MGC#B sets **a = setup: active**. + - MGC#B sends an **ADD w SDP (B2':B2')** to NAT#Y. NAT#Y sets **a = setup: passive**. + - NAT#Y sends an **INVITE w SDP (B2:B2)** to UE#B. UE#B sets **a = setup: active**. + - UE#B sends a **200 OK w SDP (A2:A2)** back to NAT#Y. + - NAT#Y sends a **200 OK w SDP (B2:B2)** back to MGC#B. + - MGC#B sends a **200 OK w SDP (B1':B1')** back to MGC#A. + - MGC#A sends an **ACK** back to UE#A via NAT#X. +- TCP Connection Establishment:** + - UE#A sends a **17. TCP SYN** to NAT#X. + - NAT#X forwards it as **17. TCP SYN** to MG#A. + - MG#A forwards it as **18. TCP SYN** to MG#B. + - MG#B forwards it as **16. TCP SYN** to NAT#Y. + - NAT#Y forwards it as **16. TCP SYN** to UE#B. + - UE#B responds with **19. TCP SYN ACK** to NAT#Y. + - NAT#Y forwards it as **19. TCP SYN ACK** to MG#B. + - MG#B forwards it as **20. TCP SYN ACK** to MG#A. + - MG#A forwards it as **21. TCP SYN ACK** to NAT#X. + - NAT#X forwards it as **21. TCP SYN ACK** to UE#A. + - UE#A sends **23. TCP ACK** to NAT#X. + - NAT#X forwards it as **23. TCP ACK** to MG#A. + - MG#A forwards it as **24. TCP ACK** to MG#B. + - MG#B forwards it as **22. TCP ACK** to NAT#Y. + - NAT#Y forwards it as **22. TCP ACK** to UE#B. +- XoTCP Data Transfer:** + - UE#A sends **25. XoTCP send** to NAT#X. + - NAT#X forwards it as **25. XoTCP send** to MG#A. + - MG#A forwards it as **26. XoTCP send** to MG#B. + - MG#B forwards it as **27. XoTCP send** to NAT#Y. + - NAT#Y forwards it as **27. XoTCP send** to UE#B. + - UE#B receives it as **28. XoTCP receive**. + - UE#B sends **28. XoTCP receive** back to NAT#Y. + - NAT#Y forwards it as **28. XoTCP receive** to MG#B. + - MG#B forwards it as **29. XoTCP receive** to MG#A. + - MG#A forwards it as **30. XoTCP receive** to NAT#X. + - NAT#X forwards it as **30. XoTCP receive** to UE#A. +- Teardown:** + - A dashed line indicates **Data transfer finish**. + - A wide double-headed arrow indicates **Release SIP dialogue**. + - A wide double-headed arrow indicates **Tear down TCP connection**. + +**Notes:** + +- IP address and L4 port in IP bearer path +- TCP relay mode due to absence of SDP **a = setup:passive in LD** +- TCP merge mode due to presence of SDP **a = setup:passive in LD** +- For this phase MG#2 behaves as TCP server to both sides to provide the TCP merge function +- MG operate in TCP relay mode + +Legend: ---- SIP, — ITU-T H.248, — XoTCP + +H.248.84(12)\_FI.1 + +Sequence diagram showing SIP and XOTCP signaling across multiple domains (X, A, Z, B, Y) involving UEs, NATs, MGs, and MGCs. The diagram illustrates the interaction for a 'TCP bearer path with SIP signalling path' use case. + +Figure I.1 – Example signalling for use case "TCP bearer path with SIP signalling path" + +![Sequence diagram showing ITU-T H.248 signalling for TCP mode assignment in TCP merge mode. The diagram involves a SIP server (MGC), an MG (Media Gateway), and an external entity. The sequence includes SIP INVITE/ANSWER messages and ITU-T H.248 ADD/MOD requests and responses. Key steps include context creation (Cz) for incoming and outgoing terminations, and the final context configuration in TCP merge mode.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +**Sequence of messages:** + +- SIP INVITE (SDP offer)** with SDP media description [IP transport address = A, TCP setup = active] (External to MGC) +- ITU-T H.248 ADD.req** with Termination = \$, LD[ SDP[ IP transport address = \$, Transport = TCP, TCP setup = passive]], RD[ SDP[ IP transport address = A, Transport = TCP]] (MGC to MG) +- Create context $C_z$** with (incoming) termination $T_a$ and stream endpoint $S_i$ (MG internal) +- ITU-T H.248 ADD.rep** with Termination $T_a$ , LD[ SDP[ IP transport address = A']], RD[ SDP[ IP transport address = A]] (MG to MGC) +- ITU-T H.248 ADD.req** with Termination = \$, LD[ SDP[ IP transport address = \$, Transport = TCP, TCP setup = passive]] (MGC to MG) +- Context $C_z$ : add (outgoing) termination $T_b$ and stream endpoint $S_i$** (MG internal) +- ITU-T H.248 ADD.rep** with Termination $T_b$ , LD[ SDP[ IP transport address = B']] (MG to MGC) +- Modify SDP offer** (MGC internal) +- SIP INVITE (SDP offer)** with SDP media description [IP transport address = B', TCP setup = passive] (MGC to External) +- SIP ... (SDP answer)** with SDP media description [IP transport address = B, TCP setup = passive] (External to MGC) +- ITU-T H.248 MOD.req** for Termination = $T_b$ , RD[ SDP[ IP transport address = B, Transport = TCP]] (MGC to MG) +- Context $C_z$ : configuration for RD side of termination $T_b$ completed** (MG internal) +- ITU-T H.248 MOD.rep** with Termination $T_b$ , RD[ SDP[ IP transport address = B]] (MG to MGC) +- Context $C_z$ in TCP merge mode** (MG internal) +- SIP ... (SDP answer)** with SDP media description [IP transport address = B, TCP setup = passive] (MGC to External) + +**Comments:** +- The two ADD.req commands (1), (5) may be sent in a single or two ITU-T H.248 messages. + +H.248.84(12)\_FI.2 + +Sequence diagram showing ITU-T H.248 signalling for TCP mode assignment in TCP merge mode. The diagram involves a SIP server (MGC), an MG (Media Gateway), and an external entity. The sequence includes SIP INVITE/ANSWER messages and ITU-T H.248 ADD/MOD requests and responses. Key steps include context creation (Cz) for incoming and outgoing terminations, and the final context configuration in TCP merge mode. + +**Figure I.2 – ITU-T H.248 signalling for TCP mode assignment – Here: TCP merge mode** + +#### I.1.2.2 TCP relay mode + +This is the same as Figure I.2, but the LD-/RD-embedded SDP does not contain the "TCP setup = ..." information (i.e., not the SDP line "a=setup:passive" in protocol syntax) in signalling steps 2, 5, 9 and 10. + +### I.1.3 TCP bearer traffic during TCP connection establishment attempts + +The principle flow of TCP segments for a simultaneous TCP open procedure between A and B, and the TCP merge activity by the MG, is illustrated in Figure I.3. It could be observed that the MG is + +required for the detection of TCP SYN and ACK segments, the handling of sequence and acknowledgement numbers, the keeping of state information, handling of unsuccessful scenarios, etc. + +![Sequence diagram showing successful resolution of a simultaneous TCP open situation by an ITU-T H.248 MG in TCP merge mode. The diagram shows Peer A and Peer B both initiating SYN requests. The MG (Context Cz) intercepts these, stores sequence numbers in local variables, and then generates SYN/ACK responses to both sides to drive a normal 3-way handshake. Finally, it drops the resulting ACKs from the peers to establish an end-to-end connection.](339be989b91d5b1e73e5ecdc8401ca75_img.jpg) + +``` + +sequenceDiagram + participant A as Peer TCP A + participant Ta as Termination Ta + participant Tb as Termination Tb + participant B as Peer TCP B + + Note over Ta, Tb: ITU-T H.248 context Cz / TCP merge + B->>Tb: SYN(SN_Init = B1) + Note right of Tb: Store SN_Rx = B1 + Tb->>Ta: SYN(SN_Init = B1) + Note left of Ta: Store SN_Tx = B1 + Note over Ta: Wait on SYN from A-side + A->>Ta: SYN(SN_Init = A1) + Note left of Ta: Store SN_Rx = A1 + Ta->>Tb: SYN(SN_Init = A1) + Note right of Tb: Store SN_Tx = A1 + Note over Ta: Combine SYN segments + Ta->>A: SYN(SN_Init = B1), ACK(SN_Init = A1+1) + Note over Tb: Combine SYN segments + Tb->>B: SYN(SN_Init = A1), ACK(SN_Init = B1+1) + A->>Ta: ACK(SN_Init = B1+1) + Note over Ta: Drop received ACK + B->>Tb: ACK(SN_Init = A1+1) + Note over Tb: Drop received ACK + Note over A, B: End-to-end TCP connection established + +``` + +Initial connection establishment + +Termination "Ta" +Stream endpoint Si +    ITU-T H.248 context CZ     +Termination "Tb" +Stream endpoint Si +Both SEPs in steady state "TCP merge" + +MG strategy: "Drive both remote TCP entities for normal, 3-way handshake open". + +A Peer TCP endpoint or TCP relay node          B Peer TCP endpoint or TCP relay node + +$\Phi_{\text{SYN, Rx}}(\text{SN}_{\text{Rx}} = \text{unknown})$ + $\Phi_{\text{SYN, Tx}}(\text{SN}_{\text{Tx}} = \text{unknown})$ +         + $\Phi_{\text{SYN, Rx}}(\text{SN}_{\text{Rx}} = \text{unknown})$ + $\Phi_{\text{SYN, Tx}}(\text{SN}_{\text{Tx}} = \text{unknown})$ + +SYN( $\text{SN}_{\text{Init}} = \text{B1}$ ) + +$\Phi_{\text{SYN, Rx}}(\text{SN}_{\text{Rx}} = \text{SN}_{\text{Init}} = \text{B1})$ + $\Phi_{\text{SYN, Tx}}(\text{SN}_{\text{Tx}} = \text{unknown})$ + +SYN( $\text{SN}_{\text{Init}} = \text{B1}$ ) + +$\Phi_{\text{SYN, Rx}}(\text{SN}_{\text{Rx}} = \text{unknown})$ + $\Phi_{\text{SYN, Tx}}(\text{SN}_{\text{Tx}} = \text{SN}_{\text{Init}} = \text{B1})$ + +*Wait on SYN segment from A-side* + +SYN( $\text{SN}_{\text{Init}} = \text{A1}$ ) + +$\Phi_{\text{SYN, Rx}}(\text{SN}_{\text{Rx}} = \text{SN}_{\text{Init}} = \text{A1})$ + $\Phi_{\text{SYN, Tx}}(\text{SN}_{\text{Tx}} = \text{SN}_{\text{Init}} = \text{B1})$ + +SYN( $\text{SN}_{\text{Init}} = \text{A1}$ ) + +$\Phi_{\text{SYN, Rx}}(\text{SN}_{\text{Rx}} = \text{SN}_{\text{Init}} = \text{B1})$ + $\Phi_{\text{SYN, Tx}}(\text{SN}_{\text{Tx}} = \text{SN}_{\text{Init}} = \text{A1})$ + +*Combine SYN segments from both sides in SYN/ACK reply towards A* + +SYN( $\text{SN}_{\text{Init}} = \text{B1}$ ), ACK( $\text{SN}_{\text{Init}} = \text{A1}+1$ ) + +*Combine SYN segments from both sides in SYN/ACK reply towards B* + +SYN( $\text{SN}_{\text{Init}} = \text{A1}$ ), ACK( $\text{SN}_{\text{Init}} = \text{B1}+1$ ) + +*Incoming TCP segment drives "normal TCP open" (3-way handshake) at A-side* + +*Incoming TCP segment drives "normal TCP open" (3-way handshake) at B-side* + +ACK( $\text{SN}_{\text{Init}} = \text{B1}+1$ ) + +ACK( $\text{SN}_{\text{Init}} = \text{A1}+1$ ) + +*Drop received ACK segment*          *Drop received ACK segment* + +End-to-end TCP connection established + +H.248.84(12)\_Fl.3 + +$\text{SN}_{\text{Init}}$ Initial sequence number + $\text{SN}_{\text{Rx}}$ SN in incoming direction + $\text{SN}_{\text{Tx}}$ SN in outgoing direction + $\Phi_{\text{SYN, Rx}}$ Local variable for storing SYNchronize sequence numbers in incoming direction + $\Phi_{\text{SYN, Tx}}$ Ditto in outgoing direction + +Sequence diagram showing successful resolution of a simultaneous TCP open situation by an ITU-T H.248 MG in TCP merge mode. The diagram shows Peer A and Peer B both initiating SYN requests. The MG (Context Cz) intercepts these, stores sequence numbers in local variables, and then generates SYN/ACK responses to both sides to drive a normal 3-way handshake. Finally, it drops the resulting ACKs from the peers to establish an end-to-end connection. + +**Figure I.3 – Successful resolution of a simultaneous TCP open situation by an ITU-T H.248 MG in TCP merge mode (MG strategy: "Drive both remote TCP entities for normal, 3-way handshake open")** + +Some notes to the signalling flow (Figure I.3): + +- The starting point is a successfully prepared MG for TCP merge mode as described in clause I.1.2.1); +- The required MG capabilities according to clause 13.7.3.1 lead e.g., to the creation of SEP-specific variables $\Phi$ for tracking the numbers of SN and AN in incoming and outgoing direction, here: + - SEP Ta/Si: variables $\Phi_{\text{SYN,Rx}}$ and $\Phi_{\text{SYN,Tx}}$ and + - SEP Tb/Si: variables $\Phi_{\text{SYN,Rx}}$ and $\Phi_{\text{SYN,Tx}}$ and + - all variable values are initially set to unknown. +- The TCP simultaneous open starts (from MG perspective) with an incoming TCP SYN segment (from B side) with an initial SN value equal to B1; +- The TCP SYN segment is internally forwarded to SEP Ta/Si and the correspondent variables are updated (i.e., Ta/Si: $\Phi_{\text{SYN,Tx}} = B1$ and Tb/Si: $\Phi_{\text{SYN,Rx}} = B1$ ); +- This TCP SYN segment is then not forwarded, the MG rather waits on an incoming TCP SYN segment from A side; +- The associated TCP SYN segment from A side with an initial SN value equal to A1 is then received by SEP Ta/Si; +- which is then also internally forwarded to SEP Tb/Si and leads to updated variables (i.e., Ta/Si: $\Phi_{\text{SYN,Rx}} = A1$ and Tb/Si: $\Phi_{\text{SYN,Tx}} = A1$ ); and +- combined TCP SYN/ACK segments are sent to both remote TCP entities A and B. + +Such an MG approach looks like a regular TCP connection establishment procedure from A and B side. Both TCP entities A and B act in the role of a "TCP client", and the MG provides the correspondent "TCP server" role. + +Figure I.4 provides a slightly modified behaviour by the MG, but effectively leading to the same result. + +![Sequence diagram showing the resolution of a simultaneous TCP open situation between two endpoints, A and B, through an ITU-T H.248 context. The diagram shows the exchange of SYN and ACK segments, with local variables ΦSYN,Rx and ΦSYN,Tx tracking sequence numbers. Annotations explain the 'normal TCP open' at A-side and 'TCP simultaneous open' at B-side, leading to a successful connection establishment.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +Initial connection establishment + +Termination "Ta" Stream endpoint Sa + +ITU-T H.248 context CZ + +Both SEPs in steady state "TCP merge" + +Termination "Tb" Stream endpoint Sb + +MG strategy: "Drive one remote TCP entity for simultaneous open". + +A Peer TCP endpoint or TCP relay node + +B Peer TCP endpoint or TCP relay node + +$\Phi_{SYN, Rx}(SN_{Rx} = \text{unknown})$ + $\Phi_{SYN, Tx}(SN_{Tx} = \text{unknown})$ + +$\Phi_{SYN, Rx}(SN_{Rx} = \text{unknown})$ + $\Phi_{SYN, Tx}(SN_{Tx} = \text{unknown})$ + +SYN( $SN_{Init} = B1$ ) + +$\Phi_{SYN, Rx}(SN_{Rx} = SN_{Init} = B1)$ + $\Phi_{SYN, Tx}(SN_{Tx} = \text{unknown})$ + +SYN( $SN_{Init} = B1$ ) + +$\Phi_{SYN, Rx}(SN_{Rx} = \text{unknown})$ + $\Phi_{SYN, Tx}(SN_{Tx} = SN_{Init} = B1)$ + +*Drop internally received SYN segment* + +SYN( $SN_{Init} = A1$ ) + +$\Phi_{SYN, Rx}(SN_{Rx} = SN_{Init} = A1)$ + $\Phi_{SYN, Tx}(SN_{Tx} = SN_{Init} = A1)$ + +SYN( $SN_{Init} = A1$ ) + +Incoming TCP segment drives "TCP simultaneous open" at B-side + +$\Phi_{SYN, Rx}(SN_{Rx} = SN_{Init} = B1)$ + $\Phi_{SYN, Tx}(SN_{Tx} = SN_{Init} = A1)$ + +SYN( $SN_{Init} = A1$ ) + +SYN( $SN_{Init} = B1$ ), ACK( $SN_{Init} = A1+1$ ) + +Incoming TCP segment drives "normal TCP open" (3-way handshake) at A-side + +SYN( $SN_{Init} = B1$ ), ACK( $SN_{Init} = A1+1$ ) + +ACK( $SN_{Init} = B1+1$ ) + +ACK( $SN_{Init} = B1+1$ ) + +ACK( $SN_{Init} = B1+1$ ) + +End-to-end TCP connection established + +Sequence diagram showing the resolution of a simultaneous TCP open situation between two endpoints, A and B, through an ITU-T H.248 context. The diagram shows the exchange of SYN and ACK segments, with local variables ΦSYN,Rx and ΦSYN,Tx tracking sequence numbers. Annotations explain the 'normal TCP open' at A-side and 'TCP simultaneous open' at B-side, leading to a successful connection establishment. + +H.248.84(12)\_FI.4 + +$SN_{Init}$ Initial sequence number + $SN_{Rx}$ SN in incoming direction + $SN_{Tx}$ SN in outgoing direction + $\Phi_{SYN, Rx}$ Local variable for storing SYNchronize sequence numbers in incoming direction + $\Phi_{SYN, Tx}$ Ditto in outgoing direction + +**Figure I.4 – Successful resolution of a simultaneous TCP open situation by an ITU-T H.248 MG in TCP merge mode (MG strategy: "Drive one remote TCP entity for simultaneous open")** + +The major difference is related to the fact that the MG drops the first incoming TCP SYN segment (after updating the local variables). This is the TCP SYN segment from the B side in Figure I.4. Side B then provides TCP simultaneous open behaviour due to the missing ACK in the incoming SYN segment. However, there is finally again just a single end-to-end TCP connection, thus effectively the same result as in Figure I.3, even with respect to the values of the SN and AN elements. + +There may be further MG strategies concerning implementation of TCP merge mode. This topic is out of scope of this Recommendation. + +# Appendix II + +## TCP Functions versus ITU-T H.248 TCP modes of operation + +(This appendix does not form an integral part of this Recommendation.) + +## II.1 Purpose and scope + +This appendix attempts to structure functions related to TCP protocol processing from the perspective of ITU-T H.248 media gateways. Such functions are relevant to ITU-T H.248 MG modes of operation for TCP traffic, as subject of this Recommendation. + +Three major TCP modes are identified. There may be further TCP modes in the future, primarily due to the ongoing active work by the IETF concerning the specification of TCP extensions. + +The information of this appendix may provide some useful guidelines for implementers; however, it is not binding because the majority of TCP functions are implementation specific. + +The primary purpose of this appendix is to indicate the common and especially the different characteristics between the ITU-T H.248 TCP modes of operation in an MG. The list of TCP functions focuses on the major TCP capabilities, but this list is not exhaustive (see also [b-IETF RFC 4614]). + +## II.2 Overview + +The following list provides an overview of TCP areas and functions discussed in this Appendix: + +- Table II.1 – TCP functions versus ITU-T H.248 TCP modes of operation – Basic capabilities +- Table II.2 – TCP functions versus ITU-T H.248 TCP modes of operation – Orthogonal functions "Topology hiding" +- Table II.3 – TCP functions versus ITU-T H.248 TCP modes of operation – Orthogonal functions "Protocol encryption" +- Table II.4 – TCP functions versus ITU-T H.248 TCP modes of operation – Orthogonal functions "Security" +- Table II.5 – TCP functions versus ITU-T H.248 TCP modes of operation – Orthogonal functions "Application data inactivity detection" +- Table II.6 – TCP functions versus ITU-T H.248 TCP modes of operation – Orthogonal functions "Interactions with other policy rules" +- Table II.7 – TCP functions versus ITU-T H.248 TCP modes of operation – Orthogonal functions "Performance measurements & statistics" +- Table II.8 – TCP functions versus ITU-T H.248 TCP modes of operation – Orthogonal functions "Connection keep alive support" +- Table II.9 – TCP functions versus ITU-T H.248 TCP modes of operation – Orthogonal functions "Add-on's to TCP" +- Table II.10 – TCP functions versus ITU-T H.248 TCP modes of operation – Orthogonal functions "IP layer operations" + +## II.3 Tables of TCP functions versus ITU-T H.248 TCP modes of operation + +**Table II.1 – TCP functions versus ITU-T H.248 TCP modes of operation +– Basic capabilities** + +| No. | TCP Function | Mode "TCP Relay" | Mode "TCP Proxy" | Mode "TCP Merge" | Comments | +|------------------------------------|------------------------------------------------------------------------|------------------|------------------|------------------|--------------------------------------------| +| 1.1 | Validate IP header "protocol number" = 'TCP' | Yes | Yes | Yes | Value 6 = 'TCP' | +| TCP protocol – Header processing: | | | | | | +| 1.2 | Sequence number handling | No | Yes | Yes | | +| 1.3 | Acknowledgement number handling | No | Yes | Yes | | +| 1.4 | Segmentation | No | No | No | Note 3 | +| 1.5 | If yes: Segmentation timer | No | No | No | | +| 1.6 | Reassembly (incl. reordering) | No | Yes | No (Note 6) | | +| 1.7 | Window size control | No | Yes | Yes | | +| 1.8 | Flow control | No | Yes | Yes | | +| 1.9 | Checksum update | Yes (Note 4) | Yes | Yes | | +| 1.10 | Flag 'URG' | No | Yes | No | | +| 1.11 | Flag 'ACK' | No | Yes | Yes | | +| 1.12 | Flag 'PSH' | No | Yes | No | | +| 1.13 | Flag 'RST' | No | Yes | Yes | | +| 1.14 | Flag 'SYN' | No | Yes | Yes | | +| 1.15 | Flag 'FIN' | No | Yes | Yes | | +| 1.16 | others? | | | | | +| TCP protocol – Connection control: | | | | | | +| 1.17 | TCP connection state machine for "full endpoint" (Note 1) | No | Yes | No | Just a subset state machine in merge mode. | +| 1.18 | TCP connection state machine for "lightweight endpoint" (Note 2) | No | No | Yes | | +| 1.19 | TCP connection establishment protocol ("Three-way handshake protocol") | No | Yes | Yes | | +| 1.20 | TCP connection termination protocol | No | Yes | Yes | | +| 1.21 | Timer for connection establishment/release | No | Yes | Yes | | +| 1.22 | Packet Buffer (for retransmissions) | No | Yes | Yes | | +| 1.23 | Support of "active" connection establishment | No | Yes | Yes | | +| 1.24 | Support of "passive" connection establishment | No | Yes | Yes | | +| 1.25 | Support of "TCP half-close" | No | Yes (Note 5) | Yes (Note 5) | | +| 1.26 | Support of "TCP Simultaneous Open" | No | No | Yes | | +| 1.27 | Support of "TCP Simultaneous Close" | No | No | Yes | | + +**Table II.1 – TCP functions versus ITU-T H.248 TCP modes of operation +– Basic capabilities** + +| No. | TCP Function | Mode
"TCP Relay" | Mode
"TCP Proxy" | Mode
"TCP Merge" | Comments | +|-------------------------|-----------------------------------------------------------------------------------------------|---------------------|---------------------|---------------------|----------| +| 1.28 | others? | | | | | +| TCP protocol – options: | | | | | | +| 1.29 | Support of TCP protocol options? | No | No | No | | +| TCP packet handling: | | | | | | +| 1.30 | Transparent packet forwarding:
No TCP payload modification;
No TCP header modification | Yes | No | No | Note 4 | +| 1.31 | Transparent packet forwarding:
No TCP payload modification;
but TCP header modification | No | Yes | Yes | Note 4 | + +NOTE 1 – TCP connection states (see e.g., [b-IETF RFC 4022]): closed(1), listen(2), synSent(3), synReceived(4), established(5), finWait1(6), finWait2(7), closeWait(8), lastAck(9), closing(10), timeWait(11), deleteTCB(12). +NOTE 2 – Subset of states with regards to connection establishment: closed(1), listen(2), synSent(3), synReceived(4), established(5). +NOTE 3 – It is supposed that the received TCP traffic by the MG is already "segmented" and that the supported MG-local L2 interfaces do not require a further segmentation. +NOTE 4 – Dependent on local NA(P)T mode (see Table II). +NOTE 5 – The ITU-T H.248 packet bearer is "bidirectional" in general. Thus, any explicit support of unidirectional only ("for TCP half-plex communication") appears not mandatory. Every TCP termination procedure of a TCP connection consists of two TCP half-close procedures. +NOTE 6 – It is sufficient to process only individual incoming TCP segments for a minimum TCP merge mode. + +**Table II.2 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "Topology hiding"** + +| No. | TCP Function | Mode
"TCP Relay" | Mode
"TCP Proxy" | Mode
"TCP Merge" | Comments | +|-----|----------------------------------------------------------|---------------------|---------------------|---------------------|----------| +| 2.1 | NAT (IP address translation) – NAT-full vs NAT-less? | Yes and No | Yes (Note) | Yes (Note) | | +| 2.2 | PT (TCP port translation) – PT-full vs PT-less? | Yes and No | Yes (Note) | Yes (Note) | | +| 2.3 | NAT64 for TCP/IPv4 to TCP/IPv6 transitioning | Yes | Yes (Note) | Yes (Note) | | +| 2.4 | ITU-T H.248.78 policy rule for "TCP payload ALG support" | add-on | add-on | add-on | | + +NOTE – Inherent due to TCP endpoint function ("each ITU-T H.248 'TCP' Stream endpoint represents a self-contained TCP 'socket'"). + +**Table II.3 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "Protocol encryption"** + +| No. | TCP Function | Mode
"TCP Relay" | Mode
"TCP Proxy" | Mode
"TCP Merge" | Comments | +|-----|-----------------------------------------|----------------------------|---------------------|---------------------|-------------------------------| +| 3.1 | L3 encryption: IPsec? | add-on | add-on | add-on | | +| 3.2 | L4 encryption: TLS?
"Non-TLS-to-TLS" | No | Yes | Yes | | +| 3.3 | L4 encryption: TLS?
"TLS-to-TLS" | Yes ("TLS is transparent") | Yes | Yes | | +| 3.4 | Application data encryption? | Yes
("transparent") | Yes | Yes | Encryption limited on L4+-SDU | + +**Table II.4 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "Security"** + +| No. | TCP Function | Mode
"TCP Relay" | Mode
"TCP Proxy" | Mode
"TCP Merge" | Comments | +|------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|---------------------|---------------------|---------------------|----------| +| 4.1 | TCP security policy rule(s) for "Stateless, TCP port only based filters" | Yes | Yes | Yes | | +| 4.2 | TCP security policy rule(s) for "Stateless, TCP flag (bits) specific filters" | No | Yes | Yes | | +| 4.3 | TCP security policy rule(s) for "Stateless, TCP header or/and payload size specific filters" | Yes | Yes | Yes | | +| 4.4 | TCP security policy rule(s) for "Stateful, TCP sequence/acknowledgement number specific filters" | No | Yes | Yes | | +| 4.5 | TCP security policy rule(s) for "Stateful, TCP flag (bits) specific filters" | No | Yes | Yes | | +| NOTE – The high-level TCP filter categories are based on [b-ITU-T H.248.79]. | | | | | | + +**Table II.5 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "Application data inactivity detection"** + +| No. | TCP Function | Mode "TCP Relay" | Mode "TCP Proxy" | Mode "TCP Merge" | Comments | +|-----|-----------------------------------------------------------------------|------------------|------------------|------------------|----------| +| 5.1 | Detection of TCP inactivity ("application-agnostic") | Yes | Yes | Yes | Note 1 | +| 5.2 | Detection of TCP Application Data inactivity ("application-specific") | No | Yes | Yes | Note 2 | +| 5.3 | ITU-T H.248.40 policy rule for generic IP/L4 packet detection | Yes | Yes | Yes | Note 3 | + +NOTE 1 – Assumption that detection logic contains also a condition based on (I.1). + +NOTE 2 – Assumption that detection logic contains also a condition related to the TCP transport application protocol. The 'tbd' indicates that possibly a "deep packet inspection" is required (= "deep TCP payload inspection"). + +NOTE 3 – [ITU-T H.248.40] defines a transport protocol agnostic, generic IP/L4 endpoint based detection logic. + +**Table II.6 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "Interactions with other policy rules"** + +| No. | TCP Function | Mode "TCP Relay" | Mode "TCP Proxy" | Mode "TCP Merge" | Comments | +|-----|---------------------------------------------------------|------------------|------------------|------------------|-----------------------------| +| 6.1 | ITU-T H.248.43 policy rule for IP filtering | Yes | Yes | Yes | See also [b-ITU-T H.248.43] | +| 6.2 | ITU-T H.248.53 policy rule for IP byterate policing | Yes | Yes | Yes | See also [b-ITU-T H.248.53] | +| 6.3 | ITU-T H.248.76 policy rule for filter groups in general | Yes | Yes | Yes | See also [b-ITU-T H.248.76] | + +Table II.7 provides a list of some TCP performance parameters and their possible support by ITU-T H.248 Statistics. + +**Table II.7 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "Performance measurements & statistics"** + +| No. | TCP performance metric | Mode "TCP Relay" | Mode "TCP Proxy" | Mode "TCP Merge" | Comments | +|-----|----------------------------------|------------------|------------------|------------------|---------------------------------------------| +| 7.1 | Statistic "TCP bytes sent" | Yes | Yes | Yes | See statistic "tcptv/tcpos" (clause 10.4.1) | +| 7.2 | Statistic "TCP bytes received" | Yes | Yes | Yes | See statistic "tcptv/tcpor" (clause 10.4.2) | +| 7.3 | Statistic "TCP packets sent" | Yes | Yes | Yes | See statistic "tcptv/tcpss" (clause 10.4.3) | +| 7.4 | Statistic "TCP packets received" | Yes | Yes | Yes | See statistic "tcptv/tcprr" (clause 10.4.4) | + +**Table II.7 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "Performance measurements & statistics"** + +| No. | TCP performance metric | Mode
"TCP Relay" | Mode
"TCP Proxy" | Mode
"TCP Merge" | Comments | +|------|----------------------------------------------------------------|---------------------|---------------------|---------------------|----------------------------------------------------------------| +| 7.5 | Statistic "TCP round-trip time" (RTT) | No | Yes | Yes | See statistic
"tcpqcm/tcprrttest"
(clause 12.4.1) | +| 7.6 | Statistic "TCP connection establishment delay" | No | Yes | Yes | See statistic
"tcpccm/tcppest"
(clause 11.4.1)
Note 2 | +| 7.7 | Statistic "TCP connection establishment reattempts" | No | Yes | Yes | Not yet supported. | +| 7.8 | Statistic "TCP packet retransmissions" | No | Yes | Yes | Not yet supported. | +| 7.9 | Statistic "Received TCP connection establishment attempts" | No | Yes | Yes | See statistic
"tcpccm/tcpsynrx"
(clause 11.4.3) | +| 7.10 | Statistic "Sent TCP connection establishment attempts" | No | Yes | Yes | See statistic
"tcpccm/tcpsyntx"
(clause 11.4.2) | +| 7.11 | Statistic " Number of received TCP segments with set RST flag" | No | Yes | Yes | See statistic
"tcpiph/rstrx"
(clause 9.4.1) | +| 7.12 | Statistic " Number of received TCP segments with set SYN flag" | No | Yes | Yes | See statistic
"tcpiph/synrx"
(clause 9.4.2) | +| 7.13 | ITU-T Y.1560 related TCP performance metrics | Yes | Yes | Yes | Note 1 | + +NOTE 1 – [b-ITU-T Y.1560] indicates multiple use cases, which may lead to MG involvement in all three TCP modes. +NOTE 2 – There is a difference between the TCP endpoint specific "TCP connection establishment delay" and this ITU-T H.248 Statistic, see also clause V.1 + +**Table II.8 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "Connection keep alive support"** + +| No. | TCP Function | Mode
"TCP Relay" | Mode
"TCP Proxy" | Mode
"TCP Merge" | Comments | +|-----|---------------------------------------|---------------------|---------------------|---------------------|-----------------------------------------------| +| 8.1 | TCP endpoint initiated TCP keep alive | No | Yes | No | TCP keep alive
is beyond
[IETF RFC 793] | + +**Table II.9 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "Add-on's to TCP"** + +| No. | TCP Function | Mode
"TCP Relay" | Mode
"TCP Proxy" | Mode
"TCP Merge" | Comments | +|-----|--------------------------------|---------------------|---------------------|---------------------|-------------------------------------| +| 9.1 | Path MTU discovery | No | Optional | Optional | If [b-IETF RFC 1191] supported. | +| 9.2 | TCP "Long Fat Pipe" support | No | No (Note) | No (Note) | [b-IETF RFC 1323] | +| 9.3 | TCP "Window Scale" option | No | No | No | 32-bit (instead 16-bit) window size | +| 9.4 | TCP "Timestamp" option | No | No | No | [b-IETF RFC 1323] | +| 9.5 | TCP "PAWS" option 2 | No | No | No | [b-IETF RFC 1323] | +| 9.6 | Others | | | | | + +NOTE – It is supposed that the ITU-T H.248 TCP bearer connections will be used with limited transport capacity (rather than with "infinite bandwidth"). + +**Table II.10 – TCP functions versus ITU-T H.248 TCP modes of operation +– Orthogonal functions "IP layer operations"** + +| No. | TCP Function | Mode
"TCP Relay" | Mode
"TCP Proxy" | Mode
"TCP Merge" | Comments | +|------|--------------------------|---------------------|---------------------|---------------------|----------| +| 10.1 | MG-local ICMP processing | No | Yes | Yes | | + +## II.4 Relation between TCP proxy and TCP merge mode + +It looks like that both modes have significant overlap when comparing the columns in clause II.3. However, both modes still differ significantly, primarily in terms of: + +- example network application: + - TCP proxy mode: e.g., ITU-T H.248 MG as ITU-T Y.1560 middle box (for cases of full TCP termination); + - TCP merge mode: e.g., ITU-T H.248 MG providing support according to this Recommendation; +- end-to-end transport **connection principle**: + - TCP proxy mode: separate TCP connection segments; + - TCP merge mode: single, end-to-end TCP connection; +- involvement with regard to the **lifetime of a TCP connection**: + - TCP proxy mode: entire lifetime, i.e., inclusive data transfer phase; + - TCP merge mode: primarily just during the short establishment phase and possible later modification phases, i.e., the TCP merge mode would be active during "hole punching" phase(s) only; + +2 Protection Against Wrapped Sequence Numbers. + +- TCP **state** machine: + - TCP proxy mode: full TCP state machine; + - TCP merge mode: lightweight TCP state machine, just a sub-set of states; +- amount of **resources** required for implementations: + - TCP proxy mode: resources for realizing full TCP endpoints, inclusive memory for storing and repeating not yet acknowledged TCP segments; + - TCP merge mode: much less than TCP proxy, particularly due to involvement just during connection establishment phase. + +# Appendix III + +## TCP mode control – SDP "a=setup" clarification due to b-IETF RFC 6135 + +(This appendix does not form an integral part of this Recommendation.) + +The NAT traversal method in the example use case of TCP bearer connections and SIP signalling at MGC level is based on SDP usage across the ITU-T H.248 interface by [IETF RFC 4145] defined SDP attributes (see clause 13). The two SDP attributes introduced by [IETF RFC 4145] are referred to by [b-IETF RFC 6135], which raises the question whether this Recommendation should mention [b-IETF RFC 6135] as well. [b-IETF RFC 6135] is specifically for use with the IP application protocol MSRP [IETF RFC 4975], whereas [IETF RFC 4145] is generic ("application agnostic"). + +Figure III.1 outlines the principal relation between the main IETF RFCs in this context. + +[b-IETF RFC 6135] does not define any syntactical extensions with respect to [IETF RFC 4145], and is rather profiling the SDP attribute usage by specifying the subset of allowed values. Further: [b-IETF RFC 6135] is considered for SIP-level SDP Offer/Answer signalling. + +It may be concluded that [b-IETF RFC 6135] does not impact the ITU-T H.248 TCP hole punching package. There are neither new SDP values nor any restriction of the used SDP values for TCP mode control of the ITU-T H.248 MG. [b-IETF RFC 6135] is therefore rather transparent for the ITU-T H.248 MG, similar to [IETF RFC 4145] SDP usage at SIP level. + +![Diagram showing the relationship between major IETF RFCs related to TCP transport control. The diagram is divided into two horizontal sections: 'Application protocol' and 'Transport protocol'. In the 'Application protocol' section, RFC 4975 (09/2007) Message Session Relay Protocol (MSRP) and RFC 6135 (02/2011) An Alternative Connection Model for the Message Session Relay Protocol are shown. An arrow labeled '„alternative“' points from RFC 6135 to RFC 4975. In the 'Transport protocol' section, RFC 4145 (09/2005) TCP-Based Media Transport in the Session Description Protocol (SDP) and RFC 4572 (06/2006) Connection-Oriented Media Transport over the TLS Protocol in the SDP are shown. An arrow labeled 'extension for L4 security' points from RFC 4145 to RFC 4572. Dashed arrows labeled 'Profiling' point from RFC 6135 to both RFC 4145 and RFC 4572. A solid arrow labeled 'used for MSRP-over-TCP transport' points from RFC 4975 to RFC 4145. A note next to RFC 6135 states '= Profile for SDP attribute usage for „a=setup:](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +*Application-independent RFCs for TCP transport (RFCs 4145, 4572), +and application-specific RFCs for MSRP with reference to TCP transport (RFCs 4975, 6135)* + +**RFC 4975 (09/2007)** +Message Session Relay Protocol (MSRP) + +**RFC 6135 (02/2011)** +An Alternative Connection Model for the Message Session Relay Protocol + +„alternative“ + +used for MSRP-over-TCP transport + +Profiling + += Profile for SDP attribute usage for „a=setup:" and „a=connection:" + +**Application protocol** + +--- + +**Transport protocol** + +**RFC 4145 (09/2005)** +TCP-Based Media Transport in the Session Description Protocol (SDP) + +**RFC 4572 (06/2006)** +Connection-Oriented Media Transport over the TLS Protocol in the SDP + +extension for L4 security + +„connection-oriented media (COMEDIA) mechanism“ + +- a=setup: +- a=connection: + +additional SDP attribute: + +- a=fingerprint: + +Diagram showing the relationship between major IETF RFCs related to TCP transport control. The diagram is divided into two horizontal sections: 'Application protocol' and 'Transport protocol'. In the 'Application protocol' section, RFC 4975 (09/2007) Message Session Relay Protocol (MSRP) and RFC 6135 (02/2011) An Alternative Connection Model for the Message Session Relay Protocol are shown. An arrow labeled '„alternative“' points from RFC 6135 to RFC 4975. In the 'Transport protocol' section, RFC 4145 (09/2005) TCP-Based Media Transport in the Session Description Protocol (SDP) and RFC 4572 (06/2006) Connection-Oriented Media Transport over the TLS Protocol in the SDP are shown. An arrow labeled 'extension for L4 security' points from RFC 4145 to RFC 4572. Dashed arrows labeled 'Profiling' point from RFC 6135 to both RFC 4145 and RFC 4572. A solid arrow labeled 'used for MSRP-over-TCP transport' points from RFC 4975 to RFC 4145. A note next to RFC 6135 states '= Profile for SDP attribute usage for „a=setup: + +Figure III.1 – Relationship between major IETF RFCs related to TCP transport control + +# Appendix IV + +## Generic NAT traversal models + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides background information for potential use cases with the *nattp2p* package defined in clause 8. + +Following additional terms are introduced by this appendix: + +- **NAT device type 'BEHAVE-compliant'**: a network address translator with functional behaviour according to the technologies defined by the IETF BEHAVE working group ("*Behavior Engineering for Hindrance Avoidance*"). Such NAT behaviour is characterized by protocol specific support at IP and transport layer and the consideration of general behavioural requirements for enhanced NAT traversal services. +- **NAT device type 'legacy'**: a network address translator *without* support or consideration of technologies and/or behavioural specifications as defined by the IETF BEHAVE working group. + +## IV.1 ITU-T H.248 gateways in SIP environments and remote NAT devices + +The generic NAT-T model can be characterized by aspects such as + +- L4 independence (i.e., NAT-T means independent of specific transport protocols) or +- Unawareness of remote NAT device behaviour. + +Figure IV.1 illustrates the generic model for a SIP environment, which implies a SIP-controlled IP terminal and an MGC tightly coupled to a SIP server. + +![Diagram of the generic NAT traversal model from an ITU-T H.248 perspective in SIP environments. It shows a Peer_x (IP Host with SIP user agent and L4/IP endpoint) connected to a NAT_x (NAT device). The NAT_x is connected to a cloud representing the network, which has SIP and L4/IP bearer paths. The network is connected to a SIP server (containing an MGC) and an ITU-T H.248 border router/gateway (containing a NAT-T mode). The border router/gateway is connected to an MG (Media Gateway) via an ITU-T H.248 path. The MG is connected to an L4/IP bearer. A dashed box labeled 'Two principal NAT types:' points to the NAT_x and lists: a) Remote NAT devices, not compliant with RFC 5382 (so called 'legacy NAT') and b) Remote NAT devices compliant with RFC 5382 (so called 'BEHAVE-compliant NAT'). The diagram is labeled H.248.84(84)_FIV.1. A legend at the bottom defines NAT as Network address (and port) translator and SIP as Session initiation protocol.](1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg) + +Generic NAT traversal model from ITU-T H.248 perspective (SIP environments) + +Two principal NAT types: + +- a) Remote NAT devices, not compliant with RFC 5382 (so called "legacy NAT") +- b) Remote NAT devices compliant with RFC 5382 (so called "BEHAVE-compliant NAT") + +IP Host + +- SIP user agent +- L4/IP endpoint + +Peerx + +NAT + +NATx + +SIP + +L4/IP bearer + +SIP server + +MGC + +ITU-T H.248 + +ITU-T H.248 border router/gateway + +NAT-T mode + +L4/IP bearer + +MG + +H.248.84(84)\_FIV.1 + +NAT Network address (and port) translator + +SIP Session initiation protocol + +Diagram of the generic NAT traversal model from an ITU-T H.248 perspective in SIP environments. It shows a Peer\_x (IP Host with SIP user agent and L4/IP endpoint) connected to a NAT\_x (NAT device). The NAT\_x is connected to a cloud representing the network, which has SIP and L4/IP bearer paths. The network is connected to a SIP server (containing an MGC) and an ITU-T H.248 border router/gateway (containing a NAT-T mode). The border router/gateway is connected to an MG (Media Gateway) via an ITU-T H.248 path. The MG is connected to an L4/IP bearer. A dashed box labeled 'Two principal NAT types:' points to the NAT\_x and lists: a) Remote NAT devices, not compliant with RFC 5382 (so called 'legacy NAT') and b) Remote NAT devices compliant with RFC 5382 (so called 'BEHAVE-compliant NAT'). The diagram is labeled H.248.84(84)\_FIV.1. A legend at the bottom defines NAT as Network address (and port) translator and SIP as Session initiation protocol. + +**Figure IV.1 – Generic NAT traversal model from an ITU-T H.248 perspective (SIP environments)** + +The principal NAT device behaviour is described in the next clause. + +## IV.2 Basic types of remote NAT devices + +There was an attempt by the IETF3 in recent years to specify requirements for functional behaviour of NAT devices, in order to reduce the unpredictability of NAT device behaviour, support of NAT traversal and other goals. Hence a differentiation between *legacy NATs* and so-called *BEHAVE-compliant NATs* is possible (see Figure IV.2 and formal definitions in clauses 3.2.1 and 3.2.2). + +Generic NAT-traversal model from ITU-T H.248 MG perspective with regards to transport layer protocol aspects and distinction of BEHAVE-compliant versus legacy NATs + +![Figure IV.2: Generic NAT-Traversal model from ITU-T H.248 MG perspective. The diagram shows an IP host (Peer) connected to a Remote NAT device (Type 'legacy NAT' or Type 'BEHAVE-compliant NAT') via an IP bearer path. The Remote NAT device is connected to an ITU-T H.248 border router/gateway (MG) via an IP bearer path. The MG contains 'Additional NAT-traversal support for peer-to-peer' and 'Basic NAT-traversal tools [ITU-T H.248.37] and [ITU-T H.248.50]'. The diagram also includes a list of NAT behavioral requirements and feedback from the remote NAT device to the MG.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +The diagram illustrates the generic NAT-traversal model from the ITU-T H.248 MG perspective. On the left, an **IP host** (labeled as **Peer**) contains a **Bearer endpoint**. An **IP bearer path** connects this endpoint to a **Remote NAT device**. The Remote NAT device is shown as a green box labeled **Type "BEHAVE-compliant NAT"**, which is nested within a larger orange box labeled **Type "legacy NAT"**. A dashed line representing the **IP bearer path** continues from the Remote NAT device through a cloud to an **ITU-T H.248 border router/gateway** (labeled as **MG**). The MG contains two functional blocks: **Additional NAT-traversal support for peer-to-peer** and **Basic NAT-traversal tools [ITU-T H.248.37] and [ITU-T H.248.50]**. An **IP bearer path** exits the MG to the right. Below the Remote NAT device, a dashed box lists **NAT behavioral requirements** for various protocols including ICMP, TCP, UDP, DCCP, SCTP, and L4+ protocols, referencing RFCs and application design guidelines. To the right of the MG, a dashed box lists **"Feedback from remote NAT device to MG:"**, categorized into **L4-specific feedback** (e.g., [IETF RFC 5382]) and **L4-independent feedback** (e.g., [b-IETF RFC 5508]). The diagram is identified by the code H.248.84(12)\_FIV.2. + +Figure IV.2: Generic NAT-Traversal model from ITU-T H.248 MG perspective. The diagram shows an IP host (Peer) connected to a Remote NAT device (Type 'legacy NAT' or Type 'BEHAVE-compliant NAT') via an IP bearer path. The Remote NAT device is connected to an ITU-T H.248 border router/gateway (MG) via an IP bearer path. The MG contains 'Additional NAT-traversal support for peer-to-peer' and 'Basic NAT-traversal tools [ITU-T H.248.37] and [ITU-T H.248.50]'. The diagram also includes a list of NAT behavioral requirements and feedback from the remote NAT device to the MG. + +Figure IV.2 – Generic NAT-Traversal model from ITU-T H.248 MG perspective with regards to transport layer protocol aspects and distinction of BEHAVE-compliant versus legacy NATs + +From ITU-T H.248 gateway perspective, the following can be concluded: + +1. Knowledge about the functional behaviour of remote NAT devices can be beneficial for the MG-local NAT-T support function(s). +2. There are different behaviours, particularly between legacy and BEHAVE-compliant NATs. +3. The observation of the IP bearer-path, especially in direction from remote NAT device towards MG may allow the derivation of helpful information (for the MG- or MGC-level NAT-T support logic). +4. Such "feedback" from remote NAT devices may be classified in L4-specific and L4-independent information. +5. L4-specific information would be covered by L4-specific NAT-T packages (such as the TCP hole punching package in case of TCP, see clause 9), and L4-independent information could be part of solutions using the generic NAT-traversal peer-to-peer package. + +This Recommendation aims to address network scenarios with consideration of legacy and BEHAVE-compliant NAT devices in order to improve the likelihood of successful NAT traversal. + +3 See IETF WG BEHAVE (). + +## **IV.3 Local NAT function by ITU-T H.248 MG and end-to-end consideration** + +The previous model with a remote NAT entity may need to be extended for scenarios whereby the MG itself provides an embedded NAT function. Figure IV.3 illustrates such a model from an end-to-end P2P service point of view. + +It may be noted that such a local NAT function should be preferably compliant to "BEHAVE". + +NOTE – "BEHAVE compliance" would relate to a number of IETF RFCs, as well as work in progress like e.g., "*Common requirements for Carrier Grade NAT (CGN)*" [b-IETF behave-lsn], see also clause 3.2.1. + +There may be scenarios with chained, remote and local NAT functions. The evaluation of such consecutive NAT devices in the IP bearer path, possibly with different NAT behaviour, is for further studies. + + + +Generic end-to-end NAT-Traversal model, if ITU-T H.248 MG provides also a local NAT function + +![Diagram of a generic end-to-end NAT-Traversal model. It shows two peers, Peer_x and Peer_y, connected via IP bearer paths through Remote NAT devices and a central ITU-T H.248 border router/gateway (MG). Peer_x consists of an IP host with a bearer endpoint connected to a Remote NAT_x device. This device has a 'Type "legacy NAT"' and a 'Type "BEHAVE-compliant NAT"'. The path continues through a cloud representing the IP bearer path to the MG. The MG is an ITU-T H.248 border router/gateway containing 'Additional NAT-traversal support for peer-to-peer', 'Basic NAT-traversal tools [ITU-T H.248.37] and [ITU-T H.248.50]', and a 'Local NAT function (e.g., if B2BIH mode)'. A dashed line from the MG's local NAT function points to a requirement: 'Requirement: any MG-local NAT function should be "BEHAVE-compliant"!'. The path continues through another cloud representing the IP bearer path to a Remote NAT_y device, which also has 'Type "legacy NAT"' and 'Type "BEHAVE-compliant NAT"'. Finally, it connects to Peer_y, which consists of an IP Host with a bearer endpoint. A dashed line labeled 'Feedback path in X-to-Y direction' originates from the MG and points towards Peer_y. The diagram is labeled H.248.84(12)_FIV.3.](fc02903382cebe6fc11e4c0d74b5313f_img.jpg) + +``` + +graph LR + subgraph Peer_x + IP_host_x[IP host] + Bearer_endpoint_x[Bearer endpoint] + end + + Remote_NAT_x[Remote NATx device] + MG[ITU-T H.248 border router/gateway MG] + Remote_NAT_y[Remote NATy device] + + subgraph Peer_y + IP_host_y[IP Host] + Bearer_endpoint_y[Bearer endpoint] + end + + Peer_x -- IP bearer path --> Remote_NAT_x + Remote_NAT_x -- IP bearer path --> MG + MG -- IP bearer path --> Remote_NAT_y + Remote_NAT_y -- IP bearer path --> Peer_y + + MG -. Feedback path in X-to-Y direction .-> Peer_y + +``` + +ITU-T H.248 + +ITU-T H.248 border router/gateway + +Additional NAT-traversal support for peer-to-peer + +Basic NAT-traversal tools [ITU-T H.248.37] and [ITU-T H.248.50] + +Local NAT function (e.g., if B2BIH mode) + +MG + +Requirement: any MG-local NAT function should be "BEHAVE-compliant"! + +"Feedback path in X-to-Y direction" + +IP host + +Bearer endpoint + +*Peerx* + +IP bearer path + +Type "legacy NAT" + +Type "BEHAVE-compliant NAT" + +*Remote NATx device* + +IP bearer path + +IP Host + +Bearer endpoint + +*Peery* + +IP bearer path + +Type "legacy NAT" + +Type "BEHAVE-compliant NAT" + +*Remote NATy device* + +H.248.84(12)\_FIV.3 + +Diagram of a generic end-to-end NAT-Traversal model. It shows two peers, Peer\_x and Peer\_y, connected via IP bearer paths through Remote NAT devices and a central ITU-T H.248 border router/gateway (MG). Peer\_x consists of an IP host with a bearer endpoint connected to a Remote NAT\_x device. This device has a 'Type "legacy NAT"' and a 'Type "BEHAVE-compliant NAT"'. The path continues through a cloud representing the IP bearer path to the MG. The MG is an ITU-T H.248 border router/gateway containing 'Additional NAT-traversal support for peer-to-peer', 'Basic NAT-traversal tools [ITU-T H.248.37] and [ITU-T H.248.50]', and a 'Local NAT function (e.g., if B2BIH mode)'. A dashed line from the MG's local NAT function points to a requirement: 'Requirement: any MG-local NAT function should be "BEHAVE-compliant"!'. The path continues through another cloud representing the IP bearer path to a Remote NAT\_y device, which also has 'Type "legacy NAT"' and 'Type "BEHAVE-compliant NAT"'. Finally, it connects to Peer\_y, which consists of an IP Host with a bearer endpoint. A dashed line labeled 'Feedback path in X-to-Y direction' originates from the MG and points towards Peer\_y. The diagram is labeled H.248.84(12)\_FIV.3. + +**Figure IV.3 – Generic end-to-end NAT-Traversal model (if ITU-T H.248 MG provides also a local NAT function)** + +# Appendix V + +## Illustration of performance measurements + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides background information for some Statistics defined by this Recommendation. + +## V.1 Statistic "TCP connection establishment delay (in TCP merge mode)" + +This ITU-T H.248 Statistic (defined in clause 11.4.1) is an ITU-T H.248 gateway specific performance metric, not to be confused with the existing TCP connection establishment delay (as defined for TCP endpoints). + +NOTE – The existing TCP connection establishment delay $\tau_{\text{EST}}$ may be precisely defined on basis of the TCP state transition diagram. It is the time between the triggering of active/passive Open in state CLOSED till reaching state ESTABLISHED. + +Figure V.1 is based on Figure I.4 with additional performance parameters related to establishment delay. The performance parameters (indicated as bold, dashed arrows) provide again the existing TCP connection establishment delay $\tau_{\text{EST,A}}$ and $\tau_{\text{EST,B}}$ from remote TCP perspective. The parameters (indicated as bold, dotted arrows) are related to the considered ITU-T H.248 Statistic. + +Figure V.1 outlines two principal performance parameters: + +- Stream-endpoint specific Statistics: $\tau_{\text{EST,Ta/Si}}$ for SEP *Ta/Si* and $\tau_{\text{EST,Tb/Si}}$ for SEP *Tb/Si*; and +- Stream specific Statistic: $\tau_{\text{EST,Si}}$ for Stream *Si*. + +ITU-T H.248 Statistic *tcpccm/tcpest* relates to the Stream level statistic $\tau_{\text{EST,Si}}$ . + +The connection establishment delay is bounded by a start event and end event, also known as reference events in the area of performance measurements. The reference events for Statistic *tcpccm/tcpest* are + +- *start event*: related to ITU-T H.248 signalling – the received ITU-T H.248 Command.req (from the MGC) which triggers the creation of the 2nd SEP, thus the complete ITU-T H.248 Stream for TCP traffic; +- *end event*: related to TCP packets – when TCP ACK is received or sent at both SEPs (at the MG external bearer interfaces). +- Stream-endpoint specific Statistics: could be based on a received or sent TCP ACK at the SEP. + +ITU-T H.248 Statistic *tcpccm/tcpest* allows thus the correlation of call control signalling with successful bearer establishment, and would be then a meaningful performance parameter for "TCP merge" operations. + +![Sequence diagram of ITU-T H.248 Statistic 'TCP connection establishment delay (in TCP merge mode)'. The diagram shows the interaction between two Peer TCP endpoints (A and B) and a central ITU-T H.248 context C_Z containing two Stream endpoints, S_a and S_b. The process involves SYN and ACK segments being exchanged between the peers and the stream endpoints. Key delays are marked: Node A's connection establishment delay (tau_EST,A), MG SEP Ta/Si connection establishment delay (tau_EST,Ta/Si), MG stream Si connection establishment delay (tau_EST,Si), MG SEP Tb/Si connection establishment delay (tau_EST,Tb/Si), and Node B's connection establishment delay (tau_EST,B). The diagram also includes TCP state variables like Phi_SYN,Rx and Phi_SYN,Tx with sequence numbers. A note indicates the MG strategy is 'Drive one remote TCP entity for simultaneous open'.](89f8aefc01866631793087542316cef2_img.jpg) + +Initial connection establishment + +Termination "Ta" +Stream endpoint Si + +**ITU-T H.248 context CZ** +Both SEPs in steady state "TCP merge" + +Termination "Tb" +Stream endpoint Si + +MG strategy: "*Drive one remote TCP entity for simultaneous open*". + +A +Peer TCP endpoint or TCP relay node + +B +Peer TCP endpoint or TCP relay node + +Node A: connection establishment delay $\tau_{EST, A}$ + +MG SEP Ta/Si: connection establishment delay $\tau_{EST, Ta/Si}$ + +MG stream Si: connection establishment delay $\tau_{EST, Si}$ + +MG SEP Tb/Si: connection establishment delay $\tau_{EST, Tb/Si}$ + +Node B: connection establishment delay $\tau_{EST, B}$ + +End-to-end TCP connection established + +H.248.84(12)\_FV.1 + +Sequence diagram of ITU-T H.248 Statistic 'TCP connection establishment delay (in TCP merge mode)'. The diagram shows the interaction between two Peer TCP endpoints (A and B) and a central ITU-T H.248 context C\_Z containing two Stream endpoints, S\_a and S\_b. The process involves SYN and ACK segments being exchanged between the peers and the stream endpoints. Key delays are marked: Node A's connection establishment delay (tau\_EST,A), MG SEP Ta/Si connection establishment delay (tau\_EST,Ta/Si), MG stream Si connection establishment delay (tau\_EST,Si), MG SEP Tb/Si connection establishment delay (tau\_EST,Tb/Si), and Node B's connection establishment delay (tau\_EST,B). The diagram also includes TCP state variables like Phi\_SYN,Rx and Phi\_SYN,Tx with sequence numbers. A note indicates the MG strategy is 'Drive one remote TCP entity for simultaneous open'. + +Legend: Symbol $\tau$ for performance parameter *TCP connection establishment delay*, +with $\tau_{EST,Tb/Si}$ as observed by the Stream endpoint *Tb/Si* (= Stream *Si* at Termination *Tb*) +and $\tau_{EST,Ta/Si}$ as observed by the Stream endpoint *Ta/Si* (= Stream *Si* at Termination *Ta*) +and $\tau_{EST,Si}$ as observed by Stream *Si* as such; +Symbol $\Phi$ for *TCP state variable concerning sequence numbers* (see clause I.1.3). + +**Figure V.1 – ITU-T H.248 Statistic "TCP connection establishment delay (in TCP merge mode)"** + +## V.2 Statistic "TCP round-trip time during connection establishment phase" + +This ITU-T H.248 Statistic, defined in clause 12.4.1, is an ITU-T H.248 gateway specific performance metric, not to be confused with the existing "TCP round-trip time during TCP connection lifetime" (as defined for TCP endpoints). + +Figure V.2 illustrates the existing TCP performance parameter and the ITU-T H.248 Statistic form clause 12: + +The performance parameters (indicated as bold, dashed arrows) provide the TCP RTT $\tau_{RTT,A}$ and $\tau_{RTT,B}$ from remote TCP perspective. The parameters (indicated as bold, dotted arrows) are related to the considered ITU-T H.248 Statistic *tcpqgm/tcprttest*. + +![Sequence diagram showing TCP connection establishment between Node A and Node B via ITU-T H.248 context Cz.](675af5bb2357ce5b510e613d04f66bdc_img.jpg) + +The diagram depicts the initial connection establishment phase between Peer TCP endpoint A and Peer TCP endpoint B through an ITU-T H.248 context $C_z$ . The context contains Termination " $T_a$ " with Stream endpoint $S_i$ and Termination " $T_b$ " with Stream endpoint $S_j$ , both in steady state "TCP merge". + +The sequence starts with Node B sending a $SYN(SN_{Init} = B1)$ . At Termination $T_b$ , the state is $\Phi_{SYN, Rx}(SN_{Rx} = unknown)$ and $\Phi_{SYN, Tx}(SN_{Tx} = unknown)$ . After receiving the SYN, the state at $T_b$ updates to $\Phi_{SYN, Rx}(SN_{Rx} = SN_{Init} = B1)$ . A red dashed arrow indicates "Note: no valid RTT measurement because SYN is not acknowledged => connection establishment reattempt, see below". + +Node A then sends $SYN(SN_{Init} = A1)$ . This segment is dropped internally at Termination $T_a$ where states are initially unknown. After the drop, Node A sends $SYN(SN_{Init} = A1)$ again. Termination $T_a$ updates to $\Phi_{SYN, Rx}(SN_{Rx} = SN_{Init} = A1)$ and $\Phi_{SYN, Tx}(SN_{Tx} = SN_{Init} = B1)$ . Termination $T_b$ updates to $\Phi_{SYN, Rx}(SN_{Rx} = SN_{Init} = B1)$ and $\Phi_{SYN, Tx}(SN_{Tx} = SN_{Init} = A1)$ . + +The exchange continues with $SYN(SN_{Init} = B1), ACK(SN_{Init} = A1+1)$ being sent from the MG towards Node A and Node B. Node A responds with $ACK(SN_{Init} = B1+1)$ . The diagram shows RTT measurements: $\tau_{RTT,A}$ at Node A, $\tau_{RTT,Ta/Si}$ at MG SEP Ta/Si, $\tau_{RTT,Tb/Sj}$ at MG SEP Tb/Sj, and $\tau_{RTT,B}$ at Node B. The process concludes with "End-to-end TCP connection established". + +Sequence diagram showing TCP connection establishment between Node A and Node B via ITU-T H.248 context Cz. + +H.248.84(12)\_FV.2 + +Legend: Symbol $\tau$ for performance parameter *TCP round-trip time*: +with $\tau_{RTT,A}$ as observed by remote node A, +and $\tau_{RTT,Ta/Si}$ as observed by the Stream endpoint $Ta/Si$ (= Stream $S_i$ at Termination $Ta$ ) +and ditto for the other side B. + +**Figure V.2 – ITU-T H.248 Statistic "TCP round-trip time during connection establishment phase"** + +It may be noted that there are two RTT statistic types differentiated, related to the connection *establishment* phase (clause 12.4.1) and the entire connection *lifetime* (clause 12.4.2). Such a separation is motivated by TCP mode dependency and cost factors. + +# Bibliography + +- [b-ITU-T H.248.43] Recommendation ITU-T H.248.43 (06/2008), *Gateway control protocol: Packages for gate management and gate control.* +- [b-ITU-T H.248.53] Recommendation ITU-T H.248.53 (03/2009), *Gateway control protocol: Traffic management packages.* +- [b-ITU-T H.248.76] Recommendation ITU-T H.248.76 (09/2010), *Gateway control protocol: Filter group package and guidelines.* +- [b-ITU-T H.248.79] Recommendation ITU-T H.248.79 (02/2012), *Gateway control protocol: Guidelines for packet-based streams.* +- [b-ITU-T Y.1560] Recommendation ITU-T Y.1560 (09/2003), *Parameters for TCP connection performance in the presence of middleboxes.* +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (04/2010), *Functional requirements and architecture of next generation networks.* +- [b-IETF RFC 1191] IETF RFC 1191 (1990), *Path MTU Discovery.* +- [b-IETF RFC 1323] IETF RFC 1323 (1992), *TCP Extensions for High Performance.* +- [b-IETF RFC 2663] IETF RFC 2663 (1999), *IP Network Address Translator (NAT) Terminology and Considerations.* +- [b-IETF RFC 3142] IETF RFC 3142 (2001), *An IPv6-to-IPv4 Transport Relay Translator.* +- [b-IETF RFC 4022] IETF RFC 4022 (2005), *Management Information Base for the Transmission Control Protocol (TCP).* +- [b-IETF RFC 4572] IETF RFC 4572 (2006), *Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP).* +- [b-IETF RFC 4614] IETF RFC 4614 (2006), *A Roadmap for Transmission Control Protocol (TCP) Specification Documents.* +- [b-IETF RFC 4787] IETF RFC 4787 (2007), *Network Address Translation (NAT) Behavioral Requirements for Unicast UDP.* +- [b-IETF RFC 5128] IETF RFC 5128 (03/2008), *State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs).* +- [b-IETF RFC 5508] IETF RFC 5508 (2009), *NAT Behavioral Requirements for ICMP.* +- [b-IETF RFC 5597] IETF RFC 5597 (2009), *Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol.* +- [b-IETF RFC 6135] IETF RFC 6135 (2011), *An Alternative Connection Model for the Message Session Relay Protocol (MSRP).* +- [b-IETF RFC 6296] IETF RFC 6296 (2011), *IPv6-to-IPv6 Network Prefix Translation.* +- [b-IETF behave-app] IETF draft-ford-behave-app-05 (2007), *Application Design Guidelines for Traversal through Network Address Translators.* (expired document). +- [b-IETF behave-lsn] IETF ietf-behave-lsn-requirements-05 (2011), *Common requirements for Carrier Grade NATs (CGNs).* + +- [b-IETF behave-sctponat] IETF draft-ietf-behave-sctponat-06 (2012), *Stream Control Transmission Protocol (SCTP) Network Address Translation*. +- [b-ETSI TR 183 068] ETSI TR 183 068 V3.1.1 (2009-08), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Guidelines on using Ia H.248 profile for control of Border Gateway Functions (BGF); Border Gateway Guidelines*. +- [b-ETSI TR 187 008] ETSI TR 187 008 V1.1.1 (2008-03), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NAT traversal feasibility study report*. +- [b-ETSI TS 183 018] ETSI TS 183 018 V3.5.2 (2010-01), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile Version 3 for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification*. +- [b-IANA SDP] IANA registered Session Description Protocol (SDP) Parameters +. +- [b-TCP/IP Vol.1] Stevens, W.R. (1994), *TCP/IP Illustrated, Volume 1: The Protocols*, Addison-Wesley. +- [b-TCP/IP Vol.2] Wright, G.R., and Stevens, W.R. (1995), *TCP/IP Illustrated, Volume 2: The Implementation*, Addison-Wesley. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6cd488f97bbd730a433586f8e4c91a9a2c0718b --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16bbf5311bd2aa0518eced80b337821e45d042f5bb8bdd9416bc6c2e08647882 +size 22690 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c7fb69ccae5b24e660d61b3147193bd3fe9a405 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4442b8b8d0b85e711fb5a4e269e935946b02658acf708cf1e7d974d80eeef8d0 +size 118646 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3435610985e242405abf41e8ca07323afcd1b3c1 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:285f022cc8ea95e20d3fd4fff4ebdb4bbe71494f6343dc0012dbeaded9003d7c +size 23766 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2d46f264b1e8b25a5b3005b6d8b4304623f1102 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c106e67871b57c326b03f4def5ba710d998a19e697628e177659f8e31b68b0c2 +size 132929 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fdeb8df8aafc2b247f1b417e191ed860ded6642 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33a68a292e4311457724b8bd0fd3154f6862290b87f2e8dabb9d0edac5f9c754 +size 157244 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc527f7a0bd07a02940be4f6e3fed3218fd59c0d --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebf8c1e702153cb6e5045cd2f713b6335314dd0228713904de81859a5447c733 +size 87587 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a92c5beefefdccd8245cd8c612763755bda5bf1c --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7db05e4302a80d38c2a83b6cedac1951243f41106079ce2f4552364edfd26678 +size 35673 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..884d314ceeeb1d13ff8fe325ec54edf8001a9809 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba486286441479a788bf2bd74ceddca7a13d5e5cb69f14f8b0c2b9aa6cf04707 +size 55028 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7542b4a2d950731b5eb34f84aade325fb379674e --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:963087a7568f5a94f8d9a45108f9bf38bc5fb28c45f9703286cc5e7203908245 +size 24596 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9096fe90ce673242ccb18de75bfd566e310883c9 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cf3770b21b5154b47f2deb7b6a571d8ea9c22d3e406cee712df4caa4dfb884e +size 44835 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9464fc4680d08a4d46487cf50f3ec899d7f0ca7 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:563ce4c55aaea4ea78d99f9e557d1985f70970ad6f606794b936790c445b7a64 +size 173901 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f1e39527b0671552f671e4b33e6e91a72857590 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2c9b88251c7a5572062945c955f53dc9776ad7323c039e8d4ae83a2c489f53b +size 84813 diff --git a/marked/H/T-REC-H.248.86-201401-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/H/T-REC-H.248.86-201401-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bda47e9a9d25738be40c3ea50145882c60cff163 --- /dev/null +++ b/marked/H/T-REC-H.248.86-201401-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30ead67c8ef73b5464d102b7736a1200a6a6419dc4041b40d02bbe9e9c440def +size 24066 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2a4e65c839a409a51c5562fcc84963ad1449c69 --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2939374af1665dbc1fc39ac17c3726f476f63cfdb558c820c9c182b0bf644ba3 +size 129007 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d59d1d8e2ad7f40b664295e405663ab3ac628df5 --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10fab7151b85da144dc811c3943d1ca6c9a33ff1329681178d98ab9b7befb269 +size 81769 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ad98c6e45b6c52f074f0054407ca88a640d8f1d --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58019f38be268f19eaa80c6d56d0f6b39d5741569a8f3ccc04117fa95d9c6465 +size 4016 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..120f466454db9eb6752274f253dcdc5c4894688b --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cb4501e80f57ae6a7c827e03a18d3c91622568737575a58f376ddab30e1be66 +size 185224 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45036f0da54fa37bd128535cfbd3f7ebb6a64eba --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19af435911dea466753797926ea3d763f95bb7d4f5ecf405e20c112a0b4edfbf +size 140924 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef4a9fef8053efa94dd0ebf0642c19183dbd0041 --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9f60ab48e9019da72d44fc8e586a7d010f5d018f577a73d892dcd734bf66c10 +size 117843 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db4ecf32d3892d65b725896d138f05a1d8fd1623 --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22aa1eda886d0ea8de7244740c47ea511f93279c9d0e2eb8b049b39dac4377ba +size 182859 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41c842ad424c72b7d0137d96d236d077db496a66 --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f24316d89d027b6d979a89d46f2e7edd9949a65568690b9da6c53758e83a6fa +size 142677 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed56ab891673d79c9ed339576daffc36d2e17b34 --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c177e973a597003ea164ccb6ca17d569a0ca74fa50532d75c9ec3f4f79e4aa2b +size 187968 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..befa237923f37e8043dd1cf2934b4bc9b30adb87 --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0244899cd09408dd61f69ec406841ea6aa7d07895b975ee4773fb75cc5dd961 +size 144653 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f3784c500df17ca0d8c09401aac7e5a5c506250 --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:562b8cac38f40462fc920fbcbdd5871672d8134c75b1e654d3633fb16e20e5aa +size 140760 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c3835dde0e27f7b0d1cfd1afe9e29b9eff6b7db --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de8fc2f33f7d18805f6bed8273998263f9277742832c13927b4d1075ae29ab86 +size 138497 diff --git a/marked/H/T-REC-H.248.87-201401-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg b/marked/H/T-REC-H.248.87-201401-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c444392d8545827efe80d6861db0682b4144f478 --- /dev/null +++ b/marked/H/T-REC-H.248.87-201401-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a95081cf311c7d16d5b5cfa211c83fbfa02b7fe45c54b74efe94bdafb919a791 +size 111033 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e815cf7d8b93f743b8431f78dd5ca65278ef648 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ec3cac2233a0b4e4fd26fde5ffc2ac266601a126320cd4b988439c9697b4957 +size 56437 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/19f5ea8afbf380781eb0645831a88987_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/19f5ea8afbf380781eb0645831a88987_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6afedfd0d413c3a9e420dadf029d2347c68060b0 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/19f5ea8afbf380781eb0645831a88987_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e34348e9e4533dde7df60f14b4eb6dc3f82f09f86ae3cd41711e6aa69de1052 +size 83252 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055 +size 6859 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/23816aaa8e6defc50fc888da62fd59cc_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/23816aaa8e6defc50fc888da62fd59cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..539997957dc91cd3f42269a6f515736d0c30e58e --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/23816aaa8e6defc50fc888da62fd59cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0bdbe552473fc8ecf3b66c81b38719e142ea2547b1087ad3153c9f29043ebb8 +size 80407 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..181c1fd518bd481abee2bee21be8fb9c65c6ced8 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b8e195319b47e7b0d974aafb8c664f6d5c433096c95bee22a6bf14db42205eb +size 90173 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33e2871338e6fa1e8a4c9213683dab8e8ccb19b9 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f46e9ad4f899832fdb2efa044aa2d1cbad10e4b722d5a6a27d0138634d16888 +size 91060 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e78a6a4fb97d8b5680da965bb5ea9b835d09f77 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e2692e3e6d54cda2f3ee275ccd201ebdb828157df7ed9211a51afad62957b28 +size 64519 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba806a272cc4f23bdde826e0235b14af86eeb440 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc3e5e5182bd65678dee678ff4c03994bf1be12fb22c2feaf16c478e416606ec +size 54799 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c684be74d18a2e627b3e1af0c01cdc9a1b41d20 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d68697d4d5fbb69f924b76ab64e143bc2219361abd9b828425c2d5373538df2 +size 54628 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fabdb54db1dafb67ddfa4f6a9f567bca58142847 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc46ae2726357b5049267034855197ba48705f618c3808697169f5153fe000db +size 84767 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a8876f83c165f9882a5dfa8684c391b16f5d693 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcb6cae660c00fe698f51774705b9166179283cf710c51f96215e78a3ef1a732 +size 103175 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67af8d346550bc7ff47166e35fd34342fb590156 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a795e95cf8699b57f7edcd0d583da27429f8196e5ec359325abc5c2113b3324d +size 90944 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/920eeb131e71a5b81535239f1c838c68_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/920eeb131e71a5b81535239f1c838c68_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bed8538637d5caea02903637c1ec830da19ec52 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/920eeb131e71a5b81535239f1c838c68_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9936a7d22c4134d77b7f5669aba6703ccfad8ccac92ed41e0118d821a158010b +size 77369 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/99938fa8d7d80af041634eba601e418b_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/99938fa8d7d80af041634eba601e418b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ed432d1211d3279184c03126a43192ec4beba15 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/99938fa8d7d80af041634eba601e418b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bf66abdece17fa9a5f2b84c265fb63dc289950b04685948d1b42b79a54fe09b +size 85275 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/9b62a616c7a1097c5da57f001ab6dd64_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/9b62a616c7a1097c5da57f001ab6dd64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4118cd01e390a9c24f7e50bf2bfcb3ed1c29dca4 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/9b62a616c7a1097c5da57f001ab6dd64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae5d049e41784463ba11070d3d32a8988c88cc55cd2a4a7e3f59ce3af2f82ab4 +size 82865 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5397c57f6bdeeb2ab604549b551fc84e742801b7 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3255b2e7d4bbf4902b706397f77641a288b9e67dc20138c073f4aa35d18a041 +size 90592 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fb5fd118a811510cb72325b40b08d5d9047a60a --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71a06b2d3616eb2f8ae53c3555e90500c861674f28a02aca61712c0422597501 +size 70458 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2885d600eac96fa18034ee2ee7ddf4fec894d38 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa8e2a03f30a044e65e03573cf260b49c1a84cf833ddc4b6d7226328ba636658 +size 94510 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2923ed631d82b53fbc917fc4490ed0914ae37709 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8ac29ae2e8be9ca9856a27b01b740fd9ea79dcd41af040d6976afaa0e921a90 +size 104400 diff --git a/marked/H/T-REC-H.248.92-201410-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/H/T-REC-H.248.92-201410-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f68e2eb9f855f1a1d4628df5b5bc486cd4e63a73 --- /dev/null +++ b/marked/H/T-REC-H.248.92-201410-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:264542489b69510d59dacfb9fd13819b1f4a8df6e8383192b6c60a4fb8d1f9b4 +size 66667 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf36454bced2a65211cb37752a8659e507300900 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3da1be37607883fb61b9a9c000e0ab4741b74192ba150585e4c84fa04d746a5c +size 27523 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..037d78dc1bef13694b26b99107821e8e28495f06 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d51f50de83dd2be628d6c211b05ca4aa9f4a15b0aeb8e1c1e0ae9ec0a2055ca +size 118133 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827609df9ad8667ae079f875841506349f063390 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d2afb537db9f3588854962a991eb1178220b2bbb8ff3cea6712979a53a864b +size 4107 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e01fcdf7a191ac396330930c6d59f34d9852f171 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13b8df8d88720df8eb7dbe8a43f63d421fa34f9528a2cdbfc2a9142b5707deac +size 58112 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94a7cbaeefcc9f96fec148248d7e9bb9cc35c881 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b22bb5fa0be9ac16de898feaf0c9be3546a973dd8bd9a8d30dfe5f75c48ce4c +size 33494 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77359ebbf2a59590da9d8ab4950004e1509d5a1b --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b2e0482633005a4930ca3e1b607f4963d1512e76337567b1632e6833cfa36c2 +size 52671 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9c132cd7b95ecf927415d00537e33a7c7ba6f37 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8c2e536ec0af7d3cb3902cdbc5b6958f8c2d32791015a35d53c4e5a61068c37 +size 85328 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bebab98425baed992050fdacf326a03c79464d5c --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b34bd450cd98e126c58e69408f099b930da780b2405d12586ffc50cf879d3ef2 +size 89713 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6eaceed5e325e07ed0078958f5698dfc97023565 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bc15ed3bbd7e6d8ef6a2a0eff1927c9d4c40573eebbf4eddc4b09f0cfce9d24 +size 41562 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff52a15f28cdc621e3bad2b02673e869ef2a2bfe --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c809b6224a81c7796838d942fb69a763ade3b305f498f6b919b5066885382dce +size 41161 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a79f231d26991c6f625187f31bc14fb2afb409c --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e92f3f57e816fa2f111e2cee42aeedd8554272cc73b138ac11d4fb484784f753 +size 70206 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a8f9ac520113f4f03025d9d7e79228c14fa4104 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e3228425e61925a05a0844f433e9bfdc30f4a28ff20a7391a09e215f9e86e78 +size 94038 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7280d9abb9559fb43362f8842eeb6eaae97a1b4 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f1839b5812f77239bbbb9a416801176709ac90d9302d8b59a65ecce3a371493 +size 36292 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ef41fb4a3d124340091021c41e1592ffc85bf9a --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87b3db3ecc65bbc7ec20ae82dde7b3b0a047c085404077b2f15cd4e850f852eb +size 38878 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fa56169490a843a8a852ef4f56f745eba55ba99 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d541be74b1c2d540d369c45cd64043ba17849e1fa22accbb6540b5e86747b92 +size 92420 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47dea5d4e9c6423718a2cdcfbc1f5f4a734d81a8 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90cee8f5236fa1d65c161b188b60dd35e087abbe5306f056dfc3b4693ace2865 +size 65495 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9963cfe7822f479c77683d69cfae54cefad3523f --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e41e538a3e842722a1a9329a1ad8dcc4fc0ebc7ae2dbe269904775115c337a47 +size 241959 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c018e132fb8f8bd91cfef73fbbcc3d8bb1dae27c --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a10736d6b1e7c435c836f1f2a574578d54d82d34f9015a6e6e6cd7274097f2d0 +size 66385 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..212ea420c896e1cc531683cff355b5301aaf3ac6 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de16d2a16892e561b6f5247f500f321de905aa089312892690da03e533c38807 +size 146092 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ca1b8c8f9d0c8e6300f7ecbf42a8d39addffbdd --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef9d78d8aadf72e9fcea622d3889e66e88e4cbd6735fb0e75032ccab7dd0ac8d +size 55985 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43f36aed31961e08d45ec7f97acbda1a880fc5b2 --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fc110c90be48480d4a8d525ff1c6838b039767878eaf5064cc67638a57ef99d +size 54629 diff --git a/marked/H/T-REC-H.248.93-201410-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/H/T-REC-H.248.93-201410-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..216035643bf319105d11258c48c2ab126f0cf10f --- /dev/null +++ b/marked/H/T-REC-H.248.93-201410-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e05f2ab509b54aaf0df7968f309c1caaee88be5eb1f1e1532924120d8bf7186 +size 57158 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e82f87358820d72e06026b805c3b1ffa83b1ee0 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e70588dfc9823dacd07eb3f7c7f1febe9beed881079e2906293b384690f6e7bc +size 109534 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1405eabe9b4eb78a41162fd3d623e3ddcc0c3fad --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4accb1d0dfdf2f51ceace324c2bf36747e0905998ff2e857f99581ba51a62d7 +size 84361 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4342410b5f354c3a71bb2eaf20c33e65399bc2f --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc571e4f4fef7464e42129cc2d821e7a4155760c2ae819b006ee11fdc34b0539 +size 84311 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a0ef3350aaaa27225f3ab73ace90306d559c92e --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d5e7f70f121b6ebe07ee6e776b0ba4aeee814f0c8aedabbf9984cad4296eb19 +size 57163 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2200b25925b2de95e233c12c0bd6d4c7311e3543 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d851ba933c8d84da1bd8fbd22c9edf6f0281144b39d5973618ab26a8414d5f50 +size 81798 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827609df9ad8667ae079f875841506349f063390 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d2afb537db9f3588854962a991eb1178220b2bbb8ff3cea6712979a53a864b +size 4107 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d744b5401c6b74311a58b1141199743d39499867 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52ad8d0eda4584e540653a7ea0b34ba7d73a3ae0d90f5d9547b81dc95c8443ca +size 54547 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..071e19e7d0ca24dd9376b19597a9cf1304726069 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0494694a7d09a355b7d138a2c7b642c61e70cb96d4522b3de6675b85b7317152 +size 88909 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..684a869aca7c436059c6acdbf797f3b1e4cf49d8 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2f3c7cb4bdde2254ba3f6fc2288263f034fa7473e6dfe27fde6172eba80de5b +size 83322 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/446100c084b94817a19c319fa776b412_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/446100c084b94817a19c319fa776b412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f619e8c5fece0b12c78a0b753833ec3f9288d35 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/446100c084b94817a19c319fa776b412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:838011fd114d1bdc4209c54cc3918a6a929cddec5cd41d1962930e03ff806677 +size 86217 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40c5a8bf7a672f500bb7cfa21af476d7d58e0636 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a6f63743db4133a1214bcca9342fe9571b6d8476baa8c35a02f5ad6f10b1224 +size 62406 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e26645f00a34d98fe894a58aed317a0145b7981e --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:206095fa4b95e98bba6c88e0fdc3a0b9b1964a92831abf078b0fd7246d251832 +size 81511 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..532c6f458fe4e638432091069296d2f74a6a0ad7 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6702bd8e637a5e69ac5d0933e2469ea95eed12042ca3bf926539376462e2f909 +size 69668 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..206475af4c03e9f0e3773ec1b6e2b1e30d723e8a --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:642a7f55c251c71dcbe6064bf5b8e9473b3c16045971f9652846b0028c5415b3 +size 83007 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0513f734c5e22cdad9c32b4edda230739c25f6b3 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a8cd2948d96e69c6779394f5d42d04ad7fd52e5f03884c0250d789429ea98e9 +size 108174 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f80831bec17590dff7d2dcdf7bed73722dd580a6 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aca7d8faf2165238ab5f9bd09729d90e3c09bcc41331c88ce1f2af3979a2cfd4 +size 67356 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5188ac92f1c318dc93c3f8ed2ec51f46ce06e4a4 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2506f1260811f30ad626716c49c99bb04ef4331282e0231266ec9b95592ee65d +size 55249 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/aa9441a5971655a79987d70fc551b26a_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/aa9441a5971655a79987d70fc551b26a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19d320e67da3867652d180ff54481fb85be4b8d4 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/aa9441a5971655a79987d70fc551b26a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57a456ef5e908808a5c237cbb8a5e5168e622df4318e0784de6ebcfdb3626a0d +size 44104 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2e8e5e3111f31ba7b029997dad7d59be2cdbeb1 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8044e6eaf7e13665bea33c6e47bbaccf788e535cc36cf435e2e074ac23c9f649 +size 82471 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34d45b107fd92fd4b25e1332cc5ca6caa1995a1c --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93bd2f9ab45cd4c9fd59b33b6b1ab36de597e83a66a4036dde502cefcd6216bf +size 77325 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28d4108a1ec95ccaee6327f479029156d453068f --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6462ad15254f588af8c8302a99c00c71dc29e4b1e76df3b96c236b92b73175bf +size 59221 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfddffeba3249bd3934bf205c5bdf5c92a985417 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:198853380a6d866ec3739ecfa581157d34ec5cac1178c47b6cd48e8b616762ea +size 43428 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c25a3d18cb47bb11a58797f3f1053bf2db788b5 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3ee79d8ea6358fb737ce6442ace20626761d1f75187a3c9441ad14a0eb2c4fb +size 107815 diff --git a/marked/H/T-REC-H.248.97-201511-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/H/T-REC-H.248.97-201511-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c55e80a31dedbb279d0fadca3babb00d279c1e1 --- /dev/null +++ b/marked/H/T-REC-H.248.97-201511-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b450b07ea6f5dd479aa3ddcbf8020ef0e973cc5ceab0c55333159b8aae9d082 +size 139298 diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/raw.md b/marked/H/T-REC-H.263-200501-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c4c0ddb5d299f6e73f630c7d34c2de8968fd4772 --- /dev/null +++ b/marked/H/T-REC-H.263-200501-I_PDF-E/raw.md @@ -0,0 +1,7458 @@ + + +International Telecommunication Union + +# **ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **H.263** + +(01/2005) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Coding of moving video + +--- + +## **Video coding for low bit rate communication** + +ITU-T Recommendation H.263 + +**ITU-T** + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a stylized blue globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Video coding for low bit rate communication + +## Summary + +This Recommendation specifies a coded representation that can be used for compressing the moving picture component of audio-visual services at low bit rates. The basic configuration of the video source coding algorithm is based on ITU-T Rec. H.261 and is a hybrid of inter-picture prediction to utilize temporal redundancy and transform coding of the remaining signal to reduce spatial redundancy. The source coder can operate on five standardized video source formats: sub-QCIF, QCIF, CIF, 4CIF and 16CIF, and can also operate using a broad range of custom video formats. + +The decoder has motion compensation capability, allowing optional incorporation of this technique in the coder. Half pixel precision is used for the motion compensation, as opposed to ITU-T Rec. H.261 where full pixel precision and a loopfilter are used. Variable length coding is used for the symbols to be transmitted. + +In addition to the basic video source coding algorithm, eighteen negotiable coding options are included for improved compression performance and the support of additional capabilities. Additional supplemental information may also be included in the bitstream for enhanced display capability and for external usage. + +This third edition of H.263 integrates Annexes U, V, W and X, which were approved and published separately before, with a number of corrections and clarifications: + +- correction of Figure 8; +- clarification in Table 1 regarding BPPmaxKb table and Picture Padding; +- clarification in clause 5.3.2 regarding macroblock stuffing preceding a start code; +- clarification regarding interaction between H.263 Annex J and IDCT rounding error; +- clarification in Annex N regarding parsability of the GN/MBA field in BCM; +- clarification in Annex O regarding direct bi-dir predicted MBs and picture extrapolation; +- clarification on the use of B pictures with intra reference pictures in Annex O; +- clarification on the use of Annex P with Annex N; +- correction of Figure U.7 in Annex U. + +## Source + +ITU-T Recommendation H.263 was approved on 13 January 2005 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2005 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | | Page | +|-----|------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 2.1 | Normative references..... | 1 | +| 2.2 | Informative references..... | 1 | +| 3 | Brief specification..... | 2 | +| 3.1 | Video input and output ..... | 2 | +| 3.2 | Digital output and input..... | 2 | +| 3.3 | Sampling frequency..... | 2 | +| 3.4 | Source coding algorithm..... | 2 | +| 3.5 | Bit rate ..... | 5 | +| 3.6 | Buffering..... | 6 | +| 3.7 | Symmetry of transmission..... | 6 | +| 3.8 | Error handling..... | 6 | +| 3.9 | Multipoint operation..... | 6 | +| 4 | Source coder ..... | 7 | +| 4.1 | Source format ..... | 7 | +| 4.2 | Video source coding algorithm ..... | 9 | +| 4.3 | Coding control..... | 13 | +| 4.4 | Forced updating ..... | 13 | +| 4.5 | Byte alignment of start codes ..... | 13 | +| 5 | Syntax and semantics..... | 13 | +| 5.1 | Picture layer..... | 22 | +| 5.2 | Group of Blocks Layer ..... | 32 | +| 5.3 | Macroblock layer..... | 33 | +| 5.4 | Block layer..... | 40 | +| 6 | Decoding process..... | 44 | +| 6.1 | Motion compensation ..... | 44 | +| 6.2 | Coefficients decoding..... | 46 | +| 6.3 | Reconstruction of blocks ..... | 48 | +| | Annex A – Inverse transform accuracy specification ..... | 48 | +| | Annex B – Hypothetical Reference Decoder..... | 49 | +| | Annex C – Considerations for multipoint..... | 51 | +| C.1 | Freeze picture request..... | 51 | +| C.2 | Fast update request ..... | 51 | +| C.3 | Freeze picture release ..... | 51 | +| C.4 | Continuous Presence Multipoint and Video Multiplexing (CPM)..... | 51 | + +| | | +|--------------------------------------------------------------------|----| +| Annex D – Unrestricted Motion Vector mode..... | 53 | +| D.1    Motion vectors over picture boundaries ..... | 53 | +| D.2    Extension of the motion vector range..... | 54 | +| Annex E – Syntax-based Arithmetic Coding mode ..... | 56 | +| E.1    Introduction ..... | 56 | +| E.2    Specification of SAC encoder ..... | 57 | +| E.3    Specification of SAC decoder ..... | 58 | +| E.4    Syntax ..... | 58 | +| E.5    PSC_FIFO ..... | 59 | +| E.6    Header layer symbols ..... | 59 | +| E.7    Macroblock and Block layer symbols ..... | 60 | +| E.8    SAC models..... | 60 | +| Annex F – Advanced Prediction mode ..... | 64 | +| F.1    Introduction ..... | 64 | +| F.2    Four motion vectors per macroblock..... | 64 | +| F.3    Overlapped motion compensation for luminance..... | 65 | +| Annex G – PB-frames mode ..... | 68 | +| G.1    Introduction ..... | 68 | +| G.2    PB-frames and INTRA blocks..... | 68 | +| G.3    Block layer..... | 68 | +| G.4    Calculation of vectors for the B-picture in a PB-frame..... | 69 | +| G.5    Prediction of a B-block in a PB-frame ..... | 69 | +| Annex H – Forward error correction for coded video signal..... | 71 | +| H.1    Introduction ..... | 71 | +| H.2    Error correction framing..... | 71 | +| H.3    Error correcting code ..... | 71 | +| H.4    Relock time for error corrector framing ..... | 72 | +| Annex I – Advanced INTRA Coding mode..... | 72 | +| I.1    Introduction ..... | 72 | +| I.2    Syntax ..... | 73 | +| I.3    Decoding process..... | 74 | +| Annex J – Deblocking Filter mode ..... | 80 | +| J.1    Introduction ..... | 80 | +| J.2    Relation to UMV and AP modes (Annexes D and F) ..... | 81 | +| J.3    Definition of the deblocking edge filter ..... | 81 | +| Annex K – Slice Structured mode ..... | 85 | +| K.1    Introduction ..... | 85 | +| K.2    Structure of slice layer..... | 86 | + +| | | +|--------------------------------------------------------------------------------------|-----| +| Annex L – Supplemental enhancement information specification ..... | 88 | +| L.1    Introduction ..... | 88 | +| L.2    PSUPP format..... | 88 | +| L.3    Do Nothing ..... | 89 | +| L.4    Full-Picture Freeze Request ..... | 89 | +| L.5    Partial-Picture Freeze Request ..... | 89 | +| L.6    Resizing Partial-Picture Freeze Request ..... | 90 | +| L.7    Partial-Picture Freeze-Release Request..... | 90 | +| L.8    Full-Picture Snapshot Tag ..... | 90 | +| L.9    Partial-Picture Snapshot Tag ..... | 91 | +| L.10   Video Time Segment Start Tag ..... | 91 | +| L.11   Video Time Segment End Tag ..... | 91 | +| L.12   Progressive Refinement Segment Start Tag ..... | 91 | +| L.13   Progressive Refinement Segment End Tag ..... | 91 | +| L.14   Chroma Keying Information ..... | 92 | +| L.15   Extended Function Type..... | 94 | +| Annex M – Improved PB-frames mode..... | 94 | +| M.1    Introduction ..... | 94 | +| M.2    B PB -macroblock prediction modes ..... | 95 | +| M.3    Calculation of vectors for bidirectional prediction of a the B-macroblock.... | 95 | +| M.4    MODB table ..... | 95 | +| Annex N – Reference Picture Selection mode..... | 96 | +| N.1    Introduction ..... | 96 | +| N.2    Video source coding algorithm ..... | 97 | +| N.3    Channel for back-channel messages..... | 97 | +| N.4    Syntax ..... | 98 | +| N.5    Decoder process..... | 101 | +| Annex O – Temporal, SNR, and Spatial Scalability mode..... | 102 | +| O.1    Overview ..... | 102 | +| O.2    Transmission order of pictures ..... | 106 | +| O.3    Picture layer syntax ..... | 107 | +| O.4    Macroblock layer syntax ..... | 108 | +| O.5    Motion vector decoding..... | 112 | +| O.6    Interpolation filters ..... | 112 | +| Annex P – Reference picture resampling..... | 115 | +| P.1    Introduction ..... | 115 | +| P.2    Syntax ..... | 118 | +| P.3    Resampling algorithm ..... | 120 | +| P.4    Example of implementation ..... | 123 | +| P.5    Factor-of-4 resampling ..... | 126 | + +| | | +|---------------------------------------------------------------------------------|-----| +| Annex Q – Reduced-Resolution Update mode ..... | 130 | +| Q.1    Introduction ..... | 130 | +| Q.2    Decoding procedure..... | 131 | +| Q.3    Extension of referenced picture..... | 133 | +| Q.4    Reconstruction of motion vectors..... | 134 | +| Q.5    Enlarged overlapped motion compensation for luminance ..... | 136 | +| Q.6    Upsampling of the reduced-resolution reconstructed prediction error..... | 138 | +| Q.7    Block boundary filter..... | 141 | +| Annex R – Independent Segment Decoding mode ..... | 143 | +| R.1    Introduction ..... | 143 | +| R.2    Mode operation..... | 143 | +| R.3    Constraints on usage..... | 144 | +| Annex S – Alternative INTER VLC mode ..... | 145 | +| S.1    Introduction ..... | 145 | +| S.2    Alternative INTER VLC for coefficients ..... | 145 | +| S.3    Alternative INTER VLC for CBPY ..... | 146 | +| Annex T – Modified Quantization mode ..... | 146 | +| T.1    Introduction ..... | 146 | +| T.2    Modified DQUANT Update..... | 146 | +| T.3    Altered quantization step size for chrominance coefficients..... | 147 | +| T.4    Modified coefficient range ..... | 148 | +| T.5    Usage restrictions ..... | 148 | +| Annex U – Enhanced reference picture selection mode ..... | 149 | +| U.1    Introduction ..... | 149 | +| U.2    Video source coding algorithm ..... | 150 | +| U.3    Forward-channel syntax ..... | 151 | +| U.4    Decoder process..... | 169 | +| U.5    Back-channel messages ..... | 174 | +| Annex V – Data-partitioned slice mode..... | 178 | +| V.1    Scope ..... | 178 | +| V.2    Structure of data partitioning..... | 178 | +| V.3    Interaction with other optional modes..... | 181 | +| Annex W – Additional supplemental enhancement information specification ..... | 185 | +| W.1    Scope ..... | 185 | +| W.2    References ..... | 185 | +| W.3    Additional FTYPE Values..... | 185 | +| W.4    Recommended maximum number of PSUPP octets ..... | 185 | +| W.5    Fixed-point IDCT ..... | 185 | +| W.6    Picture message ..... | 195 | + +| | | +|---------------------------------------------------------------------------|-----| +| Annex X – Profiles and levels definition ..... | 200 | +| X.1    Scope ..... | 200 | +| X.2    Profiles of preferred mode support..... | 200 | +| X.3    Picture formats and picture clock frequencies..... | 204 | +| X.4    Levels of performance capability ..... | 205 | +| X.5    Generic capability definitions for use with ITU-T Rec. H.245 ..... | 209 | +| Appendix I – Error tracking ..... | 213 | +| I.1    Introduction ..... | 213 | +| I.2    Error tracking..... | 213 | +| Appendix II – Recommended optional enhancement ..... | 214 | + + + +# Video coding for low bit rate communication + +# 1 Scope + +This Recommendation specifies a coded representation that can be used for compressing the moving picture component of audio-visual services at low bit rates. The basic configuration of the video source coding algorithm is based on ITU-T Rec. H.261. Eighteen negotiable coding options are included for improved performance and increased functionality. This Recommendation contains Version 2 of ITU-T Rec. H.263, which is fully compatible with the original Recommendation, adding only optional features to the original Version 1 content of the Recommendation. + +# 2 References + +## 2.1 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-R Recommendation BT.601-5 (1995), *Studio encoding parameters of digital television for standard 4:3 and wide-screen 16:9 aspect ratios*. + +Reference [1] is referenced herein to define the ( $Y, C_B, C_R$ ) colour space and its 8-bit integer representation for pictures used by video codecs designed according to this Recommendation. (Reference [1] is not used to define any other aspects of this Recommendation.) + +## 2.2 Informative references + +The following additional ITU-T Recommendations are mentioned for illustration purposes in this text. + +- [2] ITU-T Recommendation H.223 (2001), *Multiplexing protocol for low bit rate multimedia communication*. +- [3] ITU-T Recommendation H.242 (2004), *System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s*. +- [4] ITU-T Recommendation H.245 (2005), *Control protocol for multimedia communication*. +- [5] ITU-T Recommendation H.261 (1993), *Video codec for audiovisual services at $p \times 64$ kbit/s*. +- [6] ITU-T Recommendation H.262 (2000) | ISO/IEC 13818-2:2000, *Information technology – Generic coding of moving pictures and associated audio information: Video*. +- [7] ITU-T Recommendation H.324 (2002), *Terminal for low bit-rate multimedia communication*. + +# 3 Brief specification + +An outline block diagram of the codec is given in Figure 1. + +![Figure 1/H.263 – Outline block diagram of the video codec. The diagram shows two main paths: a) Video coder and b) Video decoder. The video coder path consists of a Source coder, a Video multiplex coder, and a Transmission buffer. The video decoder path consists of a Receiving buffer, a Video multiplex decoder, and a Source decoder. A Coding control block is connected to the Source coder and Video multiplex coder. External control is also connected to the Coding control block. The entire system is enclosed in a dashed box labeled T1602680-97.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +``` +graph LR + subgraph Codec [ ] + CC[Coding control] + subgraph VC [a) Video coder] + SC[Source coder] + VMC[Video multiplex coder] + end + subgraph VD [b) Video decoder] + RB[Receiving buffer] + VMD[Video multiplex decoder] + SD[Source decoder] + end + CC --> SC + CC --> VMC + SC --> VMC + VMC --> TB[Transmission buffer] + TB --> CB[Coded bitstream] + CB --> RB + RB --> VMD + VMD --> SD + SD --> VS[Video signal] + end + EC[External control] --> CC + style Codec fill:none,stroke-dasharray: 5 5 +``` + +Figure 1/H.263 – Outline block diagram of the video codec. The diagram shows two main paths: a) Video coder and b) Video decoder. The video coder path consists of a Source coder, a Video multiplex coder, and a Transmission buffer. The video decoder path consists of a Receiving buffer, a Video multiplex decoder, and a Source decoder. A Coding control block is connected to the Source coder and Video multiplex coder. External control is also connected to the Coding control block. The entire system is enclosed in a dashed box labeled T1602680-97. + +Figure 1/H.263 – Outline block diagram of the video codec + +## 3.1 Video input and output + +To permit a single Recommendation to cover use in and between regions using 625- and 525-line television standards, the standardized source formats on which the source coder operates are based on a Common Intermediate Format (CIF). It is also possible using external negotiation (for example, ITU-T Rec. H.245), to enable the use of a wide range of optional custom source formats. The standards of the input and output television signals, which may, for example, be composite or component, analogue or digital and the methods of performing any necessary conversion to and from the source coding format are not subject to recommendation. + +## 3.2 Digital output and input + +The video coder provides a self-contained digital bitstream which may be combined with other multi-facility signals (for example as defined in ITU-T Rec. H.223). The video decoder performs the reverse process. + +## 3.3 Sampling frequency + +Pictures are sampled at an integer multiple of the video line rate. This sampling clock and the digital network clock are asynchronous. + +## 3.4 Source coding algorithm + +A hybrid of inter-picture prediction to utilize temporal redundancy and transform coding of the remaining signal to reduce spatial redundancy is adopted. The decoder has motion compensation capability, allowing optional incorporation of this technique in the coder. Half pixel precision is used for the motion compensation, as opposed to ITU-T Rec. H.261 where full pixel precision and a loopfilter are used. Variable length coding is used for the symbols to be transmitted. + +In addition to the core H.263 coding algorithm, eighteen negotiable coding options can be used, either together or separately (subject to certain restrictions). Additional supplemental information may also be included in the bitstream for enhanced display capability and for external usage. A forward error correction method for application to the resulting video bitstream is provided for use, + +when necessary. The negotiable coding options, forward error correction, and supplemental information usage are described in the subsequent subclauses. + +### **3.4.1 Continuous Presence Multipoint and Video Multiplex mode** + +In this optional mode, up to four separate video "Sub-Bitstreams" can be sent within the same video channel. This feature is designed for use in continuous presence multipoint application or other situations in which separate logical channels are not available, but the use of multiple video bitstreams is desired (see also Annex C). + +### **3.4.2 Unrestricted Motion Vector mode** + +In this optional mode, motion vectors are allowed to point outside the picture. The edge pixels are used as prediction for the "non-existing" pixels. With this mode a significant gain is achieved if there is movement across the edges of the picture, especially for the smaller picture formats (see also Annex D). Additionally, this mode includes an extension of the motion vector range so that larger motion vectors can be used. This is especially useful in case of camera movement and large picture formats. + +### **3.4.3 Syntax-based Arithmetic Coding mode** + +In this optional mode, arithmetic coding is used instead of variable length coding. The SNR and reconstructed pictures will be the same, but significantly fewer bits will be produced (see also Annex E). + +### **3.4.4 Advanced Prediction mode** + +In this optional mode, Overlapped Block Motion Compensation (OBMC) is used for the luminance part of P-pictures (see also Annex F). Four $8 \times 8$ vectors instead of one $16 \times 16$ vector are used for some of the macroblocks in the picture. The encoder has to decide which type of vectors to use. Four vectors use more bits, but give better prediction. The use of this mode generally gives a considerable improvement. A subjective gain is achieved because OBMC results in less blocking artifacts. + +### **3.4.5 PB-frames mode** + +A PB-frame consists of two pictures being coded as one unit. The name PB comes from the name of picture types in ITU-T Rec. H.262 where there are P-pictures and B-pictures. Thus a PB-frame consists of one P-picture which is predicted from the previous decoded P-picture and one B-picture which is predicted from both the previous decoded P-picture and the P-picture currently being decoded. The name B-picture was chosen because parts of B-pictures may be bidirectionally predicted from the past and future pictures. With this coding option, the picture rate can be increased considerably without substantially increasing the bit rate (see also Annex G). However, an Improved PB-frames mode is also provided (see also Annex M). The original PB-frames mode is retained herein only for purposes of compatibility with systems made prior to the adoption of the Improved PB-frames mode. + +### **3.4.6 Forward Error Correction** + +A forward error correction method is specified for use when necessary for the protection of the video bitstream for use, when appropriate. The method provided for forward error correction is the same BCH code method specified also in ITU-T Rec. H.261 (see also Annex H). + +### **3.4.7 Advanced INTRA Coding mode** + +In this optional mode, INTRA blocks are first predicted from neighbouring INTRA blocks prior to coding (see also Annex I). Separate Variable Length Code (VLC) tables are defined for the INTRA blocks. The technique is applied to INTRA-macroblocks within INTRA pictures and to + +INTRA-macroblocks within INTER pictures. This mode significantly improves the compression performance over the INTRA coding of the core H.263 syntax. + +### **3.4.8 Deblocking Filter mode** + +In this optional mode, a filter is applied across the $8 \times 8$ block edge boundaries of decoded I- and P-pictures to reduce blocking artifacts (see also Annex J). The purpose of the filter is to mitigate the occurrence of block edge artifacts in the decoded picture. The filter affects the picture that is used for the prediction of subsequent pictures and thus lies within the motion prediction loop. + +### **3.4.9 Slice Structured mode** + +In this optional mode, a "slice" layer is substituted for the GOB layer of the bitstream syntax (see also Annex K). The purposes of this mode are to provide enhanced error resilience capability, to make the bitstream more amenable to use with an underlying packet transport delivery, and to minimize video delay. A slice is similar to a GOB, in that it is a layer of the syntax that lies between the picture layer and the macroblock layer. However, the use of a slice layer allows a flexible partitioning of the picture, in contrast with the fixed partitioning and fixed transmission order required by the GOB structure. + +### **3.4.10 Supplemental enhancement information** + +Additional supplemental information may be included in the bitstream to signal enhanced display capability or to provide information for external usage (see also Annex L). This supplemental information can be used to signal a full-picture or partial-picture freeze or freeze-release request with or without resizing, can also be used to tag particular pictures or sequences of pictures within the video stream for external usage, and can be used to convey chroma key information for video compositing. The supplemental information may be present in the bitstream even though the decoder may not be capable of providing the enhanced capability to use it, or even to properly interpret it – simply discarding the supplemental information is allowable by decoders unless a requirement to provide the requested capability has been negotiated by external means. + +### **3.4.11 Improved PB-frames mode** + +This optional mode represents an improvement compared to the PB-frames mode option (see also Annexes G and M). The main difference between the two modes is that in the Improved PB-frames mode, each B-block may be forward predicted using a separate motion vector or backward predicted with a zero vector. This significantly improves coding efficiency in situations in which downscaled P-vectors are not good candidates for B-prediction. The backward prediction is particularly useful when there is a scene cut between the previous P-frame and the PB-frame. + +### **3.4.12 Reference Picture Selection mode** + +An optional mode is provided which improves the performance of real-time video communication over error-prone channel by allowing temporal prediction from pictures other than the most recently-sent reference picture (see also Annex N). This mode can be used with back-channel status messages which are sent back to the encoder to inform it about whether its bitstream is being properly received. In error-prone channel environments, this mode allows the encoder to optimize its video encoding for the conditions of the channel. + +### **3.4.13 Temporal, SNR and Spatial Scalability mode** + +In this optional mode, there is support for temporal, SNR, and spatial scalability (see also Annex O). Scalability implies that a bitstream is composed of a base layer and one or more associated enhancement layers. The base layer is a separately decodable bitstream. The enhancement layers can be decoded in conjunction with the base layer to increase perceived quality by either increasing the picture rate, increasing the picture quality, or increasing the picture size. SNR scalability refers to enhancement information to increase the picture quality without increasing + +picture resolution. Spatial scalability refers to enhancement information to increase the picture quality by increasing picture resolution either horizontally, vertically, or both. There is also support for temporal scalability by the use of B-pictures. A B-picture is a scalability enhancement containing pictures that can be bidirectionally predicted from two pictures in a reference layer, one temporally previous to the current picture and one temporally subsequent. B-pictures allows enhancement layer information to be used to increase perceived quality by increasing the picture rate of the displayed enhanced video sequence. This mode can be useful for heterogenous networks with varying bandwidth capacity and also in conjunction with error correction schemes. + +### **3.4.14 Reference Picture Resampling mode** + +A syntax is provided for supporting an optional mode for which the reference picture used for video image prediction is processed by a resampling operation prior to its use in forming a predictor for the current input picture (see also Annex P). This allows efficient dynamic selection of an appropriate image resolution for video encoding, and can also support picture warping for use as a global motion compensator or special-effect generator. + +### **3.4.15 Reduced-Resolution Update mode** + +An optional mode is provided which allows reduced-resolution updates to a reference picture having a higher resolution (see also Annex Q). This mode is expected to be used when encoding a highly active scene, and allows an encoder to increase the picture rate at which moving parts of a scene can be represented, while maintaining a higher resolution representation in more static areas of the scene. + +### **3.4.16 Independent Segment Decoding mode** + +An optional mode is provided which allows a picture to be constructed without any data dependencies which cross GOB or multi-GOB video picture segments or slice boundaries (see also Annex R). This mode provides error robustness by preventing the propagation of erroneous data across the boundaries of the video picture segment areas. + +### **3.4.17 Alternative INTER VLC mode** + +An optional mode is provided which improves the efficiency of INTER picture coding when significant changes are evident in the picture (see also Annex S). This efficiency improvement is obtained by allowing a VLC code originally designed for INTRA pictures to be used for some INTER picture coefficients as well. + +### **3.4.18 Modified Quantization mode** + +An optional mode is provided which improves the bit-rate control ability for encoding, reduces chrominance quantization error, expands the range of representable DCT coefficients, and places certain restrictions on coefficient values (see also Annex T). This mode modifies the semantics of the differential quantization step size parameter of the bitstream by broadening the range of step size changes that can be specified. It also reduces the quantization step size used for chrominance data. The range of DCT coefficient levels is broadened to ensure that any possible coefficient value can be encoded to within the accuracy allowed by the step size. Certain restrictions are also placed on coefficients in this mode to increase error detection performance and minimize decoder complexity. + +## **3.5 Bit rate** + +The transmission clock is provided externally. The video bit rate may be variable. In this Recommendation, no constraints on the video bit rate are given; constraints will be given by the terminal or the network. + +## 3.6 Buffering + +The encoder shall control its output bitstream to comply with the requirements of the hypothetical reference decoder defined in Annex B. Video data shall be provided on every valid clock cycle. This can be ensured by MCBPC stuffing (see Tables 7 and 8) or, when forward error correction is used, also by forward error correction stuffing frames (see Annex H). + +The number of bits created by coding any single picture shall not exceed a maximum value specified by the parameter BPPmaxKb which is measured in units of 1024 bits. The minimum allowable value of the BPPmaxKb parameter depends on the largest picture size that has been negotiated for use in the bitstream (see Table 1). The picture size is measured as the picture width times height for the luminance (Y) component, measured in pixels. An encoder may use a larger value for BPPmaxKb than as specified in Table 1, provided the larger value is first negotiated by external means, for example ITU-T Rec. H.245. + +When the Temporal, SNR, and Spatial Scalability mode (Annex O) is employed, the number of bits sent for each picture in each enhancement layer shall not exceed the maximum value specified by BPPmaxKb. + +**Table 1/H.263 – Minimum BPPmaxKb for different source picture formats** + +| Y picture size in pixels
(= width × height as given in picture header) | Minimum BPPmaxKb | +|-----------------------------------------------------------------------------------|-------------------------| +| up to 25 344 (or QCIF) | 64 | +| 25 360 to 101 376 (or CIF) | 256 | +| 101 392 to 405 504 (or 4CIF) | 512 | +| 405 520 and above | 1024 | + +## 3.7 Symmetry of transmission + +The codec may be used for bidirectional or unidirectional visual communication. + +## 3.8 Error handling + +Error handling should be provided by external means (for example, ITU-T Rec. H.223). If it is not provided by external means (for example, in ITU-T Rec. H.221), the optional error correction code and framing as described in Annex H can be used. + +A decoder can send a command to encode one or more GOBs (or slices if Annex K is employed) of its next picture in INTRA mode with coding parameters such as to avoid buffer overflow. A decoder can also send a command to transmit only non-empty GOB headers if the Slice Structured mode (see Annex K) is not in use. The transmission method for these signals is by external means (for example, ITU-T Rec. H.245). + +## 3.9 Multipoint operation + +Features necessary to support switched multipoint operation are included in Annex C. + +# 4 Source coder + +## 4.1 Source format + +The source coder operates on non-interlaced pictures having a source format which is defined in terms of: + +- 1) the picture format, as determined by the number of pixels per line, the number of lines per picture, and the pixel aspect ratio; and +- 2) the timing between pictures, as determined by the Picture Clock Frequency (PCF). For example, the Common Intermediate Format (CIF) has 352 pixels per line, 288 lines, a pixel aspect ratio of 12:11, and a picture clock frequency of 30 000/1001 pictures per second. + +The source coder operates on non-interlaced pictures occurring at a Picture Clock Frequency (PCF) of 30 000/1001 (approximately 29.97) times per second, termed the CIF PCF. It is also possible to negotiate the use of an optional custom PCF by external means. A custom PCF is given by $1\,800\,000 / (\text{clock divisor} * \text{clock conversion factor})$ where clock divisor can have values of 1 through 127 and clock conversion factor can either be 1000 or 1001. The tolerance on the picture clock frequency is $\pm 50$ ppm. + +Pictures are coded as luminance and two colour difference components ( $Y$ , $C_B$ and $C_R$ ). These components and the codes representing their sampled values are as defined in ITU-R Rec. BT.601-5. + +- Black = 16; +- White = 235; +- Zero colour difference = 128; +- Peak colour difference = 16 and 240. + +These values are nominal ones and the coding algorithm functions with input values of 1 through to 254. + +There are five standardized picture formats: sub-QCIF, QCIF, CIF, 4CIF and 16CIF. It is also possible to negotiate a custom picture format. For all of these picture formats, the luminance sampling structure is $d_x$ pixels per line, $d_y$ lines per picture in an orthogonal arrangement. Sampling of each of the two colour difference components is at $d_x/2$ pixels per line, $d_y/2$ lines per picture, orthogonal. The values of $d_x$ , $d_y$ , $d_x/2$ and $d_y/2$ are given in Table 2 for each of the standardized picture formats. + +**Table 2/H.263 – Number of pixels per line and number of lines for each of the standardized H.263 picture formats** + +| Picture format | Number of pixels for luminance ( $d_x$ ) | Number of lines for luminance ( $d_y$ ) | Number of pixels for chrominance ( $d_x/2$ ) | Number of lines for chrominance ( $d_y/2$ ) | +|----------------|------------------------------------------|-----------------------------------------|----------------------------------------------|---------------------------------------------| +| sub-QCIF | 128 | 96 | 64 | 48 | +| QCIF | 176 | 144 | 88 | 72 | +| CIF | 352 | 288 | 176 | 144 | +| 4CIF | 704 | 576 | 352 | 288 | +| 16CIF | 1408 | 1152 | 704 | 576 | + +For all picture formats, colour difference samples are sited such that their block boundaries coincide with luminance block boundaries as shown in Figure 2. The pixel aspect ratio is the same for each of the standardized picture formats and is the same as defined for QCIF and CIF in ITU-T Rec. H.261: $(288/3):(352/4)$ , which simplifies to 12:11 in relatively prime numbers. The picture + +area covered by all of the standardized picture formats except the sub-QCIF picture format has an aspect ratio of 4:3. + +![Diagram illustrating the positioning of luminance and chrominance samples within a 4x4 block. The block is divided into four 2x2 quadrants by a dashed line representing the block edge. Luminance samples are marked with 'X' and chrominance samples with 'O'. The pattern shows luminance samples at the corners and centers of the 2x2 quadrants, while chrominance samples are positioned at the midpoints of the outer edges of the block.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +X Luminance sample + O Chrominance sample + - - - - Block edge + +T1602690-97 + +Diagram illustrating the positioning of luminance and chrominance samples within a 4x4 block. The block is divided into four 2x2 quadrants by a dashed line representing the block edge. Luminance samples are marked with 'X' and chrominance samples with 'O'. The pattern shows luminance samples at the corners and centers of the 2x2 quadrants, while chrominance samples are positioned at the midpoints of the outer edges of the block. + +**Figure 2/H.263 – Positioning of luminance and chrominance samples** + +Custom picture formats can have a custom pixel aspect ratio as described in Table 3, if the custom pixel aspect ratio use is first negotiated by external means. Custom picture formats can have any number of lines and any number of pixels per line, provided that the number of lines is divisible by four and is in the range [4, ..., 1152], and provided that the number of pixels per line is also divisible by four and is in the range [4, ..., 2048]. For picture formats having a width or height that is not divisible by 16, the picture is decoded in the same manner as if the width or height had the next larger size that would be divisible by 16 and then the picture is cropped at the right and the bottom to the proper width and height for display purposes only. + +**Table 3/H.263 – Custom pixel aspect ratios** + +| Pixel aspect ratio | Pixel width:Pixel height | +|---------------------------|-----------------------------------| +| Square | 1:1 | +| CIF | 12:11 | +| 525-type for 4:3 picture | 10:11 | +| CIF for 16:9 picture | 16:11 | +| 525-type for 16:9 picture | 40:33 | +| Extended PAR | m:n, m and n are relatively prime | + +All decoders and encoders shall be able to operate using the CIF picture clock frequency. Some decoders and encoders may also support custom picture clock frequencies. All decoders shall be able to operate using the sub-QCIF picture format. All decoders shall also be able to operate using the QCIF picture format. Some decoders may also operate with CIF, 4CIF or 16CIF, or custom picture formats. Encoders shall be able to operate with one of the picture formats sub-QCIF and QCIF. The encoders determine which of these two formats are used, and are not obliged to be able to operate with both. Some encoders can also operate with CIF, 4CIF, 16CIF, or custom picture formats. Which optional formats and which picture clock frequencies can be handled by the decoder is signalled by external means, for example ITU-T Rec. H.245. For a complete overview of possible picture formats and video coding algorithms, refer to the terminal description, for example ITU-T Rec. H.324. + +NOTE – For CIF, the number of pixels per line is compatible for practical purposes with sampling the active portions of the luminance and colour difference signals from 525- or 625-line sources at 6.75 and 3.375 MHz respectively. These frequencies have a simple relationship to those in ITU-R Rec. BT.601-5. + +Means shall be provided to restrict the maximum picture rate of encoders by having a minimum number of non-transmitted pictures between transmitted ones. Selection of this minimum number shall be by external means (for example, ITU-T Rec. H.245). For the calculation of the minimum number of non-transmitted pictures in PB-frames mode, the P-picture and the B-picture of a PB-frames unit are taken as two separate pictures. + +## 4.2 Video source coding algorithm + +The source coder is shown in generalized form in Figure 3. The main elements are prediction, block transformation and quantization. + +![Figure 3/H.263 – Source coder block diagram. The diagram shows the flow of video data through various processing blocks. 'Video in' enters from the left and is split: one path goes to a subtraction node (circle with a minus sign), and the other goes to a switch (dashed box with 'o'). The subtraction node also receives input from a 'P' block. The output of the subtraction node goes to a 'T' (Transform) block, which then goes to a 'Q' (Quantizer) block. The 'Q' block outputs 'q' and 'qz'. The 'q' output goes to 'To video multiplex coder' through 'Q^-1' and 'T^-1' blocks, then to an addition node (circle with a plus sign). The 'qz' output goes to a 'CC' (Coding control) block. The 'CC' block outputs 'p' and 't'. The 'CC' block also has a control line to the 'P' block. The 'P' block outputs 'v' (Motion vector) and its output goes to the subtraction node. The 'To video multiplex coder' label is on the right, with a bracket grouping the 'Q^-1', 'T^-1', and addition node outputs. A small label 'T1602700-97' is at the bottom right of the diagram.](10781f43062bf3e9601a1e086710556c_img.jpg) + +Figure 3/H.263 – Source coder block diagram. The diagram shows the flow of video data through various processing blocks. 'Video in' enters from the left and is split: one path goes to a subtraction node (circle with a minus sign), and the other goes to a switch (dashed box with 'o'). The subtraction node also receives input from a 'P' block. The output of the subtraction node goes to a 'T' (Transform) block, which then goes to a 'Q' (Quantizer) block. The 'Q' block outputs 'q' and 'qz'. The 'q' output goes to 'To video multiplex coder' through 'Q^-1' and 'T^-1' blocks, then to an addition node (circle with a plus sign). The 'qz' output goes to a 'CC' (Coding control) block. The 'CC' block outputs 'p' and 't'. The 'CC' block also has a control line to the 'P' block. The 'P' block outputs 'v' (Motion vector) and its output goes to the subtraction node. The 'To video multiplex coder' label is on the right, with a bracket grouping the 'Q^-1', 'T^-1', and addition node outputs. A small label 'T1602700-97' is at the bottom right of the diagram. + +| | | +|----|-------------------------------------------------------| +| T | Transform | +| Q | Quantizer | +| P | Picture Memory with motion compensated variable delay | +| CC | Coding control | +| p | Flag for INTRA/INTER | +| t | Flag for transmitted or not | +| qz | Quantizer indication | +| q | Quantizing index for transform coefficients | +| v | Motion vector | + +**Figure 3/H.263 – Source coder** + +### 4.2.1 GOBs, slices, macroblocks and blocks + +Each picture is divided either into Groups Of Blocks (GOBs) or into slices. + +A Group Of Blocks (GOB) comprises of up to $k * 16$ lines, where $k$ depends on the number of lines in the picture format and depends on whether the optional Reduced-Resolution Update mode is in use (see Annex Q). The dependencies are shown in Table 4. If the number of lines is less than or equal to 400 and the optional Reduced-Resolution Update mode is not in use, then $k = 1$ . If the number of lines is less than or equal to 800 and the optional Reduced-Resolution Update mode is in use or the number of lines is more than 400, then $k = 2$ . If the number of lines is more than 800, then $k = 4$ . When using custom picture sizes, the number of lines in the last (bottom-most) GOB may be less than $k * 16$ if the number of lines in the picture is not divisible by $k * 16$ . However, every GOB in each of the standardized picture formats has $k * 16$ lines, as the number of lines in + +each standardized picture format is an integer multiple of $k * 16$ . Thus, for example, if the optional Reduced-Resolution mode is not in use, the number of GOBs per picture is 6 for sub-QCIF, 9 for QCIF, and 18 for CIF, 4CIF and 16CIF. The GOB numbering is done by use of vertical scan of the GOBs, starting with the upper GOB (number 0) and ending with the bottom-most GOB. An example of the arrangement of GOBs in a picture is given for the CIF picture format in Figure 4. Data for each GOB consists of a GOB header (may be empty) followed by data for macroblocks. Data for GOBs is transmitted per GOB in increasing GOB number. + +**Table 4/H.263 – Parameter k for GOB size definition** + +| Number of Lines $d_y$ | Value of k when not in RRU mode | Value of k when in RRU mode | +|-----------------------|---------------------------------|-----------------------------| +| 4, ... , 400 | 1 | 2 | +| 404, ... , 800 | 2 | 2 | +| 804, ... , 1152 | 4 | 4 | + +The Slice Structured mode is described in Annex K. Slices are similar to GOBs in that they are a multi-macroblock layer of the syntax, but slices have a more flexible shape and usage than GOBs, and slices may appear in the bitstream in any order, under certain conditions. + +| | +|----| +| 0 | +| 1 | +| 2 | +| 3 | +| 4 | +| 5 | +| 6 | +| 7 | +| 8 | +| 9 | +| 10 | +| 11 | +| 12 | +| 13 | +| 14 | +| 15 | +| 16 | +| 17 | + +**Figure 4/H.263 – Arrangement of Groups of Blocks in a CIF picture** + +Each GOB is divided into macroblocks. The macroblock structure depends on whether the optional Reduced-Resolution Update (RRU) mode is in use (see Annex Q). Unless in RRU mode, each macroblock relates to 16 pixels by 16 lines of Y and the spatially corresponding 8 pixels by 8 lines of $C_B$ and $C_R$ . Further, a macroblock consists of four luminance blocks and the two spatially corresponding colour difference blocks as shown in Figure 5. Each luminance or chrominance block + +thus relates to 8 pixels by 8 lines of $Y$ , $C_B$ or $C_R$ . Unless in RRU mode, a GOB comprises one macroblock row for sub-QCIF, QCIF and CIF, two macroblock rows for 4CIF and four macroblock rows for 16CIF. + +![Figure 5/H.263 – Arrangement of blocks in a macroblock. The diagram shows three separate blocks: Y, C_B, and C_R. The Y block is a 2x2 grid of four smaller squares numbered 1, 2, 3, and 4. The C_B and C_R blocks are single large squares numbered 5 and 6 respectively. A small text label 'T1602710-97' is located to the right of the C_R block.](812e188283162af0b54fb3e30ffee51b_img.jpg) + +Figure 5/H.263 – Arrangement of blocks in a macroblock. The diagram shows three separate blocks: Y, C\_B, and C\_R. The Y block is a 2x2 grid of four smaller squares numbered 1, 2, 3, and 4. The C\_B and C\_R blocks are single large squares numbered 5 and 6 respectively. A small text label 'T1602710-97' is located to the right of the C\_R block. + +**Figure 5/H.263 – Arrangement of blocks in a macroblock** + +When in RRU mode, a macroblock relates to 32 pixels by 32 lines of $Y$ and the spatially corresponding 16 pixels by 16 lines of $C_B$ and $C_R$ , and each luminance or chrominance block relates to 16 pixels by 16 lines of $Y$ , $C_B$ or $C_R$ . Furthermore, a GOB comprises one macroblock row for CIF and 4CIF, and two macroblock rows for 16CIF. + +The macroblock numbering is done by use of horizontal scan of the macroblock rows from left to right, starting with the upper macroblock row and ending with the lower macroblock row. Data for the macroblocks is transmitted per macroblock in increasing macroblock number. Data for the blocks is transmitted per block in increasing block number (see Figure 5). + +The criteria for choice of mode and transmitting a block are not subject to recommendation and may be varied dynamically as part of the coding control strategy. Transmitted blocks are transformed and resulting coefficients are quantized and entropy coded. + +### 4.2.2 Prediction + +The primary form of prediction is inter-picture and may be augmented by motion compensation (see 4.2.3). The coding mode in which temporal prediction is applied is called INTER; the coding mode is called INTRA if no temporal prediction is applied. The INTRA coding mode can be signalled at the picture level (INTRA for I-pictures or INTER for P-pictures) or at the macroblock level in P-pictures. In the optional PB-frames mode, B-pictures are always coded in INTER mode. The B-pictures are partly predicted bidirectionally (refer to Annex G). + +In total, H.263 has seven basic picture types (of which only the first two are mandatory) which are defined primarily in terms of their prediction structure: + +- 1) INTRA: A picture having no reference picture(s) for prediction (also called an I-picture); +- 2) INTER: A picture using a temporally previous reference picture (also called a P-picture); +- 3) PB: A frame representing two pictures and having a temporally previous reference picture (see Annex G); +- 4) Improved PB: A frame functionally similar but normally better than a PB-frame (see Annex M); +- 5) B: A picture having two reference pictures, one of which temporally precedes the B-picture and one of which temporally succeeds the B-picture and has the same picture size (see Annex O); +- 6) EI: A picture having a temporally simultaneous reference picture which has either the same or a smaller picture size (see Annex O); and + +- 7) EP: A picture having two reference pictures, one of which temporally precedes the EP-picture and one of which is temporally simultaneous and has either the same or a smaller picture size (see Annex O). + +As used herein, a "reference" or "anchor" picture is a picture that contains data which can be used by reference as a basis for the decoding of another picture. This use by reference is also known as "prediction", although it sometimes may actually indicate use in a reverse-temporal direction. + +### 4.2.3 Motion compensation + +The decoder will accept one vector per macroblock or, if the Advanced Prediction mode or the Deblocking Filter mode is used, one or four vectors per macroblock (see Annexes F and J). If the PB-frames mode is used, one additional delta vector can be transmitted per macroblock for adaptation of the motion vectors for prediction of the B-macroblock. Similarly, an Improved PB-frame macroblock (see Annex M) can include an additional forward motion vector. B-picture macroblocks (see Annex O) can be transmitted together with a forward and a backward motion vector, and EP-pictures can be transmitted with a forward motion vector. + +Both horizontal and vertical components of the motion vectors have integer or half integer values. In the default prediction mode, these values are restricted to the range $[-16, 15.5]$ (this is also valid for the forward and backward motion vector components for B-pictures). + +In the Unrestricted Motion Vector mode, however, the maximum range for vector components is increased. If PLUSPTYPE is absent, the range is $[-31.5, 31.5]$ , with the restriction that only values that are within a range of $[-16, 15.5]$ around the predictor for each motion vector component can be reached if the predictor is in the range $[-15.5, 16]$ . If PLUSPTYPE is absent and the predictor is outside $[-15.5, 16]$ , all values within the range $[-31.5, 31.5]$ with the same sign as the predictor plus the zero value can be reached. If PLUSPTYPE is present, the motion vector values are less restricted (see also Annex D). + +In the Reduced-Resolution Update mode, the motion vector range is enlarged to approximately double size, and each vector component is restricted to have only a half-integer or zero value. Therefore, the range of each motion vector component is $[-31.5, 30.5]$ in the default Reduced-Resolution Update mode (see Annex Q) and a larger range if the Unrestricted Motion Vector mode is also used (see also Annex D). + +A positive value of the horizontal or vertical component of the motion vector signifies that the prediction is formed from pixels in the referenced picture which are spatially to the right or below the pixels being predicted. + +Motion vectors are restricted such that all pixels referenced by them are within the coded picture area, except when the Unrestricted Motion Vector mode, the Advanced Prediction mode, the Advanced Prediction mode, or the Deblocking Filter mode is used (see Annexes D, F and J), or in B- and EP-pictures of the Temporal, SNR, and Spatial Scalability mode (see Annex O). + +### 4.2.4 Quantization + +Unless the optional Advanced INTRA Coding mode or Modified Quantization mode is in use, the number of quantizers is 1 for the first coefficient of INTRA blocks and 31 for all other coefficients. Within a macroblock the same quantizer is used for all coefficients except the first one of INTRA blocks. The decision levels are not defined. The first coefficient of INTRA blocks is nominally the transform dc value uniformly quantized with a step size of 8. Each of the other 31 quantizers use equally spaced reconstruction levels with a central dead-zone around zero and with a step size of an even value in the range 2 to 62. For the exact formulas, refer to 6.2. For quantization using the Advanced INTRA Coding mode, refer to Annex I. For quantization using the Modified Quantization mode, refer to Annex T. + +NOTE – For the smaller quantization step sizes, the full dynamic range of the transform coefficients cannot be represented unless the optional Modified Quantization mode is in use. + +## 4.3 Coding control + +Several parameters may be varied to control the rate of generation of coded video data. These include processing prior to the source coder, the quantizer, block significance criterion and temporal subsampling. The proportions of such measures in the overall control strategy are not subject to recommendation. + +When invoked, temporal subsampling is performed by discarding complete pictures. + +A decoder can signal its preference for a certain tradeoff between spatial and temporal resolution of the video signal. The encoder shall signal its default tradeoff at the beginning of the call and shall indicate whether it is capable of responding to decoder requests to change this tradeoff. The transmission method for these signals is by external means (for example, ITU-T Rec. H.245). + +## 4.4 Forced updating + +This function is achieved by forcing the use of the INTRA mode of the coding algorithm. The update pattern is not defined. To control the accumulation of inverse transform mismatch error, each macroblock shall be coded in INTRA mode at least once every 132 times when coefficients are transmitted for this macroblock in P-pictures. A similar requirement applies when using optional EP-pictures (see Annex O), for which each macroblock shall be coded in an INTRA or upward mode at least once every 132 times when coefficients are transmitted for the macroblock. + +## 4.5 Byte alignment of start codes + +Byte alignment of start codes is achieved by inserting a stuffing codeword consisting of less than 8 zero-bits before the start code such that the first bit of the start code is the first (most significant) bit of a byte. A start code is therefore byte aligned if the position of its most significant bit is a multiple of 8 bits from the first bit in the H.263 bitstream. All picture, slice, and EOSBS start codes shall be byte aligned, and GOB and EOS start codes may be byte aligned. + +NOTE 1 – The number of bits spent for a certain picture is variable but always a multiple of 8 bits. + +NOTE 2 – H.324 requires H.263 encoders to align picture start codes with the start of logical information units passed to the Adaptation Layer (AL\_SDUs). + +# 5 Syntax and semantics + +The video syntax is arranged in a hierarchical structure with four primary layers. From top to bottom the layers are: + +- Picture; +- Group of Blocks, or slice, or video picture segment; +- Macroblock; +- Block. + +The syntax diagram is shown in Figure 6. A guide for interpretation of the diagram consists of the following: + +- 1) Arrow paths show the possible flows of syntax elements. Any syntax element which has zero length is considered absent for arrow path diagramming purposes (thus, for example, there is an arrow path bypassing PSTUF despite the mandatory nature the PSTUF field since the length of the PSTUF field may be zero). +- 2) Abbreviations and semantics for each syntax element are as defined in later clauses. +- 3) The set of syntax elements and arrow paths shown using thick solid lines denotes the syntax flow of the "baseline" mode of operation, without the use of any optional enhancements. (This syntax was also present in the Version 1 of this Recommendation, and remains unchanged in any way.) + +- 4) The set of syntax elements and arrow paths shown using thick dotted lines denotes the additional elements in the syntax flow of the optional enhancements which have been present in both Version 1 and Version 2 of this Recommendation. (This syntax remains unchanged in any way.) +- 5) The set of syntax elements and arrow paths shown using thin solid lines denotes the additional new elements in the syntax flow of the optional enhancements which are specific to the additional optional features added in Version 2. (This syntax was not present in Version 1.) +- 6) Syntax element fields shown with square-edged boundaries indicate fixed-length fields, and those with rounded boundaries indicate variable-length fields. One syntax element (DQUANT) is shown with both types of boundaries, because it can have either a variable or fixed length. +- 7) A fixed-length field is defined to be a field for which the length of the field is not dependent on the data in the content of the field itself. The length of this field is either always the same, or is determined by the prior data in the syntax flow. +- 8) The term "layer" is used to refer to any part of the syntax which can be understood and diagrammed as a distinct entity. + +Unless specified otherwise, the most significant bit is transmitted first. This is bit 1 and is the left most bit in the code tables in this Recommendation. Unless specified otherwise, all unused or spare bits are set to "1". Spare bits shall not be used until their functions are specified by the ITU-T. + +![Syntax diagram for the video bitstream (part 1 of 7). The diagram shows the hierarchical structure of a Picture Layer, starting with PSC, TR, PTYPE, PLUS HEADER, PQUANT, CPM, and then optional elements PSBI, TRB, and DBQUANT. It also branches into PEI, PSUPP, GOB LAYER, SLICE LAYER, ESTUF, EOS, EOSBS, ESBI, and PSTUF.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +``` + +graph TD + subgraph PictureLayer [PICTURE LAYER] + PSC[PSC] --> TR[TR] + TR --> PTYPE([PTYPE]) + PTYPE --> PLUS_HEADER([PLUS HEADER]) + PLUS_HEADER --> PQUANT[PQUANT] + PQUANT --> CPM[CPM] + CPM --> PSBI[PSBI] + PSBI --> TRB[TRB] + TRB --> DBQUANT[DBQUANT] + DBQUANT --> PLUS_HEADER + end + + PSC --> PEI[PEI] + PEI --> PSUPP[PSUPP] + PSUPP --> GOB_LAYER([GOB LAYER]) + PSUPP --> SLICE_LAYER([SLICE LAYER]) + + GOB_LAYER --> ESTUF([ESTUF]) + SLICE_LAYER --> ESTUF + + subgraph ESTUF_Group [ ] + ESTUF --> EOS[EOS] + ESTUF --> EOSBS[EOSBS] + EOSBS --> ESBI[ESBI] + ESBI --> ESTUF + end + + EOS --> PSTUF([PSTUF]) + ESBI --> PSTUF + PSTUF --> PLUS_HEADER + +``` + +T1602720-97 + +Syntax diagram for the video bitstream (part 1 of 7). The diagram shows the hierarchical structure of a Picture Layer, starting with PSC, TR, PTYPE, PLUS HEADER, PQUANT, CPM, and then optional elements PSBI, TRB, and DBQUANT. It also branches into PEI, PSUPP, GOB LAYER, SLICE LAYER, ESTUF, EOS, EOSBS, ESBI, and PSTUF. + +Figure 6/H.263 – Syntax diagram for the video bitstream (part 1 of 7) + +![Syntax diagram for the video bitstream (part 2 of 7). The diagram shows two main paths starting from 'PLUS HEADER' and 'PLUSPTYPE'. The left path from 'PLUS HEADER' goes through 'PLUSPTYPE', 'CPM', 'PSBI', 'CPFMT', 'EPAR', 'CPCFC', 'ETR', 'UUI', and 'SSS'. A large loop on the right side contains 'ELNUM', 'RLNUM', 'RPSMF', 'TRPI', 'TRP', 'BCI', 'BCM LAYER', and 'RPRP LAYER', with various back-edges. The right path from 'PLUSPTYPE' goes through 'UFEP', 'OPPTYPE', and 'MPPTYPE'.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +``` + +graph TD + subgraph PLUS_HEADER [PLUS HEADER] + direction TB + P1[PLUSPTYPE] --> CPM[CPM] + CPM --> PSBI[PSBI] + PSBI --> CPFMT[CPFMT] + CPFMT --> EPAR[EPAR] + EPAR --> CPCFC[CPCFC] + CPCFC --> ETR[ETR] + ETR --> UUI[UUI] + UUI --> SSS[SSS] + end + + subgraph PLUSPTYPE [PLUSPTYPE] + direction TB + UFEP[UFEP] --> OPPTYPE[OPPTYPE] + OPPTYPE --> MPPTYPE[MPPTYPE] + end + + SSS --> ELNUM[ELNUM] + ELNUM --> RLNUM[RLNUM] + RLNUM --> RPSMF[RPSMF] + RPSMF --> TRPI[TRPI] + TRPI --> TRP[TRP] + TRP --> BCI[BCI] + BCI --> BCM_LAYER[BCM LAYER] + BCM_LAYER --> RPRP_LAYER[RPRP LAYER] + RPRP_LAYER --> END[ ] + + %% Back-edges for loops + PSBI -.-> PSBI + CPFMT -.-> PSBI + EPAR -.-> PSBI + EPAR -.-> CPFMT + CPCFC -.-> PSBI + CPCFC -.-> CPFMT + CPCFC -.-> EPAR + ETR -.-> PSBI + ETR -.-> CPFMT + ETR -.-> EPAR + ETR -.-> CPCFC + UUI -.-> PSBI + UUI -.-> CPFMT + UUI -.-> EPAR + UUI -.-> CPCFC + UUI -.-> ETR + SSS -.-> PSBI + SSS -.-> CPFMT + SSS -.-> EPAR + SSS -.-> CPCFC + SSS -.-> ETR + SSS -.-> UUI + + RLNUM -.-> RLNUM + RLNUM -.-> RPSMF + RPSMF -.-> RPSMF + RPSMF -.-> TRPI + TRPI -.-> TRPI + TRPI -.-> TRP + TRP -.-> TRP + TRP -.-> BCI + BCI -.-> BCI + BCI -.-> BCM_LAYER + BCM_LAYER -.-> BCM_LAYER + BCM_LAYER -.-> RPRP_LAYER + RPRP_LAYER -.-> RPRP_LAYER + +``` + +Syntax diagram for the video bitstream (part 2 of 7). The diagram shows two main paths starting from 'PLUS HEADER' and 'PLUSPTYPE'. The left path from 'PLUS HEADER' goes through 'PLUSPTYPE', 'CPM', 'PSBI', 'CPFMT', 'EPAR', 'CPCFC', 'ETR', 'UUI', and 'SSS'. A large loop on the right side contains 'ELNUM', 'RLNUM', 'RPSMF', 'TRPI', 'TRP', 'BCI', 'BCM LAYER', and 'RPRP LAYER', with various back-edges. The right path from 'PLUSPTYPE' goes through 'UFEP', 'OPPTYPE', and 'MPPTYPE'. + +T1602730-97 + +Figure 6/H.263 – Syntax diagram for the video bitstream (part 2 of 7) + +![Syntax diagram for the video bitstream (part 3 of 7) showing the flow from GOB LAYER through various processing blocks like GSTUF, GBSC, GN, GSBI, GFID, GQUANT, TRI, TR, TRPI, TRP, BCI, BCM LAYER, and MB LAYER.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +``` + +graph TD + GOB[GOB LAYER] --> GSTUF_Start[ ] + GSTUF_Start --> GSTUF([GSTUF]) + GSTUF --> GSTUF + GSTUF --> GBSC[GBSC] + GBSC --> GN[GN] + GN --> GSBI_Start[ ] + GSBI_Start --> GSBI([GSBI]) + GSBI --> GSBI + GSBI --> GFID[GFID] + GFID --> GQUANT[GQUANT] + GQUANT --> MB_Join[ ] + + GSTUF_Start --> TRI[TRI] + TRI --> TR_Start[ ] + TR_Start --> TR([TR]) + TR --> TR + TR --> TRPI[TRPI] + TRPI --> TRP_Start[ ] + TRP_Start --> TRP([TRP]) + TRP --> TRP + TRP --> BCI([BCI]) + BCI --> BCM([BCM LAYER]) + BCM --> MB_Join + + TR_Start --> MB_Join + TRP_Start --> MB_Join + + MB_Join --> MB([MB LAYER]) + MB --> MB + MB --> GSTUF_Start + MB --> End[ ] + + style GSTUF_Start fill:none,stroke:none + style GSBI_Start fill:none,stroke:none + style TR_Start fill:none,stroke:none + style TRP_Start fill:none,stroke:none + style MB_Join fill:none,stroke:none + style End fill:none,stroke:none + +``` + +The diagram illustrates the syntax structure of a video bitstream. It begins with the **GOB LAYER** at the top. The flow then splits into two parallel processing paths. The left path consists of a sequence of blocks: **GSTUF** (rounded rectangle with a loop), **GBSC**, **GN**, **GSBI** (rounded rectangle with a loop), **GFID**, and **GQUANT**. The right path consists of **TRI**, **TR** (rounded rectangle with a loop), **TRPI**, **TRP** (rounded rectangle with a loop), **BCI** (rounded rectangle), and **BCM LAYER** (rounded rectangle). There are bypass paths from before TR and before TRP that lead directly to the MB LAYER. Both main paths converge to the **MB LAYER** (rounded rectangle with a loop) at the bottom. A feedback loop returns from after the MB LAYER to the start of the processing paths. A small code **T1602740-97** is visible near the bottom right. + +Syntax diagram for the video bitstream (part 3 of 7) showing the flow from GOB LAYER through various processing blocks like GSTUF, GBSC, GN, GSBI, GFID, GQUANT, TRI, TR, TRPI, TRP, BCI, BCM LAYER, and MB LAYER. + +**Figure 6/H.263 – Syntax diagram for the video bitstream (part 3 of 7)** + +![Syntax diagram for the video bitstream (part 4 of 7). The diagram shows two vertical columns of elements. The left column starts with SLICE LAYER and contains SSTUF, SSC, SEPB1, SSBI, MBA, SEPB2, SQUANT, SWI, SEPB3, and GFID. The right column contains TRI, TR, TRPI, TRP, BCI, BCM LAYER, and MB LAYER. Arrows indicate the flow and optional repetitions between elements.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +``` + +graph TD + SLICE_LAYER[SLICE LAYER] --> SSTUF + subgraph LeftColumn [ ] + SSTUF --> SSC + SSC --> SEPB1 + SEPB1 --> SSBI + SSBI --> MBA + MBA --> SEPB2 + SEPB2 --> SQUANT + SQUANT --> SWI + SWI --> SEPB3 + SEPB3 --> GFID + end + subgraph RightColumn [ ] + TRI --> TR + TR --> TRPI + TRPI --> TRP + TRP --> BCI + BCI --> BCM_LAYER[BCM LAYER] + BCM_LAYER --> MB_LAYER[MB LAYER] + end + SSTUF -.-> SSTUF + SSC -.-> SSC + SSBI -.-> SSBI + SEPB2 -.-> SEPB2 + SQUANT -.-> SQUANT + SWI -.-> SWI + TR -.-> TR + TRP -.-> TRP + GFID -.-> GFID + GFID --> MB_LAYER + MB_LAYER --> End(( )) + style LeftColumn fill:none,stroke:none + style RightColumn fill:none,stroke:none + +``` + +Syntax diagram for the video bitstream (part 4 of 7). The diagram shows two vertical columns of elements. The left column starts with SLICE LAYER and contains SSTUF, SSC, SEPB1, SSBI, MBA, SEPB2, SQUANT, SWI, SEPB3, and GFID. The right column contains TRI, TR, TRPI, TRP, BCI, BCM LAYER, and MB LAYER. Arrows indicate the flow and optional repetitions between elements. + +T1602750-97 + +Figure 6/H.263 – Syntax diagram for the video bitstream (part 4 of 7) + +![Syntax diagram for the video bitstream (part 5 of 7). The diagram shows three main vertical paths. The left path starts with 'BCM SEPARATE LOGICAL CHANNEL LAYER' leading to 'External framing', then 'BCM LAYER', and 'BSTUF' with a self-loop. The middle path starts with 'BCM LAYER' leading to a sequence of blocks: 'BT', 'URF', 'TR', 'ELNUMI', and 'ELNUM' with a self-loop. The right path starts with 'BCM LAYER' leading to 'BCPM', then 'BSBI', 'BEPB1', 'GN/MBA', 'BEPB2', and 'RTR' with a self-loop. Arrows indicate the flow and loops between these elements.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +graph TD + subgraph BCM_SEPARATE_LOGICAL_CHANNEL_LAYER [BCM SEPARATE LOGICAL CHANNEL LAYER] + EF[External framing] + end + subgraph BCM_LAYER_1 [BCM LAYER] + BL1([BCM LAYER]) + end + subgraph BSTUF [BSTUF] + BS([BSTUF]) + end + subgraph BCM_LAYER_2 [BCM LAYER] + BL2([BCM LAYER]) + end + subgraph BT [BT] + BT[BT] + end + subgraph URF [URF] + URF[URF] + end + subgraph TR [TR] + TR[TR] + end + subgraph ELNUMI [ELNUMI] + ELNUMI[ELNUMI] + end + subgraph ELNUM [ELNUM] + ELNUM[ELNUM] + end + subgraph BCPM [BCPM] + BCPM[BCPM] + end + subgraph BSBI [BSBI] + BSBI[BSBI] + end + subgraph BEPB1 [BEPB1] + BEPB1[BEPB1] + end + subgraph GN_MBA [GN/MBA] + GN_MBA[GN/MBA] + end + subgraph BEPB2 [BEPB2] + BEPB2[BEPB2] + end + subgraph RTR [RTR] + RTR[RTR] + end + + EF --> BL1 + BL1 --> BS + BS --> EF + BL2 --> BT + BT --> URF + URF --> TR + TR --> ELNUMI + ELNUMI --> ELNUM + ELNUM --> ELNUM + ELNUM --> BCPM + BCPM --> BSBI + BSBI --> BSBI + BSBI --> BEPB1 + BEPB1 --> BEPB1 + BEPB1 --> GN_MBA + GN_MBA --> BEPB2 + BEPB2 --> BEPB2 + BEPB2 --> RTR + RTR --> RTR + RTR --> T1602760-97[T1602760-97] + +``` + +Syntax diagram for the video bitstream (part 5 of 7). The diagram shows three main vertical paths. The left path starts with 'BCM SEPARATE LOGICAL CHANNEL LAYER' leading to 'External framing', then 'BCM LAYER', and 'BSTUF' with a self-loop. The middle path starts with 'BCM LAYER' leading to a sequence of blocks: 'BT', 'URF', 'TR', 'ELNUMI', and 'ELNUM' with a self-loop. The right path starts with 'BCM LAYER' leading to 'BCPM', then 'BSBI', 'BEPB1', 'GN/MBA', 'BEPB2', and 'RTR' with a self-loop. Arrows indicate the flow and loops between these elements. + +Figure 6/H.263 – Syntax diagram for the video bitstream (part 5 of 7) + +![Syntax diagram for the video bitstream (part 6 of 7). The diagram shows the flow from RPRP LAYER to WDA, then branching into 'All other pictures' (MVD, FILL_MODE, Y_FILL, CB_EPB, CB_FILL, CR_EPB, CR_FILL) and 'EP SNR pictures' (WPRB).](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +``` + +graph TD + RPRP[RPRP LAYER] --> WDA[WDA] + WDA --> AllOther[All other pictures] + WDA --> EPSNR[EP SNR pictures] + AllOther --> MVD([MVD]) + MVD --> FILL_MODE[FILL_MODE] + FILL_MODE --> Y_FILL[Y_FILL] + Y_FILL --> CB_EPB[CB_EPB] + CB_EPB --> CB_FILL[CB_FILL] + CB_FILL --> CR_EPB[CR_EPB] + CR_EPB --> CR_FILL[CR_FILL] + CR_FILL --> Join1(( )) + EPSNR --> EPSpatial[EP spatial pictures] + EPSpatial --> WPRB[WPRB] + WPRB --> Join2(( )) + Join1 --> Join2 + Join2 --> End[ ] + style End fill:none,stroke:none + +``` + +T1602770-97 + +Syntax diagram for the video bitstream (part 6 of 7). The diagram shows the flow from RPRP LAYER to WDA, then branching into 'All other pictures' (MVD, FILL\_MODE, Y\_FILL, CB\_EPB, CB\_FILL, CR\_EPB, CR\_FILL) and 'EP SNR pictures' (WPRB). + +**Figure 6/H.263 – Syntax diagram for the video bitstream (part 6 of 7)** + +![Syntax diagram for the video bitstream (part 7 of 7) showing the hierarchy of macroblock (MB) layers for different picture types.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +The diagram illustrates the syntax structure for the video bitstream, starting from the **MB LAYER**. It branches into three main paths based on picture type: + +- I and P pictures, PB and Improved PB frames:** This path starts with **COD**, followed by **MCBPC**, **INTRA\_MODE**, **MODB** (optional), **CBPB** (optional), **CBPY**, **DQUANT**, **MVD**, **MVD2,4** (optional), **MVDB** (optional), and finally **BLOCK LAYER**. There are feedback loops from **MCBPC** to **COD**, **INTRA\_MODE** to **MODB**, **MODB** to **CBPB**, **CBPB** to **CBPY**, **DQUANT** to **MVD**, **MVD** to **MVD2,4**, **MVD2,4** to **MVDB**, and **MVDB** to **BLOCK LAYER**. +- B and EP pictures:** This path starts with **COD**, followed by **MBTYPE**, **INTRA\_MODE**, **CBPC**, **CBPY**, **DQUANT**, **MVDFW**, **MVDBW**, and finally **BLOCK LAYER**. There are feedback loops from **MBTYPE** to **COD**, **INTRA\_MODE** to **CBPC**, **CBPC** to **CBPY**, **CBPY** to **DQUANT**, **DQUANT** to **MVDFW**, **MVDFW** to **MVDBW**, and **MVDBW** to **BLOCK LAYER**. +- EI pictures:** This path starts with **COD**, followed by **MCBPC**, **INTRA\_MODE**, **CBPY**, **DQUANT**, and finally **BLOCK LAYER**. There are feedback loops from **MCBPC** to **COD**, **INTRA\_MODE** to **CBPY**, **CBPY** to **DQUANT**, and **DQUANT** to **BLOCK LAYER**. + +Below the third path, there is a separate **BLOCK LAYER** box, followed by **INTRA DC** and **TCOEFF**, with feedback loops from **INTRA DC** to **TCOEFF** and from **TCOEFF** back to the input of **INTRA DC**. + +Syntax diagram for the video bitstream (part 7 of 7) showing the hierarchy of macroblock (MB) layers for different picture types. + +T1602780-97 + +Figure 6/H.263 – Syntax diagram for the video bitstream (part 7 of 7) + +## 5.1 Picture layer + +Data for each picture consists of a picture header followed by data for Group of Blocks or for slices, eventually followed by an optional end-of-sequence code and stuffing bits. The structure is shown in Figure 7 for pictures that do not include the optional PLUSPTYPE data field. PSBI is only present if indicated by CPM. TRB and DBQUANT are only present if PTYPE indicates use of the "PB-frame" mode (unless the PLUSPTYPE field is present and the use of DBQUANT is indicated therein). + +The optional PLUSPTYPE data field is present when so indicated in bits 6-8 of PTYPE. When present, an additional set of data is included in the bitstream, which immediately follows PTYPE and precedes PQUANT. In addition, the CPM and PSBI fields are moved forward in the picture header when PLUSPTYPE is present, so that they appear immediately after PLUSPTYPE rather than being located after PQUANT. The format for the additional data following PLUSPTYPE is shown in Figure 8. All fields in this additional picture header data after PLUSPTYPE are optional, depending on whether their presence is indicated in PLUSPTYPE. When the Slice Structured mode (see Annex K) is in use, slices are substituted for GOBs in the location shown in Figure 7. + +Combinations of PSUPP and PEI may not be present, and may be repeated when present. EOS and EOSBS+ESBI may not be present, while ESTUF may be present only if EOS or EOSBS is present. EOS shall not be repeated unless at least one picture start code appears between each pair of EOS codes. Picture headers for dropped pictures are not transmitted. + +![Figure 7: Structure of picture layer (without optional PLUSPTYPE-related fields). The diagram shows a sequence of fields: PSC, TR, PTYPE, PQUANT, CPM, PSBI, TRB, DBQUANT, PEI, PSUPP, PEI, GOBs, ESTUF, EOS, PSTUF. A bracket above the first nine fields (PSC to PEI) indicates they form the main picture header. A bracket above the last five fields (PSUPP to PSTUF) indicates they form the optional end-of-sequence and stuffing bits.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +T1602790-97 + +Figure 7: Structure of picture layer (without optional PLUSPTYPE-related fields). The diagram shows a sequence of fields: PSC, TR, PTYPE, PQUANT, CPM, PSBI, TRB, DBQUANT, PEI, PSUPP, PEI, GOBs, ESTUF, EOS, PSTUF. A bracket above the first nine fields (PSC to PEI) indicates they form the main picture header. A bracket above the last five fields (PSUPP to PSTUF) indicates they form the optional end-of-sequence and stuffing bits. + +**Figure 7/H.263 – Structure of picture layer (without optional PLUSPTYPE-related fields)** + +![Figure 8: Structure of optional PLUSPTYPE-related fields. The diagram shows a sequence of fields: PLUSPTYPE, CPM, PSBI, CPFMT, EPAR, CPCFC, ETR, UUI, SSS. Below this, a bracket groups ELNUM, RLNUM, RPSMF, TRPI, TRP, BCI, BCM, and RPRP. Arrows indicate that PLUSPTYPE points to CPM, PSBI, and CPFMT. CPM points to PSBI. PSBI points to CPFMT. CPFMT points to EPAR. EPAR points to CPCFC. CPCFC points to ETR. ETR points to UUI. UUI points to SSS. SSS points to ELNUM. ELNUM points to RLNUM. RLNUM points to RPSMF. RPSMF points to TRPI. TRPI points to TRP. TRP points to BCI. BCI points to BCM. BCM points to RPRP. RPRP points to an ellipsis.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +T1605280-98 + +Figure 8: Structure of optional PLUSPTYPE-related fields. The diagram shows a sequence of fields: PLUSPTYPE, CPM, PSBI, CPFMT, EPAR, CPCFC, ETR, UUI, SSS. Below this, a bracket groups ELNUM, RLNUM, RPSMF, TRPI, TRP, BCI, BCM, and RPRP. Arrows indicate that PLUSPTYPE points to CPM, PSBI, and CPFMT. CPM points to PSBI. PSBI points to CPFMT. CPFMT points to EPAR. EPAR points to CPCFC. CPCFC points to ETR. ETR points to UUI. UUI points to SSS. SSS points to ELNUM. ELNUM points to RLNUM. RLNUM points to RPSMF. RPSMF points to TRPI. TRPI points to TRP. TRP points to BCI. BCI points to BCM. BCM points to RPRP. RPRP points to an ellipsis. + +**Figure 8/H.263 – Structure of optional PLUSPTYPE-related fields +(located immediately after PTYPE when present)** + +### 5.1.1 Picture Start Code (PSC) (22 bits) + +PSC is a word of 22 bits. Its value is 0000 0000 0000 0000 1 00000. All picture start codes shall be byte aligned. This shall be achieved by inserting PSTUF bits as necessary before the start code such that the first bit of the start code is the first (most significant) bit of a byte. + +### 5.1.2 Temporal Reference (TR) (8 bits) + +The value of TR is formed by incrementing its value in the temporally previous reference picture header by one plus the number of skipped or non-reference pictures at the picture clock frequency since the previously transmitted one. The interpretation of TR depends on the active picture clock frequency. Under the standard CIF picture clock frequency, TR is an 8-bit number which can have + +256 possible values. The arithmetic is performed with only the eight LSBs. If a custom picture clock frequency is signalled in use, Extended TR in 5.1.8 and TR form a 10-bit number where TR stores the eight Least Significant Bits (LSBs) and ETR stores the two Most Significant Bits (MSBs). The arithmetic in this case is performed with the ten LSBs. In the optional PB-frames or Improved PB-frames mode, TR only addresses P-pictures; for the temporal reference for the B-picture part of PB or Improved PB frames, refer to 5.1.22. + +### 5.1.3 Type Information (PTYPE) (Variable Length) + +Information about the complete picture: + +- Bit 1: Always "1", in order to avoid start code emulation. +- Bit 2: Always "0", for distinction with ITU-T Rec. H.261. +- Bit 3: Split screen indicator, "0" off, "1" on. +- Bit 4: Document camera indicator, "0" off, "1" on. +- Bit 5: Full Picture Freeze Release, "0" off, "1" on. +- Bits 6-8: Source Format, "000" forbidden, "001" sub-QCIF, "010" QCIF, "011" CIF, "100" 4CIF, "101" 16CIF, "110" reserved, "111" extended PTYPE. + +If bits 6-8 are not equal to "111", which indicates an extended PTYPE (PLUSPTYPE), the following five bits are also present in PTYPE: + +- Bit 9: Picture Coding Type, "0" INTRA (I-picture), "1" INTER (P-picture). +- Bit 10: Optional Unrestricted Motion Vector mode (see Annex D), "0" off, "1" on. +- Bit 11: Optional Syntax-based Arithmetic Coding mode (see Annex E), "0" off, "1" on. +- Bit 12: Optional Advanced Prediction mode (see Annex F), "0" off, "1" on. +- Bit 13: Optional PB-frames mode (see Annex G), "0" normal I- or P-picture, "1" PB-frame. + +Split screen indicator is a signal that indicates that the upper and lower half of the decoded picture could be displayed side by side. This bit has no direct effect on the encoding or decoding of the picture. + +Full Picture Freeze Release is a signal from an encoder which responds to a request for packet retransmission (if not acknowledged) or fast update request (see also Annex C) or picture freeze request (see also Annex L) and allows a decoder to exit from its freeze picture mode and display the decoded picture in the normal manner. + +If bits 6-8 indicate a different source format than in the previous picture header, the current picture shall be an I-picture, unless an extended PTYPE is indicated in bits 6-8 and the capability to use the optional Reference Picture Resampling mode (see Annex P) has been negotiated externally (for example, ITU-T Rec. H.245). + +Bits 10-13 refer to optional modes that are only used after negotiation between encoder and decoder (see also Annexes D, E, F and G, respectively). If bit 9 is set to "0", bit 13 shall be set to "0" as well. + +Bits 6-8 shall not have a value of "111" which indicates the presence of an extended PTYPE (PLUSPTYPE) unless the capability has been negotiated externally (for example, ITU-T Rec. H.245) to allow the use of a custom source format or one or more of the other optional modes available only by the use of an extended PTYPE (see Annexes I through K and M through T). Whenever bit 6-8 do not have a value of "111", all of the additional modes available only by the use of an extended PTYPE shall be considered to have been set to an "off" state and shall be inferred to remain "off" unless explicitly switched on later in the bitstream. + +### 5.1.4 Plus PTYPE (PLUSPTYPE) (Variable Length) + +A codeword of 12 or 30 bits which is present only if the presence of extended PTYPE is indicated in bits 6-8 of PTYPE. + +PLUSPTYPE is comprised of up to three subfields: UFEP, OPPTYPE, and MPPTYPE. OPPTYPE is present only if UFEP has a particular value. + +#### 5.1.4.1 Update Full Extended PTYPE (UFEP) (3 bits) + +A fixed length codeword of 3 bits which is present only if "extended PTYPE" is indicated in PTYPE bits 6-8. When set to "000", it indicates that only those extended PTYPE fields which need to be signalled in every picture header (MPPTYPE) are included in the current picture header. When set to "001", it indicates that all extended PTYPE fields are included in the current picture header. If the picture type is INTRA or EI, this field shall be set to "001". + +In addition, if PLUSPTYPE is present in each of a continuing sequence of pictures, this field shall be set to "001" at least as often as specified by a five-second or five-picture timeout period, whichever allows a larger interval of time. More specifically, the timeout period requires UFEP = "001" to appear in the PLUSPTYPE field (if PLUSPTYPE is present in every intervening picture) of the first picture header with temporal reference indicating a time interval greater than or equal to five seconds since the last occurrence of UFEP = "001", or of the fifth picture after the last occurrence of UFEP = "001" (whichever requirement allows a longer period of time as measured by temporal reference). + +Encoders should set UFEP to "001" more often in error-prone environments. Values of UFEP other than "000" and "001" are reserved. + +#### 5.1.4.2 The Optional Part of PLUSPTYPE (OPPTYPE) (18 bits) + +If UFEP is "001", then the following bits are present in PLUSPTYPE: + +- Bits 1-3 Source Format, "000" reserved, "001" sub-QCIF, "010" QCIF, "011" CIF, "100" 4CIF, "101" 16CIF, "110" custom source format, "111" reserved; +- Bit 4 Optional Custom PCF, "0" CIF PCF, "1" custom PCF; +- Bit 5 Optional Unrestricted Motion Vector (UMV) mode (see Annex D), "0" off, "1" on; +- Bit 6 Optional Syntax-based Arithmetic Coding (SAC) mode (see Annex E), "0" off, "1" on; +- Bit 7 Optional Advanced Prediction (AP) mode (see Annex F), "0" off, "1" on; +- Bit 8 Optional Advanced INTRA Coding (AIC) mode (see Annex I), "0" off, "1" on; +- Bit 9 Optional Deblocking Filter (DF) mode (see Annex J), "0" off, "1" on; +- Bit 10 Optional Slice Structured (SS) mode (see Annex K), "0" off, "1" on; +- Bit 11 Optional Reference Picture Selection (RPS) mode (see Annex N), "0" off, "1" on; +- Bit 12 Optional Independent Segment Decoding (ISD) mode (see Annex R), "0" off, "1" on; +- Bit 13 Optional Alternative INTER VLC (AIV) mode (see Annex S), "0" off, "1" on; +- Bit 14 Optional Modified Quantization (MQ) mode (see Annex T), "0" off, "1" on; +- Bit 15 Equal to "1" to prevent start code emulation; +- Bit 16 Reserved, shall be equal to "0"; +- Bit 17 Reserved, shall be equal to "0"; +- Bit 18 Reserved, shall be equal to "0". + +#### 5.1.4.3 The mandatory part of PLUSPTYPE when PLUSPTYPE present (MPPTYPE) (9 bits) + +Regardless of the value of UFEP, the following 9 bits are also present in PLUSPTYPE: + +- Bits 1-3 Picture Type Code: + - "000" I-picture (INTRA); + - "001" P-picture (INTER); + - "010" Improved PB-frame (see Annex M); + - "011" B-picture (see Annex O); + - "100" EI-picture (see Annex O); + - "101" EP-picture (see Annex O); + - "110" Reserved; + - "111" Reserved; +- Bit 4 Optional Reference Picture Resampling (RPR) mode (see Annex P), "0" off, "1" on; +- Bit 5 Optional Reduced-Resolution Update (RRU) mode (see Annex Q), "0" off, "1" on; +- Bit 6 Rounding Type (RTYPE) (see 6.1.2); +- Bit 7 Reserved, shall be equal to "0"; +- Bit 8 Reserved, shall be equal to "0"; +- Bit 9 Equal to "1" to prevent start code emulation. + +The encoder should control the rounding type so that P-pictures, Improved PB-frames, and EP-pictures have different values for bit 6 (Rounding Type for P-pictures) from their reference pictures for motion compensation. Bit 6 can have an arbitrary value if the reference picture is an I- or an EI-picture. Bit 6 can be set to "1" only when bits 1-3 indicate a P-picture, Improved PB-frame, or EP-picture. For other types of pictures, this bit shall always be set to "0". + +#### 5.1.4.4 The semantics of PLUSPTYPE + +The mandatory part of PLUSPTYPE consists of features which are likely to be changed on a picture-by-picture basis. Primarily, these are the bits that indicate the picture type among I, P, Improved PB, B, EI, and EP. (Note that the PB-frames mode of Annex G cannot be used with PLUSPTYPE present – the Improved PB-frames mode of Annex M should be used instead.) However, they also include indications for the use of the RPR and RRU modes, as these may change from picture to picture as well. + +Features that are likely to remain in use rather than being changed from one picture to another (except in obvious ways as discussed in 5.1.4.5) have been placed in the optional part of PLUSPTYPE. When UFEP is 000, the missing mode information is inferred from the type of picture and from the mode information sent in a previous PLUSPTYPE with UFEP equal to 001. + +If PLUSPTYPE is present but UFEP is 000, then: + +- 1) For a P-picture or Improved PB-frame (see Annex M), the pixel aspect ratio, picture width, and picture height are unchanged from those of the reference picture. +- 2) For a temporal-scalability B-picture (see Annex O) in an enhancement layer, the Reference Layer Number (RLNUM) is the same as the Enhancement Layer Number (ELNUM) if the last picture sent in the enhancement layer was an EI- or EP-picture. If the last picture sent in the enhancement layer was a B-picture, the reference layer number is the same as the reference layer number of the last B-picture. The pixel aspect ratio, picture width and + +picture height are unchanged from those of the temporally subsequent reference layer picture. + +Note that if temporally surrounding EI- or EP-pictures exist in the same enhancement layer as the B-picture, RLNUM (explicit or implied) shall always be equal to ELNUM. Note also that the pixel aspect ratio, picture width and picture height of a B-picture (explicit or implied) shall always be equal to those of its temporally subsequent reference layer picture. + +- 3) For a SNR/Spatial scalability EP-picture (see Annex O), the pixel aspect ratio, picture width and picture height are unchanged from those of the temporally previous reference picture in the same enhancement layer. + +#### **5.1.4.5 Mode restrictions for certain picture types and mode inference rules** + +Certain modes do not apply to certain types of pictures. Particularly, these restrictions apply: + +- 1) The following modes do not apply within I (INTRA) pictures: Unrestricted Motion Vector (see Annex D), Advanced Prediction (see Annex F), Alternative INTER VLC (see Annex S), Reference Picture Resampling (see Annex P), and Reduced-Resolution Update (see Annex Q). +- 2) The following modes do not apply within B-pictures (see Annex O): Syntax-based Arithmetic Coding (see Annex E), Deblocking Filter (see Annex J), and Advanced Prediction (see Annex F). +- 3) The following modes do not apply within EI-pictures (see Annex O): Unrestricted Motion Vector (see Annex D), Syntax-based Arithmetic Coding (see Annex E), Advanced Prediction (see Annex F), Reference Picture Resampling (see Annex P), Reduced-Resolution Update (see Annex Q), and Alternative INTER VLC (see Annex S). +- 4) The following modes do not apply within EP-pictures (see Annex O): Syntax-based Arithmetic Coding (see Annex E) and Advanced Prediction (see Annex F). + +One or more of the modes listed in the above four-item list may have a mode flag having a value "1" in the optional part of PLUSPTYPE within a picture of a type that is prohibited for that mode (types I, B, EI, or EP). This condition is allowed and shall be interpreted subject to the mode inference rules which follow in the next paragraph. + +Mode states are subject to the following mode inference rules: + +- 1) Once a mode flag has been set to "1" in the optional part of PLUSPTYPE, the current picture and each subsequent picture in the bitstream shall be assigned a state of "on" for that mode. +- 2) An inferred state of "off" shall be assigned to any mode which does not apply within a picture having the current picture type code. However, each subsequent picture in the bitstream shall have an inferred state of "on" for that mode (unless this too results in an obvious conflict – which shall be resolved in the same way). In the case of layered scalable bitstreams (see Annex O), the mode state shall be inferred only from within the same layer of the bitstream. +- 3) The inference of state shall continue until a picture in the same layer that either contains the optional part of PLUSPTYPE or does not contain PLUSPTYPE at all is sent. If a new picture containing the optional part of PLUSPTYPE is sent, the state sent in the new message shall override the old state. If a picture is sent which does not contain PLUSPTYPE (a picture in which bits 6-8 of PTYPE is not "111"), a state of "off" shall be assigned to all modes not explicitly set to "on" in the PTYPE field, and all modes shall continue to have an inferred state of "off" until a new picture containing the optional part of PLUSPTYPE is sent. + +- 4) Two modes do not require mode state inference, since the mode flags for these modes appear in the mandatory part of PLUSPTYPE. These are the Reference Picture Resampling mode (Annex P) and the Reduced-Resolution Update mode (Annex Q). The mode flag for either of these modes shall not be set unless the current picture allows the use of the mode. For example, the Reduced-Resolution Update mode bit shall not be set in an INTRA picture. + +#### 5.1.4.6 Mode interaction restrictions + +Certain modes cannot be used in combination with certain other modes. + +- 1) The Syntax-based Arithmetic Coding mode (see Annex E) shall not be used with the Alternative INTER VLC mode (see Annex S) or the Modified Quantization mode (see Annex T). +- 2) If PLUSPTYPE is present, the Unrestricted Motion Vector mode (see Annex D) shall not be used with the Syntax-based Arithmetic Coding mode (see Annex E). +- 3) The Independent Segment Decoding mode (see Annex R) shall not be used with the Reference Picture Resampling mode (see Annex P). +- 4) The Independent Segment Decoding mode (see Annex R) shall not be used with the Slice Structured mode without the simultaneous use of the Rectangular Slice submode of the Slice Structured mode (see Annex K). + +#### 5.1.4.7 The picture header location of CPM (1 bit) and PSBI (2 bits) + +The location of the CPM and PSBI fields in the picture header depends on whether or not PLUSPTYPE is present (see 5.1.20 and 5.1.21). If PLUSPTYPE is present, then CPM follows immediately after PLUSPTYPE in the picture header. If PLUSPTYPE is not present, then CPM follows immediately after PQUANT in the picture header. PSBI always follows immediately after CPM (if CPM = "1"). + +### 5.1.5 Custom Picture Format (CPFMT) (23 bits) + +A fixed length codeword of 23 bits that is present only if the use of a custom picture format is signalled in PLUSPTYPE and UFEP is '001'. When present, CPFMT consists of: + +- Bits 1-4 Pixel Aspect Ratio Code: A 4-bit index to the PAR value in Table 5. For extended PAR, the exact pixel aspect ratio shall be specified in EPAR (see 5.1.6); +- Bits 5-13 Picture Width Indication: Range [0, ... , 511]; Number of pixels per line = (PWI + 1) \* 4; +- Bit 14 Equal to "1" to prevent start code emulation; +- Bits 15-23 Picture Height Indication: Range [1, ... , 288]; Number of lines = PHI \* 4. + +**Table 5/H.263 – PAR code definition** + +| PAR code | Pixel aspect ratios | +|-----------|---------------------------------------------| +| 0000 | Forbidden | +| 0001 | 1:1 (Square) | +| 0010 | 12:11 (CIF for 4:3 picture) | +| 0011 | 10:11 (525-type for 4:3 picture) | +| 0100 | 16:11 (CIF stretched for 16:9 picture) | +| 0101 | 40:33 (525-type stretched for 16:9 picture) | +| 0110-1110 | Reserved | +| 1111 | Extended PAR | + +### **5.1.6 Extended Pixel Aspect Ratio (EPAR) (16 bits)** + +A fixed length codeword of 16 bits that is present only if CPFMT is present and extended PAR is indicated therein. When present, EPAR consists of: + +- Bits 1-8 PAR Width: "0" is forbidden. The natural binary representation of the PAR width; +- Bits 9-16 PAR Height: "0" is forbidden. The natural binary representation of the PAR height. + +The PAR Width and PAR Height shall be relatively prime. + +### **5.1.7 Custom Picture Clock Frequency Code (CPCFC) (8 bits)** + +A fixed length codeword of 8 bits that is present only if PLUSPTYPE is present and UFEP is 001 and a custom picture clock frequency is signalled in PLUSPTYPE. When present, CPCFC consists of: + +- Bit 1 Clock Conversion Code: "0" indicates a clock conversion factor of 1000 and "1" indicates 1001; +- Bits 2-8 Clock Divisor: "0" is forbidden. The natural binary representation of the value of the clock divisor. + +The custom picture clock frequency is given by $1\,800\,000 / (\text{clock divisor} * \text{clock conversion factor})$ Hz. + +The temporal reference counter shall count in units of the inverse of the picture clock frequency, in seconds. When the PCF changes from that specified for the previous picture, the temporal reference for the current picture is measured in terms of the prior PCF, so that the new PCF takes effect only for the temporal reference interpretation of future pictures. + +### **5.1.8 Extended Temporal Reference (ETR) (2 bits)** + +A fixed length codeword of 2 bits which is present only if a custom picture clock frequency is in use (regardless of the value of UFEP). It is the two MSBs of the 10-bit number defined in 5.1.2. + +### **5.1.9 Unlimited Unrestricted Motion Vectors Indicator (UUI) (Variable length)** + +A variable length codeword of 1 or 2 bits that is present only if the optional Unrestricted Motion Vector mode is indicated in PLUSPTYPE and UFEP is 001. When UUI is present it indicates the effective limitation of the range of the motion vectors being used. + +- UUI = "1" The motion vector range is limited according to Tables D.1 and D.2. +- UUI = "01" The motion vector range is not limited except by the picture size. + +### **5.1.10 Slice Structured Submode bits (SSS) (2 bits)** + +A fixed length codeword of 2 bits which is present only if the optional Slice Structured mode (see Annex K) is indicated in PLUSPTYPE and UFEP is 001. If the Slice Structured mode is in use but UFEP is not 001, the last values sent for SSS shall remain in effect. + +- Bit 1 Rectangular Slices, "0" indicates free-running slices, "1" indicates rectangular slices; +- Bit 2 Arbitrary Slice Ordering, "0" indicates sequential order, "1" indicates arbitrary order. + +### **5.1.11 Enhancement Layer Number (ELNUM) (4 bits)** + +A fixed length codeword of 4 bits which is present only if the optional Temporal, SNR, and Spatial Scalability mode is in use (regardless of the value of UFEP). The particular enhancement layer is identified by an enhancement layer number, ELNUM. Picture correspondence between layers is achieved via the temporal reference. Picture size is either indicated within each enhancement layer using the existing source format fields or is inferred by the relationship to the reference layer. The first enhancement layer above the base layer is designated as Enhancement Layer Number 2, and the base layer has number 1. + +### **5.1.12 Reference Layer Number (RLNUM) (4 bits)** + +A fixed length codeword of 4 bits which is present only if the optional Temporal, SNR, and Spatial Scalability mode is in use (see Annex O) and UFEP is 001. The layer number for the pictures used as reference anchors is identified by a Reference Layer Number (RLNUM). Time correspondence between layers is achieved via the temporal reference. + +Note that for B-pictures in an enhancement layer having temporally surrounding EI- or EP-pictures which are present in the same enhancement layer, RLNUM shall be equal to ELNUM (see Annex O). + +### **5.1.13 Reference Picture Selection Mode Flags (RPSMF) (3 bits)** + +A fixed length codeword of 3 bits that is present only if the Reference Picture Selection mode is in use and UFEP is 001. When present, RPSMF indicates which type of back-channel messages are needed by the encoder. If the Reference Picture Selection mode is in use but RPSMF is not present, the last value of RPSMF that was sent shall remain in effect. + +- 100: neither ACK nor NACK signals needed; +- 101: need ACK signals to be returned; +- 110: need NACK signals to be returned; +- 111: need both ACK and NACK signals to be returned; +- 000-011: Reserved. + +### **5.1.14 Temporal Reference for Prediction Indication (TRPI) (1 bit)** + +A fixed length codeword of 1 bit that is present only if the optional Reference Picture Selection mode is in use (regardless of the value of UFEP). When present, TRPI indicates the presence of the following TRP field: + +- 0: TRP field is not present; +- 1: TRP field is present. + +TRPI shall be 0 whenever the picture header indicates an I- or EI-picture. + +### **5.1.15 Temporal Reference for Prediction (TRP) (10 bits)** + +When present (as indicated in TRPI), TRP indicates the Temporal Reference which is used for prediction of the encoding, except for in the case of B-pictures. For B-pictures, the picture having the temporal reference TRP is used for the prediction in the forward direction. (Prediction in the reverse-temporal direction always uses the immediately temporally subsequent picture.) TRP is a ten-bit number. If a custom picture clock frequency was not in use for the reference picture, the two MSBs of TRP are zero and the LSBs contain the eight-bit TR found in the picture header of the reference picture. If a custom picture clock frequency was in use for the reference picture, TRP is a ten-bit number consisting of the concatenation of ETR and TR from the reference picture header. + +When TRP is not present, the most recent temporally previous anchor picture shall be used for prediction, as when not in the Reference Picture Selection mode. TRP is valid until the next PSC, GSC, or SSC. + +### **5.1.16 Back-Channel message Indication (BCI) (Variable length)** + +A variable length field of one or two bits that is present only if the optional Reference Picture Selection mode is in use. When set to "1", this signals the presence of the following optional video Back-Channel Message (BCM) field. "01" indicates the absence or the end of the video back-channel message field. Combinations of BCM and BCI may not be present, and may be repeated when present. BCI shall be set to "01" if the videomux submode of the optional Reference Picture Selection mode is not in use. + +### **5.1.17 Back-Channel Message (BCM) (Variable length)** + +The Back-Channel message with syntax as specified in N.4.2, which is present only if the preceding BCI field is present and is set to "1". + +### **5.1.18 Reference Picture Resampling Parameters (RPRP) (Variable length)** + +A variable length field that is present only if the optional Reference Picture Resampling mode bit is set in PLUSPTYPE. This field carries the parameters of the Reference Picture Resampling mode (see Annex P). Note that the Reference Picture Resampling mode can also be invoked implicitly by the occurrence of a picture header for an INTER coded picture having a picture size which differs from that of the previous encoded picture, in which case the RPRP field is not present and the Reference Picture Resampling mode bit is not set. + +### **5.1.19 Quantizer Information (PQUANT) (5 bits)** + +A fixed length codeword of 5 bits which indicates the quantizer QUANT to be used for the picture until updated by any subsequent GQUANT or DQUANT. The codewords are the natural binary representations of the values of QUANT which, being half the step sizes, range from 1 to 31. + +### **5.1.20 Continuous Presence Multipoint and Video Multiplex (CPM) (1 bit)** + +A codeword of 1 bit that signals the use of the optional Continuous Presence Multipoint and Video Multiplex mode (CPM); "0" is off, "1" is on. For the use of CPM, refer to Annex C. CPM follows immediately after PLUSPTYPE if PLUSPTYPE is present, but follows PQUANT in the picture header if PLUSPTYPE is not present. + +### **5.1.21 Picture Sub-Bitstream Indicator (PSBI) (2 bits)** + +A fixed length codeword of 2 bits that is only present if Continuous Presence Multipoint and Video Multiplex mode is indicated by CPM. The codewords are the natural binary representation of the sub-bitstream number for the picture header and all following information until the next Picture or GOB start code (see also Annex C). PSBI follows immediately after CPM if CPM is "1" (the location of CPM and PSBI in the picture header depend on whether PLUSPTYPE is present). + +### 5.1.22 Temporal Reference for B-pictures in PB-frames ( $TR_B$ ) (3/5 bits) + +$TR_B$ is present if PTYPE or PLUSPTYPE indicates "PB-frame" or "Improved PB-frame" (see also Annexes G and M) and indicates the number of non-transmitted or non-reference pictures (at 29.97 Hz or the custom picture clock frequency indicated in CPCFC) since the last P- or I-picture or P-part of a PB- or Improved PB-frame and before the B-picture part of the PB- or Improved PB-frame. The codeword is the natural binary representation of the number of non-transmitted pictures plus one. It is 3 bits long for standard CIF picture clock frequency and is extended to 5 bits when a custom picture clock frequency is in use. The maximum number of non-transmitted pictures is 6 for the standard CIF picture clock frequency and 30 when a custom picture clock frequency is used. + +### 5.1.23 Quantization information for B-pictures in PB-frames (DBQUANT) (2 bits) + +DBQUANT is present if PTYPE or PLUSPTYPE indicates "PB-frame" or "Improved PB-frame" (see also Annexes G and M). In the decoding process a quantization parameter QUANT is obtained for each macroblock. With PB-frames QUANT is used for the P-block, while for the B-block a different quantization parameter BQUANT is used. QUANT ranges from 1 to 31. DBQUANT indicates the relation between QUANT and BQUANT as defined in Table 6. In this table, "/" means division by truncation. BQUANT ranges from 1 to 31; if the value for BQUANT resulting from Table 6 is greater than 31, it is clipped to 31. + +**Table 6/H.263 – DBQUANT codes and relation between QUANT and BQUANT** + +| DBQUANT | BQUANT | +|---------|----------------------| +| 00 | $(5 \times QUANT)/4$ | +| 01 | $(6 \times QUANT)/4$ | +| 10 | $(7 \times QUANT)/4$ | +| 11 | $(8 \times QUANT)/4$ | + +### 5.1.24 Extra Insertion Information (PEI) (1 bit) + +A bit which when set to "1" signals the presence of the following optional data field. + +### 5.1.25 Supplemental Enhancement Information (PSUPP) (0/8/16 ... bits) + +If PEI is set to "1", then 9 bits follow consisting of 8 bits of data (PSUPP) and then another PEI bit to indicate if a further 9 bits follow and so on. Encoders shall use PSUPP as specified in Annex L. Decoders which do not support the extended capabilities described in Annex L shall be designed to discard PSUPP if PEI is set to 1. This enables backward compatibility for the extended capabilities of Annex L so that a bitstream which makes use of the extended capabilities can also be used without alteration by decoders which do not support those capabilities. + +### 5.1.26 Stuffing (ESTUF) (Variable length) + +A codeword of variable length consisting of less than 8 zero-bits. Encoders may insert this codeword directly before an EOS codeword. Encoders shall insert this codeword as necessary to attain mandatory byte alignment directly before an EOSBS codeword. If ESTUF is present, the last bit of ESTUF shall be the last (least significant) bit of a byte, so that the start of the EOS or EOSBS codeword is byte aligned. Decoders shall be designed to discard ESTUF. See Annex C for a description of EOSBS and its use. + +### 5.1.27 End Of Sequence (EOS) (22 bits) + +A codeword of 22 bits. Its value is 0000 0000 0000 0000 1 11111. It is up to the encoder to insert this codeword or not. EOS may be byte aligned. This can be achieved by inserting ESTUF before the EOS code such that the first bit of the EOS code is the first (most significant) bit of a byte. EOS shall not be repeated unless at least one picture start code appears between each pair of EOS codes. + +### 5.1.28 Stuffing (PSTUF) (Variable length) + +A codeword of variable length consisting of less than 8 zero-bits. Encoders shall insert this codeword for byte alignment of the next PSC. The last bit of PSTUF shall be the last (least significant) bit of a byte, so that the video bitstream including PSTUF is a multiple of 8 bits from the first bit in the H.263 bitstream. Decoders shall be designed to discard PSTUF. + +If for some reason the encoder stops encoding pictures for a certain time-period and resumes encoding later, PSTUF shall be transmitted before the encoder stops, to prevent that the last up to 7 bits of the previous picture are not sent until the coder resumes coding. + +## 5.2 Group of Blocks Layer + +Data for each Group of Blocks (GOB) consists of a GOB header followed by data for macroblocks. The structure is shown in Figure 9. Each GOB contains one or more rows of macroblocks. For the first GOB in each picture (with number 0), no GOB header shall be transmitted. For all other GOBs, the GOB header may be empty, depending on the encoder strategy. A decoder can signal the remote encoder to transmit only non-empty GOB headers by external means, for example ITU-T Rec. H.245. GSTUF may be present when GBSC is present. GN, GFID and GQUANT are present when GBSC is present. GSBI is present when CPM is "1" in the Picture header. + +![Figure 9/H.263 – Structure of GOB layer. A horizontal table with 7 cells: GSTUF, GBSC, GN, GSBI, GFID, GQUANT, and Macroblock Data.](43979979715bb3304389a0cb18f34444_img.jpg) + +| | | | | | | | +|-------|------|----|------|------|--------|-----------------| +| GSTUF | GBSC | GN | GSBI | GFID | GQUANT | Macroblock Data | +|-------|------|----|------|------|--------|-----------------| + +Figure 9/H.263 – Structure of GOB layer. A horizontal table with 7 cells: GSTUF, GBSC, GN, GSBI, GFID, GQUANT, and Macroblock Data. + +Figure 9/H.263 – Structure of GOB layer + +### 5.2.1 Stuffing (GSTUF) (Variable length) + +A codeword of variable length consisting of less than 8 zero-bits. Encoders may insert this codeword directly before a GBSC codeword. If GSTUF is present, the last bit of GSTUF shall be the last (least significant) bit of a byte, so that the start of the GBSC codeword is byte aligned. Decoders shall be designed to discard GSTUF. + +### 5.2.2 Group of Block Start Code (GBSC) (17 bits) + +A word of 17 bits. Its value is 0000 0000 0000 0000 1. GOB start codes may be byte aligned. This can be achieved by inserting GSTUF before the start code such that the first bit of the start code is the first (most significant) bit of a byte. + +### 5.2.3 Group Number (GN) (5 bits) + +A fixed length codeword of 5 bits. The bits are the binary representation of the number of the Group of Blocks. For the GOB with number 0, the GOB header including GSTUF, GBSC, GN, GSBI, GFID and GQUANT is empty; as group number 0 is used in the PSC. Group numbers 1 through 17 are used in GOB headers of the standard picture formats. Group numbers 1 through 24 are used in GOB headers of custom picture formats. Group numbers 16 through 28 are emulated in the slice header (see Annex K) when CPM = "0", and Group Numbers 25-27 and 29 are emulated in the slice header (see Annex K) when CPM = "1". Group number 31 is used in the EOS code, and group number 30 is used in the EOSBS code. + +### 5.2.4 GOB Sub-Bitstream Indicator (GSBI) (2 bits) + +A fixed length codeword of 2 bits that is only present if CPM is "1" in the picture header. The codewords are the natural binary representation of the sub-bitstream number for the GOB header and all following information until the next Picture or GOB start code (see also Annex C). + +### 5.2.5 GOB Frame ID (GFID) (2 bits) + +A fixed length codeword of 2 bits. GFID shall have the same value in every GOB (or slice) header of a given picture. Moreover, if PTTYPE as indicated in a picture header is the same as for the previous transmitted picture, GFID shall have the same value as in that previous picture, provided PLUSPTYPE is not present. However, if PTTYPE in a certain picture header differs from the PTTYPE in the previous transmitted picture header, the value for GFID in that picture shall differ from the value in the previous picture. + +If PLUSPTYPE is present, the value of GFID shall be the same as that for the previous picture (in the same layer) if the PTTYPE, and PLUSPTYPE, and all of the present fields among CPFMT, EPAR, CPCFC, SSS, ELNUM, RLNUM, UUI, RPSMF, and RPRP remain in effect as for the previous picture; otherwise, GFID shall be different from that for the previous picture. + +### 5.2.6 Quantizer Information (GQUANT) (5 bits) + +A fixed length codeword of 5 bits which indicates the quantizer QUANT to be used for the remaining part of the picture until updated by any subsequent GQUANT or DQUANT. The codewords are the natural binary representations of the values of QUANT which, being half the step sizes, range from 1 to 31. + +## 5.3 Macroblock layer + +Data for each macroblock consists of a macroblock header followed by data for blocks. The structure is shown in Figure 10. COD is only present in pictures that are not of type 'INTRA', for each macroblock in these pictures. MCBPC is present when indicated by COD or when the picture is of type 'INTRA'. MODB is present for MB-type 0-4 if PTTYPE indicates "PB-frame". CBPY, DQUANT, MVD and MVD2-4 are present when indicated by MCBPC. CBPB and MVDB are only present if indicated by MODB. Block Data is present when indicated by MCBPC and CBPY. MVD2-4 are only present when in Advanced Prediction mode (refer to Annex F) or Deblocking Filter mode (refer to Annex J). MODB, CBPB and MVDB are only present in PB-frames mode (refer to Annex G). For coding of the symbols in the Syntax-based Arithmetic Coding mode, refer to Annex E. For coding of the macroblock layer in B-, EI-, and EP-pictures, see Annex O. + +| | | | | | | | | | | | | +|-----|-------|------|------|------|--------|-----|------------------|------------------|------------------|------|------------| +| COD | MCBPC | MODB | CBPB | CBPY | DQUANT | MVD | MVD 2 | MVD 3 | MVD 4 | MVDB | Block Data | +|-----|-------|------|------|------|--------|-----|------------------|------------------|------------------|------|------------| + +Figure 10/H.263 – Structure of macroblock layer + +### 5.3.1 Coded macroblock indication (COD) (1 bit) + +A bit which when set to "0" signals that the macroblock is coded. If set to "1", no further information is transmitted for this macroblock; in that case the decoder shall treat the macroblock as an INTER macroblock with motion vector for the whole block equal to zero and with no coefficient data. COD is only present in pictures that are not of type "INTRA", for each macroblock in these pictures. + +NOTE – In Advanced Prediction mode (see Annex F), overlapped block motion compensation is also performed if COD is set to "1"; and in Deblocking Filter mode (see Annex J), the deblocking filter can also affect the values of some pixels of macroblocks having COD is set to "1". + +### 5.3.2 Macroblock type & Coded Block Pattern for Chrominance (MCBPC) (Variable length) + +MCBPC is a variable length codeword giving information about the macroblock type and the coded block pattern for chrominance. The codewords for MCBPC are given in Tables 7 and 8. MCBPC is always included in coded macroblocks. + +**Table 7/H.263 – VLC table for MCBPC (for I-pictures)** + +| Index | MB type | CBPC (56) | Number of bits | Code | +|-------|----------|-----------|----------------|-------------| +| 0 | 3 | 00 | 1 | 1 | +| 1 | 3 | 01 | 3 | 001 | +| 2 | 3 | 10 | 3 | 010 | +| 3 | 3 | 11 | 3 | 011 | +| 4 | 4 | 00 | 4 | 0001 | +| 5 | 4 | 01 | 6 | 0000 01 | +| 6 | 4 | 10 | 6 | 0000 10 | +| 7 | 4 | 11 | 6 | 0000 11 | +| 8 | Stuffing | – | 9 | 0000 0000 1 | + +**Table 8/H.263 – VLC table for MCBPC (for P-pictures)** + +| Index | MB type | CBPC (56) | Number of bits | Code | +|-------|---------|-----------|----------------|-------------| +| 0 | 0 | 00 | 1 | 1 | +| 1 | 0 | 01 | 4 | 0011 | +| 2 | 0 | 10 | 4 | 0010 | +| 3 | 0 | 11 | 6 | 0001 01 | +| 4 | 1 | 00 | 3 | 011 | +| 5 | 1 | 01 | 7 | 0000 111 | +| 6 | 1 | 10 | 7 | 0000 110 | +| 7 | 1 | 11 | 9 | 0000 0010 1 | +| 8 | 2 | 00 | 3 | 010 | +| 9 | 2 | 01 | 7 | 0000 101 | +| 10 | 2 | 10 | 7 | 0000 100 | +| 11 | 2 | 11 | 8 | 0000 0101 | +| 12 | 3 | 00 | 5 | 0001 1 | +| 13 | 3 | 01 | 8 | 0000 0100 | +| 14 | 3 | 10 | 8 | 0000 0011 | +| 15 | 3 | 11 | 7 | 0000 011 | +| 16 | 4 | 00 | 6 | 0001 00 | +| 17 | 4 | 01 | 9 | 0000 0010 0 | +| 18 | 4 | 10 | 9 | 0000 0001 1 | +| 19 | 4 | 11 | 9 | 0000 0001 0 | + +**Table 8/H.263 – VLC table for MCBPC (for P-pictures)** + +| Index | MB type | CBPC (56) | Number of bits | Code | +|-------|----------|-----------|----------------|------------------| +| 20 | Stuffing | – | 9 | 0000 0000 1 | +| 21 | 5 | 00 | 11 | 0000 0000 010 | +| 22 | 5 | 01 | 13 | 0000 0000 0110 0 | +| 23 | 5 | 10 | 13 | 0000 0000 0111 0 | +| 24 | 5 | 11 | 13 | 0000 0000 0111 1 | + +An extra codeword is available in the tables for bit stuffing. This codeword should be discarded by decoders. If an Improved PB-frame is indicated by MPPTYPE bits 1-3 and Custom Source Format is indicated in OPPTYPE bits 1-3, then MBA shall not indicate stuffing before the first macroblock of the picture (in order to prevent start code emulation). + +NOTE – Decoders should be designed to allow the macroblock type to indicate bit stuffing immediately prior to the location of a picture, GOB, or slice start code in the bitstream. However, encoders should not use macroblock-layer stuffing in this manner (for interoperability with decoders that may have been designed before the need for decoders to support this was clarified). + +The macroblock type gives information about the macroblock and which data elements are present. Macroblock types and included elements are listed in Tables 9 and 10. Macroblock type 5 (indices 21-24 in Table 8) shall not be present unless an extended PTYPE (PLUSPTYPE) is present in the picture header and either the Advanced Prediction mode (see Annex F) or the Deblocking Filter mode (see Annex J) is in use, and shall not be present for the first macroblock of a picture. Also, encoders shall not allow an MCBPC code for macroblock type 5 to immediately follow seven consecutive zeros in the bitstream (as can be caused by particular INTRADC codes followed by COD = 0), in order to prevent start code emulation. Codes for macroblock type 5 can be preceded by stuffing when necessary to fulfill this requirement (for macroblocks other than the first of a picture). + +**Table 9/H.263 – Macroblock types and included data elements for normal pictures** + +| Picture type | MB type | Name | COD | MCBPC | CBPY | DQUANT | MVD | MVD 2,4 | +|--------------|-----------|-----------|-----|-------|------|--------|-----|--------------------| +| INTER | Not coded | – | X | | | | | | +| INTER | 0 | INTER | X | X | X | | X | | +| INTER | 1 | INTER+Q | X | X | X | X | X | | +| INTER | 2 | INTER4V | X | X | X | | X | X | +| INTER | 3 | INTRA | X | X | X | | | | +| INTER | 4 | INTRA+Q | X | X | X | X | | | +| INTER | 5 | INTER4V+Q | X | X | X | X | X | X | +| INTER | Stuffing | – | X | X | | | | | +| INTRA | 3 | INTRA | | X | X | | | | +| INTRA | 4 | INTRA+Q | | X | X | X | | | +| INTRA | Stuffing | – | | X | | | | | + +NOTE – "X" means that the item is present in the macroblock. + +**Table 10/H.263 – Macroblock types and included data elements for PB-frames** + +| Picture type | MB type | Name | COD | MCBPC | MODB | CBPY | CBPB | DQUANT | MVD | MVDB | MVD 2-4 | +|--------------|-----------|-----------|-----|-------|------|------|------|--------|-----|------|--------------------| +| INTER | Not coded | – | X | | | | | | | | | +| INTER | 0 | INTER | X | X | X | X | (X) | | X | (X) | | +| INTER | 1 | INTER+Q | X | X | X | X | (X) | X | X | (X) | | +| INTER | 2 | INTER4V | X | X | X | X | (X) | | X | (X) | X | +| INTER | 3 | INTRA | X | X | X | X | (X) | | X | (X) | | +| INTER | 4 | INTRA+Q | X | X | X | X | (X) | X | X | (X) | | +| INTER | 5 | INTER4V+Q | X | X | X | X | (X) | X | X | (X) | X | +| INTER | Stuffing | – | X | X | | | | | | | | + +NOTE 1 – "X" means that the item is present in the macroblock. + +NOTE 2 – CBPB and MVDB are only present if indicated by MODB. + +NOTE 3 – B-blocks are always coded in INTER mode, even if the macroblock type of the PB-macroblock indicates INTRA. + +The coded block pattern for chrominance signifies CB and/or CR blocks when at least one non-INTRADC transform coefficient is transmitted (INTRADC is the dc-coefficient for INTRA blocks, see 5.4.1), unless the optional Advanced INTRA Coding mode is in use. CBPCN = 1 if any non-INTRADC coefficient is present for block N, else 0, for CBPC5 and CBPC6 in the coded block pattern. If Advanced INTRA Coding is in use, the usage is similar, but the INTRADC coefficient is indicated in the same way as the other coefficients (see Annex I). Block numbering is given in Figure 5. When MCBPC = Stuffing, the remaining part of the macroblock layer is skipped. In this case, the preceding COD = 0 is not related to any coded or not-coded macroblock and therefore the macroblock number is not incremented. For P-pictures, multiple stuffings are accomplished by multiple sets of COD = 0 and MCBPC = Stuffing. See Tables 7 and 8. + +### 5.3.3 Macroblock mode for B-blocks (MODB) (Variable length) + +MODB is present for MB-type 0-4 if PTYPE indicates "PB-frame" and is a variable length codeword indicating whether CBPB is present (indicates that B-coefficients are transmitted for this macroblock) and/or MVDB is present. In Table 11 the codewords for MODB are defined. MODB is coded differently for Improved PB-frames, as specified in Annex M. + +**Table 11/H.263 – VLC table for MODB** + +| Index | CBPB | MVDB | Number of bits | Code | +|--------------------------------------------------------------|------|------|----------------|------| +| 0 | | | 1 | 0 | +| 1 | | X | 2 | 10 | +| 2 | X | X | 2 | 11 | +| NOTE – "X" means that the item is present in the macroblock. | | | | | + +### 5.3.4 Coded Block Pattern for B-blocks (CBPB) (6 bits) + +CBPB is only present in PB-frames mode if indicated by MODB. CBPBN = 1 if any coefficient is present for B-block N, else 0, for each bit CBPBN in the coded block pattern. Block numbering is given in Figure 5, the utmost left bit of CBPB corresponding with block number 1. + +### 5.3.5 Coded Block Pattern for luminance (CBPY) (Variable length) + +Variable length codeword giving a pattern number signifying those Y blocks in the macroblock for which at least one non-INTRADC transform coefficient is transmitted (INTRADC is the dc-coefficient for INTRA blocks, see 5.4.1), unless the Advanced INTRA Coding mode is in use. If + +Advanced INTRA Coding is in use, INTRADC is indicated in the same manner as the other coefficients (see Annex I). + +CBPYN = 1 if any non-INTRADC coefficient is present for block N, else 0, for each bit CBPYN in the coded block pattern. Block numbering is given in Figure 5, the utmost left bit of CBPY corresponding with block number 1. For a certain pattern CBPYN, different codewords are used for INTER and INTRA macroblocks as defined in Table 12. + +**Table 12/H.263 – VLC table for CBPY** + +| Index | CBPY(INTRA)
(12, 34) | CBPY(INTER)
(12, 34) | Number of bits | Code | +|-------|-------------------------|-------------------------|----------------|---------| +| 0 | 00
00 | 11
11 | 4 | 0011 | +| 1 | 00
01 | 11
10 | 5 | 0010 1 | +| 2 | 00
10 | 11
01 | 5 | 0010 0 | +| 3 | 00
11 | 11
00 | 4 | 1001 | +| 4 | 01
00 | 10
11 | 5 | 0001 1 | +| 5 | 01
01 | 10
10 | 4 | 0111 | +| 6 | 01
10 | 10
01 | 6 | 0000 10 | +| 7 | 01
11 | 10
00 | 4 | 1011 | +| 8 | 10
00 | 01
11 | 5 | 0001 0 | +| 9 | 10
01 | 01
10 | 6 | 0000 11 | +| 10 | 10
10 | 01
01 | 4 | 0101 | +| 11 | 10
11 | 01
00 | 4 | 1010 | +| 12 | 11
00 | 00
11 | 4 | 0100 | +| 13 | 11
01 | 00
10 | 4 | 1000 | +| 14 | 11
10 | 00
01 | 4 | 0110 | +| 15 | 11
11 | 00
00 | 2 | 11 | + +### 5.3.6 Quantizer Information (DQUANT) (2 bits/Variable Length) + +If the Modified Quantization mode is not in use, DQUANT is a two-bit code to define a change in QUANT. In Table 13 the differential values for the different codewords are given. QUANT ranges from 1 to 31; if the value for QUANT after adding the differential value is less than 1 or greater than 31, it is clipped to 1 and 31 respectively. If the Modified Quantization mode is in use, DQUANT is a variable length codeword as specified in Annex T. + +**Table 13/H.263 – DQUANT codes and differential values for QUANT** + +| Index | Differential value | DQUANT | +|-------|--------------------|--------| +| 0 | -1 | 00 | +| 1 | -2 | 01 | +| 2 | 1 | 10 | +| 3 | 2 | 11 | + +### 5.3.7 Motion Vector Data (MVD) (Variable length) + +MVD is included for all INTER macroblocks (in PB-frames mode also for INTRA macroblocks) and consists of a variable length codeword for the horizontal component followed by a variable length codeword for the vertical component. Variable length codes are given in Table 14. If the Unrestricted Motion Vector mode is used and PLUSPTYPE is present, motion vectors are coded using Table D.3 instead of Table 14 (see Annex D). + +**Table 14/H.263 – VLC table for MVD** + +| Index | Vector | Differences | Bit number | Codes | +|-------|--------|-------------|------------|------------------| +| 0 | -16 | 16 | 13 | 0000 0000 0010 1 | +| 1 | -15.5 | 16.5 | 13 | 0000 0000 0011 1 | +| 2 | -15 | 17 | 12 | 0000 0000 0101 | +| 3 | -14.5 | 17.5 | 12 | 0000 0000 0111 | +| 4 | -14 | 18 | 12 | 0000 0000 1001 | +| 5 | -13.5 | 18.5 | 12 | 0000 0000 1011 | +| 6 | -13 | 19 | 12 | 0000 0000 1101 | +| 7 | -12.5 | 19.5 | 12 | 0000 0000 1111 | +| 8 | -12 | 20 | 11 | 0000 0001 001 | +| 9 | -11.5 | 20.5 | 11 | 0000 0001 011 | +| 10 | -11 | 21 | 11 | 0000 0001 101 | +| 11 | -10.5 | 21.5 | 11 | 0000 0001 111 | +| 12 | -10 | 22 | 11 | 0000 0010 001 | +| 13 | -9.5 | 22.5 | 11 | 0000 0010 011 | +| 14 | -9 | 23 | 11 | 0000 0010 101 | +| 15 | -8.5 | 23.5 | 11 | 0000 0010 111 | +| 16 | -8 | 24 | 11 | 0000 0011 001 | +| 17 | -7.5 | 24.5 | 11 | 0000 0011 011 | +| 18 | -7 | 25 | 11 | 0000 0011 101 | +| 19 | -6.5 | 25.5 | 11 | 0000 0011 111 | + +**Table 14/H.263 – VLC table for MVD** + +| Index | Vector | Differences | Bit number | Codes | +|-------|--------|-------------|------------|----------------| +| 20 | -6 | 26 | 11 | 0000 0100 001 | +| 21 | -5.5 | 26.5 | 11 | 0000 0100 011 | +| 22 | -5 | 27 | 10 | 0000 0100 11 | +| 23 | -4.5 | 27.5 | 10 | 0000 0101 01 | +| 24 | -4 | 28 | 10 | 0000 0101 11 | +| 25 | -3.5 | 28.5 | 8 | 0000 0111 | +| 26 | -3 | 29 | 8 | 0000 1001 | +| 27 | -2.5 | 29.5 | 8 | 0000 1011 | +| 28 | -2 | 30 | 7 | 0000 111 | +| 29 | -1.5 | 30.5 | 5 | 0001 1 | +| 30 | -1 | 31 | 4 | 0011 | +| 31 | -0.5 | 31.5 | 3 | 011 | +| 32 | 0 | | 1 | 1 | +| 33 | 0.5 | -31.5 | 3 | 010 | +| 34 | 1 | -31 | 4 | 0010 | +| 35 | 1.5 | -30.5 | 5 | 0001 0 | +| 36 | 2 | -30 | 7 | 0000 110 | +| 37 | 2.5 | -29.5 | 8 | 0000 1010 | +| 38 | 3 | -29 | 8 | 0000 1000 | +| 39 | 3.5 | -28.5 | 8 | 0000 0110 | +| 40 | 4 | -28 | 10 | 0000 0101 10 | +| 41 | 4.5 | -27.5 | 10 | 0000 0101 00 | +| 42 | 5 | -27 | 10 | 0000 0100 10 | +| 43 | 5.5 | -26.5 | 11 | 0000 0100 010 | +| 44 | 6 | -26 | 11 | 0000 0100 000 | +| 45 | 6.5 | -25.5 | 11 | 0000 0011 110 | +| 46 | 7 | -25 | 11 | 0000 0011 100 | +| 47 | 7.5 | -24.5 | 11 | 0000 0011 010 | +| 48 | 8 | -24 | 11 | 0000 0011 000 | +| 49 | 8.5 | -23.5 | 11 | 0000 0010 110 | +| 50 | 9 | -23 | 11 | 0000 0010 100 | +| 51 | 9.5 | -22.5 | 11 | 0000 0010 010 | +| 52 | 10 | -22 | 11 | 0000 0010 000 | +| 53 | 10.5 | -21.5 | 11 | 0000 0001 110 | +| 54 | 11 | -21 | 11 | 0000 0001 100 | +| 55 | 11.5 | -20.5 | 11 | 0000 0001 010 | +| 56 | 12 | -20 | 11 | 0000 0001 000 | +| 57 | 12.5 | -19.5 | 12 | 0000 0000 1110 | + +**Table 14/H.263 – VLC table for MVD** + +| Index | Vector | Differences | Bit number | Codes | +|-------|--------|-------------|------------|------------------| +| 58 | 13 | –19 | 12 | 0000 0000 1100 | +| 59 | 13.5 | –18.5 | 12 | 0000 0000 1010 | +| 60 | 14 | –18 | 12 | 0000 0000 1000 | +| 61 | 14.5 | –17.5 | 12 | 0000 0000 0110 | +| 62 | 15 | –17 | 12 | 0000 0000 0100 | +| 63 | 15.5 | –16.5 | 13 | 0000 0000 0011 0 | + +### 5.3.8 Motion Vector Data (MVD2-4) (Variable length) + +The three codewords MVD2-4 are included if indicated by PTYPE and by MCBPC, and consist each of a variable length codeword for the horizontal component followed by a variable length codeword for the vertical component of each vector. Variable length codes are given in Table 14. MVD2-4 are only present when in Advanced Prediction mode (see Annex F) or Deblocking Filter mode (see Annex J). + +### 5.3.9 Motion Vector Data for B-macroblock (MVDB) (Variable length) + +MVDB is only present in PB-frames or Improved PB-frames mode if indicated by MODB, and consists of a variable length codeword for the horizontal component followed by a variable length codeword for the vertical component of each vector. Variable length codes are given in Table 14. For the use of MVDB, refer to Annexes G and M. + +## 5.4 Block layer + +If not in PB-frames mode, a macroblock comprises four luminance blocks and one of each of the two colour difference blocks (see Figure 5). The structure of the block layer is shown in Figure 11. INTRADC is present for every block of the macroblock if MCBPC indicates macroblock type 3 or 4 (see Tables 7 and 8). TCOEF is present if indicated by MCBPC or CBPY. + +In PB-frames mode, a macroblock comprises twelve blocks. First the data for the six P-blocks is transmitted as in the default H.263 mode, then the data for the six B-blocks. INTRADC is present for every P-block of the macroblock if MCBPC indicates macroblock type 3 or 4 (see Tables 7 and 8). INTRADC is not present for B-blocks. TCOEF is present for P-blocks if indicated by MCBPC or CBPY. TCOEF is present for B-blocks if indicated by CBPB. + +For coding of the symbols in the Syntax-based Arithmetic Coding mode, refer to Annex E. + +| | | +|---------|-------| +| INTRADC | TCOEF | +|---------|-------| + +**Figure 11/H.263 – Structure of block layer** + +### 5.4.1 DC coefficient for INTRA blocks (INTRADC) (8 bits) + +A codeword of 8 bits. The code 0000 0000 is not used. The code 1000 0000 is not used, the reconstruction level of 1024 being coded as 1111 1111 (see Table 15). + +**Table 15/H.263 – Reconstruction levels for INTRA-mode DC coefficient** + +| Index | FLC | Reconstruction level into inverse transform | +|-------|-----------------|---------------------------------------------| +| 0 | 0000 0001 (1) | 8 | +| 1 | 0000 0010 (2) | 16 | +| 2 | 0000 0011 (3) | 24 | +| ... | ... | ... | +| 126 | 0111 1111 (127) | 1016 | +| 127 | 1111 1111 (255) | 1024 | +| 128 | 1000 0001 (129) | 1032 | +| ... | ... | ... | +| 252 | 1111 1101 (253) | 2024 | +| 253 | 1111 1110 (254) | 2032 | + +### 5.4.2 Transform Coefficient (TCOEF) (Variable length) + +The most commonly occurring EVENTS are coded with the variable length codes given in Table 16. The last bit "s" denotes the sign of the level, "0" for positive and "1" for negative. + +An EVENT is a combination of a last non-zero coefficient indication (LAST; "0": there are more non-zero coefficients in this block, "1": this is the last non-zero coefficient in this block), the number of successive zeros preceding the coded coefficient (RUN), and the non-zero value of the coded coefficient (LEVEL). + +The remaining combinations of (LAST, RUN, LEVEL) are coded with a 22-bit word consisting of 7 bits ESCAPE, 1 bit LAST, 6 bits RUN and 8 bits LEVEL. Use of this 22-bit word for encoding the combinations listed in Table 16 is not prohibited. For the 8-bit word for LEVEL, the code 0000 0000 is forbidden, and the code 1000 0000 is forbidden unless the Modified Quantization mode is in use (see Annex T). The codes for RUN and for LEVEL are given in Table 17. + +**Table 16/H.263 – VLC table for TCOEF** + +| Index | LAST | RUN | LEVEL | Bits | VLC code | +|-------|------|-----|-------|------|----------------| +| 0 | 0 | 0 | 1 | 3 | 10s | +| 1 | 0 | 0 | 2 | 5 | 1111s | +| 2 | 0 | 0 | 3 | 7 | 0101 01s | +| 3 | 0 | 0 | 4 | 8 | 0010 111s | +| 4 | 0 | 0 | 5 | 9 | 0001 1111s | +| 5 | 0 | 0 | 6 | 10 | 0001 0010 1s | +| 6 | 0 | 0 | 7 | 10 | 0001 0010 0s | +| 7 | 0 | 0 | 8 | 11 | 0000 1000 01s | +| 8 | 0 | 0 | 9 | 11 | 0000 1000 00s | +| 9 | 0 | 0 | 10 | 12 | 0000 0000 111s | + +**Table 16/H.263 – VLC table for TCOEF** + +| Index | LAST | RUN | LEVEL | Bits | VLC code | +|--------------|-------------|------------|----------------|-------------|-----------------| +| 10 | 0 | 0 | 11 | 12 | 0000 0000 110s | +| 11 | 0 | 0 | 12 | 12 | 0000 0100 000s | +| 12 | 0 | 1 | 1 | 4 | 110s | +| 13 | 0 | 1 | 2 | 7 | 0101 00s | +| 14 | 0 | 1 | 3 | 9 | 0001 1110s | +| 15 | 0 | 1 | 4 | 11 | 0000 0011 11s | +| 16 | 0 | 1 | 5 | 12 | 0000 0100 001s | +| 17 | 0 | 1 | 6 | 13 | 0000 0101 0000s | +| 18 | 0 | 2 | 1 | 5 | 1110s | +| 19 | 0 | 2 | 2 | 9 | 0001 1101s | +| 20 | 0 | 2 | 3 | 11 | 0000 0011 10s | +| 21 | 0 | 2 | 4 | 13 | 0000 0101 0001s | +| 22 | 0 | 3 | 1 | 6 | 0110 1s | +| 23 | 0 | 3 | 2 | 10 | 0001 0001 1s | +| 24 | 0 | 3 | 3 | 11 | 0000 0011 01s | +| 25 | 0 | 4 | 1 | 6 | 0110 0s | +| 26 | 0 | 4 | 2 | 10 | 0001 0001 0s | +| 27 | 0 | 4 | 3 | 13 | 0000 0101 0010s | +| 28 | 0 | 5 | 1 | 6 | 0101 1s | +| 29 | 0 | 5 | 2 | 11 | 0000 0011 00s | +| 30 | 0 | 5 | 3 | 13 | 0000 0101 0011s | +| 31 | 0 | 6 | 1 | 7 | 0100 11s | +| 32 | 0 | 6 | 2 | 11 | 0000 0010 11s | +| 33 | 0 | 6 | 3 | 13 | 0000 0101 0100s | +| 34 | 0 | 7 | 1 | 7 | 0100 10s | +| 35 | 0 | 7 | 2 | 11 | 0000 0010 10s | +| 36 | 0 | 8 | 1 | 7 | 0100 01s | +| 37 | 0 | 8 | 2 | 11 | 0000 0010 01s | +| 38 | 0 | 9 | 1 | 7 | 0100 00s | +| 39 | 0 | 9 | 2 | 11 | 0000 0010 00s | +| 40 | 0 | 10 | 1 | 8 | 0010 110s | +| 41 | 0 | 10 | 2 | 13 | 0000 0101 0101s | +| 42 | 0 | 11 | 1 | 8 | 0010 101s | +| 43 | 0 | 12 | 1 | 8 | 0010 100s | +| 44 | 0 | 13 | 1 | 9 | 0001 1100s | +| 45 | 0 | 14 | 1 | 9 | 0001 1011s | +| 46 | 0 | 15 | 1 | 10 | 0001 0000 1s | +| 47 | 0 | 16 | 1 | 10 | 0001 0000 0s | + +**Table 16/H.263 – VLC table for TCOEF** + +| Index | LAST | RUN | LEVEL | Bits | VLC code | +|--------------|-------------|------------|----------------|-------------|-----------------| +| 48 | 0 | 17 | 1 | 10 | 0000 1111 1s | +| 49 | 0 | 18 | 1 | 10 | 0000 1111 0s | +| 50 | 0 | 19 | 1 | 10 | 0000 1110 1s | +| 51 | 0 | 20 | 1 | 10 | 0000 1110 0s | +| 52 | 0 | 21 | 1 | 10 | 0000 1101 1s | +| 53 | 0 | 22 | 1 | 10 | 0000 1101 0s | +| 54 | 0 | 23 | 1 | 12 | 0000 0100 010s | +| 55 | 0 | 24 | 1 | 12 | 0000 0100 011s | +| 56 | 0 | 25 | 1 | 13 | 0000 0101 0110s | +| 57 | 0 | 26 | 1 | 13 | 0000 0101 0111s | +| 58 | 1 | 0 | 1 | 5 | 0111s | +| 59 | 1 | 0 | 2 | 10 | 0000 1100 1s | +| 60 | 1 | 0 | 3 | 12 | 0000 0000 101s | +| 61 | 1 | 1 | 1 | 7 | 0011 11s | +| 62 | 1 | 1 | 2 | 12 | 0000 0000 100s | +| 63 | 1 | 2 | 1 | 7 | 0011 10s | +| 64 | 1 | 3 | 1 | 7 | 0011 01s | +| 65 | 1 | 4 | 1 | 7 | 0011 00s | +| 66 | 1 | 5 | 1 | 8 | 0010 011s | +| 67 | 1 | 6 | 1 | 8 | 0010 010s | +| 68 | 1 | 7 | 1 | 8 | 0010 001s | +| 69 | 1 | 8 | 1 | 8 | 0010 000s | +| 70 | 1 | 9 | 1 | 9 | 0001 1010s | +| 71 | 1 | 10 | 1 | 9 | 0001 1001s | +| 72 | 1 | 11 | 1 | 9 | 0001 1000s | +| 73 | 1 | 12 | 1 | 9 | 0001 0111s | +| 74 | 1 | 13 | 1 | 9 | 0001 0110s | +| 75 | 1 | 14 | 1 | 9 | 0001 0101s | +| 76 | 1 | 15 | 1 | 9 | 0001 0100s | +| 77 | 1 | 16 | 1 | 9 | 0001 0011s | +| 78 | 1 | 17 | 1 | 10 | 0000 1100 0s | +| 79 | 1 | 18 | 1 | 10 | 0000 1011 1s | +| 80 | 1 | 19 | 1 | 10 | 0000 1011 0s | +| 81 | 1 | 20 | 1 | 10 | 0000 1010 1s | +| 82 | 1 | 21 | 1 | 10 | 0000 1010 0s | +| 83 | 1 | 22 | 1 | 10 | 0000 1001 1s | +| 84 | 1 | 23 | 1 | 10 | 0000 1001 0s | +| 85 | 1 | 24 | 1 | 10 | 0000 1000 1s | + +**Table 16/H.263 – VLC table for TCOEF** + +| Index | LAST | RUN | LEVEL | Bits | VLC code | +|-------|--------|-----|-------|------|-----------------| +| 86 | 1 | 25 | 1 | 11 | 0000 0001 11s | +| 87 | 1 | 26 | 1 | 11 | 0000 0001 10s | +| 88 | 1 | 27 | 1 | 11 | 0000 0001 01s | +| 89 | 1 | 28 | 1 | 11 | 0000 0001 00s | +| 90 | 1 | 29 | 1 | 12 | 0000 0100 100s | +| 91 | 1 | 30 | 1 | 12 | 0000 0100 101s | +| 92 | 1 | 31 | 1 | 12 | 0000 0100 110s | +| 93 | 1 | 32 | 1 | 12 | 0000 0100 111s | +| 94 | 1 | 33 | 1 | 13 | 0000 0101 1000s | +| 95 | 1 | 34 | 1 | 13 | 0000 0101 1001s | +| 96 | 1 | 35 | 1 | 13 | 0000 0101 1010s | +| 97 | 1 | 36 | 1 | 13 | 0000 0101 1011s | +| 98 | 1 | 37 | 1 | 13 | 0000 0101 1100s | +| 99 | 1 | 38 | 1 | 13 | 0000 0101 1101s | +| 100 | 1 | 39 | 1 | 13 | 0000 0101 1110s | +| 101 | 1 | 40 | 1 | 13 | 0000 0101 1111s | +| 102 | ESCAPE | | | 7 | 0000 011 | + +**Table 17/H.263 – FLC table for RUNs and LEVELs** + +| Index | Run | Code | +|-------|-----|---------| +| 0 | 0 | 000 000 | +| 1 | 1 | 000 001 | +| 2 | 2 | 000 010 | +| . | . | . | +| . | . | . | +| 63 | 63 | 111 111 | + +| Index | Level | Code | +|-------|-------|-----------| +| – | –128 | see text | +| 0 | –127 | 1000 0001 | +| . | . | . | +| 125 | –2 | 1111 1110 | +| 126 | –1 | 1111 1111 | +| – | 0 | FORBIDDEN | +| 127 | 1 | 0000 0001 | +| 128 | 2 | 0000 0010 | +| . | . | . | +| 253 | 127 | 0111 1111 | + +# 6 Decoding process + +## 6.1 Motion compensation + +In this clause, the motion compensation for the default H.263 prediction mode is described. For a description of motion compensation in the Unrestricted Motion Vector mode, refer to Annex D. For a description of motion compensation in the Advanced Prediction mode, refer to Annex F. For a description of motion compensation in the Reduced-Resolution Update mode, refer to Annex Q. + +### 6.1.1 Differential motion vectors + +The macroblock vector is obtained by adding predictors to the vector differences indicated by MVD (see Table 14 and Table D.3). For differential coding with four vectors per macroblock, refer to Annex F. In case of one vector per macroblock, the candidate predictors for the differential coding are taken from three surrounding macroblocks as indicated in Figure 12. The predictors are calculated separately for the horizontal and vertical components. + +In the special cases at the borders of the current GOB, slice, or picture, the following decision rules are applied in increasing order: + +- 1) When the corresponding macroblock was coded in INTRA mode (if not in PB-frames mode with bidirectional prediction) or was not coded (COD = 1), the candidate predictor is set to zero. +- 2) The candidate predictor MV1 is set to zero if the corresponding macroblock is outside the picture or the slice (at the left side). +- 3) Then, the candidate predictors MV2 and MV3 are set to MV1 if the corresponding macroblocks are outside the picture (at the top) or outside the GOB (at the top) if the GOB header of the current GOB is non-empty; or outside the slice when in Slice Structured mode. +- 4) Then, the candidate predictor MV3 is set to zero if the corresponding macroblock is outside the picture (at the right side). + +For each component, the predictor is the median value of the three candidate predictors for this component. + +![Figure 12/H.263 – Motion vector prediction. The diagram shows three macroblock grids illustrating the selection of predictors (MV1, MV2, MV3) for the current motion vector (MV). A dashed line indicates the Picture or GOB border. The legend defines MV as Current motion vector, MV1 as Previous motion vector, MV2 as Above motion vector, and MV3 as Above right motion vector.](18e519d1f91133e080347562f681dfb5_img.jpg) + +The diagram illustrates three scenarios for motion vector prediction based on the position of the current macroblock relative to the Picture or GOB border (indicated by a dashed line). + +- Left Scenario:** The current macroblock (MV) is at the left border. MV1 is outside the border and is set to (0,0). MV2 and MV3 are above the current block. +- Middle Scenario:** The current macroblock (MV) is not at the border. MV1 is the previous block to the left. MV2 and MV3 are above the current block. +- Right Scenario:** The current macroblock (MV) is at the right border. MV1 is the previous block to the left. MV2 is above the current block, and MV3 is outside the border and is set to (0,0). + +Legend: + +- Picture or GOB border +- MV Current motion vector +- MV1 Previous motion vector +- MV2 Above motion vector +- MV3 Above right motion vector + +T1602810-97 + +Figure 12/H.263 – Motion vector prediction. The diagram shows three macroblock grids illustrating the selection of predictors (MV1, MV2, MV3) for the current motion vector (MV). A dashed line indicates the Picture or GOB border. The legend defines MV as Current motion vector, MV1 as Previous motion vector, MV2 as Above motion vector, and MV3 as Above right motion vector. + +**Figure 12/H.263 – Motion vector prediction** + +Advantage is taken of the fact that the range of motion vector component values is constrained. Each VLC word for MVD represents a pair of difference values. Only one of the pair will yield a macroblock vector component falling within the permitted range [-16, 15.5]. A positive value of the horizontal or vertical component of the motion vector signifies that the prediction is formed from pixels in the previous picture which are spatially to the right or below the pixels being predicted. If the unrestricted motion vector mode (see Annex D) is used, the decoding of motion vectors shall be performed as specified in D.2. + +The motion vector is used for all pixels in all four luminance blocks in the macroblock. Motion vectors for both chrominance blocks are derived by dividing the component values of the macroblock vector by two, due to the lower chrominance format. The component values of the resulting quarter pixel resolution vectors are modified towards the nearest half pixel position as indicated in Table 18. + +**Table 18/H.263 – Modification of quarter-pixel resolution chrominance vector components** + +| | | | | | | +|-------------------------------|---|-----|-----|-----|---| +| Quarter-pixel position | 0 | 1/4 | 1/2 | 3/4 | 1 | +| Resulting position | 0 | 1/2 | 1/2 | 1/2 | 1 | + +### 6.1.2 Interpolation for subpixel prediction + +Half pixel values are found using bilinear interpolation as described in Figure 13. "/" indicates division by truncation. + +The value of RCONTROL is equal to the value of the rounding type (RTYPE) bit (bit 6) in MPPTYPE (see 5.1.4.3), when the Source Format field (bits 6-8) in PTYPE indicates "extended PTYPE". Otherwise RCONTROL has an implied value of 0. Regardless of the RTYPE bit, the value of RCONTROL is set to 0 for the B-part of Improved PB frames (see Annex M). + +![Diagram illustrating bilinear interpolation for half-pixel prediction. It shows four integer pixel positions (A, B, C, D) marked with 'X' and four half-pixel positions (a, b, c, d) marked with 'O'. Position 'a' is between A and B, 'c' is between A and C, 'd' is between B and C, and 'b' is between B and D. The diagram is labeled T1602820-97.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +× Integer pixel position + ○ Half pixel position + +$$\begin{aligned} + a &= A \\ + b &= (A + B + 1 - \text{RCONTROL}) / 2 \\ + c &= (A + C + 1 - \text{RCONTROL}) / 2 \\ + d &= (A + B + C + D + 2 - \text{RCONTROL}) / 4 + \end{aligned}$$ + +T1602820-97 + +Diagram illustrating bilinear interpolation for half-pixel prediction. It shows four integer pixel positions (A, B, C, D) marked with 'X' and four half-pixel positions (a, b, c, d) marked with 'O'. Position 'a' is between A and B, 'c' is between A and C, 'd' is between B and C, and 'b' is between B and D. The diagram is labeled T1602820-97. + +**Figure 13/H.263 – Half-pixel prediction by bilinear interpolation** + +## 6.2 Coefficients decoding + +### 6.2.1 Inverse quantization + +The inverse quantization process is described in this subclause, except for when the optional Advanced INTRA Coding mode is in use (see Annex I). If LEVEL = "0", the reconstruction level REC = "0". The reconstruction level of INTRADC is given by Table 15. The reconstruction levels of all non-zero coefficients other than the INTRADC one are given by the following formulas: + +$$\begin{aligned} + |\text{REC}| &= \text{QUANT} \cdot (2 \cdot |\text{LEVEL}| + 1) && \text{if QUANT = "odd"} \\ + |\text{REC}| &= \text{QUANT} \cdot (2 \cdot |\text{LEVEL}| + 1) - 1 && \text{if QUANT = "even"} + \end{aligned}$$ + +Note that this process disallows even valued numbers. This has been found to prevent accumulation of IDCT mismatch errors. After calculation of $|\text{REC}|$ , the sign is added to obtain REC: $\text{REC} = \text{sign}(\text{LEVEL}) \cdot |\text{REC}|$ + +$\text{Sign}(\text{LEVEL})$ is given by the last bit of the TCOEF code (see Table 16) or by Table 17. + +### 6.2.2 Clipping of reconstruction levels + +After inverse quantization, the reconstruction levels of all coefficients other than the INTRADC one are clipped to the range 2048 to 2047. + +### 6.2.3 Zigzag positioning + +The quantized transform coefficients are placed into an $8 \times 8$ block according to the sequence given in Figure 14, unless the optional Advanced INTRA Coding mode is in use (see Annex I). Coefficient 1 is the dc-coefficient. + +| | | | | | | | | +|----|----|----|----|----|----|----|----| +| 1 | 2 | 6 | 7 | 15 | 16 | 28 | 29 | +| 3 | 5 | 8 | 14 | 17 | 27 | 30 | 43 | +| 4 | 9 | 13 | 18 | 26 | 31 | 42 | 44 | +| 10 | 12 | 19 | 25 | 32 | 41 | 45 | 54 | +| 11 | 20 | 24 | 33 | 40 | 46 | 53 | 55 | +| 21 | 23 | 34 | 39 | 47 | 52 | 56 | 61 | +| 22 | 35 | 38 | 48 | 51 | 57 | 60 | 62 | +| 36 | 37 | 49 | 50 | 58 | 59 | 63 | 64 | + +**Figure 14/H.263 – Zigzag positioning of quantized transform coefficients** + +### 6.2.4 Inverse transform + +After inverse quantization and zigzag of coefficients, the resulting $8 \times 8$ blocks are processed by a separable two-dimensional inverse discrete cosine transform of size 8 by 8. The output from the inverse transform ranges from $-256$ to $+255$ after clipping to be represented with 9 bits. The transfer function of the inverse transform is given by: + +$$f(x,y) = \frac{1}{4} \sum_{u=0}^7 \sum_{v=0}^7 C(u)C(v)F(u,v) \cos\left[\pi(2x+1)\frac{u}{16}\right] \cos\left[\pi(2y+1)\frac{v}{16}\right]$$ + +with $u, v, x, y = 0, 1, 2, \dots, 7$ + +where: + +$x, y$ = spatial coordinates in the pixel domain; + +$u, v$ = coordinates in the transform domain; + +$C(u) = 1/\sqrt{2}$ for $u = 0$ , otherwise 1; + +$C(v) = 1/\sqrt{2}$ for $v = 0$ , otherwise 1. + +NOTE – Within the block being transformed, $x = 0$ and $y = 0$ refer to the pixel nearest the left and top edges of the picture respectively. + +The arithmetic procedures for computing the inverse transform are not defined, but should meet the error tolerance specified in Annex A. + +## 6.3 Reconstruction of blocks + +### 6.3.1 Summation + +After motion compensation and coefficients decoding (inverse transform included), a reconstruction is formed for each luminance and chrominance block. For INTRA blocks, the reconstruction is equal to the result of the inverse transformation. For INTER blocks, the reconstruction is formed by summing the prediction and the result of the inverse transformation. The summation is performed on a pixel basis. For the summation in the Reduced-Resolution Update mode, refer to Annex Q. + +### 6.3.2 Clipping + +To prevent quantization distortion of transform coefficient amplitudes causing arithmetic overflow in the encoder and decoder loops, clipping functions are inserted. The clipper operates after the summation of prediction and reconstructed prediction error on resulting pixel values less than 0 or greater than 255, changing them to 0 and 255 respectively. + +# Annex A + +## Inverse transform accuracy specification + +**A.1** Generate random integer pixel data values in the range $-L$ to $+H$ according to the random number generator given below ("C" version). Arrange into 8 by 8 blocks. Data set of 10 000 blocks should each be generated for ( $L = 256, H = 255$ ), ( $L = H = 5$ ) and ( $L = H = 300$ ). + +**A.2** For each 8 by 8 block, perform a separable, orthonormal, matrix multiply, forward discrete cosine transform using at least 64-bit floating point accuracy. + +$$F(u,v) = \frac{1}{4} C(u) C(v) \sum_{x=0}^7 \sum_{y=0}^7 f(x,y) \cos\left[\pi(2x+1)\frac{u}{16}\right] \cos\left[\pi(2y+1)\frac{v}{16}\right]$$ + +with $u, v, x, y = 0, 1, 2, \dots, 7$ + +where: + +$x, y$ = spatial coordinates in the pixel domain; + +$u, v$ = coordinates in the transform domain; + +$C(u) = 1/\sqrt{2}$ for $u = 0$ , otherwise 1; + +$C(v) = 1/\sqrt{2}$ for $v = 0$ , otherwise 1. + +**A.3** For each block, round the 64 resulting transformed coefficients to the nearest integer values. Then clip them to the range $-2048$ to $+2047$ . This is the 12-bit input data to the inverse transform. + +**A.4** For each 8 by 8 block of 12-bit data produced by A.3, perform a separable, orthonormal, matrix multiply, inverse discrete cosine transform (IDCT) using at least 64-bit floating point accuracy. Round the resulting pixels to the nearest integer and clip to the range $-256$ to $+255$ . These blocks of $8 \times 8$ pixels are the reference IDCT output data. + +**A.5** For each 8 by 8 block produced by A.3, apply the IDCT under test and clip the output to the range $-256$ to $+255$ . These blocks of $8 \times 8$ pixels are the test IDCT output data. + +**A.6** For each of the 64 IDCT output pixels, and for each of the 10 000 block data sets generated above, measure the peak, mean and mean square error between the reference and the test data. + +- A.7** +- For any pixel, the peak error should not exceed 1 in magnitude. + - For any pixel, the mean square error should not exceed 0.06. + - Overall, the mean square error should not exceed 0.02. + - For any pixel, the mean error should not exceed 0.015 in magnitude. + - Overall, the mean error should not exceed 0.0015 in magnitude. + +**A.8** All zeros in shall produce all zeros out. + +**A.9** Re-run the measurements using exactly the same data values of A.1, but change the sign on each pixel. + +``` + +"C" program for random number generation +/* L and H shall be long, that is 32 bits */ +long rand (L,H) +long L,H; +{ + static long randx = 1; /* long is 32 bits */ + static double z = (double) 0x7fffffff; + long i,j; + double x; /* double is 64 bits */ + randx = (randx * 1103515245) + 12345; + i = randx & 0x7fffffe; /* keep 30 bits */ + x = ( (double)i ) / z; /* range 0 to 0.99999 ... */ + x *= (L+H+1); /* range 0 to < L+H+1 */ + j = x; /* truncate to integer */ + return(j - L); /* range -L to H */ +} + +``` + +# Annex B + +## Hypothetical Reference Decoder + +The Hypothetical Reference Decoder (HRD) is defined as follows: + +**B.1** The HRD and the encoder have the same clock frequency as well as the same picture clock frequency, and are operated synchronously. + +**B.2** The HRD receiving buffer size is $(B + \text{BPPmaxKb} * 1024 \text{ bits})$ where $(\text{BPPmaxKb} * 1024)$ is the maximum number of bits per picture that has been negotiated for use in the bitstream (see 3.6). The value of B is defined as follows: + +$$B = 4 \cdot R_{\max} / PCF$$ + +where PCF is the effective picture clock frequency, and $R_{\max}$ is the maximum video bit rate during the connection in bits per second. The effective picture clock frequency is the standard CIF picture clock frequency unless a custom PCF is specified in the CPCFC field of the picture header. This value for B is a minimum. An encoder may use a larger value for B, provided the larger number is first negotiated by external means, for example ITU-T Rec. H.245. + +The value for $R_{\max}$ depends on the system configuration (for example GSTN or ISDN, single or multi-link) and may be equal to the maximum bit rate supported by the physical link. Negotiation of $R_{\max}$ is done by external means (for example, ITU-T Rec. H.245). + +**B.3** The HRD is initially empty. + +**B.4** The HRD buffer is examined at picture clock intervals (1000/PCF ms). If at least one complete coded picture is in the buffer, then all the data for the earliest picture in bitstream order is instantaneously removed (e.g., at $t_{n+1}$ in Figure B.1). Immediately after removing the above data, the buffer occupancy must be less than $B$ . This is a requirement on the coder output bitstream including coded picture data and MCBPC and STUF stuffing but not error correction framing bits, fill indicator (Fi), fill bits or error correction parity information described in Annex H. + +For the purposes of this definition, unless the optional Temporal, SNR, and Spatial Scalability mode is in use, a complete coded picture is one normal I- or P-picture, or a PB-frame or Improved PB-frame. + +When the Temporal, SNR, and Spatial Scalability mode is in use (see Annex O), each enhancement layer is given an additional HRD, for which a complete coded picture is one EI-, EP-, or B-picture. The base layer buffer shall hold the bits of the picture header as they arrive, until a sufficient amount of the picture header has arrived to determine whether the picture is a base layer or enhancement layer picture, and the number of the enhancement layer. When it can be determined that the arriving picture belongs to an enhancement layer, all bits for that picture shall be instantly transferred to the appropriate enhancement layer HRD, and any later bits which arrive continue to be placed into the enhancement layer HRD until a sufficient amount of some new picture header has arrived to determine that the bitstream should again be re-routed into another HRD buffer. The process of enhancement layer identification is instantaneous and asynchronous, independent of the picture clock interval checking times. + +To meet this requirement, the number of bits for the $(n+1)$ th coded picture $d_{n+1}$ must satisfy: + +$$d_{n+1} \geq b_n + \int_{t_n}^{t_{n+1}} R(t) dt - B$$ + +where: + +$b_n$ is the buffer occupancy just after time $t_n$ ; + +$t_n$ is the time the $n$ th coded picture is removed from the HRD buffer; + +$R(t)$ is the video bit rate at time $t$ . + +![Figure B.1/H.263 – HRD buffer occupancy. A graph showing HRD buffer occupancy (bit) on the y-axis and Time (CIF interval) on the x-axis. The y-axis has a horizontal dashed line at B. The x-axis has tick marks for t_n and t_{n+1}. The graph shows a sawtooth-like pattern where the buffer occupancy increases linearly from the origin, reaches a peak at t_n, then drops to b_n. It increases again, reaching a peak at t_{n+1}, and then drops to b_{n+1}. The area under the curve between t_n and t_{n+1} is labeled with the integral of R(t) dt. The drop at t_n is labeled b_n, and the drop at t_{n+1} is labeled d_{n+1}. The label T1602830-97 is at the bottom right.](bbce254e33d654e2077bd1e3e9beae8a_img.jpg) + +Figure B.1/H.263 – HRD buffer occupancy. A graph showing HRD buffer occupancy (bit) on the y-axis and Time (CIF interval) on the x-axis. The y-axis has a horizontal dashed line at B. The x-axis has tick marks for t\_n and t\_{n+1}. The graph shows a sawtooth-like pattern where the buffer occupancy increases linearly from the origin, reaches a peak at t\_n, then drops to b\_n. It increases again, reaching a peak at t\_{n+1}, and then drops to b\_{n+1}. The area under the curve between t\_n and t\_{n+1} is labeled with the integral of R(t) dt. The drop at t\_n is labeled b\_n, and the drop at t\_{n+1} is labeled d\_{n+1}. The label T1602830-97 is at the bottom right. + +NOTE – Time $(t_{n+1} - t_n)$ is an integer number of CIF picture periods (1/29.97, 2/29.97, 3/29.97, ...). + +**Figure B.1/H.263 – HRD buffer occupancy** + +# Annex C + +## Considerations for multipoint + +The following facilities are provided to support switched multipoint operation. + +## C.1 Freeze picture request + +Causes the decoder to freeze its displayed picture until a freeze picture release signal is received or a time-out period of at least six seconds has expired. The transmission of this signal is by external means (for example, ITU-T Rec. H.245). Note that a similar command may also be sent using supplemental enhancement information within the picture header of the video bitstream (see L.4). + +## C.2 Fast update request + +Causes the encoder to encode its next picture in INTRA mode with coding parameters such as to avoid buffer overflow. The transmission method for this signal is by external means (for example, ITU-T Rec. H.245). + +## C.3 Freeze picture release + +A signal from an encoder which has responded to a fast update request and allows a decoder to exit from its freeze picture mode and display decoded pictures in the normal manner. This signal is transmitted by PTYPE (see 5.1.3) in the picture header of the first picture coded in response to the fast update request. + +## C.4 Continuous Presence Multipoint and Video Multiplexing (CPM) + +NOTE 1 – Not used for ITU-T Rec. H.324. + +In this Recommendation, a negotiable Continuous Presence Multipoint and Video Multiplexing mode is provided in which up to four independent H.263 bitstreams can be multiplexed as independent "Sub-Bitstreams" in one new video bitstream with use of the PSBI, GSBI, SSBI, and ESBI fields. Capability exchange for this mode is done by external means (for example, ITU-T Rec. H.242). Reference Picture Selection back-channel data for responding to independent Sub-Bitstreams is supported using the BCPM and BSBI fields. + +When in CPM mode, the CPM field shall be set to "1" in each of the independent H.263 Sub-Bitstreams. Sub-Bitstreams are identified by a stream identifier number using the Sub-Bitstream Indicators (SBIs) in the Picture and GOB or slice and EOSBS headers of each H.263 bitstream. The SBI indicates the number of the H.263 bitstream to which that header and all following information until the next Picture or GOB header or slice header in the composed video bitstream belongs. + +Each Sub-Bitstream is considered as a normal H.263 bitstream and shall therefore comply with the capabilities that are exchanged by external means. The information for the different H.263 bitstreams is not transmitted in any special predefined order, an SBI can have any value independent from preceding SBIs and the picture rates for the different H.263 bitstreams may be different. The information in each individual bitstream is also completely independent from the information in the other bitstreams. For example, the GFID codewords in one Sub-Bitstream are not influenced by GFID or PTYPE codewords in other Sub-Bitstreams. Similarly, the mode state inference rules when using an extended picture type (PLUSPTYPE) in the picture header and all other aspects of the video bitstream operation shall operate independently and separately for each Sub-Bitstream. + +As a matter of convention, the Sub-Bitstream with the lowest Sub-Bitstream identifier number (sent in SBI) is considered to have the highest priority in situations in which some conflict of resource + +requirements may necessitate a choice of priority (unless a different priority convention is established by external means). + +In order to mark the end of each Sub-Bitstream of the CPM mode, a syntax is provided as shown in Figure C.1, provided the ability to send this added syntax is first negotiated by external means (while CPM operation was defined in Version 1 of this Recommendation, the end of Sub-Bitstream syntax was added in Version 2 and thus is not considered a part of Version 1 CPM operation). The end of Sub-Bitstream syntax (ESTUF + EOSBS + ESBI) marks the end of each Sub-Bitstream, rather than the end of the entire stream as done by an EOS code. + +NOTE 2 – No ability to negotiate CPM Sub-Bitstream operation as defined herein for ITU-T Rec. H.263 was adopted into any ITU-T Recommendations for terminals (such as ITU-T Rec. H.324) prior to the creation of Version 2 of this Recommendation. Thus, any external negotiation of CPM operation adopted into a future H-series terminal Recommendation shall imply support for the end of Sub-Bitstream syntax unless otherwise specified in the H-series terminal Recommendation. + +There are three parts to the end of Sub-Bitstream syntax. Following mandatory byte alignment using ESTUF, an EOSBS codeword of 23 bits is sent (corresponding to a GOB header with GN = 30, which is otherwise unused in the syntax, followed by a single zero-valued bit which is reserved for future use). The EOSBS codeword is then followed by a two-bit ESBI codeword indicating which Sub-Bitstream is affected. This pair of codewords signifies that the sending of data for the associated Sub-Bitstream has ended and that any subsequent data sent for the same Sub-Bitstream shall be entirely independent from that which came before the EOSBS. In particular, the next picture for the Sub-Bitstream after the EOSBS code shall not be an INTER picture or any other picture type which can use forward temporal prediction (an I- or EI-picture is allowed, but a P-picture, PB-frame, Improved PB-frame, B-picture, or EP-picture is not). + +The syntax of EOSBS and ESBI is described in the following subclauses. ESTUF is described in 5.1.26. + +![](3c04b14104f95eb8f7100f6d497d956e_img.jpg) + +| | | | +|-------|-------|------| +| ESTUF | EOSBS | ESBI | +|-------|-------|------| + +**Figure C.1/H.263 – Syntax diagram for End of Sub-Bitstream Indicators** + +### **C.4.1 End Of Sub-Bitstream code (EOSBS) (23 bits)** + +The EOSBS code is a codeword of 23 bits. Its value is 0000 0000 0000 0000 1 11110 0. It is up to the encoder whether to insert this codeword or not. EOSBS should not be sent unless at least one picture header has previously been sent for the same Sub-Bitstream indicated in the following ESBI field, and shall not be sent unless the capability to send EOSBS has been negotiated by external means. EOSBS codes shall be byte aligned. This is achieved by inserting ESTUF before the EOSBS start code such that the first bit of the EOSBS start code is the first (most significant) bit of a byte (see 5.1.26). + +The EOSBS code indicates that the sending of data for the indicated Sub-Bitstream has stopped and the Sub-Bitstream has been declared over, until re-started by issuance of another picture start code for that Sub-Bitstream. Subsequent pictures with the same Sub-Bitstream identifier number (ESBI) shall be completely independent of and shall not depend in any way on the pictures which were sent prior to the EOSBS code. + +Control and other information associated with the video bitstream in general without specification of which Sub-Bitstreams these codes are meant to apply (such as a Freeze Picture Request or a Fast Update Request sent in ITU-T Rec. H.242) should be presumed to apply to all of the *active* Sub-Bitstreams only. A Sub-Bitstream is considered active if at least one picture start code has been received for the Sub-Bitstream and the last data sent which was applicable to that Sub-Bitstream was not an EOS or EOSBS + ESBI. + +### C.4.2 Ending Sub-Bitstream Indicator (ESBI) (2 bits) + +ESBI is a fixed length codeword of two bits which follows immediately after EOSBS. It indicates the Sub-Bitstream number of the ending Sub-Bitstream. Its value is the natural two-bit binary representation of the Sub-Bitstream number. + +# Annex D + +## Unrestricted Motion Vector mode + +This annex describes the optional Unrestricted Motion Vector mode of this Recommendation. The capability of this H.263 mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in PTYPE or PLUSPTYPE. + +The range of motion vectors and the VLC table used for coding the motion vector differences for the Unrestricted Motion Vector mode depend on whether the PLUSPTYPE field of the picture header is present. When PLUSPTYPE is present, the range of motion vectors also depends on the picture size and the value of the UUI field in the picture header. + +## D.1 Motion vectors over picture boundaries + +In the default prediction mode of this Recommendation, motion vectors are restricted such that all pixels referenced by them are within the coded picture area (see 4.2.3). In the Unrestricted Motion Vector mode, however, this restriction is removed and therefore motion vectors *are* allowed to point outside the picture. When a pixel referenced by a motion vector is outside the coded picture area, an edge pixel is used instead. This edge pixel is found by limiting the motion vector to the last full-pixel position inside the coded picture area. Limitation of the motion vector is performed on a pixel basis and separately for each component of the motion vector. + +For example, if the Unrestricted Motion Vector mode is used for a QCIF picture, the referenced pixel value for the luminance component is given by the following formula: + +$$\text{Rumv}(x, y) = \text{R}(x', y')$$ + +where: + +$x, y, x', y'$ = spatial coordinates in the pixel domain + +$\text{Rumv}(x, y)$ = pixel value of the referenced picture at $(x, y)$ when in Unrestricted Motion Vector mode + +$\text{R}(x', y')$ = pixel value of the referenced picture at $(x', y')$ when in Unrestricted Motion Vector mode + +$$x' \begin{cases} = 0 & \text{if } x < 0 \\ = 175 & \text{if } x > 175 \\ = x & \text{otherwise} \end{cases}$$ + +$$y' \begin{cases} = 0 & \text{if } y < 0 \\ = 143 & \text{if } y > 143 \\ = y & \text{otherwise} \end{cases}$$ + +and the coded picture area of $\text{R}(x', y')$ is $0 \leq x' \leq 175$ , $0 \leq y' \leq 143$ . The given boundaries are integer pixel positions; however, $(x', y')$ can also be a half-pixel position within these boundaries. + +### D.1.1 Restrictions for motion vector values + +If PLUSPTYPE is present in the picture header, the motion vector values are restricted such that no element of the $16 \times 16$ or $(8 \times 8)$ region that is selected shall have a horizontal or vertical distance more than 15 pixels outside the coded picture area. Note that this is a smaller extrapolation range than when PLUSPTYPE is not present. + +NOTE 1 – When PLUSPTYPE is absent, the extrapolation range is a maximum of 31.5 pixels outside the coded picture area when the Unrestricted Motion Vector mode is used, and 16 pixels outside the coded picture area when the Advanced Prediction mode (see Annex F) is used without the Unrestricted Motion Vector mode. + +NOTE 2 – When the Advanced Prediction mode (see Annex F) is in use, the motion vector for each $16 \times 16$ or $(8 \times 8)$ region affects a larger areas, due to overlapped block motion compensation. This can cause the effective extrapolation range to increase for the "remote" motion vectors of the Advanced Prediction mode, since the amount of overlapping (4 pixels, or 8 pixels when the Reduced-Resolution Update mode is also in use) adds to the amount of extrapolation required (even though the range of values allowed for each motion vector remains the same as when the Advanced Prediction mode is not in use). + +## D.2 Extension of the motion vector range + +In the default prediction mode, the values for both horizontal and vertical components of the motion vectors are restricted to the range $[-16, 15.5]$ (this is also valid for the forward and backward motion vector components for B-pictures). In the Unrestricted Motion Vector mode, however, the maximum range for vector components is extended. + +If the PLUSPTYPE field is not present in the picture header, the motion vector range is extended to $[-31.5, 31.5]$ , with the restriction that only values that are within a range of $[-16, 15.5]$ around the predictor for each motion vector component can be reached if the predictor is in the range $[-15.5, 16]$ . If the predictor is outside $[-15.5, 16]$ , all values within the range $[-31.5, 31.5]$ with the same sign as the predictor plus the zero value can be reached. So, if $MV_c$ is the motion vector component and $P_c$ is the predictor for it, then: + +$$\begin{aligned} -31.5 \leq MV_c \leq 0 & & \text{if } -31.5 \leq P_c \leq -16 \\ -16 + P_c \leq MV_c \leq 15.5 + P_c & & \text{if } -15.5 \leq P_c \leq 16 \\ 0 \leq MV_c \leq 31.5 & & \text{if } 16.5 \leq P_c \leq 31.5 \end{aligned}$$ + +In the Unrestricted Motion Vector mode, the interpretation of Table 14 for MVD, $MVD_{2,4}$ and MVDB is as follows: + +- If the predictor for the motion vector component is in the range $[-15.5, 16]$ , only the first column of vector differences applies. +- If the predictor for the motion vector component is outside the range $[-15.5, 16]$ , the vector difference from Table 14 shall be used that results in a vector component inside the range $[-31.5, 31.5]$ with the same sign as the predictor (including zero). + +The predictor for MVD and $MVD_{2,4}$ is defined as the median value of the vector components MV1, MV2 and MV3 as defined in 6.1.1 and F.2. For MVDB, the predictor $P_c = (TR_B \times MV)/TR_D$ , where MV represents a vector component for an $8 \times 8$ luminance block in a P-picture (see also G.4). + +If PLUSPTYPE is present, the motion vector range does not depend on the motion vector prediction value. If the UUI field is set to "1" the motion vector range depends on the picture format. For standardized picture formats up to CIF the range is $[-32, 31.5]$ , for those up to 4CIF the range is $[-64, 63.5]$ , and for those up to 16CIF the range is $[-128, 127.5]$ , and for even larger custom picture formats the range is $[-256, 255.5]$ . The horizontal and vertical motion vector ranges may be different for custom picture formats. The horizontal and vertical ranges are specified in Tables D.1 and D.2. + +**Table D.1/H.263 – Horizontal motion vector range when PLUSPTYPE present and UUI = 1** + +| Picture width | Horizontal motion vector range | +|----------------------|---------------------------------------| +| 4, ... , 352 | [-32, 31.5] | +| 356, ... , 704 | [-64, 63.5] | +| 708, ... , 1408 | [-128, 127.5] | +| 1412, ... , 2048 | [-256, 255.5] | + +**Table D.2/H.263 – Vertical motion vector range when PLUSPTYPE present and UUI = 1** + +| Picture height | Vertical motion vector range | +|-----------------------|-------------------------------------| +| 4, ... , 288 | [-32, 31.5] | +| 292, ... , 576 | [-64, 63.5] | +| 580, ... , 1152 | [-128, 127.5] | + +In the Reduced-Resolution Update mode, the specified range applies to the pseudo motion vectors. This implies that the resulting actual motion vector range is enlarged to approximately double size (see also Annex Q). + +If UUI is set to "01", the motion vectors are not limited except by their distance to the coded area border as explained in D.1.1. The same limitation applies to the actual motion vectors (not just the pseudo motion vectors) in the Reduced-Resolution Update mode. + +To encode the motion vectors when PLUSPTYPE is present, Table D.3 is used to encode the difference between the motion vector and the motion vector prediction. Every entry in Table D.3 has a single value (in contrast to Table 14). The motion vector range and the use of Table D.3 to encode motion vector data apply to all picture types when PLUSPTYPE is present. + +Motion vectors differences are always coded as a pair of a horizontal and a vertical component. If a pair equals (0.5, 0.5) six consecutive zeros are produced. To prevent start code emulation, this occurrence shall be followed by one bit set to "1". This corresponds to sending one additional zero motion vector component. + +**Table D.3/H.263 – Motion Vector Table used when PLUSPTYPE present** + +| Absolute value of vector difference in half-pixel units | Number of bits | Codes | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 1 | 1 | +| 1 | 3 | 0s0 | +| "x 0 "+2 (2:3) | 5 | 0x 0 1s0 | +| "x 1 x 0 "+4 (4:7) | 7 | 0x 1 1x 0 1s0 | +| "x 2 x 1 x 0 "+8 (8:15) | 9 | 0x 2 1x 1 1x 0 1s0 | +| "x 3 x 2 x 1 x 0 "+16 (16:31) | 11 | 0x 3 1x 2 1x 1 1x 0 1s0 | +| "x 4 x 3 x 2 x 1 x 0 "+32 (32:63) | 13 | 0x 4 1x 3 1x 2 1x 1 1x 0 1s0 | +| "x 5 x 4 x 3 x 2 x 1 x 0 "+64 (64:127) | 15 | 0x 5 1x 4 1x 3 1x 2 1x 1 1x 0 1s0 | +| "x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+128 (128:255) | 17 | 0x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 1s0 | +| "x 7 x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+256 (256:511) | 19 | 0x 7 1x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 1s0 | +| "x 8 x 7 x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+512 (512:1023) | 21 | 0x 8 1x 7 1x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 1s0 | +| "x 9 x 8 x 7 x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+1024 (1024:2047) | 23 | 0x 9 1x 8 1x 7 1x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 1s0 | +| "x 10 x 9 x 8 x 7 x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+2048 (2048:4095) | 25 | 0x 10 1x 9 1x 8 1x 7 1x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 1s0 | + +Table D.3 is a regularly constructed reversible table. Each row represents an interval of motion vector differences in half-pixel units. The bits "...x1x0" denote all bits following the leading "1" in the binary representation of the absolute value of the motion vector difference. The bit "s" denotes the sign of the motion vector difference, "0" for positive and "1" for negative. The binary representation of the motion vector difference is interleaved with bits that indicate if the code continues or ends. For example, the motion vector difference -13 has sign s = 1 and binary representation 1x2x1x0 = 1101. It is encoded as 0 x21 x11 x01 s0 = 0 11 01 11 10. The 0 in the second position of the last group of two bits indicates the end of the code. + +# Annex E + +# Syntax-based Arithmetic Coding mode + +## E.1 Introduction + +In the Variable Length Coding/Decoding (VLC/VLD) as described in clause 5, a symbol is VLC encoded using a specific table based on the syntax of the coder. This table typically stores lengths and values of the VLC code words. The symbol is mapped to an entry of the table in a table look-up operation, and then the binary code word specified by the entry is sent out normally to a buffer for transmitting to the receiver. In VLD decoding, the received bitstream is matched entry by entry in a specific table based on the syntax of the coder. This table must be the same as the one used in the encoder for encoding the current symbol. The matched entry in the table is then mapped back to the corresponding symbol which is the end result of the VLD decoder and is then used for recovering the video pictures. This VLC/VLD process implies that each symbol must be encoded into a fixed integral number of bits. Removing this restriction of fixed integral number of bits for symbols can lead to reductions of resulting bit rates, which can be achieved by arithmetic coding. + +This annex describes the optional Syntax-based Arithmetic Coding (SAC) mode of this Recommendation. In this mode, all the corresponding variable length coding/decoding operations of + +this Recommendation are replaced with arithmetic coding/decoding operations. The capability of this H.263 mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in PTYPE. + +## E.2 Specification of SAC encoder + +In SAC mode, a symbol is encoded by using a specific array of integers (or a model) based on the syntax of the coder and by calling the following procedure which is specified in C language. + +``` +#define q1 16384 +#define q2 32768 +#define q3 49152 +#define top 65535 + +static long low, high, opposite_bits, length; +void encode_a_symbol(int index, int cumul_freq[ ]) +{ + length = high - low + 1; + high = low - 1 + (length * cumul_freq[index]) / cumul_freq[0]; + low += (length * cumul_freq[index+1]) / cumul_freq[0]; + for ( ; ; ) { + if (high < q2) { + send out a bit "0" to PSC_FIFO; + while (opposite_bits > 0) { + send out a bit "1" to PSC_FIFO; + opposite_bits--; + } + } + else if (low >= q2) { + send out a bit "1" to PSC_FIFO; + while (opposite_bits > 0) { + send out a bit "0" to PSC_FIFO; + opposite_bits--; + } + low -= q2; + high -= q2; + } + else if (low >= q1 && high < q3) { + opposite_bits += 1; + low -= q1; + high -= q1; + } + else break; + + low *= 2; + high = 2 * high+1; + } +} +``` + +The values of low, high and opposite\_bits are initialized to 0, top and 0, respectively. PSC\_FIFO is a FIFO for buffering the output bits from the arithmetic encoder. The model is specified through cumul\_freq[ ], and the symbol is specified using its index in the model. + +## E.3 Specification of SAC decoder + +In SAC decoder, a symbol is decoded by using a specific model based on the syntax and by calling the following procedure which is specified in C language. + +``` +static long low, high, code_value, bit, length, index, cum; +int decode_a_symbol(int cumul_freq[ ]) +{ + length = high - low + 1; + cum = (-1 + (code_value - low + 1) * cumul_freq[0]) / length; + for (index = 1; cumul_freq[index] > cum; index++); + high = low - 1 + (length * cumul_freq[index-1]) / cumul_freq[0]; + low += (length * cumul_freq[index]) / cumul_freq[0]; + for ( ; ; ) { + if (high < q2); + else if (low >= q2) { + code_value -= q2; + low -= q2; + high -= q2; + } + else if (low >= q1 && high < q3) { + code_value -= q1; + low -= q1; + high -= q1; + } + else break; + + low *= 2; + high = 2 * high + 1; + get bit from PSC_FIFO; + code_value = 2 * code_value + bit; + } + return (index-1); +} +``` + +Again the model is specified through `cumul_freq[ ]`. The decoded symbol is returned through its index in the model. `PSC_FIFO` is a FIFO for buffering the incoming bitstream. The decoder is initialized to start decoding an arithmetic coded bitstream by calling the following procedure. + +``` +void decoder_reset( ) +{ + code_value = 0; + low = 0; + high = top; + for (int i = 1; i <= 16; i++) { + get bit from PSC_FIFO; + code_value = 2 * code_value + bit; + } +} +``` + +## E.4 Syntax + +As in VLC table mode of this Recommendation, the syntax of the symbols is partitioned into four layers: Picture, Group of Blocks, Macroblock and Block. The syntax of the top three layers remain exactly the same. The syntax of the Block layer also remains quite similar, but is illustrated in Figure E.1. + +![Diagram of the SAC Block layer structure. It shows a sequence of symbols: INTRADC, TCOEF1, TCOEF2, TCOEF3, and TCOEFr. Arrows indicate the flow of data. A 'Block layer' label is at the top left. Arrows from the top of each symbol box point to a common horizontal line, which then branches down to the next symbol. Arrows from the bottom of each symbol box point to a common horizontal line at the bottom, which then branches up to the next symbol. The diagram is labeled T1602840-97 at the bottom right.](af6c3f383ddc0c142cdd7e186cc78199_img.jpg) + +Diagram of the SAC Block layer structure. It shows a sequence of symbols: INTRADC, TCOEF1, TCOEF2, TCOEF3, and TCOEFr. Arrows indicate the flow of data. A 'Block layer' label is at the top left. Arrows from the top of each symbol box point to a common horizontal line, which then branches down to the next symbol. Arrows from the bottom of each symbol box point to a common horizontal line at the bottom, which then branches up to the next symbol. The diagram is labeled T1602840-97 at the bottom right. + +**Figure E.1/H.263 – Structure of SAC Block layer** + +In Figure E.1, TCOEF1, TCOEF2, TCOEF3 and TCOEFr are LAST-RUN-LEVEL symbols as defined in 5.4.2, and are the possible 1st, 2nd, 3rd and rest of the symbols, respectively. TCOEF1, TCOEF2, TCOEF3 and TCOEFr are only present when one, two, three or more coefficients are present in the block layer, respectively. + +## E.5 PSC\_FIFO + +PSC\_FIFO in encoder or decoder is a FIFO of size > 17 bits. In PSC\_FIFO of encoder, illegal emulations of PSC and GBSC are located and are avoided by stuffing a "1" after each successive appearance of 14 "0"s (which are not part of PSC or GBSC). In PSC\_FIFO of the decoder, the first "1" after each string of 14 "0"s is deleted; if instead a string of 14 "0"s is followed by a "0", it indicates that a legal PSC or GBSC is detected. The exact location of the PSC or GBSC is determined by the next "1" following the string of zeros. + +## E.6 Header layer symbols + +The header layers of the syntax are considered to be those syntactical elements above the block and macroblock layers (see Figure 6 and the syntax specification in the text). The header levels of the basic Version 1 syntax can form three possible strings, (PSTUF)--PSC--TR--PTYPE--PQUANT--CPM--(PSBI)--(TRB-DBQUANT)--PEI--(PSUPP--PEI--...), (GSTUF)--GBSC--GN--(GSBI)--GFID--GQUANT, and (ESTUF)--(EOS)--(PSTUF). In the revised syntax of Version 2, the header levels of the syntax can have other structures (see Figure 6 and the syntax specification in the text). The header level syntax strings are directly sent to PSC\_FIFO as in the normal VLC table mode of this Recommendation at encoder side, and are directly sent out from PSC\_FIFO in the decoder after a legal PSC, GBSC, SSC, EOS, or EOSBS is detected. + +If a header is not the first in a video session, the arithmetic encoder needs to be reset before sending the header by calling the following procedure. This procedure shall also be called at the end of a video session if (ESTUF)--EOS [or (ESTUF)--EOSBS for the Sub-Bitstream for which the last header was sent] is not sent. + +``` +void encoder_flush( ) +{ + opposite_bits++; + if (low < q1) { + send out a bit "0" to PSC_FIFO; + while (opposite_bits > 0) { + send out a bit "1" to PSC_FIFO; + opposite_bits--; + } + } +} +``` + +``` + + } + } + else { + send out a bit "1" to PSC_FIFO; + while (opposite_bits > 0) { + send out a bit "0" to PSC_FIFO; + opposite_bits--; + } + } + low = 0; + high = top; +} + +``` + +In the decoder, after each fixed length symbol string, procedure **decoder\_reset** is called. + +## E.7 Macroblock and Block layer symbols + +Models for the macroblock and block layer symbols are included in E.8. The indices as given in the VLC tables of clause 5 are used for the indexing of the integers in the models. + +The model for COD in P-pictures is named **cumf\_COD**. The index for COD being "0" is 0, and is 1 for COD being "1". The model for MCBPC in P-pictures is named **cumf\_MCBPC\_no4MVQ** unless PLUSPTYPE is present in the picture header and either the Advanced Prediction mode (Annex F) or the Deblocking Filter mode (Annex J) is in use, in which case the model is named **cumf\_MCBPC\_4MVQ**. The indexes for MCBPC are defined in Table 7 for I-pictures and Table 8 for P-pictures. The model for MCBPC in I-pictures is named by **cumf\_MCBPC\_intra**. + +The model for MODB is **cumf\_MODB\_G** if Annex G is used or **cumf\_MODB\_M** if Annex M is used. The indexes for MODB are defined in Table 11 or Table M.1, respectively. The model for CBPBn, n = 1, 2, ..., 4, is **cumf\_YCBPB**, and the model for CBPBn, n = 5, 6, is **cumf\_UVCBPB**, with index 0 for CBPBn = 0 and index 1 for CBPBn = 1. + +The model for CBPY is **cumf\_CBPY** in INTER macroblocks and **cumf\_CBPY\_intra** in INTRA macroblocks. The model for DQUANT is **cumf\_DQUANT**. The indexing for CBPY and DQUANT is defined in Tables 12 and 13, respectively. + +The model for MVD, MVD2-4 and MVDB is **cumf\_MVD** and the model for INTRADC is **cumf\_INTRADC**. The indexing is defined in Tables 14 and 15, respectively. + +A non-escaped TCOEF consists of a symbol for TCOEF1/2/3/r followed by a symbol, SIGN, for the sign of the TCOEF. The models for TCOEF1, TCOEF2, TCOEF3 and TCOEFr in INTER blocks are **cumf\_TCOEF1**, **cumf\_TCOEF2**, **cumf\_TCOEF3**, **cumf\_TCOEFr**. The models for INTRA blocks are **cumf\_TCOEF1\_intra**, **cumf\_TCOEF2\_intra**, **cumf\_TCOEF3\_intra**, **cumf\_TCOEFr\_intra**. For all TCOEFs the indexing is defined in Table 16. The model for SIGN is **cumf\_SIGN**. The indexing for SIGN is 0 for positive sign and 1 for negative sign. + +The models for LAST, RUN, LEVEL after ESCAPE are **cumf\_LAST** (**cumf\_LAST\_intra**), **cumf\_RUN** (**cumf\_RUN\_intra**), **cumf\_LEVEL** (**cumf\_LEVEL\_intra**) for INTER (INTRA) blocks. The indexing for LAST is 0 for LAST = 0 and 1 for LAST = 1, while the indexing for RUN and LEVEL is defined in Table 17. + +The model for INTRA\_MODE is **cumf\_INTRA\_AC\_DC**. The indexing is defined in Table I.1. + +## E.8 SAC models + +``` +int cumf_COD[3]={16383, 6849, 0}; +``` + +``` +int cumf_MCBPC_no4MVQ[22]={16383, 4105, 3088, 2367, 1988, 1621, 1612, 1609, 1608, 496, 353, 195, 77, 22, 17, 12, 5, 4, 3, 2, 1, 0}; +``` + +``` + +int cumf_MCBPC_4MVQ[26]={16383, 6880, 6092, 5178, 4916, 3965, 3880, 3795, 3768, 1491, +1190, 889, 655, 442, 416, 390, 360, 337, 334, 331, 327, 326, 88, 57, 26, 0}; +int cumf_MCBPC_intra[10]={16383, 7410, 6549, 5188, 442, 182, 181, 141, 1, 0}; +int cumf_MODB_G[4]={16383, 6062, 2130, 0}; +int cumf_MODB_M[7] = {16383, 6717, 4568, 2784, 1370, 655, 0}; +int cumf_YCBPB[3]={16383, 6062, 0}; +int cumf_UVCBPB[3]={16383, 491, 0}; +int cumf_CBPY[17]={16383, 14481, 13869, 13196, 12568, 11931, 11185, 10814, 9796, 9150, +8781, 7933, 6860, 6116, 4873, 3538, 0}; +int cumf_CBPY_intra[17]={16383, 13619, 13211, 12933, 12562, 12395, 11913, 11783, 11004, +10782, 10689, 9928, 9353, 8945, 8407, 7795, 0}; +int cumf_DQUANT[5]={16383, 12287, 8192, 4095, 0}; +int cumf_MVD[65]={16383, 16380, 16369, 16365, 16361, 16357, 16350, 16343, 16339, 16333, +16326, 16318, 16311, 16306, 16298, 16291, 16283, 16272, 16261, 16249, 16235, 16222, 16207, +16175, 16141, 16094, 16044, 15936, 15764, 15463, 14956, 13924, 11491, 4621, 2264, 1315, 854, +583, 420, 326, 273, 229, 196, 166, 148, 137, 123, 114, 101, 91, 82, 76, 66, 59, 53, 46, 36, 30, 26, +24, 18, 14, 10, 5, 0}; +int cumf_INTRADC[255]={16383, 16380, 16379, 16378, 16377, 16376, 16370, 16361, 16360, +16359, 16358, 16357, 16356, 16355, 16343, 16238, 16237, 16236, 16230, 16221, 16220, 16205, +16190, 16169, 16151, 16130, 16109, 16094, 16070, 16037, 16007, 15962, 15938, 15899, 15854, +15815, 15788, 15743, 15689, 15656, 15617, 15560, 15473, 15404, 15296, 15178, 15106, 14992, +14868, 14738, 14593, 14438, 14283, 14169, 14064, 14004, 13914, 13824, 13752, 13671, 13590, +13515, 13458, 13380, 13305, 13230, 13143, 13025, 12935, 12878, 12794, 12743, 12656, 12596, +12521, 12443, 12359, 12278, 12200, 12131, 12047, 12002, 11948, 11891, 11828, 11744, 11663, +11588, 11495, 11402, 11288, 11204, 11126, 11039, 10961, 10883, 10787, 10679, 10583, 10481, +10360, 10227, 10113, 9961, 9828, 9717, 9584, 9485, 9324, 9112, 9019, 8908, 8766, 8584, 8426, +8211, 7920, 7663, 7406, 7152, 6904, 6677, 6453, 6265, 6101, 5904, 5716, 5489, 5307, 5056, 4850, +4569, 4284, 3966, 3712, 3518, 3342, 3206, 3048, 2909, 2773, 2668, 2596, 2512, 2370, 2295, 2232, +2166, 2103, 2022, 1956, 1887, 1830, 1803, 1770, 1728, 1674, 1635, 1599, 1557, 1500, 1482, 1434, +1389, 1356, 1317, 1284, 1245, 1200, 1179, 1140, 1110, 1092, 1062, 1044, 1035, 1014, 1008, 993, +981, 954, 936, 912, 894, 876, 864, 849, 828, 816, 801, 792, 777, 756, 732, 690, 660, 642, 615, 597, +576, 555, 522, 489, 459, 435, 411, 405, 396, 387, 375, 360, 354, 345, 344, 329, 314, 293, 278, 251, +236, 230, 224, 215, 214, 208, 199, 193, 184, 178, 169, 154, 127, 100, 94, 73, 37, 36, 35, 34, 33, 32, +31, 30, 29, 28, 27, 26, 20, 19, 18, 17, 16, 15, 9, 0}; +int cumf_TCOEF1[104]={16383, 13455, 12458, 12079, 11885, 11800, 11738, 11700, 11681, +11661, 11651, 11645, 11641, 10572, 10403, 10361, 10346, 10339, 10335, 9554, 9445, 9427, 9419, +9006, 8968, 8964, 8643, 8627, 8624, 8369, 8354, 8352, 8200, 8192, 8191, 8039, 8036, 7920, 7917, +7800, 7793, 7730, 7727, 7674, 7613, 7564, 7513, 7484, 7466, 7439, 7411, 7389, 7373, 7369, 7359, +7348, 7321, 7302, 7294, 5013, 4819, 4789, 4096, 4073, 3373, 3064, 2674, 2357, 2177, 1975, 1798, +1618, 1517, 1421, 1303, 1194, 1087, 1027, 960, 890, 819, 758, 707, 680, 656, 613, 566, 534, 505, +475, 465, 449, 430, 395, 358, 335, 324, 303, 295, 286, 272, 233, 215, 0}; +int cumf_TCOEF2[104]={16383, 13582, 12709, 12402, 12262, 12188, 12150, 12131, 12125, +12117, 12113, 12108, 12104, 10567, 10180, 10070, 10019, 9998, 9987, 9158, 9037, 9010, 9005, +8404, 8323, 8312, 7813, 7743, 7726, 7394, 7366, 7364, 7076, 7062, 7060, 6810, 6797, 6614, 6602, +6459, 6454, 6304, 6303, 6200, 6121, 6059, 6012, 5973, 5928, 5893, 5871, 5847, 5823, 5809, 5796, +5781, 5771, 5763, 5752, 4754, 4654, 4631, 3934, 3873, 3477, 3095, 2758, 2502, 2257, 2054, 1869, + +``` + +1715, 1599, 1431, 1305, 1174, 1059, 983, 901, 839, 777, 733, 683, 658, 606, 565, 526, 488, 456, 434, 408, 380, 361, 327, 310, 296, 267, 259, 249, 239, 230, 221, 214, 0}; + +int cumf\_TCOEF3[104]={16383, 13532, 12677, 12342, 12195, 12112, 12059, 12034, 12020, 12008, 12003, 12002, 12001, 10586, 10297, 10224, 10202, 10195, 10191, 9223, 9046, 8999, 8987, 8275, 8148, 8113, 7552, 7483, 7468, 7066, 7003, 6989, 6671, 6642, 6631, 6359, 6327, 6114, 6103, 5929, 5918, 5792, 5785, 5672, 5580, 5507, 5461, 5414, 5382, 5354, 5330, 5312, 5288, 5273, 5261, 5247, 5235, 5227, 5219, 4357, 4277, 4272, 3847, 3819, 3455, 3119, 2829, 2550, 2313, 2104, 1881, 1711, 1565, 1366, 1219, 1068, 932, 866, 799, 750, 701, 662, 605, 559, 513, 471, 432, 403, 365, 336, 312, 290, 276, 266, 254, 240, 228, 223, 216, 206, 199, 192, 189, 0}; + +int cumf\_TCOEFr[104]={16383, 13216, 12233, 11931, 11822, 11776, 11758, 11748, 11743, 11742, 11741, 11740, 11739, 10203, 9822, 9725, 9691, 9677, 9674, 8759, 8609, 8576, 8566, 7901, 7787, 7770, 7257, 7185, 7168, 6716, 6653, 6639, 6276, 6229, 6220, 5888, 5845, 5600, 5567, 5348, 5327, 5160, 5142, 5004, 4900, 4798, 4743, 4708, 4685, 4658, 4641, 4622, 4610, 4598, 4589, 4582, 4578, 4570, 4566, 3824, 3757, 3748, 3360, 3338, 3068, 2835, 2592, 2359, 2179, 1984, 1804, 1614, 1445, 1234, 1068, 870, 739, 668, 616, 566, 532, 489, 453, 426, 385, 357, 335, 316, 297, 283, 274, 266, 259, 251, 241, 233, 226, 222, 217, 214, 211, 209, 208, 0}; + +int cumf\_TCOEF1\_intra[104]={16383, 13383, 11498, 10201, 9207, 8528, 8099, 7768, 7546, 7368, 7167, 6994, 6869, 6005, 5474, 5220, 5084, 4964, 4862, 4672, 4591, 4570, 4543, 4397, 4337, 4326, 4272, 4240, 4239, 4212, 4196, 4185, 4158, 4157, 4156, 4140, 4139, 4138, 4137, 4136, 4125, 4124, 4123, 4112, 4111, 4110, 4109, 4108, 4107, 4106, 4105, 4104, 4103, 4102, 4101, 4100, 4099, 4098, 4097, 3043, 2897, 2843, 1974, 1790, 1677, 1552, 1416, 1379, 1331, 1288, 1251, 1250, 1249, 1248, 1247, 1236, 1225, 1224, 1223, 1212, 1201, 1200, 1199, 1198, 1197, 1196, 1195, 1194, 1193, 1192, 1191, 1190, 1189, 1188, 1187, 1186, 1185, 1184, 1183, 1182, 1181, 1180, 1179, 0}; + +int cumf\_TCOEF2\_intra[104]={16383, 13242, 11417, 10134, 9254, 8507, 8012, 7556, 7273, 7062, 6924, 6839, 6741, 6108, 5851, 5785, 5719, 5687, 5655, 5028, 4917, 4864, 4845, 4416, 4159, 4074, 3903, 3871, 3870, 3765, 3752, 3751, 3659, 3606, 3580, 3541, 3540, 3514, 3495, 3494, 3493, 3474, 3473, 3441, 3440, 3439, 3438, 3425, 3424, 3423, 3422, 3421, 3420, 3401, 3400, 3399, 3398, 3397, 3396, 2530, 2419, 2360, 2241, 2228, 2017, 1687, 1576, 1478, 1320, 1281, 1242, 1229, 1197, 1178, 1152, 1133, 1114, 1101, 1088, 1087, 1086, 1085, 1072, 1071, 1070, 1069, 1068, 1067, 1066, 1065, 1064, 1063, 1062, 1061, 1060, 1059, 1058, 1057, 1056, 1055, 1054, 1053, 1052, 0}; + +int cumf\_TCOEF3\_intra[104]={16383, 12741, 10950, 10071, 9493, 9008, 8685, 8516, 8385, 8239, 8209, 8179, 8141, 6628, 5980, 5634, 5503, 5396, 5327, 4857, 4642, 4550, 4481, 4235, 4166, 4151, 3967, 3922, 3907, 3676, 3500, 3324, 3247, 3246, 3245, 3183, 3168, 3084, 3069, 3031, 3030, 3029, 3014, 3013, 2990, 2975, 2974, 2973, 2958, 2943, 2928, 2927, 2926, 2925, 2924, 2923, 2922, 2921, 2920, 2397, 2298, 2283, 1891, 1799, 1591, 1445, 1338, 1145, 1068, 1006, 791, 768, 661, 631, 630, 615, 592, 577, 576, 561, 546, 523, 508, 493, 492, 491, 476, 475, 474, 473, 472, 471, 470, 469, 468, 453, 452, 451, 450, 449, 448, 447, 446, 0}; + +int cumf\_TCOEFr\_intra[104]={16383, 12514, 10776, 9969, 9579, 9306, 9168, 9082, 9032, 9000, 8981, 8962, 8952, 7630, 7212, 7053, 6992, 6961, 6940, 6195, 5988, 5948, 5923, 5370, 5244, 5210, 4854, 4762, 4740, 4384, 4300, 4288, 4020, 3968, 3964, 3752, 3668, 3511, 3483, 3354, 3322, 3205, 3183, 3108, 3046, 2999, 2981, 2974, 2968, 2961, 2955, 2949, 2943, 2942, 2939, 2935, 2934, 2933, 2929, 2270, 2178, 2162, 1959, 1946, 1780, 1651, 1524, 1400, 1289, 1133, 1037, 942, 849, 763, 711, 591, 521, 503, 496, 474, 461, 449, 442, 436, 426, 417, 407, 394, 387, 377, 373, 370, 367, 366, 365, 364, 363, 362, 358, 355, 352, 351, 350, 0}; + +int cumf\_SIGN[3]={16383, 8416, 0}; + +int cumf\_LAST[3]={16383, 9469, 0}; + +int cumf\_LAST\_intra[3]={16383, 2820, 0}; + +int cumf\_RUN[65]={16383, 15310, 14702, 13022, 11883, 11234, 10612, 10192, 9516, 9016, 8623, 8366, 7595, 7068, 6730, 6487, 6379, 6285, 6177, 6150, 6083, 5989, 5949, 5922, 5895, 5828, 5774, 5773, 5394, 5164, 5016, 4569, 4366, 4136, 4015, 3867, 3773, 3692, 3611, 3476, 3341, 3301, 2787, 2503, 2219, 1989, 1515, 1095, 934, 799, 691, 583, 435, 300, 246, 206, 125, 124, 97, 57, 30, 3, 2, 1, 0}; + +int cumf\_RUN\_intra[65]={16383, 10884, 8242, 7124, 5173, 4745, 4246, 3984, 3034, 2749, 2607, 2298, 966, 681, 396, 349, 302, 255, 254, 253, 206, 159, 158, 157, 156, 155, 154, 153, 106, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0}; + +int cumf\_LEVEL[255]={16383, 16382, 16381, 16380, 16379, 16378, 16377, 16376, 16375, 16374, 16373, 16372, 16371, 16370, 16369, 16368, 16367, 16366, 16365, 16364, 16363, 16362, 16361, 16360, 16359, 16358, 16357, 16356, 16355, 16354, 16353, 16352, 16351, 16350, 16349, 16348, 16347, 16346, 16345, 16344, 16343, 16342, 16341, 16340, 16339, 16338, 16337, 16336, 16335, 16334, 16333, 16332, 16331, 16330, 16329, 16328, 16327, 16326, 16325, 16324, 16323, 16322, 16321, 16320, 16319, 16318, 16317, 16316, 16315, 16314, 16313, 16312, 16311, 16310, 16309, 16308, 16307, 16306, 16305, 16304, 16303, 16302, 16301, 16300, 16299, 16298, 16297, 16296, 16295, 16294, 16293, 16292, 16291, 16290, 16289, 16288, 16287, 16286, 16285, 16284, 16283, 16282, 16281, 16280, 16279, 16278, 16277, 16250, 16223, 16222, 16195, 16154, 16153, 16071, 15989, 15880, 15879, 15878, 15824, 15756, 15674, 15606, 15538, 15184, 14572, 13960, 10718, 7994, 5379, 2123, 1537, 992, 693, 611, 516, 448, 421, 380, 353, 352, 284, 257, 230, 203, 162, 161, 160, 133, 132, 105, 104, 103, 102, 101, 100, 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0}; + +int cumf\_LEVEL\_intra[255]={16383, 16379, 16378, 16377, 16376, 16375, 16374, 16373, 16372, 16371, 16370, 16369, 16368, 16367, 16366, 16365, 16364, 16363, 16362, 16361, 16360, 16359, 16358, 16357, 16356, 16355, 16354, 16353, 16352, 16351, 16350, 16349, 16348, 16347, 16346, 16345, 16344, 16343, 16342, 16341, 16340, 16339, 16338, 16337, 16336, 16335, 16334, 16333, 16332, 16331, 16330, 16329, 16328, 16327, 16326, 16325, 16324, 16323, 16322, 16321, 16320, 16319, 16318, 16317, 16316, 16315, 16314, 16313, 16312, 16311, 16268, 16267, 16224, 16223, 16180, 16179, 16136, 16135, 16134, 16133, 16132, 16131, 16130, 16129, 16128, 16127, 16126, 16061, 16018, 16017, 16016, 16015, 16014, 15971, 15970, 15969, 15968, 15925, 15837, 15794, 15751, 15750, 15749, 15661, 15618, 15508, 15376, 15288, 15045, 14913, 14781, 14384, 13965, 13502, 13083, 12509, 12289, 12135, 11892, 11738, 11429, 11010, 10812, 10371, 9664, 9113, 8117, 8116, 8028, 6855, 5883, 4710, 4401, 4203, 3740, 3453, 3343, 3189, 2946, 2881, 2661, 2352, 2132, 1867, 1558, 1382, 1250, 1162, 1097, 1032, 967, 835, 681, 549, 439, 351, 350, 307, 306, 305, 304, 303, 302, 301, 300, 299, 298, 255, 212, 211, 210, 167, 166, 165, 164, 163, 162, 161, 160, 159, 158, 115, 114, 113, 112, 111, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0}; + +int cumf\_INTRA\_AC\_DC[4]={16383, 9229, 5461, 0}; + +# Annex F + +## Advanced Prediction mode + +## F.1 Introduction + +This annex describes the optional Advanced Prediction mode of this Recommendation, including overlapped block motion compensation and the possibility of four motion vectors per macroblock. The capability of this mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in PTYPE. In the Advanced Prediction mode, motion vectors are allowed to cross picture boundaries as is the case in the Unrestricted Motion Vector mode (for the description of this technique, refer to D.1). The extended motion vector range feature of the Unrestricted Motion Vector mode is not automatically included in the Advanced Prediction mode, and only is active if the Unrestricted Motion Vector mode is selected. If the Advanced Prediction mode is used in combination with the PB-frames mode, overlapped motion compensation is only used for prediction of the P-pictures, not for the B-pictures. + +## F.2 Four motion vectors per macroblock + +In this Recommendation, one motion vector per macroblock is used except when in Advanced Prediction mode or Deblocking Filter mode. In this mode, the one/four vectors decision is indicated by the MCBPC codeword for each macroblock. If only one motion vector is transmitted for a certain macroblock, this is defined as four vectors with the same value. If MCBPC indicates that four motion vectors are transmitted for the current macroblock, the information for the first motion vector is transmitted as the codeword MVD and the information for the three additional motion vectors is transmitted as the codewords $MVD_{2-4}$ (see also 5.3.7 and 5.3.8). + +The vectors are obtained by adding predictors to the vector differences indicated by MVD and $MVD_{2-4}$ in a similar way as when only one motion vector per macroblock is present, according to the decision rules given in 6.1.1. Again the predictors are calculated separately for the horizontal and vertical components. However, the candidate predictors MV1, MV2 and MV3 are redefined as indicated in Figure F.1. If only one vector per macroblock is present, MV1, MV2 and MV3 are defined as for the 8 \* 8 block numbered 1 in Figure 5 (this definition is given in the upper left of the four sub-figures of Figure F.1). + +![Figure F.1/H.263 – Redefinition of the candidate predictors MV1, MV2 and MV3 for each of the luminance blocks in a macroblock. The figure shows four sub-diagrams representing different block positions within a macroblock. Each sub-diagram is a 3x3 grid of blocks. The central block is labeled 'MV'. The blocks to its left, top, and right are labeled 'MV1', 'MV2', and 'MV3' respectively. The four sub-diagrams show the 'MV' block at different positions: top-left, top-right, bottom-left, and bottom-right. In the top-left sub-diagram, 'MV' is at (1,1), 'MV1' is at (1,0), 'MV2' is at (0,1), and 'MV3' is at (0,2). In the top-right sub-diagram, 'MV' is at (1,2), 'MV1' is at (1,1), 'MV2' is at (0,1), and 'MV3' is at (0,2). In the bottom-left sub-diagram, 'MV' is at (2,1), 'MV1' is at (2,0), 'MV2' is at (1,1), and 'MV3' is at (1,2). In the bottom-right sub-diagram, 'MV' is at (2,2), 'MV1' is at (2,1), 'MV2' is at (1,1), and 'MV3' is at (1,2).](708e4c9a044ef61f586126676eb2eeb8_img.jpg) + +Figure F.1/H.263 – Redefinition of the candidate predictors MV1, MV2 and MV3 for each of the luminance blocks in a macroblock. The figure shows four sub-diagrams representing different block positions within a macroblock. Each sub-diagram is a 3x3 grid of blocks. The central block is labeled 'MV'. The blocks to its left, top, and right are labeled 'MV1', 'MV2', and 'MV3' respectively. The four sub-diagrams show the 'MV' block at different positions: top-left, top-right, bottom-left, and bottom-right. In the top-left sub-diagram, 'MV' is at (1,1), 'MV1' is at (1,0), 'MV2' is at (0,1), and 'MV3' is at (0,2). In the top-right sub-diagram, 'MV' is at (1,2), 'MV1' is at (1,1), 'MV2' is at (0,1), and 'MV3' is at (0,2). In the bottom-left sub-diagram, 'MV' is at (2,1), 'MV1' is at (2,0), 'MV2' is at (1,1), and 'MV3' is at (1,2). In the bottom-right sub-diagram, 'MV' is at (2,2), 'MV1' is at (2,1), 'MV2' is at (1,1), and 'MV3' is at (1,2). + +T1602850-97 + +**Figure F.1/H.263 – Redefinition of the candidate predictors MV1, MV2 and MV3 for each of the luminance blocks in a macroblock** + +If four vectors are used, each of the motion vectors is used for all pixels in one of the four luminance blocks in the macroblock. The numbering of the motion vectors is equivalent to the numbering of the four luminance blocks as given in Figure 5. Motion vector $MVD_{CHR}$ for both chrominance blocks is derived by calculating the sum of the four luminance vectors and dividing this sum by 8; the component values of the resulting sixteenth pixel resolution vectors are modified towards the nearest half-pixel position as indicated in Table F.1. + +**Table F.1/H.263 – Modification of sixteenth pixel resolution chrominance vector components** + +| | | | | | | | | | | | | | | | | | | +|---------------------------------|---|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|-----| +| Sixteenth pixel position | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | /16 | +| Resulting position | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | /2 | + +Half-pixel values are found using bilinear interpolation as described in 6.1.2. In Advanced Prediction mode, the prediction for luminance is obtained by overlapped motion compensation as described in F.3. The prediction for chrominance is obtained by applying the motion vector $MVD_{CHR}$ to all pixels in the two chrominance blocks (as it is done in the default prediction mode). + +## F.3 Overlapped motion compensation for luminance + +Each pixel in an $8 \times 8$ luminance prediction block is a weighted sum of three prediction values, divided by 8 (with rounding). In order to obtain the three prediction values, three motion vectors are used: the motion vector of the current luminance block, and two out of four "remote" vectors: + +- the motion vector of the block at the left or right side of the current luminance block; +- the motion vector of the block above or below the current luminance block. + +For each pixel, the remote motion vectors of the blocks at the two nearest block borders are used. This means that for the upper half of the block the motion vector corresponding to the block above the current block is used, while for the lower half of the block the motion vector corresponding to the block below the current block is used (see Figure F.3). Similarly, for the left half of the block the motion vector corresponding to the block at the left side of the current block is used, while for the right half of the block the motion vector corresponding to the block at the right side of the current block is used (see Figure F.4). + +Let $(x,y)$ be a position in a picture measured in integer pixel units. + +Let $(m,n)$ be an integer block index in a picture, as given by: + +$$m = x/8 \quad \text{and} \quad n = y/8$$ + +where "/" denotes division with truncation. + +Let $(i,j)$ be an integer pixel location in an $8 \times 8$ block, given by: + +$$i = x - m \cdot 8 \quad \text{and} \quad j = y - n \cdot 8$$ + +resulting in: + +$$(x, y) = (m \cdot 8 + i, n \cdot 8 + j)$$ + +Let $(MV^k_x, MV^k_y)$ be a motion vector, which may contain full-pixel or half pixel offsets, with $k = 0, 1, \text{ or } 2$ . For example, $(MV^k_x, MV^k_y)$ can be equal to $(-7.0, 13.5)$ . Here, $(MV^0_x, MV^0_y)$ denotes the motion vector for the current block $(m,n)$ , $(MV^1_x, MV^1_y)$ denotes the motion vector of the block either above or below, and $(MV^2_x, MV^2_y)$ denotes the motion vector either to the left or right of the current block $(m,n)$ as defined above. + +Then the creation of each pixel, $P(x,y)$ , in an $8 \times 8$ luminance prediction block with block index $(m,n)$ is governed by the following equation: + +$$P(x,y) = (q(x,y) \cdot H_0(i,j) + r(x,y) \cdot H_1(i,j) + s(x,y) \cdot H_2(i,j) + 4) / 8$$ + +where $q(x,y)$ , $r(x,y)$ and $s(x,y)$ are the prediction values taken from the referenced picture as defined by: + +$$q(x,y) = p(x + MV^0_x, y + MV^0_y)$$ + +$$r(x,y) = p(x + MV^1_x, y + MV^1_y)$$ + +$$s(x,y) = p(x + MV^2_x, y + MV^2_y)$$ + +where $p(x + MV^k_x, y + MV^k_y)$ is the prediction value at position $(x + MV^k_x, y + MV^k_y)$ in the referenced picture. Note that $(x + MV^k_x, y + MV^k_y)$ may be outside the picture and can be at a full or half-pixel position. In cases using half-pixel motion vectors, $p(x + MV^k_x, y + MV^k_y)$ refers to the value obtained after the interpolation process described in 6.1.2 is applied. + +The matrices $H_0(i,j)$ , $H_1(i,j)$ and $H_2(i,j)$ are defined in Figures F.2, F.3 and F.4, where $(i,j)$ denotes the column and row, respectively, of the matrix. + +When neither the Slice Structured mode (see Annex K) nor the Independent Segment Decoding mode (see Annex R) are in use, remote motion vectors from other video picture segments are used in the same way as remote motion vectors inside the current GOB. If either the Slice Structured mode or the Independent Segment Decoding mode are in use, the remote motion vectors corresponding to blocks from other video picture segments are set to the motion vector of the current block, regardless of the other conditions described in the next paragraph. (See Annex R for the definition of a video picture segment.) + +If one of the surrounding macroblocks was not coded, the corresponding remote motion vector is set to zero. If one of the surrounding blocks was INTRA coded, the corresponding remote motion vector is replaced by the motion vector for the current block except when in PB-frames mode. In this case (INTRA block in PB-frame mode), the INTRA block's motion vector is used (also see Annex G). If the current block is at the border of the picture and therefore a surrounding block is not present, the corresponding remote motion vector is replaced by the current motion vector. In all cases, if the current block is at the bottom of the macroblock (for block number 3 or 4, see Figure 5), the remote motion vector corresponding with an $8 \times 8$ luminance block in the macroblock below the current macroblock is replaced by the motion vector for the current block. + +The weighting values for the prediction are given in Figures F.2, F.3 and F.4. + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 4 | 5 | 5 | 5 | 5 | 5 | 5 | 4 | +| 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| 5 | 5 | 6 | 6 | 6 | 6 | 5 | 5 | +| 5 | 5 | 6 | 6 | 6 | 6 | 5 | 5 | +| 5 | 5 | 6 | 6 | 6 | 6 | 5 | 5 | +| 5 | 5 | 6 | 6 | 6 | 6 | 5 | 5 | +| 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| 4 | 5 | 5 | 5 | 5 | 5 | 5 | 4 | + +**Figure F.2/H.263 – Weighting values, $H_0$ , for prediction with motion vector of current luminance block** + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 1 | 1 | 2 | 2 | 2 | 2 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 2 | 2 | 2 | 2 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | + +**Figure F.3/H.263 – Weighting values, $H_1$ , for prediction with motion vectors of the luminance blocks on top or bottom of current luminance block** + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | +| 2 | 2 | 1 | 1 | 1 | 1 | 2 | 2 | +| 2 | 2 | 1 | 1 | 1 | 1 | 2 | 2 | +| 2 | 2 | 1 | 1 | 1 | 1 | 2 | 2 | +| 2 | 2 | 1 | 1 | 1 | 1 | 2 | 2 | +| 2 | 2 | 1 | 1 | 1 | 1 | 2 | 2 | +| 2 | 2 | 1 | 1 | 1 | 1 | 2 | 2 | +| 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | + +**Figure F.4/H.263 – Weighting values, $H_2$ , for prediction with motion vectors of the luminance blocks to the left or right of current luminance block** + +# Annex G + +## PB-frames mode + +## G.1 Introduction + +This annex describes the optional PB-frames mode of this Recommendation. The capability of this mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in PTTYPE. + +A PB-frame consists of two pictures being coded as one unit. The name PB comes from the name of picture types in ITU-T Rec. H.262 where there are P-pictures and B-pictures. Thus, a PB-frame consists of one P-picture which is predicted from the previous decoded P-picture and one B-picture which is predicted both from the previous decoded P-picture and the P-picture currently being decoded. The name B-picture was chosen because parts of B-pictures may be bidirectionally predicted from the past and future pictures. The prediction process is illustrated in Figure G.1. + +An improved version of the PB-frames mode, termed the "Improved PB-frames mode", is described in Annex M. The PB-frames mode as described in this annex is retained herein only for purposes of compatibility with systems designed prior to the adoption of the Improved PB-frames mode. For this reason, the PB-frames mode as described in this annex cannot be used with the additional features of the syntax which require the use of PLUSPTYPE. + +![Diagram illustrating the prediction process in PB-frames mode. It shows three pictures: a P picture, a B picture, and another P picture. The B picture is part of a 'PB frame' with the first P picture. Arrows indicate prediction: from the first P picture to the B picture, and from the B picture to the second P picture. A curved arrow also shows prediction from the first P picture to the second P picture. The diagram is labeled T1602860-97.](bc6f20871b4f01c61470306c304fc9fe_img.jpg) + +The diagram illustrates the prediction process in PB-frames mode. It shows three pictures: a P picture, a B picture, and another P picture. The B picture is part of a 'PB frame' with the first P picture. Arrows indicate prediction: from the first P picture to the B picture, and from the B picture to the second P picture. A curved arrow also shows prediction from the first P picture to the second P picture. The diagram is labeled T1602860-97. + +Diagram illustrating the prediction process in PB-frames mode. It shows three pictures: a P picture, a B picture, and another P picture. The B picture is part of a 'PB frame' with the first P picture. Arrows indicate prediction: from the first P picture to the B picture, and from the B picture to the second P picture. A curved arrow also shows prediction from the first P picture to the second P picture. The diagram is labeled T1602860-97. + +Figure G.1/H.263 – Prediction in PB-frames mode + +## G.2 PB-frames and INTRA blocks + +When PB-frames are used, the coding mode INTRA has the following meaning (see also 5.3.2): + +- The P-blocks are INTRA coded. +- The B-blocks are INTER coded with prediction as for an INTER block. + +If PB-frames are used, Motion Vector Data (MVD) is included also for INTRA macroblocks in pictures for which PTTYPE indicates "INTER". In this case, the vector is used for the B-blocks only. The codewords $MVD_{2..4}$ are never used for INTRA (see also Table 10). When in both the Advanced Prediction mode and the PB-frames mode, and one of the surrounding blocks was coded in INTRA mode, the corresponding remote motion vector is not replaced by the motion vector for the current block. Instead, the remote "INTRA" motion vector is used. + +## G.3 Block layer + +In a PB-frame, a macroblock comprises twelve blocks. First, the data for the six P-blocks is transmitted as in the default H.263 mode, then the data for the six B-blocks (see also 5.4). The + +structure of the block layer is shown in Figure 11. INTRADC is present for every P-block of the macroblock if MCBPC indicates macroblock type 3 or 4 (see Tables 7 and 8). INTRADC is not present for B-blocks. TCOEF is present for P-blocks if indicated by MCBPC or CBPY; TCOEF is present for B-blocks if indicated by CBPB. + +## G.4 Calculation of vectors for the B-picture in a PB-frame + +The vectors for the B-picture are calculated as follows (see also 6.1.1). Assume we have a vector component MV in half-pixel units to be used in the P-picture (MV represents a vector component for an 8 \* 8 luminance block; if only one vector per macroblock is transmitted, MV has the same value for each of the four 8 \* 8 luminance blocks). For prediction of the B-picture we need both forward and backward vector components $MV_F$ and $MV_B$ . These forward and backward vector components are derived from MV and eventually enhanced by a delta vector given by MVDB. + +- $TR_D$ : The increment of the temporal reference TR (or the combined extended temporal reference ETR and temporal reference TR in an Improved PB frame when a custom picture clock frequency is in use) from the last picture header (see 5.1.2). If $TR_D$ is negative, then $TR_D = TR_D + d$ where $d = 256$ for CIF picture frequency and 1024 for any custom picture clock frequency. +- $TR_B$ : See 5.1.2. + +Assume that $MV_D$ is the delta vector component given by MVDB and corresponding with vector component MV. If MVDB is not present, $MV_D$ is set to zero. If MVDB is present, the same $MV_D$ given by MVDB is used for each of the four luminance B-blocks within the macroblock. + +Now, $MV_F$ and $MV_B$ are given in half-pixel units by the following formulae: + +$$\begin{aligned} MV_F &= (TR_B \times MV) / TR_D + MV_D \\ MV_B &= ((TR_B - TR_D) \times MV) / TR_D && \text{if } MV_D \text{ is equal to } 0 \\ MV_B &= MV_F - MV && \text{if } MV_D \text{ is unequal to } 0 \end{aligned}$$ + +where "/" means division by truncation. It is assumed that the scaling reflects the actual position in time of P- and B-pictures. Advantage is taken of the fact that the range of values for $MV_F$ is constrained. Each VLC word for MVDB represents a pair of difference values. Only one of the pair will yield a value for $MV_F$ falling within the permitted range (default [-16, 15.5]; in Unrestricted Motion Vector mode [-31.5, 31.5]). The formulae for $MV_F$ and $MV_B$ are also used in the case of INTRA blocks where the vector data is used only for predicting B-blocks. + +For chrominance blocks, $MV_F$ is derived by calculating the sum of the four corresponding luminance $MV_F$ vectors and dividing this sum by 8; the resulting sixteenth pixel resolution vector components are modified towards the nearest half-pixel position as indicated in Table F.1. $MV_B$ for chrominance is derived by calculating the sum of the four corresponding luminance $MV_B$ vectors and dividing this sum by 8; the resulting sixteenth pixel resolution vector components are modified towards the nearest half-pixel position as indicated in Table F.1. + +A positive value of the horizontal or vertical component of the motion vector signifies that the prediction is formed from pixels in the referenced picture which are spatially to the right or below the pixels being predicted. + +## G.5 Prediction of a B-block in a PB-frame + +In this clause a block means an 8 × 8 block. The following procedure applies for luminance as well as chrominance blocks. First, the forward and backward vectors are calculated. It is assumed that the P-macroblock (luminance and chrominance) is first decoded, reconstructed and clipped (see 6.3.2). This macroblock is called $P_{REC}$ . Based on $P_{REC}$ and the prediction for $P_{REC}$ , the prediction for the B-block is calculated. + +The prediction of the B-block has two modes that are used for different parts of the block: + +- For pixels where the backward vector – $MV_B$ – points inside $P_{REC}$ , use bidirectional prediction. This is obtained as the average of the forward prediction using $MV_F$ relative to the previous decoded picture, and the backward prediction using $MV_B$ relative to $P_{REC}$ . The average is calculated by dividing the sum of the two predictions by two (division by truncation). +- For all other pixels, forward prediction using $MV_F$ relative to the previous decoded picture is used. + +Figure G.2 indicates which part of a block is predicted bidirectionally (shaded part of the B-block) and which part with forward prediction only (rest of the B-block). + +![Diagram illustrating forward and bidirectional prediction for a B-block within a P-macroblock.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +The diagram shows a 2x2 grid of blocks representing a P-macroblock. The top-left block is a B-block. Within this B-block, a shaded rectangular region on the left side is labeled 'Bidirectional prediction', and the remaining white area is labeled 'Forward prediction'. A dashed rectangle above the B-block represents a reference block. An arrow labeled 'Backward vector' points from the top-left corner of the B-block to the top-left corner of the dashed reference block. The label 'P-macroblock' is at the bottom right of the grid, and the code 'T1602870-97' is in the bottom right corner. + +Diagram illustrating forward and bidirectional prediction for a B-block within a P-macroblock. + +**Figure G.2/H.263 – Forward and bidirectional prediction for a B-block** + +Bidirectional prediction is used for pixels where the backward vector – $MV_B$ – points inside $P_{REC}$ . These pixels are defined by the following procedures which are specified in C language. + +Definitions: + +| | | +|-------------|---------------------------------------------------------------------| +| $nh$ | Horizontal position of block within a macroblock (0 or 1). | +| $nv$ | Vertical position of block within a macroblock (0 or 1). | +| $mh(nh,nv)$ | Horizontal vector component of block $(nh,nv)$ in half-pixel units. | +| $mv(nh,nv)$ | Vertical vector component of block $(nh,nv)$ in half-pixel units. | +| $mhc$ | Horizontal chrominance vector component. | +| $mvc$ | Vertical chrominance vector component. | + +### Procedure for luminance + +``` +for (nh = 0; nh <= 1; nh++) { + for (nv = 0; nv <= 1; nv++) { + for (i = nh * 8 + max(0, (-mh(nh,nv)+1)/2 - nh * 8); + i <= nh * 8 + min(7, 15-(mh(nh,nv)+1)/2 - nh * 8); i++) { + for (j = nv * 8 + max(0, (-mv(nh,nv)+1)/2 - nv * 8); + j <= nv * 8 + min(7, 15-(mv(nh,nv)+1)/2 - nv * 8); j++) { + predict pixel (i,j) bidirectionally + } + } + } +} +``` + +### Procedure for chrominance + +``` +for (i = max(0, (-mhc+1)/2); i <= min(7, 7-(mhc+1)/2); i++) { + for (j = max(0, (-mvc+1)/2); j <= min(7, 7-(mvc+1)/2); j++) { + predict pixel (i,j) bidirectionally; + } +} +``` + +Pixels not predicted bidirectionally are predicted with forward prediction only. + +# Annex H + +## Forward error correction for coded video signal + +## H.1 Introduction + +This annex describes an optional forward error correction method (code and framing) for transmission of H.263 encoded video data. This forward error correction may be used in situations where no forward error correction is provided by external means, for example at the multiplex or system level. It is not used for ITU-T Rec. H.324. Both the framing and the forward error correction code are the same as in ITU-T Rec. H.261. + +## H.2 Error correction framing + +To allow the video data and error correction parity information to be identified by a decoder, an error correction framing pattern is included. This pattern consists of multiframes of eight frames, each frame comprising 1 bit framing, 1 bit fill indicator (Fi), 492 bits of coded data (or fill all 1s) and 18 bits parity (see Figure H.1). For each multiframe the frame alignment pattern formed by the framing bits of the eight individual frames is: + +$$(S_1 S_2 S_3 S_4 S_5 S_6 S_7 S_8) = (00011011)$$ + +The fill indicator (Fi) can be set to zero by an encoder. In this case 492 consecutive fill bits (fill all 1s) are used instead of 492 bits of coded data. This may be used for stuffing data (see 3.6). + +## H.3 Error correcting code + +The error correction code is a BCH (511, 493) forward error correction code. Use of this by the decoder is optional. The parity is calculated against a code of 493 bits, comprising 1 bit fill indicator (Fi) and 492 bits of coded video data. + +The generator polynomial is: + +$$g(x) = (x^9 + x^4 + 1)(x^9 + x^6 + x^4 + x^3 + 1)$$ + +Example: for the input data of "01111 ... 11" (493 bits) the resulting correction parity bits are "011011010100011011" (18 bits). + +## H.4 Relock time for error corrector framing + +Three consecutive error correction frame alignment patterns (24 bits) should be received before frame lock is deemed to have been achieved. The decoder should be designed such that frame lock will be re-established within 34 000 bits after an error corrector framing phase change. + +NOTE – This assumes that the video data does not contain three correctly phased emulations of the error correction framing sequence during the relocking period. + +![Diagram of an error correcting frame structure. It shows a sequence of alignment patterns S1 through S8. Below this, a table shows the frame structure with columns for S1, Data, and Parity. The Data section is further divided into Fi (1 bit) and Coded data (493 bits). A separate box shows a Fill section (0 bits) and Coded data (492 bits).](e5ded42f8e352da02ee86cb55550c45d_img.jpg) + +Transmission order → $(S_1S_2S_3S_4S_5S_6S_7S_8) = (00011011)$ + +| | | | | | | | | | | +|----------------|--|----------------|--|----------------|--|----------------|--|----------------|--| +| S 1 | | S 2 | | S 3 | | S 7 | | S 8 | | +|----------------|--|----------------|--|----------------|--|----------------|--|----------------|--| + + + +| | | | +|----------------|------------|--------| +| S 1 | Data | Parity | +| 1 | 493 | 18 | +| Fi | | | +| 1 | Coded data | | + + + +| | | +|---|----------------| +| 0 | Fill (all "1") | +| 1 | 492 | + +T1602880-97 + +Diagram of an error correcting frame structure. It shows a sequence of alignment patterns S1 through S8. Below this, a table shows the frame structure with columns for S1, Data, and Parity. The Data section is further divided into Fi (1 bit) and Coded data (493 bits). A separate box shows a Fill section (0 bits) and Coded data (492 bits). + +**Figure H.1/H.263 – Error correcting frame** + +# Annex I + +## Advanced INTRA Coding mode + +This annex describes the optional Advanced INTRA Coding mode of this Recommendation. The capability of this H.263 mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in the PLUSPTYPE field of the picture header. + +## I.1 Introduction + +This optional mode alters the decoding of macroblocks of type "INTRA" (macroblocks of other types are not affected). The coding efficiency of INTRA macroblocks is improved by using: + +- 1) INTRA-block prediction using neighbouring INTRA blocks for the same component (Y, CB, or CR); +- 2) modified inverse quantization for INTRA coefficients; and +- 3) a separate VLC for INTRA coefficients. + +A particular INTRA-coded block may be predicted from the block above the current block being decoded, from the block to the left of the current block being decoded, or from both. Special cases exist for situations in which the neighbouring blocks are not INTRA coded or are not in the same + +video picture segment. Block prediction always uses data from the same luminance or color difference component ( $Y$ , $C_B$ , or $C_R$ ) as the block being decoded. In prediction, DC coefficients are always predicted in some manner. The first row of AC coefficients may be predicted from those in the block above, or the first column of AC coefficients may be predicted from those in the block to the left, or only the DC coefficient may be predicted as an average from the block above and the block to the left, as signalled on a macroblock-by-macroblock basis. The remaining AC coefficients are never predicted. Inverse quantization of the INTRADC coefficient is modified to allow a varying quantization step size, unlike in the main text of this Recommendation where a fixed step size of 8 is used for INTRADC coefficients. Inverse quantization of all INTRA coefficients is performed without a "dead-zone" in the quantizer reconstruction spacing. + +## I.2 Syntax + +When using the Advanced INTRA Coding mode, the macroblock layer syntax is altered as specified in Figure I.1. The syntax as shown in Figure I.1 is the same as that defined in 5.3 except for the insertion of an additional INTRA\_MODE field for INTRA macroblocks. INTRA\_MODE is present only when MCBPC indicates a macroblock of type INTRA (macroblock type 3 or 4). The prediction mode is coded using the variable length code shown in Table I.1. One prediction mode is transmitted per INTRA macroblock. + +![Diagram showing the structure of the macroblock layer. The top row contains fields: COD, MCBPC, INTRA_MODE, MODB, CBPB, CBPY, and DQUANT. A line from the DQUANT field leads to a second row containing fields: MVD, MVD2, MVD3, MVD4, MVDB, and Block data. The label T1602890-97 is present to the right of the second row.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +Diagram showing the structure of the macroblock layer. The top row contains fields: COD, MCBPC, INTRA\_MODE, MODB, CBPB, CBPY, and DQUANT. A line from the DQUANT field leads to a second row containing fields: MVD, MVD2, MVD3, MVD4, MVDB, and Block data. The label T1602890-97 is present to the right of the second row. + +**Figure I.1/H.263 – Structure of macroblock layer** + +**Table I.1/H.263 – VLC for INTRA\_MODE** + +| Index | Prediction Mode | VLC | +|-------|------------------------|-----| +| 0 | 0 (DC Only) | 0 | +| 1 | 1 (Vertical DC & AC) | 10 | +| 2 | 2 (Horizontal DC & AC) | 11 | + +## I.3 Decoding process + +Two scans in addition to the zigzag scan are employed. The two added scans are shown in Figure I.2-a and I.2-b, and the zigzag scan is shown in Figure 14. + +| | | | | | | | | +|----|----|----|----|----|----|----|----| +| 1 | 2 | 3 | 4 | 11 | 12 | 13 | 14 | +| 5 | 6 | 9 | 10 | 18 | 17 | 16 | 15 | +| 7 | 8 | 20 | 19 | 27 | 28 | 29 | 30 | +| 21 | 22 | 25 | 26 | 31 | 32 | 33 | 34 | +| 23 | 24 | 35 | 36 | 43 | 44 | 45 | 46 | +| 37 | 38 | 41 | 42 | 47 | 48 | 49 | 50 | +| 39 | 40 | 51 | 52 | 57 | 58 | 59 | 60 | +| 53 | 54 | 55 | 56 | 61 | 62 | 63 | 64 | + +a) Alternate-Horizontal scan + +| | | | | | | | | +|----|----|----|----|----|----|----|----| +| 1 | 5 | 7 | 21 | 23 | 37 | 39 | 53 | +| 2 | 6 | 8 | 22 | 24 | 38 | 40 | 54 | +| 3 | 9 | 20 | 25 | 35 | 41 | 51 | 55 | +| 4 | 10 | 19 | 26 | 36 | 42 | 52 | 56 | +| 11 | 18 | 27 | 31 | 43 | 47 | 57 | 61 | +| 12 | 17 | 28 | 32 | 44 | 48 | 58 | 62 | +| 13 | 16 | 29 | 33 | 45 | 49 | 59 | 63 | +| 14 | 15 | 30 | 34 | 46 | 50 | 60 | 64 | + +b) Alternate-Vertical scan (as in ITU-T Rec. H.262) + +**Figure I.2/H.263 – Alternate DCT scanning patterns for Advanced INTRA coding** + +For INTRA-coded blocks, if Prediction Mode = 0, the zigzag scan shown in Figure 14 is selected for all blocks in the macroblock; otherwise, the prediction direction is used to select a scan for the macroblock. + +Prediction Mode = 1 uses the vertically adjacent block in forming a prediction. This prediction mode is designed for INTRA blocks which are dominated by stronger horizontal frequency content, so the vertically adjacent block is used to predict the horizontal frequency content of the current block, with a prediction of zero for all coefficients representing vertical AC content. Then the scanning pattern is chosen to scan the stronger horizontal frequencies prior to the vertical ones, using the Alternate-Horizontal scan. + +Prediction Mode = 2 uses the horizontally adjacent block in forming a prediction. This prediction mode is designed for INTRA blocks which are dominated by stronger vertical frequency content, so the horizontally adjacent block is used to predict the vertical frequency content of the current block, with a prediction of zero for all coefficients representing horizontal AC content. Then the scanning pattern is chosen to scan the stronger vertical frequencies prior to the horizontal ones, using the Alternate-Vertical scan. + +For non-INTRA blocks, the $8 \times 8$ blocks of transform coefficients are scanned with "zigzag" scanning as shown in Figure 14. + +A separate VLC table is used for all INTRADC and INTRA AC coefficients. This table is specified in Table I.2. Note that the VLC codeword entries used in Table I.2 are the same as those used in the normal TCOEF table (Table 16) used when Advanced INTRA coding is not in use, but with a different interpretation of LEVEL and RUN (without altering LAST). + +**Table I.2/H.263 – VLC for INTRA TCOEF** + +| Index | LAST | RUN | LEVEL | Bits | VLC code | +|-------|------|-----|-------|------|------------| +| 0 | 0 | 0 | 1 | 3 | 10s | +| 1 | 0 | 1 | 1 | 5 | 1111s | +| 2 | 0 | 3 | 1 | 7 | 0101 01s | +| 3 | 0 | 5 | 1 | 8 | 0010 111s | +| 4 | 0 | 7 | 1 | 9 | 0001 1111s | + +**Table I.2/H.263 – VLC for INTRA TCOEF** + +| Index | LAST | RUN | LEVEL | Bits | VLC code | +|--------------|-------------|------------|----------------|-------------|-----------------| +| 5 | 0 | 8 | 1 | 10 | 0001 0010 1s | +| 6 | 0 | 9 | 1 | 10 | 0001 0010 0s | +| 7 | 0 | 10 | 1 | 11 | 0000 1000 01s | +| 8 | 0 | 11 | 1 | 11 | 0000 1000 00s | +| 9 | 0 | 4 | 3 | 12 | 0000 0000 111s | +| 10 | 0 | 9 | 2 | 12 | 0000 0000 110s | +| 11 | 0 | 13 | 1 | 12 | 0000 0100 000s | +| 12 | 0 | 0 | 2 | 4 | 110s | +| 13 | 0 | 1 | 2 | 7 | 0101 00s | +| 14 | 0 | 1 | 4 | 9 | 0001 1110s | +| 15 | 0 | 1 | 5 | 11 | 0000 0011 11s | +| 16 | 0 | 1 | 6 | 12 | 0000 0100 001s | +| 17 | 0 | 1 | 7 | 13 | 0000 0101 0000s | +| 18 | 0 | 0 | 3 | 5 | 1110s | +| 19 | 0 | 3 | 2 | 9 | 0001 1101s | +| 20 | 0 | 2 | 3 | 11 | 0000 0011 10s | +| 21 | 0 | 3 | 4 | 13 | 0000 0101 0001s | +| 22 | 0 | 0 | 5 | 6 | 0110 1s | +| 23 | 0 | 4 | 2 | 10 | 0001 0001 1s | +| 24 | 0 | 3 | 3 | 11 | 0000 0011 01s | +| 25 | 0 | 0 | 4 | 6 | 0110 0s | +| 26 | 0 | 5 | 2 | 10 | 0001 0001 0s | +| 27 | 0 | 5 | 3 | 13 | 0000 0101 0010s | +| 28 | 0 | 2 | 1 | 6 | 0101 1s | +| 29 | 0 | 6 | 2 | 11 | 0000 0011 00s | +| 30 | 0 | 0 | 25 | 13 | 0000 0101 0011s | +| 31 | 0 | 4 | 1 | 7 | 0100 11s | +| 32 | 0 | 7 | 2 | 11 | 0000 0010 11s | +| 33 | 0 | 0 | 24 | 13 | 0000 0101 0100s | +| 34 | 0 | 0 | 8 | 7 | 0100 10s | +| 35 | 0 | 8 | 2 | 11 | 0000 0010 10s | +| 36 | 0 | 0 | 7 | 7 | 0100 01s | +| 37 | 0 | 2 | 4 | 11 | 0000 0010 01s | +| 38 | 0 | 0 | 6 | 7 | 0100 00s | +| 39 | 0 | 12 | 1 | 11 | 0000 0010 00s | +| 40 | 0 | 0 | 9 | 8 | 0010 110s | +| 41 | 0 | 0 | 23 | 13 | 0000 0101 0101s | +| 42 | 0 | 2 | 2 | 8 | 0010 101s | + +**Table I.2/H.263 – VLC for INTRA TCOEF** + +| Index | LAST | RUN | LEVEL | Bits | VLC code | +|--------------|-------------|------------|----------------|-------------|-----------------| +| 43 | 0 | 1 | 3 | 8 | 0010 100s | +| 44 | 0 | 6 | 1 | 9 | 0001 1100s | +| 45 | 0 | 0 | 10 | 9 | 0001 1011s | +| 46 | 0 | 0 | 12 | 10 | 0001 0000 1s | +| 47 | 0 | 0 | 11 | 10 | 0001 0000 0s | +| 48 | 0 | 0 | 18 | 10 | 0000 1111 1s | +| 49 | 0 | 0 | 17 | 10 | 0000 1111 0s | +| 50 | 0 | 0 | 16 | 10 | 0000 1110 1s | +| 51 | 0 | 0 | 15 | 10 | 0000 1110 0s | +| 52 | 0 | 0 | 14 | 10 | 0000 1101 1s | +| 53 | 0 | 0 | 13 | 10 | 0000 1101 0s | +| 54 | 0 | 0 | 20 | 12 | 0000 0100 010s | +| 55 | 0 | 0 | 19 | 12 | 0000 0100 011s | +| 56 | 0 | 0 | 22 | 13 | 0000 0101 0110s | +| 57 | 0 | 0 | 21 | 13 | 0000 0101 0111s | +| 58 | 1 | 0 | 1 | 5 | 0111s | +| 59 | 1 | 14 | 1 | 10 | 0000 1100 1s | +| 60 | 1 | 20 | 1 | 12 | 0000 0000 101s | +| 61 | 1 | 1 | 1 | 7 | 0011 11s | +| 62 | 1 | 19 | 1 | 12 | 0000 0000 100s | +| 63 | 1 | 2 | 1 | 7 | 0011 10s | +| 64 | 1 | 3 | 1 | 7 | 0011 01s | +| 65 | 1 | 0 | 2 | 7 | 0011 00s | +| 66 | 1 | 5 | 1 | 8 | 0010 011s | +| 67 | 1 | 6 | 1 | 8 | 0010 010s | +| 68 | 1 | 4 | 1 | 8 | 0010 001s | +| 69 | 1 | 0 | 3 | 8 | 0010 000s | +| 70 | 1 | 9 | 1 | 9 | 0001 1010s | +| 71 | 1 | 10 | 1 | 9 | 0001 1001s | +| 72 | 1 | 11 | 1 | 9 | 0001 1000s | +| 73 | 1 | 12 | 1 | 9 | 0001 0111s | +| 74 | 1 | 13 | 1 | 9 | 0001 0110s | +| 75 | 1 | 8 | 1 | 9 | 0001 0101s | +| 76 | 1 | 7 | 1 | 9 | 0001 0100s | +| 77 | 1 | 0 | 4 | 9 | 0001 0011s | +| 78 | 1 | 17 | 1 | 10 | 0000 1100 0s | +| 79 | 1 | 18 | 1 | 10 | 0000 1011 1s | +| 80 | 1 | 16 | 1 | 10 | 0000 1011 0s | + +**Table I.2/H.263 – VLC for INTRA TCOEF** + +| Index | LAST | RUN | LEVEL | Bits | VLC code | +|-------|--------|-----|-------|------|-----------------| +| 81 | 1 | 15 | 1 | 10 | 0000 1010 1s | +| 82 | 1 | 2 | 2 | 10 | 0000 1010 0s | +| 83 | 1 | 1 | 2 | 10 | 0000 1001 1s | +| 84 | 1 | 0 | 6 | 10 | 0000 1001 0s | +| 85 | 1 | 0 | 5 | 10 | 0000 1000 1s | +| 86 | 1 | 4 | 2 | 11 | 0000 0001 11s | +| 87 | 1 | 3 | 2 | 11 | 0000 0001 10s | +| 88 | 1 | 1 | 3 | 11 | 0000 0001 01s | +| 89 | 1 | 0 | 7 | 11 | 0000 0001 00s | +| 90 | 1 | 2 | 3 | 12 | 0000 0100 100s | +| 91 | 1 | 1 | 4 | 12 | 0000 0100 101s | +| 92 | 1 | 0 | 9 | 12 | 0000 0100 110s | +| 93 | 1 | 0 | 8 | 12 | 0000 0100 111s | +| 94 | 1 | 21 | 1 | 13 | 0000 0101 1000s | +| 95 | 1 | 22 | 1 | 13 | 0000 0101 1001s | +| 96 | 1 | 23 | 1 | 13 | 0000 0101 1010s | +| 97 | 1 | 7 | 2 | 13 | 0000 0101 1011s | +| 98 | 1 | 6 | 2 | 13 | 0000 0101 1100s | +| 99 | 1 | 5 | 2 | 13 | 0000 0101 1101s | +| 100 | 1 | 3 | 3 | 13 | 0000 0101 1110s | +| 101 | 1 | 0 | 10 | 13 | 0000 0101 1111s | +| 102 | ESCAPE | | | 7 | 0000 011 | + +Depending on the value of INTRA\_MODE, either one or eight coefficients are prediction residuals that must be added to a predictor as described below. Figure I.3 shows three $8 \times 8$ blocks of final reconstructed DCT levels for the same component ( $Y$ , $C_B$ , or $C_R$ ), labelled $\text{RecA}'(u,v)$ , $\text{RecB}'(u,v)$ and $\text{RecC}'(u,v)$ , where $u$ and $v$ are column (horizontal) and row (vertical) indices, respectively. The reconstruction process differs from the processing described in 6.2.1. INTRADC residuals are reconstructed differently by use of a variable step size, as opposed to using Table 15, and then a predictor is added to the residual values to obtain the final coefficient reconstruction value. INTRA coefficients other than INTRADC are also reconstructed differently than in 6.2.1, using a reconstruction spacing without a "dead-zone" and then in some cases adding a predictor to obtain the final coefficient reconstruction value. The block may contain both DC and AC prediction residuals. + +![Figure I.3/H.263 – Three neighbouring blocks in the DCT domain. The figure shows three 8x8 grids representing blocks A, B, and C. Block A (top right) is labeled 'Block A RecA'(u,v)' and has columns u=0 to 7 and rows v=0 to 7. The first column (u=0) is shaded gray. A black dot is at (u=0, v=0). Block B (bottom left) is labeled 'Block B RecB'(u,v)' and has columns u=0 to 7 and rows v=0 to 7. The first column (u=0) is shaded gray. A black dot is at (u=0, v=0). Block C (bottom right) is labeled 'Block C RecC'(u,v)' and has columns u=0 to 7 and rows v=0 to 7. A black dot is at (u=0, v=0). A small label 'T1602900-97' is at the bottom right of Block C.](b9745e4d501fcfe72053e7211ab39fed_img.jpg) + +Figure I.3/H.263 – Three neighbouring blocks in the DCT domain. The figure shows three 8x8 grids representing blocks A, B, and C. Block A (top right) is labeled 'Block A RecA'(u,v)' and has columns u=0 to 7 and rows v=0 to 7. The first column (u=0) is shaded gray. A black dot is at (u=0, v=0). Block B (bottom left) is labeled 'Block B RecB'(u,v)' and has columns u=0 to 7 and rows v=0 to 7. The first column (u=0) is shaded gray. A black dot is at (u=0, v=0). Block C (bottom right) is labeled 'Block C RecC'(u,v)' and has columns u=0 to 7 and rows v=0 to 7. A black dot is at (u=0, v=0). A small label 'T1602900-97' is at the bottom right of Block C. + +**Figure I.3/H.263 – Three neighbouring blocks in the DCT domain** + +The definitions of MCBPC and CBPY are changed when Advanced INTRA coding is in use. When Advanced INTRA coding is in use, INTRADC transform coefficients are no longer handled as a separate case, but are instead treated in the same way as the AC coefficients in regard to MCBPC and CBPY. This means that a zero INTRADC will not be coded as a LEVEL, but will simply increase the run for the following AC coefficients. + +The inverse quantization process for the B-part of an Improved PB frame (see Annex M) is not altered by the use of the Advanced INTRA coding mode. + +Define $\text{RecC}(u,v)$ to be the reconstructed coefficient *residuals* of the current block. For all INTRA coefficients, the reconstructed residual value is obtained by: + +$$\text{RecC}(u,v) = 2 * \text{QUANT} * \text{LEVEL}(u,v) \quad u = 0, \dots, 7, v = 0, \dots, 7$$ + +NOTE – $\text{LEVEL}(u,v)$ denotes a quantity having both a magnitude and a sign in the above equation. + +Define $\text{RecC}'(u,v)$ to be the *final* reconstructed coefficient values of the current block (after adjustments for prediction, oddification as described below, and clipping). The final reconstructed coefficient values $\text{RecC}'(u,v)$ are recovered by adding $\text{RecC}(u,v)$ to the appropriate prediction as signalled in the INTRA\_MODE field, altering the least-significant bit if needed for oddification of the DC coefficient, and clipping. + +RecA'(u,v) denotes the *final* reconstructed coefficient values for the block immediately above the current block. RecB'(u,v) denotes the *final* reconstructed coefficient values of the block immediately to the left of the current block. + +The ability to use the reconstructed coefficient values for blocks A and B in the prediction of the coefficient values for block C depends on whether blocks A and B are in the same video picture segment as block C. A block is defined to be "in the same video picture segment" as another block only if the following conditions are fulfilled: + +- 1) The relevant block is within the boundary of the picture; and +- 2) If not in Slice Structured mode (see Annex K), the relevant block is either within the same GOB or no GOB header is present for the current GOB; and +- 3) If in Slice Structured mode, the relevant block is within the same slice. + +The block C to be decoded is predicted only from INTRA blocks within the same video picture segment as block C, as shown below. + +If Prediction Mode = 0 is used (DC prediction only) and blocks A and B are both INTRA blocks within the same video picture segment as block C, then the DC coefficient of block C is predicted from the average (with truncation) of the DC coefficients of blocks A and B. If only one of the two blocks A and B is an INTRA block within the same video picture segment as block C, then the DC coefficient of only this one of the two blocks is used as the predictor for Prediction Mode = 0. If neither of the two blocks A and B are INTRA blocks within the same video picture segment as block C, then the prediction uses the value of 1024 as the predictor for the DC coefficient. + +If Prediction Mode = 1 or 2 (vertical DC & AC or horizontal DC & AC prediction) and the referenced block (block A or block B) is not an INTRA block within the same video picture segment as block C, then the prediction uses the value of 1024 as the predictor for the DC coefficient and the value of 0 as the predictor for the AC coefficients of block C. + +A process of "oddification" is applied to the DC coefficient in order to minimize the impact of IDCT mismatch errors. Certain values of coefficients can cause a round-off error mismatch between different IDCT implementations, especially certain values of the (0,0), (0,4), (4,0), and (4,4) coefficients. For example, a DC coefficient of $8k + 4$ for some integer $k$ results in an inverse-transformed block having a constant value $k + 0.5$ , for which slight errors can cause rounding in different directions on different implementations. + +Define the clipAC() function to indicate clipping to the range -2048 to 2047. Define the clipDC() function to indicate clipping to the range 0 to 2047. Define the oddifyclipDC(x) function as: + +``` + +If (x is even) { + result = clipDC(x+1) +} else { + result = clipDC(x) +} + +``` + +The reconstruction for each INTRA prediction mode is then specified as follows, in which the operator "/" is defined as division by truncation: + +Mode 0: DC prediction only. + +``` + +RecC'(u,v) = clipAC( RecC(u,v) ) (u,v) ≠ (0,0), u = 0, ..., 7, v = 0, ..., 7. +If (block A and block B are both INTRA coded and are both in the same + video picture segment as block C) { + tempDC = RecC(0,0) + ( RecA'(0,0) + RecB'(0,0) ) / 2 +} else { + If (block A is INTRA coded and is in the same video picture segment + as block C) { + tempDC = RecC(0,0) + RecA'(0,0) + +``` + +``` + + } else { + If (block B is INTRA coded and is in the same video picture segment + as block C) { + tempDC = RecC(0,0) + RecB'(0,0) + } else { + tempDC = RecC(0,0) + 1024 + } + } + RecC'(0,0) = oddifyclipDC( tempDC ) + +``` + +Mode 1: DC and AC prediction from the block above. + +``` + +If (block A is INTRA coded and is in the same video picture segment as + block C) { + tempDC = RecC(0,0) + RecA'(0,0) + RecC'(u,0) = clipAC( RecC(u,0) + RecA'(u,0) ) u = 1, ..., 7, + RecC'(u,v) = clipAC( RecC(u,v) ) u = 0, ..., 7, v = 1, ..., 7. +} else { + tempDC = RecC(0,0) + 1024 + RecC'(u,v) = clipAC( RecC(u,v) ) (u,v) ≠ (0,0), u = 0, ..., 7, v = 0, ..., 7 +} +RecC'(0,0) = oddifyclipDC( tempDC ) + +``` + +Mode 2: DC and AC prediction from the block to the left. + +``` + +If (block B is INTRA coded and is in the same video picture segment as + block C) { + tempDC = RecC(0,0) + RecB'(0,0) + RecC'(0,v) = clipAC( RecC(0,v) + RecB'(0,v) ) v = 1, ..., 7, + RecC'(u,v) = clipAC( RecC(u,v) ) u = 1, ..., 7, v = 0, ..., 7. +} else { + tempDC = RecC(0,0) + 1024 + RecC'(u,v) = clipAC( RecC(u,v) ) (u,v) ≠ (0,0), u = 0, ..., 7, v = 0, ..., 7 +} +RecC'(0,0) = oddifyclipDC( tempDC ) + +``` + +# Annex J + +# Deblocking Filter mode + +## J.1 Introduction + +This annex describes the use of an optional block edge filter within the coding loop. The main purpose of the block edge filter is to reduce blocking artifacts. The filtering is performed on $8 \times 8$ block edges. Motion vectors may have either $8 \times 8$ or $16 \times 16$ resolution (see J.2). The processing described in this annex applies only for the P-, I-, EP-, or EI-pictures or the P-picture part of an Improved PB-frame. (Possible filtering of B-pictures or the B-picture part of an Improved PB-frame is not a matter for standardization; however, some type of filtering is recommended for improved picture quality.) The capability of this mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in the PLUSPTYPE field of the picture header. + +NOTE – The problem of IDCT mismatch can be aggravated when using Annex J with a small quantization step size and not using the Annex W IDCT in both the encoder and decoder. In some cases, the amount of rounding error mismatch may even be amplified by the Annex J filtering process. Encoders should avoid this problem, by, for example, not using Annex J when the quantization step size is very small. + +## J.2 Relation to UMV and AP modes (Annexes D and F) + +The use of the deblocking filter mode has similar effects on picture quality as Overlapped Block Motion Compensation (OBMC) as defined in Annex F when used alone. When both techniques are used together, a further improvement in picture quality can be obtained. The Advanced Prediction mode (see also Annex F) consists of three elements: + +- 1) four motion vectors per macroblock as defined in F.2; +- 2) overlapped motion compensation for luminance as defined in F.3; +- 3) motion vectors over picture boundaries as defined in D.1. + +In order for the Deblocking Filter mode to be able to provide maximum performance when complexity considerations may prevent use of the OBMC part of the Advanced Prediction mode, the Deblocking Filter mode includes the ability to use four motion vectors per macroblock and motion vectors over picture boundaries. + +In summary, the three options defined in Annexes D, F and J contain the following five coding elements: + +- 1) motion vectors over picture boundaries (D.1); +- 2) extension of motion vector range (D.2); +- 3) four motion vectors per macroblock (F.2); +- 4) overlapped motion compensation for luminance (F.3); +- 5) deblocking edge filter (J.3). + +Table J.1 indicates which of the five elements are turned on depending on which of the three options defined in Annexes D, F and J are turned on. + +**Table J.1/H.263 – Feature Elements for UMV, AP, and DF modes** + +| Unrestricted Motion Vector mode | Advanced Prediction mode | Deblocking Filter mode | Motion vectors over picture boundaries | Extension of motion vector range | Four motion vectors per macroblock | Overlapped motion compensation for luminance | Deblocking edge filter | +|---------------------------------|--------------------------|------------------------|----------------------------------------|----------------------------------|------------------------------------|----------------------------------------------|------------------------| +| OFF | OFF | OFF | OFF | OFF | OFF | OFF | OFF | +| OFF | OFF | ON | ON | OFF | ON | OFF | ON | +| OFF | ON | OFF | ON | OFF | ON | ON | OFF | +| OFF | ON | ON | ON | OFF | ON | ON | ON | +| ON | OFF | OFF | ON | ON | OFF | OFF | OFF | +| ON | OFF | ON | ON | ON | ON | OFF | ON | +| ON | ON | OFF | ON | ON | ON | ON | OFF | +| ON | ON | ON | ON | ON | ON | ON | ON | + +## J.3 Definition of the deblocking edge filter + +The filter operations are performed across $8 \times 8$ block edges at the encoder as well as on the decoder side. The reconstructed image data (the sum of the prediction and reconstructed prediction error) are clipped to the range of 0 to 255 as described in 6.3.2. Then the filtering is applied, which alters the picture that is to be stored in the picture store for future prediction. The filtering operations include an additional clipping to ensure that resulting pixel values stay in the range 0..255. No filtering is performed across a picture edge, and when the Independent Segment Decoding mode is in use, no filtering is performed across slice edges when the Slice Structured mode is in use (see Annexes K and R) or across the top boundary of GOBs having GOB headers + +present when the Slice Structured mode is not in use (see Annex R). Chrominance as well as luminance data are filtered. + +When the mode described in this annex is used together with the Improved PB-frames mode of Annex M, the backward prediction of the B-macroblock is based on the reconstructed P-macroblock (named $P_{REC}$ in G.5) after the clipping operation but before the deblocking edge filter operations. The forward prediction of the B-macroblock is based on the filtered version of the previous decoded picture (the same picture data that are used for prediction of the P-macroblock). + +The deblocking filter operates using a set of four (clipped) pixel values on a horizontal or vertical line of the reconstructed picture, denoted as A, B, C and D, of which A and B belong to one block called block1 and C and D belong to a neighbouring block called block2 which is to the right of or below block1. Figure J.1 shows examples for the position of these pixels. + +![Figure J.1/H.263 – Examples of positions of filtered pixels. The diagram shows a grid of blocks. A vertical line represents a 'Block boundary' between 'block1' (left) and 'block2' (right). On the left side of the boundary, pixels A and B are shown. On the right side, pixels C and D are shown. Arrows point to these pixels with labels: 'Example for filtered pixels on a vertical block edge' for the vertical case and 'Example for filtered pixels on a horizontal block edge' for the horizontal case.](38d82ffe820e339811b396206f40a201_img.jpg) + +Figure J.1/H.263 – Examples of positions of filtered pixels. The diagram shows a grid of blocks. A vertical line represents a 'Block boundary' between 'block1' (left) and 'block2' (right). On the left side of the boundary, pixels A and B are shown. On the right side, pixels C and D are shown. Arrows point to these pixels with labels: 'Example for filtered pixels on a vertical block edge' for the vertical case and 'Example for filtered pixels on a horizontal block edge' for the horizontal case. + +**Figure J.1/H.263 – Examples of positions of filtered pixels** + +One or both of the following conditions must be fulfilled in order to apply the filter across a particular edge: + +- Condition 1: block1 belongs to a coded macroblock ( $COD==0 \parallel MB\text{-type} == INTRA$ ); or +- Condition 2: block2 belongs to a coded macroblock ( $COD==0 \parallel MB\text{-type} == INTRA$ ). + +If filtering is to be applied across the edge, A, B, C, and D shall be replaced by A1, B1, C1, D1 where: + +$$B1 = \text{clip}(B + d1)$$ + +$$C1 = \text{clip}(C - d1)$$ + +$$A1 = A - d2$$ + +$$D1 = D + d2$$ + +$$d = (A - 4B + 4C - D) / 8$$ + +$$d1 = \text{UpDownRamp}(d, \text{STRENGTH})$$ + +$$d2 = \text{clipd1}((A - D) / 4, d1/2)$$ + +$$\begin{aligned} \text{UpDownRamp}(x, \text{STRENGTH}) = \\ \text{SIGN}(x) * (\text{MAX}(0, \text{abs}(x) - \text{MAX}(0, 2 * (\text{abs}(x) - \text{STRENGTH})))) \end{aligned}$$ + +STRENGTH depends on QUANT and determines the amount of filtering. The relation between STRENGTH and QUANT is given in Table J.2. + +QUANT = quantization parameter used for block2 if block2 belongs to a coded macroblock, or + +QUANT = quantization parameter used for block1 if block2 does not belong to a coded macroblock (but block1 does). + +**Table J.2/H.263 – Relationship between QUANT and STRENGTH of filter** + +| QUANT | STRENGTH | QUANT | STRENGTH | +|-------|----------|-------|----------| +| 1 | 1 | 17 | 8 | +| 2 | 1 | 18 | 8 | +| 3 | 2 | 19 | 8 | +| 4 | 2 | 20 | 9 | +| 5 | 3 | 21 | 9 | +| 6 | 3 | 22 | 9 | +| 7 | 4 | 23 | 10 | +| 8 | 4 | 24 | 10 | +| 9 | 4 | 25 | 10 | +| 10 | 5 | 26 | 11 | +| 11 | 5 | 27 | 11 | +| 12 | 6 | 28 | 11 | +| 13 | 6 | 29 | 12 | +| 14 | 7 | 30 | 12 | +| 15 | 7 | 31 | 12 | +| 16 | 7 | | | + +The function $\text{clip}(x)$ is defined according to 6.3.2, and the function $\text{clipd1}(x, \text{lim})$ clips $x$ to the range $\pm \text{abs}(\text{lim})$ . The symbol "/" denotes division by truncation toward zero. + +Figure J.2 shows how the value of $d1$ varies as a function of $d$ . As a result, the filter has an effect only if $d$ is smaller than $2 \cdot \text{STRENGTH}$ (and different from zero). This is to prevent the filtering of strong true edges in the picture content. However, if the Reduced-Resolution Update mode is in use, STRENGTH is set to infinity, and as a result, the value of $d1$ is always equal to the value of $d$ (see Q.7.2). + +![A line graph showing parameter d1 as a function of parameter d. The vertical axis is labeled d1 and the horizontal axis is labeled d. The graph consists of three segments: a line from the origin (0,0) to a peak at d = Strength, a line from the peak to a point at d = 2*Strength, and a horizontal line from d = 2*Strength to the right. The peak value of d1 is at d = Strength. The horizontal axis has tick marks at 'Strength' and '2*Strength'. A small text 'T1602920-97' is located below the horizontal axis.](2cca454bbea734b85b2a785da04388f9_img.jpg) + +A line graph showing parameter d1 as a function of parameter d. The vertical axis is labeled d1 and the horizontal axis is labeled d. The graph consists of three segments: a line from the origin (0,0) to a peak at d = Strength, a line from the peak to a point at d = 2\*Strength, and a horizontal line from d = 2\*Strength to the right. The peak value of d1 is at d = Strength. The horizontal axis has tick marks at 'Strength' and '2\*Strength'. A small text 'T1602920-97' is located below the horizontal axis. + +**Figure J.2/H.263 – Parameter d1 as a function of parameter d for deblocking filter mode** + +The definition of d1 is designed to ensure that small mismatches between the encoder and decoder will remain small and will not build up over multiple pictures of a video sequence. This would be a problem, for example, with a condition that simply switches the filter on or off, because a mismatch of only $\pm 1$ for d could then cause the filter to be switched on at the encoder side and off at the decoder side, or vice versa. + +Due to rounding effects, the order of edges where filtering is performed must be specified. + +Filtering across horizontal edges: + +Basically this process is assumed to take place first. More precisely, the pixels $\begin{pmatrix} A \\ B \\ C \\ D \end{pmatrix}$ that are used in filtering across a horizontal edge shall not have been influenced by previous filtering across a vertical edge. + +Filtering across vertical edges: + +Before filtering across a vertical edge using pixels (A, B, C, D), all modifications of pixels (A, B, C, D) resulting from filtering across a horizontal edge shall have taken place. + +Note that if one or more of the pixels (A, B, C, D) taking part in a filtering process are outside of a picture, no filtering takes place. Also, if the Independent Segment Decoding mode is in use (see Annex R) and one or more of the pixels (A, B, C, D) taking part in a filtering process are in different video picture segments (see I.3 concerning when a block is considered to be in the same video picture segment), no filtering is performed. + +# Annex K + +# Slice Structured mode + +## K.1 Introduction + +This annex describes the optional Slice Structured mode of this Recommendation. The capability of this H.263 mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in the PLUSPTYPE field of the picture header. In order to facilitate optimal usage in a number of environments, this mode contains two submodes which are also capable of being signalled by external means (for example, ITU-T Rec. H.245). These two submodes are used to indicate whether or not rectangular slices will be used and/or whether the slices will be transmitted in sequential order or sent in an arbitrary order. + +A slice is defined as a slice header followed by consecutive macroblocks in scanning order. An exception is for the slice that immediately follows the picture start code in the bitstream for a picture (which is not necessarily the slice starting with macroblock 0). In this case only part of the slice header is transmitted as described in K.2. The slice layer defines a video picture segment, and is used in place of the GOB layer in this optional mode. A slice video picture segment starts at a macroblock boundary in the picture and contains a number of macroblocks. Different slices within the same picture shall not overlap with each other, and every macroblock shall belong to one and only one slice. + +This mode contains two submodes, which are signalled in the SSS field of the picture header: + +- 1) The Rectangular Slice submode (RS): When RS is in use, the slice shall occupy a rectangular region of width specified by the SWI parameter of the slice header in units of macroblocks, and contains a number of macroblocks in scanning order within the rectangular region. When the Rectangular Slice submode is not in use, the SWI field is not present in the slice header and a slice contains a number of macroblocks in scanning order within the picture as a whole. +- 2) The Arbitrary Slice Ordering submode (ASO): When ASO is in use, the slices may appear in any order within the bitstream. When ASO is not in use, the slices must be sent in the (unique) order for which the MBA field of the slice header is strictly increasing from each slice to each subsequent slice in the picture. + +Slice boundaries are treated differently from simple macroblock boundaries in order to allow slice header locations within the bitstream to act as resynchronization points for bit error and packet loss recovery and in order to allow out-of-order slice decoding within a picture. Thus, no data dependencies can cross the slice boundaries within the current picture, except for the Deblocking Filter mode which, when in use without the Independent Segment Decoding mode, filters across the boundaries of the blocks in the picture. However, motion vectors within a slice can cause data dependencies which cross the slice boundaries in the reference picture used for prediction purposes, unless the optional Independent Segment Decoding mode is in use. + +The following rules are adopted to ensure that slice boundary locations can act as resynchronization points and to ensure that slices can be sent out of order without causing additional decoding delays: + +- 1) The prediction of motion vector values are the same as if a GOB header were present (see 6.1.1), preventing the use of motion vectors of blocks outside the current slice for the prediction of the values of motion vectors within the slice. +- 2) The Advanced INTRA Coding mode (see Annex I) treats the slice boundary as if it were a picture boundary with respect to the prediction of INTRA block DCT coefficient values. + +- 3) The assignment of remote motion vectors for use in overlapped block motion compensation within the Advanced Prediction mode also prevents the use of motion vectors of blocks outside the current slice for use as remote motion vectors (see F.3). + +## K.2 Structure of slice layer + +The structure of the slice layer of the syntax is shown in Figure K.1 for all slices except the slice that immediately follows the picture start code in the bitstream for a picture. For the slice following the picture start code, only the emulation prevention bits (SEPB1, SEPB3, and conditionally SEPB2 as specified below), the MBA field and, when in the RS submode, also the SWI field are included. + +![](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +| | | | | | | | | | | | +|-------|-----|-------|------|-----|-------|--------|-----|-------|------|-----------------| +| SSTUF | SSC | SEPB1 | SSBI | MBA | SEPB2 | SQUANT | SWI | SEPB3 | GFID | Macroblock Data | +|-------|-----|-------|------|-----|-------|--------|-----|-------|------|-----------------| + +**Figure K.1/H.263 – Structure of slice layer** + +Refer to 5.2.5 for GFID, and to 5.3 for description of Macroblock layer. + +### K.2.1 Stuffing (SSTUF) (Variable length) + +A codeword of variable length consisting of less than 8 bits. Encoders shall insert this codeword directly before an SSC codeword whenever needed to ensure that SSC is byte aligned. If SSTUF is present, the last bit of SSTUF shall be the last (least significant) bit of a byte, so that the start of the SSC codeword is byte aligned. Decoders shall be designed to discard SSTUF. Notice that 0 is used for stuffing within SSTUF. + +### K.2.2 Slice Start Code (SSC) (17 bits) + +A word of 17 bits. Its value is 0000 0000 0000 0000 1. Slice start codes shall be byte aligned. This can be achieved by inserting SSTUF before the start code such that the first bit of the start code is the first (most significant) bit of a byte. The slice start code is not present for the slice which follows the picture start code. + +### K.2.3 Slice Emulation Prevention Bit 1 (SEPB1) (1 bit) + +A single bit always having the value of "1", which is included to prevent start code emulation. + +### K.2.4 Slice Sub-Bitstream Indicator (SSBI) (4 bits) + +A codeword of length four bits which is present only when CPM = "1" in the picture header. SSBI indicates the Sub-Bitstream number for the slice for Continuous Presence Multipoint and Video Multiplex operation, as described in Annex C. The mapping from the value of SSBI to the Sub-Bitstream number is shown in Table K.1. SSBI is not present for the slice which follows the picture start code. + +**Table K.1/H.263 – Values of SSBI and associated Sub-Bitstream numbers** + +| Sub-Bitstream number | SSBI field value | GN value emulated | +|----------------------|------------------|-------------------| +| 0 | 1001 | 25 | +| 1 | 1010 | 26 | +| 2 | 1011 | 27 | +| 3 | 1101 | 29 | + +### K.2.5 Macroblock Address (MBA) (5/6/7/9/11/12/13/14 bits) + +A codeword having a length that is dependent on the current picture size and whether the Reduced-Resolution Update mode is in effect (see Annex Q). The bits are the binary representation of the macroblock number of the first macroblock in the current slice as counted from the beginning of the picture in scanning order, starting with macroblock number 0 at the upper left corner. MBA uniquely identifies which macroblock in the picture the current slice starts with. Codeword lengths for this codeword are provided in Table K.2. For custom picture sizes, the field width is given by the first entry in the table that has an equal or larger number of macroblocks, and the maximum value is the number of macroblocks in the current picture minus one. When in the Reduced-Resolution Update mode, the relevant picture size is the lower resolution update picture size rather than the picture size indicated in the picture header (see Annex Q). + +**Table K.2/H.263 – Specification of MBA parameter** + +| Picture format | Default | | RRU mode | | +|----------------|-----------|-------------|-----------|-------------| +| | Max value | Field width | Max value | Field width | +| sub-QCIF | 47 | 6 | 11 | 5 | +| QCIF | 98 | 7 | 29 | 6 | +| CIF | 395 | 9 | 98 | 7 | +| 4CIF | 1583 | 11 | 395 | 9 | +| 16CIF | 6335 | 13 | 1583 | 11 | +| 2048 × 1152 | 9215 | 14 | 2303 | 12 | + +### K.2.6 Slice Emulation Prevention Bit 2 (SEPB2) (1 bit) + +A single bit always having the value "1", which is included under certain conditions to prevent start code emulation. For slices other than the one following the picture start code, SEPB2 is included only if the MBA field width is greater than 11 bits and CPM = "0" in the picture header, or if the MBA field width is greater than 9 bits and CPM = "1" in the picture header. For the slice following the picture start code, SEPB2 is included only if the Rectangular Slice submode is in use. + +### K.2.7 Quantizer Information (SQUANT) (5 bits) + +A fixed length codeword of five bits which indicates the quantizer QUANT to be used for that slice until updated by any subsequent DQUANT. The codewords are the natural binary representations of the values of QUANT which, being half the step sizes, range from 1 to 31. SQUANT is not present for the slice which follows the picture start code. + +### K.2.8 Slice Width Indication in Macroblocks (SWI) (3/4/5/6/7 bits) + +A codeword which is present only if the Rectangular Slice submode is active, and having a length which depends on the current picture size and whether the Reduced-Resolution Update mode is active, as specified in Table K.3. For custom picture sizes, the field width is given by the next standard format size which is equal or larger in width (QCIF, CIF, ... ), and the maximum value is the total number of macroblocks across the picture minus one. The last row of the table indicates the field width for picture sizes wider than 16CIF. SWI refers to the width of the current rectangular slice having its first macroblock (upper left) specified by MBA. The calculation of the actual slice width is given by: + +$$\text{Actual Slice Width} = \text{SWI} + 1$$ + +When in the Reduced-Resolution Update mode, the relevant picture size is that of the lower resolution picture size for the update information, rather than the picture size indicated in the picture header. + +**Table K.3/H.263 – Specification of SWI parameter** + +| Picture format | Default | | RRU mode | | +|-------------------------|------------------|--------------------|------------------|--------------------| +| | Max value | Field width | Max value | Field width | +| sub-QCIF | 7 | 4 | 3 | 3 | +| QCIF | 10 | 4 | 5 | 3 | +| CIF | 21 | 5 | 10 | 4 | +| 4CIF | 43 | 6 | 21 | 5 | +| 16CIF | 87 | 7 | 43 | 6 | +| 1412...2048 pixels wide | 127 | 7 | 63 | 6 | + +### **K.2.9 Slice Emulation Prevention Bit 3 (SEPB3) (1 bit)** + +A single bit always having the value of "1" in order to prevent start code emulation. + +# **Annex L** + +# **Supplemental enhancement information specification** + +## **L.1 Introduction** + +This annex describes the format of the supplemental enhancement information sent in the PSUPP field of the picture layer of this Recommendation. The capability of a decoder to provide any or all of the enhanced capabilities described in this annex may be signalled by external means (for example, ITU-T Rec. H.245). Decoders which do not provide the enhanced capabilities may simply discard any PSUPP information bits that appear in the bitstream. The presence of this supplemental enhancement information is indicated in PEI, and an additional PEI bit is inserted between every octet of PSUPP data, as described in 5.1.24 and 5.1.25. + +In this annex, a distinction is made between the "decoded picture" and the "displayed picture". For purposes of this annex, the "displayed picture" is a picture having the same picture format as specified for the current picture by the picture layer of the video bitstream syntax. The "displayed picture" is constructed as described in this annex from the decoded picture, the prior displayed picture, the supplementary enhancement information described herein, and in some cases partly from a background picture which is externally controlled. + +## **L.2 PSUPP format** + +The PSUPP data consists of a four-bit function type indication FTYPE, followed by a four-bit parameter data size specification DSIZE, followed by DSIZE octets of function parameter data, optionally followed by another function type indication, and so on. One function type indication value is defined as an escape code to provide for future extensibility to allow definition of more than fifteen different functions. A decoder which receives a function type indication which it does not support can discard the function parameter data for that function and then check for a + +subsequent function type indication which may be supported. The defined FTTYPE values are shown in Table L.1. + +**Table L.1/H.263 – FTTYPE function type values** + +| | | +|----|------------------------------------------| +| 0 | Reserved | +| 1 | Do Nothing | +| 2 | Full-Picture Freeze Request | +| 3 | Partial-Picture Freeze Request | +| 4 | Resizing Partial-Picture Freeze Request | +| 5 | Partial-Picture Freeze-Release Request | +| 6 | Full-Picture Snapshot Tag | +| 7 | Partial-Picture Snapshot Tag | +| 8 | Video Time Segment Start Tag | +| 9 | Video Time Segment End Tag | +| 10 | Progressive Refinement Segment Start Tag | +| 11 | Progressive Refinement Segment End Tag | +| 12 | Chroma Key Information | +| 13 | Reserved | +| 14 | Reserved | +| 15 | Extended Function Type | + +## **L.3 Do Nothing** + +No action is requested by the Do Nothing function. This function is used to prevent start code emulation. Whenever the last five or more bits of the final octet of the previous PSUPP octet are all zero and no additional PSUPP function requests are to be sent, the Do Nothing function shall be inserted into PSUPP to prevent the possibility of start code emulation. The Do Nothing function may also be sent when it is not required by rule expressed in the previous sentence. DSIZE shall be zero for the Do Nothing function. + +## **L.4 Full-Picture Freeze Request** + +The full-picture freeze request function indicates that the contents of the entire prior displayed video picture shall be kept unchanged, without updating the displayed picture using the contents of the current decoded picture. The displayed picture shall then remain unchanged until the freeze picture release bit in the current PTTYPE or in a subsequent PTTYPE is set to 1, or until timeout occurs, whichever comes first. The request shall lapse due to timeout after five seconds or five pictures, whichever is a longer period of time. The timeout can be prevented by the issuance of another full-picture freeze request prior to or upon expiration of the timeout period (e.g., repeating the request in the header of the first picture with temporal reference indicating a time interval greater than or equal to five seconds since issuance, or in the header of the fifth picture after issuance). DSIZE shall be zero for the full-picture freeze request function. + +## **L.5 Partial-Picture Freeze Request** + +The partial-picture freeze request function indicates that the contents of a specified rectangular area of the prior displayed video picture should be kept unchanged, without updating the specified area of the displayed picture using the contents of the current decoded picture. The specified area of the displayed picture shall then remain unchanged until the freeze picture release bit in the current + +PTYPE or in a subsequent PTYPE is set to 1, until a partial-picture freeze-release request affecting the specified area is received, until the source format specified in a picture header differs from that of previous picture headers, or until timeout occurs, whichever comes first. Any change in the picture source format shall act as a freeze release for all active partial-picture freeze requests. The request shall lapse due to timeout after five seconds or five pictures, whichever is a longer period of time. The timeout can be prevented by the issuance of an identical partial-picture freeze request prior to or upon expiration of the timeout period (e.g., repeating the request in the header of the first picture with temporal reference indicating a time interval greater than or equal to five seconds since issuance, or in the header of the fifth picture after issuance). DSIZE shall be equal to 4 for the partial-picture freeze request. The four octets of PSUPP that follow contain the horizontal and vertical location of the upper left corner of the frozen picture rectangle, and the width and height of the rectangle, respectively, using eight bits each and expressed in units of eight pixels. For example, a 24-pixel wide and 16 pixel tall area in the upper left corner of the video display is specified by the four parameters (0, 0, 3, 2). + +## **L.6 Resizing Partial-Picture Freeze Request** + +The resizing partial-picture freeze request function indicates that the contents of a specified rectangular area of the prior displayed video picture should be resized to fit into a smaller part of the displayed video picture, which should then be kept unchanged, without updating the specified area of the displayed picture using the contents of the current decoded picture. The specified area of the displayed picture shall then remain unchanged until the freeze release bit in the current PTYPE or in a subsequent PTYPE is set to 1, until a partial-picture freeze-release request affecting the specified area is received, until the source format specified in a picture header differs from that of previous picture headers, or until timeout occurs, whichever comes first. Any change in the picture source format shall act as a freeze release for all active resizing partial-picture freeze requests. The request shall lapse due to timeout after five seconds or five pictures, whichever is a longer period of time. The timeout can be prevented by the issuance of a partial-picture freeze request for the affected area of the displayed picture prior to or upon expiration of the timeout period (e.g., issuing a partial-picture freeze request in the header of the first picture with temporal reference indicating a time interval greater than or equal to five seconds since issuance, or in the header of the fifth picture after issuance). DSIZE shall be equal to 8 for the resizing partial-picture freeze request. The eight octets of PSUPP data that follow contain 32 bits used to specify the rectangular region of the affected area of the displayed picture, and then 32 bits used to specify the corresponding rectangular region of the affected area of the decoded picture. The width and height of the rectangular region in the decoded picture shall both be equal to $2^i$ times the width and height specified for the rectangular region in the displayed picture, where $i$ is an integer in the range of 1 to 8. The location and size of each of these two rectangular regions is specified using the same format as such a region is specified in the partial-picture freeze request function. + +## **L.7 Partial-Picture Freeze-Release Request** + +The partial-picture freeze-release request function indicates that the contents of a specified rectangular area of the displayed video picture shall be updated by the current and subsequent decoded pictures. DSIZE shall be equal to 4 for the partial-picture freeze-release request. The four octets of PSUPP data that follow specify a rectangular region of the displayed picture in the same format as such a region is specified in the partial-picture freeze request function. + +## **L.8 Full-Picture Snapshot Tag** + +The full-picture snapshot tag function indicates that the current picture is labelled for external use as a still-image snapshot of the video content. DSIZE shall be equal to 4 for the full-picture snapshot tag function. The four octets of PSUPP data that follow specify a snapshot identification number for external use. + +## **L.9 Partial-Picture Snapshot Tag** + +The partial-picture snapshot tag function indicates that a specified rectangular area of the current picture is labelled for external use as a still-image snapshot of the video content. DSIZE shall be equal to 8 for the partial-picture snapshot tag function. The first four octets of PSUPP data that follow specify a snapshot identification number for external use, and the remaining four octets of PSUPP data that follow specify a rectangular region of the decoded picture in the same format as such a region is specified in the partial-picture freeze request function. + +## **L.10 Video Time Segment Start Tag** + +The video time segment start tag function indicates that the beginning of a specified sub-sequence of video data is labelled as a useful section of video content for external use, starting with the current picture. The tagged sub-sequence of video data shall continue until stopped by the receipt of a matching video time segment end tag function or until timeout, whichever comes first. The tagged sub-sequence shall end due to timeout after five seconds or five pictures, whichever is a longer period of time. The timeout can be prevented by the issuance of an identical video time segment start tag function prior to or upon expiration of the timeout period (e.g., repeating the video time segment start tag function in the header of the first picture with temporal reference indicating a time interval greater than or equal to five seconds since issuance, or in the header of the fifth picture after issuance). DSIZE shall be equal to 4 for the video time segment start tag function. The four octets of PSUPP data that follow specify a video time segment identification number for external use. + +## **L.11 Video Time Segment End Tag** + +The video time segment end tag function indicates that the end of a specified sub-sequence of video data is labelled as a useful section of video content for external use, ending with the previous picture. DSIZE shall be equal to 4 for the video time segment start tag function. The four octets of PSUPP data that follow specify a video time segment identification number for external use. + +## **L.12 Progressive Refinement Segment Start Tag** + +The progressive refinement segment start tag function indicates the beginning of a specified sub-sequence of video data which is labelled as the current picture followed by a sequence of zero or more pictures of refinement of the quality of the current picture, rather than as a representation of a continually moving scene. The tagged sub-sequence of video data shall continue until stopped by the receipt of a matching progressive refinement segment end tag function or until timeout, whichever comes first. The tagged sub-sequence shall end due to timeout after five seconds or five pictures, whichever is a longer period of time. The timeout can be prevented by the issuance of an identical progressive refinement segment start tag function prior to or upon expiration of the timeout period (e.g., repeating the progressive refinement start tag function in the header of the first picture with temporal reference indicating a time interval greater than or equal to five seconds since issuance, or in the header of the fifth picture after issuance). DSIZE shall be equal to 4 for the video time segment start tag function. The four octets of PSUPP data that follow specify a progressive refinement segment identification number for external use. + +## **L.13 Progressive Refinement Segment End Tag** + +The progressive refinement segment end tag function indicates the end of a specified sub-sequence of video data which is labelled as an initial picture followed by a sequence of zero or more pictures of the refinement of the quality of the initial picture, and ending with the previous picture. DSIZE shall be equal to 4 for the video time segment start tag function. The four octets of PSUPP data that follow specify a progressive refinement identification number for external use. + +## L.14 Chroma Keying Information + +The Chroma Keying Information Function (CKIF) indicates that the "chroma keying" technique is used to represent "transparent" and "semi-transparent" pixels in the decoded video pictures. When being presented on the display, "transparent" pixels are not displayed. Instead, a background picture which is either a prior reference picture or is an externally controlled picture is revealed. Semi-transparent pixels are displayed by blending the pixel value in the current picture with the corresponding value in the background picture. One octet is used to indicate the keying color value for each component ( $Y$ , $C_B$ , or $C_R$ ) which is used for chroma keying. To represent pixels that are to be "semi-transparent", two threshold values, denoted as $T_1$ and $T_2$ , are used. Let $\alpha$ denote the transparency of a pixel; $\alpha = 255$ indicates that the pixel is opaque, and $\alpha = 0$ indicates that the pixel is transparent. For other values of $\alpha$ , the resulting value for a pixel should be a weighted combination of the pixel value in the current picture and the pixel value from the background picture (which is specified externally). The values of $\alpha$ may be used to form an image that is called an "alpha map." Thus, the resulting value for each component may be: + +$$[\alpha \cdot X + (255 - \alpha) \cdot Z] / 255$$ + +where $X$ is the decoded pixel component value (for $Y$ , $C_B$ , or $C_R$ ), and $Z$ is the corresponding pixel component value from the background picture. + +The $\alpha$ value can be calculated as follows. First, the distance of the pixel color from the key color value is calculated: + +$$d = A_Y(X_Y - K_Y)^2 + A_B(X_B - K_B)^2 + A_R(X_R - K_R)^2$$ + +in which $X_Y$ , $X_B$ , and $X_R$ are the $Y$ , $C_B$ , and $C_R$ values of the decoded pixel color, $K_Y$ , $K_B$ , and $K_R$ are the corresponding key color parameters, and $A_Y$ , $A_B$ , and $A_R$ are keying flag bits which indicate which color components are used as keys. Once the distance $d$ is calculated, the $\alpha$ value may be computed as specified in the following pseudo-code: + +``` +for each pixel + if (d < T1) then α = 0; + else if (d > T2) then α = 255; + else α = [255 · (d - T1)] / (T2 - T1) +``` + +However, the precise method for performing the chroma keying operation in the decoder is not specified herein, since normative specification of the method is not needed for interoperability. The process described here is provided for illustration purposes in order to convey the intended interpretation of the data parameters. + +Since the derived $\alpha$ value is simply a function of $X_Y$ , $X_B$ , and $X_R$ , a Look-Up Table (LUT) can be built to achieve the above operation. Such an LUT has $2^{8 \times N}$ entries corresponding to all pixel values, where $N$ is the number of color components used as keys. Each entry in the LUT would then contain the corresponding $\alpha$ value. + +DSIZE shall be in the range of 1 to 9 (inclusive) for chroma keying information, according to the amount of data sent with the CKIF. No more than one CKIF shall be sent with a picture. + +The first octet following the DSIZE octet shall contain the representation order of the current picture – streams having a lower representation order are assumed to form the background picture for streams having a higher representation order. + +If DSIZE is greater than one, the next octet after the representation order octet shall be used to send six flag bits defined as: + +- bit 1: $A_Y$ : A flag bit indicating the presence of a $K_Y$ key parameter for luminance $Y$ values +- bit 2: $A_B$ : A flag bit indicating the presence of a $K_B$ key parameter for chroma $C_B$ values +- bit 3: $A_R$ : A flag bit indicating the presence of a $K_R$ key parameter for chroma $C_R$ values +- bit 4: $A_1$ : A flag bit indicating the presence of a $T_1$ threshold parameter for transparency +- bit 5: $A_2$ : A flag bit indicating the presence of a $T_2$ threshold parameter for opacity +- bit 6: RPB: A flag bit indicating the use of the reference picture as a background picture +- bit 7: reserved +- bit 8: reserved + +DSIZE shall be equal to 1 or shall be equal to 2 plus the number of flag bits among $A_Y$ , $A_B$ , and $A_R$ which are set to 1, plus 2 times the number of bits among $A_1$ and $A_2$ which are set to 1. If DSIZE is greater than 1, then an additional octet shall be sent to specify the value of each color component for each of the flag bits $A_Y$ , $A_B$ , and $A_R$ which are set to one and two additional octets shall be sent to specify each of the flagged threshold values among $T_1$ and $T_2$ . These octets shall follow in the same order as the flag bits. + +If DSIZE is equal to 1, or if all three keying color flag bits $A_Y$ , $A_B$ , and $A_R$ , are zero, the keying flag bits $A_Y$ , $A_B$ , and $A_R$ and keying colours $K_Y$ , $K_B$ , and $K_R$ which were used for the previous keyed picture should also be used for the current picture. If no previous values have been sent for the video sequence, the default keying flag bits $A_Y = 1$ , $A_B = 1$ , and $A_R = 1$ and the default key colours $K_Y = 50$ , $K_B = 220$ , and $K_R = 100$ should be used as the previous values. + +If DSIZE is equal to 1, or if both of the keying threshold flag bits $A_1$ and $A_2$ are zero, the keying threshold values $T_1$ and $T_2$ which were used for the previous keyed picture should also be used for the current picture. If no previous values have been sent for the video sequence, the default threshold values $T_1 = 48$ and $T_2 = 75$ should be used as the previous values. + +In the portion where the pixels are "semi-transparent" (i.e., when $T_1 < d < T_2$ ), the decoded pixels typically contain the chroma key color in components where chroma keys are used. This may result in certain color artifacts. To address this problem, these pixel values may be adjusted before they are blended with the background color. Such a correction process may be applied to color components being used in the chroma key operation as indicated by the flag bits. The process is as follows: + +$$X' = K + (T_2 / d)(X - K)$$ + +where $X$ is the original decoded pixel component value, and $X'$ is the corrected value. + +Since the adjusted pixel values $X'_Y$ , $X'_B$ , and $X'_R$ are functions of $X_Y$ , $X_B$ , and $X_R$ , the color correction can be achieved by using an LUT. This LUT would have $2^{8N}$ entries corresponding to all pixel values, where $N$ is the number of color components used as keys. Each entry would then contain the corresponding corrected values. + +If the Reference Picture Background (RPB) flag bit is set to "1", this indicates that the temporally previous reference picture (prior to any Annex P resampling performed for the current picture) should be held as the (opaque) background of the current picture and of all subsequent chroma keyed pictures, until replaced by the arrival of another picture having an RPB flag set to "1". If the current picture has no temporally previous reference picture (i.e, if the current picture is a picture of type INTRA or EI), the picture to which the RPB flag bit refers is the picture which would normally + +have been the reference picture if the current picture were of type INTER or EP as appropriate. If the RPB flag bit is set to "0", this indicates that background should remain as previously controlled (either under external control or using a reference picture which was previously stored upon receipt of a prior picture having RPB set to "1"). + +The use of the chroma keying which is invoked by the issuance of the chroma keying information function shall start with the current picture and shall continue until a subsequent picture of type INTRA or EI occurs or until a timeout period expires, whichever comes first. The use of chroma keying shall end due to timeout after five seconds or five pictures, whichever is a longer period of time. The timeout can be prevented by the issuance of an identical chroma keying information function prior to or upon expiration of the timeout period (e.g., repeating the chroma keying information function in the header of the first picture with temporal reference indicating a time interval greater than or equal to five seconds since issuance, or in the header of the fifth picture after issuance). The encoder shall send sufficient information with the chroma keying information function for complete resynchronization to occur with each picture of type INTRA or EI and within each timeout interval (it shall not rely on using stored or default values of the key colours or thresholds). + +## **L.15 Extended function type** + +The extended function type indication is used to signal that the following PSUPP octet contains an extended function. The usage of extended functions is reserved for the ITU to have a later ability to define a larger number of backward-compatible PSUPP data functions. DSIZE shall be equal to zero for the extended function type indication. In order to allow backward compatibility of future use of the extended function type indication, decoders shall treat the second set of four bits in the octet which follows the extended function type indication as a DSIZE value indicating the number of subsequent octets of PSUPP that are to be skipped for extended function parameter data, which may be followed by additional FTYPE indications. + +# **Annex M** + +## **Improved PB-frames mode** + +## **M.1 Introduction** + +This annex describes an optional Improved PB-frames mode of this Recommendation. It is therefore considered to be advantageous to use the present Improved PB-frames mode instead of the PB-frames mode defined in Annex G. The capability of this mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in the PLUSPTYPE field of the picture header. + +Most parts of this option are similar to the PB-frame option defined in Annex G. + +To avoid confusion with B-pictures as defined in Annex O, the terms B-picture, B-macroblock, and B-block will not be used in this annex. Instead, we will use the notation $B_{PB}$ to mean the "B-part" of an Improved PB-frame. When reference is made to Annex G, B-picture and B-block shall be read as $B_{PB}$ -picture and $B_{PB}$ -block. + +The main difference between the PB-frames mode and the Improved PB-frames mode is that in the Improved PB-frames mode, the $B_{PB}$ -macroblock has available a forward and a backward prediction mode in addition to the bidirectional prediction mode. In this annex, MVDB (when present) refers to a forward motion vector. (Note that, in Annex G, MVDB was used to refer to an enhancement of the downscaled forward and backward vectors for bidirectional prediction, rather than a distinct forward motion vector.) + +All the differences from Annex G are identified in this annex. When nothing is indicated, it means that the same procedure as described in Annex G is used. + +## **M.2 BPP-macroblock prediction modes** + +There are three different ways of coding a BPP-macroblock. The different coding modes are signalled by the parameter MODB. The BPP-macroblock coding modes are: + +### **M.2.1 Bidirectional prediction** + +In the bidirectional prediction mode, prediction uses the reference pictures before and after the BPP-picture (in the case of a sequence of Improved PB-frames, this means the P-picture part of the temporally previous Improved PB-frame and the P-picture part of the current Improved PB-frame). This prediction is equivalent to the prediction defined in Annex G when $MV_D = 0$ . Notice that in this mode (and only in this mode), Motion Vector Data (MVD) of the PB-macroblock must be included even if the P-macroblock is INTRA coded. (Notice the difference between MVD – motion vector data – and $MV_D$ – delta vector – defined in Annex G.) + +### **M.2.2 Forward prediction** + +In the forward prediction mode, the vector data contained in MVDB are used for forward prediction from the previous reference picture (an INTRA or INTER picture, or the P-picture part of a PB or Improved PB-frame). This means that there is always only one $16 \times 16$ vector for the BPP-macroblock in this prediction mode. + +A simple predictor is used for coding of the forward motion vector. The rule for this predictor is that if the current macroblock is not at the far left edge of the picture or slice and the macroblock to the left has a forward motion vector, then the predictor of the forward motion vector for the current macroblock is set to the value of the forward motion vector of the block to the left; otherwise, the predictor is set to zero. The difference between the predictor and the desired motion vector is then VLC coded in the same way as vector data to be used for the P-picture (MVD). + +Concerning motion vectors over picture boundaries defined in D.1, the described technique also applies for the forward BPP-vector if this feature is in use (this applies for forward as well as for bidirectional prediction mode). + +### **M.2.3 Backward prediction** + +In the backward prediction mode, the prediction of the BPP macroblock is identical to PREC (defined in G.5). No motion vector data is used for the backward prediction. + +## **M.3 Calculation of vectors for bidirectional prediction of a the B-macroblock** + +In case bidirectional prediction is used, the scaled forward and backward vectors are calculated as described in Annex G when $MV_D = 0$ . + +## **M.4 MODB table** + +A new definition for MODB (replacing Table 11) is shown in Table M.1. It indicates the possible coding modes for a BPP-block. + +**Table M.1/H.263 – MODB table for Improved PB-frames mode** + +| Index | CBPB | MVDB | Number of bits | Code | Coding mode | +|-------|------|------|----------------|-------|--------------------------| +| 0 | | | 1 | 0 | Bidirectional prediction | +| 1 | x | | 2 | 10 | Bidirectional prediction | +| 2 | | x | 3 | 110 | Forward prediction | +| 3 | x | x | 4 | 1110 | Forward prediction | +| 4 | | | 5 | 11110 | Backward prediction | +| 5 | x | | 5 | 11111 | Backward prediction | + +NOTE – The symbol "x" indicates that the associated syntax element is present. + +# Annex N + +# Reference Picture Selection mode + +## N.1 Introduction + +This annex describes the optional Reference Picture Selection mode of this Recommendation, which operates using a modified interframe prediction method called "NEWPRED." The capability of this H.263 mode is signalled by external means (for example, ITU-T Rec. H.245). The amount of additional picture memory accommodated in the decoder may also be signalled by external means to help the memory management at the encoder. This mode can use backward channel messages sent from a decoder to an encoder to inform the encoder which part of which pictures have been correctly decoded at the decoder. The use of this mode is indicated in the PLUSPTYPE field of the picture header. This mode has two back-channel mode switches which define whether a backward channel is used and what kind of messages are returned on that backward channel from the decoder, and has another submode defined in terms of the channel for the backward channel messages. + +The two back-channel mode switches of this mode determine the type of messages sent on the back-channel, specifying whether ACK (Acknowledgment messages), or NACK (Non-Acknowledgment messages) are sent. Together, the two switches define four basic methods of operation: + +- 1) NEITHER, in which no back-channel data is returned from the decoder to the encoder; +- 2) ACK, in which the decoder returns only acknowledgment messages; +- 3) NACK, in which the decoder returns only non-acknowledgment messages; and +- 4) ACK+NACK, in which the decoder returns both acknowledgment and non-acknowledgment messages. + +The specific type of messages to be sent as outlined above is indicated in the picture header. + +There are also two methods of operation in terms of the channel for backward channel messages: + +- 1) Separate Logical Channel mode: This method of operation delivers back-channel data through a separate logical channel in the multiplex layer of the system; and +- 2) VideoMux mode: This method of operation delivers back-channel data for received video within the forward video data of a video stream of encoded data. + +This annex specifies a syntax for the backward channel messages as well as for forward-channel data. + +## N.2 Video source coding algorithm + +The source coder of this mode is shown in generalized form in Figure N.1. This figure shows a structure which uses a number of picture memories. The source coder may select one of the picture memories to suppress the temporal error propagation due to the inter-frame coding. The Independent Segment Decoding mode (see Annex R), which treats boundaries of GOBs with non-empty headers or slices as picture boundaries, can be used to avoid error propagation due to motion compensation across the boundaries of the GOBs or slices when this mode is applied to a smaller unit than a picture, such as a GOB or slice. The information to signal which picture is selected for prediction is included in the encoded bitstream. The strategy used by the encoder to select the picture to be used for prediction is out of the scope of this Recommendation. + +![Block diagram of the source coder for NEWPRED. The input 'Video in' is subtracted from a prediction signal (indicated by a circle with a minus sign). The result is processed by a switch (indicated by a dashed box with 'p' and 'o' terminals), then a Transform (T) block, and a Quantizer (Q) block. The Quantizer outputs 'qz' and 'q' to the 'To video multiplex coder'. The quantized signal is also processed by an inverse Quantizer (Q⁻¹) and an inverse Transform (T⁻¹) block, then added to the prediction signal (indicated by a circle with a plus sign). The prediction signal is generated by a Picture Memory (P) block with motion compensated variable delay, which outputs 'p' and 't' to the 'To video multiplex coder'. The P block is controlled by a switch (indicated by a dashed box with 'p' and 'o' terminals). The P block also feeds into a series of Additional Picture Memory (AP) blocks: AP₁, AP₂, ..., APₙ. The AP blocks are also controlled by switches (indicated by dashed boxes with 'p' and 'o' terminals). The AP blocks output to the 'To video multiplex coder'. A Coding control (CC) block provides control signals to the T, Q, and P blocks. The diagram is labeled 'T1602930-97'.](27d6042f4bce01ea5789efbd9e8d1f50_img.jpg) + +T Transform + Q Quantizer + P Picture Memory with motion compensated variable delay + AP Additional Picture Memory + CC Coding control + p Flag for INTRA/INTER + t Flag for transmitted or not + qz Quantizer indication + q Quantizing index for transform coefficients + v Motion vector + +Block diagram of the source coder for NEWPRED. The input 'Video in' is subtracted from a prediction signal (indicated by a circle with a minus sign). The result is processed by a switch (indicated by a dashed box with 'p' and 'o' terminals), then a Transform (T) block, and a Quantizer (Q) block. The Quantizer outputs 'qz' and 'q' to the 'To video multiplex coder'. The quantized signal is also processed by an inverse Quantizer (Q⁻¹) and an inverse Transform (T⁻¹) block, then added to the prediction signal (indicated by a circle with a plus sign). The prediction signal is generated by a Picture Memory (P) block with motion compensated variable delay, which outputs 'p' and 't' to the 'To video multiplex coder'. The P block is controlled by a switch (indicated by a dashed box with 'p' and 'o' terminals). The P block also feeds into a series of Additional Picture Memory (AP) blocks: AP₁, AP₂, ..., APₙ. The AP blocks are also controlled by switches (indicated by dashed boxes with 'p' and 'o' terminals). The AP blocks output to the 'To video multiplex coder'. A Coding control (CC) block provides control signals to the T, Q, and P blocks. The diagram is labeled 'T1602930-97'. + +Figure N.1/H.263 – Source coder for NEWPRED + +## N.3 Channel for back-channel messages + +This mode has two methods of operation in terms of the type of channel for back-channel messages. One is the separate logical channel mode and the other is the videomux mode. The separate logical channel mode is a preferred mode and delivers the back-channel message defined in N.4.2 through the dedicated logical channel. The videomux mode is prepared for the system which cannot set up the separate extra channel for the back-channel messages due to the restriction of the number of + +channels' combinations. The videomux mode delivers the back-channel messages through the same logical channel with the forward video data in the opposite direction. + +### N.3.1 Separate logical channel mode + +The separate logical channel mode delivers back-channel messages through a dedicated logical channel opened only for the purpose of the back-channel messages. The association mechanism with the forward channel which delivers video data is provided by external means (for example, ITU-T Rec. H.245). Separate logical channel operation requires an external framing mechanism for synchronization of the messages within the back channel, as the back-channel syntax defined herein contains no synchronization flag words. + +### N.3.2 Videomux mode + +The videomux mode delivers the back-channel messages through the same logical channel with the forward video data in the opposite direction. The syntax of the multiplexed bitstream is described in N.4.1. The back-channel messages may be inserted by using the Back-Channel message Indication (BCI) in the GOB or slice header. + +## N.4 Syntax + +### N.4.1 Forward channel + +The syntax for the forward-channel data which conveys the compressed video signal is altered only in the Group of Blocks (GOB) or slice layer. + +The syntax of the GOB layer is illustrated in Figure N.2. The fields of TRI, TR, TRPI, TRP, BCI, and BCM are added to Figure 9. + +![Figure N.2/H.263 – Structure of GOB layer for NEWPRED](b753a53960aa3a47023b9f767e02fecb_img.jpg) + +``` + +graph LR + GSTUF[GSTUF] --> GBSC[GBSC] + GBSC --> GN[GN] + GN --> GSBI[GSBI] + GSBI --> GFID[GFID] + GFID --> GQUANT[GQUANT] + GQUANT --> MB[Macroblock data] + GQUANT --> TRI[TRI] + TRI --> TR[TR] + TR --> TRPI[TRPI] + TRPI --> TRP[TRP] + TRP --> BCI[BCI] + BCI --> BCM[BCM] + BCM --> BCI + BCM --> MB + +``` + +T1602940-97 + +Figure N.2/H.263 – Structure of GOB layer for NEWPRED + +**Figure N.2/H.263 – Structure of GOB layer for NEWPRED** + +When the optional Slice Structured mode (see Annex K) is in use, the syntax of the slice layer is modified in the same way as the GOB layer. The syntax is illustrated Figure N.3. + +![Figure N.3/H.263 – Structure of slice layer for NEWPRED](dd8d0fefeae62d64861afbb42b0df50e_img.jpg) + +``` + +graph LR + SSTUF[SSTUF] --> SSC[SSC] + SSC --> SEPB1[SEPB1] + SEPB1 --> SSBI[SSBI] + SSBI --> MBA[MBA] + MBA --> SEPB2[SEPB2] + SEPB2 --> SQUANT[SQUANT] + SQUANT --> SWI[SWI] + SWI --> SEPB3[SEPB3] + SEPB3 --> GFID[GFID] + GFID --> MB[Macroblock data] + GFID --> TRI[TRI] + TRI --> TR[TR] + TR --> TRPI[TRPI] + TRPI --> TRP[TRP] + TRP --> BCI[BCI] + BCI --> BCM[BCM] + BCM --> BCI + BCM --> MB + +``` + +T1602950-97 + +Figure N.3/H.263 – Structure of slice layer for NEWPRED + +**Figure N.3/H.263 – Structure of slice layer for NEWPRED** + +#### **N.4.1.1 Temporal Reference Indicator (TRI) (1 bit)** + +TRI indicates whether or not the following TR field is present. + +0: TR field is not present. + +1: TR field is present. + +#### **N.4.1.2 Temporal Reference (TR) (8/10 bits)** + +When present, TR is an eight-bit number unless a custom picture clock frequency is in use, in which case it is a ten-bit number consisting of the concatenation of ETR and TR of the picture header. + +#### **N.4.1.3 Temporal Reference for Prediction Indicator (TRPI) (1 bit)** + +TRPI indicates whether or not the following TRP field is present: + +0: TRP field is not present. + +1: TRP field is present. + +TRPI shall be equal to zero whenever the picture is an I- or EI-picture. + +#### **N.4.1.4 Temporal Reference for Prediction (TRP) (10 bits)** + +When present (as indicated in TRPI), TRP indicates the Temporal Reference which is used for prediction of the encoding, except in the case of B-pictures and the B-picture part of an Improved PB-frame. For B-pictures or the B-picture part of an Improved PB-frame, the picture having the temporal reference TRP is used for the prediction in the forward direction. (Prediction in the reverse-temporal direction always uses the immediately temporally subsequent picture.) TRP is a ten-bit number. If a custom picture clock frequency was not in use for the reference picture, the two MSBs of TRP are zero and the LSBs contain the eight-bit TR found in the picture header of the reference picture. If a custom picture clock frequency was in use for the reference picture, TRP is a ten-bit number consisting of the concatenation of ETR and TR from the reference picture header. + +When TRP is not present, the most recent temporally previous anchor picture shall be used for prediction, as when not in the Reference Picture Selection mode. TRP is valid until the next PSC, GSC, or SSC. + +#### **N.4.1.5 Back-Channel message Indication (BCI) (Variable length)** + +This field contains one or two bits; when set to "1", it signals the presence of the following video Back-Channel Message (BCM) field. Otherwise, the field value is "01", which indicates the absence or the end of the video back-channel message field. Combinations of BCM and BCI may not be present, and may be repeated when present. BCI shall always be set to "01" if the videomux mode is not in use. + +#### **N.4.1.6 Back-Channel Message (BCM) (Variable length)** + +The Back-Channel Message having syntax as defined in N.4.2, which is present only if the preceding BCI field is set to "1". + +### **N.4.2 Back-Channel Message (BCM) syntax** + +The syntax for the back-channel which conveys the acknowledgment/non-acknowledgment messages is illustrated in Figure N.4. This message is returned from a decoder to an encoder in order to tell whether a forward-channel data was correctly decoded or not. + +| | | | | | | | | | | | | +|----|-----|----|--------|-------|------|------|-------|--------|-------|-----|-------| +| BT | URF | TR | ELNUMI | ELNUM | BCPM | BSBI | BEPB1 | GN/MBA | BEPB2 | RTR | BSTUF | +|----|-----|----|--------|-------|------|------|-------|--------|-------|-----|-------| + +**Figure N.4/H.263 – Structure of Back-Channel Message (BCM) syntax for NEWPRED** + +#### **N.4.2.1 Back-channel message Type (BT) (2 bits)** + +Back-channel message type indicates if the corresponding part of the encoded message is correctly decoded or not. Which type of message is required for the encoder is indicated in the picture header of the forward channel. + +00: Reserved for future use. + +01: Reserved for future use. + +10: NACK. This indicates the erroneous decoding of the corresponding part of the forward-channel data. + +11: ACK. This indicates the correct decoding of the corresponding part of the forward-channel data. + +#### **N.4.2.2 Unreliable Flag (URF) (1 bit)** + +The Unreliable Flag is set to 1 when a reliable value for TR or GN/MBA is not available to the decoder. (When BT is NACK, a reliable TR may not be available at the decoder.) + +0: Reliable. + +1: Unreliable. + +#### **N.4.2.3 Temporal Reference (TR) (10 bits)** + +Temporal reference contains the TR information of the video picture segment for which the ACK/NACK is indicated in the back-channel message. + +NOTE – The meaning of the term "video picture segment" as used herein is defined in Annex R. If a custom picture clock frequency was not in use for the reference picture, the two MSBs of TR are zero and the LSBs contain the eight-bit TR found in the picture header of the reference picture. If a custom picture clock frequency was in use for the reference picture, TR is a ten-bit number consisting of the concatenation of ETR and TR from the reference picture header. + +#### **N.4.2.4 Enhancement Layer Number Indication (ELNUMI) (1 bit)** + +The enhancement layer number indication is "0" unless the optional Temporal, SNR and Spatial Scalability mode (Annex O) is used in the forward-channel data and some enhancement layers of the forward channel are combined on one logical channel and the back-channel message refers to an enhancement layer (rather than the base layer), in which case the enhancement layer number indication shall be "1". + +#### **N.4.2.5 Enhancement Layer Number (ELNUM) (4 bits)** + +Enhancement layer number is present if and only if ELNUMI is "1", in which case it contains the layer number of the enhancement layer referred to in the back-channel message. + +#### **N.4.2.6 BCPM (1 bit)** + +BCPM is "0" unless the CPM mode is used in the forward-channel data, in which case it is "1". If BCPM is "1", this indicates that BSBI is present. + +#### **N.4.2.7 Back-channel Sub-Bitstream Indicator (BSBI) (2 bits)** + +A fixed length codeword of 2 bits that is only present if BCPM is "1". The BSBI is the natural binary representation of the appropriate Sub-Bitstream number in the forward-channel data for which the ACK/NACK message is indicated in the back-channel message as described in 5.2.4 and in Annex C. + +#### **N.4.2.8 Back-channel Emulation Prevention Bit 1 (BEPB1) (1 bit)** + +A field which is present if and only if the videomux mode is in use. This field is always set to "1" to prevent a start code emulation. + +#### **N.4.2.9 GOB Number/Macroblock Address (GN/MBA) (5/6/7/9/11/12/13/14 bits)** + +A GOB number or macroblock address is present in this field. If the optional Slice Structured mode (see Annex K) is not in use, this field contains the GOB number of the beginning of the video picture segment for which the NACK/ACK message is indicated in the back-channel message. If the optional Slice Structured mode is in use, this field contains the macroblock address of the beginning of the slice for which the NACK/ACK message is indicated in the back-channel message. The length of this field is the length specified elsewhere in this Recommendation for GN or MBA. + +NOTE – When this field is received in the videomux mode, the use of the optional Slice Structured mode refers to the use of this mode in the video bitstream to which the BCM applies and not in the video bitstream that transports the BCM data. + +#### **N.4.2.10 Back-channel Emulation Prevention Bit 2 (BEPB2) (1 bit)** + +A field which is present if and only if the videomux mode is in use. This field is always set to "1" to prevent a start code emulation. + +#### **N.4.2.11 Requested Temporal Reference (RTR) (10 bits)** + +Requested temporal reference is present only if BT is NACK. RTR indicates the requested temporal reference of the GOB or slice associated with the NACK. Typically, it is the TR of the last correctly decoded video picture segment of the corresponding position at the decoder. If a custom picture clock frequency was not in use for the requested reference picture, the two MSBs of RTR are zero and the LSBs contain the eight-bit TR found in the picture header of the requested reference picture. If a custom picture clock frequency was in use for the requested reference picture, RTR is a ten-bit number consisting of the concatenation of ETR and TR from the requested reference picture header. + +#### **N.4.2.12 Stuffing (BSTUF) (Variable length)** + +This field is present if and only if the separate logical channel mode is in use and the back-channel message is the last in an external frame. BSTUF consists of a codeword of variable length consisting of zero or more bits of value "0". This field is only present at the end of an external frame. + +## **N.5 Decoder process** + +The decoder of this mode may need an additional number of picture memories to store the correctly decoded video signals and their Temporal Reference (TR) information. The decoder uses the stored picture for which the TR is TRP as the reference picture for inter-frame decoding instead of the last decoded picture, if the TRP field exists in the forward-channel data. When the picture for which the TR is TRP is not available at the decoder, the decoder may send a forced INTRA update signal to the encoder by external means (for example, ITU-T Rec. H.245). Unless a different frame storage policy is negotiated by external means, correctly decoded video picture segments shall be stored into memory for use as later reference pictures on a first-in, first-out basis as shown in Figure N.1 (except for B-pictures, which are not used as reference pictures), and video picture segments which are detected as having been incorrectly decoded should not replace correctly decoded ones in this memory area. + +An Acknowledgment message (ACK) and a Non-Acknowledgment message (NACK) are defined as back-channel messages. An ACK may be returned when the decoder decodes a video picture segment successfully. NACKs may be returned when the decoder fails to decode a video picture segment, and may continue to be returned until the decoder gets the expected forward channel data which includes the requested TRP or an INTRA update. Which types of message shall be sent is indicated in the RPSMF field of the picture header of the forward-channel data. + +In a usage scenario known as "Video Redundancy Coding", the Reference Picture Selection mode may be used by some encoders in a manner in which more than one representation is sent for the pictured scene at the same temporal instant (usually using different reference pictures). In such a + +case in which the Reference Picture Selection mode is in use and in which adjacent pictures in the bitstream have the same temporal reference, the decoder shall regard this occurrence as an indication that redundant copies have been sent of approximately the same pictured scene content, and shall decode and use the first such received picture while discarding the subsequent redundant picture(s). + +# Annex O + +## Temporal, SNR, and Spatial Scalability mode + +This annex describes the optional mode of this Recommendation in support of Temporal, SNR, and Spatial Scalability. This mode may also be used in conjunction with error control schemes. The capability of this mode and the extent to which its features are supported is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in PLUSPTYPE. + +## O.1 Overview + +Scalability allows for the decoding of a sequence at more than one quality level. This is done by using a hierarchy of pictures and enhancement pictures partitioned into one or more layers. There are three types of pictures used for scalability: B-, EI-, and EP-pictures, as explained below. Each of these has an enhancement layer number ELNUM that indicates to which layer it belongs, and a reference layer number RLNUM that indicates which layer is used for its prediction. The lowest layer is called the base layer, and has layer number 1. + +Scalability is achieved by three basic methods: temporal, SNR, and spatial enhancement. + +### O.1.1 Temporal scalability + +Temporal scalability is achieved using bidirectionally predicted pictures, or B-pictures. B-pictures allow prediction from either or both a previous and subsequent reconstructed picture in the reference layer. This property generally results in improved compression efficiency as compared to that of P-pictures. These B-pictures differ from the B-picture part of a PB- (or Improved PB-) frame (see Annexes G and M) in that they are separate entities in the bitstream: they are not syntactically intermixed with a subsequent P- (or EP-) picture. + +B-pictures (and the B-part of PB- or Improved PB-frames) are not used as reference pictures for the prediction of any other pictures. This property allows for B-pictures to be discarded if necessary without adversely affecting any subsequent pictures, thus providing temporal scalability. Figure O.1 illustrates the predictive structure of P- and B-pictures. + +![Diagram illustrating B-picture prediction dependencies. It shows a sequence of five pictures: I1, B2, P3, B4, and P5. Arrows indicate prediction dependencies: I1 points to B2; B2 points to P3; P3 points to B4; B4 points to P5. Below the pictures, two long arrows indicate temporal order, pointing from left to right. The label T1602960-97 is present at the bottom right.](4ecb55f0a56c2f3deb9eeddfde39d501_img.jpg) + +The diagram shows a sequence of five pictures: I1, B2, P3, B4, and P5. Arrows indicate prediction dependencies: I1 points to B2; B2 points to P3; P3 points to B4; B4 points to P5. Below the pictures, two long arrows indicate temporal order, pointing from left to right. The label T1602960-97 is present at the bottom right. + +Diagram illustrating B-picture prediction dependencies. It shows a sequence of five pictures: I1, B2, P3, B4, and P5. Arrows indicate prediction dependencies: I1 points to B2; B2 points to P3; P3 points to B4; B4 points to P5. Below the pictures, two long arrows indicate temporal order, pointing from left to right. The label T1602960-97 is present at the bottom right. + +Figure O.1/H.263 – Illustration of B-picture prediction dependencies + +The location of B-pictures in the bitstream is in a data-dependence order rather than in strict temporal order. (This rule is consistent with the ordering of other pictures in the bitstream, but for all picture types other than the B-picture, no such conflict arises between the data-dependence order and the temporal order.) For example, if the pictures of a video sequence were numbered 1, 2, 3, ... , then the bitstream order of the encoded pictures would be I1, P3, B2, P5, B4, ... , where the subscript refers to the original picture number (as illustrated in Figure O.1). + +There is no limit to the number of B-pictures that may be inserted between pairs of reference pictures in the reference layer (other than what is necessary to prevent temporal ambiguity from overflows of the temporal reference field in the picture header). However, a maximum number of such pictures may be signalled by external means (for example, ITU-T Rec. H.245). + +The picture height, width, and pixel aspect ratio of a B-picture shall always be equal to those of its temporally subsequent reference layer picture. + +Motion vectors are allowed to extend beyond the picture boundaries of B-pictures. + +### O.1.2 SNR scalability + +The other basic method to achieve scalability is through spatial/SNR enhancement. Spatial scalability and SNR scalability are equivalent except for the use of interpolation as is described shortly. Because compression introduces artifacts and distortions, the difference between a reconstructed picture and its original in the encoder is (nearly always) a nonzero-valued picture, containing what can be called the coding error. Normally, this coding error is lost at the encoder and never recovered. With SNR scalability, these coding error pictures can also be encoded and sent to the decoder, producing an enhancement to the decoded picture. The extra data serves to increase the signal-to-noise ratio of the video picture, and hence, the term SNR scalability. Figure O.2 illustrates the data flow for SNR scalability. The vertical arrows from the lower layer illustrate that the picture in the enhancement layer is predicted from a reconstructed approximation of that picture in the reference (lower) layer. + +If prediction is only formed from the lower layer, then the enhancement layer picture is referred to as an EI-picture. It is possible, however, to create a modified bidirectionally predicted picture using both a prior enhancement layer picture and a temporally simultaneous lower layer reference picture. This type of picture is referred to as an EP-picture or "Enhancement" P-picture. The prediction flow for EI- and EP-pictures is shown in Figure O.2. (Although not specifically shown in Figure O.2, an EI-picture in an enhancement layer may have a P-picture as its lower layer reference picture, and an EP-picture may have an I-picture as its lower-layer enhancement picture.) + +![Diagram illustrating SNR scalability with two layers: Enhancement layer and Base layer. The Base layer contains I, P, and P pictures. The Enhancement layer contains EI, EP, and EP pictures. Arrows show temporal flow within the Base layer and vertical flow from Base layer pictures to Enhancement layer pictures. Horizontal arrows also show temporal flow within the Enhancement layer.](034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg) + +The diagram illustrates the data flow for SNR scalability across two layers: the Base layer and the Enhancement layer. The Base layer contains three pictures: an I-picture, followed by two P-pictures. The Enhancement layer contains three pictures: an EI-picture, followed by two EP-pictures. Arrows indicate the temporal flow of pictures within each layer (left to right). Vertical arrows point from each picture in the Base layer to its corresponding picture in the Enhancement layer, indicating that the enhancement layer pictures are predicted from the reconstructed approximation of the base layer pictures. Horizontal arrows also connect the EI-picture to the first EP-picture, and the first EP-picture to the second EP-picture, showing temporal dependencies within the enhancement layer. + +Diagram illustrating SNR scalability with two layers: Enhancement layer and Base layer. The Base layer contains I, P, and P pictures. The Enhancement layer contains EI, EP, and EP pictures. Arrows show temporal flow within the Base layer and vertical flow from Base layer pictures to Enhancement layer pictures. Horizontal arrows also show temporal flow within the Enhancement layer. + +Figure O.2/H.263 – Illustration of SNR scalability + +For both EI- and EP-pictures, the prediction from the reference layer uses no motion vectors. However, as with normal P-pictures, EP-pictures use motion vectors when predicting from their temporally prior reference picture in the same layer. + +### O.1.3 Spatial scalability + +The third and final scalability method in the Temporal, SNR, and Spatial Scalability mode is spatial scalability, which is closely related to SNR scalability. The only difference is that before the picture in the reference layer is used to predict the picture in the spatial enhancement layer, it is interpolated by a factor of two either horizontally or vertically (1-D spatial scalability), or both horizontally and vertically (2-D spatial scalability). The interpolation filters for this operation are defined in O.6. For a decoder to be capable of some forms of spatial scalability, it may also need to be capable of custom picture formats. For example, if the base layer is sub-QCIF ( $128 \times 96$ ), the 2-D spatial enhancement layer picture would be $256 \times 192$ , which does not correspond to a standard picture format. Another example would be if the base layer were QCIF ( $176 \times 144$ ), with the standard pixel aspect ratio of 12:11. A 1-D horizontal spatial enhancement layer would then correspond to a picture format of $352 \times 144$ with a pixel aspect ratio of 6:11. Thus a custom picture format would have to be used for the enhancement layer in these cases. An example which does not require a custom picture format would be the use of a QCIF base layer with a CIF 2-D spatial enhancement layer. Spatial scalability is illustrated in Figure O.3. + +![Diagram illustrating spatial scalability with two layers: Enhancement layer and Base layer. The Base layer contains I, P, and P pictures. The Enhancement layer contains EI, EP, and EP pictures. Arrows show temporal prediction within the Base layer and vertical prediction from the Base layer to the Enhancement layer. Horizontal arrows show temporal prediction within the Enhancement layer.](6e9d059430baba0c363e33749f68b107_img.jpg) + +The diagram illustrates spatial scalability with two layers: Enhancement layer and Base layer. The Base layer contains three pictures: I, P, and P. The Enhancement layer contains three pictures: EI, EP, and EP. Arrows indicate the flow of prediction: vertical arrows from Base layer pictures to Enhancement layer pictures (I to EI, P to EP, P to EP), horizontal arrows between pictures in the Base layer (I to P, P to P), and horizontal arrows between pictures in the Enhancement layer (EI to EP, EP to EP). A small label 'T1602980-97' is present at the bottom right of the diagram. + +Diagram illustrating spatial scalability with two layers: Enhancement layer and Base layer. The Base layer contains I, P, and P pictures. The Enhancement layer contains EI, EP, and EP pictures. Arrows show temporal prediction within the Base layer and vertical prediction from the Base layer to the Enhancement layer. Horizontal arrows show temporal prediction within the Enhancement layer. + +**Figure O.3/H.263 – Illustration of spatial scalability** + +Other than requiring an upsampling process to increase the size of the reference layer picture prior to its use as a reference for the encoding process, the processing and syntax for a spatial scalability picture is functionally identical to that for an SNR scalability picture. + +Since there is very little syntactical distinction between pictures using SNR scalability and pictures using spatial scalability, the pictures used for either purpose are called EI- and EP-pictures. + +The picture in the base layer which is used for upward prediction in an EI- or EP-picture may be an I-picture, a P-picture, or the P-part of a PB- or Improved PB-frame (but shall not be a B-picture or the B-part of a PB- or Improved PB-frame). + +### O.1.4 Multilayer scalability + +It is possible not only for B-pictures to be temporally inserted between pictures of types I, P, PB, and Improved PB, but also between pictures of types EI and EP, whether these consist of SNR or spatial enhancement pictures. It is also possible to have more than one SNR or spatial enhancement layer in conjunction with a base layer. Thus, a multilayer scalable bitstream can be a combination of SNR layers, spatial layers, and B-pictures. The size of a picture cannot decrease, however, with + +increasing layer number. It can only stay the same or increase by a factor of two in one or both dimensions. Figure O.4 illustrates a multilayer scalable bitstream. + +![Diagram illustrating multilayer scalability in H.263. It shows three layers: Base layer, Enhancement layer 1, and Enhancement layer 2. The Base layer contains I, P, P, P frames. Enhancement layer 1 contains EI, EP, EP, EP frames. Enhancement layer 2 contains EI, B, EI, EP frames. Arrows indicate temporal and spatial dependencies between frames.](c19f37cdfc7768db716bfc0cc5934cfb_img.jpg) + +The diagram illustrates a multilayer scalable bitstream with three layers: + + +- Base layer:** Contains four frames labeled I, P, P, P. Horizontal arrows show temporal dependencies: I to the first P, and subsequent P frames to each other. +- Enhancement layer 1:** Contains four frames labeled EI, EP, EP, EP. Vertical arrows show spatial dependencies from Base layer frames (I, P, P, P) to Enhancement layer 1 frames (EI, EP, EP, EP). Horizontal arrows show temporal dependencies: EI to the first EP, and subsequent EP frames to each other. +- Enhancement layer 2:** Contains four frames labeled EI, B, EI, EP. Vertical arrows show spatial dependencies from Enhancement layer 1 frames (EI, EP, EP, EP) to Enhancement layer 2 frames (EI, B, EI, EP). Horizontal arrows show temporal dependencies: EI to B, B to EI, and EI to EP. + +T1602990-97 + +Diagram illustrating multilayer scalability in H.263. It shows three layers: Base layer, Enhancement layer 1, and Enhancement layer 2. The Base layer contains I, P, P, P frames. Enhancement layer 1 contains EI, EP, EP, EP frames. Enhancement layer 2 contains EI, B, EI, EP frames. Arrows indicate temporal and spatial dependencies between frames. + +**Figure O.4/H.263 – Illustration of multilayer scalability** + +In the case of multilayer scalability, the picture in a reference layer which is used for upward prediction in an EI- or EP-picture may be a I-, P-, EI-, or EP-picture, or may be the P-part of a PB- or Improved PB-frame in the base layer (but shall not be a B-picture or the B-part of a PB- or Improved PB-frame). + +As with the two-layer case, B-pictures may occur in any layer. However, any picture in an enhancement layer which is temporally simultaneous with a B-picture in its reference layer must be a B-picture or the B-picture part of an PB- or Improved PB-frame. This is to preserve the disposable nature of B-pictures. Note, however, that B-pictures may occur in layers that have no corresponding picture in lower layers. This allows an encoder to send enhancement video with a higher picture rate than the lower layers. + +The enhancement layer number and the reference layer number for each enhancement picture (B-, EI-, or EP-) are indicated in the ELNUM and RLNUM fields, respectively, of the picture header (when present). See the inference rules described in 5.1.4.4 for when these fields are not present. If a B-picture appears in an enhancement layer in which temporally surrounding SNR or spatial scalability pictures also appear, the Reference Layer Number (RLNUM) of the B-picture shall be the same as the Enhancement Layer Number (ELNUM). + +The picture height, width, and pixel aspect ratio of a B-picture shall always be equal to those of its temporally subsequent reference layer picture. + +## O.2 Transmission order of pictures + +Pictures which are dependent on other pictures shall be located in the bitstream after the pictures on which they depend. + +The bitstream syntax order is specified such that for reference pictures (i.e., picture having types I, P, EI, or EP, or the P-part of PB or Improved PB), the following two rules shall be obeyed: + +- 1) All reference pictures with the same temporal reference shall appear in the bitstream in increasing enhancement layer order (since each lower layer reference picture is needed to decode the next higher layer reference picture). +- 2) All temporally simultaneous reference pictures as discussed in item 1) above shall appear in the bitstream prior to any B-pictures for which any of these reference pictures is the first temporally subsequent reference picture in the reference layer of the B-picture (in order to reduce the delay of decoding all reference pictures which may be needed as references for B-pictures). + +Then, the B-pictures with earlier temporal references shall follow (temporally ordered within each enhancement layer). + +The bitstream location of each B-picture shall comply with the following rules: + +- 1) Its bitstream location shall be after that of its first temporally subsequent reference picture in the reference layer (since the decoding of the B-picture generally depends on the prior decoding of that reference picture). +- 2) Its bitstream location shall be after that of all reference pictures that are temporally simultaneous with the first temporally subsequent reference picture in the reference layer (in order to reduce the delay of decoding all reference pictures which may be needed as references for B-pictures). +- 3) Its bitstream location shall precede the location of any additional temporally subsequent pictures other than B-pictures in its reference layer (since to allow otherwise would increase picture-storage memory requirements for the reference layer pictures). +- 4) Its bitstream location shall be after that of all EI- and EP-pictures that are temporally simultaneous with the first temporally subsequent reference picture. +- 5) Its bitstream location shall precede the location of all temporally subsequent pictures within its same enhancement layer (since to allow otherwise would introduce needless delay and increase picture-storage memory requirements for the enhancement layer). + +Figure O.5 illustrates two allowable picture transmission orders given by the rules above for the layering structure shown therein (with numbers in dotted-line boxes indicating the bitstream order, separated by commas for the two alternatives). + +![Diagram illustrating the picture transmission order across three layers: Base layer, Enhancement layer 1, and Enhancement layer 2. The Base layer contains I, B, and P pictures. Enhancement layer 1 contains EI, B, and EP pictures. Enhancement layer 2 contains B pictures. Arrows indicate the transmission order and reference relationships between pictures. Each picture is associated with a pair of numbers in a dashed box (e.g., [1,1] for the first I picture).](dd00cc2325415c09afb8bf178f60f33b_img.jpg) + +The diagram shows three layers of video pictures and their transmission order: + +- Base layer:** Contains three pictures: I (labeled [1,1]), B (labeled [8,5]), and P (labeled [3,3]). Transmission order is I → B → P. +- Enhancement layer 1:** Contains three pictures: EI (labeled [2,2]), B (labeled [6,7]), and EP (labeled [4,4]). Transmission order is EI → B → EP. Upward arrows show EI referencing the Base I picture and EP referencing the Base P picture. +- Enhancement layer 2:** Contains two pictures: B (labeled [5,6]) and B (labeled [7,8]). Transmission order is B → B. Upward arrows show the first B picture referencing the Base I picture and the second B picture referencing the Base P picture. + +Horizontal arrows indicate the transmission sequence within each layer, while diagonal arrows show reference relationships from enhancement pictures back to base pictures. + +Diagram illustrating the picture transmission order across three layers: Base layer, Enhancement layer 1, and Enhancement layer 2. The Base layer contains I, B, and P pictures. Enhancement layer 1 contains EI, B, and EP pictures. Enhancement layer 2 contains B pictures. Arrows indicate the transmission order and reference relationships between pictures. Each picture is associated with a pair of numbers in a dashed box (e.g., [1,1] for the first I picture). + +**Figure O.5/H.263 – Example of picture transmission order** + +## O.3 Picture layer syntax + +The Enhancement Layer Number (ELNUM) (see 5.1.11) is always present in any enhancement (B, EI, or EP) picture and shall not be present in I- or P-pictures, or in PB- or Improved PB-frames. The Reference Layer Number (RLNUM) (see 5.1.12) is present for some enhancement pictures and is inferred for others, as described in 5.1.12. + +There is exactly one base layer, and it has ELNUM and RLNUM equal to 1. The RLNUM gives the enhancement layer number of the forward and backward reference pictures for B-pictures, for the upward reference picture for EI- and EP-pictures. The reference pictures of the base layer may consist of I-, PB-, Improved PB-, and P-pictures, none of which include ELNUM or RLNUM in the picture header (their implied values are 1). + +For B-pictures, RLNUM must be less or equal to ELNUM, while for EI- and EP-pictures, RLNUM must be smaller than ELNUM. + +ELNUM may be different from the layer number used at the system level. Since B-pictures have no other pictures dependent on themselves, they may even be put in a separate enhancement layer by system components external to this Recommendation (for example, ITU-T Recs H.245 and H.223). Moreover, it is up to the implementor as to whether the enhancement pictures are sent in separate video channels or remain multiplexed together with the base layer pictures. + +As stated in 5.1.4.5, the Deblocking Filter mode (see Annex J) does not apply within B-pictures. This is because B-pictures are not used for the prediction of any other pictures, and thus the application of a deblocking filter to these pictures is entirely a post-processing technique which is outside the scope of this Recommendation. However, the use of some type of deblocking filter for B-pictures is encouraged, and a filter such as that described in Annex J may in fact be a good design to use for that purpose. + +The Temporal Reference (TR) (see 5.1.2) is defined exactly as for I- and P-pictures. + +There shall be no TRB (see 5.1.22) or DBQUANT (see 5.1.23) fields in the picture header of B-, EI- or EP-pictures. + +## 0.4 Macroblock layer syntax + +The macroblock layer syntax for B- and EP-pictures is the same, since each uses two reference pictures in a similar way. However, the interpretation varies slightly depending on the picture type. Figure O.6 indicates the B and EP syntax. The MBTYPE field indicates whether there is direct-mode prediction, forward prediction, backward/upward prediction, or bidirectional prediction. The MBTYPE is defined differently for B- and EP-pictures as described below. + +![Figure O.6/H.263 – Macroblock syntax for EP- and B-pictures. A flow diagram showing syntax elements. COD is in a rectangle (fixed length code). MBTYPE, CBPC, CBPY, DQUANT, MVDFW, MVDBW, and Block layer are in ovals (variable length code). Arrows show the sequence and various skip paths between elements.](0b2ee589f5c7802f3d332f421340cae1_img.jpg) + +``` + +graph LR + Start(( )) --> COD[COD] + COD --> MBTYPE((MBTYPE)) + MBTYPE --> CBPC((CBPC)) + CBPC --> CBPY((CBPY)) + CBPY --> DQUANT((DQUANT)) + DQUANT --> MVDFW((MVDFW)) + MVDFW --> MVDBW((MVDBW)) + MVDBW --> BlockLayer((Block layer)) + BlockLayer --> End(( )) + + %% Skip paths + COD --> End + MBTYPE --> MVDFW + MBTYPE --> BlockLayer + MBTYPE --> End + CBPC --> DQUANT + CBPY --> MVDFW + DQUANT --> BlockLayer + MVDFW --> End + MVDBW --> End + +``` + +Fixed length code      Variable length code + +T1603010-97 + +Figure O.6/H.263 – Macroblock syntax for EP- and B-pictures. A flow diagram showing syntax elements. COD is in a rectangle (fixed length code). MBTYPE, CBPC, CBPY, DQUANT, MVDFW, MVDBW, and Block layer are in ovals (variable length code). Arrows show the sequence and various skip paths between elements. + +**Figure O.6/H.263 – Macroblock syntax for EP- and B-pictures** + +The direct prediction mode is only available for B-pictures. It is a bidirectional prediction mode similar to the bidirectional mode in Improved PB-frames mode (Annex M). The only difference is that there is no restriction on which pixels can be backward predicted since the complete backward prediction image is known at the decoder. Bidirectional mode uses separate motion vectors for forward and backward prediction. In both direct and bidirectional mode, the prediction pixel values are calculated by averaging the forward and backward prediction pixels. The average is calculated by dividing the sum of the two predictions by two (division by truncation). In direct mode, when there are four motion vectors in the reference macroblock, then all four motion vectors are used as in Improved PB-frames mode (Annex M). + +For B-pictures, forward prediction means prediction from a previous reference picture in the reference layer. Backward prediction means prediction from a temporally subsequent reference picture in the reference layer. + +For EP-pictures, forward prediction means prediction from a previous EI- or EP-picture in the same layer, while upward prediction is used to mean prediction from the temporally simultaneous (possibly interpolated) reference picture in the reference layer. No motion vector is used for the upward prediction (which is syntactically in the same place as backward prediction for B-pictures), although one can be used for the forward prediction. + +The macroblock syntax for EI-pictures is slightly different. As shown in Figure O.7, the MBTYPE and CBPC are combined into an MCBPC field. No forward prediction is used, only upward prediction from the temporally simultaneous reference picture in the reference layer. No motion vector is used. + +In B and EP pictures, motion vectors over picture boundaries may be used as described in D.1 (although extension of the motion vector range as described in D.2 is only active if the Unrestricted Motion Vector mode is also in use). + +Encoders shall ensure conformance to D.1.1 for all macroblocks, including those predicted with the direct prediction mode; that is, the direct prediction mode shall not be selected by the encoder unless the motion vector values inferred by the direct mode prediction process do not result in any + +element of the $16 \times 16$ (or $8 \times 8$ ) prediction region having a horizontal or vertical distance more than 15 pixels outside the coded picture area. + +![Figure O.7/H.263 – Macroblock syntax for EI-pictures. The diagram shows a sequence of macroblock syntax elements: COD (Fixed length code), MCBPC (Variable length code), CBPY (Variable length code), DQUANT (Variable length code), and a Block layer. Arrows indicate the flow and feedback loops between these elements. A legend at the bottom shows a rectangle for 'Fixed length code' and an oval for 'Variable length code'.](708e7ef81dbf726e558047afe57d6ff7_img.jpg) + +The diagram illustrates the macroblock syntax for EI-pictures. It consists of a sequence of elements: COD (Fixed length code), MCBPC (Variable length code), CBPY (Variable length code), DQUANT (Variable length code), and a Block layer. Arrows indicate the flow and feedback loops between these elements. A legend at the bottom shows a rectangle for 'Fixed length code' and an oval for 'Variable length code'. + +Figure O.7/H.263 – Macroblock syntax for EI-pictures. The diagram shows a sequence of macroblock syntax elements: COD (Fixed length code), MCBPC (Variable length code), CBPY (Variable length code), DQUANT (Variable length code), and a Block layer. Arrows indicate the flow and feedback loops between these elements. A legend at the bottom shows a rectangle for 'Fixed length code' and an oval for 'Variable length code'. + +**Figure O.7/H.263 – Macroblock syntax for EI-pictures** + +### O.4.1 Coded macroblock indication (COD) (1 bit) + +A bit which, when set to "0", signals that the macroblock is coded. If set to "1", no further information is transmitted for this macroblock and the macroblock is handled as "skipped" as described below. + +### O.4.2 MBTYPE/MCBPC (VLC) + +There are different MBTYPE tables for B- and EP-pictures. For EI-pictures, there is instead a MCBPC table. Table O.1 is the MBTYPE table for B-pictures. Table O.2 is the MBTYPE table for EP-pictures. Table O.3 is the MCBPC table for EI-pictures. + +For B-pictures, the "Direct (skipped)" prediction type indicates that neither MBTYPE, nor any data, is transmitted in the macroblock and that the decoder derives forward and backward motion vectors and the corresponding bidirectional prediction. This is signalled by the COD bit. The "Forward (no texture)", the "Backward (no texture)", and the "Bi-dir (no texture)" prediction types for a B-picture indicate forward, backward, and bi-directional prediction with no coefficients, and with one transmitted motion vector for forward and backward prediction, and two transmitted motion vectors for bidirectional prediction. + +For EP-pictures, the "Forward (skipped)" prediction type indicates that no additional data is sent for the macroblock, so that the decoder should use forward prediction with a zero motion vector and no coefficients. The "Upward (no texture)" and "Bi-dir (no texture)" prediction types for an EP-picture indicate upward and bidirectional prediction with no coefficients, and with zero motion vector(s). + +For EI-pictures, the "Upward (skipped)" prediction type indicates that no additional data is sent for the macroblock, so that the decoder should use upward prediction with a zero motion vector and no coefficients. + +**Table O.1/H.263 – MBTYPE VLC codes for B-pictures** + +| Index | Prediction type | MVDFW | MVDBW | CBPC
+
CBPY | DQUANT | MBTYPE | Bits | +|-------|-----------------------|-------|-------|-------------------|--------|-------------|------| +| – | Direct (skipped) | | | | | (COD = 1) | 0 | +| 0 | Direct | | | X | | 11 | 2 | +| 1 | Direct + Q | | | X | X | 0001 | 4 | +| 2 | Forward (no texture) | X | | | | 100 | 3 | +| 3 | Forward | X | | X | | 101 | 3 | +| 4 | Forward + Q | X | | X | X | 0011 0 | 5 | +| 5 | Backward (no texture) | | X | | | 010 | 3 | +| 6 | Backward | | X | X | | 011 | 3 | +| 7 | Backward + Q | | X | X | X | 0011 1 | 5 | +| 8 | Bi-dir (no texture) | X | X | | | 0010 0 | 5 | +| 9 | Bi-dir | X | X | X | | 0010 1 | 5 | +| 10 | Bi-dir + Q | X | X | X | X | 0000 1 | 5 | +| 11 | INTRA | | | X | | 0000 01 | 6 | +| 12 | INTRA + Q | | | X | X | 0000 001 | 7 | +| 13 | Stuffing | | | | | 0000 0000 1 | 9 | + +**Table O.2/H.263 – MBTYPE VLC codes for EP-pictures** + +| Index | Prediction type | MVDFW | MVDBW | CBPC
+
CBPY | DQUANT | MBTYPE | Bits | +|-------|---------------------|-------|-------|-------------------|--------|-------------|------| +| – | Forward (skipped) | | | | | (COD = 1) | 0 | +| 0 | Forward | X | | X | | 1 | 1 | +| 1 | Forward + Q | X | | X | X | 001 | 3 | +| 2 | Upward (no texture) | | | | | 010 | 3 | +| 3 | Upward | | | X | | 011 | 3 | +| 4 | Upward + Q | | | X | X | 0000 1 | 5 | +| 5 | Bi-dir (no texture) | | | | | 0001 0 | 5 | +| 6 | Bi-dir | X | | X | | 0001 1 | 5 | +| 7 | Bi-dir + Q | X | | X | X | 0000 01 | 6 | +| 8 | INTRA | | | X | | 0000 001 | 7 | +| 9 | INTRA + Q | | | X | X | 0000 0001 | 8 | +| 10 | Stuffing | | | | | 0000 0000 1 | 9 | + +**Table O.3/H.263 – MCBPC VLC codes for EI-pictures** + +| Index | Prediction type | Code block pattern (56) | CBPY | DQUANT | MCBPC | Bits | +|-------|------------------|-------------------------|------|--------|-------------|------| +| – | Upward (skipped) | | | | (COD = 1) | 0 | +| 0 | Upward | 00 | X | | 1 | 1 | +| 1 | Upward | 01 | X | | 001 | 3 | +| 2 | Upward | 10 | X | | 010 | 3 | +| 3 | Upward | 11 | X | | 011 | 3 | +| 4 | Upward + Q | 00 | X | X | 0001 | 4 | +| 5 | Upward + Q | 01 | X | X | 0000 001 | 7 | +| 6 | Upward + Q | 10 | X | X | 0000 010 | 7 | +| 7 | Upward + Q | 11 | X | X | 0000 011 | 7 | +| 8 | INTRA | 00 | X | | 0000 0001 | 8 | +| 9 | INTRA | 01 | X | | 0000 1001 | 8 | +| 10 | INTRA | 10 | X | | 0000 1010 | 8 | +| 11 | INTRA | 11 | X | | 0000 1011 | 8 | +| 12 | INTRA+Q | 00 | X | X | 0000 1100 | 8 | +| 13 | INTRA+Q | 01 | X | X | 0000 1101 | 8 | +| 14 | INTRA+Q | 10 | X | X | 0000 1110 | 8 | +| 15 | INTRA+Q | 11 | X | X | 0000 1111 | 8 | +| 16 | Stuffing | | | | 0000 0000 1 | 9 | + +### O.4.3 Coded Block Pattern for Chrominance (CBPC) (Variable length) + +When present, CBPC indicates the coded block pattern for chrominance blocks as described in Table O.4. CBPC is present only for EP- and B-pictures, when its presence is indicated by MBTYPE (see Tables O.1 and O.2). + +**Table O.4/H.263 – CBPC VLC codes** + +| Index | Code block pattern (56) | CBPC | Bits | +|-------|-------------------------|------|------| +| 0 | 00 | 0 | 1 | +| 1 | 01 | 10 | 2 | +| 2 | 10 | 111 | 3 | +| 3 | 11 | 110 | 3 | + +### O.4.4 Coded Block Pattern for Luminance (CBPY) (Variable length) + +When present, CBPY indicates which blocks in the luminance portion of the macroblock are present. CBPY is present only when its presence is indicated by MBTYPE (see Tables O.1, O.2 and O.3). CBPY is coded as described in 5.3.5 and in Table 12. Upward predicted macroblocks in EI- and EP-pictures, bidirectional predicted macroblocks in EP-pictures, and INTRA macroblocks in EI-, EP-, and B-pictures use the CBPY definition for INTRA macroblocks, and other macroblock types in EI-, EP-, and B-pictures use the CBPY definition for INTER macroblocks. + +### O.4.5 Quantizer Information (DQUANT) (2 bits/Variable length) + +DQUANT is used as in other picture macroblock types. See 5.3.6 and Annex T. + +### **O.4.6 Motion vector data (MVDFW, MVDBW) (Variable length)** + +MVDFW is the motion vector data for the forward vector, if present. MVDBW is the motion vector data for the backward vector, if present (allowed only in B-pictures). The variable length codewords are given in Table 14, or in Table D.3 if the Unrestricted Motion Vector mode is used (see Annex D). + +## **O.5 Motion vector decoding** + +### **O.5.1 Differential motion vectors** + +Motion vectors for forward, backward or bidirectionally predicted blocks are differentially encoded. To recover the macroblock motion vectors, a prediction is added to the motion vector differences. The predictions are formed in a similar manner to that described in 6.1.1, except that forward motion vectors are predicted only from forward motion vectors in surrounding macroblocks, and backward motion vectors are predicted only from backward motion vectors in surrounding macroblocks. The same decision rules apply for the special cases at picture, GOB or slice borders as described in 6.1.1. If a neighboring macroblock does not have a motion vector of the same type (forward or backward), the candidate predictor for that macroblock is zero for that motion vector type. + +### **O.5.2 Motion vectors in direct mode** + +For macroblocks coded in direct mode, no vector differences are transmitted. Instead, the forward and backward motion vectors are directly computed from the temporally consecutive P-vector as described in G.4 with the restriction that $MV_D$ is always zero. These derived vectors are not used for prediction of other motion vectors. If the corresponding area of the temporally subsequent reference picture is coded in INTRA mode, the forward and backward motion vectors assigned to that area for use in the prediction process for the direct mode shall have the value zero. + +## **O.6 Interpolation filters** + +The method by which a picture is interpolated for 2-D spatial scalability is shown in Figures O.8 and O.9. The first figure shows the interpolation for interior pixels, while the second one shows the interpolation close to picture boundaries. This is the same technique used in Annex Q and in some cases in Annex P. The method by which a picture is interpolated for 1-D spatial scalability is shown in Figures O.10 and O.11. Figure O.10 shows the interpolation for interior pixels in the horizontal direction. The interpolation for the vertical direction is analogous. Figure O.11 shows the interpolation for pixels at picture boundaries. Again, the interpolation for the vertical direction is analogous. Again, this is the same technique used in some cases in Annex P. + +![Diagram showing pixel positions for interpolation. A 4x4 grid of circles is shown. The outer circles are white (interpolated). The inner circles are labeled: top-left is 'A' (gray, original), top-right is 'B' (gray, original), bottom-left is 'C' (gray, original), and bottom-right is 'D' (gray, original). Between A and B are two white circles labeled 'a' and 'b'. Between C and D are two white circles labeled 'c' and 'd'. To the right of the grid are four equations for calculating 'a', 'b', 'c', and 'd' based on 'A', 'B', 'C', and 'D'. Below the equations are three vertical dots. At the bottom of the grid area is the text 'T1603030-97'.](49d7bfbc65a92a7e1bd61777326a212d_img.jpg) + +$$a = (9A + 3B + 3C + D + 8) / 16$$ + +$$b = (3A + 9B + C + 3D + 8) / 16$$ + +$$c = (3A + B + 9C + 3D + 8) / 16$$ + +$$d = (A + 3B + 3C + 9D + 8) / 16$$ + +⋮ + +T1603030-97 + +Diagram showing pixel positions for interpolation. A 4x4 grid of circles is shown. The outer circles are white (interpolated). The inner circles are labeled: top-left is 'A' (gray, original), top-right is 'B' (gray, original), bottom-left is 'C' (gray, original), and bottom-right is 'D' (gray, original). Between A and B are two white circles labeled 'a' and 'b'. Between C and D are two white circles labeled 'c' and 'd'. To the right of the grid are four equations for calculating 'a', 'b', 'c', and 'd' based on 'A', 'B', 'C', and 'D'. Below the equations are three vertical dots. At the bottom of the grid area is the text 'T1603030-97'. + +- Image: Gray circle + + Original pixel positions +- Image: White circle + + Interpolated pixel positions + +**Figure O.8/H.263 – Method for interpolating pixels for 2-D scalability** + +![Diagram illustrating 2-D interpolation at boundaries. It shows a grid of pixels with original positions A, B, C, and D (shaded gray) and interpolated positions a, b, c, d, and e (white). Formulas for each interpolated pixel are provided: a = A, b = (3 * A + B + 2) / 4, c = (A + 3 * B + 2) / 4, d = (3 * A + C + 2) / 4, and e = (A + 3 * C + 2) / 4. A legend indicates that shaded circles are original pixel positions and white circles are interpolated pixel positions. The diagram is labeled T1603040-97. Shaded circle White circle](fda85db2e355bb8e3edcd5a74bf3d673_img.jpg) + +Picture boundary + +$a = A$ + $b = (3 * A + B + 2) / 4$ + $c = (A + 3 * B + 2) / 4$ + $d = (3 * A + C + 2) / 4$ + $e = (A + 3 * C + 2) / 4$ + +T1603040-97 + +Picture boundary + +Original pixel positions + Interpolated pixel positions + +Diagram illustrating 2-D interpolation at boundaries. It shows a grid of pixels with original positions A, B, C, and D (shaded gray) and interpolated positions a, b, c, d, and e (white). Formulas for each interpolated pixel are provided: a = A, b = (3 \* A + B + 2) / 4, c = (A + 3 \* B + 2) / 4, d = (3 \* A + C + 2) / 4, and e = (A + 3 \* C + 2) / 4. A legend indicates that shaded circles are original pixel positions and white circles are interpolated pixel positions. The diagram is labeled T1603040-97. Shaded circle White circle + +**Figure O.9/H.263 – Method for 2-D interpolation at boundaries** + +![Diagram illustrating pixel interpolation for 1-D scalability. It shows a horizontal sequence of pixels: white, shaded A, white a, white b, shaded B, white. Formulas for a and b are provided: a = (3A + B + 2) / 4 and b = (A + 3B + 2) / 4. A legend indicates that shaded circles are original pixel positions and white circles are interpolated pixel positions. The diagram is labeled T1603050-97. Shaded circle White circle](9cf678d634932a43b7f6582878972a5d_img.jpg) + +$a = (3A + B + 2) / 4$ + $b = (A + 3B + 2) / 4$ + +Original pixel positions + Interpolated pixel positions + +T1603050-97 + +Diagram illustrating pixel interpolation for 1-D scalability. It shows a horizontal sequence of pixels: white, shaded A, white a, white b, shaded B, white. Formulas for a and b are provided: a = (3A + B + 2) / 4 and b = (A + 3B + 2) / 4. A legend indicates that shaded circles are original pixel positions and white circles are interpolated pixel positions. The diagram is labeled T1603050-97. Shaded circle White circle + +**Figure O.10/H.263 – Method for interpolating pixels for 1-D scalability** + +![Diagram illustrating the method for 1-D interpolation at picture boundaries. It shows a horizontal line representing the 'Picture boundary'. Above the line, there are six circles. From left to right: a white circle labeled 'a', a gray circle labeled 'A', a white circle, a white circle, a gray circle labeled 'B', and a white circle. To the right of the circles, the text 'a = A' is present. Below the line, the text 'T1603060-97' is present. Below the diagram, there is a legend. It consists of two entries: a gray circle followed by the text 'Original pixel positions', and a white circle followed by the text 'Interpolated pixel positions'. The text 'Picture boundary' is also written below the line on the left side.](3d46409f8d0190e611a910ff27f8ec07_img.jpg) + +Diagram illustrating the method for 1-D interpolation at picture boundaries. It shows a horizontal line representing the 'Picture boundary'. Above the line, there are six circles. From left to right: a white circle labeled 'a', a gray circle labeled 'A', a white circle, a white circle, a gray circle labeled 'B', and a white circle. To the right of the circles, the text 'a = A' is present. Below the line, the text 'T1603060-97' is present. Below the diagram, there is a legend. It consists of two entries: a gray circle followed by the text 'Original pixel positions', and a white circle followed by the text 'Interpolated pixel positions'. The text 'Picture boundary' is also written below the line on the left side. + +**Figure O.11/H.263 – Method for 1-D interpolation at picture boundaries** + +# Annex P + +## Reference picture resampling + +## P.1 Introduction + +This annex describes the use and syntax of a resampling process which can be applied to the previous decoded reference picture in order to generate a "warped" picture for use in predicting the current picture. This resampling syntax can specify the relationship of the current picture to a prior picture having a different source format, and can also specify a "global motion" warping alteration of the shape, size, and location of the prior picture with respect to the current picture. In particular, the Reference Picture Resampling mode can be used to adaptively alter the resolution of pictures during encoding. A fast algorithm is used to generate bilinear interpolation coefficients. The capability to use this mode and the extent to which its features are supported is negotiated externally (for example, ITU-T Rec. H.245). This mode may be used in restricted scenarios that may be defined during capability negotiation (e.g., to support only factor-of-four picture resizing, to support only half-pixel resolution picture warping, or to support arbitrary image size resizing and displacements). + +NOTE – The default image transformation between pictures of differing resolutions is defined to maintain the spatial alignment of the edges of the picture area and of the relative locations of the luminance and chrominance samples. This may have implications on the design of any resampling operations used for generating pictures of various resolutions at the encoder and for displaying pictures of various resolutions after decoding (particularly regarding shifts in spatial location caused by phase shifts induced in resampling). Also, since this mode can be used for dynamic adaptive picture resolution changes, operation with this mode may benefit from external negotiation to display the decoded picture at a higher resolution than its encoded picture size, in order to allow switching between encoded picture sizes without resizing the picture display. + +If the Reference Picture Resampling bit in the PLUSPTYPE field is not set, but PLUSPTYPE is present and the picture is an INTER-, B-, or EP-picture or an Improved PB-frame, and the picture size differs from that of the temporally previous encoded picture, this condition invokes Reference Picture Resampling with warping parameters (see P.2.2) set equal to zero, fill mode (see P.2.3) set to *clip*, and displacement accuracy (see P.2.1) set to $\frac{1}{16}$ -pixel accuracy. This causes the resampling process to easily act as a predictively-encoded change in picture resolution. In simple factor-of-four + +resolution change cases such as transitions between CIF and 4CIF, the resampling process reduces to the same simple filter used for Spatial Scalability (Annex O) or for Reduced-Resolution Update (Annex Q), except for the application of rounding control. + +If the picture is an EP-picture and the Reference Picture Resampling bit is set in the PLUSPTYPE field of the picture header of the reference layer, this bit shall also be set in the picture header of the EP-picture in the enhancement layer. + +If a B-picture uses the Reference Picture Resampling mode, the resampling process shall be applied to the temporally previous anchor picture and not to the temporally subsequent one. The temporally previous anchor picture to which the resampling process is applied shall be the decoded picture (i.e., prior to any resampling applied by Reference Picture Resampling if this mode is also invoked for the subsequent reference picture). The temporally subsequent anchor picture shall have the same picture size as the B-picture. + +If the Reference Picture Resampling mode is invoked for an Improved PB-frame, one set of warping parameters is sent and the resampled reference picture is used as the reference for both the B- and P-parts of the Improved PB-frame. + +The Reference Picture Resampling mode shall not be invoked when the Reference Picture Selection mode (see Annex N) is in use unless the values of TRPI and TRP in all picture, GOB, and slice headers of the current picture specify the use of the same reference picture – in which case the indicated reference picture is the picture that determines whether the reference picture resampling process is to be invoked implicitly and is the picture to which the resampling process shall be applied. + +The Reference Picture Resampling is defined in terms of the displacement of the four corners of the current picture area. For the luminance field of the current picture with horizontal size $H$ and vertical size $V$ , four conceptual motion vectors $\underline{v}^{00}$ , $\underline{v}^{H0}$ , $\underline{v}^{0V}$ , and $\underline{v}^{HV}$ , are defined for the upper left, upper right, lower left, and lower right corners of the picture, respectively. These vectors describe how to move the corners of the current picture to map them onto the corresponding corners of the previous decoded picture, as shown in Figure P.1. The units of these vectors are the same as those in the reference picture grid. To generate a vector $\underline{v}(x, y)$ at some real-valued location $(x, y)$ in the interior of the current picture, an approximation to bilinear interpolation is used, i.e., as in: + +$$\underline{v}(x, y) = \left(1 - \frac{y}{V}\right) \left[ \left(1 - \frac{x}{H}\right) \underline{v}^{00} + \left(\frac{x}{H}\right) \underline{v}^{H0} \right] + \left(\frac{y}{V}\right) \left[ \left(1 - \frac{x}{H}\right) \underline{v}^{0V} + \left(\frac{x}{H}\right) \underline{v}^{HV} \right]$$ + +![Figure P.1/H.263: A diagram illustrating conceptual motion vectors used for warping. It shows a rectangular frame representing a picture. Four vectors originate from the top-left corner: v^00 (solid line to the top-left corner of a smaller, shifted rectangle), v^H0 (dotted line to the top-right corner of the shifted rectangle), v^0V (dotted line to the bottom-left corner of the shifted rectangle), and v^HV (solid line to the bottom-right corner of the shifted rectangle). The text 'T1603070-97' is located at the bottom right of the diagram.](07e69273eef4109e165ab7129bf9f350_img.jpg) + +Figure P.1/H.263: A diagram illustrating conceptual motion vectors used for warping. It shows a rectangular frame representing a picture. Four vectors originate from the top-left corner: v^00 (solid line to the top-left corner of a smaller, shifted rectangle), v^H0 (dotted line to the top-right corner of the shifted rectangle), v^0V (dotted line to the bottom-left corner of the shifted rectangle), and v^HV (solid line to the bottom-right corner of the shifted rectangle). The text 'T1603070-97' is located at the bottom right of the diagram. + +**Figure P.1/H.263 – Example of conceptual motion vectors used for warping** + +The horizontal size $H$ and vertical size $V$ of the current picture, and the horizontal size $H_R$ and vertical size $V_R$ of the reference picture are those indicated by the picture header, regardless of whether these values are divisible by 16 or not. If the picture width or height is not divisible by 16, the additional area shall be generated by adding pixels to the resampled picture using the same fill mode as used in the resampling process. + +For the simplicity of description, the resampling vectors $\underline{r}^0$ , $\underline{r}^x$ , $\underline{r}^y$ and $\underline{r}^{xy}$ are defined as: + +$$\begin{aligned}\underline{r}^0 &= \underline{v}^{00} \\ \underline{r}^x &= \underline{v}^{H0} - \underline{v}^{00} \\ \underline{r}^y &= \underline{v}^{0V} - \underline{v}^{00} \\ \underline{r}^{xy} &= \underline{v}^{00} - \underline{v}^{H0} - \underline{v}^{0V} + \underline{v}^{HV}\end{aligned}$$ + +Using this definition, the equation for bilinear interpolation is rewritten as: + +$$\underline{v}(x, y) = \underline{r}^0 + \left(\frac{x}{H}\right)\underline{r}^x + \left(\frac{y}{V}\right)\underline{r}^y + \left(\frac{x}{H}\right)\left(\frac{y}{V}\right)\underline{r}^{xy}$$ + +For warping purposes, it is assumed that the coordinates of the upper left corner of the picture area are $(x, y) = (0, 0)$ and that each pixel has unit height and width, so that the centres of the pixels lie at the points $(x, y) = \left(i_L + \frac{1}{2}, j_L + \frac{1}{2}\right)$ for $i_L = 0, \dots, H - 1$ and $j_L = 0, \dots, V - 1$ , where the $L$ subscript indicates that $i_L$ and $j_L$ pertain to the luminance field. (As the pixel aspect ratio is usually constant or the conversion of the aspect ratio is performed by this resampling, there is no need to consider the actual pixel aspect ratio for these purposes.) Using this convention, the $x$ - and $y$ -displacements at the locations of interest in the luminance field of the reference picture are: + +$$v_x(i_L, j_L) = \frac{1}{HV} \left[ HVr_x^0 + \left(i_L + \frac{1}{2}\right)Vr_x^x + \left(j_L + \frac{1}{2}\right)Hr_x^y + \left(i_L + \frac{1}{2}\right)\left(j_L + \frac{1}{2}\right)r_x^{xy} \right]$$ + +$$v_y(i_L, j_L) = \frac{1}{HV} \left[ HVr_y^0 + \left(i_L + \frac{1}{2}\right) V_r^x + \left(j_L + \frac{1}{2}\right) H_r^y + \left(i_L + \frac{1}{2}\right) \left(j_L + \frac{1}{2}\right) r_y^{xy} \right]$$ + +Because all positions and phases must be computed relative to the centre of the upper-left corner pixel, which has the coordinate $(x, y) = \left(\frac{1}{2}, \frac{1}{2}\right)$ , the quantities of primary interest are: + +$$\begin{aligned} x_R(i_L, j_L) - \frac{1}{2} &= \left(i_L + \frac{1}{2}\right) + v_x(i_L, j_L) - \frac{1}{2} \\ &= \frac{1}{HV} \left[ HVr_x^0 + \left(i_L + \frac{1}{2}\right) (HV + V_r^x) + \left(j_L + \frac{1}{2}\right) H_r^x + \left(i_L + \frac{1}{2}\right) \left(j_L + \frac{1}{2}\right) r_x^{xy} \right] - \frac{1}{2} \\ y_R(i_L, j_L) - \frac{1}{2} &= \left(i_L + \frac{1}{2}\right) + v_y(i_L, j_L) - \frac{1}{2} \\ &= \frac{1}{HV} \left[ HVr_y^0 + \left(j_L + \frac{1}{2}\right) V_r^x + \left(j_L + \frac{1}{2}\right) (HV + H_r^y) + \left(i_L + \frac{1}{2}\right) \left(j_L + \frac{1}{2}\right) r_y^{xy} \right] - \frac{1}{2} \end{aligned}$$ + +Once a location has been determined in the prior decoded reference picture using an approximation of these equations, bilinear interpolation as specified later in this annex shall be used to generate a value for the resampled pixel. + +Each resampling vector can be decomposed into two components, with the first component describing the geometrical warping and the second component accounting for any difference in size between the predicted picture (horizontal size $H$ and vertical size $V$ ) and the reference picture (horizontal size $H_R$ and vertical size $V_R$ ). This decomposition is as follows: + +$$\begin{aligned} \underline{v}^{00} &= \underline{v}_{warp}^{00} + \underline{v}_{size}^{00} = \underline{v}_{warp}^{00} + (0, 0) \\ \underline{v}^{H0} &= \underline{v}_{warp}^{H0} + \underline{v}_{size}^{H0} = \underline{v}_{warp}^{H0} + (H_R - H, 0) \\ \underline{v}^{0V} &= \underline{v}_{warp}^{0V} + \underline{v}_{size}^{0V} = \underline{v}_{warp}^{0V} + (0, V_R - V) \\ \underline{v}^{HV} &= \underline{v}_{warp}^{HV} + \underline{v}_{size}^{HV} = \underline{v}_{warp}^{HV} + (H_R - H, V_R - V) \end{aligned}$$ + +## P.2 Syntax + +Whenever the reference picture resampling bit is set in the PLUSTPYPE field of the picture header, the RPRP field of the picture header includes parameters which control the Reference Picture Resampling process. This includes a two-bit Warping Displacement Accuracy (WDA) field, may include eight warping parameters or one-bit warping parameter refinements, and includes a fill mode, as described in this subclause. + +### P.2.1 Warping Displacement Accuracy (WDA) (2 bits) + +A two-bit warping displacement accuracy field WDA appears first in the RPRP field of the bitstream, and indicates the accuracy of the displacements for each pixel. A value of "10" indicates that the $x$ - and $y$ -displacements for each pixel are quantized to half-pixel accuracy. A value of "11" indicates that the displacements are quantized to $\frac{1}{16}$ -pixel accuracy. The use of other values is reserved. + +### P.2.2 Warping parameters (Variable length) + +When the Reference Picture Resampling parameters are sent for an INTER- or B-picture, or an Improved PB-frame, eight warping parameters are included in the picture header using the variable length code (VLC) shown in Table D.3. For an EP-picture using SNR scalability, the warping parameters of the lower layer are used and no warping parameters are transmitted. If the Reference Picture Resampling bit is set in the PLUSPTYPE field of the picture header for an EP-picture using spatial scalability, the warping parameters of the lower layer are refined to the accuracy needed for the current layer by multiplying the warping parameter for each up-sampled dimension (warping parameters with subscript $x$ and/or $y$ ) of the lower layer by two and adding the value of one additional bit that is sent in place of the associated warping parameter to define the least significant bit of the warping parameter. + +The eight integer warping parameters (or their one-bit refinements) are sent in the following order: + +$$w_x^0, w_y^0, w_x^x, w_y^x, w_x^y, w_y^y, w_x^{xy}, \text{ and } w_y^{xy}$$ + +When not a one-bit refinement, these parameters are sent in a similar manner as motion vector differences in the Unrestricted Motion Vector mode when PLUSPTYPE is present, using Table D.3 with no restriction on the range of the parameters (i.e., a range of $-4095$ to $+4095$ ). As when encoding motion vector difference pairs, an emulation prevention bit shall be added as needed after each pair of warping parameters is sent, such that if the all-zero codeword (the value $+1$ in half-pixel units) of Table D.3 is used for both warping parameters in the pair ( $w_x^0$ and $w_y^0$ , $w_x^x$ and $w_y^x$ , or $w_x^{xy}$ and $w_y^{xy}$ ) the pair of codewords is followed by a single bit equal to 1 to prevent start code emulation. + +These eight warping parameters are interpreted as picture corner displacements relative to the displacements that would be induced by removing the resizing component of the resampling vectors. The warping parameters are scaled to represent half-pixel offsets in the luminance field of the current picture, and the range for the values of these parameters is $-4095$ to $+4095$ . The warping parameters are defined using the resampling vectors by the relations: + +$$\begin{aligned} w_x^0 &= 2r_x^0 & w_y^0 &= 2r_y^0 \\ w_x^x &= 2(r_x^x - (H_R - H)) & w_y^x &= 2r_y^x \\ w_x^y &= 2r_x^y & w_y^y &= 2(r_y^y - (V_R - V)) \\ w_x^y &= 2r_x^y & w_y^{xy} &= 2r_y^{xy} \end{aligned}$$ + +### P.2.3 Fill Mode (FILL\_MODE) (2 bits) + +For an INTER- or B-picture or an Improved PB-frame, immediately following the VLC-coded warping parameters in the picture header are two bits which define the fill-mode action to be taken for the values of pixels for which the calculated location in the reference picture lies outside of the reference picture area. The meaning of these two bits is shown in Table P.1 and their location is shown in Figure P.2. For an EP-picture, the fill-mode action is the same as that for the reference layer, and the two fill-mode bits are not sent. + +**Table P.1/H.263 – Fill-mode bits/action** + +| Fill-mode bits | Fill action | +|----------------|--------------| +| 0 0 | color | +| 0 1 | black | +| 1 0 | gray | +| 1 1 | clip | + +If the fill mode is *clip*, the coordinates of locations in the prior reference picture are independently limited as in the Unrestricted Motion Vector mode so that pixel values outside of the prior reference picture area are estimated by extrapolation from the values of pixels at the image border. If the fill mode is *black*, luminance samples outside of the prior reference picture area are assigned a value of $Y = 16$ and chrominance samples are assigned a value of $C_B = C_R = 128$ . If the fill mode is *gray*, luminance and chrominance values are assigned a value of $Y = C_B = C_R = 128$ . If the fill mode is *color*, then additional fields are sent to specify a fill color, as described in the next subclause. + +### **P.2.4 Fill Color Specification (Y\_FILL, CB\_EPB, CB\_FILL, CR\_EPB, CR\_FILL) (26 bits)** + +If the fill mode is *color* and the picture is not an EP-picture, then the fill-mode bits are followed in the bitstream by three eight-bit integers, $Y\_fill$ , $C_B\_fill$ , and $C_R\_fill$ , which specify a fill color precisely. Between these three eight-bit integers are two emulation prevention bits (CB\_EPB and CR\_EPB) each of which is equal to 1. The format of this color specification, which is present only when the fill mode is *color*, is shown in Figure P.2. Each eight-bit integer field is sent using its natural representation. For an EP-picture, the fill-mode action (and fill color) is the same as that for the reference layer, and the fill color specification is not sent. + +| | | | | | | +|-----------|--------|---------------------|----------------------|---------------------|----------------------| +| FILL_MODE | Y_FILL | C B _EPB | C B _FILL | C R _EPB | C R _FILL | +|-----------|--------|---------------------|----------------------|---------------------|----------------------| + +**Figure P.2/H.263 – Format of fill mode and fill color specification data** + +## **P.3 Resampling algorithm** + +The method described in this clause shall be mathematically equal in result to that used to generate the samples of the resampled reference picture. Using the integer warping parameters $w_x^0, w_y^0, w_x^x, w_y^x, w_x^y, w_y^y, w_x^{xy},$ and $w_y^{xy}$ integer parameters + +$u_x^{00}, u_y^{00}, u_x^{H0}, u_y^{H0}, u_x^{0V}, u_y^{0V}, u_x^{HV},$ and $u_y^{HV}$ which denote the x- and y-displacements at the corners of the luminance field in $\frac{1}{32}$ -pixel accuracy (the actual displacements are obtained by dividing these values by 32) are defined as: + +$$\begin{aligned} + u_x^{00} &= 16w_x^0 & u_y^{00} &= 16w_y^0 \\ + u_x^{H0} &= 16(w_x^0 + w_x^x + 2(H_R - H)) & u_y^{H0} &= 16(w_y^0 + w_y^x) \\ + u_x^{0V} &= 16(w_x^0 + w_x^y) & u_y^{0V} &= 16(w_y^0 + w_y^y + 2(V_R - V)) \\ + u_x^{HV} &= 16(w_x^0 + w_x^x + w_x^y + w_x^{xy} + 2(H_R - H)) & u_y^{HV} &= 16(w_y^0 + w_y^x + w_y^y + w_y^{xy} + 2(V_R - V)) + \end{aligned}$$ + +Next, $H'$ and $V'$ , which denote the horizontal and vertical size of the *virtual frame*, are defined as the smallest integers that satisfy the following condition: + +$$H' \geq H, V' \geq V, H' = 2^m, V' = 2^n, m \text{ and } n \text{ are positive integers}$$ + +By applying bilinear extrapolation to the corner vectors of the luminance field, the integer parameters $u_x^{LT}$ , $u_y^{LT}$ , $u_x^{RT}$ , $u_y^{RT}$ , $u_x^{LB}$ , $u_y^{LB}$ , $u_x^{RB}$ , and $u_y^{RB}$ which denote the $x$ - and $y$ -displacements of the luminance field at the *virtual points* $(x, y) = (0, 0)$ , $(H', 0)$ , $(0, V')$ , and $(H', V')$ in $\frac{1}{32}$ -pixel accuracy (the actual displacements are obtained by dividing these values by 32) are defined as: + +$$\begin{aligned} u_x^{LT} &= u_x^{00} & u_y^{LT} &= u_y^{00} \\ u_x^{RT} &= \left( (H - H') u_x^{00} + H' u_x^{H0} \right) // H & u_y^{RT} &= \left( (H - H') u_y^{00} + H' u_y^{H0} \right) // H \\ u_x^{LB} &= \left( (V - V') u_x^{00} + V' u_x^{0V} \right) // V & u_y^{LB} &= \left( (V - V') u_y^{00} + V' u_y^{0V} \right) // V \\ u_x^{RB} &= \left( (V - V') \left( (H - H') u_x^{00} + H' u_x^{H0} \right) + V' \left( (H - H') u_x^{0V} + H' u_x^{HV} \right) \right) // (HV) \\ u_y^{RB} &= \left( (V - V') \left( (H - H') u_y^{00} + H' u_y^{H0} \right) + V' \left( (H - H') u_y^{0V} + H' u_y^{HV} \right) \right) // (HV) \end{aligned}$$ + +where " //" denotes integer division that rounds the quotient to the nearest integer, and rounds half integer values away from 0. + +In the remainder of this annex, it is assumed that the centres of the pixels lie at the points $(x, y) = \left( i + \frac{1}{2}, j + \frac{1}{2} \right)$ for both the luminance and chrominance fields. Integer parameters $i, j$ are defined as: + +- $i = 0, \dots, H - 1$ and $j = 0, \dots, V - 1$ for luminance; and +- $i = 0, \dots, \frac{H}{2} - 1$ and $j = 0, \dots, \frac{V}{2} - 1$ for chrominance. + +This implies that different coordinate systems are used for luminance and chrominance as shown in Figure P.3. Using the coordinate system for chrominance, the integer parameters $u_x^{LT}$ , $u_y^{LT}$ , $u_x^{RT}$ , $u_y^{RT}$ , $u_x^{LB}$ , $u_y^{LB}$ , $u_x^{RB}$ , and $u_y^{RB}$ defined above can also be regarded as the $x$ - and $y$ -displacements of the chrominance field at virtual points $(x, y) = (0, 0)$ , $(H'/2, 0)$ , $(0, V'/2)$ , and $(H'/2, V'/2)$ in $\frac{1}{64}$ -pixel accuracy (the actual displacements are obtained by dividing these values by 64). Using these parameters and an additional parameter $S$ , which is defined as 2 for luminance and as 1 for chrominance, the resampling algorithm for the luminance and chrominance fields are defined using common equations. + +![Figure P.3/H.263 – Coordinate systems for luminance and chrominance fields. The figure shows two coordinate systems. The left one is for Luminance, with x-axis from 0 to 5 and y-axis from 0 to 5. The right one is for Chrominance, with x-axis from 0 to 2 and y-axis from 0 to 2. Both plots show a grid of 'X' marks (Luminance samples) and 'O' marks (Chrominance samples) within a dashed rectangle representing the picture boundary. The legend indicates: X = Luminance sample, O = Chrominance sample, ----- = Picture boundary. A small code 'T1603080-97' is present near the bottom right of the Chrominance plot.](0ea4dd371cc3e49d6c56433444d4ccc3_img.jpg) + +Figure P.3/H.263 – Coordinate systems for luminance and chrominance fields. The figure shows two coordinate systems. The left one is for Luminance, with x-axis from 0 to 5 and y-axis from 0 to 5. The right one is for Chrominance, with x-axis from 0 to 2 and y-axis from 0 to 2. Both plots show a grid of 'X' marks (Luminance samples) and 'O' marks (Chrominance samples) within a dashed rectangle representing the picture boundary. The legend indicates: X = Luminance sample, O = Chrominance sample, ----- = Picture boundary. A small code 'T1603080-97' is present near the bottom right of the Chrominance plot. + +**Figure P.3/H.263 – Coordinate systems for luminance and chrominance fields** + +The integer parameters $u_x^L(j)$ , $u_y^L(j)$ , $u_x^R(j)$ , and $u_y^R(j)$ which denote the x- and y-displacements of the picture field at $(x, y) = (0, j + \frac{1}{2})$ and $(SH'/2, j + \frac{1}{2})$ in $\frac{s}{64}$ -pixel accuracy (the actual displacements are obtained by dividing these values by $64/S$ ) are defined using one dimensional linear interpolation as: + +$$u_x^L(j) = \left( (SV' - 2j - 1)u_x^{LT} + (2j + 1)u_x^{LB} \right) // (SV') \quad u_y^L(j) = \left( (SV' - 2j - 1)u_y^{LT} + (2j + 1)u_y^{LB} \right) // (SV')$$ + +$$u_x^R(j) = \left( (SV' - 2j - 1)u_x^{RT} + (2j + 1)u_x^{RB} \right) // (SV') \quad u_y^R(j) = \left( (SV' - 2j - 1)u_y^{RT} + (2j + 1)u_y^{RB} \right) // (SV')$$ + +where " //" denotes integer division that rounds the quotient to the nearest integer, and rounds half integer values away from 0. + +Finally, the parameters that specify the transformed position in the reference picture become: + +$$I_R(i, j) = Pi + \left( (SH' - 2i - 1)u_x^L(j) + (2i + 1)u_x^R(j) + 32H'/P \right) // (64H'/P)$$ + +$$J_R(i, j) = Pj + \left( (SH' - 2i - 1)u_y^L(j) + (2i + 1)u_y^R(j) + 32H'/P \right) // (64H'/P)$$ + +$$i_R(i, j) = I_R(i, j) // P \quad j_R(i, j) = J_R(i, j) // P$$ + +$$\emptyset_x = I_R(i, j) - (I_R(i, j) // P)P \quad \emptyset_y = J_R(i, j) - (J_R(i, j) // P)P$$ + +where: + +"///" integer division with truncation towards the negative infinity; + +"//" integer division (in this case resulting in no loss of accuracy); + +$P$ accuracy of $x$ - and $y$ -displacements ( $P = 2$ when WDA = "10" and $P = 16$ when WDA = "11" or is absent, see P.2.1 for the definition of WDA); + +$\left( \frac{I_R(i,j)}{P} + \frac{1}{2}, \frac{J_R(i,j)}{P} + \frac{1}{2} \right)$ $(x, y)$ location of the transformed position (both $I_R(i,j)$ and $J_R(i,j)$ are integers); + +$\left( i_R(i,j) + \frac{1}{2}, j_R(i,j) + \frac{1}{2} \right)$ $(x, y)$ location of the sampling point near the transformed position (both $i_R(i,j)$ and $j_R(i,j)$ are integers); + +$(\emptyset_x, \emptyset_y)$ bilinear interpolation coefficients of the transformed position (both $\emptyset_x$ and $\emptyset_y$ are integers). + +The computation of this equation can be simplified by replacing the divisions by shift operations, since $64H'/P = 2^{m+2}$ when $P = 16$ and $64H'/P = 2^{m+5}$ when $P = 2$ . + +Using these parameters, the sample value, $E_P(i, j)$ , of the pixel located at $(x, y) = \left( i + \frac{1}{2}, j + \frac{1}{2} \right)$ in the resampled picture is obtained using bilinear interpolation by: + +$$E_P(i, j) = \left( (P - \emptyset_y) \left( (P - \emptyset_x) E_R(i_R, j_R) + \emptyset_x E_R(i_R + 1, j_R) \right) + \emptyset_y \left( (P - \emptyset_x) E_R(i_R, j_R + 1) + \emptyset_x E_R(i_R + 1, j_R + 1) \right) + P^2 / 2 - 1 + RCRPR \right) / P^2$$ + +where "/" denotes division by truncation. $i_R$ and $j_R$ are simplified notations for $i_R(i, j)$ and $j_R(i, j)$ , and $E_R(i_R, j_R)$ denotes the sample value of the pixel located at $(x, y) = \left( i_R + \frac{1}{2}, j_R + \frac{1}{2} \right)$ in the reference picture after extrapolation using the proper fill mode if necessary. The value of parameter RCRPR is defined as follows: + +- For a B-picture (or the B-part of an Improved PB-frame) which has a P-picture as its temporally subsequent anchor picture, RCRPR is equal to the rounding type (RTYPE) bit in MPPTYPE (see 5.1.4.3) of this temporally subsequent P-picture. This implies that for Improved PB-frames, RCRPR has the same value for the P-part and the B-part. +- For other types of pictures, RCRPR is equal to the RTYPE bit of the current picture. + +## P.4 Example of implementation + +In this clause, an implementation example of the algorithm described in the previous clause is provided as pseudo-code. + +### P.4.1 Displacements of virtual points + +When a large picture is coded, a straightforward implementation of the equation for obtaining parameters $u_x^{RB}$ and $u_y^{RB}$ shown in P.3 may necessitate the usage of variables requiring more than 32 bits for their binary representation. For systems which cannot easily use 64-bit integer or floating point registers, an example of an algorithm which does not require variables with more than 32 bits for the calculation of $u_x^{RB}$ and $u_y^{RB}$ is shown below. + +Since $H$ , $V$ , $H'$ , and $V'$ are divisible by 4, the definition of $u_x^{RB}$ can be rewritten as: + +$$u_x^{RB} = \left( (V_Q - V_{Q'}) \left( (H_Q - H_{Q'}) u_x^{00} + H_{Q'} u_x^{H0} \right) + V_{Q'} \left( (H_Q - H_{Q'}) u_x^{0V} + H_{Q'} u_x^{HV} \right) \right) // A$$ + +where $H_Q = H/4$ , $V_Q = V/4$ , $H_{Q'} = H'/4$ , $V_{Q'} = V'/4$ , $A = H_Q V_Q$ , and "///" denotes integer division that rounds the quotient to the nearest integer, and rounds half integer values away from 0. Next, parameters $T_T$ and $T_B$ are defined as: + +$$T_T = (H_Q - H_{Q'}) u_x^{00} + H_{Q'} u_x^{H0}$$ + +$$T_B = (H_Q - H_{Q'}) u_x^{0V} + H_{Q'} u_x^{HV}$$ + +for simplicity of description. Using operator "///" which denotes integer division with truncation towards the negative infinity, and operator "%" which is defined as $a \% b = a - (a /// b) b$ , the value of $u_x^{RB}$ can be obtained via the following pseudo-code: + +``` +q = (V_Q - V_{Q'}) * (T_T /// A) + V_{Q'} * (T_B /// A) + ((V_Q - V_{Q'}) * (T_T % A) + V_{Q'} * (T_B % A)) /// A; +r = ((V_Q - V_{Q'}) * (T_T % A) + V_{Q'} * (T_B % A)) % A; +if (q < 0) + u_x^{RB} = q + (r + (A - 1) / 2) / A; +else + u_x^{RB} = q + (r + A / 2) / A; +``` + +The value of $u_y^{RB}$ can also be calculated using this algorithm. + +### P.4.2 Resampling algorithm + +To simplify the description of the algorithm, a function `prior_sample` is defined. Its purpose is to generate a pixel value for any integer location $(i_p, j_p)$ relative to the prior reference picture sampling grid: + +``` +clip(x_min, x, x_max) { + if (x < x_min) { + return x_min; + } else if (x > x_max) { + return x_max; + } else { + return x; + } +} + +prior_sample(i_p, j_p) { + if (FILL_MODE = clip) { + i_c = clip(0, i_p, S*H_R / 2 - 1); + j_c = clip(0, j_p, S*V_R / 2 - 1); + return prior_ref[i_c, j_c]; + } else { + if ((i_p < 0) OR (i_p > S*H_R / 2 - 1) or (j_p < 0) OR (j_p > S*V_R / 2 - 1) { + return fill_value; + } else { + return prior_ref[i_p, j_p]; + } + } +} +``` + +In the pseudo-code, `prior_ref[i, j]` indicates the sample in column $i$ and row $j$ in the temporally previous reference picture. + +Next, a filter function that implements the bilinear interpolation described in P.3 is defined. It is assumed that all arguments of the following function are integers and that the bilinear interpolation coefficients, $\phi_x$ and $\phi_y$ , are quantized in the range 0, ..., $P-1$ (inclusive). + +``` +filter( $x_0, y_0, \phi_x, \phi_y$ ) { + return $[(P - \phi_y) \cdot ((P - \phi_x) \cdot \text{prior\_sample}(x_0, y_0) + \phi_x \cdot \text{prior\_sample}(x_0 + 1, y_0)) +$ + $\phi_y \cdot ((P - \phi_x) \cdot \text{prior\_sample}(x_0, y_0 + 1) + \phi_x \cdot \text{prior\_sample}(x_0 + 1, y_0 + 1)) +$ + $P^2 / 2 - 1 + \text{RCRPRJ} / P^2;$ +} +``` + +Finally, the method for warping the reference picture to generate a prediction for the current picture can be specified in terms of these functions. The pixels of the prediction picture can be generated in a raster scan order. It is assumed that the values $u_x^L(j)$ , $u_y^L(j)$ , $u_x^R(j)$ , and $u_y^R(j)$ are already calculated and loaded into variables $u_x^L$ , $u_y^L$ , $u_x^R$ , and $u_y^R$ . Defining parameter $D$ as $D = 64H'/P$ and noting that $H' = 2^m$ , the sample values of the pixels in the $j$ th line of the resampled field (the topmost line is defined as the 0th line) is obtained by the following pseudo-code: + +``` + $a_x^i = D * P + 2 * (u_x^R - u_x^L);$ + $a_y^i = 2 * (u_y^R - u_y^L);$ + $a_x = u_x^L * S * 2^m + (u_x^R - u_x^L); + D / 2;$ + $a_y = j * D * P + u_y^L * S * 2^m + (u_y^R - u_y^L); + D / 2;$ +for ( $i = 0; i < S * H / 2; i++$ ) { + $I_R = a_x \text{ /// } D;$ + $J_R = a_y \text{ /// } D;$ + $i_R = I_R \text{ /// } P;$ + $j_R = J_R \text{ /// } P;$ + $\phi_x = I_R - (i_R * P);$ + $\phi_y = J_R - (j_R * P);$ + $\text{new\_ref}[i, j] = \text{filter}(i_R, j_R, \phi_x, \phi_y);$ + $a_x += a_x^i;$ + $a_y += a_y^i;$ +} +``` + +where all the variables used in this code are integer variables and $\text{new\_ref}[i, j]$ indicates the sample generated for column $i$ and row $j$ in the resampled reference picture. According to the definition of the parameters, all the divisions in this code can be replaced by binary shift operations. For example, when $P = 16$ : + +``` + $I_R = a_x \text{ /// } D;$ + $J_R = a_y \text{ /// } D;$ + $i_R = I_R \text{ /// } P;$ + $j_R = J_R \text{ /// } P;$ + $\phi_x = I_R - (i_R * P);$ + $\phi_y = J_R - (j_R * P);$ +``` + +can be rewritten, assuming that $a_x$ , $a_y$ , $I_R$ , and $J_R$ are binary-coded integer variables in two's complement representation, as: + +$$\begin{aligned} I_R &= a_x \gg (m+2); \\ J_R &= a_y \gg (m+2); \\ i_R &= I_R \gg 4; \\ j_R &= J_R \gg 4; \\ \emptyset_x &= I_R \& 15; \\ \emptyset_y &= J_R \& 15; \end{aligned}$$ + +where " $\gg N_{shift}$ " denotes a right arithmetic binary shift by $N_{shift}$ bits ( $N_{shift}$ is a positive integer), and "&" denotes a bit-wise AND operation. + +## P.5 Factor-of-4 resampling + +Factor-of-4 resampling, which converts both the horizontal and vertical size of the picture by a factor of 2 or $\frac{1}{2}$ , is a special case of the resampling algorithm described in P.3. The simplified description of the resampling algorithm for this special case is provided in this clause. + +The value of the parameter RCRPR used in Figures P.4 to P.6 is determined by the Rounding Type (RTYPE) bit in MPPTYPE (see 5.1.4.3) as described in P.3. Additionally, "/" in the figures indicates division by truncation. + +### P.5.1 Factor-of-4 upsampling + +The pixel value interpolation method used in factor-of-4 upsampling for internal pixels are shown in Figure P.4. By assuming the existence of pixels outside the picture according to the selected fill mode (see P.2.3 and P.2.4), the same interpolation method is applied for boundary pixels. The interpolation method for boundary pixels when *clip* is selected as the fill mode is shown in Figure P.5. Since precise factor-of-4 upsampling requires x- and y-displacements with at least $\frac{1}{4}$ -pixel accuracy, the Warping Displacement Accuracy (WDA) field specified in P.2.1 must be set to "11" or the resampling must be implicitly invoked in order to use this upsampling method. + +![Diagram showing pixel positions for factor-of-4 upsampling. It features a 2x2 grid of reference pixels (A, B, C, D) in gray circles and four upsampled pixels (a, b, c, d) in white circles. Formulas for a, b, c, and d are provided on the right, each involving a weighted sum of reference pixels and a rounding constant (RCRPR). Vertical ellipsis dots indicate additional pixels.](79403f771ea4876ca26ecee2f288b1d1_img.jpg) + +$a = (9A + 3B + 3C + D + 7 + \text{RCRPR}) / 16$ + $b = (3A + 9B + C + 3D + 7 + \text{RCRPR}) / 16$ + $c = (3A + B + 9C + 3D + 7 + \text{RCRPR}) / 16$ + $d = (A + 3B + 3C + 9D + 7 + \text{RCRPR}) / 16$ + +⋮ + +Diagram showing pixel positions for factor-of-4 upsampling. It features a 2x2 grid of reference pixels (A, B, C, D) in gray circles and four upsampled pixels (a, b, c, d) in white circles. Formulas for a, b, c, and d are provided on the right, each involving a weighted sum of reference pixels and a rounding constant (RCRPR). Vertical ellipsis dots indicate additional pixels. + +T1603090-97 + +- Image: Gray circle icon + + Pixel positions of the reference picture +- Image: White circle icon + + Pixel positions of the upsampled predicted picture + +**Figure P.4/H.263 – Factor-of-4 upsampling for pixels inside the picture** + +![Diagram illustrating factor-of-4 upsampling for pixels at the picture boundary. It shows a grid of circles representing pixel positions. Gray circles are labeled A, B, C, and D, representing reference picture pixels. White circles are labeled a, b, c, d, e, and others, representing upsampled predicted picture pixels. Formulas for a, b, c, d, and e are provided, showing they are averages of reference pixels and a constant RCRPR. A legend at the bottom identifies gray circles as 'Pixel positions of the reference picture' and white circles as 'Pixel positions of the upsampled predicted picture'.](143c8ee1010bf7669caabfbed815df1b_img.jpg) + +Picture boundary + +a = A + b = (3A + B + 1 + RCRPR) / 4 + c = (A + 3B + 1 + RCRPR) / 4 + d = (3A + C + 1 + RCRPR) / 4 + e = (A + 3C + 1 + RCRPR) / 4 + ⋮ + +Picture boundary + +T1603100-97 + +● Pixel positions of the reference picture + +○ Pixel positions of the upsampled predicted picture + +Diagram illustrating factor-of-4 upsampling for pixels at the picture boundary. It shows a grid of circles representing pixel positions. Gray circles are labeled A, B, C, and D, representing reference picture pixels. White circles are labeled a, b, c, d, e, and others, representing upsampled predicted picture pixels. Formulas for a, b, c, d, and e are provided, showing they are averages of reference pixels and a constant RCRPR. A legend at the bottom identifies gray circles as 'Pixel positions of the reference picture' and white circles as 'Pixel positions of the upsampled predicted picture'. + +**Figure P.5/H.263 – Factor-of-4 upsampling for pixels at the picture boundary (fill mode = clip)** + +### P.5.2 Factor-of-4 downsampling + +The pixel value interpolation method for factor-of-4 downsampling is shown in Figure P.6. Since x- and y-displacements with $\frac{1}{2}$ -pixel accuracy is sufficient for precise factor-of-4 downsampling, both "10" and "11" are allowed as the value of the displacement accuracy (WDA) field (if present) specified in P.2.1. + +![Diagram illustrating factor-of-4 downsampling. It shows a 2x2 block of reference pixels (A, B, C, D) and a corresponding single pixel (a) in the downsampled predicted picture. The formula for 'a' is given as a = (A + B + C + D + 1 + RCRPR) / 4. A legend at the bottom indicates that gray circles represent pixel positions of the reference picture and white circles represent pixel positions of the downsampled predicted picture.](e2245b4865907ad1259fd155f4beb6cf_img.jpg) + +Diagram illustrating factor-of-4 downsampling. The diagram shows a 2x2 block of reference pixels (A, B, C, D) and a corresponding single pixel (a) in the downsampled predicted picture. The formula for 'a' is given as: + +$$a = (A + B + C + D + 1 + \text{RCRPR}) / 4$$ + +Below the formula, there are three vertical dots indicating that the process is repeated for multiple blocks. The diagram is labeled T1603110-97. + +Legend: + +- Gray circle: Pixel positions of reference picture +- White circle: Pixel positions of the downsampled predicted picture + +Diagram illustrating factor-of-4 downsampling. It shows a 2x2 block of reference pixels (A, B, C, D) and a corresponding single pixel (a) in the downsampled predicted picture. The formula for 'a' is given as a = (A + B + C + D + 1 + RCRPR) / 4. A legend at the bottom indicates that gray circles represent pixel positions of the reference picture and white circles represent pixel positions of the downsampled predicted picture. + +**Figure P.6/H.263 – Factor-of-4 downsampling** + +# Annex Q + +# Reduced-Resolution Update mode + +## Q.1 Introduction + +This annex describes an optional Reduced-Resolution Update mode of this Recommendation. The capability of this mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode is indicated in the PLUSPTYPE field of the picture header. + +The Reduced-Resolution Update mode is expected to be used when encoding a highly active scene, and provides the opportunity to increase the coding picture rate while maintaining sufficient subjective quality. This mode allows the encoder to send update information for a picture that is encoded at a reduced resolution, while preserving the detail in a higher resolution reference image to create a final image at the higher resolution. + +The syntax of the bitstream in this mode is identical to the syntax for coding without the mode, but the semantics, or interpretation of the bitstream is somewhat different. In this mode, the portion of the picture covered by a macroblock is twice as wide and twice as high. Thus, there is approximately one-quarter the number of macroblocks as there would be without this mode. Motion vector data also refers to blocks of twice the normal height and width, or $32 \times 32$ and $16 \times 16$ instead of the normal $16 \times 16$ and $8 \times 8$ . On the other hand, the DCT or texture data should be thought of as describing $8 \times 8$ blocks on a reduced-resolution version of the picture. To produce the final picture, the texture data is decoded at a reduced resolution and then up-sampled to the full resolution of the picture. After upsampling, the full resolution texture image is added to the (already full resolution) motion compensated image to create the image for display and further reference. + +In this mode, a picture which has the horizontal size $H$ and vertical size $V$ as indicated in the picture header is created as a final image for display. + +In this mode, a referenced picture used for prediction and created for further decoding has a horizontal size $H_R$ and a vertical size $V_R$ which are the same as in the default mode as defined in 4.1. That is, the $H_R$ and $V_R$ are: + +$$H_R = ((H + 15) / 16) * 16$$ + +$$V_R = ((V + 15) / 16) * 16$$ + +where $H$ and $V$ are the horizontal size and the vertical size as indicated in the picture header and "/" is defined as division by truncation. + +Then in this annex, the texture is coded at a reduced resolution with height and width of $H_C$ and $V_C$ where: + +$$H_C = ((H_R + 31) / 32) * 32$$ + +$$V_C = ((V_R + 31) / 32) * 32$$ + +and "/" is defined as division by truncation. + +If $H_C$ and $H_R$ , or $V_C$ and $V_R$ are not identical to each other, such as in the QCIF format, an extension of the referenced picture is performed, and the picture is decoded in the same manner as if the width and height are $H_C$ and $V_C$ . Then the resulting picture which is tiled by $32 * 32$ macroblocks is cropped at the right and the bottom to the width $H_R$ and height $V_R$ , and this cropped picture is stored as a reference picture for further decoding. + +If both $H$ and $V$ are the same as those of a resulting picture having the width $H_C$ and the height $V_C$ , this resulting picture is used for display. Otherwise, this resulting picture is further cropped to the size $H * V$ , and the cropped picture here is used for display purpose only. + +If the Temporal, SNR, and Spatial Scalability mode (Annex O) or Reference Picture Resampling mode (Annex P) is also used with this option, the source format of the current picture might be different from that of the reference picture. In this case, the resampling of the reference picture shall be performed before decoding. + +NOTE – This mode can be used with the Reference Picture Selection mode (see Annex N) without modification, since the reference picture (after possible resampling by the Reference Picture Resampling mode) has the same size as indicated in the current picture header when this option is used. + +## Q.2 Decoding procedure + +Figure Q.1 shows the block diagram of the block decoding in the Reduced-Resolution Update mode. + +![Block diagram of block decoding in Reduced-Resolution Update mode. The diagram shows two parallel processing paths starting from a 'Bitstream' input. The top path involves 'Block layer decoding' to produce an '8 * 8 Coefficients block', followed by 'Coefficients decoding' to produce the 'Result of inverse transform' (represented by an 8x8 grid), and then 'Up-sampling' to create a '16 * 16 Reconstructed prediction error block' (represented by a 16x16 grid). The bottom path involves 'Macroblock layer decoding' to produce a 'Pseudo-vector', which is then 'Scaling-up' to a 'Reconstructed vector', followed by 'Motion compensation' to create a '16 * 16 prediction block' (represented by a 16x16 grid). The two 16 * 16 blocks are then added together (indicated by a circle with a plus sign) to produce the final '16 * 16 reconstructed block'. A label 'T1603120-97' is present in the bottom right corner of the diagram area.](a83c022a6dac411615bcc38b7cd0d573_img.jpg) + +Block diagram of block decoding in Reduced-Resolution Update mode. The diagram shows two parallel processing paths starting from a 'Bitstream' input. The top path involves 'Block layer decoding' to produce an '8 \* 8 Coefficients block', followed by 'Coefficients decoding' to produce the 'Result of inverse transform' (represented by an 8x8 grid), and then 'Up-sampling' to create a '16 \* 16 Reconstructed prediction error block' (represented by a 16x16 grid). The bottom path involves 'Macroblock layer decoding' to produce a 'Pseudo-vector', which is then 'Scaling-up' to a 'Reconstructed vector', followed by 'Motion compensation' to create a '16 \* 16 prediction block' (represented by a 16x16 grid). The two 16 \* 16 blocks are then added together (indicated by a circle with a plus sign) to produce the final '16 \* 16 reconstructed block'. A label 'T1603120-97' is present in the bottom right corner of the diagram area. + +**Figure Q.1/H.263 – Block diagram of block decoding in Reduced-Resolution Update mode** + +The decoding procedure is given in the following subclauses: + +### Q.2.1 Reference preparation + +In some cases, the available reference picture has different size from $H_C$ and $V_C$ . Then, the reference picture shall be converted before decoding procedure according to Q.2.1.1 or Q.2.1.2. + +#### Q.2.1.1 Reference Picture Resampling + +If the Temporal, SNR, and Spatial Scalability mode (Annex O) or Reference Picture Resampling mode (Annex P) is also used with this option, the source format of the current picture might be different from that of the reference picture. In this case, the resampling of the reference picture according to each annex shall be performed first. + +#### Q.2.1.2 Extension of Reference Picture + +If $H_R$ or $V_R$ is not divisible by 32, such as with the QCIF format, the reference picture is extended. The detailed procedure for this extension is defined in Q.3. + +### Q.2.2 Macroblock layer decoding + +Decoding can be thought of as operating on "enlarged" blocks of size $32 \times 32$ in luminance and $16 \times 16$ in chrominance. The texture and motion data for each enlarged block is decoded to create a $32 \times 32$ motion block and a $32 \times 32$ texture block, as described in Q.2.2.1 and Q.2.2.2 respectively. These motion and texture blocks are then added as described in Q.2.2.3. + +#### Q.2.2.1 Motion compensation + +First, each component of the macroblock motion vector (or four macroblock motion vectors) is formed from MVD (and possibly $MVD_{2-4}$ ). If in Improved PB-Frames mode, $MV_F$ and $MV_B$ for B-Picture is also formed from MVDB. The detailed procedure for this motion vector formation is defined in Q.4. If the current picture mode is a B-picture or EP-picture, the motion vector for forward and backward are also obtained according to Q.4. + +The motion vector for the two chrominance blocks of the macroblock is obtained from the macroblock motion vector according to 6.1.1. If either the Advanced Prediction mode or the Deblocking Filter mode is in use and thus four motion vectors are defined for the macroblock, the motion vector for both chrominance blocks is obtained from the four motion vectors according to F.2. If in the Improved PB-frames mode, the creation of the chrominance vector is specified in Annex M. If a B-picture or EP-picture is used, the creation of the chrominance vector is specified in Annex O. + +Then, a prediction is formed from the motion vector for an INTER macroblock. Four $16 \times 16$ luminance prediction blocks are obtained from the macroblock motion vector, and two $16 \times 16$ chrominance prediction blocks are obtained from the chrominance motion vector. For interpolation for subpixel prediction, refer to 6.1.2. If Advanced Prediction mode is also used, an enlarged overlapped motion compensation is performed to obtain four $16 \times 16$ luminance prediction blocks using enlarged weighting matrices, for which a detailed procedure is defined in Q.5. If the current picture mode is an Improved PB-frame, B-picture, or EP-picture, the prediction is obtained according to the other relevant annexes, except that the size of the predicted blocks is $16 \times 16$ instead of $8 \times 8$ . + +#### Q.2.2.2 Texture decoding + +First, the bitstream of the block layer is decoded according to 5.4. Then, coefficients are decoded and the $8 \times 8$ reduced-resolution reconstructed prediction error blocks are obtained as the result of inverse transform according to 6.2. + +Then the $16 \times 16$ reconstructed prediction error blocks are obtained by upsampling the $8 \times 8$ reduced-resolution reconstructed prediction error blocks. For the creation of the edge pixels in each $16 \times 16$ reconstructed prediction error block, only the pixels which belong to the corresponding block are used. The detailed procedure is defined in Q.6. + +#### Q.2.2.3 Reconstruction of block + +For each luminance and chrominance block, a summation of the prediction and prediction error is performed. The procedure is identical to 6.3.1, except that the size of blocks is $16 \times 16$ instead of $8 \times 8$ . Then the clipping is performed according to the 6.3.2. + +Then, a block boundary filter is applied to the boundary pixels of the $16 \times 16$ reconstructed blocks. The detailed procedure is described in Q.7. + +### Q.2.3 Picture store + +If both $H_R$ and $V_R$ are divisible by 32, such as with the CIF format, the resulting picture reconstructed as described in Q.2.2 is stored as a reference picture as it is for further decoding. Otherwise, such as the QCIF format, the reconstructed picture which is just covered with + +$32 \times 32$ macroblocks is cropped at the right and the bottom to the width $H_R$ and height $V_R$ , and this cropped picture is stored as a reference picture for further decoding. + +### Q.2.4 Display + +If both $H$ and $V$ are the same as $H_C$ and $V_C$ , the resulting picture in Q.2.2 is used for display purposes as it is. Otherwise, this resulting picture is further cropped to the size $H \times V$ , and the cropped picture is used for display purpose only. + +## Q.3 Extension of referenced picture + +If $H_R$ or $V_R$ is not divisible by 32, such as with the QCIF format, the extension of the referenced picture is performed before decoding macroblock/block layer. The width and the height of the extended reference picture for luminance are the next larger size that would be divisible by 32, and those for chrominance are the next larger size that would be divisible by 16. + +NOTE – The width and height of the referenced picture in the default mode are always extended to be divisible by 16 even if the picture format has a width or height that is not divisible by 16, because the picture shall be decoded as if the width or height had the next larger size that would be divisible by 16. See 4.1. + +If neither Unrestricted Motion Vector mode, Advanced Prediction mode nor Deblocking Filter mode is used with this option, the extended pixels can be arbitrary values, because the extended pixels will be never used as a reference pixels of the decoded picture to be reconstructed and displayed. + +If either Unrestricted Motion Vector mode, Advanced Prediction mode or Deblocking Filter mode is also used with this option, the extension of the referenced picture is performed by duplicating the edge pixel of the referenced picture, in order to ensure the decoding when motion vectors point outside the right and bottom edge of the picture. + +For example, if the Reduced-Resolution Update mode is used for a QCIF, the width of the referenced picture is 176 and the height is 144, which are not divisible by 32. In order to cover a QCIF picture with $32 \times 32$ -sized macroblocks, the number of macroblock row should be 6, and the number of macroblock column should be 5. Therefore, the width of the extended referenced picture is 192 and the height is 160. + +![Diagram illustrating the extension of a referenced picture for QCIF picture size. The original 'referenced picture' has dimensions 176 (width) and 144 (height). The 'Extended referenced picture' has dimensions 192 (width) and 160 (height). The extension is calculated as 192 = 32 * 6 and 160 = 32 * 5. The diagram shows the original picture as a grid of 5 columns and 4.5 rows of 32x32 macroblocks, with the top-left corner of the 5th column and the first 4 rows of the 6th column shaded to represent the extension. A label 'T1603130-97' is present near the bottom right of the grid.](4fed8a9f7064898f635d0f83b0a1ae61_img.jpg) + +Diagram illustrating the extension of a referenced picture for QCIF picture size. The original 'referenced picture' has dimensions 176 (width) and 144 (height). The 'Extended referenced picture' has dimensions 192 (width) and 160 (height). The extension is calculated as $192 = 32 * 6$ and $160 = 32 * 5$ . The diagram shows the original picture as a grid of 5 columns and 4.5 rows of $32 \times 32$ macroblocks, with the top-left corner of the 5th column and the first 4 rows of the 6th column shaded to represent the extension. A label 'T1603130-97' is present near the bottom right of the grid. + +Diagram illustrating the extension of a referenced picture for QCIF picture size. The original 'referenced picture' has dimensions 176 (width) and 144 (height). The 'Extended referenced picture' has dimensions 192 (width) and 160 (height). The extension is calculated as 192 = 32 \* 6 and 160 = 32 \* 5. The diagram shows the original picture as a grid of 5 columns and 4.5 rows of 32x32 macroblocks, with the top-left corner of the 5th column and the first 4 rows of the 6th column shaded to represent the extension. A label 'T1603130-97' is present near the bottom right of the grid. + +Figure Q.2/H.263 – Extension of referenced picture for QCIF picture size + +The extension of the referenced picture in QCIF is illustrated in Figure Q.2. The extended referenced picture for luminance is given by the following formula: + +$$R_{RRU}(x, y) = R(x', y')$$ + +where: + +$x, y$ = spatial coordinates of the extended referenced picture in the pixel domain + +$x', y'$ = spatial coordinates of the referenced picture in the pixel domain + +$R_{RRU}(x, y)$ = pixel value of the extended referenced picture at $(x, y)$ + +$R(x', y')$ = pixel value of the referenced picture at $(x', y')$ + +$$x' = \begin{cases} 175 & \text{if } x > 175 \text{ and } x < 192 \\ x & \text{otherwise} \end{cases}$$ + +$$y' = \begin{cases} 143 & \text{if } y > 143 \text{ and } y < 160 \\ y & \text{otherwise} \end{cases}$$ + +The referenced pictures for chrominance is also extended in the same manner. + +## Q.4 Reconstruction of motion vectors + +In Reduced-Resolution Update mode, the motion vector range is enlarged to approximately double size in both the horizontal and vertical directions. In order to realize an enlarged range using the VLC for MVD defined in Table 14, each vector component is restricted to be only half-pel or zero value. Therefore the range of each motion vector component is $[-31.5, 30.5]$ in the default Reduced-Resolution Update mode. If the Unrestricted Motion Vector mode is used, the vector range $[-\text{limit}, \text{limit}]$ as defined in D.2 applies to the pseudo-motion vectors and translates into $[-(2 * \text{limit}-0.5), 2 * \text{limit}-1.5]$ for the motion vectors. For CIF this means that the pseudo-motion vector range is $[-32, 31.5]$ and the motion vector range is $[-63.5, 62.5]$ . If the UUI field is set to "01", the motion vectors are unlimited. However, the motion vectors (not just the pseudo-motion vectors) are always limited to point not more than 15 pixels outside the coded area as described in D.1.1. Figure Q.3 illustrates the possible positions of macroblock motion vector or four motion vector predictions around the $(0, 0)$ vector value. The dashed lines indicate the integer coordinates. + +![Figure Q.3/H.263 – Reconstruction of motion vector. The diagram shows a grid of 11x11 points. A horizontal and vertical axis intersect at the center point, which is labeled (0, 0). The axes have arrows at their ends. The grid lines are dashed, and the points are solid black circles.](011605f44dd7f77a182efb20ed953a2e_img.jpg) + +Figure Q.3/H.263 – Reconstruction of motion vector. The diagram shows a grid of 11x11 points. A horizontal and vertical axis intersect at the center point, which is labeled (0, 0). The axes have arrows at their ends. The grid lines are dashed, and the points are solid black circles. + +T1603140-97 + +**Figure Q.3/H.263 – Reconstruction of motion vector** + +For the macroblock using differential motion vectors in a B-picture, the motion vector for forward and backward prediction are obtained independently. In the Reduced-Resolution Update mode, the motion vector component $MV_C$ for a luminance block is reconstructed from $MVD$ and $MVD_{2-4}$ as follows: + +- 1) Pseudo-prediction vector component **pseudo- $P_C$** is created from the prediction vector component **$P_C$** . + +$$\text{pseudo-}P_C = 0 \quad \text{if } P_C = 0$$ + +$$\text{pseudo-}P_C = \text{sign}(P_C) * (|P_C| + 0.5) / 2.0 \quad \text{if } P_C \neq 0$$ + +"/" indicates floating-point division (without loss of accuracy). The prediction vector component $P_C$ is defined as the median value of the vector components $MV1$ , $MV2$ and $MV3$ as defined in 6.1.1 and F.2. + +- 2) Pseudo-macroblock vector component **pseudo- $MV_C$** is obtained by adding the motion vector differences $MVD$ (and $MVD_{2-4}$ ) from Table 14 to the **pseudo- $P_C$** . + +In the default Reduced-Resolution Update mode, the value of **pseudo- $MV_C$** is restricted to the range $[-16, 15.5]$ . Only one of the pair will yield a **pseudo- $MV_C$** falling within the permitted range. The procedure is performed in a similar way as defined in 6.1.1. + +If the Unrestricted Motion Vector mode is also used with the Reduced-Resolution Update mode, **pseudo- $MV_C$** is obtained by adding the motion vector differences $MVD$ (and $MVD_{2-4}$ ) from Table D.3. + +If four motion vectors are present, the procedure is performed in a similar way as defined in F.2. + +- 3) Motion vector component $MV_C$ is obtained from pseudo- $MV_C$ in the following formula: + +$$MV_C = 0 \qquad \qquad \qquad \text{if pseudo-}MV_C = 0$$ + +$$MV_C = \text{sign}(\text{pseudo-}MV_C) * (2.0 * |\text{pseudo-}MV_C| - 0.5) \qquad \text{if pseudo-}MV_C \neq 0$$ + +As a result, each vector component is restricted to have a half-integer or zero value, and the range of each motion vector component is enlarged to approximately twice the pseudo-motion vector range. + +- 4) If the current picture mode is an Improved PB-frame, or when the MBTYPE indicates the direct mode in a B-picture, the motion vector components $MV_F$ and/or $MV_B$ for forward and backward prediction are created. + +First, pseudo-motion vector components **pseudo- $MV_F$** and/or **pseudo- $MV_B$** are calculated based on the rules for the prediction modes defined in Annexes O or M. + +In the case of the Bidirectional prediction in the Improved PB-frames mode (see M.2.1) or when the MBTYPE indicates the direct mode in a B-picture (see O.5.2), pseudo- $MV_F$ and pseudo- $MV_B$ are calculated from **pseudo- $MV_D$** and **pseudo- $MV_C$** assuming that pseudo- $MV_D$ is zero and pseudo- $MV_C$ is $MV$ , as defined in Annexes G and M. + +In the case of forward prediction in the Improved PB-frames mode (see M.2.2), **pseudo- $MV_{DB}$** is obtained by decoding the variable length code MVDB according to Table 12. Then, pseudo- $MV_F$ is obtained by adding the pseudo- $MV_{DB}$ to the **pseudo-Predictor**. In order to form the pseudo-Predictor, the predictor obtained according to the procedure defined in M.2.2 is converted to the pseudo-Predictor vector according to the formula defined in item 1 of this clause. + +In the case of backward prediction in the Improved PB-frames mode (see M.2.3), pseudo- $MV_B$ is set to zero. + +Then, the motion vectors $MV_F$ and/or $MV_B$ for forward and backward prediction are obtained from pseudo- $MV_F$ and/or pseudo- $MV_B$ according to the formula defined in item 3 of this clause. + +## Q.5 Enlarged overlapped motion compensation for luminance + +If Advanced Prediction mode is also used with Reduced-Resolution Update mode, enlarged matrices of weighting values are used to perform the overlapped motion compensation. Except that the size of each block and weighting matrices is $16 \times 16$ , the procedure of the creation of each prediction block is identical to the description in F.3. + +The enlarged matrices of weighting values for the $16 \times 16$ luminance prediction are given in Figures Q.4, Q.5 and Q.6. + +| | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 4 | 4 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 4 | 4 | +| 4 | 4 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 4 | 4 | +| 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| 4 | 4 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 4 | 4 | +| 4 | 4 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 4 | 4 | + +Figure Q.4/H.263 – Weighting values, $H_0$ , for prediction with motion vector of current $16 \times 16$ luminance block + +| | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | + +Figure Q.5/H.263 – Weighting values, $H_1$ , for prediction with motion vector of current $16 \times 16$ luminance blocks on top or bottom of current $16 \times 16$ luminance block + +| | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | +| 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | +| 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | +| 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | + +**Figure Q.6/H.263 – Weighting values, $H_2$ , for prediction with motion vector of $16 \times 16$ luminance blocks to the left or right of current $16 \times 16$ luminance block** + +## Q.6 Upsampling of the reduced-resolution reconstructed prediction error + +The $16 \times 16$ reconstructed prediction error block is obtained by upsampling the $8 \times 8$ reduced-resolution reconstructed prediction error block. In order to realize a simple implementation, filtering is closed within a block which enables to perform an individual upsampling on block basis. Figure Q.7 shows the positioning of samples. The upsampling procedure for the luminance and chrominance pixels which are inside the $16 \times 16$ reconstructed prediction error blocks is defined in Q.6.1. For the creation of the luminance and chrominance pixels which are at the boundary of $16 \times 16$ reconstructed prediction error block, the procedure is defined in Q.6.2. Chrominance blocks as well as luminance blocks are up-sampled. The symbol "/" in Figures Q.8 and Q.9 indicates division by truncation. + +![A diagram showing a 16x16 grid of samples. The grid is enclosed by a dashed line representing the block edge. Samples are represented by circles. Most circles are white, representing samples in a 16x16 reconstructed prediction error block. Some circles are shaded gray, representing samples in an 8x8 reduced-resolution reconstructed prediction error block. The shaded circles are arranged in a regular pattern, with one shaded circle for every four white circles in a 2x2 sub-grid.](dbbf61c7ed2ecc71307e31402743ca6b_img.jpg) + +A diagram showing a 16x16 grid of samples. The grid is enclosed by a dashed line representing the block edge. Samples are represented by circles. Most circles are white, representing samples in a 16x16 reconstructed prediction error block. Some circles are shaded gray, representing samples in an 8x8 reduced-resolution reconstructed prediction error block. The shaded circles are arranged in a regular pattern, with one shaded circle for every four white circles in a 2x2 sub-grid. + +T1603150-97 + +○ Position of samples in 8 \* 8 reduced-resolution reconstructed prediction error block + +○ Position of samples in 16 \* 16 reconstructed prediction error block + +----- Block edge + +**Figure Q.7/H.263 – Positioning of samples in 8 × 8 reduced-resolution reconstructed prediction error block and 16 × 16 reconstructed prediction error block** + +### Q.6.1 Upsampling procedure for the pixels inside a $16 \times 16$ reconstructed prediction error block + +The creation of reconstructed prediction error for pixels inside block is described in Figure Q.8. "/" indicates division by truncation. + +![Diagram illustrating the upsampling procedure for pixels inside a 16x16 reconstructed prediction error block. It shows a 2x2 grid of reduced-resolution pixels (A, B, C, D) and four intermediate pixels (a, b, c, d) to be reconstructed. Formulas for a, b, c, and d are provided, involving weighted sums of A, B, C, and D with truncation division by 16. A legend at the bottom identifies the gray circles as 'Reduced-Resolution reconstructed prediction error' and white circles as 'Reconstructed prediction error'.](1daee79ab1ab652586116f083d50ed9d_img.jpg) + +Diagram illustrating the upsampling procedure for pixels inside a $16 \times 16$ reconstructed prediction error block. The diagram shows a 2x2 grid of reduced-resolution pixels (A, B, C, D) and four intermediate pixels (a, b, c, d) to be reconstructed. The formulas for the reconstructed pixels are: + +$$\begin{aligned} a &= (9A + 3B + 3C + D + 8) / 16 \\ b &= (3A + 9B + C + 3D + 8) / 16 \\ c &= (3A + B + 9C + 3D + 8) / 16 \\ d &= (A + 3B + 3C + 9D + 8) / 16 \end{aligned}$$ + +⋮ + +T1603160-97 + +● Reduced-Resolution reconstructed prediction error + +○ Reconstructed prediction error + +Diagram illustrating the upsampling procedure for pixels inside a 16x16 reconstructed prediction error block. It shows a 2x2 grid of reduced-resolution pixels (A, B, C, D) and four intermediate pixels (a, b, c, d) to be reconstructed. Formulas for a, b, c, and d are provided, involving weighted sums of A, B, C, and D with truncation division by 16. A legend at the bottom identifies the gray circles as 'Reduced-Resolution reconstructed prediction error' and white circles as 'Reconstructed prediction error'. + +Figure Q.8/H.263 – Creation of reconstructed prediction error for pixels inside block + +### Q.6.2 Upsampling procedure for the pixels at the boundary of $16 \times 16$ reconstructed prediction error block + +The creation of reconstructed prediction error for pixels of a $16 \times 16$ block is shown in Figure Q.9. + +![Diagram illustrating the creation of reconstructed prediction error for pixels at the block boundary. It shows a 4x4 grid of circles representing pixels. The left and top edges are labeled 'Block boundary'. Some circles are labeled 'a', 'b', 'c', 'd', 'e'. To the right of the grid, formulas are provided: a = A, b = (3 * A + B + 2) / 4, c = (A + 3 * B + 2) / 4, d = (3 * A + C + 2) / 4, e = (A + 3 * C + 2) / 4. Below the grid, a legend shows a gray circle for 'Reduced-resolution reconstructed prediction error' and a white circle for 'Reconstructed prediction error'. The text 'T1603170-97' is also present.](d7896dd2d38adf224c3b76cd22d29c10_img.jpg) + +Block boundary + +a = A + $b = (3 * A + B + 2) / 4$ + $c = (A + 3 * B + 2) / 4$ + $d = (3 * A + C + 2) / 4$ + $e = (A + 3 * C + 2) / 4$ + +Block boundary + +T1603170-97 + +Reduced-resolution reconstructed prediction error + +Reconstructed prediction error + +Diagram illustrating the creation of reconstructed prediction error for pixels at the block boundary. It shows a 4x4 grid of circles representing pixels. The left and top edges are labeled 'Block boundary'. Some circles are labeled 'a', 'b', 'c', 'd', 'e'. To the right of the grid, formulas are provided: a = A, b = (3 \* A + B + 2) / 4, c = (A + 3 \* B + 2) / 4, d = (3 \* A + C + 2) / 4, e = (A + 3 \* C + 2) / 4. Below the grid, a legend shows a gray circle for 'Reduced-resolution reconstructed prediction error' and a white circle for 'Reconstructed prediction error'. The text 'T1603170-97' is also present. + +**Figure Q.9/H.263 – Creation of reconstructed prediction error for pixels at the block boundary** + +## Q.7 Block boundary filter + +The filter operations are performed along the edges of the $16 \times 16$ reconstructed blocks at the encoder as well as on the decoder side. There are two alternative of filtering, depending on whether Deblocking Filter mode is used or not. + +The default filtering in Reduced-Resolution Update mode is performed according to Q.7.1. + +If Deblocking Filter mode is also used with Reduced-Resolution Update mode, the filtering is performed according to Q.7.2. + +In both cases, filtering is performed on the complete reconstructed image data before storing the data in the picture store for future prediction. No filtering is performed across picture edges, slice edges in Slice Structured mode (see Annex K), or GOB boundaries having GOB headers present in Independent Segment Decoding mode (see Annex R). Chrominance as well as luminance data is filtered. + +### Q.7.1 Definition of the default block boundary filter + +In the Reduced-Resolution Update mode, the default filtering is performed according to this subclause. + +If A and B are two pixel values on a line – horizontal or vertical – of the reconstructed picture, and A belongs to one $16 \times 16$ block called block1 whereas B belongs to a neighboring $16 \times 16$ block called block2 which is to the right or below of block1. Figure Q.10 shows examples for the position of these pixels. + +![Figure Q.10/H.263 – Default block boundary filter. The diagram shows a grid of 16x16 blocks. A vertical line separates 'block1' (left) and 'block2' (right). A horizontal line separates 'block1' (top) and 'block2' (bottom). A thick black line labeled 'Block boundary' runs vertically between block1 and block2. Two pixels, A and B, are shown on this boundary. An arrow points to pixel A with the text 'Example for filtered pixels on a vertical block edge'. Another arrow points to pixel B with the text 'Example for filtered pixels on a horizontal block edge'. The diagram is labeled T1603180-97.](a98f3ef00da8508d2468334c6867f90f_img.jpg) + +Figure Q.10/H.263 – Default block boundary filter. The diagram shows a grid of 16x16 blocks. A vertical line separates 'block1' (left) and 'block2' (right). A horizontal line separates 'block1' (top) and 'block2' (bottom). A thick black line labeled 'Block boundary' runs vertically between block1 and block2. Two pixels, A and B, are shown on this boundary. An arrow points to pixel A with the text 'Example for filtered pixels on a vertical block edge'. Another arrow points to pixel B with the text 'Example for filtered pixels on a horizontal block edge'. The diagram is labeled T1603180-97. + +**Figure Q.10/H.263 – Default block boundary filter** + +One of the following conditions must be fulfilled in order to turn the filter on for a particular edge: + +- block1 belongs to a coded macroblock (COD==0 || MB-type == INTRA); **or** +- block2 belongs to a coded macroblock (COD==0 || MB-type == INTRA). + +A shall be replaced by A1 and B shall be replaced by B1. "/" indicates division by truncation. + +$$A1 = (3 * A + B + 2) / 4$$ + +$$B1 = (A + 3 * B + 2) / 4$$ + +The order of edges where filtering is performed is identical to the description provided in J.3. + +### **Q.7.2 Definition of the block boundary filter when Deblocking Filter mode is used** + +If the Deblocking Filter mode (see Annex J) is used with the Reduced-Resolution Update mode, the filtering which is defined in Annex J with one modification is performed on the boundary pixels of $16 \times 16$ luminance and chrominance blocks, in place of the filtering described in Q.7.1. The one modification of the filtering in Annex J is that the parameter STRENGTH is given the value of positive infinity. This implies that the function UpDownRamp(x, STRENGTH) defined in J.3 becomes a linear function of x. + +As a result, the procedure of the deblocking filter described in J.3 is redefined in the following manner: + +$$B1 = \text{clip}(B + d1)$$ + +$$C1 = \text{clip}(C - d1)$$ + +$$A1 = A - d2$$ + +$$D1 = D + d2$$ + +$$d1 = (A - 4B + 4C - D) / 8$$ + +$$d2 = \text{clipd1}((A - D) / 4, d1/2)$$ + +# Annex R + +# Independent Segment Decoding mode + +## R.1 Introduction + +This annex describes the optional Independent Segment Decoding mode of this Recommendation, which allows a picture to be decoded without the presence of any data dependencies across slice boundaries or across GOB boundaries having non-empty GOB headers. The use of this mode is indicated in the PLUSPTYPE field of the picture header. The capability to use this optional mode is negotiated by external means (for example, ITU-T Rec. H.245). + +When the use of this mode is indicated, the video picture segment boundaries (as defined by the boundaries of the slices or the upper boundaries of the GOBs for which GOB headers are sent, or the boundaries of the picture, whichever bounds a region in the smallest way) are treated as picture boundaries when decoding, including the treatment of motion vectors which cross those boundaries (which result in boundary extrapolation when the Unrestricted Motion Vector mode, the Advanced Prediction mode, the Deblocking Filter mode, or the Temporal, SNR, and Spatial Scalability mode are in use, and which are prohibited when none of those optional modes are in use). + +## R.2 Mode operation + +A video picture segment is defined by the following. + +If the Slice Structured mode (see Annex K) is not in use, then one GOB or a plural number of consecutive GOBs forms one video picture segment. The location of the top of each video picture segment is indicated by the presence of a non-empty GOB header for which the border of the video picture segment lies just above the macroblocks in the GOB for which a header is present, or the top of the picture, whichever is lower. The location of the bottom of each video picture segment is defined by the top of the next video picture segment, or the bottom of the picture, whichever is uppermost. + +If the Slice Structured mode (see Annex K) is in use, then each slice forms one video picture segment. + +In the Independent Segment Decoding mode, each video picture segment is decoded with complete independence from all other video picture segments, and is also independent of all data outside the same video picture segment location in the reference picture(s). This includes: + +- 1) no use of motion vectors outside of the current video picture segment for motion vector prediction (as in 6.1.1); +- 2) no use of motion vectors outside of the current video picture segment as remote motion vectors for overlapped block motion compensation when the Advanced Prediction mode is in use (see F.3); +- 3) no deblocking filter operation across video picture segment boundaries (see J.3); +- 4) no use of motion vectors which reference data outside the current video picture segment unless the Unrestricted Motion Vector mode (see Annex D), the Advanced Prediction mode (see Annex F), the Deblocking Filter mode (see Annex J) or the Temporal, SNR, and Spatial Scalability mode (see Annex O) are in use; in which case the borders of the current video picture segment in the prior picture are extrapolated as described in Annex D to form predictions of the pixels which reference the out-of-bounds region; +- 5) no bilinear interpolation across the boundaries of the $\frac{1}{4}$ -size or $\frac{1}{2}$ -size region corresponding to the current video picture segment for upward prediction in spatial scalability EI- and EP-pictures (as defined in Annex O); + +- 6) when the Reduced-Resolution Update mode (see Annex Q) is in use, no block boundary filter operation across video picture segment boundaries; +- 7) no use of the Reference Picture Resampling mode with the Independent Segment Decoding mode. + +## **R.3 Constraints on usage** + +Certain restrictions are placed on the use of other aspects of the video coding syntax when the Independent Segment Decoding mode is in use. These restrictions are made to prevent two pathological cases which otherwise would make operation of the Independent Segment Decoding mode difficult. + +### **R.3.1 Constraint on segment shapes** + +In the use of the Slice Structured mode (Annex K) without the use of the Rectangular Slice submode (see K.1), there can arise cases in which the shape of a video picture segment may be non-convex (having "inside corners", or even comprising two distinct and separated regions of the picture). + +Therefore, the Independent Segment Decoding mode shall not be used with the Slice Structured mode without the simultaneous use of the Rectangular Slice submode of the Slice Structured mode (see Annex K). This constraint is mandated to prevent the need for difficult special-case treatment in order to determine how and when to perform extrapolation of each video picture segment. + +### **R.3.2 Constraint on changes of segment shapes** + +If the shape of the video picture segments were allowed to change in any way from picture to picture in the bitstream, there could arise cases in which the bitstream would be difficult to decode. This is because in such cases the bitstream content is not sufficient to determine the shape of each video picture segment prior to the possible appearance of motion vectors in the bitstream which require knowledge of the video picture segment shape for proper interpretation. + +Therefore, when the Independent Segment Decoding mode is in use, the video picture segmentation for all pictures and frames allowing temporal prediction (i.e., all P-, B-, and EP-pictures and all Improved PB-frames) shall be the same as that used in its temporal reference picture. Also, when the Independent Segment Decoding mode is in use, the video picture segmentation for all EI-pictures shall either be the same or shall differ only by sub-dividing the video picture segmentation used in its reference picture. Also, the Independent Segment Decoding mode shall not be used in any picture or frame which uses reference pictures (all picture types except INTRA) unless the Independent Segment Decoding mode is also used in all of the reference picture(s) for the current picture. As a result of this constraint, the shape of the video picture segments in the Independent Segment Decoding mode shall never change from picture to picture except as changed in I- and EI-pictures (and the manner in which EI-pictures can change segmentation is itself also somewhat constrained). + +# Annex S + +# Alternative INTER VLC mode + +## S.1 Introduction + +This annex describes an optional Alternative INTER VLC mode of this Recommendation, which improves the efficiency of inter-picture coding when significant changes are evident in the picture. This efficiency improvement is obtained by allowing some VLC codes originally designed for INTRA pictures to be used for some INTER picture coefficients and CBPY data as well. The use of this mode is indicated in the PLUSPTYPE field of the picture header. The capability to use this optional mode is negotiated by external means (for example, ITU-T Rec. H.245). The mode contains two syntax alterations, one for the encoding of INTER coefficients and another for the encoding of the INTER CBPY values. + +## S.2 Alternative INTER VLC for coefficients + +The concept behind the design of the INTRA VLC table of Annex I is to use the same codewords as in the original INTER VLC but with a different interpretation of LEVEL and RUN. The INTRA VLC is better suited in cases where there are many and/or large-valued coefficients. + +The INTRA VLC is constructed so that codewords have the same value for LAST (0 or 1) in both the INTER and INTRA tables. The INTRA table is therefore produced by "reshuffling" the meaning of the codewords with the same value of LAST. Furthermore, for events with large |LEVEL| the INTRA table uses a codeword which in the INTER table has a large RUN. In INTER blocks having a large number of large-magnitude coefficients, it can sometimes be more efficient to use the INTRA table than the INTER table, and in some such cases the choice of the VLC table can be apparent to the decoder since decoding using the INTER table would result in RUN values so large as to indicate the presence of more than 64 coefficients for a block. Under these circumstances, the INTRA table can be used to improve the efficiency of INTER coding. + +### S.2.1 Encoder action + +The encoder may use the INTRA VLC table for coding an INTER block whenever the decoder can detect its use – in other words, whenever decoding using the INTER VLC table would cause coefficients outside the 64 coefficients of a block to be addressed. + +The encoder would normally choose to use the INTRA VLC table for coding an INTER block only when the above condition is satisfied and also when the INTRA VLC usage results in fewer bits than the INTER VLC for the same coefficient values. This will often be the case when there are many large coefficients, due to the way the INTRA VLC was produced (since the ordinary INTER VLC table contains long run-lengths for the same codewords in which the INTRA VLC table contains large coefficient amplitudes). + +### S.2.2 Decoder action + +The decoding process is as follows: + +- 1) The decoder first receives all coefficient codes of a block. +- 2) The codewords are then interpreted assuming that INTER VLC is used. If the addressing of coefficients stays inside the 64 coefficients of a block, the VLC decoding is finished. +- 3) If coefficients outside the block are addressed, the codewords shall be interpreted according to the INTRA VLC. + +## S.3 Alternative INTER VLC for CBPY + +The INTER CBPY codewords (Table 12) are designed with the assumption that there are more Y blocks with all zero coefficients than there are with at least one non-zero coefficient. When both $C_B$ and $C_R$ blocks have at least one non-zero coefficient, i.e., $CBPC_5 = CBPC_6 = 1$ , this assumption no longer holds. For this reason, when the Alternative INTER VLC mode is in use, the CBPY codewords as defined in Table 12 for INTRA macroblocks shall also be used for INTER macroblocks whenever $CBPC_5 = CBPC_6 = 1$ . + +# Annex T + +# Modified Quantization mode + +## T.1 Introduction + +This annex describes an optional Modified Quantization mode of this Recommendation, which modifies quantizer operation. The use of this mode is indicated in the PLUSPTYPE field of the picture header. The capability to use this optional mode is negotiated by external means (for example, ITU-T Rec. H.245). + +This mode includes four key features: + +- 1) The bit-rate control ability for encoding is improved by altering the syntax for the DQUANT field. +- 2) Chrominance fidelity is improved by specifying a smaller step size for chrominance than that for luminance data. +- 3) The range of representable coefficient values is extended to allow the representation of any possible true coefficient value to within the accuracy allowed by the quantization step size. +- 4) The range of quantized coefficient levels is restricted to those which can reasonably occur, to improve the detectability of errors and minimize decoding complexity. + +## T.2 Modified DQUANT Update + +This mode modifies the semantics of the DQUANT field. With this mode, it is possible to use DQUANT either to modify QUANT by plus or minus a small amount, or to signal any specific new value for QUANT. The size of the small amount of modification depends on the current value of QUANT. By use of this mode, more flexible control of the quantizer step size can be specified in the DQUANT field. + +The codeword for DQUANT in this mode is no longer a two-bit fixed length field. It is a variable length field which can either be two bits or six bits in length. Whether it is two or six bits depends on the first bit of the code. The description below is therefore split into two sections, depending on the first bit. + +### T.2.1 Small-step QUANT alteration + +When the first bit of the DQUANT field is 1, only one additional bit is sent in DQUANT. The single additional bit is used to modify QUANT by a differential value. The change in the value of QUANT is dependent on the second bit of DQUANT and on the prior value of QUANT, as shown in Table T.1. + +Example: If the previous value of QUANT is 29 and DQUANT is signalled with the codeword "11", then the differential value is +2, and thus the resulting new QUANT value is 31. + +**Table T.1/H.263 – Semantics of small-step QUANT alteration** + +| Prior QUANT | Change of QUANT | | +|--------------------|------------------------|--------------------| +| | DQUANT = 10 | DQUANT = 11 | +| 1 | +2 | +1 | +| 2-10 | −1 | +1 | +| 11-20 | −2 | +2 | +| 21-28 | −3 | +3 | +| 29 | −3 | +2 | +| 30 | −3 | +1 | +| 31 | −3 | −5 | + +### **T.2.2 Arbitrary QUANT selection** + +When the first bit of the DQUANT field is 0, five additional bits are sent in DQUANT. The following five bits represent a new QUANT as defined in 5.1.19. + +Example: Regardless of the current value of QUANT, if DQUANT is signalled with the code word '001111', then the new value of QUANT is 15. + +## **T.3 Altered quantization step size for chrominance coefficients** + +When the modified quantization mode is in use, the quantization parameter of the chrominance coefficients is different from the quantization parameter of the luminance. The luminance quantization parameter is signalled in the bitstream. It is called QUANT. When this mode is in use, a different quantization parameter termed QUANT\_C is used for the inverse quantization of chrominance coefficients. The relation between QUANT and QUANT\_C is given in Table T.2. If the Deblocking Filter mode (see Annex J) is in use, QUANT\_C shall also be used for the application of the deblocking filter to the chrominance data. Whenever QUANT is discussed herein in any other context, it shall mean the quantization step size of the luminance. + +**Table T.2/H.263 – Relationship between QUANT and QUANT\_C** + +| Range of QUANT | Value of QUANT_C | +|-----------------------|-------------------------| +| 1-6 | QUANT_C = QUANT | +| 7-9 | QUANT_C = QUANT − 1 | +| 10-11 | 9 | +| 12-13 | 10 | +| 14-15 | 11 | +| 16-18 | 12 | +| 19-21 | 13 | +| 22-26 | 14 | +| 27-31 | 15 | + +## T.4 Modified coefficient range + +When the Modified Quantization mode is in use, quantized DCT coefficients having quantization level magnitudes greater than 127 can be represented in the bitstream. This has two advantages: + +- 1) Encoder performance is improved by allowing the true full range of possible coefficient values to be represented. +- 2) Encoder complexity is reduced by eliminating the need to increase the quantization step size upon encountering certain large coefficient values which would otherwise be unrepresentable. + +It is possible that the correct value of a DCT coefficient prior to quantization in the encoder will have a magnitude as high as 2040. Thus, a range of $-127$ to $+127$ for LEVEL is insufficient to cover the entire range of possible coefficient values whenever the quantization parameter QUANT or QUANT\_C is less than 8. The expanded coefficient range broadens the range of LEVEL to allow any true coefficient value to be more properly encoded. + +When the Modified Quantization mode is in use, the meaning of the LEVEL field following an ESCAPE code (0000 011, as per 5.4.2) is altered. In this mode, rather than being forbidden, the bit sequence 1000 0000 is used to represent an EXTENDED-ESCAPE code. An AC coefficient of magnitude greater than 127 is represented by sending an EXTENDED-ESCAPE code, immediately followed by a fixed-length EXTENDED-LEVEL field of 11 bits. An extended coefficient value is encoded into the EXTENDED-LEVEL field by taking the least significant 11 bits of the two's-complement binary representation of LEVEL and cyclically rotating them to the right by 5-bit positions. This rotation is necessary to prevent start code emulation. The cyclic rotation is illustrated in Figure T.1. + +![](2f108a589e99e93fd7aa8fac626398c7_img.jpg) + +Bits of LEVEL field + +| | | | | | | | | | | | +|-----|-----|----|----|----|----|----|----|----|----|----| +| b11 | b10 | b9 | b8 | b7 | b6 | b5 | b4 | b3 | b2 | b1 | +|-----|-----|----|----|----|----|----|----|----|----|----| + + + +Bits of EXTENDED-LEVEL field + +| | | | | | | | | | | | +|----|----|----|----|----|-----|-----|----|----|----|----| +| b5 | b4 | b3 | b2 | b1 | b11 | b10 | b9 | b8 | b7 | b6 | +|----|----|----|----|----|-----|-----|----|----|----|----| + +**Figure T.1/H.263 – Cyclic rotation of coefficient representation** + +## T.5 Usage restrictions + +When the Modified Quantization mode is in use, certain restrictions are placed on the encoded coefficient values. This has several benefits: + +- 1) The detectability of bit errors is improved by prohibiting certain unreasonable coefficient values, thus allowing these values to be recognized as bit errors by the decoder; and +- 2) Decoder complexity is reduced by reducing the wordlength necessary for inverse quantization prior to clipping; +- 3) Start-code emulation is prevented for coefficients encoded using the EXTENDED-ESCAPE mechanism described in T.4. + +These restrictions are as follows. When the Modified Quantization mode is in use: + +- 1) For any coefficient, the reconstruction level magnitude $|\text{REC}|$ produced by the inverse quantization process described in 6.2.1 using the current value of QUANT or QUANT\_C as appropriate, and the encoded value of LEVEL, shall be less than 4096. This additional restriction applies to all coefficients, regardless of whether the coefficient is sent using the EXTENDED-ESCAPE mechanism or not. + +- 2) The bitstream shall not use either the normal ESCAPE code or the EXTENDED-ESCAPE code to encode a combination of LAST, RUN, and LEVEL for which there exists a codeword entry in the applicable VLC table, which is either Table 16 (see 5.4.2) or Table I.2 (see I.3). +- 3) The EXTENDED-ESCAPE code shall be used only when the quantization parameter for the coefficient (QUANT or QUANT\_C) is less than eight (8). +- 4) The EXTENDED-ESCAPE code shall be used only when it is followed by an EXTENDED-LEVEL field representing a value of LEVEL which is outside of the range -127 to +127. + +# Annex U + +## Enhanced reference picture selection mode + +## U.1 Introduction + +This annex describes the optional Enhanced Reference Picture Selection (ERPS) mode of this Recommendation. The capability to use this optional mode is negotiated by external means (for example, ITU-T Rec. H.245). The amount of picture memory accommodated in the decoder for ERPS operation should also be signalled by external means. The use of this mode shall be indicated by setting the formerly reserved bit 16 of the optional part of the PLUSPTYPE (OPPTYPE) to "1". The mode provides benefits for both error resilience and coding efficiency by using a memory buffer of reference pictures. + +A sub-mode of the ERPS mode is specified for Sub-Picture Removal. The purpose of Sub-Picture Removal is to reduce the amount of memory required to store multiple reference pictures. The memory reduction is accomplished by specifying the partitioning of each reference picture into smaller rectangular units called sub-pictures. The encoder can then indicate to the decoder that specific sub-picture areas of specific reference pictures will not be used as a reference for the prediction of subsequent pictures, thus allowing the memory allocated in the decoder for storing these areas to be used to store data from other reference pictures. The support for this sub-mode and the allowed fragmentation of the picture memory into minimum picture units (MPUs) for Sub-Picture Removal as defined herein is also negotiated by external means (for example, ITU-T Rec. H.245). + +A sub-mode of the ERPS mode is specified for enabling two-picture backward prediction in B pictures. This sub-mode can enhance performance by providing encoders for B pictures not only with an ability to use multiple references for forward prediction, but also to use more than one reference picture for backward prediction. The support for this sub-mode is negotiated by external means (for example, ITU-T Rec. H.245). + +For error resilience, the ERPS mode can use backward channel messages, which are signalled by external means (for example, ITU-T Rec. H.245) sent from a decoder to an encoder to inform the encoder which pictures or parts of pictures have been incorrectly decoded. The ERPS mode provides enhanced performance compared to the Reference Picture Selection (RPS) mode defined in Annex N. It shall not be used simultaneously with the RPS mode. (It can be used in such a way as to provide essentially the same functionality as the RPS mode.) + +For coding efficiency, motion compensation can be extended to prediction from multiple pictures. The extension of motion compensation to multi-picture prediction is achieved by extending each motion vector by a picture reference parameter that is used to address a macroblock or block prediction region for motion compensation in any of the multiple reference pictures. The picture + +reference parameter is a variable length code specifying a relative buffer index. The reference pictures are assembled in a buffering scheme that is controlled by the encoder. + +The ERPS mode shall not be used with the Syntax-based Arithmetic Coding mode (see Annex E) or the Data Partitioned Slice mode (see Annex V). + +Once activated, the ERPS mode shall not be inactivated in subsequent pictures in the bitstream unless the initial inactivation occurs in an I or EI picture and any reactivation is also in an I or EI picture and is accompanied by a buffer reset (RESET equal to "1"). If inactivated, the entire contents of the ERPS multi-picture buffer shall be set to "unused" status. + +## U.2 Video source coding algorithm + +The source coder of this mode is shown in generalized form in Figure U.1. This figure shows a structure that uses a number of picture memories. + +![Block diagram of the source coder for Enhanced Reference Picture Selection mode. The diagram shows the flow of video data from 'Video in' through various processing blocks including a subtractor, a switch, a Transform (T) block, a Quantizer (Q) block, and a series of Picture Memory (PM) blocks. A Coding Control (CC) block provides control signals (p, t, qz) to the quantizer and other components. The quantized data is then processed by a Quantizer (Q-) and a Transform (T-) block before being added back to the original video signal at a second adder. The output of the second adder is labeled 'v' (Motion vector) and is also fed into the Picture Memory (PM) blocks. The PM blocks are labeled PM0, PM1, ..., PM_M-1. A switch selects between the output of the PM blocks and the output of the second adder. The final output is labeled 'To video multiplex coder'.](7fdddd449ff61579cf1f067a3bde63b0_img.jpg) + +T1608680-00 + +Block diagram of the source coder for Enhanced Reference Picture Selection mode. The diagram shows the flow of video data from 'Video in' through various processing blocks including a subtractor, a switch, a Transform (T) block, a Quantizer (Q) block, and a series of Picture Memory (PM) blocks. A Coding Control (CC) block provides control signals (p, t, qz) to the quantizer and other components. The quantized data is then processed by a Quantizer (Q-) and a Transform (T-) block before being added back to the original video signal at a second adder. The output of the second adder is labeled 'v' (Motion vector) and is also fed into the Picture Memory (PM) blocks. The PM blocks are labeled PM0, PM1, ..., PM\_M-1. A switch selects between the output of the PM blocks and the output of the second adder. The final output is labeled 'To video multiplex coder'. + +| | | +|----|-------------------------------------------------------| +| T | Transform | +| Q | Quantizer | +| P | Picture Memory with motion compensated variable delay | +| PM | Picture Memory | +| CC | Coding control | +| p | Flag for INTRA/INTER | +| t | Flag for transmitted or not | +| qz | Quantizer indication | +| q | Quantizing index for transform coefficients | +| v | Motion vector | + +**Figure U.1/H.263 – Source coder for Enhanced Reference Picture Selection mode** + +The video source coding algorithm can be extended to multi-picture motion compensation. Enhanced coding efficiency may be achieved by allowing reference picture selection on the macroblock level. A picture buffering scheme with relative indexing is employed for efficient addressing of pictures in the multi-picture buffer. The multi-picture buffer control may work in two distinct types of operation. + +In the first of these two types of operation, a "Sliding Window" over time can be accommodated by the buffer control unit. In such a buffering scheme using $M$ picture memories $PM_0 \dots PM_{M-1}$ , the most recent preceding (up to $M$ ) decoded and reconstructed pictures are stored in the picture memories and can be used as references for decoding. If the number of pictures maximally accommodated by the multi-picture buffer corresponds to $M$ , the motion estimation when coding a picture $m$ , if $0 \leq m \leq M - 1$ , can utilize $m$ pictures. When coding a picture $m \geq M$ , the maximum number of pictures $M$ can be used. Alternatively, a second "Adaptive Memory Control" type of operation can be used for a more flexible and specific control of the picture memories than with the simple "Sliding Window" scheme. + +The operation of the ERPS mode results in the assignment of "unused" status to some pictures or sub-picture areas of pictures that have been sent to the decoder. Once some picture or area of a picture has been assigned to "unused" status, the bitstream shall not contain any data that causes a reference to any "unused" area for the prediction of subsequent pictures. By managing the assignment of "unused" status to previous pictures, the encoder shall ensure that sufficient memory is available in the decoder to store all data needed for the representation of subsequent pictures. The overall buffer size and structure is conveyed to the decoder in the bitstream, and the encoder shall control the buffer such that the specified total capacity is not exceeded by stored picture data that has not been assigned to "unused" status. + +The source coder may select one or several of the picture memories to suppress temporal error propagation caused by inter-picture coding. The Independent Segment Decoding mode (see Annex R), which treats boundaries of GOBs with non-empty headers or slices as picture boundaries, can be used to avoid spatial error propagation due to motion compensation across the boundaries of the GOBs or slices when this mode is applied to a smaller unit than a picture, such as a GOB or slice. The information to signal which picture is selected for prediction is included in the encoded bitstream. + +The strategy used by the encoder to select the picture or pictures to be used for prediction is out of the scope of this Recommendation. + +## U.3 Forward-channel syntax + +The syntax is altered in the picture, Group of Blocks (GOB), and slice layers. When indicated by a parameter MRPA being equal to "1", the syntax is also altered in the macroblock layer. In the picture, GOB, and slice layers, an Enhanced Reference Picture Selection layer (ERPS layer) is inserted. In the macroblock layer, picture reference parameters are inserted under certain conditions to enable multi-picture motion compensation. + +### U.3.1 Syntax of the picture, GOB, and slice layer + +The Enhanced Reference Picture Selection syntax for the PLUS header (otherwise as shown in Figure 8) is shown in Figure U.2. The fields of RPSMF, PN, and the ERPS layer are inserted into the PLUS header. The fields of TRPI, TRP, BCI, and BCM are not present (since they are only needed for the RPS mode of Annex N, which is not allowed when the ERPS mode is active). + +![Figure U.2/H.263 – Structure of PLUS header for the ERPS mode](a76fa39f5daf6a026e032495262ed0f6_img.jpg) + +``` + +graph LR + subgraph PLUS_Header + PLUSPTYPE --- CPM --- PSBI --- CPMFT --- EPAR --- CPCFC --- ETR --- UUI --- SSS --- ELNUM --- RLNUM + end + RLNUM -.-> RPS_Group + subgraph RPS_Group + RPSMF --- PN --- ERPS_layer + end + ERPS_layer --> RPRP_layer + style RPRP_layer stroke-dasharray: 0 + +``` + +The diagram illustrates the structure of the PLUS header for the ERPS mode. At the top, a horizontal row of eleven fields is shown: PLUSPTYPE, CPM, PSBI, CPMFT, EPAR, CPCFC, ETR, UUI, SSS, ELNUM, and RLNUM. Below this row, a line descends from RLNUM to a second-level box containing three elements: RPSMF, PN, and ERPS layer. An arrow points from this box to a third-level box labeled RPRP layer. Below the RPRP layer box, the reference code T1608690-00 is displayed. + +Figure U.2/H.263 – Structure of PLUS header for the ERPS mode + +**Figure U.2/H.263 – Structure of PLUS header for the ERPS mode** + +The syntax for the GOB layer is shown in Figure U.3. The fields of PNI, PN, NOERPSL, and the ERPS layer are added to the syntax (otherwise defined as in Figure 9). + +![Figure U.3/H.263 – Structure of GOB layer for the ERPS mode](5525e7460947727851585808324e1f98_img.jpg) + +``` + +graph TD + Start(( )) --> GSTUF([GSTUF]) + GSTUF --> GBSC[GBSC] + GBSC --> GN[GN] + GN --> GSBI[GSBI] + GSBI --> GFID[GFID] + GFID --> GQUANT[GQUANT] + + GSTUF -.-> PNI[PNI] + PNI --> PN[PN] + PNI --> NOERPSL[NOERPSL] + PN --> NOERPSL + NOERPSL --> ERPS_layer([ERPS layer]) + + ERPS_layer --> MB_Layer([MB Layer]) + GSTUF --> MB_Layer + MB_Layer --> MB_Layer + MB_Layer --> End(( )) + +``` + +The diagram illustrates the structure of the GOB layer for the ERPS mode. It begins with a horizontal sequence of fields: GSTUF (oval), GBSC, GN, GSBI, GFID, and GQUANT. Below the GSTUF field, a vertical sequence of elements is shown: PNI, PN, NOERPSL, and ERPS layer (oval). An arrow points from the ERPS layer to an MB Layer (oval). Below the GFID and GQUANT fields, the reference code T1608700-00 is displayed. Arrows indicate the flow and branching of the syntax elements. + +Figure U.3/H.263 – Structure of GOB layer for the ERPS mode + +**Figure U.3/H.263 – Structure of GOB layer for the ERPS mode** + +When the optional Slice Structured mode (see Annex K) is in use, the syntax of the slice layer is modified in the same way as the GOB layer. The syntax for the slice layer is shown in Figure U.4. The slice that immediately follows the picture start code in the bitstream also includes all of the added fields PNI, PN, NOERPSL, and the ERPS layer. + +![Flowchart showing the structure of the slice layer for the ERPS mode. The diagram illustrates the sequence of fields and layers: SSTUF, SSC, SEPB1, SSBI, MBA, SEPB2, SQUANT, SWI, SEPB3, GFID, PNI, PN, NOERPSL, ERPS layer, and MB layer. Arrows indicate the flow and optional loops between these elements.](26a7a1b6f7ec54302b6fa07ad23380b0_img.jpg) + +``` + +graph TD + Start(( )) --> SSTUF([SSTUF]) + SSTUF --> SSC[SSC] + SSC --> SEPB1[SEPB1] + SEPB1 --> SSBI[SSBI] + SSBI --> MBA[MBA] + MBA --> SEPB2[SEPB2] + SEPB2 --> SQUANT[SQUANT] + SQUANT --> SWI[SWI] + SWI --> SEPB3[SEPB3] + SEPB3 --> GFID[GFID] + GFID --> PNI[PNI] + PNI --> PN[PN] + PN --> NOERPSL[NOERPSL] + NOERPSL --> ERPS_layer([ERPS layer]) + ERPS_layer --> MB_layer([MB layer]) + MB_layer --> End(( )) + MB_layer --> SSTUF + MBA --> SQUANT + SEPB2 --> SQUANT + SEPB2 --> SWI + SEPB2 --> SEPB3 + SEPB2 --> GFID + SEPB2 --> PNI + SEPB2 --> PN + SEPB2 --> NOERPSL + SEPB2 --> ERPS_layer + SEPB2 --> MB_layer + T1608710-00[T1608710-00] + End --- T1608710-00 + +``` + +Flowchart showing the structure of the slice layer for the ERPS mode. The diagram illustrates the sequence of fields and layers: SSTUF, SSC, SEPB1, SSBI, MBA, SEPB2, SQUANT, SWI, SEPB3, GFID, PNI, PN, NOERPSL, ERPS layer, and MB layer. Arrows indicate the flow and optional loops between these elements. + +**Figure U.4/H.263 – Structure of slice layer for the ERPS mode** + +The ERPS layer is shown in Figure U.5. + +![Block diagram of the ERPS layer structure showing components MRPA, RMPNI, ADPN, LPIR, BTPSM, RPB, MMCO, MLIP1, LPIN, DPN, SPRB, SPREPB, SPWI, SPHI, SPTN, and RESET with their interconnections.](f54b2e4444e410765295be668123f27a_img.jpg) + +The diagram illustrates the internal structure of the ERPS layer. It begins with an input signal entering a block labeled MRPA. The output of MRPA is connected to RMPNI. RMPNI has two outputs: one to ADPN and another to LPIR. Both ADPN and LPIR have feedback loops back to RMPNI. The output of RMPNI also connects to RPB. RPB has a feedback loop back to MRPA. The output of RPB is connected to BTPSM and MMCO. BTPSM has a feedback loop back to RPB. MMCO has multiple outputs: one to MLIP1, one to LPIN, one to DPN, and one to a group of four blocks: SPWI, SPHI, SPTN, and RESET. LPIN has a feedback loop back to MMCO and an output to SPRB. SPRB has a feedback loop back to LPIN and an output to SPREPB. SPREPB has a feedback loop back to SPRB and an output to LPIN. DPN has a feedback loop back to MMCO and an output to SPRB. The outputs of MLIP1, LPIN, SPRB, SPREPB, DPN, SPWI, SPHI, SPTN, and RESET all converge to a common output line. A small label 'T1608720-00' is located at the bottom right of the diagram. + +Block diagram of the ERPS layer structure showing components MRPA, RMPNI, ADPN, LPIR, BTPSM, RPB, MMCO, MLIP1, LPIN, DPN, SPRB, SPREPB, SPWI, SPHI, SPTN, and RESET with their interconnections. + +Figure U.5/H.263 – Structure of the ERPS layer + +Variable length codes for the ADPN, LPIR, MLIP1, DPN, LPIN, SPTN, PR, PR0, PR2, PR3, PR4, PRB and PRFW fields are given in Table U.1. + +**Table U.1/H.263 – Variable length codes for ADPN, LPIR, MLIP1, DPN, LPIN, SPTN, PR, PR0, PR2, PR3, PR4, PRB, and PRFW** + +| Absolute position | Number of bits | Codes | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 1 | 1 | +| "x 0 "+1 (1:2) | 3 | 0x 0 0 | +| "x 1 x 0 "+3 (3:6) | 5 | 0x 1 1x 0 0 | +| "x 2 x 1 x 0 "+7 (7:14) | 7 | 0x 2 1x 1 1x 0 0 | +| "x 3 x 2 x 1 x 0 "+15 (15:30) | 9 | 0x 3 1x 2 1x 1 1x 0 0 | +| "x 4 x 3 x 2 x 1 x 0 "+31 (31:62) | 11 | 0x 4 1x 3 1x 2 1x 1 1x 0 0 | +| "x 5 x 4 x 3 x 2 x 1 x 0 "+63 (63:126) | 13 | 0x 5 1x 4 1x 3 1x 2 1x 1 1x 0 0 | +| "x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+127 (127:254) | 15 | 0x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 0 | +| "x 7 x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+255 (255:510) | 17 | 0x 7 1x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 0 | +| "x 8 x 7 x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+511 (511:1022) | 19 | 0x 8 1x 7 1x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 0 | +| "x 9 x 8 x 7 x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+1023 (1023:2046) | 21 | 0x 9 1x 8 1x 7 1x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 0 | +| "x 10 x 9 x 8 x 7 x 6 x 5 x 4 x 3 x 2 x 1 x 0 "+2047 (2047:4094) | 23 | 0x 10 1x 9 1x 8 1x 7 1x 6 1x 5 1x 4 1x 3 1x 2 1x 1 1x 0 0 | + +#### U.3.1.1 Reference Picture Selection Mode Flags (RPSMF) (3 bits) + +RPSMF is a 3-bit fixed-length codeword that is present in the PLUS header whenever the ERPS mode is in use (regardless of the value of UFEP). RPSMF shall not be present in the GOB or slice layer. When present, RPSMF indicates which type of back-channel messages are needed by the encoder. The values of RPSMF shall be as defined in 5.1.13. + +#### U.3.1.2 Picture Number Indicator (PNI) (1 bit) + +PNI is a single-bit fixed-length codeword that is always present at the GOB or slice layer when the ERPS mode is in use, and is not present in the PLUS header. When present, PNI indicates whether or not the following PN field is also present. + +"0": PN field is not present. + +"1": PN field is present. + +#### U.3.1.3 Picture Number (PN) (10 bits) + +PN is a 10-bit fixed-length codeword that is always present in the PLUS header when the ERPS mode is in use, and is present at the GOB or slice layer only when indicated by PNI. + +PN shall be incremented by 1 for each coded and transmitted picture, in a 10-bit modulo operation, relative to the PN of the previous stored picture. The term "stored picture" is defined in U.3.1.5.7. For EI and EP pictures, PN shall be incremented from the value in the last stored EI or EP picture within the same scalability enhancement layer. For B pictures, PN shall be incremented from the value in the most temporally-recent stored non-B picture in the reference layer of the B picture which precedes the B picture in bitstream order (a picture which is temporally subsequent to the B picture). B pictures are not stored in the multi-picture buffer, as they are not used as references for subsequent pictures. Thus, a picture immediately following a B picture in the reference layer of the B picture or another B picture which immediately follows a B picture shall have the same PN as the + +B picture. Similarly, if a non-B picture is present in the bitstream which is not stored, the picture following this non-B picture (in the same enhancement layer, in the case of Annex O operation) shall have the same PN as the non-stored non-B picture. + +In a usage scenario known as "Video Redundancy Coding", the ERPS mode may be used by some encoders in a manner in which more than one representation is sent for the pictured scene at the same temporal instant (usually using different reference pictures). In such a case in which the ERPS mode is in use and in which adjacent pictures in the bitstream have the same temporal reference and the same picture number, the decoder shall regard this occurrence as an indication that redundant copies have been sent of approximately the same pictured scene content, and shall decode and use the first such received picture while discarding the subsequent redundant picture(s). + +The PN serves as a unique ID for each picture stored in the picture buffer within 1024 coded and stored pictures. Therefore, a picture cannot be kept in the buffer after more than 1023 subsequent coded and stored pictures (in the same enhancement layer, in the case of Annex O operation) unless it has been assigned a long-term picture index as specified below. The encoder shall ensure that the bitstream shall not specify retaining any short-term picture after more than 1023 subsequent stored pictures. A decoder which encounters a picture number on a current stored picture having a value equal to the picture number of some other short-term picture in the multi-picture buffer should treat this condition as an error. + +#### **U.3.1.4 No Enhanced Reference Picture Selection Layer (NOERPSL) (1 bit)** + +NOERPSL is a single-bit fixed-length codeword that is present at the GOB or slice level whenever the ERPS mode is in use. It is not present in the PLUS header. The values of NOERPSL shall be as follows: + +- "0": The ERPS layer is sent. +- "1": The ERPS layer is not sent. + +If NOERPSL is "1", all ERPS settings and re-mappings in effect for the picture shall be applied also for the relevant video picture segment that follows the GOB or slice layer data. ERPS layer information sent at the GOB or slice level governs the decoding process for the video picture segment preceded by the GOB or slice level data, and does not affect the decoding process of any other video picture segment. (See Annex R for the definition of a video picture segment.) + +#### **U.3.1.5 Enhanced Reference Picture Selection layer (ERPS) (variable length)** + +The ERPS layer is always present at the picture level when the ERPS mode is in use, and is present at the GOB or slice level if NOERPSL is "0". It specifies the buffer indexing used to decode the current picture or video picture segment, and manages the contents of the picture buffer. + +##### **U.3.1.5.1 Multiple Reference Pictures Active (MRPA) (1 bit)** + +MRPA is a single-bit fixed-length codeword that is present only if the picture coding type indicates a P picture, an EP picture, an Improved PB frame, or B picture. MRPA is the first element in the ERPS layer if present. MRPA specifies whether the number of active reference pictures for forward-prediction or backward-prediction decoding of the current picture or video picture segment may be larger than one. The value of MRPA shall be as follows: + +- "1": More than one reference picture may be used for forward or backward motion compensation. +- "0": Only one reference picture is used for forward or backward motion compensation. In this case, the extensions of the macroblock layer syntax in U.3.2 do not apply. + +MRPA may be changed from video picture segment to video picture segment, so that different video picture segments may address different numbers of reference pictures. + +MRPA shall be "0" in any picture which invokes the Reference Picture Resampling mode (see Annex P), and the same picture shall be indicated as the forward reference picture to be used at both the picture and GOB or slice levels for any such current picture. If the current picture is a B picture, the backward reference picture shall have the same size as the current picture, and any reference picture resampling process shall be applied only to the forward reference picture. Reference picture resampling shall be invoked only if the multi-picture buffer contains sufficient "unused" capacity to store the resampled forward reference picture, but after the resampled reference picture is used for the decoding of the current picture, the resampled forward reference picture shall not be stored in the multi-picture buffer. + +##### U.3.1.5.2 Re-Mapping of Picture Numbers Indicator (RMPNI) (variable length) + +RMPNI is a variable-length codeword that is present in the ERPS layer if the picture is a P, EP, Improved PB, or B picture. RMPNI indicates whether any default picture indices are to be re-mapped for motion compensation of the current picture or video picture segment – and how the re-mapping of the relative indices into the multi-picture buffer is to be specified if indicated. RMPNI is transmitted using Table U.2. If RMPNI indicates the presence of an ADPN or LPIR field, an additional RMPNI field immediately follows the ADPN or LPIR field. + +**Table U.2/H.263 – RMPNI operations for re-mapping of reference pictures** + +| Value | Re-mapping specified | +|-------|------------------------------------------------------------------------------------------------------------| +| "1" | ADPN field is present and corresponds to a negative difference to add to a picture number prediction value | +| "010" | ADPN field is present and corresponds to a positive difference to add to a picture number prediction value | +| "011" | LPIR field is present and specifies the long-term index for a reference picture | +| "001" | End loop for re-mapping of picture relative indexing default order | + +A picture reference parameter is a relative index into the ordered set of pictures. The RMPNI, ADPN, and LPIR fields allow the order of that relative indexing into the multi-picture buffer to be temporarily altered from the default index order for the decoding of a particular picture or video picture segment. The default index order is for the short-term pictures (i.e., pictures which have not been given a long-term index) to precede the long-term pictures in the reference indexing order. Within the set of short-term pictures, the default order is for the pictures to be ordered starting with the most recent buffered reference picture and proceeding through to the oldest reference picture (i.e., in decreasing order of picture number in the absence of wrapping of the ten-bit picture number field). Within the set of long-term pictures, the default order is for the pictures to be ordered starting with the picture with the smallest long-term index and proceeding up to the picture with long-term index equal to the most recent value of MLIP1 – 1. + +For example, if the buffer contains three short-term pictures with short-term picture numbers 300, 302, and 303 (which were transmitted in increasing picture-number order) and two long-term pictures with long-term picture indices 0 and 3, the default index order is: + +- default relative index 0 refers to the short-term picture with picture number 303; +- default relative index 1 refers to the short-term picture with picture number 302; +- default relative index 2 refers to the short-term picture with picture number 300; +- default relative index 3 refers to the long-term picture with long-term picture index 0; and +- default relative index 4 refers to the long-term picture with long-term picture index 3. + +The first ADPN or LPIR field that is received (if any) moves a specified picture out of the default order to the relative index of zero. The second such field moves a specified picture to the relative + +index of one, etc. The set of remaining pictures not moved to the front of the relative indexing order in this manner shall retain their default order amongst themselves and shall follow the pictures that have been moved to the front of the buffer in relative indexing order. + +If MRPA is "0", no more than one ADPN or LPIR field shall be present in the same ERPS layer unless the current picture is a B picture. If the current picture is a B picture and MRPA is "0", no more than two ADPN or LPIR fields shall be present in the same ERPS layer. + +Any re-mapping of picture numbers specified for some picture shall not affect the decoding process for any other picture. Any re-mapping of picture numbers specified for some video picture segment shall not affect the decoding process for any other video picture segment. A re-mapping of picture numbers specified for a picture shall only affect the decoding process for any video picture segment within that picture in two ways: + +- If NOERPSL is "1" at the GOB or slice level, then the re-mapping specified at the picture level is also used for the associated video picture segment. +- If the picture is a B picture, the re-mapping specified at the picture level shall specify the calculation of the value of $TR_B$ and $TR_D$ for direct bidirectional prediction. + +An RMPNI "end loop" indication is the last element of the ERPS layer for a B picture if MRPA is "0". In a B picture with MRPA equal to "1", an RMPNI "end loop" indication is followed by BTPSM. In a P or EP picture or Improved PB frame, an RMPNI "end loop" indication is followed by RPBT. + +Within one ERPS layer, RMPNI shall not specify the placement of any individual reference picture into more than one re-mapped position in relative index order. + +##### **U.3.1.5.3 Absolute Difference of Picture Numbers (ADPN) (variable length)** + +ADPN is a variable-length codeword that is present only if indicated by RMPNI. ADPN follows RMPNI when present. ADPN is transmitted using Table U.1, where the index into the table corresponds to $ADPN - 1$ . ADPN represents the absolute difference between the picture number of the currently re-mapped picture and the prediction value for that picture number. If no previous ADPN fields have been sent within the current ERPS layer, the prediction value shall be the picture number of the current picture. If some previous ADPN field has been sent, the prediction value shall be the picture number of the last picture that was re-mapped using ADPN. + +If the picture number prediction is denoted $PNP$ , and the picture number in question is denoted $PNQ$ , the decoder shall determine $PNQ$ from $PNP$ and ADPN in a manner mathematically equivalent to the following: + +``` +if (RMPNI == "1") { // a negative difference + if (PNP - ADPN < 0) + PNQ = PNP - ADPN + 1024; + else + PNQ = PNP - ADPN; +} else { // a positive difference + if (PNP + ADPN > 1023) + PNQ = PNP + ADPN - 1024; + else + PNQ = PNP + ADPN; +} +``` + +The encoder shall control RMPNI and ADPN such that the decoded value of ADPN shall not be greater than or equal to 1024. + +As an example implementation, the encoder may use the following process to determine values of ADPN and RMPNI to specify a re-mapped picture number in question, PNQ: + +``` +DELTA = PNQ - PNP; +if (DELTA < 0) { + if (DELTA < -511) + MDELTA = DELTA + 1024; + else + MDELTA = DELTA; +} else { + if (DELTA > 512) + MDELTA = DELTA - 1024; + else + MDELTA = DELTA; +} +``` + +``` +ADPN = abs(MDELTA); +``` + +where abs() indicates an absolute value operation. Note that the index into Table U.1 corresponds to the value of ADPN - 1, rather than the value of ADPN itself. + +RMPNI would then be determined by the sign of MDELTA. + +#### **U.3.1.5.4 Long-term Picture Index for Re-Mapping (LPIR) (variable length)** + +LPIR is a variable-length codeword that is present only if indicated by RMPNI. LPIR follows RMPNI when present. LPIR is transmitted using Table U.1. It represents the long-term picture index to be re-mapped. The prediction value used by any subsequent ADPN re-mappings is not affected by LPIR. + +#### **U.3.1.5.5 B-picture Two-Picture Prediction Sub-Mode (BTPSM) (1 bit)** + +BTPSM is a single-bit fixed-length codeword that is present only in a B picture (see Annex O) and only when MRPA is "1". It follows an RMPNI "end loop" indication and is the last element of the ERPS layer for the B picture when present. It indicates whether the two-picture backward-prediction sub-mode is in use for the picture as follows: + +"0": Single-picture backward prediction. + +"1": Two-picture backward prediction. + +BTPSM has an implied value of "0" if not present (when MRPA is "0"). + +The set of pictures available for use as forward-prediction references is the set of pictures in the multi-picture buffer other than the set of backward reference pictures. The set of backward reference pictures is determined by the value of BTPSM. If single-picture backward prediction is specified by BTPSM, the first picture in (possibly re-mapped) relative index order is the only backward reference picture. If two-picture backward prediction is specified by BTPSM, the first two pictures in (possibly re-mapped) relative index order are the two backward reference pictures. The relative index for forward prediction then becomes a relative index into the set of forward reference pictures. + +The contents of the multi-picture buffer are not affected by the presence of a B picture. The B picture is not stored in the multi-picture buffer and is not used as a reference for the coding of subsequent pictures. + +#### **U.3.1.5.6 Reference Picture Buffering Type (RPBT) (1 bit)** + +RPBT is a single-bit fixed-length codeword that specifies the buffering type of the currently decoded picture. It follows an RMPNI "end loop" indication when the picture is not an I, EI, or B picture. It is the first element of the ERPS layer if the picture is an I or EI picture. It is not present if the picture is a B picture. The values for RPBT are defined as follows: + +"1": Sliding Window. + +"0": Adaptive Memory Control. + +In the "Sliding Window" buffering type, the current decoded picture shall be added to the buffer with index 0, and any marking of pictures as "unused" in the buffer is performed automatically in a first-in-first-out fashion among the set of short-term pictures. In this case, if the buffer has sufficient "unused" capacity to store the current picture, no additional pictures shall be marked as "unused" in the buffer. If the buffer does not have sufficient "unused" capacity to store the current picture, the picture (or pictures as necessary to free the needed amount of memory in the case of sub-picture removal) with the largest default index (or indices as necessary in the case of sub-picture removal) among the short-term pictures in the buffer shall be marked as "unused". In the "Sliding Window" buffering type, no additional information is transmitted to control the buffer contents. + +In the "Adaptive Memory Control" buffering type, the encoder explicitly specifies any addition to the buffer or marking of data as "unused" in the buffer, and may also assign long-term indices to short-term pictures. The current picture and other pictures may be explicitly marked as "unused" in the buffer, as specified by the encoder. This buffering type requires further information that is controlled by memory management control operation (MMCO) parameters. + +RPBT, if present in GOB or slice layers, shall be the same as in the picture layer. Any MMCO command present in GOB or slice layers shall convey the same operation as some MMCO command in the picture layer. + +If the picture is a B picture, RPBT shall not be present and the decoded picture shall not be stored in the multi-picture buffer. This ensures that a B picture shall not affect the contents of the multi-picture buffer. + +Similarly, the B-picture part of an Improved PB frame shall not be stored in the buffer. All control fields associated with controlling the storage of an Improved PB frame shall be considered to be associated with controlling the storage of only the P-picture part of the Improved PB frame. + +#### **U.3.1.5.7 Memory Management Control Operation (MMCO) (variable length)** + +MMCO is a variable-length codeword that is present only when RPBT indicates "Adaptive Memory Control", and may occur multiple times if present. It specifies a control operation to be applied to manage the multi-picture buffer memory. The MMCO parameter is followed by data necessary for the operation specified by the value of MMCO, and then an additional MMCO parameter follows – until the MMCO value indicates the end of the list of such operations. MMCO commands do not affect the buffer contents or the decoding process for the decoding of the current picture – rather, they specify the necessary buffer status for the decoding of subsequent pictures in the bitstream. The values and control operations associated with MMCO are defined in Table U.3. + +**Table U.3/H.263 – Memory Management Control Operation (MMCO) values** + +| Value | Memory Management Control Operation | Associated data fields following | +|--------------|-----------------------------------------------|-----------------------------------------| +| "1" | End MMCO loop | None (end of ERPS layer) | +| "011" | Mark a short-term picture as "Unused" | DPN | +| "0100" | Mark a long-term picture as "Unused" | LPIN | +| "0101" | Assign a long-term index to a picture | DPN and LPIN | +| "00100" | Mark short-term sub-picture areas as "Unused" | DPN and SPRB | +| "00101" | Mark long-term sub-picture areas as "Unused" | LPIN and SPRB | +| "00110" | Specify the maximum long-term picture index | MLIP1 | +| "00111" | Specify the buffer size and structure | SPWI, SPHI, SPTN, and RESET | + +All memory management control operations specified using MMCO shall be specified in the picture layer. Some or all of the same operations as are specified at the picture layer may also be specified at the GOB or slice layer (with the same associated data). MMCO shall not specify memory operations at the GOB or slice layer that are not also specified with the same associated data at the picture layer. + +A buffer size and structure specification MMCO command shall be the first MMCO command if present. No more than one buffer size and structure specification MMCO command shall be present in a given ERPS layer. A buffer size and structure specification MMCO command with RESET equal to "1" shall be present in the first picture in which the ERPS mode is activated in any series of ERPS mode pictures in the bitstream. A buffer size and structure specification MMCO command with RESET equal to "1" shall precede any use of MMCO to indicate marking sub-picture areas of any short-term or long-term pictures as "unused". The sub-picture width and height specified in a buffer size and structure specification MMCO command shall not differ from the value of these parameters in a prior buffer size and structure specification MMCO command unless the current picture is an I or EI picture with RESET equal to "1". The picture height and width shall not change within the bitstream except within a picture containing a buffer size and structure specification MMCO command with RESET equal to "1" (or within a picture in which the ERPS mode is not in use). + +If a B picture using single-picture backward prediction is present in the bitstream, exactly one temporally subsequent non-B picture in the reference layer of the B picture shall precede the B picture in bitstream order, as specified in O.2. No memory management control operations shall be present within any ERPS layer of this immediately temporally subsequent non-B picture within the reference layer of the B picture which mark any part of that immediately temporally succeeding non-B picture as "unused", since that reference layer picture is needed for display until after the decoding of the B picture. + +The transmission order constraints specified in O.2 are adjusted as necessary for B pictures using two-picture backward prediction. If a B picture using two-picture backward prediction is present in the bitstream, exactly two temporally subsequent non-B pictures in the reference layer of the B picture shall precede the B picture in bitstream order. The other restrictions on the transmission order of the B picture in the bitstream specified in O.2 shall apply, but as adjusted for the use of two temporally subsequent reference layer pictures. No memory management control operations shall be present within any ERPS layer of these two immediately temporally subsequent two non-B pictures within the reference layer of the B picture which mark any part of these two non-B pictures as "unused", since these reference layer pictures are needed for display until after the decoding of the B picture. + +A "stored picture" is defined as a non-B picture which does not contain an MMCO command in its ERPS layer which marks that picture as "unused". If the current picture is not a stored picture, its ERPS layer shall not contain any of the following types of MMCO commands: + +- an MMCO command to specify the buffer size and structure with RESET equal to "1"; +- any MMCO command which marks any other picture as "unused" that has not also been marked as "unused" in the ERPS layer of a prior stored picture; +- any MMCO command which assigns a long-term index to a picture that has not also been assigned the same long-term index in the ERPS layer of a prior stored picture; or +- any MMCO command which marks sub-picture areas of any picture as "unused" that have not also been marked as "unused" in the ERPS layer of a prior stored picture. + +#### **U.3.1.5.8 Difference of Picture Numbers (DPN) (variable length)** + +DPN is present when indicated by MMCO. DPN follows MMCO if present. DPN is transmitted using codewords in Table U.1 and is used to calculate the PN of a picture for a memory control operation. It is used in order to assign a long-term index to a picture, mark a short-term picture as "unused", or mark sub-picture areas of a short-term picture as "unused". If the current decoded picture number is PNC and the decoded value from Table U.1 is DPN, an operation mathematically equivalent to the following equations shall be used for calculation of PNQ, the specified picture number in question: + +``` +if (PNC - DPN < 0) + PNQ = PNC - DPN + 1024; +else + PNQ = PNC - DPN; +``` + +Similarly, the encoder may compute the DPN value to encode using the following relation: + +``` +if (PNC - PNQ < 0) + DPN = PNC - PNQ + 1024; +else + DPN = PNC - PNQ; +``` + +For example, if the decoded value of DPN is zero and MMCO indicates marking a short-term picture as "unused", the current decoded picture shall be marked as "unused". + +#### **U.3.1.5.9 Long-term Picture Index (LPIN) (variable length)** + +LPIN is present when indicated by MMCO. LPIN is transmitted using codewords in Table U.1 and specifies the long-term picture index of a picture. It follows DPN if the operation is to assign a long-term index to a picture. It follows MMCO if the operation is to mark a long-term picture as "unused" or to mark sub-picture areas of a long-term picture as "unused". + +#### **U.3.1.5.10 Sub-Picture Removal Bit-map (SPRB) (fixed length)** + +SPRB is a fixed-length codeword that contains one bit for each sub-picture and is present when indicated by MMCO. The number of bits of SPRB data is determined by the most recent values of SPWI and SPHI. SPRB is used to indicate which sub-picture areas of a buffered picture are to be marked as "unused". SPRB follows DPN if the operation is to mark sub-picture areas of a short-term picture as "unused", and follows LPIN if the operation is to mark sub-picture areas of a long-term picture as "unused". + +Sub-pictures are numbered in raster scan order starting from the upper-left corner of the picture. For example, consider a case in which a reference picture, specified by DPN, is partitioned into six sub-pictures. Let " $s_1 s_2 s_3 s_4 s_5 s_6$ " represent six bits of SPRB data. If bit $s_i$ is "1", then the decoder should mark the $i$ th sub-picture in the indicated reference picture as "unused". For example, if the SPRB is "000110", then the fourth and fifth sub-pictures areas are marked as "unused". + +To prevent start code emulation, all necessary SPREPB emulation prevention bits shall be inserted within or following the SPRB data as specified in U.3.1.5.11. + +If SPRB is present and the specified picture has been previously been affected by a prior SPRB bit-map, the bit-map specified by SPRB shall contain a "1" for any sub-picture area that contained a "1" in the previous SPRB bit-map. Every SPRB bit-map shall contain at least one bit having the value "0" and at least one bit having the value "1". + +#### **U.3.1.5.11 Sub-Picture Removal Emulation Prevention Bit (SPREPB) (one bit)** + +SPREPB is a single-bit fixed-length codeword having the value "1" which shall be inserted immediately after any string of 8 consecutive zero bits of SPRB data. + +#### **U.3.1.5.12 Maximum Long-term Picture Index Plus 1 (MLIP1) (variable length)** + +MLIP1 is a variable-length codeword that is present if indicated by MMCO. MLIP1 follows MMCO if present. MLIP1 is transmitted using codewords in Table U.1. If present, MLIP1 is used to determine the maximum index allowed for long-term reference pictures (until receipt of another value of MLIP1). The decoder shall initially assume MLIP1 is "0" until some other value has been received. Upon receiving an MLIP1 parameter, the decoder shall consider all long-term pictures having indices greater than the decoded value of MLIP1 – 1 as "unused" for referencing by the decoding process for subsequent pictures. For all other pictures in the multi-picture buffer, no change of status shall be indicated by MLIP1. + +#### **U.3.1.5.13 Sub-Picture Width Indication (SPWI) (7 bits)** + +SPWI is a fixed-length codeword of 7 bits that is present if indicated by MMCO. SPWI follows MMCO when indicated. SPWI specifies the width of a sub-picture in units of 16 luminance samples, such that the indicated sub-picture width is $16 \cdot (SPWI + 1)$ luminance samples. The current picture has a width in sub-picture units of $\text{ceil}(\text{ceil}(pw/16)/(SPWI + 1))$ sub-pictures, where pw is the width of the picture and "/" indicates floating-point division. For positive numbers, the ceiling function, $\text{ceil}(x)$ , equals x if x is an integer and otherwise $\text{ceil}(x)$ equals one plus the integer part of x. If a minimum picture unit (MPU) size defining the minimum width and height of a sub-picture has been negotiated by external means (for example, ITU-T Rec. H.245), the sub-picture width specified by SPWI shall be an integer multiple of the width of the MPU; otherwise, the sub-picture width specified by SPWI shall be such that SPWI is equal to $\text{ceil}(pw/16) - 1$ . + +#### **U.3.1.5.14 Sub-Picture Height Indication (SPHI) (7 bits)** + +SPHI is a fixed-length codeword of 7 bits that is present if SPWI is present (as indicated by MMCO). SPHI follows SPWI if present. SPHI specifies the height of a sub-picture in units of 16 luminance samples, such that the indicated sub-picture height is $16 \cdot SPHI$ . The allowed range of values of SPHI is from 1 to 72. The current picture has a height of $\text{ceil}(\text{ceil}(ph/16)/SPHI)$ sub-pictures, where ph is the height of the picture and "/" indicates floating-point division. If a minimum picture unit (MPU) size defining the minimum width and height of a sub-picture has been negotiated by external means (for example, ITU-T Rec. H.245), the sub-picture height specified by SPHI shall be an integer multiple of the height of the MPU; otherwise, the sub-picture height specified by SPHI shall be such that SPHI is equal to $\text{ceil}(ph/16)$ . + +#### **U.3.1.5.15 Sub-Picture Total Number (SPTN) (variable length)** + +SPTN is a variable-length codeword that is present if SPWI and SPHI are present (as indicated by MMCO). SPTN follows SPHI if present. SPTN is coded using Table U.1, where the index into Table U.1 corresponds to the decoded value of SPTN – 1. The decoded value of SPTN is the total operational size capacity of the multi-picture buffer in units of sub-pictures as specified by SPWI and SPHI. The memory capacity needed for the decoding of current pictures is not included in SPTN – only the memory capacity needed for storing the reference pictures to use for the prediction of other pictures. When sub-picture removal is not in use (i.e., when SPWI and SPHI have whole-picture dimensions), the maximum number of active short-term reference pictures (for example, for sliding window operation) is thus given by SPTN minus the number of pictures that have been assigned to long-term indices and have not been subsequently marked as "unused". + +#### **U.3.1.5.16 Buffer Reset Indicator (RESET) (1 bit)** + +RESET is a single-bit fixed-length codeword that is present if SPWI, SPHI, and SPTN are present (as indicated by MMCO). RESET follows SPTN if present. The values of RESET shall be as follows: + +- "0": The buffer contents are not reset. +- "1": The buffer contents are reset. + +If RESET is "1", all pictures in the multi-picture buffer (but not the current picture unless specified separately) shall be marked "unused" (including both short-term and long-term pictures). + +### U.3.2 Macroblock layer syntax + +#### U.3.2.1 P-picture and Improved PB frames macroblock syntax + +The macroblock layer syntax is modified if the ERPS layer is present for P pictures and Improved PB frames when the number of selected forward reference pictures may be greater than one, as indicated by MRPA. The field MRPA is signalled in the ERPS layer. The macroblock layer syntax is shown in Figure U.6 when MRPA is "1". Otherwise, the macroblock syntax format in a P picture or Improved PB frame is not altered from that shown in Figure 10. + +![Diagram of macroblock layer syntax for ERPS mode. It shows three levels of hierarchy. The top level is a single row of fields: COD, PR0, MEPB0, MCBPC, MODB, CBPB, CBPY, and DQUANT. An arrow points from the DQUANT field down to the second level. The second level is a row of fields: PR, MEPB, MVD, PR2, MEPB2, MVD2, PR3, MEPB3, MVD3, PR4, MEPB4, and MVD4. An arrow points from the MVD4 field down to the third level. The third level is a row of fields: PRB, MEPBB, MVDB, and Block data. The text 'T1608730-00' is located to the right of the second level.](330e22134db7091a48c4c2366006c0d4_img.jpg) + +Diagram of macroblock layer syntax for ERPS mode. It shows three levels of hierarchy. The top level is a single row of fields: COD, PR0, MEPB0, MCBPC, MODB, CBPB, CBPY, and DQUANT. An arrow points from the DQUANT field down to the second level. The second level is a row of fields: PR, MEPB, MVD, PR2, MEPB2, MVD2, PR3, MEPB3, MVD3, PR4, MEPB4, and MVD4. An arrow points from the MVD4 field down to the third level. The third level is a row of fields: PRB, MEPBB, MVDB, and Block data. The text 'T1608730-00' is located to the right of the second level. + +**Figure U.6/H.263 – Structure of P-picture and Improved PB frame macroblock layer for the ERPS mode** + +##### U.3.2.1.1 Interpretation of COD + +If the COD bit is "1", no further information is transmitted for the macroblock. In that case, the decoder shall treat the macroblock as an INTER macroblock with the motion vector for the entire macroblock equal to zero, picture reference parameter equal to zero, and with no coefficient data. If the COD bit is "0", indicating that the macroblock is coded, the syntax of the macroblock layer is depicted in Figure U.6 with the fields PR0, PR, PR2, PR3, PR4, and PRB being included in the syntax. PR0, PR, PR2, PR3, PR4, and PRB each consist of a variable length codeword as given in Table U.1. + +##### U.3.2.1.2 Picture Reference Parameter 0 (PR0) (variable length) + +PR0 is a variable length codeword as specified in Table U.1. It is present whenever COD is "0". If PR0 has a decoded value of zero (codeword "1"), it indicates that further information will follow for the macroblock. If decoded as non-zero, it indicates the coding of the macroblock using only a picture reference parameter. + +If the field PR0 does not have a decoded value of zero (codeword "1"), no further information is transmitted for this macroblock. In that case the decoder shall treat the macroblock as an INTER macroblock with the motion vector for the whole block equal to zero, the picture reference parameter equal to PR0, and with no coefficient data. + +If the field PR0 has a decoded value of zero (codeword "1"), the macroblock is coded. The meaning and usage of the fields MCBPC, CBPB, CBPY, and DQUANT remains unaltered. The field PR is included together with the field MVD for all INTER macroblocks (and in Improved PB frames mode also for INTRA macroblocks). The use of MODB in Improved PB frames is described in U.3.2.1.4. + +#### U.3.2.1.3 Macroblock Emulation Prevention Bit 0 (MEPB0) (1 bit) + +MEPB0 is a single-bit fixed-length codeword having the value "1" that follows PR0 if, and only if, PR0 is present and has a decoded value of "1" (codeword "000"), and either of the following two conditions are satisfied: + +- 1) the slice structured mode (see Annex K) is in use; or +- 2) the COD for the current macroblock immediately follows after another macroblock which also has COD = "0" and PR0 = "1" (codeword "000"), and the PR0 of the previous macroblock is not followed by an MEPB0 bit. + +The purpose of MEPB0 is to prevent start-code emulation and, in the slice structured mode, to aid in determining the number of macroblocks in a slice. + +#### U.3.2.1.4 Macroblock Picture Reference parameters (PR, PR2-4, and PRB) (variable length) + +PR is the primary picture reference parameter. PR is present whenever MVD is present. The three codewords PR2-4 are included together with MVD2-4 if indicated by PTYPE and if MCBPC specifies an INTER4V or INTER4V+Q macroblock (a macroblock of type 2 or 5 in Tables 8 and 9). PR2-4 and MVD2-4 are only present when in Advanced Prediction mode (see Annex F) or Deblocking Filter mode (see Annex J). PRB is only present in an Improved PB frame when MODB indicates that MVDB is present. PR, PR2-4, and PRB each specify a picture reference relative index into the multi-picture buffer. + +PR is used as the picture reference parameter for motion compensation of the entire macroblock if the macroblock is not an INTER4V or INTER4V+Q macroblock. If the macroblock is an INTER4V or INTER4V+Q macroblock, PR is used for motion compensated prediction of the first of the four 8 × 8 luminance blocks in the macroblock and for the two chrominance blocks of the macroblock (with the motion compensation process otherwise as specified in 6.1). PR2-4 are used for motion compensation of the remaining three 8 × 8 blocks of luminance data in the macroblock. If MODB indicates that MVDB is present, PRB is the picture reference parameter for forward prediction of the B part of the Improved PB frame. + +In Improved PB frames when MODB indicates BPB bidirectional prediction, the values of TRD and TRB shall be computed as the temporal reference increments based on the temporal reference data of the current picture and that of the most recent previous reference picture, regardless of whether or not the most recent previous reference picture has been re-mapped to a difference relative index order, marked as "unused", or assigned to a long-term index. The picture used as the forward reference picture for BPB bidirectional prediction in Improved PB frames shall be the picture specified by PR. + +#### U.3.2.1.5 Macroblock Emulation Prevention Bits (MEPB, MEPB2-4 and MEPBB) (1 bit each) + +MEPB, MEPB2-4, and MEPBB are each a single bit having the value "1" if present. Each shall be present if, and only if, the Unrestricted Motion Vector mode (see Annex D) is not in use and the associated PR, PR2-4, or PRB field is present and has the decoded value "1" (codeword "000"). Their purpose is to prevent start-code emulation. + +### U.3.2.2 B-picture and EP-picture macroblock syntax + +The macroblock layer syntax for B and EP pictures (see Annex O) is modified in a similar fashion as in P pictures. The COD bit, if equal to "1", indicates a skipped macroblock as defined in Annex O, using a picture reference parameter of zero for the forward (skipped) prediction in an EP picture and for the forward part of direct (skipped) bidirectional prediction in a B picture and using the first backward prediction picture for the backward part of direct (skipped) bidirectional + +prediction in a B picture (in the case of two-picture backward prediction, as when BSBBW is present and equal to "0"). If COD is "0", a PR0 parameter is inserted into the syntax and is used in a similar manner as described in U.3.2.1.2. If PR0 is present and does not have a decoded value of zero (codeword "1"), it indicates that the macroblock is to be predicted with forward INTER prediction using a zero-valued motion vector and a picture reference parameter of PR0. If PR0 has a decoded value of zero, MBTYPE follows and specifies the macroblock type. The format of the CBPC, CBPY, and DQUANT fields is unchanged. The MVDFW and MVDBW fields are encoded in the same manner as when the ERPS mode is not in use, but are each used in conjunction with a picture reference, and possibly an emulation prevention bit. + +For a B picture, the backward reference pictures in the multi-picture buffer are defined as follows: + +- in the case of single-picture backward prediction, there is only one backward reference picture, which is the first picture in (possibly re-mapped) relative index order; and +- in the case of two-picture backward prediction, there are two backward reference pictures, which are the first two pictures in (possibly re-mapped) relative index order. + +The forward reference pictures in the multi-picture buffer are defined as the pictures in the multi-picture buffer other than the backward reference pictures. The relative indexing for forward prediction is a relative index into the forward reference picture set, and the relative indexing for backward prediction is a relative index into the backward reference picture set. + +For example, if the buffer contains three short-term pictures with short-term picture numbers 300, 302, and 303 (which were transmitted in increasing picture-number order) and two long-term pictures with long-term picture indices 0 and 3, the default index order in the case of two-picture backward prediction is: + +- default backward relative index 0 refers to the short-term picture with picture number 303; +- default backward relative index 1 refers to the short-term picture with picture number 302; +- default forward relative index 0 refers to the short-term picture with picture number 300; +- default forward relative index 1 refers to the long-term picture with long-term picture index 0; and +- default forward relative index 2 refers to the long-term picture with long-term picture index 3; + +and in the case of single-picture backward prediction: + +- the single default backward reference picture is the short-term picture with picture number 303; +- default forward relative index 0 refers to the short-term picture with picture number 302; +- default forward relative index 1 refers to the short-term picture with picture number 300; +- default forward relative index 2 refers to the long-term picture with long-term picture index 0; and +- default forward relative index 3 refers to the long-term picture with long-term picture index 3; + +and if these pictures have been re-mapped to a new relative indexing order of short-term picture 302, followed by short-term picture 303, followed by long-term picture 0, followed by short-term picture 300, followed by long-term picture 3, the new relative index order in the case of two-picture backward prediction is: + +- re-mapped backward relative index 0 refers to the short-term picture with picture number 302; +- re-mapped backward relative index 1 refers to the short-term picture with picture number 303; + +- re-mapped forward relative index 0 refers to the long-term picture with long-term picture index 0; +- re-mapped forward relative index 1 refers to the short-term picture with picture number 300; and +- re-mapped forward relative index 2 refers to the long-term picture with long-term picture index 3; + +and in the case of single-picture backward prediction: + +- the single re-mapped backward reference picture is the short-term picture with picture number 302; +- re-mapped forward relative index 0 refers to the short-term picture with picture number 303; +- re-mapped forward relative index 1 refers to the long-term picture with long-term picture index 0; +- re-mapped forward relative index 2 refers to the short-term picture with picture number 300; and +- re-mapped forward relative index 3 refers to the long-term picture with long-term picture index 3. + +The $TR_D$ used for direct bidirectional prediction in a B picture shall be computed as the temporal reference increment between the first forward reference picture in (possibly re-mapped) relative index order and the first backward reference picture in (possibly re-mapped) relative index order (i.e., if two-picture backward prediction is in use, this would be the picture referenced when BSBBW is "0" as described in U.3.2.2.3). The $TR_B$ used for direct bidirectional prediction in a B picture shall be computed as the temporal reference increment between the B picture and the first forward reference picture in (possibly re-mapped) relative index order. The relative index order used in the computation of $TR_D$ and $TR_B$ shall be that specified by the ERPS layer at the picture level of the B picture syntax (i.e., re-mappings at the GOB or slice level shall not affect the values of $TR_D$ and $TR_B$ ). (See Figure U.7.) + +![Figure U.7/H.263 – Structure of EP- and B-picture macroblock layer for the ERPS mode. The diagram shows a flowchart of macroblock layer elements. It starts with COD, which points to PR₀. PR₀ points to MBTYPE. MBTYPE points to CBPC. CBPC points to CBPY. CBPY points to DQUANT. DQUANT points to PRFW. PRFW points to MEPBFW. MEPBFW points to MVDFW. MVDFW points to BSBBW. BSBBW points to MEPBBW. MEPBBW points to MVDBW. MVDBW points to Block layer. Block layer points to COD. There are also feedback loops from PRFW, MVDFW, BSBBW, MVDBW, and Block layer back to COD.](f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg) + +``` + +graph TD + COD[COD] --> PR0((PR₀)) + PR0 --> MBTYPE[MBTYPE] + MBTYPE --> CBPC[CBPC] + CBPC --> CBPY[CBPY] + CBPY --> DQUANT[DQUANT] + DQUANT --> PRFW((PRFW)) + PRFW --> MEPBFW[MEPBFW] + MEPBFW --> MVDFW((MVDFW)) + MVDFW --> BSBBW[BSBBW] + BSBBW --> MEPBBW[MEPBBW] + MEPBBW --> MVDBW((MVDBW)) + MVDBW --> BlockLayer((Block layer)) + BlockLayer --> COD + PRFW --> COD + MVDFW --> COD + BSBBW --> COD + MVDBW --> COD + BlockLayer --> COD + +``` + +T1608740-00 + +Figure U.7/H.263 – Structure of EP- and B-picture macroblock layer for the ERPS mode. The diagram shows a flowchart of macroblock layer elements. It starts with COD, which points to PR₀. PR₀ points to MBTYPE. MBTYPE points to CBPC. CBPC points to CBPY. CBPY points to DQUANT. DQUANT points to PRFW. PRFW points to MEPBFW. MEPBFW points to MVDFW. MVDFW points to BSBBW. BSBBW points to MEPBBW. MEPBBW points to MVDBW. MVDBW points to Block layer. Block layer points to COD. There are also feedback loops from PRFW, MVDFW, BSBBW, MVDBW, and Block layer back to COD. + +**Figure U.7/H.263 – Structure of EP- and B-picture macroblock layer for the ERPS mode** + +#### **U.3.2.2.1 Picture Reference for Forward Prediction (PRFW) (variable length)** + +PRFW is a variable-length picture reference parameter that is present whenever forward motion vector data is present, and is encoded using Table U.1. PRFW is a relative index into the set of forward reference pictures. + +#### **U.3.2.2.2 Emulation Prevention Bit for Forward Prediction (MEPBFW) (1 bit)** + +MEPBFW is a single-bit fixed-length codeword having the value "1" which shall be inserted after PRFW if and only if PRFW is present and has a decoded value of "1" (codeword "000") and the unrestricted motion vector mode (see Annex D) is not in use. + +#### **U.3.2.2.3 B-picture Selection Bit for Backward Prediction (BSBBW) (1 bit)** + +BSBBW is a single-bit fixed-length codeword that is present only for B pictures when MVDBW is present and only when two-picture backward prediction is specified for the B-picture operation. The meaning of this bit shall be defined as: + +- "0": Prediction from the first backward reference picture in relative index order (in default order, this would be the most recent short-term reference picture if that picture has not been assigned a long-term index or marked as "unused"). +- "1": Prediction from the second backward reference picture in relative index order (in default order, this would be the second-most recent short-term reference picture if neither of the last two reference pictures has been assigned a long-term index or marked as "unused"). + +#### **U.3.2.2.4 Emulation Prevention Bit for Backward Prediction (MEPBBW) (1 bit)** + +MEPBBW is a single-bit fixed-length codeword having the value "1" that is present only under the following conditions: + +- BSBBW is present and equal to "0"; and +- the unrestricted motion vector mode (see Annex D) is not in use; and +- BSBBW is preceded by five bits having the value "00000". + +### **U.4 Decoder process** + +The decoder for the ERPS mode stores the reference pictures for inter-picture decoding in a multi-picture buffer. The decoder may need additional memory capacity to store the multiple decoded pictures (relative to the memory capacity needed without support of the ERPS mode). The decoder replicates the multi-picture buffer of the encoder according to the reference picture buffering type and any memory management control operations specified in the bitstream. The buffering scheme may also be operated when partially erroneous pictures are decoded. + +Each transmitted and stored picture is assigned a Picture Number (PN) which is stored with the picture in the multi-picture buffer. PN represents a sequential picture counting identifier for stored pictures. PN is constrained, using modulo 1024 arithmetic operation. For the first transmitted picture, PN should be "0". For each and every other transmitted and stored picture, PN shall be increased by 1 (within a given scalability layer, if Annex O is in use). If the difference (modulo 1024) of the PNs of two consecutively received and stored pictures is not 1, the decoder should infer a loss of pictures or corruption of data. In such a case, a back-channel message indicating the loss of pictures may be sent to the encoder. + +Besides the PN, each picture stored in the multi-picture buffer has an associated index, called the default index. When a picture is first added to the multi-picture buffer, it is given default index 0 – unless it is assigned to a long-term index. The indices of pictures in the multi-picture buffer are modified when pictures are added to or removed from the multi-picture buffer. + +The pictures stored in the multi-picture buffers can also be divided into two categories: long-term pictures and short-term pictures. A long-term picture can stay in the multi-picture buffer for a long time (more than 1023 coded and stored picture intervals). The current picture is initially considered a short-term picture. Any short-term picture can be changed to a long-term picture by assigning it a long-term index according to information in the bitstream. The PN is the unique ID for all short-term pictures in the multi-picture buffer. When a short-term picture is changed to a long-term picture, it is also assigned a long-term picture index (LPIN). A long-term picture index is assigned to a picture by associating its PN to an LPIN. Once a long-term picture index has been assigned to a picture, the only potential subsequent use of the long-term picture's PN within the bitstream shall be in a repetition of the long-term index assignment. The PNs of the long-term pictures are unique within 1024 transmitted and stored pictures. Therefore, the PN of a long-term picture cannot be used for assignment of a long-term index after 1023 transmitted subsequent stored pictures. LPIN becomes the unique ID for the life of a long-term picture. + +PN (for a short-term picture) or LPIN (for a long-term picture) can be used to re-map the pictures into re-mapped indices for efficient reference picture addressing. + +#### U.4.1 Decoder process for short-/long-term picture management + +The decoder may have both long-term pictures and short-term pictures in its multi-picture buffer. The MLIP1 field is used to indicate the maximum long-term picture index allowed in the buffer. If no prior value of MLIP1 has been sent, no long-term pictures shall be in use, i.e., MLIP1 shall initially have an implied value of "0" upon invocation of the ERPS mode. Upon receiving an MLIP1 parameter, a new MLIP1 shall take effect until another value of MLIP1 is received. Upon receiving a new MLIP1 parameter in the bitstream, all long-term pictures with associated long-term indices greater than or equal to MLIP1 shall be considered marked "unused". The frequency of transmitting MLIP1 is out of the scope of this Recommendation. However, the encoder should send an MLIP1 parameter upon receiving an error message, such as an INTRA request message. + +A short-term picture can be changed to a long-term picture by using an MMCO command with an associated DPN and LPIN. The short-term picture number is derived from DPN and the long-term picture index is LPIN. Upon receiving such an MMCO command, the decoder shall change the short-term picture with PN indicated by DPN to a long-term picture and shall assign it to the long-term index indicated by LPIN. If a long-term picture with the same long-term index already exists in the buffer, the previously-existing long-term picture shall be marked "unused". An encoder shall not assign a long-term index greater than MLIP1 – 1 to any picture. If LPIN is greater than MLIP1 – 1, this condition should be treated by the decoder as an error. For error resilience, the encoder may send the same long-term index assignment operation or MLIP1 specification message repeatedly. If the picture specified in a long-term assignment operation is already associated with the required LPIN, no action shall be taken by the decoder. An encoder shall not assign the same picture to more than one long-term index value. If the picture specified in a long-term index assignment operation is already associated with a different long-term index, this condition should be treated as an error. An encoder shall only change a short-term picture to a long-term picture within 1024 transmitted consecutive stored pictures. In other words, a short-term picture shall not stay in the short-term buffer after more than 1023 subsequent stored pictures have been transmitted. An encoder shall not assign a long-term index to a short-term picture that has been marked as "unused" by the decoding process prior to the first such assignment message in the bitstream. An encoder shall not assign a long-term index to a picture number that has not been sent. + +#### U.4.2 Decoder process for reference picture buffer mapping + +The decoder employs indices when referencing a picture for motion compensation on the macroblock layer using the fields PR0, PR, PR2, PR3, PR4, PRB, PRFW, and BSBBW. In pictures other than B pictures, these indices are the default relative indices of pictures in the multi-picture buffer when the fields ADPN and LPIR are not present in the current picture, GOB, or slice layer as applicable, and are re-mapped indices when these fields are present. In B pictures, the first one or two pictures (depending on BTSPM) in relative index order are used for backward prediction, and the forward picture reference parameters specify a relative index into the remaining pictures for use in forward prediction. + +The indices of pictures in the multi-picture buffer can be re-mapped onto newly specified indices by transmitting the RMPNI, ADPN, and LPIR fields. RMPNI indicates whether ADPN or LPIR is present. If ADPN is present, RMPNI specifies the sign of the difference to be added to a picture number prediction value. The ADPN value corresponds to the absolute difference between the PN of the picture to be re-mapped and a prediction of that PN value. The first transmitted ADPN is computed as the absolute difference between the PN of the current picture and the PN of the picture to be re-mapped. The next transmitted ADPN field represents the difference between the PN of the previous picture that was re-mapped using ADPN and that of another picture to be re-mapped. The process continues until all necessary re-mapping is complete. The presence of re-mappings specified using LPIR does not affect the prediction value for subsequent re-mappings using ADPN. If RMPNI indicates the presence of an LPIR field, the re-mapped picture corresponds to a long-term picture with a long-term index of LPIR. If any pictures are not re-mapped to a specific order by + +RMPNI, these remaining pictures shall follow after any pictures having a re-mapped order in the indexing scheme, following the default order amongst these non-re-mapped pictures. + +If the decoder detects a missing picture, it may invoke some concealment process, and may insert an error-concealed picture into the multi-picture buffer. Missing pictures can be identified if one or several picture numbers are missing or if a picture not stored in the multi-picture buffer is indicated in a transmitted ADPN or LPIR. Concealment may be conducted by copying the closest temporally preceding picture that is available in the multi-picture buffer into the position of the missing picture. The temporal order of the short-term pictures in the multi-picture buffer can be inferred from their default index order and PN fields. In addition or instead, the decoder may send a forced INTRA update signal to the encoder by external means (for example, ITU-T Rec. H.245), or the decoder may use external means or back-channel messages (for example, ITU-T Rec. H.245) to indicate the loss of pictures to the encoder. A concealed picture may be inserted into the multi-picture buffer when using the "Sliding Window" buffering type. If a missing picture is detected when decoding a GOB or Slice layer, the concealment may be applied to the picture as if the missing picture had been detected at the picture layer. + +#### **U.4.3 Decoder process for sub-picture removal** + +Sub-picture removal may be used to reduce the amount of memory required to save multiple reference pictures. In sub-picture removal, each reference picture is partitioned into smaller equal-sized sub-pictures. The memory reduction is accomplished by marking undesired sub-pictures as "unused". The strategy used by the encoder to decide which of the sub-pictures to mark as "unused" is outside the scope of this Recommendation. The encoder signals to the decoder the size of the sub-pictures and which of the sub-pictures to mark as "unused" using MMCO commands in the enhanced reference picture selection (ERPS) layer. The encoder shall not send information in the bitstream that causes any samples in reference pictures or sub-pictures that it has caused to be marked as "unused" to be indicated for use in the prediction of subsequent pictures. + +The sub-picture removal capability is negotiated by external means (for example, ITU-T Rec. H.245). In addition, the decoder signals, also by external means, the minimum partition unit (MPU) which is described in terms of a minimum width and height (in units of 16 luminance samples) of a sub-picture and the total amount of memory it has available for its multi-picture buffer. Memory management is facilitated by the partition rules described below. + +Each reference picture is partitioned into rectangular sub-pictures of equal size. The encoder specifies the sub-picture size which shall be an integer multiple of the MPU. The width and height of the sub-picture shall be integer multiples of the minimum width and height negotiated externally as the MPU. The upper-left-hand corner of the first sub-picture is coincident with the upper-left-hand corner of the reference picture. Consequently, the entire partition may be described by specifying the width and height of a sub-picture. If the picture size is not an integer multiple of the sub-picture size, some sub-pictures may extend beyond the right and bottom boundaries of the reference picture. When a sub-picture that extends past the reference picture boundary is saved, a convenient memory management strategy is to set aside enough memory to save the entire sub-picture, rather than just the memory necessary to save the portion of the reference picture that lies within that sub-picture. This is the convention which shall be followed in any calculation of buffer spare capacity for the purpose of determining buffer fullness (e.g., in order to determine whether to automatically mark buffered pictures as "unused" in "sliding window" operation). A decoder designed such that each sub-picture occupies the same amount of memory will prevent the possibility of memory fragmentation. + +An example method designed to access referenced picture samples when sub-picture removal is in use is described briefly as follows. One important element in any reference picture access technique is a mechanism to identify where the samples in each sub-picture are stored in memory. If there are $R$ reference pictures and each picture is partitioned into $S$ sub-pictures, then there are a total of $K = R \cdot S$ sub-pictures. For example, the sub-picture in the upper-left hand corner of the first + +reference picture number can be considered sub-picture number 0, and the sub-picture to the right of it can be considered sub-picture number 1 and so on in raster scan order progressing from reference picture 1 to R until all K sub-pictures have a label. The total buffer capacity is SPTN sub-picture memory buffers, and SPTN is typically less than K. A K-element array can be defined, subPicMem[K], such that $t = \text{subPicMem}[k]$ corresponds to the sub-picture memory area that contains the samples in the kth sub-picture. For example, a case can be considered in which R = 5 reference pictures each have S = 12 sub-pictures. Then the samples for the 6th sub-picture in reference picture 3 would be found in sub-picture memory area $t = \text{subPicMem}[k]$ where $k = 3 \cdot S + 6 = 42$ . + +For example, when referencing samples for motion-compensated prediction of one block of luminance or chrominance data when the Advanced Prediction and Reduced Resolution Update optional modes are not in use, it is necessary to acquire $n \times m$ samples, where n and m may take values of 8 or 9 to accommodate half-integer motion compensation. Since the samples in one block may lie in up to four different sub-pictures, four separate cases must be considered. In all cases, the first step is to find the location in memory that contains the upper-left hand sample (U) of the block to be referenced. The sub-picture containing U can be identified by dividing the horizontal or vertical location of U by the sub-picture width or height. If U lies in sub-picture k, then that sample will be located in the subPicMem[k] sub-picture memory area. Next, if both the sample $m - 1$ samples to the right of U (i.e., the upper-right-hand corner of the block) and the sample $n - 1$ samples down from U (i.e., the lower-left-hand corner of the block) lie in sub-picture k, this can be considered case number one. If the sample $n - 1$ samples down from U lies within k, but the sample $m - 1$ samples to the right of U does not, this can be considered case two. If the sample $m - 1$ samples to the right of U lies within k, but the sample $n - 1$ down does not, this can be considered case three. Otherwise, when both the sample $m - 1$ samples to the right of U and the one $n - 1$ samples down lie outside of sub-picture k, this can be considered case four. + +In case number one, all samples in the reference block are contained within the kth sub-picture. In this case, all relevant $n \times m$ samples may be found in sub-picture memory area subPicMem[k] and it is a simple task to access them. In case two, the samples that lie in the kth sub-picture can be obtained from sub-picture memory area subPicMem[k] and the remaining samples can be obtained from subPicMem[kr] where kr is the sub-picture to the right of k. In case three, the samples that lie in the kth sub-picture can be obtained from memory area subPicMem[k], and the remaining samples can be obtained from subPicMem[kd] where kd is the sub-picture below k. In case four, the samples that lie in the kth sub-picture can be obtained from sub-picture memory area subPicMem[k] and the remaining samples can be obtained from memory areas subPicMem[kr], subPicMem[kd] and subPicMem[krd] where kr and kd are defined above and krd is the sub-picture to the right and below k. + +#### U.4.4 Decoder process for multi-picture motion compensation + +Multi-picture motion compensation is applied if the MRPA field indicates the use of more than one reference picture. For multi-picture motion compensation, the decoder chooses a reference picture as indicated using the fields PR0, PR1, PR2, PR3, PR4, PRB, PRFW and BSBBW on the macroblock layer. Once the reference picture is specified, the decoding process for motion compensation proceeds as described in 6.1. + +In case four motion vectors per macroblock are used and the MRPA field indicates the use of more than one reference picture, the picture reference index for both chrominance blocks is that associated with the first of the four motion vectors (with the motion compensation process otherwise as specified by 6.1). + +#### U.4.5 Decoder process for reference picture buffering + +The buffering of the currently decoded picture can be specified using the reference picture buffering type (RPBT) for non-B pictures. The buffering may follow a first-in, first-out ("Sliding Window") mode. Alternatively, the buffering may follow a customized adaptive buffering ("Adaptive Memory Control") operation that is specified by the encoder in the forward channel. B pictures do not affect buffer contents. + +The "Sliding Window" buffering type operates as follows. First, the decoder determine whether the picture can be stored into "unused" buffer capacity. If there is insufficient "unused" buffer capacity, the short-term picture with the largest default index (i.e., the oldest short-term picture in the buffer) shall be marked as "unused". This process is repeated if necessary (in the case of sub-picture removal) until sufficient memory capacity is freed to hold the current decoded picture. The current picture is stored in the buffer and assigned a default relative buffer index of zero. The default relative index of all other short-term pictures is incremented by one. The default relative index of all long-term pictures is incremented by one minus the number of short-term pictures removed. + +In the "Adaptive Memory Control" buffering type, specified pictures or sub-picture areas may be removed from the multi-picture buffer explicitly. The currently decoded picture, which is initially considered a short-term picture, may be inserted into the buffer with default relative index 0, may be assigned to a long-term index, or may be marked as "unused" by the encoder. Other short-term pictures may also be assigned to long-term indices. The buffering process shall operate in a manner functionally equivalent to the following: First, the current picture is added to the multi-picture buffer with default relative index 0, and the default relative indices of all other pictures is incremented by one. Then, the MMCO commands are processed: + +- If MMCO indicates a reset of the buffer contents by using RESET equal to "1", all pictures in the buffer are marked as "unused" except the current picture (which will be the picture with default relative index 0 since a buffer reset must be the first MMCO command as required by U.3.1.5.7). +- If MMCO indicates a maximum long-term index using MLIP1, all long-term pictures having long-term indices greater than or equal to MLIP1 are marked as "unused" and the default relative index order of the remaining pictures are not affected. +- If MMCO indicates that a picture is to be marked as "unused" in the multi-picture buffer and if that picture has not already been marked as "unused", the specified picture is marked as "unused" in the multi-picture buffer and the default relative index of all subsequent pictures in default order is decremented by one. +- If MMCO indicates that sub-picture areas of some picture are to be marked as "unused" in the multi-picture buffer, the specified sub-picture areas are marked as "unused" and the default relative index order of the pictures is not affected. As required by U.3.1.5.10, not all sub-picture areas of any given picture will be marked "unused" by a sub-picture removal MMCO command (instead, the encoder should send an MMCO command marking the picture as a whole as "unused"). +- If MMCO indicates the assignment of a long-term index to a specified short-term picture and if the specified long-term index has not already been assigned to the specified short-term picture, the specified short-term picture is marked in the buffer as a long-term picture with the specified long-term index. If another picture is already present in the buffer with the same long-term index as the specified long-term index, the other picture is marked as "unused". All short-term pictures that were subsequent to the specified short-term picture in default relative index order and all long-term pictures having a long-term index less than the specified long-term index have their associated default relative indices decremented by one. The specified picture is assigned to a default relative index of one plus the highest of the decremented default relative indices, or zero if there are no such decremented indices. + +The resulting buffered quantity of pictures or sub-picture regions not marked as "unused" shall not exceed the buffer capacity indicated by the most recent value of SPTN. If the decoder detects this condition, it should be treated as an error. + +## U.5 Back-channel messages + +An out-of-band channel, which need not necessarily be reliable, can be used to convey back-channel messages. The syntax of this out-of-band channel (which could be a separate logical channel, for example using ITU-T Rec. H.223 or ITU-T Rec. H.225.0) should be the one defined herein. The "videomux" operation of back-channel messages as defined in Annex N is not supported in the ERPS mode. + +### U.5.1 BCM separate logical channel layer + +The BCM layer as specified in U.5.2 should be carried by a BCM separate logical channel layer as shown in Figure U.8. + +![Diagram showing the structure of the BCM separate logical channel layer for ERPS mode. It consists of three stacked components: 'External framing' at the top, 'BCM layer' in the middle, and 'BSTUF' at the bottom. Arrows indicate the flow of data: from the top into 'External framing', from 'External framing' into 'BCM layer', and from 'BCM layer' into 'BSTUF'. A feedback arrow originates from the 'BSTUF' component and loops back up to the 'External framing' component. The diagram is labeled T1608750-00 at the bottom right.](864e6cb4a0166a5b21a5d19f694e1606_img.jpg) + +T1608750-00 + +Diagram showing the structure of the BCM separate logical channel layer for ERPS mode. It consists of three stacked components: 'External framing' at the top, 'BCM layer' in the middle, and 'BSTUF' at the bottom. Arrows indicate the flow of data: from the top into 'External framing', from 'External framing' into 'BCM layer', and from 'BCM layer' into 'BSTUF'. A feedback arrow originates from the 'BSTUF' component and loops back up to the 'External framing' component. The diagram is labeled T1608750-00 at the bottom right. + +Figure U.8/H.263 – Structure of BCM separate logical channel layer for ERPS mode + +#### U.5.1.1 External framing + +External framing of back-channel messages should be provided as shown in Figure U.8. The external framing is used to determine the starting point for the back-channel messages and the amount of back-channel message data to follow. + +#### U.5.1.2 Back-channel Stuffing (BSTUF) (variable length) + +BSTUF is a variable-length codeword that may be present only after the last back-channel message in an external frame. BSTUF consists of a codeword of variable length consisting of one or more bits of value "0". + +## U.5.2 Back-channel message layer syntax + +The syntax for the back-channel message (BCM) layer defined herein shall be as shown in Figure U.9. + +![Flowchart of Back-Channel Message (BCM) layer syntax for ERPS mode.](1c3caf3c28fe1461a879e214f5df25ae_img.jpg) + +``` +graph TD; BT[BT] --> ELNUMI[ELNUMI]; ELNUMI --> ELNUM[ELNUM]; ELNUM --> BCPM[BCPM]; BCPM --> BSBI[BSBI]; BSBI --> PNT[PNT]; PNT --> PN1[PN]; PNT --> LPIN1([LPIN]); PN1 --> RPNT[RPNT]; LPIN1 --> RPNT; RPNT --> PN2[PN]; RPNT --> LPIN2([LPIN]); PN2 --> ADT[ADT]; LPIN2 --> ADT; ADT --> GN_MBA[GN/MBA]; GN_MBA --> NMBM1[NMBM1]; NMBM1 --> ADT; NMBM1 --> RPNT; NMBM1 --> GN_MBA; T1608760-00[T1608760-00]; +``` + +The diagram illustrates the structure of the Back-Channel Message (BCM) layer for ERPS mode. It begins with the Back-Channel Message Type (BT), which points to the ELNUMI field. ELNUMI points to the ELNUM field, which in turn points to the BCPM field. BCPM points to the BSBI field, which points to the PNT field. PNT branches into PN and LPIN fields. Both PN and LPIN point to the RPNT field. RPNT branches into PN and LPIN fields. Both PN and LPIN point to the ADT field. ADT points to the GN/MBA field, which points to the NMBM1 field. NMBM1 points back to the ADT field, and also has feedback loops to the RPNT and GN/MBA fields. A label 'T1608760-00' is present below the NMBM1 field. + +Flowchart of Back-Channel Message (BCM) layer syntax for ERPS mode. + +Figure U.9/H.263 – Structure of Back-Channel Message (BCM) layer for ERPS mode + +### U.5.2.1 Back-channel message Type (BT) (2 bits) + +BT is a 2-bit fixed-length codeword which indicates the type of back-channel message. BT is the first codeword present in each back-channel message. Which type or types of message are requested by the encoder is indicated in the RPSMF field of the forward-channel syntax. The values of BT shall be defined as: + +- "00": Reserved for future use. +- "01": Reserved for future use. +- "10": NACK. This indicates the loss or erroneous decoding of the corresponding part of the forward channel data. +- "11": ACK. This indicates the correct decoding of the corresponding part of the forward channel data. + +#### **U.5.2.2 Enhancement Layer Number Indication (ELNUMI) (1 bit)** + +ELNUMI is a single-bit fixed-length codeword that follows BT in the back-channel message. ELNUMI shall be "0" unless the optional Temporal, SNR, and Spatial Scalability mode (see Annex O) is used in the forward channel and some enhancement layers of the forward channel are combined in one logical channel and the back-channel message refers to an enhancement layer (rather than the base layer), in which case ELNUMI shall be "1". + +#### **U.5.2.3 Enhancement Layer Number (ELNUM) (4 bits)** + +ELNUM is a 4-bit fixed-length codeword that is present only if ELNUMI is "1". It follows ELNUMI if present. When present, ELNUM contains the layer number of the enhancement layer referred to in the back-channel message. + +#### **U.5.2.4 Back-channel CPM Indicator (BCPM) (1 bit)** + +BCPM is a single-bit fixed-length codeword that follows ELNUMI or ELNUM in the back-channel message. BCPM shall be "0" unless the CPM mode (see 5.2.4 and Annex C) is used in the forward channel data, in which case BCPM shall be "1". If BCPM is "1", this indicates that BSBI is present. + +#### **U.5.2.5 Back-channel Sub-Bitstream Indicator (BSBI) (2 bits)** + +BSBI is a 2-bit fixed-length codeword that follows BCPM when present. BSBI is present only if BCPM is "1". BSBI is the natural binary representation of the Sub-Bitstream number in the forward channel data to which the back-channel message refers (see 5.2.4 and Annex C). + +#### **U.5.2.6 Picture Number Type (PNT) (1 bit)** + +PNT is a single-bit fixed-length codeword that is always present and follows BCPM or BSBI in the back-channel message. The values of PNT shall be defined as: + +"0": The message concerns a picture specified by a short-term picture number (PN). + +"1": The message concerns a picture specified by a long-term picture index (LPIN). + +PNT is followed by PN or LPIN, depending on the value of PNT. PN and LPIN shall be represented as specified for use in forward channel data in U.3.1.3 and U.3.1.5.9, respectively. + +#### **U.5.2.7 Requested Picture Number Type (RPNT) (2 bits)** + +RPNT is a 2-bit fixed-length codeword that is present only if BT indicates a NACK message. It follows PN or LPIN when present. It determines how to identify a picture in the multi-picture buffer which may be used as a reference for the coding of subsequent pictures. The values of RPNT shall be defined as: + +"00": No valid pictures in buffer – Buffer should be reset by an I or EI picture with RESET equal to "1". + +"01": No particular picture is identified to be used as a reference. + +"10": A picture which may be used as a reference is identified by a short-term picture number (PN). + +"11": A picture which may be used as a reference is identified by a long-term picture index (LPIN). + +If RPNT is "10" or "11", RPNT is followed by PN or LPIN, depending on the value of RPNT. PN and LPIN shall be represented as specified for use in forward channel data in U.3.1.3 and U.3.1.5.9, respectively. Typically the PN or LPIN specified using RPNT identifies the last correctly decoded spatially-corresponding picture area for the picture or region identified in the back-channel message. + +#### **U.5.2.8 Additional Data Type (ADT) (2 bits)** + +ADT is a 2-bit fixed-length codeword that is present after PN, LPIN, or RPNT, as determined by PNT (in an ACK message) or RPNT (in a NACK message). It may occur multiple times if present. It specifies the type of additional data used to identify a region of the picture of concern to which the back-channel message applies. The values of ADT shall be defined as: + +"00": End of additional data. + +"01": A region is identified by only a GN/MBA field. + +"10": A region is identified as a raster-scan area within a picture by GN/MBA and NMBM1. + +"11": A region is identified as a raster-scan area within a rectangular slice by GN/MBA and NMBM1. + +If ADT is "00", no more data follows in the back-channel message. If ADT is "01", ADT is followed by GN/MBA and then by another ADT. If ADT is "10" or "11", ADT is followed by GN/MBA and NMBM1 and then by another ADT. + +If ADT is "10", the region is identified as a region starting at a particular spatial location specified by GN/MBA and containing a specified number of macroblocks in raster-scan order within the picture. If ADT is "11", the region is identified as a region starting at a particular spatial location specified by GN/MBA and containing a specified number of macroblocks in raster-scan order within a rectangular slice. If ADT is present only once and is "00", the region identified is the picture as a whole. If ADT is present more than once, the value "00" is used only to end the loop rather than to identify a region. + +#### **U.5.2.9 GOB Number/Macroblock Address (GN/MBA) (5/6/7/9/11/12/13/14 bits)** + +GN/MBA is a fixed-length codeword which specifies a GOB number or macroblock address. GN/MBA follows ADT when present. GN/MBA is present when indicated by ADT. If the optional Slice Structured mode (see Annex K) is not in use, GN/MBA contains the GOB number of the beginning of an area to which the back-channel message refers. If the optional Slice Structured mode is in use, GN/MBA contains the macroblock address of the beginning of the area to which the back-channel message refers. The length of this field shall be as specified elsewhere in this Recommendation for GN or MBA. + +#### **U.5.2.10 Number of Macroblocks Minus 1 (NMBM1) (5/6/7/9/11/12/13/14 bits)** + +NMBM1 is a fixed-length codeword which specifies a number of macroblocks. NMBM1 is present when indicated by ADT. It follows GN/MBA when present. It contains the natural representation of the number of specified macroblocks minus 1. The length of this field shall be the length defined for a macroblock address in K.2.5 and in Table K.2. + +## Annex V + +### Data-partitioned slice mode + +#### V.1 Scope + +This annex describes the optional data-partitioned slice (DPS) mode of H.263. The capability of this mode is signalled by external means (for example, ITU-T Rec. H.245). The use of this mode shall be indicated by setting the formerly-reserved bit 17 of the optional part of the PLUSPTYPE (OPPTYPE) to "1". This mode uses the header structure defined in Annex K. + +Data partitioning provides robustness in error prone environments. This is accomplished using a rearrangement of the H.263 syntax to enable early detection of and recovery from errors that have been introduced during transmission. + +#### V.2 Structure of data partitioning + +When data partitioning is used, the data is arranged as a video picture segment, as defined in R.2. The MBs in the segment are rearranged so that the header information for all the MBs in the segment are transmitted together, followed by the MVs for all the MBs in the segment, and then by the DCT coefficients for all the MBs in the segment. The segment header uses the same syntax as described in K.2. The header, MV, and DCT partitions are separated by markers, allowing for resynchronization at the end of the partition in which an error occurred. Each segment shall contain the data for an integer number of MBs. When this mode is in use, the syntax shown in Figure V.1 shall be used. + +![Diagram of Data partitioning syntax showing the flow from Annex K Header to Macroblock Data, with a detailed view of the Macroblock Data structure.](22bf3e72e46aed04ae8d8cc27f802995_img.jpg) + +The diagram illustrates the data partitioning syntax. At the top, a bracket labeled "Annex K Header" spans over a sequence of fields: SSTUF, SSC, SEPB1, SSBI, MBA, SEPB2, SQUANT, SWI, SEPB3, and GFID. This is followed by a field labeled "Macroblock Data". Below this, a detailed view of the "Macroblock Data" is shown, which is divided into six fields: HD, HM, MVD, LMVV, MVM, and Coeff Data. A line connects the "Macroblock Data" field to its detailed view. The text "T1608770-00" is located at the bottom right of the diagram. + +Diagram of Data partitioning syntax showing the flow from Annex K Header to Macroblock Data, with a detailed view of the Macroblock Data structure. + +Figure V.1/H.263 – Data partitioning syntax + +Note that when this annex is not active, the MV and DCT data are transmitted in an interleaved fashion for all the MBs in a video picture segment, in which case an error normally results in the loss of all information for the remaining MBs in the packet. + +##### V.2.1 Header Data (HD) (Variable length) + +The Header Data field contains the COD and MCBPC information for all the MBs in the packets, plus the MODB data in case of PB-frames or Improved PB-frames. A reversible variable length code (RVLC) is used to combine the COD and the MCBPC for all the MBs in the packet. This code is shown in Tables V.1 through V.5. If Annex O is in use, the COD is only combined with the MB TYPE to form the RVLC for B and EP pictures using Tables V.3 and V.4, and the CBPC is coded with codewords in Table O.4. If COD = 0 and Annex G or Annex M is in use, the codeword for the COD+MCBPC shall be immediately followed by the reversible variable-length encoded data corresponding to the MODB field of the macroblock. Table V.6 shall be used for PB-frames, Table V.7 shall be used for Improved PB-frames. + +## V.2.2 Header Marker (HM) (9 bits) + +A codeword of 9 bits. Its value is 1010 0010 1. The HM terminates the header partition. When reversed decoding is used by a decoder, the decoder searches for this marker. This value cannot occur naturally in the HD field. + +## V.2.3 Motion vector data layer (Variable length) + +### V.2.3.1 Motion vector difference coding + +For the motion vectors, the RVLC codewords shown in Table D.3 are used to encode the difference between the motion vector and the motion vector prediction. Note that this annex only uses the entropy coding from Annex D, but not its other aspects unless Annex D is also in use. + +### V.2.3.2 Prediction of motion vector values + +The first motion vector in the packet is coded using a predictor value of 0 for both horizontal and vertical components, and the MVs for the subsequent coded MBs are coded predictively using the MV difference (MVD). This differs from the method otherwise used for coding the MVs in which the MVs following a skipped or INTRA MB are coded using a predictor value of 0 for both horizontal and vertical components. + +Forward Direction: $MV_i = MV_{i-1} + MVD_i = MV_{i-1} + (MV_i - MV_{i-1})$ + +Backward Direction: $MV_{i-1} = MV_i - MVD_i = MV_i - (MV_i - MV_{i-1})$ . + +( $MV_i$ and $MVD_i$ are the $i$ th MV and MV Difference in the packet respectively). + +The motion vector information for the last motion vector in the packet is coded in this manner and is also coded again in the LMVV field as described below in V.2.4. This allows the decoder to independently decode the sequence of MVs using two different prediction paths: + +- 1) in the forward direction, starting from the beginning of the motion data of the packet; and +- 2) in the backward direction, from the end of the motion data in a packet. + +This provides robustness for better error detection and concealment. + +NOTE 1 – When the DPS mode is not in use, motion vectors are predictively coded, with the prediction of the current motion vector being the median value of 3 motion vectors of neighboring locations as described in 6.1.1. Because packets in this annex are formed in a way such that the number of MBs coded in each packet is variable, using the median predictive coding method (which involves motion vectors on different rows of the frame) would prevent reversible decoding of the motion vectors in a slice. When the DPS mode is in use, a single prediction thread is formed for the MVs in the whole packet. This is shown in Figure V.2. + +![Diagram illustrating single thread motion vector prediction across four macroblocks (MBs). The first MB has 1 MV, the second and third have 4 MVs each, and the fourth has 1 MV. Arrows show the prediction thread moving from left to right, with arrows indicating the direction of motion vector prediction within each MB.](2fbbd361d3aff2374a19eb4fe03983bd_img.jpg) + +The diagram shows four macroblocks (MBs) arranged horizontally. The first MB is labeled 'MB with 1 MV' and has a single arrow pointing right. The second MB is labeled 'MB with 4 MVs' and contains four arrows forming a loop: top-left pointing right, top-right pointing up, bottom-right pointing left, and bottom-left pointing down. The third MB is also labeled 'MB with 4 MVs' and contains the same four arrows. The fourth MB is labeled 'MB with 1 MV' and has a single arrow pointing right. A continuous line with arrows connects the arrows across the MBs, showing a single prediction thread. Vertical labels '16 pixels' are present on the left and top of the first MB. + +Diagram illustrating single thread motion vector prediction across four macroblocks (MBs). The first MB has 1 MV, the second and third have 4 MVs each, and the fourth has 1 MV. Arrows show the prediction thread moving from left to right, with arrows indicating the direction of motion vector prediction within each MB. + +T1608780-00 + +**Figure V.2/H.263 – Single thread motion vector prediction** + +In case of B pictures or EP pictures (Annex O), MVDFW and MVDBW may be present as indicated by the MBTYPE codeword in Tables V.3 and V.4. MVDFW is predictively encoded + +using the same single prediction thread as described above and MVDBW (when present in B pictures) shall be encoded as specified in O.4.6. MVDFW and MVDBW shall be coded with the codewords from Table D.3. + +In case of PB-frames (Annex G) and Improved PB-frames (Annex M), the MVDB data shall be encoded as specified in corresponding annexes and shall be coded using the codewords from Table D.3. + +NOTE 2 – If the backward decoding mode is engaged in a B frame (Annex O) or in Improved PB-frames (Annex M), MVDB and MVDBW should be discarded by the decoder as the Motion Vector data for the backward prediction may not be recovered properly across the packet boundaries. + +### V.2.3.3 Start-code emulation prevention in motion vector difference coding + +The MVD start-code-emulation avoidance method is changed from the method described in D.2, in order to facilitate independent parsing in the backward direction. The MV partition shall be scanned from left to right and a MVD = 0 (codeword "1") shall be inserted after any two MVDs that are both equal to 1 (codeword "000"). If a third MVD = 1 codeword follows these two MVD = 1 codewords in the original bitstream (before insertion), it shall be considered the first MVD = 1 codeword detected in the remaining codewords in the MV partition. It shall not be considered a second MVD = 1 codeword, and shall not have a MVD = 0 codeword inserted after it. This differs from Annex D, in which the bit is only inserted when two consecutive MVD = 1 (codeword "000") form a pair (i.e., when the first MVD is the horizontal component, and the second is the vertical component). If Annex D and Annex V are both in use, this Annex V method of start-code-emulation avoidance method shall be used instead of the method described in D.2. + +### V.2.4 Last Motion Vector Value (LMVV) (Variable length) + +The LMVV field contains the last MV in the packet. It is coded using a predictor value of 0 for both the horizontal and vertical components. If there are no motion vectors or only one motion vector in the packet, LMVV shall not be present. (This use of a fixed zero-valued predictor enables the use of reversible decoding.) + +### V.2.5 Motion Vector Marker (MVM) (10 bits) + +A codeword of 10 bits having the value "0000 0000 01". The MVM terminates the motion vector partition. When reverse decoding is used in a decoder, the decoder searches for this marker. The Motion Vector Marker (MVM) shall not be included in the packet if the packet does not contain Motion Vector Data (if all the macroblocks in the packet are intra-coded or with CODs equal to 1). + +### V.2.6 Coefficient Data Layer (Variable length) + +The DCT data layer contains INTRA\_MODE (if present), CBPB (if present), CBPC (if present), CBPY, DQUANT (if present), and DCT coefficients coded as specified in I.2, 5.3.4, O.4.3, 5.3.5, 5.3.6, and 5.4.2, respectively. The syntax diagram of DCT Data is illustrated in Figure V.3. The presence of CBPC is indicated in Tables V.3 and V.4. + +![Figure V.3/H.263 – Coefficient Data syntax. A flowchart showing the sequence of fields: INTRA_MODE, CBPB, CBPC, CBPY, DQUANT, and BLOCK LAYER. Arrows indicate the flow, with feedback loops from INTRA_MODE, CBPB, CBPC, and DQUANT back to their entry points. A legend at the bottom left shows a rounded rectangle for Variable Length Code and a rectangle for Fixed Length Code. The text 'T1608790-00' is in the bottom right.](b9f3b61f140ea64afb9205312d52eb0e_img.jpg) + +``` + +graph LR + Start(( )) --> INTRA_MODE[INTRA_MODE] + INTRA_MODE --> CBPB[CBPB] + CBPB --> CBPC[CBPC] + CBPC --> CBPY[CBPY] + CBPY --> DQUANT[DQUANT] + DQUANT --> BLOCK_LAYER[BLOCK LAYER] + BLOCK_LAYER --> End(( )) + + INTRA_MODE --> INTRA_MODE + CBPB --> CBPB + CBPC --> CBPC + DQUANT --> DQUANT + +``` + +Variable Length Code + +Fixed Length Code + +T1608790-00 + +Figure V.3/H.263 – Coefficient Data syntax. A flowchart showing the sequence of fields: INTRA\_MODE, CBPB, CBPC, CBPY, DQUANT, and BLOCK LAYER. Arrows indicate the flow, with feedback loops from INTRA\_MODE, CBPB, CBPC, and DQUANT back to their entry points. A legend at the bottom left shows a rounded rectangle for Variable Length Code and a rectangle for Fixed Length Code. The text 'T1608790-00' is in the bottom right. + +Figure V.3/H.263 – Coefficient Data syntax + +### V.3 Interaction with other optional modes + +The DPS mode acts effectively as a sub-mode of the Slice Structured mode of Annex K, and uses its outer picture and slice header structures. The SS mode shall therefore be indicated as being in use whenever the DPS mode is in use. Both of the other sub-modes of the Slice Structured mode (the Arbitrary Slice Ordering and Rectangular Slice sub-modes) may be used in conjunction with the DPS mode. + +The Syntax-Based Arithmetic Coding mode of Annex E shall not be used with this annex, as it does not allow for reversible decoding. + +Annex H Forward Error Correction should not be used with this annex, as it can result in the bitstream being disrupted in undesirable places. However, the use of Annex H with the DPS mode is not forbidden, as the FEC defined in Annex H is required in some existing standard system designs. + +The Temporal, SNR, and Spatial Scalability (TSSS) mode of Annex O may be used in conjunction with the DPS mode. When the TSSS and DPS modes are used together, the codewords provided in Tables V.3, V.4 and V.5 shall be used instead of those defined in Annex O. + +Annex U shall not be used with this annex. + +**Table V.1/H.263 – COD + MCBPC RVLC table for INTRA MBs** + +| MB type | CBPC (56) | Codeword
(for combined
COD + MCBPC) | Number of bits | +|---------------|-----------|-------------------------------------------|----------------| +| 3 (INTRA) | 00 | 1 | 1 | +| 3 | 01 | 010 | 3 | +| 3 | 10 | 0110 | 4 | +| 3 | 11 | 01110 | 5 | +| 4 (INTRA + Q) | 00 | 00100 | 5 | +| 4 | 01 | 011110 | 6 | +| 4 | 10 | 001100 | 6 | +| 4 | 11 | 0111110 | 7 | +| stuffing | | 0011100 | 7 | + +**Table V.2/H.263 – COD + MCBPC RVLC table for INTER MBs** + +| MB type | CBPC (56) | Codeword
(for combined
COD+MCBPC) | Number of bits | +|-----------------|------------------|--------------------------------------------------|-----------------------| +| skipped | | 1 | 1 | +| 0 (INTER) | 00 | 010 | 3 | +| 0 | 10 | 00100 | 5 | +| 0 | 01 | 011110 | 6 | +| 0 | 11 | 0011100 | 7 | +| 1 (INTER + Q) | 00 | 01110 | 5 | +| 1 | 10 | 00011000 | 8 | +| 1 | 01 | 011111110 | 9 | +| 1 | 11 | 01111111110 | 11 | +| 2 (INTER4V) | 00 | 0110 | 4 | +| 2 | 10 | 01111110 | 8 | +| 2 | 01 | 00111100 | 8 | +| 2 | 11 | 000010000 | 9 | +| 3 (INTRA) | 00 | 001100 | 6 | +| 3 | 11 | 0001000 | 7 | +| 3 | 10 | 001111100 | 9 | +| 3 | 01 | 000111000 | 9 | +| 4 (INTRA + Q) | 00 | 0111110 | 7 | +| 4 | 11 | 0011111100 | 10 | +| 4 | 10 | 0001111000 | 10 | +| 4 | 01 | 0000110000 | 10 | +| 5 (INTER4V + Q) | 00 | 00111111100 | 11 | +| 5 | 01 | 00011111000 | 11 | +| 5 | 10 | 00001110000 | 11 | +| 5 | 11 | 00000100000 | 11 | +| stuffing | | 0111111110 | 10 | + +**Table V.3/H.263 – MBTYPE RVLC codes for B MBs** + +| Index | Prediction type | MVDFW | MVDBW | CBPC
+
CBPY | DQUANT | MBTYPE | Bits | +|-------|-----------------------|-------|-------|-------------------|--------|-----------|------| +| – | Direct (skipped) | | | | | 1 (COD=1) | 1 | +| 0 | Direct | | | X | | 010 | 3 | +| 1 | Direct + Q | | | X | X | 001100 | 6 | +| 2 | Forward (no texture) | X | | | | 00100 | 5 | +| 3 | Forward | X | | X | | 011110 | 6 | +| 4 | Forward + Q | X | | X | X | 01111110 | 8 | +| 5 | Backward (no texture) | | X | | | 0110 | 4 | +| 6 | Backward | | X | X | | 01110 | 5 | +| 7 | Backward + Q | | X | X | X | 00111100 | 8 | +| 8 | Bi-Dir (no texture) | X | X | | | 0011100 | 7 | +| 9 | Bi-Dir | X | X | X | | 0001000 | 7 | +| 10 | Bi-Dir + Q | X | X | X | X | 0111110 | 7 | +| 11 | INTRA | | | X | | 00011000 | 8 | +| 12 | INTRA + Q | | | X | X | 011111110 | 9 | +| 13 | Stuffing | | | | | 001111100 | 9 | + +**Table V.4/H.263 – MBTYPE RVLC table for EP MBs** + +| Index | Prediction type | MVDFW | MVDBW | CBPC
+
CBPY | DQUANT | MBTYPE | Bits | +|-------|---------------------|-------|-------|-------------------|--------|-----------|------| +| – | Forward (skipped) | | | | | 1 (COD=1) | 1 | +| 0 | Forward | X | | X | | 010 | 3 | +| 1 | Forward + Q | X | | X | X | 0110 | 4 | +| 2 | Upward (no texture) | | | | | 01110 | 5 | +| 3 | Upward | | | X | | 00100 | 5 | +| 4 | Upward + Q | | | X | X | 011110 | 6 | +| 5 | Bi-Dir (no texture) | | | | | 001100 | 6 | +| 6 | Bi-Dir | X | | X | | 0111110 | 7 | +| 7 | Bi-Dir + Q | X | | X | X | 0011100 | 7 | +| 8 | INTRA | | | X | | 0001000 | 7 | +| 9 | INTRA + Q | | | X | X | 01111110 | 8 | +| 10 | Stuffing | | | | | 00111100 | 8 | + +**Table V.5/H.263 – COD + MCBPC RVLC table for EI MBs** + +| Prediction type | QCBP (56) | Codeword
(for combined
COD+MCBPC) | Number of
bits | +|------------------|-----------|-----------------------------------------|-------------------| +| Upward (skipped) | | 1 | 1 | +| 0 (Upward) | 00 | 010 | 3 | +| 0 | 01 | 0110 | 4 | +| 0 | 10 | 01110 | 5 | +| 0 | 11 | 00100 | 5 | +| 1 (Upward + Q) | 00 | 011110 | 6 | +| 1 | 01 | 001100 | 6 | +| 1 | 10 | 0111110 | 7 | +| 1 | 11 | 0011100 | 7 | +| 2 (INTRA) | 00 | 0001000 | 7 | +| 2 | 01 | 01111110 | 8 | +| 2 | 10 | 00111100 | 8 | +| 2 | 11 | 00011000 | 8 | +| 3 (INTRA + Q) | 00 | 011111110 | 9 | +| 3 | 01 | 001111100 | 9 | +| 3 | 10 | 000111000 | 9 | +| 3 | 11 | 000010000 | 9 | +| Stuffing | | 0111111110 | 10 | + +**Table V.6/H.263 – RVLC table for MODB** + +| Index | CBPB | MVDB | Number of bits | Code | +|--------------------------------------------------------------|------|------|----------------|-------| +| 0 | | | 3 | 010 | +| 1 | | X | 4 | 0110 | +| 2 | X | X | 5 | 01110 | +| NOTE – "X" means that the item is present in the macroblock. | | | | | + +**Table V.7/H.263 – RVLC table for MODB for Improved PB-frames mode** + +| Index | CBPB | MVDB | Number
of bits | Code | Coding mode | +|---------------------------------------------------------------------------------------------------|------|------|-------------------|--------|--------------------------| +| 0 | | | 3 | 010 | Bidirectional prediction | +| 1 | X | | 4 | 0110 | Bidirectional prediction | +| 2 | | X | 5 | 01110 | Forward prediction | +| 3 | X | X | 5 | 00100 | Forward prediction | +| 4 | | | 6 | 011110 | Backward prediction | +| 5 | X | | 6 | 001100 | Backward prediction | +| NOTE – The symbol "X" in the table above indicates that the associated syntax element is present. | | | | | | + +## Annex W + +### Additional supplemental enhancement information specification + +#### W.1 Scope + +This annex describes the format of the additional supplemental enhancement information sent in the PSUPP field of the picture layer of H.263, which adds to the functionality defined in Annex L. The capability of a decoder to provide any or all of the capabilities described in this annex may be signalled by external means (for example, ITU-T Rec. H.245). Decoders which do not provide the additional capabilities may simply discard any of the newly defined PSUPP information bits that appear in the bitstream. The presence of this supplemental enhancement information is indicated by the presence of both the PEI bit, and by the following PSUPP octet whose FTYPE field has one of the two newly defined values. The basic interpretation of PEI, PSUPP, FTYPE, and DSIZE is identical to Annex L and to clauses 5.1.24 and 5.1.25. + +#### W.2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ISO/IEC 10646:2003, *Information technology – Universal Multiple-Octet Coded Character Set (UCS)*. +- IETF RFC 2396 (1998), *Uniform Resource Identifiers (URI): Generic Syntax*. + +#### W.3 Additional FTYPE values + +Two values that were reserved in Annex L, Table L.1 are defined as in Table W.1. + +**Table W.1/H.263 – FTYPE function type values** + +| | | +|----|------------------| +| 13 | Fixed-Point IDCT | +| 14 | Picture Message | + +#### W.4 Recommended maximum number of PSUPP octets + +When using any of the aforementioned FTYPE functions defined in this annex, the total number of PSUPP octets per picture should, in relation to the coded picture size, be kept reasonably small, and should not exceed 256 octets regardless of the coded picture size. + +NOTE – Some data transmission protocols used for conveyance of the video bitstream may provide for external repetition of picture header contents for error resilience purposes, and may place limits on the amount of such data that can be repeated from a picture header (e.g., 504 bits in the IETF RFC 2429 packetization format). The inclusion of a large number of PSUPP octets may result in the lack of such an external protocol to provide for full repetition of the picture header contents. + +#### W.5 Fixed-point IDCT + +The fixed-point IDCT function indicates that a particular IDCT approximation is used in construction of the bitstream. DSIZE shall be equal to 1 for the fixed-point IDCT function. The + +octet of PSUPP data that follows specifies the particular IDCT implementation. A value of 0 indicates the reference IDCT 0 as described in W.5.3; values of 1 through 255 are reserved. + +### W.5.1 Decoder operation + +The capability of a decoder to perform a particular fixed-point IDCT may be signalled to the encoder by external means (for example, ITU-T Rec. H.245). When receiving an encoded bitstream with the fixed-point IDCT indication, a decoder shall use the particular fixed-point IDCT if it is capable of doing so. + +### W.5.2 Removal of forced updating + +Annex A specifies the accuracy requirements for the inverse discrete cosine transform (IDCT), allowing numerous compliant implementations. To control accumulation of errors due to mismatched IDCTs at the encoder and decoder, clause 4.4, Forced Updating, requires that macroblocks be coded in INTRA mode at least once every 132 times when coefficients are transmitted. + +If the fixed-point IDCT function type is indicated in the bitstream, then the forced updating requirement is removed, and the frequency of INTRA coding is unregulated. An encoder should continue to use forced updating, however, unless it has ascertained through external means that the decoder is capable of the particular fixed-point IDCT specified herein; otherwise there may be mismatch. + +### W.5.3 Reference IDCT 0 + +The reference IDCT 0 is any implementation that, for every input block, produces identical output values as the C source program listed below. + +NOTE – This fixed-point IDCT is compliant with Annex A, but is not compliant with the extended range of values requirement in Annex A of ITU-T Rec. H.262 | ISO/IEC 13818-2. + +``` +/* ***** + * + * FIXED-POINT IDCT + * + * Fixed-point fast, separable idct + * Storage precision: 16 bits signed + * Internal calculation precision: 32 bits signed + * Input range: 12 bits signed, stored in 16 bits + * Output range: [-256, +255] + * All operations are signed + * + * *****/ + +/* + * Includes + */ + +#include +#include + +/* + * Typedefs + */ + +typedef short int REGISTER; /* 16 bits signed */ +typedef long int LONG; /* 32 bits signed */ + +/* + * Global constants + */ +``` + +``` + +const REGISTER cp08 = 0x539f; /* 32768*cos(pi/8)*1/sqrt(2) */ +const REGISTER sp08 = 0x4546; /* 32768*sin(pi/8)*sqrt(2) */ +const REGISTER cp16 = 0x7d8a; /* 32768*cos(pi/16) */ +const REGISTER sp16 = 0x18f9; /* 32768*sin(pi/16) */ +const REGISTER c3p16 = 0x6a6e; /* 32768*cos(3*pi/16) */ +const REGISTER s3p16 = 0x471d; /* 32768*sin(3*pi/16) */ +const REGISTER OoR2 = 0x5a82; /* 32768*1/sqrt(2) */ + +/* + * Function declarations + */ + +void Transpose(REGISTER block[64]); +void HalfSwap(REGISTER block[64]); +void Swap(REGISTER block[64]); +void Scale(REGISTER block[64], signed char sh); +void Round(REGISTER block[64], signed char sh, + const REGISTER min, const REGISTER max); +REGISTER Multiply(const REGISTER a, REGISTER x, signed char sh); +void Rotate(REGISTER *x, REGISTER *y, + signed char sha, signed char shb, + const REGISTER a, const REGISTER b, + int inv); +void Butterfly(REGISTER column[8], char pass); +void IDCT(REGISTER block[64]); + +/* + * Transpose(): + * Transpose a block + * Input: + * REGISTER block[64] + * Output: + * block + * Return value: + * none + */ +void Transpose(REGISTER block[64]) +{ + int i, j; + REGISTER temp; + + for (i=0; i<8; i++) { + for (j=0; j0) { + for (i=0; i<64; i++) + block[i] >>= sh; + } + else { + for (i=0; i<64; i++) + block[i] <<= -sh; + } +} + +/* + * Round(): + * Performs the final rounding of an 8x8 block + * Input: + * REGISTER block[64] + */ + +``` + +``` + +* signed char sh +* const REGISTER min +* const REGISTER max +* Output: +* block +* Return value: +* none +*/ +void Round(REGISTER block[64], signed char sh, + const REGISTER min, const REGISTER max) +{ + int i; + + for (i=0; i<64; i++) { + if (block[i] < 0x00007FFF - (1<<(sh-1))) + block[i] += (1<<(sh-1)); + else + block[i] = 0x00007FFF; + block[i] >>= sh; + block[i] = (block[i]max) ? max : block[i]); + } + return; +} + +/* + * Multiply(): + * Multiply by a constant with shift + * Input: + * const REGISTER a + * REGISTER x + * signed char sh + * Output: + * none + * Return value: + * REGISTER, the result of the multiply + */ +REGISTER Multiply(const REGISTER a, REGISTER x, signed char sh) +{ + LONG tmp; + REGISTER reg_out; + + /* multiply */ + tmp = (LONG)a * (LONG)x; + + /* shift */ + if (sh > 0) + tmp >>= sh; + else + tmp <<= -sh; + + /* rounding and saturating */ + if (tmp < 0x7FFFFFFF - 0x00007FFF) + tmp = tmp + 0x00007FFF; + else + tmp = 0x7FFFFFFF; + + reg_out = (REGISTER) (tmp >>16); + + return(reg_out); +} + +/* + * Rotate(): + * Perform rotate operation on two registers + */ + +``` + +``` + +* Input: +* REGISTER *x pointer to the 1st register +* REGISTER *y pointer to the 2nd register +* signed char sha shift associated with factor a +* signed char shb shift associated with factor b +* const REGISTER a factor a +* const REGISTER b factor b +* int inv 1 for inverse dct, 0 for forward dct +* Output: +* *x, *y +* Return value: +* none +*/ +void Rotate(REGISTER *x, REGISTER *y, + signed char sha, signed char shb, + const REGISTER a, const REGISTER b, + int inv) +{ + LONG tmplxa, tmplya, tmplxb, tmplyb; + LONG tmpl1, tmpl2; + + /* + * intermediate calculation + */ + + tmplxa = (LONG) (*x) * (LONG) a; + if (sha > 0) + tmplxa >>= sha; + else + tmplxa <<= -sha; + + tmplya = (LONG) (*y) * (LONG) a; + if (sha > 0) + tmplya >>= sha; + else + tmplya <<= -sha; + + tmplxb = (LONG) (*x) * (LONG) b; + if (shb > 0) + tmplxb >>= shb; + else + tmplxb <<= -shb; + + tmplyb = (LONG) (*y) * (LONG) b; + if (shb > 0) + tmplyb >>= shb; + else + tmplyb <<= -shb; + + /* + * rounding and rotation + */ + + if (inv) { + tmplxa += 0x00007FFF; + tmplxb += 0x00007FFF; + + tmpl1 = tmplxb - tmplya; + tmpl2 = tmplxa + tmplyb; + } + else { + tmplya += 0x00007FFF; + tmplyb += 0x00007FFF; + } +} + +``` + +``` + + tmpl1 = tmplxb + tmplya; + tmpl2 = -tmplxa + tmplyb; + } + + /* + * final rounding + */ + + *x = (REGISTER) (tmpl1 >>16); + *y = (REGISTER) (tmpl2 >>16); + + return; +} + +/* + * Butterfly(): + * Perform 1D IDCT on a column + * Input: + * REGISTER column[8] + * char pass + * Output: + * column + * Return value: + * none + */ +void Butterfly(REGISTER column[8], char pass) +{ + int i; + REGISTER shadow_column[8]; + + /* + * For readability, we use a shadow column + * that contains the state of column at the + * preceding stage of the butterfly. + */ + + /* + * Initialization + */ + + for (i=0; i<8; i++) + shadow_column[i] = column[i]; + + /* + * First Phase + */ + + Rotate(column+2, column+6, pass-2, pass-1, cpo8, spo8, 1); + Rotate(column+1, column+7, pass-1, pass-1, cpo16, spo16, 1); + Rotate(column+3, column+5, pass-1, pass-1, c3po16, s3po16, 1); + + if (pass) { + int a, tmp=column[4], b=column[0]; + a = b+tmp; + b = b-tmp; + column[0] = (a - ((tmp<0) ? 1 : 0)) >> 1; + column[4] = (b - ((tmp<0) ? 1 : 0)) >> 1; + } + else { + column[0] = shadow_column[0] + shadow_column[4]; + column[4] = shadow_column[0] - shadow_column[4]; + } +} + +``` + +``` + + for (i=0; i<8; i++) + shadow_column[i] = column[i]; + + /* + * Second Phase + */ + + column[1] = shadow_column[1] - shadow_column[3]; + column[3] = shadow_column[1] + shadow_column[3]; + + column[7] = shadow_column[7] - shadow_column[5]; + column[5] = shadow_column[7] + shadow_column[5]; + + column[0] = shadow_column[0] + shadow_column[6]; + column[6] = shadow_column[0] - shadow_column[6]; + + column[4] = shadow_column[4] + shadow_column[2]; + column[2] = shadow_column[4] - shadow_column[2]; + + for (i=0; i<8; i++) + shadow_column[i] = column[i]; + + /* + * Third Phase + */ + + column[7] = shadow_column[7] - shadow_column[3]; + column[3] = shadow_column[7] + shadow_column[3]; + + column[1] = Multiply(OoR2, shadow_column[1], -2); + column[5] = Multiply(OoR2, shadow_column[5], -2); + + for (i=0; i<8; i++) + shadow_column[i] = column[i]; + + /* + * Fourth Phase + */ + + column[4] = shadow_column[4] + shadow_column[3]; + column[3] = shadow_column[4] - shadow_column[3]; + + column[2] = shadow_column[2] + shadow_column[7]; + column[7] = shadow_column[2] - shadow_column[7]; + + column[0] = shadow_column[0] + shadow_column[5]; + column[5] = shadow_column[0] - shadow_column[5]; + + column[6] = shadow_column[6] + shadow_column[1]; + column[1] = shadow_column[6] - shadow_column[1]; + + return; +} + +/* + * IDCT(): + * Perform 2D IDCT on a block + * Input: + * REGISTER block[64] + * Output: + * block + * Return value: + * none + */ + +``` + +``` + +void IDCT(REGISTER block[64]) +{ + int i; + + Scale(block, -4); + + for (i=0; i<8; i++) + Butterfly(block+8*i, 0); + + Transpose(block); + + for (i=0; i<8; i++) + Butterfly(block+8*i, 1); + + Round(block, 6, -256, 255); + + Swap(block); +} + +``` + +For informative purposes, a related forward discrete cosine transform (FDCT) implementation is shown below. This fixed-point FDCT does not form an integral part of this Recommendation. + +``` + +/***** + * + * FIXED-POINT FDCT + * + * Fixed-point fast, separable fdct + * Storage precision: 16 bits signed + * Internal calculation precision: 32 bits signed + * Input range: 9 bits signed, stored in 16 bits + * Output range: [-2048, +2047] + * All operations are signed + * + *****/ + +/* + * Function declarations + */ + +void FButterfly(REGISTER column[8]); +void FDCT(REGISTER block[64]); + +/* + * FButterfly(): + * Perform 1D FDCT on a column + * Input: + * REGISTER column[8] + * Output: + * column + * Return value: + * none + */ +void FButterfly(REGISTER column[8]) +{ + int i; + REGISTER shadow_column[8]; + + /* + * For readability, we use a shadow column + * that contains the state of column at the + * preceding stage of the butterfly. + */ + +``` + +``` + + /* + * Initialization + */ + + for (i=0; i<8; i++) + shadow_column[i] = column[i]; + + /* + * First Phase + */ + + for (i=0; i<4; i++) { + column[i] = shadow_column[i] + shadow_column[7-i]; + column[7-i] = shadow_column[i] - shadow_column[7-i]; + } + + for (i=0; i<8; i++) + shadow_column[i] = column[i]; + + /* + * Second Phase + */ + + column[0] = shadow_column[0] + shadow_column[3]; + column[3] = shadow_column[0] - shadow_column[3]; + + column[1] = shadow_column[1] + shadow_column[2]; + column[2] = shadow_column[1] - shadow_column[2]; + + column[4] = Multiply(OoR2, shadow_column[4], -2); + column[7] = Multiply(OoR2, shadow_column[7], -2); + + column[6] = shadow_column[6] - shadow_column[5]; + column[5] = shadow_column[6] + shadow_column[5]; + + for (i=0; i<8; i++) + shadow_column[i] = column[i]; + + /* + * Third Phase + */ + + column[0] = shadow_column[0] + shadow_column[1]; + column[1] = shadow_column[0] - shadow_column[1]; + + column[6] = shadow_column[6] - shadow_column[4]; + column[4] = shadow_column[6] + shadow_column[4]; + + column[7] = shadow_column[7] - shadow_column[5]; + column[5] = shadow_column[7] + shadow_column[5]; + + for (i=0; i<8; i++) + shadow_column[i] = column[i]; + + /* + * Fourth Phase + */ + + Rotate(column+2, column+3, -2, -1, cpo8, spo8, 0); + Rotate(column+4, column+5, -1, -1, cpo16, spo16, 0); + Rotate(column+6, column+7, -1, -1, c3po16, s3po16, 0); + + return; +} + +``` + +``` + +/* + * FDCT(): + * Perform 2D FDCT on a block + * Input: + * REGISTER block[64] + * Output: + * block + * Return value: + * none + */ +void FDCT(REGISTER block[64]) +{ + int i; + + for (i=0; i<8; i++) + FButterfly(block+8*i); + + Transpose(block); + + for (i=0; i<8; i++) + FButterfly(block+8*i); + + Round(block, 3, -2048, 2047); + + Swap(block); +} + +``` + +## W.6 Picture message + +The picture message function indicates the presence of one or more octets representing message data. The first octet of the message data is a message header with the following structure, as shown in Figure W.1. + +| | | | +|------|------|-------| +| CONT | EBIT | MTYPE | +|------|------|-------| + +**Figure W.1/H.263 – Structure of first message octet** + +DSIZE shall be equal to the number of octets in the message data corresponding to a picture message function, including the first octet shown in Figure W.1. + +Decoders shall parse picture message data as required by basic PSUPP syntax, but decoder response to picture messages is otherwise undefined. + +### W.6.1 Continuation (CONT) (1 bit) + +If equal to "1", CONT indicates that the message data associated with this picture message function is part of the same logical message as the message data associated with the next picture message function. If equal to "0", CONT indicates that the message data associated with this picture message function terminates the current logical message. CONT may be used, for example, to represent logical messages that span more than 14 octets. + +### W.6.2 End Bit Position or Track Number (EBIT) (3 bits) + +For non-text picture messages, EBIT specifies the number of least significant bits that shall be ignored in the last message octet. In non-text picture messages, if CONT is "1", or if there is only one message octet (i.e., the octet in Figure W.1), EBIT shall equal "0". The number of valid message bits for a non-text picture message function excluding the CONT/EBIT/MTYPE bits is + +equal to $(DSIZE - 1) \times 8 - EBITS$ . The number of valid message bits for a logical message may be greater due to continuation. + +For picture message types containing text information, EBIT shall contain a text track number. The precise meaning of the text track number is not specified herein, but should indicate a particular type (e.g., language) for the text. Track number zero should be considered the default track. + +### **W.6.3 Message Type (MTYPE) (4 bits)** + +MTYPE indicates the type of message. The defined types are shown in Table W.2. + +**Table W.2/H.263 – MTYPE message type values** + +| | | +|--------|-----------------------------------------------| +| 0 | Arbitrary Binary Data | +| 1 | Arbitrary Text | +| 2 | Copyright Text | +| 3 | Caption Text | +| 4 | Video Description Text | +| 5 | Uniform Resource Identifier Text | +| 6 | Current Picture Header Repetition | +| 7 | Previous Picture Header Repetition | +| 8 | Next Picture Header Repetition, Reliable TR | +| 9 | Next Picture Header Repetition, Unreliable TR | +| 10 | Top Interlaced Field Indication | +| 11 | Bottom Interlaced Field Indication | +| 12 | Picture Number | +| 13 | Spare Reference Pictures | +| 14..15 | Reserved | + +#### **W.6.3.1 Arbitrary binary data** + +Arbitrary binary data is used to convey any non-ISO/IEC 10646 UTF-8 coded binary message. The interpretation of contents of the arbitrary binary data are outside the scope of this Recommendation, but should begin with some identifying pattern (e.g., a four-octet identifier code) to aid in distinguishing one type of such data from others. + +#### **W.6.3.2 Arbitrary text** + +Arbitrary text is used to convey a generic ISO/IEC 10646 UTF-8 coded text message. More specific text messages such as copyright information should be represented with other message types (e.g., copyright text) as appropriate. + +#### **W.6.3.3 Copyright text** + +Copyright text shall be used only to convey intellectual property information regarding the source or the encoded representation in the bitstream. The copyright message shall be coded according to ISO/IEC 10646 UTF-8. + +#### **W.6.3.4 Caption text** + +Caption text shall be used only to convey caption information associated with the current and subsequent pictures of the bitstream. The caption message shall be coded according to ISO/IEC 10646 UTF-8. The caption text shall be inserted in the bitstream as if it were to be displayed in a separate text area where new text is appended at the end of previous text and earlier text scrolled + +away from the point of insertion. The Form Feed (hexadecimal "0x000C") control code shall be used to indicate clearing of the visible text area. The End of Medium (hexadecimal "0x0019") control code shall be used to indicate "caption off" status. However, this Recommendation puts no restriction on how caption text is actually displayed and stored. + +#### **W.6.3.5 Video description text** + +Video description text shall be used only to convey descriptive information associated with the information contents of the current bitstream. The video description shall be coded according to ISO/IEC 10646 UTF-8. The video description text shall be inserted in the bitstream as if it were to be displayed in a separate text area where new text is appended at the end of previous text and earlier text scrolled away from the point of insertion. The Form Feed (hexadecimal "0x000C") control code shall be used to indicate clearing of the visible text area. The End of Medium (hexadecimal "0x0019") control code shall be used to indicate "description off" status. However, this Recommendation puts no restriction on how video description text is actually displayed and stored. + +#### **W.6.3.6 Uniform Resource Identifier (URI) text** + +The message consists of a uniform resource identifier (URI), as defined in IETF RFC 2396. The URI shall be coded according to ISO/IEC 10646 UTF-8. + +#### **W.6.3.7 Current picture header repetition** + +The picture header from the current picture is repeated in this message. The repeated bits exclude any supplemental enhancement information (PEI/PSUPP). All other bits up to the GOB or Slice layer should be included, subject to the limitations of W.4. + +#### **W.6.3.8 Previous picture header repetition** + +The picture header from the previously transmitted picture is repeated in this message. The repeated bits exclude the first two bytes of picture start code (PSC) and any supplemental enhancement information (PEI/PSUPP). All other bits up to the GOB or Slice layer should be included, subject to the limitations of W.4. + +#### **W.6.3.9 Next picture header repetition, reliable TR** + +The picture header from the next picture to be transmitted is repeated in this message. The repeated bits exclude the first two bytes of picture start code (PSC) and any supplemental enhancement information (PEI/PSUPP). All other bits up to the GOB or Slice layer should be included, subject to the limitations of W.4. + +#### **W.6.3.10 Next picture header repetition, unreliable TR** + +The picture header from the next picture to be transmitted is repeated in this message. The repeated bits exclude the first three bytes of picture header and any supplemental enhancement information (PEI/PSUPP). All other bits up to the GOB or Slice layer should be included, subject to the limitations of W.4. Any TR or ETR bits in the repeated picture header are not necessarily the same as the corresponding bits in the next picture header. + +#### **W.6.3.11 Interlaced field indications** + +In the case of interlaced field indications, the message consists of an indication of interlaced field coding. This indication does not affect the decoding process. However, it indicates that the current picture was not actually scanned as a progressive-scan picture. In other words, it indicates that the current coded picture contains only half of the lines of the full resolution source picture. DSIZE shall be 1, CONT shall be 0, and EBIT shall be 0 for interlaced field indications. In the case of interlaced field coding, each increment of the temporal reference denotes the time between the sampling of alternate half-picture fields of a picture, rather than the time between two complete + +pictures. In the case of a top interlaced field indication, the current picture contains the first (i.e., top), third, fifth, etc. lines of the complete picture. In the case of a bottom interlaced field indication, the current picture contains the second, fourth, sixth, etc. lines of the complete picture. When sending interlaced field indications, an encoder shall conform to the following conventions: + +- 1) The encoder shall use a picture clock frequency (custom picture clock frequency, if necessary) such that each new field of the original source video corresponds to an increment of 1 in the temporal reference. +- 2) The encoder shall use a picture size (custom picture size, if necessary) such that the picture dimensions correspond to those of a single field. +- 3) The encoder shall use a pixel aspect ratio (custom pixel aspect ratio, if necessary) such that the full-height picture aspect ratio corresponds to the picture aspect ratio derived from the pixel aspect ratio of the single field represented by the current encoded picture. + +Interlaced field scanning was introduced originally as an analog video compression technique. Although progressive picture scanning is generally regarded as superior for digital compression and display, the use of interlaced field scanning has persisted in many camera and display designs. Interlaced field coding (which can be implemented with lower delay than either interlaced full-picture coding or progressive-scan picture coding at half the interlaced field rate) is therefore supported by the indications herein. + +An encoder shall not send interlaced field indications unless the capability of the decoder to receive and properly process such field-based pictures has been established by external means (for example, ITU-T Rec. H.245). Failure to establish such a decoder capability may produce a visually annoying small-amplitude vertical shaking behaviour in the decoded picture received and displayed by a decoder. + +For example, an encoder may use interlaced field coding with application of the Reference Picture Selection mode (specified in Annex N) or the Enhanced Reference Picture Selection mode (specified in Annex U) to allow the addressing of more than one prior field. For "525/60" interlaced field coding for a 4:3 picture aspect ratio with 704 coded luminance samples per line and 240 coded luminance lines per field, the encoder shall use a custom picture size having a picture width of 704 and a picture height of 240, a custom pixel aspect ratio of 5:11, and a custom picture clock frequency specified with a clock conversion code "1" and a clock divisor of 30. For "625/50" interlaced field coding for a 4:3 picture aspect ratio with 704 coded luminance samples per line and 288 coded luminance lines per field, the encoder shall use a custom picture size having a picture width of 704 and a picture height of 288, a custom pixel aspect ratio of 6:11, and a custom picture clock frequency specified with a clock conversion code "0" and a clock divisor of 36. + +The vertical sampling positions of the chrominance samples in interlaced field coding of a top field picture are specified as shifted up by 1/4 luminance sample height relative to the field sampling grid in order for these samples to align vertically to the usual position relative to the full-picture sampling grid. The vertical sampling positions of the chrominance samples in interlaced field coding of a bottom field picture are specified as shifted down by 1/4 luminance sample height relative to the field sampling grid in order for these samples to align vertically to the usual position relative to the full-picture sampling grid. The horizontal sampling positions of the chrominance samples are specified as unaffected by the application of interlaced field coding. The vertical sampling positions are shown with their corresponding temporal sampling positions in Figure W.2. + +![Diagram showing vertical and temporal alignment of chrominance samples for interlaced field coding. It features three columns: Top Field, Bottom Field, and Top Field. A horizontal arrow at the bottom indicates the progression of Time. The legend indicates that an 'X' represents a Luminance Sample and an 'O' represents a Chrominance Sample. The diagram shows the temporal sequence of these samples across multiple fields.](39729be7ec83c3de8e480061966e4505_img.jpg) + +Top Field    Bottom Field    Top Field + +X                                    X + O                                    O +           X + X                                    X +           O +           X + X                                    X + O                                    O +           X + X                                    X +           O +           X + +→ Time + +X Luminance Sample + O Chrominance Sample + +T1608800-00 + +Diagram showing vertical and temporal alignment of chrominance samples for interlaced field coding. It features three columns: Top Field, Bottom Field, and Top Field. A horizontal arrow at the bottom indicates the progression of Time. The legend indicates that an 'X' represents a Luminance Sample and an 'O' represents a Chrominance Sample. The diagram shows the temporal sequence of these samples across multiple fields. + +**Figure W.2/H.263 – Vertical and temporal alignment of chrominance samples for interlaced field coding** + +### W.6.3.12 Picture number + +This message shall not be used if Annex U is in use. The message contains two data bytes that carry a 10-bit Picture Number. Consequently, DSIZE shall be 3, CONT shall be 0, and EBIT shall be 6. Picture Number shall be incremented by 1 for each coded and transmitted I or P picture or PB or Improved PB frame, in a 10-bit modulo operation. For EI and EP pictures, Picture Number shall be incremented for each EI or EP picture within the same scalability enhancement layer. For B pictures, Picture Number shall be incremented relative to the value in the most recent non-B picture in the reference layer of the B picture which precedes the B picture in bitstream order (a picture which is temporally subsequent to the B picture). If adjacent pictures in the same enhancement layer have the same temporal reference, and if the reference picture selection mode (see Annex N) is in use, the decoder shall regard this occurrence as an indication that redundant copies have been sent of approximately the same pictured scene content, and all of these pictures shall share the same Picture Number. If the difference (modulo 1024) of the Picture Numbers of two consecutively received non-B pictures in the same enhancement layer is not 1, and if the pictures do not represent approximately the same pictured scene content as described above, the decoder should infer a loss of pictures or corruption of data. + +### W.6.3.13 Spare reference pictures + +Encoders can use this message to instruct decoders which pictures resemble the current motion compensation reference picture so well that one of them can be used as a spare reference picture if the actual reference picture is lost during transmission. If a decoder lacks an actual reference picture but can access a spare reference picture, it should not request for an INTRA picture update. It is up to encoders to choose the spare reference pictures, if any. The message data bytes contain the + +Picture Numbers of the spare reference pictures in preference order (the most preferred appearing first). Picture Numbers refer to the values that are transmitted according to Annex U or W.6.3.12. This message can be used for P, B, PB, Improved PB, and EP picture types. However, if Annex N or Annex U is in use and if the picture is associated with multiple reference pictures, this message shall not be used. For EP pictures, the message shall be used only for forward prediction, whereas upward prediction is always done from the temporally corresponding reference layer picture. For B, PB, and Improved PB picture types, it specifies a picture for use as a forward motion prediction reference. This message shall not be used if the picture is an I or EI picture. + +## Annex X + +### Profiles and levels definition + +#### X.1 Scope + +With the variety of optional modes available in this Recommendation, it is crucial that several preferred mode combinations for operation be defined, so that option-enhanced terminals will have a high probability of connecting to each other using some syntax better than the "baseline". This annex contains a list of preferred feature combinations, which are structured into "profiles" of support. It also defines some groupings of maximum performance parameters as "levels" of support for these profiles. The primary objectives of this annex are: + +- 1) to provide a simple means of describing or negotiating the capabilities of a decoder (by specifying profile and level parameters); +- 2) to encourage common enhancement features to be supported in decoders for achieving maximal interoperability; and +- 3) to describe feature sets chosen as particularly appropriate for addressing certain key applications. + +The profiles and levels are defined in the following clauses and in Tables X.1 and X.2. The minimum picture interval as specified in Table X.2 is the minimum difference in time between the decoding of consecutive pictures in the bitstream. Support of any level other than level 45 implies support of all lower levels. Support of level 45 implies support of level 10. + +#### X.2 Profiles of preferred mode support + +The profiles of support are defined by the set of features supported in the decoder for each profile. Decoder support for a given profile implies support for all valid subset combinations of the constituent modes of that profile. This requirement exists so that the limitations placed upon an encoder's choice of mode combinations are minimized. This is in keeping with the primary objective of this annex, which is to describe which optional modes should be supported at the decoder to address key applications, rather than to enforce a particular small set of mode combinations upon the encoder. + +##### X.2.1 The Baseline Profile (Profile 0) + +The Baseline Profile, designated as Profile 0, is defined herein to provide a profile designation for the minimal "baseline" capability of this Recommendation. "Baseline" refers to the syntax of this Recommendation with no optional modes of operation. This profile of support is composed of only the baseline design. + +## X.2.2 H.320 Coding Efficiency Version 2 Backward-Compatibility Profile (Profile 1) + +The H.320 Coding Efficiency Version 2 Backward Compatibility Profile, designated as Profile 1, is defined herein to provide compatibility with a feature set adopted into the H.242 capability exchange mechanism for use by H.320 circuit-switched terminal systems. It provides basic enhanced coding efficiency and simple enhanced functionality within the feature set available in the second version of this Recommendation (which did not include Annexes U, V and W). This profile of support is composed of the baseline design plus the following modes: + +- 1) **Advanced INTRA Coding (Annex I)** – Use of this mode improves the coding efficiency for INTRA macroblocks (whether within INTRA pictures or predictively-coded pictures). The additional computational requirements of this mode are minimal at both the encoder and decoder (as low as a maximum of 8 additions/subtractions per $8 \times 8$ block in the decoding process plus the use of a different but very similar VLC table in order to obtain a significant improvement in coding efficiency). For these reasons, Advanced INTRA Coding is included in this basic package of support. +- 2) **Deblocking Filter (Annex J)** – Because of the significant subjective quality improvement that may be realized with a deblocking filter, these filters are widely in use as a method of post-processing in video communication terminals. Annex J represents the preferred mode of operation for a deblocking filter because it places the filter within the coding loop. This placement eases the implementation of the filter (by reducing the required memory) and somewhat improves the coding performance over a post-processing implementation. As with the Advanced Prediction mode, this mode also includes the four-motion-vector-per-macroblock feature and picture boundary extrapolation for motion compensation, both of which can further improve coding efficiency. The computational requirements of the deblocking filter are several hundred operations per coded macroblock, but memory accesses and computational dependencies are uncomplicated. This last point is what makes the Deblocking Filter preferable to Advanced Prediction for some implementations. Also, the benefits of Advanced Prediction are not as substantial when the Deblocking Filter is used as well. Thus, the Deblocking Filter is included in this basic package of support. +- 3) **Full-Picture Freeze Supplemental Enhancement Information (Annex L, clause L.4)** – The full-picture freeze is very simple to implement, requiring only that the decoder be able to stop the transfer of new pictures from its output buffer to the video display. This capability is useful for preventing the display of low-fidelity pictures while the encoder is building up a higher fidelity picture. +- 4) **Modified Quantization (Annex T)** – This mode includes an extended DCT coefficient range, modified DQUANT syntax, and a modified step size for chrominance. The first two features allow for more flexibility at the encoder and may actually decrease the encoder's computational load (by eliminating the need re-encode macroblocks when coefficient level saturation occurs). The third feature noticeably improves chrominance fidelity, typically with little added bit-rate cost and with virtually no increase in computation. At the decoder, the only significant added computational burden is the ability to parse some new bitstream symbols. + +## X.2.3 Version 1 Backward-Compatibility Profile (Profile 2) + +The Version 1 Backward-Compatibility Profile, designated as Profile 2, is defined herein to provide enhanced coding efficiency performance within the feature set available in the first version of ITU-T Rec. H.263 (which did not include Supplemental Enhancement Information or any of the optional features which use PLUSPTYPE). This profile of support is composed of the baseline design plus the following single mode: + +- 1) **Advanced Prediction (Annex F)** – From a coding efficiency standpoint, this mode is the most important of the modes available in the first version (Version 1) of this Recommendation. It includes overlapped block motion compensation, the four-motion-vector-per-macroblock feature, and it allows for motion vectors to point outside of the picture boundaries. The use of Advanced Prediction results in significant improvements in both subjective and objective performance. It does, however, require an appreciable increase in computation and introduces complicating data dependencies in the order of processing at the decoder. However, since implementations of this Recommendation that were designed prior to the adoption of the other modes in this list might have implemented Advanced Prediction by itself, Advanced Prediction-only operation is recommended for maximal quality with backward compatibility to version 1 decoders. + +#### **X.2.4 Version 2 Interactive and Streaming Wireless Profile (Profile 3)** + +The Version 2 Interactive and Streaming Wireless Profile, designated as Profile 3, is defined herein to provide enhanced coding efficiency performance and enhanced error resilience for delivery to wireless devices within the feature set available in the second version of this Recommendation (which did not include Annexes U, V, and W). This profile of support is composed of the baseline design plus the following modes: + +- 1) **Advanced INTRA Coding (Annex I)** – See X.2.2 item 1. +- 2) **Deblocking Filter (Annex J)** – See X.2.2 item 2. +- 3) **Slice Structured Mode (Annex K)** – The Slice Structured mode is included here due to its enhanced ability to provide resynchronization points within the video bitstream for recovery from erroneous or lost data. Support for the Arbitrary Slice Ordering (ASO) and Rectangular Slice (RS) submodes of the Slice Structured mode are not included in this profile, in order to limit the complexity requirements of the decoder. The additional computational burden imposed by the Slice Structured mode is minimal, limited primarily to bitstream generation and parsing. +- 4) **Modified Quantization (Annex T)** – See X.2.2 item 4. + +#### **X.2.5 Version 3 Interactive and Streaming Wireless Profile (Profile 4)** + +The Version 3 Interactive and Streaming Wireless Profile, designated as Profile 4, is defined herein to provide enhanced coding efficiency performance and enhanced error resilience for delivery to wireless devices, while taking advantage of the enhanced features of the third version of this Recommendation. This profile of support is composed of the baseline design, plus the following additional features as follows: + +- 1) **Profile 3** – This feature set provides several enhancements useful for support of wireless video transmission. +- 2) **Data Partitioned Slice Mode (Annex V)** – This feature enhances error resilience performance by separating motion vector data from DCT coefficient data within slices, and protects the motion vector information (the most important part of the detailed macroblock data) by using reversible variable-length coding. Support of the Arbitrary Slice Ordering (ASO) and Rectangular Slice (RS) submodes are not included in this profile, in order to limit the complexity requirements of the decoder. +- 3) **Previous Picture Header Repetition Supplemental Enhancement Information (Annex W, clause W.6.3.8)** – This feature allows the decoder to receive and recover the header information from a previous picture in case of data loss or corruption. + +## X.2.6 Conversational High Compression Profile (Profile 5) + +The Conversational High Compression Profile, designated as Profile 5, is defined herein to provide enhanced coding efficiency performance without adding the delay associated with the use of B pictures and without adding error resilience features. This profile of support is composed of the baseline design, plus the following additional features as follows: + +- 1) **Profile 1** – This feature set provides several enhancements useful for enhanced coding efficiency. +- 2) **Profile 2** – This profile adds the Advanced Prediction mode (Annex F), which provides a further enhancement of coding efficiency performance and backward-compatibility with implementations of the first version of this Recommendation. +- 3) **Unrestricted Motion Vectors with UUI = "1" (Annex D)** – Annex D has two primary features: + - a) picture boundary extrapolation; and + - b) longer motion vector support.The first of these features is already supported by the inclusion of Annex J in Profile 1. The longer motion vector support can provide a significant improvement in coding efficiency, especially for large picture sizes, rapid motion, camera movement, and low picture rates. When used with PLUSPTYPE present, this mode also allows for longer motion vector differences, which can significantly simplify encoder operation. The longer motion vectors do present a potential problem for the decoder in terms of memory access, but picture-size-dependent limits on the maximum motion vector size prevent this problem from becoming an appreciable obstacle to implementation. +- 4) **Enhanced Reference Picture Selection (Annex U)** – This mode adds a significant gain in compression efficiency performance due to the ability to use multiple prior pictures as reference data for macroblock-level prediction of the subsequent pictures. The Sub-Picture Removal submode (Annex U, clause U.4.3) of the Enhanced Reference Picture Selection mode is not included in Profile 5. + +## X.2.7 Conversational Internet Profile (Profile 6) + +The Conversational Internet Profile, designated as Profile 6, is defined herein to provide enhanced coding efficiency performance without adding the delay associated with the use of B pictures, but adding some error resilience suitable for use on Internet Protocol (IP) networks (which use packet-based data protocols with relatively large packets and which exhibit data losses rather than data corruption). This profile of support is composed of the baseline design, plus the following additional features as follows: + +- 1) **Profile 5** – This feature set provides several enhancements useful for enhanced coding efficiency. +- 2) **Slice Structured mode (Annex K) with Arbitrary Slice Ordering (ASO) submode** – The Slice Structured mode is included here due to its enhanced ability to provide resynchronization points within the video bitstream for recovery from lost data packets. The Arbitrary Slice Ordering (ASO) submode of the Slice Structured mode is also included in order to allow for interleaved packetization for motion-compensated error concealment and for out-of-sequence data reception. Support for the Rectangular Slice (RS) submode of the Slice Structured mode is not included in this profile, in order to limit the complexity requirements of the decoder. The additional computational burden imposed by the Slice Structured mode is minimal, limited primarily to bitstream generation and parsing. + +### **X.2.8 Conversational Interlace Profile (Profile 7)** + +The Conversational Interlace Profile, designated as Profile 7, is defined herein to provide enhanced coding efficiency performance for low-delay applications, plus support of interlaced video sources. This profile of support is composed of the baseline design, plus the following additional features as follows: + +- 1) **Profile 5** – This feature set provides several enhancements useful for enhancing coding efficiency without adding delay. +- 2) **Interlaced Field Indications For 240-line and 288-line Pictures (Annex W, clause W.6.3.11)** – This feature allows video to be sent in an interlaced source picture format for compatibility with existing camera designs. + +### **X.2.9 High Latency Profile (Profile 8)** + +The High Latency Profile, designated as Profile 8, is defined herein to provide enhanced coding efficiency performance for applications without critical delay constraints. This profile of support is composed of the baseline design, plus the following additional features as follows: + +- 1) **Profile 6** – This feature set provides several enhancements useful for enhanced coding efficiency and robustness to data losses. +- 2) **Reference Picture Resampling (Implicit Factor-of-4 Mode Only) (Annex P, clause P.5)** – The implicit factor-of-4 mode of Reference Picture Resampling allows for automatic reference picture resampling only when the size of the new frame is changed, as indicated in the picture header. No bitstream overhead is required for this mode of operation. Predictive dynamic resolution changes allow an encoder to make intelligent trade-offs between temporal and spatial resolution. Furthermore, this simplest mode of operation for Annex P (factor-of-4 upsampling or downsampling only) adds only a modest amount of computational complexity to both the encoder or decoder, since the factor-of-4 case uses a simple fixed FIR filter (requiring roughly 4 operations per pixel, at most). +- 3) **B Pictures (Temporal Scalability, Annex O, clause O.1.1)** – This feature consists of B pictures, which are pictures allowing bidirectional temporal prediction. The addition of B pictures enhances coding efficiency performance, but at some cost in added processing power and encoding and decoding delay. The two-picture backward prediction submode for B pictures in Enhanced Reference Picture Selection mode (Annex U, clause U.3.1.5.5) is not supported in Profile 8. + +## **X.3 Picture formats and picture clock frequencies** + +To ensure a high quality level of interoperability, encoders and decoders supporting a large standard picture format (QCIF, CIF, 4CIF, 16CIF) should support all smaller standard picture formats. This is a requirement of all decoders conforming to the profiles and levels defined in this annex. (As specified elsewhere in this Recommendation, decoders shall support sub-QCIF and QCIF, and encoders shall support sub-QCIF or QCIF.) For example, a decoder conforming to a profile and level defined in this annex which is capable of decoding 4CIF pictures shall also support the decoding of CIF pictures. + +Decoders should be capable of operation with a smaller picture format at maximum picture rates no lower than the maximum picture rate for which it is capable of operation with a larger standard picture format. This is a requirement of all decoders conforming to the profiles and levels defined in this annex. For example, a decoder conforming to a profile and level defined in this annex which is capable of decoding 4CIF pictures at 25 pictures per second shall also be able to decode CIF, QCIF and SQCIF pictures at least at 25 pictures per second. + +Encoders and decoders supporting custom picture formats and/or custom picture clock frequencies are recommended to follow the rules defined in this paragraph. These rules are requirements of all decoders conforming to the profiles and levels defined in this annex: + +- 1) A decoder for any profile and level defined herein that supports a maximum picture format shall support all standard picture formats smaller or equal in both height and width than those of the maximum supported picture format. For example, a decoder supporting a custom picture format of $720 \times 288$ shall support CIF, QCIF and sub-QCIF picture decoding. +- 2) A decoder for any profile and level defined herein that supports custom picture formats shall support all standard or custom picture formats having both height and width smaller than or equal to those of the maximum supported picture format. +- 3) A decoder for any profile and level defined herein that supports a minimum picture interval with the standard picture clock frequency of $(30\,000)/1001$ units per second shall support the same or smaller minimum picture interval for all supported picture formats having both height and width smaller than or equal to those of the maximum picture format at which the minimum picture interval is specified. +- 4) A decoder for any profile and level defined herein that supports a minimum picture interval and supports custom picture clock frequencies shall support the use of any picture clock frequency with the same or larger picture interval for all supported picture formats having both height and width smaller than or equal to those of the maximum picture format at which the minimum picture interval is specified. + +#### X.4 Levels of performance capability + +Eight levels of performance capability are defined for decoder implementation. The Hypothetical Reference Decoder has the minimal size specified in Table X.1 for all levels of Profiles 0 through 4. In Profiles 5 though 8 the Hypothetical Reference Decoder has an increased size and Enhanced Reference Picture Selection is supported with multiple reference pictures. Table X.2 defines the detailed performance parameters of each of these levels: + +- 1) **Level 10** – Support of QCIF and sub-QCIF resolution decoding, capable of operation with a bit rate up to $64\,000$ bits per second with a picture decoding rate up to $(15\,000)/1001$ pictures per second. +- 2) **Level 20** – Support of CIF, QCIF and sub-QCIF resolution decoding, capable of operation with a bit rate up to $2 \cdot (64\,000) = 128\,000$ bits per second with a picture decoding rate up to $(15\,000)/1001$ pictures per second for CIF pictures and $(30\,000)/1001$ pictures per second for QCIF and sub-QCIF pictures. +- 3) **Level 30** – Support of CIF, QCIF and sub-QCIF resolution decoding, capable of operation with a bit rate up to $6 \cdot (64\,000) = 384\,000$ bits per second with a picture decoding rate up to $(30\,000)/1001$ pictures per second. +- 4) **Level 40** – Support of CIF, QCIF and sub-QCIF resolution decoding, capable of operation with a bit rate up to $32 \cdot (64\,000) = 2\,048\,000$ bits per second with a picture decoding rate up to $(30\,000)/1001$ pictures per second. +- 4.5) **Level 45** – Support of QCIF and sub-QCIF resolution decoding, capable of operation with a bit rate up to $2 \cdot (64\,000) = 128\,000$ bits per second with a picture decoding rate up to $(15\,000)/1001$ pictures per second. Additionally, in profiles other than profiles 0 and 2, support of custom picture formats of size QCIF and smaller. +- 5) **Level 50** – Support of custom and standard picture formats of size CIF and smaller, capable of operation with a bit rate up to $64 \cdot (64\,000) = 4\,096\,000$ bits per second with a picture decoding rate up to 50 pictures per second for CIF or smaller picture formats and up to $(60\,000)/1001$ pictures per second for $352 \times 240$ and smaller picture formats. + +- 6) **Level 60** – Support of custom and standard picture formats of size $720 \times 288$ and smaller, capable of operation with a bit rate up to $128 \cdot (64\,000) = 8\,192\,000$ bits per second with a picture decoding rate up to 50 pictures per second for $720 \times 288$ or smaller picture formats and up to $(60\,000)/1001$ pictures per second for $720 \times 240$ and smaller picture formats. +- 7) **Level 70** – Support of custom and standard picture formats of size $720 \times 576$ and smaller, capable of operation with a bit rate up to $256 \cdot (64\,000) = 16\,384\,000$ bits per second with a picture decoding rate up to 50 pictures per second for $720 \times 576$ or smaller picture formats and up to $(60\,000)/1001$ pictures per second for $720 \times 480$ and smaller picture formats. + +The bit rate at which a particular profile and level are used in a system shall never exceed that specified in this annex. However, particular systems may include other means to signal further limits on the bit rate. Other aspects of profile and level capabilities may also be subject to additional capability restrictions when used in particular systems, but the capabilities required for decoding any bitstream for a particular profile and level defined herein shall never exceed those specified in this annex. + +**Table X.1/H.263 – Summary of profiles** + +| Annex/clause below for profile listed at the right | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|---|---| +| 5.1.5: Custom Picture Format (CPFMT) | L | L | L | L | L | L | L | L | L | +| 5.1.7: Custom Picture Clock Frequency Code (CPCFC) | L | L | L | L | L | L | L | L | L | +| C: Continuous Presence Multipoint and Video Mux | | | | | | | | | | +| D.1: Motion vectors over picture boundaries | | X | X | X | X | X | X | X | X | +| D.2 with UUI = '1' or UUI not present: Extension of the motion vector range | | | | | | X | X | X | X | +| D.2 with UUI = '01': Unlimited extension of the motion vector range | | | | | | | | | | +| E: Syntax-based Arithmetic Coding | | | | | | | | | | +| F.2: Four motion vectors per macroblock | | X | X | X | X | X | X | X | X | +| F.3: Overlapped block motion compensation | | | X | | | X | X | X | X | +| G: PB-Frames | | | | | | | | | | +| H: Forward Error Correction (use may be imposed at system level as in ITU-T Rec. H.320) | | | | | | | | | | +| I: Advanced Intra Coding | | X | | X | X | X | X | X | X | +| J: Deblocking Filter | | X | | X | X | X | X | X | X | +| K without submodes: Slice Structured Coding – Without submodes | | | | X | X | | X | | X | +| K with ASO: Slice Structured Coding – With Arbitrary Slice Ordering submode | | | | | | | X | | X | +| K with RS: Slice Structured Coding – With Rectangular Slice submode | | | | | | | | | | +| L.4: Supplemental Enhancement Full picture freeze | | X | | | | X | X | X | X | +| L: Supplemental Enhancement – Other SEI features | | | | | | | | | | +| M: Improved PB-Frames | | | | | | | | | | +| N: Reference Picture Selection (and submodes) | | | | | | | | | | +| O.1.1 Temporal (B pictures): Temporal, SNR, and Spatial Scalability – B pictures for Temporal Scalability | | | | | | | | | X | + +**Table X.1/H.263 – Summary of profiles** + +| Annex/clause below for profile listed at the right | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|---|---| +| O SNR and Spatial: Temporal, SNR, and Spatial Scalability – EI and EP pictures for SNR and Spatial Scalability | | | | | | | | | | +| P.5: Reference Picture Resampling – Implicit Factor of Four | | | | | | | | | X | +| P: Reference Picture Resampling – More General Resampling | | | | | | | | | | +| Q: Reduced Resolution Update | | | | | | | | | | +| R: Independent Segment Decoding | | | | | | | | | | +| S: Alternative Inter VLC | | | | | | | | | | +| T: Modified Quantization | | X | | X | X | X | X | X | X | +| U without submodes: Enhanced Reference Picture Selection – Without submodes | | | | | | X | X | X | X | +| U with SPR: Enhanced Reference Picture Selection – With Sub-Picture Removal submode | | | | | | | | | | +| U with BTPSM: Enhanced Reference Picture Selection – With B-Picture Two-Picture submode | | | | | | | | | | +| V: Data Partitioned Slices | | | | | X | | | | | +| W.6.3.8: Additional SEI Specification – Prior Picture Header Repetition | | | | | X | | | | | +| W.6.3.11: Additional SEI Specification – Interlaced Field Indications | | | | | | | | X | | +| W: Additional SEI Specification – Other SEI features | | | | | | | | | | +| "X" indicates that support of a feature is part of a profile. | | | | | | | | | | +| "L" indicates that the inclusion of a feature depends on the level within the profile. | | | | | | | | | | + +**Table X.2/H.263 – Levels of operation** + +| Parameter below for level listed at the right | 10 | 20 | 30 | 40 | 45 | 50 | 60 | 70 | +|-----------------------------------------------|-----------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| Max picture format | QCIF (176 × 144) | CIF (352 × 288) | CIF (352 × 288) | CIF (352 × 288) | QCIF (176 × 144) support of CPFMT in profiles other than 0 and 2 | CIF (352 × 288) support of CPFMT | CPFMT: 720 × 288 support of CPFMT | CPFMT: 720 × 576 support of CPFMT | +| Min picture interval | 2002/(30 000) s | 2002/(30 000) s for CIF
1001/(30 000) s for QCIF and sub-QCIF | 1001/(30 000) s | 1001/(30 000) s | 2002/(30 000) s
support of CPCFC in profiles other than 0 and 2 | 1/50 s at CIF or lower
1001/(60 000) s at 352 × 240 or smaller
support of CPCFC | 1/50 s at 720 × 288 or lower
1001/(60 000) s at 720 × 240 or smaller
support of CPCFC | 1/50 s at 720 × 576 or lower
1001/(60 000) s at 720 × 480 or smaller
support of CPCFC | +| Max bit rate in 64 000 bits/s units | 1 | 2 | 6 | 32 | 2 | 64 | 128 | 256 | +| Max HRD B in 16 384 bit units | 1: Prof. 5-8 | 2: Prof. 5-8 | 6: Prof. 5-8 | 32: Prof. 5-8 | 2: Prof. 5-8 | 64: Prof. 5-8 | 64: Prof. 5-8 | 256: Prof. 5-8 | +| Max BPPmaxKb in 1024 bit units | 128: Prof. 5-8 | 512: Prof. 5-8 | 512: Prof. 5-8 | 512: Prof. 5-8 | 128: Prof. 5-8 | 512: Prof. 5-8 | 1024: Prof. 5-8 | 1024: Prof. 5-8 | +| Max ERPS reference pictures (Annex U) | 5: Prof. 5-7
10: Prof. 8 | 5: Prof. 5-7
10: Prof. 8 multiplied by 2 for QCIF or sub-QCIF in Prof. 5-8 | 5: Prof. 5-7
10: Prof. 8 multiplied by 2 for QCIF or sub-QCIF in Prof. 5-8 | 5: Prof. 5-7
10: Prof. 8 multiplied by 2 for QCIF or sub-QCIF in Prof. 5-8 | 5: Prof. 5-7
10: Prof. 8 | 5: Prof. 5-7
10: Prof. 8 multiplied by 2 for QCIF or smaller in Prof. 5-8 | 5: Prof. 5-7
10: Prof. 8 multiplied by 2 for CIF or smaller, and by 4 for QCIF or smaller in Prof. 5-8 | 5: Prof. 5-7
10: Prof. 8 multiplied by 2 for CIF or smaller, and by 4 for QCIF or smaller in Prof. 5-8 | + +NOTE 1 – In profiles for which a maximum number of reference picture buffers is not specified in Table X.2, no support for multiple reference picture buffering is required. + +NOTE 2 – In profiles for which a maximum BPPmaxKb and HRD B are not specified in Table X.2, the minimum value specified in Table X.1 applies for the specified maximum bit rate and resolution. + +## X.5 Generic capability definitions for use with ITU-T Rec. H.245 + +Table X.3 defines a capability identifier for establishing H.263 capabilities for use in systems that use ITU-T Rec. H.245 for capability determination. These parameters shall only be included as **genericVideoCapability** within the **VideoCapability** structure and as **genericVideoMode** within the **VideoMode** structure of ITU-T Rec. H.245. Tables X.4 to X.14 define the associated capability parameters. + +When included in Logical Channel Signalling or Mode Request, exactly one parameter with Parameter identifier value in the range zero to eight shall be present; that is, only one profile shall be specified. + +**Table X.3/H.263 – Capability identifier for H.263 capability** + +| | | +|------------------------------|-------------------------------------------------------------------| +| Capability name: | H.263 | +| Capability class: | Video codec | +| Capability identifier type: | Standard | +| Capability identifier value: | itu-t (0) recommendation (0) h (8) 263 generic-capabilities (1) 0 | +| MaxBitRate: | The maxBitRate field shall always be included. | +| NonCollapsingRaw: | This field shall not be included. | +| Transport: | This field shall not be included. | + +**Table X.4/H.263 – The Baseline Profile (Profile 0) capability** + +| | | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | baselineProfile | +| Parameter description: | This is a collapsing GenericParameter.
baselineProfile indicates the maximum level of support for the Baseline Profile when present in Capability Exchange, the maximum level to be transmitted when present in Logical Channel Signalling, and the desired level when present in Mode Request. | +| Parameter identifier value: | 0 | +| Parameter status: | Mandatory | +| Parameter type: | unsignedMin | +| Supersedes: | – | + +**Table X.5/H.263 – H.320 Coding Efficiency Version 2 +Backward-Compatible Profile (Profile 1) capability** + +| | | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | h320Profile | +| Parameter description: | This is a collapsing GenericParameter.
h320Profile indicates the maximum level of support for the H.320 Coding Efficiency Version 2 Backward-Compatible Profile when present in Capability Exchange, the maximum level to be transmitted when present in Logical Channel Signalling, and the desired level when present in Mode Request. | +| Parameter identifier value: | 1 | +| Parameter status: | Optional | +| Parameter type: | unsignedMin | +| Supersedes: | – | + +**Table X.6/H.263 – Version 1 Backward-Compatible Profile (Profile 2) capability** + +| | | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | backwardCompatibleProfile | +| Parameter description: | This is a collapsing GenericParameter.
backwardCompatibleProfile indicates the maximum level of support for the Version 1 Backward-Compatible Profile when present in Capability Exchange, the maximum level to be transmitted when present in Logical Channel Signalling, and the desired level when present in Mode Request. | +| Parameter identifier value: | 2 | +| Parameter status: | Optional | +| Parameter type: | unsignedMin | +| Supersedes: | – | + +**Table X.7/H.263 – Version 2 Interactive and Streaming +Wireless Profile (Profile 3) capability** + +| | | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | v2WirelessProfile | +| Parameter description: | This is a collapsing GenericParameter.
v2WirelessProfile indicates the maximum level of support for the Version 2 Interactive and Streaming Wireless Profile when present in Capability Exchange, the maximum level to be transmitted when present in Logical Channel Signalling, and the desired level when present in Mode Request. | +| Parameter identifier value: | 3 | +| Parameter status: | Optional | +| Parameter type: | unsignedMin | +| Supersedes: | – | + +**Table X.8/H.263 – Version 3 Interactive and Streaming Wireless Profile (Profile 4) capability** + +| | | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | v3WirelessProfile | +| Parameter description: | This is a collapsing GenericParameter.
v3WirelessProfile indicates the maximum level of support for the Version 3 Interactive and Streaming Wireless Profile when present in Capability Exchange, the maximum level to be transmitted when present in Logical Channel Signalling, and the desired level when present in Mode Request. | +| Parameter identifier value: | 4 | +| Parameter status: | Optional | +| Parameter type: | unsignedMin | +| Supersedes: | – | + +**Table X.9/H.263 – Conversational High Compression Profile (Profile 5) capability** + +| | | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | conversationalProfile | +| Parameter description: | This is a collapsing GenericParameter.
conversationalProfile indicates the maximum level of support for the Conversational High Compression Profile when present in Capability Exchange, the maximum level to be transmitted when present in Logical Channel Signalling, and the desired level when present in Mode Request. | +| Parameter identifier value: | 5 | +| Parameter status: | Optional | +| Parameter type: | unsignedMin | +| Supersedes: | – | + +**Table X.10/H.263 – Conversational Internet Profile (Profile 6) capability** + +| | | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | conversationalInternetProfile | +| Parameter description: | This is a collapsing GenericParameter.
conversationalInternetProfile indicates the maximum level of support for the Conversational Internet Profile when present in Capability Exchange, the maximum level to be transmitted when present in Logical Channel Signalling, and the desired level when present in Mode Request. | +| Parameter identifier value: | 6 | +| Parameter status: | Optional | +| Parameter type: | unsignedMin | +| Supersedes: | – | + +**Table X.11/H.263 – Conversational Plus Interlace Profile (Profile 7) capability** + +| | | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | conversationalInterlaceProfile | +| Parameter description: | This is a collapsing GenericParameter.
conversationalInterlaceProfile indicates the maximum level of support for the Conversational Plus Interlace Profile when present in Capability Exchange, the maximum level to be transmitted when present in Logical Channel Signalling, and the desired level when present in Mode Request. | +| Parameter identifier value: | 7 | +| Parameter status: | Optional | +| Parameter type: | unsignedMin | +| Supersedes: | – | + +**Table X.12/H.263 – High Latency Profile (Profile 8) capability** + +| | | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | highLatencyProfile | +| Parameter description: | This is a collapsing GenericParameter.
highLatencyProfile indicates the maximum level of support for the High Latency Profile when present in Capability Exchange, the maximum level to be transmitted when present in Logical Channel Signalling, and the desired level when present in Mode Request. | +| Parameter identifier value: | 8 | +| Parameter status: | Optional | +| Parameter type: | unsignedMin | +| Supersedes: | – | + +**Table X.13/H.263 – Temporal Spatial Trade-Off capability** + +| | | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | temporalSpatialTradeOffCapability | +| Parameter description: | This is a collapsing GenericParameter.
The presence of this parameter indicates that the encoder is able to vary its trade-off between temporal and spatial resolution as commanded by the remote terminal. It has no meaning when part of a receive capability. | +| Parameter identifier value: | 9 | +| Parameter status: | Optional | +| Parameter type: | logical | +| Supersedes: | – | + +**Table X.14/H.263 – Video Bad Macroblocks capability** + +| | | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | videoBadMBsCap | +| Parameter description: | This is a collapsing GenericParameter.
The presence of this parameter indicates the capability of an encoder to receive or a decoder to transmit the videoBadMBs command. When part of a transmit capability, it indicates the ability of the encoder to process videoBadMBs commands and to take appropriate corrective action toward recovery of video quality. When part of a receive capability, it indicates the ability of the decoder to send appropriate videoBadMBs indications. | +| Parameter identifier value: | 10 | +| Parameter status: | Optional | +| Parameter type: | logical | +| Supersedes: | – | + +## Appendix I + +### Error tracking + +#### I.1 Introduction + +This appendix describes a method to recover efficiently after transmission errors if erroneous MBs are reported via a feedback channel to the encoder. The capability of sending and processing feedback information is signalled via external means (for example, by ITU-T Rec. H.245). Furthermore, format and content of the feedback message are defined externally (for example, by ITU-T Rec. H.245). + +#### I.2 Error tracking + +Because INTRA coding stops temporal error propagation, it should be used for macroblocks which are severely affected by transmission errors. This requires that the location and extent of image artefacts can be made available to the encoder. The following algorithm provides an estimated error distribution based on feedback information received by the encoder. It considers spatial error propagation caused by motion-compensated prediction as well as the delay until the reception of the feedback message. The algorithm illustrates one possible approach to evaluate feedback messages for spatio-temporal error tracking. Other algorithms are possible. + +Assume N macroblocks within each frame enumerated $mb = 1 \dots N$ from top-left to bottom-right. Let $\{n_{err}, mb_{first}, mb_{last}\}$ be the feedback message to the encoder, where $mb_{first} \leq mb \leq mb_{last}$ indicates a set of erroneous macroblocks in frame $n_{err}$ . + +To evaluate the feedback message, the encoder must continuously record information during the encoding of each frame. First, the initial error $E_0(mb, n)$ that would be introduced by the loss of macroblock $mb$ in frame $n$ needs to be stored. Assuming a simple error concealment where erroneous macroblocks are treated as not coded, $E_0(mb, n)$ is computed as the Summed Absolute Difference (SAD) of macroblock $mb$ in frame $n$ and $n - 1$ . Second, the number of pixels transferred from macroblock $mb_{source}$ in frame $n - 1$ to macroblock $mb_{dest}$ in frame $n$ is stored in dependencies $d(mb_{source}, mb_{dest}, n)$ . These dependencies are derived from the motion vectors. + +Assume that a feedback message arrives before frame $n_{\text{next}}$ is encoded, such that $n_{\text{next}} > n_{\text{err}}$ . Then, the estimated error $E(\text{mb}, n_{\text{err}})$ in macroblock $\text{mb}$ and frame $n_{\text{err}}$ is initialized as: + +$$E(\text{mb}, n_{\text{err}}) = \begin{cases} E_0(\text{mb}, n_{\text{err}}) & \text{for } \text{mb}_{\text{first}} \leq \text{mb} \leq \text{mb}_{\text{last}} \\ 0 & \text{else} \end{cases}$$ + +For subsequent frames $n$ , with $n_{\text{err}} < n < n_{\text{next}}$ , the error may be estimated as: + +$$E(\text{mb}, n) = \sum_{i=1}^N E(i, n-1) \frac{d(i, \text{mb}, n)}{256}$$ + +where a uniformly distributed error in each macroblock is assumed after each iteration. + +The estimated error $E(\text{mb}, n_{\text{next}} - 1)$ is incorporated into the mode decision of the next frame. For example, macroblock $\text{mb}$ is coded in INTRA mode, if $E(\text{mb}, n_{\text{next}} - 1)$ exceeds a threshold. + +In practice, error tracking information will only be stored for the latest $M$ frames. Then, if $n_{\text{err}} < n_{\text{next}} - M$ , no error-tracking information is available and the encoder must take special action. For example, the next frame may be coded in INTRA mode. However, other procedures are possible and may be more effective. + +## Appendix II + +### Recommended optional enhancement + +The content of the H.263 Appendix II approved in February 1998 has become obsolete after the approval of H.263 Annex X. Since this appendix is used as a reference by many users of ITU-T texts, this appendix is provided mainly as a reference for users unaware of the contents of H.263 Annex X. + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/raw.md b/marked/H/T-REC-H.264-202408-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b0ed5c84f5f4c39d2526f5c5ce5365732cd61e09 --- /dev/null +++ b/marked/H/T-REC-H.264-202408-I_PDF-E/raw.md @@ -0,0 +1,34700 @@ + + +# Recommendation + +# **ITU-T H.264 (V15) (08/2024)** + +SERIES H: Audiovisual and multimedia systems + +Infrastructure of audiovisual services – Coding of moving video + +--- + +## **Advanced video coding for generic audiovisual services** + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +## **Audiovisual and multimedia systems** + +| | | +|-------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| General | H.200-H.219 | +| Transmission multiplexing and synchronization | H.220-H.229 | +| Systems aspects | H.230-H.239 | +| Communication procedures | H.240-H.259 | +| Coding of moving video | H.260-H.279 | +| Related systems aspects | H.280-H.299 | +| Systems and terminal equipment for audiovisual services | H.300-H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350-H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360-H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420-H.439 | +| Supplementary services for multimedia | H.450-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Advanced video coding for generic audiovisual services + +# Summary + +Recommendation ITU-T H.264 | International Standard ISO/IEC 14496-10 represents an evolution of the existing video coding standards (ITU-T H.261, ITU-T H.262, and ITU-T H.263) and it was developed in response to the growing need for higher compression of moving pictures for various applications such as videoconferencing, digital storage media, television broadcasting, Internet streaming, and communication. It is also designed to enable the use of the coded video representation in a flexible manner for a wide variety of network environments. The use of this Recommendation | International Standard allows motion video to be manipulated as a form of computer data and to be stored on various storage media, transmitted and received over existing and future networks and distributed on existing and future broadcasting channels. + +The 1st edition of Rec. ITU-T H.264 was approved in 2003-05. + +Corrigendum 1 to the 1st version of Rec. ITU-T H.264, approved in 2004-05, included various minor corrections and clarifications. This corrigendum was never published independently, its content having been included in the 1st published edition. + +The 2nd edition of ITU-T H.264, approved in 2005-03, contained modifications of the video coding standard to add four new profiles, referred to as the High, High 10, High 4:2:2, and High 4:4:4 profiles, to improve video quality capability and to extend the range of applications addressed by the standard (for example, by including support for a greater range of picture sample precision and higher-resolution chroma formats). Additionally, a definition of new types of supplemental data was specified to further broaden the applicability of the video coding standard. Finally, a number of corrections to errors in the published text were included. + +Corrigendum 1 to the 2nd edition of Rec. ITU-T H.264, approved in 2005-09, corrected and updated various minor aspects to bring the ITU-T version of the text up to date relative to the 2005-04 output status approved as a new edition of the corresponding jointly-developed and technically-aligned text ISO/IEC 14496-10. It additionally fixed a number of minor errors and needs for clarification and defined three previously-reserved sample aspect ratio indicators. This corrigendum was never published independently, its content having been included in the 2nd published edition, which was published in 2005-11. + +Amendment 1, "Support of additional colour spaces and removal of the High 4:4:4 Profile", approved in 2006-06, contained alterations to Rec. ITU-T H.264 | ISO/IEC 14496-10, Advanced Video Coding, to specify the support of additional colour spaces and to remove the definition of the High 4:4:4 profile. + +Amendment 2, "New profiles for professional applications", approved in 2007-04, contained extensions to Rec. ITU-T H.264 | ISO/IEC 14496-10 Advanced Video Coding to specify the support of five additional profiles intended primarily for professional applications (the High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, CAVLC 4:4:4 Intra, and High 4:4:4 Predictive profiles) and two new types of supplemental enhancement information (SEI) messages (the post-filter hint SEI message and the tone mapping information SEI message). + +Amendment 3, "Scalable video coding", approved in 2007-11 in an integrated 3rd ITU-T H.264 edition, contained extensions to Rec. ITU-T H.264 | ISO/IEC 14496-10, Advanced Video Coding, to specify a scalable video coding extension in three profiles (the Scalable Baseline, Scalable High, and Scalable High Intra profiles). + +ITU-T H.264 (2005) Amd.2 (2007) was available only as pre-published text since it was superseded by ITU-T H.264 Amd.3 (2007-11) before its publication. Furthermore, ITU-T H.264 Amd.3 was not published separately. The changes introduced by the three amendments were integrated into the 3rd ITU-T H.264 edition, which was approved in 2007-11. + +Corrigendum 1 to the 2nd edition, approved in 2009-01, provided a significant number of minor corrections, clarifications, consistency improvements and formatting improvements drafted in response to accumulated errata reports collected since publication of the 2nd edition (dated 2005-03, which included a Cor.1 approved in 2005-09). + +The 4th edition of ITU-T H.264, approved in 2009-05, contained enhancement extensions to support multiview video coding (MVC), specification of a "Constrained Baseline Profile", and some miscellaneous corrections and clarifications. + +The 5th edition of ITU-T H.264, approved in 2010-03, contained the specification of a new profile (the Stereo High profile) for two-view video coding with support of interlaced coding tools, the specification a new SEI message (the frame packing arrangement SEI message), and some miscellaneous corrections and clarifications. + +The 6th edition of ITU-T H.264, approved in 2011-07, contained the specification of a new level (Level 5.2) supporting higher processing rates in terms of maximum macroblocks per second, a new profile (the Progressive High profile) to enable implementation of decoders supporting only the frame coding tools of the previously specified High profile, and included miscellaneous corrections and clarifications. + +The 7th edition of Rec. ITU-T H.264, approved in 2012-01, contained the specification of three additional profiles intended primarily for communication applications (the Constrained High, Scalable Constrained Baseline, and Scalable Constrained High profiles). + +The 8th edition of Rec. ITU-T H.264, approved in 2013-04, contained an additional profile for multiview video coding with depth information (the Multiview Depth High profile), and contained additional SEI message enhancements, additional colorimetry identifiers, and corrections and clarifications. + +The 9th edition of Rec. ITU-T H.264 approved in 2014-02 specified multi-resolution frame-compatible (MFC) enhancement for stereoscopic video coding, including the specification of an additional profile, the MFC High profile, an enhanced profile for combined multiview video coding with depth information (the Enhanced Multiview Depth High profile), and includes miscellaneous minor corrections and clarifications. + +The 10th edition of Rec. ITU-T H.264 approved in 2016-02 specified MFC stereoscopic video with depth maps, including the specification of an additional profile, the MFC Depth High profile, and the mastering display colour volume SEI message, additional colour-related video usability information codepoint identifiers, and miscellaneous minor corrections and clarifications. + +The 11th edition of Rec. ITU-T H.264, approved in 2016-10, specified additional levels of decoder capability supporting larger picture sizes (Levels 6, 6.1, and 6.2), the green metadata SEI message, the alternative depth information SEI message, additional colour-related video usability information codepoint identifiers, and miscellaneous minor corrections and clarifications. + +The 12th edition of Rec. ITU-T H.264, approved in 2017-04, specified the Progressive High 10 profile; support for additional colour-related indicators including the hybrid log-gamma transfer characteristics indication, the alternative transfer characteristics SEI message, the ICTCP colour matrix transformation, chromaticity-derived constant luminance and non-constant luminance colour matrix coefficients, the colour remapping information SEI message; and miscellaneous minor corrections and clarifications. + +The 13th edition of Rec. ITU-T H.264, approved in 2019-06, specified additional SEI messages for ambient viewing environment, content light level information, content colour volume, equirectangular projection, cubemap projection, sphere rotation, region-wise packing, omnidirectional viewport, SEI manifest, and SEI prefix, and miscellaneous minor corrections and clarifications. + +The 14th edition of Rec. ITU-T H.264, approved in 2021-08, specifies additional SEI messages for annotated regions and shutter interval information, and miscellaneous minor corrections and clarifications. + +The 15th edition of Rec. ITU-T H.264, approved in 2024-08, specifies additional SEI messages for neural-network post-filter characteristics, neural-network post-filter activation, and phase indication (through referencing to Rec. ITU-T H.274 | ISO/IEC 23002-7), additional colour type identifiers, and miscellaneous minor corrections and clarifications. Users of previous editions are forewarned that, since previous placeholder Annex F was removed in this edition, all subsequent Annexes, clauses, tables, figures and equations were renumbered. + +# History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|---------------------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.264 | 2003-05-30 | 16 | 11.1002/1000/6312 | +| 1.1 | ITU-T H.264 (2003) Cor. 1 | 2004-05-07 | 16 | 11.1002/1000/7255 | +| 2.0 | ITU-T H.264 | 2005-03-01 | 16 | 11.1002/1000/7825 | +| 2.1 | ITU-T H.264 (2005) Cor. 1 | 2005-09-13 | 16 | 11.1002/1000/8572 | +| 2.2 | ITU-T H.264 (2005) Amd. 1 | 2006-06-13 | 16 | 11.1002/1000/8811 | +| 2.3 | ITU-T H.264 (2005) Amd. 2 | 2007-04-06 | 16 | 11.1002/1000/9036 | +| 3.0 | ITU-T H.264 | 2007-11-22 | 16 | 11.1002/1000/9226 | +| 3.1 | ITU-T H.264 (2007) Cor. 1 | 2009-01-13 | 16 | 11.1002/1000/9519 | +| 4.0 | ITU-T H.264 | 2009-03-16 | 16 | 11.1002/1000/9710 | +| 5.0 | ITU-T H.264 | 2010-03-09 | 16 | 11.1002/1000/10635 | +| 6.0 | ITU-T H.264 | 2011-06-29 | 16 | 11.1002/1000/11293 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +| | | | | | +|------|-------------------|------------|----|--------------------| +| 7.0 | ITU-T H.264 | 2012-01-13 | 16 | 11.1002/1000/11466 | +| 8.0 | ITU-T H.264 | 2013-04-13 | 16 | 11.1002/1000/11830 | +| 9.0 | ITU-T H.264 (V9) | 2014-02-13 | 16 | 11.1002/1000/12063 | +| 10.0 | ITU-T H.264 (V10) | 2016-02-13 | 16 | 11.1002/1000/12641 | +| 11.0 | ITU-T H.264 (V11) | 2016-10-14 | 16 | 11.1002/1000/12904 | +| 12.0 | ITU-T H.264 (V12) | 2017-04-13 | 16 | 11.1002/1000/13189 | +| 13.0 | ITU-T H.264 (V13) | 2019-06-13 | 16 | 11.1002/1000/13903 | +| 14.0 | ITU-T H.264 (V14) | 2021-08-22 | 16 | 11.1002/1000/14659 | +| 15.0 | ITU-T H.264 (V15) | 2024-08-13 | 16 | 11.1002/1000/15935 | + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +# INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# Table of Contents + +Page + +| | | | +|----------|---------------------------------------------------------------------------------------------------------|----| +| 0 | Introduction..... | 1 | +| 0.1 | Prologue..... | 1 | +| 0.2 | Purpose..... | 1 | +| 0.3 | Applications..... | 1 | +| 0.4 | Publication and versions of this Specification..... | 1 | +| 0.5 | Profiles and levels..... | 3 | +| 0.6 | Overview of the design characteristics..... | 4 | +| 0.6.1 | Predictive coding..... | 5 | +| 0.6.2 | Coding of progressive and interlaced video..... | 5 | +| 0.6.3 | Picture partitioning into macroblocks and smaller partitions..... | 5 | +| 0.6.4 | Spatial redundancy reduction..... | 5 | +| 0.7 | How to read this Specification..... | 6 | +| 1 | Scope..... | 6 | +| 2 | Normative references..... | 6 | +| 3 | Definitions..... | 7 | +| 4 | Abbreviations..... | 16 | +| 5 | Conventions..... | 16 | +| 5.1 | Arithmetic operators..... | 16 | +| 5.2 | Logical operators..... | 17 | +| 5.3 | Relational operators..... | 17 | +| 5.4 | Bit-wise operators..... | 17 | +| 5.5 | Assignment operators..... | 17 | +| 5.6 | Range notation..... | 18 | +| 5.7 | Mathematical functions..... | 18 | +| 5.8 | Order of operation precedence..... | 19 | +| 5.9 | Variables, syntax elements, and tables..... | 20 | +| 5.10 | Text description of logical operations..... | 21 | +| 5.11 | Processes..... | 22 | +| 6 | Source, coded, decoded and output data formats, scanning processes, and neighbouring relationships..... | 22 | +| 6.1 | Bitstream formats..... | 22 | +| 6.2 | Source, decoded, and output picture formats..... | 22 | +| 6.3 | Spatial subdivision of pictures and slices..... | 27 | +| 6.4 | Inverse scanning processes and derivation processes for neighbours..... | 28 | +| 6.4.1 | Inverse macroblock scanning process..... | 28 | +| 6.4.2 | Inverse macroblock partition and sub-macroblock partition scanning process..... | 29 | +| 6.4.2.1 | Inverse macroblock partition scanning process..... | 30 | +| 6.4.2.2 | Inverse sub-macroblock partition scanning process..... | 30 | +| 6.4.3 | Inverse 4x4 luma block scanning process..... | 30 | +| 6.4.4 | Inverse 4x4 Cb or Cr block scanning process for ChromaArrayType equal to 3..... | 31 | +| 6.4.5 | Inverse 8x8 luma block scanning process..... | 31 | +| 6.4.6 | Inverse 8x8 Cb or Cr block scanning process for ChromaArrayType equal to 3..... | 31 | +| 6.4.7 | Inverse 4x4 chroma block scanning process..... | 31 | +| 6.4.8 | Derivation process of the availability for macroblock addresses..... | 32 | +| 6.4.9 | Derivation process for neighbouring macroblock addresses and their availability..... | 32 | +| 6.4.10 | Derivation process for neighbouring macroblock addresses and their availability in MBAFF frames..... | 33 | +| 6.4.11 | Derivation processes for neighbouring macroblocks, blocks, and partitions..... | 33 | +| 6.4.11.1 | Derivation process for neighbouring macroblocks..... | 34 | +| 6.4.11.2 | Derivation process for neighbouring 8x8 luma block..... | 34 | +| 6.4.11.3 | Derivation process for neighbouring 8x8 chroma blocks for ChromaArrayType equal to 3..... | 35 | +| 6.4.11.4 | Derivation process for neighbouring 4x4 luma blocks..... | 35 | +| 6.4.11.5 | Derivation process for neighbouring 4x4 chroma blocks..... | 36 | +| 6.4.11.6 | Derivation process for neighbouring 4x4 chroma blocks for ChromaArrayType equal to 3..... | 36 | +| 6.4.11.7 | Derivation process for neighbouring partitions..... | 36 | +| 6.4.12 | Derivation process for neighbouring locations..... | 38 | +| 6.4.12.1 | Specification for neighbouring locations in fields and non-MBAFF frames..... | 38 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------|-----| +| 6.4.12.2 | Specification for neighbouring locations in MBAFF frames ..... | 39 | +| 6.4.13 | Derivation processes for block and partition indices ..... | 40 | +| 6.4.13.1 | Derivation process for 4x4 luma block indices ..... | 41 | +| 6.4.13.2 | Derivation process for 4x4 chroma block indices ..... | 41 | +| 6.4.13.3 | Derivation process for 8x8 luma block indices ..... | 41 | +| 6.4.13.4 | Derivation process for macroblock and sub-macroblock partition indices ..... | 41 | +| 7 | Syntax and semantics ..... | 42 | +| 7.1 | Method of specifying syntax in tabular form ..... | 42 | +| 7.2 | Specification of syntax functions, categories, and descriptors ..... | 43 | +| 7.3 | Syntax in tabular form ..... | 45 | +| 7.3.1 | NAL unit syntax ..... | 45 | +| 7.3.2 | Raw byte sequence payloads and RBSP trailing bits syntax ..... | 45 | +| 7.3.2.1 | Sequence parameter set RBSP syntax ..... | 45 | +| 7.3.2.2 | Picture parameter set RBSP syntax ..... | 49 | +| 7.3.2.3 | Supplemental enhancement information RBSP syntax ..... | 50 | +| 7.3.2.4 | Access unit delimiter RBSP syntax ..... | 50 | +| 7.3.2.5 | End of sequence RBSP syntax ..... | 51 | +| 7.3.2.6 | End of stream RBSP syntax ..... | 51 | +| 7.3.2.7 | Filler data RBSP syntax ..... | 51 | +| 7.3.2.8 | Slice layer without partitioning RBSP syntax ..... | 51 | +| 7.3.2.9 | Slice data partition RBSP syntax ..... | 51 | +| 7.3.2.10 | RBSP slice trailing bits syntax ..... | 52 | +| 7.3.2.11 | RBSP trailing bits syntax ..... | 52 | +| 7.3.2.12 | Prefix NAL unit RBSP syntax ..... | 53 | +| 7.3.2.13 | Slice layer extension RBSP syntax ..... | 53 | +| 7.3.3 | Slice header syntax ..... | 53 | +| 7.3.3.1 | Reference picture list modification syntax ..... | 55 | +| 7.3.3.2 | Prediction weight table syntax ..... | 56 | +| 7.3.3.3 | Decoded reference picture marking syntax ..... | 57 | +| 7.3.4 | Slice data syntax ..... | 58 | +| 7.3.5 | Macroblock layer syntax ..... | 59 | +| 7.3.5.1 | Macroblock prediction syntax ..... | 60 | +| 7.3.5.2 | Sub-macroblock prediction syntax ..... | 61 | +| 7.3.5.3 | Residual data syntax ..... | 62 | +| 7.4 | Semantics ..... | 65 | +| 7.4.1 | NAL unit semantics ..... | 65 | +| 7.4.1.1 | Encapsulation of an SODB within an RBSP (informative) ..... | 69 | +| 7.4.1.2 | Order of NAL units and association to coded pictures, access units, and video sequences ..... | 70 | +| 7.4.2 | Raw byte sequence payloads and RBSP trailing bits semantics ..... | 76 | +| 7.4.2.1 | Sequence parameter set RBSP semantics ..... | 76 | +| 7.4.2.2 | Picture parameter set RBSP semantics ..... | 85 | +| 7.4.2.3 | Supplemental enhancement information RBSP semantics ..... | 87 | +| 7.4.2.4 | Access unit delimiter RBSP semantics ..... | 87 | +| 7.4.2.5 | End of sequence RBSP semantics ..... | 88 | +| 7.4.2.6 | End of stream RBSP semantics ..... | 88 | +| 7.4.2.7 | Filler data RBSP semantics ..... | 88 | +| 7.4.2.8 | Slice layer without partitioning RBSP semantics ..... | 88 | +| 7.4.2.9 | Slice data partition RBSP semantics ..... | 88 | +| 7.4.2.10 | RBSP slice trailing bits semantics ..... | 89 | +| 7.4.2.11 | RBSP trailing bits semantics ..... | 90 | +| 7.4.2.12 | Prefix NAL unit RBSP semantics ..... | 90 | +| 7.4.2.13 | Slice layer extension RBSP semantics ..... | 90 | +| 7.4.3 | Slice header semantics ..... | 90 | +| 7.4.3.1 | Reference picture list modification semantics ..... | 96 | +| 7.4.3.2 | Prediction weight table semantics ..... | 96 | +| 7.4.3.3 | Decoded reference picture marking semantics ..... | 97 | +| 7.4.4 | Slice data semantics ..... | 101 | +| 7.4.5 | Macroblock layer semantics ..... | 101 | +| 7.4.5.1 | Macroblock prediction semantics ..... | 109 | +| 7.4.5.2 | Sub-macroblock prediction semantics ..... | 110 | +| 7.4.5.3 | Residual data semantics ..... | 112 | + +| | | | +|---------|------------------------------------------------------------------------------------------------------------------|-----| +| 8 | Decoding process..... | 114 | +| 8.1 | NAL unit decoding process..... | 115 | +| 8.2 | Slice decoding process..... | 116 | +| 8.2.1 | Decoding process for picture order count ..... | 116 | +| 8.2.1.1 | Decoding process for picture order count type 0 ..... | 117 | +| 8.2.1.2 | Decoding process for picture order count type 1 ..... | 118 | +| 8.2.1.3 | Decoding process for picture order count type 2 ..... | 119 | +| 8.2.2 | Decoding process for macroblock to slice group map ..... | 120 | +| 8.2.2.1 | Specification for interleaved slice group map type..... | 121 | +| 8.2.2.2 | Specification for dispersed slice group map type..... | 121 | +| 8.2.2.3 | Specification for foreground with left-over slice group map type ..... | 121 | +| 8.2.2.4 | Specification for box-out slice group map types..... | 122 | +| 8.2.2.5 | Specification for raster scan slice group map types ..... | 122 | +| 8.2.2.6 | Specification for wipe slice group map types ..... | 122 | +| 8.2.2.7 | Specification for explicit slice group map type..... | 123 | +| 8.2.2.8 | Specification for conversion of map unit to slice group map to macroblock to slice group map .... | 123 | +| 8.2.3 | Decoding process for slice data partitions..... | 123 | +| 8.2.4 | Decoding process for reference picture lists construction..... | 124 | +| 8.2.4.1 | Decoding process for picture numbers..... | 124 | +| 8.2.4.2 | Initialization process for reference picture lists ..... | 125 | +| 8.2.4.3 | Modification process for reference picture lists..... | 128 | +| 8.2.5 | Decoded reference picture marking process ..... | 130 | +| 8.2.5.1 | Sequence of operations for decoded reference picture marking process ..... | 131 | +| 8.2.5.2 | Decoding process for gaps in frame_num..... | 131 | +| 8.2.5.3 | Sliding window decoded reference picture marking process ..... | 132 | +| 8.2.5.4 | Adaptive memory control decoded reference picture marking process ..... | 132 | +| 8.3 | Intra prediction process..... | 134 | +| 8.3.1 | Intra_4x4 prediction process for luma samples..... | 135 | +| 8.3.1.1 | Derivation process for Intra4x4PredMode..... | 135 | +| 8.3.1.2 | Intra_4x4 sample prediction ..... | 137 | +| 8.3.2 | Intra_8x8 prediction process for luma samples..... | 141 | +| 8.3.2.1 | Derivation process for Intra8x8PredMode..... | 141 | +| 8.3.2.2 | Intra_8x8 sample prediction ..... | 143 | +| 8.3.3 | Intra_16x16 prediction process for luma samples..... | 148 | +| 8.3.3.1 | Specification of Intra_16x16_Vertical prediction mode ..... | 149 | +| 8.3.3.2 | Specification of Intra_16x16_Horizontal prediction mode ..... | 149 | +| 8.3.3.3 | Specification of Intra_16x16_DC prediction mode ..... | 149 | +| 8.3.3.4 | Specification of Intra_16x16_Plane prediction mode ..... | 149 | +| 8.3.4 | Intra prediction process for chroma samples..... | 150 | +| 8.3.4.1 | Specification of Intra_Chroma_DC prediction mode ..... | 151 | +| 8.3.4.2 | Specification of Intra_Chroma_Horizontal prediction mode ..... | 152 | +| 8.3.4.3 | Specification of Intra_Chroma_Vertical prediction mode ..... | 153 | +| 8.3.4.4 | Specification of Intra_Chroma_Plane prediction mode ..... | 153 | +| 8.3.4.5 | Intra prediction for chroma samples with ChromaArrayType equal to 3 ..... | 153 | +| 8.3.5 | Sample construction process for I_PCM macroblocks ..... | 154 | +| 8.4 | Inter prediction process..... | 154 | +| 8.4.1 | Derivation process for motion vector components and reference indices..... | 157 | +| 8.4.1.1 | Derivation process for luma motion vectors for skipped macroblocks in P and SP slices..... | 158 | +| 8.4.1.2 | Derivation process for luma motion vectors for B_Skip, B_Direct_16x16, and B_Direct_8x8..... | 158 | +| 8.4.1.3 | Derivation process for luma motion vector prediction..... | 165 | +| 8.4.1.4 | Derivation process for chroma motion vectors ..... | 167 | +| 8.4.2 | Decoding process for Inter prediction samples ..... | 168 | +| 8.4.2.1 | Reference picture selection process ..... | 169 | +| 8.4.2.2 | Fractional sample interpolation process..... | 170 | +| 8.4.2.3 | Weighted sample prediction process..... | 175 | +| 8.4.3 | Derivation process for prediction weights ..... | 176 | +| 8.5 | Transform coefficient decoding process and picture construction process prior to deblocking filter process ..... | 178 | +| 8.5.1 | Specification of transform decoding process for 4x4 luma residual blocks..... | 179 | +| 8.5.2 | Specification of transform decoding process for luma samples of Intra_16x16 macroblock prediction mode..... | 179 | +| 8.5.3 | Specification of transform decoding process for 8x8 luma residual blocks..... | 180 | +| 8.5.4 | Specification of transform decoding process for chroma samples ..... | 181 | + +| | | | +|----------|-------------------------------------------------------------------------------------------------------|-----| +| 8.5.5 | Specification of transform decoding process for chroma samples with ChromaArrayType equal to 3 .. | 183 | +| 8.5.6 | Inverse scanning process for 4x4 transform coefficients and scaling lists ..... | 183 | +| 8.5.7 | Inverse scanning process for 8x8 transform coefficients and scaling lists ..... | 184 | +| 8.5.8 | Derivation process for chroma quantization parameters ..... | 185 | +| 8.5.9 | Derivation process for scaling functions ..... | 186 | +| 8.5.10 | Scaling and transformation process for DC transform coefficients for Intra_16x16 macroblock type ... | 187 | +| 8.5.11 | Scaling and transformation process for chroma DC transform coefficients ..... | 188 | +| 8.5.11.1 | Transformation process for chroma DC transform coefficients ..... | 188 | +| 8.5.11.2 | Scaling process for chroma DC transform coefficients ..... | 189 | +| 8.5.12 | Scaling and transformation process for residual 4x4 blocks ..... | 189 | +| 8.5.12.1 | Scaling process for residual 4x4 blocks ..... | 190 | +| 8.5.12.2 | Transformation process for residual 4x4 blocks ..... | 191 | +| 8.5.13 | Scaling and transformation process for residual 8x8 blocks ..... | 192 | +| 8.5.13.1 | Scaling process for residual 8x8 blocks ..... | 192 | +| 8.5.13.2 | Transformation process for residual 8x8 blocks ..... | 193 | +| 8.5.14 | Picture construction process prior to deblocking filter process ..... | 195 | +| 8.5.15 | Intra residual transform-bypass decoding process ..... | 196 | +| 8.6 | Decoding process for P macroblocks in SP slices or SI macroblocks ..... | 196 | +| 8.6.1 | SP decoding process for non-switching pictures ..... | 197 | +| 8.6.1.1 | Luma transform coefficient decoding process ..... | 197 | +| 8.6.1.2 | Chroma transform coefficient decoding process ..... | 198 | +| 8.6.2 | SP and SI slice decoding process for switching pictures ..... | 199 | +| 8.6.2.1 | Luma transform coefficient decoding process ..... | 199 | +| 8.6.2.2 | Chroma transform coefficient decoding process ..... | 200 | +| 8.7 | Deblocking filter process ..... | 201 | +| 8.7.1 | Filtering process for block edges ..... | 205 | +| 8.7.2 | Filtering process for a set of samples across a horizontal or vertical block edge ..... | 206 | +| 8.7.2.1 | Derivation process for the luma content dependent boundary filtering strength ..... | 207 | +| 8.7.2.2 | Derivation process for the thresholds for each block edge ..... | 209 | +| 8.7.2.3 | Filtering process for edges with bS less than 4 ..... | 210 | +| 8.7.2.4 | Filtering process for edges for bS equal to 4 ..... | 211 | +| 9 | Parsing process ..... | 212 | +| 9.1 | Parsing process for Exp-Golomb codes ..... | 212 | +| 9.1.1 | Mapping process for signed Exp-Golomb codes ..... | 214 | +| 9.1.2 | Mapping process for coded block pattern ..... | 214 | +| 9.2 | CAVLC parsing process for transform coefficient levels ..... | 217 | +| 9.2.1 | Parsing process for total number of non-zero transform coefficient levels and number of trailing ones | 217 | +| 9.2.2 | Parsing process for level information ..... | 221 | +| 9.2.2.1 | Parsing process for level_prefix ..... | 222 | +| 9.2.3 | Parsing process for run information ..... | 223 | +| 9.2.4 | Combining level and run information ..... | 226 | +| 9.3 | CABAC parsing process for slice data ..... | 226 | +| 9.3.1 | Initialization process ..... | 228 | +| 9.3.1.1 | Initialization process for context variables ..... | 229 | +| 9.3.1.2 | Initialization process for the arithmetic decoding engine ..... | 252 | +| 9.3.2 | Binarization process ..... | 252 | +| 9.3.2.1 | Unary (U) binarization process ..... | 255 | +| 9.3.2.2 | Truncated unary (TU) binarization process ..... | 256 | +| 9.3.2.3 | Concatenated unary/ k-th order Exp-Golomb (UEGk) binarization process ..... | 256 | +| 9.3.2.4 | Fixed-length (FL) binarization process ..... | 257 | +| 9.3.2.5 | Binarization process for macroblock type and sub-macroblock type ..... | 257 | +| 9.3.2.6 | Binarization process for coded block pattern ..... | 260 | +| 9.3.2.7 | Binarization process for mb_qp_delta ..... | 260 | +| 9.3.3 | Decoding process flow ..... | 260 | +| 9.3.3.1 | Derivation process for ctxIdx ..... | 261 | +| 9.3.3.2 | Arithmetic decoding process ..... | 274 | +| 9.3.4 | Arithmetic encoding process (informative) ..... | 281 | +| 9.3.4.1 | Initialization process for the arithmetic encoding engine (informative) ..... | 281 | +| 9.3.4.2 | Encoding process for a binary decision (informative) ..... | 282 | +| 9.3.4.3 | Renormalization process in the arithmetic encoding engine (informative) ..... | 283 | +| 9.3.4.4 | Bypass encoding process for binary decisions (informative) ..... | 285 | +| 9.3.4.5 | Encoding process for a binary decision before termination (informative) ..... | 286 | + +| | | | +|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 9.3.4.6 | Byte stuffing process (informative) ..... | 288 | +| Annex A – Profiles and levels ..... | | 289 | +| A.1 | Requirements on video decoder capability ..... | 289 | +| A.2 | Profiles..... | 289 | +| A.2.1 | Baseline profile ..... | 289 | +| A.2.1.1 | Constrained Baseline profile..... | 290 | +| A.2.2 | Main profile ..... | 290 | +| A.2.3 | Extended profile..... | 290 | +| A.2.4 | High profile..... | 291 | +| A.2.4.1 | Progressive High profile ..... | 291 | +| A.2.4.2 | Constrained High profile..... | 292 | +| A.2.5 | High 10 profile..... | 292 | +| A.2.5.1 | Progressive High 10 profile ..... | 292 | +| A.2.6 | High 4:2:2 profile..... | 293 | +| A.2.7 | High 4:4:4 Predictive profile..... | 293 | +| A.2.8 | High 10 Intra profile ..... | 294 | +| A.2.9 | High 4:2:2 Intra profile ..... | 294 | +| A.2.10 | High 4:4:4 Intra profile ..... | 295 | +| A.2.11 | CAVLC 4:4:4 Intra profile..... | 295 | +| A.3 | Levels..... | 296 | +| A.3.1 | Level limits common to the Baseline, Constrained Baseline, Main, and Extended profiles..... | 296 | +| A.3.2 | Level limits common to the High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles ..... | 298 | +| A.3.3 | Profile-specific level limits ..... | 300 | +| A.3.3.1 | Level limits of the Baseline and Constrained Baseline profile ..... | 302 | +| A.3.3.2 | Level limits of the Main, High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profile..... | 303 | +| A.3.3.3 | Level limits of the Extended profile ..... | 304 | +| A.3.4 | Effect of level limits on frame rate (informative) ..... | 305 | +| A.3.5 | Effect of level limits on maximum DPB size in units of frames (informative)..... | 308 | +| Annex B – Byte stream format ..... | | 311 | +| B.1 | Byte stream NAL unit syntax and semantics ..... | 311 | +| B.1.1 | Byte stream NAL unit syntax..... | 311 | +| B.1.2 | Byte stream NAL unit semantics ..... | 311 | +| B.2 | Byte stream NAL unit decoding process ..... | 312 | +| B.3 | Decoder byte-alignment recovery (informative)..... | 312 | +| Annex C – Hypothetical reference decoder ..... | | 313 | +| C.1 | Operation of coded picture buffer (CPB)..... | 318 | +| C.1.1 | Timing of bitstream arrival ..... | 318 | +| C.1.2 | Timing of coded picture removal..... | 319 | +| C.2 | Operation of the decoded picture buffer (DPB)..... | 319 | +| C.2.1 | Decoding of gaps in frame_num and storage of "non-existing" frames..... | 320 | +| C.2.2 | Picture decoding and output..... | 321 | +| C.2.3 | Removal of pictures from the DPB before possible insertion of the current picture..... | 322 | +| C.2.4 | Current decoded picture marking and storage..... | 323 | +| C.2.4.1 | Marking and storage of a reference picture into the DPB..... | 323 | +| C.2.4.2 | Storage of a non-reference picture into the DPB ..... | 324 | +| C.3 | Bitstream conformance ..... | 324 | +| C.4 | Decoder conformance ..... | 326 | +| C.4.1 | Operation of the output order DPB ..... | 326 | +| C.4.2 | Decoding of gaps in frame_num and storage of "non-existing" pictures..... | 327 | +| C.4.3 | Picture decoding..... | 328 | +| C.4.4 | Removal of pictures from the DPB before possible insertion of the current picture..... | 328 | +| C.4.5 | Current decoded picture marking and storage..... | 329 | +| C.4.5.1 | Storage and marking of a reference decoded picture into the DPB ..... | 330 | +| C.4.5.2 | Storage and marking of a non-reference decoded picture into the DPB ..... | 330 | +| C.4.5.3 | "Bumping" process ..... | 331 | + +| | | +|--------------------------------------------------------------------------------|-----| +| Annex D – Supplemental enhancement information ..... | 333 | +| D.1 SEI payload syntax ..... | 333 | +| D.1.1 General SEI message syntax ..... | 333 | +| D.1.2 Buffering period SEI message syntax ..... | 337 | +| D.1.3 Picture timing SEI message syntax ..... | 337 | +| D.1.4 Pan-scan rectangle SEI message syntax ..... | 338 | +| D.1.5 Filler payload SEI message syntax ..... | 338 | +| D.1.6 User data registered by Rec. ITU-T T.35 SEI message syntax ..... | 339 | +| D.1.7 User data unregistered SEI message syntax ..... | 339 | +| D.1.8 Recovery point SEI message syntax ..... | 339 | +| D.1.9 Decoded reference picture marking repetition SEI message syntax ..... | 340 | +| D.1.10 Spare picture SEI message syntax ..... | 340 | +| D.1.11 Scene information SEI message syntax ..... | 341 | +| D.1.12 Sub-sequence information SEI message syntax ..... | 341 | +| D.1.13 Sub-sequence layer characteristics SEI message syntax ..... | 341 | +| D.1.14 Sub-sequence characteristics SEI message syntax ..... | 342 | +| D.1.15 Full-frame freeze SEI message syntax ..... | 342 | +| D.1.16 Full-frame freeze release SEI message syntax ..... | 342 | +| D.1.17 Full-frame snapshot SEI message syntax ..... | 342 | +| D.1.18 Progressive refinement segment start SEI message syntax ..... | 343 | +| D.1.19 Progressive refinement segment end SEI message syntax ..... | 343 | +| D.1.20 Motion-constrained slice group set SEI message syntax ..... | 343 | +| D.1.21 Film grain characteristics SEI message syntax ..... | 344 | +| D.1.22 Deblocking filter display preference SEI message syntax ..... | 344 | +| D.1.23 Stereo video information SEI message syntax ..... | 345 | +| D.1.24 Post-filter hint SEI message syntax ..... | 345 | +| D.1.25 Tone mapping information SEI message syntax ..... | 346 | +| D.1.26 Frame packing arrangement SEI message syntax ..... | 347 | +| D.1.27 Display orientation SEI message syntax ..... | 347 | +| D.1.28 Green metadata SEI message syntax ..... | 347 | +| D.1.29 Mastering display colour volume SEI message syntax ..... | 348 | +| D.1.30 Colour remapping information SEI message syntax ..... | 349 | +| D.1.31 Content light level information SEI message syntax ..... | 350 | +| D.1.32 Alternative transfer characteristics SEI message syntax ..... | 350 | +| D.1.33 Content colour volume SEI message syntax ..... | 350 | +| D.1.34 Ambient viewing environment SEI message syntax ..... | 351 | +| D.1.35 Syntax of omnidirectional video specific SEI messages ..... | 351 | +| D.1.35.1 Equirectangular projection SEI message syntax ..... | 351 | +| D.1.35.2 Cubemap projection SEI message syntax ..... | 351 | +| D.1.35.3 Sphere rotation SEI message syntax ..... | 352 | +| D.1.35.4 Region-wise packing SEI message syntax ..... | 353 | +| D.1.35.5 Omnidirectional viewport SEI message syntax ..... | 354 | +| D.1.36 SEI manifest SEI message syntax ..... | 354 | +| D.1.37 SEI prefix indication SEI message syntax ..... | 354 | +| D.1.38 Shutter interval information SEI message syntax ..... | 355 | +| D.1.39 Reserved SEI message syntax ..... | 355 | +| D.2 SEI payload semantics ..... | 355 | +| D.2.1 General SEI payload semantics ..... | 355 | +| D.2.2 Buffering period SEI message semantics ..... | 355 | +| D.2.3 Picture timing SEI message semantics ..... | 356 | +| D.2.4 Pan-scan rectangle SEI message semantics ..... | 361 | +| D.2.5 Filler payload SEI message semantics ..... | 362 | +| D.2.6 User data registered by Rec. ITU-T T.35 SEI message semantics ..... | 362 | +| D.2.7 User data unregistered SEI message semantics ..... | 363 | +| D.2.8 Recovery point SEI message semantics ..... | 363 | +| D.2.9 Decoded reference picture marking repetition SEI message semantics ..... | 365 | +| D.2.10 Spare picture SEI message semantics ..... | 365 | +| D.2.11 Scene information SEI message semantics ..... | 367 | +| D.2.12 Sub-sequence information SEI message semantics ..... | 368 | +| D.2.13 Sub-sequence layer characteristics SEI message semantics ..... | 370 | +| D.2.14 Sub-sequence characteristics SEI message semantics ..... | 371 | +| D.2.15 Full-frame freeze SEI message semantics ..... | 372 | +| D.2.16 Full-frame freeze release SEI message semantics ..... | 372 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------|-----| +| D.2.17 | Full-frame snapshot SEI message semantics ..... | 373 | +| D.2.18 | Progressive refinement segment start SEI message semantics..... | 373 | +| D.2.19 | Progressive refinement segment end SEI message semantics..... | 373 | +| D.2.20 | Motion-constrained slice group set SEI message semantics ..... | 374 | +| D.2.21 | Film grain characteristics SEI message semantics ..... | 374 | +| D.2.22 | Deblocking filter display preference SEI message semantics ..... | 381 | +| D.2.23 | Stereo video information SEI message semantics..... | 382 | +| D.2.24 | Post-filter hint SEI message semantics ..... | 383 | +| D.2.25 | Tone mapping information SEI message semantics..... | 384 | +| D.2.26 | Frame packing arrangement SEI message semantics..... | 388 | +| D.2.27 | Display orientation SEI message semantics..... | 400 | +| D.2.28 | Green metadata SEI message semantics ..... | 401 | +| D.2.29 | Mastering display colour volume SEI message semantics..... | 401 | +| D.2.30 | Colour remapping information SEI message semantics..... | 403 | +| D.2.31 | Content light level information SEI message semantics ..... | 405 | +| D.2.32 | Alternative transfer characteristics SEI message semantics..... | 406 | +| D.2.33 | Content colour volume SEI message semantics..... | 406 | +| D.2.34 | Ambient viewing environment SEI message semantics..... | 408 | +| D.2.35 | Semantics of omnidirectional video specific SEI messages..... | 408 | +| D.2.35.1 | Equirectangular projection SEI message semantics..... | 408 | +| D.2.35.2 | Cubemap projection SEI message semantics..... | 410 | +| D.2.35.3 | Sphere rotation SEI message semantics..... | 410 | +| D.2.35.4 | Region-wise packing SEI message semantics..... | 411 | +| D.2.35.5 | Omnidirectional viewport SEI message semantics ..... | 416 | +| D.2.35.6 | Sample location remapping process..... | 417 | +| D.2.36 | SEI manifest SEI message semantics..... | 421 | +| D.2.37 | SEI prefix indication SEI message semantics ..... | 423 | +| D.2.38 | Shutter interval information SEI message semantics ..... | 424 | +| D.2.39 | Reserved SEI message semantics..... | 425 | +| D.3 | Use of SEI messages specified in other documents ..... | 425 | +| D.3.1 | General..... | 425 | +| D.3.2 | Use of the annotated regions SEI message..... | 425 | +| D.3.3 | Use of the neural network post-filter characteristics SEI message and the neural-network post-filter activation SEI message ..... | 426 | +| D.3.4 | Use of the phase indication SEI message..... | 428 | +| Annex E | – Video usability information ..... | 429 | +| E.1 | VUI syntax..... | 429 | +| E.1.1 | VUI parameters syntax..... | 429 | +| E.1.2 | HRD parameters syntax ..... | 430 | +| E.2 | VUI semantics..... | 431 | +| E.2.1 | VUI parameters semantics ..... | 431 | +| E.2.2 | HRD parameters semantics ..... | 446 | +| Annex F | – Scalable video coding ..... | 449 | +| F.1 | Scope..... | 449 | +| F.2 | Normative references ..... | 449 | +| F.3 | Definitions ..... | 449 | +| F.4 | Abbreviations ..... | 453 | +| F.5 | Conventions ..... | 453 | +| F.6 | Source, coded, decoded and output data formats, scanning processes, neighbouring and reference layer relationships..... | 453 | +| F.6.1 | Derivation process for reference layer macroblocks..... | 453 | +| F.6.1.1 | Field-to-frame reference layer macroblock conversion process ..... | 455 | +| F.6.1.2 | Frame-to-field reference layer macroblock conversion process ..... | 455 | +| F.6.2 | Derivation process for reference layer partitions ..... | 455 | +| F.6.3 | Derivation process for reference layer sample locations in resampling ..... | 456 | +| F.6.4 | SVC derivation process for macroblock and sub-macroblock partition indices ..... | 458 | +| F.7 | Syntax and semantics ..... | 459 | +| F.7.1 | Method of specifying syntax in tabular form ..... | 459 | +| F.7.2 | Specification of syntax functions, categories, and descriptors..... | 459 | +| F.7.3 | Syntax in tabular form..... | 459 | +| F.7.3.1 | NAL unit syntax..... | 459 | + +| | | | +|---------|------------------------------------------------------------------------------------------------------------------------------------|-----| +| F.7.3.2 | Raw byte sequence payloads and RBSP trailing bits syntax..... | 459 | +| F.7.3.3 | Slice header syntax ..... | 461 | +| F.7.3.4 | Slice data syntax ..... | 464 | +| F.7.3.5 | Macroblock layer syntax..... | 465 | +| F.7.3.6 | Macroblock layer in scalable extension syntax..... | 466 | +| F.7.4 | Semantics ..... | 469 | +| F.7.4.1 | NAL unit semantics ..... | 470 | +| F.7.4.2 | Raw byte sequence payloads and RBSP trailing bits semantics ..... | 478 | +| F.7.4.3 | Slice header semantics ..... | 483 | +| F.7.4.4 | Slice data semantics ..... | 497 | +| F.7.4.5 | Macroblock layer semantics ..... | 497 | +| F.7.4.6 | Macroblock layer in scalable extension semantics ..... | 498 | +| F.8 | SVC decoding process ..... | 501 | +| F.8.1 | SVC initialization and decoding processes ..... | 502 | +| F.8.1.1 | Derivation process for the set of layer representations required for decoding..... | 503 | +| F.8.1.2 | Array assignment, initialization, and restructuring processes..... | 503 | +| F.8.1.3 | Layer representation decoding processes..... | 506 | +| F.8.1.4 | Slice decoding processes..... | 508 | +| F.8.1.5 | Macroblock initialization and decoding processes..... | 509 | +| F.8.2 | SVC reference picture lists construction and decoded reference picture marking process ..... | 521 | +| F.8.2.1 | SVC decoding process for picture order count ..... | 523 | +| F.8.2.2 | SVC decoding process for picture numbers..... | 523 | +| F.8.2.3 | SVC decoding process for reference picture lists construction..... | 524 | +| F.8.2.4 | SVC decoded reference picture marking process ..... | 525 | +| F.8.2.5 | SVC decoding process for gaps in frame_num..... | 531 | +| F.8.3 | SVC intra decoding processes..... | 532 | +| F.8.3.1 | SVC derivation process for intra prediction modes ..... | 532 | +| F.8.3.2 | SVC intra sample prediction and construction process..... | 535 | +| F.8.4 | SVC Inter prediction process ..... | 541 | +| F.8.4.1 | SVC derivation process for motion vector components and reference indices..... | 541 | +| F.8.4.2 | SVC decoding process for Inter prediction samples ..... | 547 | +| F.8.5 | SVC transform coefficient decoding and sample array construction processes..... | 552 | +| F.8.5.1 | Transform coefficient scaling and refinement process ..... | 553 | +| F.8.5.2 | Transform coefficient level scaling process prior to transform coefficient refinement ..... | 560 | +| F.8.5.3 | Residual construction and accumulation process..... | 561 | +| F.8.5.4 | Sample array accumulation process ..... | 565 | +| F.8.5.5 | Sample array re-initialization process..... | 568 | +| F.8.6 | Resampling processes for prediction data, intra samples, and residual samples..... | 568 | +| F.8.6.1 | Derivation process for inter-layer predictors for macroblock type, sub-macroblock type, reference indices, and motion vectors..... | 568 | +| F.8.6.2 | Resampling process for intra samples..... | 577 | +| F.8.6.3 | Resampling process for residual samples ..... | 589 | +| F.8.7 | SVC deblocking filter processes ..... | 596 | +| F.8.7.1 | Deblocking filter process for Intra_Base prediction ..... | 596 | +| F.8.7.2 | Deblocking filter process for target representations ..... | 596 | +| F.8.7.3 | Derivation process for quantization parameters used in the deblocking filter process ..... | 597 | +| F.8.7.4 | Macroblock deblocking filter process..... | 598 | +| F.8.8 | Specification of sub-bitstreams..... | 608 | +| F.8.8.1 | Sub-bitstream extraction process ..... | 608 | +| F.8.8.2 | Specification of the base layer bitstream ..... | 609 | +| F.9 | Parsing process ..... | 609 | +| F.9.1 | Alternative parsing process for coded block pattern..... | 609 | +| F.9.2 | Alternative CAVLC parsing process for transform coefficient levels ..... | 610 | +| F.9.2.1 | Additional parsing process for total number of non-zero transform coefficient levels and number of trailing ones ..... | 611 | +| F.9.2.2 | Alternative parsing process for run information ..... | 613 | +| F.9.3 | Alternative CABAC parsing process for slice data in scalable extension..... | 614 | +| F.9.3.1 | Initialization process ..... | 614 | +| F.9.3.2 | Binarization process..... | 615 | +| F.9.3.3 | Decoding process flow..... | 616 | +| F.10 | Profiles and levels ..... | 617 | +| F.10.1 | Profiles ..... | 617 | + +| | | | +|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| F.10.1.1 | Scalable Baseline profile..... | 617 | +| F.10.1.2 | Scalable High profile ..... | 620 | +| F.10.1.3 | Scalable High Intra profile ..... | 622 | +| F.10.2 | Levels..... | 623 | +| F.10.2.1 | Level limits common to Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, and Scalable High Intra profiles ..... | 623 | +| F.10.2.2 | Profile specific level limits ..... | 625 | +| F.11 | Byte stream format..... | 628 | +| F.12 | Hypothetical reference decoder ..... | 628 | +| F.13 | Supplemental enhancement information..... | 628 | +| F.13.1 | SEI payload syntax..... | 628 | +| F.13.1.1 | Scalability information SEI message syntax..... | 628 | +| F.13.1.2 | Sub-picture scalable layer SEI message syntax ..... | 631 | +| F.13.1.3 | Non-required layer representation SEI message syntax..... | 631 | +| F.13.1.4 | Priority layer information SEI message syntax..... | 631 | +| F.13.1.5 | Layers not present SEI message syntax ..... | 631 | +| F.13.1.6 | Layer dependency change SEI message syntax ..... | 632 | +| F.13.1.7 | Scalable nesting SEI message syntax..... | 632 | +| F.13.1.8 | Base layer temporal HRD SEI message syntax ..... | 632 | +| F.13.1.9 | Quality layer integrity check SEI message syntax ..... | 633 | +| F.13.1.10 | Redundant picture property SEI message syntax..... | 634 | +| F.13.1.11 | Temporal level zero dependency representation index SEI message syntax ..... | 634 | +| F.13.1.12 | Temporal level switching point SEI message syntax..... | 634 | +| F.13.2 | SEI payload semantics ..... | 634 | +| F.13.2.1 | Scalability information SEI message semantics ..... | 636 | +| F.13.2.2 | Sub-picture scalable layer SEI message semantics ..... | 651 | +| F.13.2.3 | Non-required layer representation SEI message semantics ..... | 652 | +| F.13.2.4 | Priority layer information SEI message semantics ..... | 652 | +| F.13.2.5 | Layers not present SEI message semantics..... | 653 | +| F.13.2.6 | Layer dependency change SEI message semantics..... | 653 | +| F.13.2.7 | Scalable nesting SEI message semantics ..... | 655 | +| F.13.2.8 | Base layer temporal HRD SEI message semantics ..... | 656 | +| F.13.2.9 | Quality layer integrity check SEI message semantics..... | 657 | +| F.13.2.10 | Redundant picture property SEI message semantics..... | 657 | +| F.13.2.11 | Temporal level zero dependency representation index SEI message semantics ..... | 659 | +| F.13.2.12 | Temporal level switching point SEI message semantics ..... | 660 | +| F.14 | Video usability information ..... | 661 | +| F.14.1 | SVC VUI parameters extension syntax..... | 661 | +| F.14.2 | SVC VUI parameters extension semantics ..... | 661 | +| Annex G – Multiview video coding ..... | | 664 | +| G.1 | Scope..... | 664 | +| G.2 | Normative references ..... | 664 | +| G.3 | Definitions ..... | 664 | +| G.4 | Abbreviations..... | 666 | +| G.5 | Conventions ..... | 666 | +| G.6 | Source, coded, decoded and output data formats, scanning processes, and neighbouring relationships..... | 667 | +| G.7 | Syntax and semantics..... | 667 | +| G.7.1 | Method of specifying syntax in tabular form ..... | 667 | +| G.7.2 | Specification of syntax functions, categories, and descriptors..... | 667 | +| G.7.3 | Syntax in tabular form..... | 667 | +| G.7.3.1 | NAL unit syntax..... | 667 | +| G.7.3.2 | Raw byte sequence payloads and RBSP trailing bits syntax..... | 667 | +| G.7.3.3 | Slice header syntax ..... | 669 | +| G.7.3.4 | Slice data syntax ..... | 670 | +| G.7.3.5 | Macroblock layer syntax..... | 670 | +| G.7.4 | Semantics ..... | 671 | +| G.7.4.1 | NAL unit semantics ..... | 671 | +| G.7.4.2 | Raw byte sequence payloads and RBSP trailing bits semantics ..... | 678 | +| G.7.4.3 | Slice header semantics..... | 682 | +| G.7.4.4 | Slice data semantics ..... | 684 | +| G.7.4.5 | Macroblock layer semantics ..... | 684 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------------------|-----| +| G.8 | MVC decoding process..... | 685 | +| G.8.1 | MVC decoding process for picture order count..... | 685 | +| G.8.2 | MVC decoding process for reference picture lists construction..... | 686 | +| G.8.2.1 | Initialization process for reference picture list for inter-view prediction references ..... | 687 | +| G.8.2.2 | Modification process for reference picture lists..... | 687 | +| G.8.3 | MVC decoded reference picture marking process ..... | 690 | +| G.8.4 | MVC inter prediction and inter-view prediction process..... | 690 | +| G.8.4.1 | Additional processing for an inter-view prediction reference..... | 690 | +| G.8.5 | Specification of sub-bitstreams..... | 694 | +| G.8.5.1 | Derivation process for required anchor view components..... | 695 | +| G.8.5.2 | Derivation process for required non-anchor view components..... | 695 | +| G.8.5.3 | Sub-bitstream extraction process ..... | 695 | +| G.8.5.4 | Specification of the base view bitstream..... | 697 | +| G.8.5.5 | Creation of a base view during sub-bitstream extraction (informative)..... | 697 | +| G.8.6 | MFC enhanced resolution picture reconstruction ..... | 698 | +| G.9 | Parsing process ..... | 702 | +| G.10 | Profiles and levels ..... | 702 | +| G.10.1 | Profiles ..... | 702 | +| G.10.1.1 | Multiview High profile ..... | 702 | +| G.10.1.2 | Stereo High profile..... | 703 | +| G.10.1.3 | MFC High profile ..... | 704 | +| G.10.2 | Levels..... | 704 | +| G.10.2.1 | Level limits common to Multiview High, Stereo High, and MFC High profiles..... | 705 | +| G.10.2.2 | Profile specific level limits ..... | 708 | +| G.11 | Byte stream format..... | 708 | +| G.12 | MVC hypothetical reference decoder ..... | 708 | +| G.13 | MVC SEI messages ..... | 708 | +| G.13.1 | SEI message syntax..... | 708 | +| G.13.1.1 | Parallel decoding information SEI message syntax ..... | 708 | +| G.13.1.2 | MVC scalable nesting SEI message syntax ..... | 708 | +| G.13.1.3 | View scalability information SEI message syntax..... | 709 | +| G.13.1.4 | Multiview scene information SEI message syntax ..... | 710 | +| G.13.1.5 | Multiview acquisition information SEI message syntax..... | 710 | +| G.13.1.6 | Non-required view component SEI message syntax..... | 711 | +| G.13.1.7 | View dependency change SEI message syntax..... | 712 | +| G.13.1.8 | Operation point not present SEI message syntax..... | 712 | +| G.13.1.9 | Base view temporal HRD SEI message syntax..... | 712 | +| G.13.1.10 | Multiview view position SEI message syntax ..... | 713 | +| G.13.2 | SEI message semantics ..... | 713 | +| G.13.2.1 | Parallel decoding information SEI message semantics..... | 714 | +| G.13.2.2 | MVC scalable nesting SEI message semantics..... | 715 | +| G.13.2.3 | View scalability information SEI message semantics..... | 716 | +| G.13.2.4 | Multiview scene information SEI message semantics ..... | 719 | +| G.13.2.5 | Multiview acquisition information SEI message semantics..... | 719 | +| G.13.2.6 | Non-required view component SEI message semantics ..... | 722 | +| G.13.2.7 | View dependency change SEI message semantics ..... | 723 | +| G.13.2.8 | Operation point not present SEI message semantics..... | 724 | +| G.13.2.9 | Base view temporal HRD SEI message semantics ..... | 724 | +| G.13.2.10 | Multiview view position SEI message semantics ..... | 725 | +| G.14 | Video usability information ..... | 725 | +| G.14.1 | MVC VUI parameters extension syntax ..... | 725 | +| G.14.2 | MVC VUI parameters extension semantics ..... | 726 | +| Annex H | – Multiview and depth video coding..... | 728 | +| H.1 | Scope..... | 728 | +| H.2 | Normative references ..... | 728 | +| H.3 | Definitions ..... | 728 | +| H.4 | Abbreviations..... | 729 | +| H.5 | Conventions ..... | 729 | +| H.6 | Source, coded, decoded and output data formats, scanning processes, and neighbouring relationships..... | 729 | +| H.7 | Syntax and semantics ..... | 729 | +| H.7.1 | Method of specifying syntax in tabular form ..... | 729 | + +| | | | +|----------|----------------------------------------------------------------------------------------------|-----| +| H.7.2 | Specification of syntax functions, categories, and descriptors..... | 729 | +| H.7.3 | Syntax in tabular form..... | 729 | +| H.7.3.1 | NAL unit syntax..... | 729 | +| H.7.3.2 | Raw byte sequence payloads and RBSP trailing bits syntax..... | 729 | +| H.7.3.3 | Slice header syntax ..... | 731 | +| H.7.3.4 | Slice data syntax ..... | 731 | +| H.7.3.5 | Macroblock layer syntax..... | 732 | +| H.7.4 | Semantics ..... | 732 | +| H.7.4.1 | NAL unit semantics ..... | 732 | +| H.7.4.2 | Raw byte sequence payloads and RBSP trailing bits semantics ..... | 739 | +| H.7.4.3 | Slice header semantics ..... | 741 | +| H.7.4.4 | Slice data semantics ..... | 742 | +| H.7.4.5 | Macroblock layer semantics ..... | 742 | +| H.8 | MVCD decoding process ..... | 742 | +| H.8.1 | MVCD decoding process for picture order count ..... | 743 | +| H.8.2 | MVC decoding process for reference picture lists construction..... | 743 | +| H.8.2.1 | Initialization process for reference picture list for inter-view prediction references ..... | 743 | +| H.8.2.2 | Modification process for reference picture lists..... | 743 | +| H.8.3 | MVCD decoded reference picture marking process ..... | 743 | +| H.8.4 | MVCD inter prediction and inter-view prediction process ..... | 743 | +| H.8.5 | Specification of sub-bitstreams ..... | 743 | +| H.8.5.1 | Derivation process for required anchor view components..... | 744 | +| H.8.5.2 | Derivation process for required non-anchor view components..... | 744 | +| H.8.5.3 | Sub-bitstream extraction process ..... | 744 | +| H.8.5.4 | Specification of the base view bitstream..... | 746 | +| H.8.5.5 | Specification of the stereoscopic texture bitstream..... | 746 | +| H.9 | Parsing process ..... | 746 | +| H.10 | Profiles and levels ..... | 746 | +| H.10.1 | Profiles ..... | 746 | +| H.10.1.1 | Multiview Depth High profile ..... | 746 | +| H.10.1.2 | MFC Depth High profile..... | 747 | +| H.10.2 | Levels..... | 748 | +| H.10.2.1 | Level limits common to Multiview Depth High profiles ..... | 748 | +| H.10.2.2 | Profile specific level limits ..... | 751 | +| H.11 | Byte stream format..... | 751 | +| H.12 | MVCD hypothetical reference decoder ..... | 752 | +| H.13 | MVCD SEI messages ..... | 752 | +| H.13.1 | SEI message syntax..... | 752 | +| H.13.1.1 | MVCD view scalability information SEI message syntax..... | 752 | +| H.13.1.2 | MVCD scalable nesting SEI message syntax ..... | 753 | +| H.13.1.3 | Depth representation information SEI message syntax..... | 754 | +| H.13.1.4 | 3D reference displays information SEI message syntax ..... | 755 | +| H.13.1.5 | Depth timing SEI message syntax ..... | 756 | +| H.13.1.6 | Alternative depth information SEI message syntax ..... | 756 | +| H.13.1.7 | Depth sampling information SEI message syntax..... | 758 | +| H.13.2 | SEI message semantics ..... | 758 | +| H.13.2.1 | MVCD view scalability information SEI message semantics..... | 761 | +| H.13.2.2 | MVCD scalable nesting SEI message semantics ..... | 761 | +| H.13.2.3 | Depth representation information SEI message semantics ..... | 762 | +| H.13.2.4 | 3D reference displays information SEI message semantics ..... | 765 | +| H.13.2.5 | Depth timing SEI message semantics ..... | 767 | +| H.13.2.6 | Alternative depth information SEI message semantics..... | 768 | +| H.13.2.7 | Depth sampling information SEI message semantics ..... | 771 | +| H.14 | Video usability information ..... | 773 | +| H.14.1 | MVCD VUI parameters extension syntax ..... | 773 | +| H.14.2 | MVCD VUI parameters extension semantics ..... | 773 | + +| | | +|---------------------------------------------------------------------------------------------------------------------------|-----| +| Annex I – Multiview and depth video with enhanced non-base view coding ..... | 776 | +| I.1 Scope..... | 776 | +| I.2 Normative references ..... | 776 | +| I.3 Definitions ..... | 776 | +| I.4 Abbreviations..... | 776 | +| I.5 Conventions ..... | 776 | +| I.6 Source, coded, decoded and output data formats, scanning processes, and neighbouring relationships..... | 776 | +| I.6.1 Inverse sub-macroblock partition scanning process..... | 776 | +| I.7 Syntax and semantics ..... | 777 | +| I.7.1 Method of specifying syntax in tabular form..... | 777 | +| I.7.2 Specification of syntax functions, categories, and descriptors..... | 777 | +| I.7.3 Syntax in tabular form..... | 777 | +| I.7.3.1 NAL unit syntax..... | 777 | +| I.7.3.2 Raw byte sequence payloads and RBSP trailing bits syntax..... | 778 | +| I.7.3.3 Slice header syntax ..... | 782 | +| I.7.3.4 Slice data syntax ..... | 785 | +| I.7.3.5 Macroblock layer syntax..... | 787 | +| I.7.3.6 Macroblock layer in 3D-AVC extension syntax..... | 787 | +| I.7.4 Semantics..... | 790 | +| I.7.4.1 NAL unit semantics ..... | 790 | +| I.7.4.2 Raw byte sequence payloads and RBSP trailing bits semantics ..... | 792 | +| I.7.4.3 Slice header semantics ..... | 797 | +| I.7.4.4 Slice data semantics ..... | 799 | +| I.7.4.5 Macroblock layer semantics ..... | 799 | +| I.7.4.6 Macroblock layer in 3D-AVC extension semantics..... | 800 | +| I.8 3D-AVC decoding process ..... | 801 | +| I.8.1 3D-AVC decoding process for reference picture lists construction..... | 802 | +| I.8.2 3D-AVC inter prediction, inter-view prediction, view synthesis prediction and adaptive luminance compensation ..... | 802 | +| I.8.2.1 Derivation process for motion vector components and reference indices..... | 805 | +| I.8.2.2 Derivation of prediction weights in depth-range-based weighted prediction..... | 814 | +| I.8.2.3 Derivation process for motion vectors and reference indices for adaptive luminance compensation..... | 816 | +| I.8.2.4 Derivation process for prediction weights in adaptive luminance compensation ..... | 816 | +| I.8.3 Specification of sub-bitstreams..... | 818 | +| I.8.4 Decoding process for depth range parameters ..... | 818 | +| I.9 Parsing process ..... | 819 | +| I.9.1 Alternative CABAC parsing process for slice data and macroblock layer in depth extension ..... | 819 | +| I.9.1.1 Initialization process ..... | 819 | +| I.9.1.2 Binarization process..... | 820 | +| I.9.1.3 Decoding process flow..... | 821 | +| I.10 Profiles and levels..... | 823 | +| I.10.1 Profiles ..... | 823 | +| I.10.1.1 Enhanced Multiview Depth High profile..... | 824 | +| I.10.2 Levels..... | 824 | +| I.10.2.1 Level limits for Enhanced Multiview Depth High profile ..... | 824 | +| I.10.2.2 Profile specific level limits ..... | 824 | +| I.11 Byte stream format..... | 825 | +| I.12 3D-AVC hypothetical reference decoder..... | 825 | +| I.13 3D-AVC SEI messages..... | 825 | +| I.13.1 SEI message syntax..... | 825 | +| I.13.1.1 Constrained depth parameter set identifier SEI message syntax..... | 825 | +| I.13.2 SEI message semantics ..... | 825 | +| I.13.2.1 Constrained depth parameter set identifier SEI message semantics ..... | 825 | +| I.14 Video usability information ..... | 826 | + +## List of Figures + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| Figure 6-1 – Nominal vertical and horizontal locations of 4:2:0 luma and chroma samples in a frame..... | 24 | +| Figure 6-2 – Nominal vertical and horizontal sampling locations of 4:2:0 samples in top and bottom fields ..... | 25 | +| Figure 6-3 – Nominal vertical and horizontal locations of 4:2:2 luma and chroma samples in a frame..... | 25 | +| Figure 6-4 – Nominal vertical and horizontal sampling locations of 4:2:2 samples top and bottom fields ..... | 26 | +| Figure 6-5 – Nominal vertical and horizontal locations of 4:4:4 luma and chroma samples in a frame..... | 26 | +| Figure 6-6 – Nominal vertical and horizontal sampling locations of 4:4:4 samples top and bottom fields ..... | 27 | +| Figure 6-7 – A picture with 11 by 9 macroblocks that is partitioned into two slices..... | 28 | +| Figure 6-8 – Partitioning of the decoded frame into macroblock pairs ..... | 28 | +| Figure 6-9 – Macroblock partitions, sub-macroblock partitions, macroblock partition scans, and sub-macroblock
partition scans ..... | 30 | +| Figure 6-10 – Scan for 4x4 luma blocks..... | 31 | +| Figure 6-11 – Scan for 8x8 luma blocks..... | 31 | +| Figure 6-12 – Neighbouring macroblocks for a given macroblock ..... | 32 | +| Figure 6-13 – Neighbouring macroblocks for a given macroblock in MBAFF frames..... | 33 | +| Figure 6-14 – Determination of the neighbouring macroblock, blocks, and partitions (informative) ..... | 34 | +| Figure 7-1 – Structure of an access unit not containing any NAL units with nal_unit_type equal to 0, 7, 8,
or in the range of 12 to 18, inclusive, or in the range of 20 to 31, inclusive..... | 74 | +| Figure 8-1 – Intra_4x4 prediction mode directions (informative) ..... | 136 | +| Figure 8-2 – Example for temporal direct-mode motion vector inference (informative) ..... | 165 | +| Figure 8-3 – Directional segmentation prediction (informative) ..... | 166 | +| Figure 8-4 – Integer samples (shaded blocks with upper-case letters) and fractional sample positions
(un-shaded blocks with lower-case letters) for quarter sample luma interpolation..... | 172 | +| Figure 8-5 – Fractional sample position dependent variables in chroma interpolation and surrounding
integer position samples A, B, C, and D..... | 174 | +| Figure 8-6 – Assignment of the indices of dcY to luma4x4BlkIdx ..... | 180 | +| Figure 8-7 – Assignment of the indices of dcC to chroma4x4BlkIdx: (a) ChromaArrayType equal to 1,
(b) ChromaArrayType equal to 2..... | 182 | +| Figure 8-8 – 4x4 block scans. (a) Zig-zag scan. (b) Field scan (informative) ..... | 183 | +| Figure 8-9 – 8x8 block scans. (a) 8x8 zig-zag scan. (b) 8x8 field scan (informative)..... | 184 | +| Figure 8-10 – Boundaries in a macroblock to be filtered..... | 202 | +| Figure 8-11 – Convention for describing samples across a 4x4 block horizontal or vertical boundary ..... | 206 | +| Figure 9-1 – Illustration of CABAC parsing process for a syntax element SE (informative) ..... | 228 | +| Figure 9-2 – Overview of the arithmetic decoding process for a single bin (informative)..... | 275 | +| Figure 9-3 – Flowchart for decoding a decision ..... | 277 | +| Figure 9-4 – Flowchart of renormalization..... | 279 | +| Figure 9-5 – Flowchart of bypass decoding process..... | 280 | +| Figure 9-6 – Flowchart of decoding a decision before termination ..... | 281 | +| Figure 9-7 – Flowchart for encoding a decision ..... | 283 | +| Figure 9-8 – Flowchart of renormalization in the encoder ..... | 284 | +| Figure 9-9 – Flowchart of PutBit(B)..... | 285 | +| Figure 9-10 – Flowchart of encoding bypass..... | 286 | +| Figure 9-11 – Flowchart of encoding a decision before termination ..... | 287 | +| Figure 9-12 – Flowchart of flushing at termination..... | 287 | +| Figure C-1 – Structure of byte streams and NAL unit streams for HRD conformance checks ..... | 313 | +| Figure C-2 – HRD buffer model..... | 315 | + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| Figure D-1 – Rearrangement and upconversion of checkerboard interleaving (frame_packing_arrangement_type equal to 0) ..... | 394 | +| Figure D-2 – Rearrangement and upconversion of column interleaving with frame_packing_arrangement_type equal to 1, quincunx_sampling_flag equal to 0, and (x, y) equal to (0, 0) or (4, 8) for both constituent frames .... | 394 | +| Figure D-3 – Rearrangement and upconversion of column interleaving with frame_packing_arrangement_type equal to 1, quincunx_sampling_flag equal to 0, (x, y) equal to (0, 0) or (4, 8) for constituent frame 0 and (x, y) equal to (12, 8) for constituent frame 1 ..... | 395 | +| Figure D-4 – Rearrangement and upconversion of row interleaving with frame_packing_arrangement_type equal to 2, quincunx_sampling_flag equal to 0, and (x, y) equal to (0, 0) or (8, 4) for both constituent frames .... | 395 | +| Figure D-5 – Rearrangement and upconversion of row interleaving with frame_packing_arrangement_type equal to 2, quincunx_sampling_flag equal to 0, (x, y) equal to (0, 0) or (8, 4) for constituent frame 0, and (x, y) equal to (8, 12) for constituent frame 1 ..... | 396 | +| Figure D-6 – Rearrangement and upconversion of side-by-side packing arrangement with frame_packing_arrangement_type equal to 3, quincunx_sampling_flag equal to 0, and (x, y) equal to (0, 0) or (4, 8) for both constituent frames ..... | 396 | +| Figure D-7 – Rearrangement and upconversion of side-by-side packing arrangement with frame_packing_arrangement_type equal to 3, quincunx_sampling_flag equal to 0, (x, y) equal to (12, 8) for constituent frame 0, and (x, y) equal to (0, 0) or (4, 8) for constituent frame 1 ..... | 397 | +| Figure D-8 – Rearrangement and upconversion of top-bottom packing arrangement with frame_packing_arrangement_type equal to 4, quincunx_sampling_flag equal to 0, and (x, y) equal to (0, 0) or (8, 4) for both constituent frames ..... | 398 | +| Figure D-9 – Rearrangement and upconversion of top-bottom packing arrangement with frame_packing_arrangement_type equal to 4, quincunx_sampling_flag equal to 0, (x, y) equal to (8, 12) for constituent frame 0, and (x, y) equal to (0, 0) or (8, 4) for constituent frame 1 ..... | 399 | +| Figure D-10 – Rearrangement and upconversion of side-by-side packing arrangement with quincunx sampling (frame_packing_arrangement_type equal to 3 with quincunx_sampling_flag equal to 1) ..... | 399 | +| Figure D-11 – Rearrangement of a temporal interleaving frame arrangement (frame_packing_arrangement_type equal to 5) ..... | 400 | +| Figure D-12 – Rearrangement and upconversion of tile format packing arrangement (frame_packing_arrangement_type equal to 7) ..... | 400 | +| Figure E-1 – Location of chroma samples for top and bottom fields for chroma_format_idc equal to 1 (4:2:0 chroma format) as a function of chroma_sample_loc_type_top_field and chroma_sample_loc_type_bottom_field..... | 443 | + +## List of Tables + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|-----| +| Table 5-1 – Operation precedence from highest (at top of table) to lowest (at bottom of table) ..... | 20 | +| Table 6-1 – SubWidthC, and SubHeightC values derived from chroma_format_idc and separate_colour_plane_flag .. | 23 | +| Table 6-2 – Specification of input and output assignments for clauses 6.4.11.1 to 6.4.11.7 ..... | 34 | +| Table 6-3 – Specification of mbAddrN ..... | 38 | +| Table 6-4 – Specification of mbAddrN and yM ..... | 40 | +| Table 7-1 – NAL unit type codes, syntax element categories, and NAL unit type classes..... | 67 | +| Table 7-2 – Assignment of mnemonic names to scaling list indices and specification of fall-back rule..... | 79 | +| Table 7-3 – Specification of default scaling lists Default_4x4_Intra and Default_4x4_Inter ..... | 79 | +| Table 7-4 – Specification of default scaling lists Default_8x8_Intra and Default_8x8_Inter ..... | 80 | +| Table 7-5 – Meaning of primary_pic_type ..... | 88 | +| Table 7-6 – Name association to slice_type ..... | 90 | +| Table 7-7 – modification_of_pic_nums_idc operations for modification of reference picture lists ..... | 96 | +| Table 7-8 – Interpretation of adaptive_ref_pic_marking_mode_flag ..... | 98 | +| Table 7-9 – Memory management control operation ( memory_management_control_operation ) values ..... | 99 | +| Table 7-10 – Allowed collective macroblock types for slice_type ..... | 102 | +| Table 7-11 – Macroblock types for I slices ..... | 103 | +| Table 7-12 – Macroblock type with value 0 for SI slices ..... | 104 | +| Table 7-13 – Macroblock type values 0 to 4 for P and SP slices..... | 105 | +| Table 7-14 – Macroblock type values 0 to 22 for B slices..... | 106 | +| Table 7-15 – Specification of CodedBlockPatternChroma values..... | 108 | +| Table 7-16 – Relationship between intra_chroma_pred_mode and spatial prediction modes..... | 109 | +| Table 7-17 – Sub-macroblock types in P macroblocks..... | 110 | +| Table 7-18 – Sub-macroblock types in B macroblocks ..... | 111 | +| Table 8-1 – Refined slice group map type ..... | 120 | +| Table 8-2 – Specification of Intra4x4PredMode[ luma4x4BlkIdx ] and associated names ..... | 136 | +| Table 8-3 – Specification of Intra8x8PredMode[ luma8x8BlkIdx ] and associated names ..... | 142 | +| Table 8-4 – Specification of Intra16x16PredMode and associated names ..... | 149 | +| Table 8-5 – Specification of Intra chroma prediction modes and associated names..... | 151 | +| Table 8-6 – Specification of the variable colPic ..... | 159 | +| Table 8-7 – Specification of PicCodingStruct( X ) ..... | 159 | +| Table 8-8 – Specification of mbAddrCol , yM , and vertMvScale ..... | 160 | +| Table 8-9 – Assignment of prediction utilization flags..... | 162 | +| Table 8-10 – Derivation of the vertical component of the chroma vector in field coding mode ..... | 168 | +| Table 8-11 – Differential full-sample luma locations ..... | 172 | +| Table 8-12 – Assignment of the luma prediction sample predPartLXL[ xL, yL ] ..... | 174 | +| Table 8-13 – Specification of mapping of idx to $c_{ij}$ for zig-zag and field scan..... | 184 | +| Table 8-14 – Specification of mapping of idx to $c_{ij}$ for 8x8 zig-zag and 8x8 field scan..... | 185 | +| Table 8-15 – Specification of QPc as a function of qP1 ..... | 186 | +| Table 8-16 – Derivation of offset dependent threshold variables $\alpha'$ and $\beta'$ from indexA and indexB ..... | 210 | + +| | | +|---------------------------------------------------------------------------------------------------------------|-----| +| Table 8-17 – Value of variable $t'_{c0}$ as a function of indexA and bS..... | 210 | +| Table 9-1 – Bit strings with "prefix" and "suffix" bits and assignment to codeNum ranges (informative) ..... | 213 | +| Table 9-2 – Exp-Golomb bit strings and codeNum in explicit form and used as $ue(v)$ (informative)..... | 213 | +| Table 9-3 – Assignment of syntax element to codeNum for signed Exp-Golomb coded syntax elements $se(v)$ ..... | 214 | +| Table 9-4 – Assignment of codeNum to values of coded_block_pattern for macroblock prediction modes ..... | 215 | +| Table 9-5 – coeff_token mapping to TotalCoeff( coeff_token ) and TrailingOnes( coeff_token )..... | 219 | +| Table 9-6 – Codeword table for level_prefix (informative)..... | 222 | +| Table 9-7 – total_zeros tables for 4x4 blocks with tzVlcIndex 1 to 7 ..... | 224 | +| Table 9-8 – total_zeros tables for 4x4 blocks with tzVlcIndex 8 to 15 ..... | 224 | +| Table 9-9 – total_zeros tables for chroma DC 2x2 and 2x4 blocks..... | 225 | +| Table 9-10 – Tables for run_before ..... | 226 | +| Table 9-11 – Association of ctxIdx and syntax elements for each slice type in the initialization process..... | 230 | +| Table 9-12 – Values of variables m and n for ctxIdx from 0 to 10..... | 231 | +| Table 9-13 – Values of variables m and n for ctxIdx from 11 to 23..... | 232 | +| Table 9-14 – Values of variables m and n for ctxIdx from 24 to 39..... | 232 | +| Table 9-15 – Values of variables m and n for ctxIdx from 40 to 53..... | 232 | +| Table 9-16 – Values of variables m and n for ctxIdx from 54 to 59, and 399 to 401 ..... | 233 | +| Table 9-17 – Values of variables m and n for ctxIdx from 60 to 69..... | 233 | +| Table 9-18 – Values of variables m and n for ctxIdx from 70 to 104..... | 234 | +| Table 9-19 – Values of variables m and n for ctxIdx from 105 to 165..... | 235 | +| Table 9-20 – Values of variables m and n for ctxIdx from 166 to 226..... | 236 | +| Table 9-21 – Values of variables m and n for ctxIdx from 227 to 275..... | 237 | +| Table 9-22 – Values of variables m and n for ctxIdx from 277 to 337..... | 238 | +| Table 9-23 – Values of variables m and n for ctxIdx from 338 to 398..... | 239 | +| Table 9-24 – Values of variables m and n for ctxIdx from 402 to 459..... | 240 | +| Table 9-25 – Values of variables m and n for ctxIdx from 460 to 483..... | 241 | +| Table 9-26 – Values of variables m and n for ctxIdx from 484 to 571..... | 241 | +| Table 9-27 – Values of variables m and n for ctxIdx from 572 to 659..... | 243 | +| Table 9-28 – Values of variables m and n for ctxIdx from 660 to 717..... | 245 | +| Table 9-29 – Values of variables m and n for ctxIdx from 718 to 775..... | 246 | +| Table 9-30 – Values of variables m and n for ctxIdx from 776 to 863..... | 247 | +| Table 9-31 – Values of variables m and n for ctxIdx from 864 to 951..... | 249 | +| Table 9-32 – Values of variables m and n for ctxIdx from 952 to 1011..... | 251 | +| Table 9-33 – Values of variables m and n for ctxIdx from 1012 to 1023..... | 252 | +| Table 9-34 – Syntax elements and associated types of binarization, maxBinIdxCtx, and ctxIdxOffset..... | 253 | +| Table 9-35 – Bin string of the unary binarization (informative)..... | 256 | +| Table 9-36 – Binarization for macroblock types in I slices ..... | 258 | +| Table 9-37 – Binarization for macroblock types in P, SP, and B slices..... | 259 | +| Table 9-38 – Binarization for sub-macroblock types in P, SP, and B slices..... | 260 | + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| Table 9-39 – Assignment of ctxIdxInc to binIdx for all ctxIdxOffset values except those related to the syntax elements coded_block_flag, significant_coeff_flag, last_significant_coeff_flag, and coeff_abs_level_minus1 ..... | 262 | +| Table 9-40 – Assignment of ctxIdxBlockCatOffset to ctxBlockCat for syntax elements coded_block_flag, significant_coeff_flag, last_significant_coeff_flag, and coeff_abs_level_minus1 ..... | 263 | +| Table 9-41 – Specification of ctxIdxInc for specific values of ctxIdxOffset and binIdx ..... | 271 | +| Table 9-42 – Specification of ctxBlockCat for the different blocks ..... | 272 | +| Table 9-43 – Mapping of scanning position to ctxIdxInc for ctxBlockCat == 5, 9, or 13 ..... | 273 | +| Table 9-44 – Specification of rangeTabLPS depending on pStateIdx and qCodIRangeIdx ..... | 278 | +| Table 9-45 – State transition table ..... | 279 | +| Table A-1 – Level limits ..... | 298 | +| Table A-2 – Specification of cpbBrVclFactor and cpbBrNalFactor ..... | 302 | +| Table A-3 – Baseline and Constrained Baseline profile level limits ..... | 302 | +| Table A-4 – Main, High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profile level limits ..... | 303 | +| Table A-5 – Extended profile level limits ..... | 304 | +| Table A-6 – Maximum frame rates (frames per second) for some example frame sizes ..... | 305 | +| Table A-7 – Maximum DPB size (frames) for some example frame sizes ..... | 308 | +| Table D-1 – Interpretation of pic_struct ..... | 358 | +| Table D-2 – Mapping of ct_type to source picture scan ..... | 359 | +| Table D-3 – Definition of counting_type values ..... | 360 | +| Table D-4 – scene_transition_type values ..... | 367 | +| Table D-5 – film_grain_model_id values ..... | 375 | +| Table D-6 – blending_mode_id values ..... | 376 | +| Table D-7 – filter_hint_type values ..... | 384 | +| Table D-8 – Interpretation of camera_iso_speed_idc and exposure_index_idc ..... | 387 | +| Table D-9 – Definition of frame_packing_arrangement_type ..... | 389 | +| Table D-10 – Definition of content_interpretation_type ..... | 391 | +| Table D-11 – transform_type[ i ] values ..... | 413 | +| Table D-12– manifest_sei_description[ i ] values ..... | 423 | +| Table E-1 – Meaning of sample aspect ratio indicator ..... | 431 | +| Table E-2 – Meaning of video_format ..... | 432 | +| Table E-3 – Colour primaries interpretation using colour_primaries syntax element ..... | 433 | +| Table E-4 – Transfer characteristics interpretation using transfer_characteristics syntax element ..... | 434 | +| Table E-5 – Matrix coefficients interpretation using the matrix_coefficients syntax element ..... | 441 | +| Table E-6 – Divisor for computation of $\Delta t_{fi,dpb}(n)$ ..... | 444 | +| Table F-1 – Name association to slice_type for NAL units with nal_unit_type equal to 20 ..... | 487 | +| Table F-2 – Interpretation of adaptive_ref_base_pic_marking_mode_flag ..... | 496 | +| Table F-3 – Memory management base control operation (memory_management_base_control_operation) values ..... | 496 | +| Table F-4 – Allowed collective macroblock types for slice_type ..... | 499 | +| Table F-5 – Inferred macroblock type I_BL for EI slices ..... | 500 | + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| Table F-6 – Scale values cS for transform coefficient level scaling..... | 560 | +| Table F-7 – Macroblock type predictors mbTypeILPred ..... | 576 | +| Table F-8 – Sub-macroblock type predictors subMbTypeILPred[ mbPartIdx ] ..... | 577 | +| Table F-9 – 16-phase luma interpolation filter for resampling in Intra_Base prediction..... | 586 | +| Table F-10 – Mapping of ( nX, nY ) to coeffTokenIdx and vice versa ..... | 611 | +| Table F-11 – Association of ctxIdx and syntax elements for each slice type in the initialization process ..... | 615 | +| Table F-12 – Values of variables m and n for ctxIdx from 1024 to 1026..... | 615 | +| Table F-13 – Values of variables m and n for ctxIdx from 1027 to 1030..... | 615 | +| Table F-14 – Syntax elements and associated types of binarization, maxBinIdxCtx, and ctxIdxOffset ..... | 616 | +| Table F-15 – Assignment of ctxIdxInc to binIdx for the ctxIdxOffset values related to the syntax elements
base_mode_flag and residual_prediction_flag..... | 616 | +| Table F-16 – Scalable Baseline and Scalable Constrained Baseline profile level limits ..... | 627 | +| Table F-17 – Specification of cpbBrVclFactor and cpbBrNalFactor ..... | 628 | +| Table G-1 – Association between frame packing arrangement type and syntax elements ..... | 680 | +| Table G-2 – modification_of_pic_nums_idc operations for modification of reference picture lists ..... | 684 | +| Table G-3 – Association between camera parameter variables and syntax elements ..... | 722 | +| Table H-1 – Definition of depth_representation_type ..... | 763 | +| Table H-2 – Association between depth parameter variables and syntax elements..... | 763 | +| Table H-3 – Association between camera parameter variables and syntax elements ..... | 766 | +| Table H-4 – Locations of the top-left luma samples of constituent pictures packed in a non-base texture view
relative to the top-left luma sample of this picture ..... | 768 | +| Table I-1 – Respective syntax elements for pre_slice_header_src, pre_ref_lists_src, pre_pred_weight_table_src
and pre_dec_ref_pic_marking_src..... | 798 | +| Table I-2 – Semantics of the values of pre_slice_header_src, pre_ref_lists_src, pre_pred_weight_table_src and
pre_dec_ref_pic_marking_src ..... | 798 | +| Table I-3 – Macroblock type values 0 to 4 for P and SP slices ..... | 800 | +| Table I-4 – Association between depth parameter variables and syntax elements ..... | 819 | +| Table I-5 – Association of ctxIdx and syntax elements in the initialization process ..... | 820 | +| Table I-6 – Values of variables m and n for ctxIdx from 1031 to 1039..... | 820 | +| Table I-7 – Values of variables m and n for ctxIdx from 1040 to 1052..... | 820 | +| Table I-8 – Syntax elements and associated types of binarization, maxBinIdxCtx, and ctxIdxOffset ..... | 821 | +| Table I-9 – Assignment of ctxIdxInc to binIdx for the ctxIdxOffset values related to the syntax elements
mb_vsskip_flag, mb_direct_type_flag, mb_alc_skip_flag, mb_alc_flag and mb_vsp_flag ..... | 822 | + +## Advanced video coding for generic audiovisual services + +### 0 Introduction + +This clause and its subclauses do not form an integral part of this Recommendation | International Standard. + +#### 0.1 Prologue + +This clause does not form an integral part of this Recommendation | International Standard. + +As the costs for both processing power and memory have reduced, network support for coded video data has diversified, and advances in video coding technology have progressed, the need has arisen for an industry standard for compressed video representation with substantially increased coding efficiency and enhanced robustness to network environments. Toward these ends the ITU-T Video Coding Experts Group (VCEG) and the ISO/IEC Moving Picture Experts Group (MPEG) formed a Joint Video Team (JVT) in 2001 for development of a new Recommendation | International Standard. The standard has since been maintained and enhanced jointly by VCEG and MPEG. + +#### 0.2 Purpose + +This clause does not form an integral part of this Recommendation | International Standard. + +This Recommendation | International Standard was developed in response to the growing need for higher compression of moving pictures for various applications such as videoconferencing, digital storage media, television broadcasting, internet streaming, and communication. It is also designed to enable the use of the coded video representation in a flexible manner for a wide variety of network environments. The use of this Recommendation | International Standard allows motion video to be manipulated as a form of computer data and to be stored on various storage media, transmitted and received over existing and future networks and distributed on existing and future broadcasting channels. + +#### 0.3 Applications + +This clause does not form an integral part of this Recommendation | International Standard. + +This Recommendation | International Standard is designed to cover a broad range of applications for video content including but not limited to the following: + +- CATV Cable TV on optical networks, copper, etc. +- DBS Direct broadcast satellite video services +- DSL Digital subscriber line video services +- DTTB Digital terrestrial television broadcasting +- ISM Interactive storage media (optical disks, etc.) +- MMM Multimedia mailing +- MSPN Multimedia services over packet networks +- RTC Real-time conversational services (videoconferencing, videophone, etc.) +- RVS Remote video surveillance +- SSM Serial storage media (digital VTR, etc.) + +#### 0.4 Publication and versions of this Specification + +This clause does not form an integral part of this Recommendation | International Standard. + +This Specification has been jointly developed by ITU-T Video Coding Experts Group (VCEG) and the ISO/IEC Moving Picture Experts Group. It is published as technically-aligned twin text in both organizations ITU-T and ISO/IEC. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 1 refers to the first approved version of this Recommendation | International Standard. Version 1 was approved by ITU-T on 30 May 2003. The first published version in ISO/IEC corresponded to version 1. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 2 refers to the integrated text containing the corrections specified in the first technical corrigendum. The first fully-published version in the ITU-T was version 2 as approved by ITU-T on 7 May 2004, due to the development of the corrigendum during the publication process. Version 2 was also published in integrated form by ISO/IEC. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 3 refers to the integrated text containing both the first technical corrigendum (2004) and the first amendment, which is referred to as the "Fidelity range extensions". Version 3 was approved by ITU-T on 1 March 2005. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 4 refers to the integrated text containing the first technical corrigendum (2004), the first amendment (the "Fidelity range extensions"), and an additional technical corrigendum (2005). Version 4 was approved by ITU-T on 13 September 2005. In both ITU-T and ISO/IEC, the next complete published version after version 2 was version 4. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 5 refers to the integrated version 4 text with its specification of the High 4:4:4 profile removed. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 6 refers to the integrated version 5 text after its amendment to support additional colour space indicators. In the ITU-T, the changes for versions 5 and 6 were approved on 13 June 2006 and were published as a single amendment. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 7 refers to the integrated version 6 text after its amendment to define five new profiles intended primarily for professional applications (the High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, CAVLC 4:4:4 Intra, and High 4:4:4 Predictive profiles) and two new types of supplemental enhancement information (SEI) messages (the post-filter hint SEI message and the tone mapping information SEI message). Version 7 was approved by ITU-T on 6 April 2007. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 8 refers to the integrated version 7 text after its amendment to specify scalable video coding in three profiles (Scalable Baseline, Scalable High, and Scalable High Intra profiles). Version 8 was approved by ITU-T on 22 November 2007. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 9 refers to the integrated version 8 text after applying the corrections specified in a third technical corrigendum. Version 9 was approved by ITU-T on 13 January 2009. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 10 refers to the integrated version 9 text after its amendment to specify a profile for multiview video coding (the Multiview High profile) and to define additional SEI messages. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 11 refers to the integrated version 10 text after its amendment to define a new profile (the Constrained Baseline profile) intended primarily to enable implementation of decoders supporting only the common subset of capabilities supported in various previously-specified profiles. In the ITU-T, the changes for versions 10 and 11 were approved on 16 March 2009. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 12 refers to the integrated version 11 text after its amendment to define a new profile (the Stereo High profile) for two-view video coding with support of interlaced coding tools and to specify an additional SEI message specified as the frame packing arrangement SEI message. The changes for versions 11 and 12 were processed as a single amendment in the ISO/IEC approval process. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 13 refers to the integrated version 12 text with various minor corrections and clarifications as specified in a fourth technical corrigendum. In the ITU-T, the changes for versions 12 and 13 were approved on 9 March 2010. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 14 refers to the integrated version 13 text after its amendment to define a new level (Level 5.2) supporting higher processing rates in terms of maximum macroblocks per second and a new profile (the Progressive High profile) to enable implementation of decoders supporting only the frame coding tools of the previously-specified High profile. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 15 refers to the integrated version 14 text with miscellaneous corrections and clarifications as specified in a fifth technical corrigendum. In the ITU-T, the changes for versions 14 and 15 were approved on 29 June 2011. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 16 refers to the integrated version 15 text after its amendment to define three new profiles intended primarily for communication applications (the Constrained High, Scalable Constrained Baseline, and Scalable Constrained High profiles). In the ITU-T, the changes for version 16 were approved on 13 January 2012. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 17-T refers to the integrated version 16 text after its amendment to define additional supplemental enhancement information (SEI) message data, including the multiview view position SEI message, the display orientation SEI message, and an additional frame packing arrangement type indication value for the frame packing arrangement SEI message (the 2D content type indication value). + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 18-T refers to the integrated version 17-T text after its amendment to specify the coding of depth signals, including the specification of an additional profile, the Multiview Depth High profile. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 19-T refers to the integrated version 18-T text after incorporating a correction to the sub-bitstream extraction process for multiview video coding. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 20-T refers to the integrated version 19-T text after its amendment to specify additional colorimetry identifiers and an additional model type in the tone mapping information SEI message. In the ITU-T, the changes for versions 17-T, 18-T, 19-T, and 20-T were approved on 13 April 2013. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 21-T refers to the integrated version 20-T text after its amendment to define an additional frame packing arrangement type indication values for the frame packing arrangement SEI message (the tiled arrangement type indication value) and to specify the combined coding of video view and depth enhancement, including the specification of an additional profile, the Enhanced Multiview Depth High profile. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 22 refers to the integrated version 21-T text after its amendment to specify multi-resolution frame-compatible (MFC) enhancement for stereoscopic video coding, including the specification of an additional profile, the MFC High profile, and the inclusion of miscellaneous minor corrections and clarifications. In the ITU-T, the changes for versions 21-T and 22 were approved on 12 February 2014. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 23 refers to the integrated version 22 text after its amendment to specify multi-resolution frame-compatible (MFC) stereoscopic video with depth maps, including the specification of an additional profile, the MFC Depth High profile, and the mastering display colour volume SEI message, additional colour-related video usability information codepoint identifiers, and introduces miscellaneous minor corrections and clarifications. In the ITU-T, the changes for version 23 were approved on 13 February 2016. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 24 refers to the integrated version 23 text after its amendment to specify additional levels of decoder capability supporting larger picture sizes (Levels 6, 6.1, and 6.2), the green metadata SEI message, the alternative depth information SEI message, additional colour-related video usability information codepoint identifiers, and introduces miscellaneous minor corrections and clarifications. In the ITU-T, the changes for version 24 were approved on 14 October 2016. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 25 refers to the integrated version 24 text after its amendment to specify the Progressive High 10 profile; support for additional colour-related indicators, including the hybrid log-gamma transfer characteristics indication, the alternative transfer characteristics SEI message, the $IC_T C_P$ colour matrix transformation, chromaticity-derived constant luminance and non-constant luminance colour matrix coefficients, the colour remapping information SEI message, and introduces miscellaneous minor corrections and clarifications. In the ITU-T, the changes for version 25 were approved on 13 April 2017. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 26 refers to the integrated version 25 text after its amendment to specify additional SEI messages for ambient viewing environment, content light level information, content colour volume, equirectangular projection, cubemap projection, sphere rotation, region-wise packing, omnidirectional viewport, SEI manifest, and SEI prefix, and introduces miscellaneous minor corrections and clarifications. In the ITU-T, the changes for version 26 were approved on 13 June 2019. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 27 refers to the integrated version 26 text after its amendment to specify additional SEI messages for annotated regions and shutter interval information, and introduces miscellaneous minor corrections and clarifications. In the ITU-T, the changes for version 27 were approved on 22 August 2021. + +Rec. ITU-T H.264 | ISO/IEC 14496-10 version 28 (the current Specification) refers to the integrated version 27 text after its amendment to specify additional SEI messages for neural-network post-filter characteristics, neural-network post-filter activation, and phase indication (through referencing to Rec. ITU-T H.274 | ISO/IEC 23002-7), additional colour type identifiers, and miscellaneous minor corrections and clarifications. In the ITU-T, the changes for version 28 were approved on 13 August 2024. + +NOTE – Users of versions previous to Rec. ITU-T H.264 | ISO/IEC 14496-10 version 28 are forewarned that, since previous placeholder Annex F was removed in this version, all subsequent annexes, clauses, tables, figures and equations were renumbered. + +## 0.5 Profiles and levels + +This clause does not form an integral part of this Recommendation | International Standard. + +This Recommendation | International Standard is designed to be generic in the sense that it serves a wide range of applications, bit rates, resolutions, qualities, and services. Applications should cover, among other things, digital storage media, television broadcasting and real-time communications. In the course of creating this Specification, various requirements from typical applications have been considered, necessary algorithmic elements have been developed, and these have been integrated into a single syntax. Hence, this Specification will facilitate video data interchange among different applications. + +Considering the practicality of implementing the full syntax of this Specification, however, a limited number of subsets of the syntax are also stipulated by means of "profiles" and "levels". These and other related terms are formally defined in clause 3. + +A "profile" is a subset of the entire bitstream syntax that is specified by this Recommendation | International Standard. Within the bounds imposed by the syntax of a given profile it is still possible to require a very large variation in the performance of encoders and decoders depending upon the values taken by syntax elements in the bitstream such as the specified size of the decoded pictures. In many applications, it is currently neither practical nor economic to implement a decoder capable of dealing with all hypothetical uses of the syntax within a particular profile. + +In order to deal with this problem, "levels" are specified within each profile. A level is a specified set of constraints imposed on values of the syntax elements in the bitstream. These constraints may be simple limits on values. Alternatively they may take the form of constraints on arithmetic combinations of values (e.g., picture width multiplied by picture height multiplied by number of pictures decoded per second). + +Coded video content conforming to this Recommendation | International Standard uses a common syntax. In order to achieve a subset of the complete syntax, flags, parameters, and other syntax elements are included in the bitstream that signal the presence or absence of syntactic elements that occur later in the bitstream. + +## 0.6 Overview of the design characteristics + +This clause does not form an integral part of this Recommendation | International Standard. + +The coded representation specified in the syntax is designed to enable a high compression capability for a desired image quality. With the exception of the transform bypass mode of operation for lossless coding in the High 4:4:4 Intra, CAVLC 4:4:4 Intra, and High 4:4:4 Predictive profiles, and the I\_PCM mode of operation in all profiles, the algorithm is typically not lossless, as the exact source sample values are typically not preserved through the encoding and decoding processes. A number of techniques may be used to achieve highly efficient compression. Encoding algorithms (not specified in this Recommendation | International Standard) may select between inter and intra coding for block-shaped regions of each picture. Inter coding uses motion vectors for block-based inter prediction to exploit temporal statistical dependencies between different pictures. Intra coding uses various spatial prediction modes to exploit spatial statistical dependencies in the source signal for a single picture. Motion vectors and intra prediction modes may be specified for a variety of block sizes in the picture. The prediction residual is then further compressed using a transform to remove spatial correlation inside the transform block before it is quantized, producing an irreversible process that typically discards less important visual information while forming a close approximation to the source samples. Finally, the motion vectors or intra prediction modes are combined with the quantized transform coefficient information and encoded using either variable length coding or arithmetic coding. + +Scalable video coding is specified in Annex F allowing the construction of bitstreams that contain sub-bitstreams that conform to this Specification. For temporal bitstream scalability, i.e., the presence of a sub-bitstream with a smaller temporal sampling rate than the bitstream, complete access units are removed from the bitstream when deriving the sub-bitstream. In this case, high-level syntax and inter prediction reference pictures in the bitstream are constructed accordingly. For spatial and quality bitstream scalability, i.e., the presence of a sub-bitstream with lower spatial resolution or quality than the bitstream, NAL units are removed from the bitstream when deriving the sub-bitstream. In this case, inter-layer prediction, i.e., the prediction of the higher spatial resolution or quality signal by data of the lower spatial resolution or quality signal, is typically used for efficient coding. Otherwise, the coding algorithm as described in the previous paragraph is used. + +Multiview video coding is specified in Annex G allowing the construction of bitstreams that represent multiple views. Similar to scalable video coding, bitstreams that represent multiple views may also contain sub-bitstreams that conform to this Specification. For temporal bitstream scalability, i.e., the presence of a sub-bitstream with a smaller temporal sampling rate than the bitstream, complete access units are removed from the bitstream when deriving the sub-bitstream. In this case, high-level syntax and inter prediction reference pictures in the bitstream are constructed accordingly. For view bitstream scalability, i.e., the presence of a sub-bitstream with fewer views than the bitstream, NAL units are removed from the bitstream when deriving the sub-bitstream. In this case, inter-view prediction, i.e., the prediction of one view signal by data of another view signal, is typically used for efficient coding. Otherwise, the coding algorithm as described in the previous paragraph is used. + +An extension of multiview video coding that additionally supports the inclusion of depth maps is specified in Annex H, allowing the construction of bitstreams that represent multiple views with corresponding depth views. In a similar manner, as with the multiview video coding specified in Annex G, bitstreams encoded as specified in Annex H may also contain sub-bitstreams that conform to this Specification. + +A multiview video coding extension with depth information is specified in Annex I. Sub-bitstreams consisting of a texture base view conform to this Specification, sub-bitstreams consisting of multiple texture views may also conform to Annex G of this Specification, and sub-bitstreams consisting of one or more texture views and one or more depth views may also + +conform to Annex H of this Specification. Enhanced texture view coding that utilizes the associated depth views and decoding processes for depth views are specified for this extension. + +Rec. ITU-T H.274 | ISO/IEC 23002-7 specifies the syntax and semantics of supplemental enhancement information (SEI) messages that do not affect the conformance specifications in Annex C and clauses F.12, G.12, H.12 and I.12. Among these SEI messages, those for which the syntax and semantics are not specified in this Specification may be used together with this Specification. SEI messages for which the syntax and semantics are specified in this Specification may always be used together with this Specification. To enable being used together with this Specification, the SEI payload type value of an SEI message specified in Rec. ITU-T H.274 | ISO/IEC 23002-7 needs to be specified in this Specification. For example, the SEI payload type value 202 (for the annotated regions SEI message) is specified in clause D.1.1, while the syntax and semantics of that SEI message are specified in Rec. ITU-T H.274 | ISO/IEC 23002-7. + +#### **0.6.1 Predictive coding** + +This clause does not form an integral part of this Recommendation | International Standard. + +Because of the conflicting requirements of random access and highly efficient compression, two main coding types are specified. Intra coding is done without reference to other pictures. Intra coding may provide access points to the coded sequence where decoding can begin and continue correctly, but typically also shows only moderate compression efficiency. Inter coding (predictive or bi-predictive) is more efficient using inter prediction of each block of sample values from some previously decoded picture selected by the encoder. In contrast to some other video coding standards, pictures coded using bi-predictive inter prediction may also be used as references for inter coding of other pictures. + +The application of the three coding types to pictures in a sequence is flexible, and the order of the decoding process is generally not the same as the order of the source picture capture process in the encoder or the output order from the decoder for display. The choice is left to the encoder and will depend on the requirements of the application. The decoding order is specified such that the decoding of pictures that use inter-picture prediction follows later in decoding order than other pictures that are referenced in the decoding process. + +#### **0.6.2 Coding of progressive and interlaced video** + +This clause does not form an integral part of this Recommendation | International Standard. + +This Recommendation | International Standard specifies a syntax and decoding process for video that originated in either progressive-scan or interlaced-scan form, which may be mixed together in the same sequence. The two fields of an interlaced frame are separated in capture time while the two fields of a progressive frame share the same capture time. Each field may be coded separately or the two fields may be coded together as a frame. Progressive frames are typically coded as a frame. For interlaced video, the encoder can choose between frame coding and field coding. Frame coding or field coding can be adaptively selected on a picture-by-picture basis and also on a more localized basis within a coded frame. Frame coding is typically preferred when the video scene contains significant detail with limited motion. Field coding typically works better when there is fast picture-to-picture motion. + +#### **0.6.3 Picture partitioning into macroblocks and smaller partitions** + +This clause does not form an integral part of this Recommendation | International Standard. + +As in previous video coding Recommendations and International Standards, a macroblock, consisting of a 16x16 block of luma samples and two corresponding blocks of chroma samples, is used as the basic processing unit of the video decoding process. + +A macroblock can be further partitioned for inter prediction. The selection of the size of inter prediction partitions is a result of a trade-off between the coding gain provided by using motion compensation with smaller blocks and the quantity of data needed to represent the data for motion compensation. In this Recommendation | International Standard the inter prediction process can form segmentations for motion representation as small as 4x4 luma samples in size, using motion vector accuracy of one-quarter of the luma sample grid spacing displacement. The process for inter prediction of a sample block can also involve the selection of the picture to be used as the reference picture from a number of stored previously-decoded pictures. Motion vectors are encoded differentially with respect to predicted values formed from nearby encoded motion vectors. + +Typically, the encoder calculates appropriate motion vectors and other data elements represented in the video data stream. This motion estimation process in the encoder and the selection of whether to use inter prediction for the representation of each region of the video content is not specified in this Recommendation | International Standard. + +#### **0.6.4 Spatial redundancy reduction** + +This clause does not form an integral part of this Recommendation | International Standard. + +Both source pictures and prediction residuals have high spatial redundancy. This Recommendation | International Standard is based on the use of a block-based transform method for spatial redundancy removal. After inter prediction + +from previously-decoded samples in other pictures or spatial-based prediction from previously-decoded samples within the current picture, the resulting prediction residual is split into 4x4 blocks. These are converted into the transform domain where they are quantized. After quantization many of the transform coefficients are zero or have low amplitude and can thus be represented with a small amount of encoded data. The processes of transformation and quantization in the encoder are not specified in this Recommendation | International Standard. + +## 0.7 How to read this Specification + +This clause does not form an integral part of this Recommendation | International Standard. + +It is suggested that the reader starts with clause 1 (Scope) and moves on to clause 3 (Definitions). Clause 6 should be read for the geometrical relationship of the source, input, and output of the decoder. Clause 7 (Syntax and semantics) specifies the order to parse syntax elements from the bitstream. See clauses 7.1 to 7.3 for syntactical order and see clause 7.4 for semantics; i.e., the scope, restrictions, and conditions that are imposed on the syntax elements. The actual parsing for most syntax elements is specified in clause 9 (Parsing process). Finally, clause 8 (Decoding process) specifies how the syntax elements are mapped into decoded samples. Throughout reading this Specification, the reader should refer to clauses 2 (Normative references), 4 (Abbreviations), and 5 (Conventions) as needed. Annexes A to I also form an integral part of this Recommendation | International Standard. + +Annex A specifies fourteen profiles (Baseline, Constrained Baseline, Main, Extended, High, Progressive High, Constrained High, High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra), each being tailored to certain application domains, and defines the so-called levels of the profiles. Annex B specifies syntax and semantics of a byte stream format for delivery of coded video as an ordered stream of bytes. Annex C specifies the hypothetical reference decoder and its use to check bitstream and decoder conformance. Annex D specifies syntax and semantics for supplemental enhancement information message payloads. Annex E specifies syntax and semantics of the video usability information parameters of the sequence parameter set. + +Annex F specifies scalable video coding (SVC). The reader is referred to Annex F for the entire decoding process for SVC, which is specified there with references being made to clauses 2 to 9 and Annexes A to E. Clause F.10 specifies five profiles for SVC (Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, and Scalable High Intra). + +Annex G specifies multiview video coding (MVC) and multi-resolution frame compatible stereo coding (MFC). The reader is referred to Annex G for the entire decoding process for MVC and MFC, which is specified there with references being made to clauses 2 to 9 and Annexes A to F. Clause G.10 specifies two profiles for MVC (Multiview High and Stereo High) and one profile for MFC (MFC High). + +Annex H specifies MVC extensions for inclusion of depth maps, referred to as multiview video coding with depth (MVCD). The reader is referred to Annex H for the entire decoding process for MVCD, which is specified there with references being made to clauses 2 to 9, Annexes A to G. Clause H.10 specifies two profiles for MVCD (Multiview Depth High and MFC Depth High). + +Annex I specifies a multiview video coding extension with depth information (3D-AVC). The reader is referred to Annex I for the entire decoding process for 3D-AVC, which is specified there with references being made to clauses 2 to 9 and Annexes A to E, G, and H. Clause I.10 specifies one profile for 3D-AVC. + +Throughout this Specification, statements appearing with the preamble "NOTE –" are informative and are not an integral part of this Recommendation | International Standard. + +## 1 Scope + +This document specifies Recommendation ITU-T H.264 | International Standard ISO/IEC 14496-10 Advanced video coding. + +## 2 Normative references + +The following Recommendations and International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this Recommendation | International Standard are encouraged to investigate the possibility of applying the most recent edition of the Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently valid ITU-T Recommendations. + +- Recommendation ITU-T H.274: in force | ISO/IEC 23002-7: in force, *Versatile supplemental enhancement information messages for coded video bitstreams*. +- Recommendation ITU-T T.35 (2000), *Procedure for the allocation of ITU-T defined codes for non-standard facilities*. +- ISO/IEC 11578:1996, *Information technology – Open Systems Interconnection – Remote Procedure Call (RPC)*. +- ISO 11664-1:2007, *Colorimetry – Part 1: CIE standard colorimetric observers*. +- ISO 12232:2006, *Photography – Digital still cameras – Determination of exposure index, ISO speed ratings, standard output sensitivity, and recommended exposure index*. +- ISO/IEC 23001-11, *Information Technology – MPEG Systems Technologies – Part 11: Energy-efficient media consumption (Green metadata)*. + +For the additional normative reference that applies for the scalability information SEI message specified in Annex F, see clause F.2. + +### 3 Definitions + +For the purposes of this Recommendation | International Standard, the following definitions apply: + +- 3.1 access unit:** A set of *NAL units* that are consecutive in *decoding order* and contain exactly one *primary coded picture*. In addition to the *primary coded picture*, an access unit may also contain one or more *redundant coded pictures*, one *auxiliary coded picture*, or other *NAL units* not containing *slices* or *slice data partitions* of a *coded picture*. The decoding of an access unit always results in a *decoded picture*. +- 3.2 AC transform coefficient:** Any *transform coefficient* for which the *frequency index* in one or both dimensions is non-zero. +- 3.3 adaptive binary arithmetic decoding process:** An entropy *decoding process* that derives the values of *bins* from a *bitstream* produced by an *adaptive binary arithmetic encoding process*. +- 3.4 adaptive binary arithmetic encoding process:** An entropy *encoding process*, not normatively specified in this Recommendation | International Standard, that codes a sequence of *bins* and produces a *bitstream* that can be decoded using the *adaptive binary arithmetic decoding process*. +- 3.5 alpha blending:** A process not specified by this Recommendation | International Standard, in which an *auxiliary coded picture* is used in combination with a *primary coded picture* and with other data not specified by this Recommendation | International Standard in the *display process*. In an alpha blending process, the samples of an *auxiliary coded picture* are interpreted as indications of the degree of opacity (or, equivalently, the degrees of transparency) associated with the corresponding *luma* samples of the *primary coded picture*. +- 3.6 arbitrary slice order (ASO):** A *decoding order* of *slices* in which the *macroblock address* of the first *macroblock* of some *slice* of a *slice group* may be less than the *macroblock address* of the first *macroblock* of some other preceding *slice* of the same *slice group* or, in the case of a *picture* that is coded using three separate colour planes, some other preceding *slice* of the same *slice group* within the same colour plane, or in which the *slices* of a *slice group* of a *picture* may be interleaved with the *slices* of one or more other *slice groups* of the *picture* or, in the case of a *picture* that is coded using three separate colour planes, with the *slices* of one or more other *slice groups* within the same colour plane. +- 3.7 auxiliary coded picture:** A *picture* that supplements the *primary coded picture* that may be used in combination with other data not specified by this Recommendation | International Standard in the *display process*. An auxiliary coded picture has the same syntactic and semantic restrictions as a monochrome *redundant coded picture*. An auxiliary coded picture must contain the same number of *macroblocks* as the *primary coded picture*. Auxiliary coded pictures have no normative effect on the *decoding process*. See also *primary coded picture* and *redundant coded picture*. +- 3.8 azimuth circle:** circle on a sphere connecting all points with the same azimuth value. +NOTE – An azimuth circle is always a *great circle* like a longitude line on the earth. +- 3.9 B slice:** A *slice* that may be decoded using *intra prediction* or *inter prediction* using at most two *motion vectors* and *reference indices* to predict the sample values of each *block*. +- 3.10 bin:** One bit of a *bin string*. +- 3.11 binarization:** A set of *bin strings* for all possible values of a *syntax element*. + +- 3.12 **binarization process:** A unique mapping process of all possible values of a *syntax element* onto a set of *bin strings*. +- 3.13 **bin string:** A string of *bins*. A bin string is an intermediate binary representation of values of *syntax elements* from the *binarization* of the *syntax element*. +- 3.14 **bi-predictive slice:** See *B slice*. +- 3.15 **bitstream:** A sequence of bits that forms the representation of *coded pictures* and associated data forming one or more *coded video sequences*. Bitstream is a collective term used to refer either to a *NAL unit stream* or a *byte stream*. +- 3.16 **block:** An $M \times N$ ( $M$ -column by $N$ -row) array of samples, or an $M \times N$ array of *transform coefficients*. +- 3.17 **bottom field:** One of two *fields* that comprise a *frame*. Each row of a *bottom field* is spatially located immediately below a corresponding row of a *top field*. +- 3.18 **bottom macroblock (of a macroblock pair):** The *macroblock* within a *macroblock pair* that contains the samples in the bottom row of samples for the *macroblock pair*. For a *field macroblock pair*, the bottom macroblock represents the samples from the region of the *bottom field* of the *frame* that lie within the spatial region of the *macroblock pair*. For a *frame macroblock pair*, the bottom macroblock represents the samples of the *frame* that lie within the bottom half of the spatial region of the *macroblock pair*. +- 3.19 **broken link:** A location in a *bitstream* at which it is indicated that some subsequent *pictures* in *decoding order* may contain serious visual artefacts due to unspecified operations performed in the generation of the *bitstream*. +- 3.20 **byte:** A sequence of 8 bits, written and read with the most significant bit on the left and the least significant bit on the right. When represented in a sequence of data bits, the most significant bit of a byte is first. +- 3.21 **byte-aligned:** A position in a *bitstream* is byte-aligned when the position is an integer multiple of 8 bits from the position of the first bit in the *bitstream*. A bit or *byte* or *syntax element* is said to be byte-aligned when the position at which it appears in a *bitstream* is byte-aligned. +- 3.22 **byte stream:** An encapsulation of a *NAL unit stream* containing *start code prefixes* and *NAL units* as specified in Annex B. +- 3.23 **can:** A term used to refer to behaviour that is allowed, but not necessarily required. +- 3.24 **category:** A number associated with each *syntax element*. The category is used to specify the allocation of *syntax elements* to *NAL units* for *slice data partitioning*. It may also be used in a manner determined by the application to refer to classes of *syntax elements* in a manner not specified in this Recommendation | International Standard. +- 3.25 **chroma:** An adjective specifying that a sample array or single sample is representing one of the two colour difference signals related to the primary colours. The symbols used for a chroma array or sample are Cb and Cr. +- NOTE – The term chroma is used rather than the term chrominance in order to avoid the implication of the use of linear light transfer characteristics that is often associated with the term chrominance. +- 3.26 **coded field:** A *coded representation* of a *field*. +- 3.27 **coded frame:** A *coded representation* of a *frame*. +- 3.28 **coded picture:** A *coded representation* of a *picture*. A coded picture may be either a *coded field* or a *coded frame*. Coded picture is a collective term referring to a *primary coded picture* or a *redundant coded picture*, but not to both together. +- 3.29 **coded picture buffer (CPB):** A first-in first-out buffer containing *access units* in *decoding order* specified in the *hypothetical reference decoder* in Annex C. +- 3.30 **coded representation:** A data element as represented in its coded form. +- 3.31 **coded slice data partition NAL unit:** A *NAL unit* containing a *slice data partition*. +- 3.32 **coded slice NAL unit:** A *NAL unit* containing a *slice* that is not a *slice* of an *auxiliary coded picture*. +- 3.33 **coded video sequence:** A sequence of *access units* that consists, in decoding order, of an *IDR access unit* followed by zero or more non-IDR *access units* including all subsequent *access units* up to but not including any subsequent *IDR access unit*. + +- 3.34 **component:** An array or single sample from one of the three arrays (*luma* and two *chroma*) that make up a *field* or *frame* in 4:2:0, 4:2:2, or 4:4:4 colour format or the array or a single sample of the array that make up a *field* or *frame* in monochrome format. +- 3.35 **complementary field pair:** A collective term for a *complementary reference field pair* or a *complementary non-reference field pair*. +- 3.36 **complementary non-reference field pair:** Two *non-reference fields* that are in consecutive *access units* in *decoding order* as two *coded fields* of opposite parity and share the same value of the *frame\_num syntax element*, where the first *field* is not already a *paired field*. +- 3.37 **complementary reference field pair:** Two *reference fields* that are in consecutive *access units* in *decoding order* as two *coded fields* and share the same value of the *frame\_num syntax element*, where the second *field* in *decoding order* is not an *IDR picture* and does not include a *memory\_management\_control\_operation syntax element* equal to 5. +- 3.38 **constituent picture:** part of a spatially frame-packed stereoscopic video picture that corresponds to one view, or a picture itself when frame packing is not in use or the temporal interleaving frame packing arrangement is in use. +- 3.39 **context variable:** A variable specified for the *adaptive binary arithmetic decoding process* of a *bin* by an equation containing recently decoded *bins*. +- 3.40 **DC transform coefficient:** A *transform coefficient* for which the *frequency index* is zero in all dimensions. +- 3.41 **decoded picture:** A *decoded picture* is derived by decoding a *coded picture*. A *decoded picture* is either a *decoded frame*, or a *decoded field*. A *decoded field* is either a *decoded top field* or a *decoded bottom field*. +- 3.42 **decoded picture buffer (DPB):** A buffer holding *decoded pictures* for reference, output reordering, or output delay specified for the *hypothetical reference decoder* in Annex C. +- 3.43 **decoder:** An embodiment of a *decoding process*. +- 3.44 **decoder under test (DUT):** A *decoder* that is tested for conformance to this Recommendation | International Standard by operating the *hypothetical stream scheduler* to deliver a conforming *bitstream* to the *decoder* and to the *hypothetical reference decoder* and comparing the values and timing of the output of the two *decoders*. +- 3.45 **decoding order:** The order in which *syntax elements* are processed by the *decoding process*. +- 3.46 **decoding process:** The process specified in this Recommendation | International Standard that reads a *bitstream* and derives *decoded pictures* from it. +- 3.47 **direct prediction:** An *inter prediction* for a *block* for which no *motion vector* is decoded. Two *direct prediction* modes are specified that are referred to as *spatial direct prediction* and *temporal prediction* mode. +- 3.48 **display process:** A process not specified in this Recommendation | International Standard having, as its input, the cropped *decoded pictures* that are the output of the *decoding process*. +- 3.49 **elevation circle:** circle on a sphere connecting all points with the same elevation value. +NOTE – An elevation circle is similar to a latitude line on the earth. Except when the elevation value is zero, an elevation circle is not a *great circle* like a longitude circle on the earth. +- 3.50 **emulation prevention byte:** A *byte* equal to 0x03 that may be present within a *NAL unit*. The presence of emulation prevention bytes ensures that no sequence of consecutive *byte-aligned bytes* in the *NAL unit* contains a *start code prefix*. +- 3.51 **encoder:** An embodiment of an *encoding process*. +- 3.52 **encoding process:** A process, not specified in this Recommendation | International Standard, that produces a *bitstream* conforming to this Recommendation | International Standard. +- 3.53 **field:** An assembly of alternate rows of a *frame*. A *frame* is composed of two *fields*, a *top field* and a *bottom field*. +- 3.54 **field macroblock:** A *macroblock* containing samples from a single *field*. All *macroblocks* of a *coded field* are *field macroblocks*. When *macroblock-adaptive frame/field decoding* is in use, some *macroblocks* of a *coded frame* may be *field macroblocks*. +- 3.55 **field macroblock pair:** A *macroblock pair* decoded as two *field macroblocks*. +- 3.56 **field scan:** A specific sequential ordering of *transform coefficients* that differs from the *zig-zag scan* by scanning columns more rapidly than rows. Field scan is used for *transform coefficients* in *field macroblocks*. + +- 3.57 **flag:** A variable that can take one of the two possible values 0 and 1. +- 3.58 **frame:** A *frame* contains an array of *luma* samples in monochrome format or an array of *luma* samples and two corresponding arrays of *chroma* samples in 4:2:0, 4:2:2, and 4:4:4 colour format. A *frame* consists of two *fields*, a *top field* and a *bottom field*. +- 3.59 **frame macroblock:** A *macroblock* representing samples from the two *fields* of a *coded frame*. When *macroblock-adaptive frame/field decoding* is not in use, all *macroblocks* of a *coded frame* are frame macroblocks. When *macroblock-adaptive frame/field decoding* is in use, some *macroblocks* of a *coded frame* may be frame macroblocks. +- 3.60 **frame macroblock pair:** A *macroblock pair* decoded as two *frame macroblocks*. +- 3.61 **frequency index:** A one-dimensional or two-dimensional index associated with a *transform coefficient* prior to an *inverse transform* part of the *decoding process*. +- 3.62 **global coordinate axes:** coordinate axes associated with *omnidirectional video* that are associated with an externally referenceable position and orientation. +NOTE – The global coordinate axes may correspond to the position and orientation of a device or rig used for omnidirectional audio/video acquisition as well as the position of an observer's head in the three-dimensional space of the *omnidirectional video* rendering environment. +- 3.63 **great circle:** intersection of a sphere and a plane that passes through the centre point of the sphere. +NOTE – A great circle is also known as an orthodrome or Riemannian circle. +- 3.64 **hypothetical reference decoder (HRD):** A hypothetical *decoder* model that specifies constraints on the variability of conforming *NAL unit streams* or conforming *byte streams* that an encoding process may produce. +- 3.65 **hypothetical stream scheduler (HSS):** A hypothetical delivery mechanism for the timing and data flow of the input of a *bitstream* into the *hypothetical reference decoder*. The HSS is used for checking the conformance of a *bitstream* or a *decoder*. +- 3.66 **I slice:** A *slice* that is not an *SI slice* that is decoded using *intra prediction* only. +- 3.67 **informative:** A term used to refer to content provided in this Recommendation | International Standard that is not an integral part of this Recommendation | International Standard. Informative content does not establish any mandatory requirements for conformance to this Recommendation | International Standard. +- 3.68 **instantaneous decoding refresh (IDR) access unit:** An *access unit* in which the *primary coded picture* is an *IDR picture*. +- 3.69 **instantaneous decoding refresh (IDR) picture:** A *coded picture* for which the variable *IdrPicFlag* is equal to 1. An IDR picture causes the *decoding process* to mark all *reference pictures* as "unused for reference" immediately after the decoding of the IDR picture. All *coded pictures* that follow an IDR picture in *decoding order* can be decoded without *inter prediction* from any *picture* that precedes the IDR picture in *decoding order*. The first *picture* of each *coded video sequence* in *decoding order* is an IDR picture. +- 3.70 **inter coding:** Coding of a *block*, *macroblock*, *slice*, or *picture* that uses *inter prediction*. +- 3.71 **inter prediction:** A *prediction* derived from decoded samples of *reference pictures* other than the current *decoded picture*. +- 3.72 **interpretation sample value:** A possibly-altered value corresponding to a decoded sample value of an *auxiliary coded picture* that may be generated for use in the *display process*. Interpretation sample values are not used in the *decoding process* and have no normative effect on the *decoding process*. +- 3.73 **intra coding:** Coding of a *block*, *macroblock*, *slice*, or *picture* that uses *intra prediction*. +- 3.74 **intra prediction:** A *prediction* derived from the decoded samples of the same decoded *slice*. +- 3.75 **intra slice:** See *I slice*. +- 3.76 **inverse transform:** A part of the *decoding process* by which a set of *transform coefficients* are converted into spatial-domain values, or by which a set of *transform coefficients* are converted into *DC transform coefficients*. +- 3.77 **layer:** One of a set of syntactical structures in a non-branching hierarchical relationship. Higher layers contain lower layers. The coding layers are the *coded video sequence*, *picture*, *slice*, and *macroblock* layers. +- 3.78 **level:** A defined set of constraints on the values that may be taken by the *syntax elements* and variables of this Recommendation | International Standard. The same set of levels is defined for all *profiles*, with most aspects of the definition of each level being in common across different *profiles*. Individual implementations may, + +within specified constraints, support a different level for each supported *profile*. In a different context, a level is the value of a *transform coefficient* prior to *scaling* (see the definition of *transform coefficient level*). + +- 3.79 **list:** A one-dimensional array of *syntax elements* or variables. +- 3.80 **list 0 (list 1) motion vector:** A *motion vector* associated with a *reference index* pointing into *reference picture list 0 (list 1)*. +- 3.81 **list 0 (list 1) prediction:** *Inter prediction* of the content of a *slice* using a *reference index* pointing into *reference picture list 0 (list 1)*. +- 3.82 **local coordinate axes:** coordinate axes having a specified rotation relationship relative to the *global coordinate axes*. +- 3.83 **luma:** An adjective specifying that a sample array or single sample is representing the monochrome signal related to the primary colours. The symbol or subscript used for luma is Y or L. +NOTE – The term luma is used rather than the term luminance in order to avoid the implication of the use of linear light transfer characteristics that is often associated with the term luminance. The symbol L is sometimes used instead of the symbol Y to avoid confusion with the symbol y as used for vertical location. +- 3.84 **macroblock:** A 16x16 *block* of *luma* samples and two corresponding *blocks* of *chroma* samples of a *picture* that has three sample arrays, or a 16x16 *block* of samples of a monochrome *picture* or a *picture* that is coded using three separate colour planes. The division of a *slice* or a *macroblock pair* into macroblocks is a *partitioning*. +- 3.85 **macroblock-adaptive frame/field decoding:** A *decoding process* for *coded frames* in which some *macroblocks* may be decoded as *frame macroblocks* and others may be decoded as *field macroblocks*. +- 3.86 **macroblock address:** When *macroblock-adaptive frame/field decoding* is not in use, a macroblock address is the index of a *macroblock* in a *macroblock raster scan* of the *picture* starting with zero for the top-left *macroblock* in a *picture*. When *macroblock-adaptive frame/field decoding* is in use, the macroblock address of the *top macroblock* of a *macroblock pair* is two times the index of the *macroblock pair* in a *macroblock pair raster scan* of the *picture*, and the macroblock address of the *bottom macroblock* of a *macroblock pair* is the macroblock address of the corresponding *top macroblock* plus 1. The macroblock address of the *top macroblock* of each *macroblock pair* is an even number and the macroblock address of the *bottom macroblock* of each *macroblock pair* is an odd number. +- 3.87 **macroblock location:** The two-dimensional coordinates of a *macroblock* in a *picture* denoted by ( x, y ). For the top left *macroblock* of the *picture* ( x, y ) is equal to ( 0, 0 ). x is incremented by 1 for each *macroblock* column from left to right. When *macroblock-adaptive frame/field decoding* is not in use, y is incremented by 1 for each *macroblock* row from top to bottom. When *macroblock-adaptive frame/field decoding* is in use, y is incremented by 2 for each *macroblock pair* row from top to bottom, and is incremented by an additional 1 when a *macroblock* is a *bottom macroblock*. +- 3.88 **macroblock pair:** A pair of vertically contiguous *macroblocks* in a *frame* that is coupled for use in *macroblock-adaptive frame/field decoding*. The division of a *slice* into macroblock pairs is a *partitioning*. +- 3.89 **macroblock partition:** A *block* of *luma* samples and two corresponding *blocks* of *chroma* samples resulting from a *partitioning* of a *macroblock* for *inter prediction* for a *picture* that has three sample arrays or a *block* of *luma* samples resulting from a *partitioning* of a *macroblock* for *inter prediction* for a monochrome *picture* or a *picture* that is coded using three separate colour planes. +- 3.90 **macroblock to slice group map:** A means of mapping *macroblocks* of a *picture* into *slice groups*. The macroblock to slice group map consists of a list of numbers, one for each coded *macroblock*, specifying the *slice group* to which each coded *macroblock* belongs. +- 3.91 **map unit to slice group map:** A means of mapping *slice group map units* of a *picture* into *slice groups*. The map unit to slice group map consists of a list of numbers, one for each *slice group map unit*, specifying the *slice group* to which each coded *slice group map unit* belongs. +- 3.92 **matrix:** A two-dimensional array of *syntax elements* or variables. +- 3.93 **may:** A term used to refer to behaviour that is allowed, but not necessarily required. In some places where the optional nature of the described behaviour is intended to be emphasized, the phrase "may or may not" is used to provide emphasis. +- 3.94 **memory management control operation:** Seven operations that control *reference picture marking*. +- 3.95 **motion vector:** A two-dimensional vector used for *inter prediction* that provides an offset from the coordinates in the *decoded picture* to the coordinates in a *reference picture*. + +- 3.96 **must:** A term used in expressing an observation about a requirement or an implication of a requirement that is specified elsewhere in this Recommendation | International Standard. This term is used exclusively in an *informative* context. +- 3.97 **NAL unit:** A *syntax structure* containing an indication of the type of data to follow and *bytes* containing that data in the form of an *RBSP* interspersed as necessary with *emulation prevention bytes*. +- 3.98 **NAL unit stream:** A sequence of *NAL units*. +- 3.99 **non-paired field:** A collective term for a *non-paired reference field* or a *non-paired non-reference field*. +- 3.100 **non-paired non-reference field:** A decoded *non-reference field* that is not part of a *complementary non-reference field pair*. +- 3.101 **non-paired reference field:** A decoded *reference field* that is not part of a *complementary reference field pair*. +- 3.102 **non-reference field:** A *field* coded with *nal\_ref\_idc* equal to 0. +- 3.103 **non-reference frame:** A *frame* coded with *nal\_ref\_idc* equal to 0. +- 3.104 **non-reference picture:** A *picture* coded with *nal\_ref\_idc* equal to 0. A *non-reference picture* is not used for *inter prediction* of any other *pictures*. +- 3.105 **note:** A term used to prefix *informative* remarks. This term is used exclusively in an *informative* context. +- 3.106 **omnidirectional video:** video content in a format that enables rendering according to the user's viewing orientation, e.g., if viewed using a head-mounted device, or according to a user's desired *viewport*, reflecting a potentially rotated viewing position. +- 3.107 **opposite parity:** The *opposite parity* of *top* is *bottom*, and vice versa. +- 3.108 **output order:** The order in which the *decoded pictures* are output from the *decoded picture buffer*. +- 3.109 **P slice:** A *slice* that is not an *SP slice* that may be decoded using *intra prediction* or *inter prediction* using at most one *motion vector* and *reference index* to *predict* the sample values of each *block*. +- 3.110 **packed region:** region in a *region-wise packed picture* that is mapped to a *projected region* according to a *region-wise packing*. +- 3.111 **parameter:** A *syntax element* of a *sequence parameter set* or a *picture parameter set*. Parameter is also used as part of the defined term *quantization parameter*. +- 3.112 **parity:** The parity of a *field* can be *top* or *bottom*. +- 3.113 **partitioning:** The division of a set into *subsets* such that each element of the set is in exactly one of the *subsets*. +- 3.114 **picture:** A collective term for a *field* or a *frame*. +- 3.115 **picture parameter set:** A *syntax structure* containing *syntax elements* that apply to zero or more entire *coded pictures* as determined by the *pic\_parameter\_set\_id* *syntax element* found in each *slice header*. +- 3.116 **picture order count:** A variable that is associated with each *coded field* and each *field* of a *coded frame* and has a value that is non-decreasing with increasing *field* position in *output order* relative to the first output *field* of the previous *IDR picture* in *decoding order* or relative to the first output *field* of the previous *picture*, in *decoding order*, that contains a *memory management control operation* that marks all *reference pictures* as "unused for reference". +- 3.117 **prediction:** An embodiment of the *prediction process*. +- 3.118 **prediction process:** The use of a *predictor* to provide an estimate of the sample value or data element currently being decoded. +- 3.119 **predictive slice:** See *P slice*. +- 3.120 **predictor:** A combination of specified values or previously decoded sample values or data elements used in the *decoding process* of subsequent sample values or data elements. +- 3.121 **primary coded picture:** The coded representation of a *picture* to be used by the *decoding process* for a bitstream conforming to this Recommendation | International Standard. The primary coded picture contains all *macroblocks* of the *picture*. The only *pictures* that have a normative effect on the *decoding process* are primary coded pictures. See also *redundant coded picture*. +- 3.122 **profile:** A specified *subset* of the syntax of this Recommendation | International Standard. + +- 3.123 **projected picture:** picture that uses a *projection* format for *omnidirectional video*. +- 3.124 **projected region:** region in a *projected picture* that is mapped to a *packed region* according to a *region-wise packing*. +- 3.125 **projection:** specified correspondence between the colour samples of a *projected picture* and azimuth and elevation positions on a sphere. +- 3.126 **quantization parameter:** A variable used by the *decoding process* for *scaling of transform coefficient levels*. +- 3.127 **random access:** The act of starting the decoding process for a *bitstream* at a point other than the beginning of the stream. +- 3.128 **raster scan:** A mapping of a rectangular two-dimensional pattern to a one-dimensional pattern such that the first entries in the one-dimensional pattern are from the first top row of the two-dimensional pattern scanned from left to right, followed similarly by the second, third, etc., rows of the pattern (going down) each scanned from left to right. +- 3.129 **raw byte sequence payload (RBSP):** A *syntax structure* containing an integer number of *bytes* that is encapsulated in a *NAL unit*. An RBSP is either empty or has the form of a *string of data bits* containing *syntax elements* followed by an *RBSP stop bit* and followed by zero or more subsequent bits equal to 0. +- 3.130 **raw byte sequence payload (RBSP) stop bit:** A bit equal to 1 present within a *raw byte sequence payload (RBSP)* after a *string of data bits*. The location of the end of the *string of data bits* within an RBSP can be identified by searching from the end of the RBSP for the *RBSP stop bit*, which is the last non-zero bit in the RBSP. +- 3.131 **recovery point:** A point in the *bitstream* at which the recovery of an exact or an approximate representation of the *decoded pictures* represented by the *bitstream* is achieved after a *random access* or *broken link*. +- 3.132 **redundant coded picture:** A coded representation of a *picture* or a part of a *picture*. The content of a redundant coded picture shall not be used by the *decoding process* for a *bitstream* conforming to this Recommendation | International Standard. A *redundant coded picture* is not required to contain all *macroblocks* in the *primary coded picture*. Redundant coded pictures have no normative effect on the *decoding process*. See also *primary coded picture*. +- 3.133 **reference field:** A *reference field* may be used for *inter prediction* when *P*, *SP*, and *B slices* of a *coded field* or *field macroblocks* of a *coded frame* are decoded. See also *reference picture*. +- 3.134 **reference frame:** A *reference frame* may be used for *inter prediction* when *P*, *SP*, and *B slices* of a *coded frame* are decoded. See also *reference picture*. +- 3.135 **reference index:** An index into a *reference picture list*. +- 3.136 **reference picture:** A *picture* with *nal\_ref\_idc* not equal to 0. A *reference picture* contains samples that may be used for *inter prediction* in the *decoding process* of subsequent *pictures* in *decoding order*. +- 3.137 **reference picture list:** A list of *reference pictures* that is used for *inter prediction* of a *P*, *B*, or *SP slice*. For the *decoding process* of a *P* or *SP slice*, there is one reference picture list. For the *decoding process* of a *B slice*, there are two reference picture lists. +- 3.138 **reference picture list 0:** A *reference picture list* used for *inter prediction* of a *P*, *B*, or *SP slice*. All *inter prediction* used for *P* and *SP slices* uses reference picture list 0. Reference picture list 0 is one of two *reference picture lists* used for *inter prediction* for a *B slice*, with the other being *reference picture list 1*. +- 3.139 **reference picture list 1:** A *reference picture list* used for *inter prediction* of a *B slice*. Reference picture list 1 is one of two *reference picture lists* used for *inter prediction* for a *B slice*, with the other being *reference picture list 0*. +- 3.140 **reference picture marking:** Specifies, in the bitstream, how the *decoded pictures* are marked for *inter prediction*. +- 3.141 **region-wise packed picture:** decoded picture that contains one or more *packed regions*. +NOTE – A packed picture may contain a *region-wise packing* of a *projected picture*. +- 3.142 **region-wise packing:** transformation, resizing, and relocation of *packed regions* of a *region-wise packed picture* to remap the *packed regions* to *projected regions* of a *projected picture*. +- 3.143 **reserved:** The term reserved, when used in the clauses specifying some values of a particular *syntax element*, are for future use by ITU-T | ISO/IEC. These values shall not be used in *bitstreams* conforming to this + +Recommendation | International Standard, but may be used in future extensions of this Recommendation | International Standard by ITU-T | ISO/IEC. + +- 3.144 **residual:** The decoded difference between a *prediction* of a sample or data element and its decoded value. +- 3.145 **run:** A number of consecutive data elements represented in the decoding process. In one context, the number of zero-valued *transform coefficient levels* preceding a non-zero *transform coefficient level* in the list of *transform coefficient levels* generated by a *zig-zag scan* or a *field scan*. In other contexts, *run* refers to a number of *macroblocks*. +- 3.146 **sample aspect ratio:** Specifies, for assisting the *display process*, which is not specified in this Recommendation | International Standard, the ratio between the intended horizontal distance between the columns and the intended vertical distance between the rows of the *luma* sample array in a *frame*. Sample aspect ratio is expressed as *h:v*, where *h* is horizontal width and *v* is vertical height (in arbitrary units of spatial distance). +- 3.147 **scaling:** The process of multiplying *transform coefficient levels* by a factor, resulting in *transform coefficients*. +- 3.148 **sequence parameter set:** A *syntax structure* containing *syntax elements* that apply to zero or more entire *coded video sequences* as determined by the content of a *seq\_parameter\_set\_id syntax element* found in the *picture parameter set* referred to by the *pic\_parameter\_set\_id syntax element* found in each *slice header*. +- 3.149 **shall:** A term used to express mandatory requirements for conformance to this Recommendation | International Standard. When used to express a mandatory constraint on the values of *syntax elements* or on the results obtained by operation of the specified *decoding process*, it is the responsibility of the *encoder* to ensure that the constraint is fulfilled. When used in reference to operations performed by the *decoding process*, any *decoding process* that produces identical results to the *decoding process* described herein conforms to the *decoding process* requirements of this Recommendation | International Standard. +- 3.150 **should:** A term used to refer to behaviour of an implementation that is encouraged to be followed under anticipated ordinary circumstances, but is not a mandatory requirement for conformance to this Recommendation | International Standard. +- 3.151 **SI slice:** A *slice* that is coded using *intra prediction* only and using quantization of the *prediction* samples. An SI slice can be coded such that its decoded samples can be constructed identically to an SP slice. +- 3.152 **skipped macroblock:** A *macroblock* for which no data is coded other than an indication that the *macroblock* is to be decoded as "skipped". This indication may be common to several *macroblocks*. +- 3.153 **slice:** An integer number of *macroblocks* or *macroblock pairs* ordered consecutively in the *raster scan* within a particular *slice group*. For the *primary coded picture*, the division of each *slice group* into slices is a *partitioning*. Although a slice contains *macroblocks* or *macroblock pairs* that are consecutive in the *raster scan* within a *slice group*, these *macroblocks* or *macroblock pairs* are not necessarily consecutive in the *raster scan* within the *picture*. The *macroblock addresses* are derived from the first *macroblock address* in a slice (as represented in the *slice header*) and the *macroblock to slice group map*, and, when a *picture* is coded using three separate colour planes, a colour plane identifier. +- 3.154 **slice data partition:** A non-empty *subset* of the *syntax elements* of the slice data *syntax structure* for a *slice*. The *syntax elements* of a slice data partition are associated with the same *category*. +- 3.155 **slice data partitioning:** A method of *partitioning* selected *syntax elements* into *syntax structures* based on a *category* associated with each *syntax element*. +- 3.156 **slice group:** A *subset* of the *macroblocks* or *macroblock pairs* of a *picture*. The division of the *picture* into slice groups is a *partitioning* of the *picture*. The *partitioning* is specified by the *macroblock to slice group map*. +- 3.157 **slice group map units:** The units of the *map unit to slice group map*. +- 3.158 **slice header:** A part of a coded *slice* containing the data elements pertaining to the first or all *macroblocks* represented in the *slice*. +- 3.159 **source:** Term used to describe the video material or some of its attributes before encoding. +- 3.160 **SP slice:** A *slice* that may be coded using *intra prediction* or *inter prediction* with quantization of the *prediction* samples using at most one *motion vector* and *reference index* to *predict* the sample values of each *block*. An SP slice can be coded such that its decoded samples can be constructed identically to another SP slice or an SI slice. +- 3.161 **sphere coordinates:** azimuth and elevation angles identifying a location of a point on a sphere. +- 3.162 **sphere region:** region on a sphere, specified either by four *great circles* or by two *azimuth circles* and two *elevation circles*, or such a region on a rotated sphere after applying yaw, pitch, and roll rotations. + +- 3.163 **start code prefix:** A unique sequence of three *bytes* equal to 0x000001 embedded in the *byte stream* as a prefix to each *NAL unit*. The location of a start code prefix can be used by a *decoder* to identify the beginning of a new *NAL unit* and the end of a previous *NAL unit*. Emulation of start code prefixes is prevented within *NAL units* by the inclusion of *emulation prevention bytes*. +- 3.164 **string of data bits (SODB):** A sequence of some number of bits representing *syntax elements* present within a *raw byte sequence payload* prior to the *raw byte sequence payload stop bit*. Within an SODB, the left-most bit is considered to be the first and most significant bit, and the right-most bit is considered to be the last and least significant bit. +- 3.165 **sub-bitstream:** A *bitstream* that is derived as a *subset* from a *bitstream* by discarding zero or more *NAL units*. +- 3.166 **sub-macroblock:** One quarter of the samples of a *macroblock*, i.e., an 8x8 *luma block* and two corresponding *chroma blocks* of which one corner is located at a corner of the *macroblock* for a *picture* that has three sample arrays or an 8x8 *luma block* of which one corner is located at a corner of the *macroblock* for a monochrome *picture* or a *picture* that is coded using three separate colour planes. +- 3.167 **sub-macroblock partition:** A *block* of *luma* samples and two corresponding *blocks* of *chroma* samples resulting from a *partitioning* of a *sub-macroblock* for *inter prediction* for a *picture* that has three sample arrays or a *block* of *luma* samples resulting from a *partitioning* of a *sub-macroblock* for *inter prediction* for a monochrome *picture* or a *picture* that is coded using three separate colour planes. +- 3.168 **subset:** A *subset* contains only elements that are also contained in the set from which the *subset* is derived. The *subset* may be identical to the set from which it is derived. +- 3.169 **switching I slice:** See *SI slice*. +- 3.170 **switching P slice:** See *SP slice*. +- 3.171 **syntax element:** An element of data represented in the *bitstream*. +- 3.172 **syntax structure:** Zero or more *syntax elements* present together in the *bitstream* in a specified order. +- 3.173 **tilt angle:** angle indicating the amount of tilt of a *sphere region*, measured as the amount of rotation of a *sphere region* along the axis originating from the sphere origin passing through the centre point of the *sphere region*, where the angle value increases clockwise when looking from the origin towards the positive end of the axis. +- 3.174 **top field:** One of two *fields* that comprise a *frame*. Each row of a *top field* is spatially located immediately above the corresponding row of the *bottom field*. +- 3.175 **top macroblock (of a macroblock pair):** The *macroblock* within a *macroblock pair* that contains the samples in the top row of samples for the *macroblock pair*. For a *field macroblock pair*, the top macroblock represents the samples from the region of the *top field* of the *frame* that lie within the spatial region of the *macroblock pair*. For a *frame macroblock pair*, the top macroblock represents the samples of the *frame* that lie within the top half of the spatial region of the *macroblock pair*. +- 3.176 **transform coefficient:** A scalar quantity, considered to be in a frequency domain, that is associated with a particular one-dimensional or two-dimensional *frequency index* in an *inverse transform* part of the *decoding process*. +- 3.177 **transform coefficient level:** An integer quantity representing the value associated with a particular two-dimensional frequency index in the *decoding process* prior to *scaling* for computation of a *transform coefficient* value. +- 3.178 **universal unique identifier (UUID):** An identifier that is unique with respect to the space of all universal unique identifiers. +- 3.179 **unspecified:** The term unspecified, when used in the clauses specifying some values of a particular *syntax element*, indicates that the values have no specified meaning in this Recommendation | International Standard and will not have a specified meaning in the future as an integral part of this Recommendation | International Standard. +- 3.180 **variable length coding (VLC):** A reversible procedure for entropy coding that assigns shorter bit strings to *symbols* expected to be more frequent and longer bit strings to *symbols* expected to be less frequent. +- 3.181 **VCL NAL unit:** A collective term for *coded slice NAL units* and *coded slice data partition NAL units*. +- 3.182 **viewport:** region of *omnidirectional video* content suitable for display and viewing by the user. +- 3.183 **zig-zag scan:** A specific sequential ordering of *transform coefficient levels* from (approximately) the lowest spatial frequency to the highest. Zig-zag scan is used for *transform coefficient levels* in *frame macroblocks*. + +## 4 Abbreviations + +For the purposes of this Recommendation | International Standard, the following abbreviations apply: + +| | | +|-------|-------------------------------------------------| +| CABAC | Context-based Adaptive Binary Arithmetic Coding | +| CAVLC | Context-based Adaptive Variable Length Coding | +| CBR | Constant Bit Rate | +| CPB | Coded Picture Buffer | +| DPB | Decoded Picture Buffer | +| DUT | Decoder under test | +| FIFO | First-In, First-Out | +| HRD | Hypothetical Reference Decoder | +| HSS | Hypothetical Stream Scheduler | +| IDR | Instantaneous Decoding Refresh | +| LSB | Least Significant Bit | +| MB | Macroblock | +| MBAFF | Macroblock-Adaptive Frame-Field Coding | +| MSB | Most Significant Bit | +| MVC | Multiview Video Coding | +| MVCD | Multiview Video Coding with Depth | +| NAL | Network Abstraction Layer | +| RBSP | Raw Byte Sequence Payload | +| SEI | Supplemental Enhancement Information | +| SODB | String Of Data Bits | +| SVC | Scalable Video Coding | +| UUID | Universal Unique Identifier | +| VBR | Variable Bit Rate | +| VCL | Video Coding Layer | +| VLC | Variable Length Coding | +| VUI | Video Usability Information | + +## 5 Conventions + +NOTE – The mathematical operators used in this Specification are similar to those used in the C programming language. However, integer division and arithmetic shift operations are specifically defined. Numbering and counting conventions generally begin from 0. + +### 5.1 Arithmetic operators + +The following arithmetic operators are defined as follows: + +| | | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| + | Addition | +| – | Subtraction (as a two-argument operator) or negation (as a unary prefix operator) | +| * | Multiplication, including matrix multiplication | +| $x^y$ | Exponentiation. Specifies $x$ to the power of $y$ . In other contexts, such notation is used for superscripting not intended for interpretation as exponentiation. | +| / | Integer division with truncation of the result toward zero. For example, $7/4$ and $-7/-4$ are truncated to 1 and $-7/4$ and $7/-4$ are truncated to $-1$ . | + +÷ Used to denote division in mathematical equations where no truncation or rounding is intended. + +$\frac{x}{y}$ Used to denote division in mathematical equations where no truncation or rounding is intended. + +$\sum_{i=x}^y f(i)$ The summation of $f(i)$ with $i$ taking all integer values from $x$ up to and including $y$ . + +$x \% y$ Modulus. Remainder of $x$ divided by $y$ , defined only for integers $x$ and $y$ with $x \geq 0$ and $y > 0$ . + +## 5.2 Logical operators + +The following logical operators are defined as follows: + +$x \&\& y$ Boolean logical "and" of $x$ and $y$ . + +$x || y$ Boolean logical "or" of $x$ and $y$ . + +! Boolean logical "not". + +$x ? y : z$ If $x$ is TRUE or not equal to 0, evaluates to the value of $y$ ; otherwise, evaluates to the value of $z$ . + +## 5.3 Relational operators + +The following relational operators are defined as follows: + +> Greater than. + +>= Greater than or equal to. + +< Less than. + +<= Less than or equal to. + +== Equal to. + +!= Not equal to. + +When a relational operator is applied to a syntax element or variable that has been assigned the value "na" (not applicable), the value "na" is treated as a distinct value for the syntax element or variable. The value "na" is considered not to be equal to any other value. + +## 5.4 Bit-wise operators + +The following bit-wise operators are defined as follows: + +& Bit-wise "and". When operating on integer arguments, operates on a two's complement representation of the integer value. When operating on a binary argument that contains fewer bits than another argument, the shorter argument is extended by adding more significant bits equal to 0. + +| Bit-wise "or". When operating on integer arguments, operates on a two's complement representation of the integer value. When operating on a binary argument that contains fewer bits than another argument, the shorter argument is extended by adding more significant bits equal to 0. + +^ Bit-wise "exclusive or". When operating on integer arguments, operates on a two's complement representation of the integer value. When operating on a binary argument that contains fewer bits than another argument, the shorter argument is extended by adding more significant bits equal to 0. + +$x \gg y$ Arithmetic right shift of a two's complement integer representation of $x$ by $y$ binary digits. This function is defined only for non-negative integer values of $y$ . Bits shifted into the MSBs as a result of the right shift have a value equal to the MSB of $x$ prior to the shift operation. + +$x \ll y$ Arithmetic left shift of a two's complement integer representation of $x$ by $y$ binary digits. This function is defined only for non-negative integer values of $y$ . Bits shifted into the LSBs as a result of the left shift have a value equal to 0. + +## 5.5 Assignment operators + +The following arithmetic operators are defined as follows: + += Assignment operator. + +++ Increment, i.e., $x++$ is equivalent to $x = x + 1$ ; when used in an array index, evaluates to the value of the variable prior to the increment operation. + +- Decrement, i.e., $x--$ is equivalent to $x = x - 1$ ; when used in an array index, evaluates to the value of the variable prior to the decrement operation. +- += Increment by amount specified, i.e., $x += 3$ is equivalent to $x = x + 3$ , and $x += (-3)$ is equivalent to $x = x + (-3)$ . +- = Decrement by amount specified, i.e., $x -= 3$ is equivalent to $x = x - 3$ , and $x -= (-3)$ is equivalent to $x = x - (-3)$ . + +## 5.6 Range notation + +The following notation is used to specify a range of values: + +$x = y..z$ $x$ takes on integer values starting from $y$ to $z$ , inclusive, with $x$ , $y$ , and $z$ being integer numbers. + +## 5.7 Mathematical functions + +The following mathematical functions are defined as follows: + +$$\text{Abs}(x) = \begin{cases} x & ; x \geq 0 \\ -x & ; x < 0 \end{cases} \quad (5-1)$$ + +$\text{Asin}(x)$ : The trigonometric inverse sine function, operating on an argument $x$ that is in the range of $-1.0$ to $1.0$ , inclusive, with an output value in the range of $-\pi/2$ to $\pi/2$ , inclusive, in units of radians. (5-2) + +$\text{Atan}(x)$ : The trigonometric inverse tangent function, operating on an argument $x$ , with an output value in the range of $-\pi/2$ to $\pi/2$ , inclusive, in units of radians. (5-3) + +$$\text{Atan2}(y, x) = \begin{cases} \text{Atan}\left(\frac{y}{x}\right) & ; x > 0 \\ \text{Atan}\left(\frac{y}{x}\right) + \pi & ; x < 0 \ \&\& \ y \geq 0 \\ \text{Atan}\left(\frac{y}{x}\right) - \pi & ; x < 0 \ \&\& \ y < 0 \\ +\frac{\pi}{2} & ; x = 0 \ \&\& \ y \geq 0 \\ -\frac{\pi}{2} & ; \text{otherwise} \end{cases} \quad (5-4)$$ + +$\text{Ceil}(x)$ the smallest integer greater than or equal to $x$ . (5-5) + +$\text{Clip1}_V(x) = \text{Clip3}(0, (1 \ll \text{BitDepth}_V) - 1, x)$ (5-6) + +$\text{Clip1}_C(x) = \text{Clip3}(0, (1 \ll \text{BitDepth}_C) - 1, x)$ (5-7) + +$$\text{Clip3}(x, y, z) = \begin{cases} x & ; z < x \\ y & ; z > y \\ z & ; \text{otherwise} \end{cases} \quad (5-8)$$ + +$\text{Cos}(x)$ the trigonometric cosine function operating on an argument $x$ in units of radians. (5-9) + +$\text{Floor}(x)$ the greatest integer less than or equal to $x$ . (5-10) + +$$\text{InverseRasterScan}(a, b, c, d, e) = \begin{cases} (a \% (d/b)) * b & ; e == 0 \\ (a / (d/b)) * c & ; e == 1 \end{cases} \quad (5-11)$$ + +$\text{Ln}(x)$ returns the natural logarithm of $x$ . (5-12) + +$\text{Log2}(x)$ returns the base-2 logarithm of $x$ . (5-13) + +$\text{Log10}(x)$ returns the base-10 logarithm of $x$ . (5-14) + +$$\text{Median}(x, y, z) = x + y + z - \text{Min}(x, \text{Min}(y, z)) - \text{Max}(x, \text{Max}(y, z)) \quad (5-15)$$ + +$$\text{Min}(x, y) = \begin{cases} x & ; x \leq y \\ y & ; x > y \end{cases} \quad (5-16)$$ + +$$\text{Max}(x, y) = \begin{cases} x & ; x \geq y \\ y & ; x < y \end{cases} \quad (5-17)$$ + +$$\text{Round}(x) = \text{Sign}(x) * \text{Floor}(\text{Abs}(x) + 0.5) \quad (5-18)$$ + +$$\text{Sign}(x) = \begin{cases} 1 & ; x \geq 0 \\ -1 & ; x < 0 \end{cases} \quad (5-19)$$ + +$$\text{Sin}(x): \quad \text{The trigonometric sine function operating on an argument } x \text{ in units of radians.} \quad (5-20)$$ + +$$\text{Sqrt}(x): \quad \text{Returns the square root of } x. \quad (5-21)$$ + +$$\text{Tan}(x): \quad \text{The trigonometric tangent function operating on an argument } x \text{ in units of radians.} \quad (5-22)$$ + +## 5.8 Order of operation precedence + +When order of precedence in an expression is not indicated explicitly by use of parentheses, the following rules apply: + +- operations of a higher precedence are evaluated before any operation of a lower precedence, +- operations of the same precedence are evaluated sequentially from left to right. + +Table 5-1 specifies the precedence of operations from highest to lowest; a higher position in the table indicates a higher precedence. + +NOTE – For those operators that are also used in the C programming language, the order of precedence used in this Specification is the same as used in the C programming language. + +**Table 5-1 – Operation precedence from highest (at top of table) to lowest (at bottom of table)** + +| operations (with operands x, y, and z) | +|------------------------------------------------------------------------| +| "x++", "x--" | +| "!x", "-x" (as a unary prefix operator) | +| $x^y$ | +| "x * y", "x / y", "x ÷ y", " $\frac{x}{y}$ ", "x % y" | +| "x + y", "x - y" (as a two-argument operator), " $\sum_{i=x}^y f(i)$ " | +| "x << y", "x >> y" | +| "x < y", "x <= y", "x > y", "x >= y" | +| "x == y", "x != y" | +| "x & y" | +| "x y" | +| "x && y" | +| "x y" | +| "x ? y : z" | +| "x = y", "x += y", "x -= y" | + +## 5.9 Variables, syntax elements, and tables + +Syntax elements in the bitstream are represented in **bold** type. Each syntax element is described by its name (all lower case letters with underscore characters), its one or two syntax categories, and one or two descriptors for its method of coded representation. The decoding process behaves according to the value of the syntax element and to the values of previously decoded syntax elements. When a value of a syntax element is used in the syntax tables or the text, it appears in regular (i.e., not bold) type. + +In some cases the syntax tables may use the values of other variables derived from syntax elements values. Such variables appear in the syntax tables, or text, named by a mixture of lower case and upper case letter and without any underscore characters. Variables starting with an upper case letter are derived for the decoding of the current syntax structure and all depending syntax structures. Variables starting with an upper case letter may be used in the decoding process for later syntax structures without mentioning the originating syntax structure of the variable. Variables starting with a lower case letter are only used within the clause in which they are derived. + +In some cases, "mnemonic" names for syntax element values or variable values are used interchangeably with their numerical values. Sometimes "mnemonic" names are used without any associated numerical values. The association of values and names is specified in the text. The names are constructed from one or more groups of letters separated by an underscore character. Each group starts with an upper case letter and may contain more upper case letters. + +NOTE – The syntax is described in a manner that closely follows the C-language syntactic constructs. + +Functions that specify properties of the current position in the bitstream are referred to as syntax functions. These functions are specified in clause 7.2 and assume the existence of a bitstream pointer with an indication of the position of the next bit to be read by the decoding process from the bitstream. Syntax functions are described by their names, which are constructed as syntax element names and end with left and right round parentheses including zero or more variable names (for definition) or values (for usage), separated by commas (if more than one variable). + +Functions that are not syntax functions (including mathematical functions specified in clause 5.7) are described by their names, which start with an upper case letter, contain a mixture of lower and upper case letters without any underscore character, and end with left and right parentheses including zero or more variable names (for definition) or values (for usage) separated by commas (if more than one variable). + +Subscripts or square parentheses are used for the indexing of arrays. In reference to a visual depiction of a matrix, the first subscript is used as a row (vertical) index and the second subscript is used as a column (horizontal) index. The indexing order is reversed when using square parentheses rather than subscripts for indexing. Thus, an element of a matrix s at horizontal position x and vertical position y may be denoted either as $s[x, y]$ or as $s_{yx}$ . + +Binary notation is indicated by enclosing the string of bit values by single quote marks. For example, '01000001' represents an eight-bit string having only its second and its last bits (counted from the most to the least significant bit) equal to 1. + +Hexadecimal notation, indicated by prefixing the hexadecimal number by "0x", may be used instead of binary notation when the number of bits is an integer multiple of 4. For example, 0x41 represents an eight-bit string having only its second and its last bits (counted from the most to the least significant bit) equal to 1. + +Numerical values not enclosed in single quotes and not prefixed by "0x" are decimal values. + +A value equal to 0 represents a FALSE condition in a test statement. The value TRUE is represented by any value different from zero. + +## 5.10 Text description of logical operations + +In the text, a statement of logical operations as would be described in pseudo-code as + +``` +if( condition 0 ) + statement 0 +else if ( condition 1 ) + statement 1 +... +else /* informative remark on remaining condition */ + statement n +``` + +may be described in the following manner: + +... as follows / ... the following applies: + +- If condition 0, statement 0 +- Otherwise, if condition 1, statement 1 +- ... +- Otherwise (informative remark on remaining condition), statement n + +Each "If ... Otherwise, if ... Otherwise, ..." statement in the text is introduced with "... as follows" or "... the following applies" immediately followed by "If ... ". The last condition of the "If ... Otherwise, if ... Otherwise, ..." is always an "Otherwise, ...". Interleaved "If ... Otherwise, if ... Otherwise, ..." statements can be identified by matching "... as follows" or "... the following applies" with the ending "Otherwise, ...". + +In the text, a statement of logical operations as would be described in pseudo-code as + +``` +if( condition 0a && condition 0b ) + statement 0 +else if ( condition 1a || condition 1b ) + statement 1 +... +else + statement n +``` + +may be described in the following manner: + +... as follows / ... the following applies: + +- If all of the following conditions are true, statement 0 + - condition 0a + - condition 0b +- Otherwise, if any of the following conditions are true, statement 1 + - condition 1a + - condition 1b +- ... +- Otherwise, statement n + +In the text, a statement of logical operations as would be described in pseudo-code as: + +``` +if( condition 0 ) + statement 0 +if( condition 1 ) + statement 1 +``` + +may be described in the following manner: + +When condition 0, statement 0 + +When condition 1, statement 1 + +## 5.11 Processes + +Processes are used to describe the decoding of syntax elements. A process has a separate specification and invoking. All syntax elements and upper case variables that pertain to the current syntax structure and depending syntax structures are available in the process specification and invoking. A process specification may also have a lower case variable explicitly specified as the input. Each process specification has explicitly specified an output. The output is a variable that can either be an upper case variable or a lower case variable. + +When invoking a process, the assignment of variables is specified as follows: + +- If the variables at the invoking and the process specification do not have the same name, the variables are explicitly assigned to lower case input or output variables of the process specification. +- Otherwise (the variables at the invoking and the process specification have the same name), assignment is implied. + +In the specification of a process, a specific macroblock may be referred to by the variable name having a value equal to the address of the specific macroblock. + +## 6 Source, coded, decoded and output data formats, scanning processes, and neighbouring relationships + +### 6.1 Bitstream formats + +This clause specifies the relationship between the NAL unit stream and byte stream, either of which are referred to as the bitstream. + +The bitstream can be in one of two formats: the NAL unit stream format or the byte stream format. The NAL unit stream format is conceptually the more "basic" type. It consists of a sequence of syntax structures called NAL units. This sequence is ordered in decoding order. There are constraints imposed on the decoding order (and contents) of the NAL units in the NAL unit stream. + +The byte stream format can be constructed from the NAL unit stream format by ordering the NAL units in decoding order and prefixing each NAL unit with a start code prefix and zero or more zero-valued bytes to form a stream of bytes. The NAL unit stream format can be extracted from the byte stream format by searching for the location of the unique start code prefix pattern within this stream of bytes. Methods of framing the NAL units in a manner other than use of the byte stream format are outside the scope of this Recommendation | International Standard. The byte stream format is specified in Annex B. + +### 6.2 Source, decoded, and output picture formats + +This clause specifies the relationship between source and decoded frames and fields that is given via the bitstream. + +The video source that is represented by the bitstream is a sequence of either or both frames or fields (called collectively pictures) in decoding order. + +The source and decoded pictures (frames or fields) are each comprised of one or more sample arrays: + +- Luma (Y) only (monochrome), with or without an auxiliary array. +- Luma and two Chroma (YCbCr or YCgCo), with or without an auxiliary array. +- Green, Blue and Red (GBR, also known as RGB), with or without an auxiliary array. +- Arrays representing other unspecified monochrome or tri-stimulus colour samplings (for example, YZX, also known as XYZ), with or without an auxiliary array. + +For convenience of notation and terminology in this Specification, the variables and terms associated with these arrays are referred to as luma (or L or Y) and chroma, where the two chroma arrays are referred to as Cb and Cr; regardless of the actual colour representation method in use. The actual colour representation method in use can be indicated in syntax that is specified in Annex E. The (monochrome) auxiliary arrays, which may or may not be present as auxiliary pictures in a coded video sequence, are optional for decoding and can be used for such purposes as alpha blending. + +The variables SubWidthC, and SubHeightC are specified in Table 6-1, depending on the chroma format sampling structure, which is specified through chroma\_format\_idc and separate\_colour\_plane\_flag. An entry marked as "-" in Table 6-1 denotes an undefined value for SubWidthC or SubHeightC. Other values of chroma\_format\_idc, SubWidthC, and SubHeightC may be specified in the future by ITU-T | ISO/IEC. + +**Table 6-1 – SubWidthC, and SubHeightC values derived from chroma\_format\_idc and separate\_colour\_plane\_flag** + +| chroma_format_idc | separate_colour_plane_flag | Chroma Format | SubWidthC | SubHeightC | +|-------------------|----------------------------|---------------|-----------|------------| +| 0 | 0 | monochrome | - | - | +| 1 | 0 | 4:2:0 | 2 | 2 | +| 2 | 0 | 4:2:2 | 2 | 1 | +| 3 | 0 | 4:4:4 | 1 | 1 | +| 3 | 1 | 4:4:4 | - | - | + +In monochrome sampling there is only one sample array, which is nominally considered the luma array. + +In 4:2:0 sampling, each of the two chroma arrays has half the height and half the width of the luma array. + +In 4:2:2 sampling, each of the two chroma arrays has the same height and half the width of the luma array. + +In 4:4:4 sampling, depending on the value of separate\_colour\_plane\_flag, the following applies: + +- If separate\_colour\_plane\_flag is equal to 0, each of the two chroma arrays has the same height and width as the luma array. +- Otherwise (separate\_colour\_plane\_flag is equal to 1), the three colour planes are separately processed as monochrome sampled pictures. + +The width and height of the luma sample arrays are each an integer multiple of 16. In coded video sequences using 4:2:0 chroma sampling, the width and height of chroma sample arrays are each an integer multiple of 8. In coded video sequences using 4:2:2 sampling, the width of the chroma sample arrays is an integer multiple of 8 and the height is an integer multiple of 16. The height of a luma array that is coded as two separate fields or in macroblock-adaptive frame-field coding (see below) is an integer multiple of 32. In coded video sequences using 4:2:0 chroma sampling, the height of each chroma array that is coded as two separate fields or in macroblock-adaptive frame-field coding (see below) is an integer multiple of 16. The width or height of pictures output from the decoding process need not be an integer multiple of 16 and can be specified using a cropping rectangle. + +The syntax for the luma and (when present) chroma arrays are ordered such when data for all three colour components is present, the data for the luma array is first, followed by any data for the Cb array, followed by any data for the Cr array, unless otherwise specified. + +The width of fields coded referring to a specific sequence parameter set is the same as that of frames coded referring to the same sequence parameter set (see below). The height of fields coded referring to a specific sequence parameter set is half that of frames coded referring to the same sequence parameter set (see below). + +The number of bits necessary for the representation of each of the samples in the luma and chroma arrays in a video sequence is in the range of 8 to 14, and the number of bits used in the luma array may differ from the number of bits used in the chroma arrays. + +When the value of chroma\_format\_idc is equal to 1, the nominal vertical and horizontal relative locations of luma and chroma samples in frames are shown in Figure 6-1. Alternative chroma sample relative locations may be indicated in video usability information (see Annex E). + +![Figure 6-1 - Nominal vertical and horizontal locations of 4:2:0 luma and chroma samples in a frame](76959415a1298a6f58ea1fff16fb01b6_img.jpg) + +The figure shows a grid of 'X' and 'O' symbols representing luma and chroma sample locations. 'X' marks luma samples, and 'O' marks chroma samples. The grid is arranged in rows and columns. Luma samples (X) are present at every grid intersection. Chroma samples (O) are located between every other vertical pair of luma samples in every other column, specifically aligned horizontally with the first, third, and fifth luma columns, and vertically centered between the first and second, third and fourth, and fifth and sixth luma rows. A label 'Frame' is on the right. A legend at the bottom specifies: 'X Location of luma sample' and 'O Location of chroma sample'. The reference code 'H.264(09)\_F6-1' is in the bottom right of the diagram area. + +Figure 6-1 - Nominal vertical and horizontal locations of 4:2:0 luma and chroma samples in a frame + +**Figure 6-1 – Nominal vertical and horizontal locations of 4:2:0 luma and chroma samples in a frame** + +A frame consists of two fields as described below. A coded picture may represent a coded frame or an individual coded field. A coded video sequence conforming to this Recommendation | International Standard may contain arbitrary combinations of coded frames and coded fields. The decoding process is also specified in a manner that allows smaller regions of a coded frame to be coded either as a frame or field region, by use of macroblock-adaptive frame-field coding. + +Source and decoded fields are one of two types: top field or bottom field. When two fields are output at the same time, or are combined to be used as a reference frame (see below), the two fields (which shall be of opposite parity) are interleaved. The first (i.e., top), third, fifth, etc., rows of a decoded frame are the top field rows. The second, fourth, sixth, etc., rows of a decoded frame are the bottom field rows. A top field consists of only the top field rows of a decoded frame. When the top field or bottom field of a decoded frame is used as a reference field (see below) only the even rows (for a top field) or the odd rows (for a bottom field) of the decoded frame are used. + +When the value of chroma\_format\_idc is equal to 1, the nominal vertical and horizontal relative locations of luma and chroma samples in top and bottom fields are shown in Figure 6-2. The nominal vertical sampling relative locations of the chroma samples in a top field are specified as shifted up by one-quarter luma sample height relative to the field-sampling grid. The vertical sampling locations of the chroma samples in a bottom field are specified as shifted down by one-quarter luma sample height relative to the field-sampling grid. Alternative chroma sample relative locations may be indicated in the video usability information (see Annex E). + +NOTE – The shifting of the chroma samples is in order for these samples to align vertically to the usual location relative to the full-frame sampling grid as shown in Figure 6-1. + +24          **Rec. ITU-T H.264 (V15) (08/2024)** + +![Diagram showing nominal vertical and horizontal sampling locations of 4:2:0 samples in top and bottom fields. The diagram is split into two sections: 'Top field' on the left and 'Bottom field' on the right. Each section shows a grid of 'X' marks (luma samples) and 'O' marks (chroma samples). In the top field, luma samples are at (1,1), (2,1), (3,1), (4,1), (5,1), (6,1) and chroma samples are at (1,2), (3,2), (5,2). In the bottom field, luma samples are at (1,1), (2,1), (3,1), (4,1), (5,1), (6,1) and chroma samples are at (1,2), (3,2), (5,2). Ellipses indicate continuation of the pattern.](657acccf744d33f1fc3a1652741a256e_img.jpg) + +X Location of luma sample +O Location of chroma sample + +H.264(09)\_F6-2 + +Diagram showing nominal vertical and horizontal sampling locations of 4:2:0 samples in top and bottom fields. The diagram is split into two sections: 'Top field' on the left and 'Bottom field' on the right. Each section shows a grid of 'X' marks (luma samples) and 'O' marks (chroma samples). In the top field, luma samples are at (1,1), (2,1), (3,1), (4,1), (5,1), (6,1) and chroma samples are at (1,2), (3,2), (5,2). In the bottom field, luma samples are at (1,1), (2,1), (3,1), (4,1), (5,1), (6,1) and chroma samples are at (1,2), (3,2), (5,2). Ellipses indicate continuation of the pattern. + +**Figure 6-2 – Nominal vertical and horizontal sampling locations of 4:2:0 samples in top and bottom fields** + +When the value of chroma\_format\_idc is equal to 2, the chroma samples are co-sited with the corresponding luma samples and the nominal locations in a frame and in fields are as shown in Figures 6-3 and 6-4, respectively. + +![Diagram showing nominal vertical and horizontal locations of 4:2:2 luma and chroma samples in a frame. The diagram shows a grid of 'X' marks (luma samples) and 'X' marks inside circles (chroma samples) co-sited at the same locations. The grid shows luma samples at (1,1), (2,1), (3,1), (4,1), (5,1), (6,1) and chroma samples at the same locations. Ellipses indicate continuation of the pattern.](9f92854fe6ecaf47760515c891a4fccc_img.jpg) + +X Location of luma sample +O Location of chroma sample + +H.264(09)\_F6-3 + +Diagram showing nominal vertical and horizontal locations of 4:2:2 luma and chroma samples in a frame. The diagram shows a grid of 'X' marks (luma samples) and 'X' marks inside circles (chroma samples) co-sited at the same locations. The grid shows luma samples at (1,1), (2,1), (3,1), (4,1), (5,1), (6,1) and chroma samples at the same locations. Ellipses indicate continuation of the pattern. + +**Figure 6-3 – Nominal vertical and horizontal locations of 4:2:2 luma and chroma samples in a frame** + +![Diagram showing nominal vertical and horizontal sampling locations of 4:2:2 samples top and bottom fields. It displays two grids of samples, one for the 'Top field' and one for the 'Bottom field'. Each grid shows a regular pattern of 'X' marks (luma samples) and circled 'X' marks (chroma samples). The chroma samples are horizontally subsampled compared to the luma samples. Vertical ellipses and horizontal ellipses indicate that the pattern continues.](6ef03c6e28f2f1fd4f98529146ffeccc_img.jpg) + +X Location of luma sample + ⊗ Location of chroma sample + +H.264(09)\_F6-4 + +Diagram showing nominal vertical and horizontal sampling locations of 4:2:2 samples top and bottom fields. It displays two grids of samples, one for the 'Top field' and one for the 'Bottom field'. Each grid shows a regular pattern of 'X' marks (luma samples) and circled 'X' marks (chroma samples). The chroma samples are horizontally subsampled compared to the luma samples. Vertical ellipses and horizontal ellipses indicate that the pattern continues. + +**Figure 6-4 – Nominal vertical and horizontal sampling locations of 4:2:2 samples top and bottom fields** + +When the value of chroma\_format\_idc is equal to 3, all array samples are co-sited for all cases of frames and fields and the nominal locations in a frame and in fields are as shown in Figures 6-5 and 6-6, respectively. + +![Diagram showing nominal vertical and horizontal locations of 4:4:4 luma and chroma samples in a frame. It displays a single grid of samples where every sample location contains both a luma sample (X) and a chroma sample (circled X), indicating full resolution for both components. Vertical ellipses and horizontal ellipses indicate that the pattern continues.](75b9cb95f5815d6f3bbe57020a049504_img.jpg) + +X Location of luma sample + ⊗ Location of chroma sample + +H.264(09)\_F6-5 + +Diagram showing nominal vertical and horizontal locations of 4:4:4 luma and chroma samples in a frame. It displays a single grid of samples where every sample location contains both a luma sample (X) and a chroma sample (circled X), indicating full resolution for both components. Vertical ellipses and horizontal ellipses indicate that the pattern continues. + +**Figure 6-5 – Nominal vertical and horizontal locations of 4:4:4 luma and chroma samples in a frame** + +![Diagram showing nominal vertical and horizontal sampling locations of 4:4:4 samples top and bottom fields. The diagram illustrates two fields, 'Top field' and 'Bottom field', each containing a grid of samples. The 'Top field' grid shows a 6x4 arrangement of samples, with the first row starting at the top left. The 'Bottom field' grid shows a 6x4 arrangement of samples, with the first row starting at the top right. The legend indicates that 'X' represents the location of a luma sample and 'O' represents the location of a chroma sample. The text 'H.264(09)_F6-6' is visible in the bottom right corner of the diagram area.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +⊗ ⊗ ⊗ ⊗ ⊗ ⊗ ... + +⊗ ⊗ ⊗ ⊗ ⊗ ⊗ + +Top field + +⊗ ⊗ ⊗ ⊗ ⊗ ⊗ + +⋮ ⋮ + +⊗ ⊗ ⊗ ⊗ ⊗ ⊗ ... + +⊗ ⊗ ⊗ ⊗ ⊗ ⊗ + +Bottom field + +⊗ ⊗ ⊗ ⊗ ⊗ ⊗ + +⋮ ⋮ + +X Location of luma sample +O Location of chroma sample + +H.264(09)\_F6-6 + +Diagram showing nominal vertical and horizontal sampling locations of 4:4:4 samples top and bottom fields. The diagram illustrates two fields, 'Top field' and 'Bottom field', each containing a grid of samples. The 'Top field' grid shows a 6x4 arrangement of samples, with the first row starting at the top left. The 'Bottom field' grid shows a 6x4 arrangement of samples, with the first row starting at the top right. The legend indicates that 'X' represents the location of a luma sample and 'O' represents the location of a chroma sample. The text 'H.264(09)\_F6-6' is visible in the bottom right corner of the diagram area. + +**Figure 6-6 – Nominal vertical and horizontal sampling locations of 4:4:4 samples top and bottom fields** + +The samples are processed in units of macroblocks. The luma array for each macroblock is 16 samples in both width and height. The variables MbWidthC and MbHeightC, which specify the width and height, respectively, of the chroma arrays for each macroblock, are derived as follows: + +- If chroma\_format\_idc is equal to 0 (monochrome) or separate\_colour\_plane\_flag is equal to 1, MbWidthC and MbHeightC are both equal to 0. +- Otherwise, MbWidthC and MbHeightC are derived as + +$$\text{MbWidthC} = 16 / \text{SubWidthC} \quad (6-1)$$ + +$$\text{MbHeightC} = 16 / \text{SubHeightC} \quad (6-2)$$ + +### 6.3 Spatial subdivision of pictures and slices + +This clause specifies how a picture is partitioned into slices and macroblocks. Pictures are divided into slices. A slice is a sequence of macroblocks, or, when macroblock-adaptive frame/field decoding is in use, a sequence of macroblock pairs. + +Each macroblock is comprised of one 16x16 luma array and, when the chroma sampling format is not equal to 4:0:0 and separate\_colour\_plane\_flag is equal to 0, two corresponding chroma sample arrays. When separate\_colour\_plane\_flag is equal to 1, each macroblock is comprised of one 16x16 luma or chroma sample array. When macroblock-adaptive frame/field decoding is not in use, each macroblock represents a spatial rectangular region of the picture. For example, a picture may be divided into two slices as shown in Figure 6-7. + +When a picture is coded using three separate colour planes (separate\_colour\_plane\_flag is equal to 1), a slice contains only macroblocks of one colour component being identified by the corresponding value of colour\_plane\_id, and each colour component array of a picture consists of slices having the same colour\_plane\_id value. Coded slices with different values of colour\_plane\_id within an access unit can be interleaved with each other under the constraint that for each value of colour\_plane\_id, the coded slice NAL units with that value colour\_plane\_id shall be in the order of increasing macroblock address for the first macroblock of each coded slice NAL unit. + +NOTE – When separate\_colour\_plane\_flag is equal to 0, each macroblock of a picture is contained in exactly one slice. When separate\_colour\_plane\_flag is equal to 1, each macroblock of a colour component is contained in exactly one slice (i.e., information for each macroblock of a picture is present in exactly three slices and these three slices have different values of colour\_plane\_id). + +![Figure 6-7: A grid of 11 by 9 macroblocks. A thick black line partitions the grid into two slices. The first slice contains the first 4 columns of the first 5 rows. The second slice contains the remaining 7 columns of the first 5 rows, plus all 11 columns of the remaining 4 rows.](9a627a1ad2e909ac4af71874ed1b0502_img.jpg) + +Figure 6-7: A grid of 11 by 9 macroblocks. A thick black line partitions the grid into two slices. The first slice contains the first 4 columns of the first 5 rows. The second slice contains the remaining 7 columns of the first 5 rows, plus all 11 columns of the remaining 4 rows. + +H.264(09)\_F6-7 + +Figure 6-7 – A picture with 11 by 9 macroblocks that is partitioned into two slices + +When macroblock-adaptive frame/field decoding is in use, the picture is partitioned into slices containing an integer number of macroblock pairs as shown in Figure 6-8. Each macroblock pair consists of two macroblocks. + +![Figure 6-8: A grid of 11 by 9 macroblocks. A vertical dashed line partitions the grid into two slices. The first slice contains the first 5 columns. The second slice contains the remaining 6 columns. Within the second slice, a 2x1 block of macroblocks is highlighted with a solid black border and an arrow pointing to it from the text 'A macroblock pair'.](8e77aa74bd5ab059077bf9bdb397e287_img.jpg) + +Figure 6-8: A grid of 11 by 9 macroblocks. A vertical dashed line partitions the grid into two slices. The first slice contains the first 5 columns. The second slice contains the remaining 6 columns. Within the second slice, a 2x1 block of macroblocks is highlighted with a solid black border and an arrow pointing to it from the text 'A macroblock pair'. + +H.264(09)\_F6-8 + +Figure 6-8 – Partitioning of the decoded frame into macroblock pairs + +## 6.4 Inverse scanning processes and derivation processes for neighbours + +This clause specifies inverse scanning processes; i.e., the mapping of indices to locations, and derivation processes for neighbours. + +### 6.4.1 Inverse macroblock scanning process + +Input to this process is a macroblock address mbAddr. + +Output of this process is the location ( x, y ) of the upper-left luma sample for the macroblock with address mbAddr relative to the upper-left sample of the picture. + +The inverse macroblock scanning process is specified as follows: + +- If MbaffFrameFlag is equal to 0, + +$$x = \text{InverseRasterScan}(\text{mbAddr}, 16, 16, \text{PicWidthInSamples}_L, 0) \quad (6-3)$$ + +$$y = \text{InverseRasterScan}(\text{mbAddr}, 16, 16, \text{PicWidthInSamples}_L, 1) \quad (6-4)$$ + +- Otherwise (MbaffFrameFlag is equal to 1), the following ordered steps are specified: + +1. The luma location ( xO, yO ) is derived by + +$$xO = \text{InverseRasterScan}( \text{mbAddr} / 2, 16, 32, \text{PicWidthInSamplesL}, 0 ) \quad (6-5)$$ + +$$yO = \text{InverseRasterScan}( \text{mbAddr} / 2, 16, 32, \text{PicWidthInSamplesL}, 1 ) \quad (6-6)$$ + +2. Depending on the current macroblock the following applies: + +- If the current macroblock is a frame macroblock + +$$x = xO \quad (6-7)$$ + +$$y = yO + ( \text{mbAddr} \% 2 ) * 16 \quad (6-8)$$ + +- Otherwise (the current macroblock is a field macroblock), + +$$x = xO \quad (6-9)$$ + +$$y = yO + ( \text{mbAddr} \% 2 ) \quad (6-10)$$ + +#### 6.4.2 Inverse macroblock partition and sub-macroblock partition scanning process + +Macroblocks or sub-macroblocks may be partitioned, and the partitions are scanned for inter prediction as shown in Figure 6-9. The outer rectangles refer to the samples in a macroblock or sub-macroblock, respectively. The rectangles refer to the partitions. The number in each rectangle specifies the index of the inverse macroblock partition scan or inverse sub-macroblock partition scan. + +The functions MbPartWidth(), MbPartHeight(), SubMbPartWidth(), and SubMbPartHeight() describing the width and height of macroblock partitions and sub-macroblock partitions are specified in Tables 7-13, 7-14, 7-17, and 7-18. MbPartWidth() and MbPartHeight() are set to appropriate values for each macroblock, depending on the macroblock type. SubMbPartWidth() and SubMbPartHeight() are set to appropriate values for each sub-macroblock of a macroblock with mb\_type equal to P\_8x8, P\_8x8ref0, or B\_8x8, depending on the sub-macroblock type. + +![A single square partition labeled 0. Two horizontal rectangular partitions labeled 0 (top) and 1 (bottom). Two vertical rectangular partitions labeled 0 (left) and 1 (right). A 2x2 grid of square partitions labeled 0, 1 (top) and 2, 3 (bottom). A single square sub-partition labeled 0. Two horizontal rectangular sub-partitions labeled 0 (top) and 1 (bottom). Two vertical rectangular sub-partitions labeled 0 (left) and 1 (right). A 2x2 grid of square sub-partitions labeled 0, 1 (top) and 2, 3 (bottom).](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg) + +| | 1 macroblock partition of 16*16 luma samples and associated chroma samples | 2 macroblock partitions of 16*8 luma samples and associated chroma samples | 2 macroblock partitions of 8*16 luma samples and associated chroma samples | 4 sub-macroblocks of 8*8 luma samples and associated chroma samples | +|----------------------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| Macroblock partitions | | | | | +| | 1 sub-macroblock partition of 8*8 luma samples and associated chroma samples | 2 sub-macroblock partitions of 8*4 luma samples and associated chroma samples | 2 sub-macroblock partitions of 4*8 luma samples and associated chroma samples | 4 sub-macroblock partitions of 4*4 luma samples and associated chroma samples | +| Sub-macroblock partitions | | | | | + +H.264(09)\_F6-9 + +A single square partition labeled 0. Two horizontal rectangular partitions labeled 0 (top) and 1 (bottom). Two vertical rectangular partitions labeled 0 (left) and 1 (right). A 2x2 grid of square partitions labeled 0, 1 (top) and 2, 3 (bottom). A single square sub-partition labeled 0. Two horizontal rectangular sub-partitions labeled 0 (top) and 1 (bottom). Two vertical rectangular sub-partitions labeled 0 (left) and 1 (right). A 2x2 grid of square sub-partitions labeled 0, 1 (top) and 2, 3 (bottom). + +**Figure 6-9 – Macroblock partitions, sub-macroblock partitions, macroblock partition scans, and sub-macroblock partition scans** + +#### 6.4.2.1 Inverse macroblock partition scanning process + +Input to this process is the index of a macroblock partition mbPartIdx. + +Output of this process is the location ( x, y ) of the upper-left luma sample for the macroblock partition mbPartIdx relative to the upper-left sample of the macroblock. + +The inverse macroblock partition scanning process is specified by + +$$x = \text{InverseRasterScan}( \text{mbPartIdx}, \text{MbPartWidth}( \text{mb\_type} ), \text{MbPartHeight}( \text{mb\_type} ), 16, 0 ) \quad (6-11)$$ + +$$y = \text{InverseRasterScan}( \text{mbPartIdx}, \text{MbPartWidth}( \text{mb\_type} ), \text{MbPartHeight}( \text{mb\_type} ), 16, 1 ) \quad (6-12)$$ + +#### 6.4.2.2 Inverse sub-macroblock partition scanning process + +Inputs to this process are the index of a macroblock partition mbPartIdx and the index of a sub-macroblock partition subMbPartIdx. + +Output of this process is the location ( x, y ) of the upper-left luma sample for the sub-macroblock partition subMbPartIdx relative to the upper-left sample of the sub-macroblock. + +The inverse sub-macroblock partition scanning process is specified as follows: + +- If mb\_type is equal to P\_8x8, P\_8x8ref0, or B\_8x8, + +$$x = \text{InverseRasterScan}( \text{subMbPartIdx}, \text{SubMbPartWidth}( \text{sub\_mb\_type}[ \text{mbPartIdx} ] ), \text{SubMbPartHeight}( \text{sub\_mb\_type}[ \text{mbPartIdx} ] ), 8, 0 ) \quad (6-13)$$ + +$$y = \text{InverseRasterScan}( \text{subMbPartIdx}, \text{SubMbPartWidth}( \text{sub\_mb\_type}[ \text{mbPartIdx} ] ), \text{SubMbPartHeight}( \text{sub\_mb\_type}[ \text{mbPartIdx} ] ), 8, 1 ) \quad (6-14)$$ + +- Otherwise (mb\_type is not equal to P\_8x8, P\_8x8ref0, or B\_8x8), + +$$x = \text{InverseRasterScan}( \text{subMbPartIdx}, 4, 4, 8, 0 ) \quad (6-15)$$ + +$$y = \text{InverseRasterScan}( \text{subMbPartIdx}, 4, 4, 8, 1 ) \quad (6-16)$$ + +#### 6.4.3 Inverse 4x4 luma block scanning process + +Input to this process is the index of a 4x4 luma block luma4x4BlkIdx. + +Output of this process is the location ( x, y ) of the upper-left luma sample for the 4x4 luma block with index luma4x4BlkIdx relative to the upper-left luma sample of the macroblock. + +Figure 6-10 shows the scan for the 4x4 luma blocks. + +| | | | | +|----|----|----|----| +| 0 | 1 | 4 | 5 | +| 2 | 3 | 6 | 7 | +| 8 | 9 | 12 | 13 | +| 10 | 11 | 14 | 15 | + +**Figure 6-10 – Scan for 4x4 luma blocks** + +The inverse 4x4 luma block scanning process is specified by + +$$x = \text{InverseRasterScan}(\text{ luma4x4BlkIdx } / 4, 8, 8, 16, 0 ) + \text{InverseRasterScan}(\text{ luma4x4BlkIdx } \% 4, 4, 4, 8, 0 ) \quad (6-17)$$ + +$$y = \text{InverseRasterScan}(\text{ luma4x4BlkIdx } / 4, 8, 8, 16, 1 ) + \text{InverseRasterScan}(\text{ luma4x4BlkIdx } \% 4, 4, 4, 8, 1 ) \quad (6-18)$$ + +**6.4.4 Inverse 4x4 Cb or Cr block scanning process for ChromaArrayType equal to 3** + +This process is only invoked when ChromaArrayType is equal to 3. + +The inverse 4x4 chroma block scanning process is identical to inverse 4x4 luma block scanning process as specified in clause 6.4.3 when substituting the term "luma" with the term "Cb" or the term "Cr", and substituting the term "luma4x4BlkIdx" with the term "cb4x4BlkIdx" or the term "cr4x4BlkIdx" in all places in clause 6.4.3. + +**6.4.5 Inverse 8x8 luma block scanning process** + +Input to this process is the index of an 8x8 luma block luma8x8BlkIdx. + +Output of this process is the location ( x, y ) of the upper-left luma sample for the 8x8 luma block with index luma8x8BlkIdx relative to the upper-left luma sample of the macroblock. + +Figure 6-11 shows the scan for the 8x8 luma blocks. + +| | | +|---|---| +| 0 | 1 | +| 2 | 3 | + +**Figure 6-11 – Scan for 8x8 luma blocks** + +The inverse 8x8 luma block scanning process is specified by: + +$$x = \text{InverseRasterScan}(\text{ luma8x8BlkIdx, 8, 8, 16, 0 } ) \quad (6-19)$$ + +$$y = \text{InverseRasterScan}(\text{ luma8x8BlkIdx, 8, 8, 16, 1 } ) \quad (6-20)$$ + +**6.4.6 Inverse 8x8 Cb or Cr block scanning process for ChromaArrayType equal to 3** + +This process is only invoked when ChromaArrayType is equal to 3. + +The inverse 8x8 chroma block scanning process is identical to inverse 8x8 luma block scanning process as specified in clause 6.4.5 when substituting the term "luma" with the term "Cb" or the term "Cr", and substituting the term "luma8x8BlkIdx" with the term "cb8x8BlkIdx" or the term "cr8x8BlkIdx" in all places in clause 6.4.5. + +**6.4.7 Inverse 4x4 chroma block scanning process** + +Input to this process is the index of a 4x4 chroma block chroma4x4BlkIdx. + +Output of this process is the location ( x, y ) of the upper-left chroma sample for a 4x4 chroma block with index chroma4x4BlkIdx relative to the upper-left chroma sample of the macroblock. + +The inverse 4x4 chroma block scanning process is specified by + +$$x = \text{InverseRasterScan}(\text{chroma4x4BlkIdx}, 4, 4, 8, 0) \quad (6-21)$$ + +$$y = \text{InverseRasterScan}(\text{chroma4x4BlkIdx}, 4, 4, 8, 1) \quad (6-22)$$ + +#### 6.4.8 Derivation process of the availability for macroblock addresses + +Input to this process is a macroblock address mbAddr. + +Output of this process is the availability of the macroblock mbAddr. + +NOTE – The meaning of availability is determined when this process is invoked. + +The macroblock is marked as available, unless any of the following conditions are true, in which case the macroblock is marked as not available: + +- $\text{mbAddr} < 0$ , +- $\text{mbAddr} > \text{CurrMbAddr}$ , +- the macroblock with address mbAddr belongs to a different slice than the macroblock with address CurrMbAddr. + +#### 6.4.9 Derivation process for neighbouring macroblock addresses and their availability + +This process can only be invoked when MbaffFrameFlag is equal to 0. + +The outputs of this process are: + +- mbAddrA: the address and availability status of the macroblock to the left of the current macroblock, +- mbAddrB: the address and availability status of the macroblock above the current macroblock, +- mbAddrC: the address and availability status of the macroblock above-right of the current macroblock, +- mbAddrD: the address and availability status of the macroblock above-left of the current macroblock. + +Figure 6-12 shows the relative spatial locations of the macroblocks with mbAddrA, mbAddrB, mbAddrC, and mbAddrD relative to the current macroblock with CurrMbAddr. + +| | | | +|---------|------------|---------| +| mbAddrD | mbAddrB | mbAddrC | +| mbAddrA | CurrMbAddr | | +| | | | + +**Figure 6-12 – Neighbouring macroblocks for a given macroblock** + +Input to the process in clause 6.4.8 is $\text{mbAddrA} = \text{CurrMbAddr} - 1$ and the output is whether the macroblock mbAddrA is available. In addition, mbAddrA is marked as not available when $\text{CurrMbAddr} \% \text{PicWidthInMbs}$ is equal to 0. + +Input to the process in clause 6.4.8 is $\text{mbAddrB} = \text{CurrMbAddr} - \text{PicWidthInMbs}$ and the output is whether the macroblock mbAddrB is available. + +Input to the process in clause 6.4.8 is $\text{mbAddrC} = \text{CurrMbAddr} - \text{PicWidthInMbs} + 1$ and the output is whether the macroblock mbAddrC is available. In addition, mbAddrC is marked as not available when $(\text{CurrMbAddr} + 1) \% \text{PicWidthInMbs}$ is equal to 0. + +Input to the process in clause 6.4.8 is $mbAddrD = CurrMbAddr - PicWidthInMbs - 1$ and the output is whether the macroblock $mbAddrD$ is available. In addition, $mbAddrD$ is marked as not available when $CurrMbAddr \% PicWidthInMbs$ is equal to 0. + +#### 6.4.10 Derivation process for neighbouring macroblock addresses and their availability in MBAFF frames + +This process can only be invoked when MbaffFrameFlag is equal to 1. + +The outputs of this process are: + +- **mbAddrA**: the address and availability status of the top macroblock of the macroblock pair to the left of the current macroblock pair, +- **mbAddrB**: the address and availability status of the top macroblock of the macroblock pair above the current macroblock pair, +- **mbAddrC**: the address and availability status of the top macroblock of the macroblock pair above-right of the current macroblock pair, +- **mbAddrD**: the address and availability status of the top macroblock of the macroblock pair above-left of the current macroblock pair. + +Figure 6-13 shows the relative spatial locations of the macroblocks with $mbAddrA$ , $mbAddrB$ , $mbAddrC$ , and $mbAddrD$ relative to the current macroblock with $CurrMbAddr$ . + +$mbAddrA$ , $mbAddrB$ , $mbAddrC$ , and $mbAddrD$ have identical values regardless whether the current macroblock is the top or the bottom macroblock of a macroblock pair. + +| | | | +|---------|---------------|---------| +| mbAddrD | mbAddrB | mbAddrC | +| | | | +| mbAddrA | CurrMbAddr or | | +| | CurrMbAddr | | + +**Figure 6-13 – Neighbouring macroblocks for a given macroblock in MBAFF frames** + +Input to the process in clause 6.4.8 is $mbAddrA = 2 * ( CurrMbAddr / 2 - 1 )$ and the output is whether the macroblock $mbAddrA$ is available. In addition, $mbAddrA$ is marked as not available when $( CurrMbAddr / 2 ) \% PicWidthInMbs$ is equal to 0. + +Input to the process in clause 6.4.8 is $mbAddrB = 2 * ( CurrMbAddr / 2 - PicWidthInMbs )$ and the output is whether the macroblock $mbAddrB$ is available. + +Input to the process in clause 6.4.8 is $mbAddrC = 2 * ( CurrMbAddr / 2 - PicWidthInMbs + 1 )$ and the output is whether the macroblock $mbAddrC$ is available. In addition, $mbAddrC$ is marked as not available when $( CurrMbAddr / 2 + 1 ) \% PicWidthInMbs$ is equal to 0. + +Input to the process in clause 6.4.8 is $mbAddrD = 2 * ( CurrMbAddr / 2 - PicWidthInMbs - 1 )$ and the output is whether the macroblock $mbAddrD$ is available. In addition, $mbAddrD$ is marked as not available when $( CurrMbAddr / 2 ) \% PicWidthInMbs$ is equal to 0. + +#### 6.4.11 Derivation processes for neighbouring macroblocks, blocks, and partitions + +Clause 6.4.11.1 specifies the derivation process for neighbouring macroblocks. + +Clause 6.4.11.2 specifies the derivation process for neighbouring 8x8 luma blocks. + +Clause 6.4.11.3 specifies the derivation process for neighbouring 8x8 chroma blocks for ChromaArrayType equal to 3. + +Clause 6.4.11.4 specifies the derivation process for neighbouring 4x4 luma blocks. + +Clause 6.4.11.5 specifies the derivation process for neighbouring 4x4 chroma blocks. + +Clause 6.4.11.6 specifies the derivation process for neighbouring 4x4 chroma blocks for ChromaArrayType equal to 3. + +Clause 6.4.11.7 specifies the derivation process for neighbouring partitions. + +Table 6-2 specifies the values for the difference of luma location $( xD, yD )$ for the input and the replacement for N in *mbAddrN*, *mbPartIdxN*, *subMbPartIdxN*, *luma8x8BlkIdxN*, *cb8x8BlkIdxN*, *cr8x8BlkIdxN*, *luma4x4BlkIdxN*, *cb4x4BlkIdxN*, *cr4x4BlkIdxN*, and *chroma4x4BlkIdxN* for the output. These input and output assignments are used in clauses 6.4.11.1 to 6.4.11.7. The variable *predPartWidth* is specified when Table 6-2 is referred to. + +**Table 6-2 – Specification of input and output assignments for clauses 6.4.11.1 to 6.4.11.7** + +| N | xD | yD | +|---|---------------|----| +| A | -1 | 0 | +| B | 0 | -1 | +| C | predPartWidth | -1 | +| D | -1 | -1 | + +Figure 6-14 illustrates the relative location of the neighbouring macroblocks, blocks, or partitions A, B, C, and D to the current macroblock, partition, or block, when the current macroblock, partition, or block is in frame coding mode. + +![Diagram showing the relative location of neighbouring macroblocks, blocks, or partitions A, B, C, and D to the current macroblock, partition, or block. The diagram is a grid where D is top-left, B is top-center, C is top-right, A is middle-left, and the center cell is the current macroblock.](237b76118be454462fc9b4e96adaa6c7_img.jpg) + +| | | | +|---|---------------------------------------------------|---| +| D | B | C | +| A | Current
Macroblock
or Partition
or Block | | + +Diagram showing the relative location of neighbouring macroblocks, blocks, or partitions A, B, C, and D to the current macroblock, partition, or block. The diagram is a grid where D is top-left, B is top-center, C is top-right, A is middle-left, and the center cell is the current macroblock. + +**Figure 6-14 – Determination of the neighbouring macroblock, blocks, and partitions (informative)** + +#### 6.4.11.1 Derivation process for neighbouring macroblocks + +Outputs of this process are: + +- *mbAddrA*: the address of the macroblock to the left of the current macroblock and its availability status, +- *mbAddrB*: the address of the macroblock above the current macroblock and its availability status. + +*mbAddrN* (with N being A or B) is derived as specified by the following ordered steps: + +1. The difference of luma location $( xD, yD )$ is set according to Table 6-2. +2. The derivation process for neighbouring locations as specified in clause 6.4.12 is invoked for luma locations with $( xN, yN )$ equal to $( xD, yD )$ , and the output is assigned to *mbAddrN*. + +#### 6.4.11.2 Derivation process for neighbouring 8x8 luma block + +Input to this process is an 8x8 luma block index *luma8x8BlkIdx*. + +The *luma8x8BlkIdx* specifies the 8x8 luma blocks of a macroblock in a raster scan. + +Outputs of this process are: + +- *mbAddrA*: either equal to *CurrMbAddr* or the address of the macroblock to the left of the current macroblock and its availability status, + +- luma8x8BlkIdxA: the index of the 8x8 luma block to the left of the 8x8 block with index luma8x8BlkIdx and its availability status, +- mbAddrB: either equal to CurrMbAddr or the address of the macroblock above the current macroblock and its availability status, +- luma8x8BlkIdxB: the index of the 8x8 luma block above the 8x8 block with index luma8x8BlkIdx and its availability status. + +mbAddrN and luma8x8BlkIdxN (with N being A or B) are derived as specified by the following ordered steps: + +1. The difference of luma location ( xD, yD ) is set according to Table 6-2. +2. The luma location ( xN, yN ) is specified by + +$$xN = ( \text{luma8x8BlkIdx} \% 2 ) * 8 + xD \tag{6-23}$$ + +$$yN = ( \text{luma8x8BlkIdx} / 2 ) * 8 + yD \tag{6-24}$$ + +3. The derivation process for neighbouring locations as specified in clause 6.4.12 is invoked for luma locations with ( xN, yN ) as the input and the output is assigned to mbAddrN and ( xW, yW ). +4. The variable luma8x8BlkIdxN is derived as follows: + - If mbAddrN is not available, luma8x8BlkIdxN is marked as not available. + - Otherwise (mbAddrN is available), the derivation process for 8x8 luma block indices as specified in clause 6.4.13.3 is invoked with the luma location ( xW, yW ) as the input and the output is assigned to luma8x8BlkIdxN. + +#### 6.4.11.3 Derivation process for neighbouring 8x8 chroma blocks for ChromaArrayType equal to 3 + +This process is only invoked when ChromaArrayType is equal to 3. + +The derivation process for neighbouring 8x8 chroma block is identical to the derivation process for neighbouring 8x8 luma block as specified in clause 6.4.11.2 when substituting the term "luma" with the term "Cb" or the term "Cr", and substituting the term "luma8x8BlkIdx" with the term "cb8x8BlkIdx" or the term "cr8x8BlkIdx" in all places in clause 6.4.11.2. + +#### 6.4.11.4 Derivation process for neighbouring 4x4 luma blocks + +Input to this process is a 4x4 luma block index luma4x4BlkIdx. + +Outputs of this process are: + +- mbAddrA: either equal to CurrMbAddr or the address of the macroblock to the left of the current macroblock and its availability status, +- luma4x4BlkIdxA: the index of the 4x4 luma block to the left of the 4x4 block with index luma4x4BlkIdx and its availability status, +- mbAddrB: either equal to CurrMbAddr or the address of the macroblock above the current macroblock and its availability status, +- luma4x4BlkIdxB: the index of the 4x4 luma block above the 4x4 block with index luma4x4BlkIdx and its availability status. + +mbAddrN and luma4x4BlkIdxN (with N being A or B) are derived as specified by the following ordered steps: + +1. The difference of luma location ( xD, yD ) is set according to Table 6-2. +2. The inverse 4x4 luma block scanning process as specified in clause 6.4.3 is invoked with luma4x4BlkIdx as the input and ( x, y ) as the output. +3. The luma location ( xN, yN ) is specified by: + +$$xN = x + xD \tag{6-25}$$ + +$$yN = y + yD \tag{6-26}$$ + +4. The derivation process for neighbouring locations as specified in clause 6.4.12 is invoked for luma locations with ( xN, yN ) as the input and the output is assigned to mbAddrN and ( xW, yW ). + +5. The variable luma4x4BlkIdxN is derived as follows: + - If mbAddrN is not available, luma4x4BlkIdxN is marked as not available. + - Otherwise (mbAddrN is available), the derivation process for 4x4 luma block indices as specified in clause 6.4.13.1 is invoked with the luma location ( xW, yW ) as the input and the output is assigned to luma4x4BlkIdxN. + +#### 6.4.11.5 Derivation process for neighbouring 4x4 chroma blocks + +This clause is only invoked when ChromaArrayType is equal to 1 or 2. + +Input to this process is a 4x4 chroma block index chroma4x4BlkIdx. + +Outputs of this process are: + +- mbAddrA (either equal to CurrMbAddr or the address of the macroblock to the left of the current macroblock) and its availability status, +- chroma4x4BlkIdxA (the index of the 4x4 chroma block to the left of the 4x4 chroma block with index chroma4x4BlkIdx) and its availability status, +- mbAddrB (either equal to CurrMbAddr or the address of the macroblock above the current macroblock) and its availability status, +- chroma4x4BlkIdxB (the index of the 4x4 chroma block above the 4x4 chroma block with index chroma4x4BlkIdx) and its availability status. + +mbAddrN and chroma4x4BlkIdxN (with N being A or B) are derived as specified by the following ordered steps: + +1. The difference of chroma location ( xD, yD ) is set according to Table 6-2. +2. The inverse 4x4 chroma block scanning process as specified in clause 6.4.7 is invoked with chroma4x4BlkIdx as the input and ( x, y ) as the output. +3. The chroma location ( xN, yN ) is specified by + +$$xN = x + xD \tag{6-27}$$ + +$$yN = y + yD \tag{6-28}$$ + +4. The derivation process for neighbouring locations as specified in clause 6.4.12 is invoked for chroma locations with ( xN, yN ) as the input and the output is assigned to mbAddrN and ( xW, yW ). +5. The variable chroma4x4BlkIdxN is derived as follows: + - If mbAddrN is not available, chroma4x4BlkIdxN is marked as not available. + - Otherwise (mbAddrN is available), the derivation process for 4x4 chroma block indices as specified in clause 6.4.13.2 is invoked with the chroma location ( xW, yW ) as the input and the output is assigned to chroma4x4BlkIdxN. + +#### 6.4.11.6 Derivation process for neighbouring 4x4 chroma blocks for ChromaArrayType equal to 3 + +This process is only invoked when ChromaArrayType is equal to 3. + +The derivation process for neighbouring 4x4 chroma block in 4:4:4 chroma format is identical to the derivation process for neighbouring 4x4 luma block as specified in clause 6.4.11.4 when substituting the term "luma" with the term "Cb" or the term "Cr", and substituting the term "luma4x4BlkIdx" with the term "cb4x4BlkIdx" or the term "cr4x4BlkIdx" in all places in clause 6.4.11.4. + +#### 6.4.11.7 Derivation process for neighbouring partitions + +Inputs to this process are: + +- a macroblock partition index mbPartIdx +- a current sub-macroblock type currSubMbType +- a sub-macroblock partition index subMbPartIdx + +Outputs of this process are: + +- mbAddrA\mbPartIdxA\subMbPartIdxA: specifying the macroblock or sub-macroblock partition to the left of the current macroblock and its availability status, or the sub-macroblock partition CurrMbAddr\mbPartIdx\subMbPartIdx and its availability status, +- mbAddrB\mbPartIdxB\subMbPartIdxB: specifying the macroblock or sub-macroblock partition above the current macroblock and its availability status, or the sub-macroblock partition CurrMbAddr\mbPartIdx\subMbPartIdx and its availability status, +- mbAddrC\mbPartIdxC\subMbPartIdxC: specifying the macroblock or sub-macroblock partition to the right-above of the current macroblock and its availability status, or the sub-macroblock partition CurrMbAddr\mbPartIdx\subMbPartIdx and its availability status, +- mbAddrD\mbPartIdxD\subMbPartIdxD: specifying the macroblock or sub-macroblock partition to the left-above of the current macroblock and its availability status, or the sub-macroblock partition CurrMbAddr\mbPartIdx\subMbPartIdx and its availability status. + +mbAddrN, mbPartIdxN, and subMbPartIdxN (with N being A, B, C, or D) are derived as specified by the following ordered steps: + +1. The inverse macroblock partition scanning process as described in clause 6.4.2.1 is invoked with mbPartIdx as the input and ( x, y ) as the output. +2. The location of the upper-left luma sample inside a macroblock partition ( xS, yS ) is derived as follows: + - If mb\_type is equal to P\_8x8, P\_8x8ref0 or B\_8x8, the inverse sub-macroblock partition scanning process as described in clause 6.4.2.2 is invoked with subMbPartIdx as the input and ( xS, yS ) as the output. + - Otherwise, ( xS, yS ) are set to ( 0, 0 ). +3. The variable predPartWidth in Table 6-2 is specified as follows: + - If mb\_type is equal to P\_Skip, B\_Skip, or B\_Direct\_16x16, predPartWidth = 16. + - Otherwise, if mb\_type is equal to B\_8x8, the following applies: + - If currSubMbType is equal to B\_Direct\_8x8, predPartWidth = 16. + +NOTE 1 – When currSubMbType is equal to B\_Direct\_8x8 and direct\_spatial\_mv\_pred\_flag is equal to 1, the predicted motion vector is the predicted motion vector for the complete macroblock. + - Otherwise, predPartWidth = SubMbPartWidth( sub\_mb\_type[ mbPartIdx ] ). + - Otherwise, if mb\_type is equal to P\_8x8 or P\_8x8ref0, predPartWidth = SubMbPartWidth( sub\_mb\_type[ mbPartIdx ] ). + - Otherwise, predPartWidth = MbPartWidth( mb\_type ). +4. The difference of luma location ( xD, yD ) is set according to Table 6-2. +5. The neighbouring luma location ( xN, yN ) is specified by + +$$xN = x + xS + xD \tag{6-29}$$ + +$$yN = y + yS + yD \tag{6-30}$$ + +6. The derivation process for neighbouring locations as specified in clause 6.4.12 is invoked for luma locations with ( xN, yN ) as the input and the output is assigned to mbAddrN and ( xW, yW ). +7. Depending on mbAddrN, the following applies: + - If mbAddrN is not available, the macroblock or sub-macroblock partition mbAddrN\mbPartIdxN\subMbPartIdxN is marked as not available. + - Otherwise (mbAddrN is available), the following ordered steps are specified: + - a. Let mbTypeN be the syntax element mb\_type of the macroblock with macroblock address mbAddrN and, when mbTypeN is equal to P\_8x8, P\_8x8ref0, or B\_8x8, let subMbTypeN be the syntax element list sub\_mb\_type of the macroblock with macroblock address mbAddrN. + - b. The derivation process for macroblock and sub-macroblock partition indices as specified in clause 6.4.13.4 is invoked with the luma location ( xW, yW ), the macroblock type mbTypeN, and, when mbTypeN is equal to P\_8x8, P\_8x8ref0, or B\_8x8, the list of sub-macroblock types + +subMbTypeN as the inputs and the outputs are the macroblock partition index mbPartIdxN and the sub-macroblock partition index subMbPartIdxN. + +- c. When the partition given by mbPartIdxN and subMbPartIdxN is not yet decoded, the macroblock partition mbPartIdxN and the sub-macroblock partition subMbPartIdxN are marked as not available. + +NOTE 2 – The latter condition is, for example, the case when mbPartIdx = 2, subMbPartIdx = 3, xD = 4, yD = −1, i.e., when neighbour C of the last 4x4 luma block of the third sub-macroblock is requested. + +#### 6.4.12 Derivation process for neighbouring locations + +Input to this process is a luma or chroma location ( xN, yN ) expressed relative to the upper left corner of the current macroblock. + +Outputs of this process are: + +- mbAddrN: either equal to CurrMbAddr or to the address of neighbouring macroblock that contains (xN, yN) and its availability status, +- ( xW, yW ): the location (xN, yN) expressed relative to the upper-left corner of the macroblock mbAddrN (rather than relative to the upper-left corner of the current macroblock). + +Let maxW and maxH be variables specifying maximum values of the location components xN, xW, and yN, yW, respectively. maxW and maxH are derived as follows: + +- If this process is invoked for neighbouring luma locations, + +$$\text{maxW} = \text{maxH} = 16 \quad (6-31)$$ + +- Otherwise (this process is invoked for neighbouring chroma locations), + +$$\text{maxW} = \text{MbWidthC} \quad (6-32)$$ + +$$\text{maxH} = \text{MbHeightC} \quad (6-33)$$ + +Depending on the variable MbaffFrameFlag, the neighbouring locations are derived as follows: + +- If MbaffFrameFlag is equal to 0, the specification for neighbouring locations in fields and non-MBAFF frames as described in clause 6.4.12.1 is applied. +- Otherwise (MbaffFrameFlag is equal to 1), the specification for neighbouring locations in MBAFF frames as described in clause 6.4.12.2 is applied. + +##### 6.4.12.1 Specification for neighbouring locations in fields and non-MBAFF frames + +The specifications in this clause are applied when MbaffFrameFlag is equal to 0. + +The derivation process for neighbouring macroblock addresses and their availability in clause 6.4.9 is invoked with mbAddrA, mbAddrB, mbAddrC, and mbAddrD as well as their availability status as the output. + +Table 6-3 specifies mbAddrN depending on ( xN, yN ). + +**Table 6-3 – Specification of mbAddrN** + +| xN | yN | mbAddrN | +|-------------|-------------|---------------| +| < 0 | < 0 | mbAddrD | +| < 0 | 0..maxH − 1 | mbAddrA | +| 0..maxW − 1 | < 0 | mbAddrB | +| 0..maxW − 1 | 0..maxH − 1 | CurrMbAddr | +| > maxW − 1 | < 0 | mbAddrC | +| > maxW − 1 | 0..maxH − 1 | not available | +| | > maxH − 1 | not available | + +The neighbouring location ( $xW$ , $yW$ ) relative to the upper-left corner of the macroblock $mbAddrN$ is derived as + +$$xW = ( xN + maxW ) \% maxW \quad (6-34)$$ + +$$yW = ( yN + maxH ) \% maxH \quad (6-35)$$ + +#### 6.4.12.2 Specification for neighbouring locations in MBAFF frames + +The specifications in this clause are applied when $MbaffFrameFlag$ is equal to 1. + +The derivation process for neighbouring macroblock addresses and their availability in clause 6.4.10 is invoked with $mbAddrA$ , $mbAddrB$ , $mbAddrC$ , and $mbAddrD$ as well as their availability status as the output. + +The variable $currMbFrameFlag$ is derived as follows: + +- If the macroblock with address $CurrMbAddr$ is a frame macroblock, $currMbFrameFlag$ is set equal to 1. +- Otherwise (the macroblock with address $CurrMbAddr$ is a field macroblock), $currMbFrameFlag$ is set equal to 0. + +The variable $mbIsTopMbFlag$ is derived as follows: + +- If the macroblock with address $CurrMbAddr$ is a top macroblock (i.e., $CurrMbAddr \% 2$ is equal to 0), $mbIsTopMbFlag$ is set equal to 1. +- Otherwise (the macroblock with address $CurrMbAddr$ is a bottom macroblock, i.e., $CurrMbAddr \% 2$ is equal to 1), $mbIsTopMbFlag$ is set equal to 0. + +Table 6-4 specifies the macroblock addresses $mbAddrN$ and $yM$ in two ordered steps: + +1. Specification of a macroblock address $mbAddrX$ depending on ( $xN$ , $yN$ ) and the variables $currMbFrameFlag$ and $mbIsTopMbFlag$ : +2. Depending on the availability of $mbAddrX$ , the following applies: + - If $mbAddrX$ is not available, $mbAddrN$ is marked as not available. + - Otherwise ( $mbAddrX$ is available), $mbAddrN$ is marked as available and Table 6-4 specifies $mbAddrN$ and $yM$ depending on ( $xN$ , $yN$ ), $currMbFrameFlag$ , $mbIsTopMbFlag$ , and the variable $mbAddrXFrameFlag$ , which is derived as follows: + - If the macroblock $mbAddrX$ is a frame macroblock, $mbAddrXFrameFlag$ is set equal to 1. + - Otherwise (the macroblock $mbAddrX$ is a field macroblock), $mbAddrXFrameFlag$ is set equal to 0. + +Unspecified values (na) of the above flags in Table 6-4 indicate that the value of the corresponding flag is not relevant for the current table rows. + +Table 6-4 – Specification of mbAddrN and yM + +| xN | yN | currMbFrameFlag | mbIsTopMbFlag | mbAddrX | mbAddrXFrameFlag | additional condition | mbAddrN | yM | +|-------------|-------------|-----------------|---------------|---------------|------------------|----------------------|----------------|------------------------| +| < 0 | < 0 | 1 | 1 | mbAddrD | | | mbAddrD + 1 | yN | +| | | | 0 | mbAddrA | 1 | | mbAddrA | yN | +| | | | | | 0 | | mbAddrA + 1 | ( yN + maxH ) >> 1 | +| | | 0 | 1 | mbAddrD | 1 | | mbAddrD + 1 | 2 * yN | +| | | | | | 0 | | mbAddrD | yN | +| | | | 0 | mbAddrD | | | mbAddrD + 1 | yN | +| < 0 | 0..maxH – 1 | 1 | 1 | mbAddrA | 1 | | mbAddrA | yN | +| | | | | | 0 | yN % 2 == 0 | mbAddrA | yN >> 1 | +| | | | | | | yN % 2 != 0 | mbAddrA + 1 | yN >> 1 | +| | | | 0 | mbAddrA | 1 | | mbAddrA + 1 | yN | +| | | | | | 0 | yN % 2 == 0 | mbAddrA | ( yN + maxH ) >> 1 | +| | | 0 | 1 | mbAddrA | 0 | yN % 2 != 0 | mbAddrA + 1 | ( yN + maxH ) >> 1 | +| | | | | | 1 | yN < ( maxH / 2 ) | mbAddrA | yN << 1 | +| | | | | | | yN >= ( maxH / 2 ) | mbAddrA + 1 | ( yN << 1 ) – maxH | +| | | | | | 0 | | mbAddrA | yN | +| | | | 0 | mbAddrA | 1 | yN < ( maxH / 2 ) | mbAddrA | ( yN << 1 ) + 1 | +| | | | | | | yN >= ( maxH / 2 ) | mbAddrA + 1 | ( yN << 1 ) + 1 – maxH | +| | | | | | 0 | | mbAddrA + 1 | yN | +| 0..maxW – 1 | < 0 | 1 | 1 | mbAddrB | | | mbAddrB + 1 | yN | +| | | | 0 | CurrMbAddr | | | CurrMbAddr – 1 | yN | +| | | 0 | 1 | mbAddrB | 1 | | mbAddrB + 1 | 2 * yN | +| | | | | | 0 | | mbAddrB | yN | +| 0..maxW – 1 | 0..maxH – 1 | | | CurrMbAddr | | | CurrMbAddr | yN | +| > maxW – 1 | < 0 | 1 | 1 | mbAddrC | | | mbAddrC + 1 | yN | +| | | | 0 | not available | | | not available | na | +| | | 0 | 1 | mbAddrC | 1 | | mbAddrC + 1 | 2 * yN | +| | | | | | 0 | | mbAddrC | yN | +| > maxW – 1 | 0..maxH – 1 | | | not available | | | not available | na | +| | > maxH – 1 | | | not available | | | not available | na | + +The neighbouring luma location ( xW, yW ) relative to the upper-left corner of the macroblock mbAddrN is derived as + +$$xW = ( xN + maxW ) \% maxW \quad (6-36)$$ + +$$yW = ( yM + maxH ) \% maxH \quad (6-37)$$ + +#### 6.4.13 Derivation processes for block and partition indices + +Clause 6.4.13.1 specifies the derivation process for 4x4 luma block indices. + +Clause 6.4.13.2 specifies the derivation process for 4x4 chroma block indices. + +Clause 6.4.13.3 specifies the derivation process for 8x8 luma block indices. + +Clause 6.4.13.4 specifies the derivation process for macroblock and sub-macroblock partition indices. + +#### 6.4.13.1 Derivation process for 4x4 luma block indices + +Input to this process is a luma location ( xP, yP ) relative to the upper-left luma sample of a macroblock. + +Output of this process is a 4x4 luma block index luma4x4BlkIdx. + +The 4x4 luma block index luma4x4BlkIdx is derived by + +$$\text{luma4x4BlkIdx} = 8 * ( yP / 8 ) + 4 * ( xP / 8 ) + 2 * ( ( yP \% 8 ) / 4 ) + ( ( xP \% 8 ) / 4 ) \quad (6-38)$$ + +#### 6.4.13.2 Derivation process for 4x4 chroma block indices + +This clause is only invoked when ChromaArrayType is equal to 1 or 2. + +Input to this process is a chroma location ( xP, yP ) relative to the upper-left chroma sample of a macroblock. + +Output of this process is a 4x4 chroma block index chroma4x4BlkIdx. + +The 4x4 chroma block index chroma4x4BlkIdx is derived by + +$$\text{chroma4x4BlkIdx} = 2 * ( yP / 4 ) + ( xP / 4 ) \quad (6-39)$$ + +#### 6.4.13.3 Derivation process for 8x8 luma block indices + +Input to this process is a luma location ( xP, yP ) relative to the upper-left luma sample of a macroblock. + +Outputs of this process is an 8x8 luma block index luma8x8BlkIdx. + +The 8x8 luma block index luma8x8BlkIdx is derived by + +$$\text{luma8x8BlkIdx} = 2 * ( yP / 8 ) + ( xP / 8 ) \quad (6-40)$$ + +#### 6.4.13.4 Derivation process for macroblock and sub-macroblock partition indices + +Inputs to this process are: + +- a luma location ( xP, yP ) relative to the upper-left luma sample of a macroblock, +- a macroblock type mbType, +- when mbType is equal to P\_8x8, P\_8x8ref0, or B\_8x8, a list of sub-macroblock types subMbType with 4 elements. + +Outputs of this process are: + +- a macroblock partition index mbPartIdx, +- a sub-macroblock partition index subMbPartIdx. + +The macroblock partition index mbPartIdx is derived as follows: + +- If mbType specifies an I macroblock type, mbPartIdx is set equal to 0. +- Otherwise (mbType does not specify an I macroblock type), mbPartIdx is derived by + +$$\text{mbPartIdx} = ( 16 / \text{MbPartWidth}(\text{mbType}) ) * ( yP / \text{MbPartHeight}(\text{mbType}) ) + ( xP / \text{MbPartWidth}(\text{mbType}) ) \quad (6-41)$$ + +The sub-macroblock partition index subMbPartIdx is derived as follows: + +- If mbType is not equal to P\_8x8, P\_8x8ref0, B\_8x8, B\_Skip, or B\_Direct\_16x16, subMbPartIdx is set equal to 0. +- Otherwise, if mbType is equal to B\_Skip or B\_Direct\_16x16, subMbPartIdx is derived by + +$$\text{subMbPartIdx} = 2 * ( ( yP \% 8 ) / 4 ) + ( ( xP \% 8 ) / 4 ) \quad (6-42)$$ + +- Otherwise (mbType is equal to P\_8x8, P\_8x8ref0, or B\_8x8), subMbPartIdx is derived by + +$$\text{subMbPartIdx} = ( 8 / \text{SubMbPartWidth}(\text{subMbType}[\text{mbPartIdx}]) ) * ( ( yP \% 8 ) / \text{SubMbPartHeight}(\text{subMbType}[\text{mbPartIdx}]) ) + ( ( xP \% 8 ) / \text{SubMbPartWidth}(\text{subMbType}[\text{mbPartIdx}]) ) \quad (6-43)$$ + +## 7 Syntax and semantics + +### 7.1 Method of specifying syntax in tabular form + +The syntax tables specify a superset of the syntax of all allowed bitstreams. Additional constraints on the syntax may be specified, either directly or indirectly, in other clauses. + +NOTE – An actual decoder should implement means for identifying entry points into the bitstream and means to identify and handle non-conforming bitstreams. The methods for identifying and handling errors and other such situations are not specified here. + +The following table lists examples of pseudo code used to describe the syntax. When **syntax\_element** appears, it specifies that a syntax element is parsed from the bitstream and the bitstream pointer is advanced to the next position beyond the syntax element in the bitstream parsing process. + +| | C | Descriptor | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|------------| +| /* A statement can be a syntax element with an associated syntax category and descriptor or can be an expression used to specify conditions for the existence, type, and quantity of syntax elements, as in the following two examples */ | | | +| syntax_element | 3 | ue(v) | +| conditioning statement | | | +| | | | +| /* A group of statements enclosed in curly brackets is a compound statement and is treated functionally as a single statement. */ | | | +| { | | | +| statement | | | +| statement | | | +| ... | | | +| } | | | +| | | | +| /* A "while" structure specifies a test of whether a condition is true, and if true, specifies evaluation of a statement (or compound statement) repeatedly until the condition is no longer true */ | | | +| while( condition ) | | | +| statement | | | +| | | | +| /* A "do ... while" structure specifies evaluation of a statement once, followed by a test of whether a condition is true, and if true, specifies repeated evaluation of the statement until the condition is no longer true */ | | | +| do | | | +| statement | | | +| while( condition ) | | | +| | | | +| /* An "if ... else" structure specifies a test of whether a condition is true, and if the condition is true, specifies evaluation of a primary statement, otherwise, specifies evaluation of an alternative statement. The "else" part of the structure and the associated alternative statement is omitted if no alternative statement evaluation is needed */ | | | +| if( condition ) | | | +| primary statement | | | +| else | | | +| alternative statement | | | +| | | | +| /* A "for" structure specifies evaluation of an initial statement, followed by a test of a condition, and if the condition is true, specifies repeated evaluation of a primary statement followed by a subsequent statement until the condition is no longer true. */ | | | +| for( initial statement; condition; subsequent statement ) | | | +| primary statement | | | + +## 7.2 Specification of syntax functions, categories, and descriptors + +The functions presented here are used in the syntactical description. These functions assume the existence of a bitstream pointer with an indication of the position of the next bit to be read by the decoding process from the bitstream. + +`byte_aligned()` is specified as follows: + +- If the current position in the bitstream is on a byte boundary, i.e., the next bit in the bitstream is the first bit in a byte, the return value of `byte_aligned()` is equal to TRUE. +- Otherwise, the return value of `byte_aligned()` is equal to FALSE. + +`more_data_in_byte_stream()`, which is used only in the byte stream NAL unit syntax structure specified in Annex B, is specified as follows: + +- If more data follow in the byte stream, the return value of `more_data_in_byte_stream()` is equal to TRUE. +- Otherwise, the return value of `more_data_in_byte_stream()` is equal to FALSE. + +`more_rbsp_data()` is specified as follows: + +- If there is no more data in the RBSP, the return value of `more_rbsp_data()` is equal to FALSE. +- Otherwise, the RBSP data is searched for the last (least significant, right-most) bit equal to 1 that is present in the RBSP. Given the position of this bit, which is the first bit (`rbsp_stop_one_bit`) of the `rbsp_trailing_bits()` syntax structure, the following applies: + - If there is more data in an RBSP before the `rbsp_trailing_bits()` syntax structure, the return value of `more_rbsp_data()` is equal to TRUE. + - Otherwise, the return value of `more_rbsp_data()` is equal to FALSE. + +The method for enabling determination of whether there is more data in the RBSP is specified by the application (or in Annex B for applications that use the byte stream format). + +`more_rbsp_trailing_data()` is specified as follows: + +- If there is more data in an RBSP, the return value of `more_rbsp_trailing_data()` is equal to TRUE. +- Otherwise, the return value of `more_rbsp_trailing_data()` is equal to FALSE. + +`next_bits(n)` provides the next bits in the bitstream for comparison purposes, without advancing the bitstream pointer. When used within the byte stream as specified in Annex B, `next_bits(n)` returns a value of 0 if fewer than `n` bits remain within the byte stream. + +`read_bits(n)` reads the next `n` bits from the bitstream and advances the bitstream pointer by `n` bit positions. When `n` is equal to 0, `read_bits(n)` is specified to return a value equal to 0 and to not advance the bitstream pointer. + +Categories (labelled in the table as **C**) specify the partitioning of slice data into at most three slice data partitions. Slice data partition A contains all syntax elements of category 2. Slice data partition B contains all syntax elements of category 3. Slice data partition C contains all syntax elements of category 4. The meaning of other category values is not specified. For some syntax elements, two category values, separated by a vertical bar, are used. In these cases, the category value to be applied is further specified in the text. For syntax structures used within other syntax structures, the categories of all syntax elements found within the included syntax structure are listed, separated by a vertical bar. A syntax element or syntax structure with category marked as "All" is present within all syntax structures that include that syntax element or syntax structure. For syntax structures used within other syntax structures, a numeric category value provided in a syntax table at the location of the inclusion of a syntax structure containing a syntax element with category marked as "All" is considered to apply to the syntax elements with category "All". + +The following descriptors specify the parsing process of each syntax element. For some syntax elements, two descriptors, separated by a vertical bar, are used. In these cases, the left descriptors apply when `entropy_coding_mode_flag` is equal to 0 and the right descriptor applies when `entropy_coding_mode_flag` is equal to 1. + +- `ae(v)`: context-adaptive arithmetic entropy-coded syntax element. The parsing process for this descriptor is specified in clause 9.3. +- `b(8)`: byte having any pattern of bit string (8 bits). The parsing process for this descriptor is specified by the return value of the function `read_bits(8)`. + +NOTE – The `b(8)` syntax descriptor is functionally the same as `u(8)` but is used in contexts where there is a desire to emphasize that the interpretation of the syntax element involves the processing of bytes and that each byte is not necessarily interpreted as an 8-bit unsigned integer; e.g. a syntax element parsed as `b(8)` is sometimes interpreted as a character code or part of a multi-byte character code. + +- ce(v): context-adaptive variable-length entropy-coded syntax element with the left bit first. The parsing process for this descriptor is specified in clause 9.2. +- f(n): fixed-pattern bit string using n bits written (from left to right) with the left bit first. The parsing process for this descriptor is specified by the return value of the function read\_bits( n ). +- i(n): signed integer using n bits. When n is "v" in the syntax table, the number of bits varies in a manner dependent on the value of other syntax elements. The parsing process for this descriptor is specified by the return value of the function read\_bits( n ) interpreted as a two's complement integer representation with most significant bit written first. +- me(v): mapped Exp-Golomb-coded syntax element with the left bit first. The parsing process for this descriptor is specified in clause 9.1. +- se(v): signed integer Exp-Golomb-coded syntax element with the left bit first. The parsing process for this descriptor is specified in clause 9.1. +- te(v): truncated Exp-Golomb-coded syntax element with left bit first. The parsing process for this descriptor is specified in clause 9.1. +- u(n): unsigned integer using n bits. When n is "v" in the syntax table, the number of bits varies in a manner dependent on the value of other syntax elements. The parsing process for this descriptor is specified by the return value of the function read\_bits( n ) interpreted as a binary representation of an unsigned integer with most significant bit written first. +- ue(v): unsigned integer Exp-Golomb-coded syntax element with the left bit first. The parsing process for this descriptor is specified in clause 9.1. + +### 7.3 Syntax in tabular form + +#### 7.3.1 NAL unit syntax + +| nal_unit( NumBytesInNALUnit ) { | C | Descriptor | +|------------------------------------------------------------------------------|-----|------------| +| forbidden_zero_bit | All | f(1) | +| nal_ref_idc | All | u(2) | +| nal_unit_type | All | u(5) | +| NumBytesInRBSP = 0 | | | +| nalUnitHeaderBytes = 1 | | | +| if( nal_unit_type == 14 nal_unit_type == 20
nal_unit_type == 21 ) { | | | +| if( nal_unit_type != 21 ) | | | +| svc_extension_flag | All | u(1) | +| else | | | +| avc_3d_extension_flag | All | u(1) | +| if( svc_extension_flag ) { | | | +| nal_unit_header_svc_extension() /* specified in Annex F */ | All | | +| nalUnitHeaderBytes += 3 | | | +| } else if( avc_3d_extension_flag ) { | | | +| nal_unit_header_3davc_extension() /* specified in Annex I */ | | | +| nalUnitHeaderBytes += 2 | | | +| } else { | | | +| nal_unit_header_mvc_extension() /* specified in Annex G */ | All | | +| nalUnitHeaderBytes += 3 | | | +| } | | | +| } | | | +| for( i = nalUnitHeaderBytes; i < NumBytesInNALUnit; i++ ) { | | | +| if( i + 2 < NumBytesInNALUnit && next_bits( 24 ) == 0x000003 ) { | | | +| rbsp_byte [ NumBytesInRBSP++ ] | All | b(8) | +| rbsp_byte [ NumBytesInRBSP++ ] | All | b(8) | +| i += 2 | | | +| emulation_prevention_three_byte /* equal to 0x03 */ | All | f(8) | +| } else | | | +| rbsp_byte [ NumBytesInRBSP++ ] | All | b(8) | +| } | | | +| } | | | + +#### 7.3.2 Raw byte sequence payloads and RBSP trailing bits syntax + +##### 7.3.2.1 Sequence parameter set RBSP syntax + +| seq_parameter_set_rbsp() { | C | Descriptor | +|----------------------------|---|------------| +| seq_parameter_set_data() | 0 | | +| rbsp_trailing_bits() | 0 | | +| } | | | + +### 7.3.2.1.1 Sequence parameter set data syntax + +| seq_parameter_set_data() { | C | Descriptor | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|------------| +| profile_idc | 0 | u(8) | +| constraint_set0_flag | 0 | u(1) | +| constraint_set1_flag | 0 | u(1) | +| constraint_set2_flag | 0 | u(1) | +| constraint_set3_flag | 0 | u(1) | +| constraint_set4_flag | 0 | u(1) | +| constraint_set5_flag | 0 | u(1) | +| reserved_zero_2bits /* equal to 0 */ | 0 | u(2) | +| level_idc | 0 | u(8) | +| seq_parameter_set_id | 0 | ue(v) | +| if( profile_idc == 100 profile_idc == 110
profile_idc == 122 profile_idc == 244 profile_idc == 44
profile_idc == 83 profile_idc == 86 profile_idc == 118
profile_idc == 128 profile_idc == 138 profile_idc == 139
profile_idc == 134 profile_idc == 135 ) { | | | +| chroma_format_idc | 0 | ue(v) | +| if( chroma_format_idc == 3 ) | | | +| separate_colour_plane_flag | 0 | u(1) | +| bit_depth_luma_minus8 | 0 | ue(v) | +| bit_depth_chroma_minus8 | 0 | ue(v) | +| qpprime_y_zero_transform_bypass_flag | 0 | u(1) | +| seq_scaling_matrix_present_flag | 0 | u(1) | +| if( seq_scaling_matrix_present_flag ) | | | +| for( i = 0; i < ( ( chroma_format_idc != 3 ) ? 8 : 12 ); i++ ) { | | | +| seq_scaling_list_present_flag[ i ] | 0 | u(1) | +| if( seq_scaling_list_present_flag[ i ] ) | | | +| if( i < 6 ) | | | +| scaling_list( ScalingList4x4[ i ], 16,
UseDefaultScalingMatrix4x4Flag[ i ] ) | 0 | | +| else | | | +| scaling_list( ScalingList8x8[ i - 6 ], 64,
UseDefaultScalingMatrix8x8Flag[ i - 6 ] ) | 0 | | +| } | | | +| } | | | +| } | | | +| } | | | + +| | | | +|--------------------------------------------------------------|---|-------| +| log2_max_frame_num_minus4 | 0 | ue(v) | +| pic_order_cnt_type | 0 | ue(v) | +| if( pic_order_cnt_type == 0 ) | | | +| log2_max_pic_order_cnt_lsb_minus4 | 0 | ue(v) | +| else if( pic_order_cnt_type == 1 ) { | | | +| delta_pic_order_always_zero_flag | 0 | u(1) | +| offset_for_non_ref_pic | 0 | se(v) | +| offset_for_top_to_bottom_field | 0 | se(v) | +| num_ref_frames_in_pic_order_cnt_cycle | 0 | ue(v) | +| for( i = 0; i < num_ref_frames_in_pic_order_cnt_cycle; i++ ) | | | +| offset_for_ref_frame[ i ] | 0 | se(v) | +| } | | | +| max_num_ref_frames | 0 | ue(v) | +| gaps_in_frame_num_value_allowed_flag | 0 | u(1) | +| pic_width_in_mbs_minus1 | 0 | ue(v) | +| pic_height_in_map_units_minus1 | 0 | ue(v) | +| frame_mbs_only_flag | 0 | u(1) | +| if( !frame_mbs_only_flag ) | | | +| mb_adaptive_frame_field_flag | 0 | u(1) | +| direct_8x8_inference_flag | 0 | u(1) | +| frame_cropping_flag | 0 | u(1) | +| if( frame_cropping_flag ) { | | | +| frame_crop_left_offset | 0 | ue(v) | +| frame_crop_right_offset | 0 | ue(v) | +| frame_crop_top_offset | 0 | ue(v) | +| frame_crop_bottom_offset | 0 | ue(v) | +| } | | | +| vui_parameters_present_flag | 0 | u(1) | +| if( vui_parameters_present_flag ) | | | +| vui_parameters( ) | 0 | | +| } | | | + +#### 7.3.2.1.1.1 Scaling list syntax + +| | | | +|--------------------------------------------------------------------------------------|----------|-------------------| +| scaling_list( scalingList, sizeOfScalingList, useDefaultScalingMatrixFlag ) { | C | Descriptor | +| lastScale = 8 | | | +| nextScale = 8 | | | +| for( j = 0; j < sizeOfScalingList; j++ ) { | | | +| if( nextScale != 0 ) { | | | +| delta_scale | 0 1 | se(v) | +| nextScale = ( lastScale + delta_scale + 256 ) % 256 | | | +| useDefaultScalingMatrixFlag = ( j == 0 && nextScale == 0 ) | | | +| } | | | +| scalingList[ j ] = ( nextScale == 0 ) ? lastScale : nextScale | | | +| lastScale = scalingList[ j ] | | | +| } | | | +| } | | | + +### 7.3.2.1.2 Sequence parameter set extension RBSP syntax + +| seq_parameter_set_extension_rbsp( ) { | C | Descriptor | +|---------------------------------------|----|------------| +| seq_parameter_set_id | 10 | ue(v) | +| aux_format_idc | 10 | ue(v) | +| if( aux_format_idc != 0 ) { | | | +| bit_depth_aux_minus8 | 10 | ue(v) | +| alpha_incr_flag | 10 | u(1) | +| alpha_opaque_value | 10 | u(v) | +| alpha_transparent_value | 10 | u(v) | +| } | | | +| additional_extension_flag | 10 | u(1) | +| rbsp_trailing_bits( ) | 10 | | +| } | | | + +### 7.3.2.1.3 Subset sequence parameter set RBSP syntax + +| subset_seq_parameter_set_rbsp( ) { | C | Descriptor | +|----------------------------------------------------------------------------------|---|------------| +| seq_parameter_set_data( ) | 0 | | +| if( profile_idc == 83 profile_idc == 86 ) { | | | +| seq_parameter_set_svc_extension( ) /* specified in Annex F */ | 0 | | +| svc_vui_parameters_present_flag | 0 | u(1) | +| if( svc_vui_parameters_present_flag == 1 ) | | | +| svc_vui_parameters_extension( ) /* specified in Annex F */ | 0 | | +| } else if( profile_idc == 118 profile_idc == 128
profile_idc == 134 ) { | | | +| bit_equal_to_one /* equal to 1 */ | 0 | f(1) | +| seq_parameter_set_mvc_extension( ) /* specified in Annex G */ | 0 | | +| mvc_vui_parameters_present_flag | 0 | u(1) | +| if( mvc_vui_parameters_present_flag == 1 ) | | | +| mvc_vui_parameters_extension( ) /* specified in Annex G */ | 0 | | +| } else if( profile_idc == 138 profile_idc == 135 ) { | | | +| bit_equal_to_one /* equal to 1 */ | 0 | f(1) | +| seq_parameter_set_mvcd_extension( ) /* specified in Annex H */ | | | +| } else if( profile_idc == 139 ) { | | | +| bit_equal_to_one /* equal to 1 */ | 0 | f(1) | +| seq_parameter_set_mvcd_extension( ) /* specified in Annex H */ | 0 | | +| seq_parameter_set_3dave_extension( ) /* specified in Annex I */ | 0 | | +| } | | | +| additional_extension2_flag | 0 | u(1) | +| if( additional_extension2_flag == 1 ) | | | +| while( more_rbsp_data( ) ) | | | +| additional_extension2_data_flag | 0 | u(1) | +| rbsp_trailing_bits( ) | 0 | | +| } | | | + +### 7.3.2.2 Picture parameter set RBSP syntax + +| pic_parameter_set_rbsp() { | C | Descriptor | +|--------------------------------------------------------------------------------------------------------|---|------------| +| pic_parameter_set_id | 1 | ue(v) | +| seq_parameter_set_id | 1 | ue(v) | +| entropy_coding_mode_flag | 1 | u(1) | +| bottom_field_pic_order_in_frame_present_flag | 1 | u(1) | +| num_slice_groups_minus1 | 1 | ue(v) | +| if( num_slice_groups_minus1 > 0 ) { | | | +| slice_group_map_type | 1 | ue(v) | +| if( slice_group_map_type == 0 ) | | | +| for( iGroup = 0; iGroup <= num_slice_groups_minus1; iGroup++ ) | | | +| run_length_minus1[ iGroup ] | 1 | ue(v) | +| else if( slice_group_map_type == 2 ) | | | +| for( iGroup = 0; iGroup < num_slice_groups_minus1; iGroup++ ) { | | | +| top_left[ iGroup ] | 1 | ue(v) | +| bottom_right[ iGroup ] | 1 | ue(v) | +| } | | | +| else if( slice_group_map_type == 3
slice_group_map_type == 4
slice_group_map_type == 5 ) { | | | +| slice_group_change_direction_flag | 1 | u(1) | +| slice_group_change_rate_minus1 | 1 | ue(v) | +| } else if( slice_group_map_type == 6 ) { | | | +| pic_size_in_map_units_minus1 | 1 | ue(v) | +| for( i = 0; i <= pic_size_in_map_units_minus1; i++ ) | | | +| slice_group_id[ i ] | 1 | u(v) | +| } | | | +| } | | | +| num_ref_idx_l0_default_active_minus1 | 1 | ue(v) | +| num_ref_idx_l1_default_active_minus1 | 1 | ue(v) | +| weighted_pred_flag | 1 | u(1) | +| weighted_bipred_idc | 1 | u(2) | +| pic_init_qp_minus26 | 1 | se(v) | +| pic_init_qs_minus26 | 1 | se(v) | +| chroma_qp_index_offset | 1 | se(v) | +| deblocking_filter_control_present_flag | 1 | u(1) | +| constrained_intra_pred_flag | 1 | u(1) | +| redundant_pic_cnt_present_flag | 1 | u(1) | +| if( more_rbsp_data() ) { | | | +| transform_8x8_mode_flag | 1 | u(1) | +| pic_scaling_matrix_present_flag | 1 | u(1) | +| if( pic_scaling_matrix_present_flag ) | | | +| for( i = 0; i < 6 +
( ( chroma_format_idc != 3 ) ? 2 : 6 ) * transform_8x8_mode_flag;
i++ ) { | | | +| pic_scaling_list_present_flag[ i ] | 1 | u(1) | +| if( pic_scaling_list_present_flag[ i ] ) | | | +| if( i < 6 ) | | | + +| | | | +|-----------------------------------------------------------------------------------------|---|-------| +| scaling_list( ScalingList4x4[ i ], 16,
UseDefaultScalingMatrix4x4Flag[ i ] ) | 1 | | +| else | | | +| scaling_list( ScalingList8x8[ i - 6 ], 64,
UseDefaultScalingMatrix8x8Flag[ i - 6 ] ) | 1 | | +| } | | | +| second_chroma_qp_index_offset | 1 | se(v) | +| } | | | +| rbsp_trailing_bits( ) | 1 | | +| } | | | + +### 7.3.2.3 Supplemental enhancement information RBSP syntax + +| | | | +|----------------------------|----------|-------------------| +| sei_rbsp( ) { | C | Descriptor | +| do | | | +| sei_message( ) | 5 | | +| while( more_rbsp_data( ) ) | | | +| rbsp_trailing_bits( ) | 5 | | +| } | | | + +#### 7.3.2.3.1 Supplemental enhancement information message syntax + +| | | | +|-----------------------------------------|----------|-------------------| +| sei_message( ) { | C | Descriptor | +| payloadType = 0 | | | +| while( next_bits( 8 ) == 0xFF ) { | | | +| ff_byte /* equal to 0xFF */ | 5 | f(8) | +| payloadType += 255 | | | +| } | | | +| last_payload_type_byte | 5 | u(8) | +| payloadType += last_payload_type_byte | | | +| payloadSize = 0 | | | +| while( next_bits( 8 ) == 0xFF ) { | | | +| ff_byte /* equal to 0xFF */ | 5 | f(8) | +| payloadSize += 255 | | | +| } | | | +| last_payload_size_byte | 5 | u(8) | +| payloadSize += last_payload_size_byte | | | +| sei_payload( payloadType, payloadSize ) | 5 | | +| } | | | + +### 7.3.2.4 Access unit delimiter RBSP syntax + +| | | | +|---------------------------------|----------|-------------------| +| access_unit_delimiter_rbsp( ) { | C | Descriptor | +| primary_pic_type | 6 | u(3) | +| rbsp_trailing_bits( ) | 6 | | +| } | | | + +### 7.3.2.5 End of sequence RBSP syntax + +| | | | +|---------------------|---|------------| +| end_of_seq_rbsp() { | C | Descriptor | +| } | | | + +### 7.3.2.6 End of stream RBSP syntax + +| | | | +|------------------------|---|------------| +| end_of_stream_rbsp() { | C | Descriptor | +| } | | | + +### 7.3.2.7 Filler data RBSP syntax + +| | | | +|------------------------------------|---|------------| +| filler_data_rbsp() { | C | Descriptor | +| while( next_bits( 8 ) == 0xFF ) | | | +| ff_byte /* equal to 0xFF */ | 9 | f(8) | +| rbsp_trailing_bits() | 9 | | +| } | | | + +### 7.3.2.8 Slice layer without partitioning RBSP syntax + +| | | | +|----------------------------------------------------------|-----------|------------| +| slice_layer_without_partitioning_rbsp() { | C | Descriptor | +| slice_header() | 2 | | +| slice_data() /* all categories of slice_data() syntax */ | 2 3 4 | | +| rbsp_slice_trailing_bits() | 2 | | +| } | | | + +### 7.3.2.9 Slice data partition RBSP syntax + +#### 7.3.2.9.1 Slice data partition A RBSP syntax + +| | | | +|-----------------------------------------------------------------|-----|------------| +| slice_data_partition_a_layer_rbsp() { | C | Descriptor | +| slice_header() | 2 | | +| slice_id | All | ue(v) | +| slice_data() /* only category 2 parts of slice_data() syntax */ | 2 | | +| rbsp_slice_trailing_bits() | 2 | | +| } | | | + +### 7.3.2.9.2 Slice data partition B RBSP syntax + +| slice_data_partition_b_layer_rbsp() { | C | Descriptor | +|-----------------------------------------------------------------|-----|------------| +| slice_id | All | ue(v) | +| if( separate_colour_plane_flag == 1 ) | | | +| colour_plane_id | All | u(2) | +| if( redundant_pic_cnt_present_flag ) | | | +| redundant_pic_cnt | All | ue(v) | +| slice_data() /* only category 3 parts of slice_data() syntax */ | 3 | | +| rbps_slice_trailing_bits() | 3 | | +| } | | | + +### 7.3.2.9.3 Slice data partition C RBSP syntax + +| slice_data_partition_c_layer_rbsp() { | C | Descriptor | +|-----------------------------------------------------------------|-----|------------| +| slice_id | All | ue(v) | +| if( separate_colour_plane_flag == 1 ) | | | +| colour_plane_id | All | u(2) | +| if( redundant_pic_cnt_present_flag ) | | | +| redundant_pic_cnt | All | ue(v) | +| slice_data() /* only category 4 parts of slice_data() syntax */ | 4 | | +| rbps_slice_trailing_bits() | 4 | | +| } | | | + +### 7.3.2.10 RBSP slice trailing bits syntax + +| rbps_slice_trailing_bits() { | C | Descriptor | +|----------------------------------------------|-----|------------| +| rbps_trailing_bits() | All | | +| if( entropy_coding_mode_flag ) | | | +| while( more_rbps_trailing_data() ) | | | +| cabac_zero_word /* equal to 0x0000 */ | All | f(16) | +| } | | | + +### 7.3.2.11 RBSP trailing bits syntax + +| rbps_trailing_bits() { | C | Descriptor | +|-------------------------------------------------|-----|------------| +| rbps_stop_one_bit /* equal to 1 */ | All | f(1) | +| while( !byte_aligned() ) | | | +| rbps_alignment_zero_bit /* equal to 0 */ | All | f(1) | +| } | | | + +### 7.3.2.12 Prefix NAL unit RBSP syntax + +| prefix_nal_unit_rbsp() { | C | Descriptor | +|---------------------------------------------------|---|------------| +| if( svc_extension_flag ) | | | +| prefix_nal_unit_svc( ) /* specified in Annex F */ | 2 | | +| } | | | + +### 7.3.2.13 Slice layer extension RBSP syntax + +| slice_layer_extension_rbsp() { | C | Descriptor | +|------------------------------------------------------------------|-----------|------------| +| if( svc_extension_flag ) { | | | +| slice_header_in_scalable_extension( ) /* specified in Annex F */ | 2 | | +| if( !slice_skip_flag ) | | | +| slice_data_in_scalable_extension( ) /* specified in Annex F */ | 2 3 4 | | +| } else if( avc_3d_extension_flag ) { | | | +| slice_header_in_3davc_extension( ) /* specified in Annex J */ | 2 | | +| slice_data_in_3davc_extension( ) /* specified in Annex J */ | 2 3 4 | | +| } else { | | | +| slice_header( ) | 2 | | +| slice_data( ) | 2 3 4 | | +| } | | | +| rbsp_slice_trailing_bits( ) | 2 | | +| } | | | + +### 7.3.3 Slice header syntax + +| slice_header( ) { | C | Descriptor | +|-----------------------------------------------------------------------|---|------------| +| first_mb_in_slice | 2 | ue(v) | +| slice_type | 2 | ue(v) | +| pic_parameter_set_id | 2 | ue(v) | +| if( separate_colour_plane_flag == 1 ) | | | +| colour_plane_id | 2 | u(2) | +| frame_num | 2 | u(v) | +| if( !frame_mbs_only_flag ) { | | | +| field_pic_flag | 2 | u(1) | +| if( field_pic_flag ) | | | +| bottom_field_flag | 2 | u(1) | +| } | | | +| if( IdrPicFlag ) | | | +| idr_pic_id | 2 | ue(v) | +| if( pic_order_cnt_type == 0 ) { | | | +| pic_order_cnt_lsb | 2 | u(v) | +| if( bottom_field_pic_order_in_frame_present_flag && !field_pic_flag ) | | | +| delta_pic_order_cnt_bottom | 2 | se(v) | +| } | | | +| if( pic_order_cnt_type == 1 && !delta_pic_order_always_zero_flag ) { | | | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------|---|-------| +| delta_pic_order_cnt[ 0 ] | 2 | se(v) | +| if( bottom_field_pic_order_in_frame_present_flag && !field_pic_flag ) | | | +| delta_pic_order_cnt[ 1 ] | 2 | se(v) | +| } | | | +| if( redundant_pic_cnt_present_flag ) | | | +| redundant_pic_cnt | 2 | ue(v) | +| if( slice_type == B ) | | | +| direct_spatial_mv_pred_flag | 2 | u(1) | +| if( slice_type == P slice_type == SP slice_type == B ) { | | | +| num_ref_idx_active_override_flag | 2 | u(1) | +| if( num_ref_idx_active_override_flag ) { | | | +| num_ref_idx_l0_active_minus1 | 2 | ue(v) | +| if( slice_type == B ) | | | +| num_ref_idx_l1_active_minus1 | 2 | ue(v) | +| } | | | +| } | | | +| if( nal_unit_type == 20 nal_unit_type == 21 ) | | | +| ref_pic_list_mvc_modification( ) /* specified in Annex G */ | 2 | | +| else | | | +| ref_pic_list_modification( ) | 2 | | +| if( ( weighted_pred_flag && ( slice_type == P slice_type == SP ) )
( weighted_bipred_idc == 1 && slice_type == B ) ) | | | +| pred_weight_table( ) | 2 | | +| if( nal_ref_idc != 0 ) | | | +| dec_ref_pic_marking( ) | 2 | | +| if( entropy_coding_mode_flag && slice_type != I && slice_type != SI ) | | | +| cabac_init_idc | 2 | ue(v) | +| slice_qp_delta | 2 | se(v) | +| if( slice_type == SP slice_type == SI ) { | | | +| if( slice_type == SP ) | | | +| sp_for_switch_flag | 2 | u(1) | +| slice_qs_delta | 2 | se(v) | +| } | | | +| if( deblocking_filter_control_present_flag ) { | | | +| disable_deblocking_filter_idc | 2 | ue(v) | +| if( disable_deblocking_filter_idc != 1 ) { | | | +| slice_alpha_c0_offset_div2 | 2 | se(v) | +| slice_beta_offset_div2 | 2 | se(v) | +| } | | | +| } | | | +| if( num_slice_groups_minus1 > 0 &&
slice_group_map_type >= 3 && slice_group_map_type <= 5) | | | +| slice_group_change_cycle | 2 | u(v) | +| } | | | + +### 7.3.3.1 Reference picture list modification syntax + +| ref_pic_list_modification( ) { | C | Descriptor | +|---------------------------------------------------------------------------------|---|------------| +| if( slice_type % 5 != 2 && slice_type % 5 != 4 ) { | | | +| ref_pic_list_modification_flag_l0 | 2 | u(1) | +| if( ref_pic_list_modification_flag_l0 ) | | | +| do { | | | +| modification_of_pic_nums_idc | 2 | ue(v) | +| if( modification_of_pic_nums_idc == 0
modification_of_pic_nums_idc == 1 ) | | | +| abs_diff_pic_num_minus1 | 2 | ue(v) | +| else if( modification_of_pic_nums_idc == 2 ) | | | +| long_term_pic_num | 2 | ue(v) | +| } while( modification_of_pic_nums_idc != 3 ) | | | +| } | | | +| if( slice_type % 5 == 1 ) { | | | +| ref_pic_list_modification_flag_l1 | 2 | u(1) | +| if( ref_pic_list_modification_flag_l1 ) | | | +| do { | | | +| modification_of_pic_nums_idc | 2 | ue(v) | +| if( modification_of_pic_nums_idc == 0
modification_of_pic_nums_idc == 1 ) | | | +| abs_diff_pic_num_minus1 | 2 | ue(v) | +| else if( modification_of_pic_nums_idc == 2 ) | | | +| long_term_pic_num | 2 | ue(v) | +| } while( modification_of_pic_nums_idc != 3 ) | | | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | + +### 7.3.3.2 Prediction weight table syntax + +| pred_weight_table() { | C | Descriptor | +|--------------------------------------------------------|---|------------| +| luma_log2_weight_denom | 2 | ue(v) | +| if( ChromaArrayType != 0 ) | | | +| chroma_log2_weight_denom | 2 | ue(v) | +| for( i = 0; i <= num_ref_idx_l0_active_minus1; i++ ) { | | | +| luma_weight_l0_flag | 2 | u(1) | +| if( luma_weight_l0_flag ) { | | | +| luma_weight_l0[ i ] | 2 | se(v) | +| luma_offset_l0[ i ] | 2 | se(v) | +| } | | | +| if( ChromaArrayType != 0 ) { | | | +| chroma_weight_l0_flag | 2 | u(1) | +| if( chroma_weight_l0_flag ) | | | +| for( j = 0; j < 2; j++ ) { | | | +| chroma_weight_l0[ i ][ j ] | 2 | se(v) | +| chroma_offset_l0[ i ][ j ] | 2 | se(v) | +| } | | | +| } | | | +| } | | | +| if( slice_type % 5 == 1 ) | | | +| for( i = 0; i <= num_ref_idx_l1_active_minus1; i++ ) { | | | +| luma_weight_l1_flag | 2 | u(1) | +| if( luma_weight_l1_flag ) { | | | +| luma_weight_l1[ i ] | 2 | se(v) | +| luma_offset_l1[ i ] | 2 | se(v) | +| } | | | +| if( ChromaArrayType != 0 ) { | | | +| chroma_weight_l1_flag | 2 | u(1) | +| if( chroma_weight_l1_flag ) | | | +| for( j = 0; j < 2; j++ ) { | | | +| chroma_weight_l1[ i ][ j ] | 2 | se(v) | +| chroma_offset_l1[ i ][ j ] | 2 | se(v) | +| } | | | +| } | | | +| } | | | +| } | | | + +### 7.3.3.3 Decoded reference picture marking syntax + +| dec_ref_pic_marking( ) { | C | Descriptor | +|-----------------------------------------------------------------------------------------------|-------|------------| +| if( IdrPicFlag ) { | | | +| no_output_of_prior_pics_flag | 2 5 | u(1) | +| long_term_reference_flag | 2 5 | u(1) | +| } else { | | | +| adaptive_ref_pic_marking_mode_flag | 2 5 | u(1) | +| if( adaptive_ref_pic_marking_mode_flag ) | | | +| do { | | | +| memory_management_control_operation | 2 5 | ue(v) | +| if( memory_management_control_operation == 1
memory_management_control_operation == 3 ) | | | +| difference_of_pic_nums_minus1 | 2 5 | ue(v) | +| if( memory_management_control_operation == 2 ) | | | +| long_term_pic_num | 2 5 | ue(v) | +| if( memory_management_control_operation == 3
memory_management_control_operation == 6 ) | | | +| long_term_frame_idx | 2 5 | ue(v) | +| if( memory_management_control_operation == 4 ) | | | +| max_long_term_frame_idx_plus1 | 2 5 | ue(v) | +| } while( memory_management_control_operation != 0 ) | | | +| } | | | +| } | | | + +### 7.3.4 Slice data syntax + +| slice_data() { | C | Descriptor | +|------------------------------------------------------------------------------------------------|-----------|--------------| +| if( entropy_coding_mode_flag ) | | | +| while( !byte_aligned() ) | | | +| cabac_alignment_one_bit | 2 | f(1) | +| CurrMbAddr = first_mb_in_slice * ( 1 + MbaffFrameFlag ) | | | +| moreDataFlag = 1 | | | +| prevMbSkipped = 0 | | | +| do { | | | +| if( slice_type != I && slice_type != SI ) | | | +| if( !entropy_coding_mode_flag ) { | | | +| mb_skip_run | 2 | ue(v) | +| prevMbSkipped = ( mb_skip_run > 0 ) | | | +| for( i=0; i 0 ) | | | +| moreDataFlag = more_rbsp_data( ) | | | +| } else { | | | +| mb_skip_flag | 2 | ae(v) | +| moreDataFlag = !mb_skip_flag | | | +| } | | | +| if( moreDataFlag ) { | | | +| if( MbaffFrameFlag && ( CurrMbAddr % 2 == 0
( CurrMbAddr % 2 == 1 && prevMbSkipped ) ) ) | | | +| mb_field_decoding_flag | 2 | u(1) ae(v) | +| macroblock_layer( ) | 2 3 4 | | +| } | | | +| if( !entropy_coding_mode_flag ) | | | +| moreDataFlag = more_rbsp_data( ) | | | +| else { | | | +| if( slice_type != I && slice_type != SI ) | | | +| prevMbSkipped = mb_skip_flag | | | +| if( MbaffFrameFlag && CurrMbAddr % 2 == 0 ) | | | +| moreDataFlag = 1 | | | +| else { | | | +| end_of_slice_flag | 2 | ae(v) | +| moreDataFlag = !end_of_slice_flag | | | +| } | | | +| } | | | +| CurrMbAddr = NextMbAddress( CurrMbAddr ) | | | +| } while( moreDataFlag ) | | | +| } | | | + +### 7.3.5 Macroblock layer syntax + +| macroblock_layer() { | C | Descriptor | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---------------| +| mb_type | 2 | ue(v) ae(v) | +| if( mb_type == I_PCM ) { | | | +| while( !byte_aligned() ) | | | +| pcm_alignment_zero_bit | 3 | f(1) | +| for( i = 0; i < 256; i++ ) | | | +| pcm_sample_luma[ i ] | 3 | u(v) | +| for( i = 0; i < 2 * MbWidthC * MbHeightC; i++ ) | | | +| pcm_sample_chroma[ i ] | 3 | u(v) | +| } else { | | | +| noSubMbPartSizeLessThan8x8Flag = 1 | | | +| if( mb_type != I_NxN &&
MbPartPredMode( mb_type, 0 ) != Intra_16x16 &&
NumMbPart( mb_type ) == 4 ) { | | | +| sub_mb_pred( mb_type ) | 2 | | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( sub_mb_type[ mbPartIdx ] != B_Direct_8x8 ) { | | | +| if( NumSubMbPart( sub_mb_type[ mbPartIdx ] ) > 1 ) | | | +| noSubMbPartSizeLessThan8x8Flag = 0 | | | +| } else if( !direct_8x8_inference_flag ) | | | +| noSubMbPartSizeLessThan8x8Flag = 0 | | | +| } else { | | | +| if( transform_8x8_mode_flag && mb_type == I_NxN ) | | | +| transform_size_8x8_flag | 2 | u(1) ae(v) | +| mb_pred( mb_type ) | 2 | | +| } | | | +| if( MbPartPredMode( mb_type, 0 ) != Intra_16x16 ) { | | | +| coded_block_pattern | 2 | me(v) ae(v) | +| if( CodedBlockPatternLuma > 0 &&
transform_8x8_mode_flag && mb_type != I_NxN &&
noSubMbPartSizeLessThan8x8Flag &&
( mb_type != B_Direct_16x16 direct_8x8_inference_flag ) ) | | | +| transform_size_8x8_flag | 2 | u(1) ae(v) | +| } | | | +| if( CodedBlockPatternLuma > 0 CodedBlockPatternChroma > 0
MbPartPredMode( mb_type, 0 ) == Intra_16x16 ) { | | | +| mb_qp_delta | 2 | se(v) ae(v) | +| residual( 0, 15 ) | 3 4 | | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | + +### 7.3.5.1 Macroblock prediction syntax + +| mb_pred( mb_type ) { | C | Descriptor | +|-----------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| if( MbPartPredMode( mb_type, 0 ) == Intra_4x4
MbPartPredMode( mb_type, 0 ) == Intra_8x8
MbPartPredMode( mb_type, 0 ) == Intra_16x16 ) { | | | +| if( MbPartPredMode( mb_type, 0 ) == Intra_4x4 ) | | | +| for( luma4x4BlkIdx=0; luma4x4BlkIdx<16; luma4x4BlkIdx++ ) { | | | +| prev_intra4x4_pred_mode_flag [ luma4x4BlkIdx ] | 2 | u(1) ae(v) | +| if( !prev_intra4x4_pred_mode_flag[ luma4x4BlkIdx ] ) | | | +| rem_intra4x4_pred_mode [ luma4x4BlkIdx ] | 2 | u(3) ae(v) | +| } | | | +| if( MbPartPredMode( mb_type, 0 ) == Intra_8x8 ) | | | +| for( luma8x8BlkIdx=0; luma8x8BlkIdx<4; luma8x8BlkIdx++ ) { | | | +| prev_intra8x8_pred_mode_flag [ luma8x8BlkIdx ] | 2 | u(1) ae(v) | +| if( !prev_intra8x8_pred_mode_flag[ luma8x8BlkIdx ] ) | | | +| rem_intra8x8_pred_mode [ luma8x8BlkIdx ] | 2 | u(3) ae(v) | +| } | | | +| if( ChromaArrayType == 1 ChromaArrayType == 2 ) | | | +| intra_chroma_pred_mode | 2 | ue(v) ae(v) | +| } else if( MbPartPredMode( mb_type, 0 ) != Direct ) { | | | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( ( num_ref_idx_l0_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
MbPartPredMode( mb_type, mbPartIdx ) != Pred_L1 ) | | | +| ref_idx_l0 [ mbPartIdx ] | 2 | te(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( ( num_ref_idx_l1_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
MbPartPredMode( mb_type, mbPartIdx ) != Pred_L0 ) | | | +| ref_idx_l1 [ mbPartIdx ] | 2 | te(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( MbPartPredMode( mb_type, mbPartIdx ) != Pred_L1 ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_l0 [ mbPartIdx ][ 0 ][ compIdx ] | 2 | se(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( MbPartPredMode( mb_type, mbPartIdx ) != Pred_L0 ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_l1 [ mbPartIdx ][ 0 ][ compIdx ] | 2 | se(v) ae(v) | +| } | | | +| } | | | +| } | | | + +### 7.3.5.2 Sub-macroblock prediction syntax + +| sub_mb_pred( mb_type ) { | C | Descriptor | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| sub_mb_type[ mbPartIdx ] | 2 | ue(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( ( num_ref_idx_10_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
mb_type != P_8x8ref0 &&
sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L1 ) | | | +| ref_idx_10[ mbPartIdx ] | 2 | te(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( ( num_ref_idx_11_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L0 ) | | | +| ref_idx_11[ mbPartIdx ] | 2 | te(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L1 ) | | | +| for( subMbPartIdx = 0;
subMbPartIdx < NumSubMbPart( sub_mb_type[ mbPartIdx ] );
subMbPartIdx++ ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_10[ mbPartIdx ][ subMbPartIdx ][ compIdx ] | 2 | se(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L0 ) | | | +| for( subMbPartIdx = 0;
subMbPartIdx < NumSubMbPart( sub_mb_type[ mbPartIdx ] );
subMbPartIdx++ ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_11[ mbPartIdx ][ subMbPartIdx ][ compIdx ] | 2 | se(v) ae(v) | +| } | | | + +### 7.3.5.3 Residual data syntax + +| residual( startIdx, endIdx ) { | C | Descriptor | +|--------------------------------------------------------------------------------------------------------|-------|------------| +| if( !entropy_coding_mode_flag ) | | | +| residual_block = residual_block_cavlc | | | +| else | | | +| residual_block = residual_block_cabac | | | +| residual_luma( i16x16DClevel, i16x16AClevel, level4x4, level8x8,
startIdx, endIdx ) | 3 4 | | +| Intra16x16DCLevel = i16x16DClevel | | | +| Intra16x16ACLevel = i16x16AClevel | | | +| LumaLevel4x4 = level4x4 | | | +| LumaLevel8x8 = level8x8 | | | +| if( ChromaArrayType == 1 ChromaArrayType == 2 ) { | | | +| NumC8x8 = 4 / ( SubWidthC * SubHeightC ) | | | +| for( iCbCr = 0; iCbCr < 2; iCbCr++ ) | | | +| if( ( CodedBlockPatternChroma & 3 ) && startIdx == 0 )
/* chroma DC residual present */ | | | +| residual_block( ChromaDCLevel[ iCbCr ], 0, 4 * NumC8x8 – 1,
4 * NumC8x8 ) | 3 4 | | +| else | | | +| for( i = 0; i < 4 * NumC8x8; i++ ) | | | +| ChromaDCLevel[ iCbCr ][ i ] = 0 | | | +| for( iCbCr = 0; iCbCr < 2; iCbCr++ ) | | | +| for( i8x8 = 0; i8x8 < NumC8x8; i8x8++ ) | | | +| for( i4x4 = 0; i4x4 < 4; i4x4++ ) | | | +| if( CodedBlockPatternChroma & 2 )
/* chroma AC residual present */ | | | +| residual_block( ChromaACLevel[ iCbCr ][ i8x8 * 4 + i4x4 ],
Max( 0, startIdx – 1 ), endIdx – 1, 15 ) | 3 4 | | +| else | | | +| for( i = 0; i < 15; i++ ) | | | +| ChromaACLevel[ iCbCr ][ i8x8 * 4 + i4x4 ][ i ] = 0 | | | +| } else if( ChromaArrayType == 3 ) { | | | +| residual_luma( i16x16DClevel, i16x16AClevel, level4x4, level8x8,
startIdx, endIdx ) | 3 4 | | +| CbIntra16x16DCLevel = i16x16DClevel | | | +| CbIntra16x16ACLevel = i16x16AClevel | | | +| CbLevel4x4 = level4x4 | | | +| CbLevel8x8 = level8x8 | | | +| residual_luma( i16x16DClevel, i16x16AClevel, level4x4, level8x8,
startIdx, endIdx ) | 3 4 | | +| CrIntra16x16DCLevel = i16x16DClevel | | | +| CrIntra16x16ACLevel = i16x16AClevel | | | +| CrLevel4x4 = level4x4 | | | +| CrLevel8x8 = level8x8 | | | +| } | | | +| } | | | + +### 7.3.5.3.1 Residual luma syntax + +| residual_luma( i16x16DClevel, i16x16AClevel, level4x4, level8x8, startIdx, endIdx ) { | C | Descriptor | +|-----------------------------------------------------------------------------------------------|-------|------------| +| if( startIdx == 0 && MbPartPredMode( mb_type, 0 ) == Intra_16x16 ) | | | +| residual_block( i16x16DClevel, 0, 15, 16 ) | 3 | | +| for( i8x8 = 0; i8x8 < 4; i8x8++ ) | | | +| if( !transform_size_8x8_flag !entropy_coding_mode_flag ) | | | +| for( i4x4 = 0; i4x4 < 4; i4x4++ ) { | | | +| if( CodedBlockPatternLuma & ( 1 << i8x8 ) ) | | | +| if( MbPartPredMode( mb_type, 0 ) == Intra_16x16 ) | | | +| residual_block( i16x16AClevel[ i8x8 * 4 + i4x4 ],
Max( 0, startIdx − 1 ), endIdx − 1, 15 ) | 3 | | +| else | | | +| residual_block( level4x4[ i8x8 * 4 + i4x4 ],
startIdx, endIdx, 16 ) | 3 4 | | +| else if( MbPartPredMode( mb_type, 0 ) == Intra_16x16 ) | | | +| for( i = 0; i < 15; i++ ) | | | +| i16x16AClevel[ i8x8 * 4 + i4x4 ][ i ] = 0 | | | +| else | | | +| for( i = 0; i < 16; i++ ) | | | +| level4x4[ i8x8 * 4 + i4x4 ][ i ] = 0 | | | +| if( !entropy_coding_mode_flag && transform_size_8x8_flag ) | | | +| for( i = 0; i < 16; i++ ) | | | +| level8x8[ i8x8 ][ 4 * i + i4x4 ] = level4x4[ i8x8 * 4 + i4x4 ][ i ] | | | +| } | | | +| else if( CodedBlockPatternLuma & ( 1 << i8x8 ) ) | | | +| residual_block( level8x8[ i8x8 ], 4 * startIdx, 4 * endIdx + 3, 64 ) | 3 4 | | +| else | | | +| for( i = 0; i < 64; i++ ) | | | +| level8x8[ i8x8 ][ i ] = 0 | | | +| } | | | + +### 7.3.5.3.2 Residual block CAVLC syntax + +| residual_block_cavlc( coeffLevel, startIdx, endIdx, maxNumCoeff ) { | C | Descriptor | +|-------------------------------------------------------------------------|-------|------------| +| for( i = 0; i < maxNumCoeff; i++ ) | | | +| coeffLevel[ i ] = 0 | | | +| coeff_token | 3 4 | ce(v) | +| if( TotalCoeff( coeff_token ) > 0 ) { | | | +| if( TotalCoeff( coeff_token ) > 10 && TrailingOnes( coeff_token ) < 3 ) | | | +| suffixLength = 1 | | | +| else | | | +| suffixLength = 0 | | | +| for( i = 0; i < TotalCoeff( coeff_token ); i++ ) | | | +| if( i < TrailingOnes( coeff_token ) ) { | | | +| trailing_ones_sign_flag | 3 4 | u(1) | +| levelVal[ i ] = 1 − 2 * trailing_ones_sign_flag | | | + +| | | | +|-----------------------------------------------------------------------------------|-------|-------| +| } else { | | | +| level_prefix | 3 4 | ce(v) | +| levelCode = ( Min( 15, level_prefix ) << suffixLength ) | | | +| if( suffixLength > 0 level_prefix >= 14 ) { | | | +| level_suffix | 3 4 | u(v) | +| levelCode += level_suffix | | | +| } | | | +| if( level_prefix >= 15 && suffixLength == 0 ) | | | +| levelCode += 15 | | | +| if( level_prefix >= 16 ) | | | +| levelCode += ( 1 << ( level_prefix - 3 ) ) - 4096 | | | +| if( i == TrailingOnes( coeff_token ) &&
TrailingOnes( coeff_token ) < 3 ) | | | +| levelCode += 2 | | | +| if( levelCode % 2 == 0 ) | | | +| levelVal[ i ] = ( levelCode + 2 ) >> 1 | | | +| else | | | +| levelVal[ i ] = ( -levelCode - 1 ) >> 1 | | | +| if( suffixLength == 0 ) | | | +| suffixLength = 1 | | | +| if( Abs( levelVal[ i ] ) > ( 3 << ( suffixLength - 1 ) ) &&
suffixLength < 6 ) | | | +| suffixLength++ | | | +| } | | | +| if( TotalCoeff( coeff_token ) < endIdx - startIdx + 1 ) { | | | +| total_zeros | 3 4 | ce(v) | +| zerosLeft = total_zeros | | | +| } else | | | +| zerosLeft = 0 | | | +| for( i = 0; i < TotalCoeff( coeff_token ) - 1; i++ ) { | | | +| if( zerosLeft > 0 ) { | | | +| run_before | 3 4 | ce(v) | +| runVal[ i ] = run_before | | | +| } else | | | +| runVal[ i ] = 0 | | | +| zerosLeft = zerosLeft - runVal[ i ] | | | +| } | | | +| runVal[ TotalCoeff( coeff_token ) - 1 ] = zerosLeft | | | +| coeffNum = -1 | | | +| for( i = TotalCoeff( coeff_token ) - 1; i >= 0; i-- ) { | | | +| coeffNum += runVal[ i ] + 1 | | | +| coeffLevel[ startIdx + coeffNum ] = levelVal[ i ] | | | +| } | | | +| } | | | +| } | | | + +### 7.3.5.3.3 Residual block CABAC syntax + +| residual_block_cabac( coeffLevel, startIdx, endIdx, maxNumCoeff ) { | C | Descriptor | +|---------------------------------------------------------------------------------------------------------------------------------|-------|------------| +| if( maxNumCoeff != 64 ChromaArrayType == 3 ) | | | +| coded_block_flag | 3 4 | ae(v) | +| for( i = 0; i < maxNumCoeff; i++ ) | | | +| coeffLevel[ i ] = 0 | | | +| if( coded_block_flag ) { | | | +| numCoeff = endIdx + 1 | | | +| i = startIdx | | | +| while( i < numCoeff − 1 ) { | | | +| significant_coeff_flag[ i ] | 3 4 | ae(v) | +| if( significant_coeff_flag[ i ] ) { | | | +| last_significant_coeff_flag[ i ] | 3 4 | ae(v) | +| if( last_significant_coeff_flag[ i ] ) | | | +| numCoeff = i + 1 | | | +| } | | | +| i++ | | | +| } | | | +| coeff_abs_level_minus1[ numCoeff − 1 ] | 3 4 | ae(v) | +| coeff_sign_flag[ numCoeff − 1 ] | 3 4 | ae(v) | +| coeffLevel[ numCoeff − 1 ] =
( coeff_abs_level_minus1[ numCoeff − 1 ] + 1 ) *
( 1 − 2 * coeff_sign_flag[ numCoeff − 1 ] ) | | | +| for( i = numCoeff − 2; i >= startIdx; i−− ) | | | +| if( significant_coeff_flag[ i ] ) { | | | +| coeff_abs_level_minus1[ i ] | 3 4 | ae(v) | +| coeff_sign_flag[ i ] | 3 4 | ae(v) | +| coeffLevel[ i ] = ( coeff_abs_level_minus1[ i ] + 1 ) *
( 1 − 2 * coeff_sign_flag[ i ] ) | | | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | + +## 7.4 Semantics + +Semantics associated with the syntax structures and with the syntax elements within these structures are specified in this clause. When the semantics of a syntax element are specified using a table or a set of tables, any values that are not specified in the table(s) shall not be present in the bitstream unless otherwise specified in this Recommendation | International Standard. + +### 7.4.1 NAL unit semantics + +NOTE 1 – The VCL is specified to efficiently represent the content of the video data. The NAL is specified to format that data and provide header information in a manner appropriate for conveyance on a variety of communication channels or storage media. All data are contained in NAL units, each of which contains an integer number of bytes. A NAL unit specifies a generic format for use in both packet-oriented and bitstream systems. The format of NAL units for both packet-oriented transport and byte stream is identical except that each NAL unit can be preceded by a start code prefix and extra padding bytes in the byte stream format. + +NumBytesInNALUnit specifies the size of the NAL unit in bytes. This value is required for decoding of the NAL unit. Some form of demarcation of NAL unit boundaries is necessary to enable inference of NumBytesInNALUnit. One such demarcation method is specified in Annex B for the byte stream format. Other methods of demarcation may be specified outside of this Recommendation | International Standard. + +**forbidden\_zero\_bit** shall be equal to 0. + +**nal\_ref\_idc** not equal to 0 specifies that the content of the NAL unit contains a sequence parameter set, a sequence parameter set extension, a subset sequence parameter set, a picture parameter set, a slice of a reference picture, a slice data partition of a reference picture, or a prefix NAL unit preceding a slice of a reference picture. + +For coded video sequences conforming to one or more of the profiles specified in Annex A that are decoded using the decoding process specified in clauses 2 to 9, nal\_ref\_idc equal to 0 for a NAL unit containing a slice or slice data partition indicates that the slice or slice data partition is part of a non-reference picture. + +nal\_ref\_idc shall not be equal to 0 for sequence parameter set or sequence parameter set extension or subset sequence parameter set or picture parameter set NAL units. When nal\_ref\_idc is equal to 0 for one NAL unit with nal\_unit\_type in the range of 1 to 4, inclusive, of a particular picture, it shall be equal to 0 for all NAL units with nal\_unit\_type in the range of 1 to 4, inclusive, of the picture. + +nal\_ref\_idc shall not be equal to 0 for NAL units with nal\_unit\_type equal to 5. + +nal\_ref\_idc shall be equal to 0 for all NAL units having nal\_unit\_type equal to 6, 9, 10, 11, or 12. + +**nal\_unit\_type** specifies the type of RBSP data structure contained in the NAL unit as specified in Table 7-1. + +The column marked "C" in Table 7-1 lists the categories of the syntax elements that may be present in the NAL unit. In addition, syntax elements with syntax category "All" may be present, as determined by the syntax and semantics of the RBSP data structure. The presence or absence of any syntax elements of a particular listed category is determined from the syntax and semantics of the associated RBSP data structure. nal\_unit\_type shall not be equal to 3 or 4 unless at least one syntax element is present in the RBSP data structure having a syntax element category value equal to the value of nal\_unit\_type and not categorized as "All". + +For coded video sequences conforming to one or more of the profiles specified in Annex A that are decoded using the decoding process specified in clauses 2-9, VCL and non-VCL NAL units are specified in Table 7-1 in the column labelled "Annex A NAL unit type class". For coded video sequences conforming to one or more of the profiles specified in Annex F that are decoded using the decoding process specified in Annex F and for coded video sequences conforming to one or more of the profiles specified in Annex G that are decoded using the decoding process specified in Annex G, VCL and non-VCL NAL units are specified in Table 7-1 in the column labelled "Annex F and Annex G NAL unit type class". The entry "suffix dependent" for nal\_unit\_type equal to 14 is specified as follows: + +- If the NAL unit directly following in decoding order a NAL unit with nal\_unit\_type equal to 14 is a NAL unit with nal\_unit\_type equal to 1 or 5, the NAL unit with nal\_unit\_type equal to 14 is a VCL NAL unit. +- Otherwise (the NAL unit directly following in decoding order a NAL unit with nal\_unit\_type equal to 14 is a NAL unit with nal\_unit\_type not equal to 1 or 5), the NAL unit with nal\_unit\_type equal to 14 is a non-VCL NAL unit. Decoders shall ignore (remove from the bitstream and discard) the NAL unit with nal\_unit\_type equal to 14 and the NAL unit directly following (in decoding order) the NAL unit with nal\_unit\_type equal to 14. + +**Table 7-1 – NAL unit type codes, syntax element categories, and NAL unit type classes** + +| nal_unit_type | Content of NAL unit and RBSP
syntax structure | C | Annex A | Annex F
and
Annex G | Annex H
and
Annex I | +|---------------|----------------------------------------------------------------------------------------------------------------------------|---------|------------------------|---------------------------|---------------------------| +| | | | NAL unit
type class | NAL unit
type class | NAL unit
type class | +| 0 | Unspecified | | non-VCL | non-VCL | non-VCL | +| 1 | Coded slice of a non-IDR picture
slice_layer_without_partitioning_rbsp( ) | 2, 3, 4 | VCL | VCL | VCL | +| 2 | Coded slice data partition A
slice_data_partition_a_layer_rbsp( ) | 2 | VCL | not applicable | not applicable | +| 3 | Coded slice data partition B
slice_data_partition_b_layer_rbsp( ) | 3 | VCL | not applicable | not applicable | +| 4 | Coded slice data partition C
slice_data_partition_c_layer_rbsp( ) | 4 | VCL | not applicable | not applicable | +| 5 | Coded slice of an IDR picture
slice_layer_without_partitioning_rbsp( ) | 2, 3 | VCL | VCL | VCL | +| 6 | Supplemental enhancement information (SEI)
sei_rbsp( ) | 5 | non-VCL | non-VCL | non-VCL | +| 7 | Sequence parameter set
seq_parameter_set_rbsp( ) | 0 | non-VCL | non-VCL | non-VCL | +| 8 | Picture parameter set
pic_parameter_set_rbsp( ) | 1 | non-VCL | non-VCL | non-VCL | +| 9 | Access unit delimiter
access_unit_delimiter_rbsp( ) | 6 | non-VCL | non-VCL | non-VCL | +| 10 | End of sequence
end_of_seq_rbsp( ) | 7 | non-VCL | non-VCL | non-VCL | +| 11 | End of stream
end_of_stream_rbsp( ) | 8 | non-VCL | non-VCL | non-VCL | +| 12 | Filler data
filler_data_rbsp( ) | 9 | non-VCL | non-VCL | non-VCL | +| 13 | Sequence parameter set extension
seq_parameter_set_extension_rbsp( ) | 10 | non-VCL | non-VCL | non-VCL | +| 14 | Prefix NAL unit
prefix_nal_unit_rbsp( ) | 2 | non-VCL | suffix
dependent | suffix
dependent | +| 15 | Subset sequence parameter set
subset_seq_parameter_set_rbsp( ) | 0 | non-VCL | non-VCL | non-VCL | +| 16 | Depth parameter set
depth_parameter_set_rbsp( ) | 11 | non-VCL | non-VCL | non-VCL | +| 17..18 | Reserved | | non-VCL | non-VCL | non-VCL | +| 19 | Coded slice of an auxiliary coded
picture without partitioning
slice_layer_without_partitioning_rbsp( ) | 2, 3, 4 | non-VCL | non-VCL | non-VCL | +| 20 | Coded slice extension
slice_layer_extension_rbsp( ) | 2, 3, 4 | non-VCL | VCL | VCL | +| 21 | Coded slice extension for a depth view
component or a 3D-AVC texture view
component
slice_layer_extension_rbsp( ) | 2, 3, 4 | non-VCL | non-VCL | VCL | +| 22..23 | Reserved | | non-VCL | non-VCL | VCL | +| 24..31 | Unspecified | | non-VCL | non-VCL | non-VCL | + +When NAL units with nal\_unit\_type equal to 13 or 19 are present in a coded video sequence, decoders shall either perform the (optional) decoding process specified for these NAL units or shall ignore (remove from the bitstream and discard) the contents of these NAL units. + +Decoders that conform to one or more of the profiles specified in Annex A rather than the profiles specified in Annexes F or G shall ignore (remove from the bitstream and discard) the contents of all NAL units with nal\_unit\_type equal to 14, 15, or 20. + +NAL units that use `nal_unit_type` equal to 0 or in the range of 24..31, inclusive, shall not affect the decoding process specified in this Recommendation | International Standard. + +NOTE 2 – NAL unit types 0 and 24..31 may be used as determined by the application. No decoding process for these values of `nal_unit_type` is specified in this Recommendation | International Standard. Since different applications might use NAL unit types 0 and 24..31 for different purposes, particular care must be exercised in the design of encoders that generate NAL units with `nal_unit_type` equal to 0 or in the range of 24 to 31, inclusive, and in the design of decoders that interpret the content of NAL units with `nal_unit_type` equal to 0 or in the range of 24 to 31, inclusive. + +Decoders shall ignore (remove from the bitstream and discard) the contents of all NAL units that use reserved values of `nal_unit_type`. + +NOTE 3 – This requirement allows future definition of compatible extensions to this Recommendation | International Standard. + +NOTE 4 – In previous editions of this Recommendation | International Standard, the NAL unit types 13..15 and 19..20 (or a subset of these NAL unit types) were reserved and no decoding process for NAL units having these values of `nal_unit_type` was specified. In later editions of this Recommendation | International Standard, currently reserved values of `nal_unit_type` might become non-reserved and a decoding process for these values of `nal_unit_type` might be specified. Encoders should take into consideration that the values of `nal_unit_type` that were reserved in previous editions of this Recommendation | International Standard might be ignored by decoders. + +In the text, coded slice NAL unit collectively refers to a coded slice of a non-IDR picture NAL unit or to a coded slice of an IDR picture NAL unit. The variable `IdrPicFlag` is specified as + +$$\text{IdrPicFlag} = ( ( \text{nal\_unit\_type} == 5 ) ? 1 : 0 ) \hfill (7-1)$$ + +When the value of `nal_unit_type` is equal to 5 for a NAL unit containing a slice of a particular picture, the picture shall not contain NAL units with `nal_unit_type` in the range of 1 to 4, inclusive. For coded video sequences conforming to one or more of the profiles specified in Annex A that are decoded using the decoding process specified in clauses 2 to 9, such a picture is referred to as an IDR picture. + +NOTE 5 – Slice data partitioning cannot be used for IDR pictures. + +**svc\_extension\_flag** indicates whether a `nal_unit_header_svc_extension()` or `nal_unit_header_mvc_extension()` will follow next in the syntax structure. + +When `svc_extension_flag` is not present, the value of `svc_extension_flag` is inferred to be equal to 0. + +The value of `svc_extension_flag` shall be equal to 1 for coded video sequences conforming to one or more profiles specified in Annex F. Decoders conforming to one or more profiles specified in Annex F shall ignore (remove from the bitstream and discard) NAL units for which `nal_unit_type` is equal to 14 or 20 and for which `svc_extension_flag` is equal to 0. + +The value of `svc_extension_flag` shall be equal to 0 for coded video sequences conforming to one or more profiles specified in Annex G. Decoders conforming to one or more profiles specified in Annex G shall ignore (remove from the bitstream and discard) NAL units for which `nal_unit_type` is equal to 14 or 20 and for which `svc_extension_flag` is equal to 1. + +The value of `svc_extension_flag` shall be equal to 0 for coded video sequences conforming to one or more profiles specified in Annex H. Decoders conforming to one or more profiles specified in Annex H shall ignore (remove from the bitstream and discard) NAL units for which `nal_unit_type` is equal to 14, 20, or 21 and for which `svc_extension_flag` is equal to 1. + +The value of `svc_extension_flag` shall be equal to 0 for coded video sequences conforming to one or more profiles specified in Annex I. Decoders conforming to one or more profiles specified in Annex I shall ignore (remove from the bitstream and discard) NAL units for which `nal_unit_type` is equal to 14 or 20 and for which `svc_extension_flag` is equal to 1. + +**avc\_3d\_extension\_flag** indicates for NAL units having `nal_unit_type` equal to 21 whether a `nal_unit_header_mvc_extension()` or `nal_unit_header_3davc_extension()` will follow next in the syntax structure. + +When `avc_3d_extension_flag` is not present, the value of `avc_3d_extension_flag` is inferred to be equal to 0. + +The value of `DepthFlag` is specified as follows: + +$$\text{DepthFlag} = ( \text{nal\_unit\_type} != 21 ) ? 0 : ( \text{avc\_3d\_extension\_flag} ? \text{depth\_flag} : 1 ) \hfill (7-2)$$ + +The value of `avc_3d_extension_flag` shall be equal to 0 for coded video sequences conforming to one or more profiles specified in Annex H. Decoders conforming to one or more profiles specified in Annex H shall ignore (remove from the bitstream and discard) NAL units for which `nal_unit_type` is equal to 21 and for which `avc_3d_extension_flag` is equal to 1. + +**rbsp\_byte[ i ]** is the i-th byte of an RBSP. An RBSP is specified as an ordered sequence of bytes as follows. + +The RBSP contains an SODB as follows: + +- If the SODB is empty (i.e., zero bits in length), the RBSP is also empty. +- Otherwise, the RBSP contains the SODB as follows: + - 1) The first byte of the RBSP contains the first (most significant, left-most) eight bits of the SODB; the next byte of the RBSP contains the next eight bits of the SODB, etc., until fewer than eight bits of the SODB remain. + - 2) The *rbsp\_trailing\_bits*( ) syntax structure is present after the SODB as follows: + - i) The first (most significant, left-most) bits of the final RBSP byte contain the remaining bits of the SODB (if any). + - ii) The next bit consists of a single bit equal to 1 (i.e., *rbsp\_stop\_one\_bit*). + - iii) When the *rbsp\_stop\_one\_bit* is not the last bit of a byte-aligned byte, one or more zero-valued bits (i.e., instances of *rbsp\_alignment\_zero\_bit*) are present to result in byte alignment. + - 3) One or more *cabac\_zero\_word* 16-bit syntax elements equal to 0x0000 may be present in some RBSPs after the *rbsp\_trailing\_bits*( ) at the end of the RBSP. + +Syntax structures having these RBSP properties are denoted in the syntax tables using an "\_rbsp" suffix. These structures shall be carried within NAL units as the content of the *rbsp\_byte*[ i ] data bytes. The association of the RBSP syntax structures to the NAL units shall be as specified in Table 7-1. + +NOTE 6 – When the boundaries of the RBSP are known, the decoder can extract the SODB from the RBSP by concatenating the bits of the bytes of the RBSP and discarding the *rbsp\_stop\_one\_bit*, which is the last (least significant, right-most) bit equal to 1, and discarding any following (less significant, farther to the right) bits that follow it, which are equal to 0. The data necessary for the decoding process is contained in the SODB part of the RBSP. + +**emulation\_prevention\_three\_byte** is a byte equal to 0x03. When an **emulation\_prevention\_three\_byte** is present in the NAL unit, it shall be discarded by the decoding process. + +The last byte of the NAL unit shall not be equal to 0x00. + +Within the NAL unit, the following three-byte sequences shall not occur at any byte-aligned position: + +- 0x000000 +- 0x000001 +- 0x000002 + +Within the NAL unit, any four-byte sequence that starts with 0x000003 other than the following sequences shall not occur at any byte-aligned position: + +- 0x00000300 +- 0x00000301 +- 0x00000302 +- 0x00000303 + +NOTE 7 – When *nal\_unit\_type* is equal to 0, particular care must be exercised in the design of encoders to avoid the presence of the above-listed three-byte and four-byte patterns at the beginning of the NAL unit syntax structure, as the syntax element *emulation\_prevention\_three\_byte* cannot be the third byte of a NAL unit. + +#### 7.4.1.1 Encapsulation of an SODB within an RBSP (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +The form of encapsulation of an SODB within an RBSP and the use of the *emulation\_prevention\_three\_byte* for encapsulation of an RBSP within a NAL unit is specified for the following purposes: + +- to prevent the emulation of start codes within NAL units while allowing any arbitrary SODB to be represented within a NAL unit, +- to enable identification of the end of the SODB within the NAL unit by searching the RBSP for the *rbsp\_stop\_one\_bit* starting at the end of the RBSP, +- to enable a NAL unit to have a size larger than that of the SODB under some circumstances (using one or more *cabac\_zero\_word*). + +The encoder can produce a NAL unit from an RBSP by the following procedure: + +1. The RBSP data is searched for byte-aligned bits of the following binary patterns: + +'00000000 00000000 000000xx' (where xx represents any 2 bit pattern: 00, 01, 10, or 11), + +and a byte equal to 0x03 is inserted to replace these bit patterns with the patterns: + +'00000000 00000000 00000011 000000xx', + +and finally, when the last byte of the RBSP data is equal to 0x00 (which can only occur when the RBSP ends in a `cabac_zero_word`), a final byte equal to 0x03 is appended to the end of the data. The last zero byte of a byte-aligned three-byte sequence 0x000000 in the RBSP (which is replaced by the four-byte sequence 0x00000300) is taken into account when searching the RBSP data for the next occurrence of byte-aligned bits with the binary patterns specified above. + +2. The resulting sequence of bytes is then prefixed as follows: + - If `nal_unit_type` is not equal to 14 or 20, the sequence of bytes is prefixed with the first byte of the NAL unit containing the syntax elements `forbidden_zero_bit`, `nal_ref_idc`, and `nal_unit_type`, where `nal_unit_type` indicates the type of RBSP data structure the NAL unit contains. + - Otherwise (`nal_unit_type` is equal to 14 or 20), the sequence of bytes is prefixed with the first four bytes of the NAL unit, where the first byte contains the syntax elements `forbidden_zero_bit`, `nal_ref_idc`, and `nal_unit_type` and the following three bytes contain the syntax structure `nal_unit_header_svc_extension()`. The syntax element `nal_unit_type` in the first byte indicates the presence of the syntax structure `nal_unit_header_svc_extension()` in the following three bytes and the type of RBSP data structure the NAL unit contains. + +The process specified above results in the construction of the entire NAL unit. + +This process can allow any SODB to be represented in a NAL unit while ensuring that + +- no byte-aligned start code prefix is emulated within the NAL unit, +- no sequence of 8 zero-valued bits followed by a start code prefix, regardless of byte-alignment, is emulated within the NAL unit. + +#### 7.4.1.2 Order of NAL units and association to coded pictures, access units, and video sequences + +This clause specifies constraints on the order of NAL units in the bitstream. + +Any order of NAL units in the bitstream obeying these constraints is referred to in the text as the decoding order of NAL units. Within a NAL unit, the syntax in clauses 7.3, D.1, and E.1 specifies the decoding order of syntax elements. Decoders shall be capable of receiving NAL units and their syntax elements in decoding order. + +##### 7.4.1.2.1 Order of sequence and picture parameter set RBSPs and their activation + +This clause specifies the activation process of picture and sequence parameter sets for coded video sequences that conform to one or more of the profiles specified in Annex A and are decoded using the decoding process specified in clauses 2 to 9. + +NOTE 1 – The sequence and picture parameter set mechanism decouples the transmission of infrequently changing information from the transmission of coded macroblock data. Sequence and picture parameter sets may, in some applications, be conveyed "out-of-band" using a reliable transport mechanism. + +A picture parameter set RBSP includes parameters that can be referred to by the coded slice NAL units or coded slice data partition A NAL units of one or more coded pictures. Each picture parameter set RBSP is initially considered not active at the start of the operation of the decoding process. At most one picture parameter set RBSP is considered active at any given moment during the operation of the decoding process, and the activation of any particular picture parameter set RBSP results in the deactivation of the previously-active picture parameter set RBSP (if any). + +When a picture parameter set RBSP (with a particular value of `pic_parameter_set_id`) is not active and it is referred to by a coded slice NAL unit or coded slice data partition A NAL unit (using that value of `pic_parameter_set_id`), it is activated. This picture parameter set RBSP is called the active picture parameter set RBSP until it is deactivated by the activation of another picture parameter set RBSP. A picture parameter set RBSP, with that particular value of `pic_parameter_set_id`, shall be available to the decoding process prior to its activation. + +Any picture parameter set NAL unit containing the value of `pic_parameter_set_id` for the active picture parameter set RBSP for a coded picture shall have the same content as that of the active picture parameter set RBSP for the coded picture unless it follows the last VCL NAL unit of the coded picture and precedes the first VCL NAL unit of another coded picture. + +When a picture parameter set NAL unit with a particular value of `pic_parameter_set_id` is received, its content replaces the content of the previous picture parameter set NAL unit, in decoding order, with the same value of `pic_parameter_set_id` (when a previous picture parameter set NAL unit with the same value of `pic_parameter_set_id` was present in the bitstream). + +NOTE 2 – A decoder must be capable of simultaneously storing the contents of the picture parameter sets for all values of `pic_parameter_set_id`. The content of the picture parameter set with a particular value of `pic_parameter_set_id` is overwritten when a new picture parameter set NAL unit with the same value of `pic_parameter_set_id` is received. + +A sequence parameter set RBSP includes parameters that can be referred to by one or more picture parameter set RBSPs or one or more SEI NAL units containing a buffering period SEI message. Each sequence parameter set RBSP is initially considered not active at the start of the operation of the decoding process. At most one sequence parameter set RBSP is considered active at any given moment during the operation of the decoding process, and the activation of any particular sequence parameter set RBSP results in the deactivation of the previously-active sequence parameter set RBSP (if any). + +When a sequence parameter set RBSP (with a particular value of `seq_parameter_set_id`) is not already active and it is referred to by activation of a picture parameter set RBSP (using that value of `seq_parameter_set_id`) or is referred to by an SEI NAL unit containing a buffering period SEI message (using that value of `seq_parameter_set_id`), it is activated. This sequence parameter set RBSP is called the active sequence parameter set RBSP until it is deactivated by the activation of another sequence parameter set RBSP. A sequence parameter set RBSP, with that particular value of `seq_parameter_set_id`, shall be available to the decoding process prior to its activation. An activated sequence parameter set RBSP shall remain active for the entire coded video sequence. + +NOTE 3 – Because an IDR access unit begins a new coded video sequence and an activated sequence parameter set RBSP must remain active for the entire coded video sequence, a sequence parameter set RBSP can only be activated by a buffering period SEI message when the buffering period SEI message is part of an IDR access unit. + +Any sequence parameter set NAL unit containing the value of `seq_parameter_set_id` for the active sequence parameter set RBSP for a coded video sequence shall have the same content as that of the active sequence parameter set RBSP for the coded video sequence unless it follows the last access unit of the coded video sequence and precedes the first VCL NAL unit and the first SEI NAL unit containing a buffering period SEI message (when present) of another coded video sequence. + +NOTE 4 – If picture parameter set RBSP or sequence parameter set RBSP are conveyed within the bitstream, these constraints impose an order constraint on the NAL units that contain the picture parameter set RBSP or sequence parameter set RBSP, respectively. Otherwise (picture parameter set RBSP or sequence parameter set RBSP are conveyed by other means not specified in this Recommendation | International Standard), they must be available to the decoding process in a timely fashion such that these constraints are obeyed. + +When a sequence parameter set NAL unit with a particular value of `seq_parameter_set_id` is received, its content replaces the content of the previous sequence parameter set NAL unit, in decoding order, with the same value of `seq_parameter_set_id` (when a previous sequence parameter set NAL unit with the same value of `seq_parameter_set_id` was present in the bitstream). + +NOTE 5 – A decoder must be capable of simultaneously storing the contents of the sequence parameter sets for all values of `seq_parameter_set_id`. The content of the sequence parameter set with a particular value of `seq_parameter_set_id` is overwritten when a new sequence parameter set NAL unit with the same value of `seq_parameter_set_id` is received. + +When present, a sequence parameter set extension RBSP includes parameters having a similar function to those of a sequence parameter set RBSP. For purposes of establishing constraints on the syntax elements of the sequence parameter set extension RBSP and for purposes of determining activation of a sequence parameter set extension RBSP, the sequence parameter set extension RBSP shall be considered part of the preceding sequence parameter set RBSP with the same value of `seq_parameter_set_id`. When a sequence parameter set RBSP is present that is not followed by a sequence parameter set extension RBSP with the same value of `seq_parameter_set_id` prior to the activation of the sequence parameter set RBSP, the sequence parameter set extension RBSP and its syntax elements shall be considered not present for the active sequence parameter set RBSP. + +All constraints that are expressed on the relationship between the values of the syntax elements (and the values of variables derived from those syntax elements) in sequence parameter sets and picture parameter sets and other syntax elements are expressions of constraints that apply only to the active sequence parameter set and the active picture parameter set. If any sequence parameter set RBSP is present that is not activated in the bitstream, its syntax elements shall have values that would conform to the specified constraints if it were activated by reference in an otherwise-conforming bitstream. If any picture parameter set RBSP is present that is not ever activated in the bitstream, its syntax elements shall have values that would conform to the specified constraints if it were activated by reference in an otherwise-conforming bitstream. + +During operation of the decoding process (see clause 8), the values of parameters of the active picture parameter set and the active sequence parameter set shall be considered in effect. For interpretation of SEI messages, the values of the parameters of the picture parameter set and sequence parameter set that are active for the operation of the decoding process for the VCL NAL units of the primary coded picture in the same access unit shall be considered in effect unless otherwise specified in the SEI message semantics. + +#### 7.4.1.2.2 Order of access units and association to coded video sequences + +A bitstream conforming to this Recommendation | International Standard consists of one or more coded video sequences. + +A coded video sequence consists of one or more access units. For coded video sequences that conform to one or more of the profiles specified in Annex A and are decoded using the decoding process specified in clauses 2 to 9, the order of NAL units and coded pictures and their association to access units is described in clause 7.4.1.2.3. + +The first access unit of each coded video sequence is an IDR access unit. All subsequent access units in the coded video sequence are non-IDR access units. + +It is a requirement of bitstream conformance that, when two consecutive access units in decoding order within a coded video sequence both contain non-reference pictures, the value of picture order count for each coded field or field of a coded frame in the first such access unit shall be less than or equal to the value of picture order count for each coded field or field of a coded frame in the second such access unit. + +It is a requirement of bitstream conformance that, when present, an access unit following an access unit that contains an end of sequence NAL unit shall be an IDR access unit. + +It is a requirement of bitstream conformance that, when an SEI NAL unit contains data that pertain to more than one access unit (for example, when the SEI NAL unit has a coded video sequence as its scope), it shall be contained in the first access unit to which it applies. + +It is a requirement of bitstream conformance that, when an end of stream NAL unit is present in an access unit, this access unit shall be the last access unit in the bitstream and the end of stream NAL unit shall be the last NAL unit in that access unit. + +#### **7.4.1.2.3 Order of NAL units and coded pictures and association to access units** + +This clause specifies the order of NAL units and coded pictures and association to access unit for coded video sequences that conform to one or more of the profiles specified in Annex A and are decoded using the decoding process specified in clauses 2 to 9. + +NOTE 1 – Some bitstreams that conform to profiles specified in Annexes F or G may violate the NAL unit order specified in this clause. Conditions under which such a violation of the NAL unit order occurs are specified in clauses F.7.4.1.2.3 and G.7.4.1.2.3. + +An access unit consists of one primary coded picture, zero or more corresponding redundant coded pictures, and zero or more non-VCL NAL units. The association of VCL NAL units to primary or redundant coded pictures is described in clause 7.4.1.2.5. + +The first access unit in the bitstream starts with the first NAL unit of the bitstream. + +The first of any of the following NAL units after the last VCL NAL unit of a primary coded picture specifies the start of a new access unit: + +- access unit delimiter NAL unit (when present), +- sequence parameter set NAL unit (when present), +- picture parameter set NAL unit (when present), +- SEI NAL unit (when present), +- NAL units with nal\_unit\_type in the range of 14 to 18, inclusive (when present), +- first VCL NAL unit of a primary coded picture (always present). + +The constraints for the detection of the first VCL NAL unit of a primary coded picture are specified in clause 7.4.1.2.4. + +The following constraints shall be obeyed by the order of the coded pictures and non-VCL NAL units within an access unit: + +- When an access unit delimiter NAL unit is present, it shall be the first NAL unit. There shall be at most one access unit delimiter NAL unit in any access unit. +- When any SEI NAL units are present, they shall precede the primary coded picture. +- When an SEI NAL unit containing a buffering period SEI message is present, the buffering period SEI message shall be the first SEI message payload of the first SEI NAL unit in the access unit. +- The primary coded picture shall precede the corresponding redundant coded pictures. +- When redundant coded pictures are present, they shall be ordered in ascending order of the value of redundant\_pic\_cnt. + +- When a sequence parameter set extension NAL unit is present, it shall be the next NAL unit after a sequence parameter set NAL unit having the same value of `seq_parameter_set_id` as in the sequence parameter set extension NAL unit. +- When one or more coded slice of an auxiliary coded picture without partitioning NAL units is present, they shall follow the primary coded picture and all redundant coded pictures (if any). +- When an end of sequence NAL unit is present, it shall follow the primary coded picture and all redundant coded pictures (if any) and all coded slice of an auxiliary coded picture without partitioning NAL units (if any). +- When an end of stream NAL unit is present, it shall be the last NAL unit. +- NAL units having `nal_unit_type` equal to 0, 12, or in the range of 20 to 31, inclusive, shall not precede the first VCL NAL unit of the primary coded picture. + +NOTE 2 – Sequence parameter set NAL units or picture parameter set NAL units may be present in an access unit, but cannot follow the last VCL NAL unit of the primary coded picture within the access unit, as this condition would specify the start of a new access unit. + +NOTE 3 – When a NAL unit having `nal_unit_type` equal to 7 or 8 is present in an access unit, it may or may not be referred to in the coded pictures of the access unit in which it is present, and may be referred to in coded pictures of subsequent access units. + +The structure of access units not containing any NAL units with `nal_unit_type` equal to 0, 7, 8, or in the range of 12 to 18, inclusive, or in the range of 20 to 31, inclusive, is shown in Figure 7-1. + +![Flowchart showing the structure of an access unit. It starts with 'start', followed by 'Access unit delimiter', 'SEI', 'Primary coded picture', 'Redundant coded picture', 'Auxiliary coded picture', 'End of sequence', and 'End of stream'. Arrows indicate the flow, with some boxes having self-loops. The diagram is labeled H.264(09)_F7-1 and ends with 'end'.](b3335932702b8668e62791e9fd12c9ff_img.jpg) + +``` + +graph TD + start((start)) --> A[Access unit delimiter] + A --> A + A --> S[SEI] + S --> S + S --> P[Primary coded picture] + P --> R[Redundant coded picture] + R --> R + R --> X[Auxiliary coded picture] + X --> X + X --> E[End of sequence] + E --> E + E --> ES[End of stream] + ES --> ES + ES --> end((end)) + +``` + +H.264(09)\_F7-1 + +Flowchart showing the structure of an access unit. It starts with 'start', followed by 'Access unit delimiter', 'SEI', 'Primary coded picture', 'Redundant coded picture', 'Auxiliary coded picture', 'End of sequence', and 'End of stream'. Arrows indicate the flow, with some boxes having self-loops. The diagram is labeled H.264(09)\_F7-1 and ends with 'end'. + +**Figure 7-1 – Structure of an access unit not containing any NAL units with nal\_unit\_type equal to 0, 7, 8, or in the range of 12 to 18, inclusive, or in the range of 20 to 31, inclusive** + +#### 7.4.1.2.4 Detection of the first VCL NAL unit of a primary coded picture + +This clause specifies constraints on VCL NAL unit syntax that are sufficient to enable the detection of the first VCL NAL unit of each primary coded picture for coded video sequences that conform to one or more of the profiles specified in Annex A and are decoded using the decoding process specified in clauses 2 to 9. + +Any coded slice NAL unit or coded slice data partition A NAL unit of the primary coded picture of the current access unit shall be different from any coded slice NAL unit or coded slice data partition A NAL unit of the primary coded picture of the previous access unit in one or more of the following ways: + +- frame\_num differs in value. The value of frame\_num used to test this condition is the value of frame\_num that appears in the syntax of the slice header, regardless of whether that value is inferred to have been equal to 0 for subsequent use in the decoding process due to the presence of memory\_management\_control\_operation equal to 5. + +NOTE 1 – A consequence of the above statement is that a primary coded picture having frame\_num equal to 1 cannot contain a memory\_management\_control\_operation equal to 5 unless some other condition listed below is fulfilled for the next primary coded picture that follows after it (if any). + +- pic\_parameter\_set\_id differs in value. +- field\_pic\_flag differs in value. +- bottom\_field\_flag is present in both and differs in value. +- nal\_ref\_idc differs in value with one of the nal\_ref\_idc values being equal to 0. +- pic\_order\_cnt\_type is equal to 0 for both and either pic\_order\_cnt\_lsb differs in value, or delta\_pic\_order\_cnt\_bottom differs in value. +- pic\_order\_cnt\_type is equal to 1 for both and either delta\_pic\_order\_cnt[ 0 ] differs in value, or delta\_pic\_order\_cnt[ 1 ] differs in value. + +- IdrPicFlag differs in value. +- IdrPicFlag is equal to 1 for both and idr\_pic\_id differs in value. + +NOTE 2 – Some of the VCL NAL units in redundant coded pictures or some non-VCL NAL units (e.g., an access unit delimiter NAL unit) may also be used for the detection of the boundary between access units, and may therefore aid in the detection of the start of a new primary coded picture. + +#### 7.4.1.2.5 Order of VCL NAL units and association to coded pictures + +This clause specifies the order of VCL NAL units and association to coded pictures for coded video sequences that conform to one or more of the profiles specified in Annex A and are decoded using the decoding process specified in clauses 2 to 9. + +Each VCL NAL unit is part of a coded picture. + +The order of the VCL NAL units within a coded IDR picture is constrained as follows: + +- If arbitrary slice order is allowed as specified in Annex A, coded slice of an IDR picture NAL units may have any order relative to each other. +- Otherwise (arbitrary slice order is not allowed), the following applies: + - If separate\_colour\_plane\_flag is equal to 0, coded slice of an IDR picture NAL units of a slice group shall not be interleaved with coded slice of an IDR picture NAL units of another slice group and the order of coded slice of an IDR picture NAL units within a slice group shall be in the order of increasing macroblock address for the first macroblock of each coded slice of an IDR picture NAL unit of the particular slice group. + - Otherwise (separate\_colour\_plane\_flag is equal to 1), coded slice of an IDR picture NAL units of a slice group for a particular value of colour\_plane\_id shall not be interleaved with coded slice of an IDR picture NAL units of another slice group with the same value of colour\_plane\_id and the order of coded slices of IDR picture NAL units within a slice group for a particular value of colour\_plane\_id shall be in the order of increasing macroblock address for the first macroblock of each coded slice of an IDR picture NAL unit of the particular slice group having the particular value of colour\_plane\_id. + +NOTE 1 – When separate\_colour\_plane\_flag is equal to 1, the relative ordering of coded slices having different values of colour\_plane\_id is not constrained. + +The order of the VCL NAL units within a coded non-IDR picture is constrained as follows: + +- If arbitrary slice order is allowed as specified in Annex A, coded slice of a non-IDR picture NAL units or coded slice data partition A NAL units may have any order relative to each other. A coded slice data partition A NAL unit with a particular value of slice\_id shall precede any present coded slice data partition B NAL unit with the same value of slice\_id. A coded slice data partition A NAL unit with a particular value of slice\_id shall precede any present coded slice data partition C NAL unit with the same value of slice\_id. When a coded slice data partition B NAL unit with a particular value of slice\_id is present, it shall precede any present coded slice data partition C NAL unit with the same value of slice\_id. +- Otherwise (arbitrary slice order is not allowed), the following applies: + - If separate\_colour\_plane\_flag is equal to 0, coded slice of a non-IDR picture NAL units or coded slice data partition NAL units of a slice group shall not be interleaved with coded slice of a non-IDR picture NAL units or coded slice data partition NAL units of another slice group and the order of coded slice of a non-IDR picture NAL units or coded slice data partition A NAL units within a slice group shall be in the order of increasing macroblock address for the first macroblock of each coded slice of a non-IDR picture NAL unit or coded slice data partition A NAL unit of the particular slice group. A coded slice data partition A NAL unit with a particular value of slice\_id shall immediately precede any present coded slice data partition B NAL unit with the same value of slice\_id. A coded slice data partition A NAL unit with a particular value of slice\_id shall immediately precede any present coded slice data partition C NAL unit with the same value of slice\_id, when a coded slice data partition B NAL unit with the same value of slice\_id is not present. When a coded slice data partition B NAL unit with a particular value of slice\_id is present, it shall immediately precede any present coded slice data partition C NAL unit with the same value of slice\_id. + - Otherwise (separate\_colour\_plane\_flag is equal to 1), coded slice of a non-IDR picture NAL units or coded slice data partition NAL units of a slice group for a particular value of colour\_plane\_id shall not be interleaved with coded slice of a non-IDR picture NAL units or coded slice data partition NAL units of another slice group with the same value of colour\_plane\_id and the order of coded slice of a non-IDR picture NAL units or coded slice data partition A NAL units within a slice group for particular value of colour\_plane\_id shall be in the order of increasing macroblock address for the first macroblock of each coded slice of a non-IDR picture NAL unit or coded slice data partition A NAL unit of the particular slice group having the particular value of colour\_plane\_id. A coded slice data partition A NAL unit associated with a particular value of slice\_id and + +colour\_plane\_id shall immediately precede any present coded slice data partition B NAL unit with the same value of slice\_id and colour\_plane\_id. A coded slice data partition A NAL unit associated with a particular value of slice\_id and colour\_plane\_id shall immediately precede any present coded slice data partition C NAL unit with the same value of slice\_id and colour\_plane\_id, when a coded slice data partition B NAL unit with the same value of slice\_id and colour\_plane\_id is not present. When a coded slice data partition B NAL unit with a particular value of slice\_id and colour\_plane\_id is present, it shall immediately precede any present coded slice data partition C NAL unit with the same value of slice\_id and colour\_plane\_id. + +NOTE 2 – When separate\_colour\_plane\_flag is equal to 1, the relative ordering of coded slices having different values of colour\_plane\_id is not constrained. + +NAL units having nal\_unit\_type equal to 12 may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having nal\_unit\_type equal to 0 or in the range of 24 to 31, inclusive, which are unspecified, may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having nal\_unit\_type in the range of 20 to 23, inclusive, shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +#### 7.4.2 Raw byte sequence payloads and RBSP trailing bits semantics + +##### 7.4.2.1 Sequence parameter set RBSP semantics + +###### 7.4.2.1.1 Sequence parameter set data semantics + +**profile\_idc** and **level\_idc** indicate the profile and level to which the coded video sequence conforms. + +**constraint\_set0\_flag** equal to 1 indicates that the coded video sequence obeys all constraints specified in clause A.2.1. **constraint\_set0\_flag** equal to 0 indicates that the coded video sequence may or may not obey all constraints specified in clause A.2.1. + +**constraint\_set1\_flag** equal to 1 indicates that the coded video sequence obeys all constraints specified in clause A.2.2. **constraint\_set1\_flag** equal to 0 indicates that the coded video sequence may or may not obey all constraints specified in clause A.2.2. + +**constraint\_set2\_flag** equal to 1 indicates that the coded video sequence obeys all constraints specified in clause A.2.3. **constraint\_set2\_flag** equal to 0 indicates that the coded video sequence may or may not obey all constraints specified in clause A.2.3. + +NOTE 1 – When one or more than one of **constraint\_set0\_flag**, **constraint\_set1\_flag**, or **constraint\_set2\_flag** are equal to 1, the coded video sequence must obey the constraints of all of the indicated subclauses of clause A.2. When **profile\_idc** is equal to 44, 100, 110, 122, or 244, the values of **constraint\_set0\_flag**, **constraint\_set1\_flag**, and **constraint\_set2\_flag** must all be equal to 0. + +**constraint\_set3\_flag** is specified as follows: + +- If **profile\_idc** is equal to 66, 77, or 88 and **level\_idc** is equal to 11, **constraint\_set3\_flag** equal to 1 indicates that the coded video sequence obeys all constraints specified in Annex A for level 1b and **constraint\_set3\_flag** equal to 0 indicates that the coded video sequence obeys all constraints specified in Annex A for level 1.1. +- Otherwise, if **profile\_idc** is equal to 100 or 110, **constraint\_set3\_flag** equal to 1 indicates that the coded video sequence obeys all constraints specified in Annex A for the High 10 Intra profile, and **constraint\_set3\_flag** equal to 0 indicates that the coded video sequence may or may not obey these corresponding constraints. +- Otherwise, if **profile\_idc** is equal to 122, **constraint\_set3\_flag** equal to 1 indicates that the coded video sequence obeys all constraints specified in Annex A for the High 4:2:2 Intra profile, and **constraint\_set3\_flag** equal to 0 indicates that the coded video sequence may or may not obey these corresponding constraints. +- Otherwise, if **profile\_idc** is equal to 44, **constraint\_set3\_flag** shall be equal to 1. When **profile\_idc** is equal to 44, the value of 0 for **constraint\_set3\_flag** is forbidden. +- Otherwise, if **profile\_idc** is equal to 244, **constraint\_set3\_flag** equal to 1 indicates that the coded video sequence obeys all constraints specified in Annex A for the High 4:4:4 Intra profile, and **constraint\_set3\_flag** equal to 0 indicates that the coded video sequence may or may not obey these corresponding constraints. +- Otherwise (**profile\_idc** is equal to 66, 77, or 88 and **level\_idc** is not equal to 11, or **profile\_idc** is not equal to 66, 77, 88, 100, 110, 122, 244, or 44), the value of 1 for **constraint\_set3\_flag** is reserved for future use by ITU-T | ISO/IEC. **constraint\_set3\_flag** shall be equal to 0 for coded video sequences with **profile\_idc** equal to 66, 77, or 88 and **level\_idc** not equal to 11 and for coded video sequences with **profile\_idc** not equal to 66, 77, 88, 100, 110, 122, 244, or 44 in bitstreams conforming to this Recommendation | International Standard. Decoders shall ignore the value of **constraint\_set3\_flag** when **profile\_idc** is equal to 66, 77, or 88 and **level\_idc** is not equal to 11 or when **profile\_idc** is not equal to 66, 77, 88, 100, 110, 122, 244, or 44. + +**constraint\_set4\_flag** is specified as follows: + +- If **profile\_idc** is equal to 77, 88, 100, or 110, **constraint\_set4\_flag** equal to 1 indicates that the value of **frame\_mbs\_only\_flag** is equal to 1. **constraint\_set4\_flag** equal to 0 indicates that the value of **frame\_mbs\_only\_flag** may or may not be equal to 1. +- Otherwise, if **profile\_idc** is equal to 118, 128, or 134, **constraint\_set4\_flag** equal to 1 indicates that the coded video sequence obeys all constraints specified in clause G.10.1.1. **constraint\_set4\_flag** equal to 0 indicates that the coded video sequence may or may not obey the constraints specified in clause G.10.1.1. +- Otherwise (**profile\_idc** is not equal to 77, 88, 100, 110, 118, 128, or 134), the value of 1 for **constraint\_set4\_flag** is reserved for future use by ITU-T | ISO/IEC. **constraint\_set4\_flag** shall be equal to 0 for coded video sequences with **profile\_idc** not equal to 77, 88, 100, 110, 118, 128, or 134 in bitstreams conforming to this Recommendation | International Standard. Decoders shall ignore the value of **constraint\_set4\_flag** when **profile\_idc** is not equal to 77, 88, 100, 110, 118, 128, or 134. + +**constraint\_set5\_flag** is specified as follows: + +- If **profile\_idc** is equal to 77, 88, or 100, **constraint\_set5\_flag** equal to 1 indicates that B slice types are not present in the coded video sequence. **constraint\_set5\_flag** equal to 0 indicates that B slice types may or may not be present in the coded video sequence. +- Otherwise, if **profile\_idc** is equal to 118, **constraint\_set5\_flag** equal to 1 indicates that the coded video sequence obeys all constraints specified in clause G.10.1.2 and **constraint\_set5\_flag** equal to 0 indicates that the coded video sequence may or may not obey all constraints specified in clause G.10.1.2. +- Otherwise (**profile\_idc** is not equal to 77, 88, 100, or 118), the value of 1 for **constraint\_set5\_flag** is reserved for future use by ITU-T | ISO/IEC. **constraint\_set5\_flag** shall be equal to 0 when **profile\_idc** is not equal to 77, 88, 100, or 118 in bitstreams conforming to this Recommendation | International Standard. Decoders shall ignore the value of **constraint\_set5\_flag** when **profile\_idc** is not equal to 77, 88, 100, or 118. + +NOTE 2 – For a coded video sequence conforming to both the Multiview High and Stereo High profiles, a corresponding combination would use **profile\_idc** equal to 118 and **constraint\_set5\_flag** equal to 1. + +**reserved\_zero\_2bits** shall be equal to 0. Other values of **reserved\_zero\_2bits** may be specified in the future by ITU-T | ISO/IEC. Decoders shall ignore the value of **reserved\_zero\_2bits**. + +**seq\_parameter\_set\_id** identifies the sequence parameter set that is referred to by the picture parameter set. The value of **seq\_parameter\_set\_id** shall be in the range of 0 to 31, inclusive. + +NOTE 3 – When feasible, encoders should use distinct values of **seq\_parameter\_set\_id** when the values of other sequence parameter set syntax elements differ rather than changing the values of the syntax elements associated with a specific value of **seq\_parameter\_set\_id**. + +**chroma\_format\_idc** specifies the chroma sampling relative to the luma sampling as specified in clause 6.2. The value of **chroma\_format\_idc** shall be in the range of 0 to 3, inclusive. When **chroma\_format\_idc** is not present, it shall be inferred to be equal to 1 (4:2:0 chroma format). + +**separate\_colour\_plane\_flag** equal to 1 specifies that the three colour components of the 4:4:4 chroma format are coded separately. **separate\_colour\_plane\_flag** equal to 0 specifies that the colour components are not coded separately. When **separate\_colour\_plane\_flag** is not present, it shall be inferred to be equal to 0. When **separate\_colour\_plane\_flag** is equal to 1, the primary coded picture consists of three separate components, each of which consists of coded samples of one colour plane (Y, Cb or Cr) that each use the monochrome coding syntax. In this case, each colour plane is associated with a specific **colour\_plane\_id** value. + +NOTE 4 – There is no dependency in decoding processes between the colour planes having different **colour\_plane\_id** values. For example, the decoding process of a monochrome picture with one value of **colour\_plane\_id** does not use any data from monochrome pictures having different values of **colour\_plane\_id** for inter prediction. + +Depending on the value of **separate\_colour\_plane\_flag**, the value of the variable **ChromaArrayType** is assigned as follows: + +- If **separate\_colour\_plane\_flag** is equal to 0, **ChromaArrayType** is set equal to **chroma\_format\_idc**. +- Otherwise (**separate\_colour\_plane\_flag** is equal to 1), **ChromaArrayType** is set equal to 0. + +**bit\_depth\_luma\_minus8** specifies the bit depth of the samples of the luma array and the value of the luma quantization parameter range offset **QpBdOffsety**, as specified by + +$$\text{BitDepth}_Y = 8 + \text{bit\_depth\_luma\_minus8} \quad (7-3)$$ + +$$\text{QpBdOffset}_Y = 6 * \text{bit\_depth\_luma\_minus8} \quad (7-4)$$ + +When `bit_depth_luma_minus8` is not present, it shall be inferred to be equal to 0. `bit_depth_luma_minus8` shall be in the range of 0 to 6, inclusive. + +**bit\_depth\_chroma\_minus8** specifies the bit depth of the samples of the chroma arrays and the value of the chroma quantization parameter range offset `QpBdOffsetC`, as specified by + +$$\text{BitDepth}_C = 8 + \text{bit\_depth\_chroma\_minus8} \quad (7-5)$$ + +$$\text{QpBdOffset}_C = 6 * \text{bit\_depth\_chroma\_minus8} \quad (7-6)$$ + +When `bit_depth_chroma_minus8` is not present, it shall be inferred to be equal to 0. `bit_depth_chroma_minus8` shall be in the range of 0 to 6, inclusive. + +NOTE 5 – The value of `bit_depth_chroma_minus8` is not used in the decoding process when `ChromaArrayType` is equal to 0. In particular, when `separate_colour_plane_flag` is equal to 1, each colour plane is decoded as a distinct monochrome picture using the luma component decoding process (except for the selection of scaling matrices) and the luma bit depth is used for all three colour components. + +The variable `RawMbBits` is derived as + +$$\text{RawMbBits} = 256 * \text{BitDepth}_Y + 2 * \text{MbWidth}_C * \text{MbHeight}_C * \text{BitDepth}_C \quad (7-7)$$ + +**qpprime\_y\_zero\_transform\_bypass\_flag** equal to 1 specifies that, when $QP'_Y$ is equal to 0, a transform bypass operation for the transform coefficient decoding process and picture construction process prior to deblocking filter process as specified in clause 8.5 shall be applied. `qpprime_y_zero_transform_bypass_flag` equal to 0 specifies that the transform coefficient decoding process and picture construction process prior to deblocking filter process shall not use the transform bypass operation. When `qpprime_y_zero_transform_bypass_flag` is not present, it shall be inferred to be equal to 0. + +**seq\_scaling\_matrix\_present\_flag** equal to 1 specifies that the flags `seq_scaling_list_present_flag[ i ]` for $i = 0..7$ or $i = 0..11$ are present. `seq_scaling_matrix_present_flag` equal to 0 specifies that these flags are not present and the sequence-level scaling list specified by `Flat_4x4_16` shall be inferred for $i = 0..5$ and the sequence-level scaling list specified by `Flat_8x8_16` shall be inferred for $i = 6..11$ . When `seq_scaling_matrix_present_flag` is not present, it shall be inferred to be equal to 0. + +The scaling lists `Flat_4x4_16` and `Flat_8x8_16` are specified as follows: + +$$\text{Flat\_4x4\_16}[ k ] = 16, \quad \text{with } k = 0..15, \quad (7-8)$$ + +$$\text{Flat\_8x8\_16}[ k ] = 16, \quad \text{with } k = 0..63. \quad (7-9)$$ + +**seq\_scaling\_list\_present\_flag[ i ]** equal to 1 specifies that the syntax structure for scaling list $i$ is present in the sequence parameter set. `seq_scaling_list_present_flag[ i ]` equal to 0 specifies that the syntax structure for scaling list $i$ is not present in the sequence parameter set and the scaling list fall-back rule set A specified in Table 7-2 shall be used to infer the sequence-level scaling list for index $i$ . + +**Table 7-2 – Assignment of mnemonic names to scaling list indices and specification of fall-back rule** + +| Value of scaling list index | Mnemonic name | Block size | MB prediction type | Component | Scaling list fall-back rule set A | Scaling list fall-back rule set B | Default scaling list | +|-----------------------------|-----------------|------------|--------------------|-----------|-----------------------------------|-----------------------------------|----------------------| +| 0 | SI_4x4_Intra_Y | 4x4 | Intra | Y | default scaling list | sequence-level scaling list | Default_4x4_Intra | +| 1 | SI_4x4_Intra_Cb | 4x4 | Intra | Cb | scaling list for i = 0 | scaling list for i = 0 | Default_4x4_Intra | +| 2 | SI_4x4_Intra_Cr | 4x4 | Intra | Cr | scaling list for i = 1 | scaling list for i = 1 | Default_4x4_Intra | +| 3 | SI_4x4_Inter_Y | 4x4 | Inter | Y | default scaling list | sequence-level scaling list | Default_4x4_Inter | +| 4 | SI_4x4_Inter_Cb | 4x4 | Inter | Cb | scaling list for i = 3 | scaling list for i = 3 | Default_4x4_Inter | +| 5 | SI_4x4_Inter_Cr | 4x4 | Inter | Cr | scaling list for i = 4 | scaling list for i = 4 | Default_4x4_Inter | +| 6 | SI_8x8_Intra_Y | 8x8 | Intra | Y | default scaling list | sequence-level scaling list | Default_8x8_Intra | +| 7 | SI_8x8_Inter_Y | 8x8 | Inter | Y | default scaling list | sequence-level scaling list | Default_8x8_Inter | +| 8 | SI_8x8_Intra_Cb | 8x8 | Intra | Cb | scaling list for i = 6 | scaling list for i = 6 | Default_8x8_Intra | +| 9 | SI_8x8_Inter_Cb | 8x8 | Inter | Cb | scaling list for i = 7 | scaling list for i = 7 | Default_8x8_Inter | +| 10 | SI_8x8_Intra_Cr | 8x8 | Intra | Cr | scaling list for i = 8 | scaling list for i = 8 | Default_8x8_Intra | +| 11 | SI_8x8_Inter_Cr | 8x8 | Inter | Cr | scaling list for i = 9 | scaling list for i = 9 | Default_8x8_Inter | + +Table 7-3 specifies the default scaling lists Default\_4x4\_Intra and Default\_4x4\_Inter. Table 7-4 specifies the default scaling lists Default\_8x8\_Intra and Default\_8x8\_Inter. + +**Table 7-3 – Specification of default scaling lists Default\_4x4\_Intra and Default\_4x4\_Inter** + +| idx | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +|--------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| Default_4x4_Intra[ idx ] | 6 | 13 | 13 | 20 | 20 | 20 | 28 | 28 | 28 | 28 | 32 | 32 | 32 | 37 | 37 | 42 | +| Default_4x4_Inter[ idx ] | 10 | 14 | 14 | 20 | 20 | 20 | 24 | 24 | 24 | 24 | 27 | 27 | 27 | 30 | 30 | 34 | + +**Table 7-4 – Specification of default scaling lists Default\_8x8\_Intra and Default\_8x8\_Inter** + +| idx | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +|--------------------------|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| Default_8x8_Intra[ idx ] | 6 | 10 | 10 | 13 | 11 | 13 | 16 | 16 | 16 | 16 | 18 | 18 | 18 | 18 | 18 | 23 | +| Default_8x8_Inter[ idx ] | 9 | 13 | 13 | 15 | 13 | 15 | 17 | 17 | 17 | 17 | 19 | 19 | 19 | 19 | 19 | 21 | + +**Table 7-4 (continued) – Specification of default scaling lists Default\_8x8\_Intra and Default\_8x8\_Inter** + +| idx | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | +|--------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| Default_8x8_Intra[ idx ] | 23 | 23 | 23 | 23 | 23 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | 27 | 27 | 27 | 27 | +| Default_8x8_Inter[ idx ] | 21 | 21 | 21 | 21 | 21 | 22 | 22 | 22 | 22 | 22 | 22 | 22 | 24 | 24 | 24 | 24 | + +**Table 7-4 (continued) – Specification of default scaling lists Default\_8x8\_Intra and Default\_8x8\_Inter** + +| idx | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | +|--------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| Default_8x8_Intra[ idx ] | 27 | 27 | 27 | 27 | 29 | 29 | 29 | 29 | 29 | 29 | 29 | 31 | 31 | 31 | 31 | 31 | +| Default_8x8_Inter[ idx ] | 24 | 24 | 24 | 24 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | 27 | 27 | 27 | 27 | 27 | + +**Table 7-4 (concluded) – Specification of default scaling lists Default\_8x8\_Intra and Default\_8x8\_Inter** + +| idx | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | +|--------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| Default_8x8_Intra[ idx ] | 31 | 33 | 33 | 33 | 33 | 33 | 36 | 36 | 36 | 36 | 38 | 38 | 38 | 40 | 40 | 42 | +| Default_8x8_Inter[ idx ] | 27 | 28 | 28 | 28 | 28 | 28 | 30 | 30 | 30 | 30 | 32 | 32 | 32 | 33 | 33 | 35 | + +**log2\_max\_frame\_num\_minus4** specifies the value of the variable MaxFrameNum that is used in frame\_num related derivations as follows: + +$$\text{MaxFrameNum} = 2^{(\text{log2\_max\_frame\_num\_minus4} + 4)} \quad (7-10)$$ + +The value of log2\_max\_frame\_num\_minus4 shall be in the range of 0 to 12, inclusive. + +**pic\_order\_cnt\_type** specifies the method to decode picture order count (as specified in clause 8.2.1). The value of pic\_order\_cnt\_type shall be in the range of 0 to 2, inclusive. + +pic\_order\_cnt\_type shall not be equal to 2 in a coded video sequence that contains any of the following: + +- an access unit containing a non-reference frame followed immediately by an access unit containing a non-reference picture, +- two access units each containing a field with the two fields together forming a complementary non-reference field pair followed immediately by an access unit containing a non-reference picture, +- an access unit containing a non-reference field followed immediately by an access unit containing another non-reference picture that does not form a complementary non-reference field pair with the first of the two access units. + +**log2\_max\_pic\_order\_cnt\_lsb\_minus4** specifies the value of the variable MaxPicOrderCntLsb that is used in the decoding process for picture order count as specified in clause 8.2.1 as follows: + +$$\text{MaxPicOrderCntLsb} = 2^{(\text{log2\_max\_pic\_order\_cnt\_lsb\_minus4} + 4)} \quad (7-11)$$ + +The value of log2\_max\_pic\_order\_cnt\_lsb\_minus4 shall be in the range of 0 to 12, inclusive. + +**delta\_pic\_order\_always\_zero\_flag** equal to 1 specifies that delta\_pic\_order\_cnt[ 0 ] and delta\_pic\_order\_cnt[ 1 ] are not present in the slice headers of the sequence and shall be inferred to be equal to 0. delta\_pic\_order\_always\_zero\_flag equal to 0 specifies that delta\_pic\_order\_cnt[ 0 ] is present in the slice headers of the sequence and delta\_pic\_order\_cnt[ 1 ] may be present in the slice headers of the sequence. + +**offset\_for\_non\_ref\_pic** is used to calculate the picture order count of a non-reference picture as specified in clause 8.2.1. The value of offset\_for\_non\_ref\_pic shall be in the range of $-2^{31} + 1$ to $2^{31} - 1$ , inclusive. + +**offset\_for\_top\_to\_bottom\_field** is used to calculate the picture order count of a bottom field as specified in clause 8.2.1. The value of offset\_for\_top\_to\_bottom\_field shall be in the range of $-2^{31} + 1$ to $2^{31} - 1$ , inclusive. + +**num\_ref\_frames\_in\_pic\_order\_cnt\_cycle** is used in the decoding process for picture order count as specified in clause 8.2.1. The value of num\_ref\_frames\_in\_pic\_order\_cnt\_cycle shall be in the range of 0 to 255, inclusive. + +**offset\_for\_ref\_frame[ i ]** is an element of a list of num\_ref\_frames\_in\_pic\_order\_cnt\_cycle values used in the decoding process for picture order count as specified in clause 8.2.1. The value of offset\_for\_ref\_frame[ i ] shall be in the range of $-2^{31} + 1$ to $2^{31} - 1$ , inclusive. + +When pic\_order\_cnt\_type is equal to 1, the variable ExpectedDeltaPerPicOrderCntCycle is derived by + +$$\begin{aligned} \text{ExpectedDeltaPerPicOrderCntCycle} &= 0 \\ \text{for ( i = 0; i < num\_ref\_frames\_in\_pic\_order\_cnt\_cycle; i++)} \\ \text{ExpectedDeltaPerPicOrderCntCycle} &+= \text{offset\_for\_ref\_frame[ i ]} \end{aligned} \quad (7-12)$$ + +**max\_num\_ref\_frames** specifies the maximum number of short-term and long-term reference frames, complementary reference field pairs, and non-paired reference fields that may be used by the decoding process for inter prediction of any picture in the coded video sequence. max\_num\_ref\_frames also determines the size of the sliding window operation as specified in clause 8.2.5.3. The value of max\_num\_ref\_frames shall be in the range of 0 to MaxDpbFrames (as specified in clause A.3.1 or A.3.2), inclusive. + +**gaps\_in\_frame\_num\_value\_allowed\_flag** specifies the allowed values of frame\_num as specified in clause 7.4.3 and the decoding process in case of an inferred gap between values of frame\_num as specified in clause 8.2.5.2. + +**pic\_width\_in\_mbs\_minus1** plus 1 specifies the width of each decoded picture in units of macroblocks. + +The variable for the picture width in units of macroblocks is derived as + +$$\text{PicWidthInMbs} = \text{pic\_width\_in\_mbs\_minus1} + 1 \quad (7-13)$$ + +The variable for picture width for the luma component is derived as + +$$\text{PicWidthInSamples}_L = \text{PicWidthInMbs} * 16 \quad (7-14)$$ + +The variable for picture width for the chroma components is derived as + +$$\text{PicWidthInSamples}_C = \text{PicWidthInMbs} * \text{MbWidthC} \quad (7-15)$$ + +**pic\_height\_in\_map\_units\_minus1** plus 1 specifies the height in slice group map units of a decoded frame or field. + +The variables PicHeightInMapUnits and PicSizeInMapUnits are derived as + +$$\text{PicHeightInMapUnits} = \text{pic\_height\_in\_map\_units\_minus1} + 1 \quad (7-16)$$ + +$$\text{PicSizeInMapUnits} = \text{PicWidthInMbs} * \text{PicHeightInMapUnits} \quad (7-17)$$ + +**frame\_mbs\_only\_flag** equal to 0 specifies that coded pictures of the coded video sequence may either be coded fields or coded frames. frame\_mbs\_only\_flag equal to 1 specifies that every coded picture of the coded video sequence is a coded frame containing only frame macroblocks. + +The allowed range of values for pic\_width\_in\_mbs\_minus1, pic\_height\_in\_map\_units\_minus1, and frame\_mbs\_only\_flag is specified by constraints in Annex A. + +Depending on frame\_mbs\_only\_flag, semantics are assigned to pic\_height\_in\_map\_units\_minus1 as follows: + +- If frame\_mbs\_only\_flag is equal to 0, pic\_height\_in\_map\_units\_minus1 plus 1 is the height of a field in units of macroblocks. +- Otherwise (frame\_mbs\_only\_flag is equal to 1), pic\_height\_in\_map\_units\_minus1 plus 1 is the height of a frame in units of macroblocks. + +The variable FrameHeightInMbs is derived as + +$$\text{FrameHeightInMbs} = ( 2 - \text{frame\_mbs\_only\_flag} ) * \text{PicHeightInMapUnits} \quad (7-18)$$ + +**mb\_adaptive\_frame\_field\_flag** equal to 0 specifies no switching between frame and field macroblocks within a picture. **mb\_adaptive\_frame\_field\_flag** equal to 1 specifies the possible use of switching between frame and field macroblocks within frames. When **mb\_adaptive\_frame\_field\_flag** is not present, it shall be inferred to be equal to 0. + +**direct\_8x8\_inference\_flag** specifies the method used in the derivation process for luma motion vectors for B\_Skip, B\_Direct\_16x16 and B\_Direct\_8x8 as specified in clause 8.4.1.2. When **frame\_mbs\_only\_flag** is equal to 0, **direct\_8x8\_inference\_flag** shall be equal to 1. + +**frame\_cropping\_flag** equal to 1 specifies that the frame cropping offset parameters follow next in the sequence parameter set. **frame\_cropping\_flag** equal to 0 specifies that the frame cropping offset parameters are not present. + +**frame\_crop\_left\_offset**, **frame\_crop\_right\_offset**, **frame\_crop\_top\_offset**, **frame\_crop\_bottom\_offset** specify the samples of the pictures in the coded video sequence that are output from the decoding process, in terms of a rectangular region specified in frame coordinates for output. + +The variables CropUnitX and CropUnitY are derived as follows: + +- If ChromaArrayType is equal to 0, CropUnitX and CropUnitY are derived as: + +$$\text{CropUnitX} = 1 \tag{7-19}$$ + +$$\text{CropUnitY} = 2 - \text{frame\_mbs\_only\_flag} \tag{7-20}$$ + +- Otherwise (ChromaArrayType is equal to 1, 2, or 3), CropUnitX and CropUnitY are derived as: + +$$\text{CropUnitX} = \text{SubWidthC} \tag{7-21}$$ + +$$\text{CropUnitY} = \text{SubHeightC} * ( 2 - \text{frame\_mbs\_only\_flag} ) \tag{7-22}$$ + +The variables CroppedWidth and CroppedHeight are derived as follows: + +$$\begin{aligned} \text{CroppedWidth} = \text{PicWidthInSamples} - \\ \text{CropUnitX} * ( \text{frame\_crop\_left\_offset} + \text{frame\_crop\_right\_offset} ) \end{aligned} \tag{7-23}$$ + +$$\begin{aligned} \text{CroppedHeight} = 16 * \text{FrameHeightInMbs} - \\ \text{CropUnitY} * ( \text{frame\_crop\_top\_offset} + \text{frame\_crop\_bottom\_offset} ) \end{aligned} \tag{7-24}$$ + +The frame cropping rectangle contains luma samples with horizontal frame coordinates from $\text{CropUnitX} * \text{frame\_crop\_left\_offset}$ to $\text{PicWidthInSamples} - ( \text{CropUnitX} * \text{frame\_crop\_right\_offset} + 1 )$ and vertical frame coordinates from $\text{CropUnitY} * \text{frame\_crop\_top\_offset}$ to $( 16 * \text{FrameHeightInMbs} ) - ( \text{CropUnitY} * \text{frame\_crop\_bottom\_offset} + 1 )$ , inclusive. The value of **frame\_crop\_left\_offset** shall be in the range of 0 to $( \text{PicWidthInSamples} / \text{CropUnitX} ) - ( \text{frame\_crop\_right\_offset} + 1 )$ , inclusive; and the value of **frame\_crop\_top\_offset** shall be in the range of 0 to $( 16 * \text{FrameHeightInMbs} / \text{CropUnitY} ) - ( \text{frame\_crop\_bottom\_offset} + 1 )$ , inclusive. + +When **frame\_cropping\_flag** is equal to 0, the values of **frame\_crop\_left\_offset**, **frame\_crop\_right\_offset**, **frame\_crop\_top\_offset**, and **frame\_crop\_bottom\_offset** shall be inferred to be equal to 0. + +When ChromaArrayType is not equal to 0, the corresponding specified samples of the two chroma arrays are the samples having frame coordinates $( x / \text{SubWidthC}, y / \text{SubHeightC} )$ , where $( x, y )$ are the frame coordinates of the specified luma samples. + +For decoded fields, the specified samples of the decoded field are the samples that fall within the rectangle specified in frame coordinates. + +**vui\_parameters\_present\_flag** equal to 1 specifies that the **vui\_parameters()** syntax structure as specified in Annex E is present. **vui\_parameters\_present\_flag** equal to 0 specifies that the **vui\_parameters()** syntax structure as specified in Annex E is not present. + +#### 7.4.2.1.1.1 Scaling list semantics + +**delta\_scale** is used to derive the j-th element of the scaling list for j in the range of 0 to $\text{sizeOfScalingList} - 1$ , inclusive. The value of **delta\_scale** shall be in the range of -128 to +127, inclusive. + +When **useDefaultScalingMatrixFlag** is derived to be equal to 1, the scaling list shall be inferred to be equal to the default scaling list as specified in Table 7-2. + +#### 7.4.2.1.2 Sequence parameter set extension RBSP semantics + +**seq\_parameter\_set\_id** identifies the sequence parameter set associated with the sequence parameter set extension. The value of **seq\_parameter\_set\_id** shall be in the range of 0 to 31, inclusive. + +**aux\_format\_idc** equal to 0 indicates that there are no auxiliary coded pictures in the coded video sequence. **aux\_format\_idc** equal to 1 indicates that exactly one auxiliary coded picture is present in each access unit of the coded video sequence, and that for alpha blending purposes the decoded samples of the associated primary coded picture in each access unit should be multiplied by the interpretation sample values of the auxiliary coded picture in the access unit in the display process after output from the decoding process. **aux\_format\_idc** equal to 2 indicates that exactly one auxiliary coded picture exists in each access unit of the coded video sequence, and that for alpha blending purposes the decoded samples of the associated primary coded picture in each access unit should not be multiplied by the interpretation sample values of the auxiliary coded picture in the access unit in the display process after output from the decoding process. **aux\_format\_idc** equal to 3 indicates that exactly one auxiliary coded picture exists in each access unit of the coded video sequence, and that the usage of the auxiliary coded pictures is unspecified. The value of **aux\_format\_idc** shall be in the range of 0 to 3, inclusive. Values greater than 3 for **aux\_format\_idc** are reserved to indicate the presence of exactly one auxiliary coded picture in each access unit of the coded video sequence for purposes to be specified in the future by ITU-T | ISO/IEC. When **aux\_format\_idc** is not present, it shall be inferred to be equal to 0. + +NOTE 1 – Decoders are not required to decode auxiliary coded pictures. + +**bit\_depth\_aux\_minus8** specifies the bit depth of the samples of the sample array of the auxiliary coded picture. **bit\_depth\_aux\_minus8** shall be in the range of 0 to 4, inclusive. + +**alpha\_incr\_flag** equal to 0 indicates that the interpretation sample value for each decoded auxiliary coded picture sample value is equal to the decoded auxiliary coded picture sample value for purposes of alpha blending. **alpha\_incr\_flag** equal to 1 indicates that, for purposes of alpha blending, after decoding the auxiliary coded picture samples, any auxiliary coded picture sample value that is greater than $\text{Min}(\text{alpha\_opaque\_value}, \text{alpha\_transparent\_value})$ should be increased by one to obtain the interpretation sample value for the auxiliary coded picture sample, and any auxiliary coded picture sample value that is less than or equal to $\text{Min}(\text{alpha\_opaque\_value}, \text{alpha\_transparent\_value})$ should be used without alteration as the interpretation sample value for the decoded auxiliary coded picture sample value. + +**alpha\_opaque\_value** specifies the interpretation sample value of an auxiliary coded picture sample for which the associated luma and chroma samples of the same access unit are considered opaque for purposes of alpha blending. The number of bits used for the representation of the **alpha\_opaque\_value** syntax element is **bit\_depth\_aux\_minus8** + 9 bits. + +**alpha\_transparent\_value** specifies the interpretation sample value of an auxiliary coded picture sample for which the associated luma and chroma samples of the same access unit are considered transparent for purposes of alpha blending. The number of bits used for the representation of the **alpha\_transparent\_value** syntax element is **bit\_depth\_aux\_minus8** + 9 bits. + +When **alpha\_incr\_flag** is equal to 1, **alpha\_transparent\_value** shall not be equal to **alpha\_opaque\_value** and $\text{Log2}(\text{Abs}(\text{alpha\_opaque\_value} - \text{alpha\_transparent\_value}))$ shall have an integer value. A value of **alpha\_transparent\_value** that is equal to **alpha\_opaque\_value** indicates that the auxiliary coded picture is not intended for alpha blending purposes. + +NOTE 2 – For alpha blending purposes, **alpha\_opaque\_value** may be greater than **alpha\_transparent\_value**, or it may be less than **alpha\_transparent\_value**. Interpretation sample values should be clipped to the range of **alpha\_opaque\_value** to **alpha\_transparent\_value**, inclusive. + +The decoding of the sequence parameter set extension and the decoding of auxiliary coded pictures is not required for conformance with this Recommendation | International Standard. + +The syntax of each coded slice of an auxiliary coded picture shall obey the same constraints as a coded slice of a redundant picture, with the following differences of constraints: + +- a) In regard to whether the primary coded picture is an IDR picture, the following applies: + - If the primary coded picture is an IDR picture, the auxiliary coded slice syntax shall correspond to that of a slice having **nal\_unit\_type** equal to 5 (a slice of an IDR picture). + - Otherwise (the primary coded picture is not an IDR picture), the auxiliary coded slice syntax shall correspond to that of a slice having **nal\_unit\_type** equal to 1 (a slice of a non-IDR picture). +- b) The slices of an auxiliary coded picture (when present) shall contain all macroblocks corresponding to those of the primary coded picture. +- c) **redundant\_pic\_cnt** shall be equal to 0 in all auxiliary coded slices. + +The (optional) decoding process for the decoding of auxiliary coded pictures is the same as if the auxiliary coded pictures were primary coded pictures in a separate coded video stream that differs from the primary coded pictures in the current coded video stream in the following ways: + +- The IDR or non-IDR status of each auxiliary coded picture shall be inferred to be the same as the IDR or non-IDR status of the primary picture in the same access unit, rather than being inferred from the value of **nal\_unit\_type**. + +- The value of `chroma_format_idc` and the value of `ChromaArrayType` shall be inferred to be equal to 0 for the decoding of the auxiliary coded pictures. +- The value of `bit_depth_luma_minus8` shall be inferred to be equal to `bit_depth_aux_minus8` for the decoding of the auxiliary coded pictures. + +NOTE 3 – Alpha blending composition is normally performed with a background picture B, a foreground picture F, and a decoded auxiliary coded picture A, all of the same size. Assume for purposes of example illustration that the chroma resolution of B and F have been upsampled to the same resolution as the luma. Denote corresponding samples of B, F and A by `b`, `f` and `a`, respectively. Denote luma and chroma samples by subscripts `Y`, `Cb` and `Cr`. + +Define the variables `alphaRange`, `alphaFwt` and `alphaBwt` as follows: + +$$\text{alphaRange} = \text{Abs}(\text{alpha\_opaque\_value} - \text{alpha\_transparent\_value})$$ + +$$\text{alphaFwt} = \text{Abs}(\text{a} - \text{alpha\_transparent\_value})$$ + +$$\text{alphaBwt} = \text{Abs}(\text{a} - \text{alpha\_opaque\_value})$$ + +Then, in alpha blending composition, samples `d` of the displayed picture D may be calculated as + +$$d_Y = (\text{alphaFwt} * f_Y + \text{alphaBwt} * b_Y + \text{alphaRange} / 2) / \text{alphaRange}$$ + +$$d_{Cb} = (\text{alphaFwt} * f_{Cb} + \text{alphaBwt} * b_{Cb} + \text{alphaRange} / 2) / \text{alphaRange}$$ + +$$d_{Cr} = (\text{alphaFwt} * f_{Cr} + \text{alphaBwt} * b_{Cr} + \text{alphaRange} / 2) / \text{alphaRange}$$ + +The samples of pictures D, F and B could also represent red, green, and blue component values (see clause E.2.1). Here we have assumed `Y`, `Cb` and `Cr` component values. Each component, e.g., `Y`, is assumed for purposes of example illustration above to have the same bit depth in each of the pictures D, F and B. However, different components, e.g., `Y` and `Cb`, need not have the same bit depth in this example. + +When `aux_format_idc` is equal to 1, F would be the decoded picture obtained from the decoded luma and chroma, and A would be the decoded picture obtained from the decoded auxiliary coded picture. In this case, the indicated example alpha blending composition involves multiplying the samples of F by factors obtained from the samples of A. + +A picture format that is useful for editing or direct viewing, and that is commonly used, is called pre-multiplied-black video. If the foreground picture was F, then the pre-multiplied-black video S is given by + +$$s_Y = (\text{alphaFwt} * f_Y) / \text{alphaRange}$$ + +$$s_{Cb} = (\text{alphaFwt} * f_{Cb}) / \text{alphaRange}$$ + +$$s_{Cr} = (\text{alphaFwt} * f_{Cr}) / \text{alphaRange}$$ + +Pre-multiplied-black video has the characteristic that the picture S will appear correct if displayed against a black background. For a non-black background B, the composition of the displayed picture D may be calculated as + +$$d_Y = s_Y + (\text{alphaBwt} * b_Y + \text{alphaRange} / 2) / \text{alphaRange}$$ + +$$d_{Cb} = s_{Cb} + (\text{alphaBwt} * b_{Cb} + \text{alphaRange} / 2) / \text{alphaRange}$$ + +$$d_{Cr} = s_{Cr} + (\text{alphaBwt} * b_{Cr} + \text{alphaRange} / 2) / \text{alphaRange}$$ + +When `aux_format_idc` is equal to 2, S would be the decoded picture obtained from the decoded luma and chroma, and A would again be the decoded picture obtained from the decoded auxiliary coded picture. In this case, alpha blending composition does not involve multiplication of the samples of S by factors obtained from the samples of A. + +**additional\_extension\_flag** equal to 0 indicates that no additional data follows within the sequence parameter set extension syntax structure prior to the RBSP trailing bits. The value of `additional_extension_flag` shall be equal to 0. The value of 1 for `additional_extension_flag` is reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all data that follows the value of 1 for `additional_extension_flag` in a sequence parameter set extension NAL unit. + +#### 7.4.2.1.3 Subset sequence parameter set RBSP semantics + +**svc\_vui\_parameters\_present\_flag** equal to 0 specifies that the syntax structure `svc_vui_parameters_extension()` is not present. `svc_vui_parameters_present_flag` equal to 1 specifies that the syntax structure `svc_vui_parameters_extension()` is present. + +**bit\_equal\_to\_one** shall be equal to 1. + +**mvc\_vui\_parameters\_present\_flag** equal to 0 specifies that the syntax structure `mvc_vui_parameters_extension()` is not present. `mvc_vui_parameters_present_flag` equal to 1 specifies that the syntax structure `mvc_vui_parameters_extension()` is present. + +**additional\_extension2\_flag** equal to 0 specifies that no `additional_extension2_data_flag` syntax elements are present in the subset sequence parameter set RBSP syntax structure. `additional_extension2_flag` shall be equal to 0 in bitstreams conforming to this Recommendation | International Standard. The value of 1 for `additional_extension2_flag` is reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all data that follow the value 1 for `additional_extension2_flag` in a subset sequence parameter set NAL unit. + +**additional\_extension2\_data\_flag** may have any value. It shall not affect the conformance to profiles specified in Annex A, F, G, or H. + +#### 7.4.2.2 Picture parameter set RBSP semantics + +**pic\_parameter\_set\_id** identifies the picture parameter set that is referred to in the slice header. The value of **pic\_parameter\_set\_id** shall be in the range of 0 to 255, inclusive. + +**seq\_parameter\_set\_id** refers to the active sequence parameter set. The value of **seq\_parameter\_set\_id** shall be in the range of 0 to 31, inclusive. + +**entropy\_coding\_mode\_flag** selects the entropy decoding method to be applied for the syntax elements for which two descriptors appear in the syntax tables as follows: + +- If **entropy\_coding\_mode\_flag** is equal to 0, the method specified by the left descriptor in the syntax table is applied (Exp-Golomb coded, see clause 9.1 or CAVLC, see clause 9.2). +- Otherwise (**entropy\_coding\_mode\_flag** is equal to 1), the method specified by the right descriptor in the syntax table is applied (CABAC, see clause 9.3). + +**bottom\_field\_pic\_order\_in\_frame\_present\_flag** equal to 1 specifies that the syntax elements **delta\_pic\_order\_cnt\_bottom** (when **pic\_order\_cnt\_type** is equal to 0) or **delta\_pic\_order\_cnt[ 1 ]** (when **pic\_order\_cnt\_type** is equal to 1), which are related to picture order counts for the bottom field of a coded frame, are present in the slice headers for coded frames as specified in clause 7.3.3. **bottom\_field\_pic\_order\_in\_frame\_present\_flag** equal to 0 specifies that the syntax elements **delta\_pic\_order\_cnt\_bottom** and **delta\_pic\_order\_cnt[ 1 ]** are not present in the slice headers. + +**num\_slice\_groups\_minus1** plus 1 specifies the number of slice groups for a picture. When **num\_slice\_groups\_minus1** is equal to 0, all slices of the picture belong to the same slice group. The allowed range of **num\_slice\_groups\_minus1** is specified in Annex A. + +**slice\_group\_map\_type** specifies how the mapping of slice group map units to slice groups is coded. The value of **slice\_group\_map\_type** shall be in the range of 0 to 6, inclusive. + +**slice\_group\_map\_type** equal to 0 specifies interleaved slice groups. + +**slice\_group\_map\_type** equal to 1 specifies a dispersed slice group mapping. + +**slice\_group\_map\_type** equal to 2 specifies one or more "foreground" slice groups and a "leftover" slice group. + +**slice\_group\_map\_type** values equal to 3, 4, and 5 specify changing slice groups. When **num\_slice\_groups\_minus1** is not equal to 1, **slice\_group\_map\_type** shall not be equal to 3, 4, or 5. + +**slice\_group\_map\_type** equal to 6 specifies an explicit assignment of a slice group to each slice group map unit. + +Slice group map units are specified as follows: + +- If **frame\_mbs\_only\_flag** is equal to 0 and **mb\_adaptive\_frame\_field\_flag** is equal to 1 and the coded picture is a frame, the slice group map units are macroblock pair units. +- Otherwise, if **frame\_mbs\_only\_flag** is equal to 1 or the coded picture is a field, the slice group map units are units of macroblocks. +- Otherwise (**frame\_mbs\_only\_flag** is equal to 0 and **mb\_adaptive\_frame\_field\_flag** is equal to 0 and the coded picture is a frame), the slice group map units are units of two macroblocks that are vertically contiguous as in a frame macroblock pair of an MBAFF frame. + +**run\_length\_minus1[ i ]** is used to specify the number of consecutive slice group map units to be assigned to the i-th slice group in raster scan order of slice group map units. The value of **run\_length\_minus1[ i ]** shall be in the range of 0 to **PicSizeInMapUnits** – 1, inclusive. + +**top\_left[ i ]** and **bottom\_right[ i ]** specify the top-left and bottom-right corners of a rectangle, respectively. **top\_left[ i ]** and **bottom\_right[ i ]** are slice group map unit positions in a raster scan of the picture for the slice group map units. For each rectangle i, all of the following constraints shall be obeyed by the values of the syntax elements **top\_left[ i ]** and **bottom\_right[ i ]**: + +- **top\_left[ i ]** shall be less than or equal to **bottom\_right[ i ]** and **bottom\_right[ i ]** shall be less than **PicSizeInMapUnits**. +- $( \text{top\_left[ i ]} \% \text{PicWidthInMbs} )$ shall be less than or equal to the value of $( \text{bottom\_right[ i ]} \% \text{PicWidthInMbs} )$ . + +**slice\_group\_change\_direction\_flag** is used with **slice\_group\_map\_type** to specify the refined map type when **slice\_group\_map\_type** is 3, 4, or 5. + +**slice\_group\_change\_rate\_minus1** is used to specify the variable **SliceGroupChangeRate**. **SliceGroupChangeRate** specifies the multiple in number of slice group map units by which the size of a slice group can change from one picture + +to the next. The value of `slice_group_change_rate_minus1` shall be in the range of 0 to `PicSizeInMapUnits - 1`, inclusive. The `SliceGroupChangeRate` variable is specified as follows: + +$$\text{SliceGroupChangeRate} = \text{slice\_group\_change\_rate\_minus1} + 1 \quad (7-25)$$ + +**pic\_size\_in\_map\_units\_minus1** is used to specify the number of slice group map units in the picture. `pic_size_in_map_units_minus1` shall be equal to `PicSizeInMapUnits - 1`. + +**slice\_group\_id[ i ]** identifies a slice group of the i-th slice group map unit in raster scan order. The length of the `slice_group_id[ i ]` syntax element is $\text{Ceil}(\text{Log2}(\text{num\_slice\_groups\_minus1} + 1))$ bits. The value of `slice_group_id[ i ]` shall be in the range of 0 to `num_slice_groups_minus1`, inclusive. + +**num\_ref\_idx\_l0\_default\_active\_minus1** specifies how `num_ref_idx_l0_active_minus1` is inferred for P, SP, and B slices with `num_ref_idx_active_override_flag` equal to 0. The value of `num_ref_idx_l0_default_active_minus1` shall be in the range of 0 to 31, inclusive. + +**num\_ref\_idx\_l1\_default\_active\_minus1** specifies how `num_ref_idx_l1_active_minus1` is inferred for B slices with `num_ref_idx_active_override_flag` equal to 0. The value of `num_ref_idx_l1_default_active_minus1` shall be in the range of 0 to 31, inclusive. + +**weighted\_pred\_flag** equal to 0 specifies that the default weighted prediction shall be applied to P and SP slices. `weighted_pred_flag` equal to 1 specifies that explicit weighted prediction shall be applied to P and SP slices. + +**weighted\_bipred\_idc** equal to 0 specifies that the default weighted prediction shall be applied to B slices. `weighted_bipred_idc` equal to 1 specifies that explicit weighted prediction shall be applied to B slices. `weighted_bipred_idc` equal to 2 specifies that implicit weighted prediction shall be applied to B slices. The value of `weighted_bipred_idc` shall be in the range of 0 to 2, inclusive. + +**pic\_init\_qp\_minus26** specifies the initial value minus 26 of `SliceQPV` for each slice. The initial value is modified at the slice layer when a non-zero value of `slice_qp_delta` is decoded, and is modified further when a non-zero value of `mb_qp_delta` is decoded at the macroblock layer. The value of `pic_init_qp_minus26` shall be in the range of $-(26 + \text{QpBdOffset}_V)$ to $+25$ , inclusive. + +**pic\_init\_qs\_minus26** specifies the initial value minus 26 of `SliceQSV` for all macroblocks in SP or SI slices. The initial value is modified at the slice layer when a non-zero value of `slice_qs_delta` is decoded. The value of `pic_init_qs_minus26` shall be in the range of $-26$ to $+25$ , inclusive. + +**chroma\_qp\_index\_offset** specifies the offset that shall be added to `QPV` and `QSV` for addressing the table of `QPC` values for the Cb chroma component. The value of `chroma_qp_index_offset` shall be in the range of $-12$ to $+12$ , inclusive. + +**deblocking\_filter\_control\_present\_flag** equal to 1 specifies that a set of syntax elements controlling the characteristics of the deblocking filter is present in the slice header. `deblocking_filter_control_present_flag` equal to 0 specifies that the set of syntax elements controlling the characteristics of the deblocking filter is not present in the slice headers and their inferred values are in effect. + +**constrained\_intra\_pred\_flag** equal to 0 specifies that intra prediction allows usage of residual data and decoded samples of neighbouring macroblocks coded using Inter macroblock prediction modes for the prediction of macroblocks coded using Intra macroblock prediction modes. `constrained_intra_pred_flag` equal to 1 specifies constrained intra prediction, in which case prediction of macroblocks coded using Intra macroblock prediction modes only uses residual data and decoded samples from I or SI macroblock types. + +**redundant\_pic\_cnt\_present\_flag** equal to 0 specifies that the `redundant_pic_cnt` syntax element is not present in slice headers, coded slice data partition B NAL units, and coded slice data partition C NAL units that refer (either directly or by association with a corresponding coded slice data partition A NAL unit) to the picture parameter set. `redundant_pic_cnt_present_flag` equal to 1 specifies that the `redundant_pic_cnt` syntax element is present in all slice headers, coded slice data partition B NAL units, and coded slice data partition C NAL units that refer (either directly or by association with a corresponding coded slice data partition A NAL unit) to the picture parameter set. + +**transform\_8x8\_mode\_flag** equal to 1 specifies that the 8x8 transform decoding process may be in use (see clause 8.5). `transform_8x8_mode_flag` equal to 0 specifies that the 8x8 transform decoding process is not in use. When `transform_8x8_mode_flag` is not present, it shall be inferred to be 0. + +**pic\_scaling\_matrix\_present\_flag** equal to 1 specifies that parameters are present to modify the scaling lists specified in the sequence parameter set. `pic_scaling_matrix_present_flag` equal to 0 specifies that the scaling lists used for the picture shall be inferred to be equal to those specified by the sequence parameter set. When `pic_scaling_matrix_present_flag` is not present, it shall be inferred to be equal to 0. + +**pic\_scaling\_list\_present\_flag[ i ]** equal to 1 specifies that the scaling list syntax structure is present to specify the scaling list for index i. pic\_scaling\_list\_present\_flag[ i ] equal to 0 specifies that the syntax structure for scaling list i is not present in the picture parameter set and that depending on the value of seq\_scaling\_matrix\_present\_flag, the following applies: + +- If seq\_scaling\_matrix\_present\_flag is equal to 0, the scaling list fall-back rule set A as specified in Table 7-2 shall be used to derive the picture-level scaling list for index i. +- Otherwise (seq\_scaling\_matrix\_present\_flag is equal to 1), the scaling list fall-back rule set B as specified in Table 7-2 shall be used to derive the picture-level scaling list for index i. + +**second\_chroma\_qp\_index\_offset** specifies the offset that shall be added to QPV and QPS for addressing the table of QPC values for the Cr chroma component. The value of second\_chroma\_qp\_index\_offset shall be in the range of –12 to +12, inclusive. + +When second\_chroma\_qp\_index\_offset is not present, it shall be inferred to be equal to chroma\_qp\_index\_offset. + +NOTE – When ChromaArrayType is equal to 0, the values of bit\_depth\_chroma\_minus8, chroma\_qp\_index\_offset and second\_chroma\_qp\_index\_offset are not used in the decoding process. In particular, when separate\_colour\_plane\_flag is equal to 1, each colour plane is decoded as a distinct monochrome picture using the luma component decoding process (except for the selection of scaling matrices), including the application of the luma quantization parameter derivation process without application of an offset for the decoding of the pictures having colour\_plane\_id not equal to 0. + +#### 7.4.2.3 Supplemental enhancement information RBSP semantics + +Supplemental Enhancement Information (SEI) contains information that is not necessary to decode the samples of coded pictures from VCL NAL units. + +##### 7.4.2.3.1 Supplemental enhancement information message semantics + +An SEI RBSP contains one or more SEI messages. Each SEI message consists of the variables specifying the type payloadType and size payloadSize of the SEI payload. SEI payloads are specified in Annex D. The derived SEI payload size payloadSize is specified in bytes and shall be equal to the number of RBSP bytes in the SEI payload. + +NOTE – The NAL unit byte sequence containing the SEI message might include one or more emulation prevention bytes (represented by emulation\_prevention\_three\_byte syntax elements). Since the payload size of an SEI message is specified in RBSP bytes, the quantity of emulation prevention bytes is not included in the size payloadSize of an SEI payload. + +**ff\_byte** is a byte equal to 0xFF identifying a need for a longer representation of the syntax structure that it is used within. + +**last\_payload\_type\_byte** is the last byte of the payload type of an SEI message. + +**last\_payload\_size\_byte** is the last byte of the payload size of an SEI message. + +#### 7.4.2.4 Access unit delimiter RBSP semantics + +The access unit delimiter may be used to indicate the type of slices present in a primary coded picture and to simplify the detection of the boundary between access units. There is no normative decoding process associated with the access unit delimiter. + +**primary\_pic\_type** indicates that the slice\_type values for all slices of the primary coded picture are members of the set listed in Table 7-5 for the given value of primary\_pic\_type. + +NOTE – The value of primary\_pic\_type applies to the slice\_type values in all slice headers of the primary coded picture, including the slice\_type syntax elements in all NAL units with nal\_unit\_type equal to 1, 2, or 5. + +**Table 7-5 – Meaning of primary\_pic\_type** + +| primary_pic_type | slice_type values that may be present in the primary coded picture | +|-------------------------|---------------------------------------------------------------------------| +| 0 | 2, 7 | +| 1 | 0, 2, 5, 7 | +| 2 | 0, 1, 2, 5, 6, 7 | +| 3 | 4, 9 | +| 4 | 3, 4, 8, 9 | +| 5 | 2, 4, 7, 9 | +| 6 | 0, 2, 3, 4, 5, 7, 8, 9 | +| 7 | 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 | + +#### 7.4.2.5 End of sequence RBSP semantics + +The end of sequence RBSP specifies that the next subsequent access unit in the bitstream in decoding order (if any) shall be an IDR access unit. The syntax content of the SODB and RBSP for the end of sequence RBSP are empty. No normative decoding process is specified for an end of sequence RBSP. + +#### 7.4.2.6 End of stream RBSP semantics + +The end of stream RBSP indicates that no additional NAL units shall be present in the bitstream that are subsequent to the end of stream RBSP in decoding order. The syntax content of the SODB and RBSP for the end of stream RBSP are empty. No normative decoding process is specified for an end of stream RBSP. + +NOTE – When an end of stream NAL unit is present, the bitstream is considered to end (for purposes of the scope of this Recommendation | International Standard). In some system environments, another bitstream may follow after the bitstream that has ended, either immediately or at some time thereafter, possibly within the same communication channel. Under such circumstances, the scope of this Recommendation | International Standard applies only to the processing of each of these individual bitstreams. No requirements are specified herein regarding the transition between such bitstreams (e.g., in regard to timing, buffering operation, etc.). + +#### 7.4.2.7 Filler data RBSP semantics + +The filler data RBSP contains zero or more bytes. No normative decoding process is specified for a filler data RBSP. + +**ff\_byte** is a byte. It is a requirement of bitstream conformance that the value of ff\_byte shall be equal to 0xFF. + +#### 7.4.2.8 Slice layer without partitioning RBSP semantics + +The slice layer without partitioning RBSP consists of a slice header and slice data. + +#### 7.4.2.9 Slice data partition RBSP semantics + +##### 7.4.2.9.1 Slice data partition A RBSP semantics + +When slice data partitioning is in use, the coded data for a single slice is divided into three separate partitions. Slice data partition A contains all syntax elements of category 2. + +Category 2 syntax elements include all syntax elements in the slice header and slice data syntax structures other than the syntax elements in the residual( ) syntax structure. + +**slice\_id** identifies the slice associated with the slice data partition. The value of slice\_id is constrained as follows: + +- If separate\_colour\_plane\_flag is equal to 0, the following applies: + - If arbitrary slice order is not allowed as specified in Annex A, the first slice of a coded picture, in decoding order, shall have slice\_id equal to 0 and the value of slice\_id shall be incremented by one for each subsequent slice of the coded picture in decoding order. + - Otherwise (arbitrary slice order is allowed), each slice shall have a unique slice\_id value within the set of slices of the coded picture. +- Otherwise (separate\_colour\_plane\_flag is equal to 1), the following applies: + - If arbitrary slice order is not allowed as specified in Annex A, the first slice of a coded picture having each value of colour\_plane\_id, in decoding order, shall have slice\_id equal to 0 and the value of slice\_id shall be incremented by one for each subsequent slice of the coded picture having the same value of colour\_plane\_id, in decoding order. + +- Otherwise (arbitrary slice order is allowed) each slice shall have a unique `slice_id` value within each set of slices of the coded picture that have the same value of `colour_plane_id`. + +The range of `slice_id` is specified as follows: + +- If `MbaffFrameFlag` is equal to 0, `slice_id` shall be in the range of 0 to `PicSizeInMbs` – 1, inclusive. +- Otherwise (`MbaffFrameFlag` is equal to 1), `slice_id` shall be in the range of 0 to `PicSizeInMbs` / 2 – 1, inclusive. + +#### 7.4.2.9.2 Slice data partition B RBSP semantics + +When slice data partitioning is in use, the coded data for a single slice is divided into one to three separate partitions. Slice data partition B contains all syntax elements of category 3. + +Category 3 syntax elements include all syntax elements in the `residual()` syntax structure and in syntax structures used within that syntax structure for collective macroblock types I and SI as specified in Table 7-10. + +**`slice_id`** has the same semantics as specified in clause 7.4.2.9.1. + +**`colour_plane_id`** specifies the colour plane associated with the current slice RBSP when `separate_colour_plane_flag` is equal to 1. The value of `colour_plane_id` shall be in the range of 0 to 2, inclusive. `colour_plane_id` equal to 0, 1, and 2 correspond to the Y, Cb, and Cr planes, respectively. + +NOTE – There is no dependency between the decoding processes of pictures having different values of `colour_plane_id`. + +**`redundant_pic_cnt`** shall be equal to 0 for coded slices and coded slice data partitions belonging to the primary coded picture. The `redundant_pic_cnt` shall be greater than 0 for coded slices and coded slice data partitions in redundant coded pictures. When `redundant_pic_cnt` is not present, its value shall be inferred to be equal to 0. The value of `redundant_pic_cnt` shall be in the range of 0 to 127, inclusive. + +The presence of a slice data partition B RBSP is specified as follows: + +- If the syntax elements of a slice data partition A RBSP indicate the presence of any syntax elements of category 3 in the slice data for a slice, a slice data partition B RBSP shall be present having the same value of `slice_id` and `redundant_pic_cnt` as in the slice data partition A RBSP. +- Otherwise (the syntax elements of a slice data partition A RBSP do not indicate the presence of any syntax elements of category 3 in the slice data for a slice), no slice data partition B RBSP shall be present having the same value of `slice_id` and `redundant_pic_cnt` as in the slice data partition A RBSP. + +#### 7.4.2.9.3 Slice data partition C RBSP semantics + +When slice data partitioning is in use, the coded data for a single slice is divided into three separate partitions. Slice data partition C contains all syntax elements of category 4. + +Category 4 syntax elements include all syntax elements in the `residual()` syntax structure and in syntax structures used within that syntax structure for collective macroblock types P and B as specified in Table 7-10. + +**`slice_id`** has the same semantics as specified in clause 7.4.2.9.1. + +**`colour_plane_id`** has the same semantics as specified in clause 7.4.2.9.2. + +**`redundant_pic_cnt`** has the same semantics as specified in clause 7.4.2.9.2. + +The presence of a slice data partition C RBSP is specified as follows: + +- If the syntax elements of a slice data partition A RBSP indicate the presence of any syntax elements of category 4 in the slice data for a slice, a slice data partition C RBSP shall be present having the same value of `slice_id` and `redundant_pic_cnt` as in the slice data partition A RBSP. +- Otherwise (the syntax elements of a slice data partition A RBSP do not indicate the presence of any syntax elements of category 4 in the slice data for a slice), no slice data partition C RBSP shall be present having the same value of `slice_id` and `redundant_pic_cnt` as in the slice data partition A RBSP. + +#### 7.4.2.10 RBSP slice trailing bits semantics + +**`cabac_zero_word`** is a byte-aligned sequence of two bytes equal to 0x0000. + +Let `NumBytesInVclNALUnits` be the sum of the values of `NumBytesInNALUnit` for all VCL NAL units of a coded picture. + +Let `BinCountsInNALUnits` be the number of times that the parsing process function `DecodeBin()`, specified in clause 9.3.3.2, is invoked to decode the contents of all VCL NAL units of a coded picture. When + +entropy\_coding\_mode\_flag is equal to 1, it is a requirement of bitstream conformance that BinCountsInNALUnits shall not exceed $( 32 \div 3 ) * \text{NumBytesInVclNALUnits} + ( \text{RawMbBits} * \text{PicSizeInMbs} ) \div 32$ . + +NOTE – The constraint on the maximum number of bins resulting from decoding the contents of the slice layer NAL units can be met by inserting a number of cabac\_zero\_word syntax elements to increase the value of NumBytesInVclNALUnits. Each cabac\_zero\_word is represented in a NAL unit by the three-byte sequence 0x000003 (as a result of the constraints on NAL unit contents that result in requiring inclusion of an emulation\_prevention\_three\_byte for each cabac\_zero\_word). + +#### 7.4.2.11 RBSP trailing bits semantics + +rbsp\_stop\_one\_bit shall be equal to 1. + +rbsp\_alignment\_zero\_bit shall be equal to 0. + +#### 7.4.2.12 Prefix NAL unit RBSP semantics + +The content of the prefix NAL unit RBSP is dependent on the value of svc\_extension\_flag. + +#### 7.4.2.13 Slice layer extension RBSP semantics + +The content of the slice layer extension RBSP is dependent on the value of svc\_extension\_flag. + +Coded slice extension NAL units with svc\_extension\_flag equal to 1 are also referred to as coded slice in scalable extension NAL units and coded slice extension NAL units with svc\_extension\_flag equal to 0 are also referred to as coded slice MVC extension NAL units. + +### 7.4.3 Slice header semantics + +When present, the value of the slice header syntax elements pic\_parameter\_set\_id, frame\_num, field\_pic\_flag, bottom\_field\_flag, idr\_pic\_id, pic\_order\_cnt\_lsb, delta\_pic\_order\_cnt\_bottom, delta\_pic\_order\_cnt[ 0 ], delta\_pic\_order\_cnt[ 1 ], sp\_for\_switch\_flag, and slice\_group\_change\_cycle shall be the same in all slice headers of a coded picture. + +**first\_mb\_in\_slice** specifies the address of the first macroblock in the slice. When arbitrary slice order is not allowed as specified in Annex A, the value of first\_mb\_in\_slice is constrained as follows: + +- If separate\_colour\_plane\_flag is equal to 0, the value of first\_mb\_in\_slice shall not be less than the value of first\_mb\_in\_slice for any other slice of the current picture that precedes the current slice in decoding order. +- Otherwise (separate\_colour\_plane\_flag is equal to 1), the value of first\_mb\_in\_slice shall not be less than the value of first\_mb\_in\_slice for any other slice of the current picture that precedes the current slice in decoding order and has the same value of colour\_plane\_id. + +The first macroblock address of the slice is derived as follows: + +- If MbaaffFrameFlag is equal to 0, first\_mb\_in\_slice is the macroblock address of the first macroblock in the slice, and first\_mb\_in\_slice shall be in the range of 0 to PicSizeInMbs – 1, inclusive. +- Otherwise (MbaaffFrameFlag is equal to 1), first\_mb\_in\_slice \* 2 is the macroblock address of the first macroblock in the slice, which is the top macroblock of the first macroblock pair in the slice, and first\_mb\_in\_slice shall be in the range of 0 to PicSizeInMbs / 2 – 1, inclusive. + +**slice\_type** specifies the coding type of the slice according to Table 7-6. + +**Table 7-6 – Name association to slice\_type** + +| slice_type | Name of slice_type | +|------------|--------------------| +| 0 | P (P slice) | +| 1 | B (B slice) | +| 2 | I (I slice) | +| 3 | SP (SP slice) | +| 4 | SI (SI slice) | +| 5 | P (P slice) | +| 6 | B (B slice) | +| 7 | I (I slice) | +| 8 | SP (SP slice) | +| 9 | SI (SI slice) | + +When `slice_type` has a value in the range 5..9, it is a requirement of bitstream conformance that all other slices of the current coded picture shall have a value of `slice_type` equal to the current value of `slice_type` or equal to the current value of `slice_type` minus 5. + +NOTE 1 – Values of `slice_type` in the range 5..9 can be used by an encoder to indicate that all slices of a picture have the same value of (`slice_type` % 5). Values of `slice_type` in the range 5..9 are otherwise equivalent to corresponding values in the range 0..4. + +When `nal_unit_type` is equal to 5 (IDR picture), `slice_type` shall be equal to 2, 4, 7, or 9. + +When `max_num_ref_frames` is equal to 0, `slice_type` shall be equal to 2, 4, 7, or 9. + +**pic\_parameter\_set\_id** specifies the picture parameter set in use. The value of `pic_parameter_set_id` shall be in the range of 0 to 255, inclusive. + +**colour\_plane\_id** specifies the colour plane associated with the current slice RBSP when `separate_colour_plane_flag` is equal to 1. The value of `colour_plane_id` shall be in the range of 0 to 2, inclusive. `colour_plane_id` equal to 0, 1, and 2 correspond to the Y, Cb, and Cr planes, respectively. + +NOTE 2 – There is no dependency between the decoding processes of pictures having different values of `colour_plane_id`. + +**frame\_num** is used as an identifier for pictures and shall be represented by `log2_max_frame_num_minus4 + 4` bits in the bitstream. `frame_num` is constrained as follows: + +The variable `PrevRefFrameNum` is derived as follows: + +- If the current picture is an IDR picture, `PrevRefFrameNum` is set equal to 0. +- Otherwise (the current picture is not an IDR picture), `PrevRefFrameNum` is set as follows: + - If the decoding process for gaps in `frame_num` specified in clause 8.2.5.2 was invoked by the decoding process for an access unit that contained a non-reference picture that followed the previous access unit in decoding order that contained a reference picture, `PrevRefFrameNum` is set equal to the value of `frame_num` for the last of the "non-existing" reference frames inferred by the decoding process for gaps in `frame_num` specified in clause 8.2.5.2. + - Otherwise, `PrevRefFrameNum` is set equal to the value of `frame_num` for the previous access unit in decoding order that contained a reference picture. + +The value of `frame_num` is constrained as follows: + +- If the current picture is an IDR picture, `frame_num` shall be equal to 0. +- Otherwise (the current picture is not an IDR picture), referring to the primary coded picture in the previous access unit in decoding order that contains a reference picture as the preceding reference picture, the value of `frame_num` for the current picture shall not be equal to `PrevRefFrameNum` unless all of the following three conditions are true: + - a) The current picture and the preceding reference picture belong to consecutive access units in decoding order. + - b) The current picture and the preceding reference picture are reference fields having opposite parity. + - c) One or more of the following conditions is true: + - The preceding reference picture is an IDR picture, + - The preceding reference picture includes a `memory_management_control_operation` syntax element equal to 5, + - NOTE 3 – When the preceding reference picture includes a `memory_management_control_operation` syntax element equal to 5, `PrevRefFrameNum` is equal to 0. + - There is a primary coded picture that precedes the preceding reference picture and the primary coded picture that precedes the preceding reference picture does not have `frame_num` equal to `PrevRefFrameNum`, + - There is a primary coded picture that precedes the preceding reference picture and the primary coded picture that precedes the preceding reference picture is not a reference picture. + +When the value of `frame_num` is not equal to `PrevRefFrameNum`, it is a requirement of bitstream conformance that the following constraints shall be obeyed: + +- a) There shall not be any previous field or frame in decoding order that is currently marked as "used for short-term reference" that has a value of `frame_num` equal to any value taken on by the variable `UnusedShortTermFrameNum` in the following: + +$$\begin{aligned} +\text{UnusedShortTermFrameNum} &= ( \text{PrevRefFrameNum} + 1 ) \% \text{MaxFrameNum} \\ +\text{while}( \text{UnusedShortTermFrameNum} \neq \text{frame\_num} ) \\ +\text{UnusedShortTermFrameNum} &= ( \text{UnusedShortTermFrameNum} + 1 ) \% \text{MaxFrameNum} +\end{aligned} \tag{7-26}$$ + +b) The value of `frame_num` is constrained as follows: + +- If `gaps_in_frame_num_value_allowed_flag` is equal to 0, the value of `frame_num` for the current picture shall be equal to $( \text{PrevRefFrameNum} + 1 ) \% \text{MaxFrameNum}$ . +- Otherwise (`gaps_in_frame_num_value_allowed_flag` is equal to 1), the following applies: + - If `frame_num` is greater than `PrevRefFrameNum`, there shall not be any non-reference pictures in the bitstream that follow the previous reference picture and precede the current picture in decoding order in which either of the following conditions is true: + - The value of `frame_num` for the non-reference picture is less than `PrevRefFrameNum`, + - The value of `frame_num` for the non-reference picture is greater than the value of `frame_num` for the current picture. + - Otherwise (`frame_num` is less than `PrevRefFrameNum`), there shall not be any non-reference pictures in the bitstream that follow the previous reference picture and precede the current picture in decoding order in which both of the following conditions are true: + - The value of `frame_num` for the non-reference picture is less than `PrevRefFrameNum`, + - The value of `frame_num` for the non-reference picture is greater than the value of `frame_num` for the current picture. + +A picture including a `memory_management_control_operation` equal to 5 shall have `frame_num` constraints as described above and, after the decoding of the current picture and the processing of the memory management control operations, the picture shall be inferred to have had `frame_num` equal to 0 for all subsequent use in the decoding process, except as specified in clause 7.4.1.2.4. + +NOTE 4 – When the primary coded picture is not an IDR picture and does not contain `memory_management_control_operation` syntax element equal to 5, the value of `frame_num` of a corresponding redundant coded picture is the same as the value of `frame_num` in the primary coded picture. Alternatively, the redundant coded picture includes a `memory_management_control_operation` syntax element equal to 5 and the corresponding primary coded picture is an IDR picture. + +**field\_pic\_flag** equal to 1 specifies that the slice is a slice of a coded field. `field_pic_flag` equal to 0 specifies that the slice is a slice of a coded frame. When `field_pic_flag` is not present it shall be inferred to be equal to 0. + +The variable `MbaffFrameFlag` is derived as + +$$\text{MbaffFrameFlag} = ( \text{mb\_adaptive\_frame\_field\_flag} \&\& !\text{field\_pic\_flag} ) \tag{7-27}$$ + +The variable for the picture height in units of macroblocks is derived as + +$$\text{PicHeightInMbs} = \text{FrameHeightInMbs} / ( 1 + \text{field\_pic\_flag} ) \tag{7-28}$$ + +The variable for picture height for the luma component is derived as + +$$\text{PicHeightInSamples}_L = \text{PicHeightInMbs} * 16 \tag{7-29}$$ + +The variable for picture height for the chroma component is derived as + +$$\text{PicHeightInSamples}_C = \text{PicHeightInMbs} * \text{MbHeightC} \tag{7-30}$$ + +The variable `PicSizeInMbs` for the current picture is derived as + +$$\text{PicSizeInMbs} = \text{PicWidthInMbs} * \text{PicHeightInMbs} \tag{7-31}$$ + +The variable `MaxPicNum` is derived as follows: + +- If `field_pic_flag` is equal to 0, `MaxPicNum` is set equal to `MaxFrameNum`. +- Otherwise (`field_pic_flag` is equal to 1), `MaxPicNum` is set equal to $2 * \text{MaxFrameNum}$ . + +The variable `CurrPicNum` is derived as follows: + +- If `field_pic_flag` is equal to 0, `CurrPicNum` is set equal to `frame_num`. +- Otherwise (`field_pic_flag` is equal to 1), `CurrPicNum` is set equal to $2 * \text{frame\_num} + 1$ . + +**bottom\_field\_flag** equal to 1 specifies that the slice is part of a coded bottom field. **bottom\_field\_flag** equal to 0 specifies that the picture is a coded top field. When this syntax element is not present for the current slice, it shall be inferred to be equal to 0. + +**idr\_pic\_id** identifies an IDR picture. The values of **idr\_pic\_id** in all the slices of an IDR picture shall remain unchanged. When two consecutive access units in decoding order are both IDR access units, the value of **idr\_pic\_id** in the slices of the first such IDR access unit shall differ from the **idr\_pic\_id** in the second such IDR access unit. The value of **idr\_pic\_id** shall be in the range of 0 to 65535, inclusive. + +NOTE 5 – It is not prohibited for multiple IDR pictures in a bitstream to have the same value of **idr\_pic\_id** unless such pictures occur in two consecutive access units in decoding order. + +**pic\_order\_cnt\_lsb** specifies the picture order count modulo **MaxPicOrderCntLsb** for the top field of a coded frame or for a coded field. The length of the **pic\_order\_cnt\_lsb** syntax element is $\log_2 \text{max\_pic\_order\_cnt\_lsb\_minus4} + 4$ bits. The value of the **pic\_order\_cnt\_lsb** shall be in the range of 0 to **MaxPicOrderCntLsb** – 1, inclusive. + +**delta\_pic\_order\_cnt\_bottom** specifies the picture order count difference between the bottom field and the top field of a coded frame as follows: + +- If the current picture includes a **memory\_management\_control\_operation** equal to 5, the value of **delta\_pic\_order\_cnt\_bottom** shall be in the range of $(1 - \text{MaxPicOrderCntLsb})$ to $2^{31} - 1$ , inclusive. +- Otherwise (the current picture does not include a **memory\_management\_control\_operation** equal to 5), the value of **delta\_pic\_order\_cnt\_bottom** shall be in the range of $-2^{31} + 1$ to $2^{31} - 1$ , inclusive. + +When this syntax element is not present in the bitstream for the current slice, it shall be inferred to be equal to 0. + +**delta\_pic\_order\_cnt[ 0 ]** specifies the picture order count difference from the expected picture order count for the top field of a coded frame or for a coded field as specified in clause 8.2.1. The value of **delta\_pic\_order\_cnt[ 0 ]** shall be in the range of $-2^{31} + 1$ to $2^{31} - 1$ , inclusive. When this syntax element is not present in the bitstream for the current slice, it shall be inferred to be equal to 0. + +**delta\_pic\_order\_cnt[ 1 ]** specifies the picture order count difference from the expected picture order count for the bottom field of a coded frame specified in clause 8.2.1. The value of **delta\_pic\_order\_cnt[ 1 ]** shall be in the range of $-2^{31} + 1$ to $2^{31} - 1$ , inclusive. When this syntax element is not present in the bitstream for the current slice, it shall be inferred to be equal to 0. + +**redundant\_pic\_cnt** shall be equal to 0 for slices and slice data partitions belonging to the primary coded picture. The value of **redundant\_pic\_cnt** shall be greater than 0 for coded slices or coded slice data partitions of a redundant coded picture. When **redundant\_pic\_cnt** is not present in the bitstream, its value shall be inferred to be equal to 0. The value of **redundant\_pic\_cnt** shall be in the range of 0 to 127, inclusive. + +NOTE 6 – Any area of the decoded primary picture and the corresponding area that would result from application of the decoding process specified in clause 8 for any redundant picture in the same access unit should be visually similar in appearance. + +The value of **pic\_parameter\_set\_id** in a coded slice or coded slice data partition of a redundant coded picture shall be such that the value of **bottom\_field\_pic\_order\_in\_frame\_present\_flag** in the picture parameter set in use in a redundant coded picture is equal to the value of **bottom\_field\_pic\_order\_in\_frame\_present\_flag** in the picture parameter set in use in the corresponding primary coded picture. + +When present in the primary coded picture and any redundant coded picture, the following syntax elements shall have the same value: **field\_pic\_flag**, **bottom\_field\_flag**, and **idr\_pic\_id**. + +When the value of **nal\_ref\_idc** in one VCL NAL unit of an access unit is equal to 0, the value of **nal\_ref\_idc** in all other VCL NAL units of the same access unit shall be equal to 0. + +NOTE 7 – The above constraint also has the following implications. If the value of **nal\_ref\_idc** for the VCL NAL units of the primary coded picture is equal to 0, the value of **nal\_ref\_idc** for the VCL NAL units of any corresponding redundant coded picture are equal to 0; otherwise (the value of **nal\_ref\_idc** for the VCL NAL units of the primary coded picture is greater than 0), the value of **nal\_ref\_idc** for the VCL NAL units of any corresponding redundant coded picture are also greater than 0. + +The marking status of reference pictures and the value of **frame\_num** after the decoded reference picture marking process as specified in clause 8.2.5 is invoked for the primary coded picture or any redundant coded picture of the same access unit shall be identical regardless whether the primary coded picture or any redundant coded picture (instead of the primary coded picture) of the access unit would be decoded. + +NOTE 8 – The above constraint also has the following implications. + +When the primary coded picture is an IDR picture and a redundant coded picture corresponding to the primary coded picture is an IDR picture, the contents of the **dec\_ref\_pic\_marking()** syntax structure must be identical in all slice headers of the primary coded picture and the redundant coded picture corresponding to the primary coded picture. + +When the primary coded picture is an IDR picture and a redundant coded picture corresponding to the primary coded picture is not an IDR picture, all slice headers of the redundant picture must contain a **dec\_ref\_pic\_marking** syntax() structure including a **memory\_management\_control\_operation** syntax element equal to 5, and the following applies: + +- If the value of `long_term_reference_flag` in the primary coded picture is equal to 0, the `dec_ref_pic_marking` syntax structure of the redundant coded picture must not include a `memory_management_control_operation` syntax element equal to 6. +- Otherwise (the value of `long_term_reference_flag` in the primary coded picture is equal to 1), the `dec_ref_pic_marking` syntax structure of the redundant coded picture must include `memory_management_control_operation` syntax elements equal to 5, 4, and 6 in decoding order, and the value of `max_long_term_frame_idx_plus1` must be equal to 1, and the value of `long_term_frame_idx` must be equal to 0. + +The values of `TopFieldOrderCnt` and `BottomFieldOrderCnt` (if applicable) that result after completion of the decoding process for any redundant coded picture or the primary coded picture of the same access unit shall be identical regardless whether the primary coded picture or any redundant coded picture (instead of the primary coded picture) of the access unit would be decoded. + +There is no required decoding process for a coded slice or coded slice data partition of a redundant coded picture. When the `redundant_pic_cnt` in the slice header of a coded slice is greater than 0, the decoder may discard the coded slice. However, a coded slice or coded slice data partition of any redundant coded picture shall obey the same constraints as a coded slice or coded slice data partition of a primary picture. + +NOTE 9 – When some of the samples in the decoded primary picture cannot be correctly decoded due to errors or losses in transmission of the sequence and one or more coded slices of a redundant coded picture can be correctly decoded, the decoder should replace the samples of the decoded primary picture with the corresponding samples of the decoded slice or decoded slices of the redundant coded picture. When slices of more than one redundant coded picture cover the relevant region of the primary coded picture, the slice or slices of the redundant coded picture having the lowest value of `redundant_pic_cnt` should be used. + +Slices and slice data partitions having the same value of `redundant_pic_cnt` belong to the same coded picture. If the value of `redundant_pic_cnt` is equal to 0, they belong to the primary coded picture; otherwise (the value of `redundant_pic_cnt` is greater than 0), they belong to the same redundant coded picture. Decoded slices within the same redundant coded picture need not cover the entire picture area and shall not overlap. + +**`direct_spatial_mv_pred_flag`** specifies the method used in the decoding process to derive motion vectors and reference indices for inter prediction as follows: + +- If `direct_spatial_mv_pred_flag` is equal to 1, the derivation process for luma motion vectors for `B_Skip`, `B_Direct_16x16`, and `B_Direct_8x8` in clause 8.4.1.2 shall use spatial direct mode prediction as specified in clause 8.4.1.2.2. +- Otherwise (`direct_spatial_mv_pred_flag` is equal to 0), the derivation process for luma motion vectors for `B_Skip`, `B_Direct_16x16`, and `B_Direct_8x8` in clause 8.4.1.2 shall use temporal direct mode prediction as specified in clause 8.4.1.2.3. + +**`num_ref_idx_active_override_flag`** equal to 1 specifies that the syntax element `num_ref_idx_l0_active_minus1` is present for P, SP, and B slices and that the syntax element `num_ref_idx_l1_active_minus1` is present for B slices. `num_ref_idx_active_override_flag` equal to 0 specifies that the syntax elements `num_ref_idx_l0_active_minus1` and `num_ref_idx_l1_active_minus1` are not present. + +When the current slice is a P, SP, or B slice and `field_pic_flag` is equal to 0 and the value of `num_ref_idx_l0_default_active_minus1` in the picture parameter set exceeds 15, `num_ref_idx_active_override_flag` shall be equal to 1. + +When the current slice is a B slice and `field_pic_flag` is equal to 0 and the value of `num_ref_idx_l1_default_active_minus1` in the picture parameter set exceeds 15, `num_ref_idx_active_override_flag` shall be equal to 1. + +**`num_ref_idx_l0_active_minus1`** specifies the maximum reference index for reference picture list 0 that shall be used to decode the slice. + +When the current slice is a P, SP, or B slice and `num_ref_idx_l0_active_minus1` is not present, `num_ref_idx_l0_active_minus1` shall be inferred to be equal to `num_ref_idx_l0_default_active_minus1`. + +The range of `num_ref_idx_l0_active_minus1` is specified as follows: + +- If `field_pic_flag` is equal to 0, `num_ref_idx_l0_active_minus1` shall be in the range of 0 to 15, inclusive. When `MbaffFrameFlag` is equal to 1, `num_ref_idx_l0_active_minus1` is the maximum index value for the decoding of frame macroblocks and $2 * \text{num\_ref\_idx\_l0\_active\_minus1} + 1$ is the maximum index value for the decoding of field macroblocks. +- Otherwise (`field_pic_flag` is equal to 1), `num_ref_idx_l0_active_minus1` shall be in the range of 0 to 31, inclusive. + +**`num_ref_idx_l1_active_minus1`** specifies the maximum reference index for reference picture list 1 that shall be used to decode the slice. + +When the current slice is a B slice and `num_ref_idx_l1_active_minus1` is not present, `num_ref_idx_l1_active_minus1` shall be inferred to be equal to `num_ref_idx_l1_default_active_minus1`. + +The range of `num_ref_idx_l1_active_minus1` is constrained as specified in the semantics for `num_ref_idx_l0_active_minus1` with l0 and list 0 replaced by l1 and list 1, respectively. + +**cabac\_init\_idc** specifies the index for determining the initialization table used in the initialization process for context variables. The value of `cabac_init_idc` shall be in the range of 0 to 2, inclusive. + +**slice\_qp\_delta** specifies the initial value of $QP_V$ to be used for all the macroblocks in the slice until modified by the value of `mb_qp_delta` in the macroblock layer. The initial $QP_V$ quantization parameter for the slice is computed as + +$$\text{SliceQP}_V = 26 + \text{pic\_init\_qp\_minus26} + \text{slice\_qp\_delta} \quad (7-32)$$ + +The value of `slice_qp_delta` shall be limited such that $\text{SliceQP}_V$ is in the range of $-\text{QpBdOffset}_V$ to $+51$ , inclusive. + +**sp\_for\_switch\_flag** specifies the decoding process to be used to decode P macroblocks in an SP slice as follows: + +- If `sp_for_switch_flag` is equal to 0, the P macroblocks in the SP slice shall be decoded using the SP decoding process for non-switching pictures as specified in clause 8.6.1. +- Otherwise (`sp_for_switch_flag` is equal to 1), the P macroblocks in the SP slice shall be decoded using the SP and SI decoding process for switching pictures as specified in clause 8.6.2. + +**slice\_qs\_delta** specifies the value of $QS_V$ for all the macroblocks in SP and SI slices. The $QS_V$ quantization parameter for the slice is computed as + +$$\text{QS}_V = 26 + \text{pic\_init\_qs\_minus26} + \text{slice\_qs\_delta} \quad (7-33)$$ + +The value of `slice_qs_delta` shall be limited such that $\text{QS}_V$ is in the range of 0 to 51, inclusive. This value of $\text{QS}_V$ is used for the decoding of all macroblocks in SI slices with `mb_type` equal to SI and all macroblocks in SP slices that are coded in an Inter macroblock prediction mode. + +**disable\_deblocking\_filter\_idc** specifies whether the operation of the deblocking filter shall be disabled across some block edges of the slice and specifies for which edges the filtering is disabled. When `disable_deblocking_filter_idc` is not present in the slice header, the value of `disable_deblocking_filter_idc` shall be inferred to be equal to 0. + +The value of `disable_deblocking_filter_idc` shall be in the range of 0 to 2, inclusive. + +**slice\_alpha\_c0\_offset\_div2** specifies the offset used in accessing the $\alpha$ and $t_{c0}$ deblocking filter tables for filtering operations controlled by the macroblocks within the slice. From this value, the offset that shall be applied when addressing these tables shall be computed as + +$$\text{FilterOffsetA} = \text{slice\_alpha\_c0\_offset\_div2} \ll 1 \quad (7-34)$$ + +The value of `slice_alpha_c0_offset_div2` shall be in the range of $-6$ to $+6$ , inclusive. When `slice_alpha_c0_offset_div2` is not present in the slice header, the value of `slice_alpha_c0_offset_div2` shall be inferred to be equal to 0. + +**slice\_beta\_offset\_div2** specifies the offset used in accessing the $\beta$ deblocking filter table for filtering operations controlled by the macroblocks within the slice. From this value, the offset that is applied when addressing the $\beta$ table of the deblocking filter shall be computed as + +$$\text{FilterOffsetB} = \text{slice\_beta\_offset\_div2} \ll 1 \quad (7-35)$$ + +The value of `slice_beta_offset_div2` shall be in the range of $-6$ to $+6$ , inclusive. When `slice_beta_offset_div2` is not present in the slice header the value of `slice_beta_offset_div2` shall be inferred to be equal to 0. + +**slice\_group\_change\_cycle** is used to derive the number of slice group map units in slice group 0 when `slice_group_map_type` is equal to 3, 4, or 5, as specified by + +$$\text{MapUnitsInSliceGroup0} = \text{Min}(\text{slice\_group\_change\_cycle} * \text{SliceGroupChangeRate}, \text{PicSizeInMapUnits}) \quad (7-36)$$ + +The value of `slice_group_change_cycle` is represented in the bitstream by the following number of bits + +$$\text{Ceil}(\text{Log2}(\text{PicSizeInMapUnits} \div \text{SliceGroupChangeRate} + 1)) \quad (7-37)$$ + +The value of `slice_group_change_cycle` shall be in the range of 0 to $\text{Ceil}(\text{PicSizeInMapUnits} / \text{SliceGroupChangeRate})$ , inclusive. + +#### 7.4.3.1 Reference picture list modification semantics + +The syntax elements `modification_of_pic_nums_idc`, `abs_diff_pic_num_minus1`, and `long_term_pic_num` specify the change from the initial reference picture lists to the reference picture lists to be used for decoding the slice. + +`ref_pic_list_modification_flag_l0` equal to 1 specifies that the syntax element `modification_of_pic_nums_idc` is present for specifying reference picture list 0. `ref_pic_list_modification_flag_l0` equal to 0 specifies that this syntax element is not present. + +When `ref_pic_list_modification_flag_l0` is equal to 1, the number of times that `modification_of_pic_nums_idc` is not equal to 3 following `ref_pic_list_modification_flag_l0` shall not exceed `num_ref_idx_l0_active_minus1 + 1`. + +When `RefPicList0[num_ref_idx_l0_active_minus1]` in the initial reference picture list produced as specified in clause 8.2.4.2 is equal to "no reference picture", `ref_pic_list_modification_flag_l0` shall be equal to 1 and `modification_of_pic_nums_idc` shall not be equal to 3 until `RefPicList0[num_ref_idx_l0_active_minus1]` in the modified list produced as specified in clause 8.2.4.3 is not equal to "no reference picture". + +`ref_pic_list_modification_flag_l1` equal to 1 specifies that the syntax element `modification_of_pic_nums_idc` is present for specifying reference picture list 1. `ref_pic_list_modification_flag_l1` equal to 0 specifies that this syntax element is not present. + +When `ref_pic_list_modification_flag_l1` is equal to 1, the number of times that `modification_of_pic_nums_idc` is not equal to 3 following `ref_pic_list_modification_flag_l1` shall not exceed `num_ref_idx_l1_active_minus1 + 1`. + +When decoding a slice with `slice_type` equal to 1 or 6 and `RefPicList1[num_ref_idx_l1_active_minus1]` in the initial reference picture list produced as specified in clause 8.2.4.2 is equal to "no reference picture", `ref_pic_list_modification_flag_l1` shall be equal to 1 and `modification_of_pic_nums_idc` shall not be equal to 3 until `RefPicList1[num_ref_idx_l1_active_minus1]` in the modified list produced as specified in clause 8.2.4.3 is not equal to "no reference picture". + +`modification_of_pic_nums_idc` together with `abs_diff_pic_num_minus1` or `long_term_pic_num` specifies which of the reference pictures are re-mapped. The values of `modification_of_pic_nums_idc` are specified in Table 7-7. The value of the first `modification_of_pic_nums_idc` that follows immediately after `ref_pic_list_modification_flag_l0` or `ref_pic_list_modification_flag_l1` shall not be equal to 3. + +**Table 7-7 – `modification_of_pic_nums_idc` operations for modification of reference picture lists** + +| modification_of_pic_nums_idc | modification specified | +|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| 0 | abs_diff_pic_num_minus1 is present and corresponds to a difference to subtract from a picture number prediction value | +| 1 | abs_diff_pic_num_minus1 is present and corresponds to a difference to add to a picture number prediction value | +| 2 | long_term_pic_num is present and specifies the long-term picture number for a reference picture | +| 3 | End loop for modification of the initial reference picture list | + +`abs_diff_pic_num_minus1` plus 1 specifies the absolute difference between the picture number of the picture being moved to the current index in the list and the picture number prediction value. `abs_diff_pic_num_minus1` shall be in the range of 0 to $\text{MaxPicNum} - 1$ . The allowed values of `abs_diff_pic_num_minus1` are further restricted as specified in clause 8.2.4.3.1. + +`long_term_pic_num` specifies the long-term picture number of the picture being moved to the current index in the list. When decoding a coded frame, `long_term_pic_num` shall be equal to a `LongTermPicNum` assigned to one of the reference frames or complementary reference field pairs marked as "used for long-term reference". When decoding a coded field, `long_term_pic_num` shall be equal to a `LongTermPicNum` assigned to one of the reference fields marked as "used for long-term reference". + +#### 7.4.3.2 Prediction weight table semantics + +`luma_log2_weight_denom` is the base 2 logarithm of the denominator for all luma weighting factors. The value of `luma_log2_weight_denom` shall be in the range of 0 to 7, inclusive. + +**chroma\_log2\_weight\_denom** is the base 2 logarithm of the denominator for all chroma weighting factors. The value of chroma\_log2\_weight\_denom shall be in the range of 0 to 7, inclusive. + +**luma\_weight\_10\_flag** equal to 1 specifies that weighting factors for the luma component of list 0 prediction are present. luma\_weight\_10\_flag equal to 0 specifies that these weighting factors are not present. + +**luma\_weight\_10[ i ]** is the weighting factor applied to the luma prediction value for list 0 prediction using RefPicList0[ i ]. When luma\_weight\_10\_flag is equal to 1, the value of luma\_weight\_10[ i ] shall be in the range of -128 to 127, inclusive. When luma\_weight\_10\_flag is equal to 0, luma\_weight\_10[ i ] shall be inferred to be equal to $2^{\text{luma\_log2\_weight\_denom}}$ for RefPicList0[ i ]. + +**luma\_offset\_10[ i ]** is the additive offset applied to the luma prediction value for list 0 prediction using RefPicList0[ i ]. The value of luma\_offset\_10[ i ] shall be in the range of -128 to 127, inclusive. When luma\_weight\_10\_flag is equal to 0, luma\_offset\_10[ i ] shall be inferred as equal to 0 for RefPicList0[ i ]. + +**chroma\_weight\_10\_flag** equal to 1 specifies that weighting factors for the chroma prediction values of list 0 prediction are present. chroma\_weight\_10\_flag equal to 0 specifies that these weighting factors are not present. + +**chroma\_weight\_10[ i ][ j ]** is the weighting factor applied to the chroma prediction values for list 0 prediction using RefPicList0[ i ] with j equal to 0 for Cb and j equal to 1 for Cr. When chroma\_weight\_10\_flag is equal to 1, the value of chroma\_weight\_10[ i ][ j ] shall be in the range of -128 to 127, inclusive. When chroma\_weight\_10\_flag is equal to 0, chroma\_weight\_10[ i ][ j ] shall be inferred to be equal to $2^{\text{chroma\_log2\_weight\_denom}}$ for RefPicList0[ i ]. + +**chroma\_offset\_10[ i ][ j ]** is the additive offset applied to the chroma prediction values for list 0 prediction using RefPicList0[ i ] with j equal to 0 for Cb and j equal to 1 for Cr. The value of chroma\_offset\_10[ i ][ j ] shall be in the range of -128 to 127, inclusive. When chroma\_weight\_10\_flag is equal to 0, chroma\_offset\_10[ i ][ j ] shall be inferred to be equal to 0 for RefPicList0[ i ]. + +**luma\_weight\_11\_flag**, **luma\_weight\_11**, **luma\_offset\_11**, **chroma\_weight\_11\_flag**, **chroma\_weight\_11**, **chroma\_offset\_11** have the same semantics as luma\_weight\_10\_flag, luma\_weight\_10, luma\_offset\_10, chroma\_weight\_10\_flag, chroma\_weight\_10, chroma\_offset\_10, respectively, with 10, list 0, and List0 replaced by 11, list 1, and List1, respectively. + +#### 7.4.3.3 Decoded reference picture marking semantics + +The syntax elements no\_output\_of\_prior\_pics\_flag, long\_term\_reference\_flag, adaptive\_ref\_pic\_marking\_mode\_flag, memory\_management\_control\_operation, difference\_of\_pic\_nums\_minus1, long\_term\_frame\_idx, long\_term\_pic\_num, and max\_long\_term\_frame\_idx\_plus1 specify marking of the reference pictures. + +The marking of a reference picture can be "unused for reference", "used for short-term reference", or "used for long-term reference", but only one among these three. When a reference picture is referred to as being marked as "used for reference", this collectively refers to the picture being marked as "used for short-term reference" or "used for long-term reference" (but not both). A reference picture that is marked as "used for short-term reference" is referred to as a short-term reference picture. A reference picture that is marked as "used for long-term reference" is referred to as a long-term reference picture. + +The content of the decoded reference picture marking syntax structure shall be the same in all slice headers of the primary coded picture. When one or more redundant coded pictures are present, the content of the decoded reference picture marking syntax structure shall be the same in all slice headers of a redundant coded picture with a particular value of redundant\_pic\_cnt. + +NOTE 1 – It is not required that the content of the decoded reference picture marking syntax structure in a redundant coded picture with a particular value of redundant\_pic\_cnt is identical to the content of the decoded reference picture marking syntax structure in the corresponding primary coded picture or a redundant coded picture with a different value of redundant\_pic\_cnt. However, as specified in clause 7.4.3, the content of the decoded reference picture marking syntax structure in a redundant coded picture is constrained in the way that the marking status of reference pictures and the value of frame\_num after the decoded reference picture marking process in clause 8.2.5 must be identical regardless whether the primary coded picture or any redundant coded picture of the access unit would be decoded. + +The syntax category of the decoded reference picture marking syntax structure shall be inferred as follows: + +- If the decoded reference picture marking syntax structure is in a slice header, the syntax category of the decoded reference picture marking syntax structure is inferred to be equal to 2. +- Otherwise (the decoded reference picture marking syntax structure is in a decoded reference picture marking repetition SEI message as specified in Annex D), the syntax category of the decoded reference picture marking syntax structure is inferred to be equal to 5. + +**no\_output\_of\_prior\_pics\_flag** specifies how the previously-decoded pictures in the decoded picture buffer are treated after decoding of an IDR picture. See Annex C. When the IDR picture is the first IDR picture in the bitstream, the value + +of `no_output_of_prior_pics_flag` has no effect on the decoding process. When the IDR picture is not the first IDR picture in the bitstream and the value of `PicWidthInMbs`, `FrameHeightInMbs`, or `max_dec_frame_buffering` derived from the active sequence parameter set is different from the value of `PicWidthInMbs`, `FrameHeightInMbs`, or `max_dec_frame_buffering` derived from the sequence parameter set active for the preceding picture, `no_output_of_prior_pics_flag` equal to 1 may (but should not) be inferred by the decoder, regardless of the actual value of `no_output_of_prior_pics_flag`. + +**`long_term_reference_flag`** equal to 0 specifies that the `MaxLongTermFrameIdx` variable is set equal to "no long-term frame indices" and that the IDR picture is marked as "used for short-term reference". `long_term_reference_flag` equal to 1 specifies that the `MaxLongTermFrameIdx` variable is set equal to 0 and that the current IDR picture is marked "used for long-term reference" and is assigned `LongTermFrameIdx` equal to 0. When `max_num_ref_frames` is equal to 0, `long_term_reference_flag` shall be equal to 0. + +**`adaptive_ref_pic_marking_mode_flag`** selects the reference picture marking mode of the currently decoded picture as specified in Table 7-8. `adaptive_ref_pic_marking_mode_flag` shall be equal to 1 when the number of frames, complementary field pairs, and non-paired fields that are currently marked as "used for long-term reference" is equal to `Max( max_num_ref_frames, 1 )`. + +**Table 7-8 – Interpretation of `adaptive_ref_pic_marking_mode_flag`** + +| adaptive_ref_pic_marking_mode_flag | Reference picture marking mode specified | +|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Sliding window reference picture marking mode: A marking mode providing a first-in first-out mechanism for short-term reference pictures. | +| 1 | Adaptive reference picture marking mode: A reference picture marking mode providing syntax elements to specify marking of reference pictures as "unused for reference" and to assign long-term frame indices. | + +**`memory_management_control_operation`** specifies a control operation to be applied to affect the reference picture marking. The `memory_management_control_operation` syntax element is followed by data necessary for the operation specified by the value of `memory_management_control_operation`. The values and control operations associated with `memory_management_control_operation` are specified in Table 7-9. The `memory_management_control_operation` syntax elements are processed by the decoding process in the order in which they appear in the slice header, and the semantics constraints expressed for each `memory_management_control_operation` apply at the specific position in that order at which that individual `memory_management_control_operation` is processed. + +For interpretation of `memory_management_control_operation`, the term reference picture is interpreted as follows: + +- If the current picture is a frame, the term reference picture refers either to a reference frame or a complementary reference field pair. +- Otherwise (the current picture is a field), the term reference picture refers either to a reference field or a field of a reference frame. + +`memory_management_control_operation` shall not be equal to 1 in a slice header unless the specified reference picture is marked as "used for short-term reference" when the `memory_management_control_operation` is processed by the decoding process. + +`memory_management_control_operation` shall not be equal to 2 in a slice header unless the specified long-term picture number refers to a reference picture that is marked as "used for long-term reference" when the `memory_management_control_operation` is processed by the decoding process. + +`memory_management_control_operation` shall not be equal to 3 in a slice header unless the specified reference picture is marked as "used for short-term reference" when the `memory_management_control_operation` is processed by the decoding process. + +`memory_management_control_operation` shall not be equal to 3 or 6 if the value of the variable `MaxLongTermFrameIdx` is equal to "no long-term frame indices" when the `memory_management_control_operation` is processed by the decoding process. + +Not more than one `memory_management_control_operation` equal to 4 shall be present in a slice header. + +Not more than one `memory_management_control_operation` equal to 5 shall be present in a slice header. + +Not more than one `memory_management_control_operation` equal to 6 shall be present in a slice header. + +memory\_management\_control\_operation shall not be equal to 5 in a slice header unless no memory\_management\_control\_operation in the range of 1 to 3 is present in the same decoded reference picture marking syntax structure. + +A memory\_management\_control\_operation equal to 5 shall not follow a memory\_management\_control\_operation equal to 6 in the same slice header. + +When a memory\_management\_control\_operation equal to 6 is present, any memory\_management\_control\_operation equal to 2, 3, or 4 that follows the memory\_management\_control\_operation equal to 6 within the same slice header shall not specify the current picture to be marked as "unused for reference". + +NOTE 2 – These constraints prohibit any combination of multiple memory\_management\_control\_operation syntax elements that would specify the current picture to be marked as "unused for reference". However, some other combinations of memory\_management\_control\_operation syntax elements are permitted that may affect the marking status of other reference pictures more than once in the same slice header. In particular, it is permitted for a memory\_management\_control\_operation equal to 3 that specifies a long-term frame index to be assigned to a particular short-term reference picture to be followed in the same slice header by a memory\_management\_control\_operation equal to 2, 3, 4 or 6 that specifies the same reference picture to subsequently be marked as "unused for reference". + +**Table 7-9 – Memory management control operation (memory\_management\_control\_operation) values** + +| memory_management_control_operation | Memory Management Control Operation | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | End memory_management_control_operation syntax element loop | +| 1 | Mark a short-term reference picture as "unused for reference" | +| 2 | Mark a long-term reference picture as "unused for reference" | +| 3 | Mark a short-term reference picture as "used for long-term reference" and assign a long-term frame index to it | +| 4 | Specify the maximum long-term frame index and mark all long-term reference pictures having long-term frame indices greater than the maximum value as "unused for reference" | +| 5 | Mark all reference pictures as "unused for reference" and set the MaxLongTermFrameIdx variable to "no long-term frame indices" | +| 6 | Mark the current picture as "used for long-term reference" and assign a long-term frame index to it | + +When decoding a field and a memory\_management\_control\_operation command equal to 3 is present that assigns a long-term frame index to a field that is part of a short-term reference frame or part of a complementary reference field pair, another memory\_management\_control\_operation command (equal to 3 or 6) to assign the same long-term frame index to the other field of the same frame or complementary reference field pair shall be present in the same decoded reference picture marking syntax structure. + +NOTE 3 – The above requirement must be fulfilled even when the field referred to by the memory\_management\_control\_operation equal to 3 is subsequently marked as "unused for reference" (for example when a memory\_management\_control\_operation equal to 2 is present in the same slice header that causes the field to be marked as "unused for reference"). + +NOTE 4 – The above requirement has the following implications: + +- When a memory\_management\_control\_operation equal to 3 is present that assigns a long-term frame index to a field that is part of a reference frame or complementary reference field pair with both fields marked as "used for short-term reference" (when processing the memory\_management\_control\_operation equal to 3), another memory\_management\_control\_operation equal to 3 must also be present in the same decoded reference picture marking syntax structure that assigns the same long-term frame index to the other field of the reference frame or complementary reference field pair. +- When the current picture is the second field (in decoding order) of a complementary reference field pair and a memory\_management\_control\_operation equal to 3 is present in the decoded reference picture marking syntax structure of the current picture that assigns a long-term frame index to the first field (in decoding order) of the complementary reference field pair, a memory\_management\_control\_operation equal to 6 must be present in the same decoded reference picture marking syntax structure that assigns the same long-term frame index to the second field of the complementary reference field pair. + +When the first field (in decoding order) of a complementary reference field pair included a long\_term\_reference\_flag equal to 1 or a memory\_management\_control\_operation command equal to 6, the decoded reference picture marking syntax structure for the second field of the complementary reference field pair shall contain a memory\_management\_control\_operation command equal to 6 that assigns the same long-term frame index to the second field. + +NOTE 5 – The above requirement must be fulfilled even when the first field of the complementary reference field pair is subsequently marked as "unused for reference" (for example, when a memory\_management\_control\_operation equal to 2 is present in the slice header of the second field that causes the first field to be marked as "unused for reference"). + +When the second field (in decoding order) of a complementary reference field pair includes a memory\_management\_control\_operation command equal to 6 that assigns a long-term frame index to this field and the first field of the complementary reference field pair is marked as "used for short-term reference" when the memory\_management\_control\_operation command equal to 6 is processed by the decoding process, the decoded reference picture marking syntax structure of that second field shall contain either a memory\_management\_control\_operation command equal to 1 that marks the first field of the complementary field pair as "unused for reference" or a memory\_management\_control\_operation command equal to 3 that marks the first field of the complementary field pair as "used for long-term reference" and assigns the same long-term frame index to the first field. + +NOTE 6 – The above constraints specify that when both fields of a frame or a complementary field pair are marked as "used for reference" after processing all memory\_management\_control\_operation commands of the decoded reference picture marking syntax structure, either both fields must be marked as "used for short-term reference" or both fields must be marked as "used for long-term reference". When both fields are marked as "used for long-term reference", the same long-term frame index must be assigned to both fields. + +**difference\_of\_pic\_nums\_minus1** is used (with memory\_management\_control\_operation equal to 3 or 1) to assign a long-term frame index to a short-term reference picture or to mark a short-term reference picture as "unused for reference". When the associated memory\_management\_control\_operation is processed by the decoding process, the resulting picture number derived from difference\_of\_pic\_nums\_minus1 shall be a picture number assigned to one of the reference pictures marked as "used for reference" and not previously assigned to a long-term frame index. + +The resulting picture number is constrained as follows: + +- If field\_pic\_flag is equal to 0, the resulting picture number shall be one of the set of picture numbers assigned to reference frames or complementary reference field pairs. + +NOTE 7 – When field\_pic\_flag is equal to 0, the resulting picture number must be a picture number assigned to a complementary reference field pair in which both fields are marked as "used for reference" or a frame in which both fields are marked as "used for reference". In particular, when field\_pic\_flag is equal to 0, the marking of a non-paired field or a frame in which a single field is marked as "used for reference" cannot be affected by a memory\_management\_control\_operation equal to 1. + +- Otherwise (field\_pic\_flag is equal to 1), the resulting picture number shall be one of the set of picture numbers assigned to reference fields. + +**long\_term\_pic\_num** is used (with memory\_management\_control\_operation equal to 2) to mark a long-term reference picture as "unused for reference". When the associated memory\_management\_control\_operation is processed by the decoding process, long\_term\_pic\_num shall be equal to a long-term picture number assigned to one of the reference pictures that is currently marked as "used for long-term reference". + +The resulting long-term picture number is constrained as follows: + +- If field\_pic\_flag is equal to 0, the resulting long-term picture number shall be one of the set of long-term picture numbers assigned to reference frames or complementary reference field pairs. + +NOTE 8 – When field\_pic\_flag is equal to 0, the resulting long-term picture number must be a long-term picture number assigned to a complementary reference field pair in which both fields are marked as "used for reference" or a frame in which both fields are marked as "used for reference". In particular, when field\_pic\_flag is equal to 0, the marking of a non-paired field or a frame in which a single field is marked as "used for reference" cannot be affected by a memory\_management\_control\_operation equal to 2. + +- Otherwise (field\_pic\_flag is equal to 1), the resulting long-term picture number shall be one of the set of long-term picture numbers assigned to reference fields. + +**long\_term\_frame\_idx** is used (with memory\_management\_control\_operation equal to 3 or 6) to assign a long-term frame index to a picture. When the associated memory\_management\_control\_operation is processed by the decoding process, the value of long\_term\_frame\_idx shall be in the range of 0 to MaxLongTermFrameIdx, inclusive. + +**max\_long\_term\_frame\_idx\_plus1** minus 1 specifies the maximum value of long-term frame index allowed for long-term reference pictures (until receipt of another value of max\_long\_term\_frame\_idx\_plus1). The value of max\_long\_term\_frame\_idx\_plus1 shall be in the range of 0 to max\_num\_ref\_frames, inclusive. + +#### 7.4.4 Slice data semantics + +**cabac\_alignment\_one\_bit** is a bit equal to 1. + +**mb\_skip\_run** specifies the number of consecutive skipped macroblocks for which, when decoding a P or SP slice, **mb\_type** shall be inferred to be **P\_Skip** and the macroblock type is collectively referred to as a P macroblock type, or for which, when decoding a B slice, **mb\_type** shall be inferred to be **B\_Skip** and the macroblock type is collectively referred to as a B macroblock type. The value of **mb\_skip\_run** shall be in the range of 0 to **PicSizeInMbs – CurrMbAddr**, inclusive. + +**mb\_skip\_flag** equal to 1 specifies that for the current macroblock, when decoding a P or SP slice, **mb\_type** shall be inferred to be **P\_Skip** and the macroblock type is collectively referred to as P macroblock type, or for which, when decoding a B slice, **mb\_type** shall be inferred to be **B\_Skip** and the macroblock type is collectively referred to as B macroblock type. **mb\_skip\_flag** equal to 0 specifies that the current macroblock is not skipped. + +**mb\_field\_decoding\_flag** equal to 0 specifies that the current macroblock pair is a frame macroblock pair. **mb\_field\_decoding\_flag** equal to 1 specifies that the macroblock pair is a field macroblock pair. Both macroblocks of a frame macroblock pair are referred to in the text as frame macroblocks, whereas both macroblocks of a field macroblock pair are referred to in the text as field macroblocks. + +When **MbaffFrameFlag** is equal to 0 (**mb\_field\_decoding\_flag** is not present), **mb\_field\_decoding\_flag** is inferred to be equal to **field\_pic\_flag**. + +When **MbaffFrameFlag** is equal to 1 and **mb\_field\_decoding\_flag** is not present for both the top and the bottom macroblock of a macroblock pair, the value of **mb\_field\_decoding\_flag** shall be inferred as follows: + +- If there is a neighbouring macroblock pair immediately to the left of the current macroblock pair in the same slice, the value of **mb\_field\_decoding\_flag** is inferred to be equal to the value of **mb\_field\_decoding\_flag** for the neighbouring macroblock pair immediately to the left of the current macroblock pair, +- Otherwise, if there is no neighbouring macroblock pair immediately to the left of the current macroblock pair in the same slice and there is a neighbouring macroblock pair immediately above the current macroblock pair in the same slice, the value of **mb\_field\_decoding\_flag** is inferred to be equal to the value of **mb\_field\_decoding\_flag** for the neighbouring macroblock pair immediately above the current macroblock pair, +- Otherwise (there is no neighbouring macroblock pair either immediately to the left or immediately above the current macroblock pair in the same slice), the value of **mb\_field\_decoding\_flag** is inferred to be equal to 0. + +NOTE – When **MbaffFrameFlag** is equal to 1 and **mb\_field\_decoding\_flag** is not present for the top macroblock of a macroblock pair (because the top macroblock is skipped), a decoder must wait until **mb\_field\_decoding\_flag** for the bottom macroblock is read (when the bottom macroblock is not skipped) or the value of **mb\_field\_decoding\_flag** is inferred as specified above (when the bottom macroblock is also skipped) before it starts the decoding process for the top macroblock. + +**end\_of\_slice\_flag** equal to 0 specifies that another macroblock is following in the slice. **end\_of\_slice\_flag** equal to 1 specifies the end of the slice and that no further macroblock follows. + +The function **NextMbAddress()** used in the slice data syntax table is specified in clause 8.2.2. + +#### 7.4.5 Macroblock layer semantics + +**mb\_type** specifies the macroblock type. The semantics of **mb\_type** depend on the slice type. + +Tables and semantics are specified for the various macroblock types for I, SI, P, SP, and B slices. Each table presents the value of **mb\_type**, the name of **mb\_type**, the number of macroblock partitions used (given by the **NumMbPart( mb\_type )** function), the prediction mode of the macroblock (when it is not partitioned) or the first partition (given by the **MbPartPredMode( mb\_type, 0 )** function) and the prediction mode of the second partition (given by the **MbPartPredMode( mb\_type, 1 )** function). When a value is not applicable it is designated by "na". In the text, the value of **mb\_type** may be referred to as the macroblock type, the value of **MbPartPredMode()** may be referred to in the text by "macroblock (partition) prediction mode", and a value X of **MbPartPredMode()** may be referred to in the text by "X macroblock (partition) prediction mode" or as "X prediction macroblocks". + +Table 7-10 shows the allowed collective macroblock types for each **slice\_type**. + +NOTE 1 – There are some macroblock types with **Pred\_L0** macroblock (partition) prediction mode(s) that are classified as B macroblock types. + +**Table 7-10 – Allowed collective macroblock types for slice\_type** + +| slice_type | allowed collective macroblock types | +|-------------------|---------------------------------------------------------------| +| I (slice) | I (see Table 7-11) (macroblock types) | +| P (slice) | P (see Table 7-13) and I (see Table 7-11) (macroblock types) | +| B (slice) | B (see Table 7-14) and I (see Table 7-11) (macroblock types) | +| SI (slice) | SI (see Table 7-12) and I (see Table 7-11) (macroblock types) | +| SP (slice) | P (see Table 7-13) and I (see Table 7-11) (macroblock types) | + +**transform\_size\_8x8\_flag** equal to 1 specifies that for the current macroblock the transform coefficient decoding process and picture construction process prior to deblocking filter process for residual 8x8 blocks shall be invoked for luma samples, and when **ChromaArrayType == 3** also for Cb and Cr samples. **transform\_size\_8x8\_flag** equal to 0 specifies that for the current macroblock the transform coefficient decoding process and picture construction process prior to deblocking filter process for residual 4x4 blocks shall be invoked for luma samples, and when **ChromaArrayType == 3** also for Cb and Cr samples. When **transform\_size\_8x8\_flag** is not present in the bitstream, it shall be inferred to be equal to 0. + +NOTE 2 – When the current macroblock prediction mode **MbPartPredMode( mb\_type, 0 )** is equal to **Intra\_16x16**, **transform\_size\_8x8\_flag** is not present in the bitstream and then inferred to be equal to 0. + +When **sub\_mb\_type[ mbPartIdx ]** (see clause 7.4.5.2) is present in the bitstream for all 8x8 blocks indexed by **mbPartIdx = 0..3**, the variable **noSubMbPartSizeLessThan8x8Flag** indicates whether for each of the four 8x8 blocks the corresponding **SubMbPartWidth( sub\_mb\_type[ mbPartIdx ] )** and **SubMbPartHeight( sub\_mb\_type[ mbPartIdx ] )** are both equal to 8. + +NOTE 3 – When **noSubMbPartSizeLessThan8x8Flag** is equal to 0 and the current macroblock type is not equal to **I\_NxN**, **transform\_size\_8x8\_flag** is not present in the bitstream and then inferred to be equal to 0. + +Macroblock types that may be collectively referred to as I macroblock types are specified in Table 7-11. + +The macroblock types for I slices are all I macroblock types. + +Table 7-11 – Macroblock types for I slices + +| mb_type | Name of mb_type | transform_size_8x8_flag | MbPartPredMode
( mb_type, 0 ) | Intra16x16PredMode | CodedBlockPatternChroma | CodedBlockPatternLuma | +|---------|-----------------|-------------------------|----------------------------------|--------------------|-------------------------|-----------------------| +| 0 | I_NxN | 0 | Intra_4x4 | na | Equation 7-38 | Equation 7-38 | +| 0 | I_NxN | 1 | Intra_8x8 | na | Equation 7-38 | Equation 7-38 | +| 1 | I_16x16_0_0_0 | na | Intra_16x16 | 0 | 0 | 0 | +| 2 | I_16x16_1_0_0 | na | Intra_16x16 | 1 | 0 | 0 | +| 3 | I_16x16_2_0_0 | na | Intra_16x16 | 2 | 0 | 0 | +| 4 | I_16x16_3_0_0 | na | Intra_16x16 | 3 | 0 | 0 | +| 5 | I_16x16_0_1_0 | na | Intra_16x16 | 0 | 1 | 0 | +| 6 | I_16x16_1_1_0 | na | Intra_16x16 | 1 | 1 | 0 | +| 7 | I_16x16_2_1_0 | na | Intra_16x16 | 2 | 1 | 0 | +| 8 | I_16x16_3_1_0 | na | Intra_16x16 | 3 | 1 | 0 | +| 9 | I_16x16_0_2_0 | na | Intra_16x16 | 0 | 2 | 0 | +| 10 | I_16x16_1_2_0 | na | Intra_16x16 | 1 | 2 | 0 | +| 11 | I_16x16_2_2_0 | na | Intra_16x16 | 2 | 2 | 0 | +| 12 | I_16x16_3_2_0 | na | Intra_16x16 | 3 | 2 | 0 | +| 13 | I_16x16_0_0_1 | na | Intra_16x16 | 0 | 0 | 15 | +| 14 | I_16x16_1_0_1 | na | Intra_16x16 | 1 | 0 | 15 | +| 15 | I_16x16_2_0_1 | na | Intra_16x16 | 2 | 0 | 15 | +| 16 | I_16x16_3_0_1 | na | Intra_16x16 | 3 | 0 | 15 | +| 17 | I_16x16_0_1_1 | na | Intra_16x16 | 0 | 1 | 15 | +| 18 | I_16x16_1_1_1 | na | Intra_16x16 | 1 | 1 | 15 | +| 19 | I_16x16_2_1_1 | na | Intra_16x16 | 2 | 1 | 15 | +| 20 | I_16x16_3_1_1 | na | Intra_16x16 | 3 | 1 | 15 | +| 21 | I_16x16_0_2_1 | na | Intra_16x16 | 0 | 2 | 15 | +| 22 | I_16x16_1_2_1 | na | Intra_16x16 | 1 | 2 | 15 | +| 23 | I_16x16_2_2_1 | na | Intra_16x16 | 2 | 2 | 15 | +| 24 | I_16x16_3_2_1 | na | Intra_16x16 | 3 | 2 | 15 | +| 25 | I_PCM | na | na | na | na | na | + +The following semantics are assigned to the macroblock types in Table 7-11: + +- I\_NxN: A mnemonic name for mb\_type equal to 0 with MbPartPredMode( mb\_type, 0 ) equal to Intra\_4x4 or Intra\_8x8. +- I\_16x16\_0\_0\_0, I\_16x16\_1\_0\_0, I\_16x16\_2\_0\_0, I\_16x16\_3\_0\_0, I\_16x16\_0\_1\_0, I\_16x16\_1\_1\_0, I\_16x16\_2\_1\_0, I\_16x16\_3\_1\_0, I\_16x16\_0\_2\_0, I\_16x16\_1\_2\_0, I\_16x16\_2\_2\_0, I\_16x16\_3\_2\_0, I\_16x16\_0\_0\_1, I\_16x16\_1\_0\_1, I\_16x16\_2\_0\_1, I\_16x16\_3\_0\_1, I\_16x16\_0\_1\_1, I\_16x16\_1\_1\_1, I\_16x16\_2\_1\_1, I\_16x16\_3\_1\_1, I\_16x16\_0\_2\_1, I\_16x16\_1\_2\_1, I\_16x16\_2\_2\_1, I\_16x16\_3\_2\_1: the macroblock is coded as an Intra\_16x16 prediction macroblock. + +To each Intra\_16x16 prediction macroblock, an Intra16x16PredMode is assigned, which specifies the Intra\_16x16 prediction mode, and values of CodedBlockPatternLuma and CodedBlockPatternChroma are assigned as specified in Table 7-11. + +Intra\_4x4 specifies the macroblock prediction mode and specifies that the Intra\_4x4 prediction process is invoked as specified in clause 8.3.1. Intra\_4x4 is an Intra macroblock prediction mode. + +Intra\_8x8 specifies the macroblock prediction mode and specifies that the Intra\_8x8 prediction process is invoked as specified in clause 8.3.2. Intra\_8x8 is an Intra macroblock prediction mode. + +Intra\_16x16 specifies the macroblock prediction mode and specifies that the Intra\_16x16 prediction process is invoked as specified in clause 8.3.3. Intra\_16x16 is an Intra macroblock prediction mode. + +For a macroblock coded with mb\_type equal to I\_PCM, the Intra macroblock prediction mode shall be inferred. + +A macroblock type that may be referred to as the SI macroblock type is specified in Table 7-12. + +The macroblock types for SI slices are specified in Tables 7-12 and 7-11. The mb\_type value 0 is specified in Table 7-12 and the mb\_type values 1 to 26 are specified in Table 7-11, indexed by subtracting 1 from the value of mb\_type. + +**Table 7-12 – Macroblock type with value 0 for SI slices** + +| mb_type | Name of mb_type | MbPartPredMode
( mb_type, 0 ) | Intra16x16PredMode | CodedBlockPatternChroma | CodedBlockPatternLuma | +|---------|-----------------|----------------------------------|--------------------|-------------------------|-----------------------| +| 0 | SI | Intra_4x4 | na | Equation 7-38 | Equation 7-38 | + +The following semantics are assigned to the macroblock type in Table 7-12: + +- The SI macroblock is coded as Intra\_4x4 prediction macroblock. + +Macroblock types that may be collectively referred to as P macroblock types are specified in Table 7-13. + +The macroblock types for P and SP slices are specified in Tables 7-13 and 7-11. mb\_type values 0 to 4 are specified in Table 7-13 and mb\_type values 5 to 30 are specified in Table 7-11, indexed by subtracting 5 from the value of mb\_type. + +**Table 7-13 – Macroblock type values 0 to 4 for P and SP slices** + +| mb_type | Name of mb_type | NumMbPart
( mb_type ) | MbPartPredMode
( mb_type, 0 ) | MbPartPredMode
( mb_type, 1 ) | MbPartWidth
( mb_type ) | MbPartHeight
( mb_type ) | +|----------|-----------------|--------------------------|----------------------------------|----------------------------------|----------------------------|-----------------------------| +| 0 | P_L0_16x16 | 1 | Pred_L0 | na | 16 | 16 | +| 1 | P_L0_L0_16x8 | 2 | Pred_L0 | Pred_L0 | 16 | 8 | +| 2 | P_L0_L0_8x16 | 2 | Pred_L0 | Pred_L0 | 8 | 16 | +| 3 | P_8x8 | 4 | na | na | 8 | 8 | +| 4 | P_8x8ref0 | 4 | na | na | 8 | 8 | +| inferred | P_Skip | 1 | Pred_L0 | na | 16 | 16 | + +The following semantics are assigned to the macroblock types in Table 7-13: + +- P\_L0\_16x16: the samples of the macroblock are predicted with one luma macroblock partition of size 16x16 luma samples and associated chroma samples. +- P\_L0\_L0\_MxN, with MxN being replaced by 16x8 or 8x16: the samples of the macroblock are predicted using two luma partitions of size MxN equal to 16x8, or two luma partitions of size MxN equal to 8x16, and associated chroma samples, respectively. +- P\_8x8: for each sub-macroblock an additional syntax element (sub\_mb\_type[ mbPartIdx ] with mbPartIdx being the macroblock partition index for the corresponding sub-macroblock) is present in the bitstream that specifies the type of the corresponding sub-macroblock (see clause 7.4.5.2). +- P\_8x8ref0: has the same semantics as P\_8x8 but no syntax element for the reference index (ref\_idx\_10[ mbPartIdx ] with mbPartIdx = 0..3) is present in the bitstream and ref\_idx\_10[ mbPartIdx ] shall be inferred to be equal to 0 for all sub-macroblocks of the macroblock (with indices mbPartIdx = 0..3). +- P\_Skip: no further data is present for the macroblock in the bitstream. + +The following semantics are assigned to the macroblock prediction modes (for macroblocks that are not partitioned) and macroblock partition prediction modes (for macroblocks that are partitioned) specified by MbPartPredMode() in Table 7-13: + +- Pred\_L0: specifies that the Inter prediction process is invoked using list 0 prediction. Pred\_L0 is an Inter macroblock prediction mode (for macroblocks that are not partitioned) and an Inter macroblock partition prediction mode (for macroblocks that are partitioned). + +When mb\_type is equal to any of the values specified in Table 7-13, the macroblock is coded in an Inter macroblock prediction mode. + +Macroblock types that may be collectively referred to as B macroblock types are specified in Table 7-14. + +The macroblock types for B slices are specified in Tables 7-14 and 7-11. The mb\_type values 0 to 22 are specified in Table 7-14 and the mb\_type values 23 to 48 are specified in Table 7-11, indexed by subtracting 23 from the value of mb\_type. + +Table 7-14 – Macroblock type values 0 to 22 for B slices + +| mb_type | Name of mb_type | NumMbPart
( mb_type ) | MbPartPredMode
( mb_type, 0 ) | MbPartPredMode
( mb_type, 1 ) | MbPartWidth
( mb_type ) | MbPartHeight
( mb_type ) | +|----------|-----------------|--------------------------|----------------------------------|----------------------------------|----------------------------|-----------------------------| +| 0 | B_Direct_16x16 | na | Direct | na | 8 | 8 | +| 1 | B_L0_16x16 | 1 | Pred_L0 | na | 16 | 16 | +| 2 | B_L1_16x16 | 1 | Pred_L1 | na | 16 | 16 | +| 3 | B_Bi_16x16 | 1 | BiPred | na | 16 | 16 | +| 4 | B_L0_L0_16x8 | 2 | Pred_L0 | Pred_L0 | 16 | 8 | +| 5 | B_L0_L0_8x16 | 2 | Pred_L0 | Pred_L0 | 8 | 16 | +| 6 | B_L1_L1_16x8 | 2 | Pred_L1 | Pred_L1 | 16 | 8 | +| 7 | B_L1_L1_8x16 | 2 | Pred_L1 | Pred_L1 | 8 | 16 | +| 8 | B_L0_L1_16x8 | 2 | Pred_L0 | Pred_L1 | 16 | 8 | +| 9 | B_L0_L1_8x16 | 2 | Pred_L0 | Pred_L1 | 8 | 16 | +| 10 | B_L1_L0_16x8 | 2 | Pred_L1 | Pred_L0 | 16 | 8 | +| 11 | B_L1_L0_8x16 | 2 | Pred_L1 | Pred_L0 | 8 | 16 | +| 12 | B_L0_Bi_16x8 | 2 | Pred_L0 | BiPred | 16 | 8 | +| 13 | B_L0_Bi_8x16 | 2 | Pred_L0 | BiPred | 8 | 16 | +| 14 | B_L1_Bi_16x8 | 2 | Pred_L1 | BiPred | 16 | 8 | +| 15 | B_L1_Bi_8x16 | 2 | Pred_L1 | BiPred | 8 | 16 | +| 16 | B_Bi_L0_16x8 | 2 | BiPred | Pred_L0 | 16 | 8 | +| 17 | B_Bi_L0_8x16 | 2 | BiPred | Pred_L0 | 8 | 16 | +| 18 | B_Bi_L1_16x8 | 2 | BiPred | Pred_L1 | 16 | 8 | +| 19 | B_Bi_L1_8x16 | 2 | BiPred | Pred_L1 | 8 | 16 | +| 20 | B_Bi_Bi_16x8 | 2 | BiPred | BiPred | 16 | 8 | +| 21 | B_Bi_Bi_8x16 | 2 | BiPred | BiPred | 8 | 16 | +| 22 | B_8x8 | 4 | na | na | 8 | 8 | +| inferred | B_Skip | na | Direct | na | 8 | 8 | + +The following semantics are assigned to the macroblock types in Table 7-14: + +- B\_Direct\_16x16: no motion vector differences or reference indices are present for the macroblock in the bitstream. The functions MbPartWidth( B\_Direct\_16x16 ), and MbPartHeight( B\_Direct\_16x16 ) are used in the derivation process for motion vectors and reference frame indices in clause 8.4.1 for direct mode prediction. +- B\_X\_16x16 with X being replaced by L0, L1, or Bi: the samples of the macroblock are predicted with one luma macroblock partition of size 16x16 luma samples and associated chroma samples. For a macroblock with type B\_X\_16x16 with X being replaced by either L0 or L1, one motion vector difference and one reference index is + +present in the bitstream for the macroblock. For a macroblock with type B\_X\_16x16 with X being replaced by Bi, two motion vector differences and two reference indices are present in the bitstream for the macroblock. + +- B\_X0\_X1\_MxN, with X0, X1 referring to the first and second macroblock partition and being replaced by L0, L1, or Bi, and MxN being replaced by 16x8 or 8x16: the samples of the macroblock are predicted using two luma partitions of size MxN equal to 16x8, or two luma partitions of size MxN equal to 8x16, and associated chroma samples, respectively. For a macroblock partition X0 or X1 with X0 or X1 being replaced by either L0 or L1, one motion vector difference and one reference index is present in the bitstream. For a macroblock partition X0 or X1 with X0 or X1 being replaced by Bi, two motion vector differences and two reference indices are present in the bitstream for the macroblock partition. +- B\_8x8: for each sub-macroblock an additional syntax element (sub\_mb\_type[ mbPartIdx ]) with mbPartIdx being the macroblock partition index for the corresponding sub-macroblock) is present in the bitstream that specifies the type of the corresponding sub-macroblock (see clause 7.4.5.2). +- B\_Skip: no further data is present for the macroblock in the bitstream. The functions MbPartWidth( B\_Skip ), and MbPartHeight( B\_Skip ) are used in the derivation process for motion vectors and reference frame indices in clause 8.4.1 for direct mode prediction. + +The following semantics are assigned to the macroblock prediction modes (for macroblocks that are not partitioned) and macroblock partition prediction modes (for macroblocks that are partitioned) specified by MbPartPredMode( ) in Table 7-14: + +- Direct: no motion vector differences or reference indices are present for the macroblock (in case of B\_Skip or B\_Direct\_16x16) in the bitstream. Direct is an Inter macroblock prediction mode (for macroblocks that are not partitioned) and an Inter macroblock partition prediction mode (for macroblocks that are partitioned, see Table 7-18). +- Pred\_L0: the semantics specified for Table 7-13 apply. +- Pred\_L1: specifies that the Inter prediction process is invoked using list 1 prediction. Pred\_L1 is an Inter macroblock prediction mode (for macroblocks that are not partitioned) and an Inter macroblock partition prediction mode (for macroblocks that are partitioned). +- BiPred: specifies that the Inter prediction process is invoked using list 0 and list 1 prediction. BiPred is an Inter macroblock prediction mode (for macroblocks that are not partitioned) and an Inter macroblock partition prediction mode (for macroblocks that are partitioned). + +When mb\_type is equal to any of the values specified in Table 7-14, the macroblock is coded in an Inter macroblock prediction mode. + +**pcm\_alignment\_zero\_bit** is a bit equal to 0. + +**pcm\_sample\_luma[ i ]** is a sample value. The pcm\_sample\_luma[ i ] values represent luma sample values in the raster scan within the macroblock. The number of bits used to represent each of these samples is BitDepthY. + +**pcm\_sample\_chroma[ i ]** is a sample value. The first MbWidthC \* MbHeightC pcm\_sample\_chroma[ i ] values represent Cb sample values in the raster scan within the macroblock and the remaining MbWidthC \* MbHeightC pcm\_sample\_chroma[ i ] values represent Cr sample values in the raster scan within the macroblock. The number of bits used to represent each of these samples is BitDepthC. + +**coded\_block\_pattern** specifies which of the four 8x8 luma blocks and associated chroma blocks of a macroblock may contain non-zero transform coefficient levels. When coded\_block\_pattern is present in the bitstream, the variables CodedBlockPatternLuma and CodedBlockPatternChroma are derived as + +$$\begin{aligned} \text{CodedBlockPatternLuma} &= \text{coded\_block\_pattern} \% 16 \\ \text{CodedBlockPatternChroma} &= \text{coded\_block\_pattern} / 16 \end{aligned} \quad (7-38)$$ + +When the macroblock type is not equal to P\_Skip, B\_Skip, or I\_PCM, the following applies: + +- If the macroblock prediction mode is equal Intra\_16x16, the following applies: + - If ChromaArrayType is not equal to 3, the value of CodedBlockPatternLuma specifies the following. + - If CodedBlockPatternLuma is equal to 0, all AC transform coefficient levels of the luma component of the macroblock are equal to 0 for all 16 of the 4x4 blocks in the 16x16 luma block. + - Otherwise (CodedBlockPatternLuma is not equal to 0), CodedBlockPatternLuma is equal to 15, at least one of the AC transform coefficient levels of the luma component of the macroblock shall be non-zero, and the AC transform coefficient levels are scanned for all 16 of the 4x4 blocks in the 16x16 block. + +- Otherwise (ChromaArrayType is equal to 3), the value of CodedBlockPatternLuma specifies the following. + - If CodedBlockPatternLuma is equal to 0, all AC transform coefficient levels of the luma, Cb, and Cr components of the macroblock are equal to 0 for all 16 of the 4x4 blocks in the luma, Cb, and Cr components of the macroblock. + - Otherwise (CodedBlockPatternLuma is not equal to 0), CodedBlockPatternLuma is equal to 15, at least one of the AC transform coefficient levels of the luma, Cb, or Cr components of the macroblock shall be non-zero, and the AC transform coefficient levels are scanned for all 16 of the 4x4 blocks in the luma Cb, and Cr components of the macroblock. +- Otherwise (the macroblock prediction mode is not equal to Intra\_16x16), coded\_block\_pattern is present in the bitstream, and the following applies: + - If ChromaArrayType is not equal to 3, each of the four LSBs of CodedBlockPatternLuma specifies, for one of the four 8x8 luma blocks of the macroblock, the following. + - If the corresponding bit of CodedBlockPatternLuma is equal to 0, all transform coefficient levels of the luma transform blocks in the 8x8 luma block are equal to zero. + - Otherwise (the corresponding bit of CodedBlockPatternLuma is equal to 1), one or more transform coefficient levels of one or more of the luma transform blocks in the 8x8 luma block shall be non-zero valued and the transform coefficient levels of the corresponding transform blocks are scanned. + - Otherwise (ChromaArrayType is equal to 3), each of the four LSBs of CodedBlockPatternLuma specifies, for one of the four 8x8 luma blocks of the macroblock, the following. + - If the corresponding bit of CodedBlockPatternLuma is equal to 0, all transform coefficient levels of the luma, Cb, and Cr transform blocks in the 8x8 luma block are equal to zero. + - Otherwise (the corresponding bit of CodedBlockPatternLuma is equal to 1), one or more transform coefficient levels of one or more of the luma, Cb, or Cr transform blocks in the 8x8 luma block shall be non-zero valued and the transform coefficient levels of the corresponding transform blocks are scanned. + +When the macroblock type is not equal to P\_Skip, B\_Skip, or I\_PCM, CodedBlockPatternChroma is interpreted as follows: + +- If ChromaArrayType is not equal to 0 or 3, CodedBlockPatternChroma is specified in Table 7-15. +- Otherwise (ChromaArrayType is equal to 0 or 3), the bitstream shall not contain data that result in a derived value of CodedBlockPatternChroma that is not equal to 0. + +**Table 7-15 – Specification of CodedBlockPatternChroma values** + +| CodedBlockPatternChroma | Description | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | All chroma transform coefficient levels are equal to 0. | +| 1 | One or more chroma DC transform coefficient levels shall be non-zero valued.
All chroma AC transform coefficient levels are equal to 0. | +| 2 | Zero or more chroma DC transform coefficient levels are non-zero valued.
One or more chroma AC transform coefficient levels shall be non-zero valued. | + +**mb\_qp\_delta** can change the value of $QP_Y$ in the macroblock layer. The decoded value of **mb\_qp\_delta** shall be in the range of $-( 26 + QpBdOffset_Y / 2 )$ to $+( 25 + QpBdOffset_Y / 2 )$ , inclusive. **mb\_qp\_delta** shall be inferred to be equal to 0 when it is not present for any macroblock (including P\_Skip and B\_Skip macroblock types). + +The value of $QP_Y$ is derived as + +$$QP_Y = ( ( QP_{Y,PREV} + mb\_qp\_delta + 52 + 2 * QpBdOffset_Y ) \% ( 52 + QpBdOffset_Y ) ) - QpBdOffset_Y \quad (7-39)$$ + +where $QP_{Y,PREV}$ is the luma quantization parameter, $QP_Y$ , of the previous macroblock in decoding order in the current slice. For the first macroblock in the slice $QP_{Y,PREV}$ is initially set equal to $SliceQP_Y$ derived in Equation 7-32 at the start of each slice. + +The value of $QP'_Y$ is derived as + +$$QP'_Y = QP_Y + QpBdOffset_Y \quad (7-40)$$ + +The variable TransformBypassModeFlag is derived as follows: + +- If `qpprime_y_zero_transform_bypass_flag` is equal to 1 and $QP'_Y$ is equal to 0, TransformBypassModeFlag is set equal to 1. +- Otherwise (`qpprime_y_zero_transform_bypass_flag` is equal to 0 or $QP'_Y$ is not equal to 0), TransformBypassModeFlag is set equal to 0. + +#### 7.4.5.1 Macroblock prediction semantics + +All samples of the macroblock are predicted. The prediction modes are derived using the following syntax elements. + +`prev_intra4x4_pred_mode_flag[ luma4x4BlkIdx ]` and `rem_intra4x4_pred_mode[ luma4x4BlkIdx ]` specify the Intra\_4x4 prediction of the 4x4 luma block with index `luma4x4BlkIdx = 0..15`. When `ChromaArrayType` is equal to 3, `prev_intra4x4_pred_mode_flag[ luma4x4BlkIdx ]` and `rem_intra4x4_pred_mode[ luma4x4BlkIdx ]` also specify the Intra\_4x4 prediction of the 4x4 Cb block with `luma4x4BlkIdx` equal to `cb4x4BlkIdx` for `cb4x4BlkIdx = 0..15` and the Intra\_4x4 prediction of the 4x4 Cr block with `luma4x4BlkIdx` equal to `cr4x4BlkIdx` for `cr4x4BlkIdx = 0..15`. + +`prev_intra8x8_pred_mode_flag[ luma8x8BlkIdx ]` and `rem_intra8x8_pred_mode[ luma8x8BlkIdx ]` specify the Intra\_8x8 prediction of the 8x8 luma block with index `luma8x8BlkIdx = 0..3`. When `ChromaArrayType` is equal to 3, `prev_intra8x8_pred_mode_flag[ luma8x8BlkIdx ]` and `rem_intra8x8_pred_mode[ luma8x8BlkIdx ]` also specify the Intra\_8x8 prediction of the 8x8 Cb block with `luma8x8BlkIdx` equal to `cb8x8BlkIdx` for `cb8x8BlkIdx = 0..3` and the Intra\_8x8 prediction of the 8x8 Cr block with index `luma8x8BlkIdx` equal to `cr8x8BlkIdx` for `cr8x8BlkIdx = 0..3`. + +`intra_chroma_pred_mode` specifies, when `ChromaArrayType` is equal to 1 or 2, the type of spatial prediction used for chroma in macroblocks using Intra\_4x4, Intra\_8x8, or Intra\_16x16 prediction, as shown in Table 7-16. The value of `intra_chroma_pred_mode` shall be in the range of 0 to 3, inclusive. + +Table 7-16 – Relationship between `intra_chroma_pred_mode` and spatial prediction modes + +| intra_chroma_pred_mode | Intra Chroma Prediction Mode | +|-------------------------------------|------------------------------| +| 0 | DC | +| 1 | Horizontal | +| 2 | Vertical | +| 3 | Plane | + +`ref_idx_10[ mbPartIdx ]` when present, specifies the index in reference picture list 0 of the reference picture to be used for prediction. + +The range of `ref_idx_10[ mbPartIdx ]`, the index in list 0 of the reference picture, and, if applicable, the parity of the field within the reference picture used for prediction are specified as follows: + +- If `MbaffFrameFlag` is equal to 0 or `mb_field_decoding_flag` is equal to 0, the value of `ref_idx_10[ mbPartIdx ]` shall be in the range of 0 to `num_ref_idx_10_active_minus1`, inclusive. +- Otherwise (`MbaffFrameFlag` is equal to 1 and `mb_field_decoding_flag` is equal to 1), the value of `ref_idx_10[ mbPartIdx ]` shall be in the range of 0 to $2 * \text{num\_ref\_idx\_10\_active\_minus1} + 1$ , inclusive. + +When only one reference picture is used for inter prediction, the values of `ref_idx_10[ mbPartIdx ]` shall be inferred to be equal to 0. + +`ref_idx_11[ mbPartIdx ]` has the same semantics as `ref_idx_10`, with 10 and list 0 replaced by 11 and list 1, respectively. + +`mvd_10[ mbPartIdx ][ 0 ][ compIdx ]` specifies the difference between a list 0 motion vector component to be used and its prediction. The index `mbPartIdx` specifies to which macroblock partition `mvd_10` is assigned. The partitioning of the macroblock is specified by `mb_type`. The horizontal motion vector component difference is decoded first in decoding order and is assigned `compIdx = 0`. The vertical motion vector component is decoded second in decoding order and is assigned `compIdx = 1`. The value of `mvd_10[ mbPartIdx ][ 0 ][ compIdx ]` shall be in the range of $-8192$ to $8191.75$ , inclusive. The range of `mvd_10[ mbPartIdx ][ 0 ][ compIdx ]` is also constrained indirectly by constraints on the motion vector variable values derived from it as specified in Annex A. + +`mvd_11[ mbPartIdx ][ 0 ][ compIdx ]` has the same semantics as `mvd_10`, with 10 and list 0 replaced by 11 and list 1, respectively. + +### 7.4.5.2 Sub-macroblock prediction semantics + +**sub\_mb\_type[ mbPartIdx ]** specifies the sub-macroblock types. + +Tables and semantics are specified for the various sub-macroblock types for P, and B macroblock types. Each table presents the value of **sub\_mb\_type[ mbPartIdx ]**, the name of **sub\_mb\_type[ mbPartIdx ]**, the number of sub-macroblock partitions used (given by the **NumSubMbPart( sub\_mb\_type[ mbPartIdx ] )** function), and the prediction mode of the sub-macroblock (given by the **SubMbPredMode( sub\_mb\_type[ mbPartIdx ] )** function). In the text, the value of **sub\_mb\_type[ mbPartIdx ]** may be referred to by "sub-macroblock type". In the text, the value of **SubMbPredMode( )** may be referred to by "sub-macroblock prediction mode" or "macroblock partition prediction mode". + +The interpretation of **sub\_mb\_type[ mbPartIdx ]** for P macroblock types is specified in Table 7-17, where the row for "inferred" specifies values inferred when **sub\_mb\_type[ mbPartIdx ]** is not present. + +**Table 7-17 – Sub-macroblock types in P macroblocks** + +| sub_mb_type[ mbPartIdx ] | Name of sub_mb_type[ mbPartIdx ] | NumSubMbPart ( sub_mb_type[ mbPartIdx ] ) | SubMbPredMode ( sub_mb_type[ mbPartIdx ] ) | SubMbPartWidth ( sub_mb_type[ mbPartIdx ] ) | SubMbPartHeight ( sub_mb_type[ mbPartIdx ] ) | +|---------------------------------|-----------------------------------------|--------------------------------------------------|---------------------------------------------------|----------------------------------------------------|-----------------------------------------------------| +| inferred | na | na | na | na | na | +| 0 | P_L0_8x8 | 1 | Pred_L0 | 8 | 8 | +| 1 | P_L0_8x4 | 2 | Pred_L0 | 8 | 4 | +| 2 | P_L0_4x8 | 2 | Pred_L0 | 4 | 8 | +| 3 | P_L0_4x4 | 4 | Pred_L0 | 4 | 4 | + +The following semantics are assigned to the sub-macroblock types in Table 7-17: + +- **P\_L0\_MxN**, with **MxN** being replaced by 8x8, 8x4, 4x8, or 4x4: the samples of the sub-macroblock are predicted using one luma partition of size **MxN** equal to 8x8, two luma partitions of size **MxN** equal to 8x4, or two luma partitions of size **MxN** equal to 4x8, or four luma partitions of size **MxN** equal to 4x4, and associated chroma samples, respectively. + +The following semantics are assigned to the sub-macroblock prediction modes (or macroblock partition prediction modes) specified by **SubMbPredMode( )** in Table 7-17: + +- **Pred\_L0**: see semantics for Table 7-13. + +The interpretation of sub\_mb\_type[ mbPartIdx ] for B macroblock types is specified in Table 7-18, where the row for "inferred" specifies values inferred when sub\_mb\_type[ mbPartIdx ] is not present, and the inferred value "mb\_type" specifies that the name of sub\_mb\_type[ mbPartIdx ] is the same as the name of mb\_type for this case. + +**Table 7-18 – Sub-macroblock types in B macroblocks** + +| sub_mb_type[ mbPartIdx ] | Name of sub_mb_type[ mbPartIdx ] | NumSubMbPart ( sub_mb_type[ mbPartIdx ] ) | SubMbPredMode ( sub_mb_type[ mbPartIdx ] ) | SubMbPartWidth ( sub_mb_type[ mbPartIdx ] ) | SubMbPartHeight ( sub_mb_type[ mbPartIdx ] ) | +|--------------------------|----------------------------------|-------------------------------------------|--------------------------------------------|---------------------------------------------|----------------------------------------------| +| inferred | mb_type | 4 | Direct | 4 | 4 | +| 0 | B_Direct_8x8 | 4 | Direct | 4 | 4 | +| 1 | B_L0_8x8 | 1 | Pred_L0 | 8 | 8 | +| 2 | B_L1_8x8 | 1 | Pred_L1 | 8 | 8 | +| 3 | B_Bi_8x8 | 1 | BiPred | 8 | 8 | +| 4 | B_L0_8x4 | 2 | Pred_L0 | 8 | 4 | +| 5 | B_L0_4x8 | 2 | Pred_L0 | 4 | 8 | +| 6 | B_L1_8x4 | 2 | Pred_L1 | 8 | 4 | +| 7 | B_L1_4x8 | 2 | Pred_L1 | 4 | 8 | +| 8 | B_Bi_8x4 | 2 | BiPred | 8 | 4 | +| 9 | B_Bi_4x8 | 2 | BiPred | 4 | 8 | +| 10 | B_L0_4x4 | 4 | Pred_L0 | 4 | 4 | +| 11 | B_L1_4x4 | 4 | Pred_L1 | 4 | 4 | +| 12 | B_Bi_4x4 | 4 | BiPred | 4 | 4 | + +The following semantics are assigned to the sub-macroblock types in Table 7-18: + +- B\_Skip and B\_Direct\_16x16: no motion vector differences or reference indices are present for the sub-macroblock in the bitstream. The functions SubMbPartWidth( ) and SubMbPartHeight( ) are used in the derivation process for motion vectors and reference frame indices in clause 8.4.1 for direct mode prediction. +- B\_Direct\_8x8: no motion vector differences or reference indices are present for the sub-macroblock in the bitstream. The functions SubMbPartWidth( B\_Direct\_8x8 ) and SubMbPartHeight( B\_Direct\_8x8 ) are used in the derivation process for motion vectors and reference frame indices in clause 8.4.1 for direct mode prediction. +- B\_X\_MxN, with X being replaced by L0, L1, or Bi, and MxN being replaced by 8x8, 8x4, 4x8 or 4x4: the samples of the sub-macroblock are predicted using one luma partition of size MxN equal to 8x8, or the samples of the sub-macroblock are predicted using two luma partitions of size MxN equal to 8x4, or the samples of the sub-macroblock are predicted using two luma partitions of size MxN equal to 4x8, or the samples of the sub-macroblock are predicted using four luma partitions of size MxN equal to 4x4, and associated chroma samples, respectively. All sub-macroblock partitions share the same reference index. For an MxN sub-macroblock partition in a sub-macroblock with sub\_mb\_type[ mbPartIdx ] being B\_X\_MxN with X being replaced by either L0 or L1, one motion vector difference is present in the bitstream. For an MxN sub-macroblock partition in a sub-macroblock with sub\_mb\_type[ mbPartIdx ] being B\_Bi\_MxN, two motion vector difference are present in the bitstream. + +The following semantics are assigned to the sub-macroblock prediction modes (or macroblock partition prediction modes) specified by SubMbPredMode( ) in Table 7-18: + +- Direct: see semantics for Table 7-14. +- Pred\_L0: see semantics for Table 7-13. +- Pred\_L1: see semantics for Table 7-14. +- BiPred: see semantics for Table 7-14. + +**ref\_idx\_10[ mbPartIdx ]** has the same semantics as ref\_idx\_10 in clause 7.4.5.1. + +**ref\_idx\_11[ mbPartIdx ]** has the same semantics as ref\_idx\_11 in clause 7.4.5.1. + +**mvd\_10[ mbPartIdx ][ subMbPartIdx ][ compIdx ]** has the same semantics as mvd\_10 in clause 7.4.5.1, except that it is applied to the sub-macroblock partition index with subMbPartIdx. The indices mbPartIdx and subMbPartIdx specify to which macroblock partition and sub-macroblock partition mvd\_10 is assigned. + +**mvd\_11[ mbPartIdx ][ subMbPartIdx ][ compIdx ]** has the same semantics as mvd\_11 in clause 7.4.5.1, except that it is applied to the sub-macroblock partition index with subMbPartIdx. The indices mbPartIdx and subMbPartIdx specify to which macroblock partition and sub-macroblock partition mvd\_11 is assigned. + +#### 7.4.5.3 Residual data semantics + +The syntax structure residual\_block( ), which is used for parsing the transform coefficient levels, is assigned as follows: + +- If entropy\_coding\_mode\_flag is equal to 0, residual\_block is set equal to residual\_block\_cavlc, which is used for parsing the syntax elements for transform coefficient levels. +- Otherwise (entropy\_coding\_mode\_flag is equal to 1), residual\_block is set equal to residual\_block\_cabac, which is used for parsing the syntax elements for transform coefficient levels. + +The syntax structure residual\_luma( i16x16DCLevel, i16x16ACLevel, level4x4, level8x8, startIdx, endIdx ) is used with the first four variables in brackets being its output and being assigned as follows. + +Intra16x16DCLevel is set equal to i16x16DCLevel, Intra16x16ACLevel is set equal to i16x16ACLevel, LumaLevel4x4 is set equal to level4x4, and LumaLevel8x8 is set equal to level8x8. + +When ChromaArrayType is equal to 1 or 2, the following applies: + +- For each chroma component, indexed by iCbCr = 0..1, the DC transform coefficient levels of the 4 \* NumC8x8 4x4 chroma blocks are parsed into the iCbCr-th list ChromaDCLevel[ iCbCr ]. +- For each of the 4x4 chroma blocks, indexed by i4x4 = 0..3 and i8x8 = 0..NumC8x8 – 1, of each chroma component, indexed by iCbCr = 0..1, the 15 AC transform coefficient levels are parsed into the (i8x8\*4 + i4x4)-th list of the iCbCr-th chroma component ChromaACLevel[ iCbCr ][ i8x8\*4 + i4x4 ]. + +When ChromaArrayType is equal to 3, the following applies: + +- The syntax structure residual\_luma( i16x16DCLevel, i16x16ACLevel, level4x4, level8x8, startIdx, endIdx ) is used for the Cb component with the first four variables in brackets being its output and being assigned as follows. CbIntra16x16DCLevel is set equal to i16x16DCLevel, CbIntra16x16ACLevel is set equal to i16x16ACLevel, CbLevel4x4 is set equal to level4x4, and CbLevel8x8 is set equal to level8x8. +- The syntax structure residual\_luma( i16x16DCLevel, i16x16ACLevel, level4x4, level8x8, startIdx, endIdx ) is used for the Cr component with the first four variables in brackets being its output and being assigned as follows. CrIntra16x16DCLevel is set equal to i16x16DCLevel, CrIntra16x16ACLevel is set equal to i16x16ACLevel, CrLevel4x4 is set equal to level4x4, and CrLevel8x8 is set equal to level8x8. + +##### 7.4.5.3.1 Residual luma data semantics + +Output of this syntax structure are the variables i16x16DCLevel, i16x16ACLevel, level4x4, and level8x8. + +Depending on mb\_type, the syntax structure residual\_block( coeffLevel, startIdx, endIdx, maxNumCoeff ) is used with the arguments coeffLevel, which is a list containing the maxNumCoeff transform coefficient levels that are parsed in residual\_block( ), startIdx, endIdx, and maxNumCoeff as follows. + +Depending on MbPartPredMode( mb\_type, 0 ), the following applies: + +- If MbPartPredMode( mb\_type, 0 ) is equal to Intra\_16x16, the transform coefficient levels are parsed into the list i16x16DCLevel and into the 16 lists i16x16ACLevel[ i ]. i16x16DCLevel contains the 16 transform coefficient levels + +of the DC transform coefficient levels for each 4x4 luma block. For each of the 16 4x4 luma blocks indexed by $i = 0..15$ , the 15 AC transform coefficients levels of the $i$ -th block are parsed into the $i$ -th list $i16x16AClevel[ i ]$ . + +- Otherwise (`MbPartPredMode( mb_type, 0 )` is not equal to `Intra_16x16`), the following applies: + - If `transform_size_8x8_flag` is equal to 0, for each of the 16 4x4 luma blocks indexed by $i = 0..15$ , the 16 transform coefficient levels of the $i$ -th block are parsed into the $i$ -th list `level4x4[ i ]`. + - Otherwise (`transform_size_8x8_flag` is equal to 1), for each of the 4 8x8 luma blocks indexed by $i8x8 = 0..3$ , the following applies: + - If `entropy_coding_mode_flag` is equal to 0, first for each of the 4 4x4 luma blocks indexed by $i4x4 = 0..3$ , the 16 transform coefficient levels of the $i4x4$ -th block are parsed into the $(i8x8 * 4 + i4x4)$ -th list `level4x4[ i8x8 * 4 + i4x4 ]`. Then, the 64 transform coefficient levels of the $i8x8$ -th 8x8 luma block which are indexed by $4 * i + i4x4$ , where $i = 0..15$ and $i4x4 = 0..3$ , are derived as `level8x8[ i8x8 ][ 4 * i + i4x4 ] = level4x4[ i8x8 * 4 + i4x4 ][ i ]`. +NOTE – The 4x4 luma blocks with `luma4x4BlkIdx = i8x8 * 4 + i4x4` containing every fourth transform coefficient level of the corresponding $i8x8$ -th 8x8 luma block with offset $i4x4$ are assumed to represent spatial locations given by the inverse 4x4 luma block scanning process in clause 6.4.3. + - Otherwise (`entropy_coding_mode_flag` is equal to 1), the 64 transform coefficient levels of the $i8x8$ -th block are parsed into the $i8x8$ -th list `level8x8[ i8x8 ]`. + +#### 7.4.5.3.2 Residual block CAVLC semantics + +The function `TotalCoeff( coeff_token )` that is used in clause 7.3.5.3.2 returns the number of non-zero transform coefficient levels derived from `coeff_token`. + +The function `TrailingOnes( coeff_token )` that is used in clause 7.3.5.3.2 returns the trailing ones derived from `coeff_token`. + +**coeff\_token** specifies the total number of non-zero transform coefficient levels and the number of trailing one transform coefficient levels in a transform coefficient level scan. A trailing one transform coefficient level is one of up to three consecutive non-zero transform coefficient levels having an absolute value equal to 1 at the end of a scan of non-zero transform coefficient levels. The range of `coeff_token` is specified in clause 9.2.1. + +**trailing\_ones\_sign\_flag** specifies the sign of a trailing one transform coefficient level as follows: + +- If `trailing_ones_sign_flag` is equal to 0, the corresponding transform coefficient level is decoded as $+1$ . +- Otherwise (`trailing_ones_sign_flag` equal to 1), the corresponding transform coefficient level is decoded as $-1$ . + +**level\_prefix** and **level\_suffix** specify the value of a non-zero transform coefficient level. The range of `level_prefix` and `level_suffix` is specified in clause 9.2.2. + +**total\_zeros** specifies the total number of zero-valued transform coefficient levels that are located before the position of the last non-zero transform coefficient level in a scan of transform coefficient levels. The range of `total_zeros` is specified in clause 9.2.3. + +**run\_before** specifies the number of consecutive transform coefficient levels in the scan with zero value before a non-zero valued transform coefficient level. The range of `run_before` is specified in clause 9.2.3. + +`coeffLevel` contains `maxNumCoeff` transform coefficient levels for the current list of transform coefficient levels. + +#### 7.4.5.3.3 Residual block CABAC semantics + +**coded\_block\_flag** specifies whether the transform block contains non-zero transform coefficient levels as follows: + +- If `coded_block_flag` is equal to 0, the transform block contains no non-zero transform coefficient levels. +- Otherwise (`coded_block_flag` is equal to 1), the transform block contains at least one non-zero transform coefficient level. + +When `coded_block_flag` is not present, it shall be inferred to be equal to 1. + +**significant\_coeff\_flag[ i ]** specifies whether the transform coefficient level at scanning position $i$ is non-zero as follows: + +- If `significant_coeff_flag[ i ]` is equal to 0, the transform coefficient level at scanning position $i$ is set equal to 0; +- Otherwise (`significant_coeff_flag[ i ]` is equal to 1), the transform coefficient level at scanning position $i$ has a non-zero value. + +**last\_significant\_coeff\_flag[ i ]** specifies for the scanning position i whether there are non-zero transform coefficient levels for subsequent scanning positions i + 1 to maxNumCoeff – 1 as follows: + +- If last\_significant\_coeff\_flag[ i ] is equal to 1, all following transform coefficient levels (in scanning order) of the block have value equal to 0. +- Otherwise (last\_significant\_coeff\_flag[ i ] is equal to 0), there are further non-zero transform coefficient levels along the scanning path. + +**coeff\_abs\_level\_minus1[ i ]** is the absolute value of a transform coefficient level minus 1. The value of coeff\_abs\_level\_minus1 is constrained by the limits in clause 8.5. + +**coeff\_sign\_flag[ i ]** specifies the sign of a transform coefficient level as follows: + +- If coeff\_sign\_flag is equal to 0, the corresponding transform coefficient level has a positive value. +- Otherwise (coeff\_sign\_flag is equal to 1), the corresponding transform coefficient level has a negative value. + +coeffLevel contains maxNumCoeff transform coefficient levels for the current list of transform coefficient levels. + +## 8 Decoding process + +Outputs of this process are decoded samples of the current picture (sometimes referred to by the variable CurrPic). + +Depending on the value of chroma\_format\_idc, the number of sample arrays of the current picture is as follows: + +- If chroma\_format\_idc is equal to 0, the current picture consists of 1 sample array $S_L$ . +- Otherwise (chroma\_format\_idc is not equal to 0), the current picture consists of 3 sample arrays $S_L$ , $S_{Cb}$ , $S_{Cr}$ . + +This clause describes the decoding process, given syntax elements and upper-case variables from clause 7. + +The decoding process is specified such that all decoders shall produce numerically identical results. Any decoding process that produces identical results to the process described here conforms to the decoding process requirements of this Recommendation | International Standard. + +Each picture referred to in this clause is a complete primary coded picture or part of a primary coded picture. Each slice referred to in this clause is a slice of a primary coded picture. Each slice data partition referred to in this clause is a slice data partition of a primary coded picture. + +Depending on the value of separate\_colour\_plane\_flag, the decoding process is structured as follows: + +- If separate\_colour\_plane\_flag is equal to 0, the decoding process is invoked a single time with the current picture being the output. +- Otherwise (separate\_colour\_plane\_flag is equal to 1), the decoding process is invoked three times. Inputs to the decoding process are all NAL units of the primary coded picture with identical value of colour\_plane\_id. The decoding process of NAL units with a particular value of colour\_plane\_id is specified as if only a coded video sequence with monochrome colour format with that particular value of colour\_plane\_id would be present in the bitstream. The output of each of the three decoding processes is assigned to the 3 sample arrays of the current picture with the NAL units with colour\_plane\_id equal to 0 being assigned to $S_L$ , the NAL units with colour\_plane\_id equal to 1 being assigned to $S_{Cb}$ , and the NAL units with colour\_plane\_id equal to 2 being assigned to $S_{Cr}$ . + +NOTE – The variable ChromaArrayType is derived as 0 when separate\_colour\_plane\_flag is equal to 1 and chroma\_format\_idc is equal to 3. In the decoding process, the value of this variable is evaluated resulting in operations identical to that of monochrome pictures with chroma\_format\_idc being equal to 0. + +An overview of the decoding process is given as follows: + +1. The decoding of NAL units is specified in clause 8.1. +2. The processes in clause 8.2 specify decoding processes using syntax elements in the slice layer and above: + - Variables and functions relating to picture order count are derived in clause 8.2.1. (only needed to be invoked for one slice of a picture) + - Variables and functions relating to the macroblock to slice group map are derived in clause 8.2.2. (only needed to be invoked for one slice of a picture) + - The method of combining the various slice data partitions when slice data partitioning is used is described in clause 8.2.3. + +- When the frame\_num of the current picture is not equal to PrevRefFrameNum and is not equal to ( PrevRefFrameNum + 1 ) % MaxFrameNum, the decoding process for gaps in frame\_num is performed according to clause 8.2.5.2 prior to the decoding of any slices of the current picture. + - At the beginning of the decoding process for each P, SP, or B slice, the decoding process for reference picture lists construction specified in clause 8.2.4 is invoked for derivation of reference picture list 0 (RefPicList0), and when decoding a B slice, reference picture list 1 (RefPicList1). + - When the current picture is a reference picture and after all slices of the current picture have been decoded, the decoded reference picture marking process in clause 8.2.5 specifies how the current picture is used in the decoding process of inter prediction in later decoded pictures. +3. The processes in clauses 8.3, 8.4, 8.5, 8.6, and 8.7 specify decoding processes using syntax elements in the macroblock layer and above. +- The intra prediction process for I and SI macroblocks, except for I\_PCM macroblocks as specified in clause 8.3, has intra prediction samples as its output. For I\_PCM macroblocks clause 8.3 directly specifies a picture construction process. The output are constructed samples prior to the deblocking filter process. + - The inter prediction process for P and B macroblocks is specified in clause 8.4 with inter prediction samples being the output. + - The transform coefficient decoding process and picture construction process prior to deblocking filter process are specified in clause 8.5. That process derives samples for I and B macroblocks and for P macroblocks in P slices. The output are constructed samples prior to the deblocking filter process. + - The decoding process for P macroblocks in SP slices or SI macroblocks is specified in clause 8.6. That process derives samples for P macroblocks in SP slices and for SI macroblocks. The output are constructed samples prior to the deblocking filter process. + - The constructed samples prior to the deblocking filter process that are next to the edges of blocks and macroblocks are processed by a deblocking filter as specified in clause 8.7 with the output being the decoded samples. + +## 8.1 NAL unit decoding process + +Inputs to this process are NAL units. + +Outputs of this process are the RBSP syntax structures encapsulated within the NAL units. + +The decoding process for each NAL unit extracts the RBSP syntax structure from the NAL unit and then operates the decoding processes specified for the RBSP syntax structure in the NAL unit as follows. + +Clause 8.2 describes the decoding process for NAL units with nal\_unit\_type equal to 1 through 5. + +Clause 8.3 describes the decoding process for a macroblock or part of a macroblock coded in NAL units with nal\_unit\_type equal to 1, 2, and 5. + +Clause 8.4 describes the decoding process for a macroblock or part of a macroblock coded in NAL units with nal\_unit\_type equal to 1 and 2. + +Clause 8.5 describes the decoding process for a macroblock or part of a macroblock coded in NAL units with nal\_unit\_type equal to 1 and 3 to 5. + +Clause 8.6 describes the decoding process for a macroblock or part of a macroblock coded in NAL units with nal\_unit\_type equal to 1 and 3 to 5. + +Clause 8.7 describes the decoding process for a macroblock or part of a macroblock coded in NAL units with nal\_unit\_type equal to 1 to 5. + +NAL units with nal\_unit\_type equal to 7 and 8 contain sequence parameter sets and picture parameter sets, respectively. Picture parameter sets are used in the decoding processes of other NAL units as determined by reference to a picture parameter set within the slice headers of each picture. Sequence parameter sets are used in the decoding processes of other NAL units as determined by reference to a sequence parameter set within the picture parameter sets of each sequence. + +No normative decoding process is specified for NAL units with nal\_unit\_type equal to 6, 9, 10, 11, and 12. + +## 8.2 Slice decoding process + +### 8.2.1 Decoding process for picture order count + +Outputs of this process are TopFieldOrderCnt (if applicable) and BottomFieldOrderCnt (if applicable). + +Picture order counts are used to determine initial picture orderings for reference pictures in the decoding of B slices (see clauses 8.2.4.2.3 and 8.2.4.2.4), to determine co-located pictures (see clause 8.4.1.2.1) for deriving motion parameters in temporal or spatial direct mode, to represent picture order differences between frames or fields for motion vector derivation in temporal direct mode (see clause 8.4.1.2.3), for implicit mode weighted prediction in B slices (see clause 8.4.2.3.2), and for decoder conformance checking (see clause C.4). + +Picture order count information is derived for every frame, field (whether decoded from a coded field or as a part of a decoded frame), or complementary field pair as follows: + +- Each coded frame is associated with two picture order counts, called TopFieldOrderCnt and BottomFieldOrderCnt for its top field and bottom field, respectively. +- Each coded field is associated with a picture order count, called TopFieldOrderCnt for a coded top field and BottomFieldOrderCnt for a bottom field. +- Each complementary field pair is associated with two picture order counts, which are the TopFieldOrderCnt for its coded top field and the BottomFieldOrderCnt for its coded bottom field, respectively. + +TopFieldOrderCnt and BottomFieldOrderCnt indicate the picture order of the corresponding top field or bottom field relative to the first output field of the previous IDR picture or the previous reference picture including a memory\_management\_control\_operation equal to 5 in decoding order. + +TopFieldOrderCnt and BottomFieldOrderCnt are derived by invoking one of the decoding processes for picture order count type 0, 1, and 2 in clauses 8.2.1.1, 8.2.1.2, and 8.2.1.3, respectively. When the current picture includes a memory\_management\_control\_operation equal to 5, after the decoding of the current picture, tempPicOrderCnt is set equal to PicOrderCnt( CurrPic ), TopFieldOrderCnt of the current picture (if any) is set equal to TopFieldOrderCnt – tempPicOrderCnt, and BottomFieldOrderCnt of the current picture (if any) is set equal to BottomFieldOrderCnt – tempPicOrderCnt. + +NOTE 1 – When the decoding process for a picture currPic that includes a memory\_management\_control\_operation equal to 5 refers to the values of TopFieldOrderCnt (if applicable) or BottomFieldOrderCnt (if applicable) for the picture currPic (including references to the function PicOrderCnt( ) with the picture currPic as the argument and references to the function DiffPicOrderCnt( ) with one of the arguments being currPic), the values of TopFieldOrderCnt (if applicable) and BottomFieldOrderCnt (if applicable) that are derived as specified in clauses 8.2.1.1, 8.2.1.2, and 8.2.1.3 for the picture currPic are used. When the decoding process for a picture refers to the values TopFieldOrderCnt (if applicable) or BottomFieldOrderCnt (if applicable) of the previous picture prevMmco5Pic in decoding order that includes a memory\_management\_control\_operation equal to 5 (including references via the functions PicOrderCnt( ) or DiffPicOrderCnt( )), the values of TopFieldOrderCnt (if applicable) and BottomFieldOrderCnt (if applicable) that are used for the picture prevMmco5Pic are the values after the modification specified in the paragraph above (resulting in TopFieldOrderCnt and/or BottomFieldOrderCnt equal to 0). + +The bitstream shall not contain data that result in Min( TopFieldOrderCnt, BottomFieldOrderCnt ) not equal to 0 for a coded IDR frame, TopFieldOrderCnt not equal to 0 for a coded IDR top field, or BottomFieldOrderCnt not equal to 0 for a coded IDR bottom field. Thus, at least one of TopFieldOrderCnt and BottomFieldOrderCnt shall be equal to 0 for the fields of a coded IDR frame. + +When the current picture is not an IDR picture, the following applies: + +- 1) Consider the list variable listD containing as elements the TopFieldOrderCnt and BottomFieldOrderCnt values associated with the list of pictures including all of the following: + - a. The first picture in the list is the previous picture of any of the following types: + - an IDR picture, + - a picture containing a memory\_management\_control\_operation equal to 5. + - b. The following additional pictures: + - If pic\_order\_cnt\_type is equal to 0, all other pictures that follow in decoding order after the first picture in the list and are not "non-existing" frames inferred by the decoding process for gaps in frame\_num specified in clause 8.2.5.2 and either precede the current picture in decoding order or are the current picture. When pic\_order\_cnt\_type is equal to 0 and the current picture is not a "non-existing" frame inferred by the decoding process for gaps in frame\_num specified in clause 8.2.5.2, the current picture is included in listD prior to the invoking of the decoded reference picture marking process. + +- Otherwise (pic\_order\_cnt\_type is not equal to 0), all other pictures that follow in decoding order after the first picture in the list and either precede the current picture in decoding order or are the current picture. When pic\_order\_cnt\_type is not equal to 0, the current picture is included in listD prior to the invoking of the decoded reference picture marking process. +- 2) Consider the list variable listO which contains the elements of listD sorted in ascending order. listO shall not contain any of the following: +- a pair of TopFieldOrderCnt and BottomFieldOrderCnt for a frame or complementary field pair that are not at consecutive positions in listO, + - a TopFieldOrderCnt that has a value equal to another TopFieldOrderCnt, + - a BottomFieldOrderCnt that has a value equal to another BottomFieldOrderCnt, + - a BottomFieldOrderCnt that has a value equal to a TopFieldOrderCnt unless the BottomFieldOrderCnt and TopFieldOrderCnt belong to the same coded frame or complementary field pair. + +The bitstream shall not contain data that result in values of TopFieldOrderCnt, BottomFieldOrderCnt, PicOrderCntMsb, or FrameNumOffset used in the decoding process as specified in clauses 8.2.1.1 to 8.2.1.3 that exceed the range of values from $-2^{31}$ to $2^{31} - 1$ , inclusive. + +The function PicOrderCnt( picX ) is specified as follows: + +``` + +if( picX is a frame or a complementary field pair ) + PicOrderCnt( picX ) = Min( TopFieldOrderCnt, BottomFieldOrderCnt ) of the frame or complementary field pair picX +else if( picX is a top field ) + PicOrderCnt( picX ) = TopFieldOrderCnt of field picX +else if( picX is a bottom field ) + PicOrderCnt( picX ) = BottomFieldOrderCnt of field picX + +``` + +(8-1) + +Then DiffPicOrderCnt( picA, picB ) is specified as follows: + +$$\text{DiffPicOrderCnt( picA, picB )} = \text{PicOrderCnt( picA )} - \text{PicOrderCnt( picB )} \quad (8-2)$$ + +The bitstream shall not contain data that result in values of DiffPicOrderCnt( picA, picB ) used in the decoding process that exceed the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. + +NOTE 2 – Let X be the current picture and Y and Z be two other pictures in the same sequence, Y and Z are considered to be in the same output order direction from X when both DiffPicOrderCnt( X, Y ) and DiffPicOrderCnt( X, Z ) are positive or both are negative. + +NOTE 3 – Many encoders assign TopFieldOrderCnt and BottomFieldOrderCnt proportional to the sampling time of the corresponding field (which is either a coded field or a field of a coded frame) relative to the sampling time of the first output field of the previous IDR picture or the previous reference picture (in decoding order) that includes a memory\_management\_control\_operation equal to 5. + +When the current picture includes a memory\_management\_control\_operation equal to 5, PicOrderCnt( CurrPic ) shall be greater than PicOrderCnt( any other picture in listD ). + +#### 8.2.1.1 Decoding process for picture order count type 0 + +This process is invoked when pic\_order\_cnt\_type is equal to 0. + +Input to this process is PicOrderCntMsb of the previous reference picture in decoding order as specified in this clause. + +Outputs of this process are either or both TopFieldOrderCnt or BottomFieldOrderCnt. + +The variables prevPicOrderCntMsb and prevPicOrderCntLsb are derived as follows: + +- If the current picture is an IDR picture, prevPicOrderCntMsb is set equal to 0 and prevPicOrderCntLsb is set equal to 0. +- Otherwise (the current picture is not an IDR picture), the following applies: + - If the previous reference picture in decoding order included a memory\_management\_control\_operation equal to 5, the following applies: + - If the previous reference picture in decoding order is not a bottom field, prevPicOrderCntMsb is set equal to 0 and prevPicOrderCntLsb is set equal to the value of TopFieldOrderCnt for the previous reference picture in decoding order. + +- Otherwise (the previous reference picture in decoding order is a bottom field), prevPicOrderCntMsb is set equal to 0 and prevPicOrderCntLsb is set equal to 0. +- Otherwise (the previous reference picture in decoding order did not include a memory\_management\_control\_operation equal to 5), prevPicOrderCntMsb is set equal to PicOrderCntMsb of the previous reference picture in decoding order and prevPicOrderCntLsb is set equal to the value of pic\_order\_cnt\_lsb of the previous reference picture in decoding order. + +PicOrderCntMsb of the current picture is derived as specified by the following pseudo-code: + +``` + +if( ( pic_order_cnt_lsb < prevPicOrderCntLsb ) && + ( ( prevPicOrderCntLsb - pic_order_cnt_lsb ) >= ( MaxPicOrderCntLsb / 2 ) ) ) + PicOrderCntMsb = prevPicOrderCntMsb + MaxPicOrderCntLsb +else if( ( pic_order_cnt_lsb > prevPicOrderCntLsb ) && + ( ( pic_order_cnt_lsb - prevPicOrderCntLsb ) > ( MaxPicOrderCntLsb / 2 ) ) ) + PicOrderCntMsb = prevPicOrderCntMsb - MaxPicOrderCntLsb +else + PicOrderCntMsb = prevPicOrderCntMsb + +``` + +When the current picture is not a bottom field, TopFieldOrderCnt is derived as + +$$\text{TopFieldOrderCnt} = \text{PicOrderCntMsb} + \text{pic\_order\_cnt\_lsb} \quad (8-4)$$ + +When the current picture is not a top field, BottomFieldOrderCnt is derived as specified by the following pseudo-code: + +``` + +if( !field_pic_flag ) + BottomFieldOrderCnt = TopFieldOrderCnt + delta_pic_order_cnt_bottom +else + BottomFieldOrderCnt = PicOrderCntMsb + pic_order_cnt_lsb + +``` + +### 8.2.1.2 Decoding process for picture order count type 1 + +This process is invoked when pic\_order\_cnt\_type is equal to 1. + +Input to this process is FrameNumOffset of the previous picture in decoding order as specified in this clause. + +Outputs of this process are either or both TopFieldOrderCnt or BottomFieldOrderCnt. + +The values of TopFieldOrderCnt and BottomFieldOrderCnt are derived as specified in this clause. Let prevFrameNum be equal to the frame\_num of the previous picture in decoding order. + +When the current picture is not an IDR picture, the variable prevFrameNumOffset is derived as follows: + +- If the previous picture in decoding order included a memory\_management\_control\_operation equal to 5, prevFrameNumOffset is set equal to 0. +- Otherwise (the previous picture in decoding order did not include a memory\_management\_control\_operation equal to 5), prevFrameNumOffset is set equal to the value of FrameNumOffset of the previous picture in decoding order. + +NOTE – When gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1, the previous picture in decoding order may be a "non-existing" frame inferred by the decoding process for gaps in frame\_num specified in clause 8.2.5.2. + +The variable FrameNumOffset is derived as specified by the following pseudo-code: + +``` + +if( IdrPicFlag == 1 ) + FrameNumOffset = 0 +else if( prevFrameNum > frame_num ) + FrameNumOffset = prevFrameNumOffset + MaxFrameNum +else + FrameNumOffset = prevFrameNumOffset + +``` + +The variable absFrameNum is derived as specified by the following pseudo-code: + +``` + +if( num_ref_frames_in_pic_order_cnt_cycle != 0 ) + absFrameNum = FrameNumOffset + frame_num +else + absFrameNum = 0 +if( nal_ref_idc == 0 && absFrameNum > 0 ) + absFrameNum = absFrameNum - 1 + +``` + +When $\text{absFrameNum} > 0$ , $\text{picOrderCntCycleCnt}$ and $\text{frameNumInPicOrderCntCycle}$ are derived as + +$$\begin{aligned}\text{picOrderCntCycleCnt} &= ( \text{absFrameNum} - 1 ) / \text{num\_ref\_frames\_in\_pic\_order\_cnt\_cycle} \\ \text{frameNumInPicOrderCntCycle} &= ( \text{absFrameNum} - 1 ) \% \text{num\_ref\_frames\_in\_pic\_order\_cnt\_cycle}\end{aligned}\quad (8-8)$$ + +The variable $\text{expectedPicOrderCnt}$ is derived as specified by the following pseudo-code: + +``` +if( absFrameNum > 0 ) { + expectedPicOrderCnt = picOrderCntCycleCnt * ExpectedDeltaPerPicOrderCntCycle + for( i = 0; i <= frameNumInPicOrderCntCycle; i++ ) + expectedPicOrderCnt = expectedPicOrderCnt + offset_for_ref_frame[ i ] +} else + expectedPicOrderCnt = 0 +if( nal_ref_idc == 0 ) + expectedPicOrderCnt = expectedPicOrderCnt + offset_for_non_ref_pic +``` + +(8-9) + +The variables $\text{TopFieldOrderCnt}$ or $\text{BottomFieldOrderCnt}$ are derived as specified by the following pseudo-code: + +``` +if( !field_pic_flag ) { + TopFieldOrderCnt = expectedPicOrderCnt + delta_pic_order_cnt[ 0 ] + BottomFieldOrderCnt = TopFieldOrderCnt + + offset_for_top_to_bottom_field + delta_pic_order_cnt[ 1 ] +} else if( !bottom_field_flag ) + TopFieldOrderCnt = expectedPicOrderCnt + delta_pic_order_cnt[ 0 ] +else + BottomFieldOrderCnt = expectedPicOrderCnt + offset_for_top_to_bottom_field + delta_pic_order_cnt[ 0 ] +``` + +(8-10) + +### 8.2.1.3 Decoding process for picture order count type 2 + +This process is invoked when $\text{pic_order_cnt_type}$ is equal to 2. + +Outputs of this process are either or both $\text{TopFieldOrderCnt}$ or $\text{BottomFieldOrderCnt}$ . + +Let $\text{prevFrameNum}$ be equal to the $\text{frame\_num}$ of the previous picture in decoding order. + +When the current picture is not an IDR picture, the variable $\text{prevFrameNumOffset}$ is derived as follows: + +- If the previous picture in decoding order included a $\text{memory\_management\_control\_operation}$ equal to 5, $\text{prevFrameNumOffset}$ is set equal to 0. +- Otherwise (the previous picture in decoding order did not include a $\text{memory\_management\_control\_operation}$ equal to 5), $\text{prevFrameNumOffset}$ is set equal to the value of $\text{FrameNumOffset}$ of the previous picture in decoding order. + +NOTE 1 – When $\text{gaps\_in\_frame\_num\_value\_allowed\_flag}$ is equal to 1, the previous picture in decoding order may be a "non-existing" frame inferred by the decoding process for gaps in $\text{frame\_num}$ specified in clause 8.2.5.2. + +The variable $\text{FrameNumOffset}$ is derived as specified by the following pseudo-code: + +``` +if( IdrPicFlag == 1 ) + FrameNumOffset = 0 +else if( prevFrameNum > frame_num ) + FrameNumOffset = prevFrameNumOffset + MaxFrameNum +else + FrameNumOffset = prevFrameNumOffset +``` + +(8-11) + +The variable $\text{tempPicOrderCnt}$ is derived as specified by the following pseudo-code: + +``` +if( IdrPicFlag == 1 ) + tempPicOrderCnt = 0 +else if( nal_ref_idc == 0 ) + tempPicOrderCnt = 2 * ( FrameNumOffset + frame_num ) - 1 +else + tempPicOrderCnt = 2 * ( FrameNumOffset + frame_num ) +``` + +(8-12) + +The variables TopFieldOrderCnt or BottomFieldOrderCnt are derived as specified by the following pseudo-code: + +``` + +if( !field_pic_flag ) { + TopFieldOrderCnt = tempPicOrderCnt + BottomFieldOrderCnt = tempPicOrderCnt +} else if( bottom_field_flag ) + BottomFieldOrderCnt = tempPicOrderCnt +else + TopFieldOrderCnt = tempPicOrderCnt + +``` + +(8-13) + +NOTE 2 – Picture order count type 2 cannot be used in a coded video sequence that contains consecutive non-reference pictures that would result in more than one of these pictures having the same value of TopFieldOrderCnt or more than one of these pictures having the same value of BottomFieldOrderCnt. + +NOTE 3 – Picture order count type 2 results in an output order that is the same as the decoding order. + +## 8.2.2 Decoding process for macroblock to slice group map + +Inputs to this process are the active picture parameter set and the slice header of the slice to be decoded. + +Output of this process is a macroblock to slice group map MbToSliceGroupMap. + +This process is invoked at the start of every slice. + +NOTE – The output of this process is equal for all slices of a picture. + +When num\_slice\_groups\_minus1 is equal to 1 and slice\_group\_map\_type is equal to 3, 4, or 5, slice groups 0 and 1 have a size and shape determined by slice\_group\_change\_direction\_flag as shown in Table 8-1 and specified in clauses 8.2.2.4 to 8.2.2.6. + +**Table 8-1 – Refined slice group map type** + +| slice_group_map_type | slice_group_change_direction_flag | refined slice group map type | +|----------------------|-----------------------------------|------------------------------| +| 3 | 0 | Box-out clockwise | +| 3 | 1 | Box-out counter-clockwise | +| 4 | 0 | Raster scan | +| 4 | 1 | Reverse raster scan | +| 5 | 0 | Wipe right | +| 5 | 1 | Wipe left | + +In such a case, MapUnitsInSliceGroup0 slice group map units in the specified growth order are allocated for slice group 0 and the remaining PicSizeInMapUnits – MapUnitsInSliceGroup0 slice group map units of the picture are allocated for slice group 1. + +When num\_slice\_groups\_minus1 is equal to 1 and slice\_group\_map\_type is equal to 4 or 5, the variable sizeOfUpperLeftGroup is defined as follows: + +$$\text{sizeOfUpperLeftGroup} = ( \text{slice\_group\_change\_direction\_flag} ? (\text{PicSizeInMapUnits} - \text{MapUnitsInSliceGroup0}) : \text{MapUnitsInSliceGroup0} ) \quad (8-14)$$ + +The mapUnitToSliceGroupMap array is derived as follows: + +- If num\_slice\_groups\_minus1 is equal to 0, the map unit to slice group map is generated for all i ranging from 0 to PicSizeInMapUnits – 1, inclusive, as specified by + +$$\text{mapUnitToSliceGroupMap}[ i ] = 0 \quad (8-15)$$ + +- Otherwise (num\_slice\_groups\_minus1 is not equal to 0), mapUnitToSliceGroupMap is derived as follows: + - If slice\_group\_map\_type is equal to 0, the derivation of mapUnitToSliceGroupMap as specified in clause 8.2.2.1 applies. + - Otherwise, if slice\_group\_map\_type is equal to 1, the derivation of mapUnitToSliceGroupMap as specified in clause 8.2.2.2 applies. + - Otherwise, if slice\_group\_map\_type is equal to 2, the derivation of mapUnitToSliceGroupMap as specified in clause 8.2.2.3 applies. + +- Otherwise, if `slice_group_map_type` is equal to 3, the derivation of `mapUnitToSliceGroupMap` as specified in clause 8.2.2.4 applies. +- Otherwise, if `slice_group_map_type` is equal to 4, the derivation of `mapUnitToSliceGroupMap` as specified in clause 8.2.2.5 applies. +- Otherwise, if `slice_group_map_type` is equal to 5, the derivation of `mapUnitToSliceGroupMap` as specified in clause 8.2.2.6 applies. +- Otherwise ( `slice_group_map_type` is equal to 6), the derivation of `mapUnitToSliceGroupMap` as specified in clause 8.2.2.7 applies. + +After derivation of the `mapUnitToSliceGroupMap`, the process specified in clause 8.2.2.8 is invoked to convert the map unit to slice group map `mapUnitToSliceGroupMap` to the macroblock to slice group map `MbToSliceGroupMap`. After derivation of the macroblock to slice group map as specified in clause 8.2.2.8, the function `NextMbAddress( n )` is defined as the value of the variable `nextMbAddress` derived as specified by the following pseudo-code: + +``` + +i = n + 1 +while( i < PicSizeInMbs && MbToSliceGroupMap[ i ] != MbToSliceGroupMap[ n ] ) + i++; +nextMbAddress = i + +``` + +(8-16) + +### 8.2.2.1 Specification for interleaved slice group map type + +The specifications in this clause apply when `slice_group_map_type` is equal to 0. + +The map unit to slice group map is generated as specified by the following pseudo-code: + +``` + +i = 0 +do + for( iGroup = 0; iGroup <= num_slice_groups_minus1 && i < PicSizeInMapUnits; + i += run_length_minus1[ iGroup++ ] + 1 ) + for( j = 0; j <= run_length_minus1[ iGroup ] && i + j < PicSizeInMapUnits; j++ ) + mapUnitToSliceGroupMap[ i + j ] = iGroup + while( i < PicSizeInMapUnits ) + +``` + +(8-17) + +### 8.2.2.2 Specification for dispersed slice group map type + +The specifications in this clause apply when `slice_group_map_type` is equal to 1. + +The map unit to slice group map is generated as specified by the following pseudo-code: + +``` + +for( i = 0; i < PicSizeInMapUnits; i++ ) + mapUnitToSliceGroupMap[ i ] = ( ( i % PicWidthInMbs ) + + ( ( ( i / PicWidthInMbs ) * ( num_slice_groups_minus1 + 1 ) ) / 2 ) ) + % ( num_slice_groups_minus1 + 1 ) + +``` + +(8-18) + +### 8.2.2.3 Specification for foreground with left-over slice group map type + +The specifications in this clause apply when `slice_group_map_type` is equal to 2. + +The map unit to slice group map is generated as specified by the following pseudo-code: + +``` + +for( i = 0; i < PicSizeInMapUnits; i++ ) + mapUnitToSliceGroupMap[ i ] = num_slice_groups_minus1 +for( iGroup = num_slice_groups_minus1 - 1; iGroup >= 0; iGroup-- ) { + yTopLeft = top_left[ iGroup ] / PicWidthInMbs + xTopLeft = top_left[ iGroup ] % PicWidthInMbs + yBottomRight = bottom_right[ iGroup ] / PicWidthInMbs + xBottomRight = bottom_right[ iGroup ] % PicWidthInMbs + for( y = yTopLeft; y <= yBottomRight; y++ ) + for( x = xTopLeft; x <= xBottomRight; x++ ) + mapUnitToSliceGroupMap[ y * PicWidthInMbs + x ] = iGroup +} + +``` + +(8-19) + +NOTE – The rectangles may overlap. Slice group 0 contains the macroblocks that are within the rectangle specified by `top_left[ 0 ]` and `bottom_right[ 0 ]`. A slice group having slice group ID greater than 0 and less than `num_slice_groups_minus1` contains the macroblocks that are within the specified rectangle for that slice group that are not within the rectangle specified for any slice group + +having a smaller slice group ID. The slice group with slice group ID equal to `num_slice_groups_minus1` contains the macroblocks that are not in the other slice groups. + +#### 8.2.2.4 Specification for box-out slice group map types + +The specifications in this clause apply when `slice_group_map_type` is equal to 3. + +The map unit to slice group map is generated as specified by + +``` + +for( i = 0; i < PicSizeInMapUnits; i++ ) + mapUnitToSliceGroupMap[ i ] = 1 +x = ( PicWidthInMbs - slice_group_change_direction_flag ) / 2 +y = ( PicHeightInMapUnits - slice_group_change_direction_flag ) / 2 +( leftBound, topBound ) = ( x, y ) +( rightBound, bottomBound ) = ( x, y ) +( xDir, yDir ) = ( slice_group_change_direction_flag - 1, slice_group_change_direction_flag ) +for( k = 0; k < MapUnitsInSliceGroup0; k += mapUnitVacant ) { + mapUnitVacant = ( mapUnitToSliceGroupMap[ y * PicWidthInMbs + x ] == 1 ) + if( mapUnitVacant ) + mapUnitToSliceGroupMap[ y * PicWidthInMbs + x ] = 0 + if( xDir == -1 && x == leftBound ) { + leftBound = Max( leftBound - 1, 0 ) + x = leftBound + ( xDir, yDir ) = ( 0, 2 * slice_group_change_direction_flag - 1 ) + } else if( xDir == 1 && x == rightBound ) { + rightBound = Min( rightBound + 1, PicWidthInMbs - 1 ) + x = rightBound + ( xDir, yDir ) = ( 0, 1 - 2 * slice_group_change_direction_flag ) + } else if( yDir == -1 && y == topBound ) { + topBound = Max( topBound - 1, 0 ) + y = topBound + ( xDir, yDir ) = ( 1 - 2 * slice_group_change_direction_flag, 0 ) + } else if( yDir == 1 && y == bottomBound ) { + bottomBound = Min( bottomBound + 1, PicHeightInMapUnits - 1 ) + y = bottomBound + ( xDir, yDir ) = ( 2 * slice_group_change_direction_flag - 1, 0 ) + } else + ( x, y ) = ( x + xDir, y + yDir ) +} + +``` + +(8-20) + +#### 8.2.2.5 Specification for raster scan slice group map types + +The specifications in this clause apply when `slice_group_map_type` is equal to 4. + +The map unit to slice group map is generated as specified by + +``` + +for( i = 0; i < PicSizeInMapUnits; i++ ) + if( i < sizeOfUpperLeftGroup ) + mapUnitToSliceGroupMap[ i ] = slice_group_change_direction_flag + else + mapUnitToSliceGroupMap[ i ] = 1 - slice_group_change_direction_flag + +``` + +(8-21) + +#### 8.2.2.6 Specification for wipe slice group map types + +The specifications in this clause apply when `slice_group_map_type` is equal to 5. + +The map unit to slice group map is generated as specified by + +``` + +k = 0; +for( j = 0; j < PicWidthInMbs; j++ ) + for( i = 0; i < PicHeightInMapUnits; i++ ) + if( k++ < sizeOfUpperLeftGroup ) + mapUnitToSliceGroupMap[ i * PicWidthInMbs + j ] = slice_group_change_direction_flag + else + mapUnitToSliceGroupMap[ i * PicWidthInMbs + j ] = 1 - slice_group_change_direction_flag + +``` + +(8-22) + +### 8.2.2.7 Specification for explicit slice group map type + +The specifications in this clause apply when `slice_group_map_type` is equal to 6. + +The map unit to slice group map is generated as specified by + +$$\text{mapUnitToSliceGroupMap}[ i ] = \text{slice\_group\_id}[ i ] \quad (8-23)$$ + +for all $i$ ranging from 0 to `PicSizeInMapUnits` – 1, inclusive. + +### 8.2.2.8 Specification for conversion of map unit to slice group map to macroblock to slice group map + +For each value of $i$ ranging from 0 to `PicSizeInMbs` – 1, inclusive, the macroblock to slice group map is specified as follows: + +- If `frame_mbs_only_flag` is equal to 1 or `field_pic_flag` is equal to 1, the macroblock to slice group map is specified by + +$$\text{MbToSliceGroupMap}[ i ] = \text{mapUnitToSliceGroupMap}[ i ] \quad (8-24)$$ + +- Otherwise, if `MbaffFrameFlag` is equal to 1, the macroblock to slice group map is specified by + +$$\text{MbToSliceGroupMap}[ i ] = \text{mapUnitToSliceGroupMap}[ i / 2 ] \quad (8-25)$$ + +- Otherwise (`frame_mbs_only_flag` is equal to 0 and `mb_adaptive_frame_field_flag` is equal to 0 and `field_pic_flag` is equal to 0), the macroblock to slice group map is specified by + +$$\text{MbToSliceGroupMap}[ i ] = \text{mapUnitToSliceGroupMap}[ ( i / ( 2 * \text{PicWidthInMbs} ) ) * \text{PicWidthInMbs} + ( i \% \text{PicWidthInMbs} ) ] \quad (8-26)$$ + +### 8.2.3 Decoding process for slice data partitions + +Inputs to this process are: + +- a slice data partition A layer RBSP, +- when syntax elements of category 3 are present in the slice data, a slice data partition B layer RBSP having the same `slice_id` as in the slice data partition A layer RBSP, +- when syntax elements of category 4 are present in the slice data, a slice data partition C layer RBSP having the same `slice_id` as in the slice data partition A layer RBSP. + +NOTE 1 – The slice data partition B layer RBSP and slice data partition C layer RBSP need not be present. + +Output of this process is a coded slice. + +When slice data partitioning is not used, coded slices are represented by a slice layer without partitioning RBSP that contains a slice header followed by a slice data syntax structure that contains all the syntax elements of categories 2, 3, and 4 (see category column in clause 7.3) of the macroblock data for the macroblocks of the slice. + +When slice data partitioning is used, the macroblock data of a slice is partitioned into one to three partitions contained in separate NAL units. Partition A contains a slice data partition A header, and all syntax elements of category 2. Partition B, when present, contains a slice data partition B header and all syntax elements of category 3. Partition C, when present, contains a slice data partition C header and all syntax elements of category 4. + +When slice data partitioning is used, the syntax elements of each category are parsed from a separate NAL unit, which need not be present when no symbols of the respective category exist. The decoding process shall process the slice data partitions of a coded slice in a manner equivalent to processing a corresponding slice layer without partitioning RBSP by extracting each syntax element from the slice data partition in which the syntax element appears depending on the slice data partition assignment in the syntax tables in clause 7.3. + +NOTE 2 – Syntax elements of category 3 are relevant to the decoding of residual data of I and SI macroblock types. Syntax elements of category 4 are relevant to the decoding of residual data of P and B macroblock types. Category 2 encompasses all other syntax elements related to the decoding of macroblocks, and their information is often denoted as header information. The slice data partition A header contains all the syntax elements of the slice header, and additionally a `slice_id` that are used to associate the slice data partitions B and C with the slice data partition A. The slice data partition B and C headers contain the `slice_id` syntax element that establishes their association with the slice data partition A of the slice. + +## 8.2.4 Decoding process for reference picture lists construction + +This process is invoked at the beginning of the decoding process for each P, SP, or B slice. + +Decoded reference pictures are marked as "used for short-term reference" or "used for long-term reference" as specified by the bitstream and specified in clause 8.2.5. Short-term reference pictures are identified by the value of `frame_num`. Long-term reference pictures are assigned a long-term frame index as specified by the bitstream and specified in clause 8.2.5. + +Clause 8.2.4.1 is invoked to specify + +- the assignment of variables `FrameNum`, `FrameNumWrap`, and `PicNum` to each of the short-term reference pictures, and +- the assignment of variable `LongTermPicNum` to each of the long-term reference pictures. + +Reference pictures are addressed through reference indices as specified in clause 8.4.2.1. A reference index is an index into a reference picture list. When decoding a P or SP slice, there is a single reference picture list `RefPicList0`. When decoding a B slice, there is a second independent reference picture list `RefPicList1` in addition to `RefPicList0`. + +At the beginning of the decoding process for each slice, reference picture list `RefPicList0`, and for B slices `RefPicList1`, are derived as specified by the following ordered steps: + +1. An initial reference picture list `RefPicList0` and for B slices `RefPicList1` are derived as specified in clause 8.2.4.2. +2. When `ref_pic_list_modification_flag_l0` is equal to 1 or, when decoding a B slice, `ref_pic_list_modification_flag_l1` is equal to 1, the initial reference picture list `RefPicList0` and, for B slices, `RefPicList1` are modified as specified in clause 8.2.4.3. + +NOTE – The modification process for reference picture lists specified in clause 8.2.4.3 allows the contents of `RefPicList0` and for B slices `RefPicList1` to be modified in a flexible fashion. In particular, it is possible for a picture that is currently marked "used for reference" to be inserted into `RefPicList0` and for B slices `RefPicList1` even when the picture is not in the initial reference picture list derived as specified in clause 8.2.4.2. + +The number of entries in the modified reference picture list `RefPicList0` is `num_ref_idx_l0_active_minus1 + 1`, and for B slices the number of entries in the modified reference picture list `RefPicList1` is `num_ref_idx_l1_active_minus1 + 1`. A reference picture may appear at more than one index in the modified reference picture lists `RefPicList0` or `RefPicList1`. + +### 8.2.4.1 Decoding process for picture numbers + +This process is invoked when the decoding process for reference picture lists construction specified in clause 8.2.4, the decoded reference picture marking process specified in clause 8.2.5, or the decoding process for gaps in `frame_num` specified in clause 8.2.5.2 is invoked. + +The variables `FrameNum`, `FrameNumWrap`, `PicNum`, `LongTermFrameIdx`, and `LongTermPicNum` are used for the initialization process for reference picture lists in clause 8.2.4.2, the modification process for reference picture lists in clause 8.2.4.3, the decoded reference picture marking process in clause 8.2.5, and the decoding process for gaps in `frame_num` in clause 8.2.5.2. + +To each short-term reference picture the variables `FrameNum` and `FrameNumWrap` are assigned as follows. First, `FrameNum` is set equal to the syntax element `frame_num` that has been decoded in the slice header(s) of the corresponding short-term reference picture. Then the variable `FrameNumWrap` is derived as + +$$\begin{aligned} &\text{if( } \text{FrameNum} > \text{frame\_num} ) \\ &\quad \text{FrameNumWrap} = \text{FrameNum} - \text{MaxFrameNum} \\ &\text{else} \\ &\quad \text{FrameNumWrap} = \text{FrameNum} \end{aligned} \tag{8-27}$$ + +where the value of `frame_num` used in Equation 8-27 is the `frame_num` in the slice header(s) for the current picture. + +Each long-term reference picture has an associated value of `LongTermFrameIdx` (that was assigned to it as specified in clause 8.2.5). + +To each short-term reference picture a variable `PicNum` is assigned, and to each long-term reference picture a variable `LongTermPicNum` is assigned. The values of these variables depend on the value of field `pic_flag` and `bottom_field_flag` for the current picture and they are set as follows: + +- If `field_pic_flag` is equal to 0, the following ordered steps are specified: + 1. For each short-term reference frame or complementary reference field pair: + +$$\text{PicNum} = \text{FrameNumWrap} \quad (8-28)$$ + +2. For each long-term reference frame or long-term complementary reference field pair: + +$$\text{LongTermPicNum} = \text{LongTermFrameIdx} \quad (8-29)$$ + +NOTE – When decoding a frame the value of `MbaffFrameFlag` has no influence on the derivations in clauses 8.2.4.2, 8.2.4.3, and 8.2.5. + +- Otherwise (`field_pic_flag` is equal to 1), the following ordered steps are specified: + +1. For each short-term reference field the following applies: + +- If the reference field has the same parity as the current field + +$$\text{PicNum} = 2 * \text{FrameNumWrap} + 1 \quad (8-30)$$ + +- Otherwise (the reference field has the opposite parity of the current field), + +$$\text{PicNum} = 2 * \text{FrameNumWrap} \quad (8-31)$$ + +2. For each long-term reference field the following applies: + +- If the reference field has the same parity as the current field + +$$\text{LongTermPicNum} = 2 * \text{LongTermFrameIdx} + 1 \quad (8-32)$$ + +- Otherwise (the reference field has the opposite parity of the current field), + +$$\text{LongTermPicNum} = 2 * \text{LongTermFrameIdx} \quad (8-33)$$ + +#### 8.2.4.2 Initialization process for reference picture lists + +This initialization process is invoked when decoding a P, SP, or B slice header. + +`RefPicList0` and `RefPicList1` have initial entries as specified in clauses 8.2.4.2.1 through 8.2.4.2.5. + +When the number of entries in the initial `RefPicList0` or `RefPicList1` produced as specified in clauses 8.2.4.2.1 through 8.2.4.2.5 is greater than `num_ref_idx_l0_active_minus1 + 1` or `num_ref_idx_l1_active_minus1 + 1`, respectively, the extra entries past position `num_ref_idx_l0_active_minus1` or `num_ref_idx_l1_active_minus1` are discarded from the initial reference picture list. + +When the number of entries in the initial `RefPicList0` or `RefPicList1` produced as specified in clauses 8.2.4.2.1 through 8.2.4.2.5 is less than `num_ref_idx_l0_active_minus1 + 1` or `num_ref_idx_l1_active_minus1 + 1`, respectively, the remaining entries in the initial reference picture list are set equal to "no reference picture". + +##### 8.2.4.2.1 Initialization process for the reference picture list for P and SP slices in frames + +This initialization process is invoked when decoding a P or SP slice in a coded frame. + +When this process is invoked, there shall be at least one reference frame or complementary reference field pair that is currently marked as "used for reference" (i.e., as "used for short-term reference" or "used for long-term reference") and is not marked as "non-existing". + +The reference picture list `RefPicList0` is ordered so that short-term reference frames and short-term complementary reference field pairs have lower indices than long-term reference frames and long-term complementary reference field pairs. + +The short-term reference frames and complementary reference field pairs are ordered starting with the frame or complementary field pair with the highest `PicNum` value and proceeding through in descending order to the frame or complementary field pair with the lowest `PicNum` value. + +The long-term reference frames and complementary reference field pairs are ordered starting with the frame or complementary field pair with the lowest `LongTermPicNum` value and proceeding through in ascending order to the frame or complementary field pair with the highest `LongTermPicNum` value. + +NOTE – A non-paired reference field is not used for inter prediction for decoding a frame, regardless of the value of MbaffFrameFlag. + +For example, when three reference frames are marked as "used for short-term reference" with PicNum equal to 300, 302, and 303 and two reference frames are marked as "used for long-term reference" with LongTermPicNum equal to 0 and 3, the initial index order is: + +- RefPicList0[ 0 ] is set equal to the short-term reference picture with PicNum = 303, +- RefPicList0[ 1 ] is set equal to the short-term reference picture with PicNum = 302, +- RefPicList0[ 2 ] is set equal to the short-term reference picture with PicNum = 300, +- RefPicList0[ 3 ] is set equal to the long-term reference picture with LongTermPicNum = 0, +- RefPicList0[ 4 ] is set equal to the long-term reference picture with LongTermPicNum = 3. + +#### 8.2.4.2.2 Initialization process for the reference picture list for P and SP slices in fields + +This initialization process is invoked when decoding a P or SP slice in a coded field. + +When this process is invoked, there shall be at least one reference field (which can be a field of a reference frame) that is currently marked as "used for reference" (i.e., as "used for short-term reference" or "used for long-term reference") and is not marked as "non-existing". + +Each field included in the reference picture list RefPicList0 has a separate index in the reference picture list RefPicList0. + +NOTE – When decoding a field, there are effectively at least twice as many pictures available for referencing as there would be when decoding a frame at the same position in decoding order. + +Two ordered lists of reference frames, refFrameList0ShortTerm and refFrameList0LongTerm, are derived as follows. For purposes of the formation of this list of frames, decoded reference frames, complementary reference field pairs, non-paired reference fields and reference frames in which a single field is marked "used for short-term reference" or "used for long-term reference" are all considered reference frames. + +1. All frames having one or more fields marked "used for short-term reference" are included in the list of short-term reference frames refFrameList0ShortTerm. When the current field is the second field (in decoding order) of a complementary reference field pair and the first field is marked as "used for short-term reference", the first field is included in the list of short-term reference frames refFrameList0ShortTerm. refFrameList0ShortTerm is ordered starting with the reference frame with the highest FrameNumWrap value and proceeding through in descending order to the reference frame with the lowest FrameNumWrap value. +2. All frames having one or more fields marked "used for long-term reference" are included in the list of long-term reference frames refFrameList0LongTerm. When the current field is the second field (in decoding order) of a complementary reference field pair and the first field is marked as "used for long-term reference", the first field is included in the list of long-term reference frames refFrameList0LongTerm. refFrameList0LongTerm is ordered starting with the reference frame with the lowest LongTermFrameIdx value and proceeding through in ascending order to the reference frame with the highest LongTermFrameIdx value. + +The process specified in clause 8.2.4.2.5 is invoked with refFrameList0ShortTerm and refFrameList0LongTerm given as input and the output is assigned to RefPicList0. + +#### 8.2.4.2.3 Initialization process for reference picture lists for B slices in frames + +This initialization process is invoked when decoding a B slice in a coded frame. + +For purposes of the formation of the reference picture lists RefPicList0 and RefPicList1 the term reference entry refers in the following to decoded reference frames or complementary reference field pairs. + +When this process is invoked, there shall be at least one reference entry that is currently marked as "used for reference" (i.e., as "used for short-term reference" or "used for long-term reference") and is not marked as "non-existing". + +For B slices, the order of short-term reference entries in the reference picture lists RefPicList0 and RefPicList1 depends on output order, as given by PicOrderCnt(). When pic\_order\_cnt\_type is equal to 0, reference pictures that are marked as "non-existing" as specified in clause 8.2.5.2 are not included in either RefPicList0 or RefPicList1. + +NOTE 1 – When gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1, encoders should use reference picture list modification to ensure proper operation of the decoding process (particularly when pic\_order\_cnt\_type is equal to 0, in which case PicOrderCnt() is not inferred for "non-existing" frames). + +The reference picture list RefPicList0 is ordered such that short-term reference entries have lower indices than long-term reference entries. It is ordered as follows: + +1. Let entryShortTerm be a variable ranging over all reference entries that are currently marked as "used for short-term reference". When some values of entryShortTerm are present having PicOrderCnt( entryShortTerm ) less than PicOrderCnt( CurrPic ), these values of entryShortTerm are placed at the beginning of refPicList0 in descending order of PicOrderCnt( entryShortTerm ). All of the remaining values of entryShortTerm (when present) are then appended to refPicList0 in ascending order of PicOrderCnt( entryShortTerm ). +2. The long-term reference entries are ordered starting with the long-term reference entry that has the lowest LongTermPicNum value and proceeding through in ascending order to the long-term reference entry that has the highest LongTermPicNum value. + +The reference picture list RefPicList1 is ordered so that short-term reference entries have lower indices than long-term reference entries. It is ordered as follows: + +1. Let entryShortTerm be a variable ranging over all reference entries that are currently marked as "used for short-term reference". When some values of entryShortTerm are present having PicOrderCnt( entryShortTerm ) greater than PicOrderCnt( CurrPic ), these values of entryShortTerm are placed at the beginning of refPicList1 in ascending order of PicOrderCnt( entryShortTerm ). All of the remaining values of entryShortTerm (when present) are then appended to refPicList1 in descending order of PicOrderCnt( entryShortTerm ). +2. Long-term reference entries are ordered starting with the long-term reference frame or complementary reference field pair that has the lowest LongTermPicNum value and proceeding through in ascending order to the long-term reference entry that has the highest LongTermPicNum value. +3. When the reference picture list RefPicList1 has more than one entry and RefPicList1 is identical to the reference picture list RefPicList0, the first two entries RefPicList1[ 0 ] and RefPicList1[ 1 ] are switched. + +NOTE 2 – A non-paired reference field is not used for inter prediction of frames (independent of the value of MbuffFrameFlag). + +#### 8.2.4.2.4 Initialization process for reference picture lists for B slices in fields + +This initialization process is invoked when decoding a B slice in a coded field. + +When this process is invoked, there shall be at least one reference field (which can be a field of a reference frame) that is currently marked as "used for reference" (i.e., as "used for short-term reference" or "used for long-term reference") and is not marked as "non-existing". + +When decoding a field, each field of a stored reference frame is identified as a separate reference picture with a unique index. The order of short-term reference pictures in the reference picture lists RefPicList0 and RefPicList1 depend on output order, as given by PicOrderCnt( ). When pic\_order\_cnt\_type is equal to 0, reference pictures that are marked as "non-existing" as specified in clause 8.2.5.2 are not included in either RefPicList0 or RefPicList1. + +NOTE 1 – When gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1, encoders should use reference picture list modification to ensure proper operation of the decoding process (particularly when pic\_order\_cnt\_type is equal to 0, in which case PicOrderCnt( ) is not inferred for "non-existing" frames). + +NOTE 2 – When decoding a field, there are effectively at least twice as many pictures available for referencing as there would be when decoding a frame at the same position in decoding order. + +Three ordered lists of reference frames, refFrameList0ShortTerm, refFrameList1ShortTerm and refFrameListLongTerm, are derived as follows. For purposes of the formation of these lists of frames the term reference entry refers in the following to decoded reference frames, complementary reference field pairs, or non-paired reference fields. When pic\_order\_cnt\_type is equal to 0, the term reference entry does not refer to frames that are marked as "non-existing" as specified in clause 8.2.5.2. + +1. Let entryShortTerm be a variable ranging over all reference entries that are currently marked as "used for short-term reference". When some values of entryShortTerm are present having PicOrderCnt( entryShortTerm ) less than or equal to PicOrderCnt( CurrPic ), these values of entryShortTerm are placed at the beginning of refFrameList0ShortTerm in descending order of PicOrderCnt( entryShortTerm ). All of the remaining values of entryShortTerm (when present) are then appended to refFrameList0ShortTerm in ascending order of PicOrderCnt( entryShortTerm ). + +NOTE 3 – When the current field follows in decoding order a coded field fldPrev with which together it forms a complementary reference field pair, fldPrev is included into the list refFrameList0ShortTerm using PicOrderCnt( fldPrev ) and the ordering method described in the previous sentence is applied. + +2. Let entryShortTerm be a variable ranging over all reference entries that are currently marked as "used for short-term reference". When some values of entryShortTerm are present having PicOrderCnt( entryShortTerm ) greater than PicOrderCnt( CurrPic ), these values of entryShortTerm are placed at the beginning of refFrameList1ShortTerm in ascending order of PicOrderCnt( entryShortTerm ). All of the remaining values of + +entryShortTerm (when present) are then appended to refFrameList1ShortTerm in descending order of PicOrderCnt( entryShortTerm ). + +NOTE 4 – When the current field follows in decoding order a coded field fldPrev with which together it forms a complementary reference field pair, fldPrev is included into the list refFrameList1ShortTerm using PicOrderCnt( fldPrev ) and the ordering method described in the previous sentence is applied. + +3. refFrameListLongTerm is ordered starting with the reference entry having the lowest LongTermFrameIdx value and proceeding through in ascending order to the reference entry having highest LongTermFrameIdx value. + +NOTE 5 – When the current picture is the second field of a complementary field pair and the first field of the complementary field pair is marked as "used for long-term reference", the first field is included into the list refFrameListLongTerm. A reference entry in which only one field is marked as "used for long-term reference" is included into the list refFrameListLongTerm. + +The process specified in clause 8.2.4.2.5 is invoked with refFrameList0ShortTerm and refFrameListLongTerm given as input and the output is assigned to RefPicList0. + +The process specified in clause 8.2.4.2.5 is invoked with refFrameList1ShortTerm and refFrameListLongTerm given as input and the output is assigned to RefPicList1. + +When the reference picture list RefPicList1 has more than one entry and RefPicList1 is identical to the reference picture list RefPicList0, the first two entries RefPicList1[ 0 ] and RefPicList1[ 1 ] are switched. + +#### 8.2.4.2.5 Initialization process for reference picture lists in fields + +Inputs of this process are the reference frame lists refFrameListXShortTerm (with X may be 0 or 1) and refFrameListLongTerm. + +The reference picture list RefPicListX is a list ordered such that short-term reference fields have lower indices than long-term reference fields. Given the reference frame lists refFrameListXShortTerm and refFrameListLongTerm, it is derived as specified by the following ordered steps: + +1. Short-term reference fields are ordered by selecting reference fields from the ordered list of frames refFrameListXShortTerm by alternating between fields of differing parity, starting with a field that has the same parity as the current field (when present). When one field of a reference frame was not decoded or is not marked as "used for short-term reference", the missing field is ignored and instead the next available stored reference field of the chosen parity from the ordered list of frames refFrameListXShortTerm is inserted into RefPicListX. When there are no more short-term reference fields of the alternate parity in the ordered list of frames refFrameListXShortTerm, the next not yet indexed fields of the available parity are inserted into RefPicListX in the order in which they occur in the ordered list of frames refFrameListXShortTerm. +2. Long-term reference fields are ordered by selecting reference fields from the ordered list of frames refFrameListLongTerm by alternating between fields of differing parity, starting with a field that has the same parity as the current field (when present). When one field of a reference frame was not decoded or is not marked as "used for long-term reference", the missing field is ignored and instead the next available stored reference field of the chosen parity from the ordered list of frames refFrameListLongTerm is inserted into RefPicListX. When there are no more long-term reference fields of the alternate parity in the ordered list of frames refFrameListLongTerm, the next not yet indexed fields of the available parity are inserted into RefPicListX in the order in which they occur in the ordered list of frames refFrameListLongTerm. + +#### 8.2.4.3 Modification process for reference picture lists + +When ref\_pic\_list\_modification\_flag\_l0 is equal to 1, the following applies: + +1. Let refIdxL0 be an index into the reference picture list RefPicList0. It is initially set equal to 0. +2. The corresponding syntax elements modification\_of\_pic\_nums\_idc are processed in the order they occur in the bitstream. For each of these syntax elements, the following applies: + - If modification\_of\_pic\_nums\_idc is equal to 0 or equal to 1, the process specified in clause 8.2.4.3.1 is invoked with refIdxL0 as input, and the output is assigned to refIdxL0. + - Otherwise, if modification\_of\_pic\_nums\_idc is equal to 2, the process specified in clause 8.2.4.3.2 is invoked with refIdxL0 as input, and the output is assigned to refIdxL0. + - Otherwise (modification\_of\_pic\_nums\_idc is equal to 3), the modification process for reference picture list RefPicList0 is finished. + +When the current slice is a B slice and ref\_pic\_list\_modification\_flag\_l1 is equal to 1, the following applies: + +1. Let refIdxL1 be an index into the reference picture list RefPicList1. It is initially set equal to 0. + +2. The corresponding syntax elements `modification_of_pic_nums_idc` are processed in the order they occur in the bitstream. For each of these syntax elements, the following applies: + - If `modification_of_pic_nums_idc` is equal to 0 or equal to 1, the process specified in clause 8.2.4.3.1 is invoked with `refIdxL1` as input, and the output is assigned to `refIdxL1`. + - Otherwise, if `modification_of_pic_nums_idc` is equal to 2, the process specified in clause 8.2.4.3.2 is invoked with `refIdxL1` as input, and the output is assigned to `refIdxL1`. + - Otherwise (`modification_of_pic_nums_idc` is equal to 3), the modification process for reference picture list `RefPicList1` is finished. + +#### 8.2.4.3.1 Modification process of reference picture lists for short-term reference pictures + +Input to this process is an index `refIdxLX` (with X being 0 or 1). + +Output of this process is an incremented index `refIdxLX`. + +The variable `picNumLXNoWrap` is derived as follows: + +- If `modification_of_pic_nums_idc` is equal to 0, + + +``` + +if (picNumLXPred - ( abs_diff_pic_num_minus1 + 1 ) < 0 ) + picNumLXNoWrap = picNumLXPred - ( abs_diff_pic_num_minus1 + 1 ) + MaxPicNum +else + picNumLXNoWrap = picNumLXPred - ( abs_diff_pic_num_minus1 + 1 ) + +``` + +- Otherwise (`modification_of_pic_nums_idc` is equal to 1), + + +``` + +if (picNumLXPred + ( abs_diff_pic_num_minus1 + 1 ) >= MaxPicNum ) + picNumLXNoWrap = picNumLXPred + ( abs_diff_pic_num_minus1 + 1 ) - MaxPicNum +else + picNumLXNoWrap = picNumLXPred + ( abs_diff_pic_num_minus1 + 1 ) + +``` + +`picNumLXPred` is the prediction value for the variable `picNumLXNoWrap`. When the process specified in this clause is invoked the first time for a slice (that is, for the first occurrence of `modification_of_pic_nums_idc` equal to 0 or 1 in the `ref_pic_list_modification()` syntax), `picNumL0Pred` and `picNumL1Pred` are initially set equal to `CurrPicNum`. After each assignment of `picNumLXNoWrap`, the value of `picNumLXNoWrap` is assigned to `picNumLXPred`. + +The variable `picNumLX` is derived as specified by the following pseudo-code: + +- ``` + +if (picNumLXNoWrap > CurrPicNum) + picNumLX = picNumLXNoWrap - MaxPicNum +else + picNumLX = picNumLXNoWrap + +``` + +`picNumLX` shall be equal to the `PicNum` of a reference picture that is marked as "used for short-term reference" and shall not be equal to the `PicNum` of a short-term reference picture that is marked as "non-existing". + +The following procedure is conducted to place the picture with short-term picture number `picNumLX` into the index position `refIdxLX`, shift the position of any other remaining pictures to later in the list, and increment the value of `refIdxLX`. + +- ``` + +for( cIdx = num_ref_idx_lX_active_minus1 + 1; cIdx > refIdxLX; cIdx-- ) + RefPicListX[ cIdx ] = RefPicListX[ cIdx - 1 ] +RefPicListX[ refIdxLX++ ] = short-term reference picture with PicNum equal to picNumLX +nIdx = refIdxLX +for( cIdx = refIdxLX; cIdx <= num_ref_idx_lX_active_minus1 + 1; cIdx++ ) + if( PicNumF( RefPicListX[ cIdx ] ) != picNumLX ) + RefPicListX[ nIdx++ ] = RefPicListX[ cIdx ] + +``` + +where the function `PicNumF( RefPicListX[ cIdx ] )` is derived as follows: + +- If the picture `RefPicListX[ cIdx ]` is marked as "used for short-term reference", `PicNumF( RefPicListX[ cIdx ] )` is the `PicNum` of the picture `RefPicListX[ cIdx ]`. +- Otherwise (the picture `RefPicListX[ cIdx ]` is not marked as "used for short-term reference"), `PicNumF( RefPicListX[ cIdx ] )` is equal to `MaxPicNum`. + +NOTE 1 – A value of MaxPicNum can never be equal to picNumLX. + +NOTE 2 – Within this pseudo-code procedure, the length of the list RefPicListX is temporarily made one element longer than the length needed for the final list. After the execution of this procedure, only elements 0 through num\_ref\_idx\_IX\_active\_minus1 of the list need to be retained. + +#### 8.2.4.3.2 Modification process of reference picture lists for long-term reference pictures + +Input to this process is an index refIdxLX (with X being 0 or 1). + +Output of this process is an incremented index refIdxLX. + +The following procedure is conducted to place the picture with long-term picture number long\_term\_pic\_num into the index position refIdxLX, shift the position of any other remaining pictures to later in the list, and increment the value of refIdxLX. + +``` +for( cIdx = num_ref_idx_IX_active_minus1 + 1; cIdx > refIdxLX; cIdx-- ) + RefPicListX[ cIdx ] = RefPicListX[ cIdx - 1 ] +RefPicListX[ refIdxLX++ ] = long-term reference picture with LongTermPicNum equal to long_term_pic_num +nIdx = refIdxLX +for( cIdx = refIdxLX; cIdx <= num_ref_idx_IX_active_minus1 + 1; cIdx++ ) + if( LongTermPicNumF( RefPicListX[ cIdx ] ) != long_term_pic_num ) + RefPicListX[ nIdx++ ] = RefPicListX[ cIdx ] +``` + +(8-38) + +where the function LongTermPicNumF( RefPicListX[ cIdx ] ) is derived as follows: + +- If the picture RefPicListX[ cIdx ] is marked as "used for long-term reference", LongTermPicNumF( RefPicListX[ cIdx ] ) is the LongTermPicNum of the picture RefPicListX[ cIdx ]. +- Otherwise (the picture RefPicListX[ cIdx ] is not marked as "used for long-term reference"), LongTermPicNumF( RefPicListX[ cIdx ] ) is equal to $2 * ( \text{MaxLongTermFrameIdx} + 1 )$ . + +NOTE 1 – A value of $2 * ( \text{MaxLongTermFrameIdx} + 1 )$ can never be equal to long\_term\_pic\_num. + +NOTE 2 – Within this pseudo-code procedure, the length of the list RefPicListX is temporarily made one element longer than the length needed for the final list. After the execution of this procedure, only elements 0 through num\_ref\_idx\_IX\_active\_minus1 of the list need to be retained. + +#### 8.2.5 Decoded reference picture marking process + +This process is invoked for decoded pictures when nal\_ref\_idc is not equal to 0. + +NOTE 1 – The decoding process for gaps in frame\_num that is specified in clause 8.2.5.2 may also be invoked when nal\_ref\_idc is equal to 0, as specified in clause 8. + +A decoded picture with nal\_ref\_idc not equal to 0, referred to as a reference picture, is marked as "used for short-term reference" or "used for long-term reference". For a decoded reference frame, both of its fields are marked the same as the frame. For a complementary reference field pair, the pair is marked the same as both of its fields. A picture that is marked as "used for short-term reference" is identified by its FrameNum and, when it is a field, by its parity. A picture that is marked as "used for long-term reference" is identified by its LongTermFrameIdx and, when it is a field, by its parity. + +Frames or complementary field pairs marked as "used for short-term reference" or as "used for long-term reference" can be used as a reference for inter prediction when decoding a frame until the frame, the complementary field pair, or one of its constituent fields is marked as "unused for reference". A field marked as "used for short-term reference" or as "used for long-term reference" can be used as a reference for inter prediction when decoding a field until marked as "unused for reference". + +NOTE 2 – The marking status of a frame or complementary field pair can always be deduced from the marking status of its two fields. If both fields of a frame or complementary field pair are marked as "used for reference", the frame or complementary field pair is also marked as "used for reference"; otherwise (one field or both fields of a frame or complementary field pair are marked as "unused for reference"), the frame or complementary field pair is marked as "unused for reference". + +A picture can be marked as "unused for reference" by the sliding window reference picture marking process, a first-in, first-out mechanism specified in clause 8.2.5.3 or by the adaptive memory control reference picture marking process, a customised adaptive marking operation specified in clause 8.2.5.4. + +A short-term reference picture is identified for use in the decoding process by its variables FrameNum and FrameNumWrap and its picture number PicNum, and a long-term reference picture is identified for use in the decoding process by its long-term picture number LongTermPicNum. When the current picture is not an IDR picture, clause 8.2.4.1 is invoked to specify the assignment of the variables FrameNum, FrameNumWrap, PicNum and LongTermPicNum. + +### 8.2.5.1 Sequence of operations for decoded reference picture marking process + +Decoded reference picture marking proceeds in the following ordered steps: + +1. All slices of the current picture are decoded. +2. Depending on whether the current picture is an IDR picture, the following applies: + - If the current picture is an IDR picture, the following ordered steps are specified: + - a. All reference pictures are marked as "unused for reference" + - b. Depending on long\_term\_reference\_flag, the following applies: + - If long\_term\_reference\_flag is equal to 0, the IDR picture is marked as "used for short-term reference" and MaxLongTermFrameIdx is set equal to "no long-term frame indices". + - Otherwise (long\_term\_reference\_flag is equal to 1), the IDR picture is marked as "used for long-term reference", the LongTermFrameIdx for the IDR picture is set equal to 0, and MaxLongTermFrameIdx is set equal to 0. + - Otherwise (the current picture is not an IDR picture), the following applies: + - If adaptive\_ref\_pic\_marking\_mode\_flag is equal to 0, the process specified in clause 8.2.5.3 is invoked. + - Otherwise (adaptive\_ref\_pic\_marking\_mode\_flag is equal to 1), the process specified in clause 8.2.5.4 is invoked. +3. When the current picture is not an IDR picture and it was not marked as "used for long-term reference" by memory\_management\_control\_operation equal to 6, it is marked as "used for short-term reference". + +It is a requirement of bitstream conformance that, after marking the current decoded reference picture, the total number of frames with at least one field marked as "used for reference", plus the number of complementary field pairs with at least one field marked as "used for reference", plus the number of non-paired fields marked as "used for reference" shall not be greater than $\text{Max}(\text{max\_num\_ref\_frames}, 1)$ . + +### 8.2.5.2 Decoding process for gaps in frame\_num + +This process is invoked when frame\_num is not equal to PrevRefFrameNum and is not equal to $(\text{PrevRefFrameNum} + 1) \% \text{MaxFrameNum}$ . + +NOTE 1 – Although this process is specified as a subclause within clause 8.2.5 (which defines a process that is invoked only when nal\_ref\_idc is not equal to 0), this process may also be invoked when nal\_ref\_idc is equal to 0 (as specified in clause 8). The reasons for the location of this clause within the structure of this Recommendation | International Standard are historical. + +NOTE 2 – This process can only be invoked for a conforming bitstream when gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. When gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 0 and frame\_num is not equal to PrevRefFrameNum and is not equal to $(\text{PrevRefFrameNum} + 1) \% \text{MaxFrameNum}$ , the decoding process should infer an unintentional loss of pictures. + +When this process is invoked, a set of values of frame\_num pertaining to "non-existing" pictures is derived as all values taken on by UnusedShortTermFrameNum in Equation 7-26 except the value of frame\_num for the current picture. + +For each of the values of frame\_num pertaining to "non-existing" pictures, in the order in which the values of UnusedShortTermFrameNum are generated by Equation 7-26, the following ordered steps are specified: + +1. The decoding process for picture numbers as specified in clause 8.2.4.1 is invoked. +2. The sliding window decoded reference picture marking process as specified in clause 8.2.5.3 is invoked. +3. The decoding process generates a frame and the generated frame is marked as "non-existing" and "used for short-term reference". The sample values of the generated frame may be set to any value. + +The following constraints shall be obeyed: + +- a) The bitstream shall not contain data that result in the derivation of a co-located picture colPic that is marked as "non-existing" in any invocation of the derivation process for the co-located 4x4 sub-macroblock partitions specified in clause 8.4.1.2.1. +- b) The bitstream shall not contain data that result in the derivation of a reference picture that is marked as "non-existing" in any invocation of the reference picture selection process specified in clause 8.4.2.1. +- c) The bitstream shall not contain data that result in a variable picNumLX that is equal to the PicNum of a picture marked as "non-existing" in any invocation of the modification process for reference picture lists for short-term reference pictures specified in clause 8.2.4.3.1. + +- d) The bitstream shall not contain data that result in a variable picNumLX that is equal to the PicNum of a picture marked as "non-existing" in any invocation of the assignment process of a LongTermFrameIdx to a short-term reference picture specified in clause 8.2.5.4.3. + +NOTE 3 – The above constraints specify that frames that are marked as "non-existing" by the process specified in this clause must not be referenced in the inter prediction process (clause 8.4, including the derivation process for co-located 4x4 sub-macroblock partitions in clause 8.4.1.2.1), the modification commands for reference picture lists for short-term reference pictures (clause 8.2.4.3.1), or the assignment process of a LongTermFrameIdx to a short-term reference picture (clause 8.2.5.4.3). + +When pic\_order\_cnt\_type is not equal to 0, TopFieldOrderCnt and BottomFieldOrderCnt are derived for each of the "non-existing" frames by invoking the decoding process for picture order count in clause 8.2.1. When invoking the process in clause 8.2.1 for a particular "non-existing" frame, the current picture is considered to be a picture considered having frame\_num inferred to be equal to UnusedShortTermFrameNum, nal\_ref\_idc inferred to be not equal to 0, nal\_unit\_type inferred to be not equal to 5, IdrPicFlag inferred to be equal to 0, field\_pic\_flag inferred to be equal to 0, adaptive\_ref\_pic\_marking\_mode\_flag inferred to be equal to 0, delta\_pic\_order\_cnt[ 0 ] (if needed) inferred to be equal to 0, and delta\_pic\_order\_cnt[ 1 ] (if needed) inferred to be equal to 0. + +NOTE 4 – The decoding process should infer an unintentional picture loss when any of these values of frame\_num pertaining to "non-existing" pictures is referred to in the inter prediction process (clause 8.4, including the derivation process for the co-located 4x4 sub-macroblock partitions in clause 8.4.1.2.1), is referred to in the modification commands for reference picture lists for short-term reference pictures (clause 8.2.4.3.1), or is referred to in the assignment process of a LongTermFrameIdx to a short-term reference picture (clause 8.2.5.4.3). The decoding process should not infer an unintentional picture loss when a memory management control operation not equal to 3 is applied to a frame marked as "non-existing". + +### 8.2.5.3 Sliding window decoded reference picture marking process + +This process is invoked when adaptive\_ref\_pic\_marking\_mode\_flag is equal to 0. + +Depending on the properties of the current picture as specified below, the following applies: + +- If the current picture is a coded field that is the second field in decoding order of a complementary reference field pair, and the first field has been marked as "used for short-term reference", the current picture and the complementary reference field pair are also marked as "used for short-term reference". +- Otherwise, the following applies: + 1. Let numShortTerm be the total number of reference frames, complementary reference field pairs and non-paired reference fields for which at least one field is marked as "used for short-term reference". Let numLongTerm be the total number of reference frames, complementary reference field pairs and non-paired reference fields for which at least one field is marked as "used for long-term reference". + 2. When numShortTerm + numLongTerm is equal to Max( max\_num\_ref\_frames, 1 ), the condition that numShortTerm is greater than 0 shall be fulfilled, and the short-term reference frame, complementary reference field pair or non-paired reference field that has the smallest value of FrameNumWrap is marked as "unused for reference". When it is a frame or a complementary field pair, both of its fields are also marked as "unused for reference". + +### 8.2.5.4 Adaptive memory control decoded reference picture marking process + +This process is invoked when adaptive\_ref\_pic\_marking\_mode\_flag is equal to 1. + +The memory\_management\_control\_operation commands with values of 1 to 6 are processed in the order they occur in the bitstream after the current picture has been decoded. For each of these memory\_management\_control\_operation commands, one of the processes specified in clauses 8.2.5.4.1 to 8.2.5.4.6 is invoked depending on the value of memory\_management\_control\_operation. The memory\_management\_control\_operation command with value of 0 specifies the end of memory\_management\_control\_operation commands. + +Memory management control operations are applied to pictures as follows: + +- If field\_pic\_flag is equal to 0, memory\_management\_control\_operation commands are applied to the frames or complementary reference field pairs specified. +- Otherwise (field\_pic\_flag is equal to 1), memory\_management\_control\_operation commands are applied to the individual reference fields specified. + +#### 8.2.5.4.1 Marking process of a short-term reference picture as "unused for reference" + +This process is invoked when memory\_management\_control\_operation is equal to 1. + +Let picNumX be specified by + +$$\text{picNumX} = \text{CurrPicNum} - ( \text{difference\_of\_pic\_nums\_minus1} + 1 ). \quad (8-39)$$ + +Depending on field\_pic\_flag the value of picNumX is used to mark a short-term reference picture as "unused for reference" as follows: + +- If field\_pic\_flag is equal to 0, the short-term reference frame or short-term complementary reference field pair specified by picNumX and both of its fields are marked as "unused for reference". +- Otherwise (field\_pic\_flag is equal to 1), the short-term reference field specified by picNumX is marked as "unused for reference". When that reference field is part of a reference frame or a complementary reference field pair, the frame or complementary field pair is also marked as "unused for reference", but the marking of the other field in the same reference frame or complementary reference field pair is not changed. + +#### 8.2.5.4.2 Marking process of a long-term reference picture as "unused for reference" + +This process is invoked when memory\_management\_control\_operation is equal to 2. + +Depending on field\_pic\_flag the value of LongTermPicNum is used to mark a long-term reference picture as "unused for reference" as follows: + +- If field\_pic\_flag is equal to 0, the long-term reference frame or long-term complementary reference field pair having LongTermPicNum equal to long\_term\_pic\_num and both of its fields are marked as "unused for reference". +- Otherwise (field\_pic\_flag is equal to 1), the long-term reference field specified by LongTermPicNum equal to long\_term\_pic\_num is marked as "unused for reference". When that reference field is part of a reference frame or a complementary reference field pair, the frame or complementary field pair is also marked as "unused for reference", but the marking of the other field in the same reference frame or complementary reference field pair is not changed. + +#### 8.2.5.4.3 Assignment process of a LongTermFrameIdx to a short-term reference picture + +This process is invoked when memory\_management\_control\_operation is equal to 3. + +Given the syntax element difference\_of\_pic\_nums\_minus1, the variable picNumX is obtained as specified in clause 8.2.5.4.1. picNumX shall refer to a frame or complementary reference field pair or non-paired reference field marked as "used for short-term reference" and not marked as "non-existing". + +When LongTermFrameIdx equal to long\_term\_frame\_idx is already assigned to a long-term reference frame or a long-term complementary reference field pair, that frame or complementary field pair and both of its fields are marked as "unused for reference". When LongTermFrameIdx is already assigned to a reference field, and that reference field is not part of a complementary field pair that includes the picture specified by picNumX, that field is marked as "unused for reference". + +Depending on field\_pic\_flag the value of LongTermFrameIdx is used to mark a picture from "used for short-term reference" to "used for long-term reference" as follows: + +- If field\_pic\_flag is equal to 0, the marking of the short-term reference frame or short-term complementary reference field pair specified by picNumX and both of its fields are changed from "used for short-term reference" to "used for long-term reference" and assigned LongTermFrameIdx equal to long\_term\_frame\_idx. +- Otherwise (field\_pic\_flag is equal to 1), the marking of the short-term reference field specified by picNumX is changed from "used for short-term reference" to "used for long-term reference" and assigned LongTermFrameIdx equal to long\_term\_frame\_idx. When the field is part of a reference frame or a complementary reference field pair, and the other field of the same reference frame or complementary reference field pair is also marked as "used for long-term reference", the reference frame or complementary reference field pair is also marked as "used for long-term reference" and assigned LongTermFrameIdx equal to long\_term\_frame\_idx. + +#### 8.2.5.4.4 Decoding process for MaxLongTermFrameIdx + +This process is invoked when memory\_management\_control\_operation is equal to 4. + +All pictures for which LongTermFrameIdx is greater than max\_long\_term\_frame\_idx\_plus1 – 1 and that are marked as "used for long-term reference" are marked as "unused for reference". + +The variable MaxLongTermFrameIdx is derived as follows: + +- If max\_long\_term\_frame\_idx\_plus1 is equal to 0, MaxLongTermFrameIdx is set equal to "no long-term frame indices". +- Otherwise (max\_long\_term\_frame\_idx\_plus1 is greater than 0), MaxLongTermFrameIdx is set equal to max\_long\_term\_frame\_idx\_plus1 – 1. + +NOTE – The memory\_management\_control\_operation command equal to 4 can be used to mark long-term reference pictures as "unused for reference". The frequency of transmitting max\_long\_term\_frame\_idx\_plus1 is not specified by this + +Recommendation | International Standard. However, the encoder should send a memory\_management\_control\_operation command equal to 4 upon receiving an error message, such as an intra refresh request message. + +#### 8.2.5.4.5 Marking process of all reference pictures as "unused for reference" and setting MaxLongTermFrameIdx to "no long-term frame indices" + +This process is invoked when memory\_management\_control\_operation is equal to 5. + +All reference pictures are marked as "unused for reference" and the variable MaxLongTermFrameIdx is set equal to "no long-term frame indices". + +#### 8.2.5.4.6 Process for assigning a long-term frame index to the current picture + +This process is invoked when memory\_management\_control\_operation is equal to 6. + +When a variable LongTermFrameIdx equal to long\_term\_frame\_idx is already assigned to a long-term reference frame or a long-term complementary reference field pair, that frame or complementary field pair and both of its fields are marked as "unused for reference". When LongTermFrameIdx is already assigned to a reference field, and that reference field is not part of a complementary field pair that includes the current picture, that field is marked as "unused for reference". + +The current picture is marked as "used for long-term reference" and assigned LongTermFrameIdx equal to long\_term\_frame\_idx. + +When field\_pic\_flag is equal to 0, both its fields are also marked as "used for long-term reference" and assigned LongTermFrameIdx equal to long\_term\_frame\_idx. + +When field\_pic\_flag is equal to 1 and the current picture is the second field (in decoding order) of a complementary reference field pair, and the first field of the complementary reference field pair is also currently marked as "used for long-term reference", the complementary reference field pair is also marked as "used for long-term reference" and assigned LongTermFrameIdx equal to long\_term\_frame\_idx. + +After marking the current decoded reference picture, the total number of frames with at least one field marked as "used for reference", plus the number of complementary field pairs with at least one field marked as "used for reference", plus the number of non-paired fields marked as "used for reference" shall not be greater than Max( max\_num\_ref\_frames, 1 ). + +NOTE – Under some circumstances, the above statement may impose a constraint on the order in which a memory\_management\_control\_operation syntax element equal to 6 can appear in the decoded reference picture marking syntax relative to a memory\_management\_control\_operation syntax element equal to 1, 2, 3, or 4. + +### 8.3 Intra prediction process + +This process is invoked for I and SI macroblock types. + +Inputs to this process are constructed samples prior to the deblocking filter process and, for Intra\_NxN prediction modes (where NxN is equal to 4x4 or 8x8), the values of IntraNxNPredMode from neighbouring macroblocks. + +Outputs of this process are specified as follows: + +- If the macroblock prediction mode is Intra\_4x4 or Intra\_8x8, the outputs are constructed luma samples prior to the deblocking filter process and (when ChromaArrayType is not equal to 0) chroma prediction samples of the macroblock predC, where C is equal to Cb and Cr. +- Otherwise, if mb\_type is not equal to I\_PCM, the outputs are luma prediction samples of the macroblock predL and (when ChromaArrayType is not equal to 0) chroma prediction samples of the macroblock predC, where C is equal to Cb and Cr. +- Otherwise (mb\_type is equal to I\_PCM), the outputs are constructed luma and (when ChromaArrayType is not equal to 0) chroma samples prior to the deblocking filter process. + +The variable MvCnt is set equal to 0. + +Depending on the value of mb\_type the following applies: + +- If mb\_type is equal to I\_PCM, the sample construction process for I\_PCM macroblocks as specified in clause 8.3.5 is invoked. +- Otherwise (mb\_type is not equal to I\_PCM), the following applies: + 1. The decoding processes for Intra prediction modes are described for the luma component as follows: + - If the macroblock prediction mode is equal to Intra\_4x4, the Intra\_4x4 prediction process for luma samples as specified in clause 8.3.1 is invoked. + +- Otherwise, if the macroblock prediction mode is equal to Intra\_8x8, the Intra\_8x8 prediction process as specified in clause 8.3.2 is invoked. + - Otherwise (the macroblock prediction mode is equal to Intra\_16x16), the Intra\_16x16 prediction process as specified in clause 8.3.3 is invoked with $S'_L$ as the input and the outputs are luma prediction samples of the macroblock $pred_L$ . +2. When ChromaArrayType is not equal to 0, the Intra prediction process for chroma samples as specified in clause 8.3.4 is invoked with $S'_{Cb}$ and $S'_{Cr}$ as the inputs and the outputs are chroma prediction samples of the macroblock $pred_{Cb}$ and $pred_{Cr}$ . + +Samples used in the Intra prediction process are the sample values prior to alteration by any deblocking filter operation. + +### 8.3.1 Intra\_4x4 prediction process for luma samples + +This process is invoked when the macroblock prediction mode is equal to Intra\_4x4. + +Inputs to this process are the values of Intra4x4PredMode (if available) or Intra8x8PredMode (if available) from neighbouring macroblocks or macroblock pairs. + +The luma component of a macroblock consists of 16 blocks of 4x4 luma samples. These blocks are inverse scanned using the 4x4 luma block inverse scanning process as specified in clause 6.4.3. + +For all 4x4 luma blocks of the luma component of a macroblock with $luma4x4BlkIdx = 0..15$ , the derivation process for the Intra4x4PredMode as specified in clause 8.3.1.1 is invoked with $luma4x4BlkIdx$ as well as Intra4x4PredMode and Intra8x8PredMode that are previously (in decoding order) derived for adjacent macroblocks as the input and the variable Intra4x4PredMode[ $luma4x4BlkIdx$ ] as the output. + +For each luma block of 4x4 samples indexed using $luma4x4BlkIdx = 0..15$ , the following ordered steps are specified: + +1. The Intra\_4x4 sample prediction process in clause 8.3.1.2 is invoked with $luma4x4BlkIdx$ and the array $S'_L$ containing constructed luma samples prior to the deblocking filter process from adjacent luma blocks as the inputs and the outputs are the Intra\_4x4 luma prediction samples $pred4x4_L[ x, y ]$ with $x, y = 0..3$ . +2. The position of the upper-left sample of a 4x4 luma block with index $luma4x4BlkIdx$ inside the current macroblock is derived by invoking the inverse 4x4 luma block scanning process in clause 6.4.3 with $luma4x4BlkIdx$ as the input and the output being assigned to $( xO, yO )$ . +3. The values of the prediction samples $pred_L[ xO + x, yO + y ]$ with $x, y = 0..3$ are derived by + +$$pred_L[ xO + x, yO + y ] = pred4x4_L[ x, y ] \quad (8-40)$$ + +4. The transform coefficient decoding process and picture construction process prior to deblocking filter process in clause 8.5 is invoked with $pred_L$ and $luma4x4BlkIdx$ as the input and the constructed samples for the current 4x4 luma block $S'_L$ as the output. + +#### 8.3.1.1 Derivation process for Intra4x4PredMode + +Inputs to this process are the index of the 4x4 luma block $luma4x4BlkIdx$ and variable arrays Intra4x4PredMode (if available) and Intra8x8PredMode (if available) that are previously (in decoding order) derived for adjacent macroblocks. + +Output of this process is the variable Intra4x4PredMode[ $luma4x4BlkIdx$ ]. + +Table 8-2 specifies the values for Intra4x4PredMode[ $luma4x4BlkIdx$ ] and the associated names. + +**Table 8-2 – Specification of Intra4x4PredMode[ luma4x4BlkIdx ] and associated names** + +| Intra4x4PredMode[ luma4x4BlkIdx ] | Name of Intra4x4PredMode[ luma4x4BlkIdx ] | +|-----------------------------------|-------------------------------------------------| +| 0 | Intra_4x4_Vertical (prediction mode) | +| 1 | Intra_4x4_Horizontal (prediction mode) | +| 2 | Intra_4x4_DC (prediction mode) | +| 3 | Intra_4x4_Diagonal_Down_Left (prediction mode) | +| 4 | Intra_4x4_Diagonal_Down_Right (prediction mode) | +| 5 | Intra_4x4_Vertical_Right (prediction mode) | +| 6 | Intra_4x4_Horizontal_Down (prediction mode) | +| 7 | Intra_4x4_Vertical_Left (prediction mode) | +| 8 | Intra_4x4_Horizontal_Up (prediction mode) | + +Intra4x4PredMode[ luma4x4BlkIdx ] labelled 0, 1, 3, 4, 5, 6, 7, and 8 represent directions of predictions as illustrated in Figure 8-1. + +![Figure 8-1: Intra_4x4 prediction mode directions (informative). The diagram shows a central point with 16 arrows radiating outwards. The arrows are labeled with numbers 0 through 8. Arrow 0 points vertically downwards. Arrow 1 points horizontally to the right. Arrow 3 points diagonally down and to the left. Arrow 4 points diagonally down and to the right. Arrow 5 points vertically to the right. Arrow 6 points horizontally downwards. Arrow 7 points vertically to the left. Arrow 8 points horizontally upwards. The remaining arrows (2, 10, 11, 12, 13, 14, 15) are unlabeled and represent other possible directions. A small label 'H.264(09)_F8-1' is present in the bottom right corner of the diagram.](15fe9d98813f20e61e8f2177ed1b84b4_img.jpg) + +Figure 8-1: Intra\_4x4 prediction mode directions (informative). The diagram shows a central point with 16 arrows radiating outwards. The arrows are labeled with numbers 0 through 8. Arrow 0 points vertically downwards. Arrow 1 points horizontally to the right. Arrow 3 points diagonally down and to the left. Arrow 4 points diagonally down and to the right. Arrow 5 points vertically to the right. Arrow 6 points horizontally downwards. Arrow 7 points vertically to the left. Arrow 8 points horizontally upwards. The remaining arrows (2, 10, 11, 12, 13, 14, 15) are unlabeled and represent other possible directions. A small label 'H.264(09)\_F8-1' is present in the bottom right corner of the diagram. + +**Figure 8-1 – Intra\_4x4 prediction mode directions (informative)** + +Intra4x4PredMode[ luma4x4BlkIdx ] is derived as specified by the following ordered steps: + +1. The process specified in clause 6.4.11.4 is invoked with luma4x4BlkIdx given as input and the output is assigned to mbAddrA, luma4x4BlkIdxA, mbAddrB, and luma4x4BlkIdxB. +2. The variable dcPredModePredictedFlag is derived as follows: + - If any of the following conditions are true, dcPredModePredictedFlag is set equal to 1 + - the macroblock with address mbAddrA is not available + - the macroblock with address mbAddrB is not available + - the macroblock with address mbAddrA is available and coded in an Inter macroblock prediction mode and constrained\_intra\_pred\_flag is equal to 1 + - the macroblock with address mbAddrB is available and coded in an Inter macroblock prediction mode and constrained\_intra\_pred\_flag is equal to 1 + - Otherwise, dcPredModePredictedFlag is set equal to 0. +3. For N being either replaced by A or B, the variables intraMxMPredModeN are derived as follows: + - If dcPredModePredictedFlag is equal to 1 or the macroblock with address mbAddrN is not coded in Intra\_4x4 or Intra\_8x8 macroblock prediction mode, intraMxMPredModeN is set equal to 2 (Intra\_4x4\_DC prediction mode). + - Otherwise (dcPredModePredictedFlag is equal to 0 and the macroblock with address mbAddrN is coded in Intra\_4x4 or Intra\_8x8 macroblock prediction mode), the following applies: + +- If the macroblock with address mbAddrN is coded in Intra\_4x4 macroblock prediction mode, intraMxMPredModeN is set equal to Intra4x4PredMode[ luma4x4BlkIdxN ], where Intra4x4PredMode is the variable array assigned to the macroblock mbAddrN. +- Otherwise (the macroblock with address mbAddrN is coded in Intra\_8x8 macroblock prediction mode), intraMxMPredModeN is set equal to Intra8x8PredMode[ luma4x4BlkIdxN >> 2 ], where Intra8x8PredMode is the variable array assigned to the macroblock mbAddrN. + +4. Intra4x4PredMode[ luma4x4BlkIdx ] is derived by applying the following procedure: + +``` +predIntra4x4PredMode = Min( intraMxMPredModeA, intraMxMPredModeB ) +if( prev_intra4x4_pred_mode_flag[ luma4x4BlkIdx ] ) + Intra4x4PredMode[ luma4x4BlkIdx ] = predIntra4x4PredMode +else + if( rem_intra4x4_pred_mode[ luma4x4BlkIdx ] < predIntra4x4PredMode ) + Intra4x4PredMode[ luma4x4BlkIdx ] = rem_intra4x4_pred_mode[ luma4x4BlkIdx ] + else + Intra4x4PredMode[ luma4x4BlkIdx ] = rem_intra4x4_pred_mode[ luma4x4BlkIdx ] + 1 +``` + +(8-41) + +### 8.3.1.2 Intra\_4x4 sample prediction + +This process is invoked for each 4x4 luma block of a macroblock with macroblock prediction mode equal to Intra\_4x4 followed by the transform decoding process and picture construction process prior to deblocking for each 4x4 luma block. + +Inputs to this process are: + +- the index of a 4x4 luma block luma4x4BlkIdx, +- an (PicWidthInSamplesL)x(PicHeightInSamplesL) array cSL containing constructed luma samples prior to the deblocking filter process of neighbouring macroblocks. + +Output of this process are the prediction samples pred4x4L[ x, y ], with x, y = 0..3, for the 4x4 luma block with index luma4x4BlkIdx. + +The position of the upper-left sample of a 4x4 luma block with index luma4x4BlkIdx inside the current macroblock is derived by invoking the inverse 4x4 luma block scanning process in clause 6.4.3 with luma4x4BlkIdx as the input and the output being assigned to ( xO, yO ). + +The 13 neighbouring samples p[ x, y ] that are constructed luma samples prior to the deblocking filter process, with x = -1, y = -1..3 and x = 0..7, y = -1, are derived as specified by the following ordered steps: + +1. The luma location ( xN, yN ) is specified by + +$$xN = xO + x \tag{8-42}$$ + +$$yN = yO + y \tag{8-43}$$ + +2. The derivation process for neighbouring locations in clause 6.4.12 is invoked for luma locations with ( xN, yN ) as input and mbAddrN and ( xW, yW ) as output. + +3. Each sample p[ x, y ] with x = -1, y = -1..3 and x = 0..7, y = -1 is derived as follows: + +- If any of the following conditions are true, the sample p[ x, y ] is marked as "not available for Intra\_4x4 prediction" + - mbAddrN is not available, + - the macroblock mbAddrN is coded in an Inter macroblock prediction mode and constrained\_intra\_pred\_flag is equal to 1, + - the macroblock mbAddrN has mb\_type equal to SI and constrained\_intra\_pred\_flag is equal to 1 and the current macroblock does not have mb\_type equal to SI, + - x is greater than 3 and luma4x4BlkIdx is equal to 3 or 11. + +- Otherwise, the sample $p[ x, y ]$ is marked as "available for Intra\_4x4 prediction" and the value of the sample $p[ x, y ]$ is derived as specified by the following ordered steps: + - The location of the upper-left luma sample of the macroblock $mbAddrN$ is derived by invoking the inverse macroblock scanning process in clause 6.4.1 with $mbAddrN$ as the input and the output is assigned to $( xM, yM )$ . + - Depending on the variable $MbaffFrameFlag$ and the macroblock $mbAddrN$ , the sample value $p[ x, y ]$ is derived as follows: + - If $MbaffFrameFlag$ is equal to 1 and the macroblock $mbAddrN$ is a field macroblock, + +$$p[ x, y ] = cSL[ xM + xW, yM + 2 * yW ] \quad (8-44)$$ + +- Otherwise ( $MbaffFrameFlag$ is equal to 0 or the macroblock $mbAddrN$ is a frame macroblock), + +$$p[ x, y ] = cSL[ xM + xW, yM + yW ] \quad (8-45)$$ + +When samples $p[ x, -1 ]$ , with $x = 4..7$ , are marked as "not available for Intra\_4x4 prediction," and the sample $p[ 3, -1 ]$ is marked as "available for Intra\_4x4 prediction," the sample value of $p[ 3, -1 ]$ is substituted for sample values $p[ x, -1 ]$ , with $x = 4..7$ , and samples $p[ x, -1 ]$ , with $x = 4..7$ , are marked as "available for Intra\_4x4 prediction". + +NOTE – Each block is assumed to be constructed into a picture array prior to decoding of the next block. + +Depending on $Intra4x4PredMode[ luma4x4BlkIdx ]$ , one of the Intra\_4x4 prediction modes specified in clauses 8.3.1.2.1 to 8.3.1.2.9 is invoked. + +#### 8.3.1.2.1 Specification of Intra\_4x4\_Vertical prediction mode + +This Intra\_4x4 prediction mode is invoked when $Intra4x4PredMode[ luma4x4BlkIdx ]$ is equal to 0. + +This mode shall be used only when the samples $p[ x, -1 ]$ with $x = 0..3$ are marked as "available for Intra\_4x4 prediction". + +The values of the prediction samples $pred4x4L[ x, y ]$ , with $x, y = 0..3$ , are derived by + +$$pred4x4L[ x, y ] = p[ x, -1 ], \text{ with } x, y = 0..3 \quad (8-46)$$ + +#### 8.3.1.2.2 Specification of Intra\_4x4\_Horizontal prediction mode + +This Intra\_4x4 prediction mode is invoked when $Intra4x4PredMode[ luma4x4BlkIdx ]$ is equal to 1. + +This mode shall be used only when the samples $p[ -1, y ]$ , with $y = 0..3$ , are marked as "available for Intra\_4x4 prediction". + +The values of the prediction samples $pred4x4L[ x, y ]$ , with $x, y = 0..3$ , are derived by + +$$pred4x4L[ x, y ] = p[ -1, y ], \text{ with } x, y = 0..3 \quad (8-47)$$ + +#### 8.3.1.2.3 Specification of Intra\_4x4\_DC prediction mode + +This Intra\_4x4 prediction mode is invoked when $Intra4x4PredMode[ luma4x4BlkIdx ]$ is equal to 2. + +The values of the prediction samples $pred4x4L[ x, y ]$ , with $x, y = 0..3$ , are derived as follows: + +- If all samples $p[ x, -1 ]$ , with $x = 0..3$ , and $p[ -1, y ]$ , with $y = 0..3$ , are marked as "available for Intra\_4x4 prediction", the values of the prediction samples $pred4x4L[ x, y ]$ , with $x, y = 0..3$ , are derived by + +$$pred4x4L[ x, y ] = ( p[ 0, -1 ] + p[ 1, -1 ] + p[ 2, -1 ] + p[ 3, -1 ] + p[ -1, 0 ] + p[ -1, 1 ] + p[ -1, 2 ] + p[ -1, 3 ] + 4 ) \gg 3 \quad (8-48)$$ + +- Otherwise, if any samples $p[ x, -1 ]$ , with $x = 0..3$ , are marked as "not available for Intra\_4x4 prediction" and all samples $p[ -1, y ]$ , with $y = 0..3$ , are marked as "available for Intra\_4x4 prediction", the values of the prediction samples $pred4x4L[ x, y ]$ , with $x, y = 0..3$ , are derived by + +$$pred4x4L[ x, y ] = ( p[ -1, 0 ] + p[ -1, 1 ] + p[ -1, 2 ] + p[ -1, 3 ] + 2 ) \gg 2 \quad (8-49)$$ + +- Otherwise, if any samples $p[-1, y]$ , with $y = 0..3$ , are marked as "not available for Intra\_4x4 prediction" and all samples $p[x, -1]$ , with $x = 0..3$ , are marked as "available for Intra\_4x4 prediction", the values of the prediction samples $pred4x4L[x, y]$ , with $x, y = 0..3$ , are derived by + +$$pred4x4L[x, y] = ( p[0, -1] + p[1, -1] + p[2, -1] + p[3, -1] + 2 ) \gg 2 \quad (8-50)$$ + +- Otherwise (some samples $p[x, -1]$ , with $x = 0..3$ , and some samples $p[-1, y]$ , with $y = 0..3$ , are marked as "not available for Intra\_4x4 prediction"), the values of the prediction samples $pred4x4L[x, y]$ , with $x, y = 0..3$ , are derived by + +$$pred4x4L[x, y] = ( 1 \ll ( BitDepth_Y - 1 ) ) \quad (8-51)$$ + +NOTE – A 4x4 luma block can always be predicted using this mode. + +#### 8.3.1.2.4 Specification of Intra\_4x4\_Diagonal\_Down\_Left prediction mode + +This Intra\_4x4 prediction mode is invoked when $Intra4x4PredMode[luma4x4BlkIdx]$ is equal to 3. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..7$ are marked as "available for Intra\_4x4 prediction". + +The values of the prediction samples $pred4x4L[x, y]$ , with $x, y = 0..3$ , are derived as follows: + +- If $x$ is equal to 3 and $y$ is equal to 3, + +$$pred4x4L[x, y] = ( p[6, -1] + 3 * p[7, -1] + 2 ) \gg 2 \quad (8-52)$$ + +- Otherwise ( $x$ is not equal to 3 or $y$ is not equal to 3), + +$$pred4x4L[x, y] = ( p[x + y, -1] + 2 * p[x + y + 1, -1] + p[x + y + 2, -1] + 2 ) \gg 2 \quad (8-53)$$ + +#### 8.3.1.2.5 Specification of Intra\_4x4\_Diagonal\_Down\_Right prediction mode + +This Intra\_4x4 prediction mode is invoked when $Intra4x4PredMode[luma4x4BlkIdx]$ is equal to 4. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..3$ and $p[-1, y]$ with $y = -1..3$ are marked as "available for Intra\_4x4 prediction". + +The values of the prediction samples $pred4x4L[x, y]$ , with $x, y = 0..3$ , are derived as follows: + +- If $x$ is greater than $y$ , + +$$pred4x4L[x, y] = ( p[x - y - 2, -1] + 2 * p[x - y - 1, -1] + p[x - y, -1] + 2 ) \gg 2 \quad (8-54)$$ + +- Otherwise if $x$ is less than $y$ , + +$$pred4x4L[x, y] = ( p[-1, y - x - 2] + 2 * p[-1, y - x - 1] + p[-1, y - x] + 2 ) \gg 2 \quad (8-55)$$ + +- Otherwise ( $x$ is equal to $y$ ), + +$$pred4x4L[x, y] = ( p[0, -1] + 2 * p[-1, -1] + p[-1, 0] + 2 ) \gg 2 \quad (8-56)$$ + +#### 8.3.1.2.6 Specification of Intra\_4x4\_Vertical\_Right prediction mode + +This Intra\_4x4 prediction mode is invoked when $Intra4x4PredMode[luma4x4BlkIdx]$ is equal to 5. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..3$ and $p[-1, y]$ with $y = -1..3$ are marked as "available for Intra\_4x4 prediction". + +Let the variable $zVR$ be set equal to $2 * x - y$ . + +The values of the prediction samples $pred4x4L[x, y]$ , with $x, y = 0..3$ , are derived as follows: + +- If $zVR$ is equal to 0, 2, 4, or 6, + +$$pred4x4L[x, y] = ( p[x - (y \gg 1) - 1, -1] + p[x - (y \gg 1), -1] + 1 ) \gg 1 \quad (8-57)$$ + +- Otherwise, if zVR is equal to 1, 3, or 5, + +$$\text{pred4x4}_L[x, y] = (p[x - (y \gg 1) - 2, -1] + 2 * p[x - (y \gg 1) - 1, -1] + p[x - (y \gg 1), -1] + 2) \gg 2 \quad (8-58)$$ + +- Otherwise, if zVR is equal to -1, + +$$\text{pred4x4}_L[x, y] = (p[-1, 0] + 2 * p[-1, -1] + p[0, -1] + 2) \gg 2 \quad (8-59)$$ + +- Otherwise (zVR is equal to -2 or -3), + +$$\text{pred4x4}_L[x, y] = (p[-1, y - 1] + 2 * p[-1, y - 2] + p[-1, y - 3] + 2) \gg 2 \quad (8-60)$$ + +### 8.3.1.2.7 Specification of Intra\_4x4\_Horizontal\_Down prediction mode + +This Intra\_4x4 prediction mode is invoked when Intra4x4PredMode[ luma4x4BlkIdx ] is equal to 6. + +This mode shall be used only when the samples p[ x, -1 ] with x = 0..3 and p[ -1, y ] with y = -1..3 are marked as "available for Intra\_4x4 prediction". + +Let the variable zHD be set equal to 2 \* y - x. + +The values of the prediction samples pred4x4L[ x, y ], with x, y = 0..3, are derived as follows: + +- If zHD is equal to 0, 2, 4, or 6, + +$$\text{pred4x4}_L[x, y] = (p[-1, y - (x \gg 1) - 1] + p[-1, y - (x \gg 1) + 1]) \gg 1 \quad (8-61)$$ + +- Otherwise, if zHD is equal to 1, 3, or 5, + +$$\text{pred4x4}_L[x, y] = (p[-1, y - (x \gg 1) - 2] + 2 * p[-1, y - (x \gg 1) - 1] + p[-1, y - (x \gg 1) + 2]) \gg 2 \quad (8-62)$$ + +- Otherwise, if zHD is equal to -1, + +$$\text{pred4x4}_L[x, y] = (p[-1, 0] + 2 * p[-1, -1] + p[0, -1] + 2) \gg 2 \quad (8-63)$$ + +- Otherwise (zHD is equal to -2 or -3), + +$$\text{pred4x4}_L[x, y] = (p[x - 1, -1] + 2 * p[x - 2, -1] + p[x - 3, -1] + 2) \gg 2 \quad (8-64)$$ + +### 8.3.1.2.8 Specification of Intra\_4x4\_Vertical\_Left prediction mode + +This Intra\_4x4 prediction mode is invoked when Intra4x4PredMode[ luma4x4BlkIdx ] is equal to 7. + +This mode shall be used only when the samples p[ x, -1 ] with x = 0..7 are marked as "available for Intra\_4x4 prediction". + +The values of the prediction samples pred4x4L[ x, y ], with x, y = 0..3, are derived as follows: + +- If y is equal to 0 or 2, + +$$\text{pred4x4}_L[x, y] = (p[x + (y \gg 1), -1] + p[x + (y \gg 1) + 1, -1]) \gg 1 \quad (8-65)$$ + +- Otherwise (y is equal to 1 or 3), + +$$\text{pred4x4}_L[x, y] = (p[x + (y \gg 1), -1] + 2 * p[x + (y \gg 1) + 1, -1] + p[x + (y \gg 1) + 2, -1] + 2) \gg 2 \quad (8-66)$$ + +### 8.3.1.2.9 Specification of Intra\_4x4\_Horizontal\_Up prediction mode + +This Intra\_4x4 prediction mode is invoked when Intra4x4PredMode[ luma4x4BlkIdx ] is equal to 8. + +This mode shall be used only when the samples p[ -1, y ] with y = 0..3 are marked as "available for Intra\_4x4 prediction". + +Let the variable zHU be set equal to x + 2 \* y. + +The values of the prediction samples pred4x4L[ x, y ], with x, y = 0..3, are derived as follows: + +- If zHU is equal to 0, 2, or 4 + +$$\text{pred4x4}_L[x, y] = (p[-1, y + (x \gg 1)] + p[-1, y + (x \gg 1) + 1] + 1) \gg 1 \quad (8-67)$$ + +- Otherwise, if zHU is equal to 1 or 3 + +$$\text{pred4x4}_L[x, y] = (p[-1, y + (x \gg 1)] + 2 * p[-1, y + (x \gg 1) + 1] + p[-1, y + (x \gg 1) + 2] + 2) \gg 2 \quad (8-68)$$ + +- Otherwise, if zHU is equal to 5, + +$$\text{pred4x4}_L[x, y] = (p[-1, 2] + 3 * p[-1, 3] + 2) \gg 2 \quad (8-69)$$ + +- Otherwise (zHU is greater than 5), + +$$\text{pred4x4}_L[x, y] = p[-1, 3] \quad (8-70)$$ + +### 8.3.2 Intra\_8x8 prediction process for luma samples + +This process is invoked when the macroblock prediction mode is equal to Intra\_8x8. + +Inputs to this process are the values of Intra4x4PredMode (if available) or Intra8x8PredMode (if available) from the neighbouring macroblocks or macroblock pairs. + +Outputs of this process are 8x8 luma sample arrays as part of the 16x16 luma array of prediction samples of the macroblock $\text{pred}_L$ . + +The luma component of a macroblock consists of 4 blocks of 8x8 luma samples. These blocks are inverse scanned using the inverse 8x8 luma block scanning process as specified in clause 6.4.5. + +For all 8x8 luma blocks of the luma component of a macroblock with $\text{luma8x8BlkIdx} = 0..3$ , the derivation process for Intra8x8PredMode as specified in clause 8.3.2.1 is invoked with $\text{luma8x8BlkIdx}$ as well as Intra4x4PredMode and Intra8x8PredMode that are previously (in decoding order) derived for adjacent macroblocks as the input and the variable $\text{Intra8x8PredMode}[\text{luma8x8BlkIdx}]$ as the output. + +For each luma block of 8x8 samples indexed using $\text{luma8x8BlkIdx} = 0..3$ , the following ordered steps are specified: + +1. The Intra\_8x8 sample prediction process in clause 8.3.2.2 is invoked with $\text{luma8x8BlkIdx}$ and the array $S'_L$ containing constructed samples prior to the deblocking filter process from adjacent luma blocks as the input and the output are the Intra\_8x8 luma prediction samples $\text{pred8x8}_L[x, y]$ with $x, y = 0..7$ . +2. The position of the upper-left sample of an 8x8 luma block with index $\text{luma8x8BlkIdx}$ inside the current macroblock is derived by invoking the inverse 8x8 luma block scanning process in clause 6.4.5 with $\text{luma8x8BlkIdx}$ as the input and the output being assigned to $(xO, yO)$ . +3. The values of the prediction samples $\text{pred}_L[xO + x, yO + y]$ with $x, y = 0..7$ are derived by + +$$\text{pred}_L[xO + x, yO + y] = \text{pred8x8}_L[x, y] \quad (8-71)$$ + +4. The transform coefficient decoding process and picture construction process prior to deblocking filter process in clause 8.5 is invoked with $\text{pred}_L$ and $\text{luma8x8BlkIdx}$ as the input and the constructed samples for the current 8x8 luma block $S'_L$ as the output. + +#### 8.3.2.1 Derivation process for Intra8x8PredMode + +Inputs to this process are the index of the 8x8 luma block $\text{luma8x8BlkIdx}$ and variable arrays Intra4x4PredMode (if available) and Intra8x8PredMode (if available) that are previously (in decoding order) derived for adjacent macroblocks. + +Output of this process is the variable $\text{Intra8x8PredMode}[\text{luma8x8BlkIdx}]$ . + +Table 8-3 specifies the values for $\text{Intra8x8PredMode}[\text{luma8x8BlkIdx}]$ and the associated mnemonic names. + +**Table 8-3 – Specification of Intra8x8PredMode[ luma8x8BlkIdx ] and associated names** + +| Intra8x8PredMode[ luma8x8BlkIdx ] | Name of Intra8x8PredMode[ luma8x8BlkIdx ] | +|-----------------------------------|-------------------------------------------------| +| 0 | Intra_8x8_Vertical (prediction mode) | +| 1 | Intra_8x8_Horizontal (prediction mode) | +| 2 | Intra_8x8_DC (prediction mode) | +| 3 | Intra_8x8_Diagonal_Down_Left (prediction mode) | +| 4 | Intra_8x8_Diagonal_Down_Right (prediction mode) | +| 5 | Intra_8x8_Vertical_Right (prediction mode) | +| 6 | Intra_8x8_Horizontal_Down (prediction mode) | +| 7 | Intra_8x8_Vertical_Left (prediction mode) | +| 8 | Intra_8x8_Horizontal_Up (prediction mode) | + +Intra8x8PredMode[ luma8x8BlkIdx ] is derived as specified by the following ordered steps: + +1. The process specified in clause 6.4.11.2 is invoked with luma8x8BlkIdx given as input and the output is assigned to mbAddrA, luma8x8BlkIdxA, mbAddrB, and luma8x8BlkIdxB. +2. The variable dcPredModePredictedFlag is derived as follows: + - If any of the following conditions are true, dcPredModePredictedFlag is set equal to 1: + - the macroblock with address mbAddrA is not available, + - the macroblock with address mbAddrB is not available, + - the macroblock with address mbAddrA is available and coded in an Inter macroblock prediction mode and constrained\_intra\_pred\_flag is equal to 1, + - the macroblock with address mbAddrB is available and coded in an Inter macroblock prediction mode and constrained\_intra\_pred\_flag is equal to 1. + - Otherwise, dcPredModePredictedFlag is set equal to 0. +3. For N being either replaced by A or B, the variables intraMxMPredModeN are derived as follows: + - If dcPredModePredictedFlag is equal to 1 or the macroblock with address mbAddrN is not coded in Intra\_4x4 or Intra\_8x8 macroblock prediction mode, intraMxMPredModeN is set equal to 2 (Intra\_8x8\_DC prediction mode). + - Otherwise (dcPredModePredictedFlag is equal to 0 and (the macroblock with address mbAddrN is coded in Intra\_4x4 macroblock prediction mode or the macroblock with address mbAddrN is coded in Intra\_8x8 macroblock prediction mode)), the following applies: + - If the macroblock with address mbAddrN is coded in Intra\_8x8 macroblock prediction mode, intraMxMPredModeN is set equal to Intra8x8PredMode[ luma8x8BlkIdxN ], where Intra8x8PredMode is the variable array assigned to the macroblock mbAddrN. + - Otherwise (the macroblock with address mbAddrN is coded in Intra\_4x4 macroblock prediction mode), intraMxMPredModeN is derived by the following procedure, where Intra4x4PredMode is the variable array assigned to the macroblock mbAddrN. + +$$\text{intraMxMPredModeN} = \text{Intra4x4PredMode[ luma8x8BlkIdxN * 4 + n ]} \quad (8-72)$$ + +where the variable n is derived as follows: + +- If N is equal to A, depending on the variable MbaffFrameFlag, the variable luma8x8BlkIdx, the current macroblock, and the macroblock mbAddrN, the following applies: + +- If MbaffFrameFlag is equal to 1, the current macroblock is a frame coded macroblock, the macroblock mbAddrN is a field coded macroblock, and luma8x8BlkIdx is equal to 2, n is set equal to 3. + - Otherwise (MbaffFrameFlag is equal to 0 or the current macroblock is a field coded macroblock or the macroblock mbAddrN is a frame coded macroblock or luma8x8BlkIdx is not equal to 2), n is set equal to 1. + - Otherwise (N is equal to B), n is set equal to 2. +4. Finally, given intraMxMPredModeA and intraMxMPredModeB, the variable Intra8x8PredMode[ luma8x8BlkIdx ] is derived by applying the following procedure. +- ``` + +predIntra8x8PredMode = Min( intraMxMPredModeA, intraMxMPredModeB ) +if( prev_intra8x8_pred_mode_flag[ luma8x8BlkIdx ] ) + Intra8x8PredMode[ luma8x8BlkIdx ] = predIntra8x8PredMode +else + if( rem_intra8x8_pred_mode[ luma8x8BlkIdx ] < predIntra8x8PredMode ) + Intra8x8PredMode[ luma8x8BlkIdx ] = rem_intra8x8_pred_mode[ luma8x8BlkIdx ] + else + Intra8x8PredMode[ luma8x8BlkIdx ] = rem_intra8x8_pred_mode[ luma8x8BlkIdx ] + 1 + +``` +- (8-73) + +### 8.3.2.2 Intra\_8x8 sample prediction + +This process is invoked for each 8x8 luma block of a macroblock with macroblock prediction mode equal to Intra\_8x8 followed by the transform decoding process and picture construction process prior to deblocking for each 8x8 luma block. + +Inputs to this process are: + +- the index of an 8x8 luma block luma8x8BlkIdx, +- an (PicWidthInSamplesL)x(PicHeightInSamplesL) array cSL containing constructed luma samples prior to the deblocking filter process of neighbouring macroblocks. + +Output of this process are the prediction samples pred8x8L[ x, y ], with x, y = 0..7, for the 8x8 luma block with index luma8x8BlkIdx. + +The position of the upper-left sample of an 8x8 luma block with index luma8x8BlkIdx inside the current macroblock is derived by invoking the inverse 8x8 luma block scanning process in clause 6.4.5 with luma8x8BlkIdx as the input and the output being assigned to ( xO, yO ). + +The 25 neighbouring samples p[ x, y ] that are constructed luma samples prior to the deblocking filter process, with x = -1, y = -1..7 and x = 0..15, y = -1, are derived as specified by the following ordered steps: + +1. The luma location ( xN, yN ) is specified by + +$$xN = xO + x \tag{8-74}$$ + +$$yN = yO + y \tag{8-75}$$ + +2. The derivation process for neighbouring locations in clause 6.4.12 is invoked for luma locations with ( xN, yN ) as input and mbAddrN and ( xW, yW ) as output. +3. Each sample p[ x, y ] with x = -1, y = -1..7 and x = 0..15, y = -1 is derived as follows: + - If any of the following conditions are true, the sample p[ x, y ] is marked as "not available for Intra\_8x8 prediction": + - mbAddrN is not available, + - the macroblock mbAddrN is coded in an Inter macroblock prediction mode and constrained\_intra\_pred\_flag is equal to 1. + - Otherwise, the sample p[ x, y ] is marked as "available for Intra\_8x8 prediction" and the sample value p[ x, y ] is derived as specified by the following ordered steps: + - a. The location of the upper-left luma sample of the macroblock mbAddrN is derived by invoking the inverse macroblock scanning process in clause 6.4.1 with mbAddrN as the input and the output is assigned to ( xM, yM ). + +b. Depending on the variable MbaffFrameFlag and the macroblock mbAddrN, the sample value $p[ x, y ]$ is derived as follows: + +- If MbaffFrameFlag is equal to 1 and the macroblock mbAddrN is a field macroblock, + +$$p[ x, y ] = cSL[ xM + xW, yM + 2 * yW ] \quad (8-76)$$ + +- Otherwise (MbaffFrameFlag is equal to 0 or the macroblock mbAddrN is a frame macroblock), + +$$p[ x, y ] = cSL[ xM + xW, yM + yW ] \quad (8-77)$$ + +When samples $p[ x, -1 ]$ , with $x = 8..15$ , are marked as "not available for Intra\_8x8 prediction," and the sample $p[ 7, -1 ]$ is marked as "available for Intra\_8x8 prediction," the sample value of $p[ 7, -1 ]$ is substituted for sample values $p[ x, -1 ]$ , with $x = 8..15$ , and samples $p[ x, -1 ]$ , with $x = 8..15$ , are marked as "available for Intra\_8x8 prediction". + +NOTE – Each block is assumed to be constructed into a picture array prior to decoding of the next block. + +The reference sample filtering process for Intra\_8x8 sample prediction in clause 8.3.2.2.1 is invoked with the samples $p[ x, y ]$ with $x = -1, y = -1..7$ and $x = 0..15, y = -1$ (if available) as input and $p'[ x, y ]$ with $x = -1, y = -1..7$ and $x = 0..15, y = -1$ as output. + +Depending on Intra8x8PredMode[ luma8x8BlkIdx ], one of the Intra\_8x8 prediction modes specified in clauses 8.3.2.2.2 to 8.3.2.2.10 is invoked. + +### 8.3.2.2.1 Reference sample filtering process for Intra\_8x8 sample prediction + +Inputs to this process are the reference samples $p[ x, y ]$ with $x = -1, y = -1..7$ and $x = 0..15, y = -1$ (if available) for Intra\_8x8 sample prediction. + +Outputs of this process are the filtered reference samples $p'[ x, y ]$ with $x = -1, y = -1..7$ and $x = 0..15, y = -1$ for Intra\_8x8 sample prediction. + +When all samples $p[ x, -1 ]$ with $x = 0..15$ are marked as "available for Intra\_8x8 prediction", the following applies: + +1. The value of $p'[ 0, -1 ]$ is derived as follows: + +- If $p[ -1, -1 ]$ is marked as "available for Intra\_8x8 prediction", $p'[ 0, -1 ]$ is derived by + +$$p'[ 0, -1 ] = ( p[ -1, -1 ] + 2 * p[ 0, -1 ] + p[ 1, -1 ] + 2 ) \gg 2 \quad (8-78)$$ + +- Otherwise ( $p[ -1, -1 ]$ is marked as "not available for Intra\_8x8 prediction"), $p'[ 0, -1 ]$ is derived by + +$$p'[ 0, -1 ] = ( 3 * p[ 0, -1 ] + p[ 1, -1 ] + 2 ) \gg 2 \quad (8-79)$$ + +2. The values of $p'[ x, -1 ]$ , with $x = 1..14$ , are derived by + +$$p'[ x, -1 ] = ( p[ x - 1, -1 ] + 2 * p[ x, -1 ] + p[ x + 1, -1 ] + 2 ) \gg 2 \quad (8-80)$$ + +3. The value of $p'[ 15, -1 ]$ is derived by + +$$p'[ 15, -1 ] = ( p[ 14, -1 ] + 3 * p[ 15, -1 ] + 2 ) \gg 2 \quad (8-81)$$ + +When the sample $p[ -1, -1 ]$ is marked as "available for Intra\_8x8 prediction", the value of $p'[ -1, -1 ]$ is derived as follows: + +- If the sample $p[ 0, -1 ]$ is marked as "not available for Intra\_8x8 prediction" or the sample $p[ -1, 0 ]$ is marked as "not available for Intra\_8x8 prediction", the following applies: + +- If the sample $p[ 0, -1 ]$ is marked as "available for Intra\_8x8 prediction", $p'[ -1, -1 ]$ is derived by + +$$p'[ -1, -1 ] = ( 3 * p[ -1, -1 ] + p[ 0, -1 ] + 2 ) \gg 2 \quad (8-82)$$ + +- Otherwise, if the sample $p[ 0, -1 ]$ is marked as "not available for Intra\_8x8 prediction" and the sample $p[ -1, 0 ]$ is marked as "available for Intra\_8x8 prediction", $p'[ -1, -1 ]$ is derived by + +$$p'[ -1, -1 ] = ( 3 * p[ -1, -1 ] + p[ -1, 0 ] + 2 ) \gg 2 \quad (8-83)$$ + +- Otherwise (the sample $p[ 0, -1 ]$ is marked as "not available for Intra\_8x8 prediction" and the sample $p[ -1, 0 ]$ is marked as "not available for Intra\_8x8 prediction"), $p'[ -1, -1 ]$ is set equal to $p[ -1, -1 ]$ . + +NOTE – When both samples $p[0, -1]$ and $p[-1, 0]$ are marked as "not available for Intra\_8x8 prediction", the derived sample $p'[-1, -1]$ is not used in the intra prediction process. + +- Otherwise (the sample $p[0, -1]$ is marked as "available for Intra\_8x8 prediction" and the sample $p[-1, 0]$ is marked as "available for Intra\_8x8 prediction"), $p'[-1, -1]$ is derived by + +$$p'[-1, -1] = (p[0, -1] + 2 * p[-1, -1] + p[-1, 0] + 2) \gg 2 \quad (8-84)$$ + +When all samples $p[-1, y]$ with $y = 0..7$ are marked as "available for Intra\_8x8 prediction", the following applies: + +1. The value of $p'[-1, 0]$ is derived as follows: + +- If $p[-1, -1]$ is marked as "available for Intra\_8x8 prediction", $p'[-1, 0]$ is derived by + +$$p'[-1, 0] = (p[-1, -1] + 2 * p[-1, 0] + p[-1, 1] + 2) \gg 2 \quad (8-85)$$ + +- Otherwise ( $p[-1, -1]$ is marked as "not available for Intra\_8x8 prediction"), $p'[-1, 0]$ is derived by + +$$p'[-1, 0] = (3 * p[-1, 0] + p[-1, 1] + 2) \gg 2 \quad (8-86)$$ + +2. The values of $p'[-1, y]$ , with $y = 1..6$ , are derived by + +$$p'[-1, y] = (p[-1, y-1] + 2 * p[-1, y] + p[-1, y+1] + 2) \gg 2 \quad (8-87)$$ + +3. The value of $p'[-1, 7]$ is derived by + +$$p'[-1, 7] = (p[-1, 6] + 3 * p[-1, 7] + 2) \gg 2 \quad (8-88)$$ + +### 8.3.2.2.2 Specification of Intra\_8x8\_Vertical prediction mode + +This Intra\_8x8 prediction mode is invoked when $\text{Intra8x8PredMode}[\text{luma8x8BlkIdx}]$ is equal to 0. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..7$ are marked as "available for Intra\_8x8 prediction". + +The values of the prediction samples $\text{pred8x8L}[x, y]$ , with $x, y = 0..7$ , are derived by + +$$\text{pred8x8L}[x, y] = p'[x, -1], \text{ with } x, y = 0..7 \quad (8-89)$$ + +### 8.3.2.2.3 Specification of Intra\_8x8\_Horizontal prediction mode + +This Intra\_8x8 prediction mode is invoked when $\text{Intra8x8PredMode}[\text{luma8x8BlkIdx}]$ is equal to 1. + +This mode shall be used only when the samples $p[-1, y]$ , with $y = 0..7$ , are marked as "available for Intra\_8x8 prediction". + +The values of the prediction samples $\text{pred8x8L}[x, y]$ , with $x, y = 0..7$ , are derived by + +$$\text{pred8x8L}[x, y] = p'[-1, y], \text{ with } x, y = 0..7 \quad (8-90)$$ + +### 8.3.2.2.4 Specification of Intra\_8x8\_DC prediction mode + +This Intra\_8x8 prediction mode is invoked when $\text{Intra8x8PredMode}[\text{luma8x8BlkIdx}]$ is equal to 2. + +The values of the prediction samples $\text{pred8x8L}[x, y]$ , with $x, y = 0..7$ , are derived as follows: + +- If all samples $p[x, -1]$ , with $x = 0..7$ , and $p[-1, y]$ , with $y = 0..7$ , are marked as "available for Intra\_8x8 prediction," the values of the prediction samples $\text{pred8x8L}[x, y]$ , with $x, y = 0..7$ , are derived by + +$$\text{pred8x8L}[x, y] = \left( \sum_{x'=0}^7 p'[x', -1] + \sum_{y'=0}^7 p'[-1, y'] + 8 \right) \gg 4 \quad (8-91)$$ + +- Otherwise, if any samples $p[x, -1]$ , with $x = 0..7$ , are marked as "not available for Intra\_8x8 prediction" and all samples $p[-1, y]$ , with $y = 0..7$ , are marked as "available for Intra\_8x8 prediction", the values of the prediction samples $\text{pred8x8L}[x, y]$ , with $x, y = 0..7$ , are derived by + +$$\text{pred8x8L}[x, y] = \left( \sum_{y'=0}^7 p'[-1, y'] + 4 \right) \gg 3 \quad (8-92)$$ + +- Otherwise, if any samples $p[-1, y]$ , with $y = 0..7$ , are marked as "not available for Intra\_8x8 prediction" and all samples $p[x, -1]$ , with $x = 0..7$ , are marked as "available for Intra\_8x8 prediction", the values of the prediction samples $pred8x8L[x, y]$ , with $x, y = 0..7$ , are derived by + +$$pred8x8L[x, y] = \left( \sum_{x'=0}^7 p[x', -1] + 4 \right) \gg 3 \quad (8-93)$$ + +- Otherwise (some samples $p[x, -1]$ , with $x = 0..7$ , and some samples $p[-1, y]$ , with $y = 0..7$ , are marked as "not available for Intra\_8x8 prediction"), the values of the prediction samples $pred8x8L[x, y]$ , with $x, y = 0..7$ , are derived by + +$$pred8x8L[x, y] = (1 \ll (\text{BitDepth}_Y - 1)) \quad (8-94)$$ + +NOTE – An 8x8 luma block can always be predicted using this mode. + +### 8.3.2.2.5 Specification of Intra\_8x8\_Diagonal\_Down\_Left prediction mode + +This Intra\_8x8 prediction mode is invoked when $\text{Intra8x8PredMode}[\text{luma8x8BlkIdx}]$ is equal to 3. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..15$ are marked as "available for Intra\_8x8 prediction". + +The values of the prediction samples $pred8x8L[x, y]$ , with $x, y = 0..7$ , are derived as follows: + +- If $x$ is equal to 7 and $y$ is equal to 7, + +$$pred8x8L[x, y] = (p[14, -1] + 3 * p[15, -1] + 2) \gg 2 \quad (8-95)$$ + +- Otherwise ( $x$ is not equal to 7 or $y$ is not equal to 7), + +$$pred8x8L[x, y] = (p[x + y, -1] + 2 * p[x + y + 1, -1] + p[x + y + 2, -1] + 2) \gg 2 \quad (8-96)$$ + +### 8.3.2.2.6 Specification of Intra\_8x8\_Diagonal\_Down\_Right prediction mode + +This Intra\_8x8 prediction mode is invoked when $\text{Intra8x8PredMode}[\text{luma8x8BlkIdx}]$ is equal to 4. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..7$ and $p[-1, y]$ with $y = -1..7$ are marked as "available for Intra\_8x8 prediction". + +The values of the prediction samples $pred8x8L[x, y]$ , with $x, y = 0..7$ , are derived as follows: + +- If $x$ is greater than $y$ , + +$$pred8x8L[x, y] = (p[x - y - 2, -1] + 2 * p[x - y - 1, -1] + p[x - y, -1] + 2) \gg 2 \quad (8-97)$$ + +- Otherwise if $x$ is less than $y$ , + +$$pred8x8L[x, y] = (p[-1, y - x - 2] + 2 * p[-1, y - x - 1] + p[-1, y - x] + 2) \gg 2 \quad (8-98)$$ + +- Otherwise ( $x$ is equal to $y$ ), + +$$pred8x8L[x, y] = (p[0, -1] + 2 * p[-1, -1] + p[-1, 0] + 2) \gg 2 \quad (8-99)$$ + +### 8.3.2.2.7 Specification of Intra\_8x8\_Vertical\_Right prediction mode + +This Intra\_8x8 prediction mode is invoked when $\text{Intra8x8PredMode}[\text{luma8x8BlkIdx}]$ is equal to 5. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..7$ and $p[-1, y]$ with $y = -1..7$ are marked as "available for Intra\_8x8 prediction". + +Let the variable $zVR$ be set equal to $2 * x - y$ . + +The values of the prediction samples $pred8x8L[x, y]$ , with $x, y = 0..7$ , are derived as follows: + +- If $zVR$ is equal to 0, 2, 4, 6, 8, 10, 12, or 14 + +$$pred8x8L[x, y] = (p[x - (y \gg 1) - 1, -1] + p[x - (y \gg 1), -1] + 1) \gg 1 \quad (8-100)$$ + +- Otherwise, if zVR is equal to 1, 3, 5, 7, 9, 11, or 13 + +$$\text{pred8x8L}[x, y] = (p'[x - (y \gg 1) - 2, -1] + 2 * p'[x - (y \gg 1) - 1, -1] + p'[x - (y \gg 1), -1] + 2) \gg 2 \quad (8-101)$$ + +- Otherwise, if zVR is equal to -1, + +$$\text{pred8x8L}[x, y] = (p'[-1, 0] + 2 * p'[-1, -1] + p'[0, -1] + 2) \gg 2 \quad (8-102)$$ + +- Otherwise (zVR is equal to -2, -3, -4, -5, -6, or -7), + +$$\text{pred8x8L}[x, y] = (p'[-1, y - 2*x - 1] + 2 * p'[-1, y - 2*x - 2] + p'[-1, y - 2*x - 3] + 2) \gg 2 \quad (8-103)$$ + +### 8.3.2.2.8 Specification of Intra\_8x8\_Horizontal\_Down prediction mode + +This Intra\_8x8 prediction mode is invoked when Intra8x8PredMode[ luma8x8BlkIdx ] is equal to 6. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..7$ and $p[-1, y]$ with $y = -1..7$ are marked as "available for Intra\_8x8 prediction". + +Let the variable zHD be set equal to $2 * y - x$ . + +The values of the prediction samples $\text{pred8x8L}[x, y]$ , with $x, y = 0..7$ , are derived as follows: + +- If zHD is equal to 0, 2, 4, 6, 8, 10, 12, or 14 + +$$\text{pred8x8L}[x, y] = (p'[-1, y - (x \gg 1) - 1] + p'[-1, y - (x \gg 1) + 1] + 1) \gg 1 \quad (8-104)$$ + +- Otherwise, if zHD is equal to 1, 3, 5, 7, 9, 11, or 13 + +$$\text{pred8x8L}[x, y] = (p'[-1, y - (x \gg 1) - 2] + 2 * p'[-1, y - (x \gg 1) - 1] + p'[-1, y - (x \gg 1) + 2]) \gg 2 \quad (8-105)$$ + +- Otherwise, if zHD is equal to -1, + +$$\text{pred8x8L}[x, y] = (p'[-1, 0] + 2 * p'[-1, -1] + p'[0, -1] + 2) \gg 2 \quad (8-106)$$ + +- Otherwise (zHD is equal to -2, -3, -4, -5, -6, -7), + +$$\text{pred8x8L}[x, y] = (p'[x - 2*y - 1, -1] + 2 * p'[x - 2*y - 2, -1] + p'[x - 2*y - 3, -1] + 2) \gg 2 \quad (8-107)$$ + +### 8.3.2.2.9 Specification of Intra\_8x8\_Vertical\_Left prediction mode + +This Intra\_8x8 prediction mode is invoked when Intra8x8PredMode[ luma8x8BlkIdx ] is equal to 7. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..15$ are marked as "available for Intra\_8x8 prediction". + +The values of the prediction samples $\text{pred8x8L}[x, y]$ , with $x, y = 0..7$ , are derived as follows: + +- If y is equal to 0, 2, 4 or 6 + +$$\text{pred8x8L}[x, y] = (p'[x + (y \gg 1), -1] + p'[x + (y \gg 1) + 1, -1] + 1) \gg 1 \quad (8-108)$$ + +- Otherwise (y is equal to 1, 3, 5, 7), + +$$\text{pred8x8L}[x, y] = (p'[x + (y \gg 1), -1] + 2 * p'[x + (y \gg 1) + 1, -1] + p'[x + (y \gg 1) + 2, -1] + 2) \gg 2 \quad (8-109)$$ + +### 8.3.2.2.10 Specification of Intra\_8x8\_Horizontal\_Up prediction mode + +This Intra\_8x8 prediction mode is invoked when Intra8x8PredMode[ luma8x8BlkIdx ] is equal to 8. + +This mode shall be used only when the samples $p[-1, y]$ with $y = 0..7$ are marked as "available for Intra\_8x8 prediction". + +Let the variable zHU be set equal to $x + 2 * y$ . + +The values of the prediction samples $\text{pred8x8L}[x, y]$ , with $x, y = 0..7$ , are derived as follows: + +- If zHU is equal to 0, 2, 4, 6, 8, 10, or 12 + +$$\text{pred8x8L}[x, y] = (p'[-1, y + (x \gg 1)] + p'[-1, y + (x \gg 1) + 1] + 1) \gg 1 \quad (8-110)$$ + +- Otherwise, if zHU is equal to 1, 3, 5, 7, 9, or 11 + +$$\text{pred8x8L}[x, y] = (p'[-1, y + (x \gg 1)] + 2 * p'[-1, y + (x \gg 1) + 1] + p'[-1, y + (x \gg 1) + 2] + 2) \gg 2 \quad (8-111)$$ + +- Otherwise, if zHU is equal to 13, + +$$\text{pred8x8L}[x, y] = (p'[-1, 6] + 3 * p'[-1, 7] + 2) \gg 2 \quad (8-112)$$ + +- Otherwise (zHU is greater than 13), + +$$\text{pred8x8L}[x, y] = p'[-1, 7] \quad (8-113)$$ + +### 8.3.3 Intra\_16x16 prediction process for luma samples + +This process is invoked when the macroblock prediction mode is equal to Intra\_16x16. It specifies how the Intra prediction luma samples for the current macroblock are derived. + +Input to this process is a (PicWidthInSamplesL)x(PicHeightInSamplesL) array cSL containing constructed luma samples prior to the deblocking filter process of neighbouring macroblocks. + +Outputs of this process are Intra prediction luma samples for the current macroblock predL[x, y]. + +The 33 neighbouring samples p[x, y] that are constructed luma samples prior to the deblocking filter process, with x = -1, y = -1..15 and with x = 0..15, y = -1, are derived as specified by the following ordered steps: + +1. The derivation process for neighbouring locations in clause 6.4.12 is invoked for luma locations with (x, y) assigned to (xN, yN) as input and mbAddrN and (xW, yW) as output. +2. Each sample p[x, y] with x = -1, y = -1..15 and with x = 0..15, y = -1 is derived as follows: + - If any of the following conditions are true, the sample p[x, y] is marked as "not available for Intra\_16x16 prediction": + - mbAddrN is not available, + - the macroblock mbAddrN is coded in an Inter macroblock prediction mode and constrained\_intra\_pred\_flag is equal to 1, + - the macroblock mbAddrN has mb\_type equal to SI and constrained\_intra\_pred\_flag is equal to 1. + - Otherwise, the sample p[x, y] is marked as "available for Intra\_16x16 prediction" and the value of the sample p[x, y] is derived as specified by the following ordered steps: + - a. The location of the upper-left luma sample of the macroblock mbAddrN is derived by invoking the inverse macroblock scanning process in clause 6.4.1 with mbAddrN as the input and the output is assigned to (xM, yM). + - b. Depending on the variable MbaffFrameFlag and the macroblock mbAddrN, the sample value p[x, y] is derived as follows: + - If MbaffFrameFlag is equal to 1 and the macroblock mbAddrN is a field macroblock, +$$p[x, y] = cS_L[xM + xW, yM + 2 * yW] \quad (8-114)$$ + - Otherwise (MbaffFrameFlag is equal to 0 or the macroblock mbAddrN is a frame macroblock), +$$p[x, y] = cS_L[xM + xW, yM + yW] \quad (8-115)$$ + +Let predL[x, y] with x, y = 0..15 denote the prediction samples for the 16x16 luma block samples. + +Intra\_16x16 prediction modes are specified in Table 8-4. + +**Table 8-4 – Specification of Intra16x16PredMode and associated names** + +| Intra16x16PredMode | Name of Intra16x16PredMode | +|--------------------|------------------------------------------| +| 0 | Intra_16x16_Vertical (prediction mode) | +| 1 | Intra_16x16_Horizontal (prediction mode) | +| 2 | Intra_16x16_DC (prediction mode) | +| 3 | Intra_16x16_Plane (prediction mode) | + +Depending on Intra16x16PredMode, one of the Intra\_16x16 prediction modes specified in clauses 8.3.3.1 to 8.3.3.4 is invoked. + +**8.3.3.1 Specification of Intra\_16x16\_Vertical prediction mode** + +This Intra\_16x16 prediction mode shall be used only when the samples $p[ x, -1 ]$ with $x = 0..15$ are marked as "available for Intra\_16x16 prediction". + +The values of the prediction samples $predL[ x, y ]$ , with $x, y = 0..15$ , are derived by + +$$predL[ x, y ] = p[ x, -1 ], \text{ with } x, y = 0..15 \quad (8-116)$$ + +**8.3.3.2 Specification of Intra\_16x16\_Horizontal prediction mode** + +This Intra\_16x16 prediction mode shall be used only when the samples $p[-1, y]$ with $y = 0..15$ are marked as "available for Intra\_16x16 prediction". + +The values of the prediction samples $predL[ x, y ]$ , with $x, y = 0..15$ , are derived by + +$$predL[ x, y ] = p[ -1, y ], \text{ with } x, y = 0..15 \quad (8-117)$$ + +**8.3.3.3 Specification of Intra\_16x16\_DC prediction mode** + +This Intra\_16x16 prediction mode operates, depending on whether the neighbouring samples are marked as "available for Intra\_16x16 prediction", as follows: + +- If all neighbouring samples $p[ x, -1 ]$ , with $x = 0..15$ , and $p[ -1, y ]$ , with $y = 0..15$ , are marked as "available for Intra\_16x16 prediction", the prediction for all luma samples in the macroblock is given by: + +$$predL[ x, y ] = \left( \sum_{x'=0}^{15} p[x', -1] + \sum_{y'=0}^{15} p[-1, y'] + 16 \right) \gg 5, \text{ with } x, y = 0..15 \quad (8-118)$$ + +- Otherwise, if any of the neighbouring samples $p[ x, -1 ]$ , with $x = 0..15$ , are marked as "not available for Intra\_16x16 prediction" and all of the neighbouring samples $p[ -1, y ]$ , with $y = 0..15$ , are marked as "available for Intra\_16x16 prediction", the prediction for all luma samples in the macroblock is given by: + +$$predL[ x, y ] = \left( \sum_{y'=0}^{15} p[-1, y'] + 8 \right) \gg 4, \text{ with } x, y = 0..15 \quad (8-119)$$ + +- Otherwise, if any of the neighbouring samples $p[ -1, y ]$ , with $y = 0..15$ , are marked as "not available for Intra\_16x16 prediction" and all of the neighbouring samples $p[ x, -1 ]$ , with $x = 0..15$ , are marked as "available for Intra\_16x16 prediction", the prediction for all luma samples in the macroblock is given by: + +$$predL[ x, y ] = \left( \sum_{x'=0}^{15} p[x', -1] + 8 \right) \gg 4, \text{ with } x, y = 0..15 \quad (8-120)$$ + +- Otherwise (some of the neighbouring samples $p[ x, -1 ]$ , with $x = 0..15$ , and some of the neighbouring samples $p[ -1, y ]$ , with $y = 0..15$ , are marked as "not available for Intra\_16x16 prediction"), the prediction for all luma samples in the macroblock is given by: + +$$predL[ x, y ] = ( 1 \ll ( \text{BitDepth}_Y - 1 ) ), \text{ with } x, y = 0..15 \quad (8-121)$$ + +**8.3.3.4 Specification of Intra\_16x16\_Plane prediction mode** + +This Intra\_16x16 prediction mode shall be used only when the samples $p[ x, -1 ]$ with $x = -1..15$ and $p[ -1, y ]$ with $y = 0..15$ are marked as "available for Intra\_16x16 prediction". + +The values of the prediction samples $\text{pred}_L[ x, y ]$ , with $x, y = 0..15$ , are derived by + +$$\text{pred}_L[ x, y ] = \text{Clip1V}( ( a + b * ( x - 7 ) + c * ( y - 7 ) + 16 ) \gg 5 ), \text{ with } x, y = 0..15, \quad (8-122)$$ + +where + +$$a = 16 * ( p[ -1, 15 ] + p[ 15, -1 ] ) \quad (8-123)$$ + +$$b = ( 5 * H + 32 ) \gg 6 \quad (8-124)$$ + +$$c = ( 5 * V + 32 ) \gg 6 \quad (8-125)$$ + +and H and V are specified as + +$$H = \sum_{x'=0}^7 ( x'+1 ) * ( p[ 8 + x', -1 ] - p[ 6 - x', -1 ] ) \quad (8-126)$$ + +$$V = \sum_{y'=0}^7 ( y'+1 ) * ( p[ -1, 8 + y' ] - p[ -1, 6 - y' ] ) \quad (8-127)$$ + +### 8.3.4 Intra prediction process for chroma samples + +This process is invoked for I and SI macroblock types. It specifies how the Intra prediction chroma samples for the current macroblock are derived. + +Inputs to this process are two $(\text{PicWidthInSamples}_C) \times (\text{PicHeightInSamples}_C)$ arrays $\text{cS}_{Cb}$ and $\text{cS}_{Cr}$ containing constructed chroma samples prior to the deblocking filter process of neighbouring macroblocks. + +Outputs of this process are Intra prediction chroma samples for the current macroblock $\text{pred}_{Cb}[ x, y ]$ and $\text{pred}_{Cr}[ x, y ]$ . + +Depending on the value of $\text{ChromaArrayType}$ , the following applies: + +- If $\text{ChromaArrayType}$ is equal to 3, the Intra prediction chroma samples for the current macroblock $\text{pred}_{Cb}[ x, y ]$ and $\text{pred}_{Cr}[ x, y ]$ are derived using the Intra prediction process for chroma samples with $\text{ChromaArrayType}$ equal to 3 as specified in clause 8.3.4.5. +- Otherwise ( $\text{ChromaArrayType}$ is equal to 1 or 2), the following text specifies the Intra prediction chroma samples for the current macroblock $\text{pred}_{Cb}[ x, y ]$ and $\text{pred}_{Cr}[ x, y ]$ . + +Both chroma blocks ( $Cb$ and $Cr$ ) of the macroblock use the same prediction mode. The prediction mode is applied to each of the chroma blocks separately. The process specified in this clause is invoked for each chroma block. In the remainder of this clause, chroma block refers to one of the two chroma blocks and the subscript $C$ is used as a replacement of the subscript $Cb$ or $Cr$ . + +The neighbouring samples $p[ x, y ]$ that are constructed chroma samples prior to the deblocking filter process, with $x = -1$ , $y = -1..MbHeightC - 1$ and with $x = 0..MbWidthC - 1$ , $y = -1$ , are derived as specified by the following ordered steps: + +1. The derivation process for neighbouring locations in clause 6.4.12 is invoked for chroma locations with $( x, y )$ assigned to $( xN, yN )$ as input and $\text{mbAddrN}$ and $( xW, yW )$ as output. +2. Each sample $p[ x, y ]$ is derived as follows: + - If any of the following conditions are true, the sample $p[ x, y ]$ is marked as "not available for Intra chroma prediction": + - $\text{mbAddrN}$ is not available, + - the macroblock $\text{mbAddrN}$ is coded in an Inter macroblock prediction mode and $\text{constrained\_intra\_pred\_flag}$ is equal to 1, + - the macroblock $\text{mbAddrN}$ has $\text{mb\_type}$ equal to SI and $\text{constrained\_intra\_pred\_flag}$ is equal to 1 and the current macroblock does not have $\text{mb\_type}$ equal to SI. + - Otherwise, the sample $p[ x, y ]$ is marked as "available for Intra chroma prediction" and the value of the sample $p[ x, y ]$ is derived as specified by the following ordered steps: + - a. The location of the upper-left luma sample of the macroblock $\text{mbAddrN}$ is derived by invoking the inverse macroblock scanning process in clause 6.4.1 with $\text{mbAddrN}$ as the input and the output is assigned to $( xL, yL )$ . + +b. The location ( xM, yM ) of the upper-left chroma sample of the macroblock mbAddr is derived by: + +$$xM = ( xL \gg 4 ) * MbWidthC \quad (8-128)$$ + +$$yM = ( ( yL \gg 4 ) * MbHeightC ) + ( yL \% 2 ) \quad (8-129)$$ + +c. Depending on the variable MbaffFrameFlag and the macroblock mbAddrN, the sample value p[ x, y ] is derived as follows: + +- If MbaffFrameFlag is equal to 1 and the macroblock mbAddrN is a field macroblock, + +$$p[ x, y ] = cSc[ xM + xW, yM + 2 * yW ] \quad (8-130)$$ + +- Otherwise (MbaffFrameFlag is equal to 0 or the macroblock mbAddrN is a frame macroblock), + +$$p[ x, y ] = cSc[ xM + xW, yM + yW ] \quad (8-131)$$ + +Let predc[ x, y ] with x = 0..MbWidthC – 1, y = 0..MbHeightC – 1 denote the prediction samples for the chroma block samples. + +Intra chroma prediction modes are specified in Table 8-5. + +**Table 8-5 – Specification of Intra chroma prediction modes and associated names** + +| intra_chroma_pred_mode | Name of intra_chroma_pred_mode | +|------------------------|-------------------------------------------| +| 0 | Intra_Chroma_DC (prediction mode) | +| 1 | Intra_Chroma_Horizontal (prediction mode) | +| 2 | Intra_Chroma_Vertical (prediction mode) | +| 3 | Intra_Chroma_Plane (prediction mode) | + +Depending on intra\_chroma\_pred\_mode, one of the Intra chroma prediction modes specified in clauses 8.3.4.1 to 8.3.4.4 is invoked. + +#### 8.3.4.1 Specification of Intra\_Chroma\_DC prediction mode + +This Intra chroma prediction mode is invoked when intra\_chroma\_pred\_mode is equal to 0. + +For each chroma block of 4x4 samples indexed by chroma4x4BlkIdx = 0..( 1 << ( ChromaArrayType + 1 ) ) – 1, the following applies: + +- The position of the upper-left sample of a 4x4 chroma block with index chroma4x4BlkIdx inside the current macroblock is derived by invoking the inverse 4x4 chroma block scanning process in clause 6.4.7 with chroma4x4BlkIdx as the input and the output being assigned to ( xO, yO ). + +- Depending on the values of xO and yO, the following applies: + +- If ( xO, yO ) is equal to ( 0, 0 ) or xO and yO are greater than 0, the values of the prediction samples predc[ x + xO, y + yO ] with x, y = 0..3 are derived as follows: + +- If all samples p[ x + xO, –1 ], with x = 0..3, and p[ –1, y + yO ], with y = 0..3, are marked as "available for Intra chroma prediction", the values of the prediction samples predc[ x + xO, y + yO ], with x, y = 0..3, are derived as: + +$$pred_c[ x + xO, y + yO ] = \left( \sum_{x'=0}^3 p[ x' + xO, -1 ] + \sum_{y'=0}^3 p[ -1, y' + yO ] + 4 \right) \gg 3, \text{ with } x, y = 0..3. \quad (8-132)$$ + +- Otherwise, if any samples p[ x + xO, –1 ], with x = 0..3, are marked as "not available for Intra chroma prediction" and all samples p[ –1, y + yO ], with y = 0..3, are marked as "available for Intra chroma prediction", the values of the prediction samples predc[ x + xO, y + yO ], with x, y = 0..3, are derived as: + +$$pred_c[ x + xO, y + yO ] = \left( \sum_{y'=0}^3 p[ -1, y' + yO ] + 2 \right) \gg 2, \text{ with } x, y = 0..3. \quad (8-133)$$ + +- Otherwise, if any samples $p[-1, y + yO]$ , with $y = 0..3$ , are marked as "not available for Intra chroma prediction" and all samples $p[x + xO, -1]$ , with $x = 0..3$ , are marked as "available for Intra chroma prediction", the values of the prediction samples $pred_c[x + xO, y + yO]$ , with $x, y = 0..3$ , are derived as: + +$$pred_c[x + xO, y + yO] = \left( \sum_{x'=0}^3 p[x' + xO, -1] + 2 \right) \gg 2, \text{ with } x, y = 0..3. \quad (8-134)$$ + +- Otherwise (some samples $p[x + xO, -1]$ , with $x = 0..3$ , and some samples $p[-1, y + yO]$ , with $y = 0..3$ , are marked as "not available for Intra chroma prediction"), the values of the prediction samples $pred_c[x + xO, y + yO]$ , with $x, y = 0..3$ , are derived as: + +$$pred_c[x + xO, y + yO] = (1 \ll (\text{BitDepth}_c - 1)), \text{ with } x, y = 0..3. \quad (8-135)$$ + +- Otherwise, if $xO$ is greater than 0 and $yO$ is equal to 0, the values of the prediction samples $pred_c[x + xO, y + yO]$ with $x, y = 0..3$ are derived as follows: + +- If all samples $p[x + xO, -1]$ , with $x = 0..3$ , are marked as "available for Intra chroma prediction", the values of the prediction samples $pred_c[x + xO, y + yO]$ , with $x, y = 0..3$ , are derived as: + +$$pred_c[x + xO, y + yO] = \left( \sum_{x'=0}^3 p[x' + xO, -1] + 2 \right) \gg 2, \text{ with } x, y = 0..3. \quad (8-136)$$ + +- Otherwise, if all samples $p[-1, y + yO]$ , with $y = 0..3$ , are marked as "available for Intra chroma prediction", the values of the prediction samples $pred_c[x + xO, y + yO]$ , with $x, y = 0..3$ , are derived as: + +$$pred_c[x + xO, y + yO] = \left( \sum_{y'=0}^3 p[-1, y' + yO] + 2 \right) \gg 2, \text{ with } x, y = 0..3. \quad (8-137)$$ + +- Otherwise (some samples $p[x + xO, -1]$ , with $x = 0..3$ , and some samples $p[-1, y + yO]$ , with $y = 0..3$ , are marked as "not available for Intra chroma prediction"), the values of the prediction samples $pred_c[x + xO, y + yO]$ , with $x, y = 0..3$ , are derived as: + +$$pred_c[x + xO, y + yO] = (1 \ll (\text{BitDepth}_c - 1)), \text{ with } x, y = 0..3. \quad (8-138)$$ + +- Otherwise ( $xO$ is equal to 0 and $yO$ is greater than 0), the values of the prediction samples $pred_c[x + xO, y + yO]$ with $x, y = 0..3$ are derived as follows: + +- If all samples $p[-1, y + yO]$ , with $y = 0..3$ , are marked as "available for Intra chroma prediction", the values of the prediction samples $pred_c[x + xO, y + yO]$ , with $x, y = 0..3$ , are derived as: + +$$pred_c[x + xO, y + yO] = \left( \sum_{y'=0}^3 p[-1, y' + yO] + 2 \right) \gg 2, \text{ with } x, y = 0..3. \quad (8-139)$$ + +- Otherwise, if all samples $p[x + xO, -1]$ , with $x = 0..3$ , are marked as "available for Intra chroma prediction", the values of the prediction samples $pred_c[x + xO, y + yO]$ , with $x, y = 0..3$ , are derived as: + +$$pred_c[x + xO, y + yO] = \left( \sum_{x'=0}^3 p[x' + xO, -1] + 2 \right) \gg 2, \text{ with } x, y = 0..3. \quad (8-140)$$ + +- Otherwise (some samples $p[x + xO, -1]$ , with $x = 0..3$ , and some samples $p[-1, y + yO]$ , with $y = 0..3$ , are marked as "not available for Intra chroma prediction"), the values of the prediction samples $pred_c[x + xO, y + yO]$ , with $x, y = 0..3$ , are derived as: + +$$pred_c[x + xO, y + yO] = (1 \ll (\text{BitDepth}_c - 1)), \text{ with } x, y = 0..3. \quad (8-141)$$ + +### 8.3.4.2 Specification of Intra\_Chroma\_Horizontal prediction mode + +This Intra chroma prediction mode is invoked when $intra\_chroma\_pred\_mode$ is equal to 1. + +This mode shall be used only when the samples $p[-1, y]$ with $y = 0..MbHeightC - 1$ are marked as "available for Intra chroma prediction". + +The values of the prediction samples $\text{predC}[x, y]$ are derived as: + +$$\text{predC}[x, y] = p[-1, y], \text{ with } x = 0..MbWidthC - 1 \text{ and } y = 0..MbHeightC - 1 \quad (8-142)$$ + +### 8.3.4.3 Specification of Intra\_Chroma\_Vertical prediction mode + +This Intra chroma prediction mode is invoked when $\text{intra\_chroma\_pred\_mode}$ is equal to 2. + +This mode shall be used only when the samples $p[x, -1]$ with $x = 0..MbWidthC - 1$ are marked as "available for Intra chroma prediction". + +The values of the prediction samples $\text{predC}[x, y]$ are derived as: + +$$\text{predC}[x, y] = p[x, -1], \text{ with } x = 0..MbWidthC - 1 \text{ and } y = 0..MbHeightC - 1 \quad (8-143)$$ + +### 8.3.4.4 Specification of Intra\_Chroma\_Plane prediction mode + +This Intra chroma prediction mode is invoked when $\text{intra\_chroma\_pred\_mode}$ is equal to 3. + +This mode shall be used only when the samples $p[x, -1]$ , with $x = 0..MbWidthC - 1$ and $p[-1, y]$ , with $y = -1..MbHeightC - 1$ are marked as "available for Intra chroma prediction". + +Let the variable $xCF$ be set equal to $((\text{ChromaArrayType} == 3) ? 4 : 0)$ and let the variable $yCF$ be set equal to $((\text{ChromaArrayType} != 1) ? 4 : 0)$ . + +The values of the prediction samples $\text{predC}[x, y]$ are derived by: + +$$\text{predC}[x, y] = \text{Clip1C}((a + b * (x - 3 - xCF) + c * (y - 3 - yCF) + 16) \gg 5), \\ \text{with } x = 0..MbWidthC - 1 \text{ and } y = 0..MbHeightC - 1 \quad (8-144)$$ + +where + +$$a = 16 * (p[-1, MbHeightC - 1] + p[MbWidthC - 1, -1]) \quad (8-145)$$ + +$$b = ((34 - 29 * (\text{ChromaArrayType} == 3)) * H + 32) \gg 6 \quad (8-146)$$ + +$$c = ((34 - 29 * (\text{ChromaArrayType} != 1)) * V + 32) \gg 6 \quad (8-147)$$ + +and $H$ and $V$ are specified as: + +$$H = \sum_{x'=0}^{3+xCF} (x'+1) * (p[4 + xCF + x', -1] - p[2 + xCF - x', -1]) \quad (8-148)$$ + +$$V = \sum_{y'=0}^{3+yCF} (y'+1) * (p[-1, 4 + yCF + y'] - p[-1, 2 + yCF - y']) \quad (8-149)$$ + +### 8.3.4.5 Intra prediction for chroma samples with ChromaArrayType equal to 3 + +This process is invoked when $\text{ChromaArrayType}$ is equal to 3. This process is invoked for I and SI macroblock types. It specifies how the Intra prediction chroma samples for the current macroblock are derived when $\text{ChromaArrayType}$ is equal to 3. + +Inputs to this process are constructed samples prior to the deblocking filter process from neighbouring Cb and Cr blocks and for Intra\_NxN (where NxN is equal to 4x4 or 8x8) prediction mode, the associated values of $\text{IntraNxNPredMode}$ from neighbouring macroblocks. + +Outputs of this process are the Intra prediction samples of the Cb and Cr components of the macroblock or in case of the Intra\_NxN prediction process, the outputs are NxN Cb sample arrays as part of the 16x16 Cb array of prediction samples of the macroblock, and NxN Cr sample arrays as part of the 16x16 Cr array of prediction samples of the macroblock. + +Each Cb, Cr, and luma block with the same block index of the macroblock use the same prediction mode. The prediction mode is applied to each of the Cb and Cr blocks separately. The process specified in this clause is invoked for each Cb and Cr block. + +Depending on the macroblock prediction mode, the following applies: + +- If the macroblock prediction mode is equal to Intra\_4x4, the following applies: + +- The same process described in clause 8.3.1 is also applied to Cb or Cr samples, substituting luma with Cb or Cr, substituting luma4x4BlkIdx with cb4x4BlkIdx or cr4x4BlkIdx, substituting pred4x4L with pred4x4Cb or pred4x4Cr, and substituting BitDepthY with BitDepthC. +- The output variable Intra4x4PredMode[luma4x4BlkIdx] from the process described in clause 8.3.1.1 is also used for the 4x4 Cb or 4x4 Cr blocks with index luma4x4BlkIdx equal to index cb4x4BlkIdx or cr4x4BlkIdx. +- The process to derive prediction Cb or Cr samples is identical to the process described in clause 8.3.1.2 and its subsequent subclauses when substituting luma with Cb or Cr, substituting pred4x4L with pred4x4Cb or pred4x4Cr, and substituting BitDepthY with BitDepthC. +- Otherwise, if the macroblock prediction mode is equal to Intra\_8x8, the following applies: + - The same process described in clause 8.3.2 is also applied to Cb or Cr samples, substituting luma with Cb or Cr, substituting luma8x8BlkIdx with cb8x8BlkIdx or cr8x8BlkIdx, substituting pred8x8L with pred8x8Cb or pred8x8Cr, and substituting BitDepthY with BitDepthC. + - The output variable Intra8x8PredMode[luma8x8BlkIdx] from the process described in clause 8.3.2.1 is used for the 8x8 Cb or 8x8 Cr blocks with index luma8x8BlkIdx equal to index cb8x8BlkIdx or cr8x8BlkIdx. + - The process to derive prediction Cb or Cr samples is identical to the process described in clause 8.3.2.2 and its subsequent subclauses when substituting luma with Cb or Cr, substituting pred8x8L with pred8x8Cb or pred8x8Cr, and substituting BitDepthY with BitDepthC. +- Otherwise (the macroblock prediction mode is equal to Intra\_16x16), the same process described in clause 8.3.3 and its subsequent subclauses is also applied to Cb or Cr samples, substituting luma with Cb or Cr, substituting predL with predCb or predCr, and substituting BitDepthY with BitDepthC. + +### 8.3.5 Sample construction process for I\_PCM macroblocks + +This process is invoked when mb\_type is equal to I\_PCM. + +The variable dy is derived as follows: + +- If MbaffFrameFlag is equal to 1 and the current macroblock is a field macroblock, dy is set equal to 2. +- Otherwise (MbaffFrameFlag is equal to 0 or the current macroblock is a frame macroblock), dy is set equal to 1. + +The position of the upper-left luma sample of the current macroblock is derived by invoking the inverse macroblock scanning process in clause 6.4.1 with CurrMbAddr as input and the output being assigned to ( xP, yP ). + +The constructed luma samples prior to the deblocking process are generated as specified by: + +$$\begin{aligned} & \text{for( i = 0; i < 256; i++ )} \\ & S'_L[ ( xP + ( i \% 16 ), yP + dy * ( i / 16 ) ) ] = \text{pcm\_sample\_luma[ i ]} \end{aligned} \quad (8-150)$$ + +When ChromaArrayType is not equal to 0, the constructed chroma samples prior to the deblocking process are generated as specified by: + +$$\begin{aligned} & \text{for( i = 0; i < MbWidthC * MbHeightC; i++ )} \{ \\ & S'_{Cb}[ ( xP / \text{SubWidthC} ) + ( i \% \text{MbWidthC} ), \\ & \quad ( ( yP + \text{SubHeightC} - 1 ) / \text{SubHeightC} ) + dy * ( i / \text{MbWidthC} ) ] = \\ & \quad \text{pcm\_sample\_chroma[ i ]} \\ & S'_{Cr}[ ( xP / \text{SubWidthC} ) + ( i \% \text{MbWidthC} ), \\ & \quad ( ( yP + \text{SubHeightC} - 1 ) / \text{SubHeightC} ) + dy * ( i / \text{MbWidthC} ) ] = \\ & \quad \text{pcm\_sample\_chroma[ i + MbWidthC * MbHeightC ]} \\ & \} \end{aligned} \quad (8-151)$$ + +## 8.4 Inter prediction process + +This process is invoked when decoding P and B macroblock types. + +Outputs of this process are Inter prediction samples for the current macroblock that are a 16x16 array predL of luma samples and when ChromaArrayType is not equal to 0 two (MbWidthC)x(MbHeightC) arrays predCb and predCr of chroma samples, one for each of the chroma components Cb and Cr. + +The partitioning of a macroblock is specified by mb\_type. Each macroblock partition is referred to by mbPartIdx. When the macroblock partitioning consists of partitions that are equal to sub-macroblocks, each sub-macroblock can be further partitioned into sub-macroblock partitions as specified by sub\_mb\_type[ mbPartIdx ]. Each sub-macroblock partition is + +referred to by subMbPartIdx. When the macroblock partitioning does not consist of sub-macroblocks, subMbPartIdx is set equal to 0. + +The following steps are specified for each macroblock partition or for each sub-macroblock partition. + +The functions MbPartWidth(), MbPartHeight(), SubMbPartWidth(), and SubMbPartHeight() describing the width and height of macroblock partitions and sub-macroblock partitions are specified in Tables 7-13, 7-14, 7-17, and 7-18. + +The range of the macroblock partition index mbPartIdx is derived as follows: + +- If mb\_type is equal to B\_Skip or B\_Direct\_16x16, mbPartIdx proceeds over values 0..3. +- Otherwise (mb\_type is not equal to B\_Skip or B\_Direct\_16x16), mbPartIdx proceeds over values 0..NumMbPart( mb\_type ) – 1. + +For each value of mbPartIdx, the variables partWidth and partHeight for each macroblock partition or sub-macroblock partition in the macroblock are derived as follows: + +- If mb\_type is not equal to P\_8x8, P\_8x8ref0, B\_Skip, B\_Direct\_16x16, or B\_8x8, subMbPartIdx is set equal to 0, and partWidth and partHeight are derived as: + +$$\text{partWidth} = \text{MbPartWidth}(\text{mb\_type}) \quad (8-152)$$ + +$$\text{partHeight} = \text{MbPartHeight}(\text{mb\_type}) \quad (8-153)$$ + +- Otherwise, if mb\_type is equal to P\_8x8 or P\_8x8ref0, or mb\_type is equal to B\_8x8 and sub\_mb\_type[ mbPartIdx ] is not equal to B\_Direct\_8x8, subMbPartIdx proceeds over values 0..NumSubMbPart( sub\_mb\_type[ mbPartIdx ] ) – 1, and partWidth and partHeight are derived as: + +$$\text{partWidth} = \text{SubMbPartWidth}(\text{sub\_mb\_type}[\text{mbPartIdx}]) \quad (8-154)$$ + +$$\text{partHeight} = \text{SubMbPartHeight}(\text{sub\_mb\_type}[\text{mbPartIdx}]) \quad (8-155)$$ + +- Otherwise (mb\_type is equal to B\_Skip or B\_Direct\_16x16, or mb\_type is equal to B\_8x8 and sub\_mb\_type[ mbPartIdx ] is equal to B\_Direct\_8x8), subMbPartIdx proceeds over values 0..3, and partWidth and partHeight are derived as: + +$$\text{partWidth} = 4 \quad (8-156)$$ + +$$\text{partHeight} = 4 \quad (8-157)$$ + +When ChromaArrayType is not equal to 0, the variables partWidthC and partHeightC are derived as: + +$$\text{partWidthC} = \text{partWidth} / \text{SubWidthC} \quad (8-158)$$ + +$$\text{partHeightC} = \text{partHeight} / \text{SubHeightC} \quad (8-159)$$ + +Let the variable MvCnt be initially set equal to 0 before any invocation of clause 8.4.1 for the macroblock. + +The Inter prediction process for a macroblock partition mbPartIdx and a sub-macroblock partition subMbPartIdx consists of the following ordered steps: + +1. The derivation process for motion vector components and reference indices as specified in clause 8.4.1 is invoked. + +Inputs to this process are: + +- a macroblock partition mbPartIdx, +- a sub-macroblock partition subMbPartIdx. + +Outputs of this process are: + +- luma motion vectors mvL0 and mvL1 and when ChromaArrayType is not equal to 0, the chroma motion vectors mvCL0 and mvCL1 +- reference indices refIdxL0 and refIdxL1 +- prediction list utilization flags predFlagL0 and predFlagL1 +- the sub-macroblock partition motion vector count subMvCnt. + +2. The variable MvCnt is incremented by subMvCnt. + +- When (weighted\_pred\_flag is equal to 1 and (slice\_type % 5) is equal to 0 or 3) or (weighted\_bipred\_idc is greater than 0 and (slice\_type % 5) is equal to 1), the derivation process for prediction weights as specified in clause 8.4.3 is invoked. + +Inputs to this process are: + +- reference indices refIdxL0 and refIdxL1 +- prediction list utilization flags predFlagL0 and predFlagL1 + +Outputs of this process are variables for weighted prediction logWDC, w0C, w1C, o0C, o1C with C being replaced by L and, when ChromaArrayType is not equal to 0, Cb and Cr. + +- The decoding process for Inter prediction samples as specified in clause 8.4.2 is invoked. + +Inputs to this process are: + +- a macroblock partition mbPartIdx, +- a sub-macroblock partition subMbPartIdx, +- variables specifying partition width and height for luma and chroma (if available), partWidth, partHeight, partWidthC (if available), and partHeightC (if available), +- luma motion vectors mvL0 and mvL1 and when ChromaArrayType is not equal to 0, the chroma motion vectors mvCL0 and mvCL1, +- reference indices refIdxL0 and refIdxL1, +- prediction list utilization flags predFlagL0 and predFlagL1, +- variables for weighted prediction logWDC, w0C, w1C, o0C, o1C with C being replaced by L and, when ChromaArrayType is not equal to 0, Cb and Cr. + +Outputs of this process are inter prediction samples (pred); which are a (partWidth)x(partHeight) array predPartL of prediction luma samples and when ChromaArrayType is not equal to 0 two (partWidthC)x(partHeightC) arrays predPartCr and predPartCb of prediction chroma samples, one for each of the chroma components Cb and Cr. + +For use in derivation processes of variables invoked later in the decoding process, the following assignments are made: + +$$\text{MvL0[ mbPartIdx ][ subMbPartIdx ]} = \text{mvL0} \quad (8-160)$$ + +$$\text{MvL1[ mbPartIdx ][ subMbPartIdx ]} = \text{mvL1} \quad (8-161)$$ + +$$\text{RefIdxL0[ mbPartIdx ]} = \text{refIdxL0} \quad (8-162)$$ + +$$\text{RefIdxL1[ mbPartIdx ]} = \text{refIdxL1} \quad (8-163)$$ + +$$\text{PredFlagL0[ mbPartIdx ]} = \text{predFlagL0} \quad (8-164)$$ + +$$\text{PredFlagL1[ mbPartIdx ]} = \text{predFlagL1} \quad (8-165)$$ + +The location of the upper-left sample of the macroblock partition relative to the upper-left sample of the macroblock is derived by invoking the inverse macroblock partition scanning process as described in clause 6.4.2.1 with mbPartIdx as the input and ( xP, yP ) as the output. + +The location of the upper-left sample of the sub-macroblock partition relative to the upper-left sample of the macroblock partition is derived by invoking the inverse sub-macroblock partition scanning process as described in clause 6.4.2.2 with subMbPartIdx as the input and ( xS, yS ) as the output. + +The macroblock prediction is formed by placing the macroblock or sub-macroblock partition prediction samples in their correct relative positions in the macroblock, as follows. + +The variable predL[ xP + xS + x, yP + yS + y ] with x = 0..partWidth – 1, y = 0..partHeight – 1 is derived by: + +$$\text{pred}_L[ \text{xP} + \text{xS} + \text{x}, \text{yP} + \text{yS} + \text{y} ] = \text{predPart}_L[ \text{x}, \text{y} ] \quad (8-166)$$ + +When ChromaArrayType is not equal to 0, the variable predC with x = 0..partWidthC – 1, y = 0..partHeightC – 1, and C in predC and predPartC being replaced by Cb or Cr is derived by: + +$$\text{pred}_c[ xP / \text{SubWidthC} + xS / \text{SubWidthC} + x, yP / \text{SubHeightC} + yS / \text{SubHeightC} + y ] = \text{predPart}_c[ x, y ] \quad (8-167)$$ + +#### 8.4.1 Derivation process for motion vector components and reference indices + +Inputs to this process are: + +- a macroblock partition `mbPartIdx`, +- a sub-macroblock partition `subMbPartIdx`. + +Outputs of this process are: + +- luma motion vectors `mvL0` and `mvL1` and when `ChromaArrayType` is not equal to 0, the chroma motion vectors `mvCL0` and `mvCL1`, +- reference indices `refIdxL0` and `refIdxL1`, +- prediction list utilization flags `predFlagL0` and `predFlagL1`, +- a motion vector count variable `subMvCnt`. + +For the derivation of the variables `mvL0` and `mvL1` as well as `refIdxL0` and `refIdxL1`, the following applies: + +- If `mb_type` is equal to `P_Skip`, the derivation process for luma motion vectors for skipped macroblocks in P and SP slices in clause 8.4.1.1 is invoked with the output being the luma motion vectors `mvL0` and reference indices `refIdxL0`, and `predFlagL0` is set equal to 1. `mvL1` and `refIdxL1` are marked as not available and `predFlagL1` is set equal to 0. The motion vector count variable `subMvCnt` is set equal to 1. +- Otherwise, if `mb_type` is equal to `B_Skip` or `B_Direct_16x16` or `sub_mb_type[ mbPartIdx ]` is equal to `B_Direct_8x8`, the derivation process for luma motion vectors for `B_Skip`, `B_Direct_16x16`, and `B_Direct_8x8` in B slices in clause 8.4.1.2 is invoked with `mbPartIdx` and `subMbPartIdx` as the input and the output being the luma motion vectors `mvL0`, `mvL1`, the reference indices `refIdxL0`, `refIdxL1`, the motion vector count variable `subMvCnt`, and the prediction utilization flags `predFlagL0` and `predFlagL1`. +- Otherwise, for X being replaced by either 0 or 1 in the variables `predFlagLX`, `mvLX`, `refIdxLX`, and in `Pred_LX` and in the syntax elements `ref_idx_IX` and `mvd_IX`, the following applies: + +1. The variables `refIdxLX` and `predFlagLX` are derived as follows: + +- If `MbPartPredMode( mb_type, mbPartIdx )` or `SubMbPredMode( sub_mb_type[ mbPartIdx ] )` is equal to `Pred_LX` or to `BiPred`, + +$$\text{refIdxLX} = \text{ref\_idx\_IX}[ \text{mbPartIdx} ] \quad (8-168)$$ + +$$\text{predFlagLX} = 1 \quad (8-169)$$ + +- Otherwise, the variables `refIdxLX` and `predFlagLX` are specified by + +$$\text{refIdxLX} = -1 \quad (8-170)$$ + +$$\text{predFlagLX} = 0 \quad (8-171)$$ + +2. The motion vector count variable `subMvCnt` is set equal to `predFlagL0 + predFlagL1`. + +3. The variable `currSubMbType` is derived as follows: + +- If the macroblock type is equal to `B_8x8`, `currSubMbType` is set equal to `sub_mb_type[ mbPartIdx ]`. +- Otherwise (the macroblock type is not equal to `B_8x8`), `currSubMbType` is set equal to "na". + +4. When `predFlagLX` is equal to 1, the derivation process for luma motion vector prediction in clause 8.4.1.3 is invoked with `mbPartIdx`, `subMbPartIdx`, `refIdxLX`, and `currSubMbType` as the inputs and the output being `mvpLX`. The luma motion vectors are derived by + +$$\text{mvLX}[ 0 ] = \text{mvpLX}[ 0 ] + \text{mvd\_IX}[ \text{mbPartIdx} ][ \text{subMbPartIdx} ][ 0 ] \quad (8-172)$$ + +$$\text{mvLX}[ 1 ] = \text{mvpLX}[ 1 ] + \text{mvd\_IX}[ \text{mbPartIdx} ][ \text{subMbPartIdx} ][ 1 ] \quad (8-173)$$ + +When ChromaArrayType is not equal to 0 and predFlagLX (with X being either 0 or 1) is equal to 1, the derivation process for chroma motion vectors in clause 8.4.1.4 is invoked with mvLX and refIdxLX as input and the output being mvCLX. + +#### 8.4.1.1 Derivation process for luma motion vectors for skipped macroblocks in P and SP slices + +This process is invoked when mb\_type is equal to P\_Skip. + +Outputs of this process are the motion vector mvL0 and the reference index refIdxL0. + +The reference index refIdxL0 for a skipped macroblock is derived as: + +$$\text{refIdxL0} = 0. \quad (8-174)$$ + +For the derivation of the motion vector mvL0 of a P\_Skip macroblock type, the following ordered steps are specified: + +1. The process specified in clause 8.4.1.3.2 is invoked with mbPartIdx set equal to 0, subMbPartIdx set equal to 0, currSubMbType set equal to "na", and listSuffixFlag set equal to 0 as input and the output is assigned to mbAddrA, mbAddrB, mvL0A, mvL0B, refIdxL0A, and refIdxL0B. +2. The variable mvL0 is specified as follows: + - If any of the following conditions are true, both components of the motion vector mvL0 are set equal to 0: + - mbAddrA is not available, + - mbAddrB is not available, + - refIdxL0A is equal to 0 and both components of mvL0A are equal to 0, + - refIdxL0B is equal to 0 and both components of mvL0B are equal to 0. + - Otherwise, the derivation process for luma motion vector prediction as specified in clause 8.4.1.3 is invoked with mbPartIdx = 0, subMbPartIdx = 0, refIdxL0, and currSubMbType = "na" as inputs and the output is assigned to mvL0. + +NOTE – The output is directly assigned to mvL0, since the predictor is equal to the actual motion vector. + +#### 8.4.1.2 Derivation process for luma motion vectors for B\_Skip, B\_Direct\_16x16, and B\_Direct\_8x8 + +This process is invoked when mb\_type is equal to B\_Skip or B\_Direct\_16x16, or sub\_mb\_type[ mbPartIdx ] is equal to B\_Direct\_8x8. + +Inputs to this process are mbPartIdx and subMbPartIdx. + +Outputs of this process are the reference indices refIdxL0, refIdxL1, the motion vectors mvL0 and mvL1, the motion vector count variable subMvCnt, and the prediction list utilization flags, predFlagL0 and predFlagL1. + +The derivation process depends on the value of direct\_spatial\_mv\_pred\_flag, which is present in the bitstream in the slice header syntax as specified in clause 7.3.3, and is specified as follows: + +- If direct\_spatial\_mv\_pred\_flag is equal to 1, the mode in which the outputs of this process are derived is referred to as spatial direct prediction mode. +- Otherwise (direct\_spatial\_mv\_pred\_flag is equal to 0), mode in which the outputs of this process are derived is referred to as temporal direct prediction mode. + +Both spatial and temporal direct prediction mode use the co-located motion vectors and reference indices as specified in clause 8.4.1.2.1. + +The motion vectors and reference indices are derived as follows: + +- If spatial direct prediction mode is used, the direct motion vector and reference index prediction mode specified in clause 8.4.1.2.2 is used, with subMvCnt being an output. +- Otherwise (temporal direct prediction mode is used), the direct motion vector and reference index prediction mode specified in clause 8.4.1.2.3 is used and the variable subMvCnt is derived as follows: + - If subMbPartIdx is equal to 0, subMvCnt is set equal to 2. + - Otherwise (subMbPartIdx is not equal to 0), subMvCnt is set equal to 0. + +##### 8.4.1.2.1 Derivation process for the co-located 4x4 sub-macroblock partitions + +Inputs to this process are mbPartIdx and subMbPartIdx. + +Outputs of this process are the picture colPic, the co-located macroblock mbAddrCol, the motion vector mvCol, the reference index refIdxCol, and the variable vertMvScale (which can be One\_To\_One, Frm\_To\_Fld or Fld\_To\_Frm). + +When RefPicList1[ 0 ] is a frame or a complementary field pair, let firstRefPicL1Top and firstRefPicL1Bottom be the top and bottom fields of RefPicList1[ 0 ], respectively, and let the following variables be specified as + +$$\text{topAbsDiffPOC} = \text{Abs}(\text{DiffPicOrderCnt}(\text{firstRefPicL1Top}, \text{CurrPic})) \quad (8-175)$$ + +$$\text{bottomAbsDiffPOC} = \text{Abs}(\text{DiffPicOrderCnt}(\text{firstRefPicL1Bottom}, \text{CurrPic})) \quad (8-176)$$ + +The variable colPic specifies the picture that contains the co-located macroblock as specified in Table 8-6. + +**Table 8-6 – Specification of the variable colPic** + +| field_pic_flag | RefPicList1[ 0 ] is ... | mb_field_decoding_flag | additional condition | colPic | +|----------------|----------------------------|------------------------|-----------------------------------|---------------------------------------| +| 1 | a field of a decoded frame | | | the frame containing RefPicList1[ 0 ] | +| | a decoded field | | | RefPicList1[ 0 ] | +| 0 | a decoded frame | | | RefPicList1[ 0 ] | +| | a complementary field pair | 0 | topAbsDiffPOC < bottomAbsDiffPOC | firstRefPicL1Top | +| | | | topAbsDiffPOC >= bottomAbsDiffPOC | firstRefPicL1Bottom | +| | | 1 | ( CurrMbAddr & 1 ) == 0 | firstRefPicL1Top | +| | | | ( CurrMbAddr & 1 ) != 0 | firstRefPicL1Bottom | + +NOTE – The picture order count values of a complementary field pair marked as "used for long-term reference" have an impact on the decoding process when the current picture is a coded frame, the current macroblock is a frame macroblock, and the complementary field pair marked as "used for long-term reference" is the first picture in reference list 1. + +Let PicCodingStruct( X ) be a function with the argument X being either CurrPic or colPic. It is specified in Table 8-7. + +**Table 8-7 – Specification of PicCodingStruct( X )** + +| X is coded with field_pic_flag equal to ... | mb_adaptive_frame_field_flag | PicCodingStruct( X ) | +|---------------------------------------------|------------------------------|----------------------| +| 1 | | FLD | +| 0 | 0 | FRM | +| 0 | 1 | AFRM | + +The variable luma4x4BlkIdx is derived as follows: + +- If direct\_8x8\_inference\_flag is equal to 0, luma4x4BlkIdx is set equal to (4 \* mbPartIdx + subMbPartIdx). +- Otherwise (direct\_8x8\_inference\_flag is equal to 1), luma4x4BlkIdx is set equal to (5 \* mbPartIdx). + +The inverse 4x4 luma block scanning process as specified in clause 6.4.3 is invoked with luma4x4BlkIdx as the input and ( x, y ) assigned to ( xCol, yCol ) as the output. + +Table 8-8 specifies the co-located macroblock address mbAddrCol, yM, and the variable vertMvScale in two steps: + +1. Specification of a macroblock address mbAddrX depending on PicCodingStruct( CurrPic ), and PicCodingStruct( colPic ). + +NOTE – It is not possible for CurrPic and colPic picture coding types to be either (FRM, AFRM) or (AFRM, FRM) because these picture coding types must be separated by an IDR picture. + +2. Specification of mbAddrCol, yM, and vertMvScale depending on mb\_field\_decoding\_flag and the variable fieldDecodingFlagX, which is derived as follows: + +- If the macroblock mbAddrX in the picture colPic is a field macroblock, fieldDecodingFlagX is set equal to 1. + +- Otherwise (the macroblock mbAddrX in the picture colPic is a frame macroblock), fieldDecodingFlagX is set equal to 0. + +Unspecified values in Table 8-8 indicate that the value of the corresponding variable is not relevant for the current table row. + +mbAddrCol is set equal to CurrMbAddr or to one of the following values. + +$$\text{mbAddrCol1} = 2 * \text{PicWidthInMbs} * ( \text{CurrMbAddr} / \text{PicWidthInMbs} ) + ( \text{CurrMbAddr} \% \text{PicWidthInMbs} ) + \text{PicWidthInMbs} * ( \text{yCol} / 8 ) \quad (8-177)$$ + +$$\text{mbAddrCol2} = 2 * \text{CurrMbAddr} + ( \text{yCol} / 8 ) \quad (8-178)$$ + +$$\text{mbAddrCol3} = 2 * \text{CurrMbAddr} + \text{bottom\_field\_flag} \quad (8-179)$$ + +$$\text{mbAddrCol4} = \text{PicWidthInMbs} * ( \text{CurrMbAddr} / ( 2 * \text{PicWidthInMbs} ) ) + ( \text{CurrMbAddr} \% \text{PicWidthInMbs} ) \quad (8-180)$$ + +$$\text{mbAddrCol5} = \text{CurrMbAddr} / 2 \quad (8-181)$$ + +$$\text{mbAddrCol6} = 2 * ( \text{CurrMbAddr} / 2 ) + ( ( \text{topAbsDiffPOC} < \text{bottomAbsDiffPOC} ) ? 0 : 1 ) \quad (8-182)$$ + +$$\text{mbAddrCol7} = 2 * ( \text{CurrMbAddr} / 2 ) + ( \text{yCol} / 8 ) \quad (8-183)$$ + +**Table 8-8 – Specification of mbAddrCol, yM, and vertMvScale** + +| PicCodingStruct( CurrPic ) | PicCodingStruct( colPic ) | mbAddrX | mb_field_decoding_flag | fieldDecodingFlagX | mbAddrCol | yM | vertMvScale | +|----------------------------|---------------------------|--------------|------------------------|--------------------|------------|---------------------------------------------------------------|-------------| +| FLD | FLD | | | | CurrMbAddr | yCol | One_To_One | +| | FRM | | | | mbAddrCol1 | ( 2 * yCol ) % 16 | Frm_To_Fld | +| | AFRM | 2*CurrMbAddr | | 0 | mbAddrCol2 | ( 2 * yCol ) % 16 | Frm_To_Fld | +| | | | | 1 | mbAddrCol3 | yCol | One_To_One | +| FRM | FLD | | | | mbAddrCol4 | 8 * ( ( CurrMbAddr / PicWidthInMbs ) % 2 ) + 4 * ( yCol / 8 ) | Fld_To_Frm | +| | FRM | | | | CurrMbAddr | yCol | One_To_One | +| AFRM | FLD | | 0 | | mbAddrCol5 | 8 * ( CurrMbAddr % 2 ) + 4 * ( yCol / 8 ) | Fld_To_Frm | +| | | | 1 | | mbAddrCol5 | yCol | One_To_One | +| | AFRM | CurrMbAddr | 0 | 0 | CurrMbAddr | yCol | One_To_One | +| | | | | 1 | mbAddrCol6 | 8 * ( CurrMbAddr % 2 ) + 4 * ( yCol / 8 ) | Fld_To_Frm | +| | | CurrMbAddr | 1 | 0 | mbAddrCol7 | ( 2 * yCol ) % 16 | Frm_To_Fld | +| | | | | 1 | CurrMbAddr | yCol | One_To_One | + +Let $mbTypeCol$ be the syntax element $mb\_type$ of the macroblock with address $mbAddrCol$ inside the picture $colPic$ and, when $mbTypeCol$ is equal to $P\_8x8$ , $P\_8x8ref0$ , or $B\_8x8$ , let $subMbTypeCol$ be the syntax element list $sub\_mb\_type$ of the macroblock with address $mbAddrCol$ inside the picture $colPic$ . + +Let $mbPartIdxCol$ be the macroblock partition index of the co-located partition and $subMbPartIdxCol$ the sub-macroblock partition index of the co-located sub-macroblock partition. The derivation process for macroblock and sub-macroblock partition indices as specified in clause 6.4.13.4 is invoked with the luma location $(xCol, yM)$ , the macroblock type $mbTypeCol$ , and, when $mbTypeCol$ is equal to $P\_8x8$ , $P\_8x8ref0$ , or $B\_8x8$ , the list of sub-macroblock types $subMbTypeCol$ as the inputs and the outputs are the macroblock partition index $mbPartIdxCol$ and the sub-macroblock partition index $subMbPartIdxCol$ . + +The motion vector $mvCol$ and the reference index $refIdxCol$ are derived as follows: + +- If the macroblock $mbAddrCol$ is coded in an Intra macroblock prediction mode, both components of $mvCol$ are set equal to 0 and $refIdxCol$ is set equal to $-1$ . +- Otherwise (the macroblock $mbAddrCol$ is not coded in an Intra macroblock prediction mode), the prediction utilization flags $predFlagL0Col$ and $predFlagL1Col$ are set equal to $PredFlagL0[ mbPartIdxCol ]$ and $PredFlagL1[ mbPartIdxCol ]$ , respectively, which are the prediction utilization flags that have been assigned to the macroblock partition $mbAddrCol\backslash mbPartIdxCol$ inside the picture $colPic$ , and the following applies: + - If $predFlagL0Col$ is equal to 1, the motion vector $mvCol$ and the reference index $refIdxCol$ are set equal to $MvL0[ mbPartIdxCol ][ subMbPartIdxCol ]$ and $RefIdxL0[ mbPartIdxCol ]$ , respectively, which are the motion vector $mvL0$ and the reference index $refIdxL0$ that have been assigned to the (sub-)macroblock partition $mbAddrCol\backslash mbPartIdxCol\backslash subMbPartIdxCol$ inside the picture $colPic$ . + - Otherwise ( $predFlagL0Col$ is equal to 0 and $predFlagL1Col$ is equal to 1), the motion vector $mvCol$ and the reference index $refIdxCol$ are set equal to $MvL1[ mbPartIdxCol ][ subMbPartIdxCol ]$ and $RefIdxL1[ mbPartIdxCol ]$ , respectively, which are the motion vector $mvL1$ and the reference index $refIdxL1$ that have been assigned to the (sub-)macroblock partition $mbAddrCol\backslash mbPartIdxCol\backslash subMbPartIdxCol$ inside the picture $colPic$ . + +#### 8.4.1.2.2 Derivation process for spatial direct luma motion vector and reference index prediction mode + +This process is invoked when $direct\_spatial\_mv\_pred\_flag$ is equal to 1 and any of the following conditions are true: + +- $mb\_type$ is equal to $B\_Skip$ , +- $mb\_type$ is equal to $B\_Direct\_16x16$ , +- $sub\_mb\_type[ mbPartIdx ]$ is equal to $B\_Direct\_8x8$ . + +Inputs to this process are $mbPartIdx$ , $subMbPartIdx$ . + +Outputs of this process are the reference indices $refIdxL0$ , $refIdxL1$ , the motion vectors $mvL0$ and $mvL1$ , the motion vector count variable $subMvCnt$ , and the prediction list utilization flags, $predFlagL0$ and $predFlagL1$ . + +The reference indices $refIdxL0$ and $refIdxL1$ and the variable $directZeroPredictionFlag$ are derived by applying the following ordered steps. + +1. Let the variable $currSubMbType$ be set equal to $sub\_mb\_type[ mbPartIdx ]$ . +2. The process specified in clause 8.4.1.3.2 is invoked with $mbPartIdx = 0$ , $subMbPartIdx = 0$ , $currSubMbType$ , and $listSuffixFlag = 0$ as inputs and the output is assigned to the motion vectors $mvL0N$ and the reference indices $refIdxL0N$ with $N$ being replaced by $A$ , $B$ , or $C$ . +3. The process specified in clause 8.4.1.3.2 is invoked with $mbPartIdx = 0$ , $subMbPartIdx = 0$ , $currSubMbType$ , and $listSuffixFlag = 1$ as inputs and the output is assigned to the motion vectors $mvL1N$ and the reference indices $refIdxL1N$ with $N$ being replaced by $A$ , $B$ , or $C$ . + +NOTE 1 – The motion vectors $mvL0N$ , $mvL1N$ and the reference indices $refIdxL0N$ , $refIdxL1N$ are identical for all $4x4$ sub-macroblock partitions of a macroblock. + +4. The reference indices $refIdxL0$ , $refIdxL1$ , and $directZeroPredictionFlag$ are derived by: + +$$refIdxL0 = \text{MinPositive}( refIdxL0A, \text{MinPositive}( refIdxL0B, refIdxL0C ) ) \quad (8-184)$$ + +$$refIdxL1 = \text{MinPositive}( refIdxL1A, \text{MinPositive}( refIdxL1B, refIdxL1C ) ) \quad (8-185)$$ + +$$directZeroPredictionFlag = 0 \quad (8-186)$$ + +where + +$$\text{MinPositive}(x, y) = \begin{cases} \text{Min}(x, y) & \text{if } x \geq 0 \text{ and } y \geq 0 \\ \text{Max}(x, y) & \text{otherwise} \end{cases} \quad (8-187)$$ + +- 5. When both reference indices `refIdxL0` and `refIdxL1` are less than 0, + +$$\text{refIdxL0} = 0 \quad (8-188)$$ + +$$\text{refIdxL1} = 0 \quad (8-189)$$ + +$$\text{directZeroPredictionFlag} = 1 \quad (8-190)$$ + +The process specified in clause 8.4.1.2.1 is invoked with `mbPartIdx`, `subMbPartIdx` given as input and the output is assigned to `refIdxCol` and `mvCol`. + +The variable `colZeroFlag` is derived as follows: + +- If all of the following conditions are true, `colZeroFlag` is set equal to 1: + - `RefPicList1[ 0 ]` is currently marked as "used for short-term reference", + - `refIdxCol` is equal to 0, + - both motion vector components `mvCol[ 0 ]` and `mvCol[ 1 ]` lie in the range of $-1$ to $1$ in units specified as follows: + - If the co-located macroblock is a frame macroblock, the units of `mvCol[ 0 ]` and `mvCol[ 1 ]` are units of quarter luma frame samples. + - Otherwise (the co-located macroblock is a field macroblock), the units of `mvCol[ 0 ]` and `mvCol[ 1 ]` are units of quarter luma field samples. + +NOTE 2 – For purposes of determining the condition above, the value `mvCol[ 1 ]` is not scaled to use the units of a motion vector for the current macroblock in cases when the current macroblock is a frame macroblock and the co-located macroblock is a field macroblock or when the current macroblock is a field macroblock and the co-located macroblock is a frame macroblock. This aspect differs from the use of `mvCol[ 1 ]` in the temporal direct mode as specified in clause 8.4.1.2.3, which applies scaling to the motion vector of the co-located macroblock to use the same units as the units of a motion vector for the current macroblock, using Equation 8-193 or Equation 8-194 in these cases. + +- Otherwise, `colZeroFlag` is set equal to 0. + +The motion vectors `mvLX` (with `X` being 0 or 1) are derived as follows: + +- If any of the following conditions are true, both components of the motion vector `mvLX` are set equal to 0: + - `directZeroPredictionFlag` is equal to 1, + - `refIdxLX` is less than 0, + - `refIdxLX` is equal to 0 and `colZeroFlag` is equal to 1. +- Otherwise, the process specified in clause 8.4.1.3 is invoked with `mbPartIdx = 0`, `subMbPartIdx = 0`, `refIdxLX`, and `currSubMbType` as inputs and the output is assigned to `mvLX`. + +NOTE 3 – The motion vector `mvLX` returned from clause 8.4.1.3 is identical for all 4x4 sub-macroblock partitions of a macroblock for which the process is invoked. + +The prediction utilization flags `predFlagL0` and `predFlagL1` are derived as specified using Table 8-9. + +**Table 8-9 – Assignment of prediction utilization flags** + +| refIdxL0 | refIdxL1 | predFlagL0 | predFlagL1 | +|-----------------------|-----------------------|-------------------------|-------------------------| +| $\geq 0$ | $\geq 0$ | 1 | 1 | +| $\geq 0$ | $< 0$ | 1 | 0 | +| $< 0$ | $\geq 0$ | 0 | 1 | + +The variable `subMvCnt` is derived as follows: + +- If `subMbPartIdx` is not equal to 0, `subMvCnt` is set equal to 0. +- Otherwise (`subMbPartIdx` is equal to 0), `subMvCnt` is set equal to `predFlagL0 + predFlagL1`. + +#### 8.4.1.2.3 Derivation process for temporal direct luma motion vector and reference index prediction mode + +This process is invoked when `direct_spatial_mv_pred_flag` is equal to 0 and any of the following conditions are true: + +- `mb_type` is equal to `B_Skip`, +- `mb_type` is equal to `B_Direct_16x16`, +- `sub_mb_type[ mbPartIdx ]` is equal to `B_Direct_8x8`. + +Inputs to this process are `mbPartIdx` and `subMbPartIdx`. + +Outputs of this process are the motion vectors `mvL0` and `mvL1`, the reference indices `refIdxL0` and `refIdxL1`, and the prediction list utilization flags, `predFlagL0` and `predFlagL1`. + +The process specified in clause 8.4.1.2.1 is invoked with `mbPartIdx`, `subMbPartIdx` given as input and the output is assigned to `colPic`, `mbAddrCol`, `mvCol`, `refIdxCol`, and `vertMvScale`. + +The reference indices `refIdxL0` and `refIdxL1` are derived as + +$$\text{refIdxL0} = ( ( \text{refIdxCol} < 0 ) ? 0 : \text{MapColToList0}( \text{refIdxCol} ) ) \quad (8-191)$$ + +$$\text{refIdxL1} = 0 \quad (8-192)$$ + +NOTE 1 – If the current macroblock is a field macroblock, `refIdxL0` and `refIdxL1` index a list of fields; otherwise (the current macroblock is a frame macroblock), `refIdxL0` and `refIdxL1` index a list of frames or complementary reference field pairs. + +Let `refPicCol` be a frame, a field, or a complementary field pair that was referred by the reference index `refIdxCol` when decoding the co-located macroblock `mbAddrCol` inside the picture `colPic`. The function `MapColToList0( refIdxCol )` is specified as follows: + +- If `vertMvScale` is equal to `One_To_One`, the following applies: + - If `field_pic_flag` is equal to 0 and the current macroblock is a field macroblock, the following applies: + - Let `refIdxL0Frm` be the lowest valued reference index in the current reference picture list `RefPicList0` that references the frame or complementary field pair that contains the field `refPicCol`. `RefPicList0` shall contain a frame or complementary field pair that contains the field `refPicCol`. The return value of `MapColToList0( )` is specified as follows: + - If the field referred to by `refIdxCol` has the same parity as the current macroblock, `MapColToList0( refIdxCol )` returns the reference index ( `refIdxL0Frm << 1` ). + - Otherwise (the field referred by `refIdxCol` has the opposite parity of the current macroblock), `MapColToList0( refIdxCol )` returns the reference index ( ( `refIdxL0Frm << 1` ) + 1 ). + - Otherwise (`field_pic_flag` is equal to 1 or the current macroblock is a frame macroblock), `MapColToList0( refIdxCol )` returns the lowest valued reference index `refIdxL0` in the current reference picture list `RefPicList0` that references `refPicCol`. `RefPicList0` shall contain `refPicCol`. +- Otherwise, if `vertMvScale` is equal to `Frm_To_Fld`, the following applies: + - If `field_pic_flag` is equal to 0, let `refIdxL0Frm` be the lowest valued reference index in the current reference picture list `RefPicList0` that references `refPicCol`. `MapColToList0( refIdxCol )` returns the reference index ( `refIdxL0Frm << 1` ). `RefPicList0` shall contain `refPicCol`. + - Otherwise (`field_pic_flag` is equal to 1), `MapColToList0( refIdxCol )` returns the lowest valued reference index `refIdxL0` in the current reference picture list `RefPicList0` that references the field of `refPicCol` with the same parity as the current picture `CurrPic`. `RefPicList0` shall contain the field of `refPicCol` with the same parity as the current picture `CurrPic`. +- Otherwise (`vertMvScale` is equal to `Fld_To_Frm`), `MapColToList0( refIdxCol )` returns the lowest valued reference index `refIdxL0` in the current reference picture list `RefPicList0` that references the frame or complementary field pair that contains `refPicCol`. `RefPicList0` shall contain a frame or complementary field pair that contains the field `refPicCol`. + +NOTE 2 – A decoded reference picture that was marked as "used for short-term reference" when it was referenced in the decoding process of the picture containing the co-located macroblock may have been modified to be marked as "used for long-term reference" before being used for reference for inter prediction using the direct prediction mode for the current macroblock. + +Depending on the value of `vertMvScale` the vertical component of `mvCol` is modified as follows: + +- If `vertMvScale` is equal to `Frm_To_Fld` + +$$mvCol[ 1 ] = mvCol[ 1 ] / 2 \quad (8-193)$$ + +- Otherwise, if `vertMvScale` is equal to `Fld_To_Frm` + +$$mvCol[ 1 ] = mvCol[ 1 ] * 2 \quad (8-194)$$ + +- Otherwise (`vertMvScale` is equal to `One_To_One`), `mvCol[ 1 ]` remains unchanged. + +The variables `currPicOrField`, `pic0`, and `pic1`, are derived as follows: + +- If `field_pic_flag` is equal to 0 and the current macroblock is a field macroblock, the following applies: + 1. `currPicOrField` is the field of the current picture `CurrPic` that has the same parity as the current macroblock. + 2. `pic1` is the field of `RefPicList1[ 0 ]` that has the same parity as the current macroblock. + 3. The variable `pic0` is derived as follows: + - If `refIdxL0 % 2` is equal to 0, `pic0` is the field of `RefPicList0[ refIdxL0 / 2 ]` that has the same parity as the current macroblock. + - Otherwise (`refIdxL0 % 2` is not equal to 0), `pic0` is the field of `RefPicList0[ refIdxL0 / 2 ]` that has the opposite parity of the current macroblock. +- Otherwise (`field_pic_flag` is equal to 1 or the current macroblock is a frame macroblock), `currPicOrField` is the current picture `CurrPic`, `pic1` is the decoded reference picture `RefPicList1[ 0 ]`, and `pic0` is the decoded reference picture `RefPicList0[ refIdxL0 ]`. + +The two motion vectors `mvL0` and `mvL1` for each 4x4 sub-macroblock partition of the current macroblock are derived as follows: + +NOTE 3 – It is often the case that many of the 4x4 sub-macroblock partitions share the same motion vectors and reference pictures. In these cases, temporal direct mode motion compensation can calculate the inter prediction sample values in larger units than 4x4 luma sample blocks. For example, when `direct_8x8_inference_flag` is equal to 1, at least each 8x8 luma sample quadrant of the macroblock shares the same motion vectors and reference pictures. + +- If the reference index `refIdxL0` refers to a long-term reference picture, or `DiffPicOrderCnt( pic1, pic0 )` is equal to 0, the motion vectors `mvL0`, `mvL1` for the direct mode partition are derived by: + +$$mvL0 = mvCol \quad (8-195)$$ + +$$mvL1 = 0 \quad (8-196)$$ + +- Otherwise, the motion vectors `mvL0`, `mvL1` are derived as scaled versions of the motion vector `mvCol` of the co-located sub-macroblock partition as specified below (see Figure 8-2). + +$$tx = ( 16384 + Abs( td / 2 ) ) / td \quad (8-197)$$ + +$$DistScaleFactor = Clip3( -1024, 1023, ( tb * tx + 32 ) >> 6 ) \quad (8-198)$$ + +$$mvL0 = ( DistScaleFactor * mvCol + 128 ) >> 8 \quad (8-199)$$ + +$$mvL1 = mvL0 - mvCol \quad (8-200)$$ + +where `tb` and `td` are derived as: + +$$tb = Clip3( -128, 127, DiffPicOrderCnt( currPicOrField, pic0 ) ) \quad (8-201)$$ + +$$td = Clip3( -128, 127, DiffPicOrderCnt( pic1, pic0 ) ) \quad (8-202)$$ + +NOTE 4 – `mvL0` and `mvL1` cannot exceed the ranges specified in Annex A. + +The prediction utilization flags `predFlagL0` and `predFlagL1` are both set equal to 1. + +Figure 8-2 illustrates the temporal direct-mode motion vector inference when the current picture is temporally between the reference picture from reference picture list 0 and the reference picture from reference picture list 1. + +![Figure 8-2: Example for temporal direct-mode motion vector inference (informative). The diagram shows a timeline with three vertical lines: 'List 0 reference', 'Current B', and 'List 1 reference'. A 'Direct-mode B partition' is shown as a rectangle between 'List 0 reference' and 'Current B'. A 'Co-located partition' is shown as a rectangle between 'Current B' and 'List 1 reference'. Motion vectors are indicated by arrows: 'mvCol' from 'List 0 reference' to 'Co-located partition', 'mvL0' from 'List 0 reference' to 'Direct-mode B partition', and 'mvL1' from 'Co-located partition' to 'Direct-mode B partition'. Time intervals 'td' and 'tb' are marked between 'List 0 reference' and 'Current B'. The horizontal axis is labeled 'Time' and the diagram is identified as 'H.264(09)_F8-2'.](29aa6165ccf449dee0b4335676fa7b1a_img.jpg) + +Figure 8-2: Example for temporal direct-mode motion vector inference (informative). The diagram shows a timeline with three vertical lines: 'List 0 reference', 'Current B', and 'List 1 reference'. A 'Direct-mode B partition' is shown as a rectangle between 'List 0 reference' and 'Current B'. A 'Co-located partition' is shown as a rectangle between 'Current B' and 'List 1 reference'. Motion vectors are indicated by arrows: 'mvCol' from 'List 0 reference' to 'Co-located partition', 'mvL0' from 'List 0 reference' to 'Direct-mode B partition', and 'mvL1' from 'Co-located partition' to 'Direct-mode B partition'. Time intervals 'td' and 'tb' are marked between 'List 0 reference' and 'Current B'. The horizontal axis is labeled 'Time' and the diagram is identified as 'H.264(09)\_F8-2'. + +**Figure 8-2 – Example for temporal direct-mode motion vector inference (informative)** + +#### 8.4.1.3 Derivation process for luma motion vector prediction + +Inputs to this process are: + +- the macroblock partition index $mbPartIdx$ , +- the sub-macroblock partition index $subMbPartIdx$ , +- the reference index of the current partition $refIdxLX$ (with $X$ being 0 or 1), +- the variable $currSubMbType$ . + +Output of this process is the prediction $mvpLX$ of the motion vector $mvLX$ (with $X$ being 0 or 1). + +The derivation process for the neighbouring blocks for motion data in clause 8.4.1.3.2 is invoked with $mbPartIdx$ , $subMbPartIdx$ , $currSubMbType$ , and $listSuffixFlag = X$ (with $X$ being 0 or 1 for $refIdxLX$ being $refIdxL0$ or $refIdxL1$ , respectively) as the input and with $mbAddrN\mbPartIdxN\subMbPartIdxN$ , reference indices $refIdxLXN$ and the motion vectors $mvLXN$ with $N$ being replaced by A, B, or C as the output. + +The motion vector predictor $mvpLX$ is derived as follows: + +- If $MbPartWidth( mb\_type )$ is equal to 16, $MbPartHeight( mb\_type )$ is equal to 8, $mbPartIdx$ is equal to 0, and $refIdxLXB$ is equal to $refIdxLX$ , the motion vector predictor $mvpLX$ is derived by: + +$$mvpLX = mvLXB \tag{8-203}$$ + +- Otherwise, if $MbPartWidth( mb\_type )$ is equal to 16, $MbPartHeight( mb\_type )$ is equal to 8, $mbPartIdx$ is equal to 1, and $refIdxLXA$ is equal to $refIdxLX$ , the motion vector predictor $mvpLX$ is derived by: + +$$mvpLX = mvLXA \tag{8-204}$$ + +- Otherwise, if $MbPartWidth( mb\_type )$ is equal to 8, $MbPartHeight( mb\_type )$ is equal to 16, $mbPartIdx$ is equal to 0, and $refIdxLXA$ is equal to $refIdxLX$ , the motion vector predictor $mvpLX$ is derived by: + +$$mvpLX = mvLXA \tag{8-205}$$ + +- Otherwise, if $MbPartWidth( mb\_type )$ is equal to 8, $MbPartHeight( mb\_type )$ is equal to 16, $mbPartIdx$ is equal to 1, and $refIdxLXC$ is equal to $refIdxLX$ , the motion vector predictor $mvpLX$ is derived by: + +$$mvpLX = mvLXC \tag{8-206}$$ + +- Otherwise, the derivation process for median luma motion vector prediction in clause 8.4.1.3.1 is invoked with $mbAddrN\mbPartIdxN\subMbPartIdxN$ , $mvLXN$ , $refIdxLXN$ with $N$ being replaced by A, B, or C, and $refIdxLX$ as the inputs and the output is assigned to the motion vector predictor $mvpLX$ . + +Figure 8-3 illustrates the non-median prediction as specified in Equations 8-203 to 8-206. + +![Figure 8-3: Directional segmentation prediction (informative). The diagram shows two macroblocks. The left macroblock is labeled '8*16' and is divided vertically into two equal parts. An arrow points from the left part to the right part. The right macroblock is labeled '16*8' and is divided horizontally into two equal parts. An arrow points from the top part to the bottom part. Below the right macroblock is the text 'H.264(09)_F8-3'.](3c721884a92b102becb43b52f6110e47_img.jpg) + +Figure 8-3: Directional segmentation prediction (informative). The diagram shows two macroblocks. The left macroblock is labeled '8\*16' and is divided vertically into two equal parts. An arrow points from the left part to the right part. The right macroblock is labeled '16\*8' and is divided horizontally into two equal parts. An arrow points from the top part to the bottom part. Below the right macroblock is the text 'H.264(09)\_F8-3'. + +**Figure 8-3 – Directional segmentation prediction (informative)** + +#### 8.4.1.3.1 Derivation process for median luma motion vector prediction + +Inputs to this process are: + +- the neighbouring partitions $mbAddrN\mbPartIdxN\subMbPartIdxN$ (with N being replaced by A, B, or C), +- the motion vectors $mvLXN$ (with N being replaced by A, B, or C) of the neighbouring partitions, +- the reference indices $refIdxLXN$ (with N being replaced by A, B, or C) of the neighbouring partitions, +- the reference index $refIdxLX$ of the current partition. + +Output of this process is the motion vector prediction $mvpLX$ . + +The variable $mvpLX$ is derived as specified by the following ordered steps: + +1. When both partitions $mbAddrB\mbPartIdxB\subMbPartIdxB$ and $mbAddrC\mbPartIdxC\subMbPartIdxC$ are not available and $mbAddrA\mbPartIdxA\subMbPartIdxA$ is available, + +$$mvLXB = mvLXA \tag{8-207}$$ + +$$mvLXC = mvLXA \tag{8-208}$$ + +$$refIdxLXB = refIdxLXA \tag{8-209}$$ + +$$refIdxLXC = refIdxLXA \tag{8-210}$$ + +2. Depending on reference indices $refIdxLXA$ , $refIdxLXB$ , or $refIdxLXC$ , the following applies: + +- If one and only one of the reference indices $refIdxLXA$ , $refIdxLXB$ , or $refIdxLXC$ is equal to the reference index $refIdxLX$ of the current partition, the following applies. Let $refIdxLXN$ be the reference index that is equal to $refIdxLX$ , the motion vector $mvLXN$ is assigned to the motion vector prediction $mvpLX$ : + +$$mvpLX = mvLXN \tag{8-211}$$ + +- Otherwise, each component of the motion vector prediction $mvpLX$ is given by the median of the corresponding vector components of the motion vector $mvLXA$ , $mvLXB$ , and $mvLXC$ : + +$$mvpLX[ 0 ] = \text{Median}( mvLXA[ 0 ], mvLXB[ 0 ], mvLXC[ 0 ] ) \tag{8-212}$$ + +$$mvpLX[ 1 ] = \text{Median}( mvLXA[ 1 ], mvLXB[ 1 ], mvLXC[ 1 ] ) \tag{8-213}$$ + +#### 8.4.1.3.2 Derivation process for motion data of neighbouring partitions + +Inputs to this process are: + +- the macroblock partition index $mbPartIdx$ , +- the sub-macroblock partition index $subMbPartIdx$ , +- the current sub-macroblock type $currSubMbType$ , +- the list suffix flag $listSuffixFlag$ . + +Outputs of this process are (with N being replaced by A, B, or C) + +- $mbAddrN\mbPartIdxN\subMbPartIdxN$ specifying neighbouring partitions, + +- the motion vectors $mvLXN$ of the neighbouring partitions, +- the reference indices $refIdxLXN$ of the neighbouring partitions. + +Variable names that include the string "LX" are interpreted with the X being equal to listSuffixFlag. + +The partitions $mbAddrN\mbPartIdxN\subMbPartIdxN$ with N being either A, B, or C are derived in the following ordered steps: + +1. Let $mbAddrD\mbPartIdxD\subMbPartIdxD$ be variables specifying an additional neighbouring partition. +2. The process in clause 6.4.11.7 is invoked with $mbPartIdx$ , $currSubMbType$ , and $subMbPartIdx$ as input and the output is assigned to $mbAddrN\mbPartIdxN\subMbPartIdxN$ with N being replaced by A, B, C, or D. +3. When the partition $mbAddrC\mbPartIdxC\subMbPartIdxC$ is not available, the following applies: + +$$mbAddrC = mbAddrD \tag{8-214}$$ + +$$mbPartIdxC = mbPartIdxD \tag{8-215}$$ + +$$subMbPartIdxC = subMbPartIdxD \tag{8-216}$$ + +The motion vectors $mvLXN$ and reference indices $refIdxLXN$ (with N being A, B, or C) are derived as follows: + +- If the macroblock partition or sub-macroblock partition $mbAddrN\mbPartIdxN\subMbPartIdxN$ is not available or $mbAddrN$ is coded in an Intra macroblock prediction mode or $predFlagLX$ of $mbAddrN\mbPartIdxN\subMbPartIdxN$ is equal to 0, both components of $mvLXN$ are set equal to 0 and $refIdxLXN$ is set equal to $-1$ . +- Otherwise, the following ordered steps are specified: + +1. The motion vector $mvLXN$ and reference index $refIdxLXN$ are set equal to $MvLX[ mbPartIdxN ][ subMbPartIdxN ]$ and $RefIdxLX[ mbPartIdxN ]$ , respectively, which are the motion vector $mvLX$ and reference index $refIdxLX$ that have been assigned to the (sub-)macroblock partition $mbAddrN\mbPartIdxN\subMbPartIdxN$ . +2. The variables $mvLXN[ 1 ]$ and $refIdxLXN$ are further processed as follows: + +- If the current macroblock is a field macroblock and the macroblock $mbAddrN$ is a frame macroblock + +$$mvLXN[ 1 ] = mvLXN[ 1 ] / 2 \tag{8-217}$$ + +$$refIdxLXN = refIdxLXN * 2 \tag{8-218}$$ + +- Otherwise, if the current macroblock is a frame macroblock and the macroblock $mbAddrN$ is a field macroblock + +$$mvLXN[ 1 ] = mvLXN[ 1 ] * 2 \tag{8-219}$$ + +$$refIdxLXN = refIdxLXN / 2 \tag{8-220}$$ + +- Otherwise, the vertical motion vector component $mvLXN[ 1 ]$ and the reference index $refIdxLXN$ remain unchanged. + +#### 8.4.1.4 Derivation process for chroma motion vectors + +This process is only invoked when $ChromaArrayType$ is not equal to 0. + +Inputs to this process are a luma motion vector $mvLX$ and a reference index $refIdxLX$ . + +Output of this process is a chroma motion vector $mvCLX$ . + +A chroma motion vector is derived from the corresponding luma motion vector. + +The precision of the chroma motion vector components is $1 \div ( 4 * SubWidthC )$ horizontally and $1 \div ( 4 * SubHeightC )$ vertically. + +NOTE – For example, when using the 4:2:0 chroma format, since the units of luma motion vectors are one-quarter luma sample units and chroma has half horizontal and vertical resolution compared to luma, the units of chroma motion vectors are one-eighth chroma sample units, i.e., a value of 1 for the chroma motion vector refers to a one-eighth chroma sample displacement. For example, when the luma vector applies to 8x16 luma samples, the corresponding chroma vector in 4:2:0 chroma format applies + +to 4x8 chroma samples and when the luma vector applies to 4x4 luma samples, the corresponding chroma vector in 4:2:0 chroma format applies to 2x2 chroma samples. + +For the derivation of the motion vector mvCLX, the following applies: + +- If ChromaArrayType is not equal to 1 or the current macroblock is a frame macroblock, the horizontal and vertical components of the chroma motion vector mvCLX are derived as: + +$$\text{mvCLX}[ 0 ] = \text{mvLX}[ 0 ] \quad (8-221)$$ + +$$\text{mvCLX}[ 1 ] = \text{mvLX}[ 1 ] \quad (8-222)$$ + +- Otherwise (ChromaArrayType is equal to 1 and the current macroblock is a field macroblock), only the horizontal component of the chroma motion vector mvCLX[ 0 ] is derived using Equation 8-221. The vertical component of the chroma motion vector mvCLX[ 1 ] is dependent on the parity of the current field or the current macroblock and the reference picture, which is referred by the reference index refIdxLX. mvCLX[ 1 ] is derived from mvLX[ 1 ] according to Table 8-10. + +**Table 8-10 – Derivation of the vertical component of the chroma vector in field coding mode** + +| Parity conditions | | mvCLX[ 1 ] | +|------------------------------|------------------------------------|---------------| +| Reference picture (refIdxLX) | Current field (picture/macroblock) | | +| Top field | Bottom field | mvLX[ 1 ] + 2 | +| Bottom field | Top field | mvLX[ 1 ] – 2 | +| Otherwise | | mvLX[ 1 ] | + +#### 8.4.2 Decoding process for Inter prediction samples + +Inputs to this process are: + +- a macroblock partition mbPartIdx, +- a sub-macroblock partition subMbPartIdx, +- variables specifying partition width and height for luma and chroma (if available), partWidth, partHeight, partWidthC (if available) and partHeightC (if available), +- luma motion vectors mvL0 and mvL1 and when ChromaArrayType is not equal to 0 chroma motion vectors mvCL0 and mvCL1, +- reference indices refIdxL0 and refIdxL1, +- prediction list utilization flags, predFlagL0 and predFlagL1, +- variables for weighted prediction logWDC, w0C, w1C, o0C, o1C with C being replaced by L and, when ChromaArrayType is not equal to 0, Cb and Cr. + +Outputs of this process are the Inter prediction samples predPart, which are a (partWidth)x(partHeight) array predPartL of prediction luma samples, and when ChromaArrayType is not equal to 0 two (partWidthC)x(partHeightC) arrays predPartCb, predPartCr of prediction chroma samples, one for each of the chroma components Cb and Cr. + +Let predPartL0L and predPartL1L be (partWidth)x(partHeight) arrays of predicted luma sample values and when ChromaArrayType is not equal to 0 predPartL0Cb, predPartL1Cb, predPartL0Cr, and predPartL1Cr be (partWidthC)x(partHeightC) arrays of predicted chroma sample values. + +For LX being replaced by either L0 or L1 in the variables predFlagLX, RefPicListX, refIdxLX, refPicLX, predPartLX, the following is specified. + +When predFlagLX is equal to 1, the following applies: + +- The reference picture consisting of an ordered two-dimensional array refPicLXL of luma samples and when ChromaArrayType is not equal to 0 two ordered two-dimensional arrays refPicLXCb and refPicLXCr of chroma samples is derived by invoking the process specified in clause 8.4.2.1 with refIdxLX and RefPicListX given as input. + +- The array $\text{predPartLX}_L$ and when $\text{ChromaArrayType}$ is not equal to 0 the arrays $\text{predPartLX}_{Cb}$ and $\text{predPartLX}_{Cr}$ are derived by invoking the process specified in clause 8.4.2.2 with the current partition specified by $\text{mbPartIdx}\backslash\text{subMbPartIdx}$ , the motion vectors $\text{mvLX}$ , $\text{mvCLX}$ (if available), and the reference arrays with $\text{refPicLX}_L$ , $\text{refPicLX}_{Cb}$ (if available), and $\text{refPicLX}_{Cr}$ (if available) given as input. + +For C being replaced by L, Cb (if available), or Cr (if available), the array $\text{predPart}_C$ of the prediction samples of component C is derived by invoking the process specified in clause 8.4.2.3 with the current partition specified by $\text{mbPartIdx}$ and $\text{subMbPartIdx}$ , the prediction utilization flags $\text{predFlagL0}$ and $\text{predFlagL1}$ , the arrays $\text{predPartL0}_C$ and $\text{predPartL1}_C$ , and the variables for weighted prediction $\text{logWD}_C$ , $w_{0C}$ , $w_{1C}$ , $o_{0C}$ , $o_{1C}$ given as input. + +#### 8.4.2.1 Reference picture selection process + +Input to this process is a reference index $\text{refIdxLX}$ . + +Output of this process is a reference picture consisting of a two-dimensional array of luma samples $\text{refPicLX}_L$ and, when $\text{ChromaArrayType}$ is not equal to 0, two two-dimensional arrays of chroma samples $\text{refPicLX}_{Cb}$ and $\text{refPicLX}_{Cr}$ . + +Depending on $\text{field\_pic\_flag}$ , the reference picture list $\text{RefPicListX}$ (which has been derived as specified in clause 8.2.4) consists of the following. + +- If $\text{field\_pic\_flag}$ is equal to 1, each entry of $\text{RefPicListX}$ is a reference field or a field of a reference frame. +- Otherwise ( $\text{field\_pic\_flag}$ is equal to 0), each entry of $\text{RefPicListX}$ is a reference frame or a complementary reference field pair. + +For the derivation of the reference picture, the following applies: + +- If $\text{field\_pic\_flag}$ is equal to 1, the reference field or field of a reference frame $\text{RefPicListX}[\text{refIdxLX}]$ is the output. The output reference field or field of a reference frame consists of a $(\text{PicWidthInSamples}_L) \times (\text{PicHeightInSamples}_L)$ array of luma samples $\text{refPicLX}_L$ and, when $\text{ChromaArrayType}$ is not equal to 0, two $(\text{PicWidthInSamples}_C) \times (\text{PicHeightInSamples}_C)$ arrays of chroma samples $\text{refPicLX}_{Cb}$ and $\text{refPicLX}_{Cr}$ . +- Otherwise ( $\text{field\_pic\_flag}$ is equal to 0), the following applies: + - If the current macroblock is a frame macroblock, the reference frame or complementary reference field pair $\text{RefPicListX}[\text{refIdxLX}]$ is the output. The output reference frame or complementary reference field pair consists of a $(\text{PicWidthInSamples}_L) \times (\text{PicHeightInSamples}_L)$ array of luma samples $\text{refPicLX}_L$ and, when $\text{ChromaArrayType}$ is not equal to 0, two $(\text{PicWidthInSamples}_C) \times (\text{PicHeightInSamples}_C)$ arrays of chroma samples $\text{refPicLX}_{Cb}$ and $\text{refPicLX}_{Cr}$ . + - Otherwise (the current macroblock is a field macroblock), the following ordered steps are specified: + 1. Let $\text{refFrame}$ be the reference frame or complementary reference field pair $\text{RefPicListX}[\text{refIdxLX} / 2]$ . + 2. The field of $\text{refFrame}$ is selected as follows: + - If $\text{refIdxLX} \% 2$ is equal to 0, the field of $\text{refFrame}$ that has the same parity as the current macroblock is the output. + - Otherwise ( $\text{refIdxLX} \% 2$ is equal to 1), the field of $\text{refFrame}$ that has the opposite parity as the current macroblock is the output. + 3. The output reference field or field of a reference frame consists of a $(\text{PicWidthInSamples}_L) \times (\text{PicHeightInSamples}_L / 2)$ array of luma samples $\text{refPicLX}_L$ and, when $\text{ChromaArrayType}$ is not equal to 0, two $(\text{PicWidthInSamples}_C) \times (\text{PicHeightInSamples}_C / 2)$ arrays of chroma samples $\text{refPicLX}_{Cb}$ and $\text{refPicLX}_{Cr}$ . + +Depending on $\text{separate\_colour\_plane\_flag}$ , the following applies: + +- If $\text{separate\_colour\_plane\_flag}$ is equal to 0, the reference picture sample arrays $\text{refPicLX}_L$ , $\text{refPicLX}_{Cb}$ (if available), and $\text{refPicLX}_{Cr}$ (if available) correspond to decoded sample arrays $S_L$ , $S_{Cb}$ (if available), $S_{Cr}$ (if available) derived in clause 8.7 for a previously-decoded reference field or reference frame or complementary reference field pair or field of a reference frame. +- Otherwise ( $\text{separate\_colour\_plane\_flag}$ is equal to 1), the following applies: + - If $\text{colour\_plane\_id}$ is equal to 0, the reference picture sample array $\text{refPicLX}_L$ corresponds to the decoded sample array $S_L$ derived in clause 8.7 for a previously-decoded reference field or reference frame or complementary reference field pair or field of a reference frame. + +- Otherwise, if *colour\_plane\_id* is equal to 1, the reference picture sample array *refPicLXL* corresponds to the decoded sample array *SCb* derived in clause 8.7 for a previously-decoded reference field or reference frame or complementary reference field pair or field of a reference frame. +- Otherwise (*colour\_plane\_id* is equal to 2), the reference picture sample array *refPicLXL* corresponds to the decoded sample array *SCr* derived in clause 8.7 for a previously-decoded reference field or reference frame or complementary reference field pair or field of a reference frame. + +#### 8.4.2.2 Fractional sample interpolation process + +Inputs to this process are: + +- the current partition given by its partition index *mbPartIdx* and its sub-macroblock partition index *subMbPartIdx*, +- the width and height *partWidth*, *partHeight* of this partition in luma-sample units, +- a luma motion vector *mvLX* given in quarter-luma-sample units, +- when *ChromaArrayType* is not equal to 0, a chroma motion vector *mvCLX* with a precision of one-(4\**SubWidthC*)-th chroma-sample units horizontally and one-(4\**SubHeightC*)-th chroma-sample units vertically, +- the selected reference picture sample arrays *refPicLXL*, and when *ChromaArrayType* is not equal to 0, *refPicLXCb*, and *refPicLXCr*. + +Outputs of this process are: + +- a (*partWidth*)x(*partHeight*) array *predPartLXL* of prediction luma sample values, +- when *ChromaArrayType* is not equal to 0, two (*partWidthC*)x(*partHeightC*) arrays *predPartLXCb*, and *predPartLXCr* of prediction chroma sample values. + +Let (*xAL*, *yAL*) be the location given in full-sample units of the upper-left luma sample of the current partition given by *mbPartIdx*\subMbPartIdx relative to the upper-left luma sample location of the given two-dimensional array of luma samples. + +Let (*xIntL*, *yIntL*) be a luma location given in full-sample units and (*xFracL*, *yFracL*) be an offset given in quarter-sample units. These variables are used only inside this clause for specifying general fractional-sample locations inside the reference sample arrays *refPicLXL*, *refPicLXCb* (if available), and *refPicLXCr* (if available). + +For each luma sample location (0 ≤ *xL* < *partWidth*, 0 ≤ *yL* < *partHeight*) inside the prediction luma sample array *predPartLXL*, the corresponding prediction luma sample value *predPartLXL[ xL, yL ]* is derived as specified by the following ordered steps: + +1. The variables *xIntL*, *yIntL*, *xFracL*, and *yFracL* are derived by: + +$$xInt_L = xA_L + ( mvLX[ 0 ] \gg 2 ) + x_L \quad (8-223)$$ + +$$yInt_L = yA_L + ( mvLX[ 1 ] \gg 2 ) + y_L \quad (8-224)$$ + +$$xFrac_L = mvLX[ 0 ] \& 3 \quad (8-225)$$ + +$$yFrac_L = mvLX[ 1 ] \& 3 \quad (8-226)$$ + +2. The prediction luma sample value *predPartLXL[ xL, yL ]* is derived by invoking the process specified in clause 8.4.2.2.1 with (*xIntL*, *yIntL*), (*xFracL*, *yFracL*) and *refPicLXL* given as input. + +When *ChromaArrayType* is not equal to 0, the following applies. + +Let (*xIntC*, *yIntC*) be a chroma location given in full-sample units and (*xFracC*, *yFracC*) be an offset given in one-(4\**SubWidthC*)-th chroma-sample units horizontally and one-(4\**SubHeightC*)-th chroma-sample units vertically. These variables are used only inside this clause for specifying general fractional-sample locations inside the reference sample arrays *refPicLXCb*, and *refPicLXCr*. + +For each chroma sample location (0 ≤ *xC* < *partWidthC*, 0 ≤ *yC* < *partHeightC*) inside the prediction chroma sample arrays *predPartLXCb* and *predPartLXCr*, the corresponding prediction chroma sample values *predPartLXCb[ xC, yC ]* and *predPartLXCr[ xC, yC ]* are derived as specified by the following ordered steps: + +1. Depending on *ChromaArrayType*, the variables *xIntC*, *yIntC*, *xFracC*, and *yFracC* are derived as follows: + +- If *ChromaArrayType* is equal to 1, + +$$xInt_C = ( xA_L / SubWidthC ) + ( mvCLX[ 0 ] \gg 3 ) + x_C \quad (8-227)$$ + +$$yInt_C = ( yA_L / SubHeightC ) + ( mvCLX[ 1 ] \gg 3 ) + y_C \quad (8-228)$$ + +$$xFrac_C = mvCLX[ 0 ] \& 7 \quad (8-229)$$ + +$$yFrac_C = mvCLX[ 1 ] \& 7 \quad (8-230)$$ + +- Otherwise, if ChromaArrayType is equal to 2, + +$$xInt_C = ( x_{A_L} / SubWidth_C ) + ( mvCLX[ 0 ] \gg 3 ) + x_C \quad (8-231)$$ + +$$yInt_C = ( y_{A_L} / SubHeight_C ) + ( mvCLX[ 1 ] \gg 2 ) + y_C \quad (8-232)$$ + +$$xFrac_C = mvCLX[ 0 ] \& 7 \quad (8-233)$$ + +$$yFrac_C = ( mvCLX[ 1 ] \& 3 ) \ll 1 \quad (8-234)$$ + +- Otherwise (ChromaArrayType is equal to 3), + +$$xInt_C = x_{A_L} + ( mvLX[ 0 ] \gg 2 ) + x_C \quad (8-235)$$ + +$$yInt_C = y_{A_L} + ( mvLX[ 1 ] \gg 2 ) + y_C \quad (8-236)$$ + +$$xFrac_C = ( mvCX[ 0 ] \& 3 ) \quad (8-237)$$ + +$$yFrac_C = ( mvCX[ 1 ] \& 3 ) \quad (8-238)$$ + +- 2. Depending on ChromaArrayType, the following applies: + +- If ChromaArrayType is not equal to 3, the following applies: + - The prediction sample value $predPartLX_{Cb}[ x_C, y_C ]$ is derived by invoking the process specified in clause 8.4.2.2.2 with $( xInt_C, yInt_C )$ , $( xFrac_C, yFrac_C )$ and $refPicLX_{Cb}$ given as input. + - The prediction sample value $predPartLX_{Cr}[ x_C, y_C ]$ is derived by invoking the process specified in clause 8.4.2.2.2 with $( xInt_C, yInt_C )$ , $( xFrac_C, yFrac_C )$ and $refPicLX_{Cr}$ given as input. +- Otherwise (ChromaArrayType is equal to 3), the following applies: + - The prediction sample value $predPartLX_{Cb}[ x_C, y_C ]$ is derived by invoking the process specified in clause 8.4.2.2.1 with $( xInt_C, yInt_C )$ , $( xFrac_C, yFrac_C )$ and $refPicLX_{Cb}$ given as input. + - The prediction sample value $predPartLX_{Cr}[ x_C, y_C ]$ is derived by invoking the process specified in clause 8.4.2.2.1 with $( xInt_C, yInt_C )$ , $( xFrac_C, yFrac_C )$ and $refPicLX_{Cr}$ given as input. + +#### 8.4.2.2.1 Luma sample interpolation process + +Inputs to this process are: + +- a luma location in full-sample units $( xInt_L, yInt_L )$ , +- a luma location offset in fractional-sample units $( xFrac_L, yFrac_L )$ , +- the luma sample array of the selected reference picture $refPicLX_L$ . + +Output of this process is a predicted luma sample value $predPartLX_L[ x_L, y_L ]$ . + +![Figure 8-4: Integer samples (shaded blocks with upper-case letters) and fractional sample positions (un-shaded blocks with lower-case letters) for quarter sample luma interpolation. The diagram shows a grid of blocks. Shaded blocks (integer samples) are labeled with upper-case letters: A, B, C, D, E, F, G, H, I, J, K, L, M, N, P, Q, R, S, T, U. Un-shaded blocks (fractional positions) are labeled with lower-case letters: aa, bb, cc, dd, ee, ff, gg, hh, a, b, c, d, e, f, g, h, i, j, k, m, n, p, q, r, s. The blocks are arranged in a 2D array with some blocks missing or empty (represented by gray squares).](bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg) + +Figure 8-4: Integer samples (shaded blocks with upper-case letters) and fractional sample positions (un-shaded blocks with lower-case letters) for quarter sample luma interpolation. The diagram shows a grid of blocks. Shaded blocks (integer samples) are labeled with upper-case letters: A, B, C, D, E, F, G, H, I, J, K, L, M, N, P, Q, R, S, T, U. Un-shaded blocks (fractional positions) are labeled with lower-case letters: aa, bb, cc, dd, ee, ff, gg, hh, a, b, c, d, e, f, g, h, i, j, k, m, n, p, q, r, s. The blocks are arranged in a 2D array with some blocks missing or empty (represented by gray squares). + +**Figure 8-4 – Integer samples (shaded blocks with upper-case letters) and fractional sample positions (un-shaded blocks with lower-case letters) for quarter sample luma interpolation** + +The variable $refPicHeightEffective_L$ , which is the height of the effective reference picture luma array, is derived as follows: + +- If $MbaffFrameFlag$ is equal to 0 or $mb\_field\_decoding\_flag$ is equal to 0, $refPicHeightEffective_L$ is set equal to $PicHeightInSamples_L$ . +- Otherwise ( $MbaffFrameFlag$ is equal to 1 and $mb\_field\_decoding\_flag$ is equal to 1), $refPicHeightEffective_L$ is set equal to $PicHeightInSamples_L / 2$ . + +In Figure 8-4, the positions labelled with upper-case letters within shaded blocks represent luma samples at full-sample locations inside the given two-dimensional array $refPicLX_L$ of luma samples. These samples may be used for generating the predicted luma sample value $predPartLX_L[ x_L, y_L ]$ . The locations $( xZ_L, yZ_L )$ for each of the corresponding luma samples Z, where Z may be A, B, C, D, E, F, G, H, I, J, K, L, M, N, P, Q, R, S, T, or U, inside the given array $refPicLX_L$ of luma samples are derived as: + +$$xZ_L = Clip3( 0, PicWidthInSamples_L - 1, xInt_L + xDZ_L ) \quad (8-239)$$ + +$$yZ_L = Clip3( 0, refPicHeightEffective_L - 1, yInt_L + yDZ_L ) \quad (8-240)$$ + +Table 8-11 specifies $( xDZ_L, yDZ_L )$ for different replacements of Z. + +**Table 8-11 – Differential full-sample luma locations** + +| Z | A | B | C | D | E | F | G | H | I | J | K | L | M | N | P | Q | R | S | T | U | +|---------|----|----|----|----|----|----|---|---|---|---|----|----|---|---|---|---|---|---|---|---| +| $xDZ_L$ | 0 | 1 | 0 | 1 | -2 | -1 | 0 | 1 | 2 | 3 | -2 | -1 | 0 | 1 | 2 | 3 | 0 | 1 | 0 | 1 | +| $yDZ_L$ | -2 | -2 | -1 | -1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 3 | 3 | + +Given the luma samples 'A' to 'U' at full-sample locations $( xA_L, yA_L )$ to $( xU_L, yU_L )$ , the luma samples 'a' to 's' at fractional sample positions are derived by the following rules. The luma prediction values at half sample positions are derived by applying a 6-tap filter with tap values $( 1, -5, 20, 20, -5, 1 )$ . The luma prediction values at quarter sample + +positions are derived by averaging samples at full and half sample positions. The process for each fractional position is described below. + +- The samples at half sample positions labelled b are derived by first calculating intermediate values denoted as $b_1$ by applying the 6-tap filter to the nearest integer position samples in the horizontal direction. The samples at half sample positions labelled h are derived by first calculating intermediate values denoted as $h_1$ by applying the 6-tap filter to the nearest integer position samples in the vertical direction: + +$$b_1 = ( E - 5 * F + 20 * G + 20 * H - 5 * I + J ) \quad (8-241)$$ + +$$h_1 = ( A - 5 * C + 20 * G + 20 * M - 5 * R + T ) \quad (8-242)$$ + +The final prediction values b and h are derived using + +$$b = \text{Clip1Y}(( b_1 + 16 ) \gg 5 ) \quad (8-243)$$ + +$$h = \text{Clip1Y}(( h_1 + 16 ) \gg 5 ) \quad (8-244)$$ + +- The samples at half sample position labelled as j are derived by first calculating intermediate value denoted as $j_1$ by applying the 6-tap filter to the intermediate values of the closest half sample positions in either the horizontal or vertical direction because these yield an equal result: + +$$j_1 = cc - 5 * dd + 20 * h_1 + 20 * m_1 - 5 * ee + ff, \text{ or} \quad (8-245)$$ + +$$j_1 = aa - 5 * bb + 20 * b_1 + 20 * s_1 - 5 * gg + hh \quad (8-246)$$ + +where intermediate values denoted as aa, bb, gg, $s_1$ and hh are derived by applying the 6-tap filter horizontally in the same manner as the derivation of $b_1$ and intermediate values denoted as cc, dd, ee, $m_1$ and ff are derived by applying the 6-tap filter vertically in the same manner as the derivation of $h_1$ . The final prediction value j are derived using + +$$j = \text{Clip1Y}(( j_1 + 512 ) \gg 10 ) \quad (8-247)$$ + +- The final prediction values s and m are derived from $s_1$ and $m_1$ in the same manner as the derivation of b and h, as given by + +$$s = \text{Clip1Y}(( s_1 + 16 ) \gg 5 ) \quad (8-248)$$ + +$$m = \text{Clip1Y}(( m_1 + 16 ) \gg 5 ) \quad (8-249)$$ + +- The samples at quarter sample positions labelled as a, c, d, n, f, i, k, and q are derived by averaging with upward rounding of the two nearest samples at integer and half sample positions using + +$$a = ( G + b + 1 ) \gg 1 \quad (8-250)$$ + +$$c = ( H + b + 1 ) \gg 1 \quad (8-251)$$ + +$$d = ( G + h + 1 ) \gg 1 \quad (8-252)$$ + +$$n = ( M + h + 1 ) \gg 1 \quad (8-253)$$ + +$$f = ( b + j + 1 ) \gg 1 \quad (8-254)$$ + +$$i = ( h + j + 1 ) \gg 1 \quad (8-255)$$ + +$$k = ( j + m + 1 ) \gg 1 \quad (8-256)$$ + +$$q = ( j + s + 1 ) \gg 1 \quad (8-257)$$ + +- The samples at quarter sample positions labelled as e, g, p, and r are derived by averaging with upward rounding of the two nearest samples at half sample positions in the diagonal direction using + +$$e = ( b + h + 1 ) \gg 1 \quad (8-258)$$ + +$$g = ( b + m + 1 ) \gg 1 \quad (8-259)$$ + +$$p = ( h + s + 1 ) \gg 1 \quad (8-260)$$ + +$$r = ( m + s + 1 ) \gg 1 \quad (8-261)$$ + +The luma location offset in fractional-sample units ( $xFrac_L, yFrac_L$ ) specifies which of the generated luma samples at full-sample and fractional-sample locations is assigned to the predicted luma sample value $\text{predPartLX}_L[x_L, y_L]$ . This assignment is done according to Table 8-12. The value of $\text{predPartLX}_L[x_L, y_L]$ is the output. + +**Table 8-12 – Assignment of the luma prediction sample predPartLXL[ xL, yL ]** + +| | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| xFrac L | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 3 | +| yFrac L | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | +| predPartLX L [ x L , y L ] | G | d | h | n | a | e | i | p | b | f | j | q | c | g | k | r | + +**8.4.2.2.2 Chroma sample interpolation process** + +This process is only invoked when ChromaArrayType is equal to 1 or 2. + +Inputs to this process are: + +- a chroma location in full-sample units ( xIntC, yIntC ), +- a chroma location offset in fractional-sample units ( xFracC, yFracC ), +- chroma component samples from the selected reference picture refPicLXC. + +Output of this process is a predicted chroma sample value predPartLXC[ xC, yC ]. + +In Figure 8-5, the positions labelled with A, B, C, and D represent chroma samples at full-sample locations inside the given two-dimensional array refPicLXC of chroma samples. + +![Diagram showing a square with vertices A (top-left), B (top-right), C (bottom-left), and D (bottom-right). A point inside the square represents the fractional sample position. Horizontal distances from the left edge are labeled xFrac_C and 8-xFrac_C. Vertical distances from the top and bottom edges are labeled yFrac_C and 8-yFrac_C. The diagram is labeled H.264(09)_F8-5.](03703ee0fb20f67f19e3eb7c97a4b1e4_img.jpg) + +Diagram showing a square with vertices A (top-left), B (top-right), C (bottom-left), and D (bottom-right). A point inside the square represents the fractional sample position. Horizontal distances from the left edge are labeled xFrac\_C and 8-xFrac\_C. Vertical distances from the top and bottom edges are labeled yFrac\_C and 8-yFrac\_C. The diagram is labeled H.264(09)\_F8-5. + +**Figure 8-5 – Fractional sample position dependent variables in chroma interpolation and surrounding integer position samples A, B, C, and D** + +The variable refPicHeightEffectiveC, which is the height of the effective reference picture chroma array, is derived as follows: + +- If MbaffFrameFlag is equal to 0 or mb\_field\_decoding\_flag is equal to 0, refPicHeightEffectiveC is set equal to PicHeightInSamplesC. +- Otherwise (MbaffFrameFlag is equal to 1 and mb\_field\_decoding\_flag is equal to 1), refPicHeightEffectiveC is set equal to PicHeightInSamplesC / 2. + +The sample coordinates specified in Equations 8-262 through 8-269 are used for generating the predicted chroma sample value predPartLXC[ xC, yC ]. + +$$xA_C = \text{Clip3}( 0, \text{PicWidthInSamples}_C - 1, xInt_C ) \tag{8-262}$$ + +$$xB_C = \text{Clip3}( 0, \text{PicWidthInSamples}_C - 1, xInt_C + 1 ) \tag{8-263}$$ + +$$xC_C = \text{Clip3}( 0, \text{PicWidthInSamples}_C - 1, xInt_C ) \tag{8-264}$$ + +$$xD_C = \text{Clip3}( 0, \text{PicWidthInSamples}_C - 1, xInt_C + 1 ) \tag{8-265}$$ + +$$yA_C = \text{Clip3}( 0, \text{refPicHeightEffective}_C - 1, yInt_C ) \tag{8-266}$$ + +$$yB_C = \text{Clip3}( 0, \text{refPicHeightEffective}_C - 1, yInt_C ) \tag{8-267}$$ + +$$yC_C = \text{Clip3}( 0, \text{refPicHeightEffective}_C - 1, yInt_C + 1 ) \tag{8-268}$$ + +$$yD_C = \text{Clip3}( 0, \text{refPicHeightEffective}_C - 1, yInt_C + 1 ) \tag{8-269}$$ + +Given the chroma samples A, B, C, and D at full-sample locations specified in Equations 8-262 through 8-269, the predicted chroma sample value $\text{predPartLX}_C[x_C, y_C]$ is derived as: + +$$\text{predPartLX}_C[x_C, y_C] = \left( \begin{array}{c} (8 - x\text{Frac}_C) * (8 - y\text{Frac}_C) * A + x\text{Frac}_C * (8 - y\text{Frac}_C) * B + \\ (8 - x\text{Frac}_C) * y\text{Frac}_C * C + x\text{Frac}_C * y\text{Frac}_C * D \end{array} + 32 \right) \gg 6 \quad (8-270)$$ + +#### 8.4.2.3 Weighted sample prediction process + +Inputs to this process are: + +- $\text{mbPartIdx}$ : the current partition given by the partition index, +- $\text{subMbPartIdx}$ : the sub-macroblock partition index, +- $\text{predFlagL0}$ and $\text{predFlagL1}$ : prediction list utilization flags, +- $\text{predPartLX}_L$ : a $(\text{partWidth}) \times (\text{partHeight})$ array of prediction luma samples (with LX being replaced by L0 or L1 depending on $\text{predFlagL0}$ and $\text{predFlagL1}$ ), +- when $\text{ChromaArrayType}$ is not equal to 0, $\text{predPartLX}_{Cb}$ and $\text{predPartLX}_{Cr}$ : $(\text{partWidthC}) \times (\text{partHeightC})$ arrays of prediction chroma samples, one for each of the chroma components Cb and Cr (with LX being replaced by L0 or L1 depending on $\text{predFlagL0}$ and $\text{predFlagL1}$ ), +- variables for weighted prediction $\text{logWD}_C$ , $w_{0C}$ , $w_{1C}$ , $o_{0C}$ , $o_{1C}$ with C being replaced by L and, when $\text{ChromaArrayType}$ is not equal to 0, Cb and Cr. + +Outputs of this process are: + +- $\text{predPart}_L$ : a $(\text{partWidth}) \times (\text{partHeight})$ array of prediction luma samples, +- when $\text{ChromaArrayType}$ is not equal to 0, $\text{predPart}_{Cb}$ and $\text{predPart}_{Cr}$ : $(\text{partWidthC}) \times (\text{partHeightC})$ arrays of prediction chroma samples, one for each of the chroma components Cb and Cr. + +For macroblocks or partitions with $\text{predFlagL0}$ equal to 1 in P and SP slices, the following applies: + +- If $\text{weighted\_pred\_flag}$ is equal to 0, the default weighted sample prediction process as described in clause 8.4.2.3.1 is invoked with the same inputs and outputs as the process described in this clause. +- Otherwise ( $\text{weighted\_pred\_flag}$ is equal to 1), the explicit weighted sample prediction process as described in clause 8.4.2.3.2 is invoked with the same inputs and outputs as the process described in this clause. + +For macroblocks or partitions with $\text{predFlagL0}$ or $\text{predFlagL1}$ equal to 1 in B slices, the following applies: + +- If $\text{weighted\_bipred\_idc}$ is equal to 0, the default weighted sample prediction process as described in clause 8.4.2.3.1 is invoked with the same inputs and outputs as the process described in this clause. +- Otherwise, if $\text{weighted\_bipred\_idc}$ is equal to 1, the explicit weighted sample prediction process as described in clause 8.4.2.3.2 is invoked with the same inputs and outputs as the process described in this clause. +- Otherwise ( $\text{weighted\_bipred\_idc}$ is equal to 2), the following applies: + - If $\text{predFlagL0}$ is equal to 1 and $\text{predFlagL1}$ is equal to 1, the implicit weighted sample prediction process as described in clause 8.4.2.3.2 is invoked with the same inputs and outputs as the process described in this clause. + - Otherwise ( $\text{predFlagL0}$ or $\text{predFlagL1}$ are equal to 1 but not both), the default weighted sample prediction process as described in clause 8.4.2.3.1 is invoked with the same inputs and outputs as the process described in this clause. + +##### 8.4.2.3.1 Default weighted sample prediction process + +Input to this process are the same as specified in clause 8.4.2.3. + +Output of this process are the same as specified in clause 8.4.2.3. + +Depending on the available component for which the prediction block is derived, the following applies: + +- If the luma sample prediction values $\text{predPart}_L[x, y]$ are derived, the following applies with C set equal to L, x set equal to $0..partWidth - 1$ , and y set equal to $0..partHeight - 1$ . +- Otherwise, if the chroma Cb component sample prediction values $\text{predPart}_{Cb}[x, y]$ are derived, the following applies with C set equal to Cb, x set equal to $0..partWidthC - 1$ , and y set equal to $0..partHeightC - 1$ . + +- Otherwise (the chroma Cr component sample prediction values $\text{predPart}_c[ x, y ]$ are derived), the following applies with C set equal to Cr, x set equal to $0..partWidthC - 1$ , and y set equal to $0..partHeightC - 1$ . + +The prediction sample values are derived as follows: + +- If $\text{predFlagL0}$ is equal to 1 and $\text{predFlagL1}$ is equal to 0, + +$$\text{predPart}_c[ x, y ] = \text{predPartL0}_c[ x, y ] \quad (8-271)$$ + +- Otherwise, if $\text{predFlagL0}$ is equal to 0 and $\text{predFlagL1}$ is equal to 1, + +$$\text{predPart}_c[ x, y ] = \text{predPartL1}_c[ x, y ] \quad (8-272)$$ + +- Otherwise ( $\text{predFlagL0}$ and $\text{predFlagL1}$ are equal to 1), + +$$\text{predPart}_c[ x, y ] = ( \text{predPartL0}_c[ x, y ] + \text{predPartL1}_c[ x, y ] + 1 ) \gg 1. \quad (8-273)$$ + +#### 8.4.2.3.2 Weighted sample prediction process + +Inputs to this process are the same as specified in clause 8.4.2.3. + +Outputs of this process are the same as specified in clause 8.4.2.3. + +Depending on the available component for which the prediction block is derived, the following applies: + +- If the luma sample prediction values $\text{predPart}_L[ x, y ]$ are derived, the following applies with C set equal to L, x set equal to $0..partWidth - 1$ , y set equal to $0..partHeight - 1$ , and $\text{Clip1}()$ being substituted with $\text{Clip1}_Y()$ . +- Otherwise, if the chroma Cb component sample prediction values $\text{predPart}_{Cb}[ x, y ]$ are derived, the following applies with C set equal to Cb, x set equal to $0..partWidthC - 1$ , y set equal to $0..partHeightC - 1$ , and $\text{Clip1}()$ being substituted with $\text{Clip1}_C()$ . +- Otherwise (the chroma Cr component sample prediction values $\text{predPart}_c[ x, y ]$ are derived), the following applies with C set equal to Cr, x set equal to $0..partWidthC - 1$ , y set equal to $0..partHeightC - 1$ , and $\text{Clip1}()$ being substituted with $\text{Clip1}_C()$ . + +The prediction sample values are derived as follows: + +- If the $\text{predFlagL0}$ is equal to 1 and $\text{predFlagL1}$ is equal to 0, the final predicted sample values $\text{predPart}_c[ x, y ]$ are derived by + +$$\begin{aligned} & \text{if} ( \log WD_C \geq 1 ) \\ & \quad \text{predPart}_c[ x, y ] = \text{Clip1} ( ( ( \text{predPartL0}_c[ x, y ] * w_{0C} + 2^{\log WD_C - 1} ) \gg \log WD_C ) + o_{0C} ) \\ & \text{else} \\ & \quad \text{predPart}_c[ x, y ] = \text{Clip1} ( \text{predPartL0}_c[ x, y ] * w_{0C} + o_{0C} ) \end{aligned} \quad (8-274)$$ + +- Otherwise, if the $\text{predFlagL0}$ is equal to 0 and $\text{predFlagL1}$ is equal to 1, the final predicted sample values $\text{predPart}_c[ x, y ]$ are derived by + +$$\begin{aligned} & \text{if} ( \log WD_C \geq 1 ) \\ & \quad \text{predPart}_c[ x, y ] = \text{Clip1} ( ( ( \text{predPartL1}_c[ x, y ] * w_{1C} + 2^{\log WD_C - 1} ) \gg \log WD_C ) + o_{1C} ) \\ & \text{else} \\ & \quad \text{predPart}_c[ x, y ] = \text{Clip1} ( \text{predPartL1}_c[ x, y ] * w_{1C} + o_{1C} ) \end{aligned} \quad (8-275)$$ + +- Otherwise (both $\text{predFlagL0}$ and $\text{predFlagL1}$ are equal to 1), the final predicted sample values $\text{predPart}_c[ x, y ]$ are derived by + +$$\text{predPart}_c[ x, y ] = \text{Clip1} ( ( ( \text{predPartL0}_c[ x, y ] * w_{0C} + \text{predPartL1}_c[ x, y ] * w_{1C} + 2^{\log WD_C} ) \gg ( \log WD_C + 1 ) ) + ( ( o_{0C} + o_{1C} + 1 ) \gg 1 ) ) \quad (8-276)$$ + +#### 8.4.3 Derivation process for prediction weights + +Inputs to this process are: + +- the reference indices $\text{refIdxL0}$ and $\text{refIdxL1}$ , +- the prediction utilization flags $\text{predFlagL0}$ and $\text{predFlagL1}$ . + +Outputs of this process are variables for weighted prediction $\log WD_C$ , $w_{0C}$ , $w_{1C}$ , $o_{0C}$ , $o_{1C}$ with C being replaced by L and, when ChromaArrayType is not equal to 0, Cb and Cr. + +The variables implicitModeFlag and explicitModeFlag are derived as follows: + +- If weighted\_bipred\_idc is equal to 2, (slice\_type % 5) is equal to 1, predFlagL0 is equal to 1, and predFlagL1 is equal to 1, implicitModeFlag is set equal to 1 and explicitModeFlag is set equal to 0. +- Otherwise, if weighted\_bipred\_idc is equal to 1, (slice\_type % 5) is equal to 1, and predFlagL0 + predFlagL1 is equal to 1 or 2, implicitModeFlag is set equal to 0 and explicitModeFlag is set equal to 1. +- Otherwise, if weighted\_pred\_flag is equal to 1, (slice\_type % 5) is equal to 0 or 3, and predFlagL0 is equal to 1, implicitModeFlag is set equal to 0 and explicitModeFlag is set equal to 1. +- Otherwise, implicitModeFlag is set equal to 0 and explicitModeFlag is set equal to 0. + +For C being replaced by L and, when ChromaArrayType is not equal to 0, Cb and Cr, the variables $\log WD_C$ , $w_{0C}$ , $w_{1C}$ , $o_{0C}$ , $o_{1C}$ are derived as follows: + +- If implicitModeFlag is equal to 1, implicit mode weighted prediction is used as follows: + +$$\log WD_C = 5 \tag{8-277}$$ + +$$o_{0C} = 0 \tag{8-278}$$ + +$$o_{1C} = 0 \tag{8-279}$$ + +and $w_{0C}$ and $w_{1C}$ are derived as specified in the following ordered steps: + +1. The variables currPicOrField, pic0, and pic1 are derived as follows: + +- If field\_pic\_flag is equal to 0 and the current macroblock is a field macroblock, the following applies: + - a. currPicOrField is the field of the current picture CurrPic that has the same parity as the current macroblock. + - b. The variable pic0 is derived as follows: + - If refIdxL0 % 2 is equal to 0, pic0 is the field of RefPicList0[ refIdxL0 / 2 ] that has the same parity as the current macroblock. + - Otherwise (refIdxL0 % 2 is not equal to 0), pic0 is the field of RefPicList0[ refIdxL0 / 2 ] that has the opposite parity of the current macroblock. + - c. The variable pic1 is derived as follows: + - If refIdxL1 % 2 is equal to 0, pic1 is the field of RefPicList1[ refIdxL1 / 2 ] that has the same parity as the current macroblock. + - Otherwise (refIdxL1 % 2 is not equal to 0), pic1 is the field of RefPicList1[ refIdxL1 / 2 ] that has the opposite parity of the current macroblock. +- Otherwise (field\_pic\_flag is equal to 1 or the current macroblock is a frame macroblock), currPicOrField is the current picture CurrPic, pic1 is RefPicList1[ refIdxL1 ], and pic0 is RefPicList0[ refIdxL0 ]. + +2. The variables $w_{0C}$ and $w_{1C}$ are derived as follows: + +- If DiffPicOrderCnt( pic1, pic0 ) is equal to 0 or one or both of pic1 and pic0 is marked as "used for long-term reference" or $( \text{DistScaleFactor} \gg 2 ) < -64$ or $( \text{DistScaleFactor} \gg 2 ) > 128$ , $w_{0C}$ and $w_{1C}$ are derived as: + +$$w_{0C} = 32 \tag{8-280}$$ + +$$w_{1C} = 32 \tag{8-281}$$ + +- Otherwise, the variables tb, td, tx, and DistScaleFactor are derived from the values of currPicOrField, pic0, and pic1 using Equations 8-201, 8-202, 8-197, and 8-198, respectively, and the weights $w_{0C}$ and $w_{1C}$ are derived as + +$$w_{0C} = 64 - (\text{DistScaleFactor} \gg 2) \tag{8-282}$$ + +$$w_{1C} = \text{DistScaleFactor} \gg 2 \tag{8-283}$$ + +- Otherwise, if explicitModeFlag is equal to 1, explicit mode weighted prediction is used as specified by the following ordered steps: + +1. The variables refIdxL0WP and refIdxL1WP are derived as follows: + +- If MbuffFrameFlag is equal to 1 and the current macroblock is a field macroblock + +$$\text{refIdxL0WP} = \text{refIdxL0} \gg 1 \quad (8-284)$$ + +$$\text{refIdxL1WP} = \text{refIdxL1} \gg 1 \quad (8-285)$$ + +- Otherwise (MbuffFrameFlag is equal to 0 or the current macroblock is a frame macroblock), + +$$\text{refIdxL0WP} = \text{refIdxL0} \quad (8-286)$$ + +$$\text{refIdxL1WP} = \text{refIdxL1} \quad (8-287)$$ + +2. The variables logWDC, w0C, w1C, o0C, and o1C are derived as follows: + +- If C is equal to L for luma samples + +$$\text{logWDC} = \text{luma\_log2\_weight\_denom} \quad (8-288)$$ + +$$\text{w}_{0C} = \text{luma\_weight\_l0}[\text{refIdxL0WP}] \quad (8-289)$$ + +$$\text{w}_{1C} = \text{luma\_weight\_l1}[\text{refIdxL1WP}] \quad (8-290)$$ + +$$\text{o}_{0C} = \text{luma\_offset\_l0}[\text{refIdxL0WP}] * (1 \ll (\text{BitDepth}_Y - 8)) \quad (8-291)$$ + +$$\text{o}_{1C} = \text{luma\_offset\_l1}[\text{refIdxL1WP}] * (1 \ll (\text{BitDepth}_Y - 8)) \quad (8-292)$$ + +- Otherwise (C is equal to Cb or Cr for chroma samples, with iCbCr = 0 for Cb, iCbCr = 1 for Cr), + +$$\text{logWDC} = \text{chroma\_log2\_weight\_denom} \quad (8-293)$$ + +$$\text{w}_{0C} = \text{chroma\_weight\_l0}[\text{refIdxL0WP}][\text{iCbCr}] \quad (8-294)$$ + +$$\text{w}_{1C} = \text{chroma\_weight\_l1}[\text{refIdxL1WP}][\text{iCbCr}] \quad (8-295)$$ + +$$\text{o}_{0C} = \text{chroma\_offset\_l0}[\text{refIdxL0WP}][\text{iCbCr}] * (1 \ll (\text{BitDepth}_C - 8)) \quad (8-296)$$ + +$$\text{o}_{1C} = \text{chroma\_offset\_l1}[\text{refIdxL1WP}][\text{iCbCr}] * (1 \ll (\text{BitDepth}_C - 8)) \quad (8-297)$$ + +- Otherwise (implicitModeFlag is equal to 0 and explicitModeFlag is equal to 0), the variables logWDC, w0C, w1C, o0C, o1C are not used in the reconstruction process for the current macroblock. + +When explicitModeFlag is equal to 1 and predFlagL0 and predFlagL1 are equal to 1, the following constraint shall be obeyed for C equal to L and, when ChromaArrayType is not equal to 0, Cb and Cr: + +$$-128 \leq \text{w}_{0C} + \text{w}_{1C} \leq ((\text{logWDC} == 7) ? 127 : 128) \quad (8-298)$$ + +NOTE – For implicitModeFlag equal to 1, weights w0C and w1C are each guaranteed to be in the range of –64..128 and the constraint expressed in Equation 8-298, although not explicitly imposed, will always be met. For explicitModeFlag equal to 1 with logWDC equal to 7, when one of the two weights w0C or w1C is inferred to be equal to 128 (as a consequence of luma\_weight\_l0\_flag, luma\_weight\_l1\_flag, chroma\_weight\_l0\_flag, or chroma\_weight\_l1\_flag equal to 0), the other weight (w1C or w0C) must have a negative value in order for the constraint expressed in Equation 8-298 to hold (and therefore the other flag luma\_weight\_l0\_flag, luma\_weight\_l1\_flag, chroma\_weight\_l0\_flag, or chroma\_weight\_l1\_flag must be equal to 1). + +## 8.5 Transform coefficient decoding process and picture construction process prior to deblocking filter process + +Inputs to this process are Intra16x16DCLevel (if available), Intra16x16ACLevel (if available), CbIntra16x16DCLevel (if available), CbIntra16x16ACLevel (if available), CrIntra16x16DCLevel (if available), CrIntra16x16ACLevel (if available), LumaLevel4x4 (if available), LumaLevel8x8 (if available), ChromaDCLevel (if available), ChromaACLevel (if available), CbLevel4x4 (if available), CrLevel4x4 (if available), CbLevel8x8 (if available), CrLevel8x8 (if available), + +and available Inter or Intra prediction sample arrays for the current macroblock for the applicable components $\text{pred}_L$ , $\text{pred}_{Cb}$ , or $\text{pred}_{Cr}$ . + +NOTE 1 – When decoding a macroblock in Intra\_4x4 (or Intra\_8x8) macroblock prediction mode, the luma component of the macroblock prediction array may not be complete, since for each 4x4 (or 8x8) luma block, the Intra\_4x4 (or Intra\_8x8) prediction process for luma samples as specified in clause 8.3.1 (or 8.3.2) and the process specified in this clause are iterated. When $\text{ChromaArrayType}$ is equal to 3, the Cb and Cr component of the macroblock prediction array may not be complete for the same reason. + +Outputs of this process are the constructed sample arrays prior to the deblocking filter process for the applicable components $S'_L$ , $S'_{Cb}$ , or $S'_{Cr}$ . + +NOTE 2 – When decoding a macroblock in Intra\_4x4 (or Intra\_8x8) macroblock prediction mode, the luma component of the macroblock constructed sample arrays prior to the deblocking filter process may not be complete, since for each 4x4 (or 8x8) luma block, the Intra\_4x4 (or Intra\_8x8) prediction process for luma samples as specified in clause 8.3.1 (or 8.3.2) and the process specified in this clause are iterated. When $\text{ChromaArrayType}$ is equal to 3, the Cb and Cr component of the macroblock constructed sample arrays prior to the deblocking filter process may not be complete for the same reason. + +This clause specifies transform coefficient decoding and picture construction prior to the deblocking filter process. + +When the current macroblock is coded as P\_Skip or B\_Skip, all values of $\text{LumaLevel4x4}$ , $\text{LumaLevel8x8}$ , $\text{CbLevel4x4}$ , $\text{CbLevel8x8}$ , $\text{CrLevel4x4}$ , $\text{CrLevel8x8}$ , $\text{ChromaDCLevel}$ , $\text{ChromaACLevel}$ are set equal to 0 for the current macroblock. + +### 8.5.1 Specification of transform decoding process for 4x4 luma residual blocks + +This specification applies when $\text{transform\_size\_8x8\_flag}$ is equal to 0. + +When the current macroblock prediction mode is not equal to Intra\_16x16, the variable $\text{LumaLevel4x4}$ contains the levels for the luma transform coefficients. For a 4x4 luma block indexed by $\text{luma4x4BlkIdx} = 0..15$ , the following ordered steps are specified: + +1. The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with $\text{LumaLevel4x4}[\text{luma4x4BlkIdx}]$ as the input and the two-dimensional array $c$ as the output. +2. The scaling and transformation process for residual 4x4 blocks as specified in clause 8.5.12 is invoked with $c$ as the input and $r$ as the output. +3. When $\text{TransformBypassModeFlag}$ is equal to 1, the macroblock prediction mode is equal to Intra\_4x4, and $\text{Intra4x4PredMode}[\text{luma4x4BlkIdx}]$ is equal to 0 or 1, the intra residual transform-bypass decoding process as specified in clause 8.5.15 is invoked with $\text{nW}$ set equal to 4, $\text{nH}$ set equal to 4, $\text{horPredFlag}$ set equal to $\text{Intra4x4PredMode}[\text{luma4x4BlkIdx}]$ , and the 4x4 array $r$ as the inputs, and the output is a modified version of the 4x4 array $r$ . +4. The position of the upper-left sample of a 4x4 luma block with index $\text{luma4x4BlkIdx}$ inside the macroblock is derived by invoking the inverse 4x4 luma block scanning process in clause 6.4.3 with $\text{luma4x4BlkIdx}$ as the input and the output being assigned to $(xO, yO)$ . +5. The 4x4 array $u$ with elements $u_{ij}$ for $i, j = 0..3$ is derived as: + +$$u_{ij} = \text{Clip1}_Y(\text{pred}_L[xO + j, yO + i] + r_{ij}) \quad (8-299)$$ + +When $\text{TransformBypassModeFlag}$ is equal to 1, the bitstream shall not contain data that result in a value of $u_{ij}$ as computed by Equation 8-299 that is not equal to $\text{pred}_L[xO + j, yO + i] + r_{ij}$ . + +6. The picture construction process prior to deblocking filter process in clause 8.5.14 is invoked with $u$ and $\text{luma4x4BlkIdx}$ as the inputs. + +### 8.5.2 Specification of transform decoding process for luma samples of Intra\_16x16 macroblock prediction mode + +When the current macroblock prediction mode is equal to Intra\_16x16, the variables $\text{Intra16x16DCLevel}$ and $\text{Intra16x16ACLevel}$ contain the levels for the luma transform coefficients. The transform coefficient decoding proceeds in the following ordered steps: + +1. The 4x4 luma DC transform coefficients of all 4x4 luma blocks of the macroblock are decoded. + - a. The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with $\text{Intra16x16DCLevel}$ as the input and the two-dimensional array $c$ as the output. + - b. The scaling and transformation process for luma DC transform coefficients for Intra\_16x16 macroblock type as specified in clause 8.5.10 is invoked with $\text{BitDepth}_Y$ , $\text{QP}'_Y$ , and $c$ as the input and $\text{dcY}$ as the output. +2. The 16x16 array $\text{rMb}$ is derived by processing the 4x4 luma blocks indexed by $\text{luma4x4BlkIdx} = 0..15$ , and for each 4x4 luma block, the following ordered steps are specified: + +- a. The variable lumaList, which is a list of 16 entries, is derived. The first entry of lumaList is the corresponding value from the array dcY. Figure 8-6 shows the assignment of the indices of the array dcY to the luma4x4BlkIdx. The two numbers in the small squares refer to indices i and j in dcYij, and the numbers in large squares refer to luma4x4BlkIdx. + +| | | | | +|----------|----------|----------|----------| +| 00
0 | 01
1 | 02
4 | 03
5 | +| 10
2 | 11
3 | 12
6 | 13
7 | +| 20
8 | 21
9 | 22
12 | 23
13 | +| 30
10 | 31
11 | 32
14 | 33
15 | + +H.264(09)\_F8-6 + +**Figure 8-6 – Assignment of the indices of dcY to luma4x4BlkIdx** + +The elements in lumaList with index $k = 1..15$ are specified as: + +$$\text{lumaList}[ k ] = \text{Intra16x16ACLevel}[ \text{luma4x4BlkIdx} ][ k - 1 ] \quad (8-300)$$ + +- b. The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with lumaList as the input and the two-dimensional array c as the output. +- c. The scaling and transformation process for residual 4x4 blocks as specified in clause 8.5.12 is invoked with c as the input and r as the output. +- d. The position of the upper-left sample of a 4x4 luma block with index luma4x4BlkIdx inside the macroblock is derived by invoking the inverse 4x4 luma block scanning process in clause 6.4.3 with luma4x4BlkIdx as the input and the output being assigned to ( xO, yO ). +- e. The elements rMb[ x, y ] of the 16x16 array rMb with $x = xO..xO + 3$ and $y = yO..yO + 3$ are derived by + +$$\text{rMb}[ xO + j, yO + i ] = r_{ij} \quad (8-301)$$ + +3. When TransformBypassModeFlag is equal to 1 and Intra16x16PredMode is equal to 0 or 1, the intra residual transform-bypass decoding process as specified in clause 8.5.15 is invoked with nW set equal to 16, nH set equal to 16, horPredFlag set equal to Intra16x16PredMode, and the 16x16 array rMb as the inputs, and the output is a modified version of the 16x16 array rMb. +4. The 16x16 array u with elements $u_{ij}$ for $i, j = 0..15$ is derived as + +$$u_{ij} = \text{Clip1}_Y( \text{pred}_L[ j, i ] + \text{rMb}[ j, i ] ) \quad (8-302)$$ + +When TransformBypassModeFlag is equal to 1, the bitstream shall not contain data that result in a value of $u_{ij}$ as computed by Equation 8-302 that is not equal to $\text{pred}_L[ j, i ] + \text{rMb}[ j, i ]$ . + +5. The picture construction process prior to deblocking filter process in clause 8.5.14 is invoked with u as the input. + +### 8.5.3 Specification of transform decoding process for 8x8 luma residual blocks + +This specification applies when transform\_size\_8x8\_flag is equal to 1. + +The variable LumaLevel8x8[ luma8x8BlkIdx ] with luma8x8BlkIdx = 0..3 contains the levels for the luma transform coefficients for the luma 8x8 block with index luma8x8BlkIdx. + +For an 8x8 luma block indexed by luma8x8BlkIdx = 0..3, the following ordered steps are specified: + +1. The inverse scanning process for 8x8 transform coefficients and scaling lists as specified in clause 8.5.7 is invoked with LumaLevel8x8[ luma8x8BlkIdx ] as the input and the two-dimensional array c as the output. + +2. The scaling and transformation process for residual 8x8 blocks as specified in clause 8.5.13 is invoked with *c* as the input and *r* as the output. +3. When *TransformBypassModeFlag* is equal to 1, the macroblock prediction mode is equal to *Intra\_8x8*, and *Intra8x8PredMode[ luma8x8BlkIdx ]* is equal to 0 or 1, the intra residual transform-bypass decoding process as specified in clause 8.5.15 is invoked with *nW* set equal to 8, *nH* set equal to 8, *horPredFlag* set equal to *Intra8x8PredMode[ luma8x8BlkIdx ]*, and the 8x8 array *r* as the inputs, and the output is a modified version of the 8x8 array *r*. +4. The position of the upper-left sample of an 8x8 luma block with index *luma8x8BlkIdx* inside the macroblock is derived by invoking the inverse 8x8 luma block scanning process in clause 6.4.5 with *luma8x8BlkIdx* as the input and the output being assigned to ( *xO*, *yO* ). +5. The 8x8 array *u* with elements *uij* for *i, j = 0..7* is derived as: + +$$u_{ij} = \text{Clip1}_V( \text{pred}_L[ xO + j, yO + i ] + r_{ij} ) \quad (8-303)$$ + +When *TransformBypassModeFlag* is equal to 1, the bitstream shall not contain data that result in a value of *uij* as computed by Equation 8-303 that is not equal to *predL[ xO + j, yO + i ] + rij*. + +6. The picture construction process prior to deblocking filter process in clause 8.5.14 is invoked with *u* and *luma8x8BlkIdx* as the inputs. + +#### 8.5.4 Specification of transform decoding process for chroma samples + +This process is invoked for each chroma component Cb and Cr separately when *ChromaArrayType* is not equal to 0. + +Depending on *ChromaArrayType*, the following applies: + +- If *ChromaArrayType* is equal to 3, the transform decoding process for chroma samples with *ChromaArrayType* equal to 3 as specified in clause 8.5.5 is invoked. +- Otherwise (*ChromaArrayType* is not equal to 3), the following text specifies the transform decoding process for chroma samples. + +For each chroma component, the variables *ChromaDCLevel[ iCbCr ]* and *ChromaACLevel[ iCbCr ]*, with *iCbCr* set equal to 0 for Cb and *iCbCr* set equal to 1 for Cr, contain the levels for both components of the chroma transform coefficients. + +Let the variable *numChroma4x4Blks* be set equal to ( *MbWidthC* / 4 ) \* ( *MbHeightC* / 4 ). + +For each chroma component, the transform decoding proceeds separately in the following ordered steps: + +1. The *numChroma4x4Blks* chroma DC transform coefficients of the 4x4 chroma blocks of the component indexed by *iCbCr* of the macroblock are decoded as specified in the following ordered steps: + - a. Depending on the variable *ChromaArrayType*, the following applies: + - If *ChromaArrayType* is equal to 1, the 2x2 array *c* is derived using the inverse raster scanning process applied to *ChromaDCLevel* as follows: + +$$c = \begin{bmatrix} \text{ChromaDCLevel}[iCbCr][0] & \text{ChromaDCLevel}[iCbCr][1] \\ \text{ChromaDCLevel}[iCbCr][2] & \text{ChromaDCLevel}[iCbCr][3] \end{bmatrix} \quad (8-304)$$ + +- Otherwise (*ChromaArrayType* is equal to 2), the 2x4 array *c* is derived using the inverse raster scanning process applied to *ChromaDCLevel* as follows: + +$$c = \begin{bmatrix} \text{ChromaDCLevel}[iCbCr][0] & \text{ChromaDCLevel}[iCbCr][2] \\ \text{ChromaDCLevel}[iCbCr][1] & \text{ChromaDCLevel}[iCbCr][5] \\ \text{ChromaDCLevel}[iCbCr][3] & \text{ChromaDCLevel}[iCbCr][6] \\ \text{ChromaDCLevel}[iCbCr][4] & \text{ChromaDCLevel}[iCbCr][7] \end{bmatrix} \quad (8-305)$$ + +- b. The scaling and transformation process for chroma DC transform coefficients as specified in clause 8.5.11 is invoked with *c* as the input and *dcC* as the output. +2. The ( *MbWidthC* ) x ( *MbHeightC* ) array *rMb* is derived by processing the 4x4 chroma blocks indexed by *chroma4x4BlkIdx = 0..numChroma4x4Blks - 1* of the component indexed by *iCbCr*, and for each 4x4 chroma block, the following ordered steps are specified: + +- a. The variable chromaList, which is a list of 16 entries, is derived. The first entry of chromaList is the corresponding value from the array dcC. Figure 8-7 shows the assignment of the indices of the array dcC to the chroma4x4BlkIdx. The two numbers in the small squares refer to indices i and j in dcCij, and the numbers in large squares refer to chroma4x4BlkIdx. + +![Figure 8-7: Assignment of the indices of dcC to chroma4x4BlkIdx. (a) ChromaArrayType equal to 1, (b) ChromaArrayType equal to 2. Diagram (a) shows a 2x2 grid of large squares labeled 0, 1, 2, 3. Each large square contains a small square with two numbers: 00, 01 in 0; 10, 11 in 1; 20, 21 in 2; 30, 31 in 3. Diagram (b) shows a 2x4 grid of large squares labeled 0 through 7. Each large square contains a small square with two numbers: 00, 01 in 0; 10, 11 in 1; 20, 21 in 2; 30, 31 in 3; 40, 41 in 4; 50, 51 in 5; 60, 61 in 6; 70, 71 in 7. A label H.264(09)_F8-7 is present next to diagram (b).](c3ba400c25c28fedce1c7d29414198de_img.jpg) + +Figure 8-7: Assignment of the indices of dcC to chroma4x4BlkIdx. (a) ChromaArrayType equal to 1, (b) ChromaArrayType equal to 2. Diagram (a) shows a 2x2 grid of large squares labeled 0, 1, 2, 3. Each large square contains a small square with two numbers: 00, 01 in 0; 10, 11 in 1; 20, 21 in 2; 30, 31 in 3. Diagram (b) shows a 2x4 grid of large squares labeled 0 through 7. Each large square contains a small square with two numbers: 00, 01 in 0; 10, 11 in 1; 20, 21 in 2; 30, 31 in 3; 40, 41 in 4; 50, 51 in 5; 60, 61 in 6; 70, 71 in 7. A label H.264(09)\_F8-7 is present next to diagram (b). + +**Figure 8-7 – Assignment of the indices of dcC to chroma4x4BlkIdx:** +**(a) ChromaArrayType equal to 1, (b) ChromaArrayType equal to 2** + +The elements in chromaList with index k = 1..15 are specified as: + +$$\text{chromaList}[k] = \text{ChromaACLevel}[\text{chroma4x4BlkIdx}][k - 1] \quad (8-306)$$ + +- b. The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with chromaList as the input and the two-dimensional array c as the output. +- c. The scaling and transformation process for residual 4x4 blocks as specified in clause 8.5.12 is invoked with c as the input and r as the output. +- d. The position of the upper-left sample of a 4x4 chroma block with index chroma4x4BlkIdx inside the current macroblock is derived by invoking the inverse 4x4 chroma block scanning process as specified in clause 6.4.7 with chroma4x4BlkIdx as the input and the output being assigned to ( xO, yO ). +- e. The elements rMb[ x, y ] of the (MbWidthC)x(MbHeightC) array rMb with x = xO..xO + 3 and y = yO..yO + 3 are derived by: + +$$\text{rMb}[xO + j, yO + i] = r_{ij} \quad (8-307)$$ + +3. When TransformBypassModeFlag is equal to 1, the macroblock prediction mode is equal to Intra\_4x4, Intra\_8x8, or Intra\_16x16, and intra\_chroma\_pred\_mode is equal to 1 or 2, the intra residual transform-bypass decoding process as specified in clause 8.5.15 is invoked with nW set equal to MbWidthC, nH set equal to MbHeightC, horPredFlag set equal to (2 - intra\_chroma\_pred\_mode), and the (MbWidthC)x(MbHeightC) array rMb as the inputs, and the output is a modified version of the (MbWidthC)x(MbHeightC) array rMb. +4. The (MbWidthC)x(MbHeightC) array u with elements uij for i = 0..MbHeightC - 1 and j = 0..MbWidthC - 1 is derived as: + +$$u_{ij} = \text{Clip1c}(\text{predc}[j, i] + \text{rMb}[j, i]) \quad (8-308)$$ + +When TransformBypassModeFlag is equal to 1, the bitstream shall not contain data that result in a value of uij as computed by Equation 8-308 that is not equal to predc[ j, i ] + rMb[ j, i ]. + +5. The picture construction process prior to deblocking filter process in clause 8.5.14 is invoked with u as the input. + +### 8.5.5 Specification of transform decoding process for chroma samples with ChromaArrayType equal to 3 + +This process is invoked for each chroma component Cb and Cr separately when ChromaArrayType is equal to 3. + +Depending on the macroblock prediction mode and transform\_size\_8x8\_flag, the following applies: + +- If the macroblock prediction mode is equal to Intra\_16x16, the transform decoding process for Cb or Cr residual blocks shall be identical to the process described in clause 8.5.2 when substituting luma with Cb or Cr, substituting Intra16x16DCLevel with CbIntra16x16DCLevel or CrIntra16x16DCLevel, substituting Intra16x16ACLevel with CbIntra16x16ACLevel or CrIntra16x16ACLevel, and substituting $pred_L$ with $pred_{Cb}$ or $pred_{Cr}$ , substituting luma4x4BlkIdx with cb4x4BlkIdx or cr4x4BlkIdx, substituting lumaList with CbList or CrList, substituting BitDepthY with BitDepthC, substituting $QP'_Y$ with $QP'_C$ , and substituting Clip1Y with Clip1C. During the scaling of 4x4 block transform coefficient levels that is specified in clause 8.5.12.1, which is invoked as part of the process specified in clause 8.5.2, the input 4x4 array c is treated as relating to a luma residual block coded using an Intra\_16x16 macroblock prediction mode. +- Otherwise, if transform\_size\_8x8\_flag is equal to 1, the transform decoding process for 8x8 Cb or 8x8 Cr residual blocks shall be identical to the process described in clause 8.5.3 when substituting luma with Cb or Cr, substituting LumaLevel8x8 with CbLevel8x8 or CrLevel8x8, substituting $pred_L$ with $pred_{Cb}$ or $pred_{Cr}$ , substituting luma8x8BlkIdx with cb8x8BlkIdx or cr8x8BlkIdx, and substituting Clip1Y with Clip1C. +- Otherwise (the macroblock prediction mode is not equal to Intra\_16x16 and transform\_size\_8x8\_flag is equal to 0), the transform decoding process for 4x4 Cb or 4x4 Cr residual blocks shall be identical to the process described in clause 8.5.1 when substituting luma with Cb or Cr, substituting LumaLevel4x4 with CbLevel4x4 or CrLevel4x4, substituting $pred_L$ with $pred_{Cb}$ or $pred_{Cr}$ , substituting luma4x4BlkIdx with cb4x4BlkIdx or cr4x4BlkIdx, and substituting Clip1Y with Clip1C. During the scaling of 4x4 block transform coefficient levels that is specified in clause 8.5.12.1, which is invoked as part of the process specified in clause 8.5.1, the input 4x4 array c is treated as relating to a luma residual block not coded using an Intra\_16x16 macroblock prediction mode. + +### 8.5.6 Inverse scanning process for 4x4 transform coefficients and scaling lists + +Input to this process is a list of 16 values. + +Output of this process is a variable c containing a two-dimensional array of 4x4 values. In the case of transform coefficients, these 4x4 values represent levels assigned to locations in the transform block. In the case of applying the inverse scanning process to a scaling list, the output variable c contains a two-dimensional array representing a 4x4 scaling matrix. + +When this clause is invoked with a list of transform coefficient levels as the input, the sequence of transform coefficient levels is mapped to the transform coefficient level positions. Table 8-13 specifies the two mappings: inverse zig-zag scan and inverse field scan. The inverse zig-zag scan is used for transform coefficients in frame macroblocks and the inverse field scan is used for transform coefficients in field macroblocks. + +When this clause is invoked with a scaling list as the input, the sequence of scaling list entries is mapped to the positions in the corresponding scaling matrix. For this mapping, the inverse zig-zag scan is used. + +Figure 8-8 illustrates the scans. + +![Figure 8-8 shows two diagrams illustrating 4x4 block scans. (a) Zig-zag scan: A 4x4 grid of 16 elements (0-15) is scanned in a zig-zag pattern. The sequence starts at 0, goes to 1, then 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15. (b) Field scan (informative): A 4x4 grid of 16 elements (0-15) is scanned in a field scan pattern. The sequence starts at 0, goes to 1, then 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15. The field scan pattern is: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15.](4f2ed2a6c82bec5477b9e99a4b47e5e5_img.jpg) + +Figure 8-8 shows two diagrams illustrating 4x4 block scans. (a) Zig-zag scan: A 4x4 grid of 16 elements (0-15) is scanned in a zig-zag pattern. The sequence starts at 0, goes to 1, then 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15. (b) Field scan (informative): A 4x4 grid of 16 elements (0-15) is scanned in a field scan pattern. The sequence starts at 0, goes to 1, then 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15. The field scan pattern is: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15. + +Figure 8-8 – 4x4 block scans. (a) Zig-zag scan. (b) Field scan (informative) + +Table 8-13 provides the mapping from the index idx of input list of 16 elements to indices i and j of the two-dimensional array c. + +**Table 8-13 – Specification of mapping of idx to $c_{ij}$ for zig-zag and field scan** + +| idx | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +|----------------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------| +| zig-zag | $c_{00}$ | $c_{01}$ | $c_{10}$ | $c_{20}$ | $c_{11}$ | $c_{02}$ | $c_{03}$ | $c_{12}$ | $c_{21}$ | $c_{30}$ | $c_{31}$ | $c_{22}$ | $c_{13}$ | $c_{23}$ | $c_{32}$ | $c_{33}$ | +| field | $c_{00}$ | $c_{10}$ | $c_{01}$ | $c_{20}$ | $c_{30}$ | $c_{11}$ | $c_{21}$ | $c_{31}$ | $c_{02}$ | $c_{12}$ | $c_{22}$ | $c_{32}$ | $c_{03}$ | $c_{13}$ | $c_{23}$ | $c_{33}$ | + +**8.5.7 Inverse scanning process for 8x8 transform coefficients and scaling lists** + +Input to this process is a list of 64 values. + +Output of this process is a variable $c$ containing a two-dimensional array of 8x8 values. In the case of transform coefficients, these 8x8 values represent levels assigned to locations in the transform block. In the case of applying the inverse scanning process to a scaling list, the output variable $c$ contains a two-dimensional array representing an 8x8 scaling matrix. + +When this clause is invoked with a list of transform coefficient levels as the input, the sequence of transform coefficient levels is mapped to the transform coefficient level positions. Table 8-14 specifies the two mappings: inverse 8x8 zig-zag scan and inverse 8x8 field scan. The inverse 8x8 zig-zag scan is used for transform coefficient levels in frame macroblocks and the inverse 8x8 field scan is used for transform coefficient levels in field macroblocks. + +When this clause is invoked with a scaling list as the input, the sequence of scaling list entries is mapped to the positions in the corresponding scaling matrix. For this mapping, the inverse zig-zag scan is used. + +Figure 8-9 illustrates the scans. + +![Figure 8-9 shows two diagrams of 8x8 block scans. (a) 8x8 zig-zag scan: A grid of 64 elements numbered 0 to 63, with arrows indicating the zig-zag scanning path. (b) 8x8 field scan (informative): A grid of 64 elements numbered 0 to 63, with arrows indicating the field scanning path. The field scan path is more complex, involving vertical and diagonal movements. A small label 'H.264(09)_F8-9' is present near the bottom right of diagram (b).](6afc9bc8eaf6acd589f4f81494c19c5a_img.jpg) + +Figure 8-9 shows two diagrams of 8x8 block scans. (a) 8x8 zig-zag scan: A grid of 64 elements numbered 0 to 63, with arrows indicating the zig-zag scanning path. (b) 8x8 field scan (informative): A grid of 64 elements numbered 0 to 63, with arrows indicating the field scanning path. The field scan path is more complex, involving vertical and diagonal movements. A small label 'H.264(09)\_F8-9' is present near the bottom right of diagram (b). + +**Figure 8-9 – 8x8 block scans. (a) 8x8 zig-zag scan. (b) 8x8 field scan (informative)** + +Table 8-14 provides the mapping from the index $idx$ of the input list of 64 elements to indices $i$ and $j$ of the two-dimensional array $c$ . + +**Table 8-14 – Specification of mapping of idx to cij for 8x8 zig-zag and 8x8 field scan** + +| idx | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +|----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| zig-zag | c 00 | c 01 | c 10 | c 20 | c 11 | c 02 | c 03 | c 12 | c 21 | c 30 | c 40 | c 31 | c 22 | c 13 | c 04 | c 05 | +| field | c 00 | c 10 | c 20 | c 01 | c 11 | c 30 | c 40 | c 21 | c 02 | c 31 | c 50 | c 60 | c 70 | c 41 | c 12 | c 03 | + +**Table 8-14 (continued) – Specification of mapping of idx to cij for 8x8 zig-zag and 8x8 field scan** + +| idx | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | +|----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| zig-zag | c 14 | c 23 | c 32 | c 41 | c 50 | c 60 | c 51 | c 42 | c 33 | c 24 | c 15 | c 06 | c 07 | c 16 | c 25 | c 34 | +| field | c 22 | c 51 | c 61 | c 71 | c 32 | c 13 | c 04 | c 23 | c 42 | c 52 | c 62 | c 72 | c 33 | c 14 | c 05 | c 24 | + +**Table 8-14 (continued) – Specification of mapping of idx to cij for 8x8 zig-zag and 8x8 field scan** + +| idx | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | +|----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| zig-zag | c 43 | c 52 | c 61 | c 70 | c 71 | c 62 | c 53 | c 44 | c 35 | c 26 | c 17 | c 27 | c 36 | c 45 | c 54 | c 63 | +| field | c 43 | c 53 | c 63 | c 73 | c 34 | c 15 | c 06 | c 25 | c 44 | c 54 | c 64 | c 74 | c 35 | c 16 | c 26 | c 45 | + +**Table 8-14 (concluded) – Specification of mapping of idx to cij for 8x8 zig-zag and 8x8 field scan** + +| idx | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | +|----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| zig-zag | c 72 | c 73 | c 64 | c 55 | c 46 | c 37 | c 47 | c 56 | c 65 | c 74 | c 75 | c 66 | c 57 | c 67 | c 76 | c 77 | +| field | c 55 | c 65 | c 75 | c 36 | c 07 | c 17 | c 46 | c 56 | c 66 | c 76 | c 27 | c 37 | c 47 | c 57 | c 67 | c 77 | + +### 8.5.8 Derivation process for chroma quantization parameters + +Outputs of this process are: + +- QPC: the chroma quantization parameter for each chroma component Cb and Cr, +- QSC: the additional chroma quantization parameter for each chroma component Cb and Cr required for decoding SP and SI slices (if applicable). + +NOTE 1 – QP quantization parameter values QPY and QSY are always in the range of –QpBdOffsetY to 51, inclusive. QP quantization parameter values QPC and QSC are always in the range of –QpBdOffsetC to 39, inclusive. + +The value of QPC for a chroma component is determined from the current value of QPY and the value of chroma\_qp\_index\_offset (for Cb) or second\_chroma\_qp\_index\_offset (for Cr). + +NOTE 2 – The scaling equations are specified such that the equivalent transform coefficient level scaling factor doubles for every increment of 6 in QPY. Thus, there is an increase in the factor used for scaling of approximately 12 % for each increase of 1 in the value of QPY. + +The value of QPC for each chroma component is determined as specified in Table 8-15 based on the index denoted as qPI. + +The variable qPOffset for each chroma component is derived as follows: + +- If the chroma component is the Cb component, qPOffset is specified as: + +$$qP_{Offset} = \text{chroma\_qp\_index\_offset} \quad (8-309)$$ + +- Otherwise (the chroma component is the Cr component), qPOffset is specified as: + +$$qP_{Offset} = \text{second\_chroma\_qp\_index\_offset} \quad (8-310)$$ + +The value of qPI for each chroma component is derived as: + +$$qP_I = \text{Clip3}(-\text{QpBdOffset}_C, 51, \text{QP}_Y + qP_{Offset}) \quad (8-311)$$ + +The value of $QP'_C$ for the chroma components is derived as: + +$$QP'_C = QP_C + QpBdOffset_C \quad (8-312)$$ + +**Table 8-15 – Specification of $QP_C$ as a function of $qP_T$** + +| | | | | | | | | | | | | | | | | | | | | | | | | +|--------|----------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| $qP_T$ | <30 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | +| $QP_C$ | $= qP_T$ | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | + +When the current slice is an SP or SI slice, $QS_C$ is derived using the above process, substituting $QP_V$ with $QS_V$ and $QP_C$ with $QS_C$ . + +### 8.5.9 Derivation process for scaling functions + +Outputs of this process are: + +- LevelScale4x4: the scaling factor for 4x4 block transform luma or chroma coefficient levels, +- LevelScale8x8: the scaling factor for 8x8 block transform luma or chroma coefficient levels. + +The variable $mbIsInterFlag$ is derived as follows: + +- If the current macroblock is coded using Inter macroblock prediction modes, $mbIsInterFlag$ is set equal to 1. +- Otherwise (the current macroblock is coded using Intra macroblock prediction modes), $mbIsInterFlag$ is set equal to 0. + +The variable $iYCbCr$ derived as follows: + +- If $separate\_colour\_plane\_flag$ is equal to 1, $iYCbCr$ is set equal to $colour\_plane\_id$ . +- Otherwise ( $separate\_colour\_plane\_flag$ is equal to 0), the following applies: + - If the scaling function $LevelScale4x4$ or $LevelScale8x8$ is derived for a luma residual block, $iYCbCr$ is set equal to 0. + - Otherwise, if the scaling function $LevelScale4x4$ or $LevelScale8x8$ is derived for a chroma residual block and the chroma component is equal to Cb, $iYCbCr$ is set equal to 1. + - Otherwise (the scaling function $LevelScale4x4$ or $LevelScale8x8$ is derived for a chroma residual block and the chroma component is equal to Cr), $iYCbCr$ is set equal to 2. + +The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with $ScalingList4x4[iYCbCr + ( (mbIsInterFlag == 1) ? 3 : 0 )]$ as the input and the output is assigned to the 4x4 matrix $weightScale4x4$ . + +$LevelScale4x4(m, i, j)$ is specified by: + +$$LevelScale4x4(m, i, j) = weightScale4x4(i, j) * normAdjust4x4(m, i, j) \quad (8-313)$$ + +where + +$$normAdjust4x4(m, i, j) = \begin{cases} v_{m0} & \text{for } (i \% 2, j \% 2) \text{ equal to } (0,0), \\ v_{m1} & \text{for } (i \% 2, j \% 2) \text{ equal to } (1,1), \\ v_{m2} & \text{otherwise;} \end{cases} \quad (8-314)$$ + +where the first and second subscripts of $v$ are row and column indices, respectively, of the matrix specified as: + +$$v = \begin{bmatrix} 10 & 16 & 13 \\ 11 & 18 & 14 \\ 13 & 20 & 16 \\ 14 & 23 & 18 \\ 16 & 25 & 20 \\ 18 & 29 & 23 \end{bmatrix}. \quad (8-315)$$ + +The inverse scanning process for 8x8 transform coefficients and scaling lists as specified in clause 8.5.7 is invoked with `ScalingList8x8[ 2 * iYCbCr + mbIsInterFlag ]` as the input and the output is assigned to the 8x8 matrix `weightScale8x8`. + +`LevelScale8x8( m, i, j )` is specified by: + +$$\text{LevelScale8x8}( m, i, j ) = \text{weightScale8x8}( i, j ) * \text{normAdjust8x8}( m, i, j ) \quad (8-316)$$ + +where + +$$\text{normAdjust8x8}( m, i, j ) = \begin{cases} v_{m0} & \text{for } (i \% 4, j \% 4) \text{ equal to } (0,0), \\ v_{m1} & \text{for } (i \% 2, j \% 2) \text{ equal to } (1,1), \\ v_{m2} & \text{for } (i \% 4, j \% 4) \text{ equal to } (2,2), \\ v_{m3} & \text{for } (i \% 4, j \% 2) \text{ equal to } (0,1) \text{ or } (i \% 2, j \% 4) \text{ equal to } (1,0), \\ v_{m4} & \text{for } (i \% 4, j \% 4) \text{ equal to } (0,2) \text{ or } (i \% 4, j \% 4) \text{ equal to } (2,0), \\ v_{m5} & \text{otherwise;} \end{cases} \quad (8-317)$$ + +where the first and second subscripts of `v` are row and column indices, respectively, of the matrix specified as: + +$$v = \begin{bmatrix} 20 & 18 & 32 & 19 & 25 & 24 \\ 22 & 19 & 35 & 21 & 28 & 26 \\ 26 & 23 & 42 & 24 & 33 & 31 \\ 28 & 25 & 45 & 26 & 35 & 33 \\ 32 & 28 & 51 & 30 & 40 & 38 \\ 36 & 32 & 58 & 34 & 46 & 43 \end{bmatrix}. \quad (8-318)$$ + +### 8.5.10 Scaling and transformation process for DC transform coefficients for Intra\_16x16 macroblock type + +Inputs to this process are: + +- the variables `bitDepth` and `qP`, +- transform coefficient level values for DC transform coefficients of Intra\_16x16 macroblocks as a 4x4 array `c` with elements `cij`, where `i` and `j` form a two-dimensional frequency index. + +Outputs of this process are 16 scaled DC values for 4x4 blocks of Intra\_16x16 macroblocks as a 4x4 array `dcY` with elements `dcYij`. + +Depending on the value of `TransformBypassModeFlag`, the following applies: + +- If `TransformBypassModeFlag` is equal to 1, the output `dcY` is derived as: + +$$\text{dcY}_{ij} = c_{ij} \text{ with } i, j = 0..3 \quad (8-319)$$ + +- Otherwise (`TransformBypassModeFlag` is equal to 0), the following text of this process specifies the output. + +The inverse transform for the 4x4 luma DC transform coefficients is specified by: + +$$f = \begin{bmatrix} 1 & 1 & 1 & 1 \\ 1 & 1 & -1 & -1 \\ 1 & -1 & -1 & 1 \\ 1 & -1 & 1 & -1 \end{bmatrix} * \begin{bmatrix} c_{00} & c_{01} & c_{02} & c_{03} \\ c_{10} & c_{11} & c_{12} & c_{13} \\ c_{20} & c_{21} & c_{22} & c_{23} \\ c_{30} & c_{31} & c_{32} & c_{33} \end{bmatrix} * \begin{bmatrix} 1 & 1 & 1 & 1 \\ 1 & 1 & -1 & -1 \\ 1 & -1 & -1 & 1 \\ 1 & -1 & 1 & -1 \end{bmatrix}. \quad (8-320)$$ + +The bitstream shall not contain data that result in any element $f_{ij}$ of $f$ with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +After the inverse transform, the scaling is performed as follows: + +- If $\text{qP}$ is greater than or equal to 36, the scaled result is derived as: + +$$\text{dcY}_{ij} = ( f_{ij} * \text{LevelScale4x4}(\text{qP} \% 6, 0, 0) ) \ll ( \text{qP} / 6 - 6 ), \quad \text{with } i, j = 0..3 \quad (8-321)$$ + +- Otherwise ( $\text{qP}$ is less than 36), the scaled result is derived as: + +$$\text{dcY}_{ij} = ( f_{ij} * \text{LevelScale4x4}(\text{qP} \% 6, 0, 0) + ( 1 \ll ( 5 - \text{qP} / 6 ) ) ) \gg ( 6 - \text{qP} / 6 ), \quad \text{with } i, j = 0..3 \quad (8-322)$$ + +The bitstream shall not contain data that result in any element $\text{dcY}_{ij}$ of $\text{dcY}$ with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +NOTE 1 – When $\text{entropy\_coding\_mode\_flag}$ is equal to 0 and $\text{qP}$ is less than 10 and $\text{profile\_idc}$ is equal to 66, 77, or 88, the range of values that can be represented for the elements $c_{ij}$ of $c$ is not sufficient to represent the full range of values of the elements $\text{dcY}_{ij}$ of $\text{dcY}$ that could be necessary to form a close approximation of the content of any possible source picture by use of the Intra\_16x16 macroblock type. + +NOTE 2 – Since the range limit imposed on the elements $\text{dcY}_{ij}$ of $\text{dcY}$ is imposed after the right shift in Equation 8-322, a larger range of values must be supported in the decoder prior to the right shift. + +### 8.5.11 Scaling and transformation process for chroma DC transform coefficients + +This process is only invoked when $\text{ChromaArrayType}$ is equal to 1 or 2. + +Inputs to this process are transform coefficient level values for chroma DC transform coefficients of one chroma component of the macroblock as an $(\text{MbWidthC} / 4) \times (\text{MbHeightC} / 4)$ array $c$ with elements $c_{ij}$ , where $i$ and $j$ form a two-dimensional frequency index. + +Outputs of this process are the scaled DC values as an $(\text{MbWidthC} / 4) \times (\text{MbHeightC} / 4)$ array $\text{dcC}$ with elements $\text{dcC}_{ij}$ . The variables $\text{bitDepth}$ and $\text{qP}$ are set equal to $\text{BitDepth}_C$ and $\text{QP}'_C$ , respectively. + +Depending on the value of $\text{TransformBypassModeFlag}$ , the following applies: + +- If $\text{TransformBypassModeFlag}$ is equal to 1, the output $\text{dcC}$ is derived as: + +$$\text{dcC}_{ij} = c_{ij} \quad \text{with } i = 0..(\text{MbWidthC} / 4) - 1 \text{ and } j = 0..(\text{MbHeightC} / 4) - 1. \quad (8-323)$$ + +- Otherwise ( $\text{TransformBypassModeFlag}$ is equal to 0), the following ordered steps are specified: + +1. The transformation process for chroma DC transform coefficients as specified in clause 8.5.11.1 is invoked with $\text{bitDepth}$ and $c$ as the inputs and the output is assigned to the $(\text{MbWidthC} / 4) \times (\text{MbHeightC} / 4)$ array $f$ of chroma DC values with elements $f_{ij}$ . +2. The scaling process for chroma DC transform coefficients as specified in clause 8.5.11.2 is invoked with $\text{bitDepth}$ , $\text{qP}$ , and $f$ as the inputs and the output is assigned to the $(\text{MbWidthC} / 4) \times (\text{MbHeightC} / 4)$ array $\text{dcC}$ of scaled chroma DC values with elements $\text{dcC}_{ij}$ . + +#### 8.5.11.1 Transformation process for chroma DC transform coefficients + +Inputs of this process are transform coefficient level values for chroma DC transform coefficients of one chroma component of the macroblock as an $(\text{MbWidthC} / 4) \times (\text{MbHeightC} / 4)$ array $c$ with elements $c_{ij}$ , where $i$ and $j$ form a two-dimensional frequency index. + +Outputs of this process are the DC values as an $(\text{MbWidthC} / 4) \times (\text{MbHeightC} / 4)$ array $f$ with elements $f_{ij}$ . + +Depending on the variable $\text{ChromaArrayType}$ , the inverse transform is specified as follows: + +- If $\text{ChromaArrayType}$ is equal to 1, the inverse transform for the 2x2 chroma DC transform coefficients is specified as: + +$$f = \begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix} * \begin{bmatrix} c_{00} & c_{01} \\ c_{10} & c_{11} \end{bmatrix} * \begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix} \quad (8-324)$$ + +- Otherwise, ( $\text{ChromaArrayType}$ is equal to 2), the inverse transform for the 2x4 chroma DC transform coefficients is specified as: + +$$f = \begin{bmatrix} 1 & 1 & 1 & 1 \\ 1 & 1 & -1 & -1 \\ 1 & -1 & -1 & 1 \\ 1 & -1 & 1 & -1 \end{bmatrix} * \begin{bmatrix} c_{00} & c_{01} \\ c_{10} & c_{11} \\ c_{20} & c_{21} \\ c_{30} & c_{31} \end{bmatrix} * \begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix} \quad (8-325)$$ + +### 8.5.11.2 Scaling process for chroma DC transform coefficients + +Inputs of this process are: + +- the variables bitDepth and qP, +- DC values as an (MbWidthC / 4)x(MbHeightC / 4) array f with elements $f_{ij}$ . + +Outputs of this process are scaled DC values as an (MbWidthC / 4)x(MbHeightC / 4) array dcC with elements $dcC_{ij}$ . + +The bitstream shall not contain data that result in any element $f_{ij}$ of f with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +Scaling is performed depending on the variable ChromaArrayType as follows: + +- If ChromaArrayType is equal to 1, the scaled result is derived as: + +$$dcC_{ij} = ( ( f_{ij} * \text{LevelScale4x4}( \text{qP} \% 6, 0, 0 ) ) \ll ( \text{qP} / 6 ) ) \gg 5, \text{ with } i, j = 0, 1 \quad (8-326)$$ + +- Otherwise (ChromaArrayType is equal to 2), the following ordered steps are specified: + 1. The variable qPDC is derived as: + +$$qP_{DC} = qP + 3 \quad (8-327)$$ + +2. Depending on the value of qPDC, the following applies: + +- If qPDC is greater than or equal to 36, the scaled result is derived as: + +$$dcC_{ij} = ( ( f_{ij} * \text{LevelScale4x4}( \text{qP} \% 6, 0, 0 ) ) \ll ( \text{qP} / 6 ) - 6 ), \text{ with } i = 0..3, j = 0, 1 \quad (8-328)$$ + +- Otherwise (qPDC is less than 36), the scaled result is derived as: + +$$dcC_{ij} = ( ( f_{ij} * \text{LevelScale4x4}( \text{qP}_{DC} \% 6, 0, 0 ) + 2^{5 - \text{qP}_{DC} / 6} ) \gg ( 6 - \text{qP}_{DC} / 6 ), \text{ with } i = 0..3, j = 0, 1 \quad (8-329)$$ + +The bitstream shall not contain data that result in any element $dcC_{ij}$ of dcC with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +NOTE 1 – When entropy\_coding\_mode\_flag is equal to 0 and qP is less than 4 and profile\_idc is equal to 66, 77, or 88, the range of values that can be represented for the elements $c_{ij}$ of c in clause 8.5.11.1 may not be sufficient to represent the full range of values of the elements $dcC_{ij}$ of dcC that could be necessary to form a close approximation of the content of any possible source picture. + +NOTE 2 – Since the range limit imposed on the elements $dcC_{ij}$ of dcC is imposed after the right shift in Equation 8-326 or 8-329, a larger range of values must be supported in the decoder prior to the right shift. + +### 8.5.12 Scaling and transformation process for residual 4x4 blocks + +Input to this process is a 4x4 array c with elements $c_{ij}$ which is either an array relating to a residual block of the luma component or an array relating to a residual block of a chroma component. + +Outputs of this process are residual sample values as 4x4 array r with elements $r_{ij}$ . + +The variable bitDepth is derived as follows: + +- If the input array c relates to a luma residual block, bitDepth is set equal to BitDepthy. +- Otherwise (the input array c relates to a chroma residual block), bitDepth is set equal to BitDepthc. + +The variable sMbFlag is derived as follows: + +- If mb\_type is equal to SI or the macroblock prediction mode is equal to Inter in an SP slice, sMbFlag is set equal to 1, +- Otherwise (mb\_type not equal to SI and the macroblock prediction mode is not equal to Inter in an SP slice), sMbFlag is set equal to 0. + +The variable $qP$ is derived as follows: + +- If the input array $c$ relates to a luma residual block and $sMbFlag$ is equal to 0, + +$$qP = QP'_{\gamma} \quad (8-330)$$ + +- Otherwise, if the input array $c$ relates to a luma residual block and $sMbFlag$ is equal to 1, + +$$qP = QS_{\gamma} \quad (8-331)$$ + +- Otherwise, if the input array $c$ relates to a chroma residual block and $sMbFlag$ is equal to 0, + +$$qP = QP'_{c} \quad (8-332)$$ + +- Otherwise (the input array $c$ relates to a chroma residual block and $sMbFlag$ is equal to 1), + +$$qP = QS_{c} \quad (8-333)$$ + +Depending on the value of $TransformBypassModeFlag$ , the following applies: + +- If $TransformBypassModeFlag$ is equal to 1, the output $r$ is derived as: + +$$r_{ij} = c_{ij} \text{ with } i, j = 0..3 \quad (8-334)$$ + +- Otherwise ( $TransformBypassModeFlag$ is equal to 0), the following ordered steps are specified: + +1. The scaling process for residual 4x4 blocks as specified in clause 8.5.12.1 is invoked with $bitDepth$ , $qP$ , and $c$ as the inputs and the output is assigned to the 4x4 array $d$ of scaled transform coefficients with elements $d_{ij}$ . +2. The transformation process for residual 4x4 blocks as specified in clause 8.5.12.2 is invoked with $bitDepth$ and $d$ as the inputs and the output is assigned to the 4x4 array $r$ of residual sample values with elements $r_{ij}$ . + +### 8.5.12.1 Scaling process for residual 4x4 blocks + +Inputs of this process are: + +- the variables $bitDepth$ and $qP$ , +- a 4x4 array $c$ with elements $c_{ij}$ which is either an array relating to a residual block of luma component or an array relating to a residual block of a chroma component. + +Output of this process is a 4x4 array of scaled transform coefficients $d$ with elements $d_{ij}$ . + +The bitstream shall not contain data that result in any element $c_{ij}$ of $c$ with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + bitDepth)}$ to $2^{(7 + bitDepth)} - 1$ , inclusive. + +Scaling of 4x4 block transform coefficient levels $c_{ij}$ proceeds as follows: + +- If all of the following conditions are true: + - $i$ is equal to 0, + - $j$ is equal to 0, + - $c$ relates to a luma residual block coded using Intra\_16x16 macroblock prediction mode or $c$ relates to a chroma residual block. + +the variable $d_{00}$ is derived by + +$$d_{00} = c_{00} \quad (8-335)$$ + +- Otherwise, the following applies: + +- If $qP$ is greater than or equal to 24, the scaled result is derived as + +$$d_{ij} = ( c_{ij} * \text{LevelScale4x4}( qP \% 6, i, j ) ) \ll ( qP / 6 - 4 ), \text{ with } i, j = 0..3 \text{ except as noted above} \quad (8-336)$$ + +- Otherwise ( $qP$ is less than 24), the scaled result is derived as + +$$d_{ij} = ( c_{ij} * \text{LevelScale4x4}( qP \% 6, i, j ) + 2^{3 - qP/6} ) \gg ( 4 - qP / 6 ), \text{ with } i, j = 0..3 \text{ except as noted above} \quad (8-337)$$ + +The bitstream shall not contain data that result in any element $d_{ij}$ of $d$ with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +### 8.5.12.2 Transformation process for residual 4x4 blocks + +Inputs of this process are: + +- the variable $\text{bitDepth}$ , +- a 4x4 array of scaled transform coefficients $d$ with elements $d_{ij}$ . + +Outputs of this process are residual sample values as 4x4 array $r$ with elements $r_{ij}$ . + +The bitstream shall not contain data that result in any element $d_{ij}$ of $d$ with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +The transform process shall convert the block of scaled transform coefficients to a block of output samples in a manner mathematically equivalent to the following. + +First, each (horizontal) row of scaled transform coefficients is transformed using a one-dimensional inverse transform as follows. + +A set of intermediate values is computed as follows: + +$$e_{i0} = d_{i0} + d_{i2}, \quad \text{with } i = 0..3 \quad (8-338)$$ + +$$e_{i1} = d_{i0} - d_{i2}, \quad \text{with } i = 0..3 \quad (8-339)$$ + +$$e_{i2} = ( d_{i1} \gg 1 ) - d_{i3}, \quad \text{with } i = 0..3 \quad (8-340)$$ + +$$e_{i3} = d_{i1} + ( d_{i3} \gg 1 ), \quad \text{with } i = 0..3 \quad (8-341)$$ + +The bitstream shall not contain data that result in any element $e_{ij}$ of $e$ with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +Then, the transformed result is computed from these intermediate values as follows: + +$$f_{i0} = e_{i0} + e_{i3}, \quad \text{with } i = 0..3 \quad (8-342)$$ + +$$f_{i1} = e_{i1} + e_{i2}, \quad \text{with } i = 0..3 \quad (8-343)$$ + +$$f_{i2} = e_{i1} - e_{i2}, \quad \text{with } i = 0..3 \quad (8-344)$$ + +$$f_{i3} = e_{i0} - e_{i3}, \quad \text{with } i = 0..3 \quad (8-345)$$ + +The bitstream shall not contain data that result in any element $f_{ij}$ of $f$ with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +Then, each (vertical) column of the resulting matrix is transformed using the same one-dimensional inverse transform as follows. + +A set of intermediate values is computed as follows: + +$$g_{0j} = f_{0j} + f_{2j}, \quad \text{with } j = 0..3 \quad (8-346)$$ + +$$g_{1j} = f_{0j} - f_{2j}, \quad \text{with } j = 0..3 \quad (8-347)$$ + +$$g_{2j} = ( f_{1j} \gg 1 ) - f_{3j}, \quad \text{with } j = 0..3 \quad (8-348)$$ + +$$g_{3j} = f_{1j} + ( f_{3j} \gg 1 ), \quad \text{with } j = 0..3 \quad (8-349)$$ + +The bitstream shall not contain data that result in any element $g_{ij}$ of $g$ with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +Then, the transformed result is computed from these intermediate values as follows: + +$$h_{0j} = g_{0j} + g_{3j}, \quad \text{with } j = 0..3 \quad (8-350)$$ + +$$h_{1j} = g_{1j} + g_{2j}, \quad \text{with } j = 0..3 \quad (8-351)$$ + +$$h_{2j} = g_{1j} - g_{2j}, \text{ with } j = 0..3 \quad (8-352)$$ + +$$h_{3j} = g_{0j} - g_{3j}, \text{ with } j = 0..3 \quad (8-353)$$ + +The bitstream shall not contain data that result in any element $h_{ij}$ of $h$ with $i, j = 0..3$ that exceeds the range of integer values from $-2^{(7+\text{bitDepth})}$ to $2^{(7+\text{bitDepth})} - 33$ , inclusive. + +After performing both the one-dimensional horizontal and the one-dimensional vertical inverse transforms to produce an array of transformed samples, the final constructed residual sample values is derived as: + +$$r_{ij} = (h_{ij} + 2^5) \gg 6, \text{ with } i, j = 0..3 \quad (8-354)$$ + +### 8.5.13 Scaling and transformation process for residual 8x8 blocks + +Input to this process is an 8x8 array $c$ with elements $c_{ij}$ which is either an array relating to an 8x8 residual block of the luma component or, when $\text{ChromaArrayType}$ is equal to 3, an array relating to an 8x8 residual block of a chroma component. + +NOTE 1 – When $\text{separate\_colour\_plane\_flag}$ is equal to 1, all residual blocks are considered to be associated with the luma component for purposes of the decoding process of each coded picture (prior to the final assignment of the decoded picture to a particular luma or chroma picture array according to the value of $\text{colour\_plane\_id}$ ). + +Outputs of this process are residual sample values as 8x8 array $r$ with elements $r_{ij}$ . + +The variables $\text{bitDepth}$ and $\text{qP}$ are derived as follows: + +- If the input array $c$ relates to a luma residual block, $\text{bitDepth}$ is set equal to $\text{BitDepth}_Y$ and $\text{qP}$ is set equal to $\text{QP}'_Y$ . +- Otherwise (the input array $c$ relates to a chroma residual block), $\text{bitDepth}$ is set equal to $\text{BitDepth}_C$ and $\text{qP}$ is set equal to $\text{QP}'_C$ . + +NOTE 2 – When $\text{separate\_colour\_plane\_flag}$ is equal to 1, all residual blocks are considered to be associated with the luma component for purposes of the decoding process of each colour component of a picture. + +Depending on the value of $\text{TransformBypassModeFlag}$ , the following applies: + +- If $\text{TransformBypassModeFlag}$ is equal to 1, the output $r$ is derived as + +$$r_{ij} = c_{ij} \text{ with } i, j = 0..7 \quad (8-355)$$ + +- Otherwise ( $\text{TransformBypassModeFlag}$ is equal to 0), the following ordered steps are specified: + 1. The scaling process for residual 8x8 blocks as specified in clause 8.5.13.1 is invoked with $\text{bitDepth}$ , $\text{qP}$ , and $c$ as the inputs and the output is assigned to the 8x8 array $d$ of scaled transform coefficients with elements $d_{ij}$ . + 2. The transformation process for residual 8x8 blocks as specified in clause 8.5.13.2 is invoked with $\text{bitDepth}$ and $d$ as the inputs and the output is assigned to the 8x8 array $r$ of residual sample values with elements $r_{ij}$ . + +#### 8.5.13.1 Scaling process for residual 8x8 blocks + +Inputs of this process are: + +- the variables $\text{bitDepth}$ and $\text{qP}$ , +- an 8x8 array $c$ with elements $c_{ij}$ which is either an array relating to a residual block of luma component or an array relating to a residual block of a chroma component. + +Output of this process is an 8x8 array of scaled transform coefficients $d$ with elements $d_{ij}$ . + +The bitstream shall not contain data that result in any element $c_{ij}$ of $c$ with $i, j = 0..7$ that exceeds the range of integer values from $-2^{(7+\text{bitDepth})}$ to $2^{(7+\text{bitDepth})} - 1$ , inclusive. + +The scaling process for 8x8 block transform coefficient levels $c_{ij}$ proceeds as follows: + +- If $\text{qP}$ is greater than or equal to 36, the scaled result is derived as: + +$$d_{ij} = (c_{ij} * \text{LevelScale8x8}(\text{qP} \% 6, i, j)) \ll (\text{qP} / 6 - 6), \text{ with } i, j = 0..7 \quad (8-356)$$ + +- Otherwise ( $\text{qP}$ is less than 36), the scaled result is derived as: + +$$d_{ij} = (c_{ij} * \text{LevelScale8x8}(\text{qP} \% 6, i, j) + 2^{5-\text{qP}/6}) \gg (6 - \text{qP} / 6), \text{ with } i, j = 0..7 \quad (8-357)$$ + +The bitstream shall not contain data that result in any element $d_{ij}$ of $d$ with $i, j = 0..7$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +### 8.5.13.2 Transformation process for residual 8x8 blocks + +Inputs of this process are: + +- the variable $\text{bitDepth}$ , +- an 8x8 array of scaled transform coefficients $d$ with elements $d_{ij}$ . + +Outputs of this process are residual sample values as 8x8 array $r$ with elements $r_{ij}$ . + +The bitstream shall not contain data that result in any element $d_{ij}$ of $d$ with $i, j = 0..7$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +The transform process shall convert the block of scaled transform coefficients to a block of output samples in a manner mathematically equivalent to the following. + +First, each (horizontal) row of scaled transform coefficients is transformed using a one-dimensional inverse transform as follows: + +- A set of intermediate values $e_{ij}$ is derived by: + +$$e_{i0} = d_{i0} + d_{i4}, \text{ with } i = 0..7 \quad (8-358)$$ + +$$e_{i1} = -d_{i3} + d_{i5} - d_{i7} - (d_{i7} \gg 1), \text{ with } i = 0..7 \quad (8-359)$$ + +$$e_{i2} = d_{i0} - d_{i4}, \text{ with } i = 0..7 \quad (8-360)$$ + +$$e_{i3} = d_{i1} + d_{i7} - d_{i3} - (d_{i3} \gg 1), \text{ with } i = 0..7 \quad (8-361)$$ + +$$e_{i4} = (d_{i2} \gg 1) - d_{i6}, \text{ with } i = 0..7 \quad (8-362)$$ + +$$e_{i5} = -d_{i1} + d_{i7} + d_{i5} + (d_{i5} \gg 1), \text{ with } i = 0..7 \quad (8-363)$$ + +$$e_{i6} = d_{i2} + (d_{i6} \gg 1), \text{ with } i = 0..7 \quad (8-364)$$ + +$$e_{i7} = d_{i3} + d_{i5} + d_{i1} + (d_{i1} \gg 1), \text{ with } i = 0..7 \quad (8-365)$$ + +- A second set of intermediate results $f_{ij}$ is computed from the intermediate values $e_{ij}$ as: + +$$f_{i0} = e_{i0} + e_{i6}, \text{ with } i = 0..7 \quad (8-366)$$ + +$$f_{i1} = e_{i1} + (e_{i7} \gg 2), \text{ with } i = 0..7 \quad (8-367)$$ + +$$f_{i2} = e_{i2} + e_{i4}, \text{ with } i = 0..7 \quad (8-368)$$ + +$$f_{i3} = e_{i3} + (e_{i5} \gg 2), \text{ with } i = 0..7 \quad (8-369)$$ + +$$f_{i4} = e_{i2} - e_{i4}, \text{ with } i = 0..7 \quad (8-370)$$ + +$$f_{i5} = (e_{i3} \gg 2) - e_{i5}, \text{ with } i = 0..7 \quad (8-371)$$ + +$$f_{i6} = e_{i0} - e_{i6}, \text{ with } i = 0..7 \quad (8-372)$$ + +$$f_{i7} = e_{i7} - (e_{i1} \gg 2), \text{ with } i = 0..7 \quad (8-373)$$ + +- Then, the transformed result $g_{ij}$ is computed from these intermediate values $f_{ij}$ as: + +$$g_{i0} = f_{i0} + f_{i7}, \text{ with } i = 0..7 \quad (8-374)$$ + +$$g_{i1} = f_{i2} + f_{i5}, \text{ with } i = 0..7 \quad (8-375)$$ + +$$g_{i2} = f_{i4} + f_{i3}, \text{ with } i = 0..7 \quad (8-376)$$ + +$$g_{i3} = f_{i6} + f_{i1}, \text{ with } i = 0..7 \quad (8-377)$$ + +$$g_{i4} = f_{i6} - f_{i1}, \text{ with } i = 0..7 \quad (8-378)$$ + +$$g_{i5} = f_{i4} - f_{i3}, \text{ with } i = 0..7 \quad (8-379)$$ + +$$g_{i6} = f_{i2} - f_{i5}, \text{ with } i = 0..7 \quad (8-380)$$ + +$$g_{i7} = f_{i0} - f_{i7}, \text{ with } i = 0..7 \quad (8-381)$$ + +Then, each (vertical) column of the resulting matrix is transformed using the same one-dimensional inverse transform as follows: + +- A set of intermediate values $h_{ij}$ is computed from the horizontally transformed value $g_{ij}$ as: + +$$h_{0j} = g_{0j} + g_{4j}, \text{ with } j = 0..7 \quad (8-382)$$ + +$$h_{1j} = -g_{3j} + g_{5j} - g_{7j} - (g_{7j} \gg 1), \text{ with } j = 0..7 \quad (8-383)$$ + +$$h_{2j} = g_{0j} - g_{4j}, \text{ with } j = 0..7 \quad (8-384)$$ + +$$h_{3j} = g_{1j} + g_{7j} - g_{3j} - (g_{3j} \gg 1), \text{ with } j = 0..7 \quad (8-385)$$ + +$$h_{4j} = (g_{2j} \gg 1) - g_{6j}, \text{ with } j = 0..7 \quad (8-386)$$ + +$$h_{5j} = -g_{1j} + g_{7j} + g_{5j} + (g_{5j} \gg 1), \text{ with } j = 0..7 \quad (8-387)$$ + +$$h_{6j} = g_{2j} + (g_{6j} \gg 1), \text{ with } j = 0..7 \quad (8-388)$$ + +$$h_{7j} = g_{3j} + g_{5j} + g_{1j} + (g_{1j} \gg 1), \text{ with } j = 0..7 \quad (8-389)$$ + +- A second set of intermediate results $k_{ij}$ is computed from the intermediate values $h_{ij}$ as: + +$$k_{0j} = h_{0j} + h_{6j}, \text{ with } j = 0..7 \quad (8-390)$$ + +$$k_{1j} = h_{1j} + (h_{7j} \gg 2), \text{ with } j = 0..7 \quad (8-391)$$ + +$$k_{2j} = h_{2j} + h_{4j}, \text{ with } j = 0..7 \quad (8-392)$$ + +$$k_{3j} = h_{3j} + (h_{5j} \gg 2), \text{ with } j = 0..7 \quad (8-393)$$ + +$$k_{4j} = h_{2j} - h_{4j}, \text{ with } j = 0..7 \quad (8-394)$$ + +$$k_{5j} = (h_{3j} \gg 2) - h_{5j}, \text{ with } j = 0..7 \quad (8-395)$$ + +$$k_{6j} = h_{0j} - h_{6j}, \text{ with } j = 0..7 \quad (8-396)$$ + +$$k_{7j} = h_{7j} - (h_{1j} \gg 2), \text{ with } j = 0..7 \quad (8-397)$$ + +- Then, the transformed result $m_{ij}$ is computed from these intermediate values $k_{ij}$ as: + +$$m_{0j} = k_{0j} + k_{7j}, \text{ with } j = 0..7 \quad (8-398)$$ + +$$m_{1j} = k_{2j} + k_{5j}, \text{ with } j = 0..7 \quad (8-399)$$ + +$$m_{2j} = k_{4j} + k_{3j}, \text{ with } j = 0..7 \quad (8-400)$$ + +$$m_{3j} = k_{6j} + k_{1j}, \text{ with } j = 0..7 \quad (8-401)$$ + +$$m_{4j} = k_{6j} - k_{1j}, \text{ with } j = 0..7 \quad (8-402)$$ + +$$m_{5j} = k_{4j} - k_{3j}, \text{ with } j = 0..7 \quad (8-403)$$ + +$$m_{6j} = k_{2j} - k_{5j}, \text{ with } j = 0..7 \quad (8-404)$$ + +$$m_{ij} = k_{0j} - k_{7j}, \text{ with } j = 0..7 \quad (8-405)$$ + +The bitstream shall not contain data that result in any element $e_{ij}$ , $f_{ij}$ , $g_{ij}$ , $h_{ij}$ , or $k_{ij}$ for $i$ and $j$ in the range of 0..7, inclusive, that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +The bitstream shall not contain data that result in any element $m_{ij}$ for $i$ and $j$ in the range of 0..7, inclusive, that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 33$ , inclusive. + +After performing both the one-dimensional horizontal and the one-dimensional vertical inverse transforms to produce an array of transformed samples, the final constructed residual sample values are derived as + +$$r_{ij} = ( m_{ij} + 2^5 ) \gg 6 \text{ with } i, j = 0..7 \quad (8-406)$$ + +#### 8.5.14 Picture construction process prior to deblocking filter process + +Inputs to this process are: + +- a sample array $u$ with elements $u_{ij}$ which is a 16x16 luma block or an $(\text{MbWidthC}) \times (\text{MbHeightC})$ chroma block or a 4x4 luma block or a 4x4 chroma block or an 8x8 luma block or, when $\text{ChromaArrayType}$ is equal to 3, an 8x8 chroma block, +- when $u$ is not a 16x16 luma block or an $(\text{MbWidthC}) \times (\text{MbHeightC})$ chroma block, a block index $\text{luma4x4BlkIdx}$ or $\text{chroma4x4BlkIdx}$ or $\text{luma8x8BlkIdx}$ or $\text{cb4x4BlkIdx}$ or $\text{cr4x4BlkIdx}$ or $\text{cb8x8BlkIdx}$ or $\text{cr8x8BlkIdx}$ . + +The position of the upper-left luma sample of the current macroblock is derived by invoking the inverse macroblock scanning process in clause 6.4.1 with $\text{CurrMbAddr}$ as input and the output being assigned to $(xP, yP)$ . + +When $u$ is a luma block, for each sample $u_{ij}$ of the luma block, the following ordered steps are specified: + +1. Depending on the size of the block $u$ , the following applies: + - If $u$ is a 16x16 luma block, the position $(xO, yO)$ of the upper-left sample of the 16x16 luma block inside the macroblock is set equal to $(0, 0)$ and the variable $nE$ is set equal to 16. + - Otherwise, if $u$ is an 4x4 luma block, the position of the upper-left sample of the 4x4 luma block with index $\text{luma4x4BlkIdx}$ inside the macroblock is derived by invoking the inverse 4x4 luma block scanning process in clause 6.4.3 with $\text{luma4x4BlkIdx}$ as the input and the output being assigned to $(xO, yO)$ , and the variable $nE$ is set equal to 4. + - Otherwise ( $u$ is an 8x8 luma block), the position of the upper-left sample of the 8x8 luma block with index $\text{luma8x8BlkIdx}$ inside the macroblock is derived by invoking the inverse 8x8 luma block scanning process in clause 6.4.5 with $\text{luma8x8BlkIdx}$ as the input and the output being assigned to $(xO, yO)$ , and the variable $nE$ is set equal to 8. +2. Depending on the variable $\text{MbaffFrameFlag}$ and the current macroblock, the following applies: + +- If $\text{MbaffFrameFlag}$ is equal to 1 and the current macroblock is a field macroblock, + +$$S'_L[ xP + xO + j, yP + 2 * ( yO + i ) ] = u_{ij} \text{ with } i, j = 0..nE - 1 \quad (8-407)$$ + +- Otherwise ( $\text{MbaffFrameFlag}$ is equal to 0 or the current macroblock is a frame macroblock), + +$$S'_L[ xP + xO + j, yP + yO + i ] = u_{ij} \text{ with } i, j = 0..nE - 1 \quad (8-408)$$ + +When $u$ is a chroma block, for each sample $u_{ij}$ of the chroma block, the following ordered steps are specified: + +1. The subscript $C$ in the variable $S'_C$ is replaced with $Cb$ for the $Cb$ chroma component and with $Cr$ for the $Cr$ chroma component. +2. Depending on the size of the block $u$ , the following applies: + - If $u$ is an $(\text{MbWidthC}) \times (\text{MbHeightC})$ $Cb$ or $Cr$ block, the variable $nW$ is set equal to $\text{MbWidthC}$ , the variable $nH$ is set equal to $\text{MbHeightC}$ , and the position $(xO, yO)$ of the upper-left sample of the $(nW) \times (nH)$ $Cb$ or $Cr$ block inside the macroblock is set equal to $(0, 0)$ . + - Otherwise, if $u$ is a 4x4 $Cb$ or $Cr$ block, the variables $nW$ and $nH$ are set equal to 4 and, depending on the variable $\text{ChromaArrayType}$ , the position of the upper-left sample of a 4x4 $Cb$ or $Cr$ block with index $\text{chroma4x4BlkIdx}$ inside the macroblock is derived as follows: + +- If ChromaArrayType is equal to 1 or 2, the position of the upper-left sample of the 4x4 chroma block with index chroma4x4BlkIdx inside the macroblock is derived by invoking the inverse 4x4 chroma block scanning process in clause 6.4.7 with chroma4x4BlkIdx as the input and the output being assigned to ( xO, yO ). + - Otherwise (ChromaArrayType is equal to 3), the position of the upper-left sample of the 4x4 Cb block with index cb4x4BlkIdx or the 4x4 Cr block with index cr4x4BlkIdx inside the macroblock is derived by invoking the inverse 4x4 Cb or Cr block scanning process in clause 6.4.4 with cb4x4BlkIdx or cr4x4BlkIdx as the input and the output being assigned to ( xO, yO ). + - Otherwise (u is an 8x8 Cb or Cr block when ChromaArrayType is equal to 3), the variables nW and nH are set equal to 8 and the position of the upper-left sample of the 8x8 Cb block with index cb8x8BlkIdx or the Cr block with index cr8x8BlkIdx inside the macroblock is derived by invoking the inverse 8x8 Cb or Cr block scanning process in clause 6.4.6 with cb8x8BlkIdx or cr8x8BlkIdx as the input and the output being assigned to ( xO, yO ). +3. Depending on the variable MbuffFrameFlag and the current macroblock, the following applies: +- If MbuffFrameFlag is equal to 1 and the current macroblock is a field macroblock, +$$S'c[ ( xP / \text{subWidthC} ) + xO + j, ( ( yP + \text{SubHeightC} - 1 ) / \text{SubHeightC} ) + 2 * ( yO + i ) ] = u_{ij}$$ +with $i = 0..nH - 1$ and $j = 0..nW - 1$ (8-409) + - Otherwise (MbuffFrameFlag is equal to 0 or the current macroblock is a frame macroblock), +$$S'c[ ( xP / \text{subWidthC} ) + xO + j, ( yP / \text{SubHeightC} ) + yO + i ] = u_{ij}$$ +with $i = 0..nH - 1$ and $j = 0..nW - 1$ (8-410) + +### 8.5.15 Intra residual transform-bypass decoding process + +This process is invoked when TransformBypassModeFlag is equal to 1, the macroblock prediction mode is equal to Intra\_4x4, Intra\_8x8, or Intra\_16x16, and the applicable intra prediction mode is equal to the vertical or horizontal mode. The process for the Cb and Cr components is applied in the same way as for the luma (L or Y) component. + +Inputs to this process are: + +- two variables nW and nH, +- a variable horPredFlag, +- an (nW)x(nH) array r with elements $r_{ij}$ which is either an array relating to a residual transform-bypass block of the luma component or an array relating to a residual transform-bypass block of the Cb and Cr component. + +Output of this process is a modified version of the (nW)x(nH) array r with elements $r_{ij}$ containing the result of the intra residual transform-bypass decoding process. + +Let f be a temporary (nW)x(nH) array with elements $f_{ij}$ , which are derived by: + +$$f_{ij} = r_{ij} \quad \text{with } i = 0..nH - 1 \text{ and } j = 0..nW - 1 \quad (8-411)$$ + +Depending on horPredFlag, the following applies: + +- If horPredFlag is equal to 0, the modified array r is derived by: + +$$r_{ij} = \sum_{k=0}^i f_{kj} \quad \text{with } i = 0..nH - 1 \text{ and } j = 0..nW - 1 \quad (8-412)$$ + +- Otherwise (horPredFlag is equal to 1), the modified array r is derived by: + +$$r_{ij} = \sum_{k=0}^j f_{ik} \quad \text{with } i = 0..nH - 1 \text{ and } j = 0..nW - 1 \quad (8-413)$$ + +## 8.6 Decoding process for P macroblocks in SP slices or SI macroblocks + +This process is invoked when decoding P macroblock types in an SP slice type or the SI macroblock type in SI slices. + +Inputs to this process are the prediction residual transform coefficient levels and the predicted samples for the current macroblock. + +Outputs of this process are the decoded samples of the current macroblock prior to the deblocking filter process. + +This clause specifies the transform coefficient decoding process and picture construction process for P macroblock types in SP slices and the SI macroblock type in SI slices. + +NOTE – SP slices make use of Inter predictive coding to exploit temporal redundancy in the sequence, in a similar manner to P slice coding. Unlike P slice coding, however, SP slice coding allows identical reconstruction of a slice even when different reference pictures are being used. SI slices make use of spatial prediction, in a similar manner to I slices. SI slice coding allows identical reconstruction to a corresponding SP slice. The properties of SP and SI slices aid in providing functionalities for bitstream switching, splicing, random access, fast-forward, fast reverse, and error resilience/recovery. + +An SP slice consists of macroblocks coded either as I macroblock types or P macroblock types. + +An SI slice consists of macroblocks coded either as I macroblock types or SI macroblock type. + +The transform coefficient decoding process and picture construction process prior to deblocking filter process for I macroblock types in SI slices is invoked as specified in clause 8.5. The SI macroblock type is decoded as described below. + +When the current macroblock is coded as P\_Skip, all values of LumaLevel4x4, ChromaDCLevel, ChromaACLevel are set equal to 0 for the current macroblock. + +### 8.6.1 SP decoding process for non-switching pictures + +This process is invoked, when decoding P macroblock types in SP slices in which sp\_for\_switch\_flag is equal to 0. + +Inputs to this process are Inter prediction samples for the current macroblock from clause 8.4 and the prediction residual transform coefficient levels. + +Outputs of this process are the decoded samples of the current macroblock prior to the deblocking filter process. + +This clause applies to all macroblocks in SP slices in which sp\_for\_switch\_flag is equal to 0, except those with macroblock prediction mode equal to Intra\_4x4 or Intra\_16x16. It does not apply to SI slices. + +#### 8.6.1.1 Luma transform coefficient decoding process + +Inputs to this process are Inter prediction luma samples for the current macroblock predL from clause 8.4 and the prediction residual transform coefficient levels, LumaLevel4x4, and the index of the 4x4 luma block luma4x4BlkIdx. + +The position of the upper-left sample of the 4x4 luma block with index luma4x4BlkIdx inside the current macroblock is derived by invoking the inverse 4x4 luma block scanning process in clause 6.4.3 with luma4x4BlkIdx as the input and the output being assigned to ( x, y ). + +Let the variable p be a 4x4 array of prediction samples with element pij being derived as: + +$$p_{ij} = \text{pred}_L[ x + j, y + i ] \quad \text{with } i, j = 0..3 \quad (8-414)$$ + +The variable p is transformed producing transform coefficients cp according to: + +$$c^p = \begin{bmatrix} 1 & 1 & 1 & 1 \\ 2 & 1 & -1 & -2 \\ 1 & -1 & -1 & 1 \\ 1 & -2 & 2 & -1 \end{bmatrix} * \begin{bmatrix} p_{00} & p_{01} & p_{02} & p_{03} \\ p_{10} & p_{11} & p_{12} & p_{13} \\ p_{20} & p_{21} & p_{22} & p_{23} \\ p_{30} & p_{31} & p_{32} & p_{33} \end{bmatrix} * \begin{bmatrix} 1 & 2 & 1 & 1 \\ 1 & 1 & -1 & -2 \\ 1 & -1 & -1 & 2 \\ 1 & -2 & 1 & -1 \end{bmatrix} \quad (8-415)$$ + +The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with LumaLevel4x4[ luma4x4BlkIdx ] as the input and the two-dimensional array cr with elements cijr as the output. + +The prediction residual transform coefficients cr are scaled using quantization parameter QPY, and added to the transform coefficients of the prediction block cp with i, j = 0..3 as follows: + +$$c_{ij}^s = c_{ij}^p + ( ( c_{ij}^r * \text{LevelScale4x4}( QP_Y \% 6, i, j ) * A_{ij} ) \ll ( QP_Y / 6 ) ) \gg 10 ) \quad (8-416)$$ + +where $\text{LevelScale4x4}(m, i, j)$ is specified in Equation 8-313, and $A_{ij}$ is specified as: + +$$A_{ij} = \begin{cases} 16 & \text{for } (i, j) \in \{(0,0), (0,2), (2,0), (2,2)\}, \\ 25 & \text{for } (i, j) \in \{(1,1), (1,3), (3,1), (3,3)\}, \\ 20 & \text{otherwise;} \end{cases} \quad (8-417)$$ + +The function $\text{LevelScale2}(m, i, j)$ , used in the equations below, is specified as + +$$\text{LevelScale2}(m, i, j) = \begin{cases} w_{m0} & \text{for } (i, j) \in \{(0,0), (0,2), (2,0), (2,2)\}, \\ w_{m1} & \text{for } (i, j) \in \{(1,1), (1,3), (3,1), (3,3)\}, \\ w_{m2} & \text{otherwise;} \end{cases} \quad (8-418)$$ + +where the first and second subscripts of $w$ are row and column indices, respectively, of the matrix specified as + +$$w = \begin{bmatrix} 13107 & 5243 & 8066 \\ 11916 & 4660 & 7490 \\ 10082 & 4194 & 6554 \\ 9362 & 3647 & 5825 \\ 8192 & 3355 & 5243 \\ 7282 & 2893 & 4559 \end{bmatrix} \quad (8-419)$$ + +The resulting sum, $c^s$ , is quantized with a quantization parameter $QS_Y$ and with $i, j = 0..3$ as follows: + +$$c_{ij} = \text{Sign}(c_{ij}^s) * ( ( \text{Abs}(c_{ij}^s) * \text{LevelScale2}(QS_Y \% 6, i, j) + (1 \ll (14 + QS_Y / 6)) ) \gg (15 + QS_Y / 6) ) \quad (8-420)$$ + +The scaling and transformation process for residual 4x4 blocks as specified in clause 8.5.12 is invoked with $c$ as the input and $r$ as the output. + +The 4x4 array $u$ with elements $u_{ij}$ is derived by: + +$$u_{ij} = \text{Clip1}_V(r_{ij}) \text{ with } i, j = 0..3 \quad (8-421)$$ + +The picture construction process prior to deblocking filter process in clause 8.5.14 is invoked with $\text{luma4x4BlkIdx}$ and $u$ as the inputs. + +### 8.6.1.2 Chroma transform coefficient decoding process + +Inputs to this process are Inter prediction chroma samples for the current macroblock from clause 8.4 and the prediction residual transform coefficient levels, $\text{ChromaDCLevel}$ and $\text{ChromaACLevel}$ . + +This process is invoked twice: once for the Cb component and once for the Cr component. The component is referred to by replacing C with Cb for the Cb component and C with Cr for the Cr component. Let $iCbCr$ select the current chroma component. + +For each 4x4 block of the current chroma component indexed using $\text{chroma4x4BlkIdx}$ with $\text{chroma4x4BlkIdx}$ equal to 0..3, the following ordered steps are specified: + +1. The position of the upper-left sample of a 4x4 chroma block with index $\text{chroma4x4BlkIdx}$ inside the macroblock is derived by invoking the inverse 4x4 chroma block scanning process in clause 6.4.7 with $\text{chroma4x4BlkIdx}$ as the input and the output being assigned to $(xO, yO)$ . +2. Let $p$ be a 4x4 array of prediction samples with elements $p_{ij}$ being derived as + +$$p_{ij} = \text{predC}[x + j, y + i] \text{ with } i, j = 0..3 \quad (8-422)$$ + +3. The 4x4 array $p$ is transformed producing transform coefficients $c^p(\text{chroma4x4BlkIdx})$ using Equation 8-415. +4. The variable $\text{chromaList}$ , which is a list of 16 entries, is derived. $\text{chromaList}[0]$ is set equal to 0. $\text{chromaList}[k]$ with index $k = 1..15$ are specified as follows: + +$$\text{chromaList}[k] = \text{ChromaACLevel}[iCbCr][\text{chroma4x4BlkIdx}][k - 1] \quad (8-423)$$ + +5. The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with $\text{chromaList}$ as the input and the 4x4 array $c^r$ as the output. + +6. The prediction residual transform coefficients $c^r$ are scaled using quantization parameter $QP_C$ , and added to the transform coefficients of the prediction block $c^p$ with $i, j = 0..3$ except for the combination $i = 0, j = 0$ as follows: + +$$c_{ij}^s = c_{ij}^p(\text{chroma4x4BlkIdx}) + ( ( c_{ij}^r * \text{LevelScale4x4}( QP_C \% 6, i, j ) * A_{ij} ) \ll ( QP_C / 6 ) ) \gg 10 ) \quad (8-424)$$ + +7. The resulting sum, $c^s$ , is quantized with a quantization parameter $QS_C$ and with $i, j = 0..3$ except for the combination $i = 0, j = 0$ as follows. The derivation of $c_{00}(\text{chroma4x4BlkIdx})$ is described below in this clause. + +$$c_{ij}(\text{chroma4x4BlkIdx}) = ( \text{Sign}( c_{ij}^s ) * ( \text{Abs}( c_{ij}^s ) * \text{LevelScale2}( QS_C \% 6, i, j ) + ( 1 \ll ( 14 + QS_C / 6 ) ) ) ) \gg ( 15 + QS_C / 6 ) ) \quad (8-425)$$ + +8. The scaling and transformation process for residual 4x4 blocks as specified in clause 8.5.12 is invoked with $c(\text{chroma4x4BlkIdx})$ as the input and $r$ as the output. + +9. The 4x4 array $u$ with elements $u_{ij}$ is derived by: + +$$u_{ij} = \text{Clip1c}( r_{ij} ) \text{ with } i, j = 0..3 \quad (8-426)$$ + +10. The picture construction process prior to deblocking filter process in clause 8.5.14 is invoked with $\text{chroma4x4BlkIdx}$ and $u$ as the inputs. + +The derivation of the DC transform coefficient level $c_{00}(\text{chroma4x4BlkIdx})$ is specified as follows. The DC transform coefficients of the 4 prediction chroma 4x4 blocks of the current component of the macroblock are assembled into a 2x2 matrix with elements $c_{00}^p(\text{chroma4x4BlkIdx})$ and a 2x2 transform is applied to the DC transform coefficients as follows: + +$$dc^p = \begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix} * \begin{bmatrix} c_{00}^p(0) & c_{00}^p(1) \\ c_{00}^p(2) & c_{00}^p(3) \end{bmatrix} * \begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix} \quad (8-427)$$ + +The chroma DC prediction residual transform coefficient levels, $\text{ChromaDCLevel}[ iCbCr ][ k ]$ with $k = 0..3$ are scaled using quantization parameter $QP_C$ , and added to the prediction DC transform coefficients as follows: + +$$dc_{ij}^s = dc_{ij}^p + ( ( ( \text{ChromaDCLevel}[ iCbCr ][ j * 2 + i ] * \text{LevelScale4x4}( QP_C \% 6, 0, 0 ) * A_{00} ) \ll ( QP_C / 6 ) ) \gg 9 ) \text{ with } i, j = 0, 1 \quad (8-428)$$ + +The 2x2 array $dc^s$ , is quantized using the quantization parameter $QS_C$ as follows: + +$$dc_{ij}^r = ( \text{Sign}( dc_{ij}^s ) * ( \text{Abs}( dc_{ij}^s ) * \text{LevelScale2}( QS_C \% 6, 0, 0 ) + ( 1 \ll ( 15 + QS_C / 6 ) ) ) ) \gg ( 16 + QS_C / 6 ) \text{ with } i, j = 0, 1 \quad (8-429)$$ + +The 2x2 array $f$ with elements $f_{ij}$ and $i, j = 0..1$ is derived as: + +$$f = \begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix} * \begin{bmatrix} dc_{00}^r & dc_{01}^r \\ dc_{10}^r & dc_{11}^r \end{bmatrix} * \begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix} \quad (8-430)$$ + +Scaling of the elements $f_{ij}$ of $f$ is performed as follows: + +$$c_{00}(j * 2 + i) = ( ( f_{ij} * \text{LevelScale4x4}( QS_C \% 6, 0, 0 ) ) \ll ( QS_C / 6 ) ) \gg 5 \text{ with } i, j = 0, 1 \quad (8-431)$$ + +## 8.6.2 SP and SI slice decoding process for switching pictures + +This process is invoked, when decoding P macroblock types in SP slices in which $sp\_for\_switch\_flag$ is equal to 1 and when decoding the SI macroblock type in SI slices. + +Inputs to this process are the prediction residual transform coefficient levels and the prediction sample arrays $pred_L$ , $pred_{Cb}$ and $pred_{Cr}$ for the current macroblock. + +### 8.6.2.1 Luma transform coefficient decoding process + +Inputs to this process are prediction luma samples $pred_L$ and the luma prediction residual transform coefficient levels, $\text{LumaLevel4x4}$ . + +The 4x4 array $p$ with elements $p_{ij}$ with $i, j = 0..3$ is derived as in clause 8.6.1.1, is transformed according to Equation 8-415 to produce transform coefficients $c^p$ . These transform coefficients are then quantized with the quantization parameter $QS_Y$ , as follows: + +$$c_{ij}^s = \text{Sign}(c_{ij}^p) * ( ( \text{Abs}(c_{ij}^p) * \text{LevelScale2}( \text{QS}_Y \% 6, i, j ) + ( 1 \ll ( 14 + \text{QS}_Y / 6 ) ) ) \gg ( 15 + \text{QS}_Y / 6 ) ) \text{ with } i, j = 0..3 \quad (8-432)$$ + +The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with `LumaLevel4x4[ luma4x4BlkIdx ]` as the input and the two-dimensional array $c^r$ with elements $c_{ij}^r$ as the output. + +The 4x4 array $c$ with elements $c_{ij}$ with $i, j = 0..3$ is derived by: + +$$c_{ij} = c_{ij}^r + c_{ij}^s \text{ with } i, j = 0..3 \quad (8-433)$$ + +The scaling and transformation process for residual 4x4 blocks as specified in clause 8.5.12 is invoked with $c$ as the input and $r$ as the output. + +The 4x4 array $u$ with elements $u_{ij}$ is derived by: + +$$u_{ij} = \text{Clip1}_V(r_{ij}) \text{ with } i, j = 0..3 \quad (8-434)$$ + +The picture construction process prior to deblocking filter process in clause 8.5.14 is invoked with `luma4x4BlkIdx` and $u$ as the inputs. + +### 8.6.2.2 Chroma transform coefficient decoding process + +Inputs to this process are predicted chroma samples for the current macroblock from clause 8.4 and the prediction residual transform coefficient levels, `ChromaDCLevel` and `ChromaACLevel`. + +This process is invoked twice: once for the Cb component and once for the Cr component. The component is referred to by replacing C with Cb for the Cb component and C with Cr for the Cr component. Let `iCbCr` select the current chroma component. + +For each 4x4 block of the current chroma component indexed using `chroma4x4BlkIdx` with `chroma4x4BlkIdx` equal to 0..3, the following ordered steps are specified: + +1. The 4x4 array $p$ with elements $p_{ij}$ with $i, j = 0..3$ is derived as in clause 8.6.1.2, is transformed according to Equation 8-415 to produce transform coefficients $c^p(\text{chroma4x4BlkIdx})$ . These transform coefficients are then quantized with the quantization parameter $\text{QS}_C$ , with $i, j = 0..3$ except for the combination $i = 0, j = 0$ as follows. The processing of $c_{00}^p(\text{chroma4x4BlkIdx})$ is described below in this clause. + +$$c_{ij}^s = ( \text{Sign}(c_{ij}^p(\text{chroma4x4BlkIdx})) * ( \text{Abs}(c_{ij}^p(\text{chroma4x4BlkIdx})) * \text{LevelScale2}(\text{QS}_C \% 6, i, j) + ( 1 \ll ( 14 + \text{QS}_C / 6 ) ) ) \gg ( 15 + \text{QS}_C / 6 ) ) \quad (8-435)$$ + +2. The variable `chromaList`, which is a list of 16 entries, is derived. `chromaList[ 0 ]` is set equal to 0. `chromaList[ k ]` with index $k = 1..15$ are specified as follows: + +$$\text{chromaList}[ k ] = \text{ChromaACLevel}[ \text{iCbCr} ][ \text{chroma4x4BlkIdx} ][ k - 1 ] \quad (8-436)$$ + +3. The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with `chromaList` as the input and the two-dimensional array $c^r(\text{chroma4x4BlkIdx})$ with elements $c_{ij}^r(\text{chroma4x4BlkIdx})$ as the output. + +4. The 4x4 array $c(\text{chroma4x4BlkIdx})$ with elements $c_{ij}(\text{chroma4x4BlkIdx})$ with $i, j = 0..3$ except for the combination $i = 0, j = 0$ is derived as follows. The derivation of $c_{00}(\text{chroma4x4BlkIdx})$ is described below. + +$$c_{ij}(\text{chroma4x4BlkIdx}) = c_{ij}^r(\text{chroma4x4BlkIdx}) + c_{ij}^s \quad (8-437)$$ + +5. The scaling and transformation process for residual 4x4 blocks as specified in clause 8.5.12 is invoked with $c(\text{chroma4x4BlkIdx})$ as the input and $r$ as the output. + +6. The 4x4 array $u$ with elements $u_{ij}$ is derived by: + +$$u_{ij} = \text{Clip1}_C(r_{ij}) \text{ with } i, j = 0..3 \quad (8-438)$$ + +7. The picture construction process prior to deblocking filter process in clause 8.5.14 is invoked with `chroma4x4BlkIdx` and $u$ as the inputs. + +The derivation of the DC transform coefficient level $c_{00}(\text{chroma4x4BlkIdx})$ is specified as follows. The DC transform coefficients of the 4 prediction 4x4 chroma blocks of the current component of the macroblock, $c_{00}^p(\text{chroma4x4BlkIdx})$ , + +are assembled into a 2x2 matrix, and a 2x2 transform is applied to the DC transform coefficients of these blocks according to Equation 8-427 resulting in DC transform coefficients $dc_{ij}^p$ . + +These DC transform coefficients are then quantized with the quantization parameter $QSc$ , as given by: + +$$dc_{ij}^s = (\text{Sign}(dc_{ij}^p) * (\text{Abs}(dc_{ij}^p) * \text{LevelScale2}(QSc \% 6, 0, 0) + (1 \ll (15 + QSc / 6)))) \gg (16 + QSc / 6)) \text{ with } i, j = 0, 1 \quad (8-439)$$ + +The parsed chroma DC prediction residual transform coefficients, $\text{ChromaDCLevel}[iCbCr][k]$ with $k = 0..3$ are added to these quantized DC transform coefficients of the prediction block, as given by: + +$$dc_{ij}^r = dc_{ij}^s + \text{ChromaDCLevel}[iCbCr][j * 2 + i] \text{ with } i, j = 0, 1 \quad (8-440)$$ + +The 2x2 array $f$ with elements $f_{ij}$ and $i, j = 0..1$ is derived using Equation 8-430. + +The 2x2 array $f$ with elements $f_{ij}$ and $i, j = 0..1$ is copied as follows: + +$$c_{00}(j * 2 + i) = f_{ij} \text{ with } i, j = 0, 1 \quad (8-441)$$ + +## 8.7 Deblocking filter process + +A conditional filtering process is specified in this clause that is an integral part of the decoding process which shall be applied by decoders conforming to the Baseline, Constrained Baseline, Main, Extended, High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, and High 4:4:4 Predictive profiles. For decoders conforming to the High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles, the filtering process specified in this clause, or one similar to it, should be applied but is not required. + +The conditional filtering process is applied to all $N \times N$ (where $N = 4$ or $N = 8$ for luma, $N = 4$ for chroma when $\text{ChromaArrayType}$ is equal to 1 or 2, and $N = 4$ or $N = 8$ for chroma when $\text{ChromaArrayType}$ is equal to 3) block edges of a picture, except edges at the boundary of the picture and any edges for which the deblocking filter process is disabled by $\text{disable_deblocking_filter_idc}$ , as specified below. This filtering process is performed on a macroblock basis after the completion of the picture construction process prior to deblocking filter process (as specified in clauses 8.5 and 8.6) for the entire decoded picture, with all macroblocks in a picture processed in order of increasing macroblock addresses. + +NOTE 1 – Prior to the operation of the deblocking filter process for each macroblock, the deblocked samples of the macroblock or macroblock pair above (if any) and the macroblock or macroblock pair to the left (if any) of the current macroblock are always available because the deblocking filter process is performed after the completion of the picture construction process prior to deblocking filter process for the entire decoded picture. However, for purposes of determining which edges are to be filtered when $\text{disable_deblocking_filter_idc}$ is equal to 2, macroblocks in different slices are considered not available during specified steps of the operation of the deblocking filter process. + +The deblocking filter process is invoked for the luma and chroma components separately. For each macroblock and each component, vertical edges are filtered first, starting with the edge on the left-hand side of the macroblock proceeding through the edges towards the right-hand side of the macroblock in their geometrical order, and then horizontal edges are filtered, starting with the edge on the top of the macroblock proceeding through the edges towards the bottom of the macroblock in their geometrical order. Figure 8-10 shows edges of a macroblock which can be interpreted as luma or chroma edges. + +When interpreting the edges in Figure 8-10 as luma edges, depending on the $\text{transform\_size\_8x8\_flag}$ , the following applies: + +- If $\text{transform\_size\_8x8\_flag}$ is equal to 0, both types, the solid bold and dashed bold luma edges are filtered. +- Otherwise ( $\text{transform\_size\_8x8\_flag}$ is equal to 1), only the solid bold luma edges are filtered. + +When interpreting the edges in Figure 8-10 as chroma edges, depending on $\text{ChromaArrayType}$ , the following applies: + +- If $\text{ChromaArrayType}$ is equal to 1 (4:2:0 format), only the solid bold chroma edges are filtered. +- Otherwise, if $\text{ChromaArrayType}$ is equal to 2 (4:2:2 format), the solid bold vertical chroma edges are filtered and both types, the solid bold and dashed bold horizontal chroma edges are filtered. +- Otherwise, if $\text{ChromaArrayType}$ is equal to 3 (4:4:4 format), the following applies: + - If $\text{transform\_size\_8x8\_flag}$ is equal to 0, both types, the solid bold and dashed bold chroma edges are filtered. + - Otherwise ( $\text{transform\_size\_8x8\_flag}$ is equal to 1), only the solid bold chroma edges are filtered. +- Otherwise ( $\text{ChromaArrayType}$ is equal to 0), no chroma edges are filtered. + +![Figure 8-10: Boundaries in a macroblock to be filtered. The diagram shows two 4x4 grids representing macroblocks. The left grid has vertical dashed lines between columns, labeled 'Vertical edges' with arrows pointing to them. The right grid has horizontal dashed lines between rows, labeled 'Horizontal edges' with arrows pointing to them. The text 'H.264(09)_F8-10' is at the bottom right of the right grid.](1b2e5b12ac4f5d7bb2fa18524982f2d8_img.jpg) + +Figure 8-10: Boundaries in a macroblock to be filtered. The diagram shows two 4x4 grids representing macroblocks. The left grid has vertical dashed lines between columns, labeled 'Vertical edges' with arrows pointing to them. The right grid has horizontal dashed lines between rows, labeled 'Horizontal edges' with arrows pointing to them. The text 'H.264(09)\_F8-10' is at the bottom right of the right grid. + +**Figure 8-10 – Boundaries in a macroblock to be filtered** + +For the current macroblock address $CurrMbAddr$ proceeding over values $0..PicSizeInMbs - 1$ , the following ordered steps are specified: + +1. The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to $mbAddrA$ and $mbAddrB$ . +2. The variables $fieldMbInFrameFlag$ , $filterInternalEdgesFlag$ , $filterLeftMbEdgeFlag$ and $filterTopMbEdgeFlag$ are derived as specified by the following ordered steps: + - a. The variable $fieldMbInFrameFlag$ is derived as follows: + - If $MbaffFrameFlag$ is equal to 1 and $mb\_field\_decoding\_flag$ is equal to 1, $fieldMbInFrameFlag$ is set equal to 1. + - Otherwise ( $MbaffFrameFlag$ is equal to 0 or $mb\_field\_decoding\_flag$ is equal to 0), $fieldMbInFrameFlag$ is set equal to 0. + - b. The variable $filterInternalEdgesFlag$ is derived as follows: + - If $disable\_deblocking\_filter\_idc$ for the slice that contains the macroblock $CurrMbAddr$ is equal to 1, the variable $filterInternalEdgesFlag$ is set equal to 0. + - Otherwise ( $disable\_deblocking\_filter\_idc$ for the slice that contains the macroblock $CurrMbAddr$ is not equal to 1), the variable $filterInternalEdgesFlag$ is set equal to 1. + - c. The variable $filterLeftMbEdgeFlag$ is derived as follows: + - If any of the following conditions are true, the variable $filterLeftMbEdgeFlag$ is set equal to 0: + - $MbaffFrameFlag$ is equal to 0 and $CurrMbAddr \% PicWidthInMbs$ is equal to 0, + - $MbaffFrameFlag$ is equal to 1 and $(CurrMbAddr \gg 1) \% PicWidthInMbs$ is equal to 0, + - $disable\_deblocking\_filter\_idc$ for the slice that contains the macroblock $CurrMbAddr$ is equal to 1, + - $disable\_deblocking\_filter\_idc$ for the slice that contains the macroblock $CurrMbAddr$ is equal to 2 and the macroblock $mbAddrA$ is not available. + - Otherwise, the variable $filterLeftMbEdgeFlag$ is set equal to 1. + - d. The variable $filterTopMbEdgeFlag$ is derived as follows: + - If any of the following conditions are true, the variable $filterTopMbEdgeFlag$ is set equal to 0: + - $MbaffFrameFlag$ is equal to 0 and $CurrMbAddr$ is less than $PicWidthInMbs$ , + - $MbaffFrameFlag$ is equal to 1, $(CurrMbAddr \gg 1)$ is less than $PicWidthInMbs$ , and the macroblock $CurrMbAddr$ is a field macroblock, + - $MbaffFrameFlag$ is equal to 1, $(CurrMbAddr \gg 1)$ is less than $PicWidthInMbs$ , the macroblock $CurrMbAddr$ is a frame macroblock, and $CurrMbAddr \% 2$ is equal to 0, + +- disable\_deblocking\_filter\_idc for the slice that contains the macroblock CurrMbAddr is equal to 1, + - disable\_deblocking\_filter\_idc for the slice that contains the macroblock CurrMbAddr is equal to 2 and the macroblock mbAddrB is not available. + - Otherwise, the variable filterTopMbEdgeFlag is set equal to 1. +3. Given the variables fieldMbInFrameFlag, filterInternalEdgesFlag, filterLeftMbEdgeFlag and filterTopMbEdgeFlag the deblocking filtering is controlled as follows: +- a. When filterLeftMbEdgeFlag is equal to 1, the left vertical luma edge is filtered by invoking the process specified in clause 8.7.1 with chromaEdgeFlag = 0, verticalEdgeFlag = 1, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(xE_k, yE_k) = (0, k)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - b. When filterInternalEdgesFlag is equal to 1, the filtering of the internal vertical luma edges is specified by the following ordered steps: + - i. When transform\_size\_8x8\_flag is equal to 0, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 0, verticalEdgeFlag = 1, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(xE_k, yE_k) = (4, k)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - ii. The process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 0, verticalEdgeFlag = 1, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(xE_k, yE_k) = (8, k)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - iii. When transform\_size\_8x8\_flag is equal to 0, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 0, verticalEdgeFlag = 1, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(xE_k, yE_k) = (12, k)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - c. When filterTopMbEdgeFlag is equal to 1, the filtering of the top horizontal luma edge is specified as follows: + - If MbaaffFrameFlag is equal to 1, $(CurrMbAddr \% 2)$ is equal to 0, CurrMbAddr is greater than or equal to $2 * PicWidthInMbs$ , the macroblock CurrMbAddr is a frame macroblock, and the macroblock $(CurrMbAddr - 2 * PicWidthInMbs + 1)$ is a field macroblock, the following ordered steps are specified: + - i. The process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 0, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = 1, and $(xE_k, yE_k) = (k, 0)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - ii. The process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 0, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = 1, and $(xE_k, yE_k) = (k, 1)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - Otherwise, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 0, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(xE_k, yE_k) = (k, 0)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - d. When filterInternalEdgesFlag is equal to 1, the filtering of the internal horizontal luma edges is specified by the following ordered steps: + - i. When transform\_size\_8x8\_flag is equal to 0, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 0, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(xE_k, yE_k) = (k, 4)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - ii. The process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 0, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(xE_k, yE_k) = (k, 8)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - iii. When transform\_size\_8x8\_flag is equal to 0, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 0, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(xE_k, yE_k) = (k, 12)$ with $k = 0..15$ as the inputs and $S'_L$ as the output. + - e. When ChromaArrayType is not equal to 0, for the filtering of both chroma components, with iCbCr = 0 for Cb and iCbCr = 1 for Cr, the following ordered steps are specified: + - i. When filterLeftMbEdgeFlag is equal to 1, the left vertical chroma edge is filtered by invoking the process specified in clause 8.7.1 with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 1, + +fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(x_{Ek}, y_{Ek}) = (0, k)$ with $k = 0..MbHeightC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. + +- ii. When filterInternalEdgesFlag is equal to 1, the filtering of the internal vertical chroma edge is specified by the following ordered steps: + - (1) When ChromaArrayType is not equal to 3 or transform\_size\_8x8\_flag is equal to 0, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 1, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(x_{Ek}, y_{Ek}) = (4, k)$ with $k = 0..MbHeightC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. + - (2) When ChromaArrayType is equal to 3, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 1, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(x_{Ek}, y_{Ek}) = (8, k)$ with $k = 0..MbHeightC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. + - (3) When ChromaArrayType is equal to 3 and transform\_size\_8x8\_flag is equal to 0, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 1, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(x_{Ek}, y_{Ek}) = (12, k)$ with $k = 0..MbHeightC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. +- iii. When filterTopMbEdgeFlag is equal to 1, the filtering of the top horizontal chroma edge is specified as follows: + - If MbuffFrameFlag is equal to 1, (CurrMbAddr % 2) is equal to 0, CurrMbAddr is greater than or equal to 2 \* PicWidthInMbs, the macroblock CurrMbAddr is a frame macroblock, and the macroblock (CurrMbAddr – 2 \* PicWidthInMbs + 1) is a field macroblock, the following ordered steps are specified: + - (1) The process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = 1, and $(x_{Ek}, y_{Ek}) = (k, 0)$ with $k = 0..MbWidthC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. + - (2) The process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = 1, and $(x_{Ek}, y_{Ek}) = (k, 1)$ with $k = 0..MbWidthC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. + - Otherwise, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(x_{Ek}, y_{Ek}) = (k, 0)$ with $k = 0..MbWidthC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. +- iv. When filterInternalEdgesFlag is equal to 1, the filtering of the internal horizontal chroma edge is specified by the following ordered steps: + - (1) When ChromaArrayType is not equal to 3 or transform\_size\_8x8\_flag is equal to 0, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(x_{Ek}, y_{Ek}) = (k, 4)$ with $k = 0..MbWidthC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. + - (2) When ChromaArrayType is not equal to 1, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(x_{Ek}, y_{Ek}) = (k, 8)$ with $k = 0..MbWidthC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. + - (3) When ChromaArrayType is equal to 2, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(x_{Ek}, y_{Ek}) = (k, 12)$ with $k = 0..MbWidthC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $C_b$ for $iCbCr = 0$ and $C$ being replaced by $C_r$ for $iCbCr = 1$ as the output. + - (4) When ChromaArrayType is equal to 3 and transform\_size\_8x8\_flag is equal to 0, the process specified in clause 8.7.1 is invoked with chromaEdgeFlag = 1, iCbCr, verticalEdgeFlag = 0, fieldModeInFrameFilteringFlag = fieldMbInFrameFlag, and $(x_{Ek}, y_{Ek}) = (k, 12)$ with + +$k = 0..MbWidthC - 1$ as the inputs and $S'_C$ with $C$ being replaced by $Cb$ for $iCbCr = 0$ and $C$ being replaced by $Cr$ for $iCbCr = 1$ as the output. + +NOTE 2 – When field mode filtering (fieldModeInFrameFilteringFlag is equal to 1) is applied across the top horizontal edges of a frame macroblock, this vertical filtering across the top or bottom macroblock boundary may involve some samples that extend across an internal block edge that is also filtered internally in frame mode. + +NOTE 3 – For example, in 4:2:0 chroma format when transform\_size\_8x8\_flag is equal to 0, the following applies. 3 horizontal luma edges, 1 horizontal chroma edge for $Cb$ , and 1 horizontal chroma edge for $Cr$ are filtered that are internal to a macroblock. When field mode filtering (fieldModeInFrameFilteringFlag is equal to 1) is applied to the top edges of a frame macroblock, 2 horizontal luma, 2 horizontal chroma edges for $Cb$ , and 2 horizontal chroma edges for $Cr$ between the frame macroblock and the above macroblock pair are filtered using field mode filtering, for a total of up to 5 horizontal luma edges, 3 horizontal chroma edges for $Cb$ , and 3 horizontal chroma edges for $Cr$ filtered that are considered to be controlled by the frame macroblock. In all other cases, at most 4 horizontal luma, 2 horizontal chroma edges for $Cb$ , and 2 horizontal chroma edges for $Cr$ are filtered that are considered to be controlled by a particular macroblock. + +Depending on separate\_colour\_plane\_flag the following applies: + +- If separate\_colour\_plane\_flag is equal to 0, the arrays $S'_L$ , $S'_{Cb}$ , $S'_{Cr}$ are assigned to the arrays $S_L$ , $S_{Cb}$ , $S_{Cr}$ (which represent the decoded picture), respectively. +- Otherwise (separate\_colour\_plane\_flag is equal to 1), the following applies: + - If colour\_plane\_id is equal to 0, the arrays $S'_L$ is assigned to the array $S_L$ (which represent the luma component of the decoded picture). + - Otherwise, if colour\_plane\_id is equal to 1, the arrays $S'_L$ is assigned to the array $S_{Cb}$ (which represents the $Cb$ component of the decoded picture). + - Otherwise (colour\_plane\_id is equal to 2), the arrays $S'_L$ is assigned to the array $S_{Cr}$ (which represents the $Cr$ component of the decoded picture). + +### 8.7.1 Filtering process for block edges + +Inputs to this process are chromaEdgeFlag, the chroma component index $iCbCr$ (when chromaEdgeFlag is equal to 1), verticalEdgeFlag, fieldModeInFrameFilteringFlag, and a set of $nE$ sample locations $(xE_k, yE_k)$ , with $k = 0..nE - 1$ , expressed relative to the upper left corner of the macroblock CurrMbAddr. The set of sample locations $(xE_k, yE_k)$ represent the sample locations immediately to the right of a vertical edge (when verticalEdgeFlag is equal to 1) or immediately below a horizontal edge (when verticalEdgeFlag is equal to 0). + +The variable $nE$ is derived as follows: + +- If chromaEdgeFlag is equal to 0, $nE$ is set equal to 16. +- Otherwise (chromaEdgeFlag is equal to 1), $nE$ is set equal to $(\text{verticalEdgeFlag} == 1) ? \text{MbHeightC} : \text{MbWidthC}$ . + +Let $s'$ be a variable specifying a luma or chroma sample array. $s'$ is derived as follows: + +- If chromaEdgeFlag is equal to 0, $s'$ represents the luma sample array $S'_L$ of the current picture. +- Otherwise, if chromaEdgeFlag is equal to 1 and $iCbCr$ is equal to 0, $s'$ represents the chroma sample array $S'_{Cb}$ of the chroma component $Cb$ of the current picture. +- Otherwise (chromaEdgeFlag is equal to 1 and $iCbCr$ is equal to 1), $s'$ represents the chroma sample array $S'_{Cr}$ of the chroma component $Cr$ of the current picture. + +The variable $dy$ is set equal to $(1 + \text{fieldModeInFrameFilteringFlag})$ . + +The position of the upper-left luma sample of the macroblock CurrMbAddr is derived by invoking the inverse macroblock scanning process in clause 6.4.1 with $\text{mbAddr} = \text{CurrMbAddr}$ as input and the output being assigned to $(xI, yI)$ . + +The variables $xP$ and $yP$ are derived as follows: + +- If chromaEdgeFlag is equal to 0, $xP$ is set equal to $xI$ and $yP$ is set equal to $yI$ . +- Otherwise (chromaEdgeFlag is equal to 1), $xP$ is set equal to $xI / \text{SubWidthC}$ and $yP$ is set equal to $(yI + \text{SubHeightC} - 1) / \text{SubHeightC}$ . + +| | | | | | | | | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| p 3 | p 2 | p 1 | p 0 | q 0 | q 1 | q 2 | q 3 | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| + +**Figure 8-11 – Convention for describing samples across a 4x4 block horizontal or vertical boundary** + +For each sample location ( $x_{E_k}, y_{E_k}$ ), $k = 0..(n_E - 1)$ , the following ordered steps are specified: + +1. The filtering process is applied to a set of eight samples across a 4x4 block horizontal or vertical edge denoted as $p_i$ and $q_i$ with $i = 0..3$ as shown in Figure 8-11 with the edge lying between $p_0$ and $q_0$ . $p_i$ and $q_i$ with $i = 0..3$ are specified as follows: + +– If $verticalEdgeFlag$ is equal to 1, + +$$q_i = s'[ x_P + x_{E_k} + i, y_P + dy * y_{E_k} ] \quad (8-442)$$ + +$$p_i = s'[ x_P + x_{E_k} - i - 1, y_P + dy * y_{E_k} ] \quad (8-443)$$ + +– Otherwise ( $verticalEdgeFlag$ is equal to 0), + +$$q_i = s'[ x_P + x_{E_k}, y_P + dy * ( y_{E_k} + i ) - ( y_{E_k} \% 2 ) ] \quad (8-444)$$ + +$$p_i = s'[ x_P + x_{E_k}, y_P + dy * ( y_{E_k} - i - 1 ) - ( y_{E_k} \% 2 ) ] \quad (8-445)$$ + +2. The process specified in clause 8.7.2 is invoked with the sample values $p_i$ and $q_i$ ( $i = 0..3$ ), $chromaEdgeFlag$ , and $verticalEdgeFlag$ as the inputs, and the output is assigned to the filtered result sample values $p'_i$ and $q'_i$ with $i = 0..2$ . + +3. The input sample values $p_i$ and $q_i$ with $i = 0..2$ are replaced by the corresponding filtered result sample values $p'_i$ and $q'_i$ with $i = 0..2$ inside the sample array $s'$ as follows: + +– If $verticalEdgeFlag$ is equal to 1, + +$$s'[ x_P + x_{E_k} + i, y_P + dy * y_{E_k} ] = q'_i \quad (8-446)$$ + +$$s'[ x_P + x_{E_k} - i - 1, y_P + dy * y_{E_k} ] = p'_i \quad (8-447)$$ + +– Otherwise ( $verticalEdgeFlag$ is equal to 0), + +$$s'[ x_P + x_{E_k}, y_P + dy * ( y_{E_k} + i ) - ( y_{E_k} \% 2 ) ] = q'_i \quad (8-448)$$ + +$$s'[ x_P + x_{E_k}, y_P + dy * ( y_{E_k} - i - 1 ) - ( y_{E_k} \% 2 ) ] = p'_i \quad (8-449)$$ + +### 8.7.2 Filtering process for a set of samples across a horizontal or vertical block edge + +Inputs to this process are the input sample values $p_i$ and $q_i$ with $i$ in the range of 0..3 of a single set of samples across an edge that is to be filtered, $chromaEdgeFlag$ , and $verticalEdgeFlag$ . + +Outputs of this process are the filtered result sample values $p'_i$ and $q'_i$ with $i$ in the range of 0..2. + +The content dependent boundary filtering strength variable $bS$ is derived as follows: + +- If $chromaEdgeFlag$ is equal to 0, the derivation process for the content dependent boundary filtering strength specified in clause 8.7.2.1 is invoked with $p_0$ , $q_0$ , and $verticalEdgeFlag$ as input, and the output is assigned to $bS$ . +- Otherwise ( $chromaEdgeFlag$ is equal to 1), the $bS$ used for filtering a set of samples of a horizontal or vertical chroma edge is set equal to the value of $bS$ for filtering the set of samples of a horizontal or vertical luma edge, respectively, that contains the luma sample at location ( $SubWidthC * x, SubHeightC * y$ ) inside the luma array of the same field, where ( $x, y$ ) is the location of the chroma sample $q_0$ inside the chroma array for that field. + +Let $filterOffsetA$ and $filterOffsetB$ be the values of $FilterOffsetA$ and $FilterOffsetB$ as specified in clause 7.4.3 for the slice that contains the macroblock containing sample $q_0$ . + +Let $qP_p$ and $qP_q$ be variables specifying quantization parameter values for the macroblocks containing the samples $p_0$ and $q_0$ , respectively. The variables $qP_z$ (with $z$ being replaced by $p$ or $q$ ) are derived as follows: + +- If $chromaEdgeFlag$ is equal to 0, the following applies: + +- If the macroblock containing the sample $z_0$ is an I\_PCM macroblock, $qP_z$ is set to 0. +- Otherwise (the macroblock containing the sample $z_0$ is not an I\_PCM macroblock), $qP_z$ is set to the value of $QP_Y$ of the macroblock containing the sample $z_0$ . +- Otherwise (chromaEdgeFlag is equal to 1), the following applies: + - If the macroblock containing the sample $z_0$ is an I\_PCM macroblock, $qP_z$ is set equal to the value of $QP_C$ that corresponds to a value of 0 for $QP_Y$ as specified in clause 8.5.8. + - Otherwise (the macroblock containing the sample $z_0$ is not an I\_PCM macroblock), $qP_z$ is set equal to the value of $QP_C$ that corresponds to the value $QP_Y$ of the macroblock containing the sample $z_0$ as specified in clause 8.5.8. + +The process specified in clause 8.7.2.2 is invoked with $p_0$ , $q_0$ , $p_1$ , $q_1$ , chromaEdgeFlag, bS, filterOffsetA, filterOffsetB, $qP_p$ , and $qP_q$ as inputs, and the outputs are assigned to filterSamplesFlag, indexA, $\alpha$ , and $\beta$ . + +The variable chromaStyleFilteringFlag is set by + +$$\text{chromaStyleFilteringFlag} = \text{chromaEdgeFlag} \&\& ( \text{ChromaArrayType} \neq 3 ) \quad (8-450)$$ + +Depending on the variable filterSamplesFlag, the following applies: + +- If filterSamplesFlag is equal to 1, the following applies: + - If bS is less than 4, the process specified in clause 8.7.2.3 is invoked with $p_i$ and $q_i$ ( $i = 0..2$ ), chromaEdgeFlag, chromaStyleFilteringFlag, bS, $\beta$ , and indexA given as input, and the output is assigned to $p'_i$ and $q'_i$ ( $i = 0..2$ ). + - Otherwise (bS is equal to 4), the process specified in clause 8.7.2.4 is invoked with $p_i$ and $q_i$ ( $i = 0..3$ ), chromaEdgeFlag, chromaStyleFilteringFlag, $\alpha$ , and $\beta$ given as input, and the output is assigned to $p'_i$ and $q'_i$ ( $i = 0..2$ ). +- Otherwise (filterSamplesFlag is equal to 0), the filtered result samples $p'_i$ and $q'_i$ ( $i = 0..2$ ) are replaced by the corresponding input samples $p_i$ and $q_i$ : + +$$\text{for } i = 0..2, \quad p'_i = p_i \quad (8-451)$$ + +$$\text{for } i = 0..2, \quad q'_i = q_i \quad (8-452)$$ + +### 8.7.2.1 Derivation process for the luma content dependent boundary filtering strength + +Inputs to this process are the input sample values $p_0$ and $q_0$ of a single set of samples across an edge that is to be filtered and verticalEdgeFlag. + +Output of this process is the variable bS. + +Let the variable mixedModeEdgeFlag be derived as follows: + +- If MbuffFrameFlag is equal to 1 and the samples $p_0$ and $q_0$ are in different macroblock pairs, one of which is a field macroblock pair and the other is a frame macroblock pair, mixedModeEdgeFlag is set equal to 1. +- Otherwise, mixedModeEdgeFlag is set equal to 0. + +The variable bS is derived as follows: + +- If the block edge is also a macroblock edge and any of the following conditions are true, a value of bS equal to 4 is the output: + - the samples $p_0$ and $q_0$ are both in frame macroblocks and either or both of the samples $p_0$ or $q_0$ is in a macroblock coded using an Intra macroblock prediction mode, + - the samples $p_0$ and $q_0$ are both in frame macroblocks and either or both of the samples $p_0$ or $q_0$ is in a macroblock that is in a slice with slice\_type equal to SP or SI, + - MbuffFrameFlag is equal to 1 or field\_pic\_flag is equal to 1, and verticalEdgeFlag is equal to 1, and either or both of the samples $p_0$ or $q_0$ is in a macroblock coded using an Intra macroblock prediction mode, + - MbuffFrameFlag is equal to 1 or field\_pic\_flag is equal to 1, and verticalEdgeFlag is equal to 1, and either or both of the samples $p_0$ or $q_0$ is in a macroblock that is in a slice with slice\_type equal to SP or SI. + +- Otherwise, if any of the following conditions are true, a value of bS equal to 3 is the output: + - mixedModeEdgeFlag is equal to 0 and either or both of the samples $p_0$ or $q_0$ is in a macroblock coded using an Intra macroblock prediction mode, + - mixedModeEdgeFlag is equal to 0 and either or both of the samples $p_0$ or $q_0$ is in a macroblock that is in a slice with slice\_type equal to SP or SI, + - mixedModeEdgeFlag is equal to 1, verticalEdgeFlag is equal to 0, and either or both of the samples $p_0$ or $q_0$ is in a macroblock coded using an Intra macroblock prediction mode, + - mixedModeEdgeFlag is equal to 1, verticalEdgeFlag is equal to 0, and either or both of the samples $p_0$ or $q_0$ is in a macroblock that is in a slice with slice\_type equal to SP or SI. +- Otherwise, if any of the following conditions are true, a value of bS equal to 2 is the output: + - transform\_size\_8x8\_flag is equal to 1 for the macroblock containing the sample $p_0$ and the 8x8 luma transform block associated with the 8x8 luma block containing the sample $p_0$ contains non-zero transform coefficient levels, + - transform\_size\_8x8\_flag is equal to 0 for the macroblock containing the sample $p_0$ and the 4x4 luma transform block associated with the 4x4 luma block containing the sample $p_0$ contains non-zero transform coefficient levels, + - transform\_size\_8x8\_flag is equal to 1 for the macroblock containing the sample $q_0$ and the 8x8 luma transform block associated with the 8x8 luma block containing the sample $q_0$ contains non-zero transform coefficient levels, + - transform\_size\_8x8\_flag is equal to 0 for the macroblock containing the sample $q_0$ and the 4x4 luma transform block associated with the 4x4 luma block containing the sample $q_0$ contains non-zero transform coefficient levels. +- Otherwise, if any of the following conditions are true, a value of bS equal to 1 is the output: + - mixedModeEdgeFlag is equal to 1, + - mixedModeEdgeFlag is equal to 0 and for the prediction of the macroblock/sub-macroblock partition containing the sample $p_0$ different reference pictures or a different number of motion vectors are used than for the prediction of the macroblock/sub-macroblock partition containing the sample $q_0$ , + + +NOTE 1 – The determination of whether the reference pictures used for the two macroblock/sub-macroblock partitions are the same or different is based only on which pictures are referenced, without regard to whether a prediction is formed using an index into reference picture list 0 or an index into reference picture list 1, and also without regard to whether the index position within a reference picture list is different. + +NOTE 2 – The number of motion vectors that are used for the prediction of a macroblock partition with macroblock partition index mbPartIdx, or a sub-macroblock partition contained in this macroblock partition, is equal to PredFlagL0[ mbPartIdx ] + PredFlagL1[ mbPartIdx ]. + - mixedModeEdgeFlag is equal to 0 and one motion vector is used to predict the macroblock/sub-macroblock partition containing the sample $p_0$ and one motion vector is used to predict the macroblock/sub-macroblock partition containing the sample $q_0$ and the absolute difference between the horizontal or vertical components of the motion vectors used is greater than or equal to 4 in units of quarter luma frame samples, + - mixedModeEdgeFlag is equal to 0 and two motion vectors and two different reference pictures are used to predict the macroblock/sub-macroblock partition containing the sample $p_0$ and two motion vectors for the same two reference pictures are used to predict the macroblock/sub-macroblock partition containing the sample $q_0$ and, for either or both of the two used reference pictures, the absolute difference between the horizontal or vertical components of the two motion vectors used in the prediction of the two macroblock/sub-macroblock partitions for the particular reference picture is greater than or equal to 4 in units of quarter luma frame samples, + - mixedModeEdgeFlag is equal to 0 and two motion vectors for the same reference picture are used to predict the macroblock/sub-macroblock partition containing the sample $p_0$ and two motion vectors for the same reference picture are used to predict the macroblock/sub-macroblock partition containing the sample $q_0$ and both of the following conditions are true: + - The absolute difference between the horizontal or vertical components of list 0 motion vectors used in the prediction of the two macroblock/sub-macroblock partitions is greater than or equal to 4 in quarter luma frame samples or the absolute difference between the horizontal or vertical components of the list 1 motion vectors used in the prediction of the two macroblock/sub-macroblock partitions is greater than or equal to 4 in units of quarter luma frame samples, + +- The absolute difference between the horizontal or vertical components of list 0 motion vector used in the prediction of the macroblock/sub-macroblock partition containing the sample $p_0$ and the list 1 motion vector used in the prediction of the macroblock/sub-macroblock partition containing the sample $q_0$ is greater than or equal to 4 in units of quarter luma frame samples or the absolute difference between the horizontal or vertical components of the list 1 motion vector used in the prediction of the macroblock/sub-macroblock partition containing the sample $p_0$ and list 0 motion vector used in the prediction of the macroblock/sub-macroblock partition containing the sample $q_0$ is greater than or equal to 4 in units of quarter luma frame samples. + +NOTE 3 – A vertical difference of 4 in units of quarter luma frame samples is a difference of 2 in units of quarter luma field samples. + +- Otherwise, a value of bS equal to 0 is the output. + +### 8.7.2.2 Derivation process for the thresholds for each block edge + +Inputs to this process are: + +- the input sample values $p_0$ , $q_0$ , $p_1$ and $q_1$ of a single set of samples across an edge that is to be filtered, +- the variables chromaEdgeFlag and bS, for the set of input samples, as specified in clause 8.7.2, +- the variables filterOffsetA, filterOffsetB, $qP_p$ , and $qP_q$ . + +Outputs of this process are the variable filterSamplesFlag, which indicates whether the input samples are filtered, the value of indexA, and the values of the threshold variables $\alpha$ and $\beta$ . + +Let $qP_{av}$ be a variable specifying an average quantization parameter. It is derived as: + +$$qP_{av} = ( qP_p + qP_q + 1 ) \gg 1 \quad (8-453)$$ + +NOTE – In SP and SI slices, $qP_{av}$ is derived in the same way as in other slice types. $QS_V$ from Equation 7-33 is not used in the deblocking filter. + +Let indexA be a variable that is used to access the $\alpha$ table (Table 8-16) as well as the $t_{C0}$ table (Table 8-17), which is used in filtering of edges with bS less than 4 as specified in clause 8.7.2.3, and let indexB be a variable that is used to access the $\beta$ table (Table 8-16). The variables indexA and indexB are derived as: + +$$indexA = \text{Clip3}( 0, 51, qP_{av} + \text{filterOffsetA} ) \quad (8-454)$$ + +$$indexB = \text{Clip3}( 0, 51, qP_{av} + \text{filterOffsetB} ) \quad (8-455)$$ + +The variables $\alpha'$ and $\beta'$ depending on the values of indexA and indexB are specified in Table 8-16. Depending on chromaEdgeFlag, the corresponding threshold variables $\alpha$ and $\beta$ are derived as follows: + +- If chromaEdgeFlag is equal to 0, + +$$\alpha = \alpha' * ( 1 \ll ( \text{BitDepth}_Y - 8 ) ) \quad (8-456)$$ + +$$\beta = \beta' * ( 1 \ll ( \text{BitDepth}_Y - 8 ) ) \quad (8-457)$$ + +- Otherwise (chromaEdgeFlag is equal to 1), + +$$\alpha = \alpha' * ( 1 \ll ( \text{BitDepth}_C - 8 ) ) \quad (8-458)$$ + +$$\beta = \beta' * ( 1 \ll ( \text{BitDepth}_C - 8 ) ) \quad (8-459)$$ + +The variable filterSamplesFlag is derived by: + +$$\text{filterSamplesFlag} = ( \text{bS} \neq 0 \ \&\& \ \text{Abs}( p_0 - q_0 ) < \alpha \ \&\& \ \text{Abs}( p_1 - p_0 ) < \beta \ \&\& \ \text{Abs}( q_1 - q_0 ) < \beta ) \quad (8-460)$$ + +**Table 8-16 – Derivation of offset dependent threshold variables $\alpha'$ and $\beta'$ from indexA and indexB** + +| | indexA (for $\alpha'$ ) or indexB (for $\beta'$ ) | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------|---------------------------------------------------|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | +| $\alpha'$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 12 | 13 | | +| $\beta'$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 3 | 3 | 3 | 3 | 4 | 4 | 4 | | + +**Table 8-16 (concluded) – Derivation of indexA and indexB from offset dependent threshold variables $\alpha'$ and $\beta'$** + +| | indexA (for $\alpha'$ ) or indexB (for $\beta'$ ) | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------|---------------------------------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | +| $\alpha'$ | 15 | 17 | 20 | 22 | 25 | 28 | 32 | 36 | 40 | 45 | 50 | 56 | 63 | 71 | 80 | 90 | 101 | 113 | 127 | 144 | 162 | 182 | 203 | 226 | 255 | 255 | +| $\beta'$ | 6 | 6 | 7 | 7 | 8 | 8 | 9 | 9 | 10 | 10 | 11 | 11 | 12 | 12 | 13 | 13 | 14 | 14 | 15 | 15 | 16 | 16 | 17 | 17 | 18 | 18 | + +**8.7.2.3 Filtering process for edges with bS less than 4** + +Inputs to this process are the input sample values $p_i$ and $q_i$ ( $i = 0..2$ ) of a single set of samples across an edge that is to be filtered, chromaEdgeFlag, chromaStyleFilteringFlag, bS, $\beta$ , and indexA, for the set of input samples, as specified in clause 8.7.2. + +Outputs of this process are the filtered result sample values $p'_i$ and $q'_i$ ( $i = 0..2$ ) for the set of input sample values. + +Depending on the values of indexA and bS, the variable $t'_{c0}$ is specified in Table 8-17. Depending on chromaEdgeFlag, the corresponding threshold variable $t_{c0}$ is derived as follows: + +- If chromaEdgeFlag is equal to 0, + +$$t_{c0} = t'_{c0} * (1 \ll ( \text{BitDepth}_Y - 8 )) \tag{8-461}$$ + +- Otherwise (chromaEdgeFlag is equal to 1), + +$$t_{c0} = t'_{c0} * (1 \ll ( \text{BitDepth}_C - 8 )) \tag{8-462}$$ + +**Table 8-17 – Value of variable $t'_{c0}$ as a function of indexA and bS** + +| | indexA | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------|--------|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | +| bS = 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | +| bS = 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | +| bS = 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | + +**Table 8-17 (concluded) – Value of variable $t'_{c0}$ as a function of indexA and bS** + +| | indexA | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------|--------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | +| bS = 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 9 | 10 | 11 | 13 | +| bS = 2 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 5 | 5 | 6 | 7 | 8 | 8 | 10 | 11 | 12 | 13 | 15 | 17 | +| bS = 3 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 9 | 10 | 11 | 13 | 14 | 16 | 18 | 20 | 23 | 25 | + +The threshold variables $a_p$ and $a_q$ are derived by: + +$$a_p = \text{Abs}(p_2 - p_0) \quad (8-463)$$ + +$$a_q = \text{Abs}(q_2 - q_0) \quad (8-464)$$ + +The threshold variable $t_c$ is determined as follows: + +- If $\text{chromaStyleFilteringFlag}$ is equal to 0, + +$$t_c = t_{c0} + ((a_p < \beta) ? 1 : 0) + ((a_q < \beta) ? 1 : 0) \quad (8-465)$$ + +- Otherwise ( $\text{chromaStyleFilteringFlag}$ is equal to 1), + +$$t_c = t_{c0} + 1 \quad (8-466)$$ + +Let $\text{Clip1}()$ be a function that is replaced by $\text{Clip1}_V()$ when $\text{chromaEdgeFlag}$ is equal to 0 and by $\text{Clip1}_C()$ when $\text{chromaEdgeFlag}$ is equal to 1. + +The filtered result samples $p'_0$ and $q'_0$ are derived by: + +$$\Delta = \text{Clip3}(-t_c, t_c, (((q_0 - p_0) \ll 2) + (p_1 - q_1) + 4) \gg 3)) \quad (8-467)$$ + +$$p'_0 = \text{Clip1}(p_0 + \Delta) \quad (8-468)$$ + +$$q'_0 = \text{Clip1}(q_0 - \Delta) \quad (8-469)$$ + +The filtered result sample $p'_1$ is derived as follows: + +- If $\text{chromaStyleFilteringFlag}$ is equal to 0 and $a_p$ is less than $\beta$ , + +$$p'_1 = p_1 + \text{Clip3}(-t_{c0}, t_{c0}, (p_2 + ((p_0 + q_0 + 1) \gg 1) - (p_1 \ll 1)) \gg 1) \quad (8-470)$$ + +- Otherwise ( $\text{chromaStyleFilteringFlag}$ is equal to 1 or $a_p$ is greater than or equal to $\beta$ ), + +$$p'_1 = p_1 \quad (8-471)$$ + +The filtered result sample $q'_1$ is derived as follows: + +- If $\text{chromaStyleFilteringFlag}$ is equal to 0 and $a_q$ is less than $\beta$ , + +$$q'_1 = q_1 + \text{Clip3}(-t_{c0}, t_{c0}, (q_2 + ((p_0 + q_0 + 1) \gg 1) - (q_1 \ll 1)) \gg 1) \quad (8-472)$$ + +- Otherwise ( $\text{chromaStyleFilteringFlag}$ is equal to 1 or $a_q$ is greater than or equal to $\beta$ ), + +$$q'_1 = q_1 \quad (8-473)$$ + +The filtered result samples $p'_2$ and $q'_2$ are always set equal to the input samples $p_2$ and $q_2$ : + +$$p'_2 = p_2 \quad (8-474)$$ + +$$q'_2 = q_2 \quad (8-475)$$ + +#### 8.7.2.4 Filtering process for edges for bS equal to 4 + +Inputs to this process are the input sample values $p_i$ and $q_i$ ( $i = 0..3$ ) of a single set of samples across an edge that is to be filtered, $\text{chromaEdgeFlag}$ , $\text{chromaStyleFilteringFlag}$ , and the values of the threshold variables $\alpha$ and $\beta$ for the set of samples, as specified in clause 8.7.2. + +Outputs of this process are the filtered result sample values $p'_i$ and $q'_i$ ( $i = 0..2$ ) for the set of input sample values. + +Let $a_p$ and $a_q$ be two threshold variables as specified in Equations 8-463 and 8-464, respectively, in clause 8.7.2.3. + +The filtered result samples $p'_i$ ( $i = 0..2$ ) are derived as follows: + +- If $\text{chromaStyleFilteringFlag}$ is equal to 0 and the following condition holds, + +$$a_p < \beta \ \&\& \ \text{Abs}(p_0 - q_0) < ((\alpha \gg 2) + 2) \quad (8-476)$$ + +then the variables $p'_0$ , $p'_1$ , and $p'_2$ are derived by: + +$$p'_0 = ( p_2 + 2*p_1 + 2*p_0 + 2*q_0 + q_1 + 4 ) \gg 3 \quad (8-477)$$ + +$$p'_1 = ( p_2 + p_1 + p_0 + q_0 + 2 ) \gg 2 \quad (8-478)$$ + +$$p'_2 = ( 2*p_3 + 3*p_2 + p_1 + p_0 + q_0 + 4 ) \gg 3 \quad (8-479)$$ + +- Otherwise (chromaStyleFilteringFlag is equal to 1 or the condition in Equation 8-476 does not hold), the variables $p'_0$ , $p'_1$ , and $p'_2$ are derived by: + +$$p'_0 = ( 2*p_1 + p_0 + q_1 + 2 ) \gg 2 \quad (8-480)$$ + +$$p'_1 = p_1 \quad (8-481)$$ + +$$p'_2 = p_2 \quad (8-482)$$ + +The filtered result samples $q'_i$ ( $i = 0..2$ ) are derived as follows: + +- If chromaStyleFilteringFlag is equal to 0 and the following condition holds, + +$$a_q < \beta \ \&\& \ \text{Abs}( p_0 - q_0 ) < ( ( \alpha \gg 2 ) + 2 ) \quad (8-483)$$ + +then the variables $q'_0$ , $q'_1$ , and $q'_2$ are derived by + +$$q'_0 = ( p_1 + 2*p_0 + 2*q_0 + 2*q_1 + q_2 + 4 ) \gg 3 \quad (8-484)$$ + +$$q'_1 = ( p_0 + q_0 + q_1 + q_2 + 2 ) \gg 2 \quad (8-485)$$ + +$$q'_2 = ( 2*q_3 + 3*q_2 + q_1 + q_0 + p_0 + 4 ) \gg 3 \quad (8-486)$$ + +- Otherwise (chromaStyleFilteringFlag is equal to 1 or the condition in Equation 8-483 does not hold), the variables $q'_0$ , $q'_1$ , and $q'_2$ are derived by: + +$$q'_0 = ( 2*q_1 + q_0 + p_1 + 2 ) \gg 2 \quad (8-487)$$ + +$$q'_1 = q_1 \quad (8-488)$$ + +$$q'_2 = q_2 \quad (8-489)$$ + +## 9 Parsing process + +Inputs to this process are bits from the RBSP. + +Outputs of this process are syntax element values. + +This process is invoked when the descriptor of a syntax element in the syntax tables in clause 7.3 is equal to ue(v), me(v), se(v), te(v) (see clause 9.1), ce(v) (see clause 9.2), or ae(v) (see clause 9.3). + +### 9.1 Parsing process for Exp-Golomb codes + +This process is invoked when the descriptor of a syntax element in the syntax tables in clause 7.3 is equal to ue(v), me(v), se(v), or te(v). For syntax elements in clauses 7.3.4 and 7.3.5, this process is invoked only when entropy\_coding\_mode\_flag is equal to 0. + +Inputs to this process are bits from the RBSP. + +Outputs of this process are syntax element values. + +Syntax elements coded as ue(v), me(v), or se(v) are Exp-Golomb-coded. Syntax elements coded as te(v) are truncated Exp-Golomb-coded. The parsing process for these syntax elements begins with reading the bits starting at the current location in the bitstream up to and including the first non-zero bit, and counting the number of leading bits that are equal to 0. This process is specified as follows: + +``` + +leadingZeroBits = -1 +for ( b = 0; !b; leadingZeroBits++ ) + b = read_bits( 1 ) + +``` + +$$(9-1)$$ + +The variable codeNum is then assigned as follows: + +$$\text{codeNum} = 2^{\text{leadingZeroBits}} - 1 + \text{read\_bits}(\text{leadingZeroBits}) \quad (9-2)$$ + +where the value returned from $\text{read\_bits}(\text{leadingZeroBits})$ is interpreted as a binary representation of an unsigned integer with most significant bit written first. + +Table 9-1 illustrates the structure of the Exp-Golomb code by separating the bit string into "prefix" and "suffix" bits. The "prefix" bits are those bits that are parsed in the above pseudo-code for the computation of $\text{leadingZeroBits}$ , and are shown as either 0 or 1 in the bit string column of Table 9-1. The "suffix" bits are those bits that are parsed in the computation of $\text{codeNum}$ and are shown as $x_i$ in Table 9-1, with $i$ being in the range 0 to $\text{leadingZeroBits} - 1$ , inclusive. Each $x_i$ can take on values 0 or 1. + +**Table 9-1 – Bit strings with "prefix" and "suffix" bits and assignment to codeNum ranges (informative)** + +| Bit string form | Range of codeNum | +|-----------------------------------|------------------| +| 1 | 0 | +| 0 1 $x_0$ | 1..2 | +| 0 0 1 $x_1 x_0$ | 3..6 | +| 0 0 0 1 $x_2 x_1 x_0$ | 7..14 | +| 0 0 0 0 1 $x_3 x_2 x_1 x_0$ | 15..30 | +| 0 0 0 0 0 1 $x_4 x_3 x_2 x_1 x_0$ | 31..62 | +| ... | ... | + +Table 9-2 illustrates explicitly the assignment of bit strings to codeNum values. + +**Table 9-2 – Exp-Golomb bit strings and codeNum in explicit form and used as ue(v) (informative)** + +| Bit string | codeNum | +|---------------|---------| +| 1 | 0 | +| 0 1 0 | 1 | +| 0 1 1 | 2 | +| 0 0 1 0 0 | 3 | +| 0 0 1 0 1 | 4 | +| 0 0 1 1 0 | 5 | +| 0 0 1 1 1 | 6 | +| 0 0 0 1 0 0 0 | 7 | +| 0 0 0 1 0 0 1 | 8 | +| 0 0 0 1 0 1 0 | 9 | +| ... | ... | + +Depending on the descriptor, the value of a syntax element is derived as follows: + +- If the syntax element is coded as $\text{ue}(v)$ , the value of the syntax element is equal to $\text{codeNum}$ . +- Otherwise, if the syntax element is coded as $\text{se}(v)$ , the value of the syntax element is derived by invoking the mapping process for signed Exp-Golomb codes as specified in clause 9.1.1 with $\text{codeNum}$ as the input. + +- Otherwise, if the syntax element is coded as $me(v)$ , the value of the syntax element is derived by invoking the mapping process for coded block pattern as specified in clause 9.1.2 with $codeNum$ as the input. +- Otherwise (the syntax element is coded as $te(v)$ ), the range of possible values for the syntax element is determined first. The range of this syntax element may be between 0 and $x$ , with $x$ being greater than or equal to 1 and the range is used in the derivation of the value of the syntax element value as follows: + - If $x$ is greater than 1, $codeNum$ and the value of the syntax element is derived in the same way as for syntax elements coded as $ue(v)$ . + - Otherwise ( $x$ is equal to 1), the parsing process for $codeNum$ which is equal to the value of the syntax element is given by a process equivalent to: + +$$\begin{aligned} b &= \text{read\_bits}( 1 ) \\ codeNum &= !b \end{aligned} \tag{9-3}$$ + +### 9.1.1 Mapping process for signed Exp-Golomb codes + +Input to this process is $codeNum$ as specified in clause 9.1. + +Output of this process is a value of a syntax element coded as $se(v)$ . + +The syntax element is assigned to the $codeNum$ by ordering the syntax element by its absolute value in increasing order and representing the positive value for a given absolute value with the lower $codeNum$ . Table 9-3 provides the assignment rule. + +**Table 9-3 – Assignment of syntax element to $codeNum$ for signed Exp-Golomb coded syntax elements $se(v)$** + +| codeNum | syntax element value | +|-----------------------------|------------------------------------| +| 0 | 0 | +| 1 | 1 | +| 2 | -1 | +| 3 | 2 | +| 4 | -2 | +| 5 | 3 | +| 6 | -3 | +| $k$ | $(-1)^{k+1} \text{Ceil}(k \div 2)$ | + +### 9.1.2 Mapping process for coded block pattern + +Input to this process is $codeNum$ as specified in clause 9.1. + +Output of this process is a value of the syntax element $coded\_block\_pattern$ coded as $me(v)$ . + +Table 9-4 shows the assignment of $coded\_block\_pattern$ to $codeNum$ depending on whether the macroblock prediction mode is equal to $Intra\_4x4$ , $Intra\_8x8$ or $Inter$ . + +**Table 9-4 – Assignment of codeNum to values of coded\_block\_pattern for macroblock prediction modes** + +**(a) ChromaArrayType is equal to 1 or 2** + +| codeNum | coded_block_pattern | | +|---------|----------------------|-------| +| | Intra_4x4, Intra_8x8 | Inter | +| 0 | 47 | 0 | +| 1 | 31 | 16 | +| 2 | 15 | 1 | +| 3 | 0 | 2 | +| 4 | 23 | 4 | +| 5 | 27 | 8 | +| 6 | 29 | 32 | +| 7 | 30 | 3 | +| 8 | 7 | 5 | +| 9 | 11 | 10 | +| 10 | 13 | 12 | +| 11 | 14 | 15 | +| 12 | 39 | 47 | +| 13 | 43 | 7 | +| 14 | 45 | 11 | +| 15 | 46 | 13 | +| 16 | 16 | 14 | +| 17 | 3 | 6 | +| 18 | 5 | 9 | +| 19 | 10 | 31 | +| 20 | 12 | 35 | +| 21 | 19 | 37 | +| 22 | 21 | 42 | +| 23 | 26 | 44 | +| 24 | 28 | 33 | +| 25 | 35 | 34 | +| 26 | 37 | 36 | +| 27 | 42 | 40 | +| 28 | 44 | 39 | +| 29 | 1 | 43 | +| 30 | 2 | 45 | + +**(a) ChromaArrayType is equal to 1 or 2** + +| codeNum | coded_block_pattern | | +|---------|----------------------|-------| +| | Intra_4x4, Intra_8x8 | Inter | +| 31 | 4 | 46 | +| 32 | 8 | 17 | +| 33 | 17 | 18 | +| 34 | 18 | 20 | +| 35 | 20 | 24 | +| 36 | 24 | 19 | +| 37 | 6 | 21 | +| 38 | 9 | 26 | +| 39 | 22 | 28 | +| 40 | 25 | 23 | +| 41 | 32 | 27 | +| 42 | 33 | 29 | +| 43 | 34 | 30 | +| 44 | 36 | 22 | +| 45 | 40 | 25 | +| 46 | 38 | 38 | +| 47 | 41 | 41 | + +**(b) ChromaArrayType is equal to 0 or 3** + +| codeNum | coded_block_pattern | | +|---------|----------------------|-------| +| | Intra_4x4, Intra_8x8 | Inter | +| 0 | 15 | 0 | +| 1 | 0 | 1 | +| 2 | 7 | 2 | +| 3 | 11 | 4 | +| 4 | 13 | 8 | +| 5 | 14 | 3 | +| 6 | 3 | 5 | +| 7 | 5 | 10 | +| 8 | 10 | 12 | +| 9 | 12 | 15 | + +**(b) ChromaArrayType is equal to 0 or 3** + +| codeNum | coded_block_pattern | | +|---------|----------------------|-------| +| | Intra_4x4, Intra_8x8 | Inter | +| 10 | 1 | 7 | +| 11 | 2 | 11 | +| 12 | 4 | 13 | +| 13 | 8 | 14 | +| 14 | 6 | 6 | +| 15 | 9 | 9 | + +**9.2 CAVLC parsing process for transform coefficient levels** + +This process is invoked for the parsing of syntax elements with descriptor equal to ce(v) in clause 7.3.5.3.2 when entropy\_coding\_mode\_flag is equal to 0. + +Inputs to this process are bits from slice data, a maximum number of non-zero transform coefficient levels maxNumCoeff, the luma block index luma4x4BlkIdx or the chroma block index chroma4x4BlkIdx, cb4x4BlkIdx or cr4x4BlkIdx of the current block of transform coefficient levels. + +Output of this process is the list coeffLevel containing transform coefficient levels of the luma block with block index luma4x4BlkIdx or the chroma block with block index chroma4x4BlkIdx, cb4x4BlkIdx or cr4x4BlkIdx. + +The process is specified in the following ordered steps: + +1. All transform coefficient level values coeffLevel[ i ], with indices i ranging from 0 to maxNumCoeff – 1, in the list coeffLevel are set equal to 0. +2. The total number of non-zero transform coefficient levels TotalCoeff( coeff\_token ) and the number of trailing one transform coefficient levels TrailingOnes( coeff\_token ) are derived by parsing coeff\_token as specified in clause 9.2.1. +3. The following then applies: + - If the number of non-zero transform coefficient levels TotalCoeff( coeff\_token ) is equal to 0, the list coeffLevel (in which all transform coefficient level values are equal to 0) is returned and no further steps are carried out. + - Otherwise, the following steps are carried out: + - a. The non-zero transform coefficient levels are derived by parsing trailing\_ones\_sign\_flag, level\_prefix, and level\_suffix as specified in clause 9.2.2. + - b. The runs of zero transform coefficient levels before each non-zero transform coefficient level are derived by parsing total\_zeros and run\_before as specified in clause 9.2.3. + - c. The level and run information are combined into the list coeffLevel as specified in clause 9.2.4. + +**9.2.1 Parsing process for total number of non-zero transform coefficient levels and number of trailing ones** + +Inputs to this process are bits from slice data, a maximum number of non-zero transform coefficient levels maxNumCoeff, the luma block index luma4x4BlkIdx or the chroma block index chroma4x4BlkIdx, cb4x4BlkIdx or cr4x4BlkIdx of the current block of transform coefficient levels. + +Outputs of this process are TotalCoeff( coeff\_token ), TrailingOnes( coeff\_token ), and the variable nC. + +The syntax element coeff\_token is decoded using one of the six VLCs specified in the six right-most columns of Table 9-5. Each VLC specifies both TotalCoeff( coeff\_token ) and TrailingOnes( coeff\_token ) for a given codeword coeff\_token. The selection of the applicable column of Table 9-5 is determined by a variable nC. The value of nC is derived as follows: + +- If the CAVLC parsing process is invoked for ChromaDCLevel, nC is derived as follows: + +- If ChromaArrayType is equal to 1, nC is set equal to –1, +- Otherwise (ChromaArrayType is equal to 2), nC is set equal to –2, +- Otherwise, the following ordered steps are performed: + 1. When the CAVLC parsing process is invoked for Intra16x16DCLevel, luma4x4BlkIdx is set equal to 0. + 2. When the CAVLC parsing process is invoked for CbIntra16x16DCLevel, cb4x4BlkIdx is set equal to 0. + 3. When the CAVLC parsing process is invoked for CrIntra16x16DCLevel, cr4x4BlkIdx is set equal to 0. + 4. The variables blkA and blkB are derived as follows: + - If the CAVLC parsing process is invoked for Intra16x16DCLevel, Intra16x16ACLevel, or LumaLevel4x4, the process specified in clause 6.4.11.4 is invoked with luma4x4BlkIdx as the input, and the output is assigned to mbAddrA, mbAddrB, luma4x4BlkIdxA, and luma4x4BlkIdxB. The 4x4 luma block specified by mbAddrA\luma4x4BlkIdxA is assigned to blkA, and the 4x4 luma block specified by mbAddrB\luma4x4BlkIdxB is assigned to blkB. + - Otherwise, if the CAVLC parsing process is invoked for CbIntra16x16DCLevel, CbIntra16x16ACLevel, or CbLevel4x4, the process specified in clause 6.4.11.6 is invoked with cb4x4BlkIdx as the input, and the output is assigned to mbAddrA, mbAddrB, cb4x4BlkIdxA, and cb4x4BlkIdxB. The 4x4 Cb block specified by mbAddrA\cb4x4BlkIdxA is assigned to blkA, and the 4x4 Cb block specified by mbAddrB\cb4x4BlkIdxB is assigned to blkB. + - Otherwise, if the CAVLC parsing process is invoked for CrIntra16x16DCLevel, CrIntra16x16ACLevel, or CrLevel4x4, the process specified in clause 6.4.11.6 is invoked with cr4x4BlkIdx as the input, and the output is assigned to mbAddrA, mbAddrB, cr4x4BlkIdxA, and cr4x4BlkIdxB. The 4x4 Cr block specified by mbAddrA\cr4x4BlkIdxA is assigned to blkA, and the 4x4 Cr block specified by mbAddrB\cr4x4BlkIdxB is assigned to blkB. + - Otherwise (the CAVLC parsing process is invoked for ChromaACLevel), the process specified in clause 6.4.11.5 is invoked with chroma4x4BlkIdx as input, and the output is assigned to mbAddrA, mbAddrB, chroma4x4BlkIdxA, and chroma4x4BlkIdxB. The 4x4 chroma block specified by mbAddrA\iCbCr\chroma4x4BlkIdxA is assigned to blkA, and the 4x4 chroma block specified by mbAddrB\iCbCr\chroma4x4BlkIdxB is assigned to blkB. + 5. The variable availableFlagN with N being replaced by A and B is derived as follows: + - If any of the following conditions are true, availableFlagN is set equal to 0: + - mbAddrN is not available, + - the current macroblock is coded using an Intra macroblock prediction mode, constrained\_intra\_pred\_flag is equal to 1, mbAddrN is coded using an Inter macroblock prediction mode, and slice data partitioning is in use (nal\_unit\_type is in the range of 2 to 4, inclusive). + - Otherwise, availableFlagN is set equal to 1. + 6. For N being replaced by A and B, when availableFlagN is equal to 1, the variable nN is derived as follows: + - If any of the following conditions are true, nN is set equal to 0: + - The macroblock mbAddrN has mb\_type equal to P\_Skip or B\_Skip, + - The macroblock mbAddrN has mb\_type not equal to I\_PCM and all AC residual transform coefficient levels of the neighbouring block blkN are equal to 0 due to the corresponding bit of CodedBlockPatternLuma or CodedBlockPatternChroma being equal to 0. + - Otherwise, if mbAddrN is an I\_PCM macroblock, nN is set equal to 16. + - Otherwise, nN is set equal to the value TotalCoeff( coeff\_token ) of the neighbouring block blkN. + + +NOTE 1 – The values nA and nB that are derived using TotalCoeff( coeff\_token ) do not include the DC transform coefficient levels in Intra\_16x16 macroblocks or DC transform coefficient levels in chroma blocks, because these transform coefficient levels are decoded separately. When the block above or to the left belongs to an Intra\_16x16 macroblock, nA or nB is the number of decoded non-zero AC transform coefficient levels for the adjacent 4x4 block in the Intra\_16x16 macroblock. When the block above or to the left is a chroma block, nA or nB is the number of decoded non-zero AC transform coefficient levels for the adjacent chroma block. + +NOTE 2 – When parsing for Intra16x16DCLevel, CbIntra16x16DCLevel, or CrIntra16x16DCLevel, the values nA and nB are based on the number of non-zero transform coefficient levels in adjacent 4x4 blocks and not on the number of non-zero DC transform coefficient levels in adjacent 16x16 blocks. + +7. The variable nC is derived as follows: + +- If availableFlagA is equal to 1 and availableFlagB is equal to 1, the variable nC is set equal to $(nA + nB + 1) \gg 1$ . +- Otherwise, if availableFlagA is equal to 1 (and availableFlagB is equal to 0), the variable nC is set equal to nA. +- Otherwise, if availableFlagB is equal to 1 (and availableFlagA is equal to 0), the variable nC is set equal to nB. +- Otherwise (availableFlagA is equal to 0 and availableFlagB is equal to 0), the variable nC is set equal to 0. + +When maxNumCoeff is equal to 15, it is a requirement of bitstream conformance that the value of TotalCoeff( coeff\_token ) resulting from decoding coeff\_token shall not be equal to 16. + +**Table 9-5 – coeff\_token mapping to TotalCoeff( coeff\_token ) and TrailingOnes( coeff\_token )** + +| TrailingOnes
( coeff_token ) | TotalCoeff
( coeff_token ) | $0 \leq nC < 2$ | $2 \leq nC < 4$ | $4 \leq nC < 8$ | $8 \leq nC$ | $nC == -1$ | $nC == -2$ | +|---------------------------------|-------------------------------|------------------|-----------------|-----------------|-------------|------------|----------------| +| 0 | 0 | 1 | 11 | 1111 | 0000 11 | 01 | 1 | +| 0 | 1 | 0001 01 | 0010 11 | 0011 11 | 0000 00 | 0001 11 | 0001 111 | +| 1 | 1 | 01 | 10 | 1110 | 0000 01 | 1 | 01 | +| 0 | 2 | 0000 0111 | 0001 11 | 0010 11 | 0001 00 | 0001 00 | 0001 110 | +| 1 | 2 | 0001 00 | 0011 1 | 0111 1 | 0001 01 | 0001 10 | 0001 101 | +| 2 | 2 | 001 | 011 | 1101 | 0001 10 | 001 | 001 | +| 0 | 3 | 0000 0011 1 | 0000 111 | 0010 00 | 0010 00 | 0000 11 | 0000 0011 1 | +| 1 | 3 | 0000 0110 | 0010 10 | 0110 0 | 0010 01 | 0000 011 | 0001 100 | +| 2 | 3 | 0000 101 | 0010 01 | 0111 0 | 0010 10 | 0000 010 | 0001 011 | +| 3 | 3 | 0001 1 | 0101 | 1100 | 0010 11 | 0001 01 | 0000 1 | +| 0 | 4 | 0000 0001 11 | 0000 0111 | 0001 111 | 0011 00 | 0000 10 | 0000 0011 0 | +| 1 | 4 | 0000 0011 0 | 0001 10 | 0101 0 | 0011 01 | 0000 0011 | 0000 0010 1 | +| 2 | 4 | 0000 0101 | 0001 01 | 0101 1 | 0011 10 | 0000 0010 | 0001 010 | +| 3 | 4 | 0000 11 | 0100 | 1011 | 0011 11 | 0000 000 | 0000 01 | +| 0 | 5 | 0000 0000 111 | 0000 0100 | 0001 011 | 0100 00 | - | 0000 0001 11 | +| 1 | 5 | 0000 0001 10 | 0000 110 | 0100 0 | 0100 01 | - | 0000 0001 10 | +| 2 | 5 | 0000 0010 1 | 0000 101 | 0100 1 | 0100 10 | - | 0000 0010 0 | +| 3 | 5 | 0000 100 | 0011 0 | 1010 | 0100 11 | - | 0001 001 | +| 0 | 6 | 0000 0000 0111 1 | 0000 0011 1 | 0001 001 | 0101 00 | - | 0000 0000 111 | +| 1 | 6 | 0000 0000 110 | 0000 0110 | 0011 10 | 0101 01 | - | 0000 0000 110 | +| 2 | 6 | 0000 0001 01 | 0000 0101 | 0011 01 | 0101 10 | - | 0000 0001 01 | +| 3 | 6 | 0000 0100 | 0010 00 | 1001 | 0101 11 | - | 0001 000 | +| 0 | 7 | 0000 0000 0101 1 | 0000 0001 111 | 0001 000 | 0110 00 | - | 0000 0000 0111 | +| 1 | 7 | 0000 0000 0111 0 | 0000 0011 0 | 0010 10 | 0110 01 | - | 0000 0000 0110 | +| 2 | 7 | 0000 0000 101 | 0000 0010 1 | 0010 01 | 0110 10 | - | 0000 0000 101 | + +Table 9-5 – coeff\_token mapping to TotalCoeff( coeff\_token ) and TrailingOnes( coeff\_token ) + +| TrailingOnes
(coeff_token) | TotalCoeff
(coeff_token) | 0 ≤ nC < 2 | 2 ≤ nC < 4 | 4 ≤ nC < 8 | 8 ≤ nC | nC == -1 | nC == -2 | +|-------------------------------|-----------------------------|---------------------|-------------------|--------------|---------|----------|------------------| +| 3 | 7 | 0000 0010 0 | 0001 00 | 1000 | 0110 11 | - | 0000 0001 00 | +| 0 | 8 | 0000 0000 0100 0 | 0000 0001 011 | 0000 1111 | 0111 00 | - | 0000 0000 0011 1 | +| 1 | 8 | 0000 0000 0101 0 | 0000 0001 110 | 0001 110 | 0111 01 | - | 0000 0000 0101 | +| 2 | 8 | 0000 0000 0110 1 | 0000 0001 101 | 0001 101 | 0111 10 | - | 0000 0000 0100 | +| 3 | 8 | 0000 0001 00 | 0000 100 | 0110 1 | 0111 11 | - | 0000 0000 100 | +| 0 | 9 | 0000 0000 0011 11 | 0000 0000 1111 | 0000 1011 | 1000 00 | - | - | +| 1 | 9 | 0000 0000 0011 10 | 0000 0001 010 | 0000 1110 | 1000 01 | - | - | +| 2 | 9 | 0000 0000 0100 1 | 0000 0001 001 | 0001 010 | 1000 10 | - | - | +| 3 | 9 | 0000 0000 100 | 0000 0010 0 | 0011 00 | 1000 11 | - | - | +| 0 | 10 | 0000 0000 0010 11 | 0000 0000 1011 | 0000 0111 1 | 1001 00 | - | - | +| 1 | 10 | 0000 0000 0010 10 | 0000 0000 1110 | 0000 1010 | 1001 01 | - | - | +| 2 | 10 | 0000 0000 0011 01 | 0000 0000 1101 | 0000 1101 | 1001 10 | - | - | +| 3 | 10 | 0000 0000 0110 0 | 0000 0001 100 | 0001 100 | 1001 11 | - | - | +| 0 | 11 | 0000 0000 0001 111 | 0000 0000 1000 | 0000 0101 1 | 1010 00 | - | - | +| 1 | 11 | 0000 0000 0001 110 | 0000 0000 1010 | 0000 0111 0 | 1010 01 | - | - | +| 2 | 11 | 0000 0000 0010 01 | 0000 0000 1001 | 0000 1001 | 1010 10 | - | - | +| 3 | 11 | 0000 0000 0011 00 | 0000 0001 000 | 0000 1100 | 1010 11 | - | - | +| 0 | 12 | 0000 0000 0001 011 | 0000 0000 0111 1 | 0000 0100 0 | 1011 00 | - | - | +| 1 | 12 | 0000 0000 0001 010 | 0000 0000 0111 0 | 0000 0101 0 | 1011 01 | - | - | +| 2 | 12 | 0000 0000 0001 101 | 0000 0000 0110 1 | 0000 0110 1 | 1011 10 | - | - | +| 3 | 12 | 0000 0000 0010 00 | 0000 0000 1100 | 0000 1000 | 1011 11 | - | - | +| 0 | 13 | 0000 0000 0000 1111 | 0000 0000 0101 1 | 0000 0011 01 | 1100 00 | - | - | +| 1 | 13 | 0000 0000 0000 001 | 0000 0000 0101 0 | 0000 0011 1 | 1100 01 | - | - | +| 2 | 13 | 0000 0000 0001 001 | 0000 0000 0100 1 | 0000 0100 1 | 1100 10 | - | - | +| 3 | 13 | 0000 0000 0001 100 | 0000 0000 0110 0 | 0000 0110 0 | 1100 11 | - | - | +| 0 | 14 | 0000 0000 0000 1011 | 0000 0000 0011 1 | 0000 0010 01 | 1101 00 | - | - | +| 1 | 14 | 0000 0000 0000 1110 | 0000 0000 0010 11 | 0000 0011 00 | 1101 01 | - | - | +| 2 | 14 | 0000 0000 0000 1101 | 0000 0000 0011 0 | 0000 0010 11 | 1101 10 | - | - | +| 3 | 14 | 0000 0000 0001 000 | 0000 0000 0100 0 | 0000 0010 10 | 1101 11 | - | - | +| 0 | 15 | 0000 0000 0000 0111 | 0000 0000 0010 01 | 0000 0001 01 | 1110 00 | - | - | +| 1 | 15 | 0000 0000 0000 1010 | 0000 0000 0010 00 | 0000 0010 00 | 1110 01 | - | - | +| 2 | 15 | 0000 0000 0000 1001 | 0000 0000 0010 10 | 0000 0001 11 | 1110 10 | - | - | +| 3 | 15 | 0000 0000 0000 1100 | 0000 0000 0000 1 | 0000 0001 10 | 1110 11 | - | - | +| 0 | 16 | 0000 0000 0000 0100 | 0000 0000 0001 11 | 0000 0000 01 | 1111 00 | - | - | + +**Table 9-5 – coeff\_token mapping to TotalCoeff( coeff\_token ) and TrailingOnes( coeff\_token )** + +| TrailingOnes
(coeff_token) | TotalCoeff
(coeff_token) | 0 ≤ nC < 2 | 2 ≤ nC < 4 | 4 ≤ nC < 8 | 8 ≤ nC | nC == -1 | nC == -2 | +|-------------------------------|-----------------------------|---------------------|-------------------|--------------|---------|----------|----------| +| 1 | 16 | 0000 0000 0000 0110 | 0000 0000 0001 10 | 0000 0001 00 | 1111 01 | - | - | +| 2 | 16 | 0000 0000 0000 0101 | 0000 0000 0001 01 | 0000 0000 11 | 1111 10 | - | - | +| 3 | 16 | 0000 0000 0000 1000 | 0000 0000 0001 00 | 0000 0000 10 | 1111 11 | - | - | + +### 9.2.2 Parsing process for level information + +Inputs to this process are bits from slice data, the number of non-zero transform coefficient levels TotalCoeff( coeff\_token ), and the number of trailing one transform coefficient levels TrailingOnes( coeff\_token ). + +Output of this process is a list with name levelVal containing transform coefficient levels. + +Initially an index i is set equal to 0. Then, when TrailingOnes( coeff\_token ) is not equal to 0, the following ordered steps are applied TrailingOnes( coeff\_token ) times to decode the trailing one transform coefficient levels: + +1. A 1-bit syntax element trailing\_ones\_sign\_flag is decoded and evaluated as follows: + - If trailing\_ones\_sign\_flag is equal to 0, levelVal[ i ] is set equal to 1. + - Otherwise (trailing\_ones\_sign\_flag is equal to 1), levelVal[ i ] is set equal to -1. +2. The index i is incremented by 1. + +Then, the variable suffixLength is initialized as follows: + +- If TotalCoeff( coeff\_token ) is greater than 10 and TrailingOnes( coeff\_token ) is less than 3, suffixLength is set equal to 1. +- Otherwise (TotalCoeff( coeff\_token ) is less than or equal to 10 or TrailingOnes( coeff\_token ) is equal to 3), suffixLength is set equal to 0. + +Then, when TotalCoeff( coeff\_token ) – TrailingOnes( coeff\_token ) is not equal to 0, the following ordered steps are applied TotalCoeff( coeff\_token ) – TrailingOnes( coeff\_token ) times to decode the remaining non-zero level values: + +1. The syntax element level\_prefix is decoded as specified in clause 9.2.2.1. +2. The variable levelSuffixSize is set as follows: + - If level\_prefix is equal to 14 and suffixLength is equal to 0, levelSuffixSize is set equal to 4. + - Otherwise, if level\_prefix is greater than or equal to 15, levelSuffixSize is set equal to level\_prefix – 3. + - Otherwise, levelSuffixSize is set equal to suffixLength. +3. The syntax element level\_suffix is decoded as follows: + - If levelSuffixSize is greater than 0, the syntax element level\_suffix is decoded as unsigned integer representation u(v) with levelSuffixSize bits. + - Otherwise (levelSuffixSize is equal to 0), the syntax element level\_suffix is inferred to be equal to 0. +4. The variable levelCode is set equal to ( Min( 15, level\_prefix ) << suffixLength ) + level\_suffix. +5. When level\_prefix is greater than or equal to 15 and suffixLength is equal to 0, levelCode is incremented by 15. +6. When level\_prefix is greater than or equal to 16, levelCode is incremented by (1<<( level\_prefix – 3 )) – 4096. +7. When the index i is equal to TrailingOnes( coeff\_token ) and TrailingOnes( coeff\_token ) is less than 3, levelCode is incremented by 2. +8. The variable levelVal[ i ] is derived as follows: + - If levelCode is an even number, levelVal[ i ] is set equal to ( levelCode + 2 ) >> 1. + +- Otherwise (levelCode is an odd number), levelVal[ i ] is set equal to ( -levelCode - 1 ) >> 1. +- 9. When suffixLength is equal to 0, suffixLength is set equal to 1. +- 10. When the absolute value of levelVal[ i ] is greater than ( 3 << ( suffixLength - 1 ) ) and suffixLength is less than 6, suffixLength is incremented by 1. +- 11. The index i is incremented by 1. + +### 9.2.2.1 Parsing process for level\_prefix + +Inputs to this process are bits from slice data. + +Output of this process is level\_prefix. + +The parsing process for this syntax element consists in reading the bits starting at the current location in the bitstream up to and including the first non-zero bit, and counting the number of leading bits that are equal to 0. This process is specified as follows: + +``` + +leadingZeroBits = -1 +for( b = 0; !b; leadingZeroBits++ ) + b = read_bits( 1 ) +level_prefix = leadingZeroBits + +``` + +(9-4) + +Table 9-6 illustrates the codeword table for level\_prefix. + +NOTE – The value of level\_prefix is constrained to not exceed 15 in bitstreams conforming to the Baseline, Constrained Baseline, Main, and Extended profiles, as specified in clauses A.2.1, A.2.1.1, A.2.2, and A.2.3, respectively. In bitstreams conforming to other profiles, it has been reported that the value of level\_prefix cannot exceed 11 + bitDepth with bitDepth being the variable BitDepthY for transform coefficient blocks related to the luma component and being the variable BitDepthC for transform coefficient blocks related to a chroma component. + +**Table 9-6 – Codeword table for level\_prefix (informative)** + +| level_prefix | bit string | +|--------------|---------------------| +| 0 | 1 | +| 1 | 01 | +| 2 | 001 | +| 3 | 0001 | +| 4 | 0000 1 | +| 5 | 0000 01 | +| 6 | 0000 001 | +| 7 | 0000 0001 | +| 8 | 0000 0000 1 | +| 9 | 0000 0000 01 | +| 10 | 0000 0000 001 | +| 11 | 0000 0000 0001 | +| 12 | 0000 0000 0000 1 | +| 13 | 0000 0000 0000 01 | +| 14 | 0000 0000 0000 001 | +| 15 | 0000 0000 0000 0001 | +| ... | ... | + +### 9.2.3 Parsing process for run information + +Inputs to this process are bits from slice data, the number of non-zero transform coefficient levels $\text{TotalCoeff}(\text{coeff\_token})$ , and the maximum number of non-zero transform coefficient levels $\text{maxNumCoeff}$ . + +Output of this process is a list of runs of zero transform coefficient levels preceding non-zero transform coefficient levels called $\text{runVal}$ . + +Initially, an index $i$ is set equal to 0. + +The variable $\text{zerosLeft}$ is derived as follows: + +- If the number of non-zero transform coefficient levels $\text{TotalCoeff}(\text{coeff\_token})$ is equal to the maximum number of non-zero transform coefficient levels $\text{maxNumCoeff}$ , a variable $\text{zerosLeft}$ is set equal to 0. +- Otherwise (the number of non-zero transform coefficient levels $\text{TotalCoeff}(\text{coeff\_token})$ is less than the maximum number of non-zero transform coefficient levels $\text{maxNumCoeff}$ ), $\text{total\_zeros}$ is decoded and $\text{zerosLeft}$ is set equal to its value. + +The variable $\text{tzVlcIndex}$ is set equal to $\text{TotalCoeff}(\text{coeff\_token})$ . + +The VLC used to decode $\text{total\_zeros}$ is derived as follows: + +- If $\text{maxNumCoeff}$ is equal to 4, one of the VLCs specified in Table 9-9 (a) is used. +- Otherwise, if $\text{maxNumCoeff}$ is equal to 8, one of the VLCs specified in Table 9-9 (b) is used. +- Otherwise ( $\text{maxNumCoeff}$ is not equal to 4 and not equal to 8), VLCs from Tables 9-7 and 9-8 are used. + +The following ordered steps are then performed $\text{TotalCoeff}(\text{coeff\_token}) - 1$ times: + +1. The variable $\text{runVal}[i]$ is derived as follows: + - If $\text{zerosLeft}$ is greater than zero, a value $\text{run\_before}$ is decoded based on Table 9-10 and $\text{zerosLeft}$ . $\text{runVal}[i]$ is set equal to $\text{run\_before}$ . + - Otherwise ( $\text{zerosLeft}$ is equal to 0), $\text{runVal}[i]$ is set equal to 0. +2. The value of $\text{runVal}[i]$ is subtracted from $\text{zerosLeft}$ and the result is assigned to $\text{zerosLeft}$ . It is a requirement of bitstream conformance that the result of the subtraction shall be greater than or equal to 0. +3. The index $i$ is incremented by 1. + +Finally the value of $\text{zerosLeft}$ is assigned to $\text{runVal}[i]$ . + +**Table 9-7 – total\_zeros tables for 4x4 blocks with tzVlcIndex 1 to 7** + +| total_zeros | tzVlcIndex | | | | | | | +|-------------|-------------|---------|---------|--------|--------|---------|---------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| 0 | 1 | 111 | 0101 | 0001 1 | 0101 | 0000 01 | 0000 01 | +| 1 | 011 | 110 | 111 | 111 | 0100 | 0000 1 | 0000 1 | +| 2 | 010 | 101 | 110 | 0101 | 0011 | 111 | 101 | +| 3 | 0011 | 100 | 101 | 0100 | 111 | 110 | 100 | +| 4 | 0010 | 011 | 0100 | 110 | 110 | 101 | 011 | +| 5 | 0001 1 | 0101 | 0011 | 101 | 101 | 100 | 11 | +| 6 | 0001 0 | 0100 | 100 | 100 | 100 | 011 | 010 | +| 7 | 0000 11 | 0011 | 011 | 0011 | 011 | 010 | 0001 | +| 8 | 0000 10 | 0010 | 0010 | 011 | 0010 | 0001 | 001 | +| 9 | 0000 011 | 0001 1 | 0001 1 | 0010 | 0000 1 | 001 | 0000 00 | +| 10 | 0000 010 | 0001 0 | 0001 0 | 0001 0 | 0001 | 0000 00 | - | +| 11 | 0000 0011 | 0000 11 | 0000 01 | 0000 1 | 0000 0 | - | - | +| 12 | 0000 0010 | 0000 10 | 0000 1 | 0000 0 | - | - | - | +| 13 | 0000 0001 1 | 0000 01 | 0000 00 | - | - | - | - | +| 14 | 0000 0001 0 | 0000 00 | - | - | - | - | - | +| 15 | 0000 0000 1 | - | - | - | - | - | - | + +**Table 9-8 – total\_zeros tables for 4x4 blocks with tzVlcIndex 8 to 15** + +| total_zeros | tzVlcIndex | | | | | | | | +|-------------|------------|---------|--------|------|------|-----|----|----| +| | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +| 0 | 0000 01 | 0000 01 | 0000 1 | 0000 | 0000 | 000 | 00 | 0 | +| 1 | 0001 | 0000 00 | 0000 0 | 0001 | 0001 | 001 | 01 | 1 | +| 2 | 0000 1 | 0001 | 001 | 001 | 01 | 1 | 1 | - | +| 3 | 011 | 11 | 11 | 010 | 1 | 01 | - | - | +| 4 | 11 | 10 | 10 | 1 | 001 | - | - | - | +| 5 | 10 | 001 | 01 | 011 | - | - | - | - | +| 6 | 010 | 01 | 0001 | - | - | - | - | - | +| 7 | 001 | 0000 1 | - | - | - | - | - | - | +| 8 | 0000 00 | - | - | - | - | - | - | - | + +**Table 9-9 – total\_zeros tables for chroma DC 2x2 and 2x4 blocks** + +**(a) Chroma DC 2x2 block (4:2:0 chroma sampling)** + +| total_zeros | tzVlcIndex | | | +|-------------|------------|----|---| +| | 1 | 2 | 3 | +| 0 | 1 | 1 | 1 | +| 1 | 01 | 01 | 0 | +| 2 | 001 | 00 | - | +| 3 | 000 | - | - | + +**(b) Chroma DC 2x4 block (4:2:2 chroma sampling)** + +| total_zeros | tzVlcIndex | | | | | | | +|-------------|------------|-----|-----|-----|----|----|---| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| 0 | 1 | 000 | 000 | 110 | 00 | 00 | 0 | +| 1 | 010 | 01 | 001 | 00 | 01 | 01 | 1 | +| 2 | 011 | 001 | 01 | 01 | 10 | 1 | - | +| 3 | 0010 | 100 | 10 | 10 | 11 | - | - | +| 4 | 0011 | 101 | 110 | 111 | - | - | - | +| 5 | 0001 | 110 | 111 | - | - | - | - | +| 6 | 0000 1 | 111 | - | - | - | - | - | +| 7 | 0000 0 | - | - | - | - | - | - | + +**Table 9-10 – Tables for run\_before** + +| run_before | zerosLeft | | | | | | | +|------------|-----------|----|----|-----|-----|-----|-------------| +| | 1 | 2 | 3 | 4 | 5 | 6 | >6 | +| 0 | 1 | 1 | 11 | 11 | 11 | 11 | 111 | +| 1 | 0 | 01 | 10 | 10 | 10 | 000 | 110 | +| 2 | - | 00 | 01 | 01 | 011 | 001 | 101 | +| 3 | - | - | 00 | 001 | 010 | 011 | 100 | +| 4 | - | - | - | 000 | 001 | 010 | 011 | +| 5 | - | - | - | - | 000 | 101 | 010 | +| 6 | - | - | - | - | - | 100 | 001 | +| 7 | - | - | - | - | - | - | 0001 | +| 8 | - | - | - | - | - | - | 00001 | +| 9 | - | - | - | - | - | - | 000001 | +| 10 | - | - | - | - | - | - | 0000001 | +| 11 | - | - | - | - | - | - | 00000001 | +| 12 | - | - | - | - | - | - | 000000001 | +| 13 | - | - | - | - | - | - | 0000000001 | +| 14 | - | - | - | - | - | - | 00000000001 | + +### 9.2.4 Combining level and run information + +Input to this process are a list of transform coefficient levels called levelVal, a list of runs called runVal, and the number of non-zero transform coefficient levels TotalCoeff( coeff\_token ). + +Output of this process is an list coeffLevel of transform coefficient levels. + +A variable coeffNum is set equal to -1 and an index i is set equal to TotalCoeff( coeff\_token ) - 1. The following ordered steps are then applied TotalCoeff( coeff\_token ) times: + +1. coeffNum is incremented by runVal[ i ] + 1. +2. coeffLevel[ coeffNum ] is set equal to levelVal[ i ]. +3. The index i is decremented by 1. + +### 9.3 CABAC parsing process for slice data + +This process is invoked when parsing syntax elements with descriptor ae(v) in clauses 7.3.4 and 7.3.5 when entropy\_coding\_mode\_flag is equal to 1. + +Inputs to this process are a request for a value of a syntax element and values of prior parsed syntax elements. + +Output of this process is the value of the syntax element. + +When starting the parsing of the slice data of a slice in clause 7.3.4, the initialization process of the CABAC parsing process is invoked as specified in clause 9.3.1. + +The parsing of syntax elements proceeds as follows. + +For each requested value of a syntax element a binarization is derived as described in clause 9.3.2. + +The binarization for the syntax element and the sequence of parsed bins determines the decoding process flow as described in clause 9.3.3. + +For each bin of the binarization of the syntax element, which is indexed by the variable binIdx, a context index ctxIdx is derived as specified in clause 9.3.3.1. + +For each ctxIdx the arithmetic decoding process is invoked as specified in clause 9.3.3.2. + +The resulting sequence ( $b_0..b_{binIdx}$ ) of parsed bins is compared to the set of bin strings given by the binarization process after decoding of each bin. When the sequence matches a bin string in the given set, the corresponding value is assigned to the syntax element. + +In case the request for a value of a syntax element is processed for the syntax element mb\_type and the decoded value of mb\_type is equal to I\_PCM, the decoding engine is initialized after the decoding of any pcm\_alignment\_zero\_bit and all pcm\_sample\_luma and pcm\_sample\_chroma data as specified in clause 9.3.1.2. + +The whole CABAC parsing process is illustrated in the flowchart of Figure 9-1 with the abbreviation SE for syntax element. + +![Flowchart of CABAC parsing process for a syntax element SE. The process starts with CABACParsing(SE), checks if it's the first SE in a slice, initializes context variables and the decoding engine if needed, then enters a loop to get binarization, initialize binIdx to -1, increment binIdx, get ctxIdx, and decode the bin until all bits are decoded. Finally, it checks if the SE is of type mb_type and value I_PCM, initializing the decoding engine again if so, before ending.](166d8ee3cc0c825044a113560f81799c_img.jpg) + +``` + +graph TD + Start([CABACParsing(SE)]) --> FirstSE{First SE in +slice?} + FirstSE -- Yes --> InitCtx[Initialization of +context variables] + InitCtx --> InitEngine1[Initialization of +decoding engine] + FirstSE -- No --> GetBinarization[Get Binarization(SE)] + InitEngine1 --> GetBinarization + GetBinarization --> binIdxInit[binIdx = -1] + binIdxInit --> binIdxInc[binIdx++] + binIdxInc --> GetCtxIdx[Get ctxIdx(binIdx)] + GetCtxIdx --> DecodeBin[DecodeBin(ctxIdx)] + DecodeBin --> AllBits{(b_0, \dots, b_{binIdx}) in +Binarization(SE)?} + AllBits -- No --> binIdxInc + AllBits -- Yes --> PCMCheck{SE == mb_type +&& value(b_0, \dots, b_{binIdx})== +I_PCM?} + PCMCheck -- Yes --> InitEngine2[Initialization of +decoding engine] + PCMCheck -- No --> Done([Done]) + InitEngine2 --> Done + +``` + +Flowchart of CABAC parsing process for a syntax element SE. The process starts with CABACParsing(SE), checks if it's the first SE in a slice, initializes context variables and the decoding engine if needed, then enters a loop to get binarization, initialize binIdx to -1, increment binIdx, get ctxIdx, and decode the bin until all bits are decoded. Finally, it checks if the SE is of type mb\_type and value I\_PCM, initializing the decoding engine again if so, before ending. + +H.264(09)\_F9-1 + +**Figure 9-1 – Illustration of CABAC parsing process for a syntax element SE (informative)** + +### 9.3.1 Initialization process + +Outputs of this process are initialized CABAC internal variables. + +The processes in clauses 9.3.1.1 and 9.3.1.2 are invoked when starting the parsing of the slice data of a slice in clause 7.3.4. + +The process in clause 9.3.1.2 is also invoked after decoding any pcm\_alignment\_zero\_bit and all pcm\_sample\_luma and pcm\_sample\_chroma data for a macroblock of type I\_PCM. + +### 9.3.1.1 Initialization process for context variables + +Outputs of this process are the initialized CABAC context variables indexed by ctxIdx. + +Tables 9-12 to 9-33 contain the values of the variables n and m used in the initialization of context variables that are assigned to all syntax elements in clauses 7.3.4 and 7.3.5 except for the end-of-slice flag. + +For each context variable, the two variables pStateIdx and valMPS are initialized. + +NOTE 1 – The variable pStateIdx corresponds to a probability state index and the variable valMPS corresponds to the value of the most probable symbol as further described in clause 9.3.3.2. + +The two values assigned to pStateIdx and valMPS for the initialization are derived from SliceQPV, which is derived in Equation 7-32. Given the two table entries ( m, n ), the initialization is specified by the following pseudo-code process: + +``` +preCtxState = Clip3( 1, 126, ( ( m * Clip3( 0, 51, SliceQPV ) ) >> 4 ) + n ) +if( preCtxState <= 63 ) { + pStateIdx = 63 - preCtxState + valMPS = 0 +} else { + pStateIdx = preCtxState - 64 + valMPS = 1 +} +``` + +(9-5) + +In Table 9-11, the ctxIdx for which initialization is needed for each of the slice types are listed. Also listed is the table number that includes the values of m and n needed for the initialization. For P, SP and B slice type, the initialization depends also on the value of the cabac\_init\_idc syntax element. Note that the syntax element names do not affect the initialization process. + +**Table 9-11 – Association of ctxIdx and syntax elements for each slice type in the initialization process** + +| | Syntax element | Table | Slice type | | | | +|--------------------------------|------------------------------|----------------------------------------|------------|----------|----------|----------| +| | | | SI | I | P, SP | B | +| slice_data() | mb_skip_flag | Table 9-13
Table 9-14 | | | 11..13 | 24..26 | +| | mb_field_decoding_flag | Table 9-18 | 70..72 | 70..72 | 70..72 | 70..72 | +| macroblock_layer() | mb_type | Table 9-12
Table 9-13
Table 9-14 | 0..10 | 3..10 | 14..20 | 27..35 | +| | transform_size_8x8_flag | Table 9-16 | na | 399..401 | 399..401 | 399..401 | +| | coded_block_pattern (luma) | Table 9-18 | 73..76 | 73..76 | 73..76 | 73..76 | +| | coded_block_pattern (chroma) | Table 9-18 | 77..84 | 77..84 | 77..84 | 77..84 | +| | mb_qp_delta | Table 9-17 | 60..63 | 60..63 | 60..63 | 60..63 | +| mb_pred() | prev_intra4x4_pred_mode_flag | Table 9-17 | 68 | 68 | 68 | 68 | +| | rem_intra4x4_pred_mode | Table 9-17 | 69 | 69 | 69 | 69 | +| | prev_intra8x8_pred_mode_flag | Table 9-17 | na | 68 | 68 | 68 | +| | rem_intra8x8_pred_mode | Table 9-17 | na | 69 | 69 | 69 | +| | intra_chroma_pred_mode | Table 9-17 | 64..67 | 64..67 | 64..67 | 64..67 | +| mb_pred() and
sub_mb_pred() | ref_idx_l0 | Table 9-16 | | | 54..59 | 54..59 | +| | ref_idx_l1 | Table 9-16 | | | | 54..59 | +| | mvd_l0[ ][ ][ 0 ] | Table 9-15 | | | 40..46 | 40..46 | +| | mvd_l1[ ][ ][ 0 ] | Table 9-15 | | | | 40..46 | +| | mvd_l0[ ][ ][ 1 ] | Table 9-15 | | | 47..53 | 47..53 | +| | mvd_l1[ ][ ][ 1 ] | Table 9-15 | | | | 47..53 | +| sub_mb_pred() | sub_mb_type[ ] | Table 9-13
Table 9-14 | | | 21..23 | 36..39 | + +**Table 9-11 – Association of ctxIdx and syntax elements for each slice type in the initialization process** + +| | Syntax element | Table | Slice type | | | | +|------------------------|--------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------| +| | | | SI | I | P, SP | B | +| residual_block_cabac() | coded_block_flag | Table 9-18
Table 9-25
Table 9-33 | 85..104
460..483 | 85..104
460..483
1012..1023 | 85..104
460..483
1012..1023 | 85..104
460..483
1012..1023 | +| | significant_coeff_flag[ ] | Table 9-19
Table 9-22
Table 9-24
Table 9-24
Table 9-26
Table 9-30
Table 9-28
Table 9-29 | 105..165
277..337 | 105..165
277..337
402..416
436..450
484..571
776..863
660..689
718..747 | 105..165
277..337
402..416
436..450
484..571
776..863
660..689
718..747 | 105..165
277..337
402..416
436..450
484..571
776..863
660..689
718..747 | +| | last_significant_coeff_flag[ ] | Table 9-20
Table 9-23
Table 9-24
Table 9-24
Table 9-27
Table 9-31
Table 9-28
Table 9-29 | 166..226
338..398 | 166..226
338..398
417..425
451..459
572..659
864..951
690..707
748..765 | 166..226
338..398
417..425
451..459
572..659
864..951
690..707
748..765 | 166..226
338..398
417..425
451..459
572..659
864..951
690..707
748..765 | +| | coeff_abs_level_minus1[ ] | Table 9-21
Table 9-24
Table 9-32
Table 9-28
Table 9-29 | 227..275 | 227..275
426..435
952..1011
708..717
766..775 | 227..275
426..435
952..1011
708..717
766..775 | 227..275
426..435
952..1011
708..717
766..775 | + +NOTE 2 – ctxIdx equal to 276 is associated with the end\_of\_slice\_flag and the bin of mb\_type, which specifies the I\_PCM macroblock type. The decoding process specified in clause 9.3.3.2.4 applies to ctxIdx equal to 276. This decoding process, however, may also be implemented by using the decoding process specified in clause 9.3.3.2.1. In this case, the initial values associated with ctxIdx equal to 276 are specified to be pStateIdx = 63 and valMPS = 0, where pStateIdx = 63 represents a non-adapting probability state. + +**Table 9-12 – Values of variables m and n for ctxIdx from 0 to 10** + +| Initialization variables | ctxIdx | | | | | | | | | | | +|--------------------------|--------|----|----|-----|----|----|-----|-----|----|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | +| m | 20 | 2 | 3 | 20 | 2 | 3 | -28 | -23 | -6 | -1 | 7 | +| n | -15 | 54 | 74 | -15 | 54 | 74 | 127 | 104 | 53 | 54 | 51 | + +**Table 9-13 – Values of variables m and n for ctxIdx from 11 to 23** + +| Value of cabac_init_idc | Initialization variables | ctxIdx | | | | | | | | | | | | | +|-------------------------|--------------------------|--------|----|----|-----|----|-----|----|-----|-----|----|----|-----|----| +| | | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | +| 0 | m | 23 | 23 | 21 | 1 | 0 | -37 | 5 | -13 | -11 | 1 | 12 | -4 | 17 | +| | n | 33 | 2 | 0 | 9 | 49 | 118 | 57 | 78 | 65 | 62 | 49 | 73 | 50 | +| 1 | m | 22 | 34 | 16 | -2 | 4 | -29 | 2 | -6 | -13 | 5 | 9 | -3 | 10 | +| | n | 25 | 0 | 0 | 9 | 41 | 118 | 65 | 71 | 79 | 52 | 50 | 70 | 54 | +| 2 | m | 29 | 25 | 14 | -10 | -3 | -27 | 26 | -4 | -24 | 5 | 6 | -17 | 14 | +| | n | 16 | 0 | 0 | 51 | 62 | 99 | 16 | 85 | 102 | 57 | 57 | 73 | 57 | + +**Table 9-14 – Values of variables m and n for ctxIdx from 24 to 39** + +| Value of cabac_init_idc | Initialization variables | ctxIdx | | | | | | | | | | | | | | | | +|-------------------------|--------------------------|--------|----|----|----|----|-----|---------|---------|----|---------|---------|----|----|---------|----|----| +| | | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | +| 0 | m | 18 | 9 | 29 | 26 | 16 | 9 | -4
6 | -2
0 | 1 | -1
3 | -1
1 | 1 | -6 | -1
7 | -6 | 9 | +| | n | 64 | 43 | 0 | 67 | 90 | 104 | 127 | 104 | 67 | 78 | 65 | 62 | 86 | 95 | 61 | 45 | +| 1 | m | 26 | 19 | 40 | 57 | 41 | 26 | -4
5 | -1
5 | -4 | -6 | -1
3 | 5 | 6 | -1
3 | 0 | 8 | +| | n | 34 | 22 | 0 | 2 | 36 | 69 | 127 | 101 | 76 | 71 | 79 | 52 | 69 | 90 | 52 | 43 | +| 2 | m | 20 | 20 | 29 | 54 | 37 | 12 | -3
2 | -2
2 | -2 | -4 | -2
4 | 5 | -6 | -1
4 | -6 | 4 | +| | n | 40 | 10 | 0 | 0 | 42 | 97 | 127 | 117 | 74 | 85 | 102 | 57 | 93 | 88 | 44 | 55 | + +**Table 9-15 – Values of variables m and n for ctxIdx from 40 to 53** + +| Value of cabac_init_idc | Initialization variables | ctxIdx | | | | | | | | | | | | | | +|-------------------------|--------------------------|--------|-----|-----|----|----|----|-----|----|----|-----|----|----|----|-----| +| | | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | +| 0 | m | -3 | -6 | -11 | 6 | 7 | -5 | 2 | 0 | -3 | -10 | 5 | 4 | -3 | 0 | +| | n | 69 | 81 | 96 | 55 | 67 | 86 | 88 | 58 | 76 | 94 | 54 | 69 | 81 | 88 | +| 1 | m | -2 | -5 | -10 | 2 | 2 | -3 | -3 | 1 | -3 | -6 | 0 | -3 | -7 | -5 | +| | n | 69 | 82 | 96 | 59 | 75 | 87 | 100 | 56 | 74 | 85 | 59 | 81 | 86 | 95 | +| 2 | m | -11 | -15 | -21 | 19 | 20 | 4 | 6 | 1 | -5 | -13 | 5 | 6 | -3 | -1 | +| | n | 89 | 103 | 116 | 57 | 58 | 84 | 96 | 63 | 85 | 106 | 63 | 75 | 90 | 101 | + +**Table 9-16 – Values of variables m and n for ctxIdx from 54 to 59, and 399 to 401** + +| Value of cabac_init_idc | Initialization variables | ctxIdx | | | | | | | | | +|-------------------------|--------------------------|--------|----|----|-----|----|----|-----|-----|-----| +| | | 54 | 55 | 56 | 57 | 58 | 59 | 399 | 400 | 401 | +| 1 slices | m | na | na | na | na | na | na | 31 | 31 | 25 | +| | n | na | na | na | na | na | na | 21 | 31 | 50 | +| 0 | m | -7 | -5 | -4 | -5 | -7 | 1 | 12 | 11 | 14 | +| | n | 67 | 74 | 74 | 80 | 72 | 58 | 40 | 51 | 59 | +| 1 | m | -1 | -1 | 1 | -2 | -5 | 0 | 25 | 21 | 21 | +| | n | 66 | 77 | 70 | 86 | 72 | 61 | 32 | 49 | 54 | +| 2 | m | 3 | -4 | -2 | -12 | -7 | 1 | 21 | 19 | 17 | +| | n | 55 | 79 | 75 | 97 | 50 | 60 | 33 | 50 | 61 | + +**Table 9-17 – Values of variables m and n for ctxIdx from 60 to 69** + +| Initialization variables | ctxIdx | | | | | | | | | | +|--------------------------|--------|----|----|----|----|----|----|----|----|----| +| | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | +| m | 0 | 0 | 0 | 0 | -9 | 4 | 0 | -7 | 13 | 3 | +| n | 41 | 63 | 63 | 63 | 83 | 86 | 97 | 72 | 41 | 62 | + +**Table 9-18 – Values of variables m and n for ctxIdx from 70 to 104** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|-----------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----|------------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----| +| | 0 | | 1 | | 2 | | 0 | | | 1 | | 2 | | | | | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 70 | 0 | 11 | 0 | 45 | 13 | 15 | 7 | 34 | 88 | -11 | 115 | -13 | 108 | -4 | 92 | 5 | 78 | +| 71 | 1 | 55 | -4 | 78 | 7 | 51 | -9 | 88 | 89 | -12 | 63 | -3 | 46 | 0 | 39 | -6 | 55 | +| 72 | 0 | 69 | -3 | 96 | 2 | 80 | -20 | 127 | 90 | -2 | 68 | -1 | 65 | 0 | 65 | 4 | 61 | +| 73 | -17 | 127 | -27 | 126 | -39 | 127 | -36 | 127 | 91 | -15 | 84 | -1 | 57 | -15 | 84 | -14 | 83 | +| 74 | -13 | 102 | -28 | 98 | -18 | 91 | -17 | 91 | 92 | -13 | 104 | -9 | 93 | -35 | 127 | -37 | 127 | +| 75 | 0 | 82 | -25 | 101 | -17 | 96 | -14 | 95 | 93 | -3 | 70 | -3 | 74 | -2 | 73 | -5 | 79 | +| 76 | -7 | 74 | -23 | 67 | -26 | 81 | -25 | 84 | 94 | -8 | 93 | -9 | 92 | -12 | 104 | -11 | 104 | +| 77 | -21 | 107 | -28 | 82 | -35 | 98 | -25 | 86 | 95 | -10 | 90 | -8 | 87 | -9 | 91 | -11 | 91 | +| 78 | -27 | 127 | -20 | 94 | -24 | 102 | -12 | 89 | 96 | -30 | 127 | -23 | 126 | -31 | 127 | -30 | 127 | +| 79 | -31 | 127 | -16 | 83 | -23 | 97 | -17 | 91 | 97 | -1 | 74 | 5 | 54 | 3 | 55 | 0 | 65 | +| 80 | -24 | 127 | -22 | 110 | -27 | 119 | -31 | 127 | 98 | -6 | 97 | 6 | 60 | 7 | 56 | -2 | 79 | +| 81 | -18 | 95 | -21 | 91 | -24 | 99 | -14 | 76 | 99 | -7 | 91 | 6 | 59 | 7 | 55 | 0 | 72 | +| 82 | -27 | 127 | -18 | 102 | -21 | 110 | -18 | 103 | 100 | -20 | 127 | 6 | 69 | 8 | 61 | -4 | 92 | +| 83 | -21 | 114 | -13 | 93 | -18 | 102 | -13 | 90 | 101 | -4 | 56 | -1 | 48 | -3 | 53 | -6 | 56 | +| 84 | -30 | 127 | -29 | 127 | -36 | 127 | -37 | 127 | 102 | -5 | 82 | 0 | 68 | 0 | 68 | 3 | 68 | +| 85 | -17 | 123 | -7 | 92 | 0 | 80 | 11 | 80 | 103 | -7 | 76 | -4 | 69 | -7 | 74 | -8 | 71 | +| 86 | -12 | 115 | -5 | 89 | -5 | 89 | 5 | 76 | 104 | -22 | 125 | -8 | 88 | -9 | 88 | -13 | 98 | +| 87 | -16 | 122 | -7 | 96 | -7 | 94 | 2 | 84 | | | | | | | | | | + +**Table 9-19 – Values of variables m and n for ctxIdx from 105 to 165** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|--------|-----------------|-----|-------------------------|-----|-----|-----|-----|----|--------|-----------------|-----|-------------------------|----|-----|----|-----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 105 | -7 | 93 | -2 | 85 | -13 | 103 | -4 | 86 | 136 | -13 | 101 | 5 | 53 | 0 | 58 | -5 | 75 | +| 106 | -11 | 87 | -6 | 78 | -13 | 91 | -12 | 88 | 137 | -13 | 91 | -2 | 61 | -1 | 60 | -8 | 80 | +| 107 | -3 | 77 | -1 | 75 | -9 | 89 | -5 | 82 | 138 | -12 | 94 | 0 | 56 | -3 | 61 | -21 | 83 | +| 108 | -5 | 71 | -7 | 77 | -14 | 92 | -3 | 72 | 139 | -10 | 88 | 0 | 56 | -8 | 67 | -21 | 64 | +| 109 | -4 | 63 | 2 | 54 | -8 | 76 | -4 | 67 | 140 | -16 | 84 | -13 | 63 | -25 | 84 | -13 | 31 | +| 110 | -4 | 68 | 5 | 50 | -12 | 87 | -8 | 72 | 141 | -10 | 86 | -5 | 60 | -14 | 74 | -25 | 64 | +| 111 | -12 | 84 | -3 | 68 | -23 | 110 | -16 | 89 | 142 | -7 | 83 | -1 | 62 | -5 | 65 | -29 | 94 | +| 112 | -7 | 62 | 1 | 50 | -24 | 105 | -9 | 69 | 143 | -13 | 87 | 4 | 57 | 5 | 52 | 9 | 75 | +| 113 | -7 | 65 | 6 | 42 | -10 | 78 | -1 | 59 | 144 | -19 | 94 | -6 | 69 | 2 | 57 | 17 | 63 | +| 114 | 8 | 61 | -4 | 81 | -20 | 112 | 5 | 66 | 145 | 1 | 70 | 4 | 57 | 0 | 61 | -8 | 74 | +| 115 | 5 | 56 | 1 | 63 | -17 | 99 | 4 | 57 | 146 | 0 | 72 | 14 | 39 | -9 | 69 | -5 | 35 | +| 116 | -2 | 66 | -4 | 70 | -78 | 127 | -4 | 71 | 147 | -5 | 74 | 4 | 51 | -11 | 70 | -2 | 27 | +| 117 | 1 | 64 | 0 | 67 | -70 | 127 | -2 | 71 | 148 | 18 | 59 | 13 | 68 | 18 | 55 | 13 | 91 | +| 118 | 0 | 61 | 2 | 57 | -50 | 127 | 2 | 58 | 149 | -8 | 102 | 3 | 64 | -4 | 71 | 3 | 65 | +| 119 | -2 | 78 | -2 | 76 | -46 | 127 | -1 | 74 | 150 | -15 | 100 | 1 | 61 | 0 | 58 | -7 | 69 | +| 120 | 1 | 50 | 11 | 35 | -4 | 66 | -4 | 44 | 151 | 0 | 95 | 9 | 63 | 7 | 61 | 8 | 77 | +| 121 | 7 | 52 | 4 | 64 | -5 | 78 | -1 | 69 | 152 | -4 | 75 | 7 | 50 | 9 | 41 | -10 | 66 | +| 122 | 10 | 35 | 1 | 61 | -4 | 71 | 0 | 62 | 153 | 2 | 72 | 16 | 39 | 18 | 25 | 3 | 62 | +| 123 | 0 | 44 | 11 | 35 | -8 | 72 | -7 | 51 | 154 | -11 | 75 | 5 | 44 | 9 | 32 | -3 | 68 | +| 124 | 11 | 38 | 18 | 25 | 2 | 59 | -4 | 47 | 155 | -3 | 71 | 4 | 52 | 5 | 43 | -20 | 81 | +| 125 | 1 | 45 | 12 | 24 | -1 | 55 | -6 | 42 | 156 | 15 | 46 | 11 | 48 | 9 | 47 | 0 | 30 | +| 126 | 0 | 46 | 13 | 29 | -7 | 70 | -3 | 41 | 157 | -13 | 69 | -5 | 60 | 0 | 44 | 1 | 7 | +| 127 | 5 | 44 | 13 | 36 | -6 | 75 | -6 | 53 | 158 | 0 | 62 | -1 | 59 | 0 | 51 | -3 | 23 | +| 128 | 31 | 17 | -10 | 93 | -8 | 89 | 8 | 76 | 159 | 0 | 65 | 0 | 59 | 2 | 46 | -21 | 74 | +| 129 | 1 | 51 | -7 | 73 | -34 | 119 | -9 | 78 | 160 | 21 | 37 | 22 | 33 | 19 | 38 | 16 | 66 | +| 130 | 7 | 50 | -2 | 73 | -3 | 75 | -11 | 83 | 161 | -15 | 72 | 5 | 44 | -4 | 66 | -23 | 124 | +| 131 | 28 | 19 | 13 | 46 | 32 | 20 | 9 | 52 | 162 | 9 | 57 | 14 | 43 | 15 | 38 | 17 | 37 | +| 132 | 16 | 33 | 9 | 49 | 30 | 22 | 0 | 67 | 163 | 16 | 54 | -1 | 78 | 12 | 42 | 44 | -18 | +| 133 | 14 | 62 | -7 | 100 | -44 | 127 | -5 | 90 | 164 | 0 | 62 | 0 | 60 | 9 | 34 | 50 | -34 | +| 134 | -13 | 108 | 9 | 53 | 0 | 54 | 1 | 67 | 165 | 12 | 72 | 9 | 69 | 0 | 89 | -22 | 127 | +| 135 | -15 | 100 | 2 | 53 | -5 | 61 | -15 | 72 | | | | | | | | | | + +Table 9-20 – Values of variables m and n for ctxIdx from 166 to 226 + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|--------|-----------------|-----|-------------------------|----|-----|-----|----|-----|--------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----| +| | m | n | 0 | | 1 | | 2 | | | m | n | 0 | | 1 | | 2 | | +| | | | m | n | m | n | m | n | | | | m | n | m | n | m | n | +| 166 | 24 | 0 | 11 | 28 | 4 | 45 | 4 | 39 | 197 | 26 | -17 | 28 | 3 | 36 | -28 | 28 | -3 | +| 167 | 15 | 9 | 2 | 40 | 10 | 28 | 0 | 42 | 198 | 30 | -25 | 28 | 4 | 38 | -28 | 24 | 10 | +| 168 | 8 | 25 | 3 | 44 | 10 | 31 | 7 | 34 | 199 | 28 | -20 | 32 | 0 | 38 | -27 | 27 | 0 | +| 169 | 13 | 18 | 0 | 49 | 33 | -11 | 11 | 29 | 200 | 33 | -23 | 34 | -1 | 34 | -18 | 34 | -14 | +| 170 | 15 | 9 | 0 | 46 | 52 | -43 | 8 | 31 | 201 | 37 | -27 | 30 | 6 | 35 | -16 | 52 | -44 | +| 171 | 13 | 19 | 2 | 44 | 18 | 15 | 6 | 37 | 202 | 33 | -23 | 30 | 6 | 34 | -14 | 39 | -24 | +| 172 | 10 | 37 | 2 | 51 | 28 | 0 | 7 | 42 | 203 | 40 | -28 | 32 | 9 | 32 | -8 | 19 | 17 | +| 173 | 12 | 18 | 0 | 47 | 35 | -22 | 3 | 40 | 204 | 38 | -17 | 31 | 19 | 37 | -6 | 31 | 25 | +| 174 | 6 | 29 | 4 | 39 | 38 | -25 | 8 | 33 | 205 | 33 | -11 | 26 | 27 | 35 | 0 | 36 | 29 | +| 175 | 20 | 33 | 2 | 62 | 34 | 0 | 13 | 43 | 206 | 40 | -15 | 26 | 30 | 30 | 10 | 24 | 33 | +| 176 | 15 | 30 | 6 | 46 | 39 | -18 | 13 | 36 | 207 | 41 | -6 | 37 | 20 | 28 | 18 | 34 | 15 | +| 177 | 4 | 45 | 0 | 54 | 32 | -12 | 4 | 47 | 208 | 38 | 1 | 28 | 34 | 26 | 25 | 30 | 20 | +| 178 | 1 | 58 | 3 | 54 | 102 | -94 | 3 | 55 | 209 | 41 | 17 | 17 | 70 | 29 | 41 | 22 | 73 | +| 179 | 0 | 62 | 2 | 58 | 0 | 0 | 2 | 58 | 210 | 30 | -6 | 1 | 67 | 0 | 75 | 20 | 34 | +| 180 | 7 | 61 | 4 | 63 | 56 | -15 | 6 | 60 | 211 | 27 | 3 | 5 | 59 | 2 | 72 | 19 | 31 | +| 181 | 12 | 38 | 6 | 51 | 33 | -4 | 8 | 44 | 212 | 26 | 22 | 9 | 67 | 8 | 77 | 27 | 44 | +| 182 | 11 | 45 | 6 | 57 | 29 | 10 | 11 | 44 | 213 | 37 | -16 | 16 | 30 | 14 | 35 | 19 | 16 | +| 183 | 15 | 39 | 7 | 53 | 37 | -5 | 14 | 42 | 214 | 35 | -4 | 18 | 32 | 18 | 31 | 15 | 36 | +| 184 | 11 | 42 | 6 | 52 | 51 | -29 | 7 | 48 | 215 | 38 | -8 | 18 | 35 | 17 | 35 | 15 | 36 | +| 185 | 13 | 44 | 6 | 55 | 39 | -9 | 4 | 56 | 216 | 38 | -3 | 22 | 29 | 21 | 30 | 21 | 28 | +| 186 | 16 | 45 | 11 | 45 | 52 | -34 | 4 | 52 | 217 | 37 | 3 | 24 | 31 | 17 | 45 | 25 | 21 | +| 187 | 12 | 41 | 14 | 36 | 69 | -58 | 13 | 37 | 218 | 38 | 5 | 23 | 38 | 20 | 42 | 30 | 20 | +| 188 | 10 | 49 | 8 | 53 | 67 | -63 | 9 | 49 | 219 | 42 | 0 | 18 | 43 | 18 | 45 | 31 | 12 | +| 189 | 30 | 34 | -1 | 82 | 44 | -5 | 19 | 58 | 220 | 35 | 16 | 20 | 41 | 27 | 26 | 27 | 16 | +| 190 | 18 | 42 | 7 | 55 | 32 | 7 | 10 | 48 | 221 | 39 | 22 | 11 | 63 | 16 | 54 | 24 | 42 | +| 191 | 10 | 55 | -3 | 78 | 55 | -29 | 12 | 45 | 222 | 14 | 48 | 9 | 59 | 7 | 66 | 0 | 93 | +| 192 | 17 | 51 | 15 | 46 | 32 | 1 | 0 | 69 | 223 | 27 | 37 | 9 | 64 | 16 | 56 | 14 | 56 | +| 193 | 17 | 46 | 22 | 31 | 0 | 0 | 20 | 33 | 224 | 21 | 60 | -1 | 94 | 11 | 73 | 15 | 57 | +| 194 | 0 | 89 | -1 | 84 | 27 | 36 | 8 | 63 | 225 | 12 | 68 | -2 | 89 | 10 | 67 | 26 | 38 | +| 195 | 26 | -19 | 25 | 7 | 33 | -25 | 35 | -18 | 226 | 2 | 97 | -9 | 108 | -10 | 116 | -24 | 127 | +| 196 | 22 | -17 | 30 | -7 | 34 | -30 | 33 | -25 | | | | | | | | | | + +Table 9-21 – Values of variables m and n for ctxIdx from 227 to 275 + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|--------|-----------------|----|-------------------------|-----|-----|-----|-----|-----|--------|-----------------|-----|-------------------------|----|-----|----|-----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 227 | -3 | 71 | -6 | 76 | -23 | 112 | -24 | 115 | 252 | -12 | 73 | -6 | 55 | -16 | 72 | -14 | 75 | +| 228 | -6 | 42 | -2 | 44 | -15 | 71 | -22 | 82 | 253 | -8 | 76 | 0 | 58 | -7 | 69 | -10 | 79 | +| 229 | -5 | 50 | 0 | 45 | -7 | 61 | -9 | 62 | 254 | -7 | 80 | 0 | 64 | -4 | 69 | -9 | 83 | +| 230 | -3 | 54 | 0 | 52 | 0 | 53 | 0 | 53 | 255 | -9 | 88 | -3 | 74 | -5 | 74 | -12 | 92 | +| 231 | -2 | 62 | -3 | 64 | -5 | 66 | 0 | 59 | 256 | -17 | 110 | -10 | 90 | -9 | 86 | -18 | 108 | +| 232 | 0 | 58 | -2 | 59 | -11 | 77 | -14 | 85 | 257 | -11 | 97 | 0 | 70 | 2 | 66 | -4 | 79 | +| 233 | 1 | 63 | -4 | 70 | -9 | 80 | -13 | 89 | 258 | -20 | 84 | -4 | 29 | -9 | 34 | -22 | 69 | +| 234 | -2 | 72 | -4 | 75 | -9 | 84 | -13 | 94 | 259 | -11 | 79 | 5 | 31 | 1 | 32 | -16 | 75 | +| 235 | -1 | 74 | -8 | 82 | -10 | 87 | -11 | 92 | 260 | -6 | 73 | 7 | 42 | 11 | 31 | -2 | 58 | +| 236 | -9 | 91 | -17 | 102 | -34 | 127 | -29 | 127 | 261 | -4 | 74 | 1 | 59 | 5 | 52 | 1 | 58 | +| 237 | -5 | 67 | -9 | 77 | -21 | 101 | -21 | 100 | 262 | -13 | 86 | -2 | 58 | -2 | 55 | -13 | 78 | +| 238 | -5 | 27 | 3 | 24 | -3 | 39 | -14 | 57 | 263 | -13 | 96 | -3 | 72 | -2 | 67 | -9 | 83 | +| 239 | -3 | 39 | 0 | 42 | -5 | 53 | -12 | 67 | 264 | -11 | 97 | -3 | 81 | 0 | 73 | -4 | 81 | +| 240 | -2 | 44 | 0 | 48 | -7 | 61 | -11 | 71 | 265 | -19 | 117 | -11 | 97 | -8 | 89 | -13 | 99 | +| 241 | 0 | 46 | 0 | 55 | -11 | 75 | -10 | 77 | 266 | -8 | 78 | 0 | 58 | 3 | 52 | -13 | 81 | +| 242 | -16 | 64 | -6 | 59 | -15 | 77 | -21 | 85 | 267 | -5 | 33 | 8 | 5 | 7 | 4 | -6 | 38 | +| 243 | -8 | 68 | -7 | 71 | -17 | 91 | -16 | 88 | 268 | -4 | 48 | 10 | 14 | 10 | 8 | -13 | 62 | +| 244 | -10 | 78 | -12 | 83 | -25 | 107 | -23 | 104 | 269 | -2 | 53 | 14 | 18 | 17 | 8 | -6 | 58 | +| 245 | -6 | 77 | -11 | 87 | -25 | 111 | -15 | 98 | 270 | -3 | 62 | 13 | 27 | 16 | 19 | -2 | 59 | +| 246 | -10 | 86 | -30 | 119 | -28 | 122 | -37 | 127 | 271 | -13 | 71 | 2 | 40 | 3 | 37 | -16 | 73 | +| 247 | -12 | 92 | 1 | 58 | -11 | 76 | -10 | 82 | 272 | -10 | 79 | 0 | 58 | -1 | 61 | -10 | 76 | +| 248 | -15 | 55 | -3 | 29 | -10 | 44 | -8 | 48 | 273 | -12 | 86 | -3 | 70 | -5 | 73 | -13 | 86 | +| 249 | -10 | 60 | -1 | 36 | -10 | 52 | -8 | 61 | 274 | -13 | 90 | -6 | 79 | -1 | 70 | -9 | 83 | +| 250 | -6 | 62 | 1 | 38 | -10 | 57 | -8 | 66 | 275 | -14 | 97 | -8 | 85 | -4 | 78 | -10 | 87 | +| 251 | -4 | 65 | 2 | 43 | -9 | 58 | -7 | 70 | | | | | | | | | | + +**Table 9-22 – Values of variables m and n for ctxIdx from 277 to 337** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|--------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----|------------|-----------------|----|-------------------------|----|-----|----|-----|----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 277 | -6 | 93 | -13 | 106 | -21 | 126 | -22 | 127 | 308 | -16 | 96 | -1 | 51 | -16 | 77 | -10 | 67 | +| 278 | -6 | 84 | -16 | 106 | -23 | 124 | -25 | 127 | 309 | -7 | 88 | 7 | 49 | -2 | 64 | 1 | 68 | +| 279 | -8 | 79 | -10 | 87 | -20 | 110 | -25 | 120 | 310 | -8 | 85 | 8 | 52 | 2 | 61 | 0 | 77 | +| 280 | 0 | 66 | -21 | 114 | -26 | 126 | -27 | 127 | 311 | -7 | 85 | 9 | 41 | -6 | 67 | 2 | 64 | +| 281 | -1 | 71 | -18 | 110 | -25 | 124 | -19 | 114 | 312 | -9 | 85 | 6 | 47 | -3 | 64 | 0 | 68 | +| 282 | 0 | 62 | -14 | 98 | -17 | 105 | -23 | 117 | 313 | -13 | 88 | 2 | 55 | 2 | 57 | -5 | 78 | +| 283 | -2 | 60 | -22 | 110 | -27 | 121 | -25 | 118 | 314 | 4 | 66 | 13 | 41 | -3 | 65 | 7 | 55 | +| 284 | -2 | 59 | -21 | 106 | -27 | 117 | -26 | 117 | 315 | -3 | 77 | 10 | 44 | -3 | 66 | 5 | 59 | +| 285 | -5 | 75 | -18 | 103 | -17 | 102 | -24 | 113 | 316 | -3 | 76 | 6 | 50 | 0 | 62 | 2 | 65 | +| 286 | -3 | 62 | -21 | 107 | -26 | 117 | -28 | 118 | 317 | -6 | 76 | 5 | 53 | 9 | 51 | 14 | 54 | +| 287 | -4 | 58 | -23 | 108 | -27 | 116 | -31 | 120 | 318 | 10 | 58 | 13 | 49 | -1 | 66 | 15 | 44 | +| 288 | -9 | 66 | -26 | 112 | -33 | 122 | -37 | 124 | 319 | -1 | 76 | 4 | 63 | -2 | 71 | 5 | 60 | +| 289 | -1 | 79 | -10 | 96 | -10 | 95 | -10 | 94 | 320 | -1 | 83 | 6 | 64 | -2 | 75 | 2 | 70 | +| 290 | 0 | 71 | -12 | 95 | -14 | 100 | -15 | 102 | 321 | -7 | 99 | -2 | 69 | -1 | 70 | -2 | 76 | +| 291 | 3 | 68 | -5 | 91 | -8 | 95 | -10 | 99 | 322 | -14 | 95 | -2 | 59 | -9 | 72 | -18 | 86 | +| 292 | 10 | 44 | -9 | 93 | -17 | 111 | -13 | 106 | 323 | 2 | 95 | 6 | 70 | 14 | 60 | 12 | 70 | +| 293 | -7 | 62 | -22 | 94 | -28 | 114 | -50 | 127 | 324 | 0 | 76 | 10 | 44 | 16 | 37 | 5 | 64 | +| 294 | 15 | 36 | -5 | 86 | -6 | 89 | -5 | 92 | 325 | -5 | 74 | 9 | 31 | 0 | 47 | -12 | 70 | +| 295 | 14 | 40 | 9 | 67 | -2 | 80 | 17 | 57 | 326 | 0 | 70 | 12 | 43 | 18 | 35 | 11 | 55 | +| 296 | 16 | 27 | -4 | 80 | -4 | 82 | -5 | 86 | 327 | -11 | 75 | 3 | 53 | 11 | 37 | 5 | 56 | +| 297 | 12 | 29 | -10 | 85 | -9 | 85 | -13 | 94 | 328 | 1 | 68 | 14 | 34 | 12 | 41 | 0 | 69 | +| 298 | 1 | 44 | -1 | 70 | -8 | 81 | -12 | 91 | 329 | 0 | 65 | 10 | 38 | 10 | 41 | 2 | 65 | +| 299 | 20 | 36 | 7 | 60 | -1 | 72 | -2 | 77 | 330 | -14 | 73 | -3 | 52 | 2 | 48 | -6 | 74 | +| 300 | 18 | 32 | 9 | 58 | 5 | 64 | 0 | 71 | 331 | 3 | 62 | 13 | 40 | 12 | 41 | 5 | 54 | +| 301 | 5 | 42 | 5 | 61 | 1 | 67 | -1 | 73 | 332 | 4 | 62 | 17 | 32 | 13 | 41 | 7 | 54 | +| 302 | 1 | 48 | 12 | 50 | 9 | 56 | 4 | 64 | 333 | -1 | 68 | 7 | 44 | 0 | 59 | -6 | 76 | +| 303 | 10 | 62 | 15 | 50 | 0 | 69 | -7 | 81 | 334 | -13 | 75 | 7 | 38 | 3 | 50 | -11 | 82 | +| 304 | 17 | 46 | 18 | 49 | 1 | 69 | 5 | 64 | 335 | 11 | 55 | 13 | 50 | 19 | 40 | -2 | 77 | +| 305 | 9 | 64 | 17 | 54 | 7 | 69 | 15 | 57 | 336 | 5 | 64 | 10 | 57 | 3 | 66 | -2 | 77 | +| 306 | -12 | 104 | 10 | 41 | -7 | 69 | 1 | 67 | 337 | 12 | 70 | 26 | 43 | 18 | 50 | 25 | 42 | +| 307 | -11 | 97 | 7 | 46 | -6 | 67 | 0 | 68 | | | | | | | | | | + +Table 9-23 – Values of variables m and n for ctxIdx from 338 to 398 + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|--------|-----------------|-----|-------------------------|-----|----|-----|----|-----|--------|-----------------|-----|-------------------------|----|----|-----|-----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 338 | 15 | 6 | 14 | 11 | 19 | -6 | 17 | -13 | 369 | 32 | -26 | 31 | -4 | 40 | -37 | 37 | -17 | +| 339 | 6 | 19 | 11 | 14 | 18 | -6 | 16 | -9 | 370 | 37 | -30 | 27 | 6 | 38 | -30 | 32 | 1 | +| 340 | 7 | 16 | 9 | 11 | 14 | 0 | 17 | -12 | 371 | 44 | -32 | 34 | 8 | 46 | -33 | 34 | 15 | +| 341 | 12 | 14 | 18 | 11 | 26 | -12 | 27 | -21 | 372 | 34 | -18 | 30 | 10 | 42 | -30 | 29 | 15 | +| 342 | 18 | 13 | 21 | 9 | 31 | -16 | 37 | -30 | 373 | 34 | -15 | 24 | 22 | 40 | -24 | 24 | 25 | +| 343 | 13 | 11 | 23 | -2 | 33 | -25 | 41 | -40 | 374 | 40 | -15 | 33 | 19 | 49 | -29 | 34 | 22 | +| 344 | 13 | 15 | 32 | -15 | 33 | -22 | 42 | -41 | 375 | 33 | -7 | 22 | 32 | 38 | -12 | 31 | 16 | +| 345 | 15 | 16 | 32 | -15 | 37 | -28 | 48 | -47 | 376 | 35 | -5 | 26 | 31 | 40 | -10 | 35 | 18 | +| 346 | 12 | 23 | 34 | -21 | 39 | -30 | 39 | -32 | 377 | 33 | 0 | 21 | 41 | 38 | -3 | 31 | 28 | +| 347 | 13 | 23 | 39 | -23 | 42 | -30 | 46 | -40 | 378 | 38 | 2 | 26 | 44 | 46 | -5 | 33 | 41 | +| 348 | 15 | 20 | 42 | -33 | 47 | -42 | 52 | -51 | 379 | 33 | 13 | 23 | 47 | 31 | 20 | 36 | 28 | +| 349 | 14 | 26 | 41 | -31 | 45 | -36 | 46 | -41 | 380 | 23 | 35 | 16 | 65 | 29 | 30 | 27 | 47 | +| 350 | 14 | 44 | 46 | -28 | 49 | -34 | 52 | -39 | 381 | 13 | 58 | 14 | 71 | 25 | 44 | 21 | 62 | +| 351 | 17 | 40 | 38 | -12 | 41 | -17 | 43 | -19 | 382 | 29 | -3 | 8 | 60 | 12 | 48 | 18 | 31 | +| 352 | 17 | 47 | 21 | 29 | 32 | 9 | 32 | 11 | 383 | 26 | 0 | 6 | 63 | 11 | 49 | 19 | 26 | +| 353 | 24 | 17 | 45 | -24 | 69 | -71 | 61 | -55 | 384 | 22 | 30 | 17 | 65 | 26 | 45 | 36 | 24 | +| 354 | 21 | 21 | 53 | -45 | 63 | -63 | 56 | -46 | 385 | 31 | -7 | 21 | 24 | 22 | 22 | 24 | 23 | +| 355 | 25 | 22 | 48 | -26 | 66 | -64 | 62 | -50 | 386 | 35 | -15 | 23 | 20 | 23 | 22 | 27 | 16 | +| 356 | 31 | 27 | 65 | -43 | 77 | -74 | 81 | -67 | 387 | 34 | -3 | 26 | 23 | 27 | 21 | 24 | 30 | +| 357 | 22 | 29 | 43 | -19 | 54 | -39 | 45 | -20 | 388 | 34 | 3 | 27 | 32 | 33 | 20 | 31 | 29 | +| 358 | 19 | 35 | 39 | -10 | 52 | -35 | 35 | -2 | 389 | 36 | -1 | 28 | 23 | 26 | 28 | 22 | 41 | +| 359 | 14 | 50 | 30 | 9 | 41 | -10 | 28 | 15 | 390 | 34 | 5 | 28 | 24 | 30 | 24 | 22 | 42 | +| 360 | 10 | 57 | 18 | 26 | 36 | 0 | 34 | 1 | 391 | 32 | 11 | 23 | 40 | 27 | 34 | 16 | 60 | +| 361 | 7 | 63 | 20 | 27 | 40 | -1 | 39 | 1 | 392 | 35 | 5 | 24 | 32 | 18 | 42 | 15 | 52 | +| 362 | -2 | 77 | 0 | 57 | 30 | 14 | 30 | 17 | 393 | 34 | 12 | 28 | 29 | 25 | 39 | 14 | 60 | +| 363 | -4 | 82 | -14 | 82 | 28 | 26 | 20 | 38 | 394 | 39 | 11 | 23 | 42 | 18 | 50 | 3 | 78 | +| 364 | -3 | 94 | -5 | 75 | 23 | 37 | 18 | 45 | 395 | 30 | 29 | 19 | 57 | 12 | 70 | -16 | 123 | +| 365 | 9 | 69 | -19 | 97 | 12 | 55 | 15 | 54 | 396 | 34 | 26 | 22 | 53 | 21 | 54 | 21 | 53 | +| 366 | -12 | 109 | -35 | 125 | 11 | 65 | 0 | 79 | 397 | 29 | 39 | 22 | 61 | 14 | 71 | 22 | 56 | +| 367 | 36 | -35 | 27 | 0 | 37 | -33 | 36 | -16 | 398 | 19 | 66 | 11 | 86 | 11 | 83 | 25 | 61 | +| 368 | 36 | -34 | 28 | 0 | 39 | -36 | 37 | -14 | | | | | | | | | | + +Table 9-24 – Values of variables m and n for ctxIdx from 402 to 459 + +| ctxIdx | I slices | | Value of cabac_init_idc | | | | | | ctxIdx | I slices | | Value of cabac_init_idc | | | | | | +|--------|----------|-----|-------------------------|----|-----|-----|-----|-----|--------|----------|-----|-------------------------|-----|-----|-----|-----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 402 | -17 | 120 | -4 | 79 | -5 | 85 | -3 | 78 | 431 | -2 | 55 | -12 | 56 | -9 | 57 | -12 | 59 | +| 403 | -20 | 112 | -7 | 71 | -6 | 81 | -8 | 74 | 432 | 0 | 61 | -6 | 60 | -6 | 63 | -8 | 63 | +| 404 | -18 | 114 | -5 | 69 | -10 | 77 | -9 | 72 | 433 | 1 | 64 | -5 | 62 | -4 | 65 | -9 | 67 | +| 405 | -11 | 85 | -9 | 70 | -7 | 81 | -10 | 72 | 434 | 0 | 68 | -8 | 66 | -4 | 67 | -6 | 68 | +| 406 | -15 | 92 | -8 | 66 | -17 | 80 | -18 | 75 | 435 | -9 | 92 | -8 | 76 | -7 | 82 | -10 | 79 | +| 407 | -14 | 89 | -10 | 68 | -18 | 73 | -12 | 71 | 436 | -14 | 106 | -5 | 85 | -3 | 81 | -3 | 78 | +| 408 | -26 | 71 | -19 | 73 | -4 | 74 | -11 | 63 | 437 | -13 | 97 | -6 | 81 | -3 | 76 | -8 | 74 | +| 409 | -15 | 81 | -12 | 69 | -10 | 83 | -5 | 70 | 438 | -15 | 90 | -10 | 77 | -7 | 72 | -9 | 72 | +| 410 | -14 | 80 | -16 | 70 | -9 | 71 | -17 | 75 | 439 | -12 | 90 | -7 | 81 | -6 | 78 | -10 | 72 | +| 411 | 0 | 68 | -15 | 67 | -9 | 67 | -14 | 72 | 440 | -18 | 88 | -17 | 80 | -12 | 72 | -18 | 75 | +| 412 | -14 | 70 | -20 | 62 | -1 | 61 | -16 | 67 | 441 | -10 | 73 | -18 | 73 | -14 | 68 | -12 | 71 | +| 413 | -24 | 56 | -19 | 70 | -8 | 66 | -8 | 53 | 442 | -9 | 79 | -4 | 74 | -3 | 70 | -11 | 63 | +| 414 | -23 | 68 | -16 | 66 | -14 | 66 | -14 | 59 | 443 | -14 | 86 | -10 | 83 | -6 | 76 | -5 | 70 | +| 415 | -24 | 50 | -22 | 65 | 0 | 59 | -9 | 52 | 444 | -10 | 73 | -9 | 71 | -5 | 66 | -17 | 75 | +| 416 | -11 | 74 | -20 | 63 | 2 | 59 | -11 | 68 | 445 | -10 | 70 | -9 | 67 | -5 | 62 | -14 | 72 | +| 417 | 23 | -13 | 9 | -2 | 17 | -10 | 9 | -2 | 446 | -10 | 69 | -1 | 61 | 0 | 57 | -16 | 67 | +| 418 | 26 | -13 | 26 | -9 | 32 | -13 | 30 | -10 | 447 | -5 | 66 | -8 | 66 | -4 | 61 | -8 | 53 | +| 419 | 40 | -15 | 33 | -9 | 42 | -9 | 31 | -4 | 448 | -9 | 64 | -14 | 66 | -9 | 60 | -14 | 59 | +| 420 | 49 | -14 | 39 | -7 | 49 | -5 | 33 | -1 | 449 | -5 | 58 | 0 | 59 | 1 | 54 | -9 | 52 | +| 421 | 44 | 3 | 41 | -2 | 53 | 0 | 33 | 7 | 450 | 2 | 59 | 2 | 59 | 2 | 58 | -11 | 68 | +| 422 | 45 | 6 | 45 | 3 | 64 | 3 | 31 | 12 | 451 | 21 | -10 | 21 | -13 | 17 | -10 | 9 | -2 | +| 423 | 44 | 34 | 49 | 9 | 68 | 10 | 37 | 23 | 452 | 24 | -11 | 33 | -14 | 32 | -13 | 30 | -10 | +| 424 | 33 | 54 | 45 | 27 | 66 | 27 | 31 | 38 | 453 | 28 | -8 | 39 | -7 | 42 | -9 | 31 | -4 | +| 425 | 19 | 82 | 36 | 59 | 47 | 57 | 20 | 64 | 454 | 28 | -1 | 46 | -2 | 49 | -5 | 33 | -1 | +| 426 | -3 | 75 | -6 | 66 | -5 | 71 | -9 | 71 | 455 | 29 | 3 | 51 | 2 | 53 | 0 | 33 | 7 | +| 427 | -1 | 23 | -7 | 35 | 0 | 24 | -7 | 37 | 456 | 29 | 9 | 60 | 6 | 64 | 3 | 31 | 12 | +| 428 | 1 | 34 | -7 | 42 | -1 | 36 | -8 | 44 | 457 | 35 | 20 | 61 | 17 | 68 | 10 | 37 | 23 | +| 429 | 1 | 43 | -8 | 45 | -2 | 42 | -11 | 49 | 458 | 29 | 36 | 55 | 34 | 66 | 27 | 31 | 38 | +| 430 | 0 | 54 | -5 | 48 | -2 | 52 | -10 | 56 | 459 | 14 | 67 | 42 | 62 | 47 | 57 | 20 | 64 | + +**Table 9-25 – Values of variables m and n for ctxIdx from 460 to 483** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | | +|--------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----|--------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----|--| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | | +| 460 | -17 | 123 | -7 | 92 | 0 | 80 | 11 | 80 | 472 | -17 | 123 | -7 | 92 | 0 | 80 | 11 | 80 | | +| 461 | -12 | 115 | -5 | 89 | -5 | 89 | 5 | 76 | 473 | -12 | 115 | -5 | 89 | -5 | 89 | 5 | 76 | | +| 462 | -16 | 122 | -7 | 96 | -7 | 94 | 2 | 84 | 474 | -16 | 122 | -7 | 96 | -7 | 94 | 2 | 84 | | +| 463 | -11 | 115 | -13 | 108 | -4 | 92 | 5 | 78 | 475 | -11 | 115 | -13 | 108 | -4 | 92 | 5 | 78 | | +| 464 | -12 | 63 | -3 | 46 | 0 | 39 | -6 | 55 | 476 | -12 | 63 | -3 | 46 | 0 | 39 | -6 | 55 | | +| 465 | -2 | 68 | -1 | 65 | 0 | 65 | 4 | 61 | 477 | -2 | 68 | -1 | 65 | 0 | 65 | 4 | 61 | | +| 466 | -15 | 84 | -1 | 57 | -15 | 84 | -14 | 83 | 478 | -15 | 84 | -1 | 57 | -15 | 84 | -14 | 83 | | +| 467 | -13 | 104 | -9 | 93 | -35 | 127 | -37 | 127 | 479 | -13 | 104 | -9 | 93 | -35 | 127 | -37 | 127 | | +| 468 | -3 | 70 | -3 | 74 | -2 | 73 | -5 | 79 | 480 | -3 | 70 | -3 | 74 | -2 | 73 | -5 | 79 | | +| 469 | -8 | 93 | -9 | 92 | -12 | 104 | -11 | 104 | 481 | -8 | 93 | -9 | 92 | -12 | 104 | -11 | 104 | | +| 470 | -10 | 90 | -8 | 87 | -9 | 91 | -11 | 91 | 482 | -10 | 90 | -8 | 87 | -9 | 91 | -11 | 91 | | +| 471 | -30 | 127 | -23 | 126 | -31 | 127 | -30 | 127 | 483 | -30 | 127 | -23 | 126 | -31 | 127 | -30 | 127 | | + +**Table 9-26 – Values of variables m and n for ctxIdx from 484 to 571** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | | +|--------|-----------------|----|-------------------------|----|-----|-----|-----|----|--------|-----------------|----|-------------------------|----|-----|-----|-----|----|--| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | | +| 484 | -7 | 93 | -2 | 85 | -13 | 103 | -4 | 86 | 528 | -7 | 93 | -2 | 85 | -13 | 103 | -4 | 86 | | +| 485 | -11 | 87 | -6 | 78 | -13 | 91 | -12 | 88 | 529 | -11 | 87 | -6 | 78 | -13 | 91 | -12 | 88 | | +| 486 | -3 | 77 | -1 | 75 | -9 | 89 | -5 | 82 | 530 | -3 | 77 | -1 | 75 | -9 | 89 | -5 | 82 | | +| 487 | -5 | 71 | -7 | 77 | -14 | 92 | -3 | 72 | 531 | -5 | 71 | -7 | 77 | -14 | 92 | -3 | 72 | | +| 488 | -4 | 63 | 2 | 54 | -8 | 76 | -4 | 67 | 532 | -4 | 63 | 2 | 54 | -8 | 76 | -4 | 67 | | +| 489 | -4 | 68 | 5 | 50 | -12 | 87 | -8 | 72 | 533 | -4 | 68 | 5 | 50 | -12 | 87 | -8 | 72 | | +| 490 | -12 | 84 | -3 | 68 | -23 | 110 | -16 | 89 | 534 | -12 | 84 | -3 | 68 | -23 | 110 | -16 | 89 | | +| 491 | -7 | 62 | 1 | 50 | -24 | 105 | -9 | 69 | 535 | -7 | 62 | 1 | 50 | -24 | 105 | -9 | 69 | | +| 492 | -7 | 65 | 6 | 42 | -10 | 78 | -1 | 59 | 536 | -7 | 65 | 6 | 42 | -10 | 78 | -1 | 59 | | +| 493 | 8 | 61 | -4 | 81 | -20 | 112 | 5 | 66 | 537 | 8 | 61 | -4 | 81 | -20 | 112 | 5 | 66 | | +| 494 | 5 | 56 | 1 | 63 | -17 | 99 | 4 | 57 | 538 | 5 | 56 | 1 | 63 | -17 | 99 | 4 | 57 | | +| 495 | -2 | 66 | -4 | 70 | -78 | 127 | -4 | 71 | 539 | -2 | 66 | -4 | 70 | -78 | 127 | -4 | 71 | | +| 496 | 1 | 64 | 0 | 67 | -70 | 127 | -2 | 71 | 540 | 1 | 64 | 0 | 67 | -70 | 127 | -2 | 71 | | +| 497 | 0 | 61 | 2 | 57 | -50 | 127 | 2 | 58 | 641 | 0 | 61 | 2 | 57 | -50 | 127 | 2 | 58 | | +| 498 | -2 | 78 | -2 | 76 | -46 | 127 | -1 | 74 | 542 | -2 | 78 | -2 | 76 | -46 | 127 | -1 | 74 | | + +**Table 9-26 – Values of variables m and n for ctxIdx from 484 to 571** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | | +|--------|-----------------|-----|-------------------------|-----|-----|-----|-----|----|--------|-----------------|-----|-------------------------|-----|-----|-----|-----|----|--| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | | +| 499 | 1 | 50 | 11 | 35 | -4 | 66 | -4 | 44 | 543 | 1 | 50 | 11 | 35 | -4 | 66 | -4 | 44 | | +| 500 | 7 | 52 | 4 | 64 | -5 | 78 | -1 | 69 | 544 | 7 | 52 | 4 | 64 | -5 | 78 | -1 | 69 | | +| 501 | 10 | 35 | 1 | 61 | -4 | 71 | 0 | 62 | 545 | 10 | 35 | 1 | 61 | -4 | 71 | 0 | 62 | | +| 502 | 0 | 44 | 11 | 35 | -8 | 72 | -7 | 51 | 546 | 0 | 44 | 11 | 35 | -8 | 72 | -7 | 51 | | +| 503 | 11 | 38 | 18 | 25 | 2 | 59 | -4 | 47 | 547 | 11 | 38 | 18 | 25 | 2 | 59 | -4 | 47 | | +| 504 | 1 | 45 | 12 | 24 | -1 | 55 | -6 | 42 | 548 | 1 | 45 | 12 | 24 | -1 | 55 | -6 | 42 | | +| 505 | 0 | 46 | 13 | 29 | -7 | 70 | -3 | 41 | 549 | 0 | 46 | 13 | 29 | -7 | 70 | -3 | 41 | | +| 506 | 5 | 44 | 13 | 36 | -6 | 75 | -6 | 53 | 550 | 5 | 44 | 13 | 36 | -6 | 75 | -6 | 53 | | +| 507 | 31 | 17 | -10 | 93 | -8 | 89 | 8 | 76 | 551 | 31 | 17 | -10 | 93 | -8 | 89 | 8 | 76 | | +| 508 | 1 | 51 | -7 | 73 | -34 | 119 | -9 | 78 | 552 | 1 | 51 | -7 | 73 | -34 | 119 | -9 | 78 | | +| 509 | 7 | 50 | -2 | 73 | -3 | 75 | -11 | 83 | 553 | 7 | 50 | -2 | 73 | -3 | 75 | -11 | 83 | | +| 510 | 28 | 19 | 13 | 46 | 32 | 20 | 9 | 52 | 554 | 28 | 19 | 13 | 46 | 32 | 20 | 9 | 52 | | +| 511 | 16 | 33 | 9 | 49 | 30 | 22 | 0 | 67 | 555 | 16 | 33 | 9 | 49 | 30 | 22 | 0 | 67 | | +| 512 | 14 | 62 | -7 | 100 | -44 | 127 | -5 | 90 | 556 | 14 | 62 | -7 | 100 | -44 | 127 | -5 | 90 | | +| 513 | -13 | 108 | 9 | 53 | 0 | 54 | 1 | 67 | 557 | -13 | 108 | 9 | 53 | 0 | 54 | 1 | 67 | | +| 514 | -15 | 100 | 2 | 53 | -5 | 61 | -15 | 72 | 558 | -15 | 100 | 2 | 53 | -5 | 61 | -15 | 72 | | +| 515 | -13 | 101 | 5 | 53 | 0 | 58 | -5 | 75 | 559 | -13 | 101 | 5 | 53 | 0 | 58 | -5 | 75 | | +| 516 | -13 | 91 | -2 | 61 | -1 | 60 | -8 | 80 | 560 | -13 | 91 | -2 | 61 | -1 | 60 | -8 | 80 | | +| 517 | -12 | 94 | 0 | 56 | -3 | 61 | -21 | 83 | 561 | -12 | 94 | 0 | 56 | -3 | 61 | -21 | 83 | | +| 518 | -10 | 88 | 0 | 56 | -8 | 67 | -21 | 64 | 562 | -10 | 88 | 0 | 56 | -8 | 67 | -21 | 64 | | +| 519 | -16 | 84 | -13 | 63 | -25 | 84 | -13 | 31 | 563 | -16 | 84 | -13 | 63 | -25 | 84 | -13 | 31 | | +| 520 | -10 | 86 | -5 | 60 | -14 | 74 | -25 | 64 | 564 | -10 | 86 | -5 | 60 | -14 | 74 | -25 | 64 | | +| 521 | -7 | 83 | -1 | 62 | -5 | 65 | -29 | 94 | 565 | -7 | 83 | -1 | 62 | -5 | 65 | -29 | 94 | | +| 522 | -13 | 87 | 4 | 57 | 5 | 52 | 9 | 75 | 566 | -13 | 87 | 4 | 57 | 5 | 52 | 9 | 75 | | +| 523 | -19 | 94 | -6 | 69 | 2 | 57 | 17 | 63 | 567 | -19 | 94 | -6 | 69 | 2 | 57 | 17 | 63 | | +| 524 | 1 | 70 | 4 | 57 | 0 | 61 | -8 | 74 | 568 | 1 | 70 | 4 | 57 | 0 | 61 | -8 | 74 | | +| 525 | 0 | 72 | 14 | 39 | -9 | 69 | -5 | 35 | 569 | 0 | 72 | 14 | 39 | -9 | 69 | -5 | 35 | | +| 526 | -5 | 74 | 4 | 51 | -11 | 70 | -2 | 27 | 570 | -5 | 74 | 4 | 51 | -11 | 70 | -2 | 27 | | +| 527 | 18 | 59 | 13 | 68 | 18 | 55 | 13 | 91 | 571 | 18 | 59 | 13 | 68 | 18 | 55 | 13 | 91 | | + +Table 9-27 – Values of variables m and n for ctxIdx from 572 to 659 + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|--------|-----------------|-----|-------------------------|----|-----|-----|----|-----|--------|-----------------|-----|-------------------------|----|-----|-----|----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 572 | 24 | 0 | 11 | 28 | 4 | 45 | 4 | 39 | 616 | 24 | 0 | 11 | 28 | 4 | 45 | 4 | 39 | +| 573 | 15 | 9 | 2 | 40 | 10 | 28 | 0 | 42 | 617 | 15 | 9 | 2 | 40 | 10 | 28 | 0 | 42 | +| 574 | 8 | 25 | 3 | 44 | 10 | 31 | 7 | 34 | 618 | 8 | 25 | 3 | 44 | 10 | 31 | 7 | 34 | +| 575 | 13 | 18 | 0 | 49 | 33 | -11 | 11 | 29 | 619 | 13 | 18 | 0 | 49 | 33 | -11 | 11 | 29 | +| 576 | 15 | 9 | 0 | 46 | 52 | -43 | 8 | 31 | 620 | 15 | 9 | 0 | 46 | 52 | -43 | 8 | 31 | +| 577 | 13 | 19 | 2 | 44 | 18 | 15 | 6 | 37 | 621 | 13 | 19 | 2 | 44 | 18 | 15 | 6 | 37 | +| 578 | 10 | 37 | 2 | 51 | 28 | 0 | 7 | 42 | 622 | 10 | 37 | 2 | 51 | 28 | 0 | 7 | 42 | +| 579 | 12 | 18 | 0 | 47 | 35 | -22 | 3 | 40 | 623 | 12 | 18 | 0 | 47 | 35 | -22 | 3 | 40 | +| 580 | 6 | 29 | 4 | 39 | 38 | -25 | 8 | 33 | 624 | 6 | 29 | 4 | 39 | 38 | -25 | 8 | 33 | +| 581 | 20 | 33 | 2 | 62 | 34 | 0 | 13 | 43 | 625 | 20 | 33 | 2 | 62 | 34 | 0 | 13 | 43 | +| 582 | 15 | 30 | 6 | 46 | 39 | -18 | 13 | 36 | 626 | 15 | 30 | 6 | 46 | 39 | -18 | 13 | 36 | +| 583 | 4 | 45 | 0 | 54 | 32 | -12 | 4 | 47 | 627 | 4 | 45 | 0 | 54 | 32 | -12 | 4 | 47 | +| 584 | 1 | 58 | 3 | 54 | 102 | -94 | 3 | 55 | 628 | 1 | 58 | 3 | 54 | 102 | -94 | 3 | 55 | +| 585 | 0 | 62 | 2 | 58 | 0 | 0 | 2 | 58 | 629 | 0 | 62 | 2 | 58 | 0 | 0 | 2 | 58 | +| 586 | 7 | 61 | 4 | 63 | 56 | -15 | 6 | 60 | 630 | 7 | 61 | 4 | 63 | 56 | -15 | 6 | 60 | +| 587 | 12 | 38 | 6 | 51 | 33 | -4 | 8 | 44 | 631 | 12 | 38 | 6 | 51 | 33 | -4 | 8 | 44 | +| 588 | 11 | 45 | 6 | 57 | 29 | 10 | 11 | 44 | 632 | 11 | 45 | 6 | 57 | 29 | 10 | 11 | 44 | +| 589 | 15 | 39 | 7 | 53 | 37 | -5 | 14 | 42 | 633 | 15 | 39 | 7 | 53 | 37 | -5 | 14 | 42 | +| 590 | 11 | 42 | 6 | 52 | 51 | -29 | 7 | 48 | 634 | 11 | 42 | 6 | 52 | 51 | -29 | 7 | 48 | +| 591 | 13 | 44 | 6 | 55 | 39 | -9 | 4 | 56 | 635 | 13 | 44 | 6 | 55 | 39 | -9 | 4 | 56 | +| 592 | 16 | 45 | 11 | 45 | 52 | -34 | 4 | 52 | 636 | 16 | 45 | 11 | 45 | 52 | -34 | 4 | 52 | +| 593 | 12 | 41 | 14 | 36 | 69 | -58 | 13 | 37 | 637 | 12 | 41 | 14 | 36 | 69 | -58 | 13 | 37 | +| 594 | 10 | 49 | 8 | 53 | 67 | -63 | 9 | 49 | 638 | 10 | 49 | 8 | 53 | 67 | -63 | 9 | 49 | +| 595 | 30 | 34 | -1 | 82 | 44 | -5 | 19 | 58 | 639 | 30 | 34 | -1 | 82 | 44 | -5 | 19 | 58 | +| 596 | 18 | 42 | 7 | 55 | 32 | 7 | 10 | 48 | 640 | 18 | 42 | 7 | 55 | 32 | 7 | 10 | 48 | +| 597 | 10 | 55 | -3 | 78 | 55 | -29 | 12 | 45 | 641 | 10 | 55 | -3 | 78 | 55 | -29 | 12 | 45 | +| 598 | 17 | 51 | 15 | 46 | 32 | 1 | 0 | 69 | 642 | 17 | 51 | 15 | 46 | 32 | 1 | 0 | 69 | +| 599 | 17 | 46 | 22 | 31 | 0 | 0 | 20 | 33 | 643 | 17 | 46 | 22 | 31 | 0 | 0 | 20 | 33 | +| 600 | 0 | 89 | -1 | 84 | 27 | 36 | 8 | 63 | 644 | 0 | 89 | -1 | 84 | 27 | 36 | 8 | 63 | +| 601 | 26 | -19 | 25 | 7 | 33 | -25 | 35 | -18 | 645 | 26 | -19 | 25 | 7 | 33 | -25 | 35 | -18 | +| 602 | 22 | -17 | 30 | -7 | 34 | -30 | 33 | -25 | 646 | 22 | -17 | 30 | -7 | 34 | -30 | 33 | -25 | + +**Table 9-27 – Values of variables m and n for ctxIdx from 572 to 659** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|------------|-----------------|-----|-------------------------|----|----|-----|----|-----|------------|-----------------|-----|-------------------------|----|----|-----|----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 603 | 26 | -17 | 28 | 3 | 36 | -28 | 28 | -3 | 647 | 26 | -17 | 28 | 3 | 36 | -28 | 28 | -3 | +| 604 | 30 | -25 | 28 | 4 | 38 | -28 | 24 | 10 | 648 | 30 | -25 | 28 | 4 | 38 | -28 | 24 | 10 | +| 605 | 28 | -20 | 32 | 0 | 38 | -27 | 27 | 0 | 649 | 28 | -20 | 32 | 0 | 38 | -27 | 27 | 0 | +| 606 | 33 | -23 | 34 | -1 | 34 | -18 | 34 | -14 | 650 | 33 | -23 | 34 | -1 | 34 | -18 | 34 | -14 | +| 607 | 37 | -27 | 30 | 6 | 35 | -16 | 52 | -44 | 651 | 37 | -27 | 30 | 6 | 35 | -16 | 52 | -44 | +| 608 | 33 | -23 | 30 | 6 | 34 | -14 | 39 | -24 | 652 | 33 | -23 | 30 | 6 | 34 | -14 | 39 | -24 | +| 609 | 40 | -28 | 32 | 9 | 32 | -8 | 19 | 17 | 653 | 40 | -28 | 32 | 9 | 32 | -8 | 19 | 17 | +| 610 | 38 | -17 | 31 | 19 | 37 | -6 | 31 | 25 | 654 | 38 | -17 | 31 | 19 | 37 | -6 | 31 | 25 | +| 611 | 33 | -11 | 26 | 27 | 35 | 0 | 36 | 29 | 655 | 33 | -11 | 26 | 27 | 35 | 0 | 36 | 29 | +| 612 | 40 | -15 | 26 | 30 | 30 | 10 | 24 | 33 | 656 | 40 | -15 | 26 | 30 | 30 | 10 | 24 | 33 | +| 613 | 41 | -6 | 37 | 20 | 28 | 18 | 34 | 15 | 657 | 41 | -6 | 37 | 20 | 28 | 18 | 34 | 15 | +| 614 | 38 | 1 | 28 | 34 | 26 | 25 | 30 | 20 | 658 | 38 | 1 | 28 | 34 | 26 | 25 | 30 | 20 | +| 615 | 41 | 17 | 17 | 70 | 29 | 41 | 22 | 73 | 659 | 41 | 17 | 17 | 70 | 29 | 41 | 22 | 73 | + +Table 9-28 – Values of variables m and n for ctxIdx from 660 to 717 + +| ctxIdx | I slices | | Value of cabac_init_idc | | | | | | ctxIdx | I slices | | Value of cabac_init_idc | | | | | | +|--------|----------|-----|-------------------------|----|-----|----|-----|----|--------|----------|-----|-------------------------|-----|----|-----|-----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 660 | -17 | 120 | -4 | 79 | -5 | 85 | -3 | 78 | 689 | 2 | 59 | 2 | 59 | 2 | 58 | -11 | 68 | +| 661 | -20 | 112 | -7 | 71 | -6 | 81 | -8 | 74 | 690 | 23 | -13 | 9 | -2 | 17 | -10 | 9 | -2 | +| 662 | -18 | 114 | -5 | 69 | -10 | 77 | -9 | 72 | 691 | 26 | -13 | 26 | -9 | 32 | -13 | 30 | -10 | +| 663 | -11 | 85 | -9 | 70 | -7 | 81 | -10 | 72 | 692 | 40 | -15 | 33 | -9 | 42 | -9 | 31 | -4 | +| 664 | -15 | 92 | -8 | 66 | -17 | 80 | -18 | 75 | 693 | 49 | -14 | 39 | -7 | 49 | -5 | 33 | -1 | +| 665 | -14 | 89 | -10 | 68 | -18 | 73 | -12 | 71 | 694 | 44 | 3 | 41 | -2 | 53 | 0 | 33 | 7 | +| 666 | -26 | 71 | -19 | 73 | -4 | 74 | -11 | 63 | 695 | 45 | 6 | 45 | 3 | 64 | 3 | 31 | 12 | +| 667 | -15 | 81 | -12 | 69 | -10 | 83 | -5 | 70 | 696 | 44 | 34 | 49 | 9 | 68 | 10 | 37 | 23 | +| 668 | -14 | 80 | -16 | 70 | -9 | 71 | -17 | 75 | 697 | 33 | 54 | 45 | 27 | 66 | 27 | 31 | 38 | +| 669 | 0 | 68 | -15 | 67 | -9 | 67 | -14 | 72 | 698 | 19 | 82 | 36 | 59 | 47 | 57 | 20 | 64 | +| 670 | -14 | 70 | -20 | 62 | -1 | 61 | -16 | 67 | 699 | 21 | -10 | 21 | -13 | 17 | -10 | 9 | -2 | +| 671 | -24 | 56 | -19 | 70 | -8 | 66 | -8 | 53 | 700 | 24 | -11 | 33 | -14 | 32 | -13 | 30 | -10 | +| 672 | -23 | 68 | -16 | 66 | -14 | 66 | -14 | 59 | 701 | 28 | -8 | 39 | -7 | 42 | -9 | 31 | -4 | +| 673 | -24 | 50 | -22 | 65 | 0 | 59 | -9 | 52 | 702 | 28 | -1 | 46 | -2 | 49 | -5 | 33 | -1 | +| 674 | -11 | 74 | -20 | 63 | 2 | 59 | -11 | 68 | 703 | 29 | 3 | 51 | 2 | 53 | 0 | 33 | 7 | +| 675 | -14 | 106 | -5 | 85 | -3 | 81 | -3 | 78 | 704 | 29 | 9 | 60 | 6 | 64 | 3 | 31 | 12 | +| 676 | -13 | 97 | -6 | 81 | -3 | 76 | -8 | 74 | 705 | 35 | 20 | 61 | 17 | 68 | 10 | 37 | 23 | +| 677 | -15 | 90 | -10 | 77 | -7 | 72 | -9 | 72 | 706 | 29 | 36 | 55 | 34 | 66 | 27 | 31 | 38 | +| 678 | -12 | 90 | -7 | 81 | -6 | 78 | -10 | 72 | 707 | 14 | 67 | 42 | 62 | 47 | 57 | 20 | 64 | +| 679 | -18 | 88 | -17 | 80 | -12 | 72 | -18 | 75 | 708 | -3 | 75 | -6 | 66 | -5 | 71 | -9 | 71 | +| 680 | -10 | 73 | -18 | 73 | -14 | 68 | -12 | 71 | 709 | -1 | 23 | -7 | 35 | 0 | 24 | -7 | 37 | +| 681 | -9 | 79 | -4 | 74 | -3 | 70 | -11 | 63 | 710 | 1 | 34 | -7 | 42 | -1 | 36 | -8 | 44 | +| 682 | -14 | 86 | -10 | 83 | -6 | 76 | -5 | 70 | 711 | 1 | 43 | -8 | 45 | -2 | 42 | -11 | 49 | +| 683 | -10 | 73 | -9 | 71 | -5 | 66 | -17 | 75 | 712 | 0 | 54 | -5 | 48 | -2 | 52 | -10 | 56 | +| 684 | -10 | 70 | -9 | 67 | -5 | 62 | -14 | 72 | 713 | -2 | 55 | -12 | 56 | -9 | 57 | -12 | 59 | +| 685 | -10 | 69 | -1 | 61 | 0 | 57 | -16 | 67 | 714 | 0 | 61 | -6 | 60 | -6 | 63 | -8 | 63 | +| 686 | -5 | 66 | -8 | 66 | -4 | 61 | -8 | 53 | 715 | 1 | 64 | -5 | 62 | -4 | 65 | -9 | 67 | +| 687 | -9 | 64 | -14 | 66 | -9 | 60 | -14 | 59 | 716 | 0 | 68 | -8 | 66 | -4 | 67 | -6 | 68 | +| 688 | -5 | 58 | 0 | 59 | 1 | 54 | -9 | 52 | 717 | -9 | 92 | -8 | 76 | -7 | 82 | -10 | 79 | + +Table 9-29 – Values of variables m and n for ctxIdx from 718 to 775 + +| ctxIdx | I slices | | Value of cabac_init_idc | | | | | | ctxIdx | I slices | | Value of cabac_init_idc | | | | | | +|--------|----------|-----|-------------------------|----|-----|----|-----|----|--------|----------|-----|-------------------------|-----|----|-----|-----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 718 | -17 | 120 | -4 | 79 | -5 | 85 | -3 | 78 | 747 | 2 | 59 | 2 | 59 | 2 | 58 | -11 | 68 | +| 719 | -20 | 112 | -7 | 71 | -6 | 81 | -8 | 74 | 748 | 23 | -13 | 9 | -2 | 17 | -10 | 9 | -2 | +| 720 | -18 | 114 | -5 | 69 | -10 | 77 | -9 | 72 | 749 | 26 | -13 | 26 | -9 | 32 | -13 | 30 | -10 | +| 721 | -11 | 85 | -9 | 70 | -7 | 81 | -10 | 72 | 750 | 40 | -15 | 33 | -9 | 42 | -9 | 31 | -4 | +| 722 | -15 | 92 | -8 | 66 | -17 | 80 | -18 | 75 | 751 | 49 | -14 | 39 | -7 | 49 | -5 | 33 | -1 | +| 723 | -14 | 89 | -10 | 68 | -18 | 73 | -12 | 71 | 752 | 44 | 3 | 41 | -2 | 53 | 0 | 33 | 7 | +| 724 | -26 | 71 | -19 | 73 | -4 | 74 | -11 | 63 | 753 | 45 | 6 | 45 | 3 | 64 | 3 | 31 | 12 | +| 725 | -15 | 81 | -12 | 69 | -10 | 83 | -5 | 70 | 754 | 44 | 34 | 49 | 9 | 68 | 10 | 37 | 23 | +| 726 | -14 | 80 | -16 | 70 | -9 | 71 | -17 | 75 | 755 | 33 | 54 | 45 | 27 | 66 | 27 | 31 | 38 | +| 727 | 0 | 68 | -15 | 67 | -9 | 67 | -14 | 72 | 756 | 19 | 82 | 36 | 59 | 47 | 57 | 20 | 64 | +| 728 | -14 | 70 | -20 | 62 | -1 | 61 | -16 | 67 | 757 | 21 | -10 | 21 | -13 | 17 | -10 | 9 | -2 | +| 729 | -24 | 56 | -19 | 70 | -8 | 66 | -8 | 53 | 758 | 24 | -11 | 33 | -14 | 32 | -13 | 30 | -10 | +| 730 | -23 | 68 | -16 | 66 | -14 | 66 | -14 | 59 | 759 | 28 | -8 | 39 | -7 | 42 | -9 | 31 | -4 | +| 731 | -24 | 50 | -22 | 65 | 0 | 59 | -9 | 52 | 760 | 28 | -1 | 46 | -2 | 49 | -5 | 33 | -1 | +| 732 | -11 | 74 | -20 | 63 | 2 | 59 | -11 | 68 | 761 | 29 | 3 | 51 | 2 | 53 | 0 | 33 | 7 | +| 733 | -14 | 106 | -5 | 85 | -3 | 81 | -3 | 78 | 762 | 29 | 9 | 60 | 6 | 64 | 3 | 31 | 12 | +| 734 | -13 | 97 | -6 | 81 | -3 | 76 | -8 | 74 | 763 | 35 | 20 | 61 | 17 | 68 | 10 | 37 | 23 | +| 735 | -15 | 90 | -10 | 77 | -7 | 72 | -9 | 72 | 764 | 29 | 36 | 55 | 34 | 66 | 27 | 31 | 38 | +| 736 | -12 | 90 | -7 | 81 | -6 | 78 | -10 | 72 | 765 | 14 | 67 | 42 | 62 | 47 | 57 | 20 | 64 | +| 737 | -18 | 88 | -17 | 80 | -12 | 72 | -18 | 75 | 766 | -3 | 75 | -6 | 66 | -5 | 71 | -9 | 71 | +| 738 | -10 | 73 | -18 | 73 | -14 | 68 | -12 | 71 | 767 | -1 | 23 | -7 | 35 | 0 | 24 | -7 | 37 | +| 739 | -9 | 79 | -4 | 74 | -3 | 70 | -11 | 63 | 768 | 1 | 34 | -7 | 42 | -1 | 36 | -8 | 44 | +| 740 | -14 | 86 | -10 | 83 | -6 | 76 | -5 | 70 | 769 | 1 | 43 | -8 | 45 | -2 | 42 | -11 | 49 | +| 741 | -10 | 73 | -9 | 71 | -5 | 66 | -17 | 75 | 770 | 0 | 54 | -5 | 48 | -2 | 52 | -10 | 56 | +| 742 | -10 | 70 | -9 | 67 | -5 | 62 | -14 | 72 | 771 | -2 | 55 | -12 | 56 | -9 | 57 | -12 | 59 | +| 743 | -10 | 69 | -1 | 61 | 0 | 57 | -16 | 67 | 772 | 0 | 61 | -6 | 60 | -6 | 63 | -8 | 63 | +| 744 | -5 | 66 | -8 | 66 | -4 | 61 | -8 | 53 | 773 | 1 | 64 | -5 | 62 | -4 | 65 | -9 | 67 | +| 745 | -9 | 64 | -14 | 66 | -9 | 60 | -14 | 59 | 774 | 0 | 68 | -8 | 66 | -4 | 67 | -6 | 68 | +| 746 | -5 | 58 | 0 | 59 | 1 | 54 | -9 | 52 | 775 | -9 | 92 | -8 | 76 | -7 | 82 | -10 | 79 | + +**Table 9-30 – Values of variables m and n for ctxIdx from 776 to 863** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|--------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----|--------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 776 | -6 | 93 | -13 | 106 | -21 | 126 | -22 | 127 | 820 | -6 | 93 | -13 | 106 | -21 | 126 | -22 | 127 | +| 777 | -6 | 84 | -16 | 106 | -23 | 124 | -25 | 127 | 821 | -6 | 84 | -16 | 106 | -23 | 124 | -25 | 127 | +| 778 | -8 | 79 | -10 | 87 | -20 | 110 | -25 | 120 | 822 | -8 | 79 | -10 | 87 | -20 | 110 | -25 | 120 | +| 779 | 0 | 66 | -21 | 114 | -26 | 126 | -27 | 127 | 823 | 0 | 66 | -21 | 114 | -26 | 126 | -27 | 127 | +| 780 | -1 | 71 | -18 | 110 | -25 | 124 | -19 | 114 | 824 | -1 | 71 | -18 | 110 | -25 | 124 | -19 | 114 | +| 781 | 0 | 62 | -14 | 98 | -17 | 105 | -23 | 117 | 825 | 0 | 62 | -14 | 98 | -17 | 105 | -23 | 117 | +| 782 | -2 | 60 | -22 | 110 | -27 | 121 | -25 | 118 | 826 | -2 | 60 | -22 | 110 | -27 | 121 | -25 | 118 | +| 783 | -2 | 59 | -21 | 106 | -27 | 117 | -26 | 117 | 827 | -2 | 59 | -21 | 106 | -27 | 117 | -26 | 117 | +| 784 | -5 | 75 | -18 | 103 | -17 | 102 | -24 | 113 | 828 | -5 | 75 | -18 | 103 | -17 | 102 | -24 | 113 | +| 785 | -3 | 62 | -21 | 107 | -26 | 117 | -28 | 118 | 829 | -3 | 62 | -21 | 107 | -26 | 117 | -28 | 118 | +| 786 | -4 | 58 | -23 | 108 | -27 | 116 | -31 | 120 | 830 | -4 | 58 | -23 | 108 | -27 | 116 | -31 | 120 | +| 787 | -9 | 66 | -26 | 112 | -33 | 122 | -37 | 124 | 831 | -9 | 66 | -26 | 112 | -33 | 122 | -37 | 124 | +| 788 | -1 | 79 | -10 | 96 | -10 | 95 | -10 | 94 | 832 | -1 | 79 | -10 | 96 | -10 | 95 | -10 | 94 | +| 789 | 0 | 71 | -12 | 95 | -14 | 100 | -15 | 102 | 833 | 0 | 71 | -12 | 95 | -14 | 100 | -15 | 102 | +| 790 | 3 | 68 | -5 | 91 | -8 | 95 | -10 | 99 | 834 | 3 | 68 | -5 | 91 | -8 | 95 | -10 | 99 | +| 791 | 10 | 44 | -9 | 93 | -17 | 111 | -13 | 106 | 835 | 10 | 44 | -9 | 93 | -17 | 111 | -13 | 106 | +| 792 | -7 | 62 | -22 | 94 | -28 | 114 | -50 | 127 | 836 | -7 | 62 | -22 | 94 | -28 | 114 | -50 | 127 | +| 793 | 15 | 36 | -5 | 86 | -6 | 89 | -5 | 92 | 837 | 15 | 36 | -5 | 86 | -6 | 89 | -5 | 92 | +| 794 | 14 | 40 | 9 | 67 | -2 | 80 | 17 | 57 | 838 | 14 | 40 | 9 | 67 | -2 | 80 | 17 | 57 | +| 795 | 16 | 27 | -4 | 80 | -4 | 82 | -5 | 86 | 839 | 16 | 27 | -4 | 80 | -4 | 82 | -5 | 86 | +| 796 | 12 | 29 | -10 | 85 | -9 | 85 | -13 | 94 | 840 | 12 | 29 | -10 | 85 | -9 | 85 | -13 | 94 | +| 797 | 1 | 44 | -1 | 70 | -8 | 81 | -12 | 91 | 841 | 1 | 44 | -1 | 70 | -8 | 81 | -12 | 91 | +| 798 | 20 | 36 | 7 | 60 | -1 | 72 | -2 | 77 | 842 | 20 | 36 | 7 | 60 | -1 | 72 | -2 | 77 | +| 799 | 18 | 32 | 9 | 58 | 5 | 64 | 0 | 71 | 843 | 18 | 32 | 9 | 58 | 5 | 64 | 0 | 71 | +| 800 | 5 | 42 | 5 | 61 | 1 | 67 | -1 | 73 | 844 | 5 | 42 | 5 | 61 | 1 | 67 | -1 | 73 | +| 801 | 1 | 48 | 12 | 50 | 9 | 56 | 4 | 64 | 845 | 1 | 48 | 12 | 50 | 9 | 56 | 4 | 64 | +| 802 | 10 | 62 | 15 | 50 | 0 | 69 | -7 | 81 | 846 | 10 | 62 | 15 | 50 | 0 | 69 | -7 | 81 | +| 803 | 17 | 46 | 18 | 49 | 1 | 69 | 5 | 64 | 847 | 17 | 46 | 18 | 49 | 1 | 69 | 5 | 64 | +| 804 | 9 | 64 | 17 | 54 | 7 | 69 | 15 | 57 | 848 | 9 | 64 | 17 | 54 | 7 | 69 | 15 | 57 | +| 805 | -12 | 104 | 10 | 41 | -7 | 69 | 1 | 67 | 849 | -12 | 104 | 10 | 41 | -7 | 69 | 1 | 67 | +| 806 | -11 | 97 | 7 | 46 | -6 | 67 | 0 | 68 | 850 | -11 | 97 | 7 | 46 | -6 | 67 | 0 | 68 | + +**Table 9-30 – Values of variables m and n for ctxIdx from 776 to 863** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|------------|-----------------|----|-------------------------|----|-----|----|-----|----|------------|-----------------|----|-------------------------|----|-----|----|-----|----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 807 | -16 | 96 | -1 | 51 | -16 | 77 | -10 | 67 | 851 | -16 | 96 | -1 | 51 | -16 | 77 | -10 | 67 | +| 808 | -7 | 88 | 7 | 49 | -2 | 64 | 1 | 68 | 852 | -7 | 88 | 7 | 49 | -2 | 64 | 1 | 68 | +| 809 | -8 | 85 | 8 | 52 | 2 | 61 | 0 | 77 | 853 | -8 | 85 | 8 | 52 | 2 | 61 | 0 | 77 | +| 810 | -7 | 85 | 9 | 41 | -6 | 67 | 2 | 64 | 854 | -7 | 85 | 9 | 41 | -6 | 67 | 2 | 64 | +| 811 | -9 | 85 | 6 | 47 | -3 | 64 | 0 | 68 | 855 | -9 | 85 | 6 | 47 | -3 | 64 | 0 | 68 | +| 812 | -13 | 88 | 2 | 55 | 2 | 57 | -5 | 78 | 856 | -13 | 88 | 2 | 55 | 2 | 57 | -5 | 78 | +| 813 | 4 | 66 | 13 | 41 | -3 | 65 | 7 | 55 | 857 | 4 | 66 | 13 | 41 | -3 | 65 | 7 | 55 | +| 814 | -3 | 77 | 10 | 44 | -3 | 66 | 5 | 59 | 858 | -3 | 77 | 10 | 44 | -3 | 66 | 5 | 59 | +| 815 | -3 | 76 | 6 | 50 | 0 | 62 | 2 | 65 | 859 | -3 | 76 | 6 | 50 | 0 | 62 | 2 | 65 | +| 816 | -6 | 76 | 5 | 53 | 9 | 51 | 14 | 54 | 860 | -6 | 76 | 5 | 53 | 9 | 51 | 14 | 54 | +| 817 | 10 | 58 | 13 | 49 | -1 | 66 | 15 | 44 | 861 | 10 | 58 | 13 | 49 | -1 | 66 | 15 | 44 | +| 818 | -1 | 76 | 4 | 63 | -2 | 71 | 5 | 60 | 862 | -1 | 76 | 4 | 63 | -2 | 71 | 5 | 60 | +| 819 | -1 | 83 | 6 | 64 | -2 | 75 | 2 | 70 | 863 | -1 | 83 | 6 | 64 | -2 | 75 | 2 | 70 | + +**Table 9-31 – Values of variables m and n for ctxIdx from 864 to 951** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|------------|-----------------|-----|-------------------------|-----|----|-----|----|-----|------------|-----------------|-----|-------------------------|-----|----|-----|----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 864 | 15 | 6 | 14 | 11 | 19 | -6 | 17 | -13 | 908 | 15 | 6 | 14 | 11 | 19 | -6 | 17 | -13 | +| 865 | 6 | 19 | 11 | 14 | 18 | -6 | 16 | -9 | 909 | 6 | 19 | 11 | 14 | 18 | -6 | 16 | -9 | +| 866 | 7 | 16 | 9 | 11 | 14 | 0 | 17 | -12 | 910 | 7 | 16 | 9 | 11 | 14 | 0 | 17 | -12 | +| 867 | 12 | 14 | 18 | 11 | 26 | -12 | 27 | -21 | 911 | 12 | 14 | 18 | 11 | 26 | -12 | 27 | -21 | +| 868 | 18 | 13 | 21 | 9 | 31 | -16 | 37 | -30 | 912 | 18 | 13 | 21 | 9 | 31 | -16 | 37 | -30 | +| 869 | 13 | 11 | 23 | -2 | 33 | -25 | 41 | -40 | 913 | 13 | 11 | 23 | -2 | 33 | -25 | 41 | -40 | +| 870 | 13 | 15 | 32 | -15 | 33 | -22 | 42 | -41 | 914 | 13 | 15 | 32 | -15 | 33 | -22 | 42 | -41 | +| 871 | 15 | 16 | 32 | -15 | 37 | -28 | 48 | -47 | 915 | 15 | 16 | 32 | -15 | 37 | -28 | 48 | -47 | +| 872 | 12 | 23 | 34 | -21 | 39 | -30 | 39 | -32 | 916 | 12 | 23 | 34 | -21 | 39 | -30 | 39 | -32 | +| 873 | 13 | 23 | 39 | -23 | 42 | -30 | 46 | -40 | 917 | 13 | 23 | 39 | -23 | 42 | -30 | 46 | -40 | +| 874 | 15 | 20 | 42 | -33 | 47 | -42 | 52 | -51 | 918 | 15 | 20 | 42 | -33 | 47 | -42 | 52 | -51 | +| 875 | 14 | 26 | 41 | -31 | 45 | -36 | 46 | -41 | 919 | 14 | 26 | 41 | -31 | 45 | -36 | 46 | -41 | +| 876 | 14 | 44 | 46 | -28 | 49 | -34 | 52 | -39 | 920 | 14 | 44 | 46 | -28 | 49 | -34 | 52 | -39 | +| 877 | 17 | 40 | 38 | -12 | 41 | -17 | 43 | -19 | 921 | 17 | 40 | 38 | -12 | 41 | -17 | 43 | -19 | +| 878 | 17 | 47 | 21 | 29 | 32 | 9 | 32 | 11 | 922 | 17 | 47 | 21 | 29 | 32 | 9 | 32 | 11 | +| 879 | 24 | 17 | 45 | -24 | 69 | -71 | 61 | -55 | 923 | 24 | 17 | 45 | -24 | 69 | -71 | 61 | -55 | +| 880 | 21 | 21 | 53 | -45 | 63 | -63 | 56 | -46 | 924 | 21 | 21 | 53 | -45 | 63 | -63 | 56 | -46 | +| 881 | 25 | 22 | 48 | -26 | 66 | -64 | 62 | -50 | 925 | 25 | 22 | 48 | -26 | 66 | -64 | 62 | -50 | +| 882 | 31 | 27 | 65 | -43 | 77 | -74 | 81 | -67 | 926 | 31 | 27 | 65 | -43 | 77 | -74 | 81 | -67 | +| 883 | 22 | 29 | 43 | -19 | 54 | -39 | 45 | -20 | 927 | 22 | 29 | 43 | -19 | 54 | -39 | 45 | -20 | +| 884 | 19 | 35 | 39 | -10 | 52 | -35 | 35 | -2 | 928 | 19 | 35 | 39 | -10 | 52 | -35 | 35 | -2 | +| 885 | 14 | 50 | 30 | 9 | 41 | -10 | 28 | 15 | 929 | 14 | 50 | 30 | 9 | 41 | -10 | 28 | 15 | +| 886 | 10 | 57 | 18 | 26 | 36 | 0 | 34 | 1 | 930 | 10 | 57 | 18 | 26 | 36 | 0 | 34 | 1 | +| 887 | 7 | 63 | 20 | 27 | 40 | -1 | 39 | 1 | 931 | 7 | 63 | 20 | 27 | 40 | -1 | 39 | 1 | +| 888 | -2 | 77 | 0 | 57 | 30 | 14 | 30 | 17 | 932 | -2 | 77 | 0 | 57 | 30 | 14 | 30 | 17 | +| 889 | -4 | 82 | -14 | 82 | 28 | 26 | 20 | 38 | 933 | -4 | 82 | -14 | 82 | 28 | 26 | 20 | 38 | +| 890 | -3 | 94 | -5 | 75 | 23 | 37 | 18 | 45 | 934 | -3 | 94 | -5 | 75 | 23 | 37 | 18 | 45 | +| 891 | 9 | 69 | -19 | 97 | 12 | 55 | 15 | 54 | 935 | 9 | 69 | -19 | 97 | 12 | 55 | 15 | 54 | +| 892 | -12 | 109 | -35 | 125 | 11 | 65 | 0 | 79 | 936 | -12 | 109 | -35 | 125 | 11 | 65 | 0 | 79 | +| 893 | 36 | -35 | 27 | 0 | 37 | -33 | 36 | -16 | 937 | 36 | -35 | 27 | 0 | 37 | -33 | 36 | -16 | +| 894 | 36 | -34 | 28 | 0 | 39 | -36 | 37 | -14 | 938 | 36 | -34 | 28 | 0 | 39 | -36 | 37 | -14 | + +**Table 9-31 – Values of variables m and n for ctxIdx from 864 to 951** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | +|------------|-----------------|-----|-------------------------|----|----|-----|----|-----|------------|-----------------|-----|-------------------------|----|----|-----|----|-----| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | n | m | n | +| 895 | 32 | -26 | 31 | -4 | 40 | -37 | 37 | -17 | 939 | 32 | -26 | 31 | -4 | 40 | -37 | 37 | -17 | +| 896 | 37 | -30 | 27 | 6 | 38 | -30 | 32 | 1 | 940 | 37 | -30 | 27 | 6 | 38 | -30 | 32 | 1 | +| 897 | 44 | -32 | 34 | 8 | 46 | -33 | 34 | 15 | 941 | 44 | -32 | 34 | 8 | 46 | -33 | 34 | 15 | +| 898 | 34 | -18 | 30 | 10 | 42 | -30 | 29 | 15 | 942 | 34 | -18 | 30 | 10 | 42 | -30 | 29 | 15 | +| 899 | 34 | -15 | 24 | 22 | 40 | -24 | 24 | 25 | 943 | 34 | -15 | 24 | 22 | 40 | -24 | 24 | 25 | +| 900 | 40 | -15 | 33 | 19 | 49 | -29 | 34 | 22 | 944 | 40 | -15 | 33 | 19 | 49 | -29 | 34 | 22 | +| 901 | 33 | -7 | 22 | 32 | 38 | -12 | 31 | 16 | 945 | 33 | -7 | 22 | 32 | 38 | -12 | 31 | 16 | +| 902 | 35 | -5 | 26 | 31 | 40 | -10 | 35 | 18 | 946 | 35 | -5 | 26 | 31 | 40 | -10 | 35 | 18 | +| 903 | 33 | 0 | 21 | 41 | 38 | -3 | 31 | 28 | 947 | 33 | 0 | 21 | 41 | 38 | -3 | 31 | 28 | +| 904 | 38 | 2 | 26 | 44 | 46 | -5 | 33 | 41 | 948 | 38 | 2 | 26 | 44 | 46 | -5 | 33 | 41 | +| 905 | 33 | 13 | 23 | 47 | 31 | 20 | 36 | 28 | 949 | 33 | 13 | 23 | 47 | 31 | 20 | 36 | 28 | +| 906 | 23 | 35 | 16 | 65 | 29 | 30 | 27 | 47 | 950 | 23 | 35 | 16 | 65 | 29 | 30 | 27 | 47 | +| 907 | 13 | 58 | 14 | 71 | 25 | 44 | 21 | 62 | 951 | 13 | 58 | 14 | 71 | 25 | 44 | 21 | 62 | + +**Table 9-32 – Values of variables m and n for ctxIdx from 952 to 1011** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | | +|------------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----|-------------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----|--| +| | m | n | 0 | | 1 | | 2 | | | m | n | 0 | | 1 | | 2 | | | +| | | | m | n | m | n | m | n | | | | m | n | m | n | m | n | | +| 952 | -3 | 71 | -6 | 76 | -23 | 112 | -24 | 115 | 982 | -3 | 71 | -6 | 76 | -23 | 112 | -24 | 115 | | +| 953 | -6 | 42 | -2 | 44 | -15 | 71 | -22 | 82 | 983 | -6 | 42 | -2 | 44 | -15 | 71 | -22 | 82 | | +| 954 | -5 | 50 | 0 | 45 | -7 | 61 | -9 | 62 | 984 | -5 | 50 | 0 | 45 | -7 | 61 | -9 | 62 | | +| 955 | -3 | 54 | 0 | 52 | 0 | 53 | 0 | 53 | 985 | -3 | 54 | 0 | 52 | 0 | 53 | 0 | 53 | | +| 956 | -2 | 62 | -3 | 64 | -5 | 66 | 0 | 59 | 986 | -2 | 62 | -3 | 64 | -5 | 66 | 0 | 59 | | +| 957 | 0 | 58 | -2 | 59 | -11 | 77 | -14 | 85 | 987 | 0 | 58 | -2 | 59 | -11 | 77 | -14 | 85 | | +| 958 | 1 | 63 | -4 | 70 | -9 | 80 | -13 | 89 | 988 | 1 | 63 | -4 | 70 | -9 | 80 | -13 | 89 | | +| 959 | -2 | 72 | -4 | 75 | -9 | 84 | -13 | 94 | 989 | -2 | 72 | -4 | 75 | -9 | 84 | -13 | 94 | | +| 960 | -1 | 74 | -8 | 82 | -10 | 87 | -11 | 92 | 990 | -1 | 74 | -8 | 82 | -10 | 87 | -11 | 92 | | +| 961 | -9 | 91 | -17 | 102 | -34 | 127 | -29 | 127 | 991 | -9 | 91 | -17 | 102 | -34 | 127 | -29 | 127 | | +| 962 | -5 | 67 | -9 | 77 | -21 | 101 | -21 | 100 | 992 | -5 | 67 | -9 | 77 | -21 | 101 | -21 | 100 | | +| 963 | -5 | 27 | 3 | 24 | -3 | 39 | -14 | 57 | 993 | -5 | 27 | 3 | 24 | -3 | 39 | -14 | 57 | | +| 964 | -3 | 39 | 0 | 42 | -5 | 53 | -12 | 67 | 994 | -3 | 39 | 0 | 42 | -5 | 53 | -12 | 67 | | +| 965 | -2 | 44 | 0 | 48 | -7 | 61 | -11 | 71 | 995 | -2 | 44 | 0 | 48 | -7 | 61 | -11 | 71 | | +| 966 | 0 | 46 | 0 | 55 | -11 | 75 | -10 | 77 | 996 | 0 | 46 | 0 | 55 | -11 | 75 | -10 | 77 | | +| 967 | -16 | 64 | -6 | 59 | -15 | 77 | -21 | 85 | 997 | -16 | 64 | -6 | 59 | -15 | 77 | -21 | 85 | | +| 968 | -8 | 68 | -7 | 71 | -17 | 91 | -16 | 88 | 998 | -8 | 68 | -7 | 71 | -17 | 91 | -16 | 88 | | +| 969 | -10 | 78 | -12 | 83 | -25 | 107 | -23 | 104 | 999 | -10 | 78 | -12 | 83 | -25 | 107 | -23 | 104 | | +| 970 | -6 | 77 | -11 | 87 | -25 | 111 | -15 | 98 | 1000 | -6 | 77 | -11 | 87 | -25 | 111 | -15 | 98 | | +| 971 | -10 | 86 | -30 | 119 | -28 | 122 | -37 | 127 | 1001 | -10 | 86 | -30 | 119 | -28 | 122 | -37 | 127 | | +| 972 | -12 | 92 | 1 | 58 | -11 | 76 | -10 | 82 | 1002 | -12 | 92 | 1 | 58 | -11 | 76 | -10 | 82 | | +| 973 | -15 | 55 | -3 | 29 | -10 | 44 | -8 | 48 | 1003 | -15 | 55 | -3 | 29 | -10 | 44 | -8 | 48 | | +| 974 | -10 | 60 | -1 | 36 | -10 | 52 | -8 | 61 | 1004 | -10 | 60 | -1 | 36 | -10 | 52 | -8 | 61 | | +| 975 | -6 | 62 | 1 | 38 | -10 | 57 | -8 | 66 | 1005 | -6 | 62 | 1 | 38 | -10 | 57 | -8 | 66 | | +| 976 | -4 | 65 | 2 | 43 | -9 | 58 | -7 | 70 | 1006 | -4 | 65 | 2 | 43 | -9 | 58 | -7 | 70 | | +| 977 | -12 | 73 | -6 | 55 | -16 | 72 | -14 | 75 | 1007 | -12 | 73 | -6 | 55 | -16 | 72 | -14 | 75 | | +| 978 | -8 | 76 | 0 | 58 | -7 | 69 | -10 | 79 | 1008 | -8 | 76 | 0 | 58 | -7 | 69 | -10 | 79 | | +| 979 | -7 | 80 | 0 | 64 | -4 | 69 | -9 | 83 | 1009 | -7 | 80 | 0 | 64 | -4 | 69 | -9 | 83 | | +| 980 | -9 | 88 | -3 | 74 | -5 | 74 | -12 | 92 | 1010 | -9 | 88 | -3 | 74 | -5 | 74 | -12 | 92 | | +| 981 | -17 | 110 | -10 | 90 | -9 | 86 | -18 | 108 | 1011 | -17 | 110 | -10 | 90 | -9 | 86 | -18 | 108 | | + +**Table 9-33 – Values of variables m and n for ctxIdx from 1012 to 1023** + +| ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | ctxIdx | I and SI slices | | Value of cabac_init_idc | | | | | | | +|-------------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----|-------------|-----------------|-----|-------------------------|-----|-----|-----|-----|-----|--| +| | | | 0 | | 1 | | 2 | | | | | 0 | | 1 | | 2 | | | +| | m | n | m | n | m | n | m | n | | m | n | m | n | m | N | m | n | | +| 1012 | -3 | 70 | -3 | 74 | -2 | 73 | -5 | 79 | 1018 | -10 | 90 | -8 | 87 | -9 | 91 | -11 | 91 | | +| 1013 | -8 | 93 | -9 | 92 | -12 | 104 | -11 | 104 | 1019 | -30 | 127 | -23 | 126 | -31 | 127 | -30 | 127 | | +| 1014 | -10 | 90 | -8 | 87 | -9 | 91 | -11 | 91 | 1020 | -3 | 70 | -3 | 74 | -2 | 73 | -5 | 79 | | +| 1015 | -30 | 127 | -23 | 126 | -31 | 127 | -30 | 127 | 1021 | -8 | 93 | -9 | 92 | -12 | 104 | -11 | 104 | | +| 1016 | -3 | 70 | -3 | 74 | -2 | 73 | -5 | 79 | 1022 | -10 | 90 | -8 | 87 | -9 | 91 | -11 | 91 | | +| 1017 | -8 | 93 | -9 | 92 | -12 | 104 | -11 | 104 | 1023 | -30 | 127 | -23 | 126 | -31 | 127 | -30 | 127 | | + +**9.3.1.2 Initialization process for the arithmetic decoding engine** + +This process is invoked before decoding the first macroblock of a slice or after the decoding of any pcm\_alignment\_zero\_bit and all pcm\_sample\_luma and pcm\_sample\_chroma data for a macroblock of type I\_PCM. + +Outputs of this process are the initialized decoding engine registers codIRange and codIOffset both in 16-bit register precision. + +The status of the arithmetic decoding engine is represented by the variables codIRange and codIOffset. In the initialization procedure of the arithmetic decoding process, codIRange is set equal to 510 and codIOffset is set equal to the value returned from read\_bits( 9 ) interpreted as a 9 bit binary representation of an unsigned integer with most significant bit written first. + +The bitstream shall not contain data that result in a value of codIOffset being equal to 510 or 511. + +NOTE – The description of the arithmetic decoding engine in this Recommendation | International Standard utilizes 16-bit register precision. However, a minimum register precision of 9 bits is required for storing the values of the variables codIRange and codIOffset after invocation of the arithmetic decoding process (DecodeBin) as specified in clause 9.3.3.2. The arithmetic decoding process for a binary decision (DecodeDecision) as specified in clause 9.3.3.2.1 and the decoding process for a binary decision before termination (DecodeTerminate) as specified in clause 9.3.3.2.4 require a minimum register precision of 9 bits for the variables codIRange and codIOffset. The bypass decoding process for binary decisions (DecodeBypass) as specified in clause 9.3.3.2.3 requires a minimum register precision of 10 bits for the variable codIOffset and a minimum register precision of 9 bits for the variable codIRange. + +**9.3.2 Binarization process** + +Input to this process is a request for a syntax element. + +Output of this process is the binarization of the syntax element, maxBinIdxCtx, ctxIdxOffset, and bypassFlag. + +Table 9-34 specifies the type of binarization process, maxBinIdxCtx, and ctxIdxOffset associated with each syntax element. + +The specification of the unary (U) binarization process, the truncated unary (TU) binarization process, the concatenated unary / k-th order Exp-Golomb (UEGk) binarization process, and the fixed-length (FL) binarization process are given in clauses 9.3.2.1 to 9.3.2.4, respectively. Other binarizations are specified in clauses 9.3.2.5 to 9.3.2.7. + +Except for I slices, the binarizations for the syntax element mb\_type as specified in clause 9.3.2.5 consist of bin strings given by a concatenation of prefix and suffix bit strings. The UEGk binarization as specified in clause 9.3.2.3, which is used for the binarization of the syntax elements mvd\_IX (X = 0, 1) and coeff\_abs\_level\_minus1, and the binarization of the coded\_block\_pattern also consist of a concatenation of prefix and suffix bit strings. For these binarization processes, the prefix and the suffix bit string are separately indexed using the binIdx variable as specified further in clause 9.3.3. The two sets of prefix bit strings and suffix bit strings are referred to as the binarization prefix part and the binarization suffix part, respectively. + +Associated with each binarization or binarization part of a syntax element is a specific value of the context index offset (ctxIdxOffset) variable and a specific value of the maxBinIdxCtx variable as given in Table 9-34. When two values for each of these variables are specified for one syntax element in Table 9-34, the value in the upper row is related to the prefix part while the value in the lower row is related to the suffix part of the binarization of the corresponding syntax element. + +The use of the DecodeBypass process and the variable bypassFlag is derived as follows: + +- If no value is assigned to ctxIdxOffset for the corresponding binarization or binarization part in Table 9-34 labelled as "na", all bins of the bit strings of the corresponding binarization or of the binarization prefix/suffix part are decoded by invoking the DecodeBypass process as specified in clause 9.3.3.2.3. In such a case, bypassFlag is set equal to 1, where bypassFlag is used to indicate that for parsing the value of the bin from the bitstream the DecodeBypass process is applied. +- Otherwise, for each possible value of binIdx up to the specified value of maxBinIdxCtx given in Table 9-34, a specific value of the variable ctxIdx is further specified in clause 9.3.3. bypassFlag is set equal to 0. + +The possible values of the context index ctxIdx are in the range 0 to 1023, inclusive. The value assigned to ctxIdxOffset specifies the lower value of the range of ctxIdx assigned to the corresponding binarization or binarization part of a syntax element. + +ctxIdx = ctxIdxOffset = 276 is assigned to the syntax element end\_of\_slice\_flag and the bin of mb\_type, which specifies the I\_PCM macroblock type as further specified in clause 9.3.3.1. For parsing the value of the corresponding bin from the bitstream, the arithmetic decoding process for decisions before termination (DecodeTerminate) as specified in clause 9.3.3.2.4 is applied. + +NOTE – The bins of mb\_type in I slices and the bins of the suffix for mb\_type in SI slices that correspond to the same value of binIdx share the same ctxIdx. The last bin of the prefix of mb\_type and the first bin of the suffix of mb\_type in P, SP, and B slices may share the same ctxIdx. + +**Table 9-34 – Syntax elements and associated types of binarization, maxBinIdxCtx, and ctxIdxOffset** + +| Syntax element | Type of binarization | maxBinIdxCtx | ctxIdxOffset | +|---------------------------------------------------------------|---------------------------------------------------------------------|-------------------------|----------------------------------------------| +| mb_type
(SI slices only) | prefix and suffix
as specified in clause 9.3.2.5 | prefix: 0
suffix: 6 | prefix: 0
suffix: 3 | +| mb_type (I slices only) | as specified in clause 9.3.2.5 | 6 | 3 | +| mb_skip_flag
(P, SP slices only) | FL, cMax=1 | 0 | 11 | +| mb_type (P, SP slices only) | prefix and suffix
as specified in clause 9.3.2.5 | prefix: 2
suffix: 5 | prefix: 14
suffix: 17 | +| sub_mb_type[ ]
(P, SP slices only) | as specified in clause 9.3.2.5 | 2 | 21 | +| mb_skip_flag
(B slices only) | FL, cMax=1 | 0 | 24 | +| mb_type (B slices only) | prefix and suffix
as specified in clause 9.3.2.5 | prefix: 3
suffix: 5 | prefix: 27
suffix: 32 | +| sub_mb_type[ ] (B slices only) | as specified in clause 9.3.2.5 | 3 | 36 | +| mvd_l0[ ][ ][ 0 ], mvd_l1[ ][ ][ 0 ] | prefix and suffix as given by UEG3
with signedValFlag=1, uCoff=9 | prefix: 4
suffix: na | prefix: 40
suffix: na (uses DecodeBypass) | +| mvd_l0[ ][ ][ 1 ], mvd_l1[ ][ ][ 1 ] | | prefix: 4
suffix: na | prefix: 47
suffix: na (uses DecodeBypass) | +| ref_idx_l0, ref_idx_l1 | U | 2 | 54 | +| mb_qp_delta | as specified in clause 9.3.2.7 | 2 | 60 | +| intra_chroma_pred_mode | TU, cMax=3 | 1 | 64 | +| prev_intra4x4_pred_mode_flag,
prev_intra8x8_pred_mode_flag | FL, cMax=1 | 0 | 68 | +| rem_intra4x4_pred_mode,
rem_intra8x8_pred_mode | FL, cMax=7 | 0 | 69 | +| mb_field_decoding_flag | FL, cMax=1 | 0 | 70 | + +**Table 9-34 – Syntax elements and associated types of binarization, maxBinIdxCtx, and ctxIdxOffset** + +| Syntax element | Type of binarization | maxBinIdxCtx | ctxIdxOffset | +|------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------|------------------------------------------------| +| coded_block_pattern | prefix and suffix as specified in clause 9.3.2.6 | prefix: 3
suffix: 1 | prefix: 73
suffix: 77 | +| coded_block_flag
(blocks with ctxBlockCat < 5) | FL, cMax=1 | 0 | 85 | +| significant_coeff_flag
(frame coded blocks with ctxBlockCat < 5) | FL, cMax=1 | 0 | 105 | +| last_significant_coeff_flag
(frame coded blocks with ctxBlockCat < 5) | FL, cMax=1 | 0 | 166 | +| coeff_abs_level_minus1
(blocks with ctxBlockCat < 5) | prefix and suffix as given by UEGO with signedValFlag=0, uCoff=14 | prefix: 1
suffix: na | prefix: 227
suffix: na, (uses DecodeBypass) | +| coeff_sign_flag | FL, cMax=1 | 0 | na, (uses DecodeBypass) | +| end_of_slice_flag | FL, cMax=1 | 0 | 276 | +| significant_coeff_flag
(field coded blocks with ctxBlockCat < 5) | FL, cMax=1 | 0 | 277 | +| last_significant_coeff_flag
(field coded blocks with ctxBlockCat < 5) | FL, cMax=1 | 0 | 338 | +| transform_size_8x8_flag | FL, cMax=1 | 0 | 399 | +| significant_coeff_flag
(frame coded blocks with ctxBlockCat == 5) | FL, cMax=1 | 0 | 402 | +| last_significant_coeff_flag
(frame coded blocks with ctxBlockCat == 5) | FL, cMax=1 | 0 | 417 | +| coeff_abs_level_minus1
(blocks with ctxBlockCat == 5) | prefix and suffix as given by UEGO with signedValFlag=0, uCoff=14 | prefix: 1
suffix: na | prefix: 426
suffix: na, (uses DecodeBypass) | +| significant_coeff_flag
(field coded blocks with ctxBlockCat == 5) | FL, cMax=1 | 0 | 436 | +| last_significant_coeff_flag
(field coded blocks with ctxBlockCat == 5) | FL, cMax=1 | 0 | 451 | +| coded_block_flag
(5 < ctxBlockCat < 9) | FL, cMax=1 | 0 | 460 | +| coded_block_flag
(9 < ctxBlockCat < 13) | FL, cMax=1 | 0 | 472 | +| coded_block_flag
(ctxBlockCat == 5, 9, or 13) | FL, cMax=1 | 0 | 1012 | +| significant_coeff_flag
(frame coded blocks with 5 < ctxBlockCat < 9) | FL, cMax=1 | 0 | 484 | +| significant_coeff_flag
(frame coded blocks with 9 < ctxBlockCat < 13) | FL, cMax=1 | 0 | 528 | +| last_significant_coeff_flag
(frame coded blocks with 5 < ctxBlockCat < 9) | FL, cMax=1 | 0 | 572 | + +**Table 9-34 – Syntax elements and associated types of binarization, maxBinIdxCtx, and ctxIdxOffset** + +| Syntax element | Type of binarization | maxBinIdxCtx | ctxIdxOffset | +|-------------------------------------------------------------------------------------|----------------------------------------------------------------------|-------------------------|------------------------------------------------| +| last_significant_coeff_flag
(frame coded blocks with
$9 < ctxBlockCat < 13$ ) | FL, cMax=1 | 0 | 616 | +| coeff_abs_level_minus1
(blocks with $5 < ctxBlockCat < 9$ ) | prefix and suffix as given by UEG0
with signedValFlag=0, uCoff=14 | prefix: 1
suffix: na | prefix: 952
suffix: na, (uses DecodeBypass) | +| coeff_abs_level_minus1
(blocks with $9 < ctxBlockCat < 13$ ) | prefix and suffix as given by UEG0
with signedValFlag=0, uCoff=14 | prefix: 1
suffix: na | prefix: 982
suffix: na, (uses DecodeBypass) | +| significant_coeff_flag
(field coded blocks with $5 < ctxBlockCat < 9$ ) | FL, cMax=1 | 0 | 776 | +| significant_coeff_flag
(field coded blocks with
$9 < ctxBlockCat < 13$ ) | FL, cMax=1 | 0 | 820 | +| last_significant_coeff_flag
(field coded blocks with $5 < ctxBlockCat < 9$ ) | FL, cMax=1 | 0 | 864 | +| last_significant_coeff_flag
(field coded blocks with
$9 < ctxBlockCat < 13$ ) | FL, cMax=1 | 0 | 908 | +| significant_coeff_flag
(frame coded blocks with $ctxBlockCat == 9$ ) | FL, cMax=1 | 0 | 660 | +| significant_coeff_flag
(frame coded blocks with
$ctxBlockCat == 13$ ) | FL, cMax=1 | 0 | 718 | +| last_significant_coeff_flag
(frame coded blocks with $ctxBlockCat == 9$ ) | FL, cMax=1 | 0 | 690 | +| last_significant_coeff_flag
(frame coded blocks with
$ctxBlockCat == 13$ ) | FL, cMax=1 | 0 | 748 | +| coeff_abs_level_minus1
(blocks with $ctxBlockCat == 9$ ) | prefix and suffix as given by UEG0
with signedValFlag=0, uCoff=14 | prefix: 1
suffix: na | prefix: 708
suffix: na, (uses DecodeBypass) | +| coeff_abs_level_minus1
(blocks with $ctxBlockCat == 13$ ) | prefix and suffix as given by UEG0
with signedValFlag=0, uCoff=14 | prefix: 1
suffix: na | prefix: 766
suffix: na, (uses DecodeBypass) | +| significant_coeff_flag
(field coded blocks with $ctxBlockCat == 9$ ) | FL, cMax=1 | 0 | 675 | +| significant_coeff_flag
(field coded blocks with $ctxBlockCat == 13$ ) | FL, cMax=1 | 0 | 733 | +| last_significant_coeff_flag
(field coded blocks with $ctxBlockCat == 9$ ) | FL, cMax=1 | 0 | 699 | +| last_significant_coeff_flag
(field coded blocks with $ctxBlockCat == 13$ ) | FL, cMax=1 | 0 | 757 | + +### 9.3.2.1 Unary (U) binarization process + +Input to this process is a request for a U binarization for a syntax element. + +Output of this process is the U binarization of the syntax element. + +The bin string of a syntax element having (unsigned integer) value synElVal is a bit string of length synElVal + 1 indexed by binIdx. The bins for binIdx less than synElVal are equal to 1. The bin with binIdx equal to synElVal is equal to 0. + +Table 9-35 illustrates the bin strings of the unary binarization for a syntax element. + +**Table 9-35 – Bin string of the unary binarization (informative)** + +| Value of syntax element | Bin string | | | | | | +|-------------------------|------------|-----|-------|---------|-----------|-------------| +| | 0 | 1 | 2 | 3 | 4 | 5 | +| 0 (I_NxN) | 0 | | | | | | +| 1 | | 1 0 | | | | | +| 2 | | | 1 1 0 | | | | +| 3 | | | | 1 1 1 0 | | | +| 4 | | | | | 1 1 1 1 0 | | +| 5 | | | | | | 1 1 1 1 1 0 | +| ... | | | | | | | +| binIdx | 0 | 1 | 2 | 3 | 4 | 5 | + +**9.3.2.2 Truncated unary (TU) binarization process** + +Input to this process is a request for a TU binarization for a syntax element and cMax. + +Output of this process is the TU binarization of the syntax element. + +For syntax element (unsigned integer) values less than cMax, the U binarization process as specified in clause 9.3.2.1 is invoked. For the syntax element value equal to cMax the bin string is a bit string of length cMax with all bins being equal to 1. + +NOTE – TU binarization is always invoked with a cMax value equal to the largest possible value of the syntax element being decoded. + +**9.3.2.3 Concatenated unary/ k-th order Exp-Golomb (UEGk) binarization process** + +Input to this process is a request for a UEGk binarization for a syntax element, signedValFlag and uCoff. + +Output of this process is the UEGk binarization of the syntax element. + +A UEGk bin string is a concatenation of a prefix bit string and a suffix bit string. The prefix of the binarization is specified by invoking the TU binarization process for the prefix part Min( uCoff, Abs( synEIVal ) ) of a syntax element value synEIVal as specified in clause 9.3.2.2 with cMax = uCoff, where uCoff > 0. + +The variable k for a UEGk bin string is dependent on the syntax element for which a UEGk binarization is requested. Table 9-34 specifies the associated types of binarization for syntax elements, including the value of k for syntax elements that use UEGk binarization. + +NOTE 1 – For the syntax elements mvd\_10[ ][ ][ ] and mvd\_11[ ][ ][ ] a UEG3 binarization is used (k is equal to 3). For the syntax element coeff\_abs\_level\_minus1 a UEG0 binarization is used (k is equal to 0). + +The UEGk bin string is derived as follows: + +- If one of the following is true, the bin string of a syntax element having value synEIVal consists only of a prefix bit string: + - signedValFlag is equal to 0 and the prefix bit string is not equal to the bit string of length uCoff with all bits equal to 1, + - signedValFlag is equal to 1 and the prefix bit string is equal to the bit string that consists of a single bit with value equal to 0. + +- Otherwise, the bin string of the UEGk suffix part of a syntax element value synEIVal is specified by a process equivalent to the following pseudo-code with k being initialized to the value that is specified in Table 9-34 for the requested UEGk binarization process. At the beginning of the following pseudo-code, the bin string of a syntax element having value synEIVal is set equal to the empty string. Each call of the function put( X ), with X being equal to 0 or 1, adds the binary value X at the end of the bin string. + +``` + +if( Abs( synEIVal ) >= uCoff ) { + sufS = Abs( synEIVal ) - uCoff + stopLoop = 0 + do { + if( sufS >= ( 1 << k ) ) { + put( 1 ) + sufS = sufS - ( 1 << k ) + k++ + } else { + put( 0 ) + while( k-- ) + put( ( sufS >> k ) & 1 ) + stopLoop = 1 + } + } while( !stopLoop ) +} +if( signedValFlag && synEIVal != 0 ) + if( synEIVal > 0 ) + put( 0 ) + else + put( 1 ) + +``` + +(9-6) + +NOTE 2 – The specification for the k-th order Exp-Golomb (EGk) code uses 1's and 0's in reverse meaning for the unary part of the Exp-Golomb code of 0-th order as specified in clause 9.1. + +### 9.3.2.4 Fixed-length (FL) binarization process + +Input to this process is a request for a FL binarization for a syntax element and cMax. + +Output of this process is the FL binarization of the syntax element. + +FL binarization is constructed by using a fixedLength-bit unsigned integer bin string of the syntax element value, where fixedLength = Ceil( Log2( cMax + 1 ) ). The indexing of bins for the FL binarization is such that the binIdx = 0 relates to the least significant bit with increasing values of binIdx towards the most significant bit. + +### 9.3.2.5 Binarization process for macroblock type and sub-macroblock type + +Input to this process is a request for a binarization for syntax elements mb\_type or sub\_mb\_type[ ]. + +Output of this process is the binarization of the syntax element. + +The binarization scheme for decoding of macroblock type in I slices is specified in Table 9-36. + +For macroblock types in SI slices, the binarization consists of bin strings specified as a concatenation of a prefix and a suffix bit string as follows. + +The prefix bit string consists of a single bit, which is specified by $b_0 = ( ( \text{mb\_type} == \text{SI} ) ? 0 : 1 )$ . For the syntax element value for which $b_0$ is equal to 0, the bin string only consists of the prefix bit string. For the syntax element value for which $b_0$ is equal to 1, the binarization is given by concatenating the prefix $b_0$ and the suffix bit string as specified in Table 9-36 for macroblock type in I slices indexed by subtracting 1 from the value of mb\_type in SI slices. + +**Table 9-36 – Binarization for macroblock types in I slices** + +| Value (name) of mb_type | Bin string | | | | | | | +|-------------------------|------------|---|---|---|---|---|---| +| 0 (I_NxN) | 0 | | | | | | | +| 1 (I_16x16_0_0_0) | 1 | 0 | 0 | 0 | 0 | 0 | | +| 2 (I_16x16_1_0_0) | 1 | 0 | 0 | 0 | 0 | 1 | | +| 3 (I_16x16_2_0_0) | 1 | 0 | 0 | 0 | 1 | 0 | | +| 4 (I_16x16_3_0_0) | 1 | 0 | 0 | 0 | 1 | 1 | | +| 5 (I_16x16_0_1_0) | 1 | 0 | 0 | 1 | 0 | 0 | 0 | +| 6 (I_16x16_1_1_0) | 1 | 0 | 0 | 1 | 0 | 0 | 1 | +| 7 (I_16x16_2_1_0) | 1 | 0 | 0 | 1 | 0 | 1 | 0 | +| 8 (I_16x16_3_1_0) | 1 | 0 | 0 | 1 | 0 | 1 | 1 | +| 9 (I_16x16_0_2_0) | 1 | 0 | 0 | 1 | 1 | 0 | 0 | +| 10 (I_16x16_1_2_0) | 1 | 0 | 0 | 1 | 1 | 0 | 1 | +| 11 (I_16x16_2_2_0) | 1 | 0 | 0 | 1 | 1 | 1 | 0 | +| 12 (I_16x16_3_2_0) | 1 | 0 | 0 | 1 | 1 | 1 | 1 | +| 13 (I_16x16_0_0_1) | 1 | 0 | 1 | 0 | 0 | 0 | | +| 14 (I_16x16_1_0_1) | 1 | 0 | 1 | 0 | 0 | 1 | | +| 15 (I_16x16_2_0_1) | 1 | 0 | 1 | 0 | 1 | 0 | | +| 16 (I_16x16_3_0_1) | 1 | 0 | 1 | 0 | 1 | 1 | | +| 17 (I_16x16_0_1_1) | 1 | 0 | 1 | 1 | 0 | 0 | 0 | +| 18 (I_16x16_1_1_1) | 1 | 0 | 1 | 1 | 0 | 0 | 1 | +| 19 (I_16x16_2_1_1) | 1 | 0 | 1 | 1 | 0 | 1 | 0 | +| 20 (I_16x16_3_1_1) | 1 | 0 | 1 | 1 | 0 | 1 | 1 | +| 21 (I_16x16_0_2_1) | 1 | 0 | 1 | 1 | 1 | 0 | 0 | +| 22 (I_16x16_1_2_1) | 1 | 0 | 1 | 1 | 1 | 0 | 1 | +| 23 (I_16x16_2_2_1) | 1 | 0 | 1 | 1 | 1 | 1 | 0 | +| 24 (I_16x16_3_2_1) | 1 | 0 | 1 | 1 | 1 | 1 | 1 | +| 25 (I_PCM) | 1 | 1 | | | | | | +| binIdx | 0 | 1 | 2 | 3 | 4 | 5 | 6 | + +The binarization schemes for P macroblock types in P and SP slices and for B macroblocks in B slices are specified in Table 9-37. + +The bin string for I macroblock types in P and SP slices corresponding to mb\_type values 5 to 30 consists of a concatenation of a prefix, which consists of a single bit with value equal to 1 as specified in Table 9-37 and a suffix as specified in Table 9-36, indexed by subtracting 5 from the value of mb\_type. + +mb\_type equal to 4 (P\_8x8ref0) is not allowed. + +For I macroblock types in B slices (mb\_type values 23 to 48) the binarization consists of bin strings specified as a concatenation of a prefix bit string as specified in Table 9-37 and suffix bit strings as specified in Table 9-36, indexed by subtracting 23 from the value of mb\_type. + +**Table 9-37 – Binarization for macroblock types in P, SP, and B slices** + +| Slice type | Value (name) of mb_type | Bin string | | | | | | | +|-------------|-------------------------------|------------|---|---|---|---|---|---| +| P, SP slice | 0 (P_L0_16x16) | 0 | 0 | 0 | | | | | +| | 1 (P_L0_L0_16x8) | 0 | 1 | 1 | | | | | +| | 2 (P_L0_L0_8x16) | 0 | 1 | 0 | | | | | +| | 3 (P_8x8) | 0 | 0 | 1 | | | | | +| | 4 (P_8x8ref0) | na | | | | | | | +| | 5 to 30 (Intra, prefix only) | 1 | | | | | | | +| B slice | 0 (B_Direct_16x16) | 0 | | | | | | | +| | 1 (B_L0_16x16) | 1 | 0 | 0 | | | | | +| | 2 (B_L1_16x16) | 1 | 0 | 1 | | | | | +| | 3 (B_Bi_16x16) | 1 | 1 | 0 | 0 | 0 | 0 | | +| | 4 (B_L0_L0_16x8) | 1 | 1 | 0 | 0 | 0 | 1 | | +| | 5 (B_L0_L0_8x16) | 1 | 1 | 0 | 0 | 1 | 0 | | +| | 6 (B_L1_L1_16x8) | 1 | 1 | 0 | 0 | 1 | 1 | | +| | 7 (B_L1_L1_8x16) | 1 | 1 | 0 | 1 | 0 | 0 | | +| | 8 (B_L0_L1_16x8) | 1 | 1 | 0 | 1 | 0 | 1 | | +| | 9 (B_L0_L1_8x16) | 1 | 1 | 0 | 1 | 1 | 0 | | +| | 10 (B_L1_L0_16x8) | 1 | 1 | 0 | 1 | 1 | 1 | | +| | 11 (B_L1_L0_8x16) | 1 | 1 | 1 | 1 | 1 | 0 | | +| | 12 (B_L0_Bi_16x8) | 1 | 1 | 1 | 0 | 0 | 0 | 0 | +| | 13 (B_L0_Bi_8x16) | 1 | 1 | 1 | 0 | 0 | 0 | 1 | +| | 14 (B_L1_Bi_16x8) | 1 | 1 | 1 | 0 | 0 | 1 | 0 | +| | 15 (B_L1_Bi_8x16) | 1 | 1 | 1 | 0 | 0 | 1 | 1 | +| | 16 (B_Bi_L0_16x8) | 1 | 1 | 1 | 0 | 1 | 0 | 0 | +| | 17 (B_Bi_L0_8x16) | 1 | 1 | 1 | 0 | 1 | 0 | 1 | +| | 18 (B_Bi_L1_16x8) | 1 | 1 | 1 | 0 | 1 | 1 | 0 | +| | 19 (B_Bi_L1_8x16) | 1 | 1 | 1 | 0 | 1 | 1 | 1 | +| | 20 (B_Bi_Bi_16x8) | 1 | 1 | 1 | 1 | 0 | 0 | 0 | +| | 21 (B_Bi_Bi_8x16) | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| | 22 (B_8x8) | 1 | 1 | 1 | 1 | 1 | 1 | | +| | 23 to 48 (Intra, prefix only) | 1 | 1 | 1 | 1 | 0 | 1 | | +| binIdx | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | + +For P, SP, and B slices the specification of the binarization for sub\_mb\_type[ ] is given in Table 9-38. + +**Table 9-38 – Binarization for sub-macroblock types in P, SP, and B slices** + +| Slice type | Value (name) of sub_mb_type[ ] | Bin string | | | | | | +|-------------|--------------------------------|------------|---|---|---|---|---| +| P, SP slice | 0 (P_L0_8x8) | 1 | | | | | | +| | 1 (P_L0_8x4) | 0 | 0 | | | | | +| | 2 (P_L0_4x8) | 0 | 1 | 1 | | | | +| | 3 (P_L0_4x4) | 0 | 1 | 0 | | | | +| B slice | 0 (B_Direct_8x8) | 0 | | | | | | +| | 1 (B_L0_8x8) | 1 | 0 | 0 | | | | +| | 2 (B_L1_8x8) | 1 | 0 | 1 | | | | +| | 3 (B_Bi_8x8) | 1 | 1 | 0 | 0 | 0 | | +| | 4 (B_L0_8x4) | 1 | 1 | 0 | 0 | 1 | | +| | 5 (B_L0_4x8) | 1 | 1 | 0 | 1 | 0 | | +| | 6 (B_L1_8x4) | 1 | 1 | 0 | 1 | 1 | | +| | 7 (B_L1_4x8) | 1 | 1 | 1 | 0 | 0 | 0 | +| | 8 (B_Bi_8x4) | 1 | 1 | 1 | 0 | 0 | 1 | +| | 9 (B_Bi_4x8) | 1 | 1 | 1 | 0 | 1 | 0 | +| | 10 (B_L0_4x4) | 1 | 1 | 1 | 0 | 1 | 1 | +| | 11 (B_L1_4x4) | 1 | 1 | 1 | 1 | 0 | | +| | 12 (B_Bi_4x4) | 1 | 1 | 1 | 1 | 1 | | +| binIdx | | 0 | 1 | 2 | 3 | 4 | 5 | + +**9.3.2.6 Binarization process for coded block pattern** + +Input to this process is a request for a binarization for the syntax element coded\_block\_pattern. + +Output of this process is the binarization of the syntax element. + +The binarization of coded\_block\_pattern consists of a prefix part and (when present) a suffix part. The prefix part of the binarization is given by the FL binarization of CodedBlockPatternLuma with cMax = 15. When ChromaArrayType is not equal to 0 or 3, the suffix part is present and consists of the TU binarization of CodedBlockPatternChroma with cMax = 2. The relationship between the value of the syntax element coded\_block\_pattern and the values of CodedBlockPatternLuma and CodedBlockPatternChroma is given as specified in clause 7.4.5. + +**9.3.2.7 Binarization process for mb\_qp\_delta** + +Input to this process is a request for a binarization for the syntax element mb\_qp\_delta. + +Output of this process is the binarization of the syntax element. + +The bin string of mb\_qp\_delta is derived by the U binarization of the mapped value of the syntax element mb\_qp\_delta, where the assignment rule between the signed value of mb\_qp\_delta and its mapped value is given as specified in Table 9-3. + +**9.3.3 Decoding process flow** + +Input to this process is a binarization of the requested syntax element, maxBinIdxCtx, bypassFlag and ctxIdxOffset as specified in clause 9.3.2. + +Output of this process is the value of the syntax element. + +This process specifies how each bit of a bit string is parsed for each syntax element. + +After parsing each bit, the resulting bit string is compared to all bin strings of the binarization of the syntax element and the following applies: + +- If the bit string is equal to one of the bin strings, the corresponding value of the syntax element is the output. +- Otherwise (the bit string is not equal to one of the bin strings), the next bit is parsed. + +While parsing each bin, the variable binIdx is incremented by 1 starting with binIdx being set equal to 0 for the first bin. + +When the binarization of the corresponding syntax element consists of a prefix and a suffix binarization part,, the variable binIdx is set equal to 0 for the first bin of each part of the bin string (prefix part or suffix part). In this case, after parsing the prefix bit string, the parsing process of the suffix bit string related to the binarizations specified in clauses 9.3.2.3 and 9.3.2.5 is invoked depending on the resulting prefix bit string as specified in clauses 9.3.2.3 and 9.3.2.5. Note that for the binarization of the syntax element coded\_block\_pattern, the suffix bit string is present regardless of the prefix bit string of length 4 as specified in clause 9.3.2.6. + +Depending on the variable bypassFlag, the following applies: + +- If bypassFlag is equal to 1, the bypass decoding process as specified in clause 9.3.3.2.3 is applied for parsing the value of the bins from the bitstream. +- Otherwise (bypassFlag is equal to 0), the parsing of each bin is specified by the following two ordered steps: + 1. Given binIdx, maxBinIdxCtx and ctxIdxOffset, ctxIdx is derived as specified in clause 9.3.3.1. + 2. Given ctxIdx, the value of the bin from the bitstream as specified in clause 9.3.3.2 is decoded. + +### 9.3.3.1 Derivation process for ctxIdx + +Inputs to this process are binIdx, maxBinIdxCtx and ctxIdxOffset. + +Output of this process is ctxIdx. + +Table 9-39 shows the assignment of ctxIdx increments (ctxIdxInc) to binIdx for all ctxIdxOffset values except those related to the syntax elements coded\_block\_flag, significant\_coeff\_flag, last\_significant\_coeff\_flag, and coeff\_abs\_level\_minus1. + +The ctxIdx to be used with a specific binIdx is specified by first determining the ctxIdxOffset associated with the given bin string or part thereof. The ctxIdx is determined as follows: + +- If the ctxIdxOffset is listed in Table 9-39, the ctxIdx for a binIdx is the sum of ctxIdxOffset and ctxIdxInc, which is found in Table 9-39. When more than one value is listed in Table 9-39 for a binIdx, the assignment process for ctxIdxInc for that binIdx is further specified in the clauses given in parenthesis of the corresponding table entry. +- Otherwise (ctxIdxOffset is not listed in Table 9-39), the ctxIdx is specified to be the sum of the following terms: ctxIdxOffset and ctxIdxBlockCatOffset(ctxBlockCat) as specified in Table 9-40 and ctxIdxInc(ctxBlockCat). Clause 9.3.3.1.3 specifies which ctxBlockCat is used. Clause 9.3.3.1.1.9 specifies the assignment of ctxIdxInc(ctxBlockCat) for coded\_block\_flag, and clause 9.3.3.1.3 specifies the assignment of ctxIdxInc(ctxBlockCat) for significant\_coeff\_flag, last\_significant\_coeff\_flag, and coeff\_abs\_level\_minus1. + +All bins with binIdx greater than maxBinIdxCtx are parsed using the value of ctxIdx being assigned to binIdx equal to maxBinIdxCtx. + +All entries in Table 9-39 labelled with "na" correspond to values of binIdx that do not occur for the corresponding ctxIdxOffset. + +ctxIdx = 276 is assigned to the binIdx of mb\_type indicating the I\_PCM mode. For parsing the value of the corresponding bins from the bitstream, the arithmetic decoding process for decisions before termination as specified in clause 9.3.3.2.4 is applied. + +**Table 9-39 – Assignment of ctxIdxInc to binIdx for all ctxIdxOffset values except those related to the syntax elements coded\_block\_flag, significant\_coeff\_flag, last\_significant\_coeff\_flag, and coeff\_abs\_level\_minus1** + +| ctxIdxOffset | binIdx | | | | | | | +|--------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------|---------------------------|------| +| | 0 | 1 | 2 | 3 | 4 | 5 | >= 6 | +| 0 | 0,1,2
(clause 9.3.3.1.1.3) | na | na | na | na | na | na | +| 3 | 0,1,2
(clause 9.3.3.1.1.3) | ctxIdx=276 | 3 | 4 | 5,6
(clause 9.3.3.1.2) | 6,7
(clause 9.3.3.1.2) | 7 | +| 11 | 0,1,2
(clause 9.3.3.1.1.1) | na | na | na | na | na | na | +| 14 | 0 | 1 | 2,3
(clause 9.3.3.1.2) | na | na | na | na | +| 17 | 0 | ctxIdx=276 | 1 | 2 | 2,3
(clause 9.3.3.1.2) | 3 | 3 | +| 21 | 0 | 1 | 2 | na | na | na | na | +| 24 | 0,1,2
(clause 9.3.3.1.1.1) | na | na | na | na | na | na | +| 27 | 0,1,2
(clause 9.3.3.1.1.3) | 3 | 4,5
(clause 9.3.3.1.2) | 5 | 5 | 5 | 5 | +| 32 | 0 | ctxIdx=276 | 1 | 2 | 2,3
(clause 9.3.3.1.2) | 3 | 3 | +| 36 | 0 | 1 | 2,3
(clause 9.3.3.1.2) | 3 | 3 | 3 | na | +| 40 | 0,1,2
(clause 9.3.3.1.1.7) | 3 | 4 | 5 | 6 | 6 | 6 | +| 47 | 0,1,2
(clause 9.3.3.1.1.7) | 3 | 4 | 5 | 6 | 6 | 6 | +| 54 | 0,1,2,3
(clause 9.3.3.1.1.6) | 4 | 5 | 5 | 5 | 5 | 5 | +| 60 | 0,1
(clause 9.3.3.1.1.5) | 2 | 3 | 3 | 3 | 3 | 3 | +| 64 | 0,1,2
(clause 9.3.3.1.1.8) | 3 | 3 | na | na | na | na | +| 68 | 0 | na | na | na | na | na | na | +| 69 | 0 | 0 | 0 | na | na | na | na | +| 70 | 0,1,2
(clause 9.3.3.1.1.2) | na | na | na | na | na | na | +| 73 | 0,1,2,3
(clause 9.3.3.1.1.4) | 0,1,2,3
(clause 9.3.3.1.1.4) | 0,1,2,3
(clause 9.3.3.1.1.4) | 0,1,2,3
(clause 9.3.3.1.1.4) | na | na | na | +| 77 | 0,1,2,3
(clause 9.3.3.1.1.4) | 4,5,6,7
(clause 9.3.3.1.1.4) | na | na | na | na | na | +| 276 | 0 | na | na | na | na | na | na | +| 399 | 0,1,2
(clause 9.3.3.1.1.10) | na | na | na | na | na | na | + +Table 9-40 shows the values of ctxIdxBlockCatOffset depending on ctxBlockCat for the syntax elements coded\_block\_flag, significant\_coeff\_flag, last\_significant\_coeff\_flag, and coeff\_abs\_level\_minus1. The specification of ctxBlockCat is given in Table 9-42. + +**Table 9-40 – Assignment of ctxIdxBlockCatOffset to ctxBlockCat for syntax elements coded\_block\_flag, significant\_coeff\_flag, last\_significant\_coeff\_flag, and coeff\_abs\_level\_minus1** + +| Syntax element | ctxBlockCat (as specified in Table 9-42) | | | | | | | | | | | | | | +|-----------------------------|------------------------------------------|----|----|----|----|---|---|----|----|---|----|----|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | +| coded_block_flag | 0 | 4 | 8 | 12 | 16 | 0 | 0 | 4 | 8 | 4 | 0 | 4 | 8 | 8 | +| significant_coeff_flag | 0 | 15 | 29 | 44 | 47 | 0 | 0 | 15 | 29 | 0 | 0 | 15 | 29 | 0 | +| last_significant_coeff_flag | 0 | 15 | 29 | 44 | 47 | 0 | 0 | 15 | 29 | 0 | 0 | 15 | 29 | 0 | +| coeff_abs_level_minus1 | 0 | 10 | 20 | 30 | 39 | 0 | 0 | 10 | 20 | 0 | 0 | 10 | 20 | 0 | + +### 9.3.3.1.1 Assignment process of ctxIdxInc using neighbouring syntax elements + +Clause 9.3.3.1.1.1 specifies the derivation process of ctxIdxInc for the syntax element mb\_skip\_flag. + +Clause 9.3.3.1.1.2 specifies the derivation process of ctxIdxInc for the syntax element mb\_field\_decoding\_flag. + +Clause 9.3.3.1.1.3 specifies the derivation process of ctxIdxInc for the syntax element mb\_type. + +Clause 9.3.3.1.1.4 specifies the derivation process of ctxIdxInc for the syntax element coded\_block\_pattern. + +Clause 9.3.3.1.1.5 specifies the derivation process of ctxIdxInc for the syntax element mb\_qp\_delta. + +Clause 9.3.3.1.1.6 specifies the derivation process of ctxIdxInc for the syntax elements ref\_idx\_l0 and ref\_idx\_l1. + +Clause 9.3.3.1.1.7 specifies the derivation process of ctxIdxInc for the syntax elements mvd\_l0 and mvd\_l1. + +Clause 9.3.3.1.1.8 specifies the derivation process of ctxIdxInc for the syntax element intra\_chroma\_pred\_mode. + +Clause 9.3.3.1.1.9 specifies the derivation process of ctxIdxInc for the syntax element coded\_block\_flag. + +Clause 9.3.3.1.1.10 specifies the derivation process of ctxIdxInc for the syntax element transform\_size\_8x8\_flag. + +#### 9.3.3.1.1.1 Derivation process of ctxIdxInc for the syntax element mb\_skip\_flag + +Output of this process is ctxIdxInc. + +When MbuffFrameFlag is equal to 1 and mb\_field\_decoding\_flag has not been decoded (yet) for the current macroblock pair with top macroblock address $2 * (CurrMbAddr / 2)$ , the inference rule for the syntax element mb\_field\_decoding\_flag as specified in clause 7.4.4 is applied. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If mbAddrN is not available or mb\_skip\_flag for the macroblock mbAddrN is equal to 1, condTermFlagN is set equal to 0. +- Otherwise (mbAddrN is available and mb\_skip\_flag for the macroblock mbAddrN is equal to 0), condTermFlagN is set equal to 1. + +The variable ctxIdxInc is derived by: + +$$ctxIdxInc = condTermFlagA + condTermFlagB \quad (9-7)$$ + +#### 9.3.3.1.1.2 Derivation process of ctxIdxInc for the syntax element mb\_field\_decoding\_flag + +Output of this process is ctxIdxInc. + +The derivation process for neighbouring macroblock addresses and their availability in MBAFF frames as specified in clause 6.4.10 is invoked and the output is assigned to mbAddrA and mbAddrB. + +When both macroblocks mbAddrN and mbAddrN + 1 have mb\_type equal to P\_Skip or B\_Skip, the inference rule for the syntax element mb\_field\_decoding\_flag as specified in clause 7.4.4 is applied for the macroblock mbAddrN. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If any of the following conditions are true, condTermFlagN is set equal to 0: + - mbAddrN is not available, + - the macroblock mbAddrN is a frame macroblock. +- Otherwise, condTermFlagN is set equal to 1. + +The variable ctxIdxInc is derived by + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (9-8)$$ + +#### 9.3.3.1.1.3 Derivation process of ctxIdxInc for the syntax element mb\_type + +Input to this process is ctxIdxOffset. + +Output of this process is ctxIdxInc. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If any of the following conditions are true, condTermFlagN is set equal to 0: + - mbAddrN is not available, + - ctxIdxOffset is equal to 0 and mb\_type for the macroblock mbAddrN is equal to SI, + - ctxIdxOffset is equal to 3 and mb\_type for the macroblock mbAddrN is equal to I\_NxN, + - ctxIdxOffset is equal to 27 and mb\_type for the macroblock mbAddrN is equal to B\_Skip or B\_Direct\_16x16. +- Otherwise, condTermFlagN is set equal to 1. + +The variable ctxIdxInc is derived as + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (9-9)$$ + +#### 9.3.3.1.1.4 Derivation process of ctxIdxInc for the syntax element coded\_block\_pattern + +Inputs to this process are ctxIdxOffset and binIdx. + +Output of this process is ctxIdxInc. + +Depending on the value of the variable ctxIdxOffset, the following ordered steps are specified: + +- If ctxIdxOffset is equal to 73, the following applies: + 1. The derivation process for neighbouring 8x8 luma blocks specified in clause 6.4.11.2 is invoked with luma8x8BlkIdx = binIdx as input and the output is assigned to mbAddrA, mbAddrB, luma8x8BlkIdxA, and luma8x8BlkIdxB. + 2. Let the variable condTermFlagN (with N being either A or B) be derived as follows: + - If any of the following conditions are true, condTermFlagN is set equal to 0: + - mbAddrN is not available, + - mb\_type for the macroblock mbAddrN is equal to I\_PCM, + - the macroblock mbAddrN is not the current macroblock CurrMbAddr and the macroblock mbAddrN does not have mb\_type equal to P\_Skip or B\_Skip, and $((\text{CodedBlockPatternLuma} \gg \text{luma8x8BlkIdxN}) \& 1)$ is not equal to 0 for the value of CodedBlockPatternLuma for the macroblock mbAddrN, + - Otherwise, condTermFlagN is set equal to 1. + +- the macroblock mbAddrN is the current macroblock CurrMbAddr and the prior decoded bin value $b_k$ of coded\_block\_pattern with $k = \text{luma8x8BlkIdxN}$ is not equal to 0. + - Otherwise, condTermFlagN is set equal to 1. +3. The variable ctxIdxInc is derived as + +$$\text{ctxIdxInc} = \text{condTermFlagA} + 2 * \text{condTermFlagB} \quad (9-10)$$ + +- Otherwise (ctxIdxOffset is equal to 77), the following ordered steps are specified: + 1. The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + 2. Let the variable condTermFlagN (with N being either A or B) be derived as follows: + - If mbAddrN is available and mb\_type for the macroblock mbAddrN is equal to I\_PCM, condTermFlagN is set equal to 1. + - Otherwise, if any of the following conditions are true, condTermFlagN is set equal to 0: + - mbAddrN is not available or the macroblock mbAddrN has mb\_type equal to P\_Skip or B\_Skip, + - binIdx is equal to 0 and CodedBlockPatternChroma for the macroblock mbAddrN is equal to 0, + - binIdx is equal to 1 and CodedBlockPatternChroma for the macroblock mbAddrN is not equal to 2. + - Otherwise, condTermFlagN is set equal to 1. + 3. The variable ctxIdxInc is derived as + +$$\text{ctxIdxInc} = \text{condTermFlagA} + 2 * \text{condTermFlagB} + ( ( \text{binIdx} == 1 ) ? 4 : 0 ) \quad (9-11)$$ + +NOTE – When a macroblock is coded in Intra\_16x16 macroblock prediction mode, the values of CodedBlockPatternLuma and CodedBlockPatternChroma for the macroblock are derived from mb\_type as specified in Table 7-11. + +#### 9.3.3.1.1.5 Derivation process of ctxIdxInc for the syntax element mb\_qp\_delta + +Output of this process is ctxIdxInc. + +Let prevMbAddr be the macroblock address of the macroblock that precedes the current macroblock in decoding order. When the current macroblock is the first macroblock of a slice, prevMbAddr is marked as not available. + +Let the variable ctxIdxInc be derived as follows: + +- If any of the following conditions are true, ctxIdxInc is set equal to 0: + - prevMbAddr is not available or the macroblock prevMbAddr has mb\_type equal to P\_Skip or B\_Skip, + - mb\_type of the macroblock prevMbAddr is equal to I\_PCM, + - The macroblock prevMbAddr is not coded in Intra\_16x16 macroblock prediction mode and both CodedBlockPatternLuma and CodedBlockPatternChroma for the macroblock prevMbAddr are equal to 0, + - mb\_qp\_delta for the macroblock prevMbAddr is equal to 0. +- Otherwise, ctxIdxInc is set equal to 1. + +#### 9.3.3.1.1.6 Derivation process of ctxIdxInc for the syntax elements ref\_idx\_l0 and ref\_idx\_l1 + +Input to this process is mbPartIdx. + +Output of this process is ctxIdxInc. + +The interpretation of ref\_idx\_lX and Pred\_lX within this clause is specified as follows: + +- If this process is invoked for the derivation of ref\_idx\_l0, ref\_idx\_lX is interpreted as ref\_idx\_l0 and Pred\_lX is interpreted as Pred\_l0. +- Otherwise (this process is invoked for the derivation of ref\_idx\_l1), ref\_idx\_lX is interpreted as ref\_idx\_l1 and Pred\_lX is interpreted as Pred\_l1. + +The derivation process for neighbouring partitions specified in clause 6.4.11.7 is invoked with mbPartIdx, currSubMbType set equal to sub\_mb\_type[ mbPartIdx ], and subMbPartIdx = 0 as input and the output is assigned to mbAddrA\mbPartIdxA and mbAddrB\mbPartIdxB. + +With ref\_idx\_IX[ mbPartIdxN ] (with N being either A or B) specifying the syntax element for the macroblock mbAddrN, let the variable refIdxZeroFlagN be derived as follows: + +- If MbAffFrameFlag is equal to 1, the current macroblock is a frame macroblock, and the macroblock mbAddrN is a field macroblock, + +$$\text{refIdxZeroFlagN} = ( ( \text{ref\_idx\_IX[ mbPartIdxN ]} > 1 ) ? 0 : 1 ) \quad (9-12)$$ + +- Otherwise, + +$$\text{refIdxZeroFlagN} = ( ( \text{ref\_idx\_IX[ mbPartIdxN ]} > 0 ) ? 0 : 1 ) \quad (9-13)$$ + +Let the variable predModeEqualFlagN be specified as follows: + +- If mb\_type for the macroblock mbAddrN is equal to B\_Direct\_16x16 or B\_Skip, predModeEqualFlagN is set equal to 0. +- Otherwise, if the macroblock mbAddrN has mb\_type equal to P\_8x8 or B\_8x8, the following applies: + - If SubMbPredMode( sub\_mb\_type[ mbPartIdxN ] ) is not equal to Pred\_LX and not equal to BiPred, predModeEqualFlagN is set equal to 0, where sub\_mb\_type specifies the syntax element list for the macroblock mbAddrN. + - Otherwise, predModeEqualFlagN is set equal to 1. +- Otherwise, the following applies: + - If MbPartPredMode( mb\_type, mbPartIdxN ) is not equal to Pred\_LX and not equal to BiPred, predModeEqualFlagN is set equal to 0, where mb\_type specifies the syntax element for the macroblock mbAddrN. + - Otherwise, predModeEqualFlagN is set equal to 1. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If any of the following conditions are true, condTermFlagN is set equal to 0: + - mbAddrN is not available, + - the macroblock mbAddrN has mb\_type equal to P\_Skip or B\_Skip, + - the macroblock mbAddrN is coded in an Intra macroblock prediction mode, + - predModeEqualFlagN is equal to 0, + - refIdxZeroFlagN is equal to 1. +- Otherwise, condTermFlagN is set equal to 1. + +The variable ctxIdxInc is derived as + +$$\text{ctxIdxInc} = \text{condTermFlagA} + 2 * \text{condTermFlagB} \quad (9-14)$$ + +### 9.3.3.1.1.7 Derivation process of ctxIdxInc for the syntax elements mvd\_l0 and mvd\_l1 + +Inputs to this process are mbPartIdx, subMbPartIdx, and ctxIdxOffset. + +Output of this process is ctxIdxInc. + +The interpretation of mvd\_IX and Pred\_LX within this clause is specified as follows: + +- If this process is invoked for the derivation of mvd\_l0, mvd\_IX is interpreted as mvd\_l0 and Pred\_LX is interpreted as Pred\_L0. +- Otherwise (this process is invoked for the derivation of mvd\_l1), mvd\_IX is interpreted as mvd\_l1 and Pred\_LX is interpreted as Pred\_L1. + +The derivation process for neighbouring partitions specified in clause 6.4.11.7 is invoked with mbPartIdx, currSubMbType set equal to sub\_mb\_type[ mbPartIdx ], and subMbPartIdx as input and the output is assigned to mbAddrA\mbPartIdxA\subMbPartIdxA and mbAddrB\mbPartIdxB\subMbPartIdxB. + +Let the variable compIdx be derived as follows: + +- If ctxIdxOffset is equal to 40, compIdx is set equal to 0. +- Otherwise (ctxIdxOffset is equal to 47), compIdx is set equal to 1. + +Let the variable predModeEqualFlagN be specified as follows: + +- If mb\_type for the macroblock mbAddrN is equal to B\_Direct\_16x16 or B\_Skip, predModeEqualFlagN is set equal to 0. +- Otherwise, if the macroblock mbAddrN has mb\_type equal to P\_8x8 or B\_8x8, the following applies: + - If SubMbPredMode( sub\_mb\_type[ mbPartIdxN ] ) is not equal to Pred\_LX and not equal to BiPred, predModeEqualFlagN is set equal to 0, where sub\_mb\_type specifies the syntax element list for the macroblock mbAddrN. + - Otherwise, predModeEqualFlagN is set equal to 1. +- Otherwise, the following applies: + - If MbPartPredMode( mb\_type, mbPartIdxN ) is not equal to Pred\_LX and not equal to BiPred, predModeEqualFlagN is set equal to 0, where mb\_type specifies the syntax element for the macroblock mbAddrN. + - Otherwise, predModeEqualFlagN is set equal to 1. + +Let the variable absMvdCompN (with N being either A or B) be derived as follows: + +- If any of the following conditions are true, absMvdCompN is set equal to 0: + - mbAddrN is not available, + - the macroblock mbAddrN has mb\_type equal to P\_Skip or B\_Skip, + - the macroblock mbAddrN is coded in an Intra macroblock prediction mode, + - predModeEqualFlagN is equal to 0. +- Otherwise, the following applies: + - If compIdx is equal to 1, MbaffFrameFlag is equal to 1, the current macroblock is a frame macroblock, and the macroblock mbAddrN is a field macroblock, + +$$\text{absMvdCompN} = \text{Abs}( \text{mvd\_IX}[ \text{mbPartIdxN} ] [ \text{subMbPartIdxN} ] [ \text{compIdx} ] ) * 2 \quad (9-15)$$ + +- Otherwise, if compIdx is equal to 1, MbaffFrameFlag is equal to 1, the current macroblock is a field macroblock, and the macroblock mbAddrN is a frame macroblock, + +$$\text{absMvdCompN} = \text{Abs}( \text{mvd\_IX}[ \text{mbPartIdxN} ] [ \text{subMbPartIdxN} ] [ \text{compIdx} ] ) / 2 \quad (9-16)$$ + +- Otherwise, + +$$\text{absMvdCompN} = \text{Abs}( \text{mvd\_IX}[ \text{mbPartIdxN} ] [ \text{subMbPartIdxN} ] [ \text{compIdx} ] ) \quad (9-17)$$ + +The variable ctxIdxInc is derived as follows: + +- If absMvdCompA is greater than 32 or absMvdCompB is greater than 32, ctxIdxInc is set equal to 2. +- Otherwise, if absMvdCompA + absMvdCompB is greater than 32, ctxIdxInc is set equal to 2. +- Otherwise, if absMvdCompA + absMvdCompB is greater than 2, ctxIdxInc is set equal to 1. +- Otherwise (absMvdCompA + absMvdCompB is less than or equal to 2), ctxIdxInc is set equal to 0. + +NOTE – Although the above form of expression for the derivation of ctxIdxInc could have been somewhat simplified, the form shown above was selected to assist the reader in avoiding a potential dynamic range problem in the derivation process. + +#### 9.3.3.1.1.8 Derivation process of ctxIdxInc for the syntax element intra\_chroma\_pred\_mode + +Output of this process is ctxIdxInc. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + +Let the variable condTermFlagN (with N being replaced by either A or B) be derived as follows: + +- If any of the following conditions are true, condTermFlagN is set equal to 0: + - mbAddrN is not available, + - The macroblock mbAddrN is coded in an Inter macroblock prediction mode, + - mb\_type for the macroblock mbAddrN is equal to I\_PCM, + - intra\_chroma\_pred\_mode for the macroblock mbAddrN is equal to 0. +- Otherwise, condTermFlagN is set equal to 1. + +The variable ctxIdxInc is derived by: + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (9-18)$$ + +#### 9.3.3.1.1.9 Derivation process of ctxIdxInc for the syntax element coded\_block\_flag + +Input to this process is ctxBlockCat and additional input is specified as follows: + +- If ctxBlockCat is equal to 0, 6, or 10, no additional input. +- Otherwise, if ctxBlockCat is equal to 1 or 2, luma4x4BlkIdx. +- Otherwise, if ctxBlockCat is equal to 3, the chroma component index iCbCr. +- Otherwise, if ctxBlockCat is equal to 4, chroma4x4BlkIdx and the chroma component index iCbCr. +- Otherwise, if ctxBlockCat is equal to 5, luma8x8BlkIdx. +- Otherwise, if ctxBlockCat is equal to 7 or 8, cb4x4BlkIdx. +- Otherwise, if ctxBlockCat is equal to 9, cb8x8BlkIdx. +- Otherwise, if ctxBlockCat is equal to 11 or 12, cr4x4BlkIdx. +- Otherwise (ctxBlockCat is equal to 13), cr8x8BlkIdx. + +Output of this process is ctxIdxInc( ctxBlockCat ). + +Let the variable transBlockN (with N being either A or B) be derived as follows: + +- If ctxBlockCat is equal to 0, 6, or 10, the following ordered steps are specified: + 1. The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrN (with N being either A or B). + 2. The variable transBlockN is derived as follows: + - If mbAddrN is available and the macroblock mbAddrN is coded in Intra\_16x16 macroblock prediction mode, the following applies: + - If ctxBlockCat is equal to 0, the luma DC block of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, if ctxBlockCat is equal to 6, the Cb DC block of macroblock mbAddrN is assigned to transBlockN. + - Otherwise (ctxBlockCat is equal to 10), the Cr DC block of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, transBlockN is marked as not available. +- Otherwise, if ctxBlockCat is equal to 1 or 2, the following ordered steps are specified: + 1. The derivation process for neighbouring 4x4 luma blocks specified in clause 6.4.11.4 is invoked with luma4x4BlkIdx as input and the output is assigned to mbAddrN, luma4x4BlkIdxN (with N being either A or B). + +2. The variable transBlockN is derived as follows: + - If mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip, B\_Skip, or I\_PCM, ( ( CodedBlockPatternLuma >> ( luma4x4BlkIdxN >> 2 ) ) & 1 ) is not equal to 0 for the macroblock mbAddrN, and transform\_size\_8x8\_flag is equal to 0 for the macroblock mbAddrN, the 4x4 luma block with index luma4x4BlkIdxN of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, if mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip or B\_Skip, ( ( CodedBlockPatternLuma >> ( luma4x4BlkIdxN >> 2 ) ) & 1 ) is not equal to 0 for the macroblock mbAddrN, and transform\_size\_8x8\_flag is equal to 1 for the macroblock mbAddrN, the 8x8 luma block with index ( luma4x4BlkIdxN >> 2 ) of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, transBlockN is marked as not available. +- Otherwise, if ctxBlockCat is equal to 3, the following ordered steps are specified: + 1. The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrN (with N being either A or B). + 2. The variable transBlockN is derived as follows: + - If mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip, B\_Skip, or I\_PCM, and CodedBlockPatternChroma is not equal to 0 for the macroblock mbAddrN, the chroma DC block of chroma component iCbCr of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, transBlockN is marked as not available. +- Otherwise, if ctxBlockCat is equal to 4, the following ordered steps are specified: + 1. The derivation process for neighbouring 4x4 chroma blocks specified in clause 6.4.11.5 is invoked with chroma4x4BlkIdx as input and the output is assigned to mbAddrN, chroma4x4BlkIdxN (with N being either A or B). + 2. The variable transBlockN is derived as follows: + - If mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip, B\_Skip, or I\_PCM, and CodedBlockPatternChroma is equal to 2 for the macroblock mbAddrN, the 4x4 chroma block with chroma4x4BlkIdxN of the chroma component iCbCr of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, transBlockN is marked as not available. +- Otherwise, if ctxBlockCat is equal to 5, the following ordered steps are specified: + 1. The derivation process for neighbouring 8x8 luma blocks specified in clause 6.4.11.2 is invoked with luma8x8BlkIdx as input and the output is assigned to mbAddrN, luma8x8BlkIdxN (with N being either A or B). + 2. The variable transBlockN is derived as follows: + - If mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip, B\_Skip, or I\_PCM, ( ( CodedBlockPatternLuma >> luma8x8BlkIdx ) & 1 ) is not equal to 0 for the macroblock mbAddrN, and transform\_size\_8x8\_flag is equal to 1 for the macroblock mbAddrN, the 8x8 luma block with index luma8x8BlkIdxN of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, transBlockN is marked as not available. +- Otherwise, if ctxBlockCat is equal to 7 or 8, the following ordered steps are specified: + 1. The derivation process for neighbouring 4x4 Cb blocks specified in clause 6.4.11.5 is invoked with cb4x4BlkIdx as input and the output is assigned to mbAddrN, cb4x4BlkIdxN (with N being either A or B). + 2. The variable transBlockN is derived as follows: + - If mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip, B\_Skip, or I\_PCM, ( ( CodedBlockPatternLuma >> ( cb4x4BlkIdxN >> 2 ) ) & 1 ) is not equal to 0 for the macroblock mbAddrN, and transform\_size\_8x8\_flag is equal to 0 for the macroblock mbAddrN, the 4x4 Cb block with index cb4x4BlkIdxN of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, if mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip or B\_Skip, ( ( CodedBlockPatternLuma >> ( cb4x4BlkIdxN >> 2 ) ) & 1 ) is not equal to 0 for the + +macroblock mbAddrN, and transform\_size\_8x8\_flag is equal to 1 for the macroblock mbAddrN, the 8x8 Cb block with index ( cb4x4BlkIdxN >> 2 ) of macroblock mbAddrN is assigned to transBlockN. + +- Otherwise, transBlockN is marked as not available. +- Otherwise, if ctxBlockCat is equal to 9, the following ordered steps are specified: + 1. The derivation process for neighbouring 8x8 Cb blocks specified in clause 6.4.11.3 is invoked with cb8x8BlkIdx as input and the output is assigned to mbAddrN, cb8x8BlkIdxN (with N being either A or B). + 2. The variable transBlockN is derived as follows: + - If mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip, B\_Skip, or I\_PCM, ( ( CodedBlockPatternLuma >> cb8x8BlkIdx ) & 1 ) is not equal to 0 for the macroblock mbAddrN, and transform\_size\_8x8\_flag is equal to 1 for the macroblock mbAddrN, the 8x8 Cb block with index cb8x8BlkIdxN of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, transBlockN is marked as not available. +- Otherwise, if ctxBlockCat is equal to 11 or 12, the following ordered steps are specified: + 1. The derivation process for neighbouring 4x4 Cr blocks specified in clause 6.4.11.5 is invoked with cr4x4BlkIdx as input and the output is assigned to mbAddrN, cr4x4BlkIdxN (with N being either A or B). + 2. The variable transBlockN is derived as follows: + - If mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip, B\_Skip, or I\_PCM, ( ( CodedBlockPatternLuma >> ( cr4x4BlkIdxN >> 2 ) ) & 1 ) is not equal to 0 for the macroblock mbAddrN, and transform\_size\_8x8\_flag is equal to 0 for the macroblock mbAddrN, the 4x4 Cr block with index cr4x4BlkIdxN of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, if mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip or B\_Skip, ( ( CodedBlockPatternLuma >> ( cr4x4BlkIdxN >> 2 ) ) & 1 ) is not equal to 0 for the macroblock mbAddrN, and transform\_size\_8x8\_flag is equal to 1 for the macroblock mbAddrN, the 8x8 Cr block with index ( cr4x4BlkIdxN >> 2 ) of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, transBlockN is marked as not available. +- Otherwise (ctxBlockCat is equal to 13), the following ordered steps are specified: + 1. The derivation process for neighbouring 8x8 Cr blocks specified in clause 6.4.11.3 is invoked with cr8x8BlkIdx as input and the output is assigned to mbAddrN, cr8x8BlkIdxN (with N being either A or B). + 2. The variable transBlockN is derived as follows: + - If mbAddrN is available, the macroblock mbAddrN does not have mb\_type equal to P\_Skip, B\_Skip, or I\_PCM,, ( ( CodedBlockPatternLuma >> cr8x8BlkIdx ) & 1 ) is not equal to 0 for the macroblock mbAddrN, and transform\_size\_8x8\_flag is equal to 1 for the macroblock mbAddrN, the 8x8 Cr block with index cr8x8BlkIdxN of macroblock mbAddrN is assigned to transBlockN. + - Otherwise, transBlockN is marked as not available. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If any of the following conditions are true, condTermFlagN is set equal to 0: + - mbAddrN is not available and the current macroblock is coded in an Inter macroblock prediction mode, + - mbAddrN is available and transBlockN is not available and mb\_type for the macroblock mbAddrN is not equal to I\_PCM, + - The current macroblock is coded in an Intra macroblock prediction mode, constrained\_intra\_pred\_flag is equal to 1, the macroblock mbAddrN is available and coded in an Inter macroblock prediction mode, and slice data partitioning is in use (nal\_unit\_type is in the range of 2 through 4, inclusive). +- Otherwise, if any of the following conditions are true, condTermFlagN is set equal to 1: + - mbAddrN is not available and the current macroblock is coded in an Intra macroblock prediction mode, + - mb\_type for the macroblock mbAddrN is equal to I\_PCM. +- Otherwise, condTermFlagN is set equal to the value of the coded\_block\_flag of the transform block transBlockN that was decoded for the macroblock mbAddrN. + +The variable `ctxIdxInc( ctxBlockCat )` is derived by + +$$\text{ctxIdxInc}(\text{ctxBlockCat}) = \text{condTermFlagA} + 2 * \text{condTermFlagB} \quad (9-19)$$ + +#### 9.3.3.1.1.10 Derivation process of `ctxIdxInc` for the syntax element `transform_size_8x8_flag` + +Output of this process is `ctxIdxInc`. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to `mbAddrA` and `mbAddrB`. + +Let the variable `condTermFlagN` (with N being either A or B) be derived as follows: + +- If any of the following conditions are true, `condTermFlagN` is set equal to 0: + - `mbAddrN` is not available, + - `transform_size_8x8_flag` for the macroblock `mbAddrN` is equal to 0. +- Otherwise, `condTermFlagN` is set equal to 1. + +The variable `ctxIdxInc` is derived by + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (9-20)$$ + +#### 9.3.3.1.2 Assignment process of `ctxIdxInc` using prior decoded bin values + +Inputs to this process are `ctxIdxOffset` and `binIdx`. + +Output of this process is `ctxIdxInc`. + +Table 9-41 contains the specification of `ctxIdxInc` for the given values of `ctxIdxOffset` and `binIdx`. + +For each value of `ctxIdxOffset` and `binIdx`, `ctxIdxInc` is derived by using some of the values of prior decoded bin values ( $b_0, b_1, b_2, \dots, b_k$ ), where the value of the index $k$ is less than the value of `binIdx`. + +**Table 9-41 – Specification of `ctxIdxInc` for specific values of `ctxIdxOffset` and `binIdx`** + +| Value (name) of ctxIdxOffset | binIdx | ctxIdxInc | +|-------------------------------------------|---------------------|------------------------| +| 3 | 4 | $(b_3 \neq 0) ? 5 : 6$ | +| | 5 | $(b_3 \neq 0) ? 6 : 7$ | +| 14 | 2 | $(b_1 \neq 1) ? 2 : 3$ | +| 17 | 4 | $(b_3 \neq 0) ? 2 : 3$ | +| 27 | 2 | $(b_1 \neq 0) ? 4 : 5$ | +| 32 | 4 | $(b_3 \neq 0) ? 2 : 3$ | +| 36 | 2 | $(b_1 \neq 0) ? 2 : 3$ | + +#### 9.3.3.1.3 Assignment process of `ctxIdxInc` for syntax elements `significant_coeff_flag`, `last_significant_coeff_flag`, and `coeff_abs_level_minus1` + +Inputs to this process are `ctxIdxOffset` and `binIdx`. + +Output of this process is `ctxIdxInc`. + +The assignment process of `ctxIdxInc` for syntax elements `significant_coeff_flag`, `last_significant_coeff_flag`, and `coeff_abs_level_minus1` as well as for `coded_block_flag` depends on categories of different blocks denoted by the variable `ctxBlockCat`. The specification of these block categories is given in Table 9-42. + +**Table 9-42 – Specification of ctxBlockCat for the different blocks** + +| Block description | maxNumCoeff | ctxBlockCat | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| block of luma DC transform coefficient levels
(i.e., list Intra16x16DCLevel as described in clause 7.4.5.3) | 16 | 0 | +| block of luma AC transform coefficient levels
(i.e., list Intra16x16ACLevel[ i ] as described in clause 7.4.5.3) | 15 | 1 | +| block of 16 luma transform coefficient levels
(i.e., list LumaLevel4x4[ i ] as described in clause 7.4.5.3) | 16 | 2 | +| block of chroma DC transform coefficient levels when ChromaArrayType is equal to 1 or 2
(i.e., list ChromaDCLevel as described in clause 7.4.5.3) | 4 * NumC8x8 | 3 | +| block of chroma AC transform coefficient levels when ChromaArrayType is equal to 1 or 2
(i.e., list ChromaACLevel as described in clause 7.4.5.3) | 15 | 4 | +| block of 64 luma transform coefficient levels
(i.e., list LumaLevel8x8[ i ] as described in clause 7.4.5.3) | 64 | 5 | +| block of Cb DC transform coefficient levels when ChromaArrayType is equal to 3
(i.e., list CbIntra16x16DCLevel as described in clause 7.4.5.3) | 16 | 6 | +| block of Cb AC transform coefficient levels when ChromaArrayType is equal to 3
(i.e., list CbIntra16x16ACLevel[ i ] as described in clause 7.4.5.3) | 15 | 7 | +| block of 16 Cb transform coefficient levels when ChromaArrayType is equal to 3
(i.e., list CbLevel4x4[ i ] as described in clause 7.4.5.3) | 16 | 8 | +| block of 64 Cb transform coefficient levels when ChromaArrayType is equal to 3
(i.e., list CbLevel8x8[ i ] as described in clause 7.4.5.3) | 64 | 9 | +| block of Cr DC transform coefficient levels when ChromaArrayType is equal to 3
(i.e., list CrIntra16x16DCLevel as described in clause 7.4.5.3) | 16 | 10 | +| block of Cr AC transform coefficient levels when ChromaArrayType is equal to 3
(i.e., list CrIntra16x16ACLevel[ i ] as described in clause 7.4.5.3) | 15 | 11 | +| block of 16 Cr transform coefficient levels when ChromaArrayType is equal to 3
(i.e., list CrLevel4x4[ i ] as described in clause 7.4.5.3) | 16 | 12 | +| block of 64 Cr transform coefficient levels when ChromaArrayType is equal to 3
(i.e., list CrLevel8x8[ i ] as described in clause 7.4.5.3) | 64 | 13 | + +Let the variable levelListIdx be set equal to the index of the list of transform coefficient levels as specified in clause 7.4.5.3. + +For the syntax elements significant\_coeff\_flag and last\_significant\_coeff\_flag in blocks with ctxBlockCat not equal to 3, 5, 9, and 13, the variable ctxIdxInc is derived by + +$$\text{ctxIdxInc} = \text{levelListIdx} \quad (9-21)$$ + +where levelListIdx ranges from 0 to maxNumCoeff – 2, inclusive. + +For the syntax elements significant\_coeff\_flag and last\_significant\_coeff\_flag in blocks with ctxBlockCat == 3, the variable ctxIdxInc is derived by + +$$\text{ctxIdxInc} = \text{Min}(\text{levelListIdx} / \text{NumC8x8}, 2) \quad (9-22)$$ + +where levelListIdx ranges from 0 to 4 \* NumC8x8 – 2, inclusive. + +For the syntax elements significant\_coeff\_flag and last\_significant\_coeff\_flag in 8x8 luma, Cb, or Cr blocks with ctxBlockCat == 5, 9, or 13, Table 9-43 contains the specification of ctxIdxInc for the given values of levelListIdx, where levelListIdx ranges from 0 to 62, inclusive. + +Table 9-43 – Mapping of scanning position to ctxIdxInc for ctxBlockCat == 5, 9, or 13 + +| levelIdx | ctxIdxInc for significant_coeff_flag (frame coded macroblocks) | ctxIdxInc for significant_coeff_flag (field coded macroblocks) | ctxIdxInc for last_significant_coeff_flag | levelIdx | ctxIdxInc for significant_coeff_flag (frame coded macroblocks) | ctxIdxInc for significant_coeff_flag (field coded macroblocks) | ctxIdxInc for last_significant_coeff_flag | +|----------|----------------------------------------------------------------|----------------------------------------------------------------|-------------------------------------------|----------|----------------------------------------------------------------|----------------------------------------------------------------|-------------------------------------------| +| 0 | 0 | 0 | 0 | 32 | 7 | 9 | 3 | +| 1 | 1 | 1 | 1 | 33 | 6 | 9 | 3 | +| 2 | 2 | 1 | 1 | 34 | 11 | 10 | 3 | +| 3 | 3 | 2 | 1 | 35 | 12 | 10 | 3 | +| 4 | 4 | 2 | 1 | 36 | 13 | 8 | 3 | +| 5 | 5 | 3 | 1 | 37 | 11 | 11 | 3 | +| 6 | 5 | 3 | 1 | 38 | 6 | 12 | 3 | +| 7 | 4 | 4 | 1 | 39 | 7 | 11 | 3 | +| 8 | 4 | 5 | 1 | 40 | 8 | 9 | 4 | +| 9 | 3 | 6 | 1 | 41 | 9 | 9 | 4 | +| 10 | 3 | 7 | 1 | 42 | 14 | 10 | 4 | +| 11 | 4 | 7 | 1 | 43 | 10 | 10 | 4 | +| 12 | 4 | 7 | 1 | 44 | 9 | 8 | 4 | +| 13 | 4 | 8 | 1 | 45 | 8 | 13 | 4 | +| 14 | 5 | 4 | 1 | 46 | 6 | 13 | 4 | +| 15 | 5 | 5 | 1 | 47 | 11 | 9 | 4 | +| 16 | 4 | 6 | 2 | 48 | 12 | 9 | 5 | +| 17 | 4 | 9 | 2 | 49 | 13 | 10 | 5 | +| 18 | 4 | 10 | 2 | 50 | 11 | 10 | 5 | +| 19 | 4 | 10 | 2 | 51 | 6 | 8 | 5 | +| 20 | 3 | 8 | 2 | 52 | 9 | 13 | 6 | +| 21 | 3 | 11 | 2 | 53 | 14 | 13 | 6 | +| 22 | 6 | 12 | 2 | 54 | 10 | 9 | 6 | +| 23 | 7 | 11 | 2 | 55 | 9 | 9 | 6 | +| 24 | 7 | 9 | 2 | 56 | 11 | 10 | 7 | +| 25 | 7 | 9 | 2 | 57 | 12 | 10 | 7 | +| 26 | 8 | 10 | 2 | 58 | 13 | 14 | 7 | +| 27 | 9 | 10 | 2 | 59 | 11 | 14 | 7 | + +**Table 9-43 – Mapping of scanning position to ctxIdxInc for ctxBlockCat == 5, 9, or 13** + +| levelListIdx | ctxIdxInc for significant_coeff_flag (frame coded macroblocks) | ctxIdxInc for significant_coeff_flag (field coded macroblocks) | ctxIdxInc for last_significant_coeff_flag | levelListIdx | ctxIdxInc for significant_coeff_flag (frame coded macroblocks) | ctxIdxInc for significant_coeff_flag (field coded macroblocks) | ctxIdxInc for last_significant_coeff_flag | +|--------------|----------------------------------------------------------------|----------------------------------------------------------------|-------------------------------------------|--------------|----------------------------------------------------------------|----------------------------------------------------------------|-------------------------------------------| +| 28 | 10 | 8 | 2 | 60 | 14 | 14 | 8 | +| 29 | 9 | 11 | 2 | 61 | 10 | 14 | 8 | +| 30 | 8 | 12 | 2 | 62 | 12 | 14 | 8 | +| 31 | 7 | 11 | 2 | | | | | + +Let numDecodAbsLevelEq1 denote the accumulated number of decoded transform coefficient levels with absolute value equal to 1, and let numDecodAbsLevelGt1 denote the accumulated number of decoded transform coefficient levels with absolute value greater than 1. Both numbers are related to the same transform coefficient block, where the current decoding process takes place. Then, for decoding of coeff\_abs\_level\_minus1, ctxIdxInc for coeff\_abs\_level\_minus1 is specified depending on binIdx as follows: + +- If binIdx is equal to 0, ctxIdxInc is derived by + +$$\text{ctxIdxInc} = ( ( \text{numDecodAbsLevelGt1} \neq 0 ) ? 0 : \text{Min}( 4, 1 + \text{numDecodAbsLevelEq1} ) ) \quad (9-23)$$ + +- Otherwise (binIdx is greater than 0), ctxIdxInc is derived by + +$$\text{ctxIdxInc} = 5 + \text{Min}( 4 - ( ( \text{ctxBlockCat} == 3 ) ? 1 : 0 ), \text{numDecodAbsLevelGt1} ) \quad (9-24)$$ + +### 9.3.3.2 Arithmetic decoding process + +Inputs to this process are the bypassFlag, ctxIdx as derived in clause 9.3.3.1, and the state variables codIRange and codIOffset of the arithmetic decoding engine. + +Output of this process is the value of the bin. + +Figure 9-2 illustrates the whole arithmetic decoding process for a single bin. For decoding the value of a bin, the context index ctxIdx is passed to the arithmetic decoding process DecodeBin(ctxIdx), which is specified as follows: + +- If bypassFlag is equal to 1, DecodeBypass( ) as specified in clause 9.3.3.2.3 is invoked. +- Otherwise, if bypassFlag is equal to 0 and ctxIdx is equal to 276, DecodeTerminate( ) as specified in clause 9.3.3.2.4 is invoked. +- Otherwise (bypassFlag is equal to 0 and ctxIdx is not equal to 276), DecodeDecision( ) as specified in clause 9.3.3.2.1 is applied. + +![Flowchart of the arithmetic decoding process for a single bin. The process starts with DecodeBin(ctxIdx), followed by a decision bypassFlag == 1? If Yes, it goes to DecodeBypass. If No, it goes to another decision ctxIdx == 276? If Yes, it goes to DecodeTerminate. If No, it goes to DecodeDecision(ctxIdx). All three paths (DecodeBypass, DecodeTerminate, and DecodeDecision) lead to the Done terminal.](886a88caad59e8f8b1cf54c72e8adf4a_img.jpg) + +``` + +graph TD + Start([DecodeBin(ctxIdx)]) --> D1{bypassFlag == 1?} + D1 -- Yes --> P1[DecodeBypass] + D1 -- No --> D2{ctxIdx == 276?} + D2 -- Yes --> P2[DecodeTerminate] + D2 -- No --> P3[DecodeDecision(ctxIdx)] + P1 --> Done([Done]) + P2 --> Done + P3 --> Done + +``` + +Flowchart of the arithmetic decoding process for a single bin. The process starts with DecodeBin(ctxIdx), followed by a decision bypassFlag == 1? If Yes, it goes to DecodeBypass. If No, it goes to another decision ctxIdx == 276? If Yes, it goes to DecodeTerminate. If No, it goes to DecodeDecision(ctxIdx). All three paths (DecodeBypass, DecodeTerminate, and DecodeDecision) lead to the Done terminal. + +H.264(09)\_F9-2 + +**Figure 9-2 – Overview of the arithmetic decoding process for a single bin (informative)** + +NOTE – Arithmetic coding is based on the principle of recursive interval subdivision. Given a probability estimation $p(0)$ and $p(1) = 1 - p(0)$ of a binary decision (0, 1), an initially given code sub-interval with the range $codIRange$ will be subdivided into two sub-intervals having range $p(0) * codIRange$ and $codIRange - p(0) * codIRange$ , respectively. Depending on the decision, which has been observed, the corresponding sub-interval will be chosen as the new code interval, and a binary code string pointing into that interval will represent the sequence of observed binary decisions. It is useful to distinguish between the most probable symbol (MPS) and the least probable symbol (LPS), so that binary decisions have to be identified as either MPS or LPS, rather than 0 or 1. Given this terminology, each context is specified by the probability $pLPS$ of the LPS and the value of MPS ( $valMPS$ ), which is either 0 or 1. + +The arithmetic core engine in this Recommendation | International Standard has three distinct properties: + +- The probability estimation is performed by means of a finite-state machine with a table-based transition process between 64 different representative probability states $\{pLPS(pStateIdx) | 0 \leq pStateIdx < 64\}$ for the LPS probability $pLPS$ . The numbering of the states is arranged in such a way that the probability state with index $pStateIdx = 0$ corresponds to an LPS probability value of 0.5, with decreasing LPS probability towards higher state indices. +- The range $codIRange$ representing the state of the coding engine is quantized to a small set $\{Q_1, \dots, Q_4\}$ of pre-set quantization values prior to the calculation of the new interval range. Storing a table containing all $64 \times 4$ pre-computed product values of $Q_i * pLPS(pStateIdx)$ allows a multiplication-free approximation of the product $codIRange * pLPS(pStateIdx)$ . +- For syntax elements or parts thereof for which an approximately uniform probability distribution is assumed to be given a separate simplified encoding and decoding bypass process is used. + +### 9.3.3.2.1 Arithmetic decoding process for a binary decision + +Inputs to this process are $ctxIdx$ , $codIRange$ , and $codIOffset$ . + +Outputs of this process are the decoded value $binVal$ , and the updated variables $codIRange$ and $codIOffset$ . + +Figure 9-3 shows the flowchart for decoding a single decision (DecodeDecision): + +1. The value of the variable $codIRangeLPS$ is derived as follows: + +- Given the current value of $codIRange$ , the variable $qCodIRangeIdx$ is derived by + +$$qCodIRangeIdx = (codIRange \gg 6) \& 3 \quad (9-25)$$ + +- Given $qCodIRangeIdx$ and $pStateIdx$ associated with $ctxIdx$ , the value of the variable $rangeTabLPS$ as specified in Table 9-44 is assigned to $codIRangeLPS$ : + +$$codIRangeLPS = rangeTabLPS[pStateIdx][qCodIRangeIdx] \quad (9-26)$$ + +2. The variable *codIRange* is set equal to *codIRange* – *codIRangeLPS* and the following applies: + - If *codIOffset* is greater than or equal to *codIRange*, the variable *binVal* is set equal to $1 - valMPS$ , *codIOffset* is decremented by *codIRange*, and *codIRange* is set equal to *codIRangeLPS*. + - Otherwise, the variable *binVal* is set equal to *valMPS*. + +Given the value of *binVal*, the state transition is performed as specified in clause 9.3.3.2.1.1. Depending on the current value of *codIRange*, renormalization is performed as specified in clause 9.3.3.2.2. + +#### 9.3.3.2.1.1 State transition process + +Inputs to this process are the current *pStateIdx*, the decoded value *binVal* and *valMPS* values of the context variable associated with *ctxIdx*. + +Outputs of this process are the updated *pStateIdx* and *valMPS* of the context variable associated with *ctxIdx*. + +Depending on the decoded value *binVal*, the update of the two variables *pStateIdx* and *valMPS* associated with *ctxIdx* is derived as specified by the following pseudo-code: + +``` + +if( binVal == valMPS ) + pStateIdx = transIdxMPS( pStateIdx ) +else { + if( pStateIdx == 0 ) + valMPS = 1 – valMPS + pStateIdx = transIdxLPS( pStateIdx ) +} + +``` + +(9-27) + +Table 9-45 specifies the transition rules transIdxMPS( ) and transIdxLPS( ) after decoding the value of *valMPS* and $1 - valMPS$ , respectively. + +![Flowchart for decoding a decision. The process starts with DecodeDecision(ctxIdx), followed by calculations for qCodIRangeIdx, codIRangeLPS, and codIRange. A decision diamond codIOffset >= codIRange leads to two paths: Yes (binVal = !valMPS, codIOffset = codIOffset - codIRange, codIRange = codIRangeLPS) and No (binVal = valMPS, pStateIdx = transIdxMPS[pStateIdx]). Both paths lead to a decision diamond pStateIdx == 0?. The Yes path from pStateIdx == 0? leads to valMPS = 1 - valMPS. The No path from pStateIdx == 0? leads to pStateIdx = transIdxLPS[pStateIdx]. Both valMPS = 1 - valMPS and pStateIdx = transIdxLPS[pStateIdx] lead to RenormD, which finally leads to Done.](2399254baf1cd3a8e04cf5313b4d9b8f_img.jpg) + +``` + +graph TD + Start([DecodeDecision ctxIdx]) --> Init["qCodIRangeIdx = (codIRange>>6) & 3 +codIRangeLPS = rangeTabLPS[pStateIdx][qCodIRangeIdx] +codIRange = codIRange - codIRangeLPS"] + Init --> Dec1{codIOffset >= codIRange} + Dec1 -- Yes --> YesPath["binVal = !valMPS +codIOffset = codIOffset - codIRange +codIRange = codIRangeLPS"] + Dec1 -- No --> NoPath["binVal = valMPS +pStateIdx = transIdxMPS[pStateIdx]"] + YesPath --> Dec2{pStateIdx == 0?} + Dec2 -- Yes --> YesPath2["valMPS = 1 - valMPS"] + Dec2 -- No --> NoPath2["pStateIdx = transIdxLPS[pStateIdx]"] + YesPath2 --> RenormD[RenormD] + NoPath2 --> RenormD + NoPath --> RenormD + RenormD --> Done([Done]) + +``` + +Flowchart for decoding a decision. The process starts with DecodeDecision(ctxIdx), followed by calculations for qCodIRangeIdx, codIRangeLPS, and codIRange. A decision diamond codIOffset >= codIRange leads to two paths: Yes (binVal = !valMPS, codIOffset = codIOffset - codIRange, codIRange = codIRangeLPS) and No (binVal = valMPS, pStateIdx = transIdxMPS[pStateIdx]). Both paths lead to a decision diamond pStateIdx == 0?. The Yes path from pStateIdx == 0? leads to valMPS = 1 - valMPS. The No path from pStateIdx == 0? leads to pStateIdx = transIdxLPS[pStateIdx]. Both valMPS = 1 - valMPS and pStateIdx = transIdxLPS[pStateIdx] lead to RenormD, which finally leads to Done. + +H.264(09)\_F9-3 + +Figure 9-3 – Flowchart for decoding a decision + +**Table 9-44 – Specification of rangeTabLPS depending on pStateIdx and qCodIRangeIdx** + +| pStateIdx | qCodIRangeIdx | | | | pStateIdx | qCodIRangeIdx | | | | +|-----------|---------------|-----|-----|-----|-----------|---------------|----|----|----| +| | 0 | 1 | 2 | 3 | | 0 | 1 | 2 | 3 | +| 0 | 128 | 176 | 208 | 240 | 32 | 27 | 33 | 39 | 45 | +| 1 | 128 | 167 | 197 | 227 | 33 | 26 | 31 | 37 | 43 | +| 2 | 128 | 158 | 187 | 216 | 34 | 24 | 30 | 35 | 41 | +| 3 | 123 | 150 | 178 | 205 | 35 | 23 | 28 | 33 | 39 | +| 4 | 116 | 142 | 169 | 195 | 36 | 22 | 27 | 32 | 37 | +| 5 | 111 | 135 | 160 | 185 | 37 | 21 | 26 | 30 | 35 | +| 6 | 105 | 128 | 152 | 175 | 38 | 20 | 24 | 29 | 33 | +| 7 | 100 | 122 | 144 | 166 | 39 | 19 | 23 | 27 | 31 | +| 8 | 95 | 116 | 137 | 158 | 40 | 18 | 22 | 26 | 30 | +| 9 | 90 | 110 | 130 | 150 | 41 | 17 | 21 | 25 | 28 | +| 10 | 85 | 104 | 123 | 142 | 42 | 16 | 20 | 23 | 27 | +| 11 | 81 | 99 | 117 | 135 | 43 | 15 | 19 | 22 | 25 | +| 12 | 77 | 94 | 111 | 128 | 44 | 14 | 18 | 21 | 24 | +| 13 | 73 | 89 | 105 | 122 | 45 | 14 | 17 | 20 | 23 | +| 14 | 69 | 85 | 100 | 116 | 46 | 13 | 16 | 19 | 22 | +| 15 | 66 | 80 | 95 | 110 | 47 | 12 | 15 | 18 | 21 | +| 16 | 62 | 76 | 90 | 104 | 48 | 12 | 14 | 17 | 20 | +| 17 | 59 | 72 | 86 | 99 | 49 | 11 | 14 | 16 | 19 | +| 18 | 56 | 69 | 81 | 94 | 50 | 11 | 13 | 15 | 18 | +| 19 | 53 | 65 | 77 | 89 | 51 | 10 | 12 | 15 | 17 | +| 20 | 51 | 62 | 73 | 85 | 52 | 10 | 12 | 14 | 16 | +| 21 | 48 | 59 | 69 | 80 | 53 | 9 | 11 | 13 | 15 | +| 22 | 46 | 56 | 66 | 76 | 54 | 9 | 11 | 12 | 14 | +| 23 | 43 | 53 | 63 | 72 | 55 | 8 | 10 | 12 | 14 | +| 24 | 41 | 50 | 59 | 69 | 56 | 8 | 9 | 11 | 13 | +| 25 | 39 | 48 | 56 | 65 | 57 | 7 | 9 | 11 | 12 | +| 26 | 37 | 45 | 54 | 62 | 58 | 7 | 9 | 10 | 12 | +| 27 | 35 | 43 | 51 | 59 | 59 | 7 | 8 | 10 | 11 | +| 28 | 33 | 41 | 48 | 56 | 60 | 6 | 8 | 9 | 11 | +| 29 | 32 | 39 | 46 | 53 | 61 | 6 | 7 | 9 | 10 | +| 30 | 30 | 37 | 43 | 50 | 62 | 6 | 7 | 8 | 9 | +| 31 | 29 | 35 | 41 | 48 | 63 | 2 | 2 | 2 | 2 | + +Table 9-45 – State transition table + +| | | | | | | | | | | | | | | | | | +|-------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| pStateIdx | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +| transIdxLPS | 0 | 0 | 1 | 2 | 2 | 4 | 4 | 5 | 6 | 7 | 8 | 9 | 9 | 11 | 11 | 12 | +| transIdxMPS | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | +| pStateIdx | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | +| transIdxLPS | 13 | 13 | 15 | 15 | 16 | 16 | 18 | 18 | 19 | 19 | 21 | 21 | 22 | 22 | 23 | 24 | +| transIdxMPS | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | +| pStateIdx | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | +| transIdxLPS | 24 | 25 | 26 | 26 | 27 | 27 | 28 | 29 | 29 | 30 | 30 | 30 | 31 | 32 | 32 | 33 | +| transIdxMPS | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | +| pStateIdx | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | +| transIdxLPS | 33 | 33 | 34 | 34 | 35 | 35 | 35 | 36 | 36 | 36 | 37 | 37 | 37 | 38 | 38 | 63 | +| transIdxMPS | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 62 | 63 | + +### 9.3.3.2.2 Renormalization process in the arithmetic decoding engine + +Inputs to this process are bits from slice data and the variables codIRange and codIOffset. + +Outputs of this process are the updated variables codIRange and codIOffset. + +A flowchart of the renormalization is shown in Figure 9-4. The current value of codIRange is first compared to 256 and further steps are specified as follows: + +- If codIRange is greater than or equal to 256, no renormalization is needed and the RenormD process is finished; +- Otherwise (codIRange is less than 256), the renormalization loop is entered. Within this loop, the value of codIRange is doubled, i.e., left-shifted by 1 and a single bit is shifted into codIOffset by using read\_bits( 1 ). + +The bitstream shall not contain data that result in a value of codIOffset being greater than or equal to codIRange upon completion of this process. + +![Flowchart of renormalization process. It starts with 'RenormD', followed by a decision 'codIRange < 256'. If 'Yes', it performs 'codIRange = codIRange << 1', 'codIOffset = codIOffset << 1', and 'codIOffset = codIOffset | read_bits(1)'. If 'No', it goes to 'Done'. The loop returns to the decision after the 'Yes' path.](9ad891694657f787cf68e07db7060576_img.jpg) + +``` + +graph TD + RenormD([RenormD]) --> Decision{codIRange < 256} + Decision -- Yes --> Update["codIRange = codIRange << 1 +codIOffset = codIOffset << 1 +codIOffset = codIOffset | read_bits(1)"] + Update --> Decision + Decision -- No --> Done([Done]) + +``` + +H.264(09)\_F9-4 + +Flowchart of renormalization process. It starts with 'RenormD', followed by a decision 'codIRange < 256'. If 'Yes', it performs 'codIRange = codIRange << 1', 'codIOffset = codIOffset << 1', and 'codIOffset = codIOffset | read\_bits(1)'. If 'No', it goes to 'Done'. The loop returns to the decision after the 'Yes' path. + +Figure 9-4 – Flowchart of renormalization + +### 9.3.3.2.3 Bypass decoding process for binary decisions + +Inputs to this process are bits from slice data and the variables `codIRange` and `codIOffset`. + +Outputs of this process are the updated variable `codIOffset` and the decoded value `binVal`. + +The bypass decoding process is invoked when `bypassFlag` is equal to 1. Figure 9-5 shows a flowchart of the corresponding process. + +First, the value of `codIOffset` is doubled, i.e., left-shifted by 1 and a single bit is shifted into `codIOffset` by using `read_bits( 1 )`. Then, the value of `codIOffset` is compared to the value of `codIRange` and further steps are specified as follows: + +- If `codIOffset` is greater than or equal to `codIRange`, the variable `binVal` is set equal to 1 and `codIOffset` is decremented by `codIRange`. +- Otherwise (`codIOffset` is less than `codIRange`), the variable `binVal` is set equal to 0. + +The bitstream shall not contain data that result in a value of `codIOffset` being greater than or equal to `codIRange` upon completion of this process. + +![Flowchart of bypass decoding process](09e581718ac5e06150e10552056892f3_img.jpg) + +``` +graph TD; A([DecodeBypass]) --> B["codIOffset = codIOffset << 1
codIOffset = codIOffset | read_bits(1)"]; B --> C{codIOffset >= codIRange}; C -- Yes --> D["binVal = 1
codIOffset = codIOffset - codIRange"]; C -- No --> E["binVal = 0"]; D --> F([Done]); E --> F +``` + +The flowchart illustrates the bypass decoding process. It begins with an oval labeled 'DecodeBypass', which points to a rectangular box containing the initialization steps: `codIOffset = codIOffset << 1` and `codIOffset = codIOffset | read_bits(1)`. This box leads to a decision diamond labeled `codIOffset >= codIRange`. If the answer is 'Yes', the flow proceeds to a rectangular box where `binVal = 1` and `codIOffset = codIOffset - codIRange`. If the answer is 'No', the flow proceeds to a rectangular box where `binVal = 0`. Both of these boxes lead to a final oval labeled 'Done'. + +Flowchart of bypass decoding process + +H.264(09)\_F9-5 + +Figure 9-5 – Flowchart of bypass decoding process + +### 9.3.3.2.4 Decoding process for binary decisions before termination + +Inputs to this process are bits from slice data and the variables `codIRange` and `codIOffset`. + +Outputs of this process are the updated variables `codIRange` and `codIOffset`, and the decoded value `binVal`. + +This special decoding routine applies to decoding of `end_of_slice_flag` and of the bin indicating the I\_PCM mode corresponding to `ctxIdx` equal to 276. Figure 9-6 shows the flowchart of the corresponding decoding process, which is specified as follows. + +First, the value of `codIRange` is decremented by 2. Then, the value of `codIOffset` is compared to the value of `codIRange` and further steps are specified as follows: + +- If `codIOffset` is greater than or equal to `codIRange`, the variable `binVal` is set equal to 1, no renormalization is carried out, and CABAC decoding is terminated. The last bit inserted in register `codIOffset` is equal to 1. When decoding `end_of_slice_flag`, this last bit inserted in register `codIOffset` is interpreted as `rbsp_stop_one_bit`. +- Otherwise (`codIOffset` is less than `codIRange`), the variable `binVal` is set equal to 0 and renormalization is performed as specified in clause 9.3.3.2.2. + +NOTE – This procedure may also be implemented using `DecodeDecision(ctxIdx)` with `ctxIdx = 276`. In the case where the decoded value is equal to 1, seven more bits would be read by `DecodeDecision(ctxIdx)` and a decoding process would have to adjust its bitstream pointer accordingly to properly decode following syntax elements. + +![Flowchart of decoding a decision before termination. The process starts with DecodeTerminate, followed by codIRange = codIRange-2. A decision diamond asks if codIOffset >= codIRange. If Yes, binVal = 1. If No, binVal = 0, followed by RenormD. Both paths lead to Done.](ad9b0c8d0d3fc421b0dbc2ecc61376f4_img.jpg) + +``` + +graph TD + A([DecodeTerminate]) --> B[codIRange = codIRange-2] + B --> C{codIOffset >= codIRange} + C -- Yes --> D[binVal = 1] + C -- No --> E[binVal = 0] + E --> F[[RenormD]] + D --> G([Done]) + F --> G + +``` + +H.264(09)\_F9-6 + +Flowchart of decoding a decision before termination. The process starts with DecodeTerminate, followed by codIRange = codIRange-2. A decision diamond asks if codIOffset >= codIRange. If Yes, binVal = 1. If No, binVal = 0, followed by RenormD. Both paths lead to Done. + +**Figure 9-6 – Flowchart of decoding a decision before termination** + +### 9.3.4 Arithmetic encoding process (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +Inputs to this process are decisions that are to be encoded and written. + +Outputs of this process are bits that are written to the RBSP. + +This informative clause describes an arithmetic encoding engine that matches the arithmetic decoding engine described in clause 9.3.3.2. The encoding engine is essentially symmetric with the decoding engine, i.e., procedures are called in the same order. The following procedures are described in this section: InitEncoder, EncodeDecision, EncodeBypass, EncodeTerminate, which correspond to InitDecoder, DecodeDecision, DecodeBypass, and DecodeTerminate, respectively. The state of the arithmetic encoding engine is represented by a value of the variable codILow pointing to the lower end of a sub-interval and a value of the variable codIRange specifying the corresponding range of that sub-interval. + +#### 9.3.4.1 Initialization process for the arithmetic encoding engine (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +This process is invoked before encoding the first macroblock of a slice, and after encoding any pcm\_alignment\_zero\_bit and all pcm\_sample\_luma and pcm\_sample\_chroma data for a macroblock of type I\_PCM. + +Outputs of this process are the values codILow, codIRange, firstBitFlag, bitsOutstanding, and BinCountsInNALUnits of the arithmetic encoding engine. + +In the initialization procedure of the encoder, codILow is set equal to 0, and codIRange is set equal to 510. Furthermore, firstBitFlag is set equal to 1 and the counter bitsOutstanding is set equal to 0. + +Depending on whether the current slice is the first slice of a coded picture, the following applies: + +- If the current slice is the first slice of a coded picture, the counter BinCountsInNALUnits is set equal to 0. +- Otherwise (the current slice is not the first slice of a coded picture), the counter BinCountsInNALUnits is not modified. The value of BinCountsInNALUnits is the result of encoding all the slices of a coded picture that precede the current slice in decoding order. After initializing for the first slice of a coded picture as specified in this clause, BinCountsInNALUnits is incremented as specified in clauses 9.3.4.2, 9.3.4.4, and 9.3.4.5. + +NOTE – The minimum register precision required for storing the values of the variables codILow and codIRange after invocation of any of the arithmetic encoding processes specified in clauses 9.3.4.2, 9.3.4.4, and 9.3.4.5 is 10 bits and 9 bits, respectively. The encoding process for a binary decision (EncodeDecision) as specified in clause 9.3.4.2 and the encoding process for a binary decision before termination (EncodeTerminate) as specified in clause 9.3.4.5 require a minimum register precision of 10 bits for + +the variable `codILow` and a minimum register precision of 9 bits for the variable `codIRange`. The bypass encoding process for binary decisions (`EncodeBypass`) as specified in clause 9.3.4.4 requires a minimum register precision of 11 bits for the variable `codILow` and a minimum register precision of 9 bits for the variable `codIRange`. The precision required for the counters `bitsOutstanding` and `BinCountsInNALUnits` should be sufficiently large to prevent overflow of the related registers. When `maxBinCountInSlice` denotes the maximum total number of binary decisions to encode in one slice and `maxBinCountInPic` denotes the maximum total number of binary decisions to encode a picture, the minimum register precision required for the variables `bitsOutstanding` and `BinCountsInNALUnits` is given by $\text{Ceil}(\text{Log}_2(\text{maxBinCountInSlice} + 1))$ and $\text{Ceil}(\text{Log}_2(\text{maxBinCountInPic} + 1))$ , respectively. + +#### 9.3.4.2 Encoding process for a binary decision (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +Inputs to this process are the context index `ctxIdx`, the value of `binVal` to be encoded, and the variables `codIRange`, `codILow` and `BinCountsInNALUnits`. + +Outputs of this process are the variables `codIRange`, `codILow`, and `BinCountsInNALUnits`. + +Figure 9-7 shows the flowchart for encoding a single decision. In a first step, the variable `codIRangeLPS` is derived as follows. + +Given the current value of `codIRange`, `codIRange` is mapped to the index `qCodIRangeIdx` of a quantized value of `codIRange` by using Equation 9-25. The value of `qCodIRangeIdx` and the value of `pStateIdx` associated with `ctxIdx` are used to determine the value of the variable `rangeTabLPS` as specified in Table 9-44, which is assigned to `codIRangeLPS`. The value of `codIRange` – `codIRangeLPS` is assigned to `codIRange`. + +In a second step, the value of `binVal` is compared to `valMPS` associated with `ctxIdx`. When `binVal` is different from `valMPS`, `codIRange` is added to `codILow` and `codIRange` is set equal to the value `codIRangeLPS`. Given the encoded decision, the state transition is performed as specified in clause 9.3.3.2.1.1. Depending on the current value of `codIRange`, renormalization is performed as specified in clause 9.3.4.3. Finally, the variable `BinCountsInNALUnits` is incremented by 1. + +![Flowchart for encoding a decision. The process starts with EncodeDecision(ctxIdx, binVal), followed by calculations for qCodiRangeIdx, codIRangeLPS, and codIRange. A decision diamond binVal != valMPS leads to either updating codILow and codIRange (Yes) or skipping to pStateIdx update (No). Another decision pStateIdx != 0 leads to updating valMPS (No) or skipping (Yes). Both paths lead to pStateIdx update, then RenormE, BinCountsInNALunits increment, and Done.](22a8a787e18103c0859f95076ad941b5_img.jpg) + +``` + +graph TD + Start([EncodeDecision(ctxIdx, binVal)]) --> Init["qCodiRangeIdx = (codIRange >> 6) & 3 +codIRangeLPS = rangeTabLPS[pStateIdx][qCodiRangeIdx] +codIRange = codIRange - codIRangeLPS"] + Init --> Dec1{binVal != valMPS} + Dec1 -- Yes --> Update1["codILow = codILow + codIRange +codIRange = codIRangeLPS"] + Update1 --> Dec2{pStateIdx != 0} + Dec2 -- No --> Update2["valMPS = 1 - valMPS"] + Dec2 -- Yes --> Update3["pStateIdx = transIdxLPS[pStateIdx]"] + Update2 --> Update3 + Dec1 -- No --> Update4["pStateIdx = transIdxMPS[pStateIdx]"] + Update3 --> RenormE[[RenormE]] + Update4 --> RenormE + RenormE --> Update5["BinCountsInNALunits = BinCountsInNALunits + 1"] + Update5 --> Done([Done]) + +``` + +Flowchart for encoding a decision. The process starts with EncodeDecision(ctxIdx, binVal), followed by calculations for qCodiRangeIdx, codIRangeLPS, and codIRange. A decision diamond binVal != valMPS leads to either updating codILow and codIRange (Yes) or skipping to pStateIdx update (No). Another decision pStateIdx != 0 leads to updating valMPS (No) or skipping (Yes). Both paths lead to pStateIdx update, then RenormE, BinCountsInNALunits increment, and Done. + +H.264(09)\_F9-7 + +Figure 9-7 – Flowchart for encoding a decision + +### 9.3.4.3 Renormalization process in the arithmetic encoding engine (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +Inputs to this process are the variables codIRange, codILow, firstBitFlag, and bitsOutstanding. + +Outputs of this process are zero or more bits written to the RBSP and the updated variables codIRange, codILow, firstBitFlag, and bitsOutstanding. + +Renormalization is illustrated in Figure 9-8. + +![Flowchart of renormalization in the encoder](8c126c290eea7c5d7807a293fd40f2d9_img.jpg) + +``` +graph TD; RenormE([RenormE]) --> D1{codIRange < 256}; D1 -- No --> Done([Done]); D1 -- Yes --> D2{codILow < 256}; D2 -- Yes --> PutBit0[PutBit(0)]; D2 -- No --> D3{codILow >= 512}; D3 -- No --> UpdateLow1["codILow = codILow - 256
bitsOutstanding = bitsOutstanding + 1"]; D3 -- Yes --> UpdateLow2["codILow = codILow - 512"]; UpdateLow1 --> PutBit0; UpdateLow2 --> PutBit1[PutBit(1)]; PutBit0 --> UpdateRange["codIRange = codIRange << 1
codILow = codILow << 1"]; PutBit1 --> UpdateRange; UpdateRange --> Done +``` + +The flowchart illustrates the renormalization process in the encoder. It begins with the entry point 'RenormE'. The first decision is 'codIRange < 256'. If 'No', the process ends at 'Done'. If 'Yes', it proceeds to the next decision 'codILow < 256'. If 'Yes', it calls 'PutBit(0)'. If 'No', it proceeds to the decision 'codILow >= 512'. If 'No', it performs 'codILow = codILow - 256' and 'bitsOutstanding = bitsOutstanding + 1', then calls 'PutBit(0)'. If 'Yes', it performs 'codILow = codILow - 512', then calls 'PutBit(1)'. Both 'PutBit(0)' and 'PutBit(1)' lead to the update block 'codIRange = codIRange << 1' and 'codILow = codILow << 1', which then leads to 'Done'. + +Flowchart of renormalization in the encoder + +H.264(09)\_F9-8 + +Figure 9-8 – Flowchart of renormalization in the encoder + +The PutBit( ) procedure described in Figure 9-9 provides carry over control. It uses the function WriteBits( B, N ) that writes N bits with value B to the bitstream and advances the bitstream pointer by N bit positions. This function assumes the existence of a bitstream pointer with an indication of the position of the next bit to be written to the bitstream by the encoding process. + +![Flowchart of PutBit(B) process. It starts with PutBit(B), then checks if firstBitFlag != 0. If Yes, firstBitFlag = 0. If No, WriteBits(B, 1). Both lead to a loop condition bitsOutstanding > 0. If Yes, WriteBits(1 - B, 1) and bitsOutstanding = bitsOutstanding - 1, then loops back. If No, Done.](d90f09fa97733a2cf12bb1ecaf8ddba8_img.jpg) + +``` + +graph TD + Start([PutBit(B)]) --> Decision1{firstBitFlag != 0} + Decision1 -- Yes --> Process1[firstBitFlag = 0] + Decision1 -- No --> Process2[WriteBits(B, 1)] + Process1 --> Decision2{bitsOutstanding > 0} + Process2 --> Decision2 + Decision2 -- Yes --> Process3["WriteBits(1 - B, 1) +bitsOutstanding = bitsOutstanding - 1"] + Process3 --> Decision2 + Decision2 -- No --> End([Done]) + +``` + +H.264(09)\_F9-9 + +Flowchart of PutBit(B) process. It starts with PutBit(B), then checks if firstBitFlag != 0. If Yes, firstBitFlag = 0. If No, WriteBits(B, 1). Both lead to a loop condition bitsOutstanding > 0. If Yes, WriteBits(1 - B, 1) and bitsOutstanding = bitsOutstanding - 1, then loops back. If No, Done. + +**Figure 9-9 – Flowchart of PutBit(B)** + +#### 9.3.4.4 Bypass encoding process for binary decisions (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +Inputs to this process are the variables binVal, codILow, codIRange, bitsOutstanding, and BinCountsInNALunits. + +Output of this process is a bit written to the RBSP and the updated variables codILow, bitsOutstanding, and BinCountsInNALunits. + +This encoding process applies to all binary decisions with bypassFlag equal to 1. Renormalization is included in the specification of this process as given in Figure 9-10. + +![Flowchart of encoding bypass process. The process starts with EncodeBypass(binVal), followed by codILow = codILow << 1. A decision diamond 'binVal != 0' follows. If Yes, codILow = codILow + codIRange. If No, it skips to the next decision. Next is 'codILow >= 1024'. If Yes, PutBit(1) and codILow = codILow - 1024. If No, it goes to 'codILow < 512'. If Yes, PutBit(0). If No, codILow = codILow - 512 and bitsOutstanding = bitsOutstanding + 1. All three paths (PutBit(0), the update block, and codILow = codILow - 1024) lead to BinCountsInNALunits = BinCountsInNALunits + 1, which then leads to Done.](ce54f2a44c590dd67df743472e4de6d5_img.jpg) + +``` + +graph TD + Start([EncodeBypass(binVal)]) --> Init[codILow = codILow << 1] + Init --> binValCheck{binVal != 0} + binValCheck -- Yes --> AddRange[codILow = codILow + codIRange] + binValCheck -- No --> codILowCheck1{codILow >= 1024} + AddRange --> codILowCheck1 + codILowCheck1 -- Yes --> PutBit1[PutBit(1)] + PutBit1 --> Subtract1024[codILow = codILow - 1024] + codILowCheck1 -- No --> codILowCheck2{codILow < 512} + codILowCheck2 -- Yes --> PutBit0[PutBit(0)] + codILowCheck2 -- No --> UpdateOutstanding[codILow = codILow - 512 +bitsOutstanding = bitsOutstanding + 1] + PutBit0 --> UpdateCounts[BinCountsInNALunits = BinCountsInNALunits + 1] + UpdateOutstanding --> UpdateCounts + Subtract1024 --> UpdateCounts + UpdateCounts --> Done([Done]) + +``` + +Flowchart of encoding bypass process. The process starts with EncodeBypass(binVal), followed by codILow = codILow << 1. A decision diamond 'binVal != 0' follows. If Yes, codILow = codILow + codIRange. If No, it skips to the next decision. Next is 'codILow >= 1024'. If Yes, PutBit(1) and codILow = codILow - 1024. If No, it goes to 'codILow < 512'. If Yes, PutBit(0). If No, codILow = codILow - 512 and bitsOutstanding = bitsOutstanding + 1. All three paths (PutBit(0), the update block, and codILow = codILow - 1024) lead to BinCountsInNALunits = BinCountsInNALunits + 1, which then leads to Done. + +H.264(09)\_F9-10 + +Figure 9-10 – Flowchart of encoding bypass + +#### 9.3.4.5 Encoding process for a binary decision before termination (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +Inputs to this process are the variables binVal, codIRange, codILow, bitsOutstanding, and BinCountsInNALunits. + +Outputs of this process are zero or more bits written to the RBSP and the updated variables codILow, codIRange, bitsOutstanding, and BinCountsInNALunits. + +This encoding routine shown in Figure 9-11 applies to encoding of the end\_of\_slice\_flag and of the bin indicating the I\_PCM mb\_type both associated with ctxIdx equal to 276. + +![Flowchart of encoding a decision before termination. The process starts with EncodeTerminate(binVal), followed by codIRange = codIRange - 2. A decision diamond binVal != 0 follows. If Yes, codILow = codILow + codIRange and EncodeFlush are performed. If No, RenormE is performed. Both paths lead to BinCountsInNALUnits = BinCountsInNALUnits + 1 and then Done.](527edc51c92c9d7126850c568985b4c8_img.jpg) + +``` + +graph TD + A([EncodeTerminate(binVal)]) --> B[codIRange = codIRange - 2] + B --> C{binVal != 0} + C -- Yes --> D[codILow = codILow + codIRange] + D --> E[[EncodeFlush]] + C -- No --> F[[RenormE]] + E --> G[BinCountsInNALUnits = BinCountsInNALUnits + 1] + F --> G + G --> H([Done]) + +``` + +Flowchart of encoding a decision before termination. The process starts with EncodeTerminate(binVal), followed by codIRange = codIRange - 2. A decision diamond binVal != 0 follows. If Yes, codILow = codILow + codIRange and EncodeFlush are performed. If No, RenormE is performed. Both paths lead to BinCountsInNALUnits = BinCountsInNALUnits + 1 and then Done. + +H.264(09)\_F9-11 + +**Figure 9-11 – Flowchart of encoding a decision before termination** + +When the value of binVal to encode is equal to 1, CABAC encoding is terminated and the flushing procedure shown in Figure 9-12 is applied. In this flushing procedure, the last bit written by WriteBits( B, N ) is equal to 1. When encoding end\_of\_slice\_flag, this last bit is interpreted as the rbsp\_stop\_one\_bit. + +![Flowchart of flushing at termination. The process starts with EncodeFlush, followed by codIRange = 2, RenormE, PutBit((codILow >> 9) & 1), WriteBits(((codILow >> 7) & 3) | 1, 2), and finally Done.](8f8dd46963501da43c58707865c44cfb_img.jpg) + +``` + +graph TD + A([EncodeFlush]) --> B[codIRange = 2] + B --> C[[RenormE]] + C --> D[[PutBit((codILow >> 9) & 1)]] + D --> E[WriteBits(((codILow >> 7) & 3) | 1, 2)] + E --> F([Done]) + +``` + +Flowchart of flushing at termination. The process starts with EncodeFlush, followed by codIRange = 2, RenormE, PutBit((codILow >> 9) & 1), WriteBits(((codILow >> 7) & 3) | 1, 2), and finally Done. + +H.264(09)\_F9-12 + +**Figure 9-12 – Flowchart of flushing at termination** + +#### 9.3.4.6 Byte stuffing process (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +This process is invoked after encoding the last macroblock of the last slice of a picture and after encapsulation. + +Inputs to this process are the number of bytes NumBytesInVclNALUnits of all VCL NAL units of a picture, the number of macroblocks PicSizeInMbs in the picture, and the number of binary symbols BinCountsInNALUnits resulting from encoding the contents of all VCL NAL units of the picture. + +NOTE – The value of BinCountsInNALUnits is the result of encoding all slices of a coded picture. After initializing for the first slice of a coded picture as specified in clause 9.3.4.1, BinCountsInNALUnits is incremented as specified in clauses 9.3.4.2, 9.3.4.4, and 9.3.4.5. + +Outputs of this process are zero or more bytes appended to the NAL unit. + +Let the variable $k$ be set equal to $\text{Ceil}( ( \text{Ceil}( 3 * ( 32 * \text{BinCountsInNALUnits} - \text{RawMbBits} * \text{PicSizeInMbs} ) \div 1024 ) - \text{NumBytesInVclNALUnits} ) \div 3 )$ . Depending on the variable $k$ the following applies: + +- If $k$ is less than or equal to 0, no `cabac_zero_word` is appended to the NAL unit. +- Otherwise ( $k$ is greater than 0), the 3-byte sequence 0x000003 is appended $k$ times to the NAL unit after encapsulation, where the first two bytes 0x0000 represent a `cabac_zero_word` and the third byte 0x03 represents an `emulation_prevention_three_byte`. + +## Annex A + +### Profiles and levels + +(This annex forms an integral part of this Recommendation | International Standard.) + +Profiles and levels specify restrictions on bitstreams and hence limits on the capabilities needed to decode the bitstreams. Profiles and levels may also be used to indicate interoperability points between individual decoder implementations. + +NOTE 1 – This Recommendation | International Standard does not include individually selectable "options" at the decoder, as this would increase interoperability difficulties. + +Each profile specifies a subset of algorithmic features and limits that shall be supported by all decoders conforming to that profile. + +NOTE 2 – Encoders are not required to make use of any particular subset of features supported in a profile. + +Each level specifies a set of limits on the values that may be taken by the syntax elements of this Recommendation | International Standard. The same set of level definitions is used with all profiles, but individual implementations may support a different level for each supported profile. For any given profile, levels generally correspond to decoder processing load and memory capability. + +The profiles that are specified in clause A.2 are also referred to as the profiles specified in Annex A. + +#### A.1 Requirements on video decoder capability + +Capabilities of video decoders conforming to this Recommendation | International Standard are specified in terms of the ability to decode video streams conforming to the constraints of profiles and levels specified in this annex. For each such profile, the level supported for that profile shall also be expressed. + +Specific values are specified in this annex for the syntax elements `profile_idc` and `level_idc`. All other values of `profile_idc` and `level_idc` are reserved for future use by ITU-T | ISO/IEC. + +NOTE – Decoders should not infer that when a reserved value of `profile_idc` or `level_idc` falls between the values specified in this Recommendation | International Standard that this indicates intermediate capabilities between the specified profiles or levels, as there are no restrictions on the method to be chosen by ITU-T | ISO/IEC for the use of such future reserved values. + +#### A.2 Profiles + +All constraints for picture parameter sets that are specified in clauses A.2.1 to A.2.11 are constraints for picture parameter sets that are activated in the bitstream. All constraints for sequence parameter sets that are specified in clauses A.2.1 to A.2.11 are constraints for sequence parameter sets that are activated in the bitstream. + +##### A.2.1 Baseline profile + +Bitstreams conforming to the Baseline profile shall obey the following constraints: + +- Only I and P slice types may be present. +- NAL unit streams shall not contain `nal_unit_type` values in the range of 2 to 4, inclusive. +- Sequence parameter sets shall have `frame_mbs_only_flag` equal to 1. +- The syntax elements `chroma_format_idc`, `bit_depth_luma_minus8`, `bit_depth_chroma_minus8`, `qprime_y_zero_transform_bypass_flag`, and `seq_scaling_matrix_present_flag` shall not be present in sequence parameter sets. +- Picture parameter sets shall have `weighted_pred_flag` and `weighted_bipred_idc` both equal to 0. +- Picture parameter sets shall have `entropy_coding_mode_flag` equal to 0. +- Picture parameter sets shall have `num_slice_groups_minus1` in the range of 0 to 7, inclusive. +- The syntax elements `transform_8x8_mode_flag`, `pic_scaling_matrix_present_flag`, and `second_chroma_qp_index_offset` shall not be present in picture parameter sets. +- The syntax element `level_prefix` shall not be greater than 15 (when present). +- The syntax elements `pcm_sample_luma[ i ]`, with $i = 0..255$ , and `pcm_sample_chroma[ i ]`, with $i = 0..2 * \text{MbWidthC} * \text{MbHeightC} - 1$ , shall not be equal to 0 (when present). +- The level constraints specified for the Baseline profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the Baseline profile is indicated by profile\_idc being equal to 66. + +Decoders conforming to the Baseline profile at a specific level shall be capable of decoding all bitstreams in which profile\_idc is equal to 66 or constraint\_set0\_flag is equal to 1 and in which level\_idc and constraint\_set3\_flag represent a level less than or equal to the specified level. + +#### A.2.1.1 Constrained Baseline profile + +Bitstreams conforming to the Constrained Baseline profile shall obey all constraints specified in clause A.2.1 for the Baseline profile and all constraints specified in clause A.2.2 for the Main profile. + +Conformance of a bitstream to the Constrained Baseline profile is indicated by profile\_idc being equal to 66 with constraint\_set1\_flag being equal to 1. + +NOTE – This specification of the Constrained Baseline profile is technically identical to specification of the use of the Baseline profile with constraint\_set1\_flag equal to 1. Thus, any existing specifications (in other documents that reference this Recommendation | International Standard) that have referred to the use of the Baseline profile with constraint\_set1\_flag equal to 1 should thus be interpreted as continuing in force as being technically identical to referring to the use of the Constrained Baseline profile (without any need for revision of these existing specifications to instead refer explicitly to the use of the Constrained Baseline profile). + +Decoders conforming to the Constrained Baseline profile at a specific level shall be capable of decoding all bitstreams in which all of the following are true: + +- profile\_idc is equal to 66 or constraint\_set0\_flag is equal to 1, +- constraint\_set1\_flag is equal to 1, +- level\_idc and constraint\_set3\_flag represent a level less than or equal to the specified level. + +#### A.2.2 Main profile + +Bitstreams conforming to the Main profile shall obey the following constraints: + +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain nal\_unit\_type values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- The syntax elements chroma\_format\_idc, bit\_depth\_luma\_minus8, bit\_depth\_chroma\_minus8, qpprime\_y\_zero\_transform\_bypass\_flag, and seq\_scaling\_matrix\_present\_flag shall not be present in sequence parameter sets. +- Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0 only. +- Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0 only. +- The syntax elements transform\_8x8\_mode\_flag, pic\_scaling\_matrix\_present\_flag, and second\_chroma\_qp\_index\_offset shall not be present in picture parameter sets. +- The syntax element level\_prefix shall not be greater than 15 (when present). +- The syntax elements pcm\_sample\_luma[ i ], with $i = 0..255$ , and pcm\_sample\_chroma[ i ], with $i = 0..2 * \text{MbWidthC} * \text{MbHeightC} - 1$ , shall not be equal to 0 (when present). +- The level constraints specified for the Main profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the Main profile is indicated by profile\_idc being equal to 77. + +Decoders conforming to the Main profile at a specified level shall be capable of decoding all bitstreams in which profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1 and in which level\_idc and constraint\_set3\_flag represent a level less than or equal to the specified level. + +#### A.2.3 Extended profile + +Bitstreams conforming to the Extended profile shall obey the following constraints: + +- Sequence parameter sets shall have direct\_8x8\_inference\_flag equal to 1. +- The syntax elements chroma\_format\_idc, bit\_depth\_luma\_minus8, bit\_depth\_chroma\_minus8, qpprime\_y\_zero\_transform\_bypass\_flag, and seq\_scaling\_matrix\_present\_flag shall not be present in sequence parameter sets. +- Picture parameter sets shall have entropy\_coding\_mode\_flag equal to 0. +- Picture parameter sets shall have num\_slice\_groups\_minus1 in the range of 0 to 7, inclusive. +- The syntax elements transform\_8x8\_mode\_flag, pic\_scaling\_matrix\_present\_flag, and second\_chroma\_qp\_index\_offset shall not be present in picture parameter sets. + +- The syntax element `level_prefix` shall not be greater than 15 (when present). +- The syntax elements `pcm_sample_luma[ i ]`, with $i = 0..255$ , and `pcm_sample_chroma[ i ]`, with $i = 0..2 * \text{MbWidthC} * \text{MbHeightC} - 1$ , shall not be equal to 0 (when present). +- The level constraints specified for the Extended profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the Extended profile is indicated by `profile_idc` being equal to 88. + +Decoders conforming to the Extended profile at a specified level shall be capable of decoding all bitstreams in which `profile_idc` is equal to 88 or `constraint_set2_flag` is equal to 1 and in which `level_idc` represents a level less than or equal to specified level. + +Decoders conforming to the Extended profile at a specified level shall also be capable of decoding all bitstreams in which `profile_idc` is equal to 66 or `constraint_set0_flag` is equal to 1, in which `level_idc` and `constraint_set3_flag` represent a level less than or equal to the specified level. + +#### A.2.4 High profile + +Bitstreams conforming to the High profile shall obey the following constraints: + +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain `nal_unit_type` values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have `num_slice_groups_minus1` equal to 0 only. +- Picture parameter sets shall have `redundant_pic_cnt_present_flag` equal to 0 only. +- Sequence parameter sets shall have `chroma_format_idc` in the range of 0 to 1 inclusive. +- Sequence parameter sets shall have `bit_depth_luma_minus8` equal to 0 only. +- Sequence parameter sets shall have `bit_depth_chroma_minus8` equal to 0 only. +- Sequence parameter sets shall have `qpprime_y_zero_transform_bypass_flag` equal to 0 only. +- The level constraints specified for the High profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the High profile is indicated by `profile_idc` being equal to 100. Decoders conforming to the High profile at a specific level shall be capable of decoding all bitstreams in which either or both of the following conditions are true: + +- (`profile_idc` is equal to 77 or `constraint_set1_flag` is equal to 1) and the combination of `level_idc` and `constraint_set3_flag` represent a level less than or equal to the specified level, +- `profile_idc` is equal to 100 and `level_idc` represents a level less than or equal to the specified level. + +NOTE – The value 100 for `profile_idc` indicates that the bitstream conforms to the High profile as specified in this clause. When `profile_idc` is equal to 100 and `constraint_set3_flag` is equal to 1, this indicates that the bitstream conforms to the High profile and additionally conforms to the constraints specified for the High 10 Intra profile in clause A.2.8. For example, such a bitstream must have `bit_depth_luma_minus8` equal to 0, have `bit_depth_chroma_minus8` equal to 0, obey the MinCR, MaxBR and MaxCPB constraints of the High profile, contain only IDR pictures, have `max_num_ref_frames` equal to 0, have `dpb_output_delay` equal to 0, and obey the maximum slice size constraint of the High 10 Intra profile. + +##### A.2.4.1 Progressive High profile + +Bitstreams conforming to the Progressive High profile shall obey all constraints specified in clause A.2.4 for the High profile, and shall additionally obey the constraint that sequence parameter sets shall have `frame_mbs_only_flag` equal to 1. + +Conformance of a bitstream to the Progressive High profile is indicated by `profile_idc` being equal to 100 with `constraint_set4_flag` being equal to 1. + +Decoders conforming to the Progressive High profile at a specific level shall be capable of decoding all bitstreams in which one or more of the following conditions are true: + +- (`profile_idc` is equal to 66 or `constraint_set0_flag` is equal to 1), `constraint_set1_flag` is equal to 1, and the combination of `level_idc` and `constraint_set3_flag` represents a level less than or equal to the specified level. +- `profile_idc` is equal to 77, `constraint_set0_flag` is equal to 1, and the combination of `level_idc` and `constraint_set3_flag` represents a level less than or equal to the specified level. +- `profile_idc` is equal to 77, `constraint_set4_flag` is equal to 1, and the combination of `level_idc` and `constraint_set3_flag` represents a level less than or equal to the specified level. + +- profile\_idc is equal to 88, constraint\_set1\_flag is equal to 1, constraint\_set4\_flag is equal to 1, and the combination of level\_idc and constraint\_set3\_flag represents a level less than or equal to the specified level. +- profile\_idc is equal to 100, constraint\_set4\_flag is equal to 1, and level\_idc represents a level less than or equal to the specified level. + +#### A.2.4.2 Constrained High profile + +Bitstreams conforming to the Constrained High profile shall obey all constraints specified in clause A.2.4.1 for the Progressive High profile, and shall additionally obey the constraint that B slice types shall not be present. + +Conformance of a bitstream to the Constrained High profile is indicated by profile\_idc being equal to 100 with both constraint\_set4\_flag and constraint\_set5\_flag being equal to 1. + +Decoders conforming to the Constrained High profile at a specific level shall be capable of decoding all bitstreams in which one or more of the following conditions are true: + +- (profile\_idc is equal to 66 or constraint\_set0\_flag is equal to 1), constraint\_set1\_flag is equal to 1, and the combination of level\_idc and constraint\_set3\_flag represents a level less than or equal to the specified level. +- profile\_idc is equal to 77, constraint\_set0\_flag is equal to 1, and the combination of level\_idc and constraint\_set3\_flag represents a level less than or equal to the specified level. +- profile\_idc is equal to 77, constraint\_set4\_flag is equal to 1, constraint\_set5\_flag is equal to 1, and level\_idc represents a level less than or equal to the specified level. +- profile\_idc is equal to 88, constraint\_set1\_flag is equal to 1, constraint\_set4\_flag is equal to 1, constraint\_set5\_flag is equal to 1, and the combination of level\_idc and constraint\_set3\_flag represents a level less than or equal to the specified level. +- profile\_idc is equal to 100, constraint\_set4\_flag is equal to 1, constraint\_set5\_flag is equal to 1, and level\_idc represents a level less than or equal to the specified level. + +#### A.2.5 High 10 profile + +Bitstreams conforming to the High 10 profile shall obey the following constraints: + +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain nal\_unit\_type values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0 only. +- Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0 only. +- Sequence parameter sets shall have chroma\_format\_idc in the range of 0 to 1 inclusive. +- Sequence parameter sets shall have bit\_depth\_luma\_minus8 in the range of 0 to 2 inclusive. +- Sequence parameter sets shall have bit\_depth\_chroma\_minus8 in the range of 0 to 2 inclusive. +- Sequence parameter sets shall have qpprime\_y\_zero\_transform\_bypass\_flag equal to 0 only. +- The level constraints specified for the High 10 profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the High 10 profile is indicated by profile\_idc being equal to 110. Decoders conforming to the High 10 profile at a specific level shall be capable of decoding all bitstreams in which either or both of the following conditions are true: + +- (profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1) and the combination of level\_idc and constraint\_set3\_flag represent a level less than or equal to the specified level, +- profile\_idc is equal to 100 or 110 and level\_idc represents a level less than or equal to the specified level. + +##### A.2.5.1 Progressive High 10 profile + +Bitstreams conforming to the Progressive High 10 profile shall obey all constraints specified in clause A.2.5 for the High 10 profile, and shall additionally obey the constraint that sequence parameter sets shall have frame\_mbs\_only\_flag equal to 1. + +Conformance of a bitstream to the Progressive High 10 profile is indicated by profile\_idc being equal to 110 with constraint\_set4\_flag being equal to 1. + +Decoders conforming to the Progressive High 10 profile at a specific level shall be capable of decoding all bitstreams in which one or more of the following conditions are true: + +- (profile\_idc is equal to 66 or constraint\_set0\_flag is equal to 1), constraint\_set1\_flag is equal to 1, and the combination of level\_idc and constraint\_set3\_flag represents a level less than or equal to the specified level. +- profile\_idc is equal to 77, constraint\_set0\_flag is equal to 1, and the combination of level\_idc and constraint\_set3\_flag represents a level less than or equal to the specified level. +- profile\_idc is equal to 77, constraint\_set4\_flag is equal to 1, and the combination of level\_idc and constraint\_set3\_flag represents a level less than or equal to the specified level. +- profile\_idc is equal to 88, constraint\_set1\_flag is equal to 1, constraint\_set4\_flag is equal to 1, and the combination of level\_idc and constraint\_set3\_flag represents a level less than or equal to the specified level. +- profile\_idc is equal to 100 or 110, constraint\_set4\_flag is equal to 1, and level\_idc represents a level less than or equal to the specified level. + +#### **A.2.6 High 4:2:2 profile** + +Bitstreams conforming to the High 4:2:2 profile shall obey the following constraints: + +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain nal\_unit\_type values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0 only. +- Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0 only. +- Sequence parameter sets shall have chroma\_format\_idc in the range of 0 to 2 inclusive. +- Sequence parameter sets shall have bit\_depth\_luma\_minus8 in the range of 0 to 2 inclusive. +- Sequence parameter sets shall have bit\_depth\_chroma\_minus8 in the range of 0 to 2 inclusive. +- Sequence parameter sets shall have qpprime\_y\_zero\_transform\_bypass\_flag equal to 0 only. +- The level constraints specified for the High 4:2:2 profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the High 4:2:2 profile is indicated by profile\_idc being equal to 122. Decoders conforming to the High 4:2:2 profile at a specific level shall be capable of decoding all bitstreams in which either or both of the following conditions are true: + +- (profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1) and the combination of level\_idc and constraint\_set3\_flag represent a level less than or equal to the specified level, +- profile\_idc is equal to 100, 110, or 122 and level\_idc represents a level less than or equal to the specified level. + +#### **A.2.7 High 4:4:4 Predictive profile** + +Bitstreams conforming to the High 4:4:4 Predictive profile shall obey the following constraints: + +- Only I, P, B slice types may be present. +- NAL unit streams shall not contain nal\_unit\_type values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0 only. +- Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0 only. +- Sequence parameter sets shall have bit\_depth\_luma\_minus8 in the range of 0 to 6 inclusive. +- Sequence parameter sets shall have bit\_depth\_chroma\_minus8 in the range of 0 to 6 inclusive. +- The level constraints specified for the High 4:4:4 Predictive profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the High 4:4:4 Predictive profile is indicated by profile\_idc being equal to 244. Decoders conforming to the High 4:4:4 Predictive profile at a specific level shall be capable of decoding all bitstreams in which either or both of the following conditions are true: + +- (profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1) and the combination of level\_idc and constraint\_set3\_flag represent a level less than or equal to the specified level, +- profile\_idc is equal to 44, 100, 110, 122, or 244 and the value of level\_idc represents a level less than or equal to the specified level. + +### A.2.8 High 10 Intra profile + +Bitstreams conforming to the High 10 Intra profile shall obey the following constraints: + +- All constraints specified in clause A.2.5 for the High 10 profile shall be obeyed. +- All pictures shall be IDR pictures. +- Sequence parameter sets shall have max\_num\_ref\_frames equal to 0. +- When vui\_parameters\_present\_flag is equal to 1 and bitstream\_restriction\_flag is equal to 1, sequence parameter sets shall have max\_num\_reorder\_frames equal to 0. +- When vui\_parameters\_present\_flag is equal to 1 and bitstream\_restriction\_flag is equal to 1, sequence parameter sets shall have max\_dec\_frame\_buffering equal to 0. +- Picture timing SEI messages, whether present in the bitstream (by non-VCL NAL units) or conveyed equivalently by other means not specified in this Recommendation | International Standard, shall have dpb\_output\_delay equal to 0. +- The level constraints specified for the High 10 Intra profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the High 10 Intra profile is indicated by constraint\_set3\_flag being equal to 1 with profile\_idc equal to 110. Decoders conforming to the High 10 Intra profile at a specific level shall be capable of decoding all bitstreams in which all of the following conditions are true: + +- profile\_idc is equal to 100 or 110, +- constraint\_set3\_flag is equal to 1, +- level\_idc represents a level less than or equal to the specified level. + +NOTE 1 – The value 100 for profile\_idc indicates that the bitstream conforms to the High profile as specified in clause A.2.4. When profile\_idc is equal to 100 and constraint\_set3\_flag is equal to 1, this indicates that the bitstream conforms to the High profile and additionally conforms to the constraints specified for the High 10 Intra profile in this clause. For example, such a bitstream must have bit\_depth\_luma\_minus8 equal to 0, have bit\_depth\_chroma\_minus8 equal to 0, obey the MinCR, MaxBR and MaxCPB constraints of the High profile, contain only IDR pictures, have max\_num\_ref\_frames equal to 0, have dpb\_output\_delay equal to 0, and obey the maximum slice size constraint of the High 10 Intra profile. + +The operation of the deblocking filter process specified in clause 8.7 is not required for decoder conformance to the High 10 Intra profile. + +NOTE 2 – The deblocking filter process specified in clause 8.7 or some similar post-processing filter should be performed, although this is not a requirement for decoder conformance to the High 10 Intra profile. The syntax elements sent by an encoder for control of the deblocking filter process specified in clause 8.7 are considered only as advisory information for decoders conformance to the High 10 Intra profile. However, the application of the deblocking filter process specified in clause 8.7 is required for decoder conformance to the High 10, High 4:2:2, and High 4:4:4 Predictive profiles when decoding bitstreams that conform to the High 10 Intra profile. + +### A.2.9 High 4:2:2 Intra profile + +Bitstreams conforming to the High 4:2:2 Intra profile shall obey the following constraints: + +- All constraints specified in clause A.2.6 for the High 4:2:2 profile shall be obeyed. +- All pictures shall be IDR pictures. +- Sequence parameter sets shall have max\_num\_ref\_frames equal to 0. +- When vui\_parameters\_present\_flag is equal to 1 and bitstream\_restriction\_flag is equal to 1, sequence parameter sets shall have max\_num\_reorder\_frames equal to 0. +- When vui\_parameters\_present\_flag is equal to 1 and bitstream\_restriction\_flag is equal to 1, sequence parameter sets shall have max\_dec\_frame\_buffering equal to 0. +- Picture timing SEI messages, whether present in the bitstream (by non-VCL NAL units) or conveyed equivalently by other means not specified in this Recommendation | International Standard, shall have dpb\_output\_delay equal to 0. +- The level constraints specified for the High 4:2:2 Intra profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the High 4:2:2 Intra profile is indicated by constraint\_set3\_flag being equal to 1 with profile\_idc equal to 122. Decoders conforming to the High 4:2:2 Intra profile at a specific level shall be capable of decoding all bitstreams in which all of the following conditions are true: + +- profile\_idc is equal to 100, 110, or 122, +- constraint\_set3\_flag is equal to 1, +- level\_idc represents a level less than or equal to the specified level. + +The operation of the deblocking filter process specified in clause 8.7 is not required for decoder conformance to the High 4:2:2 Intra profile. + +NOTE – The deblocking filter process specified in clause 8.7 or some similar post-processing filter should be performed, although this is not a requirement for decoder conformance to the High 4:2:2 Intra profile. The syntax elements sent by an encoder for control of the deblocking filter process specified in clause 8.7 are considered only as advisory information for decoders conformance to the High 4:2:2 Intra profile. However, the application of the deblocking filter process specified in clause 8.7 is required for decoder conformance to the High 4:2:2, and High 4:4:4 Predictive profiles when decoding bitstreams that conform to the High 4:2:2 Intra profile. + +#### **A.2.10 High 4:4:4 Intra profile** + +Bitstreams conforming to the High 4:4:4 Intra profile shall obey the following constraints: + +- All constraints specified in clause A.2.7 for the High 4:4:4 Predictive profile shall be obeyed. +- All pictures shall be IDR pictures. +- Sequence parameter sets shall have max\_num\_ref\_frames equal to 0. +- When vui\_parameters\_present\_flag is equal to 1 and bitstream\_restriction\_flag is equal to 1, sequence parameter sets shall have max\_num\_reorder\_frames equal to 0. +- When vui\_parameters\_present\_flag is equal to 1 and bitstream\_restriction\_flag is equal to 1, sequence parameter sets shall have max\_dec\_frame\_buffering equal to 0. +- Picture timing SEI messages, whether present in the bitstream (by non-VCL NAL units) or conveyed equivalently by other means not specified in this Recommendation | International Standard, shall have dpb\_output\_delay equal to 0. +- The level constraints specified for the High 4:4:4 Intra profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the High 4:4:4 Intra profile is indicated by constraint\_set3\_flag being equal to 1 with profile\_idc equal to 244. Decoders conforming to the High 4:4:4 Intra profile at a specific level shall be capable of decoding all bitstreams in which all of the following conditions are true: + +- profile\_idc is equal to 44, 100, 110, 122, or 244, +- constraint\_set3\_flag is equal to 1, +- level\_idc represents a level less than or equal to the specified level. + +The operation of the deblocking filter process specified in clause 8.7 is not required for decoder conformance to the High 4:4:4 Intra profile. + +NOTE – The deblocking filter process specified in clause 8.7 or some similar post-processing filter should be performed, although this is not a requirement for decoder conformance to the High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles. The syntax elements sent by an encoder for control of the deblocking filter process specified in clause 8.7 are considered only as advisory information for decoders conformance to the High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles. However, the application of the deblocking filter process specified in clause 8.7 is required for decoder conformance to the High 4:4:4 Predictive profile when decoding bitstreams that conform to the High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles. + +#### **A.2.11 CAVLC 4:4:4 Intra profile** + +Bitstreams conforming to the CAVLC 4:4:4 Intra profile shall obey the following constraints: + +- All constraints specified in clause A.2.10 for the High 4:4:4 Intra profile shall be obeyed. +- Picture parameter sets shall have entropy\_coding\_mode\_flag equal to 0. +- The level constraints specified for the CAVLC 4:4:4 Intra profile in clause A.3 shall be fulfilled. + +Conformance of a bitstream to the CAVLC 4:4:4 Intra profile is indicated by profile\_idc being equal to 44. Decoders conforming to the CAVLC 4:4:4 Intra profile at a specific level shall be capable of decoding all bitstreams in which all of the following conditions are true: + +- profile\_idc is equal to 44, +- level\_idc represents a level less than or equal to the specified level. + +The operation of the deblocking filter process specified in clause 8.7 is not required for decoder conformance to the CAVLC 4:4:4 Intra profile. + +NOTE – The deblocking filter process specified in clause 8.7 or some similar post-processing filter should be performed, although this is not a requirement for decoder conformance to the High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles. The syntax elements sent by an encoder for control of the deblocking filter process specified in clause 8.7 are considered only as advisory information for decoders conformance to the High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles. However, the application of the deblocking filter process specified in clause 8.7 is required for decoder conformance to the High 4:4:4 Predictive profile when decoding bitstreams that conform to the High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles. + +### A.3 Levels + +The following is specified for expressing the constraints in this annex. + +- Let access unit $n$ be the $n$ -th access unit in decoding order with the first access unit being access unit 0. +- Let picture $n$ be the primary coded picture or the corresponding decoded picture of access unit $n$ . + +Let the variable $fR$ be derived as follows: + +- If the level number is equal to 6.0, 6.1, or 6.2, $fR$ is set equal to $1 \div 300$ . +- Otherwise, if picture $n$ is a frame, $fR$ is set equal to $1 \div 172$ . +- Otherwise (picture $n$ is a field), $fR$ is set equal to $1 \div (172 * 2)$ . + +#### A.3.1 Level limits common to the Baseline, Constrained Baseline, Main, and Extended profiles + +Bitstreams conforming to the Baseline, Constrained Baseline, Main, or Extended profiles at a specified level shall obey the following constraints: + +- The nominal removal time of access unit $n$ with $n > 0$ from the CPB as specified in clause C.1.2, satisfies the constraint that $t_{r,n}(n) - t_r(n-1)$ is greater than or equal to $\text{Max}(\text{PicSizeInMbs} \div \text{MaxMBPS}, fR)$ , where $\text{MaxMBPS}$ is the value specified in Table A-1 that applies to picture $n-1$ and $\text{PicSizeInMbs}$ is the number of macroblocks in picture $n-1$ . +- The difference between consecutive output times of pictures from the DPB as specified in clause C.2.2, satisfies the constraint that $\Delta t_{o,dpb}(n) \geq \text{Max}(\text{PicSizeInMbs} \div \text{MaxMBPS}, fR)$ , where $\text{MaxMBPS}$ is the value specified in Table A-1 for picture $n$ and $\text{PicSizeInMbs}$ is the number of macroblocks of picture $n$ , provided that picture $n$ is a picture that is output and is not the last picture of the bitstream that is output. +- The sum of the $\text{NumBytesInNALunit}$ variables for access unit 0 is less than or equal to $384 * (\text{Max}(\text{PicSizeInMbs}, fR * \text{MaxMBPS}) + \text{MaxMBPS} * (t_r(0) - t_{r,n}(0))) \div \text{MinCR}$ , where $\text{MaxMBPS}$ and $\text{MinCR}$ are the values specified in Table A-1 that apply to picture 0 and $\text{PicSizeInMbs}$ is the number of macroblocks in picture 0. +- The sum of the $\text{NumBytesInNALunit}$ variables for access unit $n$ with $n > 0$ is less than or equal to $384 * \text{MaxMBPS} * (t_r(n) - t_r(n-1)) \div \text{MinCR}$ , where $\text{MaxMBPS}$ and $\text{MinCR}$ are the values specified in Table A-1 that apply to picture $n$ . +- $\text{PicWidthInMbs} * \text{FrameHeightInMbs} \leq \text{MaxFS}$ , where $\text{MaxFS}$ is specified in Table A-1 +- $\text{PicWidthInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ +- $\text{FrameHeightInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ +- $\text{max\_dec\_frame\_buffering} \leq \text{MaxDpbFrames}$ , where $\text{MaxDpbFrames}$ is equal to $\text{Min}(\text{MaxDpbMbs} / (\text{PicWidthInMbs} * \text{FrameHeightInMbs}), 16)$ and $\text{MaxDpbMbs}$ is given in Table A-1. +- For the VCL HRD parameters, $\text{BitRate}[\text{SchedSelIdx}] \leq 1000 * \text{MaxBR}$ and $\text{CpbSize}[\text{SchedSelIdx}] \leq 1000 * \text{MaxCPB}$ for at least one value of $\text{SchedSelIdx}$ , where $\text{BitRate}[\text{SchedSelIdx}]$ and $\text{CpbSize}[\text{SchedSelIdx}]$ are given as follows: + - If $\text{vcl\_hrd\_parameters\_present\_flag}$ is equal to 1, $\text{BitRate}[\text{SchedSelIdx}]$ and $\text{CpbSize}[\text{SchedSelIdx}]$ are given by Equations E-81 and E-82, respectively, using the syntax elements of the $\text{hrd\_parameters}()$ syntax structure that immediately follows $\text{vcl\_hrd\_parameters\_present\_flag}$ . + - Otherwise ( $\text{vcl\_hrd\_parameters\_present\_flag}$ is equal to 0), $\text{BitRate}[\text{SchedSelIdx}]$ and $\text{CpbSize}[\text{SchedSelIdx}]$ are inferred as specified in clause E.2.2 for VCL HRD parameters. + +$\text{MaxBR}$ and $\text{MaxCPB}$ are specified in Table A-1 in units of 1000 bits/s and 1000 bits, respectively. The bitstream shall satisfy these conditions for at least one value of $\text{SchedSelIdx}$ in the range 0 to $\text{cpb\_cnt\_minus1}$ , inclusive. + +- For the NAL HRD parameters, $\text{BitRate}[\text{SchedSelIdx}] \leq 1200 * \text{MaxBR}$ and $\text{CpbSize}[\text{SchedSelIdx}] \leq 1200 * \text{MaxCPB}$ for at least one value of $\text{SchedSelIdx}$ , where $\text{BitRate}[\text{SchedSelIdx}]$ and $\text{CpbSize}[\text{SchedSelIdx}]$ are given as follows: + - If $\text{nal\_hrd\_parameters\_present\_flag}$ is equal to 1, $\text{BitRate}[\text{SchedSelIdx}]$ and $\text{CpbSize}[\text{SchedSelIdx}]$ are given by Equations E-81 and E-82, respectively, using the syntax elements of the $\text{hrd\_parameters}()$ syntax structure that immediately follows $\text{nal\_hrd\_parameters\_present\_flag}$ . + - Otherwise ( $\text{nal\_hrd\_parameters\_present\_flag}$ is equal to 0), $\text{BitRate}[\text{SchedSelIdx}]$ and $\text{CpbSize}[\text{SchedSelIdx}]$ are inferred as specified in clause E.2.2 for NAL HRD parameters. + +MaxBR and MaxCPB are specified in Table A-1 in units of 1200 bits/s and 1200 bits, respectively. The bitstream shall satisfy these conditions for at least one value of SchedSelIdx in the range 0 to cpb\_cnt\_minus1. + +- k) The vertical motion vector component range for luma motion vectors does not exceed the range from $-MaxVmvR$ to $(MaxVmvR - 0.25)$ in units of luma frame samples, where $MaxVmvR$ is specified in Table A-1 + +NOTE 1 – When $chroma\_format\_idc$ is equal to 1 and the current macroblock is a field macroblock, the motion vector component range for chroma motion vectors may exceed the range from $-MaxVmvR$ to $(MaxVmvR - 0.25)$ in units of luma frame samples, due to the method of deriving chroma motion vectors as specified in clause 8.4.1.4. + +- l) The horizontal motion vector component range for luma motion vectors does not exceed the following range: + - If the level number is less than 6.0, the specified range is from $-2048$ to $2047.75$ , inclusive, in units of luma samples. + - Otherwise, the specified range is from $-8192$ to $8191.75$ , inclusive, in units of luma samples. +- m) Let $setOf2Mb$ be the set of unsorted pairs of macroblocks that contains the unsorted pairs of macroblocks ( $mbA$ , $mbB$ ) of a coded video sequence for which any of the following conditions are true: + - $mbA$ and $mbB$ are macroblocks that belong to the same slice and are consecutive in decoding order, + - arbitrary slice order is not allowed, $mbA$ is the last macroblock (in decoding order) of a slice, and $mbB$ is the first macroblock (in decoding order) of the next slice in decoding order, + - NOTE 2 – The macroblocks $mbA$ and $mbB$ can belong to different pictures. + - arbitrary slice order is allowed, $mbA$ is the last macroblock (in decoding order) of a slice of a particular picture, and $mbB$ is the first macroblock (in decoding order) of any other slice of the same picture, + - arbitrary slice order is allowed, $mbA$ is the last macroblock (in decoding order) of a slice of a particular picture, and $mbB$ is the first macroblock (in decoding order) of any slice of the next picture in decoding order. + +For each unsorted pair of macroblocks ( $mbA$ , $mbB$ ) of the set $setOf2Mb$ , the total number of motion vectors (given by the sum of the number of motion vectors for macroblock $mbA$ and the number of motion vectors for macroblock $mbB$ ) does not exceed $MaxMvsPer2Mb$ , where $MaxMvsPer2Mb$ is specified in Table A-1. The number of motion vectors for each macroblock is the value of the variable $MvCnt$ after the completion of the intra or inter prediction process for the macroblock. + +NOTE 3 – The constraint specifies that the total number of motion vectors for two consecutive macroblocks in decoding order must not exceed $MaxMvsPer2Mb$ . When arbitrary slice order is allowed, it is specified that this constraint must also be obeyed when slices of a picture are reordered, e.g., during transmission. + +- n) The number of bits of $macroblock\_layer()$ data for any macroblock is not greater than 3200. Depending on $entropy\_coding\_mode\_flag$ , the bits of $macroblock\_layer()$ data are counted as follows: + - If $entropy\_coding\_mode\_flag$ is equal to 0, the number of bits of $macroblock\_layer()$ data is given by the number of bits in the $macroblock\_layer()$ syntax structure for a macroblock. + - Otherwise ( $entropy\_coding\_mode\_flag$ is equal to 1), the number of bits of $macroblock\_layer()$ data for a macroblock is given by the number of times $read\_bits(1)$ is called in clauses 9.3.3.2.2 and 9.3.3.2.3 when parsing the $macroblock\_layer()$ associated with the macroblock. + +Table A-1 specifies the limits for each level. A definition of all levels identified in the "Level number" column of Table A-1 is specified for the Baseline, Constrained Baseline, Main, and Extended profiles. Each entry in Table A-1 indicates, for the level corresponding to the row of the table, the absence or value of a limit that is imposed by the variable corresponding to the column of the table, as follows: + +- If the table entry is marked as "-", no limit is imposed by the value of the variable as a requirement of bitstream conformance to the profile at the specified level. +- Otherwise, the table entry specifies the value of the variable for the associated limit that is imposed as a requirement of bitstream conformance to the profile at the specified level. + +For purposes of comparison of level capabilities, a level shall be considered to be a lower (higher) level than some other level if the level appears nearer to the top (bottom) row of Table A-1 than the other level. + +In bitstreams conforming to the Baseline, Constrained Baseline, Main, or Extended profiles, the conformance of the bitstream to a specified level is indicated by the syntax elements $level\_idc$ and $constraint\_set3\_flag$ as follows: + +- If $level\_idc$ is equal to 11 and $constraint\_set3\_flag$ is equal to 1, the indicated level is level 1b. + +- Otherwise (level\_idc is not equal to 11 or constraint\_set3\_flag is not equal to 1), level\_idc is equal to a value of ten times the level number (of the indicated level) specified in Table A-1. + +**Table A-1 – Level limits** + +| Level number | Max macroblock processing rate MaxMBPS (MB/s) | Max frame size MaxFS (MBs) | Max decoded picture buffer size MaxDpbMbs (MBs) | Max video bit rate MaxBR (1000 bits/s, 1200 bits/s, cpbBrVclFactor bits/s, or cpbBrNalFactor bits/s) | Max CPB size MaxCPB (1000 bits, 1200 bits, cpbBrVclFactor bits, or cpbBrNalFactor bits) | Vertical MV component limit MaxVmvR (luma frame samples) | Min compression ratio MinCR | Max number of motion vectors per two consecutive MBs MaxMvsPer2Mb | +|--------------|-----------------------------------------------|----------------------------|-------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------------------------------------|-----------------------------|-------------------------------------------------------------------| +| 1 | 1 485 | 99 | 396 | 64 | 175 | 64 | 2 | - | +| 1b | 1 485 | 99 | 396 | 128 | 350 | 64 | 2 | - | +| 1.1 | 3 000 | 396 | 900 | 192 | 500 | 128 | 2 | - | +| 1.2 | 6 000 | 396 | 2 376 | 384 | 1 000 | 128 | 2 | - | +| 1.3 | 11 880 | 396 | 2 376 | 768 | 2 000 | 128 | 2 | - | +| 2 | 11 880 | 396 | 2 376 | 2 000 | 2 000 | 128 | 2 | - | +| 2.1 | 19 800 | 792 | 4 752 | 4 000 | 4 000 | 256 | 2 | - | +| 2.2 | 20 250 | 1 620 | 8 100 | 4 000 | 4 000 | 256 | 2 | - | +| 3 | 40 500 | 1 620 | 8 100 | 10 000 | 10 000 | 256 | 2 | 32 | +| 3.1 | 108 000 | 3 600 | 18 000 | 14 000 | 14 000 | 512 | 4 | 16 | +| 3.2 | 216 000 | 5 120 | 20 480 | 20 000 | 20 000 | 512 | 4 | 16 | +| 4 | 245 760 | 8 192 | 32 768 | 20 000 | 25 000 | 512 | 4 | 16 | +| 4.1 | 245 760 | 8 192 | 32 768 | 50 000 | 62 500 | 512 | 2 | 16 | +| 4.2 | 522 240 | 8 704 | 34 816 | 50 000 | 62 500 | 512 | 2 | 16 | +| 5 | 589 824 | 22 080 | 110 400 | 135 000 | 135 000 | 512 | 2 | 16 | +| 5.1 | 983 040 | 36 864 | 184 320 | 240 000 | 240 000 | 512 | 2 | 16 | +| 5.2 | 2 073 600 | 36 864 | 184 320 | 240 000 | 240 000 | 512 | 2 | 16 | +| 6 | 4 177 920 | 139 264 | 696 320 | 240 000 | 240 000 | 8 192 | 2 | 16 | +| 6.1 | 8 355 840 | 139 264 | 696 320 | 480 000 | 480 000 | 8 192 | 2 | 16 | +| 6.2 | 16 711 680 | 139 264 | 696 320 | 800 000 | 800 000 | 8 192 | 2 | 16 | + +Levels with non-integer level numbers in Table A-1 are referred to as "intermediate levels". + +NOTE 4 – All levels have the same status, but some applications may choose to use only the integer-numbered levels. + +Informative clause A.3.4 shows the effect of these limits on frame rates for several example picture formats. + +### A.3.2 Level limits common to the High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles + +Bitstreams conforming to the High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, or CAVLC 4:4:4 Intra profiles at a specified level shall obey the following constraints: + +- The nominal removal time of access unit $n$ (with $n > 0$ ) from the CPB as specified in clause C.1.2, satisfies the constraint that $t_{r,n}(n) - t_{r,n}(n - 1)$ is greater than or equal to $\text{Max}(\text{PicSizeInMbs} \div \text{MaxMBPS}, f_R)$ , where $\text{MaxMBPS}$ is the value specified in Table A-1 that applies to picture $n - 1$ , and $\text{PicSizeInMbs}$ is the number of macroblocks in picture $n - 1$ . + +- b) The difference between consecutive output times of pictures from the DPB as specified in clause C.2.2, satisfies the constraint that $\Delta t_{o,dpb}(n) \geq \text{Max}(\text{PicSizeInMbs} \div \text{MaxMBPS}, f_R)$ , where $\text{MaxMBPS}$ is the value specified in Table A-1 for picture $n$ , and $\text{PicSizeInMbs}$ is the number of macroblocks of picture $n$ , provided that picture $n$ is a picture that is output and is not the last picture of the bitstream that is output. +- c) $\text{PicWidthInMbs} * \text{FrameHeightInMbs} \leq \text{MaxFS}$ , where $\text{MaxFS}$ is specified in Table A-1 +- d) $\text{PicWidthInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ +- e) $\text{FrameHeightInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ +- f) $\text{max\_dec\_frame\_buffering} \leq \text{MaxDpbFrames}$ , where $\text{MaxDpbFrames}$ is equal to $\text{Min}(\text{MaxDpbMbs} / (\text{PicWidthInMbs} * \text{FrameHeightInMbs}), 16)$ and $\text{MaxDpbMbs}$ is specified in Table A-1. +- g) The vertical motion vector component range for luma motion vectors does not exceed the range from $-\text{MaxVmvR}$ to $(\text{MaxVmvR} - 0.25)$ in units of luma frame samples, where $\text{MaxVmvR}$ is specified in Table A-1. +- h) The horizontal motion vector component range for luma motion vectors does not exceed the following range: + - If the level number is less than 6.0, the specified range is from $-2048$ to $2047.75$ , inclusive, in units of luma samples. + - Otherwise, the specified range is from $-8192$ to $8191.75$ , inclusive, in units of luma samples. +- i) Let $\text{setOf2Mb}$ be the set of unsorted pairs of macroblocks that contains the unsorted pairs of macroblocks $(\text{mbA}, \text{mbB})$ of a coded video sequence for which any of the following conditions are true: + - $\text{mbA}$ and $\text{mbB}$ are macroblocks that belong to the same slice and are consecutive in decoding order, + - $\text{separate\_colour\_plane\_flag}$ is equal to 0, $\text{mbA}$ is the last macroblock (in decoding order) of a slice, and $\text{mbB}$ is the first macroblock (in decoding order) of the next slice in decoding order, + - $\text{separate\_colour\_plane\_flag}$ is equal to 1, $\text{mbA}$ is the last macroblock (in decoding order) of a slice with a particular value of $\text{colour\_plane\_id}$ , and $\text{mbB}$ is the first macroblock (in decoding order) of the next slice with the same value of $\text{colour\_plane\_id}$ in decoding order. + +NOTE 1 – In the two above conditions, the macroblocks $\text{mbA}$ and $\text{mbB}$ can belong to different pictures. + +For each unsorted pair of macroblocks $(\text{mbA}, \text{mbB})$ of the set $\text{setOf2Mb}$ , the total number of motion vectors (given by the sum of the number of motion vectors for macroblock $\text{mbA}$ and the number of motion vectors for macroblock $\text{mbB}$ ) does not exceed $\text{MaxMvsPer2Mb}$ , where $\text{MaxMvsPer2Mb}$ is specified in Table A-1. The number of motion vectors for each macroblock is the value of the variable $\text{MvCnt}$ after the completion of the intra or inter prediction process for the macroblock. + +NOTE 2 – When $\text{separate\_colour\_plane\_flag}$ is equal to 0, the constraint specifies that the total number of motion vectors for two consecutive macroblocks in decoding order must not exceed $\text{MaxMvsPer2Mb}$ . When $\text{separate\_colour\_plane\_flag}$ is equal to 1, the constraint specifies that the total number of motion vectors for two consecutive macroblocks (in decoding order) with the same value of $\text{colour\_plane\_id}$ must not exceed $\text{MaxMvsPer2Mb}$ . For macroblocks that are consecutive in decoding order but are associated with a different value of $\text{colour\_plane\_id}$ , no constraint for the total number of motion vectors is specified. + +- j) The number of bits of $\text{macroblock\_layer}()$ data for any macroblock is not greater than $128 + \text{RawMbBits}$ . Depending on $\text{entropy\_coding\_mode\_flag}$ , the bits of $\text{macroblock\_layer}()$ data are counted as follows: + - If $\text{entropy\_coding\_mode\_flag}$ is equal to 0, the number of bits of $\text{macroblock\_layer}()$ data is given by the number of bits in the $\text{macroblock\_layer}()$ syntax structure for a macroblock. + - Otherwise ( $\text{entropy\_coding\_mode\_flag}$ is equal to 1), the number of bits of $\text{macroblock\_layer}()$ data for a macroblock is given by the number of times $\text{read\_bits}(1)$ is called in clauses 9.3.3.2.2 and 9.3.3.2.3 when parsing the $\text{macroblock\_layer}()$ associated with the macroblock. + +Table A-1 specifies the limits for each level. A definition of all levels identified in the "Level number" column of Table A-1 is specified for the High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles. Each entry in Table A-1 indicates, for the level corresponding to the row of the table, the absence or value of a limit that is imposed by the variable corresponding to the column of the table, as follows: + +- If the table entry is marked as "-", no limit is imposed by the value of the variable as a requirement of bitstream conformance to the profile at the specified level. +- Otherwise, the table entry specifies the value of the variable for the associated limit that is imposed as a requirement of bitstream conformance to the profile at the specified level. + +The use of the MinCR parameter column of Table A-1 for the High, High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles is specified in clause A.3.3. + +In bitstreams conforming to the High, High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, or CAVLC 4:4:4 Intra profiles, the conformance of the bitstream to a specified level is indicated by the syntax element `level_idc` as follows: + +- If `level_idc` is equal to 9, the indicated level is level 1b. +- Otherwise (`level_idc` is not equal to 9), `level_idc` is equal to a value of ten times the level number (of the indicated level) specified in Table A-1. + +### A.3.3 Profile-specific level limits + +- a) In bitstreams conforming to the Main, High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, or CAVLC 4:4:4 Intra profiles, the removal time of access unit 0 shall satisfy the constraint that the number of slices in picture 0 is less than or equal to $(\text{Max}(\text{PicSizeInMbs}, \text{fR} \cdot \text{MaxMBPS}) + \text{MaxMBPS} \cdot (t_r(0) - t_{r,n}(0)) \div \text{SliceRate})$ , where `MaxMBPS` and `SliceRate` are the values specified in Tables A-1 and A-4, respectively, that apply to picture 0 and `PicSizeInMbs` is the number of macroblocks in picture 0. +- b) In bitstreams conforming to the Main, High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, or CAVLC 4:4:4 Intra profiles, the difference between consecutive removal times of access units $n$ and $n - 1$ with $n > 0$ shall satisfy the constraint that the number of slices in picture $n$ is less than or equal to $\text{MaxMBPS} \cdot (t_r(n) - t_r(n - 1)) \div \text{SliceRate}$ , where `MaxMBPS` and `SliceRate` are the values specified in Tables A-1 and A-4, respectively, that apply to picture $n$ . +- c) In bitstreams conforming to the Main, High, Progressive High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive profiles, sequence parameter sets shall have `direct_8x8_inference_flag` equal to 1 for the levels specified in Table A-4. + +NOTE 1 – `direct_8x8_inference_flag` is not relevant to the Baseline, Constrained Baseline, Constrained High, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles as these profiles do not allow B slice types, and `direct_8x8_inference_flag` is equal to 1 for all levels of the Extended profile. + +- d) In bitstreams conforming to the Main, High, High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, CAVLC 4:4:4 Intra, or Extended profiles, sequence parameter sets shall have `frame_mbs_only_flag` equal to 1 for the levels specified in Table A-4 for the Main, High, High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, or CAVLC 4:4:4 Intra profiles and in Table A-5 for the Extended profile. + +NOTE 2 – `frame_mbs_only_flag` is equal to 1 for all levels of the Baseline, Constrained Baseline, Progressive High, Constrained High, and Progressive High 10 profiles (specified in clauses A.2.1, A.2.1.1, A.2.4.1, A.2.4.2, and A.2.5.1, respectively). + +- e) In bitstreams conforming to the Main, High, Progressive High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, or Extended profiles, the value of `sub_mb_type[ mbPartIdx ]` with `mbPartIdx = 0..3` in B macroblocks with `mb_type` equal to `B_8x8` shall not be equal to `B_Bi_8x4`, `B_Bi_4x8`, or `B_Bi_4x4` for the levels in which `MinLumaBiPredSize` is shown as 8x8 in Table A-4 for the Main, High, Progressive High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive profiles and in Table A-5 for the Extended profile. +- f) In bitstreams conforming to the Baseline, Constrained Baseline, or Extended profiles, $(xInt_{\max} - xInt_{\min} + 6) \cdot (yInt_{\max} - yInt_{\min} + 6) \leq \text{MaxSubMbRectSize}$ in macroblocks coded with `mb_type` equal to `P_8x8`, `P_8x8ref0` or `B_8x8` for all invocations of the process specified in clause 8.4.2.2.1 used to generate the predicted luma sample array for a single reference picture list (reference picture list 0 or reference picture list 1) for each 8x8 sub-macroblock with the macroblock partition index `mbPartIdx`, where $\text{NumSubMbPart}(\text{sub\_mb\_type}[ \text{mbPartIdx} ]) > 1$ , where `MaxSubMbRectSize` is specified in Table A-3 for the Baseline and Constrained Baseline profiles and in Table A-5 for the Extended profile and + - `xIntmin` is the minimum value of `xIntL` among all luma sample predictions for the sub-macroblock + - `xIntmax` is the maximum value of `xIntL` among all luma sample predictions for the sub-macroblock + - `yIntmin` is the minimum value of `yIntL` among all luma sample predictions for the sub-macroblock + - `yIntmax` is the maximum value of `yIntL` among all luma sample predictions for the sub-macroblock +- g) In bitstreams conforming to the High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, or CAVLC 4:4:4 Intra profiles, for the VCL HRD parameters, $\text{BitRate}[ \text{SchedSelIdx} ] \leq \text{cpbBrVclFactor} \cdot \text{MaxBR}$ and + +CpbSize[ SchedSelIdx ] $\leq$ cpbBrVclFactor \* MaxCPB for at least one value of SchedSelIdx, where cpbBrVclFactor is specified in Table A-2 and BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are given as follows: + +- If vcl\_hrd\_parameters\_present\_flag is equal to 1, BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are given by Equations E-81 and E-82, respectively, using the syntax elements of the hrd\_parameters( ) syntax structure that immediately follows vcl\_hrd\_parameters\_present\_flag. +- Otherwise (vcl\_hrd\_parameters\_present\_flag is equal to 0), BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are inferred as specified in clause E.2.2 for VCL HRD parameters. + +MaxBR and MaxCPB are specified in Table A-1 in units of cpbBrVclFactor bits/s and cpbBrVclFactor bits, respectively. The bitstream shall satisfy these conditions for at least one value of SchedSelIdx in the range 0 to cpb\_cnt\_minus1, inclusive. + +- h) In bitstreams conforming to the High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, or CAVLC 4:4:4 Intra profiles, for the NAL HRD parameters, BitRate[ SchedSelIdx ] $\leq$ cpbBrNalFactor \* MaxBR and CpbSize[ SchedSelIdx ] $\leq$ cpbBrNalFactor \* MaxCPB for at least one value of SchedSelIdx, where cpbBrNalFactor is specified in Table A-2 and BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are given as follows: + +- If nal\_hrd\_parameters\_present\_flag is equal to 1, BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are given by Equations E-81 and E-82, respectively, using the syntax elements of the hrd\_parameters( ) syntax structure that immediately follows nal\_hrd\_parameters\_present\_flag. +- Otherwise (nal\_hrd\_parameters\_present\_flag is equal to 0), BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are inferred as specified in clause E.2.2 for NAL HRD parameters. + +MaxBR and MaxCPB are specified in Table A-1 in units of cpbBrNalFactor bits/s and cpbBrNalFactor bits, respectively. The bitstream shall satisfy these conditions for at least one value of SchedSelIdx in the range 0 to cpb\_cnt\_minus1, inclusive. + +- i) In bitstreams conforming to the High, Progressive High, or Constrained High profiles, the sum of the NumBytesInNALunit variables for access unit 0 is less than or equal to $384 * ( \text{Max PicSizeInMbs, fR} * \text{MaxMBPS} ) + \text{MaxMBPS} * ( t_r( 0 ) - t_{r,n}( 0 ) ) \div \text{MinCR}$ , where MaxMBPS and MinCR are the values specified in Table A-1 that apply to picture 0 and PicSizeInMbs is the number of macroblocks in picture 0. + +NOTE 3 – Such a limit involving MinCR is not imposed for bitstream conformance to the High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles. + +- j) In bitstreams conforming to the High, Progressive High, or Constrained High profiles, the sum of the NumBytesInNALunit variables for access unit n with $n > 0$ is less than or equal to $384 * \text{MaxMBPS} * ( t_r( n ) - t_r( n - 1 ) ) \div \text{MinCR}$ , where MaxMBPS and MinCR are the values specified in Table A-1 that apply to picture n. + +NOTE 4 – Such a limit involving MinCR is not imposed for bitstream conformance to the High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles. + +- k) In bitstreams conforming to the High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, or CAVLC 4:4:4 Intra profiles, when the level number is less than 6.0 and PicSizeInMbs is greater than 1620, the number of macroblocks in any coded slice shall not exceed MaxFS / 4, where MaxFS is specified in Table A-1. + +**Table A-2 – Specification of cpbBrVclFactor and cpbBrNalFactor** + +| Profile | cpbBrVclFactor | cpbBrNalFactor | +|-----------------------------------------------------------------------|----------------|----------------| +| High
Progressive High
Constrained High | 1 250 | 1 500 | +| High 10
Progressive High 10
High 10 Intra | 3 000 | 3 600 | +| High 4:2:2
High 4:2:2 Intra | 4 000 | 4 800 | +| High 4:4:4 Predictive
High 4:4:4 Intra
CAVLC 4:4:4 Intra | 4 000 | 4 800 | + +**A.3.3.1 Level limits of the Baseline and Constrained Baseline profile** + +Table A-3 specifies limits for each level that are specific to bitstreams conforming to the Baseline or Constrained Baseline profiles. Each entry in Table A-3 indicates, for the level corresponding to the row of the table, the absence or value of a limit that is imposed by the variable corresponding to the column of the table, as follows: + +- If the table entry is marked as "-", no limit is imposed by the value of the variable as a requirement of bitstream conformance to the profile at the specified level. +- Otherwise, the table entry specifies the value of the variable for the associated limit that is imposed as a requirement of bitstream conformance to the profile at the specified level. + +**Table A-3 – Baseline and Constrained Baseline profile level limits** + +| Level number | MaxSubMbRectSize | +|--------------|------------------| +| 1 | 576 | +| 1b | 576 | +| 1.1 | 576 | +| 1.2 | 576 | +| 1.3 | 576 | +| 2 | 576 | +| 2.1 | 576 | +| 2.2 | 576 | +| 3 | 576 | +| 3.1 | - | +| 3.2 | - | +| 4 | - | +| 4.1 | - | +| 4.2 | - | +| 5 | - | +| 5.1 | - | +| 5.2 | - | +| 6.0 | - | +| 6.1 | - | + +| | | +|-----|---| +| 6.2 | - | +|-----|---| + +**A.3.3.2 Level limits of the Main, High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profile** + +Table A-4 specifies limits for each level that are specific to bitstreams conforming to the Main, High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, or CAVLC 4:4:4 Intra profiles. Each entry in Table A-4 indicates, for the level corresponding to the row of the table, the absence or value of a limit that is imposed by the variable corresponding to the column of the table, as follows: + +- If the table entry is marked as "-", no limit is imposed by the value of the variable as a requirement of bitstream conformance to the profile at the specified level. +- Otherwise, the table entry specifies the value of the variable for the associated limit that is imposed as a requirement of bitstream conformance to the profile at the specified level. + +NOTE – The constraints for MinLumaBiPredSize and direct\_8x8\_inference\_flag are not relevant to the Constrained High, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles, as these profiles do not support B slices. + +**Table A-4 – Main, High, Progressive High, Constrained High, High 10, Progressive High 10, High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profile level limits** + +| Level number | SliceRate | MinLumaBiPredSize | direct_8x8_inference_flag | frame_mbs_only_flag | +|--------------|-----------|-------------------|---------------------------|---------------------| +| 1 | - | - | - | 1 | +| 1b | - | - | - | 1 | +| 1.1 | - | - | - | 1 | +| 1.2 | - | - | - | 1 | +| 1.3 | - | - | - | 1 | +| 2 | - | - | - | 1 | +| 2.1 | - | - | - | - | +| 2.2 | - | - | - | - | +| 3 | 22 | - | 1 | - | +| 3.1 | 60 | 8x8 | 1 | - | +| 3.2 | 60 | 8x8 | 1 | - | +| 4 | 60 | 8x8 | 1 | - | +| 4.1 | 24 | 8x8 | 1 | - | +| 4.2 | 24 | 8x8 | 1 | 1 | +| 5 | 24 | 8x8 | 1 | 1 | +| 5.1 | 24 | 8x8 | 1 | 1 | +| 5.2 | 24 | 8x8 | 1 | 1 | +| 6 | 24 | 8x8 | 1 | 1 | +| 6.1 | 24 | 8x8 | 1 | 1 | +| 6.2 | 24 | 8x8 | 1 | 1 | + +### A.3.3.3 Level limits of the Extended profile + +Table A-5 specifies limits for each level that are specific to bitstreams conforming to the Extended profile. Each entry in Table A-5 indicates, for the level corresponding to the row of the table, the absence or value of a limit that is imposed by the variable corresponding to the column of the table, as follows: + +- If the table entry is marked as "-", no limit is imposed by the value of the variable as a requirement of bitstream conformance to the profile at the specified level. +- Otherwise, the table entry specifies the value of the variable for the associated limit that is imposed as a requirement of bitstream conformance to the profile at the specified level. + +**Table A-5 – Extended profile level limits** + +| Level number | MaxSubMbRectSize | MinLumaBiPredSize | frame mbs only flag | +|--------------|------------------|-------------------|---------------------| +| 1 | 576 | - | 1 | +| 1b | 576 | - | 1 | +| 1.1 | 576 | - | 1 | +| 1.2 | 576 | - | 1 | +| 1.3 | 576 | - | 1 | +| 2 | 576 | - | 1 | +| 2.1 | 576 | - | - | +| 2.2 | 576 | - | - | +| 3 | 576 | - | - | +| 3.1 | - | 8x8 | - | +| 3.2 | - | 8x8 | - | +| 4 | - | 8x8 | - | +| 4.1 | - | 8x8 | - | +| 4.2 | - | 8x8 | 1 | +| 5 | - | 8x8 | 1 | +| 5.1 | - | 8x8 | 1 | +| 5.2 | - | 8x8 | 1 | +| 6 | - | 8x8 | 1 | +| 6.1 | - | 8x8 | 1 | +| 6.2 | - | 8x8 | 1 | + +### A.3.4 Effect of level limits on frame rate (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +Table A-6 – Maximum frame rates (frames per second) for some example frame sizes + +| Level: | | | | | 1 | 1b | 1.1 | 1.2 | 1.3 | 2 | 2.1 | +|-------------------------------|------------|-------------|-----------|--------------|---------|---------|---------|-----------|-----------|-----------|-----------| +| Max frame size (macroblocks): | | | | | 99 | 99 | 396 | 396 | 396 | 396 | 792 | +| Max macroblocks/second: | | | | | 1 485 | 1 485 | 3 000 | 6 000 | 11 880 | 11 880 | 19 800 | +| Max frame size (samples): | | | | | 25 344 | 25 344 | 101 376 | 101 376 | 101 376 | 101 376 | 202 752 | +| Max samples/second: | | | | | 380 160 | 380 160 | 768 000 | 1 536 000 | 3 041 280 | 3 041 280 | 5 068 800 | +| Format | Luma Width | Luma Height | MBs Total | Luma Samples | | | | | | | | +| SQCIF | 128 | 96 | 48 | 12 288 | 30.9 | 30.9 | 62.5 | 125.0 | 172.0 | 172.0 | 172.0 | +| QCIF | 176 | 144 | 99 | 25 344 | 15.0 | 15.0 | 30.3 | 60.6 | 120.0 | 120.0 | 172.0 | +| QVGA | 320 | 240 | 300 | 76 800 | - | - | 10.0 | 20.0 | 39.6 | 39.6 | 66.0 | +| 525 SIF | 352 | 240 | 330 | 84 480 | - | - | 9.1 | 18.2 | 36.0 | 36.0 | 60.0 | +| CIF | 352 | 288 | 396 | 101 376 | - | - | 7.6 | 15.2 | 30.0 | 30.0 | 50.0 | +| 525 HHR | 352 | 480 | 660 | 168 960 | - | - | - | - | - | - | 30.0 | +| 625 HHR | 352 | 576 | 792 | 202 752 | - | - | - | - | - | - | 25.0 | +| VGA | 640 | 480 | 1 200 | 307 200 | - | - | - | - | - | - | - | +| 525 4SIF | 704 | 480 | 1 320 | 337 920 | - | - | - | - | - | - | - | +| 525 SD | 720 | 480 | 1 350 | 345 600 | - | - | - | - | - | - | - | +| 4CIF | 704 | 576 | 1 584 | 405 504 | - | - | - | - | - | - | - | +| 625 SD | 720 | 576 | 1 620 | 414 720 | - | - | - | - | - | - | - | +| SVGA | 800 | 600 | 1 900 | 486 400 | - | - | - | - | - | - | - | +| XGA | 1024 | 768 | 3 072 | 786 432 | - | - | - | - | - | - | - | +| 720p HD | 1280 | 720 | 3 600 | 921 600 | - | - | - | - | - | - | - | +| 4VGA | 1280 | 960 | 4 800 | 1 228 800 | - | - | - | - | - | - | - | +| SXGA | 1280 | 1024 | 5 120 | 1 310 720 | - | - | - | - | - | - | - | +| 525 16SIF | 1408 | 960 | 5 280 | 1 351 680 | - | - | - | - | - | - | - | +| 16CIF | 1408 | 1152 | 6 336 | 1 622 016 | - | - | - | - | - | - | - | +| 4SVGA | 1600 | 1200 | 7 500 | 1 920 000 | - | - | - | - | - | - | - | +| 1080 HD | 1920 | 1088 | 8 160 | 2 088 960 | - | - | - | - | - | - | - | +| 2Kx1K | 2048 | 1024 | 8 192 | 2 097 152 | - | - | - | - | - | - | - | +| 2Kx1080 | 2048 | 1088 | 8 704 | 2 228 224 | - | - | - | - | - | - | - | +| 4XGA | 2048 | 1536 | 12 288 | 3 145 728 | - | - | - | - | - | - | - | +| 16VGA | 2560 | 1920 | 19 200 | 4 915 200 | - | - | - | - | - | - | - | +| 3616x1536 (2.35:1) | 3616 | 1536 | 21 696 | 5 554 176 | - | - | - | - | - | - | - | +| 3672x1536 (2.39:1) | 3680 | 1536 | 22 080 | 5 652 480 | - | - | - | - | - | - | - | +| 3840x2160 | 3840 | 2160 | 31 035 | 7 948 800 | - | - | - | - | - | - | - | +| 4Kx2K | 4096 | 2048 | 32 768 | 8 388 608 | - | - | - | - | - | - | - | +| 4096x2160 | 4096 | 2160 | 34 560 | 8 847 360 | - | - | - | - | - | - | - | +| 4096x2304 (16:9) | 4096 | 2304 | 36 864 | 9 437 184 | - | - | - | - | - | - | - | +| 7680x4320 | 7680 | 4320 | 129 600 | 33 177 600 | - | - | - | - | - | - | - | +| 8192x4096 | 8192 | 4096 | 131 072 | 33 554 432 | - | - | - | - | - | - | - | +| 8192x4320 | 8192 | 4320 | 138 240 | 35 389 440 | - | - | - | - | - | - | - | + +**Table A-6 (continued) – Maximum frame rates (frames per second) for some example frame sizes** + +| Level: | | | | | 2.2 | 3 | 3.1 | 3.2 | 4 | 4.1 | 4.2 | +|-------------------------------|------------|-------------|-----------|--------------|-----------|------------|------------|------------|------------|------------|-------------| +| Max frame size (macroblocks): | | | | | 1 620 | 1 620 | 3 600 | 5 120 | 8 192 | 8 192 | 8 704 | +| Max macroblocks/second: | | | | | 20 250 | 40 500 | 108 000 | 216 000 | 245 760 | 245 760 | 522 240 | +| Max frame size (samples): | | | | | 414 720 | 414 720 | 921 600 | 1 310 720 | 2 097 152 | 2 097 152 | 2 228 224 | +| Max samples/second: | | | | | 5 184 000 | 10 368 000 | 27 648 000 | 55 296 000 | 62 914 560 | 62 914 560 | 133 693 440 | +| Format | Luma Width | Luma Height | MBs Total | Luma Samples | | | | | | | | +| SQCIF | 128 | 96 | 48 | 12 288 | 172.0 | 172.0 | 172.0 | 172.0 | 172.0 | 172.0 | 172.0 | +| QCIF | 176 | 144 | 99 | 25 344 | 172.0 | 172.0 | 172.0 | 172.0 | 172.0 | 172.0 | 172.0 | +| QVGA | 320 | 240 | 300 | 76 800 | 67.5 | 135.0 | 172.0 | 172.0 | 172.0 | 172.0 | 172.0 | +| 525 SIF | 352 | 240 | 330 | 84 480 | 61.4 | 122.7 | 172.0 | 172.0 | 172.0 | 172.0 | 172.0 | +| CIF | 352 | 288 | 396 | 101 376 | 51.1 | 102.3 | 172.0 | 172.0 | 172.0 | 172.0 | 172.0 | +| 525 HHR | 352 | 480 | 660 | 168 960 | 30.7 | 61.4 | 163.6 | 172.0 | 172.0 | 172.0 | 172.0 | +| 625 HHR | 352 | 576 | 792 | 202 752 | 25.6 | 51.1 | 136.4 | 172.0 | 172.0 | 172.0 | 172.0 | +| VGA | 640 | 480 | 1 200 | 307 200 | 16.9 | 33.8 | 90.0 | 172.0 | 172.0 | 172.0 | 172.0 | +| 525 4SIF | 704 | 480 | 1 320 | 337 920 | 15.3 | 30.7 | 81.8 | 163.6 | 172.0 | 172.0 | 172.0 | +| 525 SD | 720 | 480 | 1 350 | 345 600 | 15.0 | 30.0 | 80.0 | 160.0 | 172.0 | 172.0 | 172.0 | +| 4CIF | 704 | 576 | 1 584 | 405 504 | 12.8 | 25.6 | 68.2 | 136.4 | 155.2 | 155.2 | 172.0 | +| 625 SD | 720 | 576 | 1 620 | 414 720 | 12.5 | 25.0 | 66.7 | 133.3 | 151.7 | 151.7 | 172.0 | +| SVGA | 800 | 600 | 1 900 | 486 400 | - | - | 56.8 | 113.7 | 129.3 | 129.3 | 172.0 | +| XGA | 1024 | 768 | 3 072 | 786 432 | - | - | 35.2 | 70.3 | 80.0 | 80.0 | 170.0 | +| 720p HD | 1280 | 720 | 3 600 | 921 600 | - | - | 30.0 | 60.0 | 68.3 | 68.3 | 145.1 | +| 4VGA | 1280 | 960 | 4 800 | 1 228 800 | - | - | - | 45.0 | 51.2 | 51.2 | 108.8 | +| SXGA | 1280 | 1024 | 5 120 | 1 310 720 | - | - | - | 42.2 | 48.0 | 48.0 | 102.0 | +| 525 16SIF | 1408 | 960 | 5 280 | 1 351 680 | - | - | - | - | 46.5 | 46.5 | 98.9 | +| 16CIF | 1408 | 1152 | 6 336 | 1 622 016 | - | - | - | - | 38.8 | 38.8 | 82.4 | +| 4SVGA | 1600 | 1200 | 7 500 | 1 920 000 | - | - | - | - | 32.8 | 32.8 | 69.6 | +| 1080 HD | 1920 | 1088 | 8 160 | 2 088 960 | - | - | - | - | 30.1 | 30.1 | 64.0 | +| 2Kx1K | 2048 | 1024 | 8 192 | 2 097 152 | - | - | - | - | 30.0 | 30.0 | 63.8 | +| 2Kx1080 | 2048 | 1088 | 8 704 | 2 228 224 | - | - | - | - | - | - | 60.0 | +| 4XGA | 2048 | 1536 | 12 288 | 3 145 728 | - | - | - | - | - | - | - | +| 16VGA | 2560 | 1920 | 19 200 | 4 915 200 | - | - | - | - | - | - | - | +| 3616x1536 (2.35:1) | 3616 | 1536 | 21 696 | 5 554 176 | - | - | - | - | - | - | - | +| 3672x1536 (2.39:1) | 3680 | 1536 | 22 080 | 5 652 480 | - | - | - | - | - | - | - | +| 3840x2160 | 3840 | 2160 | 31 035 | 7 948 800 | - | - | - | - | - | - | - | +| 4Kx2K | 4096 | 2048 | 32 768 | 8 388 608 | - | - | - | - | - | - | - | +| 4096x2160 | 4096 | 2160 | 34 560 | 8 847 360 | - | - | - | - | - | - | - | +| 4096x2304 (16:9) | 4096 | 2304 | 36 864 | 9 437 184 | - | - | - | - | - | - | - | +| 7680x4320 | 7680 | 4320 | 129 600 | 33 177 600 | - | - | - | - | - | - | - | +| 8192x4096 | 8192 | 4096 | 131 072 | 33 554 432 | - | - | - | - | - | - | - | +| 8192x4320 | 8192 | 4320 | 138 240 | 35 389 440 | - | - | - | - | - | - | - | + +**Table A-6 (concluded) – Maximum frame rates (frames per second) for some example frame sizes** + +| Level: | | | | | 5 | 5.1 | 5.2 | 6 | 6.1 | 6.2 | +|-------------------------------|------------|-------------|-----------|--------------|-------------|-------------|-------------|---------------|---------------|---------------| +| Max frame size (macroblocks): | | | | | 22 080 | 36 864 | 36 864 | 139 264 | 139 264 | 139 264 | +| Max macroblocks/second: | | | | | 589 824 | 983 040 | 2 073 600 | 4 177 920 | 8 355 840 | 16 711 680 | +| Max frame size (samples): | | | | | 5 652 480 | 9 437 184 | 9 437 184 | 35 651 584 | 35 651 584 | 35 651 584 | +| Max samples/second: | | | | | 150 994 944 | 251 658 240 | 530 841 600 | 1 069 547 520 | 2 139 095 040 | 4 278 190 080 | +| Format | Luma Width | Luma Height | MBs Total | Luma Samples | | | | | | | +| SQCIF | 128 | 96 | 48 | 12 288 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| QCIF | 176 | 144 | 99 | 25 344 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| QVGA | 320 | 240 | 300 | 76 800 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 525 SIF | 352 | 240 | 330 | 84 480 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| CIF | 352 | 288 | 396 | 101 376 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 525 HHR | 352 | 480 | 660 | 168 960 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 625 HHR | 352 | 576 | 792 | 202 752 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| VGA | 640 | 480 | 1 200 | 307 200 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 525 4SIF | 704 | 480 | 1 320 | 337 920 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 525 SD | 720 | 480 | 1 350 | 345 600 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 4CIF | 704 | 576 | 1 584 | 405 504 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 625 SD | 720 | 576 | 1 620 | 414 720 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| SVGA | 800 | 600 | 1 900 | 486 400 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| XGA | 1024 | 768 | 3 072 | 786 432 | 172.0 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 720p HD | 1280 | 720 | 3 600 | 921 600 | 163.8 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 4VGA | 1280 | 960 | 4 800 | 1 228 800 | 122.9 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| SXGA | 1280 | 1024 | 5 120 | 1 310 720 | 115.2 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 525 16SIF | 1408 | 960 | 5 280 | 1 351 680 | 111.7 | 172.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 16CIF | 1408 | 1152 | 6 336 | 1 622 016 | 93.1 | 155.2 | 172.0 | 300.0 | 300.0 | 300.0 | +| 4SVGA | 1600 | 1200 | 7 500 | 1 920 000 | 78.6 | 131.1 | 172.0 | 300.0 | 300.0 | 300.0 | +| 1080 HD | 1920 | 1088 | 8 160 | 2 088 960 | 72.3 | 120.5 | 172.0 | 300.0 | 300.0 | 300.0 | +| 2Kx1K | 2048 | 1024 | 8 192 | 2 097 152 | 72.0 | 120.0 | 172.0 | 300.0 | 300.0 | 300.0 | +| 2Kx1080 | 2048 | 1088 | 8 704 | 2 228 224 | 67.8 | 112.9 | 172.0 | 300.0 | 300.0 | 300.0 | +| 4XGA | 2048 | 1536 | 12 288 | 3 145 728 | 48.0 | 80.0 | 168.8 | 300.0 | 300.0 | 300.0 | +| 16VGA | 2560 | 1920 | 19 200 | 4 915 200 | 30.7 | 51.2 | 108.0 | 217.6 | 300.0 | 300.0 | +| 3616x1536 (2.35:1) | 3616 | 1536 | 21 696 | 5 554 176 | 27.2 | 45.3 | 95.6 | 192.6 | 300.0 | 300.0 | +| 3672x1536 (2.39:1) | 3680 | 1536 | 22 080 | 5 652 480 | 26.7 | 44.5 | 93.9 | 189.2 | 300.0 | 300.0 | +| 3840x2160 | 3840 | 2160 | 31 035 | 7 948 800 | - | 30.3 | 64.0 | 128.9 | 257.9 | 300.0 | +| 4Kx2K | 4096 | 2048 | 32 768 | 8 388 608 | - | 30.0 | 63.3 | 127.5 | 255.0 | 300.0 | +| 4096x2160 | 4096 | 2160 | 34 560 | 8 847 360 | - | 28.4 | 60.0 | 120.9 | 241.8 | 300.0 | +| 4096x2304 (16:9) | 4096 | 2304 | 36 864 | 9 437 184 | - | 26.7 | 56.3 | 113.3 | 226.7 | 300.0 | +| 7680x4320 | 7680 | 4320 | 129 600 | 33 177 600 | - | - | - | 32.2 | 64.5 | 128.9 | +| 8192x4096 | 8192 | 4096 | 131 072 | 33 554 432 | - | - | - | 31.9 | 63.8 | 127.5 | +| 8192x4320 | 8192 | 4320 | 138 240 | 35 389 440 | - | - | - | 30.2 | 60.4 | 120.9 | + +The following should be noted: + +- This Recommendation | International Standard is a variable-frame-size specification. The specific frame sizes in Table A-6 are illustrative examples only. +- As used in Table A-6, "525" refers to typical use for environments using 525 analogue scan lines (of which approximately 480 lines contain the visible picture region), and "625" refers to environments using 625 analogue scan lines (of which approximately 576 lines contain the visible picture region). +- XGA is also known as (aka) XVGA, 4SVGA aka UXGA, 16XGA aka 4Kx3K, CIF aka 625 SIF, 625 HHR aka 2CIF aka half 625 D-1, aka half 625 ITU-R BT.601, 525 SD aka 525 D-1 aka 525 ITU-R BT.601, 625 SD aka 625 D-1 aka 625 ITU-R BT.601. +- The given maximum frame rate values that have a zero to the right of the decimal point are exact. Others have been rounded to the nearest 0.1 frames per second, i.e., the precise maximum frame rates may be higher or lower within a margin of plus or minus 0.05 frames per second. For example, for Level 4, the maximum frame rate for 720p HD has been rounded up to 68.3 from a value of 68.2666..., and the maximum frame rate for 1080 HD has been rounded down to 30.1 from a value of 30.1176.... +- Frame rates given are correct for progressive scan modes. The frame rates are also correct for interlaced video coding for the cases of frame height divisible by 32. + +### A.3.5 Effect of level limits on maximum DPB size in units of frames (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +Table A-7 – Maximum DPB size (frames) for some example frame sizes + +| Level: | | | | 1 | 1b | 1.1 | 1.2 | 1.3 | 2 | 2.1 | 2.2 | +|-------------------------------|------------|-------------|-----------|-----|-----|-----|-------|-------|-------|-------|-------| +| Max frame size (macroblocks): | | | | 99 | 99 | 396 | 396 | 396 | 396 | 792 | 1 620 | +| Max DPB size (macroblocks): | | | | 396 | 396 | 900 | 2 376 | 2 376 | 2 376 | 4 752 | 8 100 | +| Format | Luma Width | Luma Height | MBs Total | | | | | | | | | +| QCIF | 128 | 96 | 48 | 8 | 8 | 16 | 16 | 16 | 16 | 16 | 16 | +| QCIF | 176 | 144 | 99 | 4 | 4 | 9 | 16 | 16 | 16 | 16 | 16 | +| QVGA | 320 | 240 | 300 | - | - | 3 | 7 | 7 | 7 | 15 | 16 | +| 525 SIF | 352 | 240 | 330 | - | - | 2 | 7 | 7 | 7 | 14 | 16 | +| CIF | 352 | 288 | 396 | - | - | 2 | 6 | 6 | 6 | 12 | 16 | +| 525 HHR | 352 | 480 | 660 | - | - | - | - | - | - | 7 | 12 | +| 625 HHR | 352 | 576 | 792 | - | - | - | - | - | - | 6 | 10 | +| VGA | 640 | 480 | 1 200 | - | - | - | - | - | - | - | 6 | +| 525 4SIF | 704 | 480 | 1 320 | - | - | - | - | - | - | - | 6 | +| 525 SD | 720 | 480 | 1 350 | - | - | - | - | - | - | - | 6 | +| 4CIF | 704 | 576 | 1 584 | - | - | - | - | - | - | - | 5 | +| 625 SD | 720 | 576 | 1 620 | - | - | - | - | - | - | - | 5 | +| SVGA | 800 | 600 | 1 900 | - | - | - | - | - | - | - | - | +| XGA | 1024 | 768 | 3 072 | - | - | - | - | - | - | - | - | +| 720p HD | 1280 | 720 | 3 600 | - | - | - | - | - | - | - | - | +| 4VGA | 1280 | 960 | 4 800 | - | - | - | - | - | - | - | - | +| SXGA | 1280 | 1024 | 5 120 | - | - | - | - | - | - | - | - | +| 525 16SIF | 1408 | 960 | 5 280 | - | - | - | - | - | - | - | - | +| 16CIF | 1408 | 1152 | 6 336 | - | - | - | - | - | - | - | - | +| 4SVGA | 1600 | 1200 | 7 500 | - | - | - | - | - | - | - | - | +| 1080 HD | 1920 | 1088 | 8 160 | - | - | - | - | - | - | - | - | +| 2Kx1K | 2048 | 1024 | 8 192 | - | - | - | - | - | - | - | - | +| 2Kx1080 | 2048 | 1088 | 8 704 | - | - | - | - | - | - | - | - | +| 4XGA | 2048 | 1536 | 12 288 | - | - | - | - | - | - | - | - | +| 16VGA | 2560 | 1920 | 19 200 | - | - | - | - | - | - | - | - | +| 3616x1536 (2.35:1) | 3616 | 1536 | 21 696 | - | - | - | - | - | - | - | - | +| 3672x1536 (2.39:1) | 3680 | 1536 | 22 080 | - | - | - | - | - | - | - | - | +| 3840x2160 | 3840 | 2160 | 31 035 | - | - | - | - | - | - | - | - | +| 4Kx2K | 4096 | 2048 | 32 768 | - | - | - | - | - | - | - | - | +| 4096x2160 | 4096 | 2160 | 34 560 | - | - | - | - | - | - | - | - | +| 4096x2304 (16:9) | 4096 | 2304 | 36 864 | - | - | - | - | - | - | - | - | +| 7680x4320 | 7680 | 4320 | 129 600 | - | - | - | - | - | - | - | - | +| 8192x4096 | 8192 | 4096 | 131 072 | - | - | - | - | - | - | - | - | +| 8192x4320 | 8192 | 4320 | 138 240 | - | - | - | - | - | - | - | - | + +**Table A-7 (continued) – Maximum DPB size (frames) for some example frame sizes** + +| Level: | | | | 3 | 3.1 | 3.2 | 4 | 4.1 | 4.2 | +|-------------------------------|------------|-------------|-----------|-------|--------|--------|--------|--------|--------| +| Max frame size (macroblocks): | | | | 1 620 | 3 600 | 5 120 | 8 192 | 8 192 | 8 704 | +| Max DPB size (macroblocks): | | | | 8 100 | 18 000 | 20 480 | 32 768 | 32 768 | 34 816 | +| Format | Luma Width | Luma Height | MBs Total | | | | | | | +| SQCIF | 128 | 96 | 48 | 16 | 16 | 16 | 16 | 16 | 16 | +| QCIF | 176 | 144 | 99 | 16 | 16 | 16 | 16 | 16 | 16 | +| QVGA | 320 | 240 | 300 | 16 | 16 | 16 | 16 | 16 | 16 | +| 525 SIF | 352 | 240 | 330 | 16 | 16 | 16 | 16 | 16 | 16 | +| CIF | 352 | 288 | 396 | 16 | 16 | 16 | 16 | 16 | 16 | +| 525 HHR | 352 | 480 | 660 | 12 | 16 | 16 | 16 | 16 | 16 | +| 625 HHR | 352 | 576 | 792 | 10 | 16 | 16 | 16 | 16 | 16 | +| VGA | 640 | 480 | 1 200 | 6 | 15 | 16 | 16 | 16 | 16 | +| 525 4SIF | 704 | 480 | 1 320 | 6 | 13 | 15 | 16 | 16 | 16 | +| 525 SD | 720 | 480 | 1 350 | 6 | 13 | 15 | 16 | 16 | 16 | +| 4CIF | 704 | 576 | 1 584 | 5 | 11 | 12 | 16 | 16 | 16 | +| 625 SD | 720 | 576 | 1 620 | 5 | 11 | 12 | 16 | 16 | 16 | +| SVGA | 800 | 600 | 1 900 | - | 9 | 10 | 16 | 16 | 16 | +| XGA | 1024 | 768 | 3 072 | - | 5 | 6 | 10 | 10 | 11 | +| 720p HD | 1280 | 720 | 3 600 | - | 5 | 5 | 9 | 9 | 9 | +| 4VGA | 1280 | 960 | 4 800 | - | - | 4 | 6 | 6 | 7 | +| SXGA | 1280 | 1024 | 5 120 | - | - | 4 | 6 | 6 | 6 | +| 525 16SIF | 1408 | 960 | 5 280 | - | - | - | 6 | 6 | 6 | +| 16CIF | 1408 | 1152 | 6 336 | - | - | - | 5 | 5 | 5 | +| 4SVGA | 1600 | 1200 | 7 500 | - | - | - | 4 | 4 | 4 | +| 1080 HD | 1920 | 1088 | 8 160 | - | - | - | 4 | 4 | 4 | +| 2Kx1K | 2048 | 1024 | 8 192 | - | - | - | 4 | 4 | 4 | +| 2Kx1080 | 2048 | 1088 | 8 704 | - | - | - | - | - | 4 | +| 4XGA | 2048 | 1536 | 12 288 | - | - | - | - | - | - | +| 16VGA | 2560 | 1920 | 19 200 | - | - | - | - | - | - | +| 3616x1536 (2.35:1) | 3616 | 1536 | 21 696 | - | - | - | - | - | - | +| 3672x1536 (2.39:1) | 3680 | 1536 | 22 080 | - | - | - | - | - | - | +| 3840x2160 | 3840 | 2160 | 31 035 | - | - | - | - | - | - | +| 4Kx2K | 4096 | 2048 | 32 768 | - | - | - | - | - | - | +| 4096x2160 | 4096 | 2160 | 34 560 | - | - | - | - | - | - | +| 4096x2304 (16:9) | 4096 | 2304 | 36 864 | - | - | - | - | - | - | +| 7680x4320 | 7680 | 4320 | 129 600 | - | - | - | - | - | - | +| 8192x4096 | 8192 | 4096 | 131 072 | - | - | - | - | - | - | +| 8192x4320 | 8192 | 4320 | 138 240 | - | - | - | - | - | - | + +**Table A-7 (concluded) – Maximum DPB size (frames) for some example frame sizes** + +| Level: | | | | 5 | 5.1 | 5.2 | 6 | 6.1 | 6.2 | +|-------------------------------|------------|-------------|-----------|---------|---------|---------|---------|---------|---------| +| Max frame size (macroblocks): | | | | 22 080 | 36 864 | 36 864 | 129 600 | 131 072 | 138 240 | +| Max DPB size (macroblocks): | | | | 110 400 | 184 320 | 184 320 | 696 320 | 696 320 | 696 320 | +| Format | Luma Width | Luma Height | MBs Total | | | | | | | +| SQCIF | 128 | 96 | 48 | 16 | 16 | 16 | 16 | 16 | 16 | +| QCIF | 176 | 144 | 99 | 16 | 16 | 16 | 16 | 16 | 16 | +| QVGA | 320 | 240 | 300 | 16 | 16 | 16 | 16 | 16 | 16 | +| 525 SIF | 352 | 240 | 330 | 16 | 16 | 16 | 16 | 16 | 16 | +| CIF | 352 | 288 | 396 | 16 | 16 | 16 | 16 | 16 | 16 | +| 525 HHR | 352 | 480 | 660 | 16 | 16 | 16 | 16 | 16 | 16 | +| 625 HHR | 352 | 576 | 792 | 16 | 16 | 16 | 16 | 16 | 16 | +| VGA | 640 | 480 | 1 200 | 16 | 16 | 16 | 16 | 16 | 16 | +| 525 4SIF | 704 | 480 | 1 320 | 16 | 16 | 16 | 16 | 16 | 16 | +| 525 SD | 720 | 480 | 1 350 | 16 | 16 | 16 | 16 | 16 | 16 | +| 4CIF | 704 | 576 | 1 584 | 16 | 16 | 16 | 16 | 16 | 16 | +| 625 SD | 720 | 576 | 1 620 | 16 | 16 | 16 | 16 | 16 | 16 | +| SVGA | 800 | 600 | 1 900 | 16 | 16 | 16 | 16 | 16 | 16 | +| XGA | 1024 | 768 | 3 072 | 16 | 16 | 16 | 16 | 16 | 16 | +| 720p HD | 1280 | 720 | 3 600 | 16 | 16 | 16 | 16 | 16 | 16 | +| 4VGA | 1280 | 960 | 4 800 | 16 | 16 | 16 | 16 | 16 | 16 | +| SXGA | 1280 | 1024 | 5 120 | 16 | 16 | 16 | 16 | 16 | 16 | +| 525 16SIF | 1408 | 960 | 5 280 | 16 | 16 | 16 | 16 | 16 | 16 | +| 16CIF | 1408 | 1152 | 6 336 | 16 | 16 | 16 | 16 | 16 | 16 | +| 4SVGA | 1600 | 1200 | 7 500 | 14 | 16 | 16 | 16 | 16 | 16 | +| 1080 HD | 1920 | 1088 | 8 160 | 13 | 16 | 16 | 16 | 16 | 16 | +| 2Kx1K | 2048 | 1024 | 8 192 | 13 | 16 | 16 | 16 | 16 | 16 | +| 2Kx1080 | 2048 | 1088 | 8 704 | 12 | 16 | 16 | 16 | 16 | 16 | +| 4XGA | 2048 | 1536 | 12 288 | 8 | 15 | 15 | 16 | 16 | 16 | +| 16VGA | 2560 | 1920 | 19 200 | 5 | 9 | 9 | 16 | 16 | 16 | +| 3616x1536 (2.35:1) | 3616 | 1536 | 21 696 | 5 | 8 | 8 | 16 | 16 | 16 | +| 3672x1536 (2.39:1) | 3680 | 1536 | 22 080 | 5 | 8 | 8 | 16 | 16 | 16 | +| 3840x2160 | 3840 | 2160 | 31 035 | - | 5 | 5 | 16 | 16 | 16 | +| 4Kx2K | 4096 | 2048 | 32 768 | - | 5 | 5 | 16 | 16 | 16 | +| 4096x2160 | 4096 | 2160 | 34 560 | - | 5 | 5 | 16 | 16 | 16 | +| 4096x2304 (16:9) | 4096 | 2304 | 36 864 | - | 5 | 5 | 16 | 16 | 16 | +| 7680x4320 | 7680 | 4320 | 129 600 | - | - | - | 5 | 5 | 5 | +| 8192x4096 | 8192 | 4096 | 131 072 | - | - | - | 5 | 5 | 5 | +| 8192x4320 | 8192 | 4320 | 138 240 | - | - | - | 5 | 5 | 5 | + +The following should be noted: + +- As used in Table A-7, "525" refers to typical use for environments using 525 analogue scan lines (of which approximately 480 lines contain the visible picture region), and "625" refers to environments using 625 analogue scan lines (of which approximately 576 lines contain the visible picture region). +- XGA is also known as (aka) XVGA, 4SVGA aka UXGA, 16XGA aka 4Kx3K, CIF aka 625 SIF, 625 HHR aka 2CIF aka half 625 D-1, aka half 625 ITU-R BT.601, 525 SD aka 525 D-1 aka 525 ITU-R BT.601, 625 SD aka 625 D-1 aka 625 ITU-R BT.601. + +## Annex B + +### Byte stream format + +(This annex forms an integral part of this Recommendation | International Standard.) + +This annex specifies syntax and semantics of a byte stream format specified for use by applications that deliver some or all of the NAL unit stream as an ordered stream of bytes or bits within which the locations of NAL unit boundaries need to be identifiable from patterns in the data, such as Rec. ITU-T H.222.0 | ISO/IEC 13818-1 systems or Rec. ITU-T H.320 systems. For bit-oriented delivery, the bit order for the byte stream format is specified to start with the MSB of the first byte, proceed to the LSB of the first byte, followed by the MSB of the second byte, etc. + +The byte stream format consists of a sequence of byte stream NAL unit syntax structures. Each byte stream NAL unit syntax structure contains one start code prefix followed by one `nal_unit( NumBytesInNALUnit )` syntax structure. It may (and under some circumstances, it shall) also contain an additional `zero_byte` syntax element. It may also contain one or more additional `trailing_zero_8bits` syntax elements. When it is the first byte stream NAL unit in the bitstream, it may also contain one or more additional `leading_zero_8bits` syntax elements. + +#### B.1 Byte stream NAL unit syntax and semantics + +##### B.1.1 Byte stream NAL unit syntax + +| byte_stream_nal_unit( NumBytesInNALUnit ) { | C | Descriptor | +|-----------------------------------------------------------------------------------------------------------|---|------------| +| while( next_bits( 24 ) != 0x000001 &&
next_bits( 32 ) != 0x00000001 ) | | | +| leading_zero_8bits /* equal to 0x00 */ | | f(8) | +| if( next_bits( 24 ) != 0x000001 ) | | | +| zero_byte /* equal to 0x00 */ | | f(8) | +| start_code_prefix_one_3bytes /* equal to 0x000001 */ | | f(24) | +| nal_unit( NumBytesInNALUnit ) | | | +| while( more_data_in_byte_stream() &&
next_bits( 24 ) != 0x000001 &&
next_bits( 32 ) != 0x00000001 ) | | | +| trailing_zero_8bits /* equal to 0x00 */ | | f(8) | +| } | | | + +##### B.1.2 Byte stream NAL unit semantics + +The order of byte stream NAL units in the byte stream shall follow the decoding order of the NAL units contained in the byte stream NAL units (see clause 7.4.1.2). The content of each byte stream NAL unit is associated with the same access unit as the NAL unit contained in the byte stream NAL unit (see clause 7.4.1.2.3). + +**leading\_zero\_8bits** is a byte equal to 0x00. + +NOTE – The `leading_zero_8bits` syntax element can only be present in the first byte stream NAL unit of the bitstream, because (as shown in the syntax diagram of clause B.1.1) any bytes equal to 0x00 that follow a NAL unit syntax structure and precede the four-byte sequence 0x00000001 (which is to be interpreted as a `zero_byte` followed by a `start_code_prefix_one_3bytes`) will be considered to be `trailing_zero_8bits` syntax elements that are part of the preceding byte stream NAL unit. + +**zero\_byte** is a single byte equal to 0x00. + +When any of the following conditions are true, the `zero_byte` syntax element shall be present: + +- the `nal_unit_type` within the `nal_unit( )` is equal to 7 (sequence parameter set) or 8 (picture parameter set), +- the byte stream NAL unit syntax structure contains the first NAL unit of an access unit in decoding order, as specified in clause 7.4.1.2.3. + +**start\_code\_prefix\_one\_3bytes** is a fixed-value sequence of 3 bytes equal to 0x000001. This syntax element is called a start code prefix. + +**trailing\_zero\_8bits** is a byte equal to 0x00. + +## B.2 Byte stream NAL unit decoding process + +Input to this process consists of an ordered stream of bytes consisting of a sequence of byte stream NAL unit syntax structures. + +Output of this process consists of a sequence of NAL unit syntax structures. + +At the beginning of the decoding process, the decoder initializes its current position in the byte stream to the beginning of the byte stream. It then extracts and discards each `leading_zero_8bits` syntax element (if present), moving the current position in the byte stream forward one byte at a time, until the current position in the byte stream is such that the next four bytes in the bitstream form the four-byte sequence 0x00000001. + +The decoder then performs the following step-wise process repeatedly to extract and decode each NAL unit syntax structure in the byte stream until the end of the byte stream has been encountered (as determined by unspecified means) and the last NAL unit in the byte stream has been decoded: + +1. When the next four bytes in the bitstream form the four-byte sequence 0x00000001, the next byte in the byte stream (which is a `zero_byte` syntax element) is extracted and discarded and the current position in the byte stream is set equal to the position of the byte following this discarded byte. +2. The next three-byte sequence in the byte stream (which is a `start_code_prefix_one_3bytes`) is extracted and discarded and the current position in the byte stream is set equal to the position of the byte following this three-byte sequence. +3. `NumBytesInNALUnit` is set equal to the number of bytes starting with the byte at the current position in the byte stream up to and including the last byte that precedes the location of any of the following: + - A subsequent byte-aligned three-byte sequence equal to 0x000000, + - A subsequent byte-aligned three-byte sequence equal to 0x000001, + - The end of the byte stream, as determined by unspecified means. +4. `NumBytesInNALUnit` bytes are removed from the bitstream and the current position in the byte stream is advanced by `NumBytesInNALUnit` bytes. This sequence of bytes is `nal_unit( NumBytesInNALUnit )` and is decoded using the NAL unit decoding process. +5. When the current position in the byte stream is not at the end of the byte stream (as determined by unspecified means) and the next bytes in the byte stream do not start with a three-byte sequence equal to 0x000001 and the next bytes in the byte stream do not start with a four byte sequence equal to 0x00000001, the decoder extracts and discards each `trailing_zero_8bits` syntax element, moving the current position in the byte stream forward one byte at a time, until the current position in the byte stream is such that the next bytes in the byte stream form the four-byte sequence 0x00000001 or the end of the byte stream has been encountered (as determined by unspecified means). + +## B.3 Decoder byte-alignment recovery (informative) + +This clause does not form an integral part of this Recommendation | International Standard. + +Many applications provide data to a decoder in a manner that is inherently byte aligned, and thus have no need for the bit-oriented byte alignment detection procedure described in this clause. + +A decoder is said to have byte-alignment with a bitstream when the decoder is able to determine whether or not the positions of data in the bitstream are byte-aligned. When a decoder does not have byte alignment with the encoder's byte stream, the decoder may examine the incoming bitstream for the binary pattern '00000000 00000000 00000000 00000001' (31 consecutive bits equal to 0 followed by a bit equal to 1). The bit immediately following this pattern is the first bit of an aligned byte following a start code prefix. Upon detecting this pattern, the decoder will be byte aligned with the encoder and positioned at the start of a NAL unit in the byte stream. + +Once byte aligned with the encoder, the decoder can examine the incoming byte stream for subsequent three-byte sequences 0x000001 and 0x000003. + +When the three-byte sequence 0x000001 is detected, this is a start code prefix. + +When the three-byte sequence 0x000003 is detected, the third byte (0x03) is an `emulation_prevention_three_byte` to be discarded as specified in clause 7.4.1. + +When an error in the bitstream syntax is detected (e.g., a non-zero value of the `forbidden_zero_bit` or one of the three-byte or four-byte sequences that are prohibited in clause 7.4.1), the decoder may consider the detected condition as an indication that byte alignment may have been lost and may discard all bitstream data until the detection of byte alignment at a later position in the bitstream as described in this clause. + +## Annex C + +### Hypothetical reference decoder + +(This annex forms an integral part of this Recommendation | International Standard.) + +This annex specifies the hypothetical reference decoder (HRD) and its use to check bitstream and decoder conformance. + +Two types of bitstreams are subject to HRD conformance checking for this Recommendation | International Standard. The first such type of bitstream, called Type I bitstream, is a NAL unit stream containing only the VCL NAL units and filler data NAL units for all access units in the bitstream. The second type of bitstream, called a Type II bitstream, contains, in addition to the VCL NAL units and filler data NAL units for all access units in the bitstream, at least one of the following: + +- additional non-VCL NAL units other than filler data NAL units, +- all leading\_zero\_8bits, zero\_byte, start\_code\_prefix\_one\_3bytes, and trailing\_zero\_8bits syntax elements that form a byte stream from the NAL unit stream (as specified in Annex B). + +Figure C-1 shows the types of bitstream conformance points checked by the HRD. + +![Diagram illustrating the structure of byte streams and NAL unit streams for HRD conformance checks. It shows three main paths: Type I HRD conformance point (VCL NAL units and Filter data NAL units), Type II HRD conformance point when not using byte stream format (VCL NAL units, Filter data NAL units, and Non-VCL NAL units other than filler data NAL units), and Type II HRD conformance point when using byte stream format (VCL NAL units, Filter data NAL units, and Non-VCL NAL units other than filler data NAL units via Byte stream format encapsulation).](212f85622719de88fe92d2a398eb778f_img.jpg) + +The diagram illustrates the structure of byte streams and NAL unit streams for HRD conformance checks. It shows three main paths: + +- Type I HRD conformance point:** This path is for bitstreams containing only VCL NAL units and Filter data NAL units. Arrows from these two types of NAL units point directly to a box labeled "Type I HRD conformance point". +- Type II HRD conformance point when not using byte stream format:** This path is for bitstreams containing VCL NAL units, Filter data NAL units, and Non-VCL NAL units other than filler data NAL units. Arrows from all three types of NAL units point to a box labeled "Type II HRD conformance point when not using byte stream format". +- Type II HRD conformance point when using byte stream format:** This path is for bitstreams containing VCL NAL units, Filter data NAL units, and Non-VCL NAL units other than filler data NAL units. The first two types of NAL units point to a box labeled "Byte stream format encapsulation (see Annex B)". The Non-VCL NAL units other than filler data NAL units point to a box labeled "Type II HRD conformance point when using byte stream format". An arrow from the encapsulation box also points to this same box. + +H.264(09)\_FC-1 + +Diagram illustrating the structure of byte streams and NAL unit streams for HRD conformance checks. It shows three main paths: Type I HRD conformance point (VCL NAL units and Filter data NAL units), Type II HRD conformance point when not using byte stream format (VCL NAL units, Filter data NAL units, and Non-VCL NAL units other than filler data NAL units), and Type II HRD conformance point when using byte stream format (VCL NAL units, Filter data NAL units, and Non-VCL NAL units other than filler data NAL units via Byte stream format encapsulation). + +**Figure C-1 – Structure of byte streams and NAL unit streams for HRD conformance checks** + +The syntax elements of non-VCL NAL units (or their default values for some of the syntax elements), required for the HRD, are specified in the semantics subclauses of clause 7, Annexes D and E, and clauses F.7, F.13, F.14, G.7, G.13, G.14, H.7, H.13, and H.14. + +Two types of HRD parameter sets (NAL HRD parameters and VCL HRD parameters) are used. The HRD parameter sets are signalled as follows: + +- When the coded video sequence conforms to one or more of the profiles specified in Annex A and the decoding process specified in clauses 2 to 9 is applied, the HRD parameter sets are signalled through video usability information as specified in clauses E.1 and E.2, which is part of the sequence parameter set syntax structure. +- When the coded video sequence conforms to one or more of the profiles specified in Annex F and the decoding process specified in Annex F is applied, the HRD parameter sets are signalled through the SVC video usability information extension as specified in clauses F.14.1 and F.14.2, which is part of the subset sequence parameter set syntax structure. + +NOTE 1 – For coded video sequences that conform to both, one or more of the profiles specified in Annex A and one or more of the profiles specified in Annex F, the signalling of the applicable HRD parameter sets is depending on whether the decoding process specified in clauses 2 to 9 or the decoding process specified in Annex F is applied. + +- When the coded video sequence conforms to one or more of the profiles specified in Annex G and the decoding process specified in Annex G is applied, the HRD parameter sets are signalled through the MVC video usability information extension as specified in clauses G.14.1 and G.14.2, which is part of the subset sequence parameter set syntax structure. + +NOTE 2 – For coded video sequences that conform to both, one or more of the profiles specified in Annex A and one or more of the profiles specified in Annex G, the signalling of the applicable HRD parameter sets is depending on whether the decoding process specified in clauses 2 to 9 or the decoding process specified in Annex G is applied. + +- When the coded video sequence conforms to one or more of the profiles specified in Annex H and the decoding process specified in Annex H is applied, the HRD parameter sets are signalled through the MVC video usability information extension as specified in clause H.14, which is part of the subset sequence parameter set syntax structure. + +NOTE 3 – For coded video sequences that conform to one or more of the profiles specified in Annex A, one or more of the profiles specified in Annex G and one or more of the profiles specified in Annex H, the signalling of the applicable HRD parameter sets is dependent on whether the decoding process specified in clauses 2-9, the decoding process specified in Annex G, or the decoding process specified in Annex H is applied. + +All sequence parameter sets and picture parameter sets referred to in the VCL NAL units, and corresponding buffering period and picture timing SEI messages shall be conveyed to the HRD, in a timely manner, either in the bitstream (by non-VCL NAL units), or by other means not specified in this Recommendation | International Standard. + +In Annexes C, D, and E, and clauses F.12, F.13, F.14, G.12, G.13, G.14, H.13 and H.14 the specification for "presence" of non-VCL NAL units is also satisfied when those NAL units (or just some of them) are conveyed to decoders (or to the HRD) by other means not specified by this Recommendation | International Standard. For the purpose of counting bits, only the appropriate bits that are actually present in the bitstream are counted. + +NOTE 4 – As an example, synchronization of a non-VCL NAL unit, conveyed by means other than presence in the bitstream, with the NAL units that are present in the bitstream, can be achieved by indicating two points in the bitstream, between which the non-VCL NAL unit would have been present in the bitstream, had the encoder decided to convey it in the bitstream. + +When the content of a non-VCL NAL unit is conveyed for the application by some means other than presence within the bitstream, the representation of the content of the non-VCL NAL unit is not required to use the same syntax specified in this annex. + +NOTE 5 – When HRD information is contained within the bitstream, it is possible to verify the conformance of a bitstream to the requirements of this clause based solely on information contained in the bitstream. When the HRD information is not present in the bitstream, as is the case for all "stand-alone" Type I bitstreams, conformance can only be verified when the HRD data is supplied by some other means not specified in this Recommendation | International Standard. + +The HRD contains a coded picture buffer (CPB), an instantaneous decoding process, a decoded picture buffer (DPB), and output cropping as shown in Figure C-2. + +![Flowchart of the HRD buffer model. The process starts with a 'Hypothetical stream scheduler (HSS)' which outputs a 'Type I or Type II bitstream' to a 'Coded picture buffer (CPB)'. The CPB outputs 'Access units' to a 'Decoding process (instantaneous)'. The decoding process outputs 'Pictures' to a 'Decoded picture buffer (DPB)'. The DPB outputs 'Pictures' to an 'Output cropping' block. The 'Output cropping' block outputs 'Output cropped pictures'. A feedback loop labeled 'Reference fields or frames' goes from the 'Decoded picture buffer (DPB)' back to the 'Decoding process (instantaneous)'. The diagram is labeled 'H.264(13)_FC-2' at the bottom right.](84d7d5863a5092cbe730c1baeb4fae2e_img.jpg) + +``` + +graph TD + HSS[Hypothetical stream scheduler (HSS)] -- "Type I or Type II bitstream" --> CPB[Coded picture buffer (CPB)] + CPB -- "Access units" --> DP[Decoding process (instantaneous)] + DP -- "Pictures" --> DBP[Decoded picture buffer (DPB)] + DBP -- "Reference fields or frames" --> DP + DBP -- "Pictures" --> OC[Output cropping] + OC -- "Output cropped pictures" --> Output[Output cropped pictures] + +``` + +Flowchart of the HRD buffer model. The process starts with a 'Hypothetical stream scheduler (HSS)' which outputs a 'Type I or Type II bitstream' to a 'Coded picture buffer (CPB)'. The CPB outputs 'Access units' to a 'Decoding process (instantaneous)'. The decoding process outputs 'Pictures' to a 'Decoded picture buffer (DPB)'. The DPB outputs 'Pictures' to an 'Output cropping' block. The 'Output cropping' block outputs 'Output cropped pictures'. A feedback loop labeled 'Reference fields or frames' goes from the 'Decoded picture buffer (DPB)' back to the 'Decoding process (instantaneous)'. The diagram is labeled 'H.264(13)\_FC-2' at the bottom right. + +**Figure C-2 – HRD buffer model** + +The CPB size (number of bits) is $CpbSize[ SchedSelIdx ]$ . The DPB size (number of frame buffers) is $Max( 1, max\_dec\_frame\_buffering )$ . When the coded video sequence conforms to one or more of the profiles specified in Annex G and the decoding process specified in Annex G is applied, the DPB size is specified in units of view components. When the coded video sequence conforms to one or more of the profiles specified in Annex H and the decoding process specified in Annex H is applied, the DPB is operated separately for texture view components and depth view components and the terms texture DPB and depth DPB are used, respectively. The texture DPB size is specified in units of texture view components and the depth DPB size is specified in units of depth view components. + +The HRD operates as follows. Data associated with access units that flow into the CPB according to a specified arrival schedule are delivered by the HSS. The data associated with each access unit are removed and decoded instantaneously by the instantaneous decoding process at CPB removal times. Each decoded picture is placed in the DPB at its CPB removal time unless it is output at its CPB removal time and is a non-reference picture. When a picture is placed in the DPB it is removed from the DPB at the later of the DPB output time or the time that it is marked as "unused for reference". + +For each picture in the bitstream, the variable $OutputFlag$ for the decoded picture and, when applicable, the reference base picture, is set as follows: + +- If the coded video sequence containing the picture conforms to one or more of the profiles specified in Annex A and the decoding process specified in clauses 2 to 9 is applied, $OutputFlag$ is set equal to 1. +- Otherwise, if the coded video sequence containing the picture conforms to one or more of the profiles specified in Annex F and the decoding process specified in Annex F is applied, the following applies: + - For a reference base picture, $OutputFlag$ is set equal to 0. + - For a decoded picture, $OutputFlag$ is set equal to the value of the $output\_flag$ syntax element of the target layer representation. +- Otherwise, if the coded video sequence containing the picture conforms to one or more of the profiles specified in Annex G and the decoding process specified in Annex G is applied, the following applies: + - For the decoded view components of the target output views, $OutputFlag$ is set equal to 1. + - For the decoded view components of other views, $OutputFlag$ is set equal to 0. +- Otherwise (the coded video sequence containing the picture conforms to one or more of the profiles specified in Annex H and the decoding process specified in Annex H is applied), the following applies: + +- For the decoded texture view components and corresponding depth view components with the same VOIdx as the target output views, OutputFlag is set equal to 1. +- For the decoded texture view components and corresponding depth view components with the same VOIdx as other views, OutputFlag is set equal to 0. + +The operation of the CPB is specified in clause C.1. The instantaneous decoder operation is specified in clauses 2 to 9 (for coded video sequences conforming to one or more of the profiles specified in Annex A) and in Annex F (for coded video sequences conforming to one or more of the profiles specified in Annex F) and in Annex G (for coded video sequences conforming to one or more of the profiles specified in Annex G) and in Annex H (for coded video sequences conforming to one or more of the profiles specified in Annex H). The operation of the DPB is specified in clause C.2. The output cropping is specified in clause C.2.2. + +NOTE 6 – Coded video sequences that conform to one or more of the profiles specified in Annex A, and at the same time, one or more of the profiles specified in Annex F can be decoded either by the decoding process specified in clauses 2 to 9 or by the decoding process specified in Annex F. The decoding result and the HRD operation may be dependent on which of the decoding processes is applied. + +NOTE 7 – Coded video sequences that conform to one or more of the profiles specified in Annex A, and at the same time, one or more of the profiles specified in Annex G can be decoded either by the decoding process specified in clauses 2 to 9 or by the decoding process specified in Annex G. The decoding result and the HRD operation may be dependent on which of the decoding processes is applied. + +NOTE 8 – Coded video sequences that conform to one or more of the profiles specified in Annex A, one or more of the profiles specified in Annex G, and one or more of the profiles specified in Annex H, can be decoded either by the decoding process specified in clauses 2 to 9, by the decoding process specified in Annex G or by the decoding process specified in Annex H. The decoding result and the HRD operation may be dependent on which of the decoding processes is applied. + +HSS and HRD information concerning the number of enumerated delivery schedules and their associated bit rates and buffer sizes is specified in clauses E.1.1, E.1.2, E.2.1, E.2.2, F.14.1, F.14.2, G.14.1, G.14.2 and H.14. The HRD is initialized as specified by the buffering period SEI message as specified in clauses D.1.2 and D.2.1. The removal timing of access units from the CPB and output timing from the DPB are specified in the picture timing SEI message as specified in clauses D.1.3 and D.2.3. All timing information relating to a specific access unit shall arrive prior to the CPB removal time of the access unit. + +When the coded video sequence conforms to one or more of the profiles specified in Annex F and the decoding process specified in Annex F is applied, the following is specified: + +- (a) When an access unit contains one or more buffering period SEI messages that are included in scalable nesting SEI messages and are associated with values of DQId in the range of $((DQIdMax \gg 4) \ll 4)$ to $((DQIdMax \gg 4) \ll 4) + 15$ , inclusive, the last of these buffering period SEI messages in decoding order is the buffering period SEI message that initializes the HRD. Let hrdDQId be the largest value of $16 * sei\_dependency\_id[i] + sei\_quality\_id[i]$ that is associated with the scalable nesting SEI message containing the buffering period SEI message that initializes the HRD, let hrdDId and hrdQId be equal to $hrdDQId \gg 4$ and $hrdDQId \& 15$ , respectively, and let hrdTId be the value of $sei\_temporal\_id$ that is associated with the scalable nesting SEI message containing the buffering period SEI message that initializes the HRD. +- (b) The picture timing SEI messages that specify the removal timing of access units from the CPB and output timing from the DPB are the picture timing SEI messages that are included in scalable nesting SEI messages associated with values of $sei\_dependency\_id[i]$ , $sei\_quality\_id[i]$ , and $sei\_temporal\_id$ equal to hrdDId, hrdQId, and hrdTId, respectively. +- (c) The HRD parameters that are used for conformance checking are the HRD parameters included in the SVC video usability information extension of the active SVC sequence parameter set that are associated with values of $vui\_ext\_dependency\_id[i]$ , $vui\_ext\_quality\_id[i]$ , and $vui\_ext\_temporal\_id[i]$ equal to hrdDId, hrdQId, and hrdTId, respectively. For the specification in this annex, $num\_units\_in\_tick$ , $time\_scale$ , $fixed\_frame\_rate\_flag$ , $nal\_hrd\_parameters\_present\_flag$ , $vcl\_hrd\_parameters\_present\_flag$ , $low\_delay\_hrd\_flag$ , and $pic\_struct\_present\_flag$ are substituted with the values of $vui\_ext\_num\_units\_in\_tick[i]$ , $vui\_ext\_time\_scale[i]$ , $vui\_ext\_fixed\_frame\_rate\_flag[i]$ , $vui\_ext\_nal\_hrd\_parameters\_present\_flag[i]$ , $vui\_ext\_vcl\_hrd\_parameters\_present\_flag[i]$ , $vui\_ext\_low\_delay\_hrd\_flag[i]$ , and $vui\_ext\_pic\_struct\_present\_flag[i]$ , respectively, with $i$ being the value for which $vui\_ext\_dependency\_id[i]$ , $vui\_ext\_quality\_id[i]$ , and $vui\_ext\_temporal\_id[i]$ are equal to hrdDId, hrdQId, and hrdTId, respectively. + +When the coded video sequence conforms to one or more of the profiles specified in Annex G and the decoding process specified in Annex G is applied, the following is specified: + +- (a) When an access unit contains one or more buffering period SEI messages that are included in MVC scalable nesting SEI messages, the buffering period SEI message that is associated with the operation point being decoded is the buffering period SEI message that initializes the HRD. Let $hrdVId[i]$ be equal to $sei\_op\_view\_id[i]$ for all $i$ in the range of 0 to $num\_view\_components\_op\_minus1$ , inclusive, and let hrdTId + +be the value of `sei_op_temporal_id`, that are associated with the MVC scalable nesting SEI message containing the buffering period SEI message that initializes the HRD. + +- (b) The picture timing SEI messages that specify the removal timing of access units from the CPB and output timing from the DPB are the picture timing SEI messages that are included in MVC scalable nesting SEI messages associated with values of `sei_op_view_id[ i ]` equal to `hrdVID[ i ]` for all `i` in the range of 0 to `num_view_components_op_minus1`, inclusive, and `sei_temporal_id` equal to `hrdTId`. +- (c) The HRD parameters that are used for conformance checking are the HRD parameters included in the MVC video usability information extension of the active MVC sequence parameter set that are associated with values of `vui_mvc_view_id[ i ][ j ]` for all `j` in the range of 0 to `vui_mvc_num_target_output_views_minus1[ i ]`, inclusive, equal to `hrdVID[ j ]`, and the value of `vui_mvc_temporal_id[ i ]` equal to `hrdTId`. For the specification in this annex, `num_units_in_tick`, `time_scale`, `fixed_frame_rate_flag`, `nal_hrd_parameters_present_flag`, `vcl_hrd_parameters_present_flag`, `low_delay_hrd_flag`, and `pic_struct_present_flag` are substituted with the values of `vui_mvc_num_units_in_tick[ i ]`, `vui_mvc_time_scale[ i ]`, `vui_mvc_fixed_frame_rate_flag[ i ]`, `vui_mvc_nal_hrd_parameters_present_flag[ i ]`, `vui_mvc_vcl_hrd_parameters_present_flag[ i ]`, `vui_mvc_low_delay_hrd_flag[ i ]`, and `vui_mvc_pic_struct_present_flag[ i ]`, respectively, with `i` being the value for which `vui_mvc_view_id[ i ]` is equal to `hrdVID[ j ]` for all `j` in the range of 0 to `vui_mvc_num_target_output_views_minus1[ i ]`, inclusive, and `vui_mvc_temporal_id[ i ]` equal to `hrdTId`. + +When the coded video sequence conforms to one or more of the profiles specified in Annex H and the decoding process specified in Annex H is applied, the following is specified: + +- (a) When an access unit contains one or more buffering period SEI messages that are included in MVCD scalable nesting SEI messages, the buffering period SEI message that is associated with the operation point being decoded is the buffering period SEI message that initializes the HRD. Let `hrdVID[ i ]` be equal to `sei_op_view_id[ i ]` for all `i` in the range of 0 to `num_view_components_op_minus1`, inclusive, and let `hrdTId` be the value of `sei_op_temporal_id`, that are associated with the MVCD scalable nesting SEI message containing the buffering period SEI message that initializes the HRD. +- (b) The picture timing SEI messages that specify the removal timing of access units from the CPB and output timing from the DPB are the picture timing SEI messages that are included in MVCD scalable nesting SEI messages associated with values of `sei_op_view_id[ i ]` equal to `hrdVID[ i ]` for all `i` in the range of 0 to `num_view_components_op_minus1`, inclusive, and `sei_temporal_id` equal to `hrdTId`. +- (c) The HRD parameter sets that are used for conformance checking are the HRD parameter sets, included in the MVC video usability information extension of the active MVCD sequence parameter set, that are associated with values of `vui_mvc_view_id[ i ][ j ]` for all `j` in the range of 0 to `vui_mvc_num_target_output_views_minus1[ i ]`, inclusive, equal to `hrdVID[ j ]`, and the value of `vui_mvc_temporal_id[ i ]` equal to `hrdTId`. For the specification in this annex, `num_units_in_tick`, `time_scale`, `fixed_frame_rate_flag`, `nal_hrd_parameters_present_flag`, `vcl_hrd_parameters_present_flag`, `low_delay_hrd_flag`, and `pic_struct_present_flag` are substituted with the values of `vui_mvc_num_units_in_tick[ i ]`, `vui_mvc_time_scale[ i ]`, `vui_mvc_fixed_frame_rate_flag[ i ]`, `vui_mvc_nal_hrd_parameters_present_flag[ i ]`, `vui_mvc_vcl_hrd_parameters_present_flag[ i ]`, `vui_mvc_low_delay_hrd_flag[ i ]`, and `vui_mvc_pic_struct_present_flag[ i ]`, respectively, with `i` being the value for which `vui_mvc_view_id[ i ]` is equal to `hrdVID[ j ]` for all `j` in the range of 0 to `vui_mvc_num_target_output_views_minus1[ i ]`, inclusive, and `vui_mvc_temporal_id[ i ]` equal to `hrdTId`. + +The HRD is used to check conformance of bitstreams and decoders as specified in clauses C.3 and C.4, respectively. + +NOTE 9 – While conformance is guaranteed under the assumption that all frame-rates and clocks used to generate the bitstream match exactly the values signalled in the bitstream, in a real system each of these may vary from the signalled or specified value. + +All the arithmetic in this annex is done with real values, so that no rounding errors can propagate. For example, the number of bits in a CPB just prior to or after removal of an access unit is not necessarily an integer. + +The variable $t_c$ is derived as follows and is called a clock tick: + +$$t_c = \text{num\_units\_in\_tick} \div \text{time\_scale} \quad (\text{C-1})$$ + +The following is specified for expressing the constraints in this annex: + +- Let access unit $n$ be the $n$ -th access unit in decoding order with the first access unit being access unit 0. +- Let picture $n$ be the primary coded picture or the decoded primary picture of access unit $n$ . + +## C.1 Operation of coded picture buffer (CPB) + +The specifications in this clause apply independently to each set of CPB parameters that is present and to both the Type I and Type II conformance points shown in Figure C-1. + +### C.1.1 Timing of bitstream arrival + +The HRD may be initialized at any one of the buffering period SEI messages. Prior to initialization, the CPB is empty. + +NOTE – After initialization, the HRD is not initialized again by subsequent buffering period SEI messages. + +Each access unit is referred to as access unit $n$ , where the number $n$ identifies the particular access unit. The access unit that is associated with the buffering period SEI message that initializes the CPB is referred to as access unit 0. The value of $n$ is incremented by 1 for each subsequent access unit in decoding order. + +The time at which the first bit of access unit $n$ begins to enter the CPB is referred to as the initial arrival time $t_{ai}(n)$ . + +The initial arrival time of access units is derived as follows: + +- If the access unit is access unit 0, $t_{ai}(0) = 0$ , +- Otherwise (the access unit is access unit $n$ with $n > 0$ ), the following applies: + - If $\text{cbr\_flag[ SchedSelIdx ]}$ is equal to 1, the initial arrival time for access unit $n$ , is equal to the final arrival time (which is derived below) of access unit $n - 1$ , i.e., + +$$t_{ai}(n) = t_{af}(n - 1) \quad (C-2)$$ + +- Otherwise ( $\text{cbr\_flag[ SchedSelIdx ]}$ is equal to 0), the initial arrival time for access unit $n$ is derived by + +$$t_{ai}(n) = \text{Max}( t_{af}(n - 1), t_{ai,earliest}(n) ) \quad (C-3)$$ + +where $t_{ai,earliest}(n)$ is derived as follows: + +- If access unit $n$ is not the first access unit of a subsequent buffering period, $t_{ai,earliest}(n)$ is derived as + +$$t_{ai,earliest}(n) = t_{r,n}(n) - ( \text{initial\_cpb\_removal\_delay[ SchedSelIdx ]} + \text{initial\_cpb\_removal\_delay\_offset[ SchedSelIdx ]} ) \div 90000 \quad (C-4)$$ + +with $t_{r,n}(n)$ being the nominal removal time of access unit $n$ from the CPB as specified in clause C.1.2 and $\text{initial\_cpb\_removal\_delay[ SchedSelIdx ]}$ and $\text{initial\_cpb\_removal\_delay\_offset[ SchedSelIdx ]}$ being specified in the previous buffering period SEI message. + +- Otherwise (access unit $n$ is the first access unit of a subsequent buffering period), $t_{ai,earliest}(n)$ is derived as + +$$t_{ai,earliest}(n) = t_{r,n}(n) - ( \text{initial\_cpb\_removal\_delay[ SchedSelIdx ]} \div 90000 ) \quad (C-5)$$ + +with $\text{initial\_cpb\_removal\_delay[ SchedSelIdx ]}$ being specified in the buffering period SEI message associated with access unit $n$ . + +The final arrival time for access unit $n$ is derived by + +$$t_{af}(n) = t_{ai}(n) + b(n) \div \text{BitRate[ SchedSelIdx ]} \quad (C-6)$$ + +where $b(n)$ is the size in bits of access unit $n$ , counting the bits of the VCL NAL units and the filler data NAL units for the Type I conformance point or all bits of the Type II bitstream for the Type II conformance point, where the Type I and Type II conformance points are as shown in Figure C-1. + +The values of $\text{SchedSelIdx}$ , $\text{BitRate[ SchedSelIdx ]}$ , and $\text{CpbSize[ SchedSelIdx ]}$ are constrained as follows: + +- If the content of the active sequence parameter sets for access unit $n$ and access unit $n - 1$ differ, the HSS selects a value $\text{SchedSelIdx1}$ of $\text{SchedSelIdx}$ from among the values of $\text{SchedSelIdx}$ provided in the active sequence parameter set for access unit $n$ that results in a $\text{BitRate[ SchedSelIdx1 ]}$ or $\text{CpbSize[ SchedSelIdx1 ]}$ for access unit $n$ . The value of $\text{BitRate[ SchedSelIdx1 ]}$ or $\text{CpbSize[ SchedSelIdx1 ]}$ may differ from the value of $\text{BitRate[ SchedSelIdx0 ]}$ or $\text{CpbSize[ SchedSelIdx0 ]}$ for the value $\text{SchedSelIdx0}$ of $\text{SchedSelIdx}$ that was in use for access unit $n - 1$ . +- Otherwise, the HSS continues to operate with the previous values of $\text{SchedSelIdx}$ , $\text{BitRate[ SchedSelIdx ]}$ and $\text{CpbSize[ SchedSelIdx ]}$ . + +When the HSS selects values of BitRate[ SchedSelIdx ] or CpbSize[ SchedSelIdx ] that differ from those of the previous access unit, the following applies: + +- the variable BitRate[ SchedSelIdx ] comes into effect at time $t_{ai}( n )$ +- the variable CpbSize[ SchedSelIdx ] comes into effect as follows: + - If the new value of CpbSize[ SchedSelIdx ] exceeds the old CPB size, it comes into effect at time $t_{ai}( n )$ , + - Otherwise, the new value of CpbSize[ SchedSelIdx ] comes into effect at the time $t_r( n )$ . + +### C.1.2 Timing of coded picture removal + +When an access unit $n$ is the access unit with $n$ equal to 0 (the access unit that initializes the HRD), the nominal removal time of the access unit from the CPB is specified by + +$$t_{r,n}( 0 ) = \text{initial\_cpb\_removal\_delay}[ \text{SchedSelIdx} ] \div 90000 \quad (C-7)$$ + +When an access unit $n$ is the first access unit of a buffering period that does not initialize the HRD, the nominal removal time of the access unit from the CPB is specified by + +$$t_{r,n}( n ) = t_{r,n}( n_b ) + t_c * \text{cpb\_removal\_delay}( n ) \quad (C-8)$$ + +where $t_{r,n}( n_b )$ is the nominal removal time of the first access unit of the previous buffering period and $\text{cpb\_removal\_delay}( n )$ is the value of $\text{cpb\_removal\_delay}$ specified in the picture timing SEI message associated with access unit $n$ . + +The nominal removal time $t_{r,n}( n )$ of an access unit $n$ that is not the first access unit of a buffering period is given by + +$$t_{r,n}( n ) = t_{r,n}( n_b ) + t_c * \text{cpb\_removal\_delay}( n ) \quad (C-9)$$ + +where $t_{r,n}( n_b )$ is the nominal removal time of the first access unit of the current buffering period and $\text{cpb\_removal\_delay}( n )$ is the value of $\text{cpb\_removal\_delay}$ specified in the picture timing SEI message associated with access unit $n$ . + +The removal time of access unit $n$ is specified as follows: + +- If $\text{low\_delay\_hrd\_flag}$ is equal to 0 or $t_{r,n}( n ) \geq t_{af}( n )$ , the removal time of access unit $n$ is specified by + +$$t_r( n ) = t_{r,n}( n ) \quad (C-10)$$ + +- Otherwise ( $\text{low\_delay\_hrd\_flag}$ is equal to 1 and $t_{r,n}( n ) < t_{af}( n )$ ), the removal time of access unit $n$ is specified by + +$$t_r( n ) = t_{r,n}( n ) + t_c * \text{Ceil}( ( t_{af}( n ) - t_{r,n}( n ) ) \div t_c ) \quad (C-11)$$ + +NOTE – The latter case indicates that the size of access unit $n$ , $b( n )$ , is so large that it prevents removal at the nominal removal time. + +When an access unit $n$ is the first access unit of a buffering period, $n_b$ is set equal to $n$ at the removal time $t_r( n )$ of the access unit $n$ . + +### C.2 Operation of the decoded picture buffer (DPB) + +The decoded picture buffer contains frame buffers. When a coded video sequence conforming to one or more of the profiles specified in Annex A is decoded by applying the decoding process specified in clauses 2 to 9, each of the frame buffers may contain a decoded frame, a decoded complementary field pair or a single (non-paired) decoded field that is marked as "used for reference" (reference pictures) or is held for future output (reordered or delayed pictures). When a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded by applying the decoding process specified in Annex F, each frame buffer may contain a decoded frame, a decoded complementary field pair, a single (non-paired) decoded field, a decoded reference base frame, a decoded reference base complementary field pair or a single (non-paired) decoded reference base field that is marked as "used for reference" (reference pictures) or is held for future output (reordered or delayed pictures). When a coded video sequence conforming to one or more of the profiles specified in Annex G is decoded by applying the decoding process specified in Annex G, each of the frame buffers may contain a decoded frame view component, a decoded complementary field view component pair, or a single (non-paired) decoded field view component that is marked as "used for reference" (reference pictures) or is held for future output (reordered or delayed pictures) or is held as reference for inter-view prediction (inter-view only reference components). When a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying + +the decoding process specified in Annex H, each of the frame buffers of the texture DPB may contain: a decoded depth frame view component, a decoded complementary texture field view component pair, or a single (non-paired) decoded texture field view component that is marked as "used for reference" (reference pictures) or is held for future output (reordered or delayed pictures) or is held as reference for inter-view prediction (inter-view only reference components). When a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying the decoding process specified in Annex H, each of the frame buffers of the depth DPB may contain a decoded depth frame view component, a decoded complementary depth field view component pair, or a single (non-paired) decoded depth field view component that is marked as "used for reference" (reference pictures) or is held for future output (reordered or delayed pictures) or is held as reference for inter-view prediction (inter-view only reference components). + +Prior to initialization, the DPB is empty (the DPB fullness is set to zero). The following steps specified in this clause all happen instantaneously at $t_c(n)$ and in the order listed. When the decoding process specified in Annex G or Annex H is applied, the view components of the current primary coded picture are processed by applying the ordered steps to each view component in increasing order of the associated view order index VOIdx. During the invocation of the process for a particular texture view, only the texture view components of the particular view are considered. During the invocation of the process for a particular depth view, only the depth view components of the particular view are considered. For each view component of the current primary coded picture, the corresponding depth view component with the same view order index VOIdx, if present, is processed after the texture view component. + +1. The process of decoding gaps in frame\_num and storing "non-existing" frames as specified in clause C.2.1 is invoked. +2. The picture decoding and output process as specified in clause C.2.2 is invoked. +3. The process of removing pictures from the DPB before possible insertion of the current picture as specified in clause C.2.3 is invoked. +4. The process of marking and storing the current decoded picture as specified in clause C.2.4 is invoked. + +NOTE – When the decoding process specified in Annex F is applied, the DPB is only operated for decoded pictures and reference base pictures associated with decoded pictures. The DPB is not operated for layer pictures with dependency\_id less than DependencyIdMax (and associated reference base pictures). All decoded pictures and associated reference base pictures are decoded pictures and associated reference base pictures for dependency\_id equal to DependencyIdMax, which represent the results of the decoding process specified in clause F.8. + +### C.2.1 Decoding of gaps in frame\_num and storage of "non-existing" frames + +When the decoding process specified in Annex G is applied, the process specified in this clause is invoked for a particular view with view order index VOIdx, with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". During the invocation of the process for a particular view, only view components of the particular view are considered and view components of other views are not marked as "unused for reference" or removed from the DPB. When the decoding process specified in Annex H is applied, the process specified in this clause for Annex G is invoked for particular texture view or depth view with view order index VOIdx, with each "view component" being replaced by "texture view component" or "depth view component", "frame view component" being replaced by "texture frame view component" or "depth frame view component", and "field view component" being replaced by "texture field view component". During the invocation of the process for a particular texture view, only the texture view components of the particular view are considered and during the invocation of the process for a particular depth view, only the depth view components of the particular view are considered and view components of other views are not marked as "unused for reference" or removed from the DPB. + +The DPB fullness represents the total number of non-empty frame buffers. When the decoding process specified in Annex G is applied; this includes frame buffers that contain view components of other views. When the decoding process specified in Annex H is applied, this includes frame buffers that contain texture or depth view components of other views. + +When applicable, gaps in frame\_num are detected by the decoding process and the generated frames are marked and inserted into the DPB as specified below. + +Gaps in frame\_num are detected by the decoding process and the generated frames are marked as specified in clauses 8.2.5.2 and F.8.2.5. + +After the marking of each generated frame, each picture $m$ marked by the "sliding window" process as "unused for reference" is removed from the DPB when it is also marked as "non-existing" or its DPB output time is less than or equal to the CPB removal time of the current picture $n$ ; i.e., $t_{o,dpb}(m) \leq t_c(n)$ , or it has OutputFlag equal to 0. When a frame or the last field in a frame buffer is removed from the DPB, the DPB fullness is decremented by one. The "non-existing" generated frame is inserted into the DPB and the DPB fullness is incremented by one. + +## C.2.2 Picture decoding and output + +When the decoding process specified in Annex G is applied, the process specified in this clause is invoked for a particular view with view order index VOIdx. + +When the decoding process specified in Annex H is applied, the process specified in this clause is invoked for a particular texture view or depth view with view order index VOIdx. + +The decoding of the current picture or view component (when applying the decoding process specified in Annex G or Annex H) and the derivation of the DPB output time (if applicable) is specified as follows: + +- If the decoding process specified in clause 8 or Annex F is applied, the following applies: + - The current primary coded picture $n$ is decoded. + - When picture $n$ has OutputFlag equal to 1, its DPB output time $t_{o,dpb}(n)$ is derived by + +$$t_{o,dpb}(n) = t_r(n) + t_c * dpb\_output\_delay(n) \quad (C-12)$$ + +where $dpb\_output\_delay(n)$ is the value of $dpb\_output\_delay$ specified in the picture timing SEI message associated with access unit $n$ . + +- Otherwise (the decoding process specified in Annex G or Annex H is applied), the following applies: + - The view component with view order index VOIdx of the current primary coded picture $n$ is decoded. + - When VOIdx is equal to VOIdxMin and any of the view components of picture $n$ has OutputFlag equal to 1, the DPB output time $t_{o,dpb}(n)$ for picture $n$ is derived by Equation C-12, where $dpb\_output\_delay(n)$ is the value of $dpb\_output\_delay$ specified in the picture timing SEI message associated with access unit $n$ . + +The output of the current picture or view component (when applying the decoding process specified in Annex G) is specified as follows: + +- If OutputFlag is equal to 1 and $t_{o,dpb}(n) = t_r(n)$ , the current picture or view component is output. + +NOTE 1 – When the current picture or view component has $nal\_ref\_idc$ greater than 0 (when using the decoding process specified in Annex F, $nal\_ref\_idc$ is the syntax element of the target layer representation), it will be stored in the DPB. + +- Otherwise, if OutputFlag is equal to 0, the current picture or view component is not output, but it may be stored in the DPB as specified in clause C.2.4. +- Otherwise (OutputFlag is equal to 1 and $t_{o,dpb}(n) > t_r(n)$ ), the current picture or view component is output later and will be stored in the DPB (as specified in clause C.2.4) and is output at time $t_{o,dpb}(n)$ unless indicated not to be output by the decoding or inference of $no\_output\_of\_prior\_pics\_flag$ equal to 1 at a time that precedes $t_{o,dpb}(n)$ . + +NOTE 2 – When the coded video sequence conforms to a profile specified in Annex G and the decoding process specified in Annex G is used, the view components of all the target output views of a picture are output at the same time instant and in increasing order of the view order index VOIdx. + +NOTE 3 – When the coded video sequence conforms to a profile specified in Annex H and the decoding process specified in Annex H is used, the view components of all the target output views of a picture are output at the same time instant and in increasing order of the view order index VOIdx. A depth view component, if present, follows the texture view component within the same view component. + +When output, the picture or view component shall be cropped, using the cropping rectangle specified in the active sequence parameter set for the picture or view component. + +When the decoding process specified in clause 8 or Annex F is applied, the current picture $n$ is a picture that is output and is not the last picture of the bitstream that is output, the value of $\Delta t_{o,dpb}(n)$ is derived by + +$$\Delta t_{o,dpb}(n) = t_{o,dpb}(n_n) - t_{o,dpb}(n) \quad (C-13)$$ + +where $n_n$ indicates the picture that follows after picture $n$ in output order and has OutputFlag equal to 1. + +When the decoding process specified in Annex G or Annex H is applied, the current picture $n$ is a picture that contains at least one view component that is output and the current picture is not the last picture of the bitstream that contains at least one view component that is output and VOIdx is equal to VOIdxMin, the value of $\Delta t_{o,dpb}(n)$ is derived by Equation C-13, where $n_n$ indicates the picture that follows after picture $n$ in output order and contains at least one any view component with OutputFlag equal to 1. + +The decoded picture or view component is temporarily stored (not in the DPB). + +### C.2.3 Removal of pictures from the DPB before possible insertion of the current picture + +When the decoding process specified in Annex G is applied, the process specified in this clause is invoked for a particular view with view order index VOIdx, with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". + +When the decoding process specified in Annex H is applied, the process specified in this clause for Annex H is invoked for particular texture view and depth view with view order index VOIdx, with each "view component" being replaced by "texture view component" or "depth view component", "frame view component" being replaced by "texture frame view component" or "depth frame view component", and "field view component" being replaced by "texture field view component". During the invocation of the process for a particular texture view, only the texture view components of the particular view are considered and during the invocation of the process for a particular depth view, only the depth view components of the particular view are considered. + +When the decoding process specified in Annex G or Annex H is applied, the following process is specified for removing inter-view only reference components of the current access unit from the DPB. By this process, view components of the current view with view order index VOIdx are not removed from the DPB, but inter-view only reference components of other views may be removed. The removal of inter-view only reference components is specified as follows: + +- If the view order index VOIdx of the current view is equal to VOIdxMax, all inter-view only reference components $m$ for which any of the following conditions are true are removed from the DPB: + - OutputFlag is equal to 0, + - The DPB output time $t_{o,dpb}(m)$ of the picture containing the view component $m$ is less than or equal to the CPB removal time $t_r(n)$ of the current picture. +- Otherwise (the view order index VOIdx of the current view is less than VOIdxMax), all inter-view only reference components $m$ for which both of the following conditions are true are removed from the DPB: + - OutputFlag is equal to 0 or the DPB output time $t_{o,dpb}(m)$ of the picture containing the view component $m$ is less than or equal to the CPB removal time $t_r(n)$ of the current picture, + - One of the following conditions is true: + - The current view component is a view component of an anchor picture and the view\_id of the inter-view only reference component $m$ is not equal to any value of $anchor\_ref\_IX[ k ][ j ]$ , with $X$ being equal to 0 or 1, $k$ being any integer value greater than the view order index VOIdx of the current view, and $j$ being any integer value in the range of 0 to $Max( 0, num\_anchor\_refs\_IX[ k ] - 1 )$ , inclusive, + - The current view component is not a view component of an anchor picture and the view\_id of the inter-view only reference component $m$ is not equal to any value of $non\_anchor\_ref\_IX[ k ][ j ]$ , with $X$ being equal to 0 or 1, $k$ being any integer value greater than the view order index VOIdx of the current view, and $j$ being any integer value in the range of 0 to $Max( 0, num\_non\_anchor\_refs\_IX[ k ] - 1 )$ , inclusive. + +When the decoding process specified in Annex G is applied, for the following processes specified in this clause, only view components of the particular view for which this clause is invoked are considered, and view components of other views are not marked as "unused for reference" or removed from the DPB. When the decoding process specified in Annex H is applied, for the following processes specified for Annex H in this clause, during the invocation of the process for a particular texture view, only texture view components of the particular texture view are considered and during the invocation of the process for a particular depth view, only depth view components of the particular depth view are considered, and view components of other views are not marked as "unused for reference" or removed from the DPB. + +The DPB fullness represents the total number of non-empty frame buffers. When the decoding process specified in Annex G is applied, this includes frame buffers that contain texture view components of other views. When the decoding process specified in Annex H is applied, this includes frame buffers that contain texture or depth view components of other views. + +The removal of pictures from the DPB before possible insertion of the current picture proceeds as follows: + +- If the decoded picture is an IDR picture the following applies: + 1. All reference pictures in the DPB are marked as "unused for reference" as specified in clause 8.2.5.1 when a coded video sequence conforming to one or more of the profiles specified in Annex A is decoded by applying the decoding process specified in clauses 2 to 9, or as specified in clause F.8.2.4 when a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded by applying the decoding process specified in Annex F, or as specified in clause G.8.3 when a coded video sequence conforming to one or more of the profiles specified in Annex G is decoded by applying the decoding process specified in Annex G, or as + +specified in clause H.8.3 when a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying the decoding process specified in Annex H. + +2. When the IDR picture is not the first IDR picture decoded and the value of PicWidthInMbs or FrameHeightInMbs or max\_dec\_frame\_buffering derived from the active sequence parameter set is different from the value of PicWidthInMbs or FrameHeightInMbs or max\_dec\_frame\_buffering derived from the sequence parameter set that was active for the preceding picture, respectively, no\_output\_of\_prior\_pics\_flag is inferred to be equal to 1 by the HRD, regardless of the actual value of no\_output\_of\_prior\_pics\_flag. + +NOTE – Decoder implementations should try to handle frame or DPB size changes more gracefully than the HRD in regard to changes in PicWidthInMbs or FrameHeightInMbs. + +3. When no\_output\_of\_prior\_pics\_flag is equal to 1 or is inferred to be equal to 1, all frame buffers in the DPB are emptied without output of the pictures they contain, and DPB fullness is set to 0. + +– Otherwise (the decoded picture is not an IDR picture), the following applies: + +- If the slice header of the current picture includes memory\_management\_control\_operation equal to 5, all reference pictures in the DPB are marked as "unused for reference". +- Otherwise (the slice header of the current picture does not include memory\_management\_control\_operation equal to 5), the decoded reference picture marking process specified in clause 8.2.5 is invoked when a coded video sequence conforming to one or more of the profiles specified in Annex A is decoded by applying the decoding process specified in clauses 2 to 9, or the decoded reference picture marking process specified in clause F.8.2.4 is invoked when a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded by applying the decoding process specified in Annex F, or the decoded reference picture marking process specified in clause G.8.3 is invoked when a coded video sequence conforming to one or more of the profiles specified in Annex G is decoded by applying the decoding process specified in Annex G, or the decoded reference picture marking process specified in clause H.8.3 is invoked when a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying the decoding process specified in Annex H. + +All pictures m in the DPB, for which all of the following conditions are true, are removed from the DPB: + +- picture m is marked as "unused for reference" or picture m is a non-reference picture. When a picture is a reference frame, it is considered to be marked as "unused for reference" only when both of its fields have been marked as "unused for reference", +- picture m is marked as "non-existing" or it has OutputFlag equal to 0 or its DPB output time $t_{o,dpb}(m)$ is less than or equal to the CPB removal time $t_r(n)$ of the current picture n. + +When a frame or the last field in a frame buffer is removed from the DPB, the DPB fullness is decremented by one. + +#### C.2.4 Current decoded picture marking and storage + +When the decoding process specified in Annex G is applied, the process specified in this clause is invoked for a particular view with view order index VOIdx, with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". When the decoding process specified in Annex H is applied, the process specified in this clause for Annex H is invoked for particular texture view and depth view with view order index VOIdx, with each "view component" being replaced by "texture view component" and "depth view component", "frame view component" being replaced by "texture frame view component" and "depth frame view component", and "field view component" being replaced by "texture field view component". In clause C.2.4.2, the DPB output time $t_{o,dpb}(n)$ and the CPB removal time $t_r(n)$ of a view component are the DPB output time and the CPB removal time of the picture n containing the view component. + +The marking and storage of the current decoded picture is specified as follows: + +- If the current picture is a reference picture, the marking and storage process for reference pictures as specified in clause C.2.4.1 is invoked. +- Otherwise (the current picture is a non-reference picture), the storage process for non-reference pictures as specified in clause C.2.4.2 is invoked. + +##### C.2.4.1 Marking and storage of a reference picture into the DPB + +The current picture is stored in the DPB as follows: + +- If the current decoded picture is a second field (in decoding order) of a complementary reference field pair, and the first field of the pair is still in the DPB, the current decoded picture is stored in the same frame buffer as the first field of the pair. + +- Otherwise, the current decoded picture is stored in an empty frame buffer, and the DPB fullness is incremented by one. + +When the coded video sequence conforms to one or more of the profiles specified in Annex F and the decoding process specified in Annex F is applied and the current picture has `store_ref_base_pic_flag` equal to 1 (i.e., the current picture is associated with a reference base picture), the associated reference base picture is stored in the DPB as follows: + +- If the reference base picture is a second field (in decoding order) of a complementary reference base field pair, and the first field of the pair is still in the DPB, the reference base picture is stored in the same frame buffer as the first field of the pair. +- Otherwise, the reference base picture is stored in an empty frame buffer, and the DPB fullness is incremented by one. + +#### C.2.4.2 Storage of a non-reference picture into the DPB + +The variable `storePicFlag` is derived as follows: + +- If any of the following conditions are true, `storePicFlag` is set equal to 1: + - the current picture `n` has `OutputFlag` equal to 1 and $t_{o,dpb}(n) > t_r(n)$ , + - the decoding process specified in Annex G or Annex H is used and the current view component has a view order index `VOIdx` less than `VOIdxMax` and `inter_view_flag` equal to 1. +- Otherwise, `storePicFlag` is set equal to 0. + +When `storePicFlag` is equal to 1, the current picture is stored in the DPB as follows: + +- If the current decoded picture is a second field (in decoding order) of a complementary non-reference field pair, and the first field of the pair is still in the DPB, the current decoded picture is stored in the same frame buffer as the first field of the pair. +- Otherwise, the current decoded picture is stored in an empty frame buffer, and the DPB fullness is incremented by one. + +### C.3 Bitstream conformance + +A bitstream of coded data conforming to this Recommendation | International Standard fulfils the following requirements. + +The bitstream is constructed according to the syntax, semantics, and constraints specified in this Recommendation | International Standard outside of this annex. + +The bitstream is tested by the HRD as specified below: + +For Type I bitstreams, the number of tests carried out is equal to `cpb_cnt_minus1 + 1` where `cpb_cnt_minus1` is either the syntax element of `hrd_parameters()` following the `vc1_hrd_parameters_present_flag` or is determined by the application by other means not specified in this Recommendation | International Standard. One test is carried out for each bit rate and CPB size combination specified by `hrd_parameters()` following the `vc1_hrd_parameters_present_flag`. Each of these tests is conducted at the Type I conformance point shown in Figure C-1. + +For Type II bitstreams there are two sets of tests. The number of tests of the first set is equal to `cpb_cnt_minus1 + 1` where `cpb_cnt_minus1` is either the syntax element of `hrd_parameters()` following the `vc1_hrd_parameters_present_flag` or is determined by the application by other means not specified in this Recommendation | International Standard. One test is carried out for each bit rate and CPB size combination. Each of these tests is conducted at the Type I conformance point shown in Figure C-1. For these tests, only VCL and filler data NAL units are counted for the input bit rate and CPB storage. + +The number of tests of the second set, for Type II bitstreams, is equal to `cpb_cnt_minus1 + 1` where `cpb_cnt_minus1` is either the syntax element of `hrd_parameters()` following the `nal_hrd_parameters_present_flag` or is determined by the application by other means not specified in this Recommendation | International Standard. One test is carried out for each bit rate and CPB size combination specified by `hrd_parameters()` following the `nal_hrd_parameters_present_flag`. Each of these tests is conducted at the Type II conformance point shown in Figure C-1. For these tests, all NAL units (of a Type II NAL unit stream) or all bytes (of a byte stream) are counted for the input bit rate and CPB storage. + +NOTE 1 – NAL HRD parameters established by a value of `SchedSelIdx` for the Type II conformance point shown in Figure C-1 are sufficient to also establish VCL HRD conformance for the Type I conformance point shown in Figure C-1 for the same values of `initial_cpb_removal_delay[SchedSelIdx]`, `BitRate[SchedSelIdx]`, and `CpbSize[SchedSelIdx]` for the VBR case (`cbr_flag[SchedSelIdx]` equal to 0). This is because the data flow into the Type I conformance point is a subset of the data flow into the Type II conformance point and because, for the VBR case, the CPB is allowed to become empty and stay empty until the time a next picture is scheduled to begin to arrive. For example, when a coded video sequence conforming to one or more of the + +profiles specified in Annex A is decoded by applying the decoding process specified in clauses 2 to 9, when NAL HRD parameters are provided for the Type II conformance point that not only fall within the bounds set for NAL HRD parameters for profile conformance in item j) of clause A.3.1 or item h) of clause A.3.3 (depending on the profile in use) but also fall within the bounds set for VCL HRD parameters for profile conformance in item i) of clause A.3.1 or item g) of clause A.3.3 (depending on the profile in use), conformance of the VCL HRD for the Type I conformance point is also assured to fall within the bounds of item i) of clause A.3.1. + +For conforming bitstreams, all of the following conditions shall be fulfilled for each of the tests: + +1. For each access unit $n$ , with $n > 0$ , associated with a buffering period SEI message, with $\Delta t_{g,90}(n)$ specified by + +$$\Delta t_{g,90}(n) = 90000 * (t_{r,n}(n) - t_{ar}(n-1)) \quad (C-14)$$ + +the value of $initial\_cpb\_removal\_delay[ \text{SchedSelIdx} ]$ shall be constrained as follows: + +- If $cbr\_flag[ \text{SchedSelIdx} ]$ is equal to 0, + +$$initial\_cpb\_removal\_delay[ \text{SchedSelIdx} ] \leq \text{Ceil}( \Delta t_{g,90}(n) ) \quad (C-15)$$ + +- Otherwise ( $cbr\_flag[ \text{SchedSelIdx} ]$ is equal to 1), + +$$\text{Floor}( \Delta t_{g,90}(n) ) \leq initial\_cpb\_removal\_delay[ \text{SchedSelIdx} ] \leq \text{Ceil}( \Delta t_{g,90}(n) ) \quad (C-16)$$ + +NOTE 2 – The exact number of bits in the CPB at the removal time of each picture may depend on which buffering period SEI message is selected to initialize the HRD. Encoders must take this into account to ensure that all specified constraints must be obeyed regardless of which buffering period SEI message is selected to initialize the HRD, as the HRD may be initialized at any one of the buffering period SEI messages. + +2. A CPB overflow is specified as the condition in which the total number of bits in the CPB is larger than the CPB size. The CPB shall never overflow. +3. A CPB underflow is specified as the condition in which $t_{r,n}(n)$ is less than $t_{ar}(n)$ . When $low\_delay\_hrd\_flag$ is equal to 0, the CPB shall never underflow. +4. The nominal removal times of pictures from the CPB (starting from the second picture in decoding order), shall satisfy the constraints on $t_{r,n}(n)$ and $t_r(n)$ expressed in clauses A.3.1 through A.3.3 for the profile and level specified in the bitstream when a coded video sequence conforming to one or more of the profiles specified in Annex A is decoded by applying the decoding process specified in clauses 2 to 9, and they shall satisfy the constraints on $t_{r,n}(n)$ and $t_r(n)$ expressed in clauses F.10.2.1 and F.10.2.2 for profile and level specified in the bitstream when a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded by applying the decoding process specified in Annex F, and they shall satisfy the constraints on $t_{r,n}(n)$ and $t_r(n)$ expressed in clause G.10.2 for the profile and level specified in the bitstream when a coded video sequence conforming to one or more of the profiles specified in Annex G is decoded by applying the decoding process specified in Annex G, and they shall satisfy the constraints on $t_{r,n}(n)$ and $t_r(n)$ expressed in clause H.10.2 for the profile and level specified in the bitstream when a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying the decoding process specified in Annex H. +5. Immediately after any decoded picture is added to the DPB, the fullness of the DPB shall be less than or equal to the DPB size as constrained by Annexes A, D, and E, and clauses F.10, F.13, F.14, G.10, G.13, G.14, and H.14 for the profile and level specified in the bitstream. +6. All reference pictures shall be present in the DPB when needed for prediction. Each picture shall be present in the DPB at its DPB output time unless it is not stored in the DPB at all, or is removed from the DPB before its output time by one of the processes specified in clause C.2. +7. The value of $\Delta t_{o,dpb}(n)$ as given by Equation C-13, which is the difference between the output time of a picture and that of the first picture following it in output order and having $OutputFlag$ equal to 1, shall satisfy the constraint expressed in clause A.3.1 for the profile and level specified in the bitstream when a coded video sequence conforming to one or more of the profiles specified in Annex A is decoded by applying the decoding process specified in clauses 2 to 9, and it shall satisfy the constraint expressed in clause F.10.2.1 for profile and level specified in the bitstream when a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded by applying the decoding process specified in Annex F, and it shall satisfy the constraints expressed in clause G.10.2 for the profile and level specified in the bitstream when a coded video sequence conforming to one or more of the profiles specified in Annex G is decoded by applying the decoding process specified in Annex G, and it shall satisfy the constraints expressed in clause H.10.2 for the profile and level specified in the bitstream when a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying the decoding process specified in Annex H. + +## C.4 Decoder conformance + +A decoder conforming to this Recommendation | International Standard fulfils the following requirements. + +A decoder claiming conformance to a specific profile and level shall be able to decode successfully all conforming bitstreams specified for decoder conformance in clause C.3, provided that all sequence parameter sets and picture parameter sets referred to in the VCL NAL units, and appropriate buffering period and picture timing SEI messages are conveyed to the decoder, in a timely manner, either in the bitstream (by non-VCL NAL units), or by external means not specified by this Recommendation | International Standard. + +There are two types of conformance that can be claimed by a decoder: output timing conformance and output order conformance. + +To check conformance of a decoder, test bitstreams conforming to the claimed profile and level, as specified in clause C.3 are delivered by a hypothetical stream scheduler (HSS) both to the HRD and to the decoder under test (DUT). All pictures output by the HRD shall also be output by the DUT and, for each picture output by the HRD, the values of all samples that are output by the DUT for the corresponding picture shall be equal to the values of the samples output by the HRD. + +For output timing decoder conformance, the HSS operates as described above, with delivery schedules selected only from the subset of values of SchedSelIdx for which the bit rate and CPB size are restricted as specified in Annex A, Annex F, Annex G, and Annex H for the specified profile and level, or with "interpolated" delivery schedules as specified below for which the bit rate and CPB size are restricted as specified in Annex A, Annex F, Annex G, and Annex H. The same delivery schedule is used for both the HRD and DUT. + +When the HRD parameters and the buffering period SEI messages are present with cpb\_cnt\_minus1 greater than 0, the decoder shall be capable of decoding the bitstream as delivered from the HSS operating using an "interpolated" delivery schedule specified as having peak bit rate $r$ , CPB size $c(r)$ , initial CPB removal delay $(f(r) \div r)$ , and initial CPB removal delay offset $(o(r) \div r)$ as follows: + +$$\alpha = (r - \text{BitRate}[\text{SchedSelIdx} - 1]) \div (\text{BitRate}[\text{SchedSelIdx}] - \text{BitRate}[\text{SchedSelIdx} - 1]), \quad (\text{C-17})$$ + +$$c(r) = \alpha * \text{CpbSize}[\text{SchedSelIdx}] + (1 - \alpha) * \text{CpbSize}[\text{SchedSelIdx} - 1], \quad (\text{C-18})$$ + +$$f(r) = \alpha * \text{initial\_cpb\_removal\_delay}[\text{SchedSelIdx}] * \text{BitRate}[\text{SchedSelIdx}] + (1 - \alpha) * \text{initial\_cpb\_removal\_delay}[\text{SchedSelIdx} - 1] * \text{BitRate}[\text{SchedSelIdx} - 1] \quad (\text{C-19})$$ + +$$o(r) = \alpha * \text{initial\_cpb\_removal\_delay\_offset}[\text{SchedSelIdx}] * \text{BitRate}[\text{SchedSelIdx}] + (1 - \alpha) * \text{initial\_cpb\_removal\_delay\_offset}[\text{SchedSelIdx} - 1] * \text{BitRate}[\text{SchedSelIdx} - 1] \quad (\text{C-20})$$ + +for any SchedSelIdx > 0 and $r$ such that $\text{BitRate}[\text{SchedSelIdx} - 1] \leq r \leq \text{BitRate}[\text{SchedSelIdx}]$ such that $r$ and $c(r)$ are within the limits as specified in Annex A, Annex F, Annex G, and Annex H for the maximum bit rate and buffer size for the specified profile and level. + +NOTE 1 – $\text{initial\_cpb\_removal\_delay}[\text{SchedSelIdx}]$ can be different from one buffering period to another and have to be re-calculated. + +For output timing decoder conformance, an HRD as described above is used and the timing (relative to the delivery time of the first bit) of picture output is the same for both HRD and the DUT up to a fixed delay. + +For output order decoder conformance, the HSS delivers the bitstream to the DUT "by demand" from the DUT, meaning that the HSS delivers bits (in decoding order) only when the DUT requires more bits to proceed with its processing. + +NOTE 2 – This means that for this test, the coded picture buffer of the DUT could be as small as the size of the largest access unit. + +A modified HRD as described below is used, and the HSS delivers the bitstream to the HRD by one of the schedules specified in the bitstream such that the bit rate and CPB size are restricted as specified in Annex A, Annex F, Annex G, and Annex H. The order of pictures output shall be the same for both HRD and the DUT. + +For output order decoder conformance, the HRD CPB size is equal to $\text{CpbSize}[\text{SchedSelIdx}]$ for the selected schedule and the DPB size is equal to $\text{MaxDpbFrames}$ . Removal time from the CPB for the HRD is equal to final bit arrival time and decoding is immediate. The operation of the DPB of this HRD is specified in clause C.4.1. + +### C.4.1 Operation of the output order DPB + +The decoded picture buffer contains frame buffers. When a coded video sequence conforming to one or more of the profiles specified in Annex A is decoded by applying the decoding process specified in clauses 2 to 9, each of the frame buffers may contain a decoded frame, a decoded complementary field pair or a single (non-paired) decoded field that is marked as "used for reference" or is held for future output (reordered pictures). When a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded by applying the decoding process specified in Annex F, + +each frame buffer may contain a decoded frame, a decoded complementary field pair, a single (non-paired) decoded field, a decoded reference base frame, a decoded reference base complementary field pair or a single (non-paired) decoded reference base field that is marked as "used for reference" (reference pictures) or is held for future output (reordered or delayed pictures). When a coded video sequence conforming to one or more of the profiles specified in Annex G is decoded by applying the decoding process specified in Annex G, each of the frame buffers may contain a decoded frame view component, a decoded complementary field view component pair, or a single (non-paired) decoded field view component that is marked as "used for reference" (reference pictures) or is held for future output (reordered or delayed pictures) or is held for inter-view prediction (inter-view only reference components). When a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying the decoding process specified in Annex H, each of the frame buffers of the texture DPB may contain a decoded texture frame view component, a decoded complementary texture field view component pair, a single (non-paired) decoded texture field view component that is marked as "used for reference" (reference pictures) or is held for future output (reordered or delayed pictures) or is held for inter-view prediction (inter-view only reference components). When a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying the decoding process specified in Annex H, each of the frame buffers of the depth DPB may contain a decoded depth frame view component, a decoded complementary depth field view component pair, or a single (non-paired) decoded depth field view component that is marked as "used for reference" (reference pictures) or is held for future output (reordered or delayed pictures) or is held as reference for inter-view prediction (inter-view only reference components). + +At HRD initialization, the DPB fullness, measured in non-empty frame buffers, is set equal to 0. The following steps all happen instantaneously when an access unit is removed from the CPB, and in the order listed. When the decoding process specified in Annex G or Annex H is applied, the view components of the current primary coded picture are processed by applying the ordered steps to each view component in increasing order of the associated view order index VOIdx. The invocation of the process for a depth view component, if present, follows the invocation of the process for the texture view component within the same view component. + +1. The process of decoding gaps in frame\_num and storing "non-existing" frames as specified in clause C.4.2 is invoked. +2. The picture decoding and output process as specified in clause C.4.3 is invoked. +3. The process of removing pictures from the DPB before possible insertion of the current picture as specified in clause C.4.4 is invoked. +4. The process of marking and storing the current decoded picture as specified in clause C.4.5 is invoked. + +NOTE – When the decoding process specified in Annex F is applied, the DPB is only operated for decoded pictures and reference base pictures associated with decoded pictures. The DPB is not operated for layer pictures with dependency\_id less than DependencyIdMax (and associated reference base pictures). All decoded pictures and associated reference base pictures are decoded pictures and associated reference base pictures for dependency\_id equal to DependencyIdMax, which represent the results of the decoding process specified in clause F.8. + +#### C.4.2 Decoding of gaps in frame\_num and storage of "non-existing" pictures + +When the decoding process specified in Annex G is applied, the process specified in this clause is invoked for a particular view with view order index VOIdx, with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". During the invocation of the process for a particular view, only view components of the particular view are considered and view components of other views are not marked as "unused for reference" or removed from the DPB. + +When the decoding process specified in Annex H is applied, the process specified in this clause for Annex G is invoked for particular texture view and depth view with view order index VOIdx, with each "view component" being replaced by "texture view component" or "depth view component", "frame view component" being replaced by "texture frame view component" or "depth frame view component", and "field view component" being replaced by "texture field view component". During the invocation of the process for a particular texture view, only the texture view components of the particular view are considered and during the invocation of the process for a particular depth view, only the depth view components of the particular view are considered and view components of other views are not marked as "unused for reference" or removed from the DPB. + +The DPB fullness represents the total number of non-empty frame buffers. When the decoding process specified in Annex G is applied, this includes frame buffers that contain view components of other views. When the decoding process specified in Annex H is applied, this includes frame buffers that contain texture or depth view components of other views. + +When applicable, gaps in frame\_num are detected by the decoding process and the necessary number of "non-existing" frames are inferred in the order specified by the generation of values of UnusedShortTermFrameNum in Equation 7-26 and are marked as specified in clauses 8.2.5.2 and F.8.2.5. Frame buffers containing a frame or a complementary field pair or a non-paired field which are marked as "not needed for output" and "unused for reference" are emptied (without + +output), and the DPB fullness is decremented by the number of frame buffers emptied. Each "non-existing" frame is stored in the DPB as follows: + +- When there is no empty frame buffer (i.e., DPB fullness is equal to DPB size), the "bumping" process specified in clause C.4.5.3 is invoked repeatedly until there is an empty frame buffer in which to store the "non-existing" frame. +- The "non-existing" frame is stored in an empty frame buffer and is marked as "not needed for output", and the DPB fullness is incremented by one. + +#### C.4.3 Picture decoding + +When the decoding process specified in Annex G is applied, the process specified in this clause is invoked for a particular view with view order index VOIdx. + +When the decoding process specified in Annex H is applied, the process specified for Annex G in this clause is invoked for a particular texture view and depth view with view order index VOIdx. + +The decoding of the current picture or view component (when applying the decoding process specified in Annex G or Annex H) is specified as follows: + +- If the decoding process specified in clause 8 or Annex F is applied, the current primary coded picture n is decoded and is temporarily stored (not in the DPB). +- Otherwise (the decoding process specified in Annex G or Annex H is applied), the view component with view order index VOIdx of the current primary coded picture n is decoded and is temporarily stored (not in the DPB). + +#### C.4.4 Removal of pictures from the DPB before possible insertion of the current picture + +When the decoding process specified in Annex G is applied, the process specified in this clause is invoked for a particular view with view order index VOIdx, with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". + +When the decoding process specified in Annex H is applied, the process specified in this clause for Annex G is invoked for particular texture view and depth view with view order index VOIdx, with each "view component" being replaced by "texture view component" or "depth view component", "frame view component" being replaced by "texture frame view component" or "depth frame view component", and "field view component" being replaced by "texture field view component". During the invocation of the process for a particular texture view, only the texture view components of the particular view are considered and during the invocation of the process for a particular depth view, only the depth view components of the particular view are considered. + +When the decoding process specified in Annex G or Annex H is applied, the following process is specified for emptying frame buffers containing inter-view only reference components of the current access unit. By this process, frame buffers that contain view components of the current view with view order index VOIdx are not emptied, but frame buffers that contain inter-view only reference components of other views may be emptied. The process is specified as follows: + +- If the view order index VOIdx of the current view is equal to VOIdxMax, all frame buffers containing a frame or a complementary field pair or a non-paired field which are marked as "not needed for output" and "unused for reference" are emptied (without output), and the DPB fullness is decremented by the number of frame buffers emptied. + +NOTE 1 – At this stage of the process, all frame buffers that contain a frame or a complementary field pair or a non-paired field marked as "not needed for output" and "unused for reference" are frame buffers that contain an inter-view only reference component (of the current access unit and a view with view order index less than VOIdx) with OutputFlag equal to 0. + +- Otherwise (the view order index VOIdx of the current view is less than VOIdxMax), frame buffers containing a frame or a complementary field pair or a non-paired field for which both of the following conditions are true are emptied (without output), and the DPB fullness is decremented by the number of frame buffers emptied: + +- the frame or complementary field pair or non-paired field is marked as "not needed for output" and "unused for reference", + +NOTE 2 – At this stage of the process, all frame buffers that contain a frame or a complementary field pair or a non-paired field marked as "not needed for output" and "unused for reference" are frame buffers that contain an inter-view only reference component (of the current access unit and a view with view order index less than VOIdx) with OutputFlag equal to 0. + +- one of the following conditions is true: + - the current view component is a view component of an anchor picture and the view\_id of the frame or complementary field pair or non-paired field is not equal to any value of anchor\_ref\_IX[ k ][ j ], with X + +being equal to 0 or 1, k being any integer value greater than the view order index VOIdx of the current view, and j being any integer value in the range of 0 to Max( 0, num\_anchor\_refs\_IX[ k ] - 1 ), inclusive, + +- the current view component is not a view component of an anchor picture and the view\_id of the frame or complementary field pair or non-paired field is not equal to any value of non\_anchor\_ref\_IX[ k ][ j ], with X being equal to 0 or 1, k being any integer value greater than the view order index VOIdx of the current view, and j being any integer value in the range of 0 to Max( 0, num\_non\_anchor\_refs\_IX[ k ] - 1 ), inclusive. + +When the decoding process specified in Annex G or Annex H is applied, for the following processes specified in this clause, only view components of the particular view for which this clause is invoked are considered, and frame buffers containing view components of other views are not emptied. The DPB fullness represents the total number of non-empty frame buffers, including frame buffers that contain view components of other views. + +The removal of pictures from the DPB before possible insertion of the current picture proceeds as follows: + +- If the decoded picture is an IDR picture the following applies: + 1. All reference pictures in the DPB are marked as "unused for reference" as specified in clause 8.2.5 when a coded video sequence conforming to one or more of the profiles specified in Annex A is decoded by applying the decoding process specified in clauses 2 to 9, or as specified in clause F.8.2.4 when a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded by applying the decoding process specified in Annex F, or as specified in clause G.8.3 when a coded video sequence conforming to one or more of the profiles specified in Annex G is decoded by applying the decoding process specified in Annex G, or as specified in clause H.8.3 when a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying the decoding process specified in Annex H. + 2. When the IDR picture is not the first IDR picture decoded and the value of PicWidthInMbs or FrameHeightInMbs or max\_dec\_frame\_buffering derived from the active sequence parameter set is different from the value of PicWidthInMbs or FrameHeightInMbs or max\_dec\_frame\_buffering derived from the sequence parameter set that was active for the preceding picture, respectively, no\_output\_of\_prior\_pics\_flag is inferred to be equal to 1 by the HRD, regardless of the actual value of no\_output\_of\_prior\_pics\_flag. + +NOTE 3 – Decoder implementations should try to handle changes in the value of PicWidthInMbs or FrameHeightInMbs or max\_dec\_frame\_buffering more gracefully than the HRD. + +3. When no\_output\_of\_prior\_pics\_flag is equal to 1 or is inferred to be equal to 1, all frame buffers in the DPB are emptied without output of the pictures they contain, and DPB fullness is set to 0. +- Otherwise (the decoded picture is not an IDR picture), the decoded reference picture marking process is invoked as specified in clause 8.2.5 when a coded video sequence conforming to one or more of the profiles specified in Annex A is decoded by applying the decoding process specified in clauses 2 to 9, or as specified in clause F.8.2.4 when a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded by applying the decoding process specified in Annex F, or as specified in clause G.8.3 when a coded video sequence conforming to one or more of the profiles specified in Annex G is decoded by applying the decoding process specified in Annex G, or as specified in clause H.8.3 when a coded video sequence conforming to one or more of the profiles specified in Annex H is decoded by applying the decoding process specified in Annex H. Frame buffers containing a frame or a complementary field pair or a non-paired field which are marked as "not needed for output" and "unused for reference" are emptied (without output), and the DPB fullness is decremented by the number of frame buffers emptied. + +When the current picture has a memory\_management\_control\_operation equal to 5 or is an IDR picture for which no\_output\_of\_prior\_pics\_flag is not equal to 1 and is not inferred to be equal to 1, the following two steps are performed. + +1. Frame buffers containing a frame or a complementary field pair or a non-paired field which are marked as "not needed for output" and "unused for reference" are emptied (without output), and the DPB fullness is decremented by the number of frame buffers emptied. +2. All non-empty frame buffers in the DPB are emptied by repeatedly invoking the "bumping" process specified in clause C.4.5.3, and the DPB fullness is set to 0. + +#### C.4.5 Current decoded picture marking and storage + +When the decoding process specified in Annex G is applied, the process specified in this clause is invoked for a particular view with view order index VOIdx, with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". During the invocation of the process for a particular view, only view components of the particular view are considered and frame buffers containing view components of other views are not emptied. + +When the decoding process specified in Annex H is applied, the process specified in this clause for Annex G is invoked for particular texture view and depth view with view order index VOIdx, with each "view component" being replaced by + +"texture view component" or "depth view component", "frame view component" being replaced by "texture frame view component" or "depth frame view component", and "field view component" being replaced by "texture field view component". During the invocation of the process for a particular texture view, only the texture view components of the particular view are considered and during the invocation of the process for a particular depth view, only the depth view components of the particular view are considered and frame buffers containing view components of other views are not emptied. + +The DPB fullness represents the total number of non-empty frame buffers. When the decoding process specified in Annex G is applied, this includes frame buffers that contain view components of other views. When the decoding process specified in Annex H is applied, this includes frame buffers that contain texture or depth view components of other views. + +The marking and storage of the current decoded picture is specified as follows: + +- If the current picture is a reference picture, the storage and marking process for decoded reference pictures as specified in clause C.4.5.1 is invoked. +- Otherwise (the current picture is a non-reference picture), the storage and marking process for decoded non-reference pictures as specified in clause C.4.5.2 is invoked. + +#### **C.4.5.1 Storage and marking of a reference decoded picture into the DPB** + +The current picture is stored in the DPB as follows: + +- If the current decoded picture is the second field (in decoding order) of a complementary reference field pair, and the first field of the pair is still in the DPB, the current picture is stored in the same frame buffer as the first field of the pair and the following applies: + - If the current decoded picture has OutputFlag equal to 1, it is marked as "needed for output". + - Otherwise (the current decoded picture has OutputFlag equal to 0), it is marked as "not needed for output". +- Otherwise, the following operations are performed: + 1. When there is no empty frame buffer (i.e., DPB fullness is equal to DPB size), the "bumping" process specified in clause C.4.5.3 is invoked repeatedly until there is an empty frame buffer in which to store the current decoded picture. + 2. The current decoded picture is stored in an empty frame buffer, the DPB fullness is incremented by one, and the following applies: + - If the current decoded picture has OutputFlag equal to 1, it is marked as "needed for output". + - Otherwise (the current decoded picture has OutputFlag equal to 0), it is marked as "not needed for output". + +When the coded video sequence conforms to one or more of the profiles specified in Annex F and the decoding process specified in Annex F is applied and the current picture has store\_ref\_base\_pic\_flag equal to 1 (i.e., the current picture is associated with a reference base picture), the associated reference base picture is stored in the DPB as follows: + +- If the reference base picture is a second field (in decoding order) of a complementary reference base field pair, and the first field of the pair is still in the DPB, the reference base picture is stored in the same frame buffer as the first field of the pair and marked as "not needed for output". +- Otherwise, the following operations are performed: + 1. When there is no empty frame buffer (i.e., DPB fullness is equal to DPB size), the "bumping" process specified in clause C.4.5.3 is invoked repeatedly until there is an empty frame buffer in which to store the reference base picture. + 2. The reference base picture is stored in an empty frame buffer and marked as "not needed for output" and the DPB fullness is incremented by one. + +#### **C.4.5.2 Storage and marking of a non-reference decoded picture into the DPB** + +The current picture is associated with a variable StoreInterViewOnlyRefFlag, which is derived as follows: + +- If the decoding process specified in Annex G or Annex H is applied, the current view component has a view order index VOIdx less than VOIdxMax and inter\_view\_flag equal to 1, StoreInterViewOnlyRefFlag is set equal to 1. +- Otherwise, StoreInterViewOnlyRefFlag is set equal to 0. + +The current picture is stored in the DPB or output as follows: + +- If the current decoded picture is the second field (in decoding order) of a complementary non-reference field pair and the first field of the pair is still in the DPB, the current picture is stored in the same frame buffer as the first field of the pair and the following applies: + - If the current decoded picture has OutputFlag equal to 1, it is marked as "needed for output". + - Otherwise (the current decoded picture has OutputFlag equal to 0), it is marked as "not needed for output". +- Otherwise, if the current picture has OutputFlag equal to 0 and StoreInterViewOnlyRefFlag equal to 0, the DPB is not modified and the current picture is not output. +- Otherwise, if the current picture has StoreInterViewOnlyRefFlag equal to 1, the following operations are performed: + 1. When there is no empty frame buffer (i.e., DPB fullness is equal to DPB size), the "bumping" process specified in clause C.4.5.3 is invoked repeatedly until there is an empty frame buffer in which to store the current decoded picture. + 2. The current decoded picture is stored in an empty frame buffer, the DPB fullness is incremented by one, and the following applies: + - If the current decoded picture has OutputFlag equal to 1, it is marked as "needed for output". + - Otherwise (the current decoded picture has OutputFlag equal to 0), it is marked as "not needed for output". +- Otherwise, the following operations are performed repeatedly until the current decoded picture has been cropped and output or has been stored in the DPB: + - If there is no empty frame buffer (i.e., DPB fullness is equal to DPB size), the following applies: + - If the current picture does not have a lower value of PicOrderCnt( ) than all pictures in the DPB that are marked as "needed for output", the "bumping" process described in clause C.4.5.3 is performed. + - Otherwise (the current picture has a lower value of PicOrderCnt( ) than all pictures in the DPB that are marked as "needed for output"), the current picture is cropped, using the cropping rectangle specified in the active sequence parameter set for the picture and the cropped picture is output. + - Otherwise (there is an empty frame buffer, i.e., DPB fullness is less than DPB size), the current decoded picture is stored in an empty frame buffer and is marked as "needed for output", and the DPB fullness is incremented by one. + +#### C.4.5.3 "Bumping" process + +When the decoding process specified in Annex G is applied, the process specified in this clause is invoked for a particular view with view order index VOIdx, with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". During the invocation of the process for a particular view, only view components of the particular view are considered and frame buffers containing view components of other views are not emptied. + +When the decoding process specified in Annex H is applied, the process specified in this clause for Annex G is invoked for particular texture view and depth view with view order index VOIdx, with each "view component" being replaced by "texture view component" or "depth view component", "frame view component" being replaced by "texture frame view component" or "depth frame view component", and "field view component" being replaced by "texture field view component". During the invocation of the process for a particular texture view, only the texture view components of the particular view are considered while respective depth view components may be cropped and output too. During the invocation of the process for a particular depth view, only the depth view components of the particular view are considered and frame buffers containing view components of other views are not emptied. The DPB fullness represents the total number of non-empty frame buffers, including frame buffers that contain view components of other views, for the texture DPB or the depth DPB depending on whether the process is invoked for a texture view or a depth view, respectively. + +The DPB fullness represents the total number of non-empty frame buffers. When the decoding process specified in Annex G is applied, this includes frame buffers that contain view components of other views. When the decoding process specified in Annex H is applied, this includes frame buffers that contain texture or depth view components of other views. + +The "bumping" process is invoked in the following cases. + +- There is no empty frame buffer (i.e., DPB fullness is equal to DPB size) and an empty frame buffer is needed for storage of an inferred "non-existing" frame, as specified in clause C.4.2. +- The current picture is an IDR picture and no\_output\_of\_prior\_pics\_flag is not equal to 1 and is not inferred to be equal to 1, as specified in clause C.4.4. +- The current picture has memory\_management\_control\_operation equal to 5, as specified in clause C.4.4. + +- There is no empty frame buffer (i.e., DPB fullness is equal to DPB size) and an empty frame buffer is needed for storage of a decoded (non-IDR) reference picture or a reference base picture, as specified in clause C.4.5.1. +- There is no empty frame buffer (i.e., DPB fullness is equal to DPB size) and the current picture is a non-reference picture that is not the second field of a complementary non-reference field pair and the current picture has OutputFlag equal to 1 and there are pictures in the DPB that are marked as "needed for output" that precede the current non-reference picture in output order, as specified in clause C.4.5.2, so an empty buffer is needed for storage of the current picture. +- There is no empty frame buffer (i.e., DPB fullness is equal to DPB size) and the current picture is a non-reference picture that is not the second field of a complementary non-reference field pair and the current picture has StoreInterViewOnlyRefFlag equal to 1, as specified in clause C.4.5.2, so an empty buffer is needed for storage of the current picture. + +The "bumping" process consists of the following ordered steps: + +1. The picture or complementary reference field pair that is considered first for output is selected as follows: + - a. The frame buffer is selected that contains the picture having the smallest value of PicOrderCnt( ) of all pictures in the DPB marked as "needed for output". + - b. Depending on the frame buffer, the following applies: + - If this frame buffer contains a complementary non-reference field pair with both fields marked as "needed for output" and both fields have the same PicOrderCnt( ), the first of these two fields in decoding order is considered first for output. + - Otherwise, if this frame buffer contains a complementary reference field pair with both fields marked as "needed for output" and both fields have the same PicOrderCnt( ), the entire complementary reference field pair is considered first for output. + +NOTE – When the two fields of a complementary reference field pair have the same value of PicOrderCnt( ), this "bumping" process will output these pictures together, although the two fields have different output times from a decoder that satisfies output timing conformance criteria (as specified in clause C.2.2). + - Otherwise, the picture in this frame buffer that has the smallest value of PicOrderCnt( ) is considered first for output. +2. Depending on whether a single picture or a complementary reference field pair is considered for output, the following applies: + - If a single picture is considered first for output, this picture is cropped, using the cropping rectangle specified in the active sequence parameter set for the picture, the cropped picture is output, and the picture is marked as "not needed for output". + - Otherwise (a complementary reference field pair is considered first for output), the two fields of the complementary reference field pair are both cropped, using the cropping rectangle specified in the active sequence parameter set for the pictures, the two fields of the complementary reference field pair are output together, and both fields of the complementary reference field pair are marked as "not needed for output". +3. When there is a single depth view component or a complementary depth view component pair having the same values of view\_id and PicOrderCnt( ) as the single picture or complementary reference field pair considered for output, the single depth view component or complementary depth view component pair are output as in step 2. +4. The frame buffer that included the picture or complementary reference field pair that was cropped and output is checked, and when any of the following conditions are true, the frame buffer is emptied and the DPB fullness is decremented by 1: + - The frame buffer contains a non-reference non-paired field. + - The frame buffer contains a non-reference frame. + - The frame buffer contains a complementary non-reference field pair with both fields marked as "not needed for output". + - The frame buffer contains a non-paired reference field marked as "unused for reference". + - The frame buffer contains a reference frame with both fields marked as "unused for reference". + - The frame buffer contains a complementary reference field pair with both fields marked as "unused for reference" and "not needed for output". + +## Annex D + +### Supplemental enhancement information + +(This annex forms an integral part of this Recommendation | International Standard.) + +This annex specifies syntax and semantics for SEI message payloads. + +SEI messages assist in processes related to decoding, display or other purposes. However, SEI messages are not required for constructing the luma or chroma samples by the decoding process. Conforming decoders are not required to process this information for output order conformance to this Recommendation | International Standard (see Annex C for the specification of conformance). Some SEI message information is required to check bitstream conformance and for output timing decoder conformance. + +In Annex D, specification for presence of SEI messages are also satisfied when those messages (or some subset of them) are conveyed to decoders (or to the HRD) by other means not specified by this Recommendation | International Standard. When present in the bitstream, SEI messages shall obey the syntax and semantics specified in clauses 7.3.2.3 and 7.4.2.3 and this annex. When the content of an SEI message is conveyed for the application by some means other than presence within the bitstream, the representation of the content of the SEI message is not required to use the same syntax specified in this annex. For the purpose of counting bits, only the appropriate bits that are actually present in the bitstream are counted. + +#### D.1 SEI payload syntax + +##### D.1.1 General SEI message syntax + +| sei_payload( payloadType, payloadSize ) { | C | Descriptor | +|-----------------------------------------------|---|------------| +| if( payloadType == 0 ) | | | +| buffering_period( payloadSize ) | 5 | | +| else if( payloadType == 1 ) | | | +| pic_timing( payloadSize ) | 5 | | +| else if( payloadType == 2 ) | | | +| pan_scan_rect( payloadSize ) | 5 | | +| else if( payloadType == 3 ) | | | +| filler_payload( payloadSize ) | 5 | | +| else if( payloadType == 4 ) | | | +| user_data_registered_itu_t_t35( payloadSize ) | 5 | | +| else if( payloadType == 5 ) | | | +| user_data_unregistered( payloadSize ) | 5 | | +| else if( payloadType == 6 ) | | | +| recovery_point( payloadSize ) | 5 | | +| else if( payloadType == 7 ) | | | +| dec_ref_pic_marking_repetition( payloadSize ) | 5 | | +| else if( payloadType == 8 ) | | | +| spare_pic( payloadSize ) | 5 | | +| else if( payloadType == 9 ) | | | +| scene_info( payloadSize ) | 5 | | +| else if( payloadType == 10 ) | | | +| sub_seq_info( payloadSize ) | 5 | | +| else if( payloadType == 11 ) | | | +| sub_seq_layer_characteristics( payloadSize ) | 5 | | +| else if( payloadType == 12 ) | | | +| sub_seq_characteristics( payloadSize ) | 5 | | + +| | | | +|-------------------------------------------------------------------------|---|--| +| else if( payloadType == 13 ) | | | +| full_frame_freeze( payloadSize ) | 5 | | +| else if( payloadType == 14 ) | | | +| full_frame_freeze_release( payloadSize ) | 5 | | +| else if( payloadType == 15 ) | | | +| full_frame_snapshot( payloadSize ) | 5 | | +| else if( payloadType == 16 ) | | | +| progressive_refinement_segment_start( payloadSize ) | 5 | | +| else if( payloadType == 17 ) | | | +| progressive_refinement_segment_end( payloadSize ) | 5 | | +| else if( payloadType == 18 ) | | | +| motion_constrained_slice_group_set( payloadSize ) | 5 | | +| else if( payloadType == 19 ) | | | +| film_grain_characteristics( payloadSize ) | 5 | | +| else if( payloadType == 20 ) | | | +| deblocking_filter_display_preference( payloadSize ) | 5 | | +| else if( payloadType == 21 ) | | | +| stereo_video_info( payloadSize ) | 5 | | +| else if( payloadType == 22 ) | | | +| post_filter_hint( payloadSize ) | 5 | | +| else if( payloadType == 23 ) | | | +| tone_mapping_info( payloadSize ) | 5 | | +| else if( payloadType == 24 ) | | | +| scalability_info( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 25 ) | | | +| sub_pic_scalable_layer( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 26 ) | | | +| non_required_layer_rep( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 27 ) | | | +| priority_layer_info( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 28 ) | | | +| layers_not_present( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 29 ) | | | +| layer_dependency_change( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 30 ) | | | +| scalable_nesting( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 31 ) | | | +| base_layer_temporal_hrd( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 32 ) | | | +| quality_layer_integrity_check( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 33 ) | | | +| redundant_pic_property( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 34 ) | | | +| tl0_dep_rep_index( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 35 ) | | | +| tl_switching_point( payloadSize ) /* specified in Annex F */ | 5 | | +| else if( payloadType == 36 ) | | | +| parallel_decoding_info( payloadSize ) /* specified in Annex G */ | 5 | | + +| | | | +|-----------------------------------------------------------------------------------------|---|--| +| else if( payloadType == 37 ) | | | +| mvc_scalable_nesting( payloadSize ) /* specified in Annex G */ | 5 | | +| else if( payloadType == 38 ) | | | +| view_scalability_info( payloadSize ) /* specified in Annex G */ | 5 | | +| else if( payloadType == 39 ) | | | +| multiview_scene_info( payloadSize ) /* specified in Annex G */ | 5 | | +| else if( payloadType == 40 ) | | | +| multiview_acquisition_info( payloadSize ) /* specified in Annex G */ | 5 | | +| else if( payloadType == 41 ) | | | +| non_required_view_component( payloadSize ) /* specified in Annex G */ | 5 | | +| else if( payloadType == 42 ) | | | +| view_dependency_change( payloadSize ) /* specified in Annex G */ | 5 | | +| else if( payloadType == 43 ) | | | +| operation_points_not_present( payloadSize ) /* specified in Annex G */ | 5 | | +| else if( payloadType == 44 ) | | | +| base_view_temporal_hrd( payloadSize ) /* specified in Annex G */ | 5 | | +| else if( payloadType == 45 ) | | | +| frame_packing_arrangement( payloadSize ) | 5 | | +| else if( payloadType == 46 ) | | | +| multiview_view_position( payloadSize ) /* specified in Annex G */ | 5 | | +| else if( payloadType == 47 ) | | | +| display_orientation( payloadSize ) | 5 | | +| else if( payloadType == 48 ) | | | +| mvcd_scalable_nesting( payloadSize ) /* specified in Annex H */ | 5 | | +| else if( payloadType == 49 ) | | | +| mvcd_view_scalability_info( payloadSize ) /* specified in Annex H */ | 5 | | +| else if( payloadType == 50 ) | | | +| depth_representation_info( payloadSize ) /* specified in Annex H */ | 5 | | +| else if( payloadType == 51 ) | | | +| three_dimensional_reference_displays_info( payloadSize )
/* specified in Annex H */ | 5 | | +| else if( payloadType == 52 ) | | | +| depth_timing( payloadSize ) /* specified in Annex H */ | 5 | | +| else if( payloadType == 53 ) | | | +| depth_sampling_info( payloadSize ) /* specified in Annex H */ | 5 | | +| else if( payloadType == 54 ) | | | +| constrained_depth_parameter_set_identifier( payloadSize )
/* specified in Annex I */ | 5 | | +| else if( payloadType == 56 ) | | | +| green_metadata( payloadSize ) /* specified in ISO/IEC 23001-11 */ | 5 | | +| else if( payloadType == 137 ) | | | +| mastering_display_colour_volume( payloadSize ) | 5 | | +| else if( payloadType == 142 ) | | | +| colour_remapping_info( payloadSize ) | 5 | | +| else if( payloadType == 144 ) | | | +| content_light_level_info( payloadSize ) | 5 | | +| else if( payloadType == 147 ) | | | +| alternative_transfer_characteristics( payloadSize ) | 5 | | + +Rec. ITU-T H.264 (V15) (08/2024)     335 + +336 Rec. ITU-T H.264 (V15) (08/2024) + +| | | | +|-----------------------------------------------------------------------------------------------------|---|------| +| else if( payloadType == 148 ) | | | +| ambient_viewing_environment( payloadSize ) | 5 | | +| else if( payloadType == 149 ) | | | +| content_colour_volume( payloadSize ) | 5 | | +| else if( payloadType == 150 ) | | | +| equirectangular_projection( payloadSize ) | 5 | | +| else if( payloadType == 151 ) | | | +| cubemap_projection( payloadSize ) | 5 | | +| else if( payloadType == 154 ) | | | +| sphere_rotation( payloadSize ) | 5 | | +| else if( payloadType == 155 ) | | | +| regionwise_packing( payloadSize ) | 5 | | +| else if( payloadType == 156 ) | | | +| omni_viewport( payloadSize ) | 5 | | +| else if( payloadType == 181 ) | | | +| alternative_depth_info( payloadSize ) /* specified in Annex H */ | 5 | | +| else if( payloadType == 200 ) | | | +| sei_manifest( payloadSize ) | 5 | | +| else if( payloadType == 201 ) | | | +| sei_prefix_indication( payloadSize ) | 5 | | +| else if( payloadType == 202 ) | | | +| annotated_regions( payloadSize ) /* specified in Rec. ITU-T H.274 ISO/IEC 23002-7 */ | 5 | | +| else if( payloadType == 210 ) | | | +| nn_post_filter_characteristics( payloadSize ) /* specified in Rec. ITU-T H.274 ISO/IEC 23002-7 */ | 5 | | +| else if( payloadType == 211 ) | | | +| nn_post_filter_activation( payloadSize ) /* specified in Rec. ITU-T H.274 ISO/IEC 23002-7 */ | 5 | | +| else if( payloadType == 212 ) | | | +| phase_indication( payloadSize ) /* specified in Rec. ITU-T H.274 ISO/IEC 23002-7 */ | 5 | | +| else if( payloadType == 205 ) | | | +| shutter_interval_info( payloadSize ) | 5 | | +| else | | | +| reserved_sei_message( payloadSize ) | 5 | | +| if( !byte_aligned( ) ) { | | | +| bit_equal_to_one /* equal to 1 */ | 5 | f(1) | +| while( !byte_aligned( ) ) | | | +| bit_equal_to_zero /* equal to 0 */ | 5 | f(1) | +| } | | | +| } | | | + +#### D.1.2 Buffering period SEI message syntax + +| buffering_period( payloadSize ) { | C | Descriptor | +|------------------------------------------------------------------------|---|------------| +| seq_parameter_set_id | 5 | ue(v) | +| if( NalHrdBpPresentFlag ) | | | +| for( SchedSelIdx = 0; SchedSelIdx <= cpb_cnt_minus1; SchedSelIdx++ ) { | | | +| initial_cpb_removal_delay [ SchedSelIdx ] | 5 | u(v) | +| initial_cpb_removal_delay_offset [ SchedSelIdx ] | 5 | u(v) | +| } | | | +| if( VclHrdBpPresentFlag ) | | | +| for( SchedSelIdx = 0; SchedSelIdx <= cpb_cnt_minus1; SchedSelIdx++ ) { | | | +| initial_cpb_removal_delay [ SchedSelIdx ] | 5 | u(v) | +| initial_cpb_removal_delay_offset [ SchedSelIdx ] | 5 | u(v) | +| } | | | +| } | | | + +#### D.1.3 Picture timing SEI message syntax + +| pic_timing( payloadSize ) { | C | Descriptor | +|-------------------------------------|---|------------| +| if( CpbDpbDelaysPresentFlag ) { | | | +| cpb_removal_delay | 5 | u(v) | +| dpb_output_delay | 5 | u(v) | +| } | | | +| if( pic_struct_present_flag ) { | | | +| pic_struct | 5 | u(4) | +| for( i = 0; i < NumClockTS; i++ ) { | | | +| clock_timestamp_flag [ i ] | 5 | u(1) | +| if( clock_timestamp_flag[ i ] ) { | | | +| ct_type | 5 | u(2) | +| nuit_field_based_flag | 5 | u(1) | +| counting_type | 5 | u(5) | +| full_timestamp_flag | 5 | u(1) | +| discontinuity_flag | 5 | u(1) | +| cnt_dropped_flag | 5 | u(1) | +| n_frames | 5 | u(8) | +| if( full_timestamp_flag ) { | | | +| seconds_value /* 0..59 */ | 5 | u(6) | +| minutes_value /* 0..59 */ | 5 | u(6) | +| hours_value /* 0..23 */ | 5 | u(5) | +| } else { | | | +| seconds_flag | 5 | u(1) | +| if( seconds_flag ) { | | | + +| | | | +|----------------------------------------|---|------| +| seconds_value /* range 0..59 */ | 5 | u(6) | +| minutes_flag | 5 | u(1) | +| if( minutes_flag ) { | | | +| minutes_value /* 0..59 */ | 5 | u(6) | +| hours_flag | 5 | u(1) | +| if( hours_flag ) | | | +| hours_value /* 0..23 */ | 5 | u(5) | +| } | | | +| } | | | +| if( time_offset_length > 0 ) | | | +| time_offset | 5 | i(v) | +| } | | | +| } | | | +| } | | | +| } | | | + +#### D.1.4 Pan-scan rectangle SEI message syntax + +| pan_scan_rect( payloadSize ) { | C | Descriptor | +|-----------------------------------------------|---|------------| +| pan_scan_rect_id | 5 | ue(v) | +| pan_scan_rect_cancel_flag | 5 | u(1) | +| if( !pan_scan_rect_cancel_flag ) { | | | +| pan_scan_cnt_minus1 | 5 | ue(v) | +| for( i = 0; i <= pan_scan_cnt_minus1; i++ ) { | | | +| pan_scan_rect_left_offset[ i ] | 5 | se(v) | +| pan_scan_rect_right_offset[ i ] | 5 | se(v) | +| pan_scan_rect_top_offset[ i ] | 5 | se(v) | +| pan_scan_rect_bottom_offset[ i ] | 5 | se(v) | +| } | | | +| pan_scan_rect_repetition_period | 5 | ue(v) | +| } | | | +| } | | | + +#### D.1.5 Filler payload SEI message syntax + +| filler_payload( payloadSize ) { | C | Descriptor | +|------------------------------------|---|------------| +| for( k = 0; k < payloadSize; k++ ) | | | +| ff_byte /* equal to 0xFF */ | 5 | f(8) | +| } | | | + +**D.1.6 User data registered by Rec. ITU-T T.35 SEI message syntax** + +| | | | +|-------------------------------------------------|----------|-------------------| +| user_data_registered_itu_t_t35( payloadSize ) { | C | Descriptor | +| itu_t_t35_country_code | 5 | b(8) | +| if( itu_t_t35_country_code != 0xFF ) | | | +| i = 1 | | | +| else { | | | +| itu_t_t35_country_code_extension_byte | 5 | b(8) | +| i = 2 | | | +| } | | | +| do { | | | +| itu_t_t35_payload_byte | 5 | b(8) | +| i++ | | | +| } while( i < payloadSize ) | | | +| } | | | + +**D.1.7 User data unregistered SEI message syntax** + +| | | | +|-----------------------------------------|----------|-------------------| +| user_data_unregistered( payloadSize ) { | C | Descriptor | +| uuid_iso_iec_11578 | 5 | u(128) | +| for( i = 16; i < payloadSize; i++ ) | | | +| user_data_payload_byte | 5 | b(8) | +| } | | | + +**D.1.8 Recovery point SEI message syntax** + +| | | | +|---------------------------------|----------|-------------------| +| recovery_point( payloadSize ) { | C | Descriptor | +| recovery_frame_cnt | 5 | ue(v) | +| exact_match_flag | 5 | u(1) | +| broken_link_flag | 5 | u(1) | +| changing_slice_group_idc | 5 | u(2) | +| } | | | + +**D.1.9 Decoded reference picture marking repetition SEI message syntax** + +| | | | +|-------------------------------------------------|----------|-------------------| +| dec_ref_pic_marking_repetition( payloadSize ) { | C | Descriptor | +| original_idr_flag | 5 | u(1) | +| original_frame_num | 5 | ue(v) | +| if( !frame_mbs_only_flag ) { | | | +| original_field_pic_flag | 5 | u(1) | +| if( original_field_pic_flag ) | | | +| original_bottom_field_flag | 5 | u(1) | +| } | | | +| dec_ref_pic_marking( ) | 5 | | +| } | | | + +**D.1.10 Spare picture SEI message syntax** + +| | | | +|----------------------------------------------------|----------|-------------------| +| spare_pic( payloadSize ) { | C | Descriptor | +| target_frame_num | 5 | ue(v) | +| spare_field_flag | 5 | u(1) | +| if( spare_field_flag ) | | | +| target_bottom_field_flag | 5 | u(1) | +| num_spare_pics_minus1 | 5 | ue(v) | +| for( i = 0; i < num_spare_pics_minus1 + 1; i++ ) { | | | +| delta_spare_frame_num[ i ] | 5 | ue(v) | +| if( spare_field_flag ) | | | +| spare_bottom_field_flag[ i ] | 5 | u(1) | +| spare_area_idc[ i ] | 5 | ue(v) | +| if( spare_area_idc[ i ] == 1 ) | | | +| for( j = 0; j < PicSizeInMapUnits; j++ ) | | | +| spare_unit_flag[ i ][ j ] | 5 | u(1) | +| else if( spare_area_idc[ i ] == 2 ) { | | | +| mapUnitCnt = 0 | | | +| for( j=0; mapUnitCnt < PicSizeInMapUnits; j++ ) { | | | +| zero_run_length[ i ][ j ] | 5 | ue(v) | +| mapUnitCnt += zero_run_length[ i ][ j ] + 1 | | | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | + +#### D.1.11 Scene information SEI message syntax + +| | | | +|---------------------------------|---|------------| +| scene_info( payloadSize ) { | C | Descriptor | +| scene_info_present_flag | 5 | u(1) | +| if( scene_info_present_flag ) { | | | +| scene_id | 5 | ue(v) | +| scene_transition_type | 5 | ue(v) | +| if( scene_transition_type > 3 ) | | | +| second_scene_id | 5 | ue(v) | +| } | | | +| } | | | + +#### D.1.12 Sub-sequence information SEI message syntax + +| | | | +|---------------------------------|---|------------| +| sub_seq_info( payloadSize ) { | C | Descriptor | +| sub_seq_layer_num | 5 | ue(v) | +| sub_seq_id | 5 | ue(v) | +| first_ref_pic_flag | 5 | u(1) | +| leading_non_ref_pic_flag | 5 | u(1) | +| last_pic_flag | 5 | u(1) | +| sub_seq_frame_num_flag | 5 | u(1) | +| if( sub_seq_frame_num_flag ) | | | +| sub_seq_frame_num | 5 | ue(v) | +| } | | | + +#### D.1.13 Sub-sequence layer characteristics SEI message syntax + +| | | | +|-----------------------------------------------------------------|---|------------| +| sub_seq_layer_characteristics( payloadSize ) { | C | Descriptor | +| num_sub_seq_layers_minus1 | 5 | ue(v) | +| for( layer = 0; layer <= num_sub_seq_layers_minus1; layer++ ) { | | | +| accurate_statistics_flag | 5 | u(1) | +| average_bit_rate | 5 | u(16) | +| average_frame_rate | 5 | u(16) | +| } | | | +| } | | | + +#### D.1.14 Sub-sequence characteristics SEI message syntax + +| | | | +|-------------------------------------------------|---|------------| +| sub_seq_characteristics( payloadSize ) { | C | Descriptor | +| sub_seq_layer_num | 5 | ue(v) | +| sub_seq_id | 5 | ue(v) | +| duration_flag | 5 | u(1) | +| if( duration_flag) | | | +| sub_seq_duration | 5 | u(32) | +| average_rate_flag | 5 | u(1) | +| if( average_rate_flag ) { | | | +| accurate_statistics_flag | 5 | u(1) | +| average_bit_rate | 5 | u(16) | +| average_frame_rate | 5 | u(16) | +| } | | | +| num_referenced_subseqs | 5 | ue(v) | +| for( n = 0; n < num_referenced_subseqs; n++ ) { | | | +| ref_sub_seq_layer_num | 5 | ue(v) | +| ref_sub_seq_id | 5 | ue(v) | +| ref_sub_seq_direction | 5 | u(1) | +| } | | | +| } | | | + +#### D.1.15 Full-frame freeze SEI message syntax + +| | | | +|--------------------------------------------|---|------------| +| full_frame_freeze( payloadSize ) { | C | Descriptor | +| full_frame_freeze_repetition_period | 5 | ue(v) | +| } | | | + +#### D.1.16 Full-frame freeze release SEI message syntax + +| | | | +|--------------------------------------------|---|------------| +| full_frame_freeze_release( payloadSize ) { | C | Descriptor | +| } | | | + +#### D.1.17 Full-frame snapshot SEI message syntax + +| | | | +|--------------------------------------|---|------------| +| full_frame_snapshot( payloadSize ) { | C | Descriptor | +| snapshot_id | 5 | ue(v) | +| } | | | + +#### D.1.18 Progressive refinement segment start SEI message syntax + +| progressive_refinement_segment_start( payloadSize ) { | C | Descriptor | +|-------------------------------------------------------|---|------------| +| progressive_refinement_id | 5 | ue(v) | +| num_refinement_steps_minus1 | 5 | ue(v) | +| } | | | + +#### D.1.19 Progressive refinement segment end SEI message syntax + +| progressive_refinement_segment_end( payloadSize ) { | C | Descriptor | +|-----------------------------------------------------|---|------------| +| progressive_refinement_id | 5 | ue(v) | +| } | | | + +#### D.1.20 Motion-constrained slice group set SEI message syntax + +| motion_constrained_slice_group_set( payloadSize ) { | C | Descriptor | +|--------------------------------------------------------|---|------------| +| num_slice_groups_in_set_minus1 | 5 | ue(v) | +| if( num_slice_groups_minus1 > 0 ) | | | +| for( i = 0; i <= num_slice_groups_in_set_minus1; i++ ) | | | +| slice_group_id[ i ] | 5 | u(v) | +| exact_sample_value_match_flag | 5 | u(1) | +| pan_scan_rect_flag | 5 | u(1) | +| if( pan_scan_rect_flag ) | | | +| pan_scan_rect_id | 5 | ue(v) | +| } | | | + +#### D.1.21 Film grain characteristics SEI message syntax + +| film_grain_characteristics( payloadSize ) { | C | Descriptor | +|---------------------------------------------------------------|---|------------| +| film_grain_characteristics_cancel_flag | 5 | u(1) | +| if( !film_grain_characteristics_cancel_flag ) { | | | +| film_grain_model_id | 5 | u(2) | +| separate_colour_description_present_flag | 5 | u(1) | +| if( separate_colour_description_present_flag ) { | | | +| film_grain_bit_depth_luma_minus8 | 5 | u(3) | +| film_grain_bit_depth_chroma_minus8 | 5 | u(3) | +| film_grain_full_range_flag | 5 | u(1) | +| film_grain_colour_primaries | 5 | u(8) | +| film_grain_transfer_characteristics | 5 | u(8) | +| film_grain_matrix_coefficients | 5 | u(8) | +| } | | | +| blending_mode_id | 5 | u(2) | +| log2_scale_factor | 5 | u(4) | +| for( c = 0; c < 3; c++ ) | | | +| comp_model_present_flag[ c ] | 5 | u(1) | +| for( c = 0; c < 3; c++ ) | | | +| if( comp_model_present_flag[ c ] ) { | | | +| num_intensity_intervals_minus1[ c ] | 5 | u(8) | +| num_model_values_minus1[ c ] | 5 | u(3) | +| for( i = 0; i <= num_intensity_intervals_minus1[ c ]; i++ ) { | | | +| intensity_interval_lower_bound[ c ][ i ] | 5 | u(8) | +| intensity_interval_upper_bound[ c ][ i ] | 5 | u(8) | +| for( j = 0; j <= num_model_values_minus1[ c ]; j++ ) | | | +| comp_model_value[ c ][ i ][ j ] | 5 | se(v) | +| } | | | +| } | | | +| film_grain_characteristics_repetition_period | 5 | ue(v) | +| } | | | +| } | | | + +#### D.1.22 Deblocking filter display preference SEI message syntax + +| deblocking_filter_display_preference( payloadSize ) { | C | Descriptor | +|--------------------------------------------------------|---|------------| +| deblocking_display_preference_cancel_flag | 5 | u(1) | +| if( !deblocking_display_preference_cancel_flag ) { | | | +| display_prior_to_deblocking_preferred_flag | 5 | u(1) | +| dec_frame_buffering_constraint_flag | 5 | u(1) | +| deblocking_display_preference_repetition_period | 5 | ue(v) | +| } | | | +| } | | | + +D.1.23 Stereo video information SEI message syntax + +| stereo_video_info( payloadSize ) { | C | Descriptor | +|----------------------------------------|---|------------| +| field_views_flag | 5 | u(1) | +| if( field_views_flag ) | | | +| top_field_is_left_view_flag | 5 | u(1) | +| else { | | | +| current_frame_is_left_view_flag | 5 | u(1) | +| next_frame_is_second_view_flag | 5 | u(1) | +| } | | | +| left_view_self_contained_flag | 5 | u(1) | +| right_view_self_contained_flag | 5 | u(1) | +| } | | | + +D.1.24 Post-filter hint SEI message syntax + +| post_filter_hint( payloadSize ) { | C | Descriptor | +|----------------------------------------------|---|------------| +| filter_hint_size_y | 5 | ue(v) | +| filter_hint_size_x | 5 | ue(v) | +| filter_hint_type | 5 | u(2) | +| for( cldx = 0; cldx < 3; cldx++ ) | | | +| for( cy = 0; cy < filter_hint_size_y; cy++ ) | | | +| for( cx = 0; cx < filter_hint_size_x; cx++ ) | | | +| filter_hint_value[ cldx ][ cx ][ cy ] | 5 | se(v) | +| additional_extension_flag | 5 | u(1) | +| } | | | + +D.1.25 Tone mapping information SEI message syntax + +| tone_mapping_info( payloadSize ) { | C | Descriptor | +|--------------------------------------------------|---|------------| +| tone_map_id | 5 | ue(v) | +| tone_map_cancel_flag | 5 | u(1) | +| if( !tone_map_cancel_flag ) { | | | +| tone_map_repetition_period | 5 | ue(v) | +| coded_data_bit_depth | 5 | u(8) | +| target_bit_depth | 5 | u(8) | +| tone_map_model_id | 5 | ue(v) | +| if( tone_map_model_id == 0 ) { | | | +| min_value | 5 | u(32) | +| max_value | 5 | u(32) | +| } | | | +| if( tone_map_model_id == 1 ) { | | | +| sigmoid_midpoint | 5 | u(32) | +| sigmoid_width | 5 | u(32) | +| } | | | +| if( tone_map_model_id == 2 ) | | | +| for( i = 0; i < ( 1 << target_bit_depth ); i++ ) | | | +| start_of_coded_interval[ i ] | 5 | u(v) | +| if( tone_map_model_id == 3 ) { | | | +| num_pivots | 5 | u(16) | +| for( i=0; i < num_pivots; i++ ) { | | | +| coded_pivot_value[ i ] | 5 | u(v) | +| target_pivot_value[ i ] | 5 | u(v) | +| } | | | +| } | | | +| if( tone_map_model_id == 4 ) { | | | +| camera_iso_speed_idc | 5 | u(8) | +| if( camera_iso_speed_idc == Extended_ISO ) | | | +| camera_iso_speed_value | 5 | u(32) | +| exposure_index_idc | 5 | u(8) | +| if( exposure_index_idc == Extended_ISO ) | | | +| exposure_index_value | 5 | u(32) | +| exposure_compensation_value_sign_flag | 5 | u(1) | +| exposure_compensation_value_numerator | 5 | u(16) | +| exposure_compensation_value_denom_idc | 5 | u(16) | +| ref_screen_luminance_white | 5 | u(32) | +| extended_range_white_level | 5 | u(32) | +| nominal_black_level_luma_code_value | 5 | u(16) | +| nominal_white_level_luma_code_value | 5 | u(16) | +| extended_white_level_luma_code_value | 5 | u(16) | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | + +#### D.1.26 Frame packing arrangement SEI message syntax + +| frame_packing_arrangement( payloadSize ) { | C | Descriptor | +|---------------------------------------------------------------------------|---|------------| +| frame_packing_arrangement_id | 5 | ue(v) | +| frame_packing_arrangement_cancel_flag | 5 | u(1) | +| if( !frame_packing_arrangement_cancel_flag ) { | | | +| frame_packing_arrangement_type | 5 | u(7) | +| quincunx_sampling_flag | 5 | u(1) | +| content_interpretation_type | 5 | u(6) | +| spatial_flipping_flag | 5 | u(1) | +| frame0_flipped_flag | 5 | u(1) | +| field_views_flag | 5 | u(1) | +| current_frame_is_frame0_flag | 5 | u(1) | +| frame0_self_contained_flag | 5 | u(1) | +| frame1_self_contained_flag | 5 | u(1) | +| if( !quincunx_sampling_flag &&
frame_packing_arrangement_type != 5 ) { | | | +| frame0_grid_position_x | 5 | u(4) | +| frame0_grid_position_y | 5 | u(4) | +| frame1_grid_position_x | 5 | u(4) | +| frame1_grid_position_y | 5 | u(4) | +| } | | | +| frame_packing_arrangement_reserved_byte | 5 | u(8) | +| frame_packing_arrangement_repetition_period | 5 | ue(v) | +| } | | | +| frame_packing_arrangement_extension_flag | 5 | u(1) | +| } | | | + +#### D.1.27 Display orientation SEI message syntax + +| display_orientation( payloadSize ) { | C | Descriptor | +|----------------------------------------------|---|------------| +| display_orientation_cancel_flag | 5 | u(1) | +| if( !display_orientation_cancel_flag ) { | | | +| hor_flip | 5 | u(1) | +| ver_flip | 5 | u(1) | +| anticlockwise_rotation | 5 | u(16) | +| display_orientation_repetition_period | 5 | ue(v) | +| display_orientation_extension_flag | 5 | u(1) | +| } | | | +| } | | | + +#### D.1.28 Green metadata SEI message syntax + +The syntax for this SEI message is specified in ISO/IEC 23001-11 (Green metadata), which facilitates reduced power consumption in decoders, encoders, displays, and in media selection. + +#### D.1.29 Mastering display colour volume SEI message syntax + +| mastering_display_colour_volume( payloadSize ) { | C | Descriptor | +|--------------------------------------------------|---|------------| +| for( c = 0; c < 3; c++ ) { | | | +| display_primaries_x[ c ] | 5 | u(16) | +| display_primaries_y[ c ] | 5 | u(16) | +| } | | | +| white_point_x | 5 | u(16) | +| white_point_y | 5 | u(16) | +| max_display_mastering_luminance | 5 | u(32) | +| min_display_mastering_luminance | 5 | u(32) | +| } | | | + +**D.1.30 Colour remapping information SEI message syntax** + +| colour_remapping_info( payloadSize ) { | C | Descriptor | +|--------------------------------------------------------|----------|-------------------| +| colour_remap_id | 5 | ue(v) | +| colour_remap_cancel_flag | 5 | u(1) | +| if( !colour_remap_cancel_flag ) { | | | +| colour_remap_repetition_period | 5 | ue(v) | +| colour_remap_video_signal_info_present_flag | 5 | u(1) | +| if( colour_remap_video_signal_info_present_flag ) { | | | +| colour_remap_full_range_flag | 5 | u(1) | +| colour_remap_primaries | 5 | u(8) | +| colour_remap_transfer_function | 5 | u(8) | +| colour_remap_matrix_coefficients | 5 | u(8) | +| } | | | +| colour_remap_input_bit_depth | 5 | u(8) | +| colour_remap_output_bit_depth | 5 | u(8) | +| for( c = 0; c < 3; c++ ) { | | | +| pre_lut_num_val_minus1[ c ] | 5 | u(8) | +| if( pre_lut_num_val_minus1[ c ] > 0 ) | | | +| for( i = 0; i <= pre_lut_num_val_minus1[ c ]; i++ ) { | | | +| pre_lut_coded_value[ c ][ i ] | 5 | u(v) | +| pre_lut_target_value[ c ][ i ] | 5 | u(v) | +| } | | | +| } | | | +| colour_remap_matrix_present_flag | 5 | u(1) | +| if( colour_remap_matrix_present_flag ) { | | | +| log2_matrix_denom | 5 | u(4) | +| for( c = 0; c < 3; c++ ) | | | +| for( i = 0; i < 3; i++ ) | | | +| colour_remap_coeffs[ c ][ i ] | 5 | se(v) | +| } | | | +| for( c = 0; c < 3; c++ ) { | | | +| post_lut_num_val_minus1[ c ] | 5 | u(8) | +| if( post_lut_num_val_minus1[ c ] > 0 ) | | | +| for( i = 0; i <= post_lut_num_val_minus1[ c ]; i++ ) { | | | +| post_lut_coded_value[ c ][ i ] | 5 | u(v) | +| post_lut_target_value[ c ][ i ] | 5 | u(v) | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | + +**D.1.31 Content light level information SEI message syntax** + +| | | | +|-------------------------------------------|----------|-------------------| +| content_light_level_info( payloadSize ) { | C | Descriptor | +| max_content_light_level | 5 | u(16) | +| max_pic_average_light_level | 5 | u(16) | +| } | | | + +**D.1.32 Alternative transfer characteristics SEI message syntax** + +| | | | +|-------------------------------------------------------|----------|-------------------| +| alternative_transfer_characteristics( payloadSize ) { | C | Descriptor | +| preferred_transfer_characteristics | 5 | u(8) | +| } | | | + +**D.1.33 Content colour volume SEI message syntax** + +| | | | +|--------------------------------------------|----------|-------------------| +| content_colour_volume( payloadSize ) { | C | Descriptor | +| ccv_cancel_flag | 5 | u(1) | +| if( !ccv_cancel_flag ) { | | | +| ccv_persistence_flag | 5 | u(1) | +| ccv_primaries_present_flag | 5 | u(1) | +| ccv_min_luminance_value_present_flag | 5 | u(1) | +| ccv_max_luminance_value_present_flag | 5 | u(1) | +| ccv_avg_luminance_value_present_flag | 5 | u(1) | +| ccv_reserved_zero_2bits | 5 | u(2) | +| if( ccv_primaries_present_flag ) | | | +| for( c = 0; c < 3; c++ ) { | | | +| ccv_primaries_x[ c ] | 5 | i(32) | +| ccv_primaries_y[ c ] | 5 | i(32) | +| } | | | +| if( ccv_min_luminance_value_present_flag ) | | | +| ccv_min_luminance_value | 5 | u(32) | +| if( ccv_max_luminance_value_present_flag ) | | | +| ccv_max_luminance_value | 5 | u(32) | +| if( ccv_avg_luminance_value_present_flag ) | | | +| ccv_avg_luminance_value | 5 | u(32) | +| } | | | +| } | | | +| } | | | + +#### D.1.34 Ambient viewing environment SEI message syntax + +| ambient_viewing_environment( payloadSize ) { | C | Descriptor | +|----------------------------------------------|---|------------| +| ambient_illuminance | 5 | u(32) | +| ambient_light_x | 5 | u(16) | +| ambient_light_y | 5 | u(16) | +| } | | | + +#### D.1.35 Syntax of omnidirectional video specific SEI messages + +##### D.1.35.1 Equirectangular projection SEI message syntax + +| equirectangular_projection( payloadSize ) { | C | Descriptor | +|---------------------------------------------|---|------------| +| erp_cancel_flag | 5 | u(1) | +| if( !erp_cancel_flag ) | | | +| erp_persistence_flag | 5 | u(1) | +| erp_padding_flag | 5 | u(1) | +| erp_reserved_zero_2bits | 5 | u(2) | +| if( erp_padding_flag == 1 ) { | | | +| gp_erp_type | 5 | u(3) | +| left_gb_erp_width | 5 | u(8) | +| right_gb_erp_width | 5 | u(8) | +| } | | | +| } | | | +| } | | | + +##### D.1.35.2 Cubemap projection SEI message syntax + +| cubemap_projection( payloadSize ) { | C | Descriptor | +|-------------------------------------|---|------------| +| cmp_cancel_flag | 5 | u(1) | +| if( !cmp_cancel_flag ) | | | +| cmp_persistence_flag | 5 | u(1) | +| } | | | +| } | | | + +D.1.35.3 Sphere rotation SEI message syntax + +| | | | +|--------------------------------------------|---|------------| +| sphere_rotation( payloadSize ) { | C | Descriptor | +| sphere_rotation_cancel_flag | 5 | u(1) | +| if( !sphere_rotation_cancel_flag ) { | | | +| sphere_rotation_persistence_flag | 5 | u(1) | +| sphere_rotation_reserved_zero_6bits | 5 | u(6) | +| yaw_rotation | 5 | i(32) | +| pitch_rotation | 5 | i(32) | +| roll_rotation | 5 | i(32) | +| } | | | +| } | | | + +D.1.35.4 Region-wise packing SEI message syntax + +| regionwise_packing( payloadSize ) { | C | Descriptor | +|---------------------------------------------|---|------------| +| rwp_cancel_flag | 5 | u(1) | +| if( !rwp_cancel_flag ) { | | | +| rwp_persistence_flag | 5 | u(1) | +| constituent_picture_matching_flag | 5 | u(1) | +| rwp_reserved_zero_5bits | 5 | u(5) | +| num_packed_regions | 5 | u(8) | +| proj_picture_width | 5 | u(32) | +| proj_picture_height | 5 | u(32) | +| packed_picture_width | 5 | u(16) | +| packed_picture_height | 5 | u(16) | +| for( i = 0; i < num_packed_regions; i++ ) { | | | +| rwp_reserved_zero_4bits[ i ] | 5 | u(4) | +| transform_type[ i ] | 5 | u(3) | +| guard_band_flag[ i ] | 5 | u(1) | +| proj_region_width[ i ] | 5 | u(32) | +| proj_region_height[ i ] | 5 | u(32) | +| proj_region_top[ i ] | 5 | u(32) | +| proj_region_left[ i ] | 5 | u(32) | +| packed_region_width[ i ] | 5 | u(16) | +| packed_region_height[ i ] | 5 | u(16) | +| packed_region_top[ i ] | 5 | u(16) | +| packed_region_left[ i ] | 5 | u(16) | +| if( guard_band_flag[ i ] ) { | | | +| left_gb_width[ i ] | 5 | u(8) | +| right_gb_width[ i ] | 5 | u(8) | +| top_gb_height[ i ] | 5 | u(8) | +| bottom_gb_height[ i ] | 5 | u(8) | +| gb_not_used_for_pred_flag[ i ] | 5 | u(1) | +| for( j = 0; j < 4; j++ ) | | | +| gb_type[ i ][ j ] | 5 | u(3) | +| rwp_gb_reserved_zero_3bits[ i ] | 5 | u(3) | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | + +#### D.1.35.5 Omnidirectional viewport SEI message syntax + +| | | | +|----------------------------------------------------|---|------------| +| omni_viewport( payloadSize ) { | C | Descriptor | +| omni_viewport_id | 5 | u(10) | +| omni_viewport_cancel_flag | 5 | u(1) | +| if( !omni_viewport_cancel_flag ) { | | | +| omni_viewport_persistence_flag | 5 | u(1) | +| omni_viewport_cnt_minus1 | 5 | u(4) | +| for( i = 0; i <= omni_viewport_cnt_minus1; i++ ) { | | | +| omni_viewport_azimuth_centre[ i ] | 5 | i(32) | +| omni_viewport_elevation_centre[ i ] | 5 | i(32) | +| omni_viewport_tilt_centre[ i ] | 5 | i(32) | +| omni_viewport_hor_range[ i ] | 5 | u(32) | +| omni_viewport_ver_range[ i ] | 5 | u(32) | +| } | | | +| } | | | +| } | | | + +#### D.1.36 SEI manifest SEI message syntax + +| | | | +|-----------------------------------------------------|---|------------| +| sei_manifest( payloadSize ) { | C | Descriptor | +| manifest_num_sei_msg_types | 5 | u(16) | +| for( i = 0; i < manifest_num_sei_msg_types; i++ ) { | | | +| manifest_sei_payload_type[ i ] | 5 | u(16) | +| manifest_sei_description[ i ] | 5 | u(8) | +| } | | | +| } | | | + +#### D.1.37 SEI prefix indication SEI message syntax + +| | | | +|-------------------------------------------------------------------|---|------------| +| sei_prefix_indication( payloadSize ) { | C | Descriptor | +| prefix_sei_payload_type | 5 | u(16) | +| num_sei_prefix_indications_minus1 | 5 | u(8) | +| for( i = 0; i <= num_sei_prefix_indications_minus1; i++ ) { | | | +| num_bits_in_prefix_indication_minus1[ i ] | 5 | u(16) | +| for( j = 0; j <= num_bits_in_prefix_indication_minus1[ i ]; j++ ) | | | +| sei_prefix_data_bit[ i ][ j ] | 5 | u(1) | +| while( !byte_aligned() ) | | | +| byte_alignment_bit_equal_to_one /* equal to 1 */ | 5 | f(1) | +| } | | | +| } | | | +| } | | | + +#### D.1.38 Shutter interval information SEI message syntax + +| shutter_interval_info( payloadSize ) { | C | Descriptor | +|-----------------------------------------------------|---|------------| +| sii_sub_layer_idx | 5 | ue(v) | +| if( sii_sub_layer_idx == 0 ) { | | | +| shutter_interval_info_present_flag | 5 | u(1) | +| if( shutter_interval_info_present_flag ) { | | | +| sii_time_scale | 5 | u(32) | +| fixed_shutter_interval_within_cvs_flag | 5 | u(1) | +| if( fixed_shutter_interval_within_cvs_flag ) | | | +| sii_num_units_in_shutter_interval | 5 | u(32) | +| else { | | | +| sii_max_sub_layers_minus1 | 5 | u(3) | +| for( i = 0; i <= sii_max_sub_layers_minus1; i++ ) | | | +| sub_layer_num_units_in_shutter_interval[ i ] | 5 | u(32) | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | + +#### D.1.39 Reserved SEI message syntax + +| reserved_sei_message( payloadSize ) { | C | Descriptor | +|------------------------------------------|---|------------| +| for( i = 0; i < payloadSize; i++ ) | | | +| reserved_sei_message_payload_byte | 5 | b(8) | +| } | | | + +### D.2 SEI payload semantics + +#### D.2.1 General SEI payload semantics + +**bit\_equal\_to\_one** shall be equal to 1. + +**bit\_equal\_to\_zero** shall be equal to 0. + +The semantics and persistence scope for each SEI message are specified in the semantics specification for each particular SEI message. + +The values of some SEI message syntax elements, including **pan\_scan\_rect\_id**, **scene\_id**, **second\_scene\_id**, **snapshot\_id**, **progressive\_refinement\_id**, **tone\_map\_id**, **frame\_packing\_arrangement\_id**, and **colour\_remap\_id**, are split into two sets of value ranges, where the first set is specified as "may be used as determined by the application", and the second set is specified as "reserved for future use by ITU-T | ISO/IEC". Applications should be cautious of potential "collisions" of the interpretation for values of these syntax elements belonging to the first set of value ranges. Since different applications might use these IDs having values in the first set of value ranges for different purposes, particular care should be exercised in the design of encoders that generate SEI messages with these IDs having values in the first set of value ranges, and in the design of decoders that interpret SEI messages with these IDs. This Specification does not define any management for these values. These IDs having values in the first set of value ranges might only be suitable for use in contexts in which "collisions" of usage (i.e., different definitions of the syntax and semantics of an SEI message with one of these IDs having the same value in the first set of value ranges) are unimportant, or not possible, or are managed – e.g., defined or managed in the controlling application or transport specification, or by controlling the environment in which bitstreams are distributed. + +**PayloadBits** is set equal to $8 * \text{payloadSize} - \text{nPayloadAlignmentBits}$ where **nPayloadAlignmentBits** is the number of **bit\_equal\_to\_one** and **bit\_equal\_to\_zero** syntax elements at the end of the **sei\_payload( )** syntax structure. + +#### D.2.2 Buffering period SEI message semantics + +The presence of the buffering period SEI message in the bitstream is specified as follows: + +- If NalHrdBpPresentFlag is equal to 1 or VclHrdBpPresentFlag is equal to 1, one buffering period SEI message can be present in any access unit of the bitstream, and one buffering period SEI message shall be present in every IDR access unit and every access unit associated with a recovery point SEI message. +- Otherwise (NalHrdBpPresentFlag is equal to 0 and VclHrdBpPresentFlag is equal to 0), no buffering period SEI messages shall be present in any access unit of the bitstream. + +NOTE 1 – For some applications, the frequent presence of a buffering period SEI message may be desirable. + +A buffering period is specified as the set of access units between two instances of the buffering period SEI message in decoding order. + +**seq\_parameter\_set\_id** specifies the sequence parameter set for the current coded video sequence. The value of seq\_parameter\_set\_id shall be equal to the value of seq\_parameter\_set\_id in the picture parameter set referenced by the primary coded picture associated with the buffering period SEI message. The value of seq\_parameter\_set\_id shall be in the range of 0 to 31, inclusive. + +NOTE 2 – When the sequence parameter set identified by seq\_parameter\_set\_id is not already active, the buffering SEI message will activate the identified sequence parameter set for the current coded video sequence as specified in clause 7.4.1.2.1. + +**initial\_cpb\_removal\_delay[ SchedSelIdx ]** specifies the delay for the SchedSelIdx-th CPB between the time of arrival in the CPB of the first bit of the coded data associated with the access unit associated with the buffering period SEI message and the time of removal from the CPB of the coded data associated with the same access unit, for the first buffering period after HRD initialization. The syntax element has a length in bits given by initial\_cpb\_removal\_delay\_length\_minus1 + 1. It is in units of a 90 kHz clock. initial\_cpb\_removal\_delay[ SchedSelIdx ] shall not be equal to 0 and shall not exceed $90000 * ( CpbSize[ SchedSelIdx ] \div BitRate[ SchedSelIdx ] )$ , the time-equivalent of the CPB size in 90 kHz clock units. + +**initial\_cpb\_removal\_delay\_offset[ SchedSelIdx ]** is used for the SchedSelIdx-th CPB in combination with the cpb\_removal\_delay to specify the initial delivery time of coded access units to the CPB. initial\_cpb\_removal\_delay\_offset[ SchedSelIdx ] is in units of a 90 kHz clock. The initial\_cpb\_removal\_delay\_offset[ SchedSelIdx ] syntax element is a fixed length code having a length in bits given by initial\_cpb\_removal\_delay\_length\_minus1 + 1. This syntax element is not used by decoders and is needed only for the delivery scheduler (HSS) specified in Annex C. + +Over the entire coded video sequence, the sum of initial\_cpb\_removal\_delay[ SchedSelIdx ] and initial\_cpb\_removal\_delay\_offset[ SchedSelIdx ] shall be constant for each value of SchedSelIdx. + +### D.2.3 Picture timing SEI message semantics + +NOTE 1 – The syntax of the picture timing SEI message is dependent on the content of the sequence parameter set that is active for the primary coded picture associated with the picture timing SEI message. However, unless the picture timing SEI message of an IDR access unit is preceded by a buffering period SEI message within the same access unit, the activation of the associated sequence parameter set (and, for IDR pictures that are not the first picture in the bitstream, the determination that the primary coded picture is an IDR picture) does not occur until the decoding of the first coded slice NAL unit of the primary coded picture. Since the coded slice NAL unit of the primary coded picture follows the picture timing SEI message in NAL unit order, there may be cases in which it is necessary for a decoder to store the RBSP containing the picture timing SEI message until determining the parameters of the sequence parameter that will be active for the primary coded picture, and then perform the parsing of the picture timing SEI message. + +The presence of the picture timing SEI message in the bitstream is specified as follows: + +- If CpbDpbDelaysPresentFlag is equal to 1 or pic\_struct\_present\_flag is equal to 1, one picture timing SEI message shall be present in every access unit of the coded video sequence. +- Otherwise (CpbDpbDelaysPresentFlag is equal to 0 and pic\_struct\_present\_flag is equal to 0), no picture timing SEI messages shall be present in any access unit of the coded video sequence. + +**cpb\_removal\_delay** specifies how many clock ticks (see clause E.2.1) to wait after removal from the CPB of the access unit associated with the most recent buffering period SEI message in a preceding access unit before removing from the buffer the access unit data associated with the picture timing SEI message. This value is also used to calculate an earliest possible time of arrival of access unit data into the CPB for the HSS, as specified in Annex C. The syntax element is a fixed length code having a length in bits given by cpb\_removal\_delay\_length\_minus1 + 1. The cpb\_removal\_delay is the remainder of a modulo $2^{(cpb\_removal\_delay\_length\_minus1 + 1)}$ counter. + +NOTE 2 – The value of cpb\_removal\_delay\_length\_minus1 that determines the length (in bits) of the syntax element cpb\_removal\_delay is the value of cpb\_removal\_delay\_length\_minus1 coded in the sequence parameter set that is active for the primary coded picture associated with the picture timing SEI message, although cpb\_removal\_delay specifies a number of clock ticks relative to the removal time of the preceding access unit containing a buffering period SEI message, which may be an access unit of a different coded video sequence. + +**dpb\_output\_delay** is used to compute the DPB output time of the picture. It specifies how many clock ticks to wait after removal of an access unit from the CPB before the decoded picture can be output from the DPB (see clause C.2). + +NOTE 3 – A picture is not removed from the DPB at its output time when it is still marked as "used for short-term reference" or "used for long-term reference". + +NOTE 4 – Only one dpb\_output\_delay is specified for a decoded picture. + +The length of the syntax element dpb\_output\_delay is given in bits by dpb\_output\_delay\_length\_minus1 + 1. When max\_dec\_frame\_buffering is equal to 0, dpb\_output\_delay shall be equal to 0. + +The output time derived from the dpb\_output\_delay of any picture that is output from an output timing conforming decoder as specified in clause C.2 shall precede the output time derived from the dpb\_output\_delay of all pictures in any subsequent coded video sequence in decoding order. + +The output time derived from the dpb\_output\_delay of the second field, in decoding order, of a complementary non-reference field pair shall exceed the output time derived from the dpb\_output\_delay of the first field of the same complementary non-reference field pair. + +The picture output order established by the values of this syntax element shall be the same order as established by the values of PicOrderCnt( ) as specified in clauses C.4.1 to C.4.5, except that when the two fields of a complementary reference field pair have the same value of PicOrderCnt( ), the two fields have different output times. + +For pictures that are not output by the "bumping" process of clause C.4.5 because they precede, in decoding order, an IDR picture with no\_output\_of\_prior\_pics\_flag equal to 1 or inferred to be equal to 1, the output times derived from dpb\_output\_delay shall be increasing with increasing value of PicOrderCnt( ) relative to all pictures within the same coded video sequence subsequent to any picture having a memory\_management\_control\_operation equal to 5. + +**pic\_struct** indicates whether a picture should be displayed as a frame or one or more fields, according to Table D-1. Frame doubling (pic\_struct equal to 7) indicates that the frame should be displayed two times consecutively, and frame tripling (pic\_struct equal to 8) indicates that the frame should be displayed three times consecutively. + +NOTE 5 – Frame doubling can facilitate the display, for example, of 25p video on a 50p display and 29.97p video on a 59.94p display. Using frame doubling and frame tripling in combination on every other frame can facilitate the display of 23.98p video on a 59.94p display. + +When pic\_struct is present (pic\_struct\_present\_flag is equal to 1), the constraints specified in the third column of Table D-1 shall be obeyed. + +NOTE 6 – When pic\_struct\_present\_flag is equal to 0, then in many cases default values may be inferred. In the absence of other indications of the intended display type of a picture, the decoder should infer the value of pic\_struct as follows: + +- If field\_pic\_flag is equal to 1, pic\_struct should be inferred to be equal to (1 + bottom\_field\_flag). +- Otherwise, if TopFieldOrderCnt is equal to BottomFieldOrderCnt, pic\_struct should be inferred to be equal to 0. +- Otherwise, if TopFieldOrderCnt is less than BottomFieldOrderCnt, pic\_struct should be inferred to be equal to 3. +- Otherwise (field\_pic\_flag is equal to 0 and TopFieldOrderCnt is greater than BottomFieldOrderCnt), pic\_struct should be inferred to be equal to 4. + +pic\_struct is only a hint as to how the decoded video should be displayed on an assumed display type (e.g., interlaced or progressive) at an assumed display rate. When another display type or display rate is used by the decoder, then pic\_struct does not indicate the display method, but may aid in processing the decoded video for the alternative display. When it is desired for pic\_struct to have an effective value in the range of 5 to 8, inclusive, pic\_struct\_present\_flag should be equal to 1, as the above inference rule will not produce these values. + +**Table D-1 – Interpretation of pic\_struct** + +| Value | Indicated display of picture | Restrictions | NumClockTS | +|-------|------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------| +| 0 | (progressive) frame | field_pic_flag shall be 0,
TopFieldOrderCnt shall be equal to
BottomFieldOrderCnt | 1 | +| 1 | top field | field_pic_flag shall be 1,
bottom_field_flag shall be 0 | 1 | +| 2 | bottom field | field_pic_flag shall be 1,
bottom_field_flag shall be 1 | 1 | +| 3 | top field, bottom field, in that order | field_pic_flag shall be 0,
TopFieldOrderCnt shall be less than or
equal to BottomFieldOrderCnt | 2 | +| 4 | bottom field, top field, in that order | field_pic_flag shall be 0,
BottomFieldOrderCnt shall be less than
or equal to TopFieldOrderCnt | 2 | +| 5 | top field, bottom field, top field repeated,
in that order | field_pic_flag shall be 0,
TopFieldOrderCnt shall be less than or
equal to BottomFieldOrderCnt | 3 | +| 6 | bottom field, top field, bottom field
repeated, in that order | field_pic_flag shall be 0,
BottomFieldOrderCnt shall be less than
or equal to TopFieldOrderCnt | 3 | +| 7 | frame doubling | field_pic_flag shall be 0,
fixed_frame_rate_flag shall be 1,
TopFieldOrderCnt shall be equal to
BottomFieldOrderCnt | 2 | +| 8 | frame tripling | field_pic_flag shall be 0,
fixed_frame_rate_flag shall be 1,
TopFieldOrderCnt shall be equal to
BottomFieldOrderCnt | 3 | +| 9..15 | reserved | | | + +When fixed\_frame\_rate\_flag is equal to 1, it is a requirement of bitstream conformance that the constraints specified as follows shall be obeyed throughout the operation of the following process, which is operated in output order. + +1. Prior to output of the first picture of the bitstream (in output order) and prior to the output of the first picture (in output order) of each subsequent coded video sequence for which the content of the active sequence parameter set differs from that of the previously-active sequence parameter set, the variable lastFieldBottom is set equal to "not determined". +2. After the output of each picture, the value of lastFieldBottom is checked and set as follows, using the values of field\_pic\_flag, bottom\_field\_flag, pic\_struct, TopFieldOrderCnt and BottomFieldOrderCnt (when applicable) for the picture that was output. + - If field\_pic\_flag is equal to 1, it is a requirement of bitstream conformance that the value of lastFieldBottom shall not be equal to bottom\_field\_flag. The value of lastFieldBottom is then set equal to bottom\_field\_flag. + - Otherwise (field\_pic\_flag is equal to 0), the following applies: + - If pic\_struct is present and is equal to 3 or 5, it is a requirement of bitstream conformance that the value of lastFieldBottom shall not be equal to 0. The value of lastFieldBottom is then set equal to $1 - (( \text{pic\_struct} - 1 ) \gg 2)$ . + - Otherwise, if pic\_struct is present and is equal to 4 or 6, it is a requirement of bitstream conformance that the value of lastFieldBottom shall not be equal to 1. The value of lastFieldBottom is then set equal to $(( \text{pic\_struct} - 1 ) \gg 2)$ . + +- Otherwise, if TopFieldOrderCnt is less than BottomFieldOrderCnt, it is a requirement of bitstream conformance that the value of lastFieldBottom shall not be equal to 0. The value of lastFieldBottom is then set equal to 1. +- Otherwise, if TopFieldOrderCnt is greater than BottomFieldOrderCnt, it is a requirement of bitstream conformance that the value of lastFieldBottom shall not be equal to 1. The value of lastFieldBottom is then set equal to 0. +- Otherwise (TopFieldOrderCnt is equal to BottomFieldOrderCnt and pic\_struct is not present or is not in the range of 3 to 6, inclusive), lastFieldBottom may have any value, and its value is not changed. + +NumClockTS is determined by pic\_struct as specified in Table D-1. There are up to NumClockTS sets of clock timestamp information for a picture, as specified by clock\_timestamp\_flag[ i ] for each set. The sets of clock timestamp information apply to the field(s) or the frame(s) associated with the picture by pic\_struct. + +The contents of the clock timestamp syntax elements indicate a time of origin, capture, or alternative ideal display. This indicated time is computed as + +$$\text{clockTimestamp} = ( ( \text{hH} * 60 + \text{mM} ) * 60 + \text{sS} ) * \text{time\_scale} + \text{nFrames} * ( \text{num\_units\_in\_tick} * ( 1 + \text{nuit\_field\_based\_flag} ) ) + \text{tOffset}, \quad (\text{D-1})$$ + +in units of clock ticks of a clock with clock frequency equal to time\_scale Hz, relative to some unspecified point in time for which clockTimestamp is equal to 0. Output order and DPB output timing are not affected by the value of clockTimestamp. When two or more frames with pic\_struct equal to 0 are consecutive in output order and have equal values of clockTimestamp, the indication is that the frames represent the same content and that the last such frame in output order is the preferred representation. + +NOTE 7 – clockTimestamp time indications may aid display on devices with refresh rates other than those well-matched to DPB output times. + +**clock\_timestamp\_flag[ i ]** equal to 1 indicates that a number of clock timestamp syntax elements are present and follow immediately. clock\_timestamp\_flag[ i ] equal to 0 indicates that the associated clock timestamp syntax elements are not present. When NumClockTS is greater than 1 and clock\_timestamp\_flag[ i ] is equal to 1 for more than one value of i, the value of clockTimestamp shall be non-decreasing with increasing value of i. + +**ct\_type** indicates the scan type (interlaced or progressive) of the source material as specified in Table D-2. + +Two fields of a coded frame may have different values of ct\_type. + +When clockTimestamp is equal for two fields of opposite parity that are consecutive in output order, both with ct\_type equal to 0 (progressive) or ct\_type equal to 2 (unknown), the two fields are indicated to have come from the same original progressive frame. Two consecutive fields in output order shall have different values of clockTimestamp when the value of ct\_type for either field is 1 (interlaced). + +**Table D-2 – Mapping of ct\_type to source picture scan** + +| Value | Original picture scan | +|-------|-----------------------| +| 0 | progressive | +| 1 | interlaced | +| 2 | unknown | +| 3 | reserved | + +**nuit\_field\_based\_flag** is used in calculating clockTimestamp, as specified in Equation D-1. + +**counting\_type** specifies the method of dropping values of the n\_frames as specified in Table D-3. + +**Table D-3 – Definition of counting\_type values** + +| Value | Interpretation | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | no dropping of n_frames count values and no use of time_offset | +| 1 | no dropping of n_frames count values | +| 2 | dropping of individual zero values of n_frames count | +| 3 | dropping of individual MaxFPS – 1 values of n_frames count | +| 4 | dropping of the two lowest (value 0 and 1) n_frames counts when seconds_value is equal to 0 and minutes_value is not an integer multiple of 10 | +| 5 | dropping of unspecified individual n_frames count values | +| 6 | dropping of unspecified numbers of unspecified n_frames count values | +| 7..31 | reserved | + +**full\_timestamp\_flag** equal to 1 specifies that the n\_frames syntax element is followed by seconds\_value, minutes\_value, and hours\_value. full\_timestamp\_flag equal to 0 specifies that the n\_frames syntax element is followed by seconds\_flag. + +**discontinuity\_flag** equal to 0 indicates that the difference between the current value of clockTimestamp and the value of clockTimestamp computed from the previous clock timestamp in output order can be interpreted as the time difference between the times of origin or capture of the associated frames or fields. discontinuity\_flag equal to 1 indicates that the difference between the current value of clockTimestamp and the value of clockTimestamp computed from the previous clock timestamp in output order should not be interpreted as the time difference between the times of origin or capture of the associated frames or fields. When discontinuity\_flag is equal to 0, the value of clockTimestamp shall be greater than or equal to all values of clockTimestamp present for the preceding picture in DPB output order. + +**cnt\_dropped\_flag** specifies the skipping of one or more values of n\_frames using the counting method specified by counting\_type. + +**n\_frames** specifies the value of nFrames used to compute clockTimestamp. n\_frames shall be less than + +$$\text{MaxFPS} = \text{Ceil}(\text{time\_scale} \div (2 * \text{num\_units\_in\_tick})) \quad (\text{D-2})$$ + +NOTE 8 – n\_frames is a frame-based counter. For field-specific timing indications, time\_offset should be used to indicate a distinct clockTimestamp for each field. + +When counting\_type is equal to 2 and cnt\_dropped\_flag is equal to 1, n\_frames shall be equal to 1 and the value of n\_frames for the previous picture in output order shall not be equal to 0 unless discontinuity\_flag is equal to 1. + +NOTE 9 – When counting\_type is equal to 2, the need for increasingly large magnitudes of tOffset in Equation D-1 when using fixed non-integer frame rates (e.g., 12.5 frames per second with time\_scale equal to 50 and num\_units\_in\_tick equal to 2 and nuit\_field\_based\_flag equal to 0) can be avoided by occasionally skipping over the value n\_frames equal to 0 when counting (e.g., counting n\_frames from 0 to 12, then incrementing seconds\_value and counting n\_frames from 1 to 12, then incrementing seconds\_value and counting n\_frames from 0 to 12, etc.). + +When counting\_type is equal to 3 and cnt\_dropped\_flag is equal to 1, n\_frames shall be equal to 0 and the value of n\_frames for the previous picture in output order shall not be equal to MaxFPS – 1 unless discontinuity\_flag is equal to 1. + +NOTE 10 – When counting\_type is equal to 3, the need for increasingly large magnitudes of tOffset in Equation D-1 when using fixed non-integer frame rates (e.g., 12.5 frames per second with time\_scale equal to 50 and num\_units\_in\_tick equal to 2 and nuit\_field\_based\_flag equal to 0) can be avoided by occasionally skipping over the value n\_frames equal to MaxFPS – 1 when counting (e.g., counting n\_frames from 0 to 12, then incrementing seconds\_value and counting n\_frames from 0 to 11, then incrementing seconds\_value and counting n\_frames from 0 to 12, etc.). + +When counting\_type is equal to 4 and cnt\_dropped\_flag is equal to 1, n\_frames shall be equal to 2 and the specified value of sS shall be zero and the specified value of mM shall not be an integer multiple of ten and n\_frames for the previous picture in output order shall not be equal to 0 or 1 unless discontinuity\_flag is equal to 1. + +NOTE 11 – When counting\_type is equal to 4, the need for increasingly large magnitudes of tOffset in Equation D-1 when using fixed non-integer frame rates (e.g., 30000÷1001 frames per second with time\_scale equal to 60000 and num\_units\_in\_tick equal to 1 001 and nuit\_field\_based\_flag equal to 1) can be reduced by occasionally skipping over the values of n\_frames equal to 0 + +and 1 when counting (e.g., counting *n\_frames* from 0 to 29, then incrementing *seconds\_value* and counting *n\_frames* from 0 to 29, etc., until the *seconds\_value* is zero and *minutes\_value* is not an integer multiple of ten, then counting *n\_frames* from 2 to 29, then incrementing *seconds\_value* and counting *n\_frames* from 0 to 29, etc.). This counting method is well known in industry and is often referred to as "NTSC drop-frame" counting. + +When *counting\_type* is equal to 5 or 6 and *cnt\_dropped\_flag* is equal to 1, *n\_frames* shall not be equal to 1 plus the value of *n\_frames* for the previous picture in output order modulo *MaxFPS* unless *discontinuity\_flag* is equal to 1. + +NOTE 12 – When *counting\_type* is equal to 5 or 6, the need for increasingly large magnitudes of *tOffset* in Equation D-1 when using fixed non-integer frame rates can be avoided by occasionally skipping over some values of *n\_frames* when counting. The specific values of *n\_frames* that are skipped are not specified when *counting\_type* is equal to 5 or 6. + +**seconds\_flag** equal to 1 specifies that *seconds\_value* and *minutes\_flag* are present when *full\_timestamp\_flag* is equal to 0. *seconds\_flag* equal to 0 specifies that *seconds\_value* and *minutes\_flag* are not present. + +**seconds\_value** specifies the value of sS used to compute *clockTimestamp*. The value of *seconds\_value* shall be in the range of 0 to 59, inclusive. When *seconds\_value* is not present, the previous *seconds\_value* in decoding order shall be used as sS to compute *clockTimestamp*. + +**minutes\_flag** equal to 1 specifies that *minutes\_value* and *hours\_flag* are present when *full\_timestamp\_flag* is equal to 0 and *seconds\_flag* is equal to 1. *minutes\_flag* equal to 0 specifies that *minutes\_value* and *hours\_flag* are not present. + +**minutes\_value** specifies the value of mM used to compute *clockTimestamp*. The value of *minutes\_value* shall be in the range of 0 to 59, inclusive. When *minutes\_value* is not present, the previous *minutes\_value* in decoding order shall be used as mM to compute *clockTimestamp*. + +**hours\_flag** equal to 1 specifies that *hours\_value* is present when *full\_timestamp\_flag* is equal to 0 and *seconds\_flag* is equal to 1 and *minutes\_flag* is equal to 1. + +**hours\_value** specifies the value of hH used to compute *clockTimestamp*. The value of *hours\_value* shall be in the range of 0 to 23, inclusive. When *hours\_value* is not present, the previous *hours\_value* in decoding order shall be used as hH to compute *clockTimestamp*. + +**time\_offset** specifies the value of *tOffset* used to compute *clockTimestamp*. The number of bits used to represent *time\_offset* shall be equal to *time\_offset\_length*. When *time\_offset* is not present, the value 0 shall be used as *tOffset* to compute *clockTimestamp*. + +#### D.2.4 Pan-scan rectangle SEI message semantics + +The pan-scan rectangle SEI message syntax elements specify the coordinates of a rectangle relative to the cropping rectangle of the sequence parameter set. Each coordinate of this rectangle is specified in units of one-sixteenth sample spacing relative to the luma sampling grid. + +**pan\_scan\_rect\_id** contains an identifying number that may be used to identify the purpose of the pan-scan rectangle (for example, to identify the rectangle as the area to be shown on a particular display device or as the area that contains a particular actor in the scene). The value of *pan\_scan\_rect\_id* shall be in the range of 0 to $2^{32} - 2$ , inclusive. + +Values of *pan\_scan\_rect\_id* from 0 to 255, inclusive, and from 512 to $2^{31} - 1$ , inclusive, may be used as determined by the application. Values of *pan\_scan\_rect\_id* from 256 to 511, inclusive, and from $2^{31}$ to $2^{32} - 2$ , inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of *pan\_scan\_rect\_id* in the range of 256 to 511, inclusive, or in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, shall ignore it. + +**pan\_scan\_rect\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous pan-scan rectangle SEI message in output order. *pan\_scan\_rect\_cancel\_flag* equal to 0 indicates that pan-scan rectangle information follows. + +**pan\_scan\_cnt\_minus1** specifies the number of pan-scan rectangles that are present in the SEI message. *pan\_scan\_cnt\_minus1* shall be in the range of 0 to 2, inclusive. *pan\_scan\_cnt\_minus1* equal to 0 indicates that a single pan-scan rectangle is present that applies to all fields of the decoded picture. *pan\_scan\_cnt\_minus1* shall be equal to 0 when the current picture is a field. *pan\_scan\_cnt\_minus1* equal to 1 indicates that two pan-scan rectangles are present, the first of which applies to the first field of the picture in output order and the second of which applies to the second field of the picture in output order. *pan\_scan\_cnt\_minus1* equal to 2 indicates that three pan-scan rectangles are present, the first of which applies to the first field of the picture in output order, the second of which applies to the second field of the picture in output order, and the third of which applies to a repetition of the first field as a third field in output order. + +**pan\_scan\_rect\_left\_offset[ i ]**, **pan\_scan\_rect\_right\_offset[ i ]**, **pan\_scan\_rect\_top\_offset[ i ]**, and **pan\_scan\_rect\_bottom\_offset[ i ]**, specify, as signed integer quantities in units of one-sixteenth sample spacing relative to the luma sampling grid, the location of the pan-scan rectangle. The values of each of these four syntax elements shall be in the range of $-2^{31} + 1$ to $2^{31} - 1$ , inclusive. + +The pan-scan rectangle is specified, in units of one-sixteenth sample spacing relative to a luma frame sampling grid, as the region with frame horizontal coordinates from $16 * \text{CropUnitX} * \text{frame\_crop\_left\_offset} + \text{pan\_scan\_rect\_left\_offset}[i]$ to $16 * (16 * \text{PicWidthInMbs} - \text{CropUnitX} * \text{frame\_crop\_right\_offset}) + \text{pan\_scan\_rect\_right\_offset}[i] - 1$ and with vertical coordinates from $16 * \text{CropUnitY} * \text{frame\_crop\_top\_offset} + \text{pan\_scan\_rect\_top\_offset}[i]$ to $16 * (16 * \text{PicHeightInMbs} - \text{CropUnitY} * \text{frame\_crop\_bottom\_offset}) + \text{pan\_scan\_rect\_bottom\_offset}[i] - 1$ , inclusive. The value of $16 * \text{CropUnitX} * \text{frame\_crop\_left\_offset} + \text{pan\_scan\_rect\_left\_offset}[i]$ shall be less than or equal to $16 * (16 * \text{PicWidthInMbs} - \text{CropUnitX} * \text{frame\_crop\_right\_offset}) + \text{pan\_scan\_rect\_right\_offset}[i] - 1$ ; and the value of $16 * \text{CropUnitY} * \text{frame\_crop\_top\_offset} + \text{pan\_scan\_rect\_top\_offset}[i]$ shall be less than or equal to $16 * (16 * \text{PicHeightInMbs} - \text{CropUnitY} * \text{frame\_crop\_bottom\_offset}) + \text{pan\_scan\_rect\_bottom\_offset}[i] - 1$ . + +When the pan-scan rectangular area includes samples outside of the cropping rectangle, the region outside of the cropping rectangle may be filled with synthesized content (such as black video content or neutral grey video content) for display. + +**pan\_scan\_rect\_repetition\_period** specifies the persistence of the pan-scan rectangle SEI message and may specify a picture order count interval within which another pan-scan rectangle SEI message with the same value of **pan\_scan\_rect\_id** or the end of the coded video sequence shall be present in the bitstream. The value of **pan\_scan\_rect\_repetition\_period** shall be in the range of 0 to 16 384, inclusive. When **pan\_scan\_cnt\_minus1** is greater than 0, **pan\_scan\_rect\_repetition\_period** shall not be greater than 1. + +**pan\_scan\_rect\_repetition\_period** equal to 0 specifies that the pan-scan rectangle information applies to the current decoded picture only. + +**pan\_scan\_rect\_repetition\_period** equal to 1 specifies that the pan-scan rectangle information persists in output order until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a pan-scan rectangle SEI message with the same value of **pan\_scan\_rect\_id** is output having **PicOrderCnt()** greater than **PicOrderCnt( CurrPic )**. + +**pan\_scan\_rect\_repetition\_period** equal to 0 or equal to 1 indicates that another pan-scan rectangle SEI message with the same value of **pan\_scan\_rect\_id** may or may not be present. + +**pan\_scan\_rect\_repetition\_period** greater than 1 specifies that the pan-scan rectangle information persists until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a pan-scan rectangle SEI message with the same value of **pan\_scan\_rect\_id** is output having **PicOrderCnt()** greater than **PicOrderCnt( CurrPic )** and less than or equal to **PicOrderCnt( CurrPic ) + pan\_scan\_rect\_repetition\_period**. + +**pan\_scan\_rect\_repetition\_period** greater than 1 indicates that another pan-scan rectangle SEI message with the same value of **pan\_scan\_rect\_id** shall be present for a picture in an access unit that is output having **PicOrderCnt()** greater than **PicOrderCnt( CurrPic )** and less than or equal to **PicOrderCnt( CurrPic ) + pan\_scan\_rect\_repetition\_period**; unless the bitstream ends or a new coded video sequence begins without output of such a picture. + +#### D.2.5 Filler payload SEI message semantics + +This message contains a series of **payloadSize** bytes of value 0xFF, which can be discarded. + +**ff\_byte** shall be a byte having the value 0xFF. + +#### D.2.6 User data registered by Rec. ITU-T T.35 SEI message semantics + +This message contains user data registered as specified by Rec. ITU-T T.35, the contents of which are not specified by this Recommendation | International Standard. + +**itu\_t\_t35\_country\_code** shall be a byte having a value specified as a country code by Rec. ITU-T T.35 Annex A. + +**itu\_t\_t35\_country\_code\_extension\_byte** shall be a byte having a value specified as a country code by Rec. ITU-T T.35 Annex B. + +**itu\_t\_t35\_payload\_byte** shall be a byte containing data registered as specified by Rec. ITU-T T.35. + +The ITU-T T.35 terminal provider code and terminal provider oriented code shall be contained in the first one or more bytes of the **itu\_t\_t35\_payload\_byte**, in the format specified by the Administration that issued the terminal provider code. Any remaining **itu\_t\_t35\_payload\_byte** data shall be data having syntax and semantics as specified by the entity identified by the ITU-T T.35 country code and terminal provider code. + +#### D.2.7 User data unregistered SEI message semantics + +This message contains unregistered user data identified by a UUID, the contents of which are not specified by this Recommendation | International Standard. + +**uuid\_iso\_iec\_11578** shall have a value specified as a UUID according to the procedures of ISO/IEC 11578:1996 Annex A. + +**user\_data\_payload\_byte** shall be a byte containing data having syntax and semantics as specified by the UUID generator. + +#### D.2.8 Recovery point SEI message semantics + +The recovery point SEI message assists a decoder in determining when the decoding process will produce acceptable pictures for display after the decoder initiates random access or after the encoder indicates a broken link in the coded video sequence. When the decoding process is started with the access unit in decoding order associated with the recovery point SEI message, all decoded pictures at or subsequent to the recovery point in output order specified in this SEI message are indicated to be correct or approximately correct in content. Decoded pictures produced by random access at or before the picture associated with the recovery point SEI message need not be correct in content until the indicated recovery point, and the operation of the decoding process starting at the picture associated with the recovery point SEI message may contain references to pictures not available in the decoded picture buffer. + +In addition, by use of the **broken\_link\_flag**, the recovery point SEI message can indicate to the decoder the location of some pictures in the bitstream that can result in serious visual artefacts when displayed, even when the decoding process was begun at the location of a previous IDR access unit in decoding order. + +NOTE 1 – The **broken\_link\_flag** can be used by encoders to indicate the location of a point after which the decoding process for the decoding of some pictures may cause references to pictures that, though available for use in the decoding process, are not the pictures that were used for reference when the bitstream was originally encoded (e.g., due to a splicing operation performed during the generation of the bitstream). + +The recovery point is specified as a count in units of **frame\_num** increments subsequent to the **frame\_num** of the current access unit at the position of the SEI message. + +NOTE 2 – When HRD information is present in the bitstream, a buffering period SEI message should be associated with the access unit associated with the recovery point SEI message in order to establish initialization of the HRD buffer model after a random access. + +Any picture parameter set RBSP that is referred to by a picture associated with a recovery point SEI message or by any picture following such a picture in decoding order shall be available to the decoding process prior to its activation, regardless of whether or not the decoding process is started at the beginning of the bitstream or with the access unit, in decoding order, that is associated with the recovery point SEI message. + +Any sequence parameter set RBSP that is referred to by a picture associated with a recovery point SEI message or by any picture following such a picture in decoding order shall be available to the decoding process prior to its activation, regardless of whether or not the decoding process is started at the beginning of the bitstream or with the access unit, in decoding order, that is associated with the recovery point SEI message. + +**recovery\_frame\_cnt** specifies the recovery point of output pictures in output order. All decoded pictures in output order are indicated to be correct or approximately correct in content starting at the output order position of the reference picture having the **frame\_num** equal to the **frame\_num** of the VCL NAL units for the current access unit incremented by **recovery\_frame\_cnt** in modulo **MaxFrameNum** arithmetic. **recovery\_frame\_cnt** shall be in the range of 0 to **MaxFrameNum** – 1, inclusive. + +**exact\_match\_flag** indicates whether decoded pictures at and subsequent to the specified recovery point in output order derived by starting the decoding process at the access unit associated with the recovery point SEI message shall be an exact match to the pictures that would be produced by starting the decoding process at the location of a previous IDR access unit in the NAL unit stream. The value 0 indicates that the match need not be exact and the value 1 indicates that the match shall be exact. + +When decoding starts from the location of the recovery point SEI message, all references to not available reference pictures shall be inferred as references to pictures containing only macroblocks coded using Intra macroblock prediction modes and having sample values given by $Y$ samples equal to $(1 \ll (\text{BitDepth}_Y - 1))$ , $Cb$ samples equal to $(1 \ll (\text{BitDepth}_C - 1))$ , and $Cr$ samples equal to $(1 \ll (\text{BitDepth}_C - 1))$ (mid-level grey) for purposes of determining the conformance of the value of **exact\_match\_flag**. + +NOTE 3 – When performing random access, decoders should infer all references to not available reference pictures as references to pictures containing only intra macroblocks and having sample values given by $Y$ equal to $(1 \ll (\text{BitDepth}_Y - 1))$ , $Cb$ equal to $(1 \ll (\text{BitDepth}_C - 1))$ , and $Cr$ equal to $(1 \ll (\text{BitDepth}_C - 1))$ (mid-level grey), regardless of the value of **exact\_match\_flag**. + +When `exact_match_flag` is equal to 0, the quality of the approximation at the recovery point is chosen by the encoding process and is not specified by this Recommendation | International Standard. + +NOTE 4 – Under some circumstances, the decoding process of pictures depends on the difference `DiffPicOrderCnt(picA, picB)` between the `PicOrderCnt()` values for two pictures `picA` and `picB`. However, no particular values of `TopFieldOrderCnt` and `BottomFieldOrderCnt` (as applicable) are specified to be assigned to the reference pictures that are not available due to the initiation of random access at the location of a picture associated with a recovery point SEI message. Also, no particular value has been specified for initialization (for random access purposes) of the related variables `prevPicOrderCntMsb`, `prevPicOrderCntLsb`, `prevFrameNumOffset`, and `prevFrameNum`. Thus, any values for these variables may be assigned that could hypothetically have resulted from operation of the decoding process starting with a hypothetical preceding IDR picture in decoding order, although such values may not be the same as the values that would have been obtained if the decoding process had started with the actual preceding IDR picture in the bitstream. When performing random access at a picture associated with a recovery point SEI message, it is suggested that decoders should derive the picture order count variables `TopFieldOrderCnt` and `BottomFieldOrderCnt` according to the following method: + +- A bit range greater than 32 bits should be allocated for the variables `TopFieldOrderCnt` and `BottomFieldOrderCnt` for each current picture to be decoded, as well as for the intermediate variables used for deriving these variables as specified in clause 8.2.1. (Due to the lack of assurance of correspondence of the values used for initialization of the related variables when random access is performed to the values that would be obtained if the decoding process had begun with the preceding IDR picture in decoding order, the calculations involving these variables in the decoding process of subsequent pictures may result in violation of the 32 bit range.) +- Any value within in the range of $-2^{31}$ to $2^{31} - 1$ , inclusive, may be assigned to the values of the variables `TopFieldOrderCnt` and `BottomFieldOrderCnt` of the reference pictures that are not available due to the random access operation. For example, the value 0 may be assigned to these variables. +- For the derivation of the picture order count variables for the picture at which random access is performed, `prevPicOrderCntMsb` may be set equal to any integer multiple of `MaxPicOrderCntLsb` in the range of $-2^{31}$ to $2^{31} - 1$ , inclusive, `prevPicOrderCntLsb` may be set equal to any value in the range of 0 to `MaxPicOrderCntLsb - 1`, inclusive, `prevFrameNumOffset` may be set equal to any integer multiple of `MaxFrameNum` in the range of 0 to $2^{31} - 1$ , inclusive, and `prevFrameNum` may be set equal to any value in the range of 0 to `MaxFrameNum - 1`, inclusive. For example, the value 0 may be assigned to all of the variables `prevPicOrderCntMsb`, `prevPicOrderCntLsb`, `prevFrameNumOffset`, and `prevFrameNum`. + +When `exact_match_flag` is equal to 1, it is a requirement of bitstream conformance that the values of the samples in the decoded pictures at or subsequent to the recovery point in output order shall be independent of the values that a decoder assigns to the variables `prevPicOrderCntMsb`, `prevPicOrderCntLsb`, `prevFrameNumOffset`, and `prevFrameNum` used in clause 8.2.1 for deriving the picture order count variables for the initialization of the decoding process at the picture associated with the recovery point SEI message, and of the values that are assigned to the `TopFieldOrderCnt` and `BottomFieldOrderCnt` variables of the reference pictures that are not available due to the random access operation. + +**broken\_link\_flag** indicates the presence or absence of a broken link in the NAL unit stream at the location of the recovery point SEI message and is assigned further semantics as follows: + +- If `broken_link_flag` is equal to 1, pictures produced by starting the decoding process at the location of a previous IDR access unit may contain undesirable visual artefacts to the extent that decoded pictures at and subsequent to the access unit associated with the recovery point SEI message in decoding order should not be displayed until the specified recovery point in output order. +- Otherwise (`broken_link_flag` is equal to 0), no indication is given regarding any potential presence of visual artefacts. + +Regardless of the value of the `broken_link_flag`, pictures subsequent to the specified recovery point in output order are specified to be correct or approximately correct in content. + +NOTE 5 – When a sub-sequence information SEI message is present in conjunction with a recovery point SEI message in which `broken_link_flag` is equal to 1 and when `sub_seq_layer_num` is equal to 0, `sub_seq_id` should be different from the latest `sub_seq_id` for `sub_seq_layer_num` equal to 0 that was decoded prior to the location of the recovery point SEI message. When `broken_link_flag` is equal to 0, the `sub_seq_id` in sub-sequence layer 0 should remain unchanged. + +**changing\_slice\_group\_idc** equal to 0 indicates that decoded pictures are correct or approximately correct in content at and subsequent to the recovery point in output order when all macroblocks of the primary coded pictures are decoded within the changing slice group period, i.e., the period between the access unit associated with the recovery point SEI message (inclusive) and the specified recovery point (inclusive) in decoding order. `changing_slice_group_idc` shall be equal to 0 when `num_slice_groups_minus1` is equal to 0 in any primary coded picture within the changing slice group period. + +When `changing_slice_group_idc` is equal to 1 or 2, `num_slice_groups_minus1` shall be equal to 1 and the macroblock-to-slice-group map type 3, 4, or 5 shall be applied in each primary coded picture in the changing slice group period. + +`changing_slice_group_idc` equal to 1 indicates that within the changing slice group period no sample values outside the decoded macroblocks covered by slice group 0 are used for inter prediction of any macroblock within slice group 0. In addition, `changing_slice_group_idc` equal to 1 indicates that when all macroblocks in slice group 0 within the changing slice group period are decoded, decoded pictures will be correct or approximately correct in content at and subsequent to + +the specified recovery point in output order regardless of whether any macroblock in slice group 1 within the changing slice group period is decoded. + +changing\_slice\_group\_idc equal to 2 indicates that within the changing slice group period no sample values outside the decoded macroblocks covered by slice group 1 are used for inter prediction of any macroblock within slice group 1. In addition, changing\_slice\_group\_idc equal to 2 indicates that when all macroblocks in slice group 1 within the changing slice group period are decoded, decoded pictures will be correct or approximately correct in content at and subsequent to the specified recovery point in output order regardless of whether any macroblock in slice group 0 within the changing slice group period is decoded. + +changing\_slice\_group\_idc shall be in the range of 0 to 2, inclusive. + +#### D.2.9 Decoded reference picture marking repetition SEI message semantics + +The decoded reference picture marking repetition SEI message is used to repeat the decoded reference picture marking syntax structure that was located in the slice headers of an earlier picture in the same coded video sequence in decoding order. + +**original\_idr\_flag** shall be equal to 1 when the decoded reference picture marking syntax structure occurred originally in an IDR picture. **original\_idr\_flag** shall be equal to 0 when the repeated decoded reference picture marking syntax structure did not occur in an IDR picture originally. + +**original\_frame\_num** shall be equal to the **frame\_num** of the picture where the repeated decoded reference picture marking syntax structure originally occurred. The picture indicated by **original\_frame\_num** is the previous coded picture having the specified value of **frame\_num**. The value of **original\_frame\_num** used to refer to a picture having a **memory\_management\_control\_operation** equal to 5 shall be 0. + +**original\_field\_pic\_flag** shall be equal to the **field\_pic\_flag** of the picture where the repeated decoded reference picture marking syntax structure originally occurred. + +**original\_bottom\_field\_flag** shall be equal to the **bottom\_field\_flag** of the picture where the repeated decoded reference picture marking syntax structure originally occurred. + +**dec\_ref\_pic\_marking()** shall contain a copy of the decoded reference picture marking syntax structure of the picture that has a value of **frame\_num** equal to **original\_frame\_num**. The **IdrPicFlag** used in the specification of the repeated **dec\_ref\_pic\_marking()** syntax structure shall be the **IdrPicFlag** of the slice header(s) of the picture that has a value of **frame\_num** equal to **original\_frame\_num** (i.e., **IdrPicFlag** as used in clause 7.3.3.3 shall be considered equal to **original\_idr\_flag**). + +#### D.2.10 Spare picture SEI message semantics + +This SEI message indicates that certain slice group map units, called spare slice group map units, in one or more decoded reference pictures resemble the co-located slice group map units in a specified decoded picture called the target picture. A spare slice group map unit may be used to replace a co-located, incorrectly decoded slice group map unit, in the target picture. A decoded picture containing spare slice group map units is called a spare picture. + +A spare picture SEI message shall not be present in an IDR access unit. The value of the **PicSizeInMapUnits** variable for the target picture (as specified later in this clause) shall be equal to the value of the **PicSizeInMapUnits** variable for the sequence parameter set that is active when processing the spare picture SEI message. + +For all spare pictures identified in a spare picture SEI message, the value of **frame\_mbs\_only\_flag** shall be equal to the value of **frame\_mbs\_only\_flag** of the target picture in the same SEI message. The spare pictures in the SEI message are constrained as follows: + +- If the target picture is a decoded field, all spare pictures identified in the same SEI message shall be decoded fields. +- Otherwise (the target picture is a decoded frame), all spare pictures identified in the same SEI message shall be decoded frames. + +For all spare pictures identified in a spare picture SEI message, the values of **pic\_width\_in\_mbs\_minus1** and **pic\_height\_in\_map\_units\_minus1** shall be equal to the values of **pic\_width\_in\_mbs\_minus1** and **pic\_height\_in\_map\_units\_minus1**, respectively, of the target picture in the same SEI message. The picture associated (as specified in clause 7.4.1.2.3) with this SEI message shall appear after the target picture, in decoding order. + +**target\_frame\_num** indicates the **frame\_num** of the target picture. + +**spare\_field\_flag** equal to 0 indicates that the target picture and the spare pictures are decoded frames. **spare\_field\_flag** equal to 1 indicates that the target picture and the spare pictures are decoded fields. + +**target\_bottom\_field\_flag** equal to 0 indicates that the target picture is a top field. **target\_bottom\_field\_flag** equal to 1 indicates that the target picture is a bottom field. + +A target picture is a decoded reference picture for which the corresponding primary coded picture precedes the current picture, in decoding order, and in which the values of `frame_num`, `field_pic_flag` (when present) and `bottom_field_flag` (when present) are equal to `target_frame_num`, `spare_field_flag` and `target_bottom_field_flag`, respectively. + +**num\_spare\_pics\_minus1** indicates the number of spare pictures for the specified target picture. The number of spare pictures is equal to `num_spare_pics_minus1 + 1`. The value of `num_spare_pics_minus1` shall be in the range of 0 to 15, inclusive. + +**delta\_spare\_frame\_num[ i ]** is used to identify the spare picture that contains the i-th set of spare slice group map units, hereafter called the i-th spare picture, as specified below. The value of `delta_spare_frame_num[ i ]` shall be in the range of 0 to `MaxFrameNum - 2 + spare_field_flag`, inclusive. + +The `frame_num` of the i-th spare picture, `spareFrameNum[ i ]`, is derived as follows for all values of i from 0 to `num_spare_pics_minus1`, inclusive: + +``` + +candidateSpareFrameNum = target_frame_num - 1 + spare_field_flag +for ( i = 0; i <= num_spare_pics_minus1; i++ ) { + if( candidateSpareFrameNum < 0 ) + candidateSpareFrameNum = MaxFrameNum - 1 + spareFrameNum[ i ] = candidateSpareFrameNum - delta_spare_frame_num[ i ] + if( spareFrameNum[ i ] < 0 ) + spareFrameNum[ i ] = MaxFrameNum + spareFrameNum[ i ] + candidateSpareFrameNum = spareFrameNum[ i ] - 1 + spare_field_flag +} + +``` + +(D-3) + +**spare\_bottom\_field\_flag[ i ]** equal to 0 indicates that the i-th spare picture is a top field. `spare_bottom_field_flag[ i ]` equal to 1 indicates that the i-th spare picture is a bottom field. + +The 0-th spare picture is a decoded reference picture for which the corresponding primary coded picture precedes the target picture, in decoding order, and in which the values of `frame_num`, `field_pic_flag` (when present) and `bottom_field_flag` (when present) are equal to `spareFrameNum[ 0 ]`, `spare_field_flag` and `spare_bottom_field_flag[ 0 ]`, respectively. The i-th spare picture is a decoded reference picture for which the corresponding primary coded picture precedes the ( i - 1 )-th spare picture, in decoding order, and in which the values of `frame_num`, `field_pic_flag` (when present) and `bottom_field_flag` (when present) are equal to `spareFrameNum[ i ]`, `spare_field_flag` and `spare_bottom_field_flag[ i ]`, respectively. + +**spare\_area\_idc[ i ]** indicates the method used to identify the spare slice group map units in the i-th spare picture. `spare_area_idc[ i ]` shall be in the range of 0 to 2, inclusive. `spare_area_idc[ i ]` equal to 0 indicates that all slice group map units in the i-th spare picture are spare units. `spare_area_idc[ i ]` equal to 1 indicates that the value of the syntax element `spare_unit_flag[ i ][ j ]` is used to identify the spare slice group map units. `spare_area_idc[ i ]` equal to 2 indicates that the `zero_run_length[ i ][ j ]` syntax element is used to derive the values of `spareUnitFlagInBoxOutOrder[ i ][ j ]`, as described below. + +**spare\_unit\_flag[ i ][ j ]** equal to 0 indicates that the j-th slice group map unit in raster scan order in the i-th spare picture is a spare unit. `spare_unit_flag[ i ][ j ]` equal to 1 indicates that the j-th slice group map unit in raster scan order in the i-th spare picture is not a spare unit. + +**zero\_run\_length[ i ][ j ]** is used to derive the values of `spareUnitFlagInBoxOutOrder[ i ][ j ]` when `spare_area_idc[ i ]` is equal to 2. In this case, the spare slice group map units identified in `spareUnitFlagInBoxOutOrder[ i ][ j ]` appear in counter-clockwise box-out order, as specified in clause 8.2.2.4, for each spare picture. `spareUnitFlagInBoxOutOrder[ i ][ j ]` equal to 0 indicates that the j-th slice group map unit in counter-clockwise box-out order in the i-th spare picture is a spare unit. `spareUnitFlagInBoxOutOrder[ i ][ j ]` equal to 1 indicates that the j-th slice group map unit in counter-clockwise box-out order in the i-th spare picture is not a spare unit. + +When `spare_area_idc[ 0 ]` is equal to 2, `spareUnitFlagInBoxOutOrder[ 0 ][ j ]` is derived as specified by the following pseudo-code: + +``` + +for( j = 0, loop = 0; j < PicSizeInMapUnits; loop++ ) { + for( k = 0; k < zero_run_length[ 0 ][ loop ]; k++ ) + spareUnitFlagInBoxOutOrder[ 0 ][ j++ ] = 0 + spareUnitFlagInBoxOutOrder[ 0 ][ j++ ] = 1 +} + +``` + +(D-4) + +When `spare_area_idc[i]` is equal to 2 and the value of `i` is greater than 0, `spareUnitFlagInBoxOutOrder[i][j]` is derived as specified by the following pseudo-code: + +``` +for(j = 0, loop = 0; j < PicSizeInMapUnits; loop++) { + for( k = 0; k < zero_run_length[i][loop]; k++ ) + spareUnitFlagInBoxOutOrder[i][j] = spareUnitFlagInBoxOutOrder[i - 1][j++] + spareUnitFlagInBoxOutOrder[i][j] = !spareUnitFlagInBoxOutOrder[i - 1][j++] +} +``` + +(D-5) + +#### D.2.11 Scene information SEI message semantics + +A scene and a scene transition are herein defined as a set of consecutive pictures in output order. + +NOTE 1 – Decoded pictures within one scene generally have similar content. The scene information SEI message is used to label pictures with scene identifiers and to indicate scene changes. The message specifies how the source pictures for the labelled pictures were created. The decoder may use the information to select an appropriate algorithm to conceal transmission errors. For example, a specific algorithm may be used to conceal transmission errors that occurred in pictures belonging to a gradual scene transition. Furthermore, the scene information SEI message may be used in a manner determined by the application, such as for indexing the scenes of a coded sequence. + +A scene information SEI message labels all pictures, in decoding order, from the primary coded picture to which the SEI message is associated (inclusive), as specified in clause 7.4.1.2.3, to the primary coded picture to which the next scene information SEI message (if present) in decoding order is associated (exclusive) or (otherwise) to the last access unit in the bitstream (inclusive). These pictures are herein referred to as the target pictures. + +**scene\_info\_present\_flag** equal to 0 indicates that the scene or scene transition to which the target pictures belong is unspecified. **scene\_info\_present\_flag** equal to 1 indicates that the target pictures belong to the same scene or scene transition. + +**scene\_id** identifies the scene to which the target pictures belong. When the value of **scene\_transition\_type** of the target pictures is less than 4, and the previous picture in output order is marked with a value of **scene\_transition\_type** less than 4, and the value of **scene\_id** is the same as the value of **scene\_id** of the previous picture in output order, this indicates that the source scene for the target pictures and the source scene for the previous picture (in output order) are considered by the encoder to have been the same scene. When the value of **scene\_transition\_type** of the target pictures is greater than 3, and the previous picture in output order is marked with a value of **scene\_transition\_type** less than 4, and the value of **scene\_id** is the same as the value of **scene\_id** of the previous picture in output order, this indicates that one of the source scenes for the target pictures and the source scene for the previous picture (in output order) are considered by the encoder to have been the same scene. When the value of **scene\_id** is not equal to the value of **scene\_id** of the previous picture in output order, this indicates that the target pictures and the previous picture (in output order) are considered by the encoder to have been from different source scenes. + +The value of **scene\_id** shall be in the range of 0 to $2^{32} - 2$ , inclusive. + +Values of **scene\_id** in the range of 0 to 255, inclusive, and in the range of 512 to $2^{31} - 1$ , inclusive, may be used as determined by the application. Values of **scene\_id** in the range of 256 to 511, inclusive, and in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of **scene\_id** in the range of 256 to 511, inclusive, or in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, shall ignore (remove from the bitstream and discard) it. + +**scene\_transition\_type** specifies in which type of a scene transition (if any) the target pictures are involved. The valid values of **scene\_transition\_type** are specified in Table D-4. + +**Table D-4 – scene\_transition\_type values** + +| Value | Description | +|-------|---------------------------------------------------| +| 0 | No transition | +| 1 | Fade to black | +| 2 | Fade from black | +| 3 | Unspecified transition from or to constant colour | +| 4 | Dissolve | +| 5 | Wipe | +| 6 | Unspecified mixture of two scenes | + +When **scene\_transition\_type** is greater than 3, the target pictures include contents both from the scene labelled by its **scene\_id** and the next scene, in output order, which is labelled by **second\_scene\_id** (see below). The term "the current + +scene" is used to indicate the scene labelled by `scene_id`. The term "the next scene" is used to indicate the scene labelled by `second_scene_id`. It is not required for any following picture, in output order, to be labelled with `scene_id` equal to `second_scene_id` of the current SEI message. + +Scene transition types are specified as follows. + +"No transition" specifies that the target pictures are not involved in a gradual scene transition. + +NOTE 2 – When two consecutive pictures in output order have `scene_transition_type` equal to 0 and different values of `scene_id`, a scene cut occurred between the two pictures. + +"Fade to black" indicates that the target pictures are part of a sequence of pictures, in output order, involved in a fade to black scene transition, i.e., the luma samples of the scene gradually approach zero and the chroma samples of the scene gradually approach 128. + +NOTE 3 – When two pictures are labelled to belong to the same scene transition and their `scene_transition_type` is "Fade to black", the later one, in output order, is darker than the previous one. + +"Fade from black" indicates that the target pictures are part of a sequence of pictures, in output order, involved in a fade from black scene transition, i.e., the luma samples of the scene gradually diverge from zero and the chroma samples of the scene may gradually diverge from 128. + +NOTE 4 – When two pictures are labelled to belong to the same scene transition and their `scene_transition_type` is "Fade from black", the later one in output order is lighter than the previous one. + +"Dissolve" indicates that the sample values of each target picture (before encoding) were generated by calculating a sum of co-located weighted sample values of a picture from the current scene and a picture from the next scene. The weight of the current scene gradually decreases from full level to zero level, whereas the weight of the next scene gradually increases from zero level to full level. When two pictures are labelled to belong to the same scene transition and their `scene_transition_type` is "Dissolve", the weight of the current scene for the later one, in output order, is less than the weight of the current scene for the previous one, and the weight of the next scene for the later one, in output order, is greater than the weight of the next scene for the previous one. + +"Wipe" indicates that some of the sample values of each target picture (before encoding) were generated by copying co-located sample values of a picture in the current scene and the remaining sample values of each target picture (before encoding) were generated by copying co-located sample values of a picture in the next scene. When two pictures are labelled to belong to the same scene transition and their `scene_transition_type` is "Wipe", the number of samples copied from the next scene to the later picture in output order is greater than the number of samples copied from the next scene to the previous picture. + +**`second_scene_id`** identifies the next scene in the gradual scene transition in which the target pictures are involved. The value of `second_scene_id` shall not be equal to the value of `scene_id`. The value of `second_scene_id` shall not be equal to the value of `scene_id` in the previous picture in output order. When the next picture in output order is marked with a value of `scene_transition_type` less than 4, and the value of `second_scene_id` is the same as the value of `scene_id` of the next picture in output order, this indicates that the encoder considers one of the source scenes for the target pictures and the source scene for the next picture (in output order) to have been the same scene. When the value of `second_scene_id` is not equal to the value of `scene_id` or `second_scene_id` (if present) of the next picture in output order, this indicates that the encoder considers the target pictures and the next picture (in output order) to have been from different source scenes. + +When the value of `scene_id` of a picture is equal to the value of `scene_id` of the following picture in output order and the value of `scene_transition_type` in both of these pictures is less than 4, this indicates that the encoder considers the two pictures to have been from the same source scene. When the values of `scene_id`, `scene_transition_type` and `second_scene_id` (if present) of a picture are equal to the values of `scene_id`, `scene_transition_type` and `second_scene_id` (respectively) of the following picture in output order and the value of `scene_transition_type` is greater than 0, this indicates that the encoder considers the two pictures to have been from the same source gradual scene transition. + +The value of `second_scene_id` shall be in the range of 0 to $2^{32} - 2$ , inclusive. + +Values of `second_scene_id` in the range of 0 to 255, inclusive, and in the range of 512 to $2^{31} - 1$ , inclusive, may be used as determined by the application. Values of `second_scene_id` in the range of 256 to 511, inclusive, and in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of `second_scene_id` in the range of 256 to 511, inclusive, or in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, shall ignore (remove from the bitstream and discard) it. + +#### D.2.12 Sub-sequence information SEI message semantics + +The sub-sequence information SEI message is used to indicate the position of a picture in data dependency hierarchy that consists of sub-sequence layers and sub-sequences. + +A sub-sequence layer contains a subset of the coded pictures in a sequence. Sub-sequence layers are numbered with non-negative integers. A layer having a larger layer number is a higher layer than a layer having a smaller layer number. + +The layers are ordered hierarchically based on their dependency on each other so that any picture in a layer shall not be predicted from any picture on any higher layer. + +NOTE 1 – In other words, any picture in layer 0 must not be predicted from any picture in layer 1 or above, pictures in layer 1 may be predicted from layer 0, pictures in layer 2 may be predicted from layers 0 and 1, etc. + +NOTE 2 – The subjective quality is expected to increase along with the number of decoded layers. + +A sub-sequence is a set of coded pictures within a sub-sequence layer. A picture shall reside in one sub-sequence layer and in one sub-sequence only. Any picture in a sub-sequence shall not be predicted from any picture in another sub-sequence in the same or in a higher sub-sequence layer. A sub-sequence in layer 0 can be decoded independently of any picture that does not belong to the sub-sequence. + +The sub-sequence information SEI message concerns the current access unit. The primary coded picture in the access unit is herein referred to as the current picture. + +The sub-sequence information SEI message shall not be present unless gaps\_in\_frame\_num\_value\_allowed\_flag in the sequence parameter set referenced by the picture associated with the sub-sequence SEI message is equal to 1. + +**sub\_seq\_layer\_num** specifies the sub-sequence layer number of the current picture. When sub\_seq\_layer\_num is greater than 0, memory management control operations shall not be used in any slice header of the current picture. When the current picture resides in a sub-sequence for which the first picture in decoding order is an IDR picture, the value of sub\_seq\_layer\_num shall be equal to 0. For a non-paired reference field, the value of sub\_seq\_layer\_num shall be equal to 0. sub\_seq\_layer\_num shall be in the range of 0 to 255, inclusive. + +**sub\_seq\_id** identifies the sub-sequence within a layer. When the current picture resides in a sub-sequence for which the first picture in decoding order is an IDR picture, the value of sub\_seq\_id shall be the same as the value of idr\_pic\_id of the IDR picture. sub\_seq\_id shall be in the range of 0 to 65535, inclusive. + +**first\_ref\_pic\_flag** equal to 1 specifies that the current picture is the first reference picture of the sub-sequence in decoding order. When the current picture is not the first picture of the sub-sequence in decoding order, the first\_ref\_pic\_flag shall be equal to 0. + +**leading\_non\_ref\_pic\_flag** equal to 1 specifies that the current picture is a non-reference picture preceding any reference picture in decoding order within the sub-sequence or that the sub-sequence contains no reference pictures. When the current picture is a reference picture or the current picture is a non-reference picture succeeding at least one reference picture in decoding order within the sub-sequence, the leading\_non\_ref\_pic\_flag shall be equal to 0. + +**last\_pic\_flag** equal to 1 indicates that the current picture is the last picture of the sub-sequence (in decoding order), including all reference and non-reference pictures of the sub-sequence. When the current picture is not the last picture of the sub-sequence (in decoding order), last\_pic\_flag shall be equal to 0. + +The current picture is assigned to a sub-sequence as follows: + +- If one or more of the following conditions are true, the current picture is the first picture of a sub-sequence in decoding order: + - no earlier picture in decoding order is labelled with the same values of sub\_seq\_id and sub\_seq\_layer\_num as the current picture, + - the value of leading\_non\_ref\_pic\_flag is equal to 1 and the value of leading\_non\_ref\_pic\_flag is equal to 0 in the previous picture in decoding order having the same values of sub\_seq\_id and sub\_seq\_layer\_num as the current picture, + - the value of first\_ref\_pic\_flag is equal to 1 and the value of leading\_non\_ref\_pic\_flag is equal to 0 in the previous picture in decoding order having the same values of sub\_seq\_id and sub\_seq\_layer\_num as the current picture, + - the value of last\_pic\_flag is equal to 1 in the previous picture in decoding order having the same values of sub\_seq\_id and sub\_seq\_layer\_num as the current picture. +- Otherwise, the current picture belongs to the same sub-sequence as the previous picture in decoding order having the same values of sub\_seq\_id and sub\_seq\_layer\_num as the current picture. + +**sub\_seq\_frame\_num\_flag** equal to 0 specifies that sub\_seq\_frame\_num is not present. sub\_seq\_frame\_num\_flag equal to 1 specifies that sub\_seq\_frame\_num is present. + +**sub\_seq\_frame\_num** shall be equal to 0 for the first reference picture of the sub-sequence and for any non-reference picture preceding the first reference picture of the sub-sequence in decoding order. sub\_seq\_frame\_num is further constrained as follows: + +- If the current picture is not the second field of a complementary field pair, `sub_seq_frame_num` shall be incremented by 1, in modulo `MaxFrameNum` operation, relative to the previous reference picture, in decoding order, that belongs to the sub-sequence. +- Otherwise (the current picture is the second field of a complementary field pair), the value of `sub_seq_frame_num` shall be the same as the value of `sub_seq_frame_num` for the first field of the complementary field pair. + +`sub_seq_frame_num` shall be in the range of 0 to `MaxFrameNum` – 1, inclusive. + +When the current picture is an IDR picture, it shall start a new sub-sequence in sub-sequence layer 0. Thus, the `sub_seq_layer_num` shall be 0, the `sub_seq_id` shall be different from the previous sub-sequence in sub-sequence layer 0, `first_ref_pic_flag` shall be 1, and `leading_non_ref_pic_flag` shall be equal to 0. + +When the sub-sequence information SEI message is present for both coded fields of a complementary field pair, the values of `sub_seq_layer_num`, `sub_seq_id`, `leading_non_ref_pic_flag` and `sub_seq_frame_num`, when present, shall be the same for both of these pictures. + +When the sub-sequence information SEI message is present only for one coded field of a complementary field pair, the values of `sub_seq_layer_num`, `sub_seq_id`, `leading_non_ref_pic_flag` and `sub_seq_frame_num`, when present, are also applicable to the other coded field of the complementary field pair. + +#### D.2.13 Sub-sequence layer characteristics SEI message semantics + +The sub-sequence layer characteristics SEI message specifies the characteristics of sub-sequence layers. + +**num\_sub\_seq\_layers\_minus1** plus 1 specifies the number of sub-sequence layers in the sequence. `num_sub_seq_layers_minus1` shall be in the range of 0 to 255, inclusive. + +A pair of `average_bit_rate` and `average_frame_rate` characterizes each sub-sequence layer. The first pair of `average_bit_rate` and `average_frame_rate` specifies the characteristics of sub-sequence layer 0. When present, the second pair specifies the characteristics of sub-sequence layers 0 and 1 jointly. Each pair in decoding order specifies the characteristics for a range of sub-sequence layers from layer number 0 to the layer number specified by the layer loop counter. The values are in effect from the point they are decoded until an update of the values is decoded. + +**accurate\_statistics\_flag** equal to 1 indicates that the values of `average_bit_rate` and `average_frame_rate` are rounded from statistically correct values. `accurate_statistics_flag` equal to 0 indicates that the `average_bit_rate` and the `average_frame_rate` are estimates and may deviate somewhat from the correct values. + +When `accurate_statistics_flag` is equal to 0, the quality of the approximation used in the computation of the values of `average_bit_rate` and the `average_frame_rate` is chosen by the encoding process and is not specified by this Recommendation | International Standard. + +**average\_bit\_rate** indicates the average bit rate in units of 1000 bits per second. All NAL units in the range of sub-sequence layers specified above are taken into account in the calculation. The average bit rate is derived according to the access unit removal time specified in Annex C of the Recommendation | International Standard. In the following, `bTotal` is the number of bits in all NAL units succeeding a sub-sequence layer characteristics SEI message (including the bits of the NAL units of the current access unit) and preceding the next access unit (in decoding order) including a sub-sequence layer characteristics SEI message (if present) or the end of the stream (otherwise). $t_1$ is the removal time (in seconds) of the current access unit, and $t_2$ is the removal time (in seconds) of the latest access unit (in decoding order) before the next sub-sequence layer characteristics SEI message (if present) or the end of the stream (otherwise). + +When `accurate_statistics_flag` is equal to 1, the following conditions shall be fulfilled as follows: + +- If $t_1$ is not equal to $t_2$ , the following condition shall be true: + +$$\text{average\_bit\_rate} == \text{Round}(b\text{Total} \div ((t_2 - t_1) * 1000)) \quad (\text{D-6})$$ + +- Otherwise ( $t_1$ is equal to $t_2$ ), the following condition shall be true: + +$$\text{average\_bit\_rate} == 0 \quad (\text{D-7})$$ + +**average\_frame\_rate** indicates the average frame rate in units of frames/(256 seconds). All NAL units in the range of sub-sequence layers specified above are taken into account in the calculation. In the following, `fTotal` is the number of frames, complementary field pairs and non-paired fields between the current picture (inclusive) and the next sub-sequence layer characteristics SEI message (if present) or the end of the stream (otherwise). $t_1$ is the removal time (in seconds) of the current access unit, and $t_2$ is the removal time (in seconds) of the latest access unit (in decoding order) before the next sub-sequence layer characteristics SEI message (if present) or the end of the stream (otherwise). + +When `accurate_statistics_flag` is equal to 1, the following conditions shall be fulfilled as follows: + +- If $t_1$ is not equal to $t_2$ , the following condition shall be true: + +$$\text{average\_frame\_rate} == \text{Round}(f_{\text{Total}} * 256 \div (t_2 - t_1)) \quad (\text{D-8})$$ + +- Otherwise ( $t_1$ is equal to $t_2$ ), the following condition shall be true: + +$$\text{average\_frame\_rate} == 0 \quad (\text{D-9})$$ + +#### D.2.14 Sub-sequence characteristics SEI message semantics + +The sub-sequence characteristics SEI message indicates the characteristics of a sub-sequence. It also indicates inter prediction dependencies between sub-sequences. This message shall be contained in the first access unit in decoding order of the sub-sequence to which the sub-sequence characteristics SEI message applies. This sub-sequence is herein called the target sub-sequence. + +**sub\_seq\_layer\_num** identifies the sub-sequence layer number of the target sub-sequence. `sub_seq_layer_num` shall be in the range of 0 to 255, inclusive. + +**sub\_seq\_id** identifies the target sub-sequence. `sub_seq_id` shall be in the range of 0 to 65535, inclusive. + +**duration\_flag** equal to 0 indicates that the duration of the target sub-sequence is not specified. + +**sub\_seq\_duration** specifies the duration of the target sub-sequence in clock ticks of a 90-kHz clock. + +**average\_rate\_flag** equal to 0 indicates that the average bit rate and the average frame rate of the target sub-sequence are unspecified. + +**accurate\_statistics\_flag** indicates how reliable the values of `average_bit_rate` and `average_frame_rate` are. `accurate_statistics_flag` equal to 1, indicates that the `average_bit_rate` and the `average_frame_rate` are rounded from statistically correct values. `accurate_statistics_flag` equal to 0 indicates that the `average_bit_rate` and the `average_frame_rate` are estimates and may deviate from the statistically correct values. + +**average\_bit\_rate** indicates the average bit rate in (1000 bits)/second of the target sub-sequence. All NAL units of the target sub-sequence are taken into account in the calculation. The average bit rate is derived according to the access unit removal time specified in clause C.1.2. In the following, $nB$ is the number of bits in all NAL units in the sub-sequence. $t_1$ is the removal time (in seconds) of the first access unit of the sub-sequence (in decoding order), and $t_2$ is the removal time (in seconds) of the last access unit of the sub-sequence (in decoding order). + +When `accurate_statistics_flag` is equal to 1, the following conditions shall be fulfilled as follows: + +- If $t_1$ is not equal to $t_2$ , the following condition shall be true: + +$$\text{average\_bit\_rate} == \text{Round}(nB \div ((t_2 - t_1) * 1000)) \quad (\text{D-10})$$ + +- Otherwise ( $t_1$ is equal to $t_2$ ), the following condition shall be true: + +$$\text{average\_bit\_rate} == 0 \quad (\text{D-11})$$ + +**average\_frame\_rate** indicates the average frame rate in units of frames/(256 seconds) of the target sub-sequence. All NAL units of the target sub-sequence are taken into account in the calculation. The average frame rate is derived according to the access unit removal time specified in clause C.1.2. In the following, $fC$ is the number of frames, complementary field pairs and non-paired fields in the sub-sequence. $t_1$ is the removal time (in seconds) of the first access unit of the sub-sequence (in decoding order), and $t_2$ is the removal time (in seconds) of the last access unit of the sub-sequence (in decoding order). + +When `accurate_statistics_flag` is equal to 1, the following conditions shall be fulfilled as follows: + +- If $t_1$ is not equal to $t_2$ , the following condition shall be true: + +$$\text{average\_frame\_rate} == \text{Round}(fC * 256 \div (t_2 - t_1)) \quad (\text{D-12})$$ + +- Otherwise ( $t_1$ is equal to $t_2$ ), the following condition shall be true: + +$$\text{average\_frame\_rate} == 0 \quad (\text{D-13})$$ + +**num\_referenced\_subseqs** specifies the number of sub-sequences that contain pictures that are used as reference pictures for inter prediction in the pictures of the target sub-sequence. **num\_referenced\_subseqs** shall be in the range of 0 to 255, inclusive. + +**ref\_sub\_seq\_layer\_num**, **ref\_sub\_seq\_id**, and **ref\_sub\_seq\_direction** identify the sub-sequence that contains pictures that are used as reference pictures for inter prediction in the pictures of the target sub-sequence. Depending on **ref\_sub\_seq\_direction**, the following applies: + +- If **ref\_sub\_seq\_direction** is equal to 0, a set of candidate sub-sequences consists of the sub-sequences which have a value of **sub\_seq\_id** equal to **ref\_sub\_seq\_id**, which reside in the sub-sequence layer having **sub\_seq\_layer\_num** equal to **ref\_sub\_seq\_layer\_num**, and for which the first picture in decoding order precedes the first picture of the target sub-sequence in decoding order. +- Otherwise (**ref\_sub\_seq\_direction** is equal to 1), a set of candidate sub-sequences consists of the sub-sequences which have a value of **sub\_seq\_id** equal to **ref\_sub\_seq\_id**, which reside in the sub-sequence layer having **sub\_seq\_layer\_num** equal to **ref\_sub\_seq\_layer\_num**, and for which the first picture in decoding order succeeds the first picture of the target sub-sequence in decoding order. + +The sub-sequence used as a reference for the target sub-sequence is the sub-sequence among the set of candidate sub-sequences for which the first picture is the closest to the first picture of the target sub-sequence in decoding order. + +#### D.2.15 Full-frame freeze SEI message semantics + +The full-frame freeze SEI message indicates that the current picture and any subsequent pictures in output order that meet specified conditions should not affect the content of the display. No more than one full-frame freeze SEI message shall be present in any access unit. + +**full\_frame\_freeze\_repetition\_period** specifies the persistence of the full-frame freeze SEI message and may specify a picture order count interval within which another full-frame freeze SEI message or a full-frame freeze release SEI message or the end of the coded video sequence shall be present in the bitstream. The value of **full\_frame\_freeze\_repetition\_period** shall be in the range of 0 to 16 384, inclusive. + +**full\_frame\_freeze\_repetition\_period** equal to 0 specifies that the full-frame freeze SEI message applies to the current decoded picture only. + +**full\_frame\_freeze\_repetition\_period** equal to 1 specifies that the full-frame freeze SEI message persists in output order until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a full-frame freeze SEI message or a full-frame freeze release SEI message is output having **PicOrderCnt()** greater than **PicOrderCnt( CurrPic )**. + +**full\_frame\_freeze\_repetition\_period** greater than 1 specifies that the full-frame freeze SEI message persists until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a full-frame freeze SEI message or a full-frame freeze release SEI message is output having **PicOrderCnt()** greater than **PicOrderCnt( CurrPic )** and less than or equal to **PicOrderCnt( CurrPic ) + full\_frame\_freeze\_repetition\_period**. + +**full\_frame\_freeze\_repetition\_period** greater than 1 indicates that another full-frame freeze SEI message or a full-frame freeze release SEI message shall be present for a picture in an access unit that is output having **PicOrderCnt()** greater than **PicOrderCnt( CurrPic )** and less than or equal to **PicOrderCnt( CurrPic ) + full\_frame\_freeze\_repetition\_period**; unless the bitstream ends or a new coded video sequence begins without output of such a picture. + +#### D.2.16 Full-frame freeze release SEI message semantics + +The full-frame freeze release SEI message cancels the effect of any full-frame freeze SEI message sent with pictures that precede the current picture in output order. The full-frame freeze release SEI message indicates that the current picture and subsequent pictures in output order should affect the contents of the display. + +No more than one full-frame freeze release SEI message shall be present in any access unit. A full-frame freeze release SEI message shall not be present in an access unit containing a full-frame freeze SEI message. When a full-frame freeze SEI message is present in an access unit containing a field of a complementary field pair in which the values of **PicOrderCnt( CurrPic )** for the two fields of the complementary field pair are equal to each other, a full-frame freeze release SEI message shall not be present in either of the two access units. + +#### D.2.17 Full-frame snapshot SEI message semantics + +The full-frame snapshot SEI message indicates that the current frame is labelled for use as determined by the application as a still-image snapshot of the video content. + +**snapshot\_id** specifies a snapshot identification number. **snapshot\_id** shall be in the range of 0 to $2^{32} - 2$ , inclusive. + +Values of **snapshot\_id** in the range of 0 to 255, inclusive, and in the range of 512 to $2^{31} - 1$ , inclusive, may be used as determined by the application. Values of **snapshot\_id** in the range of 256 to 511, inclusive, and in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of **snapshot\_id** in the range of 256 to 511, inclusive, or in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, shall ignore (remove from the bitstream and discard) it. + +#### D.2.18 Progressive refinement segment start SEI message semantics + +The progressive refinement segment start SEI message specifies the beginning of a set of consecutive coded pictures that is labelled as the current picture followed by a sequence of one or more pictures of refinement of the quality of the current picture, rather than as a representation of a continually moving scene. + +The tagged set of consecutive coded pictures shall continue until one of the following conditions is true. When a condition below becomes true, the next slice to be decoded does not belong to the tagged set of consecutive coded pictures: + +- The next slice to be decoded belongs to an IDR picture. +- **num\_refinement\_steps\_minus1** is greater than 0 and the **frame\_num** of the next slice to be decoded is $(\text{currFrameNum} + \text{num\_refinement\_steps\_minus1} + 1) \% \text{MaxFrameNum}$ , where **currFrameNum** is the value of **frame\_num** of the picture in the access unit containing the SEI message. +- **num\_refinement\_steps\_minus1** is 0 and a progressive refinement segment end SEI message with the same **progressive\_refinement\_id** as the one in this SEI message is decoded. + +The decoding order of pictures within the tagged set of consecutive pictures should be the same as their output order. + +**progressive\_refinement\_id** specifies an identification number for the progressive refinement operation. **progressive\_refinement\_id** shall be in the range of 0 to $2^{32} - 2$ , inclusive. + +Values of **progressive\_refinement\_id** in the range of 0 to 255, inclusive, and in the range of 512 to $2^{31} - 1$ , inclusive, may be used as determined by the application. Values of **progressive\_refinement\_id** in the range of 256 to 511, inclusive, and in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of **progressive\_refinement\_id** in the range of 256 to 511, inclusive, or in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, shall ignore (remove from the bitstream and discard) it. + +**num\_refinement\_steps\_minus1** specifies the number of reference frames in the tagged set of consecutive coded pictures as follows: + +- If **num\_refinement\_steps\_minus1** is equal to 0, the number of reference frames in the tagged set of consecutive coded pictures is unknown. +- Otherwise, the number of reference frames in the tagged set of consecutive coded pictures is equal to **num\_refinement\_steps\_minus1** + 1. + +**num\_refinement\_steps\_minus1** shall be in the range of 0 to **MaxFrameNum** – 1, inclusive. + +#### D.2.19 Progressive refinement segment end SEI message semantics + +The progressive refinement segment end SEI message specifies the end of a set of consecutive coded pictures that has been labelled by use of a progressive refinement segment start SEI message as an initial picture followed by a sequence of one or more pictures of the refinement of the quality of the initial picture, and ending with the current picture. + +**progressive\_refinement\_id** specifies an identification number for the progressive refinement operation. **progressive\_refinement\_id** shall be in the range of 0 to $2^{32} - 2$ , inclusive. + +The progressive refinement segment end SEI message specifies the end of any progressive refinement segment previously started using a progressive refinement segment start SEI message with the same value of **progressive\_refinement\_id**. + +Values of **progressive\_refinement\_id** in the range of 0 to 255, inclusive, and in the range of 512 to $2^{31} - 1$ , inclusive, may be used as determined by the application. Values of **progressive\_refinement\_id** in the range of 256 to 511, inclusive, and in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of **progressive\_refinement\_id** in the range of 256 to 511, inclusive, or in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, shall ignore (remove from the bitstream and discard) it. + +#### D.2.20 Motion-constrained slice group set SEI message semantics + +NOTE 1 – The syntax of the motion-constrained slice group set SEI message is dependent on the content of the picture parameter set that is active for the primary coded picture associated with the motion-constrained slice group set SEI message. However, the activation of the associated picture parameter set does not occur until the decoding of the first coded slice NAL unit of the primary coded picture. Since the coded slice NAL units of the primary coded picture follow the motion-constrained slice group set SEI message in NAL unit order, it may be necessary for a decoder to store the RBSP containing the motion-constrained slice group set SEI message until determining the parameters of the picture parameter set that will be active for the primary coded picture, and then perform the parsing of the motion-constrained slice group set SEI message. + +This SEI message indicates that inter prediction over slice group boundaries is constrained as specified below. When present, the message shall only appear where it is associated, as specified in clause 7.4.1.2.3, with an IDR access unit. + +The target picture set for this SEI message contains all consecutive primary coded pictures in decoding order starting with the associated primary coded IDR picture (inclusive) and ending with the following primary coded IDR picture (exclusive) or with the very last primary coded picture in the bitstream (inclusive) in decoding order when there is no following primary coded IDR picture. The slice group set is a collection of one or more slice groups, identified by the `slice_group_id[ i ]` syntax element. When `separate_colour_plane_flag` is equal to 1, the term "primary coded pictures" represents the parts of the corresponding primary coded pictures that correspond to the NAL units having the same `colour_plane_id`. + +This SEI message indicates that, for each picture in the target picture set, the inter prediction process is constrained as follows: No sample value outside the slice group set, and no sample value at a fractional sample position that is derived using one or more sample values outside the slice group set is used for inter prediction of any sample within the slice group set. + +**num\_slice\_groups\_in\_set\_minus1** plus 1 specifies the number of slice groups in the slice group set. The allowed range of `num_slice_groups_in_set_minus1` is 0 to `num_slice_groups_minus1`, inclusive. The allowed range of `num_slice_groups_minus1` is specified in Annex A and clauses F.10 and G.10. + +**slice\_group\_id[ i ]** with `i = 0.. num_slice_groups_in_set_minus1` identifies the slice group(s) contained within the slice group set. The allowed range for `slice_group_id[ i ]` is from 0 to `num_slice_groups_minus1`, inclusive. The length of the `slice_group_id[ i ]` syntax element is $\text{Ceil}(\text{Log2}(\text{num\_slice\_groups\_minus1} + 1))$ bits. + +When `num_slice_groups_minus1` is equal to 0 (i.e., `num_slice_groups_in_set_minus1` is equal to 0 and `slice_group_id[ 0 ]` is not present), the value of `slice_group_id[ 0 ]` shall be inferred to be equal to 0. + +**exact\_sample\_value\_match\_flag** equal to 0 indicates that, within the target picture set, when the macroblocks that do not belong to the slice group set are not decoded, the value of each sample in the slice group set need not be exactly the same as the value of the same sample when all the macroblocks are decoded. `exact_sample_value_match_flag` equal to 1 indicates that, within the target picture set, when the macroblocks that do not belong to the slice group set are not decoded, the value of each sample in the slice group set shall be exactly the same as the value of the same sample when all the macroblocks in the target picture set are decoded. + +NOTE 2 – When `disable_deblocking_filter_idc` is equal to 1 or 2 in all slices in the target picture set, `exact_sample_value_match_flag` should be 1. + +**pan\_scan\_rect\_flag** equal to 0 specifies that `pan_scan_rect_id` is not present. `pan_scan_rect_flag` equal to 1 specifies that `pan_scan_rect_id` is present. + +**pan\_scan\_rect\_id** indicates that the specified slice group set covers at least the pan-scan rectangle identified by `pan_scan_rect_id` within the target picture set. + +NOTE 3 – Multiple `motion_constrained_slice_group_set` SEI messages may be associated with the same IDR picture. Consequently, more than one slice group set may be active within a target picture set. + +NOTE 4 – The size, shape, and location of the slice groups in the slice group set may change within the target picture set. + +#### D.2.21 Film grain characteristics SEI message semantics + +This SEI message provides the decoder with a parameterized model for a film grain synthesis process. The film grain synthesis process should be applied to the decoded pictures prior to their display. + +NOTE 1 – For example, an encoder could use the film grain characteristics SEI message to characterize film grain that was present in the original source video material and was removed by pre-processing filtering techniques. Synthesis of simulated film grain on the decoded images for the display process is optional and does not need to exactly follow the specified semantics of the film grain characteristics SEI message. When synthesis of simulated film grain on the decoded images for the display process is performed, there is no requirement that the method by which the synthesis is performed be the same as the parameterized model for the film grain as provided in the film grain characteristics SEI message. + +NOTE 2 – The display process is not specified in this Specification. + +NOTE 3 – Society of Motion Picture and Television Engineers document RDD 5 specifies a film grain simulator based on the information provided in the film grain characteristics SEI message. + +The film grain models specified in the film grain characteristics SEI message are expressed for application to decoded pictures that have 4:4:4 colour format with luma and chroma bit depths corresponding to the luma and chroma bit depths of the film grain model and use the same colour representation domain as the identified film grain model. When the colour format of the decoded video is not 4:4:4 or the decoded video uses a different luma or chroma bit depth from that of the film grain model or uses a different colour representation domain from that of the identified film grain model, an unspecified conversion process is expected to be applied to convert the decoded pictures to the form that is expressed for application of the film grain model. + +NOTE 4 – Because the use of a specific method is not required for performing the film grain generation function used by the display process, a decoder could, if desired, down-convert the model information for chroma in order to simulate film grain for other chroma formats (4:2:0 or 4:2:2) rather than up-converting the decoded video (using a method not specified in this Specification) before performing film grain generation. + +**film\_grain\_characteristics\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous film grain characteristics SEI message in output order. film\_grain\_characteristics\_cancel\_flag equal to 0 indicates that film grain modelling information follows. + +**film\_grain\_model\_id** identifies the film grain simulation model as specified in Table D-5. The value of film\_grain\_model\_id shall be in the range of 0 to 1, inclusive. The values of 2 and 3 for film\_grain\_model\_id are reserved for future use by ITU-T | ISO/IEC and shall not be present in bitstreams conforming to this version of this Specification. Decoders shall ignore film grain characteristic SEI messages with film\_grain\_model\_id equal to 2 or 3. + +**Table D-5 – film\_grain\_model\_id values** + +| Value | Description | +|-------|---------------------| +| 0 | frequency filtering | +| 1 | auto-regression | +| 2 | reserved | +| 3 | reserved | + +**separate\_colour\_description\_present\_flag** equal to 1 indicates that a distinct combination of luma bit depth, chroma bit depth, video full range flag, colour primaries, transfer characteristics, and matrix coefficients for the film grain characteristics specified in the SEI message is present in the film grain characteristics SEI message syntax. separate\_colour\_description\_present\_flag equal to 0 indicates that the combination of luma bit depth, chroma bit depth, video full range flag, colour primaries, transfer characteristics, and matrix coefficients for the film grain characteristics specified in the SEI message are the same as indicated in the VUI parameters for the coded video sequence. + +NOTE 5 – When separate\_colour\_description\_present\_flag is equal to 1, any of the luma bit depth, chroma bit depth, video full range flag, colour primaries, transfer characteristics, and matrix coefficients specified for the film grain characteristics specified in the SEI message could differ from those for the pictures in the coded video sequence. + +When VUI parameters are not present for the coded video sequence or the value of colour\_description\_present\_flag is equal to 0, and equivalent information to that conveyed when colour\_description\_present\_flag is equal to 1 is not conveyed by external means, separate\_colour\_description\_present\_flag shall be equal to 1. + +The decoded image $I_{\text{decoded}}$ used in the equations in this clause is in the same colour representation domain as the simulated film grain signal. Therefore, when any of these parameters does differ from that for the pictures in the coded video sequence, the decoded image $I_{\text{decoded}}$ used in the equations in this clause would be in a different colour representation domain than that for the pictures in the coded video sequence. For example, when the value of film\_grain\_bit\_depth\_luma\_minus8 + 8 is greater than the bit depth of the luma component of the pictures in the coded video sequence, the bit depth of $I_{\text{decoded}}$ used in the equations in this clause is also greater than the bit depth of the luma component of the pictures in the coded video sequence. In such a case, the decoded image $I_{\text{decoded}}$ corresponding to an actual decoded picture would be generated by converting the actual decoded picture to be in the same colour representation domain as the simulated film grain signal. The process for converting the actual decoded pictures to the 4:4:4 colour format with the same colour representation domain as the simulated film grain signal is not specified in this Specification. + +**film\_grain\_bit\_depth\_luma\_minus8** plus 8 specifies the bit depth used for the luma component of the film grain characteristics specified in the SEI message. When film\_grain\_bit\_depth\_luma\_minus8 is not present in the film grain characteristics SEI message, the value of film\_grain\_bit\_depth\_luma\_minus8 is inferred to be equal to bit\_depth\_luma\_minus8. + +The value of filmGrainBitDepth[ 0 ] is derived as follows: + +$$\text{filmGrainBitDepth}[ 0 ] = \text{film\_grain\_bit\_depth\_luma\_minus8} + 8 \quad (\text{D-14})$$ + +**film\_grain\_bit\_depth\_chroma\_minus8** plus 8 specifies the bit depth used for the Cb and Cr components of the film grain characteristics specified in the SEI message. When **film\_grain\_bit\_depth\_chroma\_minus8** is not present in the film grain characteristics SEI message, the value of **film\_grain\_bit\_depth\_chroma\_minus8** is inferred to be equal to **bit\_depth\_chroma\_minus8**. + +The value of **filmGrainBitDepth[ c ]** for **c = 1** and **2** is derived as follows: + +$$\text{filmGrainBitDepth[ c ]} = \text{film\_grain\_bit\_depth\_chroma\_minus8} + 8 \quad \text{with } c = 1, 2 \quad (\text{D-15})$$ + +**film\_grain\_full\_range\_flag** has the same semantics as specified in clause E.2.1 for the **video\_full\_range\_flag** syntax element, except as follows: + +- **film\_grain\_full\_range\_flag** specifies the video full range flag of the film grain characteristics specified in the SEI message, rather than the video full range flag used for the coded video sequence. +- When **film\_grain\_full\_range\_flag** is not present in the film grain characteristics SEI message, the value of **film\_grain\_full\_range\_flag** is inferred to be equal to **video\_full\_range\_flag**. + +**film\_grain\_colour\_primaries** has the same semantics as specified in clause E.2.1 for the **colour\_primaries** syntax element, except as follows: + +- **film\_grain\_colour\_primaries** specifies the colour primaries of the film grain characteristics specified in the SEI message, rather than the colour primaries used for the coded video sequence. +- When **film\_grain\_colour\_primaries** is not present in the film grain characteristics SEI message, the value of **film\_grain\_colour\_primaries** is inferred to be equal to **colour\_primaries**. + +**film\_grain\_transfer\_characteristics** has the same semantics as specified in clause E.2.1 for the **transfer\_characteristics** syntax element, except as follows: + +- **film\_grain\_transfer\_characteristics** specifies the transfer characteristics of the film grain characteristics specified in the SEI message, rather than the transfer characteristics used for the coded video sequence. +- When **film\_grain\_transfer\_characteristics** is not present in the film grain characteristics SEI message, the value of **film\_grain\_transfer\_characteristics** is inferred to be equal to **transfer\_characteristics**. + +**film\_grain\_matrix\_coefficients** has the same semantics as specified in clause E.2.1 for the **matrix\_coefficients** syntax element, except as follows: + +- **film\_grain\_matrix\_coefficients** specifies the matrix coefficients of the film grain characteristics specified in the SEI message, rather than the matrix coefficients used for the coded video sequence. +- When **film\_grain\_matrix\_coefficients** is not present in the film grain characteristics SEI message, the value of **film\_grain\_matrix\_coefficients** is inferred to be equal to **matrix\_coefficients**. +- The values allowed for **film\_grain\_matrix\_coefficients** are not constrained by the chroma format of the decoded pictures that is indicated by the value of **chroma\_format\_idc** for the semantics of the VUI parameters. + +**film\_grain\_matrix\_coefficients** shall not be equal to 0, 16, or 17 unless **film\_grain\_bit\_depth\_luma\_minus8** is equal to **film\_grain\_bit\_depth\_chroma\_minus8**. + +**film\_grain\_matrix\_coefficients** shall not be equal to 8 unless one of the following conditions is true: + +- **film\_grain\_bit\_depth\_luma\_minus8** is equal to **film\_grain\_bit\_depth\_chroma\_minus8**. +- **film\_grain\_bit\_depth\_chroma\_minus8** is equal to **film\_grain\_bit\_depth\_luma\_minus8** + 1. + +**blending\_mode\_id** identifies the blending mode used to blend the simulated film grain with the decoded images as specified in Table D-6. **blending\_mode\_id** shall be in the range of 0 to 1, inclusive. The values of 2 and 3 for **blending\_mode\_id** are reserved for future use by ITU-T | ISO/IEC and shall not be present in bitstreams conforming to this version of this Specification. Decoders shall ignore film grain characteristic SEI messages with **blending\_mode\_id** equal to 2 or 3. + +**Table D-6 – blending\_mode\_id values** + +| Value | Description | +|-------|----------------| +| 0 | additive | +| 1 | multiplicative | +| 2 | reserved | +| 3 | reserved | + +Depending on the value of `blending_mode_id`, the blending mode is specified as follows: + +- If `blending_mode_id` is equal to 0 the blending mode is additive as specified by + +$$I_{\text{grain}}[c][x][y] = \text{Clip3}(0, (1 \ll \text{filmGrainBitDepth}[c]) - 1, I_{\text{decoded}}[c][x][y] + G[c][x][y]) \quad (\text{D-16})$$ + +- Otherwise (`blending_mode_id` is equal to 1), the blending mode is multiplicative as specified by + +$$I_{\text{grain}}[c][x][y] = \text{Clip3}(0, (1 \ll \text{filmGrainBitDepth}[c]) - 1, I_{\text{decoded}}[c][x][y] + \text{Round}((I_{\text{decoded}}[c][x][y] * G[c][x][y]) \div ((1 \ll \text{bitDepth}[c]) - 1))) \quad (\text{D-17})$$ + +where `Idecoded[c][x][y]` represents the sample value at coordinates `(x, y)` of the colour component `c` of the decoded image `Idecoded`, `G[c][x][y]` is the simulated film grain value at the same position and colour component, and `filmGrainBitDepth[c]` is the number of bits used for each sample in a fixed-length unsigned binary representation of the arrays `Igrain[c][x][y]`, `Idecoded[c][x][y]`, and `G[c][x][y]`, where `c = 0..2`, `x = 0..PicWidthInSamplesL - 1`, and `y = 0..PicHeightInSamplesL - 1` + +**log2\_scale\_factor** specifies a scale factor used in the film grain characterization equations. + +**comp\_model\_present\_flag[c]** equal to 0 indicates that film grain is not modelled on the `c`-th colour component, where `c` equal to 0 refers to the luma component, `c` equal to 1 refers to the Cb component, and `c` equal to 2 refers to the Cr component. `comp_model_present_flag[c]` equal to 1 indicates that syntax elements specifying modelling of film grain on colour component `c` are present in the SEI message. + +When `separate_colour_description_present_flag` is equal to 0 and `chroma_format_idc` is equal to 0, the value of `comp_model_present_flag[1]` and `comp_model_present_flag[2]` shall be equal to 0. + +**num\_intensity\_intervals\_minus1[c]** plus 1 specifies the number of intensity intervals for which a specific set of model values has been estimated. + +NOTE 6 – The intensity intervals could overlap in order to simulate multi-generational film grain. + +**num\_model\_values\_minus1[c]** plus 1 specifies the number of model values present for each intensity interval in which the film grain has been modelled. The value of `num_model_values_minus1[c]` shall be in the range of 0 to 5, inclusive. + +**intensity\_interval\_lower\_bound[c][i]** specifies the lower bound of the `i`-th intensity interval for which the set of model values applies. + +**intensity\_interval\_upper\_bound[c][i]** specifies the upper bound of the `i`-th intensity interval for which the set of model values applies. + +The variable `intensityIntervalIdx[c][x][y][j]` represents the `j`-th index to the list of intensity intervals selected for the sample value `Idecoded[c][x][y]` for `c = 0..2`, `x = 0..PicWidthInSamplesL - 1`, `y = 0..PicHeightInSamplesL - 1`, and `j = 0..numApplicableIntensityIntervals[c][x][y] - 1`, where `numApplicableIntensityIntervals[c][x][y]` is derived below. + +Depending on the value of `film_grain_model_id`, the selection of one or more intensity intervals for the sample value `Idecoded[c][x][y]` is specified as follows: + +- The variable `numApplicableIntensityIntervals[c][x][y]` is initially set equal to 0. +- If `film_grain_model_id` is equal to 0, the following applies: + - The top-left sample location `(xB, yB)` of the current 8x8 block `b` that contains the sample value `Idecoded[c][x][y]` is derived as `(xB, yB) = (x / 8, y / 8)`. + - The average value `bavg` of the current 8x8 block `b` is derived as follows: + +$$\begin{aligned} \text{sum8x8} &= 0 \\ \text{for}(i = 0; i < 8; i++) \\ \quad \text{for}(j = 0; j < 8; j++) \\ \quad \quad \text{sum8x8} &+= I_{\text{decoded}}[c][xB * 8 + i][yB * 8 + j] \\ \text{b}_{\text{avg}} &= \text{Clip3}(0, 255, (\text{sum8x8} + (1 \ll (\text{filmGrainBitDepth}[c] - 3)))) \gg (\text{filmGrainBitDepth}[c] - 2) \end{aligned} \quad (\text{D-18})$$ + +- The values of `intensityIntervalIdx[c][x][y][j]` and `numApplicableIntensityIntervals[c][x][y]` are derived as follows: + +``` + +for( i = 0, j = 0; i <= num_intensity_intervals_minus1[ c ]; i++ ) + if( b_avg >= intensity_interval_lower_bound[ c ][ i ] && + b_avg <= intensity_interval_upper_bound[ c ][ i ] ) { + intensityIntervalIdx[ c ][ x ][ y ][ j ] = i + j++ + } +numApplicableIntensityIntervals[ c ][ x ][ y ] = j + +``` + +(D-19) + +- Otherwise (film\_grain\_model\_id is equal to 1), the values of intensityIntervalIdx[ c ][ x ][ y ][ j ] and numApplicableIntensityIntervals[ c ][ x ][ y ] are derived as follows: + +``` + +Is[ c ][ x ][ y ] = ( filmGrainBitDepth[ c ] == 8 ) ? ( Idecoded[ c ][ x ][ y ] : + Clip3( 0, 255, ( Idecoded[ c ][ x ][ y ] + + ( 1 << ( filmGrainBitDepth[ c ] - 9 ) ) ) >> ( filmGrainBitDepth[ c ] - 8 ) ) ) +for( i = 0, j = 0; i <= num_intensity_intervals_minus1[ c ]; i++ ) + if( Is[ c ][ x ][ y ] >= intensity_interval_lower_bound[ c ][ i ] && + Is[ c ][ x ][ y ] <= intensity_interval_upper_bound[ c ][ i ] ) { + intensityIntervalIdx[ c ][ x ][ y ][ j ] = i + j++ + } +numApplicableIntensityIntervals[ c ][ x ][ y ] = j + +``` + +(D-20) + +Samples that do not fall into any of the defined intervals (i.e., those samples for which the value of numApplicableIntensityIntervals[ c ][ x ][ y ] is equal to 0) are not modified by the grain generation function. Samples that fall into more than one interval (i.e., those samples for which the value of numApplicableIntensityIntervals[ c ][ x ][ y ] is greater than 1) will originate multi-generation grain. Multi-generation grain results from adding the grain computed independently for each of the applicable intensity intervals. + +In the equations in the remainder of this clause, the variable sj in each instance of the list comp\_model\_value[ c ][ sj ] is the value of intensityIntervalIdx[ c ][ x ][ y ][ j ] derived for the sample value Idecoded[ c ][ x ][ y ]. + +**comp\_model\_value**[ c ][ i ][ j ] specifies the j-th model value present for the colour component c and the i-th intensity interval. The set of model values has different meaning depending on the value of film\_grain\_model\_id. The value of comp\_model\_value[ c ][ i ][ j ] is constrained as follows, and could be additionally constrained as specified elsewhere in this clause. + +- If film\_grain\_model\_id is equal to 0, comp\_model\_value[ c ][ i ][ j ] shall be in the range of 0 to 2filmGrainBitDepth[ c ] - 1 - 1, inclusive. +- Otherwise (film\_grain\_model\_id is equal to 1), comp\_model\_value[ c ][ i ][ j ] shall be in the range of -2( filmGrainBitDepth[ c ] - 1 ) to 2( filmGrainBitDepth[ c ] - 1 ) - 1, inclusive. + +Depending on the value of film\_grain\_model\_id, the synthesis of the film grain is modelled as follows: + +- If film\_grain\_model\_id is equal to 0, a frequency filtering model enables simulating the original film grain for c = 0..2, x = 0..PicWidthInSamplesL - 1, and y = 0..PicHeightInSamplesL - 1 as specified by: + +$$G[ c ][ x ][ y ] = ( \text{comp\_model\_value}[ c ][ s_j ][ 0 ] * Q[ c ][ x ][ y ] + \text{comp\_model\_value}[ c ][ s_j ][ 5 ] * G[ c - 1 ][ x ][ y ] ) \gg \text{log2\_scale\_factor} \quad (D-21)$$ + +where Q[ c ] is a two-dimensional random process generated by filtering 16x16 blocks gaussRv with random-variable elements gaussRvij generated with a normalized Gaussian distribution (independent and identically distributed Gaussian random variable samples with zero mean and unity variance) and the value of an element G[ c - 1 ][ x ][ y ] used in the right-hand side of the equation is inferred to be equal to 0 when c - 1 is less than 0. + +NOTE 7 – A normalized Gaussian random variable can be generated from two independent, uniformly distributed random variables over the interval from 0 to 1 (and not equal to 0), denoted as uRv0 and uRv1, using the Box-Muller transformation specified by + +$$\text{gaussRv}_{ij} = \text{Sqrt}( -2 * \text{Ln}( \text{uRv}_0 ) ) * \text{Cos}( 2 * \pi * \text{uRv}_1 ) \quad (D-22)$$ + +where π is Archimedes' constant 3.141 592 653 589 793.... + +The band-pass filtering of blocks gaussRv can be performed in the discrete cosine transform (DCT) domain as follows: + +``` +for( y = 0; y < 16; y++ ) + for( x = 0; x < 16; x++ ) + if( ( x < comp_model_value[ c ][ sj ][ 3 ] && y < comp_model_value[ c ][ sj ][ 4 ] ) || + ( x > comp_model_value[ c ][ sj ][ 1 ] || y > comp_model_value[ c ][ sj ][ 2 ] ) ) + gaussRv[ x ][ y ] = 0 +filteredRv = IDCT16x16( gaussRv ) +``` + +(D-23) + +where IDCT16x16( z ) refers to a unitary inverse discrete cosine transformation (IDCT) operating on a 16x16 matrix argument z as specified by + +$$\text{IDCT16x16}(z) = r * z * r^T \quad (\text{D-24})$$ + +where the superscript T indicates a matrix transposition and r is the 16x16 matrix with elements $r_{ij}$ specified by + +$$r_{ij} = \frac{(i == 0) ? 1 : \text{Sqrt}(2)}{4} * \text{Cos}\left(\frac{i * (2 * j + 1) * \pi}{32}\right) \quad (\text{D-25})$$ + +where $\pi$ is Archimedes' constant 3.141 592 653 589 793.... + +Q[ c ] is formed by the frequency-filtered blocks filteredRv. + +NOTE 8 – Coded model values are based on blocks of size 16x16, but a decoder implementation could use other block sizes. For example, decoders implementing the IDCT on 8x8 blocks could down-convert by a factor of two the set of coded model values $\text{comp\_model\_value}[ c ][ sj ][ i ]$ for i equal to 1..4. + +NOTE 9 – To reduce the degree of visible blocks that can result from mosaicking the frequency-filtered blocks filteredRv, decoders could apply a low-pass filter to the boundaries between frequency-filtered blocks. + +- Otherwise (film\_grain\_model\_id is equal to 1), an auto-regression model enables simulating the original film grain for $c = 0..2$ , $x = 0..PicWidthInSamples_L - 1$ , and $y = 0..PicHeightInSamples_L - 1$ as specified by + +``` +G[ c ][ x ][ y ] = ( comp_model_value[ c ][ sj ][ 0 ] * n[ c ][ x ][ y ] + + comp_model_value[ c ][ sj ][ 1 ] * ( G[ c ][ x - 1 ][ y ] + + ( ( comp_model_value[ c ][ sj ][ 4 ] * G[ c ][ x ][ y - 1 ] ) >> + log2_scale_factor ) + comp_model_value[ c ][ sj ][ 3 ] * + ( ( comp_model_value[ c ][ sj ][ 4 ] * ( G[ c ][ x - 1 ][ y - 1 ] + G[ c ][ x + 1 ][ y - 1 ] ) ) >> + log2_scale_factor ) + + comp_model_value[ c ][ sj ][ 5 ] * ( G[ c ][ x - 2 ][ y ] + + ( ( comp_model_value[ c ][ sj ][ 4 ] * comp_model_value[ c ][ sj ][ 4 ] * G[ c ][ x ][ y - 2 ] ) >> + ( 2 * log2_scale_factor ) ) + + comp_model_value[ c ][ sj ][ 2 ] * G[ c - 1 ][ x ][ y ] ) >> log2_scale_factor +``` + +(D-26) + +where $n[ c ][ x ][ y ]$ is a random variable with normalized Gaussian distribution (independent and identically distributed Gaussian random variable samples with zero mean and unity variance for each value of c, x, and y) and the value of an element $G[ c ][ x ][ y ]$ used in the right-hand side of the equation is inferred to be equal to 0 when any of the following conditions are true: + +- x is less than 0, +- y is less than 0, +- c is less than 0. + +$\text{comp\_model\_value}[ c ][ i ][ 0 ]$ provides the first model value for the model as specified by film\_grain\_model\_id. $\text{comp\_model\_value}[ c ][ i ][ 0 ]$ corresponds to the standard deviation of the Gaussian noise term in the generation functions specified in Equations D-21 through D-26. + +$\text{comp\_model\_value}[ c ][ i ][ 1 ]$ provides the second model value for the model as specified by film\_grain\_model\_id. When film\_grain\_model\_id is equal to 0, $\text{comp\_model\_value}[ c ][ i ][ 1 ]$ shall be greater than or equal to 0 and less than 16. + +When not present in the film grain characteristics SEI message, $\text{comp\_model\_value}[ c ][ i ][ 1 ]$ is inferred as follows: + +- If film\_grain\_model\_id is equal to 0, $\text{comp\_model\_value}[ c ][ i ][ 1 ]$ is inferred to be equal to 8. +- Otherwise (film\_grain\_model\_id is equal to 1), $\text{comp\_model\_value}[ c ][ i ][ 1 ]$ is inferred to be equal to 0. + +$\text{comp\_model\_value}[ c ][ i ][ 1 ]$ is interpreted as follows: + +- If `film_grain_model_id` is equal to 0, `comp_model_value[ c ][ i ][ 1 ]` indicates the horizontal high cut frequency to be used to filter the DCT of a block of 16x16 random variables. +- Otherwise (`film_grain_model_id` is equal to 1), `comp_model_value[ c ][ i ][ 1 ]` indicates the first order spatial correlation for neighbouring samples at positions $(x - 1, y)$ and $(x, y - 1)$ . + +`comp_model_value[ c ][ i ][ 2 ]` provides the third model value for the model as specified by `film_grain_model_id`. When `film_grain_model_id` is equal to 0, `comp_model_value[ c ][ i ][ 2 ]` shall be greater than or equal to 0 and less than 16. + +When not present in the film grain characteristics SEI message, `comp_model_value[ c ][ i ][ 2 ]` is inferred as follows: + +- If `film_grain_model_id` is equal to 0, `comp_model_value[ c ][ i ][ 2 ]` is inferred to be equal to `comp_model_value[ c ][ i ][ 1 ]` +- Otherwise (`film_grain_model_id` is equal to 1), `comp_model_value[ c ][ i ][ 2 ]` is inferred to be equal to 0. + +`comp_model_value[ c ][ i ][ 2 ]` is interpreted as follows: + +- If `film_grain_model_id` is equal to 0, `comp_model_value[ c ][ i ][ 2 ]` indicates the vertical high cut frequency to be used to filter the DCT of a block of 16x16 random variables. +- Otherwise (`film_grain_model_id` is equal to 1), `comp_model_value[ c ][ i ][ 2 ]` indicates the colour correlation between consecutive colour components. + +`comp_model_value[ c ][ i ][ 3 ]` provides the fourth model value for the model as specified by `film_grain_model_id`. When `film_grain_model_id` is equal to 0, `comp_model_value[ c ][ i ][ 3 ]` shall be greater than or equal to 0 and less than or equal to `comp_model_value[ c ][ i ][ 1 ]`. + +When not present in the film grain characteristics SEI message, `comp_model_value[ c ][ i ][ 3 ]` is inferred to be equal to 0. + +`comp_model_value[ c ][ i ][ 3 ]` is interpreted as follows: + +- If `film_grain_model_id` is equal to 0, `comp_model_value[ c ][ i ][ 3 ]` indicates the horizontal low cut frequency to be used to filter the DCT of a block of 16x16 random variables. +- Otherwise (`film_grain_model_id` is equal to 1), `comp_model_value[ c ][ i ][ 3 ]` indicates the first order spatial correlation for neighbouring samples at positions $(x - 1, y - 1)$ and $(x + 1, y - 1)$ . + +`comp_model_value[ c ][ i ][ 4 ]` provides the fifth model value for the model as specified by `film_grain_model_id`. When `film_grain_model_id` is equal to 0, `comp_model_value[ c ][ i ][ 4 ]` shall be greater than or equal to 0 and less than or equal to `comp_model_value[ c ][ i ][ 2 ]`. + +When not present in the film grain characteristics SEI message, `comp_model_value[ c ][ i ][ 4 ]` is inferred to be equal to `film_grain_model_id`. + +`comp_model_value[ c ][ i ][ 4 ]` is interpreted as follows: + +- If `film_grain_model_id` is equal to 0, `comp_model_value[ c ][ i ][ 4 ]` indicates the vertical low cut frequency to be used to filter the DCT of a block of 16x16 random variables. +- Otherwise (`film_grain_model_id` is equal to 1), `comp_model_value[ c ][ i ][ 4 ]` indicates the aspect ratio of the modelled grain. + +`comp_model_value[ c ][ i ][ 5 ]` provides the sixth model value for the model as specified by `film_grain_model_id`. + +When not present in the film grain characteristics SEI message, `comp_model_value[ c ][ i ][ 5 ]` is inferred to be equal to 0. + +`comp_model_value[ c ][ i ][ 5 ]` is interpreted as follows: + +- If `film_grain_model_id` is equal to 0, `comp_model_value[ c ][ i ][ 5 ]` indicates the colour correlation between consecutive colour components. +- Otherwise (`film_grain_model_id` is equal to 1), `comp_model_value[ c ][ i ][ 5 ]` indicates the second order spatial correlation for neighbouring samples at positions $(x, y - 2)$ and $(x - 2, y)$ . + +**film grain characteristics repetition period** specifies the persistence of the film grain characteristics SEI message and may specify a picture order count interval within which another film grain characteristics SEI message or the end of the coded video sequence shall be present in the bitstream. The value of `film_grain_characteristics_repetition_period` shall be in the range 0 to 16 384, inclusive. + +`film_grain_characteristics_repetition_period` equal to 0 specifies that the film grain characteristics SEI message applies to the current decoded picture only. + +film\_grain\_characteristics\_repetition\_period equal to 1 specifies that the film grain characteristics SEI message persists in output order until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a film grain characteristics SEI message is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ). + +film\_grain\_characteristics\_repetition\_period greater than 1 specifies that the film grain characteristics SEI message persists until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a film grain characteristics SEI message is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ) and less than or equal to PicOrderCnt( CurrPic ) + film\_grain\_characteristics\_repetition\_period. + +film\_grain\_characteristics\_repetition\_period greater than 1 indicates that another film grain characteristics SEI message shall be present for a picture in an access unit that is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ) and less than or equal to PicOrderCnt( CurrPic ) + film\_grain\_characteristics\_repetition\_period; unless the bitstream ends or a new coded video sequence begins without output of such a picture. + +#### D.2.22 Deblocking filter display preference SEI message semantics + +This SEI message provides the decoder with an indication of whether the display of the cropped result of the deblocking filter process specified in clause 8.7 or of the cropped result of the picture construction process prior to the deblocking filter process specified in clause 8.5.14 is preferred by the encoder for the display of each decoded picture that is output. + +NOTE 1 – The display process is not specified in this Recommendation | International Standard. The means by which an encoder determines what to indicate as its preference expressed in a deblocking filter display preference SEI message is also not specified in this Recommendation | International Standard, and the expression of an expressed preference in a deblocking filter display preference SEI message does not impose any requirement on the display process. + +**deblocking\_display\_preference\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous deblocking filter display preference SEI message in output order. **deblocking\_display\_preference\_cancel\_flag** equal to 0 indicates that a **display\_prior\_to\_deblocking\_preferred\_flag** and **deblocking\_display\_preference\_repetition\_period** follow. + +NOTE 2 – In the absence of the deblocking filter display preference SEI message, or after the receipt of a deblocking filter display preference SEI message in which **deblocking\_display\_preference\_cancel\_flag** is equal to 1, the decoder should infer that the display of the cropped result of the deblocking filter process specified in clause 8.7 is preferred over the display of the cropped result of the picture construction process prior to the deblocking filter process specified in clause 8.5.14 for the display of each decoded picture that is output. + +**display\_prior\_to\_deblocking\_preferred\_flag** equal to 1 indicates that the encoder preference is for the display process (which is not specified in this Recommendation | International Standard) to display the cropped result of the picture construction process prior to the deblocking filter process specified in clause 8.5.14 rather than the cropped result of the deblocking filter process specified in clause 8.7 for each picture that is cropped and output as specified in Annex C. **display\_prior\_to\_deblocking\_preferred\_flag** equal to 0 indicates that the encoder preference is for the display process (which is not specified in this Recommendation | International Standard) to display the cropped result of the deblocking filter process specified in clause 8.7 rather than the cropped result of the picture construction process prior to the deblocking filter process specified in clause 8.5.14 for each picture that is cropped and output as specified in Annex C. + +NOTE 3 – The presence or absence of the deblocking filter display preference SEI message and the value of **display\_prior\_to\_deblocking\_preferred\_flag** does not affect the requirements of the decoding process specified in this Recommendation | International Standard. Rather, it only provides an indication of when, in addition to fulfilling the requirements of this Recommendation | International Standard for the decoding process, enhanced visual quality might be obtained by performing the display process (which is not specified in this Recommendation | International Standard) in an alternative fashion. Encoders that use the deblocking filter display preference SEI message should be designed with an awareness that unless the encoder restricts its use of the DPB capacity specified in Annex A and clauses F.10 and G.10 for the profile and level in use, some decoders may not have sufficient memory capacity for the storage of the result of the picture construction process prior to the deblocking filter process specified in clause 8.5.14 in addition to the storage of the result of the deblocking filter process specified in clause 8.7 when reordering and delaying pictures for display, and such decoders would therefore not be able to benefit from the preference indication. By restricting its use of the DPB capacity, an encoder can be able to use at least half of the DPB capacity specified in Annex A and clauses F.10 and G.10 while allowing the decoder to use the remaining capacity for storage of unfiltered pictures that have been indicated as preferable for display until the output time arrives for those pictures. + +**dec\_frame\_buffering\_constraint\_flag** equal to 1 indicates that the use of the frame buffering capacity of the HRD decoded picture buffer (DPB) as specified by **max\_dec\_frame\_buffering** has been constrained such that the coded video sequence will not require a decoded picture buffer with more than $\text{Max}( 1, \text{max\_dec\_frame\_buffering} )$ frame buffers to enable the output of the decoded filtered or unfiltered pictures, as indicated by the deblocking filter display preference SEI messages, at the output times specified by the **dpb\_output\_delay** of the picture timing SEI messages. **dec\_frame\_buffering\_constraint\_flag** equal to 0 indicates that the use of the frame buffering capacity in the HRD may or may not be constrained in the manner that would be indicated by **dec\_frame\_buffering\_constraint\_flag** equal to 1. + +For purposes of determining the constraint imposed when **dec\_frame\_buffering\_constraint\_flag** is equal to 1, the quantity of frame buffering capacity used at any given point in time by each frame buffer of the DPB that contains a picture shall be derived as follows: + +- If both of the following criteria are satisfied for the frame buffer, the frame buffer is considered to use two frame buffers of capacity for its storage. + - The frame buffer contains a frame or one or more fields that is marked as "used for reference", and + - The frame buffer contains a picture for which both of the following criteria are fulfilled: + - The HRD output time of the picture is greater than the given point in time. + - It has been indicated in a deblocking filter display preference SEI message that the encoder preference for the picture is for the display process to display the cropped result of the picture construction process prior to the deblocking filter process specified in clause 8.5.14 rather than the cropped result of the deblocking filter process specified in clause 8.7. +- Otherwise, the frame buffer is considered to use one frame buffer of DPB capacity for its storage. + +When **dec\_frame\_buffering\_constraint\_flag** is equal to 1, the frame buffering capacity used by all of the frame buffers in the DPB that contain pictures, as derived in this manner, shall not be greater than $\text{Max}( 1, \text{max\_dec\_frame\_buffering} )$ during the operation of the HRD for the coded video sequence. + +The value of **dec\_frame\_buffering\_constraint\_flag** shall be the same in all deblocking filter display preference SEI messages of the coded video sequence. + +**deblocking\_display\_preference\_repetition\_period** specifies the persistence of the deblocking filter display preference SEI message and may specify a picture order count interval within which another deblocking filter display preference message or the end of the coded video sequence shall be present in the bitstream. The value of **deblocking\_display\_preference\_repetition\_period** shall be in the range 0 to 16 384, inclusive. + +**deblocking\_display\_preference\_repetition\_period** equal to 0 specifies that the deblocking filter display preference SEI message applies to the current decoded picture only. + +**deblocking\_display\_preference\_repetition\_period** equal to 1 specifies that the deblocking filter display preference SEI message persists in output order until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a deblocking filter display preference SEI message is output having **PicOrderCnt()** greater than **PicOrderCnt( CurrPic )**. + +**deblocking\_display\_preference\_repetition\_period** greater than 1 specifies that the deblocking filter display preference SEI message persists until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a deblocking filter display preference SEI message is output having **PicOrderCnt()** greater than **PicOrderCnt( CurrPic )** and less than or equal to **PicOrderCnt( CurrPic ) + deblocking\_display\_preference\_repetition\_period**. + +**deblocking\_display\_preference\_repetition\_period** greater than 1 indicates that another deblocking filter display preference SEI message shall be present for a picture in an access unit that is output having **PicOrderCnt()** greater than **PicOrderCnt( CurrPic )** and less than or equal to **PicOrderCnt( CurrPic ) + deblocking\_display\_preference\_repetition\_period**; unless the bitstream ends or a new coded video sequence begins without output of such a picture. + +#### D.2.23 Stereo video information SEI message semantics + +NOTE 1 – The stereo video information SEI message is included in this Specification primarily for historical reasons. It is now suggested to use the frame packing arrangement SEI message rather than the stereo video information SEI message to signal stereo video information. + +This SEI message provides the decoder with an indication that the entire coded video sequence consists of pairs of pictures forming stereo-view content. + +The stereo video information SEI message shall not be present in any access unit of a coded video sequence unless a stereo video information SEI message is present in the first access unit of the coded video sequence in decoding order. + +**field\_views\_flag** equal to 1 indicates that all pictures in the current coded video sequence are fields and all fields of a particular parity are considered a left view and all fields of the opposite parity are considered a right view for stereo-view content. field\_views\_flag equal to 0 indicates that all pictures in the current coded video sequence are frames and alternating frames in output order represent a view of a stereo view. The value of field\_views\_flag shall be the same in all stereo video information SEI messages within a coded video sequence. + +When the stereo video information SEI message is present and field\_views\_flag is equal to 1, the left view and right view of a stereo video pair shall be coded as a complementary field pair, the display time of the first field of the field pair in output order should be delayed to coincide with the display time of the second field of the field pair in output order, and the spatial locations of the samples in each individual field should be interpreted for display purposes as representing complete pictures as shown in Figure 6-1 rather than as spatially-distinct fields within a frame as shown in Figure 6-2. + +NOTE 2 – The display process is not specified in this Recommendation | International Standard. + +**top\_field\_is\_left\_view\_flag** equal to 1 indicates that the top fields in the coded video sequence represent a left view and the bottom fields in the coded video sequence represent a right view. top\_field\_is\_left\_view\_flag equal to 0 indicates that the bottom fields in the coded video sequence represent a left view and the top fields in the coded video sequence represent a right view. When present, the value of top\_field\_is\_left\_view\_flag shall be the same in all stereo video information SEI messages within a coded video sequence. + +**current\_frame\_is\_left\_view\_flag** equal to 1 indicates that the current picture is the left view of a stereo-view pair. current\_frame\_is\_left\_view\_flag equal to 0 indicates that the current picture is the right view of a stereo-view pair. + +**next\_frame\_is\_second\_view\_flag** equal to 1 indicates that the current picture and the next picture in output order form a stereo-view pair, and the display time of the current picture should be delayed to coincide with the display time of the next picture in output order. next\_frame\_is\_second\_view\_flag equal to 0 indicates that the current picture and the previous picture in output order form a stereo-view pair, and the display time of the current picture should not be delayed for purposes of stereo-view pairing. + +**left\_view\_self\_contained\_flag** equal to 1 indicates that no inter prediction operations within the decoding process for the left-view pictures of the coded video sequence refer to reference pictures that are right-view pictures. left\_view\_self\_contained\_flag equal to 0 indicates that some inter prediction operations within the decoding process for the left-view pictures of the coded video sequence may or may not refer to reference pictures that are right-view pictures. Within a coded video sequence, the value of left\_view\_self\_contained\_flag in all stereo video information SEI messages shall be the same. + +**right\_view\_self\_contained\_flag** equal to 1 indicates that no inter prediction operations within the decoding process for the right-view pictures of the coded video sequence refer to reference pictures that are left-view pictures. right\_view\_self\_contained\_flag equal to 0 indicates that some inter prediction operations within the decoding process for the right-view pictures of the coded video sequence may or may not refer to reference pictures that are left-view pictures. Within a coded video sequence, the value of right\_view\_self\_contained\_flag in all stereo video information SEI messages shall be the same. + +#### D.2.24 Post-filter hint SEI message semantics + +This SEI message provides the coefficients of a post-filter or correlation information for the design of a post-filter for potential use in post-processing of the current picture after it is decoded, cropped, and output, to obtain improved displayed quality. + +**filter\_hint\_size\_y** specifies the vertical size of the filter coefficient or correlation array. The value of filter\_hint\_size\_y shall be in the range of 1 to 15, inclusive. + +**filter\_hint\_size\_x** specifies the horizontal size of the filter coefficient or correlation array. The value of filter\_hint\_size\_x shall be in the range of 1 to 15, inclusive. + +**filter\_hint\_type** identifies the type of the filter hints as specified in Table D-7. The value of filter\_hint\_type shall be in the range of 0 to 2, inclusive. The value of filter\_hint\_type equal to 3 is reserved for future use by ITU-T | ISO/IEC and shall not be present in bitstreams conforming to this version of this Specification. Decoders shall ignore post-filter hint SEI messages having filter\_hint\_type equal to the reserved value 3. + +**Table D-7 – filter\_hint\_type values** + +| Value | Description | +|-------|------------------------------------| +| 0 | Coefficients of a 2D FIR filter | +| 1 | Coefficients of two 1D FIR filters | +| 2 | Cross-correlation matrix | + +**filter\_hint\_value[ cIdx ][ cx ][ cy ]** specifies a filter coefficient or an element of a cross-correlation matrix between the original and the output signal with 16-bit precision. The value of **filter\_hint\_value[ cIdx ][ cx ][ cy ]** shall be in the range of $-2^{31} + 1$ to $2^{31} - 1$ , inclusive. **cIdx** specifies the related colour component. **cx** represents a counter in the horizontal direction, **cy** represents a counter in the vertical direction. + +When **filter\_hint\_type** is equal to 1, **filter\_hint\_size\_y** shall be equal to 2. + +Depending on the value of **filter\_hint\_type**, the following applies: + +- If **filter\_hint\_type** is equal to 0, the coefficients of a two-dimensional FIR filter with the size of **filter\_hint\_size\_x** \* **filter\_hint\_size\_y** are provided. +- Otherwise, if **filter\_hint\_type** is equal to 1, the filter coefficients of two one-dimensional FIR filters are provided. In this case, **filter\_hint\_size\_y** shall be equal to 2. In this case, the index **cy** equal to 0 specifies the filter coefficients of the horizontal filter and **cy** equal to 1 specifies the filter coefficients of the vertical filter. In the indicated filtering process, the horizontal filter is applied first and the result is filtered by the vertical filter. +- Otherwise (**filter\_hint\_type** is equal to 2), the hint values specify a cross-correlation matrix between the original signal **s** and the output signal prior to the post-filtering operation **s'**. + +When **filter\_hint\_type** is equal to 2, the normalized cross-correlation matrix values for a related colour component identified by **cIdx** with the size of **filter\_hint\_size\_x** \* **filter\_hint\_size\_y** should be derived by the encoder as follows: + +$$\text{filter\_hint\_value[ cIdx ][ cx ][ cy ]} = \text{Round}\left(\frac{1}{4^{(\text{bitDepth} - 8) * w * h}} * \sum_{n=0}^{h-1} \sum_{m=0}^{w-1} s[m][n] * s'[\text{Clip3}(0, w - 1, m + \text{cx} - \text{midX})][\text{Clip3}(0, h - 1, n + \text{cy} - \text{midY})]\right) \quad (\text{D-27})$$ + +where **s** denotes the array of samples of the colour component **cIdx** of the original picture, **s'** denotes the corresponding array of the cropped output picture, **h** denotes the vertical height of the related colour component, **w** denotes the horizontal width of the related colour component, **bitDepth** denotes the bit depth of the colour component, **midX** is equal to (**filter\_hint\_size\_x** >> 1), **midY** is equal to (**filter\_hint\_size\_y** >> 1), $0 \leq \text{cx} < \text{filter\_hint\_size\_x}$ and $0 \leq \text{cy} < \text{filter\_hint\_size\_y}$ . + +NOTE – A decoder can derive a Wiener post-filter from the cross-correlation matrix between the original signal **s** and the output signal **s'** and the auto-correlation matrix of the output signal **s'** (which the decoder can compute from the output signal **s'**). + +**additional\_extension\_flag** equal to 0 indicates that no additional data follows within the post-filter hint SEI message. The value of **additional\_extension\_flag** shall be equal to 0. The value of 1 for **additional\_extension\_flag** is reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all data that follows the value of 1 for **additional\_extension\_flag** in a post-filter hint SEI message. + +#### D.2.25 Tone mapping information SEI message semantics + +This SEI message provides information to enable remapping of the colour samples of the output decoded pictures for customization to particular display environments. The remapping process maps coded sample values in the RGB colour space (specified in Annex E) to target sample values. The mappings are expressed in the luma or RGB colour space domain, and should be applied to the luma component or to each RGB component produced by colour space conversion of the decoded image accordingly. + +**tone\_map\_id** contains an identifying number that may be used to identify the purpose of the tone mapping model. The value of **tone\_map\_id** shall be in the range of 0 to $2^{32} - 2$ , inclusive. + +Values of **tone\_map\_id** from 0 to 255, inclusive, and from 512 to $2^{31} - 1$ , inclusive, may be used as determined by the application. Values of **tone\_map\_id** from 256 to 511, inclusive, and from $2^{31}$ to $2^{32} - 2$ , inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of **tone\_map\_id** in the range of 256 to 511, inclusive, or in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, shall ignore it. + +NOTE 1 – The tone\_map\_id can be used to support tone mapping operations that are suitable for different display scenarios. For example, different values of tone\_map\_id may correspond to different display bit depths. + +**tone\_map\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous tone mapping information SEI message in output order. tone\_map\_cancel\_flag equal to 0 indicates that tone mapping information follows. + +**tone\_map\_repetition\_period** specifies the persistence of the tone mapping information SEI message and may specify a picture order count interval within which another tone mapping information SEI message with the same value of tone\_map\_id or the end of the coded video sequence shall be present in the bitstream. The value of tone\_map\_repetition\_period shall be in the range of 0 to 16 384, inclusive. + +tone\_map\_repetition\_period equal to 0 specifies that the tone map information applies to the current decoded picture only. + +tone\_map\_repetition\_period equal to 1 specifies that the tone map information persists in output order until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a tone mapping information SEI message with the same value of tone\_map\_id is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ). + +tone\_map\_repetition\_period equal to 0 or equal to 1 indicates that another tone mapping information SEI message with the same value of tone\_map\_id may or may not be present. + +tone\_map\_repetition\_period greater than 1 specifies that the tone map information persists until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a tone mapping information SEI message with the same value of tone\_map\_id is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ) and less than or equal to PicOrderCnt( CurrPic ) + tone\_map\_repetition\_period. + +tone\_map\_repetition\_period greater than 1 indicates that another tone mapping information SEI message with the same value of tone\_map\_id shall be present for a picture in an access unit that is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ) and less than or equal to PicOrderCnt( CurrPic ) + tone\_map\_repetition\_period; unless the bitstream ends or a new coded video sequence begins without output of such a picture. + +**coded\_data\_bit\_depth** specifies the BitDepthy for interpretation of the luma component of the associated pictures for purposes of interpretation of the tone mapping information SEI message. If tone mapping information SEI messages are present that have coded\_data\_bit\_depth that is not equal to BitDepthy, these refer to the hypothetical result of a transcoding operation performed to convert the coded video to the BitDepthy corresponding to the value of coded\_data\_bit\_depth. + +The value of coded\_data\_bit\_depth shall be in the range of 8 to 14, inclusive. Values of coded\_data\_bit\_depth from 0 to 7 and from 15 to 255 are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore (remove from the bitstream and discard) all tone mapping SEI messages that contain a coded\_data\_bit\_depth in the range of 0 to 7 or in the range of 15 to 255, and bitstreams shall not contain such values. + +**target\_bit\_depth** specifies the bit depth of the output of the dynamic range mapping function (or tone mapping function) described by the tone mapping information SEI message. The tone mapping function specified with a particular target\_bit\_depth is suggested to be reasonable for all display bit depths that are less than or equal to the target\_bit\_depth. + +The value of target\_bit\_depth shall be in the range of 1 to 16, inclusive. Values of target\_bit\_depth equal to 0 and in the range of 17 to 255 are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore (remove from the bitstream and discard) all tone mapping SEI messages that contain a value of target\_bit\_depth equal to 0 or in the range of 17 to 255, and bitstreams shall not contain such values. + +**tone\_map\_model\_id** specifies the model utilized for mapping the coded data into the target\_bit\_depth range. Values greater than 3 are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore (remove from the bitstream and discard) all tone mapping SEI messages that contain a value of tone\_map\_model\_id greater than 4, and bitstreams shall not contain such values. Decoders shall allow reserved values of tone\_map\_model\_id in the range of 5 to 16 384, inclusive, to be present in the bitstream. + +NOTE 2 – A tone\_map\_model\_id value of 0 corresponds to a linear mapping with clipping; a tone\_map\_model\_id value of 1 corresponds to a sigmoidal mapping; a tone\_map\_model\_id value of 2 corresponds to a user-defined table mapping, a tone\_map\_model\_id value of 3 corresponds to a piece-wise linear mapping, and a tone\_map\_model\_id value of 4 corresponds to luminance dynamic range information. + +**min\_value** specifies the RGB sample value that maps to the minimum value in the bit depth indicated by target\_bit\_depth. It is used in combination with the max\_value parameter. All sample values of the decoded picture that are less than or + +equal to *min\_value* after conversion to the RGB domain (when decoded in a different domain) are mapped to this minimum value in the *target\_bit\_depth* representation. + +**max\_value** specifies the RGB sample value that maps to the maximum value in the bit depth indicated by *target\_bit\_depth*. It is used in combination with the *min\_value* parameter. All sample values of the decoded picture that are greater than or equal to *max\_value* after conversion to the RGB domain (when decoded in a different domain) are mapped to this maximum value in the *target\_bit\_depth* representation. + +*max\_value* shall be greater than or equal to *min\_value*. + +**sigmoid\_midpoint** specifies the RGB sample value of the coded data that is mapped to the centre point of the *target\_bit\_depth* representation. It is used in combination with the *sigmoid\_width* parameter. + +**sigmoid\_width** specifies the distance between two coded data values that approximately correspond to the 5% and 95% values of the *target\_bit\_depth* representation, respectively. It is used in combination with the *sigmoid\_midpoint* parameter and is interpreted according to the following function: + +$$f(i) = \text{Round} \left( \frac{2^{\text{target\_bit\_depth}} - 1}{1 + \exp \left( \frac{-6 * (i - \text{sigmoid\_midpoint})}{\text{sigmoid\_width}} \right)} \right) \quad \text{for } i = 0, \dots, (2^{\text{coded\_bit\_depth}} - 1) \quad (\text{D-28})$$ + +where $f(i)$ denotes the function that maps an RGB sample value *i* from the coded data to a resulting RGB sample value in the *target\_bit\_depth* representation. + +**start\_of\_coded\_interval[ i ]** specifies the beginning point of an interval in the coded data such that all RGB sample values that are greater than or equal to *start\_of\_coded\_interval[ i ]* and less than *start\_of\_coded\_interval[ i + 1 ]* are mapped to *i* in the target bit depth representation. The value of *start\_of\_coded\_interval[ 2target\_bit\_depth ]* is equal to $2^{\text{coded\_bit\_depth}}$ . The number of bits used for the representation of the *start\_of\_coded\_interval* is $((\text{coded\_data\_bit\_depth} + 7) \gg 3) \ll 3$ . + +**num\_pivots** specifies the number of pivot points in the piece-wise linear mapping function without counting the two default end points, (0, 0) and $(2^{\text{coded\_data\_bit\_depth}} - 1, 2^{\text{target\_bit\_depth}} - 1)$ . + +**coded\_pivot\_value[ i ]** specifies the value in the *coded\_data\_bit\_depth* corresponding to the *i*-th pivot point. The number of bits used for the representation of the *coded\_pivot\_value* is $((\text{coded\_data\_bit\_depth} + 7) \gg 3) \ll 3$ . + +**target\_pivot\_value[ i ]** specifies the value in the reference *target\_bit\_depth* corresponding to the *i*-th pivot point. The number of bits used for the representation of the *target\_pivot\_value* is $((\text{target\_bit\_depth} + 7) \gg 3) \ll 3$ . + +**camera\_iso\_speed\_idc** indicates the camera ISO speed for daylight illumination as specified by ISO 12232, interpreted as specified by Table D-8. When *camera\_iso\_speed\_idc* indicates Extended\_ISO, the ISO speed is represented by *camera\_iso\_speed\_value*. + +**camera\_iso\_speed\_value** indicates the camera ISO speed for daylight illumination as specified by ISO 12232 when *camera\_iso\_speed\_idc* is set to Extended\_ISO. The value of *camera\_iso\_speed\_value* shall not be equal to 0. + +**exposure\_index\_idc** indicates the exposure index setting of the camera as specified by ISO 12232, interpreted as specified by Table D-8. When *exposure\_index\_idc* indicates Extended\_ISO, the exposure index is indicated by *exposure\_index\_value*. + +The values of *camera\_iso\_speed\_idc* and *exposure\_index\_idc* in the range of 31 to 254, inclusive, are reserved for future use by ITU-T | ISO/IEC, and shall not be present in bitstreams conforming to this version of this Specification. Decoders conforming to this version of this Specification shall ignore tone mapping SEI messages that contain these values. + +**exposure\_index\_value** indicates the exposure index setting of the camera as specified by ISO 12232 when *exposure\_index\_idc* indicates Extended\_ISO. The value of *exposure\_index\_value* shall not be equal to 0. + +**Table D-8 – Interpretation of camera\_iso\_speed\_idc and exposure\_index\_idc** + +| camera_iso_speed_idc or
exposure_index_idc | Indicated value | +|-------------------------------------------------------|------------------------| +| 0 | Unspecified | +| 1 | 10 | +| 2 | 12 | +| 3 | 16 | +| 4 | 20 | +| 5 | 25 | +| 6 | 32 | +| 7 | 40 | +| 8 | 50 | +| 9 | 64 | +| 10 | 80 | +| 11 | 100 | +| 12 | 125 | +| 13 | 160 | +| 14 | 200 | +| 15 | 250 | +| 16 | 320 | +| 17 | 400 | +| 18 | 500 | +| 19 | 640 | +| 20 | 800 | +| 21 | 1000 | +| 22 | 1250 | +| 23 | 1600 | +| 24 | 2000 | +| 25 | 2500 | +| 26 | 3200 | +| 27 | 4000 | +| 28 | 5000 | +| 29 | 6400 | +| 30 | 8000 | +| 31..254 | Reserved | +| 255 | Extended_ISO | + +**exposure\_compensation\_value\_sign\_flag**, when applicable as specified below, specifies the sign of the variable ExposureCompensationValue that indicates the exposure compensation value setting used for the process of image production. + +**exposure\_compensation\_value\_numerator**, when applicable as specified below, specifies the numerator of the variable ExposureCompensationValue that indicates the exposure compensation value setting used for the process of image production. + +**exposure\_compensation\_value\_denom\_idc**, when not equal to 0, specifies the denominator of the variable ExposureCompensationValue that indicates the exposure compensation value setting used for the process of image production. + +When exposure\_compensation\_value\_denom\_idc is present and not equal to 0, the variable ExposureCompensationValue is derived from exposure\_compensation\_value\_sign\_flag, exposure\_compensation\_value\_numerator and exposure\_compensation\_value\_denom\_idc. exposure\_compensation\_value\_sign\_flag equal to 0 indicates that the ExposureCompensationValue is positive. exposure\_compensation\_value\_sign\_flag equal to 1 indicates that the ExposureCompensationValue is negative. When ExposureCompensationValue is positive, the image is indicated to have been further sensitized through the process of production, relative to the recommended exposure index of the camera as specified by ISO 12232. When ExposureCompensationValue is negative, the image is indicated to have been further desensitized through the process of production, relative to the recommended exposure index of the camera as specified by ISO 12232. + +When exposure\_compensation\_value\_denom\_idc is present and not equal to 0, the variable ExposureCompensationValue is derived as follows: + +$$\text{ExposureCompensationValue} = ( 1 - 2 * \text{exposure\_compensation\_value\_sign\_flag} ) * \frac{\text{exposure\_compensation\_value\_numerator}}{\text{exposure\_compensation\_value\_denom\_idc}} \quad (\text{D-29})$$ + +The value of ExposureCompensationValue is interpreted in units of exposure steps such that an increase of 1 in ExposureCompensationValue corresponds to a doubling of exposure in units of lux-seconds. For example, the exposure compensation value equal to $+1 \div 2$ at the production stage may be indicated by setting exposure\_compensation\_value\_sign\_flag to 0, exposure\_compensation\_value\_numerator to 1, and exposure\_compensation\_value\_denom\_idc to 2. + +When exposure\_compensation\_value\_denom\_idc is present and equal to 0, the exposure compensation value is indicated as unknown or unspecified. + +**ref\_screen\_luminance\_white** indicates the reference screen brightness setting for the extended range white level used for image production process in units of candela per square metre. + +**extended\_range\_white\_level** indicates the luminance dynamic range for extended dynamic-range display of the associated pictures, after conversion to the linear light domain for display, expressed as an integer percentage relative to the nominal white level. When present, the value of extended\_range\_white\_level should be greater than or equal to 100. + +**nominal\_black\_level\_luma\_code\_value** specifies the luma sample value of the associated decoded pictures to which the nominal black level is assigned. For example, when coded\_data\_bit\_depth is equal to 8, video\_full\_range\_flag is equal to 0, and matrix\_coefficients is equal to 1, nominal\_black\_level\_luma\_code\_value should be equal to 16. + +**nominal\_white\_level\_luma\_code\_value** specifies the luma sample value of the associated decoded pictures to which the nominal white level is assigned. For example, when coded\_data\_bit\_depth is equal to 8, video\_full\_range\_flag is equal to 0, and matrix\_coefficients is equal to 1, nominal\_white\_level\_luma\_code\_value should be equal to 235. When present, the value of nominal\_white\_level\_luma\_code\_value shall be greater than nominal\_black\_level\_luma\_code\_value. + +**extended\_white\_level\_luma\_code\_value** specifies the luma sample value of the associated decoded pictures to which the white level associated with an extended dynamic range is assigned. When present, the value of extended\_white\_level\_luma\_code\_value shall be greater than or equal to nominal\_white\_level\_luma\_code\_value. + +#### D.2.26 Frame packing arrangement SEI message semantics + +This SEI message informs the decoder that the output cropped decoded picture contains samples of multiple distinct spatially packed constituent frames that are packed into one frame, or that the output cropped decoded pictures in output order form a temporal interleaving of alternating first and second constituent frames, using an indicated frame packing arrangement scheme. This information can be used by the decoder to appropriately rearrange and process the samples of the constituent frames appropriately for display or other purposes (which are outside the scope of this Specification). + +This SEI message may be associated with pictures that are either frames or fields. The frame packing arrangement of the samples is specified in terms of the sampling structure of a frame in order to define a frame packing arrangement structure that is invariant with respect to whether a picture is a single field of such a packed frame or is a complete packed frame. + +**frame\_packing\_arrangement\_id** contains an identifying number that may be used to identify the usage of the frame packing arrangement SEI message. The value of frame\_packing\_arrangement\_id shall be in the range of 0 to $2^{32} - 2$ , inclusive. + +Values of frame\_packing\_arrangement\_id from 0 to 255, inclusive, and from 512 to $2^{31} - 1$ , inclusive, may be used as determined by the application. Values of frame\_packing\_arrangement\_id from 256 to 511, inclusive, and from $2^{31}$ to $2^{32} - 2$ , inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of frame\_packing\_arrangement\_id in the range of 256 to 511, inclusive, or in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, shall ignore it. + +**frame\_packing\_arrangement\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous frame packing arrangement SEI message in output order. frame\_packing\_arrangement\_cancel\_flag equal to 0 indicates that frame packing arrangement information follows. + +**frame\_packing\_arrangement\_type** identifies the indicated interpretation of the sample arrays of the output cropped decoded picture as specified in Table D-9. + +**Table D-9 – Definition of frame\_packing\_arrangement\_type** + +| Value | Interpretation | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | The frame packing arrangement structure contains a "checkerboard" based interleaving of corresponding planes of two constituent frames as illustrated in Figure D-1. | +| 1 | The frame packing arrangement structure contains a column based interleaving of corresponding planes of two constituent frames as illustrated in Figure D-2 and Figure D-3. | +| 2 | The frame packing arrangement structure contains a row based interleaving of corresponding planes of two constituent frames as illustrated in Figure D-4 and Figure D-5. | +| 3 | The frame packing arrangement structure contains a side-by-side packing arrangement of corresponding planes of two constituent frames as illustrated in Figure D-6, Figure D-7, and Figure D-10. | +| 4 | The frame packing arrangement structure contains a top-bottom packing arrangement of corresponding planes of two constituent frames as illustrated in Figure D-8 and Figure D-9. | +| 5 | The component planes of the output cropped decoded pictures in output order form a temporal interleaving of alternating first and second constituent frames as illustrated in Figure D-11. | +| 6 | The output cropped decoded picture constitutes a complete 2D frame (when field_pic_flag is equal to 0) or field (when field_pic_flag is equal to 1) without any frame packing. | +| 7 | The frame packing arrangement structure contains a tile format packing arrangement of corresponding planes of two constituent frames as illustrated in Figure D-12. | + +NOTE 1 – Figure D-1 to Figure D-10 provide typical examples of rearrangement and upconversion processing for various packing arrangement schemes. Actual characteristics of the constituent frames are signalled in detail by the subsequent syntax elements of the frame packing arrangement SEI message. In Figure D-1 to Figure D-10, an upconversion processing is performed on each constituent frame to produce frames having the same resolution as that of the decoded frame. An example of the upsampling method to be applied to a quincunx sampled frame as shown in Figure D-1 or Figure D-10 is to fill in missing positions with an average of the available spatially neighbouring samples (the average of the values of the available samples above, below, to the left and to the right of each sample to be generated). The actual upconversion process to be performed, if any, is outside the scope of this Specification. + +NOTE 2 – The sample aspect ratio (SAR) indicated in the VUI parameters should indicate the output picture shape for the packed decoded frame output by a decoder that does not interpret the frame packing arrangement SEI message. In the examples shown in Figure D-1 to Figure D-10, the SAR produced in each upconverted colour plane would be the same as the SAR indicated in the VUI parameters, since the illustrated upconversion process produces the same total number of samples from each constituent frame as existed in the packed decoded frame. + +NOTE 3 – When the output time of the samples of constituent frame 0 differs from the output time of the samples of constituent frame 1 (i.e., when field\_views\_flag is equal to 1 or frame\_packing\_arrangement\_type is equal to 5) and the display system in use presents two views simultaneously, the display time for constituent frame 0 should be delayed to coincide with the display time for constituent frame 1. (The display process is not specified in this Recommendation | International Standard.) + +NOTE 4 – When `field_views_flag` is equal to 1 or `frame_packing_arrangement_type` is equal to 5, the value 0 for `fixed_frame_rate_flag` is not expected to be prevalent in industry use of this SEI message. + +NOTE 5 – `frame_packing_arrangement_type` equal to 5 describes a temporal interleaving process of different views. + +NOTE 6 – Figure D-12 provides an illustration of the rearrangement process for the frame packing arrangement scheme for the `frame_packing_arrangement_type` value of 7. + +All other values of `frame_packing_arrangement_type` are reserved for future use by ITU-T | ISO/IEC. It is a requirement of bitstream conformance that the bitstreams shall not contain such other values of `frame_packing_arrangement_type`. + +**quincunx\_sampling\_flag** equal to 1 indicates that each colour component plane of each constituent frame is quincunx sampled as illustrated in Figure D-1 or Figure D-10, and `quincunx_sampling_flag` equal to 0 indicates that the colour component planes of each constituent frame are not quincunx sampled. + +When `frame_packing_arrangement_type` is equal to 0, it is a requirement of bitstream conformance that `quincunx_sampling_flag` shall be equal to 1. When `frame_packing_arrangement_type` is equal to 5, 6, or 7, it is a requirement of bitstream conformance that `quincunx_sampling_flag` shall be equal to 0. + +NOTE 7 – For any chroma format (4:2:0, 4:2:2, or 4:4:4), the luma plane and each chroma plane is quincunx sampled as illustrated in Figure D-1 when `quincunx_sampling_flag` is equal to 1. + +Let `CroppedWidth` and `CroppedHeight` be the width and height, respectively, of the cropped frame area output from the decoder in units of luma samples, derived as follows: + +$$\text{CroppedWidth} = \text{PicWidthInSamplesL} - \text{CropUnitX} * ( \text{frame\_crop\_left\_offset} + \text{frame\_crop\_right\_offset} ) \quad (\text{D-30})$$ + +$$\text{CroppedHeight} = 16 * \text{FrameHeightInMbs} - \text{CropUnitY} * ( \text{frame\_crop\_top\_offset} + \text{frame\_crop\_bottom\_offset} ) \quad (\text{D-31})$$ + +When `frame_packing_arrangement_type` is equal to 7, it is a requirement of bitstream conformance that `CroppedWidth` and `CroppedHeight` shall be integer multiples of 3. + +Let `oneThirdWidth` and `oneThirdHeight` be derived as follows: + +$$\text{oneThirdWidth} = \text{CroppedWidth} / 3 \quad (\text{D-32})$$ + +$$\text{oneThirdHeight} = \text{CroppedHeight} / 3 \quad (\text{D-33})$$ + +When `frame_packing_arrangement_type` is equal to 7, the frame packing arrangement is composed of five rectangular regions identified as R0, R1, R2, R3, and R4 as illustrated in Figure D-12. + +The width and height of region R0 are specified in units of frame luma samples as follows: + +$$r0_W = 2 * \text{oneThirdWidth} \quad (\text{D-34})$$ + +$$r0_H = 2 * \text{oneThirdHeight} \quad (\text{D-35})$$ + +The width and height of region R1 are specified in units of frame luma samples as follows: + +$$r1_W = \text{oneThirdWidth} \quad (\text{D-36})$$ + +$$r1_H = 2 * \text{oneThirdHeight} \quad (\text{D-37})$$ + +The width and height of region R2 are specified in units of frame luma samples as follows: + +$$r2_W = \text{oneThirdWidth} \quad (\text{D-38})$$ + +$$r2_H = \text{oneThirdHeight} \quad (\text{D-39})$$ + +The width and height of region R3 are specified in units of frame luma samples as follows: + +$$r3_W = \text{oneThirdWidth} \quad (\text{D-40})$$ + +$$r3_H = \text{oneThirdHeight} \quad (\text{D-41})$$ + +The width and height of region R4 are specified in units of frame luma samples as follows: + +$$r4_W = \text{oneThirdWidth}$$ + +$$(D-42)$$ + +$$r4_H = \text{oneThirdHeight}$$ + +$$(D-43)$$ + +When frame\_packing\_arrangement\_type is equal to 7, constituent frame 0 is obtained by cropping from the decoded frames region R0, and constituent frame 1 is obtained by stacking vertically regions R2 and R3 and placing the resulting rectangle to the right of the region R1. Region R4 is not part of either constituent frame and is discarded. + +**content\_interpretation\_type** indicates the intended interpretation of the constituent frames as specified in Table D-10. Values of content\_interpretation\_type that do not appear in Table D-10 are reserved for future specification by ITU-T | ISO/IEC. When frame\_packing\_arrangement\_type is equal to 6, content\_interpretation\_type shall be equal to 0. + +When frame\_packing\_arrangement\_type is not equal to 6, for each specified frame packing arrangement scheme, there are two constituent frames that are referred to as frame 0 and frame 1. + +**Table D-10 – Definition of content\_interpretation\_type** + +| Value | Interpretation | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Unspecified relationship between the frame packed constituent frames | +| 1 | Indicates that the two constituent frames form the left and right views of a stereo view scene, with frame 0 being associated with the left view and frame 1 being associated with the right view | +| 2 | Indicates that the two constituent frames form the right and left views of a stereo view scene, with frame 0 being associated with the right view and frame 1 being associated with the left view | + +NOTE 8 – The value 2 for content\_interpretation\_type is not expected to be prevalent in industry use of this SEI message. However, the value was specified herein for purposes of completeness. + +When frame\_packing\_arrangement\_type is equal to 6, content\_interpretation\_type, frame0\_self\_contained\_flag, frame1\_self\_contained\_flag, frame0\_grid\_position\_x, frame0\_grid\_position\_y, frame1\_grid\_position\_x, and frame1\_grid\_position\_y have no meaning and shall be equal to 0, and decoders shall ignore the values of these syntax elements. In this case, semantics for other values of these syntax elements are reserved for future specification by ITU-T | ISO/IEC. + +**spatial\_flipping\_flag** equal to 1, when frame\_packing\_arrangement\_type is equal to 3 or 4, indicates that one of the two constituent frames is spatially flipped relative to its intended orientation for display or other such purposes. + +When frame\_packing\_arrangement\_type is equal to 3 or 4 and spatial\_flipping\_flag is equal to 1, the type of spatial flipping that is indicated is as follows: + +- If frame\_packing\_arrangement\_type is equal to 3, the indicated spatial flipping is horizontal flipping. +- Otherwise (frame\_packing\_arrangement\_type is equal to 4), the indicated spatial flipping is vertical flipping. + +When frame\_packing\_arrangement\_type is not equal to 3 or 4, it is a requirement of bitstream conformance that spatial\_flipping\_flag shall be equal to 0. When frame\_packing\_arrangement\_type is not equal to 3 or 4, the value 1 for spatial\_flipping\_flag is reserved for future use by ITU-T | ISO/IEC. When frame\_packing\_arrangement\_type is not equal to 3 or 4, decoders shall ignore the value 1 for spatial\_flipping\_flag. + +**frame0\_flipped\_flag**, when spatial\_flipping\_flag is equal to 1, indicates which one of the two constituent frames is flipped. + +When spatial\_flipping\_flag is equal to 1, frame0\_flipped\_flag equal to 0 indicates that frame 0 is not spatially flipped and frame 1 is spatially flipped, and frame0\_flipped\_flag equal to 1 indicates that frame 0 is spatially flipped and frame 1 is not spatially flipped. + +When spatial\_flipping\_flag is equal to 0, it is a requirement of bitstream conformance that frame0\_flipped\_flag shall be equal to 0. When spatial\_flipping\_flag is equal to 0, the value 1 for spatial\_flipping\_flag is reserved for future use by ITU-T | ISO/IEC. When spatial\_flipping\_flag is equal to 0, decoders shall ignore the value of frame0\_flipped\_flag. + +**field\_views\_flag** equal to 1 indicates that all pictures in the current coded video sequence are coded as complementary field pairs. All fields of a particular parity are considered a first constituent frame and all fields of the opposite parity are considered a second constituent frame. When frame\_packing\_arrangement\_type is not equal to 2, it is a requirement of bitstream conformance that the field\_views\_flag shall be equal to 0. When frame\_packing\_arrangement\_type is not equal to 2, the value 1 for field\_views\_flag is reserved for future use by ITU-T | ISO/IEC. When frame\_packing\_arrangement\_type is not equal to 2, decoders shall ignore the value of field\_views\_flag. + +**current\_frame\_is\_frame0\_flag** equal to 1, when **frame\_packing\_arrangement** is equal to 5, indicates that the current decoded frame is constituent frame 0 and the next decoded frame in output order is constituent frame 1, and the display time of the constituent frame 0 should be delayed to coincide with the display time of constituent frame 1. **current\_frame\_is\_frame0\_flag** equal to 0, when **frame\_packing\_arrangement** is equal to 5, indicates that the current decoded frame is constituent frame 1 and the previous decoded frame in output order is constituent frame 0, and the display time of the constituent frame 1 should not be delayed for purposes of stereo-view pairing. + +When **frame\_packing\_arrangement\_type** is not equal to 5, the constituent frame associated with the upper-left sample of the decoded frame is considered to be constituent frame 0 and the other constituent frame is considered to be constituent frame 1. When **frame\_packing\_arrangement\_type** is not equal to 5, it is a requirement of bitstream conformance that **current\_frame\_is\_frame0\_flag** shall be equal to 0. When **frame\_packing\_arrangement\_type** is not equal to 5, the value 1 for **current\_frame\_is\_frame0\_flag** is reserved for future use by ITU-T | ISO/IEC. When **frame\_packing\_arrangement\_type** is not equal to 5, decoders shall ignore the value of **current\_frame\_is\_frame0\_flag**. + +**frame0\_self\_contained\_flag** equal to 1 indicates that no inter prediction operations within the decoding process for the samples of constituent frame 0 of the coded video sequence refer to samples of any constituent frame 1. **frame0\_self\_contained\_flag** equal to 0 indicates that some inter prediction operations within the decoding process for the samples of constituent frame 0 of the coded video sequence may or may not refer to samples of some constituent frame 1. When **frame\_packing\_arrangement\_type** is equal to 0 or 1, it is a requirement of bitstream conformance that **frame0\_self\_contained\_flag** shall be equal to 0. When **frame\_packing\_arrangement\_type** is equal to 0 or 1, the value 1 for **frame0\_self\_contained\_flag** is reserved for future use by ITU-T | ISO/IEC. When **frame\_packing\_arrangement\_type** is equal to 0 or 1, decoders shall ignore the value of **frame0\_self\_contained\_flag**. Within a coded video sequence, the value of **frame0\_self\_contained\_flag** in all **frame packing arrangement SEI messages** shall be the same. + +**frame1\_self\_contained\_flag** equal to 1 indicates that no inter prediction operations within the decoding process for the samples of constituent frame 1 of the coded video sequence refer to samples of any constituent frame 0. **frame1\_self\_contained\_flag** equal to 0 indicates that some inter prediction operations within the decoding process for the samples of constituent frame 1 of the coded video sequence may or may not refer to samples of some constituent frame 0. When **frame\_packing\_arrangement\_type** is equal to 0 or 1, it is a requirement of bitstream conformance that **frame1\_self\_contained\_flag** shall be equal to 0. When **frame\_packing\_arrangement\_type** is equal to 0 or 1, the value 1 for **frame1\_self\_contained\_flag** is reserved for future use by ITU-T | ISO/IEC. When **frame\_packing\_arrangement\_type** is equal to 0 or 1, decoders shall ignore the value of **frame1\_self\_contained\_flag**. Within a coded video sequence, the value of **frame1\_self\_contained\_flag** in all **frame packing arrangement SEI messages** shall be the same. + +NOTE 9 – When **frame0\_self\_contained\_flag** is equal to 1 or **frame1\_self\_contained\_flag** is equal to 1, and **frame\_packing\_arrangement\_type** is equal to 2, it is expected that the decoded frame should not be an MBAFF frame. + +When **quincunx\_sampling\_flag** is equal to 0 and **frame\_packing\_arrangement\_type** is not equal to 5, two (x, y) coordinate pairs are specified to determine the indicated luma sampling grid alignment for constituent frame 0 and constituent frame 1, relative to the upper left corner of the rectangular area represented by the samples of the corresponding constituent frame. + +NOTE 10 – The location of chroma samples relative to luma samples can be indicated by the **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** syntax elements in the VUI parameters. + +**frame0\_grid\_position\_x** (when present) specifies the x component of the (x, y) coordinate pair for constituent frame 0. + +**frame0\_grid\_position\_y** (when present) specifies the y component of the (x, y) coordinate pair for constituent frame 0. + +**frame1\_grid\_position\_x** (when present) specifies the x component of the (x, y) coordinate pair for constituent frame 1. + +**frame1\_grid\_position\_y** (when present) specifies the y component of the (x, y) coordinate pair for constituent frame 1. + +When **quincunx\_sampling\_flag** is equal to 0 and **frame\_packing\_arrangement\_type** is not equal to 5 the (x, y) coordinate pair for each constituent frame is interpreted as follows: + +- If the (x, y) coordinate pair for a constituent frame is equal to (0, 0), this indicates a default sampling grid alignment specified as follows: + - If **frame\_packing\_arrangement\_type** is equal to 1 or 3, the indicated position is the same as for the (x, y) coordinate pair value (4, 8), as illustrated in Figure D-2 and Figure D-6. + - Otherwise (**frame\_packing\_arrangement\_type** is equal to 2 or 4), the indicated position is the same as for the (x, y) coordinate pair value (8, 4), as illustrated in Figure D-4 and Figure D-8. +- Otherwise, if the (x, y) coordinate pair for a constituent frame is equal to (15, 15), this indicates that the sampling grid alignment is unknown or unspecified or specified by other means not specified in this Recommendation | International Standard. +- Otherwise, the x and y elements of the (x, y) coordinate pair specify the indicated horizontal and vertical sampling grid alignment positioning to the right of and below the upper left corner of the rectangular area represented by the + +corresponding constituent frame, respectively, in units of one sixteenth of the luma sample grid spacing between the samples of the columns and rows of the constituent frame that are present in the decoded frame (prior to any upsampling for display or other purposes). + +NOTE 11 – The spatial location reference information frame0\_grid\_position\_x, frame0\_grid\_position\_y, frame1\_grid\_position\_x, and frame1\_grid\_position\_y is not provided when quincunx\_sampling\_flag is equal to 1 because the spatial alignment in this case is assumed to be such that constituent frame 0 and constituent frame 1 cover corresponding spatial areas with interleaved quincunx sampling patterns as illustrated in Figure D-1 and Figure D-10. + +NOTE 12 – When frame\_packing\_arrangement\_type is equal to 2 and field\_views\_flag is equal to 1, it is suggested that frame0\_grid\_position\_y should be equal to frame1\_grid\_position\_y. + +**frame\_packing\_arrangement\_reserved\_byte** is reserved for future use by ITU-T | ISO/IEC. It is a requirement of bitstream conformance that the value of frame\_packing\_arrangement\_reserved\_byte shall be equal to 0. All other values of frame\_packing\_arrangement\_reserved\_byte are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore (remove from the bitstream and discard) the value of frame\_packing\_arrangement\_reserved\_byte. + +**frame\_packing\_arrangement\_repetition\_period** specifies the persistence of the frame packing arrangement SEI message and may specify a frame order count interval within which another frame packing arrangement SEI message with the same value of frame\_packing\_arrangement\_id or the end of the coded video sequence shall be present in the bitstream. The value of frame\_packing\_arrangement\_repetition\_period shall be in the range of 0 to 16 384, inclusive. + +frame\_packing\_arrangement\_repetition\_period equal to 0 specifies that the frame packing arrangement SEI message applies to the current decoded frame only. + +frame\_packing\_arrangement\_repetition\_period equal to 1 specifies that the frame packing arrangement SEI message persists in output order until any of the following conditions are true: + +- A new coded video sequence begins. +- A frame in an access unit containing a frame packing arrangement SEI message with the same value of frame\_packing\_arrangement\_id is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ). + +frame\_packing\_arrangement\_repetition\_period equal to 0 or equal to 1 indicates that another frame packing arrangement SEI message with the same value of frame\_packing\_arrangement\_id may or may not be present. + +frame\_packing\_arrangement\_repetition\_period greater than 1 specifies that the frame packing arrangement SEI message persists until any of the following conditions are true: + +- A new coded video sequence begins. +- A frame in an access unit containing a frame packing arrangement SEI message with the same value of frame\_packing\_arrangement\_id is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ) and less than or equal to PicOrderCnt( CurrPic ) + frame\_packing\_arrangement\_repetition\_period. + +frame\_packing\_arrangement\_repetition\_period greater than 1 indicates that another frame packing arrangement SEI message with the same value of frame\_packing\_arrangement\_frames\_id shall be present for a frame in an access unit that is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ) and less than or equal to PicOrderCnt( CurrPic ) + frame\_packing\_arrangement\_repetition\_period; unless the bitstream ends or a new coded video sequence begins without output of such a frame. + +**frame\_packing\_arrangement\_extension\_flag** equal to 0 indicates that no additional data follows within the frame packing arrangement SEI message. It is a requirement of bitstream conformance that the value of frame\_packing\_arrangement\_extension\_flag shall be equal to 0. The value 1 for frame\_packing\_arrangement\_extension\_flag is reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore the value 1 for frame\_packing\_arrangement\_extension\_flag in a frame packing arrangement SEI message and shall ignore all data that follows within a frame packing arrangement SEI message after the value 1 for frame\_packing\_arrangement\_extension\_flag. + +![Diagram illustrating the rearrangement and upconversion of checkerboard interleaving. It shows the process of decomposing an interleaved frame into two constituent frames (0 and 1), upconverting each, and then recombining them.](71d7b20ced0151b68d524e8163f48ecb_img.jpg) + +The diagram illustrates the rearrangement and upconversion of checkerboard interleaving. It starts with an **Interleaved colour component plane of checkerboard interleaved decoded frame**, which is an 8x8 grid of alternating 'X' and 'O' samples. This is processed through **Checkerboard interleaving decomposition** to produce two separate grids: **Samples of colour component plane of constituent frame 0** (containing 'X' samples) and **Samples of colour component plane of constituent frame 1** (containing 'O' samples). Both are then processed through **Upconversion processing** to produce larger grids: **Upconverted colour component plane of constituent frame 0** and **Upconverted colour component plane of constituent frame 1**. The text H.264(17)\_FD.1 is present at the bottom right. + +Diagram illustrating the rearrangement and upconversion of checkerboard interleaving. It shows the process of decomposing an interleaved frame into two constituent frames (0 and 1), upconverting each, and then recombining them. + +**Figure D-1 – Rearrangement and upconversion of checkerboard interleaving (frame\_packing\_arrangement\_type equal to 0)** + +![Diagram illustrating the rearrangement and upconversion of column interleaving. It shows the process of decomposing an interleaved frame into two constituent frames (0 and 1), upconverting each, and then recombining them.](460111aa57aedbb167f7464b02748cef_img.jpg) + +The diagram illustrates the rearrangement and upconversion of column interleaving. It starts with an **Interleaved colour component plane of a column interleaved decoded frame**, which is an 8x8 grid of alternating 'X' and 'O' samples. This is processed through **Column interleaving decomposition** to produce two separate grids: **Samples of colour component plane of constituent frame 0** (containing 'X' samples) and **Samples of colour component plane of constituent frame 1** (containing 'O' samples). Both are then processed through **Upconversion processing** to produce larger grids: **Upconverted colour component plane of constituent frame 0** and **Upconverted colour component plane of constituent frame 1**. The text H.264(17)\_FD.2 is present at the bottom right. + +Diagram illustrating the rearrangement and upconversion of column interleaving. It shows the process of decomposing an interleaved frame into two constituent frames (0 and 1), upconverting each, and then recombining them. + +**Figure D-2 – Rearrangement and upconversion of column interleaving with frame\_packing\_arrangement\_type equal to 1, quincunx\_sampling\_flag equal to 0, and (x, y) equal to (0, 0) or (4, 8) for both constituent frames** + +![Diagram illustrating the rearrangement and upconversion of column interleaving. It shows the flow from an interleaved colour component plane through column interleaving decomposition into samples for constituent frames 0 and 1, followed by upconversion processing to produce upconverted colour component planes for each frame. The diagram includes 8x8 grids of 'X' and 'O' characters representing samples.](51b3f989269d40b52bbf69c7a448bf52_img.jpg) + +The diagram shows the process of column interleaving decomposition and upconversion. It starts with an 8x8 grid of 'X' and 'O' characters representing an interleaved colour component plane. This is processed through 'Column interleaving decomposition' to produce two separate 8x8 grids: one for constituent frame 0 (mostly 'X's) and one for constituent frame 1 (mostly 'O's). These are then processed through 'Upconversion processing' to produce larger 16x16 grids of 'X's and 'O's respectively, representing the upconverted colour component planes for constituent frames 0 and 1. + +Interleaved colour component plane of a column interleaved decoded frame + +Column interleaving decomposition + +Samples of colour component plane of constituent frame 0 + +Upconversion processing + +Upconverted colour component plane of constituent frame 0 + +Samples of colour component plane of constituent frame 1 + +Upconversion processing + +Upconverted colour component plane of constituent frame 1 + +H.264(17)\_FD.3 + +Diagram illustrating the rearrangement and upconversion of column interleaving. It shows the flow from an interleaved colour component plane through column interleaving decomposition into samples for constituent frames 0 and 1, followed by upconversion processing to produce upconverted colour component planes for each frame. The diagram includes 8x8 grids of 'X' and 'O' characters representing samples. + +**Figure D-3 – Rearrangement and upconversion of column interleaving with frame\_packing\_arrangement\_type equal to 1, quincunx\_sampling\_flag equal to 0, (x, y) equal to (0, 0) or (4, 8) for constituent frame 0 and (x, y) equal to (12, 8) for constituent frame 1** + +![Diagram illustrating the rearrangement and upconversion of row interleaving. It shows the flow from an interleaved colour component plane through row interleaving decomposition into samples for constituent frames 0 and 1, followed by upconversion processing to produce upconverted colour component planes for each frame. The diagram includes 8x8 grids of 'X' and 'O' characters representing samples.](5a2819c2426bdc3b4d4593dc4b1fba4e_img.jpg) + +The diagram shows the process of row interleaving decomposition and upconversion. It starts with an 8x8 grid of 'X' and 'O' characters representing an interleaved colour component plane. This is processed through 'Row interleaving decomposition' to produce two separate 8x8 grids: one for constituent frame 0 (mostly 'X's) and one for constituent frame 1 (mostly 'O's). These are then processed through 'Upconversion processing' to produce larger 16x16 grids of 'X's and 'O's respectively, representing the upconverted colour component planes for constituent frames 0 and 1. + +Interleaved colour component plane of a row interleaved decoded frame + +Row interleaving decomposition + +Samples of colour component plane of constituent frame 0 + +Upconversion processing + +Upconverted colour component plane of constituent frame 0 + +Samples of colour component plane of constituent frame 1 + +Upconversion processing + +Upconverted colour component plane of constituent frame 1 + +H.264(17)\_FD.4 + +Diagram illustrating the rearrangement and upconversion of row interleaving. It shows the flow from an interleaved colour component plane through row interleaving decomposition into samples for constituent frames 0 and 1, followed by upconversion processing to produce upconverted colour component planes for each frame. The diagram includes 8x8 grids of 'X' and 'O' characters representing samples. + +**Figure D-4 – Rearrangement and upconversion of row interleaving with frame\_packing\_arrangement\_type equal to 2, quincunx\_sampling\_flag equal to 0, and (x, y) equal to (0, 0) or (8, 4) for both constituent frames** + +![Diagram illustrating the rearrangement and upconversion of row interleaving. It shows the flow from an interleaved colour component plane through row interleaving decomposition into two constituent frames, followed by upconversion processing for each, resulting in upconverted colour component planes. The diagram uses 'X' and 'O' to represent samples in a grid. The first grid is 8x8 with alternating X and O. The second grid is 8x8 with only X samples. The third grid is 8x8 with only O samples. The upconverted grids are 16x16.](926c64a6177547a91f650c4c6f85ecb2_img.jpg) + +Interleaved colour component plane of a row interleaved decoded frame + +Row interleaving decomposition + +Samples of colour component plane of constituent frame 0 + +Upconversion processing + +Upconverted colour component plane of constituent frame 0 + +Samples of colour component plane of constituent frame 1 + +Upconversion processing + +Upconverted colour component plane of constituent frame 1 + +H.264(17)\_FD.5 + +Diagram illustrating the rearrangement and upconversion of row interleaving. It shows the flow from an interleaved colour component plane through row interleaving decomposition into two constituent frames, followed by upconversion processing for each, resulting in upconverted colour component planes. The diagram uses 'X' and 'O' to represent samples in a grid. The first grid is 8x8 with alternating X and O. The second grid is 8x8 with only X samples. The third grid is 8x8 with only O samples. The upconverted grids are 16x16. + +Figure D-5 – Rearrangement and upconversion of row interleaving with frame\_packing\_arrangement\_type equal to 2, quincunx\_sampling\_flag equal to 0, (x, y) equal to (0, 0) or (8, 4) for constituent frame 0, and (x, y) equal to (8, 12) for constituent frame 1 + +![Diagram illustrating the rearrangement and upconversion of side-by-side packing arrangement. It shows the flow from an interleaved colour component plane through side-by-side packing rearrangement into two constituent frames, followed by upconversion processing for each, resulting in upconverted colour component planes. The diagram uses 'X' and 'O' to represent samples in a grid. The first grid is 8x8 with X samples in the first 4 columns and O samples in the last 4 columns. The second grid is 8x8 with only X samples. The third grid is 8x8 with only O samples. The upconverted grids are 16x16.](91ee3a5581ec88bfc52991720cd93795_img.jpg) + +Interleaved colour component plane of side-by-side packed decoded frame + +Side-by side packing rearrangement + +Samples of colour component plane of constituent frame 0 + +Upconversion processing + +Upconverted colour component plane of constituent frame 0 + +Samples of colour component plane of constituent frame 1 + +Upconversion processing + +Upconverted colour component plane of constituent frame 1 + +H.264(17)\_FD.6 + +Diagram illustrating the rearrangement and upconversion of side-by-side packing arrangement. It shows the flow from an interleaved colour component plane through side-by-side packing rearrangement into two constituent frames, followed by upconversion processing for each, resulting in upconverted colour component planes. The diagram uses 'X' and 'O' to represent samples in a grid. The first grid is 8x8 with X samples in the first 4 columns and O samples in the last 4 columns. The second grid is 8x8 with only X samples. The third grid is 8x8 with only O samples. The upconverted grids are 16x16. + +Figure D-6 – Rearrangement and upconversion of side-by-side packing arrangement with frame\_packing\_arrangement\_type equal to 3, quincunx\_sampling\_flag equal to 0, and (x, y) equal to (0, 0) or (4, 8) for both constituent frames + +![Diagram showing the rearrangement and upconversion of side-by-side packing arrangement. It starts with an interleaved colour component plane of a side-by-side packed decoded frame (12x8 grid of X and O). This is processed through 'Side-by side packing rearrangement' to produce two separate grids: 'Samples of colour component plane of constituent frame 0' (8x8 grid of X) and 'Samples of colour component plane of constituent frame 1' (8x8 grid of O). These are then processed through 'Upconversion processing' to produce larger grids: 'Upconverted colour component plane of constituent frame 0' (16x16 grid of X) and 'Upconverted colour component plane of constituent frame 1' (16x16 grid of O). The diagram is labeled H.264(17)_FD.7.](7b325ed905fc90e53b5696554528d6e3_img.jpg) + +Diagram showing the rearrangement and upconversion of side-by-side packing arrangement. It starts with an interleaved colour component plane of a side-by-side packed decoded frame (12x8 grid of X and O). This is processed through 'Side-by side packing rearrangement' to produce two separate grids: 'Samples of colour component plane of constituent frame 0' (8x8 grid of X) and 'Samples of colour component plane of constituent frame 1' (8x8 grid of O). These are then processed through 'Upconversion processing' to produce larger grids: 'Upconverted colour component plane of constituent frame 0' (16x16 grid of X) and 'Upconverted colour component plane of constituent frame 1' (16x16 grid of O). The diagram is labeled H.264(17)\_FD.7. + +Figure D-7 – Rearrangement and upconversion of side-by-side packing arrangement with frame\_packing\_arrangement\_type equal to 3, quincunx\_sampling\_flag equal to 0, (x, y) equal to (12, 8) for constituent frame 0, and (x, y) equal to (0, 0) or (4, 8) for constituent frame 1 + +![Diagram showing the rearrangement and upconversion of top-bottom packing arrangement. It starts with an interleaved colour component plane of a top-bottom packed decoded frame (16x8 grid of X and O). This is processed through 'Top-bottom packing rearrangement' to produce two separate grids: 'Samples of colour component plane of constituent frame 0' (8x8 grid of X) and 'Samples of colour component plane of constituent frame 1' (8x8 grid of O). These are then processed through 'Upconversion processing' to produce larger grids: 'Upconverted colour component plane of constituent frame 0' (16x16 grid of X) and 'Upconverted colour component plane of constituent frame 1' (16x16 grid of O). The diagram is labeled H.264(19)_FD.8.](cf9dafde28ab662345982f029d24ae77_img.jpg) + +Diagram showing the rearrangement and upconversion of top-bottom packing arrangement. It starts with an interleaved colour component plane of a top-bottom packed decoded frame (16x8 grid of X and O). This is processed through 'Top-bottom packing rearrangement' to produce two separate grids: 'Samples of colour component plane of constituent frame 0' (8x8 grid of X) and 'Samples of colour component plane of constituent frame 1' (8x8 grid of O). These are then processed through 'Upconversion processing' to produce larger grids: 'Upconverted colour component plane of constituent frame 0' (16x16 grid of X) and 'Upconverted colour component plane of constituent frame 1' (16x16 grid of O). The diagram is labeled H.264(19)\_FD.8. + +Figure D-8 – Rearrangement and upconversion of top-bottom packing arrangement with frame\_packing\_arrangement\_type equal to 4, quincunx\_sampling\_flag equal to 0, and (x, y) equal to (0, 0) or (8, 4) for both constituent frames + +![Diagram illustrating the rearrangement and upconversion of top-bottom packing arrangement. It shows the flow from an interleaved colour component plane to separate planes for constituent frames 0 and 1 via top-bottom packing rearrangement, followed by upconversion processing to produce upconverted colour component planes.](37e0794107700a747532b186849ffa68_img.jpg) + +The diagram illustrates the process of rearranging and upconverting a top-bottom packed decoded frame. It starts with an **Interleaved colour component plane of a top-bottom packed decoded frame**, represented as a 10x10 grid of 'X' and 'O' characters. This is processed through **Top-bottom packing rearrangement** to produce two separate grids: **Samples of colour component plane of constituent frame 0** (containing 'X' characters) and **Samples of colour component plane of constituent frame 1** (containing 'O' characters). Both are then processed through **Upconversion processing** to produce the final **Upconverted colour component plane of constituent frame 0** and **Upconverted colour component plane of constituent frame 1**, both of which are 10x10 grids of 'X' and 'O' characters respectively. + +H.264(19)\_FD.9 + +Diagram illustrating the rearrangement and upconversion of top-bottom packing arrangement. It shows the flow from an interleaved colour component plane to separate planes for constituent frames 0 and 1 via top-bottom packing rearrangement, followed by upconversion processing to produce upconverted colour component planes. + +Figure D-9 – Rearrangement and upconversion of top-bottom packing arrangement with frame\_packing\_arrangement\_type equal to 4, quincunx\_sampling\_flag equal to 0, (x, y) equal to (8, 12) for constituent frame 0, and (x, y) equal to (0, 0) or (8, 4) for constituent frame 1 + +![Diagram illustrating the rearrangement and upconversion of top-bottom packing arrangement. It shows the flow from a side-by-side packed colour component plane through 'Side-by side quincunx packing rearrangement' to separate samples for constituent frames 0 and 1, which are then processed through 'Upconversion processing' to produce upconverted colour component planes.](83a2e09b22f494ed17fc9c23d1cd2921_img.jpg) + +The diagram shows the following process: + +- Input:** A 16x16 grid representing a side-by-side packed colour component plane. The left 8 columns contain 'X' (data for frame 0) and the right 8 columns contain 'O' (data for frame 1). Below it is the text: "Side-by-side packed colour component plane of a decoded frame with quincunx sampling". +- Rearrangement:** An arrow labeled "Side-by side quincunx packing rearrangement" points to two separate grids. + - The top grid represents "Samples of colour component plane of constituent frame 0" and contains 'X' characters in a sparse quincunx pattern. + - The bottom grid represents "Samples of colour component plane of constituent frame 1" and contains 'O' characters in a sparse quincunx pattern. +- Upconversion:** Each of these grids is processed through a block labeled "Upconversion processing". + - The top path results in an 8x16 grid of 'X' characters, labeled "Upconverted colour component plane of constituent frame 0". + - The bottom path results in an 8x16 grid of 'O' characters, labeled "Upconverted colour component plane of constituent frame 1". +- Reference:** The text "H.264(19)\_FD.10" is located at the bottom right of the diagram. + +Diagram illustrating the rearrangement and upconversion of top-bottom packing arrangement. It shows the flow from a side-by-side packed colour component plane through 'Side-by side quincunx packing rearrangement' to separate samples for constituent frames 0 and 1, which are then processed through 'Upconversion processing' to produce upconverted colour component planes. + +Figure D-10 – Rearrangement and upconversion of side-by-side packing arrangement with quincunx sampling (frame\_packing\_arrangement\_type equal to 3 with quincunx\_sampling\_flag equal to 1) + +![Diagram illustrating the rearrangement and upconversion of side-by-side packing arrangement with quincunx sampling. It shows the flow from sequentially decoded frames with temporal interleaving through 'Temporal interleaving decomposition' to separate samples for constituent frames 0 and 1, which are then upconverted.](d74ed29ed2b7aca01173043c14d46cab_img.jpg) + +The diagram shows the following process: + +- Input:** A sequence of four 3D blocks representing "Sequentially decoded frames with temporal interleaving frame arrangement". The blocks are labeled with temporal indices $2N$ , $2N+1$ , $2N+2$ , and $2N+3$ . Each block contains a mix of 'X' and 'O' characters. An arrow labeled $t$ indicates the temporal progression. +- Decomposition:** An arrow labeled "Temporal interleaving decomposition" points to two separate sequences of 3D blocks. + - The top sequence represents "Samples of colour component plane of constituent frames 0" and contains 'O' characters. The blocks are labeled $2N$ and $2N+2$ . + - The bottom sequence represents "Samples of colour component plane of constituent frames 1" and contains 'X' characters. The blocks are labeled $2N+1$ and $2N+3$ . + - An arrow labeled $t$ indicates the temporal progression for these sequences as well. +- Reference:** The text "H.264(17)\_FD.11" is located at the bottom right of the diagram. + +Diagram illustrating the rearrangement and upconversion of side-by-side packing arrangement with quincunx sampling. It shows the flow from sequentially decoded frames with temporal interleaving through 'Temporal interleaving decomposition' to separate samples for constituent frames 0 and 1, which are then upconverted. + +Figure D-11 – Rearrangement of a temporal interleaving frame arrangement +(frame\_packing\_arrangement\_type equal to 5) + +![Figure D-11 and D-12 diagrams showing frame rearrangement. Figure D-11 shows a source frame divided into regions R0, R1 (top half, filled with 'x') and R2, R3, R4 (bottom half, filled with 'o'). Figure D-12 shows these regions rearranged into two separate frames. One frame contains R1 and R3 (filled with 'o') with dimensions r1_W, r2_W, r1_H, r2_H, r3_H. The other frame contains R0 (filled with 'x') with dimensions r0_W and r0_H.](8e2056c5aa3b9d2021a48047657970f4_img.jpg) + +Figure D-11 and D-12 diagrams showing frame rearrangement. Figure D-11 shows a source frame divided into regions R0, R1 (top half, filled with 'x') and R2, R3, R4 (bottom half, filled with 'o'). Figure D-12 shows these regions rearranged into two separate frames. One frame contains R1 and R3 (filled with 'o') with dimensions r1\_W, r2\_W, r1\_H, r2\_H, r3\_H. The other frame contains R0 (filled with 'x') with dimensions r0\_W and r0\_H. + +Figure D-12 – Rearrangement and upconversion of tile format packing arrangement +(frame\_packing\_arrangement\_type equal to 7) + +#### D.2.27 Display orientation SEI message semantics + +This SEI message informs the decoder of a transformation that is recommended to be applied to the output decoded and cropped picture prior to display. + +**display\_orientation\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous display orientation SEI message in output order. **display\_orientation\_cancel\_flag** equal to 0 indicates that display orientation information follows. + +**hor\_flip** equal to 1 indicates that the cropped decoded picture should be flipped horizontally for display. **hor\_flip** equal to 0 indicates that the decoded picture should not be flipped horizontally. + +When **hor\_flip** is equal to 1, the cropped decoded picture should be flipped as follows for each colour component $Z = L, C_b, \text{ and } C_r$ , letting $dZ$ be the final cropped array of output samples for the component $Z$ : + +``` + +for( x = 0; x < croppedWidthInSamplesZ; x++ ) + for( y = 0; y < croppedHeightInSamplesZ; y++ ) + dZ[ x ][ y ] = Z[ croppedWidthInSamplesZ - x - 1 ][ y ] + +``` + +**ver\_flip** equal to 1 indicates that the cropped decoded picture should be flipped vertically (in addition to any horizontal flipping when **hor\_flip** is equal to 1) for display. **ver\_flip** equal to 0 indicates that the decoded picture should not be flipped vertically. + +When **ver\_flip** is equal to 1, the cropped decoded picture should be flipped as follows for each colour component $Z = L, C_b, \text{ and } C_r$ , letting $dZ$ be the final cropped array of output samples for the component $Z$ : + +``` + +for( x = 0; x < croppedWidthInSamplesZ; x++ ) + for( y = 0; y < croppedHeightInSamplesZ; y++ ) + dZ[ x ][ y ] = Z[ x ][ croppedHeightInSamplesZ - y - 1 ] + +``` + +**anticlockwise\_rotation** specifies the recommended anticlockwise rotation of the decoded picture (after applying horizontal and/or vertical flipping when **hor\_flip** or **ver\_flip** is set) prior to display. The decoded picture should be rotated by $360 * \text{anticlockwise\_rotation} \div 2^{16}$ degrees ( $2 * \pi * \text{anticlockwise\_rotation} \div 2^{16}$ radians, where $\pi$ is Archimedes' Constant (3.141 592 653 589 793 ...)) in the anticlockwise direction prior to display. For example, **anticlockwise\_rotation** + +equal to 0 indicates no rotation and anticlockwise\_rotation equal to 16 384 indicates 90 degrees ( $\pi \div 2$ radians) rotation in the anticlockwise direction. + +NOTE – It is possible for equivalent transformations to be expressed in multiple ways using these syntax elements. For example, the combination of having both hor\_flip and ver\_flip equal to 1 with anticlockwise\_rotation equal to 0 can alternatively be expressed by having both hor\_flip and ver\_flip equal to 1 with anticlockwise\_rotation equal to 0x8000000, and the combination of hor\_flip equal to 1 with ver\_flip equal to 0 and anticlockwise\_rotation equal to 0 can alternatively be expressed by having hor\_flip equal to 0 with ver\_flip equal to 1 and anticlockwise\_rotation equal to 0x8000000. + +**display\_orientation\_repetition\_period** specifies the persistence of the display orientation SEI message and may specify a picture order count interval within which another display orientation SEI message or the end of the coded video sequence shall be present in the bitstream. The value of display\_orientation\_repetition\_period shall be in the range 0 to 16 384, inclusive. + +display\_orientation\_repetition\_period equal to 0 specifies that the display orientation SEI message applies to the current decoded picture only. + +display\_orientation\_repetition\_period equal to 1 specifies that the display orientation SEI message persists in output order until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a display orientation SEI message is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ). + +display\_orientation\_repetition\_period greater than 1 specifies that the display orientation SEI message persists until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a display orientation SEI message is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ) and less than or equal to PicOrderCnt( CurrPic ) + display\_orientation\_repetition\_period. + +display\_orientation\_repetition\_period greater than 1 indicates that another display orientation SEI message shall be present for a picture in an access unit that is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ) and less than or equal to PicOrderCnt( CurrPic ) + display\_orientation\_repetition\_period; unless the bitstream ends or a new coded video sequence begins without output of such a picture. + +**display\_orientation\_extension\_flag** equal to 0 indicates that no additional data follows within the display orientation SEI message. The value of display\_orientation\_extension\_flag shall be equal to 0. The value of 1 for display\_orientation\_extension\_flag is reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all data that follows the value of 1 for display\_orientation\_extension\_flag in a display orientation SEI message. + +#### D.2.28 Green metadata SEI message semantics + +The semantics for this SEI message are specified in ISO/IEC 23001-11 (Green metadata), which facilitates reduced power consumption in decoders, encoders, displays, and in media selection. + +#### D.2.29 Mastering display colour volume SEI message semantics + +This SEI message identifies the colour volume (the colour primaries, white point, and luminance range) of a display considered to be the mastering display for the associated video content – e.g., the colour volume of a display that was used for viewing while authoring the video content. The described mastering display is a three-colour additive display system that has been configured to use the indicated mastering colour volume. + +This SEI message does not specify the measurement methodologies and procedures used for determining the indicated values or any description of the mastering environment. It also does not provide information on colour transformations that would be appropriate to preserve creative intent on displays with colour volumes different from that of the described mastering display. + +The information conveyed in this SEI message is intended to be adequate for purposes corresponding to the use of Society of Motion Picture and Television Engineers ST 2086. + +When a mastering display colour volume SEI message is present in any access unit of a coded video sequence, a mastering display colour volume SEI message shall be present in the IDR access unit that is the first access unit of the coded video sequence. All mastering display colour volume SEI messages that apply to the same coded video sequence shall have the same content. + +The mastering display colour volume SEI message persists in decoding order from the current access unit until the end of the coded video sequence. + +**display\_primaries\_x[ c ]**, when in the range of 5 to 37 000, inclusive, specifies the normalized x chromaticity coordinate of the colour primary component c of the mastering display, according to the CIE 1931 definition of x as specified in ISO 11664-1 (see also ISO 11664-3 and CIE 15), in increments of 0.00002. When display\_primaries\_x[ c ] is not in the range of 5 to 37 000, inclusive, the normalized x chromaticity coordinate of the colour primary component c of the mastering display is unknown or unspecified or specified by other means not specified in this Specification. + +**display\_primaries\_y[ c ]**, when in the range of 5 to 42 000, inclusive, specifies the normalized y chromaticity coordinate of the colour primary component c of the mastering display, according to the CIE 1931 definition of y as specified in ISO 11664-1 (see also ISO 11664-3 and CIE 15), in increments of 0.00002. When display\_primaries\_y[ c ] is not in the range of 5 to 42 000, inclusive, the normalized y chromaticity coordinate of the colour primary component c of the mastering display is unknown or unspecified or specified by other means not specified in this Specification. + +For describing mastering displays that use red, green, and blue colour primaries, it is suggested that index value c equal to 0 should correspond to the green primary, c equal to 1 should correspond to the blue primary and c equal to 2 should correspond to the red colour primary (see also Annex E and Table E-3). + +**white\_point\_x**, when in the range of 5 to 37 000, inclusive, specifies the normalized x chromaticity coordinate of the white point of the mastering display, according to the CIE 1931 definition of x as specified in ISO 11664-1 (see also ISO 11664-3 and CIE 15), in normalized increments of 0.00002. When white\_point\_x is not in the range of 5 to 37 000, inclusive, the normalized x chromaticity coordinate of the white point of the mastering display is indicated to be unknown or unspecified or specified by other means not specified in this Specification. + +**white\_point\_y**, when in the range of 5 to 42 000, inclusive, specifies the normalized y chromaticity coordinate of the white point of the mastering display, according to the CIE 1931 definition of y as specified in ISO 11664-1 (see also ISO 11664-3 and CIE 15), in normalized increments of 0.00002. When white\_point\_y is not in the range of 5 to 42 000, inclusive, the normalized y chromaticity coordinate of the white point of the mastering display is indicated to be unknown or unspecified or specified by other means not specified in this Specification. + +NOTE 1 – Society of Motion Picture and Television Engineers ST 2086 (2018) specifies that the normalized x and y chromaticity coordinate values for the mastering display colour primaries and white point are to be represented with four decimal places. This would correspond with using values of the syntax elements display\_primaries\_x[ c ], display\_primaries\_y[ c ], white\_point\_x, and white\_point\_y, as defined in this Specification, that are multiples of 5. + +NOTE 2 – An example of the use of values outside the range for which semantics are specified in this Specification is that ANSI/CTA 861-G (2016) uses normalized (x, y) chromaticity coordinate values of (0,0) for the white point to indicate that the white point chromaticity is unknown. + +**max\_display\_mastering\_luminance**, when in the range of 50 000 to 100 000 000, specifies the nominal maximum display luminance of the mastering display in units of 0.0001 candelas per square metre. When max\_display\_mastering\_luminance is not in the range of 50 000 to 100 000 000, the nominal maximum display luminance of the mastering display is indicated to be unknown or unspecified or specified by other means not specified in this Specification. + +NOTE 3 – Society of Motion Picture and Television Engineers ST 2086 (2018) specifies that the nominal maximum display luminance of the mastering display is to be specified as a multiple of 1 candela per square meter. This would correspond with using values of the syntax element max\_display\_mastering\_luminance, as defined in this Specification, that are a multiple of 10 000. + +NOTE 4 – An example of the use of values outside the range for which semantics are specified in this Specification is that ANSI/CTA 861-G (2016) uses the value 0 for the nominal maximum display luminance of the mastering display to indicate that the nominal maximum display luminance of the mastering display is unknown. + +**min\_display\_mastering\_luminance**, when in the range of 1 to 50 000, specifies the nominal minimum display luminance of the mastering display in units of 0.0001 candelas per square metre. When min\_display\_mastering\_luminance is not in the range of 1 to 50 000, the nominal maximum display luminance of the mastering display is unknown or unspecified or specified by other means not specified in this Specification. When max\_display\_mastering\_luminance is equal to 50 000, min\_display\_mastering\_luminance shall not be equal to 50 000. + +NOTE 5 – Society of Motion Picture and Television Engineers ST 2086 (2018) specifies that the nominal minimum display luminance of the mastering display is to be specified as a multiple of 0.0001 candelas per square metre, which corresponds to the semantics specified in this Specification. + +NOTE 6 – An example of the use of values outside the range for which semantics are specified in this Specification is that ANSI/CTA 861-G (2016) uses the value 0 for the nominal minimum display luminance of the mastering display to indicate that the nominal minimum display luminance of the mastering display is unknown. + +NOTE 7 – Another example of the potential use of values outside the range for which semantics are specified in this Specification is that Society of Motion Picture and Television Engineers ST 2086 (2018) indicates that values outside the specified range could be used to indicate that the black level and contrast of the mastering display have been adjusted using picture line-up generation equipment (PLUGE). + +At the minimum luminance, the mastering display is considered to have the same nominal chromaticity as the white point. + +### D.2.30 Colour remapping information SEI message semantics + +The colour remapping information SEI message provides information to enable remapping of the reconstructed colour samples of the output pictures for purposes such as converting the output pictures to a representation that is more suitable for an alternative display. The colour remapping model used in the colour remapping information SEI message is composed of a first piece-wise linear function applied to each colour component (specified by the "pre" set of syntax elements herein), followed by a three-by-three matrix applied to the three resulting colour components, followed by a second piece-wise linear function applied to each resulting colour component (specified by the "post" set of syntax elements herein). + +NOTE 1 – Colour remapping of the output pictures for the display process (which is outside the scope of this Specification) is optional and does not affect the decoding process specified in this Specification. + +Unless indicated otherwise by some means not specified in this Specification, the input to the indicated remapping process is the set of decoded sample values after applying an (unspecified) upsampling conversion process to the 4:4:4 colour sampling format as necessary when the colour remapping three-by-three matrix coefficients are present in the SEI message and chroma\_format\_idc is equal to 1 (4:2:0 chroma format) or 2 (4:2:2 chroma format). When chroma\_format\_idc is equal to 0 (monochrome), the colour remapping information SEI message shall not be present, although decoders shall allow such messages to be present and shall ignore any such colour remapping information SEI messages that may be present. + +**colour\_remap\_id** contains an identifying number that may be used to identify the purpose of the colour remapping information. The value of colour\_remap\_id may be used (in a manner not specified in this Specification) to indicate that the input to the remapping process is the output of some conversion process that is not specified in this Specification, such as a conversion of the picture to some alternative colour representation (e.g., conversion from a YCbCr colour representation to a GBR colour representation). When more than one colour remapping information SEI message is present with the same value of colour\_remap\_id, the content of these colour remapping information SEI messages shall be the same. When colour remapping information SEI messages are present that have more than one value of colour\_remap\_id, this may indicate that the remapping processes indicated by the different values of colour\_remap\_id are alternatives that are provided for different purposes or that a cascading of remapping processes is to be applied in a sequential order (an order that is not specified in this Specification). The value of colour\_remap\_id shall be in the range of 0 to $2^{32} - 2$ , inclusive. + +Values of colour\_remap\_id from 0 to 255, inclusive, and from 512 to $2^{31} - 1$ , inclusive, may be used as determined by the application. Values of colour\_remap\_id from 256 to 511, inclusive, and from $2^{31}$ to $2^{32} - 2$ , inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of colour\_remap\_id in the range of 256 to 511, inclusive, or in the range of $2^{31}$ to $2^{32} - 2$ , inclusive, shall ignore it. + +NOTE 2 – The colour\_remap\_id can be used to support different colour remapping processes that are suitable for different display scenarios. For example, different values of colour\_remap\_id may correspond to different remapped colour spaces supported by displays. + +**colour\_remap\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous colour remapping information SEI message in output order that applies to the current layer. colour\_remap\_cancel\_flag equal to 0 indicates that colour remapping information follows. + +**colour\_remap\_repetition\_period** specifies the persistence of the colour remapping information SEI message and may specify a picture order count interval within which another colour remapping information SEI message with the same value of colour\_remap\_id or the end of the coded video sequence shall be present in the bitstream. The value of colour\_remap\_repetition\_period shall be in the range of 0 to 16 384, inclusive. + +colour\_remap\_repetition\_period equal to 0 specifies that the colour remapping information applies to the current decoded picture only. + +colour\_remap\_repetition\_period equal to 1 specifies that the colour remapping information persists in output order until any of the following conditions are true: + +- A new coded video sequence begins. +- A picture in an access unit containing a colour remapping information SEI message with the same value of colour\_remap\_id is output having PicOrderCnt( ) greater than PicOrderCnt( CurrPic ). + +colour\_remap\_repetition\_period equal to 0 or equal to 1 indicates that another colour remapping information SEI message with the same value of colour\_remap\_id may or may not be present. + +colour\_remap\_repetition\_period greater than 1 specifies that the colour remapping information persists until any of the following conditions are true: + +- A new coded video sequence begins. + +- A picture in an access unit containing a colour remapping information SEI message with the same value of `colour_remap_id` is output having `PicOrderCnt()` greater than `PicOrderCnt( CurrPic )` and less than or equal to `PicOrderCnt( CurrPic ) + colour_remap_repetition_period`. + +`colour_remap_repetition_period` greater than 1 indicates that another colour remapping information SEI message with the same value of `colour_remap_id` shall be present for a picture in an access unit that is output having `PicOrderCnt()` greater than `PicOrderCnt( CurrPic )` and less than or equal to `PicOrderCnt( CurrPic ) + colour_remap_repetition_period`; unless the bitstream ends or a new coded video sequence begins without output of such a picture. + +**`colour_remap_video_signal_info_present_flag`** equal to 1 specifies that syntax elements `colour_remap_full_range_flag`, `colour_remap_primaries`, `colour_remap_transfer_function` and `colour_remap_matrix_coefficients` are present, `colour_remap_video_signal_info_present_flag` equal to 0 specifies that syntax elements `colour_remap_full_range_flag`, `colour_remap_primaries`, `colour_remap_transfer_function` and `colour_remap_matrix_coefficients` are not present. + +**`colour_remap_full_range_flag`** has the same semantics as specified in clause E.2.1 for the `video_full_range_flag` syntax element, except that `colour_remap_full_range_flag` identifies the colour space of the remapped reconstructed picture, rather than the colour space used for the coded video sequence. When not present, the value of `colour_remap_full_range_flag` is inferred to be equal to the value of `video_full_range_flag`. + +**`colour_remap_primaries`** has the same semantics as specified in clause E.2.1 for the `colour_primaries` syntax element, except that `colour_remap_primaries` identifies the colour space of the remapped reconstructed picture, rather than the colour space used for the coded video sequence. When not present, the value of `colour_remap_primaries` is inferred to be equal to the value of `colour_primaries`. + +**`colour_remap_transfer_function`** has the same semantics as specified in clause E.2.1 for the `transfer_characteristics` syntax element, except that `colour_remap_transfer_function` identifies the colour space of the remapped reconstructed picture, rather than the colour space used for the coded video sequence. When not present, the value of `colour_remap_transfer_function` is inferred to be equal to the value of `transfer_characteristics`. + +**`colour_remap_matrix_coefficients`** has the same semantics as specified in clause E.2.1 for the `matrix_coefficients` syntax element, except that `colour_remap_matrix_coefficients` identifies the colour space of the remapped reconstructed picture, rather than the colour space used for the coded video sequence. When not present, the value of `colour_remap_matrix_coefficients` is inferred to be equal to the value of `matrix_coefficients`. + +**`colour_remap_input_bit_depth`** specifies the bit depth of the colour components of the associated pictures for purposes of interpretation of the colour remapping information SEI message. When any colour remapping information SEI messages is present with the value of `colour_remap_input_bit_depth` not equal to the bit depth of the decoded colour components, the SEI message refers to the hypothetical result of a conversion operation performed to convert the decoded colour component samples to the bit depth equal to `colour_remap_input_bit_depth`. + +The value of `colour_remap_input_bit_depth` shall be in the range of 8 to 16, inclusive. Values of `colour_remap_input_bit_depth` from 0 to 7, inclusive, and from 17 to 255, inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all colour remapping SEI messages that contain a `colour_remap_input_bit_depth` in the range of 0 to 7, inclusive, or in the range of 17 to 255, inclusive, and bitstreams shall not contain such values. + +**`colour_remap_output_bit_depth`** specifies the bit depth of the output of the colour remapping function described by the colour remapping information SEI message. + +The value of `colour_remap_output_bit_depth` shall be in the range of 8 to 16, inclusive. Values of `colour_remap_output_bit_depth` from 0 to 7, inclusive, and in the range of 17 to 255, inclusive, are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all colour remapping SEI messages that contain a value of `colour_remap_output_bit_depth` from 0 to 7, inclusive, or in the range of 17 to 255, inclusive, and bitstreams shall not contain such values. + +**`pre_lut_num_val_minus1[ c ]`** plus 1 specifies the number of pivot points in the piece-wise linear remapping function for the `c`-th component, where `c` equal to 0 refers to the luma or G component, `c` equal to 1 refers to the Cb or B component, and `c` equal to 2 refers to the Cr or R component. When `pre_lut_num_val_minus1[ c ]` is equal to 0, the default end points of the input values are 0 and $2^{\text{colour\_remap\_input\_bit\_depth}} - 1$ , and the corresponding default end points of the output values are 0 and $2^{\text{colour\_remap\_output\_bit\_depth}} - 1$ , for the `c`-th component. In bitstreams conforming to this version of this Specification, the value of `pre_lut_num_val_minus1[ c ]` shall be in the range of 0 to 32, inclusive. + +**`pre_lut_coded_value[ c ][ i ]`** specifies the value of the `i`-th pivot point for the `c`-th component. The number of bits used to represent `pre_lut_coded_value[ c ][ i ]` is $(( \text{colour\_remap\_input\_bit\_depth} + 7 ) \gg 3) \ll 3$ . + +**`pre_lut_target_value[ c ][ i ]`** specifies the value of the `i`-th pivot point for the `c`-th component. The number of bits used to represent `pre_lut_target_value[ c ][ i ]` is $(( \text{colour\_remap\_output\_bit\_depth} + 7 ) \gg 3) \ll 3$ . + +When $pre\_lut\_coded\_value[ c ][ 0 ]$ is greater than 0, an initial linear segment should be inferred that maps input values ranging from 0 to $pre\_lut\_coded\_value[ c ][ 0 ]$ , inclusive, to target values ranging from 0 to $pre\_lut\_target\_value[ c ][ 0 ]$ , inclusive. + +When $pre\_lut\_coded\_value[ c ][ pre\_lut\_num\_val\_minus1[ c ] ]$ is not equal to $2^{colour\_remap\_input\_bit\_depth} - 1$ , a final linear segment should be inferred that maps input values ranging from $pre\_lut\_coded\_value[ c ][ pre\_lut\_num\_val\_minus1[ c ] ]$ to $2^{colour\_remap\_input\_bit\_depth} - 1$ , inclusive, to target values ranging from $pre\_lut\_target\_value[ c ][ pre\_lut\_num\_val\_minus1[ c ] ]$ to $2^{colour\_remap\_output\_bit\_depth} - 1$ , inclusive. + +**colour\_remap\_matrix\_present\_flag** equal to 1 indicates that the syntax elements $log2\_matrix\_denom$ and $colour\_remap\_coeffs[ c ][ i ]$ , for $c$ and $i$ in the range of 0 to 2, inclusive, are present. $colour\_remap\_matrix\_present\_flag$ equal to 0 indicates that the syntax elements $log2\_matrix\_denom$ and $colour\_remap\_coeffs[ c ][ i ]$ , for $c$ and $i$ in the range of 0 to 2, inclusive, are not present. + +**log2\_matrix\_denom** specifies the base 2 logarithm of the denominator for all matrix coefficients. The value of $log2\_matrix\_denom$ shall be in the range of 0 to 15, inclusive. When not present, the value of $log2\_matrix\_denom$ is inferred to be equal to 0. + +**colour\_remap\_coeffs[ c ][ i ]** specifies the value of the three-by-three colour remapping matrix coefficients. The value of $colour\_remap\_coeffs[ c ][ i ]$ shall be in the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. When $colour\_remap\_coeffs[ c ][ i ]$ is not present, it is inferred to be equal to 1 if $c$ is equal to $i$ , and inferred to be equal to 0 otherwise. + +NOTE 3 – When $colour\_remap\_matrix\_present\_flag$ is equal to 0, the colour remapping matrix is inferred to be equal to the identity matrix of size $3 \times 3$ . + +The variable $matrixOutput[ c ]$ for $c = 0, 1$ and $2$ is derived as follows: + +$$\begin{aligned} roundingOffset &= log2\_matrix\_denom == 0 ? 0 : 1 \ll ( log2\_matrix\_denom - 1 ) \\ matrixOutput[ c ] &= Clip3( 0, ( 1 \ll colour\_remap\_output\_bit\_depth ) - 1, \\ &\quad ( colour\_remap\_coeffs[ c ][ 0 ] * matrixInput[ 0 ] + colour\_remap\_coeffs[ c ][ 1 ] * matrixInput[ 1 ] \\ &\quad + colour\_remap\_coeffs[ c ][ 2 ] * matrixInput[ 2 ] + roundingOffset ) \gg log2\_matrix\_denom ) \end{aligned} \quad (D-44)$$ + +where $matrixInput[ c ]$ is the input sample value of the $c$ -th colour component, and $matrixOutput[ c ]$ is the output sample value of the $c$ -th colour component. + +**post\_lut\_num\_val\_minus1[ c ]** has the same semantics as $pre\_lut\_num\_val\_minus1[ c ]$ , with $pre$ replaced by $post$ , except that the default end points of the input values are 0 and $2^{colour\_remap\_output\_bit\_depth} - 1$ for the $c$ -th colour component. The value of $post\_lut\_num\_val\_minus1[ c ]$ shall be in the range of 0 to 32, inclusive. + +**post\_lut\_coded\_value[ c ][ i ]** has the same semantics as $pre\_lut\_coded\_value[ c ][ i ]$ , with "pre" replaced by "post", except that the number of bits used to represent $post\_lut\_coded\_value[ c ][ i ]$ is $(( colour\_remap\_output\_bit\_depth + 7 ) \gg 3 ) \ll 3$ . + +**post\_lut\_target\_value[ c ][ i ]** has the same semantics as $pre\_lut\_target\_value[ c ][ i ]$ , with "pre" replaced by "post" except that $colour\_remap\_input\_bit\_depth$ is replaced by $colour\_remap\_output\_bit\_depth$ in the semantics. + +### D.2.31 Content light level information SEI message semantics + +This SEI message identifies upper bounds for the nominal target brightness light level of the pictures of the coded video sequence. + +The information conveyed in this SEI message is intended to be adequate for purposes corresponding to the use of the Consumer Technology Association 861.3 specification. + +The semantics of the content light level information SEI message are defined in relation to the values of samples in a 4:4:4 representation of red, green, and blue colour primary intensities in the linear light domain for the pictures of the coded video sequence, in units of candelas per square metre. However, this SEI message does not, by itself, identify a conversion process for converting the sample values of a decoded picture to the samples in a 4:4:4 representation of red, green, and blue colour primary intensities in the linear light domain for the picture. + +NOTE 1 – Other syntax elements, such as $colour\_primaries$ , $transfer\_characteristics$ , $matrix\_coefficients$ , and the chroma resampling filter hint SEI message, when present, may assist in the identification of such a conversion process. + +Given the red, green, and blue colour primary intensities in the linear light domain for the location of a luma sample in a corresponding 4:4:4 representation, denoted as $E_R$ , $E_G$ , and $E_B$ , the maximum component intensity is defined as $E_{Max} = \text{Max}( E_R, \text{Max}( E_G, E_B ) )$ . The light level corresponding to the stimulus is then defined as the CIE 1931 luminance corresponding to equal amplitudes of $E_{Max}$ for all three colour primary intensities for red, green, and blue (with appropriate scaling to reflect the nominal luminance level associated with peak white – e.g., ordinarily scaling to associate peak white with 10 000 candelas per square metre when $transfer\_characteristics$ is equal to 16). + +NOTE 2 – Since the maximum value $E_{\text{Max}}$ is used in this definition at each sample location, rather than a direct conversion from $E_R$ , $E_G$ , and $E_B$ to the corresponding CIE 1931 luminance, the CIE 1931 luminance at a location may in some cases be less than the indicated light level. This situation would occur, for example, when $E_R$ and $E_G$ are very small and $E_B$ is large, in which case the indicated light level would be much larger than the true CIE 1931 luminance associated with the ( $E_R$ , $E_G$ , $E_B$ ) triplet. + +When a content light level information SEI message is present in any access unit of a coded video sequence, a content light level information SEI message shall be present in the IDR access unit that is the first access unit of the coded video sequence. All content light level information SEI messages that apply to the same coded video sequence shall have the same content. + +The content light level information SEI message persists in decoding order from the current access unit until the end of the coded video sequence. + +**max\_content\_light\_level**, when not equal to 0, indicates an upper bound on the maximum light level among all individual samples in a 4:4:4 representation of red, green, and blue colour primary intensities (in the linear light domain) for the pictures of the coded video sequence, in units of candelas per square metre. When equal to 0, no such upper bound is indicated by max\_content\_light\_level. + +**max\_pic\_average\_light\_level**, when not equal to 0, indicates an upper bound on the maximum average light level among the samples in a 4:4:4 representation of red, green, and blue colour primary intensities (in the linear light domain) for any individual picture of the coded video sequence, in units of candelas per square metre. When equal to 0, no such upper bound is indicated by max\_pic\_average\_light\_level. + +NOTE 3 – When the visually relevant region does not correspond to the entire cropped decoded picture, such as for "letterbox" encoding of video content with a wide picture aspect ratio within a taller cropped decoded picture, the indicated average should be performed only within the visually relevant region. + +#### D.2.32 Alternative transfer characteristics SEI message semantics + +The alternative transfer characteristics SEI message provides a preferred alternative value for the transfer\_characteristics syntax element that is indicated by the colour description syntax of VUI parameters of the sequence parameter set. This SEI message is intended to be used in cases when some value of transfer\_characteristics is preferred for interpretation of the pictures of the coded video sequence although some other value of transfer\_characteristics may also be acceptable for interpretation of the pictures of the coded video sequence and that other value is provided in the colour description syntax of VUI parameters of the sequence parameter set for interpretation by decoders that do not support interpretation of the preferred value (e.g., because the preferred value had not yet been defined in a previous version of this Specification). + +When an alternative transfer characteristics SEI message is present for any picture of a coded video sequence, an alternative transfer characteristics SEI message shall be present for the IDR picture of the coded video sequence. The alternative transfer characteristics SEI message persists in decoding order from the current picture until the end of the coded video sequence. All alternative transfer characteristics SEI messages that apply to the same coded video sequence shall have the same content. + +**preferred\_transfer\_characteristics** specifies a preferred alternative value for the transfer\_characteristics syntax element of the colour description syntax of VUI parameters of the sequence parameter set. The semantics for preferred\_transfer\_characteristics are otherwise the same as for the transfer\_characteristics syntax element specified in the VUI parameters of the sequence parameter set (see clause E.2.1 and Table E-4). When preferred\_transfer\_characteristics is not equal to the value of transfer\_characteristics indicated in the VUI parameters of the sequence parameter set, decoders should ignore the value of transfer\_characteristics indicated in the VUI parameters of the sequence parameter set and instead use the value indicated by preferred\_transfer\_characteristics. + +#### D.2.33 Content colour volume SEI message semantics + +The content colour volume SEI message describes the colour volume characteristics of the associated pictures. These colour volume characteristics are expressed in terms of a nominal range, although deviations from this range may occur. + +The variable transferCharacteristics is specified as follows: + +- If an alternative transfer characteristics SEI message is present for the coded video sequence, transferCharacteristics is set equal to preferred\_transfer\_characteristics; +- Otherwise, (an alternative transfer characteristics SEI message is not present for the coded video sequence), transferCharacteristics is set equal to transfer\_characteristics. + +The content colour volume SEI message shall not be present, and decoders shall ignore it, when any of the following conditions is true: + +- Any of the values of transferCharacteristics, colour\_primaries, and matrix\_coefficients has a value defined as unspecified. +- The value of transfer\_characteristics is equal to 2, 4, or 5. + +- The value of `colour_primaries` is equal to 2. + +The following applies when converting the signal from a non-linear to a linear representation: + +- If the value of `transferCharacteristics` is equal to 1, 6, 7, 14, or 15, the Rec. ITU-R BT.1886-0 reference electro-optical transfer function should be used to convert the signal to its linear representation, where the value of screen luminance for white is set equal to 100 cd/m2, the value of screen luminance for black is set equal to 0 cd/m2, and the value of the exponent of the power function is set equal to 2.4. +- Otherwise, if the value of `transferCharacteristics` is equal to 18, the hybrid log-gamma reference electro-optical transfer function specified in Rec. ITU-R BT.2100-2 should be used to convert the signal to its linear representation, where the value of nominal peak luminance of the display is set equal to 1000 cd/m2, the value of the display luminance for black is set equal to 0 cd/m2, and the value of system gamma is set equal to 1.2. +- Otherwise (the value of `transferCharacteristics` is not equal to 1, 6, 7, 14, 15, or 18) when the content colour volume SEI message is present, the exact inverse of the transfer function specified in Table E-4 should be used to convert the non-linear signal to a linear representation. + +**ccv\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous content colour volume SEI message in output order. `ccv_cancel_flag` equal to 0 indicates that content colour volume information follows. + +**ccv\_persistence\_flag** specifies the persistence of the content colour volume SEI message. + +`ccv_persistence_flag` equal to 0 specifies that the content colour volume SEI message applies to the current decoded picture only. + +Let `picA` be the current picture. `ccv_persistence_flag` equal to 1 specifies that the content colour volume SEI message persists in output order until one or more of the following conditions are true: + +- A new coded video sequence begins. +- The bitstream ends. +- A picture `picB` in an access unit containing a content colour volume SEI message is output having `PicOrderCnt(picB)` greater than `PicOrderCnt(picA)`. + +**ccv\_primaries\_present\_flag** equal to 1 specifies that the syntax elements `ccv_primaries_x[ c ]` and `ccv_primaries_y[ c ]` are present. `ccv_primaries_present_flag` equal to 0 specifies that the syntax elements `ccv_primaries_x[ c ]` and `ccv_primaries_y[ c ]` are not present. + +**ccv\_min\_luminance\_value\_present\_flag** equal to 1 specifies that the syntax element `ccv_min_luminance_value` is present. `ccv_min_luminance_value_present_flag` equal to 0 specifies that the syntax element `ccv_min_luminance_value` is not present. + +**ccv\_max\_luminance\_value\_present\_flag** equal to 1 specifies that the syntax element `ccv_max_luminance_value` is present. `ccv_max_luminance_value_present_flag` equal to 0 specifies that the syntax element `ccv_max_luminance_value` is not present. + +**ccv\_avg\_luminance\_value\_present\_flag** equal to 1 specifies that the syntax element `ccv_avg_luminance_value` is present. `ccv_avg_luminance_value_present_flag` equal to 0 specifies that the syntax element `ccv_avg_luminance_value` is not present. + +It is a requirement of bitstream conformance that the values of `ccv_primaries_present_flag`, `ccv_min_luminance_value_present_flag`, `ccv_max_luminance_value_present_flag`, and `ccv_avg_luminance_value_present_flag` shall not all be equal to 0. + +**ccv\_reserved\_zero\_2bits** shall be equal to 0 in bitstreams conforming to this version of this Specification. Other values for `ccv_reserved_zero_2bits` are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore the value of `ccv_reserved_zero_2bits`. + +**ccv\_primaries\_x[ c ]** and **ccv\_primaries\_y[ c ]** specify the normalized x and y chromaticity coordinates, respectively, of the colour primary component `c` of the nominal content colour volume in normalized increments of 0.00002, according to the CIE 1931 definition of x and y as specified in ISO 11664-1 (see also ISO 11664-3 and CIE 15), in normalized increments of 0.00002. For describing colour volumes that use red, green, and blue colour primaries, it is suggested that index value `c` equal to 0 should correspond to the green primary, `c` equal to 1 should correspond to the blue primary, and `c` equal to 2 should correspond to the red colour primary (see also Annex E and Table E-3). + +The values of `ccv_primaries_x[ c ]` and `ccv_primaries_y[ c ]` shall be in the range of –5 000 000 to 5 000 000, inclusive. + +When `ccv_primaries_x[ c ]` and `ccv_primaries_y[ c ]` are not present, they are inferred to be equal to the normalized x and y chromaticity coordinates, respectively, specified by `colour_primaries`. + +**ccv\_min\_luminance\_value** specifies the normalized minimum luminance value, according to CIE 1931, that is expected to be present in the content, where values are normalized to $L_o$ or $L_c$ as specified in Table E-4 according to the indicated transfer characteristics of the signal. The values of **ccv\_min\_luminance\_value** are in normalized increments of 0.0000001. + +**ccv\_max\_luminance\_value** specifies the maximum luminance value, according to CIE 1931, that is expected to be present in the content, where values are normalized to $L_o$ or $L_c$ as specified in Table E-4 according to the transfer characteristics of the signal. The values of **ccv\_max\_luminance\_value** are in normalized increments of 0.0000001. + +**ccv\_avg\_luminance\_value** specifies the average luminance value, according to CIE 1931, that is expected to be present in the content, where values are normalized to $L_o$ or $L_c$ as specified in Table E-4 according to the transfer characteristics of the signal. The values of **ccv\_avg\_luminance\_value** are in normalized increments of 0.0000001. + +NOTE – The resulting domain from this conversion process may or may not represent light in a source or display domain – it is merely a gamut representation domain rather than necessarily being a representation of actual light in either the scene or display domain. Therefore, the values corresponding to **ccv\_min\_luminance\_value**, **ccv\_max\_luminance\_value**, and **ccv\_avg\_luminance\_value** might not necessarily correspond to a true luminance value. + +The value of **ccv\_min\_luminance\_value**, when present, shall be less than or equal to **ccv\_avg\_luminance\_value**, when present. The value of **ccv\_avg\_luminance\_value**, when present, shall be less than or equal to **ccv\_max\_luminance\_value**, when present. The value of **ccv\_min\_luminance\_value**, when present, shall be less than or equal to **ccv\_max\_luminance\_value**, when present. + +When the visually relevant region does not correspond to the entire cropped decoded picture, such as for "letterbox" encoding of video content with a wide picture aspect ratio within a taller cropped decoded picture, the indicated **ccv\_min\_luminance\_value**, **ccv\_max\_luminance\_value**, and **ccv\_avg\_luminance\_value** should correspond only to values within the visually relevant region. + +#### D.2.34 Ambient viewing environment SEI message semantics + +The ambient viewing environment SEI message identifies the characteristics of the nominal ambient viewing environment for the display of the associated video content. The syntax elements of the ambient viewing environment SEI message may assist the receiving system in adapting the received video content for local display in viewing environments that may be similar or may substantially differ from those assumed or intended when mastering the video content. + +This SEI message does not provide information on colour transformations that would be appropriate to preserve creative intent on displays with colour volumes different from that of the described mastering display. + +When an ambient viewing environment SEI message is present for any picture of a coded video sequence, an ambient viewing environment SEI message shall be present in the IDR access unit that is the first access unit of the coded video sequence. All ambient viewing environment SEI messages that apply to the same coded video sequence shall have the same content. + +**ambient\_illuminance** specifies the environmental illuminance of the ambient viewing environment in units of 0.0001 lux. **ambient\_illuminance** shall not be equal to 0. + +**ambient\_light\_x** and **ambient\_light\_y** specify the normalized x and y chromaticity coordinates, respectively, of the environmental ambient light in the nominal viewing environment, according to the CIE 1931 definition of x and y as specified in ISO 11664-1 (see also ISO 11664-3 and CIE 15), in normalized increments of 0.00002. The values of **ambient\_light\_x** and **ambient\_light\_y** shall be in the range of 0 to 50 000, inclusive. + +NOTE – For example, the conditions identified in Rec. ITU-R BT.2035 can be expressed using **ambient\_illuminance** equal to 100 000 with background chromaticity indicating D65 (**ambient\_light\_x** equal to 15 635, **ambient\_light\_y** equal to 16 450), or optionally in some regions, background chromaticity indicating D93 (**ambient\_light\_x** equal to 14 155, **ambient\_light\_y** equal to 14 855). + +#### D.2.35 Semantics of omnidirectional video specific SEI messages + +##### D.2.35.1 Equirectangular projection SEI message semantics + +The equirectangular projection SEI message provides information to enable remapping (through an equirectangular projection) of the colour samples of the projected pictures onto a sphere coordinate space in sphere coordinates ( $\phi$ , $\theta$ ) for use in omnidirectional video applications for which the viewing perspective is from the origin looking outward toward the inside of the sphere. The sphere coordinates are defined so that $\phi$ is the azimuth (longitude, increasing eastward) and $\theta$ is the elevation (latitude, increasing northward). + +When an equirectangular projection SEI message is present for any picture of a coded video sequence, an equirectangular projection SEI message shall be present for the first picture of the coded video sequence and no SEI message indicating a different type of projection shall be present for any picture of the coded video sequence. + +When **aspect\_ratio\_idc** is present and greater than 1 in the active sequence parameter set, there should be no equirectangular projection SEI messages applicable for any picture of the coded video sequence. + +A frame packing arrangement SEI message for which all the following conditions are true is referred to as an effectively applicable frame packing arrangement SEI message: + +- The value of `frame_packing_arrangement_cancel_flag` is equal to 0. +- The value of `frame_packing_arrangement_type` is equal to 3, 4, or 5. +- The value of `quincunx_sampling_flag` is equal to 0. +- The value of `spatial_flipping_flag` is equal to 0. +- The value of `field_views_flag` is equal to 0. +- The value of `frame0_grid_position_x` is equal to 0. +- The value of `frame0_grid_position_y` is equal to 0. +- The value of `frame1_grid_position_x` is equal to 0. +- The value of `frame1_grid_position_y` is equal to 0. + +When an effectively applicable frame packing arrangement SEI message that applies to the picture is not present, an equirectangular projection SEI message with `erp_cancel_flag` equal to 0 that applies to the picture shall not be present. Decoders shall ignore equirectangular projection SEI messages when an effectively applicable frame packing arrangement SEI message that applies to the picture is not present. + +**erp\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous equirectangular projection SEI message in output order. `erp_cancel_flag` equal to 0 indicates that equirectangular projection information follows. + +**erp\_persistence\_flag** specifies the persistence of the equirectangular projection SEI message. + +`erp_persistence_flag` equal to 0 specifies that the equirectangular projection SEI message applies to the current decoded picture only. + +Let `picA` be the current picture. `erp_persistence_flag` equal to 1 specifies that the equirectangular projection SEI message persists in output order until one or more of the following conditions are true: + +- A new coded video sequence begins. +- The bitstream ends. +- A picture `picB` in an access unit containing an equirectangular projection SEI message is output having `PicOrderCnt( picB )` greater than `PicOrderCnt( picA )`. + +**erp\_padding\_flag** equal to 1 indicates that the constituent picture contains padded areas for which the sizes are specified by the syntax elements `left_gb_erp_width` and `right_gb_erp_width`. `erp_padding_flag` equal to 0 indicates that the constituent picture does not contain padded areas for which the sizes are specified by the syntax elements `left_gb_erp_width` and `right_gb_erp_width`. + +**erp\_reserved\_zero\_2bits** shall be equal to 0 in bitstreams conforming to this version of this Specification. Other values for `erp_reserved_zero_2bits` are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore the value of `erp_reserved_zero_2bits`. + +**gb\_erp\_type** specifies the type of the guard bands as follows: + +- `gb_erp_type` equal to 0 specifies that the content of the guard band in relation to the content of the constituent picture is unspecified. +- `gb_erp_type` equal to 1 specifies that the content of the guard band suffices for interpolation of sample values at sub-pel sample fractional locations within the constituent picture. + +NOTE – `gb_erp_type` equal to 1 could be used when the boundary samples of a constituent picture have been copied horizontally to the guard band. + +- `gb_erp_type` equal to 2 specifies that the content of the guard band represents actual picture content at quality that gradually changes from the picture quality of the constituent picture. +- `gb_erp_type` equal to 3 specifies that the content of the guard bands represents actual picture content at a similar level of quality as the constituent picture. +- `gb_erp_type` values greater than 3 are reserved. Decoders shall ignore the value of `gb_erp_type` when the value is greater than 3. + +**left\_gb\_erp\_width** specifies the width of the guard band on the left side of the constituent picture in units of luma samples. When `erp_padding_flag` is equal to 0, the value of `left_gb_erp_width` is inferred to be equal to 0. When the decoded picture has 4:2:0 or 4:2:2 chroma format, `left_gb_erp_width` shall be an even number. + +**right\_gb\_erp\_width** specifies the width of the guard band on the right side of the constituent picture in units of luma samples. When **erp\_padding\_flag** is equal to 0, the value of **right\_gb\_erp\_width** is inferred to be equal to 0. When the decoded picture has 4:2:0 or 4:2:2 chroma format, **right\_gb\_erp\_width** shall be an even number. + +#### D.2.35.2 Cubemap projection SEI message semantics + +The cubemap projection SEI message provides information to enable remapping (through a cubemap projection) of the colour samples of the projected pictures onto a sphere coordinate space in sphere coordinates ( $\phi$ , $\theta$ ) for use in omnidirectional video applications for which the viewing perspective is from the origin looking outward toward the inside of the sphere. The sphere coordinates are defined so that $\phi$ is the azimuth (longitude, increasing eastward) and $\theta$ is the elevation (latitude, increasing northward). + +When a cubemap projection SEI message is present for any picture of a coded video sequence, a cubemap projection SEI message shall be present for the first picture of the coded video sequence and no SEI message indicating a different type of projection shall be present for any picture. + +When **aspect\_ratio\_idc** is present and greater than 1 in the active sequence parameter set, there should be no cubemap projection SEI messages applicable for any picture of the coded video sequence. + +A frame packing arrangement SEI message for which all the following conditions are true is referred to as an effectively applicable frame packing arrangement SEI message: + +- The value of **frame\_packing\_arrangement\_cancel\_flag** is equal to 0. +- The value of **frame\_packing\_arrangement\_type** is equal to 3, 4, or 5. +- The value of **quincunx\_sampling\_flag** is equal to 0. +- The value of **spatial\_flipping\_flag** is equal to 0. +- The value of **field\_views\_flag** is equal to 0. +- The value of **frame0\_grid\_position\_x** is equal to 0. +- The value of **frame0\_grid\_position\_y** is equal to 0. +- The value of **frame1\_grid\_position\_x** is equal to 0. +- The value of **frame1\_grid\_position\_y** is equal to 0. + +When an effectively applicable frame packing arrangement SEI message that applies to the picture is not present, a cubemap projection SEI message with **cmp\_cancel\_flag** equal to 0 that applies to the picture shall not be present. Decoders shall ignore cubemap projection SEI messages when an effectively applicable frame packing arrangement SEI message that applies to the picture is not present. + +**cmp\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous cubemap projection SEI message in output order. **cmp\_cancel\_flag** equal to 0 indicates that cubemap projection information follows. + +**cmp\_persistence\_flag** specifies the persistence of the cubemap projection SEI message. + +**cmp\_persistence\_flag** equal to 0 specifies that the cubemap projection SEI message applies to the current decoded picture only. + +Let **picA** be the current picture. **cmp\_persistence\_flag** equal to 1 specifies that the cubemap projection SEI message persists in output order until one or more of the following conditions are true: + +- A new coded video sequence begins. +- The bitstream ends. +- A picture **picB** in an access unit containing a cubemap projection SEI message is output having **PicOrderCnt( picB )** greater than **PicOrderCnt( picA )**. + +#### D.2.35.3 Sphere rotation SEI message semantics + +The sphere rotation SEI message provides information on rotation angles yaw ( $\alpha$ ), pitch ( $\beta$ ), and roll ( $\gamma$ ) that are used for conversion between the global coordinate axes and the local coordinate axes. + +Relative to an (x, y, z) Cartesian coordinate system, yaw expresses a rotation around the z (vertical, up) axis, pitch rotates around the y (lateral, side-to-side) axis, and roll rotates around the x (back-to-front) axis. Rotations are extrinsic, i.e., around x, y, and z fixed reference axes. The angles increase clockwise when looking from the origin towards the positive end of an axis. + +**sphere\_rotation\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous sphere rotation SEI message in output order. **sphere\_rotation\_cancel\_flag** equal to 0 indicates that sphere rotation information follows. + +**sphere\_rotation\_persistence\_flag** specifies the persistence of the sphere rotation SEI message. + +sphere\_rotation\_persistence\_flag equal to 0 specifies that the sphere rotation SEI message applies to the current decoded picture only. + +Let picA be the current picture. sphere\_rotation\_persistence\_flag equal to 1 specifies that the sphere rotation SEI message persists in output order until one or more of the following conditions are true: + +- A new coded video sequence begins. +- The bitstream ends. +- A picture picB in an access unit containing a sphere rotation SEI message is output having PicOrderCnt( picB ) greater than PicOrderCnt( picA ). + +When an equirectangular projection SEI message with erp\_cancel\_flag equal to 0 or a cubemap projection SEI message with cmp\_cancel\_flag equal to 0 is not present in the coded video sequence that applies to the current picture and precedes the sphere rotation SEI message in decoding order, a sphere rotation SEI message with sphere\_rotation\_cancel\_flag equal to 0 shall not be present in the coded video sequence that applies to the current picture. Decoders shall ignore sphere rotation SEI messages with sphere\_rotation\_cancel\_flag equal to 0 that do not follow, in decoding order, an equirectangular projection SEI message with erp\_cancel\_flag equal to 0 or a cubemap projection SEI message with cmp\_cancel\_flag equal to 0 in the coded video sequence that applies to the current picture. + +**sphere\_rotation\_reserved\_zero\_6bits** shall be equal to 0 in bitstreams conforming to this version of this Specification. Other values for sphere\_rotation\_reserved\_zero\_6bits are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore the value of sphere\_rotation\_reserved\_zero\_6bits. + +**yaw\_rotation** specifies the value of the yaw rotation angle, in units of $2^{-16}$ degrees. The value of yaw\_rotation shall be in the range of $-180 * 2^{16}$ (i.e., -11 796 480) to $180 * 2^{16} - 1$ (i.e., 11 796 479), inclusive. When not present, the value of yaw\_rotation is inferred to be equal to 0. + +**pitch\_rotation** specifies the value of the pitch rotation angle, in units of $2^{-16}$ degrees. The value of pitch\_rotation shall be in the range of $-90 * 2^{16}$ (i.e., -5 898 240) to $90 * 2^{16}$ (i.e., 5 898 240), inclusive. When not present, the value of pitch\_rotation is inferred to be equal to 0. + +**roll\_rotation** specifies the value of the roll rotation angle, in units of $2^{-16}$ degrees. The value of roll\_rotation shall be in the range of $-180 * 2^{16}$ (i.e., -11 796 480) to $180 * 2^{16} - 1$ (i.e., 11 796 479), inclusive. When not present, the value of roll\_rotation is inferred to be equal to 0. + +#### D.2.35.4 Region-wise packing SEI message semantics + +The region-wise packing SEI message provides information to enable remapping of the colour samples of the cropped decoded pictures onto projected pictures as well as information on the location and size of the guard bands, if any. + +**rwp\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous region-wise packing SEI message in output order. rwp\_cancel\_flag equal to 0 indicates that region-wise packing information follows. + +**rwp\_persistence\_flag** specifies the persistence of the region-wise packing SEI message. + +rwp\_persistence\_flag equal to 0 specifies that the region-wise packing SEI message applies to the current decoded picture only. + +Let picA be the current picture. rwp\_persistence\_flag equal to 1 specifies that the region-wise packing SEI message persists in output order until one or more of the following conditions are true: + +- A new coded video sequence begins. +- The bitstream ends. +- A picture picB in an access unit containing a region-wise packing SEI message is output having PicOrderCnt( picB ) greater than PicOrderCnt( picA ). + +When an equirectangular projection SEI message with erp\_cancel\_flag equal to 0 and erp\_padding\_flag equal to 0 or a cubemap projection SEI message with cmp\_cancel\_flag equal to 0 is not present in the coded video sequence that applies to the current picture and precedes the region-wise packing SEI message in decoding order, a region-wise packing SEI message with rwp\_cancel\_flag equal to 0 shall not be present in the coded video sequence that applies to the current picture. Decoders shall ignore region-wise packing SEI messages with rwp\_cancel\_flag equal to 0 that do not follow, in decoding order, an equirectangular projection SEI message with erp\_cancel\_flag equal to 0 or a cubemap projection SEI message with cmp\_cancel\_flag equal to 0 in the coded video sequence that applies to the current picture. + +For the frame packing arrangement scheme indicated by a frame packing arrangement SEI message that applies to the current picture, if a region-wise packing SEI message with rwp\_cancel\_flag equal to 0 is present that applies to the current + +picture, the frame packing arrangement scheme applies to the projected picture, otherwise, the frame packing arrangement scheme applies to the cropped decoded picture. + +If a frame packing arrangement SEI message with frame\_packing\_arrangement\_cancel\_flag equal to 0, frame\_packing\_arrangement\_type equal to 3, 4, or 5, and quincunx\_sampling\_flag equal to 0 is not present that applies to the current picture, the variables StereoFlag, TopBottomFlag, SideBySideFlag, and TempInterleavingFlag are all set equal to 0, the variables HorDiv1 and VerDiv1 are both set equal to 1. Otherwise the following applies: + +- StereoFlag is equal to 1. +- When the frame\_packing\_arrangement\_type is equal to 3, SideBySideFlag is set equal to 1, TopBottomFlag and TempInterleavingFlag are both set equal to 0, HorDiv1 is set equal to 2 and VerDiv1 is set equal to 1. +- When the frame\_packing\_arrangement\_type is equal to 4, TopBottomFlag is set equal to 1, SideBySideFlag and TempInterleavingFlag are both set equal to 0, HorDiv1 is set equal to 1 and VerDiv1 is set equal to 2. +- When the frame\_packing\_arrangement\_type is equal to 5, TempInterleavingFlag is set equal to 1, TopBottomFlag and SideBySideFlag are both set equal to 0, HorDiv1 and VerDiv1 are both set equal to 1. + +**constituent\_picture\_matching\_flag** equal to 1 specifies that the projected region information, packed region information, and guard band region information in this SEI message apply individually to each constituent picture and that the packed picture and the projected picture have the same stereoscopic frame packing format indicated by the frame packing arrangement SEI message. constituent\_picture\_matching\_flag equal to 0 specifies that the projected region information, packed region information, and guard band region information in this SEI message apply to the projected picture. + +When either of the following two conditions is true, the value of constituent\_picture\_matching\_flag shall be equal to 0: + +- StereoFlag is equal to 0. +- StereoFlag is equal to 1 and frame\_packing\_arrangement\_type is equal to 5. + +**rwp\_reserved\_zero\_5bits** shall be equal to 0 in bitstreams conforming to this version of this Specification. Other values for rwp\_reserved\_zero\_5bits[ i ] are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore the value of rwp\_reserved\_zero\_5bits[ i ]. + +**num\_packed\_regions** specifies the number of packed regions when constituent\_picture\_matching\_flag is equal to 0. The value of num\_packed\_regions shall be greater than 0. When constituent\_picture\_matching\_flag is equal to 1, the total number of packed regions is equal to num\_packed\_regions \* 2, and the information in each entry of the loop of num\_packed\_regions entries applies to each constituent picture of the projected picture and the packed picture. + +**proj\_picture\_width** and **proj\_picture\_height** specify the width and height, respectively, of the projected picture, in relative projected picture sample units. + +The values of proj\_picture\_width and proj\_picture\_height shall both be greater than 0. + +**packed\_picture\_width** and **packed\_picture\_height** specify the width and height, respectively, of the packed picture, in relative packed picture sample units. + +The values of packed\_picture\_width and packed\_picture\_height shall both be greater than 0. + +It is a requirement of bitstream conformance that packed\_picture\_width and packed\_picture\_height shall have such values that packed\_picture\_width is an integer multiple of cropPicWidth and packed\_picture\_height is an integer multiple of cropPicHeight, where cropPicWidth and cropPicHeight are the width and height, respectively, of the cropped decoded picture. + +**rwp\_reserved\_zero\_4bits[ i ]** shall be equal to 0 in bitstreams conforming to this version of this Specification. Other values for rwp\_reserved\_zero\_4bits[ i ] are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore the value of rwp\_reserved\_zero\_4bits[ i ]. + +**transform\_type[ i ]** specifies the rotation and mirroring to be applied to the i-th packed region to remap to the i-th projected region. When transform\_type[ i ] specifies both rotation and mirroring, rotation applies before mirroring. The values of transform\_type[ i ] are specified in Table D-11: + +**Table D-11 – transform\_type[ i ] values** + +| Value | Description | +|-------|-----------------------------------------------------------------------| +| 0 | no transform | +| 1 | mirroring horizontally | +| 2 | rotation by 180 degrees (anticlockwise) | +| 3 | rotation by 180 degrees (anticlockwise) before mirroring horizontally | +| 4 | rotation by 90 degrees (anticlockwise) before mirroring horizontally | +| 5 | rotation by 90 degrees (anticlockwise) | +| 6 | rotation by 270 degrees (anticlockwise) before mirroring horizontally | +| 7 | rotation by 270 degrees (anticlockwise) | + +**guard\_band\_flag[ i ]** equal to 0 specifies that the i-th packed region does not have a guard band. guard\_band\_flag[ i ] equal to 1 specifies that the i-th packed region has a guard band. + +**proj\_region\_width[ i ]**, **proj\_region\_height[ i ]**, **proj\_region\_top[ i ]** and **proj\_region\_left[ i ]** specify the width, height, top sample row, and the left-most sample column, respectively, of the i-th projected region, either within the projected picture (when constituent\_picture\_matching\_flag is equal to 0) or within the constituent picture of the projected picture (when constituent\_picture\_matching\_flag is equal to 1). + +proj\_region\_width[ i ], proj\_region\_height[ i ], proj\_region\_top[ i ], and proj\_region\_left[ i ] are indicated in relative projected picture sample units. + +NOTE 1 – Two projected regions may partially or entirely overlap with each other. + +**packed\_region\_width[ i ]**, **packed\_region\_height[ i ]**, **packed\_region\_top[ i ]**, and **packed\_region\_left[ i ]** specify the width, height, the top luma sample row, and the left-most luma sample column, respectively, of the packed region, either within the region-wise packed picture (when constituent\_picture\_matching\_flag is equal to 0) or within each constituent picture of the region-wise packed picture (when constituent\_picture\_matching\_flag is equal to 1). + +packed\_region\_width[ i ], packed\_region\_height[ i ], packed\_region\_top[ i ], and packed\_region\_left[ i ] are indicated in relative region-wise packed picture sample units. packed\_region\_width[ i ], packed\_region\_height[ i ], packed\_region\_top[ i ], and packed\_region\_left[ i ] shall represent integer horizontal and vertical coordinates of luma sample units within the cropped decoded pictures. + +NOTE 2 – Two packed regions may partially or entirely overlap with each other. + +**left\_gb\_width[ i ]** specifies the width of the guard band on the left side of the i-th packed region in relative region-wise packed picture sample units. When the decoded picture has 4:2:0 or 4:2:2 chroma format, left\_gb\_width[ i ] shall correspond to an even number of luma samples within the cropped decoded picture. + +**right\_gb\_width[ i ]** specifies the width of the guard band on the right side of the i-th packed region in relative region-wise packed picture sample units. When the decoded picture has 4:2:0 or 4:2:2 chroma format, right\_gb\_width[ i ] shall correspond to an even number of luma samples within the cropped decoded picture. + +**top\_gb\_height[ i ]** specifies the height of the guard band above the i-th packed region in relative region-wise packed picture sample units. When the decoded picture has 4:2:0 chroma format, top\_gb\_height[ i ] shall correspond to an even number of luma samples within the cropped decoded picture. + +**bottom\_gb\_height[ i ]** specifies the height of the guard band below the i-th packed region in relative region-wise packed picture sample units. When the decoded picture has 4:2:0 chroma format, bottom\_gb\_height[ i ] shall correspond to an even number of luma samples within the cropped decoded picture. + +When guard\_band\_flag[ i ] is equal to 1, left\_gb\_width[ i ], right\_gb\_width[ i ], top\_gb\_height[ i ], or bottom\_gb\_height[ i ] shall be greater than 0. + +The i-th packed region as specified by this SEI message shall not overlap with any other packed region specified by the same SEI message or any guard band specified by the same SEI message. + +The guard bands associated with the i-th packed region, if any, as specified by this SEI message shall not overlap with any packed region specified by the same SEI message or any other guard bands specified by the same SEI message. + +**gb\_not\_used\_for\_pred\_flag[ i ]** equal to 0 specifies that the guard bands may or may not be used in the inter prediction process. **gb\_not\_used\_for\_pred\_flag[ i ]** equal to 1 specifies that the sample values of the guard bands are not used in the inter prediction process. + +NOTE 3 – When **gb\_not\_used\_for\_pred\_flag[ i ]** is equal to 1, the sample values within guard bands in cropped decoded pictures can be rewritten even if the cropped decoded pictures were used as references for inter prediction of subsequent pictures to be decoded. For example, the content of a packed region can be seamlessly expanded to its guard band with decoded and re-projected samples of another packed region. + +**gb\_type[ i ][ j ]** specifies the type of the guard bands for the i-th packed region as follows, with j equal to 0, 1, 2, or 3 indicating that the semantics below apply to the left, right, top, or bottom edge, respectively, of the packed region: + +- **gb\_type[ i ][ j ]** equal to 0 specifies that the content of the guard bands in relation to the content of the packed regions is unspecified. When **gb\_not\_used\_for\_pred\_flag[ i ]** is equal to 0, **gb\_type[ i ][ j ]** shall not be equal to 0. +- **gb\_type[ i ][ j ]** equal to 1 specifies that the content of the guard bands suffices for interpolation of sample values at sub-pel sample fractional locations within the packed region and less than sample outside of the boundary of the packed region. + +NOTE 4 – **gb\_type[ i ][ j ]** equal to 1 can be used when the boundary samples of a packed region have been copied horizontally or vertically to the guard band. + +- **gb\_type[ i ][ j ]** equal to 2 specifies that the content of the guard bands represents actual picture content that is spherically adjacent to the content in the packed region and is on the surface of the packed region at quality that gradually changes from the picture quality of the packed region to that of the spherically adjacent packed region. +- **gb\_type[ i ][ j ]** equal to 3 specifies that the content of the guard bands represents actual picture content that is spherically adjacent to the content in the packed region and is on the surface of the packed region at the picture quality of the packed region. +- **gb\_type[ i ][ j ]** values greater than 3 are reserved. Decoders shall ignore the value of **gb\_type[ i ][ j ]** when the value is greater than 3. + +**rwp\_gb\_reserved\_zero\_3bits[ i ]** shall be equal to 0 in bitstreams conforming to this version of this Specification. Other values for **rwp\_gb\_reserved\_zero\_3bits[ i ]** are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore the value of **rwp\_gb\_reserved\_zero\_3bits[ i ]**. + +The variables **NumPackedRegions**, **PackedRegionLeft[ n ]**, **PackedRegionTop[ n ]**, **PackedRegionWidth[ n ]**, **PackedRegionHeight[ n ]**, **ProjRegionLeft[ n ]**, **ProjRegionTop[ n ]**, **ProjRegionWidth[ n ]**, **ProjRegionHeight[ n ]**, and **TrasnformType[ n ]** are derived as follows: + +- For n in the range of 0 to **num\_packed\_regions** – 1, inclusive, the following applies: + - **PackedRegionLeft[ n ]** is set equal to **packed\_region\_left[ n ]**. + - **PackedRegionTop[ n ]** is set equal to **packed\_region\_top[ n ]**. + - **PackedRegionWidth[ n ]** is set equal to **packed\_region\_width[ n ]**. + - **PackedRegionHeight[ n ]** is set equal to **packed\_region\_height[ n ]**. + - **ProjRegionLeft[ n ]** is set equal to **proj\_region\_left[ n ]**. + - **ProjRegionTop[ n ]** is set equal to **proj\_region\_top[ n ]**. + - **ProjRegionWidth[ n ]** is set equal to **proj\_region\_width[ n ]**. + - **ProjRegionHeight[ n ]** is set equal to **proj\_region\_height[ n ]**. + - **TransformType[ n ]** is set equal to **transform\_type[ n ]**. +- If **constituent\_picture\_matching\_flag** is equal to 0, the following applies: + - **NumPackedRegions** is set equal to **num\_packed\_regions**. +- Otherwise (**constituent\_picture\_matching\_flag** is equal to 1), the following applies: + - **NumPackedRegions** is set equal to $2 * \text{num\_packed\_regions}$ . + - When **TopBottomFlag** is equal to 1, the following applies: + - **projLeftOffset** and **packedLeftOffset** are both set equal to 0. + +- projTopOffset is set equal to $\text{proj\_picture\_height} / 2$ and packedTopOffset is set equal to $\text{packed\_picture\_height} / 2$ . +- When SideBySideFlag is equal to 1, the following applies: + - projLeftOffset is set equal to $\text{proj\_picture\_width} / 2$ and packedLeftOffset is set equal to $\text{packed\_picture\_width} / 2$ . + - projTopOffset and packedTopOffset are both set equal to 0. +- For n in the range of $\text{NumPackedRegions} / 2$ to $\text{NumPackedRegions} - 1$ , inclusive, the following applies: + - nIdx is set equal to $n - \text{NumPackedRegions} / 2$ . + - PackedRegionLeft[ n ] is set equal to $\text{packed\_region\_left}[ \text{nIdx} ] + \text{packedLeftOffset}$ . + - PackedRegionTop[ n ] is set equal to $\text{packed\_region\_top}[ \text{nIdx} ] + \text{packedTopOffset}$ . + - PackedRegionWidth[ n ] is set equal to $\text{packed\_region\_width}[ \text{nIdx} ]$ . + - PackedRegionHeight[ n ] is set equal to $\text{packed\_region\_height}[ \text{nIdx} ]$ . + - ProjRegionLeft[ n ] is set equal to $\text{proj\_region\_left}[ \text{nIdx} ] + \text{projLeftOffset}$ . + - ProjRegionTop[ n ] is set equal to $\text{proj\_region\_top}[ \text{nIdx} ] + \text{projTopOffset}$ . + - ProjRegionWidth[ n ] is set equal to $\text{proj\_region\_width}[ \text{nIdx} ]$ . + - ProjRegionHeight[ n ] is set equal to $\text{proj\_region\_height}[ \text{nIdx} ]$ . + - TransformType[ n ] is set equal to $\text{transform\_type}[ \text{nIdx} ]$ . + +For each value of n in the range of 0 to $\text{NumPackedRegions} - 1$ , inclusive, the values of ProjRegionWidth[ n ], ProjRegionHeight[ n ], ProjRegionTop[ n ], and ProjRegionLeft[ n ] are constrained as follows: + +- ProjRegionWidth[ n ] shall be in the range of 1 to $\text{proj\_picture\_width}$ , inclusive. +- ProjRegionHeight[ n ] shall be in the range of 1 to $\text{proj\_picture\_height}$ , inclusive. +- ProjRegionLeft[ n ] shall be in the range of 0 to $\text{proj\_picture\_width} - 1$ , inclusive. +- ProjRegionTop[ n ] shall be in the range of 0 to $\text{proj\_picture\_height} - 1$ , inclusive. +- If ProjRegionTop[ n ] is less than $\text{proj\_picture\_height} / \text{VerDiv1}$ , the sum of ProjRegionTop[ n ] and ProjRegionHeight[ n ] shall be less than or equal to $\text{proj\_picture\_height} / \text{VerDiv1}$ . Otherwise, the sum of ProjRegionTop[ n ] and ProjRegionHeight[ n ] shall be less than or equal to $\text{proj\_picture\_height} / \text{VerDiv1} * 2$ . + +For each value of n in the range of 0 to $\text{NumPackedRegions} - 1$ , inclusive, the values of PackedRegionWidth[ n ], PackedRegionHeight[ n ], PackedRegionTop[ n ], and PackedRegionLeft[ n ] are constrained as follows: + +- PackedRegionWidth[ n ] shall be in the range of 1 to $\text{packed\_picture\_width}$ , inclusive. +- ProjRegionHeight[ n ] shall be in the range of 1 to $\text{packed\_picture\_height}$ , inclusive. +- PackedRegionLeft[ n ] shall be in the range of 0 to $\text{packed\_picture\_width} - 1$ , inclusive. +- PackedRegionTop[ n ] shall be in the range of 0 to $\text{packed\_picture\_height} - 1$ , inclusive. +- If PackedRegionLeft[ n ] is less than $\text{packed\_picture\_width} / \text{HorDiv1}$ , the sum of PackedRegionLeft[ n ] and PackedRegionWidth[ n ] shall be less than or equal to $\text{packed\_picture\_width} / \text{HorDiv1}$ . Otherwise, the sum of PackedRegionLeft[ n ] and PackedRegionWidth[ n ] shall be less than or equal to $\text{packed\_picture\_width} / \text{HorDiv1} * 2$ . +- If PackedRegionTop[ n ] is less than $\text{packed\_picture\_height} / \text{VerDiv1}$ , the sum of PackedRegionTop[ n ] and PackedRegionHeight[ n ] shall be less than or equal to $\text{packed\_picture\_height} / \text{VerDiv1}$ . Otherwise, the sum of PackedRegionTop[ n ] and PackedRegionHeight[ n ] shall be less than or equal to $\text{packed\_picture\_height} / \text{VerDiv1} * 2$ . +- When chroma\_format\_idc is equal to 1 (4:2:0 chroma format) or 2 (4:2:2 chroma format), PackedRegionLeft[ n ] shall correspond to an even horizontal coordinate value of luma sample units, and PackedRegionWidth[ n ] shall correspond to an even number of luma samples, both within the decoded picture. + +- When `chroma_format_idc` is equal to 1 (4:2:0 chroma format), `PackedRegionTop[ n ]` shall correspond to an even vertical coordinate value of luma sample units, and `ProjRegionHeight[ n ]` shall correspond to an even number of luma samples, both within the decoded picture. + +#### D.2.35.5 Omnidirectional viewport SEI message semantics + +The omnidirectional viewport SEI message specifies the coordinates of one or more regions of spherical-coordinate geometry, bounded by four great circles, corresponding to viewports recommended for display when the user does not have control of the viewing orientation or has released control of the viewing orientation. + +When an effectively applicable frame packing arrangement SEI message, as specified in clause D.2.35.1 or D.2.35.2, that applies to the picture is present, the information indicated by the omnidirectional viewport SEI message applies to both views. + +**omni\_viewport\_id** contains an identifying number that may be used to identify the purpose of the one or more recommended viewport regions. + +`omni_viewport_id` equal to 0 indicates that the recommended viewports are per "director's cut", i.e., a viewport suggested according to the creative intent of the content author or content provider. `omni_viewport_id` equal to 1 indicates that the recommended viewports are selected based on measurements of viewing statistics. + +Values of `omni_viewport_id` from 2 to 511, inclusive, may be used as determined by the application. Values of `omni_viewport_id` from 512 to 1023 are reserved for future use by ITU-T | ISO/IEC. Decoders encountering a value of `omni_viewport_id` in the range of 512 to 1023, inclusive, shall ignore it. + +**omni\_viewport\_cancel\_flag** equal to 1 indicates that the SEI message cancels the persistence of any previous omnidirectional viewport SEI message in output order. `omni_viewport_cancel_flag` equal to 0 indicates that omnidirectional viewport information follows. + +**omni\_viewport\_persistence\_flag** specifies the persistence of the omnidirectional viewport SEI message. + +`omni_viewport_persistence_flag` equal to 0 specifies that the omnidirectional viewport SEI message applies to the current decoded picture only. + +Let `picA` be the current picture. `omni_viewport_persistence_flag` equal to 1 specifies that the omnidirectional viewport SEI message persists in output order until one or more of the following conditions are true: + +- A new coded video sequence begins. +- The bitstream ends. +- A picture `picB` in an access unit containing an omnidirectional viewport SEI message is output having `PicOrderCnt( picB )` greater than `PicOrderCnt( picA )`. + +When an equirectangular projection SEI message with `erp_cancel_flag` equal to 0 or a cubemap projection SEI message with `cmp_cancel_flag` equal to 0 is not present in the coded video sequence that applies to the current picture and precedes the omnidirectional viewport SEI message in decoding order, an omnidirectional viewport SEI message with `omni_viewport_cancel_flag` equal to 0 shall not be present in the coded video sequence that applies to the current picture. Decoders shall ignore omnidirectional viewport SEI messages with `omni_viewport_cancel_flag` equal to 0 that do not follow, in decoding order, an equirectangular projection SEI message with `erp_cancel_flag` equal to 0 or a cubemap projection SEI message with `cmp_cancel_flag` equal to 0 in the coded video sequence that applies to the current picture. + +**omni\_viewport\_cnt\_minus1** plus 1 specifies the number of recommended viewport regions that are indicated by the SEI message. + +When `omni_viewport_cnt_minus1` is greater than 0 and there is no information provided by external means not specified in this Specification on which recommended viewport is suggested to be displayed, the following applies: + +- When `omni_viewport_id` is equal to 0 or 1, the 0-th recommended viewport is suggested to be displayed when the user does not have control of the viewing orientation or has released control of the viewing orientation. +- When `omni_viewport_id` is equal to 0, between any two recommended viewports per director's cut, the `i`-th recommended viewport has higher priority than the `j`-th recommended viewport for any values of `i` and `j` when `i` is less than `j`. The 0-th recommended viewport per director's cut has the highest priority. +- When `omni_viewport_id` is equal to 1, between any two recommended viewports, the `i`-th recommended viewport has higher popularity, among some selection of candidate viewports, than the `j`-th recommended viewport for any values of `i` and `j` when `i` is less than `j`. The 0-th most-viewed recommended viewport has the highest popularity. The selection of the candidate viewports is outside the scope of this Specification. + +**omni\_viewport\_azimuth\_centre[i]** and **omni\_viewport\_elevation\_centre[i]** indicate the centre of the i-th recommended viewport region, in units of $2^{-16}$ degrees relative to the global coordinate axes. The value of **omni\_viewport\_azimuth\_centre[i]** shall be in the range of $-180 * 2^{16}$ (i.e., -11 796 480) to $180 * 2^{16} - 1$ (i.e., 11 796 479), inclusive. The value of **omni\_viewport\_elevation\_centre[i]** shall be in the range of $-90 * 2^{16}$ (i.e., -5 898 240) to $90 * 2^{16}$ (i.e., 5 898 240), inclusive. + +**omni\_viewport\_tilt\_centre[i]** indicates the tilt angle of the i-th recommended viewport region, in units of $2^{-16}$ degrees. The value of **omni\_viewport\_tilt\_centre[i]** shall be in the range of $-180 * 2^{16}$ (i.e., -11 796 480) to $2^{16} - 1$ (i.e., 11 796 479), inclusive. + +**omni\_viewport\_hor\_range[i]** indicates the azimuth range of the i-th recommended viewport region, in units of $2^{-16}$ degrees. The value of **omni\_viewport\_hor\_range[i]** shall be in the range of 1 to $360 * 2^{16}$ (i.e., 23 592 960), inclusive. + +**omni\_viewport\_ver\_range[i]** indicates the elevation range of the i-th recommended viewport region, in units of $2^{-16}$ degrees. The value of **omni\_viewport\_ver\_range[i]** shall be in the range of 1 to $180 * 2^{16}$ (i.e., 11 796 480), inclusive. + +## D.2.35.6 Sample location remapping process + +### D.2.35.6.1 General + +To remap colour sample locations of a region-wise packed picture to a unit sphere, the following ordered steps are applied: + +- A region-wise packed picture is obtained as the cropped decoded picture by decoding a coded picture. For purposes of interpretation of chroma samples, the input to the indicated remapping process is the set of decoded sample values after applying an (unspecified) upsampling conversion process to the 4:4:4 colour sampling format as necessary when **chroma\_format\_idc** is equal to 1 (4:2:0 chroma format) or 2 (4:2:2 chroma format). This (unspecified) upsampling process should account for the relative positioning relationship between the luma and chroma samples as indicated by **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field**, when present. +- If region-wise packing is indicated, the sample locations of the region-wise packed picture are converted to sample locations of the respective projected picture as specified in clause D.2.35.6.4. Otherwise, the projected picture is identical to the region-wise packed picture. +- If frame packing is indicated, the sample locations of the projected picture are converted to sample locations of the respective constituent picture of the projected picture, as specified in clause D.2.35.6.6. Otherwise, the constituent picture of the projected picture is identical to the projected picture. +- The sample locations of a constituent picture of the projected picture are converted to sphere coordinates relative to the local coordinate axes, as specified in clause D.2.35.6.2. +- If rotation is indicated, the sphere coordinates relative to the local coordinate axes are converted to sphere coordinates relative to the global coordinate axes, as specified in clause D.2.35.6.3. Otherwise, the global coordinate axes are identical to the local coordinate axes. + +The overall process for mapping of luma sample locations within a region-wise packed picture to sphere coordinates relative to the global coordinate axes is normatively specified in clause D.2.35.6.5. + +For each region-wise packed picture corresponding to a decoded picture, the following applies: + +- When an equirectangular projection SEI message with **erp\_cancel\_flag** equal to 0 that applies to the picture is present, **ErpFlag** is set equal to 1, and **CmpFlag** is set equal to 0. +- When a cubemap projection SEI message with **cmp\_cancel\_flag** equal to 0 that applies to the picture is present, **CmpFlag** is set equal to 1, and **ErpFlag** is set equal to 0. +- If a sphere rotation SEI message with **sphere\_rotation\_cancel\_flag** equal to 0 that applies to the picture is present, **RotationFlag** is set equal to 1, and **RotationYaw**, **RotationPitch**, and **RotationRoll** are set equal to $\text{yaw\_rotation} \div 2^{16}$ , $\text{pitch\_rotation} \div 2^{16}$ , and $\text{roll\_rotation} \div 2^{16}$ , respectively. +- Otherwise, **RotationFlag** is set equal to 0. +- If a frame packing arrangement SEI message with **frame\_packing\_arrangement\_cancel\_flag** equal to 0 that applies to the picture is not present, **StereoFlag**, **TopBottomFlag**, and **SideBySideFlag** are all set equal to 0, **HorDiv1** is set equal to 1, and **VerDiv1** is set equal to 1. +- Otherwise, the following applies: + - **StereoFlag** is set equal to 1. + +- If the value of `frame_packing_arrangement_type` of the frame packing arrangement SEI message is equal to 3, `TopBottomFlag` is set equal to 0, `SideBySideFlag` is set equal to 1, `HorDiv1` is set equal to 2 and `VerDiv1` is set equal to 1. +- Otherwise, if the value of `frame_packing_arrangement_type` of the frame packing arrangement SEI message is equal to 4, `TopBottomFlag` is set equal to 1, `SideBySideFlag` is set equal to 0, `HorDiv1` is set equal to 1, and `VerDiv1` is set equal to 2. +- Otherwise, `TopBottomFlag` is set equal to 0, `SideBySideFlag` is set equal to 0, `HorDiv1` is set equal to 1, and `VerDiv1` is set equal to 1. +- If a region-wise packing SEI message with `rwp_cancel_flag` equal to 0 that applies to the picture is not present, `RegionWisePackingFlag` is set equal to 0, and `ConstituentPicWidth` and `ConstituentPicHeight` are set to be equal to `cropPicWidth / HorDiv1` and `cropPicHeight / VerDiv1`, respectively, where `cropPicWidth` and `cropPicHeight` are the width and height, respectively, of the cropped decoded picture. +- Otherwise, `RegionWisePackingFlag` is set equal to 1, and `ConstituentPicWidth` and `ConstituentPicHeight` are set equal to `proj_picture_width / HorDiv1` and `proj_picture_height / VerDiv1`, respectively. + +#### D.2.35.6.2 Projection for a sample location + +Inputs to this clause are: + +- `pictureWidth` and `pictureHeight`, which are the width and height, respectively, of a monoscopic projected luma picture, in relative projected picture sample units, and +- the centre point of a sample location (`hPos`, `vPos`) along the horizontal and vertical axes, respectively, in relative projected picture sample units, where `hPos` and `vPos` may have non-integer real values. + +Outputs of this clause are: + +- sphere coordinates ( $\phi$ , $\theta$ ) for the sample location in degrees relative to the coordinate axes specified in clause D.2.35.6.1. + +The projection for a sample location is derived as follows: + +- If `ErpFlag` is equal to 1, the following applies: + - If `RegionWisePackingFlag` is equal to 0 and `erp_padding_flag` is equal to 1, the following applies: + +$$\begin{aligned} hPos' &= hPos - left\_gb\_erp\_width \\ tmpPicWidth &= pictureWidth - left\_gb\_erp\_width - right\_gb\_erp\_width \end{aligned} \quad (D-45)$$ + +- Otherwise, the following applies: + +$$\begin{aligned} hPos' &= hPos \\ tmpPicWidth &= pictureWidth \end{aligned} \quad (D-46)$$ + +- The following applies: + +$$\begin{aligned} \phi &= 180 - hPos' * ( 360 \div tmpPicWidth ) \\ \theta &= 90 - vPos * ( 180 \div pictureHeight ) \end{aligned} \quad (D-47)$$ + +- Otherwise (`CmpFlag` is equal to 1), it is a requirement of bitstream conformance that `pictureWidth` shall be a multiple of 3 and `pictureHeight` shall be a multiple of 2, and that `pictureWidth / 3` shall be equal to `pictureHeight / 2`, and the following applies: + +``` + +lw = pictureWidth / 3 +lh = pictureHeight / 2 +w = Floor( hPos ÷ lw ) +h = Floor( vPos ÷ lh ) +tmpHorVal = hPos - w * lw +tmpVerVal = vPos - h * lh +hPos' = -( 2 * tmpHorVal ÷ lw ) + 1 +vPos' = -( 2 * tmpVerVal ÷ lh ) + 1 +if( w == 1 && h == 0 ) { /* positive x front face */ + x = 1.0 + y = hPos' + z = vPos' +} else if( w == 1 && h == 1 ) { /* negative x back face */ + x = -1.0 +} + +``` + +``` + + y = -vPos' + z = -hPos' + } else if( w == 2 && h == 1 ) { /* positive z top face */ + x = -hPos' + y = -vPos' + z = 1.0 + } else if( w == 0 && h == 1 ) { /* negative z bottom face */ + x = hPos' + y = -vPos' + z = -1.0 + } else if( w == 0 && h == 0 ) { /* positive y left face */ + x = -hPos' + y = 1.0 + z = vPos' + } else { /* ( w == 2 && h == 0 ), negative y right face */ + x = hPos' + y = -1.0 + z = vPos' + } +} + $\phi = \text{Atan2}( y, x ) * 180 \div \pi$ + $\theta = \text{Asin}( z \div \text{Sqrt}( x^2 + y^2 + z^2 ) ) * 180 \div \pi$ + +``` + +(D-48) + +### D.2.35.6.3 Conversion from the local coordinate axes to the global coordinate axes + +Inputs to this clause are: + +- rotation\_yaw ( $\alpha_d$ ), rotation\_pitch ( $\beta_d$ ), rotation\_roll ( $\gamma_d$ ), all in units of degrees, and +- sphere coordinates ( $\phi_d, \theta_d$ ) relative to the local coordinate axes. + +Outputs of this clause are: + +- sphere coordinates ( $\phi', \theta'$ ) relative to the global coordinate axes. + +The outputs are derived as follows: + +``` + + $\phi = \phi_d * \pi \div 180$ + $\theta = \theta_d * \pi \div 180$ + $\alpha = \alpha_d * \pi \div 180$ + $\beta = \beta_d * \pi \div 180$ + $\gamma = \gamma_d * \pi \div 180$ + $x_1 = \text{Cos}( \phi ) * \text{Cos}( \theta )$ + $y_1 = \text{Sin}( \phi ) * \text{Cos}( \theta )$ + $z_1 = \text{Sin}( \theta )$ + $x_2 = \text{Cos}( \beta ) * \text{Cos}( \gamma ) * x_1 - \text{Cos}( \beta ) * \text{Sin}( \gamma ) * y_1 + \text{Sin}( \beta ) * z_1$ + $y_2 = ( \text{Cos}( \alpha ) * \text{Sin}( \gamma ) + \text{Sin}( \alpha ) * \text{Sin}( \beta ) * \text{Cos}( \gamma ) ) * x_1 +$ + $( \text{Cos}( \alpha ) * \text{Cos}( \gamma ) - \text{Sin}( \alpha ) * \text{Sin}( \beta ) * \text{Sin}( \gamma ) ) * y_1 -$ + $\text{Sin}( \alpha ) * \text{Cos}( \beta ) * z_1$ + $z_2 = ( \text{Sin}( \alpha ) * \text{Sin}( \gamma ) - \text{Cos}( \alpha ) * \text{Sin}( \beta ) * \text{Cos}( \gamma ) ) * x_1 +$ + $( \text{Sin}( \alpha ) * \text{Cos}( \gamma ) + \text{Cos}( \alpha ) * \text{Sin}( \beta ) * \text{Sin}( \gamma ) ) * y_1 +$ + $\text{Cos}( \alpha ) * \text{Cos}( \beta ) * z_1$ + $\phi' = \text{Atan2}( y_2, x_2 ) * 180 \div \pi$ + $\theta' = \text{Asin}( z_2 ) * 180 \div \pi$ + +``` + +(D-49) + +### D.2.35.6.4 Conversion of sample locations for rectangular region-wise packing + +Inputs to this clause are: + +- sample location ( $x, y$ ) within the packed region, where $x$ and $y$ are in relative packed picture sample units, while the sample location is at an integer sample location within the packed picture, +- the width and the height ( $\text{projRegWidth}, \text{projRegHeight}$ ) of the projected region, in relative projected picture sample units, +- the width and the height ( $\text{packedRegWidth}, \text{packedRegHeight}$ ) of the packed region, in relative packed picture sample units, and +- transform type ( $\text{transformType}$ ). + +Outputs of this clause are: + +- the centre point of the sample location (hPos, vPos) within the projected region in relative projected picture sample units, where hPos and vPos may have non-integer real values. + +The outputs are derived as follows: + +``` + +if( transformType == 0 || transformType == 1 || transformType == 2 || transformType == 3 ) { + horRatio = projRegWidth ÷ packedRegWidth + verRatio = projRegHeight ÷ packedRegHeight +} else if( transformType == 4 || transformType == 5 || transformType == 6 || + transformType == 7 ) { + horRatio = projRegWidth ÷ packedRegHeight + verRatio = projRegHeight ÷ packedRegWidth +} +if( transformType == 0 ) { + hPos = horRatio * ( x + 0.5 ) + vPos = verRatio * ( y + 0.5 ) +} else if( transformType == 1 ) { + hPos = horRatio * ( packedRegWidth - x - 0.5 ) + vPos = verRatio * ( y + 0.5 ) +} else if( transformType == 2 ) { + hPos = horRatio * ( packedRegWidth - x - 0.5 ) + vPos = verRatio * ( packedRegHeight - y - 0.5 ) +} else if( transformType == 3 ) { + hPos = horRatio * ( x + 0.5 ) + vPos = verRatio * ( packedRegHeight - y - 0.5 ) +} else if( transformType == 4 ) { + hPos = horRatio * ( y + 0.5 ) + vPos = verRatio * ( x + 0.5 ) +} else if( transformType == 5 ) { + hPos = horRatio * ( y + 0.5 ) + vPos = verRatio * ( packedRegWidth - x - 0.5 ) +} else if( transformType == 6 ) { + hPos = horRatio * ( packedRegHeight - y - 0.5 ) + vPos = verRatio * ( packedRegWidth - x - 0.5 ) +} else if( transformType == 7 ) { + hPos = horRatio * ( packedRegHeight - y - 0.5 ) + vPos = verRatio * ( x + 0.5 ) +} +} +(D-50) + +``` + +#### D.2.35.6.5 Mapping of luma sample locations within a cropped decoded picture to sphere coordinates relative to the global coordinate axes + +This clause specifies the mapping of luma sample locations within a cropped decoded picture to sphere coordinates relative to the global coordinate axes. + +If RegionWisePackingFlag is equal to 1, the following applies for each packed region n in the range of 0 to NumPackedRegions – 1, inclusive: + +- For each sample location (xPackedPicture, yPackedPicture) belonging to the n-th packed region, the following applies: + - The corresponding sample location (xProjPicture, yProjPicture) of the projected picture is derived as follows: + - x is set equal to xPackedPicture – PackedRegionLeft[ n ]. + - y is set equal to yPackedPicture – PackedRegionTop[ n ]. + - Clause D.2.35.6.4 is invoked with x, y, PackedRegionWidth[ n ], PackedRegionHeight[ n ], ProjRegionWidth[ n ], ProjRegionHeight[ n ], and TransformType[ n ] as inputs, and the output is assigned to sample location (hPos, vPos). + - xProjPicture is set equal to ProjRegionLeft[ n ] + hPos. + - When StereoFlag is equal to 0 or TopBottomFlag is equal to 1, and when xProjPicture is greater than or equal to proj\_picture\_width, xProjPicture is set equal to xProjPicture – proj\_picture\_width. + - When SideBySideFlag is equal to 1, the following applies: + +- When ProjRegionLeft[ n ] is less than proj\_picture\_width / 2 and xProjPicture is greater than or equal to proj\_picture\_width / 2, xProjPicture is set equal to xProjPicture – proj\_picture\_width / 2. +- When ProjRegionLeft[ n ] is greater than or equal to proj\_picture\_width / 2 and xProjPicture is greater than or equal to proj\_picture\_width, xProjPicture is set equal to xProjPicture – proj\_picture\_width / 2. +- yProjPicture is set equal to ProjRegionTop[ n ] + vPos. +- Clause D.2.35.6.6 is invoked with xProjPicture, yProjPicture, ConstituentPicWidth, and ConstituentPicHeight as inputs, and the outputs indicating the sphere coordinates and the constituent picture index (for frame-packed stereoscopic video) for the luma sample location (xPackedPicture, yPackedPicture) belonging to the n-th packed region in the decoded picture. + +Otherwise (RegionWisePackingFlag is equal 0), the following applies for each sample location (x, y) that is not an equirectangular projection padded sample within the cropped decoded picture, where a sample location (x, y) is an equirectangular projection padded sample when and only when ErpFlag is equal to 1, x is in the range of 0 to left\_gb\_erp\_width – 1, inclusive, or ConstituentPicWidth – right\_gb\_erp\_width to ConstituentPicWidth – 1, inclusive, and y is in the range of 0 to ConstituentPicHeight – 1, inclusive: + +- xProjPicture is set equal to x + 0.5. +- yProjPicture is set equal to y + 0.5. +- If ErpFlag is equal to 0, projPicWidth is set equal to ConstituentPicWidth. Otherwise (ErpFlag is equal to 1), projPicWidth is set equal to ConstituentPicWidth – ( left\_gb\_erp\_width + right\_gb\_erp\_width ). +- Clause D.2.35.6.6 is invoked with xProjPicture, yProjPicture, projPicWidth, and ConstituentPicHeight as inputs, and the outputs indicating the sphere coordinates and the constituent picture index (for frame-packed stereoscopic video) for the sample location (x, y) within the region-wise packed picture. + +#### **D.2.35.6.6 Conversion from a sample location in a projected picture to sphere coordinates relative to the global coordinate axes** + +Inputs to this clause are: + +- the centre point of a sample location (xProjPicture, yProjPicture) within a projected picture, where xProjPicture and yProjPicture are in relative projected picture sample units and may have non-integer real values, and +- pictureWidth and pictureHeight, which are the width and height, respectively, of a monoscopic projected luma picture, in relative projected picture sample units. + +Outputs of this clause are: + +- sphere coordinates (azimuthGlobal, elevationGlobal), in units of degrees relative to the global coordinate axes, and +- when StereoFlag is equal to 1, the index of the constituent picture (constituentPicture) equal to 0 or 1. + +The outputs are derived with the following ordered steps: + +- If xProjPicture is greater than or equal to pictureWidth or yProjPicture is greater than or equal to pictureHeight, the following applies: + - constituentPicture is set equal to 1. + - If xProjPicture is greater than or equal to pictureWidth, xProjPicture is set to xProjPicture – pictureWidth. + - If yProjPicture is greater than or equal to pictureHeight, yProjPicture is set to yProjPicture – pictureHeight. +- Otherwise, constituentPicture is set equal to 0. +- Clause D.2.35.6.2 is invoked with pictureWidth, pictureHeight, xProjPicture, and yProjPicture as inputs, and the output is assigned to azimuthLocal, elevationLocal. +- If RotationFlag is equal to 1, clause D.2.35.6.3 is invoked with azimuthLocal, elevationLocal, RotationYaw, RotationPitch, and RotationRoll as inputs, and the output is assigned to azimuthGlobal and elevationGlobal. +- Otherwise, azimuthGlobal is set equal to azimuthLocal and elevationGlobal is set equal to elevationLocal. + +#### **D.2.36 SEI manifest SEI message semantics** + +The SEI manifest SEI message conveys information on SEI messages that are indicated as expected (i.e., likely) to be present or not present. Such information may include: + +- The indication that certain types of SEI messages are expected (i.e., likely) to be present (although not guaranteed to be present) in the coded video sequence. +- For each type of SEI message that is indicated as expected (i.e., likely) to be present in the coded video sequence, the degree of expressed necessity of interpretation of the SEI messages of this type. + +The degree of necessity of interpretation of an SEI message type may be indicated as "necessary", "unnecessary", or "undetermined". + +An SEI message is indicated by the encoder (i.e., the content producer) as being "necessary" when the information conveyed by the SEI message is considered as necessary for interpretation by the decoder or receiving system in order to properly process the content and enable an adequate user experience; it does not mean that the bitstream is required to contain the SEI message in order to be a conforming bitstream. It is at the discretion of the encoder to determine which SEI messages are to be considered as necessary in a particular coded video sequence. However, it is suggested that some SEI messages, such as the frame packing arrangement, segmented rectangular frame packing arrangement, and omnidirectional projection indication SEI messages, should typically be considered as necessary. + +- The indication that certain types of SEI messages are expected (i.e., likely) not to be present (although not guaranteed not to be present) in the coded video sequence. + +NOTE – An example of such a usage of an SEI manifest SEI message is to express the expectation that there are no frame packing arrangement SEI messages, segmented rectangular frame packing arrangement SEI messages, display orientation SEI messages, or omnidirectional projection indication SEI messages in the coded video sequence, and therefore that the rendering of the decoded video pictures for display purposes would not need any of the additional post-processing that is commonly associated with the interpretation of these SEI messages. + +The content of an SEI manifest SEI message may, for example, be used by transport-layer or systems-layer processing elements to determine whether the coded video sequence is suitable for delivery to a receiving and decoding system, based on whether the receiving system can properly process the coded video sequence to enable an adequate user experience or whether the coded video sequence satisfies the application needs. + +When an SEI manifest SEI message is present in any access unit of a coded video sequence, an SEI manifest SEI message shall be present in the first access unit of the coded video sequence in decoding order. The SEI manifest SEI message persists in decoding order from the current access unit until the end of the coded video sequence. When there are multiple SEI manifest SEI messages present in a coded video sequence, they shall have the same content. + +An SEI NAL unit containing an SEI manifest SEI message shall not contain any other SEI messages other than SEI prefix indication SEI messages. When present in an SEI NAL unit, the SEI manifest SEI message shall be the first SEI message in the SEI NAL unit. + +**manifest\_num\_sei\_msg\_types** specifies the number of types of SEI messages for which information is provided in the SEI manifest SEI message. + +**manifest\_sei\_payload\_type[ i ]** indicates the payloadType value of the i-th type of SEI message for which information is provided in the SEI manifest SEI message. The values of **manifest\_sei\_payload\_type[ m ]** and **manifest\_sei\_payload\_type[ n ]** shall not be identical when m is not equal to n. + +**manifest\_sei\_description[ i ]** provides information on SEI messages with payloadType equal to **manifest\_sei\_payload\_type[ i ]** as specified in Table D-12. + +**Table D-12– manifest\_sei\_description[ i ] values** + +| Value | Description | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Indicates that there is no SEI message with payloadType equal to manifest_sei_payload_type[ i ] expected to be present in the coded video sequence. | +| 1 | Indicates that there are SEI messages with payloadType equal to manifest_sei_payload_type[ i ] expected to be present in the coded video sequence, and these SEI messages are considered as necessary. | +| 2 | Indicates that there are SEI messages with payloadType equal to manifest_sei_payload_type[ i ] expected to be present in the coded video sequence, and these SEI messages are considered as unnecessary. | +| 3 | Indicates that there are SEI messages with payloadType equal to manifest_sei_payload_type[ i ] expected to be present in the coded video sequence, and the necessity of these SEI messages is undetermined. | +| 4-255 | Reserved | + +The value of manifest\_sei\_description[ i ] shall be in the range of 0 to 3, inclusive, in bitstreams conforming to this version of this Specification. Other values for manifest\_sei\_description[ i ] are reserved for future use by ITU-T | ISO/IEC. Decoders shall allow the value of manifest\_sei\_description[ i ] greater than or equal to 4 to appear in the syntax and shall ignore all information for payloadType equal to manifest\_sei\_payload\_type[ i ] signalled in the SEI manifest SEI message and shall ignore all SEI prefix indication SEI messages with prefix\_sei\_payload\_type equal to manifest\_sei\_payload\_type[ i ] when manifest\_sei\_description[ i ] is greater than or equal to 4. + +#### D.2.37 SEI prefix indication SEI message semantics + +The SEI prefix indication SEI message carries one or more SEI prefix indications for SEI messages of a particular value of payloadType. Each SEI prefix indication is a bit string that follows the SEI payload syntax of that value of payloadType and contains a number of complete syntax elements starting from the first syntax element in the SEI payload. + +Each SEI prefix indication for an SEI message of a particular value of payloadType indicates that one or more SEI messages of this value of payloadType are expected (i.e., likely) to be present in the coded video sequence and to start with the provided bit string. A starting bit string would typically contain only a true subset of an SEI payload of the type of SEI message indicated by the payloadType, may contain a complete SEI payload, and shall not contain more than a complete SEI payload. It is not prohibited for SEI messages of the indicated value of payloadType to be present that do not start with any of the indicated bit strings. + +These SEI prefix indications should provide sufficient information for indicating what type of processing is needed or what type of content is included. The former (type of processing) indicates decoder-side processing capability, e.g., whether some type of frame unpacking is needed. The latter (type of content) indicates, for example, whether the bitstream contains subtitle captions in a particular language. + +The content of an SEI prefix indication SEI message may, for example, be used by transport-layer or systems-layer processing elements to determine whether the coded video sequence is suitable for delivery to a receiving and decoding system, based on whether the receiving system can properly process the coded video sequence to enable an adequate user experience or whether the coded video sequence satisfies the application needs (as determined in some manner by external means outside the scope of this Specification). + +In one example, when the payloadType indicates the frame packing arrangement SEI message, an SEI prefix indication should include up to at least the syntax element frame\_packing\_arrangement\_type; and when the payloadType indicates the omnidirectional projection indication SEI message, an SEI prefix indication should include up to at least the syntax element projection\_type. + +In another example, for user data registered SEI messages that are used to carry captioning information, an SEI prefix indication should include up to at least the language code; and for user data unregistered SEI messages extended for private use, an SEI prefix indication should include up to at least the UUID. + +When an SEI prefix indication SEI message is present in any access unit of a coded video sequence, an SEI prefix indication SEI message shall be present in the first access unit of the coded video sequence in decoding order. The SEI prefix indication SEI message persists in decoding order from the current access unit until the end of the coded video + +sequence. When there are multiple SEI prefix indication SEI messages present in a coded video sequence for a particular value of `payloadType`, they shall have the same content. + +An SEI NAL unit containing an SEI prefix indication SEI message for a particular value of `payloadType` shall not contain any other SEI messages other than an SEI manifest SEI message and SEI prefix indication SEI messages for other values of `payloadType`. + +**prefix\_sei\_payload\_type** indicates the `payloadType` value of the SEI messages for which one or more SEI prefix indications are provided in the SEI prefix indication SEI message. When an SEI manifest SEI message is also present for the coded video sequence, the value of `prefix_sei_payload_type` shall be equal to one of the `manifest_sei_payload_type[ m ]` values for which `manifest_sei_description[ m ]` is equal to 1 to 3, inclusive, as indicated by an SEI manifest SEI message that applies to the coded video sequence. + +**num\_sei\_prefix\_indications\_minus1** plus 1 specifies the number of SEI prefix indications. + +**num\_bits\_in\_prefix\_indication\_minus1[ i ]** plus 1 specifies the number of bits in the i-th SEI prefix indication. + +**sei\_prefix\_data\_bit[ i ][ j ]** specifies the j-th bit of the i-th SEI prefix indication. + +The bits `sei_prefix_data_bit[ i ][ j ]` for j ranging from 0 to `num_bits_in_prefix_indication_minus1[ i ]`, inclusive, follow the syntax of the SEI payload with `payloadType` equal to `prefix_sei_payload_type`, and contain a number of complete syntax elements starting from the first syntax element in the SEI payload syntax, and may or may not contain all the syntax elements in the SEI payload syntax. The last bit of these bits (i.e., the bit `sei_prefix_data_bit[ i ][ num_bits_in_prefix_indication_minus1[ i ] ]`) shall be the last bit of a syntax element in the SEI payload syntax, unless it is a bit within an `itu_t_t35_payload_byte` or `user_data_payload_byte`. + +NOTE – The exception for `itu_t_t35_payload_byte` and `user_data_payload_byte` is provided because these syntax elements may contain externally-specified syntax elements, and the determination of the boundaries of such externally-specified syntax elements is a matter outside the scope of this Specification. + +#### D.2.38 Shutter interval information SEI message semantics + +The shutter interval information SEI message indicates the shutter interval for the associated video source pictures prior to encoding, e.g., for camera-captured content, the shutter interval is the amount of time that an image sensor is exposed to produce each source picture. + +**sii\_sub\_layer\_idx** specifies the shutter interval temporal sub-layer index of the current picture. The value of `sii_sub_layer_idx` shall be equal to 0 when the current access unit is the first access unit of the coded video sequence. When `fixed_shutter_interval_within_cvs_flag` is equal to 1, the value of `sii_sub_layer_idx` shall be equal to 0. Otherwise, `fixed_shutter_interval_within_cvs_flag` is equal to 0, the value of `sii_sub_layer_idx` shall be less than or equal to the value of `sii_max_sub_layers_minus1`. + +**shutter\_interval\_info\_present\_flag** equal to 1 indicates that the syntax elements `sii_time_scale`, `fixed_shutter_interval_within_cvs_flag`, and either `sii_num_units_in_shutter_interval` or `sii_max_sub_layers_minus1` and `sub_layer_num_units_in_shutter_interval[ i ]` are present. `shutter_interval_info_present_flag` equal to 0 indicates that the syntax elements `sii_time_scale`, `fixed_shutter_interval_within_cvs_flag`, `sii_num_units_in_shutter_interval`, `sii_max_sub_layers_minus1`, and `sub_layer_num_units_in_shutter_interval[ i ]` are not present. The value of `shutter_interval_info_present_flag` shall be equal to 1 when the current access unit is the first access unit of the coded video sequence. Otherwise, the current access unit is not the first access unit of the coded video sequence, the value of `shutter_interval_info_present_flag` shall be equal to 0. + +**sii\_time\_scale** specifies the number of time units that pass in one second. The value of `sii_time_scale` shall be greater than 0. For example, a time coordinate system that measures time using a 27 MHz clock has an `sii_time_scale` of 27 000 000. + +**fixed\_shutter\_interval\_within\_cvs\_flag** equal to 1 specifies that the indicated shutter interval is the same for all pictures in the coded video sequence. `fixed_shutter_interval_within_cvs_flag` equal to 0 specifies that the indicated shutter interval may not be the same for all pictures in the coded video sequence. + +**sii\_num\_units\_in\_shutter\_interval**, when `fixed_shutter_interval_within_cvs_flag` is equal to 1, specifies the number of time units of a clock operating at the frequency `sii_time_scale` Hz that corresponds to the indicated shutter interval of each picture in the coded video sequence. The value 0 may be used to indicate that the associated video content contains screen capture content, computer generated content, or other non-camera-captured content. + +The indicated shutter interval, denoted by the variable `shutterInterval`, in units of seconds, is equal to the quotient of `sii_num_units_in_shutter_interval` divided by `sii_time_scale`. For example, to represent a shutter interval equal to 0.04 seconds, `sii_time_scale` may be equal to 27 000 000 and `sii_num_units_in_shutter_interval` may be equal to 1 080 000. + +**sii\_max\_sub\_layers\_minus1** plus 1 specifies the maximum number of shutter interval temporal sub-layers indexes that may be present in the coded video sequence. + +**sub\_layer\_num\_units\_in\_shutter\_interval[ i ]**, when present, specifies the number of time units of a clock operating at the frequency **sii\_time\_scale** Hz that corresponds to the shutter interval of each picture in the coded video sequence for which the value of **sii\_sub\_layer\_idx** is equal to i. The sub-layer shutter interval for each picture for which the value of **sii\_sub\_layer\_idx** is equal to i, denoted by the variable **subLayerShutterInterval[ i ]**, in units of seconds, is equal to the quotient of **sub\_layer\_num\_units\_in\_shutter\_interval[ i ]** divided by **sii\_time\_scale**. + +The variable **subLayerShutterInterval[ i ]**, corresponding to the indicated shutter interval of each picture in the coded video sequence for which the value of **sii\_sub\_layer\_idx** is equal to i, is thus derived as follows: + +$$\begin{aligned} & \text{if( fixed\_shutter\_interval\_within\_cvs\_flag )} \\ & \quad \text{subLayerShutterInterval[ i ]} = \text{sii\_num\_units\_in\_shutter\_interval} \div \text{sii\_time\_scale} \\ & \text{else} \\ & \quad \text{subLayerShutterInterval[ i ]} = \text{sub\_layer\_num\_units\_in\_shutter\_interval[ i ]} \div \text{sii\_time\_scale} \end{aligned} \quad (\text{D-51})$$ + +When a shutter interval information SEI message is present for any access unit in a coded video sequence, a shutter interval information SEI message shall be present for the IDR access unit that is the first access unit of the coded video sequence. All shutter interval information SEI messages that apply to the same access unit shall have the same content. + +**sii\_time\_scale** and **fixed\_shutter\_interval\_within\_cvs\_flag** persist from the first access unit of the coded video sequence until a new coded video sequence begins or the bitstream ends. + +When the value of **fixed\_shutter\_interval\_within\_cvs\_flag** is equal to 0, a shutter interval information SEI message shall be present for every picture in the coded video sequence. When present, **sii\_num\_units\_in\_shutter\_interval**, **sii\_max\_sub\_layers\_minus1**, and **sub\_layer\_num\_units\_in\_shutter\_interval[ i ]**, persist from the first access unit of the coded video sequence until a new coded video sequence begins or the bitstream ends. + +#### D.2.39 Reserved SEI message semantics + +This message consists of data reserved for future backward-compatible use by ITU-T | ISO/IEC. Encoders conforming to this Recommendation | International Standard shall not send reserved SEI messages until and unless the use of such messages has been specified by ITU-T | ISO/IEC. Decoders that encounter reserved SEI messages shall discard their content without effect on the decoding process, except as specified in future Recommendations | International Standards specified by ITU-T | ISO/IEC. + +**reserved\_sei\_message\_payload\_byte** is a byte reserved for future use by ITU-T | ISO/IEC. + +### D.3 Use of SEI messages specified in other documents + +#### D.3.1 General + +The SEI messages identified in clause D.1.1 as having syntax structures specified in other documents including Rec. ITU-T H.274 | ISO/IEC 23002-7 or ISO/IEC 23001-11 may be used together with bitstreams specified by this Specification. + +When any SEI message for which the payload type value is specified in this Specification and the syntax and semantics are specified in Rec. ITU-T H.274 | ISO/IEC 23002-7 is included in a bitstream specified by this Specification, the SEI payload syntax shall be included into the **sei\_payload()** syntax structure as specified in clause D.1.1, shall use the **payloadType** value specified in clause D.1.1, and, additionally, any SEI-message-specific constraints specified in this annex for that particular SEI message shall apply. + +Some definitions of terms in Rec. ITU-T H.274 | ISO/IEC 23002-7 differ from those in this Specification, and the semantics specified therein are to be interpreted using its terminology. + +The value of **PayloadBits** as specified in clause D.1.1 is passed to the parser of the SEI message syntax structures specified in Rec. ITU-T H.274 | ISO/IEC 23002-7. + +#### D.3.2 Use of the annotated regions SEI message + +When an annotated regions SEI message is included in a bitstream specified by this Specification, for purposes of interpretation of the annotated regions SEI message, the following variables are specified: + +- **CroppedWidth** and **CroppedHeight**, set as specified by Equations 7-23 and 7-24, respectively. +- A conformance cropping window left offset, **ConfWinLeftOffset**, set equal to **CropUnitX \* frame\_crop\_left\_offset**. +- A conformance cropping window top offset, **ConfWinTopOffset**, set equal to **CropUnitY \* frame\_crop\_top\_offset**. +- **ChromaFormatIdc**, set equal to **chroma\_format\_idc**. + +### D.3.3 Use of the neural network post-filter characteristics SEI message and the neural-network post-filter activation SEI message + +Let `currPic` be the cropped decoded output picture that results from the decoding process specified in clauses 2 to 9 and for which the neural-network post-processing filter (NNPF) defined by the neural-network post-filter characteristics (NNPFC) SEI message is activated by a neural-network post-filter activation (NNPFA) SEI message. + +The variable `pictureRateUpsamplingFlag` is set equal to $(( \text{nnpfc\_purpose} \& 0x08 ) > 0) ? 1 : 0$ . + +The variable `numInputPics` is set equal to `nnpfc_num_input_pics_minus1 + 1`. + +The variable `numInferences` is derived as follows: + +- If all of the following conditions are true, the variable `numPostRoll` is set equal to the value of `i` such that `nnpfc_interpolated_pics[ i ]` is greater than 0 and the variable `numInferences` is set equal to `1 + numPostRoll`: + - `nnpfc_purpose` is equal to 8 (i.e., the only purpose for the NNPF is picture rate upsampling). + - The NNPFA SEI message that activated this NNPF has `nnpfa_persistence_flag` equal to 1. + - `nnpfc_interpolated_pics[ i ]` is greater than 0 only for a single value of `i` that is greater than 0. + - Either of the following conditions is true: + - `currPic` is the last picture of the bitstream in output order. + - `currPic` is the last picture in the coded video sequence in output order and `nnpfa_no_foll_clvs_flag` is equal to 1. +- Otherwise, if all of the following conditions are true, the variable `numPostRoll` is set equal to `InpIdx[ i ]` for the value of `i` such that `nnpfa_output_flag[ i ]` is equal to 1, and the variable `numInferences` is set equal to `1 + numPostRoll`: + - `pictureRateUpsamplingFlag` is equal to 0. + - `numInputPics` is greater than 1. + - The NNPFA SEI message that activated this NNPF has `nnpfa_persistence_flag` equal to 1. + - `nnpfa_output_flag[ idx ]` is equal to 1 for a single value of `idx` in the range of 0 to `NumInpPicsInOutputTensor – 1`, inclusive, and for that single value of `idx`, `InpIdx[ idx ]` is greater than 0. + - Either of the following conditions is true: + - `currPic` is the last picture of the bitstream in output order. + - `currPic` is the last picture in the coded video sequence in output order and `nnpfa_no_foll_clvs_flag` is equal to 1. +- Otherwise, the variable `numInferences` is set equal to 1. + +For each value of `j` in the range of 0 to `numInferences – 1`, inclusive, the following applies: + +- The arrays `inputPic[ i ]` and `inputPresentFlag[ i ]` for `i` in the range of 0 to `numInputPics – 1`, inclusive, representing all the input pictures and the presence of input pictures, respectively, are specified as follows: + - When `j` is greater than 0, for each value of `k` in the range of 0 to `j – 1`, inclusive, `inputPic[ k ]` is set to be `currPic` and `inputPresentFlag[ k ]` is set equal to 0. + - The `j`-th input picture, `inputPic[ j ]`, is set to be `currPic` and `inputPresentFlag[ j ]` is set equal to 1. + - When `numInputPics` is greater than 1, the following applies for each value of `i` in the range of `j + 1` to `numInputPics – 1`, inclusive, in increasing order of `i`: + - If both of the following conditions are true, `inputPic[ i ]` is set to be `prevPic` and `inputPresentFlag[ i ]` is set equal to 1: + - Either of the following conditions is true: + - `pictureRateUpsamplingFlag` is equal to 1 and `currPic` is associated with a frame packing arrangement SEI message with `frame_packing_arrangement_type` equal to 5 and a particular value of `current_frame_is_frame0_flag`, and there is a cropped decoded output picture `prevPic` that is the last picture in output order among all cropped decoded output pictures that precede `inputPic[ i – 1 ]` in output order, and are associated with a frame packing arrangement SEI + +message with frame\_packing\_arrangement\_type equal to 5 and the same value of current\_frame\_is\_frame0\_flag. + +- pictureRateUpsamplingFlag is equal to 0 or currPic is not associated with a frame packing arrangement SEI message with frame\_packing\_arrangement\_type equal to 5, and there is a cropped decoded output picture prevPic that is the last picture in output order among all cropped decoded output pictures that precede inputPic[ i – 1 ] in output order. +- nnpfa\_no\_prev\_clvs\_flag is equal to 0 or the coded picture corresponding to prevPic and the current picture are present in the same coded video sequence. +- Otherwise, the following applies: + - inputPic[ i ] is set to be the same picture as inputPic[ i – 1 ] and inputPresentFlag[ i ] is set equal to 0. + - It is a requirement of bitstream conformance that, when pictureRateUpsamplingFlag is equal to 1, nnpfc\_interpolated\_pics[ i – 1 ] shall be equal to 0. + - It is a requirement of bitstream conformance that when inputPresentFlag[ i ] is equal to 0 and nnpfc\_input\_pic\_output\_flag[ i ] is equal to 1, the value of nnpfa\_output\_flag[ idx ] shall be equal to 0 for the value of idx such that InpIdx[ idx ] is equal to i. +- For purposes of interpretation of the NNPFC SEI message, the following variables are specified: + - If numInputPics is greater than 1 and there is a second NNPF that is defined by at least one NNPFC SEI message, is activated by an NNPFA SEI message for currPic, and has nnpfc\_purpose equal to 4, the following applies: + - CroppedWidth is set equal to nnpfcOutputPicWidth defined for the second NNPF. + - CroppedHeight is set equal to nnpfcOutputPicHeight defined for the second NNPF. + - Otherwise, the following applies: + - CroppedWidth is set as specified by Equation 7-23 for currPic. + - CroppedHeight is set as specified by Equation 7-24 for currPic. + - The luma sample arrays CroppedYPic[ i ] and the chroma sample arrays CroppedCbPic[ i ] and CroppedCrPic[ i ], when present, are derived as follows for each value of i in the range of 0 to numInputPics – 1, inclusive: + - The variable sourcePic is derived as follows: + - If inputPresentFlag[ i ] is equal to 1 or nnpfc\_absent\_input\_pic\_zero\_flag is equal to 0, sourcePic is set to be inputPic[ i ]. + - Otherwise(inputPresentFlag[ i ] is equal to 0 and nnpfc\_absent\_input\_pic\_zero\_flag is equal to 1), sourcePic is set to be a picture with a luma sample array of CroppedWidth × CroppedHeight samples equal to 0 and Cb and Cr sample arrays of ( CroppedWidth / SubWidthC ) × ( CroppedHeight / SubHeightC ) samples equal to 0. + - If numInputPics is equal to 1, the following applies: + - The luma sample array CroppedYPic[ i ] and the chroma sample arrays CroppedCbPic[ i ] and CroppedCrPic[ i ], when present, are set to be the 2-dimensional arrays of decoded sample values of the Y, Cb and Cr components, respectively, of sourcePic. + - Otherwise (numInputPics is greater than 1), the following applies: + - The variable sourceWidth is set equal to the value of CroppedWidth set as specified by Equation 7-23 for sourcePic. + - The variable sourceHeight is set equal to the value of CroppedHeight is set as specified by Equation 7-24 for sourcePic. + - If sourceWidth is equal to CroppedWidth and sourceHeight is equal to CroppedHeight, resampledPic is set to be the same as sourcePic. + +- Otherwise (sourceWidth is not equal to CroppedWidth or sourceHeight is not equal to CroppedHeight), the following applies: + - There shall be an NNPF, hereafter referred to as the super resolution NNPF, that is defined by at least one NNPFC SEI message, is activated by an NNPFA SEI message for sourcePic, and has nnpfc\_purpose equal to 4, nnpfcOutputPicWidth equal to CroppedWidth and nnpfcOutputPicHeight equal to CroppedHeight. + - resampledPic is set to be the output of the neural-network inference of the super resolution NNPF with sourcePic being an input. +- The luma sample array CroppedYPic[ i ] and the chroma sample arrays CroppedCbPic[ i ] and CroppedCrPic[ i ], when present, are set to be the 2-dimensional arrays of decoded sample values of the Y, Cb and Cr components, respectively, of resampledPic. +- BitDepthY and BitDepthC are set equal to BitDepthY and BitDepthC, respectively +- ChromaFormatIdc is set equal to chroma\_format\_idc. +- The array StrengthControlVal[ i ] for all values of i in the range of 0 to numInputPics – 1, inclusive, specifying the filtering strength control value for the input pictures for the NNPF, is derived as follows: + - StrengthControlVal[ i ] is set equal to the value of $( \text{firstSliceQp}_Y + \text{QpBdOffset}_Y ) \div ( 51 + \text{QpBdOffset}_Y )$ , where firstSliceQpY is equal to SliceQPY of the first slice of inputPic[ i ]. + +There shall not be more than two NNPFC SEI messages present in an access unit with the same value of nnpfc\_id. When there are two NNPFC SEI messages present in an access unit with the same value of nnpfc\_id, these SEI messages shall have different content. When two NNPFC SEI messages with the same nnpfc\_id and different content are present in the same access unit, both of these NNPFC SEI messages shall be in the same SEI NAL unit. + +#### D.3.4 Use of the phase indication SEI message + +For purposes of interpretation of the phase indication SEI message, the following variables are specified: + +- CroppedWidth and CroppedHeight, set as specified by Equations 7-23 and 7-24, respectively. + +## Annex E + +### Video usability information + +(This annex forms an integral part of this Recommendation | International Standard.) + +This annex specifies syntax and semantics of the VUI parameters of the sequence parameter sets. + +VUI parameters are not required for constructing the luma or chroma samples by the decoding process. Conforming decoders are not required to process this information for output order conformance to this Recommendation | International Standard (see Annex C for the specification of conformance). Some VUI parameters are required to check bitstream conformance and for output timing decoder conformance. + +In Annex E, specification for presence of VUI parameters is also satisfied when those parameters (or some subset of them) are conveyed to decoders (or to the HRD) by other means not specified by this Recommendation | International Standard. When present in the bitstream, VUI parameters shall follow the syntax and semantics specified in clauses 7.3.2.1 and 7.4.2.1 and this annex. When the content of VUI parameters is conveyed for the application by some means other than presence within the bitstream, the representation of the content of the VUI parameters is not required to use the same syntax specified in this annex. For the purpose of counting bits, only the appropriate bits that are actually present in the bitstream are counted. + +#### E.1 VUI syntax + +##### E.1.1 VUI parameters syntax + +| vui_parameters( ) { | C | Descriptor | +|--------------------------------------------|---|------------| +| aspect_ratio_info_present_flag | 0 | u(1) | +| if( aspect_ratio_info_present_flag ) { | | | +| aspect_ratio_idc | 0 | u(8) | +| if( aspect_ratio_idc == Extended_SAR ) { | | | +| sar_width | 0 | u(16) | +| sar_height | 0 | u(16) | +| } | | | +| } | | | +| overscan_info_present_flag | 0 | u(1) | +| if( overscan_info_present_flag ) | | | +| overscan_appropriate_flag | 0 | u(1) | +| video_signal_type_present_flag | 0 | u(1) | +| if( video_signal_type_present_flag ) { | | | +| video_format | 0 | u(3) | +| video_full_range_flag | 0 | u(1) | +| colour_description_present_flag | 0 | u(1) | +| if( colour_description_present_flag ) { | | | +| colour_primaries | 0 | u(8) | +| transfer_characteristics | 0 | u(8) | +| matrix_coefficients | 0 | u(8) | +| } | | | +| } | | | +| chroma_loc_info_present_flag | 0 | u(1) | +| if( chroma_loc_info_present_flag ) { | | | +| chroma_sample_loc_type_top_field | 0 | ue(v) | +| chroma_sample_loc_type_bottom_field | 0 | ue(v) | + +| | | | +|--------------------------------------------------------------------------|---|-------| +| } | | | +| timing_info_present_flag | 0 | u(1) | +| if( timing_info_present_flag ) { | | | +| num_units_in_tick | 0 | u(32) | +| time_scale | 0 | u(32) | +| fixed_frame_rate_flag | 0 | u(1) | +| } | | | +| nal_hrd_parameters_present_flag | 0 | u(1) | +| if( nal_hrd_parameters_present_flag ) | | | +| hrd_parameters( ) | 0 | | +| vc1_hrd_parameters_present_flag | 0 | u(1) | +| if( vc1_hrd_parameters_present_flag ) | | | +| hrd_parameters( ) | 0 | | +| if( nal_hrd_parameters_present_flag vc1_hrd_parameters_present_flag ) | | | +| low_delay_hrd_flag | 0 | u(1) | +| pic_struct_present_flag | 0 | u(1) | +| bitstream_restriction_flag | 0 | u(1) | +| if( bitstream_restriction_flag ) { | | | +| motion_vectors_over_pic_boundaries_flag | 0 | u(1) | +| max_bytes_per_pic_denom | 0 | ue(v) | +| max_bits_per_mb_denom | 0 | ue(v) | +| log2_max_mv_length_horizontal | 0 | ue(v) | +| log2_max_mv_length_vertical | 0 | ue(v) | +| max_num_reorder_frames | 0 | ue(v) | +| max_dec_frame_buffering | 0 | ue(v) | +| } | | | +| } | | | + +### E.1.2 HRD parameters syntax + +| | | | +|------------------------------------------------------------------------|----------|-------------------| +| hrd_parameters( ) { | C | Descriptor | +| cpb_cnt_minus1 | 0 5 | ue(v) | +| bit_rate_scale | 0 5 | u(4) | +| cpb_size_scale | 0 5 | u(4) | +| for( SchedSelIdx = 0; SchedSelIdx <= cpb_cnt_minus1; SchedSelIdx++ ) { | | | +| bit_rate_value_minus1[ SchedSelIdx ] | 0 5 | ue(v) | +| cpb_size_value_minus1[ SchedSelIdx ] | 0 5 | ue(v) | +| cbr_flag[ SchedSelIdx ] | 0 5 | u(1) | +| } | | | +| initial_cpbe_removal_delay_length_minus1 | 0 5 | u(5) | +| cpbe_removal_delay_length_minus1 | 0 5 | u(5) | +| dpb_output_delay_length_minus1 | 0 5 | u(5) | +| time_offset_length | 0 5 | u(5) | +| } | | | + +## E.2 VUI semantics + +### E.2.1 VUI parameters semantics + +**aspect\_ratio\_info\_present\_flag** equal to 1 specifies that **aspect\_ratio\_idc** is present. **aspect\_ratio\_info\_present\_flag** equal to 0 specifies that **aspect\_ratio\_idc** is not present. + +**aspect\_ratio\_idc** specifies the value of the sample aspect ratio of the luma samples. Table E-1 shows the meaning of the code. When **aspect\_ratio\_idc** indicates **Extended\_SAR**, the sample aspect ratio is represented by **sar\_width** : **sar\_height**. When the **aspect\_ratio\_idc** syntax element is not present, **aspect\_ratio\_idc** value shall be inferred to be equal to 0. + +**Table E-1 – Meaning of sample aspect ratio indicator** + +| aspect_ratio_idc | Sample aspect ratio | (informative)
Examples of use | +|-------------------------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Unspecified | | +| 1 | 1:1
("square") | 7680x4320 16:9 frame without horizontal overscan
3840x2160 16:9 frame without horizontal overscan
1280x720 16:9 frame without horizontal overscan
1920x1080 16:9 frame without horizontal overscan (cropped from 1920x1088)
640x480 4:3 frame without horizontal overscan | +| 2 | 12:11 | 720x576 4:3 frame with horizontal overscan
352x288 4:3 frame without horizontal overscan | +| 3 | 10:11 | 720x480 4:3 frame with horizontal overscan
352x240 4:3 frame without horizontal overscan | +| 4 | 16:11 | 720x576 16:9 frame with horizontal overscan
528x576 4:3 frame without horizontal overscan | +| 5 | 40:33 | 720x480 16:9 frame with horizontal overscan
528x480 4:3 frame without horizontal overscan | +| 6 | 24:11 | 352x576 4:3 frame without horizontal overscan
480x576 16:9 frame with horizontal overscan | +| 7 | 20:11 | 352x480 4:3 frame without horizontal overscan
480x480 16:9 frame with horizontal overscan | +| 8 | 32:11 | 352x576 16:9 frame without horizontal overscan | +| 9 | 80:33 | 352x480 16:9 frame without horizontal overscan | +| 10 | 18:11 | 480x576 4:3 frame with horizontal overscan | +| 11 | 15:11 | 480x480 4:3 frame with horizontal overscan | +| 12 | 64:33 | 528x576 16:9 frame without horizontal overscan | +| 13 | 160:99 | 528x480 16:9 frame without horizontal overscan | +| 14 | 4:3 | 1440x1080 16:9 frame without horizontal overscan | +| 15 | 3:2 | 1280x1080 16:9 frame without horizontal overscan | +| 16 | 2:1 | 960x1080 16:9 frame without horizontal overscan | +| 17..254 | Reserved | | +| 255 | Extended_SAR | | + +NOTE 1 – For the examples in Table E-1, the term "without horizontal overscan" refers to display processes in which the display area matches the area of the cropped decoded pictures and the term "with horizontal overscan" refers to display processes in which some parts near the left and/or right border of the cropped decoded pictures are not visible in the display area. As an example, the entry "720x576 4:3 frame with horizontal overscan" for **aspect\_ratio\_idc** equal to 2 refers to having an area of 704x576 luma samples (which has an aspect ratio of 4:3) of the cropped decoded frame (720x576 luma samples) that is visible in the display area. + +**sar\_width** indicates the horizontal size of the sample aspect ratio (in arbitrary units). + +**sar\_height** indicates the vertical size of the sample aspect ratio (in the same arbitrary units as **sar\_width**). + +**sar\_width** and **sar\_height** shall be relatively prime or equal to 0. When **aspect\_ratio\_idc** is equal to 0 or **sar\_width** is equal to 0 or **sar\_height** is equal to 0, the sample aspect ratio shall be considered unspecified by this Recommendation | International Standard. + +**overscan\_info\_present\_flag** equal to 1 specifies that the overscan\_appropriate\_flag is present. When overscan\_info\_present\_flag is equal to 0 or is not present, the preferred display method for the video signal is unspecified. + +**overscan\_appropriate\_flag** equal to 1 indicates that the cropped decoded pictures output are suitable for display using overscan. overscan\_appropriate\_flag equal to 0 indicates that the cropped decoded pictures output contain visually important information in the entire region out to the edges of the cropping rectangle of the picture, such that the cropped decoded pictures output should not be displayed using overscan. Instead, they should be displayed using either an exact match between the display area and the cropping rectangle, or using underscan. As used in this paragraph, the term "overscan" refers to display processes in which some parts near the borders of the cropped decoded pictures are not visible in the display area. The term "underscan" describes display processes in which the entire cropped decoded pictures are visible in the display area, but they do not cover the entire display area. For display processes that neither use overscan nor underscan, the display area exactly matches the area of the cropped decoded pictures. + +NOTE 2 – For example, overscan\_appropriate\_flag equal to 1 might be used for entertainment television programming, or for a live view of people in a videoconference, and overscan\_appropriate\_flag equal to 0 might be used for computer screen capture or security camera content. + +**video\_signal\_type\_present\_flag** equal to 1 specifies that video\_format, video\_full\_range\_flag and colour\_description\_present\_flag are present. video\_signal\_type\_present\_flag equal to 0, specify that video\_format, video\_full\_range\_flag and colour\_description\_present\_flag are not present. + +**video\_format** indicates the representation of the pictures as specified in Table E-2, before being coded in accordance with this Recommendation | International Standard. When the video\_format syntax element is not present, video\_format value shall be inferred to be equal to 5. + +**Table E-2 – Meaning of video\_format** + +| video_format | Meaning | +|---------------------|--------------------------| +| 0 | Component | +| 1 | PAL | +| 2 | NTSC | +| 3 | SECAM | +| 4 | MAC | +| 5 | Unspecified video format | +| 6 | Reserved | +| 7 | Reserved | + +**video\_full\_range\_flag** indicates the black level and range of the luma and chroma signals as derived from E'Y, E'PB, and E'PR or E'R, E'G, and E'B real-valued component signals. + +When the video\_full\_range\_flag syntax element is not present, the value of video\_full\_range\_flag shall be inferred to be equal to 0. + +**colour\_description\_present\_flag** equal to 1 specifies that colour\_primaries, transfer\_characteristics and matrix\_coefficients are present. colour\_description\_present\_flag equal to 0 specifies that colour\_primaries, transfer\_characteristics and matrix\_coefficients are not present. + +**colour\_primaries** indicates the chromaticity coordinates of the source primaries as specified in Table E-3 in terms of the CIE 1931 definition of x and y as specified by ISO 11664-1. + +When the colour\_primaries syntax element is not present, the value of colour\_primaries shall be inferred to be equal to 2 (the chromaticity is unspecified or is determined by the application). + +**Table E-3 – Colour primaries interpretation using colour\_primaries syntax element** + +| Value | Primaries | Informative remark | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Reserved | For future use by ITU-T ISO/IEC | +| 1 | primary        x        y
green        0.300        0.600
blue        0.150        0.060
red        0.640        0.330
white D65        0.3127        0.3290 | Rec. ITU-R BT.709-6
Rec. ITU-R BT.1361-0 conventional colour gamut system and extended colour gamut system (historical)
IEC 61966-2-1 sRGB or sYCC
IEC 61966-2-4
Society of Motion Picture and Television Engineers RP 177 (1993) Annex B | +| 2 | Unspecified | Image characteristics are unknown or are determined by the application. | +| 3 | Reserved | For future use by ITU-T ISO/IEC | +| 4 | primary        x        y
green        0.21        0.71
blue        0.14        0.08
red        0.67        0.33
white C        0.310        0.316 | Rec. ITU-R BT.470-7 System M (historical)
United States National Television System Committee 1953 Recommendation for transmission standards for colour television
United States Federal Communications Commission Title 47 Code of Federal Regulations (2016) 73.682 (a) (20) | +| 5 | primary        x        y
green        0.29        0.60
blue        0.15        0.06
red        0.64        0.33
white D65        0.3127        0.3290 | Rec. ITU-R BT.470-7 System B, G (historical)
Rec. ITU-R BT.601-7 625
Rec. ITU-R BT.1358-0 625 (historical)
Rec. ITU-R BT.1700-0 625 PAL and 625 SECAM | +| 6 | primary        x        y
green        0.310        0.595
blue        0.155        0.070
red        0.630        0.340
white D65        0.3127        0.3290 | Rec. ITU-R BT.601-7 525
Rec. ITU-R BT.1358-1 525 or 625 (historical)
Rec. ITU-R BT.1700-0 NTSC
Society of Motion Picture and Television Engineers 170M (2004)
(functionally the same as the value 7) | +| 7 | primary        x        y
green        0.310        0.595
blue        0.155        0.070
red        0.630        0.340
white D65        0.3127        0.3290 | Society of Motion Picture and Television Engineers 240M (1999, historical)
(functionally the same as the value 6) | +| 8 | primary        x        y
green        0.243        0.692 (Wratten 58)
blue        0.145        0.049 (Wratten 47)
red        0.681        0.319 (Wratten 25)
white C        0.310        0.316 | Generic film (colour filters using Illuminant C) | +| 9 | primary        x        y
green        0.170        0.797
blue        0.131        0.046
red        0.708        0.292
white D65        0.3127        0.3290 | Rec. ITU-R BT.2020-2
Rec. ITU-R BT.2100-2 | +| 10 | primary        x        y
Y        0.0        1.0
Z        0.0        0.0
X        1.0        0.0
centre white $1 \div 3$ $1 \div 3$ | Society of Motion Picture and Television Engineers ST 428-1 (2006)
(CIE 1931 XYZ as in ISO 11664-1) | +| 11 | primary        x        y
green        0.265        0.690
blue        0.150        0.060
red        0.680        0.320
white        0.314        0.351 | Society of Motion Picture and Television Engineers RP 431-2 (2011)
Society of Motion Picture and Television Engineers RP ST 2113 (2018) "P3DCI" | + +| | | | | | +|---------|-----------|--------|--------|---------------------------------------------------------------------------| +| 12 | primary | x | y | Society of Motion Picture and Television Engineers EG 432-1 (2010) | +| | green | 0.265 | 0.690 | | +| | blue | 0.150 | 0.060 | Society of Motion Picture and Television Engineers ST 2113 (2018) "P3D65" | +| | red | 0.680 | 0.320 | | +| | white D65 | 0.3127 | 0.3290 | | +| 13..21 | Reserved | | | For future use by ITU-T ISO/IEC | +| 22 | primary | x | y | EBU Tech. 3213-E (1975) | +| | green | 0.295 | 0.605 | | +| | blue | 0.155 | 0.077 | | +| | red | 0.630 | 0.340 | | +| | white D65 | 0.3127 | 0.3290 | | +| 23..255 | Reserved | | | For future use by ITU-T ISO/IEC | + +**transfer\_characteristics**, as specified in Table E-4, either indicates the reference opto-electronic transfer characteristic function of the source picture as a function of a source input linear optical intensity input $L_c$ with a nominal real-valued range of 0 to 1 or indicates the inverse of the reference electro-optical transfer characteristic function as a function of an output linear optical intensity $L_o$ with a nominal real-valued range of 0 to 1. For interpretation of entries in Table E-4 that are expressed in terms of multiple curve segments parameterized by the variable $\alpha$ over a region bounded by the variable $\beta$ or by the variables $\beta$ and $\gamma$ , the values of $\alpha$ and $\beta$ are defined to be the positive constants necessary for the curve segments that meet at the value $\beta$ to have continuity of both value and slope at the value $\beta$ . The value of $\gamma$ , when applicable, is defined to be the positive constant necessary for the associated curve segments to meet at the value $\gamma$ . For example, for transfer\_characteristics equal to 1, 6, 11, 14, or 15, $\alpha$ has the value $1 + 5.5 * \beta = 1.099\,296\,826\,809\,442\dots$ and $\beta$ has the value $0.018\,053\,968\,510\,807\dots$ + +When video\_full\_range\_flag is equal to 1 and either or both of the following conditions apply, transfer\_characteristics shall not be equal to 16 or 18: + +- BitDepthY is less than 10. +- chroma\_format\_idc is not equal to 0 (monochrome) and BitDepthC is less than 10. + +When the transfer\_characteristics syntax element is not present, the value of transfer\_characteristics shall be inferred to be equal to 2 (the transfer characteristics are unspecified or are determined by the application). Values of transfer\_characteristics that are identified as reserved in Table E-4 are reserved for future use by ITU-T | ISO/IEC and shall not be present in bitstreams conforming to this version of this Specification. Decoders shall interpret reserved values of transfer\_characteristics as equivalent to the value 2. + +NOTE 3 – As indicated in Table E-4, some values of transfer\_characteristics are defined in terms of a reference opto-electronic transfer characteristic function and others are defined in terms of a reference electro-optical transfer characteristic function, according to the convention that has been applied in other Specifications. In the cases of Rec. ITU-R BT.709-6 and Rec. ITU-R BT.2020-2 (which may be indicated by transfer\_characteristics equal to 1, 6, 14, or 15), although the value is defined in terms of a reference opto-electronic transfer characteristic function, a suggested corresponding reference electro-optical transfer characteristic function for flat panel displays used in HDTV studio production has been specified in Rec. ITU-R BT.1886-0. + +**Table E-4 – Transfer characteristics interpretation using transfer\_characteristics syntax element** + +| Value | Transfer characteristic | Informative remark | +|-------|--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Reserved | For future use by ITU-T ISO/IEC | +| 1 | $V = \alpha * L_c^{0.45} - (\alpha - 1)$ for $1 \geq L_c \geq \beta$
$V = 4.500 * L_c$ for $\beta > L_c \geq 0$ | Rec. ITU-R BT.709-6
Rec. ITU-R BT.1361-0 conventional colour gamut system (historical)
(functionally the same as the value 6, 14, and 15) | +| 2 | Unspecified | Image characteristics are unknown or are determined by the application. | +| 3 | Reserved | For future use by ITU-T ISO/IEC | + +| | | | +|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4 | Assumed display gamma 2.2 | Rec. ITU-R BT.470-7 System M (historical)
United States National Television System Committee 1953 Recommendation for transmission standards for colour television
United States Federal Communications Commission Title 47 Code of Federal Regulations (2016) 73.682 (a) (20)
Rec. ITU-R BT.1700-0 625 PAL and 625 SECAM | +| 5 | Assumed display gamma 2.8 | Rec. ITU-R BT.470-7 System B, G (historical) | +| 6 | $V = \alpha * L_c^{0.45} - (\alpha - 1)$ for $1 \geq L_c \geq \beta$
$V = 4.500 * L_c$ for $\beta > L_c \geq 0$ | Rec. ITU-R BT.601-7 525 or 625
Rec. ITU-R BT.1358-1 525 or 625 (historical)
Rec. ITU-R BT.1700-0 NTSC
Society of Motion Picture and Television Engineers 170M (2004)
(functionally the same as the value 1) | +| 7 | $V = \alpha * L_c^{0.45} - (\alpha - 1)$ for $1 \geq L_c \geq \beta$
$V = 4.0 * L_c$ for $\beta > L_c \geq 0$ | Society of Motion Picture and Television Engineers 240M (1999, historical) | +| 8 | $V = L_c$ for $1 > L_c \geq 0$ | Linear transfer characteristics | +| 9 | $V = 1.0 + \text{Log}_{10}(L_c) \div 2$ for $1 \geq L_c \geq 0.01$
$V = 0.0$ for $0.01 > L_c \geq 0$ | Logarithmic transfer characteristic (100:1 range) | +| 10 | $V = 1.0 + \text{Log}_{10}(L_c) \div 2.5$ for $1 \geq L_c \geq \text{Sqrt}(10) \div 1000$
$V = 0.0$ for $\text{Sqrt}(10) \div 1000 > L_c \geq 0$ | Logarithmic transfer characteristic (100 * Sqrt(10) : 1 range) | +| 11 | $V = \alpha * L_c^{0.45} - (\alpha - 1)$ for $L_c \geq \beta$
$V = 4.500 * L_c$ for $\beta > L_c > -\beta$
$V = -\alpha * (-L_c)^{0.45} + (\alpha - 1)$ for $-\beta \geq L_c$ | IEC 61966-2-4 | +| 12 | $V = \alpha * L_c^{0.45} - (\alpha - 1)$ for $1.33 > L_c \geq \beta$
$V = 4.500 * L_c$ for $\beta > L_c \geq -\gamma$
$V = -(\alpha * (-4 * L_c)^{0.45} - (\alpha - 1)) \div 4$ for $-\gamma \geq L_c \geq -0.25$ | Rec. ITU-R BT.1361-0 extended colour gamut system (historical) | +| 13 | – If matrix_coefficients is equal to 0
$V = \alpha * L_c^{(1 \div 2.4)} - (\alpha - 1)$ for $1 > L_c \geq \beta$
$V = 12.92 * L_c$ for $\beta > L_c \geq 0$
– Otherwise
$V = \alpha * L_c^{(1 \div 2.4)} - (\alpha - 1)$ for $L_c \geq \beta$
$V = 12.92 * L_c$ for $\beta > L_c > -\beta$
$V = -\alpha * (-L_c)^{(1 \div 2.4)} + (\alpha - 1)$ for $-\beta \geq L_c$ | IEC 61966-2-1 sRGB (with matrix_coefficients equal to 0)
IEC 61966-2-1 sYCC (with matrix_coefficients equal to 5) | +| 14 | $V = \alpha * L_c^{0.45} - (\alpha - 1)$ for $1 \geq L_c \geq \beta$
$V = 4.500 * L_c$ for $\beta > L_c \geq 0$ | Rec. ITU-R BT.2020-2 (10 bit system) (functionally the same as the values 1, 6, and 15) | +| 15 | $V = \alpha * L_c^{0.45} - (\alpha - 1)$ for $1 \geq L_c \geq \beta$
$V = 4.500 * L_c$ for $\beta > L_c \geq 0$ | Rec. ITU-R BT.2020-2 (12 bit system) (functionally the same as the values 1, 6, and 15) | +| 16 | $V = ((c_1 + c_2 * L_o^n) \div (1 + c_3 * L_o^n))^m$ for all values of $L_o$
$c_1 = c_3 - c_2 + 1 = 107 \div 128 = 0.8359375$
$c_2 = 2413 \div 128 = 18.8515625$
$c_3 = 2392 \div 128 = 18.6875$
$m = 2523 \div 32 = 78.84375$
$n = 1305 \div 8192 = 0.1593017578125$
for which $L_o$ equal to 1 for peak white is ordinarily intended to correspond to a reference output luminance level of 10 000 candelas per square metre | Society of Motion Picture and Television Engineers ST 2084 for 10, 12, 14, and 16-bit systems (2014)
Rec. ITU-R BT.2100-2 perceptual quantization (PQ) system | + +| | | | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| 17 | $V = ( 48 * L_o \div 52.37 ) ( 1 \div 2.6 )$ for all values of $L_o$
for which $L_o$ equal to 1 for peak white is ordinarily intended to correspond to a reference output luminance level of 48 candelas per square metre | Society of Motion Picture and Television Engineers ST 428-1 (2006) | +| 18 | $V = a * \text{Ln} ( 12 * L_c - b ) + c$ for $1 \geq L_c > 1 \div 12$
$V = \text{Sqrt} ( 3 ) * L_c^{0.5}$ for $1 \div 12 \geq L_c \geq 0$
$a = 0.17883277$
$b = 0.28466892$
$c = 0.55991073$ | Association of Radio Industries and Businesses (ARIB) STD-B67
Rec. ITU-R BT.2100-2 hybrid log-gamma (HLG) system | +| 19..255 | Reserved | For future use by ITU-T ISO/IEC | + +NOTE 4 – For transfer\_characteristics equal to 18, the equations given in Table E-4 are normalized for a source input linear optical intensity $L_c$ with a nominal real-valued range of 0 to 1. An alternative scaling that is mathematically equivalent is used in ARIB STD-B67 with the source input linear optical intensity having a nominal real-valued range of 0 to 12. + +**matrix\_coefficients** describes the matrix coefficients used in deriving luma and chroma signals from the green, blue, and red, or Y, Z, and X primaries, as specified in Table E-5. + +matrix\_coefficients shall not be equal to 0, 16, or 17 unless both of the following conditions are true: + +- BitDepthC is equal to BitDepthY, +- chroma\_format\_idc is equal to 3 (4:4:4). + +The specification of the use of matrix\_coefficients equal to 0, 16, or 17 under all other conditions is reserved for future use by ITU-T | ISO/IEC. + +matrix\_coefficients shall not be equal to 8 unless one of the following conditions is true: + +- BitDepthC is equal to BitDepthY, +- BitDepthC is equal to BitDepthY + 1 and chroma\_format\_idc is equal to 3 (4:4:4). + +The specification of the use of matrix\_coefficients equal to 8 under all other conditions is reserved for future use by ITU-T | ISO/IEC. + +When the matrix\_coefficients syntax element is not present, the value of matrix\_coefficients is inferred to be equal to 2 (unspecified). + +The interpretation of matrix\_coefficients, together with colour\_primaries and transfer\_characteristics, is specified by the equations below. + +NOTE 5 – For purposes of YZX representation when matrix\_coefficients is equal to 0, the symbols R, G, and B would be substituted for X, Y, and Z, respectively, in the following descriptions of Equations E-1 to E-3, E-20 to E-22, E-26 to E-28, and E-38 to E-40. + +$E_R$ , $E_G$ , and $E_B$ are defined as "linear-domain" real-valued signals based on the indicated colour primaries before application of the transfer characteristics function. + +Nominal white is specified as having $E_R$ equal to 1, $E_G$ equal to 1, and $E_B$ equal to 1. + +Nominal black is specified as having $E_R$ equal to 0, $E_G$ equal to 0, and $E_B$ equal to 0. + +The application of the transfer characteristics function is denoted by $( x )'$ for an argument $x$ . + +- If matrix\_coefficients is not equal to 14 or 15, the signals $E'_R$ , $E'_G$ , and $E'_B$ are determined by application of the transfer characteristics function as follows: + +$$E'_R = ( E_R )' \tag{E-1}$$ + +$$E'_G = ( E_G )' \tag{E-2}$$ + +$$E'_B = ( E_B )' \tag{E-3}$$ + +In this case, the range of $E'_R$ , $E'_G$ , and $E'_B$ is specified as follows: + +- If transfer\_characteristics is equal to 11 or 12, or transfer\_characteristics is equal to 13 and matrix\_coefficients is not equal to 0, $E'_R$ , $E'_G$ , and $E'_B$ are real numbers with values that have a larger range than the range of 0 to 1, and their range is not specified in this Specification. + +- Otherwise, $E'_R$ , $E'_G$ , and $E'_B$ are real numbers with values in the range of 0 to 1. +- Otherwise (matrix\_coefficients is equal to 14 or 15), the signals $E'_L$ , $E'_M$ , and $E'_S$ are determined by the following ordered steps: + +a) The "linear-domain" real-valued signals $E_L$ , $E_M$ , and $E_S$ are determined as follows: + +- If matrix\_coefficients is equal to 14, the signals $E_L$ , $E_M$ , and $E_S$ are determined as follows: + +$$E_L = ( 1688 * E_R + 2146 * E_G + 262 * E_B ) \div 4096 \quad (E-4)$$ + +$$E_M = ( 683 * E_R + 2951 * E_G + 462 * E_B ) \div 4096 \quad (E-5)$$ + +$$E_S = ( 99 * E_R + 309 * E_G + 3688 * E_B ) \div 4096 \quad (E-6)$$ + +- Otherwise (matrix\_coefficients is equal to 15), the signals $E_L$ , $E_M$ , and $E_S$ are determined as follows: + +$$E_L = ( 1747 * E_R + 2169 * E_G + 180 * E_B ) \div 4096 \quad (E-7)$$ + +$$E_M = ( 673 * E_R + 3029 * E_G + 394 * E_B ) \div 4096 \quad (E-8)$$ + +$$E_S = ( 50 * E_R + 207 * E_G + 3839 * E_B ) \div 4096 \quad (E-9)$$ + +b) The signals $E'_L$ , $E'_M$ , and $E'_S$ are determined by application of the transfer characteristics function as follows: + +$$E'_L = ( E_L )' \quad (E-10)$$ + +$$E'_M = ( E_M )' \quad (E-11)$$ + +$$E'_S = ( E_S )' \quad (E-12)$$ + +When matrix\_coefficients is equal to 0, 8, 16, or 17, the variables bitDepthRGB and maxValRGB are derived as follows: + +a) The variable bitDepthRGB is derived as follows: + +- If matrix\_coefficients is equal to 0 or 8, the following applies: + +$$\text{bitDepth}_{\text{RGB}} = \text{BitDepth}_Y \quad (E-13)$$ + +- Otherwise, if matrix\_coefficients is equal to 16, the following applies: + +$$\text{bitDepth}_{\text{RGB}} = \text{BitDepth}_Y - 2 \quad (E-14)$$ + +- Otherwise (matrix\_coefficients is equal to 17), the following applies: + +$$\text{bitDepth}_{\text{RGB}} = \text{BitDepth}_Y - 1 \quad (E-15)$$ + +b) The variable maxValRGB is derived as follows: + +$$\text{maxVal}_{\text{RGB}} = ( 1 \ll \text{bitDepth}_{\text{RGB}} ) - 1 \quad (E-16)$$ + +The interpretation of matrix\_coefficients is specified as follows: + +- If video\_full\_range\_flag is equal to 0, the following applies: + +- If matrix\_coefficients is equal to 1, 4, 5, 6, 7, 9, 10, 11, 12, 13, 14, or 15 the following equations apply: + +$$Y = \text{Clip1}_Y( \text{Round}( ( 1 \ll ( \text{BitDepth}_Y - 8 ) ) * ( 219 * E'_Y + 16 ) ) ) \quad (E-17)$$ + +$$C_b = \text{Clip1}_C( \text{Round}( ( 1 \ll ( \text{BitDepth}_C - 8 ) ) * ( 224 * E'_{PB} + 128 ) ) ) \quad (E-18)$$ + +$$C_r = \text{Clip1}_C( \text{Round}( ( 1 \ll ( \text{BitDepth}_C - 8 ) ) * ( 224 * E'_{PR} + 128 ) ) ) \quad (E-19)$$ + +- Otherwise, if matrix\_coefficients is equal to 0, 8, 16, or 17, the following equations apply: + +$$R = \text{Clip3}( 0, \text{maxVal}_{\text{RGB}}, ( 1 \ll ( \text{bitDepth}_{\text{RGB}} - 8 ) ) * ( 219 * E'_R + 16 ) ) \quad (E-20)$$ + +$$G = \text{Clip3}( 0, \text{maxVal}_{\text{RGB}}, ( 1 \ll ( \text{bitDepth}_{\text{RGB}} - 8 ) ) * ( 219 * E'_G + 16 ) ) \quad (E-21)$$ + +$$B = \text{Clip3}(0, \text{maxVal}_{\text{RGB}}, (1 \ll (\text{bitDepth}_{\text{RGB}} - 8)) * (219 * E'_B + 16)) \quad (\text{E-22})$$ + +- Otherwise, if $\text{matrix\_coefficients}$ is equal to 2, the interpretation of the $\text{matrix\_coefficients}$ syntax element is unknown or is determined by the application. +- Otherwise ( $\text{matrix\_coefficients}$ is not equal to 0, 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, or 17), the interpretation of the $\text{matrix\_coefficients}$ syntax element is reserved for future definition by ITU-T | ISO/IEC. +- Otherwise ( $\text{video\_full\_range\_flag}$ is equal to 1), the following applies: + - If $\text{matrix\_coefficients}$ is equal to 1, 4, 5, 6, 7, 9, 10, 11, 12, 13, 14, or 15, the following equations apply: + +$$Y = \text{Clip1}_Y(\text{Round}((1 \ll \text{BitDepth}_Y - 1) * E'_Y)) \quad (\text{E-23})$$ + +$$Cb = \text{Clip1}_C(\text{Round}((1 \ll \text{BitDepth}_C - 1) * E'_{\text{PB}} + (1 \ll (\text{BitDepth}_C - 1)))) \quad (\text{E-24})$$ + +$$Cr = \text{Clip1}_C(\text{Round}((1 \ll \text{BitDepth}_C - 1) * E'_{\text{PR}} + (1 \ll (\text{BitDepth}_C - 1)))) \quad (\text{E-25})$$ + +- Otherwise, if $\text{matrix\_coefficients}$ is equal to 0, 8, 16, or 17, the following equations apply: + +$$R = \text{Clip3}(0, \text{maxVal}_{\text{RGB}}, \text{maxVal}_{\text{RGB}} * E'_R) \quad (\text{E-26})$$ + +$$G = \text{Clip3}(0, \text{maxVal}_{\text{RGB}}, \text{maxVal}_{\text{RGB}} * E'_G) \quad (\text{E-27})$$ + +$$B = \text{Clip3}(0, \text{maxVal}_{\text{RGB}}, \text{maxVal}_{\text{RGB}} * E'_B) \quad (\text{E-28})$$ + +- Otherwise, if $\text{matrix\_coefficients}$ is equal to 2, the interpretation of the $\text{matrix\_coefficients}$ syntax element is unknown or is determined by the application. +- Otherwise ( $\text{matrix\_coefficients}$ is not equal to 0, 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, or 17), the interpretation of the $\text{matrix\_coefficients}$ syntax element is reserved for future definition by ITU-T | ISO/IEC. + +Reserved values for $\text{matrix\_coefficients}$ shall not be present in bitstreams conforming to this version of this Specification. Decoders shall interpret reserved values of $\text{matrix\_coefficients}$ as equivalent to the value 2. + +It is a requirement of bitstream conformance to this version of this Specification that when $\text{colour\_primaries}$ is not equal to 1, 4, 5, 6, 7, 8, 9, 10, 11, 12, or 22, $\text{matrix\_coefficients}$ shall not be equal to 12 or 13. + +When $\text{matrix\_coefficients}$ is equal to 1, 4, 5, 6, 7, 9, 10, 11, 12, or 13, the constants $K_R$ and $K_B$ are specified as follows: + +- If $\text{matrix\_coefficients}$ is not equal to 12 or 13, the constants $K_R$ and $K_B$ are specified in Table E-5. +- Otherwise ( $\text{matrix\_coefficients}$ is equal to 12 or 13), the constants $K_R$ and $K_B$ are computed as follows, using the chromaticity coordinates $(x_R, y_R)$ , $(x_G, y_G)$ , $(x_B, y_B)$ , and $(x_W, y_W)$ specified by Table E-3 for the $\text{colour\_primaries}$ syntax element for the red, green, blue, and white colour primaries, respectively: + +$$K_R = \frac{y_R * (x_W * (y_G * z_B - y_B * z_G) + y_W * (x_B * z_G - x_G * z_B) + z_W * (x_G * y_B - x_B * y_G))}{y_W * (x_R * (y_G * z_B - y_B * z_G) + x_G * (y_B * z_R - y_R * z_B) + x_B * (y_R * z_G - y_G * z_R))} \quad (\text{E-29})$$ + +$$K_B = \frac{y_B * (x_W * (y_R * z_G - y_G * z_R) + y_W * (x_G * z_R - x_R * z_G) + z_W * (x_R * y_G - x_G * y_R))}{y_W * (x_R * (y_G * z_B - y_B * z_G) + x_G * (y_B * z_R - y_R * z_B) + x_B * (y_R * z_G - y_G * z_R))} \quad (\text{E-30})$$ + +where the values of $z_R$ , $z_G$ , $z_B$ , and $z_W$ , are given by: + +$$z_R = 1 - (x_R + y_R) \quad (\text{E-31})$$ + +$$z_G = 1 - (x_G + y_G) \quad (\text{E-32})$$ + +$$z_B = 1 - (x_B + y_B) \quad (\text{E-33})$$ + +$$z_W = 1 - (x_W + y_W) \quad (\text{E-34})$$ + +The variables $E'_Y$ , $E'_{\text{PB}}$ , and $E'_{\text{PR}}$ (for $\text{matrix\_coefficients}$ not equal to 0, 8, 16, or 17) or $Y$ , $Cb$ , and $Cr$ (for $\text{matrix\_coefficients}$ equal to 0, 8, 16, or 17) are specified as follows: + +- If $\text{matrix\_coefficients}$ is not equal to 0, 8, 10, 11, 13, 14, 15, 16, or 17, the following equations apply: + +$$E'_Y = K_R * E'_R + (1 - K_R - K_B) * E'_G + K_B * E'_B \quad (\text{E-35})$$ + +$$E'_{PB} = 0.5 * (E'_B - E'_Y) \div (1 - K_B) \quad (E-36)$$ + +$$E'_{PR} = 0.5 * (E'_R - E'_Y) \div (1 - K_R) \quad (E-37)$$ + +$E'_Y$ is a real number with the value 0 associated with nominal black and the value 1 associated with nominal white. $E'_{PB}$ and $E'_{PR}$ are real numbers with the value 0 associated with both nominal black and nominal white. When transfer\_characteristics is not equal to 11 or 12, $E'_Y$ is a real number with values in the range of 0 to 1. When transfer\_characteristics is not equal to 11 or 12, $E'_{PB}$ and $E'_{PR}$ are real numbers with values in the range of -0.5 to 0.5. When transfer\_characteristics is equal to 11, or 12, $E'_Y$ , $E'_{PB}$ and $E'_{PR}$ are real numbers with a larger range not specified in this Specification. + +- Otherwise, if matrix\_coefficients is equal to 0, the following equations apply: + +$$Y = \text{Round}(G) \quad (E-38)$$ + +$$Cb = \text{Round}(B) \quad (E-39)$$ + +$$Cr = \text{Round}(R) \quad (E-40)$$ + +- Otherwise, if matrix\_coefficients is equal to 8 and BitDepthC is equal to BitDepthY, the following applies: + +$$Y = \text{Round}(0.5 * G + 0.25 * (R + B)) \quad (E-41)$$ + +$$Cb = \text{Round}(0.5 * G - 0.25 * (R + B)) + (1 \ll (\text{BitDepth}_C - 1)) \quad (E-42)$$ + +$$Cr = \text{Round}(0.5 * (R - B)) + (1 \ll (\text{BitDepth}_C - 1)) \quad (E-43)$$ + +NOTE 6 – A problem has been reported with Equations E-41 to E-43, as it has been observed that the maximum value resulting from Equation E-42 or Equation E-43 can be equal to $(1 \ll \text{BitDepth}_C)$ , which exceeds the intended range of values for Cb and Cr. A small modification of these equations is likely to be introduced in a future version of this Specification to address the issue. + +NOTE 7 – In this case, for purposes of the YCbCr nomenclature used in Table E-5, Cb and Cr of Equations E-42 and E-43 would be referred to as Cg and Co, respectively. An appropriate inverse conversion for Equations E-41 to E-43 is as follows: + +$$t = Y - (Cb - (1 \ll (\text{BitDepth}_C - 1))) \quad (E-44)$$ + +$$G = \text{Clip1}_Y(Y + (Cb - (1 \ll (\text{BitDepth}_C - 1)))) \quad (E-45)$$ + +$$B = \text{Clip1}_Y(t - (Cr - (1 \ll (\text{BitDepth}_C - 1)))) \quad (E-46)$$ + +$$R = \text{Clip1}_Y(t + (Cr - (1 \ll (\text{BitDepth}_C - 1)))) \quad (E-47)$$ + +- Otherwise, if matrix\_coefficients is equal to 8, 16, or 17, the following equations apply: + +$$Cr = \text{Round}(R) - \text{Round}(B) + (1 \ll (\text{BitDepth}_C - 1)) \quad (E-48)$$ + +$$t = \text{Round}(B) + ((Cr - (1 \ll (\text{BitDepth}_C - 1))) \gg 1) \quad (E-49)$$ + +$$Cb = \text{Round}(G) - t + (1 \ll (\text{BitDepth}_C - 1)) \quad (E-50)$$ + +$$Y = t + ((Cb - (1 \ll (\text{BitDepth}_C - 1))) \gg 1) \quad (E-51)$$ + +NOTE 8 – In this case, for purposes of the YCbCr nomenclature used in Table E-5, Cb and Cr of Equations E-50 and E-48 would be referred to as Cg and Co, respectively. An appropriate inverse conversion for Equations E-48 to E-51 is as follows: + +$$t = Y - ((Cb - (1 \ll (\text{BitDepth}_C - 1))) \gg 1) \quad (E-52)$$ + +$$G = \text{Clip3}(0, \text{maxVal}_{\text{RGB}}, t + (Cb - (1 \ll (\text{BitDepth}_C - 1)))) \quad (E-53)$$ + +$$B = \text{Clip3}(0, \text{maxVal}_{\text{RGB}}, t - ((Cr - (1 \ll (\text{BitDepth}_C - 1))) \gg 1)) \quad (E-54)$$ + +$$R = \text{Clip3}(0, \text{maxVal}_{\text{RGB}}, B + (Cr - (1 \ll (\text{BitDepth}_C - 1)))) \quad (E-55)$$ + +- Otherwise, if matrix\_coefficients is equal to 10 or 13, the signal $E'_Y$ is determined by application of the transfer characteristics function as follows: + +$$E_Y = K_R * E_R + (1 - K_R - K_B) * E_G + K_B * E_B \quad (E-56)$$ + +$$E'_Y = (E_Y)' \quad (E-57)$$ + +In this case, $E_Y$ is defined from the "linear-domain" signals for $E_R$ , $E_G$ , and $E_B$ , prior to application of the transfer characteristics function, which is then applied to produce the signal $E'_Y$ . $E_Y$ and $E'_Y$ are real values with the value 0 associated with nominal black and the value 1 associated with nominal white. + +In this case, the signals $E'_{PB}$ and $E'_{PR}$ are determined as follows: + +$$E'_{PB} = (E'_B - E'_Y) \div (2 * N_B) \quad \text{for } -N_B \leq E'_B - E'_Y \leq 0 \quad (\text{E-58})$$ + +$$E'_{PB} = (E'_B - E'_Y) \div (2 * P_B) \quad \text{for } 0 < E'_B - E'_Y \leq P_B \quad (\text{E-59})$$ + +$$E'_{PR} = (E'_R - E'_Y) \div (2 * N_R) \quad \text{for } -N_R \leq E'_R - E'_Y \leq 0 \quad (\text{E-60})$$ + +$$E'_{PR} = (E'_R - E'_Y) \div (2 * P_R) \quad \text{for } 0 < E'_R - E'_Y \leq P_R \quad (\text{E-61})$$ + +where the constants $N_B$ , $P_B$ , $N_R$ , and $P_R$ are determined by application of the transfer characteristics function to expressions involving the constants $K_B$ and $K_R$ as follows: + +$$N_B = (1 - K_B)' \quad (\text{E-62})$$ + +$$P_B = 1 - (K_B)' \quad (\text{E-63})$$ + +$$N_R = (1 - K_R)' \quad (\text{E-64})$$ + +$$P_R = 1 - (K_R)' \quad (\text{E-65})$$ + +– Otherwise, if matrix\_coefficients is equal to 11, the following equations apply: + +$$E'_Y = E'_G \quad (\text{E-66})$$ + +$$E'_{PB} = (0.986566 * E'_B - E'_Y) \div 2 \quad (\text{E-67})$$ + +$$E'_{PR} = (E'_R - 0.991902 * E'_Y) \div 2 \quad (\text{E-68})$$ + +NOTE 9 – In this case, for purposes of the $Y'D'Z'D'X$ nomenclature used in Table E-5, $E'_{PB}$ and $E'_{PR}$ of Equations E-67 and E-68 would be referred to as $D'_Z$ and $D'_X$ , respectively. + +– Otherwise, if matrix\_coefficients is equal to 14, the following applies: + +– If transfer\_characteristics is not equal to 18, the following equations apply: + +$$E'_Y = 0.5 * (E'_L + E'_M) \quad (\text{E-69})$$ + +$$E'_{PB} = (6610 * E'_L - 13613 * E'_M + 7003 * E'_S) \div 4096 \quad (\text{E-70})$$ + +$$E'_{PR} = (17933 * E'_L - 17390 * E'_M - 543 * E'_S) \div 4096 \quad (\text{E-71})$$ + +– Otherwise, the following equations apply: + +$$E'_Y = 0.5 * (E'_L + E'_M) \quad (\text{E-72})$$ + +$$E'_{PB} = (3625 * E'_L - 7465 * E'_M + 3840 * E'_S) \div 4096 \quad (\text{E-73})$$ + +$$E'_{PR} = (9500 * E'_L - 9212 * E'_M - 288 * E'_S) \div 4096 \quad (\text{E-74})$$ + +NOTE 10 – In this case, for purposes of the $IC_T C_P$ nomenclature used in Table E-5, $E'_Y$ , $E'_{PB}$ , and $E'_{PR}$ of Equations E-69, E-70, and E-71 may be referred to as $I$ , $C_T$ , and $C_P$ , respectively. Equations E-69 through E-71 were designed specifically for use with transfer\_characteristics equal to 16 (PQ), and Equations E-72 through E-74 were designed specifically for use with transfer\_characteristics equal to 18 (HLG). + +– Otherwise (matrix\_coefficients is equal to 15), the following applies: + +$$E'_Y = (1638 * E'_L + 1638 * E'_M + 820 * E'_S) \div 4096 \quad (\text{E-75})$$ + +$$E'_{PB} = (18248 * E'_L - 19870 * E'_M + 1622 * E'_S) \div 4096 \quad (\text{E-76})$$ + +$$E'_{PR} = (3300 * E'_L + 1463 * E'_M - 4763 * E'_S) \div 4096 \quad (\text{E-77})$$ + +NOTE 11 – In this case, for purposes of the IPT-C2 nomenclature used in Table E-5, $E'_Y$ , $E'_{PB}$ , and $E'_{PR}$ of Equations E-75, E-76, and E-77 may be referred to as $I$ , $P$ , and $T$ , respectively. + +**Table E-5 – Matrix coefficients interpretation using the matrix\_coefficients syntax element** + +| Value | Matrix | Informative remark | +|-------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | GBR | The identity matrix.
Typically used for GBR (often referred to as RGB); however, may also be used for YZX (often referred to as XYZ)
IEC 61966-2-1 (sRGB)
Society of Motion Picture and Television Engineers ST 428-1 XYZ (2006)
See Equations E-1 to E-3 | +| 1 | $K_R = 0.2126; K_B = 0.0722$ | Rec. ITU-R BT.709-6
Rec. ITU-R BT.1361-0 conventional colour gamut system and extended colour gamut system (historical)
IEC 61966-2-4 xvYCC 709
Society of Motion Picture and Television Engineers RP 177 (1993)
Annex B
See Equations E-35 to E-37 | +| 2 | Unspecified | Image characteristics are unknown or are determined by the application. | +| 3 | Reserved | For future use by ITU-T ISO/IEC | +| 4 | $K_R = 0.30; K_B = 0.11$ | United States Federal Communications Commission Title 47 Code of Federal Regulations (2016) 73.682 (a) (20)
See Equations E-35 to E-37 | +| 5 | $K_R = 0.299; K_B = 0.114$ | Rec. ITU-R BT.470-7 System B, G (historical)
Rec. ITU-R BT.601-7 625
Rec. ITU-R BT.1358-0 625 (historical)
Rec. ITU-R BT.1700-0 625 PAL and 625 SECAM
IEC 61966-2-1 (sYCC)
IEC 61966-2-4 xvYCC 601
(functionally the same as the value 6)
See Equations E-35 to E-37 | +| 6 | $K_R = 0.299; K_B = 0.114$ | Rec. ITU-R BT.601-7 525
Rec. ITU-R BT.1358-1 525 or 625
Rec. ITU-R BT.1700-0 NTSC
Society of Motion Picture and Television Engineers 170M (2004)
(functionally the same as the value 5)
See Equations E-35 to E-37 | +| 7 | $K_R = 0.212; K_B = 0.087$ | Society of Motion Picture and Television Engineers 240M (1999, historical)
See Equations E-35 to E-37 | +| 8 | YCgCo or YCgCo-R | See Equations E-41 to E-47 for YCgCo (when BitDepth C is equal to BitDepth Y )
See Equations E-48 to E-55 for YCgCo-R (when BitDepth C is equal to BitDepth Y + 1) | +| 9 | $K_R = 0.2627; K_B = 0.0593$ | Rec. ITU-R BT.2020-2 non-constant luminance system
Rec. ITU-R BT.2100-2 Y'CbCr
See Equations E-35 to E-37 | +| 10 | $K_R = 0.2627; K_B = 0.0593$ | Rec. ITU-R BT.2020-2 constant luminance system
See Equations E-56 to E-65 | +| 11 | $Y'D'Z'D'_X$ | Society of Motion Picture and Television Engineers ST 2085 (2015)
See Equations E-66 to E-68 | +| 12 | See Equations E-29 to E-34. | Chromaticity-derived non-constant luminance system
See Equations E-35 to E-37. | +| 13 | See Equations E-29 to E-34. | Chromaticity-derived constant luminance system
See Equations E-56 to E-65. | +| 14 | $IC_T C_P$ | Rec. ITU-R BT.2100-2 $IC_T C_P$
See Equations E-69 to E-71. for transfer_characteristics value 16 (PQ)
See Equations E-72 to E-74 for transfer_characteristics value 18 (HLG) | + +| | | | +|---------|----------|--------------------------------------------------------------------------------------| +| 15 | IPT-C2 | Colour representation developed in SMPTE as IPT-PQ-C2.
See Equations E-75 to E-77 | +| 16 | YCGCo-Re | See Equations E-48 to E-55 | +| 17 | YCGCo-Ro | See Equations E-48 to E-55 | +| 18..255 | Reserved | For future use by ITU-T ISO/IEC | + +**chroma\_loc\_info\_present\_flag** equal to 1 specifies that **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** are present. **chroma\_loc\_info\_present\_flag** equal to 0 specifies that **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** are not present. + +When **chroma\_format\_idc** is not equal to 1, **chroma\_loc\_info\_present\_flag** should be equal to 0. + +**chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** specify the location of chroma samples as follows: + +- If **chroma\_format\_idc** is equal to 1 (4:2:0 chroma format), **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** specify the location of chroma samples for the top field and the bottom field, respectively, as shown in Figure E-1. +- Otherwise (**chroma\_format\_idc** is not equal to 1), the values of the syntax elements **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** shall be ignored. When **chroma\_format\_idc** is equal to 2 (4:2:2 chroma format) or 3 (4:4:4 chroma format), the location of chroma samples is specified in clause 6.2. When **chroma\_format\_idc** is equal to 0, there is no chroma sample array. + +The value of **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** shall be in the range of 0 to 5, inclusive. When the **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** are not present, the values of **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** shall be inferred to be equal to 0. + +NOTE 12 – When coding progressive-scan source material, the syntax elements **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** should have the same value. + +![Figure E-1: Location of chroma samples for top and bottom fields for chroma_format_idc equal to 1 (4:2:0 chroma format) as a function of chroma_sample_loc_type_top_field and chroma_sample_loc_type_bottom_field. The diagram shows four rows of sample positions. Each row contains four groups of symbols: 'X 0 X' followed by an ellipsis. Below each 'X 0 X' group are two rows of symbols: a circle with a triangle (top field) and a square with a triangle (bottom field). The first row shows white circle/triangle and square/triangle. The second row shows grey circle/triangle and square/triangle. The third row shows white circle/triangle and square/triangle. The fourth row shows grey circle/triangle and square/triangle. A vertical ellipsis is at the bottom left, and 'H.264(09)_FE-1' is at the bottom right.](24ca424ca19ebeeafb6a9249dcd7bcfa_img.jpg) + +Figure E-1: Location of chroma samples for top and bottom fields for chroma\_format\_idc equal to 1 (4:2:0 chroma format) as a function of chroma\_sample\_loc\_type\_top\_field and chroma\_sample\_loc\_type\_bottom\_field. The diagram shows four rows of sample positions. Each row contains four groups of symbols: 'X 0 X' followed by an ellipsis. Below each 'X 0 X' group are two rows of symbols: a circle with a triangle (top field) and a square with a triangle (bottom field). The first row shows white circle/triangle and square/triangle. The second row shows grey circle/triangle and square/triangle. The third row shows white circle/triangle and square/triangle. The fourth row shows grey circle/triangle and square/triangle. A vertical ellipsis is at the bottom left, and 'H.264(09)\_FE-1' is at the bottom right. + +**Interpretation of symbols** + +Luma sample position indications: + +X Luma sample top field                      □ Luma sample bottom field + +Chroma sample position indications, where grey fill indicates a bottom field sample type and no fill indicates a top field sample type: + +| | | +|------------------------|------------------------| +| ○ Chroma sample type 2 | ⬮ Chroma sample type 3 | +| ○ Chroma sample type 0 | ▼ Chroma sample type 1 | +| ◇ Chroma sample type 4 | △ Chroma sample type 5 | + +**Figure E-1 – Location of chroma samples for top and bottom fields for chroma\_format\_idc equal to 1 (4:2:0 chroma format) as a function of chroma\_sample\_loc\_type\_top\_field and chroma\_sample\_loc\_type\_bottom\_field** + +**timing\_info\_present\_flag** equal to 1 specifies that num\_units\_in\_tick, time\_scale and fixed\_frame\_rate\_flag are present in the bitstream. timing\_info\_present\_flag equal to 0 specifies that num\_units\_in\_tick, time\_scale and fixed\_frame\_rate\_flag are not present in the bitstream. + +**num\_units\_in\_tick** is the number of time units of a clock operating at the frequency time\_scale Hz that corresponds to one increment (called a clock tick) of a clock tick counter. num\_units\_in\_tick shall be greater than 0. A clock tick is the minimum interval of time that can be represented in the coded data. For example, when the frame rate of a video signal is 30 000 ÷ 1001 Hz, time\_scale may be equal to 60 000 and num\_units\_in\_tick may be equal to 1001. See Equation C-1. + +**time\_scale** is the number of time units that pass in one second. For example, a time coordinate system that measures time using a 27 MHz clock has a time\_scale of 27 000 000. time\_scale shall be greater than 0. + +**fixed\_frame\_rate\_flag** equal to 1 indicates that the temporal distance between the HRD output times of any two consecutive pictures in output order is constrained as follows. fixed\_frame\_rate\_flag equal to 0 indicates that no such constraints apply to the temporal distance between the HRD output times of any two consecutive pictures in output order. + +When fixed\_frame\_rate\_flag is not present, it shall be inferred to be equal to 0. + +For each picture n where n indicates the n-th picture (in output order) that is output and picture n is not the last picture in the bitstream (in output order) that is output, the value of Δtfi,dpb( n ) is specified by + +$$\Delta t_{fi,dpb}( n ) = \Delta t_{o,dpb}( n ) \div \text{DeltaTfiDivisor} \quad (\text{E-78})$$ + +where $\Delta t_{o,dpb}(n)$ is specified in Equation C-13 and $\Delta t_{fi,dpb}$ is specified by Table E-6 based on the value of `pic_struct_present_flag`, `field_pic_flag`, and `pic_struct` for the coded video sequence containing picture $n$ . Entries marked "-" in Table E-6 indicate a lack of dependence of $\Delta t_{fi,dpb}$ on the corresponding syntax element. + +When `fixed_frame_rate_flag` is equal to 1 for a coded video sequence containing picture $n$ , the value computed for $\Delta t_{fi,dpb}(n)$ shall be equal to $t_c$ as specified in Equation C-1 (using the value of $t_c$ for the coded video sequence containing picture $n$ ) when either or both of the following conditions are true for the following picture $n_n$ that is specified for use in Equation C-13: + +- picture $n_n$ is in the same coded video sequence as picture $n$ . +- picture $n_n$ is in a different coded video sequence and `fixed_frame_rate_flag` is equal to 1 in the coded video sequence containing picture $n_n$ and the value of $\text{num\_units\_in\_tick} \div \text{time\_scale}$ is the same for both coded video sequences. + +**Table E-6 – Divisor for computation of $\Delta t_{fi,dpb}(n)$** + +| pic_struct_present_flag | field_pic_flag | pic_struct | DeltaTfiDivisor | +|--------------------------------------|-----------------------------|-------------------------|------------------------------| +| 0 | 1 | - | 1 | +| 1 | - | 1 | 1 | +| 1 | - | 2 | 1 | +| 0 | 0 | - | 2 | +| 1 | - | 0 | 2 | +| 1 | - | 3 | 2 | +| 1 | - | 4 | 2 | +| 1 | - | 5 | 3 | +| 1 | - | 6 | 3 | +| 1 | - | 7 | 4 | +| 1 | - | 8 | 6 | + +NOTE 13 – In order to produce a $\Delta t_{fi,dpb}$ other than 2 for a picture with `field_pic_flag` equal to 0, `pic_struct_present_flag` must be equal to 1. + +**`nal_hrd_parameters_present_flag`** equal to 1 specifies that NAL HRD parameters (pertaining to the Type II bitstream conformance point) are present. `nal_hrd_parameters_present_flag` equal to 0 specifies that NAL HRD parameters are not present. + +NOTE 14 – When `nal_hrd_parameters_present_flag` is equal to 0, the conformance of the bitstream cannot be verified without provision of the NAL HRD parameters and all buffering period SEI messages, and, when `vcl_hrd_parameters_present_flag` is also equal to 0, all picture timing SEI messages, by some means not specified in this Recommendation | International Standard. + +When `nal_hrd_parameters_present_flag` is equal to 1, NAL HRD parameters (clauses E.1.2 and E.2.2) immediately follow the flag. + +The variable `NalHrdBpPresentFlag` is derived as follows: + +- If any of the following is true, the value of `NalHrdBpPresentFlag` shall be set equal to 1: + - `nal_hrd_parameters_present_flag` is present in the bitstream and is equal to 1, + - the need for presence of buffering periods for NAL HRD operation to be present in the bitstream in buffering period SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of `NalHrdBpPresentFlag` shall be set equal to 0. + +**`vcl_hrd_parameters_present_flag`** equal to 1 specifies that VCL HRD parameters (pertaining to the Type I bitstream conformance point) are present. `vcl_hrd_parameters_present_flag` equal to 0 specifies that VCL HRD parameters are not present. + +NOTE 15 – When `vcl_hrd_parameters_present_flag` is equal to 0, the conformance of the bitstream cannot be verified without provision of the VCL HRD parameters and all buffering period SEI messages and, when `nal_hrd_parameters_present_flag` is also equal to 0, all picture timing SEI messages, by some means not specified in this Recommendation | International Standard. + +When `vcl_hrd_parameters_present_flag` is equal to 1, VCL HRD parameters (clauses E.1.2 and E.2.2) immediately follow the flag. + +The variable `VclHrdBpPresentFlag` is derived as follows: + +- If any of the following is true, the value of VclHrdBpPresentFlag shall be set equal to 1: + - `vc1_hrd_parameters_present_flag` is present in the bitstream and is equal to 1, + - the need for presence of buffering period parameters for VCL HRD operation in the bitstream in buffering period SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of VclHrdBpPresentFlag shall be set equal to 0. + +The variable CpbDpbDelaysPresentFlag is derived as follows: + +- If any of the following is true, the value of CpbDpbDelaysPresentFlag shall be set equal to 1: + - `nal_hrd_parameters_present_flag` is present in the bitstream and is equal to 1, + - `vc1_hrd_parameters_present_flag` is present in the bitstream and is equal to 1, + - the need for presence of CPB and DPB output delays in the bitstream in picture timing SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of CpbDpbDelaysPresentFlag shall be set equal to 0. + +**low\_delay\_hrd\_flag** specifies the HRD operational mode as specified in Annex C. When `fixed_frame_rate_flag` is equal to 1, `low_delay_hrd_flag` shall be equal to 0. When `low_delay_hrd_flag` is not present, its value shall be inferred to be equal to 1 – `fixed_frame_rate_flag`. + +NOTE 16 – When `low_delay_hrd_flag` is equal to 1, "big pictures" that violate the nominal CPB removal times due to the number of bits used by an access unit are permitted. It is expected, but not required, that such "big pictures" occur only occasionally. + +**pic\_struct\_present\_flag** equal to 1 specifies that picture timing SEI messages (clause D.2.3) are present that include the `pic_struct` syntax element. `pic_struct_present_flag` equal to 0 specifies that the `pic_struct` syntax element is not present in picture timing SEI messages. When `pic_struct_present_flag` is not present, its value shall be inferred to be equal to 0. + +**bitstream\_restriction\_flag** equal to 1, specifies that the following coded video sequence bitstream restriction parameters are present. `bitstream_restriction_flag` equal to 0, specifies that the following coded video sequence bitstream restriction parameters are not present. + +**motion\_vectors\_over\_pic\_boundaries\_flag** equal to 0 indicates that no sample outside the picture boundaries and no sample at a fractional sample position for which the sample value is derived using one or more samples outside the picture boundaries is used for inter prediction of any sample. `motion_vectors_over_pic_boundaries_flag` equal to 1 indicates that one or more samples outside picture boundaries may be used in inter prediction. When the `motion_vectors_over_pic_boundaries_flag` syntax element is not present, `motion_vectors_over_pic_boundaries_flag` value shall be inferred to be equal to 1. + +**max\_bytes\_per\_pic\_denom** indicates a number of bytes not exceeded by the sum of the sizes of the VCL NAL units associated with any coded picture in the coded video sequence. + +The number of bytes that represent a picture in the NAL unit stream is specified for this purpose as the total number of bytes of VCL NAL unit data (i.e., the total of the NumBytesInNALUnit variables for the VCL NAL units) for the picture. The value of `max_bytes_per_pic_denom` shall be in the range of 0 to 16, inclusive. + +Depending on `max_bytes_per_pic_denom` the following applies: + +- If `max_bytes_per_pic_denom` is equal to 0, no limits are indicated. +- Otherwise (`max_bytes_per_pic_denom` is not equal to 0), it is a requirement of bitstream conformance that no coded picture shall be represented in the coded video sequence by more than the following number of bytes. + +$$( \text{PicSizeInMbs} * \text{RawMbBits} ) \div ( 8 * \text{max\_bytes\_per\_pic\_denom} ) \quad (\text{E-79})$$ + +When the `max_bytes_per_pic_denom` syntax element is not present, the value of `max_bytes_per_pic_denom` shall be inferred to be equal to 2. + +**max\_bits\_per\_mb\_denom** indicates an upper bound for the number of coded bits of `macroblock_layer()` data for any macroblock in any picture of the coded video sequence. The value of `max_bits_per_mb_denom` shall be in the range of 0 to 16, inclusive. + +Depending on `max_bits_per_mb_denom` the following applies: + +- If `max_bits_per_mb_denom` is equal to 0, no limit is specified by this syntax element. +- Otherwise (`max_bits_per_mb_denom` is not equal to 0), it is a requirement of bitstream conformance that no coded macroblock\_layer() shall be represented in the bitstream by more than the following number of bits. + +$$(128 + \text{RawMbBits}) \div \text{max\_bits\_per\_mb\_denom}$$ + +(E-80) + +Depending on `entropy_coding_mode_flag`, the bits of `macroblock_layer()` data are counted as follows: + +- If `entropy_coding_mode_flag` is equal to 0, the number of bits of `macroblock_layer()` data is given by the number of bits in the `macroblock_layer()` syntax structure for a macroblock. +- Otherwise (`entropy_coding_mode_flag` is equal to 1), the number of bits of `macroblock_layer()` data for a macroblock is given by the number of times `read_bits( 1 )` is called in clauses 9.3.3.2.2 and 9.3.3.2.3 when parsing the `macroblock_layer()` associated with the macroblock. + +When the `max_bits_per_mb_denom` is not present, the value of `max_bits_per_mb_denom` shall be inferred to be equal to 1. + +**`log2_max_mv_length_horizontal`** and **`log2_max_mv_length_vertical`** indicate the value range of a decoded horizontal and vertical motion vector component, respectively, in $\frac{1}{4}$ luma sample units, for all pictures in the coded video sequence. A value of $n$ asserts that no value of a motion vector component shall exceed the range from $-2^n$ to $2^n - 1$ , inclusive, in units of $\frac{1}{4}$ luma sample displacement. The value of `log2_max_mv_length_horizontal` shall be in the range of 0 to 15, inclusive. The value of `log2_max_mv_length_vertical` shall be in the range of 0 to 15, inclusive. When `log2_max_mv_length_horizontal` is not present, the values of `log2_max_mv_length_horizontal` and `log2_max_mv_length_vertical` shall be inferred to be equal to 15. + +NOTE 17 – The value range of a decoded vertical or horizontal motion vector component is also constrained by profile and level limits as specified in Annex A and clauses F.10 and G.10. + +For bitstreams of levels 6, 6.1, and 6.2 (see Annex A), it has been reported that some decoder implementations do not properly decode bitstreams that have horizontal motion vector component values that exceed the range from $-2048$ to $2047$ , inclusive, or that have vertical motion vector component values that exceed the range from $-512$ to $511$ , inclusive, in units of $\frac{1}{4}$ luma sample displacement. It is therefore suggested that bitstreams should not contain motion vector component values that exceed these ranges. This constraint can be indicated by using values of `log2_max_mv_length_horizontal` less than or equal to 11 and values of `log2_max_mv_length_vertical` less than or equal to 9. + +**`max_num_reorder_frames`** indicates an upper bound for the number of frames buffers, in the decoded picture buffer (DPB), that are required for storing frames, complementary field pairs, and non-paired fields before output. It is a requirement of bitstream conformance that the maximum number of frames, complementary field pairs, or non-paired fields that precede any frame, complementary field pair, or non-paired field in the coded video sequence in decoding order and follow it in output order shall be less than or equal to `max_num_reorder_frames`. The value of `max_num_reorder_frames` shall be in the range of 0 to `max_dec_frame_buffering`, inclusive. When the `max_num_reorder_frames` syntax element is not present, the value of `max_num_reorder_frames` value shall be inferred as follows: + +- If `profile_idc` is equal to 44, 86, 100, 110, 122, or 244 and `constraint_set3_flag` is equal to 1, the value of `max_num_reorder_frames` shall be inferred to be equal to 0. +- Otherwise (`profile_idc` is not equal to 44, 86, 100, 110, 122, or 244 or `constraint_set3_flag` is equal to 0), the value of `max_num_reorder_frames` shall be inferred to be equal to `MaxDpbFrames`. + +**`max_dec_frame_buffering`** specifies the required size of the HRD decoded picture buffer (DPB) in units of frame buffers. It is a requirement of bitstream conformance that the coded video sequence shall not require a decoded picture buffer with size of more than $\text{Max}( 1, \text{max\_dec\_frame\_buffering} )$ frame buffers to enable the output of decoded pictures at the output times specified by `dpb_output_delay` of the picture timing SEI messages. The value of `max_dec_frame_buffering` shall be greater than or equal to `max_num_ref_frames`. An upper bound for the value of `max_dec_frame_buffering` is specified by the level limits in clauses A.3.1, A.3.2, F.10.2.1, and G.10.2. + +When the `max_dec_frame_buffering` syntax element is not present, the value of `max_dec_frame_buffering` shall be inferred as follows: + +- If `profile_idc` is equal to 44, 86, 100, 110, 122, or 244 and `constraint_set3_flag` is equal to 1, the value of `max_dec_frame_buffering` shall be inferred to be equal to 0. +- Otherwise (`profile_idc` is not equal to 44, 86, 100, 110, 122, or 244 or `constraint_set3_flag` is equal to 0), the value of `max_dec_frame_buffering` shall be inferred to be equal to `MaxDpbFrames`. + +## E.2.2 HRD parameters semantics + +The syntax category of the HRD parameters syntax structure shall be inferred as follows: + +- If the HRD parameters syntax structure is not part of an SEI message, the syntax category of the HRD parameters syntax structure is inferred to be equal to 0. + +- Otherwise (the HRD parameters syntax structure is part of the base layer temporal HRD SEI message as specified in clause F.13 or the base view temporal HRD SEI message as specified in clause G.13), the syntax category of the HRD parameters syntax structure is inferred to be equal to 5. + +**cpb\_cnt\_minus1** plus 1 specifies the number of alternative CPB specifications in the bitstream. The value of **cpb\_cnt\_minus1** shall be in the range of 0 to 31, inclusive. When **low\_delay\_hrd\_flag** is equal to 1, **cpb\_cnt\_minus1** shall be equal to 0. When **cpb\_cnt\_minus1** is not present, it shall be inferred to be equal to 0. + +**bit\_rate\_scale** (together with **bit\_rate\_value\_minus1[ SchedSelIdx ]**) specifies the maximum input bit rate of the SchedSelIdx-th CPB. + +**cpb\_size\_scale** (together with **cpb\_size\_value\_minus1[ SchedSelIdx ]**) specifies the CPB size of the SchedSelIdx-th CPB. + +**bit\_rate\_value\_minus1[ SchedSelIdx ]** (together with **bit\_rate\_scale**) specifies the maximum input bit rate for the SchedSelIdx-th CPB. **bit\_rate\_value\_minus1[ SchedSelIdx ]** shall be in the range of 0 to $2^{32} - 2$ , inclusive. For any **SchedSelIdx** > 0, **bit\_rate\_value\_minus1[ SchedSelIdx ]** shall be greater than **bit\_rate\_value\_minus1[ SchedSelIdx - 1 ]**. The bit rate in bits per second is given by + +$$\text{BitRate[ SchedSelIdx ]} = ( \text{bit\_rate\_value\_minus1[ SchedSelIdx ]} + 1 ) * 2^{(6 + \text{bit\_rate\_scale})} \quad (\text{E-81})$$ + +When the **bit\_rate\_value\_minus1[ SchedSelIdx ]** syntax element is not present, the value of **BitRate[ SchedSelIdx ]** shall be inferred as follows: + +- If **profile\_idc** is equal to 66, 77, or 88, **BitRate[ SchedSelIdx ]** shall be inferred to be equal to 1000 \* MaxBR for VCL HRD parameters and to be equal to 1200 \* MaxBR for NAL HRD parameters, where MaxBR is specified in clause A.3.1. +- Otherwise, **BitRate[ SchedSelIdx ]** shall be inferred to be equal to **cpbBrVclFactor** \* MaxBR for VCL HRD parameters and to be equal to **cpbBrNalFactor** \* MaxBR for NAL HRD parameters, where MaxBR is specified in clause A.3.1 and **cpbBrVclFactor** and **cpbBrNalFactor** are specified in clause A.3.3 (for profiles specified in Annex A) or clause F.10.2.2 (for profiles specified in Annex F) or clause G.10.2 (for profiles specified in Annex G). + +**cpb\_size\_value\_minus1[ SchedSelIdx ]** is used together with **cpb\_size\_scale** to specify the SchedSelIdx-th CPB size. **cpb\_size\_value\_minus1[ SchedSelIdx ]** shall be in the range of 0 to $2^{32} - 2$ , inclusive. For any **SchedSelIdx** greater than 0, **cpb\_size\_value\_minus1[ SchedSelIdx ]** shall be less than or equal to **cpb\_size\_value\_minus1[ SchedSelIdx - 1 ]**. + +The CPB size in bits is given by + +$$\text{CpbSize[ SchedSelIdx ]} = ( \text{cpb\_size\_value\_minus1[ SchedSelIdx ]} + 1 ) * 2^{(4 + \text{cpb\_size\_scale})} \quad (\text{E-82})$$ + +When the **cpb\_size\_value\_minus1[ SchedSelIdx ]** syntax element is not present, the value of **CpbSize[ SchedSelIdx ]** shall be inferred as follows: + +- If **profile\_idc** is equal to 66, 77, or 88, **CpbSize[ SchedSelIdx ]** shall be inferred to be equal to 1000 \* MaxCPB for VCL HRD parameters and to be equal to 1200 \* MaxCPB for NAL HRD parameters, where MaxCPB is specified in clause A.3.1. +- Otherwise, **CpbSize[ SchedSelIdx ]** shall be inferred to be equal to **cpbBrVclFactor** \* MaxCPB for VCL HRD parameters and to be equal to **cpbBrNalFactor** \* MaxCPB for NAL HRD parameters, where MaxCPB is specified in clause A.3.1 and **cpbBrVclFactor** and **cpbBrNalFactor** are specified in clause A.3.3 (for profiles specified in Annex A) or clause F.10.2.2 (for profiles specified in Annex F) or clause G.10.2 (for profiles specified in Annex G). + +**cbr\_flag[ SchedSelIdx ]** equal to 0 specifies that to decode this bitstream by the HRD using the SchedSelIdx-th CPB specification, the hypothetical stream delivery scheduler (HSS) operates in an intermittent bit rate mode. **cbr\_flag[ SchedSelIdx ]** equal to 1 specifies that the HSS operates in a constant bit rate (CBR) mode. When the **cbr\_flag[ SchedSelIdx ]** syntax element is not present, the value of **cbr\_flag** shall be inferred to be equal to 0. + +**initial\_cpb\_removal\_delay\_length\_minus1** specifies the length in bits of the **initial\_cpb\_removal\_delay[ SchedSelIdx ]** and **initial\_cpb\_removal\_delay\_offset[ SchedSelIdx ]** syntax elements of the buffering period SEI message. The length of **initial\_cpb\_removal\_delay[ SchedSelIdx ]** and of **initial\_cpb\_removal\_delay\_offset[ SchedSelIdx ]** is **initial\_cpb\_removal\_delay\_length\_minus1** + 1. When the **initial\_cpb\_removal\_delay\_length\_minus1** syntax element is present in more than one **hrd\_parameters( )** syntax structure within the VUI parameters syntax structure, the value of the **initial\_cpb\_removal\_delay\_length\_minus1** parameters shall be equal in both **hrd\_parameters( )** syntax structures. When the **initial\_cpb\_removal\_delay\_length\_minus1** syntax element is not present, it shall be inferred to be equal to 23. + +**cpb\_removal\_delay\_length\_minus1** specifies the length in bits of the **cpb\_removal\_delay** syntax element. The length of the **cpb\_removal\_delay** syntax element of the picture timing SEI message is **cpb\_removal\_delay\_length\_minus1** + 1. + +When the cpb\_removal\_delay\_length\_minus1 syntax element is present in more than one hrd\_parameters( ) syntax structure within the VUI parameters syntax structure, the value of the cpb\_removal\_delay\_length\_minus1 parameters shall be equal in both hrd\_parameters( ) syntax structures. When the cpb\_removal\_delay\_length\_minus1 syntax element is not present, it shall be inferred to be equal to 23. + +**dpb\_output\_delay\_length\_minus1** specifies the length in bits of the dpb\_output\_delay syntax element. The length of the dpb\_output\_delay syntax element of the picture timing SEI message is dpb\_output\_delay\_length\_minus1 + 1. When the dpb\_output\_delay\_length\_minus1 syntax element is present in more than one hrd\_parameters( ) syntax structure within the VUI parameters syntax structure, the value of the dpb\_output\_delay\_length\_minus1 parameters shall be equal in both hrd\_parameters( ) syntax structures. When the dpb\_output\_delay\_length\_minus1 syntax element is not present, it shall be inferred to be equal to 23. + +**time\_offset\_length** greater than 0 specifies the length in bits of the time\_offset syntax element. time\_offset\_length equal to 0 specifies that the time\_offset syntax element is not present. When the time\_offset\_length syntax element is present in more than one hrd\_parameters( ) syntax structure within the VUI parameters syntax structure, the value of the time\_offset\_length parameters shall be equal in both hrd\_parameters( ) syntax structures. When the time\_offset\_length syntax element is not present, it shall be inferred to be equal to 24. + +## Annex F + +### Scalable video coding + +(This annex forms an integral part of this Recommendation | International Standard.) + +This annex specifies scalable video coding, referred to as SVC. + +#### F.1 Scope + +Bitstreams and decoders conforming to one or more of the profiles specified in this annex are completely specified in this annex with reference made to clauses 2 to 9 and Annexes A to E. + +#### F.2 Normative references + +The specifications in clause 2 apply with the following addition. + +- IETF RFC 3986 (2005), *Uniform Resource Identifiers (URI): Generic Syntax*. + +#### F.3 Definitions + +For the purpose of this annex, the following definitions apply in addition to the definitions in clause 3. These definitions are either not present in clause 3 or replace definitions in clause 3. + +- F.3.1 arbitrary slice order (ASO):** A *decoding order of slices* in which the *macroblock address* of the first *macroblock* of some *slice* of a *slice group* within a *layer representation* may be less than the *macroblock address* of the first *macroblock* of some other preceding *slice* of the same *slice group* within the same *layer representation* or in which the *slices* of a *slice group* within a *layer representation* may be interleaved with the *slices* of one or more other *slices groups* within the same *layer representation*. +- F.3.2 associated NAL unit:** A *NAL unit* that directly succeeds a *prefix NAL unit* in *decoding order*. +- F.3.3 B slice:** A *slice* that may be decoded using *intra-layer intra prediction* or *inter prediction* using at most two *motion vectors* and *reference indices* to *predict* the sample values of each *block*. +- F.3.4 base layer:** A *sub-bitstream* that contains all *NAL units* with the *nal\_unit\_type syntax element* equal to 1 and 5 of the *bitstream* and does not contain any *NAL unit* with the *nal\_unit\_type syntax element* equal to 14, 15, or 20 and conforms to one or more of the profiles specified in Annex A. +- F.3.5 base quality layer representation:** The *layer representation* of the *target dependency representation* of an *access unit* that is associated with the *quality\_id syntax element* equal to 0. +- F.3.6 bottom macroblock (of a macroblock pair):** The *macroblock* within a *macroblock pair* that contains the samples in the bottom row of samples for the *macroblock pair*. For a *field macroblock pair*, the bottom macroblock represents the samples from the region of the *bottom field* or *layer bottom field* of the *frame* or *layer frame*, respectively, that lie within the spatial region of the *macroblock pair*. For a *frame macroblock pair*, the bottom macroblock represents the samples of the *frame* or *layer frame* that lie within the bottom half of the spatial region of the *macroblock pair*. +- F.3.7 coded slice in scalable extension NAL unit:** A *coded slice NAL unit* that contains an *EI slice*, *EP slice*, or an *EB slice*. +- F.3.8 complementary reference field pair:** A collective term for two *reference fields* that are in consecutive *access units* in *decoding order* as two *coded fields*, where the *target dependency representations* of the *fields* share the same value of the *frame\_num syntax element* and where the second *field* in *decoding order* is not an *IDR picture* and the *target dependency representation* of the second *field* does not include a *memory\_management\_control\_operation syntax element* equal to 5, or a *complementary reference base field pair*. +- F.3.9 complementary reference base field pair:** Two *reference base fields* that are associated with two *coded fields* that are in consecutive *access units* in *decoding order*, where the *target dependency representations* of the *coded fields* share the same value of the *frame\_num syntax element* and where the second *coded field* in *decoding order* is not an *IDR picture* and the *target dependency representation* of the second *coded field* does not include a *memory\_management\_control\_operation syntax element* equal to 5. A *complementary reference base field pair* is a *complementary reference field pair*. + +- F.3.10 dependency representation:** A subset of VCL NAL units within an access unit that are associated with the same value of the *dependency\_id* syntax element, which is provided as part of the NAL unit header or by an associated prefix NAL unit, and the same value of the *redundant\_pic\_cnt* syntax element. A *dependency representation* consists of one or more *layer representations*. +- F.3.11 EB slice:** A slice that may be decoded using *intra prediction* or *inter prediction* or *inter-layer prediction* from syntax elements and derived variables of the *reference layer representation*. For *inter-prediction* of EB slices at most two *motion vectors* and *reference indices* are used to predict the sample values of each block. +- F.3.12 EI slice:** A slice that is not an I slice or SI slice that is decoded using *intra prediction* only. +- F.3.13 EP slice:** A slice that may be decoded using *intra prediction* or *inter prediction* or *inter-layer prediction* from syntax elements and derived variables of the *reference layer representation*. For *inter-prediction* of EP slices at most one *motion vector* and *reference index* is used to predict the sample values of each block. +- F.3.14 field macroblock:** A macroblock containing samples from a single *field* or *layer field*. +- F.3.15 frame macroblock:** A macroblock containing samples from the two *fields* or *layer fields* of a *frame* or *layer frame*, respectively. +- F.3.16 I slice:** A slice that is decoded using *intra-layer intra prediction* only. +- F.3.17 instantaneous decoding refresh (IDR) picture:** A coded picture for which the variable *IdrPicFlag* is equal to 1 for the *target dependency representation*. An IDR picture causes the *decoding process* to mark all *reference pictures* as "unused for reference" immediately after the decoding of the IDR picture. All coded pictures that follow an IDR picture in *decoding order* can be decoded without *inter prediction* from any picture that precedes the IDR picture in *decoding order*. The first picture of each coded video sequence in *decoding order* is an IDR picture. +- F.3.18 inter-layer intra prediction:** An *inter-layer prediction* derived from decoded samples of *intra-coded macroblocks* of the *reference layer representation*. +- F.3.19 inter-layer prediction:** A prediction derived from syntax elements, derived variables, or decoded samples of the *reference layer representation*. +- F.3.20 intra-layer intra prediction:** A prediction derived from decoded samples of the same decoded slice. +- F.3.21 intra prediction:** A collective term for *intra-layer intra prediction* or *inter-layer intra prediction* or a combination of *intra-layer intra prediction* together with *inter-layer prediction* from syntax elements and derived variables of the *reference layer representation*. +- F.3.22 intra slice:** A collective term for I slice or EI slice. +- F.3.23 layer bottom field:** One of two *layer fields* that comprise a *layer frame*. Each row of a *layer bottom field* is spatially located immediately below a corresponding row of a *layer top field*. +- F.3.24 layer field:** An assembly of alternate rows of a *layer frame*. A *layer frame* is composed of two *layer fields*, a *layer top field* and a *layer bottom field*. +- F.3.25 layer frame:** A *layer frame* contains an array of *luma* samples that represents an intermediate decoding result for a *field* or a *frame* in monochrome format or an array of *luma* samples and two corresponding arrays of *chroma* samples that represent an intermediate decoding result for a *field* or a *frame* in 4:2:0, 4:2:2, and 4:4:4 colour format. A *layer frame* consists of two *layer fields*, a *layer top field* and a *layer bottom field*. +- F.3.26 layer picture:** A collective term for a *layer field* or a *layer frame*. +- F.3.27 layer top field:** One of two *layer fields* that comprise a *layer frame*. Each row of a *layer top field* is spatially located immediately above a corresponding row of a *layer bottom field*. +- F.3.28 layer representation:** A subset of VCL NAL units within an access unit that are associated with the same values of the *dependency\_id* and *quality\_id* syntax elements, which are provided as part of the VCL NAL unit header or by an associated prefix NAL unit, and the same value of the *redundant\_pic\_cnt* syntax element. One or more *layer representations* represent a *dependency representation*. +- F.3.29 layer representation identifier:** An integer value by which a particular *layer representation* inside a coded picture is uniquely identified. +- F.3.30 macroblock:** A 16x16 block of *luma* samples and two corresponding blocks of *chroma* samples of a *picture* or *layer picture* that has three sample arrays, or a 16x16 block of samples of a monochrome *picture* or *layer picture*. The division of a slice or a macroblock pair into macroblocks is a *partitioning*. + +- F.3.31 macroblock-adaptive frame/field decoding:** A decoding process for coded frames or layer representations in which some macroblocks may be decoded as frame macroblocks and others may be decoded as field macroblocks. +- F.3.32 macroblock address:** When macroblock-adaptive frame/field decoding is not in use, a macroblock address is the index of a macroblock in a macroblock raster scan of the picture or layer picture starting with zero for the top-left macroblock in a picture or layer picture. When macroblock-adaptive frame/field decoding is in use, the macroblock address of the top macroblock of a macroblock pair is two times the index of the macroblock pair in a macroblock pair raster scan of the picture or layer picture, and the macroblock address of the bottom macroblock of a macroblock pair is the macroblock address of the corresponding top macroblock plus 1. The macroblock address of the top macroblock of each macroblock pair is an even number and the macroblock address of the bottom macroblock of each macroblock pair is an odd number. +- F.3.33 macroblock location:** The two-dimensional coordinates of a macroblock in a picture or layer picture denoted by ( x, y ). For the top left macroblock of the picture or layer picture ( x, y ) is equal to ( 0, 0 ). x is incremented by 1 for each macroblock column from left to right. When macroblock-adaptive frame/field decoding is not in use, y is incremented by 1 for each macroblock row from top to bottom. When macroblock-adaptive frame/field decoding is in use, y is incremented by 2 for each macroblock pair row from top to bottom, and is incremented by an additional 1 when a macroblock is a bottom macroblock. +- F.3.34 macroblock pair:** A pair of vertically contiguous macroblocks in a frame or layer frame that is coupled for use in macroblock-adaptive frame/field decoding. The division of a slice into macroblock pairs is a partitioning. +- F.3.35 macroblock to slice group map:** A means of mapping macroblocks of a picture or layer picture into slice groups. The macroblock to slice group map consists of a list of numbers, one for each coded macroblock, specifying the slice group to which each coded macroblock belongs. +- F.3.36 map unit to slice group map:** A means of mapping slice group map units of a picture or layer picture into slice groups. The map unit to slice group map consists of a list of numbers, one for each slice group map unit, specifying the slice group to which each coded slice group map unit belongs to. +- F.3.37 non-paired reference base field:** A reference base field that is not part of a complementary reference base field pair. A non-paired reference base field is a non-paired reference field. +- F.3.38 P slice:** A slice that may be decoded using intra-layer intra prediction or inter prediction using at most one motion vector and reference index to predict the sample values of each block. +- F.3.39 parameter:** A syntax element of an SVC sequence parameter set or a picture parameter set. Parameter is also used as part of the defined term quantization parameter. +- F.3.40 picture parameter set:** A syntax structure containing syntax elements that apply to zero or more layer representations as determined by the pic\_parameter\_set\_id syntax element found in each slice header. +- F.3.41 prefix NAL unit:** A NAL unit with nal\_unit\_type equal to 14 that immediately precedes in decoding order a NAL unit with nal\_unit\_type equal to 1 or 5. The NAL unit that immediately succeeds the prefix NAL unit in decoding order is referred to as the associated NAL unit. The prefix NAL unit contains data associated with the associated NAL unit, which are considered to be part of the associated NAL unit. +- F.3.42 reference base field:** A reference field that is obtained by decoding a base quality layer representation with the nal\_ref\_idc syntax element not equal to 0, the store\_ref\_base\_pic\_flag syntax element equal to 1, and the field\_pic\_flag syntax element equal to 1 of a coded picture and all layer representations of the coded picture that are referred to by inter-layer prediction in the base quality layer representation. A reference base field is not a decoded picture and it is not an output of the decoding process, but may be used for inter prediction when P, B, EP, and EB slices of a coded field or a field macroblock of a coded frame are decoded. See also reference base picture. +- F.3.43 reference base frame:** A reference frame that is obtained by decoding a base quality layer representation with the nal\_ref\_idc syntax element not equal to 0, the store\_ref\_base\_pic\_flag syntax element equal to 1, and the field\_pic\_flag syntax element equal to 0 of a coded picture and all layer representations of the coded picture that are referred to by inter-layer prediction of the base quality layer representation. A reference base frame is not a decoded picture and it is not an output of the decoding process, but may be used for inter prediction when P, B, EP, and EB slices of a coded frame are decoded. See also reference base picture. +- F.3.44 reference base picture:** A collective term for a reference base field or a reference base frame. +- F.3.45 reference field:** A reference field may be used for inter prediction when P, B, EP, or EB slices of a coded field or field macroblocks of a coded frame are decoded. See also reference picture. + +- F.3.46 reference frame:** A *reference frame* may be used for *inter prediction* when *P*, *B*, *EP*, or *EB* slices of a *coded frame* are decoded. See also *reference picture*. +- F.3.47 reference layer macroblock:** A *macroblock* of a *reference layer representation*. +- F.3.48 reference layer representation:** A *reference layer representation* for a particular *layer representation* of a *coded picture* is the *layer representation* that is used for *inter-layer prediction* of the particular *layer representation*. The *reference layer representation* belongs to the same *access unit* as the *layer representation* that uses the *reference layer representation* for *inter-layer prediction*. +- F.3.49 reference picture:** A collective term for a *decoded picture* that is obtained by decoding a *coded picture* for which the *nal\_ref\_idc syntax element* that is associated with the *target dependency representation* is not equal to 0 or a *reference base picture*. A *reference picture* contains samples that may be used for *inter prediction* in the *decoding process* of subsequent *pictures* in *decoding order*. +- F.3.50 reference picture list:** A list of *reference pictures* that is used for *inter prediction* of a *P*, *B*, *EP*, or *EB* slice. For the *decoding process* of a *P* or *EP* slice, there is one *reference picture list*. For the *decoding process* of a *B* or *EB* slice, there are two *reference picture lists*. +- F.3.51 reference picture list 0:** A *reference picture list* used for *inter prediction* of a *P*, *B*, *EP*, or *EB* slice. All *inter prediction* used for *P* and *EP* slices uses *reference picture list 0*. *Reference picture list 0* is one of two *reference picture lists* used for *inter prediction* for a *B* or *EB* slice, with the other being *reference picture list 1*. +- F.3.52 reference picture list 1:** A *reference picture list* used for *inter prediction* of a *B* or *EB* slice. *Reference picture list 1* is one of two *reference picture lists* used for *inter prediction* for a *B* or *EB* slice, with the other being *reference picture list 0*. +- F.3.53 scalable bitstream:** A *bitstream* with the property that one or more *sub-bitstreams* that are not identical to the *scalable bitstream* form another *bitstream* that conforms to this specification. +- F.3.54 sequence parameter set:** A *syntax structure* containing *syntax elements* that apply to zero or more *layer representations* with the *dependency\_id syntax element* equal to 0 and the *quality\_id syntax element* equal to 0 as determined by the content of a *seq\_parameter\_set\_id syntax element* found in the *picture parameter set* referred to by the *pic\_parameter\_set\_id syntax element* found in each *slice header* of *I*, *P*, and *B* slices. +- F.3.55 slice:** An integer number of *macroblocks* or *macroblock pairs* ordered consecutively in the *raster scan* within a particular *slice group*. Each *macroblock* or *macroblock pair* of a *picture* or *layer picture* shall not be contained in more than one *slice* of a particular *layer representation*. Although a *slice* contains *macroblocks* or *macroblock pairs* that are consecutive in the *raster scan* within a *slice group*, these *macroblocks* or *macroblock pairs* are not necessarily consecutive in the *raster scan* within the *picture* or *layer picture*. The *macroblock addresses* are derived from the first *macroblock address* in a *slice* (as represented in the *slice header*) and the *macroblock to slice group map*. +- F.3.56 slice group:** A subset of the *macroblocks* or *macroblock pairs* of a *picture* or *layer picture*. The division of the *picture* or *layer picture* into *slice groups* is a *partitioning* of the *picture* or *layer picture*. The *partitioning* is specified by the *macroblock to slice group map*. +- F.3.57 spatial intra prediction:** See *intra-layer intra prediction*. +- F.3.58 subset sequence parameter set:** A *syntax structure* containing *syntax elements* that apply to zero or more *layer representations* with the *dependency\_id syntax element* not equal to 0 or the *quality\_id syntax element* not equal to 0 as determined by the content of a *seq\_parameter\_set\_id syntax element* found in the *picture parameter set* referred to by the *pic\_parameter\_set\_id syntax element* found in each *slice header* of *EI*, *EP*, and *EB* slices. +- F.3.59 SVC sequence parameter set:** A collective term for *sequence parameter set* or *subset sequence parameter set*. +- F.3.60 SVC sequence parameter set RBSP:** A collective term for *sequence parameter set RBSP* or *subset sequence parameter set RBSP*. +- F.3.61 target dependency representation:** The *dependency representation* of a *coded picture* that is associated with the largest value of the *dependency\_id syntax element* for all *dependency representations* of the *coded picture*. +- F.3.62 target layer representation:** The *layer representation* of the *target dependency representation* of a *coded picture* that is associated with the largest value of the *quality\_id syntax element* for all *layer representations* of the *target dependency representation* of the *coded picture*. +- F.3.63 top macroblock (of a macroblock pair):** The *macroblock* within a *macroblock pair* that contains the samples in the top row of samples for the *macroblock pair*. For a *field macroblock pair*, the top *macroblock* represents the samples from the region of the *top field* or *layer top field* of the *frame* or *layer frame* that lie within the spatial + +region of the *macroblock pair*. For a *frame macroblock pair*, the top macroblock represents the samples of the *frame* or *layer frame* that lie within the top half of the spatial region of the *macroblock pair*. + +**F.3.64 VCL NAL unit:** A collective term for *coded slice NAL units* and *prefix NAL units*. + +## F.4 Abbreviations + +The specifications in clause 4 apply. + +## F.5 Conventions + +The specifications in clause 5 apply. + +## F.6 Source, coded, decoded and output data formats, scanning processes, neighbouring and reference layer relationships + +The specifications in clause 6 apply with substituting SVC sequence parameter set for sequence parameter set. The specification in clause 6.3 also applies to layer pictures. Additionally, the following processes are specified. + +### F.6.1 Derivation process for reference layer macroblocks + +This process is only invoked when `no_inter_layer_pred_flag` is equal to 0. + +Inputs to this process are: + +- a luma location ( `xP`, `yP` ) relative to the upper-left luma sample of the current macroblock, +- a variable `fieldMbFlag` specifying whether the current macroblock is a field or a frame macroblock, +- a one-dimensional array `refLayerFieldMbFlag` with `RefLayerPicSizeInMbs` elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array `refLayerMbType` with `RefLayerPicSizeInMbs` elements specifying macroblock types for the macroblocks of the reference layer representation. + +Outputs of this process are: + +- the macroblock address `mbAddrRefLayer` specifying the reference layer macroblock, +- a luma location ( `xB`, `yB` ) relative to the upper-left luma sample of the reference layer macroblock. + +Let `currDQId` be the current value of `DQId` and let `levelIdc` be the value of `level_idc` in the SVC sequence parameter set that is referred to in coded slice NAL units with `DQId` equal to $(( \text{currDQId} \gg 4 ) \ll 4)$ . + +The variables `shiftX`, `shiftY`, `scaleX`, `scaleY`, `offsetX`, and `offsetY` are derived as specified in the following ordered steps: + +1. The variables `refW`, `refH`, `scaledW`, `scaledH`, `offsetX`, and `offsetY` are derived by + +$$\text{refW} = \text{RefLayerPicWidthInSamples}_L \quad (\text{F-1})$$ + +$$\text{refH} = \text{RefLayerPicHeightInSamples}_L \quad (\text{F-2})$$ + +$$\text{scaledW} = \text{ScaledRefLayerPicWidthInSamples}_L \quad (\text{F-3})$$ + +$$\text{scaledH} = \text{ScaledRefLayerPicHeightInSamples}_L \quad (\text{F-4})$$ + +$$\text{offsetX} = \text{ScaledRefLayerLeftOffset} \quad (\text{F-5})$$ + +$$\text{offsetY} = \text{ScaledRefLayerTopOffset} / ( 1 + \text{field\_pic\_flag} ) \quad (\text{F-6})$$ + +2. The variables `shiftX` and `shiftY` are derived by + +$$\text{shiftX} = ( ( \text{levelIdc} \leq 30 ) ? 16 : ( 31 - \text{Ceil}( \text{Log2}( \text{refW} ) ) ) ) \quad (\text{F-7})$$ + +$$\text{shiftY} = ( ( \text{levelIdc} \leq 30 ) ? 16 : ( 31 - \text{Ceil}( \text{Log2}( \text{refH} ) ) ) ) \quad (\text{F-8})$$ + +3. The variables `scaleX` and `scaleY` are derived by + +$$\text{scaleX} = ( ( \text{refW} \ll \text{shiftX} ) + ( \text{scaledW} \gg 1 ) ) / \text{scaledW} \quad (\text{F-9})$$ + +$$\text{scaleY} = ( ( \text{refH} \ll \text{shiftY} ) + ( \text{scaledH} \gg 1 ) ) / \text{scaledH} \quad (\text{F-10})$$ + +NOTE 1 – The variables `shiftX`, `shiftY`, `scaleX`, `scaleY`, `offsetX`, and `offsetY` do not depend on the luma location ( `xP`, `yP` ), the variable `fieldMbFlag`, or the current macroblock. + +The reference layer luma location ( $xRef$ , $yRef$ ) relative to the upper-left sample of the reference layer picture is derived as specified by the following ordered steps: + +1. The inverse macroblock scanning process as specified in clause 6.4.1 is invoked with $CurrMbAddr$ as the input and the output is assigned to ( $xM$ , $yM$ ). For this invocation of the process in clause 6.4.1, the current macroblock is treated as field macroblock when $fieldMbFlag$ is equal to 1, and it is treated as frame macroblock when $fieldMbFlag$ is equal to 0. +2. The luma location ( $xC$ , $yC$ ) is derived by + +$$xC = xM + xP \tag{F-11}$$ + +$$yC = yM + yP * ( 1 + fieldMbFlag - field\_pic\_flag ) \tag{F-12}$$ + +3. The reference layer luma location is derived by + +$$xRef = ( ( xC - offsetX ) * scaleX + ( 1 \ll ( shiftX - 1 ) ) ) \gg shiftX \tag{F-13}$$ + +$$yRef = ( ( yC - offsetY ) * scaleY + ( 1 \ll ( shiftY - 1 ) ) ) \gg shiftY \tag{F-14}$$ + +4. The reference layer luma location is modified by + +$$xRef = \text{Min}( \text{RefLayerPicWidthInSamples}_L - 1, xRef ) \tag{F-15}$$ + +$$yRef = \text{Min}( \text{RefLayerPicHeightInSamples}_L - 1, yRef ) \tag{F-16}$$ + +The reference layer macroblock address $mbAddrRefLayer$ and a luma location ( $xB$ , $yB$ ) relative to the upper-left sample of the reference layer macroblock $mbAddrRefLayer$ are derived as follows: + +- If $MbaffFrameFlag$ is equal to 0 and $RefLayerMbaffFrameFlag$ is equal to 0, the following ordered steps are specified: + +1. The reference layer macroblock address $mbAddrRefLayer$ is derived by + +$$mbAddrRefLayer = ( yRef / 16 ) * \text{RefLayerPicWidthInMbs} + ( xRef / 16 ) \tag{F-17}$$ + +2. The luma location ( $xB$ , $yB$ ) is derived as follows: + +- If $mbAddrRefLayer$ is not available, ( $xB$ , $yB$ ) is marked as not available. +- Otherwise ( $mbAddrRefLayer$ is available), ( $xB$ , $yB$ ) is set equal to ( $xRef \% 16$ , $yRef \% 16$ ). + +- Otherwise ( $MbaffFrameFlag$ is equal to 1 or $RefLayerMbaffFrameFlag$ is equal to 1), the following ordered steps are specified: + +NOTE 2 – When $MbaffFrameFlag$ is equal to 1 or $RefLayerMbaffFrameFlag$ is equal to 1, $field\_pic\_flag$ and $RefLayerFieldPicFlag$ are both equal to 0 (see clause F.7.4.3.4). + +1. A virtual reference layer macroblock address $virtMbAddrRefLayer$ is derived as follows: + +- If $RefLayerMbaffFrameFlag$ is equal to 1, $virtMbAddrRefLayer$ is derived by + +$$virtMbAddrRefLayer = 2 * ( ( ( yRef / 32 ) * \text{RefLayerPicWidthInMbs} + ( xRef / 16 ) ) + ( yRef \% 32 ) / 16 ) \tag{F-18}$$ + +- Otherwise ( $RefLayerMbaffFrameFlag$ is equal to 0), $virtMbAddrRefLayer$ is derived by + +$$virtMbAddrRefLayer = ( yRef / 16 ) * \text{RefLayerPicWidthInMbs} + ( xRef / 16 ) \tag{F-19}$$ + +2. The reference layer macroblock address $mbAddrRefLayer$ and the luma location ( $xB$ , $yB$ ) are derived as follows: + +- If $fieldMbFlag$ is equal to 0 and $refLayerFieldMbRef[ virtMbAddrRefLayer ]$ is equal to 1, the field-to-frame reference layer macroblock conversion process as specified in clause F.6.1.1 is invoked with $virtMbAddrRefLayer$ , ( $xRef$ , $yRef$ ), and $refLayerMbType$ as the inputs and the outputs are assigned to $mbAddrRefLayer$ and ( $xB$ , $yB$ ). +- Otherwise, if $fieldMbFlag$ is equal to 1 and $refLayerFieldMbRef[ virtMbAddrRefLayer ]$ is equal to 0, the frame-to-field reference layer macroblock conversion process as specified in clause F.6.1.2 is invoked with $virtMbAddrRefLayer$ and ( $xRef$ , $yRef$ ) as the inputs and the outputs are assigned to $mbAddrRefLayer$ and ( $xB$ , $yB$ ). + +- Otherwise (fieldMbFlag is equal to refLayerFieldMbRef[ virtMbAddrRefLayer ]), mbAddrRefLayer and ( xB, yB ) are derived by + +$$\begin{aligned} \text{mbAddrRefLayer} = & ( ( \text{virtMbAddrRefLayer} \gg \text{fieldMbFlag} ) \ll \text{fieldMbFlag} ) \\ & + ( \text{CurrMbAddr} \% 2 ) * \text{fieldMbFlag} \end{aligned} \quad (\text{F-20})$$ + +$$\text{xB} = ( \text{xRef} \% 16 ) \quad (\text{F-21})$$ + +$$\text{yB} = ( \text{yRef} \% ( 16 \ll \text{fieldMbFlag} ) ) \gg \text{fieldMbFlag} \quad (\text{F-22})$$ + +#### F.6.1.1 Field-to-frame reference layer macroblock conversion process + +Inputs to this process are: + +- a virtual reference layer macroblock address virtMbAddrRefLayer, +- a reference layer luma location ( xRef, yRef ) relative to the upper-left luma sample of the reference layer picture, +- a one-dimensional array refLayerMbType with RefLayerPicSizeInMbs elements specifying macroblock types for the macroblocks of the reference layer representation. + +Outputs of this process are: + +- the macroblock address mbAddrRefLayer of the reference layer macroblock, +- a luma location ( xB, yB ) relative to the upper-left luma sample of the reference layer macroblock. + +The macroblock addresses mbAddrRefLayerTop and mbAddrRefLayerBot are derived by + +$$\text{mbAddrRefLayerTop} = \text{virtMbAddrRefLayer} - ( \text{virtMbAddrRefLayer} \% 2 ) \quad (\text{F-23})$$ + +$$\text{mbAddrRefLayerBot} = \text{mbAddrRefLayerTop} + 1 \quad (\text{F-24})$$ + +The reference layer macroblock address mbAddrRefLayer is derived as follows: + +- If refLayerMbType[ mbAddrRefLayerTop ] is equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL, mbAddrRefLayer is set equal to mbAddrRefLayerBot. +- Otherwise (refLayerMbType[ mbAddrRefLayerTop ] is not equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL), mbAddrRefLayer is set equal to mbAddrRefLayerTop. + +The luma location ( xB, yB ) is derived by + +$$\text{xB} = \text{xRef} \% 16 \quad (\text{F-25})$$ + +$$\text{yB} = 8 * ( ( \text{yRef} / 16 ) \% 2 ) + 4 * ( ( \text{yRef} \% 16 ) / 8 ) \quad (\text{F-26})$$ + +#### F.6.1.2 Frame-to-field reference layer macroblock conversion process + +Inputs to this process are: + +- a virtual reference layer macroblock address virtMbAddrRefLayer, +- a virtual reference layer luma location ( xRef, yRef ) relative to the upper-left luma sample of the reference layer picture. + +Outputs of this process are: + +- the macroblock address mbAddrRefLayer of the reference layer macroblock, +- a luma location ( xB, yB ) relative to the upper-left luma sample of the reference layer macroblock. + +The reference layer macroblock address mbAddrRefLayer and the luma location ( xB, yB ) are derived by + +$$\text{mbAddrRefLayer} = \text{virtMbAddrRefLayer} \quad (\text{F-27})$$ + +$$\text{xB} = \text{xRef} \% 16 \quad (\text{F-28})$$ + +$$\text{yB} = \text{yRef} \% 16 \quad (\text{F-29})$$ + +#### F.6.2 Derivation process for reference layer partitions + +This process is only invoked when no\_inter\_layer\_pred\_flag is equal to 0. + +Inputs to this process are: + +- a luma location ( xP, yP ) relative to the upper-left luma sample of the current macroblock, + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a one-dimensional array refLayerFieldMbFlag with RefLayerPicSizeInMbs elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array refLayerMbType with RefLayerPicSizeInMbs elements specifying macroblock types for the macroblocks of the reference layer representation, +- a (RefLayerPicSizeInMbs)x4 array refLayerSubMbType specifying the sub-macroblock types for the macroblocks of the reference layer representation. + +Outputs of this process are: + +- the macroblock address mbAddrRefLayer specifying the reference layer macroblock, +- the macroblock partition index mbPartIdxRefLayer specifying the reference layer macroblock partition inside the reference layer macroblock mbAddrRefLayer, +- the sub-macroblock partition index subMbPartIdxRefLayer specifying the reference layer sub-macroblock partition inside the macroblock partition mbPartIdxRefLayer of the reference layer macroblock mbAddrRefLayer. + +The derivation process for reference layer macroblocks as specified in clause F.6.1 is invoked with the luma location ( xP, yP ), fieldMbFlag, refLayerFieldMbFlag, and refLayerMbType as the input and the outputs are assigned to mbAddrRefLayer and ( xB, yB ). + +The SVC derivation process for macroblock and sub-macroblock partition indices as specified in clause F.6.4 is invoked with currDQId set equal to ref\_layer\_dq\_id, the luma location ( xB, yB ), the macroblock type refLayerMbType[ mbAddrRefLayer ], and, when refLayerMbType[ mbAddrRefLayer ] is equal to P\_8x8, P\_8x8ref0, or B\_8x8, the list of sub-macroblock types refLayerSubMbType[ mbAddrRefLayer ] as the inputs and the outputs are the reference layer macroblock partition index mbPartIdxRefLayer and the reference layer sub-macroblock partition index subMbPartIdxRefLayer. + +#### F.6.3 Derivation process for reference layer sample locations in resampling + +Inputs to this process are: + +- a variable chromaFlag specifying whether the luma or a chroma component is subject to the resampling process, +- a sample location ( xP, yP ) relative to the upper-left sample of the current macroblock, +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable botFieldFlag specifying whether a top or a bottom field is subject to the resampling process (when RefLayerFrameMbsOnlyFlag is equal to 0 or frame\_mbs\_only\_flag is equal to 0). + +Output of this process is a reference layer sample location ( xRef16, yRef16 ), which specifies the following: + +- If RefLayerFrameMbsOnlyFlag is equal to 1 or RefLayerFieldPicFlag is equal to 1, ( xRef16, yRef16 ) specifies the reference layer sample location in units of 1/16-th sample relative to the upper-left sample of the reference layer picture. +- Otherwise (RefLayerFrameMbsOnlyFlag is equal to 0 and RefLayerFieldPicFlag is equal to 0), ( xRef16, yRef16 ) specifies the reference layer sample location in units of 1/16-th field sample relative to the upper-left sample of the field specified by botFieldFlag of the reference layer picture. + +Let currDQId be the current value of DQId and let levelIdc be the value of level\_idc in the SVC sequence parameter set that is referred to in coded slice NAL units with DQId equal to (( currDQId >> 4 ) << 4). + +The variables subW, subH, shiftX, shiftY, scaleX, scaleY, offsetX, offsetY, addX, addY, deltaX, and deltaY are derived as specified in the following ordered steps: + +1. With Z being replaced by L for chromaFlag equal to 0 and C for chromaFlag equal to 1, the variables refW, refH, scaledW, and scaledH are derived by + +$$\text{refW} = \text{RefLayerPicWidthInSamples}_Z \quad (\text{F-30})$$ + +$$\text{refH} = \text{RefLayerPicHeightInSamples}_Z * ( 1 + \text{RefLayerFieldPicFlag} ) \quad (\text{F-31})$$ + +$$\text{scaledW} = \text{ScaledRefLayerPicWidthInSamples}_Z \quad (\text{F-32})$$ + +$$\text{scaledH} = \text{ScaledRefLayerPicHeightInSamples}_Z * ( 1 + \text{field\_pic\_flag} ) \quad (\text{F-33})$$ + +2. When frame\_mbs\_only\_flag is equal to 0 and RefLayerFrameMbsOnlyFlag is equal to 1, the variable scaledH is modified by + +$$\text{scaledH} = \text{scaledH} / 2 \quad (\text{F-34})$$ + +3. The variables `refPhaseX`, `refPhaseY`, `phaseX`, `phaseY`, `subW`, and `subH` are derived by + +$$\text{refPhaseX} = ( ( \text{chromaFlag} == 0 ) ? 0 : ( \text{ref\_layer\_chroma\_phase\_x\_plus1\_flag} - 1 ) ) \quad (\text{F-35})$$ + +$$\text{refPhaseY} = ( ( \text{chromaFlag} == 0 ) ? 0 : ( \text{ref\_layer\_chroma\_phase\_y\_plus1\_flag} - 1 ) ) \quad (\text{F-36})$$ + +$$\text{phaseX} = ( ( \text{chromaFlag} == 0 ) ? 0 : ( \text{chroma\_phase\_x\_plus1\_flag} - 1 ) ) \quad (\text{F-37})$$ + +$$\text{phaseY} = ( ( \text{chromaFlag} == 0 ) ? 0 : ( \text{chroma\_phase\_y\_plus1\_flag} - 1 ) ) \quad (\text{F-38})$$ + +$$\text{subW} = ( ( \text{chromaFlag} == 0 ) ? 1 : \text{SubWidthC} ) \quad (\text{F-39})$$ + +$$\text{subH} = ( ( \text{chromaFlag} == 0 ) ? 1 : \text{SubHeightC} ) \quad (\text{F-40})$$ + +4. When `RefLayerFrameMbsOnlyFlag` is equal to 0 or `frame_mbs_only_flag` is equal to 0, the following applies: + +- If `RefLayerFrameMbsOnlyFlag` is equal to 1, the variables `phaseY` and `refPhaseY` are modified by + +$$\text{phaseY} = \text{phaseY} + 4 * \text{botFieldFlag} + 3 - \text{subH} \quad (\text{F-41})$$ + +$$\text{refPhaseY} = 2 * \text{refPhaseY} + 2 \quad (\text{F-42})$$ + +- Otherwise (`RefLayerFrameMbsOnlyFlag` is equal to 0), the variables `phaseY` and `refPhaseY` are modified by + +$$\text{phaseY} = \text{phaseY} + 4 * \text{botFieldFlag} \quad (\text{F-43})$$ + +$$\text{refPhaseY} = \text{refPhaseY} + 4 * \text{botFieldFlag} \quad (\text{F-44})$$ + +5. The variables `shiftX` and `shiftY` are derived by + +$$\text{shiftX} = ( ( \text{levelIdc} \leq 30 ) ? 16 : ( 31 - \text{Ceil}( \text{Log2}( \text{refW} ) ) ) ) \quad (\text{F-45})$$ + +$$\text{shiftY} = ( ( \text{levelIdc} \leq 30 ) ? 16 : ( 31 - \text{Ceil}( \text{Log2}( \text{refH} ) ) ) ) \quad (\text{F-46})$$ + +6. The variables `scaleX` and `scaleY` are derived by + +$$\text{scaleX} = ( ( \text{refW} \ll \text{shiftX} ) + ( \text{scaledW} \gg 1 ) ) / \text{scaledW} \quad (\text{F-47})$$ + +$$\text{scaleY} = ( ( \text{refH} \ll \text{shiftY} ) + ( \text{scaledH} \gg 1 ) ) / \text{scaledH} \quad (\text{F-48})$$ + +7. The variables `offsetX`, `addX`, and `deltaX` are derived by + +$$\text{offsetX} = \text{ScaledRefLayerLeftOffset} / \text{subW} \quad (\text{F-49})$$ + +$$\text{addX} = ( ( ( \text{refW} * ( 2 + \text{phaseX} ) ) \ll ( \text{shiftX} - 2 ) ) + ( \text{scaledW} \gg 1 ) ) / \text{scaledW} \\ + ( 1 \ll ( \text{shiftX} - 5 ) ) \quad (\text{F-50})$$ + +$$\text{deltaX} = 4 * ( 2 + \text{refPhaseX} ) \quad (\text{F-51})$$ + +8. The variables `offsetY`, `addY`, and `deltaY` are derived as follows: + +- If `RefLayerFrameMbsOnlyFlag` is equal to 1 and `frame_mbs_only_flag` is equal to 1, the variables `offsetY`, `addY`, and `deltaY` are derived by + +$$\text{offsetY} = \text{ScaledRefLayerTopOffset} / \text{subH} \quad (\text{F-52})$$ + +$$\text{addY} = ( ( ( \text{refH} * ( 2 + \text{phaseY} ) ) \ll ( \text{shiftY} - 2 ) ) + ( \text{scaledH} \gg 1 ) ) / \text{scaledH} \\ + ( 1 \ll ( \text{shiftY} - 5 ) ) \quad (\text{F-53})$$ + +$$\text{deltaY} = 4 * ( 2 + \text{refPhaseY} ) \quad (\text{F-54})$$ + +- Otherwise (`RefLayerFrameMbsOnlyFlag` is equal to 0 or `frame_mbs_only_flag` is equal to 0), the variables `offsetY`, `addY`, and `deltaY` are derived by + +$$\text{offsetY} = \text{ScaledRefLayerTopOffset} / ( 2 * \text{subH} ) \quad (\text{F-55})$$ + +$$\text{addY} = ( ( ( \text{refH} * ( 2 + \text{phaseY} ) ) \ll ( \text{shiftY} - 3 ) ) + ( \text{scaledH} \gg 1 ) ) / \text{scaledH} \\ + ( 1 \ll ( \text{shiftY} - 5 ) ) \quad (\text{F-56})$$ + +$$\text{deltaY} = 2 * ( 2 + \text{refPhaseY} ) \quad (\text{F-57})$$ + +NOTE – The variables `subW`, `subH`, `shiftX`, `shiftY`, `scaleX`, `scaleY`, `offsetX`, `offsetY`, `addX`, `addY`, `deltaX`, and `deltaY` do not depend on the input sample location ( `xP`, `yP` ), the input variable `fieldMbFlag`, or the current macroblock address `CurrMbAddr`. + +The sample location ( $xC, yC$ ) is derived as specified in the following ordered steps: + +1. The inverse macroblock scanning process as specified in clause 6.4.1 is invoked with CurrMbAddr as input and the output is assigned to ( $xM, yM$ ). For this invocation of the process in clause 6.4.1, the current macroblock is treated as field macroblock when fieldMbFlag is equal to 1 and it is treated as frame macroblock when fieldMbFlag is equal to 0. +2. The sample location ( $xC, yC$ ) is derived by + +$$xC = xP + ( xM \gg ( \text{subW} - 1 ) ) \quad (\text{F-58})$$ + +$$yC = yP + ( yM \gg ( \text{subH} - 1 + \text{fieldMbFlag} - \text{field\_pic\_flag} ) ) \quad (\text{F-59})$$ + +3. When RefLayerFrameMbsOnlyFlag is equal to 0 or frame\_mbs\_only\_flag is equal to 0, the vertical component of the sample location ( $xC, yC$ ) is modified by + +$$yC = yC \gg ( 1 - \text{fieldMbFlag} ) \quad (\text{F-60})$$ + +The reference layer sample location ( $xRef16, yRef16$ ) is derived by + +$$xRef16 = ( ( ( xC - \text{offsetX} ) * \text{scaleX} + \text{addX} ) \gg ( \text{shiftX} - 4 ) ) - \text{deltaX} \quad (\text{F-61})$$ + +$$yRef16 = ( ( ( yC - \text{offsetY} ) * \text{scaleY} + \text{addY} ) \gg ( \text{shiftY} - 4 ) ) - \text{deltaY} \quad (\text{F-62})$$ + +#### F.6.4 SVC derivation process for macroblock and sub-macroblock partition indices + +Inputs to this process are: + +- a variable currDQId specifying an identifier for a layer representation, +- a luma location ( $xP, yP$ ) relative to the upper-left luma sample of a macroblock, +- a macroblock type mbType, +- when mbType is equal to P\_8x8, P\_8x8ref0, or B\_8x8, a list of sub-macroblock types subMbType with 4 elements. + +Outputs of this process are: + +- a macroblock partition index mbPartIdx, +- a sub-macroblock partition index subMbPartIdx. + +The variable svcDirectModeFlag is derived as follows: + +- If currDQId is greater than 0 and any of the following conditions are true, svcDirectModeFlag is set equal to 1. + - mbType is equal to B\_Skip or B\_Direct\_16x16 + - mbType is equal to B\_8x8 and $\text{subMbType}[ 2 * ( yP / 8 ) + ( xP / 8 ) ]$ is equal to B\_Direct\_8x8 +- Otherwise, svcDirectModeFlag is set equal to 0. + +Depending on svcDirectModeFlag, the following applies: + +- If svcDirectModeFlag is equal to 0, the derivation process for macroblock and sub-macroblock partition indices as specified in clause 6.4.13.4 is invoked with the luma location ( $xP, yP$ ), the macroblock type mbType, and, when mbType is equal to P\_8x8, P\_8x8ref0, or B\_8x8, the list of sub-macroblock types subMbType as the inputs and the outputs are the macroblock partition index mbPartIdx and the sub-macroblock partition index subMbPartIdx. +- Otherwise, if mbType is equal to B\_Skip or B\_Direct\_16x16, mbPartIdx is set equal to 0 and subMbPartIdx is set equal to 0. +- Otherwise (currDQId is greater than 0, mbType is equal to B\_8x8, and $\text{subMbType}[ 2 * ( yP / 8 ) + ( xP / 8 ) ]$ is equal to B\_Direct\_8x8), mbPartIdx is set equal to ( $2 * ( yP / 8 ) + ( xP / 8 )$ ) and subMbPartIdx is set equal to 0. + +## F.7 Syntax and semantics + +This clause specifies syntax and semantics for coded video sequences that conform to one or more of the profiles specified in this annex. + +### F.7.1 Method of specifying syntax in tabular form + +The specifications in clause 7.1 apply. + +### F.7.2 Specification of syntax functions, categories, and descriptors + +The specifications in clause 7.2 apply. + +### F.7.3 Syntax in tabular form + +#### F.7.3.1 NAL unit syntax + +The syntax table is specified in clause 7.3.1. + +##### F.7.3.1.1 NAL unit header SVC extension syntax + +| nal_unit_header_svc_extension( ) { | C | Descriptor | +|------------------------------------|-----|------------| +| idr_flag | All | u(1) | +| priority_id | All | u(6) | +| no_inter_layer_pred_flag | All | u(1) | +| dependency_id | All | u(3) | +| quality_id | All | u(4) | +| temporal_id | All | u(3) | +| use_ref_base_pic_flag | All | u(1) | +| discardable_flag | All | u(1) | +| output_flag | All | u(1) | +| reserved_three_2bits | All | u(2) | +| } | | | + +#### F.7.3.2 Raw byte sequence payloads and RBSP trailing bits syntax + +##### F.7.3.2.1 Sequence parameter set RBSP syntax + +The syntax table is specified in clause 7.3.2.1. + +###### F.7.3.2.1.1 Sequence parameter set data syntax + +The syntax table is specified in clause 7.3.2.1.1. + +###### F.7.3.2.1.1.1 Scaling list syntax + +The syntax table is specified in clause 7.3.2.1.1.1. + +###### F.7.3.2.1.2 Sequence parameter set extension RBSP syntax + +The syntax table is specified in clause 7.3.2.1.2. + +###### F.7.3.2.1.3 Subset sequence parameter set RBSP syntax + +The syntax table is specified in clause 7.3.2.1.3. + +#### F.7.3.2.1.4 Sequence parameter set SVC extension syntax + +| seq_parameter_set_svc_extension() { | C | Descriptor | +|-----------------------------------------------------------|---|------------| +| inter_layer_deblocking_filter_control_present_flag | 0 | u(1) | +| extended_spatial_scalability_idc | 0 | u(2) | +| if( ChromaArrayType == 1 ChromaArrayType == 2 ) | | | +| chroma_phase_x_plus1_flag | 0 | u(1) | +| if( ChromaArrayType == 1 ) | | | +| chroma_phase_y_plus1 | 0 | u(2) | +| if( extended_spatial_scalability_idc == 1 ) { | | | +| if( ChromaArrayType > 0 ) { | | | +| seq_ref_layer_chroma_phase_x_plus1_flag | 0 | u(1) | +| seq_ref_layer_chroma_phase_y_plus1 | 0 | u(2) | +| } | | | +| seq_scaled_ref_layer_left_offset | 0 | se(v) | +| seq_scaled_ref_layer_top_offset | 0 | se(v) | +| seq_scaled_ref_layer_right_offset | 0 | se(v) | +| seq_scaled_ref_layer_bottom_offset | 0 | se(v) | +| } | | | +| seq_tcoeff_level_prediction_flag | 0 | u(1) | +| if( seq_tcoeff_level_prediction_flag ) { | | | +| adaptive_tcoeff_level_prediction_flag | 0 | u(1) | +| } | | | +| slice_header_restriction_flag | 0 | u(1) | +| } | | | + +#### F.7.3.2.2 Picture parameter set RBSP syntax + +The syntax table is specified in clause 7.3.2.2. + +#### F.7.3.2.3 Supplemental enhancement information RBSP syntax + +The syntax table is specified in clause 7.3.2.3. + +##### F.7.3.2.3.1 Supplemental enhancement information message syntax + +The syntax table is specified in clause 7.3.2.3.1. + +#### F.7.3.2.4 Access unit delimiter RBSP syntax + +The syntax table is specified in clause 7.3.2.4. + +#### F.7.3.2.5 End of sequence RBSP syntax + +The syntax table is specified in clause 7.3.2.5. + +#### F.7.3.2.6 End of stream RBSP syntax + +The syntax table is specified in clause 7.3.2.6. + +#### F.7.3.2.7 Filler data RBSP syntax + +The syntax table is specified in clause 7.3.2.7. + +#### F.7.3.2.8 Slice layer without partitioning RBSP syntax + +The syntax table is specified in clause 7.3.2.8. + +#### F.7.3.2.9 Slice data partition RBSP syntax + +Slice data partition syntax is not present in coded video sequences conforming to any of the profiles specified in this annex. + +#### F.7.3.2.10 RBSP slice trailing bits syntax + +The syntax table is specified in clause 7.3.2.10. + +#### F.7.3.2.11 RBSP trailing bits syntax + +The syntax table is specified in clause 7.3.2.11. + +#### F.7.3.2.12 Prefix NAL unit RBSP syntax + +The syntax table is specified in clause 7.3.2.12. + +##### F.7.3.2.12.1 Prefix NAL unit SVC syntax + +| prefix_nal_unit_svc( ) { | C | Descriptor | +|-------------------------------------------------------------------------|---|------------| +| if( nal_ref_idc != 0 ) { | | | +| store_ref_base_pic_flag | 2 | u(1) | +| if( ( use_ref_base_pic_flag store_ref_base_pic_flag ) && !idr_flag ) | | | +| dec_ref_base_pic_marking( ) | 2 | | +| additional_prefix_nal_unit_extension_flag | 2 | u(1) | +| if( additional_prefix_nal_unit_extension_flag == 1 ) | | | +| while( more_rbsp_data( ) ) | | | +| additional_prefix_nal_unit_extension_data_flag | 2 | u(1) | +| rbsp_trailing_bits( ) | 2 | | +| } else if( more_rbsp_data( ) ) { | | | +| while( more_rbsp_data( ) ) | | | +| additional_prefix_nal_unit_extension_data_flag | 2 | u(1) | +| rbsp_trailing_bits( ) | 2 | | +| } | | | +| } | | | + +#### F.7.3.2.13 Slice layer extension RBSP syntax + +The syntax table is specified in clause 7.3.2.13. + +### F.7.3.3 Slice header syntax + +The syntax table is specified in clause 7.3.3. + +#### F.7.3.3.1 Reference picture list modification syntax + +The syntax table is specified in clause 7.3.3.1. + +#### F.7.3.3.2 Prediction weight table syntax + +The syntax table is specified in clause 7.3.3.2. + +#### F.7.3.3.3 Decoded reference picture marking syntax + +The syntax table is specified in clause 7.3.3.3. + +#### F.7.3.3.4 Slice header in scalable extension syntax + +| slice_header_in_scalable_extension( ) { | C | Descriptor | +|-----------------------------------------|---|------------| +| first_mb_in_slice | 2 | ue(v) | +| slice_type | 2 | ue(v) | +| pic_parameter_set_id | 2 | ue(v) | +| if( separate_colour_plane_flag == 1 ) | | | +| colour_plane_id | 2 | u(2) | +| frame_num | 2 | u(v) | + +| | | | +|-----------------------------------------------------------------------------------------------------------|---|-------| +| if( !frame_mbs_only_flag ) { | | | +| field_pic_flag | 2 | u(1) | +| if( field_pic_flag ) | | | +| bottom_field_flag | 2 | u(1) | +| } | | | +| if( idr_flag == 1 ) | | | +| idr_pic_id | 2 | ue(v) | +| if( pic_order_cnt_type == 0 ) { | | | +| pic_order_cnt_lsb | 2 | u(v) | +| if( bottom_field_pic_order_in_frame_present_flag && !field_pic_flag ) | | | +| delta_pic_order_cnt_bottom | 2 | se(v) | +| } | | | +| if( pic_order_cnt_type == 1 && !delta_pic_order_always_zero_flag ) { | | | +| delta_pic_order_cnt[ 0 ] | 2 | se(v) | +| if( bottom_field_pic_order_in_frame_present_flag && !field_pic_flag ) | | | +| delta_pic_order_cnt[ 1 ] | 2 | se(v) | +| } | | | +| if( redundant_pic_cnt_present_flag ) | | | +| redundant_pic_cnt | 2 | ue(v) | +| if( quality_id == 0 ) { | | | +| if( slice_type == EB ) | | | +| direct_spatial_mv_pred_flag | 2 | u(1) | +| if( slice_type == EP slice_type == EB ) { | | | +| num_ref_idx_active_override_flag | 2 | u(1) | +| if( num_ref_idx_active_override_flag ) { | | | +| num_ref_idx_l0_active_minus1 | 2 | ue(v) | +| if( slice_type == EB ) | | | +| num_ref_idx_l1_active_minus1 | 2 | ue(v) | +| } | | | +| } | | | +| ref_pic_list_modification() | 2 | | +| if( ( weighted_pred_flag && slice_type == EP )
( weighted_bipred_idc == 1 && slice_type == EB ) ) { | | | +| if( !no_inter_layer_pred_flag ) | | | +| base_pred_weight_table_flag | 2 | u(1) | +| if( no_inter_layer_pred_flag !base_pred_weight_table_flag ) | | | +| pred_weight_table() | 2 | | +| } | | | +| if( nal_ref_idc != 0 ) { | | | +| dec_ref_pic_marking() | 2 | | +| if( !slice_header_restriction_flag ) { | | | +| store_ref_base_pic_flag | 2 | u(1) | +| if( ( use_ref_base_pic_flag store_ref_base_pic_flag ) &&
!idr_flag ) | | | +| dec_ref_base_pic_marking() | 2 | | +| } | | | +| } | | | +| } | | | +| if( entropy_coding_mode_flag && slice_type != EI ) | | | + +| | | | +|---------------------------------------------------------------------------------------------|---|-------| +| cabac_init_idc | 2 | ue(v) | +| slice_qp_delta | 2 | se(v) | +| if( deblocking_filter_control_present_flag ) { | | | +| disable_deblocking_filter_idc | 2 | ue(v) | +| if( disable_deblocking_filter_idc != 1 ) { | | | +| slice_alpha_c0_offset_div2 | 2 | se(v) | +| slice_beta_offset_div2 | 2 | se(v) | +| } | | | +| } | | | +| if( num_slice_groups_minus1 > 0 && slice_group_map_type >= 3 && slice_group_map_type <= 5 ) | | | +| slice_group_change_cycle | 2 | u(v) | +| if( !no_inter_layer_pred_flag && quality_id == 0 ) { | | | +| ref_layer_dq_id | 2 | ue(v) | +| if( inter_layer_deblocking_filter_control_present_flag ) { | | | +| disable_inter_layer_deblocking_filter_idc | 2 | ue(v) | +| if( disable_inter_layer_deblocking_filter_idc != 1 ) { | | | +| inter_layer_slice_alpha_c0_offset_div2 | 2 | se(v) | +| inter_layer_slice_beta_offset_div2 | 2 | se(v) | +| } | | | +| } | | | +| constrained_intra_resampling_flag | 2 | u(1) | +| if( extended_spatial_scalability_idc == 2 ) { | | | +| if( ChromaArrayType > 0 ) { | | | +| ref_layer_chroma_phase_x_plus1_flag | 2 | u(1) | +| ref_layer_chroma_phase_y_plus1 | 2 | u(2) | +| } | | | +| scaled_ref_layer_left_offset | 2 | se(v) | +| scaled_ref_layer_top_offset | 2 | se(v) | +| scaled_ref_layer_right_offset | 2 | se(v) | +| scaled_ref_layer_bottom_offset | 2 | se(v) | +| } | | | +| } | | | +| if( !no_inter_layer_pred_flag ) { | | | +| slice_skip_flag | 2 | u(1) | +| if( slice_skip_flag ) | | | +| num_mbs_in_slice_minus1 | 2 | ue(v) | +| else { | | | +| adaptive_base_mode_flag | 2 | u(1) | +| if( !adaptive_base_mode_flag ) | | | +| default_base_mode_flag | 2 | u(1) | +| if( !default_base_mode_flag ) { | | | +| adaptive_motion_prediction_flag | 2 | u(1) | +| if( !adaptive_motion_prediction_flag ) | | | +| default_motion_prediction_flag | 2 | u(1) | +| } | | | +| adaptive_residual_prediction_flag | 2 | u(1) | +| if( !adaptive_residual_prediction_flag ) | | | + +| | | | +|------------------------------------------------------------|---|------| +| default_residual_prediction_flag | 2 | u(1) | +| } | | | +| if( adaptive_tcoeff_level_prediction_flag ) | | | +| tcoeff_level_prediction_flag | 2 | u(1) | +| } | | | +| if( !slice_header_restriction_flag && !slice_skip_flag ) { | | | +| scan_idx_start | 2 | u(4) | +| scan_idx_end | 2 | u(4) | +| } | | | +| } | | | + +**F.7.3.3.5 Decoded reference base picture marking syntax** + +| | | | +|----------------------------------------------------------|----------|-------------------| +| dec_ref_base_pic_marking() { | C | Descriptor | +| adaptive_ref_base_pic_marking_mode_flag | 2 | u(1) | +| if( adaptive_ref_base_pic_marking_mode_flag ) | | | +| do { | | | +| memory_management_base_control_operation | 2 | ue(v) | +| if( memory_management_base_control_operation == 1 ) | | | +| difference_of_base_pic_nums_minus1 | 2 | ue(v) | +| if( memory_management_base_control_operation == 2 ) | | | +| long_term_base_pic_num | 2 | ue(v) | +| } while( memory_management_base_control_operation != 0 ) | | | +| } | | | + +**F.7.3.4 Slice data syntax** + +The syntax table is specified in clause 7.3.4. + +#### F.7.3.4.1 Slice data in scalable extension syntax + +| slice_data_in_scalable_extension( ) { | C | Descriptor | +|--------------------------------------------------------------------------------------------------------|-----------|--------------| +| if( entropy_coding_mode_flag) | | | +| while( !byte_aligned( ) ) | | | +| cabac_alignment_one_bit | 2 | f(1) | +| CurrMbAddr = first_mb_in_slice * ( 1 + MbaffFrameFlag ) | | | +| moreDataFlag = 1 | | | +| prevMbSkipped = 0 | | | +| do { | | | +| if( slice_type != EI ) | | | +| if( !entropy_coding_mode_flag ) { | | | +| mb_skip_run | 2 | ue(v) | +| prevMbSkipped = ( mb_skip_run > 0 ) | | | +| for( i = 0; i < mb_skip_run; i++ ) | | | +| CurrMbAddr = NextMbAddress( CurrMbAddr ) | | | +| if( mb_skip_run > 0 ) | | | +| moreDataFlag = more_rbsp_data( ) | | | +| } else { | | | +| mb_skip_flag | 2 | ae(v) | +| moreDataFlag = !mb_skip_flag | | | +| } | | | +| if( moreDataFlag ) { | | | +| if( MbaffFrameFlag && ( ( CurrMbAddr % 2 ) == 0
( ( CurrMbAddr % 2 ) == 1 && prevMbSkipped ) ) ) | | | +| mb_field_decoding_flag | 2 | u(1) ae(v) | +| macroblock_layer_in_scalable_extension( ) | 2 3 4 | | +| } | | | +| if( !entropy_coding_mode_flag ) | | | +| moreDataFlag = more_rbsp_data( ) | | | +| else { | | | +| if( slice_type != EI ) | | | +| prevMbSkipped = mb_skip_flag | | | +| if( MbaffFrameFlag && ( CurrMbAddr % 2 ) == 0 ) | | | +| moreDataFlag = 1 | | | +| else { | | | +| end_of_slice_flag | 2 | ae(v) | +| moreDataFlag = !end_of_slice_flag | | | +| } | | | +| } | | | +| CurrMbAddr = NextMbAddress( CurrMbAddr ) | | | +| } while( moreDataFlag ) | | | +| } | | | + +#### F.7.3.5 Macroblock layer syntax + +The syntax table is specified in clause 7.3.5. + +#### F.7.3.5.1 Macroblock prediction syntax + +The syntax table is specified in clause 7.3.5.1. + +#### F.7.3.5.2 Sub-macroblock prediction syntax + +The syntax table is specified in clause 7.3.5.2. + +#### F.7.3.5.3 Residual data syntax + +The syntax table is specified in clause 7.3.5.3. + +##### F.7.3.5.3.1 Residual luma syntax + +The syntax table is specified in clause 7.3.5.3.1. + +##### F.7.3.5.3.2 Residual block CAVLC syntax + +The syntax table is specified in clause 7.3.5.3.2. + +##### F.7.3.5.3.3 Residual block CABAC syntax + +The syntax table is specified in clause 7.3.5.3.3. + +#### F.7.3.6 Macroblock layer in scalable extension syntax + +| macroblock_layer_in_scalable_extension() { | C | Descriptor | +|------------------------------------------------------------------------------------------------------|---|---------------| +| if( InCropWindow( CurrMbAddr ) && adaptive_base_mode_flag ) | | | +| base_mode_flag | 2 | u(1) ae(v) | +| if( !base_mode_flag ) | | | +| mb_type | 2 | ue(v) ae(v) | +| if( mb_type == I_PCM ) { | | | +| while( !byte_aligned() ) | | | +| pcm_alignment_zero_bit | 3 | f(1) | +| for( i = 0; i < 256; i++ ) | | | +| pcm_sample_luma[ i ] | 3 | u(v) | +| for( i = 0; i < 2 * MbWidthC * MbHeightC; i++ ) | | | +| pcm_sample_chroma[ i ] | 3 | u(v) | +| } else { | | | +| if( !base_mode_flag ) { | | | +| noSubMbPartSizeLessThan8x8Flag = 1 | | | +| if( mb_type != I_NxN && MbPartPredMode( mb_type, 0 ) != Intra_16x16 && NumMbPart( mb_type ) == 4 ) { | | | +| sub_mb_pred_in_scalable_extension( mb_type ) | 2 | | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( sub_mb_type[ mbPartIdx ] != B_Direct_8x8 ) { | | | +| if( NumSubMbPart( sub_mb_type[ mbPartIdx ] ) > 1 ) | | | +| noSubMbPartSizeLessThan8x8Flag = 0 | | | +| } else if( !direct_8x8_inference_flag ) | | | +| noSubMbPartSizeLessThan8x8Flag = 0 | | | +| } else { | | | +| if( transform_8x8_mode_flag && mb_type == I_NxN ) | | | +| transform_size_8x8_flag | 2 | u(1) ae(v) | +| mb_pred_in_scalable_extension( mb_type ) | 2 | | +| } | | | +| } | | | +| } | | | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---------------| +| if( adaptive_residual_prediction_flag && slice_type != EI && InCropWindow( CurrMbAddr ) && ( base_mode_flag ( MbPartPredMode( mb_type, 0 ) != Intra_16x16 && MbPartPredMode( mb_type, 0 ) != Intra_8x8 && MbPartPredMode( mb_type, 0 ) != Intra_4x4 ) ) ) | | | +| residual_prediction_flag | 2 | u(1) ae(v) | +| if( scan_idx_end >= scan_idx_start ) { | | | +| if( base_mode_flag MbPartPredMode( mb_type, 0 ) != Intra_16x16 ) { | | | +| coded_block_pattern | 2 | me(v) ae(v) | +| if( CodedBlockPatternLuma > 0 && transform_8x8_mode_flag && ( base_mode_flag ( mb_type != I_NxN && noSubMbPartSizeLessThan8x8Flag && ( mb_type != B_Direct_16x16 direct_8x8_inference_flag ) ) ) ) | | | +| transform_size_8x8_flag | 2 | u(1) ae(v) | +| } | | | +| if( CodedBlockPatternLuma > 0 CodedBlockPatternChroma > 0 MbPartPredMode( mb_type, 0 ) == Intra_16x16 ) { | | | +| mb_qp_delta | 2 | se(v) ae(v) | +| residual( scan_idx_start, scan_idx_end ) | 3 4 | | +| } | | | +| } | | | +| } | | | +| } | | | + +#### F.7.3.6.1 Macroblock prediction in scalable extension syntax + +| mb_pred_in_scalable_extension( mb_type ) { | C | Descriptor | +|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| if( MbPartPredMode( mb_type, 0 ) == Intra_4x4 MbPartPredMode( mb_type, 0 ) == Intra_8x8 MbPartPredMode( mb_type, 0 ) == Intra_16x16 ) { | | | +| if( MbPartPredMode( mb_type, 0 ) == Intra_4x4 ) | | | +| for( luma4x4BlkIdx = 0; luma4x4BlkIdx < 16; luma4x4BlkIdx++ ) { | | | +| prev_intra4x4_pred_mode_flag[ luma4x4BlkIdx ] | 2 | u(1) ae(v) | +| if( !prev_intra4x4_pred_mode_flag[ luma4x4BlkIdx ] ) | | | +| rem_intra4x4_pred_mode[ luma4x4BlkIdx ] | 2 | u(3) ae(v) | +| } | | | +| if( MbPartPredMode( mb_type, 0 ) == Intra_8x8 ) | | | +| for( luma8x8BlkIdx = 0; luma8x8BlkIdx < 4; luma8x8BlkIdx++ ) { | | | +| prev_intra8x8_pred_mode_flag[ luma8x8BlkIdx ] | 2 | u(1) ae(v) | +| if( !prev_intra8x8_pred_mode_flag[ luma8x8BlkIdx ] ) | | | +| rem_intra8x8_pred_mode[ luma8x8BlkIdx ] | 2 | u(3) ae(v) | +| } | | | +| if( ChromaArrayType != 0 ) | | | +| intra_chroma_pred_mode | 2 | ue(v) ae(v) | +| } else if( MbPartPredMode( mb_type, 0 ) != Direct ) { | | | +| if( InCropWindow( CurrMbAddr ) && adaptive_motion_prediction_flag ) { | | | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( MbPartPredMode( mb_type, mbPartIdx ) != Pred_L1 ) | | | +| motion_prediction_flag_10[ mbPartIdx ] | 2 | u(1) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( MbPartPredMode( mb_type, mbPartIdx ) != Pred_L0 ) | | | +| motion_prediction_flag_11[ mbPartIdx ] | 2 | u(1) ae(v) | +| } | | | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( ( num_ref_idx_10_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
MbPartPredMode( mb_type, mbPartIdx ) != Pred_L1 &&
!motion_prediction_flag_10[ mbPartIdx ] ) | | | +| ref_idx_10[ mbPartIdx ] | 2 | te(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( ( num_ref_idx_11_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
MbPartPredMode( mb_type, mbPartIdx ) != Pred_L0 &&
!motion_prediction_flag_11[ mbPartIdx ] ) | | | +| ref_idx_11[ mbPartIdx ] | 2 | te(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( MbPartPredMode( mb_type, mbPartIdx ) != Pred_L1 ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_10[ mbPartIdx ][ 0 ][ compIdx ] | 2 | se(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( MbPartPredMode( mb_type, mbPartIdx ) != Pred_L0 ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_11[ mbPartIdx ][ 0 ][ compIdx ] | 2 | se(v) ae(v) | +| } | | | +| } | | | + +### F.7.3.6.2 Sub-macroblock prediction in scalable extension syntax + +| sub_mb_pred_in_scalable_extension( mb_type ) { | C | Descriptor | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| sub_mb_type [ mbPartIdx ] | 2 | ue(v) ae(v) | +| if( InCropWindow( CurrMbAddr ) && adaptive_motion_prediction_flag ) { | | | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Direct &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L1 ) | | | +| motion_prediction_flag_10 [ mbPartIdx ] | 2 | u(1) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Direct &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L0 ) | | | +| motion_prediction_flag_11 [ mbPartIdx ] | 2 | u(1) ae(v) | +| } | | | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( ( num_ref_idx_10_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
mb_type != P_8x8ref0 &&
sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L1 &&
!motion_prediction_flag_10[ mbPartIdx ] ) | | | +| ref_idx_10 [ mbPartIdx ] | 2 | te(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( ( num_ref_idx_11_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L0 &&
!motion_prediction_flag_11[ mbPartIdx ] ) | | | +| ref_idx_11 [ mbPartIdx ] | 2 | te(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L1 ) | | | +| for( subMbPartIdx = 0;
subMbPartIdx < NumSubMbPart( sub_mb_type[ mbPartIdx ] );
subMbPartIdx++ ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_10 [ mbPartIdx ][ subMbPartIdx ][ compIdx ] | 2 | se(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L0 ) | | | +| for( subMbPartIdx = 0;
subMbPartIdx < NumSubMbPart( sub_mb_type[ mbPartIdx ] );
subMbPartIdx++ ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_11 [ mbPartIdx ][ subMbPartIdx ][ compIdx ] | 2 | se(v) ae(v) | +| } | | | + +## F.7.4 Semantics + +Semantics associated with the syntax structures and syntax elements within these structures (in clause F.7.3 and in clause 7.3 by reference in clause F.7.3) are specified in this clause and by reference to clause 7.4. When the semantics of a syntax element are specified using a table or a set of tables, any values that are not specified in the table(s) shall not be present in the bitstream unless otherwise specified in this Recommendation | International Standard. + +Sub-bitstreams that are derived according to the process specified in clause F.8.8.1 shall conform to one or more of the profiles specified in Annex A or one or more of the profiles specified in this annex. + +One or more sub-bitstreams shall conform to one or more of the profiles specified in Annex A. The decoding for these sub-bitstreams is specified in clauses 2 to 9 and Annexes B to E. + +The decoding for bitstreams conforming to one or more of the profiles specified in this annex is completely specified in this annex with reference made to clauses 2 to 9 and Annexes B to E. + +A specification or a process in clauses 2 to 9 and Annexes B to E, may be used as is or by specifying assignments or alternative meanings of certain parts. + +This clause describes the semantics of syntax elements. The syntax elements appear multiple times in the bitstream and in each access unit. The meaning of each syntax element and derived variables depends on the position of the syntax structure in the bitstream in which it is contained. A decoder conforming to this Recommendation | International Standard processes the syntax structures in decoding order and determines the semantics according to the position derived from that. + +#### F.7.4.1 NAL unit semantics + +The semantics for the syntax elements in clause F.7.3.1 are specified in clause 7.4.1. The following specifications additionally apply. + +For NAL units with `nal_unit_type` equal to 14, `nal_ref_idc` shall be identical to `nal_ref_idc` of the associated NAL unit, which succeeds the NAL unit with `nal_unit_type` equal to 14 in decoding order. + +The value of `nal_ref_idc` shall be the same for all VCL NAL units of a dependency representation. + +The variable `refNalRefIdc` is derived as follows: + +- If `nal_unit_type` is not equal to 20 or `dependency_id` is equal to the minimum value of `dependency_id` for all VCL NAL units of the coded picture, `refNalRefIdc` is set equal to 0. +- Otherwise (`nal_unit_type` is equal to 20 and `dependency_id` is not equal to the minimum value of `dependency_id` for all VCL NAL units of the coded picture), `refNalRefIdc` is set equal to the maximum value of `nal_ref_idc` for all VCL NAL units of the coded picture with a value of `dependency_id` less than the current value of `dependency_id`. + +When `refNalRefIdc` is greater than 0, the value of `nal_ref_idc` shall not be equal to 0. + +`nal_ref_idc` equal to 0 for a NAL unit containing a slice and having a value of `dependency_id` that is equal to the maximum value of `dependency_id` in the coded picture indicates that all coded slice NAL units of the coded picture are coded slice NAL units of a non-reference picture. + +`nal_ref_idc` greater than 0 for a NAL unit containing a slice and having a value of `dependency_id` that is equal to the maximum value of `dependency_id` in the coded picture indicates that all coded slice NAL units of the coded picture are coded slice NAL units of a reference picture. + +##### F.7.4.1.1 NAL unit header SVC extension semantics + +The syntax elements `idr_flag`, `priority_id`, `no_inter_layer_pred_flag`, `dependency_id`, `quality_id`, `temporal_id`, `use_ref_base_pic_flag`, `discardable_flag`, and `output_flag`, when present in a prefix NAL unit, are considered as if they were present in the associated NAL unit. + +**`idr_flag`** equal to 1 specifies that the current coded picture is an IDR picture when the value of `dependency_id` for the NAL unit is equal to the maximum value of `dependency_id` in the coded picture. `idr_flag` equal to 0 specifies that the current coded picture is not an IDR picture when the value of `dependency_id` for the NAL unit is equal to the maximum value of `dependency_id` in the coded picture. The value of `idr_flag` shall be the same for all NAL units of a dependency representation. + +NOTE 1 – The classification of a coded picture as IDR picture and the partitioning of a sequence of access units in coded video sequences depends on the maximum value of `dependency_id` that is present in the associated NAL units. When NAL units are removed from a bitstream, e.g. in order to adjust the bitstream to the capabilities of a receiving device, the maximum value of `dependency_id` in the coded pictures may change and hence the classification of coded pictures as IDR pictures may change and with that the partitioning of the sequence of access units into coded video sequences may change. + +When `idr_flag` is equal to 1 for a prefix NAL unit, the associated NAL unit shall have `nal_unit_type` equal to 5. When `idr_flag` is equal to 0 for a prefix NAL unit, the associated NAL unit shall have `nal_unit_type` equal to 1. + +When `nal_ref_idc` is equal to 0, the value of `idr_flag` shall be equal to 0. + +For NAL units, in which `idr_flag` is present, the variable `IdrPicFlag` derived in clause 7.4.1 is modified by setting it equal to `idr_flag`. + +**`priority_id`** specifies a priority identifier for the NAL unit. The assignment of values to `priority_id` is constrained by the sub-bitstream extraction process as specified in clause F.8.8.1. + +NOTE 2 – The syntax element *priority\_id* is not required by the decoding process specified in this Recommendation | International Standard. The syntax element *priority\_id* may be used as determined by the application within the specified constraints. + +**no\_inter\_layer\_pred\_flag** specifies whether inter-layer prediction may be used for decoding the coded slice. When *no\_inter\_layer\_pred\_flag* is equal to 1, inter-layer prediction is not used for decoding the coded slice. When *no\_inter\_layer\_pred\_flag* is equal to 0, inter-layer prediction may be used for decoding the coded slice as signalled in the macroblock layer. + +For prefix NAL units, *no\_inter\_layer\_pred\_flag* shall be equal to 1. When *nal\_unit\_type* is equal to 20 and *quality\_id* is greater than 0, *no\_inter\_layer\_pred\_flag* shall be equal to 0. + +The variable *MinNoInterLayerPredFlag* is set equal to the minimum value of *no\_inter\_layer\_pred\_flag* for the slices of the layer representation. + +**dependency\_id** specifies a dependency identifier for the NAL unit. *dependency\_id* shall be equal to 0 in prefix NAL units. The assignment of values to *dependency\_id* is constrained by the sub-bitstream extraction process as specified in clause F.8.8.1. + +**quality\_id** specifies a quality identifier for the NAL unit. *quality\_id* shall be equal to 0 in prefix NAL units. The assignment of values to *quality\_id* is constrained by the sub-bitstream extraction process as specified in clause F.8.8.1. + +The variable *DQId* is derived by + +$$DQId = ( \text{dependency\_id} \ll 4 ) + \text{quality\_id} \quad (\text{F-63})$$ + +When *nal\_unit\_type* is equal to 20, the bitstream shall not contain data that result in *DQId* equal to 0. + +**temporal\_id** specifies a temporal identifier for the NAL unit. The assignment of values to *temporal\_id* is constrained by the sub-bitstream extraction process as specified in clause F.8.8.1. + +The value of *temporal\_id* shall be the same for all prefix NAL units and coded slice in scalable extension NAL units of an access unit. When an access unit contains any NAL unit with *nal\_unit\_type* equal to 5 or *idr\_flag* equal to 1, *temporal\_id* shall be equal to 0. + +**use\_ref\_base\_pic\_flag** equal to 1 specifies that reference base pictures (when present) and decoded pictures (when reference base pictures are not present) are used as reference pictures for inter prediction as specified in clause F.8.2.3. *use\_ref\_base\_pic\_flag* equal to 0 specifies that reference base pictures are not used as reference pictures for inter prediction (i.e., only decoded pictures are used for inter prediction). + +The values of *use\_ref\_base\_pic\_flag* shall be the same for all NAL units of a dependency representation. + +**discardable\_flag** equal to 1 specifies that the current NAL unit is not used for decoding dependency representations that are part of the current coded picture or any subsequent coded picture in decoding order and have a greater value of *dependency\_id* than the current NAL unit. *discardable\_flag* equal to 0 specifies that the current NAL unit may be used for decoding dependency representations that are part of the current coded picture or any subsequent coded picture in decoding order and have a greater value of *dependency\_id* than the current NAL unit. + +**output\_flag** affects the decoded picture output and removal processes as specified in Annex C. The value of *output\_flag* shall be the same for all NAL units of a dependency representation. For any particular value of *dependency\_id*, the value of *output\_flag* shall be the same for both fields of a complementary field pair. + +**reserved\_three\_2bits** shall be equal to 3. Other values of *reserved\_three\_2bits* may be specified in the future by ITU-T | ISO/IEC. Decoders shall ignore the value of *reserved\_three\_2bits*. + +#### F.7.4.1.2 Order of NAL units and association to coded pictures, access units, and video sequences + +This clause specifies constraints on the order of NAL units in the bitstream. Any order of NAL units in the bitstream obeying these constraints is referred to in the text as the decoding order of NAL units. Within a NAL unit, the syntax in clauses 7.3, D.1, E.1, F.7.3, F.13.1, and F.14.1 specifies the decoding order of syntax elements. Decoders shall be capable of receiving NAL units and their syntax elements in decoding order. + +##### F.7.4.1.2.1 Order of SVC sequence parameter set RBSPs and picture parameter set RBSPs and their activation + +NOTE 1 – The sequence and picture parameter set mechanism decouples the transmission of infrequently changing information from the transmission of coded macroblock data. Sequence and picture parameter sets may, in some applications, be conveyed "out-of-band" using a reliable transport mechanism. + +A picture parameter set RBSP includes parameters that can be referred to by the coded slice NAL units of one or more layer representations of one or more coded pictures. + +Each picture parameter set RBSP is initially considered not active at the start of the operation of the decoding process. At most one picture parameter set RBSP is considered as the active picture parameter set RBSP at any given moment during + +the operation of the decoding process, and when any particular picture parameter set RBSP becomes the active picture parameter set RBSP, the previously-active picture parameter set RBSP (if any) is deactivated. + +In addition to the active picture parameter set RBSP, zero or more picture parameter set RBSPs may be specifically active for layer representations (with a particular value of DQId less than DQIdMax) that may be referred to through inter-layer prediction in decoding the target layer representation. Such a picture parameter set RBSP is referred to as active layer picture parameter set RBSP for the particular value of DQId (less than DQIdMax). The restrictions on active picture parameter set RBSPs also apply to active layer picture parameter set RBSPs with a particular value of DQId. + +When a picture parameter set RBSP (with a particular value of pic\_parameter\_set\_id) is not the active picture parameter set RBSP and it is referred to by a coded slice NAL unit with DQId equal to DQIdMax (using that value of pic\_parameter\_set\_id), it is activated. This picture parameter set RBSP is called the active picture parameter set RBSP until it is deactivated when another picture parameter set RBSP becomes the active picture parameter set RBSP. A picture parameter set RBSP, with that particular value of pic\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a picture parameter set RBSP (with a particular value of pic\_parameter\_set\_id) is not the active layer picture parameter set for a particular value of DQId less than DQIdMax and it is referred to by a coded slice NAL unit with the particular value of DQId (using that value of pic\_parameter\_set\_id), it is activated for layer representations with the particular value of DQId. This picture parameter set RBSP is called the active layer picture parameter set RBSP for the particular value of DQId until it is deactivated when another picture parameter set RBSP becomes the active layer picture parameter set RBSP for the particular value of DQId or when decoding an access unit with DQIdMax less than or equal to the particular value of DQId. A picture parameter set RBSP, with that particular value of pic\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +Any picture parameter set NAL unit containing the value of pic\_parameter\_set\_id for the active picture parameter set RBSP for a coded picture shall have the same content as that of the active picture parameter set RBSP for the coded picture unless it follows the last VCL NAL unit of the coded picture and precedes the first VCL NAL unit of another coded picture. Any picture parameter set NAL unit containing the value of pic\_parameter\_set\_id for the active layer picture parameter set RBSP for a particular value of DQId less than DQIdMax for a coded picture shall have the same content as that of the active layer picture parameter set RBSP for the particular value of DQId for the coded picture unless it follows the last VCL NAL unit of the coded picture and precedes the first VCL NAL unit of another coded picture. + +When a picture parameter set NAL unit with a particular value of pic\_parameter\_set\_id is received, its content replaces the content of the previous picture parameter set NAL unit, in decoding order, with the same value of pic\_parameter\_set\_id (when a previous picture parameter set NAL unit with the same value of pic\_parameter\_set\_id was present in the bitstream). + +NOTE 2 – A decoder must be capable of simultaneously storing the contents of the picture parameter sets for all values of pic\_parameter\_set\_id. The content of the picture parameter set with a particular value of pic\_parameter\_set\_id is overwritten when a new picture parameter set NAL unit with the same value of pic\_parameter\_set\_id is received. + +An SVC sequence parameter set RBSP includes parameters that can be referred to by one or more picture parameter set RBSPs or one or more SEI NAL units containing a buffering period SEI message. + +Each SVC sequence parameter set RBSP is initially considered not active at the start of the operation of the decoding process. At most one SVC sequence parameter set RBSP is considered as the active SVC sequence parameter set RBSP at any given moment during the operation of the decoding process, and when any particular SVC sequence parameter set RBSP becomes the active SVC sequence parameter set RBSP, the previously-active SVC sequence parameter set RBSP (if any) is deactivated. + +In addition to the active SVC sequence parameter set RBSP, zero or more SVC sequence parameter set RBSPs may be specifically active for layer representations (with a particular value of DQId less than DQIdMax) that may be referred to through inter-layer prediction in decoding the target layer representation. Such an SVC sequence parameter set RBSP is referred to as active layer SVC sequence parameter set RBSP for the particular value of DQId (less than DQIdMax). The restrictions on active SVC sequence parameter set RBSPs also apply to active layer SVC sequence parameter set RBSPs with a particular value of DQId. + +For the following specification in this clause, the activating buffering period SEI message is specified as follows: + +- If the access unit contains one or more buffering period SEI messages that are included in a scalable nesting SEI message and are associated with values of DQId in the range of $((DQIdMax \gg 4) \ll 4)$ to $((DQIdMax \gg 4) \ll 4) + 15$ , inclusive, the last of these buffering period SEI messages in decoding order is the activating buffering period SEI message. +- Otherwise, if DQIdMax is equal to 0 and the access unit contains a buffering period SEI message that is not included in a scalable nesting SEI message, this buffering period SEI message is the activating buffering period SEI message. +- Otherwise, the access unit does not contain an activating buffering period SEI message. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active SVC sequence parameter set RBSP and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice NAL unit with nal\_unit\_type equal to 1 or 5 (the picture parameter set RBSP becomes the active picture parameter set RBSP and DQIdMax is equal to 0) and the access unit does not contain an activating buffering period SEI message, the sequence parameter set RBSP is activated. This sequence parameter set RBSP, is called the active SVC sequence parameter set RBSP until it is deactivated when another SVC sequence parameter set RBSP becomes the active SVC sequence parameter set RBSP. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active SVC sequence parameter set RBSP and it is referred to by an activating buffering period SEI message (using that value of seq\_parameter\_set\_id) that is not included in a scalable nesting SEI message (DQIdMax is equal to 0), the sequence parameter set RBSP is activated. This sequence parameter set RBSP is called the active SVC sequence parameter set RBSP until it is deactivated when another SVC sequence parameter set RBSP becomes the active SVC sequence parameter set RBSP. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active SVC sequence parameter set RBSP and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice in scalable extension NAL unit (nal\_unit\_type is equal to 20) with DQId equal to DQIdMax (the picture parameter set RBSP becomes the active picture parameter set RBSP) and the access unit does not contain an activating buffering period SEI message, the subset sequence parameter set RBSP is activated. This subset sequence parameter set RBSP is called the active SVC sequence parameter set RBSP until it is deactivated when another SVC sequence parameter set RBSP becomes the active SVC sequence parameter set RBSP. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active SVC sequence parameter set RBSP and it is referred to by an activating buffering period SEI message (using that value of seq\_parameter\_set\_id) that is included in a scalable nesting SEI message, the subset sequence parameter set RBSP is activated. This subset sequence parameter set RBSP, is called the active SVC sequence parameter set RBSP until it is deactivated when another SVC sequence parameter set RBSP becomes the active SVC sequence parameter set RBSP. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +NOTE 3 – The active SVC sequence parameter set RBSP is either a sequence parameter set RBSP or a subset sequence parameter set RBSP. Sequence parameter set RBSPs are activated by coded slice NAL units with nal\_unit\_type equal to 1 or 5 or buffering period SEI messages that are not included in a scalable nesting SEI message. Subset sequence parameter set RBSPs are activated by coded slice in scalable extension NAL units (nal\_unit\_type equal to 20) or buffering period SEI messages that are included in a scalable nesting SEI message. A sequence parameter set RBSP and a subset sequence parameter set RBSP may have the same value of seq\_parameter\_set\_id. + +NOTE 4 – Buffering period SEI messages have a higher priority for activating SVC sequence parameter sets than coded slice NAL units. When an SVC sequence parameter set RBSP is referred to by activation of a picture parameter set RBSP inside a particular access unit and this picture parameter set RBSP is activated by a coded slice NAL unit with DQId equal to DQIdMax (the picture parameter set RBSP becomes the active picture parameter set RBSP) and this particular access unit also contains an activating buffering period SEI message that refers to an SVC sequence parameter set RBSP that is different than the SVC sequence parameter set RBSP referred to by the activation of the picture parameter set RBSP, the SVC sequence parameter set RBSP that is referred to by the activating buffering period SEI message becomes the active SVC sequence parameter set. + +NOTE 5 – Compared to the specifications for profiles specified in Annex A, where an activated sequence parameter set RBSP must remain active for the entire coded video sequence, the specification for profiles specified in this annex differs. When an SVC sequence parameter set RBSP is already active (as the active SVC sequence parameter set RBSP), another SVC sequence parameter set RBSP becomes the active SVC sequence parameter set RBSP in a non-IDR access unit when it is referred to by an activating buffering period SEI message or by the activation of a picture parameter set RBSP (as the active picture parameter set RBSP). In this case, the contents of the de-activated and activated SVC sequence parameter set RBSP are mutually restricted as described below. Hence, within a coded video sequence, multiple successively activated/de-activated SVC sequence parameter set RBSPs can be present. + +For the following specification in this clause, the activating layer buffering period SEI message for a particular value of DQId is specified as follows: + +- If the access unit contains a buffering period SEI messages that is included in a scalable nesting SEI message and is associated with the particular value of DQId, this buffering period SEI message is the activating layer buffering period SEI message for the particular value of DQId. +- Otherwise, if the particular value of DQId is equal to 0 and the access unit contains a buffering period SEI message that is not included in a scalable nesting SEI message, this buffering period SEI message is the activating layer buffering period SEI message for the particular value of DQId. + +- Otherwise, the access unit does not contain an activating layer buffering period SEI message for the particular value of DQId. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active layer SVC sequence parameter set RBSP for DQId equal to 0 and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice NAL unit with nal\_unit\_type equal to 1 or 5 and DQIdMax is greater than 0 (the picture parameter set RBSP becomes the active layer picture parameter set RBSP for DQId equal to 0) and the access unit does not contain an activating layer buffering period SEI message for DQId equal to 0, the sequence parameter set RBSP is activated for layer representations with DQId equal to 0. This sequence parameter set RBSP is called the active layer SVC sequence parameter set RBSP for DQId equal to 0 until it is deactivated when another SVC sequence parameter set RBSP becomes the active layer SVC sequence parameter set RBSP for DQId equal to 0 or when decoding an access unit with DQIdMax equal to 0. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active layer SVC sequence parameter set RBSP for DQId equal to 0 and it is referred to by an activating layer buffering period SEI message for DQId equal to 0 (using that value of seq\_parameter\_set\_id) that is not included in a scalable nesting SEI message and DQIdMax is greater than 0, the sequence parameter set RBSP is activated for layer representations with DQId equal to 0. This sequence parameter set RBSP is called the active layer SVC sequence parameter set RBSP for DQId equal to 0 until it is deactivated when another SVC sequence parameter set RBSP becomes the active layer SVC sequence parameter set RBSP for DQId equal to 0 or when decoding an access unit with DQIdMax equal to 0. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active layer SVC sequence parameter set RBSP for a particular value of DQId less than DQIdMax and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice in scalable extension NAL unit (nal\_unit\_type is equal to 20) with the particular value of DQId (the picture parameter set RBSP becomes the active layer picture parameter set RBSP for the particular value of DQId) and the access unit does not contain an activating layer buffering period SEI message for the particular value of DQId, the subset sequence parameter set is activated for layer representations with the particular value of DQId. This subset sequence parameter set RBSP is called the active layer SVC sequence parameter set RBSP for the particular value of DQId until it is deactivated when another SVC sequence parameter set RBSP becomes the active layer SVC sequence parameter set RBSP for the particular value of DQId or when decoding an access unit with DQIdMax less than or equal to the particular value of DQId. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active layer SVC sequence parameter set RBSP for a particular value of DQId less than DQIdMax and it is referred to by an activating layer buffering period SEI message for the particular value of DQId (using that value of seq\_parameter\_set\_id) that is included in a scalable nesting SEI message, the subset sequence parameter set RBSP is activated for layer representations with the particular value of DQId. This subset sequence parameter set RBSP is called the active layer SVC sequence parameter set RBSP for the particular value of DQId until it is deactivated when another SVC sequence parameter set RBSP becomes the active layer SVC sequence parameter set RBSP for the particular value of DQId or when decoding an access unit with DQIdMax less than or equal to the particular value of DQId. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +A sequence parameter set RBSP or a subset sequence parameter set RBSP that includes a value of profile\_idc not specified in Annex A or F shall not be referred to by activation of a picture parameter set RBSP as the active picture parameter set RBSP or as active layer picture parameter set RBSP (using that value of seq\_parameter\_set\_id) or referred to by a buffering period SEI message (using that value of seq\_parameter\_set\_id). A sequence parameter set RBSP or a subset sequence parameter set RBSP including a value of profile\_idc not specified in Annex A or F is ignored in the decoding for profiles specified in Annex A or F. + +Let spsA and spsB be two SVC sequence parameter set RBSPs with one of the following properties: + +- spsA is the SVC sequence parameter set RBSP that is referred to by the coded slice NAL units (via the picture parameter set) of a layer representation with a particular value of dependency\_id and quality\_id equal to 0 and spsB is the SVC sequence parameter set RBSP that is referred to by the coded slice NAL units (via the picture parameter set) of another layer representation, in the same access unit, with the same value of dependency\_id and quality\_id greater than 0, + +- spsA is the active SVC sequence parameter set RBSP for an access unit and spsB is the SVC sequence parameter set RBSP that is referred to by the coded slice NAL units (via the picture parameter set) of the layer representation with DQId equal to DQIdMax, +- spsA is the active SVC sequence parameter set RBSP for an IDR access unit and spsB is the active SVC sequence parameter set RBSP for any non-IDR access unit of the same coded video sequence. + +The SVC sequence parameter set RBSPs spsA and spsB are restricted with regards to their contents as specified in the following. + +- The values of the syntax elements in the `seq_parameter_set_data()` syntax structure of spsA and spsB may only differ for the following syntax elements and shall be the same otherwise: `profile_idc`, `constraint_setX_flag` (with X being equal to 0 to 5, inclusive), `reserved_zero_2bits`, `level_idc`, `seq_parameter_set_id`, `timing_info_present_flag`, `num_units_in_tick`, `time_scale`, `fixed_frame_rate_flag`, `nal_hrd_parameters_present_flag`, `vc1_hrd_parameters_present_flag`, `low_delay_hrd_flag`, `pic_struct_present_flag`, and the `hrd_parameters()` syntax structures. +- When spsA is the active SVC sequence parameter set RBSP and spsB is the SVC sequence parameter set RBSP that is referred to by the coded slice NAL units of the layer representation with DQId equal to DQIdMax, the level specified by `level_idc` (or `level_idc` and `constraint_set3_flag`) in spsA shall not be less than the level specified by `level_idc` (or `level_idc` and `constraint_set3_flag`) in spsB. +- When the `seq_parameter_set_svc_extension()` syntax structure is present in both spsA and spsB, the values of all syntax elements in the `seq_parameter_set_svc_extension()` syntax structure shall be the same. + +It is a requirement of bitstream conformance that the following constraints are obeyed: + +- For each particular value of DQId, all coded slice NAL units of a coded video sequence shall refer to the same value of `seq_parameter_set_id` (via the picture parameter set RBSP that is referred to by the value of `pic_parameter_set_id`). +- The value of `seq_parameter_set_id` in a buffering period SEI message that is not included in a scalable nesting SEI message shall be identical to the value of `seq_parameter_set_id` in the picture parameter set RBSP that is referred to by coded slice NAL units with `nal_unit_type` equal to 1 or 5 (via the value of `pic_parameter_set_id`) in the same access unit. +- The value of `seq_parameter_set_id` in a buffering period SEI message that is included in a scalable nesting SEI message and is associated with a particular value of DQId shall be identical to the value of `seq_parameter_set_id` in the picture parameter set RBSP that is referred to by coded slice NAL units with the particular value of DQId (via the value of `pic_parameter_set_id`) in the same access unit. + +The active layer SVC sequence parameter set RBSPs for different values of DQId may be the same SVC sequence parameter set RBSP. The active SVC sequence parameter set RBSP and an active layer SVC sequence parameter set RBSP for a particular value of DQId may be the same SVC sequence parameter set RBSP. + +When the active SVC sequence parameter set RBSP for a coded picture is a sequence parameter set RBSP, any sequence parameter set RBSP with the value of `seq_parameter_set_id` for the active SVC sequence parameter set RBSP for the coded picture shall have the same content as that of the active SVC sequence parameter set RBSP for the coded picture unless it follows the last access unit of the coded video sequence containing the coded picture and precedes the first VCL NAL unit and the first SEI NAL unit containing a buffering period SEI message (when present) of another coded video sequence. + +When the active SVC sequence parameter set RBSP for a coded picture is a subset sequence parameter set RBSP, any subset sequence parameter set RBSP with the value of `seq_parameter_set_id` for the active SVC sequence parameter set RBSP for the coded picture shall have the same content as that of the active SVC sequence parameter set RBSP for the coded picture unless it follows the last access unit of the coded video sequence containing the coded picture and precedes the first VCL NAL unit and the first SEI NAL unit containing a buffering period SEI message (when present) of another coded video sequence. + +For each particular value of DQId, the following applies: + +- When the active layer SVC sequence parameter set RBSP for a coded picture is a sequence parameter set RBSP, any sequence parameter set RBSP with the value of `seq_parameter_set_id` for the active layer SVC sequence parameter set RBSP for the coded picture shall have the same content as that of the active layer SVC sequence parameter set RBSP for the coded picture unless it follows the last access unit of the coded video sequence containing the coded picture and precedes the first VCL NAL unit and the first SEI NAL unit containing a buffering period SEI message (when present) of another coded video sequence. +- When the active layer SVC sequence parameter set RBSP for a coded picture is a subset sequence parameter set RBSP, any subset sequence parameter set RBSP with the value of `seq_parameter_set_id` for the active layer SVC + +sequence parameter set RBSP for the coded picture shall have the same content as that of the active layer SVC sequence parameter set RBSP for the coded picture unless it follows the last access unit of the coded video sequence containing the coded picture and precedes the first VCL NAL unit and the first SEI NAL unit containing a buffering period SEI message (when present) of another coded video sequence. + +NOTE 6 – If picture parameter set RBSP or SVC sequence parameter set RBSP are conveyed within the bitstream, these constraints impose an order constraint on the NAL units that contain the picture parameter set RBSP or SVC sequence parameter set RBSP, respectively. Otherwise (picture parameter set RBSP or SVC sequence parameter set RBSP are conveyed by other means not specified in this Recommendation | International Standard), they must be available to the decoding process in a timely fashion such that these constraints are obeyed. + +When a sequence parameter set NAL unit with a particular value of `seq_parameter_set_id` is received, its content replaces the content of the previous sequence parameter set NAL unit, in decoding order, with the same value of `seq_parameter_set_id` (when a previous sequence parameter set NAL unit with the same value of `seq_parameter_set_id` was present in the bitstream). When a subset sequence parameter set NAL unit with a particular value of `seq_parameter_set_id` is received, its content replaces the content of the previous subset sequence parameter set NAL unit, in decoding order, with the same value of `seq_parameter_set_id` (when a previous subset sequence parameter set NAL unit with the same value of `seq_parameter_set_id` was present in the bitstream). + +NOTE 7 – A decoder must be capable of simultaneously storing the contents of the sequence parameter sets and subset sequence parameter sets for all values of `seq_parameter_set_id`. The content of the sequence parameter set with a particular value of `seq_parameter_set_id` is overwritten when a new sequence parameter set NAL unit with the same value of `seq_parameter_set_id` is received, and the content of the subset sequence parameter set with a particular value of `seq_parameter_set_id` is overwritten when a new subset sequence parameter set NAL unit with the same value of `seq_parameter_set_id` is received. + +When present, a sequence parameter set extension RBSP includes parameters having a similar function to those of a sequence parameter set RBSP. For purposes of establishing constraints on the syntax elements of the sequence parameter set extension RBSP and for purposes of determining activation of a sequence parameter set extension RBSP, the sequence parameter set extension RBSP shall be considered part of the preceding sequence parameter set RBSP with the same value of `seq_parameter_set_id`. When a sequence parameter set RBSP is present that is not followed by a sequence parameter set extension RBSP with the same value of `seq_parameter_set_id` prior to the activation of the sequence parameter set RBSP, the sequence parameter set extension RBSP and its syntax elements shall be considered not present for the active SVC sequence parameter set RBSP. The contents of sequence parameter set extension RBSPs only apply when the base layer, which conforms to one or more of the profiles specified in Annex A, of a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded. Subset sequence parameter set RBSPs shall not be followed by a sequence parameter set extension RBSP. + +NOTE 8 – Sequence parameter sets extension RBSPs are not considered to be part of a subset sequence parameter set RBSP and subset sequence parameter set RBSPs must not be followed by a sequence parameter set extension RBSP. + +For layer representations with `DQId` equal to `DQIdMax`, all constraints that are expressed on the relationship between the values of the syntax elements (and the values of variables derived from those syntax elements) in SVC sequence parameter sets and picture parameter sets and other syntax elements are expressions of constraints that apply only to the active SVC sequence parameter set and the active picture parameter set. For layer representations with a particular value of `DQId` less than `DQIdMax`, all constraints that are expressed on the relationship between the values of the syntax elements (and the values of variables derived from those syntax elements) in SVC sequence parameter sets and picture parameter sets and other syntax elements are expressions of constraints that apply only to the active layer SVC sequence parameter set and the active layer picture parameter set for the particular value of `DQId`. If any SVC sequence parameter set RBSP having `profile_idc` equal to one of the `profile_idc` values specified in Annex A or F is present that is never activated in the bitstream (i.e., it never becomes the active SVC sequence parameter set or an active layer SVC sequence parameter set), its syntax elements shall have values that would conform to the specified constraints if it were activated by reference in an otherwise-conforming bitstream. If any picture parameter set RBSP is present that is never activated in the bitstream (i.e., it never becomes the active picture parameter set or an active layer picture parameter set), its syntax elements shall have values that would conform to the specified constraints if it were activated by reference in an otherwise-conforming bitstream. + +During operation of the decoding process (see clause F.8), for layer representations with `DQId` equal to `DQIdMax`, the values of parameters of the active picture parameter set and the active SVC sequence parameter set shall be considered in effect. For layer representations with a particular value of `DQId` less than `DQIdMax`, the values of the parameters of the active layer picture parameter set and the active layer SVC sequence parameter set for the particular value of `DQId` shall be considered in effect. For interpretation of SEI messages that apply to access units or dependency representations with `dependency_id` equal to `DependencyIdMax` or layer representation with `DQId` equal to `DQIdMax`, the values of the parameters of the active picture parameter set and the active SVC sequence parameter set for the access unit shall be considered in effect unless otherwise specified in the SEI message semantics. For interpretation of SEI messages that apply to dependency representations with a particular value of `dependency_id` less than `DependencyIdMax`, the values of the parameters of the active layer picture parameter set and the active layer SVC sequence parameter set for the layer representation with `DQId` equal to ( `dependency_id` << 4 ) of the access unit shall be considered in effect unless otherwise specified in the SEI message semantics. For interpretation of SEI messages that apply to layer representations with a + +particular value of DQId less than DQIdMax, the values of the parameters of the active layer picture parameter set and the active layer SVC sequence parameter set for the layer representation with the particular value of DQId of the access unit shall be considered in effect unless otherwise specified in the SEI message semantics. + +#### **F.7.4.1.2.2 Order of access units and association to coded video sequences** + +The specification of clause 7.4.1.2.2 applies with the following modifications. + +The first access unit of the bitstream shall only contain coded slice NAL units with *nal\_unit\_type* equal to 5 or *idr\_flag* equal to 1. + +The order of NAL units and coded pictures and their association to access units is described in clause F.7.4.1.2.3. + +#### **F.7.4.1.2.3 Order of NAL units and coded pictures and association to access units** + +The specification of clause 7.4.1.2.3 applies with the following modifications. + +NOTE – Some bitstreams that conform to one or more profiles specified in this annex do not conform to any profile specified in Annex A (prior to operation of the base layer extraction process specified in clause F.8.8.2). As specified in clauses 7.4.1 and 7.4.1.2.3, for the profiles specified in Annex A, NAL units with *nal\_unit\_type* equal to 20 are classified as non-VCL NAL units that must be preceded within each access unit by at least one NAL unit with *nal\_unit\_type* in the range of 1 to 5, inclusive. For this reason, any bitstream that conforms to one or more profiles specified in this annex does not conform to any profile specified in Annex A when it contains any of the following: + +- any access unit that does not contain any NAL units with *nal\_unit\_type* equal to 1 or 5, but contains one or more NAL units with *nal\_unit\_type* equal to 6, 7, 8, 9, or 15; +- any access unit in which one or more NAL units with *nal\_unit\_type* equal to 7, 8, or 15 is present after the last NAL unit in the access unit with *nal\_unit\_type* equal to 1 or 5. + +The association of VCL NAL units to primary or redundant coded pictures is specified in clause F.7.4.1.2.5. When the primary coded picture does not contain a layer representation with a particular value of DQId, all redundant coded pictures (when present) in the same access unit shall not contain a layer representation with the particular value of DQId. + +The constraints for the detection of the first VCL NAL unit of a primary coded picture are specified in clause F.7.4.1.2.4. + +The constraint expressed in clause 7.4.1.2.3 on the order of a buffering period SEI message is replaced by the following constraints. + +- When an SEI NAL unit containing a buffering period SEI message is present, the following applies: + - If the buffering period SEI message is the only buffering period SEI message in the access unit and it is not included in a scalable nesting SEI message, the buffering period SEI message shall be the first SEI message payload of the first SEI NAL unit in the access unit. + - Otherwise (the buffering period SEI message is not the only buffering period SEI message in the access unit or it is included in a scalable nesting SEI message), the following constraints are specified: + - When a buffering period SEI message that is not included in a scalable nesting SEI message is present, this buffering period SEI message shall be the only SEI message payload of the first SEI NAL unit in the access unit. + - A scalable nesting SEI message that includes a buffering period SEI message shall not include any other SEI messages and the scalable nesting SEI message that includes a buffering period SEI message shall be the only SEI message inside an SEI NAL unit. + - All SEI NAL units that precede an SEI NAL unit that contains a scalable nesting SEI message with a buffering period SEI message as payload in an access unit shall only contain buffering period SEI messages or scalable nesting SEI messages with a buffering period SEI message as payload. + - When present, a scalable nesting SEI message with *all\_layer\_representations\_in\_au\_flag* equal to 1 and a buffering period SEI message as payload shall be the first scalable nesting SEI message in an access unit. + - Any scalable nesting SEI message with a buffering period SEI message as payload that immediately precedes another scalable nesting SEI message with a buffering period SEI message as payload shall have values of $128 * sei\_dependency\_id[ i ] + 8 * sei\_quality\_id[ i ] + sei\_temporal\_id$ , for all present i, that are less than any of the values of $128 * sei\_dependency\_id[ i ] + 8 * sei\_quality\_id[ i ] + sei\_temporal\_id$ in the immediately following scalable nesting SEI message with a buffering period SEI message as payload. + +The following additional constraints shall be obeyed: + +- Each NAL unit with *nal\_unit\_type* equal to 1 or 5 shall be immediately preceded by a prefix NAL unit. + +- In bitstreams conforming to this Recommendation | International Standard, each prefix NAL unit shall be immediately followed by a NAL unit with `nal_unit_type` equal to 1 or 5. + +#### F.7.4.1.2.4 Detection of the first VCL NAL unit of a primary coded picture + +This clause specifies constraints on VCL NAL unit syntax that are sufficient to enable the detection of the first VCL NAL unit of each primary coded picture. + +The first VCL NAL unit of the primary coded picture of the current access unit, in decoding order, shall be different from the last VCL NAL unit of the primary coded picture of the previous access unit, in decoding order, in one or more of the following ways: + +- `dependency_id` of the first VCL NAL unit of the primary coded picture of the current access unit is less than `dependency_id` of the last VCL NAL unit of the primary coded picture of the previous access unit +- `dependency_id` of the first VCL NAL unit of the primary coded picture of the current access unit is equal to `dependency_id` of the last VCL NAL unit of the primary coded picture of the previous access unit and any of the following conditions are true + - `quality_id` of the first VCL NAL unit of the primary coded picture of the current access unit is less than `quality_id` of the last VCL NAL unit of the primary coded picture of the previous access unit + - `quality_id` of the first VCL NAL unit of the primary coded picture of the current access unit and the last VCL NAL unit of the primary coded picture of the previous access unit is equal to 0, and any of the conditions specified in clause 7.4.1.2.4 is fulfilled + +#### F.7.4.1.2.5 Order of VCL NAL units and association to coded pictures + +Each VCL NAL unit is part of a coded picture. + +Let `dId` be the value of `dependency_id` and let `qId` be the value of `quality_id` of any particular VCL NAL unit. The order of the VCL NAL units within a coded picture is constrained as follows: + +- For all VCL NAL units following this particular VCL NAL unit, the value of `dependency_id` shall be greater than or equal to `dId`. +- For all VCL NAL units with a value of `dependency_id` equal to `dId` following this particular VCL NAL unit, the value of `quality_id` shall be greater than or equal to `qId`. + +For each set of VCL NAL units within a layer representation, the following applies: + +- If arbitrary slice order, as specified in Annex A or clause F.10, is allowed, coded slice NAL units of a layer representation may have any order relative to each other. +- Otherwise (arbitrary slice order is not allowed), coded slice NAL units of a slice group shall not be interleaved with coded slice NAL units of another slice group and the order of coded slice NAL units within a slice group shall be in the order of increasing macroblock address for the first macroblock of each coded slice NAL unit of the same slice group. + +NAL units having `nal_unit_type` equal to 12 may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having `nal_unit_type` equal to 0 or in the range of 24 to 31, inclusive, which are unspecified, may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having `nal_unit_type` in the range of 21 to 23, inclusive, which are reserved, shall not precede the first VCL NAL unit of the primary coded picture within the access unit (when specified in the future by ITU-T | ISO/IEC). + +### F.7.4.2 Raw byte sequence payloads and RBSP trailing bits semantics + +#### F.7.4.2.1 Sequence parameter set RBSP semantics + +The semantics specified in clause 7.4.2.1 apply. + +##### F.7.4.2.1.1 Sequence parameter set data semantics + +The semantics specified in clause 7.4.2.1.1 apply with substituting SVC sequence parameter set for sequence parameter set. Additionally, the following applies. + +**profile\_idc** and **level\_idc** indicate the profile and level to which the coded video sequence conforms when the SVC sequence parameter set is the active SVC sequence parameter set. + +**constraint\_set0\_flag** is specified as follows: + +- If the sequence parameter set data syntax structure is included in a sequence parameter set RBSP, the semantics specified in clause 7.4.2.1.1 apply. +- Otherwise (the sequence parameter set data syntax structure is included in a subset sequence parameter set RBSP), **constraint\_set0\_flag** equal to 1 specifies that all of the following conditions are obeyed: + - the coded video sequence obeys all constraints specified in clause F.10.1.1, + - the output of the decoding process as specified in clause F.8 is identical to the output of the decoding process that is obtained when **profile\_idc** would be set equal to 83. + +**constraint\_set0\_flag** equal to 0 specifies that the coded video sequence may or may not obey all constraints specified in clause F.10.1.1 and that the output of the decoding process as specified in clause F.8 may or may not be identical to the output of the decoding process that is obtained when **profile\_idc** would be set equal to 83. + +NOTE 1 – The output of the decoding process may be different, if the array **sTCoeff** contains non-zero scaled luma transform coefficient values for a transform block of a macroblock that is coded in an Inter macroblock prediction mode, but all reconstructed luma residual samples of the array **rSL** that are associated with the transform blocks are equal to 0. In this case, the boundary filter strength that is derived as specified in clause F.8.7.4.3 can depend on the value of **profile\_idc**. + +**constraint\_set1\_flag** is specified as follows: + +- If the sequence parameter set data syntax structure is included in a sequence parameter set RBSP, the semantics specified in clause 7.4.2.1.1 apply. +- Otherwise (the sequence parameter set data syntax structure is included in a subset sequence parameter set RBSP), **constraint\_set1\_flag** equal to 1 specifies that all of the following conditions are obeyed: + - the coded video sequence obeys all constraints specified in clause F.10.1.2, + - the output of the decoding process as specified in clause F.8 is identical to the output of the decoding process that is obtained when **profile\_idc** would be set equal to 86. + +**constraint\_set1\_flag** equal to 0 specifies that the coded video sequence may or may not obey all constraints specified in clause F.10.1.2 and that the output of the decoding process as specified in clause F.8 may or may not be identical to the output of the decoding process that is obtained when **profile\_idc** would be set equal to 86. + +NOTE 2 – The output of the decoding process may be different, if the array **sTCoeff** contains non-zero scaled luma transform coefficient values for a transform block of a macroblock that is coded in an Inter macroblock prediction mode, but all reconstructed luma residual samples of the array **rSL** that are associated with the transform blocks are equal to 0. In this case, the boundary filter strength that is derived as specified in clause F.8.7.4.3 can depend on the value of **profile\_idc**. + +**constraint\_set2\_flag** is specified as follows: + +- If the sequence parameter set data syntax structure is included in a sequence parameter set RBSP, the semantics specified in clause 7.4.2.1.1 apply. +- Otherwise (the sequence parameter set data syntax structure is included in a subset sequence parameter set RBSP), the value of 1 for **constraint\_set2\_flag** is reserved for future use by ITU-T | ISO/IEC. **constraint\_set2\_flag** shall be equal to 0 for coded video sequences with **profile\_idc** equal to 83 and 86 in bitstreams conforming to this Recommendation | International Standard. Decoders shall ignore the value of **constraint\_set2\_flag** when **profile\_idc** is equal to 83 or 86. + +**constraint\_set3\_flag** is specified as follows: + +- If the sequence parameter set data syntax structure is included in a sequence parameter set RBSP, the semantics specified in clause 7.4.2.1.1 apply. +- Otherwise (the sequence parameter set data syntax structure is included in a subset sequence parameter set RBSP), the following applies: + - If **profile\_idc** is equal to 86, **constraint\_set3\_flag** equal to 1 specifies that the coded video sequence obeys all constraints specified in clause F.10.1.3, and **constraint\_set3\_flag** equal to 0 specifies that the coded video sequence may or may not obey these corresponding constraints. + - Otherwise (**profile\_idc** is not equal to 86), the value of 1 for **constraint\_set3\_flag** is reserved for future use by ITU-T | ISO/IEC. **constraint\_set3\_flag** shall be equal to 0 for coded video sequences with **profile\_idc** not equal to 86 in bitstreams conforming to this Recommendation | International Standard. Decoders shall ignore the value of **constraint\_set3\_flag** when **profile\_idc** is not equal to 86. + +**constraint\_set5\_flag** is specified as follows: + +- If the sequence parameter set data syntax structure is included in a sequence parameter set RBSP, the semantics specified in clause 7.4.2.1.1 apply. + +- Otherwise (the sequence parameter set data syntax structure is included in a subset sequence parameter set RBSP), the following applies: + - If the `profile_idc` is equal to 83, `constraint_set5_flag` equal to 1 specifies that the coded video sequence obeys all constraints specified in clause F.10.1.1.1. + - Otherwise, if the `profile_idc` is equal to 86, `constraint_set5_flag` equal to 1 specifies that the coded video sequence obeys all constraints specified in clause F.10.1.2.1. + - Otherwise (`profile_idc` is not equal to 83 or 86), the value of 1 for `constraint_set5_flag` is reserved for future use by ITU-T | ISO/IEC. `constraint_set5_flag` shall be equal to 0 for coded video sequences with `profile_idc` not equal to 83 or 86 in bitstreams conforming to this Recommendation | International Standard. Decoders shall ignore the value of `constraint_set5_flag` when `profile_idc` is not equal to 83 or 86. + +The value of `separate_colour_plane_flag` shall be equal to 0 and the value of `qpprime_y_zero_transform_bypass_flag` shall be equal to 0. + +When the `seq_parameter_set_data()` syntax structure is present in a subset sequence parameter set RBSP and `vui_parameters_present_flag` is equal to 1, `timing_info_present_flag` shall be equal to 0, `nal_hrd_parameters_present_flag` shall be equal to 0, `vcl_hrd_parameters_present_flag` shall be equal to 0, and `pic_struct_present_flag` shall be equal to 0. The value of 1 for `timing_info_present_flag`, `nal_hrd_parameters_present_flag`, `vcl_hrd_parameters_present_flag`, and `pic_struct_present_flag` for subset sequence parameter set RBSPs is reserved for future use by ITU-T | ISO/IEC. When `timing_info_present_flag` is equal to 1, decoders shall ignore the values of the directly following `num_units_in_tick`, `time_scale`, `fixed_frame_rate_flag` syntax elements. When `nal_hrd_parameters_present_flag` is equal to 1, decoders shall ignore the value of the syntax elements in the directly following `hrd_parameters()` syntax structure. When `vcl_hrd_parameters_present_flag` is equal to 1, decoders shall ignore the value of the syntax elements in the directly following `hrd_parameters()` syntax structure. + +When the `seq_parameter_set_data()` syntax structure is present in a sequence parameter set RBSP and `vui_parameters_present_flag` is equal to 1, the values of `timing_info_present_flag`, `num_units_in_tick`, `time_scale`, `fixed_frame_rate_flag`, `nal_hrd_parameters_present_flag`, `vcl_hrd_parameters_present_flag`, `low_delay_hrd_flag`, `pic_struct_present_flag` and the values of syntax elements included in the `hrd_parameters()` syntax structures, when present, shall be such that the bitstream activating the sequence parameter set is conforming to one or more of the profiles specified in Annex A. + +**max\_num\_ref\_frames** specifies the maximum number of short-term and long-term reference frames, complementary reference field pairs, and non-paired reference fields that may be used by the decoding process for inter prediction of any picture in the coded video sequence. `max_num_ref_frames` also determines the size of the sliding window operation as specified in clause F.8.2.4.2. The value of `max_num_ref_frames` shall be in the range of 0 to `MaxDpbFrames` (as specified in clause F.10), inclusive. + +The allowed range of values for `pic_width_in_mbs_minus1`, `pic_height_in_map_units_minus1`, and `frame_mbs_only_flag` is specified by constraints in clause F.10. + +#### F.7.4.2.1.1.1 Scaling list semantics + +The semantics specified in clause 7.4.2.1.1.1 apply. + +#### F.7.4.2.1.2 Sequence parameter set extension RBSP semantics + +The semantics specified in clause 7.4.2.1.2 apply. Additionally, the following applies. + +Sequence parameter set extension RBSPs can only follow sequence parameter set RBSPs in decoding order. Subset sequence parameter set RBSPs shall not be followed by a sequence parameter set extension RBSP. The contents of sequence parameter set extension RBSPs only apply when the base layer, which conforms to one or more of the profiles specified in Annex A, of a coded video sequence conforming to one or more of the profiles specified in Annex F is decoded. + +#### F.7.4.2.1.3 Subset sequence parameter set RBSP semantics + +The semantics specified in clause 7.4.2.1.3 apply. + +#### F.7.4.2.1.4 Sequence parameter set SVC extension semantics + +**inter\_layer\_deblocking\_filter\_control\_present\_flag** equal to 1 specifies that a set of syntax elements controlling the characteristics of the deblocking filter for inter-layer prediction is present in the slice header. `inter_layer_deblocking_filter_control_present_flag` equal to 0 specifies that the set of syntax elements controlling the characteristics of the deblocking filter for inter-layer prediction is not present in the slice headers and their inferred values are in effect. + +**extended\_spatial\_scalability\_idc** specifies the presence of syntax elements related to geometrical parameters for the resampling processes. The value of extended\_spatial\_scalability\_idc shall be in the range of 0 to 2, inclusive, and the following applies: + +- If extended\_spatial\_scalability\_idc is equal to 0, no geometrical parameters are present in the subset sequence parameter set and the slice headers referring to this subset sequence parameter set. +- Otherwise, if extended\_spatial\_scalability\_idc is equal to 1, geometrical parameters are present in the subset sequence parameter set, but not in the slice headers referring to this subset sequence parameter set. +- Otherwise (extended\_spatial\_scalability\_idc is equal to 2), geometrical parameters are not present in the subset sequence parameter set, but they are present in the slice headers with no\_inter\_layer\_pred\_flag equal to 0 and quality\_id equal to 0 that refer to this subset sequence parameter set. + +**chroma\_phase\_x\_plus1\_flag** specifies the horizontal phase shift of the chroma components in units of half luma samples of a frame or layer frame. When chroma\_phase\_x\_plus1\_flag is not present, it shall be inferred to be equal to 1. + +When ChromaArrayType is equal to 1 and chroma\_sample\_loc\_type\_top\_field and chroma\_sample\_loc\_type\_bottom\_field are present, the following applies: + +- If chroma\_phase\_x\_plus1\_flag is equal to 0, chroma\_sample\_loc\_type\_top\_field and chroma\_sample\_loc\_type\_bottom\_field should be equal to 0, 2, or 4. +- Otherwise (chroma\_phase\_x\_plus1\_flag is equal to 1), chroma\_sample\_loc\_type\_top\_field and chroma\_sample\_loc\_type\_bottom\_field should be equal to 1, 3, or 5. + +When ChromaArrayType is equal to 2, chroma\_phase\_x\_plus1\_flag should be equal to 1. + +**chroma\_phase\_y\_plus1** specifies the vertical phase shift of the chroma components in units of half luma samples of a frame or layer frame. When chroma\_phase\_y\_plus1 is not present, it shall be inferred to be equal to 1. The value of chroma\_phase\_y\_plus1 shall be in the range of 0 to 2, inclusive. + +When ChromaArrayType is equal to 1 and chroma\_sample\_loc\_type\_top\_field and chroma\_sample\_loc\_type\_bottom\_field are present, the following applies: + +- If chroma\_phase\_y\_plus1 is equal to 0, chroma\_sample\_loc\_type\_top\_field and chroma\_sample\_loc\_type\_bottom\_field should be equal to 2 or 3. +- Otherwise, if chroma\_phase\_y\_plus1 is equal to 1, chroma\_sample\_loc\_type\_top\_field and chroma\_sample\_loc\_type\_bottom\_field should be equal to 0 or 1. +- Otherwise (chroma\_phase\_y\_plus1 is equal to 2), chroma\_sample\_loc\_type\_top\_field and chroma\_sample\_loc\_type\_bottom\_field should be equal to 4 or 5. + +**seq\_ref\_layer\_chroma\_phase\_x\_plus1\_flag** specifies the horizontal phase shift of the chroma components in units of half luma samples of a layer frame for the layer pictures that may be used for inter-layer prediction. When seq\_ref\_layer\_chroma\_phase\_x\_plus1\_flag is not present, it shall be inferred to be equal to chroma\_phase\_x\_plus1\_flag. + +**seq\_ref\_layer\_chroma\_phase\_y\_plus1** specifies the vertical phase shift of the chroma components in units of half luma samples of a layer frame for the layer pictures that may be used for inter-layer prediction. When seq\_ref\_layer\_chroma\_phase\_y\_plus1 is not present, it shall be inferred to be equal to chroma\_phase\_y\_plus1. The value of seq\_ref\_layer\_chroma\_phase\_y\_plus1 shall be in the range of 0 to 2, inclusive. + +**seq\_scaled\_ref\_layer\_left\_offset** specifies the horizontal offset between the upper-left luma sample of a resampled layer picture used for inter-layer prediction and the upper-left luma sample of the current picture or current layer picture in units of two luma samples. When seq\_scaled\_ref\_layer\_left\_offset is not present, it shall be inferred to be equal to 0. The value of seq\_scaled\_ref\_layer\_left\_offset shall be in the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. + +**seq\_scaled\_ref\_layer\_top\_offset** specifies the vertical offset between the upper-left luma sample of a resampled layer picture used for inter-layer prediction and the upper-left luma sample of the current picture or current layer picture. Depending on the value of frame\_mbs\_only\_flag, the following applies: + +- If frame\_mbs\_only\_flag is equal to 1, the vertical offset is specified in units of two luma samples. +- Otherwise (frame\_mbs\_only\_flag is equal to 0), the vertical offset is specified in units of four luma samples. + +When seq\_scaled\_ref\_layer\_top\_offset is not present, it shall be inferred to be equal to 0. The value of seq\_scaled\_ref\_layer\_top\_offset shall be in the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. + +**seq\_scaled\_ref\_layer\_right\_offset** specifies the horizontal offset between the bottom-right luma sample of a resampled layer picture used for inter-layer prediction and the bottom-right luma sample of the current picture or current layer picture + +in units of two luma samples. When `seq_scaled_ref_layer_right_offset` is not present, it shall be inferred to be equal to 0. The value of `seq_scaled_ref_layer_right_offset` shall be in the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. + +**`seq_scaled_ref_layer_bottom_offset`** specifies the vertical offset between the bottom-right luma sample of a resampled layer picture used for inter-layer prediction and the bottom-right luma sample of the current picture or current layer picture. Depending on the value of `frame_mbs_only_flag`, the following applies: + +- If `frame_mbs_only_flag` is equal to 1, the vertical offset is specified in units of two luma samples. +- Otherwise (`frame_mbs_only_flag` is equal to 0), the vertical offset is specified in units of four luma samples. + +When `seq_scaled_ref_layer_bottom_offset` is not present, it shall be inferred to be equal to 0. The value of `seq_scaled_ref_layer_bottom_offset` shall be in the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. + +**`seq_tcoeff_level_prediction_flag`** specifies the presence of the syntax element `adaptive_tcoeff_level_prediction_flag` in the subset sequence parameter set. + +**`adaptive_tcoeff_level_prediction_flag`** specifies the presence of `tcoeff_level_prediction_flag` in slice headers that refer to the subset sequence parameter set. When `adaptive_tcoeff_level_prediction_flag` is not present, it shall be inferred to be equal to 0. + +**`slice_header_restriction_flag`** specifies the presence of syntax elements in slice headers that refer to the subset sequence parameter set. + +#### **F.7.4.2.2 Picture parameter set RBSP semantics** + +The semantics specified in clause 7.4.2.2 apply with substituting "SVC sequence parameter set" for "sequence parameter set" and substituting "active SVC sequence parameter set or active layer SVC sequence parameter set" for "active sequence parameter set". Additionally, the following applies. + +**`num_slice_groups_minus1`** plus 1 specifies the number of slice groups for a picture. When `num_slice_groups_minus1` is equal to 0, all slices of the picture belong to the same slice group. The allowed range of `num_slice_groups_minus1` is specified in clause F.10. + +#### **F.7.4.2.3 Supplemental enhancement information RBSP semantics** + +The semantics specified in clause 7.4.2.3 apply. + +##### **F.7.4.2.3.1 Supplemental enhancement information message semantics** + +The semantics specified in clause 7.4.2.3.1 apply. + +#### **F.7.4.2.4 Access unit delimiter RBSP semantics** + +The semantics specified in clause 7.4.2.4 apply. + +NOTE – The value of `primary_pic_type` applies to the `slice_type` values in all slice headers of the primary coded picture, including the `slice_type` syntax elements in all NAL units with `nal_unit_type` equal to 1, 5, or 20. NAL units with `nal_unit_type` equal to 2 are not present in bitstreams conforming to any of the profiles specified in this annex. + +#### **F.7.4.2.5 End of sequence RBSP semantics** + +The end of sequence RBSP specifies that the next subsequent access unit in the bitstream in decoding order (if any) shall be an access unit for which all layer representation of the primary coded picture have `IdrPicFlag` equal to 1. The syntax content of the SODB and RBSP for the end of sequence RBSP are empty. No normative decoding process is specified for an end of sequence RBSP. + +#### **F.7.4.2.6 End of stream RBSP semantics** + +The semantics specified in clause 7.4.2.6 apply. + +#### **F.7.4.2.7 Filler data RBSP semantics** + +The semantics specified in clause 7.4.2.7 apply with the following addition. + +Filler data NAL units shall be considered to contain the syntax elements `dependency_id`, `quality_id`, `temporal_id`, and `priority_id` with values that are inferred as follows: + +1. Let `prevSvcNalUnit` be the most recent NAL unit in decoding order that has `nal_unit_type` equal to 14 or 20. + +NOTE – The most recent NAL unit in decoding order with `nal_unit_type` equal to 14 or 20 always belongs to the same access unit as the filler data NAL unit. + +2. The values of `dependency_id`, `quality_id`, `temporal_id`, and `priority_id` for the filler data NAL unit are inferred to be equal to the values of `dependency_id`, `quality_id`, `temporal_id`, and `priority_id`, respectively, of the NAL unit `prevSvcNalUnit`. + +#### F.7.4.2.8 Slice layer without partitioning RBSP semantics + +The semantics specified in clause 7.4.2.8 apply. + +#### F.7.4.2.9 Slice data partition RBSP semantics + +Slice data partition syntax is not present in bitstreams conforming to any of the profiles specified in Annex F. + +#### F.7.4.2.10 RBSP slice trailing bits semantics + +The semantics specified in clause 7.4.2.10 apply with the following modifications. + +Let NumBytesInVclNALUnits be the sum of the values of NumBytesInNALUnit for all VCL NAL units of a layer representation and let BinCountsInNALUnits be the number of times that the parsing process function DecodeBin(), specified in clause 9.3.3.2, is invoked to decode the contents of all VCL NAL units of the layer representation. When entropy\_coding\_mode\_flag is equal to 1, it is a requirement of bitstream conformance that BinCountsInNALUnits shall not exceed $(32 \div 3) * \text{NumBytesInVclNALUnits} + (\text{RawMbBits} * \text{PicSizeInMbs}) \div 32$ . + +NOTE – The constraint on the maximum number of bins resulting from decoding the contents of the slice layer NAL units of a layer representation can be met by inserting a number of cabac\_zero\_word syntax elements to increase the value of NumBytesInVclNALUnits. Each cabac\_zero\_word is represented in a NAL unit by the three-byte sequence 0x000003 (as a result of the constraints on NAL unit contents that result in requiring inclusion of an emulation\_prevention\_three\_byte for each cabac\_zero\_word). + +#### F.7.4.2.11 RBSP trailing bits semantics + +The semantics specified in clause 7.4.2.11 apply. + +#### F.7.4.2.12 Prefix NAL unit RBSP semantics + +The semantics specified in clause 7.4.2.12 apply. + +##### F.7.4.2.12.1 Prefix NAL unit SVC semantics + +The syntax element store\_ref\_base\_pic\_flag is considered as if it was present in the associated NAL unit. + +**store\_ref\_base\_pic\_flag** equal to 1 specifies that, when the value of dependency\_id as specified in the NAL unit header is equal to the maximum value of dependency\_id for the VCL NAL units of the current coded picture, an additional representation of the coded picture that may or may not be identical to the decoded picture is marked as "used for reference". This additional representation is also referred to as reference base picture and may be used for inter prediction of following pictures in decoding order, but it is not output. When store\_ref\_base\_pic\_flag is not present, it shall be inferred to be equal to 0. + +The syntax element store\_ref\_base\_pic\_flag shall have the same value for all VCL NAL units of a dependency representation. When nal\_ref\_idc is equal to 0, store\_ref\_base\_pic\_flag shall be equal to 0. + +When max\_num\_ref\_frames is less than 2 in the SVC sequence parameter set that is referred to by the associated NAL unit, store\_ref\_base\_pic\_flag shall be equal to 0. + +**additional\_prefix\_nal\_unit\_extension\_flag** equal to 0 specifies that the prefix\_nal\_unit\_svc() syntax structure does not contain any additional\_prefix\_nal\_unit\_extension\_data\_flag syntax elements. additional\_prefix\_nal\_unit\_extension\_flag shall be equal to 0 in bitstreams conforming to this Recommendation | International Standard. The value of 1 for additional\_prefix\_nal\_unit\_extension\_flag is reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all data that follow the value 1 for additional\_prefix\_nal\_unit\_extension\_flag in a prefix\_nal\_unit\_svc() syntax structure. + +**additional\_prefix\_nal\_unit\_extension\_data\_flag** may have any value. + +NOTE – The syntax elements additional\_prefix\_nal\_unit\_extension\_flag and additional\_prefix\_nal\_unit\_extension\_data\_flag are not used by the decoding process specified in this Recommendation | International Standard. + +#### F.7.4.2.13 Slice layer extension RBSP semantics + +The semantics specified in clause 7.4.2.13 apply. + +### F.7.4.3 Slice header semantics + +The semantics specified in clause 7.4.3 apply with the following modifications. + +- All referenced syntax elements and variables are syntax elements and variables for the dependency representation with dependency\_id equal to 0. +- A frame, field, top field, bottom field, picture, and decoded picture is interpreted as layer frame, layer field, layer top field, layer bottom field, layer picture, and decoded layer picture, respectively, that represent an intermediate decoding result for the dependency representation with dependency\_id equal to 0. + +- c) An IDR picture is interpreted as layer picture with IdrPicFlag equal to 1 for the dependency representation with dependency\_id equal to 0. +- d) An IDR access unit is interpreted as an access unit containing a primary coded picture with IdrPicFlag equal to 1 for the dependency representation with dependency\_id equal to 0. +- e) A reference frame, reference field, and reference picture is interpreted as layer frame, layer field, and layer picture with nal\_ref\_idc greater than 0 for the dependency representation with dependency\_id equal to 0. +- f) A non-reference frame, non-reference field, and non-reference picture is interpreted as layer frame, layer field, and layer picture with nal\_ref\_idc equal to 0 for the dependency representation with dependency\_id equal to 0. +- g) All constraints specified in clause 7.4.3 apply only to layer representations with DQId equal to 0. +- h) The slice\_header() syntax structure shall be considered to contain the following syntax elements with the following inferred values: + - ref\_layer\_dq\_id is inferred to be equal to -1. + - scan\_idx\_start is inferred to be equal to 0. + - scan\_idx\_end is inferred to be equal to 15. +- i) References to the decoded reference picture marking process as specified in clause 8.2.5 are replaced with reference to the SVC decoded reference picture marking process as specified in clause F.8.2.4. +- j) The value of direct\_spatial\_mv\_pred\_flag shall be equal to 1. +- k) The variable MaxRefLayerDQId is set equal to -1. +- l) The variable CroppingChangeFlag is set equal to 0. +- m) The variable SpatialResolutionChangeFlag is set equal to 0. +- n) In the semantics of first\_mb\_in\_slice, the reference to Annex A is substituted with a reference to clause F.10. + +#### F.7.4.3.1 Reference picture list modification semantics + +The semantics specified in clause 7.4.3.1 apply. For this specification, the modifications a) to f) specified in clause F.7.4.3 apply. When quality\_id is greater than 0, all syntax elements of the ref\_pic\_list\_modification() syntax structure are inferred as specified in the beginning of clause F.7.4.3.4. + +#### F.7.4.3.2 Prediction weight table semantics + +The semantics specified in clause 7.4.3.2 apply. When quality\_id is greater than 0, all syntax elements of the pred\_weight\_table() syntax structure are inferred as specified in the beginning of clause F.7.4.3.4. + +#### F.7.4.3.3 Decoded reference picture marking semantics + +The semantics specified in clause 7.4.3.3 apply with substituting "SVC sequence parameter set" for "sequence parameter set" and with considering the reference pictures marked as "reference base pictures" as not present. The constraints specified in clause 7.4.3.3 apply only to the dependency representation with dependency\_id equal to the current value of dependency\_id and the modifications a) and b) specified in clause F.8.2 apply with currDependencyId being equal to the current value of dependency\_id. + +When quality\_id is greater than 0, all syntax elements of the dec\_ref\_pic\_marking() syntax structure are inferred as specified in the beginning of clause F.7.4.3.4. + +In addition to the constraints specified in clause 7.4.3.3, the following constraints are specified: + +- a) When decoding a frame, the dec\_ref\_pic\_marking() syntax structure shall not contain a memory\_management\_control\_operation command equal to 3 that assigns a long-term frame index to a complementary reference field pair (not marked as "reference base picture") when any of the following conditions are true (when processing the memory\_management\_control\_operation command equal to 3): + - there exists a non-paired reference base field (marked as "reference base picture") that is associated with one of the fields of the complementary reference field pair and that is marked as "used for reference", + - there exists a complementary reference base field pair (marked as "reference base picture") that is associated with the complementary reference field pair and in which one field is marked as "used for reference" and the other field is marked as "unused for reference". +- b) When decoding a field, the dec\_ref\_pic\_marking() syntax structure shall not contain a memory\_management\_control\_operation command equal to 3 that assigns a long-term frame index to a field + +(not marked as "reference base picture") of a reference frame or a complementary reference field pair when both of the following conditions are true (when processing the memory\_management\_control\_operation command equal to 3): + +- the other field of the reference frame or complementary reference field pair is marked as "unused for reference", + - there exists a reference base frame or a complementary reference base field pair (marked as "reference base picture") that is associated with the reference frame or complementary reference field pair, respectively, and in which both fields are marked as "used for reference". +- c) When decoding the second field (in decoding order) of a complementary reference field pair, the dec\_ref\_pic\_marking( ) syntax structure shall not contain a memory\_management\_control\_operation command equal to 6 that assigns a long-term frame index to this field when both of the following conditions are true: +- there exists a reference base field (marked as "reference base picture") that is associated with the first field of the complementary reference field pair and that is marked as "used for short-term reference" when the memory\_management\_control\_operation command equal to 6 is processed, + - the dec\_ref\_pic\_marking( ) syntax structure does not contain a memory\_management\_control\_operation command equal to 3 that assigns the same long-term frame index to the first field of the complementary reference field pair. + +NOTE – The additional constraints specified above (in connection with the constraints specified in clause 7.4.3.3) ensure that after processing all memory\_management\_control\_operation commands of the decoded reference picture marking syntax structure the following applies, with reference entry being a collective term for a non-paired reference field, a reference frame, or a complementary reference field pair (not marked as "reference base picture") and reference base entry being a collective term for a non-paired reference base field, a reference base frame, or a complementary reference base field pair (marked as "reference base picture"): When one or more fields of a reference entry are marked as "used for reference" and there exists a reference base entry that is associated with the reference entry or one field of the reference entry and one or more fields of the reference base entry are marked as "used for reference", either all fields of the reference entry and the reference base entry that are marked as "used for reference" must be marked as "used for short-term reference" or all fields of the reference entry and the reference base entry that are marked as "used for reference" must be marked as "used for long-term reference". When these fields are marked as "used for long-term reference", the same value of long-term frame index must be assigned to all fields of the reference entry and the reference base entry that are marked as "used for reference". + +#### F.7.4.3.4 Slice header in scalable extension semantics + +Unless stated otherwise, for all references to clause 7.4.3 inside this clause, the following modifications apply. + +- a) All referenced syntax elements and variables are syntax elements and variables for the dependency representation with dependency\_id equal to the current value of dependency\_id. +- b) A frame, field, top field, bottom field, picture, and decoded picture is interpreted as layer frame, layer field, layer top field, layer bottom field, layer picture, and decoded layer picture, respectively, that represent an intermediate decoding result for the dependency representation with dependency\_id equal to the current value of dependency\_id. +- c) An IDR picture is interpreted as layer picture with IdrPicFlag equal to 1 for the dependency representation with dependency\_id equal to the current value of dependency\_id. +- d) An IDR access unit is interpreted as an access unit containing a primary coded picture with IdrPicFlag equal to 1 for the dependency representation with dependency\_id equal to the current value of dependency\_id. +- e) A reference frame, reference field, and reference picture is interpreted as layer frame, layer field, and layer picture with nal\_ref\_idc greater than 0 for the dependency representation with dependency\_id equal to the current value of dependency\_id. +- f) A non-reference frame, non-reference field, and non-reference picture is interpreted as layer frame, layer field, and layer picture with nal\_ref\_idc equal to 0 for the dependency representation with dependency\_id equal to the current value of dependency\_id. +- g) References to the decoded reference picture marking process as specified in clause 8.2.5 are replaced with reference to the SVC decoded reference picture marking process as specified in clause F.8.2.4. + +When quality\_id is greater than 0, the following syntax elements (which are not present) shall be inferred to be equal to the corresponding syntax elements of the slice header of the slice with dependency\_id equal to the current value of dependency\_id and quality\_id equal to 0, in the same coded picture, that covers the macroblock with the macroblock address (first\_mb\_in\_slice \* ( 1 + MbaffFrameFlag )), when present in this slice: direct\_spatial\_mv\_pred\_flag, num\_ref\_idx\_active\_override\_flag, num\_ref\_idx\_l0\_active\_minus1, num\_ref\_idx\_l1\_active\_minus1, all syntax elements of the syntax structure ref\_pic\_list\_modification( ), base\_pred\_weight\_table\_flag, all syntax elements of the + +syntax structure pred\_weight\_table( ), all syntax elements of the syntax structure dec\_ref\_pic\_marking( ), all syntax elements of the syntax structure dec\_ref\_base\_pic\_marking( ), and store\_ref\_base\_pic\_flag. + +The value of the following SVC sequence parameter set syntax elements shall be the same across all coded slice NAL units of an access unit: bit\_depth\_luma\_minus8, bit\_depth\_chroma\_minus8, and chroma\_format\_idc. + +The value of the following picture parameter set syntax elements shall be the same across all coded slice NAL units of a dependency representation: bottom\_field\_pic\_order\_in\_frame\_present\_flag, num\_ref\_idx\_l0\_default\_active\_minus1, num\_ref\_idx\_l1\_default\_active\_minus1, weighted\_pred\_flag, and weighted\_bipred\_idc. + +For all coded slice NAL units of a coded picture in which the syntax element field\_pic\_flag is present, field\_pic\_flag shall have the same value. + +For all coded slice NAL units of a coded picture in which the syntax element bottom\_field\_flag is present, bottom\_field\_flag shall have the same value. + +When present in any coded slice NAL unit of a dependency representation, the value of the following slice header syntax elements shall be the same across all slices of the dependency representation including slice headers of NAL units with nal\_unit\_type equal to 1 or 5: frame\_num, idr\_pic\_id, pic\_order\_cnt\_lsb, delta\_pic\_order\_cnt\_bottom, delta\_pic\_order\_cnt[ 0 ], and delta\_pic\_order\_cnt[ 1 ]. + +When present, the value of the following slice header syntax elements shall be the same across all slices of a layer representation: pic\_parameter\_set\_id, ref\_layer\_dq\_id, disable\_inter\_layer\_deblocking\_filter\_idc, inter\_layer\_slice\_alpha\_c0\_offset\_div2, inter\_layer\_slice\_beta\_offset\_div2, constrained\_intra\_resampling\_flag, ref\_layer\_chroma\_phase\_x\_plus1\_flag, ref\_layer\_chroma\_phase\_y\_plus1, scaled\_ref\_layer\_left\_offset, scaled\_ref\_layer\_top\_offset, scaled\_ref\_layer\_right\_offset, scaled\_ref\_layer\_bottom\_offset, slice\_group\_change\_cycle, store\_ref\_base\_pic\_flag, tcoeff\_level\_prediction\_flag, and all syntax elements of the syntax structures dec\_ref\_pic\_marking( ) and dec\_ref\_base\_pic\_marking( ). + +Let setOfRefLayerSlices be the set of slices with dependency\_id equal to the current value of dependency\_id and quality\_id equal to 0, inside the current coded picture, that are covered or partly covered by the macroblocks of the current slice. + +When quality\_id is greater than 0, the value of (slice\_type % 5) for all slices in the set setOfRefLayerSlices shall be the same as the value of (slice\_type % 5) for the current slice. + +When quality\_id is greater than 0 and setOfRefLayerSlices contains more than one slice, the following constraints shall be obeyed: + +- a) When slice\_type specifies an EP or EB slice, the value of num\_ref\_idx\_l0\_active\_minus1 (either the value transmitted in the slice header when num\_ref\_idx\_active\_override\_flag is equal to 1 or the inferred value when num\_ref\_idx\_active\_override\_flag is equal to 0) shall be the same across all slices of the set setOfRefLayerSlices. +- b) When slice\_type specifies an EB slice, the value of num\_ref\_idx\_l1\_active\_minus1 (either the value transmitted in the slice header when num\_ref\_idx\_active\_override\_flag is equal to 1 or the inferred value when num\_ref\_idx\_active\_override\_flag is equal to 0) shall be the same across all slices of the set setOfRefLayerSlices. +- c) All elements of the syntax structure ref\_pic\_list\_modification( ) shall be the same across all slices of the set setOfRefLayerSlices. +- d) When slice\_type specifies an EP slice, the following applies: + - i) When weighted\_pred\_flag is equal to 1, the value of base\_pred\_weight\_table\_flag shall be the same across all slices of the set setOfRefLayerSlices. + - ii) When weighted\_pred\_flag is equal to 1 and pred\_weight\_table( ) is present in the slices of the set setOfRefLayerSlices, the values of all syntax elements inside the syntax structure pred\_weight\_table( ) shall be the same across all slices of the set setOfRefLayerSlices. +- e) When slice\_type specifies an EB slice, the following applies: + - i) When weighted\_bipred\_idc is equal to 1, the value of base\_pred\_weight\_table\_flag shall be the same across all slices of the set setOfRefLayerSlices. + - ii) When weighted\_bipred\_idc is equal to 1 and pred\_weight\_table( ) is present in the slices of the set setOfRefLayerSlices, the values of all syntax elements inside the syntax structure pred\_weight\_table( ) shall be the same across all slices of the set setOfRefLayerSlices. + +**first\_mb\_in\_slice** has the same semantics as specified in clause 7.4.3 with the term current picture being substituted by the term current layer representation and with the reference to Annex A being substituted by a reference to clause F.10. + +**slice\_type** specifies the coding type of the slice according to Table F-1. + +**Table F-1 – Name association to slice\_type for NAL units with nal\_unit\_type equal to 20** + +| slice_type | Name of slice_type | +|-------------------|------------------------------------| +| 0, 5 | EP (P slice in scalable extension) | +| 1, 6 | EB (B slice in scalable extension) | +| 2, 7 | EI (I slice in scalable extension) | + +When **slice\_type** has a value in the range 5..7, it is a requirement of bitstream conformance that all other slices of the current layer representation shall have a value of **slice\_type** equal to the current value of **slice\_type** or equal to the current value of **slice\_type** minus 5. + +NOTE 1 – Values of **slice\_type** in the range 5..7 can be used by an encoder to indicate that all slices of a layer representation have the same value of (**slice\_type** % 5). Values of **slice\_type** in the range 5..7 are otherwise equivalent to corresponding values in the range 0..2. + +When **idr\_flag** is equal to 1 or **max\_num\_ref\_frames** is equal to 0, **slice\_type** shall be equal to 2 or 7. + +In the text (in particular when the clauses 7 to 9 are referenced in this annex), slices with (**slice\_type** % 5) equal to 0, 1, and 2 may be collectively referred to as P, B, and I slices, respectively, regardless of whether the slices are coded using NAL units with **nal\_unit\_type** equal to 20 (**slice\_type** is present in the **slice\_header\_in\_scalable\_extension()** syntax structure) or NAL units with **nal\_unit\_type** in the range of 1 to 5, inclusive (**slice\_type** is present in the **slice\_header()** syntax structure). + +**pic\_parameter\_set\_id** has the same semantics as specified in clause 7.4.3. + +**colour\_plane\_id** has the same semantics as specified in clause 7.4.3. + +**frame\_num** is used as an identifier for dependency representations and shall be represented by **log2\_max\_frame\_num\_minus4 + 4** bits in the bitstream. + +**frame\_num** is constrained as specified in clause 7.4.3. For this specification, the modifications a) to f) specified in the first paragraph of this clause apply. + +**field\_pic\_flag** and **bottom\_field\_flag** have the same semantics as specified in clause 7.4.3. For this specification, the modifications a) to d) specified in the first paragraph of this clause apply. + +**idr\_pic\_id** identifies an IDR picture when **dependency\_id** is equal to the maximum present value of **dependency\_id** in the VCL NAL units of the current coded picture. The value of **idr\_pic\_id** shall be in the range of 0 to 65535, inclusive. + +When two consecutive access units in decoding order are both IDR access units, the value of **idr\_pic\_id** in the slices of the target dependency representation in the primary coded pictures of the first such IDR access unit shall differ from the **idr\_pic\_id** in the slices of the target dependency representation in the primary coded pictures of the second such IDR access unit. + +NOTE 2 – The classification of an access unit as IDR access unit depends on the maximum present value of **dependency\_id**. When NAL units are removed from a bitstream, e.g. in order to adjust the bitstream to the capabilities of a receiving device, the classification of access units as IDR access units may change. Since all bitstreams for different conformance points supported in a scalable bitstream (in particular for different maximum values of **dependency\_id**) must conform to this Recommendation | International Standard (as specified in clause F.8.8.1), the constraints on **idr\_pic\_id** must be obeyed for all conformance points contained in a scalable bitstream. + +**pic\_order\_cnt\_lsb**, **delta\_pic\_order\_cnt\_bottom**, **delta\_pic\_order\_cnt[ 0 ]**, and **delta\_pic\_order\_cnt[ 1 ]** have the same semantics as specified in clause 7.4.3. For this specification, the modifications a) to f) specified in the first paragraph of this clause apply. + +**redundant\_pic\_cnt** has the same semantics as specified in clause 7.4.3. For this specification, the modifications a) to g) specified in the first paragraph of this clause apply. + +**direct\_spatial\_mv\_pred\_flag** specifies the method used in the decoding process to derive motion vectors and reference indices for inter prediction. When **quality\_id** is greater than 0, **direct\_spatial\_mv\_pred\_flag** is inferred as specified in the beginning of this clause. The value of **direct\_spatial\_mv\_pred\_flag** shall be equal to 1. + +**num\_ref\_idx\_active\_override\_flag**, **num\_ref\_idx\_l0\_active\_minus1**, and **num\_ref\_idx\_l1\_active\_minus1** have the same semantics as specified in clause 7.4.3. When **quality\_id** is greater than 0, **num\_ref\_idx\_active\_override\_flag**, **num\_ref\_idx\_l0\_active\_minus1**, and **num\_ref\_idx\_l1\_active\_minus1** are inferred as specified in the beginning of this clause. + +**base\_pred\_weight\_table\_flag** equal to 1 specifies that the variables for weighted prediction are inferred. When **base\_pred\_weight\_table\_flag** is not present, it shall be inferred as follows: + +- If **quality\_id** is greater than 0, **base\_pred\_weight\_table\_flag** is inferred as specified in the beginning of this clause. +- Otherwise (**quality\_id** is equal to 0), **base\_pred\_weight\_table\_flag** is inferred to be equal to 0. + +When **base\_pred\_weight\_table\_flag** is equal to 1 and **quality\_id** is equal to 0, let **refSetOfSlices** be the set of slices that is represented by the VCL NAL units with **dependency\_id** equal to (**ref\_layer\_dq\_id** >> 4) and **quality\_id** equal to 0 inside the current coded picture. + +When **base\_pred\_weight\_table\_flag** is equal to 1 and **quality\_id** is equal to 0, the following constraints shall be obeyed: + +- a) For all slices in **refSetOfSlices**, the value of (**slice\_type** % 5) shall be equal to (**slice\_type** % 5) of the current slice. +- b) **base\_pred\_weight\_table\_flag** shall have the same value in all slices in **refSetOfSlices**. +- c) When the syntax structure **pred\_weight\_table()** is present in the slices of the set **refSetOfSlices**, the values of all syntax elements inside the syntax structure **pred\_weight\_table()** shall be the same for all slices in **refSetOfSlices**. +- d) When the current slice is an EP slice, the following applies: + - i) The value of **num\_ref\_idx\_l0\_active\_minus1** of all slices in **refSetOfSlices** shall be identical to the value of **num\_ref\_idx\_l0\_active\_minus1** of the current slice. + - ii) For each slice in **refSetOfSlices**, the syntax elements inside the syntax structure **ref\_pic\_list\_modification()** shall be the same, and the syntax structure **ref\_pic\_list\_modification()** for the slices in **refSetOfSlices** shall contain syntax elements so that for **useRefBasePicFlag** equal to 0 and 1, an invocation of clause F.8.2.3 with **currDependencyId** set equal to (**ref\_layer\_dq\_id** >> 4), **useRefBasePicFlag**, and any slice of **refSetOfSlices** as the inputs derives a reference picture list **refPicList0RefLayer** that is identical to the reference picture list **refPicList0**, which is derived by invoking clause F.8.2.3 with **currDependencyId** set equal to **dependency\_id**, **useRefBasePicFlag**, and the current slice as the inputs. The entries of two reference picture lists are considered the same when they represent entries that correspond to same coded frame, the same complementary reference field pair, the same coded field, or the same field of a coded frame. + - iii) **weighted\_pred\_flag** shall be equal to 1 for the slices in **refSetOfSlices**. +- e) When the current slice is an EB slice, the following applies: + - i) The values of **num\_ref\_idx\_l0\_active\_minus1** and **num\_ref\_idx\_l1\_active\_minus1** of all slices in **refSetOfSlices** shall be identical to the values of **num\_ref\_idx\_l0\_active\_minus1** and **num\_ref\_idx\_l1\_active\_minus1**, respectively, of the current slice. + - ii) For each slice in **refSetOfSlices**, the syntax elements inside the syntax structure **ref\_pic\_list\_modification()** shall be the same, and the syntax structure **ref\_pic\_list\_modification()** for the slices in **refSetOfSlices** shall contain syntax elements so that for **useRefBasePicFlag** equal to 0 and 1, an invocation of clause F.8.2.3 with **currDependencyId** set equal to (**ref\_layer\_dq\_id** >> 4), **useRefBasePicFlag**, and any slice of **refSetOfSlices** as the inputs derives reference picture lists **refPicList0RefLayer** and **refPicList1RefLayer** that are identical to the reference picture lists **refPicList0** and **refPicList1**, respectively, which are derived by invoking clause F.8.2.3 with **currDependencyId** set equal to **dependency\_id**, **useRefBasePicFlag**, and the current slice as the inputs. The entries of two reference picture lists are considered the same when they represent entries that correspond to same coded frame, the same complementary reference field pair, the same coded field, or the same field of a coded frame. + - iii) **weighted\_bipred\_idc** shall be equal to 1 for the slices in **refSetOfSlices**. + +**store\_ref\_base\_pic\_flag** equal to 1 specifies that, when the value of **dependency\_id** is equal to the maximum value of **dependency\_id** for the VCL NAL units of the current coded picture, an additional representation of the coded picture that may or may not be identical to the decoded picture is marked as "used for reference". This additional representation is also referred to as reference base picture and may be used for inter prediction of following pictures in decoding order, but it is not output. When **store\_ref\_base\_pic\_flag** is not present, it shall be inferred as follows: + +- If **quality\_id** is equal to 0, **store\_ref\_base\_pic\_flag** is inferred to be equal to 0. +- Otherwise (**quality\_id** is greater than 0), **store\_ref\_base\_pic\_flag** is inferred as specified in the beginning of this clause. + +The syntax element `store_ref_base_pic_flag` shall have the same value for all VCL NAL units of a dependency representation. When `nal_ref_idc` is equal to 0, `store_ref_base_pic_flag` shall be equal to 0. + +When `max_num_ref_frames` is less than 2, `store_ref_base_pic_flag` shall be equal to 0. + +**`cabac_init_idc`** and **`slice_qp_delta`** have the same semantics as specified in clause 7.4.3. + +**`disable_deblocking_filter_idc`** specifies whether the operation of the deblocking filter shall be disabled across some block edges of the slice, specifies for which edges the filtering is disabled, and specifies the order of deblocking filter operations. When `disable_deblocking_filter_idc` is not present in the slice header, the value of `disable_deblocking_filter_idc` shall be inferred to be equal to 0. + +The value of `disable_deblocking_filter_idc` shall be in the range of 0 to 6, inclusive. `disable_deblocking_filter_idc` equal to 0 specifies that all luma and chroma block edges of the slice are filtered. `disable_deblocking_filter_idc` equal to 1 specifies that deblocking is disabled for all block edges of the slice. `disable_deblocking_filter_idc` equal to 2 specifies that all luma and chroma block edges of the slice are filtered with exception of the block edges that coincide with slice boundaries. `disable_deblocking_filter_idc` equal to 3 specifies a two stage deblocking filter process for the slice: After filtering all block luma and chroma block edges that do not coincide with slice boundaries (as if `disable_deblocking_filter_idc` were equal to 2), the luma and chroma block edges that coincide with slice boundaries are filtered. `disable_deblocking_filter_idc` equal to 4 specifies that all luma block edges of the slice are filtered, but the deblocking of the chroma block edges is disabled. `disable_deblocking_filter_idc` equal to 5 specifies that all luma block edges of the slice are filtered with exception of the block edges that coincide with slice boundaries (as if `disable_deblocking_filter_idc` were equal to 2), and that deblocking for chroma block edges of the slice is disabled. `disable_deblocking_filter_idc` equal to 6 specifies that the deblocking for chroma block edges is disabled and that the two stage deblocking filter process is used for luma block edges of the slice: After filtering all block luma block edges that do not coincide with slice boundaries (as if `disable_deblocking_filter_idc` were equal to 2), the luma block edges that coincide with slice boundaries are filtered. + +When `no_inter_layer_pred_flag` is equal to 1 or `tcoeff_level_prediction_flag` is equal to 1, the value of `disable_deblocking_filter_idc` shall be in the range of 0 to 2, inclusive. + +**`slice_alpha_c0_offset_div2`**, and **`slice_beta_offset_div2`** have the same semantics as specified in clause 7.4.3. + +**`slice_group_change_cycle`** has the same semantics as specified in clause 7.4.3. + +**`ref_layer_dq_id`** specifies the layer representation inside the current coded picture that is used for inter-layer prediction of the current layer representation. When present, the value of `ref_layer_dq_id` shall be in the range of 0 to `DQId - 1`, inclusive. When `ref_layer_dq_id` is not present, it shall be inferred as follows: + +- If `quality_id` is greater than 0, `ref_layer_dq_id` is inferred to be equal to (`DQId - 1`). +- Otherwise (`quality_id` is equal to 0), `ref_layer_dq_id` is inferred to be equal to `-1`. + +When `quality_id` is equal to 0, the NAL units with `DQId` equal to `ref_layer_dq_id` shall have `discardable_flag` equal to 0. + +When `ref_layer_dq_id` is greater than or equal to 0, it is a requirement of bitstream conformance that the layer representation with `DQId` equal to `ref_layer_dq_id` is present in the bitstream. + +The variable `MaxRefLayerDQId` is set equal to the maximum value of `ref_layer_dq_id` for the slices of the current layer representation. + +When `MinNoInterLayerPredFlag` is equal to 0, the layer representation inside the current coded picture that has a value of `DQId` equal `MaxRefLayerDQId` is also referred to as reference layer representation. + +When `MaxRefLayerDQId` is not equal to `-1`, the following variables are derived as follows: + +- `RefLayerPicSizeInMbs` is set equal to the value of the variable `PicSizeInMbs` for the reference layer representation. +- `RefLayerPicWidthInMbs` is set equal to the value of the variable `PicWidthInMbs` for the reference layer representation. +- `RefLayerPicHeightInMbs` is set equal to the value of the variable `PicHeightInMbs` for the reference layer representation. +- `RefLayerChromaFormatIdc` is set equal to the value of the syntax element `chroma_format_idc` for the reference layer representation. +- `RefLayerChromaArrayType` is set equal to the value of `ChromaArrayType` for the reference layer representation. +- `RefLayerPicWidthInSamplesL` is set equal to the value of the variable `PicWidthInSamplesL` for the reference layer representation. + +- RefLayerPicHeightInSamplesL is set equal to the value of the variable PicHeightInSamplesL for the reference layer representation. +- RefLayerPicWidthInSamplesC is set equal to the value of the variable PicWidthInSamplesC for the reference layer representation. +- RefLayerPicHeightInSamplesC is set equal to the value of the variable PicHeightInSamplesC for the reference layer representation. +- RefLayerMbWidthC is set equal to the value of the variable MbWidthC for the reference layer representation. +- RefLayerMbHeightC is set equal to the value of the variable MbHeightC for the reference layer representation. +- RefLayerFrameMbsOnlyFlag is set equal to the value of the syntax element frame\_mbs\_only\_flag for the reference layer representation. +- RefLayerFieldPicFlag is set equal to the value of the syntax element field\_pic\_flag for the reference layer representation. +- RefLayerBottomFieldFlag is set equal to the value of the syntax element bottom\_field\_flag for the reference layer representation. +- RefLayerMbaffFrameFlag is set equal to the value of the variable MbaffFrameFlag for the reference layer representation. + +**disable\_inter\_layer\_deblocking\_filter\_idc** specifies whether the operation of the deblocking filter for inter-layer intra prediction is disabled across some block edges of the reference layer representation, specifies for which edges the filtering is disabled, and specifies the order of deblocking filter operations for inter-layer intra prediction. When disable\_inter\_layer\_deblocking\_filter\_idc is not present in the slice header, the value of disable\_inter\_layer\_deblocking\_filter\_idc shall be inferred to be equal to 0. The value of disable\_inter\_layer\_deblocking\_filter\_idc shall be in the range of 0 to 6, inclusive. The values 0 to 6 of disable\_inter\_layer\_deblocking\_filter\_idc specify the same deblocking filter operations as the corresponding values of disable\_deblocking\_filter\_idc, but for the deblocking of the intra macroblocks of the reference layer representation specified by ref\_layer\_dq\_id before resampling. + +When disable\_inter\_layer\_deblocking\_filter\_idc is present, quality\_id is equal to 0, and SpatialResolutionChangeFlag as specified in the following paragraphs is equal to 0, disable\_inter\_layer\_deblocking\_filter\_idc shall be equal to 1. + +**inter\_layer\_slice\_alpha\_c0\_offset\_div2** specifies the offset used in accessing the $\alpha$ and $t_{C0}$ deblocking filter tables for filtering operations of the intra macroblocks of the reference layer representation before resampling. From this value, the offset that is applied when addressing these tables shall be computed as: + +$$\text{InterlayerFilterOffsetA} = \text{inter\_layer\_slice\_alpha\_c0\_offset\_div2} \ll 1 \quad (\text{F-64})$$ + +The value of inter\_layer\_slice\_alpha\_c0\_offset\_div2 shall be in the range of -6 to +6, inclusive. When inter\_layer\_slice\_alpha\_c0\_offset\_div2 is not present in the slice header, the value of inter\_layer\_slice\_alpha\_c0\_offset\_div2 shall be inferred to be equal to 0. + +**inter\_layer\_slice\_beta\_offset\_div2** specifies the offset used in accessing the $\beta$ deblocking filter table for filtering operations of the intra macroblocks of the reference layer representation before resampling. From this value, the offset that is applied when addressing the $\beta$ table of the deblocking filter is computed as: + +$$\text{InterlayerFilterOffsetB} = \text{inter\_layer\_slice\_beta\_offset\_div2} \ll 1 \quad (\text{F-65})$$ + +The value of inter\_layer\_slice\_beta\_offset\_div2 shall be in the range of -6 to +6, inclusive. When inter\_layer\_slice\_beta\_offset\_div2 is not present in the slice header the value of inter\_layer\_slice\_beta\_offset\_div2 shall be inferred to be equal to 0. + +**constrained\_intra\_resampling\_flag** specifies whether slice boundaries in the layer picture that is used for inter-layer prediction (as specified by ref\_layer\_dq\_id) are treated similar to layer picture boundaries for the intra resampling process. When constrained\_intra\_resampling\_flag is equal to 1, disable\_inter\_layer\_deblocking\_filter\_idc shall be equal to 1, 2, or 5. + +When constrained\_intra\_resampling\_flag is equal to 1, a macroblock cannot be coded using the Intra\_Base macroblock prediction mode when it covers more than one slice in the layer picture that is used for inter-layer prediction, as specified in clause F.8.6.2. + +When constrained\_intra\_resampling\_flag is not present, it shall be inferred to be equal to 0. + +**ref\_layer\_chroma\_phase\_x\_plus1\_flag** specifies the horizontal phase shift of the chroma components in units of half luma samples of a layer frame for the layer pictures that may be used for inter-layer prediction. + +When **ref\_layer\_chroma\_phase\_x\_plus1\_flag** is not present, it shall be inferred as follows: + +- If **quality\_id** is greater than 0, **ref\_layer\_chroma\_phase\_x\_plus1\_flag** is inferred to be equal to **chroma\_phase\_x\_plus1\_flag**. +- Otherwise (**quality\_id** is equal to 0), **ref\_layer\_chroma\_phase\_x\_plus1\_flag** is inferred to be equal to **seq\_ref\_layer\_chroma\_phase\_x\_plus1\_flag**. + +When **no\_inter\_layer\_pred\_flag** is equal to 0, the following is specified: + +- a) When **ref\_layer\_dq\_id** is greater than 0, **ref\_layer\_chroma\_phase\_x\_plus1\_flag** should be equal to **chroma\_phase\_x\_plus1\_flag** of the subset sequence parameter set RBSP that is referred to by the reference layer representation (with **DQId** equal to **ref\_layer\_dq\_id**). +- b) When **RefLayerChromaArrayType** is equal to 1 and **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** are present in the SVC sequence parameter set that is referred to by the reference layer representation (with **DQId** equal to **ref\_layer\_dq\_id**), the following applies: + - If **ref\_layer\_chroma\_phase\_x\_plus1\_flag** is equal to 0, **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** of the SVC sequence parameter set that is referred to by the reference layer representation should be equal to 0, 2, or 4. + - Otherwise (**ref\_layer\_chroma\_phase\_x\_plus1\_flag** is equal to 1), **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** of the SVC sequence parameter set that is referred to by the reference layer representation should be equal to 1, 3, or 5. +- c) When **RefLayerChromaArrayType** is not equal to 1, **ref\_layer\_chroma\_phase\_x\_plus1\_flag** should be equal to 1. + +**ref\_layer\_chroma\_phase\_y\_plus1** specifies the vertical phase shift of the chroma components in units of half luma samples of a layer frame for the layer pictures that may be used for inter-layer prediction. + +When **ref\_layer\_chroma\_phase\_y\_plus1** is not present, it shall be inferred as follows: + +- If **quality\_id** is greater than 0, **ref\_layer\_chroma\_phase\_y\_plus1** is inferred to be equal to **chroma\_phase\_y\_plus1**. +- Otherwise (**quality\_id** is equal to 0), **ref\_layer\_chroma\_phase\_y\_plus1** is inferred to be equal to **seq\_ref\_layer\_chroma\_phase\_y\_plus1**. + +The value of **ref\_layer\_chroma\_phase\_y\_plus1** shall be in the range of 0 to 2, inclusive. + +When **no\_inter\_layer\_pred\_flag** is equal to 0, the following applies: + +- a) When **ref\_layer\_dq\_id** is greater than 0, **ref\_layer\_chroma\_phase\_y\_plus1** should be equal to **chroma\_phase\_y\_plus1** of the subset sequence parameter set RBSP that is referred to by the reference layer representation (with **DQId** equal to **ref\_layer\_dq\_id**). +- b) When **RefLayerChromaArrayType** is equal to 1 and **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** are present in the SVC sequence parameter set that is referred to by the reference layer representation (with **DQId** equal to **ref\_layer\_dq\_id**), the following applies: + - If **ref\_layer\_chroma\_phase\_y\_plus1** is equal to 0, **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** of the SVC sequence parameter set that is referred to by the reference layer representation should be equal to 2 or 3. + - Otherwise, if **ref\_layer\_chroma\_phase\_y\_plus1** is equal to 1, **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** of the SVC sequence parameter set that is referred to by the reference layer representation should be equal to 0 or 1. + - Otherwise (**chroma\_phase\_y\_plus1** is equal to 2), **chroma\_sample\_loc\_type\_top\_field** and **chroma\_sample\_loc\_type\_bottom\_field** of the SVC sequence parameter set that is referred to by the reference layer representation should be equal to 4 or 5. +- c) When **RefLayerChromaArrayType** is not equal to 1, **ref\_layer\_chroma\_phase\_y\_plus1** should be equal to 1. + +**scaled\_ref\_layer\_left\_offset** specifies the horizontal offset between the upper-left luma sample of a resampled layer picture used for inter-layer prediction and the upper-left luma sample of the current picture or current layer picture in units of two luma samples. + +When **scaled\_ref\_layer\_left\_offset** is not present, it shall be inferred as follows: + +- If `quality_id` is greater than 0, `scaled_ref_layer_left_offset` is inferred to be equal to 0. +- Otherwise (`quality_id` is equal to 0), `scaled_ref_layer_left_offset` is inferred to be equal to `seq_scaled_ref_layer_left_offset`. + +The value of `scaled_ref_layer_left_offset` shall be in the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. + +**scaled\_ref\_layer\_top\_offset** specifies the vertical offset between the upper-left luma sample of a resampled layer picture used for inter-layer prediction and the upper-left luma sample of the current picture or current layer picture. The vertical offset is specified in units of two luma samples when `frame_mbs_only_flag` is equal to 1, and it is specified in units of four luma samples when `frame_mbs_only_flag` is equal to 0. + +When `scaled_ref_layer_top_offset` is not present, it shall be inferred as follows: + +- If `quality_id` is greater than 0, `scaled_ref_layer_top_offset` is inferred to be equal to 0. +- Otherwise (`quality_id` is equal to 0), `scaled_ref_layer_top_offset` is inferred to be equal to `seq_scaled_ref_layer_top_offset`. + +The value of `scaled_ref_layer_top_offset` shall be in the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. + +**scaled\_ref\_layer\_right\_offset** specifies the horizontal offset between the bottom-right luma sample of a resampled layer picture used for inter-layer prediction and the bottom-right luma sample of the current picture or current layer picture in units of two luma samples. + +When `scaled_ref_layer_right_offset` is not present, it shall be inferred as follows: + +- If `quality_id` is greater than 0, `scaled_ref_layer_right_offset` is inferred to be equal to 0. +- Otherwise (`quality_id` is equal to 0), `scaled_ref_layer_right_offset` is inferred to be equal to `seq_scaled_ref_layer_right_offset`. + +The value of `scaled_ref_layer_right_offset` shall be in the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. + +**scaled\_ref\_layer\_bottom\_offset** specifies the vertical offset between the bottom-right luma sample of a resampled layer picture used for inter-layer prediction and the bottom-right luma sample of the current picture or current layer picture. The vertical offset is specified in units of two luma samples when `frame_mbs_only_flag` is equal to 1, and it is specified in units of four luma samples when `frame_mbs_only_flag` is equal to 0. + +When `scaled_ref_layer_bottom_offset` is not present, it shall be inferred as follows: + +- If `quality_id` is greater than 0, `scaled_ref_layer_bottom_offset` is inferred to be equal to 0. +- Otherwise (`quality_id` is equal to 0), `scaled_ref_layer_bottom_offset` is inferred to be equal to `seq_scaled_ref_layer_bottom_offset`. + +The value of `scaled_ref_layer_bottom_offset` shall be in the range of $-2^{15}$ to $2^{15} - 1$ , inclusive. + +The variables `scaledLeftOffset`, `scaledRightOffset`, `scaledTopOffset`, and `scaledBottomOffset` are derived as follows: + +- If `MinNoInterLayerPredFlag` is equal to 0, `scaledLeftOffset`, `scaledRightOffset`, `scaledTopOffset`, and `scaledBottomOffset` are set equal to the values of `scaled_ref_layer_left_offset`, `scaled_ref_layer_right_offset`, `scaled_ref_layer_top_offset`, and `scaled_ref_layer_bottom_offset`, respectively, for the slices of the current layer representation that have `no_inter_layer_pred_flag` equal to 0. +- Otherwise (`MinNoInterLayerPredFlag` is equal to 1), `scaledLeftOffset`, `scaledRightOffset`, `scaledTopOffset`, and `scaledBottomOffset` are set equal to the values of `scaled_ref_layer_left_offset`, `scaled_ref_layer_right_offset`, `scaled_ref_layer_top_offset`, and `scaled_ref_layer_bottom_offset`, respectively. + +The variables `ScaledRefLayerLeftOffset`, `ScaledRefLayerRightOffset`, `ScaledRefLayerTopOffset`, `ScaledRefLayerBottomOffset`, `ScaledRefLayerPicWidthInSamplesL`, and `ScaledRefLayerPicHeightInSamplesL` are derived by + +$$\text{ScaledRefLayerLeftOffset} = 2 * \text{scaledLeftOffset} \quad (\text{F-66})$$ + +$$\text{ScaledRefLayerRightOffset} = 2 * \text{scaledRightOffset} \quad (\text{F-67})$$ + +$$\text{ScaledRefLayerTopOffset} = 2 * \text{scaledTopOffset} * ( 2 - \text{frame\_mbs\_only\_flag} ) \quad (\text{F-68})$$ + +$$\text{ScaledRefLayerBottomOffset} = 2 * \text{scaledBottomOffset} * ( 2 - \text{frame\_mbs\_only\_flag} ) \quad (\text{F-69})$$ + +$$\begin{aligned} \text{ScaledRefLayerPicWidthInSamples}_L = & \text{PicWidthInMbs} * 16 - \text{ScaledRefLayerLeftOffset} - \\ & \text{ScaledRefLayerRightOffset} \end{aligned} \quad (\text{F-70})$$ + +$$\begin{aligned} \text{ScaledRefLayerPicHeightInSamples}_L = & \text{PicHeightInMbs} * 16 - \\ & ( \text{ScaledRefLayerTopOffset} + \text{ScaledRefLayerBottomOffset} ) / \\ & ( 1 + \text{field\_pic\_flag} ) \end{aligned} \quad (\text{F-71})$$ + +When no\_inter\_layer\_pred\_flag is equal to 0, the following constraints shall be obeyed: + +- a) The bitstream shall not contain data that result in $\text{ScaledRefLayerPicWidthInSamples}_L$ less than $\text{RefLayerPicWidthInSamples}_L$ . +- b) When $\text{RefLayerFrameMbsOnlyFlag}$ is equal to 0 or $\text{frame\_mbs\_only\_flag}$ is equal to 1, the bitstream shall not contain data that result in $(\text{ScaledRefLayerPicHeightInSamples}_L * (1 + \text{field\_pic\_flag}))$ less than $(\text{RefLayerPicHeightInSamples}_L * (1 + \text{RefLayerFieldPicFlag}))$ . +- c) When $\text{RefLayerFrameMbsOnlyFlag}$ is equal to 1 and $\text{frame\_mbs\_only\_flag}$ is equal to 0, the bitstream shall not contain data that result in $(\text{ScaledRefLayerPicHeightInSamples}_L * (1 + \text{field\_pic\_flag}))$ less than $(2 * \text{RefLayerPicHeightInSamples}_L)$ . + +When $\text{ChromaArrayType}$ is not equal to 0, the variables $\text{ScaledRefLayerPicWidthInSamples}_C$ , and $\text{ScaledRefLayerPicHeightInSamples}_C$ are derived by + +$$\text{ScaledRefLayerPicWidthInSamples}_C = \text{ScaledRefLayerPicWidthInSamples}_L / \text{SubWidthC} \quad (\text{F-72})$$ + +$$\text{ScaledRefLayerPicHeightInSamples}_C = \text{ScaledRefLayerPicHeightInSamples}_L / \text{SubHeightC} \quad (\text{F-73})$$ + +The variable $\text{CroppingChangeFlag}$ is derived as follows: + +- If $\text{MinNoInterLayerPredFlag}$ is equal to 0, $\text{quality\_id}$ is equal to 0, and $\text{extended\_spatial\_scalability\_idc}$ is equal to 2, $\text{CroppingChangeFlag}$ is set equal to 1. +- Otherwise ( $\text{MinNoInterLayerPredFlag}$ is equal to 1, $\text{quality\_id}$ is greater than 0, or $\text{extended\_spatial\_scalability\_idc}$ is less than 2), $\text{CroppingChangeFlag}$ is set equal to 0. + +NOTE 3 – Encoder designers are encouraged to set the value of $\text{no\_inter\_layer\_pred\_flag}$ equal to 0 for at least one slice of each layer representation with $\text{extended\_spatial\_scalability\_idc}$ equal to 2 and $\text{quality\_id}$ equal to 0. + +The variable $\text{SpatialResolutionChangeFlag}$ is derived as follows: + +- If $\text{MinNoInterLayerPredFlag}$ is equal to 1, $\text{quality\_id}$ is greater than 0, or all of the following conditions are true, $\text{SpatialResolutionChangeFlag}$ is set equal to 0: + - $\text{CroppingChangeFlag}$ is equal to 0, + - $\text{ScaledRefLayerPicWidthInSamples}_L$ is equal to $\text{RefLayerPicWidthInSamples}_L$ , + - $\text{ScaledRefLayerPicHeightInSamples}_L$ is equal to $\text{RefLayerPicHeightInSamples}_L$ , + - $(\text{ScaledRefLayerLeftOffset} \% 16)$ is equal to 0, + - $(\text{ScaledRefLayerTopOffset} \% (16 * (1 + \text{field\_pic\_flag} + \text{MbaffFrameFlag})))$ is equal to 0, + - $\text{field\_pic\_flag}$ is equal to $\text{RefLayerFieldPicFlag}$ , + - $\text{MbaffFrameFlag}$ is equal to $\text{RefLayerMbaffFrameFlag}$ , + - $\text{chroma\_format\_idc}$ is equal to $\text{RefLayerChromaFormatIdc}$ , + - $\text{chroma\_phase\_x\_plus1\_flag}$ is equal to $\text{ref\_layer\_chroma\_phase\_x\_plus1\_flag}$ for the slices with $\text{no\_inter\_layer\_pred\_flag}$ equal to 0, + - $\text{chroma\_phase\_y\_plus1}$ is equal to $\text{ref\_layer\_chroma\_phase\_y\_plus1}$ for the slices with $\text{no\_inter\_layer\_pred\_flag}$ equal to 0. +- Otherwise, $\text{SpatialResolutionChangeFlag}$ is set equal to 1. + +The variable $\text{RestrictedSpatialResolutionChangeFlag}$ is derived as follows: + +- If $\text{SpatialResolutionChangeFlag}$ is equal to 0 or all of the following conditions are true, $\text{RestrictedSpatialResolutionChangeFlag}$ is set equal to 1: + - $\text{ScaledRefLayerPicWidthInSamples}_L$ is equal to $\text{RefLayerPicWidthInSamples}_L$ or $(2 * \text{RefLayerPicWidthInSamples}_L)$ , + - $\text{ScaledRefLayerPicHeightInSamples}_L$ is equal to $\text{RefLayerPicHeightInSamples}_L$ or $(2 * \text{RefLayerPicHeightInSamples}_L)$ , + - $(\text{ScaledRefLayerLeftOffset} \% 16)$ is equal to 0, + - $(\text{ScaledRefLayerTopOffset} \% (16 * (1 + \text{field\_pic\_flag})))$ is equal to 0, + - $\text{MbaffFrameFlag}$ is equal to 0, + +- RefLayerMbaffFrameFlag is equal to 0, +- field\_pic\_flag is equal to RefLayerFieldPicFlag. +- Otherwise, RestrictedSpatialResolutionChangeFlag is set equal to 0. + +**slice\_skip\_flag** specifies the presence of the slice data in scalable extension syntax structure. When slice\_skip\_flag is not present, it shall be inferred to be equal to 0. slice\_skip\_flag equal to 0 specifies that the slice data in scalable extension syntax structure is present in the NAL unit. slice\_skip\_flag equal to 1 specifies that the slice data in scalable extension syntax structure is not present in the NAL unit and that the syntax elements for the macroblock layer of the slice are derived by the following process: + +1. CurrMbAddr is derived by + +$$\text{CurrMbAddr} = \text{first\_mb\_in\_slice} * ( 1 + \text{MbaffFrameFlag} ) \quad (\text{F-74})$$ + +2. The variable mbIdx proceeds over the values 0..num\_mbs\_in\_slice\_minus1, and for each value of mbIdx, the following ordered steps are specified: + - a. The bitstream shall not contain data that result in InCropWindow( CurrMbAddr ) equal to 0. + - b. For the macroblock with address CurrMbAddr, the syntax elements mb\_skip\_flag (when applicable), mb\_skip\_run (when applicable), mb\_field\_decoding\_flag, base\_mode\_flag, residual\_prediction\_flag and coded\_block\_pattern shall be inferred as follows: + - mb\_skip\_flag (when applicable) and mb\_skip\_run (when applicable) are inferred to be equal to 0. + - mb\_field\_decoding\_flag is inferred to be equal to 0. +NOTE 4 – The frame/field mode used for decoding is inferred in clause F.8.1.5.1. + - base\_mode\_flag is inferred to be equal to 1. + - residual\_prediction\_flag is inferred to be equal to 1. + - coded\_block\_pattern is inferred to be equal to 0. + - QPY is inferred to be equal to SliceQPY. + - QP'Y is inferred to be equal to (QPY + QpBdOffsetY). + - c. When the variable mbIdx is less than num\_mbs\_in\_slice\_minus1, CurrMbAddr is set to NextMbAddress( CurrMbAddr ). The bitstream shall not contain data that result in CurrMbAddr being set equal to a value that is not less than PicSizeInMbs. + +**num\_mbs\_in\_slice\_minus1** plus 1 specifies the number of macroblocks for a slice with slice\_skip\_flag equal to 1. + +**adaptive\_base\_mode\_flag** specifies the presence of syntax elements in the slice header and in the macroblock layer in scalable extension. When adaptive\_base\_mode\_flag is not present, it shall be inferred to be equal to 0. + +**default\_base\_mode\_flag** specifies how base\_mode\_flag is inferred when it is not present in macroblock layer in scalable extension. When default\_base\_mode\_flag is not present, it shall be inferred to be equal to 0. + +**adaptive\_motion\_prediction\_flag** specifies the presence of syntax elements in the macroblock layer in scalable extension. When adaptive\_motion\_prediction\_flag is not present, it shall be inferred to be equal to 0. + +**default\_motion\_prediction\_flag** specifies how motion\_prediction\_flag\_l0[ ] and motion\_prediction\_flag\_l1[ ] are inferred when they are not present in macroblock layer in scalable extension. When default\_motion\_prediction\_flag is not present, it shall be inferred to be equal to 0. + +**adaptive\_residual\_prediction\_flag** specifies the presence of syntax elements in the macroblock layer in scalable extension. When adaptive\_residual\_prediction\_flag is not present, it shall be inferred to be equal to 0. + +**default\_residual\_prediction\_flag** specifies how residual\_prediction\_flag is inferred when it is not present in the macroblock layer in scalable extension. When default\_residual\_prediction\_flag is not present, it shall be inferred to be equal to 0. + +**tcoeff\_level\_prediction\_flag** equal to 1 specifies that an alternative inter-layer prediction process is applied as specified in clause F.8. When tcoeff\_level\_prediction\_flag is not present, it shall be inferred as follows: + +- If no\_inter\_layer\_pred\_flag is equal to 1, tcoeff\_level\_prediction\_flag is inferred to be equal to 0. +- Otherwise (no\_inter\_layer\_pred\_flag is equal to 0), tcoeff\_level\_prediction\_flag is inferred to be equal to the value of seq\_tcoeff\_level\_prediction\_flag. + +When SpatialResolutionChangeFlag is equal to 1, tcoeff\_level\_prediction\_flag shall be equal to 0. + +When tcoeff\_level\_prediction\_flag is equal to 1, the following constraints shall be obeyed: + +- a) The slices of the reference layer representation (with DQId equal to ref\_layer\_dq\_id) shall have no\_inter\_layer\_pred\_flag equal to 1 or tcoeff\_level\_prediction\_flag equal to 1. +- b) All elements of ScalingList4x4 shall be the same for the slices of the current layer representation and all slices of the reference layer representation (with DQId equal to the value of ref\_layer\_dq\_id). +- c) All elements of ScalingList8x8 shall be the same for the slices of the current layer representation and all slices of the reference layer representation (with DQId equal to the value of ref\_layer\_dq\_id). +- d) The value of the syntax element use\_ref\_base\_pic\_flag shall be equal to 0 for the slices of the current layer representation and all slices of the reference layer representation (with DQId equal to the value of ref\_layer\_dq\_id). +- e) When slice\_skip\_flag is equal to 1, the value of constrained\_intra\_pred\_flag for the current layer representation shall be identical to the value of constrained\_intra\_pred\_flag for the reference layer representation (with DQId equal to ref\_layer\_dq\_id). + +The variable MaxTCoeffLevelPredFlag is set equal to the maximum value of tcoeff\_level\_prediction\_flag for the slices of the current layer representation. + +**scan\_idx\_start** specifies the first scanning position for the transform coefficient levels in the current slice. When scan\_idx\_start is not present, it shall be inferred to be equal to 0. + +**scan\_idx\_end** specifies the last scanning position for the transform coefficient levels in the current slice. When scan\_idx\_end is not present, it shall be inferred to be equal to 15. + +When default\_base\_mode\_flag is equal to 1, (slice\_type % 5) is equal to 2, and entropy\_coding\_mode\_flag is equal to 0, it is a requirement of bitstream conformance that the value of scan\_idx\_end is greater than or equal to scan\_idx\_start. + +#### F.7.4.3.5 Decoded reference base picture marking semantics + +The specification of this clause applies to the current dependency representation. The modifications a) and b) specified in clause F.8.2 apply with currDependencyId being equal to the current value of dependency\_id. + +The syntax elements adaptive\_ref\_base\_pic\_marking\_mode\_flag, memory\_management\_base\_control\_operation, difference\_of\_base\_pic\_nums\_minus1, and long\_term\_base\_pic\_num specify marking of reference base pictures as "unused for reference". + +When present in a prefix NAL unit, all syntax elements of the dec\_ref\_base\_pic\_marking( ) syntax structure are considered as if they were present in the associated NAL unit. + +When quality\_id is greater than 0, all syntax elements of the dec\_ref\_base\_pic\_marking( ) syntax structure are inferred as specified in the beginning of clause F.7.4.3.4. + +The content of the decoded reference picture base marking syntax structure shall be the same in all slice headers of the primary coded picture. When one or more redundant coded pictures are present, the content of the decoded reference base picture marking syntax structure shall be the same in all slice headers of a redundant coded picture with a particular value of redundant\_pic\_cnt. + +NOTE 1 – It is not required that the content of the decoded reference base picture marking syntax structure in a redundant coded picture with a particular value of redundant\_pic\_cnt is identical to the content of the decoded reference base picture marking syntax structure in the corresponding primary coded picture or a redundant coded picture with a different value of redundant\_pic\_cnt. However, as specified in clause F.7.4.3.4 (by referencing clause 7.4.3), the content of the decoded reference base picture marking syntax structure in a redundant coded picture is constrained in the way that the marking status of reference pictures and the value of frame\_num after the SVC decoded reference picture marking process in clause F.8.2.4 must be identical regardless whether the primary coded picture or any redundant coded picture of the access unit would be decoded. + +The memory\_management\_base\_control\_operation commands of the dec\_ref\_base\_pic\_marking( ) syntax structure are processed by the decoding process before the memory\_management\_control\_operation commands of the dec\_ref\_pic\_marking( ) syntax structure are processed. + +**adaptive\_ref\_base\_pic\_marking\_mode\_flag** selects the reference base picture marking mode for the current picture or layer picture as specified in Table F-2. When adaptive\_ref\_base\_pic\_marking\_mode\_flag is not present and quality\_id is equal to 0, it shall be inferred to be equal to 0. + +**Table F-2 – Interpretation of adaptive\_ref\_base\_pic\_marking\_mode\_flag** + +| adaptive_ref_base_pic_marking_mode_flag | Reference base picture marking mode specified | +|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Sliding window reference picture marking mode: A marking mode providing a first-in, first-out mechanism for short-term reference pictures | +| 1 | Adaptive reference base picture marking mode: A reference picture marking mode providing syntax elements to specify marking of reference base pictures as "unused for reference" | + +**memory\_management\_base\_control\_operation** specifies a control operation to be applied to affect the marking of reference base pictures. The **memory\_management\_base\_control\_operation** syntax element is followed by data necessary for the operation specified by the value of **memory\_management\_base\_control\_operation**. The values and control operations associated with **memory\_management\_base\_control\_operation** are specified in Table F-3. The **memory\_management\_base\_control\_operation** syntax elements are processed by the decoding process in the order in which they appear, and the semantics constraints expressed for each **memory\_management\_base\_control\_operation** apply at the specific position in that order at which that individual **memory\_management\_base\_control\_operation** is processed. + +For interpretation of **memory\_management\_base\_control\_operation**, the terms reference picture and reference base picture are interpreted as follows: + +- If the current picture is a frame, the term reference picture refers either to a reference frame or a complementary reference field pair and the term reference base picture refers either to a reference base frame or a complementary reference base field pair. +- Otherwise (the current picture is a field), the term reference picture refers either to a reference field or a field of a reference frame and the term reference base picture refers either to a reference base field or a field of a reference base frame. + +**memory\_management\_base\_control\_operation** shall not be equal to 1 unless the specified reference base picture is marked as "used for short-term reference" (and as "reference base picture") when the **memory\_management\_base\_control\_operation** is processed by the decoding process. + +**memory\_management\_base\_control\_operation** shall not be equal to 2 unless the specified long-term picture number refers to a reference base picture that is marked as "used for long-term reference" (and as "reference base picture") when the **memory\_management\_base\_control\_operation** is processed by the decoding process. + +When the **dec\_ref\_pic\_marking()** syntax structure contains a **memory\_management\_control\_operation** equal to 5, **memory\_management\_base\_control\_operation** shall not be equal to 1 or 2. + +**Table F-3 – Memory management base control operation (memory\_management\_base\_control\_operation) values** + +| memory_management_base_control_operation | Memory Management Base Control Operation | +|-------------------------------------------------|-------------------------------------------------------------------------| +| 0 | End memory_management_base_control_operation syntax element loop | +| 1 | Mark a short-term reference base picture as "unused for reference" | +| 2 | Mark a long-term reference base picture as "unused for reference" | + +**difference\_of\_base\_pic\_nums\_minus1** is used (with **memory\_management\_base\_control\_operation** equal to 1) to mark a short-term reference base picture as "unused for reference". When the associated **memory\_management\_base\_control\_operation** is processed by the decoding process, the resulting picture number derived from **difference\_of\_base\_pic\_nums\_minus1** shall be a picture number assigned to one of the reference pictures marked as "used for short-term reference" and as "reference base picture". + +The resulting picture number is constrained as follows: + +- If **field\_pic\_flag** is equal to 0, the resulting picture number shall be one of the set of picture numbers assigned to reference frames or complementary reference field pairs marked as "reference base picture". + +NOTE 2 – When **field\_pic\_flag** is equal to 0, the resulting picture number must be a picture number assigned to a complementary reference field pair in which both fields are marked as "used for short-term reference" and "reference + +base picture" or a reference frame in which both fields are marked as "used for short-term reference" and "reference base picture". + +- Otherwise (field\_pic\_flag is equal to 1), the resulting picture number shall be one of the set of picture numbers assigned to reference fields marked as "reference base picture". + +**long\_term\_base\_pic\_num** is used (with memory\_management\_base\_control\_operation equal to 2) to mark a long-term reference base picture as "unused for reference". When the associated memory\_management\_base\_control\_operation is processed by the decoding process, long\_term\_base\_pic\_num shall be equal to a long-term picture number assigned to one of the reference pictures marked as "used for long-term reference" and as "reference base picture". + +The resulting long-term picture number is constrained as follows: + +- If field\_pic\_flag is equal to 0, the resulting long-term picture number shall be one of the set of long-term picture numbers assigned to reference frames or complementary reference field pairs marked as "reference base picture". + +NOTE 3 – When field\_pic\_flag is equal to 0, the resulting long-term picture number must be a long-term picture number assigned to a complementary reference field pair in which both fields are marked as "used for long-term reference" and "reference base picture" or a reference frame in which both fields are marked as "used for long-term reference" and "reference base picture". + +- Otherwise (field\_pic\_flag is equal to 1), the resulting long-term picture number shall be one of the set of long-term picture numbers assigned to reference fields marked as "reference base picture". + +#### F.7.4.4 Slice data semantics + +The semantics specified in clause 7.4.4 apply. + +##### F.7.4.4.1 Slice data in scalable extension semantics + +The semantics specified in clause 7.4.4 apply with the following modifications. + +**mb\_skip\_run** specifies the number of consecutive skipped macroblocks for which, when decoding an EP slice, mb\_type shall be inferred to be P\_Skip and the macroblock type is collectively referred to as a P macroblock type, or for which, when decoding an EB slice, mb\_type shall be inferred to be B\_Skip and the macroblock type is collectively referred to as a B macroblock type. The value of mb\_skip\_run shall be in the range of 0 to PicSizeInMbs – CurrMbAddr, inclusive. + +**mb\_skip\_flag** equal to 1 specifies that for the current macroblock, when decoding an EP slice, mb\_type shall be inferred to be P\_Skip and the macroblock type is collectively referred to as P macroblock type, or for which, when decoding an EB slice, mb\_type shall be inferred to be B\_Skip and the macroblock type is collectively referred to as B macroblock type. mb\_skip\_flag equal to 0 specifies that the current macroblock is not skipped. + +#### F.7.4.5 Macroblock layer semantics + +The semantics specified in clause 7.4.5 apply. Additionally, the following applies. + +The macroblock\_layer( ) syntax structure shall be considered to contain the following syntax elements with the following inferred values: + +- base\_mode\_flag is inferred to be equal to 0. +- residual\_prediction\_flag is inferred to be equal to 0. + +##### F.7.4.5.1 Macroblock prediction semantics + +The semantics specified in clause 7.4.5.1 apply. Additionally, the following applies. + +The value of mvd\_l0[ mbPartIdx ][ 0 ][ compIdx ] and mvd\_l1[ mbPartIdx ][ 0 ][ compIdx ] shall be in the range of -8192 to 8191.75, inclusive. The range of mvd\_l0[ mbPartIdx ][ 0 ][ compIdx ] and mvd\_l1[ mbPartIdx ][ 0 ][ compIdx ] is also constrained indirectly by constraints on the motion vector variable values derived from it as specified in clause F.10. + +The mb\_pred( ) syntax structure shall be considered to contain the following syntax elements with the following inferred values: + +- motion\_prediction\_flag\_l0[ mbPartIdx ] is inferred to be equal to 0 for each value of mbPartIdx in the range of 0 to NumMbPart( mb\_type ) – 1, inclusive. +- motion\_prediction\_flag\_l1[ mbPartIdx ] is inferred to be equal to 0 for each value of mbPartIdx in the range of 0 to NumMbPart( mb\_type ) – 1, inclusive. + +#### F.7.4.5.2 Sub-macroblock prediction semantics + +The semantics specified in clause 7.4.5.2 apply. Additionally, the following applies. + +The value of $\text{mvd\_10[ mbPartIdx ][ subMbPartIdx ][ compIdx ]}$ and $\text{mvd\_11[ mbPartIdx ][ subMbPartIdx ][ compIdx ]}$ shall be in the range of $-8192$ to $8191.75$ , inclusive. The range of $\text{mvd\_10[ mbPartIdx ][ subMbPartIdx ][ compIdx ]}$ and $\text{mvd\_11[ mbPartIdx ][ subMbPartIdx ][ compIdx ]}$ is also constrained indirectly by constraints on the motion vector variable values derived from it as specified in clause F.10. + +The $\text{sub\_mb\_pred( )}$ syntax structure shall be considered to contain the following syntax elements with the following inferred values: + +- $\text{motion\_prediction\_flag\_10[ mbPartIdx ]}$ is inferred to be equal to 0 for each value of $\text{mbPartIdx}$ in the range of 0 to 3, inclusive. +- $\text{motion\_prediction\_flag\_11[ mbPartIdx ]}$ is inferred to be equal to 0 for each value of $\text{mbPartIdx}$ in the range of 0 to 3, inclusive. + +#### F.7.4.5.3 Residual data semantics + +The semantics specified in clause 7.4.5.3 apply. + +##### F.7.4.5.3.1 Residual luma semantics + +The semantics specified in clause 7.4.5.3.1 apply. + +##### F.7.4.5.3.2 Residual block CAVLC semantics + +The semantics specified in clause 7.4.5.3.2 apply. + +##### F.7.4.5.3.3 Residual block CABAC semantics + +The semantics specified in clause 7.4.5.3.3 apply. + +#### F.7.4.6 Macroblock layer in scalable extension semantics + +The semantics specified in clause 7.4.5 apply. Additionally, the following modifications and extensions are specified. + +The function $\text{InCropWindow( mbAddr )}$ is specified by the following ordered steps: + +1. The variable $\text{mbX}$ is set equal to $(( \text{mbAddr} / ( 1 + \text{MbaffFrameFlag} ) ) \% \text{PicWidthInMbs})$ . +2. The variables $\text{mbY0}$ and $\text{mbY1}$ are derived as follows: + - If $\text{MbaffFrameFlag}$ is equal to 0, $\text{mbY0}$ and $\text{mbY1}$ are set equal to $(\text{mbAddr} / \text{PicWidthInMbs})$ . + - Otherwise ( $\text{MbaffFrameFlag}$ is equal to 1), $\text{mbY0}$ is set equal to $(2 * (( \text{mbAddr} / \text{PicWidthInMbs} ) / 2 ))$ and $\text{mbY1}$ is set equal to $(\text{mbY0} + 1)$ . +3. The variable $\text{scalMbH}$ is set equal to $(16 * ( 1 + \text{field\_pic\_flag } ))$ . +4. The return value of $\text{InCropWindow( mbAddr )}$ is derived as follows: + - If all of the following conditions are true, the return value of $\text{InCropWindow( mbAddr )}$ is equal to TRUE. + - $\text{no\_inter\_layer\_pred\_flag}$ is equal to 0 + - $\text{mbX}$ is greater than or equal to $(( \text{ScaledRefLayerLeftOffset} + 15 ) / 16)$ + - $\text{mbX}$ is less than $(( \text{ScaledRefLayerLeftOffset} + \text{ScaledRefLayerPicWidthInSamples}_L ) / 16)$ + - $\text{mbY0}$ is greater than or equal to $(( \text{ScaledRefLayerTopOffset} + \text{scalMbH} - 1 ) / \text{scalMbH})$ + - $\text{mbY1}$ is less than $(( \text{ScaledRefLayerTopOffset} + \text{ScaledRefLayerPicHeightInSamples}_L ) / \text{scalMbH})$ + - Otherwise, the return value of $\text{InCropWindow( mbAddr )}$ is equal to FALSE. + +**base\_mode\_flag** equal to 1 specifies that the macroblock partitioning, the macroblock (partition) prediction mode(s), and the corresponding motion data (when applicable) are inferred as specified in clause F.8. **base\_mode\_flag** equal to 0 specifies that the syntax element **mb\_type** is present in the macroblock layer in scalable extension syntax structure or that **mb\_type** shall be inferred as specified in clause F.7.4.4.1. + +When **base\_mode\_flag** is not present, **base\_mode\_flag** shall be inferred as follows: + +- If $\text{InCropWindow( CurrMbAddr )}$ is equal to 0, the value of **base\_mode\_flag** is inferred to be equal to 0. + +- Otherwise, if the syntax element `mb_skip_run` (when `entropy_coding_mode_flag` is equal to 0) or `mb_skip_flag` (when `entropy_coding_mode_flag` is equal to 1) specifies that `mb_type` is inferred to be equal to `P_Skip` or `B_Skip` as specified in clause F.7.4.4.1, the value of `base_mode_flag` is inferred to be equal to 0. +- Otherwise (`InCropWindow(CurrMbAddr)` is equal to 1 and the syntax element `mb_skip_run` (when `entropy_coding_mode_flag` is equal to 0) or `mb_skip_flag` (when `entropy_coding_mode_flag` is equal to 1) does not specify that `mb_type` is inferred to be equal to `P_Skip` or `B_Skip`), the value of `base_mode_flag` is inferred to be equal to `default_base_mode_flag`. + +When `store_ref_base_pic_flag` is equal to 1 and `quality_id` is greater than 0, `base_mode_flag` shall be equal to 1. + +**mb\_type** specifies the macroblock type. The semantics of `mb_type` depend on the slice type. + +When `mb_type` is not present, it shall be inferred as follows: + +- If `base_mode_flag` is equal to 1, `mb_type` is inferred to be equal to `Mb_Inferred`. +- Otherwise, (`base_mode_flag` is equal to 0), `mb_type` is inferred as specified in clause F.7.4.4.1. + +The macroblock type `Mb_Inferred` specifies that the macroblock partitioning and the macroblock (partition) prediction mode(s) are not known during the parsing process. In the decoding process specified in clause F.8, the macroblock type used for decoding is inferred to be equal to any of the macroblock types specified in Tables 7-11, 7-13, 7-14, or F-5. For the purpose of parsing the `slice_data_in_scalable_extension()` syntax structure including the processes specified in clause 9 and clause F.9, `Mb_Inferred` shall be considered an additional macroblock type that is different from all macroblock types specified in Tables 7-11, 7-13, 7-14, and F-5 and the following applies: + +- macroblocks with `mb_type` equal to `Mb_Inferred` are considered as coded in an Inter macroblock prediction mode and not coded in an Intra macroblock prediction mode, +- `NumMbPart(Mb_Inferred)` is considered to be equal to 1, +- `MbPartWidth(Mb_Inferred)` and `MbPartHeight(Mb_Inferred)` are considered to be equal to 16, +- `MbPartPredMode(Mb_Inferred, 0)` is considered to be not equal to `Intra_4x4`, `Intra_8x8`, `Intra_16x16`, `Pred_L0`, `Pred_L1`, `BiPred`, and `Direct`. + +Tables and semantics are specified for the various macroblock types for EI, EP, and EB slices. Each table presents the value of `mb_type`, the name of `mb_type`, the number of macroblock partitions used (given by `NumMbPart(mb_type)` function), the prediction mode of the macroblock (when it is not partitioned) or the first partition (given by the `MbPartPredMode(mb_type, 0)` function) and the prediction mode of the second partition (given by the `MbPartPredMode(mb_type, 1)` function). When a value is not applicable it is designated by "na". In the text, the value of `mb_type` may be referred to as the macroblock type and a value X of `MbPartPredMode()` may be referred to in the text by "X macroblock (partition) prediction mode" or as "X prediction macroblocks". The tables do not include the macroblock type `Mb_Inferred`. + +Table F-4 shows the allowed collective macroblock types for each `slice_type`. + +**Table F-4 – Allowed collective macroblock types for slice\_type** + +| slice_type | allowed collective macroblock types | +|-------------------|----------------------------------------------------------------------------| +| EI (slice) | I (see Table 7-11 and Table F-5) (macroblock types) | +| EP (slice) | P (see Table 7-13) and I (see Table 7-11 and Table F-5) (macroblock types) | +| EB (slice) | B (see Table 7-14) and I (see Table 7-11 and Table F-5) (macroblock types) | + +Macroblock types that may be collectively referred to as I macroblock types are specified in Tables F-5 and 7-11. `mb_type` values 0 to 25 are specified in Table 7-11. Table F-5 specifies the additional macroblock type `I_BL` that can be inferred in the decoding process specified in clause F.8 for macroblocks with `base_mode_flag` equal to 1 (`mb_type` inferred to be equal to `Mb_Inferred`). + +The macroblock types for EI slices are all I macroblock types. + +**Table F-5 – Inferred macroblock type I\_BL for EI slices** + +| mb_type | Name of mb_type | transform_size_8x8_flag | MbPartPredMode
(mb_type, 0) | Intra16x16PredMode | CodedBlockPatternChroma | CodedBlockPatternLuma | +|----------|-----------------|-------------------------|--------------------------------|--------------------|-------------------------|-----------------------| +| inferred | I_BL | na | Intra_Base | na | Equation 7-38 | Equation 7-38 | + +Intra\_Base specifies the macroblock prediction mode and specifies that the intra prediction samples are derived using constructed intra samples of the reference layer representation as specified in clause F.8. Intra\_Base is an Intra macroblock prediction mode. + +Macroblock types that may be collectively referred to as P macroblock types are specified in Table 7-13. + +The macroblock types for EP slices are specified in Tables 7-13, 7-11, and F-5. mb\_type values 0 to 4 are specified in Table 7-13 and mb\_type values 5 to 30 are specified in Table 7-11, indexed by subtracting 5 from the value of mb\_type. Table F-5 specifies the additional macroblock type I\_BL that can be inferred in the decoding process specified in clause F.8 for macroblocks with base\_mode\_flag equal to 1 (mb\_type inferred to be equal to Mb\_Inferred). + +Macroblock types that may be collectively referred to as B macroblock types are specified in Table 7-14. + +The macroblock types for EB slices are specified in Tables 7-14, 7-11, and F-5. mb\_type values 0 to 22 are specified in Table 7-14 and mb\_type values 23 to 48 are specified in Table 7-11, indexed by subtracting 23 from the value of mb\_type. Table F-5 specifies the additional macroblock type I\_BL that can be inferred in the decoding process specified in clause F.8 for macroblocks with base\_mode\_flag equal to 1 (mb\_type inferred to be equal to Mb\_Inferred). + +**coded\_block\_pattern** specifies which of the four 8x8 luma blocks and associated chroma blocks of a macroblock may contain non-zero transform coefficient values. When coded\_block\_pattern is present in the bitstream, the variables CodedBlockPatternLuma and CodedBlockPatternChroma are derived as specified by Equation 7-38. + +When scan\_idx\_end is less than scan\_idx\_start and one of the following conditions is true, the variables CodedBlockPatternLuma and CodedBlockPatternChroma are set equal to 0: + +- base\_mode\_flag is equal to 1, +- base\_mode\_flag is equal to 0, the macroblock type is not equal to P\_Skip, B\_Skip, or I\_PCM, and the macroblock prediction mode is not equal to Intra\_16x16. + +When the macroblock type is not equal to P\_Skip, B\_Skip, or I\_PCM, the following constraints shall be obeyed: + +- When scan\_idx\_end is less than scan\_idx\_start, and the macroblock prediction mode is equal to Intra\_16x16, the bitstream shall not contain data that result in derived values of CodedBlockPatternLuma and CodedBlockPatternChroma that are not equal to 0. +- When scan\_idx\_start is equal to 0, scan\_idx\_end is equal to 0, and the macroblock prediction mode is equal to Intra\_16x16, the bitstream shall not contain data that result in a derived value of CodedBlockPatternLuma that is not equal to 0. +- When scan\_idx\_start is equal to 0 and scan\_idx\_end is equal to 0, the bitstream shall not contain data that result in a derived value of CodedBlockPatternChroma that is equal to 2. + +The meaning of CodedBlockPatternLuma and CodedBlockPatternChroma is specified in clause 7.4.5. + +**residual\_prediction\_flag** equal to 1 specifies that the residual signal of the current macroblock is predicted as specified in clause F.8 using the reference layer representation specified by ref\_layer\_dq\_id. residual\_prediction\_flag equal to 0 specifies that the residual signal of the current macroblock is not predicted. + +When the syntax element residual\_prediction\_flag is not present, residual\_prediction\_flag shall be inferred as follows: + +- If all of the following conditions are true, residual\_prediction\_flag is inferred to be equal to default\_residual\_prediction\_flag: + +- slice\_type is not equal to EI, +- InCropWindow( CurrMbAddr ) is equal to 1, +- base\_mode\_flag is equal to 1 or mb\_type does not specify an I macroblock type. +- Otherwise, residual\_prediction\_flag is inferred to be equal to 0. + +All elements of the arrays LumaLevel4x4, LumaLevel8x8, Intra16x16DCLevel, Intra16x16ACLevel, CbLevel4x4, CbLevel8x8, CbIntra16x16DCLevel, CbIntra16x16ACLevel, CrLevel4x4, CrLevel8x8, CrIntra16x16DCLevel, CrIntra16x16ACLevel, ChromaDCLevel, and ChromaACLevel are set equal to 0 before parsing the residual( ) syntax structure. All elements of these arrays are also set equal to 0 when the residual( ) syntax structure is not present. + +#### F.7.4.6.1 Macroblock prediction in scalable extension semantics + +The semantics specified in clause 7.4.5.1 apply. Additionally, the following semantics are specified. + +**motion\_prediction\_flag\_10[ mbPartIdx ]** equal to 1 specifies that an alternative motion vector prediction process as specified in clause F.8 is used for deriving the list 0 motion vector of the macroblock partition mbPartIdx and that the list 0 reference index of the macroblock partition mbPartIdx is inferred as specified in clause F.8. + +When motion\_prediction\_flag\_10[ mbPartIdx ] is not present, motion\_prediction\_flag\_10[ mbPartIdx ] shall be inferred as follows: + +- If InCropWindow( CurrMbAddr ) is equal to 0, motion\_prediction\_flag\_10[ mbPartIdx ] is inferred to be equal to 0. +- Otherwise (InCropWindow( CurrMbAddr ) is equal to 1), motion\_prediction\_flag\_10[ mbPartIdx ] is inferred to be equal to default\_motion\_prediction\_flag. + +**motion\_prediction\_flag\_11[ mbPartIdx ]** has the same semantics as motion\_prediction\_flag\_10[ mbPartIdx ], with l0 and list 0 replaced by l1 and list 1, respectively. + +#### F.7.4.6.2 Sub-macroblock prediction in scalable extension semantics + +The semantics specified in clause 7.4.5.2 apply. Additionally, the following semantics are specified. + +**motion\_prediction\_flag\_10[ mbPartIdx ]** and **motion\_prediction\_flag\_11[ mbPartIdx ]** have the same semantics as specified in clause F.7.4.6.1. + +### F.8 SVC decoding process + +This clause describes the decoding process for an access unit, given syntax elements and upper-case variables from clause F.7 (with reference made to clause 7 in clause F.7) that are derived from the bitstream. + +NOTE 1 – All syntax elements and upper-case variables from clause F.7 are available for the entire current access unit. When syntax elements or upper-case variables appear with identical names in clause F.7 they are referred herein through unique identifiers. + +Outputs of this process are decoded samples of the current primary coded picture. + +The decoding process is specified such that all decoders shall produce numerically identical results. Any decoding process that produces identical results to the process described here conforms to the decoding process requirements of this Recommendation | International Standard. + +All sub-bitstreams that can be derived using the sub-bitstream extraction process as specified in clause F.8.8.1 with any combination of values for priority\_id, temporal\_id, dependency\_id, or quality\_id as the input shall result in a set of coded video sequences, with each coded video sequence conforming to one or more of the profiles specified in Annexes A and F. + +This clause specifies the decoding process for an access unit of a coded video sequence conforming to one or more of the profiles specified in clause F.10. + +Each picture referred to in this clause is a complete primary coded picture or part of a primary coded picture. Each dependency representation referred to in this clause is a dependency representation of a primary coded picture. Each layer representation referred to in this clause is a layer representation of a primary coded picture. Each slice referred to in this clause is a slice of a primary coded picture. All syntax elements and derived variables referred to in this clause are syntax elements and derived variables for primary coded pictures. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the decoding process specified in this clause and all child processes invoked from the process specified in this clause are the syntax elements and derived upper-case variables for the current access unit. + +The derivation process for the set of layer representations required for decoding as specified in clause F.8.1.1 is invoked and the output is a list *dqIdList* of integer values specifying layer representation identifiers. The variables *DQIdMin* and *DQIdMax* are set equal to the minimum and maximum values, respectively, of the entries of the list *dqIdList*, and the variable *DependencyIdMax* is set equal to (*DQIdMax* >> 4). *DependencyIdMax* shall be the same for all access units of the coded video sequence. + +At the start of the decoding process for an access unit, the following applies: + +1. Variables and functions relating to picture order count are derived by invoking the SVC decoding process for picture order count as specified in clause F.8.2.1 with *dqIdList* as the input. +2. The SVC decoding process for gaps in *frame\_num* as specified in clause F.8.2.5 is invoked with *dqIdList* as the input. +3. For each value of *currDQId* that is contained in the list *dqIdList*, the following applies: + - The decoding process for macroblock to slice group map as specified in clause 8.2.2 is invoked with the syntax elements of the NAL units with *DQId* equal to *currDQId* as the input. For this invocation of the process specified in clause 8.2.2, when *currDQId* is less than *DQIdMax*, "active picture parameter set" is substituted with "active layer picture parameter set". + - The function *NextMbAddress()* as specified in clause 8.2.2 is used for parsing the slice data syntax structures of all NAL units with *DQId* equal to *currDQId* and for inferring slice data and macroblock layer syntax elements for slices with *slice\_skip\_flag* equal to 1 and *DQId* equal to *currDQId* (see clause F.7.4.3.4). + +The collective terms *currentVars* and *refLayerVars* are initially marked as not available. + +The variable *currDQId* proceeds over the values *DQIdMin*..*DQIdMax*, and when a value of *currDQId* is present in the list *dqIdList*, the following ordered steps apply: + +1. The variable *spatResChangeFlag* is set equal to the variable *SpatialResolutionChangeFlag* of the layer representation with *DQId* equal to *currDQId*. +2. Depending on *spatResChangeFlag*, the following applies: + - If *spatResChangeFlag* is equal to 0, the base decoding process for layer representations without resolution change as specified in clause F.8.1.3.1 is invoked with *currDQId* and *currentVars* as the inputs and the output is a modified version of *currentVars*. + - Otherwise (*spatResChangeFlag* is equal to 1), the base decoding process for layer representations with resolution change as specified in clause F.8.1.3.2 is invoked with *currDQId* and *currentVars* as the inputs and the outputs are variables assigned to the collective term *refLayerVars* and a modified version of *currentVars*. +3. When *currDQId* is equal to (*DependencyIdMax* << 4) and *store\_ref\_base\_pic\_flag* for the dependency representation with *dependency\_id* equal to *DependencyIdMax* is equal to 1, the target layer representation decoding process as specified in clause F.8.1.3.3 is invoked with *currDQId*, *refLayerVars* (when *spatResChangeFlag* is equal to 1), and *currentVars* as the inputs and the outputs are assigned to the sample array *BL* and, when *ChromaArrayType* is not equal to 0, the sample arrays *BCb* and *BCr*. + +NOTE 2 – The sample arrays *BL*, *BCb*, and *BCr* represent the reference base picture for an access unit with *store\_ref\_base\_pic\_flag* equal to 1 for the dependency representation with *dependency\_id* equal to *DependencyIdMax*. + +The target layer representation decoding process as specified in clause F.8.1.3.3 is invoked with *currDQId* set equal to *DQIdMax*, *refLayerVars* (when the variable *SpatialResolutionChangeFlag* of the layer representation with *DQId* equal to *DQIdMax* is equal to 1), and *currentVars* as the inputs and the outputs are assigned to the sample array *SL* and, when *ChromaArrayType* is not equal to 0, the sample arrays *SCb* and *SCr*. + +NOTE 3 – The sample arrays *SL*, *SCb*, and *SCr* represent the decoded picture for the access unit. + +The SVC decoded reference picture marking process as specified in clause F.8.2.4 is invoked with *dqIdList* as the input. + +#### **F.8.1 SVC initialization and decoding processes** + +Clause F.8.1.1 specifies the derivation process for the set of layer representations required for decoding. + +Clause F.8.1.2 specifies the array assignment, initialization, and restructuring processes. + +Clause F.8.1.3 specifies the layer representation decoding processes. + +Clause F.8.1.4 specifies the slice decoding processes. + +Clause F.8.1.5 specifies the macroblock initialization and decoding processes. + +#### F.8.1.1 Derivation process for the set of layer representations required for decoding + +Inputs to this process are the coded slice NAL units of an access unit. + +Output of this process is a list dqIdList of integer values specifying layer representation identifiers. + +With currDQId being set equal to the maximum value of DQId for all coded slice NAL units of the current access unit and with refLayerDQId( dqId ) being a function that returns the value of MaxRefLayerDQId for the layer representation, of the current access unit, with DQId equal to dqId, the list dqIdList is derived as specified by the following pseudo-code. + +``` +numEntries = 0 +dqIdList[ numEntries++ ] = currDQId +while( refLayerDQId( currDQId ) >= 0 ) { + dqIdList[ numEntries++ ] = refLayerDQId( currDQId ) + currDQId = dqIdList[ numEntries - 1 ] +} +``` + +(F-75) + +#### F.8.1.2 Array assignment, initialization, and restructuring processes + +Clause F.8.1.2.1 specifies the array assignment and initialization process. + +Clause F.8.1.2.2 specifies the array restructuring process. + +##### F.8.1.2.1 Array assignment and initialization process + +Output of this process is a set of arrays that are assigned to the collective term currentVars. + +The following arrays are collectively referred to as currentVars: + +- A one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of a layer representation. An element of this array for a macroblock with address mbAddr is referred to as sliceIdc[ mbAddr ]. All elements of the array sliceIdc are initially marked as unspecified. +- A one-dimensional array fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of a layer representation are field macroblocks and which macroblocks are frame macroblocks. An element of this array for a macroblock with address mbAddr is referred to as fieldMbFlag[ mbAddr ]. All elements of the array fieldMbFlag are initially marked as unspecified. +- A one-dimensional array cTrafo with PicSizeInMbs elements specifying the luma and, when ChromaArrayType is equal to 3, chroma transform types for the macroblocks of a layer representation. An element of this array for a macroblock with address mbAddr is referred to as cTrafo[ mbAddr ]. Unless marked as unspecified, each element of cTrafo is equal to T\_4x4, T\_8x8, T\_16x16, or T\_PCM. All elements of the array cTrafo are initially marked as unspecified. +- A one-dimensional array baseModeFlag with PicSizeInMbs elements specifying the syntax element base\_mode\_flag for the macroblocks of a layer representation. An element of this array for a macroblock with address mbAddr is referred to as baseModeFlag[ mbAddr ]. All elements of the array baseModeFlag are initially marked as unspecified. +- A one-dimensional array mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of a layer representation. An element of this array for a macroblock with address mbAddr is referred to as mbType[ mbAddr ]. Unless marked as unspecified, each element of mbType is equal to I\_4x4, I\_8x8, I\_16x16, I\_PCM, I\_BL, or one of the Inter macroblock types specified in Tables 7-13 and 7-14. All elements of the array mbType are initially marked as unspecified. +- A (PicSizeInMbs)x4 array subMbType specifying sub-macroblock types for the macroblocks of a layer representation. An element of this array for a macroblock with address mbAddr and a macroblock partition index mbPartIdx is referred to as subMbType[ mbAddr ][ mbPartIdx ]. A one-dimensional array specifying sub-macroblock types for the macroblock partitions of a macroblock with address mbAddr is referred to as subMbType[ mbAddr ]. Unless marked as unspecified, each element of subMbType is equal to one of the sub-macroblock types specified in Tables 7-17 and 7-18. All elements of the array subMbType are initially marked as unspecified. +- A one-dimensional array mvCnt with PicSizeInMbs elements specifying the number of motion vectors for the macroblocks of a layer representation. An element of this array for a macroblock with address mbAddr is referred to as mvCnt[ mbAddr ]. All elements of the array mvCnt are initially set equal to 0. + +- A one-dimensional array $tQP_Y$ with $PicSizeInMbs$ elements specifying luma quantization parameters for the macroblocks of a layer representation. An element of this array for a macroblock with address $mbAddr$ is referred to as $tQP_Y[ mbAddr ]$ . All elements of the array $tQP_Y$ are initially set equal to 0. +- When $ChromaArrayType$ is not equal to 0, two one-dimensional arrays $tQP_{Cb}$ and $tQP_{Cr}$ with $PicSizeInMbs$ elements specifying $Cb$ and $Cr$ quantization parameters, respectively, for the macroblocks of a layer representation. An element of these arrays for a macroblock with address $mbAddr$ is referred to as $tQP_{CX}[ mbAddr ]$ with $CX$ being replaced by $Cb$ or $Cr$ . All elements of the arrays $tQP_{Cb}$ and $tQP_{Cr}$ are initially set equal to 0. +- A $(PicSizeInMbs) \times 16$ array $ipred4x4$ specifying Intra\_4x4 prediction modes for the macroblocks of a layer representation. An element of this array for a macroblock with address $mbAddr$ and a 4x4 block with index $c4x4BlkIdx$ is referred to as $ipred4x4[ mbAddr ][ c4x4BlkIdx ]$ . A one-dimensional array specifying Intra\_4x4 prediction modes for the 4x4 blocks of a macroblock with address $mbAddr$ is referred to as $ipred4x4[ mbAddr ]$ . All elements of the array $ipred4x4$ are initially marked as unspecified. +- A $(PicSizeInMbs) \times 4$ array $ipred8x8$ specifying Intra\_8x8 prediction modes for the macroblocks of a layer representation. An element of this array for a macroblock with address $mbAddr$ and a 8x8 block with index $c8x8BlkIdx$ is referred to as $ipred8x8[ mbAddr ][ c8x8BlkIdx ]$ . A one-dimensional array specifying Intra\_8x8 prediction modes for the 8x8 blocks of a macroblock with address $mbAddr$ is referred to as $ipred8x8[ mbAddr ]$ . All elements of the array $ipred8x8$ are initially marked as unspecified. +- A one-dimensional array $ipred16x16$ with $PicSizeInMbs$ elements specifying Intra\_16x16 prediction modes for the macroblocks of a layer representation. An element of this array for a macroblock with address $mbAddr$ is referred to as $ipred16x16[ mbAddr ]$ . All elements of the array $ipred16x16$ are initially marked as unspecified. +- When $ChromaArrayType$ is equal to 1 or 2, a one-dimensional array $ipredChroma$ with $PicSizeInMbs$ elements specifying intra chroma prediction modes for the macroblocks of a layer representation. An element of this array for a macroblock with address $mbAddr$ is referred to as $ipredChroma[ mbAddr ]$ . All elements of the array $ipredChroma$ are initially marked as unspecified. +- Two $(PicSizeInMbs) \times 4$ arrays $predFlagL0$ and $predFlagL1$ specifying prediction utilization flags for the macroblocks of a layer representation. An element of these arrays for a macroblock with address $mbAddr$ and a macroblock partition index $mbPartIdx$ is referred to as $predFlagLX[ mbAddr ][ mbPartIdx ]$ with $X$ being replaced by 0 or 1. A one-dimensional array specifying prediction utilization flags for the macroblock partitions of a macroblock with address $mbAddr$ is referred to as $predFlagLX[ mbAddr ]$ with $X$ being replaced by 0 or 1. All elements of the arrays $predFlagL0$ and $predFlagL1$ are initially set equal to 0. +- Two $(PicSizeInMbs) \times 4$ arrays $refIdxL0$ and $refIdxL1$ specifying reference indices for the macroblocks of a layer representation. An element of these arrays for a macroblock with address $mbAddr$ and a macroblock partition index $mbPartIdx$ is referred to as $refIdxLX[ mbAddr ][ mbPartIdx ]$ with $X$ being replaced by 0 or 1. A one-dimensional array specifying reference indices for the macroblock partitions of a macroblock with address $mbAddr$ is referred to as $refIdxLX[ mbAddr ]$ with $X$ being replaced by 0 or 1. All elements of the arrays $refIdxL0$ and $refIdxL1$ are initially set equal to $-1$ . +- Two $(PicSizeInMbs) \times 4 \times 4 \times 2$ arrays $mvL0$ and $mvL1$ specifying motion vector components for the macroblocks of a layer representation. An element of these arrays for a macroblock with address $mbAddr$ , a macroblock partition index $mbPartIdx$ , a sub-macroblock partition index $subMbPartIdx$ , and a motion vector component index $c$ is referred to as $mvLX[ mbAddr ][ mbPartIdx ][ subMbPartIdx ][ c ]$ with $X$ being replaced by 0 or 1. A one-dimensional array with 2 elements representing the motion vector for a sub-macroblock partition $subMbPartIdx$ of a macroblock partition $mbPartIdx$ inside a macroblock $mbAddr$ is referred to as $mvLX[ mbAddr ][ mbPartIdx ][ subMbPartIdx ]$ with $X$ being replaced by 0 or 1. A 4x2 array representing the motion vectors for a macroblock partition $mbPartIdx$ inside a macroblock $mbAddr$ is referred to as $mvLX[ mbAddr ][ mbPartIdx ]$ with $X$ being replaced by 0 or 1. A 4x4x2 array representing the motion vectors for a macroblock $mbAddr$ is referred to as $mvLX[ mbAddr ]$ with $X$ being replaced by 0 or 1. A motion vector component with component index $c$ for a macroblock partition $mbPartIdx$ of a macroblock $mbAddr$ that is not split into sub-macroblock partitions can also be referred to as $mvLX[ mbAddr ][ mbPartIdx ][ c ]$ with $X$ being replaced by 0 or 1, which is identical to $mvLX[ mbAddr ][ mbPartIdx ][ 0 ][ c ]$ . A motion vector for a macroblock partition $mbPartIdx$ of a macroblock $mbAddr$ that is not split into sub-macroblock partitions can also be referred to as $mvLX[ mbAddr ][ mbPartIdx ]$ with $X$ being replaced by 0 or 1, which is identical to $mvLX[ mbAddr ][ mbPartIdx ][ 0 ]$ . All elements of the arrays $mvL0$ and $mvL1$ are initially set equal to 0. +- A $(PicSizeInMbs) \times (256 + 2 * MbWidthC * MbHeightC)$ array $tCoeffLevel$ specifying transform coefficient level values for the macroblocks of a layer representation. An element of this array for a macroblock with address $mbAddr$ and a transform coefficient index $tCoeffIdx$ is referred to as $tCoeffLevel[ mbAddr ][ tCoeffIdx ]$ . A one-dimensional array specifying the transform coefficient level values for a macroblock with address $mbAddr$ is referred to as $tCoeffLevel[ mbAddr ]$ . All elements of the array $tCoeffLevel$ are initially set equal to 0. + +- A (PicSizeInMbs)x(256 + 2 \* MbWidthC \* MbHeightC) array sTCoeff specifying scaled transform coefficient values for the macroblocks of a layer representation. An element of this array for a macroblock with address mbAddr and a transform coefficient index tCoeffIdx is referred to as sTCoeff[ mbAddr ][ tCoeffIdx ]. A one-dimensional array specifying the scaled transform coefficient values for a macroblock with address mbAddr is referred to as sTCoeff[ mbAddr ]. All elements of the array sTCoeff are initially set equal to 0. +- A (PicWidthInSamplesL)x(PicHeightInSamplesL) array rL specifying residual luma sample values for a layer picture. An element of this array for a luma location ( x, y ) relative to the upper-left luma sample of the macroblock with address 0 is referred to as rL[ x, y ]. All elements of the array rL are initially set equal to 0. +- When ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays rCb and rCr specifying residual chroma sample values for a layer picture. An element of these arrays for a chroma location ( x, y ) relative to the upper-left chroma sample of the macroblock with address 0 is referred to as rCX[ x, y ] with CX being replaced by Cb or Cr. All elements of the arrays rCb and rCr are initially set equal to 0. +- A (PicWidthInSamplesL)x(PicHeightInSamplesL) array cL specifying constructed luma sample values for a layer picture. An element of this array for a luma location ( x, y ) relative to the upper-left luma sample of the macroblock with address 0 is referred to as cL[ x, y ]. All elements of the array cL are initially set equal to 0. +- When ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays cCb and cCr specifying constructed chroma sample values for a layer picture. An element of these arrays for a chroma location ( x, y ) relative to the upper-left chroma sample of the macroblock with address 0 is referred to as cCX[ x, y ] with CX being replaced by Cb or Cr. All elements of the arrays cCb and cCr are initially set equal to 0. + +#### F.8.1.2.2 Array restructuring process + +This process is only invoked when MinNoInterLayerPredFlag is equal to 0, SpatialResolutionChangeFlag is equal to 0, and any of the variables ScaledRefLayerLeftOffset, ScaledRefLayerRightOffset, ScaledRefLayerTopOffset, or ScaledRefLayerBottomOffset is not equal to 0. + +Input to this process is a set of arrays collectively referred to as currentVars. + +Output of this process is the set of arrays collectively referred to as currentVars with modifications related to the array sizes as well as the ordering of array elements. + +The variables that are assigned to the collective term currentVars are assigned to the collective term refLayerVars. + +The array assignment and initialization process as specified in clause F.8.1.2.1 is invoked and the output is the set of arrays collectively referred to as currentVars. + +The variables xOffset, yOffset, xOffsetC, and yOffsetC are derived by + +$$xOffset = ScaledRefLayerLeftOffset \quad (F-76)$$ + +$$yOffset = ScaledRefLayerTopOffset / ( 1 + field\_pic\_flag ) \quad (F-77)$$ + +$$xOffsetC = ( xOffset \gg 4 ) * MbWidthC \quad (F-78)$$ + +$$yOffsetC = ( yOffset \gg 4 ) * MbHeightC \quad (F-79)$$ + +For the macroblock address mbAddr proceeding over the values 0..(PicSizeInMbs – 1), the following ordered steps are specified: + +1. With eS set equal to (1 + MbaffFrameFlag), the variables refMbX and refMbY are derived by + +$$refMbX = ( ( mbAddr / eS ) % PicWidthInMbs ) - ( xOffset / 16 ) \quad (F-80)$$ + +$$refMbY = ( ( mbAddr / eS ) / PicWidthInMbs ) * eS + ( mbAddr % eS ) - ( yOffset / 16 ) \quad (F-81)$$ + +2. The reference layer macroblock address refMbAddr is derived as follows: + +- If any of the following conditions are true, refMbAddr is marked as not available: + - refMbX is less than 0 or refMbX is greater than or equal to RefLayerPicWidthInMbs, + - refMbY is less than 0 or refMbY is greater than or equal to RefLayerPicHeightInMbs. +- Otherwise, with bS set equal to (1 + RefLayerMbaffFrameFlag), refMbAddr is derived by + +$$refMbAddr = ( refMbY / bS ) * bS * RefLayerPicWidthInMbs + ( refMbY % bS ) + refMbX \quad (F-82)$$ + +3. When refMbAddr is available, for X being replaced by sliceIdc, fieldMbFlag, cTrafo, baseModeFlag, mbType, subMbType, mvCnt, tQPY, tQPCb (when ChromaArrayType is not equal to 0), tQPCr (when ChromaArrayType is not equal to 0), ipred4x4, ipred8x8, ipred16x16, ipredChroma (when ChromaArrayType is equal to 1 or 2), predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, mvL1, tCoeffLevel, and sTCoeff and with currArray representing the array X of the collective term currentVars and refLayerArray representing the array X of the + +collective term `refLayerVars`, the array element `currArray[ mbAddr ]`, which can be a scalar or an array, is set equal to the array element `refLayerArray[ refMbAddr ]`. + +For `X` being replaced by `rSL` and `cSL` and with `currArray` representing the array `X` of the collective term `currentVars` and `refLayerArray` representing the array `X` of the collective term `refLayerVars`, the array `currArray` is modified by + +$$\begin{aligned} \text{currArray}[ x, y ] &= \text{refLayerArray}[ x - x\text{Offset}, y - y\text{Offset} ] \\ \text{with } x &= \text{Max}( 0, x\text{Offset} ) .. \text{Min}( \text{PicWidthInSamples}_L, \text{RefLayerPicWidthInSamples}_L + x\text{Offset} ) - 1 \\ \text{and } y &= \text{Max}( 0, y\text{Offset} ) .. \text{Min}( \text{PicHeightInSamples}_L, \text{RefLayerPicHeightInSamples}_L + y\text{Offset} ) - 1 \end{aligned} \quad (\text{F-83})$$ + +When `ChromaArrayType` is not equal to 0, for `X` being replaced by `rSCb`, `rSCr`, `cSCb`, and `cSCr` and with `currArray` representing the array `X` of the collective term `currentVars` and `refLayerArray` representing the array `X` of the collective term `refLayerVars`, the array `currArray` is modified by + +$$\begin{aligned} \text{currArray}[ x, y ] &= \text{refLayerArray}[ x - x\text{OffsetC}, y - y\text{OffsetC} ] \\ \text{with } x &= \text{Max}( 0, x\text{OffsetC} ) .. \text{Min}( \text{PicWidthInSamples}_C, \text{RefLayerPicWidthInSamples}_C + x\text{OffsetC} ) - 1 \\ \text{and } y &= \text{Max}( 0, y\text{OffsetC} ) .. \text{Min}( \text{PicHeightInSamples}_C, \text{RefLayerPicHeightInSamples}_C + y\text{OffsetC} ) - 1 \end{aligned} \quad (\text{F-84})$$ + +### F.8.1.3 Layer representation decoding processes + +Clause F.8.1.3.1 specifies the base decoding process for layer representations without resolution change. + +Clause F.8.1.3.2 specifies the base decoding process for layer representations with resolution change. + +Clause F.8.1.3.3 specifies the target layer representation decoding process + +#### F.8.1.3.1 Base decoding process for layer representations without resolution change + +Inputs to this process are: + +- a variable `currDQId` specifying the current layer representation, +- a set of arrays collectively referred to as `currentVars`. + +Output of this process is the modified set of arrays collectively referred to as `currentVars`. + +This process modifies the variables assigned to `currentVars` using syntax elements and derived upper-case variables for the current layer representation with `DQId` equal to `currDQId`. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the current layer representation with `DQId` equal to `currDQId`. + +The base decoding process for layer representations without resolution change proceeds in the following ordered steps: + +1. Depending on `MinNoInterLayerPredFlag`, the following applies: + - If `MinNoInterLayerPredFlag` is equal to 1, the array assignment and initialization process as specified in clause F.8.1.2.1 is invoked and the output is a modified set of arrays collectively referred to as `currentVars`. + - Otherwise (`MinNoInterLayerPredFlag` is equal to 0), the following ordered steps are specified: + - a. When `MaxTCoeffLevelPredFlag` is equal to 0, the macroblock address `mbAddr` proceeds over the values `0..(RefLayerPicSizeInMbs – 1)`, and for each macroblock address `mbAddr`, the macroblock decoding process prior to decoding a layer representation without resolution change and `MaxTCoeffLevelPredFlag` equal to 0 as specified in clause F.8.1.5.4 is invoked with `currDQId` set equal to `MaxRefLayerDQId`, `mbAddr`, and `currentVars` as the inputs and the output is a modified version of `currentVars`. + - b. When any of the variables `ScaledRefLayerLeftOffset`, `ScaledRefLayerRightOffset`, `ScaledRefLayerTopOffset`, or `ScaledRefLayerBottomOffset` is not equal to 0, the array restructuring process as specified in clause F.8.1.2.2 is invoked with `currentVars` as the input and the output is a modified version of `currentVars`. +2. Let `setOfSlices` be the set of all slices of the current layer representation with `DQId` equal to `currDQId`. For each slice of the set `setOfSlices`, the base decoding process for slices without resolution change as specified in clause F.8.1.4.1 is invoked with `currSlice` representing the currently processed slice, `currDQId`, and `currentVars` as the inputs and the output is a modified version of `currentVars`. + +3. When `currDQId` is less than or equal to `(DependencyIdMax << 4)`, with `sliceIdc` being the array `sliceIdc` of the collective term `currentVars`, the bitstream shall not contain data that result in any value of `(sliceIdc[ mbAddr ] & 127)` with `mbAddr = 0..(PicSizeInMbs - 1)` not equal to `currDQId`. + +NOTE – This constraint and a similar constraint in clause F.8.1.3.2 specify that all layer representations with `quality_id` equal to 0 and all layer representations that are used for inter-layer prediction must be completely covered by the slices of the access unit. An additional constraint for layer representations with `dependency_id` equal to `DependencyIdMax` and `quality_id` greater than 0 is specified in clause F.8.1.5.1. + +#### F.8.1.3.2 Base decoding process for layer representations with resolution change + +Inputs to this process are: + +- a variable `currDQId` specifying the current layer representation, +- a set of arrays collectively referred to as `currentVars`. + +Outputs of this process are: + +- a set of arrays collectively referred to as `refLayerVars`, +- the modified set of arrays collectively referred to as `currentVars`. + +This process modifies the variables assigned to `currentVars` using syntax elements and derived upper-case variables for the current layer representation with `DQId` equal to `currDQId`. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the current layer representation with `DQId` equal to `currDQId`. + +The base decoding process for layer representations with resolution change proceeds in the following ordered steps: + +1. The macroblock address `mbAddr` proceeds over the values `0..(RefLayerPicSizeInMbs - 1)`, and for each macroblock address `mbAddr`, the macroblock decoding process prior to resolution change as specified in clause F.8.1.5.5 is invoked with `currDQId` set equal to `MaxRefLayerDQId`, `mbAddr`, and `currentVars` as the inputs and the output is a modified version of `currentVars`. +2. The deblocking filter process for `Intra_Base` prediction as specified in clause F.8.7.1 is invoked with `currDQId` and `currentVars` as the inputs and the output is a modified version of `currentVars`. +3. The variables that are assigned to the collective term `currentVars` are assigned to the collective term `refLayerVars`. +4. The array assignment and initialization process as specified in clause F.8.1.2.1 is invoked and the output is assigned to the collective term `currentVars`. +5. Let `setOfSlices` be the set of all slices of the current layer representation with `DQId` equal to `currDQId`. For each slice of the set `setOfSlices`, the base decoding process for slices with resolution change as specified in clause F.8.1.4.2 is invoked with `currSlice` representing the currently processed slice, `currDQId`, `refLayerVars`, and `currentVars` as the inputs and the output is a modified version of `currentVars`. +6. With `sliceIdc` being the array `sliceIdc` of the collective term `currentVars`, the bitstream shall not contain data that result in any value of `(sliceIdc[ mbAddr ] & 127)` with `mbAddr = 0..(PicSizeInMbs - 1)` not equal to `currDQId`. + +NOTE – This constraint and a similar constraint in clause F.8.1.3.1 specify that all layer representations with `quality_id` equal to 0 and all layer representation that are used for inter-layer prediction must be completely covered by the slices of the access unit. An additional constraint for layer representations with `dependency_id` equal to `DependencyIdMax` and `quality_id` greater than 0 is specified in clause F.8.1.5.1. + +#### F.8.1.3.3 Target layer representation decoding process + +Inputs to this process are: + +- a variable `currDQId` specifying the current layer representation, +- when present, a set of arrays collectively referred to as `refLayerVars`, +- a set of arrays collectively referred to as `currentVars`. + +Outputs of this process are: + +- a `(PicWidthInSamplesL)x(PicHeightInSamplesL)` array `sL` containing constructed luma sample values, +- when `ChromaArrayType` is not equal to 0, two `(PicWidthInSamplesC)x(PicHeightInSamplesC)` arrays `sCb` and `sCr` containing constructed chroma sample values. + +In this process the constructed samples of the array $s_L$ and, when $ChromaArrayType$ is not equal to 0, the arrays $s_{Cb}$ and $s_{Cr}$ are derived using the variables that are assigned to $currentVars$ . + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the current layer representation with $DQId$ equal to $currDQId$ . + +The target layer representation decoding process proceeds in the following ordered steps: + +1. The variables that are assigned to the collective term $currentVars$ are assigned to the collective term $tempVars$ , and in the following of this clause, the arrays that are collectively referred to as $tempVars$ are referred to by their names as specified in clause F.8.1.2.1. + +NOTE 1 – Any following modification of the variables assigned to the collective term $tempVars$ does not influence the variables assigned to the collective term $currentVars$ . + +2. The macroblock address $mbAddr$ proceeds over the values $0..(PicSizeInMbs - 1)$ , and for each macroblock address $mbAddr$ , the following ordered steps are specified: + +- a. Let $currSlice$ specify the slice of the layer representation with $DQId$ equal to $(( ( sliceIdc[ mbAddr ] \& 127 ) \gg 4 ) \ll 4 )$ that covers the macroblock with macroblock address $(( sliceIdc[ mbAddr ] \gg 7 ) * ( 1 + MbaflFrameFlag ) )$ . + +- b. Let $firstMbInSlice$ and $sliceType$ be the syntax elements $first\_mb\_in\_slice$ and $slice\_type$ of the slice $currSlice$ . + +- c. The variable $firstMbAddrInSlice$ is set equal to $(firstMbInSlice * ( 1 + MbaflFrameFlag ))$ . + +- d. The reference picture lists $refPicList0$ and $refPicList1$ are marked as not available. + +- e. When $(sliceType \% 5)$ is less than 2, the following applies: + +- If $mbAddr$ is greater than $firstMbAddrInSlice$ , the reference picture list $refPicList0$ is set equal to the reference picture list $refPicList0$ that was derived for the macroblock address $mbAddr$ equal to $firstMbAddrInSlice$ inside this clause and, when $(sliceType \% 5)$ is equal to 1, the reference picture list $refPicList1$ is set equal to the reference picture list $refPicList1$ that was derived for the macroblock address $mbAddr$ equal to $firstMbAddrInSlice$ inside this clause. + +- Otherwise ( $mbAddr$ is equal to $firstMbAddrInSlice$ ), the SVC decoding process for reference picture lists construction as specified in clause F.8.2.3 is invoked with $currDependencyId$ set equal to $dependency\_id$ , $useRefBasePicFlag$ set equal to $use\_ref\_base\_pic\_flag$ , and the slice $currSlice$ as the inputs and the outputs are the modified reference picture list $refPicList0$ and, when $(sliceType \% 5)$ is equal to 1, the modified reference picture list $refPicList1$ . + +NOTE 2 – The reference picture lists $refPicList0$ and $refPicList1$ are only constructed for the slices of the layer representation with $dependency\_id$ equal to $DependencyIdMax$ and $quality\_id$ equal to 0. For slices with $dependency\_id$ equal to $DependencyIdMax$ and $quality\_id$ greater than 0, the reference picture lists are inferred. + +- f. The target macroblock decoding process as specified in clause F.8.1.5.6 is invoked with $currDQId$ , $mbAddr$ , $refLayerVars$ (when present as input to this clause), $tempVars$ , $refPicList0$ (when available), and $refPicList1$ (when available) as the inputs and the output is a modified version of $tempVars$ . + +NOTE 3 – Although the target layer representation decoding process is invoked twice for pictures with $store\_ref\_base\_pic\_flag$ equal to 1, only a single motion compensation operation is needed for each macroblock. + +3. The deblocking filter process for target representations as specified in clause F.8.7.2 is invoked with $currDQId$ and $tempVars$ as the inputs and the output is a modified version of $tempVars$ . + +4. All sample values of the array $cS_L$ are copied to the array $s_L$ , which is output of this clause. + +5. When $ChromaArrayType$ is not equal to 0, all sample values of the arrays $cS_{Cb}$ and $cS_{Cr}$ are copied to the arrays $s_{Cb}$ and $s_{Cr}$ , respectively, which are output of this clause. + +#### F.8.1.4 Slice decoding processes + +Clause F.8.1.4.1 specifies the base decoding process for slices without resolution change. + +Clause F.8.1.4.2 specifies the base decoding process for slices with resolution change. + +##### F.8.1.4.1 Base decoding process for slices without resolution change + +Inputs to this process are: + +- the current slice $currSlice$ , + +- a variable `currDQId` specifying the current layer representation, +- a set of arrays collectively referred to as `currentVars`. + +Output of this process is the modified set of arrays collectively referred to as `currentVars`. + +This process modifies the variables assigned to `currentVars` using syntax elements and derived upper-case variables for the current slice `currSlice`. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the slice header of the current slice `currSlice`, the current picture parameter, which is identified by the syntax element `pic_parameter_set_id` inside the slice header of the current slice `currSlice`, and the current sequence parameter, which is identified by the syntax element `seq_parameter_set_id` inside the current picture parameter set. + +When `currDQId` is equal to 0 and `(slice_type % 5)` is equal to 1, the SVC decoding process for reference picture lists construction as specified in clause F.8.2.3 is invoked with `currDependencyId` equal to 0, `useRefBasePicFlag` equal to `use_ref_base_pic_flag`, and the current slice as input and the output is the reference picture list `refPicList1`. + +The macroblocks of the current slice `currSlice` are processed in increasing order of their macroblock addresses. For each macroblock with macroblock address `mbAddr`, the base decoding process for macroblocks in slices without resolution change as specified in clause F.8.1.5.2 is invoked with `currDQId`, `mbAddr`, `currentVars`, and, when `currDQId` is equal to 0 and `(slice_type % 5)` is equal to 1, the reference picture list `refPicList1` as the inputs and the output is a modified version of `currentVars`. + +#### F.8.1.4.2 Base decoding process for slices with resolution change + +Inputs to this process are: + +- the current slice `currSlice`, +- a variable `currDQId` specifying the current layer representation, +- a set of arrays collectively referred to as `refLayerVars`, +- a set of arrays collectively referred to as `currentVars`. + +Output of this process is the modified set of arrays collectively referred to as `currentVars`. + +This process modifies the variables assigned to `currentVars` using syntax elements and derived upper-case variables for the current slice `currSlice`. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the slice header of the current slice `currSlice`, the current picture parameter, which is identified by the syntax element `pic_parameter_set_id` inside the slice header of the current slice `currSlice`, and the current sequence parameter, which is identified by the syntax element `seq_parameter_set_id` inside the current picture parameter set. + +When `CroppingChangeFlag` is equal to 1 and `(slice_type % 5)` is less than 2, the SVC decoding process for reference picture lists construction as specified in clause F.8.2.3 is invoked with `currDependencyId` equal to `dependency_id`, `useRefBasePicFlag` equal to `use_ref_base_pic_flag`, and the current slice as the inputs and the outputs are the reference picture list `refPicList0` and, when `(slice_type % 5)` is equal to 1, the reference picture list `refPicList1`. + +The macroblocks of the current slice `currSlice` are processed in increasing order of their macroblock addresses. For each macroblock with macroblock address `mbAddr`, the base decoding process for macroblocks in slices with resolution change as specified in clause F.8.1.5.3 is invoked with `currDQId`, `mbAddr`, `refLayerVars`, `currentVars`, `refPicList0` (when `CroppingChangeFlag` is equal to 1 and `(slice_type % 5)` is less than 2), and `refPicList1` (when `CroppingChangeFlag` is equal to 1 and `(slice_type % 5)` is equal to 1) as the inputs and the output is a modified version of `currentVars`. + +#### F.8.1.5 Macroblock initialization and decoding processes + +Clause F.8.1.5.1 specifies the macroblock initialization process. + +Clause F.8.1.5.2 specifies the base decoding process for macroblocks in slices without resolution change. + +Clause F.8.1.5.3 specifies the base decoding process for macroblocks in slices with resolution change. + +Clause F.8.1.5.4 specifies the macroblock decoding process prior to decoding a layer representation without resolution change and `MaxTCoeffLevelPredFlag` equal to 0. + +Clause F.8.1.5.5 specifies the macroblock decoding process prior to resolution change. + +Clause F.8.1.5.6 specifies the target macroblock decoding process. + +#### F.8.1.5.1 Macroblock initialization process + +Inputs to this process are: + +- a set of arrays collectively referred to as `refLayerVars`, +- when `CroppingChangeFlag` is equal to 1 and `(slice_type % 5)` is less than 2, the reference picture list `refPicList0`, +- when `CroppingChangeFlag` is equal to 1 and `(slice_type % 5)` is equal to 1, the reference picture list `refPicList1`. + +Outputs of this process are: + +- a variable `sliceIdc` specifying the slice identification for the current macroblock, +- a variable `fieldMbFlag` specifying whether the current macroblock is a field or a frame macroblock, +- a variable `cTrafo` specifying the transform type for the current macroblock, +- a variable `baseModeFlag` specifying the syntax element `base_mode_flag` of the current macroblock, +- a variable `mbType` specifying the macroblock type of the current macroblock, +- a list `subMbType` with 4 elements specifying the sub-macroblock types of the current macroblock, +- a variable `mvCnt` specifying an initialization value for the motion vector count of the current macroblock, +- a variable `tQPY` specifying the luma quantization parameter for the current macroblock, +- when `ChromaArrayType` is not equal to 0, two variables `tQPCb` and `tQPCr` specifying the chroma quantization parameters for the current macroblock, +- two 2x2 arrays `refIdxILPredL0` and `refIdxILPredL1` specifying inter-layer predictors for the reference indices of the current macroblock, +- two 4x4x2 arrays `mvILPredL0` and `mvILPredL1` specifying inter-layer predictors for the motion vector components of the current macroblock. + +Inside this clause, the arrays `sliceIdc`, `fieldMbFlag`, `cTrafo`, `mbType`, `subMbType`, `tQPY`, `predFlagL0`, `predFlagL1`, `refIdxL0`, `refIdxL1`, `mvL0`, `mvL1`, `tCoeffLevel`, and `sTCoeff` that are collectively referred to as `refLayerVars` are referred to as `refLayerSliceIdc`, `refLayerFieldMbFlag`, `refLayerCTrafo`, `refLayerMbType`, `refLayerSubMbType`, `refLayerQPY`, `refLayerPredFlagL0`, `refLayerPredFlagL1`, `refLayerRefIdxL0`, `refLayerRefIdxL1`, `refLayerMvL0`, `refLayerMvL1`, `refLayerTCoeffLevel`, and `refLayerSTCoeff`, respectively. + +The variable `sliceIdc` is set equal to $((\text{first\_mb\_in\_slice} \ll 7) + \text{DQId})$ . + +The variable `baseModeFlag` is set equal to `base_mode_flag`. + +The variable `fieldMbFlag` is derived as follows: + +- If `field_pic_flag` is equal to 1, `fieldMbFlag` is set equal to 1. +- Otherwise, if `SpatialResolutionChangeFlag` is equal to 0 and `slice_skip_flag` is equal to 1, `fieldMbFlag` is set equal to `refLayerFieldMbFlag[ CurrMbAddr ]`. +- Otherwise, `fieldMbFlag` is set equal to `mb_field_decoding_flag`. + +The derivation process for macroblock type, sub-macroblock type, and inter-layer predictors for reference indices and motion vectors as specified in clause F.8.1.5.1.1 is invoked with `fieldMbFlag`, `refLayerFieldMbFlag`, `refLayerMbType`, `refLayerSubMbType`, `refLayerPredFlagL0`, `refLayerPredFlagL1`, `refLayerRefIdxL0`, `refLayerRefIdxL1`, `refLayerMvL0`, `refLayerMvL1`, `refPicList0` (when available), and `refPicList1` (when available) as the inputs and the outputs are the variable `mbType`, the list `subMbType`, the 2x2 arrays `refIdxILPredL0` and `refIdxILPredL1`, and the 4x4x2 arrays `mvILPredL0` and `mvILPredL1`. + +The derivation process for quantization parameters and transform type as specified in clause F.8.1.5.1.2 is invoked with `mbType`, `subMbType`, `refLayerMbType`, `refLayerCTrafo`, `refLayerQPY`, `refLayerTCoeffLevel`, and `refLayerSTCoeff` as the inputs and the outputs are `cTrafo`, `tQPY`, and, when `ChromaArrayType` is not equal to 0, `tQPCb` and `tQPCr`. + +The variable `mvCnt` is set equal to 0. + +When `quality_id` is greater than 0, the bitstream shall not contain data that result in $(\text{refLayerSliceIdc[ CurrMbAddr ]} \& 127)$ not equal to $(\text{DQId} - 1)$ . + +When `no_inter_layer_pred_flag` is equal to 0, `SpatialResolutionChangeFlag` is equal to 0, and `fieldMbFlag` is not equal to `refLayerFieldMbRef[ CurrMbAddr ]`, the following constraints shall be obeyed: + +- a) The bitstream shall not contain data that result in base\_mode\_flag equal to 1, or any motion\_prediction\_flag\_IX[ mbPartIdx ] with X being replaced by 0 and 1 and mbPartIdx = 0..3 equal to 1. +- b) When residual\_prediction\_flag is equal to 1, refLayerMbType[ CurrMbAddr ] is not equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL, and mbType is not equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL, the following applies: + - If tcoeff\_level\_prediction\_flag is equal to 0, the bitstream shall not contain data that result in any element refLayerSTCoeff[ CurrMbAddr ][ i ] not equal to 0 for i = 0..(255 + 2 \* MbWidthC \* MbHeightC). + - Otherwise (tcoeff\_level\_prediction\_flag is equal to 1), the bitstream shall not contain data that result in any element refLayerTCoeffLevel[ CurrMbAddr ][ i ] not equal to 0 for i = 0..(255 + 2 \* MbWidthC \* MbHeightC). + +#### F.8.1.5.1.1 Derivation process for macroblock type, sub-macroblock type, and inter-layer predictors for reference indices and motion vectors + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a one-dimensional array refLayerFieldMbFlag with RefLayerPicSizeInMbs elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array refLayerMbType with RefLayerPicSizeInMbs elements specifying the macroblock types for the macroblocks of the reference layer representation, +- a (RefLayerPicSizeInMbs)x4 array refLayerSubMbType specifying the sub-macroblock types for the macroblocks of the reference layer representation, +- two (RefLayerPicSizeInMbs)x4 arrays refLayerPredFlagL0 and refLayerPredFlagL1 specifying prediction utilization flags for the macroblocks of the reference layer representation, +- two (RefLayerPicSizeInMbs)x4 arrays refLayerRefIdxL0 and refLayerRefIdxL1 specifying reference indices for the macroblocks of the reference layer representation, +- two (RefLayerPicSizeInMbs)x4x4x2 arrays refLayerMvL0 and refLayerMvL1 specifying motion vector components for the macroblocks of the reference layer representation, +- when CroppingChangeFlag is equal to 1 and (slice\_type % 5) is less than 2, the reference picture list refPicList0, +- when CroppingChangeFlag is equal to 1 and (slice\_type % 5) is equal to 1, the reference picture list refPicList1. + +Outputs of this process are: + +- a variable mbType specifying the macroblock type of the current macroblock, +- a list subMbType with 4 elements specifying the sub-macroblock types of the current macroblock, +- two 2x2 arrays refIdxILPredL0 and refIdxILPredL1 specifying inter-layer predictors for the reference indices of the current macroblock, +- two 4x4x2 arrays mvILPredL0 and mvILPredL1 specifying inter-layer predictors for the motion vector components of the current macroblock. + +The variable mbTypeILPred, the list subMbTypeILPred, the 2x2 arrays refIdxILPredL0 and refIdxILPredL1, and the 4x4x2 arrays mvILPredL0 and mvILPredL1 are derived as follows: + +- If base\_mode\_flag is equal to 1 or any syntax element motion\_prediction\_flag\_IX[ mbPartIdx ] with X being replaced by 0 and 1 and mbPartIdx = 0..3 is equal to 1, the derivation process for inter-layer predictors for macroblock type, sub-macroblock type, reference indices, and motion vectors as specified in clause F.8.6.1 is invoked with fieldMbFlag, refLayerFieldMbFlag, refLayerMbType, refLayerSubMbType, refLayerPredFlagL0, refLayerPredFlagL1, refLayerRefIdxL0, refLayerRefIdxL1, refLayerMvL0, refLayerMvL1, refPicList0 (when available), and refPicList1 (when available) as the inputs and the outputs are the variable mbTypeILPred, the list subMbTypeILPred, the 2x2 arrays refIdxILPredL0 and refIdxILPredL1, and the 4x4x2 arrays mvILPredL0 and mvILPredL1. +- Otherwise (base\_mode\_flag is equal to 0 and all syntax elements motion\_prediction\_flag\_IX[ mbPartIdx ] with X being replaced by 0 and 1 and mbPartIdx = 0..3 are equal to 0), mbTypeILPred is marked as not available, all elements subMbTypeILPred[ mbPartIdx ] with mbPartIdx = 0..3 of the list subMbTypeILPred are marked as not available, all elements of the 2x2 arrays refIdxILPredL0 and refIdxILPredL1 are set equal to -1, and all elements of the 4x4x2 arrays mvILPredL0 and mvILPredL1 are set equal to 0. + +Depending on base\_mode\_flag, mb\_type, SpatialResolutionChangeFlag, refLayerMbType[ CurrMbAddr ], CodedBlockPatternLuma, and CodedBlockPatternChroma, the variable mbType is derived as follows: + +- If base\_mode\_flag is equal to 1, the following applies: + - If SpatialResolutionChangeFlag is equal to 0, refLayerMbType[ CurrMbAddr ] is equal to I\_PCM, CodedBlockPatternLuma is equal to 0, and CodedBlockPatternChroma is equal to 0, mbType is set equal to I\_PCM. + - Otherwise (SpatialResolutionChangeFlag is equal to 1, refLayerMbType[ CurrMbAddr ] is not equal to I\_PCM, CodedBlockPatternLuma is not equal to 0, or CodedBlockPatternChroma is not equal to 0), mbType is set equal to mbTypeILPred. +- Otherwise, if MbPartPredMode( mb\_type, 0 ) is equal to Intra\_4x4, mbType is set equal to I\_4x4. +- Otherwise, if MbPartPredMode( mb\_type, 0 ) is equal to Intra\_8x8, mbType is set equal to I\_8x8. +- Otherwise, if MbPartPredMode( mb\_type, 0 ) is equal to Intra\_16x16, mbType is set equal to I\_16x16. +- Otherwise, if mb\_type is equal to I\_PCM, mbType is set equal to I\_PCM. +- Otherwise (base\_mode\_flag is equal to 0 and mb\_type specifies a P or B macroblock type), mbType is set equal to mb\_type. + +Depending on mbType and base\_mode\_flag, the list subMbType is derived as follows: + +- If mbType is not equal to P\_8x8, P\_8x8ref0, or B\_8x8, all elements subMbType[ mbPartIdx ] with mbPartIdx = 0..3 are marked as unspecified. +- Otherwise, if base\_mode\_flag is equal to 1, each element subMbType[ mbPartIdx ] with mbPartIdx = 0..3 is set equal to subMbTypeILPred[ mbPartIdx ]. +- Otherwise (mbType is equal to P\_8x8, P\_8x8ref0, or B\_8x8 and base\_mode\_flag is equal to 0), each element subMbType[ mbPartIdx ] with mbPartIdx = 0..3 is set equal to sub\_mb\_type[ mbPartIdx ]. + +When slice\_type is equal to EP, base\_mode\_flag is equal to 1, and mbType is not equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL, the bitstream shall not contain data that result in any element refIdxILPredL0[ mbPartIdx ] with mbPartIdx = 0..3 that is less than 0. + +When residual\_prediction\_flag equal to 1 is present in the bitstream, the bitstream shall not contain data that result in mbType being equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL. + +#### F.8.1.5.1.2 Derivation process for quantization parameters and transform type + +Inputs to this process are: + +- a variable mbType specifying the macroblock type for the current macroblock, +- a list subMbType with 4 elements specifying the sub-macroblock types for the current macroblock, +- a one-dimensional array refLayerMbType specifying macroblock types for the macroblocks of the reference layer representation, +- a one-dimensional array refLayerCTrafo specifying transform types for the macroblocks of the reference layer representation, +- a one-dimensional array refLayerQPV specifying luma quantization parameters for the macroblocks of the reference layer representation, +- an (RefLayerPicSizeInMbs)x(256 + 2 \* MbWidthC \* MbHeightC) array refLayerTCoeffLevel specifying transform coefficient level values for the macroblocks of the reference layer representation, +- an (RefLayerPicSizeInMbs)x(256 + 2 \* MbWidthC \* MbHeightC) array refLayerSTCoeff specifying scaled transform coefficient values for the macroblocks of the reference layer representation. + +Outputs of this process are: + +- a variable cTrafo specifying the transform type for the current macroblock, +- a variable tQPV specifying the luma quantization parameter for the current macroblock, +- when ChromaArrayType is not equal to 0, two variables tQPCb and tQPCr specifying the chroma quantization parameters for the current macroblock. + +The variable $tQP_Y$ is derived as follows: + +- If $SpatialResolutionChangeFlag$ is equal to 0, and any of the following conditions are true, $tQP_Y$ is set equal to $refLayerQP_Y[ CurrMbAddr ]$ : + - $mbType$ is equal to $I\_PCM$ , $I\_16x16$ , $I\_8x8$ , $I\_4x4$ , or $I\_BL$ , $base\_mode\_flag$ is equal to 1, $CodedBlockPatternLuma$ is equal to 0, and $CodedBlockPatternChroma$ is equal to 0, + - $mbType$ is equal to $P\_Skip$ or $B\_Skip$ and $residual\_prediction\_flag$ is equal to 1, + - $mbType$ is not equal to $I\_PCM$ , $I\_16x16$ , $I\_8x8$ , $I\_4x4$ , $I\_BL$ , $P\_Skip$ , or $B\_Skip$ , $residual\_prediction\_flag$ is equal to 1, $CodedBlockPatternLuma$ is equal to 0, and $CodedBlockPatternChroma$ is equal to 0. +- Otherwise, $tQP_Y$ is set equal to $QP_Y$ . + +When $ChromaArrayType$ is not equal to 0, for $CX$ being replaced by $Cb$ and $Cr$ , the variable $tQP_{CX}$ is set equal to the value of $QP_{CX}$ that corresponds to a value of $tQP_Y$ for $QP_Y$ as specified in clause 8.5.8. + +The variable $predTrafoFlag$ is derived as follows: + +- If $SpatialResolutionChangeFlag$ is equal to 0 and any of the following conditions are true, $predTrafoFlag$ is set equal to 1: + - $base\_mode\_flag$ is equal to 1, $tcoeff\_level\_prediction\_flag$ is equal to 0, $refLayerMbType[ CurrMbAddr ]$ is equal to $I\_BL$ , and $CodedBlockPatternLuma$ is equal to 0, + - $base\_mode\_flag$ is equal to 1, $tcoeff\_level\_prediction\_flag$ is equal to 0, $refLayerMbType[ CurrMbAddr ]$ is equal to $I\_PCM$ , $CodedBlockPatternLuma$ is equal to 0, and $CodedBlockPatternChroma$ is equal to 0, + - $base\_mode\_flag$ is equal to 1, $tcoeff\_level\_prediction\_flag$ is equal to 0, $refLayerMbType[ CurrMbAddr ]$ is equal to $I\_8x8$ or $I\_4x4$ , and $CodedBlockPatternLuma$ is equal to 0, + - $base\_mode\_flag$ is equal to 1, $tcoeff\_level\_prediction\_flag$ is equal to 1, and $mbType$ is equal to $I\_PCM$ , $I\_16x16$ , $I\_8x8$ , or $I\_4x4$ , + - $residual\_prediction\_flag$ is equal to 1, $refLayerMbType[ CurrMbAddr ]$ is not equal to $I\_PCM$ , $I\_16x16$ , $I\_8x8$ , $I\_4x4$ , or $I\_BL$ , $mbType$ is not equal to $I\_PCM$ , $I\_16x16$ , $I\_8x8$ , $I\_4x4$ , or $I\_BL$ , and $CodedBlockPatternLuma$ is equal to 0. +- Otherwise, $predTrafoFlag$ is set equal to 0. + +The variable $cTrafo$ is derived as follows: + +- If $mbType$ is equal to $I\_PCM$ , $cTrafo$ is set equal to $T\_PCM$ . +- Otherwise, if $mbType$ is equal to $I\_16x16$ , $cTrafo$ is set equal to $T\_16x16$ . +- Otherwise, if $mbType$ is equal to $I\_8x8$ or $transform\_size\_8x8\_flag$ is equal to 1, $cTrafo$ is set equal to $T\_8x8$ . +- Otherwise, if $predTrafoFlag$ is equal to 1, $cTrafo$ is set equal to $refLayerCTrafo[ CurrMbAddr ]$ . +- Otherwise ( $predTrafoFlag$ is equal to 0, $transform\_size\_8x8\_flag$ is equal to 0, and $mbType$ is not equal to $I\_PCM$ , $I\_16x16$ , or $I\_8x8$ ), $cTrafo$ is set equal to $T\_4x4$ . + +When $cTrafo$ is equal to $T\_8x8$ , the SVC sequence parameter set that is referred to by the coded slice NAL unit (via $pic\_parameter\_set\_id$ in the slice header and $seq\_parameter\_set\_id$ in referenced the picture parameter set) shall have $transform\_8x8\_mode\_flag$ equal to 1. + +When $base\_mode\_flag$ is equal to 1, the following constraints shall be obeyed: + +- a) When $mbType$ is equal to $P\_8x8$ , $P\_8x8ref0$ , or $B8x8$ and $NumSubMbPart( subMbType[ mbPartIdx ] )$ is not equal to 1 for any $mbPartIdx = 0..3$ , the bitstream shall not contain $transform\_size\_8x8\_flag$ equal to 1. +- b) When $mbType$ is equal to $I\_PCM$ , the bitstream shall not contain data that result in $CodedBlockPatternLuma$ not equal to 0 or $CodedBlockPatternChroma$ not equal to 0. +- c) When $mbType$ is equal to $I\_16x16$ or $I\_4x4$ , the bitstream shall not contain $transform\_size\_8x8\_flag$ equal to 1. +- d) When $mbType$ is equal to $I\_8x8$ and $transform\_size\_8x8\_flag$ is equal to 0, the bitstream shall not contain data that result in $CodedBlockPatternLuma$ not equal to 0. + +The variable $constrainedCoeffFlag$ is derived as follows: + +- If `SpatialResolutionChangeFlag` is equal to 0 and any of the following conditions are true, `constrainedCoeffFlag` is set equal to 1: + - `base_mode_flag` is equal to 1, `tcoeff_level_prediction_flag` is equal to 0, and `refLayerMbType[ CurrMbAddr ]` is equal to `I_BL`, + - `residual_prediction_flag` is equal to 1, `refLayerMbType[ CurrMbAddr ]` is not equal to `I_PCM`, `I_16x16`, `I_8x8`, `I_4x4`, or `I_BL`, and `mbType` is not equal to `I_PCM`, `I_16x16`, `I_8x8`, `I_4x4`, or `I_BL`. +- Otherwise, `constrainedCoeffFlag` is set equal to 0. + +When `constrainedCoeffFlag` is equal to 1, the following constraints shall be obeyed: + +- a) When `refLayerCTrafo[ CurrMbAddr ]` is equal to `T_8x8` and `transform_size_8x8_flag` is equal 0, any of the following constraints shall be obeyed: + - i) The bitstream shall not contain data that result in `CodedBlockPatternLuma` not equal to 0. + - ii) Depending on `tcoeff_level_prediction_flag`, the following applies: + - If `tcoeff_level_prediction_flag` is equal to 0, the bitstream shall not contain data that result in any element `refLayerSTCoeff[ CurrMbAddr ][ i ]` not equal to 0 for $i = 0..(( \text{ChromaArrayType} \neq 3 ) ? 255 : 767)$ . + - Otherwise (`tcoeff_level_prediction_flag` is equal to 1), the bitstream shall not contain data that result in any element `refLayerTCoeffLevel[ CurrMbAddr ][ i ]` not equal to 0 for $i = 0..(( \text{ChromaArrayType} \neq 3 ) ? 255 : 767)$ . +- b) When `refLayerCTrafo[ CurrMbAddr ]` is equal to `T_4x4` and `transform_size_8x8_flag` equal to 1, the following applies: + - If `tcoeff_level_prediction_flag` is equal to 0, the bitstream shall not contain data that result in any element `refLayerSTCoeff[ CurrMbAddr ][ i ]` not equal to 0 for $i = 0..(( \text{ChromaArrayType} \neq 3 ) ? 255 : 767)$ . + - Otherwise (`tcoeff_level_prediction_flag` is equal to 1), the bitstream shall not contain data that result in any element `refLayerTCoeffLevel[ CurrMbAddr ][ i ]` not equal to 0 for $i = 0..(( \text{ChromaArrayType} \neq 3 ) ? 255 : 767)$ . + +#### F.8.1.5.2 Base decoding process for macroblocks in slices without resolution change + +Inputs to this process are: + +- a variable `currDQId` specifying the current layer representation, +- a variable `mbAddr` specifying the current macroblock inside the current layer representation, +- a set of arrays collectively referred to as `currentVars`, +- when `currDQId` is equal to 0 and `(slice_type % 5)` is equal to 1, the reference picture list `refPicList1`. + +Output of this process is the modified set of arrays collectively referred to as `currentVars`. + +This process modifies the variables assigned to `currentVars` using syntax elements and derived upper-case variables for the current macroblock, which is specified by its address `mbAddr` and the layer representation identifier `currDQId`. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the current macroblock, which is the macroblock with address `mbAddr` inside the layer representation with `DQId` equal to `currDQId`, the slice header of the current slice, which is the slice that contains the current macroblock, the current picture parameter, which is identified by the syntax element `pic_parameter_set_id` inside the slice header of the current slice, and the current sequence parameter, which is identified by the syntax element `seq_parameter_set_id` inside the current picture parameter set. + +Inside this clause, the arrays that are collectively referred to as `currentVars` are referred to by their names as specified in clause F.8.1.2.1. + +The base decoding process for macroblocks in slices without resolution change is specified by the following ordered steps: + +1. The variable `CurrMbAddr` is set equal to `mbAddr`. + +2. When `tcoeff_level_prediction_flag` is equal to 1, the variable `refQPY` is set equal to `tQPY[ mbAddr ]` and, when `ChromaArrayType` is not equal to 0, the variables `refQPCb` and `refQPCr` are set equal to `tQPCb[ mbAddr ]` and `tQPCr[ mbAddr ]`, respectively. +3. When `no_inter_layer_pred_flag` is equal to 0, the variable `refLayerIntraBLFlag` is derived as follows: + - If `mbType[ mbAddr ]` is equal to `I_BL`, `refLayerIntraBLFlag` is set equal to 1. + - Otherwise (`mbType[ mbAddr ]` is not equal to `I_BL`), `refLayerIntraBLFlag` is set equal to 0. +4. The variable `resPredFlag` is derived as follows: + - If `residual_prediction_flag` is equal to 1 and `mbType[ mbAddr ]` is not equal to `I_PCM`, `I_16x16`, `I_8x8`, `I_4x4`, or `I_BL`, `resPredFlag` is set equal to 1. + - Otherwise (`residual_prediction_flag` is equal to 0 or `mbType[ mbAddr ]` is equal to `I_PCM`, `I_16x16`, `I_8x8`, `I_4x4`, or `I_BL`), `resPredFlag` is set equal to 0. +5. The macroblock initialization process as specified in clause F.8.1.5.1 is invoked with `refLayerVars` set equal to `currentVars` as the input and the outputs are assigned to `sliceIdc[ mbAddr ]`, `fieldMbFlag[ mbAddr ]`, `cTrafo[ mbAddr ]`, `baseModeFlag[ mbAddr ]`, `mbType[ mbAddr ]`, `subMbType[ mbAddr ]`, `mvCnt[ mbAddr ]`, `tQPY[ mbAddr ]`, `tQPCb[ mbAddr ]` (when `ChromaArrayType` is not equal to 0), `tQPCr[ mbAddr ]` (when `ChromaArrayType` is not equal to 0), the 2x2 arrays `refIdxILPredL0` and `refIdxILPredL1`, and the 4x4x2 arrays `mvILPredL0` and `mvILPredL1`. +6. The SVC derivation process for motion vector components and reference indices as specified in clause F.8.4.1 is invoked with `sliceIdc`, `fieldMbFlag`, `mbType`, `subMbType`, `predFlagL0`, `predFlagL1`, `refIdxL0`, `refIdxL1`, `mvL0`, `mvL1`, `mvCnt`, `refIdxILPredL0`, `refIdxILPredL1`, `mvILPredL0`, `mvILPredL1`, and `refPicList1` (when available) as the inputs and the outputs are modified versions of the arrays `predFlagL0`, `predFlagL1`, `refIdxL0`, `refIdxL1`, `mvL0`, `mvL1`, and `mvCnt`. +7. Depending on `mbType[ mbAddr ]`, the following applies: + - If `mbType[ mbAddr ]` is equal to `I_PCM`, `I_16x16`, `I_8x8`, or `I_4x4`, the following ordered steps are specified: + - a. When `base_mode_flag` is equal to 0, the SVC derivation process for intra prediction modes as specified in clause F.8.3.1 is invoked with `sliceIdc`, `fieldMbFlag`, `baseModeFlag`, `mbType`, `ipred4x4`, `ipred8x8`, `ipred16x16`, and, when `ChromaArrayType` is equal to 1 or 2, `ipredChroma` as the inputs and the outputs are modified versions of `ipred4x4`, `ipred8x8`, `ipred16x16`, and, when `ChromaArrayType` is equal to 1 or 2, `ipredChroma`. + - b. When `tcoeff_level_prediction_flag` is equal to 1 and `base_mode_flag` is equal to 1, the transform coefficient level scaling process prior to transform coefficient refinement as specified in clause F.8.5.2 is invoked with `cTrafo[ mbAddr ]`, `tCoeffLevel[ mbAddr ]`, `tQPY[ mbAddr ]`, `refQPY`, and, when `ChromaArrayType` is not equal to 0, `tQPCb[ mbAddr ]`, `tQPCr[ mbAddr ]`, `refQPCb`, and `refQPCr` as the inputs and the output is a modified version of `tCoeffLevel[ mbAddr ]`. + - c. The transform coefficient scaling and refinement process as specified in clause F.8.5.1 is invoked with `refinementFlag` set equal to `base_mode_flag`, `fieldMbFlag[ mbAddr ]`, `mbType[ mbAddr ]`, `cTrafo[ mbAddr ]`, `sTCoeff[ mbAddr ]`, `tCoeffLevel[ mbAddr ]`, `tQPY[ mbAddr ]`, and, when `ChromaArrayType` is not equal to 0, `tQPCb[ mbAddr ]` and `tQPCr[ mbAddr ]` as the inputs and the outputs are modified versions of `sTCoeff[ mbAddr ]` and `tCoeffLevel[ mbAddr ]`. + - d. The sample array re-initialization process as specified in clause F.8.5.5 is invoked with `fieldMbFlag[ mbAddr ]`, `rSL`, and, when `ChromaArrayType` is not equal to 0, `rSCb` and `rSCr` as the inputs and the outputs are a modified version of `rSL` and, when `ChromaArrayType` is not equal to 0, modified versions of `rSCb` and `rSCr`. + - e. The sample array re-initialization process as specified in clause F.8.5.5 is invoked with `fieldMbFlag[ mbAddr ]`, `cSL`, and, when `ChromaArrayType` is not equal to 0, `cSCb` and `cSCr` as the inputs and the outputs are a modified version of `cSL` and, when `ChromaArrayType` is not equal to 0, modified versions of `cSCb` and `cSCr`. + - Otherwise, if `mbType[ mbAddr ]` is equal to `I_BL`, the transform coefficient scaling and refinement process as specified in clause F.8.5.1 is invoked with `refinementFlag` set equal to `refLayerIntraBLFlag`, `fieldMbFlag[ mbAddr ]`, `mbType[ mbAddr ]`, `cTrafo[ mbAddr ]`, `sTCoeff[ mbAddr ]`, `tCoeffLevel[ mbAddr ]`, `tQPY[ mbAddr ]`, and, when `ChromaArrayType` is not equal to 0, `tQPCb[ mbAddr ]` + +and $tQP_{Cr}[ mbAddr ]$ as the inputs and the outputs are modified versions of $sTCoeff[ mbAddr ]$ and $tCoeffLevel[ mbAddr ]$ . + +- Otherwise ( $mbType[ mbAddr ]$ is not equal to $I\_PCM$ , $I\_16x16$ , $I\_8x8$ , $I\_4x4$ , or $I\_BL$ ), the following ordered steps are specified: + - a. When $tcoeff\_level\_prediction\_flag$ is equal to 1 and $resPredFlag$ is equal to 1, the transform coefficient level scaling process prior to transform coefficient refinement as specified in clause F.8.5.2 is invoked with $cTrafo[ mbAddr ]$ , $tCoeffLevel[ mbAddr ]$ , $tQP_Y[ mbAddr ]$ , $refQP_Y$ , and, when $ChromaArrayType$ is not equal to 0, $tQP_{Cb}[ mbAddr ]$ , $tQP_{Cr}[ mbAddr ]$ , $refQP_{Cb}$ , and $refQP_{Cr}$ as the inputs and the output is a modified version of $tCoeffLevel[ mbAddr ]$ . + - b. The transform coefficient scaling and refinement process as specified in clause F.8.5.1 is invoked with $refinementFlag$ set equal to $resPredFlag$ , $fieldMbFlag[ mbAddr ]$ , $mbType[ mbAddr ]$ , $cTrafo[ mbAddr ]$ , $sTCoeff[ mbAddr ]$ , $tCoeffLevel[ mbAddr ]$ , $tQP_Y[ mbAddr ]$ , and, when $ChromaArrayType$ is not equal to 0, $tQP_{Cb}[ mbAddr ]$ and $tQP_{Cr}[ mbAddr ]$ as the inputs and the outputs are modified versions of $sTCoeff[ mbAddr ]$ and $tCoeffLevel[ mbAddr ]$ . + - c. When $resPredFlag$ is equal to 0, the sample array re-initialization process as specified in clause F.8.5.5 is invoked with $fieldMbFlag[ mbAddr ]$ , $rS_L$ , and, when $ChromaArrayType$ is not equal to 0, $rS_{Cb}$ and $rS_{Cr}$ as the inputs and the outputs are a modified versions of $rS_L$ and, when $ChromaArrayType$ is not equal to 0, modified versions of $rS_{Cb}$ and $rS_{Cr}$ . + - d. When $resPredFlag$ is equal to 0, the sample array re-initialization process as specified in clause F.8.5.5 is invoked with $fieldMbFlag[ mbAddr ]$ , $cS_L$ , and, when $ChromaArrayType$ is not equal to 0, $cS_{Cb}$ and $cS_{Cr}$ as the inputs and the outputs are a modified versions of $cS_L$ and, when $ChromaArrayType$ is not equal to 0, modified versions of $cS_{Cb}$ and $cS_{Cr}$ . + +8. The variable $MvCnt$ for the macroblock $mbAddr$ is set equal to $mvCnt[ mbAddr ]$ . + +#### F.8.1.5.3 Base decoding process for macroblocks in slices with resolution change + +Inputs to this process are: + +- a variable $currDQId$ specifying the current layer representation, +- a variable $mbAddr$ specifying the current macroblock inside the current layer representation, +- a set of arrays collectively referred to as $refLayerVars$ , +- a set of arrays collectively referred to as $currentVars$ , +- when $CroppingChangeFlag$ is equal to 1 and $(slice\_type \% 5)$ is less than 2, the reference picture list $refPicList0$ , +- when $CroppingChangeFlag$ is equal to 1 and $(slice\_type \% 5)$ is equal to 1, the reference picture list $refPicList1$ . + +Output of this process is the modified set of arrays collectively referred to as $currentVars$ . + +This process modifies the variables assigned to $currentVars$ using syntax elements and derived upper-case variables for the current macroblock, which is specified by its address $mbAddr$ and the layer representation identifier $currDQId$ , as well as variables assigned to $refLayerVars$ . + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the current macroblock, which is the macroblock with address $mbAddr$ inside the layer representation with $DQId$ equal to $currDQId$ , the slice header of the current slice, which is the slice that contains the current macroblock, the current picture parameter, which is identified by the syntax element $pic\_parameter\_set\_id$ inside the slice header of the current slice, and the current sequence parameter, which is identified by the syntax element $seq\_parameter\_set\_id$ inside the current picture parameter set. + +Inside this clause, the arrays that are collectively referred to as $currentVars$ are referred to by their names as specified in clause F.8.1.2.1. + +Inside this clause, the arrays $sliceIdc$ , $fieldMbFlag$ , $cTrafo$ , $mbType$ , $cS_L$ , $cS_{Cb}$ , $cS_{Cr}$ , $rS_L$ , $rS_{Cb}$ , and $rS_{Cr}$ of the collective term $refLayerVars$ are referred to as $refLayerSliceIdc$ , $refLayerFieldMbFlag$ , $refLayerCTrafo$ , $refLayerMbType$ , $refS_L$ , $refS_{Cb}$ , $refS_{Cr}$ , $refR_L$ , $refR_{Cb}$ , and $refR_{Cr}$ , respectively. + +The base decoding process for macroblocks in slices with resolution change is specified by the following ordered steps: + +1. The variable $CurrMbAddr$ is set equal to $mbAddr$ . + +2. The macroblock initialization process as specified in clause F.8.1.5.1 is invoked with `refLayerVars`, `refPicList0` (when available), and `refPicList1` (when available) as the inputs and the outputs are assigned to `sliceIdc[ mbAddr ]`, `fieldMbFlag[ mbAddr ]`, `cTrafo[ mbAddr ]`, `baseModeFlag[ mbAddr ]`, `mbType[ mbAddr ]`, `subMbType[ mbAddr ]`, `mvCnt[ mbAddr ]`, `tQPV[ mbAddr ]`, `tQPCb[ mbAddr ]` (when `ChromaArrayType` is not equal to 0), `tQPCr[ mbAddr ]` (when `ChromaArrayType` is not equal to 0), the 2x2 arrays `refIdxILPredL0` and `refIdxILPredL1`, and the 4x4x2 arrays `mvILPredL0` and `mvILPredL1`. +3. The SVC derivation process for motion vector components and reference indices as specified in clause F.8.4.1 is invoked with `sliceIdc`, `fieldMbFlag`, `mbType`, `subMbType`, `predFlagL0`, `predFlagL1`, `refIdxL0`, `refIdxL1`, `mvL0`, `mvL1`, `mvCnt`, `refIdxILPredL0`, `refIdxILPredL1`, `mvILPredL0`, and `mvILPredL1` as the inputs and the outputs are modified versions of the arrays `predFlagL0`, `predFlagL1`, `refIdxL0`, `refIdxL1`, `mvL0`, `mvL1`, and `mvCnt`. +4. The variable `intraResamplingFlag` is derived as follows: + - If any of the following conditions are true, `intraResamplingFlag` is set equal to 1: + - `mbType[ mbAddr ]` is equal to `I_BL`, + - `RestrictedSpatialResolutionChangeFlag` is equal to 0, `MbaffFrameFlag` is equal to 0, `RefLayerMbaffFrameFlag` is equal to 0, and `base_mode_flag` is equal to 1. + - Otherwise, `intraResamplingFlag` is set equal to 0. +5. When `intraResamplingFlag` is equal to 1, the resampling process for intra samples as specified in clause F.8.6.2 is invoked with `fieldMbFlag[ mbAddr ]`, `refLayerSliceIdc`, `refLayerFieldMbFlag`, `refLayerMbType`, `refSL`, `cSL`, and, when `ChromaArrayType` is not equal to 0, `refSCb`, `refSCr`, `cSCb`, and `cSCr` as the inputs and the outputs are a modified version of the array `cSL` and, when `ChromaArrayType` is not equal to 0, modified versions of the array `cSCb`, and `cSCr`. +6. Depending on `mbType[ mbAddr ]`, the following applies: + - If `mbType[ mbAddr ]` is equal to `I_PCM`, `I_16x16`, `I_8x8`, or `I_4x4`, the SVC derivation process for intra prediction modes as specified in clause F.8.3.1 is invoked with `sliceIdc`, `fieldMbFlag`, `baseModeFlag`, `mbType`, `ipred4x4`, `ipred8x8`, `ipred16x16`, and, when `ChromaArrayType` is equal to 1 or 2, `ipredChroma` as the inputs and the outputs are modified versions of `ipred4x4`, `ipred8x8`, `ipred16x16`, and, when `ChromaArrayType` is equal to 1 or 2, `ipredChroma`. + - Otherwise, if `mbType[ mbAddr ]` is not equal to `I_BL` and `residual_prediction_flag` is equal to 1, the resampling process for residual samples as specified in clause F.8.6.3 is invoked with `fieldMbFlag[ mbAddr ]`, `refLayerFieldMbFlag`, `refLayerCTrafo`, `refRL`, `rSL`, and, when `ChromaArrayType` is not equal to 0, `refRCb`, `refRCr`, `rSCb`, and `rSCr` as the inputs and the outputs are a modified version of the array `rSL` and, when `ChromaArrayType` is not equal to 0, modified versions of the array `rSCb`, and `rSCr`. + - Otherwise, the arrays of the collective term `currentVars` are not modified. +7. The transform coefficient scaling and refinement process as specified in clause F.8.5.1 is invoked with `refinementFlag` set equal to 0, `fieldMbFlag[ mbAddr ]`, `mbType[ mbAddr ]`, `cTrafo[ mbAddr ]`, `sTCoeff[ mbAddr ]`, `tCoeffLevel[ mbAddr ]`, `tQPV[ mbAddr ]`, and, when `ChromaArrayType` is not equal to 0, `tQPCb[ mbAddr ]` and `tQPCr[ mbAddr ]` as the inputs and the outputs are modified versions of `sTCoeff[ mbAddr ]` and `tCoeffLevel[ mbAddr ]`. +8. The variable `MvCnt` for the macroblock `mbAddr` is set equal to `mvCnt[ mbAddr ]`. + +#### F.8.1.5.4 Macroblock decoding process prior to decoding a layer representation without resolution change and MaxTCoeffLevelPredFlag equal to 0 + +Inputs to this process are: + +- a variable `currDQId` specifying the current layer representation, +- a variable `mbAddr` specifying the current macroblock inside the current layer representation, +- a set of arrays collectively referred to as `currentVars`. + +Output of this process is the modified set of arrays collectively referred to as `currentVars`. + +This process modifies the variables assigned to `currentVars` using syntax elements and derived upper-case variables for the current macroblock, which is specified by its address `mbAddr` and the layer representation identifier `currDQId`. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the current layer representation with DQId equal to currDQId. + +Inside this clause, the arrays that are collectively referred to as currentVars are referred to by their names as specified in clause F.8.1.2.1. + +The macroblock decoding process prior to decoding a layer representation without resolution change and MaxTCoeffLevelPredFlag equal to 0 is specified by the following ordered steps: + +1. The variable CurrMbAddr is set equal to mbAddr. +2. The variable intraPredFlag is derived as follows: + - If (sliceIdc[ mbAddr ] & 127) is equal to currDQId or MaxTCoeffLevelPredFlag is equal to 1, intraPredFlag is set equal to 1. + - Otherwise ((sliceIdc[ mbAddr ] & 127) is not equal to currDQId and MaxTCoeffLevelPredFlag is equal to 0), intraPredFlag is set equal to 0. +3. When intraPredFlag is equal to 1 and mbType[ mbAddr ] is equal to I\_PCM, I\_16x16, I\_8x8, or I\_4x4, the SVC intra sample prediction and construction process as specified in clause F.8.3.2 is invoked with sliceIdc, fieldMbFlag, baseModeFlag, mbType, ipred4x4[ mbAddr ], ipred8x8[ mbAddr ], ipred16x16[ mbAddr ], ipredChroma[ mbAddr ], cTrafo[ mbAddr ], sTCoeff[ mbAddr ], cSL, and, when ChromaArrayType is not equal to 0, cSCb and cSCr as the inputs and the outputs are a modified version of the array cSL and, when ChromaArrayType is not equal to 0, modified versions of the arrays cSCb and cSCr. + +#### F.8.1.5.5 Macroblock decoding process prior to resolution change + +Inputs to this process are: + +- a variable currDQId specifying the current layer representation, +- a variable mbAddr specifying the current macroblock inside the current layer representation, +- a set of arrays collectively referred to as currentVars. + +Output of this process is the modified set of arrays collectively referred to as currentVars. + +This process modifies the variables assigned to currentVars using syntax elements and derived upper-case variables for the current macroblock, which is specified by its address mbAddr and the layer representation identifier currDQId. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the current macroblock, which is the macroblock with address mbAddr inside the layer representation with DQId equal to currDQId, the slice header of the current slice, which is the slice that contains the current macroblock, the current picture parameter, which is identified by the syntax element pic\_parameter\_set\_id inside the slice header of the current slice, and the current sequence parameter, which is identified by the syntax element seq\_parameter\_set\_id inside the current picture parameter set. + +Inside this clause, the arrays that are collectively referred to as currentVars are referred to by their names as specified in clause F.8.1.2.1. + +The macroblock decoding process prior to resolution change is specified by the following ordered steps: + +1. The variable CurrMbAddr is set equal to mbAddr. +2. Depending on mbType[ mbAddr ], the following applies: + - If mbType[ mbAddr ] is equal to I\_PCM, I\_16x16, I\_8x8, or I\_4x4, the SVC intra sample prediction and construction process as specified in clause F.8.3.2 is invoked with sliceIdc, fieldMbFlag, baseModeFlag, mbType, ipred4x4[ mbAddr ], ipred8x8[ mbAddr ], ipred16x16[ mbAddr ], ipredChroma[ mbAddr ], cTrafo[ mbAddr ], sTCoeff[ mbAddr ], cSL, and, when ChromaArrayType is not equal to 0, cSCb and cSCr as the inputs and the outputs are a modified version of the array cSL and, when ChromaArrayType is not equal to 0, modified versions of the arrays cSCb and cSCr. + - Otherwise, if mbType[ mbAddr ] is equal to I\_BL, the following ordered steps are specified: + - a. The residual construction and accumulation process as specified in clause F.8.5.3 is invoked with accumulationFlag set equal to 0, fieldMbFlag[ mbAddr ], cTrafo[ mbAddr ], sTCoeff[ mbAddr ], rSL, and, when ChromaArrayType is not equal to 0, rSCb and rSCr as the inputs and the outputs are a + +modified version of $rS_L$ and, when $ChromaArrayType$ is not equal to 0, modified versions of $rS_{Cb}$ and $rS_{Cr}$ . + +- b. The sample array accumulation process as specified in clause F.8.5.4 is invoked with $fieldMbFlag[ mbAddr ]$ , $rS_L$ , $cS_L$ , and, when $ChromaArrayType$ is not equal to 0, $rS_{Cb}$ , $rS_{Cr}$ , $cS_{Cb}$ , and $cS_{Cr}$ as the inputs and the outputs are a modified version of $cS_L$ and, when $ChromaArrayType$ is not equal to 0, modified versions of $cS_{Cb}$ and $cS_{Cr}$ . + - c. The sample array re-initialization process as specified in clause F.8.5.5 is invoked with $fieldMbFlag[ mbAddr ]$ , $rS_L$ , and, when $ChromaArrayType$ is not equal to 0, $rS_{Cb}$ and $rS_{Cr}$ as the inputs and the outputs are a modified version of $rS_L$ and, when $ChromaArrayType$ is not equal to 0, modified versions of $rS_{Cb}$ and $rS_{Cr}$ . +- Otherwise ( $mbType[ mbAddr ]$ is not equal to $I\_PCM$ , $I\_16x16$ , $I\_8x8$ , $I\_4x4$ , or $I\_BL$ ), the following ordered steps are specified: +- a. The residual construction and accumulation process as specified in clause F.8.5.3 is invoked with $accumulationFlag$ set equal to 1, $fieldMbFlag[ mbAddr ]$ , $cTrafo[ mbAddr ]$ , $sTCoeff[ mbAddr ]$ , $rS_L$ , and, when $ChromaArrayType$ is not equal to 0, $rS_{Cb}$ and $rS_{Cr}$ as the inputs and the outputs are a modified version of $rS_L$ and, when $ChromaArrayType$ is not equal to 0, modified versions of $rS_{Cb}$ and $rS_{Cr}$ . + - b. The sample array re-initialization process as specified in clause F.8.5.5 is invoked with $fieldMbFlag[ mbAddr ]$ , $cS_L$ , and, when $ChromaArrayType$ is not equal to 0, $cS_{Cb}$ and $cS_{Cr}$ as the inputs and the outputs are a modified version of $cS_L$ and, when $ChromaArrayType$ is not equal to 0, modified versions of $cS_{Cb}$ and $cS_{Cr}$ . + +#### F.8.1.5.6 Target macroblock decoding process + +Inputs to this process are: + +- a variable $currDQId$ specifying the current layer representation, +- a variable $mbAddr$ specifying the current macroblock inside the current layer representation, +- when present, a set of arrays collectively referred to as $refLayerVars$ , +- a set of arrays collectively referred to as $currentVars$ , +- when $(slice\_type \% 5)$ is less than 2, the reference picture list $refPicList0$ , +- when $(slice\_type \% 5)$ is equal to 1, the reference picture list $refPicList1$ . + +Output of this process is the modified set of arrays collectively referred to as $currentVars$ . + +This process modifies the variables assigned to $currentVars$ using syntax elements and derived upper-case variables for the current macroblock, which is specified by its address $mbAddr$ and the layer representation identifier $currDQId$ . + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the current layer representation with $DQId$ equal to $currDQId$ . + +Inside this clause, the arrays that are collectively referred to as $currentVars$ are referred to by their names as specified in clause F.8.1.2.1. + +Inside this clause, the following applies: + +- If $refLayerVars$ is present as input to this clause, the arrays $fieldMbFlag$ and $mbType$ of the collective term $refLayerVars$ are referred to as $refLayerFieldMbFlag$ and $refLayerMbType$ , respectively. +- Otherwise ( $refLayerVars$ are not present as input to this clause), the variables $refLayerFieldMbFlag$ and $refLayerMbType$ are marked as not available. + +The target macroblock decoding process is specified by the following ordered steps: + +1. The variable $CurrMbAddr$ is set equal to $mbAddr$ . +2. When $MaxTCoeffLevelPredFlag$ is equal to 1, $(sliceIdc[ mbAddr ] \& 127)$ is not equal to $currDQId$ , and $ChromaArrayType$ is not equal to 0, the following ordered steps are specified: + - a. The variable $cQP_V$ is set equal to $tQP_V[ mbAddr ]$ , and for $CX$ being replaced by $Cb$ and $Cr$ , the variable $cQP_{Cx}$ is set equal to the value of $QP_{Cx}$ that corresponds to a value of $cQP_V$ for $QP_V$ as specified in clause 8.5.8. + +- b. The transform coefficient level scaling process prior to transform coefficient refinement as specified in clause F.8.5.2 is invoked with `cTrafo[ mbAddr ]`, `tCoeffLevel[ mbAddr ]`, `tQPY` set equal to `cQPY`, `refQPY` set equal to `tQPY[ mbAddr ]`, and, when `ChromaArrayType` is not equal to 0, `tQPCb` set equal to `cQPCb`, `tQPCr` set equal to `cQPCr`, `refQPCb` set equal to `tQPCb[ mbAddr ]`, `refQPCr` set equal to `tQPCr[ mbAddr ]` as the inputs and the output is a modified version of `tCoeffLevel[ mbAddr ]`. +- c. The variables `tQPCb[ mbAddr ]` and `tQPCr[ mbAddr ]` are set equal to `cQPCb` and `cQPCr`, respectively. +- d. The transform coefficient scaling and refinement process as specified in clause F.8.5.1 is invoked with `refinementFlag` equal to 1, `fieldMbFlag[ mbAddr ]`, `mbType[ mbAddr ]`, `cTrafo[ mbAddr ]`, `sTCoeff[ mbAddr ]`, `tCoeffLevel[ mbAddr ]`, `tQPY[ mbAddr ]`, `tQPCb[ mbAddr ]`, and `tQPCr[ mbAddr ]` as the inputs and the outputs are modified versions of `sTCoeff[ mbAddr ]` and `tCoeffLevel[ mbAddr ]`. For this invocation of the process in clause F.8.5.1, all elements of the arrays `LumaLevel4x4`, `LumaLevel8x8`, `Intra16x16DCLevel`, `Intra16x16ACLevel`, `CbLevel4x4`, `CbLevel8x8`, `CbIntra16x16DCLevel`, `CbIntra16x16ACLevel`, `CrLevel4x4`, `CrLevel8x8`, `CrIntra16x16DCLevel`, `CrIntra16x16ACLevel`, `ChromaDCLevel`, and `ChromaACLevel` are inferred to be equal to 0, `tcoeff_level_prediction_flag` is inferred to be equal to 1, and `base_mode_flag` is inferred to be equal to 1. + +NOTE – By the ordered steps specified above, the elements of the arrays `tCoeffLevel[ mbAddr ]` and `sTCoeff[ mbAddr ]` that are related to luma transform coefficients are not modified. The array elements that are related to chroma transform coefficients are only modified when the chroma quantization parameter offsets of the current layer representation with `DQId` equal to `currDQId` and the layer representation with `DQId` equal to `(sliceIdc[ mbAddr ] & 127)` are different. + +3. Depending on `mbType[ mbAddr ]`, the following applies: + +- If `mbType[ mbAddr ]` is equal to `I_PCM`, `I_16x16`, `I_8x8`, or `I_4x4`, the following ordered steps are specified: + - a. The variable `intraPredFlag` is derived as follows: + - If `(sliceIdc[ mbAddr ] & 127)` is equal to `currDQId` or `MaxTCoeffLevelPredFlag` is equal to 1, `intraPredFlag` is set equal to 1. + - Otherwise (`(sliceIdc[ mbAddr ] & 127)` is not equal to `currDQId` and `MaxTCoeffLevelPredFlag` is equal to 0), `intraPredFlag` is set equal to 0. + - b. When `intraPredFlag` is equal to 1, the SVC intra sample prediction and construction process as specified in clause F.8.3.2 is invoked with `sliceIdc`, `fieldMbFlag`, `baseModeFlag`, `mbType`, `ipred4x4[ mbAddr ]`, `ipred8x8[ mbAddr ]`, `ipred16x16[ mbAddr ]`, `ipredChroma[ mbAddr ]`, `cTrafo[ mbAddr ]`, `sTCoeff[ mbAddr ]`, `cSL`, and, when `ChromaArrayType` is not equal to 0, `cSCb` and `cSCr` as the inputs and the outputs are a modified version of the array `cSL` and, when `ChromaArrayType` is not equal to 0, modified versions of the arrays `cSCb` and `cSCr`. +- Otherwise, if `mbType[ mbAddr ]` is equal to `I_BL`, the following ordered steps are specified: + - a. The residual construction and accumulation process as specified in clause F.8.5.3 is invoked with `accumulationFlag` set equal to 0, `fieldMbFlag[ mbAddr ]`, `cTrafo[ mbAddr ]`, `sTCoeff[ mbAddr ]`, `rSL`, and, when `ChromaArrayType` is not equal to 0, `rSCb` and `rSCr` as the inputs and the outputs are a modified version of `rSL` and, when `ChromaArrayType` is not equal to 0, modified versions of `rSCb` and `rSCr`. + - b. The sample array accumulation process as specified in clause F.8.5.4 is invoked with `fieldMbFlag[ mbAddr ]`, `rSL`, `cSL`, and, when `ChromaArrayType` is not equal to 0, `rSCb`, `rSCr`, `cSCb`, and `cSCr` as the inputs and the outputs are a modified version of `cSL` and, when `ChromaArrayType` is not equal to 0, modified versions of `cSCb` and `cSCr`. +- Otherwise (`mbType[ mbAddr ]` is not equal to `I_PCM`, `I_16x16`, `I_8x8`, `I_4x4`, or `I_BL`), the following ordered steps are specified: + - a. The SVC decoding process for Inter prediction samples as specified in clause F.8.4.2 is invoked with `targetQId` set equal to `(currDQId & 15)`, `fieldMbFlag[ mbAddr ]`, `sliceIdc[ mbAddr ]`, `mbType[ mbAddr ]`, `subMbType[ mbAddr ]`, `predFlagL0[ mbAddr ]`, `predFlagL1[ mbAddr ]`, `refIdxL0[ mbAddr ]`, `refIdxL1[ mbAddr ]`, `mvL0[ mbAddr ]`, `mvL1[ mbAddr ]`, `refLayerFieldMbFlag` (when available), `refLayerMbType` (when available), `refPicList0`, `refPicList1` (when available), `cSL`, `rSL`, and, when `ChromaArrayType` is not equal to 0, `cSCb`, `cSCr`, `rSCb`, and `rSCr` as the inputs and the outputs are modified version of `cSL` and `rSL`, and, when `ChromaArrayType` is not equal to 0, modified versions of `cSCb`, `cSCr`, `rSCb`, and `rSCr`. + - b. The residual construction and accumulation process as specified in clause F.8.5.3 is invoked with `accumulationFlag` set equal to 1, `fieldMbFlag[ mbAddr ]`, `cTrafo[ mbAddr ]`, `sTCoeff[ mbAddr ]`, `rSL`, + +and, when `ChromaArrayType` is not equal to 0, `rSCb` and `rSCr` as the inputs and the outputs are a modified version of `rSL` and, when `ChromaArrayType` is not equal to 0, modified versions of `rSCb` and `rSCr`. + +- c. The sample array accumulation process as specified in clause F.8.5.4 is invoked with `fieldMbFlag[ mbAddr ]`, `rSL`, `cSL`, and, when `ChromaArrayType` is not equal to 0, `rSCb`, `rSCr`, `cSCb`, and `cSCr` as the inputs and the outputs are a modified version of `cSL` and, when `ChromaArrayType` is not equal to 0, modified versions of `cSCb` and `cSCr`. + +#### F.8.2 SVC reference picture lists construction and decoded reference picture marking process + +The SVC decoding process for picture order count is specified in clause F.8.2.1. + +The SVC decoding process for picture numbers is specified in clause F.8.2.2. + +The SVC decoding process for reference picture lists construction is specified in clause F.8.2.3. + +The SVC decoded reference picture marking process is specified in clause F.8.2.4. + +The SVC decoding process for gaps in `frame_num` is specified in clause F.8.2.5. + +The decoding process for picture order counts is independently applied for different values of `dependency_id`. Syntax elements that are related to picture order count for a particular value of `dependency_id` do not influence the derivation of picture order counts for other values of `dependency_id`. + +The reference picture marking is independently applied for different values of `dependency_id`. Syntax elements that are related to reference picture marking for a particular value of `dependency_id` do not influence the reference picture marking for other values of `dependency_id`. + +The decoding process for gaps in `frame_num` is independently applied for different values of `dependency_id`. + +Reference picture lists for different dependency representations are constructed independently. Syntax elements that are related to reference picture lists construction for a particular value of `dependency_id` do not influence the reference picture lists construction for other values of `dependency_id`. Reference picture lists for a particular value of `dependency_id` are constructed based on the reference picture marking for this particular value of `dependency_id`. The reference picture marking for a particular value of `dependency_id` does not influence the reference picture lists construction for a different value of `dependency_id`. + +Only the elements of the reference picture lists for `dependency_id` equal to `DependencyIdMax` represent decoded pictures that are associated with decoded samples. Only the reference picture lists for `dependency_id` equal to `DependencyIdMax` are used for the derivation of inter prediction samples as specified in clause F.8.4.2. The elements of the reference picture lists for dependency representation with `dependency_id` less than `DependencyIdMax` represent layer pictures, which are not associated with decoded samples. The elements of the reference picture lists for `dependency_id` equal to 0 are associated with the arrays `fieldMbFlag`, `mbType`, `subMbType`, `predFlagL0`, `predFlagL1`, `refIdxL0`, `refIdxL1`, `mvL0`, and `mvL1` as specified in clause F.8.1.2.1 that were derived when decoding the layer representation with `dependency_id` equal to 0 and `quality_id` equal to 0 for the corresponding access unit. These arrays are used for the derivation of motion vectors and reference indices for layer representation with `dependency_id` equal to 0 and `quality_id` equal to 0 as specified in clause F.8.4.1.2. The elements of the reference picture lists for all dependency representations with `dependency_id` greater than 0 are associated with the variables `ScaledRefLayerLeftOffset`, `ScaledRefLayerRightOffset`, `ScaledRefLayerTopOffset`, and `ScaledRefLayerBottomOffset`. These variables are used for deriving inter-layer motion vector predictions as specified in clause F.8.6.1.2. + +NOTE – For each access unit, decoded samples only need to be stored for the dependency representation with `dependency_id` equal to `DependencyIdMax` and motion data arrays only need to be stored for the dependency representation with `dependency_id` equal to 0. + +The SVC decoding processes for picture order count, reference picture lists construction, reference picture marking, and gaps in `frame_num` are specified using processes specified in clause 8. The following modifications to the processes specified in this clause and the processes of clause 8 that are invoked from these processes apply with `currDependencyId` representing the value of `dependency_id` for the dependency representation for which the processes are invoked: + +- a) All syntax elements and derived upper-case variables that are referred to in this process or in a child process invoked from this process are syntax elements and upper-case variables for the dependency representation with `dependency_id` equal to `currDependencyId`. +- b) When `dependency_id` is less than `DependencyIdMax`, the following applies: + - A frame, field, top field, bottom field, picture, and decoded picture is interpreted as layer frame, layer field, layer top field, layer bottom field, layer picture, and decoded layer picture, respectively, for the dependency + +representation with `dependency_id` equal to `currDependencyId`. A decoded layer picture is not associated with the sample arrays $S_L$ , $S_{Cb}$ , or $S_{Cr}$ . + +- An IDR picture is interpreted as layer picture with `IdrPicFlag` equal to 1 for the dependency representation with `dependency_id` equal to `currDependencyId`. +- A reference frame, reference field, and reference picture is interpreted as layer frame, layer field, and layer picture with `nal_ref_idc` greater than 0 for the dependency representation with `dependency_id` equal to `currDependencyId`. +- A non-reference frame, non-reference field, and non-reference picture is interpreted as layer frame, layer field, and layer picture with `nal_ref_idc` equal to 0 for the dependency representation with `dependency_id` equal to `currDependencyId`. +- A complementary non-reference field pair is interpreted as complementary non-reference layer field pair for the dependency representation with `dependency_id` equal to `currDependencyId`. A complementary non-reference layer field pair for a particular value of `dependency_id` is a pair of two layer fields for the particular value of `dependency_id` with the following properties: (i) the layer fields are in consecutive access units containing a dependency representation with the particular value of `dependency_id`, (ii) the dependency representations with the particular value of `dependency_id` in these access units have `nal_ref_idc` equal to 0, `field_pic_flag` equal to 1, different values of `bottom_field_flag`, and they share the same value of the `frame_num` syntax element, (iii) the first layer field is not already a paired layer field. +- A complementary reference field pair is interpreted as complementary reference layer field pair for the dependency representation with `dependency_id` equal to `currDependencyId`. A complementary reference layer field pair for a particular value of `dependency_id` is a pair of two layer fields for the particular value of `dependency_id` with the following properties: (i) the layer fields are in consecutive access units containing a dependency representation with the particular value of `dependency_id`, (ii) the dependency representations with the particular value of `dependency_id` in these access units have `nal_ref_idc` greater than 0, `field_pic_flag` equal to 1, and the same value of `frame_num`, (iii) the dependency representation with the particular value of `dependency_id` of the second access unit in decoding order has `IdrPicFlag` equal to 0 and does not contain a `memory_management_control_operation` syntax element equal to 5. +- A complementary field pair is interpreted as complementary layer field pair for the dependency representation with `dependency_id` equal to `currDependencyId`. A complementary layer field pair is a collective term for a complementary reference layer field pair and a complementary non-reference layer field pair. +- A non-paired non-reference field is interpreted as layer field with `nal_ref_idc` equal to 0 for the dependency representation with `dependency_id` equal to `currDependencyId` that is not part of a complementary non-reference layer field pair. +- A non-paired reference field is interpreted as layer field with `nal_ref_idc` greater than 0 for the dependency representation with `dependency_id` equal to `currDependencyId` that is not part of a complementary reference layer field pair. +- A non-paired field is interpreted as layer field for the dependency representation with `dependency_id` equal to `currDependencyId` that is not part of a complementary layer field pair. +- A reference base frame is interpreted as reference layer base frame for the dependency representation with `dependency_id` equal to `currDependencyId`. A reference layer base frame for a particular value of `dependency_id` represents a second representation of a layer frame for dependency representations with `nal_ref_idc` greater than 0, `store_ref_base_pic_flag` equal to 1, and `field_pic_flag` equal to 0. +- A reference base field is interpreted as reference layer base field for the dependency representation with `dependency_id` equal to `currDependencyId`. A reference layer base field for a particular value of `dependency_id` represents a second representation of a layer field for dependency representations with `nal_ref_idc` greater than 0, `store_ref_base_pic_flag` equal to 1, and `field_pic_flag` equal to 1. +- A reference base picture is interpreted as reference layer base picture for the dependency representation with `dependency_id` equal to `currDependencyId`. A reference layer base picture is a collective term for a reference layer base field or a reference layer base frame. A reference layer base picture is not associated with the sample arrays $B_L$ , $B_{Cb}$ , or $B_{Cr}$ . +- A complementary reference base field pair is interpreted as complementary reference layer base field pair for the dependency representation with `dependency_id` equal to `currDependencyId`. A complementary reference layer base field pair for a particular value of `dependency_id` is a pair of two reference layer base fields for the particular value of `dependency_id` with the following properties: (i) the reference layer base + +fields are in consecutive access units containing a dependency representation with the particular value of `dependency_id`, (ii) the dependency representations with the particular value of `dependency_id` in these access units have `nal_ref_idc` greater than 0, `store_ref_base_pic_flag` equal to 1, `field_pic_flag` equal to 1 and the same value of `frame_num`, (iii) the dependency representation with the particular value of `dependency_id` of the second of these access units in decoding order has `IdrPicFlag` equal to 0 and does not contain a `memory_management_control_operation` syntax element equal to 5. + +- A non-paired reference base field is interpreted as reference layer base field for the dependency representation with `dependency_id` equal to `currDependencyId` that is not part of a complementary reference layer base field pair. + +#### F.8.2.1 SVC decoding process for picture order count + +Input to this process is a list `dqIdList` of integer values specifying layer representation identifiers. + +Outputs of this process are the variables `TopFieldOrderCnt` (if applicable) and `BottomFieldOrderCnt` (if applicable) for all dependency representations of the set `depRepSet` specified in the following. + +Let `depRepSet` be the set of dependency representations for which (`dependency_id` << 4) is contained in the list `dqIdList`. + +For all dependency representations of the set `depRepSet`, the variables `TopFieldOrderCnt` (if applicable) and `BottomFieldOrderCnt` (if applicable) are derived by invoking the decoding process for picture order count as specified in clause 8.2.1. For these invocations of the process specified in clause 8.2.1, the modifications a) and b) specified in clause F.8.2 apply with `currDependencyId` being equal to `dependency_id` of the corresponding dependency representation. + +For all dependency representations of the set `depRepSet` for an access unit, either `TopFieldOrderCnt` or `BottomFieldOrderCnt` or both are derived. When both are derived in two or more dependency representations of an access unit, their difference shall be the same in these dependency representations of the access unit. + +The values of `TopFieldOrderCnt` and `BottomFieldOrderCnt` are restricted as specified in the following ordered steps: + +1. The set `depRepSet` for an access unit is the set `depRepSet` that has been derived in the process specified in this clause for the corresponding access unit. +2. For each access unit, the one-dimensional array `picOrderCnt` is derived as follows: + - If `TopFieldOrderCnt` is derived for all dependency representations of the set `depRepSet` for an access unit, for each dependency representation of the set `depRepSet` for this access unit, the variable `picOrderCnt[ dId ]` is set equal to `TopFieldOrderCnt` with `dId` being the value of `dependency_id` for the dependency representation. + - Otherwise (`TopFieldOrderCnt` is not derived for all dependency representations of the set `depRepSet` for an access unit), for each dependency representation of the set `depRepSet` for this access unit, the variable `picOrderCnt[ dId ]` is set equal to `BottomFieldOrderCnt` with `dId` being the value of `dependency_id` for the dependency representation. +3. Let `au0` and `au1` be any pair of access units in the bitstream with `au1` being later in decoding order than `au0`. +4. Let the flag `idrConditionFlag` be derived for each dependency representation of the set `depRepSet` for an access unit as follows: + - If the dependency representation in the access unit has `IdrPicFlag` equal to 1 or a `memory_management_control_operation` syntax element equal to 5, `idrConditionFlag` is set equal to 1. + - Otherwise (the dependency representation in the access unit has `IdrPicFlag` equal to 0 and does not have a `memory_management_control_operation` syntax element equal to 5), `idrConditionFlag` is set equal to 0. +5. Let the set `dIdSet0` be the set of all `dependency_id` values of the set `depRepSet` for `au0`. +6. Let the set `dIdSet1` be the set of all `dependency_id` values of the set `depRepSet` for `au1` for which `idrConditionFlag` is not equal to 1 in any access unit in decoding order between the access unit that follows `au0` and the access unit `au1`, inclusive. +7. For all values of `dId` that are present in both sets `dIdSet0` and `dIdSet1`, the differences between the value `picOrderCnt[ dId ]` in `au0` and the value `picOrderCnt[ dId ]` in `au1` shall be the same. + +#### F.8.2.2 SVC decoding process for picture numbers + +This process is invoked when the SVC decoding process for reference picture lists construction specified in clause F.8.2.3, the SVC reference picture marking process for a dependency representation specified in clause F.8.2.4.1, or the SVC decoding process for gaps in `frame_num` specified in clause F.8.2.5 is invoked. + +Inputs to this process are: + +- a variable `currDependencyId` specifying a dependency representation, +- a variable `refPicListConstructionFlag` specifying whether this process is invoked for reference picture lists construction, +- when `refPicListConstructionFlag` is equal to 1, a variable `useRefBasePicFlag` specifying whether reference base pictures are considered for reference picture lists construction. + +From here to the end of this clause, the modifications a) and b) specified in clause F.8.2 apply. + +The variables `FrameNum`, `FrameNumWrap`, and `PicNum` are assigned to all short-term reference pictures and the variables `LongTermFrameIdx` and `LongTermPicNum` are assigned to all long-term reference pictures by invoking the decoding process for picture numbers as specified in clause 8.2.4.1. + +NOTE 1 – For this invocation of the process specified in clause 8.2.4.1, the pictures marked as "reference base pictures" and the pictures not marked as "reference base pictures" are taken into account. + +For the following specification of this clause, reference frames, complementary reference field pairs, and non-paired reference fields with at least one field marked as "used for reference" are referred to as reference entries. When only one field of a reference entry is marked as "used for reference", the reference entry is considered to have the same marking(s) and the same assigned variables as its field marked as "used for reference". When a reference entry is marked as "not available for reference list construction" in the following process, both of its fields are also marked as "not available for reference list construction". + +When `refPicListConstructionFlag` is equal to 1, the following applies: + +- If `useRefBasePicFlag` is equal to 0, all reference entries that are marked as "reference base picture" are marked as "not available for reference list construction". + +NOTE 2 – When `useRefBasePicFlag` is equal to 0, only reference entries that are not marked as "reference base picture" are considered as present for the purpose of reference picture lists construction. + +- Otherwise (`useRefBasePicFlag` is equal to 1), all reference entries for which one of the following conditions is true are marked as "not available for reference list construction": + - the reference entry is not marked as "reference base picture", the reference entry is marked as "used for short-term reference", and there exists a reference entry with the same value of `FrameNum` that is marked as "reference base picture" and "used for short-term reference", + - the reference entry is not marked as "reference base picture", the reference entry is marked as "used for long-term reference", and there exists a reference entry with the same value of `LongTermFrameIdx` that is marked as "reference base picture" and "used for long-term reference". + +NOTE 3 – When `useRefBasePicFlag` is equal to 1 and either two short-term reference entries have the same value of `FrameNum` or two long-term reference entries have the same value of `LongTermFrameIdx` (one of these reference entries is marked as "reference base picture" and the other reference entry is not marked as "reference base picture"), only the reference entry marked as "reference base picture" is considered as present for the purpose of reference picture lists construction. + +### F.8.2.3 SVC decoding process for reference picture lists construction + +This process is invoked at the beginning of the decoding process for each P, EP, B, or EB slice. + +Inputs to this process are: + +- a variable `currDependencyId`, +- a variable `useRefBasePicFlag`, +- the current slice `currSlice`. + +Outputs of this process are: + +- a reference picture list `refPicList0`, +- for B and EB slices, a reference picture list `refPicList1`. + +After applying the process described in this clause, the output reference picture lists `refPicList0` and `refPicList1` (when applicable) shall not contain any pictures for which the syntax element `temporal_id` is greater than the syntax element `temporal_id` of the current picture. + +From here to the end of this clause, the modifications a) and b) specified in clause F.8.2 apply. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the slice header of the current slice `currSlice`, the current picture parameter, which is identified by the syntax element `pic_parameter_set_id` inside the slice header of the current slice `currSlice`, and the current sequence parameter, which is identified by the syntax element `seq_parameter_set_id` inside the current picture parameter set. + +A variable `biPred` is derived as follows: + +- If the current slice `currSlice` is a B or EB slice, `biPred` is set equal to 1. +- Otherwise, `biPred` is set equal to 0. + +Decoded reference pictures are marked as "used for short-term reference" or "used for long-term reference" as specified by the bitstream and specified in clause F.8.2.4. Short-term reference pictures are identified by the value of `frame_num` that is decoded in the slice header(s) with `dependency_id` equal to `currDependencyId`. Long-term reference pictures are identified by a long-term frame index as specified by the bitstream and specified in clause F.8.2.4. + +Clause F.8.2.2 is invoked with `currDependencyId`, `refPicListConstructionFlag` equal to 1, and `useRefBasePicFlag` as inputs to specify the following: + +- the assignment of variables `FrameNum`, `FrameNumWrap`, and `PicNum` to each of the short-term reference pictures, +- the assignment of variables `LongTermPicNum` to each of the long-term reference pictures, +- the marking of reference pictures that are not used for reference picture lists construction as "not available for reference list construction" (depending on the value of `useRefBasePicFlag`). + +NOTE 1 – The marking of reference pictures as "not available for reference list construction" is removed after construction of the reference picture lists. + +Reference pictures are addressed through reference indices as specified in clause 8.4.2.1 with the modification e) specified in clause F.8.4.2. A reference index is an index into a reference picture list. When `biPred` is equal to 0, a single reference picture list `refPicList0` is constructed. When decoding a B or EB slice (`biPred` is equal to 1), a second independent reference picture list `refPicList1` is constructed in addition to `refPicList0`. + +At the beginning of the decoding process for each slice, reference picture list `refPicList0`, and for `biPred` equal to 1 `refPicList1`, are derived as specified in the following ordered steps: + +1. Initial reference picture lists `RefPicList0` and, for `biPred` equal to 1, `RefPicList1` are derived by invoking the initialization process for reference picture lists as specified in clause 8.2.4.2. During the initialization process in clause 8.2.4.2 all reference frames, complementary reference field pairs, and non-paired reference fields that have been marked as "not available for reference list construction" by the invocation of clause F.8.2.2 are considered as not present. +2. When `ref_pic_list_modification_flag_l0` is equal to 1 or, when decoding a B or EB slice (`biPred` is equal to 1), `ref_pic_list_modification_flag_l1` is equal to 1, the initial reference picture list `RefPicList0` and for `biPred` equal to 1 `RefPicList1` are modified by invoking the modification process for reference picture lists as specified in clause 8.2.4.3. During the modification process in clause 8.2.4.3 all reference frames, complementary reference field pairs, and non-paired reference fields that have been marked as "not available for reference list construction" by the invocation of clause F.8.2.2 are considered as not present. +3. `RefPicList0` is assigned to `refPicList0`. +4. When `biPred` is equal to 1, `RefPicList1` is assigned to `refPicList1`. + +NOTE 2 – By the invocation of the process in clause F.8.2.2 some reference frames, complementary reference field pairs, and non-paired reference fields might have been marked as "not available for reference list construction". Since, these pictures are not considered in the construction process for reference picture lists, the reference picture lists `refPicList0` and, for `biPred` equal to 1, `refPicList1` are dependent on the value of the input parameter `useRefBasePicFlag`. + +The number of entries in the modified reference picture list `refPicList0` is `num_ref_idx_l0_active_minus1 + 1`, and for `biPred` equal to 1 the number of entries in the modified reference picture list `refPicList1` is `num_ref_idx_l1_active_minus1 + 1`. A reference picture may appear at more than one index in the modified reference picture lists `refPicList0` or `refPicList1`. + +For all reference frames, complementary reference field pairs, and non-paired reference fields that have been marked as "not available for reference list construction" during the invocation of clause F.8.2.2, this marking is removed. + +#### F.8.2.4 SVC decoded reference picture marking process + +Input to this process is a list `dqIdList` of integer values specifying layer representation identifiers. + +Let `depRepSet` be the set of dependency representations for which all of the following conditions are true: + +- the list `dqIdList` contains the value (`dependency_id << 4`), +- `nal_ref_idc` is greater than 0. + +For each dependency representation of the set `depRepSet`, the SVC reference picture marking process for a dependency representation as specified in clause F.8.2.4.1 is invoked. For these invocations of the process specified in clause F.8.2.4.1, the modifications a) and b) specified in clause F.8.2 apply with `currDependencyId` being equal to `dependency_id` for the corresponding dependency representation. + +#### F.8.2.4.1 SVC reference picture marking process for a dependency representation + +Input to this process is a variable `currDependencyId`. + +Output of this process is a modified reference picture marking for dependency representations with `dependency_id` equal to `currDependencyId`. + +This process is invoked for a decoded picture when `nal_ref_idc` is not equal to 0 for the dependency representation with `dependency_id` being equal to `currDependencyId`. + +All syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are syntax elements and derived upper-case variables for the dependency representation with `dependency_id` equal to `currDependencyId`. + +A decoded picture with `nal_ref_idc` not equal to 0, referred to as a reference picture, is marked as "used for short-term reference" or "used for long-term reference". When `store_ref_base_pic_flag` is equal to 1, a second representation of the decoded picture also referred to as reference base picture is marked as "used for short-term reference" or "used for long-term reference" and additionally marked as "reference base picture". Pictures that are marked as "reference base picture" are only used as references for inter prediction of following pictures with `use_ref_base_pic_flag` equal to 1. These pictures are not used for inter prediction of pictures with `use_ref_base_pic_flag` equal to 0, and these pictures do not represent an output of the decoding process. + +For a decoded reference frame, both of its fields are marked the same as the frame. For a complementary reference field pair, the pair is marked the same as both of its fields. A picture that is marked as "used for short-term reference" is identified by its `FrameNum` and, when it is a field, by its parity, and, when it is a reference base picture, by the marking "reference base picture". A picture that is marked as "used for long-term reference" is identified by its `LongTermFrameIdx` and, when it is a field, by its parity, and, when it is a reference base picture, by the marking "reference base picture". + +While decoded pictures are represented by the sample arrays `SL` and, when `ChromaArrayType` is not equal to 0, `SCB` and `SCR`, reference base pictures are represented by the sample arrays `BL` and, when `ChromaArrayType` is not equal to 0, `BCB` and `BCR`. When reference base pictures are referenced in the inter prediction process via clause 8.4.2.1, the samples arrays `BL`, `BCB`, and `BCR` are referred to as `SL`, `SCB`, and `SCR`, respectively. The sample arrays `SL`, `SCB`, `SCR`, `BL`, `BCB`, and `BCR` that referenced in the inter prediction process via clause 8.4.2.1 are constructed as specified in clause F.8. Reference base pictures are associated with the same descriptive information such as the variables `FrameNum`, `FrameNumWrap`, `PicNum`, `LongTermFrameIdx`, and `LongTermPicNum` as decoded pictures. + +Frames or complementary field pairs marked as "used for short-term reference" or as "used for long-term reference" can be used as a reference for inter prediction when decoding a frame until the frame, the complementary field pair, or one of its constituent fields is marked as "unused for reference". A field marked as "used for short-term reference" or as "used for long-term reference" can be used as a reference for inter prediction when decoding a field until marked as "unused for reference". + +A picture can be marked as "unused for reference" by the sliding window reference picture marking process, a first-in, first-out mechanism specified in clause F.8.2.4.2, or by the adaptive memory control reference picture marking process, a customised adaptive marking operation specified in clauses F.8.2.4.3 and F.8.2.4.4. + +A short-term reference picture is identified for use in the decoding process by its variables `FrameNum` and `FrameNumWrap` and its picture number `PicNum`, and, when it is a reference base picture, by the marking as "reference base picture". A long-term reference picture is identified for use in the decoding process by its variable `LongTermFrameIdx`, its long-term picture number `LongTermPicNum`, and, when it is a reference base picture, by the marking as "reference base picture". + +When the current picture is not an IDR picture, the variables `FrameNum`, `FrameNumWrap`, `PicNum`, `LongTermFrameIdx`, and `LongTermPicNum` are assigned to the reference pictures by invoking the SVC decoding process for picture numbers as specified in clause F.8.2.2 with `currDependencyId` and `refPicListConstructionFlag` set equal to 0 as the inputs. + +Decoded reference picture marking proceeds in the following ordered steps: + +1. All slices of the current access unit are decoded. +2. Depending on the current picture, the following applies: + +- If the current picture is an IDR picture, the following ordered steps are specified: + - a. All reference pictures are marked as "unused for reference". + - b. Depending on long\_term\_reference\_flag, the following applies: + - If long\_term\_reference\_flag is equal to 0, the following ordered steps are specified: + - i. The IDR picture is marked as "used for short-term reference" and MaxLongTermFrameIdx is set equal to "no long-term frame indices". + - ii. When store\_ref\_base\_pic\_flag is equal to 1, the reference base picture of the IDR picture is marked as "used for short-term reference" and as "reference base picture". + - Otherwise (long\_term\_reference\_flag is equal to 1), the following ordered steps are specified: + - i. The IDR picture is marked as "used for long-term reference", the LongTermFrameIdx for the IDR picture is set equal to 0, and MaxLongTermFrameIdx is set equal to 0. + - ii. When store\_ref\_base\_pic\_flag is equal to 1, the reference base picture of the IDR picture is marked as "used for long-term reference" and as "reference base picture", and the LongTermFrameIdx for the reference base picture of the IDR picture is set equal to 0. +- Otherwise (the current picture is not an IDR picture), the following ordered steps are specified: + - a. When adaptive\_ref\_base\_pic\_marking\_mode\_flag is equal to 1, the SVC adaptive memory control reference base picture marking process as specified in clause F.8.2.4.3 is invoked. + +NOTE 1 – By this invocation of the process specified in clause F.8.2.4.3, pictures that are marked as "used for reference" and "reference base picture" can be marked as "unused for reference". + +With currTId being the value of temporal\_id for the current access unit, the bitstream shall not contain data that result in the marking of pictures with temporal\_id less currTId as "unused for reference" during this invocation of the process in clause F.8.2.4.3. + +- b. Depending on adaptive\_ref\_pic\_marking\_mode\_flag, the following applies: + - If adaptive\_ref\_pic\_marking\_mode\_flag is equal to 1, the SVC adaptive memory control decoded reference picture marking process as specified in clause F.8.2.4.4 is invoked. + +With currTId being the value of temporal\_id for the current access unit, the bitstream shall not contain data that result in the marking of pictures with temporal\_id less currTId as "unused for reference" during this invocation of the process in clause F.8.2.4.4. + +- Otherwise (adaptive\_ref\_pic\_marking\_mode\_flag is equal to 0), the SVC sliding window decoded reference picture marking process as specified in clause F.8.2.4.2 is invoked with refBasePicFlag equal to 0 as the input. +- c. When the current picture was not marked as "used for long-term reference" by a memory\_management\_control\_operation command equal to 6, the current picture is marked as "used for short-term reference" and, when the current picture is the second field (in decoding order) of a complementary reference field pair and the first field is marked as "used for short-term reference", the complementary field pair is also marked as "used for short-term reference". +- d. When store\_ref\_base\_pic\_flag is equal to 1 and the reference base picture for the current picture was not marked as "used for long-term reference" by a memory\_management\_control\_operation command equal to 6, the following ordered steps are specified: + - i. When adaptive\_ref\_base\_pic\_marking\_mode\_flag is equal to 0, the following ordered steps are specified: + - (1) The SVC decoding process for picture numbers as specified in clause F.8.2.2 is invoked with currDependencyId and refPicListConstructionFlag set equal to 0 as the inputs. + - (2) The SVC sliding window decoded reference picture marking process as specified in clause F.8.2.4.2 is invoked with refBasePicFlag equal to 1 as the input. + - ii. The reference base picture of the current picture is marked as "used for short-term reference" and as "reference base picture" and, when the reference base picture of the current picture is the second reference base field (in decoding order) of a complementary reference base field pair and the first reference base field is marked as "used for short-term reference" (and "reference base + +picture"), the complementary reference base field pair is also marked as "used for short-term reference" and "reference base picture". + +NOTE 2 – When both the decoded picture and the reference base picture for an access unit (including the current access unit) are marked as "used for reference", either both pictures are marked as "used for short-term reference" or both pictures are marked as "used for long-term reference" after the completion of the process specified in this clause. And in the latter case, the same value of LongTermFrameIdx is assigned to both pictures. + +It is a requirement of bitstream conformance that, after marking the current decoded reference picture and, when store\_ref\_base\_pic\_flag is equal to 1, the current reference base picture, the total number of frames with at least one field marked as "used for reference", plus the number of complementary field pairs with at least one field marked as "used for reference", plus the number of non-paired fields marked as "used for reference" shall not be greater than Max( max\_num\_ref\_frames, 1 ). + +NOTE 3 – For this constraint, the pictures marked as "reference base pictures" and the pictures not marked as "reference base picture" are taken into account. + +#### F.8.2.4.2 SVC sliding window decoded reference picture marking process + +Input to this process is a variable refBasePicFlag. + +The variable newFrameBufferFlag is derived as follows: + +- If one of the following conditions is true, newFrameBufferFlag is set equal to 0: + - refBasePicFlag is equal to 0, the current picture is a coded field that is the second field in decoding order of a complementary reference field pair, and the first field of the complementary reference field pair has been marked as "used for short-term reference", + - refBasePicFlag is equal to 1, the current reference base picture is a reference base field that is the second field in decoding order of a complementary reference base field pair, and the first field has been marked as "used for short-term reference" (and "reference base picture"). +- Otherwise, newFrameBufferFlag is set equal to 1. + +When newFrameBufferFlag is equal to 1, the following ordered steps are specified: + +1. Let numShortTerm be the total number of reference frames, complementary reference field pairs, and non-paired reference fields for which at least one field is marked as "used for short-term reference". Let numLongTerm be the total number of reference frames, complementary reference field pairs, and non-paired reference fields for which at least one field is marked as "used for long-term reference". + +NOTE 1 – For this derivation of numShortTerm and numLongTerm, the pictures marked as "reference base pictures" and the pictures not marked as "reference base picture" are taken into account. + +2. When numShortTerm + numLongTerm is equal to Max( max\_num\_ref\_frames, 1 ), the following ordered steps are specified: + - a. The condition that numShortTerm is greater than 0 shall be fulfilled. + - b. Let frameNumWrapDecPic be the smallest value of FrameNumWrap that is assigned to reference frames, complementary reference field pairs, and non-paired reference fields that are marked as "used for short-term reference" and not marked as "reference base pictures". When there doesn't exist any reference frame, complementary reference field pair, or non-paired reference field that is marked as "used for short-term reference" and not marked as "reference base picture", frameNumWrapDecPic is set equal to MaxFrameNum. + - c. Let frameNumWrapBasePic be the smallest value of FrameNumWrap that is assigned to reference frames, complementary reference field pairs, and non-paired reference fields that are marked as "used for short-term reference" and marked as "reference base pictures". When there doesn't exist any reference frame, complementary reference field pair, or non-paired reference field that is marked as "used for short-term reference" and marked as "reference base picture", frameNumWrapBasePic is set equal to MaxFrameNum. + +NOTE 2 – The value of MaxFrameNum is greater than all values of FrameNumWrap that are assigned to reference frames, complementary reference field pairs, and non-paired reference fields marked as "used for short-term reference". + - d. The short-term reference frame, complementary reference field pair, or non-paired reference field picX is derived as follows: + - If frameNumWrapDecPic is less than frameNumWrapBasePic, picX is the short-term reference frame, complementary reference field pair, or non-paired reference field that has the value of FrameNumWrap equal to frameNumWrapDecPic (and is not marked as "reference base picture"). + +- Otherwise (frameNumWrapDecPic is greater than or equal to frameNumWrapBasePic), picX is the short-term reference frame, complementary reference field pair, or non-paired reference field that has the value of FrameNumWrap equal to frameNumWrapBasePic and is marked as "reference base picture". +- e. It is a requirement of bitstream conformance that the short-term reference frame, complementary reference field pair, or non-paired reference field picX shall not be the current picture or the complementary field pair that contains the current picture. + - NOTE 3 – When refBasePicFlag is equal to 1, the current picture has been marked as "used for short-term reference" in the same invocation of the process specified in clause F.8.2.4.1. +- f. The short-term reference frame, complementary reference field pair, or non-paired reference field picX is marked as "unused for reference". When it is a frame or a complementary field pair, both of its fields are also marked as "unused for reference". + +#### F.8.2.4.3 SVC adaptive memory control reference base picture marking process + +This process is invoked when adaptive\_ref\_base\_pic\_marking\_mode\_flag is equal to 1. + +The memory\_management\_base\_control\_operation commands with values of 1 and 2 are processed in the order they occur in the dec\_ref\_base\_pic\_marking() syntax structure after the current picture has been decoded. The memory\_management\_base\_control\_operation command with value of 0 specifies the end of the memory\_management\_base\_control\_operation commands. + +Memory management control base operations are applied to pictures as follows: + +- If field\_pic\_flag is equal to 0, memory\_management\_base\_control\_operation commands are applied to the reference base frames or complementary reference base field pairs specified. +- Otherwise (field\_pic\_flag is equal to 1), memory\_management\_base\_control\_operation commands are applied to the individual reference base fields specified. + +For each memory\_management\_base\_control\_operation command with a value not equal to 0, the following applies: + +- If memory\_management\_base\_control\_operation is equal to 1, the marking process of a short-term reference picture as "unused for reference" as specified in clause 8.2.5.4.1, is invoked with substituting difference\_of\_pic\_nums\_minus1 with difference\_of\_base\_pic\_nums\_minus1. For this invocation of the process specified in clause 8.2.5.4.1, all pictures that are not marked as "reference base picture" are considered as not present. + +NOTE 1 – Short-term reference pictures that are not marked as "reference base pictures" cannot be marked as "unused for reference" by a memory\_management\_base\_control\_operation equal to 1. + +- Otherwise, if memory\_management\_base\_control\_operation is equal to 2, the marking process of a long-term reference picture as "unused for reference" as specified in clause 8.2.5.4.2 is invoked with substituting long\_term\_pic\_num with long\_term\_base\_pic\_num. For this invocation of the process specified in clause 8.2.5.4.2, all pictures that are not marked as "reference base picture" are considered as not present. + +NOTE 2 – Long-term reference pictures that are not marked as "reference base pictures" cannot be marked as "unused for reference" by a memory\_management\_base\_control\_operation equal to 2. + +#### F.8.2.4.4 SVC adaptive memory control decoded reference picture marking process + +This process is invoked when adaptive\_ref\_pic\_marking\_mode\_flag is equal to 1. + +The memory\_management\_control\_operation commands with values of 1 to 6 are processed in the order they occur in the dec\_ref\_pic\_marking() syntax structure after the current picture has been decoded. The memory\_management\_control\_operation command with value of 0 specifies the end of the memory\_management\_control\_operation commands. + +Memory management control operations are applied to pictures as follows: + +- If field\_pic\_flag is equal to 0, memory\_management\_control\_operation commands are applied to the frames or complementary reference field pairs specified. +- Otherwise (field\_pic\_flag is equal to 1), memory\_management\_control\_operation commands are applied to the individual reference fields specified. + +For each memory\_management\_control\_operation command with a value not equal to 0, the following applies: + +- If memory\_management\_control\_operation is equal to 1, the marking process of a short-term reference picture as "unused for reference" as specified in clause 8.2.5.4.1 is invoked. For this invocation of the process specified in clause 8.2.5.4.1, all pictures that are marked as "reference base picture" are considered as not present. + +NOTE 1 – Short-term reference pictures that are marked as "reference base pictures" cannot be marked as "unused for reference" by a memory\_management\_control\_operation equal to 1. + +- Otherwise, if memory\_management\_control\_operation is equal to 2, the marking process of a long-term reference picture as "unused for reference" as specified in clause 8.2.5.4.2 is invoked. For this invocation of the process specified in clause 8.2.5.4.2, all pictures that are marked as "reference base picture" are considered as not present. + +NOTE 2 – Long-term reference pictures that are marked as "reference base pictures" cannot be marked as "unused for reference" by a memory\_management\_control\_operation equal to 2. + +- Otherwise, if memory\_management\_control\_operation is equal to 3, the following ordered steps are specified: + +1. The assignment process of a LongTermFrameIdx to a short-term reference picture as specified in clause 8.2.5.4.3 is invoked. For this invocation of the process specified in clause 8.2.5.4.3, all pictures that are marked as "reference base picture" are considered as not present. The variable picNumX is set equal to the value picNumX that is derived during the invocation of the process specified in clause 8.2.5.4.3. +2. Depending on whether there exists a picture that is marked as "reference base picture" and "used for short-term reference" and has a value of PicNum equal to picNumX, the following applies: + +- If there exists a picture that is marked as "reference base picture" and "used for short-term reference" and has a value of PicNum equal to picNumX, the assignment process of a LongTermFrameIdx to a short-term reference picture as specified in clause 8.2.5.4.3 is invoked again. For this second invocation of the process specified in clause 8.2.5.4.3, all pictures that are not marked as "reference base picture" are considered as not present. + +NOTE 3 – When the marking of a decoded picture (not marked as "reference base picture") is changed from "used for short-term reference" to "used for long-term reference" and there exists a reference base picture (marked as "reference base picture") that has the same value of PicNum as the decoded picture (before the marking is modified), the marking of this reference base picture is also changed from "used for short-term reference" to "used for long-term reference" and the same value of LongTermFrameIdx is assigned to both the decoded picture and the reference base picture. + +- Otherwise, if LongTermFrameIdx equal to long\_term\_frame\_idx is assigned to a long-term reference frame marked as "reference base picture" or a long-term complementary reference field pair marked as "reference base picture", that frame or complementary field pair and both of its fields are marked as "unused for reference". +- Otherwise, if LongTermFrameIdx equal to long\_term\_frame\_idx is assigned to a long-term reference field marked as "reference base picture", and the associated decoded picture (not marked as "reference base picture") is not part of a complementary field pair that includes the picture specified by picNumX (before invoking the process specified in clause 8.2.5.4.3) and not marked as "reference base picture", that field is marked as "unused for reference". + +NOTE 4 – When a particular value of LongTermFrameIdx is assigned to a reference base picture (marked as "reference base picture") and a decoded picture (not marked as "reference base picture"), the reference base picture is either associated with the same access unit as the decoded picture or with an access unit that represents a field that is part of a complementary field pair that includes the decoded picture. + +- Otherwise, the reference picture marking is not modified. + +- Otherwise, if memory\_management\_control\_operation is equal to 4, the decoding process for MaxLongTermFrameIdx as specified in clause 8.2.5.4.4 is invoked. + +NOTE 5 – For this invocation of the process specified in clause 8.2.5.4.4, the pictures marked as "reference base pictures" and the pictures not marked as "reference base picture" are taken into account. + +- Otherwise, if memory\_management\_control\_operation is equal to 5, the marking process of all reference pictures as "unused for reference" and setting MaxLongTermFrameIdx to "no long-term frame indices" as specified in clause 8.2.5.4.5 is invoked. + +NOTE 6 – For this invocation of the process specified in clause 8.2.5.4.5, the pictures marked as "reference base pictures" and the pictures not marked as "reference base picture" are taken into account. + +- Otherwise (memory\_management\_control\_operation is equal to 6), the following ordered steps are specified: + +1. The process for assigning a long-term frame index to the current picture as specified in clause 8.2.5.4.6 is invoked. For this invocation of the process specified in clause 8.2.5.4.6, all pictures that are marked as "reference base picture" are considered as not present. +2. Depending on store\_ref\_base\_pic\_flag, the following applies: + - If store\_ref\_base\_pic\_flag is equal to 1, the reference base picture of the current picture is marked as "reference base picture" and the process for assigning a long-term frame index to the current picture as specified in clause 8.2.5.4.6 is invoked again. For this second invocation of the process specified in + +clause 8.2.5.4.6, the reference base picture is considered as the current picture and all pictures that are not marked as "reference base picture" are considered as not present. When the reference base picture of the current picture is the second reference base field (in decoding order) of a complementary reference base field pair, the complementary reference base field pair is also marked as "reference base picture". + +NOTE 7 – When the current decoded picture is marked as "used for long-term reference" and `store_ref_base_pic_flag` is equal to 1, the current reference base picture is also marked as "used for long-term reference" and the same value of `LongTermFrameIdx` is assigned to both the current decoded picture and the current reference base picture. The current reference base picture is additionally marked as "reference base picture". + +- Otherwise, if `LongTermFrameIdx` equal to `long_term_frame_idx` is assigned to a long-term reference frame marked as "reference base picture" or a long-term complementary reference field pair marked as "reference base picture", that frame or complementary field pair and both of its fields are marked as "unused for reference". +- Otherwise, if `LongTermFrameIdx` equal to `long_term_frame_idx` is assigned to a long-term reference field marked as "reference base picture", and the associated decoded picture (not marked as "reference base picture") is not part of a complementary field pair that includes the current picture, that field is marked as "unused for reference". + +NOTE 8 – When a particular value of `LongTermFrameIdx` is assigned to a reference base picture (marked as "reference base picture") and a decoded picture (not marked as "reference base picture"), the reference base picture is either associated with the same access unit as the decoded picture or with an access unit that represents a field that is part of a complementary field pair that includes the decoded picture. + +- Otherwise, the reference picture marking is not modified. + +3. It is a requirement of bitstream conformance that, after marking the current decoded reference picture and, when `store_ref_base_pic_flag` is equal to 1, the current reference base picture, the total number of frames with at least one field marked as "used for reference", plus the number of complementary field pairs with at least one field marked as "used for reference", plus the number of non-paired fields marked as "used for reference" shall not be greater than $\text{Max}(\text{max\_num\_ref\_frames}, 1)$ . + +NOTE 9 – For this constraint, the pictures marked as "reference base pictures" and the pictures not marked as "reference base picture" are taken into account. + +NOTE 10 – Under some circumstances, the above statement may impose a constraint on the order in which a `memory_management_control_operation` syntax element equal to 6 can appear in the decoded reference picture marking syntax relative to a `memory_management_control_operation` syntax element equal to 1, 2, 3, or 4, or it may impose a constraint on the value of `adaptive_ref_base_pic_marking_mode_flag`. + +#### F.8.2.5 SVC decoding process for gaps in frame\_num + +Input to this process is a list `dqIdList` of integer values specifying layer representation identifiers. + +Let `depRepSet` be the set of dependency representations for which (`dependency_id` << 4) is contained in the list `dqIdList`. + +For all dependency representations of the set `depRepSet`, the following applies: + +- The variable `currDependencyId` is set equal to the value of `dependency_id` for the currently considered dependency representation of the set `depRepSet`. +- The syntax elements `gaps_in_frame_num_value_allowed_flag` and `frame_num` and the derived upper-case variables `PrevRefFrameNum` and `MaxFrameNum` are the syntax elements and derived upper-case variables for the considered dependency representation. +- When `gaps_in_frame_num_value_allowed_flag` is equal to 0, the bitstream shall not contain data that result in `frame_num` not being equal to `PrevRefFrameNum` or $(\text{PrevRefFrameNum} + 1) \% \text{MaxFrameNum}$ . + +NOTE – When `gaps_in_frame_num_value_allowed_flag` is equal to 0 and `frame_num` is not equal to `PrevRefFrameNum` and is not equal to $(\text{PrevRefFrameNum} + 1) \% \text{MaxFrameNum}$ , the decoding process should infer an unintentional loss of pictures. + +- When `frame_num` is not equal to `PrevRefFrameNum` and is not equal to $(\text{PrevRefFrameNum} + 1) \% \text{MaxFrameNum}$ , the decoding process for gaps in `frame_num` as specified in clause 8.2.5.2 is invoked. For this invocation of the process specified in clause 8.2.5.2, the modifications a) and b) specified in clause F.8.2 apply, the invocation of the decoding process for picture numbers specified in clause 8.2.4.1 is substituted with the invocation of the SVC decoding process for picture numbers specified in clause F.8.2.2 with `currDependencyId` and `refPicListConstructionFlag` equal to 0 as the inputs, and the invocation of sliding window picture marking process specified in clause 8.2.5.3 is substituted with the invocation of the SVC sliding window decoded reference picture marking process specified in clause F.8.2.4.2 with `refBasePicFlag` equal to 0 as the input. + +### F.8.3 SVC intra decoding processes + +Clause F.8.3.1 specifies the SVC derivation process for intra prediction modes. + +Clause F.8.3.2 specifies the SVC intra sample prediction and construction process. + +#### F.8.3.1 SVC derivation process for intra prediction modes + +This process is only invoked when base\_mode\_flag is equal to 0 and mbType[ CurrMbAddr ] specified as input to this process is equal to I\_PCM, I\_16x16, I\_8x8, or I\_4x4. + +Inputs to this process are: + +- a one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of the current layer representation, +- a list fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a list baseModeFlag with PicSizeInMbs elements specifying the syntax element base\_mode\_flag for the macroblocks of the current layer representation, +- a list mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current layer representation, +- a (PicSizeInMbs)x16 array ipred4x4 specifying Intra\_4x4 prediction modes for macroblocks of the current layer representation, +- a (PicSizeInMbs)x4 array ipred8x8 specifying Intra\_8x8 prediction modes for macroblocks of the current layer representation, +- a list ipred16x16 with PicSizeInMbs elements specifying Intra\_16x16 prediction modes for macroblocks of the current layer representation, +- when ChromaArrayType is equal to 1 or 2, a list ipredChroma with PicSizeInMbs elements specifying intra chroma prediction modes for macroblocks of the current layer representation. + +Outputs of this process are: + +- a modified version of the array ipred4x4, +- a modified version of the array ipred8x8, +- a modified version of the list ipred16x16, +- when ChromaArrayType is equal to 1 or 2, a modified version of the array ipredChroma. + +For all processes specified in clause 6 that are invoked from the process specified in this clause or a child process of the process specified in this clause, the following modifications apply: + +- a) In clause 6.4.12.2, a macroblock with address mbAddr is treated as field macroblock when fieldMbFlag[ mbAddr ] is equal to 1, and it is treated as frame macroblock when fieldMbFlag[ mbAddr ] is equal to 0. In particular, the current macroblock is treated as field macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 1, and it is treated as frame macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 0. +- b) In clause 6.4.8, a macroblock with address mbAddr is treated to belong to a different slice than the current macroblock CurrMbAddr, when sliceIdc[ mbAddr ] is not equal to sliceIdc[ CurrMbAddr ]. +- c) In clause 6.4.12.2, a macroblock mbAddr is treated as top macroblock when (mbAddr % 2) is equal to 0, and it is treated as bottom macroblock when (mbAddr % 2) is equal to 1. + +When mbType[ CurrMbAddr ] is not equal to I\_PCM, the following applies: + +- If mbType[ CurrMbAddr ] is equal to I\_4x4, the SVC derivation process for Intra\_4x4 prediction modes as specified in clause F.8.3.1.1 is invoked with sliceIdc, fieldMbFlag, baseModeFlag, mbType, ipred4x4, and ipred8x8 as the inputs and the output is a modified version of the array ipred4x4. +- Otherwise, if mbType[ CurrMbAddr ] is equal to I\_8x8, the SVC derivation process for Intra\_8x8 prediction modes as specified in clause F.8.3.1.2 is invoked with sliceIdc, fieldMbFlag, baseModeFlag, mbType, ipred4x4, and ipred8x8 as the inputs and the output is a modified version of the array ipred8x8. +- Otherwise, if mbType[ CurrMbAddr ] is equal to I\_16x16, ipred16x16[ CurrMbAddr ] is set equal to Intra16x16PredMode. + +When ChromaArrayType is equal to 1 or 2 and mbType[ CurrMbAddr ] is not equal to I\_PCM, ipredChroma[ CurrMbAddr ] is set equal to intra\_chroma\_pred\_mode. + +#### F.8.3.1.1 SVC derivation process for Intra\_4x4 prediction modes + +Inputs to this process are: + +- a one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of the current layer representation, +- a list fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a list baseModeFlag with PicSizeInMbs elements specifying the syntax element base\_mode\_flag for the macroblocks of the current layer representation, +- a list mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current layer representation, +- a (PicSizeInMbs)x16 array ipred4x4 specifying Intra\_4x4 prediction modes for macroblocks of the current layer representation, +- a (PicSizeInMbs)x4 array ipred8x8 specifying Intra\_8x8 prediction modes for macroblocks of the current layer representation. + +Output of this process is a modified version of the array ipred4x4. + +The 4x4 blocks indexed by c4x4BlkIdx = 0..15 are processed in increasing order of c4x4BlkIdx, and for each 4x4 block, the following ordered steps are specified: + +1. The derivation process for neighbouring 4x4 luma blocks as specified in clause 6.4.11.4 is invoked with c4x4BlkIdx as the input and the outputs are assigned to mbAddrA, c4x4BlkIdxA, mbAddrB, and c4x4BlkIdxB. For this invocation of the process in clause 6.4.11.4, the modifications specified in items a) through c) in clause F.8.3.1 apply. +2. For N being replaced by A and B, the variables availableFlagN are derived as follows: + - If the macroblock mbAddrN is available and any of the following conditions are true, availableFlagN is set equal to 1: + - constrained\_intra\_pred\_flag is equal to 0, + - mbType[ mbAddrN ] is equal to I\_PCM and tcoeff\_level\_prediction\_flag is equal to 1, + - mbType[ mbAddrN ] is equal to I\_PCM and baseModeFlag[ mbAddrN ] is equal to 0, + - mbType[ mbAddrN ] is equal to I\_16x16, I\_8x8, or I\_4x4. + - Otherwise, availableFlagN is set equal to 0. +3. The variable dcPredModePredictedFlag is derived as follows: + - If availableFlagA or availableFlagB is equal to 0, dcPredModePredictedFlag is set equal to 1. + - Otherwise (availableFlagA is equal to 1 and availableFlagB is equal to 1), dcPredModePredictedFlag is set equal to 0. +4. For N being replaced by A and B, the variables intraMxMPredModeN are derived as follows: + - If dcPredModePredictedFlag is equal to 0 and mbType[ mbAddrN ] is equal to I\_4x4, intraMxMPredModeN is set equal to ipred4x4[ mbAddrN ][ c4x4BlkIdxN ]. + - Otherwise, if dcPredModePredictedFlag is equal to 0 and mbType[ mbAddrN ] is equal to I\_8x8, intraMxMPredModeN is set equal to ipred8x8[ mbAddrN ][ c4x4BlkIdxN >> 2 ]. + - Otherwise (dcPredModePredictedFlag is equal to 1 or (mbType[ mbAddrN ] is not equal to I\_4x4 and mbType[ mbAddrN ] is not equal to I\_8x8)), intraMxMPredModeN is set equal to 2. +5. The element ipred4x4[ CurrMbAddr ][ c4x4BlkIdx ] of the array ipred4x4 is derived by applying the procedure specified in the following pseudo-code: + +``` +predIntra4x4PredMode = Min( intraMxMPredModeA, intraMxMPredModeB ) +if( prev_intra4x4_pred_mode_flag[ c4x4BlkIdx ] ) + ipred4x4[ CurrMbAddr ][ c4x4BlkIdx ] = predIntra4x4PredMode +``` + +``` + + else if( rem_intra4x4_pred_mode[ c4x4BlkIdx ] < predIntra4x4PredMode ) (F-85) + ipred4x4[ CurrMbAddr ][ c4x4BlkIdx ] = rem_intra4x4_pred_mode[ c4x4BlkIdx ] + else + ipred4x4[ CurrMbAddr ][ c4x4BlkIdx ] = rem_intra4x4_pred_mode[ c4x4BlkIdx ] + 1 + +``` + +#### F.8.3.1.2 SVC derivation process for Intra\_8x8 prediction modes + +Inputs to this process are: + +- a one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of the current layer representation, +- a list fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a list baseModeFlag with PicSizeInMbs elements specifying the syntax element base\_mode\_flag for the macroblocks of the current layer representation, +- a list mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current layer representation, +- a (PicSizeInMbs)x16 array ipred4x4 specifying Intra\_4x4 prediction modes for macroblocks of the current layer representation, +- a (PicSizeInMbs)x4 array ipred8x8 specifying Intra\_8x8 prediction modes for macroblocks of the current layer representation. + +Output of this process is a modified version of the array ipred8x8. + +The 8x8 blocks indexed by c8x8BlkIdx = 0..3 are processed in increasing order of c8x8BlkIdx, and for each 8x8 block, the following ordered steps are specified: + +1. The derivation process for neighbouring 8x8 luma blocks as specified in clause 6.4.11.2 is invoked with c8x8BlkIdx as the input and the outputs are assigned to mbAddrA, c8x8BlkIdxA, mbAddrB, and c8x8BlkIdxB. For this invocation of the process in clause 6.4.11.2, the modifications specified in items a) through c) in clause F.8.3.1 apply. +2. For N being replaced by A and B, the variables availableFlagN are derived as follows: + - If the macroblock mbAddrN is available and any of the following conditions are true, availableFlagN is set equal to 1: + - constrained\_intra\_pred\_flag is equal to 0, + - mbType[ mbAddrN ] is equal to I\_PCM and tcoeff\_level\_prediction\_flag is equal to 1, + - mbType[ mbAddrN ] is equal to I\_PCM and baseModeFlag[ mbAddrN ] is equal to 0, + - mbType[ mbAddrN ] is equal to I\_16x16, I\_8x8, or I\_4x4. + - Otherwise, availableFlagN is set equal to 0. +3. The variable dcPredModePredictedFlag is derived as follows: + - If availableFlagA or availableFlagB is equal to 0, dcPredModePredictedFlag is set equal to 1. + - Otherwise (availableFlagA is equal to 1 and availableFlagB are equal to 1), dcPredModePredictedFlag is set equal to 0. +4. For N being replaced by A and B, the variables intraMxMPredModeN are derived as follows: + - If dcPredModePredictedFlag is equal to 0 and mbType[ mbAddrN ] is equal to I\_4x4, intraMxMPredModeN is set equal to ipred4x4[ mbAddrN ][ c8x8BlkIdxN \* 4 + c4x4Idx ] with the variable c4x4Idx being derived as follows: + - If N is equal to B, c4x4Idx is set equal to 2. + - Otherwise, if fieldMbFlag[ CurrMbAddr ] is equal to 0, fieldMbFlag[ mbAddrN ] is equal to 1, and c8x8BlkIdx is equal to 2, c4x4Idx is set equal to 3. + - Otherwise (N is equal to A and (fieldMbFlag[ CurrMbAddr ] is equal to 1 or fieldMbFlag[ mbAddrN ] is equal to 0 or c8x8BlkIdx is not equal to 2)), c4x4Idx is set equal to 1. + +- Otherwise, if dcPredModePredictedFlag is equal to 0 and mbType[ mbAddrN ] is equal to I\_8x8, intraMxMPredModeN is set equal to ipred8x8[ mbAddrN ][ c8x8BlkIdxN ]. + - Otherwise (dcPredModePredictedFlag is equal to 1 or (mbType[ mbAddrN ] is not equal to I\_4x4 and mbType[ mbAddrN ] is not equal to I\_8x8)), intraMxMPredModeN is set equal to 2. +5. The element ipred8x8[ CurrMbAddr ][ c8x8BlkIdx ] of the array ipred8x8 is derived by applying the procedure specified in the following pseudo-code: + +``` +predIntra8x8PredMode = Min( intraMxMPredModeA, intraMxMPredModeB ) +if( prev_intra8x8_pred_mode_flag[ c8x8BlkIdx ] ) + ipred8x8[ CurrMbAddr ][ c8x8BlkIdx ] = predIntra8x8PredMode +else if( rem_intra8x8_pred_mode[ c8x8BlkIdx ] < predIntra8x8PredMode ) + ipred8x8[ CurrMbAddr ][ c8x8BlkIdx ] = rem_intra8x8_pred_mode[ c8x8BlkIdx ] +else + ipred8x8[ CurrMbAddr ][ c8x8BlkIdx ] = rem_intra8x8_pred_mode[ c8x8BlkIdx ] + 1 +``` + +(F-86) + +### F.8.3.2 SVC intra sample prediction and construction process + +This process is only invoked when mbType specified as input to this process is equal to I\_PCM, I\_16x16, I\_8x8, or I\_4x4. + +Inputs to this process are: + +- a one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of the current layer representation, +- a one-dimensional array fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a list baseModeFlag with PicSizeInMbs elements specifying the syntax element base\_mode\_flag for the macroblocks of the current layer representation, +- a one-dimensional array mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current layer representation, +- a list ipred4x4 with 16 elements specifying Intra\_4x4 prediction modes for the current macroblock, +- a list ipred8x8 with 4 elements specifying Intra\_8x8 prediction modes for the current macroblock, +- a variable ipred16x16 specifying the Intra\_16x16 prediction mode for the current macroblock, +- a variable ipredChroma specifying the intra chroma prediction mode for the current macroblock, +- a variable cTrafo specifying the transform type for the current macroblock, +- a list of scaled transform coefficient values sTCoeff with (256 + 2 \* MbWidthC \* MbHeightC) elements, +- a (PicWidthInSamplesL)x(PicHeightInSamplesL) array picSamplesL containing constructed luma sample values for the current layer representation. +- when ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picSamplesCB and picSamplesCR containing constructed chroma sample values for the current layer representation. + +Outputs of this process are: + +- a modified version of the array picSamplesL, +- when ChromaArrayType is not equal to 0, modified versions of the arrays picSamplesCB and picSamplesCR. + +For all processes specified in clauses 6 or 8 that are invoked from the process specified in this clause or a child process of the process specified in this clause, the following modifications apply. + +- In clause 6.4.12.2, a macroblock with address mbAddr is treated as field macroblock when fieldMbFlag[ mbAddr ] is equal to 1, and it is treated as frame macroblock when fieldMbFlag[ mbAddr ] is equal to 0. In particular, the current macroblock is treated as field macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 1, and it is treated as frame macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 0. +- In clause 6.4.8, a macroblock with address mbAddr is treated to belong to a different slice than the current macroblock CurrMbAddr, when MbToSliceGroupMap[ mbAddr ] is not equal to MbToSliceGroupMap[ CurrMbAddr ] or mbAddr is less than ( ( sliceIdc[ CurrMbAddr ] >> 7 ) \* ( 1 + MbAffFrameFlag ) ), where MbToSliceGroupMap represents the variable that is derived as specified in clause 8.2.2 for the layer representation with DQId equal to ( sliceIdc[ CurrMbAddr ] & 127 ). + +NOTE 1 – When MaxTCoeffLevelPredFlag is equal to 0 or when all macroblocks of the current layer picture are covered by slices with the same value of DQId, the above condition can be simplified. In this case, two macroblocks mbAddrA and mbAddrB can be treated to belong to different slices, when sliceIdc[ mbAddrA ] is not equal to sliceIdc[ mbAddrB ]. + +- c) In clause 6.4.12.2, a macroblock mbAddr is treated as top macroblock when (mbAddr % 2) is equal to 0, and it is treated as bottom macroblock when (mbAddr % 2) is equal to 1. +- d) In clauses 8.3.1.2, 8.3.2.2, 8.3.3, and 8.3.4, the variables Intra4x4PredMode, Intra8x8PredMode, Intra16x16PredMode, and intra\_chroma\_pred\_mode are replaced by ipred4x4, ipred8x8, ipred16x16, and ipredChroma, respectively. +- e) In clauses 8.3.1.2, 8.3.2.2, 8.3.3, and 8.3.4, the syntax element mb\_type of a macroblock with macroblock address mbAddr is replaced by mbType[ mbAddr ]. +- f) The value of constrained\_intra\_pred\_flag that is referred to in clauses 8.3.1.2, 8.3.2.2, 8.3.3, and 8.3.4 is specified as follows: + - If (sliceIdc[ CurrMbAddr ] & 127) is less than DQIdMax, the value of constrained\_intra\_pred\_flag is the value of constrained\_intra\_pred\_flag of the active layer picture parameter set for the layer representation with DQId equal to (sliceIdc[ CurrMbAddr ] & 127). + - Otherwise ((sliceIdc[ CurrMbAddr ] & 127) is equal to DQIdMax), the value of constrained\_intra\_pred\_flag is the value of constrained\_intra\_pred\_flag of the active picture parameter set. +- g) In clauses 8.3.1.2, 8.3.2.2, 8.3.3, and 8.3.4, a macroblock with mbAddrN is treated as coded in an Inter macroblock prediction mode when all of the following conditions are false: + - mbType[ mbAddrN ] is equal to I\_PCM and tcoeff\_level\_prediction\_flag for the slice with DQId equal to (sliceIdc[ mbAddrN ] & 127) and first\_mb\_in\_slice equal to (sliceIdc[ mbAddrN ] >> 7) is equal to 1, + - mbType[ mbAddrN ] is equal to I\_PCM and baseModeFlag[ mbAddrN ] is equal to 0, + - mbType[ mbAddrN ] is equal to I\_16x16, I\_8x8, or I\_4x4, + - sliceIdc[ mbAddrN ] is not equal to sliceIdc[ CurrMbAddr ]. + +NOTE 2 – The latter condition does only have an impact on the decoding process when MaxTCoeffLevelPredFlag is equal to 1 and not all macroblocks of the current layer picture are covered by slices with the same value of DQId. + +NOTE 3 – Encoder designers are encouraged to generate bitstreams for which the removal of zero or more slice data NAL units with quality\_id greater than 0 cannot result in a conforming bitstream for which a macroblock with address mbAddr is intra-predicted from a macroblock with address mbAddrN and sliceIdc[ mbAddrN ] not equal to sliceIdc[ mbAddr ]. + +The SVC intra sample prediction and construction process proceeds in the following ordered steps: + +1. The construction process for luma residuals or chroma residuals with ChromaArrayType equal to 3 as specified in clause F.8.5.3.1 is invoked with cTrafo and sTCoeff as the inputs and the outputs are residual luma sample values as a 16x16 array mbResL with elements mbResL[ x, y ]. +2. When ChromaArrayType is not equal to 0, the construction process for chroma residuals as specified in clause F.8.5.3.2 is invoked with cTrafo and sTCoeff as the inputs and the outputs are residual chroma sample values as two (MbWidthC)x(MbHeightC) arrays mbResCb and mbResCr with elements mbResCb[ x, y ] and mbResCr[ x, y ], respectively. +3. The SVC intra prediction and construction process for luma samples or chroma samples with ChromaArrayType equal to 3 as specified in clause F.8.3.2.1 is invoked with BitDepthy, sliceIdc, fieldMbFlag, mbType, ipred4x4, ipred8x8, ipred16x16, mbResL, and picSamplesL as the inputs and the output is a modified version of the array picSamplesL. +4. When ChromaArrayType is not equal to 0, the SVC intra prediction and construction process for chroma samples as specified in clause F.8.3.2.2 is invoked with sliceIdc, fieldMbFlag, mbType, ipred4x4, ipred8x8, ipred16x16, ipredChroma, mbResCb, mbResCr, picSamplesCb, and picSamplesCr as the inputs and the outputs are modified versions of the arrays picSamplesCb and picSamplesCr. + +#### F.8.3.2.1 SVC intra prediction and construction process for luma samples or chroma samples with ChromaArrayType equal to 3 + +Inputs to this process are: + +- a variable bitDepth specifying the bit depth, + +- a one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of the current layer representation, +- a one-dimensional array fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a one-dimensional array mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current layer representation, +- a list ipred4x4 with 16 elements specifying Intra\_4x4 prediction modes for the current macroblock, +- a list ipred8x8 with 4 elements specifying Intra\_8x8 prediction modes for the current macroblock, +- a variable ipred16x16 specifying the Intra\_16x16 prediction mode for the current macroblock, +- a 16x16 array mbRes containing residual sample values for the current macroblock, +- a (PicWidthInSamplesL)x(PicHeightInSamplesL) array picSamples containing constructed sample values for the current layer representation. + +Outputs of this process is a modified version of the array picSamples. + +Depending on mbType[ CurrMbAddr ], the following applies: + +- If mbType[ CurrMbAddr ] is equal to I\_PCM, the SVC construction process for luma samples and chroma samples with ChromaArrayType equal to 3 of I\_PCM macroblocks as specified in clause F.8.3.2.1.1 is invoked with fieldMbFlag, mbRes, and picSamples as the inputs and the output is a modified version of the array picSamples. +- Otherwise, if mbType[ CurrMbAddr ] is equal to I\_4x4, the SVC Intra\_4x4 sample prediction and construction process as specified in clause F.8.3.2.1.2 is invoked with bitDepth, sliceIdc, fieldMbFlag, mbType, ipred4x4, mbRes, and picSamples as the inputs and the output is a modified version of the array picSamples. +- Otherwise, if mbType[ CurrMbAddr ] is equal to I\_8x8, the SVC Intra\_8x8 sample prediction and construction process as specified in clause F.8.3.2.1.3 is invoked with bitDepth, sliceIdc, fieldMbFlag, mbType, ipred8x8, mbRes, and picSamples as the inputs and the output is a modified version of the array picSamples. +- Otherwise (mbType[ CurrMbAddr ] is equal to I\_16x16), the SVC Intra\_16x16 sample prediction and construction process as specified in clause F.8.3.2.1.4 is invoked with bitDepth, sliceIdc, fieldMbFlag, mbType, ipred16x16, mbRes, and picSamples as the inputs and the output is a modified version of the array picSamples. + +#### **F.8.3.2.1.1 SVC construction process for luma samples and chroma samples with ChromaArrayType equal to 3 of I\_PCM macroblocks** + +Inputs to this process are: + +- a one-dimensional array fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a 16x16 array mbRes containing residual sample values for the current macroblock, +- a (PicWidthInSamplesL)x(PicHeightInSamplesL) array picSamples containing constructed sample values for the current layer representation. + +Output of this process is a modified version of the array picSamples. + +The picture sample array construction process for a signal component as specified in clause F.8.5.4.3 is invoked with fieldMbFlag[ CurrMbAddr ], mbW set equal to 16, mbH set equal to 16, mbRes, and picSamples as the inputs and the output is a modified version of the array picSamples. + +#### **F.8.3.2.1.2 SVC Intra\_4x4 sample prediction and construction process** + +Inputs to this process are: + +- a variable bitDepth specifying the bit depth, +- a one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of the current layer representation, +- a one-dimensional array fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a one-dimensional array mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current layer representation, + +- a list ipred4x4 with 16 elements specifying Intra\_4x4 prediction modes for the current macroblock, +- a 16x16 array mbRes containing residual sample values for the current macroblock, +- a (PicWidthInSamplesL)x(PicHeightInSamplesL) array picSamples containing constructed sample values for the current layer representation. + +Output of this process is a modified version of the array picSamples. + +Let mbSamples be a 16x16 array containing constructed intra sample values for the current macroblock. All elements of mbSamples are initially set equal to 0. + +The 4x4 blocks indexed by c4x4BlkIdx = 0..15 are processed in increasing order of c4x4BlkIdx, and for each 4x4 block, the following ordered steps are specified: + +1. The Intra\_4x4 sample prediction process as specified in clause 8.3.1.2 is invoked with c4x4BlkIdx and picSamples as the inputs and the outputs are intra prediction sample values as a 4x4 array pred4x4 with elements pred4x4[ x, y ]. For this invocation of the process in clause 8.3.1.2, the modifications specified in items a) through g) of clause F.8.3.2 apply. Additionally in clause 8.3.1.2.3, which may be invoked as part of the process specified in clause 8.3.1.2, the variable BitDepthy is replaced by bitDepth. +2. The inverse 4x4 luma block scanning process as specified in clause 6.4.3 is invoked with c4x4BlkIdx as the input and the output is assigned to ( xP, yP ). +3. For x = xP..(xP + 3) and y = yP..(yP + 3) and with Clip( a ) specifying Clip3( 0, ( 1 << bitDepth ) – 1, a ), the elements mbSamples[ x, y ] of the 16x16 array mbSamples are derived by + +$$\text{mbSamples[ x, y ]} = \text{Clip( pred4x4[ x - xP, y - yP ] + mbRes[ x, y ] )} \quad (\text{F-87})$$ + +4. The picture sample array construction process for a signal component as specified in clause F.8.5.4.3 is invoked with fieldMbFlag[ CurrMbAddr ], mbW set equal to 16, mbH set equal to 16, mbSamples, and picSamples as the inputs and the output is a modified version of the array picSamples. + +NOTE – When c4x4BlkIdx is less than 15, the array mbSamples does only contain constructed intra samples for 4x4 blocks with c4x4BlkIdx less than or equal to the current value of c4x4BlkIdx. + +#### F.8.3.2.1.3 SVC Intra\_8x8 sample prediction and construction process + +Inputs to this process are: + +- a variable bitDepth specifying the bit depth, +- a one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of the current layer representation, +- a one-dimensional array fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a one-dimensional array mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current layer representation, +- a list ipred8x8 with 4 elements specifying Intra\_8x8 prediction modes for the current macroblock, +- a 16x16 array mbRes containing residual sample values for the current macroblock, +- a (PicWidthInSamplesL)x(PicHeightInSamplesL) array picSamples containing constructed sample values for the current layer representation. + +Output of this process is a modified version of the array picSamples. + +Let mbSamples be a 16x16 array containing constructed intra sample values for the current macroblock. All elements of mbSamples are initially set equal to 0. + +The 8x8 blocks indexed by c8x8BlkIdx = 0..3 are processed in increasing order of c8x8BlkIdx, and for each 8x8 block, the following ordered steps are specified: + +1. The Intra\_8x8 sample prediction process as specified in clause 8.3.2.2 is invoked with c8x8BlkIdx and picSamples as the inputs and the outputs are intra prediction sample values as an 8x8 array pred8x8 with elements pred8x8[ x, y ]. For this invocation of the process in clause 8.3.2.2, the modifications specified in items a) through g) of clause F.8.3.2 apply. Additionally in clause 8.3.2.2.4, which may be invoked as part of the process specified in clause 8.3.2.2, the variable BitDepthy is replaced by bitDepth. +2. The inverse 8x8 luma block scanning process as specified in clause 6.4.5 is invoked with c8x8BlkIdx as the input and the output is assigned to ( xP, yP ). + +3. For $x = xP..(xP + 7)$ and $y = yP..(yP + 7)$ and with $\text{Clip}(a)$ specifying $\text{Clip3}(0, (1 \ll \text{bitDepth}) - 1, a)$ , the elements $\text{mbSamples}[x, y]$ of the 16x16 array $\text{mbSamples}$ are derived by + +$$\text{mbSamples}[x, y] = \text{Clip}(\text{pred8x8}[x - xP, y - yP] + \text{mbRes}[x, y]) \quad (\text{F-88})$$ + +4. The picture sample array construction process for a signal component as specified in clause F.8.5.4.3 is invoked with $\text{fieldMbFlag}[\text{CurrMbAddr}]$ , $\text{mbW}$ set equal to 16, $\text{mbH}$ set equal to 16, $\text{mbSamples}$ , and $\text{picSamples}$ as the inputs and the output is a modified version of the array $\text{picSamples}$ . + +NOTE – When $\text{c8x8BlkIdx}$ is less than 3, the array $\text{mbSamples}$ does only contain constructed intra samples for 8x8 blocks with $\text{c8x8BlkIdx}$ less than or equal to the current value of $\text{c8x8BlkIdx}$ . + +#### F.8.3.2.1.4 SVC Intra\_16x16 sample prediction and construction process + +Inputs to this process are: + +- a variable $\text{bitDepth}$ specifying the bit depth, +- a one-dimensional array $\text{sliceIdc}$ with $\text{PicSizeInMbs}$ elements specifying slice identifications for the macroblocks of the current layer representation, +- a one-dimensional array $\text{fieldMbFlag}$ with $\text{PicSizeInMbs}$ elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a one-dimensional array $\text{mbType}$ with $\text{PicSizeInMbs}$ elements specifying macroblock types for the macroblocks of the current layer representation, +- a variable $\text{ipred16x16}$ specifying the Intra\_16x16 prediction mode for the current macroblock, +- a 16x16 array $\text{mbRes}$ containing residual sample values for the current macroblock, +- a $(\text{PicWidthInSamples}_L) \times (\text{PicHeightInSamples}_L)$ array $\text{picSamples}$ containing constructed sample values for the current layer representation. + +Output of this process is a modified version of the array $\text{picSamples}$ . + +The SVC Intra\_16x16 sample prediction and construction process proceeds in the following ordered steps: + +1. The Intra\_16x16 prediction process for luma samples as specified in clause 8.3.3 is invoked with $\text{picSamples}$ as the input and the outputs are intra prediction sample values as a 16x16 array $\text{pred16x16}$ with elements $\text{pred16x16}[x, y]$ . For this invocation of the process in clause 8.3.3, the modifications specified in items a) through g) of clause F.8.3.2 apply. Additionally in clause 8.3.3.3, which may be invoked as part of the process specified in clause 8.3.3, the variable $\text{BitDepth}_Y$ is replaced by $\text{bitDepth}$ . + +2. With $\text{Clip}(a)$ specifying $\text{Clip3}(0, (1 \ll \text{bitDepth}) - 1, a)$ , the 16x16 array $\text{mbSamples}$ is derived by + +$$\text{mbSamples}[x, y] = \text{Clip}(\text{pred16x16}[x, y] + \text{mbRes}[x, y]) \quad \text{with } x, y = 0..15 \quad (\text{F-89})$$ + +3. The picture sample array construction process for a signal component as specified in clause F.8.5.4.3 is invoked with $\text{fieldMbFlag}[\text{CurrMbAddr}]$ , $\text{mbW}$ set equal to 16, $\text{mbH}$ set equal to 16, $\text{mbSamples}$ , and $\text{picSamples}$ as the inputs and the output is a modified version of the array $\text{picSamples}$ . + +#### F.8.3.2.2 SVC intra prediction and construction process for chroma samples + +Inputs to this process are: + +- a one-dimensional array $\text{sliceIdc}$ with $\text{PicSizeInMbs}$ elements specifying slice identifications for the macroblocks of the current layer representation, +- a one-dimensional array $\text{fieldMbFlag}$ with $\text{PicSizeInMbs}$ elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a one-dimensional array $\text{mbType}$ with $\text{PicSizeInMbs}$ elements specifying macroblock types for the macroblocks of the current layer representation, +- a list $\text{ipred4x4}$ with 16 elements specifying Intra\_4x4 prediction modes for the current macroblock, +- a list $\text{ipred8x8}$ with 4 elements specifying Intra\_8x8 prediction modes for the current macroblock, +- a variable $\text{ipred16x16}$ specifying the Intra\_16x16 prediction mode for the current macroblock, +- a variable $\text{ipredChroma}$ specifying the intra chroma prediction mode for the current macroblock, +- two $(\text{MbWidthC}) \times (\text{MbHeightC})$ arrays $\text{mbRes}_{Cb}$ and $\text{mbRes}_{Cr}$ containing residual chroma sample values for the current macroblock, + +- two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picSamplesCb and picSamplesCr containing constructed sample values for the current layer representation. + +Outputs of this process are modified versions of the arrays picSamplesCb and picSamplesCr. + +Depending on ChromaArrayType, the following applies: + +- If ChromaArrayType is equal to 1 or 2, the following applies: + - If mbType[ CurrMbAddr ] is equal to I\_PCM, the SVC construction process for chroma samples of I\_PCM macroblock as specified in clause F.8.3.2.2.1 is invoked with fieldMbFlag, mbResCb, mbResCr, picSamplesCb, and picSamplesCr as the inputs and the outputs are modified versions of picSamplesCb and picSamplesCr. + - Otherwise (mbType[ CurrMbAddr ] is not equal to I\_PCM), the SVC intra prediction and construction process for chroma samples with ChromaArrayType equal to 1 or 2 as specified in clause F.8.3.2.2.2 is invoked with sliceIdc, fieldMbFlag, mbType, ipredChroma, mbResCb, mbResCr, picSamplesCb, and picSamplesCr as the inputs and the outputs are modified versions of the arrays picSamplesCb and picSamplesCr. +- Otherwise (ChromaArrayType is equal to 3), for CX being replaced by Cb and Cr, the SVC intra prediction and construction process for luma samples or chroma samples with ChromaArrayType equal to 3 as specified in clause F.8.3.2.1 is invoked with BitDepthC, sliceIdc, fieldMbFlag, mbType, ipred4x4, ipred8x8, ipred16x16, mbResCX, and picSamplesCX as the inputs and the output is a modified version of the array picSamplesCX. + +#### F.8.3.2.2.1 SVC construction process for chroma samples of I\_PCM macroblocks + +Inputs to this process are: + +- a one-dimensional array fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- two (MbWidthC)x(MbHeightC) arrays mbResCb and mbResCr containing residual chroma sample values for the current macroblock, +- two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picSamplesCb and picSamplesCr containing constructed chroma sample values for the current layer representation. + +Outputs of this process are modified versions of the arrays picSamplesCb and picSamplesCr. + +For CX being replaced by Cb and Cr, the picture sample array construction process for a signal component as specified in clause F.8.5.4.3 is invoked with fieldMbFlag[ CurrMbAddr ], mbW set equal to MbWidthC, mbH set equal to MbHeightC, mbResCX, and picSamplesCX as the inputs and the output is a modified version of the array picSamplesCX. + +#### F.8.3.2.2.2 SVC intra prediction and construction process for chroma samples with ChromaArrayType equal to 1 or 2 + +This process is only invoked when ChromaArrayType is equal to 1 or 2. + +Inputs to this process are: + +- a one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of the current layer representation, +- a one-dimensional array fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a one-dimensional array mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current layer representation, +- a variable ipredChroma specifying the intra chroma prediction mode for the current macroblock, +- two (MbWidthC)x(MbHeightC) arrays mbResCb and mbResCr containing residual chroma sample values for the current macroblock, +- two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picSamplesCb and picSamplesCr containing constructed chroma sample values for the current layer representation. + +Outputs of this process are modified versions of the arrays picSamplesCb and picSamplesCr. + +The SVC intra prediction and construction process for chroma samples with ChromaArrayType equal to 1 or 2 proceeds in the following ordered steps: + +1. The intra prediction process for chroma samples as specified in clause 8.3.4 is invoked with picSamplesCb and picSamplesCr as the inputs and the outputs are intra prediction chroma sample values as two + +(MbWidthC)x(MbHeightC) arrays $\text{pred}_{\text{Cb}}$ and $\text{pred}_{\text{Cr}}$ with elements $\text{pred}_{\text{Cb}}[ x, y ]$ and $\text{pred}_{\text{Cr}}[ x, y ]$ , respectively. For this invocation of the process in clause 8.3.4, the modifications specified in items a) through g) of clause F.8.3.2 apply. + +2. For CX being replaced by Cb and Cr, the (MbWidthC)x(MbHeightC) array $\text{mbSamples}_{\text{CX}}$ is derived by + +$$\text{mbSamples}_{\text{CX}}[ x, y ] = \text{Clip1C}( \text{pred}_{\text{CX}}[ x, y ] + \text{mbRes}_{\text{CX}}[ x, y ] ) \quad \text{with } x = 0..(\text{MbWidthC} - 1) \text{ and } y = 0..(\text{MbHeightC} - 1) \quad (\text{F-90})$$ + +3. For CX being replaced by Cb and Cr, the picture sample array construction process for a signal component as specified in clause F.8.5.4.3 is invoked with $\text{fieldMbFlag}[ \text{CurrMbAddr} ]$ , $\text{mbW}$ set equal to $\text{MbWidthC}$ , $\text{mbH}$ set equal to $\text{MbHeightC}$ , $\text{mbSamples}_{\text{CX}}$ , and $\text{picSamples}_{\text{CX}}$ as the inputs and the output is a modified version of the array $\text{picSamples}_{\text{CX}}$ . + +#### F.8.4 SVC Inter prediction process + +Clause F.8.4.1 specifies the SVC derivation process for motion vector components and reference indices. + +Clause F.8.4.2 specifies the SVC decoding process for Inter prediction samples + +##### F.8.4.1 SVC derivation process for motion vector components and reference indices + +Inputs to this process are: + +- a one-dimensional array $\text{sliceIdc}$ with $\text{PicSizeInMbs}$ elements specifying slice identifications for the macroblocks of the current layer representation, +- a one-dimensional array $\text{fieldMbFlag}$ with $\text{PicSizeInMbs}$ elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a one-dimensional array $\text{mbType}$ with $\text{PicSizeInMbs}$ elements specifying macroblock types for the macroblocks of the current layer representation, +- a ( $\text{PicSizeInMbs}$ )x4 array $\text{subMbType}$ specifying sub-macroblock types for the macroblocks of the current layer representation, +- two ( $\text{PicSizeInMbs}$ )x4 arrays $\text{predFlagL0}$ and $\text{predFlagL1}$ specifying prediction utilization flags for the macroblocks of the current layer representation, +- two ( $\text{PicSizeInMbs}$ )x4 arrays $\text{refIdxL0}$ and $\text{refIdxL1}$ specifying reference indices for the macroblocks of the current layer representation, +- two ( $\text{PicSizeInMbs}$ )x4x4x2 arrays $\text{mvL0}$ and $\text{mvL1}$ specifying motion vector components for the macroblocks of the current layer representation, +- a one-dimensional array $\text{mvCnt}$ with $\text{PicSizeInMbs}$ elements specifying the number of motion vectors for the macroblocks of the current layer representation, +- two 2x2 arrays $\text{refIdxILPredL0}$ and $\text{refIdxILPredL1}$ specifying inter-layer reference index predictors for the current macroblock, +- two 4x4x2 arrays $\text{mvILPredL0}$ and $\text{mvILPredL1}$ specifying inter-layer motion vector predictors for the current macroblock, +- when $\text{DQId}$ is equal to 0 and $(\text{slice\_type} \% 5)$ is equal to 1, the reference list $\text{refPicList1}$ . + +Outputs of this process are: + +- modified versions of the arrays $\text{predFlagL0}$ and $\text{predFlagL1}$ , +- modified versions of the arrays $\text{refIdxL0}$ and $\text{refIdxL1}$ , +- modified versions of the arrays $\text{mvL0}$ and $\text{mvL1}$ , +- a modified version of the array $\text{mvCnt}$ . + +Depending on $\text{mbType}[ \text{CurrMbAddr} ]$ , the following applies: + +- If $\text{mbType}[ \text{CurrMbAddr} ]$ is equal to $\text{I\_PCM}$ , $\text{I\_16x16}$ , $\text{I\_8x8}$ , $\text{I\_4x4}$ , or $\text{I\_BL}$ , the arrays $\text{predFlagL0}$ , $\text{predFlagL1}$ , $\text{refIdxL0}$ , $\text{refIdxL1}$ , $\text{mvL0}$ , $\text{mvL1}$ , and $\text{mvCnt}$ are modified by: + +$$\text{predFlagLX}[ \text{CurrMbAddr} ][ m ] = 0 \quad \text{with } X = 0..1, m = 0..3 \quad (\text{F-91})$$ + +$$\text{refIdxLX}[ \text{CurrMbAddr} ][ m ] = -1 \quad \text{with } X = 0..1, m = 0..3 \quad (\text{F-92})$$ + +$$\text{mvLX[ CurrMbAddr ][ m ][ s ][ c ]} = 0 \quad \text{with } X = 0..1, m = 0..3, s = 0..3, c = 0..1 \quad (\text{F-93})$$ + +$$\text{mvCnt[ CurrMbAddr ]} = 0 \quad (\text{F-94})$$ + +- Otherwise (mbType[ CurrMbAddr ] is not equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL), the arrays predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, mvL1, and mvCnt are modified as specified by the following text. + +The variable numMbPart is derived as follows: + +- If mbType[ CurrMbAddr ] is equal to B\_Skip or B\_Direct\_16x16 and DQId is equal to 0 (nal\_unit\_type is not equal to 20), numMbPart is set equal to 4. +- Otherwise, if mbType[ CurrMbAddr ] is equal to B\_Skip or B\_Direct\_16x16 (and DQId is greater than 0 and nal\_unit\_type is equal to 20), numMbPart is set equal to 1. +- Otherwise (mbType[ CurrMbAddr ] is not equal to B\_Skip or B\_Direct\_16x16), numMbPart is set equal to NumMbPart( mbType[ CurrMbAddr ] ). + +The macroblock partition index mbPartIdx proceeds over the values 0..(numMbPart – 1), and for each value of mbPartIdx the following ordered steps are specified: + +1. The variable isDirectFlag is derived as follows: + - If any of the following conditions are true, isDirectFlag is set equal to 1: + - mbType[ CurrMbAddr ] is equal to B\_Skip or B\_Direct\_16x16, + - mbType[ CurrMbAddr ] is equal to B\_8x8 and subMbType[ CurrMbAddr ][ mbPartIdx ] is equal to B\_Direct\_8x8. + - Otherwise, isDirectFlag is set equal to 0. +2. The variable numSubMbPart is derived as follows: + - If isDirectFlag is equal to 1 and DQId is equal to 0 (nal\_unit\_type is not equal to 20), numSubMbPart is set equal to 4. + - Otherwise, if isDirectFlag is equal to 1 (and DQId is greater than 0 and nal\_unit\_type is equal to 20), numSubMbPart is set equal to 1. + - Otherwise (isDirectFlag is equal to 0), numSubMbPart is set equal to NumSubMbPart( subMbType[ CurrMbAddr ][ mbPartIdx ] ). +3. The sub-macroblock partition index subMbPartIdx proceeds over values 0..(numSubMbPart – 1), and for each value of subMbPartIdx the SVC derivation process for luma motion vector components and reference indices of a macroblock or sub-macroblock partition as specified in clause F.8.4.1.1 is invoked with mbPartIdx, subMbPartIdx, isDirectFlag, sliceIdc, fieldMbFlag, mbType, subMbType, predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, mvL1, mvCnt, refIdxILPredL0, refIdxILPredL1, mvILPredL0, mvILPredL1, and, when DQId is equal to 0 and (slice\_type % 5) is equal to 1, the reference picture list refPicList1 as the inputs and the outputs are modified versions of the arrays predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, mvL1, and mvCnt. + +#### F.8.4.1.1 SVC derivation process for luma motion vector components and reference indices of a macroblock or sub-macroblock partition + +This clause is only invoked when mbType[ CurrMbAddr ], which is specified as input to this clause, is not equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL. + +Inputs to this process are: + +- a variable mbPartIdx specifying the current macroblock partition, +- a variable subMbPartIdx specifying the current sub-macroblock partition, +- a variable isDirectFlag specifying whether the current macroblock partition is coded in direct mode, +- a one-dimensional array sliceIdc with PicSizeInMbs elements specifying slice identifications for the macroblocks of the current layer representation, +- a one-dimensional array fieldMbFlag with PicSizeInMbs elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a one-dimensional array mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current layer representation, + +- a (PicSizeInMbs)x4 array subMbType specifying sub-macroblock types for the macroblocks of the current layer representation, +- two (PicSizeInMbs)x4 arrays predFlagL0 and predFlagL1 specifying prediction utilization flags for the macroblocks of the current layer representation, +- two (PicSizeInMbs)x4 arrays refIdxL0 and refIdxL1 specifying reference indices for the macroblocks of the current layer representation, +- two (PicSizeInMbs)x4x4x2 arrays mvL0 and mvL1 specifying motion vector components for the macroblocks of the current layer representation, +- a one-dimensional array mvCnt with PicSizeInMbs elements specifying the number of motion vectors for the macroblocks of the current layer representation, +- two 2x2 arrays refIdxILPredL0 and refIdxILPredL1 specifying inter-layer reference index predictors for the current macroblock, +- two 4x4x2 arrays mvILPredL0 and mvILPredL1 specifying inter-layer motion vector predictors for the current macroblock, +- when DQId is equal to 0 and (slice\_type % 5) is equal to 1, the reference picture list refPicList1. + +Outputs of this process are: + +- modified versions of the arrays predFlagL0 and predFlagL1, +- modified versions of the arrays refIdxL0 and refIdxL1, +- modified versions of the arrays mvL0 and mvL1, +- a modified version of the array mvCnt. + +For all processes specified in clauses 6 or 8 that are invoked from the process specified in this clause or a child process of the process specified in this clause, the following modifications apply: + +- In clauses 6.4.12.2 and 8.4.1.3.2, a macroblock with address mbAddr is treated as field macroblock when fieldMbFlag[ mbAddr ] is equal to 1, and it is treated as frame macroblock when fieldMbFlag[ mbAddr ] is equal to 0. In particular, the current macroblock is treated as field macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 1, and it is treated as frame macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 0. +- In clause 6.4.8, a macroblock with address mbAddr is treated to belong to a different slice than the current macroblock CurrMbAddr, when sliceIdc[ mbAddr ] is not equal to sliceIdc[ CurrMbAddr ]. +- In clause 6.4.12.2, a macroblock mbAddr is treated as top macroblock when (mbAddr % 2) is equal to 0, and it is treated as bottom macroblock when (mbAddr % 2) is equal to 1. +- In clauses 6.4.2.1, 6.4.2.2, 6.4.11.7, 8.4.1.1, 8.4.1.3, any occurrence of mb\_type is replaced by mbType[ CurrMbAddr ] with mbType being the array mbType that is input to this clause. +- In clauses 6.4.2.2 and 6.4.11.7, any occurrence of sub\_mb\_type is replaced by subMbType[ CurrMbAddr ] with subMbType being the array subMbType that is input to this clause. +- In clause 6.4.11.7, mb\_type for a macroblock with macroblock address mbAddrN is replaced by mbType[ mbAddrN ] with mbType being the array mbType that is input to this clause and sub\_mb\_type for a macroblock with macroblock address mbAddrN is replaced by subMbType[ mbAddrN ] with subMbType being the array subMbType that is input to this clause. +- In clause 6.4.11.7, a macroblock partition or sub-macroblock partition given by mbAddrN, mbPartIdxN, and subMbPartIdxN is treated as not yet decoded when mbAddrN is equal to CurrMbAddr and (4 \* mbPartIdxN + subMbPartIdxN) is greater than (4 \* mbPartIdx + subMbPartIdx). +- In clause 8.4.1.3.2, a macroblock with mbAddrN is treated as coded in an Intra macroblock prediction mode when mbType[ mbAddrN ] is equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL. +- In clause 8.4.1.3.2, the variable predFlagLX of a macroblock or sub-macroblock partition given by mbAddrN\mbPartIdxN\subMbPartIdxN is replaced by predFlagLX[ mbAddrN ][ mbPartIdxN ] with predFlagLX being the array predFlagLX that is input to this clause. +- In clause 8.4.1.3.2, the motion vector MvLX[ mbPartIdxN ][ subMbPartIdxN ] and the reference index RefIdxLX[ mbPartIdxN ] of a macroblock or sub-macroblock partition given by mbAddrN\mbPartIdxN\subMbPartIdxN are replaced by mvLX[ mbAddrN ][ mbPartIdxN ][ subMbPartIdxN ] and RefIdxLX[ mbAddrN ][ mbPartIdxN ][ subMbPartIdxN ] + +and `refIdxLX[ mbAddrN ][ mbPartIdxN ]`, respectively, with `mvLX` and `refIdxLX` being the arrays `mvLX` and `refIdxLX`, respectively, that are input to this clause. + +- k) In clause 8.4.1.2.1, any occurrence of `RefPicList1[ 0 ]` is replaced by `refPicList1[ 0 ]` with `refPicList1[ 0 ]` being the first layer field (when `field_pic_flag` is equal to 1) or the first layer frame or layer complementary field pair (when `field_pic_flag` is equal to 0) in the reference picture list `refPicList1` that is specified as input to this clause. The reference picture list `refPicList1` is a reference list of layer pictures that correspond to layer representations with `DQId` equal to 0 of previously decoded access units. +- l) In clause 8.4.1.2.1, the current picture `CurrPic` represents the current layer picture with `DQId` equal to 0 and the variable `colPic` specifies the layer picture, for the layer representation with `DQId` equal to 0, that contains the co-located macroblock as specified in Table 8-6. +- m) In clause 8.4.1.2.1, all picture order count values are picture order count value for the dependency representation with `dependency_id` equal to 0. +- n) In clause 8.4.1.2.1, the modification b) specified in clause F.8.2 applies with `currDependencyId` being equal to 0. +- o) In clause 8.4.1.2.1, for deriving the variable `fieldDecodingFlagX`, the macroblock `mbAddrX` is treated as field macroblock when `fieldMbColPicFlag[ mbAddrX ]` is equal to 1, it is treated as frame macroblock when `fieldMbColPicFlag[ mbAddrX ]` is equal to 0. The array `fieldMbColPicFlag` specifies the array `fieldMbFlag` that was derived by the process in clause F.8.1.5.1 for the layer representation with `DQId` equal to 0. +- p) In clause 8.4.1.2.1, the variables `PredFlagL0`, `PredFlagL1`, `RefIdxL0`, `RefIdxL1`, `MvL0`, and `MvL1` for the macroblock `mbAddrCol` inside the picture `colPic` are replaced with the `predFlagL0[ mbAddrCol ]`, `predFlagL1[ mbAddrCol ]`, `refIdxL0[ mbAddrCol ]`, `refIdxL1[ mbAddrCol ]`, `mvL0[ mbAddrCol ]`, and `mvL1[ mbAddrCol ]`, respectively, that have been derived for the layer picture `colPic` that is associated with `DQId` equal to 0. +- q) In clause 8.4.1.2.1, the macroblock `mbAddrCol` is interpreted as coded in an Intra macroblock prediction mode when `mbType[ mbAddrCol ]` that has been derived for the layer picture `colPic` that is associated with `DQId` equal to 0 is equal to `I_16x16`, `I_8x8`, `I_4x4`, or `I_PCM`. +- r) In clause 8.4.1.2.1, the syntax element `mb_type` of the macroblock with address `mbAddrCol` inside the picture `colPic` is replaced with `mbType[ mbAddrCol ]` that has been derived for the layer picture `colPic` that is associated with `DQId` equal to 0 and the syntax element `list sub_mb_type` of the macroblock with address `mbAddrCol` inside the picture `colPic` is replaced with the list `subMbType[ mbAddrCol ]` that has been derived for the layer picture `colPic` that is associated with `DQId` equal to 0. +- s) In clause 8.4.1.2.2, the co-located macroblock is treated as field macroblock when `fieldMbColPicFlag[ mbAddrCol ]` is equal to 1, it is treated as frame macroblock when `fieldMbColPicFlag[ mbAddrCol ]` is equal to 0. The array `fieldMbColPicFlag` specifies the array `fieldMbFlag` that was derived by the process in clause F.8.1.5.1 for the layer representation with `DQId` equal to 0. The macroblock address `mbAddrCol` is the macroblock address of the co-located macroblock as derived in clause 8.4.1.2.1. + +The reference index predictors `refIdxPredL0` and `refIdxPredL1`, the motion vector predictors `mvPredL0` and `mvPredL1`, and the variable `mvCntInc` are derived as follows: + +- If `mbType[ CurrMbAddr ]` is equal to `P_Skip`, the reference index predictor `refIdxPredL1` is set equal to `-1`, both components of the motion vector predictor `mvPredL1` are set equal to 0, the variable `mvCntInc` is set equal to 1, and the derivation process for luma motion vectors for skipped macroblocks in P slices as specified in clause 8.4.1.1 is invoked with the outputs being assigned to the motion vector predictor `mvPredL0` and the reference index predictor `refIdxPredL0`. For this invocation of the process in clause 8.4.1.1, the modifications specified above in items a) through j) of this clause apply. +- Otherwise, if `isDirectFlag` is equal to 1 and `DQId` is equal to 0 (`nal_unit_type` is not equal to 20), the derivation process for spatial direct luma motion vector and reference index prediction mode as specified in clause 8.4.1.2.2 is invoked with `mbPartIdx` and `subMbPartIdx` as the inputs and the output variables `refIdxL0`, `refIdxL1`, `mvL0`, `mvL1`, and `subMvCnt` are assigned to the reference index predictors `refIdxPredL0` and `refIdxPredL1`, the motion vectors predictors `mvPredL0` and `mvPredL1`, and the variable `mvCntInc`, respectively. For this invocation of the process in clause 8.4.1.2.2, the modifications specified above in items a) through s) of this clause apply. + +NOTE – When the current clause is invoked, `direct_spatial_mv_pred_flag` is always equal to 1. + +- Otherwise, if `isDirectFlag` is equal to 1 (and `DQId` is greater than 0 and `nal_unit_type` is equal to 20), the SVC derivation process for luma motion vectors and reference indices for `B_Skip`, `B_Direct_16x16`, and `B_Direct_8x8` in NAL units with `nal_unit_type` equal to 20 as specified in clause F.8.4.1.2 is invoked with `mbPartIdx`, `fieldMbFlag`, + +mbType, subMbType, predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, and mvL1 as the inputs and the outputs are refIdxPredL0, refIdxPredL1, mvPredL0, mvPredL1, and mvCntInc. + +- Otherwise, the variable mvCntInc is initially set equal to 0, and for X being replaced by 0 and 1, the following applies: + - If any of the following conditions are true, refIdxPredLX is set equal to -1 and both components of mvPredLX are set equal to 0: + - mbType[ CurrMbAddr ] is not equal to P\_8x8, P\_8x8ref0, or B\_8x8 and MbPartPredMode( mbType[ CurrMbAddr ], mbPartIdx ) is not equal to Pred\_LX or BiPred, + - mbType[ CurrMbAddr ] is equal to P\_8x8, P\_8x8ref0, or B\_8x8 and SubMbPartPredMode( subMbType[ CurrMbAddr ][ mbPartIdx ] ) is not equal to Pred\_LX or BiPred. + - Otherwise, if base\_mode\_flag is equal to 1 or motion\_prediction\_flag\_IX[ mbPartIdx ] is equal to 1, the following ordered steps are specified: + 1. The inverse macroblock partition scanning process as specified in clause 6.4.2.1 is invoked with mbPartIdx as the input and the output is assigned to ( xP, yP ). For this invocation of the process in clause 6.4.2.1, the modification specified above in item d) of this clause applies. + 2. Inverse sub-macroblock partition scanning process as specified in clause 6.4.2.2 is invoked with mbPartIdx and subMbPartIdx as the inputs and the output is assigned to ( xS, yS ). For this invocation of the process in clause 6.4.2.2, the modifications specified above in items d) and e) of this clause apply. + 3. The reference index predictor refIdxPredLX and the motion vector predictor mvPredLX are derived by + +$$\begin{aligned} \text{refIdxPredLX} &= \text{refIdxILPredLX}[ ( xP + xS ) / 8, ( yP + yS ) / 8 ] \\ \text{mvPredLX}[ c ] &= \text{mvILPredLX}[ ( xP + xS ) / 4, ( yP + yS ) / 4 ][ c ] \quad \text{with } c = 0..1 \end{aligned} \quad (\text{F-95})$$ + +The bitstream shall not contain data that result in refIdxPredLX less than 0 or refIdxPredLX greater than num\_ref\_idx\_active\_IX\_minus1. + +The bitstream shall not contain data that result in horizontal motion vector components mvPredLX[ 0 ] or vertical motion vector components mvPredLX[ 1 ] that exceed the range for motion vector components specified in clause F.10.2. + +4. mvCntInc is set equal to (mvCntInc + 1). +- Otherwise, the following ordered steps are specified: + 1. Depending on mbType[ CurrMbAddr ], the reference index predictor refIdxPredLX is derived as follows: + - If mbType[ CurrMbAddr ] is equal to P\_8x8ref0, refIdxPredLX is set equal to 0. + - Otherwise (mbType[ CurrMbAddr ] is not equal to P\_8x8ref0), refIdxPredLX is set equal to ref\_idx\_IX[ mbPartIdx ]. + 2. The derivation process for luma motion vector prediction as specified in clause 8.4.1.3 is invoked with mbPartIdx, subMbPartIdx, refIdxPredLX, and currSubMbType set equal to subMbType[ CurrMbAddr ][ mbPartIdx ] as the inputs and the output is assigned to mvPredLX. For this invocation of the process in clause 8.4.1.3, the modifications specified in items a) through j) of this clause apply + 3. mvCntInc is set equal to (mvCntInc + 1). + +For X being replaced by 0 and 1, the arrays refIdxLX, predFlagLX, and mvLX are modified by applying the following ordered steps: + +1. When subMbPartIdx is equal to 0, the arrays refIdxLX and predFlagLX are modified by + +$$\text{refIdxLX}[ \text{CurrMbAddr} ][ \text{mbPartIdx} ] = \text{refIdxPredLX} \quad (\text{F-96})$$ + +$$\text{predFlagLX}[ \text{CurrMbAddr} ][ \text{mbPartIdx} ] = ( ( \text{refIdxPredLX} < 0 ) ? 0 : 1 ) \quad (\text{F-97})$$ + +2. The array mvLX is modified by + +$$mvLX[ CurrMbAddr ][ mbPartIdx ][ subMbPartIdx ][ c ] = mvPredLX[ c ] \quad \text{with } c = 0..1 \quad (F-98)$$ + +3. When $predFlagLX[ CurrMbAddr ][ mbPartIdx ]$ is equal to 1, $base\_mode\_flag$ is equal to 0, $isDirectFlag$ is equal to 0, and $mbType[ CurrMbAddr ]$ is not equal to $P\_Skip$ , the array $mvLX$ is modified by + +$$mvLX[ CurrMbAddr ][ mbPartIdx ][ subMbPartIdx ][ c ] += mvd\_LX[ mbPartIdx ][ subMbPartIdx ][ c ] \quad \text{with } c = 0..1 \quad (F-99)$$ + +The array $mvCnt$ is modified as follows: + +- If $mbPartIdx$ is equal to 0 and $subMbPartIdx$ is equal to 0, $mvCnt[ CurrMbAddr ]$ is set equal to $mvCntInc$ . +- Otherwise ( $mbPartIdx$ is greater than 0 or $subMbPartIdx$ is greater than 0), the array $mvCnt$ is modified by + +$$mvCnt[ CurrMbAddr ] += mvCntInc \quad (F-100)$$ + +#### F.8.4.1.2 SVC derivation process for luma motion vectors and reference indices for B\_Skip, B\_Direct\_16x16, and B\_Direct\_8x8 in NAL units with nal\_unit\_type equal to 20 + +Inputs to this process are: + +- a variable $mbPartIdx$ specifying the current macroblock partition, +- a one-dimensional array $fieldMbFlag$ with $PicSizeInMbs$ elements specifying which macroblocks of the current layer representation are coded as field macroblocks and which macroblocks are coded as frame macroblocks, +- a one-dimensional array $mbType$ with $PicSizeInMbs$ elements specifying macroblock types for the macroblocks of the current layer representation, +- a $(PicSizeInMbs) \times 4$ array $subMbType$ specifying sub-macroblock types for the macroblocks of the current layer representation, +- two $(PicSizeInMbs) \times 4$ arrays $predFlagL0$ and $predFlagL1$ specifying prediction utilization flags for the macroblocks of the current layer representation, +- two $(PicSizeInMbs) \times 4$ arrays $refIdxL0$ and $refIdxL1$ specifying reference indices for the macroblocks of the current layer representation, +- two $(PicSizeInMbs) \times 4 \times 4 \times 2$ arrays $mvL0$ and $mvL1$ specifying motion vector components for the macroblocks of the current layer representation. + +Outputs of this process are: + +- the reference index predictors $refIdxPredL0$ and $refIdxPredL1$ , +- the motion vector predictors $mvPredL0$ and $mvPredL1$ , +- the variable $mvCntInc$ . + +The variable $currSubMbType$ is derived as follows: + +- If $mbType[ CurrMbAddr ]$ is equal to $B\_Skip$ or $B\_Direct\_16 \times 16$ , $currSubMbType$ is marked as "unspecified". +- Otherwise ( $mbType[ CurrMbAddr ]$ is equal to $B\_8 \times 8$ and $subMbType[ CurrMbAddr ][ mbPartIdx ]$ is equal to $B\_Direct\_8 \times 8$ ), $currSubMbType$ is set equal to $B\_Bi\_8 \times 8$ . + +NOTE – The variable $currSubMbType$ is only used for deriving the variable $predPartWidth$ in clause 6.4.11.7, which specifies the partition width of the current macroblock or sub-macroblock partition for determining neighbouring partitions that are used for motion vector prediction. Inside clause 6.4.11.7, the variable $predPartWidth$ is set equal to 16 when the current macroblock is coded with macroblock type equal to $B\_Skip$ or $B\_Direct\_16 \times 16$ or the current sub-macroblock is coded with sub-macroblock type equal to $B\_Direct\_8 \times 8$ . When the current clause is invoked for a sub-macroblock coded with sub-macroblock type equal to $B\_Direct\_8 \times 8$ (the current clause is only invoked for NAL units with $nal\_unit\_type$ equal to 20), $currSubMbType$ is set equal to $B\_Bi\_8 \times 8$ in order to set the variable $predPartWidth$ equal to 8 in clause 6.4.11.7. + +For $X$ being replaced by 0 and 1, the reference index predictor $refIdxPredLX$ is derived by applying the following ordered steps: + +1. The derivation process for motion data of neighbouring partitions as specified in clause 8.4.1.3.2 is invoked with $mbPartIdx$ , $subMbPartIdx$ set equal to 0, $currSubMbType$ , and $listSuffixFlag$ set equal to $X$ as the inputs and the outputs are the reference indices $refIdxLXN$ with $N$ being replaced by $A$ , $B$ , and $C$ . For this invocation of the process in clause 8.4.1.3.2, the modifications specified in items a) through j) of clause F.8.4.1.1 apply. + +2. The reference index predictor `refIdxPredLX` is derived by + +$$\text{refIdxPredLX} = \text{MinPositive}(\text{refIdxLXA}, \text{MinPositive}(\text{refIdxLXB}, \text{refIdxLXC})) \quad (\text{F-101})$$ + +with + +$$\text{MinPositive}(x, y) = \begin{cases} \text{Min}(x, y) & \text{if } x \geq 0 \text{ and } y \geq 0 \\ \text{Max}(x, y) & \text{otherwise} \end{cases} \quad (\text{F-102})$$ + +When both reference index predictors `refIdxPredL0` and `refIdxPredL1` are less than 0, `refIdxPredL0` and `refIdxPredL1` are set equal to 0. + +For X being replaced by 0 and 1, the motion vector predictor `mvPredLX` is derived as follows: + +- If `refIdxPredLX` is greater than or equal to 0, the derivation process for luma motion vector prediction as specified in clause 8.4.1.3 is invoked with `mbPartIdx`, `subMbPartIdx` set equal to 0, `refIdxPredLX`, and `currSubMbType` as the inputs and the output is assigned to `mvPredLX`. For this invocation of the process in clause 8.4.1.3, the modifications specified in items a) through j) of clause F.8.4.1.1 apply. +- Otherwise, both components of the motion vector `mvPredLX` are set equal to 0. + +The variable `mvCntInc` is derived as specified by the following ordered steps: + +1. `mvCntInc` is set equal to 0 +2. When `refIdxPredL0` is greater than or equal to 0, `mvCntInc` is set equal to $(\text{mvCntInc} + 1)$ . +3. When `refIdxPredL1` is greater than or equal to 0, `mvCntInc` is set equal to $(\text{mvCntInc} + 1)$ . + +#### F.8.4.2 SVC decoding process for Inter prediction samples + +Inputs to this process are: + +- a variable `targetQId` specifying the `quality_id` value for the target layer representation, +- a variable `fieldMbFlag` specifying whether the current macroblock is a field or a frame macroblock, +- a variable `sliceIdc` specifying the slice identification for the current macroblock, +- a variable `mbType` specifying the macroblock type for the current macroblock, +- a list `subMbType` with 4 elements specifying the sub-macroblock types for the current macroblock, +- two lists `predFlagL0` and `predFlagL1` with 4 elements specifying prediction utilization flags for the current macroblock, +- two lists `refIdxL0` and `refIdxL1` with 4 elements specifying reference indices for the current macroblock, +- two $4 \times 4 \times 2$ arrays `mvL0` and `mvL1` specifying motion vectors components for the current macroblock, +- when present, a one-dimensional array `refLayerFieldMbFlag` with `RefLayerPicSizeInMbs` elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- when present, a one-dimensional array `refLayerMbType` with `RefLayerPicSizeInMbs` elements specifying macroblock types for the macroblocks of the reference layer representation, +- the reference picture lists `refPicList0` and `refPicList1` (when available), +- a $(\text{PicWidthInSamples}_L) \times (\text{PicHeightInSamples}_L)$ array `picSamplesL` of luma sample values, +- a $(\text{PicWidthInSamples}_L) \times (\text{PicHeightInSamples}_L)$ array `picResL` of residual luma sample values, +- when `ChromaArrayType` is not equal to 0, two $(\text{PicWidthInSamples}_C) \times (\text{PicHeightInSamples}_C)$ arrays `picSamplesCb` and `picSamplesCr` of chroma sample values, +- when `ChromaArrayType` is not equal to 0, two $(\text{PicWidthInSamples}_C) \times (\text{PicHeightInSamples}_C)$ arrays `picResCb` and `picResCr` of residual chroma sample values. + +Outputs of this process are: + +- a modified version of the array of luma sample values `picSamplesL`, + +- a modified version of the array of residual luma sample values $\text{picRes}_L$ , +- when $\text{ChromaArrayType}$ is not equal to 0, modified versions of the two arrays of chroma sample values $\text{picSamples}_{Cb}$ and $\text{picSamples}_{Cr}$ , +- when $\text{ChromaArrayType}$ is not equal to 0, modified versions of the two arrays of residual chroma sample values $\text{picRes}_{Cb}$ and $\text{picRes}_{Cr}$ . + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the current macroblock, which is the macroblock with address $\text{CurrMbAddr}$ inside the layer representation with $\text{DQId}$ equal to $(\text{sliceIdc} \& 127)$ , the slice header of the current slice, which is the slice that contains the current macroblock, the current picture parameter, which is identified by the syntax element $\text{pic\_parameter\_set\_id}$ inside the slice header of the current slice, and the current sequence parameter, which is identified by the syntax element $\text{seq\_parameter\_set\_id}$ inside the current picture parameter set. + +For all processes specified in clauses 6 or 8 that are invoked from the process specified in this clause or a child process of the process specified in this clause, the following modifications apply: + +- In clauses 8.4.3, 8.4.1.4, and 8.4.2.1, the current macroblock is treated as field macroblock when $\text{fieldMbFlag}$ is equal to 1, and it is treated as frame macroblock when $\text{fieldMbFlag}$ is equal to 0. When $\text{field\_pic\_flag}$ is equal to 0 and the current macroblock $\text{CurrMbAddr}$ is a field macroblock, its parity is equal to top when $(\text{CurrMbAddr} \% 2)$ is equal to 0 and its parity is equal to bottom when $(\text{CurrMbAddr} \% 2)$ is equal to 1. +- In clauses 8.4.3 and 8.4.2.1, any occurrence of $\text{RefPicList0}$ or $\text{RefPicList1}$ is replaced with $\text{refPicList0}$ or $\text{refPicList1}$ , respectively, with $\text{refPicList0}$ and $\text{refPicList1}$ being the reference picture lists specified as inputs to this clause. +- In clause 8.4.1.4, the reference picture referred by $\text{refIdxLX}$ is specified by $\text{refPicListX}[\text{refIdxLX}]$ with $\text{refPicList0}$ and $\text{refPicList1}$ specified as inputs to this clause. +- In clauses 8.4.2.2.1 and 8.4.2.2.2, any occurrence of $\text{mb\_field\_decoding\_flag}$ is replaced by $\text{fieldMbFlag}$ . +- Decoded pictures are represented by the sample arrays $S_L$ and, when $\text{ChromaArrayType}$ is not equal to 0, $S_{Cb}$ and $S_{Cr}$ , reference base pictures are represented by the sample arrays $B_L$ and, when $\text{ChromaArrayType}$ is not equal to 0, $B_{Cb}$ and $B_{Cr}$ . When reference base pictures are referenced in the inter prediction process via clause 8.4.2.1, the samples arrays $B_L$ , $B_{Cb}$ , and $B_{Cr}$ are referred to as $S_L$ , $S_{Cb}$ , and $S_{Cr}$ , respectively. The sample arrays $S_L$ , $S_{Cb}$ , $S_{Cr}$ , $B_L$ , $B_{Cb}$ , and $B_{Cr}$ that referenced in the inter prediction process via clause 8.4.2.1 are constructed as specified in clause F.8. + +Let $\text{predMb}_L$ be a 16x16 array of luma prediction samples for the macroblock $\text{mbAddr}$ . + +When $\text{ChromaArrayType}$ is not equal to 0, let $\text{predMb}_{Cb}$ and $\text{predMb}_{Cr}$ be two $(\text{MbWidthC}) \times (\text{MbHeightC})$ arrays of chroma prediction samples for the macroblock $\text{mbAddr}$ . + +The variable $\text{numMbPart}$ is derived as follows: + +- If $\text{mbType}$ is equal to $\text{B\_Skip}$ or $\text{B\_Direct\_16x16}$ and $\text{DQId}$ is equal to 0 ( $\text{nal\_unit\_type}$ is not equal to 20), $\text{numMbPart}$ is set equal to 4. +- Otherwise, if $\text{mbType}$ is equal to $\text{B\_Skip}$ or $\text{B\_Direct\_16x16}$ (and $\text{DQId}$ is greater than 0 and $\text{nal\_unit\_type}$ is equal to 20), $\text{numMbPart}$ is set equal to 1. +- Otherwise ( $\text{mbType}$ is not equal to $\text{B\_Skip}$ or $\text{B\_Direct\_16x16}$ ), $\text{numMbPart}$ is set equal to $\text{NumMbPart}(\text{mbType})$ . + +The macroblock partition index $\text{mbPartIdx}$ proceeds over the values $0..(\text{numMbPart} - 1)$ , and for each value of $\text{mbPartIdx}$ the following ordered steps are specified: + +- The variable $\text{isDirectFlag}$ is derived as follows: + - If any of the following conditions are true, $\text{isDirectFlag}$ is set equal to 1: + - $\text{mbType}$ is equal to $\text{B\_Skip}$ or $\text{B\_Direct\_16x16}$ , + - $\text{mbType}$ is equal to $\text{B\_8x8}$ and $\text{subMbType}[\text{mbPartIdx}]$ is equal to $\text{B\_Direct\_8x8}$ . + - Otherwise, $\text{isDirectFlag}$ is set equal to 0. +- The variables $\text{implicitModeFlag}$ and $\text{explicitModeFlag}$ are derived as follows: + +- If weighted\_bipred\_idc is equal to 2, (slice\_type % 5) is equal to 1, predFlagL0[ mbPartIdx ] is equal to 1, and predFlagL1[ mbPartIdx ] is equal to 1, implicitModeFlag is set equal to 1 and explicitModeFlag is set equal to 0. + - Otherwise, if weighted\_bipred\_idc is equal to 1, (slice\_type % 5) is equal to 1, and predFlagL0[ mbPartIdx ] + predFlagL1[ mbPartIdx ] is equal to 1 or 2, implicitModeFlag is set equal to 0 and explicitModeFlag is set equal to 1. + - Otherwise, if weighted\_pred\_flag is equal to 1, (slice\_type % 5) is equal to 0, and predFlagL0[ mbPartIdx ] is equal to 1, implicitModeFlag is set equal to 0 and explicitModeFlag is set equal to 1. + - Otherwise, implicitModeFlag is set equal to 0 and explicitModeFlag is set equal to 0. +3. When implicitModeFlag is equal to 1 or explicitModeFlag is equal to 1, the SVC derivation process for prediction weights as specified in clause F.8.4.2.1 is invoked with fieldMbFlag, refIdxL0[ mbPartIdx ], refIdxL1[ mbPartIdx ], predFlagL0[ mbPartIdx ], predFlagL1[ mbPartIdx ], refPicList0, and refPicList1 (when available) as inputs and the outputs are assigned to logWDL, w0L, w1L, o0L, o1L, and when ChromaArrayType is not equal to 0, logWDC, w0C, w1C, o0C, o1C with C being replaced by Cb and Cr. +4. The luma location ( xP, yP ) is derived as follows: +- If mbType is equal to B\_Skip or B\_Direct\_16x16, xP is set equal to (8 \* ( mbPartIdx % 2 )) and yP is set equal to (8 \* ( mbPartIdx / 2 )). + - Otherwise (mbType is not equal to B\_Skip or B\_Direct\_16x16), the inverse macroblock partition scanning process as specified in clause 6.4.2.1 is invoked with mbPartIdx as the input and the output is assigned to ( xP, yP ). For this invocation of the process in clause 6.4.2.1, any occurrence of mb\_type is replaced by mbType. +5. The variable numSubMbPart is derived as follows: +- If isDirectFlag is equal to 1 and DQId is equal to 0 (nal\_unit\_type is not equal to 20), numSubMbPart is set equal to 4. + - Otherwise, if isDirectFlag is equal to 1 (and DQId is greater than 0 and nal\_unit\_type is equal to 20), numSubMbPart is set equal to 1. + - Otherwise (isDirectFlag is equal to 0), numSubMbPart is set equal to NumSubMbPart( subMbType[ mbPartIdx ] ) +6. The sub-macroblock partition index proceeds over values 0..(numSubMbPart – 1), and for each value of subMbPartIdx the following ordered steps are specified: +- a. The variables partWidth and partHeight are derived as follows: +- If isDirectFlag is equal to 1 and DQId is equal to 0 (nal\_unit\_type is not equal to 20), partWidth and partHeight are set equal to 4. + - Otherwise, if isDirectFlag is equal to 1 (and DQId is greater than 0 and nal\_unit\_type is equal to 20), the following applies: + - If mbType is equal to B\_Skip or B\_Direct\_16x16, partWidth and partHeight are set equal to 16. + - Otherwise (mbType is equal to B\_8x8 and subMbType[ mbPartIdx ] is equal to B\_Direct\_8x8), partWidth and partHeight are set equal to 8. + - Otherwise (isDirectFlag is equal to 0), the following applies: + - If mbType is not equal to P\_8x8, P\_8x8ref0, or B\_8x8, partWidth and partHeight are derived by +$$\text{partWidth} = \text{MbPartWidth}(\text{mbType}) \quad (\text{F-103})$$ + +$$\text{partHeight} = \text{MbPartHeight}(\text{mbType}) \quad (\text{F-104})$$ + - Otherwise (mbType is equal to P\_8x8, P\_8x8ref0, or B\_8x8), partWidth and partHeight are derived by +$$\text{partWidth} = \text{SubMbPartWidth}(\text{subMbType}[\text{mbPartIdx}]) \quad (\text{F-105})$$ + +$$\text{partHeight} = \text{SubMbPartHeight}(\text{subMbType}[\text{mbPartIdx}]) \quad (\text{F-106})$$ +- b. When ChromaArrayType is not equal to 0, the variables partWidthC and partHeightC are derived by +- $$\text{partWidthC} = \text{partWidth} / \text{SubWidthC} \quad (\text{F-107})$$ +- $$\text{partHeightC} = \text{partHeight} / \text{SubWidthC} \quad (\text{F-108})$$ + +- c. For X being replaced by 0 and 1, when ChromaArrayType is not equal to 0 and predFlagLX[ mbPartIdx ] is equal to 1, the derivation process for chroma motion vectors as specified in clause 8.4.1.4 is invoked with mvLX[ mbPartIdx ][ subMbPartIdx ] and refIdxLX[ mbPartIdx ] as the inputs and the output is the chroma motion vector mvCLX. For this invocation of the process in clause 8.4.1.4, the modifications specified above in items a) and c) of this clause apply. +- d. The decoding process for Inter prediction samples as specified in clause 8.4.2 is invoked with mbPartIdx, subMbPartIdx, partWidth and partHeight, partWidthC and partHeightC (if available), luma motion vectors mvL0[ mbPartIdx ][ subMbPartIdx ] and mvL1[ mbPartIdx ][ subMbPartIdx ], chroma motion vectors mvCL0 and mvCL1 (if available), reference indices refIdxL0[ mbPartIdx ] and refIdxL1[ mbPartIdx ], prediction utilization flags predFlagL0[ mbPartIdx ] and predFlagL1[ mbPartIdx ] as well as variables for weighted prediction logWDL, w0L, w1L, o0L, o1L, and when ChromaArrayType is not equal to 0, logWDC, w0C, w1C, o0C, o1C (with C being replaced by Cb and Cr) as the inputs and the outputs are a (partWidth)x(partHeight) array predPartL of luma prediction samples and, when ChromaArrayType is not equal to 0, two (partWidthC)x(partHeightC) arrays predPartCb and predPartCr of chroma prediction samples. For this invocation of the process in clause 8.4.2, the modifications specified above in items a), b), d), and e) of this clause apply. +- e. The luma location ( xS, yS ) is derived as follows: + - If mbType is equal to B\_8x8 and subMbType[ mbPartIdx ] is equal to B\_Direct\_8x8, xS is set equal to ( 4 \* ( subMbPartIdx % 2 ) ) and yS is set equal to ( 4 \* ( subMbPartIdx / 2 ) ). + - Otherwise (mbType is not equal to B\_8x8 or subMbType[ mbPartIdx ] is not equal to B\_Direct\_8x8), the inverse sub-macroblock partition scanning process as specified in clause 6.4.2.2 is invoked with mbPartIdx and subMbPartIdx as the inputs and the output is assigned to ( xS, yS ). For this invocation of the process in clause 6.4.2.2, any occurrence of mb\_type is replaced by mbType and any occurrence of sub\_mb\_type is replaced by subMbType. +- f. For x = 0..(partWidth – 1) and y = 0..(partHeight – 1), the 16x16 array predMbL is modified by +$$\text{predMb}_L[ xP + xS + x, yP + yS + y ] = \text{predPart}_L[ x, y ] \quad (\text{F-109})$$ +- g. When ChromaArrayType is not equal to 0, for x = 0..(partWidthC – 1) and y = 0..(partHeightC – 1), the (MbWidthC)x(MbHeightC) arrays predMbCb and predMbCr are modified by +$$\text{predMb}_{C_b}[ ( xP + xS ) / \text{SubWidthC} + x, ( yP + yS ) / \text{SubHeightC} + y ] = \text{predPart}_{C_b}[ x, y ] \quad (\text{F-110})$$ + +$$\text{predMb}_{C_r}[ ( xP + xS ) / \text{SubWidthC} + x, ( yP + yS ) / \text{SubHeightC} + y ] = \text{predPart}_{C_r}[ x, y ] \quad (\text{F-111})$$ + +When targetQId is equal to 0, base\_mode\_flag is equal to 1, MbaffFrameFlag is equal to 0, RefLayerMbaffFrameFlag is equal to 0, and RestrictedSpatialResolutionChangeFlag is equal to 0, the intra-inter prediction combination process specified in clause F.8.4.2.2 is invoked with fieldMbFlag, refLayerFieldMbFlag, refLayerMbType, predMbL, picSamplesL, picResL, and, when ChromaArrayType is not equal to 0, predMbCb, predMbCr, picSamplesCb, picSamplesCr, picResCb, and picResCr as the inputs, and the outputs are modified versions of predMbL and picResL, and, when ChromaArrayType is not equal to 0, modified versions of predMbCb, predMbCr, picResCb, and picResCr. + +The picture sample array construction process as specified in clause F.8.5.4.1 is invoked with fieldMbFlag, predMbL, picSamplesL, and, when ChromaArrayType is not equal to 0, predMbCb, predMbCr, picSamplesCb, and picSamplesCr as the inputs and the outputs are a modified version of picSamplesL and, when ChromaArrayType is not equal to 0, modified versions of picSamplesCb, and picSamplesCr. + +#### F.8.4.2.1 SVC derivation process for prediction weights + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- the reference indices refIdxL0 and refIdxL1 for the current macroblock partition, +- the prediction list utilization flags predFlagL0 and predFlagL1 for the current macroblock partition, +- the reference picture lists refPicList0 and refPicList1 (when available). + +Outputs of this process are: + +- variables for weighted prediction of luma samples logWDL, w0L, w1L, o0L, o1L, +- when ChromaArrayType is not equal to 0 (monochrome), variables for weighted prediction of chroma samples logWDC, w0C, w1C, o0C, o1C with C being replaced by Cb and Cr. + +Depending on base\_pred\_weight\_table\_flag, the following applies: + +- If `base_pred_weight_table_flag` is equal to 0, the derivation process for prediction weights as specified in clause 8.4.3 is invoked with `refIdxL0`, `refIdxL1`, `predFlagL0`, and `predFlagL1` as inputs and the outputs are assigned to `logWDL`, `w0L`, `w1L`, `o0L`, `o1L`, and when `ChromaArrayType` is not equal to 0, `logWDC`, `w0C`, `w1C`, `o0C`, `o1C` with C being replaced by Cb and Cr. For this invocation of the process in clause 8.4.3, the modifications specified in items a) and b) of clause F.8.4.2 apply. +- Otherwise (`base_pred_weight_table_flag` is equal to 1), for X being replaced by 0 and 1, the following ordered steps are specified: + +1. Let `dqIdList` be the list of DQId values that is derived by invoking the derivation process for the set of layer representations required for decoding as specified in clause F.8.1.1. Let `baseDQId` be the largest value `dqId`, inside the list `dqIdList`, that has the following properties: a) `dqId` is less than the current value of `DQId`; b) the slices of the layer representation with `DQId` equal to `dqId` have `base_pred_weight_table_flag` equal to 0. +2. Let `baseSlice` be any slice of the layer representation with `DQId` equal to `baseDQId`. +3. Let `refLayerLumaLogWD`, `aRefLayerLumaWeightLX[]`, and `aRefLayerLumaOffsetLX[]` be variables that are set equal to the values of the syntax elements `luma_log2_weight_denom`, `luma_weight_IX[]`, and `luma_offset_IX[]`, respectively, of `baseSlice`. +4. When `ChromaArrayType` is not equal to 0, let `refLayerChromaLogWD`, `aRefLayerChromaWeightLX[][]`, and `aRefLayerChromaOffsetLX[][]` be variables that are set equal to the values of the syntax elements `chroma_log2_weight_denom`, `chroma_weight_IX[]`, and `chroma_offset_IX[]`, respectively, of `baseSlice`. +5. The variable `refIdxLXWP` is derived as follows: + +- If `MbaffFrame` is equal to 1 and `fieldMbFlag` is equal to 1, + +$$\text{refIdxLXWP} = \text{refIdxLX} \gg 1 \quad (\text{F-112})$$ + +- Otherwise (`MbaffFrameFlag` is equal to 0 or `fieldMbFlag` is equal to 0), + +$$\text{refIdxLXWP} = \text{refIdxLX} \quad (\text{F-113})$$ + +6. The variables `logWDL`, `wXL`, `oXL` are derived by: + +$$\text{logWDL} = \text{refLayerLumaLogWD} \quad (\text{F-114})$$ + +$$\text{w}_{\text{XL}} = \text{aRefLayerLumaWeightLX}[\text{refIdxLXWP}] \quad (\text{F-115})$$ + +$$\text{o}_{\text{XL}} = \text{aRefLayerLumaOffsetLX}[\text{refIdxLXWP}] * ( 1 \ll ( \text{BitDepth}_Y - 8 ) ) \quad (\text{F-116})$$ + +7. When `ChromaArrayType` is not equal to 0, the variables `logWDC`, `wXC`, `oXC` (with C being replaced by Cb and Cr and `iCbCr = 0` for Cb and `iCbCr = 1` for Cr) are derived by: + +$$\text{logWDC} = \text{refLayerChromaLogWD} \quad (\text{F-117})$$ + +$$\text{w}_{\text{XC}} = \text{aRefLayerChromaWeightLX}[\text{refIdxLXWP}][\text{iCbCr}] \quad (\text{F-118})$$ + +$$\text{o}_{\text{XC}} = \text{aRefLayerChromaOffsetLX}[\text{refIdxLXWP}][\text{iCbCr}] * ( 1 \ll ( \text{BitDepth}_C - 8 ) ) \quad (\text{F-119})$$ + +8. When `predFlagL0` and `predFlagL1` are equal to 1, the following constraint shall be obeyed for C equal to L and, when `ChromaArrayType` is not equal to 0, Cb and Cr + +$$-128 \leq w_{0C} + w_{1C} \leq ( ( \text{logWDC} == 7 ) ? 127 : 128 ) \quad (\text{F-120})$$ + +#### F.8.4.2.2 Intra-inter prediction combination process + +Inputs to this process are: + +- a variable `fieldMbFlag` specifying whether the current macroblock is a field or a frame macroblock, +- a one-dimensional array `refLayerFieldMbFlag` with `RefLayerPicSizeInMbs` elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array `refLayerMbType` with `RefLayerPicSizeInMbs` elements specifying macroblock types for the macroblocks of the reference layer representation, +- a 16x16 array `predMbL` of luma inter prediction samples for the current macroblock, +- a $(\text{PicWidthInSamples}_L) \times (\text{PicHeightInSamples}_L)$ array `picSamplesL` of luma sample values, +- a $(\text{PicWidthInSamples}_L) \times (\text{PicHeightInSamples}_L)$ array `picResL` of residual luma sample values, + +- when ChromaArrayType is not equal to 0, two (MbWidthC)x(MbHeightC) arrays predMbCb and predMbCr of chroma prediction samples for the macroblock mbAddr, +- when ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picSamplesCb and picSamplesCr of chroma sample values, +- when ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picResCb and picResCr of residual chroma sample values. + +Outputs of this process are: + +- a modified version of the array predMbL of luma prediction samples for the macroblock mbAddr, +- a modified version of the array picResL of residual luma sample values, +- when ChromaArrayType is not equal to 0, modified versions of the two arrays predMbCb and predMbCr of chroma prediction samples for the macroblock mbAddr, +- when ChromaArrayType is not equal to 0, modified versions of the two arrays picResCb and picResCr of residual chroma sample values. + +Let predMbTempL be a 16x16 array and, when ChromaArrayType is not equal to 0, let predMbTempCb and predMbTempCr be two (MbWidthC)x(MbHeightC) arrays. The macroblock sample array extraction process as specified in clause F.8.5.4.2 is invoked with fieldMbFlag, picSamplesL, and when ChromaArrayType is not equal to 0, picSamplesCb and picSamplesCr as the inputs and the outputs are assigned to predMbTempL, and when ChromaArrayType is not equal to 0, predMbTempCb and predMbTempCr. + +Let resMbL be a 16x16 array and, when ChromaArrayType is not equal to 0, let resMbCb and resMbCr be two (MbWidthC)x(MbHeightC) arrays. The macroblock sample array extraction process as specified in clause F.8.5.4.2 is invoked with fieldMbFlag, picResL, and, when ChromaArrayType is not equal to 0, picResCb and picResCr as the inputs and the outputs are assigned to resMbL and, when ChromaArrayType is not equal to 0, resMbCb and resMbCr. + +For x proceeding over the values 0..15 and y proceeding over the values 0..15, the following ordered steps are specified: + +1. The derivation process for reference layer macroblocks as specified in clause F.6.1 is invoked with the luma location ( x, y ), fieldMbFlag, refLayerFieldMbFlag, and refLayerMbType as the inputs and the outputs are assigned to mbAddrRefLayer and ( xRef, yRef ). +2. When refLayerMbType[ mbAddrRefLayer ] is equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL, the following applies: + - a. The prediction luma sample predMbL[ x, y ] is modified by + +$$\text{predMb}_L[ x, y ] = \text{predMbTemp}_L[ x, y ] \quad (\text{F-121})$$ + +- b. When ChromaArrayType is not equal to 0, (x % SubWidthC) is equal to 0, and (y % SubHeightC) is equal to 0, the prediction chroma samples predMbCb[ x / SubWidthC, y / SubHeightC ] and predMbCr[ x / SubWidthC, y / SubHeightC ] are modified by + +$$\text{predMb}_{Cb}[ x / \text{SubWidthC}, y / \text{SubHeightC} ] = \text{predMbTemp}_{Cb}[ x / \text{SubWidthC}, y / \text{SubHeightC} ] \quad (\text{F-122})$$ + +$$\text{predMb}_{Cr}[ x / \text{SubWidthC}, y / \text{SubHeightC} ] = \text{predMbTemp}_{Cr}[ x / \text{SubWidthC}, y / \text{SubHeightC} ] \quad (\text{F-123})$$ + +- c. The residual luma sample resMbL[ x, y ] is set equal to 0. +- d. When ChromaArrayType is not equal to 0, (x % SubWidthC) is equal to 0, and (y % SubHeightC) is equal to 0, the residual chroma samples resMbCb[ x / SubWidthC, y / SubHeightC ] and resMbCr[ x / SubWidthC, y / SubHeightC ] are set equal to 0. + +The picture sample array construction process as specified in clause F.8.5.4.1 is invoked with fieldMbFlag, resMbL, picResL, and, when ChromaArrayType is not equal to 0, resMbCb, resMbCr, picResCb, and picResCr as the inputs and the outputs are a modified version of the array picResL and, when ChromaArrayType is not equal to 0, modified versions of the arrays picResCb and picResCr. + +## F.8.5 SVC transform coefficient decoding and sample array construction processes + +Clause F.8.5.1 specifies the transform coefficient scaling and refinement process. + +Clause F.8.5.2 specifies the transform coefficient level scaling process prior to transform coefficient refinement. + +Clause F.8.5.3 specifies the residual construction and accumulation process. + +Clause F.8.5.4 specifies the sample array accumulation process. + +Clause F.8.5.5 specifies the sample array re-initialization process. + +#### **F.8.5.1 Transform coefficient scaling and refinement process** + +Inputs to this process are: + +- a variable refinementFlag specifying whether the transform coefficients for the current macroblock are combined with the existent transform coefficients for the current macroblock, which were obtained from the reference layer representation, +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable mbType specifying the macroblock type for the current macroblock, +- a variable cTrafo specifying the transform type for the current macroblock, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- a list of transform coefficient level values tCoeffLevel with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- the luma quantization parameter $\text{tQP}_Y$ , +- when ChromaArrayType is not equal to 0, the chroma quantization parameters $\text{tQP}_{Cb}$ and $\text{tQP}_{Cr}$ . + +Outputs of this process are: + +- a modified version of the list sTCoeff, +- a modified version of the list tCoeffLevel. + +The scaling functions are derived as specified in clause 8.5.9. For this invocation of clause 8.5.9, the current macroblock is considered as coded using an Intra macroblock prediction mode when mbType is equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL; otherwise it is considered as coded using an Inter macroblock prediction mode. + +The variable $\text{qP}'_Y$ is set equal to $(\text{tQP}_Y + \text{QpBdOffset}_Y)$ . When ChromaArrayType is not equal to 0, the variables $\text{qP}'_{Cb}$ and $\text{qP}'_{Cr}$ are set equal to $(\text{tQP}_{Cb} + \text{QpBdOffset}_C)$ and $(\text{tQP}_{Cr} + \text{QpBdOffset}_C)$ , respectively. + +When refinementFlag is equal to 0, all $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements of the lists sTCoeff and tCoeffLevel are set equal to 0. + +The refinement process for luma transform coefficients as specified in clause F.8.5.1.1 is invoked with iYCbCr set equal to 0, fieldMbFlag, cTrafo, sTCoeff, tCoeffLevel, and $\text{qP}'_Y$ as the inputs and the outputs are modified versions of the lists sTCoeff and tCoeffLevel. + +When ChromaArrayType is not equal to 0, the refinement process for chroma transform coefficients as specified in clause F.8.5.1.2 is invoked with fieldMbFlag, cTrafo, sTCoeff, tCoeffLevel, $\text{qP}'_{Cb}$ , and $\text{qP}'_{Cr}$ as the inputs and the outputs are modified versions of the lists sTCoeff and tCoeffLevel. + +##### **F.8.5.1.1 Refinement process for luma transform coefficients or chroma transform coefficients with ChromaArrayType equal to 3** + +Inputs to this process are: + +- a variable iYCbCr specifying the colour component, +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable cTrafo specifying the transform type, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- a list of transform coefficient level values tCoeffLevel with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- when iYCbCr is equal to 0, the luma quantization parameter $\text{qP}'_Y$ , +- when iYCbCr is greater than 0, the chroma quantization parameters $\text{qP}'_{Cb}$ and $\text{qP}'_{Cr}$ . + +Outputs of this process are: + +- a modified version of the list sTCoeff, + +- a modified version of the list tCoeffLevel. + +When iYCbCr is not present as input to this clause, it is inferred to be equal to 0. + +Depending on iYCbCr, the variables bitDepth, qP, cO, coeffLevel4x4, coeffLevel8x8, coeffDCLevel, and coeffACLevel are derived as follows: + +- If iYCbCr is equal to 0, bitDepth is set equal to BitDepthY, qP is set equal to qP'Y, cO is set equal to 0, coeffLevel4x4 is set equal to LumaLevel4x4, coeffLevel8x8 is set equal to LumaLevel8x8, coeffDCLevel is set equal to Intra16x16DCLevel, and coeffACLevel is set equal to Intra16x16ACLevel. +- Otherwise, if iYCbCr is equal to 1, bitDepth is set equal to BitDepthC, qP is set equal to qP'Cb, cO is set equal to 256, coeffLevel4x4 is set equal to CbLevel4x4, coeffLevel8x8 is set equal to CbLevel8x8, coeffDCLevel is set equal to CbIntra16x16DCLevel, and coeffACLevel is set equal to CbIntra16x16ACLevel. +- Otherwise (iYCbCr is equal to 2), bitDepth is set equal to BitDepthC, qP is set equal to qP'Cr, cO is set equal to (256 + MbWidthC \* MbHeightC), coeffLevel4x4 is set equal to CrLevel4x4, coeffLevel8x8 is set equal to CrLevel8x8, coeffDCLevel is set equal to CrIntra16x16DCLevel, and coeffACLevel is set equal to CrIntra16x16ACLevel. + +Depending on cTrafo, the following applies: + +- If cTrafo is equal to T\_PCM, the assignment process for luma transform coefficient values or chroma transform coefficient values with ChromaArrayType equal to 3 for I\_PCM macroblocks as specified in clause F.8.5.1.1.1 is invoked with iYCbCr, sTCoeff, and tCoeffLevel as the inputs and the outputs are modified versions of sTCoeff and tCoeffLevel. +- Otherwise, if cTrafo is equal to T\_4x4, the refinement process for transform coefficients of residual 4x4 blocks as specified in clause F.8.5.1.1.2 is invoked with fieldMbFlag, bitDepth, qP, cO, coeffLevel4x4, sTCoeff, and tCoeffLevel as the inputs and the outputs are modified versions of the lists sTCoeff and tCoeffLevel. +- Otherwise, if cTrafo is equal to T\_8x8, the refinement process for transform coefficients of residual 8x8 blocks as specified in clause F.8.5.1.1.3 is invoked with fieldMbFlag, bitDepth, qP, cO, coeffLevel8x8, sTCoeff, and tCoeffLevel as the inputs and the outputs are modified versions of the lists sTCoeff and tCoeffLevel. +- Otherwise (cTrafo is equal to T\_16x16), the refinement process for transform coefficients of Intra\_16x16 macroblocks as specified in clause F.8.5.1.1.4 is invoked with fieldMbFlag, bitDepth, qP, cO, coeffDCLevel, coeffACLevel, coeffLevel4x4, sTCoeff, and tCoeffLevel as the inputs and the outputs are modified versions of the lists sTCoeff and tCoeffLevel. + +#### F.8.5.1.1.1 Assignment process for luma transform coefficient values or chroma transform coefficient values with ChromaArrayType equal to 3 for I\_PCM macroblocks + +Inputs to this process are: + +- a variable iYCbCr specifying the colour component, +- a list of scaled transform coefficient values sTCoeff with (256 + 2 \* MbWidthC \* MbHeightC) elements, +- a list of transform coefficient level values tCoeffLevel with (256 + 2 \* MbWidthC \* MbHeightC) elements. + +Outputs of this process are: + +- a modified version of the list sTCoeff, +- a modified version of the list tCoeffLevel. + +When base\_mode\_flag is equal to 0, the following ordered steps are specified: + +1. Depending on iYCbCr, the variables cO, cListOffset and pcmSample are derived by + +$$\begin{aligned} cO &= iYCbCr * 256 \\ cListOffset &= ((iYCbCr == 0) ? 0 : (iYCbCr - 1) * 256) \end{aligned} \quad (F-124)$$ + +$$pcmSample = ((iYCbCr == 0) ? pcm\_sample\_luma : pcm\_sample\_chroma) \quad (F-125)$$ + +2. The lists tCoeffLevel and sTCoeff are modified by + +$$tCoeffLevel[cO + k] = 0 \quad \text{with } k = 0..255 \quad (F-126)$$ + +$$sTCoeff[cO + k] = pcmSample[cListOffset + k] \quad \text{with } k = 0..255 \quad (F-127)$$ + +#### F.8.5.1.1.2 Refinement process for transform coefficients of residual 4x4 blocks + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable bitDepth specifying the bit depth, +- a variable qP specifying the quantization parameter value, +- a variable cO specifying the first coefficient index in the list of scaled transform coefficient values sTCoeff and in the list of transform coefficient values tCoeffLevel, +- a variable coeffLevel4x4 representing LumaLevel4x4, CbLevel4x4, or CrLevel4x4, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- a list of transform coefficient level values tCoeffLevel with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements. + +Outputs of this process are: + +- a modified version of the list sTCoeff, +- a modified version of the list tCoeffLevel. + +Depending on tcoeff\_level\_prediction\_flag, the following applies: + +- If tcoeff\_level\_prediction\_flag is equal to 1, the list sTCoeff is modified by + +$$\text{sTCoeff}[ \text{cO} + k ] = 0 \quad \text{with } k = 0..255 \quad (\text{F-128})$$ + +- Otherwise (tcoeff\_level\_prediction\_flag is equal to 0), the list tCoeffLevel is modified by + +$$\text{tCoeffLevel}[ \text{cO} + k ] = 0 \quad \text{with } k = 0..255 \quad (\text{F-129})$$ + +For each residual 4x4 block indexed by c4x4BlkIdx = 0..15, the following ordered steps are specified: + +1. The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with coeffLevel4x4[ c4x4BlkIdx ] as the input and the outputs are transform coefficient level values as a 4x4 array c with elements $c_{ij}$ . For this invocation of the process in clause 8.5.6, the current macroblock is treated as field macroblock when fieldMbFlag is equal to 1, and it is treated as frame macroblock when fieldMbFlag is equal to 0. +2. The list tCoeffLevel and the 4x4 array c are modified by + +$$\text{tCoeffLevel}[ \text{cO} + 16 * \text{c4x4BlkIdx} + 4 * i + j ] += c_{ij} \quad \text{with } i, j = 0..3 \quad (\text{F-130})$$ + +$$c_{ij} = \text{tCoeffLevel}[ \text{cO} + 16 * \text{c4x4BlkIdx} + 4 * i + j ] \quad \text{with } i, j = 0..3 \quad (\text{F-131})$$ + +3. The scaling process for residual 4x4 blocks as specified in clause 8.5.12.1 is invoked with bitDepth, qP, and the 4x4 array c as the inputs and the outputs are scaled transform coefficient values as a 4x4 array d with elements $d_{ij}$ . For this invocation of the process in clause 8.5.12.1, the array c is treated as not relating to a luma residual block coded using the Intra\_16x16 macroblock prediction mode and as not relating to a chroma residual block. +4. The list sTCoeff is modified by + +$$\text{sTCoeff}[ \text{cO} + 16 * \text{c4x4BlkIdx} + 4 * i + j ] += d_{ij} \quad \text{with } i, j = 0..3 \quad (\text{F-132})$$ + +The bitstream shall not contain data that result in any element sTCoeff[ cO + k ] with $k = 0..255$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +The bitstream shall not contain data that result in any element tCoeffLevel[ cO + k ] with $k = 0..255$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +#### F.8.5.1.1.3 Refinement process for transform coefficients of residual 8x8 blocks + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable bitDepth specifying the bit depth, +- a variable qP specifying the quantization parameter value, +- a variable cO specifying the first coefficient index in the list of scaled transform coefficient values sTCoeff and in the list of transform coefficient values tCoeffLevel, +- a variable coeffLevel8x8 representing LumaLevel8x8, CbLevel8x8, or CrLevel8x8, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, + +- a list of transform coefficient level values tCoeffLevel with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements. + +Outputs of this process are: + +- a modified version of the list sTCoeff, +- a modified version of the list tCoeffLevel. + +Depending on tcoeff\_level\_prediction\_flag, the following applies: + +- If tcoeff\_level\_prediction\_flag is equal to 1, the list sTCoeff is modified by + +$$\text{sTCoeff}[ \text{cO} + k ] = 0 \quad \text{with } k = 0..255 \quad (\text{F-133})$$ + +- Otherwise (tcoeff\_level\_prediction\_flag is equal to 0), the list tCoeffLevel is modified by + +$$\text{tCoeffLevel}[ \text{cO} + k ] = 0 \quad \text{with } k = 0..255 \quad (\text{F-134})$$ + +For each residual 8x8 block indexed by c8x8BlkIdx = 0..3, the following ordered steps are specified: + +1. The inverse scanning process for 8x8 transform coefficients and scaling lists as specified in clause 8.5.7 is invoked with coeffLevel8x8[ c8x8BlkIdx ] as the input and the outputs are transform coefficient level values as an 8x8 array c with elements $c_{ij}$ . For this invocation of the process in clause 8.5.7, the current macroblock is treated as field macroblock when fieldMbFlag is equal to 1, and it is treated as frame macroblock when fieldMbFlag is equal to 0. + +2. The list tCoeffLevel and the 8x8 array c are modified by + +$$\text{tCoeffLevel}[ \text{cO} + 64 * \text{c8x8BlkIdx} + 8 * i + j ] += c_{ij} \quad \text{with } i, j = 0..7 \quad (\text{F-135})$$ + +$$c_{ij} = \text{tCoeffLevel}[ \text{cO} + 64 * \text{c8x8BlkIdx} + 8 * i + j ] \quad \text{with } i, j = 0..7 \quad (\text{F-136})$$ + +3. The scaling process for residual 8x8 blocks as specified in clause 8.5.13.1 is invoked with bitDepth, qP, and the 8x8 array c as the inputs and the outputs are scaled transform coefficient values as an 8x8 array d with elements $d_{ij}$ . + +4. The list sTCoeff is modified by + +$$\text{sTCoeff}[ \text{cO} + 64 * \text{c8x8BlkIdx} + 8 * i + j ] += d_{ij} \quad \text{with } i, j = 0..7 \quad (\text{F-137})$$ + +The bitstream shall not contain data that result in any element sTCoeff[ cO + k ] with $k = 0..255$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +The bitstream shall not contain data that result in any element tCoeffLevel[ cO + k ] with $k = 0..255$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +#### F.8.5.1.1.4 Refinement process for transform coefficients of Intra\_16x16 macroblocks + +This process is only invoked when base\_mode\_flag is equal to 0 or tcoeff\_level\_prediction\_flag is equal to 1. + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable bitDepth specifying the bit depth, +- a variable qP specifying the quantization parameter value, +- a variable cO specifying the first coefficient index in the list of scaled transform coefficient values sTCoeff and in the list of transform coefficient values tCoeffLevel, +- a variable coeffDCLevel representing Intra16x16DCLevel, CbIntra16x16DCLevel, or CrIntra16x16DCLevel, +- a variable coeffACLevel representing Intra16x16ACLevel, CbIntra16x16ACLevel, or CrIntra16x16ACLevel, +- a variable coeffLevel4x4 representing LumaLevel4x4, CbLevel4x4, or CrLevel4x4, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- a list of transform coefficient level values tCoeffLevel with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements. + +Outputs of this process are: + +- a modified version of the list sTCoeff, +- a modified version of the list tCoeffLevel. + +NOTE 1 – When `tcoeff_level_prediction_flag` is equal to 0, this clause is always invoked as part of an invocation of clause F.8.5.1 with `refinementFlag` equal to 0, in which case all elements of the list `tCoeffLevel` are set equal to 0 before invoking this clause. + +For the DC transform coefficients of all residual 4x4 blocks, the following ordered steps are specified: + +1. Depending on `base_mode_flag`, the 4x4 array `c` with elements $c_{ij}$ is derived as follows: + +- If `base_mode_flag` is equal to 0, the inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with `coeffDCLevel` as the input and the outputs are DC transform coefficient level values for all residual 4x4 blocks as a 4x4 array `c` with elements $c_{ij}$ . For this invocation of the process in clause 8.5.6, the current macroblock is treated as field macroblock when `fieldMbFlag` is equal to 1, and it is treated as frame macroblock when `fieldMbFlag` is equal to 0. +- Otherwise (`base_mode_flag` is equal to 1), the 4x4 array `c` with elements $c_{ij}$ containing DC transform coefficient level values is derived by + +$$c_{ij} = \text{coeffLevel4x4}[ 8 * ( i / 2 ) + 4 * ( j / 2 ) + 2 * ( i \% 2 ) + ( j \% 2 ) ][ 0 ] \quad \text{with } i, j = 0..3 \quad (F-138)$$ + +2. The list `tCoeffLevel` and the 4x4 array `c` are modified by + +$$\text{tCoeffLevel}[ cO + 128 * ( i / 2 ) + 64 * ( j / 2 ) + 32 * ( i \% 2 ) + 16 * ( j \% 2 ) ] += c_{ij} \quad \text{with } i, j = 0..3 \quad (F-139)$$ + +$$c_{ij} = \text{tCoeffLevel}[ cO + 128 * ( i / 2 ) + 64 * ( j / 2 ) + 32 * ( i \% 2 ) + 16 * ( j \% 2 ) ] \quad \text{with } i, j = 0..3 \quad (F-140)$$ + +3. The scaling and transformation process for DC transform coefficients for `Intra_16x16` macroblock type as specified in clause 8.5.10 is invoked with `bitDepth`, `qP`, and `c` as the inputs and the output is the 4x4 array `d` with elements $d_{ij}$ representing scaled DC transform coefficient values for all residual 4x4 blocks. + +4. The list `sTCoeff` is modified by + +$$\text{sTCoeff}[ cO + 128 * ( i / 2 ) + 64 * ( j / 2 ) + 32 * ( i \% 2 ) + 16 * ( j \% 2 ) ] = d_{ij} \quad \text{with } i, j = 0..3 \quad (F-141)$$ + +For each residual 4x4 block indexed by `c4x4BlkIdx = 0..15`, the following ordered steps are specified: + +1. Depending on `base_mode_flag`, the variable `c4x4List`, which is a list of 16 entries, is derived as follows: + +- If `base_mode_flag` is equal to 0, the following applies: + +$$\text{c4x4List}[ k ] = ( ( k == 0 ) ? 0 : \text{coeffACLevel}[ \text{c4x4BlkIdx} ][ k - 1 ] ) \quad \text{with } k = 0..15 \quad (F-142)$$ + +- Otherwise (`base_mode_flag` is equal to 1), the following applies: + +$$\text{c4x4List}[ k ] = ( ( k == 0 ) ? 0 : \text{coeffLevel4x4}[ \text{c4x4BlkIdx} ][ k ] ) \quad \text{with } k = 0..15 \quad (F-143)$$ + +2. The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with `c4x4List` as the input and the outputs are transform coefficient level values as a 4x4 array `e` with elements $e_{ij}$ . For this invocation of the process in clause 8.5.6, the current macroblock is treated as field macroblock when `fieldMbFlag` is equal to 1, and it is treated as frame macroblock when `fieldMbFlag` is equal to 0. + +3. The list `tCoeffLevel` and the 4x4 array `e` are modified by + +$$\text{tCoeffLevel}[ cO + 16 * \text{c4x4BlkIdx} + 4 * i + j ] += e_{ij} \quad \text{with } i, j = 0..3 \text{ and } i + j > 0 \quad (F-144)$$ + +$$e_{ij} = \text{tCoeffLevel}[ cO + 16 * \text{c4x4BlkIdx} + 4 * i + j ] \quad \text{with } i, j = 0..3 \text{ and } i + j > 0 \quad (F-145)$$ + +4. The scaling process for residual 4x4 blocks as specified in clause 8.5.12.1 is invoked with `bitDepth`, `qP`, and the 4x4 array `e` as the inputs and the outputs are scaled transform coefficient values as a 4x4 array `d` with elements $d_{ij}$ . During the process in clause 8.5.12.1, the array `e` is treated as relating to a luma residual block coded using the `Intra_16x16` macroblock prediction mode. + +5. The list `sTCoeff` is modified by + +$$\text{sTCoeff}[ cO + 16 * \text{c4x4BlkIdx} + 4 * i + j ] = d_{ij} \quad \text{with } i, j = 0..3 \text{ and } i + j > 0 \quad (F-146)$$ + +NOTE 2 – The elements `tCoeffLevel[ cO + 16* c4x4BlkIdx ]` and `sTCoeff[ cO + 16* c4x4BlkIdx ]` are not modified during the process for a residual 4x4 block with index `c4x4BlkIdx`. + +The bitstream shall not contain data that result in any element `tCoeffLevel[ cO + k ]` with $k = 0..255$ that exceeds the range of integer values from $-2^{(7 + \text{bitDepth})}$ to $2^{(7 + \text{bitDepth})} - 1$ , inclusive. + +#### F.8.5.1.2 Refinement process for chroma transform coefficients + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable cTrafo specifying the transform type, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- a list of transform coefficient level values tCoeffLevel with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- the chroma quantization parameters $\text{qP}'_{\text{Cb}}$ and $\text{qP}'_{\text{Cr}}$ . + +Outputs of this process are: + +- a modified version of the list sTCoeff, +- a modified version of the list tCoeffLevel. + +For both chroma components indexed by $\text{iCbCr} = 0..1$ , the following applies: + +- If ChromaArrayType is equal to 1 or 2, the following applies: + - If cTrafo is equal to T\_PCM, the assignment process for chroma transform coefficient values for I\_PCM macroblocks as specified in clause F.8.5.1.2.1 is invoked with iCbCr, sTCoeff, and tCoeffLevel as the inputs and the outputs are modified versions of sTCoeff and tCoeffLevel. + - Otherwise (cTrafo is not equal to T\_PCM), the refinement process for chroma transform coefficients with ChromaArrayType equal to 1 or 2 as specified in clause F.8.5.1.2.2 is invoked with iCbCr, fieldMbFlag, sTCoeff, tCoeffLevel, $\text{qP}'_{\text{Cb}}$ , and $\text{qP}'_{\text{Cr}}$ as the inputs and the outputs are modified versions of the lists sTCoeff and tCoeffLevel. +- Otherwise (ChromaArrayType is equal to 3), the refinement process for luma transform coefficients or chroma transform coefficients with ChromaArrayType equal to 3 as specified in clause F.8.5.1.1 is invoked with iYCbCr set equal to $(1 + \text{iCbCr})$ , fieldMbFlag, cTrafo, sTCoeff, tCoeffLevel, $\text{qP}'_{\text{Cb}}$ , and $\text{qP}'_{\text{Cr}}$ as the inputs and the outputs are modified versions of the lists sTCoeff and tCoeffLevel. + +##### F.8.5.1.2.1 Assignment process for chroma transform coefficient values for I\_PCM macroblocks + +Inputs to this process are: + +- a variable iCbCr specifying the chroma component, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- a list of transform coefficient level values tCoeffLevel with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements. + +Outputs of this process are: + +- a modified version of the list sTCoeff, +- a modified version of the list tCoeffLevel. + +The variable numC is set equal to $(\text{MbWidthC} * \text{MbHeightC})$ and the variable cCO is set equal to $(\text{iCbCr} * \text{numC})$ . + +When base\_mode\_flag is equal to 0, the lists tCoeffLevel and sTCoeff are modified by + +$$\text{tCoeffLevel}[ 256 + \text{cCO} + k ] = 0 \quad \text{with } k = 0..(\text{numC} - 1) \quad (\text{F-147})$$ + +$$\text{sTCoeff}[ 256 + \text{cCO} + k ] = \text{pcm\_sample\_chroma}[ \text{cCO} + k ] \quad \text{with } k = 0..(\text{numC} - 1) \quad (\text{F-148})$$ + +##### F.8.5.1.2.2 Refinement process for chroma transform coefficients with ChromaArrayType equal to 1 or 2 + +This process is only invoked when ChromaArrayType is equal to 1 or 2. + +Inputs to this process are: + +- a variable iCbCr specifying the chroma component, +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- a list of transform coefficient level values tCoeffLevel with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements, +- the chroma quantization parameters $\text{qP}'_{\text{Cb}}$ and $\text{qP}'_{\text{Cr}}$ . + +Outputs of this process are: + +- a modified version of the list sTCoeff, +- a modified version of the list tCoeffLevel. + +The variables nW, nH, numB, cO, and qP are derived by + +$$\text{nW} = \text{MbWidthC} / 4 \quad (\text{F-149})$$ + +$$\text{nH} = \text{MbHeightC} / 4 \quad (\text{F-150})$$ + +$$\text{numB} = \text{nW} * \text{nH} \quad (\text{F-151})$$ + +$$\text{cO} = 256 + ( \text{iCbCr} * \text{MbWidthC} * \text{MbHeightC} ) \quad (\text{F-152})$$ + +$$\text{qP} = ( ( \text{iCbCr} == 0 ) ? \text{qP}'_{\text{Cb}} : \text{qP}'_{\text{Cr}} ) \quad (\text{F-153})$$ + +Depending on tcoeff\_level\_prediction\_flag, the following applies: + +- If tcoeff\_level\_prediction\_flag is equal to 1, the list sTCoeff is modified by + +$$\text{sTCoeff}[ \text{cO} + k ] = 0 \quad \text{with } k = 0..(\text{MbWidthC} * \text{MbHeightC} - 1) \quad (\text{F-154})$$ + +- Otherwise (tcoeff\_level\_prediction\_flag is equal to 0), the list tCoeffLevel is modified by + +$$\text{tCoeffLevel}[ \text{cO} + k ] = 0 \quad \text{with } k = 0..(\text{MbWidthC} * \text{MbHeightC} - 1) \quad (\text{F-155})$$ + +For the chroma DC transform coefficients of all residual 4x4 chroma blocks, the following ordered steps are specified: + +1. Depending on ChromaArrayType, the (nW)x(nH) array c with elements $c_{ij}$ is derived as follows: + +- If ChromaArrayType is equal to 1, + +$$c_{ij} = \text{ChromaDCLevel}[ \text{iCbCr} ][ 2 * i + j ] \quad \text{with } i = 0..(\text{nH} - 1), j = 0..(\text{nW} - 1) \quad (\text{F-156})$$ + +- Otherwise (ChromaArrayType is equal to 2), + +$$c_{ij} = \text{ChromaDCLevel}[ \text{iCbCr} ][ \text{scan422ChromaDC}[ 2 * i + j ] ] \quad (\text{F-157})$$ + +with $i = 0..(\text{nH} - 1), j = 0..(\text{nW} - 1)$ , +and $\text{scan422ChromaDC} = \{ 0, 2, 1, 5, 3, 6, 4, 7 \}$ + +2. The list tCoeffLevel and the (nW)x(nH) array c are modified by + +$$\text{tCoeffLevel}[ \text{cO} + 32 * i + 16 * j ] += c_{ij} \quad \text{with } i = 0..(\text{nH} - 1), j = 0..(\text{nW} - 1) \quad (\text{F-158})$$ + +$$c_{ij} = \text{tCoeffLevel}[ \text{cO} + 32 * i + 16 * j ] \quad \text{with } i = 0..(\text{nH} - 1), j = 0..(\text{nW} - 1) \quad (\text{F-159})$$ + +3. The variable qPDC is derived by + +$$\text{qP}_{\text{DC}} = ( ( \text{ChromaArrayType} == 1 ) ? \text{qP} : ( \text{qP} + 3 ) ) \quad (\text{F-160})$$ + +4. The (nW)x(nH) array d with elements $d_{ij}$ representing scaled chroma DC transform coefficient values for all residual 4x4 chroma blocks is derived by + +$$d_{ij} = c_{ij} * ( \text{LevelScale4x4}( \text{qP}_{\text{DC}} \% 6, 0, 0 ) \ll ( \text{qP}_{\text{DC}} / 6 ) ) \quad \text{with } i = 0..(\text{nH} - 1), j = 0..(\text{nW} - 1) \quad (\text{F-161})$$ + +5. The list sTCoeff is modified by + +$$\text{sTCoeff}[ \text{cO} + 32 * i + 16 * j ] += d_{ij} \quad \text{with } i = 0..(\text{nH} - 1), j = 0..(\text{nW} - 1) \quad (\text{F-162})$$ + +For each residual 4x4 chroma block indexed by c4x4BlkIdx = 0..(numB - 1), the following ordered steps are specified: + +1. The variable c4x4List, which is a list of 16 entries, is derived by + +$$\text{c4x4List}[ k ] = ( ( k == 0 ) ? 0 : \text{ChromaACLevel}[ \text{iCbCr} ][ \text{c4x4BlkIdx} ][ k - 1 ] ) \quad (\text{F-163})$$ + +with $k = 0..15$ + +2. The inverse scanning process for 4x4 transform coefficients and scaling lists as specified in clause 8.5.6 is invoked with c4x4List as the input and the outputs are chroma transform coefficient level values as a 4x4 array e with elements $e_{ij}$ . During the process in clause 8.5.6, the current macroblock is treated as field macroblock when fieldMbFlag is equal to 1, and it is treated as frame macroblock when fieldMbFlag is equal to 0. + +3. The list tCoeffLevel and the 4x4 array e are modified by + +$$\text{tCoeffLevel}[ \text{cO} + 16 * \text{c4x4BlkIdx} + 4 * i + j ] += e_{ij} \quad \text{with } i, j = 0..3 \text{ and } i + j > 0 \quad (\text{F-164})$$ + +$$e_{ij} = \text{tCoeffLevel}[ \text{cO} + 16 * \text{c4x4BlkIdx} + 4 * i + j ] \quad \text{with } i, j = 0..3 \text{ and } i + j > 0 \quad (\text{F-165})$$ + +4. The scaling process for residual 4x4 blocks as specified in clause 8.5.12.1 is invoked with BitDepthC, qP, and the 4x4 array e as the inputs and the outputs are scaled chroma transform coefficient values as a 4x4 array d of with elements dij. During the process in clause 8.5.12.1, the array e is treated as relating to a chroma residual block. +5. The list sTCoeff is modified by + +$$sTCoeff[ cO + 16 * c4x4BlkIdx + 4 * i + j ] += d_{ij} \quad \text{with } i, j = 0..3 \text{ and } i + j > 0 \quad (F-166)$$ + +NOTE 1 – The elements tCoeffLevel[ cO + 16\* c4x4BlkIdx ] and sTCoeff[ cO + 16\* c4x4BlkIdx ] are not modified during the process for a residual 4x4 chroma block with index c4x4BlkIdx. + +The bitstream shall not contain data that result in any element sTCoeff[ cO + 16\* b + k ] with b = 0..(numB – 1) and k = 1..15 that exceeds the range of integer values from $-2^{(7 + \text{BitDepth}_C)}$ to $2^{(7 + \text{BitDepth}_C)} - 1$ , inclusive. + +The bitstream shall not contain data that result in any element tCoeffLevel[ cO + 16\* b + k ] with b = 0..(numB – 1) and k = 1..15 that exceeds the range of integer values from $-2^{(7 + \text{BitDepth}_C)}$ to $2^{(7 + \text{BitDepth}_C)} - 1$ , inclusive. + +NOTE 2 – The elements tCoeffLevel[ cO + 16\* b ] and sTCoeff[ cO + 16\* b ] with b = 0..(numB – 1) can exceed the range of integer values from $-2^{(7 + \text{BitDepth}_C)}$ to $2^{(7 + \text{BitDepth}_C)} - 1$ , inclusive. + +### F.8.5.2 Transform coefficient level scaling process prior to transform coefficient refinement + +Inputs to this process are: + +- a variable cTrafo specifying the luma transform type for the current macroblock, +- a list tCoeffLevel with (256 + 2 \* MbWidthC \* MbHeightC) elements specifying transform coefficient level values for the current macroblock, +- a variable tQPY specifying the luma quantization parameter for the current macroblock, +- a variable refQPY specifying the quantization parameter for the macroblock of the reference layer representation, +- when ChromaArrayType is not equal to 0, two variables tQPCb and tQPCr specifying chroma quantization parameters for the current macroblock, +- when ChromaArrayType is not equal to 0, two variables refQPCb and refQPCr specifying chroma quantization parameters for the macroblock of the reference layer representation, + +Output of this process is a modified version of the list tCoeffLevel. + +Table F-6 specifies the scale values cS for transform coefficient level scaling. + +**Table F-6 – Scale values cS for transform coefficient level scaling** + +| $( \text{refQP} - \text{cQP} + 54 ) \% 6$ | scale value cS | +|-------------------------------------------|----------------| +| 0 | 8 | +| 1 | 9 | +| 2 | 10 | +| 3 | 11 | +| 4 | 13 | +| 5 | 14 | + +The variable iYCbCr proceeds over the values from 0 to $( ( \text{ChromaArrayType} == 0 ) ? 0 : 2 )$ , inclusive, and for each value of iYCbCr, the following ordered steps are specified: + +1. The variables cO, iMax, cQP, and refQP are derived by + +$$cO = ( ( iYCbCr == 0 ) ? 0 : ( 256 + ( iYCbCr - 1 ) * \text{MbWidthC} * \text{MbHeightC} ) ) \quad (F-167)$$ + +$$iMax = ( ( iYCbCr == 0 ) ? 255 : ( \text{MbWidthC} * \text{MbHeightC} - 1 ) ) \quad (F-168)$$ + +$$cQP = ( ( iYCbCr == 0 ) ? tQP_Y : ( iYCbCr == 1 ? tQP_{Cb} : tQP_{Cr} ) ) \quad (F-169)$$ + +$$refQP = ( ( iYCbCr == 0 ) ? refQP_Y : ( iYCbCr == 1 ? refQP_{Cb} : refQP_{Cr} ) ) \quad (F-170)$$ + +2. The variable cS is set as specified in Table F-6 using the values of refQP and cQP. + +3. The variable rShift is calculated by + +$$rShift = ( refQP - cQP + 54 ) / 6 \quad (F-171)$$ + +4. The list tCoeffLevel of transform coefficient level values is modified by + +$$tCoeffLevel[ cO + i ] = ( ( cS * tCoeffLevel[ cO + i ] ) \ll rShift ) \gg 12 \quad \text{with } i = 0..iMax \quad (F-172)$$ + +The following constraints shall be obeyed: + +- a) The bitstream shall not contain data that result in any element tCoeffLevel[ k ] with $k = 0..255$ that exceeds the range of integer values from $-2^{(7 + BitDepth_V)}$ to $2^{(7 + BitDepth_V)} - 1$ , inclusive. +- b) When ChromaArrayType is equal to 1 or 2, the bitstream shall not contain data that result in any element tCoeffLevel[ 256 + 16\* b + k ] with $b = 0..(MbWidthC * MbHeightC / 8 - 1)$ , and $k = 1..15$ that exceeds the range of integer values from $-2^{(7 + BitDepth_C)}$ to $2^{(7 + BitDepth_C)} - 1$ , inclusive. + +NOTE 1 – When ChromaArrayType is equal to 1 or 2 and cTrafo is not equal to T\_PCM, the elements tCoeffLevel[ 256 + 16\* b ] with $b = 0..(MbWidthC * MbHeightC / 8 - 1)$ can exceed the range of integer values from $-2^{(7 + BitDepth_C)}$ to $2^{(7 + BitDepth_C)} - 1$ , inclusive. + +- c) When ChromaArrayType is equal to 3, the bitstream shall not contain data that result in any element tCoeffLevel[ 256 + k ] with $k = 0..511$ that exceeds the range of integer values from $-2^{(7 + BitDepth_C)}$ to $2^{(7 + BitDepth_C)} - 1$ , inclusive. + +NOTE 2 – When tQPV is less than 10 and cTrafo is equal to T\_16x16, the range of values that can be represented by an alternative representation of the bitstream with entropy\_coding\_mode\_flag equal to 0 and profile\_idc equal to 66, 77, or 88, may not be sufficient to represent the full range of values of the elements tCoeffLevel[ 16 \* b ] with $b = 0..15$ that could be necessary to form a close approximation of the content of any possible source picture. + +NOTE 3 – When ChromaArrayType is equal to 1 or 2 and tQPCX with CX being replaced by Cb and Cr is less than 4, the range of values that can be represented by an alternative representation of the bitstream with entropy\_coding\_mode\_flag equal to 0 and profile\_idc equal to 66, 77, or 88, may not be sufficient to represent the full range of values of the elements tCoeffLevel[ 256 + 16 \* b ] with $b = 0..(MbWidthC * MbHeightC / 8 - 1)$ that could be necessary to form a close approximation of the content of any possible source picture. + +### F.8.5.3 Residual construction and accumulation process + +Inputs to this process are: + +- a variable accumulationFlag specifying whether the constructed residual sample values for the current macroblock are combined with the existent residual sample value for the macroblock, +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable cTrafo specifying the transform type, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * MbWidthC * MbHeightC)$ elements, +- a $(PicWidthInSamples_L) \times (PicHeightInSamples_L)$ array picResL containing residual luma sample values for the current layer representation, +- when ChromaArrayType is not equal to 0, two $(PicWidthInSamples_C) \times (PicHeightInSamples_C)$ arrays picResCb and picResCr containing residual chroma sample values for the current layer representation. + +Outputs of this process are: + +- a modified version of the array picResL, +- when ChromaArrayType is not equal to 0, modified versions of the arrays picResCb and picResCr. + +The construction process for luma residuals as specified in clause F.8.5.3.1 is invoked with cTrafo and sTCoeff as the inputs and the outputs are residual luma sample values as a 16x16 array mbResL. + +When ChromaArrayType is not equal to 0, the construction process for chroma residuals as specified in clause F.8.5.3.2 is invoked with cTrafo and sTCoeff as the inputs and the outputs are residual chroma sample values as two $(MbWidthC) \times (MbHeightC)$ arrays mbResCb and mbResCr. + +When accumulationFlag is equal to 1, the following ordered steps are specified: + +1. The macroblock sample array extraction process as specified in clause F.8.5.4.2 is invoked with fieldMbFlag, picResL, and, when ChromaArrayType is equal to 0, picResCb and picResCr as the inputs and the outputs are a 16x16 array refLayerMbResL and, when ChromaArrayType is not equal to 0, two $(MbWidthC) \times (MbHeightC)$ arrays refLayerMbResCb and refLayerMbResCr. + +2. All elements $mbRes_L[ x, y ]$ of the 16x16 array $mbRes_L$ with $x, y = 0..15$ are modified by + +$$mbRes_L[ x, y ] = Clip3( yMin, yMax, mbRes_L[ x, y ] + refLayerMbRes_L[ x, y ] ) \quad (F-173)$$ + +with + +$$yMin = - ( 1 \ll BitDepth_Y ) + 1 \quad (F-174)$$ + +$$yMax = ( 1 \ll BitDepth_Y ) - 1 \quad (F-175)$$ + +3. When $ChromaArrayType$ is not equal to 0, for CX being replaced by Cb and Cr, all elements $mbRes_{CX}[ x, y ]$ of the $(MbWidthC)x(MbHeightC)$ array $mbRes_{CX}$ with $x = 0..(MbWidthC - 1)$ and $y = 0..(MbHeightC - 1)$ are modified by + +$$mbRes_{CX}[ x, y ] = Clip3( cMin, cMax, mbRes_{CX}[ x, y ] + refLayerMbRes_{CX}[ x, y ] ) \quad (F-176)$$ + +with + +$$cMin = - ( 1 \ll BitDepth_C ) + 1 \quad (F-177)$$ + +$$cMax = ( 1 \ll BitDepth_C ) - 1 \quad (F-178)$$ + +The picture sample array construction process as specified in clause F.8.5.4.1 is invoked with $fieldMbFlag$ , $mbRes_L$ , $picRes_L$ , and, when $ChromaArrayType$ is not equal to 0, $mbRes_{Cb}$ , $mbRes_{Cr}$ , $picRes_{Cb}$ , and $picRes_{Cr}$ as the inputs and the outputs are a modified version of the array $picRes_L$ and, when $ChromaArrayType$ is not equal to 0, modified versions of the arrays $picRes_{Cb}$ and $picRes_{Cr}$ . + +#### F.8.5.3.1 Construction process for luma residuals or chroma residuals with $ChromaArrayType$ equal to 3 + +Inputs to this process are: + +- a variable $iYCbCr$ specifying the colour component (when present), +- a variable $cTrafo$ specifying the transform type, +- a list of scaled transform coefficient values $sTCoeff$ with $(256 + 2 * MbWidthC * MbHeightC)$ elements. + +Outputs of this process are residual sample values as a 16x16 array $mbRes$ with elements $mbRes[ x, y ]$ . + +When $iYCbCr$ is not present as input to this clause, it is inferred to be equal to 0. + +Depending on $iYCbCr$ , the variables $bitDepth$ and $cO$ are derived as follows: + +- If $iYCbCr$ is equal to 0, $bitDepth$ is set equal to $BitDepth_Y$ and $cO$ is set equal to 0. +- Otherwise, if $iYCbCr$ is equal to 1, $bitDepth$ is set equal to $BitDepth_C$ and $cO$ is set equal to 256. +- Otherwise ( $iYCbCr$ is equal to 2), $bitDepth$ is set equal to $BitDepth_C$ and $cO$ is set equal to $(256 + MbWidthC * MbHeightC)$ . + +Depending on $cTrafo$ , the 16x16 array $mbRes$ is derived as follows: + +- If $cTrafo$ is equal to $T\_PCM$ , the construction process for luma residuals or chroma residuals with $ChromaArrayType$ equal to 3 of $I\_PCM$ macroblocks as specified in clause F.8.5.3.1.1 is invoked with $cO$ and $sTCoeff$ as the inputs and the output is the 16x16 array $mbRes$ of residual sample values. +- Otherwise, if $cTrafo$ is equal to $T\_4x4$ , the construction process for residual 4x4 blocks as specified in clause F.8.5.3.1.2 is invoked with $bitDepth$ , $cO$ , and $sTCoeff$ as the inputs and the output is the 16x16 array $mbRes$ of residual sample values. +- Otherwise, if $cTrafo$ is equal to $T\_8x8$ , the construction process for residual 8x8 blocks as specified in clause F.8.5.3.1.3 is invoked with $bitDepth$ , $cO$ , and $sTCoeff$ as the inputs and the output is the 16x16 array $mbRes$ of residual sample values. +- Otherwise ( $cTrafo$ is equal to $T\_16x16$ ), the construction process for residuals of $Intra\_16x16$ macroblocks as specified in clause F.8.5.3.1.4 is invoked with $bitDepth$ , $cO$ , and $sTCoeff$ as the inputs and the output is the 16x16 array $mbRes$ of residual sample values. + +##### F.8.5.3.1.1 Construction process for luma residuals or chroma residuals with $ChromaArrayType$ equal to 3 of $I\_PCM$ macroblocks + +Inputs to this process are: + +- a variable $cO$ specifying the first coefficient index in the list of scaled transform coefficient values $sTCoeff$ , +- a list of scaled transform coefficient values $sTCoeff$ with $(256 + 2 * MbWidthC * MbHeightC)$ elements. + +Outputs of this process are residual sample values as a 16x16 array mbRes with elements mbRes[ x, y ]. + +The 16x16 array mbRes is derived by: + +$$\text{mbRes}[ x, y ] = \text{sTCoeff}[ cO + y * 16 + x ] \quad \text{with } x, y = 0..15 \quad (\text{F-179})$$ + +#### F.8.5.3.1.2 Construction process for residual 4x4 blocks + +Inputs to this process are: + +- a variable bitDepth specifying the bit depth, +- a variable cO specifying the first coefficient index in the list of scaled transform coefficient values sTCoeff, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements. + +Outputs of this process are residual sample values as a 16x16 array mbRes with elements mbRes[ x, y ]. + +For each residual 4x4 block indexed by c4x4BlkIdx = 0..15, the following ordered steps are specified: + +1. The 4x4 array d with elements $d_{ij}$ is derived by: + +$$d_{ij} = \text{sTCoeff}[ cO + 16 * \text{c4x4BlkIdx} + 4 * i + j ] \quad \text{with } i, j = 0..3 \quad (\text{F-180})$$ + +2. The transformation process for residual 4x4 blocks as specified in clause 8.5.12.2 is invoked with bitDepth and the 4x4 array d as the inputs and the outputs are residual sample value as a 4x4 array r with elements $r_{ij}$ . + 3. The inverse 4x4 luma block scanning process as specified in clause 6.4.3 is invoked with c4x4BlkIdx as the input and the output is assigned to ( xP, yP ). + 4. The elements mbRes[ x, y ] of the 16x16 array mbRes with $x = \text{xP}..(\text{xP} + 3)$ and $y = \text{yP}..(\text{yP} + 3)$ are derived by +- $$\text{mbRes}[ \text{xP} + j, \text{yP} + i ] = r_{ij} \quad \text{with } i, j = 0..3 \quad (\text{F-181})$$ + +#### F.8.5.3.1.3 Construction process for residual 8x8 blocks + +Inputs to this process are: + +- a variable bitDepth specifying the bit depth, +- a variable cO specifying the first coefficient index in the list of scaled transform coefficient values sTCoeff, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements. + +Outputs of this process are residual sample values as a 16x16 array mbRes with elements mbRes[ x, y ]. + +For each residual 8x8 block indexed by c8x8BlkIdx = 0..3, the following ordered steps are specified: + +1. The 8x8 array d with elements $d_{ij}$ is derived by: + +$$d_{ij} = \text{sTCoeff}[ cO + 64 * \text{c8x8BlkIdx} + 8 * i + j ] \quad \text{with } i, j = 0..7 \quad (\text{F-182})$$ + +2. The transformation process for residual 8x8 blocks as specified in clause 8.5.13.2 is invoked with bitDepth and the 8x8 array d as the inputs and the outputs are residual sample values as an 8x8 array r with elements $r_{ij}$ . + 3. The inverse 8x8 luma block scanning process as specified in clause 6.4.5 is invoked with c8x8BlkIdx as the input and the output is assigned to ( xP, yP ). + 4. The elements mbRes[ x, y ] of the 16x16 array mbRes with $x = \text{xP}..(\text{xP} + 7)$ and $y = \text{yP}..(\text{yP} + 7)$ are derived by +- $$\text{mbRes}[ \text{xP} + j, \text{yP} + i ] = r_{ij} \quad \text{with } i, j = 0..7 \quad (\text{F-183})$$ + +#### F.8.5.3.1.4 Construction process for residuals of Intra\_16x16 macroblocks + +Inputs to this process are: + +- a variable bitDepth specifying the bit depth, +- a variable cO specifying the first coefficient index in the list of scaled transform coefficient values sTCoeff, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * \text{MbWidthC} * \text{MbHeightC})$ elements. + +Outputs of this process are residual sample values as a 16x16 array mbRes with elements mbRes[ x, y ]. + +For each residual 4x4 block indexed by c4x4BlkIdx = 0..15, the following ordered steps are specified: + +1. The 4x4 array d with elements $d_{ij}$ is derived by: + +$$d_{ij} = \text{sTCoeff}[ cO + 16 * \text{c4x4BlkIdx} + 4 * i + j ] \quad \text{with } i, j = 0..3 \quad (\text{F-184})$$ + +2. The transformation process for residual 4x4 blocks as specified in clause 8.5.12.2 is invoked with bitDepth and the 4x4 array d as the inputs and the outputs are residual sample values as a 4x4 array r with elements $r_{ij}$ . +3. The inverse 4x4 luma block scanning process as specified in clause 6.4.3 is invoked with c4x4BlkIdx as the input and the output is assigned to ( xP, yP ). +4. The elements mbRes[ x, y ] of the 16x16 array mbRes with $x = xP..(xP + 3)$ and $y = yP..(yP + 3)$ are derived by + +$$mbRes[ xP + j, yP + i ] = r_{ij} \quad \text{with } i, j = 0..3 \quad (F-185)$$ + +### F.8.5.3.2 Construction process for chroma residuals + +Inputs to this process are: + +- a variable cTrafo specifying the transform type, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * MbWidthC * MbHeightC)$ elements. + +Outputs of this process are residual chroma sample values as two $(MbWidthC)x(MbHeightC)$ arrays mbResCb and mbResCr with elements mbResCb[ x, y ] and mbResCr[ x, y ], respectively. + +For both chroma components indexed by iCbCr = 0..1 and for CX being replaced by Cb for iCbCr equal to 0 and Cr for iCbCr equal to 1, the following applies: + +- If ChromaArrayType is equal to 1 or 2, the following applies: + - If cTrafo is equal to T\_PCM, the construction process for chroma residuals of I\_PCM macroblocks as specified in clause F.8.5.3.2.1 is invoked with iCbCr and sTCoeff as the inputs and the output is the $(MbWidthC)x(MbHeightC)$ array mbResCX of residual chroma sample values. + - Otherwise (cTrafo is not equal to T\_PCM), the construction process for chroma residuals with ChromaArrayType equal to 1 or 2 as specified in clause F.8.5.3.2.2 is invoked with iCbCr and sTCoeff as the inputs and the output is the $(MbWidthC)x(MbHeightC)$ array mbResCX of residual chroma sample values. +- Otherwise (ChromaArrayType is equal to 3), the construction process for luma residuals or chroma residuals with ChromaArrayType equal to 3 as specified in clause F.8.5.3.1 is invoked with iYCbCr set equal to $(1 + iCbCr)$ , cTrafo, and sTCoeff as the inputs and the output is the $(MbWidthC)x(MbHeightC)$ array mbResCX of residual chroma sample values. + +#### F.8.5.3.2.1 Construction process for chroma residuals of I\_PCM macroblocks + +Inputs to this process are: + +- a variable iCbCr specifying the chroma component, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * MbWidthC * MbHeightC)$ elements. + +Outputs of this process are residual chroma sample values as a $(MbWidthC)x(MbHeightC)$ array mbRes with elements mbRes[ x, y ]. + +The $(MbWidthC)x(MbHeightC)$ array mbRes is derived by + +$$mbRes[ x, y ] = sTCoeff[ 256 + iCbCr * MbWidthC * MbHeightC + y * MbWidthC + x ] \quad (F-186)$$ + +with $x = 0..(MbWidthC - 1)$ and $y = 0..(MbHeightC - 1)$ + +#### F.8.5.3.2.2 Construction process for chroma residuals with ChromaArrayType equal to 1 or 2 + +This process is only invoked when ChromaArrayType is equal to 1 or 2. + +Inputs to this process are: + +- a variable iCbCr specifying the chroma component, +- a list of scaled transform coefficient values sTCoeff with $(256 + 2 * MbWidthC * MbHeightC)$ elements. + +Outputs of this process are residual chroma sample values as a $(MbWidthC)x(MbHeightC)$ array mbRes with elements mbRes[ x, y ]. + +The variables nW, nH, numB, and cO are derived by + +$$nW = MbWidthC / 4 \quad (F-187)$$ + +$$nH = MbHeightC / 4 \quad (F-188)$$ + +$$numB = nW * nH \quad (F-189)$$ + +$$cO = 256 + ( iCbCr * MbWidthC * MbHeightC ) \quad (F-190)$$ + +For the chroma DC transform coefficients of all residual 4x4 chroma blocks, the following ordered steps are specified: + +1. The (nW)x(nH) array *c* with the elements *cij* is derived by + +$$c_{ij} = \text{sTCoeff}[ cO + 32 * i + 16 * j ] \quad \text{with } i = 0..(nH - 1), j = 0..(nW - 1) \quad (\text{F-191})$$ + +2. The transformation process for chroma DC transform coefficients as specified in clause 8.5.11.1 is invoked with BitDepthC and the (nW)x(nH) array *c* as the inputs and the outputs are DC values for all residual 4x4 chroma blocks as a (nW)x(nH) array *f* with elements *fij*. + +3. Depending on ChromaArrayType, the (nW)x(nH) array *dcC* with elements *dcCij* is derived as follows: + +- If ChromaArrayType is equal to 1, + +$$dcC_{ij} = f_{ij} \gg 5 \quad \text{with } i = 0..(nH - 1), j = 0..(nW - 1) \quad (\text{F-192})$$ + +- Otherwise (ChromaArrayType is equal to 2), + +$$dcC_{ij} = ( f_{ij} + ( 1 \ll 5 ) ) \gg 6 \quad \text{with } i = 0..(nH - 1), j = 0..(nW - 1) \quad (\text{F-193})$$ + +The bitstream shall not contain data that result in any element *dcCij* of *dcC* with *i* = 0..(nH – 1) and *j* = 0..(nW – 1) that exceeds the range of integer values from $-2^{(7 + \text{BitDepth}_C)}$ to $2^{(7 + \text{BitDepth}_C)} - 1$ , inclusive. + +NOTE – For the layer representation with dependency\_id equal to 0 and quality\_id equal to 0, successive invocations of clause F.8.5.1.2 (as part of an invocation of clause F.8.5.1) and this clause yield an array *dcC* that is identical to the array *dcC* that would be obtained by an invocation of clause 8.5.11. However, the intermediate values *cij* and *fij* with *i* = 0..(nH – 1) and *j* = 0..(nW – 1) that are derived in this clause can exceed the range of integer values from $-2^{(7 + \text{BitDepth}_C)}$ to $2^{(7 + \text{BitDepth}_C)} - 1$ , inclusive. + +For each residual 4x4 chroma block indexed by *c4x4BlkIdx* = 0..(numB – 1), the following ordered steps are specified. + +1. The 4x4 array *d* with elements *dij* is derived as follows: + +- The element *d00* is derived by: + +$$d_{00} = dcC_{kl} \quad \text{with } k = c4x4BlkIdx / 2 \text{ and } l = c4x4BlkIdx \% 2 \quad (\text{F-194})$$ + +- The elements *dij* with *i, j* = 0..3 and *i + j* > 0 are derived by: + +$$d_{ij} = \text{sTCoeff}[ cO + 16 * c4x4BlkIdx + 4 * i + j ] \quad (\text{F-195})$$ + +2. The transformation process for residual 4x4 blocks as specified in clause 8.5.12.2 is invoked with BitDepthC and the 4x4 array *d* as the inputs and the outputs are residual chroma sample values as a 4x4 array *r* with elements *rij*. + +3. The chroma location ( *xP, yP* ) is derived by: + +$$xP = 4 * ( c4x4BlkIdx \% 2 ) \quad (\text{F-196})$$ + +$$yP = 4 * ( c4x4BlkIdx / 2 ) \quad (\text{F-197})$$ + +4. The elements *mbRes[ x, y ]* of the (MbWidthC)x(MbHeightC) array *mbRes* with *x* = *xP*..(*xP* + 3) and *y* = *yP*..(*yP* + 3) are derived by: + +$$mbRes[ xP + j, yP + i ] = r_{ij} \quad \text{with } i, j = 0..3 \quad (\text{F-198})$$ + +#### F.8.5.4 Sample array accumulation process + +Inputs to this process are: + +- a variable *fieldMbFlag* specifying whether the current macroblock is a field or a frame macroblock, +- a (PicWidthInSamplesL)x(PicHeightInSamplesL) array *picResL* containing residual luma sample values for the current layer representation, +- a (PicWidthInSamplesL)x(PicHeightInSamplesL) array *picSamplesL* containing constructed luma sample values for the current layer representation, +- when ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays *picResCb* and *picResCr* containing residual chroma sample values for the current layer representation, +- when ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays *picSamplesCb* and *picSamplesCr* containing constructed chroma sample values for the current layer representation. + +Outputs of this process are: + +- a modified version of the array *picSamplesL*, + +- when ChromaArrayType is not equal to 0, modified versions of the arrays picSamplesCb and picSamplesCr. + +The macroblock sample array extraction process as specified in clause F.8.5.4.2 is invoked with fieldMbFlag, picResL, and, when ChromaArrayType is not equal to 0, picResCb and picResCr as the inputs and the outputs are assigned to mbResL and, when ChromaArrayType is not equal to 0, mbResCb and mbResCr. + +The macroblock sample array extraction process as specified in clause F.8.5.4.2 is invoked with fieldMbFlag, picSamplesL, and, when ChromaArrayType is not equal to 0, picSamplesCb and picSamplesCr as the inputs and the outputs are assigned to mbPredL and, when ChromaArrayType is not equal to 0, mbPredCb and mbPredCr. + +The 16x16 array mbSamplesL is derived by: + +$$\text{mbSamples}_L[ x, y ] = \text{Clip1}_V( \text{mbPred}_L[ x, y ] + \text{mbRes}_L[ x, y ] ) \quad \text{with } x, y = 0..15 \quad (\text{F-199})$$ + +When ChromaArrayType is not equal to 0, for CX being replaced by Cb and Cr, the (MbWidthC)x(MbHeightC) array mbSamplesCX is derived by: + +$$\text{mbSamples}_{CX}[ x, y ] = \text{Clip1}_C( \text{mbPred}_{CX}[ x, y ] + \text{mbRes}_{CX}[ x, y ] ) \quad \begin{aligned} &\text{with } x = 0..(\text{MbWidthC} - 1) \\ &\text{and } y = 0..(\text{MbHeightC} - 1) \end{aligned} \quad (\text{F-200})$$ + +The picture sample array construction process as specified in clause F.8.5.4.1 is invoked with fieldMbFlag, mbSamplesL, picSamplesL, and, when ChromaArrayType is not equal to 0, mbSamplesCb, mbSamplesCr, picSamplesCb, and picSamplesCr as inputs and the outputs are a modified version of picSamplesL and, when ChromaArrayType is not equal to 0, modified versions of picSamplesCb and picSamplesCr. + +#### F.8.5.4.1 Picture sample array construction process + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a 16x16 array mbArrayL containing luma sample values for the current macroblock, +- a (PicWidthInSamplesL)x(PicWidthInHeightL) array picArrayL containing luma sample values for the current layer representation, +- when ChromaArrayType is not equal to 0, two (MbWidthC)x(MbHeightC) arrays mbArrayCb and mbArrayCr containing chroma sample values for the current macroblock, +- when ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picArrayCb and picArrayCr containing chroma sample values for the current layer representation. + +Outputs of this process are: + +- a modified version of the array picArrayL, +- when ChromaArrayType is not equal to 0, modified versions of the arrays picArrayCb and picArrayCr. + +The picture sample array construction process for a colour component as specified in clause F.8.5.4.3 is invoked with fieldMbFlag, mbW set equal to 16, mbH set equal to 16, mbArrayL, and picArrayL as the inputs and the output is a modified version of the array picArrayL. + +When ChromaArrayType is not equal to 0, for CX being replaced with Cr and Cb, the picture sample array construction process for a colour component as specified in clause F.8.5.4.3 is invoked with fieldMbFlag, mbW set equal to MbWidthC, mbH set equal to MbHeightC, mbArrayCX, and picArrayCX as the inputs and the output is a modified version of the array picArrayCX. + +#### F.8.5.4.2 Macroblock sample array extraction process + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a (PicWidthInSamplesL)x(PicWidthInHeightL) array picArrayL containing luma sample values for the current layer representation, +- when ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picArrayCb and picArrayCr containing chroma sample values for the current layer representation. + +Outputs of this process are: + +- a 16x16 array mbArrayL containing luma sample values for the current macroblock, + +- when ChromaArrayType is not equal to 0, two (MbWidthC)x(MbHeightC) arrays mbArrayCb and mbArrayCr containing chroma sample values for the current macroblock. + +The macroblock sample array extraction process for a colour component as specified in clause F.8.5.4.4 is invoked with fieldMbFlag, mbW set equal to 16, mbH set equal to 16, and picArrayL as the inputs and the output is assigned to mbArrayL. + +When ChromaArrayType is not equal to 0, for CX being replaced with Cr and Cb, the macroblock sample array extraction process for a colour component as specified in clause F.8.5.4.4 is invoked with fieldMbFlag, mbW set equal to MbWidthC, mbH set equal to MbHeightC, and picArrayCX as the inputs and the output is assigned to mbArrayCX. + +#### F.8.5.4.3 Picture sample array construction process for a colour component + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable mbW specifying the width of a macroblock colour component in samples, +- a variable mbH specifying the height of a macroblock colour component in samples, +- an (mbW)x(mbH) array mbArray containing sample values for a colour component of the current macroblock, +- an (mbW \* PicWidthInMbs)x(mbH \* PicHeightInMbs) array picArray containing sample values for a colour component of the current layer representation. + +Output of this process is a modified version of the array picArray. + +The inverse macroblock scanning process as specified in clause 6.4.1 is invoked with CurrMbAddr as the input and the output is assigned to ( xO, yO ). During the process in clause 6.4.1, the current macroblock is treated as field macroblock when fieldMbFlag is equal to 1, and it is treated as frame macroblock when fieldMbFlag is equal to 0. + +The sample location ( xP, yP ) is derived by: + +$$xP = ( xO \gg 4 ) * mbW \quad (F-201)$$ + +$$yP = ( ( yO \gg 4 ) * mbH ) + ( yO \% 2 ) \quad (F-202)$$ + +Depending on the variables MbaffFrameFlag and fieldMbFlag, the array picArray is modified as follows: + +- If MbaffFrameFlag is equal to 1 and fieldMbFlag is equal to 1, + +$$picArray[ xP + x, yP + 2 * y ] = mbArray[ x, y ] \quad \text{with } x = 0..(mbW - 1), y = 0..(mbH - 1) \quad (F-203)$$ + +- Otherwise (MbaffFrameFlag is equal to 0 or fieldMbFlag is equal to 0), + +$$picArray[ xP + x, yP + y ] = mbArray[ x, y ] \quad \text{with } x = 0..(mbW - 1), y = 0..(mbH - 1) \quad (F-204)$$ + +#### F.8.5.4.4 Macroblock sample array extraction process for a colour component + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable mbW specifying the width of a macroblock colour component in samples, +- a variable mbH specifying the height of a macroblock colour component in samples, +- an (mbW \* PicWidthInMbs)x(mbH \* PicHeightInMbs) array picArray containing sample values for a colour component of the current layer representation. + +Output of this process is an (mbW)x(mbH) array mbArray containing sample values for a colour component of the current macroblock. + +The inverse macroblock scanning process as specified in clause 6.4.1 is invoked with CurrMbAddr as the input and the output is assigned to ( xO, yO ). During the process in clause 6.4.1, the current macroblock is treated as field macroblock when fieldMbFlag is equal to 1, and it is treated as frame macroblock when fieldMbFlag is equal to 0. + +The sample location ( xP, yP ) is derived by: + +$$xP = ( xO \gg 4 ) * mbW \quad (F-205)$$ + +$$yP = ( ( yO \gg 4 ) * mbH ) + ( yO \% 2 ) \quad (F-206)$$ + +Depending on the variables MbaffFrameFlag and fieldMbFlag, the samples of the array mbArray are derived as follows: + +- If MbaffFrameFlag is equal to 1 and fieldMbFlag is equal to 1, + +$$\text{mbArray}[ x, y ] = \text{picArray}[ xP + x, yP + 2 * y ] \quad \text{with } x = 0..(\text{mbW} - 1), y = 0..(\text{mbH} - 1) \quad (\text{F-207})$$ + +- Otherwise (MbaffFrameFlag is equal to 0 or fieldMbFlag is equal to 0), + +$$\text{mbArray}[ x, y ] = \text{picArray}[ xP + x, yP + y ] \quad \text{with } x = 0..(\text{mbW} - 1), y = 0..(\text{mbH} - 1) \quad (\text{F-208})$$ + +#### F.8.5.5 Sample array re-initialization process + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a (PicWidthInSamplesL)x(PicHeightInSamplesL) array picSamplesL containing luma sample values for the current layer representation, +- when ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picSamplesCb and picSamplesCr containing chroma sample values for the current layer representation. + +Outputs of this process are: + +- a modified version of the array picSamplesL, +- when ChromaArrayType is not equal to 0, modified versions of the arrays picSamplesCb and picSamplesCr. + +The 16x16 array mbSamplesL is derived by: + +$$\text{mbSamples}_L[ x, y ] = 0 \quad \text{with } x, y = 0..15 \quad (\text{F-209})$$ + +When ChromaArrayType is not equal to 0, for CX being replaced by Cb and Cr, the (MbWidthC)x(MbHeightC) array mbSamplesCX is derived by: + +$$\text{mbSamples}_{CX}[ x, y ] = 0 \quad \text{with } x = 0..(\text{MbWidthC} - 1) \text{ and } y = 0..(\text{MbHeightC} - 1) \quad (\text{F-210})$$ + +The picture sample array construction process as specified in clause F.8.5.4.1 is invoked with fieldMbFlag, mbSamplesL, picSamplesL, and, when ChromaArrayType is not equal to 0, mbSamplesCb, mbSamplesCr, picSamplesCb, and picSamplesCr as inputs and the outputs are a modified version of picSamplesL and, when ChromaArrayType is not equal to 0, modified versions of picSamplesCb and picSamplesCr. + +#### F.8.6 Resampling processes for prediction data, intra samples, and residual samples + +Clause F.8.6.1 specifies the derivation process for inter-layer predictors for macroblock type, sub-macroblock type, references indices, and motion vectors. + +Clause F.8.6.2 specifies the resampling process for intra samples. + +Clause F.8.6.3 specifies the resampling process for residual samples. + +##### F.8.6.1 Derivation process for inter-layer predictors for macroblock type, sub-macroblock type, reference indices, and motion vectors + +This process is only invoked when base\_mode\_flag is equal to 1 or any motion\_prediction\_flag\_IX[ mbPartIdx ] with X being replaced by 0 and 1 and mbPartIdx = 0..3 is equal to 1. + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a one-dimensional array refLayerFieldMbFlag with RefLayerPicSizeInMbs elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array refLayerMbType with RefLayerPicSizeInMbs elements specifying the macroblock types for the macroblocks of the reference layer representation, +- a (RefLayerPicSizeInMbs)x4 array refLayerSubMbType specifying the sub-macroblock types for the macroblocks of the reference layer representation, +- two (RefLayerPicSizeInMbs)x4 arrays refLayerPredFlagL0 and refLayerPredFlagL1 specifying prediction utilization flags for the macroblocks of the reference layer representation, +- two (RefLayerPicSizeInMbs)x4 arrays refLayerRefIdxL0 and refLayerRefIdxL1 specifying reference indices for the macroblocks of the reference layer representation, +- two (RefLayerPicSizeInMbs)x4x4x2 arrays refLayerMvL0 and refLayerMvL1 specifying motion vector components for the macroblocks of the reference layer representation, + +- when `CroppingChangeFlag` is equal to 1 and `(slice_type % 5)` is less than 2, the reference picture list `refPicList0`, +- when `CroppingChangeFlag` is equal to 1 and `(slice_type % 5)` is equal to 1, the reference picture list `refPicList1`. + +Outputs of this process are: + +- a variable `mbTypeILPred` specifying a predictor for the macroblock type of the current macroblock, +- a list `subMbTypeILPred` with 4 elements specifying predictors for sub-macroblock types of the current macroblock, +- two 2x2 arrays `refIdxILPredL0` and `refIdxILPredL1` specifying inter-layer predictors for the reference indices of the current macroblock, +- two 4x4x2 arrays `mvILPredL0` and `mvILPredL1` specifying inter-layer predictors for the motion vector components of the current macroblock. + +The derivation process for reference layer partition identifications as specified in clause F.8.6.1.1 is invoked with `fieldMbFlag`, `refLayerFieldMbFlag`, `refLayerMbType`, and `refLayerSubMbType` as the inputs and the outputs are a variable `intraILPredFlag` and, when `intraILPredFlag` is equal to 0, reference layer partition identifications as a 4x4 array `refLayerPartIdc` with elements `refLayerPartIdc[ x, y ]`. + +When `slice_type` is equal to EI, the bitstream shall not contain data that result in `intraILPredFlag` equal to 0. + +Depending on `intraILPredFlag`, the 2x2 arrays `refIdxILPredL0` and `refIdxILPredL1` and the 4x4x2 array `mvILPredL0` and `mvILPredL1` are derived as follows: + +- If `intraILPredFlag` is equal to 1, all elements of the 2x2 arrays `refIdxILPredL0` and `refIdxILPredL1` are set equal to `-1` and all elements of the 4x4x2 arrays `mvILPredL0` and `mvILPredL1` are set equal to 0. +- Otherwise (`intraILPredFlag` is equal to 0), the derivation process for inter-layer predictors for reference indices and motion vectors as specified in clause F.8.6.1.2 is invoked with `fieldMbFlag`, `refLayerFieldMbFlag`, `refLayerPredFlagL0`, `refLayerPredFlagL1`, `refLayerRefIdxL0`, `refLayerRefIdxL1`, `refLayerMvL0`, `refLayerMvL1`, `refLayerPartIdc`, `refPicList0` (when available), and `refPicList1` (when available) as the inputs and the outputs are the arrays `refIdxILPredL0`, `refIdxILPredL1`, `mvILPredL0`, and `mvILPredL1`. + +Depending on `intraILPredFlag`, the variable `mbTypeILPred` and the list `subMbTypeILPred` are derived as follows: + +- If `intraILPredFlag` is equal to 1, all elements `subMbTypeILPred[ mbPartIdx ]` of the list `subMbTypeILPred` with `mbPartIdx = 0..3` are marked as unspecified, and the variable `mbTypeILPred` is derived as follows: + - If `tcoeff_level_prediction_flag` is equal to 1, `mbTypeILPred` is set equal to `refLayerMbType[ CurrMbAddr ]`. + - Otherwise (`tcoeff_level_prediction_flag` is equal to 0), `mbTypeILPred` is set equal to `I_BL`. +- Otherwise (`intraILPredFlag` is equal to 0), the derivation process for inter-layer predictors for P and B macroblock and sub-macroblock types as specified in clause F.8.6.1.3 is invoked with `refIdxILPredL0`, `refIdxILPredL1`, `mvILPredL0`, and `mvILPredL1` as the inputs and the outputs are the variable `mbTypeILPred` and the list `subMbTypeILPred`. + +#### F.8.6.1.1 Derivation process for reference layer partition identifications + +Inputs to this process are: + +- a variable `fieldMbFlag` specifying whether the current macroblock is a field or a frame macroblock, +- a one-dimensional array `refLayerFieldMbFlag` with `ReflayerPicSizeInMbs` elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array `refLayerMbType` with `ReflayerPicSizeInMbs` elements specifying the macroblock types for the macroblocks of the reference layer representation, +- a (`ReflayerPicSizeInMbs`)x4 array `refLayerSubMbType` specifying the sub-macroblock types for the macroblocks of the reference layer representation. + +Outputs of this process are: + +- a variable `intraILPredFlag` specifying whether the samples of the current macroblock in the current layer representation can be predicted by inter-layer intra prediction or, in the case of `tcoeff_level_prediction_flag` equal to 1, by a combination of intra-layer intra prediction and inter-layer prediction, +- when `intraILPredFlag` is equal to 0, reference layer partition identifications for the current macroblock as a 4x4 array `refLayerPartIdc` with elements `refLayerPartIdc[ x, y ]`. + +When the 4x4 array `refLayerPartIdc` is output of this process, each of its elements `refLayerPartIdc[ x, y ]` specifies the macroblock address, the macroblock partition index, and the sub-macroblock partition index of the partition in the reference layer representation that can be used for inter-layer motion prediction of the macroblock or sub-macroblock partition of the current macroblock that contains the 4x4 block with coordinates `x` and `y`. + +For each 4x4 block with block coordinates `x, y = 0..3`, the element `refLayerPartIdc[ x, y ]` of the 4x4 array `refLayerPartIdc` is derived by applying the following ordered steps: + +1. The derivation process for reference layer partitions as specified in clause F.6.2 is invoked with the luma location $( 4 * x + 1, 4 * y + 1 )$ , `fieldMbFlag`, `refLayerFieldMbFlag`, `refLayerMbType`, and `refLayerSubMbType` as the inputs and the outputs are a macroblock address `refMbAddr`, a macroblock partition index `refMbPartIdx`, and a sub-macroblock partition index `refSubMbPartIdx` of a partition in the reference layer representation. +2. The element `refLayerPartIdc[ x, y ]` of the array `refLayerPartIdc` is derived as follows: + - If `refLayerMbType[ refMbAddr ]` is equal to `I_PCM`, `I_16x16`, `I_8x8`, `I_4x4`, or `I_BL`, `refLayerPartIdc[ x, y ]` is set equal to `-1`. + - Otherwise (`refLayerMbType[ refMbAddr ]` is not equal to `I_PCM`, `I_16x16`, `I_8x8`, `I_4x4`, or `I_BL`), `refLayerPartIdc[ x, y ]` is derived by + +$$\text{refLayerPartIdc}[ x, y ] = 16 * \text{refMbAddr} + 4 * \text{refMbPartIdx} + \text{refSubMbPartIdx} \quad (\text{F-211})$$ + +The variable `intraILPredFlag` is derived as follows: + +- If all elements `refLayerPartIdc[ x, y ]` with `x, y = 0..3` are equal to `-1`, `intraILPredFlag` is set equal to `1`. +- Otherwise (any element `refLayerPartIdc[ x, y ]` with `x, y = 0..3` is not equal to `-1`), `intraILPredFlag` is set equal to `0`. + +When `intraILPredFlag` is equal to `0` and `RestrictedSpatialResolutionChangeFlag` is equal to `0`, the 4x4 array `refLayerPartIdc` is modified by the following ordered steps: + +1. For each 8x8 block with block coordinates `xP, yP = 0..1`, the following ordered steps are specified. + - a. The variables `xO` and `yO` are set equal to $( 2 * xP )$ and $( 2 * yP )$ , respectively. + - b. All elements `procI4x4Blk[ xS, yS ]` of the 2x2 array `procI4x4Blk` with `xS, yS = 0..1` are set equal to `0`. + - c. The 4x4 blocks of the current 8x8 block with block coordinates `xS, yS = 0..1` are processed in increasing order of $( 2 * yS + xS )$ , and when `refLayerPartIdc[ xO + xS, yO + yS ]` is equal to `-1` for a 4x4 block, the element `procI4x4Blk[ xS, yS ]` of the array `procI4x4Blk` is set equal to `1` and the following applies: + - If `procI4x4Blk[ 1 - xS, yS ]` is equal to `0` and `refLayerPartIdc[ xO + 1 - xS, yO + yS ]` is not equal to `-1`, the element `refLayerPartIdc[ xO + xS, yO + yS ]` is modified by + +$$\text{refLayerPartIdc}[ xO + xS, yO + yS ] = \text{refLayerPartIdc}[ xO + 1 - xS, yO + yS ] \quad (\text{F-212})$$ + +- Otherwise, if `procI4x4Blk[ xS, 1 - yS ]` is equal to `0` and `refLayerPartIdc[ xO + xS, yO + 1 - yS ]` is not equal to `-1`, the element `refLayerPartIdc[ xO + xS, yO + yS ]` is modified by + +$$\text{refLayerPartIdc}[ xO + xS, yO + yS ] = \text{refLayerPartIdc}[ xO + xS, yO + 1 - yS ] \quad (\text{F-213})$$ + +- Otherwise, if `procI4x4Blk[ 1 - xS, 1 - yS ]` is equal to `0` and `refLayerPartIdc[ xO + 1 - xS, yO + 1 - yS ]` is not equal to `-1`, the element `refLayerPartIdc[ xO + xS, yO + yS ]` is modified by + +$$\text{refLayerPartIdc}[ xO + xS, yO + yS ] = \text{refLayerPartIdc}[ xO + 1 - xS, yO + 1 - yS ] \quad (\text{F-214})$$ + +- Otherwise, the element `refLayerPartIdc[ xO + xS, yO + yS ]` is not modified. + +2. All elements `procI8x8Blk[ xP, yP ]` of the 2x2 array `procI8x8Blk` with `xP, yP = 0..1` are set equal to `0`. +3. The 8x8 blocks with block coordinates `xP, yP = 0..1` are processed in increasing order of $( 2 * yP + xP )$ , and when `refLayerPartIdc[ 2 * xP, 2 * yP ]` is equal to `-1` for an 8x8 block, the element `procI8x8Blk[ xP, yP ]` of the array `procI8x8Blk` is set equal to `1` and the following applies: + - If `procI8x8Blk[ 1 - xP, yP ]` is equal to `0` and `refLayerPartIdc[ 2 - xP, 2 * yP ]` is not equal to `-1`, the elements `refLayerPartIdc[ 2 * xP + xS, 2 * yP + yS ]` with `xS, yS = 0..1` are modified by + +$$\text{refLayerPartIdc}[ 2 * xP + xS, 2 * yP + yS ] = \text{refLayerPartIdc}[ 2 - xP, 2 * yP + yS ] \quad (\text{F-215})$$ + +- Otherwise, if $\text{proc18x8Blk}[ xP, 1 - yP ]$ is equal to 0 and $\text{refLayerPartIdc}[ 2 * xP, 2 - yP ]$ is not equal to $-1$ , the elements $\text{refLayerPartIdc}[ 2 * xP + xS, 2 * yP + yS ]$ with $xS, yS = 0..1$ are modified by + +$$\text{refLayerPartIdc}[ 2 * xP + xS, 2 * yP + yS ] = \text{refLayerPartIdc}[ 2 * xP + xS, 2 - yP ] \quad (\text{F-216})$$ + +- Otherwise, if $\text{proc18x8Blk}[ 1 - xP, 1 - yP ]$ is equal to 0 and $\text{refLayerPartIdc}[ 2 - xP, 2 - yP ]$ is not equal to $-1$ , the elements $\text{refLayerPartIdc}[ 2 * xP + xS, 2 * yP + yS ]$ with $xS, yS = 0..1$ are modified by + +$$\text{refLayerPartIdc}[ 2 * xP + xS, 2 * yP + yS ] = \text{refLayerPartIdc}[ 2 - xP, 2 - yP ] \quad (\text{F-217})$$ + +- Otherwise, the elements $\text{refLayerPartIdc}[ 2 * xP + xS, 2 * yP + yS ]$ with $xS, yS = 0..1$ are not modified. + +NOTE – By the process specified above the elements $\text{refLayerPartIdc}[ x, y ]$ that are equal to $-1$ are replaced by elements $\text{refLayerPartIdc}[ x, y ]$ that are not equal to $-1$ . This process can also be applied when $\text{RestrictedSpatialResolutionChangeFlag}$ is equal to 1 or $\text{intraLPredFlag}$ is equal to 1, but in this case, the 4x4 array $\text{refLayerPartIdc}$ is not modified. + +#### F.8.6.1.2 Derivation process for inter-layer predictors for reference indices and motion vectors + +Inputs to this process are: + +- a variable $\text{fieldMbFlag}$ specifying whether the current macroblock is a field or a frame macroblock, +- a one-dimensional array $\text{refLayerFieldMbFlag}$ with $\text{RefLayerPicSizeInMbs}$ elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- two $(\text{RefLayerPicSizeInMbs}) \times 4$ arrays $\text{refLayerPredFlagL0}$ and $\text{refLayerPredFlagL1}$ specifying prediction utilization flags for the macroblocks of the reference layer representation, +- two $(\text{RefLayerPicSizeInMbs}) \times 4$ arrays $\text{refLayerRefIdxL0}$ and $\text{refLayerRefIdxL1}$ specifying reference indices for the macroblocks of the reference layer representation, +- two $(\text{RefLayerPicSizeInMbs}) \times 4 \times 4 \times 2$ arrays $\text{refLayerMvL0}$ and $\text{refLayerMvL1}$ specifying motion vector components for the macroblocks of the reference layer representation, +- a 4x4 array $\text{refLayerPartIdc}$ specifying reference layer partition identifications for the 4x4 blocks of the current macroblock, +- when $\text{CroppingChangeFlag}$ is equal to 1 and $(\text{slic\_type} \% 5)$ is less than 2, the reference picture list $\text{refPicList0}$ , +- when $\text{CroppingChangeFlag}$ is equal to 1 and $(\text{slic\_type} \% 5)$ is equal to 1, the reference picture list $\text{refPicList1}$ . + +Outputs of this process are: + +- two 2x2 arrays $\text{refIdxILPredL0}$ and $\text{refIdxILPredL1}$ specifying inter-layer predictors for the reference indices of the current macroblock, +- two 4x4x2 arrays $\text{mvILPredL0}$ and $\text{mvILPredL1}$ specifying inter-layer predictors for the motion vector components of the current macroblock. + +Let $\text{tempRefIdxPredL0}$ and $\text{tempRefIdxPredL1}$ be two 4x4 arrays with elements $\text{tempRefIdxPredL0}[ x, y ]$ and $\text{tempRefIdxPredL1}[ x, y ]$ , respectively, that specify auxiliary inter-layer predictors for reference indices. + +For each 4x4 block indexed by $x, y = 0..3$ and for $X$ being replaced by 0 and 1, the auxiliary reference index predictor $\text{tempRefIdxPredLX}[ x, y ]$ and the motion vector predictor $\text{mvILPredLX}[ x, y ]$ are derived as follows: + +- If $\text{refLayerPredFlagLX}[ \text{refLayerPartIdc}[ x, y ] / 16 ] [ ( \text{refLayerPartIdc}[ x, y ] \% 16 ) / 4 ]$ is equal 0, the reference index predictor $\text{tempRefIdxPredLX}[ x, y ]$ and the motion vector predictor $\text{mvILPredLX}[ x, y ]$ are derived by: + +$$\text{tempRefIdxPredLX}[ x, y ] = -1 \quad (\text{F-218})$$ + +$$\text{mvILPredLX}[ x, y ] [ 0 ] = 0 \quad (\text{F-219})$$ + +$$\text{mvILPredLX}[ x, y ] [ 1 ] = 0 \quad (\text{F-220})$$ + +- Otherwise ( $\text{refLayerPredFlagLX}[ \text{refLayerPartIdc}[ x, y ] / 16 ] [ ( \text{refLayerPartIdc}[ x, y ] \% 16 ) / 4 ]$ is equal to 1), the following ordered steps are specified: + +1. The variables $\text{refMbAddr}$ , $\text{refMbPartIdx}$ , and $\text{refSubMbPartIdx}$ are derived by + +$$\text{refMbAddr} = \text{refLayerPartIdc}[ x, y ] / 16 \quad (\text{F-221})$$ + +$$\text{refMbPartIdx} = ( \text{refLayerPartIdc}[ x, y ] \% 16 ) / 4 \quad (\text{F-222})$$ + +$$\text{refSubMbPartIdx} = \text{refLayerPartIdc}[ x, y ] \% 4 \quad (\text{F-223})$$ + +2. The auxiliary reference index predictor tempRefIdxPredLX[ x, y ] is derived by: + +$$\begin{aligned} \text{tempRefIdxPredLX}[ x, y ] = & \text{refLayerRefIdxLX}[ \text{refMbAddr} ][ \text{refMbPartIdx} ] \\ & * ( 1 + \text{fieldMbFlag} - \text{field\_pic\_flag} ) \\ & / ( 1 + \text{refLayerFieldMbFlag}[ \text{refMbAddr} ] - \text{RefLayerFieldPicFlag} ) \end{aligned} \quad (\text{F-224})$$ + +3. The motion vector aMv is set equal to refLayerMvLX[ refMbAddr ][ refMbPartIdx ][ refSubMbPartIdx ], and afterwards its vertical component aMv[ 1 ] is modified by: + +$$\text{aMv}[ 1 ] = \text{aMv}[ 1 ] * ( 1 + \text{refLayerFieldMbFlag}[ \text{refMbAddr} ] ) \quad (\text{F-225})$$ + +4. The variables scaledW, scaledH, refLayerW, and refLayerH are derived by: + +$$\text{scaledW} = \text{ScaledRefLayerPicWidthInSamples}_L \quad (\text{F-226})$$ + +$$\text{scaledH} = \text{ScaledRefLayerPicHeightInSamples}_L * ( 1 + \text{field\_pic\_flag} ) \quad (\text{F-227})$$ + +$$\text{refLayerW} = \text{RefLayerPicWidthInSamples}_L \quad (\text{F-228})$$ + +$$\text{refLayerH} = \text{RefLayerPicHeightInSamples}_L * ( 1 + \text{RefLayerFieldPicFlag} ) \quad (\text{F-229})$$ + +5. The variables dOX, dOY, dSW, and dSH are derived as follows: + +- If CroppingChangeFlag is equal to 0 or the reference picture refPicListX[ tempRefIdxPredLX[ x, y ] ] is not available, dOX, dOY, dSW, and dSH are set equal to 0. +- Otherwise (CroppingChangeFlag is equal to 1 and the reference picture refPicListX[ tempRefIdxPredLX[ x, y ] ] is available), the variables refPicScaledRefLayerLeftOffset, refPicScaledRefLayerRightOffset, refPicScaledRefLayerTopOffset, and refPicScaledRefLayerBottomOffset are set equal to the variables ScaledRefLayerLeftOffset, ScaledRefLayerRightOffset, ScaledRefLayerTopOffset, and ScaledRefLayerBottomOffset, respectively, that are associated with the layer representation of the reference picture refPicListX[ tempRefIdxPredLX[ x, y ] ] that has the same value of DQId as the current layer representation, and the variables dOX, dOY, dSW, and dSH are derived by: + +$$\text{dOX} = \text{ScaledRefLayerLeftOffset} - \text{refPicScaledRefLayerLeftOffset} \quad (\text{F-230})$$ + +$$\text{dOY} = \text{ScaledRefLayerTopOffset} - \text{refPicScaledRefLayerTopOffset} \quad (\text{F-231})$$ + +$$\text{dSW} = \text{ScaledRefLayerRightOffset} - \text{refPicScaledRefLayerRightOffset} + \text{dOX} \quad (\text{F-232})$$ + +$$\text{dSH} = \text{ScaledRefLayerBottomOffset} - \text{refPicScaledRefLayerBottomOffset} + \text{dOY} \quad (\text{F-233})$$ + +6. The variables scaleX and scaleY are derived by: + +$$\text{scaleX} = ( ( ( \text{scaledW} + \text{dSW} ) \ll 16 ) + ( \text{refLayerW} \gg 1 ) ) / \text{refLayerW} \quad (\text{F-234})$$ + +$$\text{scaleY} = ( ( ( \text{scaledH} + \text{dSH} ) \ll 16 ) + ( \text{refLayerH} \gg 1 ) ) / \text{refLayerH} \quad (\text{F-235})$$ + +7. The motion vector aMv is scaled by: + +$$\text{aMv}[ 0 ] = ( \text{aMv}[ 0 ] * \text{scaleX} + 32768 ) \gg 16 \quad (\text{F-236})$$ + +$$\text{aMv}[ 1 ] = ( \text{aMv}[ 1 ] * \text{scaleY} + 32768 ) \gg 16 \quad (\text{F-237})$$ + +8. When CroppingChangeFlag is equal to 1, the motion vector aMv is modified by applying the following ordered steps: + +- a. The inverse macroblock scanning process as specified in clause 6.4.1 is invoked with CurrMbAddr as the input and the output is a luma location ( xMbPic, yMbPic ). For this invocation of the process specified in clause 6.4.1, the current macroblock is treated as field macroblock when fieldMbFlag is equal to 1, and it is treated as frame macroblock when fieldMbFlag is equal to 0. + +- b. The luma location ( xFrm, yFrm ) is derived by: + +$$\text{xFrm} = ( \text{xMbPic} + ( 4 * x + 1 ) ) \quad (\text{F-238})$$ + +$$\text{yFrm} = ( \text{yMbPic} + ( 4 * y + 1 ) * ( 1 + \text{fieldMbFlag} - \text{field\_pic\_flag} ) ) * ( 1 + \text{field\_pic\_flag} ) \quad (\text{F-239})$$ + +- c. The variables scaleX and scaleY are modified by: + +$$\text{scaleX} = ( ( ( 4 * \text{dSW} ) \ll 16 ) + ( \text{scaledW} \gg 1 ) ) / \text{scaledW} \quad (\text{F-240})$$ + +$$\text{scaleY} = ( ( ( 4 * \text{dSH} ) \ll 16 ) + ( \text{scaledH} \gg 1 ) ) / \text{scaledH} \quad (\text{F-241})$$ + +- d. The motion vector aMv is modified by: + +$$\text{aMv}[ 0 ] += ( ( ( \text{xFrm} - \text{ScaledReflLayerLeftOffset} ) * \text{scaleX} + 32768 ) \gg 16 ) - 4 * \text{dOX} \quad (\text{F-242})$$ + +$$\text{aMv}[ 1 ] += ( ( ( \text{yFrm} - \text{ScaledReflLayerTopOffset} ) * \text{scaleY} + 32768 ) \gg 16 ) - 4 * \text{dOY} \quad (\text{F-243})$$ + +9. The motion vector predictor mvILPredLX[ x, y ] is derived by: + +$$\text{mvILPredLX}[ x, y ][ 0 ] = \text{aMv}[ 0 ] \quad (\text{F-244})$$ + +$$\text{mvILPredLX}[ x, y ][ 1 ] = \text{aMv}[ 1 ] / ( 1 + \text{fieldMbFlag} ) \quad (\text{F-245})$$ + +For each 8x8 block indexed by xP, yP = 0..1 and for X being replaced by 0 or 1, the reference index predictor refIdxILPredLX[ xP, yP ] is set equal to tempRefIdxPredLX[ 2 \* xP, 2 \* yP ], and when RestrictedSpatialResolutionChangeFlag is equal to 0, the following ordered steps are specified: + +1. The 4x4 blocks indexed by xS, yS = 0..1 of the current 8x8 block are processed in increasing order of (2 \* yS + xS), and for each 4x4 block, the reference index predictor refIdxILPredLX[ xP, yP ] is modified by: + +$$\text{refIdxILPredLX}[ xP, yP ] = \text{MinPositive}( \text{refIdxILPredLX}[ xP, yP ], \text{tempRefIdxPredLX}[ 2 * xP + xS, 2 * yP + yS ] ) \quad (\text{F-246})$$ + +with + +$$\text{MinPositive}( a, b ) = \begin{cases} \text{Min}( a, b ) & \text{if } a \geq 0 \text{ and } b \geq 0 \\ \text{Max}( a, b ) & \text{otherwise} \end{cases} \quad (\text{F-247})$$ + +2. The 4x4 blocks indexed by xS, yS = 0..1 of the current 8x8 block are processed in increasing order of (2 \* yS + xS), and for each 4x4 block, when tempRefIdxPredLX[ 2 \* xP + xS, 2 \* yP + yS ] is not equal to the reference index predictor refIdxILPredLX[ xP, yP ], the following applies: + +- If tempRefIdxPredLX[ 2 \* xP + 1 - xS, 2 \* yP + yS ] is equal to refIdxILPredLX[ xP, yP ], the motion vector predictor mvILPredLX[ 2 \* xP + xS, 2 \* yP + yS ] is modified by: + +$$\text{mvILPredLX}[ 2 * xP + xS, 2 * yP + yS ] = \text{mvILPredLX}[ 2 * xP + 1 - xS, 2 * yP + yS ] \quad (\text{F-248})$$ + +- Otherwise, if tempRefIdxPredLX[ 2 \* xP + xS, 2 \* yP + 1 - yS ] is equal to refIdxILPredLX[ xP, yP ], the motion vector predictor mvILPredLX[ 2 \* xP + xS, 2 \* yP + yS ] is modified by: + +$$\text{mvILPredLX}[ 2 * xP + xS, 2 * yP + yS ] = \text{mvILPredLX}[ 2 * xP + xS, 2 * yP + 1 - yS ] \quad (\text{F-249})$$ + +- Otherwise (tempRefIdxPredLX[ 2 \* xP + 1 - xS, 2 \* yP + 1 - yS ] is equal to refIdxILPredLX[ xP, yP ]), the motion vector predictor mvILPredLX[ 2 \* xP + xS, 2 \* yP + yS ] is modified by: + +$$\text{mvILPredLX}[ 2 * xP + xS, 2 * yP + yS ] = \text{mvILPredLX}[ 2 * xP + 1 - xS, 2 * yP + 1 - yS ] \quad (\text{F-250})$$ + +NOTE – The process specified above can also be applied when RestrictedSpatialResolutionChangeFlag is equal to 1, but in this case, the reference index predictor refIdxILPredLX[ xP, yP ] and the motion vector predictors mvILPredLX[ 2 \* xP + xS, 2 \* yP + yS ] with xS, yS = 0..1 will not be modified. + +When RestrictedSpatialResolutionChangeFlag is equal to 0, slice\_type is equal to EB, and direct\_8x8\_inference\_flag is equal to 1, for each 8x8 block indexed by xP, yP = 0..1 and for X being replaced by 0 or 1, the following ordered steps are specified: + +1. The motion vector tempMv with components tempMv[ 0 ] and tempMv[ 1 ] is derived by: + +$$\text{tempMv}[ c ] = \text{mvILPredX}[ 3 * xP, 3 * yP ][ c ] \quad \text{with } c = 0..1 \quad (\text{F-251})$$ + +2. The array mvILPredLX is modified by: + +$$\text{mvILPredLX}[ 2 * xP + xS, 2 * yP + yS ][ c ] = \text{tempMv}[ c ] \quad \text{with } xS, yS = 0..1 \text{ and } c = 0..1 \quad (\text{F-252})$$ + +When RestrictedSpatialResolutionChangeFlag is equal to 0, for each 8x8 block indexed by xP, yP = 0..1, the motion vector predictor arrays mvILPredL0 and mvILPredL1 are modified by applying the following ordered steps: + +1. The variable maxX is derived as follows: + +- If slice\_type is equal to EB, maxX is set equal to 1. + +- Otherwise (slice\_type is equal to EP), maxX is set equal to 0. +- The variables xO and yO are set equal to (2 \* xP) and (2 \* yP), respectively. + - The function mvDiff( mv1, mv2 ) of two motion vectors mv1 and mv2 is defined by + +$$\text{mvDiff( mv}_1, \text{mv}_2 \text{ )} = \text{Abs( mv}_1[ 0 ] - \text{mv}_2[ 0 ] ) + \text{Abs( mv}_1[ 1 ] - \text{mv}_2[ 1 ] ) \quad (\text{F-253})$$ + +- The variable subPartSize is derived as follows: + +- If for X = 0..maxX, all of the following conditions are true, subPartSize is set equal to 8x8. + - mvDiff( mvILPredLX[ xO, yO ], mvILPredLX[ xO + 1, yO ] ) is less than or equal to 1 + - mvDiff( mvILPredLX[ xO, yO ], mvILPredLX[ xO, yO + 1 ] ) is less than or equal to 1 + - mvDiff( mvILPredLX[ xO, yO ], mvILPredLX[ xO + 1, yO + 1 ] ) is less than or equal to 1 +- Otherwise, if for X = 0..maxX, all of the following conditions are true, subPartSize is set equal to 8x4. + - mvDiff( mvILPredLX[ xO, yO ], mvILPredLX[ xO + 1, yO ] ) is less than or equal to 1 + - mvDiff( mvILPredLX[ xO, yO + 1 ], mvILPredLX[ xO + 1, yO + 1 ] ) is less than or equal to 1 +- Otherwise, if for X = 0..maxX, all of the following conditions are true, subPartSize is set equal to 4x8. + - mvDiff( mvILPredLX[ xO, yO ], mvILPredLX[ xO, yO + 1 ] ) is less than or equal to 1 + - mvDiff( mvILPredLX[ xO + 1, yO ], mvILPredLX[ xO + 1, yO + 1 ] ) is less than or equal to 1 +- Otherwise, subPartSize is set equal to 4x4. + +- When subPartSize is not equal to 4x4, for X = 0..maxX, the motion vectors tempMvALX and tempMvBLX (when subPartSize is equal to 8x4 or 4x8) are derived as follows: + +- If subPartSize is equal to 8x8, tempMvALX is derived by + +$$\begin{aligned} \text{tempMvALX[ c ]} = & ( \text{mvILPredLX[ xO, yO ]}[ c ] + \\ & \text{mvILPredLX[ xO + 1, yO ]}[ c ] + \\ & \text{mvILPredLX[ xO, yO + 1 ]}[ c ] + \\ & \text{mvILPredLX[ xO + 1, yO + 1 ]}[ c ] + 2 ) \gg 2 \quad \text{with } c = 0..1 \end{aligned} \quad (\text{F-254})$$ + +- Otherwise, if subPartSize is equal to 8x4, tempMvALX and tempMvBLX are derived by + +$$\begin{aligned} \text{tempMvALX[ c ]} = & ( \text{mvILPredLX[ xO, yO ]}[ c ] + \\ & \text{mvILPredLX[ xO + 1, yO ]}[ c ] + 1 ) \gg 1 \quad \text{with } c = 0..1 \end{aligned} \quad (\text{F-255})$$ + +$$\begin{aligned} \text{tempMvBLX[ c ]} = & ( \text{mvILPredLX[ xO, yO + 1 ]}[ c ] + \\ & \text{mvILPredLX[ xO + 1, yO + 1 ]}[ c ] + 1 ) \gg 1 \quad \text{with } c = 0..1 \end{aligned} \quad (\text{F-256})$$ + +- Otherwise (subPartSize is equal to 4x8), tempMvALX and tempMvBLX are derived by + +$$\begin{aligned} \text{tempMvALX[ c ]} = & ( \text{mvILPredLX[ xO, yO ]}[ c ] + \\ & \text{mvILPredLX[ xO, yO + 1 ]}[ c ] + 1 ) \gg 1 \quad \text{with } c = 0..1 \end{aligned} \quad (\text{F-257})$$ + +$$\begin{aligned} \text{tempMvBLX[ c ]} = & ( \text{mvILPredLX[ xO + 1, yO ]}[ c ] + \\ & \text{mvILPredLX[ xO + 1, yO + 1 ]}[ c ] + 1 ) \gg 1 \quad \text{with } c = 0..1 \end{aligned} \quad (\text{F-258})$$ + +- When subPartSize is not equal to 4x4, for X = 0..maxX, the motion vector predictor array mvILPredLX is modified as follows: + +- If subPartSize is equal to 8x8, the array mvILPredLX is modified by + +$$\text{mvILPredLX[ xO + xS, yO + yS ]}[ c ] = \text{tempMvALX[ c ]} \quad \text{with } xS, yS = 0..1 \text{ and } c = 0..1 \quad (\text{F-259})$$ + +- Otherwise, if subPartSize is equal to 8x4, the array mvILPredLX is modified by + +$$\text{mvILPredLX[ xO + xS, yO ]}[ c ] = \text{tempMvALX[ c ]} \quad \text{with } xS = 0..1 \text{ and } c = 0..1 \quad (\text{F-260})$$ + +$$\text{mvILPredLX[ xO + xS, yO + 1 ]}[ c ] = \text{tempMvBLX[ c ]} \quad \text{with } xS = 0..1 \text{ and } c = 0..1 \quad (\text{F-261})$$ + +- Otherwise (subPartSize is equal to 4x8), the array mvILPredLX is modified by + +$$\text{mvILPredLX}[ xO, yO + yS ][ c ] = \text{tempMvALX}[ c ] \quad \text{with } yS = 0..1 \text{ and } c = 0..1 \quad (\text{F-262})$$ + +$$\text{mvILPredLX}[ xO + 1, yO + yS ][ c ] = \text{tempMvBLX}[ c ] \quad \text{with } yS = 0..1 \text{ and } c = 0..1 \quad (\text{F-263})$$ + +### F.8.6.1.3 Derivation process for inter-layer predictors for P and B macroblock and sub-macroblock types + +This process is only invoked when slice\_type is equal to EP or EB. + +Inputs to this process are: + +- two 2x2 arrays refIdxILPredL0 and refIdxILPredL1 specifying predictors for the reference indices of the current macroblock, +- two 4x4x2 arrays mvILPredL0 and mvILPredL1 specifying predictors for the motion vectors of the current macroblock. + +Outputs of this process are: + +- a variable mbTypeILPred specifying a predictor for the macroblock type of the current macroblock, +- a list subMbTypeILPred with 4 elements specifying predictors for sub-macroblock types of the current macroblock. + +The variable maxX is derived as follows: + +- If slice\_type is equal to EB, maxX is set equal to 1. +- Otherwise (slice\_type is equal to EP), maxX is set equal to 0. + +The macroblock type predictor mbTypeILPred is derived by applying the following ordered steps: + +1. The variable partitionSize is derived as follows: + - If for X = 0..maxX, all of the following conditions are true, partitionSize is set equal to 16x16. + - all elements refIdxILPredLX[ x, y ] with x, y = 0..1 are the same + - all elements mvILPredLX[ x, y ] with x, y = 0..3 are the same + - Otherwise, if for X = 0..maxX, all of the following conditions are true, partitionSize is set equal to 16x8. + - refIdxILPredLX[ 0, 0 ] is equal to refIdxILPredLX[ 1, 0 ] + - refIdxILPredLX[ 0, 1 ] is equal to refIdxILPredLX[ 1, 1 ] + - all elements mvILPredLX[ x, y ] with x = 0..3 and y = 0..1 are the same + - all elements mvILPredLX[ x, y ] with x = 0..3 and y = 2..3 are the same + - Otherwise, if for X = 0..maxX, all of the following conditions are true, partitionSize is set equal to 8x16. + - refIdxILPredLX[ 0, 0 ] is equal to refIdxILPredLX[ 0, 1 ] + - refIdxILPredLX[ 1, 0 ] is equal to refIdxILPredLX[ 1, 1 ] + - all elements mvILPredLX[ x, y ] with x = 0..1 and y = 0..3 are the same + - all elements mvILPredLX[ x, y ] with x = 2..3 and y = 0..3 are the same + - Otherwise, partitionSize is set equal to 8x8. +2. When slice\_type is equal to EB and partitionSize is not equal to 8x8, the variable partPredModeA is derived by + +$$\text{partPredModeA} = ( ( \text{refIdxILPredL1}[ 0, 0 ] \geq 0 ) ? 2 : 0 ) + ( ( \text{refIdxILPredL0}[ 0, 0 ] \geq 0 ) ? 1 : 0 ) \quad (\text{F-264})$$ + +3. When slice\_type is equal to EB and partitionSize is equal to 16x8 or 8x16, the variable partPredModeB is derived by + +$$\text{partPredModeB} = ( ( \text{refIdxILPredL1}[ 1, 1 ] \geq 0 ) ? 2 : 0 ) + ( ( \text{refIdxILPredL0}[ 1, 1 ] \geq 0 ) ? 1 : 0 ) \quad (\text{F-265})$$ + +4. Depending on slice\_type, partitionSize, partPredModeA (when applicable), and partPredModeB (when applicable), the macroblock type predictor mbTypeILPred is derived as specified in Table F-7. + +All elements `subMbTypeILPred[ mbPartIdx ]` of the list `subMbTypeILPred` with `mbPartIdx = 0..3` are marked as "unspecified". + +When `mbTypeILPred` is equal to `P_8x8` or `B_8x8`, each element `subMbTypeILPred[ mbPartIdx ]` with `mbPartIdx = 0..3` is modified by applying the following ordered steps: + +1. The coordinate offset ( `xO, yO` ) is set equal to $( 2 * ( mbPartIdx \% 2 ), 2 * ( mbPartIdx / 2 ) )$ . +2. The variable `subPartitionSize` is derived as follows: + - If for `X = 0..maxX`, all elements `mvILPredLX[ xO + xS, yO + yS ]` with `xS, yS = 0..1` are the same, `subPartitionSize` is set equal to `8x8`. + - Otherwise, if for `X = 0..maxX`, `mvILPredLX[ xO, yO ]` is equal to `mvILPredLX[ xO + 1, yO ]` and `mvILPredLX[ xO, yO + 1 ]` is equal to `mvILPredLX[ xO + 1, yO + 1 ]`, `subPartitionSize` is set equal to `8x4`. + - Otherwise, if for `X = 0..maxX`, `mvILPredLX[ xO, yO ]` is equal to `mvILPredLX[ xO, yO + 1 ]` and `mvILPredLX[ xO + 1, yO ]` is equal to `mvILPredLX[ xO + 1, yO + 1 ]`, `subPartitionSize` is set equal to `4x8`. + - Otherwise, `subPartitionSize` is set equal to `4x4`. +3. When `slice_type` is equal to `EB`, the variable `partPredMode` is derived by + +$$\text{partPredMode} = ( ( \text{refIdxILPredL1}[ xO / 2, yO / 2 ] \geq 0 ) ? 2 : 0 ) + ( ( \text{refIdxILPredL0}[ xO / 2, yO / 2 ] \geq 0 ) ? 1 : 0 ) \quad (\text{F-266})$$ + +4. Depending on `slice_type`, `subPartitionSize`, and `partPredMode` (when applicable), the sub-macroblock type predictor `subMbTypeILPred[ mbPartIdx ]` is derived as specified in Table F-8. + +**Table F-7 – Macroblock type predictors `mbTypeILPred`** + +| slice_type | partitionSize | partPredModeA | partPredModeB | mbTypeILPred | slice_type | partitionSize | partPredModeA | partPredModeB | mbTypeILPred | +|-------------------------|----------------------------|----------------------------|----------------------------|---------------------------|-------------------------|----------------------------|----------------------------|----------------------------|---------------------------| +| EB | 16x16 | 1 | na | B_L0_16x16 | EB | 16x8 | 2 | 3 | B_L1_Bi_16x8 | +| EB | 16x16 | 2 | na | B_L1_16x16 | EB | 8x16 | 2 | 3 | B_L1_Bi_8x16 | +| EB | 16x16 | 3 | na | B_Bi_16x16 | EB | 16x8 | 3 | 1 | B_Bi_L0_16x8 | +| EB | 16x8 | 1 | 1 | B_L0_L0_16x8 | EB | 8x16 | 3 | 1 | B_Bi_L0_8x16 | +| EB | 8x16 | 1 | 1 | B_L0_L0_8x16 | EB | 16x8 | 3 | 2 | B_Bi_L1_16x8 | +| EB | 16x8 | 2 | 2 | B_L1_L1_16x8 | EB | 8x16 | 3 | 2 | B_Bi_L1_8x16 | +| EB | 8x16 | 2 | 2 | B_L1_L1_8x16 | EB | 16x8 | 3 | 3 | B_Bi_Bi_16x8 | +| EB | 16x8 | 1 | 2 | B_L0_L1_16x8 | EB | 8x16 | 3 | 3 | B_Bi_Bi_8x16 | +| EB | 8x16 | 1 | 2 | B_L0_L1_8x16 | EB | 8x8 | na | na | B_8x8 | +| EB | 16x8 | 2 | 1 | B_L1_L0_16x8 | EP | 16x16 | na | na | P_L0_16x16 | +| EB | 8x16 | 2 | 1 | B_L1_L0_8x16 | EP | 16x8 | na | na | P_L0_L0_16x8 | +| EB | 16x8 | 1 | 3 | B_L0_Bi_16x8 | EP | 8x16 | na | na | P_L0_L0_8x16 | +| EB | 8x16 | 1 | 3 | B_L0_Bi_8x16 | EP | 8x8 | na | na | P_8x8 | + +**Table F-8 – Sub-macroblock type predictors subMbTypeILPred[ mbPartIdx ]** + +| slice_type | subPartitionSize | partPredMode | subMbTypeILPred
[ mbPartIdx ] | slice_type | subPartitionSize | partPredMode | subMbTypeILPred
[ mbPartIdx ] | +|------------|------------------|--------------|----------------------------------|------------|------------------|--------------|----------------------------------| +| EB | 8x8 | 1 | B_L0_8x8 | EB | 4x8 | 3 | B_Bi_4x8 | +| EB | 8x8 | 2 | B_L1_8x8 | EB | 4x4 | 1 | B_L0_4x4 | +| EB | 8x8 | 3 | B_Bi_8x8 | EB | 4x4 | 2 | B_L1_4x4 | +| EB | 8x4 | 1 | B_L0_8x4 | EB | 4x4 | 3 | B_Bi_4x4 | +| EB | 8x4 | 2 | B_L1_8x4 | EP | 8x8 | na | P_L0_8x8 | +| EB | 8x4 | 3 | B_Bi_8x4 | EP | 8x4 | na | P_L0_8x4 | +| EB | 4x8 | 1 | B_L0_4x8 | EP | 4x8 | na | P_L0_4x8 | +| EB | 4x8 | 2 | B_L1_4x8 | EP | 4x4 | na | P_L0_4x4 | + +### F.8.6.2 Resampling process for intra samples + +Inputs to this process are: + +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a one-dimensional array refLayerSliceIdc with RefLayerPicSizeInMbs elements specifying slice identifications for the macroblocks of the reference layer representation, +- a one-dimensional array refLayerFieldMbFlag with RefLayerPicSizeInMbs elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array refLayerMbType with RefLayerPicSizeInMbs elements specifying macroblock types for the macroblocks of the reference layer representation, +- a (RefLayerPicWidthInSamplesL)x(RefLayerPicHeightInSamplesL) array refLayerPicSamplesL of luma samples for the reference layer representation, +- a (PicWidthInSamplesL)x(PicHeightInSamplesL) array picSamplesL of luma samples, +- when ChromaArrayType is not equal to 0, two (RefLayerPicWidthInSamplesC)x(RefLayerPicHeightInSamplesC) arrays refLayerPicSamplesCb and refLayerPicSamplesCr of chroma samples for the reference layer representation, +- when ChromaArrayType is not equal to 0, two (PicWidthInSamplesC)x(PicHeightInSamplesC) arrays picSamplesCb and picSamplesCr of chroma samples. + +Outputs of this process are: + +- a modified version of the array picSamplesL of luma samples, +- when ChromaArrayType is not equal to 0, modified versions of the arrays picSamplesCb and picSamplesCr of chroma samples. + +The resampling process for intra samples of a macroblock colour component as specified in clause F.8.6.2.1 is invoked with chromaFlag equal to 0, mbW equal to 16, mbH equal to 16, fieldMbFlag, refLayerPicSamplesL, refLayerSliceIdc, refLayerFieldMbFlag, and refLayerMbType as the inputs and the output is the 16x16 array mbPredL of Intra\_Base prediction samples for the luma component of the current macroblock. + +When ChromaArrayType is not equal to 0, for CX being replaced by Cb and Cr, the resampling process for intra samples of a macroblock colour component as specified in clause F.8.6.2.1 is invoked with chromaFlag equal to 1, mbW equal to MbWidthC, mbH equal to MbHeightC, fieldMbFlag, refLayerPicSamplesCX, refLayerSliceIdc, refLayerFieldMbFlag, and refLayerMbType as the inputs and the output is the (MbWidthC)x(MbHeightC) array mbPredCX of Intra\_Base prediction samples for the CX component of the current macroblock. + +The picture sample array construction process as specified in clause F.8.5.4.1 is invoked with fieldMbFlag, mbPredL, picSamplesL and, when ChromaArrayType is not equal to 0, mbPredcb, mbPredcr, picSamplescb, and picSamplescr as the inputs and the outputs are a modified version of picSamplesL and, when ChromaArrayType is not equal to 0, modified versions of picSamplescb, and picSamplescr. + +#### F.8.6.2.1 Resampling process for intra samples of a macroblock colour component + +Inputs to this process are: + +- a variable chromaFlag specifying whether the luma or a chroma component is subject to the resampling process, +- two variables mbW and mbH specifying the width and height, respectively, of a macroblock for the considered colour component, +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- an array refLayerPicSamples, which is a (RefLayerPicWidthInSamplesL)x(RefLayerPicHeightInSamplesL) array containing constructed intra luma sample values for the reference layer representation when chromaFlag is equal to 0 or a (RefLayerPicWidthInSamplesC)x(RefLayerPicHeightInSamplesC) array containing constructed intra chroma sample values for the reference layer representation when chromaFlag is equal to 1, +- a one-dimensional array refLayerSliceIdc with RefLayerPicSizeInMbs elements specifying slice identifications for the macroblocks of the reference layer representation, +- a one-dimensional array refLayerFieldMbFlag with RefLayerPicSizeInMbs elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array refLayerMbType with RefLayerPicSizeInMbs elements specifying macroblock types for the macroblocks of the reference layer representation. + +Output of this process is an (mbW)x(mbH) array mbPred of Intra\_Base prediction samples. + +The variable botFieldFlag is derived as follows: + +- If RefLayerFrameMbsOnlyFlag is equal to 1, botFieldFlag is set equal to 0. +- Otherwise, if field\_pic\_flag is equal to 1, botFieldFlag is set equal to bottom\_field\_flag. +- Otherwise, if RefLayerFieldPicFlag is equal to 1, botFieldFlag is set equal to RefLayerBottomFieldFlag. +- Otherwise, if fieldMbFlag is equal to 1, botFieldFlag is set equal to (CurrMbAddr % 2). +- Otherwise, botFieldFlag is set equal to 0. + +The variable frameBasedResamplingFlag is derived as follows: + +- If all of the following conditions are true, frameBasedResamplingFlag is set equal to 1: + - RefLayerFrameMbsOnlyFlag is equal to 1, + - frame\_mbs\_only\_flag is equal to 1. +- Otherwise, frameBasedResamplingFlag is set equal to 0. + +The variable topAndBotResamplingFlag is derived as follows: + +- If all of the following conditions are true, topAndBotResamplingFlag is set equal to 1: + - RefLayerFrameMbsOnlyFlag is equal to 0, + - RefLayerFieldPicFlag is equal to 0, + - frame\_mbs\_only\_flag is equal to 0, + - fieldMbFlag is equal to 0. +- Otherwise, topAndBotResamplingFlag is set equal to 0. + +The variable botFieldFrameMbsOnlyRefFlag is derived as follows: + +- If RefLayerFrameMbsOnlyFlag is equal to 1, fieldMbFlag is equal to 1, and any of the following conditions are true, botFieldFrameMbsOnlyRefFlag is set equal to 1: + - field\_pic\_flag is equal to 1 and bottom\_field\_flag is equal to 1, + - field\_pic\_flag is equal to 0 and ( CurrMbAddr % 2 ) is equal to 1, + +- Otherwise, botFieldFrameMbsOnlyRefFlag is set equal to 0. + +The variable filteringModeFlag is derived as follows: + +- If chromaFlag is equal to 0 or ChromaArrayType is equal to 3, filteringModeFlag is set equal to 0. +- Otherwise (chromaFlag is equal to 1 and ChromaArrayType is not equal to 3), filteringModeFlag is set equal to 1. + +The array predArray is derived as specified in the following. + +- If botFieldFrameMbsOnlyRefFlag is equal to 1, the following ordered steps are specified: + 1. The reference layer sample array construction process prior to intra resampling as specified in clause F.8.6.2.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, refLayerPicSamples, refLayerSliceIdc, refLayerFieldMbFlag, and refLayerMbType as the inputs and the outputs are the variables refArrayW, refArrayH, the array refSampleArray of reference layer sample values, and the variables xOffset and yOffset. + 2. The variable yBorder is set equal to $( 2 - \text{chromaFlag} )$ . + 3. The interpolation process for Intra\_Base prediction as specified in clause F.8.6.2.3 is invoked with filteringModeFlag, chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, fldPrdInFrmMbFlag equal to 0, yBorder, refArrayW, refArrayH, refSampleArray, xOffset, and yOffset as the inputs and the output is the $(\text{mbW}) \times (\text{mbH} + 2 * \text{yBorder})$ array topFldPredArray of top field prediction samples. + 4. The vertical interpolation process for Intra\_Base prediction as specified in clause F.8.6.2.4 is invoked with filteringModeFlag, chromaFlag, mbW, mbH, botFieldFlag, yBorder, frameMbFlag equal to 0, and topFldPredArray as the inputs and the output is the $(\text{mbW}) \times (\text{mbH})$ array mbPred of Intra\_Base prediction samples. +- Otherwise, if frameBasedResamplingFlag is equal to 1 or fieldMbFlag is equal to 1, the following ordered steps are specified: + 1. The reference layer sample array construction process prior to intra resampling as specified in clause F.8.6.2.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, refLayerPicSamples, refLayerSliceIdc, refLayerFieldMbFlag, and refLayerMbType as the inputs and the outputs are the variables refArrayW, refArrayH, the array refSampleArray of reference layer sample values, and the variables xOffset and yOffset. + 2. The interpolation process for Intra\_Base prediction as specified in clause F.8.6.2.3 is invoked with filteringModeFlag, chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, fldPrdInFrmMbFlag equal to 0, yBorder equal to 0, refArrayW, refArrayH, refSampleArray, xOffset, and yOffset as the inputs and the output is the $(\text{mbW}) \times (\text{mbH})$ array mbPred of Intra\_Base prediction samples. +- Otherwise, if topAndBotResamplingFlag is equal to 0, the following ordered steps are specified: + 1. The reference layer sample array construction process prior to intra resampling as specified in clause F.8.6.2.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, refLayerPicSamples, refLayerSliceIdc, refLayerFieldMbFlag, and refLayerMbType as the inputs and the outputs are the variables refArrayW, refArrayH, the array refSampleArray of reference layer sample values, and the variables xOffset and yOffset. + 2. The variable yBorder is set equal to $( 2 - \text{chromaFlag} )$ . + 3. The interpolation process for Intra\_Base prediction as specified in clause F.8.6.2.3 is invoked with filteringModeFlag, chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, fldPrdInFrmMbFlag equal to 1, yBorder, refArrayW, refArrayH, refSampleArray, xOffset, and yOffset as the inputs and the output is the $(\text{mbW}) \times (\text{mbH} / 2 + 2 * \text{yBorder})$ array fieldPredArray of field prediction samples. + 4. The vertical interpolation process for Intra\_Base prediction as specified in clause F.8.6.2.4 is invoked with filteringModeFlag, chromaFlag, mbW, mbH, botFieldFlag, yBorder, frameMbFlag equal to 1, and fieldPredArray as the inputs and the output is the $(\text{mbW}) \times (\text{mbH})$ array mbPred of Intra\_Base prediction samples. +- Otherwise (topAndBotResamplingFlag is equal to 1), the following ordered steps are specified: + 1. The reference layer sample array construction process prior to intra resampling as specified in clause F.8.6.2.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag equal to 0, refLayerPicSamples, refLayerSliceIdc, refLayerFieldMbFlag, and refLayerMbType as the inputs and the outputs are the variables refArrayTopW, refArrayTopH, the array refSampleArrayTop of top field reference layer sample values, and the variables xOffsetTop and yOffsetTop. + 2. The interpolation process for Intra\_Base prediction as specified in clause F.8.6.2.3 is invoked with filteringModeFlag, chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag equal to 0, fldPrdInFrmMbFlag equal + +to 1, yBorder equal to 0, refArrayTopW, refArrayTopH, refSampleArrayTop, xOffsetTop, and yOffsetTop as the inputs and the output is the (mbW)x(mbH / 2) array topFieldPredArray of top field prediction samples. + +3. The reference layer sample array construction process prior to intra resampling as specified in clause F.8.6.2.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag equal to 1, refLayerPicSamples, refLayerSliceIdc, refLayerFieldMbFlag, and refLayerMbType as the inputs and the outputs are the variables refArrayBotW, refArrayBotH, the array refSampleArrayBot of bottom field reference layer sample values, and the variables xOffsetBot and yOffsetBot. +4. The interpolation process for Intra\_Base prediction as specified in clause F.8.6.2.3 is invoked with filteringModeFlag, chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag equal to 1, fldPrdInFrmMbFlag equal to 1, yBorder equal to 0, refArrayBotW, refArrayBotH, refSampleArrayBot, xOffsetBot, and yOffsetBot as the inputs and the output is the (mbW)x(mbH / 2) array botFieldPredArray of bottom field prediction samples. +5. Each sample predArray[ x, y ] with x = 0..(mbW - 1) and y = 0..(mbH - 1) of the array mbPred of Intra\_Base prediction samples is derived by: + +$$\text{mbPred}[ x, y ] = ( ( ( y \% 2 ) == 0 ) ? \text{topFieldPredArray}[ x, y \gg 1 ] : \text{botFieldPredArray}[ x, y \gg 1 ] ) \quad (\text{F-267})$$ + +#### F.8.6.2.2 Reference layer sample array construction process prior to intra resampling + +Inputs to this process are: + +- a variable chromaFlag specifying whether the luma or a chroma component is subject to the resampling process, +- two variables mbW and mbH specifying the width and height, respectively, of a macroblock for the considered colour component, +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable botFieldFlag specifying whether a top or a bottom field is subject to the resampling process (when RefLayerFrameMbsOnlyFlag is equal to 0 or frame\_mbs\_only\_flag is equal to 0), +- an array refLayerPicSamples, which is a (RefLayerPicWidthInSamplesL)x(RefLayerPicHeightInSamplesL) array containing constructed intra luma sample values for the reference layer representation when chromaFlag is equal to 0 or a (RefLayerPicWidthInSamplesC)x(RefLayerPicHeightInSamplesC) array containing constructed intra chroma sample values for the reference layer representation when chromaFlag is equal to 1, +- a one-dimensional array refLayerSliceIdc with RefLayerPicSizeInMbs elements specifying slice identifications for the macroblocks of the reference layer representation, +- a one-dimensional array refLayerFieldMbFlag with RefLayerPicSizeInMbs elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array refLayerMbType with RefLayerPicSizeInMbs elements specifying macroblock types for the macroblocks of the reference layer representation. + +Outputs of this process are: + +- two variables refArrayW and refArrayH specifying the width and height, respectively, of the constructed array of reference layer sample values, +- a (refArrayW)x(refArrayH) array refSampleArray of reference layer sample values, +- two variables xOffset and yOffset specifying the x and y coordinate, respectively, of the reference layer sample location that corresponds to the sample refSampleArray[ 0, 0 ] of the array refSampleArray. + +The variables refW, refH, refMbW, refMbH, xOffset, yOffset, refArrayW, refArrayH, xMin, yMin, xMax, yMax, yRefScale, and yRefAdd are derived as specified in the following ordered steps: + +1. The derivation process for reference layer sample locations in resampling as specified in clause F.6.3 is invoked with chromaFlag, the sample location ( 0, 0 ), fieldMbFlag, and botFieldFlag as the inputs and the output is the sample location ( xRefMin16, yRefMin16 ) in units of 1/16-th sample. +2. The derivation process for reference layer sample locations in resampling as specified in clause F.6.3 is invoked with chromaFlag, the sample location ( mbW - 1, mbH - 1 ), fieldMbFlag, and botFieldFlag as the inputs and the output is the sample location ( xRefMax16, yRefMax16 ) in units of 1/16-th sample. +3. With Z being replaced by L for chromaFlag equal to 0 and C for chromaFlag equal to 1, the variables refW, refH, refMbW, and refMbH are derived by: + +``` + +refW = RefLayerPicWidthInSamplesz (F-268) +refH = RefLayerPicHeightInSamplesz (F-269) +refMbW = ( ( chromaFlag == 0 ) ? 16 : RefLayerMbWidthC ) (F-270) +refMbH = ( ( chromaFlag == 0 ) ? 16 : RefLayerMbHeightC ) (F-271) + +``` + +4. The variables xOffset, yOffset, refArrayW, and refArrayH are derived by: + +``` + +xOffset = ( ( ( xRefMin16 - 64 ) >> 8 ) << 4 ) - ( refMbW >> 1 ) (F-272) +yOffset = ( ( ( yRefMin16 - 64 ) >> 8 ) << 4 ) - ( refMbH >> 1 ) (F-273) +refArrayW = ( ( ( xRefMax16 + 79 ) >> 8 ) << 4 ) + 3 * ( refMbW >> 1 ) - xOffset (F-274) +refArrayH = ( ( ( yRefMax16 + 79 ) >> 8 ) << 4 ) + 3 * ( refMbH >> 1 ) - yOffset (F-275) + +``` + +NOTE 1 – The derived array size might be larger than the array size that is actually required by the interpolation process for Intra\_Base prediction specified in clause F.8.6.2.3. + +5. The variables xMin, yMin, xMax, and yMax are derived by: + +``` + +xMin = ( xRefMin16 >> 4 ) - xOffset (F-276) +yMin = ( yRefMin16 >> 4 ) - yOffset (F-277) +xMax = ( ( xRefMax16 + 15 ) >> 4 ) - xOffset (F-278) +yMax = ( ( yRefMax16 + 15 ) >> 4 ) - yOffset (F-279) + +``` + +6. The variables yRefScale and yRefAdd are derived as follows: + +- If RefLayerFrameMbsOnlyFlag is equal to 1 or RefLayerFieldPicFlag is equal to 1, yRefScale is set equal to 1 and yRefAdd is set equal to 0. +- Otherwise (RefLayerFrameMbsOnlyFlag is equal to 0 and RefLayerFieldPicFlag is equal to 0), yRefScale is set equal to 2 and yRefAdd is set equal to botFieldFlag. + +The variable refSliceIdcMb is marked as "not available". + +When constrained\_intra\_resampling\_flag is equal to 1, the variable y proceeds over the values (yMin + 1)..(yMax - 1) and for each value of y, the variable x proceeds over the values (xMin + 1)..(xMax - 1), and for each pair ( x, y ), the following ordered steps are specified: + +1. A reference layer sample location ( xRef, yRef ) is derived by: + +``` + +xRef = Max( 0, Min( refW - 1, x + xOffset ) ) (F-280) +yRef = yRefScale * Max( 0, Min( refH / yRefScale - 1, y + yOffset ) ) + yRefAdd (F-281) + +``` + +2. The derivation process for reference layer slice and intra macroblock identifications as specified in clause F.8.6.2.2.1 is invoked with the reference layer sample location ( xRef, yRef ), refMbW, refMbH, refLayerSliceIdc, refLayerFieldMbFlag, and refLayerMbType as the inputs and the outputs are the reference layer slice identification refSliceIdc and the variable refIntraMbFlag. +3. When refIntraMbFlag is equal to 1 and refSliceIdcMb is marked as "not available", the variable refSliceIdcMb is marked as "available" and set equal to refSliceIdc. + +When constrained\_intra\_resampling\_flag is equal to 1, the following ordered steps are specified: + +1. The variable useIntraPredFlag is set equal to 0. +2. For x proceeding over the values 0..15 and y proceeding over the values 0..15, the following ordered steps are specified: + - a. The derivation process for reference layer macroblocks as specified in clause F.6.1 is invoked with the luma location ( x, y ), fieldMbFlag, refLayerFieldMbFlag, and refLayerMbType as the inputs and the outputs are assigned to mbAddrRefLayer and ( xRef, yRef ). + - b. When refLayerMbType[ mbAddrRefLayer ] is equal to I\_PCM, I\_16x16, I\_8x8, I\_4x4, or I\_BL, the variable useIntraPredFlag is set equal to 1. +3. When useIntraPredFlag is equal to 1, it is a requirement of bitstream conformance that the bitstream shall not contain data that result in refSliceIdcMb being marked as "not available". + +Each sample $\text{refSampleArray}[ x, y ]$ with $x = 0..(\text{refArrayW} - 1)$ and $y = 0..(\text{refArrayH} - 1)$ is derived as specified in the following ordered steps: + +1. A reference layer sample location $( xRef, yRef )$ is derived by + +$$xRef = \text{Max}( 0, \text{Min}( \text{refW} - 1, x + xOffset ) ) \quad (\text{F-282})$$ + +$$yRef = yRefScale * \text{Max}( 0, \text{Min}( \text{refH} / yRefScale - 1, y + yOffset ) ) + yRefAdd \quad (\text{F-283})$$ + +2. The derivation process for reference layer slice and intra macroblock identifications as specified in clause F.8.6.2.2.1 is invoked with the reference layer sample location $( xRef, yRef )$ , $\text{refMbW}$ , $\text{refMbH}$ , $\text{refLayerSliceIdc}$ , $\text{refLayerFieldMbFlag}$ , and $\text{refLayerMbType}$ as the inputs and the outputs are the reference layer slice identification $\text{refSliceIdc}$ and the variable $\text{refIntraMbFlag}$ . +3. When $\text{constrained\_intra\_resampling\_flag}$ is equal to 1, $\text{refIntraMbFlag}$ is equal to 1, $x$ is greater than $xMin$ , $x$ is less than $xMax$ , $y$ is greater than $yMin$ , and $y$ is less than $yMax$ , it is a requirement of bitstream conformance that the bitstream shall not contain data that result in $\text{refSliceIdc}$ being not equal to $\text{refSliceIdcMb}$ . + +NOTE 2 – This constraint specifies that a macroblock cannot be coded with $\text{base\_mode\_flag}$ equal to 1 when it covers intra-coded macroblocks of more than one slice in the reference layer representation, $\text{constrained\_intra\_resampling\_flag}$ is equal to 1, and either the inferred macroblock type is equal to $I\_BL$ or the conditions for invoking the intra-inter prediction combination process as specified in clause F.8.4.2.2 are fulfilled. + +4. Depending on $\text{refIntraMbFlag}$ , $\text{constrained\_intra\_resampling\_flag}$ , and $\text{refSliceIdc}$ , the following applies: + +- If any of the following conditions are true, the sample $\text{refSampleArray}[ x, y ]$ is marked as "not available for Intra\_Base prediction" and its value is set equal to 0: + - $\text{refIntraMbFlag}$ is equal to 0, + - $\text{constrained\_intra\_resampling\_flag}$ is equal to 1 and $\text{refSliceIdcMb}$ is marked as "not available", + - $\text{constrained\_intra\_resampling\_flag}$ is equal to 1 and $\text{refSliceIdc}$ is not equal to $\text{refSliceIdcMb}$ . +- Otherwise, the sample $\text{refSampleArray}[ x, y ]$ is marked as "available for Intra\_Base prediction" and its value is derived by + +$$\text{refSampleArray}[ x, y ] = \text{refLayerPicSamples}[ xRef, yRef ] \quad (\text{F-284})$$ + +The construction process for not available sample values prior to intra resampling as specified in clause F.8.6.2.2.2 is invoked with $\text{refMbW}$ , $\text{refMbH}$ , $\text{refArrayW}$ , $\text{refArrayH}$ , $\text{refSampleArray}$ , $xOffset$ , and $yOffset$ as the inputs and the output is a modified version of the sample array $\text{refSampleArray}$ . + +#### F.8.6.2.2.1 Derivation process for reference layer slice and intra macroblock identifications + +Inputs to this process are: + +- a reference layer sample location $( xRef, yRef )$ relative to the upper-left sample of the considered colour component of the reference layer picture, +- two variables $\text{refMbW}$ and $\text{refMbH}$ specifying the width and height, respectively, of a reference layer macroblock for the considered colour component, +- a one-dimensional array $\text{refLayerSliceIdc}$ with $\text{ReflayerPicSizeInMbs}$ elements specifying slice identifications for the macroblocks of the reference layer representation, +- a one-dimensional array $\text{refLayerFieldMbFlag}$ with $\text{ReflayerPicSizeInMbs}$ elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array $\text{refLayerMbType}$ with $\text{ReflayerPicSizeInMbs}$ elements specifying macroblock types for the macroblocks of the reference layer representation. + +Outputs of this process are: + +- a reference layer slice identification $\text{refSliceIdc}$ for the slice that covers the input reference layer sample location, +- a variable $\text{refIntraMbFlag}$ specifying whether the reference layer macroblock that covers the input reference layer sample location is intra coded. + +The reference layer macroblock address $\text{refMbAddr}$ is derived as follows: + +- If $\text{ReflayerMbaffFrameFlag}$ is equal to 0, the variable $\text{refMbAddr}$ is derived by + +$$\text{refMbAddr} = ( yRef / \text{refMbH} ) * \text{ReflayerPicWidthInMbs} + ( xRef / \text{refMbW} ) \quad (\text{F-285})$$ + +- Otherwise (RefLayerMbAffFrameFlag is equal to 1), the variable refMbAddr is derived as specified in the following ordered steps: + +1. A variable refMbAddrTop is derived by + +$$\text{refMbAddrTop} = 2 * ( ( yRef / ( 2 * \text{refMbH} ) ) * \text{RefLayerPicWidthInMbs} + ( xRef / \text{refMbW} ) ) \quad (\text{F-286})$$ + +2. Depending on refLayerFieldMbFlag[ refMbAddrTop ], the variable refMbAddr is derived as follows: + +- If refLayerFieldMbFlag[ refMbAddrTop ] is equal to 0, the variable refMbAddr is derived by + +$$\text{refMbAddr} = \text{refMbAddrTop} + ( yRef \% ( 2 * \text{refMbH} ) ) / \text{refMbH} \quad (\text{F-287})$$ + +- Otherwise (refLayerFieldMbFlag[ refMbAddrTop ] is equal to 1), the variable refMbAddr is derived by + +$$\text{refMbAddr} = \text{refMbAddrTop} + ( yRef \% 2 ) \quad (\text{F-288})$$ + +The reference layer slice identification refSliceIdc is set equal to refLayerSliceIdc[ refMbAddr ]. + +Depending on refLayerMbType[ refMbAddr ], the variable refIntraMbFlag is derived as follows: + +- If refLayerMbType[ refMbAddr ] is equal to I\_4x4, I\_8x8, I\_16x16, I\_PCM, or I\_BL, refIntraMbFlag is set equal to 1. +- Otherwise (refLayerMbType[ refMbAddr ] is not equal to I\_4x4, I\_8x8, I\_16x16, I\_PCM, or I\_BL), refIntraMbFlag is set equal to 0. + +#### F.8.6.2.2.2 Construction process for not available sample values prior to intra resampling + +Inputs to this process are: + +- two variables refMbW and refMbH specifying the width and height, respectively, of a reference layer macroblock for the considered colour component, +- two variables refArrayW and refArrayH specifying the width and height, respectively, of the array of reference layer sample values, +- a (refArrayW)x(refArrayH) array refSampleArray of reference layer sample values, +- two variables xOffset and yOffset specifying the x and y coordinates, respectively, of the reference layer sample location that corresponds to the sample refSampleArray[ 0, 0 ] of the array refSampleArray. + +Output of this process is a modified version of the array refSampleArray. + +For each sample refSampleArray[ x, y ] with $x = (\text{refMbW} / 2)..(\text{refArrayW} - \text{refMbW} / 2 - 1)$ and $y = (\text{refMbH} / 2)..(\text{refArrayH} - \text{refMbH} / 2 - 1)$ that is marked as "not available for Intra\_Base prediction", the following ordered steps are specified: + +1. The sample location difference ( xD, yD ) and the variable yA are derived by + +$$xR = ( x + \text{xOffset} ) \% \text{refMbW} \quad (\text{F-289})$$ + +$$yR = ( y + \text{yOffset} ) \% \text{refMbH} \quad (\text{F-290})$$ + +$$xD = ( ( xR \geq \text{refMbW} / 2 ) ? ( xR - \text{refMbW} ) : ( xR + 1 ) ) \quad (\text{F-291})$$ + +$$yD = ( ( yR \geq \text{refMbH} / 2 ) ? ( yR - \text{refMbH} ) : ( yR + 1 ) ) \quad (\text{F-292})$$ + +$$yA = yD - ( \text{refMbH} / 2 + 1 ) * \text{Sign}( yD ) \quad (\text{F-293})$$ + +2. When any of the following conditions are true, yD is set equal to yA: + +- the sample refSampleArray[ x, y - yD ] is marked as "not available for Intra\_Base prediction", the sample refSampleArray[ x, y - yA ] is marked as "available for Intra\_Base prediction", and the sample refSampleArray[ x - xD, y ] is marked as "available for Intra\_Base prediction", +- all of the samples refSampleArray[ x - xD, y ], refSampleArray[ x, y - yD ], and refSampleArray[ x - xD, y - yD ] are marked as "not available for Intra\_Base prediction" and any of the samples refSampleArray[ x, y - yA ] and refSampleArray[ x - xD, y - yA ] is marked as "available for Intra\_base prediction", +- Abs( yA ) is less than Abs( yD ) and any of the following conditions are true: + - both samples refSampleArray[ x, y - yD ] and refSampleArray[ x, y - yA ] are marked as "available for Intra\_Base prediction", + +- any of the samples `refSampleArray[ x, y - yD ]` and `refSampleArray[ x - xD, y - yD ]` is marked as "available for Intra\_Base prediction", any of the samples `refSampleArray[ x, y - yA ]` and `refSampleArray[ x - xD, y - yA ]` is marked as "available for Intra\_Base prediction", and the sample `refSampleArray[ x - xD, y ]` is marked as "not available for Intra\_Base prediction". + +NOTE – The variable `yD` is never set equal to `yA` when `ReflayerFrameMbsOnlyFlag` is equal to 1 or `ReflayerFieldPicFlag` is equal to 1. + +3. The sample value `refSampleArray[ x, y ]` is derived as follows: + +- If the sample `refSampleArray[ x - xD, y ]` and the sample `refSampleArray[ x, y - yD ]` are marked as "available for Intra\_Base prediction", the following ordered steps are specified: + - a. A variable `cornerSampleAvailableFlag` is derived as follows: + - If the sample `refSampleArray[ x - xD, y - yD ]` is marked as "available for Intra\_Base prediction", the variable `cornerSampleAvailableFlag` is set equal to 1. + - Otherwise (the sample `refSampleArray[ x - xD, y - yD ]` is marked as "not available for Intra\_Base prediction"), the variable `cornerSampleAvailable` is set equal to 0. + - b. The diagonal construction process for not available sample values as specified in clause F.8.6.2.2.2.1 is invoked with `refArrayW`, `refArrayH`, `refSampleArray`, the sample location difference ( `xD, yD` ), the sample location ( `x, y` ), and the variable `cornerSampleAvailableFlag` as the inputs and the output is the sample array `refSampleArray` with a modified sample value at sample location ( `x, y` ). +- Otherwise (the sample `refSampleArray[ x - xD, y ]` or the sample `refSampleArray[ x, y - yD ]` is marked as "not available for Intra\_Base prediction"), the following applies: + - If the sample `refSampleArray[ x - xD, y ]` is marked as "available for Intra\_Base prediction", the sample value `refSampleArray[ x, y ]` is set equal to `refSampleArray[ x - xD, y ]`. + - Otherwise, if the sample `refSampleArray[ x, y - yD ]` is marked as "available for Intra\_Base prediction", the sample value `refSampleArray[ x, y ]` is set equal to `refSampleArray[ x, y - yD ]`. + - Otherwise, if the sample `refSampleArray[ x - xD, y - yD ]` is marked as "available for Intra\_Base prediction", the sample value `refSampleArray[ x, y ]` is set equal to `refSampleArray[ x - xD, y - yD ]`. + - Otherwise (the samples `refSampleArray[ x - xD, y ]`, `refSampleArray[ x, y - yD ]`, and `refSampleArray[ x - xD, y - yD ]` are marked as "not available for Intra\_Base prediction"), the sample value `refSampleArray[ x, y ]` is not modified. + +All samples `refSampleArray[ x, y ]` with `x = 0..(refArrayW - 1)` and `y = 0..(refArrayH - 1)` are marked as "available for Intra\_Base prediction". + +#### F.8.6.2.2.2.1 Diagonal construction process for not available sample values + +Inputs to this process are: + +- two variables `refArrayW` and `refArrayH` specifying the width and height, respectively, of the array of reference layer sample values, +- a `(refArrayW)x(refArrayH)` array `p` of reference layer sample values, +- a sample location difference ( `xD, yD` ), +- a sample location ( `x, y` ) inside the reference layer sample array `refSampleArray`, +- a variable `cornerSampleAvailableFlag`. + +Output of this process is the sample array `p` with a modified sample value at sample location ( `x, y` ). + +The variables `diffHorVer` and `sgnXY` are derived by + +$$\text{diffHorVer} = \text{Abs}( xD ) - \text{Abs}( yD ) \quad (\text{F-294})$$ + +$$\text{sgnXY} = \text{Sign}( xD * yD ) \quad (\text{F-295})$$ + +When `cornerSampleAvailableFlag` is equal to 0, the following ordered steps are specified: + +1. The variable `cornerSample` is set equal to `p[ x - xD, y - yD ]`. +2. The sample location ( `xC, yC` ) is set equal to ( `x - xD + Sign( xD )`, `y - yD + Sign( yD )` ) and the sample value `p[ x - xD, y - yD ]` is modified by + +$$p[ x - xD, y - yD ] = ( p[ x - xD, yC ] + p[ xC, y - yD ] + 1 ) \gg 1 \quad (F-296)$$ + +The sample value $p[ x, y ]$ is derived as follows: + +- If $diffHorVer$ is greater than 0, the sample location $( xC, yC )$ is set equal to $( x - sgnXY * yD, y - yD )$ and the sample value $p[ x, y ]$ is derived by + +$$p[ x, y ] = ( p[ xC - 1, yC ] + 2 * p[ xC, yC ] + p[ xC + 1, yC ] + 2 ) \gg 2 \quad (F-297)$$ + +- Otherwise, if $diffHorVer$ is less than 0, the sample location $( xC, yC )$ is set equal to $( x - xD, y - sgnXY * xD )$ and the sample value $p[ x, y ]$ is derived by + +$$p[ x, y ] = ( p[ xC, yC - 1 ] + 2 * p[ xC, yC ] + p[ xC, yC + 1 ] + 2 ) \gg 2 \quad (F-298)$$ + +- Otherwise ( $diffVerHor$ is equal to 0), the sample location $( xC, yC )$ is set equal to $( x - xD + Sign( xD ), y - yD + Sign( yD ) )$ and the sample value $p[ x, y ]$ is derived by + +$$p[ x, y ] = ( p[ xC, y - yD ] + 2 * p[ x - xD, y - yD ] + p[ x - xD, yC ] + 2 ) \gg 2 \quad (F-299)$$ + +When $cornerSampleAvailableFlag$ is equal to 0, the sample value $p[ x - xD, y - yD ]$ is set equal to $cornerSample$ . + +### F.8.6.2.3 Interpolation process for Intra\_Base prediction + +Inputs to this process are: + +- a variable $filteringModeFlag$ specifying the interpolation method, +- a variable $chromaFlag$ specifying whether the luma or a chroma component is subject to the resampling process, +- two variables $mbW$ and $mbH$ specifying the width and height, respectively, of a macroblock for the considered colour component, +- a variable $fieldMbFlag$ specifying whether the current macroblock is a field or a frame macroblock, +- a variable $botFieldFlag$ specifying whether a top or a bottom field is subject to the resampling process (when $RefLayerFrameMbsOnlyFlag$ is equal to 0 or $frame\_mbs\_only\_flag$ is equal to 0), +- a variable $fldPrdInFrmMbFlag$ specifying whether field prediction for a frame macroblock is applied, +- a variable $yBorder$ specifying the vertical border for the output sample array $predSamples$ , +- two variables $refArrayW$ and $refArrayH$ specifying the width and height, respectively, of the array of reference layer sample values, +- a $(refArrayW)x(refArrayH)$ array $refSampleArray$ of reference layer sample values, +- two variables $xOffset$ and $yOffset$ specifying the x and y coordinate, respectively, of the reference layer sample location that corresponds to the sample $refSampleArray[ 0, 0 ]$ of the array $refSampleArray$ . + +Output of this process is an $(mbW)x(mbh / ( 1 + fldPrdInFrmMbFlag ) + 2 * yBorder)$ array $predArray$ of interpolated sample values. + +Table F-9 specifies the filter coefficients $eF[ p, x ]$ with $p = 0..15$ and $x = 0..3$ of the luma interpolation filter $eF$ for resampling in Intra\_Base prediction. + +**Table F-9 – 16-phase luma interpolation filter for resampling in Intra\_Base prediction** + +| phase p | interpolation filter coefficients | | | | +|---------|-----------------------------------|------------|------------|------------| +| | eF[ p, 0 ] | eF[ p, 1 ] | eF[ p, 2 ] | eF[ p, 3 ] | +| 0 | 0 | 32 | 0 | 0 | +| 1 | -1 | 32 | 2 | -1 | +| 2 | -2 | 31 | 4 | -1 | +| 3 | -3 | 30 | 6 | -1 | +| 4 | -3 | 28 | 8 | -1 | +| 5 | -4 | 26 | 11 | -1 | +| 6 | -4 | 24 | 14 | -2 | +| 7 | -3 | 22 | 16 | -3 | +| 8 | -3 | 19 | 19 | -3 | +| 9 | -3 | 16 | 22 | -3 | +| 10 | -2 | 14 | 24 | -4 | +| 11 | -1 | 11 | 26 | -4 | +| 12 | -1 | 8 | 28 | -3 | +| 13 | -1 | 6 | 30 | -3 | +| 14 | -1 | 4 | 31 | -2 | +| 15 | -1 | 2 | 32 | -1 | + +Let tempArray be a (refArrayW)x(mbH / ( 1 + fldPrdInFrmMbFlag ) + 2 \* yBorder) array of samples. Each sample tempArray[ x, y ] with x = 0..(refArrayW - 1) and y = 0..(mbH / ( 1 + fldPrdInFrmMbFlag ) + 2 \* yBorder - 1) is derived as specified in the following ordered steps: + +1. The variable yP is derived by + +$$yP = ( y - yBorder ) * ( 1 + fldPrdInFrmMbFlag ) + botFieldFlag \quad (F-300)$$ + +2. The derivation process for reference layer sample locations in resampling as specified in clause F.6.3 is invoked with chromaFlag, the sample location ( 0, yP ), fieldMbFlag, and botFieldFlag as the inputs and the output is the sample location ( xRef16, yRef16 ) in units of 1/16-th sample. + +NOTE 1 – In this invocation of the process in clause F.6.3, only the vertical component yRef16 of the sample location needs to be derived. + +3. The variables yRef and yPhase are derived by + +$$yRef = ( yRef16 \gg 4 ) - yOffset \quad (F-301)$$ + +$$yPhase = ( yRef16 - 16 * yOffset ) \% 16 \quad (F-302)$$ + +4. Depending on filteringModeFlag, the sample value tempArray[ x, y ] is derived as follows: + +- If filteringModeFlag is equal to 0, the sample value tempArray[ x, y ] is derived by + +$$\begin{aligned} tempArray[ x, y ] = & eF[ yPhase, 0 ] * refSampleArray[ x, yRef - 1 ] + \\ & eF[ yPhase, 1 ] * refSampleArray[ x, yRef ] + \\ & eF[ yPhase, 2 ] * refSampleArray[ x, yRef + 1 ] + \\ & eF[ yPhase, 3 ] * refSampleArray[ x, yRef + 2 ] \end{aligned} \quad (F-303)$$ + +- Otherwise (filteringModeFlag is equal to 1), the sample value tempArray[ x, y ] is derived by + +$$\begin{aligned} tempArray[ x, y ] = & ( 16 - yPhase ) * refSampleArray[ x, yRef ] + \\ & yPhase * refSampleArray[ x, yRef + 1 ] \end{aligned} \quad (F-304)$$ + +Each sample predArray[ x, y ] with x = 0..(mbW - 1) and y = 0..(mbH / ( 1 + fldPrdInFrmMbFlag ) + 2 \* yBorder - 1) is derived as specified in the following ordered steps: + +1. The derivation process for reference layer sample locations in resampling as specified in clause F.6.3 is invoked with chromaFlag, the sample location ( x, 0 ), fieldMbFlag, and botFieldFlag as the inputs and the output is the sample location ( xRef16, yRef16 ) in units of 1/16-th sample. + +NOTE 2 – In this invocation of the process in clause F.6.3, only the horizontal component xRef16 of the sample location needs to be derived. + +2. The variables xRef and xPhase are derived by + +$$\text{xRef} = ( \text{xRef16} \gg 4 ) - \text{xOffset} \quad (\text{F-305})$$ + +$$\text{xPhase} = ( \text{xRef16} - 16 * \text{xOffset} ) \% 16 \quad (\text{F-306})$$ + +3. Depending on filteringModeFlag, and with Clip1 being replaced by Clip1V for chromaFlag equal to 0 and Clip1C for chromaFlag equal to 1, the sample value predArray[ x, y ] is derived as follows: + +- If filteringModeFlag is equal to 0, the sample value tempArray[ x, y ] is derived by + +$$\begin{aligned} \text{predArray}[ x, y ] = \text{Clip1} ( & ( \text{eF}[ \text{xPhase}, 0 ] * \text{tempArray}[ \text{xRef} - 1, y ] + \\ & \text{eF}[ \text{xPhase}, 1 ] * \text{tempArray}[ \text{xRef}, y ] + \\ & \text{eF}[ \text{xPhase}, 2 ] * \text{tempArray}[ \text{xRef} + 1, y ] + \\ & \text{eF}[ \text{xPhase}, 3 ] * \text{tempArray}[ \text{xRef} + 2, y ] + 512 ) \gg 10 ) \end{aligned} \quad (\text{F-307})$$ + +- Otherwise (filteringModeFlag is equal to 1), the sample value tempArray[ x, y ] is derived by + +$$\begin{aligned} \text{predArray}[ x, y ] = ( & ( 16 - \text{xPhase} ) * \text{tempArray}[ \text{xRef}, y ] + \\ & \text{xPhase} * \text{tempArray}[ \text{xRef} + 1, y ] + 128 ) \gg 8 \end{aligned} \quad (\text{F-308})$$ + +#### F.8.6.2.4 Vertical interpolation process for Intra\_Base prediction + +Inputs to this process are: + +- a variable filteringModeFlag specifying the interpolation method, +- a variable chromaFlag specifying whether the luma or a chroma component is subject to the resampling process, +- two variables mbW and mbH specifying the width and height, respectively, of a macroblock for the considered colour component, +- a variable botFieldFlag specifying whether the sample array fieldPredArray contains interpolated samples for the top or bottom field, +- a variable yBorder specifying the vertical border for the sample array fieldPredArray, +- a variable frameMbFlag specifying whether the current macroblock is a frame or a field macroblock, +- an (mbW)x(mbH / ( 1 + frameMbFlag ) + 2 \* yBorder) array fieldPredArray of sample values. + +Output of this process is an (mbW)x(mbH) array predArray of interpolated sample values. + +Each sample predArray[ x, y ] with x = 0..(mbW – 1) and y = 0..(mbH – 1) is derived as follows: + +- If frameMbFlag is equal to 1 and ( y % 2 ) is equal to botFieldFlag, the sample value predArray[ x, y ] is derived by + +$$\text{predArray}[ x, y ] = \text{fieldPredArray}[ x, ( y \gg 1 ) + \text{yBorder} ] \quad (\text{F-309})$$ + +- Otherwise (frameMbFlag is equal to 0 or ( y % 2 ) is not equal to botFieldFlag), the following ordered steps are specified: + +1. The variable yFld is derived by + +$$\text{yFld} = ( y \gg \text{frameMbFlag} ) + \text{yBorder} - \text{botFieldFlag} \quad (\text{F-310})$$ + +2. Depending on filteringModeFlag, and with Clip1 being replaced by Clip1V for chromaFlag equal to 0 and Clip1C for chromaFlag equal to 1, the sample value predArray[ x, y ] is derived as follows: + +- If filteringModeFlag is equal to 0, the sample value predArray[ x, y ] is derived by + +$$\begin{aligned} \text{predArray}[ x, y ] = \text{Clip1} ( & ( 19 * ( \text{fieldPredArray}[ x, \text{yFld} ] + \\ & \text{fieldPredArray}[ x, \text{yFld} + 1 ] ) - \\ & 3 * ( \text{fieldPredArray}[ x, \text{yFld} - 1 ] + \\ & \text{fieldPredArray}[ x, \text{yFld} + 2 ] ) + 16 ) \gg 5 ) \end{aligned} \quad (\text{F-311})$$ + +- Otherwise (filteringModeFlag is equal to 1), the sample value predArray[ x, y ] is derived by + +$$\begin{aligned} \text{predArray}[ x, y ] = ( & ( \text{fieldPredArray}[ x, \text{yFld} ] + \\ & \text{fieldPredArray}[ x, \text{yFld} + 1 ] + 1 ) \gg 1 \end{aligned} \quad (\text{F-312})$$ + +#### F.8.6.2.5 Derivation process for variables related to inter-layer intra prediction + +This clause is only invoked when MinNoInterLayerPredFlag is equal to 0. + +Input to this process is a variable currDQId. + +Outputs of this process are: + +- a variable numILIntraPredSamples, +- a variable numRefLayerILIntraPredMbs. + +Unless stated otherwise, all syntax elements and derived upper-case variables that are referred to inside this clause are syntax elements and derived upper case variables for the layer representation with DQId equal to currDQId. + +Inside this clause, the collective terms currentVars and refLayerVars are specified as follows: + +- If SpatialResolutionChangeFlag is equal to 1, the following applies: + - currentVars is the collective term currentVars after completion of the base decoding process for layer representations with resolution change as specified in clause F.8.1.3.2 for the layer representation with DQId equal to currDQId, + - refLayerVars is the collective term refLayerVars after completion of the base decoding process for layer representations with resolution change as specified in clause F.8.1.3.2 for the layer representation with DQId equal to currDQId. +- Otherwise (SpatialResolutionChangeFlag is equal to 0), the following applies: + - currentVars is the collective term currentVars after completion of the base decoding process for layer representations without resolution change as specified in clause F.8.1.3.1 for the layer representation with DQId equal to currDQId, + - refLayerVars is of the collective term currentVars before invoking the base decoding process for layer representations without resolution change as specified in clause F.8.1.3.1 for the layer representation with DQId equal to currDQId. + +Inside this clause, the arrays of the collective term currentVars are referred to by their names as specified in clause F.8.1.2.1. + +Inside this clause, the arrays fieldMbFlag and mbType of the collective term refLayerVars are referred to as refLayerFieldMbFlag and refLayerMbType, respectively. + +Let currILIntraPredFlag be a (PicWidthInSamplesL)x(PicHeightInSamplesL) array and let refILIntraPredFlag be a one-dimensional array with RefLayerPicSizeInMbs elements. All elements of the arrays currILIntraPredFlag and refILIntraPredFlag are initially set equal to 0. + +The variable yC proceeds over the values 0..(PicHeightInSamplesL – 1). For each value of yC, the variable xC proceeds over the values 0..(PicWidthInSamplesL – 1). For each combination of the values yC and xC, the following ordered steps are specified: + +1. The variable mbAddr is set equal to the address of the macroblock that contains the luma sample at location ( xC, yC ) relative to the upper-left sample of the layer picture. +2. Depending on SpatialResolutionChangeFlag, the following applies: + - If SpatialResolutionChangeFlag is equal to 0, the following ordered steps are specified: + - a. The array element currILIntraPredFlag[ xC, yC ] is derived as follows: + - If mbType[ mbAddr ] is equal to I\_BL, currILIntraPredFlag[ xC, yC ] is set equal to 1. + - Otherwise (mbType[ mbAddr ] is not equal to I\_BL), currILIntraPredFlag[ xC, yC ] is set equal to 0. + - b. When currILIntraPredFlag[ xC, yC ] is equal to 1, the following ordered steps are specified: + - i. The variable refMbAddr is derived as specified in clause F.8.1.2.2 with mbAddr being the value of mbAddr derived in step 1 of this clause. + - ii. The array element refILIntraPredFlag[ refMbAddr ] is set equal to 1. + - iii. When refLayerMbType[ refMbAddr ] is equal to I\_16x16, I\_8x8, or I\_4x4, let setRefIntraMbs be the set of macroblocks that contain luma or chroma samples that are directly (by the invocation of clause F.8.3.2 for the macroblock with address refMbAddr) or indirectly (by multiple invocations of clause F.8.3.2 for macroblocks with mbAddr less than or equal to refMbAddr) used for construction of the intra prediction signal of the macroblock with address refMbAddr in the layer representation with DQId equal to MaxRefLayerDQId. + +- iv. For `refIntraMbAddr` proceeding over the macroblock addresses for the macroblocks of the set `setRefIntraMbs`, `refILIntraPredFlag[ refIntraMbAddr ]` is set equal to 1. +- Otherwise (`SpatialResolutionChangeFlag` is equal to 1), the following ordered steps are specified: + - a. When `RestrictedSpatialResolutionFlag` is equal to 0, `MbaffFrameFlag` is equal to 0, `RefLayerMbaffFrameFlag` is equal to 0, and `base_mode_flag` for the macroblock with address `mbAddr` is equal to 1, the derivation process for reference layer macroblocks as specified in clause F.6.1 is invoked with the luma location `( xC % 16, yC % 16 )`, `fieldMbFlag`, `refLayerFieldMbFlag`, and `refLayerMbType` as the inputs and the outputs are assigned to `mbAddrRefLayer` and `( xRef, yRef )`. For this invocation of clause F.6.1, `CurrMbAddr` is set equal to `mbAddr`. + - b. The element `currILIntraPredFlag[ xC, yC ]` is derived as follows: + - If any of the following conditions are true, `currILIntraPredFlag[ xC, yC ]` is set equal to 1: + - `mbType[ mbAddr ]` is equal to `I_BL`, + - `RestrictedSpatialResolutionFlag` is equal to 0, `MbaffFrameFlag` is equal to 0, `RefLayerMbaffFrameFlag` is equal to 0, `base_mode_flag` for the macroblock with address `mbAddr` is equal to 1, and `refLayerMbType[ mbAddrRefLayer ]` is equal to `I_PCM`, `I_16x16`, `I_8x8`, `I_4x4`, or `I_BL`. + - Otherwise, `currILIntraPredFlag[ xC, yC ]` is set equal to 0. + - c. When `currILIntraPredFlag[ xC, yC ]` is equal to 1, the following ordered steps are specified: + - i. Let `setOfRefSamples` be the set of reference layer luma sample locations `( xR, yR )` of the luma sample values that are used in the filtering processes specified in clause F.8.6.2.3 and, when applicable, clause F.8.6.2.4 for deriving the inter-layer intra prediction sample for the luma sample at location `( xC, yC )` relative to the upper-left luma sample of the layer picture. + - ii. For each of the reference layer luma sample locations `( xR, yR )` of the set `setOfRefSamples` that correspond to luma samples marked "available for Intra\_Base prediction" in the invocation of clause F.8.6.2.2 for the macroblock with address `mbAddr` of the layer representation with `DQId` equal to `currDQId`, the following ordered steps are specified: + - (1) Let `refMbAddr` be the macroblock address of the macroblock in the layer representation with `DQId` equal to `MaxRefLayerDQId` that contains the luma sample at location `( xR, yR )`. + - (2) The array element `refILIntraPredFlag[ refMbAddr ]` is set equal to 1. + - (3) When `refLayerMbType[ refMbAddr ]` is equal to `I_16x16`, `I_8x8`, or `I_4x4`, let `setRefIntraMbs` be the set of macroblocks that contain luma or chroma samples that are directly (by the invocation of clause F.8.3.2 for the macroblock with address `refMbAddr`) or indirectly (by multiple invocations of clause F.8.3.2 for macroblocks with `mbAddr` less than or equal to `refMbAddr`) used for construction of the intra prediction signal of the macroblock with address `refMbAddr` in the layer representation with `DQId` equal to `MaxRefLayerDQId`. + - (4) For `refIntraMbAddr` proceeding over the macroblock addresses for the macroblocks of the set `setRefIntraMbs`, `refILIntraPredFlag[ refIntraMbAddr ]` is set equal to 1. + +The variable `numILIntraPredSamples` is set equal to the number of elements of the `(PicWidthInSamplesL)x(PicHeightInSamplesL)` array `currILIntraPredFlag` that are equal to 1. + +NOTE 1 – The variable `numILIntraPredSamples` is a measure for the number of luma samples in the layer representation with `DQId` equal to `currDQId` that are predicted by inter-layer intra prediction. + +The variable `numRefLayerILIntraPredMbs` is set equal to the number of elements of the array `refILIntraPredFlag` that are equal to 1. + +NOTE 2 – The variable `numRefLayerILIntraPredMbs` is a measure for the number of intra-coded macroblocks in the reference layer representation that need to be decoded for constructing the inter-layer intra prediction samples of the layer representation with `DQId` equal to `currDQId`. + +### F.8.6.3 Resampling process for residual samples + +Inputs to this process are: + +- a variable `fieldMbFlag` specifying whether the current macroblock is a field or a frame macroblock, + +- a one-dimensional array `refLayerFieldMbFlag` with `RefLayerPicSizeInMbs` elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array `refLayerCTrafo` with `RefLayerPicSizeInMbs` elements specifying the luma transform types for the macroblocks of the reference layer representation, +- a $(\text{RefLayerPicWidthInSamples}_L) \times (\text{RefLayerPicHeightInSamples}_L)$ array `refLayerPicSamplesL` of luma samples for the reference layer representation, +- a $(\text{PicWidthInSamples}_L) \times (\text{PicHeightInSamples}_L)$ array `picSamplesL` of luma samples, +- when `ChromaArrayType` is not equal to 0, two $(\text{RefLayerPicWidthInSamples}_C) \times (\text{RefLayerPicHeightInSamples}_C)$ arrays `refLayerPicSamplesCb` and `refLayerPicSamplesCr` of chroma samples for the reference layer representation, +- when `ChromaArrayType` is not equal to 0, two $(\text{PicWidthInSamples}_C) \times (\text{PicHeightInSamples}_C)$ arrays `picSamplesCb` and `picSamplesCr` of chroma samples. + +Outputs of this process are: + +- a modified version of the array `picSamplesL` of luma samples, +- when `ChromaArrayType` is not equal to 0, modified versions of the arrays `picSamplesCb` and `picSamplesCr` of chroma samples. + +The resampling process for residual samples of a macroblock colour component as specified in clause F.8.6.3.1 is invoked with `chromaFlag` equal to 0, `mbW` equal to 16, `mbH` equal to 16, `fieldMbFlag`, `refLayerPicSamplesL`, `refLayerFieldMbFlag`, and `refLayerCTrafo` as the inputs and the output is the 16x16 array `mbPredL` of residual prediction samples for the luma component of the current macroblock. + +When `ChromaArrayType` is not equal to 0, for CX being replaced by Cb and Cr, the resampling process for residual samples of a macroblock colour component as specified in clause F.8.6.3.1 is invoked with `chromaFlag` equal to 1, `mbW` equal to `MbWidthC`, `mbH` equal to `MbHeightC`, `fieldMbFlag`, `refLayerPicSamplesCX`, `refLayerFieldMbFlag`, and `refLayerCTrafo` as the inputs and the output is the $(\text{MbWidthC}) \times (\text{MbHeightC})$ array `mbPredCX` of residual prediction samples for the CX component of the current macroblock. + +The picture sample array construction process as specified in clause F.8.5.4.1 is invoked with `fieldMbFlag`, `mbPredL`, `picSamplesL` and, when `ChromaArrayType` is not equal to 0, `mbPredCb`, `mbPredCr`, `picSamplesCb`, and `picSamplesCr` as the inputs and the outputs are a modified version of `picSamplesL` and, when `ChromaArrayType` is not equal to 0, modified versions of `picSamplesCb`, and `picSamplesCr`. + +### F.8.6.3.1 Resampling process for residual samples of a macroblock colour component + +Inputs to this process are: + +- a variable `chromaFlag` specifying whether the luma or a chroma component is subject to the resampling process, +- two variables `mbW` and `mbH` specifying the width and height, respectively, of a macroblock for the considered colour component, +- a variable `fieldMbFlag` specifying whether the current macroblock is a field or a frame macroblock, +- an array `refLayerPicSamples`, which is a $(\text{RefLayerPicWidthInSamples}_L) \times (\text{RefLayerPicHeightInSamples}_L)$ array containing constructed residual luma sample values for the reference layer representation when `chromaFlag` is equal to 0 or a $(\text{RefLayerPicWidthInSamples}_C) \times (\text{RefLayerPicHeightInSamples}_C)$ array containing constructed residual chroma sample values for the reference layer representation when `chromaFlag` is equal to 1, +- a one-dimensional array `refLayerFieldMbFlag` with `RefLayerPicSizeInMbs` elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array `refLayerCTrafo` with `RefLayerPicSizeInMbs` elements specifying the luma transform types for the macroblocks of the reference layer representation. + +Output of this process is an $(\text{mbW}) \times (\text{mbH})$ array `mbPred` of residual prediction samples. + +The variable `botFieldFlag` is derived as follows: + +- If `RefLayerFrameMbsOnlyFlag` is equal to 1, `botFieldFlag` is set equal to 0. +- Otherwise, if `field_pic_flag` is equal to 1, `botFieldFlag` is set equal to `bottom_field_flag`. +- Otherwise, if `RefLayerFieldPicFlag` is equal to 1, `botFieldFlag` is set equal to `RefLayerBottomFieldFlag`. +- Otherwise, if `fieldMbFlag` is equal to 1, `botFieldFlag` is set equal to $(\text{CurrMbAddr} \% 2)$ . + +- Otherwise, botFieldFlag is set equal to 0. + +The variable frameBasedResamplingFlag is derived as follows: + +- If all of the following conditions are true, frameBasedResamplingFlag is set equal to 1: + - RefLayerFrameMbsOnlyFlag is equal to 1, + - frame\_mbs\_only\_flag is equal to 1. +- Otherwise, frameBasedResamplingFlag is set equal to 0. + +The variable topAndBotResamplingFlag is derived as follows: + +- If all of the following conditions are true, topAndBotResamplingFlag is set equal to 1: + - RefLayerFrameMbsOnlyFlag is equal to 0, + - RefLayerFieldPicFlag is equal to 0, + - frame\_mbs\_only\_flag is equal to 0, + - fieldMbFlag is equal to 0. +- Otherwise, topAndBotResamplingFlag is set equal to 0. + +The variable botFieldFrameMbsOnlyRefFlag is derived as follows: + +- If RefLayerFrameMbsOnlyFlag is equal to 1, fieldMbFlag is equal to 1, and any of the following conditions are true, botFieldFrameMbsOnlyRefFlag is set equal to 1: + - field\_pic\_flag is equal to 1 and bottom\_field\_flag is equal to 1, + - field\_pic\_flag is equal to 0 and ( CurrMbAddr % 2 ) is equal to 1. +- Otherwise, botFieldFrameMbsOnlyRefFlag is set equal to 0. + +The array predArray is derived as specified in the following. + +- If botFieldFrameMbsOnlyRefFlag is equal to 1, the following ordered steps are specified: + 1. The reference layer sample array construction process prior to residual resampling as specified in clause F.8.6.3.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, yBorder equal to 1, refLayerPicSamples, refLayerFieldMbFlag, and refLayerCTrafo as the inputs and the outputs are the variables refArrayW, refArrayH, the array refSampleArray of reference layer sample values, the array refTransBlkIdc of reference layer transform block identifications, and the variables xOffset and yOffset. + 2. The interpolation process for residual prediction as specified in clause F.8.6.3.3 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, fldPrdInFrmMbFlag equal to 0, yBorder equal to 1, refArrayW, refArrayH, refSampleArray, refTransBlkIdc, xOffset, and yOffset as the inputs and the output is the (mbW)x(mbH + 2) array topFldPredArray of top field prediction samples. + 3. The vertical interpolation process for residual prediction as specified in clause F.8.6.3.4 is invoked with mbW, mbH, botFieldFlag, yBorder equal to 1, frameMbFlag equal to 0, and topFldPredArray as the inputs and the output is the (mbW)x(mbH) array mbPred of residual prediction samples. +- Otherwise, if frameBasedResamplingFlag is equal to 1 or fieldMbFlag is equal to 1, the following ordered steps are specified: + 1. The reference layer sample array construction process prior to residual resampling as specified in clause F.8.6.3.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, yBorder equal to 0, refLayerPicSamples, refLayerFieldMbFlag, and refLayerCTrafo as the inputs and the outputs are the variables refArrayW, refArrayH, the array refSampleArray of reference layer sample values, the array refTransBlkIdc of reference layer transform block identifications, and the variables xOffset and yOffset. + 2. The interpolation process for residual prediction as specified in clause F.8.6.3.3 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, fldPrdInFrmMbFlag equal to 0, yBorder equal to 0, refArrayW, refArrayH, refSampleArray, refTransBlkIdc, xOffset, and yOffset as the inputs and the output is the (mbW)x(mbH) array mbPred of residual prediction samples. +- Otherwise, if topAndBotResamplingFlag is equal to 0, the following ordered steps are specified: + 1. The reference layer sample array construction process prior to residual resampling as specified in clause F.8.6.3.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, yBorder equal to 1, + +refLayerPicSamples, refLayerFieldMbFlag, and refLayerCTrafo as the inputs and the outputs are the variables refArrayW, refArrayH, the array refSampleArray of reference layer sample values, the array refTransBlkIdc of reference layer transform block identifications, and the variables xOffset and yOffset. + +2. The interpolation process for residual prediction as specified in clause F.8.6.3.3 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag, fldPrdInFrmMbFlag equal to 1, yBorder equal to 1, refArrayW, refArrayH, refSampleArray, refTransBlkIdc, xOffset, and yOffset as the inputs and the output is the (mbW)x(mbH / 2 + 2) array fieldPredArray of field prediction samples. +3. The vertical interpolation process for residual prediction as specified in clause F.8.6.3.4 is invoked with mbW, mbH, botFieldFlag, yBorder equal to 1, frameMbFlag equal to 1, and fieldPredArray as the inputs and the output is the (mbW)x(mbH) array mbPred of residual prediction samples. + +– Otherwise (topAndBotResamplingFlag is equal to 1), the following ordered steps are specified: + +1. The reference layer sample array construction process prior to residual resampling as specified in clause F.8.6.3.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag equal to 0, yBorder equal to 0, refLayerPicSamples, refLayerFieldMbFlag, and refLayerCTrafo as the inputs and the outputs are the variables refArrayTopW, refArrayTopH, the array refSampleArrayTop of reference layer sample values, the array refTransBlkIdcTop of reference layer transform block identifications, and the variables xOffsetTop and yOffsetTop. +2. The interpolation process for residual prediction as specified in clause F.8.6.3.3 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag equal to 0, fldPrdInFrmMbFlag equal to 1, yBorder equal to 0, refArrayTopW, refArrayTopH, refSampleArrayTop, refTransBlkIdcTop, xOffsetTop, and yOffsetTop as the inputs and the output is the (mbW)x(mbH / 2) array topFieldPredArray of top field prediction samples. +3. The reference layer sample array construction process prior to residual resampling as specified in clause F.8.6.3.2 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag equal to 1, yBorder equal to 0, refLayerPicSamples, refLayerFieldMbFlag, and refLayerCTrafo as the inputs and the outputs are the variables refArrayBotW, refArrayBotH, the array refSampleArrayBot of reference layer sample values, the array refTransBlkIdcBot of reference layer transform block identifications, and the variables xOffsetBot and yOffsetBot. +4. The interpolation process for residual prediction as specified in clause F.8.6.3.3 is invoked with chromaFlag, mbW, mbH, fieldMbFlag, botFieldFlag equal to 1, fldPrdInFrmMbFlag equal to 1, yBorder equal to 0, refArrayBotW, refArrayBotH, refSampleArrayBot, refTransBlkIdcBot, xOffsetBot, and yOffsetBot as the inputs and the output is the (mbW)x(mbH / 2) array botFieldPredArray of bottom field prediction samples. +5. Each sample predArray[ x, y ] with x = 0..(mbW – 1) and y = 0..(mbH – 1) of the array mbPred of residual prediction samples is derived by + +$$\text{mbPred}[x, y] = \left( \left( (y \% 2) == 0 \right) ? \text{topFieldPredArray}[x, y \gg 1] : \text{botFieldPredArray}[x, y \gg 1] \right) \quad (\text{F-313})$$ + +#### F.8.6.3.2 Reference layer sample array construction process prior to residual resampling + +Inputs to this process are: + +- a variable chromaFlag specifying whether the luma or a chroma component is subject to the resampling process, +- two variables mbW and mbH specifying the width and height, respectively, of a macroblock for the considered colour component, +- a variable fieldMbFlag specifying whether the current macroblock is a field or a frame macroblock, +- a variable botFieldFlag specifying whether a top or a bottom field is subject to the resampling process (when RefLayerFrameMbsOnlyFlag is equal to 0 or frame\_mbs\_only\_flag is equal to 0), +- a variable yBorder specifying the vertical border for determining the vertical size of the output arrays, +- an array refLayerPicSamples, which is a (RefLayerPicWidthInSamplesL)x(RefLayerPicHeightInSamplesL) array containing constructed residual luma sample values for the reference layer representation when chromaFlag is equal to 0 or a (RefLayerPicWidthInSamplesC)x(RefLayerPicHeightInSamplesC) array containing constructed residual chroma sample values for the reference layer representation when chromaFlag is equal to 1, +- a one-dimensional array refLayerFieldMbFlag with RefLayerPicSizeInMbs elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array refLayerCTrafo with RefLayerPicSizeInMbs elements specifying the luma transform types for the macroblocks of the reference layer representation. + +Outputs of this process are: + +- two variables `refArrayW` and `refArrayH` specifying the width and height, respectively, of the constructed arrays of reference layer sample values and reference layer transform block identification, +- a (`refArrayW`)x(`refArrayH`) array `refSampleArray` of reference layer sample values, +- a (`refArrayW`)x(`refArrayH`) array `refTransBlkIdc` of reference layer transform block identifications, +- two variables `xOffset` and `yOffset` specifying the x and y coordinate, respectively, of the reference layer sample location that corresponds to the sample `refSampleArray[ 0, 0 ]` of the array `refSampleArray` and the transform block identification `refTransBlkIdc[ 0, 0 ]` of the array `refTransBlkIdc`. + +The variables `refW`, `refH`, `refMbW`, `refMbH`, `xOffset`, `yOffset`, `refArrayW`, `refArrayH`, `yRefScale`, and `yRefAdd` are derived as specified in the following ordered steps: + +1. The derivation process for reference layer sample locations in resampling as specified in clause F.6.3 is invoked with `chromaFlag`, the sample location ( 0, `-yBorder` ), `fieldMbFlag`, and `botFieldFlag` as the inputs and the output is the sample location ( `xRefMin16`, `yRefMin16` ) in units of 1/16-th sample. +2. The derivation process for reference layer sample locations in resampling as specified in clause F.6.3 is invoked with `chromaFlag`, the sample location ( `mbW - 1`, `mbH - 1 + yBorder` ), `fieldMbFlag`, and `botFieldFlag` as the inputs and the output is the sample location ( `xRefMax16`, `yRefMax16` ) in units of 1/16-th sample. +3. With `Z` being replaced by `L` for `chromaFlag` equal to 0 and `C` for `chromaFlag` equal to 1, the variables `refW`, `refH`, `refMbW`, and `refMbH` are derived by + +$$\text{refW} = \text{ReflayerPicWidthInSamples}_Z \quad (\text{F-314})$$ + +$$\text{refH} = \text{ReflayerPicHeightInSamples}_Z \quad (\text{F-315})$$ + +$$\text{refMbW} = ( ( \text{chromaFlag} == 0 ) ? 16 : \text{ReflayerMbWidthC} ) \quad (\text{F-316})$$ + +$$\text{refMbH} = ( ( \text{chromaFlag} == 0 ) ? 16 : \text{ReflayerMbHeightC} ) \quad (\text{F-317})$$ + +4. The variables `xOffset`, `yOffset`, `refArrayW`, and `refArrayH` are derived by + +$$\text{xOffset} = ( \text{xRefMin16} \gg 4 ) \quad (\text{F-318})$$ + +$$\text{yOffset} = ( \text{yRefMin16} \gg 4 ) \quad (\text{F-319})$$ + +$$\text{refArrayW} = ( \text{xRefMax16} \gg 4 ) - \text{xOffset} + 2 \quad (\text{F-320})$$ + +$$\text{refArrayH} = ( \text{yRefMax16} \gg 4 ) - \text{yOffset} + 2 \quad (\text{F-321})$$ + +5. The variables `yRefScale` and `yRefAdd` are derived as follows: + +- If `ReflayerFrameMbsOnlyFlag` is equal to 1 or `ReflayerFieldPicFlag` is equal to 1, `yRefScale` is set equal to 1 and `yRefAdd` is set equal to 0. +- Otherwise (`ReflayerFrameMbsOnlyFlag` is equal to 0 and `ReflayerFieldPicFlag` is equal to 0), `yRefScale` is set equal to 2 and `yRefAdd` is set equal to `botFieldFlag`. + +Each sample `refSampleArray[ x, y ]` and each transform block identification `refTransBlkIdc[ x, y ]` with `x = 0..(refArrayW - 1)` and `y = 0..(refArrayH - 1)` are derived as specified in the following ordered steps: + +1. A reference layer sample location ( `xRef`, `yRef` ) is derived by: + +$$\text{xRef} = \text{Max}( 0, \text{Min}( \text{refW} - 1, \text{x} + \text{xOffset} ) ) \quad (\text{F-322})$$ + +$$\text{yRef} = \text{yRefScale} * \text{Max}( 0, \text{Min}( \text{refH} / \text{yRefScale} - 1, \text{y} + \text{yOffset} ) ) + \text{yRefAdd} \quad (\text{F-323})$$ + +2. The sample `refSampleArray[ x, y ]` is derived by + +$$\text{refSampleArray}[ \text{x}, \text{y} ] = \text{refLayerPicSamples}[ \text{xRef}, \text{yRef} ] \quad (\text{F-324})$$ + +3. The transform block identification `refTransBlkIdc[ x, y ]` is derived by invoking the derivation process for reference layer transform block identifications as specified in clause F.8.6.3.2.1 with the reference layer sample location ( `xRef`, `yRef` ), `chromaFlag`, `refMbW`, `refMbH`, `refLayerFieldMbFlag`, and `refLayerCTrafo` as the inputs and assigning the output to `refTransBlkIdc[ x, y ]`. + +#### F.8.6.3.2.1 Derivation process for reference layer transform block identifications + +Inputs to this process are: + +- a reference layer sample location ( `xRef`, `yRef` ) relative to the upper-left sample of the considered colour component of the reference layer picture, +- a variable `chromaFlag` specifying whether the luma or a chroma component is subject to the resampling process, + +- two variables `refMbW` and `refMbH` specifying the width and height, respectively, of a reference layer macroblock for the considered colour component, +- a one-dimensional array `refLayerFieldMbFlag` with `RefLayerPicSizeInMbs` elements specifying which macroblocks of the reference layer representation are field macroblocks and which macroblocks are frame macroblocks, +- a one-dimensional array `refLayerCTrafo` with `RefLayerPicSizeInMbs` elements specifying the luma transform types for the macroblocks of the reference layer representation. + +Output of this process is a variable `refTransBlkIdc` specifying an identification for the reference layer transform block that contains the sample at location ( `xRef`, `yRef` ). + +The reference layer macroblock address `refMbAddr` and the reference layer sample location ( `xM`, `yM` ) inside the reference layer macroblock are derived as follows: + +- If `RefLayerMbaffFrameFlag` is equal to 0, the variable `refMbAddr` and the sample location ( `xM`, `yM` ) are derived by + +$$\text{refMbAddr} = ( \text{yRef} / \text{refMbH} ) * \text{RefLayerPicWidthInMbs} + ( \text{xRef} / \text{refMbW} ) \quad (\text{F-325})$$ + +$$\text{xM} = \text{xRef} \% \text{refMbW} \quad (\text{F-326})$$ + +$$\text{yM} = \text{yRef} \% \text{refMbH} \quad (\text{F-327})$$ + +- Otherwise (`RefLayerMbaffFrameFlag` is equal to 1), the variable `refMbAddr` is derived as specified in the following ordered steps: + +1. A variable `refMbAddrTop` and the horizontal sample location `xM` are derived by + +$$\text{refMbAddrTop} = 2 * ( ( \text{yRef} / ( 2 * \text{refMbH} ) ) * \text{RefLayerPicWidthInMbs} + ( \text{xRef} / \text{refMbW} ) ) \quad (\text{F-328})$$ + +$$\text{xM} = \text{xRef} \% \text{refMbW} \quad (\text{F-329})$$ + +2. Depending on `refLayerFieldMbFlag[ refMbAddrTop ]`, the variable `refMbAddr` and the vertical sample location `yM` are derived as follows: + +- If `refLayerFieldMbFlag[ refMbAddrTop ]` is equal to 0, the variables `refMbAddr` and `yM` are derived by + +$$\text{refMbAddr} = \text{refMbAddrTop} + ( \text{yRef} \% ( 2 * \text{refMbH} ) ) / \text{refMbH} \quad (\text{F-330})$$ + +$$\text{yM} = \text{yRef} \% \text{refMbH} \quad (\text{F-331})$$ + +- Otherwise (`refLayerFieldMbFlag[ refMbAddrTop ]` is equal to 1), the variables `refMbAddr` and `yM` are derived by + +$$\text{refMbAddr} = \text{refMbAddrTop} + ( \text{yRef} \% 2 ) \quad (\text{F-332})$$ + +$$\text{yM} = ( \text{yRef} \% ( 2 * \text{refMbH} ) ) \gg 1 \quad (\text{F-333})$$ + +Depending on `chromaFlag`, `RefLayerChromaArrayType`, and `refLayerCTrafo[ refMbAddr ]`, the following applies: + +- If (`chromaFlag` is equal to 0 or `RefLayerChromaArrayType` is equal to 3) and `refLayerCTrafo[ refMbAddr ]` is equal to `T_8x8`, the variable `refTransBlkIdc` is derived by: + +$$\text{refTransBlkIdc} = 1 + 2 * ( 4 * \text{refMbAddr} + 2 * ( \text{yM} / 8 ) + ( \text{xM} / 8 ) ) \quad (\text{F-334})$$ + +- Otherwise (`(chromaFlag is equal to 1 and RefLayerChromaArrayType is not equal to 3)` or `refLayerCTrafo[ refMbAddr ]` is not equal to `T_8x8`), the variable `refTransBlkIdc` is derived by + +$$\text{refTransBlkIdc} = 2 * ( 16 * \text{refMbAddr} + 4 * ( \text{yM} / 4 ) + ( \text{xM} / 4 ) ) \quad (\text{F-335})$$ + +### F.8.6.3.3 Interpolation process for residual prediction + +Inputs to this process are: + +- a variable `chromaFlag` specifying whether the luma or a chroma component is subject to the resampling process, +- two variables `mbW` and `mbH` specifying the width and height, respectively, of a macroblock for the considered colour component, +- a variable `fieldMbFlag` specifying whether the current macroblock is a field or a frame macroblock, +- a variable `botFieldFlag` specifying whether a top or a bottom field is subject to the resampling process (when `RefLayerFrameMbsOnlyFlag` is equal to 0 or `frame_mbs_only_flag` is equal to 0), +- a variable `fldPrdInFrmMbFlag` specifying whether field prediction for a frame macroblock is applied, +- a variable `yBorder` specifying the vertical border for the output sample array `predSamples`, + +- two variables refArrayW and refArrayH specifying the width and height, respectively, of the array of reference layer sample values and the array of transform block identifications, +- a (refArrayW)x(refArrayH) array refSampleArray of reference layer sample values, +- a (refArrayW)x(refArrayH) array refTransBlkIdc of transform block identifications, +- two variables xOffset and yOffset specifying the x and y coordinate, respectively, of the reference layer sample location that corresponds to the sample refSampleArray[ 0, 0 ] of the array refSampleArray and the transform block identification refTransBlkIdc[ 0, 0 ] of the array refTransBlkIdc. + +Output of this process is an (mbW)x(mbH / ( 1 + fldPrdInFrmMbFlag ) + 2 \* yBorder) array predArray of interpolated sample values. + +Each sample predArray[ x, y ] with x = 0..(mbW – 1) and y = 0..(mbH / ( 1 + fldPrdInFrmMbFlag ) + 2 \* yBorder – 1) is derived as specified in the following ordered steps: + +1. The variable yP is derived by: + +$$yP = ( y - yBorder ) * ( 1 + fldPrdInFrmMbFlag ) + botFieldFlag \quad (F-336)$$ + +2. The derivation process for reference layer sample locations in resampling as specified in clause F.6.3 is invoked with chromaFlag, the sample location ( x, yP ), fieldMbFlag, and botFieldFlag as the inputs and the output is the sample location ( xRef16, yRef16 ) in units of 1/16-th sample. +3. The variables xRef, yRef, xPhase, and yPhase are derived by: + +$$xRef = ( xRef16 \gg 4 ) - xOffset \quad (F-337)$$ + +$$yRef = ( yRef16 \gg 4 ) - yOffset \quad (F-338)$$ + +$$xPhase = ( xRef16 - 16 * xOffset ) \% 16 \quad (F-339)$$ + +$$yPhase = ( yRef16 - 16 * yOffset ) \% 16 \quad (F-340)$$ + +4. Let tempPred be a one-dimensional array with 2 elements. Each sample value tempPred[ dY ] with dY = 0..1 is derived as follows: + +- If refTransBlkIdc[ xRef, yRef + dY ] is equal to refTransBlkIdc[ xRef + 1, yRef + dY ], the sample value tempPred[ dY ] is derived by: + +$$\begin{aligned} tempPred[ dY ] = & ( 16 - xPhase ) * refSampleArray[ xRef, yRef + dY ] + \\ & xPhase * refSampleArray[ xRef + 1, yRef + dY ] \end{aligned} \quad (F-341)$$ + +- Otherwise (refTransBlkIdc[ xRef, yRef + dY ] is not equal to refTransBlkIdc[ xRef + 1, yRef + dY ]), the sample value tempPred[ dY ] is derived by: + +$$\begin{aligned} tempPred[ dY ] = & ( ( xPhase < 8 ) ? refSampleArray[ xRef, yRef + dY ] \\ & : refSampleArray[ xRef + 1, yRef + dY ] ) \ll 4 \end{aligned} \quad (F-342)$$ + +5. With xRefRound set equal to (xRef + ( xPhase / 8 )), the sample value predArray[ x, y ] is derived as follows: + +- If refTransBlkIdc[ xRefRound, yRef ] is equal to refTransBlkIdc[ xRefRound, yRef + 1 ], the sample value predArray[ x, y ] is derived by: + +$$\begin{aligned} predArray[ x, y ] = & ( ( 16 - yPhase ) * tempPred[ 0 ] + \\ & yPhase * tempPred[ 1 ] + 128 ) \gg 8 \end{aligned} \quad (F-343)$$ + +- Otherwise (refTransBlkIdc[ xRefRound, yRef ] is not equal to refTransBlkIdc[ xRefRound, yRef + 1 ]), the sample value predArray[ x, y ] is derived by: + +$$predArray[ x, y ] = ( ( ( yPhase < 8 ) ? tempPred[ 0 ] : tempPred[ 1 ] ) + 8 ) \gg 4 \quad (F-344)$$ + +#### F.8.6.3.4 Vertical interpolation process for residual prediction + +Inputs to this process are: + +- two variables mbW and mbH specifying the width and height, respectively, of a macroblock for the considered colour component, +- a variable botFieldFlag specifying whether the sample array fieldPredArray contains interpolated samples for the top or bottom field, +- a variable yBorder specifying the vertical border for the sample array fieldPredArray, +- a variable frameMbFlag specifying whether the current macroblock is a frame or a field macroblock, + +- an $(\text{mbW}) \times (\text{mbH} / (1 + \text{frameMbFlag}) + 2 * \text{yBorder})$ array fieldPredArray of sample values. + +Output of this process is an $(\text{mbW}) \times (\text{mbH})$ array predArray of interpolated sample values. + +Each sample $\text{predArray}[x, y]$ with $x = 0..(\text{mbW} - 1)$ and $y = 0..(\text{mbH} - 1)$ is derived as follows: + +- If $\text{frameMbFlag}$ is equal to 1 and $(y \% 2)$ is equal to $\text{botFieldFlag}$ , the sample value $\text{predArray}[x, y]$ is derived by + +$$\text{predArray}[x, y] = \text{fieldPredArray}[x, (y \gg 1) + \text{yBorder}] \quad (\text{F-345})$$ + +- Otherwise ( $\text{frameMbFlag}$ is equal to 0 or $(y \% 2)$ is not equal to $\text{botFieldFlag}$ ), the sample value $\text{predArray}[x, y]$ is derived by + +$$\text{predArray}[x, y] = (\text{fieldPredArray}[x, (y \gg \text{frameMbFlag}) + \text{yBorder} - \text{botFieldFlag}] + \text{fieldPredArray}[x, (y \gg \text{frameMbFlag}) + \text{yBorder} - \text{botFieldFlag} + 1] + 1) \gg 1 \quad (\text{F-346})$$ + +## F.8.7 SVC deblocking filter processes + +Clause F.8.7.1 specifies the deblocking filter process for Intra\_Base prediction. + +Clause F.8.7.2 specifies the deblocking filter process for target representations. + +### F.8.7.1 Deblocking filter process for Intra\_Base prediction + +Inputs to the process are: + +- the variable $\text{currDQId}$ , +- the collective term $\text{currentVars}$ . + +Output of this process is a modified version of $\text{currentVars}$ . + +Let the variable $\text{refLayerDQId}$ be equal to the value of the variable $\text{MaxRefLayerDQId}$ of the layer representation with $\text{DQId}$ equal to $\text{currDQId}$ . + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the layer representation with $\text{DQId}$ equal to $\text{refLayerDQId}$ . + +Inside this clause, the arrays that are collectively referred to as $\text{currentVars}$ are referred to by their names as specified in clause F.8.1.2.1. + +The derivation process for quantization parameters used in the deblocking filter process as specified in clause F.8.7.3 is invoked with $\text{deblockingDQId}$ set equal to $\text{refLayerDQId}$ , $\text{mbType}$ , $\text{tQP}_Y$ , and $\text{tCoeffLevel}$ as the inputs and the outputs are a list $\text{qpDB}_Y$ specifying luma quantization parameter that are used in the deblocking filter process and, when $\text{ChromaArrayType}$ is not equal to 0, two lists $\text{qpDB}_{Cb}$ and $\text{qpDB}_{Cr}$ specifying chroma quantization parameters that are used in the deblocking filter process. + +Let $\text{disableDeblockingFilterIdc}$ , $\text{filterOffsetA}$ , and $\text{filterOffsetB}$ be equal to the values of $\text{disable\_inter\_layer\_deblocking\_filter\_idc}$ , $\text{InterlayerFilterOffsetA}$ , and $\text{InterlayerFilterOffsetB}$ , respectively, for any slice of the layer representation with $\text{DQId}$ equal to $\text{currDQId}$ , that has $\text{no\_inter\_layer\_pred\_flag}$ equal to 0. + +For the current macroblock address $\text{CurrMbAddr}$ proceeding over values $0..(\text{PicSizeInMbs} - 1)$ , the macroblock deblocking filter process as specified in clause F.8.7.4 is invoked with $\text{interLayerDeblockingFlag} = 1$ , $\text{disableDeblockingFilterIdc}$ , $\text{filterOffsetA}$ , $\text{filterOffsetB}$ , $\text{sliceBoundariesOnlyFlag} = 0$ , $\text{currentVars}$ , $\text{qpDB}_Y$ and, when $\text{ChromaArrayType}$ is not equal to 0, $\text{qpDB}_{Cb}$ and $\text{qpDB}_{Cr}$ as the inputs and the output is a modified version of $\text{currentVars}$ . + +When $\text{disableDeblockingFilterIdc}$ is equal to 3 or 6, for the current macroblock address $\text{CurrMbAddr}$ proceeding over values $0..(\text{PicSizeInMbs} - 1)$ , the macroblock deblocking filter process as specified in clause F.8.7.4 is invoked with $\text{interLayerDeblockingFlag} = 1$ , $\text{disableDeblockingFilterIdc}$ , $\text{filterOffsetA}$ , $\text{filterOffsetB}$ , $\text{sliceBoundariesOnlyFlag} = 1$ , $\text{currentVars}$ , $\text{qpDB}_Y$ and, when $\text{ChromaArrayType}$ is not equal to 0, $\text{qpDB}_{Cb}$ and $\text{qpDB}_{Cr}$ as the inputs and the output is a modified version of $\text{currentVars}$ . + +### F.8.7.2 Deblocking filter process for target representations + +Inputs to the process are: + +- the variable $\text{currDQId}$ , +- the collective term $\text{currentVars}$ . + +Output of this process is a modified version of $\text{currentVars}$ . + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the process specified in this clause and all child processes invoked from this process are the syntax elements and derived upper-case variables for the layer representation with DQId equal to currDQId. + +Inside this clause, the arrays that are collectively referred to as currentVars are referred to by their names as specified in clause F.8.1.2.1. + +The derivation process for quantization parameters used in the deblocking filter process as specified in clause F.8.7.3 is invoked with deblockingDQId set equal to currDQId, mbType, tQPV, and tCoeffLevel as the inputs and the outputs are a list qpDBV specifying luma quantization parameter that are used in the deblocking filter process and, when ChromaArrayType is not equal to 0, two lists qpDBCb and qpDBCr specifying chroma quantization parameters that are used in the deblocking filter process. + +For the current macroblock address CurrMbAddr proceeding over values 0..(PicSizeInMbs - 1), the following ordered steps are specified: + +1. Let disableDeblockingFilterIdc, filterOffsetA, and filterOffsetB be equal to the value of disable\_deblocking\_filter\_idc, FilterOffsetA, and FilterOffsetB, respectively, for the slice with DQId equal to (sliceIdc[ CurrMbAddr ] & 127) and first\_mb\_in\_slice equal to (sliceIdc[ CurrMbAddr ] >> 7). +2. The macroblock deblocking filter process as specified in clause F.8.7.4 is invoked with interLayerDeblockingFlag = 0, disableDeblockingFilterIdc, filterOffsetA, filterOffsetB, sliceBoundariesOnlyFlag = 0, currentVars, qpDBV and, when ChromaArrayType is not equal to 0, qpDBCb and qpDBCr as the inputs and the output is a modified version of currentVars. + +For the current macroblock address CurrMbAddr proceeding over values 0..(PicSizeInMbs - 1), the following ordered steps are specified: + +1. Let disableDeblockingFilterIdc, filterOffsetA, and filterOffsetB be equal to the value of disable\_deblocking\_filter\_idc, FilterOffsetA, and FilterOffsetB, respectively, for the slice with DQId equal to (sliceIdc[ CurrMbAddr ] & 127) and first\_mb\_in\_slice equal to (sliceIdc[ CurrMbAddr ] >> 7). +2. When disableDeblockingFilterIdc is equal to 3 or 6, the macroblock deblocking filter process as specified in clause F.8.7.4 is invoked with interLayerDeblockingFlag = 0, disableDeblockingFilterIdc, filterOffsetA, filterOffsetB, sliceBoundariesOnlyFlag = 1, currentVars, qpDBV and, when ChromaArrayType is not equal to 0, qpDBCb and qpDBCr as inputs and the output is a modified version of currentVars. + +### F.8.7.3 Derivation process for quantization parameters used in the deblocking filter process + +Inputs to this process are: + +- a variable deblockingDQId, +- a one-dimensional array mbType with PicSizeInMbs elements specifying macroblock types for the macroblocks of the current decoded or partly decoded dependency representation, +- a one-dimensional array tQPV with PicSizeInMbs elements specifying luma quantization parameters for the macroblocks of the current decoded or partly decoded dependency representation, +- a (PicSizeInMbs)x(256 + 2 \* MbWidthC \* MbHeightC) array tCoeffLevel specifying transform coefficient level values for the macroblocks of the current decoded or partly decoded dependency representation. + +Outputs of this process are: + +- a one-dimensional array qpDBV with PicSizeInMbs elements specifying luma quantization parameters used in the deblocking filter process for the macroblocks of the current decoded or partly decoded dependency representation, +- when ChromaArrayType is not equal to 0, two one-dimensional arrays qpDBCb and qpDBCr with PicSizeInMbs elements specifying chroma quantization parameters used in the deblocking filter process for the macroblocks of the current decoded or partly decoded dependency representation. + +The syntax elements and derived upper-case variables that are referred to by the process specified in this clause are the syntax elements and derived upper-case variables for the layer representation with DQId equal to deblockingDQId. + +Let tempQP be a one-dimensional array with PicSizeInMbs elements. All elements tempQP[ i ] with i = 0..(PicSizeInMbs - 1) are set equal to tQPV[ i ]. + +When MaxTCoeffLevelPredFlag is equal to 1, the following ordered steps are specified: + +1. Let `firstMbInSliceGroup` and `numMbsInSliceGroup` be two one-dimensional arrays with `(num_slice_groups_minus1 + 1)` elements. The array elements are derived as specified by the following pseudo code. + +``` + +for( iGroup = 0; iGroup <= num_slice_groups_minus1; iGroup++ ) { + firstMbInSliceGroup[ iGroup ] = -1 + numMbsInSliceGroup[ iGroup ] = 0 +} +for( i = 0; i < PicSizeInMbs; i++ ) { + if( firstMbInSliceGroup[ MbToSliceGroupMap[ i ] ] == -1 ) + firstMbInSliceGroup[ MbToSliceGroupMap[ i ] ] = i + numMbsInSliceGroup[ MbToSliceGroupMap[ i ] ]++ +} + +``` + +(F-347) + +2. The variable `iGroup` proceeds over the values `0..num_slice_groups_minus1`. For each value of `iGroup`, the variable `lastMbAddr` is set equal to `firstMbInSliceGroup[ iGroup ]` and the variable `mbIdx` proceeds over the values `1..(numMbsInSliceGroup[ iGroup ] - 1)`. For each value of `mbIdx`, the following ordered steps are specified. + +- a. The variable `mbAddr` is derived as specified by the following pseudo-code: + +``` + +mbAddr = lastMbAddr + 1 +while( MbToSliceGroupMap[ mbAddr ] != MbToSliceGroupMap[ lastMbAddr ] ) + mbAddr++ + +``` + +(F-348) + +- b. When `mbType[ mbAddr ]` is not equal to `I_16x16` and all elements `tCoeffLevel[ mbAddr ][ i ]` with `i = 0..(255 + 2 * MbWidthC * MbHeightC)` are equal to 0, `tempQP[ mbAddr ]` is set equal to `tempQP[ lastMbAddr ]`. +- c. The variable `lastMbAddr` is set equal to `mbAddr`. + +The macroblock address `mbAddr` proceeds over the values `0..(PicSizeInMbs - 1)`, and for each value of `mbAddr`, the following ordered steps are specified: + +1. The variable `qpDBY[ mbAddr ]` is derived as follows: + - If `mbType[ mbAddr ]` is equal to `I_PCM`, `qpDBY[ mbAddr ]` is set equal to 0. + - Otherwise (`mbType[ mbAddr ]` is not equal to `I_PCM`), `qpDBY[ mbAddr ]` is set equal to `tempQP[ mbAddr ]`. +2. When `ChromaArrayType` is not equal to 0, for `C` being replaced by `Cb` and `Cr`, the variable `qpDBC[ mbAddr ]` is set equal to the value of `QPC` that corresponds to a value of `qpDBY[ mbAddr ]` for `QPY` as specified in clause 8.5.8. During this invocation of the process in clause 8.5.8, the syntax elements `chroma_qp_index_offset` and `second_chroma_qp_index_offset` of the layer representation with `DQId` equal to `deblockingFilterDQId` are used. + +#### F.8.7.4 Macroblock deblocking filter process + +Inputs to this process are: + +- the variables `interLayerDeblockingFlag`, `disableDeblockingFilterIdc`, `filterOffsetA`, `filterOffsetB`, and `sliceBoundariesOnlyFlag`, +- the collective term `currentVars`, +- a one-dimensional array `qpDBY` with `PicSizeInMbs` elements specifying luma quantization parameters used in the deblocking filter process for the macroblocks of the current decoded or partly decoded dependency representation, +- when `ChromaArrayType` is not equal to 0, two one-dimensional arrays `qpDBCb` and `qpDBCr` with `PicSizeInMbs` elements specifying chroma quantization parameters used in the deblocking filter process for the macroblocks of the current decoded or partly decoded dependency representation. + +Output of this process is a modified version of `currentVars`. + +In the following of this clause, the arrays that are collectively referred to as `currentVars` are referred to by their names as specified in clause F.8.1.2.1. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. For this invocation of the process in clause 6.4.11.1, the current macroblock is treated as field macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 1, and it is treated as frame macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 0. + +NOTE 1 – The availability status of the macroblocks mbAddrA and mbAddrB is not used inside this clause. Slice boundaries are detected using the array sliceIdc. + +The variable filterLeftLumaMbEdgeFlag is derived as follows: + +- If any of the following conditions are true, the variable filterLeftLumaMbEdgeFlag is set equal to 0: + - MbaffFrameFlag is equal to 0 and CurrMbAddr % PicWidthInMbs is equal to 0, + - MbaffFrameFlag is equal to 1 and ( CurrMbAddr >> 1 ) % PicWidthInMbs is equal to 0, + - disableDeblockingFilterIdc is equal to 1, + - disableDeblockingFilterIdc is equal to 2 or 5 and sliceIdc[ mbAddrA ] is different than sliceIdc[ CurrMbAddr ], + - disableDeblockingFilterIdc is equal to 3 or 6, sliceBoundariesOnlyFlag is equal to 0, and sliceIdc[ mbAddrA ] is different than sliceIdc[ CurrMbAddr ], + - disableDeblockingFilterIdc is equal to 3 or 6, sliceBoundariesOnlyFlag is equal to 1, and sliceIdc[ mbAddrA ] is equal to sliceIdc[ CurrMbAddr ], + - interLayerDeblockingFlag is equal to 1 and mbType[ CurrMbAddr ] specifies an Inter macroblock prediction mode. +- Otherwise, the variable filterLeftLumaMbEdgeFlag is set equal to 1. + +The variable filterTopLumaMbEdgeFlag is derived as follows: + +- If any of the following conditions are true, the variable filterTopLumaMbEdgeFlag is set equal to 0: + - MbaffFrameFlag is equal to 0 and CurrMbAddr is less than PicWidthInMbs, + - MbaffFrameFlag is equal to 1, ( CurrMbAddr >> 1 ) is less than PicWidthInMbs, and fieldMbFlag[ CurrMbAddr ] is equal to 1, + - MbaffFrameFlag is equal to 1, ( CurrMbAddr >> 1 ) is less than PicWidthInMbs, fieldMbFlag[ CurrMbAddr ] is equal to 0, and CurrMbAddr % 2 is equal to 0, + - disableDeblockingFilterIdc is equal to 1, + - disableDeblockingFilterIdc is equal to 2 or 5 and sliceIdc[ mbAddrB ] is different than sliceIdc[ CurrMbAddr ], + - disableDeblockingFilterIdc is equal to 3 or 6, sliceBoundariesOnlyFlag is equal to 0, and sliceIdc[ mbAddrB ] is different than sliceIdc[ CurrMbAddr ], + - disableDeblockingFilterIdc is equal to 3 or 6, sliceBoundariesOnlyFlag is equal to 1, and sliceIdc[ mbAddrB ] is equal to sliceIdc[ CurrMbAddr ], + - interLayerDeblockingFlag is equal to 1 and mbType[ CurrMbAddr ] specifies an Inter macroblock prediction mode. +- Otherwise, the variable filterTopLumaMbEdgeFlag is set equal to 1. + +The variable filterInternalLumaEdgesFlag is derived as follows: + +- If any of the following conditions are true, the variable filterInternalLumaEdgesFlag is set equal to 0: + - disableDeblockingFilterIdc is equal to 1, + - disableDeblockingFilterIdc is equal to 3 or 6 and sliceBoundariesOnlyFlag is equal to 1, + - interLayerDeblockingFlag is equal to 1 mbType[ CurrMbAddr ] specifies an Inter macroblock prediction mode. +- Otherwise the variable filterInternalLumaEdgesFlag is set equal to 1. + +The variables filterLeftChromaMbEdgeFlag, filterTopChromaMbEdgeFlag, and filterInternalChromaEdgesFlag are derived as follows: + +- If disableDeblockingFilterIdc is greater than 3, filterLeftChromaMbEdgeFlag, filterTopChromaMbEdgeFlag, and filterInternalChromaEdgesFlag are set equal to 0. + +- Otherwise (disableDeblockingFilterIdc is less than 4), filterLeftChromaMbEdgeFlag, filterTopChromaMbEdgeFlag, and filterInternalChromaEdgesFlag are set equal to filterLeftLumaMbEdgeFlag, filterTopLumaMbEdgeFlag, and filterInternalLumaEdgesFlag, respectively. + +The variable fieldMbInFrameFlag is derived as follows: + +- If MbuffFrameFlag is equal to 1 and fieldMbFlag[ CurrMbAddr ] is equal to 1, fieldMbInFrameFlag is set equal to 1. +- Otherwise (MbuffFrameFlag is equal to 0 or fieldMbFlag[ CurrMbAddr ] is equal to 0), fieldMbInFrameFlag is set equal to 0. + +When filterLeftLumaMbEdgeFlag is equal to 1, the left vertical luma edge is filtered by invoking the process specified in clause F.8.7.4.1 with interLayerDeblockingFlag, chromaEdgeFlag set equal to 0, verticalEdgeFlag set equal to 1, fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBY, currentVars, (xEk, yEk) set equal to (0, k) with k = 0..15, and cSL as the inputs and cSL as the output. + +When filterInternalLumaEdgesFlag is equal to 1, the filtering of the internal vertical luma edges is specified by the following ordered steps: + +1. When cTraf[ CurrMbAddr ] is not equal to T\_8x8, the process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 0, verticalEdgeFlag set equal to 1, fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBY, currentVars, (xEk, yEk) set equal to (4, k) with k = 0..15, and cSL as the inputs and cSL as the output. +2. The process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 0, verticalEdgeFlag set equal to 1, fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBY, currentVars, (xEk, yEk) set equal to (8, k) with k = 0..15, and cSL as the inputs and cSL as the output. +3. When cTraf[ CurrMbAddr ] is not equal to T\_8x8, the process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 0, verticalEdgeFlag set equal to 1, fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBY, currentVars, (xEk, yEk) set equal to (12, k) with k = 0..15, and cSL as the inputs and cSL as the output. + +When filterTopLumaMbEdgeFlag is equal to 1, the filtering of the top horizontal luma edge is specified as follows: + +- If MbuffFrameFlag is equal to 1, (CurrMbAddr % 2) is equal to 0, CurrMbAddr is greater than or equal to (2 \* PicWidthInMbs), fieldMbFlag[ CurrMbAddr ] is equal to 0, and fieldMbFlag[ CurrMbAddr – 2 \* PicWidthInMbs + 1 ] is equal to 1, the following ordered steps are specified: + 1. The process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 0, verticalEdgeFlag set equal to 0, fieldModeInFrameFilteringFlag set equal to 1, filterOffsetA, filterOffsetB, qpDB set equal to qpDBY, currentVars, (xEk, yEk) set equal to (k, 0) with k = 0..15, and cSL as the inputs and cSL as the output. + 2. The process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 0, verticalEdgeFlag set equal to 0, fieldModeInFrameFilteringFlag set equal to 1, filterOffsetA, filterOffsetB, qpDB set equal to qpDBY, currentVars, (xEk, yEk) set equal to (k, 1) with k = 0..15, and cSL as the inputs and cSL as the output. +- Otherwise, the process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 0, verticalEdgeFlag set equal to 0, fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBY, currentVars, (xEk, yEk) set equal to (k, 0) with k = 0..15, and cSL as the inputs and cSL as the output. + +When filterInternalLumaEdgesFlag is equal to 1, the filtering of the internal horizontal luma edges is specified by the following ordered steps: + +1. When cTraf[ CurrMbAddr ] is not equal to T\_8x8, the process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 0, verticalEdgeFlag set equal to 0, fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBY, currentVars, (xEk, yEk) set equal to (k, 4) with k = 0..15, and cSL as the inputs and cSL as the output. +2. The process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 0, verticalEdgeFlag set equal to 0, fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBY, currentVars, (xEk, yEk) set equal to (k, 8) with k = 0..15, and cSL as the inputs and cSL as the output. + +3. When `cTrafo[ CurrMbAddr ]` is not equal to `T_8x8`, the process specified in clause F.8.7.4.1 is invoked with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 0, `verticalEdgeFlag` set equal to 0, `fieldModeInFrameFilteringFlag` set equal to `fieldMbInFrameFlag`, `filterOffsetA`, `filterOffsetB`, `qpDB` set equal to `qpDBV`, `currentVars`, `(xEk, yEk)` set equal to `(k, 12)` with `k = 0..15`, and `cSL` as the inputs and `cSL` as the output. + +When `ChromaArrayType` is not equal to 0, for the filtering of both chroma components with C being replaced by Cb and Cr in `qpDBC` and `cSC`, the following ordered steps are specified: + +1. When `filterLeftChromaMbEdgeFlag` is equal to 1, the left vertical chroma edge is filtered by invoking the process specified in clause F.8.7.4.1 with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 1, `verticalEdgeFlag` set equal to 1, `fieldModeInFrameFilteringFlag` set equal to `fieldMbInFrameFlag`, `filterOffsetA`, `filterOffsetB`, `qpDB` set equal to `qpDBC`, `currentVars`, `(xEk, yEk)` set equal to `(0, k)` with `k = 0..(MbHeightC - 1)`, and `cSC` as the inputs and `cSC` as the output. +2. When `filterInternalChromaEdgesFlag` is equal to 1, the filtering of the internal vertical chroma edge is specified by the following ordered steps: + - a. When `ChromaArrayType` is not equal to 3 or `cTrafo[ CurrMbAddr ]` is not equal to `T_8x8`, the process specified in clause F.8.7.4.1 is invoked with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 1, `verticalEdgeFlag` set equal to 1, `fieldModeInFrameFilteringFlag` set equal to `fieldMbInFrameFlag`, `filterOffsetA`, `filterOffsetB`, `qpDB` set equal to `qpDBC`, `currentVars`, `(xEk, yEk)` set equal to `(4, k)` with `k = 0..(MbHeightC - 1)`, and `cSC` as the inputs and `cSC` as the output. + - b. When `ChromaArrayType` is equal to 3, the process specified in clause F.8.7.4.1 is invoked with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 1, `verticalEdgeFlag` set equal to 1, `fieldModeInFrameFilteringFlag` set equal to `fieldMbInFrameFlag`, `filterOffsetA`, `filterOffsetB`, `qpDB` set equal to `qpDBC`, `currentVars`, `(xEk, yEk)` set equal to `(8, k)` with `k = 0..(MbHeightC - 1)`, and `cSC` as the inputs and `cSC` as the output. + - c. When `ChromaArrayType` is equal to 3 and `cTrafo[ CurrMbAddr ]` is not equal to `T_8x8`, the process specified in clause F.8.7.4.1 is invoked with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 1, `verticalEdgeFlag` set equal to 1, `fieldModeInFrameFilteringFlag` set equal to `fieldMbInFrameFlag`, `filterOffsetA`, `filterOffsetB`, `qpDB` set equal to `qpDBC`, `currentVars`, `(xEk, yEk)` set equal to `(12, k)` with `k = 0..(MbHeightC - 1)`, and `cSC` as the inputs and `cSC` as the output. +3. When `filterTopChromaMbEdgeFlag` is equal to 1, the filtering of the top horizontal chroma edge is specified as follows: + - If `MbAffFrameFlag` is equal to 1, `(CurrMbAddr % 2)` is equal to 0, `CurrMbAddr` is greater than or equal to `(2 * PicWidthInMbs)`, `fieldMbFlag[ CurrMbAddr ]` is equal to 0, `fieldMbFlag[ CurrMbAddr - 2 * PicWidthInMbs + 1 ]` is equal to 1, the following ordered steps are specified: + - a. The process specified in clause F.8.7.4.1 is invoked with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 1, `verticalEdgeFlag` set equal to 0, `fieldModeInFrameFilteringFlag` set equal to 1, `filterOffsetA`, `filterOffsetB`, `qpDB` set equal to `qpDBC`, `currentVars`, `(xEk, yEk)` set equal to `(k, 0)` with `k = 0..(MbWidthC - 1)`, and `cSC` as the inputs and `cSC` as the output. + - b. The process specified in clause F.8.7.4.1 is invoked with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 1, `verticalEdgeFlag` set equal to 0, `fieldModeInFrameFilteringFlag` set equal to 1, `filterOffsetA`, `filterOffsetB`, `qpDB` set equal to `qpDBC`, `currentVars`, `(xEk, yEk)` set equal to `(k, 1)` with `k = 0..(MbWidthC - 1)`, and `cSC` as the inputs and `cSC` as the output. + - Otherwise, the process specified in clause F.8.7.4.1 is invoked with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 1, `verticalEdgeFlag` set equal to 0, `fieldModeInFrameFilteringFlag` set equal to `fieldMbInFrameFlag`, `filterOffsetA`, `filterOffsetB`, `qpDB` set equal to `qpDBC`, `currentVars`, `(xEk, yEk)` set equal to `(k, 0)` with `k = 0..(MbWidthC - 1)`, and `cSC` as the inputs and `cSC` as the output. +4. When `filterInternalChromaEdgesFlag` is equal to 1, the filtering of the internal horizontal chroma edge is specified by the following ordered steps: + - a. When `ChromaArrayType` is not equal to 3 or `cTrafo[ CurrMbAddr ]` is not equal to `T_8x8`, the process specified in clause F.8.7.4.1 is invoked with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 1, `verticalEdgeFlag` set equal to 0, `fieldModeInFrameFilteringFlag` set equal to `fieldMbInFrameFlag`, `filterOffsetA`, `filterOffsetB`, `qpDB` set equal to `qpDBC`, `currentVars`, `(xEk, yEk)` set equal to `(k, 4)` with `k = 0..(MbWidthC - 1)`, and `cSC` as the inputs and `cSC` as the output. + - b. When `ChromaArrayType` is not equal to 1, the process specified in clause F.8.7.4.1 is invoked with `interLayerDeblockingFlag`, `chromaEdgeFlag` set equal to 1, `verticalEdgeFlag` set equal to 0, + +fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBC, currentVars, (xEk, yEk) set equal to (k, 8) with k = 0..(MbWidthC - 1), and cSC as the inputs and cSC as the output. + +- c. When ChromaArrayType is equal to 2, the process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 1, verticalEdgeFlag set equal to 0, fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBC, currentVars, (xEk, yEk) set equal to (k, 12) with k = 0..(MbWidthC - 1), and cSC as the inputs and cSC as the output. +- d. When ChromaArrayType is equal to 3 and cTrafo[ CurrMbAddr ] is not equal to T\_8x8, the process specified in clause F.8.7.4.1 is invoked with interLayerDeblockingFlag, chromaEdgeFlag set equal to 1, verticalEdgeFlag set equal to 0, fieldModeInFrameFilteringFlag set equal to fieldMbInFrameFlag, filterOffsetA, filterOffsetB, qpDB set equal to qpDBC, currentVars, (xEk, yEk) set equal to (k, 12) with k = 0..(MbWidthC - 1), and cSC as the inputs and cSC as the output. + +NOTE 2 – When field mode filtering (fieldModeInFrameFilteringFlag is equal to 1) is applied across the top horizontal edges of a frame macroblock, this vertical filtering across the top or bottom macroblock boundary may involve some samples that extend across an internal block edge that is also filtered internally in frame mode. + +NOTE 3 – For example, in 4:2:0 chroma format when cTrafo[ CurrMbAddr ] is not equal to T\_8x8, the following applies. 3 horizontal luma edges, 1 horizontal chroma edge for Cb, and 1 horizontal chroma edge for Cr are filtered that are internal to a macroblock. When field mode filtering (fieldModeInFrameFilteringFlag is equal to 1) is applied to the top edges of a frame macroblock, 2 horizontal luma, 2 horizontal chroma edges for Cb, and 2 horizontal chroma edges for Cr between the frame macroblock and the above macroblock pair are filtered using field mode filtering, for a total of up to 5 horizontal luma edges, 3 horizontal chroma edges for Cb, and 3 horizontal chroma edges for Cr filtered that are considered to be controlled by the frame macroblock. In all other cases, at most 4 horizontal luma, 2 horizontal chroma edges for Cb, and 2 horizontal chroma edges for Cr are filtered that are considered to be controlled by a particular macroblock. + +#### F.8.7.4.1 SVC filtering process for block edges + +Inputs to this process are: + +- the variable interLayerDeblockingFlag, +- the variable chromaEdgeFlag, +- the variable verticalEdgeFlag, +- the variable fieldModeInFrameFilteringFlag, +- the variables filterOffsetA and filterOffsetB, +- the one-dimensional array qpDB with PicSizeInMbs elements specifying quantization parameters, +- the collective term currentVars, +- a set of nE sample locations (xEk, yEk), with k = 0..(nE - 1), expressed relative to the upper left corner of the macroblock CurrMbAddr. The set of sample locations (xEk, yEk) represent the sample locations immediately to the right of a vertical edge (when verticalEdgeFlag is equal to 1) or immediately below a horizontal edge (when verticalEdgeFlag is equal to 0), +- an array of samples s'. + +Output of this process is a modified version of the array s'. + +The variable nE is derived as follows: + +- If chromaEdgeFlag is equal to 0, nE is set equal to 16. +- Otherwise (chromaEdgeFlag is equal to 1), nE is set equal to (( verticalEdgeFlag == 1 ) ? MbHeightC : MbWidthC ). + +Inside this clause, the arrays that are collectively referred to as currentVars are referred to by their names as specified in clause F.8.1.2.1. + +The variable dy is set equal to (1 + fieldModeInFrameFilteringFlag). + +The position of the upper-left luma sample of the macroblock CurrMbAddr is derived by invoking the inverse macroblock scanning process in clause 6.4.1 with mbAddr = CurrMbAddr as input and the output being assigned to ( xI, yI ). During the process in clause 6.4.1, the current macroblock is treated as field macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 1, and it is treated as frame macroblock when fieldMbFlag[ CurrMbAddr ] is equal to 0. + +The variables xP and yP are derived as follows: + +- If chromaEdgeFlag is equal to 0, xP is set equal to xI and yP is set equal to yI. +- Otherwise (chromaEdgeFlag is equal to 1), xP is set equal to (xI / SubWidthC) and yP is set equal to (( yI + SubHeightC – 1 ) / SubHeightC ). + +For each sample location ( xEk, yEk ), k = 0..(nE – 1), the following ordered steps are specified: + +1. The filtering process is applied to a set of eight samples across a 4x4 block horizontal or vertical edge denoted as pi and qi with i = 0..3 as shown in Figure 8-11 with the edge lying between p0 and q0. pi and qi with i = 0..3 are specified as follows: + - If verticalEdgeFlag is equal to 1, + +$$q_i = s'[ xP + xE_k + i, yP + dy * yE_k ] \quad (F-349)$$ + +$$p_i = s'[ xP + xE_k - i - 1, yP + dy * yE_k ] \quad (F-350)$$ + +- Otherwise (verticalEdgeFlag is equal to 0), + +$$q_i = s'[ xP + xE_k, yP + dy * ( yE_k + i ) - ( yE_k \% 2 ) ] \quad (F-351)$$ + +$$p_i = s'[ xP + xE_k, yP + dy * ( yE_k - i - 1 ) - ( yE_k \% 2 ) ] \quad (F-352)$$ + +2. Let mbAddrP and mbAddrQ specify the addresses of the macroblocks that contain the samples p0 and q0, respectively. +3. The process specified in clause F.8.7.4.2 is invoked with the sample values pi and qi (i = 0..3), interLayerDeblockingFlag, chromaEdgeFlag, verticalEdgeFlag, filterOffsetA, filterOffsetB, qPp set equal to qpDB[ mbAddrP ], qPq set equal to qpDB[ mbAddrQ ], sliceIdc, fieldMbFlag, mbType, cTrafo, predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, mvL1, and rSL as inputs, and the output is assigned to the filtered result sample values p'i and q'i with i = 0..2. +4. The input sample values pi and qi with i = 0..2 are replaced by the corresponding filtered result sample values p'i and q'i with i = 0..2 inside the sample array s' as follows: + +- If verticalEdgeFlag is equal to 1, + +$$s'[ xP + xE_k + i, yP + dy * yE_k ] = q'_i \quad (F-353)$$ + +$$s'[ xP + xE_k - i - 1, yP + dy * yE_k ] = p'_i \quad (F-354)$$ + +- Otherwise (verticalEdgeFlag is equal to 0), + +$$s'[ xP + xE_k, yP + dy * ( yE_k + i ) - ( yE_k \% 2 ) ] = q'_i \quad (F-355)$$ + +$$s'[ xP + xE_k, yP + dy * ( yE_k - i - 1 ) - ( yE_k \% 2 ) ] = p'_i \quad (F-356)$$ + +#### F.8.7.4.2 SVC filtering process for a set of samples across a horizontal or vertical block edge + +Inputs to this process are: + +- the input sample values pi and qi with i = 0..3 of a single set of samples across an edge that is to be filtered, +- the variable interLayerDeblockingFlag, +- the variable chromaEdgeFlag, +- the variable verticalEdgeFlag, +- the variables filterOffsetA and filterOffsetB, +- the variables qPp and qPq, +- the arrays sliceIdc, fieldMbFlag, mbType, cTrafo, predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, and mvL1, +- an array rSL containing residual sample values. + +Outputs of this process are the filtered result sample values p'i and q'i with i in the range of 0..2. + +The content dependent boundary filtering strength variable bS is derived as follows: + +- If chromaEdgeFlag is equal to 0, the SVC derivation process for the luma content dependent boundary filtering strength specified in clause F.8.7.4.3 is invoked with p0, q0, interLayerDeblockingFlag, verticalEdgeFlag, sliceIdc, fieldMbFlag, mbType, cTrafo, predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, mvL1, and rSL as inputs, and the output is assigned to bS. + +- Otherwise (chromaEdgeFlag is equal to 1), the bS used for filtering a set of samples of a horizontal or vertical chroma edge is set equal to the value of bS for filtering the set of samples of a horizontal or vertical luma edge, respectively, that contains the luma sample at location ( SubWidthC \* x, SubHeightC \* y ) inside the luma array of the same field, where ( x, y ) is the location of the chroma sample $q_0$ inside the chroma array for that field. + +The process specified in clause 8.7.2.2 is invoked with $p_0$ , $q_0$ , $p_1$ , $q_1$ , chromaEdgeFlag, bS, filterOffsetA, filterOffsetB, $qP_p$ , and $qP_q$ as inputs, and the output is assigned to filterSamplesFlag, indexA, $\alpha$ , and $\beta$ . + +Depending on the variable filterSamplesFlag, the following applies: + +- If filterSamplesFlag is equal to 1, the following applies: + - If bS is less than 4, the process specified in clause 8.7.2.3 is invoked with $p_i$ and $q_i$ ( $i = 0..2$ ), chromaEdgeFlag, bS, $\beta$ , and indexA given as input, and the output is assigned to $p'_i$ and $q'_i$ ( $i = 0..2$ ). + - Otherwise (bS is equal to 4), the process specified in clause 8.7.2.4 is invoked with $p_i$ and $q_i$ ( $i = 0..3$ ), chromaEdgeFlag, $\alpha$ , and $\beta$ given as input, and the output is assigned to $p'_i$ and $q'_i$ ( $i = 0..2$ ). +- Otherwise (filterSamplesFlag is equal to 0), the filtered result samples $p'_i$ and $q'_i$ ( $i = 0..2$ ) are replaced by the corresponding input samples $p_i$ and $q_i$ : + +$$\text{for } i = 0..2, \quad p'_i = p_i; \tag{F-357}$$ + +$$\text{for } i = 0..2, \quad q'_i = q_i; \tag{F-358}$$ + +#### F.8.7.4.3 SVC derivation process for the luma content dependent boundary filtering strength + +Inputs to this process are: + +- the input sample values $p_0$ and $q_0$ of a single set of samples across an edge that is to be filtered, +- the variable interLayerDeblockingFlag, +- the variable verticalEdgeFlag, +- the arrays sliceIdc, fieldMbFlag, mbType, cTrafo, predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, and mvL1, +- the array rSL containing residual sample values. + +Output of this process is the variable bS. + +The following variables are derived as specified in the following: + +- mbAddrP and mbAddrQ specify the macroblocks containing the samples $p_0$ and $q_0$ , respectively. +- mbPartIdxP and mbPartIdxQ specify the macroblock partitions containing the samples $p_0$ and $q_0$ , respectively. +- subMbPartIdxP and subMbPartIdxQ specify the sub-macroblock partitions containing the samples $p_0$ and $q_0$ , respectively. +- pFLXP and pFLXQ with X being replaced by 0 and 1 are equal to predFlagLX[ mbAddrP ][ mbPartIdxP ] and predFlagLX[ mbAddrQ ][ mbPartIdxQ ], respectively. +- reflXP and reflXQ with X being replaced by 0 and 1 are equal to refIdxLX[ mbAddrP ][ mbPartIdxP ] and refIdxLX[ mbAddrQ ][ mbPartIdxQ ], respectively. +- mvLXP and mvLXQ with X being replaced by 0 and 1 are equal to mvLX[ mbAddrP ][ mbPartIdxP ][ subMbPartP ] and mvLX[ mbAddrQ ][ mbPartIdxQ ][ subMbPartQ ], respectively. +- numMvP and numMvQ are equal to (pFL0P + pFL1P) and (pFL0Q + pFL1Q), respectively. +- When numMvP and numMvQ are both equal to 1, the variables refX and mvX with X being replaced by P and Q are derived as follows: + - If pFL0X is equal to 1, refX is set equal to refl0X and mvX is set equal to mvL0X. + - Otherwise (pFL1X is equal to 1), refX is set equal to refl1X and mvX is set equal to mvL1X. +- sliceX with X being replaced by P and Q is the slice with DQId equal to (sliceIdc[ mbAddrX ] & 127) and first\_mb\_in\_slice equal to (sliceIdc[ mbAddrX ] >> 7) + +Let the variable mixedModeEdgeFlag be derived as follows: + +- If MbaffFrameFlag is equal to 1 and fieldMbFlag[ mbAddrP ] is not equal to fieldMbFlag[ mbAddrQ ], mixedModeEdgeFlag is set equal to 1. + +- Otherwise, mixedModeEdgeFlag is set equal to 0. + +The variable bS is derived as follows: + +- If interLayerDeblockingFlag is equal to 1 and mbType[ mbAddrP ] specifies an Inter macroblock prediction mode, bS is set equal to 0. + +NOTE 1 – This clause is not invoked when interLayerDeblockingFlag is equal to 1 and mbType[ mbAddrQ ] specifies an Inter macroblock prediction mode. + +- Otherwise, if SpatialResolutionChangeFlag is equal to 1 and either or both mbType[ mbAddrP ] or mbType[ mbAddrQ ] is equal to I\_BL, the following applies: + - If either mbType[ mbAddrP ] or mbType[ mbAddrQ ] specifies an Intra macroblock prediction mode other than I\_BL, the following applies: + - If verticalEdgeFlag is equal to 1 or both fieldMbFlag[ mbAddrP ] and fieldMbFlag[ mbAddrQ ] are equal to 0, bS is set equal to 4. + - Otherwise (verticalEdgeFlag is equal to 0 and either or both fieldMbFlag[ mbAddrP ] or fieldMbFlag[ mbAddrQ ] is equal to 1), bS is set equal to 3. + - Otherwise, if mbType[ mbAddrP ] is equal to I\_BL and mbType[ mbAddrQ ] is equal to I\_BL, the following applies: + - If any of the following conditions are true, bS is set equal to 1: + - cTrafo[ mbAddrP ] is equal to T\_8x8 and the 8x8 luma transform block coded in sliceP and associated with the 8x8 luma block containing sample $p_{0}$ contains non-zero transform coefficient levels, + - cTrafo[ mbAddrP ] is equal to T\_4x4 and the 4x4 luma transform block coded in sliceP and associated with the 4x4 luma block containing sample $p_{0}$ contains non-zero transform coefficient levels, + - cTrafo[ mbAddrQ ] is equal to T\_8x8 and the 8x8 luma transform block coded in sliceQ and associated with the 8x8 luma block containing sample $q_{0}$ contains non-zero transform coefficient levels, + - cTrafo[ mbAddrQ ] is equal to T\_4x4 and the 4x4 luma transform block coded in sliceQ and associated with the 4x4 luma block containing sample $q_{0}$ contains non-zero transform coefficient levels. + +NOTE 2 – A luma transform block coded in a particular slice is considered to contain non-zero transform coefficient levels, if non-zero transform coefficients are transmitted in the macroblock layer of the slice for the considered luma transform block. Transform coefficient levels that are transmitted in layers that are used for inter-layer prediction are not taken into account. + +- Otherwise, bS is set equal to 0. + +- Otherwise (either mbType[ mbAddrP ] or mbType[ mbAddrQ ] specifies an Inter macroblock prediction mode), the following applies: + - If any of the following conditions are true, bS is set equal to 2: + - mbType[ mbAddrP ] specifies an Inter macroblock prediction type, cTrafo[ mbAddrP ] is equal to T\_8x8, and the array rSL contains non-zero samples for the 8x8 luma block containing sample $p_{0}$ , + - mbType[ mbAddrP ] specifies an Inter macroblock prediction type, cTrafo[ mbAddrP ] is equal to T\_4x4, and the array rSL contains non-zero samples for the 4x4 luma block containing sample $p_{0}$ , + - mbType[ mbAddrQ ] specifies an Inter macroblock prediction type, cTrafo[ mbAddrQ ] is equal to T\_8x8, and the array rSL contains non-zero samples for the 8x8 luma block containing sample $q_{0}$ , + - mbType[ mbAddrQ ] specifies an Inter macroblock prediction type, cTrafo[ mbAddrQ ] is equal to T\_4x4, and the array rSL contains non-zero samples for the 4x4 luma block containing sample $q_{0}$ . + +NOTE 3 – The array rSL contains samples for the accumulated residual signal. Transform coefficient values of layer representations that are used for inter-layer prediction are taken into account. + +- Otherwise, bS is set equal to 1. + +- Otherwise, if the block edge is also a macroblock edge and any of the following conditions are true, bS is set equal to 4: + - fieldMbFlag[ mbAddrP ] is equal to 0 and fieldMbFlag[ mbAddrQ ] is equal to 0 and either or both mbType[ mbAddrP ] or mbType[ mbAddrQ ] specify an Intra macroblock prediction mode, + +- MbuffFrameFlag is equal to 1 or field\_pic\_flag is equal to 1, and verticalEdgeFlag is equal to 1, and either or both mbType[ mbAddrP ] or mbType[ mbAddrQ ] specify an Intra macroblock prediction mode. +- Otherwise, if any of the following conditions are true, bS is set equal to 3: + - mixedModeEdgeFlag is equal to 0 and either or both mbType[ mbAddrP ] or mbType[ mbAddrQ ] specify an Intra macroblock prediction mode, + - mixedModeEdgeFlag is equal to 1, verticalEdgeFlag is equal to 0, and either or both mbType[ mbAddrP ] or mbType[ mbAddrQ ] specify an Intra macroblock prediction mode. +- Otherwise, if any of the following conditions are true, bS is set equal to 2: + - cTraf[ mbAddrP ] is equal to T\_8x8 and either the array rSL contains non-zero samples for the 8x8 luma block containing sample p0 or ((sliceIdc[ mbAddrP ] & 127) is equal to 0 and the 8x8 luma transform block coded in sliceP and associated with the 8x8 luma block containing sample p0 contains non-zero transform coefficient levels), + - cTraf[ mbAddrP ] is equal to T\_4x4 and either the array rSL contains non-zero samples for the 4x4 luma block containing sample p0 or ((sliceIdc[ mbAddrP ] & 127) is equal to 0 and the 4x4 luma transform block coded in sliceP and associated with the 4x4 luma block containing sample p0 contains non-zero transform coefficient levels), + - cTraf[ mbAddrQ ] is equal to T\_8x8 and either the array rSL contains non-zero samples for the 8x8 luma block containing sample q0 or ((sliceIdc[ mbAddrQ ] & 127) is equal to 0 and the 8x8 luma transform block coded in sliceQ and associated with the 8x8 luma block containing sample q0 contains non-zero transform coefficient levels), + - cTraf[ mbAddrQ ] is equal to T\_4x4 and either the array rSL contains non-zero samples for the 4x4 luma block containing sample q0 or ((sliceIdc[ mbAddrQ ] & 127) is equal to 0 and the 4x4 luma transform block coded in sliceQ and associated with the 4x4 luma block containing sample q0 contains non-zero transform coefficient levels). + +NOTE 4 – The array rSL contains samples for the accumulated residual signal. Transform coefficient values of layer representations that are used for inter-layer prediction are taken into account. + +- Otherwise, if profile\_idc is equal to 83 and any of the following conditions are true, bS is set equal to 2: + - cTraf[ mbAddrP ] is equal to T\_8x8 and the array sTCoeff[ mbAddrP ] contains non-zero scaled transform coefficient values for the 8x8 luma transform block associated with the 8x8 luma block containing sample p0, + - cTraf[ mbAddrP ] is equal to T\_4x4 and the array sTCoeff[ mbAddrP ] contains non-zero scaled transform coefficient values for the 4x4 luma transform block associated with the 4x4 luma block containing sample p0, + - cTraf[ mbAddrQ ] is equal to T\_8x8 and the array sTCoeff[ mbAddrQ ] contains non-zero scaled transform coefficient values for the 8x8 luma transform block associated with the 8x8 luma block containing sample q0, + - cTraf[ mbAddrQ ] is equal to T\_4x4 and the array sTCoeff[ mbAddrQ ] contains non-zero scaled transform coefficient values for the 4x4 luma transform block associated with the 4x4 luma block containing sample q0. +- Otherwise, if mixedModeEdgeFlag is equal to 1 or any of the following conditions are true, bS is set equal to 1: + 1. numMvP is not equal to numMvQ. + 2. numMvP and numMvQ are both equal to 1 and any of the following conditions are true: + - refP and refQ specify different reference pictures, + - the absolute difference between the horizontal or vertical components of the motion vectors mvP and mvQ is greater than or equal to 4 in units of quarter luma frame samples. + 3. numRefP and numRefQ are both equal to 2 and any of the following conditions are true: + - a. refL0P and refL1P specify different reference pictures and any of the following conditions are true: + - i. both of the following conditions are true: + - refL0P and refL0Q specify different reference pictures or refL1P and refL1Q specify different reference pictures, + - refL0P and refL1Q specify different reference pictures or refL1P and refL0Q specify different reference pictures. + +- ii. refL0P and refL0Q specifies the same reference picture, refL1P and refL1Q specify the same reference picture, and any of the following conditions are true: + - the absolute difference between the horizontal or vertical components of the motion vectors mvL0P and mvL0Q is greater than or equal to 4 in units of quarter luma frame samples, + - the absolute difference between the horizontal or vertical components of the motion vectors mvL1P and mvL1Q is greater than or equal to 4 in units of quarter luma frame samples. + - iii. refL0P and refL1Q specifies the same reference picture, refL1P and refL0Q specify the same reference picture, and any of the following conditions are true: + - the absolute difference between the horizontal or vertical components of the motion vectors mvL0P and mvL1Q is greater than or equal to 4 in units of quarter luma frame samples, + - the absolute difference between the horizontal or vertical components of the motion vectors mvL1P and mvL0Q is greater than or equal to 4 in units of quarter luma frame samples. +- b. refL0P and refL1P specify the same reference picture and any of the following conditions are true: +- i. refL0Q or refL1Q specify a different reference picture than refL0P (or refL1P). + - ii. refL0Q and refL1Q specify the same reference picture as refL0P (and refL1P) and both of the following conditions are true: + - the absolute difference between the horizontal or vertical components of the motion vectors mvL0P and mvL0Q is greater than or equal to 4 in units of quarter luma frame samples or the absolute difference between the horizontal or vertical components of the motion vectors mvL1P and mvL1Q is greater than or equal to 4 in units of quarter luma frame samples, + - the absolute difference between the horizontal or vertical components of the motion vectors mvL0P and mvL1Q is greater than or equal to 4 in units of quarter luma frame samples or the absolute difference between the horizontal or vertical components of the motion vectors mvL1P and mvL0Q is greater than or equal to 4 in units of quarter luma frame samples. + +NOTE 5 – The determination of whether the reference pictures used for the two macroblock/sub-macroblock partitions are the same or different is based only on which pictures are referenced, without regard to whether a prediction is formed using an index into reference picture list 0 or an index into reference picture list 1, and also without regard to whether the index position within a reference picture list is different. + +NOTE 6 – A vertical difference of 4 in units of quarter luma frame samples is a difference of 2 in units of quarter luma field samples + +- Otherwise, bS is set equal to 0. + +The variable interProfileConformanceFlag is derived as follows: + +- If DQId is greater than 0, interLayerDeblockingFlag is equal to 0, and any of the following conditions are true, interProfileConformanceFlag is set equal to 1: + - profile\_idc is equal to 83 and constraint\_set1\_flag is equal to 1, + - profile\_idc is equal to 86 and constraint\_set0\_flag is equal to 1. +- Otherwise, interProfileConformanceFlag is set equal to 0. + +When interProfileConformanceFlag is equal to 1 and both mbType[ mbAddrP ] and mbType[ mbAddrQ ] specify an Inter macroblock prediction mode, it is a requirement of bitstream conformance that the following constraints are obeyed: + +- When cTraf[ mbAddrP ] is equal to T\_8x8 and the array sTCoeff[ mbAddrP ] contains at least one non-zero scaled transform coefficient value for the 8x8 luma transform block associated with the 8x8 luma block containing sample p0, the bitstream shall not contain data that result in an array rSL for which all sample values are equal to 0 for the 8x8 luma block containing sample p0. +- When cTraf[ mbAddrP ] is equal to T\_4x4 and the array sTCoeff[ mbAddrP ] contains at least one non-zero scaled transform coefficient value for the 4x4 luma transform block associated with the 4x4 luma block containing sample p0, the bitstream shall not contain data that result in an array rSL for which all sample values are equal to 0 for the 4x4 luma block containing sample p0. +- When cTraf[ mbAddrQ ] is equal to T\_8x8 and the array sTCoeff[ mbAddrQ ] contains at least one non-zero scaled transform coefficient value for the 8x8 luma transform block associated with the 8x8 luma block containing sample q0, the bitstream shall not contain data that result in an array rSL for which all sample values are equal to 0 for the 8x8 luma block containing sample q0. + +- When $cTraf[o[ mbAddrQ ]]$ is equal to $T\_4x4$ and the array $sTCoeff[o[ mbAddrQ ]]$ contains at least one non-zero scaled transform coefficient value for the 4x4 luma transform block associated with the 4x4 luma block containing sample $q_0$ , the bitstream shall not contain data that result in an array $rS_L$ for which all sample values are equal to 0 for the 4x4 luma block containing sample $q_0$ . + +## F.8.8 Specification of sub-bitstreams + +Clause F.8.8.1 specifies the sub-bitstream extraction process. + +Clause F.8.8.2 specifies the base layer bitstream. + +### F.8.8.1 Sub-bitstream extraction process + +It is requirement of bitstream conformance that any sub-bitstream that is the output of the process specified in this clause with $pIdTarget$ equal to any value in the range of 0 to 63, inclusive, $tIdTarget$ equal to any value in the range of 0 to 7, inclusive, $dIdTarget$ equal to any value in the range of 0 to 7, inclusive, and $qIdTarget$ equal to any value in the range of 0 to 15, inclusive, shall be conforming to this Recommendation | International Standard. + +NOTE – A conforming bitstream contains one or more coded slice NAL units with $priority\_id$ equal to 0, $dependency\_id$ equal to 0, $quality\_id$ equal to 0, and $temporal\_id$ equal to 0. + +Inputs to this process are: + +- a variable $pIdTarget$ (when present), +- a variable $tIdTarget$ (when present), +- a variable $dIdTarget$ (when present), +- a variable $qIdTarget$ (when present). + +Output of this process is a sub-bitstream. + +When $pIdTarget$ is not present as input to this clause, $pIdTarget$ is inferred to be equal to 63. + +When $tIdTarget$ is not present as input to this clause, $tIdTarget$ is inferred to be equal to 7. + +When $dIdTarget$ is not present as input to this clause, $dIdTarget$ is inferred to be equal to 7. + +When $qIdTarget$ is not present as input to this clause, $qIdTarget$ is inferred to be equal to 15. + +The sub-bitstream is derived by applying the following operations in sequential order: + +1. Mark all VCL NAL units and filler data NAL units for which any of the following conditions are true as "to be removed from the bitstream": + - $priority\_id$ is greater than $pIdTarget$ , + - $temporal\_id$ is greater than $tIdTarget$ , + - $dependency\_id$ is greater than $dIdTarget$ , + - $dependency\_id$ is equal to $dIdTarget$ and $quality\_id$ is greater than $qIdTarget$ . +2. Remove all access units for which all VCL NAL units are marked as "to be removed from the bitstream". +3. Remove all VCL NAL units and filler data NAL units that are marked as "to be removed from the bitstream". +4. When $dIdTarget$ is equal to 0 and $qIdTarget$ is equal to 0, remove the following NAL units: + - all NAL units with $nal\_unit\_type$ equal to 14 or 15, + - all NAL units with $nal\_unit\_type$ equal to 6 in which the first SEI message has $payloadType$ in the range of 24 to 35, inclusive. +5. Remove all NAL units with $nal\_unit\_type$ equal to 6 that only contain SEI messages that are part of a scalable nesting SEI message with any of the following properties: + - $sei\_temporal\_id$ is greater than $tIdTarget$ , + - the minimum value of $( sei\_dependency\_id[ i ] \ll 4 ) + sei\_quality\_id[ i ]$ for all $i$ in the range of 0 to $num\_layer\_representations\_minus1$ , inclusive, is greater than $( dIdTarget \ll 4 ) + qIdTarget$ . +6. Remove all NAL units with $nal\_unit\_type$ equal to 6 that contain SEI messages with $payloadType$ equal to 24, 28, or 29. + +### F.8.8.2 Specification of the base layer bitstream + +Each scalable bitstream that conforms to this specification shall contain a base layer bitstream that conforms to one or more of the profiles specified in Annex A. This base layer bitstream is derived by invoking the sub-bitstream extraction process as specified in clause F.8.8.1 with dIdTarget being equal to 0 and qIdTarget being equal to 0 and the base layer bitstream being the output. + +NOTE – Although all scalable bitstreams that conform to one or more of the profiles specified in this annex contain a base layer bitstream that conforms to one or more of the profiles specified in Annex A, the complete scalable bitstream (prior to operation of the base layer extraction process specified in this clause) may not conform to any profile specified in Annex A. + +## F.9 Parsing process + +Inputs to this process are bits from the RBSP, a request for a value of a syntax element, and values of prior parsed syntax elements (if applicable). + +Output of this process is the value of the syntax element. + +This process is invoked for all syntax elements in the syntax tables in clause F.7.3 with descriptors equal to u(v), ue(v), me(v), se(v), te(v), ce(v), and ae(v). + +When the parsing process is invoked for the first request for a value of a syntax element in the slice data and entropy\_coding\_mode\_flag is equal to 1, the following ordered steps apply: + +1. The initialization process as specified in clause 9.3.1 is invoked, where a slice\_type equal to EI is interpreted as I, a slice\_type equal to EP is interpreted as P, and a slice\_type equal to EB is interpreted as B. +2. The initialization process as specified in clause F.9.3.1 is invoked. + +Depending on entropy\_coding\_mode\_flag and the descriptor, the value of a syntax element is derived as follows: + +- If entropy\_coding\_mode\_flag is equal to 0, the following applies: + 1. The parsing process for syntax elements coded as ue(v), se(v), or te(v) is specified in clause 9.1. + 2. The parsing process for the syntax element coded\_block\_pattern is specified in clause F.9.1. + 3. The parsing process for syntax elements of the residual\_block\_cavlc() syntax structure is specified in clause F.9.2. +- Otherwise (entropy\_coding\_mode\_flag is equal to 1), the value of the syntax element is derived as follows: + - If the syntax element is equal to base\_mode\_flag, motion\_prediction\_flag\_l0, motion\_prediction\_flag\_l1, or residual\_prediction\_flag, the following applies: + 1. The binarization process as specified in clause F.9.3.2 is invoked. + 2. The decoding process flow as specified in clause F.9.3.3 is invoked. + - Otherwise (the syntax element is not equal to base\_mode\_flag, motion\_prediction\_flag\_l0, motion\_prediction\_flag\_l1, or residual\_prediction\_flag), the following applies: + 1. The binarization process as specified in clause 9.3.2 is invoked, where a slice\_type equal to EI is interpreted as I, a slice\_type equal to EP is interpreted as P, and a slice\_type equal to EB is interpreted as B. + 2. The decoding process flow as specified in clause 9.3.3 is invoked. +NOTE – For macroblocks with base\_mode\_flag equal to 1, mb\_type is inferred to be equal to Mb\_Inferred and the specifications in clause F.7.4.6 apply. + 3. When the syntax element is equal to mb\_type and the decoded value of mb\_type is equal to I\_PCM, the arithmetic decoding engine is initialized after decoding of any pcm\_alignment\_zero\_bit and all pcm\_sample\_luma and pcm\_sample\_chroma data as specified in clause 9.3.1.2. + +### F.9.1 Alternative parsing process for coded block pattern + +This process is invoked for the parsing syntax elements with descriptor equal to me(v) when entropy\_coding\_mode\_flag is equal to 0. + +Inputs to this process are bits from the RBSP. + +Outputs of this process is a value of the syntax element coded\_block\_pattern. + +The parsing process for the syntax elements begins with reading the bits starting at the current location in the bitstream up to and including the first non-zero bit. By counting the number of leading bits that are equal to 0 and assigning this value to the variable leadingZeroBits, the variable codeNum is then derived as + +$$\text{codeNum} = 2^{\text{leadingZeroBits}} - 1 + \text{read\_bits}(\text{leadingZeroBits})$$ + +where the value returned from `read_bits( leadingZeroBits )` is interpreted as a binary representation of an unsigned integer with most significant bit written first. + +When `ref_layer_dq_id` is greater than or equal to 0 and `( scan_idx_end - scan_idx_start )` is less than 15, `codeNum` is set equal to `(codeNum - 1)`. + +Depending on `codeNum`, the following applies: + +- If `codeNum` is equal to `-1`, the following ordered steps are specified: + 1. The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to `mbAddrA` and `mbAddrB`. + 2. When `mbAddrN` is available, the variable `codedBlockPatternN` (with `N` being either `A` or `B`) is derived as follows: + - If `mb_type` for the macroblock `mbAddrN` is equal to `P_Skip`, `B_Skip`, or `I_PCM`, `codedBlockPatternN` is set equal to 0. + - Otherwise (`mb_type` for the macroblock `mbAddrN` is not equal to `P_Skip`, `B_Skip`, or `I_PCM`), `codedBlockPatternN` is set equal to `(16 * cbpChromaN + cbpLumaN)` with `cbpChromaN` and `cbpLumaN` representing the values of `CodedBlockPatternLuma` and `CodedBlockPatternChroma` for the macroblock `mbAddrN`. + 3. Depending on `mbAddrA` and `mbAddrB`, the following applies: + - If `mbAddrA` is available, `coded_block_pattern` is set equal to `codedBlockPatternA`. + - Otherwise, if `mbAddrB` is available, `coded_block_pattern` is set equal to `codedBlockPatternB`. + - Otherwise (`mbAddrA` and `mbAddrB` are not available), `coded_block_pattern` is set equal to 0. +- Otherwise (`codeNum` is greater than or equal to 0), the mapping process for coded block pattern as specified in clause 9.1.2 is invoked with `codeNum` as input and the output is assigned to the syntax element `coded_block_pattern`. + +#### F.9.2 Alternative CAVLC parsing process for transform coefficient levels + +This process is invoked for the parsing syntax elements with descriptor equal to `ce(v)` when `entropy_coding_mode_flag` is equal to 0. + +Inputs to this process are a request for a value of a syntax element, bits from slice data, a maximum number of non-zero transform coefficient levels `maxNumCoeff`, the luma block index `luma4x4BlkIdx` or the chroma block index `chroma4x4BlkIdx`, `cb4x4BlkIdx` or `cr4x4BlkIdx` of the current block of transform coefficient levels. + +Output of this process is the list `coeffLevel` containing transform coefficient levels of the luma block with block index `luma4x4BlkIdx` or the chroma block with block index `chroma4x4BlkIdx`, `cb4x4BlkIdx` or `cr4x4BlkIdx`. + +The process is specified in the following ordered steps: + +1. All transform coefficient levels, with indices from 0 to `maxNumCoeff - 1`, in the list `coeffLevel` are set equal to 0. +2. The total number of non-zero transform coefficient levels `TotalCoeff( coeff_token )` and the number of trailing one transform coefficient levels `TrailingOnes( coeff_token )` are derived by parsing `coeff_token` as specified by the following ordered steps: + - a. The parsing process of `coeff_token` as specified in clause 9.2.1 is invoked and the outputs are `TotalCoeff( coeff_token )`, `TrailingOnes( coeff_token )`, and `nC`. + + +NOTE – For macroblocks with `base_mode_flag` equal to 1, `mb_type` is inferred to be equal to `Mb_Inferred` and the specifications in clause F.7.4.6 apply. + - b. When the CAVLC parsing process is invoked for `LumaLevel4x4`, `LumaLevel8x8`, `Intra16x16ACLevel`, `ChromaACLevel`, `CbIntra16x16ACLevel`, or `CrIntra16x16ACLevel` and `( scan_idx_end - scan_idx_start )` is less than 15, `nC` is modified by setting it equal to `Min( 7, nC )`, and the additional parsing process for total number of non-zero transform coefficient levels and number of trailing ones as specified in clause F.9.2.1 is invoked with `nC`, `totalCoeffStart` set equal to `TotalCoeff( coeff_token )`, and `trailingOnesStart` set equal + +to $\text{TrailingOnes}(\text{coeff\_token})$ as the inputs and the outputs are assigned to $\text{TotalCoeff}(\text{coeff\_token})$ and $\text{TrailingOnes}(\text{coeff\_token})$ . + +3. When $\text{TotalCoeff}(\text{coeff\_token})$ is greater than 0, the following ordered steps are specified: + - a. The non-zero transform coefficient levels are derived by parsing $\text{trailing\_ones\_sign\_flag}$ , $\text{level\_prefix}$ , and $\text{level\_suffix}$ as specified in clause 9.2.2. + - b. The runs of zero transform coefficient levels before each non-zero transform coefficient level are derived by parsing $\text{total\_zeros}$ and $\text{run\_before}$ as specified in clause F.9.2.2. + - c. The level and run information are combined into the list $\text{coeffLevel}$ as specified in clause 9.2.4. + +### F.9.2.1 Additional parsing process for total number of non-zero transform coefficient levels and number of trailing ones + +Inputs to this process are variables $\text{nC}$ , $\text{totalCoeffStart}$ , and $\text{trailingOnesStart}$ . + +Outputs of this process are variables $\text{totalCoeff}$ and $\text{trailingOnes}$ . + +Let $\text{invTotalCoeff}(\text{coeffTokenIdx})$ and $\text{invTrailingOnes}(\text{coeffTokenIdx})$ be functions that map the variable $\text{coeffTokenIdx}$ to the variables $\text{nX}$ and $\text{nY}$ , respectively, as specified in Table F-10 for each value of the variable $\text{nC}$ . + +A variable $\text{dX}$ is set equal to $(\text{scan\_idx\_end} - \text{scan\_idx\_start} + 2)$ . A variable $\text{dY}$ is set equal to $\text{Min}(4, \text{scan\_idx\_end} - \text{scan\_idx\_start} + 2)$ . A variable $\text{targetCoeffTokenIdx}$ is derived as specified by Table F-10 given the variables $\text{nC}$ , $\text{nX} = \text{totalCoeffStart}$ , and $\text{nY} = \text{trailingOnesStart}$ . + +The bitstream shall not contain data that result in a value of $\text{targetCoeffTokenIdx}$ that exceeds the range of values from 0 to $(\text{dX} * \text{dY} - \text{Min}(7, (1 \ll (\text{dY} - 1))))$ , inclusive. + +A variable $\text{coeffTokenIdx}$ is derived as specified by the following pseudo code: + +``` +for( coeffTokenIdx = 0, i = 0; i <= targetCoeffTokenIdx; coeffTokenIdx++ ) + if( invTotalCoeff( coeffTokenIdx ) < dX && invTrailingOnes( coeffTokenIdx ) < dY ) + i++ +``` + +(F-359) + +The variable $\text{totalCoeff}$ is set equal to $\text{invTotalCoeff}(\text{coeffTokenIdx} - 1)$ and the variable $\text{trailingOnes}$ is set equal to $\text{invTrailingOnes}(\text{coeffTokenIdx} - 1)$ . + +When the CAVLC parsing process is invoked for $\text{Intra16x16ACLevel}$ , $\text{CbIntra16x16ACLevel}$ , $\text{CrIntra16x16ACLevel}$ , or $\text{ChromaACLevel}$ , it is a requirement of bitstream conformance that the bitstream shall not contain data that result in $\text{totalCoeff}$ being greater than $(\text{scan\_idx\_end} - \text{Max}(1, \text{scan\_idx\_start}) + 1)$ . + +**Table F-10 – Mapping of ( nX, nY ) to coeffTokenIdx and vice versa** + +| nY | nX | $0 \leq nC < 2$ | $2 \leq nC < 4$ | $4 \leq nC < 8$ | +|----|----|-----------------|-----------------|-----------------| +| 0 | 0 | 0 | 0 | 0 | +| 0 | 1 | 4 | 7 | 16 | +| 1 | 1 | 1 | 1 | 1 | +| 0 | 2 | 9 | 11 | 20 | +| 1 | 2 | 5 | 5 | 8 | +| 2 | 2 | 2 | 2 | 2 | +| 0 | 3 | 13 | 15 | 23 | +| 1 | 3 | 10 | 8 | 11 | +| 2 | 3 | 7 | 9 | 9 | +| 3 | 3 | 3 | 3 | 3 | +| 0 | 4 | 17 | 19 | 24 | +| 1 | 4 | 14 | 12 | 13 | +| 2 | 4 | 11 | 13 | 12 | +| 3 | 4 | 6 | 4 | 4 | + +**Table F-10 – Mapping of ( nX, nY ) to coeffTokenIdx and vice versa** + +| nY | nX | 0 <= nC < 2 | 2 <= nC < 4 | 4 <= nC < 8 | +|----|----|-------------|-------------|-------------| +| 0 | 5 | 21 | 22 | 28 | +| 1 | 5 | 18 | 16 | 15 | +| 2 | 5 | 15 | 17 | 14 | +| 3 | 5 | 8 | 6 | 5 | +| 0 | 6 | 25 | 23 | 30 | +| 1 | 6 | 22 | 20 | 17 | +| 2 | 6 | 19 | 21 | 18 | +| 3 | 6 | 12 | 10 | 6 | +| 0 | 7 | 29 | 27 | 31 | +| 1 | 7 | 26 | 24 | 21 | +| 2 | 7 | 23 | 25 | 22 | +| 3 | 7 | 16 | 14 | 7 | +| 0 | 8 | 32 | 31 | 32 | +| 1 | 8 | 30 | 28 | 25 | +| 2 | 8 | 27 | 29 | 26 | +| 3 | 8 | 20 | 18 | 10 | +| 0 | 9 | 33 | 35 | 36 | +| 1 | 9 | 34 | 32 | 33 | +| 2 | 9 | 31 | 33 | 29 | +| 3 | 9 | 24 | 26 | 19 | +| 0 | 10 | 37 | 39 | 40 | +| 1 | 10 | 38 | 36 | 37 | +| 2 | 10 | 35 | 37 | 34 | +| 3 | 10 | 28 | 30 | 27 | +| 0 | 11 | 41 | 42 | 44 | +| 1 | 11 | 42 | 40 | 41 | +| 2 | 11 | 39 | 41 | 38 | +| 3 | 11 | 36 | 34 | 35 | +| 0 | 12 | 45 | 43 | 47 | +| 1 | 12 | 46 | 44 | 45 | +| 2 | 12 | 43 | 45 | 42 | +| 3 | 12 | 40 | 38 | 39 | +| 0 | 13 | 50 | 47 | 49 | +| 1 | 13 | 49 | 48 | 48 | +| 2 | 13 | 47 | 49 | 46 | +| 3 | 13 | 44 | 46 | 43 | +| 0 | 14 | 54 | 51 | 53 | + +**Table F-10 – Mapping of ( nX, nY ) to coeffTokenIdx and vice versa** + +| nY | nX | 0 <= nC < 2 | 2 <= nC < 4 | 4 <= nC < 8 | +|----|----|-------------|-------------|-------------| +| 1 | 14 | 51 | 54 | 50 | +| 2 | 14 | 52 | 52 | 51 | +| 3 | 14 | 48 | 50 | 52 | +| 0 | 15 | 58 | 55 | 57 | +| 1 | 15 | 55 | 56 | 54 | +| 2 | 15 | 56 | 57 | 55 | +| 3 | 15 | 53 | 53 | 56 | +| 0 | 16 | 61 | 59 | 61 | +| 1 | 16 | 59 | 60 | 58 | +| 2 | 16 | 60 | 61 | 59 | +| 3 | 16 | 57 | 58 | 60 | + +### F.9.2.2 Alternative parsing process for run information + +Inputs to this process are bits from slice data and the number of non-zero transform coefficient levels TotalCoeff( coeff\_token ). + +Output of this process is a list of runs of zero transform coefficient levels preceding non-zero transform coefficient levels called runVal. + +The variable maxCoeff is derived as follows: + +- If the CAVLC parsing process is invoked for Intra16x16DCLevel, CbIntra16x16DCLevel, or CrIntra16x16DCLevel, maxCoeff is set equal to 16. +- Otherwise, if the CAVLC parsing process is invoked for ChromaDCLevel, maxCoeff is set equal to $4 * chroma\_format\_idc$ . +- Otherwise, if the CAVLC parsing process is invoked for LumaLevel4x4 or LumaLevel8x8, maxCoeff is set equal to $(scan\_idx\_end - scan\_idx\_start + 1)$ . +- Otherwise (the CAVLC parsing process is invoked for Intra16x16ACLevel, CbIntra16x16ACLevel, CrIntra16x16ACLevel, or ChromaACLevel), maxCoeff is set equal to $(scan\_idx\_end - \text{Max}( 1, scan\_idx\_start ) + 1)$ . + +Initially, an index i is set equal to 0. + +The variable zerosLeft is derived as follows: + +- If the number of non-zero transform coefficient levels TotalCoeff( coeff\_token ) is equal to the maximum number of non-zero transform coefficient levels maxCoeff, a variable zerosLeft is set equal to 0. +- Otherwise (the number of non-zero transform coefficient levels TotalCoeff( coeff\_token ) is less than the maximum number of non-zero transform coefficient levels maxCoeff), total\_zeros is decoded and zerosLeft is set equal to its value. + +The VLC used to decode total\_zeros is derived as follows: + +- If maxCoeff is less than or equal to 4, one of the VLCs specified in Table 9-9(a) is used with tzVlcIndex being derived by + +$$tzVlcIndex = \text{TotalCoeff}( \text{coeff\_token} ) + 4 - \text{maxCoeff} \quad (\text{F-360})$$ + +- Otherwise, if maxCoeff is greater than 4 and less than or equal to 8, one of the VLCs specified in Table 9-9(b) is used with tzVlcIndex being derived by + +$$tzVlcIndex = \text{TotalCoeff}( \text{coeff\_token} ) + 8 - \text{maxCoeff} \quad (\text{F-361})$$ + +- Otherwise, if maxCoeff is greater than 8 and less than 15, VLCs from Tables 9-7 and 9-8 are used with tzVlcIndex being derived by + +$$\text{tzVlcIndex} = \text{TotalCoeff}(\text{coeff\_token}) + 16 - \text{maxCoeff} \quad (\text{F-362})$$ + +- Otherwise (maxCoeff is greater than or equal to 15), VLCs from Tables 9-7 and 9-8 are used with tzVlcIndex equal to $\text{TotalCoeff}(\text{coeff\_token})$ . + +The following procedure is then applied iteratively ( $\text{TotalCoeff}(\text{coeff\_token}) - 1$ ) times: + +1. The variable $\text{runVal}[i]$ is derived as follows: + - If $\text{zerosLeft}$ is greater than zero, a value $\text{run\_before}$ is decoded based on Table 9-10 and $\text{zerosLeft}$ . $\text{runVal}[i]$ is set equal to $\text{run\_before}$ . + - Otherwise ( $\text{zerosLeft}$ is equal to 0), $\text{runVal}[i]$ is set equal to 0. +2. The value of $\text{runVal}[i]$ is subtracted from $\text{zerosLeft}$ and the result assigned to $\text{zerosLeft}$ . The result of the subtraction shall be greater than or equal to 0. +3. The index $i$ is incremented by 1. + +Finally the value of $\text{zerosLeft}$ is assigned to $\text{runVal}[i]$ . + +### F.9.3 Alternative CABAC parsing process for slice data in scalable extension + +Clause F.9.3.1 specifies the initialization process for the alternative CABAC parsing process for slice data in scalable extension. + +Clause F.9.3.2 specifies the binarization process for the alternative CABAC parsing process for slice data in scalable extension. + +Clause F.9.3.3 specifies the decoding process flow for the alternative CABAC parsing process for slice data in scalable extension. + +#### F.9.3.1 Initialization process + +Outputs of this process are the initialized CABAC context variables indexed by $\text{ctxIdx}$ . + +Tables F-12 and F-13 contain the values of the variables $n$ and $m$ used in the initialization of context variables that are assigned to syntax element $\text{base\_mode\_flag}$ , $\text{motion\_prediction\_flag\_l0}$ , $\text{motion\_prediction\_flag\_l1}$ , and $\text{residual\_prediction\_flag}$ in clause F.7.3.4.1 and F.7.3.6. For all other syntax elements in clauses F.7.3.4.1 and F.7.3.6 the initialization process of context variables as specified in clause 9.3.1 applies. + +For each context variable, the two variables $\text{pStateIdx}$ and $\text{valMPS}$ are initialized. The two values assigned to $\text{pStateIdx}$ and $\text{valMPS}$ for the initialization are derived from $\text{SliceQP}_Y$ , which is derived in Equation 7-32. Given the two table entries ( $m, n$ ), the initialization is specified by the following pseudo-code process: + +``` + +preCtxState = Clip3( 1, 126, ( ( m * Clip3( 0, 51, SliceQPY ) ) >> 4 ) + n ) +if( preCtxState <= 63 ) { + pStateIdx = 63 - preCtxState + valMPS = 0 +} else { + pStateIdx = preCtxState - 64 + valMPS = 1 +} + +``` + +(F-363) + +In Table F-11, the $\text{ctxIdx}$ for which initialization is needed for each of the slice types EI, EP, and EB are listed. Also listed is the table number that includes the values of $m$ and $n$ needed for the initialization. For EP and EB slices, the initialization depends also on the value of the $\text{cabac\_init\_idc}$ syntax element. Note that the syntax element names do not affect the initialization process. + +**Table F-11 – Association of ctxIdx and syntax elements for each slice type in the initialization process** + +| | Syntax element | Table | Slice type | | | +|----------------------------------------------------------------------------|---------------------------|------------|------------|------------|------------| +| | | | EI | EP | EB | +| macroblock_layer_in_scalable_extension() | base_mode_flag | Table F-12 | 1024..1026 | 1024..1026 | 1024..1026 | +| mb_pred_in_scalable_extension() and
sub_mb_pred_in_scalable_extension() | motion_prediction_flag_10 | Table F-13 | | 1027 | 1027 | +| | motion_prediction_flag_11 | Table F-13 | | 1028 | 1028 | +| macroblock_layer_in_scalable_extension() | residual_prediction_flag | Table F-13 | | 1029..1030 | 1029..1030 | + +**Table F-12 – Values of variables m and n for ctxIdx from 1024 to 1026** + +| ctxIdx | EI slices | | Value of cabac_init_idc (EP, EB slices) | | | | | | +|-------------|-----------|-----|-----------------------------------------|----|---|----|---|----| +| | | | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | m | n | +| 1024 | -14 | 138 | 0 | 75 | 0 | 75 | 0 | 75 | +| 1025 | -22 | 140 | 2 | 65 | 2 | 65 | 2 | 65 | +| 1026 | -11 | 99 | 2 | 59 | 2 | 59 | 2 | 59 | + +**Table F-13 – Values of variables m and n for ctxIdx from 1027 to 1030** + +| ctxIdx | Value of cabac_init_idc | | | | | | +|-------------|-------------------------|-----|-----|-----|-----|-----| +| | 0 | | 1 | | 2 | | +| | m | n | m | n | m | n | +| 1027 | -6 | 67 | -6 | 67 | -6 | 67 | +| 1028 | -6 | 67 | -6 | 67 | -6 | 67 | +| 1029 | -23 | 104 | -23 | 104 | -23 | 104 | +| 1030 | -35 | 106 | -35 | 106 | -35 | 106 | + +### F.9.3.2 Binarization process + +Input to this process is a request for a syntax element. + +Output of this process is the binarization of the syntax element, maxBinIdxCtx, ctxIdxOffset, and bypassFlag. + +Associated with each binarization or binarization part of a syntax element is a specific value of the context index offset (ctxIdxOffset) variable and a specific value of the maxBinIdxCtx variable as given in Table F-14. + +The variable bypassFlag is set equal to 0. + +The possible values of the context index ctxIdx are in the range 1024 to 1030, inclusive. The value assigned to ctxIdxOffset specifies the lower value of the range of ctxIdx assigned to the corresponding binarization or binarization part of a syntax element. + +**Table F-14 – Syntax elements and associated types of binarization, maxBinIdxCtx, and ctxIdxOffset** + +| Syntax element | Type of binarization | maxBinIdxCtx | ctxIdxOffset | +|---------------------------|----------------------|--------------|--------------| +| base_mode_flag | FL, cMax=1 | 0 | 1024 | +| motion_prediction_flag_l0 | FL, cMax=1 | 0 | 1027 | +| motion_prediction_flag_l1 | FL, cMax=1 | 0 | 1028 | +| residual_prediction_flag | FL, cMax=1 | 0 | 1029 | + +**F.9.3.3 Decoding process flow** + +Input to this process is a binarization of the requested syntax element, maxBinIdxCtx, bypassFlag and ctxIdxOffset as specified in clause F.9.3.2. + +Output of this process is the value of the syntax element. + +This process specifies how each bit of a bit string is parsed for each syntax element. + +After parsing each bit, the resulting bit string is compared to all bin strings of the binarization of the syntax element and the following applies: + +- If the bit string is equal to one of the bin strings, the corresponding value of the syntax element is the output. +- Otherwise (the bit string is not equal to one of the bin strings), the next bit is parsed. + +While parsing each bin, the variable binIdx is incremented by 1 starting with binIdx being set equal to 0 for the first bin. + +The parsing of each bin is specified by the following two ordered steps: + +1. Given binIdx, maxBinIdxCtx and ctxIdxOffset, ctxIdx is derived as specified in clause F.9.3.3.1. +2. Given ctxIdx, the value of the bin from the bitstream as specified in clause 9.3.3.2 is decoded. + +**F.9.3.3.1 Derivation process for ctxIdx** + +Inputs to this process are binIdx, maxBinIdxCtx and ctxIdxOffset. + +Output of this process is ctxIdx. + +Table F-15 shows the assignment of ctxIdx increments (ctxIdxInc) to binIdx for all ctxIdxOffset values for the syntax elements base\_mode\_flag, motion\_prediction\_flag\_l0, motion\_prediction\_flag\_l1, and residual\_prediction\_flag. + +The ctxIdx to be used with a specific binIdx is the sum of ctxIdxOffset and ctxIdxInc, which is found in Table F-15. When more than one value is listed in Table F-15 or 9-39 for a binIdx, the assignment process for ctxIdxInc for that binIdx is further specified in the clauses given in parenthesis of the corresponding table entry. + +All entries in Table F-15 labelled with "na" correspond to values of binIdx that do not occur for the corresponding ctxIdxOffset. + +**Table F-15 – Assignment of ctxIdxInc to binIdx for the ctxIdxOffset values related to the syntax elements base\_mode\_flag and residual\_prediction\_flag** + +| ctxIdxOffset | binIdx | | | | | | | +|--------------|-------------------------------|----|----|----|----|----|------| +| | 0 | 1 | 2 | 3 | 4 | 5 | >= 6 | +| 1024 | 0,1,2
(clause F.9.3.3.2.1) | na | na | na | na | na | na | +| 1027 | 0 | na | na | na | na | na | na | +| 1028 | 0 | na | na | na | na | na | na | +| 1029 | 0,1
(clause F.9.3.3.2.2) | na | na | na | na | na | na | + +**F.9.3.3.2 Assignment process of ctxIdxInc using neighbouring syntax elements** + +Clause F.9.3.3.2.1 specifies the derivation process of ctxIdxInc for the syntax element base\_mode\_flag. + +Clause F.9.3.3.2.2 specifies the derivation process of ctxIdxInc for the syntax element residual\_prediction\_flag. + +#### F.9.3.3.2.1 Derivation process of ctxIdxInc for the syntax element base\_mode\_flag + +Output of this process is ctxIdxInc. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If mbAddrN is available and base\_mode\_flag for the macroblock mbAddrN is equal to 1, condTermFlagN is set equal to 0. +- Otherwise (mbAddrN is not available or base\_mode\_flag for the macroblock mbAddrN is equal to 0), condTermFlagN is set equal to 1. + +The variable ctxIdxInc is derived by + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (\text{F-364})$$ + +#### F.9.3.3.2.2 Derivation process of ctxIdxInc for the syntax element residual\_prediction\_flag + +Output of this process is ctxIdxInc. + +Depending on base\_mode\_flag, the following applies: + +- If base\_mode\_flag is equal to 1, ctxIdxInc is set equal to 0. +- Otherwise (base\_mode\_flag is equal to 0), ctxIdxInc is set equal to 1. + +### F.10 Profiles and levels + +The specifications in Annex A apply. Additional profiles and specific values of profile\_idc are specified in the following. + +The profiles that are specified in clause F.10.1 are also referred to as the profiles specified in Annex F. + +#### F.10.1 Profiles + +All constraints for picture parameter sets that are specified in clauses F.10.1.1 to F.10.1.3 are constraints for picture parameter sets that become the active picture parameter set or an active layer picture parameter set inside the bitstream. All constraints for SVC sequence parameter sets that are specified in clauses F.10.1.1 to F.10.1.3 are constraints for SVC sequence parameter sets that become the active SVC sequence parameter set or an active layer SVC sequence parameter set inside the bitstream. All constraints for sequence parameter sets of the base layer bitstream that are specified in clauses F.10.1.1 to F.10.1.3 are constraints for sequence parameter sets that are activated in the base layer bitstream. + +##### F.10.1.1 Scalable Baseline profile + +Bitstreams conforming to the Scalable Baseline profile shall obey the following constraints: + +- a) The base layer bitstream as specified in clause F.8.8.2 shall obey the following constraints: + - i) All constraints of the Baseline and Constrained Baseline profiles specified in clauses A.2.1 and A.2.1.1 shall be obeyed. + - ii) Sequence parameter sets should have profile\_idc equal to 66. Sequence parameter sets may have profile\_idc equal to 77 or 88. Sequence parameter sets shall not have profile\_idc equal to a value other than 66, 77, or 88. + - iii) Sequence parameter sets shall have constraint\_set0\_flag, constraint\_set1\_flag, and constraint\_set2\_flag equal to 1. + +NOTE 1 – The above constraint implies that picture parameter sets must have num\_slice\_groups\_minus1 equal to 0 and redundant\_pic\_cnt\_present\_flag equal to 0 and that arbitrary slice order is not allowed. + +NOTE 2 – In addition to the base layer constraints specified above in items i) through iii), the value of the syntax element constrained\_intra\_pred\_flag for picture parameter sets of the base layer stream is constrained as specified below in item 1). + +- b) A list of integer values specifying layer representation identifiers is derived by invoking the process specified in clause F.8.1.1 with the output being the list dqIdList. The SVC sequence parameter sets that are referred to by coded slice NAL units with DQId greater than 0 and DQId in the list dqIdList shall have profile\_idc equal to 83 or (profile\_idc equal to 86 and constraint\_set0\_flag equal to 1). +- c) Only I, P, EI, EP, and EB slices shall be present. + +- d) SVC sequence parameter sets shall have chroma\_format\_idc equal to 1. +- e) SVC sequence parameter sets shall have bit\_depth\_luma\_minus8 equal to 0. +- f) SVC sequence parameter sets shall have bit\_depth\_chroma\_minus8 equal to 0. +- g) SVC sequence parameter sets shall have separate\_colour\_plane\_flag equal to 0. +- h) SVC sequence parameter sets shall have qpprime\_y\_zero\_transform\_bypass\_flag equal to 0. +- i) SVC sequence parameter sets shall have frame\_mbs\_only\_flag equal to 1. +- j) Picture parameter sets shall have num\_slice\_groups\_minus1 in the range of 0 to 7, inclusive. +- k) The value of slice\_group\_map\_type, when present in picture parameter sets, shall be equal to 2. +- l) A list of integer values specifying layer representation identifiers is derived by invoking the process specified in clause F.8.1.1 with the output being the list dqIdList. The variable numDQEntries is set equal to the number of elements in the list dqIdList. When numDQEntries is greater than 1, for any element dqIdList[ i ] with i = 1..(numDQEntries - 1), when MaxTCoeffLevelPredFlag is equal to 0 for any layer representation with DQId in the set specified by dqIdList[ k ] with k = 0..i, the picture parameter set that is referenced by the coded slice NAL units of the layer representation with DQId equal to dqIdList[ i ] shall have constrained\_intra\_pred\_flag equal to 1. +- m) For each present layer representation with dependency\_id greater than 0, quality\_id equal to 0, and MinNoInterLayerPredFlag equal to 0, one of the following constraints shall be obeyed. + - ScaledRefLayerPicWidthInSamplesL is equal to RefLayerPicWidthInSamplesL and ScaledRefLayerPicHeightInSamplesL is equal to RefLayerPicHeightInSamplesL + - ScaledRefLayerPicWidthInSamplesL is equal to (1.5 \* RefLayerPicWidthInSamplesL) and ScaledRefLayerPicHeightInSamplesL is equal to (1.5 \* RefLayerPicHeightInSamplesL) + - ScaledRefLayerPicWidthInSamplesL is equal to (2 \* RefLayerPicWidthInSamplesL) and ScaledRefLayerPicHeightInSamplesL is equal to (2 \* RefLayerPicHeightInSamplesL) +- n) For each present layer representation with dependency\_id greater than 0, quality\_id equal to 0, and MinNoInterLayerPredFlag equal to 0, all of the following constraints shall be obeyed. + - (ScaledRefLayerLeftOffset % 16) is equal to 0 + - (ScaledRefLayerTopOffset % 16) is equal to 0 +- o) The level constraints specified in clause F.10.2 shall be fulfilled. + +Conformance of a bitstream to the Scalable Baseline profile is indicated by profile\_idc equal to 83. + +Decoders conforming to the Scalable Baseline profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- a) All active SVC sequence parameter sets have one of the following conditions fulfilled: + - profile\_idc is equal to 83, + - profile\_idc is equal to 86 and constraint\_set0\_flag is equal to 1, + - profile\_idc is equal to 66 and constraint\_set1\_flag is equal to 1, + - profile\_idc is equal to 77 and constraint\_set0\_flag is equal to 1, + - profile\_idc is equal to 88, constraint\_set0\_flag is equal to 1, and constraint\_set1\_flag is equal to 1. +- b) level\_idc or (level\_idc and constraint\_set3\_flag) for all active SVC sequence parameter sets represent a level less than or equal to the specified level. + +#### F.10.1.1.1 Scalable Constrained Baseline profile + +Bitstreams conforming to the Scalable Constrained Baseline profile shall obey the following constraints: + +- a) The base layer bitstream as specified in clause F.8.8.2 shall obey the following constraints: + - i) All constraints of the Baseline and Constrained Baseline profiles specified in clauses A.2.1 and A.2.1.1 shall be obeyed. + +- ii) Sequence parameter sets should have profile\_idc equal to 66. Sequence parameter sets may have profile\_idc equal to 77 or 88. Sequence parameter sets shall not have profile\_idc equal to a value other than 66, 77, or 88. +- iii) Sequence parameter sets shall have constraint\_set0\_flag, constraint\_set1\_flag, and constraint\_set2\_flag equal to 1. + +NOTE 1 – The above constraint implies that picture parameter sets must have num\_slice\_groups\_minus1 equal to 0 and redundant\_pic\_cnt\_present\_flag equal to 0 and that arbitrary slice order is not allowed. + +NOTE 2 – In addition to the base layer constraints specified above in items i) through iii), the value of the syntax element constrained\_intra\_pred\_flag for picture parameter sets of the base layer stream is constrained as specified below in item m). + +- b) A list of integer values specifying layer representation identifiers is derived by invoking the process specified in clause F.8.1.1 with the output being the list dqIdList. The SVC sequence parameter sets that are referred to by coded slice NAL units with DQId greater than 0 and DQId in the list dqIdList shall have profile\_idc equal to 83 and both constraint\_set1\_flag and constraint\_set5\_flag equal to 1 or (profile\_idc equal to 86 and both constraint\_set0\_flag and constraint\_set5\_flag equal to 1). +- c) Only I, P, EI, and EP slices shall be present. +- d) SVC sequence parameter sets shall have chroma\_format\_idc equal to 1. +- e) SVC sequence parameter sets shall have bit\_depth\_luma\_minus8 equal to 0. +- f) SVC sequence parameter sets shall have bit\_depth\_chroma\_minus8 equal to 0. +- g) SVC sequence parameter sets shall have separate\_colour\_plane\_flag equal to 0. +- h) SVC sequence parameter sets shall have qpprime\_y\_zero\_transform\_bypass\_flag equal to 0. +- i) SVC sequence parameter sets shall have frame\_mbs\_only\_flag equal to 1. +- j) Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0. +- k) Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0. +- l) Arbitrary slice order is not allowed. +- m) A list of integer values specifying layer representation identifiers is derived by invoking the process specified in clause F.8.1.1 with the output being the list dqIdList. The variable numDQEntries is set equal to the number of elements in the list dqIdList. When numDQEntries is greater than 1, for any element dqIdList[ i ] with i = 1..(numDQEntries - 1), when MaxTCoeffLevelPredFlag is equal to 0 for any layer representation with DQId in the set specified by dqIdList[ k ] with k = 0..i, the picture parameter set that is referenced by the coded slice NAL units of the layer representation with DQId equal to dqIdList[ i ] shall have constrained\_intra\_pred\_flag equal to 1. +- n) For each present layer representation with dependency\_id greater than 0, quality\_id equal to 0, and MinNoInterLayerPredFlag equal to 0, one of the following constraints shall be obeyed. + - ScaledRefLayerPicWidthInSamplesL is equal to RefLayerPicWidthInSamplesL and ScaledRefLayerPicHeightInSamplesL is equal to RefLayerPicHeightInSamplesL + - ScaledRefLayerPicWidthInSamplesL is equal to (1.5 \* RefLayerPicWidthInSamplesL) and ScaledRefLayerPicHeightInSamplesL is equal to (1.5 \* RefLayerPicHeightInSamplesL) + - ScaledRefLayerPicWidthInSamplesL is equal to (2 \* RefLayerPicWidthInSamplesL) and ScaledRefLayerPicHeightInSamplesL is equal to (2 \* RefLayerPicHeightInSamplesL) +- o) For each present layer representation with dependency\_id greater than 0, quality\_id equal to 0, and MinNoInterLayerPredFlag equal to 0, all of the following constraints shall be obeyed. + - (ScaledRefLayerLeftOffset % 16) is equal to 0 + - (ScaledRefLayerTopOffset % 16) is equal to 0 +- p) The level constraints specified in clause F.10.2 shall be fulfilled. + +Conformance of a bitstream to the Scalable Constrained Baseline profile is indicated by constraint\_set5\_flag being equal to 1 with profile\_idc equal to 83. + +Decoders conforming to the Scalable Constrained Baseline profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- a) All active SVC sequence parameter sets have one of the following conditions fulfilled: + - profile\_idc is equal to 83 and constraint\_set5\_flag is equal to 1, + - profile\_idc is equal to 86, constraint\_set0\_flag is equal to 1, and constraint\_set5\_flag equal to 1, + - profile\_idc is equal to 66 and constraint\_set1\_flag is equal to 1, + - profile\_idc is equal to 77 and constraint\_set0\_flag is equal to 1, + - profile\_idc is equal to 88, constraint\_set0\_flag is equal to 1, and constraint\_set1\_flag is equal to 1. +- b) level\_idc or (level\_idc and constraint\_set3\_flag) for all active SVC sequence parameter sets represent a level less than or equal to the specified level. + +#### F.10.1.2 Scalable High profile + +Bitstreams conforming to the Scalable High profile shall obey the following constraints: + +- a) The base layer bitstream as specified in clause F.8.8.2 shall obey the following constraints: + - i) All constraints of the High profile specified in clause A.2.4 shall be obeyed. + - ii) Sequence parameter sets should have profile\_idc equal to 100. Sequence parameter sets may have profile\_idc equal to 66, 77, or 88 and constraint\_set1\_flag equal to 1. Sequence parameter sets shall not have profile\_idc equal to a value other than 66, 77, 88, or 100. + - iii) The syntax element direct\_spatial\_mv\_pred\_flag shall be equal to 1. + +NOTE – In addition to the base layer constraints specified above in items i) through iii), the value of the syntax element constrained\_intra\_pred\_flag for picture parameter sets of the base layer stream is constrained as specified below in item k). + +- b) A list of integer values specifying layer representation identifiers is derived by invoking the process specified in clause F.8.1.1 with the output being the list dqIdList. The SVC sequence parameter sets that are referred to by coded slice NAL units with DQId greater than 0 and DQId in the list dqIdList shall have profile\_idc equal to 86 or (profile\_idc equal to 83 and constraint\_set1\_flag equal to 1). +- c) Only I, P, B, EI, EP, and EB slices shall be present. +- d) SVC sequence parameter sets shall have chroma\_format\_idc equal to 1. +- e) SVC sequence parameter sets shall have bit\_depth\_luma\_minus8 equal to 0. +- f) SVC sequence parameter sets shall have bit\_depth\_chroma\_minus8 equal to 0. +- g) SVC sequence parameter sets shall have separate\_colour\_plane\_flag equal to 0. +- h) SVC sequence parameter sets shall have qpprime\_y\_zero\_transform\_bypass\_flag equal to 0. +- i) Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0. +- j) Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0. +- k) A list of integer values specifying layer representation identifiers is derived by invoking the process specified in clause F.8.1.1 with the output being the list dqIdList. The variable numDQEntries is set equal to the number of elements in the list dqIdList. When numDQEntries is greater than 1, for any element dqIdList[ i ] with i = 1..(numDQEntries – 1), when MaxTCoeffLevelPredFlag is equal to 0 for any layer representation with DQId in the set specified by dqIdList[ k ] with k = 0..i, the picture parameter set that is referenced by the coded slice NAL units of the layer representation with DQId equal to dqIdList[ i ] shall have constrained\_intra\_pred\_flag equal to 1. +- l) Arbitrary slice order is not allowed. +- m) The level constraints specified in clause F.10.2 shall be fulfilled. + +Conformance of a bitstream to the Scalable High profile is indicated by profile\_idc equal to 86. + +Decoders conforming to the Scalable High profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- a) All active SVC sequence parameter sets have one of the following conditions fulfilled: + +- profile\_idc is equal to 86, + - profile\_idc is equal to 83 and constraint\_set1\_flag is equal to 1, + - profile\_idc is equal to 77 or 100, + - profile\_idc is equal to 66 or 88 and constraint\_set1\_flag is equal to 1. +- b) level\_idc or (level\_idc and constraint\_set3\_flag) for all active SVC sequence parameter sets represent a level less than or equal to the specified level. + +#### F.10.1.2.1 Scalable Constrained High profile + +Bitstreams conforming to the Scalable Constrained High profile shall obey the following constraints: + +- a) The base layer bitstream as specified in clause F.8.8.2 shall obey the following constraints: + - i) All constraints of the Constrained High profile specified in clause A.2.4.2 shall be obeyed. + - ii) Sequence parameter sets should have profile\_idc equal to 100. Sequence parameter sets may have profile\_idc equal to 66, 77, or 88 and constraint\_set1\_flag equal to 1. Sequence parameter sets shall not have profile\_idc equal to a value other than 66, 77, 88, or 100. + - iii) The syntax element direct\_spatial\_mv\_pred\_flag shall be equal to 1. + +NOTE – In addition to the base layer constraints specified above in items i) through iii), the value of the syntax element constrained\_intra\_pred\_flag for picture parameter sets of the base layer stream is constrained as specified below in item l). + +- b) A list of integer values specifying layer representation identifiers is derived by invoking the process specified in clause F.8.8.1 with the output being the list dqIdList. The SVC sequence parameter sets that are referred to by coded slice NAL units with DQId greater than 0 and DQId in the list dqIdList shall have profile\_idc equal to 86 and constraint\_set5\_flag equal to 1 or (profile\_idc equal to 83 and both constraint\_set1\_flag and constraint\_set5\_flag equal to 1). +- c) Only I, P, EI, and EP slices shall be present. +- d) SVC sequence parameter sets shall have chroma\_format\_idc equal to 1. +- e) SVC sequence parameter sets shall have bit\_depth\_luma\_minus8 equal to 0. +- f) SVC sequence parameter sets shall have bit\_depth\_chroma\_minus8 equal to 0. +- g) SVC sequence parameter sets shall have separate\_colour\_plane\_flag equal to 0. +- h) SVC sequence parameter sets shall have qpprime\_y\_zero\_transform\_bypass\_flag equal to 0. +- i) SVC sequence parameter sets shall have frame\_mbs\_only\_flag equal to 1. +- j) Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0. +- k) Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0. +- l) A list of integer values specifying layer representation identifiers is derived by invoking the process specified in clause F.8.8.1 with the output being the list dqIdList. The variable numDQEntries is set equal to the number of elements in the list dqIdList. When numDQEntries is greater than 1, for any element dqIdList[ i ] with i = 1..(numDQEntries – 1), when MaxTCoeffLevelPredFlag is equal to 0 for any layer representation with DQId in the set specified by dqIdList[ k ] with k = 0..i, the picture parameter set that is referenced by the coded slice NAL units of the layer representation with DQId equal to dqIdList[ i ] shall have constrained\_intra\_pred\_flag equal to 1. +- m) Arbitrary slice order is not allowed. +- n) For each present layer representation with dependency\_id greater than 0, quality\_id equal to 0, and MinNoInterLayerPredFlag equal to 0, one of the following constraints shall be obeyed. + - ScaledRefLayerPicWidthInSamplesL is equal to RefLayerPicWidthInSamplesL and ScaledRefLayerPicHeightInSamplesL is equal to RefLayerPicHeightInSamplesL + - ScaledRefLayerPicWidthInSamplesL is equal to (1.5 \* RefLayerPicWidthInSamplesL) and ScaledRefLayerPicHeightInSamplesL is equal to (1.5 \* RefLayerPicHeightInSamplesL) + - ScaledRefLayerPicWidthInSamplesL is equal to (2 \* RefLayerPicWidthInSamplesL) and ScaledRefLayerPicHeightInSamplesL is equal to (2 \* RefLayerPicHeightInSamplesL) + +- o) For each present layer representation with dependency\_id greater than 0, quality\_id equal to 0, and MinNoInterLayerPredFlag equal to 0, all of the following constraints shall be obeyed. + - (ScaledRefLayerLeftOffset % 16) is equal to 0 + - (ScaledRefLayerTopOffset % 16) is equal to 0 +- p) The level constraints specified in clause F.10.2 shall be fulfilled. + +Conformance of a bitstream to the Scalable Constrained High profile is indicated by constraint\_set5\_flag being equal to 1 with profile\_idc equal to 86. + +Decoders conforming to the Scalable Constrained High profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- a) All active SVC sequence parameter sets have one or more of the following conditions fulfilled: + - profile\_idc is equal to 86 and constraint\_set5\_flag is equal to 1, + - profile\_idc is equal to 83, constraint\_set1\_flag is equal to 1, and constraint\_set5\_flag is equal to 1, + - (profile\_idc is equal to 66 or constraint\_set0\_flag is equal to 1), constraint\_set1\_flag is equal to 1, + - profile\_idc is equal to 77 and constraint\_set0\_flag is equal to 1, + - profile\_idc is equal to 77, constraint\_set4\_flag is equal to 1, and constraint\_set5\_flag is equal to 1, + - profile\_idc is equal to 88, constraint\_set1\_flag is equal to 1, constraint\_set4\_flag is equal to 1, and constraint\_set5\_flag is equal to 1, + - profile\_idc is equal to 100 and constraint\_set4\_flag is equal to 1, and constraint\_set5\_flag is equal to 1, +- b) level\_idc or (level\_idc and constraint\_set3\_flag) for all active SVC sequence parameter sets represent a level less than or equal to the specified level. + +### F.10.1.3 Scalable High Intra profile + +Bitstreams conforming to the Scalable High Intra profile shall obey the following constraints: + +- a) The base layer bitstream as specified in clause F.8.8.2 shall obey the following constraints: + - i) All constraints of the High profile specified in clause A.2.4 shall be obeyed. + - ii) Sequence parameter sets should have profile\_idc equal to 100 and constraint\_set3\_flag equal to 1. Sequence parameter sets may have profile\_idc equal to 66, 77, or 88 and constraint\_set1\_flag equal to 1. Sequence parameter sets shall not have profile\_idc equal to a value other than 66, 77, 88, or 100. +- b) A list of integer values specifying layer representation identifiers is derived by invoking the process specified in clause F.8.1.1 with the output being the list dqIdList. The SVC sequence parameter sets that are referred to by coded slice NAL units with DQId greater than 0 and DQId in the list dqIdList shall have profile\_idc equal to 86 and constraint\_set3\_flag equal to 1. +- c) All constraints of the Scalable High profile specified in clause F.10.1.2 shall be obeyed. +- d) All pictures shall be IDR pictures. +- e) SVC sequence parameter sets shall have max\_num\_ref\_frames equal to 0. +- f) When vui\_parameters\_present\_flag is equal to 1 and bitstream\_restriction\_flag is equal to 1, SVC sequence parameter sets shall have max\_num\_reorder\_frames equal to 0. +- g) When vui\_parameters\_present\_flag is equal to 1 and bitstream\_restriction\_flag is equal to 1, SVC sequence parameter sets shall have max\_dec\_frame\_buffering equal to 0. +- h) Picture timing SEI messages, whether present in the bitstream (by non-VCL NAL units) or conveyed equivalently by other means not specified in this Recommendation | International Standard, shall have dpb\_output\_delay equal to 0. +- i) The level constraints specified in clause F.10.2 shall be fulfilled. + +Conformance of a bitstream to the Scalable High Intra profile is indicated by constraint\_set3\_flag being equal to 1 with profile\_idc equal to 86. + +Decoders conforming to the Scalable High Intra profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- a) All active SVC sequence parameter sets have profile\_idc equal to 86 or 100 and constraint\_set3\_flag equal to 1. +- b) level\_idc or (level\_idc and constraint\_set3\_flag) for all active SVC sequence parameter sets represents a level less than or equal to the specified level. + +The operation of the deblocking filter process for target representation as specified in clause F.8.7.2 is not required for decoder conformance to the Scalable High Intra profile. + +### F.10.2 Levels + +The following is specified for expressing the constraints in this clause: + +- Let access unit n be the n-th access unit in decoding order with the first access unit being access unit 0. +- Let picture n be the primary coded picture or the corresponding decoded picture of access unit n. + +The variable fR is derived as follows: + +- If the level number is equal to 6.0, 6.1, or 6.2, fR is set equal to $1 \div 300$ . +- Otherwise, if picture n is a frame, fR is set equal to $(1 \div 172)$ . +- Otherwise (picture n is a field), fR is set equal to $(1 \div (172 * 2))$ . + +#### F.10.2.1 Level limits common to Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, and Scalable High Intra profiles + +The variable dqIdMax is set equal to the maximum value of DQId for the layer representation of the access unit. + +The variable refLayerDQId is set equal to the value of MaxRefLayerDQId for the layer representation with DQId equal to dqIdMax. + +A list of integer values specifying layer representation identifiers for the access unit is derived by invoking the process specified in clause F.8.1.1 with the output being the list dqIdList. The variable numDQEntries is set equal to the number of elements in the list dqIdList. + +A variable dependentDId is derived by the following pseudo-code: + +``` +dependentDId = 0 +for( i = 0; i < numDQEntries; i++ ) + if( ( dqIdList[ i ] % 16 ) == 0 ) + dependentDId++ +``` + +(F-365) + +The variable svcPicSizeInMbs is derived as follows: + +- If numDQEntries is less than 3, svcPicSizeInMbs is set equal to PicSizeInMbs for the layer representation with DQId equal to dqIdMax. +- Otherwise (numDQEntries is greater than 2), svcPicSizeInMbs is derived by applying the following ordered steps: + 1. svcPicSizeInMbs is set equal to PicSizeInMbs for the layer representation with DQId equal to dqIdMax. + 2. The variable refLayerMbs is set equal to 0. + 3. For each element dqIdList[ i ] with i = 2..(numDQEntries – 1), with refLayerPicSizeInMbs being the variable PicSizeInMbs for the layer representation with DQId equal to dqIdList[ i ], the variable refLayerMbs is modified by + +``` +refLayerMbs += refLayerPicSizeInMbs +``` + +(F-366) + +4. svcPicSizeInMbs is modified by + +``` +svcPicSizeInMbs += ( refLayerMbs + 1 ) >> 1 +``` + +(F-367) + +Bitstreams conforming to the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, or Scalable High Intra profiles at a specific level shall obey the following constraints: + +- a) The nominal removal time of access unit n with $n > 0$ from the CPB as specified in clause C.1.2, satisfies the constraint that $t_{rn}(n) - t_r(n - 1)$ is greater than or equal to $\text{Max}(\text{svcPicSizeInMbs} \div \text{MaxMBPS}, \text{fR})$ , where MaxMBPS is the value specified in Table A-1 that applies to picture n – 1 and svcPicSizeInMbs is derived for picture n – 1. + +- b) The difference between consecutive output times of pictures from the DPB as specified in clause C.2.2, satisfies the constraint that $\Delta t_{o,dpb}(n) \geq \text{Max}(\text{svcPicSizeInMbs} \div \text{MaxMBPS}, f_R)$ , where $\text{MaxMBPS}$ is the value specified in Table A-1 for picture $n$ , and $\text{svcPicSizeInMbs}$ is derived for picture $n$ , provided that picture $n$ is a picture that is output and is not the last picture of the bitstream that is output. +- c) $\text{PicWidthInMbs} * \text{FrameHeightInMbs} \leq \text{MaxFS}$ , where $\text{MaxFS}$ is specified in Table A-1. $\text{PicWidthInMbs}$ and $\text{FrameHeightInMbs}$ are the derived variables for the layer representation with $\text{DQId}$ equal to $\text{dqIdMax}$ . +- d) $\text{PicWidthInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ , where $\text{MaxFS}$ is specified in Table A-1 and $\text{PicWidthInMbs}$ is the derived variable for the layer representation with $\text{DQId}$ equal to $\text{dqIdMax}$ . +- e) $\text{FrameHeightInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ , where $\text{MaxFS}$ is specified in Table A-1 and $\text{FrameHeightInMbs}$ is the derived variable for the layer representation with $\text{DQId}$ equal to $\text{dqIdMax}$ . +- f) $\text{max\_dec\_frame\_buffering} \leq \text{MaxDpbFrames}$ , where $\text{MaxDpbFrames}$ is equal to $\text{Min}(\text{MaxDpbMbs} / (\text{PicWidthInMbs} * \text{FrameHeightInMbs}), 16)$ and $\text{MaxDpbMbs}$ is specified in Table A-1. $\text{PicWidthInMbs}$ and $\text{FrameHeightInMbs}$ are the derived variables for the layer representation with $\text{DQId}$ equal to $\text{dqIdMax}$ . +- g) The vertical motion vector component range for luma motion vectors does not exceed the range from $-\text{MaxVmvR}$ to $(\text{MaxVmvR} - 0.25)$ in units of luma frame samples, where $\text{MaxVmvR}$ is specified in Table A-1. +- h) The horizontal motion vector component range for luma motion vectors does not exceed the following range: + - If the level number is less than 6.0, the specified range is from $-2048$ to $2047.75$ , inclusive, in units of luma samples. + - Otherwise, the specified range is from $-8192$ to $8191.75$ , inclusive, in units of luma samples. +- i) For each layer representation, the total number of motion vectors per two macroblocks $\text{mbAddrA}$ and $\text{mbAddrB}$ with $(\text{mbAddrA} + 1)$ equal to $\text{mbAddrB}$ does not exceed $\text{MaxMvsPer2Mb}$ , where $\text{MaxMvsPer2Mb}$ is specified in Table A-1 given the level that is indicated in the SVC sequence parameter set that is referenced by the layer representation. The number of motion vectors for each macroblock is the value of the variable $\text{MvCnt}$ after the completion of the base decoding process for slices without resolution change specified in clause F.8.1.4.1 (when $\text{SpatialResolutionChangeFlag}$ is equal to 0) or after completion the base decoding process for slices with resolution change specified in clause F.8.1.4.2 (when $\text{SpatialResolutionChangeFlag}$ is equal to 1). + + +NOTE – Due to the constraint specified in clause F.8.8.1, the number of motion vectors for the layer representation with $\text{DQId}$ equal to 0 is additionally constrained as specified in Annex A. +- j) The number of bits of $\text{macroblock\_layer}()$ and $\text{macroblock\_layer\_in\_scalable\_extension}()$ data for any macroblock in any layer representation is not greater than $128 + \text{RawMbBits}$ . Depending on $\text{entropy\_coding\_mode\_flag}$ , the bits of $\text{macroblock\_layer}()$ data are counted as follows: + - If $\text{entropy\_coding\_mode\_flag}$ is equal to 0, the number of bits of $\text{macroblock\_layer}()$ data is given by the number of bits in the $\text{macroblock\_layer}()$ syntax structure for a macroblock. + - Otherwise ( $\text{entropy\_coding\_mode\_flag}$ is equal to 1), the number of bits of $\text{macroblock\_layer}()$ data for a macroblock is given by the number of times $\text{read\_bits}(1)$ is called in clauses 9.3.3.2.2 and 9.3.3.2.3 when parsing the $\text{macroblock\_layer}()$ associated with the macroblock. +- k) The variable $\text{dependentDId}$ specified at the beginning of this clause shall not exceed 3. +- l) For each layer representation present in an access unit that has $\text{MinNoInterLayerPredFlag}$ equal to 0, the following applies: + 1. The variables $\text{numILIntraPredSamples}$ and $\text{numRefLayerILIntraPredMbs}$ are derived as specified in the derivation process for variables related to inter-layer intra prediction in clause F.8.6.2.5 with $\text{DQId}$ being the input. + 2. The following constraint shall be obeyed. + +$$\text{numRefLayerILIntraPredMbs} * 256 \leq 1.5 * \text{numILIntraPredSamples} \quad (\text{F-368})$$ +- m) When $\text{MaxRefLayerDQId}$ is greater than or equal to 0 for a particular layer representation, the value of $\text{level\_idc}$ in the SVC sequence parameter set that is referenced by the particular layer representation shall represent a level that is greater than or equal to the level that is represented by the value of $\text{level\_idc}$ or ( $\text{level\_idc}$ and $\text{constraint\_set3\_flag}$ ) in the SVC sequence parameter set that is referenced by the layer representation with $\text{DQId}$ equal to $\text{MaxRefLayerDQId}$ . + +Table A-1 specifies the limits for each level. A definition of all levels identified in the "Level number" column of Table A-1 is specified for the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, and Scalable High Intra profiles. Each entry in Table A-1 indicates, for the level corresponding to the row of the table, the absence or value of a limit that is imposed by the variable corresponding to the column of the table, as follows: + +- If the table entry is marked as "-", no limit is imposed by the value of the variable as a requirement of bitstream conformance to the profile at the specified level. +- Otherwise, the table entry specifies the value of the variable for the associated limit that is imposed as a requirement of bitstream conformance to the profile at the specified level. + +In bitstreams conforming to the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, or Scalable High Intra profiles, the conformance of the bitstream to a specified level is indicated by the syntax element `level_idc` as follows: + +- If `level_idc` is equal to 9, the indicated level is level 1b. +- Otherwise (`level_idc` is not equal to 9), `level_idc` is equal to a value of ten times the level number (of the indicated level) specified in Table A-1. + +#### F.10.2.2 Profile specific level limits + +The variable `dqIdMax` is set equal to the maximum value of `DQId` for the layer representation of the access unit. + +A list of integer values specifying layer representation identifiers for the access unit is derived by invoking the process specified in clause F.8.1.1 with the output being the list `dqIdList`. The variable `numDQEntries` is set equal to the number of elements in the list `dqIdList`. + +The variable `numSVCSlices` is derived as specified by the following pseudo-code: + +``` +numSVCSlices = 0 +for( i = 0; i < numDQEntries; i++ ) + numSVCSlices += number of slices in layer representation with DQId equal to dqIdList[ i ] +``` + +(F-369) + +The variable `svcPicSizeInMbs` is derived as specified in clause F.10.2.1. + +The following constraints are specified: + +- In bitstreams conforming to the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, or Scalable High Intra profiles, the removal time of access unit 0 shall satisfy the constraint that the `numSVCSlices` variable for picture 0 is less than or equal to $( \text{Max( svcPicSizeInMbs, fR * MaxMBPS )} + \text{MaxMBPS} * ( t_r( 0 ) - t_{r,n}( 0 ) ) ) \div \text{SliceRate}$ , where `MaxMBPS` and `SliceRate` are the values that apply to picture 0. `MaxMBPS` is specified in Table A-1. For Scalable Baseline and Scalable Constrained Baseline profiles, `SliceRate` is specified in Table F-16. For Scalable High, Scalable Constrained High, and Scalable High Intra profiles, `SliceRate` is specified in Table A-4. +- In bitstreams conforming to the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, or Scalable High Intra profiles, the difference between consecutive removal times of access units $n$ and $n - 1$ with $n > 0$ shall satisfy the constraint that the `numSVCSlices` variable for picture $n$ is less than or equal to $\text{MaxMBPS} * ( t_r( n ) - t_r( n - 1 ) ) \div \text{SliceRate}$ , where `MaxMBPS` and `SliceRate` are the values that apply to picture $n$ . `MaxMBPS` is specified in Table A-1. For the Scalable Baseline and Scalable Constrained Baseline profiles, `SliceRate` is specified in Table F-16. For the Scalable High, Scalable Constrained High, and Scalable High Intra profiles, `SliceRate` is specified in Table A-4. +- In bitstreams conforming to the Scalable High profile, SVC sequence parameter sets shall have `direct_8x8_inference_flag` equal to 1 for the levels specified in Table A-4. In bitstreams conforming to the Scalable Baseline profile, SVC sequence parameter sets shall have `direct_8x8_inference_flag` equal to 1. + +NOTE 1 – `direct_8x8_inference_flag` is not relevant to the Scalable Constrained Baseline, Scalable Constrained High, and Scalable High Intra profiles, as these profiles do not allow B or EB slice types. + +- In bitstreams conforming to the Scalable High or Scalable High Intra profiles, SVC sequence parameter sets shall have `frame_mbs_only_flag` equal to 1 for the levels specified in Table A-4. +- In bitstreams conforming to the Scalable High profile, for all macroblocks `mbAddr` and macroblock partitions `mbPartIdx`, the value of `subMbType[ mbAddr ][ mbPartIdx ]` that is derived as specified in clause F.8.1.5.1.1 shall not be equal to `B_Bi_8x4`, `B_Bi_4x8`, or `B_Bi_4x4` for the levels in which `MinLumaBiPredSize` is shown as 8x8 in Table A-4. In bitstreams conforming to the Scalable Baseline profile, for all macroblocks `mbAddr` and macroblock partitions `mbPartIdx`, the value of `subMbType[ mbAddr ][ mbPartIdx ]` that is derived as specified in clause F.8.1.5.1.1 shall not be equal to `B_Bi_8x4`, `B_Bi_4x8`, or `B_Bi_4x4`. + +NOTE 2 – The above constraint is not relevant to the Scalable Constrained Baseline, Scalable Constrained High, and Scalable High Intra profiles, as these profiles do not allow B or EB slice types. + +- f) In bitstreams conforming to the Scalable Baseline or Scalable Constrained Baseline profiles, $(xInt_{max} - xInt_{min} + 6) * (yInt_{max} - yInt_{min} + 6) \leq \text{MaxSubMbRectSize}$ in macroblocks coded with macroblock type equal to P\_8x8, P\_8x8ref0 or B\_8x8 for all invocations of the process specified in clause 8.4.2.2.1 used to generate the predicted luma sample array for a single reference picture list (reference picture list 0 or reference picture list 1) for each 8x8 sub-macroblock with the macroblock partition index $mbPartIdx$ , where $\text{NumSubMbPart}(\text{sub\_mb\_type}[ \text{mbPartIdx} ]) > 1$ , where $\text{MaxSubMbRectSize}$ is specified in Table F-16 and +- $xInt_{min}$ is the minimum value of $xInt_L$ among all luma sample predictions for the sub-macroblock, + - $xInt_{max}$ is the maximum value of $xInt_L$ among all luma sample predictions for the sub-macroblock, + - $yInt_{min}$ is the minimum value of $yInt_L$ among all luma sample predictions for the sub-macroblock, + - $yInt_{max}$ is the maximum value of $yInt_L$ among all luma sample predictions for the sub-macroblock. +- g) In bitstreams conforming to the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, or Scalable High Intra profiles, for the VCL HRD parameters, $\text{BitRate}[ \text{SchedSelIdx} ] \leq \text{cpbBrVclFactor} * \text{MaxBR}$ and $\text{CpbSize}[ \text{SchedSelIdx} ] \leq \text{cpbBrVclFactor} * \text{MaxCPB}$ for at least one value of $\text{SchedSelIdx}$ , where $\text{cpbBrVclFactor}$ is specified in Table F-17. With $\text{vui\_ext\_vcl\_hrd\_parameters\_present\_flag}[ i ]$ being the syntax element, in the SVC VUI parameters extension of the active SVC sequence parameter set, that is associated with the VCL HRD parameters that are used for conformance checking (as specified in Annex C), $\text{BitRate}[ \text{SchedSelIdx} ]$ and $\text{CpbSize}[ \text{SchedSelIdx} ]$ are given as follows: +- If $\text{vui\_ext\_vcl\_hrd\_parameters\_present\_flag}[ i ]$ is equal to 1, $\text{BitRate}[ \text{SchedSelIdx} ]$ and $\text{CpbSize}[ \text{SchedSelIdx} ]$ are given by Equations E-81 and E-82, respectively, using the syntax elements of the $\text{hrd\_parameters}( )$ syntax structure that immediately follows $\text{vui\_ext\_vcl\_hrd\_parameters\_present\_flag}[ i ]$ . + - Otherwise ( $\text{vui\_ext\_vcl\_hrd\_parameters\_present\_flag}[ i ]$ is equal to 0), $\text{BitRate}[ \text{SchedSelIdx} ]$ and $\text{CpbSize}[ \text{SchedSelIdx} ]$ are inferred as specified in clause E.2.2 for VCL HRD parameters. + +$\text{MaxBR}$ and $\text{MaxCPB}$ are specified in Table A-1 in units of $\text{cpbBrVclFactor}$ bits/s and $\text{cpbBrVclFactor}$ bits, respectively. The bitstream shall satisfy these conditions for at least one value of $\text{SchedSelIdx}$ in the range 0 to $\text{cpb\_cnt\_minus1}$ , inclusive. + +- h) In bitstreams conforming to the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, or Scalable High Intra profiles, for the NAL HRD parameters, $\text{BitRate}[ \text{SchedSelIdx} ] \leq \text{cpbBrNalFactor} * \text{MaxBR}$ and $\text{CpbSize}[ \text{SchedSelIdx} ] \leq \text{cpbBrNalFactor} * \text{MaxCPB}$ for at least one value of $\text{SchedSelIdx}$ , where $\text{cpbBrNalFactor}$ is specified in Table F-17. With $\text{vui\_ext\_nal\_hrd\_parameters\_present\_flag}[ i ]$ being the syntax element, in the SVC VUI parameters extension of the active SVC sequence parameter set, that is associated with the NAL HRD parameters that are used for conformance checking (as specified in Annex C), $\text{BitRate}[ \text{SchedSelIdx} ]$ and $\text{CpbSize}[ \text{SchedSelIdx} ]$ are given as follows: +- If $\text{vui\_ext\_nal\_hrd\_parameters\_present\_flag}[ i ]$ is equal to 1, $\text{BitRate}[ \text{SchedSelIdx} ]$ and $\text{CpbSize}[ \text{SchedSelIdx} ]$ are given by Equations E-81 and E-82, respectively, using the syntax elements of the $\text{hrd\_parameters}( )$ syntax structure that immediately follows $\text{vui\_ext\_nal\_hrd\_parameters\_present\_flag}[ i ]$ . + - Otherwise ( $\text{vui\_ext\_nal\_hrd\_parameters\_present\_flag}[ i ]$ is equal to 0), $\text{BitRate}[ \text{SchedSelIdx} ]$ and $\text{CpbSize}[ \text{SchedSelIdx} ]$ are inferred as specified in clause E.2.2 for NAL HRD parameters. + +$\text{MaxBR}$ and $\text{MaxCPB}$ are specified in Table A-1 in units of $\text{cpbBrNalFactor}$ bits/s and $\text{cpbBrNalFactor}$ bits, respectively. The bitstream shall satisfy these conditions for at least one value of $\text{SchedSelIdx}$ in the range 0 to $\text{cpb\_cnt\_minus1}$ , inclusive. + +- i) In bitstreams conforming to the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, or Scalable High Intra profiles, the sum of the $\text{NumBytesInNALUnit}$ variables for access unit 0 is less than or equal to $384 * (\text{Max}(\text{svcPicSizeInMbs}, \text{fr} * \text{MaxMBPS}) + \text{MaxMBPS} * (t_f(0) - t_{r,n}(0))) \div \text{MinCR}$ , where $\text{MaxMBPS}$ and $\text{MinCR}$ are the values specified in Table A-1 that apply to picture 0. +- j) In bitstreams conforming to the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, or Scalable High Intra profiles, the sum of the $\text{NumBytesInNALUnit}$ variables for access unit + +n with $n > 0$ is less than or equal to $384 * \text{MaxMBPS} * ( t_r(n) - t_r(n - 1) ) \div \text{MinCR}$ , where MaxMBPS and MinCR are the values specified in Table A-1 that apply to picture n. + +- k) In bitstreams conforming to the Scalable Baseline or Scalable Constrained Baseline profile, picture parameter sets shall have entropy\_coding\_mode\_flag equal to 0 and transform\_8x8\_mode\_flag equal to 0 for level 2.1 and below. +- l) In bitstreams conforming to the Scalable Baseline, Scalable Constrained Baseline, Scalable High, Scalable Constrained High, and Scalable High Intra profiles, when PicSizeInMbs is greater than 1620 for DQId equal to dQIdMax, the number of macroblocks in any coded slice shall not exceed MaxFS / 4, where MaxFS is specified in Table A-1. + +Table A-4 specifies limits for each level that are specific to bitstreams conforming to the Scalable High, Scalable Constrained High, and Scalable High Intra profiles. Table F-16 specifies limits for each level that are specific to bitstreams conforming to the Scalable Baseline and Scalable Constrained Baseline profiles. Each entry in Tables A-4 and F-16 indicates, for the level corresponding to the row of the table, the absence or value of a limit that is imposed by the variable corresponding to the column of the table, as follows: + +- If the table entry is marked as "-", no limit is imposed by the value of the variable as a requirement of bitstream conformance to the profile at the specified level. +- Otherwise, the table entry specifies the value of the variable for the associated limit that is imposed as a requirement of bitstream conformance to the profile at the specified level. + +**Table F-16 – Scalable Baseline and Scalable Constrained Baseline profile level limits** + +| Level number | SliceRate | MaxSubMbRectSize | +|--------------|-----------|------------------| +| 1 | - | 576 | +| 1b | - | 576 | +| 1.1 | - | 576 | +| 1.2 | - | 576 | +| 1.3 | - | 576 | +| 2 | - | 576 | +| 2.1 | 22 | 576 | +| 2.2 | 22 | 576 | +| 3 | 22 | 576 | +| 3.1 | 60 | 1152 | +| 3.2 | 60 | 1152 | +| 4 | 60 | 1440 | +| 4.1 | 24 | 1440 | +| 4.2 | 24 | 1440 | +| 5 | 24 | - | +| 5.1 | 24 | - | +| 6 | 24 | - | +| 6.1 | 24 | - | +| 6.2 | 24 | - | + +**Table F-17 – Specification of cpbBrVclFactor and cpbBrNalFactor** + +| Profile | cpbBrVclFactor | cpbBrNalFactor | +|--------------------------------------------------------------------------------------------------------------------------------|----------------|----------------| +| Scalable Baseline,
Scalable Constrained Baseline,
Scalable High,
Scalable Constrained High, or
Scalable High Intra | 1250 | 1500 | + +**F.11 Byte stream format** + +The specifications in Annex B apply. + +**F.12 Hypothetical reference decoder** + +The specifications in Annex C apply with substituting SVC sequence parameter set for sequence parameter set. + +**F.13 Supplemental enhancement information** + +The specifications in Annex D together with the extensions and modifications specified in this clause apply. + +**F.13.1 SEI payload syntax** + +**F.13.1.1 Scalability information SEI message syntax** + +| | | | +|-----------------------------------------------------------------------|---|------------| +| scalability_info( payloadSize ) { | C | Descriptor | +| temporal_id_nesting_flag | 5 | u(1) | +| priority_layer_info_present_flag | 5 | u(1) | +| priority_id_setting_flag | 5 | u(1) | +| num_layers_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_layers_minus1; i++ ) { | | | +| layer_id[ i ] | 5 | ue(v) | +| priority_id[ i ] | 5 | u(6) | +| discardable_flag[ i ] | 5 | u(1) | +| dependency_id[ i ] | 5 | u(3) | +| quality_id[ i ] | 5 | u(4) | +| temporal_id[ i ] | 5 | u(3) | +| sub_pic_layer_flag[ i ] | 5 | u(1) | +| sub_region_layer_flag[ i ] | 5 | u(1) | +| iroi_division_info_present_flag[ i ] | 5 | u(1) | +| profile_level_info_present_flag[ i ] | 5 | u(1) | +| bitrate_info_present_flag[ i ] | 5 | u(1) | +| frm_rate_info_present_flag[ i ] | 5 | u(1) | +| frm_size_info_present_flag[ i ] | 5 | u(1) | +| layer_dependency_info_present_flag[ i ] | 5 | u(1) | +| parameter_sets_info_present_flag[ i ] | 5 | u(1) | +| bitstream_restriction_info_present_flag[ i ] | 5 | u(1) | +| exact_inter_layer_pred_flag[ i ] | 5 | u(1) | +| if( sub_pic_layer_flag[ i ] iroi_division_info_present_flag[ i ] ) | | | +| exact_sample_value_match_flag[ i ] | 5 | u(1) | +| layer_conversion_flag[ i ] | 5 | u(1) | +| layer_output_flag[ i ] | 5 | u(1) | +| if( profile_level_info_present_flag[ i ] ) | | | + +| | | | +|------------------------------------------------------------------------------------|---|-------| +| layer_profile_level_idc[ i ] | 5 | u(24) | +| if( bitrate_info_present_flag[ i ] ) { | | | +| avg_bitrate[ i ] | 5 | u(16) | +| max_bitrate_layer[ i ] | 5 | u(16) | +| max_bitrate_layer_representation[ i ] | 5 | u(16) | +| max_bitrate_calc_window[ i ] | 5 | u(16) | +| } | | | +| if( frm_rate_info_present_flag[ i ] ) { | | | +| constant_frm_rate_idc[ i ] | 5 | u(2) | +| avg_frm_rate[ i ] | 5 | u(16) | +| } | | | +| if( frm_size_info_present_flag[ i ]
iroi_division_info_present_flag[ i ] ) { | | | +| frm_width_in_mbs_minus1[ i ] | 5 | ue(v) | +| frm_height_in_mbs_minus1[ i ] | 5 | ue(v) | +| } | | | +| if( sub_region_layer_flag[ i ] ) { | | | +| base_region_layer_id[ i ] | 5 | ue(v) | +| dynamic_rect_flag[ i ] | 5 | u(1) | +| if( !dynamic_rect_flag[ i ] ) { | | | +| horizontal_offset[ i ] | 5 | u(16) | +| vertical_offset[ i ] | 5 | u(16) | +| region_width[ i ] | 5 | u(16) | +| region_height[ i ] | 5 | u(16) | +| } | | | +| } | | | +| if( sub_pic_layer_flag[ i ] ) | | | +| roi_id[ i ] | 5 | ue(v) | +| if( iroi_division_info_present_flag[ i ] ) { | | | +| iroi_grid_flag[ i ] | 5 | u(1) | +| if( iroi_grid_flag[ i ] ) { | | | +| grid_width_in_mbs_minus1[ i ] | 5 | ue(v) | +| grid_height_in_mbs_minus1[ i ] | 5 | ue(v) | +| } else { | | | +| num_rois_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= num_rois_minus1[ i ]; j++ ) { | | | +| first_mb_in_roi[ i ][ j ] | 5 | ue(v) | +| roi_width_in_mbs_minus1[ i ][ j ] | 5 | ue(v) | +| roi_height_in_mbs_minus1[ i ][ j ] | 5 | ue(v) | +| } | | | +| } | | | +| } | | | +| if( layer_dependency_info_present_flag[ i ] ) { | | | +| num_directly_dependent_layers[ i ] | 5 | ue(v) | +| for( j = 0; j < num_directly_dependent_layers[ i ]; j++ ) | | | +| directly_dependent_layer_id_delta_minus1[ i ][ j ] | 5 | ue(v) | +| } else | | | +| layer_dependency_info_src_layer_id_delta[ i ] | 5 | ue(v) | + +| | | | +|------------------------------------------------------------|---|-------| +| if( parameter_sets_info_present_flag[ i ] ) { | | | +| num_seq_parameter_sets[ i ] | 5 | ue(v) | +| for( j = 0; j < num_seq_parameter_sets[ i ]; j++ ) | | | +| seq_parameter_set_id_delta[ i ][ j ] | 5 | ue(v) | +| num_subset_seq_parameter_sets[ i ] | 5 | ue(v) | +| for( j = 0; j < num_subset_seq_parameter_sets[ i ]; j++ ) | | | +| subset_seq_parameter_set_id_delta[ i ][ j ] | 5 | ue(v) | +| num_pic_parameter_sets_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= num_pic_parameter_sets_minus1[ i ]; j++ ) | | | +| pic_parameter_set_id_delta[ i ][ j ] | 5 | ue(v) | +| } else | | | +| parameter_sets_info_src_layer_id_delta[ i ] | 5 | ue(v) | +| if( bitstream_restriction_info_present_flag[ i ] ) { | | | +| motion_vectors_over_pic_boundaries_flag[ i ] | 5 | u(1) | +| max_bytes_per_pic_denom[ i ] | 5 | ue(v) | +| max_bits_per_mb_denom[ i ] | 5 | ue(v) | +| log2_max_mv_length_horizontal[ i ] | 5 | ue(v) | +| log2_max_mv_length_vertical[ i ] | 5 | ue(v) | +| max_num_reorder_frames[ i ] | 5 | ue(v) | +| max_dec_frame_buffering[ i ] | 5 | ue(v) | +| } | | | +| if( layer_conversion_flag[ i ] ) { | | | +| conversion_type_idc[ i ] | 5 | ue(v) | +| for( j=0; j < 2; j++ ) { | | | +| rewriting_info_flag[ i ][ j ] | 5 | u(1) | +| if( rewriting_info_flag[ i ][ j ] ) { | | | +| rewriting_profile_level_idc[ i ][ j ] | 5 | u(24) | +| rewriting_avg_bitrate[ i ][ j ] | 5 | u(16) | +| rewriting_max_bitrate[ i ][ j ] | 5 | u(16) | +| } | | | +| } | | | +| } | | | +| } | | | +| if( priority_layer_info_present_flag ) { | | | +| pr_num_dids_minus1 | 5 | ue(v) | +| for( i = 0; i <= pr_num_dids_minus1; i++ ) { | | | +| pr_dependency_id[ i ] | 5 | u(3) | +| pr_num_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= pr_num_minus1[ i ]; j++ ) { | | | +| pr_id[ i ][ j ] | 5 | ue(v) | +| pr_profile_level_idc[ i ][ j ] | 5 | u(24) | +| pr_avg_bitrate[ i ][ j ] | 5 | u(16) | +| pr_max_bitrate[ i ][ j ] | 5 | u(16) | +| } | | | +| } | | | +| } | | | +| if( priority_id_setting_flag ) { | | | +| PriorityIdSettingUriIdx = 0 | | | + +| | | | +|--------------------------------------------------------------------|---|------| +| do | | | +| priority_id_setting_uri [ PriorityIdSettingUriIdx ] | 5 | u(8) | +| while( priority_id_setting_uri[ PriorityIdSettingUriIdx++ ] != 0 ) | | | +| } | | | +| } | | | + +#### F.13.1.2 Sub-picture scalable layer SEI message syntax + +| | | | +|-----------------------------------------|----------|-------------------| +| sub_pic_scalable_layer( payloadSize ) { | C | Descriptor | +| layer_id | 5 | ue(v) | +| } | | | + +#### F.13.1.3 Non-required layer representation SEI message syntax + +| | | | +|-------------------------------------------------------------------|----------|-------------------| +| non_required_layer_rep( payloadSize ) { | C | Descriptor | +| num_info_entries_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_info_entries_minus1; i++ ) { | | | +| entry_dependency_id [ i ] | 5 | u(3) | +| num_non_required_layer_reps_minus1 [ i ] | 5 | ue(v) | +| for( j = 0; j <= num_non_required_layer_reps_minus1[ i ]; j++ ) { | | | +| non_required_layer_rep_dependency_id [ i ][ j ] | 5 | u(3) | +| non_required_layer_rep_quality_id [ i ][ j ] | 5 | u(4) | +| } | | | +| } | | | +| } | | | + +#### F.13.1.4 Priority layer information SEI message syntax + +| | | | +|-------------------------------------------|----------|-------------------| +| priority_layer_info( payloadSize ) { | C | Descriptor | +| pr_dependency_id | 5 | u(3) | +| num_priority_ids | 5 | u(4) | +| for( i = 0; i < num_priority_ids; i++ ) { | | | +| alt_priority_id [ i ] | 5 | u(6) | +| } | | | +| } | | | + +#### F.13.1.5 Layers not present SEI message syntax + +| | | | +|-------------------------------------|----------|-------------------| +| layers_not_present( payloadSize ) { | C | Descriptor | +| num_layers | 5 | ue(v) | +| for( i = 0; i < num_layers; i++ ) { | | | +| layer_id [ i ] | 5 | ue(v) | +| } | | | +| } | | | + +#### F.13.1.6 Layer dependency change SEI message syntax + +| | | | +|-------------------------------------------------------------|---|------------| +| layer_dependency_change( payloadSize ) { | C | Descriptor | +| num_layers_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_layers_minus1; i++ ) { | | | +| layer_id[ i ] | 5 | ue(v) | +| layer_dependency_info_present_flag[ i ] | 5 | u(1) | +| if( layer_dependency_info_present_flag[ i ] ) { | | | +| num_directly_dependent_layers[ i ] | 5 | ue(v) | +| for( j = 0; j < num_directly_dependent_layers[ i ]; j++ ) | | | +| directly_dependent_layer_id_delta_minus1[ i ][ j ] | 5 | ue(v) | +| } else { | | | +| layer_dependency_info_src_layer_id_delta_minus1[ i ] | 5 | ue(v) | +| } | | | +| } | | | +| } | | | +| } | | | + +#### F.13.1.7 Scalable nesting SEI message syntax + +| | | | +|------------------------------------------------------------|---|------------| +| scalable_nesting( payloadSize ) { | C | Descriptor | +| all_layer_representations_in_aus_flag | 5 | u(1) | +| if( all_layer_representations_in_aus_flag == 0 ) { | | | +| num_layer_representations_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_layer_representations_minus1; i++ ) { | | | +| sei_dependency_id[ i ] | 5 | u(3) | +| sei_quality_id[ i ] | 5 | u(4) | +| } | | | +| sei_temporal_id | 5 | u(3) | +| } | | | +| while( !byte_aligned() ) | | | +| sei_nesting_zero_bit /* equal to 0 */ | 5 | f(1) | +| do | | | +| sei_message() | 5 | | +| while( more_rbsp_data() ) | | | +| } | | | +| } | | | +| } | | | + +#### F.13.1.8 Base layer temporal HRD SEI message syntax + +| | | | +|-----------------------------------------------------------------------|---|------------| +| base_layer_temporal_hrd( payloadSize ) { | C | Descriptor | +| num_of_temporal_layers_in_base_layer_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_of_temporal_layers_in_base_layer_minus1; i++ ) { | | | +| sei_temporal_id[ i ] | 5 | u(3) | +| sei_timing_info_present_flag[ i ] | 5 | u(1) | +| if( sei_timing_info_present_flag[ i ] ) { | | | +| sei_num_units_in_tick[ i ] | 5 | u(32) | +| sei_time_scale[ i ] | 5 | u(32) | +| } | | | +| } | | | +| } | | | + +| | | | +|-----------------------------------------------------------------------------------------------|---|------| +| sei_fixed_frame_rate_flag[ i ] | 5 | u(1) | +| } | | | +| sei_nal_hrd_parameters_present_flag[ i ] | 5 | u(1) | +| if( sei_nal_hrd_parameters_present_flag[ i ] ) | | | +| hrd_parameters( ) | 5 | | +| sei_vcl_hrd_parameters_present_flag[ i ] | 5 | u(1) | +| if( sei_vcl_hrd_parameters_present_flag[ i ] ) | | | +| hrd_parameters( ) | 5 | | +| if( sei_nal_hrd_parameters_present_flag[ i ]
sei_vcl_hrd_parameters_present_flag[ i ] ) | | | +| sei_low_delay_hrd_flag[ i ] | 5 | u(1) | +| sei_pic_struct_present_flag[ i ] | 5 | u(1) | +| } | | | +| } | | | + +#### F.13.1.9 Quality layer integrity check SEI message syntax + +| | | | +|-------------------------------------------------------|----------|-------------------| +| quality_layer_integrity_check( payloadSize ) { | C | Descriptor | +|     num_info_entries_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_info_entries_minus1; i++ ) { | | | +| entry_dependency_id[ i ] | 5 | u(3) | +| quality_layer_crc[ i ] | 5 | u(16) | +| } | | | +| } | | | + +#### F.13.1.10 Redundant picture property SEI message syntax + +| | | | +|---------------------------------------------------------------|----------|-------------------| +| redundant_pic_property( payloadSize ) { | C | Descriptor | +| num_dIds_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_dIds_minus1; i++ ) { | | | +| dependency_id[ i ] | 5 | u(3) | +| num_qIds_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= num_qIds_minus1[ i ]; j++ ) { | | | +| quality_id[ i ][ j ] | 5 | u(4) | +| num_redundant_pics_minus1[ i ][ j ] | 5 | ue(v) | +| for( k = 0; k <= num_redundant_pics_minus1[ i ][ j ]; k++ ) { | | | +| redundant_pic_cnt_minus1[ i ][ j ][ k ] | 5 | ue(v) | +| pic_match_flag[ i ][ j ][ k ] | 5 | u(1) | +| if( !pic_match_flag[ i ][ j ][ k ] ) { | | | +| mb_type_match_flag[ i ][ j ][ k ] | 5 | u(1) | +| motion_match_flag[ i ][ j ][ k ] | 5 | u(1) | +| residual_match_flag[ i ][ j ][ k ] | 5 | u(1) | +| intra_samples_match_flag[ i ][ j ][ k ] | 5 | u(1) | +| } | | | +| } | | | +| } | | | +| } | | | +| } | | | + +#### F.13.1.11 Temporal level zero dependency representation index SEI message syntax + +| | | | +|------------------------------------|----------|-------------------| +| tl0_dep_rep_index( payloadSize ) { | C | Descriptor | +| tl0_dep_rep_idx | 5 | u(8) | +| effective_idr_pic_id | 5 | u(16) | +| } | | | + +#### F.13.1.12 Temporal level switching point SEI message syntax + +| | | | +|-------------------------------------|----------|-------------------| +| tl_switching_point( payloadSize ) { | C | Descriptor | +| delta_frame_num | 5 | se(v) | +| } | | | + +### F.13.2 SEI payload semantics + +The semantics of the SEI messages with payloadType in the range of 0 to 23, inclusive, or equal to 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212, which are specified in clause D.2, are extended as follows: + +- If payloadType is equal to 3, 8, 19, 20, or 22, the following applies: + - If the SEI message is not included in a scalable nesting SEI message, it applies to the layer representations of the current access unit that have dependency\_id equal to 0 and quality\_id equal to 0. + +The semantics as specified in clause D.2 apply to the bitstream that would be obtained by invoking the bitstream extraction process as specified in clause F.8.8.1 with dIdTarget equal to 0 and qIdTarget equal to 0. All syntax elements and derived variables that are referred to in the semantics in clause D.2 are syntax elements and variables for layer representations with dependency\_id equal to 0 and quality\_id equal to 0. All SEI messages that are referred to in clause D.2 are SEI messages that apply to layer representations with dependency\_id equal to 0 and quality\_id equal to 0. + +- Otherwise (the SEI message is included in a scalable nesting SEI message), the SEI message applies to all layer representations of the current access unit for which DQId is equal to any value of $((\text{sei\_dependency\_id}[i] \ll 4) + \text{sei\_quality\_id}[i])$ with $i$ in the range of 0 to $\text{num\_layer\_representations\_minus1}$ , inclusive. + +For each value of $i$ in the range of 0 to $\text{num\_layer\_representations\_minus1}$ , inclusive, the semantics as specified in clause D.2 apply to the bitstream that would be obtained by invoking the bitstream extraction process as specified in clause F.8.8.1 with dIdTarget equal to $\text{sei\_dependency\_id}[i]$ and qIdTarget equal to $\text{sei\_quality\_id}[i]$ . All syntax elements and derived variables that are referred to in the semantics in clause D.2 are syntax elements and variables for layer representations with dependency\_id equal to $\text{sei\_dependency\_id}[i]$ and quality\_id equal to $\text{sei\_quality\_id}[i]$ . All SEI messages that are referred to in clause D.2 are SEI messages that apply to layer representations with dependency\_id equal to $\text{sei\_dependency\_id}[i]$ and quality\_id equal to $\text{sei\_quality\_id}[i]$ . + +- Otherwise, if payloadType is equal to 2, 6, 7, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 21, 23, 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212, the following applies: + - If the SEI message is not included in a scalable nesting SEI message, it applies to the dependency representations of the current access unit that have dependency\_id equal to 0. + +The semantics as specified in clause D.2 apply to the bitstream that would be obtained by invoking the bitstream extraction process as specified in clause F.8.8.1 with dIdTarget equal to 0. All syntax elements and derived variables that are referred to in the semantics in clause D.2 are syntax elements and variables for dependency representations with dependency\_id equal to 0. All SEI messages that are referred to in clause D.2 are SEI messages that apply to dependency representations with dependency\_id equal to 0. + +- Otherwise (the SEI message is included in a scalable nesting SEI message), the scalable nesting SEI message containing the SEI message shall have $\text{all\_layer\_representations\_in\_au\_flag}$ equal to 1 or, when $\text{all\_layer\_representations\_in\_au\_flag}$ is equal to 0, all values of $\text{sei\_quality\_id}[i]$ present in the scalable nesting SEI message shall be equal to 0. The SEI message that is included in the scalable nesting SEI message applies to all dependency representations of the current access unit for which dependency\_id is equal to any value of $\text{sei\_dependency\_id}[i]$ with $i$ in the range of 0 to $\text{num\_layer\_representations\_minus1}$ , inclusive. + +For each value of $i$ in the range of 0 to $\text{num\_layer\_representations\_minus1}$ , inclusive, the semantics as specified in clause D.2 apply to the bitstream that would be obtained by invoking the bitstream extraction process as specified in clause F.8.8.1 with dIdTarget equal to $\text{sei\_dependency\_id}[i]$ . All syntax elements and derived variables that are referred to in the semantics in clause D.2 are syntax elements and variables for dependency representations with dependency\_id equal to $\text{sei\_dependency\_id}[i]$ . All SEI messages that are referred to in clause D.2 are SEI messages that apply to dependency representations with dependency\_id equal to $\text{sei\_dependency\_id}[i]$ . + +When payloadType is equal to 10 for the SEI message that is included in a scalable nesting SEI message, the semantics for $\text{sub\_seq\_layer\_num}$ of the sub-sequence information SEI message is modified as follows: + +**sub\_seq\_layer\_num** specifies the sub-sequence layer number of the current picture. When the current picture resides in a sub-sequence for which the first picture in decoding order is an IDR picture, the value of $\text{sub\_seq\_layer\_num}$ shall be equal to 0. For a non-paired reference field, the value of $\text{sub\_seq\_layer\_num}$ shall be equal to 0. $\text{sub\_seq\_layer\_num}$ shall be in the range of 0 to 255, inclusive. + +- Otherwise, if payloadType is equal to 0 or 1, the following applies: + - If the SEI message is not included in a scalable nesting SEI message, the following applies. When the SEI message and all other SEI messages with payloadType equal to 0 or 1 not included in a scalable nesting SEI message are used as the buffering period and picture timing SEI messages for checking the bitstream conformance according to Annex C and the decoding process specified in clauses 2 to 9 is used, the bitstream shall be conforming to this Recommendation | International Standard. + +The value of $\text{seq\_parameter\_set\_id}$ in a buffering period SEI message not included in a scalable nesting SEI message shall be equal to the value of $\text{seq\_parameter\_set\_id}$ in the picture parameter set that is referenced by the layer representation with DQId equal to 0 of the primary coded picture in the same access unit. + +- Otherwise (the SEI message is included in a scalable nesting SEI message), the following applies. When the SEI message and all other SEI messages with `payloadType` equal to 0 or 1 included in a scalable nesting SEI message with identical values of `sei_temporal_id`, `sei_dependency_id[ i ]`, and `sei_quality_id[ i ]` are used as the buffering period and picture timing SEI messages for checking the bitstream conformance according to Annex C, the bitstream that would be obtained by invoking the bitstream extraction process as specified in clause F.8.8.1 with `tIdTarget` equal to `sei_temporal_id`, `dIdTarget` equal to `sei_dependency_id[ i ]`, and `qIdTarget` equal to `sei_quality_id[ i ]` shall be conforming to this Recommendation | International Standard. + +In the semantics of clauses D.2.1 and D.2.3, the syntax elements `num_units_in_tick`, `time_scale`, `fixed_frame_rate_flag`, `nal_hrd_parameters_present_flag`, `vcl_hrd_parameters_present_flag`, `low_delay_hrd_flag`, and `pic_struct_present_flag` and the derived variables `NalHrdBpPresentFlag`, `VclHrdBpPresentFlag`, and `CpbDpbDelaysPresentFlag` are substituted with the syntax elements `vui_ext_num_units_in_tick[ i ]`, `vui_ext_time_scale[ i ]`, `vui_ext_fixed_frame_rate_flag[ i ]`, `vui_ext_nal_hrd_parameters_present_flag[ i ]`, `vui_ext_vcl_hrd_parameters_present_flag[ i ]`, `vui_ext_low_delay_hrd_flag[ i ]`, and `vui_ext_pic_struct_present_flag[ i ]` and the derived variables `VuiExtNalHrdBpPresentFlag[ i ]`, `VuiExtVclHrdBpPresentFlag[ i ]`, and `VuiExtCpbDpbDelaysPresentFlag[ i ]`. + +The value of `seq_parameter_set_id` in a buffering period SEI message included in a scalable nesting SEI message with the values of `sei_dependency_id[ i ]` and `sei_quality_id[ i ]` shall be equal to the value of `seq_parameter_set_id` in the picture parameter set that is referenced by the layer representation with `DQId` equal to $(( \text{sei\_dependency\_id}[ i ] \ll 4 ) + \text{sei\_quality\_id}[ i ])$ of the primary coded picture in the same access unit. + +- Otherwise (`payloadType` is equal to 4 or 5), the corresponding SEI message semantics are not extended. + +When an SEI message having a particular value of `payloadType` equal to 137 or 144, contained in a scalable nesting SEI message, and applying to a particular combination of `dependency_id`, `quality_id`, and `temporal_id` is present in an access unit, the SEI message with the particular value of `payloadType` applying to the particular combination of `dependency_id`, `quality_id`, and `temporal_id` shall be present a scalable nesting SEI message in the IDR access unit that is the first access unit of the coded video sequence. + +All SEI messages having a particular value of `payloadType` equal to 137 or 144, contained in scalable nesting SEI messages, and applying to a particular combination of `dependency_id`, `quality_id`, and `temporal_id` present in a coded video sequence shall have the same content. + +For the semantics of SEI messages with `payloadType` in the range of 0 to 23, inclusive, or equal to 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212, which are specified in clause D.2, SVC sequence parameter set is substituted for sequence parameter set; the parameters of the picture parameter set RBSP and SVC sequence parameter set RBSP that are in effect are specified in clause F.7.4.1.2.1. + +Coded video sequences conforming to one or more of the profiles specified in Annex F shall not include SEI NAL units that contain SEI messages with `payloadType` in the range of 36 to 44, inclusive, or equal to 46, which are specified in clause G.13, or with `payloadType` in the range of 48 to 53, inclusive, which are specified in clause H.13. + +When an SEI NAL unit contains an SEI message with `payloadType` in the range of 24 to 35, inclusive, which are specified in clause F.13, it shall not contain any SEI message that has `payloadType` less than 24 or equal to 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212 that is not included in a scalable nesting SEI message, and the first SEI message in the SEI NAL unit shall have `payloadType` in the range of 24 to 35, inclusive. + +When an SEI NAL unit contains an SEI message with `payloadType` equal to 24, 28, or 29, it shall not contain any SEI message with `payloadType` not equal to 24, 28, or 29. + +When a scalable nesting SEI message (`payloadType` is equal to 30) is present in an SEI NAL unit, it shall be the only SEI message in the SEI NAL unit. + +The semantics for SEI messages with `payloadType` in the range of 24 to 35, inclusive, are specified in the following. + +### F.13.2.1 Scalability information SEI message semantics + +The scalability information SEI message provides scalability information for subsets of the bitstream. + +In the following specification of this clause, a VCL NAL unit of a primary coded picture is also referred to as primary coded VCL NAL unit and a VCL NAL unit of a redundant coded picture is also referred to as redundant coded VCL NAL unit. + +A scalability information SEI message shall not be included in a scalable nesting SEI message. + +A scalability information SEI message shall not be present in access units that contain primary coded VCL NAL units with `IdrPicFlag` equal to 0. The set of access units consisting of the access unit associated with the scalability information + +SEI message and all succeeding access units in decoding order until, but excluding, the next access unit that does not contain any primary coded VCL NAL unit with IdrPicFlag equal to 0 (if present) or the end of the bitstream (otherwise) is referred to as the target access unit set. The scalability information SEI message applies to the target access unit set. + +The scalability information SEI message provides information for subsets of the target access unit set. These subsets are referred to as scalable layers. A scalable layer represents a set of NAL units, inside the target access unit set, that consists of VCL NAL units with the same values of dependency\_id, quality\_id, and temporal\_id, as specified later in this clause, and associated non-VCL NAL units. When present in the target access unit set, the following NAL units are associated non-VCL NAL units for a scalable layer: + +- sequence parameter set, subset sequence parameter set, and picture parameter set NAL units that are referenced in the VCL NAL units of the scalable layer (via the syntax element pic\_parameter\_set\_id), +- sequence parameter set extension NAL units that are associated with a sequence parameter set NAL unit referenced in the VCL NAL units of the scalable layer, +- filler data NAL units that are associated with the same values of dependency\_id, quality\_id, and temporal\_id as the VCL NAL units of the scalable layer, +- SEI NAL units containing SEI messages, with payloadType not equal to 24, 28, or 29, that apply to subsets of the bitstream that contain one or more VCL NAL units of the scalable layer, +- access unit delimiter, end of sequence, and end of stream NAL units that are present in access units that contain VCL NAL units of the scalable layer, +- when dependency\_id and quality\_id are both equal to 0 in the VCL NAL units of a scalable layer, coded slice of an auxiliary coded picture without partitioning NAL units that are present in access units that contain VCL NAL units of the scalable layer. + +A scalable layer A is directly dependent on a scalable layer B when any primary coded VCL NAL unit of the scalable layer A references data of any VCL NAL unit of the scalable layer B through inter prediction or inter-layer prediction as specified in the decoding process in clause F.8, with the following exception: A scalable layer A (identified by layer\_id[ a ]) is not directly dependent on a scalable layer B (identified by layer\_id[ b ]) when dependency\_id[ a ] is equal to dependency\_id[ b ], sub\_pic\_layer\_flag[ a ] is equal to 1, and one of the following conditions is true: + +- sub\_pic\_layer\_flag[ b ] is equal to 0, +- sub\_pic\_layer\_flag[ b ] is equal to 1 and (horizontal\_offset[ a ] is not equal to horizontal\_offset[ b ], vertical\_offset[ a ] is not equal to vertical\_offset[ b ], region\_width[ a ] is not equal to region\_width[ b ], or region\_height[ a ] is not equal to region\_height[ b ]). + +NOTE 1 – Sub-picture scalable layers with a particular value of dependency\_id and a particular sub-picture area are only considered to depend on scalable layers with the same value of dependency\_id when these scalable layers are associated with the same sub-picture area. + +A scalable layer A is indirectly dependent on a scalable layer B when the scalable layer A is not directly dependent on the scalable layer B but there exists a set of $n$ (with $n$ being greater than 0) scalable layers $\{C_0, \dots, C_{n-1}\}$ with the following properties: The scalable layer A is directly dependent on the scalable layer $C_0$ , each scalable layer $C_i$ with $i$ in the range of 0 to $n - 2$ , inclusive, is directly dependent on the scalable layer $C_{i+1}$ , and the scalable layer $C_{n-1}$ is directly dependent on the scalable layer B. + +The representation of a particular scalable layer is the set of NAL units that represents the set union of the particular scalable layer and all scalable layers on which the particular scalable layer directly or indirectly depends. The representation of a scalable layer is also referred to as scalable layer representation. In the following specification of this clause, the terms representation of a scalable layer and scalable layer representation are also used for referring to the access unit set that can be constructed from the NAL units of the scalable layer representation. A scalable layer representation can be decoded independently of all NAL units that do not belong to the scalable layer representation. The decoding result of a scalable layer representation is the set of decoded pictures that are obtained by decoding the access unit set of the scalable layer representation. + +NOTE 2 – The set of access units that is formed by the representation of a scalable layer with sub\_pic\_layer\_flag[ i ] equal to 1 does not conform to this Recommendation | International Standard, since the primary coded VCL NAL units with quality\_id equal to 0 that belong to such a scalable layer representation do not cover all macroblocks of the layer pictures with dependency\_id equal to dependency\_id[ i ] and quality\_id equal to 0. For the following specification in this clause, the decoding result for the representation of a scalable layer with sub\_pic\_layer\_flag[ i ] equal to 1 is the decoding result that would be obtained for the sub-picture area (as specified later in this clause) by following the decoding process in clause F.8 but ignoring the constraint that the layer representations with quality\_id equal to 0 of primary coded pictures must cover all macroblocks of the corresponding layer pictures. + +Each scalable layer is associated with a unique layer identifier as specified later in this clause. The representation of a particular scalable layer with a particular layer identifier layerId does not include any scalable layer with a layer identifier + +greater than layerId, but it may include scalable layers with layer identifiers less than layerId. The scalable layers on which a particular scalable layer depends may be indicated in the scalability information SEI message as specified later in this clause. + +NOTE 3 – When all scalable layers for which scalability information is provided in the scalability information SEI message have sub\_pic\_layer\_flag[ i ] equal to 0, the unique layer identifier values may be set equal to $( 128 * \text{dependency\_id} + 8 * \text{quality\_id} + \text{temporal\_id} )$ , with dependency\_id, quality\_id, and temporal\_id being the corresponding syntax elements that are associated with the VCL NAL units of a scalable layer. + +**temporal\_id\_nesting\_flag** indicates whether inter prediction is additionally restricted for the target access unit set. Depending on the value of temporal\_id\_nesting\_flag, the following applies: + +- If **temporal\_id\_nesting\_flag** is equal to 1, the scalability information SEI message indicates that the following constraint is obeyed for all access units sets that can be derived from the target access unit set by invoking the sub-bitstream extraction process as specified in clause F.8.8.1 with tIdTarget equal to any value in the range of 0 to 7, inclusive, dIdTarget equal to any value in the range of 0 to 7, inclusive, and qIdTarget equal to any value in the range of 0 to 15, inclusive, as the inputs: The values of the samples in the decoded pictures for each access unit auA with temporal\_id equal to tIdA and all following access units in decoding order are independent of an access unit auB with temporal\_id equal to tIdB and tIdB less than or equal to tIdA, when there exists an access unit auC with temporal\_id equal to tIdC and tIdC less than tIdB, that follows the access unit auB and precedes the access unit auA in decoding order. +- Otherwise (**temporal\_id\_nesting\_flag** is equal to 0), the scalability information SEI message indicates that the constraint specified for temporal\_id\_nesting\_flag equal to 1 may or may not be obeyed. + +NOTE 4 – The syntax element temporal\_id\_nesting\_flag is used to indicate that temporal up-switching, i.e., switching from decoding of up to a particular temporal\_id value tIdN to decoding of up to a temporal\_id value tIdM greater than tIdN, is always possible inside the target access unit set. + +**priority\_layer\_info\_present\_flag** equal to 1 specifies that characteristic information for priority layers, as specified later in this clause, is present in the scalability information SEI message and that priority layer information SEI messages associating an alternative value for priority\_id with each layer representation of the primary coded pictures in the target access unit set are present. priority\_layer\_info\_present\_flag equal to 0 specifies that characteristic information for priority layers is not present in the scalability information SEI message. + +**priority\_id\_setting\_flag** equal to 1 specifies that syntax elements priority\_id\_setting\_uri[ i ] are present in the scalability information SEI message and that the description of the method used to calculate the priority\_id values is provided by priority\_id\_setting\_uri[ i ] syntax elements. priority\_id\_setting\_flag equal to 0 specifies that priority\_id\_setting\_uri[ i ] syntax elements are not present in the scalability information SEI message. + +**num\_layers\_minus1** plus 1 specifies the number of scalable layers for which information is provided in the scalability information SEI message. The value of num\_layers\_minus1 shall be in the range of 0 to 2047, inclusive. + +**layer\_id[ i ]** specifies the layer identifier of the i-th scalable layer specified in the scalability information SEI message. layer\_id[ i ] shall be in the range of 0 to 2047, inclusive. + +For the following specification inside this clause, the scalable layer with layer identifier equal to the current value of layer\_id[ i ] is referred to as the current scalable layer, and the representation of the current scalable layer is referred to as the current scalable layer representation. + +**priority\_id[ i ]** indicates an upper bound for the priority\_id values of the current scalable layer representation. All primary coded VCL NAL units of the current scalable layer representation shall have a value of priority\_id that is less than or equal to priority\_id[ i ]. + +**discardable\_flag[ i ]** equal to 1 indicates that all primary coded VCL NAL units of the current scalable layer have discardable\_flag equal to 1. discardable\_flag[ i ] equal to 0 indicates that the current scalable layer may contain one or more primary coded VCL NAL units with discardable\_flag equal to 0. + +**dependency\_id[ i ]**, **quality\_id[ i ]**, and **temporal\_id[ i ]** are equal to the values of dependency\_id, quality\_id, and temporal\_id, respectively, of the VCL NAL units of the current scalable layer. All VCL NAL units of a scalable layer have the same values of dependency\_id, quality\_id, and temporal\_id. + +When the target access unit set does not contain any primary coded VCL NAL unit with particular values of dependency\_id, quality\_id, and temporal\_id, the scalability information SEI message shall not contain information for a scalable layer with dependency\_id[ i ], quality\_id[ i ], and temporal\_id[ i ] equal to the particular values of dependency\_id, quality\_id, and temporal\_id, respectively. + +NOTE 5 – When an application removes NAL units from a scalable bitstream, e.g. in order to adapt the bitstream to a transmission channel or the capabilities of a receiving device, and keeps the present scalability information SEI messages, it might need to modify the content of the scalability information SEI messages in order to obtain a bitstream conforming to this Recommendation | International Standard. + +**sub\_pic\_layer\_flag[ i ]** specifies whether the current scalable layer represents a sub-picture scalable layer as specified subsequently. Depending on **sub\_pic\_layer\_flag[ i ]**, the following applies: + +- If **sub\_pic\_layer\_flag[ i ]** is equal to 0, the current scalable layer does not represent a sub-picture scalable layer. The VCL NAL units of the current scalable layer are all VCL NAL units of the target access unit set that have **dependency\_id**, **quality\_id**, and **temporal\_id** equal to **dependency\_id[ i ]**, **quality\_id[ i ]**, and **temporal\_id[ i ]**, respectively. +- Otherwise (**sub\_pic\_layer\_flag[ i ]** is equal to 1), the current scalable layer represents a sub-picture scalable layer and is associated with a sub-picture area as specified in the following: + - (a) The sub-picture area is a rectangular area of slice group map units inside the layer frames with **dependency\_id** equal to **dependency\_id[ i ]** and represents a proper subset of the area of the layer frames with **dependency\_id** equal to **dependency\_id[ i ]**. The sub-picture area associated with a sub-picture scalable layer does not change inside the target access unit set. The sub-picture area is specified by the syntax elements **horizontal\_offset[ i ]**, **vertical\_offset[ i ]**, **region\_width[ i ]**, and **region\_height[ i ]** as specified later in this clause. + +NOTE 6 – The sub-picture area for a sub-picture scalable layer may additionally be indicated by the presence of sub-picture scalable layer SEI messages with **layer\_id** equal to value of **layer\_id[ i ]** for the current scalable layer. + +- (b) When a VCL NAL unit of the target access unit set has **dependency\_id** equal to **dependency\_id[ i ]** and contains any macroblock that resides inside the sub-picture area, it shall not contain any macroblock that resides outside of the sub-picture area. +- (c) The VCL NAL units of the current scalable layer are the coded slice NAL units of the target access unit set that have **dependency\_id**, **quality\_id**, and **temporal\_id** equal to **dependency\_id[ i ]**, **quality\_id[ i ]**, and **temporal\_id[ i ]**, respectively, and for which the macroblock specified by **first\_mb\_in\_slice** resides inside the specified sub-picture area and the associated prefix NAL units (when present). +- (d) For all access units sets that can be derived from the target access unit set by invoking the sub-bitstream extraction process as specified in clause F.8.8.1 with **dIdTarget** equal to **dependency\_id[ i ]** and **qIdTarget** equal to any value in the range of 0 to 15, inclusive, as the inputs, the following constraint shall be obeyed: No sample value outside the sub-picture area and no sample value at a fractional sample position that is derived using one or more sample values outside the sub-picture area is used, in the decoding process as specified in clause F.8, for inter prediction of any sample within the sub-picture area. + +When the target access unit set contains any primary coded VCL NAL unit with particular values of **dependency\_id**, **quality\_id**, and **temporal\_id**, the scalability information SEI message shall contain information for a exactly one scalable layer with **dependency\_id[ i ]**, **quality\_id[ i ]**, and **temporal\_id[ i ]** equal to the particular values of **dependency\_id**, **quality\_id**, and **temporal\_id**, respectively, and **sub\_pic\_layer\_flag[ i ]** equal to 0. + +NOTE 7 – The scalability information SEI message may additionally contain information for one or more scalable layers with **dependency\_id[ i ]**, **quality\_id[ i ]**, and **temporal\_id[ i ]** equal to the particular values of **dependency\_id**, **quality\_id**, and **temporal\_id**, respectively, and **sub\_pic\_layer\_flag[ i ]** equal to 1. + +When **sub\_pic\_layer\_flag[ i ]** is equal to 1 for the current scalable layer and the target access unit set contains any primary coded VCL NAL unit that has **dependency\_id** equal to **dependency\_id[ i ]**, resides inside the sub-picture area, and has particular values of **quality\_id** and **temporal\_id**, with either **quality\_id** not equal to **quality\_id[ i ]** or **temporal\_id** not equal to **temporal\_id[ i ]**, the scalability information SEI message shall also contain information for a scalable layer **j** with **dependency\_id[ j ]** equal to **dependency\_id[ i ]**, **quality\_id[ j ]** and **temporal\_id[ j ]** equal to the particular values of **quality\_id** and **temporal\_id**, respectively, **sub\_pic\_layer\_flag[ j ]** equal to 1, and **horizontal\_offset[ j ]**, **vertical\_offset[ j ]**, **region\_width[ j ]**, and **region\_height[ j ]** equal to **horizontal\_offset[ i ]**, **vertical\_offset[ i ]**, **region\_width[ i ]**, and **region\_height[ i ]**, respectively. + +The scalability information SEI message shall not contain information for two or more scalable layers with **sub\_pic\_layer\_flag[ i ]** equal to 1 and the same values of **dependency\_id[ i ]**, **quality\_id[ i ]**, **temporal\_id[ i ]**, **sub\_pic\_layer\_flag[ i ]**, **horizontal\_offset[ i ]**, **vertical\_offset[ i ]**, **region\_width[ i ]**, and **region\_height[ i ]**. + +When the scalability information SEI message contains information for two scalable layers A and B (identified by **layer\_id[ a ]** and **layer\_id[ b ]**, respectively) with **dependency\_id[ a ]** equal to **dependency\_id[ b ]**, **quality\_id[ a ]** equal to **quality\_id[ b ]**, **temporal\_id[ a ]** equal to **temporal\_id[ b ]**, **sub\_pic\_layer\_flag[ a ]** equal to 1, and **sub\_pic\_layer\_flag[ b ]** equal to 1, and the sub-picture areas associated with the scalable layers A and B overlap, the scalability information SEI message shall also contain information for a scalable layer C (identified by **layer\_id[ c ]**) with **dependency\_id[ c ]** equal to **dependency\_id[ b ]**, **quality\_id[ c ]** equal to **quality\_id[ b ]**, **temporal\_id[ c ]** equal to **temporal\_id[ b ]**, and **sub\_pic\_layer\_flag[ c ]** is equal to 1, and with the scalable layer C being associated with a sub-picture area that represents the intersection of the sub-picture areas associated with the scalable layers A and B. + +**sub\_region\_layer\_flag[ i ]** equal to 1 specifies that the syntax elements **base\_region\_layer\_id[ i ]** and **dynamic\_rect\_flag[ i ]** for the current scalable layer are present in the scalability information SEI message. + +`sub_region_layer_flag[ i ]` equal to 0 specifies that the syntax elements `base_region_layer_id[ i ]` and `dynamic_rect_flag[ i ]` for the current scalable layer are not present in the scalability information SEI message. + +When `sub_pic_layer_flag[ i ]` is equal to 1, `sub_region_layer_flag[ i ]` shall be equal to 1. + +**`iroi_division_info_present_flag[ i ]`** equal to 1 specifies that the layer pictures with `dependency_id` equal to `dependency_id[ i ]` are divided along slice group map unit boundaries into multiple rectangular regions of interest, referred to as interactive regions of interest (IROIs), and that the IROI division information is explicitly signalled in the scalability information SEI message as specified later in this clause, and that the syntax elements `frame_width_in_mbs_minus1[ i ]` and `frame_height_in_mbs_minus1[ i ]` for the current scalable layer are present in the scalability information SEI message. `iroi_division_info_present_flag[ i ]` equal to 0 specifies that the IROI division information for the current scalable layer is not present in the scalability information SEI message. + +When `sub_pic_layer_flag[ i ]` is equal to 1, `iroi_division_info_present_flag[ i ]` shall be equal to 0. + +When `iroi_division_info_present_flag[ i ]` is equal to 1, the following is specified: + +- (a) When a primary coded VCL NAL unit of the target access unit set has `dependency_id` equal to `dependency_id[ i ]` and contains any macroblock that resides inside a particular IROI, it shall not contain any macroblock that resides outside of the particular IROI. +- (b) For all access units sets that can be derived from the target access unit set by invoking the sub-bitstream extraction process as specified in clause F.8.8.1 with `dIdTarget` equal to `dependency_id[ i ]` and `qIdTarget` equal to any value in the range of 0 to 15, inclusive, as the inputs, the following constraint shall be obeyed: No sample value outside a particular IROI and no sample value at a fractional sample position that is derived using one or more sample values outside the particular IROI is used, in the decoding process as specified in clause F.8, for inter prediction of any sample within the particular IROI. + +All scalable layers with the same value of `dependency_id[ i ]` for which scalability information is present in the scalability information SEI message shall have the same value of `iroi_division_info_present_flag[ i ]`. + +**`profile_level_info_present_flag[ i ]`** equal to 1 specifies that `profile_idc`, `constraint_set0_flag`, `constraint_set1_flag`, `constraint_set2_flag`, `constraint_set3_flag`, `constraint_set4_flag`, `constraint_set5_flag`, `reserved_zero_2bits`, and `level_idc` applicable for the current scalable layer representation are indicated by the value of `layer_profile_level_idc[ i ]` as specified later in this clause. + +When `profile_level_info_present_flag[ i ]` is equal to 0, `profile_idc`, `constraint_set0_flag`, `constraint_set1_flag`, `constraint_set2_flag`, `constraint_set3_flag`, `constraint_set4_flag`, `constraint_set5_flag`, and `level_idc` applicable for the current scalable layer representation are not indicated in the scalability information SEI message. + +**`bitrate_info_present_flag[ i ]`** equal to 1 specifies that the bit rate information for the current scalable layer representation is present in the scalability information SEI message. `bitrate_info_present_flag[ i ]` equal to 0 specifies that the bit rate information for the current scalable layer representation is not present in the scalability information SEI message. + +**`frm_rate_info_present_flag[ i ]`** equal to 1 specifies that the frame rate information for the current scalable layer representation is present in the scalability information SEI message. `frm_rate_info_present_flag[ i ]` equal to 0 specifies that the frame rate information for the current scalable layer representation is not present in the scalability information SEI message. + +**`frm_size_info_present_flag[ i ]`** equal to 1 specifies that the frame size information for the current scalable layer representation is present in the scalability information SEI message. `frm_size_info_present_flag[ i ]` equal to 0 specifies that the presence of the frame size information for the current scalable layer representation in the scalability information SEI message is specified by `iroi_division_info_present_flag[ i ]`. + +**`layer_dependency_info_present_flag[ i ]`** equal to 1 specifies that one or more syntax elements `dependent_layer_id_delta_minus1[ i ][ j ]` indicating the layer dependency information for the current scalable layer are present in the scalability information SEI message. `layer_dependency_info_present_flag[ i ]` equal to 0 specifies that, for the current scalable layer, the syntax element `layer_dependency_info_src_layer_id_delta[ i ]` is present in the scalability information SEI message. + +**`parameter_sets_info_present_flag[ i ]`** equal to 1 specifies that the values of `seq_parameter_set_id` of the sequence parameter sets and subset sequence parameter sets and the values of `pic_parameter_set_id` of the picture parameter sets that are referred to in the primary coded VCL NAL units of the current scalable layer representation are present in the scalability information SEI message. `parameter_sets_info_present_flag[ i ]` equal to 0 specifies that, for the current scalable layer, the syntax element `parameter_sets_info_src_layer_id_delta[ i ]` is present in the scalability information SEI message. + +**`bitstream_restriction_info_present_flag[ i ]`** equal to 1 specifies that the bitstream restriction information for the current scalable layer representation is present in the scalability information SEI message. + +bitstream\_restriction\_info\_present\_flag[ i ] equal to 0 specifies that the bitstream restriction information for the current scalable layer representation is not present in the scalability information SEI message. + +**exact\_inter\_layer\_pred\_flag[ i ]** equal to 1 indicates that, for all primary coded VCL NAL units with no\_inter\_layer\_pred\_flag equal to 0 of the current scalable layer representation, the reference layer representation (specified by the syntax elements ref\_layer\_dq\_id) that is used for inter-layer prediction in the decoding process, as specified in clause F.8, is the same as the reference layer representation that was used during encoding. exact\_inter\_layer\_pred\_flag[ i ] equal to 0 indicates that, for the primary coded VCL NAL units with no\_inter\_layer\_pred\_flag equal to 0 of the current scalable layer representation, the reference layer representations that are used for inter-layer prediction in the decoding process may or may not be the same as the reference layer representations that were used during encoding. + +NOTE 8 – A mismatch between the reference layer representation that is used for inter-layer prediction in the decoding process and the reference layer representation that was used during encoding may be a result of a bitstream adaption, in which one or more layer representations that are referred to in inter-layer prediction are removed from the bitstream, any of the primary coded VCL NAL units that refer to any of the removed layer representations by inter-layer prediction is not removed from the bitstream, and the value of the syntax elements ref\_layer\_dq\_id in the primary coded VCL NAL units that refer to any of the removed layer representations is modified in order to obtain a bitstream conforming to this Recommendation | International Standard. + +exact\_inter\_layer\_pred\_flag[ i ] should be equal to 1. When the current scalable layer representation does not contain any primary coded VCL NAL unit with no\_inter\_layer\_pred\_flag equal to 0, exact\_inter\_layer\_pred\_flag[ i ] shall be equal to 1. + +**exact\_sample\_value\_match\_flag[ i ]** indicates whether the values of decoded samples for decoding the representation of the current sub-picture scalable layer (when sub\_pic\_layer\_flag[ i ] is equal to 1) or any particular IROI within the current scalable layer representation (when iroi\_division\_info\_present\_flag[ i ] is equal to 1) are identical to the values of the same decoded samples that would be obtained by decoding all layer representations, of the primary coded pictures inside the target access unit set, that have DQId less than or equal to $16 * \text{dependency\_id}[ i ] + \text{quality\_id}[ i ]$ and temporal\_id less than or equal to temporal\_id[ i ]. + +With picSubset being the set of the primary coded pictures of the current scalable layer representation that contain any VCL NAL unit with dependency\_id equal to dependency\_id[ i ], the following applies: + +- If sub\_pic\_layer\_flag[ i ] is equal to 1 (iroi\_division\_info\_present\_flag[ i ] is equal to 0), the following is specified: + 1. Let picLRepSubset be the set of primary coded pictures that is formed by all the layer representations, of the target access unit set, that contain any primary coded VCL NAL unit present in the set of pictures picSubset. + +NOTE 9 – picSubset is a proper subset of picLRepSubset. picSubset only contains the primary coded slices of the current (sub-picture) scalable layer representation, picLRepSubset contains all primary coded slices of the corresponding layer representations (i.e. the complete layer representations that contain any slice of picSubset). + +2. exact\_sample\_value\_match\_flag[ i ] equal to 1 indicates that the value of each decoded sample inside the sub-picture area for decoding the picture set picSubset is identical to the value of the same decoded sample that would be obtained by decoding the picture set picLRepSubset. +3. exact\_sample\_value\_match\_flag[ i ] equal to 0 indicates that the value of any decoded sample inside the sub-picture area for decoding the picture set picSubset may or may not be identical to the value of the same decoded sample that would be obtained by decoding the picture set picLRepSubset. + +- Otherwise (sub\_pic\_layer\_flag[ i ] is equal to 0 and iroi\_division\_info\_present\_flag[ i ] is equal to 1), for each particular IROI, the following is specified: + +1. Let picIROISubset be the set of primary coded VCL NAL units that is obtained by removing all the VCL NAL units from the set of pictures picSubset that do not cover any macroblock inside the IROI. +2. exact\_sample\_value\_match\_flag[ i ] equal to 1 indicates that the value of each decoded sample inside the IROI for decoding the picture set picSubset is identical to the value of the same decoded sample that would be obtained by decoding the picture set picIROISubset. +3. exact\_sample\_value\_match\_flag[ i ] equal to 0 indicates that the value of any decoded sample inside the IROI for decoding the picture set picSubset may or may not be identical to the value of the same decoded sample that would be obtained by decoding the picture set picIROISubset. + +NOTE 10 – In the above specification, the decoding result for picIROISubset is the decoding result that would be obtained for the IROI by following the decoding process in clause F.8 but ignoring the constraint that the layer representations with quality\_id equal to 0 of primary coded pictures must cover all macroblocks of the corresponding layer pictures. + +NOTE 11 – When disable\_deblocking\_filter\_idc is equal to 1, 2, or 5 in all primary coded slices of the current scalable layer representation that have dependency\_id equal to dependency\_id[ i ], exact\_sample\_value\_match\_flag should be equal to 1. + +**layer\_conversion\_flag[ i ]** equal to 1 indicates that the representation of the current scalable layer can be converted into an alternative set of access units that conforms to one or more of the profiles specified in Annex A and gives exactly the + +same decoding result as the current scalable layer representation and that this conversion can be done without full reconstruction and re-encoding. `layer_conversion_flag[ i ]` equal to 0 indicates that such a conversion of the current scalable layer representation may or may not be possible. + +**layer\_output\_flag[ i ]** equal to 1 indicates that the decoding result for the current scalable layer representation is intended for output. `layer_output_flag[ i ]` equal to 0 indicates that the decoding result for the current scalable layer representation is not intended for output. + +NOTE 12 – The decoding result for a scalable layer representation with `layer_output_flag[ i ]` equal to 0 may be inappropriate for output due to its low visual quality. + +**layer\_profile\_level\_idc[ i ]** indicates the conformance point of the representation of the current scalable layer. `layer_profile_level_idc[ i ]` is the exact copy of the three bytes comprised of `profile_idc`, `constraint_set0_flag`, `constraint_set1_flag`, `constraint_set2_flag`, `constraint_set3_flag`, `constraint_set4_flag`, `constraint_set5_flag`, `reserved_zero_2bits` and `level_idc`, as if these syntax elements were used to specify the profile and level conformance of the representation of the current scalable layer. + +NOTE 13 – The representation of a sub-picture scalable layer (`sub_pic_layer_flag[ i ]` is equal to 1) does not conform to this Recommendation | International Standard, since the primary coded VCL NAL units with `quality_id` equal to 0 that belong to a sub-picture scalable layer representation do not cover all macroblocks of the layer pictures with `dependency_id` equal to `dependency_id[ i ]` and `quality_id` equal to 0. For sub-picture scalable layers, the violation of the constraint that the layer representations with `quality_id` equal to 0 of primary coded pictures must cover all macroblocks of the corresponding layer pictures is ignored in the conformance point indication by `layer_profile_level_idc[ i ]`. + +**avg\_bitrate[ i ]** indicates the average bit rate of the representation of the current scalable layer. The average bit rate for the representation of the current scalable layer in bits per second is given by `BitRateBPS( avg_bitrate[ i ] )` with the function `BitRateBPS( )` being specified by: + +$$\text{BitRateBPS}(x) = (x \& (2^{14} - 1)) * 10^{(2+(x \gg 14))} \quad (\text{F-370})$$ + +The average bit rate is derived according to the access unit removal time specified in Annex C of this Recommendation | International Standard. In the following, `bTotal` is the number of bits in all NAL units of the current scalable layer representation, `t1` is the removal time (in seconds) of the access unit associated with the scalability information SEI message, and `t2` is the removal time (in seconds) of the last access unit (in decoding order) of the target access unit set. + +With `x` specifying the value of `avg_bitrate[ i ]`, the following applies: + +- If `t1` is not equal to `t2`, the following condition shall be true: + +$$(x \& (2^{14} - 1)) == \text{Round}(b\text{Total} \div ((t_2 - t_1) * 10^{(2+(x \gg 14))})) \quad (\text{F-371})$$ + +- Otherwise (`t1` is equal to `t2`), the following condition shall be true: + +$$(x \& (2^{14} - 1)) == 0 \quad (\text{F-372})$$ + +**max\_bitrate\_layer[ i ]** indicates an upper bound for the bit rate of the current scalable layer in any fixed-size time window, specified by `max_bitrate_calc_window[ i ]`, of access unit removal time as specified in Annex C. The upper bound for the bit rate of the current scalable layer in bits per second is given by `BitRateBPS( max_bitrate_layer[ i ] )` with the function `BitRateBPS( )` being specified in Equation F-370. The bit rate values are derived according to the access unit removal time specified in Annex C of this Recommendation | International Standard. In the following, `t1` is any point in time (in seconds), `t2` is set equal to `t1 + max_bitrate_calc_window[ i ] ÷ 100`, and `bTotal` is the number of bits in all NAL units of the current scalable layer that belong to access units with a removal time greater than or equal to `t1` and less than `t2`. With `x` specifying the value of `max_bitrate_layer[ i ]`, the following condition shall be obeyed for all values of `t1`: + +$$(x \& (2^{14} - 1)) \geq b\text{Total} \div ((t_2 - t_1) * 10^{(2+(x \gg 14))}) \quad (\text{F-373})$$ + +**max\_bitrate\_layer\_representation[ i ]** indicates an upper bound for the bit rate of the current scalable layer representation in any fixed-size time window, specified by `max_bitrate_calc_window[ i ]`, of access unit removal time as specified in Annex C. The upper bound for the bit rate of the current scalable layer representation in bits per second is given by `BitRateBPS( max_bitrate_layer_representation[ i ] )` with the function `BitRateBPS( )` being specified in Equation F-370. The bit rate values are derived according to the access unit removal time specified in Annex C of this Recommendation | International Standard. In the following, `t1` is any point in time (in seconds), `t2` is set equal to `t1 + max_bitrate_calc_window[ i ] ÷ 100`, and `bTotal` is the number of bits in all NAL units of the current scalable layer representation that belong to access units with a removal time greater than or equal to `t1` and less than `t2`. With `x` specifying the value of `max_bitrate_layer_representation[ i ]`, the condition specified in Equation F-373 shall be obeyed. + +**max\_bitrate\_calc\_window[ i ]** specifies the size of the time window that is used for calculating the upper bounds for the bit rate of the current scalable layer (indicated by `max_bitrate_layer[ i ]`) and the bit rate of the current scalable layer representation (indicated by `max_bitrate_layer_representation[ i ]`) in units of 1/100 second. + +**constant\_frm\_rate\_idc[ i ]** indicates whether the frame rate of the current scalable layer representation is constant. In the following, a temporal segment `tSeg` is any set of two or more consecutive access units, in decoding order, of the + +current scalable layer representation, $fTotal( tSeg )$ is the number of frames, complementary field pairs, and non-paired fields in the temporal segment $tSeg$ , $t_1( tSeg )$ is the removal time (in seconds) of the first access unit (in decoding order) of the temporal segment $tSeg$ , $t_2( tSeg )$ is the removal time (in seconds) of the last access unit (in decoding order) of the temporal segment $tSeg$ , and $avgFR( tSeg )$ is the average frame rate in the temporal segment $tSeg$ , which is given by: + +$$avgFR( tSeg ) == Round( fTotal( tSeg ) * 256 \div ( t_2( tSeg ) - t_1( tSeg ) ) ) \quad (F-374)$$ + +If the current scalable layer representation does only contain one access unit or the value of $avgFR( tSeg )$ is constant over all temporal segments of the scalable layer representation, the frame rate is constant; otherwise, the frame rate is not constant. $constant\_frm\_rate\_idc[ i ]$ equal to 0 indicates that the frame rate of the current scalable layer representation is not constant. $constant\_frm\_rate\_idc[ i ]$ equal to 1 indicates that the frame rate of the current scalable layer representation is constant. $constant\_frm\_rate\_idc[ i ]$ equal to 2 indicates that the frame rate of the current scalable layer representation may or may not be constant. The value of $constant\_frm\_rate\_idc[ i ]$ shall be in the range of 0 to 2, inclusive. + +$avg\_frm\_rate[ i ]$ indicates the average frame rate, in units of frames per 256 seconds, of the representation of the current scalable layer. With $fTotal$ being the number of frames, complementary field pairs, and non-paired fields in the current scalable layer representation, $t_1$ being the removal time (in seconds) of the access unit associated with the scalability information SEI message, and $t_2$ being the removal time (in seconds) of the last access unit (in decoding order) of the target access unit set, the following applies: + +- If $t_1$ is not equal to $t_2$ , the following condition shall be true: + +$$avg\_frm\_rate[ i ] == Round( fTotal * 256 \div ( t_2 - t_1 ) ) \quad (F-375)$$ + +- Otherwise ( $t_1$ is equal to $t_2$ ), the following condition shall be true: + +$$avg\_frm\_rate[ i ] == 0 \quad (F-376)$$ + +$frm\_width\_in\_mbs\_minus1[ i ]$ and $frm\_height\_in\_mbs\_minus1[ i ]$ indicate the width and height, respectively, of the decoded pictures for the current scalable layer representation (when $sub\_pic\_layer\_flag[ i ]$ is equal to 0) or the sub-picture area inside the decoded pictures for the current sub-picture scalable layer (when $sub\_pic\_layer\_flag[ i ]$ is equal to 1). When $frame\_mbs\_only\_flag$ is equal to 0 for any primary coded VCL NAL unit of the current scalable layer, $( frm\_height\_in\_mbs\_minus1[ i ] + 1 ) \% 2$ shall be equal to 0. + +Let $picSubset$ be the set of the primary coded pictures inside the current scalable layer representation that contain any VCL NAL unit with $dependency\_id$ equal to $dependency\_id[ i ]$ . For decoding the picture set $picSubset$ , the following applies: + +- If $sub\_pic\_layer\_flag[ i ]$ is equal to 0, the width and height of a decoded picture are equal to $frm\_width\_in\_mbs\_minus1[ i ] + 1$ and $( ( frm\_height\_in\_mbs\_minus1[ i ] + 1 ) / ( 1 + field\_pic\_flag ) )$ macroblocks, respectively, with $field\_pic\_flag$ being the slice header syntax element in the slices with $dependency\_id$ equal to $dependency\_id[ i ]$ of the corresponding primary coded picture. The width and height of the decoded pictures that are indicated by $frm\_width\_in\_mbs\_minus1[ i ]$ and $frm\_height\_in\_mbs\_minus1[ i ]$ , respectively, shall be identical to the width and height of the decoded pictures that are specified by the syntax elements $pic\_width\_in\_mbs\_minus1$ and $pic\_height\_in\_map\_units\_minus1$ , respectively, of the SVC sequence parameter sets referenced in the corresponding coded slice NAL units with $dependency\_id$ equal to $dependency\_id[ i ]$ . +- Otherwise ( $sub\_pic\_layer\_flag[ i ]$ is equal to 1), the width and height of the sub-picture area inside a decoded picture are equal to $frm\_width\_in\_mbs\_minus1[ i ] + 1$ and $( ( frm\_height\_in\_mbs\_minus1[ i ] + 1 ) / ( 1 + field\_pic\_flag ) )$ macroblocks, respectively, with $field\_pic\_flag$ being the slice header syntax element in the slices with $dependency\_id$ equal to $dependency\_id[ i ]$ of the corresponding primary coded picture. The sub-picture area that is indicated by $frm\_width\_in\_mbs\_minus1[ i ]$ and $frm\_height\_in\_mbs\_minus1[ i ]$ shall be less than the area of the decoded pictures, which is specified by the syntax elements $pic\_width\_in\_mbs\_minus1$ and $pic\_height\_in\_map\_units\_minus1$ of the SVC sequence parameter sets referenced in the corresponding coded slice NAL units with $dependency\_id$ equal to $dependency\_id[ i ]$ . + +The variable $FrmWidthInMbs[ i ]$ is set equal to $( frm\_width\_in\_mbs\_minus1[ i ] + 1 )$ . The variable $FrmHeightInMbs[ i ]$ is set equal to $( frm\_height\_in\_mbs\_minus1[ i ] + 1 )$ . The variable $FrmSizeInMbs[ i ]$ is set equal to $( FrmWidthInMbs[ i ] * FrmHeightInMbs[ i ] )$ . + +$base\_region\_layer\_id[ i ]$ indicates the layer identifier $layer\_id[ b ]$ of the scalable layer $b$ that represents the base region for the current scalable layer as specified in the following. The value of $base\_region\_layer\_id[ i ]$ shall be in the range of 0 to 2047, inclusive. + +Let $picSubset$ be the set of the primary coded pictures, inside the current scalable layer representation, that contain any VCL NAL unit with $dependency\_id$ equal to $dependency\_id[ i ]$ . Let $basePicSubset$ be the set of the primary coded pictures, inside the representation of the scalable layer $b$ with $layer\_id[ b ]$ equal to $base\_region\_layer\_id[ i ]$ , that contain + +any VCL NAL unit with dependency\_id equal to dependency\_id[ b ]. Depending on sub\_pic\_layer\_flag[ i ], the following applies: + +- If sub\_pic\_layer\_flag[ i ] is equal to 0, it is indicated that the decoded pictures for the picture set picSubset represent a subset of the areas that are represented by the decoded pictures for the picture set basePicSubset. The value of dependency\_id[ b ] for the scalable layer b shall be less than the value of dependency\_id[ i ] for the current scalable layer. The area that is represented by the decoded pictures for the picture set picSubset is also referred to as the region represented by the current scalable layer and the area represented by the corresponding decoded pictures for the picture set basePicSubset is also referred to as the base region for the current scalable layer. +- Otherwise (sub\_pic\_layer\_flag[ i ] is equal to 1), it is indicated that the sub-picture area inside the decoded pictures for the picture set picSubset represents a proper subset of the areas that are represented by the decoded pictures for the picture set basePicSubset. The value of dependency\_id[ b ] shall be equal to the value of dependency\_id[ i ] for the current sub-picture scalable layer. The area that is represented by the sub-picture area inside the decoded pictures for the picture set picSubset is also referred to as the region represented by the current scalable layer and the area represented by the corresponding decoded pictures for the picture set basePicSubset is also referred to as the base region for the current scalable layer. + +NOTE 14 – When sub\_pic\_layer\_flag[ i ] is equal to 1, the base region represents the area of the layer pictures with dependency\_id equal to dependency\_id[ i ]. + +The scalability information SEI message shall contain information for the scalable layer b with layer\_id[ b ] equal to base\_region\_layer\_id[ i ], the value of sub\_pic\_layer\_flag[ b ] for the scalable layer b shall be equal to 0, and the value of temporal\_id[ i ] for the scalable layer b shall be equal to the value of temporal\_id[ i ] for the current scalable layer. + +**dynamic\_rect\_flag[ i ]** equal to 1 indicates that the region represented by the current scalable layer representation is a dynamically changing rectangular subset of the base region. dynamic\_rect\_flag[ i ] equal to 0 indicates that the region represented by the current scalable layer representation is a fixed rectangular subset of the base region and is specified by the syntax elements horizontal\_offset[ i ], vertical\_offset[ i ], region\_width[ i ], and region\_height[ i ]. When sub\_pic\_layer\_flag[ i ] is equal to 1, dynamic\_rect\_flag[ i ] shall be equal to 0. + +**horizontal\_offset[ i ], vertical\_offset[ i ], region\_width[ i ], and region\_height[ i ]** indicate the position and size of the region represented by the current scalable layer in relation to its base region. + +Let picSubset be the set of the primary coded pictures, inside the current scalable layer representation, that contain any VCL NAL unit with dependency\_id equal to dependency\_id[ i ]. Let basePicSubset be the set of the primary coded pictures, inside the representation of the scalable layer b with layer\_id[ b ] equal to base\_region\_layer\_id[ i ], that contain any VCL NAL unit with dependency\_id equal to dependency\_id[ b ]. Depending on sub\_pic\_layer\_flag[ i ], the following applies: + +- If sub\_pic\_layer\_flag[ i ] is equal to 0, the top-left luma frame sample in the decoded pictures for picture set picSubset corresponds to the luma frame sample at the luma frame sample location ( horizontal\_offset[ i ], vertical\_offset[ i ] ) in the decoded pictures for the picture set basePicSubset. The region represented by the decoded pictures for picture set picSubset represents an area of (region\_width[ i ]x(region\_height[ i ])) luma frame samples in the decoded pictures for the picture set basePicSubset. When frame\_mbs\_only\_flag is equal to 0 for any primary coded VCL NAL unit of the current scalable layer, (vertical\_offset[ i ] % 2) and (region\_height[ i ] % 2) shall both be equal to 0. +- Otherwise (sub\_pic\_layer\_flag[ i ] is equal to 1), the top-left luma frame sample of the sub-picture area in the decoded pictures for picture set picSubset corresponds to the luma frame sample at the luma frame sample location ( horizontal\_offset[ i ], vertical\_offset[ i ] ) in the decoded pictures for the picture set basePicSubset. The region represented by the sub-picture area in the decoded pictures for picture set picSubset represents an area of (region\_width[ i ]x(region\_height[ i ])) luma frame samples in the decoded pictures for the picture set basePicSubset. (horizontal\_offset[ i ] % 16) and (region\_width[ i ] % 16) shall both be equal to 0, and depending on the values of frame\_mbs\_only\_flag for the primary coded VCL NAL units of the current scalable layer, the following applies: + - If frame\_mbs\_only\_flag is equal to 1 for all primary coded VCL NAL units of the current scalable layer, (vertical\_offset[ i ] % 16) and (region\_height[ i ] % 16) shall both be equal to 0. + - Otherwise (frame\_mbs\_only\_flag is equal to 0 for any primary coded VCL NAL units of the current scalable layer), (vertical\_offset[ i ] % 32) and (region\_height[ i ] % 32) shall both be equal to 0. + +When sub\_pic\_layer\_flag[ i ] is equal to 1 and frm\_size\_info\_present\_flag[ i ] is equal to 1, the values of region\_width[ i ] and region\_height[ i ] shall be equal to (FrmWidthInMbs[ i ] << 4) and (FrmHeightInMbs[ i ] << 4), respectively. + +**roi\_id[ i ]** specifies a region-of-interest identifier for the region represented by the current sub-picture scalable layer, which may be used for identifying the purpose of the current sub-picture scalable layer by an application. The value of roi\_id[ i ] shall be in the range of 0 to 63, inclusive. + +Let layerIdA and layerIdB be the layer identifiers of two scalable layers A and B, respectively, both of which having sub\_pic\_layer\_flag[ i ] equal to 1, and roiIdA and roiIdB be the region-of-interest identifiers of the scalable layers A and B, respectively. When layerIdA is less than layerIdB, roiIdA shall not be greater than roiIdB. + +**iroi\_grid\_flag[ i ]** specifies how the IROI division information is indicated for the current scalable layer. iroi\_grid\_flag[ i ] equal to 1 indicates that all IROIs for the current scalable layer are aligned on a fixed-size grid as specified in the following and that the syntax elements grid\_width\_in\_mbs\_minus1[ i ] and grid\_height\_in\_mbs\_minus1[ i ] for the current scalable layer are present in the scalability information SEI message. iroi\_grid\_flag[ i ] equal to 0 indicates that the IROIs for the current scalable layer may or may not be aligned on a fixed-size grid. + +All scalable layers with the same value of dependency\_id[ i ] for which scalability information is present in the scalability information SEI message and for which iroi\_division\_info\_present\_flag[ i ] is equal to 1 shall have the same value of iroi\_grid\_flag[ i ]. + +**grid\_width\_in\_mbs\_minus1[ i ]** and **grid\_height\_in\_mbs\_minus1[ i ]** indicate the size of the IROI grid for the current scalable layer. When frame\_mbs\_only\_flag is equal to 0 for any primary coded VCL NAL unit of the current scalable layer, ( grid\_height\_in\_mbs\_minus1[ i ] + 1 ) % 2 shall be equal to 0. + +The value of grid\_width\_in\_mbs\_minus1[ i ] shall be in the range of 0 to FrmWidthInMbs[ i ] - 1, inclusive. The value of grid\_height\_in\_mbs\_minus1[ i ] shall be in the range of 0 to FrmHeightInMbs[ i ] - 1, inclusive. + +Let numX and numY be equal to ( FrmWidthInMbs[ i ] + grid\_width\_in\_mbs\_minus1[ i ] ) / ( grid\_width\_in\_mbs\_minus1[ i ] + 1 ) and ( FrmHeightInMbs[ i ] + grid\_height\_in\_mbs\_minus1[ i ] ) / ( grid\_height\_in\_mbs\_minus1[ i ] + 1 ), respectively. + +The layer pictures with dependency\_id equal to dependency\_id[ i ] are partitioned into (numX \* numY) IROIs. Let ( xI[ k ], yI[ k ] ) be the location of the top-left luma sample of the k-th IROI relative to the top-left luma sample of the layer picture and let w[ k ] and h[ k ] be the width and height, in luma samples, of the k-th IROI in the layer picture. With field\_pic\_flag being the slice header syntax element for a particular layer picture with dependency\_id equal to dependency\_id[ i ], the location of the top-left luma sample and the width and height of the k-th IROI, with k = 0..(numX \* numY - 1), are given by + +$$xI[ k ] = 16 * ( k \% numX ) * ( grid\_width\_in\_mbs\_minus1[ i ] + 1 ) \quad (F-377)$$ + +$$yI[ k ] = 16 * ( k / numX ) * ( grid\_height\_in\_mbs\_minus1[ i ] + 1 ) / ( 1 + field\_pic\_flag ) \quad (F-378)$$ + +$$w[ k ] = \text{Min}( 16 * ( grid\_width\_in\_mbs\_minus1[ i ] + 1 ), 16 * \text{FrmWidthInMbs}[ i ] - xI[ k ] ) \quad (F-379)$$ + +$$h[ k ] = \text{Min}( 16 * ( grid\_height\_in\_mbs\_minus1[ i ] + 1 ) / ( 1 + field\_pic\_flag ), 16 * \text{FrmHeightInMbs}[ i ] / ( 1 + field\_pic\_flag ) - yI[ k ] ) \quad (F-380)$$ + +All scalable layers with the same value of dependency\_id[ i ] for which scalability information is present in the scalability information SEI message and for which iroi\_division\_info\_present\_flag[ i ] is equal to 1 and iroi\_grid\_flag[ i ] is equal to 1 shall have the same values of grid\_width\_in\_mbs\_minus1[ i ] and grid\_height\_in\_mbs\_minus1[ i ]. + +**num\_rois\_minus1[ i ]** plus 1 indicates the number of IROIs for the current scalable layer. + +Depending on the primary coded VCL NAL units of the current scalable layer, the following applies: + +- If frame\_mbs\_only\_flag is equal to 1 for all primary coded VCL NAL units of the current scalable layer, the value of num\_rois\_minus1[ i ] shall be in the range of 0 to FrmSizeInMbs[ i ] - 1, inclusive. +- Otherwise (frame\_mbs\_only\_flag is equal to 0 for any primary coded VCL NAL unit of the current scalable layer), the value of num\_rois\_minus1[ i ] shall be in the range of 0 to FrmSizeInMbs[ i ] / 2 - 1, inclusive. + +All scalable layers with the same value of dependency\_id[ i ] for which scalability information is present in the scalability information SEI message and for which iroi\_division\_info\_present\_flag[ i ] is equal to 1 and iroi\_grid\_flag[ i ] is equal to 0 shall have the same value of num\_rois\_minus1[ i ]. + +**first\_mb\_in\_roi[ i ][ j ]** indicates the macroblock address of the first macroblock in the j-th IROI for the current scalable layer. The value of first\_mb\_in\_roi[ i ][ j ] shall be in the range of 0 to FrmSizeInMbs[ i ] - 1, inclusive. When j is greater than 0, the value of first\_mb\_in\_roi[ i ][ j ] shall not be equal to any of the values of first\_mb\_in\_roi[ i ][ k ] with k = 0..(j - 1). + +The variables firstMbY and firstMbInROIId are derived as + +$$\text{firstMbY} = \text{first\_mb\_in\_roi}[ i ][ j ] - ( \text{first\_mb\_in\_roi}[ i ][ j ] \% \text{FrmWidthInMbs}[ i ] ) \quad (F-381)$$ + +$$\text{firstMbInROIId} = ( \text{firstMbY} \gg 1 ) + ( \text{first\_mb\_in\_roi}[ i ][ j ] \% \text{FrmWidthInMbs}[ i ] ) \quad (F-382)$$ + +When `frame_mbs_only_flag` is equal to 0 for any primary coded VCL NAL unit of the current scalable layer, `(firstMbY % 2)` shall be equal to 0. + +For each dependency representation that contains any primary coded VCL NAL unit of the current scalable layer, the following applies: + +- If `field_pic_flag` is equal to 0 and `MbaffFrameFlag` is equal to 0 for the dependency representation, the value of `first_mb_in_roi[i][j]` shall be equal to the syntax element `first_mb_in_slice` in the slice that belongs to the dependency representation and covers the top-left macroblock of the j-th IROI. +- Otherwise (`field_pic_flag` is equal to 1 or `MbaffFrameFlag` is equal to 1 for the dependency representation), the value of `firstMbInROIId` shall be equal to the syntax element `first_mb_in_slice` in the slice that belongs to the dependency representation and covers the top-left macroblock of the j-th IROI. + +`roi_width_in_mbs_minus1[i][j]` and `roi_height_in_mbs_minus1[i][j]` specify the size of the j-th IROI for the current scalable layer. When `frame_mbs_only_flag` is equal to 0 for any primary coded VCL NAL unit of the current scalable layer, `(roi_height_in_mbs_minus1[i][j] + 1) % 2` shall be equal to 0. + +The value of `roi_width_in_mbs_minus1[i][j]` shall be in the range of 0 to `(FrmWidthInMbs[i] - 1 - (first_mb_in_roi[i][j] % FrmWidthInMbs[i]))`, inclusive. The value of `roi_height_in_mbs_minus1[i][j]` shall be in the range of 0 to `(FrmHeightInMbs[i] - 1 - (firstMbY / FrmWidthInMbs[i]))`, inclusive. + +With `field_pic_flag` being the slice header syntax element for a particular layer picture with `dependency_id` equal to `dependency_id[i]`, the width and height of the j-th IROI in the layer pictures with `dependency_id` equal to `dependency_id[i]` are equal to `16 * (roi_width_in_mbs_minus1[i][j] + 1)` and `16 * (roi_height_in_mbs_minus1[i][j] + 1) / (1 + field_pic_flag)`, respectively, in units of luma samples. + +All scalable layers with the same value of `dependency_id[i]` for which scalability information is present in the scalability information SEI message and for which `iroi_division_info_present_flag[i]` is equal to 1 and `iroi_grid_flag[i]` is equal to 0 shall have the same values of `first_mb_in_roi[i][j]`, `roi_width_in_mbs_minus1[i][j]`, and `roi_height_in_mbs_minus1[i][j]` with j in the range of 0 to `num_rois_minus1[i]`, inclusive. + +`num_directly_dependent_layers[i]` specifies the number of the syntax elements `directly_dependent_layer_id_delta_minus1[i][j]` that are present for the current scalable layer. The value of `num_directly_dependent_layers` shall be in the range of 0 to 255, inclusive. + +`directly_dependent_layer_id_delta_minus1[i][j]` plus 1 indicates the difference between the value of `layer_id[i]` for the current scalable layer and the layer identifier of a particular scalable layer, on which the current scalable layer directly depends. The value of `directly_dependent_layer_id_delta_minus1[i][j]` shall be in the range of 0 to `layer_id[i] - 1`, inclusive. The layer identifier of the particular scalable layer, on which the current scalable layer directly depends, is equal to `layer_id[i] - directly_dependent_layer_id_delta_minus1[i][j] - 1`. The scalability information SEI message shall contain information for a scalable layer b with `layer_id[b]` equal to `layer_id[i] - directly_dependent_layer_id_delta_minus1[i][j] - 1` and this information shall not contain a value of `layer_dependency_info_src_layer_id_delta[i]` equal to 0. + +Let `setOfDepLayers` be the set union of the representations of the scalable layers b that have `layer_id[b]` equal to `layer_id[i] - directly_dependent_layer_id_delta_minus1[i][j] - 1`, with `j = 0..num_directly_dependent_layers[i] - 1`. When `layer_dependency_info_present_flag[i]` is equal to 1, the set `setOfDepLayers` shall not contain any scalable layer, on which the current scalable layer does not directly or indirectly depends and the current scalable layer shall not depend on any scalable layer that is not included in the set `setOfDepLayers`. + +`layer_dependency_info_src_layer_id_delta[i]` greater than 0 indicates that the current scalable layer has the same layer dependency information as the scalable layer with layer identifier equal to `layer_id[i] - layer_dependency_info_src_layer_id_delta[i]`. `layer_dependency_info_src_layer_id_delta[i]` equal to 0 specifies that the layer dependency information of the current scalable layer is not present in the scalability information SEI message. The value of `layer_dependency_info_src_layer_id_delta[i]` shall be in the range of 0 to `layer_id[i]`, inclusive. When `layer_dependency_info_src_layer_id_delta[i]` is greater than 0, the scalability information SEI message shall contain information for a scalable layer b with `layer_id[b]` equal to `layer_id[i] - layer_dependency_info_src_layer_id_delta[i]` and this information shall not contain a value of `layer_dependency_info_src_layer_id_delta[b]` equal to 0. + +When `layer_dependency_info_present_flag[i]` is equal to 0 and `layer_dependency_info_src_layer_id_delta[i]` is greater than 0, the set of scalable layers on which the current scalable layer depends shall be identical to the set of layers on which the scalable layer b with `layer_id[b]` equal to `layer_id[i] - layer_dependency_info_src_layer_id_delta[i]` depends. + +NOTE 15 – When `layer_dependency_info_src_layer_id_delta[i]` equal to 0 is not present for the current scalable layer, the representation of the current scalable layer is specified by the syntax element `layer_dependency_info_src_layer_id_delta[i]` + +or by the syntax elements `directly_dependent_layer_id_delta_minus1[ i ][ j ]`, with `j = 0..num_directly_dependent_layers[ i ] - 1`. + +NOTE 16 – A change for the layer dependency information may be signalled by the presence of one or more layer dependency change SEI messages. When a scalability information SEI message specifies that a scalable layer A does not directly or indirectly depend on a scalable layer B, this relationship applies to the complete target access unit set. When a scalability information SEI message specifies that a scalable layer A does directly or indirectly depend on a scalable layer B, a following layer dependency change SEI message may indicate that this dependency does not apply for a subset of the target access unit set. + +**num\_seq\_parameter\_sets[ i ]** indicates the number of different sequence parameter sets that are referred to by the primary coded VCL NAL units of the current scalable layer representation. The value of `num_seq_parameter_sets[ i ]` shall be in the range of 0 to 32, inclusive. + +**seq\_parameter\_set\_id\_delta[ i ][ j ]** indicates the smallest value of the `seq_parameter_set_id` of any sequence parameter set required for decoding the representation of the current scalable layer, if `j` is equal to 0. Otherwise (`j` is greater than 0), `seq_parameter_set_id_delta[ i ][ j ]` indicates the difference between the value of the `seq_parameter_set_id` of the `j`-th required sequence parameter set and the value of the `seq_parameter_set_id` of the `(j - 1)`-th required sequence parameter set for decoding the representation of the current scalable layer. The value of `seq_parameter_set_id_delta[ i ][ j ]` shall not be greater than 31. When `j` is greater than 0, the value of `seq_parameter_set_id_delta[ i ][ j ]` shall not be equal to 0. When `parameter_sets_info_present_flag[ i ]` is equal to 1, the primary coded VCL NAL units of the current scalable layer representation shall not refer to any sequence parameter set for which the value of `seq_parameter_set_id` is not indicated by the syntax elements `seq_parameter_set_id_delta[ i ][ j ]` for the current scalable layer and the syntax elements `seq_parameter_set_id_delta[ i ][ j ]` for the current scalable layer shall not indicate any sequence parameter set that is not referenced in any primary coded VCL NAL unit of the current scalable layer representation. + +**num\_subset\_seq\_parameter\_sets[ i ]** indicates the number of different subset sequence parameter sets that are referred to by the primary coded VCL NAL units of the current scalable layer representation. The value of `num_subset_seq_parameter_sets[ i ]` shall be in the range of 0 to 32, inclusive. + +**subset\_seq\_parameter\_set\_id\_delta[ i ][ j ]** indicates the smallest value of the `seq_parameter_set_id` of any subset sequence parameter set required for decoding the representation of the current scalable layer, if `j` is equal to 0. Otherwise (`j` is greater than 0), `subset_seq_parameter_set_id_delta[ i ][ j ]` indicates the difference between the value of the `seq_parameter_set_id` of the `j`-th required subset sequence parameter set and the value of the `seq_parameter_set_id` of the `(j - 1)`-th required subset sequence parameter set for decoding the representation of the current scalable layer. The value of `subset_seq_parameter_set_id_delta[ i ][ j ]` shall not be greater than 31. When `j` is greater than 0, the value of `subset_seq_parameter_set_id_delta[ i ][ j ]` shall not be equal to 0. When `parameter_sets_info_present_flag[ i ]` is equal to 1, the primary coded VCL NAL units of the current scalable layer representation shall not refer to any subset sequence parameter set for which the value of `seq_parameter_set_id` is not indicated by the syntax elements `subset_seq_parameter_set_id_delta[ i ][ j ]` for the current scalable layer and the syntax elements `subset_seq_parameter_set_id_delta[ i ][ j ]` for the current scalable layer shall not indicate any subset sequence parameter set that is not referenced in any primary coded VCL NAL unit of the current scalable layer representation. + +**num\_pic\_parameter\_sets\_minus1[ i ]** plus 1 indicates the number of different picture parameter sets that are referred to by the primary coded VCL NAL units of the current scalable layer representation. The value of `num_pic_parameter_sets_minus1[ i ]` shall be in the range of 0 to 255, inclusive. + +**pic\_parameter\_set\_id\_delta[ i ][ j ]** indicates the smallest value of the `pic_parameter_set_id` of any picture parameter set required for decoding the representation of the current scalable layer, if `j` is equal to 0. Otherwise (`j` is greater than 0), `pic_parameter_set_id_delta[ i ][ j ]` indicates the difference between the value of the `pic_parameter_set_id` of the `j`-th required picture parameter set and the value of the `pic_parameter_set_id` of the `(j - 1)`-th required picture parameter set for decoding the representation of the current scalable layer. The value of `pic_parameter_set_id_delta[ i ][ j ]` shall not be greater than 255. When `j` is greater than 0, the value of `pic_parameter_set_id_delta[ i ][ j ]` shall not be equal to 0. When `parameter_sets_info_present_flag[ i ]` is equal to 1, the primary coded VCL NAL units of the current scalable layer representation shall not refer to any picture parameter set for which the value of `pic_parameter_set_id` is not indicated by the syntax elements `pic_parameter_set_id_delta[ i ][ j ]` for the current scalable layer and the syntax elements `pic_parameter_set_id_delta[ i ][ j ]` for the current scalable layer shall not indicate any picture parameter set that is not referenced in any primary coded VCL NAL unit of the current scalable layer representation. + +**parameter\_sets\_info\_src\_layer\_id\_delta[ i ]** greater than 0 indicates that the values of `seq_parameter_set_id` of the sequence parameter sets and subset sequence parameter sets and the values of `pic_parameter_set_id` of the picture parameter sets that are referred to by the primary coded VCL NAL units of the current scalable layer representation are the same as those that are referred to by the primary coded VCL NAL units of the representation of the scalable layer `b` with the layer identifier `layer_id[ b ]` equal to `layer_id[ i ] - parameter_sets_info_src_layer_id_delta[ i ]`. When `parameter_sets_info_src_layer_id_delta[ i ]` is greater than 0, the scalability information SEI message shall contain information for a scalable layer `b` with `layer_id[ b ]` equal to `layer_id[ i ] - parameter_sets_info_src_layer_id_delta[ i ]` and this information shall not contain a value of `parameter_sets_info_src_layer_id_delta[ b ]` equal to 0. + +`parameter_sets_info_src_layer_id_delta[ i ]` equal to 0 indicates that the values of `seq_parameter_set_id` of the sequence parameter sets and subset sequence parameter sets and the values of `pic_parameter_set_id` of the picture parameter sets that are referred to by the primary coded VCL NAL units of the current scalable layer representation are not indicated in the scalability information SEI message. + +The value of `parameter_sets_info_src_layer_id_delta[ i ]` shall be in the range of 0 to `layer_id[ i ]`, inclusive. + +**`motion_vectors_over_pic_boundaries_flag[ i ]`** indicates the value of `motion_vectors_over_pic_boundaries_flag`, as specified in clause E.2.1, that applies to the current scalable layer representation. + +**`max_bytes_per_pic_denom[ i ]`** indicates the value of `max_bytes_per_pic_denom`, as specified in clause E.2.1, that applies to the current scalable layer representation. + +**`max_bits_per_mb_denom[ i ]`** indicates the value of `max_bits_per_mb_denom`, as specified in clause E.2.1, that applies to the current scalable layer representation. + +**`log2_max_mv_length_horizontal[ i ]`** and **`log2_max_mv_length_vertical[ i ]`** indicate the values of `log2_max_mv_length_horizontal` and `log2_max_mv_length_vertical`, as specified in clause E.2.1, that apply to the current scalable layer representation. + +NOTE 17 – The value range of a decoded vertical or horizontal motion vector component is also constrained by profile and level limits as specified in Annex A and clause F.10. + +**`max_num_reorder_frames[ i ]`** indicates the value of `max_num_reorder_frames`, as specified in clause E.2.1, that applies to the current scalable layer representation. + +**`max_dec_frame_buffering[ i ]`** indicates the value of `max_dec_frame_buffering`, as specified in clause E.2.1, that applies to the current scalable layer representation. + +**`conversion_type_idc[ i ]`** equal to 0 indicates that `tcoeff_level_prediction_flag` is equal to 1 for all primary coded slices of the current scalable layer representation excluding those having `no_inter_layer_pred_flag` equal to 1 and that the information specified by the syntax elements `rewriting_profile_level_idc[ i ][ j ]`, `rewriting_avg_bitrate[ i ][ j ]`, and `rewriting_max_bitrate[ i ][ j ]`, when present, is correct, though the method for converting the current scalable layer representation into an alternative set of access units that conforms to one or more of the profiles specified in Annex A and gives exactly the same decoding result as the current scalable layer representation is unspecified. + +**`conversion_type_idc[ i ]`** equal to 1 indicates that the `slice_header_restriction_flag` in the subset sequence parameter sets referred to by the primary coded VCL NAL units of the current scalable layer is equal to 1, that `slice_skip_flag` is equal to 1 for all primary coded VCL NAL units with `no_inter_layer_pred_flag` equal to 0 in the current scalable layer representation, and that the alternative set of access units obtained by applying the following operations in sequential order to the current scalable layer representation conforms to one or more of the profiles specified in Annex A: + +1. For all picture parameter set NAL units referred to by NAL units with `nal_unit_type` equal to 1 or 5, change the value of `seq_parameter_set_id` to be equal to the value of `seq_parameter_set_id` in a subset sequence parameter set NAL unit with `profile_idc` equal to 83 or 86 that is referred to by slices with `nal_unit_type` equal to 20 of the current scalable layer. +2. Remove all NAL units with `nal_unit_type` equal to 20 and `slice_skip_flag` equal to 1. +3. Remove all NAL units with `nal_unit_type` equal to 14. +4. Remove all redundant coded VCL NAL units. +5. In each access unit, remove all VCL NAL units with DQId less than DQIdMax, with DQIdMax being the maximum value of DQId in the primary coded slices of the access unit after removing the NAL units with `nal_unit_type` equal to 20 and `slice_skip_flag` equal to 1. +6. Remove the NAL unit header SVC extension from NAL units with `nal_unit_type` equal to 20. +7. For NAL units with `nal_unit_type` equal to 20 and `idr_flag` equal to 1, set `nal_unit_type` equal to 5. +8. For NAL units with `nal_unit_type` equal to 20 and `idr_flag` equal to 0, set `nal_unit_type` equal to 1. +9. Remove all SEI NAL units. +10. Remove all NAL units with `nal_unit_type` equal to 7. +11. For all NAL units with `nal_unit_type` equal to 15, set `nal_unit_type` equal to 7, remove all the syntax elements after the syntax structure `seq_parameter_set_data()` and before the `rbsp_trailing_bits()` syntax structure, replace the three bytes starting from `profile_idc` as specified by `rewriting_profile_level_idc[ i ][ entropy_coding_mode_flag ]`, when present, and change RBSP trailing bits appropriately. + +conversion\_type\_idc[ i ] equal to 2 indicates that slice\_header\_restriction\_flag in the subset sequence parameter sets referred to by the primary coded VCL NAL units of the current scalable layer is equal to 1, that no\_inter\_layer\_pred\_flag is equal to 1 in all primary coded VCL NAL units of the current scalable layer, and that the alternative set of access units obtained by applying the following operations in sequential order to the current scalable layer representation conforms to one or more of the profiles specified in Annex A: + +1. Remove all NAL units with nal\_unit\_type equal to 14. +2. Remove all redundant coded VCL NAL units. +3. In each access unit, remove all VCL NAL units with DQId less than DQIdMax. +4. Remove the NAL unit header SVC extension from NAL units with nal\_unit\_type equal to 20. +5. For NAL units with nal\_unit\_type equal to 20 and idr\_flag equal to 1, set nal\_unit\_type equal to 5. +6. For NAL units with nal\_unit\_type equal to 20 and idr\_flag equal to 0, set nal\_unit\_type equal to 1. +7. Remove all SEI NAL units. +8. Remove all NAL units with nal\_unit\_type equal to 7. +9. For all NAL units with nal\_unit\_type equal to 15, set nal\_unit\_type equal to 7, remove all the syntax elements after the syntax structure seq\_parameter\_set\_data( ) and before the rbsp\_trailing\_bits( ) syntax structure, replace the three bytes starting from profile\_idc as specified by rewriting\_profile\_level\_idc[ i ][ entropy\_coding\_mode\_flag ], when present, and change RBSP trailing bits appropriately. + +The value of conversion\_type\_idc[ i ] shall be in the range of 0 to 2, inclusive. + +For the following syntax elements rewriting\_info\_flag[ i ][ j ], rewriting\_profile\_level\_idc[ i ][ j ], rewriting\_avg\_bitrate[ i ][ j ], and rewriting\_max\_bitrate[ i ][ j ], the variable j specifies the value of entropy\_coding\_mode\_flag for all picture parameter set NAL units that are referenced in the VCL NAL units of the alternative set of access units obtained by converting the current scalable layer representation, with values for j equal to 0 or 1 indicating use of the CAVLC or CABAC entropy coding methods, respectively. + +NOTE 18 – It might be possible to convert the current scalable layer representation into two alternative sets of access units that conform to one or more of the profiles specified in Annex A, with one of these sets having entropy\_coding\_mode\_flag equal to 0 and the other set having entropy\_coding\_mode\_flag equal to 1 in all picture parameter set NAL units that are referenced in the VCL NAL units of the alternative set of access units. + +**rewriting\_info\_flag[ i ][ j ]** equal to 1 specifies that information about the alternative set of access units obtained by converting the current scalable layer representation is present in the scalability information SEI message. rewriting\_info\_flag[ i ][ j ] equal to 0 specifies that information about the alternative set of access units is not present in the scalability information SEI message. When rewriting\_info\_flag[ i ][ j ] is equal to 1, it is asserted that the information signalled by the syntax elements rewriting\_profile\_level\_idc[ i ][ j ], rewriting\_avg\_bitrate[ i ][ j ], and rewriting\_max\_bitrate[ i ][ j ] is correct, though, when conversion\_type\_idc[ i ] is equal to 0 or the value of entropy\_coding\_mode\_flag is modified, the method for constructing the alternative set of access units is unspecified. + +**rewriting\_profile\_level\_idc[ i ][ j ]** indicates the conformance point of the alternative set of access units for the current scalable layer representation after conversion. rewriting\_profile\_level\_idc[ i ] is the exact copy of the three bytes consist of profile\_idc, constraint\_set0\_flag, constraint\_set1\_flag, constraint\_set2\_flag, constraint\_set3\_flag, constraint\_set4\_flag, constraint\_set5\_flag, reserved\_zero\_2bits, and level\_idc, as if these syntax elements were used to specify the profile and level conformance of the alternative set of access units obtained by converting the scalable layer representation. + +**rewriting\_avg\_bitrate[ i ][ j ]** indicates the average bit rate of the alternative set of access units obtained by converting the representation of the current scalable layer. The average bit rate of the alternative set of access units in bits per second is given by BitRateBPS( rewriting\_avg\_bitrate[ i ][ j ] ) with the function BitRateBPS( ) being specified in Equation F-370. The average bit rate is derived according to the access unit removal time specified in Annex C of the Recommendation | International Standard. + +**rewriting\_max\_bitrate[ i ][ j ]** indicates an upper bound for the bit rate of the alternative set of access units obtained by converting the representation of the current scalable layer, in any one-second time window of access unit removal time as specified in Annex C. The upper bound for the bit rate of the alternative set of access units in bits per second is given by BitRateBPS( rewriting\_max\_bitrate[ i ][ j ] ) with the function BitRateBPS( ) being specified in Equation F-370. + +For the following specification, the terms priority layer, dependency layer, and priority layer representation are defined as follows. A priority layer consists of the set of primary coded VCL NAL units, inside the target access unit set, that are associated with a particular value of dependency\_id and a value of alt\_priority\_id[ i ], as specified in clause F.13.2.4, that is less than or equal to a particular priority identifier pId and the set of associated non-VCL NAL units. A priority layer + +is associated with a particular value of `dependency_id` and a particular priority layer identifier `pId`. When present in the target access unit, the following NAL units are associated non-VCL NAL units for a priority layer: + +- sequence parameter set, subset sequence parameter set, and picture parameter set NAL units that are referenced in the VCL NAL units of the priority layer (via the syntax element `pic_parameter_set_id`), +- sequence parameter set extension NAL units that are associated with a sequence parameter set NAL unit referenced in the VCL NAL units of the priority layer, +- filler data NAL units that belong to an access unit containing VCL NAL units of the priority layer and are associated with the same values of `dependency_id` and `quality_id` as the VCL NAL units of the priority layer in the same access unit, +- SEI NAL units containing SEI messages, with `payloadType` not equal to 24, 28, or 29, that apply to subsets of the bitstream that contain one or more VCL NAL units of the priority layer, +- access unit delimiter, end of sequence, and end of stream NAL units that are present in access units that contain VCL NAL units of the priority layer. + +The set of NAL units that represents the set union of all priority layers that are associated with the same value of `dependency_id` is referred to as `dependency layer`. A `dependency layer` is associated with a particular value of `dependency_id`. + +A priority layer A is directly dependent on a priority layer B when any VCL NAL unit of the priority layer A references data of any VCL NAL unit of the priority layer B through inter prediction or inter-layer prediction as specified in the decoding process in clause F.8. A priority layer A is indirectly dependent on a priority layer B when the priority layer A is not directly dependent on the priority layer B but there exists a set of $n$ (with $n$ being greater than 0) priority layers $\{C_0, \dots, C_{n-1}\}$ with the following properties: The priority layer A is directly dependent on the priority layer $C_0$ , each priority layer $C_i$ with $i$ in the range of 0 to $n - 2$ , inclusive, is directly dependent on the priority layer $C_{i+1}$ , and the priority layer $C_{n-1}$ is directly dependent on the priority layer B. + +The representation of a particular priority layer is the set of NAL units that represents the set union of the particular priority layer and all priority layers on which the particular priority layer directly or indirectly depends. The representation of a priority layer is also referred to as `priority layer representation`. In the following specification of this clause, the terms `representation of a priority layer` and `priority layer representation` are also used for referring to the access unit set that can be constructed from the NAL units of the priority layer representation. A priority layer representation can be decoded independently of all NAL units that do not belong to the priority layer representation. + +**`pr_num_dids_minus1`** plus 1 specifies the number of dependency layers for which the priority layer characteristic information as specified by the following syntax elements is present in the scalability information SEI message. The value of `pr_num_dids_minus1` shall be in the range of 0 to 7, inclusive. + +**`pr_dependency_id[ i ]`** specifies the value of `dependency_id` of the dependency layer for which the priority layer characteristic information is signalled by the following syntax elements. When $i$ is greater than 0, the value of `pr_dependency_id[ i ]` shall not be equal to any of the values of `pr_dependency_id[ j ]` with $j = 0..(i - 1)$ . + +**`pr_num_minus1[ i ]`** plus 1 specifies the number of priority layers with `dependency_id` equal to `pr_dependency_id[ i ]` for which priority layer characteristic information as specified by the following syntax elements is present in the scalability information SEI message. The value of `pr_num_minus1[ i ]` shall be in the range of 0 to 63, inclusive. + +**`pr_id[ i ][ j ]`** specifies the priority identifier `pId` for a priority layer with `dependency_id` equal to `pr_dependency_id[ i ]`. The value of `pr_id[ i ][ j ]` shall be in the range of 0 to 63, inclusive. The target access unit set shall contain one or more primary coded VCL NAL units that are associated with `dependency_id` equal to `pr_dependency_id[ i ]` and `alt_priority_id[ i ]` equal to `pr_id[ i ][ j ]`, where the value of `alt_priority_id[ i ]` that is associated with a primary coded VCL NAL unit is specified in clause F.13.2.4. When $j$ is greater than 0, the value of `pr_id[ i ][ j ]` shall not be equal to any of the values of `pr_id[ i ][ k ]` with $k = 0..(j - 1)$ . + +For the following specification inside the clause, the priority layer with `dependency_id` equal to the current value of `pr_dependency_id[ i ]` and the priority layer identifier `pId` equal to the current value of `pr_id[ i ][ j ]` is referred to as the `current priority layer` and the representation of the current priority layer is referred to as the `current priority layer representation`. + +**`pr_profile_level_idc[ i ][ j ]`** indicates the conformance point of the current priority layer representation. `pr_profile_level_idc[ i ]` is the exact copy of the three bytes consisting of `profile_idc`, `constraint_set0_flag`, `constraint_set1_flag`, `constraint_set2_flag`, `constraint_set3_flag`, `constraint_set4_flag`, `constraint_set5_flag`, `reserved_zero_2bits`, and `level_idc`, as if these syntax elements were used to specify the profile and level conformance of the current priority layer representation. + +**pr\_avg\_bitrate[ i ][ j ]** indicates the average bit rate of the current priority layer representation. The average bit rate of the current priority layer representation in bits per second is given by BitRateBPS( pr\_avg\_bitrate[ i ][ j ] ) with the function BitRateBPS( ) being specified in Equation F-370. The average bit rate is derived according to the access unit removal time specified in Annex C of this Recommendation | International Standard. In the following, bTotal is the number of bits in all NAL units of the current priority layer representation, t1 is the removal time (in seconds) of the access unit associated with the scalability information SEI message, and t2 is the removal time (in seconds) of the last access unit (in decoding order) of the target access unit set. + +With x specifying the value of pr\_avg\_bitrate[ i ], the following applies: + +- If t1 is not equal to t2, the condition specified in Equation F-371 shall be fulfilled. +- Otherwise (t1 is equal to t2), the condition specified in Equation F-372 shall be fulfilled. + +**pr\_max\_bitrate[ i ][ j ]** indicates an upper bound for the bit rate of the current priority layer representation in any one-second time window of access unit removal time as specified in Annex C. The upper bound for the bit rate of the current priority layer representation in bits per second is given by BitRateBPS( pr\_max\_bitrate[ i ][ j ] ) with the function BitRateBPS( ) being specified in Equation F-370. The bit rate values are derived according to the access unit removal time specified in Annex C of this Recommendation | International Standard. In the following, t1 is any point in time (in seconds), t2 is set equal to t1 + 1, and bTotal is the number of bits in all NAL units of the current priority layer representation that belong to access units with a removal time greater than or equal to t1 and less than t2. With x specifying the value of pr\_max\_bitrate[ i ][ j ], the condition specified in Equation F-373 shall be obeyed. + +**priority\_id\_setting\_uri[ PriorityIdSettingUriIdx ]** is the PriorityIdSettingUriIdx-th byte of a null-terminated string specifying the uniform resource identifier (URI) of the description of the method used to calculate the priority\_id values in the NAL unit headers for the target access unit set. The URI shall be as specified by IETF RFC 3986. + +#### F.13.2.2 Sub-picture scalable layer SEI message semantics + +The sub-picture scalable SEI message provides a mechanism for associating a slice group set indicated in a motion-constrained slice group set SEI message with a sub-picture scalable layer. + +In the following specification of this clause, the terms scalable layer, sub-picture scalable layer, and primary coded VCL NAL unit are used as specified in clause F.13.2.1. + +A sub-picture scalable layer SEI message shall not be succeeded, in decoding order, by a scalability information SEI message inside the same access unit. + +When a sub-picture scalable SEI message is present, the following applies: + +- If the sub-picture scalable layer SEI message is included in a scalable nesting SEI message, a motion-constrained slice group set SEI message, which is also referred to as the associated motion-constrained slice group set SEI message, shall be present in the same scalable nesting SEI message and it shall immediately precede the sub-picture scalable layer SEI message in decoding order. The scalable nesting SEI message that contains the sub-picture scalable layer SEI message shall contain num\_layer\_representations\_minus1 equal to 0 and sei\_quality\_id[ 0 ] equal to 0. The variable depId is set equal to the value of sei\_dependency\_id[ 0 ] that is present in the scalable nesting SEI message containing the sub-picture scalable layer SEI message. +- Otherwise (the sub-picture scalable layer SEI message is not included in a scalable nesting SEI message), the sub-picture scalable layer SEI message shall be the first SEI payload in an SEI NAL unit and the NAL unit immediately preceding the SEI NAL unit containing the sub-picture scalable layer SEI message shall be an SEI NAL unit that contains a motion-constrained slice group set SEI message, which is also referred to as associated motion-constrained slice group set SEI message, as last SEI payload. The variable depId is set equal to 0. + +The slice group set identified by the associated motion-constrained slice group set SEI message is referred to as the associated slice group set of the sub-picture scalable layer SEI message. + +The access unit associated with the sub-picture scalable layer SEI message shall not contain any primary coded VCL NAL unit that has dependency\_id equal to depId and IdrPicFlag equal to 0. The set of access units consisting of the access unit associated with the sub-picture scalable layer SEI message and all succeeding access units in decoding order until, but excluding, the next access unit that contains any primary coded VCL NAL unit with dependency\_id equal to depId and IdrPicFlag equal to 1 or that does not contain any primary coded VCL NAL units with IdrPicFlag equal to 0 (if present) or the end of the bitstream (otherwise) is referred to as the target access unit set. The sub-picture scalable layer SEI message applies to the target access unit set. + +NOTE – The set of primary coded pictures in the target access unit set for a sub-picture scalable layer SEI message is identical to the target picture set for the associated motion-constrained slice group set SEI message. + +**layer\_id** indicates, when the access unit containing the sub-picture scalable layer SEI message belongs to the target access unit set of a scalability information SEI message, the layer identifier of the sub-picture scalable layer to which the coded slice NAL units in the associated slice group set belong. The value of layer\_id shall be in the range of 0 to 2047, inclusive. + +The access unit containing the sub-picture scalable layer SEI message may or may not belong to the target access unit set of a scalability information SEI message. When the access unit containing the sub-picture scalable layer SEI message belongs to the target access unit set of a scalability information SEI message, the corresponding scalability information SEI message may or may not contain information for a scalable layer i with layer identifier layer\_id[ i ] equal to layer\_id. When the access unit containing the sub-picture scalable layer SEI message belongs to the target access unit set of a scalability information SEI message and the corresponding scalability information SEI message contains information for a scalable layer i with layer identifier layer\_id[ i ] equal to layer\_id, which is referred to as the current scalable layer in the following, the following applies. The information for the current scalable layer in the scalability SEI shall contain sub\_pic\_layer\_flag[ i ] equal to 1. The sub-picture area for the current scalable layer i, which is specified by the syntax elements horizontal\_offset[ i ], vertical\_offset[ i ], region\_width[ i ], and region\_height[ i ] in the scalability information SEI message, shall be identical to the area specified by the associated slice group set. + +### F.13.2.3 Non-required layer representation SEI message semantics + +The non-required layer representation SEI message provides a mechanism for indicating which layer representations of the current primary coded picture are not required for decoding dependency representations with a particular value of dependency\_id of the current primary coded picture and succeeding primary coded pictures, in decoding order. + +The non-required layer representation SEI message shall not be included in a scalable nesting SEI message. + +**num\_info\_entries\_minus1** plus 1 specifies the number of dependency\_id values for which non-required layer representations are indicated in the SEI message. The value of num\_info\_entries\_minus1 shall be in the range of 0 to 7, inclusive. + +**entry\_dependency\_id[ i ]** specifies the dependency\_id value for which non-required layer representations are indicated by the following syntax elements. The instances of entry\_dependency\_id[ i ] shall appear in increasing order of their values. + +The dependency representation of the primary coded picture with dependency\_id equal to entry\_dependency\_id[ i ] is referred to as the target dependency representation. + +The target dependency representation may or may not be present in the access unit. + +**num\_non\_required\_layer\_reps\_minus1[ i ]** plus 1 specifies the number of non-required layer representations for the target dependency representation that are indicated in the SEI message. The value of num\_non\_required\_layer\_reps\_minus1[ i ] shall be in the range of 0 to 127, inclusive. + +**non\_required\_layer\_rep\_dependency\_id[ i ][ j ]** indicates the value of dependency\_id of the j-th non-required layer representation for the target dependency representation. + +**non\_required\_layer\_rep\_quality\_id[ i ][ j ]** indicates the value of quality\_id of the j-th non-required layer representation for the target dependency representation. + +The i-th non-required layer representation for the target dependency representation is the layer representation of the primary coded picture that has dependency\_id equal to non\_required\_layer\_rep\_dependency\_id[ i ][ j ] and quality\_id equal to non\_required\_layer\_rep\_quality\_id[ i ][ j ]. A non-required layer representation for the target dependency representation is not required for decoding the target dependency representation and any dependency representation with dependency\_id equal to entry\_dependency\_id[ i ] of primary coded pictures that follow the current primary picture in decoding order. + +When DependencyIdMax is equal to entry\_dependency\_id[ i ], the VCL NAL units of the non-required layer representations shall not be referenced through inter or inter-layer prediction in the decoding process as specified in clause F.8. + +NOTE – In addition to the i-th non-required layer representation for the target dependency representation, those layer representations that have dependency\_id equal to non\_required\_layer\_rep\_dependency\_id[ i ][ j ] and quality\_id greater than non\_required\_layer\_rep\_quality\_id[ i ][ j ] are also non-required layer representations for the target dependency representation. + +The i-th non-required layer representation may or may not be present in the access unit. + +### F.13.2.4 Priority layer information SEI message semantics + +The priority layer information SEI message provides a mechanism for signalling alternative priority\_id values for VCL NAL units of the primary coded picture. The alternative values for priority\_id indicate priority layers. + +The priority layer information SEI message shall not be included in a scalable nesting SEI message. + +**pr\_dependency\_id** specifies the value of dependency\_id for the VCL NAL units for which alternative values for priority\_id are indicated. + +**num\_priority\_ids** specifies the number of layer representations with dependency\_id equal to pr\_dependency\_id for which alternative values of priority\_id are indicated. + +**alt\_priority\_id[ i ]** specifies the alternative value for priority\_id for the VCL NAL units of the primary coded picture that have dependency\_id equal to pr\_dependency\_id and quality\_id equal to i. + +The layer representation of the primary coded picture with dependency\_id equal to pr\_dependency\_id and quality\_id equal to i may or may not be present in the access unit. + +#### F.13.2.5 Layers not present SEI message semantics + +The layers not present SEI message provides a mechanism for signalling that NAL units of particular scalable layers indicated by the preceding scalability information SEI message are not present in a particular set of access units. + +In the following specification of this clause, the terms scalable layer and primary coded VCL NAL unit are used as specified in clause F.13.2.1. + +A layers not present SEI message shall not be included in a scalable nesting SEI message. + +A layers not present SEI message shall not be present in an access unit that does not belong to the target access unit set of any scalability information SEI message. A layers not present SEI message shall not be succeeded, in decoding order, by a scalability information SEI message inside the same access unit. The set of access units consisting of the access unit associated with the layers not present SEI message and all succeeding access units in decoding order until, but excluding, the next access unit that contains a layers not present SEI message or that does not contain any primary coded VCL NAL units with IdrPicFlag equal to 0 (if present), or the end of the bitstream (otherwise) is referred to as the target access unit set. The layers not present SEI message applies to the target access unit set. + +A layers not present SEI message refers to the most recent scalability information SEI message in decoding order. Each scalable layer that is referred to in this clause is a scalable layer indicated in the most recent scalability information SEI message in decoding order. Each layer identifier for a scalable layer that is referred to in this clause is a layer identifier for a scalable layer indicated in the most recent scalability information SEI message in decoding order. + +NOTE 1 – Layers not present SEI messages do not have a cumulative effect. + +**num\_layers** specifies the number of syntax elements layer\_id[ i ] that are present in the layers not present SEI message. The value of num\_layers shall be in the range of 0 to 2047, inclusive. + +**layer\_id[ i ]** indicates the layer identifier of a scalable layer for which no VCL NAL units are present in the target access unit set. The value of layer\_id[ i ] shall be in the range of 0 to 2047, inclusive. The value of layer\_id[ i ] shall be equal to one of the values of layer\_id[ i ] in the most recent scalability information SEI message. The target access unit set shall not contain any VCL NAL unit of the scalable layer having a layer identifier equal to layer\_id[ i ]. When i is greater than 0, the value of layer\_id[ i ] shall not be equal to any of the values of layer\_id[ j ] with j = 0..(i - 1). + +NOTE 2 – When an application removes NAL units from a scalable bitstream, e.g. in order to adapt the bitstream to a transmission channel or the capabilities of a receiving device, and keeps the present layers not present SEI messages, it might need to modify the content of some of the layers not present SEI messages and remove some other layers not present SEI messages in order to obtain a bitstream conforming to this Recommendation | International Standard. + +#### F.13.2.6 Layer dependency change SEI message semantics + +The layer dependency change SEI message provides a mechanism for signalling that the interdependencies between particular scalable layers indicated by the preceding scalability information SEI message are changed for a particular set of access units. + +In the following specification of this clause, the terms scalable layer, representation of a scalable layer, scalable layer representation, and primary coded VCL NAL unit are used as specified in clause F.13.2.1. + +A layer dependency change SEI message shall not be included in a scalable nesting SEI message. + +A layer dependency change SEI message shall not be present in an access unit that does not belong to the target access unit set of any scalability information SEI message. A layer dependency change SEI message shall not be succeeded, in decoding order, by a scalability information SEI message or a layers not present SEI message inside the same access unit. The set of access units consisting of the access unit associated with the layer dependency change SEI message and all succeeding access units in decoding order until, but excluding, the next access unit that contains a layer dependency change SEI message or a layers not present SEI message or that does not contain any primary coded VCL NAL units with IdrPicFlag equal to 0 (if present), or the end of the bitstream (otherwise) is referred to as the target access unit set. The layer dependency change SEI message applies to the target access unit set. + +A layer dependency change SEI message refers to the most recent scalability information SEI message in decoding order. Each scalable layer that is referred to in this clause is a scalable layer indicated in the most recent scalability information SEI message in decoding order. Each layer identifier for a scalable layer that is referred to in this clause is a layer identifier for a scalable layer indicated in the most recent scalability information SEI message in decoding order. + +NOTE 1 – Layer dependency change SEI messages do not have a cumulative effect. + +The presence of the layer dependency change SEI message specifies the following. For a scalable layer with a layer identifier equal to any value of `layer_id[ i ]` present in the layer dependency change SEI message, the layer dependency relationship is changed for the target access unit set relative to the layer dependency relationship specified by the most recent scalability information SEI message in decoding order. For a scalable layer with a layer identifier not equal to any value of `layer_id[ i ]` present in the layer dependency change SEI message, the layer dependency relationship remains the same as the one specified in the most recent scalability information SEI message in decoding order. + +When, according to the layer dependency information indicated in the most recent scalability information SEI message in decoding order, a scalable layer A does not directly or indirectly depend on another scalable layer B, the layer dependency change SEI message shall not specify that the scalable layer A directly or indirectly depends on the scalable layer B. + +When a scalable layer is considered to directly or indirectly depend on another scalable layer is specified in clause F.13.2.1, with the target access unit set being the target access unit set for the layer dependency change SEI message. + +**num\_layers\_minus1** plus 1 specifies the number of scalable layers for which a layer dependency information change relative to the most recent scalability information SEI message, in decoding order, is indicated in the layer dependency change SEI message. The value of `num_layers_minus1` is in the range of 0 to 2047, inclusive. + +**layer\_id[ i ]** indicates the layer identifier of the scalable layer for which a layer dependency information change is indicated by the following syntax elements. The value of `layer_id[ i ]` shall be in the range of 0 to 2047, inclusive. The value of `layer_id[ i ]` shall be equal to one of the values of `layer_id[ i ]` in the most recent scalability information SEI message. When `i` is greater than 0, the value of `layer_id[ i ]` shall not be equal to any of the values of `layer_id[ j ]` with `j = 0..(i - 1)`. + +NOTE 2 – When an application removes NAL units from a scalable bitstream, e.g. in order to adapt the bitstream to a transmission channel or the capabilities of a receiving device, and keeps the present layer dependency change SEI messages, it might need to modify the content of some of the layer dependency change SEI messages and remove some other layer dependency change SEI messages in order to obtain a bitstream conforming to this Recommendation | International Standard. + +For the following specification of this clause, the scalable layer with layer identifier equal to the current value of `layer_id[ i ]` is referred to as the current scalable layer and the representation of the current scalable layer is referred to as current scalable layer representation. + +**layer\_dependency\_info\_present\_flag[ i ]** equal to 1 specifies that one or more syntax elements `dependent_layer_id_delta_minus1[ i ][ j ]` indicating the layer dependency information for the current scalable layer are present in the layer dependency change SEI message. `layer_dependency_info_present_flag[ i ]` equal to 0 specifies that the syntax element `layer_dependency_info_src_layer_id_delta_minus1[ i ]` for the current scalable layer is present in the layer dependency change SEI message. + +**num\_directly\_dependent\_layers[ i ]** specifies the number of the syntax elements `directly_dependent_layer_id_delta_minus1[ i ][ j ]` that are present for the current scalable layer. The value of `num_directly_dependent_layers` shall be in the range of 0 to 255, inclusive. + +**directly\_dependent\_layer\_id\_delta\_minus1[ i ][ j ]** plus 1 indicates the difference between the value of `layer_id[ i ]` for the current scalable layer and the layer identifier of a particular scalable layer, on which the current scalable layer directly depends. The value of `directly_dependent_layer_id_delta_minus1[ i ][ j ]` shall be in the range of 0 to `layer_id[ i ] - 1`, inclusive. The layer identifier of the particular scalable layer, on which the current scalable layer directly depends, is equal to `layer_id[ i ] - directly_dependent_layer_id_delta_minus1[ i ][ j ] - 1`. The most recent scalability information SEI message in decoding order shall contain information for a scalable layer b with `layer_id[ b ]` equal to `layer_id[ i ] - directly_dependent_layer_id_delta_minus1[ i ][ j ] - 1` and this information shall not contain a value of `layer_dependency_info_src_layer_id_delta[ i ]` equal to 0. + +Let `setOfDepLayers` be the set union of the representations of the scalable layers b that have `layer_id[ b ]` equal to `layer_id[ i ] - directly_dependent_layer_id_delta_minus1[ i ][ j ] - 1`, with `j = 0..num_directly_dependent_layers[ i ] - 1`. When `layer_dependency_info_present_flag[ i ]` is equal to 1, the set `setOfDepLayers` shall not contain any scalable layer, on which the current scalable layer does not directly or indirectly depends inside the target access unit set and the current scalable layer shall not depend on any scalable layer, inside the target access unit set, that is not included in the set `setOfDepLayers`. + +**layer\_dependency\_info\_src\_layer\_id\_delta\_minus1[ i ]** indicates that the current scalable layer has the same layer dependency information as the scalable layer with layer identifier equal to $\text{layer\_id}[ i ] - \text{layer\_dependency\_info\_src\_layer\_id\_delta\_minus1}[ i ] - 1$ . The value of **layer\_dependency\_info\_src\_layer\_id\_delta\_minus1[ i ]** shall be in the range of 0 to $\text{layer\_id}[ i ] - 1$ , inclusive. The most recent scalability information SEI message in decoding order shall contain information for a scalable layer b with $\text{layer\_id}[ b ]$ equal to $\text{layer\_id}[ i ] - \text{layer\_dependency\_info\_src\_layer\_id\_delta\_minus1}[ i ] - 1$ and this information shall not contain a value of **layer\_dependency\_info\_src\_layer\_id\_delta[ b ]** equal to 0. + +When **layer\_dependency\_info\_present\_flag[ i ]** is equal to 0, the set of scalable layers on which the current scalable layer depends inside the target access unit set shall be identical to the set of layers on which the scalable layer b with $\text{layer\_id}[ b ]$ equal to $\text{layer\_id}[ i ] - \text{layer\_dependency\_info\_src\_layer\_id\_delta\_minus1}[ i ] - 1$ depends inside the target access unit set. + +#### F.13.2.7 Scalable nesting SEI message semantics + +The scalable nesting SEI message provides a mechanism for associating SEI messages with subsets of a bitstream. + +A scalable nesting SEI message shall contain one or more SEI messages with **payloadType** not equal to 30 and it shall not contain any SEI message with **payloadType** equal to 30. An SEI message contained in a scalable nesting SEI message is referred to as a nested SEI message. An SEI message not contained in a scalable nesting SEI message is referred to as a non-nested SEI message. The scope to which the nested SEI message applies is indicated by the syntax elements **all\_layer\_representations\_in\_au\_flag**, **num\_layer\_representations\_minus1**, **sei\_dependency\_id[ i ]**, **sei\_quality\_id[ i ]**, and **sei\_temporal\_id**, when present. + +A buffering period SEI message and an SEI message of any other type shall not be nested in the same scalable nesting SEI message. A picture timing SEI message and an SEI message of any other type shall not be nested in the same scalable nesting SEI message. + +**all\_layer\_representations\_in\_au\_flag** equal to 1 specifies that the nested SEI message applies to all layer representations of the access unit. **all\_layer\_representations\_in\_au\_flag** equal to 0 specifies that the scope of the nested SEI message is specified by the syntax elements **num\_layer\_representations\_minus1**, **sei\_dependency\_id[ i ]**, **sei\_quality\_id[ i ]**, and **sei\_temporal\_id**. + +**num\_layer\_representations\_minus1** plus 1 specifies, when **num\_layer\_representations\_minus1** is present, the number of syntax element pairs **sei\_dependency\_id[ i ]** and **sei\_quality\_id[ i ]** that are present in the scalable nesting SEI message. When **num\_layer\_representations\_minus1** is not present, it shall be inferred to be equal to $( \text{numSVCLayers} - 1 )$ with **numSVCLayers** being the number of layer representations that are present in the primary coded picture of the access unit. The value of **num\_layer\_representations\_minus1** shall be in the range of 0 to 127, inclusive. + +**sei\_dependency\_id[ i ]** and **sei\_quality\_id[ i ]** indicate the **dependency\_id** and the **quality\_id** values, respectively, of the layer representations to which the nested SEI message applies. The access unit may or may not contain layer representations with **dependency\_id** equal to **sei\_dependency\_id[ i ]** and **quality\_id** equal to **sei\_quality\_id[ i ]**. When **i** is greater than 0, the value of $( 16 * \text{sei\_dependency\_id}[ i ] + \text{sei\_quality\_id}[ i ] )$ shall not be equal to any of the values of $( 16 * \text{sei\_dependency\_id}[ j ] + \text{sei\_quality\_id}[ j ] )$ with $j = 0..(i - 1)$ . + +When **num\_layer\_representations\_minus1** is not present, the values of **sei\_dependency\_id[ i ]** and **sei\_quality\_id[ i ]** for **i** in the range of 0 to **num\_layer\_representations\_minus1** (with **num\_layer\_representations\_minus1** being the inferred value), inclusive, shall be inferred as specified in the following: + +1. Let **setDQId** be the set of the values **DQId** for all layer representations that are present in the primary coded picture of the access unit. +2. For **i** proceeding from 0 to **num\_layer\_representations\_minus1**, inclusive, the following applies: + - a. **sei\_dependency\_id[ i ]** and **sei\_quality\_id[ i ]** are inferred to be equal to $( \text{minDQId} \gg 4 )$ and $( \text{minDQId} \& 15 )$ , respectively, with **minDQId** being the smallest value (smallest value of **DQId**) in the set **setDQId**. + - b. The smallest value (smallest value of **DQId**) of the set **setDQId** is removed from **setDQId** and thus the number of elements in the set **setDQId** is decreased by 1. + +**sei\_temporal\_id** indicates the **temporal\_id** value of the sub-bitstream to which the nested SEI message applies. When **sei\_temporal\_id** is not present, it shall be inferred to be equal to **temporal\_id** of the access unit. + +When the nested SEI message is a buffering period SEI message or a picture timing SEI message (i.e., **payloadType** is equal to 0 or 1 for the nested SEI message), **sei\_temporal\_id** indicates the sub-bitstream for which the nested buffering period SEI message or picture timing SEI message applies. For a buffering period SEI message or picture timing SEI message that is nested in a scalable nesting SEI message, **sei\_dependency\_id[ i ]**, **sei\_quality\_id[ i ]**, and **sei\_temporal\_id** specify the greatest values of **dependency\_id**, **quality\_id**, and **temporal\_id**, respectively, of the sub-bitstreams to which + +the nested buffering period SEI message or picture timing SEI message applies. The bitstream may or may not contain access units with temporal\_id equal to sei\_temporal\_id. + +When the scalable nesting SEI message contains one or more SEI messages with payloadType not equal to 0 or 1, sei\_temporal\_id shall be equal to the value of temporal\_id for the access unit associated with the scalable nesting SEI message. For an nested SEI message with payloadType not equal to 0 or 1, the values of sei\_dependency\_id[ i ], sei\_quality\_id[ i ], and sei\_temporal\_id, present in or inferred for the associated scalable nesting SEI message, indicate the values of dependency\_id, quality\_id, and temporal\_id, respectively, of the VCL NAL units to which the nested SEI message applies. + +**sei\_nesting\_zero\_bit** shall be equal to 0. + +#### F.13.2.8 Base layer temporal HRD SEI message semantics + +The base layer temporal HRD SEI message provides HRD parameters for subsets of the base layer bitstream. + +The base layer temporal HRD SEI message shall not be included in a scalable nesting SEI message. The base layer temporal HRD SEI message shall not be present in access units that do not contain VCL NAL units of the primary coded picture with nal\_unit\_type equal to 5. + +When present, this SEI message applies to the target access unit set that consists of the current access unit and all subsequent access units in decoding order until, but excluding, the next access unit containing a NAL unit of the primary coded picture with nal\_unit\_type equal to 5 (if present) or the end of the bitstream (otherwise). + +**num\_of\_temporal\_layers\_in\_base\_layer\_minus1** plus 1 specifies the number of sub-bitstreams inside the target access unit set for which the following syntax elements are specified in the base layer temporal HRD SEI message. The value of num\_of\_temporal\_layers\_in\_base\_layer\_minus1 shall be in the range of 0 to 7, inclusive. + +**sei\_temporal\_id[ i ]** specifies the temporal\_id value of the i-th sub-bitstream. When i is greater than 0, the value of sei\_temporal\_id[ i ] shall not be equal to any of the values of sei\_temporal\_id[ j ] with j = 0..(i - 1). + +Access units with temporal\_id equal to sei\_temporal\_id[ i ] may or may not be present in the target access unit set. When access units with temporal\_id equal to sei\_temporal\_id[ i ] are not present in the target access unit set, the i-th sub-bitstream is considered as not existing. + +When access units with temporal\_id equal to sei\_temporal\_id[ i ] are present in the target access unit set, the i-th sub-bitstream is the sub-bitstream that is obtained by invoking the bitstream extraction process as specified in clause F.8.8.1 for the target access unit set with tIdTarget equal to sei\_temporal\_id[ i ], dIdTarget equal to 0, and qIdTarget equal to 0 as the inputs. + +**sei\_timing\_info\_present\_flag[ i ]** equal to 1 specifies that sei\_num\_units\_in\_tick[ i ], sei\_time\_scale[ i ], and sei\_fixed\_frame\_rate\_flag[ i ] are present in the base layer temporal HRD SEI message. sei\_timing\_info\_present\_flag[ i ] equal to 0 specifies that sei\_num\_units\_in\_tick[ i ], sei\_time\_scale[ i ], and sei\_fixed\_frame\_rate\_flag[ i ] are not present in the base layer temporal HRD SEI message. + +The following syntax elements for the i-th sub-bitstream are specified using references to Annex E. For these syntax elements the same semantics and constraints as the ones specified in Annex E apply, as if these syntax elements sei\_num\_units\_in\_tick[ i ], sei\_time\_scale[ i ], sei\_fixed\_frame\_rate\_flag[ i ], sei\_nal\_hrd\_parameters\_present\_flag[ i ], sei\_vcl\_hrd\_parameters\_present\_flag[ i ], sei\_low\_delay\_hrd\_flag[ i ], and sei\_pic\_struct\_present\_flag[ i ] were present as num\_units\_in\_tick, time\_scale, fixed\_frame\_rate\_flag, nal\_hrd\_parameters\_present\_flag, vcl\_hrd\_parameters\_present\_flag, low\_delay\_hrd\_flag, and pic\_struct\_present\_flag, respectively, in the VUI parameters of the active SVC sequence parameter sets for the i-th sub-bitstream. + +The parameters for the i-th sub-bitstream that are coded in the base layer temporal HRD SEI message shall be correct, as if these parameters are used for conformance checking (as specified in Annex C) of the i-th sub-bitstream. + +**sei\_num\_units\_in\_tick[ i ]** indicates the value of num\_units\_in\_tick, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +**sei\_time\_scale[ i ]** indicates the value of time\_scale, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +**sei\_fixed\_frame\_rate\_flag[ i ]** indicates the value of fixed\_frame\_rate\_flag, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +**sei\_nal\_hrd\_parameters\_present\_flag[ i ]** indicates the value of nal\_hrd\_parameters\_present\_flag, as specified in clause E.2.1, that applies to the i-th sub-bitstream. When sei\_nal\_hrd\_parameters\_present\_flag[ i ] is equal to 1, the NAL HRD parameters that apply to the i-th sub-bitstream immediately follow the sei\_nal\_hrd\_parameters\_present\_flag[ i ]. + +**sei\_vcl\_hrd\_parameters\_present\_flag[ i ]** indicates the value of **vc1\_hrd\_parameters\_present\_flag**, as specified in clause E.2.1, that applies to the i-th sub-bitstream. When **sei\_vcl\_hrd\_parameters\_present\_flag[ i ]** is equal to 1, the VCL HRD parameters that apply to the i-th sub-bitstream immediately follow the **sei\_vcl\_hrd\_parameters\_present\_flag[ i ]**. + +**sei\_low\_delay\_hrd\_flag[ i ]** indicates the value of **low\_delay\_hrd\_flag**, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +**sei\_pic\_struct\_present\_flag[ i ]** indicates the value of **pic\_struct\_present\_flag**, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +#### F.13.2.9 Quality layer integrity check SEI message semantics + +The quality layer integrity check SEI message provides a mechanism for detecting whether VCL NAL units with **quality\_id** greater than 0 of the primary coded picture have been removed from the bitstream. + +The quality layer integrity check SEI message shall not be included in a scalable nesting SEI message. + +**num\_info\_entries\_minus1** plus 1 specifies the number of syntax element pairs **entry\_dependency\_id[ i ]** and **quality\_layer\_crc[ i ]** that are present in the quality layer integrity check SEI message. The value of **num\_info\_entries\_minus1** shall be in the range of 0 to 7, inclusive. + +**entry\_dependency\_id[ i ]** specifies the **dependency\_id** value of the dependency representation for which **quality\_layer\_crc[ i ]** is indicated. The instances of **entry\_dependency\_id[ i ]** shall appear in increasing order of their values. The dependency representation of the primary coded picture that has **dependency\_id** equal to **entry\_dependency\_id[ i ]** is referred to as target dependency representation. + +The target dependency representation may or may not be present in the access unit. + +**quality\_layer\_crc[ i ]** specifies the cyclic redundancy check for all the VCL NAL units with **quality\_id** greater than 0 in the target dependency representation. + +Let **crcVal** be a variable that is derived as specified by the following ordered steps: + +1. Let the variable **qNalUnits[ ]** be the one-dimensional array of bytes that contains a concatenation, in decoding order, of the bytes of the **nal\_unit()** syntax structures of all VCL NAL units with **quality\_id** greater than 0 in the target dependency representation, in decoding order. +2. Let the variable **pLen** be the sum of the **NumBytesInNALUnit** variables of all VCL NAL units with **quality\_id** greater than 0 in the target dependency representation. +3. The value of **crcVal** is derived as specified by the following pseudo-code process: + +``` +qNalUnits[ pLen ] = 0 +qNalUnits[ pLen + 1 ] = 0 +crcVal = 65535 +for( bitIdx = 0; bitIdx < ( pLen + 2 ) * 8; bitIdx++ ) { + crcMsb = ( crcVal >> 15 ) & 1 + bitVal = ( qNalUnits[ bitIdx >> 3 ] >> ( 7 - ( bitIdx & 7 ) ) ) & 1 + crcVal = ( ( ( crcVal << 1 ) + bitVal ) & 65535 ) ^ ( crcMsb * 4129 ) +} +``` + +(F-383) + +When the target dependency representation is present in the access unit, a value of **quality\_layer\_crc[ i ]** not equal to **crcVal** indicates that one or more VCL NAL units with **quality\_id** greater than 0 of the target dependency representation have been removed from the bitstream and that the output pictures may show undesirable visual artefacts. + +#### F.13.2.10 Redundant picture property SEI message semantics + +The redundant picture property SEI message indicates properties for layer representations of redundant coded pictures. In the following, a layer representation of a redundant coded picture is also referred to as redundant coded layer representation and a layer representation of the primary coded picture is also referred to as primary coded layer representation. + +The redundant picture property SEI message shall not be included in a scalable nesting SEI message. + +**num\_dIds\_minus1** plus 1 specifies the number of **dependency\_id** values for which properties of redundant coded layer representations are indicated in the redundant picture property SEI message. The value of **num\_dIds\_minus1** shall be in the range of 0 to 7, inclusive. + +**dependency\_id[ i ]** specifies the dependency\_id value of the redundant coded layer representations for which properties are indicated by the following syntax elements. When i is greater than 0, the value of dependency\_id[ i ] shall not be equal to any of the values of dependency\_id[ j ] with j = 0..(i - 1). + +**num\_qIds\_minus1[ i ]** plus 1 specifies the number of quality\_id values for which properties of redundant coded layer representations with dependency\_id equal to dependency\_id[ i ] are indicated by the following syntax elements. The value of num\_qIds\_minus1[ i ] shall be in the range of 0 to 15, inclusive. + +**quality\_id[ i ][ j ]** specifies the quality\_id value of the redundant coded layer representations with dependency\_id equal to dependency\_id[ i ] for which properties are indicated by the following syntax elements. When j is greater than 0, the value of quality\_id[ i ][ j ] shall not be equal to any of the values of quality\_id[ i ][ k ] with k = 0..(j - 1). + +**num\_redundant\_pics\_minus1[ i ][ j ]** plus 1 specifies the number of redundant coded layer representations with dependency\_id equal to dependency\_id[ i ] and quality\_id equal to quality\_id[ i ][ j ] for which properties are indicated by the following syntax elements. The value of num\_redundant\_pics\_minus1[ i ][ j ] shall be in the range of 0 to 127, inclusive. + +**redundant\_pic\_cnt\_minus1[ i ][ j ][ k ]** plus 1 specifies the redundant\_pic\_cnt value of the redundant coded layer representation with dependency\_id equal to dependency\_id[ i ] and quality\_id equal to quality\_id[ i ][ j ] for which properties are indicated by the following syntax elements. The value of redundant\_pic\_cnt\_minus1[ i ][ j ][ k ] shall be in the range of 0 to 126, inclusive. When k is greater than 0, the value of redundant\_pic\_cnt\_minus1[ i ][ j ][ k ] shall not be equal to any of the values of redundant\_pic\_cnt\_minus1[ i ][ j ][ m ] with m = 0..(k - 1). + +The redundant coded layer representation having dependency\_id equal to dependency\_id[ i ], quality\_id equal to quality\_id[ i ][ j ], and redundant\_pic\_cnt equal to ( redundant\_pic\_cnt\_minus1[ i ][ j ][ k ] + 1 ) is referred to as the target redundant coded layer representation. The primary coded layer representation (redundant\_pic\_cnt is equal to 0) having dependency\_id equal to dependency\_id[ i ] and quality\_id equal to quality\_id[ i ][ j ] is referred to as the target primary coded layer representation. + +The target redundant coded layer representation may or may not be present in the access unit. The target primary coded layer representation may or may not be present in the access unit. + +For the following specification, the picture that only consists of the target redundant coded layer representation and the primary coded layer representations with DQId less than (dependency\_id[ i ] << 4) + quality\_id[ i ] is referred to as target redundant coded picture and the picture that only consists of the target primary coded layer representation and the primary coded layer representations with DQId less than (dependency\_id[ i ] << 4) + quality\_id[ i ] is referred to as target primary coded picture. + +For the following specification, the arrays mbType, subMbType, predFlagL0, predFlagL1, refIdxL0, refIdxL1, mvL0, mvL1, rSL, rSCb, rSCr, cSL, cSCb, and cSCr represent the corresponding arrays of the collective term currentVars after completion of the target macroblock decoding process as specified in clause F.8.1.5.6. + +**pic\_match\_flag[ i ][ j ][ k ]** equal to 1 indicates that the target redundant coded layer representation is an exact copy of the target primary coded layer representation, with the only difference in the value of redundant\_pic\_cnt. + +**mb\_type\_match\_flag[ i ][ j ][ k ]** equal to 1 indicates that the array mbType for the target redundant coded picture is identical to the array mbType for the target primary coded picture. + +**motion\_match\_flag[ i ][ j ][ k ]** equal to 1 indicates that, for each macroblock mbAddr in the target layer representation of the target primary coded picture for which the derived macroblock type mbType[ mbAddr ] represents a P or B macroblock type, the variables and arrays mbType[ mbAddr ], subMbType[ mbAddr ], predFlagL0[ mbAddr ], predFlagL1[ mbAddr ], refIdxL0[ mbAddr ], refIdxL1[ mbAddr ], mvL0[ mbAddr ], and mvL1[ mbAddr ] for the target redundant coded picture are identical to the corresponding variables and arrays for the target primary coded picture. + +**residual\_match\_flag[ i ][ j ][ k ]** equal to 1 indicates that, for each macroblock mbAddr in the target layer representation of the target primary coded picture for which the derived macroblock type mbType[ mbAddr ] represents a P or B macroblock type, the associated reconstructed residual sample values in the arrays rSL, rSCb, and rSCr for the target redundant coded picture are identical or close to the corresponding reconstructed residual sample values for the target primary coded picture. + +**intra\_samples\_match\_flag[ i ][ j ][ k ]** equal to 1 indicates that, for each macroblock mbAddr in the target layer representation of the target primary coded picture for which the derived macroblock type mbType[ mbAddr ] represents an I macroblock type, the associated reconstructed sample values in the arrays cSL, cSCb, and cSCr for the target redundant coded picture are identical or close to the corresponding reconstructed sample values for the target primary coded picture. + +#### F.13.2.11 Temporal level zero dependency representation index SEI message semantics + +The temporal level zero dependency representation index SEI message provides a mechanism for detecting whether a dependency representation with temporal\_id equal to 0 required for decoding the current access unit is available when NAL unit losses are expected during transport. + +Let setOfDId be a set of dependency\_id values that is derived as follows: + +- If the temporal level zero dependency representation index SEI message is not included in a scalable nesting SEI message, setOfDId consists of exactly one value, which is equal to 0. +- Otherwise (the temporal level zero dependency representation index SEI message is included in a scalable nesting SEI message), setOfDId consists of the values sei\_dependency\_id[ i ] for all i in the range of 0 to num\_layer\_representations\_minus1, inclusive, that are present in the scalable nesting SEI message associated with the temporal level zero dependency representation index SEI message. For the scalable nesting SEI message that contains the temporal level zero dependency representation index SEI message, all\_layer\_representations\_in\_au\_flag shall be equal to 1 or the value of sei\_quality\_id[ i ] shall be equal to 0 for all values of i in the range of 0 to num\_layer\_representations\_minus1, inclusive. + +All dependency representations that are referred to in the following specification inside this clause are dependency representations of a primary coded picture. Unless specified otherwise, all dependency representation that are referred to in the following are dependency representations of the primary coded picture of the access unit that is associated with the temporal level zero dependency representation index SEI message. + +The dependency representations of the access unit that have dependency\_id equal to any value of the set setOfDId are also referred to as associated dependency representations. + +For each value of dId in the set setOfDId, the access unit may or may not contain a dependency representation with dependency\_id equal to dId. + +**tl0\_dep\_rep\_idx** indicates the temporal level zero index for the associated dependency representations, if temporal\_id is equal to 0. Otherwise (temporal\_id is greater than 0), tl0\_dep\_rep\_idx indicates the temporal level zero index of the dependency representations of the most recent access unit with temporal\_id equal to 0 in decoding order that have the same value of dependency\_id as any of the associated dependency representations. + +For each value of dId in the set setOfDId, the following applies: + +- If the dependency representation with dependency\_id equal to dId contains a NAL unit with nal\_unit\_type equal to 5 or a NAL unit with nal\_unit\_type equal to 20 and idr\_flag equal to 1, tl0\_dep\_rep\_idx shall be equal to 0. +- Otherwise (the dependency representation with dependency\_id equal to dId does not contain a NAL unit with nal\_unit\_type equal to 5 or a NAL unit with nal\_unit\_type equal to 20 and idr\_flag equal to 1), the following is specified: + 1. Let prevTL0AU be the most recent access unit in decoding order that has temporal\_id equal to 0 and for which the primary coded picture contains a dependency representation with dependency\_id equal to dId. + 2. Let prevTL0DepRep be the dependency representation with dependency\_id equal to dId of the primary coded picture in access unit prevTL0AU. + 3. Let prevTL0DepRepIdx be equal to the value of tl0\_dep\_rep\_idx that is associated with the dependency representation prevTL0DepRep, as indicated by a corresponding temporal level zero dependency representation index SEI message. + 4. Depending on temporal\_id of the current access unit, the following applies: + - If temporal\_id of the current access unit is equal to 0, tl0\_dep\_rep\_idx shall be equal to ( prevTL0DepRepIdx + 1 ) % 256. + - Otherwise (temporal\_id of the current access unit is greater than 0), tl0\_dep\_rep\_idx shall be equal to prevTL0DepRepIdx. + +When the temporal level zero dependency representation index SEI message is associated with a particular dependency representation depRepA that has dependency\_id equal to dIdA and IdrPicFlag equal to 0, a temporal level zero dependency representation index SEI message shall also be associated with the previous dependency representation dIdB in decoding order that has dependency\_id equal to dIdA and IdrPicFlag equal to 1 and all dependency representations with dependency\_id equal to dIdA and temporal\_id equal to 0 that follow the dependency representation dIdB and precede the dependency representation dIdA in decoding order. + +NOTE – For the tl0\_dep\_rep\_idx mechanism to be effectively used, transport mechanisms should ensure that the information is present in every packet that carries data for the particular values of dependency\_id. + +**effective\_idr\_pic\_id** indicates the latest value of **idr\_pic\_id** in decoding order present in this access unit or any preceding access unit for dependency representations indicated by **sei\_dependency\_id[ i ]**. + +For each value of **dId** in the set **setOfDId**, the following applies: + +- If the dependency representation with **dependency\_id** equal to **dId** contains a NAL unit with **nal\_unit\_type** equal to 5 or a NAL unit with **nal\_unit\_type** equal to 20 and **idr\_flag** equal to 1, **effective\_idr\_pic\_id** shall be equal to **idr\_pic\_id** of the dependency representation with **dependency\_id** equal to **dId**. +- Otherwise (the dependency representation with **dependency\_id** equal to **dId** does not contain a NAL unit with **nal\_unit\_type** equal to 5 or a NAL unit with **nal\_unit\_type** equal to 20 and **idr\_flag** equal to 1), **effective\_idr\_pic\_id** shall be equal to **idr\_pic\_id** of the previous dependency representation in decoding order with **dependency\_id** equal to **dId** that contains a NAL unit with **nal\_unit\_type** equal to 5 or a NAL unit with **nal\_unit\_type** equal to 20 and **idr\_flag** equal to 1. + +#### F.13.2.12 Temporal level switching point SEI message semantics + +The temporal level switching point SEI message provides a mechanism for identifying temporal level switching points. If a dependency representation is associated with a temporal level switching point SEI message, then it is a temporal level switching point as specified subsequently and constrained by **delta\_frame\_num**. Otherwise, the dependency representation may or may not be a temporal level switching point. + +All dependency representations that are referred to in the following specification of this clause are dependency representations of primary coded pictures. + +In the following, let **tId** be the value of **temporal\_id** of the access unit that is associated with the temporal level switching point SEI message. + +NOTE 1 – Let **dId** be the value of **dependency\_id** that a bitstream adaptation process has used to generate a sub-bitstream **subBitstreamA** that contains dependency representations with **dependency\_id** less than or equal to **dId** and **temporal\_id** less than **tId** of an input bitstream (that is conforming to this Recommendation | International Standard) until the current access unit, exclusive. The bitstream adaptation process can infer from a temporal level switching point SEI message whether or not the sub-bitstream containing **subBitstreamA** and the dependency representations with **dependency\_id** less than or equal to **dId** and **temporal\_id** less than or equal to **tId** of the input bitstream starting from the current access unit, inclusive, is conforming to this Recommendation | International Standard. + +The temporal level switching point SEI message shall not be present in access units with **temporal\_id** equal to 0. + +The temporal level switching point SEI message shall be included in a scalable nesting SEI message. For the scalable nesting SEI message that contains the temporal level switching point SEI message, **all\_layer\_representations\_in\_au\_flag** shall be equal to 1 or the value of **sei\_quality\_id[ i ]** shall be equal to 0 for all values of **i** in the range of 0 to **num\_layer\_representations\_minus1**, inclusive. + +The following semantics apply independently to each value of **sei\_dependency\_id[ i ]** indicated by the scalable nesting SEI message containing the temporal level switching point SEI message. The current access unit, i.e., the access unit associated with the temporal level switching point SEI message, may or may not contain a dependency representation with **dependency\_id** equal to **sei\_dependency\_id[ i ]**. When the current access unit contains a dependency representation with **dependency\_id** equal to **sei\_dependency\_id[ i ]**, the following semantics apply. + +The following semantics are specified in a way that they apply to a bitstream conforming to this Recommendation | International Standard for which **DependencyIdMax** for the current access unit is equal to **sei\_dependency\_id[ i ]**. + +Let the switch-to dependency representation be the dependency representation in the current access unit that has **dependency\_id** equal to **sei\_dependency\_id[ i ]** and let **maxFrameNum** be the value of **MaxFrameNum** for the SVC sequence parameter set that is the active SVC sequence parameter set for the current access unit (with **DependencyIdMax** equal to **sei\_dependency\_id[ i ]**). + +**delta\_frame\_num** indicates the difference between the **frame\_num** values of the switch-to dependency representation and the dependency representation with **dependency\_id** equal to **sei\_dependency\_id[ i ]** in the required access unit, as specified subsequently. The value of **delta\_frame\_num** shall be in the range of **1 – maxFrameNum** to **maxFrameNum – 1**, inclusive. + +Let **currFrameNum** be the **frame\_num** value of the switch-to dependency representation. The variable **requiredFrameNum** is set equal to **currFrameNum – delta\_frame\_num**. Let **lastIdrAU** be the most recent access unit in decoding order that contains a dependency representation with **dependency\_id** equal to **sei\_dependency\_id[ i ]** and **IdrPicFlag** equal to 1. The bitstream shall contain an access unit that succeeds the access unit **lastIdrAU** and precedes the current access unit in decoding order and contains a dependency representation with **frame\_num** equal to **requiredFrameNum** and **dependency\_id** equal to **sei\_dependency\_id[ i ]**. The most recent access unit in decoding order that contains a dependency + +representation with frame\_num equal to requiredFrameNum and dependency\_id equal to sei\_dependency\_id[ i ] is referred to as the required access unit. The required access unit shall have a value of temporal\_id that is equal to tId - 1. + +The current access unit and all subsequent access units in decoding order for which temporal\_id is less than or equal to tId shall not reference any of the following access units through inter prediction in the decoding process specified in clause F.8: + +- access units that precede the required access unit in decoding order and have temporal\_id equal to tId - 1, +- access units that precede the current access unit in decoding order and have temporal\_id equal to tId. + +NOTE 2 – The set of access units consisting of the current access unit and all access units with temporal\_id less than or equal to tId that follow the current access unit in decoding order can be decoded when all of the following access units, which precede the current access unit in decoding order, have been decoded: all access units required for decoding the required access unit (i.e., all access units that are directly or indirectly referenced through inter prediction in the decoding process for the required access unit), the required access unit, and all access units with temporal\_id less than tId that succeed the required access unit and precede the current access unit in decoding order. + +## F.14 Video usability information + +The specifications in Annex E apply with substituting SVC sequence parameter set for sequence parameter set. The VUI parameters and the constraints specified in Annex E apply to coded video sequences for which the SVC sequence parameter set becomes the active SVC sequence parameter set. + +Additionally, the following applies. + +### F.14.1 SVC VUI parameters extension syntax + +| svc_vui_parameters_extension() { | C | Descriptor | +|-------------------------------------------------------------------------------------------------------|---|------------| +| vui_ext_num_entries_minus1 | 0 | ue(v) | +| for ( i = 0; i <= vui_ext_num_entries_minus1; i++ ) { | | | +| vui_ext_dependency_id[ i ] | 0 | u(3) | +| vui_ext_quality_id[ i ] | 0 | u(4) | +| vui_ext_temporal_id[ i ] | 0 | u(3) | +| vui_ext_timing_info_present_flag[ i ] | 0 | u(1) | +| if( vui_ext_timing_info_present_flag[ i ] ) { | | | +| vui_ext_num_units_in_tick[ i ] | 0 | u(32) | +| vui_ext_time_scale[ i ] | 0 | u(32) | +| vui_ext_fixed_frame_rate_flag[ i ] | 0 | u(1) | +| } | | | +| vui_ext_nal_hrd_parameters_present_flag[ i ] | 0 | u(1) | +| if( vui_ext_nal_hrd_parameters_present_flag[ i ] ) | | | +| hrd_parameters( ) | 0 | | +| vui_ext_vcl_hrd_parameters_present_flag[ i ] | 0 | u(1) | +| if( vui_ext_vcl_hrd_parameters_present_flag[ i ] ) | | | +| hrd_parameters( ) | 0 | | +| if( vui_ext_nal_hrd_parameters_present_flag[ i ]
vui_ext_vcl_hrd_parameters_present_flag[ i ] ) | | | +| vui_ext_low_delay_hrd_flag[ i ] | 0 | u(1) | +| vui_ext_pic_struct_present_flag[ i ] | 0 | u(1) | +| } | | | +| } | | | + +### F.14.2 SVC VUI parameters extension semantics + +The SVC VUI parameters extension specifies timing information, HRD parameter sets, and the presence of picture structure information for subsets of coded video sequences (including the complete coded video sequences) conforming one or more of the profiles specified in Annex F. In Annex C it is specified which of the HRD parameter sets specified in the SVC VUI parameters extension are used for conformance checking. + +**vui\_ext\_num\_entries\_minus1** plus 1 specifies the number of information entries that are present in the SVC VUI parameters extension syntax structure. The value of **vui\_ext\_num\_entries\_minus1** shall be in the range of 0 to 1023, inclusive. Each information entry is associated with particular values of **temporal\_id**, **dependency\_id**, and **quality\_id** and may indicate timing information, NAL HRD parameters, VCL HRD parameters, and the presence of picture structure information for a particular subset of coded video sequences as specified in the following. + +**vui\_ext\_dependency\_id[ i ]** and **vui\_ext\_quality\_id[ i ]** indicate the maximum value of DQId for the i-th subset of coded video sequences. The maximum value of DQId for the i-th subset of coded video sequences is derived by **vui\_ext\_dependency\_id[ i ] + ( vui\_ext\_quality\_id[ i ] << 4 )**. + +**vui\_ext\_temporal\_id[ i ]** indicates the maximum value of **temporal\_id** for the i-th subset of coded video sequences. + +The SVC VUI parameters extension syntax structure shall not contain two or more information entries with identical values of **vui\_ext\_dependency\_id[ i ]**, **vui\_ext\_quality\_id[ i ]**, and **vui\_ext\_temporal\_id[ i ]**. + +The following syntax elements apply to the coded video sequences that are obtained by the invoking the sub-bitstream extraction process as specified in clause F.8.8.1 with **tIdTarget** equal to **vui\_ext\_temporal\_id[ i ]**, **dIdTarget** equal to **vui\_ext\_dependency\_id[ i ]**, and **qIdTarget** equal to **vui\_ext\_quality\_id[ i ]** as the inputs and the i-th subset of coded video sequences as the output. + +**vui\_ext\_timing\_info\_present\_flag[ i ]** equal to 1 specifies that **vui\_ext\_num\_units\_in\_tick[ i ]**, **vui\_ext\_time\_scale[ i ]**, and **vui\_ext\_fixed\_frame\_rate\_flag[ i ]** for the i-th subset of coded video sequences are present in the SVC VUI parameters extension. **vui\_ext\_timing\_info\_present\_flag[ i ]** equal to 0 specifies that **vui\_ext\_num\_units\_in\_tick[ i ]**, **vui\_ext\_time\_scale[ i ]**, and **vui\_ext\_fixed\_frame\_rate\_flag[ i ]** for the i-th subset of coded video sequences are not present in the SVC VUI parameters extension. + +The following syntax elements for the i-th subset of coded video sequences are specified using references to Annex E. For these syntax elements the same semantics and constraints as the ones specified in Annex E apply, as if these syntax elements **vui\_ext\_num\_units\_in\_tick[ i ]**, **vui\_ext\_time\_scale[ i ]**, **vui\_ext\_fixed\_frame\_rate\_flag[ i ]**, **vui\_ext\_nal\_hrd\_parameters\_present\_flag[ i ]**, **vui\_ext\_vcl\_hrd\_parameters\_present\_flag[ i ]**, **vui\_ext\_low\_delay\_hrd\_flag[ i ]**, and **vui\_ext\_pic\_struct\_present\_flag[ i ]** were present as the syntax elements **num\_units\_in\_tick**, **time\_scale**, **fixed\_frame\_rate\_flag**, **nal\_hrd\_parameters\_present\_flag**, **vcl\_hrd\_parameters\_present\_flag**, **low\_delay\_hrd\_flag**, and **pic\_struct\_present\_flag**, respectively, in the VUI parameters of the active SVC sequence parameter sets for the i-th subset of coded video sequences. + +**vui\_ext\_num\_units\_in\_tick[ i ]** specifies the value of **num\_units\_in\_tick**, as specified in clause E.2.1, for the i-th subset of coded video sequences. + +**vui\_ext\_time\_scale[ i ]** specifies the value of **time\_scale**, as specified in clause E.2.1, for the i-th subset of coded video sequences. + +**vui\_ext\_fixed\_frame\_rate\_flag[ i ]** specifies the value of **fixed\_frame\_rate\_flag**, as specified in clause E.2.1, for the i-th subset of coded video sequences. + +**vui\_ext\_nal\_hrd\_parameters\_present\_flag[ i ]** specifies the value of **nal\_hrd\_parameters\_present\_flag**, as specified in clause E.2.1, for the i-th subset of coded video sequences. + +When **vui\_ext\_nal\_hrd\_parameters\_present\_flag[ i ]** is equal to 1, NAL HRD parameters (clauses E.1.2 and E.2.2) for the i-th subset of coded video sequences immediately follow the flag. + +The variable **VuiExtNalHrdBpPresentFlag[ i ]** is derived as follows: + +- If any of the following is true, the value of **VuiExtNalHrdBpPresentFlag[ i ]** shall be set equal to 1: + - **vui\_ext\_nal\_hrd\_parameters\_present\_flag[ i ]** is present in the bitstream and is equal to 1, + - for the i-th subset of coded video sequences, the need for presence of buffering periods for NAL HRD operation to be present in the bitstream in buffering period SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of **VuiExtNalHrdBpPresentFlag[ i ]** shall be set equal to 0. + +**vui\_ext\_vcl\_hrd\_parameters\_present\_flag[ i ]** specifies the value of **vcl\_hrd\_parameters\_present\_flag**, as specified in clause E.2.1, for the i-th subset of coded video sequences. + +When **vui\_ext\_vcl\_hrd\_parameters\_present\_flag[ i ]** is equal to 1, VCL HRD parameters (clauses E.1.2 and E.2.2) for the i-th subset of coded video sequences immediately follow the flag. + +The variable **VuiExtVclHrdBpPresentFlag[ i ]** is derived as follows: + +- If any of the following is true, the value of **VuiExtVclHrdBpPresentFlag[ i ]** shall be set equal to 1: + +- `vui_ext_vcl_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, +- for the i-th subset of coded video sequences, the need for presence of buffering period parameters for VCL HRD operation in the bitstream in buffering period SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of `VuiExtVclHrdBpPresentFlag[ i ]` shall be set equal to 0. + +The variable `VuiExtCpbDpbDelaysPresentFlag[ i ]` is derived as follows: + +- If any of the following is true, the value of `VuiExtCpbDpbDelaysPresentFlag[ i ]` shall be set equal to 1: + - `vui_ext_nal_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, + - `vui_ext_vcl_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, + - for the i-th subset of coded video sequences, the need for presence of CPB and DPB output delays in the bitstream in picture timing SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of `VuiExtCpbDpbDelaysPresentFlag[ i ]` shall be set equal to 0. + +**`vui_ext_low_delay_hrd_flag[ i ]`** specifies the value of `low_delay_hrd_flag`, as specified in clause E.2.1, for the i-th subset of coded video sequences. + +**`vui_ext_pic_struct_present_flag[ i ]`** specifies the value of `pic_struct_present_flag`, as specified in clause E.2.1, for the i-th subset of coded video sequences. + +## Annex G + +### Multiview video coding + +(This annex forms an integral part of this Recommendation | International Standard.) + +This annex specifies multiview video coding, referred to as MVC. + +#### G.1 Scope + +Bitstreams and decoders conforming to the profile specified in this annex are completely specified in this annex with reference made to clauses 2 to 9 and Annexes A to F. + +#### G.2 Normative references + +The specifications in clause 2 apply. + +#### G.3 Definitions + +For the purpose of this annex, the following definitions apply in addition to the definitions in clause 3. These definitions are either not present in clause 3 or replace definitions in clause 3. + +- G.3.1 access unit:** A set of *NAL units* that are consecutive in *decoding order* and contain exactly one *primary coded picture* consisting of one or more *view components*. In addition to the *primary coded picture*, an access unit may also contain one or more *redundant coded pictures*, one *auxiliary coded picture*, or other *NAL units* not containing *slices* or *slice data partitions* of a *coded picture*. The decoding of an access unit always results in one *decoded picture* consisting of one or more *decoded view components*. +- G.3.2 anchor access unit:** An *access unit* in which the *primary coded picture* is an *anchor picture*. +- G.3.3 anchor picture:** A *coded picture* in which all *slices* may reference only *slices* within the same *access unit*, i.e., *inter-view prediction* may be used, but no *inter prediction* is used, and all following *coded pictures* in output order do not use *inter prediction* from any *picture* prior to the *coded picture* in *decoding order*. The value of *anchor\_pic\_flag* is equal to 1 for all the *prefix NAL units* (when present) and all the slice extension NAL units that are contained in an *anchor picture*. +- G.3.4 anchor view component:** A *view component* in an *anchor picture*. All *view components* in an *anchor picture* are *anchor view components*. +- G.3.5 associated NAL unit:** A *NAL unit* that immediately follows a *prefix NAL unit* in *decoding order*. +- G.3.6 base view:** A *view* that has the minimum value of *view order index* in a *coded video sequence*. The base view can be decoded independently of other *views*, does not use *inter-view prediction*, and contains *VCL NAL units* only with *nal\_unit\_type* equal to 1, 5, or 14. The *sub-bitstream* corresponding to the base view conforms to one or more of the *profiles* specified in Annex A. There is only one base view in a *coded video sequence*. +- G.3.7 coded slice MVC extension NAL unit:** A *coded slice NAL unit* that has *nal\_unit\_type* equal to 20. +- G.3.8 decoded view component:** A decoded view component is derived by decoding a *view component*. A decoded view component is either a *decoded frame view component*, or a *decoded field view component*. +- G.3.9 direct prediction:** An *inter prediction* or *inter-view prediction* for a *block* for which no *motion vector* is decoded. Two direct prediction modes are specified that are referred to as spatial direct prediction mode and temporal direct prediction mode. +- G.3.10 field view component:** A *view component* of a *field*. +- G.3.11 frame view component:** A *view component* of a *frame*. +- G.3.12 instantaneous decoding refresh (IDR) view component:** A *view component* in an *IDR picture*. All *view components* in an *IDR picture* are *IDR view components*. *IDR view components* are also *anchor view components*, and *inter-view prediction* may be used for *IDR view components* that are part of a *non-base view*. +- G.3.13 inter-view coding:** Coding of a *block*, *macroblock*, *slice*, or *picture* that uses *inter-view prediction*. + +- G.3.14 inter-view only reference component:** A *view component* coded with `nal_ref_idc` equal to 0 and `inter_view_flag` equal to 1. An inter-view only reference component contains samples that may be used for *inter-view prediction* in the *decoding process* of subsequent *view components* in *decoding order*, but are not used for *inter prediction* by any *view components*. Inter-view only reference components are *non-reference pictures*. +- G.3.15 inter-view prediction:** A *prediction* derived from decoded samples of *inter-view reference components* or *inter-view only reference components* for decoding another *view component* in the same *access unit*. +- G.3.16 inter-view prediction reference:** A collective term for *inter-view reference components* or *inter-view only reference components*. +- G.3.17 inter-view reference component:** A *view component* coded with `nal_ref_idc` greater than 0 and `inter_view_flag` equal to 1. An inter-view reference component contains samples that may be used for *inter prediction* of subsequent *pictures* in *decoding order* and *inter-view prediction* of subsequent *view components* in *decoding order*. Inter-view reference components are *reference pictures*. +- G.3.18 left view:** The left part of a picture coded in a frame-packed manner with the side-by-side frame packing arrangement type or the top part of a picture coded in a frame-packed manner with the top-bottom frame packing arrangement type. +- G.3.19 list 0 (list 1) prediction:** *Inter prediction* or *inter-view prediction* of the content of a *slice* using a *reference index* pointing into *reference picture list 0 (list 1)*. +- G.3.20 macroblock partition:** A *block* of *luma* samples and two corresponding *blocks* of *chroma* samples resulting from a *partitioning* of a *macroblock* for *inter prediction* or *inter-view prediction*. +- G.3.21 motion vector:** A two-dimensional vector used for *inter prediction* or *inter-view prediction* that provides an offset from the coordinates in the *decoded view component* to the coordinates in a *reference picture* or *inter-view only reference component*. +- G.3.22 MVC sequence parameter set:** A collective term for *sequence parameter set* or *subset sequence parameter set*. +- G.3.23 MVC sequence parameter set RBSP:** A collective term for *sequence parameter set RBSP* or *subset sequence parameter set RBSP*. +- G.3.24 non-anchor access unit:** An *access unit* that is not an *anchor access unit*. +- G.3.25 non-anchor picture:** A *coded picture* that is not an *anchor picture*. +- G.3.26 non-anchor view component:** A *view component* that is not an *anchor view component*. +- G.3.27 non-base view:** A *view* that is not the *base view*. *VCL NAL units* of a non-base view have `nal_unit_type` equal to 20. Decoding of *view components* in a non-base view may require the use of *inter-view prediction*. +- G.3.28 non-reference picture:** A *view component* coded with `nal_ref_idc` equal to 0. A non-reference picture is not used for *inter prediction* in the *decoding process* of any other *view components*. +- G.3.29 operation point:** An operation point is identified by a `temporal_id` value representing the *target temporal level* and a set of `view_id` values representing the *target output views*. One *operation point* is associated with a *sub-bitstream*, which consists of the *target output views* and all other *views* the *target output views* depend on, that is derived using the *sub-bitstream* extraction process as specified in clause G.8.5.3 with `tIdTarget` equal to the `temporal_id` value and `viewIdTargetList` consisting of the set of `view_id` values as inputs. More than one *operation point* may be associated with the same *sub-bitstream*. When the specification states "an *operation point* is decoded" it refers to the decoding of a *sub-bitstream* corresponding to the *operation point* and subsequent output of the *target output views*. +- G.3.30 picture order count:** A variable that is associated with each *field view component* and each *field* of a *frame view component* and has a value that is non-decreasing with increasing *field* position in *output order* in the same *view* relative to the first output *field* of the previous *IDR view component* in *decoding order* in the same *view* or relative to the first output *field* of the previous *view component*, in *decoding order* in the same *view*, that contains a *memory management control operation* that marks all *reference pictures* in the *view* as "unused for reference". +- G.3.31 prefix NAL unit:** A *NAL unit* with `nal_unit_type` equal to 14 that immediately precedes in *decoding order* a *NAL unit* with `nal_unit_type` equal to 1 or 5. The *NAL unit* that immediately follows in *decoding order* the prefix NAL unit is referred to as the *associated NAL unit*. The prefix NAL unit contains data associated with the *associated NAL unit*, which are considered to be part of the *associated NAL unit*. + +- G.3.32 reference picture:** A *view component* coded with nal\_ref\_idc greater than 0. A reference picture contains samples that may be used for *inter prediction* in the *decoding process* of subsequent *view components* in *decoding order*. A reference picture may be an *inter-view reference component*, in which case the samples contained in the reference picture may also be used for *inter-view prediction* in the *decoding process* of subsequent *view components* in *decoding order*. +- G.3.33 reference picture list:** A list of *reference pictures* and *inter-view only reference components* that are used for *inter prediction* or *inter-view prediction* of a *P* or *B slice*. For the *decoding process* of a *P slice*, there is one reference picture list. For the *decoding process* of a *B slice*, there are two reference picture lists. +- G.3.34 reference picture list 0:** A *reference picture list* used for *inter prediction* or *inter-view prediction* of a *P* or *B slice*. All *inter prediction* or *inter-view prediction* used for *P slices* uses reference picture list 0. Reference picture list 0 is one of two *reference picture lists* used for *inter prediction* or *inter-view prediction* for a *B slice*, with the other being *reference picture list 1*. +- G.3.35 reference picture list 1:** A *reference picture list* used for *inter prediction* or *inter-view prediction* of a *B slice*. Reference picture list 1 is one of two *reference picture lists* used for *inter prediction* or *inter-view prediction* for a *B slice*, with the other being *reference picture list 0*. +- G.3.36 reference picture marking:** Specifies, in the bitstream, how the *decoded view components* are marked for *inter prediction* or *inter-view prediction*. +- G.3.37 reference processing unit:** A functional unit that processes an *inter-view prediction reference* before the *inter-view prediction reference* is used for *inter-view prediction* in the *decoding process* of subsequent *view components* in *decoding order*. +- G.3.38 reference view index:** An index into a list of *anchor view components* or a list of *non-anchor view components* that are specified in the sequence parameter set MVC extension syntax structure and can be used for *inter-view prediction* as *list 0 prediction* or *list 1 prediction*. +- G.3.39 right view:** The right part of a picture coded in a frame-packed manner with the side-by-side frame packing arrangement type or the bottom part of a picture coded in a frame-packed manner with the top-bottom frame packing arrangement type. +- G.3.40 subset sequence parameter set:** A *syntax structure* containing *syntax elements* that apply to zero or more *non-base views* as determined by the content of a *seq\_parameter\_set\_id syntax element* found in the *picture parameter set* referred to by the *pic\_parameter\_set\_id syntax element* found in each *slice header* of *I*, *P*, and *B slices* of a *non-base view component*. +- G.3.41 target output view:** A *view* that is to be output. The target output views are either indicated by external means or, when not indicated by external means, the target output view is the *base view*. +- NOTE – The output views may be requested by a receiver and may be negotiated between the receiver and the sender. +- G.3.42 target temporal level:** The *target temporal level* of an *operation point* is the greatest value of temporal\_id of all *VCL NAL units* in the *sub-bitstream* associated with the *operation point*. +- G.3.43 view:** A sequence of *view components* associated with an identical value of view\_id. +- G.3.44 view component:** A *coded representation* of a *view* in a single *access unit*. When profile\_idc is equal to 134, a view contains samples of two distinct spatially packed constituent frames that are packed into one frame using one of the frame packing arrangement schemes as specified in clause D.2.26. +- G.3.45 view order index:** An index that indicates the *decoding order* of *view components* in an *access unit*. + +## G.4 Abbreviations + +For the purpose of this annex, the following abbreviations apply in addition to the abbreviations in clause 4. + +| | | +|-----|-------------------------------------------------| +| MFC | Multi-resolution Frame Compatible stereo coding | +| RPU | Reference Processing Unit | + +## G.5 Conventions + +The specifications in clause 5 apply. + +## **G.6 Source, coded, decoded and output data formats, scanning processes, and neighbouring relationships** + +The specifications in clause 6 apply with substitution of MVC sequence parameter set for sequence parameter set. + +## **G.7 Syntax and semantics** + +This clause specifies syntax and semantics for coded video sequences that conform to one or more of the profiles specified in this annex. + +### **G.7.1 Method of specifying syntax in tabular form** + +The specifications in clause 7.1 apply. + +### **G.7.2 Specification of syntax functions, categories, and descriptors** + +The specifications in clause 7.2 apply. + +### **G.7.3 Syntax in tabular form** + +#### **G.7.3.1 NAL unit syntax** + +The syntax table is specified in clause 7.3.1. + +##### **G.7.3.1.1 NAL unit header MVC extension syntax** + +| nal_unit_header_mvc_extension() { | C | Descriptor | +|------------------------------------------------|----------|-------------------| +| non_idr_flag | All | u(1) | +| priority_id | All | u(6) | +| view_id | All | u(10) | +| temporal_id | All | u(3) | +| anchor_pic_flag | All | u(1) | +| inter_view_flag | All | u(1) | +| reserved_one_bit | All | u(1) | +| } | | | + +#### **G.7.3.2 Raw byte sequence payloads and RBSP trailing bits syntax** + +##### **G.7.3.2.1 Sequence parameter set RBSP syntax** + +The syntax table is specified in clause 7.3.2.1. + +###### **G.7.3.2.1.1 Sequence parameter set data syntax** + +The syntax table is specified in clause 7.3.2.1.1. + +###### **G.7.3.2.1.1.1 Scaling list syntax** + +The syntax table is specified in clause 7.3.2.1.1.1. + +###### **G.7.3.2.1.2 Sequence parameter set extension RBSP syntax** + +The syntax table is specified in clause 7.3.2.1.2. + +###### **G.7.3.2.1.3 Subset sequence parameter set RBSP syntax** + +The syntax table is specified in clause 7.3.2.1.3. + +###### **G.7.3.2.1.4 Sequence parameter set MVC extension syntax** + +| seq_parameter_set_mvc_extension() { | C | Descriptor | +|-------------------------------------------------------------------------|---|------------| +| num_views_minus1 | 0 | ue(v) | +| for( i = 0; i <= num_views_minus1; i++ ) | | | +| view_id[ i ] | 0 | ue(v) | +| for( i = 1; i <= num_views_minus1; i++ ) { | | | +| num_anchor_refs_10[ i ] | 0 | ue(v) | +| for( j = 0; j < num_anchor_refs_10[ i ]; j++ ) | | | +| anchor_ref_10[ i ][ j ] | 0 | ue(v) | +| num_anchor_refs_11[ i ] | 0 | ue(v) | +| for( j = 0; j < num_anchor_refs_11[ i ]; j++ ) | | | +| anchor_ref_11[ i ][ j ] | 0 | ue(v) | +| } | | | +| for( i = 1; i <= num_views_minus1; i++ ) { | | | +| num_non_anchor_refs_10[ i ] | 0 | ue(v) | +| for( j = 0; j < num_non_anchor_refs_10[ i ]; j++ ) | | | +| non_anchor_ref_10[ i ][ j ] | 0 | ue(v) | +| num_non_anchor_refs_11[ i ] | 0 | ue(v) | +| for( j = 0; j < num_non_anchor_refs_11[ i ]; j++ ) | | | +| non_anchor_ref_11[ i ][ j ] | 0 | ue(v) | +| } | | | +| num_level_values_signalled_minus1 | 0 | ue(v) | +| for( i = 0; i <= num_level_values_signalled_minus1; i++ ) { | | | +| level_idc[ i ] | 0 | u(8) | +| num_applicable_ops_minus1[ i ] | 0 | ue(v) | +| for( j = 0; j <= num_applicable_ops_minus1[ i ]; j++ ) { | | | +| applicable_op_temporal_id[ i ][ j ] | 0 | u(3) | +| applicable_op_num_target_views_minus1[ i ][ j ] | 0 | ue(v) | +| for( k = 0; k <= applicable_op_num_target_views_minus1[ i ][ j ]; k++ ) | | | +| applicable_op_target_view_id[ i ][ j ][ k ] | 0 | ue(v) | +| applicable_op_num_views_minus1[ i ][ j ] | 0 | ue(v) | +| } | | | +| } | | | +| if( profile_idc == 134 ) { | | | +| mfc_format_idc | 0 | u(6) | +| if( mfc_format_idc == 0 mfc_format_idc == 1 ) { | | | +| default_grid_position_flag | 0 | u(1) | +| if( !default_grid_position_flag ) { | | | +| view0_grid_position_x | 0 | u(4) | +| view0_grid_position_y | 0 | u(4) | +| view1_grid_position_x | 0 | u(4) | +| view1_grid_position_y | 0 | u(4) | +| } | | | +| } | | | +| rpu_filter_enabled_flag | 0 | u(1) | +| if( !frame_mbs_only_flag ) | | | +| rpu_field_processing_flag | 0 | u(1) | +| } | | | +| } | | | + +#### **G.7.3.2.2 Picture parameter set RBSP syntax** + +The syntax table is specified in clause 7.3.2.2. + +#### **G.7.3.2.3 Supplemental enhancement information RBSP syntax** + +The syntax table is specified in clause 7.3.2.3. + +##### **G.7.3.2.3.1 Supplemental enhancement information message syntax** + +The syntax table is specified in clause 7.3.2.3.1. + +#### **G.7.3.2.4 Access unit delimiter RBSP syntax** + +The syntax table is specified in clause 7.3.2.4. + +#### **G.7.3.2.5 End of sequence RBSP syntax** + +The syntax table is specified in clause 7.3.2.5. + +#### **G.7.3.2.6 End of stream RBSP syntax** + +The syntax table is specified in clause 7.3.2.6. + +#### **G.7.3.2.7 Filler data RBSP syntax** + +The syntax table is specified in clause 7.3.2.7. + +#### **G.7.3.2.8 Slice layer without partitioning RBSP syntax** + +The syntax table is specified in clause 7.3.2.8. + +#### **G.7.3.2.9 Slice data partition RBSP syntax** + +Slice data partition syntax is not present in coded video sequences conforming to one or more of the profiles specified in this annex. + +#### **G.7.3.2.10 RBSP slice trailing bits syntax** + +The syntax table is specified in clause 7.3.2.10. + +#### **G.7.3.2.11 RBSP trailing bits syntax** + +The syntax table is specified in clause 7.3.2.11. + +#### **G.7.3.2.12 Prefix NAL unit RBSP syntax** + +The syntax table is specified in clause 7.3.2.12. + +#### **G.7.3.2.13 Slice layer extension RBSP syntax** + +The syntax table is specified in clause 7.3.2.13. + +### **G.7.3.3 Slice header syntax** + +The syntax table is specified in clause 7.3.3. + +#### **G.7.3.3.1 Reference picture list modification syntax** + +The syntax table is specified in clause 7.3.3.1. + +##### **G.7.3.3.1.1 Reference picture list MVC modification syntax** + +| ref_pic_list_mvc_modification() { | C | Descriptor | +|-------------------------------------------------------------------------------------------------------------------|----------|-------------------| +| if( slice_type % 5 != 2 && slice_type % 5 != 4 ) { | | | +|     ref_pic_list_modification_flag_l0 | 2 | u(1) | +|     if( ref_pic_list_modification_flag_l0 ) | | | +|     do { | | | +|         modification_of_pic_nums_idc | 2 | ue(v) | +|         if( modification_of_pic_nums_idc == 0
            modification_of_pic_nums_idc == 1 ) | | | +|             abs_diff_pic_num_minus1 | 2 | ue(v) | +|         else if( modification_of_pic_nums_idc == 2 ) | | | + +| | | | +|--------------------------------------------------------------------------------------|---|-------| +| long_term_pic_num | 2 | ue(v) | +| else if( modification_of_pic_nums_idc == 4
modification_of_pic_nums_idc == 5 ) | | | +| abs_diff_view_idx_minus1 | 2 | ue(v) | +| } while( modification_of_pic_nums_idc != 3 ) | | | +| } | | | +| if( slice_type % 5 == 1 ) { | | | +| ref_pic_list_modification_flag_l1 | 2 | u(1) | +| if( ref_pic_list_modification_flag_l1 ) | | | +| do { | | | +| modification_of_pic_nums_idc | 2 | ue(v) | +| if( modification_of_pic_nums_idc == 0
modification_of_pic_nums_idc == 1 ) | | | +| abs_diff_pic_num_minus1 | 2 | ue(v) | +| else if( modification_of_pic_nums_idc == 2 ) | | | +| long_term_pic_num | 2 | ue(v) | +| else if( modification_of_pic_nums_idc == 4
modification_of_pic_nums_idc == 5 ) | | | +| abs_diff_view_idx_minus1 | 2 | ue(v) | +| } while( modification_of_pic_nums_idc != 3 ) | | | +| } | | | +| } | | | + +#### G.7.3.3.2 Prediction weight table syntax + +The syntax table is specified in clause 7.3.3.2. + +#### G.7.3.3.3 Decoded reference picture marking syntax + +The syntax table is specified in clause 7.3.3.3. + +#### G.7.3.4 Slice data syntax + +The syntax table is specified in clause 7.3.4. + +#### G.7.3.5 Macroblock layer syntax + +The syntax table is specified in clause 7.3.5. + +##### G.7.3.5.1 Macroblock prediction syntax + +The syntax table is specified in clause 7.3.5.1. + +##### G.7.3.5.2 Sub-macroblock prediction syntax + +The syntax table is specified in clause 7.3.5.2. + +##### G.7.3.5.3 Residual data syntax + +The syntax table is specified in clause 7.3.5.3. + +###### G.7.3.5.3.1 Residual luma syntax + +The syntax table is specified in clause 7.3.5.3.1. + +###### G.7.3.5.3.2 Residual block CAVLC syntax + +The syntax table is specified in clause 7.3.5.3.2. + +###### G.7.3.5.3.3 Residual block CABAC syntax + +The syntax table is specified in clause 7.3.5.3.3. + +## G.7.4 Semantics + +Semantics associated with the syntax structures and syntax elements within these structures (in clause G.7.3 and in clause 7.3 by reference in clause G.7.3) are specified in this clause and by reference to clause 7.4. When the semantics of a syntax element are specified using a table or a set of tables, any values that are not specified in the table(s) shall not be present in the bitstream unless otherwise specified in this Recommendation | International Standard. + +### G.7.4.1 NAL unit semantics + +The semantics for the syntax elements in clause G.7.3.1 are specified in clause 7.4.1. The following specifications additionally apply. + +For NAL units with `nal_unit_type` equal to 14, `nal_ref_idc` shall be identical to the value of `nal_ref_idc` for the associated NAL unit, which follows the NAL unit with `nal_unit_type` equal to 14 in decoding order. + +The value of `nal_ref_idc` shall be identical for all VCL NAL units of a view component. + +#### G.7.4.1.1 NAL unit header MVC extension semantics + +The syntax elements `non_idr_flag`, `priority_id`, `view_id`, `temporal_id`, `anchor_pic_flag`, and `inter_view_flag`, when present in a prefix NAL unit, are considered to apply to the associated NAL unit. + +**`non_idr_flag`** equal to 0 specifies that the current access unit is an IDR access unit. + +The value of `non_idr_flag` shall be the same for all VCL NAL units of an access unit. When `non_idr_flag` is equal to 0 for a prefix NAL unit, the associated NAL unit shall have `nal_unit_type` equal to 5. When `non_idr_flag` is equal to 1 for a prefix NAL unit, the associated NAL unit shall have `nal_unit_type` equal to 1. + +When `nal_unit_type` is equal to 1 and the NAL unit is not immediately preceded by a NAL unit with `nal_unit_type` equal to 14, `non_idr_flag` shall be inferred to be equal to 1. When `nal_unit_type` is equal to 5 and the NAL unit is not immediately preceded by a NAL unit with `nal_unit_type` equal to 14, `non_idr_flag` shall be inferred to be equal to 0. + +When `nal_ref_idc` is equal to 0, the value of `non_idr_flag` shall be equal to 1. + +For NAL units in which `non_idr_flag` is present, the variable `IdrPicFlag` derived in clause 7.4.1 is modified by setting it equal to 1 when `non_idr_flag` is equal to 0, and setting it equal to 0 when `non_idr_flag` is equal to 1. + +**`priority_id`** specifies a priority identifier for the NAL unit. A lower value of `priority_id` specifies a higher priority. The assignment of values to `priority_id` is constrained by the sub-bitstream extraction process as specified in clause G.8.5.3. + +When `nal_unit_type` is equal to 1 or 5 and the NAL unit is not immediately preceded by a NAL unit with `nal_unit_type` equal to 14, `priority_id` shall be inferred to be equal to 0. + +NOTE 1 – The syntax element `priority_id` is not used by the decoding process specified in this Recommendation | International Standard. The syntax element `priority_id` may be used as determined by the application within the specified constraints. + +**`view_id`** specifies a view identifier for the NAL unit. NAL units with the same value of `view_id` belong to the same view. The assignment of values to `view_id` is constrained by the sub-bitstream extraction process as specified in clause G.8.5.3. + +When `nal_unit_type` is equal to 1 or 5 and the NAL unit is not immediately preceded by a NAL unit with `nal_unit_type` equal to 14, the value of `view_id` shall be inferred to be equal to 0. When the bitstream does contain NAL units with `nal_unit_type` equal to 1 or 5 that are not immediately preceded by a NAL unit with `nal_unit_type` equal to 14, it shall not contain data that result in a value of `view_id` for a view component of any non-base view that is equal to 0. + +The variable `VOIdx`, representing the view order index of the view identified by `view_id`, is set equal to the value of `i` for which the syntax element `view_id[ i ]` included in the referred subset sequence parameter set is equal to `view_id`. + +**`temporal_id`** specifies a temporal identifier for the NAL unit. + +When `nal_unit_type` is equal to 1 or 5 and the NAL unit is not immediately preceded by a NAL unit with `nal_unit_type` equal to 14, `temporal_id` shall be inferred to be equal to the value of `temporal_id` for the non-base views in the same access unit. + +The value of `temporal_id` shall be the same for all prefix and coded slice MVC extension NAL units of an access unit. When an access unit contains any NAL unit with `nal_unit_type` equal to 5 or `non_idr_flag` equal to 0, `temporal_id` shall be equal to 0. + +The assignment of values to `temporal_id` is further constrained by the sub-bitstream extraction process as specified in clause G.8.5.3. + +**`anchor_pic_flag`** equal to 1 specifies that the current access unit is an anchor access unit. + +When `nal_unit_type` is equal to 1 or 5 and the NAL unit is not immediately preceded by a NAL unit with `nal_unit_type` + +equal to 14, anchor\_pic\_flag shall be inferred to be equal to the value of anchor\_pic\_flag for the non-base views in the same access unit. + +When non\_idr\_flag is equal to 0, anchor\_pic\_flag shall be equal to 1. + +When nal\_ref\_idc is equal to 0, the value of anchor\_pic\_flag shall be equal to 0. + +The value of anchor\_pic\_flag shall be the same for all VCL NAL units of an access unit. + +**inter\_view\_flag** equal to 0 specifies that the current view component is not used for inter-view prediction by any other view component in the current access unit. inter\_view\_flag equal to 1 specifies that the current view component may be used for inter-view prediction by other view components in the current access unit. + +When nal\_unit\_type is equal to 1 or 5 and the NAL unit is not immediately preceded by a NAL unit with nal\_unit\_type equal to 14, inter\_view\_flag shall be inferred to be equal to 1. + +The value of inter\_view\_flag shall be the same for all VCL NAL units of a view component. + +**reserved\_one\_bit** shall be equal to 1. The value 0 for reserved\_one\_bit may be specified by future extension of this Recommendation | International Standard. Decoders shall ignore the value of reserved\_one\_bit. + +#### **G.7.4.1.2 Order of NAL units and association to coded pictures, access units, and video sequences** + +This clause specifies constraints on the order of NAL units in the bitstream. Any order of NAL units in the bitstream obeying these constraints is referred to in the text as the decoding order of NAL units. Within a NAL unit, the syntax in clauses 7.3, D.1, E.1, G.7.3, G.13.1, and G.14.1 specifies the decoding order of syntax elements. Decoders shall be capable of receiving NAL units and their syntax elements in decoding order. + +##### **G.7.4.1.2.1 Order of MVC sequence parameter set RBSPs and picture parameter set RBSPs and their activation** + +NOTE 1 – The sequence and picture parameter set mechanism decouples the transmission of infrequently changing information from the transmission of coded macroblock data. Sequence and picture parameter sets may, in some applications, be conveyed "out-of-band" using a reliable transport mechanism. + +A picture parameter set RBSP includes parameters that can be referred to by the coded slice NAL units of one or more view components of one or more coded pictures. + +Each picture parameter set RBSP is initially considered not active at the start of the operation of the decoding process. At most one picture parameter set RBSP is considered as the active picture parameter set RBSP at any given moment during the operation of the decoding process, and when any particular picture parameter set RBSP becomes the active picture parameter set RBSP, the previously-active picture parameter set RBSP (if any) is deactivated. + +In addition to the active picture parameter set RBSP, zero or more picture parameter set RBSPs may be specifically active for view components (with a particular value of VOIdx less than VOIdxMax) that may be referred to through inter-view prediction in decoding the view component with VOIdx equal to VOIdxMax. Such a picture parameter set RBSP is referred to as active view picture parameter set RBSP for the particular value of VOIdx. The restrictions on active picture parameter set RBSPs also apply to active view picture parameter set RBSPs for a particular value of VOIdx less than VOIdxMax. + +When a picture parameter set RBSP (with a particular value of pic\_parameter\_set\_id) is not the active picture parameter set RBSP and it is referred to by a coded slice NAL unit with VOIdx equal to VOIdxMax (using that value of pic\_parameter\_set\_id), it is activated. This picture parameter set RBSP is called the active picture parameter set RBSP until it is deactivated when another picture parameter set RBSP becomes the active picture parameter set RBSP. A picture parameter set RBSP, with that particular value of pic\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a picture parameter set RBSP (with a particular value of pic\_parameter\_set\_id) is not the active view picture parameter set for a particular value of VOIdx less than VOIdxMax and it is referred to by a coded slice NAL unit with the particular value of VOIdx (using that value of pic\_parameter\_set\_id), it is activated for view components with the particular value of VOIdx. This picture parameter set RBSP is called the active view picture parameter set RBSP for the particular value of VOIdx until it is deactivated when another picture parameter set RBSP becomes the active view picture parameter set RBSP for the particular value of VOIdx. A picture parameter set RBSP, with that particular value of pic\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +Any picture parameter set NAL unit containing the value of pic\_parameter\_set\_id for the active picture parameter set RBSP for a coded picture shall have the same content as that of the active picture parameter set RBSP for this coded picture unless it follows the last VCL NAL unit of this coded picture and precedes the first VCL NAL unit of another coded picture. Any picture parameter set NAL unit containing the value of pic\_parameter\_set\_id for the active view picture parameter set RBSP for a particular value of VOIdx less than VOIdxMax for a coded picture shall have the same content as that of the active view picture parameter set RBSP for the particular value of VOIdx for this coded picture. + +unless it follows the last VCL NAL unit of this coded picture and precedes the first VCL NAL unit of another coded picture. + +When a picture parameter set NAL unit with a particular value of `pic_parameter_set_id` is received, its content replaces the content of the previous picture parameter set NAL unit, in decoding order, with the same value of `pic_parameter_set_id` (when a previous picture parameter set NAL unit with the same value of `pic_parameter_set_id` was present in the bitstream). + +NOTE 2 – A decoder must be capable of simultaneously storing the contents of the picture parameter sets for all values of `pic_parameter_set_id`. The content of the picture parameter set with a particular value of `pic_parameter_set_id` is overwritten when a new picture parameter set NAL unit with the same value of `pic_parameter_set_id` is received. + +An MVC sequence parameter set RBSP includes parameters that can be referred to by one or more picture parameter set RBSPs or one or more buffering period SEI messages. + +Each MVC sequence parameter set RBSP is initially considered not active at the start of the operation of the decoding process. At most one MVC sequence parameter set RBSP is considered as the active MVC sequence parameter set RBSP at any given moment during the operation of the decoding process, and when any particular MVC sequence parameter set RBSP becomes the active MVC sequence parameter set RBSP, the previously-active MVC sequence parameter set RBSP (if any) is deactivated. + +In addition to the active MVC sequence parameter set RBSP, zero or more MVC sequence parameter set RBSPs may be specifically active for view components (with a particular value of `VOIdx` less than `VOIdxMax`) that may be referred to through inter-view prediction in decoding the view component with `VOIdx` equal to `VOIdxMax`. Such an MVC sequence parameter set RBSP is referred to as the active view MVC sequence parameter set RBSP for the particular value of `VOIdx`. The restrictions on active MVC sequence parameter set RBSPs also apply to active view MVC sequence parameter set RBSPs for a particular value of `VOIdx` less than `VOIdxMax`. + +For the following specification, the activating buffering period SEI message is specified as follows: + +- If `VOIdxMax` is equal to `VOIdxMin` and the access unit contains a buffering period SEI message not included in an MVC scalable nesting SEI message, this buffering period SEI message is the activating buffering period SEI message. +- Otherwise if `VOIdxMax` is not equal to `VOIdxMin` and the access unit contains a buffering period SEI message included in an MVC scalable nesting SEI message and associated with the operation point being decoded, this buffering period SEI message is the activating buffering period SEI message. +- Otherwise, the access unit does not contain an activating buffering period SEI message. + +When a sequence parameter set RBSP (`nal_unit_type` is equal to 7) with a particular value of `seq_parameter_set_id` is not already the active MVC sequence parameter set RBSP and it is referred to by activation of a picture parameter set RBSP (using that value of `seq_parameter_set_id`) and the picture parameter set RBSP is activated by a coded slice NAL unit with `nal_unit_type` equal to 1 or 5 (the picture parameter set RBSP becomes the active picture parameter set RBSP and `VOIdxMax` is equal to `VOIdxMin`) and the access unit does not contain an activating buffering period SEI message, it is activated. This sequence parameter set RBSP is called the active MVC sequence parameter set RBSP until it is deactivated when another MVC sequence parameter set RBSP becomes the active MVC sequence parameter set RBSP. A sequence parameter set RBSP, with that particular value of `seq_parameter_set_id`, shall be available to the decoding process prior to its activation. + +When a sequence parameter set RBSP (`nal_unit_type` is equal to 7) with a particular value of `seq_parameter_set_id` is not already the active MVC sequence parameter set RBSP and it is referred to by an activating buffering period SEI message (using that value of `seq_parameter_set_id`) that is not included in an MVC scalable nesting SEI message and `VOIdxMax` is equal to `VOIdxMin`, it is activated. This sequence parameter set RBSP is called the active MVC sequence parameter set RBSP until it is deactivated when another MVC sequence parameter set RBSP becomes the active MVC sequence parameter set RBSP. A sequence parameter set RBSP, with that particular value of `seq_parameter_set_id`, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (`nal_unit_type` is equal to 15) with a particular value of `seq_parameter_set_id` is not already the active MVC sequence parameter set RBSP and it is referred to by activation of a picture parameter set RBSP (using that value of `seq_parameter_set_id`) and the picture parameter set RBSP is activated by a coded slice MVC extension NAL unit (`nal_unit_type` is equal to 20) with `VOIdx` equal to `VOIdxMax` (the picture parameter set RBSP becomes the active picture parameter set RBSP) and the access unit does not contain an activating buffering period SEI message, it is activated. This subset sequence parameter set RBSP is called the active MVC sequence parameter set RBSP until it is deactivated when another MVC sequence parameter set RBSP becomes the active MVC sequence parameter set RBSP. A subset sequence parameter set RBSP, with that particular value of `seq_parameter_set_id`, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active MVC sequence parameter set RBSP and it is referred to by an activating buffering period SEI message (using that value of seq\_parameter\_set\_id) that is included in an MVC scalable nesting SEI message, it is activated. This subset sequence parameter set RBSP is called the active MVC sequence parameter set RBSP until it is deactivated when another MVC sequence parameter set RBSP becomes the active MVC sequence parameter set RBSP. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +NOTE 3 – The active MVC sequence parameter set RBSP is either a sequence parameter set RBSP or a subset sequence parameter set RBSP. Sequence parameter set RBSPs are activated by coded slice NAL units with nal\_unit\_type equal to 1 or 5 or buffering period SEI messages that are not included in an MVC scalable nesting SEI message. Subset sequence parameter sets are activated by coded slice MVC extension NAL units (nal\_unit\_type equal to 20) or buffering period SEI messages that are included in an MVC scalable nesting SEI message. A sequence parameter set RBSP and a subset sequence parameter set RBSP may have the same value of seq\_parameter\_set\_id. + +For the following specification, the activating view buffering period SEI message for a particular value of VOIdx is specified as follows: + +- If the access unit contains one or more than one buffering period SEI message included in an MVC scalable nesting SEI message and associated with an operation point for which the greatest VOIdx in the associated sub-bitstream is equal to the particular value of VOIdx, the first of these buffering period SEI messages, in decoding order, is the activating view buffering period SEI message for the particular value of VOIdx. +- Otherwise, if the access unit contains a buffering period SEI message not included in an MVC scalable nesting SEI message, this buffering period SEI message is the activating view buffering period SEI message for the particular value of VOIdx equal to VOIdxMin. +- Otherwise, the access unit does not contain an activating buffering period SEI message for the particular value of VOIdx. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active view MVC sequence parameter set RBSP for VOIdx equal to VOIdxMin and VOIdxMax is greater than VOIdxMin and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice NAL unit with nal\_unit\_type equal to 1 or 5 (the picture parameter set RBSP becomes the active view picture parameter set RBSP for VOIdx equal to VOIdxMin), it is activated for view components with VOIdx equal to VOIdxMin. This sequence parameter set RBSP is called the active view MVC sequence parameter set RBSP for VOIdx equal to VOIdxMin until it is deactivated when another MVC sequence parameter set RBSP becomes the active view MVC sequence parameter set RBSP for VOIdx equal to VOIdxMin or when decoding an access unit with VOIdxMax equal to VOIdxMin, whichever is earlier. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active view MVC sequence parameter set RBSP for VOIdx equal to VOIdxMin and VOIdxMax is greater than VOIdxMin and it is referred to by an activating view buffering period SEI message (using that value of seq\_parameter\_set\_id) that is not included in an MVC scalable nesting SEI message, the sequence parameter set RBSP is activated for view components with VOIdx equal to VOIdxMin. This sequence parameter set RBSP is called the active view MVC sequence parameter set RBSP for VOIdx equal to VOIdxMin until it is deactivated when another MVC sequence parameter set RBSP becomes the active view MVC sequence parameter set RBSP for VOIdx equal to VOIdxMin or when decoding an access unit with VOIdxMax equal to VOIdxMin. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active view MVC sequence parameter set RBSP for a particular value of VOIdx less than VOIdxMax and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice MVC extension NAL unit (nal\_unit\_type equal to 20) with the particular value of VOIdx (the picture parameter set RBSP becomes the active view picture parameter set RBSP for the particular value of VOIdx), it is activated for view components with the particular value of VOIdx. This subset sequence parameter set RBSP is called the active view MVC sequence parameter set RBSP for the particular value of VOIdx until it is deactivated when another MVC sequence parameter set RBSP becomes the active view MVC sequence parameter set RBSP for the particular value of VOIdx or when decoding an access unit with VOIdxMax less than or equal to the particular value of VOIdx. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active view MVC sequence parameter set RBSP for a particular value of VOIdx less than VOIdxMax and it is referred to by an activating view buffering period SEI message (using that value of + +seq\_parameter\_set\_id) that is included in an MVC scalable nesting SEI message and associated with the particular value of VOIdx, this subset sequence parameter set RBSP is activated for view components with the particular value of VOIdx. This subset sequence parameter set RBSP is called the active view MVC sequence parameter set RBSP for the particular value of VOIdx until it is deactivated when another MVC sequence parameter set RBSP becomes the active view MVC sequence parameter set RBSP for the particular value of VOIdx or when decoding an access unit with VOIdxMax less than or equal to the particular value of VOIdx. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +An MVC sequence parameter set RBSP that includes a value of profile\_idc not specified in Annex A or Annex G shall not be referred to by activation of a picture parameter set RBSP as the active picture parameter set RBSP or as active view picture parameter set RBSP (using that value of seq\_parameter\_set\_id) or referred to by a buffering period SEI message (using that value of seq\_parameter\_set\_id). An MVC sequence parameter set RBSP including a value of profile\_idc not specified in Annex A or Annex G is ignored in the decoding for profiles specified in Annex A or Annex G. + +It is a requirement of bitstream conformance that the following constraints are obeyed: + +- For each particular value of VOIdx, all coded slice NAL units of a coded video sequence shall refer to the same value of seq\_parameter\_set\_id (via the picture parameter set RBSP that is referred to by the value of pic\_parameter\_set\_id). +- The value of seq\_parameter\_set\_id in a buffering period SEI message that is not included in an MVC scalable nesting SEI message shall be identical to the value of seq\_parameter\_set\_id in the picture parameter set RBSP that is referred to by coded slice NAL units (with nal\_unit\_type equal to 1 or 5) (via the value of pic\_parameter\_set\_id) in the same access unit. +- The value of seq\_parameter\_set\_id in a buffering period SEI message that is included in an MVC scalable nesting SEI message and is associated with a particular value of VOIdx shall be identical to the value of seq\_parameter\_set\_id in the picture parameter set RBSP that is referred to by coded slice NAL units with the particular value of VOIdx (via the value of pic\_parameter\_set\_id) in the same access unit. + +The active view MVC sequence parameter set RBSPs for different values of VOIdx may be the same MVC sequence parameter set RBSP. The active MVC sequence parameter set RBSP and an active view MVC sequence parameter set RBSP for a particular value of VOIdx may be the same MVC sequence parameter set RBSP. + +When the active MVC sequence parameter set RBSP for a coded picture is a sequence parameter set RBSP, any sequence parameter set RBSP in the coded video sequence containing this coded picture and with the value of seq\_parameter\_set\_id for the active MVC sequence parameter set RBSP shall have the same content as that of the active MVC sequence parameter set RBSP. + +When the active MVC sequence parameter set RBSP for a coded picture is a subset sequence parameter set RBSP, any subset sequence parameter set RBSP in the coded video sequence containing this coded picture and with the value of seq\_parameter\_set\_id for the active MVC sequence parameter set RBSP shall have the same content as that of the active MVC sequence parameter set RBSP. + +For each particular value of VOIdx, the following applies: + +- When the active view MVC sequence parameter set RBSP for a coded picture is a sequence parameter set RBSP, any sequence parameter set RBSP in the coded video sequence containing this coded picture and with the value of seq\_parameter\_set\_id for the active view MVC sequence parameter set RBSP shall have the same content as that of the active view MVC sequence parameter set RBSP. +- When the active view MVC sequence parameter set RBSP for a coded picture is a subset sequence parameter set RBSP, any subset sequence parameter set RBSP in the coded video sequence containing this coded picture and with the value of seq\_parameter\_set\_id for the active view MVC sequence parameter set RBSP shall have the same content as that of the active view MVC sequence parameter set RBSP. + +NOTE 4 – If picture parameter set RBSPs or MVC sequence parameter set RBSPs are conveyed within the bitstream, these constraints impose an order constraint on the NAL units that contain the picture parameter set RBSPs or MVC sequence parameter set RBSPs, respectively. Otherwise (picture parameter set RBSPs or MVC sequence parameter set RBSPs are conveyed by other means not specified in this Recommendation | International Standard), they must be available to the decoding process in a timely fashion such that these constraints are obeyed. + +When a sequence parameter set NAL unit with a particular value of seq\_parameter\_set\_id is received, its content replaces the content of the previous sequence parameter set NAL unit, in decoding order, with the same value of seq\_parameter\_set\_id (when a previous sequence parameter set NAL unit with the same value of seq\_parameter\_set\_id was present in the bitstream). When a subset sequence parameter set NAL unit with a particular value of seq\_parameter\_set\_id is received, its content replaces the content of the previous subset sequence parameter set NAL unit, in decoding order, with the same value of seq\_parameter\_set\_id (when a previous subset sequence parameter set NAL unit with the same value of seq\_parameter\_set\_id was present in the bitstream). + +NOTE 5 – A decoder must be capable of simultaneously storing the contents of the sequence parameter sets and subset sequence parameter sets for all values of `seq_parameter_set_id`. The content of the sequence parameter set with a particular value of `seq_parameter_set_id` is overwritten when a new sequence parameter set NAL unit with the same value of `seq_parameter_set_id` is received, and the content of the subset sequence parameter set with a particular value of `seq_parameter_set_id` is overwritten when a new subset sequence parameter set NAL unit with the same value of `seq_parameter_set_id` is received. + +When present, a sequence parameter set extension RBSP includes parameters having a similar function to those of a sequence parameter set RBSP. For purposes of establishing constraints on the syntax elements of the sequence parameter set extension RBSP and for purposes of determining activation of a sequence parameter set extension RBSP, the sequence parameter set extension RBSP shall be considered part of the preceding sequence parameter set RBSP with the same value of `seq_parameter_set_id`. When a sequence parameter set RBSP is present that is not followed by a sequence parameter set extension RBSP with the same value of `seq_parameter_set_id` prior to the activation of the sequence parameter set RBSP, the sequence parameter set extension RBSP and its syntax elements shall be considered not present for the active MVC sequence parameter set RBSP. The contents of sequence parameter set extension RBSPs only apply when the base view, which conforms to one or more of the profiles specified in Annex A, of a coded video sequence conforming to one or more profiles specified in Annex G is decoded. Subset sequence parameter set RBSPs shall not be followed by a sequence parameter set extension RBSP. + +NOTE 6 – Sequence parameter sets extension RBSPs are not considered to be part of a subset sequence parameter set RBSP and subset sequence parameter set RBSPs must not be followed by a sequence parameter set extension RBSP. + +For view components with `VOIdx` equal to `VOIdxMax`, all constraints that are expressed on the relationship between the values of the syntax elements (and the values of variables derived from those syntax elements) in MVC sequence parameter sets and picture parameter sets and other syntax elements are expressions of constraints that apply only to the active MVC sequence parameter set and the active picture parameter set. For view components with a particular value of `VOIdx` less than `VOIdxMax`, all constraints that are expressed on the relationship between the values of the syntax elements (and the values of variables derived from those syntax elements) in MVC sequence parameter sets and picture parameter sets and other syntax elements are expressions of constraints that apply only to the active view MVC sequence parameter set and the active view picture parameter set for the particular value of `VOIdx`. If any MVC sequence parameter set RBSP having `profile_idc` equal to the value of one of the `profile_idc` values specified in Annex A or Annex G is present that is never activated in the bitstream (i.e., it never becomes the active MVC sequence parameter set or an active view MVC sequence parameter set), its syntax elements shall have values that would conform to the specified constraints if it were activated by reference in an otherwise-conforming bitstream. If any picture parameter set RBSP is present that is never activated in the bitstream (i.e., it never becomes the active picture parameter set or an active view picture parameter set), its syntax elements shall have values that would conform to the specified constraints if it were activated by reference in an otherwise-conforming bitstream. + +During operation of the decoding process (see clause G.8), for view components with `VOIdx` equal to `VOIdxMax`, the values of parameters of the active picture parameter set and the active MVC sequence parameter set shall be considered in effect. For view components with a particular value of `VOIdx` less than `VOIdxMax`, the values of the parameters of the active view picture parameter set and the active view MVC sequence parameter set for the particular value of `VOIdx` shall be considered in effect. For interpretation of SEI messages that apply to the entire access unit or the view component with `VOIdx` equal to `VOIdxMax`, the values of the parameters of the active picture parameter set and the active MVC sequence parameter set for the same access unit shall be considered in effect unless otherwise specified in the SEI message semantics. For interpretation of SEI messages that apply to view components with a particular value of `VOIdx` less than `VOIdxMax`, the values of the parameters of the active view picture parameter set and the active view MVC sequence parameter set for the particular value of `VOIdx` for the same access unit shall be considered in effect unless otherwise specified in the SEI message semantics. + +#### **G.7.4.1.2.2 Order of access units and association to coded video sequences** + +The specification of clause 7.4.1.2.2 applies with the following modifications. + +The first access unit of the bitstream shall only contain coded slice NAL units with `nal_unit_type` equal to 5 or `non_idr_flag` equal to 0. + +The order of NAL units and coded pictures and their association to access units is described in clause G.7.4.1.2.3. + +#### **G.7.4.1.2.3 Order of NAL units and coded pictures and association to access units** + +The specification of clause 7.4.1.2.3 applies with the following modifications. + +NOTE – Some bitstreams that conform to one or more profiles specified in this annex do not conform to any profile specified in Annex A (prior to operation of the base view extraction process specified in clause G.8.5.4). As specified in clauses 7.4.1 and 7.4.1.2.3, for the profiles specified in Annex A, NAL units with `nal_unit_type` equal to 20 are classified as non-VCL NAL units that must be preceded within each access unit by at least one NAL unit with `nal_unit_type` in the range of 1 to 5, inclusive. For this reason, any bitstream that conforms to one or more profiles specified in this annex does not conform to any profile specified in Annex A when it contains any of the following: + +- any access unit that does not contain any NAL units with `nal_unit_type` equal to 1 or 5, but contains one or more NAL units with `nal_unit_type` equal to 6, 7, 8, 9, or 15; + +- any access unit in which one or more NAL units with nal\_unit\_type equal to 7, 8, or 15 is present after the last NAL unit in the access unit with nal\_unit\_type equal to 1 or 5. + +The association of VCL NAL units to primary or redundant coded pictures is specified in clause G.7.4.1.2.5. + +The constraints for the detection of the first VCL NAL unit of a primary coded picture are specified in clause G.7.4.1.2.4. + +The constraint expressed in clause 7.4.1.2.3 on the order of a buffering period SEI message is replaced by the following constraints. + +- When an SEI NAL unit containing a buffering period SEI message is present, the following applies: + - If the buffering period SEI message is the only buffering period SEI message in the access unit and it is not included in an MVC scalable nesting SEI message, the buffering period SEI message shall be the first SEI message payload of the first SEI NAL unit in the access unit. + - Otherwise (the buffering period SEI message is not the only buffering period SEI message in the access unit or it is included in an MVC scalable nesting SEI message), the following constraints are specified: + - When a buffering period SEI message that is not included in an MVC scalable nesting SEI message is present, this buffering period SEI message shall be the only SEI message payload of the first SEI NAL unit in the access unit. + - An MVC scalable nesting SEI message that includes a buffering period SEI message shall not include any other SEI messages and shall be the only SEI message inside the SEI NAL unit. + - All SEI NAL units that precede an SEI NAL unit that contains an MVC scalable nesting SEI message with a buffering period SEI message as payload in an access unit shall only contain buffering period SEI messages or MVC scalable nesting SEI messages with a buffering period SEI message as payload. + +Each prefix NAL unit shall be immediately followed by a NAL unit with nal\_unit\_type equal to 1 or 5. + +#### **G.7.4.1.2.4 Detection of the first VCL NAL unit of a primary coded picture** + +This clause specifies constraints on VCL NAL unit syntax that are sufficient to enable the detection of the first VCL NAL unit of each primary coded picture. + +The first VCL NAL unit of the primary coded picture of the current access unit, in decoding order, shall be different from the last VCL NAL unit of the primary coded picture of the previous access unit, in decoding order, in one or more of the following ways: + +- view\_id of the first VCL NAL unit of the primary coded picture of the current access unit is different from view\_id of the last VCL NAL unit of the primary coded picture of the previous access unit, and VOIdx of the first VCL NAL unit of the primary coded picture of the current access unit is less than VOIdx of the last VCL NAL unit of the primary coded picture of the previous access unit. +- view\_id of the first VCL NAL unit of the primary coded picture of the current access unit is equal to view\_id of the last VCL NAL unit of the primary coded picture of the previous access unit, and any of the conditions specified in clause 7.4.1.2.4 is fulfilled. + +#### **G.7.4.1.2.5 Order of VCL NAL units and association to coded pictures** + +Each VCL NAL unit is part of a coded picture. + +Let voIdx be the value of VOIdx of any particular VCL NAL unit. The order of the VCL NAL units within a coded picture is constrained as follows: + +- For all VCL NAL units following this particular VCL NAL unit, the value of VOIdx shall be greater than or equal to voIdx. + +For each set of VCL NAL units within a view component, the following applies: + +- If arbitrary slice order, as specified in Annex A or clause G.10, is allowed, coded slice NAL units of a view component may have any order relative to each other. +- Otherwise (arbitrary slice order is not allowed), coded slice NAL units of a slice group shall not be interleaved with coded slice NAL units of another slice group and the order of coded slice NAL units within a slice group shall be in the order of increasing macroblock address for the first macroblock of each coded slice NAL unit of the same slice group. + +NAL units having nal\_unit\_type equal to 12 may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having nal\_unit\_type equal to 0 or in the range of 24 to 31, inclusive, which are unspecified, may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having nal\_unit\_type in the range of 21 to 23, inclusive, which are reserved, shall not precede the first VCL NAL unit of the primary coded picture within the access unit (when specified in the future by ITU-T | ISO/IEC). + +#### **G.7.4.2 Raw byte sequence payloads and RBSP trailing bits semantics** + +##### **G.7.4.2.1 Sequence parameter set RBSP semantics** + +The semantics specified in clause 7.4.2.1 apply. + +###### **G.7.4.2.1.1 Sequence parameter set data semantics** + +For all syntax elements other than max\_num\_ref\_frames, the semantics specified in clause 7.4.2.1.1 apply with the substitution of MVC sequence parameter set for sequence parameter set. All constraints specified in clause 7.4.2.1.1 apply only to the view components for which the MVC sequence parameter set is the active MVC sequence parameter set or the active view MVC sequence parameter set as specified in clause G.7.4.1.2.1. + +For each coded video sequence, the active MVC sequence parameter set and all active view MVC sequence parameter sets (if any) shall have the same values of pic\_width\_in\_mbs\_minus1, pic\_height\_in\_map\_units\_minus1, and frame\_mbs\_only\_flag. + +When the seq\_parameter\_set\_data() syntax structure is present in a subset sequence parameter set RBSP and vui\_parameters\_present\_flag is equal to 1, timing\_info\_present\_flag shall be equal to 0, nal\_hrd\_parameters\_present\_flag shall be equal to 0, vcl\_hrd\_parameters\_present\_flag shall be equal to 0, and pic\_struct\_present\_flag shall be equal to 0. The value of 1 for timing\_info\_present\_flag, nal\_hrd\_parameters\_present\_flag, vcl\_hrd\_parameters\_present\_flag, and pic\_struct\_present\_flag for subset sequence parameter set RBSPs is reserved for future use by ITU-T | ISO/IEC. When timing\_info\_present\_flag is equal to 1, decoders shall ignore the values of the directly following num\_units\_in\_tick, time\_scale, fixed\_frame\_rate\_flag syntax elements. When nal\_hrd\_parameters\_present\_flag is equal to 1, decoders shall ignore the value of the syntax elements in the directly following hrd\_parameters() syntax structure. When vcl\_hrd\_parameters\_present\_flag is equal to 1, decoders shall ignore the value of the syntax elements in the directly following hrd\_parameters() syntax structure. + +If max\_num\_ref\_frames is included in a sequence parameter set, the semantics specified in clause 7.4.2.1.1 apply. Otherwise (max\_num\_ref\_frames is included in a subset sequence parameter set), the following is specified: + +**max\_num\_ref\_frames** specifies the maximum number of short-term and long-term reference frames, complementary reference field pairs, and non-paired reference fields that may be used by the decoding process for inter prediction of any view component in the coded video sequence. max\_num\_ref\_frames also determines the sliding window size of the sliding window operation as specified in clause G.8.3. The value of max\_num\_ref\_frames shall be in the range of 0 to 16, inclusive. + +###### **G.7.4.2.1.1.1 Scaling list semantics** + +The semantics specified in clause 7.4.2.1.1.1 apply. + +##### **G.7.4.2.1.2 Sequence parameter set extension RBSP semantics** + +The semantics specified in clause 7.4.2.1.2 apply. Additionally, the following applies. + +Sequence parameter set extension RBSPs can only follow sequence parameter set RBSPs in decoding order. Subset sequence parameter set RBSPs shall not be followed by a sequence parameter set extension RBSP. The contents of sequence parameter set extension RBSPs only apply when the base view, which conforms to one or more of the profiles specified in Annex A, of a coded video sequence conforming to one or more profiles specified in Annex G is decoded. + +##### **G.7.4.2.1.3 Subset sequence parameter set RBSP semantics** + +The semantics specified in clause 7.4.2.1.3 apply. + +##### **G.7.4.2.1.4 Sequence parameter set MVC extension semantics** + +The sequence parameter set MVC extension specifies inter-view dependency relationships for the coded video sequence. The sequence parameter set MVC extension also specifies level values for a subset of the operation points for the coded video sequence. All sequence parameter set MVC extensions that are referred to by a coded video sequence shall be identical. + +Some views identified by view\_id[ i ] may not be present in the coded video sequence. + +NOTE 1 – Some views or temporal subsets described by the sequence parameter set MVC extension may have been removed from the original coded video sequence, hence may not be present in the coded video sequence. However, the information in the sequence parameter set MVC extension always applies to the remaining views and temporal subsets. + +**num\_views\_minus1** plus 1 specifies the maximum number of coded views in the coded video sequence. The value of **num\_view\_minus1** shall be in the range of 0 to 1023, inclusive. + +NOTE 2 – The actual number of views in the coded video sequence may be less than **num\_views\_minus1** plus 1. + +**view\_id[ i ]** specifies the **view\_id** of the view with **VOIdx** equal to **i**. The value of **view\_id[ i ]** shall be in the range of 0 to 1023, inclusive. + +**num\_anchor\_refs\_10[ i ]** specifies the number of view components for inter-view prediction in the initial reference picture list **RefPicList0** (which is derived as specified in clause G.8.2.1) in decoding anchor view components with **VOIdx** equal to **i**. The value of **num\_anchor\_refs\_10[ i ]** shall not be greater than **Min( 15, num\_views\_minus1 )**. The value of **num\_anchor\_refs\_10[ 0 ]** shall be equal to 0. + +**anchor\_ref\_10[ i ][ j ]** specifies the **view\_id** of the **j**-th view component for inter-view prediction in the initial reference picture list **RefPicList0** (which is derived as specified in clause G.8.2.1) in decoding anchor view components with **VOIdx** equal to **i**. The value of **anchor\_ref\_10[ i ][ j ]** shall be in the range of 0 to 1023, inclusive. + +**num\_anchor\_refs\_11[ i ]** specifies the number of view components for inter-view prediction in the initial reference picture list **RefPicList1** (which is derived as specified in clause G.8.2.1) in decoding anchor view components with **VOIdx** equal to **i**. The value of **num\_anchor\_refs\_11[ i ]** shall not be greater than **Min( 15, num\_views\_minus1 )**. The value of **num\_anchor\_refs\_11[ 0 ]** shall be equal to 0. + +**anchor\_ref\_11[ i ][ j ]** specifies the **view\_id** of the **j**-th view component for inter-view prediction in the initial reference picture list **RefPicList1** (which is derived as specified in clause G.8.2.1) in decoding an anchor view component with **VOIdx** equal to **i**. The value of **anchor\_ref\_11[ i ][ j ]** shall be in the range of 0 to 1023, inclusive. + +**num\_non\_anchor\_refs\_10[ i ]** specifies the number of view components for inter-view prediction in the initial reference picture list **RefPicList0** (which is derived as specified in clause G.8.2.1) in decoding non-anchor view components with **VOIdx** equal to **i**. The value of **num\_non\_anchor\_refs\_10[ i ]** shall not be greater than **Min( 15, num\_views\_minus1 )**. The value of **num\_non\_anchor\_refs\_10[ 0 ]** shall be equal to 0. + +**non\_anchor\_ref\_10[ i ][ j ]** specifies the **view\_id** of the **j**-th view component for inter-view prediction in the initial reference picture list **RefPicList0** (which is derived as specified in clause G.8.2.1) in decoding non-anchor view components with **VOIdx** equal to **i**. The value of **non\_anchor\_ref\_10[ i ][ j ]** shall be in the range of 0 to 1023, inclusive. + +**num\_non\_anchor\_refs\_11[ i ]** specifies the number of view components for inter-view prediction in the initial reference picture list **RefPicList1** (which is derived as specified in clause G.8.2.1) in decoding non-anchor view components with **VOIdx** equal to **i**. The value of **num\_non\_anchor\_refs\_11[ i ]** shall not be greater than **Min( 15, num\_views\_minus1 )**. The value of **num\_non\_anchor\_refs\_11[ 0 ]** shall be equal to 0. + +**non\_anchor\_ref\_11[ i ][ j ]** specifies the **view\_id** of the **j**-th view component for inter-view prediction in the initial reference picture list **RefPicList1** (which is derived as specified in clause G.8.2.1) in decoding non-anchor view components with **VOIdx** equal to **i**. The value of **non\_anchor\_ref\_11[ i ][ j ]** shall be in the range of 0 to 1023, inclusive. + +For any particular view with **view\_id** equal to **vId1** and **VOIdx** equal to **vOIdx1** and another view with **view\_id** equal to **vId2** and **VOIdx** equal to **vOIdx2**, when **vId2** is equal to the value of one of **non\_anchor\_ref\_10[ vOIdx1 ][ j ]** for all **j** in the range of 0 to **num\_non\_anchor\_refs\_10[ vOIdx1 ]**, exclusive, or one of **non\_anchor\_ref\_11[ vOIdx1 ][ j ]** for all **j** in the range of 0 to **num\_non\_anchor\_refs\_11[ vOIdx1 ]**, exclusive, **vId2** shall also be equal to the value of one of **anchor\_ref\_10[ vOIdx1 ][ j ]** for all **j** in the range of 0 to **num\_anchor\_refs\_10[ vOIdx1 ]**, exclusive, or one of **anchor\_ref\_11[ vOIdx1 ][ j ]** for all **j** in the range of 0 to **num\_anchor\_refs\_11[ vOIdx1 ]**, exclusive. + +NOTE 3 – The inter-view dependency for non-anchor view components is a subset of that for anchor view components. + +**num\_level\_values\_signalled\_minus1** plus 1 specifies the number of level values signalled for the coded video sequence. The value of **num\_level\_values\_signalled\_minus1** shall be in the range of 0 to 63, inclusive. + +**level\_idc[ i ]** specifies the **i**-th level value signalled for the coded video sequence. + +**num\_applicable\_ops\_minus1[ i ]** plus 1 specifies the number of operation points to which the level indicated by **level\_idc[ i ]** applies. The value of **num\_applicable\_ops\_minus1[ i ]** shall be in the range of 0 to 1023, inclusive. + +**applicable\_op\_temporal\_id[ i ][ j ]** specifies the **temporal\_id** of the **j**-th operation point to which the level indicated by **level\_idc[ i ]** applies. + +**applicable\_op\_num\_target\_views\_minus1[ i ][ j ]** plus 1 specifies the number of target output views for the **j**-th operation point to which the level indicated by **level\_idc[ i ]** applies. The value of **applicable\_op\_num\_target\_views\_minus1[ i ][ j ]** shall be in the range of 0 to 1023, inclusive. + +**applicable\_op\_target\_view\_id[ i ][ j ][ k ]** specifies the k-th target output view for the j-th operation point to which the level indicated by **level\_idc[ i ]** applies. The value of **applicable\_op\_target\_view\_id[ i ][ j ][ k ]** shall be in the range of 0 to 1023, inclusive. + +Let **maxTId** be the greatest **temporal\_id** of all NAL units in the coded video sequence, and **vId** be **view\_id** of any view in the coded video sequence. There shall be one set of **applicable\_op\_temporal\_id[ i ][ j ]**, **applicable\_op\_num\_target\_views\_minus1[ i ][ j ]**, and **applicable\_op\_target\_view\_id[ i ][ j ][ k ]**, for any i and j and all k for the i and j, in which **applicable\_op\_temporal\_id[ i ][ j ]** is equal to **maxTId**, **applicable\_op\_num\_target\_views\_minus1[ i ][ j ]** is equal to 0, and **applicable\_op\_target\_view\_id[ i ][ j ][ k ]** is equal to **vId**. + +NOTE 4 – The above constraint ensures that the level that applies to each operation point consisting of only one target output view with the greatest highest **temporal\_id** in the coded video sequence is signalled by one of the **level\_idc[ i ]** for all i. + +NOTE 5 – Some operation points identified by **applicable\_op\_temporal\_id[ i ][ j ]**, **applicable\_op\_num\_target\_views\_minus1[ i ][ j ]**, and **applicable\_op\_target\_view\_id[ i ][ j ][ k ]**, for all i, j, and k, may not be present in the coded video sequence. + +**applicable\_op\_num\_views\_minus1[ i ][ j ]** plus 1 specifies the number of views required for decoding the target output views corresponding to the j-th operation point to which the level indicated by **level\_idc[ i ]** applies. The number of views specified by **applicable\_op\_num\_views\_minus1** includes the target output views and the views that the target output views depend on as specified by the sub-bitstream extraction process in clause G.8.5 with **tIdTarget** equal to **applicable\_op\_temporal\_id[ i ][ j ]** and **viewIdTargetList** equal to the list of **applicable\_op\_target\_view\_id[ i ][ j ][ k ]** for all k in the range of 0 to **applicable\_op\_num\_target\_views\_minus1[ i ][ j ]**, inclusive, as inputs. The value of **applicable\_op\_num\_views\_minus1[ i ][ j ]** shall be in the range of 0 to 1023, inclusive. + +**mfc\_format\_idc** specifies the frame packing arrangement type for view components of the base view and the corresponding frame packing arrangement type for view components in the non-base view. The semantics of **mfc\_format\_idc** equal to 0 and 1 are specified by Table G-1. + +In bitstreams conforming to this version of this Specification, the value of **mfc\_format\_idc** shall be equal to 0 or 1. Values of **mfc\_format\_idc** in the range of 2..63 are reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore the coded video sequence when the value of **mfc\_format\_idc** is greater than 1. + +**Table G-1 – Association between frame packing arrangement type and syntax elements** + +| mfc_format_idc | Constraints on the frame packing arrangement SEI message syntax for view components of the base view | Corresponding frame packing arrangement type inferred for view components of the non-base view | +|-----------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| 0 | frame_packing_arrangement_type shall be equal to 3 (side-by-side) | frame_packing_arrangement_type equal to 4 (top-bottom) | +| 1 | frame_packing_arrangement_type shall be equal to 4 (top-bottom) | frame_packing_arrangement_type equal to 3 (side-by-side) | + +**default\_grid\_position\_flag** equal to 0 specifies that the syntax elements **view0\_grid\_position\_x**, **view0\_grid\_position\_y**, **view1\_grid\_position\_x**, and **view1\_grid\_position\_y** are present. **default\_grid\_position\_flag** equal to 1 specifies that **view0\_grid\_position\_x**, **view0\_grid\_position\_y**, **view1\_grid\_position\_x**, and **view1\_grid\_position\_y** are not present. + +**view0\_grid\_position\_x** has the same semantics as specified in clause D.2.26 for the **frame0\_grid\_position\_x** syntax element. The value of **view0\_grid\_position\_x** shall be equal to 4, 8 or 12. + +**view0\_grid\_position\_y** has the same semantics as specified in clause D.2.26 for the **frame0\_grid\_position\_y** syntax element. The value of **view0\_grid\_position\_y** shall be equal to 4, 8 or 12. + +**view1\_grid\_position\_x** has the same semantics as specified in clause D.2.26 for the **frame1\_grid\_position\_x** syntax element. The value of **view1\_grid\_position\_x** shall be equal to 4, 8 or 12. + +**view1\_grid\_position\_y** has the same semantics as specified in clause D.2.26 for the **frame1\_grid\_position\_y** syntax element. The value of **view1\_grid\_position\_y** shall be equal to 4, 8 or 12. + +When **default\_grid\_position\_flag** is equal to 1, the values of **view0\_grid\_position\_x**, **view0\_grid\_position\_y**, **view1\_grid\_position\_x**, and **view1\_grid\_position\_y** are inferred as follows: + +- If **mfc\_format\_idc** is equal to 0, the following applies: + - **view0\_grid\_position\_x** is inferred to be equal to 4. + - **view0\_grid\_position\_y** is inferred to be equal to 8. + - **view1\_grid\_position\_x** is inferred to be equal to 12. + - **view1\_grid\_position\_y** is inferred to be equal to 8. + +- Otherwise (mfc\_format\_idc is equal to 1), the following applies: + - view0\_grid\_position\_x is inferred to be equal to 8. + - view0\_grid\_position\_y is inferred to be equal to 4. + - view1\_grid\_position\_x is inferred to be equal to 8. + - view1\_grid\_position\_y is inferred to be equal to 12. + +When mfc\_format\_idc is present, the following applies: + +- It is a requirement of bitstream conformance that each coded view component of the base view shall be associated with a frame packing arrangement SEI message for which all of the following constraints apply: + - frame\_packing\_arrangement\_type is equal to the value specified by Table G-1 for view components of the base view. + - quincunx\_sampling\_flag is equal to 0. + - content\_interpretation\_type is equal to 1. + - spatial\_flipping\_flag is equal to 0. + - frame0\_grid\_position\_x, frame0\_grid\_position\_y, frame1\_grid\_position\_x, and frame1\_grid\_position\_y are equal to view0\_grid\_position\_x, view0\_grid\_position\_y, view1\_grid\_position\_x, and view1\_grid\_position\_y, respectively. +- It is a requirement of bitstream conformance that no frame packing arrangement SEI message shall be associated with any view component of a non-base view. For each view component of a non-base view, a frame packing arrangement is inferred as follows: + - frame\_packing\_arrangement\_type is equal to the value specified by Table G-1 for the view components of the non-base view. + - quincunx\_sampling\_flag is equal to 0. + - content\_interpretation\_type is equal to 1. + - spatial\_flipping\_flag is equal to 0. + +NOTE 6 – These constraints also apply to cases where a coded view component would be associated with a frame packing arrangement SEI message that is present in an access unit that is earlier in decoding order than the access unit containing the coded view component. + +**rpu\_filter\_enabled\_flag** equal to 1 specifies that a downsampling filter process and an upsampling filter process are used to generate each colour component of an inter-view prediction reference. rpu\_filter\_enabled\_flag equal to 0 specifies that all sample values for each colour component of an inter-view prediction reference are set equal to 128. + +**rpu\_field\_processing\_flag** equal to 0 specifies that each inter-view prediction reference with field\_pic\_flag equal to 0 is processed as a frame when processed by the RPU. rpu\_field\_processing\_flag equal to 1 specifies that each inter-view prediction reference with field\_pic\_flag equal to 0 is processed as two fields when processed by the RPU. When not present, the value of rpu\_field\_processing\_flag is inferred to be equal to 0. + +#### G.7.4.2.2 Picture parameter set RBSP semantics + +The semantics specified in clause 7.4.2.2 apply with substituting MVC sequence parameter set for sequence parameter set. All constraints specified in clause 7.4.2.2 apply only to the view components for which the picture parameter set is the active picture parameter set or the active view picture parameter set as specified in clause G.7.4.1.2.1. + +**weighted\_bipred\_idc** has the same semantics as specified in clause 7.4.2.2 with the following modification. + +When there is at least one inter-view prediction reference, which belongs to the same access unit as the current view component, in RefPicList0 or RefPicList1, weighted\_bipred\_idc shall not be equal to 2. + +#### G.7.4.2.3 Supplemental enhancement information RBSP semantics + +The semantics specified in clause 7.4.2.3 apply. + +##### G.7.4.2.3.1 Supplemental enhancement information message semantics + +The semantics specified in clause 7.4.2.3.1 apply. + +#### G.7.4.2.4 Access unit delimiter RBSP semantics + +The semantics specified in clause 7.4.2.4 apply. + +NOTE – The value of primary\_pic\_type applies to the slice\_type values in all slice headers of the primary coded picture, including the slice\_type syntax elements in all NAL units with nal\_unit\_type equal to 1, 5, or 20. NAL units with nal\_unit\_type equal to 2 are not present in bitstreams conforming to any of the profiles specified in this annex. + +#### **G.7.4.2.5 End of sequence RBSP semantics** + +The semantics specified in clause 7.4.2.5 apply. + +#### **G.7.4.2.6 End of stream RBSP semantics** + +The semantics specified in clause 7.4.2.6 apply. + +#### **G.7.4.2.7 Filler data RBSP semantics** + +The semantics specified in clause 7.4.2.7 apply with the following addition. + +Filler data NAL units shall be considered to contain the syntax elements `priority_id`, `view_id`, and `temporal_id` with values that are inferred as follows: + +1. Let `prevMvcNalUnit` be the most recent NAL unit in decoding order that has `nal_unit_type` equal to 14 or 20. +NOTE – The most recent NAL unit in decoding order with `nal_unit_type` equal to 14 or 20 always belongs to the same access unit as the filler data NAL unit. +2. The values of `priority_id`, `view_id`, and `temporal_id` for the filler data NAL unit are inferred to be equal to the values of `priority_id`, `view_id`, and `temporal_id`, respectively, of the NAL unit `prevMvcNalUnit`. + +#### **G.7.4.2.8 Slice layer without partitioning RBSP semantics** + +The semantics specified in clause 7.4.2.8 apply. + +#### **G.7.4.2.9 Slice data partition RBSP semantics** + +Slice data partition syntax is not present in bitstreams conforming to one or more of the profiles specified in this annex. + +#### **G.7.4.2.10 RBSP slice trailing bits semantics** + +The semantics specified in clause 7.4.2.10 apply with the following modifications. + +Let `NumBytesInVclNALUnits` be the sum of the values of `NumBytesInNALUnit` for all VCL NAL units of a view component and let `BinCountsInNALUnits` be the number of times that the parsing process function `DecodeBin()`, specified in clause 9.3.3.2, is invoked to decode the contents of all VCL NAL units of the view component. When `entropy_coding_mode_flag` is equal to 1, it is a requirement of bitstream conformance that `BinCountsInNALUnits` shall not exceed $( 32 \div 3 ) * \text{NumBytesInVclNALUnits} + ( \text{RawMbBits} * \text{PicSizeInMbs} ) \div 32$ . + +NOTE – The constraint on the maximum number of bins resulting from decoding the contents of the slice layer NAL units of a view component can be met by inserting a number of `cabac_zero_word` syntax elements to increase the value of `NumBytesInVclNALUnits`. Each `cabac_zero_word` is represented in a NAL unit by the three-byte sequence 0x000003 (as a result of the constraints on NAL unit contents that result in requiring inclusion of an `emulation_prevention_three_byte` for each `cabac_zero_word`). + +#### **G.7.4.2.11 RBSP trailing bits semantics** + +The semantics specified in clause 7.4.2.11 apply. + +#### **G.7.4.2.12 Prefix NAL unit RBSP semantics** + +The semantics specified in clause 7.4.2.12 apply. + +#### **G.7.4.2.13 Slice layer extension RBSP semantics** + +The semantics specified in clause 7.4.2.13 apply. + +### **G.7.4.3 Slice header semantics** + +The semantics specified in clause 7.4.3 apply with the following modifications. + +All constraints specified in clause 7.4.3 apply only to the view components with the same value of `VOIdx`. + +The value of the following MVC sequence parameter set syntax elements shall be the same across all coded slice NAL units of an access unit: `chroma_format_idc`. + +The value of the following slice header syntax elements shall be the same across all coded slice NAL units of an access unit: `field_pic_flag` and `bottom_field_flag`. + +**frame\_num** is used as an identifier for view components and is represented by `log2_max_frame_num_minus4 + 4` bits in the bitstream. + +`frame_num` is constrained as specified in clause 7.4.3 where this constraint applies to view components with `view_id` equal to the current value of `view_id`. + +**direct\_spatial\_mv\_pred\_flag** has the same semantics as specified in clause 7.4.3 with the following modification. + +When RefPicList1[ 0 ] is an inter-view reference component or an inter-view only reference component, which belongs to the same access unit as the current view component, **direct\_spatial\_mv\_pred\_flag** shall be equal to 1. + +**num\_ref\_idx\_l0\_active\_minus1** has the same semantics as specified in clause 7.4.3 with the following modification. + +The range of **num\_ref\_idx\_l0\_active\_minus1** is specified as follows: + +- If **num\_views\_minus1** is equal to 1, the following applies: + - If **field\_pic\_flag** is equal to 0, **num\_ref\_idx\_l0\_active\_minus1** shall be in the range of 0 to 7, inclusive. When **MbaffFrameFlag** is equal to 1, **num\_ref\_idx\_l0\_active\_minus1** is the maximum index value for the decoding of frame macroblocks and $2 * \text{num\_ref\_idx\_l0\_active\_minus1} + 1$ is the maximum index value for the decoding of field macroblocks. + - Otherwise (**field\_pic\_flag** is equal to 1), **num\_ref\_idx\_l0\_active\_minus1** shall be in the range of 0 to 15, inclusive. +- Otherwise (**num\_views\_minus1** is greater than 1), the following applies: + - If **field\_pic\_flag** is equal to 0, **num\_ref\_idx\_l0\_active\_minus1** shall be in the range of 0 to 15, inclusive. When **MbaffFrameFlag** is equal to 1, **num\_ref\_idx\_l0\_active\_minus1** is the maximum index value for the decoding of frame macroblocks and $2 * \text{num\_ref\_idx\_l0\_active\_minus1} + 1$ is the maximum index value for the decoding of field macroblocks. + - Otherwise (**field\_pic\_flag** is equal to 1), **num\_ref\_idx\_l0\_active\_minus1** shall be in the range of 0 to 31, inclusive. + +**num\_ref\_idx\_l1\_active\_minus1** has the same semantics as specified in clause 7.4.3 with the following modification. + +The range of **num\_ref\_idx\_l1\_active\_minus1** is constrained as specified in the semantics for **num\_ref\_idx\_l0\_active\_minus1** in this clause with l0 and list 0 replaced by l1 and list 1, respectively. + +#### G.7.4.3.1 Reference picture list modification semantics + +The semantics specified in clause 7.4.3.1 apply with the following modifications. + +**ref\_pic\_list\_modification\_flag\_l0** equal to 1 specifies that the syntax element **modification\_of\_pic\_nums\_idc** is present for specifying reference picture list 0. **ref\_pic\_list\_modification\_flag\_l0** equal to 0 specifies that this syntax element is not present. + +When **ref\_pic\_list\_modification\_flag\_l0** is equal to 1, the number of times that **modification\_of\_pic\_nums\_idc** is not equal to 3 following **ref\_pic\_list\_modification\_flag\_l0** shall not exceed **num\_ref\_idx\_l0\_active\_minus1** + 1. + +When RefPicList0[ **num\_ref\_idx\_l0\_active\_minus1** ] in the initial reference picture list produced as specified in clause G.8.2.1 is equal to "no reference picture", **ref\_pic\_list\_modification\_flag\_l0** shall be equal to 1 and **modification\_of\_pic\_nums\_idc** shall not be equal to 3 until RefPicList0[ **num\_ref\_idx\_l0\_active\_minus1** ] in the modified list produced as specified in clause G.8.2.2 is not equal to "no reference picture". + +**ref\_pic\_list\_modification\_flag\_l1** equal to 1 specifies that the syntax element **modification\_of\_pic\_nums\_idc** is present for specifying reference picture list 1. **ref\_pic\_list\_modification\_flag\_l1** equal to 0 specifies that this syntax element is not present. + +When **ref\_pic\_list\_modification\_flag\_l1** is equal to 1, the number of times that **modification\_of\_pic\_nums\_idc** is not equal to 3 following **ref\_pic\_list\_modification\_flag\_l1** shall not exceed **num\_ref\_idx\_l1\_active\_minus1** + 1. + +When decoding a slice with **slice\_type** equal to 1 or 6 and RefPicList1[ **num\_ref\_idx\_l1\_active\_minus1** ] in the initial reference picture list produced as specified in clause G.8.2.1 is equal to "no reference picture", **ref\_pic\_list\_modification\_flag\_l1** shall be equal to 1 and **modification\_of\_pic\_nums\_idc** shall not be equal to 3 until RefPicList1[ **num\_ref\_idx\_l1\_active\_minus1** ] in the modified list produced as specified in clause G.8.2.2 is not equal to "no reference picture". + +##### G.7.4.3.1.1 Reference picture list MVC modification semantics + +The semantics specified in clause 7.4.3.1 apply with the following modified semantics of **modification\_of\_pic\_nums\_idc**. In addition, the semantics of **abs\_diff\_view\_idx\_minus1** specified below apply. + +**modification\_of\_pic\_nums\_idc** together with **abs\_diff\_pic\_num\_minus1**, **long\_term\_pic\_num**, or **abs\_diff\_view\_idx\_minus1** specifies which of the reference pictures or inter-view only reference components are re-mapped. The values of **modification\_of\_pic\_nums\_idc** are specified in Table G-2. The value of the first **modification\_of\_pic\_nums\_idc** that follows immediately after **ref\_pic\_list\_modification\_flag\_l0** or + +ref\_pic\_list\_modification\_flag\_11 shall not be equal to 3. + +**Table G-2 – modification\_of\_pic\_nums\_idc operations for modification of reference picture lists** + +| modification_of_pic_nums_idc | Modification specified | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| 0 | abs_diff_pic_num_minus1 is present and corresponds to a difference to subtract from a picture number prediction value | +| 1 | abs_diff_pic_num_minus1 is present and corresponds to a difference to add to a picture number prediction value | +| 2 | long_term_pic_num is present and specifies the long-term picture number for a reference picture | +| 3 | End loop for modification of the initial reference picture list | +| 4 | abs_diff_view_idx_minus1 is present and corresponds to a difference to subtract from a prediction value of the reference view index | +| 5 | abs_diff_view_idx_minus1 is present and corresponds to a difference to add to a prediction value of the reference view index | + +**abs\_diff\_view\_idx\_minus1** plus 1 specifies the absolute difference between the reference view index to put to the current index in the reference picture list and the prediction value of the reference view index. + +Let currVOIdx be the VOIdx of the current view component, and let intViewIdx be the reference view index of the target inter-view prediction reference to put to the current index in RefPicListX (X is 0 or 1). Depending on whether the current view component is an anchor view component, the following applies: + +- If the current view component is an anchor view component, the view\_id of the target inter-view prediction reference is equal to anchor\_ref\_IX[ currVOIdx ][ intViewIdx ]. For anchor view components with VOIdx equal to currVOIdx, abs\_diff\_view\_idx\_minus1 shall be in the range of 0 to Max(0, num\_anchor\_refs\_IX[ currVOIdx ] – 1 ), inclusive. +- Otherwise (the current view component is not an anchor view component), the view\_id of the target inter-view prediction reference is equal to non\_anchor\_ref\_IX[ currVOIdx ][ intViewIdx ]. For non-anchor view components with VOIdx equal to currVOIdx, abs\_diff\_view\_idx\_minus1 shall be in the range of 0 to Max(0, num\_non\_anchor\_refs\_IX[ currVOIdx ] – 1 ), inclusive. + +The allowed values of abs\_diff\_view\_idx\_minus1 are further restricted as specified in clause G.8.2.2.3. + +#### **G.7.4.3.2 Prediction weight table semantics** + +The semantics specified in clause 7.4.3.2 apply. + +#### **G.7.4.3.3 Decoded reference picture marking semantics** + +The semantics specified in clause 7.4.3.3 apply to each view independently, with "sequence parameter set" being replaced by "MVC sequence parameter set", and "primary coded picture" being replaced by "view component of the primary coded picture". + +#### **G.7.4.4 Slice data semantics** + +The semantics specified in clause 7.4.4 apply. + +#### **G.7.4.5 Macroblock layer semantics** + +The semantics specified in clause 7.4.5 apply. + +##### **G.7.4.5.1 Macroblock prediction semantics** + +The semantics specified in clause 7.4.5.1 apply. + +##### **G.7.4.5.2 Sub-macroblock prediction semantics** + +The semantics specified in clause 7.4.5.2 apply. + +##### **G.7.4.5.3 Residual data semantics** + +The semantics specified in clause 7.4.5.3 apply. + +#### **G.7.4.5.3.1 Residual luma semantics** + +The semantics specified in clause 7.4.5.3.1 apply. + +#### **G.7.4.5.3.2 Residual block CAVLC semantics** + +The semantics specified in clause 7.4.5.3.2 apply. + +#### **G.7.4.5.3.3 Residual block CABAC semantics** + +The semantics specified in clause 7.4.5.3.3 apply. + +### **G.8 MVC decoding process** + +This clause specifies the decoding process for an access unit of a coded video sequence conforming to one or more of the profiles specified in Annex G. Specifically, this clause specifies how the decoded picture with multiple view components is derived from syntax elements and global variables that are derived from NAL units in an access unit when the decoder is decoding the operation point identified by the target temporal level and the target output views. + +The decoding process is specified such that all decoders shall produce numerically identical results for the target output views. Any decoding process that produces identical results for the target output views to the process described here conforms to the decoding process requirements of this Recommendation | International Standard. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the decoding process specified in this clause and all child processes invoked from the process specified in this clause are the syntax elements and derived upper-case variables for the current access unit. + +The target output views are either specified by external means not specified in this Specification, or, when not specified by external means, there shall be one target output view which is the base view. Let OutputVOIdxList be the list of VOIdx values, in increasing order of VOIdx, of all the target output views in one access unit. The list OutputVOIdxList shall not change within a coded video sequence. + +All sub-bitstreams that can be derived using the sub-bitstream extraction process with pIdTarget equal to any value in the range of 0 to 63, inclusive, tldTarget equal to any value in the range of 0 to 7, inclusive, viewIdTargetList consisting of any one or more viewIdTarget's identifying the views in the bitstream as inputs as specified in clause G.8.5 shall result in a set of coded video sequences, with each coded video sequence conforming to one or more of the profiles specified in Annex A and Annex G. + +Let vOIdxList be a list of integer values specifying the VOIdx values of the view components of the access unit. The variable VOIdxMax is set equal to the maximum value of the entries in the list vOIdxList, and the variable vOIdxMin is set to the minimum value of the entries in the list vOIdxList. VOIdxMax shall be the same for all access units within a coded video sequence. vOIdxMin shall be the same for all anchor access units within a coded video sequence. When the current access unit is an anchor access unit, the variable VOIdxMin is set to vOIdxMin. + +The multiview video decoding process specified in this clause is repeatedly invoked for each view component with VOIdx from vOIdxMin to VOIdxMax, inclusive, which is present in the list vOIdxList, in increasing order of VOIdx. + +Outputs of the multiview video decoding process are decoded samples of the current primary coded picture including all decoded view components. + +For each view component, the specifications in clause 8 apply, with the decoding processes for picture order count, reference picture lists construction and decoded reference picture marking being modified in clauses G.8.1, G.8.2 and G.8.3, respectively. The MVC inter prediction and inter-view prediction process is specified in clause G.8.4. The specification of sub-bitstreams is specified in clause G.8.5. Additionally, when mfc\_format\_idc is present, the recommended enhanced-resolution picture reconstruction process is as described in clause G.8.6. + +#### **G.8.1 MVC decoding process for picture order count** + +The process specified in this clause is invoked for a particular view with view order index VOIdx. The specifications in clause 8.2.1 apply independently for each view, with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". + +The following constraints shall be obeyed: + +- When the view components of an access unit have field\_pic\_flag equal to 0 or (field\_pic\_flag equal to 1 and bottom\_field\_flag equal to 0), it is a requirement of bitstream conformance that the bitstream shall not contain data that result in different values of TopFieldOrderCnt for the view components of the access unit. + +- When the view components of an access unit have `field_pic_flag` equal to 0 or (`field_pic_flag` equal to 1 and `bottom_field_flag` equal to 1), it is a requirement of bitstream conformance that the bitstream shall not contain data that result in different values of `BottomFieldOrderCnt` for the view components of the access unit. + +### G.8.2 MVC decoding process for reference picture lists construction + +This process is invoked at the beginning of the decoding process for each P, SP or B slice. + +During the invocation of this process, when clauses 8.2.4.1 and 8.2.4.2 are invoked, only the reference pictures having the same value of `view_id` as the current slice are considered. All clauses of clause 8 are invoked with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". + +Decoded reference pictures are marked as "used for short-term reference" or "used for long-term reference" as specified in clause G.8.3. Short-term reference pictures are identified by the values of `frame_num`. Long-term reference pictures are assigned a long-term frame index as specified in clause G.8.3. + +In addition to reference pictures marked as "used for short-term reference" or "used for long-term reference", inter-view reference components and inter-view only reference components of the current access unit may also be included in a reference picture list. Inter-view reference components and inter-view only reference components are identified by the value of `view_id`. + +Clause 8.2.4.1 is invoked to specify + +- the assignment of variables `FrameNum`, `FrameNumWrap`, and `PicNum` to each of the short-term reference pictures, and +- the assignment of variable `LongTermPicNum` to each of the long-term reference pictures. + +Reference pictures and, when present, inter-view only reference components, are addressed through reference indices as specified in clause 8.2.4.1. A reference index is an index into a reference picture list. When decoding a P or SP slice, there is a single reference picture list `RefPicList0`. When decoding a B slice, there is a second independent reference picture list `RefPicList1` in addition to `RefPicList0`. + +At the beginning of the decoding process for each slice, reference picture list `RefPicList0`, and for B slices `RefPicList1`, are derived as specified by the following ordered steps: + +1. Depending on `non_idr_flag`, the following applies: + - If `non_idr_flag` is equal to 1, the initial reference picture list `RefPicList0` and for B slices `RefPicList1` are derived as specified in clause 8.2.4.2. + - Otherwise (`non_idr_flag` is equal to 0), all (`num_ref_idx_l0_active_minus1 + 1`) entries of the initial reference picture list `RefPicList0` are set equal to "no reference picture" and, for B slices, all (`num_ref_idx_l1_active_minus1 + 1`) entries of the initial reference picture list `RefPicList1` are set equal to "no reference picture". +2. Inter-view reference components or inter-view only reference components are appended to the initial reference picture list `RefPicList0` and for B slices `RefPicList1` as specified in clause G.8.2.1. +3. When `ref_pic_list_modification_flag_l0` is equal to 1 or, when decoding a B slice, `ref_pic_list_modification_flag_l1` is equal to 1, the reference picture list `RefPicList0` and for B slices `RefPicList1` are modified as specified in clause G.8.2.2. + +NOTE – The modification process for reference picture lists specified in clause G.8.2.2 allows the contents of `RefPicList0` and for B slices `RefPicList1` to be modified in a flexible fashion. In particular, it is possible for a reference picture that is currently marked "used for reference" to be inserted into `RefPicList0` and for B slices `RefPicList1` even when the reference picture is not in the initial reference picture list derived as specified in clauses 8.2.4.2 and G.8.2.1. + +The number of entries in the modified reference picture list `RefPicList0` is `num_ref_idx_l0_active_minus1 + 1`, and for B slices the number of entries in the modified reference picture list `RefPicList1` is `num_ref_idx_l1_active_minus1 + 1`. A reference picture or inter-view only reference component may appear at more than one index in the modified reference picture lists `RefPicList0` or `RefPicList1`. + +During the invocation of the process specified in clause G.8.2.1, an inter-view prediction reference appended to `RefPicListX` (with X being 0 or 1) may not exist. However, an inter-view prediction reference that does not exist shall not be in the modified `RefPicListX` after the invocation of the process specified in clause G.8.2.2. + +When `anchor_pic_flag` is equal to 1, the bitstream shall not contain data that result in any entry of the reference picture list `RefPicList0` or, for B slices, any entry of the reference picture list `RefPicList1` that does not represent a view component of the current access unit. + +### G.8.2.1 Initialization process for reference picture list for inter-view prediction references + +Inputs to this process are a reference picture list RefPicListX (with X being 0 or 1), inter\_view\_flag and view dependency information that has been decoded from the seq\_parameter\_set\_mvc\_extension(). + +The output of this process is a possibly modified reference picture list RefPicListX, which is still referred to as the initial reference picture list RefPicListX. + +With i being the value of VOIdx for the current slice, inter-view reference components and inter-view only reference components (the corresponding NAL units have inter\_view\_flag equal to 1) are appended to the reference picture list as specified in the following. + +- If the current slice has anchor\_pic\_flag equal to 1, for each value of reference view index j from 0 to num\_anchor\_refs\_IX[i] – 1, inclusive, in ascending order of j, the inter-view prediction reference with view\_id equal to anchor\_ref\_IX[i][j] from the same access unit as the current slice is appended to RefPicListX. +- Otherwise (the current slice has anchor\_pic\_flag equal to 0), for each value of reference view index j from 0 to num\_non\_anchor\_refs\_IX[i] – 1, inclusive, in ascending order of j, the inter-view prediction reference with view\_id equal to non\_anchor\_ref\_IX[i][j] from the same access unit as the current slice is appended to RefPicListX. + +NOTE 1 – View components with inter\_view\_flag equal to 0 are not appended to the reference picture list. + +NOTE 2 – When a NAL unit with nal\_unit\_type equal to 1 or 5 is not immediately preceded by a NAL unit with nal\_unit\_type equal to 14, the value of inter\_view\_flag is inferred to be equal to 1. Encoders that do not encode a prefix NAL unit before each NAL unit with nal\_unit\_type equal to 1 or 5 and devices that remove prefix NAL units from a bitstream should take into consideration this inferred value to avoid potential mismatches in the reference picture lists between the encoder and decoder. + +Inter-view reference components and inter-view only reference components are appended to the reference picture list starting from the first entry position of "no reference picture" in the initial reference picture list RefPicListX or starting from the entry position num\_ref\_idx\_IX\_active\_minus1+1 of the initial reference picture list RefPicListX, whichever is the earliest position. + +When the number of entries in the initial reference picture list RefPicListX is greater than (num\_ref\_idx\_IX\_active\_minus1 + 1), the extra entries past position num\_ref\_idx\_IX\_active\_minus1 are discarded from the initial reference picture list RefPicListX. + +### G.8.2.2 Modification process for reference picture lists + +Input to this process is reference picture list RefPicList0 and, when decoding a B slice, also reference picture list RefPicList1. + +Outputs of this process are a possibly modified reference picture list RefPicList0 and, when decoding a B slice, also a possibly modified reference picture list RefPicList1. + +When ref\_pic\_list\_modification\_flag\_l0 is equal to 1, the following ordered steps are specified: + +1. Let refIdxL0 be an index into the reference picture list RefPicList0. It is initially set equal to 0. +2. The corresponding syntax elements modification\_of\_pic\_nums\_idc are processed in the order they occur in the bitstream. For each of these syntax elements, the following applies: + - If modification\_of\_pic\_nums\_idc is equal to 0 or equal to 1, the process specified in clause G.8.2.2.1 is invoked with RefPicList0 and refIdxL0 given as input, and the output is assigned to RefPicList0 and refIdxL0. + - Otherwise, if modification\_of\_pic\_nums\_idc is equal to 2, the process specified in clause G.8.2.2.2 is invoked with RefPicList0 and refIdxL0 given as input, and the output is assigned to RefPicList0 and refIdxL0. + - Otherwise, if modification\_of\_pic\_nums\_idc is equal to 4 or equal to 5, the process specified in clause G.8.2.2.3 is invoked with RefPicList0 and refIdxL0 given as input, and the output is assigned to RefPicList0 and refIdxL0. + - Otherwise (modification\_of\_pic\_nums\_idc is equal to 3), the modification process for reference picture list RefPicList0 is finished. + +When ref\_pic\_list\_modification\_flag\_l1 is equal to 1, the following ordered steps are specified: + +1. Let refIdxL1 be an index into the reference picture list RefPicList1. It is initially set equal to 0. +2. The corresponding syntax elements modification\_of\_pic\_nums\_idc are processed in the order they occur in the bitstream. For each of these syntax elements, the following applies: + - If modification\_of\_pic\_nums\_idc is equal to 0 or equal to 1, the process specified in clause G.8.2.2.1 is invoked with RefPicList1 and refIdxL1 given as input, and the output is assigned to RefPicList1 and refIdxL1. + +- Otherwise, if `modification_of_pic_nums_idc` is equal to 2, the process specified in clause G.8.2.2.2 is invoked with `RefPicList1` and `refIdxL1` given as input, and the output is assigned to `RefPicList1` and `refIdxL1`. +- Otherwise, if `modification_of_pic_nums_idc` is equal to 4 or equal to 5, the process specified in clause G.8.2.2.3 is invoked with `RefPicList1` and `refIdxL1` given as input, and the output is assigned to `RefPicList1` and `refIdxL1`. +- Otherwise (`modification_of_pic_nums_idc` is equal to 3), the modification process for reference picture list `RefPicList1` is finished. + +#### G.8.2.2.1 Modification process of reference picture lists for short-term reference pictures for inter prediction + +Inputs to this process are an index `refIdxLX` and a reference picture list `RefPicListX` (with `X` being 0 or 1). + +Outputs of this process are an incremented index `refIdxLX` and a modified reference picture list `RefPicListX`. + +The variable `picNumLXNoWrap` is derived as follows: + +- If `modification_of_pic_nums_idc` is equal to 0, + +$$\begin{aligned} &\text{if( picNumLXPred - ( abs\_diff\_pic\_num\_minus1 + 1 ) < 0 )} \\ &\quad \text{picNumLXNoWrap = picNumLXPred - ( abs\_diff\_pic\_num\_minus1 + 1 ) + MaxPicNum} \\ &\text{else} \\ &\quad \text{picNumLXNoWrap = picNumLXPred - ( abs\_diff\_pic\_num\_minus1 + 1 )} \end{aligned} \quad (\text{G-1})$$ +- Otherwise (`modification_of_pic_nums_idc` is equal to 1), + +$$\begin{aligned} &\text{if( picNumLXPred + ( abs\_diff\_pic\_num\_minus1 + 1 ) >= MaxPicNum )} \\ &\quad \text{picNumLXNoWrap = picNumLXPred + ( abs\_diff\_pic\_num\_minus1 + 1 ) - MaxPicNum} \\ &\text{else} \\ &\quad \text{picNumLXNoWrap = picNumLXPred + ( abs\_diff\_pic\_num\_minus1 + 1 )} \end{aligned} \quad (\text{G-2})$$ + +`picNumLXPred` is the prediction value for the variable `picNumLXNoWrap`. When the process specified in this clause is invoked the first time for a slice (that is, for the first occurrence of `modification_of_pic_nums_idc` equal to 0 or 1 in the `ref_pic_list_modification()` syntax), `picNumL0Pred` and `picNumL1Pred` are initially set equal to `CurrPicNum`. After each assignment of `picNumLXNoWrap`, the value of `picNumLXNoWrap` is assigned to `picNumLXPred`. + +The variable `picNumLX` is derived as specified by the following pseudo-code: + +``` +if( picNumLXNoWrap > CurrPicNum ) + picNumLX = picNumLXNoWrap - MaxPicNum +else + picNumLX = picNumLXNoWrap +``` + +(G-3) + +`picNumLX` shall be equal to the `PicNum` of a reference picture that is marked as "used for short-term reference" and shall not be equal to the `PicNum` of a short-term reference picture that is marked as "non-existing". + +The following procedure is conducted to place the picture with short-term picture number `picNumLX` into the index position `refIdxLX`, shift the position of any other remaining pictures to later in the list, and increment the value of `refIdxLX`: + +``` +for( cIdx = num_ref_idx_IX_active_minus1 + 1; cIdx > refIdxLX; cIdx-- ) + RefPicListX[ cIdx ] = RefPicListX[ cIdx - 1 ] +RefPicListX[ refIdxLX++ ] = short-term reference picture with PicNum equal to picNumLX +nIdx = refIdxLX +for( cIdx = refIdxLX; cIdx <= num_ref_idx_IX_active_minus1 + 1; cIdx++ ) + if( PicNumF( RefPicListX[ cIdx ] ) != picNumLX || viewID(RefPicListX[ cIdx ]) != currViewID ) + RefPicListX[ nIdx++ ] = RefPicListX[ cIdx ] +``` + +(G-4) + +In the above, the function `viewID(refpic)` returns the `view_id` of the reference picture `refpic`, the variable `currViewID` is equal to the `view_id` of the current slice, and the function `PicNumF( RefPicListX[ cIdx ] )` is derived as follows: + +- If the reference picture `RefPicListX[ cIdx ]` is marked as "used for short-term reference", `PicNumF( RefPicListX[ cIdx ] )` is the `PicNum` of the picture `RefPicListX[ cIdx ]`. +- Otherwise (the reference picture `RefPicListX[ cIdx ]` is not marked as "used for short-term reference"), `PicNumF( RefPicListX[ cIdx ] )` is equal to `MaxPicNum`. + +NOTE 1 – The value of `picNumLX` can never be equal to `MaxPicNum`. + +NOTE 2 – Within this pseudo-code procedure, the length of the list `RefPicListX` is temporarily made one element longer than the length needed for the final list. After the execution of this procedure, only elements 0 through `num_ref_idx_IX_active_minus1` of the list need to be retained. + +#### G.8.2.2.2 Modification process of reference picture lists for long-term reference pictures for inter prediction + +Inputs to this process are an index *refIdxLX* (with X being 0 or 1) and reference picture list *RefPicListX*. + +Outputs of this process are an incremented index *refIdxLX* and a modified reference picture list *RefPicListX*. + +The following procedure is conducted to place the picture with long-term picture number *long\_term\_pic\_num* into the index position *refIdxLX*, shift the position of any other remaining pictures to later in the list, and increment the value of *refIdxLX*: + +``` +for( cIdx = num_ref_idx_lX_active_minus1 + 1; cIdx > refIdxLX; cIdx-- ) + RefPicListX[ cIdx ] = RefPicListX[ cIdx − 1 ] +RefPicListX[ refIdxLX++ ] = long-term reference picture with LongTermPicNum equal to long_term_pic_num +nIdx = refIdxLX +for( cIdx = refIdxLX; cIdx <= num_ref_idx_lX_active_minus1 + 1; cIdx++ ) + if( LongTermPicNumF( RefPicListX[ cIdx ] ) != long_term_pic_num || + viewID(RefPicListX[ cIdx ]) != currViewID ) + RefPicListX[ nIdx++ ] = RefPicListX[ cIdx ] +``` + +(G-5) + +In the above, the function *viewID(refpic)* returns the *view\_id* of the reference picture *refpic*, the variable *currViewID* is equal to the *view\_id* of the current slice, and the function *LongTermPicNumF( RefPicListX[ cIdx ] )* is derived as follows: + +- If the reference picture *RefPicListX[ cIdx ]* is marked as "used for long-term reference", *LongTermPicNumF( RefPicListX[ cIdx ] )* is the *LongTermPicNum* of the picture *RefPicListX[ cIdx ]*. +- Otherwise (the reference picture *RefPicListX[ cIdx ]* is not marked as "used for long-term reference"), *LongTermPicNumF( RefPicListX[ cIdx ] )* is equal to $2 * ( \text{MaxLongTermFrameIdx} + 1 )$ . + +NOTE 1 – The value of *long\_term\_pic\_num* can never be equal to $2 * ( \text{MaxLongTermFrameIdx} + 1 )$ . + +NOTE 2 – Within this pseudo-code procedure, the length of the list *RefPicListX* is temporarily made one element longer than the length needed for the final list. After the execution of this procedure, only elements 0 through *num\_ref\_idx\_lX\_active\_minus1* of the list need to be retained. + +#### G.8.2.2.3 Modification process for reference picture lists for inter-view prediction references + +Inputs to this process are reference picture list *RefPicListX* (with X being 0 or 1) and an index *refIdxLX* into this list. + +Outputs of this process are a modified reference picture list *RefPicListX* (with X being 0 or 1) and an incremented index *refIdxLX*. + +Let *currVOIdx* be the variable *VOIdx* of the current slice. The variable *maxViewIdx* is derived as follows: + +- If the current slice has *anchor\_pic\_flag* equal to 1, *maxViewIdx* is set equal to *num\_anchor\_refs\_lX[ currVOIdx ] − 1*. +- Otherwise (the current slice has *anchor\_pic\_flag* equal to 0), *maxViewIdx* is set equal to *num\_non\_anchor\_refs\_lX[ currVOIdx ] − 1*. + +The variable *picViewIdxLX* is derived as follows: + +- If *modification\_of\_pic\_nums\_idc* is equal to 4, + + +``` +if( picViewIdxLXPred − ( abs_diff_view_idx_minus1 + 1 ) < 0 ) + picViewIdxLX = picViewIdxLXPred − ( abs_diff_view_idx_minus1 + 1 ) + maxViewIdx + 1 +else + picViewIdxLX = picViewIdxLXPred − ( abs_diff_view_idx_minus1 + 1 ) +``` + +(G-6) + +- Otherwise (*modification\_of\_pic\_nums\_idc* is equal to 5), + + +``` +if( picViewIdxLXPred + ( abs_diff_view_idx_minus1 + 1 ) >= maxViewIdx + 1 ) + picViewIdxLX = picViewIdxLXPred + ( abs_diff_view_idx_minus1 + 1 ) − ( maxViewIdx + 1 ) +else + picViewIdxLX = picViewIdxLXPred + ( abs_diff_view_idx_minus1 + 1 ) +``` + +(G-7) + +*picViewIdxLXPred* is the prediction value for the variable *picViewIdxLX*. When the process specified in this clause is invoked the first time for a slice (that is, for the first occurrence of *modification\_of\_pic\_nums\_idc* equal to 4 or 5 in the *ref\_pic\_list\_modification()* syntax), *picViewIdxL0Pred* and *picViewIdxL1Pred* are initially set equal to −1. After each assignment of *picViewIdxLX*, the value of *picViewIdxLX* is assigned to *picViewIdxLXPred*. + +The bitstream shall not contain data that result in *picViewIdxLX* less than 0 or *picViewIdxLX* greater than *maxViewIdx*. + +The variable *targetViewID* is derived as follows: + +- If the current slice has anchor\_pic\_flag equal to 1, + +$$\text{targetViewID} = \text{anchor\_refs\_IX}[ \text{currVOIdx} ][ \text{picViewIdxLX} ] \quad (\text{G-8})$$ + +- Otherwise (the current slice has anchor\_pic\_flag equal to 0), + +$$\text{targetViewID} = \text{non\_anchor\_refs\_IX}[ \text{currVOIdx} ][ \text{picViewIdxLX} ] \quad (\text{G-9})$$ + +The following procedure is conducted to place the inter-view prediction reference with reference view index equal to picViewIdxLX into the index position refIdxLX and shift the position of any other remaining pictures to later in the list: + +``` +for( cIdx = num_ref_idx_IX_active_minus1 + 1; cIdx > refIdxLX; cIdx-- ) + RefPicListX[ cIdx ] = RefPicListX[ cIdx - 1 ] +RefPicListX[ refIdxLX++ ] = inter-view prediction reference with view_id equal to targetViewID +nIdx = refIdxLX +for( cIdx = refIdxLX; cIdx <= num_ref_idx_IX_active_minus1 + 1; cIdx++ ) + if( viewID(RefPicListX[ cIdx ]) != targetViewID || PictureOrderCnt(RefPicListX[ cIdx ]) != currPOC ) + RefPicListX[ nIdx++ ] = RefPicListX[ cIdx ] +``` + +$$\quad (\text{G-10})$$ + +In the above, the function viewID(refpic) returns the view\_id of the reference picture refpic, the variable currViewID is equal to the view\_id of the current slice, and the variable currPOC is equal to PicOrderCnt( ) of the current slice. + +### G.8.3 MVC decoded reference picture marking process + +The process specified in this clause is invoked for a particular view with view order index VOIdx. The specifications in clause 8.2.5 apply with "picture" being replaced by "view component", "frame" being replaced by "frame view component", and "field" being replaced by "field view component". During the invocation of the process for a particular view, only view components of the particular view are considered. The marking of view components of other views is not changed. + +NOTE – A view component of a picture may have a different marking status than other view components of the same picture. + +### G.8.4 MVC inter prediction and inter-view prediction process + +For both inter-prediction and inter-view prediction, the specifications in clause 8.4 apply. For the invocation of the MVC inter prediction and inter-view prediction process as specified in this clause, the inter-view reference components and inter-view only reference components that are included in the reference picture lists are considered as not being marked as "used for short-term reference" or "used for long-term reference". + +NOTE – This implies that when RefPicList1[ 0 ] represents an inter-view reference component or an inter-view only reference component, the variable colZeroFlag in clause 8.4.1.2.2 is always derived to be equal to 0. + +When mfc\_format\_idc is present, the additional processing for an inter-view prediction reference as specified in clause G.8.4.1 is invoked before the inter-view prediction reference is used for inter-view prediction. + +#### G.8.4.1 Additional processing for an inter-view prediction reference + +This process is invoked when mfc\_format\_idc is present to modify each colour component array of an inter-view prediction reference used in decoding view components of the non-base view. When rpu\_filter\_enabled\_flag is equal to 1, the modification process consists of a one-dimensional downsampling filtering process followed by a one-dimensional upsampling filtering process. The modification process converts an inter-view prediction reference from the frame packing arrangement format of the view components in the base view to the frame packing arrangement format of the view components in the non-base view. When rpu\_filter\_enabled\_flag is equal to 0, all sample values for each colour component of an inter-view prediction reference are set equal to 128. + +Inputs of this process are: + +- two variables refW and refH specifying the width and height, respectively, of the inter-view prediction reference picture sample array, +- a (refW)x(refH) inter-view prediction reference picture sample array refPicture for either the luma or a chroma component. + +Output of this process is a (refW)x(refH) modified inter-view prediction reference picture sample array RpuPicture for either the luma or a chroma component. + +The input sample array refPicture corresponds to a decoded sample array $S_L$ , $S_{Cb}$ or $S_{Cr}$ , respectively, for each colour component derived in clause 8.7 for a decoded frame or complementary field pair or field of a decoded frame from the base view. + +The output sample array RpuPicture corresponds to a decoded sample array $S_L$ , $S_{Cb}$ or $S_{Cr}$ , respectively, for each colour + +component derived in clause 8.7 for a previously-decoded reference frame or complementary reference field pair or field of a reference frame. + +Depending on the value of `rpu_field_processing_flag`, the following applies: + +- If `rpu_field_processing_flag` is equal to 1, the inter-view prediction reference picture `refPicture` is a field, the modified inter-view prediction reference picture `RpuPicture` is a field, and the inter-view prediction reference modification is applied to the individual inter-view prediction reference fields separately. +- Otherwise (`rpu_field_processing_flag` is equal to 0), the inter-view prediction reference picture `refPicture` is a frame, the modified inter-view prediction reference picture `RpuPicture` is a frame, and the inter-view prediction reference modification is applied to the inter-view prediction reference frame. + +The mathematical function `Clip1()` is defined with `Clip1()` being substituted with `Clip1V()` for the luma component and `Clip1()` being substituted with `Clip1C()` for the chroma components, respectively. + +The variables `refW` and `refH` are derived as follows: + +- For the luma component, `refW` is set equal to `PicWidthInSamplesL` and `refH` is set equal to `PicHeightInSamplesL`. +- For the chroma components, `refW` is set equal to `PicWidthInSamplesC` and `refH` is set equal to `PicHeightInSamplesC`. + +The variables `subW` and `subH` are derived as follows: + +- For the luma component, `subW` is set equal to `SubWidthC` and `subH` is set equal to `SubHeightC`. +- For the chroma components, `subW` is set equal to 1 and `subH` is set equal to 1. + +The variable `view0OffsetX` is derived as follows: + +- If `view0_grid_position_x` is equal to 4 or 8, `view0OffsetX` is set equal to 0, +- Otherwise (`view0_grid_position_x` is equal to 12), `view0OffsetX` is set equal to 1. + +The variable `view1OffsetX` is derived as follows: + +- If `view1_grid_position_x` is equal to 4 or 8, `view1OffsetX` is set equal to 0, +- Otherwise (`view1_grid_position_x` is equal to 12), `view1OffsetX` is set equal to 1. + +The variable `view0OffsetY` is derived as follows: + +- If `view0_grid_position_y` is equal to 4 or 8, `view0OffsetY` is set equal to 0, +- Otherwise (`view0_grid_position_y` is equal to 12), `view0OffsetY` is set equal to 1. + +The variable `view1OffsetY` is derived as follows: + +- If `view1_grid_position_y` is equal to 4 or 8, `view1OffsetY` is set equal to 0, +- Otherwise (`view1_grid_position_y` is equal to 12), `view1OffsetY` is set equal to 1. + +The variable `RpuW` specifying the width of an active area of the reference picture is derived as specified by the following ordered steps: + +1. `leftOffset = frame_crop_left_offset * subW` +2. `rightOffset = frame_crop_right_offset * subW` +3. `RpuW = refW - leftOffset - rightOffset` (G-11) + +The variable `RpuH` specifying the height of an active area of the reference picture is derived as specified by the following ordered steps: + +1. `topOffset = frame_crop_top_offset * subH * ( 2 - frame_mbs_only_flag )` +2. `botOffset = frame_crop_bottom_offset * subH * ( 2 - frame_mbs_only_flag )` +3. `if ( rpu_field_processing_flag )` +`topOffset = topOffset >> 1, botOffset = botOffset >> 1` +4. `RpuH = refH - topOffset - botOffset` (G-12) + +The variable `SbsV` is set equal to `RpuW >> 1`. In the side-by-side arrangement, the view boundary position between the left and right views is set equal to `SbsV + leftOffset`. + +The variable TabV is set equal to RpuH >> 1. In the top-bottom arrangement, the view boundary position between the left and right views is set equal to TabV + topOffset. + +The filtered samples of picture sample array rpuPicture[ x, y ], with x = 0..refW - 1 and y = 0..refH - 1, are derived as follows: + +- If rpu\_filter\_enabled\_flag is equal to 0, the following applies: + +$$\text{RpuPicture[ x, y ]} = 128 \text{ with } x = 0..refW - 1 \text{ and } y = 0..refH - 1 \quad (\text{G-13})$$ + +- Otherwise (rpu\_filter\_enabled\_flag is equal to 1), the following applies: + +Let tempPicture[ x, y ] be a (SbsV)x(TabV) array of samples with x = 0..SbsV - 1 and y = 0..TabV - 1. + +- If mfc\_format\_idc is equal to 0, let tempRefPic[ x, y ] be a (SbsV)x(RpuH) array of samples with x = 0..SbsV - 1 and y = 0..RpuH - 1, and tempRpuPic[ x, y ] be a (RpuW)x(TabV) array of samples with x = 0..RpuW - 1 and y = 0..TabV - 1. +- Otherwise (mfc\_format\_idc is equal to 1), let tempRefPic[ x, y ] be a (RpuW)x(TabV) array of samples with x = 0..RpuW - 1 and y = 0..TabV - 1, and tempRpuPic[ x, y ] be a (SbsV)x(RpuH) array of samples with x = 0..SbsV - 1 and y = 0..RpuH - 1. + +The filtered samples of picture sample array RpuPicture[ x, y ] with x = leftOffset..RpuW - 1 + leftOffset and y = topOffset..RpuH - 1 + topOffset are derived as specified by the following ordered steps: + +- If mfc\_format\_idc is equal to 0, the following applies: + +1. RpuPicture[ x, y ] with x = leftOffset..RpuW - 1 + leftOffset and y = topOffset..TabV - 1 + topOffset is derived from the input of the array refPicture[ x, y ] with x = leftOffset..SbsV - 1 + leftOffset and y = topOffset..RpuH - 1 + topOffset as specified by the following ordered steps: + +- a. tempRefPic[ x, y ] = refPicture[ x + leftOffset, y + topOffset ] + +$$\text{with } x = 0..SbsV - 1 \text{ and } y = 0..RpuH - 1 \quad (\text{G-14})$$ + +- b. Apply the following one-dimensional downsampling process: + +$$\begin{aligned} \text{tempPicture[ x, y ]} = & \text{Clip1( ( 4 * tempRefPic[ x, Clip3( 0, 2 * y - 2, RpuH - 1 ) ] + } \\ & 7 * \text{tempRefPic[ x, Clip3( 0, 2 * y - 1, RpuH - 1 ) ] + } \\ & 10 * \text{tempRefPic[ x, Clip3( 0, 2 * y, RpuH - 1 ) ] + } \\ & 7 * \text{tempRefPic[ x, Clip3( 0, 2 * y + 1, RpuH - 1 ) ] + } \\ & 4 * \text{tempRefPic[ x, Clip3( 0, 2 * y + 2, RpuH - 1 ) ] + 32 ) } \gg 5 ) \end{aligned} \quad (\text{G-15})$$ + +$$\text{with } x = 0..SbsV - 1 \text{ and } y = 0..TabV - 1$$ + +- c. Apply the following one-dimensional upsampling process: + +$$\text{gMin} = -2 - \text{View0OffsetX} \quad (\text{G-16})$$ + +$$\text{tempRpuPic[ 2 * x + view0OffsetX, y ]} = \text{tempPicture[ x, y ]} \quad (\text{G-17})$$ + +$$\begin{aligned} \text{tempRpuPic[ 2 * x + ( 1 - view0OffsetX ), y ]} = & \text{Clip1( ( 3 * tempPicture[ Clip3( 0, x + gMin, SbsV - 1 ), y ] - } \\ & 17 * \text{tempPicture[ Clip3( 0, x + gMin + 1, SbsV - 1 ), y ] + } \\ & 78 * \text{tempPicture[ Clip3( 0, x + gMin + 2, SbsV - 1 ), y ] + } \\ & 78 * \text{tempPicture[ Clip3( 0, x + gMin + 3, SbsV - 1 ), y ] - } \\ & 17 * \text{tempPicture[ Clip3( 0, x + gMin + 4, SbsV - 1 ), y ] + } \\ & 3 * \text{tempPicture[ Clip3( 0, x + gMin + 5, SbsV - 1 ), y ] + 64 ) } \gg 7 ) \end{aligned} \quad (\text{G-18})$$ + +$$\text{with } x = 0..SbsV - 1 \text{ and } y = 0..TabV - 1$$ + +- d. RpuPicture[ x + leftOffset, y + topOffset ] = tempRpuPic[ x, y ] + +$$\text{with } x = 0..RpuW - 1 \text{ and } y = 0..TabV - 1 \quad (\text{G-19})$$ + +2. RpuPicture[ x, y ] with x = leftOffset..RpuW - 1 + leftOffset and y = TabV + topOffset..RpuH - 1 + topOffset is derived from the input of the array refPicture[ x, y ] with x = SbsV + leftOffset..RpuW - 1 + leftOffset and y = topOffset..RpuH - 1 + topOffset as specified by the following ordered steps: + +- a. tempRefPic[ x, y ] = refPicture[ x + SbsV + leftOffset, y + topOffset ] + +with $x = 0..SbsV - 1$ and $y = 0..RpuH - 1$ (G-20) + +b. Apply the following one-dimensional downsampling process: + +$$\begin{aligned} \text{tempPicture}[x, y] = & \text{Clip1}((4 * \text{tempRefPic}[x, \text{Clip3}(0, 2 * y - 2, RpuH - 1)]) + \\ & 7 * \text{tempRefPic}[x, \text{Clip3}(0, 2 * y - 1, RpuH - 1)]) + \\ & 10 * \text{tempRefPic}[x, \text{Clip3}(0, 2 * y, RpuH - 1)]) + \\ & 7 * \text{tempRefPic}[x, \text{Clip3}(0, 2 * y + 1, RpuH - 1)]) + \\ & 4 * \text{tempRefPic}[x, \text{Clip3}(0, 2 * y + 2, RpuH - 1)]) + 32) \gg 6) \end{aligned} \quad (G-21)$$ + +with $x = 0..SbsV - 1$ and $y = 0..TabV - 1$ + +c. Apply the following one-dimensional upsampling process: + +$$\text{gMin} = -2 - \text{View1OffsetX} \quad (G-22)$$ + +$$\text{tempRpuPic}[2 * x + \text{view1OffsetX}, y] = \text{tempPicture}[x, y] \quad (G-23)$$ + +$$\begin{aligned} \text{tempRpuPic}[2 * x + (1 - \text{view1OffsetX}), y] = & \text{Clip1}((3 * \text{tempPicture}[\text{Clip3}(0, x + \text{gMin}, SbsV - 1), y]) - \\ & 17 * \text{tempPicture}[\text{Clip3}(0, x + \text{gMin} + 1, SbsV - 1), y]) + \\ & 78 * \text{tempPicture}[\text{Clip3}(0, x + \text{gMin} + 2, SbsV - 1), y]) + \\ & 78 * \text{tempPicture}[\text{Clip3}(0, x + \text{gMin} + 3, SbsV - 1), y]) - \\ & 17 * \text{tempPicture}[\text{Clip3}(0, x + \text{gMin} + 4, SbsV - 1), y]) + \\ & 3 * \text{tempPicture}[\text{Clip3}(0, x + \text{gMin} + 5, SbsV - 1), y]) + 64) \gg 7) \end{aligned} \quad (G-24)$$ + +with $x = 0..SbsV - 1$ and $y = 0..TabV - 1$ + +d. $\text{RpuPicture}[x + \text{leftOffset}, y + \text{TabV} + \text{topOffset}] = \text{tempRpuPic}[x, y]$ + +with $x = 0..RpuW - 1$ and $y = 0..TabV - 1$ (G-25) + +– Otherwise ( `mfc_format_idc` is equal to 1), the following applies: + +1. $\text{RpuPicture}[x, y]$ with $x = \text{leftOffset}..SbsV - 1 + \text{leftOffset}$ and $y = \text{topOffset}..RpuH - 1 + \text{topOffset}$ is derived from the input of the array `refPicture`[ $x, y$ ] with $x = \text{leftOffset}..RpuW - 1 + \text{leftOffset}$ and $y = \text{topOffset}..TabV - 1 + \text{topOffset}$ as specified by the following ordered steps: + +a. $\text{tempRefPic}[x, y] = \text{refPicture}[x + \text{leftOffset}, y + \text{topOffset}]$ + +with $x = 0..RpuW - 1$ and $y = 0..TabV - 1$ (G-26) + +b. Apply the following one-dimensional downsampling process: + +$$\begin{aligned} \text{tempPicture}[x, y] = & \text{Clip1}((4 * \text{tempRefPic}[\text{Clip3}(0, 2 * x - 2, RpuW - 1), y]) + \\ & 7 * \text{tempRefPic}[\text{Clip3}(0, 2 * x - 1, RpuW - 1), y]) + \\ & 10 * \text{tempRefPic}[\text{Clip3}(0, 2 * x, RpuW - 1), y]) + \\ & 7 * \text{tempRefPic}[\text{Clip3}(0, 2 * x + 1, RpuW - 1), y]) + \\ & 4 * \text{tempRefPic}[\text{Clip3}(0, 2 * x + 2, RpuW - 1), y]) + 32) \gg 6) \end{aligned} \quad (G-27)$$ + +with $x = 0..SbsV - 1$ and $y = 0..TabV - 1$ + +c. Apply the following one-dimensional upsampling process: + +$$\text{gMin} = -2 - \text{View0OffsetY} \quad (G-28)$$ + +$$\text{tempRpuPic}[x, 2 * y + \text{view0OffsetY}] = \text{tempPicture}[x, y] \quad (G-29)$$ + +$$\begin{aligned} \text{tempRpuPic}[x, 2 * y + (1 - \text{view0OffsetY})] = & \text{Clip1}((3 * \text{tempPicture}[x, \text{Clip3}(0, y + \text{gMin}, TabV - 1)]) - \\ & 17 * \text{tempPicture}[x, \text{Clip3}(0, y + \text{gMin} + 1, TabV - 1)]) + \\ & 78 * \text{tempPicture}[x, \text{Clip3}(0, y + \text{gMin} + 2, TabV - 1)]) + \\ & 78 * \text{tempPicture}[x, \text{Clip3}(0, y + \text{gMin} + 3, TabV - 1)]) - \\ & 17 * \text{tempPicture}[x, \text{Clip3}(0, y + \text{gMin} + 4, TabV - 1)]) + \\ & 3 * \text{tempPicture}[x, \text{Clip3}(0, y + \text{gMin} + 5, TabV - 1)]) + 64) \gg 7) \end{aligned} \quad (G-30)$$ + +with $x = 0..SbsV - 1$ and $y = 0..TabV - 1$ + +d. $\text{RpuPicture}[x + \text{leftOffset}, y + \text{topOffset}] = \text{tempRpuPic}[x, y]$ + +$$\text{with } x = 0..SbsV - 1 \text{ and } y = 0..RpuH - 1 \quad (G-31)$$ + +2. $RpuPicture[ x, y ]$ with $x = SbsV + leftOffset..RpuW - 1 + leftOffset$ and $y = topOffset..RpuH - 1 + topOffset$ is derived from the input of the array $refPicture[ x, y ]$ with $x = leftOffset..RpuW - 1 + leftOffset$ and $y = TabV + topOffset..RpuH - 1 + topOffset$ as specified by the following ordered steps: + +- a. $tempRefPic[ x, y ] = refPicture[ x + leftOffset, y + topOffset + TabV ]$ + +$$\text{with } x = 0..RpuW - 1 \text{ and } y = 0..TabV - 1 \quad (G-32)$$ + +- b. Apply the following one-dimensional downsampling process: + +$$\begin{aligned} tempPicture[ x, y ] = & \\ & Clip1( ( 4 * tempRefPic[ Clip3( 0, 2 * x - 2, RpuW - 1 ), y ] + \\ & 7 * tempRefPic[ Clip3( 0, 2 * x - 1, RpuW - 1 ), y ] + \\ & 10 * tempRefPic[ Clip3( 0, 2 * x, RpuW - 1 ), y ] + \\ & 7 * tempRefPic[ Clip3( 0, 2 * x + 1, RpuW - 1 ), y ] + \\ & 4 * tempRefPic[ Clip3( 0, 2 * x + 2, RpuW - 1 ), y ] + 32 ) \gg 6 ) \end{aligned} \quad (G-33)$$ + +$$\text{with } x = 0..SbsV - 1 \text{ and } y = 0..TabV - 1$$ + +- c. Apply the following one-dimensional upsampling process: + +$$gMin = - 2 - View1OffsetY \quad (G-34)$$ + +$$tempRpuPic[ x, 2 * y + view1OffsetY ] = tempPicture[ x, y ] \quad (G-35)$$ + +$$\begin{aligned} tempRpuPic[ x, 2 * y + ( 1 - view1OffsetY ) ] = & \\ & Clip1( ( 3 * tempPicture[ x, Clip3( 0, y + gMin, TabV - 1 ) ] - \\ & 17 * tempPicture[ x, Clip3( 0, y + gMin + 1, TabV - 1 ) ] + \\ & 78 * tempPicture[ x, Clip3( 0, y + gMin + 2, TabV - 1 ) ] + \\ & 78 * tempPicture[ x, Clip3( 0, y + gMin + 3, TabV - 1 ) ] - \\ & 17 * tempPicture[ x, Clip3( 0, y + gMin + 4, TabV - 1 ) ] + \\ & 3 * tempPicture[ x, Clip3( 0, y + gMin + 5, TabV - 1 ) ] + 64 ) \gg 7 ) \end{aligned} \quad (G-36)$$ + +$$\text{with } x = 0..SbsV - 1 \text{ and } y = 0..TabV - 1$$ + +- d. $RpuPicture[ x + SbsV + leftOffset, y + topOffset ] = tempRpuPic[ x, y ]$ + +$$\text{with } x = 0..SbsV - 1 \text{ and } y = 0..RpuH - 1 \quad (G-37)$$ + +The padded filtered samples of picture sample array $RpuPicture[ x, y ]$ outside frame cropping rectangle with $x = 0..leftOffset - 1$ or $x = RpuW + leftOffset..refW - 1$ or $y = 0..topOffset - 1$ or $y = RpuH + topOffset..refH - 1$ are derived as specified by the following ordered steps: + +1. $RpuPicture[ x, y ] = RpuPicture[ leftOffset, y ]$ + +$$\text{with } x = 0..leftOffset - 1 \text{ and } y = topOffset..RpuH - 1 + topOffset \quad (G-38)$$ + +2. $RpuPicture[ x, y ] = RpuPicture[ RpuW - 1 + leftOffset, y ]$ + +$$\text{with } x = RpuW + leftOffset..refW - 1 \text{ and } y = topOffset..RpuH - 1 + topOffset \quad (G-39)$$ + +3. $RpuPicture[ x, y ] = RpuPicture[ x, topOffset ]$ + +$$\text{with } x = 0..refW - 1 \text{ and } y = 0..topOffset - 1 \quad (G-40)$$ + +4. $RpuPicture[ x, y ] = RpuPicture[ x, RpuH - 1 + topOffset ]$ + +$$\text{with } x = 0..refW - 1 \text{ and } y = RpuH + topOffset..refH - 1 \quad (G-41)$$ + +NOTE – If each view component in the base view is a side-by-side frame packing arrangement picture, the inter-view reference picture is first vertically downsampled and then horizontally upsampled in a conversion to the top-bottom format. Otherwise (each view component in the base view is a top-bottom frame packing arrangement picture), the inter-view reference picture is first horizontally downsampled and then vertically upsampled in a conversion to the side-by-side format. + +## G.8.5 Specification of sub-bitstreams + +Clauses G.8.5.1 and G.8.5.2 specify the processes for deriving required anchor and non-anchor view components, respectively, that are used in the sub-bitstream extraction process. Clause G.8.5.3 specifies the sub-bitstream extraction process. Clause G.8.5.4 specifies the base view sub-bitstream. Clause G.8.5.5 gives an informative example for creation + +of a base view in case the original base view in the input bitstream to the bitstream extraction process is not included in the output sub-bitstream. + +#### **G.8.5.1 Derivation process for required anchor view components** + +This process is recursively invoked to derive the set of required anchor view components for a specified view. + +Input to this process is a variable viewId, representing a view with view\_id equal to viewId, with its corresponding view order index denoted by vOIdx. + +Outputs of this process are a possibly updated VOIdxList, and additional invocations of the derivation process based on the inter-view dependency for anchor view components in the view with view\_id equal to viewId as specified in the sequence parameter set MVC extension. + +The following ordered steps are specified: + +1. When vOIdx is not already included in VOIdxList, add vOIdx to VOIdxList. +2. Depending on num\_anchor\_refs\_10[ vOIdx ] and num\_anchor\_refs\_11[ vOIdx ], the following applies: + - If both num\_anchor\_refs\_10[ vOIdx ] and num\_anchor\_refs\_11[ vOIdx ] are equal to 0, terminate this process. + - Otherwise (num\_anchor\_refs\_10[ vOIdx ] or num\_anchor\_refs\_11[ vOIdx ] is not equal to 0), the following ordered steps are specified: + - a. When num\_anchor\_refs\_10[ vOIdx ] is not equal to 0, invoke the process specified in clause G.8.5.1 for each viewId equal to anchor\_ref\_10[ vOIdx ][ i ] for all i in the range of 0 to num\_anchor\_refs\_10[ vOIdx ] – 1, inclusive, in ascending order of i. + - b. When num\_anchor\_refs\_11[ vOIdx ] is not equal to 0, invoke the process specified in clause G.8.5.1 for each viewId equal to anchor\_ref\_11[ vOIdx ][ i ] for all i in the range of 0 to num\_anchor\_refs\_11[ vOIdx ] – 1, inclusive, in ascending order of i. + +#### **G.8.5.2 Derivation process for required non-anchor view components** + +This process is recursively invoked to derive the set of required non-anchor view components for a specified view. + +Input to this process is a variable viewId, representing a view with view\_id equal to viewId, with its corresponding view order index denoted by vOIdx. + +Outputs of this process are a possibly updated VOIdxList, and additional invocations of the derivation process based on the inter-view dependency for non-anchor view components in the view with view\_id equal to viewId as specified in the sequence parameter set MVC extension. + +The following ordered steps are specified: + +1. When vOIdx is not already included in VOIdxList, add vOIdx to VOIdxList. +2. Depending on num\_non\_anchor\_refs\_10[ vOIdx ] and num\_non\_anchor\_refs\_11[ vOIdx ], the following applies: + - If both num\_non\_anchor\_refs\_10[ vOIdx ] and num\_non\_anchor\_refs\_11[ vOIdx ] are equal to 0, terminate this process. + - Otherwise (num\_non\_anchor\_refs\_10[ vOIdx ] or num\_non\_anchor\_refs\_11[ vOIdx ] is not equal to 0), the following ordered steps are specified: + - a. When num\_non\_anchor\_refs\_10[ vOIdx ] is not equal to 0, invoke the process specified in clause G.8.5.2 for each viewId equal to non\_anchor\_ref\_10[ vOIdx ][ i ] for all i in the range of 0 to num\_non\_anchor\_refs\_10[ vOIdx ] – 1, inclusive, in ascending order of i. + - b. When num\_non\_anchor\_refs\_11[ vOIdx ] is not equal to 0, invoke the process specified in clause G.8.5.2 for each viewId equal to non\_anchor\_ref\_11[ vOIdx ][ i ] for all i in the range of 0 to num\_non\_anchor\_refs\_11[ vOIdx ] – 1, inclusive, in ascending order of i. + +#### **G.8.5.3 Sub-bitstream extraction process** + +It is requirement of bitstream conformance that any sub-bitstream that is the output of the process specified in this clause with pldTarget equal to any value in the range of 0 to 63, inclusive, tldTarget equal to any value in the range of 0 to 7, inclusive, viewIdTargetList consisting of any one or more values of viewIdTarget identifying the views in the bitstream, shall be conforming to this Recommendation | International Standard. + +NOTE 1 – A conforming bitstream contains one or more coded slice NAL units with priority\_id equal to 0 and temporal\_id equal to 0. + +NOTE 2 – It is possible that not all operation points of sub-bitstreams resulting from the sub-bitstream extraction process have an applicable level\_idc or level\_idc[ i ]. In this case, each coded video sequence in a sub-bitstream must still conform to one or more of the profiles specified in Annex A and Annex G, but may not satisfy the level constraints specified in clauses A.3 and G.10.2, respectively. + +Inputs to this process are: + +- a variable pIdTarget (when present), +- a variable tIdTarget (when present), +- a list viewIdTargetList consisting of one or more values of viewIdTarget (when present). + +Outputs of this process are a sub-bitstream and a list of VOIdx values VOIdxList. + +When pIdTarget is not present as input to this clause, pIdTarget is inferred to be equal to 63. + +When tIdTarget is not present as input to this clause, tIdTarget is inferred to be equal to 7. + +When viewIdTargetList is not present as input to this clause, there shall be one value of viewIdTarget inferred in viewIdTargetList and the value of viewIdTarget is inferred to be equal to view\_id of the base view. + +The sub-bitstream is derived by applying the following operations in sequential order: + +1. Let VOIdxList be empty and minVOIdx be the VOIdx value of the base view. +2. For each value of viewIdTarget included in viewIdTargetList, invoke the process specified in clause G.8.5.1 with the value of viewIdTarget as input. +3. For each value of viewIdTarget included in viewIdTargetList, invoke the process specified in clause G.8.5.2 with the value of viewIdTarget as input. +4. Mark all VCL NAL units and filler data NAL units for which any of the following conditions are true as "to be removed from the bitstream": + - priority\_id is greater than pIdTarget, + - temporal\_id is greater than tIdTarget, + - view\_id is not in the viewIdTargetList. +5. Remove all access units for which all VCL NAL units are marked as "to be removed from the bitstream". +6. Remove all VCL NAL units and filler data NAL units that are marked as "to be removed from the bitstream". +7. When VOIdxList contains only one value of VOIdx that is equal to minVOIdx, remove the following NAL units: + - all NAL units with nal\_unit\_type equal to 14 or 15, + - all NAL units with nal\_unit\_type equal to 6 in which the first SEI message has payloadType in the range of 36 to 44, inclusive, or equal to 46. + +NOTE 3 – When VOIdxList contains only one value of VOIdx equal to minVOIdx, the sub-bitstream contains only the base view or only a temporal subset of the base view. + +8. Let maxTId be the maximum temporal\_id of all the remaining VCL NAL units. Remove all NAL units with nal\_unit\_type equal to 6 that only contain SEI messages that are part of an MVC scalable nesting SEI message with any of the following properties: + - operation\_point\_flag is equal to 0 and all\_view\_components\_in\_au\_flag is equal to 0 and none of sei\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_minus1, inclusive, corresponds to a VOIdx value included in VOIdxList, + - operation\_point\_flag is equal to 1 and either sei\_op\_temporal\_id is greater than maxTId or the list of sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, is not a subset of viewIdTargetList (i.e., it is not true that sei\_op\_view\_id[ i ] for any i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, is equal to a value in viewIdTargetList). +9. Remove each view scalability information SEI message and each operation point not present SEI message, when present. + +- When VOIdxList does not contain a value of VOIdx equal to minVOIdx, the view with VOIdx equal to the minimum VOIdx value included in VOIdxList is converted to the base view of the extracted sub-bitstream. An informative procedure that outlines key processing steps to create a base view is described in clause G.8.5.5. + +NOTE 4 – When VOIdxList does not contain a value of VOIdx equal to minVOIdx, the resulting sub-bitstream according to the operation steps 1-9 above does not contain a base view that conforms to one or more profiles specified in Annex A. In this case, by this operation step, the remaining view with the new minimum VOIdx value is converted to be the new base view that conforms to one or more profiles specified in Annex A. + +#### G.8.5.4 Specification of the base view bitstream + +A bitstream that conforms to one or more profiles as specified in Annex G shall contain a base view bitstream that conforms to one or more of the profiles specified in Annex A. This base view bitstream is derived by invoking the sub-bitstream extraction process as specified in clause G.8.5.3 with no input and the base view bitstream being the output. + +NOTE – Although all multiview bitstreams that conform to one or more of the profiles specified in this annex contain a base view bitstream that conforms to one or more of the profiles specified in Annex A, the complete multiview bitstream (prior to operation of the base view extraction process specified in this clause) may not conform to any profile specified in Annex A. + +#### G.8.5.5 Creation of a base view during sub-bitstream extraction (informative) + +According to the sub-bitstream extraction process specified in clause G.8.5.3, the resulting sub-bitstream shall contain a base view. When the resulting bitstream does not contain a base view, the following procedure may be used to create a base view during sub-bitstream extraction. + +When VOIdxList does not contain a value of VOIdx equal to minVOIdx, let newBaseViewId be equal to the view\_id for which the VOIdx value is equal to the minimum VOIdx value included in VOIdxList, and apply the following operations in sequential order: + +- Remove all NAL units with nal\_unit\_type equal to 7. +- For all subset sequence parameter set NAL units (with nal\_unit\_type equal to 15) that are referred to by at least one remaining VCL NAL unit with view\_id equal to newBaseViewId, apply the following operations in sequential order: + - Set nal\_unit\_type to 7. + - Set profile\_idc to 100. + - Set level\_idc to level\_idc[ i ], with i equal to the value that for one value of j in the range of 0 to num\_applicable\_ops\_minus1[ i ], inclusive, applicable\_op\_temporal\_id[ i ][ j ] is equal to maxTId, applicable\_op\_num\_target\_views\_minus1[ i ][ j ] is equal to 0, and applicable\_op\_target\_view\_id[ i ][ j ][ k ] for k equal to 0 is equal to newBaseViewId. + - Remove all the syntax elements after the syntax structure seq\_parameter\_set\_data( ) and before the syntax structure rbsp\_trailing\_bits( ), and change RBSP trailing bits appropriately. +- Remove all SEI NAL units (with nal\_unit\_type equal to 6) for which the first contained SEI message has payloadType in the range of 0 to 23, inclusive. +- For each SEI NAL unit (with nal\_unit\_type equal to 6) containing an MVC scalable nesting SEI message, the following operations are applied in sequential order: + - When none of the following properties is true for the MVC scalable nesting SEI message, the SEI NAL unit is removed: + - operation\_point\_flag is equal to 0 and all\_view\_components\_in\_au\_flag is equal to 1, + - operation\_point\_flag is equal to 0, all\_view\_components\_in\_au\_flag is equal to 0, and at least one of the values of sei\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_minus1, inclusive, is equal to the value of one of the viewIdTarget's in viewIdTargetList, + - operation\_point\_flag is equal to 1, sei\_op\_temporal\_id is equal to or less than maxTId, and the list of sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, is a subset of viewIdTargetList (i.e., it is true that sei\_op\_view\_id[ i ] for any i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, is equal to a value in viewIdTargetList). + - When the SEI NAL unit is not removed, the following applies: + - If VOIdxList contains only one VOIdx value, the SEI NAL unit is replaced by an SEI NAL unit containing only the original nested SEI message not as part of an MVC scalable nesting SEI message. + +- Otherwise (VOIdxList contains more than one VOIdx value), when any of the following properties is true for the MVC scalable nesting SEI message, a new SEI NAL unit containing only the nested SEI message not as part of an MVC scalable nesting SEI message is generated and inserted immediately before the original SEI NAL unit in decoding order: + - operation\_point\_flag is equal to 0 and all\_view\_components\_in\_au\_flag is equal to 1, + - operation\_point\_flag is equal to 0, all\_view\_components\_in\_au\_flag is equal to 0, and for the values of sei\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_minus1, inclusive, one is equal to newBaseViewId, and at least another one is equal to the value of one of the viewIdTarget's in viewIdTargetList. +5. When VOIdxList contains only one value of VOIdx, remove the following NAL units: + - all NAL units with nal\_unit\_type equal to 15, + - all NAL units with nal\_unit\_type equal to 6 in which the first SEI message has payloadType in the range of 36 to 44, inclusive. + 6. For each NAL unit nalUnit with nal\_unit\_type equal to 20 and view\_id equal to newBaseViewId, the following operations are applied in sequential order: + - a. Depending on non\_idr\_flag, the following applies: + - If non\_idr\_flag is equal to 0, set nal\_unit\_type equal to 5. + - Otherwise (non\_idr\_flag is equal to 1), set nal\_unit\_type equal to 1. + - b. When VOIdxList contains more than one VOIdx value, generate a prefix NAL unit with the same NAL unit header (including NAL unit header MVC extension) as the NAL unit nalUnit, except that nal\_unit\_type is set to 14 and priority\_id may be changed, and insert the prefix NAL unit immediately before the NAL unit nalUnit in decoding order. After the last application of this operation, at least one of all the inserted prefix NAL units by the applications of this operation shall have priority\_id equal to 0. + - c. Remove the NAL unit header MVC extension of nalUnit. + +#### G.8.6 MFC enhanced resolution picture reconstruction + +This clause does not form an integral part of this Recommendation | International Standard. + +This informative clause describes a process for reconstructing the enhanced resolution stereo views from the coded video sequences conforming to the MFC High profile. The process is applied to each colour component independently. + +Inputs of this process are: + +- a (refW)x(refH) modified inter-view prediction reference picture sample array RpuPicture derived in clause G.8.4.1, +- a (RpuW)x(RpuH) cropped decoded picture sample array decBasePicture for a luma or a chroma component of the base view component with VOIdx equal to 0, +- a (RpuW)x(RpuH) cropped decoded picture sample array decEnhPicture for a luma or a chroma component of the view component with VOIdx equal to 1. + +Outputs of this process are: + +- a (RpuW)x(RpuH) enhanced resolution picture sample array leftPicture for a luma or a chroma component of the left view, +- a (RpuW)x(RpuH) enhanced resolution picture sample array rightPicture for a luma or a chroma component of the right view. + +The input sample array decBasePicture is the output cropped picture of the decoded sample arrays $S_L$ , $S_{Cb}$ or $S_{Cr}$ respectively for each colour component derived in clause 8.7 for a decoded frame or complementary field pair or field of a decoded frame from a base view. The input sample array decEnhPicture is the output cropped picture of the decoded sample arrays $S_L$ , $S_{Cb}$ or $S_{Cr}$ respectively for each colour component derived in clause 8.7 for a decoded frame or complementary field pair or field of a decoded frame of a non-base view. + +Depending on the value of rpu\_field\_processing\_flag, the following applies: + +- If rpu\_field\_processing\_flag is equal to 1, the modified inter-view prediction reference picture RpuPicture is a field, the cropped decoded view component of the base view, decBasePicture, is a field, the cropped decoded view component of the non-base view, decEnhPicture, is a field, the enhanced resolution left view picture leftPicture is a + +field, the enhanced resolution right view picture rightPicture is a field, and the enhanced resolution picture reconstruction is applied to the individual fields separately. + +- Otherwise (rpu\_field\_processing\_flag is equal to 0), the modified inter-view prediction reference picture RpuPicture is a frame, the cropped decoded view component of the base view, decBasePicture, is a frame, the cropped decoded view component of the non-base view, decEnhPicture, is a frame, the enhanced resolution left view picture leftPicture is a frame, the enhanced resolution right view picture rightPicture is a frame, and the enhanced resolution picture reconstruction is applied to the frame. + +The mathematical function Clip1() is defined with Clip1() being substituted with Clip1Y() for the luma component and Clip1() being substituted with Clip1C() for the chroma components, respectively. + +The variable tVal is set equal to ( 1 << ( BitDepthY - 1 ) ) for the luma component and tVal is set equal to ( 1 << ( BitDepthC - 1 ) ) for a chroma component, respectively. + +Let upBasePic[ x, y ] be an (RpuW)x(RpuH) array of samples with x = 0..RpuW - 1 and y = 0..RpuH - 1. + +Let resPicture[ x, y ] be an (RpuW)x(RpuH) array of samples with x = 0..RpuW - 1 and y = 0..RpuH - 1. + +Let upResPic[ x, y ] be an (RpuW)x(RpuH) array of samples with x = 0..RpuW - 1 and y = 0..RpuH - 1. + +- If mfc\_format\_idc is equal to 0, let tempDecBasePic[ x, y ] be a (SbsV)x(RpuH) array of samples with x = 0..SbsV - 1 and y = 0..RpuH - 1, tempDecEnhPic[ x, y ] be a (RpuW)x(TabV) array of samples with x = 0..RpuW - 1 and y = 0..TabV - 1, and tempRpuPic[ x, y ] be a (RpuW)x(TabV) array of samples with x = 0..RpuW - 1 and y = 0..TabV - 1. +- Otherwise (mfc\_format\_idc is equal to 1), let tempDecBasePic[ x, y ] be a (RpuW)x(TabV) array of samples with x = 0..RpuW - 1 and y = 0..TabV - 1, tempDecEnhPic[ x, y ] be a (SbsV)x(RpuH) array of samples with x = 0..SbsV - 1 and y = 0..RpuH - 1, and tempRpuPic[ x, y ] be a (SbsV)x(RpuH) array of samples with x = 0..SbsV - 1 and y = 0..RpuH - 1. + +The samples of enhanced resolution picture sample array for the left view leftPicture[ x, y ] and the right view rightPicture[ x, y ] with x = 0..RpuW - 1 and y = 0..RpuH - 1 are derived as follows: + +- If mfc\_format\_idc is equal to 0, the following applies: + +1. leftPicture[ x, y ] with x = 0..RpuW - 1 and y = 0..RpuH - 1 is derived from the input of the arrays decBasePicture[ x, y ] with x = 0..SbsV - 1 and y = 0..RpuH - 1, decEnhPicture[ x, y ] with x = 0..RpuW - 1 and y = 0..TabV - 1 and RpuPicture[ x, y ] with x = leftOffset..RpuW - 1 + leftOffset and y = topOffset..TabV - 1 + topOffset as specified by the following ordered steps: + +- a. tempDecBasePic[ x, y ] = decBasePicture[ x, y ] (G-42) + +with x = 0..SbsV - 1 and y = 0..RpuH - 1 + +- b. tempDecEnhPic[ x, y ] = decEnhPicture[ x, y ] (G-43) + +with x = 0..RpuW - 1 and y = 0..TabV - 1 + +- c. tempRpuPic[ x, y ] = RpuPicture[ x + leftOffset, y + topOffset ] (G-44) + +with x = 0..RpuW - 1 and y = 0..TabV - 1 + +- d. Apply the following one-dimensional upsampling process: + +$$gMin = - 2 - View0OffsetX \quad (G-45)$$ + +$$upBasePic[ 2 * x + view0OffsetX, y ] = tempDecBasePic[ x, y ] \quad (G-46)$$ + +$$\begin{aligned} upBasePic[ 2 * x + ( 1 - view0OffsetX ), y ] = & \\ & Clip1( ( 3 * tempDecBasePic[ Clip3( 0, x + gMin, SbsV - 1 ), y ] - \\ & 17 * tempDecBasePic[ Clip3( 0, x + gMin + 1, SbsV - 1 ), y ] + \\ & 78 * tempDecBasePic[ Clip3( 0, x + gMin + 2, SbsV - 1 ), y ] + \\ & 78 * tempDecBasePic[ Clip3( 0, x + gMin + 3, SbsV - 1 ), y ] - \\ & 17 * tempDecBasePic[ Clip3( 0, x + gMin + 4, SbsV - 1 ), y ] + \\ & 3 * tempDecBasePic[ Clip3( 0, x + gMin + 5, SbsV - 1 ), y ] + 64 ) >> 7 ) \end{aligned} \quad (G-47)$$ + +with x = 0..SbsV - 1 and y = 0..RpuH - 1 + +- e. resPicture[ x, y ] = Clip3( - tVal, tVal - 1, ( tempDecEnhPic[ x, y ] - tempRpuPic[ x, y ] ) ) (G-48) + +with x = 0..RpuW - 1 and y = 0..TabV - 1 + +- f. Apply the following one-dimensional upsampling process: + +$$\text{upResPic}[x, 2 * y] = \text{resPicture}[x, y] \quad (\text{G-49})$$ + +$$\begin{aligned} \text{upResPic}[x, 2 * y + 1] = & \text{Clip3}(-tVal, tVal - 1, (3 * \text{resPicture}[x, \text{Clip3}(0, y - 2, \text{TabV} - 1)] - \\ & 17 * \text{resPicture}[x, \text{Clip3}(0, y - 1, \text{TabV} - 1)] + \\ & 78 * \text{resPicture}[x, \text{Clip3}(0, y, \text{TabV} - 1)] + \\ & 78 * \text{resPicture}[x, \text{Clip3}(0, y + 1, \text{TabV} - 1)] - \\ & 17 * \text{resPicture}[x, \text{Clip3}(0, y + 2, \text{TabV} - 1)] + \\ & 3 * \text{resPicture}[x, \text{Clip3}(0, y + 3, \text{TabV} - 1)] + 64) \gg 7) ) \end{aligned} \quad (\text{G-50})$$ + +with $x = 0..RpuW - 1$ and $y = 0..TabV - 1$ + +- g. $\text{leftPicture}[x, y] = \text{Clip1}(\text{upBasePic}[x, y] + \text{upResPic}[x, y])$ (G-51) + +with $x = 0..RpuW - 1$ and $y = 0..RpuH - 1$ + +2. $\text{rightPicture}[x, y]$ with $x = 0..RpuW - 1$ and $y = 0..RpuH - 1$ is derived from the input of the arrays $\text{decBasePicture}[x, y]$ with $x = SbsV..RpuW - 1$ and $y = 0..RpuH - 1$ , $\text{decEnhPicture}[x, y]$ with $x = 0..RpuW - 1$ and $y = \text{TabV}..RpuH - 1$ and $\text{RpuPicture}[x, y]$ with $x = \text{leftOffset}..RpuW - 1 + \text{leftOffset}$ and $y = \text{TabV} + \text{topOffset}..RpuH - 1 + \text{topOffset}$ as specified by the following ordered steps: + +- a. $\text{tempDecBasePic}[x, y] = \text{decBasePicture}[x + SbsV, y]$ (G-52) + +with $x = 0..SbsV - 1$ and $y = 0..RpuH - 1$ + +- b. $\text{tempDecEnhPic}[x, y] = \text{decEnhPicture}[x, y + \text{TabV}]$ (G-53) + +with $x = 0..RpuW - 1$ and $y = 0..TabV - 1$ + +- c. $\text{tempRpuPic}[x, y] = \text{RpuPicture}[x + \text{leftOffset}, y + \text{TabV} + \text{topOffset}]$ (G-54) + +with $x = 0..RpuW - 1$ and $y = 0..TabV - 1$ + +- d. Apply the following one-dimensional upsampling process: + +$$gMin = -2 - \text{View1OffsetX}, \quad (\text{G-55})$$ + +$$\text{upBasePic}[2 * x + \text{view1OffsetX}, y] = \text{tempDecBasePic}[x, y], \quad (\text{G-56})$$ + +$$\begin{aligned} \text{upBasePic}[2 * x + (1 - \text{view1OffsetX}), y] = & \text{Clip1}((3 * \text{tempDecBasePic}[\text{Clip3}(0, x + gMin, SbsV - 1), y] - \\ & 17 * \text{tempDecBasePic}[\text{Clip3}(0, x + gMin + 1, SbsV - 1), y] + \\ & 78 * \text{tempDecBasePic}[\text{Clip3}(0, x + gMin + 2, SbsV - 1), y] + \\ & 78 * \text{tempDecBasePic}[\text{Clip3}(0, x + gMin + 3, SbsV - 1), y] - \\ & 17 * \text{tempDecBasePic}[\text{Clip3}(0, x + gMin + 4, SbsV - 1), y] + \\ & 3 * \text{tempDecBasePic}[\text{Clip3}(0, x + gMin + 5, SbsV - 1), y] + 64) \gg 7) ) \end{aligned} \quad (\text{G-57})$$ + +with $x = 0..SbsV - 1$ and $y = 0..RpuH - 1$ + +- e. $\text{resPicture}[x, y] = \text{Clip3}(-tVal, tVal - 1, (\text{tempDecEnhPic}[x, y] - \text{tempRpuPic}[x, y]))$ (G-58) + +with $x = 0..RpuW - 1$ and $y = 0..TabV - 1$ + +- f. Apply the following one-dimensional upsampling process: + +$$\text{upResPic}[x, 2 * y] = \text{resPicture}[x, y] \quad (\text{G-59})$$ + +$$\begin{aligned} \text{upResPic}[x, 2 * y + 1] = & \text{Clip3}(-tVal, tVal - 1, (3 * \text{resPicture}[x, \text{Clip3}(0, y - 2, \text{TabV} - 1)] - \\ & 17 * \text{resPicture}[x, \text{Clip3}(0, y - 1, \text{TabV} - 1)] + \\ & 78 * \text{resPicture}[x, \text{Clip3}(0, y, \text{TabV} - 1)] + \\ & 78 * \text{resPicture}[x, \text{Clip3}(0, y + 1, \text{TabV} - 1)] - \\ & 17 * \text{resPicture}[x, \text{Clip3}(0, y + 2, \text{TabV} - 1)] + \\ & 3 * \text{resPicture}[x, \text{Clip3}(0, y + 3, \text{TabV} - 1)] + 64) \gg 7) ) \end{aligned} \quad (\text{G-60})$$ + +with $x = 0..RpuW - 1$ and $y = 0..TabV - 1$ + +- g. $\text{rightPicture}[x, y] = \text{Clip1}(\text{upBasePic}[x, y] + \text{upResPic}[x, y])$ (G-61) + +with $x = 0..RpuW - 1$ and $y = 0..RpuH - 1$ + +– Otherwise ( mfc\_format\_idc is equal to 1 ), the following applies: + +1. leftPicture[ x, y ] with x = 0..RpuW – 1 and y = 0..RpuH – 1 is derived from the input of the arrays decBasePicture[ x, y ] with x = 0..RpuW – 1 and y = 0..TabV – 1, decEnhPicture[ x, y ] with x = 0..SbsV – 1 and y = 0..RpuH – 1 and RpuPicture[ x, y ] with x = leftOffset..SbsV – 1 + leftOffset and y = topOffset..RpuH – 1 + topOffset as specified by the following ordered steps: + +- a. tempDecBasePic[ x, y ] = decBasePicture[ x, y ] (G-62) + +with x = 0..RpuW – 1 and y = 0..TabV – 1 + +- b. tempDecEnhPic[ x, y ] = decEnhPicture[ x, y ] (G-63) + +with x = 0..SbsV – 1 and y = 0..RpuH – 1 + +- c. tempRpuPic[ x, y ] = RpuPicture[ x + leftOffset, y + topOffset ] (G-64) + +with x = 0..SbsV – 1 and y = 0..RpuH – 1 + +- d. Apply the following one-dimensional upsampling process: + +$$gMin = - 2 - View0OffsetY \quad (G-65)$$ + +$$upBasePic[ x, 2 * y + view0OffsetY ] = tempDecBasePic[ x, y ] \quad (G-66)$$ + +$$\begin{aligned} upBasePic[ x, 2 * y + ( 1 - view0OffsetY ) ] = & \\ & Clip1( ( 3 * tempDecBasePic[ x, Clip3( 0, y + gMin, TabV - 1 ) ] - \\ & 17 * tempDecBasePic[ x, Clip3( 0, y + gMin + 1, TabV - 1 ) ] + \\ & 78 * tempDecBasePic[ x, Clip3( 0, y + gMin + 2, TabV - 1 ) ] + \\ & 78 * tempDecBasePic[ x, Clip3( 0, y + gMin + 3, TabV - 1 ) ] - \\ & 17 * tempDecBasePic[ x, Clip3( 0, y + gMin + 4, TabV - 1 ) ] + \\ & 3 * tempDecBasePic[ x, Clip3( 0, y + gMin + 5, TabV - 1 ) ] + 64 ) \gg 7 ) \end{aligned} \quad (G-67)$$ + +with x = 0..RpuW – 1 and y = 0..TabV – 1 + +- e. resPicture[ x, y ] = Clip3( - tVal, tVal – 1, ( tempDecEnhPic[ x, y ] – tempRpuPic[ x, y ] ) ) (G-68) + +with x = 0..SbsV – 1 and y = 0..RpuH – 1 + +- f. Apply the following one-dimensional upsampling process: + +$$upResPic[ 2 * x, y ] = resPicture[ x, y ] \quad (G-69)$$ + +$$\begin{aligned} upResPic[ 2 * x + 1, y ] = & \\ & Clip3( - tVal, tVal – 1, ( 3 * resPicture[ Clip3( 0, x – 2, TabV – 1 ), y ] - \\ & 17 * resPicture[ Clip3( 0, x – 1, SbsV – 1 ), y ] + \\ & 78 * resPicture[ Clip3( 0, x, SbsV – 1 ), y ] + \\ & 78 * resPicture[ Clip3( 0, x + 1, SbsV – 1 ), y ] - \\ & 17 * resPicture[ Clip3( 0, x + 2, SbsV – 1 ), y ] + \\ & 3 * resPicture[ Clip3( 0, x + 3, SbsV – 1 ), y ] + 64 ) \gg 7 ) \end{aligned} \quad (G-70)$$ + +with x = 0..SbsV – 1 and y = 0..RpuH – 1 + +- g. leftPicture[ x, y ] = Clip1( upBasePic[ x, y ] + upResPic[ x, y ] ) (G-71) + +with x = 0..RpuW – 1 and y = 0..RpuH – 1 + +2. rightPicture[ x, y ] with x = 0..RpuW – 1 and y = 0..RpuH – 1 is derived from the input of the arrays decBasePicture[ x, y ] with x = 0..RpuW – 1 and y = TabV..RpuH – 1, decEnhPicture[ x, y ] with x = SbsV..RpuW – 1 and y = 0..RpuH – 1 and RpuPicture[ x, y ] with x = SbsV + leftOffset..RpuW – 1 + leftOffset and y = topOffset..RpuH – 1 + topOffset as specified by the following ordered steps: + +- a. tempDecBasePic[ x, y ] = decBasePicture[ x, y + TabV ] (G-72) + +with x = 0..RpuW – 1 and y = 0..TabV – 1 + +- b. tempDecEnhPic[ x, y ] = decEnhPicture[ x + SbsV, y ] (G-73) + +with x = 0..SbsV – 1 and y = 0..RpuH – 1 + +- c. tempRpuPic[ x, y ] = RpuPicture[ x + SbsV + leftOffset, y + topOffset ] (G-74) + +with x = 0..SbsV – 1 and y = 0..RpuH – 1 + +- d. Apply the following one-dimensional upsampling process: + +$$gMin = -2 - View1OffsetY \quad (G-75)$$ + +$$upBasePic[ x, 2 * y + view1OffsetY ] = tempDecBasePic[ x, y ] \quad (G-76)$$ + +$$\begin{aligned} upBasePic[ x, 2 * y + (1 - view1OffsetY) ] = & \\ & Clip1( ( 3 * tempDecBasePic[ x, Clip3( 0, y + gMin, TabV - 1 ) ] - \\ & 17 * tempDecBasePic[ x, Clip3( 0, y + gMin + 1, TabV - 1 ) ] + \\ & 78 * tempDecBasePic[ x, Clip3( 0, y + gMin + 2, TabV - 1 ) ] + \\ & 78 * tempDecBasePic[ x, Clip3( 0, y + gMin + 3, TabV - 1 ) ] - \\ & 17 * tempDecBasePic[ x, Clip3( 0, y + gMin + 4, TabV - 1 ) ] + \\ & 3 * tempDecBasePic[ x, Clip3( 0, y + gMin + 5, TabV - 1 ) ] + 64 ) \gg 7 ) \end{aligned} \quad (G-77)$$ + +with $x = 0..RpuW - 1$ and $y = 0..TabV - 1$ + +- e. $resPicture[ x, y ] = Clip3( -tVal, tVal - 1, ( tempDecEnhPic[ x, y ] - tempRpuPic[ x, y ] ) ) \quad (G-78)$ + +with $x = 0..SbsV - 1$ and $y = 0..RpuH - 1$ + +- f. Apply the following one-dimensional upsampling process: + +$$upResPic[ 2 * x, y ] = resPicture[ x, y ] \quad (G-79)$$ + +$$\begin{aligned} upResPic[ 2 * x + 1, y ] = & \\ & Clip3( -tVal, tVal - 1, ( 3 * resPicture[ Clip3( 0, x - 2, SbsV - 1 ), y ] - \\ & 17 * resPicture[ Clip3( 0, x - 1, SbsV - 1 ), y ] + \\ & 78 * resPicture[ Clip3( 0, x, SbsV - 1 ), y ] + \\ & 78 * resPicture[ Clip3( 0, x + 1, SbsV - 1 ), y ] - \\ & 17 * resPicture[ Clip3( 0, x + 2, SbsV - 1 ), y ] + \\ & 3 * resPicture[ Clip3( 0, x + 3, SbsV - 1 ), y ] + 64 ) \gg 7 ) \end{aligned} \quad (G-80)$$ + +with $x = 0..SbsV - 1$ and $y = 0..RpuH - 1$ + +- g. $rightPicture[ x, y ] = Clip1( upBasePic[ x, y ] + upResPic[ x, y ] ) \quad (G-81)$ + +with $x = 0..RpuW - 1$ and $y = 0..RpuH - 1$ + +## G.9 Parsing process + +The specifications in clause 9 apply. + +## G.10 Profiles and levels + +The specifications in Annex A apply. Additional profiles and specific values of profile\_idc are specified in the following. + +The profiles that are specified in clause G.10.1 are also referred to as the profiles specified in Annex G. + +### G.10.1 Profiles + +All constraints for picture parameter sets that are specified in the following are constraints for picture parameter sets that become the active picture parameter set or an active view picture parameter set inside the bitstream. All constraints for MVC sequence parameter sets that are specified in the following are constraints for MVC sequence parameter sets that become the active MVC sequence parameter set or an active view MVC sequence parameter set inside the bitstream. + +#### G.10.1.1 Multiview High profile + +Bitstreams conforming to the Multiview High profile shall obey the following constraints: + +- The base view bitstream as specified in clause G.8.5.4 shall obey all constraints of the Progressive High profile specified in clause A.2.4.1 and all active sequence parameter sets shall fulfil one or more of the following conditions: + - profile\_idc is equal to 100 or 77 and constraint\_set4\_flag is equal to 1, + - (profile\_idc is equal to 66 or constraint\_set0\_flag is equal to 1) and constraint\_set1\_flag is equal to 1, + - profile\_idc is equal to 77 and constraint\_set0\_flag is equal to 1, + - profile\_idc is equal to 88, constraint\_set1\_flag is equal to 1, and constraint\_set4\_flag is equal to 1. +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain nal\_unit\_type values in the range of 2 to 4, inclusive. + +- MVC sequence parameter sets shall have `frame_mbs_only_flag` equal to 1. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have `num_slice_groups_minus1` equal to 0 only. +- Picture parameter sets shall have `redundant_pic_cnt_present_flag` equal to 0 only. +- MVC sequence parameter sets shall have `chroma_format_idc` in the range of 0 to 1 inclusive. +- MVC sequence parameter sets shall have `bit_depth_luma_minus8` equal to 0 only. +- MVC sequence parameter sets shall have `bit_depth_chroma_minus8` equal to 0 only. +- MVC sequence parameter sets shall have `qprime_y_zero_transform_bypass_flag` equal to 0 only. +- The level constraints specified for the Multiview High profile in clause G.10.2 shall be fulfilled. + +Conformance of a bitstream to the Multiview High profile is indicated by `profile_idc` being equal to 118. + +Decoders conforming to the Multiview High profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- All active MVC sequence parameter sets have one or more of the following conditions fulfilled: + - `profile_idc` is equal to 118, + - `profile_idc` is equal to 100 or 77 and `constraint_set4_flag` is equal to 1, + - `profile_idc` is equal to 88, `constraint_set1_flag` is equal to 1, and `constraint_set4_flag` is equal to 1, + - `profile_idc` is equal to 77 and `constraint_set0_flag` is equal to 1, + - (`profile_idc` is equal to 66 or `constraint_set0_flag` is equal to 1) and `constraint_set1_flag` is equal to 1. +- All active MVC sequence parameter sets have one or more of the following conditions fulfilled: + - `level_idc` or (`level_idc` and `constraint_set3_flag`) represent a level less than or equal to the specific level, + - `level_idc[ i ]` or (`level_idc[ i ]` and `constraint_set3_flag`) represent a level less than or equal to the specific level. + +### **G.10.1.2 Stereo High profile** + +Bitstreams conforming to the Stereo High profile shall obey the following constraints: + +- The base view bitstream as specified in clause G.8.5.4 shall obey all constraints of the High profile specified in clause A.2.4 and all active sequence parameter sets shall fulfil one of the following conditions: + - `profile_idc` is equal to 77 or `constraint_set1_flag` is equal to 1, + - `profile_idc` is equal to 100. +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain `nal_unit_type` values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have `num_slice_groups_minus1` equal to 0 only. +- Picture parameter sets shall have `redundant_pic_cnt_present_flag` equal to 0 only. +- MVC sequence parameter sets shall have `chroma_format_idc` in the range of 0 to 1 inclusive. +- MVC sequence parameter sets shall have `bit_depth_luma_minus8` equal to 0 only. +- MVC sequence parameter sets shall have `bit_depth_chroma_minus8` equal to 0 only. +- MVC sequence parameter sets shall have `qprime_y_zero_transform_bypass_flag` equal to 0 only. +- When `num_views_minus1` is present in an MVC sequence parameter set, its value shall be less than 2. +- For each access unit, the value of `level_idc` for all active view MVC sequence parameter set RBSPs shall be the same as the value of `level_idc` for the active MVC sequence parameter set RBSP. +- The level constraints specified for the Stereo High profile in clause G.10.2 shall be fulfilled. + +Conformance of a bitstream to the Stereo High profile is indicated by `profile_idc` being equal to 128. + +Decoders conforming to the Stereo High profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- All active MVC sequence parameter sets have one or more of the following conditions fulfilled: + +- profile\_idc is equal to 128, + - profile\_idc is equal to 118 and constraint\_set5\_flag is equal to 1, + - profile\_idc is equal to 100, + - profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1. +- b) All active MVC sequence parameter sets have one or more of the following conditions fulfilled: +- level\_idc or (level\_idc and constraint\_set3\_flag) represent a level less than or equal to the specific level, + - level\_idc[ i ] or (level\_idc[ i ] and constraint\_set3\_flag) represent a level less than or equal to the specific level. + +### G.10.1.3MFC High profile + +Bitstreams conforming to the MFC High profile shall obey the following constraints: + +- The base view bitstream as specified in clause G.8.5.4 shall obey all constraints of the High profile specified in clause A.2.4 and all active sequence parameter sets shall fulfil one of the following conditions: + - profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1, + - profile\_idc is equal to 100. +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain nal\_unit\_type values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0 only. +- Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0 only. +- MVC sequence parameter sets shall have chroma\_format\_idc in the range of 0 to 1 inclusive. +- MVC sequence parameter sets shall have bit\_depth\_luma\_minus8 equal to 0 only. +- MVC sequence parameter sets shall have bit\_depth\_chroma\_minus8 equal to 0 only. +- MVC sequence parameter sets shall have qpprime\_y\_zero\_transform\_bypass\_flag equal to 0 only. +- When num\_views\_minus1 is present in an MVC sequence parameter set, its value shall be less than 2. +- For each access unit, the value of level\_idc for all active view MVC sequence parameter set RBSPs shall be the same as the value of level\_idc for the active MVC sequence parameter set RBSP. +- The level constraints specified for the MFC High profile in clause G.10.2 shall be fulfilled. + +Conformance of a bitstream to the MFC High profile is indicated by profile\_idc being equal to 134. + +Decoders conforming to the MFC High profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- a) All active MVC sequence parameter sets have one or more of the following conditions fulfilled: +- profile\_idc is equal to 134, + - profile\_idc is equal to 128, + - profile\_idc is equal to 118 and constraint\_set5\_flag is equal to 1, + - profile\_idc is equal to 100, + - profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1. +- b) All active MVC sequence parameter sets have one or more of the following conditions fulfilled: +- level\_idc or (level\_idc and constraint\_set3\_flag) represent a level less than or equal to the specific level, + - level\_idc[ i ] or (level\_idc[ i ] and constraint\_set3\_flag) represent a level less than or equal to the specific level. + +### G.10.2 Levels + +The following is specified for expressing the constraints in this clause: + +- Let access unit n be the n-th access unit in decoding order with the first access unit being access unit 0. + +- Let picture $n$ be the primary coded picture or the corresponding decoded picture of access unit $n$ . + +Let the variable $fR$ be derived as follows: + +- If the level number is equal to 6.0, 6.1, or 6.2, $fR$ is set equal to $1 \div 300$ . +- Otherwise, if picture $n$ is a frame, $fR$ is set equal to $1 \div 172$ . +- Otherwise (picture $n$ is a field), $fR$ is set equal to $1 \div (172 * 2)$ . + +The value of $mvcScaleFactor$ is set equal to 2. + +The value of $NumViews$ is set equal to $applicable\_op\_num\_views\_minus1[ i ][ j ]$ plus 1, which indicates the number of views required for decoding the target output views corresponding to the $j$ -th operation point for $level\_idc[ i ]$ as signalled in the subset sequence parameter set. + +#### G.10.2.1 Level limits common to Multiview High, Stereo High, and MFC High profiles + +Bitstreams conforming to the Multiview High profile at a specified level shall obey the following constraints: + +- The nominal removal time of access unit $n$ (with $n > 0$ ) from the CPB as specified in clause C.1.2, satisfies the constraint that $t_{r,n}(n) - t_r(n - 1)$ is greater than or equal to $\text{Max}(\text{NumViews} * \text{PicSizeInMbs} \div (\text{mvcScaleFactor} * \text{MaxMBPS}), fR)$ , where $\text{MaxMBPS}$ is the value specified in Table A-1 that applies to picture $n - 1$ , and $\text{PicSizeInMbs}$ is the number of macroblocks in a single view component of picture $n - 1$ . +- The difference between consecutive output times of pictures from the DPB as specified in clause C.2.2, satisfies the constraint that $\Delta t_{o,dpb}(n) \geq \text{Max}(\text{NumViews} * \text{PicSizeInMbs} \div (\text{mvcScaleFactor} * \text{MaxMBPS}), fR)$ , where $\text{MaxMBPS}$ is the value specified in Table A-1 for picture $n$ , and $\text{PicSizeInMbs}$ is the number of macroblocks of a single view component of picture $n$ , provided that picture $n$ is a picture that is output and is not the last picture of the bitstream that is output. +- $\text{PicWidthInMbs} * \text{FrameHeightInMbs} \leq \text{MaxFS}$ , where $\text{MaxFS}$ is specified in Table A-1. +- $\text{PicWidthInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ , where $\text{MaxFS}$ is specified in Table A-1. +- $\text{FrameHeightInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ , where $\text{MaxFS}$ is specified in Table A-1. +- $\text{max\_dec\_frame\_buffering} \leq \text{MaxDpbFrames}$ , where $\text{MaxDpbFrames}$ is equal to $\text{Min}(\text{mvcScaleFactor} * \text{MaxDpbMbs} / (\text{PicWidthInMbs} * \text{FrameHeightInMbs}), \text{Max}(1, \text{Ceil}(\log_2(\text{NumViews}))) * 16)$ and $\text{MaxDpbMbs}$ is specified in Table A-1. +- The vertical motion vector component range for luma motion vectors does not exceed the range from $-\text{MaxVmvR}$ to $(\text{MaxVmvR} - 0.25)$ in units of luma frame samples, where $\text{MaxVmvR}$ is specified in Table A-1. +- The horizontal motion vector component range for luma motion vectors does not exceed the following range: + - If the level number is less than 6.0, the specified range is from $-2048$ to $2047.75$ , inclusive, in units of luma samples. + - Otherwise, the specified range is from $-8192$ to $8191.75$ , inclusive, in units of luma samples. +- Let $\text{setOf2Mb}$ be the set of unsorted pairs of macroblocks that contains the unsorted pairs of macroblocks $(\text{mbA}, \text{mbB})$ of a coded video sequence for which any of the following conditions are true: + - $\text{mbA}$ and $\text{mbB}$ are macroblocks that belong to the same slice and are consecutive in decoding order, + - $\text{separate\_colour\_plane\_flag}$ is equal to 0, $\text{mbA}$ is the last macroblock (in decoding order) of a slice, and $\text{mbB}$ is the first macroblock (in decoding order) of the next slice in decoding order, + - $\text{separate\_colour\_plane\_flag}$ is equal to 1, $\text{mbA}$ is the last macroblock (in decoding order) of a slice with a particular value of $\text{colour\_plane\_id}$ , and $\text{mbB}$ is the first macroblock (in decoding order) of the next slice with the same value of $\text{colour\_plane\_id}$ in decoding order. + +NOTE 1 – In the two above conditions, the macroblocks $\text{mbA}$ and $\text{mbB}$ can belong to different pictures. + +For each unsorted pair of macroblocks $(\text{mbA}, \text{mbB})$ of the set $\text{setOf2Mb}$ , the total number of motion vectors (given by the sum of the number of motion vectors for macroblock $\text{mbA}$ and the number of motion vectors for macroblock $\text{mbB}$ ) does not exceed $\text{MaxMvsPer2Mb}$ , where $\text{MaxMvsPer2Mb}$ is specified in Table A-1. The number of motion vectors for each macroblock is the value of the variable $\text{MvCnt}$ after the completion of the intra or inter prediction process for the macroblock. + +NOTE 2 – When separate\_colour\_plane\_flag is equal to 0, the constraint specifies that the total number of motion vectors for two consecutive macroblocks in decoding order must not exceed MaxMvsPer2Mb. When separate\_colour\_plane\_flag is equal to 1, the constraint specifies that the total number of motion vectors for two consecutive macroblocks with the same value of colour\_plane\_id in decoding order must not exceed MaxMvsPer2Mb. For macroblocks that are consecutive in decoding order but are associated with a different value of colour\_plane\_id, no constraint for the total number of motion vectors is specified. + +- j) The number of bits of macroblock\_layer( ) data for any macroblock is not greater than $128 + \text{RawMbBits}$ . Depending on entropy\_coding\_mode\_flag, the bits of macroblock\_layer( ) data are counted as follows: + - If entropy\_coding\_mode\_flag is equal to 0, the number of bits of macroblock\_layer( ) data is given by the number of bits in the macroblock\_layer( ) syntax structure for a macroblock. + - Otherwise (entropy\_coding\_mode\_flag is equal to 1), the number of bits of macroblock\_layer( ) data for a macroblock is given by the number of times read\_bits( 1 ) is called in clauses 9.3.3.2.2 and 9.3.3.2.3 when parsing the macroblock\_layer( ) associated with the macroblock. + - k) The removal time of access unit 0 shall satisfy the constraint that the number of slices in picture 0 is less than or equal to $\text{mvcScaleFactor} * (\text{Max}(\text{PicSizeInMbs}, \text{fR} * \text{MaxMBPS}) + \text{MaxMBPS} * (t_r(0) - t_{r,n}(0))) \div \text{SliceRate}$ , where MaxMBPS and SliceRate are the values specified in Tables A-1 and A-4, respectively, that apply to picture 0 and PicSizeInMbs is the number of macroblocks in a single view component of picture 0. + - l) The removal time of access unit 0 shall satisfy the constraint that the number of slices in each view component of picture 0 is less than or equal to $(\text{Max}(\text{PicSizeInMbs}, \text{fR} * \text{MaxMBPS}) + \text{MaxMBPS} * (t_r(0) - t_{r,n}(0))) \div \text{SliceRate}$ , where MaxMBPS and SliceRate are the values specified in Tables A-1 and A-4, respectively, that apply to picture 0 and PicSizeInMbs is the number of macroblocks in a single view component of picture 0. + - m) The difference between consecutive removal times of access units n and n – 1 with n > 0 shall satisfy the constraint that the number of slices in picture n is less than or equal to $\text{mvcScaleFactor} * \text{MaxMBPS} * (t_r(n) - t_r(n - 1)) \div \text{SliceRate}$ , where SliceRate is the value specified in Table A-4 that applies to picture n. + - n) The difference between consecutive removal times of access units n and n – 1 with n > 0 shall satisfy the constraint that the number of slices in each view component of picture n is less than or equal to $\text{MaxMBPS} * (t_r(n) - t_r(n - 1)) \div \text{SliceRate}$ , where SliceRate is the value specified in Table A-4 that applies to picture n. + - o) MVC sequence parameter sets shall have direct\_8x8\_inference\_flag equal to 1 for the levels specified in Table A-4. + - p) The value of sub\_mb\_type[ mbPartIdx ] with mbPartIdx = 0..3 in B macroblocks with mb\_type equal to B\_8x8 shall not be equal to B\_Bi\_8x4, B\_Bi\_4x8, or B\_Bi\_4x4 for the levels in which MinLumaBiPredSize is shown as 8x8 in Table A-4. + - q) For the VCL HRD parameters, $\text{BitRate}[\text{SchedSelIdx}] \leq \text{cpbBrVclFactor} * \text{MaxBR}$ and $\text{CpbSize}[\text{SchedSelIdx}] \leq \text{cpbBrVclFactor} * \text{MaxCPB}$ for at least one value of SchedSelIdx, where cpbBrVclFactor is equal to 1250. With vui\_mvc\_vcl\_hrd\_parameters\_present\_flag[ i ] being the syntax element, in the MVC VUI parameters extension of the active MVC sequence parameter set, that is associated with the VCL HRD parameters that are used for conformance checking (as specified in Annex C), BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are given as follows: + - If vui\_mvc\_vcl\_hrd\_parameters\_present\_flag equal to 1, BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are given by Equations E-81 and E-82, respectively, using the syntax elements of the hrd\_parameters( ) syntax structure that immediately follows vui\_mvc\_vcl\_hrd\_parameters\_present\_flag. + - Otherwise (vui\_mvc\_vcl\_hrd\_parameters\_present\_flag equal to 0), BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are inferred as specified in clause E.2.2 for VCL HRD parameters. +- MaxBR and MaxCPB are specified in Table A-1 in units of cpbBrVclFactor bits/s and cpbBrVclFactor bits, respectively. The bitstream shall satisfy these conditions for at least one value of SchedSelIdx in the range 0 to cpb\_cnt\_minus1, inclusive. +- r) For the NAL HRD parameters, $\text{BitRate}[\text{SchedSelIdx}] \leq \text{cpbBrNalFactor} * \text{MaxBR}$ and $\text{CpbSize}[\text{SchedSelIdx}] \leq \text{cpbBrNalFactor} * \text{MaxCPB}$ for at least one value of SchedSelIdx, where cpbBrNalFactor is equal to 1500. With vui\_mvc\_nal\_hrd\_parameters\_present\_flag[ i ] being the syntax element, in the MVC VUI parameters extension of the active MVC sequence parameter set, that is associated with the NAL HRD parameters that are used for conformance checking (as specified in Annex C), BitRate[ SchedSelIdx ] and CpbSize[ SchedSelIdx ] are given as follows: + +- If `vui_mvc_nal_hrd_parameters_present_flag` equal to 1, `BitRate[ SchedSelIdx ]` and `CpbSize[ SchedSelIdx ]` are given by Equations E-81 and E-82, respectively, using the syntax elements of the `hrd_parameters()` syntax structure that immediately follows `vui_mvc_nal_hrd_parameters_present_flag`. +- Otherwise (`vui_mvc_nal_hrd_parameters_present_flag` equal to 0), `BitRate[ SchedSelIdx ]` and `CpbSize[ SchedSelIdx ]` are inferred as specified in clause E.2.2 for NAL HRD parameters. + +MaxBR and MaxCPB are specified in Table A-1 in units of `cpbBrNalFactor` bits/s and `cpbBrNalFactor` bits, respectively. The bitstream shall satisfy these conditions for at least one value of `SchedSelIdx` in the range 0 to `cpb_cnt_minus1`, inclusive. + +- s) The sum of the `NumBytesInNALUnit` variables for access unit 0 is less than or equal to $384 * mvcScaleFactor * ( \text{Max}( \text{PicSizeInMbs}, fR * \text{MaxMBPS} ) + \text{MaxMBPS} * ( t_r( 0 ) - t_{r,n}( 0 ) ) ) \div \text{MinCR}$ , where `MaxMBPS` and `MinCR` are the values specified in Table A-1 that apply to picture 0 and `PicSizeInMbs` is the number of macroblocks in a single view component of picture 0. +- t) The sum of the `NumBytesInNALUnit` variables for the VCL NAL units of each view component of access unit 0 is less than or equal to $384 * ( \text{Max}( \text{PicSizeInMbs}, fR * \text{MaxMBPS} ) + \text{MaxMBPS} * ( t_r( 0 ) - t_{r,n}( 0 ) ) ) \div \text{MinCR}$ , where `MaxMBPS` and `MinCR` are the values specified in Table A-1 that apply to picture 0 and `PicSizeInMbs` is the number of macroblocks in a single view component of picture 0. +- u) The sum of the `NumBytesInNALUnit` variables for access unit $n$ with $n > 0$ is less than or equal to $384 * mvcScaleFactor * \text{MaxMBPS} * ( t_r( n ) - t_r( n - 1 ) ) \div \text{MinCR}$ , where `MaxMBPS` and `MinCR` are the values specified in Table A-1 that apply to picture $n$ . +- v) The sum of the `NumBytesInNALUnit` variables for the VCL NAL units of each view component of access unit $n$ with $n > 0$ is less than or equal to $384 * \text{MaxMBPS} * ( t_r( n ) - t_r( n - 1 ) ) \div \text{MinCR}$ , where `MaxMBPS` and `MinCR` are the values specified in Table A-1 that apply to picture $n$ . +- w) When `PicSizeInMbs` is greater than 1620, the number of macroblocks in any coded slice shall not exceed `MaxFS / 4`, where `MaxFS` is specified in Table A-1. +- x) `max_num_ref_frames` shall be less than or equal to `MaxDpbFrames / mvcScaleFactor` for each view component, where `MaxDpbFrames` is specified in item f). + +Table A-1 specifies the limits for each level. A definition of all levels identified in the "Level number" column of Table A-1 is specified for the Multiview High, Stereo High, and MFC High profiles. Table A-4 specifies limits for each level that are specific to bitstreams conforming to the Multiview High, Stereo High, and MFC High profiles. Each entry in Tables A-1 and A-4 indicates, for the level corresponding to the row of the table, the absence or value of a limit that is imposed by the variable corresponding to the column of the table, as follows: + +- If the table entry is marked as "-", no limit is imposed by the value of the variable as a requirement of bitstream conformance to the profile at the specified level. +- Otherwise, the table entry specifies the value of the variable for the associated limit that is imposed as a requirement of bitstream conformance to the profile at the specified level. + +For coded video sequences conforming to the Multiview High, Stereo High, or MFC High profile, the `level_idc` value is specified as follows: + +- If `level_idc` is not equal to 0, `level_idc` indicates the level that applies to the coded video sequence operating with all the views being target output views. + +NOTE 3 – A `level_idc` value that is not equal to zero may indicate a higher level than necessary to decode the coded video sequence operating with all the views being target output views. This may occur when a subset of views or temporal subsets are removed from a coded video sequence according to the sub-bitstream extraction process specified in clause G.8.5.3, and the `level_idc` value is not updated accordingly. + +- Otherwise (`level_idc` is equal to 0), the level that applies to the coded video sequence operating with all the views being target output views is unspecified. + +NOTE 4 – When `profile_idc` is equal to 118, 128, or 134 and `level_idc` is equal to 0, there may exist a level indicated by `level_idc[ i ]` that is applicable to the coded video sequence operating with all the views being target output views. This may occur when a subset of views or temporal subsets are removed from a coded video sequence according to the sub-bitstream extraction process specified in clause G.8.5.3, and a particular value of `level_idc[ i ]` corresponds to the resulting coded video sequence. + +In bitstreams conforming to the Multiview High, Stereo High, or MFC High profiles, the conformance of the bitstream to a specified level is indicated by the syntax element `level_idc` or `level_idc[ i ]` as follows: + +- If `level_idc` or `level_idc[ i ]` is equal to 9, the indicated level is level 1b. +- Otherwise (`level_idc` or `level_idc[ i ]` is not equal to 9), `level_idc` or `level_idc[ i ]` is equal to a value of ten times the level number (of the indicated level) specified in Table A-1. + +#### G.10.2.2 Profile specific level limits + +- a) In bitstreams conforming to the Stereo High or MFC High profile, MVC sequence parameter sets shall have `frame_mbs_only_flag` equal to 1 for the levels specified in Table A-4. + +### G.11 Byte stream format + +The specifications in Annex B apply. + +### G.12 MVC hypothetical reference decoder + +The specifications in Annex C apply with substituting MVC sequence parameter set for sequence parameter set. + +### G.13 MVC SEI messages + +The specifications in Annex D together with the extensions and modifications specified in this clause apply. + +#### G.13.1 SEI message syntax + +##### G.13.1.1 Parallel decoding information SEI message syntax + +| parallel_decoding_info( payloadSize ) { | C | Descriptor | +|------------------------------------------------------|---|------------| +| seq_parameter_set_id | 5 | ue(v) | +| for( i = 1; i <= num_views_minus1; i++ ) { | | | +| if( anchor_pic_flag ) { | | | +| for( j = 0; j <= num_anchor_refs_10[ i ]; j++ ) | | | +| pdi_init_delay_anchor_minus2_10[ i ][ j ] | 5 | ue(v) | +| for( j = 0; j <= num_anchor_refs_11[ i ]; j++ ) | | | +| pdi_init_delay_anchor_minus2_11[ i ][ j ] | 5 | ue(v) | +| } | | | +| else { | | | +| for( j = 0; j <= num_non_anchor_refs_10[ i ]; j++ ) | | | +| pdi_init_delay_non_anchor_minus2_10[ i ][ j ] | 5 | ue(v) | +| for( j = 0; j <= num_non_anchor_refs_11[ i ]; j++ ) | | | +| pdi_init_delay_non_anchor_minus2_11[ i ][ j ] | 5 | ue(v) | +| } | | | +| } | | | +| } | | | +| } | | | + +##### G.13.1.2 MVC scalable nesting SEI message syntax + +| mvc_scalable_nesting( payloadSize ) { | C | Descriptor | +|-----------------------------------------|---|------------| +| operation_point_flag | 5 | u(1) | +| if( !operation_point_flag ) { | | | +| all_view_components_in_aU_flag | 5 | u(1) | +| if( !all_view_components_in_aU_flag ) { | | | +| num_view_components_minus1 | 5 | ue(v) | + +| | | | +|-------------------------------------------------------|---|-------| +| for( i = 0; i <= num_view_components_minus1; i++ ) | | | +| sei_view_id[ i ] | 5 | u(10) | +| } | | | +| } else { | | | +| num_view_components_op_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_view_components_op_minus1; i++ ) | | | +| sei_op_view_id[ i ] | 5 | u(10) | +| sei_op_temporal_id | 5 | u(3) | +| } | | | +| while( !byte_aligned() ) | | | +| sei_nesting_zero_bit /* equal to 0 */ | 5 | f(1) | +| sei_message( ) | 5 | | +| } | | | + +### G.13.1.3 View scalability information SEI message syntax + +| view_scalability_info( payloadSize ) { | C | Descriptor | +|-------------------------------------------------------------|---|------------| +| num_operation_points_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_operation_points_minus1; i++ ) { | | | +| operation_point_id[ i ] | 5 | ue(v) | +| priority_id[ i ] | 5 | u(5) | +| temporal_id[ i ] | 5 | u(3) | +| num_target_output_views_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= num_target_output_views_minus1[ i ]; j++ ) | | | +| view_id[ i ][ j ] | 5 | ue(v) | +| profile_level_info_present_flag[ i ] | 5 | u(1) | +| bitrate_info_present_flag[ i ] | 5 | u(1) | +| frm_rate_info_present_flag[ i ] | 5 | u(1) | +| if( !num_target_output_views_minus1[ i ] ) | | | +| view_dependency_info_present_flag[ i ] | 5 | u(1) | +| parameter_sets_info_present_flag[ i ] | 5 | u(1) | +| bitstream_restriction_info_present_flag[ i ] | 5 | u(1) | +| if( profile_level_info_present_flag[ i ] ) | | | +| op_profile_level_idc[ i ] | 5 | u(24) | +| if( bitrate_info_present_flag[ i ] ) { | | | +| avg_bitrate[ i ] | 5 | u(16) | +| max_bitrate[ i ] | 5 | u(16) | +| max_bitrate_calc_window[ i ] | 5 | u(16) | +| } | | | +| if( frm_rate_info_present_flag[ i ] ) { | | | +| constant_frm_rate_idc[ i ] | 5 | u(2) | +| avg_frm_rate[ i ] | 5 | u(16) | +| } | | | +| if( view_dependency_info_present_flag[ i ] ) { | | | +| num_directly_dependent_views[ i ] | 5 | ue(v) | +| for( j = 0; j < num_directly_dependent_views[ i ]; j++ ) | | | +| directly_dependent_view_id[ i ][ j ] | 5 | ue(v) | + +| | | | +|------------------------------------------------------------|---|-------| +| } else | | | +| view_dependency_info_src_op_id[ i ] | 5 | ue(v) | +| if( parameter_sets_info_present_flag[ i ] ) { | | | +| num_seq_parameter_sets[ i ] | 5 | ue(v) | +| for( j = 0; j < num_seq_parameter_sets[ i ]; j++ ) | | | +| seq_parameter_set_id_delta[ i ][ j ] | 5 | ue(v) | +| num_subset_seq_parameter_sets[ i ] | 5 | ue(v) | +| for( j = 0; j < num_subset_seq_parameter_sets[ i ]; j++ ) | | | +| subset_seq_parameter_set_id_delta[ i ][ j ] | 5 | ue(v) | +| num_pic_parameter_sets_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= num_pic_parameter_sets_minus1[ i ]; j++ ) | | | +| pic_parameter_set_id_delta[ i ][ j ] | 5 | ue(v) | +| } else | | | +| parameter_sets_info_src_op_id[ i ] | 5 | ue(v) | +| if( bitstream_restriction_info_present_flag[ i ] ) { | | | +| motion_vectors_over_pic_boundaries_flag[ i ] | 5 | u(1) | +| max_bytes_per_pic_denom[ i ] | 5 | ue(v) | +| max_bits_per_mb_denom[ i ] | 5 | ue(v) | +| log2_max_mv_length_horizontal[ i ] | 5 | ue(v) | +| log2_max_mv_length_vertical[ i ] | 5 | ue(v) | +| max_num_reorder_frames[ i ] | 5 | ue(v) | +| max_dec_frame_buffering[ i ] | 5 | ue(v) | +| } | | | +| } | | | +| } | | | + +#### G.13.1.4 Multiview scene information SEI message syntax + +| | | | +|---------------------------------------|----------|-------------------| +| multiview_scene_info( payloadSize ) { | C | Descriptor | +| max_disparity | 5 | ue(v) | +| } | | | + +#### G.13.1.5 Multiview acquisition information SEI message syntax + +| | | | +|------------------------------------------------------------------------------|----------|-------------------| +| multiview_acquisition_info( payloadSize ) { | C | Descriptor | +| num_views_minus1 | | ue(v) | +| intrinsic_param_flag | 5 | u(1) | +| extrinsic_param_flag | 5 | u(1) | +| if( intrinsic_param_flag ) { | | | +| intrinsic_params_equal_flag | 5 | u(1) | +| prec_focal_length | 5 | ue(v) | +| prec_principal_point | 5 | ue(v) | +| prec_skew_factor | 5 | ue(v) | +| for( i = 0; i <= intrinsic_params_equal_flag ? 0 : num_views_minus1; i++ ) { | | | +| sign_focal_length_x[ i ] | 5 | u(1) | +| exponent_focal_length_x[ i ] | 5 | u(6) | + +| | | | +|----------------------------------------------------------|---|-------| +| mantissa_focal_length_x[ i ] | 5 | u(v) | +| sign_focal_length_y[ i ] | 5 | u(1) | +| exponent_focal_length_y[ i ] | 5 | u(6) | +| mantissa_focal_length_y[ i ] | 5 | u(v) | +| sign_principal_point_x[ i ] | 5 | u(1) | +| exponent_principal_point_x[ i ] | 5 | u(6) | +| mantissa_principal_point_x[ i ] | 5 | u(v) | +| sign_principal_point_y[ i ] | 5 | u(1) | +| exponent_principal_point_y[ i ] | 5 | u(6) | +| mantissa_principal_point_y[ i ] | 5 | u(v) | +| sign_skew_factor[ i ] | 5 | u(1) | +| exponent_skew_factor[ i ] | 5 | u(6) | +| mantissa_skew_factor[ i ] | 5 | u(v) | +| } | | | +| } | | | +| if( extrinsic_param_flag ) { | | | +|   prec_rotation_param | 5 | ue(v) | +|   prec_translation_param | 5 | ue(v) | +|   for( i = 0; i <= num_views_minus1; i++ ) { | | | +|     for( j = 1; j <= 3; j++ ) { /* row */ | | | +|       for( k = 1; k <= 3; k++ ) { /* column */ | | | +|         sign_r[ i ][ j ][ k ] | 5 | u(1) | +|         exponent_r[ i ][ j ][ k ] | 5 | u(6) | +|         mantissa_r[ i ][ j ][ k ] | 5 | u(v) | +|       } | | | +|       sign_t[ i ][ j ] | 5 | u(1) | +|       exponent_t[ i ][ j ] | 5 | u(6) | +|       mantissa_t[ i ][ j ] | 5 | u(v) | +|     } | | | +|   } | | | +| } | | | +| } | | | + +#### G.13.1.6 Non-required view component SEI message syntax + +| | | | +|------------------------------------------------------------------------------------|----------|-------------------| +| non_required_view_component( payloadSize ) { | C | Descriptor | +|   num_info_entries_minus1 | 5 | ue(v) | +|   for( i = 0; i <= num_info_entries_minus1; i++ ) { | | | +|     view_order_index[ i ] | 5 | ue(v) | +|     num_non_required_view_components_minus1[ i ] | 5 | ue(v) | +|     for( j = 0; j <= num_non_required_view_components_minus1[ i ]; j++ ) | | | +|       index_delta_minus1[ i ][ j ] | 5 | ue(v) | +|     } | | | +| } | | | + +#### G.13.1.7 View dependency change SEI message syntax + +| view_dependency_change( payloadSize ) { | C | Descriptor | +|----------------------------------------------------|---|------------| +| seq_parameter_set_id | 5 | ue(v) | +| anchor_update_flag | 5 | u(1) | +| non_anchor_update_flag | 5 | u(1) | +| if( anchor_update_flag ) | | | +| for( i = 1; i <= num_views_minus1; i++ ) { | | | +| for( j = 0; j < num_anchor_refs_10[ i ]; j++ ) | | | +| anchor_ref_10_flag[ i ][ j ] | 5 | u(1) | +| for( j = 0; j < num_anchor_refs_11[ i ]; j++ ) | | | +| anchor_ref_11_flag[ i ][ j ] | 5 | u(1) | +| } | | | +| if( non_anchor_update_flag ) | | | +| for( i = 1; i <= num_views_minus1; i++ ) { | | | +| for( j = 0; j < num_non_anchor_refs_10[ i ]; j++ ) | | | +| non_anchor_ref_10_flag[ i ][ j ] | 5 | u(1) | +| for( j = 0; j < num_non_anchor_refs_11[ i ]; j++ ) | | | +| non_anchor_ref_11_flag[ i ][ j ] | 5 | u(1) | +| } | | | +| } | | | +| } | | | + +#### G.13.1.8 Operation point not present SEI message syntax + +| operation_point_not_present( payloadSize ) { | C | Descriptor | +|----------------------------------------------|---|------------| +| num_operation_points | 5 | ue(v) | +| for( k = 0; k < num_operation_points; k++ ) | | | +| operation_point_not_present_id[ k ] | 5 | ue(v) | +| } | | | +| } | | | + +#### G.13.1.9 Base view temporal HRD SEI message syntax + +| base_view_temporal_hrd( payloadSize ) { | C | Descriptor | +|----------------------------------------------------------------------|---|------------| +| num_of_temporal_layers_in_base_view_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_of_temporal_layers_in_base_view_minus1; i++ ) { | | | +| sei_mvc_temporal_id[ i ] | 5 | u(3) | +| sei_mvc_timing_info_present_flag[ i ] | 5 | u(1) | +| if( sei_mvc_timing_info_present_flag[ i ] ) { | | | +| sei_mvc_num_units_in_tick[ i ] | 5 | u(32) | +| sei_mvc_time_scale[ i ] | 5 | u(32) | +| sei_mvc_fixed_frame_rate_flag[ i ] | 5 | u(1) | +| } | | | +| sei_mvc_nal_hrd_parameters_present_flag[ i ] | 5 | u(1) | +| if( sei_mvc_nal_hrd_parameters_present_flag[ i ] ) | | | +| hrd_parameters( ) | 5 | | +| sei_mvc_vcl_hrd_parameters_present_flag[ i ] | 5 | u(1) | + +| | | | +|-------------------------------------------------------------------------------------------------------|---|------| +| if( sei_mvc_vcl_hrd_parameters_present_flag[ i ] ) | | | +| hrd_parameters( ) | 5 | | +| if( sei_mvc_nal_hrd_parameters_present_flag[ i ]
sei_mvc_vcl_hrd_parameters_present_flag[ i ] ) | | | +| sei_mvc_low_delay_hrd_flag[ i ] | 5 | u(1) | +| sei_mvc_pic_struct_present_flag[ i ] | 5 | u(1) | +| } | | | +| } | | | + +#### G.13.1.10 Multiview view position SEI message syntax + +| multiview_view_position( payloadSize ) { | C | Descriptor | +|-----------------------------------------------|---|------------| +| num_views_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_views_minus1; i++ ) | | | +| view_position[ i ] | 5 | ue(v) | +| multiview_view_position_extension_flag | 5 | u(1) | +| } | | | + +#### G.13.2 SEI message semantics + +Depending on payloadType, the corresponding SEI message semantics are extended as follows: + +- If payloadType is equal to 2, 3, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212, the following applies: + - If the SEI message is not included in an MVC scalable nesting SEI message, it applies to the view component of the current access unit with VOIdx equal to VOIdxMin. + - Otherwise (the SEI message is included in an MVC scalable nesting SEI message), it applies to all view components of the current access unit when all\_view\_components\_in\_au\_flag is equal to 1, or it applies to all view components of the current access unit with view\_id equal to sei\_view\_id[ i ] for any i in the range of 0 to num\_view\_components\_minus1, inclusive, when all\_view\_components\_in\_au\_flag is equal to 0. When payloadType is equal to 10 for the SEI message that is included in an MVC scalable nesting SEI message, the semantics for sub\_seq\_layer\_num of the sub-sequence information SEI message is modified as follows: + +**sub\_seq\_layer\_num** specifies the sub-sequence layer number of the current picture. When the current picture resides in a sub-sequence for which the first picture in decoding order is an IDR picture, the value of sub\_seq\_layer\_num shall be equal to 0. For a non-paired reference field, the value of sub\_seq\_layer\_num shall be equal to 0. sub\_seq\_layer\_num shall be in the range of 0 to 255, inclusive. +- Otherwise, if payloadType is equal to 0 or 1, the following applies: + - If the SEI message is not included in an MVC scalable nesting SEI message, the following applies. When the SEI message and all other SEI messages with payloadType equal to 0 or 1 not included in an MVC scalable nesting SEI message are used as the buffering period and picture timing SEI messages for checking the bitstream conformance according to Annex C and the decoding process specified in clauses 2 to 9 is used, the bitstream shall be conforming to this Recommendation | International Standard. + - Otherwise (the SEI message is included in an MVC scalable nesting SEI message), the following applies. When the SEI message and all other SEI messages with payloadType equal to 0 or 1 included in an MVC scalable nesting SEI message with identical values of sei\_op\_temporal\_id and sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, are used as the buffering period and picture timing SEI messages for checking the bitstream conformance according to Annex C, the bitstream that would be obtained by invoking the bitstream extraction process as specified in clause G.8.3 with tldTarget equal to sei\_op\_temporal\_id and viewIdTargetList equal to sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, shall be conforming to this Recommendation | International Standard. + +In the semantics of clauses D.2.1 and D.2.3, the syntax elements num\_units\_in\_tick, time\_scale, fixed\_frame\_rate\_flag, nal\_hrd\_parameters\_present\_flag, vcl\_hrd\_parameters\_present\_flag, + +low\_delay\_hrd\_flag, and pic\_struct\_present\_flag and the derived variables NalHrdBpPresentFlag, VclHrdBpPresentFlag, and CpbDpbDelaysPresentFlag are substituted with the syntax elements `vui_mvc_num_units_in_tick[ i ]`, `vui_mvc_time_scale[ i ]`, `vui_mvc_fixed_frame_rate_flag[ i ]`, `vui_mvc_nal_hrd_parameters_present_flag[ i ]`, `vui_mvc_vcl_hrd_parameters_present_flag[ i ]`, `vui_mvc_low_delay_hrd_flag[ i ]`, and `vui_mvc_pic_struct_present_flag[ i ]` and the derived variables `VuiMvcNalHrdBpPresentFlag[ i ]`, `VuiMvcVclHrdBpPresentFlag[ i ]`, and `VuiMvcCpbDpbDelaysPresentFlag[ i ]`. + +The values of `seq_parameter_set_id`'s in all buffering period SEI messages included in MVC scalable nesting SEI messages and associated with operation points for which the greatest `VOIdx` values in the associated sub-bitstreams are identical shall be identical. + +- Otherwise (all remaining `payloadType` values), the corresponding SEI message semantics are not extended. + +When an SEI message having a particular value of `payloadType` equal to 137 or 144, contained in an MVC scalable nesting SEI message, and applying to a particular combination of a list of `view_id` and a `temporal_id` is present in an access unit, the SEI message with the particular value of `payloadType` applying to the particular combination of a list of `view_id` and a `temporal_id` shall be present an MVC scalable nesting SEI message in the IDR access unit that is the first access unit of the coded video sequence. + +All SEI messages having a particular value of `payloadType` equal to 137 or 144, contained in MVC scalable nesting SEI messages, and applying to a particular combination of a list of `view_id` and a `temporal_id` present in a coded video sequence shall have the same content. + +For the semantics of SEI messages with `payloadType` in the range of 0 to 23, inclusive, or equal to 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212, which are specified in clause D.2, MVC sequence parameter set is substituted for sequence parameter set; the parameters of MVC sequence parameter set RBSP and picture parameter set RBSP that are in effect are specified in clauses G.7.4.2.1 and G.7.4.2.2, respectively. + +Coded video sequences conforming to one or more of the profiles specified in this annex shall not include SEI NAL units that contain SEI messages with `payloadType` in the range of 24 to 35, inclusive, which are specified in clause F.13. + +When an SEI NAL unit contains an SEI message with `payloadType` in the range of 36 to 44, inclusive, or equal to 46, which are specified in clause G.13, it shall not contain any SEI messages with `payloadType` less than 36 or equal to 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212, and the first SEI message in the SEI NAL unit shall have `payloadType` in the range of 36 to 44, inclusive, or equal to 46. + +When an MVC scalable nesting SEI message (`payloadType` equal to 37) or a view scalability information SEI message (`payloadType` equal to 38) or an operation point not present SEI message (`payloadType` equal to 43) is present in an SEI NAL unit, it shall be the only SEI message in the SEI NAL unit. + +### G.13.2.1 Parallel decoding information SEI message semantics + +The parallel decoding information SEI message may be associated with any access unit. The information signalled in the SEI message applies to all the access units from the access unit the SEI message is associated with to the next access unit, in decoding order, containing an SEI message of the same type, exclusively, or to the end of the coded video sequence, whichever is earlier in decoding order. + +Some view components for which the parallel decoding information is signalled in a parallel decoding information SEI message may not be present in the coded video sequence. + +**seq\_parameter\_set\_id** specifies a subset sequence parameter set that contains the inter-view dependency relationship information. The value of `seq_parameter_set_id` shall be equal to the value of `seq_parameter_set_id` in the picture parameter set referenced by a view component of the primary coded picture of the access unit containing the parallel decoding information SEI message. The value of `seq_parameter_set_id` shall be in the range of 0 to 31, inclusive. + +NOTE 1 – The inter-view dependency relationship is signalled in the sequence parameter set MVC extension, which is identical for all subset sequence parameter sets that may be activated during the decoding process for the coded video sequence. + +**pdi\_init\_delay\_anchor\_minus2\_l0[ i ][ j ]** specifies the unavailable reference area in the view component with `view_id` equal to `anchor_ref_l0[ i ][ j ]` that shall not be used for inter-view reference by the coded anchor view component with `view_id` equal to `view_id[ i ]`, where `anchor_ref_l0[ i ][ j ]` and `view_id[ i ]` are both from the MVC sequence parameter set that has a sequence parameter set identifier equal to the syntax element `seq_parameter_set_id` contained in the current SEI message. The unavailable reference area is a rectangular area with coordinates $( 0, (\text{CurrMbAddr} / \text{PicWidthInMbs} + \text{pdi\_init\_delay\_anchor\_minus2\_l0}[ i ][ j ] + 2) * 16 )$ as the top left corner and $( \text{PicWidthInSamples}, \text{PicHeightInSamples} )$ as the bottom right corner. When decoding the coded view component with `view_id` equal to `view_id[ i ]`, samples from the unavailable reference area from the view component with `view_id` equal to `anchor_ref_l0[ i ][ j ]` shall not be referred to by the inter-view prediction process. The value of `pdi_init_delay_anchor_minus2_l0[ i ][ j ]` shall be in the range of 0 to `PicHeightInMbs - 2`, inclusive. + +**pdi\_init\_delay\_anchor\_minus2\_11[ i ][ j ]** specifies the unavailable reference area in the view component with view\_id equal to anchor\_ref\_11[ i ][ j ] that shall not be used for inter-view reference by the coded anchor view component with view\_id equal to view\_id[ i ], where anchor\_ref\_11[ i ][ j ] and view\_id[ i ] are both from the MVC sequence parameter set that has a sequence parameter set identifier equal to the syntax element seq\_parameter\_set\_id contained in the current SEI message. The unavailable reference area is a rectangular area with coordinates ( 0, ( CurrMbAddr / PicWidthInMbs + pdi\_init\_delay\_anchor\_minus2\_11[ i ][ j ] + 2 ) \* 16 ) as the top left corner and ( PicWidthInSamples, PicHeightInSamples ) as the bottom right corner. When decoding the coded view component with view\_id equal to view\_id[ i ], samples from the unavailable reference area from the view component with view\_id equal to anchor\_ref\_11[ i ][ j ] shall not be referred to by the inter-view prediction process. The value of pdi\_init\_delay\_anchor\_minus2\_11[ i ][ j ] shall be in the range of 0 to PicHeightInMbs – 2, inclusive. + +**pdi\_init\_delay\_non\_anchor\_minus2\_10[ i ][ j ]** specifies the unavailable reference area in the view component with view\_id equal to non\_anchor\_ref\_10[ i ][ j ] that shall not be used for inter-view reference by the coded non-anchor view component with view\_id equal to view\_id[ i ], where non\_anchor\_ref\_10[ i ][ j ] and view\_id[ i ] are both from the MVC sequence parameter set that has a sequence parameter set identifier equal to the syntax element seq\_parameter\_set\_id contained in the current SEI message. The unavailable reference area is a rectangular area with coordinates ( 0, ( CurrMbAddr / PicWidthInMbs + pdi\_init\_delay\_non\_anchor\_minus2\_10[ i ][ j ] + 2 ) \* 16 ) as the top left corner and ( PicWidthInSamples, PicHeightInSamples ) as the bottom right corner. When decoding the coded view component with view\_id equal to view\_id[ i ], samples from the unavailable reference area from the view component with view\_id equal to non\_anchor\_ref\_10[ i ][ j ] shall not be referred to by the inter-view prediction process. The value of pdi\_init\_delay\_non\_anchor\_minus2\_10[ i ][ j ] shall be in the range of 0 to PicHeightInMbs – 2, inclusive. + +**pdi\_init\_delay\_non\_anchor\_minus2\_11[ i ][ j ]** specifies the unavailable reference area in the view component with view\_id equal to non\_anchor\_ref\_11[ i ][ j ] that shall not be used for inter-view reference by the coded anchor view component with view\_id equal to view\_id[ i ], where non\_anchor\_ref\_11[ i ][ j ] and view\_id[ i ] are both from the MVC sequence parameter set that has a sequence parameter set identifier equal to the syntax element seq\_parameter\_set\_id contained in the current SEI message. The unavailable reference area is a rectangular area with coordinates ( 0, ( CurrMbAddr / PicWidthInMbs + pdi\_init\_delay\_non\_anchor\_minus2\_11[ i ][ j ] + 2 ) \* 16 ) as the top left corner and ( PicWidthInSamples, PicHeightInSamples ) as the bottom right corner. When decoding the coded view component with view\_id equal to view\_id[ i ], samples from the unavailable reference area from the view component with view\_id equal to non\_anchor\_ref\_11[ i ][ j ] shall not be referred to by the inter-view prediction process. The value of pdi\_init\_delay\_non\_anchor\_minus2\_11[ i ][ j ] shall be in the range of 0 to PicHeightInMbs – 2, inclusive. + +#### G.13.2.2 MVC scalable nesting SEI message semantics + +An MVC nesting SEI message shall contain one and only one SEI message of payloadType less than or equal to 23, which is referred to as the nested SEI message. The scope to which the nested SEI message applies is indicated by the syntax elements operation\_point\_flag, all\_view\_components\_in\_au\_flag, num\_view\_components\_minus1, sei\_view\_id[ i ] for all i, num\_view\_components\_op\_minus1, sei\_op\_view\_id[ i ] for all i, and sei\_op\_temporal\_id. + +Some view components to which the nested SEI message applies may not be present in the access unit containing the MVC scalable nesting SEI message. + +**operation\_point\_flag** equal to 1 specifies that the nested SEI message applies to the current access unit when the associated operation point identified by sei\_op\_temporal\_id and sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, is decoded. operation\_point\_flag equal to 0 specifies that the nested SEI message applies to the view components identified by all\_view\_components\_in\_au\_flag, num\_view\_components\_minus1, and sei\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_minus1, inclusive, regardless of which operation point is decoded. + +If the nested SEI message has payloadType equal to 0 or 1, operation\_point\_flag shall be equal to 1. Otherwise (the nested SEI message has payloadType not equal to 0 or 1), operation\_point\_flag shall be equal to 0. + +**all\_view\_components\_in\_au\_flag** equal to 1 specifies that the nested SEI message applies to all view components of the access unit. all\_view\_components\_in\_au\_flag equal to 0 specifies that the applicable scope of the nested SEI message is signalled by the syntax elements num\_view\_components\_minus1 and sei\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_minus1, inclusive. + +**num\_view\_components\_minus1** plus 1 specifies the number of view components to which the nested SEI message applies when operation\_point\_flag is equal to 0 and all\_view\_components\_in\_au\_flag is equal to 0. The value of num\_view\_components\_minus1 shall be in the range of 0 to 1023, inclusive. + +**sei\_view\_id[ i ]** specifies the view\_id of the i-th view component to which the nested SEI message applies when operation\_point\_flag is equal to 0 and all\_view\_components\_in\_au\_flag is equal to 0. + +**num\_view\_components\_op\_minus1** plus 1 specifies the number of view components of the operation point to which the nested SEI message applies when operation\_point\_flag is equal to 1. The value of num\_view\_components\_op\_minus1 + +shall be in the range of 0 to 1023, inclusive. + +**sei\_op\_view\_id[ i ]** specifies the view\_id of the i-th view component to which the nested SEI message applies when operation\_point\_flag is equal to 1. + +**sei\_op\_temporal\_id** specifies the maximum temporal\_id of the sub-bitstream to which the nested SEI message applies when operation\_point\_flag is equal to 1. + +**sei\_nesting\_zero\_bit** is equal to 0. + +### G.13.2.3 View scalability information SEI message semantics + +When present, this SEI message shall be associated with an IDR access unit. The semantics of the message are valid for the current coded video sequence. A view scalability information SEI message contains view and scalability information for a subset of the operation points in the coded video sequence. Each operation point is associated with an operation point identifier. The sub-bitstream for an operation point is referred to as the operation point representation or the representation of the operation point. Information such as bit rate and frame rate, among others, are signalled for the representations of the subset of the operation points. + +NOTE 1 – Any operation point for which view and scalability information is signalled in a view scalability information SEI message (i.e. identified by a value of operation\_point\_id[ i ]) must be present in the coded video sequence. When an application keeps a view scalability information SEI message in a sub-bitstream extracted according to the process specified in clause G.8.5.3, and after the extraction any operation point for which view and scalability information is signalled in the original SEI message becomes not present in the coded video sequence, the application must change the content of the view scalability information SEI message to fulfil the condition stated by the first sentence in this note. + +**num\_operation\_points\_minus1** plus 1 specifies the number of operation points that are present in the coded video sequence and for which the view scalability information is signalled by the following syntax elements. The value of num\_operation\_points\_minus1 shall be in the range of 0 to 1023, inclusive. + +The sub-bitstream corresponding to an operation point is defined as the operation point representation or the representation of the operation point. The representation of the operation point identified by operation\_point\_id[ i ] is the output of the sub-bitstream extraction process specified in clause G.8.5.3 with tldTarget equal to temporal\_id[ i ] and viewIdTargetList consisting of view\_id[ i ][ j ] for all j in the range of 0 to num\_target\_output\_views\_minus1[ i ], inclusive, as the inputs. + +**operation\_point\_id[ i ]** specifies the identifier of the operation point. Each operation point is associated with a unique operation point identifier. The value of operation\_point\_id[ i ] shall be in the range of 0 to 65535, inclusive. + +In the following semantics in this clause, the operation point with identifier equal to operation\_point\_id[ i ] is referred to as the current operation point. + +**priority\_id[ i ]** and **temporal\_id[ i ]** specify the maximum value of priority\_id and temporal\_id, respectively, of the NAL units in the representation of the current operation point. + +**num\_target\_output\_views\_minus1[ i ]** plus 1 specifies the number of target output views for the current operation point. The value of num\_target\_output\_views\_minus1[ i ] shall be in the range of 0 to 1023, inclusive. + +**view\_id[ i ][ j ]** specifies the identifier of the j-th target output view for the current operation point. The value of view\_id[ i ][ j ] shall be in the range of 0 to 1023, inclusive. + +**profile\_level\_info\_present\_flag[ i ]** equal to 1 specifies that the profile and level information for the representation of the current operation point is present in the SEI message. profile\_level\_info\_present\_flag[ i ] equal to 0 specifies that the profile and level information for the current operation point is not present in the SEI message. + +**bitrate\_info\_present\_flag[ i ]** equal to 1 specifies that the bitrate information for the current operation point is present in the SEI message. bitrate\_info\_present\_flag[ i ] equal to 0 specifies that the bitrate information for the current operation point is not present in the SEI message. + +**frm\_rate\_info\_present\_flag[ i ]** equal to 1 specifies that the frame rate information for the current operation point is present in the SEI message. frm\_rate\_info\_present\_flag[ i ] equal to 0 specifies that the frame rate information for the current operation point is not present in the SEI message. + +**view\_dependency\_info\_present\_flag[ i ]** equal to 1 specifies that information on the views the target output view of the current operation point directly depends on is present in the SEI message. View A is directly dependent on view point B if there is at least one view component of view A using a view component of view B for inter-view prediction reference. view\_dependency\_info\_present\_flag[ i ] equal to 0 specifies that view\_dependency\_info\_src\_op\_id[ i ] is present in the SEI message. When not present, view\_dependency\_info\_present\_flag[ i ] shall be inferred to be equal to 0. + +NOTE 2 – The inter-view dependency relationship signalled in sequence parameter set MVC extension is an upper bound, in the sense that whenever view A may depend on view B at any access unit, it is specified as view A depends on view B. Therefore, the dependency relationship is indicated by sequence parameter set MVC extension when view A depends on view B at only one of all access units in the coded video sequence, or even when view A actually does not depend on view B at any access unit but when generating the sequence parameter set MVC extension the encoder thought view A might depend on view B. The dependency relationship signalled here can be more refined. For example, when view A depends on view B at access units with temporal\_id equal to 0 but not at other access units, this can be indicated through the view dependency information signalled in this SEI message for operation points with view A as the target output view and with different maximum values of temporal\_id. + +**parameter\_sets\_info\_present\_flag[ i ]** equal to 1 specifies that the values of seq\_parameter\_set\_id of the sequence parameter sets and subset sequence parameter sets and the values of pic\_parameter\_set\_id of the picture parameter sets that are referred to by the VCL NAL units of the representation of the current operation point are present in the SEI message. parameter\_sets\_info\_present\_flag[ i ] equal to 0 specifies that parameter\_sets\_info\_src\_op\_id[ i ] is present in the SEI message. + +**bitstream\_restriction\_info\_present\_flag[ i ]** equal to 1 specifies that the bitstream restriction information for the representation of the current operation point is present in the SEI message. bitstream\_restriction\_info\_present\_flag[ i ] equal to 0 specifies that the bitstream restriction information for the representation of the current operation point is not present in the SEI message. + +**op\_profile\_level\_idc[ i ]** specifies the profile and level compliance of the representation of the current operation point. op\_profile\_level\_idc[ i ] is the exact copy of the three bytes comprised of profile\_idc, constraint\_set0\_flag, constraint\_set1\_flag, constraint\_set2\_flag, constraint\_set3\_flag, constraint\_set4\_flag, constraint\_set5\_flag, reserved\_zero\_2bits, and level\_idc, if these syntax elements were used to specify the profile and level compliance of the representation of the current operation point as specified in Annexes A and G. + +**avg\_bitrate[ i ]** specifies the average bit rate of the representation of the current operation point. The average bit rate for the representation of the current operation point in bits per second is given by BitRateBPS( avg\_bitrate[ i ] ) with the function BitRateBPS( ) being specified by the following equation. + +$$\text{BitRateBPS}(x) = (x \& (2^{14} - 1)) * 10^{(2 + (x \gg 14))} \quad (\text{G-82})$$ + +All NAL units of the representation of the current operation point are taken into account in the calculation. The average bit rate is derived according to the access unit removal time specified in Annex C. In the following, bTotal is the number of bits in all NAL units of the representation of the current operation point in the current coded video sequence. $t_1$ is the removal time (in seconds) of the current access unit, and $t_2$ is the removal time (in seconds) of the last access unit (in decoding order) of the current coded video sequence. + +With x specifying the value of avg\_bitrate[ i ], the following applies: + +- If $t_1$ is not equal to $t_2$ , the following condition shall be true. + +$$(x \& (2^{14} - 1)) == \text{Round}(b\text{Total} \div ((t_2 - t_1) * 10^{(2 + (x \gg 14))})) \quad (\text{G-83})$$ + +- Otherwise ( $t_1$ is equal to $t_2$ ), the following condition shall be true. + +$$(x \& (2^{14} - 1)) == 0 \quad (\text{G-84})$$ + +**max\_bitrate[ i ]** specifies the maximum bit rate of the representation of the current operation point, given by BitRateBPS( max\_bitrate\_layer\_representation[ i ] ), in bits per second, with the function BitRateBPS( ) being specified in Equation G-82. The maximum bit rate of the representation of the current operation point is calculated based on a time window specified by max\_bitrate\_calc\_window[ i ]. + +**max\_bitrate\_calc\_window[ i ]** specifies the length of the time window, in units of 1/100 second, based on which max\_bitrate[ i ] is calculated. + +**constant\_frm\_rate\_idc[ i ]** specifies whether the frame rate of the representation of the current operation point is constant. If the value of avg\_frm\_rate as specified below is constant whichever a temporal section of the operation point representation is used for the calculation, the frame rate is constant, otherwise the frame rate is non-constant. constant\_frm\_rate\_idc[ i ] equal to 0 specifies that the frame rate is not constant, constant\_frm\_rate\_idc[ i ] equal to 1 specifies that the frame rate is constant, and constant\_frm\_rate\_idc[ i ] equal to 2 specifies that the frame rate may be or may not be constant. The value of constant\_frm\_rate\_idc[ i ] shall be in the range of 0 to 2, inclusive. + +**avg\_frm\_rate[ i ]** specifies the average frame rate, in units of frames per 256 seconds, of the representation of the current operation point. The semantics of avg\_frm\_rate[ i ] is identical to the semantics of average\_frame\_rate in sub-sequence layer characteristics SEI message when accurate\_statistics\_flag is equal to 1, except that herein the set of NAL units in the range of sub-sequence layers is replaced by the set of NAL units of the representation of the current operation point. + +**num\_directly\_dependent\_views[ i ]** specifies the number of views that the target output view of the current operation point is directly dependent on within the representation of the current operation point. The value of **num\_directly\_dependent\_views[ i ]** shall be in the range of 0 to 16, inclusive. + +**directly\_dependent\_view\_id[ i ][ j ]** specifies the **view\_id** of the j-th view that the target output view of the current operation point is directly dependent on within the representation of the current operation point. The value of **directly\_dependent\_view\_id[ i ][ j ]** shall be in the range of 0 to 1023, inclusive. + +**view\_dependency\_info\_src\_op\_id[ i ]** specifies that the views the target output view of the current operation point directly depends on within the representation of the current operation point are the same as the views the target output view of the operation point with identifier equal to **view\_dependency\_info\_src\_op\_id[ i ]** directly depends on within the representation of the operation point with identifier equal to **view\_dependency\_info\_src\_op\_id[ i ]**, if **view\_dependency\_info\_src\_op\_id[ i ]** is not equal to **operation\_point\_id[ i ]**. Otherwise (**view\_dependency\_info\_src\_op\_id[ i ]** is equal to **operation\_point\_id[ i ]**), information on the views the target output view of the current operation point directly depends on is not present in the SEI message. The value of **view\_dependency\_info\_src\_op\_id[ i ]** shall be in the range of 0 to 65535, inclusive. + +**num\_seq\_parameter\_sets[ i ]** specifies the number of different sequence parameter sets that are referred to by the VCL NAL units of the representation of the current operation point. The value of **num\_seq\_parameter\_sets[ i ]** shall be in the range of 0 to 32, inclusive. + +**seq\_parameter\_set\_id\_delta[ i ][ j ]** specifies the smallest value of the **seq\_parameter\_set\_id** of all sequence parameter sets required for decoding the representation of the current operation point, if j is equal to 0. Otherwise (j is greater than 0), **seq\_parameter\_set\_id\_delta[ i ][ j ]** specifies the difference between the value of the **seq\_parameter\_set\_id** of the j-th required sequence parameter set and the value of the **seq\_parameter\_set\_id** of the (j-1)-th required sequence parameter set for decoding the representation of the current operation point. The sequence parameter sets are logically ordered in ascending order of the value of **seq\_parameter\_set\_id**. The value of **seq\_parameter\_set\_id\_delta[ i ][ j ]** shall be in the range of 0 to 31, inclusive. + +**num\_subset\_seq\_parameter\_sets[ i ]** specifies the number of different subset sequence parameter sets that are referred to by the VCL NAL units of the representation of the current operation point. The value of **num\_subset\_seq\_parameter\_sets[ i ]** shall be in the range of 0 to 32, inclusive. + +**subset\_seq\_parameter\_set\_id\_delta[ i ][ j ]** specifies the smallest value of the **seq\_parameter\_set\_id** of all subset sequence parameter sets required for decoding the representation of the current operation point, if j is equal to 0. Otherwise (j is greater than 0), **subset\_seq\_parameter\_set\_id\_delta[ i ][ j ]** specifies the difference between the value of the **seq\_parameter\_set\_id** of the j-th required subset sequence parameter set and the value of the **seq\_parameter\_set\_id** of the (j-1)-th required subset sequence parameter set for decoding the representation of the current operation point. The subset sequence parameter sets are logically ordered in ascending order of the value of **seq\_parameter\_set\_id**. The value of **subset\_seq\_parameter\_set\_id\_delta[ i ][ j ]** shall be in the range of 0 to 31, inclusive. + +**num\_pic\_parameter\_sets\_minus1[ i ]** plus 1 specifies the number of different picture parameter sets that are referred to by the VCL NAL units of the representation of the current operation point. The value of **num\_pic\_parameter\_sets\_minus1[ i ]** shall be in the range of 0 to 255, inclusive. + +**pic\_parameter\_set\_id\_delta[ i ][ j ]** specifies the smallest value of the **pic\_parameter\_set\_id** of all picture parameter sets required for decoding the representation of the current operation point, if j is equal to 0. Otherwise (j is greater than 0), **pic\_parameter\_set\_id\_delta[ i ][ j ]** specifies the difference between the value of the **pic\_parameter\_set\_id** of the j-th required picture parameter set and the value of the **pic\_parameter\_set\_id** of the (j-1)-th required picture parameter set for decoding the representation of the current operation point. The picture parameter sets are logically ordered in ascending order of the value of **pic\_parameter\_set\_id**. The value of **pic\_parameter\_set\_id\_delta[ i ][ j ]** shall be in the range of 0 to 255, inclusive. + +**parameter\_sets\_info\_src\_op\_id[ i ]** specifies that the values of **seq\_parameter\_set\_id** of the sequence parameter sets and subset sequence parameter sets and the values of **pic\_parameter\_set\_id** of the picture parameter sets that are referred to by the VCL NAL units of the representation of the current operation point are the same as those for the representation of the operation point with identifier equal to **parameter\_sets\_info\_src\_op\_id[ i ]**, if **parameter\_sets\_info\_src\_op\_id[ i ]** is not equal to **operation\_point\_id[ i ]**. Otherwise (**parameter\_sets\_info\_src\_op\_id[ i ]** is equal to **operation\_point\_id[ i ]**), **parameter\_sets\_info\_src\_op\_id[ i ]** specifies that the values of **seq\_parameter\_set\_id** of the sequence parameter sets and subset sequence parameter sets and the values of **pic\_parameter\_set\_id** of the picture parameter sets that are referred to by the VCL NAL units of the representation of the current operation point are not present in the SEI message. The value of **parameter\_sets\_info\_src\_op\_id[ i ]** shall be in the range of 0 to 65535, inclusive. + +**motion\_vectors\_over\_pic\_boundaries\_flag[ i ]** specifies the value of **motion\_vectors\_over\_pic\_boundaries\_flag**, as specified in clause E.2.1, for the current operation point representation. When the **motion\_vectors\_over\_pic\_boundaries\_flag[ i ]** syntax element is not present, **motion\_vectors\_over\_pic\_boundaries\_flag** value for the current operation point representation shall be inferred to be equal to 1. + +**max\_bytes\_per\_pic\_denom[ i ]** specifies the max\_bytes\_per\_pic\_denom value, as specified in clause E.2.1, for the current operation point representation. When the max\_bytes\_per\_pic\_denom[ i ] syntax element is not present, the value of max\_bytes\_per\_pic\_denom for the current operation point representation shall be inferred to be equal to 2. The value of max\_bytes\_per\_pic\_denom[ i ] shall be in the range of 0 to 16, inclusive. + +**max\_bits\_per\_mb\_denom[ i ]** specifies the max\_bits\_per\_mb\_denom value, as specified in clause E.2.1, for the current operation point representation. When the max\_bits\_per\_mb\_denom[ i ] is not present, the value of max\_bits\_per\_mb\_denom for the current operation point representation shall be inferred to be equal to 1. The value of max\_bits\_per\_mb\_denom[ i ] shall be in the range of 0 to 16, inclusive. + +**log2\_max\_mv\_length\_horizontal[ i ]** and **log2\_max\_mv\_length\_vertical[ i ]** specify the values of log2\_max\_mv\_length\_horizontal and log2\_max\_mv\_length\_vertical, as specified in clause E.2.1, for the current operation point representation. When log2\_max\_mv\_length\_horizontal[ i ] is not present, the values of log2\_max\_mv\_length\_horizontal and log2\_max\_mv\_length\_vertical for the current operation point representation shall be inferred to be equal to 16. The value of log2\_max\_mv\_length\_horizontal[ i ] shall be in the range of 0 to 16, inclusive. The value of log2\_max\_mv\_length\_vertical[ i ] shall be in the range of 0 to 16, inclusive. + +NOTE 3 – The value range of a decoded vertical or horizontal motion vector component is also constrained by profile and level limits as specified in Annex A or clause G.10.2. + +**max\_num\_reorder\_frames[ i ]** specifies the value of max\_num\_reorder\_frames, as specified in clause E.2.1, for the current operation point representation. The value of max\_num\_reorder\_frames[ i ] shall be in the range of 0 to 16, inclusive. When the max\_num\_reorder\_frames[ i ] syntax element is not present, the value of max\_num\_reorder\_frames for the current operation point representation shall be inferred to be equal to 16. + +**max\_dec\_frame\_buffering[ i ]** specifies the value of max\_dec\_frame\_buffering, as specified in clause E.2.1, for the current operation point representation. The value of max\_dec\_frame\_buffering[ i ] shall be in the range of 0 to MaxDpbFrames (as specified in clauses A.3.1, A.3.2, or G.10.2), inclusive. When the max\_dec\_frame\_buffering[ i ] syntax element is not present, the value of max\_dec\_frame\_buffering for the current operation point representation shall be inferred to be equal to MaxDpbFrames. + +#### G.13.2.4 Multiview scene information SEI message semantics + +The multiview scene information SEI message indicates the maximum disparity among multiple view components in an access unit. The maximum disparity could be used for processing the decoded view components prior to rendering on a 3D display. When present, the multiview scene information SEI message shall be associated with an IDR access unit. The information signalled in the SEI message applies to the coded video sequence. + +The actual maximum disparity value may be less than the one signalled in the multiview scene information SEI message, due to that some views in the coded video sequence may have been removed from the original bitstream to produce an extracted sub-bitstream according to the process specified in clause G.8.5.3. + +**max\_disparity** specifies the maximum disparity, in units of luma samples, between spatially adjacent view components among the total set of view components in an access unit. The value of max\_disparity shall be in the range of 0 to 1023, inclusive. + +NOTE – The maximum disparity depends on the baseline distance between spatially adjacent views and the spatial resolution of each view. Therefore, if either the number of views or spatial resolution is changed, the maximum disparity should also be changed accordingly. + +#### G.13.2.5 Multiview acquisition information SEI message semantics + +The multiview acquisition information SEI message specifies various parameters of the acquisition environment. Specifically, intrinsic and extrinsic camera parameters are specified. These parameters could be used for processing the decoded view components prior to rendering on a 3D display. When present as a non-nested SEI message, the multiview acquisition information SEI message shall be associated with an IDR access unit. The information signalled in the multiview acquisition information SEI message applies to the coded video sequence. + +The multiview acquisition information SEI message may be nested in an MVCD scalable nesting SEI message to indicate parameters of the acquisition environment of texture and depth views. When present as a nested SEI message, the multiview acquisition information SEI message is recommended to be associated with an IDR access unit and may be associated with any access unit. When present as a nested SEI message, the information indicated in the SEI message applies from the access unit associated with the SEI message to the next access unit, in decoding order, containing an SEI message of the same type, exclusive, or to the end of the coded video sequence, whichever is earlier in decoding order. + +Some of the views for which the multiview acquisition information is included in a multiview acquisition information SEI message may not be present in the coded video sequence. + +The extrinsic camera parameters are specified according to a right-handed coordinate system, where the upper left corner + +of the image is the origin, i.e., the (0, 0) coordinate, with the other corners of the image having non-negative coordinates. With these specifications, a 3-dimensional world point, $wP=[x\ y\ z]$ is mapped to a 2-dimensional camera point, $cP[i] = [u\ v\ 1]$ , for the i-th camera according to: + +$$s * cP[i] = A[i] * R^{-1}[i] * (wP - T[i]) \quad (G-85)$$ + +where $A[i]$ denotes the intrinsic camera parameter matrix, $R^{-1}[i]$ denotes the inverse of the rotation matrix $R[i]$ , $T[i]$ denotes the translation vector, and $s$ (a scalar value) is an arbitrary scale factor chosen to make the third coordinate of $cP[i]$ equal to 1. The elements of $A[i]$ , $R[i]$ , $T[i]$ are determined according to the syntax elements signalled in this SEI message and as specified below. + +**num\_views\_minus1** shall be equal to the value of the syntax element `num_views_minus1` in the active MVC sequence parameter set for the coded video sequence when the SEI message is not nested. When the SEI message is nested in an MVCD scalable nesting SEI message, `num_views_minus1` shall be equal to the value of `num_view_components_minus1` of the containing MVCD scalable nesting SEI message. The value of `num_views_minus1` shall be in the range of 0 to 1023, inclusive. + +When the SEI message is not nested, the loop index $i$ in the subsequent syntax elements indicates the view order index derived from the active MVC sequence parameter set. When the SEI message is nested in an MVCD scalable nesting SEI message, the loop index $i$ in the subsequent syntax elements indicates the view with `view_id` equal to `sei_view_id[i]` of the containing MVCD scalable nesting SEI message. + +**intrinsic\_param\_flag** equal to 1 indicates the presence of intrinsic camera parameters. `intrinsic_param_flag` equal to 0 indicates the absence of intrinsic camera parameters. + +**extrinsic\_param\_flag** equal to 1 indicates the presence of extrinsic camera parameters. `extrinsic_param_flag` equal to 0 indicates the absence of extrinsic camera parameters. + +**intrinsic\_params\_equal\_flag** equal to 1 indicates that the intrinsic camera parameters are equal for all cameras and only one set of intrinsic camera parameters is present. `intrinsic_params_equal_flag` equal to 0 indicates that the intrinsic camera parameters are different for each camera and that a set of intrinsic camera parameters is present for each camera. + +**prec\_focal\_length** specifies the exponent of the maximum allowable truncation error for `focal_length_x[i]` and `focal_length_y[i]` as given by $2^{-\text{prec\_focal\_length}}$ . The value of `prec_focal_length` shall be in the range of 0 to 31, inclusive. + +**prec\_principal\_point** specifies the exponent of the maximum allowable truncation error for `principal_point_x[i]` and `principal_point_y[i]` as given by $2^{-\text{prec\_principal\_point}}$ . The value of `prec_principal_point` shall be in the range of 0 to 31, inclusive. + +**prec\_skew\_factor** specifies the exponent of the maximum allowable truncation error for skew factor as given by $2^{-\text{prec\_skew\_factor}}$ . The value of `prec_skew_factor` shall be in the range of 0 to 31, inclusive. + +**sign\_focal\_length\_x[i]** equal to 0 indicates that the sign of the focal length of the i-th camera in the horizontal direction is positive. `sign_focal_length_x[i]` equal to 1 indicates that the sign is negative. + +**exponent\_focal\_length\_x[i]** specifies the exponent part of the focal length of the i-th camera in the horizontal direction. The value of `exponent_focal_length_x[i]` shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified focal length. + +**mantissa\_focal\_length\_x[i]** specifies the mantissa part of the focal length of the i-th camera in the horizontal direction. The length of the `mantissa_focal_length_x[i]` syntax element in units of bits is variable and determined as follows: + +- If `exponent_focal_length_x[i] == 0`, the length is $\text{Max}(0, \text{prec\_focal\_length} - 30)$ . +- Otherwise ( $0 < \text{exponent\_focal\_length\_x[i]} < 63$ ), the length is $\text{Max}(0, \text{exponent\_focal\_length\_x[i]} + \text{prec\_focal\_length} - 31)$ . + +**sign\_focal\_length\_y[i]** equal to 0 indicates that the sign of the focal length of the i-th camera in the vertical direction is positive. `sign_focal_length_y[i]` equal to 1 indicates that the sign is negative. + +**exponent\_focal\_length\_y[i]** specifies the exponent part of the focal length of the i-th camera in the vertical direction. The value of `exponent_focal_length_y[i]` shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified focal length. + +**mantissa\_focal\_length\_y[i]** specifies the mantissa part of the focal length of the i-th camera in the vertical direction. The length of the `mantissa_focal_length_y[i]` syntax element in units of bits is variable and determined as follows: + +- If `exponent_focal_length_y[i] == 0`, the length is $\text{Max}(0, \text{prec\_focal\_length} - 30)$ . +- Otherwise ( $0 < \text{exponent\_focal\_length\_y[i]} < 63$ ), the length is $\text{Max}(0, \text{exponent\_focal\_length\_y[i]} + \text{prec\_focal\_length} - 31)$ . + +**sign\_principal\_point\_x[ i ]** equal to 0 indicates that the sign of the principal point of the i-th camera in the horizontal direction is positive. sign\_principal\_point\_x[ i ] equal to 1 indicates that the sign is negative. + +**exponent\_principal\_point\_x[ i ]** specifies the exponent part of the principal point of the i-th camera in the horizontal direction. The value of exponent\_principal\_point\_x[ i ] shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified principal point. + +**mantissa\_principal\_point\_x[ i ]** specifies the mantissa part of the principal point of the i-th camera in the horizontal direction. The length of the mantissa\_principal\_point\_x[ i ] syntax element in units of bits is variable and is determined as follows: + +- If exponent\_principal\_point\_x[ i ] == 0, the length is Max( 0, prec\_principal\_point – 30 ). +- Otherwise (0 < exponent\_principal\_point\_x[ i ] < 63), the length is Max( 0, exponent\_principal\_point\_x[ i ] + prec\_principal\_point – 31 ). + +**sign\_principal\_point\_y[ i ]** equal to 0 indicates that the sign of the principal point of the i-th camera in the vertical direction is positive. sign\_principal\_point\_y[ i ] equal to 1 indicates that the sign is negative. + +**exponent\_principal\_point\_y[ i ]** specifies the exponent part of the principal point of the i-th camera in the vertical direction. The value of exponent\_principal\_point\_y[ i ] shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified principal point. + +**mantissa\_principal\_point\_y[ i ]** specifies the mantissa part of the principal point of the i-th camera in the vertical direction. The length of the mantissa\_principal\_point\_y[ i ] syntax element in units of bits is variable and is determined as follows: + +- If exponent\_principal\_point\_y[ i ] == 0, the length is Max( 0, prec\_principal\_point – 30 ). +- Otherwise (0 < exponent\_principal\_point\_y[ i ] < 63), the length is Max( 0, exponent\_principal\_point\_y[ i ] + prec\_principal\_point – 31 ). + +**sign\_skew\_factor[ i ]** equal to 0 indicates that the sign of the skew factor of the i-th camera is positive. sign\_skew\_factor[ i ] equal to 1 indicates that the sign is negative. + +**exponent\_skew\_factor[ i ]** specifies the exponent part of the skew factor of the i-th camera. The value of exponent\_skew\_factor[ i ] shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified skew factor. + +**mantissa\_skew\_factor[ i ]** specifies the mantissa part of the skew factor of the i-th camera. The length of the mantissa\_skew\_factor[ i ] syntax element in units of bits is variable and determined as follows: + +- If exponent\_skew\_factor[ i ] == 0, the length is Max( 0, prec\_skew\_factor – 30 ). +- Otherwise (0 < exponent\_skew\_factor[ i ] < 63), the length is Max( 0, exponent\_skew\_factor[ i ] + prec\_skew\_factor – 31 ). + +The intrinsic matrix A[ i ] for i-th camera is represented by + +$$\begin{bmatrix} \text{focalLengthX}[i] & \text{skewFactor}[i] & \text{principalPointX}[i] \\ 0 & \text{focalLengthY}[i] & \text{principalPointY}[i] \\ 0 & 0 & 1 \end{bmatrix} \quad (\text{G-86})$$ + +**prec\_rotation\_param** specifies the exponent of the maximum allowable truncation error for $r[i][j][k]$ as given by $2^{-\text{prec\_rotation\_param}}$ . The value of prec\_rotation\_param shall be in the range of 0 to 31, inclusive. + +**prec\_translation\_param** specifies the exponent of the maximum allowable truncation error for $t[i][j]$ as given by $2^{-\text{prec\_translation\_param}}$ . The value of prec\_translation\_param shall be in the range of 0 to 31, inclusive. + +**sign\_r[ i ][ j ][ k ]** equal to 0 indicates that the sign of (j, k) component of the rotation matrix for the i-th camera is positive. sign\_r[ i ][ j ][ k ] equal to 1 indicates that the sign is negative. + +**exponent\_r[ i ][ j ][ k ]** specifies the exponent part of (j, k) component of the rotation matrix for the i-th camera. The value of exponent\_r[ i ][ j ][ k ] shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified rotation matrix. + +**mantissa\_r[ i ][ j ][ k ]** specifies the mantissa part of (j, k) component of the rotation matrix for the i-th camera. The length of the mantissa\_r[ i ][ j ][ k ] syntax element in units of bits is variable and determined as follows: + +- If exponent\_r[ i ] == 0, the length is Max( 0, prec\_rotation\_param – 30 ). + +- Otherwise ( $0 < \text{exponent\_r}[i] < 63$ ), the length is $\text{Max}(0, \text{exponent\_r}[i] + \text{prec\_rotation\_param} - 31)$ . + +The rotation matrix $R[i]$ for $i$ -th camera is represented as follows: + +$$\begin{bmatrix} rE[i][0][0] & rE[i][0][1] & rE[i][0][2] \\ rE[i][1][0] & rE[i][1][1] & rE[i][1][2] \\ rE[i][2][0] & rE[i][2][1] & rE[i][2][2] \end{bmatrix} \quad (G-87)$$ + +**sign\_t[i][j]** equal to 0 indicates that the sign of the $j$ -th component of the translation vector for the $i$ -th camera is positive. **sign\_t[i][j]** equal to 1 indicates that the sign is negative. + +**exponent\_t[i][j]** specifies the exponent part of the $j$ -th component of the translation vector for the $i$ -th camera. The value of **exponent\_t[i][j]** shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified translation vector. + +**mantissa\_t[i][j]** specifies the mantissa part of the $j$ -th component of the translation vector for the $i$ -th camera. The length $v$ of the **mantissa\_t[i][j]** syntax element in units of bits is variable and is determined as follows: + +- If **exponent\_t[i] == 0**, the length $v = \text{Max}(0, \text{prec\_translation\_param} - 30)$ . +- Otherwise ( $0 < \text{exponent\_t}[i] < 63$ ), the length $v = \text{Max}(0, \text{exponent\_t}[i] + \text{prec\_translation\_param} - 31)$ . + +The translation vector $T[i]$ for the $i$ -th camera is represented by: + +$$\begin{bmatrix} tE[i][0] \\ tE[i][1] \\ tE[i][2] \end{bmatrix} \quad (G-88)$$ + +The association between the camera parameter variables and corresponding syntax elements is specified by Table G-3. Each component of the intrinsic and rotation matrices and the translation vector is obtained from the variables specified in Table G-3 as the variable $x$ computed as follows: + +- If $0 < e < 63$ , $x = (-1)^s * 2^{(e-31)} * (1 + n \div 2^v)$ . +- Otherwise ( $e$ is equal to 0), $x = (-1)^s * 2^{-(30+v)} * n$ . + +NOTE – The above specification is similar to that found in IEC 60559:1989, *Binary floating-point arithmetic for microprocessor systems*. + +**Table G-3 – Association between camera parameter variables and syntax elements.** + +| x | s | e | n | +|---------------------------|----------------------------------|--------------------------------------|--------------------------------------| +| focalLengthX[i] | sign_focal_length_x[i] | exponent_focal_length_x[i] | mantissa_focal_length_x[i] | +| focalLengthY[i] | sign_focal_length_y[i] | exponent_focal_length_y[i] | mantissa_focal_length_y[i] | +| principalPointX[i] | sign_principal_point_x[i] | exponent_principal_point_x[i] | mantissa_principal_point_x[i] | +| principalPointY[i] | sign_principal_point_y[i] | exponent_principal_point_y[i] | mantissa_principal_point_y[i] | +| skewFactor[i] | sign_skew_factor[i] | exponent_skew_factor[i] | mantissa_skew_factor[i] | +| rE[i][j][k] | sign_r[i][j][k] | exponent_r[i][j][k] | mantissa_r[i][j][k] | +| tE[i][j] | sign_t[i][j] | exponent_t[i][j] | mantissa_t[i][j] | + +### G.13.2.6 Non-required view component SEI message semantics + +This SEI message indicates non-required view components within the associated access unit. A view component is a non-required view component for a target view component if it is not needed for decoding the target view component and subsequent view components with the same **view\_id** in decoding order within the coded video sequence. + +Some of the view components indicated by **view\_order\_index[i]** or **index\_delta\_minus1[i][j]** may not be present in the associated access unit. + +**num\_info\_entries\_minus1** plus 1 specifies the number of target view components for which non-required view components are indicated. The value of **num\_info\_entries\_minus1** shall be in the range of 0 to **num\_views\_minus1** – 1, inclusive. + +**view\_order\_index[i]** specifies the view order index of the $i$ -th target view component for which non-required view components are indicated. The $i$ -th target view component has **view\_id** equal to **view\_id[view\_order\_index[i]]**. The value of **view\_order\_index[i]** shall be in the range of 1 to **num\_views\_minus1**, inclusive. + +**num\_non\_required\_view\_components\_minus1[ i ]** plus 1 specifies the number of non-required view components for the i-th target view component. The value of **num\_non\_required\_view\_components\_minus1[ i ]** shall be in the range of 0 to **view\_order\_index[ i ]** - 1, inclusive. + +**index\_delta\_minus1[ i ][ j ]** plus 1 specifies the difference between the view order index of the i-th target view component and the view order index of the j-th non-required view component for the i-th target view component. The view order index of the j-th non-required view component for the i-th target view component is **view\_order\_index[ i ]** - **index\_delta\_minus1[ i ][ j ]** - 1. The value of **index\_delta\_minus1[ i ][ j ]** shall be in the range of 0 to **view\_order\_index[ i ]** - 1, inclusive. + +#### G.13.2.7 View dependency change SEI message semantics + +This SEI message indicates that the view dependency information changes starting with the current access unit containing the SEI message and is always interpreted with respect to the active MVC sequence parameter set. When present, the view dependency change SEI message applies to the target access unit set that consists of the current access unit and all the subsequent access units, in decoding order, until the next view dependency change SEI message or the end of the coded video sequence, whichever is earlier in decoding order. + +If, according to the view dependency information indicated in the active MVC sequence parameter set, view component A does not directly or indirectly depend on view component B and vice versa, the view dependency change SEI message shall not specify view dependency relationship between view components A and B. + +NOTE 1 – The dependent views for any view are always a subset of those indicated by the active MVC sequence parameter set. + +NOTE 2 – View dependency change SEI messages do not have a cumulative effect. + +Some of the views indicated by the following syntax elements may not be present in the target access unit set. + +**seq\_parameter\_set\_id** specifies a subset sequence parameter set that contains the inter-view dependency relationship information. The value of **seq\_parameter\_set\_id** shall be equal to the value of **seq\_parameter\_set\_id** in the picture parameter set referenced by a view component of the primary coded picture of the access unit containing the view dependency change SEI message. The value of **seq\_parameter\_set\_id** shall be in the range of 0 to 31, inclusive. + +**anchor\_update\_flag** equal to 1 indicates that there are updates for the dependencies for anchor view components relative to the dependencies defined in the active MVC sequence parameter set. **anchor\_update\_flag** equal to 0 indicates that there is no change for the dependencies for anchor view components relative to the dependencies defined in the active MVC sequence parameter set. + +**non\_anchor\_update\_flag** equal to 1 indicates that there are updates for the dependencies for non-anchor view components relative to the dependencies defined in the active MVC sequence parameter set. **non\_anchor\_update\_flag** equal to 0 indicates that there is no change for the dependencies for non-anchor view components relative to the dependencies defined in the active MVC sequence parameter set. + +**anchor\_ref\_10\_flag[ i ][ j ]** equal to 0 indicates that the j-th inter-view prediction reference in the initial reference picture list RefPicList0 (which is derived as specified in clause G.8.2.1) for any anchor view component with view order index equal to i will not be present in the final RefPicList0 after reference picture list modification for the anchor view component. **anchor\_ref\_10\_flag[ i ][ j ]** equal to 1 indicates that the j-th inter-view prediction reference in the initial reference picture list RefPicList0 for at least one anchor view component with view order index equal to i will be present in the final RefPicList0 after reference picture list modification for the anchor view component. + +**anchor\_ref\_11\_flag[ i ][ j ]** equal to 0 indicates that the j-th inter-view prediction reference in the initial reference picture list RefPicList1 (which is derived as specified in clause G.8.2.1) for any anchor view component with view order index equal to i will not be present in the final RefPicList1 after reference picture list modification for the anchor view component. **anchor\_ref\_11\_flag[ i ][ j ]** equal to 1 indicates that the j-th inter-view prediction reference in the initial reference picture list RefPicList1 for at least one anchor view component with view order index equal to i will be present in the final RefPicList1 after reference picture list modification for the anchor view component. + +**non\_anchor\_ref\_10\_flag[ i ][ j ]** equal to 0 indicates that the j-th inter-view prediction reference in the initial reference picture list RefPicList0 (which is derived as specified in clause G.8.2.1) for any non-anchor view component with view order index equal to i will not be present in the final RefPicList0 after reference picture list modification for the non-anchor view component. **non\_anchor\_ref\_10\_flag[ i ][ j ]** equal to 1 indicates that the j-th inter-view prediction reference in the initial reference picture list RefPicList0 for at least one non-anchor view component with view order index equal to i will be present in the final RefPicList0 after reference picture list modification for the non-anchor view component. + +**non\_anchor\_ref\_11\_flag[ i ][ j ]** equal to 0 indicates that the j-th inter-view prediction reference in the initial reference picture list RefPicList1 (which is derived as specified in clause G.8.2.1) for any non-anchor view component with view order index equal to i will not be present in the final RefPicList1 after reference picture list modification for the non-anchor view component. **non\_anchor\_ref\_11\_flag[ i ][ j ]** equal to 1 indicates that the j-th inter-view prediction reference + +in the initial reference picture list RefPicList1 for at least one non-anchor view component with view order index equal to i will be present in the final RefPicList1 after reference picture list modification for the non-anchor view component. + +#### G.13.2.8 Operation point not present SEI message semantics + +This SEI message indicates operation points that are not present in the bitstream starting with the current access unit, and is interpreted with respect to the previous view scalability information SEI message in decoding order. The message remains effective until the next SEI message of the same type or the end of the coded video sequence, whichever is earlier in decoding order. + +NOTE 1– Operation point not present SEI messages do not have a cumulative effect. + +NOTE 2 – Any operation point identified by a value of operation\_point\_id[ i ] in the previous view scalability information SEI message, in decoding order, and not identified by a value of operation\_point\_not\_present\_id[ k ] must be present in the coded video sequence. Therefore, when an application keeps an operation point not present SEI message in a sub-bitstream extracted according to the process specified in clause G.8.5.3, the application may need to change the content of the operation point not present SEI message according to the semantics. + +**num\_operation\_points** specifies the number of operation points that are indicated not to be present by the SEI message. num\_operation\_points equal to 0 indicates that all operation points indicated by the view scalability information SEI message are present. The value of num\_operation\_points shall be in the range of 0 to the value of num\_operation\_points\_minus1 in the previous view scalability information SEI message in decoding order, inclusive. + +**operation\_point\_not\_present\_id[ k ]** identifies an operation point that is not present. operation\_point\_not\_present\_id[ k ] shall be equal to the value of one of the operation\_point\_id[ i ] syntax elements of the previous view scalability information SEI message in decoding order. The value of operation\_point\_not\_present\_id[ k ] shall be in the range of 0 to 65535, inclusive. + +#### G.13.2.9 Base view temporal HRD SEI message semantics + +When present, this SEI message shall be associated with an IDR access unit. The SEI message applies to the coded video sequence. Some temporal subsets identified by sei\_mvc\_temporal\_id[ i ] may not be present in the coded video sequence. + +**num\_of\_temporal\_layers\_in\_base\_view\_minus1** plus 1 specifies the number of temporal sub-bitstreams in the coded video sequence for which the following syntax elements apply. The value of num\_of\_temporal\_layers\_in\_base\_view\_minus1 shall be in the range of 0 to 7, inclusive. + +**sei\_mvc\_temporal\_id[ i ]** specifies the temporal\_id value of the i-th temporal sub-bitstream. + +Let the i-th sub-bitstream for the coded video sequence that is obtained by invoking the sub-bitstream extraction process as specified in clause G.8.5.3 with tldTarget equal to sei\_mvc\_temporal\_id[ i ] as input. + +**sei\_mvc\_timing\_info\_present\_flag[ i ]** equal to 1 specifies that sei\_mvc\_num\_units\_in\_tick[ i ], sei\_mvc\_time\_scale[ i ], and sei\_mvc\_fixed\_frame\_rate\_flag[ i ] are present in the base view temporal HRD SEI message. sei\_mvc\_timing\_info\_present\_flag[ i ] equal to 0 specifies that sei\_mvc\_num\_units\_in\_tick[ i ], sei\_mvc\_time\_scale[ i ], and sei\_mvc\_fixed\_frame\_rate\_flag[ i ] are not present in the base view temporal HRD SEI message. + +The following syntax elements for the i-th sub-bitstream are specified using references to Annex E. For these syntax elements the same semantics and constraints as the ones specified in Annex E apply, as if these syntax elements sei\_mvc\_num\_units\_in\_tick[ i ], sei\_mvc\_time\_scale[ i ], sei\_mvc\_fixed\_frame\_rate\_flag[ i ], sei\_mvc\_nal\_hrd\_parameters\_present\_flag[ i ], sei\_mvc\_vcl\_hrd\_parameters\_present\_flag[ i ], sei\_mvc\_low\_delay\_hrd\_flag[ i ], and sei\_mvc\_pic\_struct\_present\_flag[ i ] were present as num\_units\_in\_tick, time\_scale, fixed\_frame\_rate\_flag, nal\_hrd\_parameters\_present\_flag, vcl\_hrd\_parameters\_present\_flag, low\_delay\_hrd\_flag, and pic\_struct\_present\_flag, respectively, in the VUI parameters of the active MVC sequence parameter sets for the i-th sub-bitstream. + +The parameters for the i-th sub-bitstream that are coded in the base view temporal HRD SEI message shall be correct, as if these parameters are used for conformance checking (as specified in Annex C) of the i-th sub-bitstream. + +**sei\_mvc\_num\_units\_in\_tick[ i ]** indicates the value of num\_units\_in\_tick, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +**sei\_mvc\_time\_scale[ i ]** indicates the value of time\_scale, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +**sei\_mvc\_fixed\_frame\_rate\_flag[ i ]** indicates the value of fixed\_frame\_rate\_flag, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +**sei\_mvc\_nal\_hrd\_parameters\_present\_flag[ i ]** indicates the value of nal\_hrd\_parameters\_present\_flag, as specified in clause E.2.1, that applies to the i-th sub-bitstream. When sei\_mvc\_nal\_hrd\_parameters\_present\_flag[ i ] is equal to 1, the + +NAL HRD parameters that apply to the i-th sub-bitstream immediately follow the `sei_mvc_nal_hrd_parameters_present_flag[ i ]`. + +`sei_mvc_vcl_hrd_parameters_present_flag[ i ]` indicates the value of `vc1_hrd_parameters_present_flag`, as specified in clause E.2.1, that applies to the i-th sub-bitstream. When `sei_mvc_vcl_hrd_parameters_present_flag[ i ]` is equal to 1, the VCL HRD parameters that apply to the i-th sub-bitstream immediately follow the `sei_mvc_vcl_hrd_parameters_present_flag[ i ]`. + +`sei_mvc_low_delay_hrd_flag[ i ]` indicates the value of `low_delay_hrd_flag`, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +`sei_mvc_pic_struct_present_flag[ i ]` indicates the value of `pic_struct_present_flag`, as specified in clause E.2.1, that applies to the i-th sub-bitstream. + +#### G.13.2.10 Multiview view position SEI message semantics + +The multiview view position SEI message specifies the relative view position along a single horizontal axis of view components within a coded video sequence. When present, the multiview view position SEI message shall be associated with an IDR access unit. The information signalled in this SEI message applies to the entire coded video sequence. + +`num_views_minus1` shall be equal to the value of the syntax element `num_views_minus1` in the active MVC sequence parameter set for the coded video sequence. The value of `num_views_minus1` shall be in the range of 0 to 1023, inclusive. + +`view_position[ i ]` indicates the order of the view with `VOIdx` equal to i among all the views from left to right for the purpose of display, with the order for the left-most view being equal to 0 and the value of the order increasing by 1 for next view from left to right. The value of `view_position[ i ]` shall be in the range of 0 to 1023, inclusive. + +`multiview_view_position_extension_flag` equal to 0 indicates that no additional data follows within the multiview view position SEI message. The value of `multiview_view_position_extension_flag` shall be equal to 0. The value of 1 for `multiview_view_position_extension_flag` is reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all data that follows the value of 1 for `multiview_view_position_extension_flag` in a multiview view position SEI message. + +#### G.14 Video usability information + +The specifications in Annex E apply with substituting MVC sequence parameter set for sequence parameter set. + +With `maxVOIdx` being the maximum value of view order index for the views that reference the MVC sequence parameter set containing the `vui_parameters( )` syntax structure, the VUI parameters and the constraints specified in Annex E apply to all views with a value of view order index that is less than or equal to `maxVOIdx`. + +Additionally, the following applies. + +##### G.14.1 MVC VUI parameters extension syntax + +| mvc_vui_parameters_extension( ) { | C | Descriptor | +|-------------------------------------------------------------------------------------|---|------------| +| vui_mvc_num_ops_minus1 | 0 | ue(v) | +| for( i = 0; i <= vui_mvc_num_ops_minus1; i++ ) { | | | +| vui_mvc_temporal_id[ i ] | 0 | u(3) | +| vui_mvc_num_target_output_views_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= vui_mvc_num_target_output_views_minus1[ i ]; j++ ) | | | +| vui_mvc_view_id[ i ][ j ] | 5 | ue(v) | +| vui_mvc_timing_info_present_flag[ i ] | 0 | u(1) | +| if( vui_mvc_timing_info_present_flag[ i ] ) { | | | +| vui_mvc_num_units_in_tick[ i ] | 0 | u(32) | +| vui_mvc_time_scale[ i ] | 0 | u(32) | +| vui_mvc_fixed_frame_rate_flag[ i ] | 0 | u(1) | +| } | | | +| vui_mvc_nal_hrd_parameters_present_flag[ i ] | 0 | u(1) | +| if( vui_mvc_nal_hrd_parameters_present_flag[ i ] ) | | | +| hrd_parameters( ) | 0 | | +| vui_mvc_vcl_hrd_parameters_present_flag[ i ] | 0 | u(1) | +| if( vui_mvc_vcl_hrd_parameters_present_flag[ i ] ) | | | + +| | | | +|-------------------------------------------------------------------------------------------------------|---|------| +| hrd_parameters() | 0 | | +| if( vui_mvc_nal_hrd_parameters_present_flag[ i ]
vui_mvc_vcl_hrd_parameters_present_flag[ i ] ) | | | +| vui_mvc_low_delay_hrd_flag[ i ] | 0 | u(1) | +| vui_mvc_pic_struct_present_flag[ i ] | 0 | u(1) | +| } | | | +| } | | | + +#### G.14.2 MVC VUI parameters extension semantics + +The MVC VUI parameters extension specifies VUI parameters that apply to one or more operation points for the coded video sequence. In Annex C it is specified which of the HRD parameter sets specified in the MVC VUI parameters extension are used for conformance checking. All MVC VUI parameters extensions that are referred to by a coded video sequence shall be identical. + +Some views identified by **vui\_mvc\_view\_id[ i ][ j ]** may not be present in the coded video sequence. Some temporal subsets identified by **vui\_mvc\_temporal\_id[ i ]** may not be present in the coded video sequence. + +**vui\_mvc\_num\_ops\_minus1** plus 1 specifies the number of operation points for which timing information, NAL HRD parameters, VCL HRD parameters, and the **pic\_struct\_present\_flag** may be present. The value of **vui\_mvc\_num\_ops\_minus1** shall be in the range of 0 to 1023, inclusive. + +**vui\_mvc\_temporal\_id[ i ]** indicates the maximum value of **temporal\_id** for all VCL NAL units in the representation of the i-th operation point. + +**vui\_mvc\_num\_target\_output\_views\_minus1[ i ]** plus one specifies the number of target output views for the i-th operation point. The value of **vui\_mvc\_num\_target\_output\_views\_minus1[ i ]** shall be in the range of 0 to 1023, inclusive. + +**vui\_mvc\_view\_id[ i ][ j ]** indicates the j-th target output view in the i-th operation point. The value of **vui\_mvc\_view\_id[ i ][ j ]** shall be in the range of 0 to 1023, inclusive. + +The following syntax elements apply to the coded video sequence that is obtained by the sub-bitstream extraction process as specified in clause G.8.5.3 with **tIdTarget** equal to **vui\_mvc\_temporal\_id[ i ]** and **viewIdTargetList** containing **vui\_mvc\_view\_id[ i ][ j ]** for all j in the range of 0 to **vui\_mvc\_num\_target\_output\_views\_minus1[ i ]**, inclusive, as the inputs and the i-th sub-bitstream as the output. + +**vui\_mvc\_timing\_info\_present\_flag[ i ]** equal to 1 specifies that **vui\_mvc\_num\_units\_in\_tick[ i ]**, **vui\_mvc\_time\_scale[ i ]**, and **vui\_mvc\_fixed\_frame\_rate\_flag[ i ]** for the i-th sub-bitstream are present in the MVC VUI parameters extension. **vui\_mvc\_timing\_info\_present\_flag[ i ]** equal to 0 specifies that **vui\_mvc\_num\_units\_in\_tick[ i ]**, **vui\_mvc\_time\_scale[ i ]**, and **vui\_mvc\_fixed\_frame\_rate\_flag[ i ]** for the i-th sub-bitstream are not present in the MVC VUI parameters extension. + +The following syntax elements for the i-th sub-bitstream are specified using references to Annex E. For these syntax elements the same semantics and constraints as the ones specified in Annex E apply, as if these syntax elements **vui\_mvc\_num\_units\_in\_tick[ i ]**, **vui\_mvc\_time\_scale[ i ]**, **vui\_mvc\_fixed\_frame\_rate\_flag[ i ]**, **vui\_mvc\_nal\_hrd\_parameters\_present\_flag[ i ]**, **vui\_mvc\_vcl\_hrd\_parameters\_present\_flag[ i ]**, **vui\_mvc\_low\_delay\_hrd\_flag[ i ]**, and **vui\_mvc\_pic\_struct\_present\_flag[ i ]** were present as the syntax elements **num\_units\_in\_tick**, **time\_scale**, **fixed\_frame\_rate\_flag**, **nal\_hrd\_parameters\_present\_flag**, **vcl\_hrd\_parameters\_present\_flag**, **low\_delay\_hrd\_flag**, and **pic\_struct\_present\_flag**, respectively, in the VUI parameters of the active MVC sequence parameter sets for the i-th sub-bitstream. + +**vui\_mvc\_num\_units\_in\_tick[ i ]** specifies the value of **num\_units\_in\_tick**, as specified in clause E.2.1, for the i-th sub-bitstream. + +**vui\_mvc\_time\_scale[ i ]** specifies the value of **time\_scale**, as specified in clause E.2.1, for the i-th sub-bitstream. + +**vui\_mvc\_fixed\_frame\_rate\_flag[ i ]** specifies the value of **fixed\_frame\_rate\_flag**, as specified in clause E.2.1, for the i-th sub-bitstream. + +**vui\_mvc\_nal\_hrd\_parameters\_present\_flag[ i ]** specifies the value of **nal\_hrd\_parameters\_present\_flag**, as specified in clause E.2.1, for the i-th sub-bitstream. + +When **vui\_mvc\_nal\_hrd\_parameters\_present\_flag[ i ]** is equal to 1, NAL HRD parameters (clauses E.1.2 and E.2.2) for the i-th sub-bitstream immediately follow the flag. + +The variable **VuiMvcNalHrdBpPresentFlag[ i ]** is derived as follows: + +- If any of the following is true, the value of `VuiMvcNalHrdBpPresentFlag[ i ]` shall be set equal to 1: + - `vui_mvc_nal_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, + - for the i-th sub-bitstream, the need for presence of buffering periods for NAL HRD operation to be present in the bitstream in buffering period SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of `VuiMvcNalHrdBpPresentFlag[ i ]` shall be set equal to 0. + +**`vui_mvc_vcl_hrd_parameters_present_flag[ i ]`** specifies the value of `vel_hrd_parameters_present_flag`, as specified in clause E.2.1, for the i-th sub-bitstream. + +When `vui_mvc_vcl_hrd_parameters_present_flag[ i ]` is equal to 1, VCL HRD parameters (clauses E.1.2 and E.2.2) for the i-th sub-bitstream immediately follow the flag. + +The variable `VuiMvcVclHrdBpPresentFlag[ i ]` is derived as follows: + +- If any of the following is true, the value of `VuiMvcVclHrdBpPresentFlag[ i ]` shall be set equal to 1: + - `vui_mvc_vcl_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, + - for the i-th sub-bitstream, the need for presence of buffering period parameters for VCL HRD operation in the bitstream in buffering period SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of `VuiMvcVclHrdBpPresentFlag[ i ]` shall be set equal to 0. + +The variable `VuiMvcCpbDpbDelaysPresentFlag[ i ]` is derived as follows: + +- If any of the following is true, the value of `VuiMvcCpbDpbDelaysPresentFlag[ i ]` shall be set equal to 1: + - `vui_mvc_nal_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, + - `vui_mvc_vcl_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, + - for the i-th sub-bitstream, the need for presence of CPB and DPB output delays in the bitstream in picture timing SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of `VuiMvcCpbDpbDelaysPresentFlag[ i ]` shall be set equal to 0. + +**`vui_mvc_low_delay_hrd_flag[ i ]`** specifies the value of `low_delay_hrd_flag`, as specified in clause E.2.1, for the i-th sub-bitstream. + +**`vui_mvc_pic_struct_present_flag[ i ]`** specifies the value of `pic_struct_present_flag`, as specified in clause E.2.1, for the i-th sub-bitstream. + +## Annex H + +### Multiview and depth video coding + +(This annex forms an integral part of this Recommendation | International Standard.) + +This annex specifies multiview video coding with depth information, referred to as MVCD. + +#### H.1 Scope + +Bitstreams and decoders conforming to the profile specified in this annex are completely specified in this annex with reference made to clauses 2 to 9 and Annexes A to G. + +#### H.2 Normative references + +The specifications in clause 2 apply. + +#### H.3 Definitions + +For the purpose of this annex, the following definitions apply in addition to the definitions in clause G.3. These definitions are either not present in clause G.3 or replace definitions in clause G.3. + +**H.3.1 depth field view:** A *depth view component* of a *field*. + +**H.3.2 depth frame view:** A *depth view component* of a *frame*. + +**H.3.3 depth view:** A sequence of *depth view components* associated with an identical value of *view\_id*. + +**H.3.4 depth view component:** A *coded representation* of the depth of a view in a single *access unit*. + +**H.3.5 inter-view only reference component:** A *view component*, *texture view component*, or *depth view component* coded with *nal\_ref\_idc* equal to 0 and *inter\_view\_flag* equal to 1. An *inter-view only reference component* contains samples that may be used for *inter-view prediction* in the *decoding process* of subsequent *view components* in *decoding order*, but are not used for *inter prediction* by any *view components*. *Inter-view only reference components* are *non-reference pictures*. + +**H.3.6 inter-view reference component:** A *view component*, *texture view component*, or *depth view component* coded with *nal\_ref\_idc* greater than 0 and *inter\_view\_flag* equal to 1. An *inter-view reference component* contains samples that may be used for *inter prediction* of subsequent *pictures* in *decoding order* and *inter-view prediction* of subsequent *view components* in *decoding order*. *Inter-view reference components* are *reference pictures*. + +**H.3.7 MVCD operation point:** An operation point for which each target output view includes a texture view or a depth view or both a texture view and a depth view. + +**H.3.8 MVCD sequence parameter set:** A collective term for *sequence parameter set* or *subset sequence parameter set*. + +**H.3.9 MVCD sequence parameter set RBSP:** A collective term for *sequence parameter set RBSP* or *subset sequence parameter set RBSP*. + +**H.3.10 reference picture:** A *view component*, *texture view component*, or *depth view component* coded with *nal\_ref\_idc* greater than 0. A *reference picture* contains samples that may be used for *inter prediction* in the *decoding process* of subsequent *view components* in *decoding order*. A *reference picture* may be an *inter-view reference component*, in which case the samples contained in the *reference picture* may also be used for *inter-view prediction* in the *decoding process* of subsequent *view components* in *decoding order*. + +**H.3.11 stereoscopic texture bitstream:** A *bitstream* containing two *texture views* and conforming to one of the *profiles* specified in Annex G. + +**H.3.12 texture field view component:** A *texture view component* of a *field*. + +**H.3.13 texture frame view component:** A *texture view component* of a *frame*. + +**H.3.14 texture view:** A sequence of *texture view components* associated with an identical value of *view\_id*. + +**H.3.15 texture view component:** A *coded representation* of the texture of a view in a single *access unit*. + +- H.3.16 view:** A *texture view* and a *depth view* with the same value of *view\_id*, unless explicitly limited to either *texture view* or *depth view*. +- H.3.17 view component:** A *coded representation* of a *view* in a single *access unit*. A *view component* may consist of a *texture view component* and a *depth view component*. +- H.3.18 view component pair:** A *texture view component* and a *depth view component* of the same *view* within the same *access unit*. + +## H.4 Abbreviations + +The specifications in clause 4 apply. + +## H.5 Conventions + +The specifications in clause 5 apply. + +## H.6 Source, coded, decoded and output data formats, scanning processes, and neighbouring relationships + +The specifications in clause 6 apply with substitution of MVCD sequence parameter set for sequence parameter set. + +## H.7 Syntax and semantics + +This clause specifies syntax and semantics for coded video sequences that conform to one or more of the profiles specified in this annex. + +### H.7.1 Method of specifying syntax in tabular form + +The specifications in clause G.7.1 apply. + +### H.7.2 Specification of syntax functions, categories, and descriptors + +The specifications in clause G.7.2 apply. + +### H.7.3 Syntax in tabular form + +#### H.7.3.1 NAL unit syntax + +The syntax table is specified in clause G.7.3.1. + +##### H.7.3.1.1 NAL unit header MVC extension syntax + +The syntax table is specified in clause G.7.3.1.1. + +#### H.7.3.2 Raw byte sequence payloads and RBSP trailing bits syntax + +##### H.7.3.2.1 Sequence parameter set RBSP syntax + +The syntax table is specified in clause G.7.3.2.1. + +###### H.7.3.2.1.1 Sequence parameter set data syntax + +The syntax table is specified in clause G.7.3.2.1.1. + +###### H.7.3.2.1.1.1 Scaling list syntax + +The syntax table is specified in clause G.7.3.2.1.1.1. + +##### H.7.3.2.1.2 Sequence parameter set extension RBSP syntax + +The syntax table is specified in clause G.7.3.2.1.2. + +##### H.7.3.2.1.3 Subset sequence parameter set RBSP syntax + +The syntax table is specified in clause G.7.3.2.1.3. + +##### H.7.3.2.1.4 Sequence parameter set MVC extension syntax + +The syntax table is specified in clause G.7.3.2.1.4. + +H.7.3.2.1.5 Sequence parameter set MVCD extension syntax + +| seq_parameter_set_mvcd_extension() { | C | Descriptor | +|----------------------------------------------------------------------------|---|------------| +| num_views_minus1 | 0 | ue(v) | +| for ( i = 0; NumDepthViews = 0; i <= num_views_minus1; i++ ) { | | | +| view_id[ i ] | 0 | ue(v) | +| depth_view_present_flag[ i ] | 0 | u(1) | +| DepthViewId[ NumDepthViews ] = view_id[ i ] | | | +| NumDepthViews += depth_view_present_flag[ i ] | | | +| texture_view_present_flag[ i ] | 0 | u(1) | +| } | | | +| for ( i = 1; i <= num_views_minus1; i++ ) | | | +| if( depth_view_present_flag[ i ] ) { | | | +| num_anchor_refs_l0[ i ] | 0 | ue(v) | +| for ( j = 0; j < num_anchor_refs_l0[ i ]; j++ ) | | | +| anchor_ref_l0[ i ][ j ] | 0 | ue(v) | +| num_anchor_refs_l1[ i ] | 0 | ue(v) | +| for ( j = 0; j < num_anchor_refs_l1[ i ]; j++ ) | | | +| anchor_ref_l1[ i ][ j ] | 0 | ue(v) | +| } | | | +| for ( i = 1; i <= num_views_minus1; i++ ) | | | +| if( depth_view_present_flag[ i ] ) { | | | +| num_non_anchor_refs_l0[ i ] | 0 | ue(v) | +| for ( j = 0; j < num_non_anchor_refs_l0[ i ]; j++ ) | | | +| non_anchor_ref_l0[ i ][ j ] | 0 | ue(v) | +| num_non_anchor_refs_l1[ i ] | 0 | ue(v) | +| for ( j = 0; j < num_non_anchor_refs_l1[ i ]; j++ ) | | | +| non_anchor_ref_l1[ i ][ j ] | 0 | ue(v) | +| } | | | +| num_level_values_signalled_minus1 | 0 | ue(v) | +| for ( i = 0; i <= num_level_values_signalled_minus1; i++ ) { | | | +| level_idc[ i ] | 0 | u(8) | +| num_applicable_ops_minus1[ i ] | 0 | ue(v) | +| for ( j = 0; j <= num_applicable_ops_minus1[ i ]; j++ ) { | | | +| applicable_op_temporal_id[ i ][ j ] | 0 | u(3) | +| applicable_op_num_target_views_minus1[ i ][ j ] | 0 | ue(v) | +| for ( k = 0; k <= applicable_op_num_target_views_minus1[ i ][ j ]; k++ ) { | | | +| applicable_op_target_view_id[ i ][ j ][ k ] | 0 | ue(v) | +| applicable_op_depth_flag[ i ][ j ][ k ] | 0 | u(1) | +| applicable_op_texture_flag[ i ][ j ][ k ] | 0 | u(1) | +| } | | | +| applicable_op_num_texture_views_minus1[ i ][ j ] | 0 | ue(v) | +| applicable_op_num_depth_views[ i ][ j ] | 0 | ue(v) | +| } | | | +| } | | | +| mvcd_vui_parameters_present_flag | 0 | u(1) | +| if( mvcd_vui_parameters_present_flag == 1 ) | | | +| mvcd_vui_parameters_extension() | | | +| texture_vui_parameters_present_flag | 0 | u(1) | +| if( texture_vui_parameters_present_flag == 1 ) | | | +| mvc_vui_parameters_extension() | 0 | | +| } | | | + +#### **H.7.3.2.2 Picture parameter set RBSP syntax** + +The syntax table is specified in clause G.7.3.2.2. + +#### **H.7.3.2.3 Supplemental enhancement information RBSP syntax** + +The syntax table is specified in clause G.7.3.2.3. + +##### **H.7.3.2.3.1 Supplemental enhancement information message syntax** + +The syntax table is specified in clause G.7.3.2.3.1. + +#### **H.7.3.2.4 Access unit delimiter RBSP syntax** + +The syntax table is specified in clause G.7.3.2.4. + +#### **H.7.3.2.5 End of sequence RBSP syntax** + +The syntax table is specified in clause G.7.3.2.5. + +#### **H.7.3.2.6 End of stream RBSP syntax** + +The syntax table is specified in clause G.7.3.2.6. + +#### **H.7.3.2.7 Filler data RBSP syntax** + +The syntax table is specified in clause G.7.3.2.7. + +#### **H.7.3.2.8 Slice layer without partitioning RBSP syntax** + +The syntax table is specified in clause G.7.3.2.8. + +#### **H.7.3.2.9 Slice data partition RBSP syntax** + +Slice data partition syntax is not present in coded video sequences conforming to one or more of the profiles specified in this annex. + +#### **H.7.3.2.10 RBSP slice trailing bits syntax** + +The syntax table is specified in clause G.7.3.2.10. + +#### **H.7.3.2.11 RBSP trailing bits syntax** + +The syntax table is specified in clause G.7.3.2.11. + +#### **H.7.3.2.12 Prefix NAL unit RBSP syntax** + +The syntax table is specified in clause G.7.3.2.12. + +#### **H.7.3.2.13 Slice layer extension RBSP syntax** + +The syntax table is specified in clause G.7.3.2.13. + +#### **H.7.3.3 Slice header syntax** + +The syntax table is specified in clause G.7.3.3. + +##### **H.7.3.3.1 Reference picture list modification syntax** + +The syntax table is specified in clause G.7.3.3.1. + +###### **H.7.3.3.1.1 Reference picture list MVC modification syntax** + +The syntax table is specified in clause G.7.3.3.1.1 + +##### **H.7.3.3.2 Prediction weight table syntax** + +The syntax table is specified in clause G.7.3.3.2. + +##### **H.7.3.3.3 Decoded reference picture marking syntax** + +The syntax table is specified in clause G.7.3.3.3. + +#### **H.7.3.4 Slice data syntax** + +The syntax table is specified in clause G.7.3.4. + +### **H.7.3.5 Macroblock layer syntax** + +The syntax table is specified in clause G.7.3.5. + +#### **H.7.3.5.1 Macroblock prediction syntax** + +The syntax table is specified in clause G.7.3.5.1. + +#### **H.7.3.5.2 Sub-macroblock prediction syntax** + +The syntax table is specified in clause G.7.3.5.2. + +#### **H.7.3.5.3 Residual data syntax** + +The syntax table is specified in clause G.7.3.5.3. + +##### **H.7.3.5.3.1 Residual luma syntax** + +The syntax table is specified in clause G.7.3.5.3.1. + +##### **H.7.3.5.3.2 Residual block CAVLC syntax** + +The syntax table is specified in clause G.7.3.5.3.2. + +##### **H.7.3.5.3.3 Residual block CABAC syntax** + +The syntax table is specified in clause G.7.3.5.3.3. + +## **H.7.4 Semantics** + +Semantics associated with the syntax structures and syntax elements within these structures (in clause H.7.3 and in clause G.7.3 by reference in clause H.7.3) are specified in this clause and by reference to clause H.7.4. When the semantics of a syntax element are specified using a table or a set of tables, any values that are not specified in the table(s) shall not be present in the bitstream unless otherwise specified in this Recommendation | International Standard. + +### **H.7.4.1 NAL unit semantics** + +The semantics for the syntax elements in clause H.7.3.1 are specified in clause G.7.4.1. + +#### **H.7.4.1.1 NAL unit header MVC extension semantics** + +The semantics for the syntax elements in clause H.7.3.1.1 are specified in clause G.7.4.1.1. + +#### **H.7.4.1.2 Order of NAL units and association to coded pictures, access units, and video sequences** + +This clause specifies constraints on the order of NAL units in the bitstream. Any order of NAL units in the bitstream obeying these constraints is referred to in the text as the decoding order of NAL units. Within a NAL unit, the syntax in clauses 7.3, D.1, E.1, G.7.3, G.13.1, G.14.1, H.13.1 and H.14.1 specifies the decoding order of syntax elements. Decoders shall be capable of receiving NAL units and their syntax elements in decoding order. + +##### **H.7.4.1.2.1 Order of MVCD sequence parameter set RBSPs and picture parameter set RBSPs and their activation** + +NOTE 1 – The sequence and picture parameter set mechanism decouples the transmission of infrequently changing information from the transmission of coded macroblock data. Sequence and picture parameter sets may, in some applications, be conveyed "out-of-band" using a reliable transport mechanism. + +A picture parameter set RBSP includes parameters that can be referred to by the coded slice NAL units of one or more texture view or depth view components of one or more coded pictures. + +Each picture parameter set RBSP is initially considered not active at the start of the operation of the decoding process. At most one picture parameter set RBSP is considered as the active picture parameter set RBSP at any given moment during the operation of the decoding process, and when any particular picture parameter set RBSP becomes the active picture parameter set RBSP, the previously-active picture parameter set RBSP (if any) is deactivated. + +In addition to the active picture parameter set RBSP, zero or more picture parameter set RBSPs may be specifically active for texture view components (with a particular value of VOIdx less than or equal to VOIdxMax) that belong to the target output views or that may be referred to through inter-view prediction in decoding texture view components belonging to the target output views. Such a picture parameter set RBSP is referred to as the active texture picture parameter set RBSP for the particular value of VOIdx. The restrictions on active picture parameter set RBSPs also apply to active texture picture parameter set RBSPs for a particular value of VOIdx. + +Furthermore, zero or more picture parameter set RBSPs may be specifically active for depth view components (with a particular value of VOIdx less than VOIdxMax) that belong to the target output views or that may be referred to through inter-view prediction in decoding depth view components belonging to the target output views. Such a picture parameter + +set RBSP is referred to as the active depth picture parameter set RBSP for the particular value of VOIdx. The restrictions on active picture parameter set RBSPs also apply to active depth picture parameter set RBSPs for a particular value of VOIdx less than VOIdxMax. + +When a picture parameter set RBSP (with a particular value of pic\_parameter\_set\_id) is not the active picture parameter set RBSP and it is referred to by a coded slice NAL unit belonging to a depth view component (i.e., with nal\_unit\_type equal to 21) and with VOIdx equal to VOIdxMax (using that value of pic\_parameter\_set\_id), it is activated. This picture parameter set RBSP is called the active picture parameter set RBSP until it is deactivated when another picture parameter set RBSP becomes the active picture parameter set RBSP. A picture parameter set RBSP, with that particular value of pic\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a picture parameter set RBSP (with a particular value of pic\_parameter\_set\_id) is not the active depth picture parameter set for a particular value of VOIdx less than VOIdxMax and it is referred to by a coded slice NAL unit belonging to a depth view component (i.e., with nal\_unit\_type equal to 21) and with the particular value of VOIdx (using that value of pic\_parameter\_set\_id), it is activated for view components with the particular value of VOIdx. This picture parameter set RBSP is called the active depth picture parameter set RBSP for the particular value of VOIdx until it is deactivated when another picture parameter set RBSP becomes the active depth picture parameter set RBSP for the particular value of VOIdx. A picture parameter set RBSP, with that particular value of pic\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a picture parameter set RBSP (with a particular value of pic\_parameter\_set\_id) is not the active texture picture parameter set for a particular value of VOIdx less than or equal to VOIdxMax and it is referred to by a coded slice NAL unit belonging to a texture view component (i.e., with nal\_unit\_type equal to 1, 5 or 20) and with the particular value of VOIdx (using that value of pic\_parameter\_set\_id), it is activated for texture view components with the particular value of VOIdx. This picture parameter set RBSP is called the active texture picture parameter set RBSP for the particular value of VOIdx until it is deactivated when another picture parameter set RBSP becomes the active texture picture parameter set RBSP for the particular value of VOIdx. A picture parameter set RBSP, with that particular value of pic\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +Any picture parameter set NAL unit containing the value of pic\_parameter\_set\_id for the active picture parameter set RBSP for a coded picture shall have the same content as that of the active picture parameter set RBSP for this coded picture unless it follows the last VCL NAL unit of this coded picture and precedes the first VCL NAL unit of another coded picture. Any picture parameter set NAL unit containing the value of pic\_parameter\_set\_id for the active depth picture parameter set RBSP for a particular value of VOIdx less than VOIdxMax for a coded picture shall have the same content as that of the active view picture parameter set RBSP for the particular value of VOIdx for this coded picture unless it follows the last VCL NAL unit of this coded picture and precedes the first VCL NAL unit of another coded picture. Any picture parameter set NAL unit containing the value of pic\_parameter\_set\_id for the active texture picture parameter set RBSP for a particular value of VOIdx for a coded picture shall have the same content as that of the active texture picture parameter set RBSP for the particular value of VOIdx for this coded picture unless it follows the last VCL NAL unit of this coded picture and precedes the first VCL NAL unit of another coded picture. + +An MVCD sequence parameter set RBSP includes parameters that can be referred to by one or more picture parameter set RBSPs or one or more buffering period SEI messages. + +Each MVCD sequence parameter set RBSP is initially considered not active at the start of the operation of the decoding process. At most one MVCD sequence parameter set RBSP is considered as the active MVCD sequence parameter set RBSP at any given moment during the operation of the decoding process, and when any particular MVCD sequence parameter set RBSP becomes the active MVCD sequence parameter set RBSP, the previously-active MVCD sequence parameter set RBSP (if any) is deactivated. + +In addition to the active MVCD sequence parameter set RBSP, zero or more MVCD sequence parameter set RBSPs may be specifically active for view components (with a particular value of VOIdx less than VOIdxMax) that belong to the target output views or that may be referred to through inter-view prediction in decoding view components belonging to the target output views. Such an MVCD sequence parameter set RBSP is referred to as the active view MVCD sequence parameter set RBSP for the particular value of VOIdx. The restrictions on active MVCD sequence parameter set RBSPs also apply to active view MVCD sequence parameter set RBSPs for a particular value of VOIdx less than VOIdxMax. + +Furthermore, zero or more MVCD sequence parameter set RBSPs may be specifically active for texture view components (with a particular value of VOIdx less than or equal to VOIdxMax) that belong to the target output views or that may be referred to through inter-view prediction in decoding texture view components belonging to the target output views. Such an MVCD sequence parameter set RBSP is referred to as the active texture MVCD sequence parameter set RBSP for the particular value of VOIdx. The restrictions on active MVCD sequence parameter set RBSPs also apply to active texture MVCD sequence parameter set RBSPs for a particular value of VOIdx. + +For the following specification, the activating buffering period SEI message is specified as follows: + +- If VOIdxMax is equal to VOIdxMin and the access unit contains a buffering period SEI message not included in an MVC scalable nesting SEI message and not included in an MVCD scalable nesting SEI message, this buffering period SEI message is the activating buffering period SEI message. +- Otherwise if VOIdxMax is not equal to VOIdxMin and the access unit contains a buffering period SEI message included in an MVCD scalable nesting SEI message and associated with the operation point being decoded, this buffering period SEI message is the activating buffering period SEI message. +- Otherwise, the access unit does not contain an activating buffering period SEI message. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active MVCD sequence parameter set RBSP and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice NAL unit with nal\_unit\_type equal to 1 or 5 (the picture parameter set RBSP becomes the active picture parameter set RBSP and VOIdxMax is equal to VOIdxMin and there is no depth view component in any access unit) and the access unit does not contain an activating buffering period SEI message, it is activated. This sequence parameter set RBSP is called the active MVCD sequence parameter set RBSP until it is deactivated when another MVCD sequence parameter set RBSP becomes the active MVCD sequence parameter set RBSP. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active MVCD sequence parameter set RBSP and it is referred to by an activating buffering period SEI message (using that value of seq\_parameter\_set\_id) that is not included in an MVCD scalable nesting SEI message and VOIdxMax is equal to VOIdxMin and there is no depth view component in the access unit, it is activated. This sequence parameter set RBSP is called the active MVCD sequence parameter set RBSP until it is deactivated when another MVCD sequence parameter set RBSP becomes the active MVCD sequence parameter set RBSP. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active MVCD sequence parameter set RBSP and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice depth extension NAL unit with nal\_unit\_type equal to 21 and with VOIdx equal to VOIdxMax (the picture parameter set RBSP becomes the active picture parameter set RBSP) and the access unit does not contain an activating buffering period SEI message, it is activated. This subset sequence parameter set RBSP is called the active MVCD sequence parameter set RBSP until it is deactivated when another MVCD sequence parameter set RBSP becomes the active MVCD sequence parameter set RBSP. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active MVCD sequence parameter set RBSP and it is referred to by an activating buffering period SEI message (using that value of seq\_parameter\_set\_id) that is included in an MVCD scalable nesting SEI message, it is activated. This subset sequence parameter set RBSP is called the active MVCD sequence parameter set RBSP until it is deactivated when another MVCD sequence parameter set RBSP becomes the active MVCD sequence parameter set RBSP. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +NOTE 2 – The active MVCD sequence parameter set RBSP is either a sequence parameter set RBSP or a subset sequence parameter set RBSP. Sequence parameter set RBSPs are activated by coded slice NAL units with nal\_unit\_type equal to 1 or 5 or buffering period SEI messages that are not included in an MVC scalable nesting SEI message or an MVCD scalable nesting SEI message. Subset sequence parameter sets are activated by coded slice depth extension NAL units (nal\_unit\_type equal to 21) or buffering period SEI messages that are included in an MVCD scalable nesting SEI message. A sequence parameter set RBSP and a subset sequence parameter set RBSP may have the same value of seq\_parameter\_set\_id. + +For the following specification, the activating texture buffering period SEI message for a particular value of VOIdx is specified as follows: + +- If the access unit contains one or more than one buffering period SEI message included in an MVC scalable nesting SEI message and associated with an operation point for which the greatest VOIdx in the associated sub-bitstream is equal to the particular value of VOIdx, the first of these buffering period SEI messages, in decoding order, is the activating texture buffering period SEI message for the particular value of VOIdx. +- Otherwise, if the access unit contains a buffering period SEI message not included in an MVC scalable nesting SEI message or an MVCD scalable nesting SEI message, this buffering period SEI message is the activating texture buffering period SEI message for the particular value of VOIdx equal to VOIdxMin. +- Otherwise, the access unit does not contain an activating texture buffering period SEI message for the particular value of VOIdx. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active texture MVCD sequence parameter set RBSP for VOIdx equal to VOIdxMin and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice NAL unit with nal\_unit\_type equal to 1 or 5 (the picture parameter set RBSP becomes the active texture picture parameter set RBSP for VOIdx equal to VOIdxMin), it is activated for texture view components with VOIdx equal to VOIdxMin. This sequence parameter set RBSP is called the active texture MVCD sequence parameter set RBSP for VOIdx equal to VOIdxMin until it is deactivated when another MVCD sequence parameter set RBSP becomes the active texture MVCD sequence parameter set RBSP for VOIdx equal to VOIdxMin. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a sequence parameter set RBSP (nal\_unit\_type is equal to 7) with a particular value of seq\_parameter\_set\_id is not already the active texture MVCD sequence parameter set RBSP for VOIdx equal to VOIdxMin and it is referred to by an activating texture buffering period SEI message (using that value of seq\_parameter\_set\_id) that is not included in an MVC scalable nesting SEI message or an MVCD scalable nesting SEI message, the sequence parameter set RBSP is activated for texture view components with VOIdx equal to VOIdxMin. This sequence parameter set RBSP is called the active texture MVCD sequence parameter set RBSP for VOIdx equal to VOIdxMin until it is deactivated when another MVCD sequence parameter set RBSP becomes the active texture MVCD sequence parameter set RBSP for VOIdx equal to VOIdxMin. A sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active texture MVCD sequence parameter set RBSP for a particular value of VOIdx less than or equal to VOIdxMax and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice MVC extension NAL unit (nal\_unit\_type equal to 20) with the particular value of VOIdx (the picture parameter set RBSP becomes the active texture picture parameter set RBSP for the particular value of VOIdx), it is activated for texture view components with the particular value of VOIdx. This subset sequence parameter set RBSP is called the active texture MVCD sequence parameter set RBSP for the particular value of VOIdx until it is deactivated when another MVCD sequence parameter set RBSP becomes the active texture MVCD sequence parameter set RBSP for the particular value of VOIdx. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active texture MVCD sequence parameter set RBSP for a particular value of VOIdx less than or equal to VOIdxMax and it is referred to by an activating texture buffering period SEI message (using that value of seq\_parameter\_set\_id) that is included in an MVC scalable nesting SEI message and associated with the particular value of VOIdx, this subset sequence parameter set RBSP is activated for texture view components with the particular value of VOIdx. This subset sequence parameter set RBSP is called the active texture MVCD sequence parameter set RBSP for the particular value of VOIdx until it is deactivated when another MVCD sequence parameter set RBSP becomes the active texture MVCD sequence parameter set RBSP for the particular value of VOIdx. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +For the following specification, the activating view buffering period SEI message for a particular value of VOIdx is specified as follows: + +- If the access unit contains one or more than one buffering period SEI message included in an MVCD scalable nesting SEI message and associated with an operation point for which the greatest VOIdx in the associated sub-bitstream is equal to the particular value of VOIdx, the first of these buffering period SEI messages, in decoding order, is the activating view buffering period SEI message for the particular value of VOIdx. +- Otherwise, the access unit does not contain an activating view buffering period SEI message for the particular value of VOIdx. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active view MVCD sequence parameter set RBSP for a particular value of VOIdx less than VOIdxMax and it is referred to by activation of a picture parameter set RBSP (using that value of seq\_parameter\_set\_id) and the picture parameter set RBSP is activated by a coded slice NAL unit with nal\_unit\_type equal to 21 and with the particular value of VOIdx (the picture parameter set RBSP becomes the active view picture parameter set RBSP for the particular value of VOIdx), it is activated for view components with the particular value of VOIdx. This subset sequence parameter set RBSP is called the active view MVCD sequence parameter set RBSP for the particular value of VOIdx until it is deactivated when another MVCD sequence parameter set RBSP becomes the active view MVCD sequence parameter set RBSP for the particular value of VOIdx or when decoding an access unit with VOIdxMax less than or equal to the particular value of VOIdx. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +When a subset sequence parameter set RBSP (nal\_unit\_type is equal to 15) with a particular value of seq\_parameter\_set\_id is not already the active view MVCD sequence parameter set RBSP for a particular value of VOIdx less than VOIdxMax and it is referred to by an activating view buffering period SEI message (using that value of seq\_parameter\_set\_id) that is included in an MVCD scalable nesting SEI message and associated with the particular value of VOIdx, this subset sequence parameter set RBSP is activated for view components with the particular value of VOIdx. This subset sequence parameter set RBSP is called the active view MVCD sequence parameter set RBSP for the particular value of VOIdx until it is deactivated when another MVCD sequence parameter set RBSP becomes the active view MVCD sequence parameter set RBSP for the particular value of VOIdx or when decoding an access unit with VOIdxMax less than or equal to the particular value of VOIdx. A subset sequence parameter set RBSP, with that particular value of seq\_parameter\_set\_id, shall be available to the decoding process prior to its activation. + +An MVCD sequence parameter set RBSP that includes a value of profile\_idc not specified in Annex A or Annex G or Annex H shall not be referred to by activation of a picture parameter set RBSP as the active picture parameter set RBSP or as active view picture parameter set RBSP or as active texture picture parameter set RBSP (using that value of seq\_parameter\_set\_id) or referred to by a buffering period SEI message (using that value of seq\_parameter\_set\_id). An MVCD sequence parameter set RBSP including a value of profile\_idc not specified in Annex A or Annex G or Annex H is ignored in the decoding for profiles specified in Annex A or Annex G or Annex H. + +It is a requirement of bitstream conformance that the following constraints are obeyed: + +- For each particular value of VOIdx, all coded slice NAL units (with nal\_unit\_type equal to 1, 5, 20, or 21) of a coded video sequence shall refer to the same value of seq\_parameter\_set\_id (via the picture parameter set RBSP that is referred to by the value of pic\_parameter\_set\_id). +- The value of seq\_parameter\_set\_id in a buffering period SEI message that is not included in an MVC scalable nesting SEI message shall be identical to the value of seq\_parameter\_set\_id in the picture parameter set RBSP that is referred to by coded slice NAL units with nal\_unit\_type equal to 1 or 5 (via the value of pic\_parameter\_set\_id) in the same access unit. +- The value of seq\_parameter\_set\_id in a buffering period SEI message that is included in an MVC scalable nesting SEI message and is associated with a particular value of VOIdx shall be identical to the value of seq\_parameter\_set\_id in the picture parameter set RBSP that is referred to by coded slice NAL units with nal\_unit\_type equal to 1, 5 or 20 with the particular value of VOIdx (via the value of pic\_parameter\_set\_id) in the same access unit. +- The value of seq\_parameter\_set\_id in a buffering period SEI message that is included in an MVCD scalable nesting SEI message and is associated with a particular value of VOIdx shall be identical to the value of seq\_parameter\_set\_id in the picture parameter set RBSP that is referred to by coded slice NAL units with nal\_unit\_type equal to 21 with the particular value of VOIdx (via the value of pic\_parameter\_set\_id) in the same access unit. + +The active view MVCD sequence parameter set RBSPs for different values of VOIdx may be the same MVCD sequence parameter set RBSP. The active MVCD sequence parameter set RBSP and an active view MVCD sequence parameter set RBSP for a particular value of VOIdx may be the same MVCD sequence parameter set RBSP. + +The active texture MVCD sequence parameter set RBSPs for different values of VOIdx may be the same MVCD sequence parameter set RBSP. The active MVCD sequence parameter set RBSP and an active texture MVCD sequence parameter set RBSP for a particular value of VOIdx may be the same MVCD sequence parameter set RBSP. + +When the active MVCD sequence parameter set RBSP for a coded picture is a sequence parameter set RBSP, any sequence parameter set RBSP in the coded video sequence containing this coded picture and with the value of seq\_parameter\_set\_id for the active MVCD sequence parameter set RBSP shall have the same content as that of the active MVCD sequence parameter set RBSP. + +When the active MVCD sequence parameter set RBSP for a coded picture is a subset sequence parameter set RBSP, any subset sequence parameter set RBSP in the coded video sequence containing this coded picture and with the value of seq\_parameter\_set\_id for the active MVCD sequence parameter set RBSP shall have the same content as that of the active MVCD sequence parameter set RBSP. + +For each particular value of VOIdx, the following applies: + +- When the active texture MVCD sequence parameter set RBSP for a coded picture is a sequence parameter set RBSP, any sequence parameter set RBSP in the coded video sequence containing this coded picture and with the value of seq\_parameter\_set\_id for the active texture MVCD sequence parameter set RBSP shall have the same content as that of the active texture MVCD sequence parameter set RBSP. +- When the active texture MVCD sequence parameter set RBSP for a coded picture is a subset sequence parameter set RBSP, any subset sequence parameter set RBSP in the coded video sequence containing this coded picture and with + +the value of `seq_parameter_set_id` for the active texture MVCD sequence parameter set RBSP shall have the same content as that of the active texture MVCD sequence parameter set RBSP. + +- The active view MVCD sequence parameter set RBSP for a coded picture is a subset sequence parameter set RBSP, and any subset sequence parameter set RBSP in the coded video sequence containing this coded picture and with the value of `seq_parameter_set_id` for the active view MVCD sequence parameter set RBSP shall have the same content as that of the active view MVCD sequence parameter set RBSP. + +NOTE 3 – If picture parameter set RBSPs or MVCD sequence parameter set RBSPs are conveyed within the bitstream, these constraints impose an order constraint on the NAL units that contain the picture parameter set RBSPs or MVCD sequence parameter set RBSPs, respectively. Otherwise (picture parameter set RBSPs or MVCD sequence parameter set RBSPs are conveyed by other means not specified in this Recommendation | International Standard), they must be available to the decoding process in a timely fashion such that these constraints are obeyed. + +When present, a sequence parameter set extension RBSP includes parameters having a similar function to those of a sequence parameter set RBSP. For purposes of establishing constraints on the syntax elements of the sequence parameter set extension RBSP and for purposes of determining activation of a sequence parameter set extension RBSP, the sequence parameter set extension RBSP shall be considered part of the preceding sequence parameter set RBSP with the same value of `seq_parameter_set_id`. When a sequence parameter set RBSP is present that is not followed by a sequence parameter set extension RBSP with the same value of `seq_parameter_set_id` prior to the activation of the sequence parameter set RBSP, the sequence parameter set extension RBSP and its syntax elements shall be considered not present for the active MVCD sequence parameter set RBSP. The contents of sequence parameter set extension RBSPs only apply when the base texture view, which conforms to one or more of the profiles specified in Annex A, of a coded video sequence conforming to one or more profiles specified in Annex H is decoded. Subset sequence parameter set RBSPs shall not be followed by a sequence parameter set extension RBSP. + +NOTE 4 – Sequence parameter sets extension RBSPs are not considered to be part of a subset sequence parameter set RBSP and subset sequence parameter set RBSPs must not be followed by a sequence parameter set extension RBSP. + +For view components with `VOIdx` equal to `VOIdxMax`, all constraints that are expressed on the relationship between the values of the syntax elements (and the values of variables derived from those syntax elements) in MVCD sequence parameter sets and picture parameter sets and other syntax elements are expressions of constraints that apply only to the active MVCD sequence parameter set and the active picture parameter set. For view components with a particular value of `VOIdx` less than `VOIdxMax`, all constraints that are expressed on the relationship between the values of the syntax elements (and the values of variables derived from those syntax elements) in MVCD sequence parameter sets and picture parameter sets and other syntax elements are expressions of constraints that apply only to the active view MVCD sequence parameter set and the active view picture parameter set for the particular value of `VOIdx`. If any MVCD sequence parameter set RBSP having `profile_idc` equal to the value of one of the `profile_idc` values specified in Annex A or Annex G or Annex H is present that is never activated in the bitstream (i.e., it never becomes the active MVCD sequence parameter set or an active view MVCD sequence parameter set), its syntax elements shall have values that would conform to the specified constraints if it were activated by reference in an otherwise-conforming bitstream. If any picture parameter set RBSP is present that is never activated in the bitstream (i.e., it never becomes the active picture parameter set or an active view picture parameter set), its syntax elements shall have values that would conform to the specified constraints if it were activated by reference in an otherwise-conforming bitstream. + +During operation of the decoding process (see clause H.8), for view components with `VOIdx` equal to `VOIdxMax`, the values of parameters of the active picture parameter set and the active MVCD sequence parameter set shall be considered in effect. For view components with a particular value of `VOIdx` less than `VOIdxMax`, the values of the parameters of the active view picture parameter set and the active view MVCD sequence parameter set for the particular value of `VOIdx` shall be considered in effect. For interpretation of SEI messages that apply to the entire access unit or the view component with `VOIdx` equal to `VOIdxMax`, the values of the parameters of the active picture parameter set and the active MVCD sequence parameter set for the same access unit shall be considered in effect unless otherwise specified in the SEI message semantics. For interpretation of SEI messages that apply to view components with a particular value of `VOIdx` less than `VOIdxMax`, the values of the parameters of the active view picture parameter set and the active view MVCD sequence parameter set for the particular value of `VOIdx` for the same access unit shall be considered in effect unless otherwise specified in the SEI message semantics. + +For any active MVCD sequence parameter set or active view MVCD sequence parameter set, part of the syntax elements in the MVC sequence parameter set extension applies only to the depth views referring to this sequence parameter set, while the some other parts of the syntax elements in the MVCD sequence parameter set extension collectively apply to both the depth views referring to this sequence parameter set and the corresponding texture views. More specifically, the view dependency information of the MVCD sequence parameter set extension applies only to the depth views, and the level definitions collectively apply to operation points, each of which contains both depth views and their corresponding texture views. Moreover, the `mvcd_vui_parameters_extension()` applies collectively to both the depth views referring to this MVCD sequence parameter set and the corresponding texture views. The `vui_parameters()` included in the sequence parameter set data syntax structure, if present, apply collectively to both the depth views referring to this sequence parameter set and the corresponding texture views, except for the aspect ratio information and the bitstream restriction + +information, if present, which apply only to the depth views referring to this MVCD sequence parameter set. The aspect ratio information and the bitstream restriction information for the texture views may be present in the `vui_parameters()` syntax structure included in an MVC sequence parameter set. + +#### **H.7.4.1.2.2 Order of access units and association to coded video sequences** + +The specification of clause G.7.4.1.2.2 apply. + +#### **H.7.4.1.2.3 Order of NAL units and coded pictures and association to access units** + +The specification of clause G.7.4.1.2.3 applies with the following modifications. + +NOTE – Some bitstreams that conform to one or more profiles specified in this annex do not conform to any profile specified in Annex A (prior to operation of the base view extraction process specified in clause H.8.5.4). As specified in clauses 7.4.1 and 7.4.1.2.3 for the profiles specified in Annex A, NAL units with `nal_unit_type` equal to 21 are classified as non-VCL NAL units that must be preceded within each access unit by at least one NAL unit with `nal_unit_type` in the range of 1 to 5, inclusive. For this reason, any bitstream that conforms to one or more profiles specified in this annex does not conform to any profile specified in Annex A when it contains any of the following: + +- any access unit that does not contain any NAL units with `nal_unit_type` equal to 1 or 5, but contains one or more NAL units with `nal_unit_type` equal to 6, 7, 8, 9, or 15 +- any access unit in which one or more NAL units with `nal_unit_type` equal to 7, 8, or 15 is present after the last NAL unit in the access unit with `nal_unit_type` equal to 1 or 5. + +The association of VCL NAL units to primary or redundant coded pictures is specified in clause H.7.4.1.2.5. + +The constraints for the detection of the first VCL NAL unit of a primary coded picture are specified in clause H.7.4.1.2.4. + +The constraint expressed in clause G.7.4.1.2.3 on the order of a buffering period SEI message is replaced by the following constraints. + +- When an SEI NAL unit containing a buffering period SEI message is present, the following applies: + - If the buffering period SEI message is the only buffering period SEI message in the access unit and it is not included in an MVC scalable nesting SEI message or an MVCD scalable nesting SEI message, the buffering period SEI message shall be the first SEI message payload of the first SEI NAL unit in the access unit. + - Otherwise (the buffering period SEI message is not the only buffering period SEI message in the access unit or it is included in an MVC scalable nesting SEI message or it is included in an MVCD scalable nesting SEI message), the following constraints are specified: + - When a buffering period SEI message that is not included in either an MVC scalable nesting SEI message or an MVCD scalable nesting SEI message is present, this buffering period SEI message shall be the only SEI message payload of the first SEI NAL unit in the access unit. + - An MVC scalable nesting SEI message that includes a buffering period SEI message shall not include any other SEI messages and shall be the only SEI message inside the SEI NAL unit. + - An MVCD scalable nesting SEI message that includes a buffering period SEI message shall not include any other SEI messages and shall be the only SEI message inside the SEI NAL unit. + - All SEI NAL units that precede an SEI NAL unit that contains an MVC scalable nesting SEI message with a buffering period SEI message as payload, or an MVCD scalable nesting SEI message with a buffering period SEI message as payload in an access unit shall only contain buffering period SEI messages or MVC scalable nesting SEI messages with a buffering period SEI message as payload, or MVCD scalable nesting SEI messages with a buffering period SEI message. + +#### **H.7.4.1.2.4 Detection of the first VCL NAL unit of a primary coded picture** + +The specification of clause G.7.4.1.2.4 applies. + +#### **H.7.4.1.2.5 Order of VCL NAL units and association to coded pictures** + +The specification of clause G.7.4.1.2.5 applies with following modifications. + +Each VCL NAL unit is part of a coded picture. + +Let `voIdx` be the value of `VOIdx` of any particular VCL NAL unit. The order of the VCL NAL units within a coded picture is constrained as follows: + +- For all VCL NAL units following this particular VCL NAL unit, the value of `VOIdx` shall be greater than or equal to `voIdx`. +- All VCL NAL units for a depth view component, if present, shall follow any VCL NAL unit of a texture view component with a same value of `VOIdx`. + +For each set of VCL NAL units within a texture or depth view component, the following applies: + +- If arbitrary slice order, as specified in Annex A, clause G.10 or clause H.10, is allowed, coded slice NAL units of a view component may have any order relative to each other. +- Otherwise (arbitrary slice order is not allowed), coded slice NAL units of a slice group shall not be interleaved with coded slice NAL units of another slice group and the order of coded slice NAL units within a slice group shall be in the order of increasing macroblock address for the first macroblock of each coded slice NAL unit of the same slice group. + +The following applies: + +- If a coded texture view component with a particular `view_id` is the first field view component of a complementary field pair, the depth view component with the same `view_id` value, if present in the access unit, shall be a coded frame view component or the first field view component of a complementary field pair. +- Otherwise, if a coded texture view component with a particular `view_id` is the second field view component of a complementary field pair, the depth view component with the same `view_id` value, if present in the access unit, shall be the second field view component of a complementary field pair. +- Otherwise, if a coded texture view component with a particular `view_id` is a non-paired field, the depth view component with the same `view_id` value, if present in the access unit, shall be a coded frame view component or a non-paired field. +- Otherwise (a coded texture view component with a particular `view_id` is a coded frame), the depth view component with the same `view_id` value, if present in the access unit, shall be a coded frame view component. + +NAL units having `nal_unit_type` equal to 12 may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having `nal_unit_type` equal to 0 or in the range of 24 to 31, inclusive, which are unspecified, may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having `nal_unit_type` in the range of 22 to 23, inclusive, which are reserved, shall not precede the first VCL NAL unit of the primary coded picture within the access unit (when specified in the future by ITU-T | ISO/IEC). + +#### **H.7.4.2 Raw byte sequence payloads and RBSP trailing bits semantics** + +##### **H.7.4.2.1 Sequence parameter set RBSP semantics** + +The semantics specified in clause 7.4.2.1 apply. + +###### **H.7.4.2.1.1 Sequence parameter set data semantics** + +The semantics specified in clause G.7.4.2.1.1 apply with the substitution of MVCD sequence parameter set for MVC sequence parameter set. All constraints specified in clause G.7.4.2.1.1 apply only to the texture view components for which the MVCD sequence parameter set is the active texture MVC sequence parameter set or to the depth view components for which the MVCD sequence parameter set is the active view MVC sequence parameter set as specified in clause H.7.4.1.2.1. + +###### **H.7.4.2.1.1.1 Scaling list semantics** + +The semantics specified in clause G.7.4.2.1.1.1 apply. + +###### **H.7.4.2.1.2 Sequence parameter set extension RBSP semantics** + +The semantics specified in clause 7.4.2.1.2 apply. Additionally, the following applies. + +Sequence parameter set extension RBSPs can only follow sequence parameter set RBSPs in decoding order. Subset sequence parameter set RBSPs shall not be followed by a sequence parameter set extension RBSP. The contents of sequence parameter set extension RBSPs only apply when the base view, which conforms to one or more of the profiles specified in Annex A, of a coded video sequence conforming to one or more profiles specified in this annex is decoded. + +###### **H.7.4.2.1.3 Subset sequence parameter set RBSP semantics** + +The semantics specified in clause 7.4.2.1.3 apply with the following additions. + +**`mvcd_vui_parameters_present_flag`** equal to 0 specifies that the syntax structure `mve_vui_parameters_extension()` corresponding to MVCD VUI parameters extension is not present. `mvcd_vui_parameters_present_flag` equal to 1 specifies that the syntax structure `mve_vui_parameters_extension()` is present and referred to as MVCD VUI parameters extension. + +**texture\_vui\_parameters\_present\_flag** equal to 0 specifies that the syntax structure mvc\_vui\_parameters\_extension() corresponding to MVCD texture sub-bitstream VUI parameters extension is not present. texture\_vui\_parameters\_present\_flag equal to 1 specifies that the syntax structure mvc\_vui\_parameters\_extension() is present and referred to as MVCD texture sub-bitstream VUI parameters extension. + +#### H.7.4.2.1.4 Sequence parameter set MVCD extension semantics + +The semantics specified in clause G.7.4.2.1.4 apply with the substitution of texture view component or depth view component for view component and with the following additions: + +**depth\_view\_present\_flag[ i ]** equal to 0 specifies that there is no depth view having a view\_id equal to view\_id[ i ] and VOIdx equal to i. depth\_view\_present\_flag[ i ] equal to 1 specifies that there is a depth view having a view\_id equal to view\_id[ i ]. + +**texture\_view\_present\_flag[ i ]** equal to 0 specifies that there is no texture view having a view\_id equal to view\_id[ i ] and VOIdx equal to i. texture\_view\_present\_flag[ i ] equal to 1 specifies that there is a texture view having a view\_id equal to view\_id[ i ] and VOIdx equal to i. When depth\_view\_present\_flag[ i ] is equal to 0, texture\_view\_present\_flag[ i ] shall be equal to 1. + +num\_anchor\_refs\_10[ i ], anchor\_ref\_10[ i ][ j ], num\_anchor\_refs\_11[ i ], anchor\_ref\_11[ i ][ j ], num\_non\_anchor\_refs\_10[ i ], non\_anchor\_ref\_10[ i ][ j ], num\_non\_anchor\_refs\_11[ i ], and non\_anchor\_ref\_11[ i ][ j ] apply to depth view components. + +**applicable\_op\_depth\_flag[ i ][ j ][ k ]** equal to 0 indicates that the depth view with view\_id equal to applicable\_op\_target\_view\_id[ i ][ j ][ k ] is not included in the j-th operation point. applicable\_op\_depth\_flag[ i ][ j ][ k ] equal to 1 indicates that the depth view with view\_id equal to applicable\_op\_target\_view\_id[ i ][ j ][ k ] is included in the j-th operation point. + +**applicable\_op\_texture\_flag[ i ][ j ][ k ]** equal to 0 indicates that the texture view with view\_id equal to applicable\_op\_target\_view\_id[ i ][ j ][ k ] is not included in the j-th operation point. applicable\_op\_texture\_flag[ i ][ j ][ k ] equal to 1 indicates that the texture view with view\_id equal to applicable\_op\_target\_view\_id[ i ][ j ][ k ] is included in the j-th operation point. When applicable\_op\_depth\_flag[ i ][ j ][ k ] is equal to 0, applicable\_op\_texture\_flag[ i ][ j ][ k ] shall be equal to 1. + +**applicable\_op\_num\_texture\_views\_minus1[ i ][ j ]** plus 1 specifies the number of texture views required for decoding the target output views corresponding to the j-th operation point to which the level indicated by level\_idc[ i ] applies. The number of texture views specified by applicable\_op\_num\_views\_minus1 includes the texture views of the target output views and the texture views that the target output views depend on. The value of applicable\_op\_num\_texture\_views\_minus1[ i ][ j ] shall be in the range of 0 to 1023, inclusive. + +**applicable\_op\_num\_depth\_views[ i ][ j ]** specifies the number of depth views required for decoding the target output views corresponding to the j-th operation point to which the level indicated by level\_idc[ i ] applies. The number of depth views specified by applicable\_op\_num\_depth\_views\_minus1 includes the depth views of the target output views and the depth views that the depth views of the target output views depend on. The value of applicable\_op\_num\_depth\_views\_minus1[ i ][ j ] shall be in the range of 0 to 1023, inclusive. + +All sequence parameter set MVCD extensions that are included in the active view MVCD sequence parameter set RBSPs of one coded video sequence shall be identical. + +#### H.7.4.2.2 Picture parameter set RBSP semantics + +The semantics specified in clause G.7.4.2.2 apply with substituting MVCD sequence parameter set for MVC sequence parameter set. All constraints specified in clause G.7.4.2.2 apply only to the texture or depth view components for which the picture parameter set is the active picture parameter set or the active view picture parameter set or the active texture picture parameter set as specified in clause H.7.4.1.2.1. + +#### H.7.4.2.3 Supplemental enhancement information RBSP semantics + +The semantics specified in clause G.7.4.2.3 apply. + +##### H.7.4.2.3.1 Supplemental enhancement information message semantics + +The semantics specified in clause G.7.4.2.3.1 apply. + +#### H.7.4.2.4 Access unit delimiter RBSP semantics + +The semantics specified in clause G.7.4.2.4 apply. + +NOTE – The value of primary\_pic\_type applies to the slice\_type values in all slice headers of the primary coded picture, including the slice\_type syntax elements in all NAL units with nal\_unit\_type equal to 1, 5, 20 or 21. NAL units with nal\_unit\_type equal to 2 are not present in bitstreams conforming to any of the profiles specified in this annex. + +#### **H.7.4.2.5 End of sequence RBSP semantics** + +The semantics specified in clause G.7.4.2.5 apply. + +#### **H.7.4.2.6 End of stream RBSP semantics** + +The semantics specified in clause G.7.4.2.6 apply. + +#### **H.7.4.2.7 Filler data RBSP semantics** + +The semantics specified in clause G.7.4.2.7 apply with the following modifications. + +Filler data NAL units shall be considered to contain the syntax elements `priority_id`, `view_id`, and `temporal_id` with values that are inferred as follows: + +1. Let `prevMvcNalUnit` be the most recent NAL unit in decoding order that has `nal_unit_type` equal to 14, 20 or 21. +NOTE – The most recent NAL unit in decoding order with `nal_unit_type` equal to 14, 20 or 21 always belongs to the same access unit as the filler data NAL unit. +2. The values of `priority_id`, `view_id`, and `temporal_id` for the filler data NAL unit are inferred to be equal to the values of `priority_id`, `view_id`, and `temporal_id`, respectively, of the NAL unit `prevMvcNalUnit`. + +#### **H.7.4.2.8 Slice layer without partitioning RBSP semantics** + +The semantics specified in clause G.7.4.2.8 apply. + +#### **H.7.4.2.9 Slice data partition RBSP semantics** + +Slice data partition syntax is not present in bitstreams conforming to one or more of the profiles specified in this annex. + +#### **H.7.4.2.10 RBSP slice trailing bits semantics** + +The semantics specified in G.7.4.2.10 apply. + +#### **H.7.4.2.11 RBSP trailing bits semantics** + +The semantics specified in clause G.7.4.2.11 apply. + +#### **H.7.4.2.12 Prefix NAL unit RBSP semantics** + +The semantics specified in clause G.7.4.2.12 apply. + +#### **H.7.4.2.13 Slice layer extension RBSP semantics** + +The semantics specified in clause G.7.4.2.13 apply. + +### **H.7.4.3 Slice header semantics** + +The semantics specified in clause G.7.4.3 apply with the substitution of texture view component (for `nal_unit_type` equal to 1, 5, and 20) or depth view component (for `nal_unit_type` equal to 21 and `avc_3d_extension_flag` equal to 0) for view component and with the following modifications. + +When `nal_unit_type` is equal to 1, 5, or 20, all constraints specified in clause G.7.4.3 apply only to the texture view components with the same value of `VOIdx`. When `nal_unit_type` is equal to 21 and `avc_3d_extension_flag` is equal to 0, all constraints specified in clause G.7.4.3 apply only to the depth view components with the same value of `VOIdx`. + +The value of the following MVCD sequence parameter set syntax elements shall be the same across all coded slice NAL units of `nal_unit_type` equal to 1, 5, and 20 of an access unit: `chroma_format_idc`. + +The value of the following slice header syntax elements shall be the same across all coded slice NAL units of `nal_unit_type` equal to 1, 5, and 20 of an access unit: `field_pic_flag` and `bottom_field_flag`. + +The value of the following slice header syntax elements shall be the same across all coded slice NAL units of `nal_unit_type` equal to 21 of an access unit: `field_pic_flag` and `bottom_field_flag`. + +#### **H.7.4.3.1 Reference picture list modification semantics** + +The semantics specified in clause G.7.4.3.1 apply. + +##### **H.7.4.3.1.1 Reference picture list MVC modification semantics** + +The semantics specified in clause G.7.4.3.1.1 apply. + +#### **H.7.4.3.2 Prediction weight table semantics** + +The semantics specified in clause G.7.4.3.2 apply. + +### **H.7.4.3.3 Decoded reference picture marking semantics** + +The semantics specified in clause 7.4.3.3 apply to each view independently, with "sequence parameter set" being replaced by "MVCD sequence parameter set", and "primary coded picture" being replaced by "texture view component" for nal\_unit\_type equal to 1, 5, and 20, and by "depth view component" for nal\_unit\_type equal to 21. + +### **H.7.4.4 Slice data semantics** + +The semantics specified in clause G.7.4.4 apply. + +### **H.7.4.5 Macroblock layer semantics** + +The semantics specified in clause G.7.4.5 apply. + +#### **H.7.4.5.1 Macroblock prediction semantics** + +The semantics specified in clause G.7.4.5.1 apply. + +#### **H.7.4.5.2 Sub-macroblock prediction semantics** + +The semantics specified in clause G.7.4.5.2 apply. + +#### **H.7.4.5.3 Residual data semantics** + +The semantics specified in clause G.7.4.5.3 apply. + +##### **H.7.4.5.3.1 Residual luma semantics** + +The semantics specified in clause G.7.4.5.3.1 apply. + +##### **H.7.4.5.3.2 Residual block CAVLC semantics** + +The semantics specified in clause G.7.4.5.3.2 apply. + +##### **H.7.4.5.3.3 Residual block CABAC semantics** + +The semantics specified in clause G.7.4.5.3.3 apply. + +## **H.8 MVCD decoding process** + +This clause specifies the decoding process for an access unit of a coded video sequence conforming to one or more of the profiles specified in this annex. Specifically, this clause specifies how the decoded picture with multiple texture view components and multiple depth view components is derived from syntax elements and global variables that are derived from NAL units in an access unit when the decoder is decoding the operation point identified by the target temporal level and the target output texture and depth views. + +The decoding process is specified such that all decoders shall produce numerically identical results for the target output texture and depth views. Any decoding process that produces identical results for the target output texture and depth views to the process described here conforms to the decoding process requirements of this Recommendation | International Standard. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the decoding process specified in this clause and all child processes invoked from the process specified in this clause are the syntax elements and derived upper-case variables for the current access unit. + +The target output texture and depth views are either specified by external means not specified in this Specification, or, when not specified by external means, there shall be one target output texture view which is the base texture view. + +NOTE – The association of VOIdx values to view\_id values according to the decoding process of clause H.8 may differ from that of the decoding process of clause G.8. + +A target output view may include only a texture view, only a depth view, or both the texture view and the depth view, which have the same view\_id value. + +All sub-bitstreams that can be derived using the sub-bitstream extraction process with depthPresentFlagTarget equal to 0 or 1, pIdTarget equal to any value in the range of 0 to 63, inclusive, tldTarget equal to any value in the range of 0 to 7, inclusive, viewIdTargetList consisting of any one or more viewIdTarget's identifying the views in the bitstream as inputs as specified in clause H.8.5 shall result in a set of coded video sequences, with each coded video sequence conforming to one or more of the profiles specified in Annex A, Annex G and Annex H. + +Let vOIdxList be a list of integer values specifying the VOIdx values of the view components of the access unit. The variable VOIdxMax is set equal to the maximum value of the entries in the list vOIdxList, and the variable vOIdxMin is + +set to the minimum value of the entries in the list vIdxList. When the current access unit is an anchor access unit, the variable VOIdxMin is set to vIdxMin. + +The MVCD video decoding process specified in this clause is repeatedly invoked for each texture and depth view component with VOIdx from vIdxMin to VOIdxMax, inclusive, which is present in the list vIdxList, in increasing order of VOIdx and in decoding order of texture or depth view components as specified in clause H.7.4.1.2.5. + +Outputs of the MVCD video decoding process are decoded samples of the current primary coded picture including all decoded texture and depth view components of the target output texture and depth views. + +For each texture view component and each depth view component, the specifications in clause G.8 apply, with the decoding processes for picture order count, reference picture lists construction and decoded reference picture marking being modified in clauses H.8.1, H.8.2, H.8.3, and H.8.4, respectively. The MVCD inter prediction and inter-view prediction process is specified in clause H.8.4. + +#### **H.8.1 MVCD decoding process for picture order count** + +The specifications in clause 8.2.1 apply independently for each texture view or depth view. + +#### **H.8.2 MVC decoding process for reference picture lists construction** + +The specification of clause G.8.2 apply with substituting "view component" as either "texture view component" or "depth view component", and "frame view component" as either "depth frame view component" or "texture frame view component", and "field view component" as "texture field view component" or "depth field view component". + +Additionally, an inter-view reference component or the inter-view only reference component is identified by the view\_id and a depth view component when the current slice is a part of a coded depth view component or a texture view component if the current slice is a part of a coded texture view component. + +##### **H.8.2.1 Initialization process for reference picture list for inter-view prediction references** + +The specifications of clause G.8.2.1 apply. + +##### **H.8.2.2 Modification process for reference picture lists** + +The specifications of clause G.8.2.2 apply. + +###### **H.8.2.2.1 Modification process of reference picture lists for short-term reference pictures for inter prediction** + +The specifications of clause G.8.2.2.1 apply. + +###### **H.8.2.2.2 Modification process of reference picture lists for long-term reference pictures for inter prediction** + +The specifications of clause G.8.2.2.2 apply. + +###### **H.8.2.2.3 Modification process for reference picture lists for inter-view prediction references** + +The specifications of clause G.8.2.2.3 apply. + +#### **H.8.3 MVCD decoded reference picture marking process** + +The specifications of clause G.8.3 apply. Additionally, the following applies. + +The process specified in this clause is invoked for a particular texture view or depth view with view order index VOIdx. The specifications in clause G.8.3 apply with "view component" being replaced by either "texture view component" or "depth view component", "frame view component" being replaced by either "texture frame view component" or "depth frame view component", and "field view component" being replaced by either "texture field view component" or "depth field view component". During the invocation of the process for a particular texture view, only texture view components of the particular view are considered. During the invocation of the process for a particular depth view, only depth view components of the particular view are considered. The marking of view components of other views is not changed. + +NOTE – A texture view component of a picture may have a different marking status than other texture view components of the same picture. A depth view component of a picture may have a different marking status than other depth view components of the same picture. A texture view component of a picture may have a different marking status than a depth view component. + +#### **H.8.4 MVCD inter prediction and inter-view prediction process** + +The specifications of clause G.8.4 apply. + +#### **H.8.5 Specification of sub-bitstreams** + +The specifications of clause G.8.5 apply. + +#### H.8.5.1 Derivation process for required anchor view components + +When invoked for a depth view, the specification of clause G.8.5.1 apply with substituting "view component" with "depth view component" and "view" with "depth view". + +When invoked for a texture view, the specification of clause G.8.5.1 apply with substituting "view component" with "texture view component" and "view" with "texture view". + +#### H.8.5.2 Derivation process for required non-anchor view components + +When invoked for a depth view, the specification of clause G.8.5.2 apply with substituting "view component" with "depth view component" and "view" with "depth view". + +When invoked for a texture view, the specification of clause G.8.5.2 apply with substituting "view component" with "texture view component" and "view" with "texture depth view". + +#### H.8.5.3 Sub-bitstream extraction process + +It is requirement of bitstream conformance that any sub-bitstream that is the output of the process specified in this clause with depthPresentFlagTarget equal to 0 or 1, pldTarget equal to any value in the range of 0 to 63, inclusive, tldTarget equal to any value in the range of 0 to 7, inclusive, viewIdTargetList consisting of any one or more values of viewIdTarget identifying the views in the bitstream, shall be conforming to this Recommendation | International Standard. + +NOTE 1 – A conforming bitstream contains one or more coded slice NAL units with priority\_id equal to 0 and temporal\_id equal to 0. + +NOTE 2 – It is possible that not all operation points of sub-bitstreams resulting from the sub-bitstream extraction process have an applicable level\_idc or level\_idc[i]. In this case, each coded video sequence in a sub-bitstream must still conform to one or more of the profiles specified in Annex A, Annex G and Annex H, but may not satisfy the level constraints specified in clauses A.3, G.10.2 and H.10.2, respectively. + +Inputs to this process are: + +- a variable depthPresentFlagTarget (when present), +- a variable pldTarget (when present), +- a variable tldTarget (when present), +- a list viewIdTargetList consisting of one or more values of viewIdTarget (when present). +- a list viewIdDepthTargetList consisting of one or more value of viewIdDepthTarget (when present). + +Outputs of this process are a sub-bitstream and a list of VOIdx values VOIdxList. + +When depthPresentFlagTarget is not present as input to this clause, depthPresentFlagTarget is inferred to be equal to 0. + +When pldTarget is not present as input to this clause, pldTarget is inferred to be equal to 63. + +When tldTarget is not present as input to this clause, tldTarget is inferred to be equal to 7. + +When viewIdTargetList is not present as input to this clause, there shall be one value of viewIdTarget inferred in viewIdTargetList and the value of viewIdTarget is inferred to be equal to view\_id of the base view. + +When viewIdDepthTargetList is not present as input to this clause, the viewIdDepthTargetList is inferred to be identical to viewIdTargetList. viewIdDepthTargetList shall not be present as input if depthPresentFlagTarget is equal to 0. + +The sub-bitstream is derived by applying the following operations in sequential order: + +1. Let VOIdxList be empty and minVOIdx be the VOIdx value of the base view. +2. For each value of viewIdTarget included in viewIdTargetList, invoke the process specified in clause H.8.5.1 for texture views with the viewIdTarget as input. +3. If depthPresentFlagTarget is equal to 1, for each value of viewIdTarget included in viewIdDepthTargetList, invoke the process specified in clause H.8.5.1 for depth views with the viewIdTarget as input. +4. For each value of viewIdTarget included in viewIdTargetList, invoke the process specified in clause H.8.5.2 for texture views with the value of viewIdTarget as input. +5. If depthPresentFlagTarget is equal to 1, for each value of viewIdTarget included in viewIdDepthTargetList, invoke the process specified in clause H.8.5.2 for depth views with the viewIdTarget as input. +6. Mark all VCL NAL units and filler data NAL units for which any of the following conditions are true as "to be removed from the bitstream": + +- priority\_id is greater than pIdTarget, + - temporal\_id is greater than tIdTarget, + - nal\_unit\_type is not equal to 21 and view\_id is not in the viewIdTargetList, + - nal\_unit\_type is equal to 21 and view\_id is not in the viewIdDepthTargetList, + - nal\_unit\_type is equal to 21 and depthPresentFlagTarget is equal to 0. +7. Remove all access units for which all VCL NAL units are marked as "to be removed from the bitstream". + 8. Remove all VCL NAL units and filler data NAL units that are marked as "to be removed from the bitstream". + 9. When VOIdxList contains only one value of VOIdx that is equal to minVOIdx, remove the following NAL units: + - all NAL units with nal\_unit\_type equal to 14 or 15, + - all NAL units with nal\_unit\_type equal to 6 in which the first SEI message has payloadType in the range of 36 to 44, inclusive, or equal to 46, or in the range of 48 to 53, inclusive. + +NOTE 3 – When VOIdxList contains only one value of VOIdx equal to minVOIdx, the sub-bitstream contains only the base view or only a temporal subset of the base view. + +10. Remove all NAL units with nal\_unit\_type equal to 6 in which the first SEI message has payloadType equal to 0 or 1, or the first SEI message has payloadType equal to 37 (MVC scalable nesting SEI message) and operation\_point\_flag in the first SEI message is equal to 1. + +NOTE 4 – The buffering period SEI and picture timing SEI messages, when not nested or nested in the MVC scalable nesting SEI message, apply for a sub-bitstream obtained with the sub-bitstream extraction process of clause G.8.5.3, which does not process NAL units of nal\_unit\_type equal to 21. + +11. When depthPresentFlagTarget is equal to 0, the following applies in sequential order. + - Replace each NAL unit with nal\_unit\_type equal to 6 in which payloadType indicates an MVCD scalable nesting SEI message with sei\_op\_texture\_only\_flag equal to 0 with a NAL unit containing an MVC scalable nesting SEI message with the same values of num\_view\_components\_op\_minus1, sei\_op\_view\_id[ i ] and sei\_op\_temporal\_id and the same nested SEI messages. + - Remove all NAL units with nal\_unit\_type equal to 6 in which payloadType indicates an MVCD texture scalable nesting SEI message. + - The following applies for each active texture MVCD sequence parameter set RBSP. + - Replace mvc\_vui\_parameters\_extension() syntax structure in an active texture MVCD sequence parameter set RBSPs with the mvc\_vui\_parameters\_extension() syntax structure of the MVCD texture sub-bitstream VUI parameters extension, if both mvc\_vui\_parameters\_extension() syntax structures apply to the same views. + - Otherwise, remove mvc\_vui\_parameters\_extension() syntax structure in an active texture MVCD sequence parameter set RBSP. + - Remove all NAL units with nal\_unit\_type equal to 6 in which the first SEI message has payloadType in the range of 48 to 53, inclusive. +12. Let maxTId be the maximum temporal\_id of all the remaining VCL NAL units. Remove all NAL units with nal\_unit\_type equal to 6 that only contain SEI messages that are part of an MVC scalable nesting SEI message or MVCD scalable nesting SEI message with any of the following properties: + - operation\_point\_flag is equal to 0 and all\_view\_components\_in\_aus\_flag is equal to 0 and none of sei\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_minus1, inclusive, corresponds to a VOIdx value included in VOIdxList, + - operation\_point\_flag is equal to 1 and either sei\_op\_temporal\_id is greater than maxTId or the list of sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, is not a subset of viewIdTargetList (i.e., it is not true that sei\_op\_view\_id[ i ] for any i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, is equal to a value in viewIdTargetList). +13. Remove each view scalability information SEI message and each operation point not present SEI message, when present. +14. When VOIdxList does not contain a value of VOIdx equal to minVOIdx, the view with VOIdx equal to the minimum VOIdx value included in VOIdxList is converted to the base view of the extracted sub-bitstream. + +NOTE 5 – When VOIdxList does not contain a value of VOIdx equal to minVOIdx, the resulting sub-bitstream according to the operation steps 1-9 above does not contain a base view that conforms to one or more profiles specified in Annex A. In this case, by this operation step, the remaining view with the new minimum VOIdx value is converted to be the new base view that conforms to one or more profiles specified in Annex A and Annex G. + +#### H.8.5.4 Specification of the base view bitstream + +A bitstream that conforms to one or more profiles as specified in this annex shall contain a base view bitstream that conforms to one or more of the profiles specified in Annex A. This base view bitstream is derived by invoking the sub-bitstream extraction process as specified in clause H.8.5.3 with no input and the base view bitstream being the output. + +NOTE – Although all multiview bitstreams that conform to one or more of the profiles specified in this annex contain a base view bitstream that conforms to one or more of the profiles specified in Annex A, the complete multiview bitstream (prior to operation of the base view extraction process specified in this clause) may not conform to any profile specified in Annex A. + +#### H.8.5.5 Specification of the stereoscopic texture bitstream + +A bitstream that conforms to a profile as specified in this annex shall contain at least one sub-bitstream that conforms to one or more of the profiles specified in Annex G with number of views equal to 2. This stereoscopic texture bitstream is derived by invoking the sub-bitstream extraction process as specified in clause H.8.5.3 with depthPresentFlagTarget equal to 0 and viewIdTargetList containing the view\_id values of the base view and a non-base view, the texture of which does not depend on any other non-base view for decoding. + +### H.9 Parsing process + +The specifications in clause 9 apply. + +### H.10 Profiles and levels + +The specifications in Annex G apply. Additional profiles and specific values of profile\_idc are specified in the following. + +The profiles that are specified in clause H.10.1 are also referred to as the profiles specified in Annex H. + +#### H.10.1 Profiles + +All constraints for picture parameter sets that are specified in the following are constraints for picture parameter sets that become the active picture parameter set or an active view picture parameter set inside the bitstream. All constraints for MVCD sequence parameter sets that are specified in the following are constraints for MVCD sequence parameter sets that become the active MVCD sequence parameter set or an active view MVCD sequence parameter set inside the bitstream. + +##### H.10.1.1 Multiview Depth High profile + +Bitstreams conforming to the Multiview Depth High profile shall obey the following constraints: + +- The base view bitstream as specified in clause H.8.5.4 shall obey all constraints of the High profile specified in clause A.2.4 and all active sequence parameter sets shall fulfil one of the following conditions: + - profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1, + - profile\_idc is equal to 100. +- The sub-bitstream of stereoscopic texture bitstream as specified in clause H.8.5.5 shall obey all constraints of the Stereo High profile specified in clause G.10.2 and all active MVC sequence parameter sets shall fulfil one of the following conditions: + - profile\_idc is equal to 128, + - profile\_idc is equal to 118 and constraint\_set5\_flag is equal to 1, + - profile\_idc is equal to 100, + - profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1. +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain nal\_unit\_type values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0 only. +- Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0 only. + +- When `frame_mbs_only_flag` is equal to 1 in an active sequence parameter set for a texture view, `frame_mbs_only_flag` shall be equal to 1 in the active sequence parameter set for the depth view having the same `view_id`. +- When `frame_mbs_only_flag` is equal to 0 in an active sequence parameter set for a depth view, `mb_adaptive_frame_field_flag` shall be equal to 0. +- MVCD sequence parameter sets for the depth views shall have `chroma_format_idc` equal to 0 only. +- MVCD sequence parameter sets shall have `bit_depth_luma_minus8` equal to 0 only. +- MVCD sequence parameter sets shall have `bit_depth_chroma_minus8` equal to 0 only. +- MVCD sequence parameter sets shall have `qpprime_y_zero_transform_bypass_flag` equal to 0 only. +- For each access unit, the value of `level_idc` for all active view MVCD sequence parameter set RBSPs shall be the same as the value of `level_idc` for the active MVCD sequence parameter set RBSP. +- The level constraints specified for the Multiview Depth High profile in clause H.10.2 shall be fulfilled. + +Conformance of a bitstream to the Multiview Depth High profile is indicated by `profile_idc` being equal to 138. + +Decoders conforming to the Multiview Depth High profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- All active MVCD sequence parameter sets have one or more of the following conditions fulfilled: + - `profile_idc` is equal to 138, + - `profile_idc` is equal to 128, + - `profile_idc` is equal to 118 and `constraint_set5_flag` is equal to 1, + - `profile_idc` is equal to 100, + - `profile_idc` is equal to 77 or `constraint_set1_flag` is equal to 1. +- All active MVCD sequence parameter sets have one or more of the following conditions fulfilled: + - `level_idc` or (`level_idc` and `constraint_set3_flag`) represent a level less than or equal to the specific level, + - `level_idc[ i ]` or (`level_idc[ i ]` and `constraint_set3_flag`) represent a level less than or equal to the specific level. + +#### H.10.1.2MFC Depth High profile + +Bitstreams conforming to the MFC Depth High profile shall obey the following constraints: + +- The base view bitstream as specified in clause H.8.5.4 shall obey all constraints of the High profile specified in clause A.2.4, and all active sequence parameter sets shall fulfil one of the following conditions: + - `profile_idc` is equal to 77 or `constraint_set1_flag` is equal to 1, + - `profile_idc` is equal to 100. +- The sub-bitstream of stereoscopic texture bitstream, as specified in clause H.8.5.5, shall obey all constraints of the MFC High profile specified in clause G.10.1.3 and all active MVC sequence parameter sets shall fulfil one of the following conditions: + - `profile_idc` is equal to 134, + - `profile_idc` is equal to 100, + - `profile_idc` is equal to 77 or `constraint_set1_flag` is equal to 1. +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain `nal_unit_type` values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have `num_slice_groups_minus1` equal to 0 only. +- Picture parameter sets shall have `redundant_pic_cnt_present_flag` equal to 0 only. +- When `frame_mbs_only_flag` is equal to 1 in an active sequence parameter set for a texture view, `frame_mbs_only_flag` shall be equal to 1 in the active sequence parameter set for the depth view having the same `view_id`. + +- When `frame_mbs_only_flag` is equal to 0 in an active sequence parameter set for a depth view, `mb_adaptive_frame_field_flag` shall be equal to 0. +- MVCD sequence parameter sets for the depth views shall have `chroma_format_idc` equal to 0 only. +- MVCD sequence parameter sets shall have `bit_depth_luma_minus8` equal to 0 only. +- MVCD sequence parameter sets shall have `bit_depth_chroma_minus8` equal to 0 only. +- MVCD sequence parameter sets shall have `qpprime_y_zero_transform_bypass_flag` equal to 0 only. +- For each access unit, the value of `level_idc` for all active view MVCD sequence parameter set RBSPs shall be the same as the value of `level_idc` for the active MVCD sequence parameter set RBSP. +- The level constraints specified for the MFC Depth High profile in clause H.10.2 shall be fulfilled. + +Conformance of a bitstream to the MFC Depth High profile is indicated by `profile_idc` being equal to 135. + +Decoders conforming to the MFC Depth High profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- All active MVCD sequence parameter sets have one or more of the following conditions fulfilled: + - `profile_idc` is equal to 135, + - `profile_idc` is equal to 138, + - `profile_idc` is equal to 134, + - `profile_idc` is equal to 128, + - `profile_idc` is equal to 118 and `constraint_set5_flag` is equal to 1, + - `profile_idc` is equal to 100, + - `profile_idc` is equal to 77 or `constraint_set1_flag` is equal to 1. +- All active MVCD sequence parameter sets have one or more of the following conditions fulfilled: + - `level_idc` or (`level_idc` and `constraint_set3_flag`) represent a level less than or equal to the specific level, + - `level_idc[ i ]` or (`level_idc[ i ]` and `constraint_set3_flag`) represent a level less than or equal to the specific level. + +## H.10.2 Levels + +The following is specified for expressing the constraints in this clause: + +- Let access unit `n` be the `n`-th access unit in decoding order with the first access unit being access unit 0. +- Let picture `n` be the primary coded picture or the corresponding decoded picture of access unit `n`. + +Let the variable `fR` be derived as follows: + +- If the level number is equal to 6.0, 6.1, or 6.2, `fR` is set equal to $1 \div 300$ . +- Otherwise, if picture `n` is a frame, `fR` is set equal to $1 \div 172$ . +- Otherwise (picture `n` is a field), `fR` is set equal to $1 \div (172 * 2)$ . + +The value of `mvcScaleFactor` is set equal to 2. + +The value of `mvcdScaleFactor` is set equal to 2.5. + +The value of `NumViews` indicates the number of views, including texture views and depth views, which are required for decoding the target output views corresponding to the `j`-th operation point for `level_idc[ i ]` as signalled in the subset sequence parameter set, and is set equal to `applicable_op_num_depth_views_minus1[ i ][ j ] + applicable_op_num_depth_views_minus1[ i ][ j ] + 2`. + +The value of `PicWidthInMbs` and `FrameHeightInMbs` refer to the width and height of each view component, while the value of `TotalPicSizeInMbs` indicates the total number of macroblocks in the texture view components and depth view components of a picture. + +### H.10.2.1 Level limits common to Multiview Depth High profiles + +Bitstreams conforming to the Multiview Depth High profile at a specified level shall obey the following constraints: + +- a) The nominal removal time of access unit $n$ (with $n > 0$ ) from the CPB as specified in clause C.1.2, satisfies the constraint that $t_{r,n}(n) - t_r(n-1)$ is greater than or equal to $\text{Max}(\text{TotalPicSizeInMbs} \div (\text{mvcdScaleFactor} * \text{MaxMBPS}), f_R)$ , where $\text{MaxMBPS}$ is the value specified in Table A-1 that applies to picture $n-1$ , and $\text{TotalPicSizeInMbs}$ is the total number of macroblocks in the texture view components and depth view components of picture $n-1$ . +- b) The difference between consecutive output times of pictures from the DPB as specified in clause C.2.2, satisfies the constraint that $\Delta t_{o,dpb}(n) \geq \text{Max}(\text{TotalPicSizeInMbs} \div (\text{mvcdScaleFactor} * \text{MaxMBPS}), f_R)$ , where $\text{MaxMBPS}$ is the value specified in Table A-1 for picture $n$ , and $\text{TotalPicSizeInMbs}$ is the total number of macroblocks in the texture view components and depth view components of picture $n$ , provided that picture $n$ is a picture that is output and is not the last picture of the bitstream that is output. +- c) $\text{PicWidthInMbs} * \text{FrameHeightInMbs} \leq \text{MaxFS}$ , where $\text{MaxFS}$ is specified in Table A-1. +- d) $\text{PicWidthInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ , where $\text{MaxFS}$ is specified in Table A-1. +- e) $\text{FrameHeightInMbs} \leq \text{Sqrt}(\text{MaxFS} * 8)$ , where $\text{MaxFS}$ is specified in Table A-1. +- f) $\text{max\_dec\_frame\_buffering} \leq \text{MaxDpbFrames}$ , where $\text{MaxDpbFrames}$ is equal to $\text{Min}(\text{mvcdScaleFactor} * \text{MaxDpbMbs} / (\text{TotalPicSizeInMbs} / \text{NumViews})), \text{Max}(1, \text{Ceil}(\log_2(\text{NumViews})) * 16)$ and $\text{MaxDpbMbs}$ is specified in Table A-1. +- g) The vertical motion vector component range for luma motion vectors does not exceed the range from $-\text{MaxVmvR}$ to $(\text{MaxVmvR} - 0.25)$ in units of luma frame samples, where $\text{MaxVmvR}$ is specified in Table A-1. +- h) The horizontal motion vector component range for luma motion vectors does not exceed the following range: + - If the level number is less than 6.0, the specified range is from $-2048$ to $2047.75$ , inclusive, in units of luma samples. + - Otherwise, the specified range is from $-8192$ to $8191.75$ , inclusive, in units of luma samples. +- i) Let $\text{setOf2Mb}$ be the set of unsorted pairs of macroblocks that contains the unsorted pairs of macroblocks $(\text{mbA}, \text{mbB})$ of a coded video sequence for which any of the following conditions are true: + - $\text{mbA}$ and $\text{mbB}$ are macroblocks that belong to the same slice and are consecutive in decoding order, + - $\text{separate\_colour\_plane\_flag}$ is equal to 0, $\text{mbA}$ is the last macroblock (in decoding order) of a slice, and $\text{mbB}$ is the first macroblock (in decoding order) of the next slice in decoding order, + - $\text{separate\_colour\_plane\_flag}$ is equal to 1, $\text{mbA}$ is the last macroblock (in decoding order) of a slice with a particular value of $\text{colour\_plane\_id}$ , and $\text{mbB}$ is the first macroblock (in decoding order) of the next slice with the same value of $\text{colour\_plane\_id}$ in decoding order. + +NOTE 1 – In the two above conditions, the macroblocks $\text{mbA}$ and $\text{mbB}$ can belong to different pictures. + +For each unsorted pair of macroblocks $(\text{mbA}, \text{mbB})$ of the set $\text{setOf2Mb}$ , the total number of motion vectors (given by the sum of the number of motion vectors for macroblock $\text{mbA}$ and the number of motion vectors for macroblock $\text{mbB}$ ) does not exceed $\text{MaxMvsPer2Mb}$ , where $\text{MaxMvsPer2Mb}$ is specified in Table A-1. The number of motion vectors for each macroblock is the value of the variable $\text{MvCnt}$ after the completion of the intra or inter prediction process for the macroblock. + +NOTE 2 – When $\text{separate\_colour\_plane\_flag}$ is equal to 0, the constraint specifies that the total number of motion vectors for two consecutive macroblocks in decoding order must not exceed $\text{MaxMvsPer2Mb}$ . When $\text{separate\_colour\_plane\_flag}$ is equal to 1, the constraint specifies that the total number of motion vectors for two consecutive macroblocks with the same value of $\text{colour\_plane\_id}$ in decoding order must not exceed $\text{MaxMvsPer2Mb}$ . For macroblocks that are consecutive in decoding order but are associated with a different value of $\text{colour\_plane\_id}$ , no constraint for the total number of motion vectors is specified. + +- j) The number of bits of $\text{macroblock\_layer}()$ data for any macroblock is not greater than $128 + \text{RawMbBits}$ . Depending on $\text{entropy\_coding\_mode\_flag}$ , the bits of $\text{macroblock\_layer}()$ data are counted as follows: + - If $\text{entropy\_coding\_mode\_flag}$ is equal to 0, the number of bits of $\text{macroblock\_layer}()$ data is given by the number of bits in the $\text{macroblock\_layer}()$ syntax structure for a macroblock. + - Otherwise ( $\text{entropy\_coding\_mode\_flag}$ is equal to 1), the number of bits of $\text{macroblock\_layer}()$ data for a macroblock is given by the number of times $\text{read\_bits}(1)$ is called in clauses 9.3.3.2.2 and 9.3.3.2.3 when parsing the $\text{macroblock\_layer}()$ associated with the macroblock. + +- k) The removal time of access unit 0 shall satisfy the constraint that the number of slices in picture 0 is less than or equal to $(\text{mvcdScaleFactor} * (\text{Max}(\text{PicSizeInMbs}, \text{fr} * \text{MaxMBPS}) + \text{MaxMBPS} * (t_r(0) - t_{r,n}(0)))) \div \text{SliceRate}$ , where $\text{MaxMBPS}$ and $\text{SliceRate}$ are the values specified in Table A-1 and Table A-4, respectively, that apply to picture 0 and $\text{PicSizeInMbs}$ is the number of macroblocks in a single texture view component of picture 0. +- l) The removal time of access unit 0 shall satisfy the constraint that the number of slices in each view component of picture 0 is less than or equal to $(\text{Max}(\text{PicSizeInMbs}, \text{fr} * \text{MaxMBPS}) + \text{MaxMBPS} * (t_r(0) - t_{r,n}(0))) \div \text{SliceRate}$ , where $\text{MaxMBPS}$ and $\text{SliceRate}$ are the values specified in Table A-1 and Table A-4, respectively, that apply to picture 0 and $\text{PicSizeInMbs}$ is the number of macroblocks in a single view component of picture 0. +- m) The difference between consecutive removal times of access units $n$ and $n - 1$ with $n > 0$ shall satisfy the constraint that the number of slices in picture $n$ is less than or equal to $\text{mvcdScaleFactor} * \text{MaxMBPS} * (t_r(n) - t_r(n - 1)) \div \text{SliceRate}$ , where $\text{SliceRate}$ is the value specified in Table A-4 that applies to picture $n$ . +- n) The difference between consecutive removal times of access units $n$ and $n - 1$ with $n > 0$ shall satisfy the constraint that the number of slices in each view component of picture $n$ is less than or equal to $\text{MaxMBPS} * (t_r(n) - t_r(n - 1)) \div \text{SliceRate}$ , where $\text{SliceRate}$ is the value specified in Table A-4 that applies to picture $n$ . +- o) MVCD sequence parameter sets shall have `direct_8x8_inference_flag` equal to 1 for the levels specified in Table A-4. +- p) The value of `sub_mb_type[ mbPartIdx ]` with `mbPartIdx = 0..3` in B macroblocks with `mb_type` equal to B\_8x8 shall not be equal to B\_Bi\_8x4, B\_Bi\_4x8, or B\_Bi\_4x4 for the levels in which `MinLumaBiPredSize` is shown as 8x8 in Table A-4. +- q) For the VCL HRD parameters, $\text{BitRate}[\text{SchedSelIdx}] \leq \text{cpbBrVclFactor} * \text{MaxBR}$ and $\text{CpbSize}[\text{SchedSelIdx}] \leq \text{cpbBrVclFactor} * \text{MaxCPB}$ for at least one value of `SchedSelIdx`, where `cpbBrVclFactor` is equal to 1250. With `vui_mvc_vcl_hrd_parameters_present_flag[ i ]` being the syntax element, in the MVCD VUI parameters extension of the active MVCD sequence parameter set, that is associated with the VCL HRD parameters that are used for conformance checking (as specified in Annex C), `BitRate[ SchedSelIdx ]` and `CpbSize[ SchedSelIdx ]` are given as follows: + - If `vui_mvc_vcl_hrd_parameters_present_flag` equal to 1, `BitRate[ SchedSelIdx ]` and `CpbSize[ SchedSelIdx ]` are given by Equations E-81 and E-82, respectively, using the syntax elements of the `hrd_parameters()` syntax structure that immediately follows `vui_mvc_vcl_hrd_parameters_present_flag`. + - Otherwise (`vui_mvc_vcl_hrd_parameters_present_flag` equal to 0), `BitRate[ SchedSelIdx ]` and `CpbSize[ SchedSelIdx ]` are inferred as specified in clause E.2.2 for VCL HRD parameters. + +`MaxBR` and `MaxCPB` are specified in Table A-1 in units of `cpbBrVclFactor` bits/s and `cpbBrVclFactor` bits, respectively. The bitstream shall satisfy these conditions for at least one value of `SchedSelIdx` in the range 0 to `cpb_cnt_minus1`, inclusive. + +- r) For the NAL HRD parameters, $\text{BitRate}[\text{SchedSelIdx}] \leq \text{cpbBrNalFactor} * \text{MaxBR}$ and $\text{CpbSize}[\text{SchedSelIdx}] \leq \text{cpbBrNalFactor} * \text{MaxCPB}$ for at least one value of `SchedSelIdx`, where `cpbBrNalFactor` is equal to 1500. With `vui_mvc_nal_hrd_parameters_present_flag[ i ]` being the syntax element, in the MVCD VUI parameters extension of the active MVCD sequence parameter set, that is associated with the NAL HRD parameters that are used for conformance checking (as specified in Annex C), `BitRate[ SchedSelIdx ]` and `CpbSize[ SchedSelIdx ]` are given as follows: + - If `vui_mvc_nal_hrd_parameters_present_flag` equal to 1, `BitRate[ SchedSelIdx ]` and `CpbSize[ SchedSelIdx ]` are given by Equations E-81 and E-82, respectively, using the syntax elements of the `hrd_parameters()` syntax structure that immediately follows `vui_mvc_nal_hrd_parameters_present_flag`. + - Otherwise (`vui_mvc_nal_hrd_parameters_present_flag` equal to 0), `BitRate[ SchedSelIdx ]` and `CpbSize[ SchedSelIdx ]` are inferred as specified in clause E.2.2 for NAL HRD parameters. + +`MaxBR` and `MaxCPB` are specified in Table A-1 in units of `cpbBrNalFactor` bits/s and `cpbBrNalFactor` bits, respectively. The bitstream shall satisfy these conditions for at least one value of `SchedSelIdx` in the range 0 to `cpb_cnt_minus1`, inclusive. + +- s) The sum of the `NumBytesInNALUnit` variables for access unit 0 is less than or equal to $384 * \text{mvcdScaleFactor} * (\text{Max}(\text{PicSizeInMbs}, \text{fr} * \text{MaxMBPS}) + \text{MaxMBPS} * (t_r(0) - t_{r,n}(0))) \div \text{MinC}$ + +R, where MaxMBPS and MinCR are the values specified in Table A-1 that apply to picture 0 and PicSizeInMbs is the number of macroblocks in a single texture view component of picture 0. + +- t) The sum of the NumBytesInNALUnit variables for the VCL NAL units of each view component of access unit 0 is less than or equal to $384 * ( \text{Max} ( \text{PicSizeInMbs, fR} ) * \text{MaxMBPS} ) + \text{MaxMBPS} * ( t_r( 0 ) - t_{r,n}( 0 ) ) ) \div \text{MinCR}$ , where MaxMBPS and MinCR are the values specified in Table A-1 that apply to picture 0 and PicSizeInMbs is the number of macroblocks in a single view component of picture 0. +- u) The sum of the NumBytesInNALUnit variables for access unit n with $n > 0$ is less than or equal to $384 * \text{mvcdScaleFactor} * \text{MaxMBPS} * ( t_r( n ) - t_r( n - 1 ) ) \div \text{MinCR}$ , where MaxMBPS and MinCR are the values specified in Table A-1 that apply to picture n. +- v) The sum of the NumBytesInNALUnit variables for the VCL NAL units of each view component of access unit n with $n > 0$ is less than or equal to $384 * \text{MaxMBPS} * ( t_r( n ) - t_r( n - 1 ) ) \div \text{MinCR}$ , where MaxMBPS and MinCR are the values specified in Table A-1 that apply to picture n. +- w) When PicSizeInMbs is greater than 1620, the number of macroblocks in any coded slice shall not exceed $\text{MaxFS} / 4$ , where MaxFS is specified in Table A-1. +- x) max\_num\_ref\_frames shall be less than or equal to $\text{MaxDpbFrames} / \text{mvcScaleFactor}$ for each texture view component, where MaxDpbFrames is specified in item f). +- y) MVCD sequence parameter sets shall have frame\_mbs\_only\_flag equal to 1 for the levels specified in Table A-4. + +Table A-1 specifies the limits for each level. A definition of all levels identified in the "Level number" column of Table A-1 is specified for the Multiview Depth High profile. Table A-4 specifies limits for each level that are specific to bitstreams conforming to the Multiview Depth High profile. Each entry in Table A-1 and Table A-4 indicates, for the level corresponding to the row of the table, the absence or value of a limit that is imposed by the variable corresponding to the column of the table, as follows: + +- If the table entry is marked as "-", no limit is imposed by the value of the variable as a requirement of bitstream conformance to the profile at the specified level. +- Otherwise, the table entry specifies the value of the variable for the associated limit that is imposed as a requirement of bitstream conformance to the profile at the specified level. + +For coded video sequences conforming to the Multiview Depth High profile, the level\_idc value is specified as follows: + +- If level\_idc is not equal to 0, level\_idc indicates the level that applies to the coded video sequence operating with all the views being target output views. + +NOTE 3 – A level\_idc value that is not equal to zero may indicate a higher level than necessary to decode the coded video sequence operating with all the views being target output views. This may occur when a subset of views or temporal subsets are removed from a coded video sequence according to the sub-bitstream extraction process specified in clause H.8.5.3, and the level\_idc value is not updated accordingly. + +- Otherwise (level\_idc is equal to 0), the level that applies to the coded video sequence operating with all the views being target output views is unspecified. + +NOTE 4 – When profile\_idc is equal to 118 or 128 and level\_idc is equal to 0, there may exist a level indicated by level\_idc[ i ] that is applicable to the coded video sequence operating with all the views being target output views. This may occur when a subset of views or temporal subsets are removed from a coded video sequence according to the sub-bitstream extraction process specified in clause H.8.5.3, and a particular value of level\_idc[ i ] corresponds to the resulting coded video sequence. + +In bitstreams conforming to the Multiview Depth High profile, the conformance of the bitstream to a specified level is indicated by the syntax element level\_idc or level\_idc[ i ] as follows: + +- If level\_idc or level\_idc[ i ] is equal to 9, the indicated level is level 1b. +- Otherwise (level\_idc or level\_idc[ i ] is not equal to 9), level\_idc or level\_idc[ i ] is equal to a value of ten times the level number (of the indicated level) specified in Table A-1. + +#### H.10.2.2 Profile specific level limits + +- a) In bitstreams conforming to the Multiview Depth High profile, MVCD sequence parameter sets shall have frame\_mbs\_only\_flag equal to 1 for the levels specified in Table A-4. + +### H.11 Byte stream format + +The specifications in Annex B apply. + +## H.12 MVCD hypothetical reference decoder + +The specifications in Annex C apply with substituting MVCD sequence parameter set for MVC sequence parameter set. + +## H.13 MVCD SEI messages + +The specifications in Annex D together with the extensions and modifications specified in this clause apply. + +### H.13.1 SEI message syntax + +#### H.13.1.1 MVCD view scalability information SEI message syntax + +| mvcd_view_scalability_info( payloadSize ) { | C | Descriptor | +|---------------------------------------------------------------|----------|-------------------| +| num_operation_points_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_operation_points_minus1; i++ ) { | | | +| operation_point_id[ i ] | 5 | ue(v) | +| priority_id[ i ] | 5 | u(5) | +| temporal_id[ i ] | 5 | u(3) | +| num_target_output_views_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= num_target_output_views_minus1[ i ]; j++ ) { | | | +| view_id[ i ][ j ] | 5 | ue(v) | +| mvcd_op_view_info( ) | | | +| } | | | +| profile_level_info_present_flag[ i ] | 5 | u(1) | +| bitrate_info_present_flag[ i ] | 5 | u(1) | +| frm_rate_info_present_flag[ i ] | 5 | u(1) | +| if( !num_target_output_views_minus1[ i ] ) | | | +| view_dependency_info_present_flag[ i ] | 5 | u(1) | +| parameter_sets_info_present_flag[ i ] | 5 | u(1) | +| bitstream_restriction_info_present_flag[ i ] | 5 | u(1) | +| if( profile_level_info_present_flag[ i ] ) | | | +| op_profile_level_idc[ i ] | 5 | u(24) | +| if( bitrate_info_present_flag[ i ] ) { | | | +| avg_bitrate[ i ] | 5 | u(16) | +| max_bitrate[ i ] | 5 | u(16) | +| max_bitrate_calc_window[ i ] | 5 | u(16) | +| } | | | +| if( frm_rate_info_present_flag[ i ] ) { | | | +| constant_frm_rate_idc[ i ] | 5 | u(2) | +| avg_frm_rate[ i ] | 5 | u(16) | +| } | | | +| if( view_dependency_info_present_flag[ i ] ) { | | | +| num_directly_dependent_views[ i ] | 5 | ue(v) | +| for( j = 0; j < num_directly_dependent_views[ i ]; j++ ) { | | | +| directly_dependent_view_id[ i ][ j ] | 5 | ue(v) | +| mvcd_op_view_info( ) | | | +| } | | | +| } else | | | +| view_dependency_info_src_op_id[ i ] | 5 | ue(v) | +| if( parameter_sets_info_present_flag[ i ] ) { | | | +| num_seq_parameter_set_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= num_seq_parameter_set_minus1[ i ]; j++ ) | | | +| seq_parameter_set_id_delta[ i ][ j ] | 5 | ue(v) | + +| | | | +|------------------------------------------------------------------|---|-------| +| num_subset_seq_parameter_set_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= num_subset_seq_parameter_set_minus1[ i ]; j++ ) | | | +| subset_seq_parameter_set_id_delta[ i ][ j ] | 5 | ue(v) | +| num_pic_parameter_set_minus1[ i ] | 5 | ue(v) | +| for( j = 0; j <= num_init_pic_parameter_set_minus1[ i ]; j++ ) | | | +| pic_parameter_set_id_delta[ i ][ j ] | 5 | ue(v) | +| } else | | | +| parameter_sets_info_src_op_id[ i ] | 5 | ue(v) | +| if( bitstream_restriction_info_present_flag[ i ] ) { | | | +| motion_vectors_over_pic_boundaries_flag[ i ] | 5 | u(1) | +| max_bytes_per_pic_denom[ i ] | 5 | ue(v) | +| max_bits_per_mb_denom[ i ] | 5 | ue(v) | +| log2_max_mv_length_horizontal[ i ] | 5 | ue(v) | +| log2_max_mv_length_vertical[ i ] | 5 | ue(v) | +| num_reorder_frames[ i ] | 5 | ue(v) | +| max_dec_frame_buffering[ i ] | 5 | ue(v) | +| } | | | +| } | | | +| } | | | + +#### H.13.1.1.1 MVCD operation point view information syntax + +| | | | +|--------------------------------------------|----------|-------------------| +| mvcd_op_view_info() { | C | Descriptor | +| view_info_depth_view_present_flag | 5 | u(1) | +| if( view_info_depth_view_present_flag ) | | | +| mvcd_depth_view_flag | 5 | u(1) | +| view_info_texture_view_present_flag | 5 | u(1) | +| if( view_info_texture_view_present_flag ) | | | +| mvcd_texture_view_flag | 5 | u(1) | +| } | | | + +#### H.13.1.2 MVCD scalable nesting SEI message syntax + +| | | | +|---------------------------------------------------------|----------|-------------------| +| mvcd_scalable_nesting( payloadSize ) { | C | Descriptor | +| operation_point_flag | 5 | u(1) | +| if( !operation_point_flag ) { | | | +| all_view_components_in_aus_flag | 5 | u(1) | +| if( !all_view_components_in_aus_flag ) { | | | +| num_view_components_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_view_components_minus1; i++ ) { | | | +| sei_view_id[ i ] | 5 | u(10) | +| sei_view_applicability_flag[ i ] | 5 | u(1) | +| } | | | +| } | | | +| } else { | | | +| sei_op_texture_only_flag | 5 | u(1) | +| num_view_components_op_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_view_components_op_minus1; i++ ) { | | | +| sei_op_view_id[ i ] | 5 | u(10) | +| if( !sei_op_texture_only_flag ) { | | | +| sei_op_depth_flag[ i ] | | | + +| | | | +|----------------------------------------------|---|------| +| sei_op_texture_flag[ i ] | | | +| } | | | +| } | | | +| sei_op_temporal_id | 5 | u(3) | +| } | | | +| while( !byte_aligned() ) | | | +| sei_nesting_zero_bit /* equal to 0 */ | 5 | f(1) | +| sei_message( ) | 5 | | +| } | | | + +### H.13.1.3 Depth representation information SEI message syntax + +| depth_representation_info( payloadSize ) { | C | Descriptor | +|----------------------------------------------------------------------------------------|---|------------| +| all_views_equal_flag | 5 | u(1) | +| if( all_views_equal_flag == 0 ) { | | | +| num_views_minus1 | 5 | ue(v) | +| numViews = num_views_minus1 + 1 | | | +| } else | | | +| numViews = 1 | | | +| z_near_flag | 5 | u(1) | +| z_far_flag | 5 | u(1) | +| if( z_near_flag z_far_flag ) { | | | +| z_axis_equal_flag | 5 | u(1) | +| if( z_axis_equal_flag ) | | | +| common_z_axis_reference_view | 5 | ue(v) | +| } | | | +| d_min_flag | 5 | u(1) | +| d_max_flag | 5 | u(1) | +| depth_representation_type | 5 | ue(v) | +| for( i = 0; i < numViews; i++ ) { | | | +| depth_info_view_id[ i ] | 5 | ue(v) | +| if( ( z_near_flag z_far_flag ) && ( z_axis_equal_flag == 0 ) ) | | | +| z_axis_reference_view[ i ] | 5 | ue(v) | +| if( d_min_flag d_max_flag ) | | | +| disparity_reference_view[ i ] | 5 | ue(v) | +| if( z_near_flag ) | | | +| depth_representation_sei_element( ZNearSign, ZNearExp,
ZNearMantissa, ZNearManLen ) | | | +| if( z_far_flag ) | | | +| depth_representation_sei_element( ZFarSign, ZFarExp,
ZFarMantissa, ZFarManLen ) | | | +| if( d_min_flag ) | | | +| depth_representation_sei_element( DMinSign, DMinExp,
DMinMantissa, DMinManLen ) | | | +| if( d_max_flag ) | | | +| depth_representation_sei_element( DMaxSign, DMaxExp,
DMaxMantissa, DMaxManLen ) | | | +| } | | | + +| | | | +|-----------------------------------------------------------------------|---|-------| +| if( depth_representation_type == 3 ) { | | | +| depth_nonlinear_representation_num_minus1 | 5 | ue(v) | +| for( i = 1; i <= depth_nonlinear_representation_num_minus1 + 1; i++ ) | | | +| depth_nonlinear_representation_model[ i ] | 5 | ue(v) | +| } | | | +| } | | | + +#### H.13.1.3.1 Depth representation SEI element syntax + +| | | | +|-------------------------------------------------------------------------------|----------|-------------------| +| depth_representation_sei_element( outSign, outExp, outMantissa, outManLen ) { | C | Descriptor | +| da_sign_flag | 5 | u(1) | +| da_exponent | 5 | u(7) | +| da_mantissa_len_minus1 | 5 | u(5) | +| da_mantissa | 5 | u(v) | +| } | | | + +#### H.13.1.4 3D reference displays information SEI message syntax + +| | | | +|------------------------------------------------------------|----------|-------------------| +| three_dimensional_reference_displays_info( payloadSize ) { | C | Descriptor | +| prec_ref_baseline | 5 | ue(v) | +| prec_ref_display_width | 5 | ue(v) | +| ref_viewing_distance_flag | 5 | u(1) | +| if( ref_viewing_distance_flag ) | | | +| prec_ref_viewing_dist | 5 | ue(v) | +| num_ref_displays_minus1 | 5 | ue(v) | +| numRefDisplays = num_ref_displays_minus1 + 1 | | | +| for( i = 0; i < numRefDisplays; i++ ) { | | | +| exponent_ref_baseline[ i ] | 5 | u(6) | +| mantissa_ref_baseline[ i ] | 5 | u(v) | +| exponent_ref_display_width[ i ] | 5 | u(6) | +| mantissa_ref_display_width[ i ] | 5 | u(v) | +| if( ref_viewing_distance_flag ) { | | | +| exponent_ref_viewing_distance[ i ] | 5 | u(6) | +| mantissa_ref_viewing_distance[ i ] | 5 | u(v) | +| } | | | +| additional_shift_present_flag[ i ] | 5 | u(1) | +| if( additional_shift_present[ i ] ) | | | +| num_sample_shift_plus512[ i ] | 5 | u(10) | +| } | | | +| three_dimensional_reference_displays_extension_flag | 5 | u(1) | +| } | | | + +### H.13.1.5 Depth timing SEI message syntax + +| depth_timing( payloadSize ) { | C | Descriptor | +|--------------------------------------|---|------------| +| per_view_depth_timing_flag | 5 | u(1) | +| if( per_view_depth_timing_flag ) | | | +| for( i = 0; i < NumDepthViews; i++ ) | | | +| depth_timing_offset( ) | | | +| else | | | +| depth_timing_offset( ) | | | +| } | | | + +#### H.13.1.5.1 Depth timing offset syntax + +| depth_timing_offset( ) { | C | Descriptor | +|-----------------------------------|---|------------| +| offset_len_minus1 | 5 | u(5) | +| depth_disp_delay_offset_fp | 5 | u(v) | +| depth_disp_delay_offset_dp | 5 | u(6) | +| } | | | + +### H.13.1.6 Alternative depth information SEI message syntax + +| alternative_depth_info( payloadSize ) { | C | Descriptor | +|----------------------------------------------------------------|---|------------| +| depth_type | 5 | ue(v) | +| if( depth_type == 0 ) { | | | +| num_constituent_views_gvd_minus1 | 5 | ue(v) | +| depth_present_gvd_flag | 5 | u(1) | +| z_gvd_flag | 5 | u(1) | +| intrinsic_param_gvd_flag | 5 | u(1) | +| rotation_gvd_flag | 5 | u(1) | +| translation_gvd_flag | 5 | u(1) | +| if( z_gvd_flag ) | | | +| for( i = 0; i <= num_constituent_views_gvd_minus1 + 1; i++ ) { | | | +| sign_gvd_z_near_flag[ i ] | 5 | u(1) | +| exp_gvd_z_near[ i ] | 5 | u(7) | +| man_len_gvd_z_near_minus1[ i ] | 5 | u(5) | +| man_gvd_z_near[ i ] | 5 | u(v) | +| sign_gvd_z_far_flag[ i ] | 5 | u(1) | +| exp_gvd_z_far[ i ] | 5 | u(7) | +| man_len_gvd_z_far_minus1[ i ] | 5 | u(5) | +| man_gvd_z_far[ i ] | 5 | u(v) | +| } | | | +| if( intrinsic_param_gvd_flag ) { | | | +| prec_gvd_focal_length | 5 | ue(v) | +| prec_gvd_principal_point | 5 | ue(v) | +| } | | | +| if( rotation_gvd_flag ) | | | +| prec_gvd_rotation_param | 5 | ue(v) | + +| | | | +|----------------------------------------------------------------|---|-------| +| if( translation_gvd_flag ) | | | +| prec_gvd_translation_param | 5 | ue(v) | +| for( i = 0; i <= num_constituent_views_gvd_minus1 + 1; i++ ) { | | | +| if( intrinsic_param_gvd_flag ) { | | | +| sign_gvd_focal_length_x[ i ] | 5 | u(1) | +| exp_gvd_focal_length_x[ i ] | 5 | u(6) | +| man_gvd_focal_length_x[ i ] | 5 | u(v) | +| sign_gvd_focal_length_y[ i ] | 5 | u(1) | +| exp_gvd_focal_length_y[ i ] | 5 | u(6) | +| man_gvd_focal_length_y[ i ] | 5 | u(v) | +| sign_gvd_principal_point_x[ i ] | 5 | u(1) | +| exp_gvd_principal_point_x[ i ] | 5 | u(6) | +| man_gvd_principal_point_x[ i ] | 5 | u(v) | +| sign_gvd_principal_point_y[ i ] | 5 | u(1) | +| exp_gvd_principal_point_y[ i ] | 5 | u(6) | +| man_gvd_principal_point_y[ i ] | 5 | u(v) | +| } | | | +| if( rotation_gvd_flag ) | | | +| for( j = 0; j < 3; j++ ) /* row */ | | | +| for( k = 0; k < 3; k++ ) { /* column */ | | | +| sign_gvd_r[ i ][ j ][ k ] | 5 | u(1) | +| exp_gvd_r[ i ][ j ][ k ] | 5 | u(6) | +| man_gvd_r[ i ][ j ][ k ] | 5 | u(v) | +| } | | | +| if( translation_gvd_flag ) { | | | +| sign_gvd_t_x[ i ] | 5 | u(1) | +| exp_gvd_t_x[ i ] | 5 | u(6) | +| man_gvd_t_x[ i ] | 5 | u(v) | +| } | | | +| } | | | +| } | | | +| if( translation_gvd_flag ) { | | | +| sign_gvd_t_x[ i ] | 5 | u(1) | +| exp_gvd_t_x[ i ] | 5 | u(6) | +| man_gvd_t_x[ i ] | 5 | u(v) | +| } | | | + +### H.13.1.7 Depth sampling information SEI message syntax + +| depth_sampling_info( payloadSize ) { | C | Descriptor | +|-------------------------------------------------------------|---|------------| +| dttsr_x_mul | 5 | u(16) | +| dttsr_x_dp | 5 | u(4) | +| dttsr_y_mul | 5 | u(16) | +| dttsr_y_dp | 5 | u(4) | +| per_view_depth_grid_pos_flag | 5 | u(1) | +| if( per_view_depth_grid_pos_flag ) { | | | +| num_video_plus_depth_views_minus1 | 5 | ue(v) | +| for( i = 0; i <= num_video_plus_depth_views_minus1; i++ ) { | | | +| depth_grid_view_id[ i ] | 5 | ue(v) | +| depth_grid_position( ) | | | +| } | | | +| } else | | | +| depth_grid_position( ) | | | +| } | | | + +#### H.13.1.7.1 Depth grid position syntax + +| depth_grid_position( ) { | C | Descriptor | +|-----------------------------------|---|------------| +| depth_grid_pos_x_fp | 5 | u(20) | +| depth_grid_pos_x_dp | 5 | u(4) | +| depth_grid_pos_x_sign_flag | 5 | u(1) | +| depth_grid_pos_y_fp | 5 | u(20) | +| depth_grid_pos_y_dp | 5 | u(4) | +| depth_grid_pos_y_sign_flag | 5 | u(1) | +| } | | | + +### H.13.2 SEI message semantics + +Depending on payloadType, the corresponding SEI message semantics are extended as follows: + +- If payloadType is equal to 2, 3, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212, the following applies: + - If the SEI message is not included in an MVC scalable nesting SEI message or an MVCD scalable nesting SEI message, it applies to the texture view component of the current access unit with VOIdx equal to VOIdxMin. + - Otherwise, if included in an MVC scalable nesting SEI message and not included in an MVCD scalable nesting SEI message, it applies to all texture view components of the current access unit when all\_view\_components\_in\_au\_flag is equal to 1, or it applies to all texture view components of the current access unit with view\_id equal to sei\_view\_id[ i ] for any i in the range of 0 to num\_view\_components\_minus1, inclusive, when all\_view\_components\_in\_au\_flag is equal to 0. When payloadType is equal to 10 for the SEI message that is included in an MVC scalable nesting SEI message, the semantics for sub\_seq\_layer\_num of the sub-sequence information SEI message is modified as follows: + +**sub\_seq\_layer\_num** specifies the sub-sequence layer number of the current picture. When the current picture resides in a sub-sequence for which the first picture in decoding order is an IDR picture, the value of sub\_seq\_layer\_num shall be equal to 0. For a non-paired reference field, the value of sub\_seq\_layer\_num shall be equal to 0. sub\_seq\_layer\_num shall be in the range of 0 to 255, inclusive. + - Otherwise, if not included in an MVC scalable nesting SEI message and included in an MVCD scalable nesting SEI message, it applies to all depth view components or view component pairs of the current access unit when all\_view\_components\_in\_au\_flag is equal to 1, or it applies to all depth view components or view component pairs of the current access unit with view\_id equal to sei\_view\_id[ i ] for any i in the range of 0 to + +num\_view\_components\_minus1, inclusive, when all\_view\_components\_in\_aus\_flag is equal to 0. When payloadType is equal to 10 for the SEI message that is included in an MVCD scalable nesting SEI message, the semantics for sub\_seq\_layer\_num of the sub-sequence information SEI message is modified as follows: + +**sub\_seq\_layer\_num** specifies the sub-sequence layer number of the current picture. When the current picture resides in a sub-sequence for which the first picture in decoding order is an IDR picture, the value of sub\_seq\_layer\_num shall be equal to 0. For a non-paired reference field, the value of sub\_seq\_layer\_num shall be equal to 0. sub\_seq\_layer\_num shall be in the range of 0 to 255, inclusive. + +- Otherwise, if payloadType is equal to 41, 42 or 43, the following applies: + - If the SEI message is not included in MVCD scalable nesting SEI message, it applies to texture views only and NAL units having nal\_unit\_type equal to 21 are non-VCL NAL units. + - Otherwise (the SEI message is included in MVCD scalable nesting SEI message), the SEI message applies to depth views, to texture views or both texture views all depth views, depending on the values of the syntax elements of the MVCD scalable nesting SEI message. +- Otherwise, if payloadType is equal to 0 or 1, the following applies: + - If the SEI message is not included in an MVC scalable nesting SEI message or an MVCD scalable nesting SEI message or an MVCD texture sub-bitstream HRD nesting SEI message, the following applies. When the SEI message and all other SEI messages with payloadType equal to 0 or 1 not included in an MVC scalable nesting SEI message or an MVCD scalable nesting SEI message or an MVCD texture sub-bitstream HRD nesting SEI message are used as the buffering period and picture timing SEI messages for checking the bitstream conformance according to Annex C and the decoding process specified in clauses 2 to 9 is used, the bitstream shall be conforming to this Recommendation | International Standard. + - Otherwise, if the SEI message is included in an MVC scalable nesting SEI message and not included in an MVCD scalable nesting SEI message or a MVCD texture sub-bitstream HRD nesting SEI message, the following applies. When the SEI message and all other SEI messages with payloadType equal to 0 or 1 included in an MVC scalable nesting SEI message with identical values of sei\_op\_temporal\_id and sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, are used as the buffering period and picture timing SEI messages for checking the bitstream conformance according to Annex C, the bitstream that would be obtained by invoking the bitstream extraction process as specified in clause G.8.3 with tldTarget equal to sei\_op\_temporal\_id and viewIdTargetList equal to sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, shall be conforming to this Recommendation | International Standard. + +In the semantics of clauses D.2.1 and D.2.3, the syntax elements num\_units\_in\_tick, time\_scale, fixed\_frame\_rate\_flag, nal\_hrd\_parameters\_present\_flag, vcl\_hrd\_parameters\_present\_flag, low\_delay\_hrd\_flag, and pic\_struct\_present\_flag and the derived variables NalHrdBpPresentFlag, VclHrdBpPresentFlag, and CpbDpbDelaysPresentFlag are substituted with the syntax elements vui\_mvc\_num\_units\_in\_tick[ i ], vui\_mvc\_time\_scale[ i ], vui\_mvc\_fixed\_frame\_rate\_flag[ i ], vui\_mvc\_nal\_hrd\_parameters\_present\_flag[ i ], vui\_mvc\_vcl\_hrd\_parameters\_present\_flag[ i ], vui\_mvc\_low\_delay\_hrd\_flag[ i ], and vui\_mvc\_pic\_struct\_present\_flag[ i ] and the derived variables VuiMvcNalHrdBpPresentFlag[ i ], VuiMvcVclHrdBpPresentFlag[ i ], and VuiMvcCpbDpbDelaysPresentFlag[ i ]. + +The values of seq\_parameter\_set\_id's in all buffering period SEI messages included in MVC scalable nesting SEI messages and associated with operation points for which the greatest VOIdx values in the associated sub-bitstreams are identical shall be identical. + +- Otherwise, if the SEI message is included in a MVCD scalable nesting SEI message and not included in an MVC scalable nesting SEI message or an MVCD texture sub-bitstream HRD nesting SEI message, the following applies. When the SEI message and all other SEI messages with payloadType equal to 0 or 1 included in an MVCD scalable nesting SEI message with identical values of sei\_op\_temporal\_id and sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, are used as the buffering period and picture timing SEI messages for checking the bitstream conformance according to Annex C, the bitstream that would be obtained by invoking the bitstream extraction process as specified in clause H.8.5 with depthPresentTargetFlag equal to 1, tldTarget equal to sei\_op\_temporal\_id and viewIdTargetList equal to sei\_op\_view\_id[ i ] for all i in the range of 0 to num\_view\_components\_op\_minus1, inclusive, shall be conforming to this Recommendation | International Standard. + +In the semantics of clauses D.2.1 and D.2.3, the syntax elements num\_units\_in\_tick, time\_scale, fixed\_frame\_rate\_flag, nal\_hrd\_parameters\_present\_flag, vcl\_hrd\_parameters\_present\_flag, low\_delay\_hrd\_flag, and pic\_struct\_present\_flag and the derived variables NalHrdBpPresentFlag, + +VclHrdBpPresentFlag, and CpbDpbDelaysPresentFlag are substituted with the syntax elements `vui_mvc_num_units_in_tick[ i ]`, `vui_mvc_time_scale[ i ]`, `vui_mvc_fixed_frame_rate_flag[ i ]`, `vui_mvc_nal_hrd_parameters_present_flag[ i ]`, `vui_mvc_vcl_hrd_parameters_present_flag[ i ]`, `vui_mvc_low_delay_hrd_flag[ i ]`, and `vui_mvc_pic_struct_present_flag[ i ]` and the derived variables `VuiMvcNalHrdBpPresentFlag[ i ]`, `VuiMvcVclHrdBpPresentFlag[ i ]`, and `VuiMvcCpbDpbDelaysPresentFlag[ i ]` for the MVCD VUI parameters extension. + +The values of `seq_parameter_set_id`'s in all buffering period SEI messages included in MVCD scalable nesting SEI messages and not included in either MVC scalable nesting SEI messages or MVCD texture sub-bitstream HRD nesting SEI messages and associated with operation points for which the greatest `VOIdx` values in the associated sub-bitstreams are identical shall be identical. + +- Otherwise, if the SEI message is included in an MVCD texture sub-bitstream HRD nesting SEI message, the following applies. When the SEI message and all other SEI messages included in an MVCD texture sub-bitstream HRD nesting SEI message with identical values of `texture_subbitstream_temporal_id` and `texture_subbitstream_view_id[ i ]` for all `i` in the range of 0 to `num_texture_subbitstream_view_components_minus1`, inclusive, are used as the buffering period and picture timing SEI messages for checking the bitstream conformance according to Annex C, the bitstream that would be obtained by invoking the bitstream extraction process as specified in clause H.8.5 with `depthPresentTargetFlag` equal to 0, `tldTarget` equal to `texture_subbitstream_temporal_id` and `viewIdTargetList` equal to `texture_subbitstream_view_id[ i ]` for all `i` in the range of 0 to `num_texture_subbitstream_view_components_minus1`, inclusive, shall be conforming to this Recommendation | International Standard. + +In the semantics of clauses D.2.1 and D.2.3, the syntax elements `num_units_in_tick`, `time_scale`, `fixed_frame_rate_flag`, `nal_hrd_parameters_present_flag`, `vcl_hrd_parameters_present_flag`, `low_delay_hrd_flag`, and `pic_struct_present_flag` and the derived variables `NalHrdBpPresentFlag`, `VclHrdBpPresentFlag`, and `CpbDpbDelaysPresentFlag` are substituted with the syntax elements `vui_mvc_num_units_in_tick[ i ]`, `vui_mvc_time_scale[ i ]`, `vui_mvc_fixed_frame_rate_flag[ i ]`, `vui_mvc_nal_hrd_parameters_present_flag[ i ]`, `vui_mvc_vcl_hrd_parameters_present_flag[ i ]`, `vui_mvc_low_delay_hrd_flag[ i ]`, and `vui_mvc_pic_struct_present_flag[ i ]` and the derived variables `VuiMvcNalHrdBpPresentFlag[ i ]`, `VuiMvcVclHrdBpPresentFlag[ i ]`, and `VuiMvcCpbDpbDelaysPresentFlag[ i ]` for the MVCD texture sub-bitstream VUI parameters extension. + +The values of `seq_parameter_set_id`'s in all buffering period SEI messages included in MVCD texture sub-bitstream HRD nesting SEI messages and associated with operation points for which the greatest `VOIdx` values in the associated sub-bitstreams are identical shall be identical. + +- Otherwise (all remaining `payloadType` values), the corresponding SEI message semantics are not extended. + +When an SEI message having a particular value of `payloadType` equal to 137 or 144, contained in an MVCD scalable nesting SEI message, and applying to a particular combination of a list of `view_id` and a `temporal_id` is present in an access unit, the SEI message with the particular value of `payloadType` applying to the particular combination of a list of `view_id` and a `temporal_id` shall be present an MVCD scalable nesting SEI message in the IDR access unit that is the first access unit of the coded video sequence. + +All SEI messages having a particular value of `payloadType` equal to 137 or 144, contained in MVCD scalable nesting SEI messages, and applying to a particular combination of a list of `view_id` and a `temporal_id` present in a coded video sequence shall have the same content. + +For the semantics of SEI messages with `payloadType` in the range of 0 to 23, inclusive, or equal to 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212, which are specified in clause D.2, MVCD sequence parameter set is substituted for sequence parameter set; the parameters of MVCD sequence parameter set RBSP and picture parameter set RBSP that are in effect are specified in clauses H.7.4.2.1 and H.7.4.2.2, respectively. + +Coded video sequences conforming to one or more of the profiles specified in this annex shall not include SEI NAL units that contain SEI messages with `payloadType` in the range of 24 to 35, inclusive. + +When an SEI NAL unit contains an SEI message with `payloadType` in the range of 36 to 44, inclusive, or equal to 46, or in the range of 48 to 53, inclusive, it shall not contain any SEI messages with `payloadType` less than 36 or equal to 45, 47, 137, 142, 144, 147, 148, 149, 150, 151, 154, 155, 156, 200, 201, 202, 205, 210, 211, or 212, and the first SEI message in the SEI NAL unit shall have `payloadType` in the range of 36 to 44, inclusive, or equal to 46, or in the range of 48 to 53, inclusive. + +When an MVC scalable nesting SEI message (`payloadType` equal to 37), a view scalability information SEI message (`payloadType` equal to 38), an operation point not present SEI message (`payloadType` equal to 43), an MVCD scalable + +nesting SEI message (payloadType equal to 48), or an MVCD view scalability information SEI messages (payloadType equal to 49) is present in an SEI NAL unit, it shall be the only SEI message in the SEI NAL unit. + +#### H.13.2.1 MVCD view scalability information SEI message semantics + +The syntax elements in the MVCD view scalability information SEI message that have the same names as those in the view scalability information SEI message specified in Annex G, except `num_directly_dependent_depth_views[ i ]` and `directly_dependent_depth_view_id[ i ][ j ]`, have the same semantics as the corresponding syntax elements in the view scalability information SEI message, but apply to operation points that may potentially contain depth view components as well as texture view components. + +`num_directly_dependent_views[ i ]` and `directly_dependent_view_id[ i ][ j ]` apply only to the texture view components of an operation point if the operation point contains both texture and depth, and otherwise have the same semantics as the corresponding syntax elements in the view scalability information SEI message. + +##### H.13.2.1.1 MVCD operation point view information semantics + +`view_info_depth_view_present_flag` equal to 0 specifies that the depth view is not included in the operation point for the view for which the `mvcd_op_view_info()` syntax structure is present. `view_info_depth_view_present_flag` equal to 1 specifies that the depth view is included in the operation point for the view for which the `mvcd_op_view_info()` syntax structure is present. + +`mvcd_depth_view_flag` equal to 0 indicates that some VCL NAL units for the depth view for the view for which the `mvcd_op_view_info()` syntax structure is present may include NAL units with `nal_unit_type` equal to 21 and `avc_3d_extension_flag` equal to 1. `mvcd_depth_view_flag` equal to 1 indicates that the VCL NAL units for the depth view for the view for which the `mvcd_op_view_info()` syntax structure is present does not include NAL units with both `nal_unit_type` equal to 21 and `avc_3d_extension_flag` equal to 1. + +`view_info_texture_view_present_flag` equal to 0 specifies that the texture view is not included in the operation point for the view for which the `mvcd_op_view_info()` syntax structure is present. `view_info_depth_view_present_flag` equal to 1 specifies that the texture view is included in the operation point for the view for which the `mvcd_op_view_info()` syntax structure is present. When `view_info_depth_view_present_flag` is equal to 0, `view_info_texture_view_present_flag` shall be equal to 1. + +`mvcd_texture_view_flag` equal to 0 indicates that some VCL NAL units for the texture view for the view for which the `mvcd_op_view_info()` syntax structure is present may include NAL units with `nal_unit_type` equal to 21 and `avc_3d_extension_flag` equal to 1. `mvcd_texture_view_flag` equal to 0 indicates that the VCL NAL units for the texture view for the view for which the `mvcd_op_view_info()` syntax structure is present does not include NAL units with both `nal_unit_type` equal to 21 and `avc_3d_extension_flag` equal to 1. + +#### H.13.2.2 MVCD scalable nesting SEI message semantics + +The syntax elements in the MVCD scalable nesting SEI message have the same semantics as the ones with the same names and present in the MVC scalable nesting SEI message in Annex G. + +`sei_view_applicability_flag[ i ]` equal to 1 indicates that the nested SEI message applies to both the texture view component and the depth view component of the view with `view_id` equal to `sei_view_id[ i ]`. `sei_view_applicability_flag[ i ]` equal to 0 indicates that the nested SEI message applies only to the depth view component of the view with `view_id` equal to `sei_view_id[ i ]`. + +`sei_op_texture_only_flag` equal to 0 specifies that the semantics of `sei_op_view_id[ i ]` and `sei_op_temporal_id` apply to both texture and depth views, if present. `sei_op_texture_only_flag` equal to 1 specifies that the nested SEI message as well as the semantics of `sei_op_view_id[ i ]` and `sei_op_temporal_id` apply to the sub-bitstream obtained by the sub-bitstream extraction process of clause H.8.5.3 with `depthPresentFlagTarget` equal to 0, `tIdTarget` equal to `sei_op_temporal_id`, and `viewIdTargetList` equal to `sei_op_view_id[ i ]` for all values of `i` in the range of 0 to `num_view_components_op_minus1`, inclusive, as inputs. + +NOTE 1 – MVC scalable nesting SEI message should be used for nesting SEI messages, when depth views may or may not be present in the bitstream, the nested SEI messages apply only to indicated texture view components and the semantics of the nested SEI messages apply when VCL and non-VCL NAL units are classified according to Annex G NAL unit type class of Table 7-1. + +NOTE 2 – MVCD scalable nesting SEI message with `sei_op_texture_only_flag` equal to 1 should be used when the nested SEI messages concern a sub-bitstream from which depth views have been excluded. For example, MVCD scalable nesting SEI message with `sei_op_texture_only_flag` equal to 1 may include buffering period and picture timing SEI messages which apply only to a sub-bitstream containing texture views from which depth views have been removed using the sub-bitstream extraction process of clause H.8.5.3 with `depthPresentFlagTarget` equal to 0. + +`sei_op_depth_flag[ i ]` equal to 0 specifies that the depth view with `view_id` equal to `sei_op_view_id[ i ]` is not included in the operation point to which the nested SEI message applies. `sei_op_depth_flag[ i ]` equal to 1 specifies that the depth + +view with view\_id equal to sei\_op\_view\_id[ i ] is included in the operation point to which the nested SEI message applies. If sei\_op\_depth\_flag[ i ] is not present, it is inferred to be equal to 1. + +**sei\_op\_texture\_flag[ i ]** equal to 0 specifies that the texture view with view\_id equal to sei\_op\_view\_id[ i ] is not included in the operation point to which the nested SEI message applies. sei\_op\_texture\_flag[ i ] equal to 1 specifies that the texture view with view\_id equal to sei\_op\_view\_id[ i ] is included in the operation point to which the nested SEI message applies. If sei\_op\_texture\_flag[ i ] is not present, it is inferred to be equal to 1. When sei\_op\_depth\_flag[ i ] is equal to 0, sei\_op\_texture\_flag[ i ] shall be equal to 1. + +### H.13.2.3 Depth representation information SEI message semantics + +The syntax elements in the depth representation information SEI message specifies various parameters for depth views for the purpose of processing decoded texture and depth view components prior to rendering on a 3D display, such as view synthesis. Specifically, depth or disparity ranges for depth views are specified. When present, the depth representation information SEI message may be associated with any access unit. It is recommended, when present, the SEI message is associated with an IDR access unit for the purpose of random access. The information indicated in the SEI message applies to all the access units from the access unit the SEI message is associated with to the next access unit, in decoding order, containing an SEI message of the same type, exclusive, or to the end of the coded video sequence, whichever is earlier in decoding order. + +NOTE 1 – Camera parameters for depth views may be indicated by including a multiview acquisition information SEI message in an MVCD scalable nesting SEI message with operation\_point\_flag equal to 0. + +**all\_views\_equal\_flag** equal to 0 specifies that depth acquisition information may not be identical to respective values for each view in target views. all\_views\_equal\_flag equal to 1 specifies that the depth acquisition information are identical to respective values for all target views. + +**num\_views\_minus1** plus 1 specifies the number of views to which subsequent syntax element apply. When present, num\_views\_minus1 shall be less than or equal to NumDepthViews – 1. The value of num\_views\_minus1 shall be in the range of 0 to 1023, inclusive. + +**z\_near\_flag** equal to 0 specifies that the syntax elements specifying the nearest depth value are not present in the syntax structure. z\_near\_flag equal to 1 specifies that the syntax elements specifying the nearest depth value are present in the syntax structure. + +**z\_far\_flag** equal to 0 specifies that the syntax elements specifying the farthest depth value are not present in the syntax structure. z\_far\_flag equal to 1 specifies that the syntax elements specifying the farthest depth value are present in the syntax structure. + +**z\_axis\_equal\_flag** equal to 0 specifies that the syntax element z\_axis\_reference\_view[ i ] is present. z\_axis\_equal\_flag equal to 1 specifies that the ZNear and ZFar values, when present, and the decoded samples of depth views, when depth\_representation\_type is equal to 0 or 2, have the same Z-axis, which is the Z-axis of the depth view indicated by the syntax element common\_z\_axis\_reference\_view. + +**common\_z\_axis\_reference\_view** specifies the view\_id value of the depth view of the Z-axis of the ZNear and ZFar values, when present, and the decoded samples of depth views, when depth\_representation\_type is equal to 0 or 2. The value of common\_z\_axis\_reference\_view shall be in the range of 0 to 1023, inclusive. + +**d\_min\_flag** equal to 0 specifies that the syntax elements specifying the minimum disparity value are not present in the syntax structure. d\_min\_flag equal to 1 specifies that the syntax elements specifying the minimum disparity value are present in the syntax structure. + +**d\_max\_flag** equal to 0 specifies that the syntax elements specifying the maximum disparity value are not present in the syntax structure. d\_max\_flag equal to 1 specifies that the syntax elements specifying the maximum disparity value are present in the syntax structure. + +**depth\_representation\_type** specifies the representation definition of decoded luma samples of depth views as specified in Table H-1. In Table H-1, disparity specifies the horizontal displacement between two texture views and Z value specifies the distance from a camera. The value of depth\_representation\_type shall be in the range of 0 to 3, inclusive, in bitstreams conforming to this version of this Specification. The values of 4 to 15, inclusive, for depth\_representation\_type are reserved for future use by ITU-T | ISO/IEC. Although the value of depth\_representation\_type is required to be in the range of 0 to 3, inclusive, in this version of this Specification, decoders shall allow values of depth\_representation\_type in the range of 4 to 15, inclusive, to appear in the syntax. Decoders conforming to this version of this Specification shall ignore all data that follow a value of depth\_representation\_type in the range of 4 to 15, inclusive, in the depth representation information SEI message. + +**Table H-1 – Definition of depth\_representation\_type** + +| depth_representation_type | Interpretation | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Each decoded luma sample value of depth views represents an inverse of Z value that is uniformly quantized into the range of 0 to 255, inclusive. | +| 1 | Each decoded luma sample value of depth views represents disparity that is uniformly quantized into the range of 0 to 255, inclusive. | +| 2 | Each decoded luma sample value of depth views represents a Z value uniformly quantized into the range of 0 to 255, inclusive. | +| 3 | Each decoded luma sample value of depth views represents a non-linearly mapped disparity, normalized in range from 0 to 255, as specified by depth_nonlinear_representation_num_minus1 and depth_nonlinear_representation_model[ i ]. | +| 4..15 | Reserved | + +**depth\_info\_view\_id[ i ]** specifies the view\_id value to which subsequent syntax elements apply. The value of depth\_info\_view\_id[ i ] shall be in the range of 0 to 1023, inclusive. + +**z\_axis\_reference\_view[ i ]** specifies the view\_id value of the depth view of the Z-axis of the ZNear[ i ] and ZFar[ i ] values, when present, and the decoded samples of the depth view with view\_id equal to depth\_info\_view\_id[ i ], when depth\_representation\_type is equal to 0 or 2. The value of z\_axis\_reference\_view[ i ] shall be in the range of 0 to 1023, inclusive. + +**disparity\_reference\_view[ i ]** specifies the view\_id value of the depth view used to derive the DMin[ i ] and Dmax[ i ] values, when present, and the decoded samples of the depth view with view\_id equal to depth\_info\_view\_id[ i ], when depth\_representation\_type is equal to 1 or 3. The value of disparity\_reference\_view[ i ] shall be in the range of 0 to 1023, inclusive. + +The variables in the x column of Table H-2 are derived as follows from the respective variables in the s, e, n, and v columns of Table H-2 as follows: + +- If $0 < e < 127$ , $x = (-1)^s * 2^{(e-31)} * (1 + n \div 2^v)$ . +- Otherwise (e is equal to 0), $x = (-1)^s * 2^{-(30+v)} * n$ . + +NOTE 2 – The above specification is similar to that found in IEC 60559. + +**Table H-2 – Association between depth parameter variables and syntax elements** + +| x | s | e | n | v | +|--------------|------------------|-----------------|----------------------|--------------------| +| ZNear[ vId ] | ZNearSign[ vId ] | ZNearExp[ vId ] | ZNearMantissa[ vId ] | ZNearManLen[ vId ] | +| ZFar[ vId ] | ZFarSign[ vId ] | ZFarExp[ vId ] | ZFarMantissa[ vId ] | ZFarManLen[ vId ] | +| DMax[ vId ] | DMaxSign[ vId ] | DMaxExp[ vId ] | DMaxMantissa[ vId ] | DMaxManLen[ vId ] | +| DMin[ vId ] | DMinSign[ vId ] | DMinExp[ vId ] | DMinMantissa[ vId ] | DMinManLen[ vId ] | + +If all\_views\_equal\_flag is equal to 0, the variables x in Table H-2 are specified as follows: + +- ZNear[ vId ]: The closest depth value for view\_id equal to vId. +- ZFar[ vId ]: The farthest depth value for view\_id equal to vId. +- DMax[ vId ]: The maximum disparity value for view\_id equal to vId. +- DMin[ vId ]: The minimum disparity value for view\_id equal to vId. + +Otherwise, the variables x in Table H-2 are specified as follows: + +- ZNear[ 0 ]: The closest depth value for all depth views. +- ZFar[ 0 ]: The farthest depth value for all depth views. +- DMax[ 0 ]: The maximum disparity value for all depth views. +- DMin[ 0 ]: The minimum disparity value for all depth views. + +The **DMin** and **DMax** values, when present, are specified in units of a luma sample width of the texture views. + +The **ZNear** and **ZFar** values, when present, are specified in units of a unit vector of the 3-dimensional coordinate system used to specify the extrinsic camera parameters as specified by the Multiview Acquisition Information SEI message associated with the respective depth views, if present. Otherwise, **ZNear** and **ZFar** values, when present, are specified in units of a unit vector of the 3-dimensional coordinate system used to specify the extrinsic camera parameters specified by the Multiview Acquisition Information SEI message associated with the respective texture views, if present. Otherwise, the units for the **ZNear** and **ZFar** values, if present, are identical but unspecified. + +**depth\_nonlinear\_representation\_num\_minus1** plus 2 specifies the number of piecewise linear segments for mapping of depth values to a scale that is uniformly quantized in terms of disparity. The value of **depth\_nonlinear\_representation\_num\_minus1** shall be in the range of 0 to 62, inclusive. + +**depth\_nonlinear\_representation\_model[ i ]** specifies the piecewise linear segments for mapping of decoded luma sample values of depth views to a scale that is uniformly quantized in terms of disparity. The value of **depth\_nonlinear\_representation\_model[ i ]** shall be in the range of 0 to 65 535, inclusive. + +NOTE 3 – When **depth\_representation\_type** is equal to 3, depth view component contains non-linearly transformed depth samples. Variable **DepthLUT[ i ]**, as specified below, is used to transform coded depth sample values from non-linear representation to the linear representation – disparity normalized in range from 0 to 255. The shape of this transform is defined by means of line-segment-approximation in two-dimensional linear-disparity-to-non-linear-disparity space. The first (0, 0) and the last (255, 255) nodes of the curve are predefined. Positions of additional nodes are transmitted in form of deviations (**depth\_nonlinear\_representation\_model[ i ]**) from the straight-line curve. These deviations are uniformly distributed along the whole range of 0 to 255, inclusive, with spacing depending on the value of **nonlinear\_depth\_representation\_num\_minus1**. + +Variable **DepthLUT[ i ]** for i in the range of 0 to 255, inclusive, is specified as follows: + +``` + +depth_nonlinear_representation_model[ 0 ] = 0 +depth_nonlinear_representation_model[depth_nonlinear_representation_num_minus1 + 2 ] = 0 +for( k=0; k<= depth_nonlinear_representation_num_minus1 + 1; ++k ) { + pos1 = ( 255 * k ) / (depth_nonlinear_representation_num_minus1 + 2 ) + dev1 = depth_nonlinear_representation_model[ k ] + pos2 = ( 255 * ( k+1 ) ) / (depth_nonlinear_representation_num_minus1 + 2 ) + dev2 = depth_nonlinear_representation_model[ k+1 ] + + x1 = pos1 - dev1 + y1 = pos1 + dev1 + x2 = pos2 - dev2 + y2 = pos2 + dev2 + + for ( x = max( x1, 0 ); x <= min( x2, 255 ); ++x ) + DepthLUT[ x ] = Clip3( 0, 255, Round( ( ( x - x1 ) * ( y2 - y1 ) ) ÷ ( x2 - x1 ) + y1 ) ) +} + +``` + +When **depth\_representation\_type** is equal to 3, **DepthLUT[ dS ]** for all decoded luma sample values dS of depth views in the range of 0 to 255, inclusive, represents disparity that is uniformly quantized into the range of 0 to 255, inclusive. + +#### H.13.2.3.1 Depth representation SEI element semantics + +The syntax structure specifies the value of an element in depth representation information. + +The **depth\_representation\_sei\_element( outSign, outExp, outMantissa, outManLen )** syntax structure sets the values of the **outSign**, **outExp**, **outMantissa**, and **outManLen** variables that represent a floating-point value. When the syntax structure is included in another syntax structure, the variable names **outSign**, **outExp**, **outMantissa**, and **outManLen** are to be interpreted as being replaced by the variable names used when the syntax structure is included. + +**da\_sign\_flag** equal to 0 indicates that the sign of the floating-point value is positive. **da\_sign\_flag** equal to 1 indicates that the sign is negative. The variable **outSign** is set equal to **da\_sign\_flag**. + +**da\_exponent** specifies the exponent of the floating-point value. The value of **da\_exponent** shall be in the range of 0 to $2^7 - 2$ , inclusive. The value $2^7 - 1$ is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value $2^7 - 1$ as indicating an unspecified value. The variable **outExp** is set equal to **da\_exponent**. + +**da\_mantissa\_len\_minus1** plus 1 specifies the number of bits in the da\_mantissa syntax element. The variable outManLen is set equal to da\_mantissa\_len\_minus1 + 1. + +**da\_mantissa** specifies the mantissa of the floating-point value. The variable outMantissa is set equal to da\_mantissa. + +#### H.13.2.43D reference displays information SEI message semantics + +When present, this SEI message shall be associated with an IDR access unit. A reference displays information message contains information about the reference display width(s) and reference viewing distance(s) as well as information about the corresponding baseline distance(s) and additional horizontal image shift(s), which form a stereo pair for the reference display width and the reference viewing distance. This information enables a view renderer to produce a proper stereo pair for the target screen width and the viewing distance. The reference display width and viewing distance values are signalled in units of centimetres. The reference baseline values shall be signalled in the same units as the x component of the translation vector in the multiview acquisition information SEI message that is valid for the same access unit. When a reference displays information SEI message is present in an access unit, the multiview acquisition information SEI message shall also be present in the same access unit. The baseline and shift information signalled for the reference display is valid for all access units they associated with and until the next IDR access unit or the next access unit containing multiview acquisition information SEI message or reference displays information SEI message. + +NOTE – The reference displays information SEI message specifies display parameters for which the 3D sequence was optimized and the corresponding reference parameters. Each reference display (i.e. a reference display width and possibly a corresponding viewing distance) is associated with one reference baseline distance. + +The following equations can be used for calculating the baseline distance and horizontal shift for the receiver's display when the ratio between the receiver's viewing distance and the reference viewing distance is the same as the ratio between the receiver screen width and the reference screen width: + +$$\text{baseline} = \text{ref\_baseline} * ( \text{ref\_display\_width} \div \text{display\_width} )$$ + +$$\text{shift} = \text{ref\_shift} * ( \text{ref\_display\_width} \div \text{display\_width} )$$ + +In the provided equations, the width of the visible part of the display used for showing the video sequence should be understood under "display width". The same equations can also be used for choosing the baseline distance and horizontal shift in cases when the viewing distance is not scaled proportionally to the screen width compared to the reference display parameters. In this case, the effect of applying these equations would be to keep the perceived depth in the same proportion to the viewing distance as in the reference setup. + +When camera parameters are updated by a multiview acquisition information SEI message in a following access unit and the baseline between the views used in the view synthesis process in the following access unit changes relative to that in the in the access unit which the reference displays information SEI belongs to, the baseline and the horizontal shift for the receiver's display in the following access unit should be modified accordingly. Let the scaling factor $s$ be equal to the ratio of the baseline between two views in the following access unit and the baseline between the same two views in the access unit, which the reference displays information SEI message belongs to, where the two views are used in the view synthesis process. Then the baseline distance for the receiver's display in the following access unit should be modified with the scaling factor $s$ relative to the baseline distance for the receiver's display in the access unit which the reference displays information SEI belongs to. The horizontal shift for the receiver's display should also be modified by scaling it with the same factor as that used to scale the baseline distance. + +**prec\_ref\_baseline** specifies the exponent of the maximum allowable truncation error for $\text{ref\_baseline}[i]$ as given by $2^{-\text{prec\_ref\_baseline}}$ . The value of **prec\_ref\_baseline** shall be in the range of 0 to 31, inclusive. + +**prec\_ref\_display\_width** specifies the exponent of the maximum allowable truncation error for $\text{ref\_display\_width}[i]$ as given by $2^{-\text{prec\_ref\_display\_width}}$ . The value of **prec\_ref\_display\_width** shall be in the range of 0 to 31, inclusive. + +**ref\_viewing\_distance\_flag** equal to 1 indicates the presence of reference viewing distance. **ref\_viewing\_distance\_flag** equal to 0 indicates that the reference viewing distance is not present in the bitstream. + +**prec\_ref\_viewing\_dist** specifies the exponent of the maximum allowable truncation error for $\text{ref\_viewing\_dist}[i]$ as given by $2^{-\text{prec\_ref\_viewing\_dist}}$ . The value of **prec\_ref\_viewing\_dist** shall be in the range of 0 to 31, inclusive. + +**num\_ref\_displays\_minus1** plus 1 specifies the number of reference displays that are signalled in the bitstream. The value of **num\_ref\_displays\_minus1** shall be in the range of 0 to 31, inclusive. + +**exponent\_ref\_baseline[i]** specifies the exponent part of the reference baseline for the $i$ -th reference display. The value of **exponent\_ref\_baseline[i]** shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified reference baseline. + +**mantissa\_ref\_baseline[i]** specifies the mantissa part of the reference baseline for the $i$ -th reference display. The length of the **mantissa\_ref\_baseline[i]** syntax element is variable and determined as follows: + +- If $\text{exponent\_ref\_baseline}[i] == 0$ , the length is $\text{Max}(0, \text{prec\_ref\_baseline} - 30)$ . + +- Otherwise ( $0 < \text{exponent\_ref\_baseline}[i] < 63$ ), the length is $\text{Max}(0, \text{exponent\_ref\_baseline}[i] + \text{prec\_ref\_baseline} - 31)$ . + +**exponent\_ref\_display\_width[i]** specifies the exponent part of the reference display width of the i-th reference display. The value of **exponent\_ref\_display\_width[i]** shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified reference display width. + +**mantissa\_ref\_display\_width[i]** specifies the mantissa part of the reference display width of the i-th reference display. The length of the **mantissa\_ref\_display\_width[i]** syntax element is variable and determined as follows: + +- If $\text{exponent\_ref\_display\_width}[i] == 0$ , the length is $\text{Max}(0, \text{prec\_ref\_display\_width} - 30)$ . +- Otherwise ( $0 < \text{exponent\_ref\_display\_width}[i] < 63$ ), the length is $\text{Max}(0, \text{exponent\_ref\_display\_width}[i] + \text{prec\_ref\_display\_width} - 31)$ . + +**exponent\_ref\_viewing\_distance[i]** specifies the exponent part of the reference viewing distance of the i-th reference display. The value of **exponent\_ref\_viewing\_distance[i]** shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value 63 as indicating an unspecified reference display width. + +**mantissa\_ref\_viewing\_distance[i]** specifies the mantissa part of the reference viewing distance of the i-th reference display. The length of the **mantissa\_ref\_viewing\_distance[i]** syntax element is variable and determined as follows: + +- If $\text{exponent\_ref\_viewing\_distance}[i] == 0$ , the length is $\text{Max}(0, \text{prec\_ref\_viewing\_distance} - 30)$ . +- Otherwise ( $0 < \text{exponent\_ref\_viewing\_distance}[i] < 63$ ), the length is $\text{Max}(0, \text{exponent\_ref\_viewing\_distance}[i] + \text{prec\_ref\_viewing\_distance} - 31)$ . + +The variables in the x column of Table H-3 are derived as follows from the respective variables or values in the s, e, and n columns of Table H-3 as follows: + +- If $0 < e < 63$ , $x = (-1)^s * 2^{(e-31)} * (1 + n \div 2^v)$ . +- Otherwise (e is equal to 0), $x = (-1)^s * 2^{-(30+v)} * n$ . + +NOTE – The above specification is similar to that found in IEC 60559. + +**Table H-3 – Association between camera parameter variables and syntax elements** + +| x | s | e | n | +|------------------------------|---|-----------------------------------------|-----------------------------------------| +| refBaseline[i] | 0 | exponent_ref_baseline[i] | mantissa_ref_baseline[i] | +| refDisplayWidth[i] | 0 | exponent_ref_display_width[i] | mantissa_ref_display_width[i] | +| refViewingDistance[i] | 0 | exponent_ref_viewing_distance[i] | mantissa_ref_viewing_distance[i] | + +**additional\_shift\_present\_flag[i]** equal to 1 indicates that the information about additional horizontal shift of the left and right views for the i-th reference display is present in the bitstream. **additional\_shift\_present\_flag[i]** equal to 0 indicates that the information about additional horizontal shift of the left and right views for the i-th reference display is not present in the bitstream. + +**num\_sample\_shift\_plus512[i]** indicates the recommended additional horizontal shift for a stereo pair corresponding to the i-th reference baseline and the i-th reference display. If $(\text{num\_sample\_shift\_plus512}[i] - 512)$ is less than 0, it is recommended that the left view of the stereo pair corresponding to the i-th reference baseline and the i-th reference display is shifted in the left direction by $(512 - \text{num\_sample\_shift\_plus512}[i])$ samples with respect to the right view of the stereo pair; if **num\_sample\_shift\_plus512[i]** is equal to 512, it is recommended that shifting is not applied; if $(\text{num\_sample\_shift\_plus512}[i] - 512)$ is greater than 0, it is recommended that the left view in the stereo pair corresponding to the i-th reference baseline and the i-th reference display should be shifted in the right direction by $(\text{num\_sample\_shift\_plus512}[i] - 512)$ samples with respect to the right view of the stereo pair. The value of **num\_sample\_shift\_plus512[i]** shall be in the range of 0 to 1023, inclusive. + +**three\_dimensional\_reference\_displays\_extension\_flag** equal to 0 indicates that no additional data follows within the reference displays SEI message. The value of **three\_dimensional\_reference\_displays\_extension\_flag** shall be equal to 0. The value of 1 for **three\_dimensional\_reference\_displays\_extension\_flag** is reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all data that follows the value of 1 for **three\_dimensional\_reference\_displays\_extension\_flag** in a reference displays SEI message. + +NOTE – Shifting the left view in the left (or right) direction by X samples with respect to the right view can be performed by the following two-step processing: + +- 1) shift the left view by X / 2 samples in the left (or right) direction, and shift the right view by X / 2 samples in the right (or left) direction +- 2) fill the left and right image margins of X / 2 samples in width in both the left and right views in background colour. + +The following pseudo code explains the recommended shifting processing in the case of shifting the left view in the left direction by X samples with respect to the right view. + +``` +for ( i = X / 2; i < width - X / 2; i++ ) { + for ( j = 0; j < height; j++ ) { + left_view[ j ][ i ] = left_view[ j ][ i + X / 2 ] + right_view[ j ][ width - 1 - i ] = right_view[ j ][ width - 1 - i - X / 2 ] + } +} +for ( i = 0; i < X / 2; i++ ) { + for ( j = 0; j < height; j++ ) { + left_view[ j ][ width - 1 - i ] = left_view[ j ][ i ] = BackgroundColour + right_view[ j ][ width - 1 - i ] = right_view[ j ][ i ] = BackgroundColour + } +} +``` + +The following pseudo code explains the recommended shifting processing in the case of shifting the left view in the right direction by X samples with respect to the right view. + +``` +for ( i = X / 2; i < width - X / 2; i++ ) { + for ( j = 0; j < height; j++ ) { + left_view[ j ][ width - 1 - i ] = left_view[ j ][ width - 1 - i - X / 2 ] + right_view[ j ][ i ] = right_view[ j ][ i + X / 2 ] + } +} +for ( i = 0; i < X / 2; i++ ) { + for ( j = 0; j < height; j++ ) { + left_view[ j ][ width - 1 - i ] = left_view[ j ][ i ] = BackgroundColour + right_view[ j ][ width - 1 - i ] = right_view[ j ][ i ] = BackgroundColour + } +} +``` + +BackgroundColour may take different values in different systems, for example black or grey. + +### H.13.2.5 Depth timing SEI message semantics + +The depth timing SEI message indicates the acquisition time of the depth view components of one or more access units relative to the DPB output time of the same access units. The depth timing SEI message may be present in any access unit and it pertains until the end of the coded video sequence or until the next depth timing SEI message, whichever is earlier in decoding order. The access units that the message pertains to are referred to as the target access unit set. + +**per\_view\_depth\_timing\_flag** equal to 0 specifies that all the depth view components within the target access unit set have the same acquisition time offset relative to the DPB output time of the respective access unit in the target access unit set. The single occurrence of the **depth\_timing\_offset** structure specifies this acquisition time offset. + +**per\_view\_depth\_timing\_flag** equal to 1 specifies that a **depth\_timing\_offset** syntax structure is present for each depth view in ascending order of view order index values for the depth views and specifies the acquisition time offset for that view. + +#### H.13.2.5.1 Depth timing offset semantics + +**offset\_len\_minus1** specifies the length of the **depth\_disp\_delay\_offset\_fp** syntax element. + +**depth\_disp\_delay\_offset\_fp** and **depth\_disp\_delay\_offset\_dp** specify that the acquisition offset of the respective depth view component or components relative to the DPB output time of the access unit containing the depth view component or components is equal to $\text{depth\_disp\_delay\_offset\_fp} \div 2^{\text{depth\_disp\_delay\_offset\_dp}}$ in units of clock ticks as specified in Annex C. + +The length of **depth\_disp\_delay\_offset\_fp** syntax element is equal to **offset\_len\_minus1** + 1. + +If **depth\_disp\_delay\_offset\_fp** is not present, it is inferred to be equal to 0. If **depth\_disp\_delay\_offset\_dp** is not present, it is inferred to be equal to 0. + +### H.13.2.6 Alternative depth information SEI message semantics + +The alternative depth information SEI message indicates that the view components of one output view contain samples of multiple distinct spatially packed constituent pictures. The related output view is not suitable to be displayed directly. This SEI message can be used by the application after the decoder output to rearrange the samples to produce additional views that are appropriate for display or use by a server for other purposes (which are outside the scope of this Recommendation | International Standard). + +When the alternative depth information SEI message is present, the texture and depth views referred to by this SEI message shall conform to the specifications in Annexes H and I, ChromaArrayType shall be equal to 1 (4:2:0), bit\_depth\_luma\_minus8 shall be equal to 0, bit\_depth\_chroma\_minus8 shall be equal to 0, and the depth representation information SEI message shall be present. The depth\_representation\_type is defined in the depth representation information SEI message. The depth representation is only carried in the luma component. + +The alternative depth information SEI message, when present, shall be associated with an IDR access unit. The information signalled in this SEI message applies to all the access units in the coded video sequence. Also, num\_anchor\_refs\_l0[ i ], num\_anchor\_refs\_l1[ i ], num\_non\_anchor\_refs\_l0[ i ] and num\_non\_anchor\_refs\_l1[ i ] shall be equal to 0 in the active SPS RBSP syntax structure for the coded video sequence and avc\_3d\_extension\_flag shall be equal to 0 in all VCL NAL units of the coded video sequence. + +NOTE 1 – These constraints disable inter-view and inter-component prediction. + +In such a coded video sequence, there shall be two output views. The base view is a complete view and the non-base view contains a packing arrangement of 1 to 4 additional views with half the width and half the height of the base view. Such lower-resolution views are referred to as constituent pictures herein. + +NOTE 2 – The view\_id of the non-base view is not used in any particular way for this SEI message. + +All constituent pictures have a width and a height equal to $((\text{pic\_width\_in\_mbs\_minus1} + 1) * 8)$ and $((\text{pic\_height\_in\_map\_unit\_minus1} + 1) * 8)$ in luma samples, respectively. frame\_mbs\_only\_flag shall be equal to 1. The variable i, with a value from 0 to num\_constituent\_views\_gvd\_minus1 + 1, inclusive, indicates the location of the constituent pictures in the non-base texture view as specified in Table H-4. i equal to 0 indicates the base texture view. i greater than 0 indicates the constituent texture view. + +**Table H-4 – Locations of the top-left luma samples of constituent pictures packed in a non-base texture view relative to the top-left luma sample of this picture** + +| Constituent picture index i | Location of the top-left luma sample in a non-base texture view | +|-----------------------------|------------------------------------------------------------------------------------| +| 1 | ( 0, 0 ) | +| 2 | ( 0, ( pic height in map unit minus1 + 1 ) * 8 ) | +| 3 | ( ( pic width in mbs minus1 + 1 ) * 8, 0 ) | +| 4 | ( ( pic width in mbs minus1 + 1 ) * 8, ( pic height in map unit minus1 + 1 ) * 8 ) | + +The decoded depth views have the same structure as the decoded texture views, i.e., they consist of a base depth view (i equal to 0) and a non-base depth view. The non-base depth view contains up to four constituent depth pictures (i in the range of 1 to 4) for the constituent views. The constituent depth pictures are packed in the non-base depth view in the same arrangement as the constituent texture pictures as specified in Table H-4. + +This arrangement of texture and depth constituent views is referred to as global view and depth (GVD) information. + +**depth\_type** shall be equal to 0. Other values are reserved for future use by ITU-T | ISO/IEC and shall not be present in bitstreams conforming to this Specification. Decoders shall ignore alternative depth information SEI messages in which such other values are present. + +**num\_constituent\_views\_gvd\_minus1** plus 1 identifies the number of constituent texture pictures packed into each texture component of the non-base view. num\_constituent\_views\_gvd\_minus1 shall be in the range of 0 to 3, inclusive. + +**depth\_present\_gvd\_flag** equal to 1 indicates that constituent depth pictures are packed into the depth components of the non-base view, with a packing arrangement as described above. depth\_present\_gvd\_flag equal to 0 specifies that the depth component of the non-base view is not present. + +Each constituent picture in the depth component of the non-base view is associated with a constituent picture in the texture component of the non-base view in the same relative location. The number of depth views in the coded video sequence is equal to 1 + depth\_present\_gvd\_flag. The depth component of the base view shall always be present, independent of the value of depth\_present\_gvd\_flag. + +NOTE 3 – The following SEI message parameters can be used along with the decoded depth components to project samples from the base view into the coordinates of constituent views such that reconstructed views can be generated by combining projected samples and samples from the constituent views. + +The function $\text{binToFp}(s, e, n, v)$ is specified as follows: + +$$\text{binToFp}(s, e, n, v) = (-1)^s * (e == 0 ? (2^{(30+v)} * n) : (2^{(e-31)} * (1 + n \div 2^v))) \quad (\text{H-1})$$ + +NOTE 4 – The above specification is similar to what is found in IEC 60559:1989, Binary floating-point arithmetic for microprocessor systems. + +**z\_gvd\_flag** equal to 1 indicates the presence of the syntax elements $\text{sign\_gvd\_z\_near\_flag}[i]$ , $\text{exp\_gvd\_z\_near}[i]$ , $\text{man\_len\_gvd\_z\_near\_minus1}[i]$ , $\text{man\_gvd\_z\_near}[i]$ , $\text{sign\_gvd\_z\_far\_flag}[i]$ , $\text{exp\_gvd\_z\_far}[i]$ , $\text{man\_len\_gvd\_z\_far\_minus1}[i]$ , and $\text{man\_gvd\_z\_far}[i]$ , for $i$ in the range of 0 to $\text{num\_constituent\_views\_gvd\_minus1} + 1$ , inclusive. $\text{z\_gvd\_flag}$ equal to 0 indicates that these syntax elements are not present. + +**intrinsic\_param\_gvd\_flag** equal to 1 indicates the presence of intrinsic camera parameter syntax elements. $\text{intrinsic\_param\_gvd\_flag}$ equal to 0 indicates that these syntax elements are not present. + +**rotation\_gvd\_flag** equal to 1 indicates the presence of rotation camera parameter syntax elements. $\text{rotation\_gvd\_flag}$ equal to 0 indicates that these syntax elements are not present. When $\text{rotation\_gvd\_flag}$ is 0, a default rotation camera parameter of a unit matrix value is inferred. + +**translation\_gvd\_flag** equal to 1 indicates the presence of horizontal translation camera parameter syntax elements. $\text{translation\_gvd\_flag}$ equal to 0 indicates that these syntax elements are not present. + +**sign\_gvd\_z\_near\_flag[i]** equal to 0 indicates that the sign of the nearest depth value of the $i$ -th camera is positive. $\text{sign\_gvd\_z\_near}[i]$ equal to 1 indicates that the sign of the nearest depth value of the $i$ -th camera is negative. + +**exp\_gvd\_z\_near[i]** specifies the exponent part of the nearest depth value of the $i$ -th camera. The value of $\text{exp\_gvd\_z\_near}[i]$ shall be in the range of 0 to 126, inclusive. The value 127 is reserved for future use by ITU-T | ISO/IEC. When $\text{exp\_gvd\_z\_near}[i]$ is equal to 127, the value of $\text{zNear}[i]$ is unspecified. + +**man\_len\_gvd\_z\_near\_minus1[i]** plus 1 specifies the length in bits of the mantissa of the nearest depth value of the $i$ -th camera. The value of $\text{man\_len\_gvd\_z\_near\_minus1}[i]$ shall be in the range of 0 to 31, inclusive. + +**man\_gvd\_z\_near[i]** specifies the mantissa part of the nearest depth value of the $i$ -th camera. The length of $\text{man\_gvd\_z\_near}[i]$ syntax elements is $\text{man\_len\_gvd\_z\_near\_minus1}[i] + 1$ bits. + +When $\text{exp\_gvd\_z\_near}[i]$ is not equal to 127, $\text{zNear}[i]$ is set equal to $\text{binToFp}(\text{sign\_gvd\_z\_near\_flag}[i], \text{exp\_gvd\_z\_near}[i], \text{man\_gvd\_z\_near}[i], \text{man\_len\_gvd\_z\_near\_minus1}[i] + 1)$ . + +**sign\_gvd\_z\_far\_flag[i]** equal to 0 indicates that the sign of the farthest depth value of the $i$ -th camera is positive. $\text{sign\_gvd\_z\_far\_flag}[i]$ equal to 1 indicates that the sign of the farthest depth value of the $i$ -th camera is negative. + +**exp\_gvd\_z\_far[i]** specifies the exponent part of the farthest depth value of the $i$ -th camera. The value of $\text{exp\_gvd\_z\_far}[i]$ shall be in the range of 0 to 126, inclusive. The value 127 is reserved for future use by ITU-T | ISO/IEC. When $\text{exp\_gvd\_z\_far}[i]$ is equal to 127, the value of $\text{zFar}[i]$ is unspecified. + +**man\_len\_gvd\_z\_far\_minus1[i]** plus 1 specifies the length in bits of the mantissa of the farthest depth value of the $i$ -th camera. The value of $\text{man\_len\_gvd\_z\_far\_minus1}[i]$ shall be in the range of 0 to 31, inclusive. + +**man\_gvd\_z\_far[i]** specifies the mantissa part of the farthest depth value of the $i$ -th camera. The length of $\text{man\_gvd\_z\_far}[i]$ syntax elements is $\text{man\_len\_gvd\_z\_far\_minus1}[i] + 1$ bits. + +When $\text{exp\_gvd\_z\_far}[i]$ is not equal to 127, $\text{zFar}[i]$ is set equal to $\text{binToFp}(\text{sign\_gvd\_z\_far\_flag}[i], \text{exp\_gvd\_z\_far}[i], \text{man\_gvd\_z\_far}[i], \text{man\_len\_gvd\_z\_far\_minus1}[i] + 1)$ . + +**prec\_gvd\_focal\_length** specifies the exponent of the maximum allowable truncation error for $\text{focalLengthX}[i]$ and $\text{focalLengthY}[i]$ as given by $2^{-\text{prec\_gvd\_focal\_length}}$ . The value of $\text{prec\_gvd\_focal\_length}$ shall be in the range of 0 to 31, inclusive. + +**prec\_gvd\_principal\_point** specifies the exponent of the maximum allowable truncation error for $\text{principalPointX}[i]$ and $\text{principalPointY}[i]$ as given by $2^{-\text{prec\_gvd\_principal\_point}}$ . The value of $\text{prec\_gvd\_principal\_point}$ shall be in the range of 0 to 31, inclusive. + +**prec\_gvd\_rotation\_param** specifies the exponent of the maximum allowable truncation error for $r[i][j][k]$ as given by $2^{-\text{prec\_gvd\_rotation\_param}}$ . The value of $\text{prec\_gvd\_rotation\_param}$ shall be in the range of 0 to 31, inclusive. + +**prec\_gvd\_translation\_param** specifies the exponent of the maximum allowable truncation error for $tX[i]$ as given by $2^{-\text{prec\_gvd\_translation\_param}}$ . The value of $\text{prec\_gvd\_translation\_param}$ shall be in the range of 0 to 31, inclusive. + +**sign\_gvd\_focal\_length\_x[i]** equal to 0 indicates that the sign of the focal length of the $i$ -th camera in the horizontal direction is positive. $\text{sign\_gvd\_focal\_length\_x}[i]$ equal to 1 indicates that the sign of the focal length of the $i$ -th camera in the horizontal direction is negative. + +**exp\_gvd\_focal\_length\_x[ i ]** specifies the exponent part of the focal length of the i-th camera in the horizontal direction. The value of exp\_gvd\_focal\_length\_x[ i ] shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. When exp\_gvd\_focal\_length\_x[ i ] is equal to 63, the value of focal length of the horizontal direction for the i-th camera is unspecified. + +**man\_gvd\_focal\_length\_x[ i ]** specifies the mantissa part of the focal length of the i-th camera in the horizontal direction. The length v of the man\_gvd\_focal\_length\_x[ i ] syntax element is determined as follows: + +- If exp\_gvd\_focal\_length\_x[ i ] is equal to 0, the length v is set equal to $\text{Max}( 0, \text{prec\_gvd\_focal\_length} - 30 )$ . +- Otherwise (exp\_gvd\_focal\_length\_x[ i ] is in the range of 1 to 62, inclusive), the length v is $\text{Max}( 0, \text{exp\_gvd\_focal\_length\_x}[ i ] + \text{prec\_gvd\_focal\_length} - 31 )$ . + +When exp\_gvd\_focal\_length\_x[ i ] is not equal to 63, the variable focalLengthX[ i ] is set equal to $\text{binToFp}( \text{sign\_gvd\_focal\_length\_x}[ i ], \text{exp\_gvd\_focal\_length\_x}[ i ], \text{man\_gvd\_focal\_length\_x}[ i ], v )$ . + +**sign\_gvd\_focal\_length\_y[ i ]** equal to 0 indicates that the sign of the focal length of the i-th camera in the vertical direction is positive. sign\_gvd\_focal\_length\_y[ i ] equal to 1 indicates that the sign of the focal length of the i-th camera in the vertical direction is negative. + +**exp\_gvd\_focal\_length\_y[ i ]** specifies the exponent part of the focal length of the i-th camera in the vertical direction. The value of exp\_gvd\_focal\_length\_y[ i ] shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. When exp\_gvd\_focal\_length\_y[ i ] is equal to 63, the value of focal length of the vertical direction is unspecified. + +**man\_gvd\_focal\_length\_y[ i ]** specifies the mantissa part of the focal length of the i-th camera in the vertical direction. + +The length v of the man\_gvd\_focal\_length\_y[ i ] syntax element is determined as follows: + +- If exp\_gvd\_focal\_length\_y[ i ] is equal to 0, the length v is set equal to $\text{Max}( 0, \text{prec\_gvd\_focal\_length} - 30 )$ . +- Otherwise (exp\_gvd\_focal\_length\_y[ i ] is in the range of 1 to 62, inclusive), the length v is set equal to $\text{Max}( 0, \text{exp\_gvd\_focal\_length\_y}[ i ] + \text{prec\_gvd\_focal\_length} - 31 )$ . + +When exp\_gvd\_focal\_length\_y[ i ] is not equal to 63, the variable focalLengthY[ i ] is set equal to $\text{binToFp}( \text{sign\_gvd\_focal\_length\_y}[ i ], \text{exp\_gvd\_focal\_length\_y}[ i ], \text{man\_gvd\_focal\_length\_y}[ i ], v )$ . + +**sign\_gvd\_principal\_point\_x[ i ]** equal to 0 indicates that the sign of the principal point of the i-th camera in the horizontal direction is positive. sign\_gvd\_principal\_point\_x[ i ] equal to 1 indicates that the sign of the principal point of the i-th camera in the horizontal direction is negative. + +**exp\_gvd\_principal\_point\_x[ i ]** specifies the exponent part of the principal point of the i-th camera in the horizontal direction. The value of exp\_gvd\_principal\_point\_x[ i ] shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. When exp\_gvd\_principal\_point\_x[ i ] is equal to 63, the value of principal point in the horizontal direction for the i-th camera is unspecified. + +**man\_gvd\_principal\_point\_x[ i ]** specifies the mantissa part of the principal point of the i-th camera in the horizontal direction The length v of the man\_gvd\_principal\_point\_x[ i ] syntax element in units of bits is determined as follows: + +- If exp\_gvd\_principal\_point\_x[ i ] is equal to 0, the length v is set equal to $\text{Max}( 0, \text{prec\_gvd\_principal\_point} - 30 )$ . +- Otherwise (exp\_gvd\_principal\_point\_x[ i ] is in the range of 1 to 62, inclusive), the length v is set equal to $\text{Max}( 0, \text{exp\_gvd\_principal\_point\_x}[ i ] + \text{prec\_gvd\_principal\_point} - 31 )$ . + +When exp\_gvd\_principal\_point\_x[ i ] is not equal to 63, the variable principalPointX[ i ] is set equal to $\text{binToFp}( \text{sign\_gvd\_principal\_point\_x}[ i ], \text{exp\_gvd\_principal\_point\_x}[ i ], \text{man\_gvd\_principal\_point\_x}[ i ], v )$ . + +**sign\_gvd\_principal\_point\_y[ i ]** equal to 0 indicates that the sign of the principal point of the i-th camera in the vertical direction is positive. sign\_gvd\_principal\_point\_y[ i ] equal to 1 indicates that the sign of the principal point of the i-th camera in the vertical direction is negative. + +**exp\_gvd\_principal\_point\_y[ i ]** specifies the exponent part of the principal point of the i-th camera in the vertical direction. The value of exp\_gvd\_principal\_point\_y[ i ] shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. When exp\_gvd\_principal\_point\_y[ i ] is equal to 63, the value of principal point in the vertical direction for the i-th camera is unspecified. + +**man\_gvd\_principal\_point\_y[ i ]** specifies the mantissa part of the principal point of the i-th camera in the vertical direction The length v of the man\_gvd\_principal\_point\_y[ i ] syntax element in units of bits is determined as follows: + +- If exp\_gvd\_principal\_point\_y[ i ] is equal to 0, the length v is set equal to $\text{Max}( 0, \text{prec\_gvd\_principal\_point} - 30 )$ . + +- Otherwise ( $\text{exp\_gvd\_principal\_point\_y}[i]$ is in the range of 1 to 62, inclusive), the length $v$ is set equal to $\text{Max}(0, \text{exp\_gvd\_principal\_point\_y}[i] + \text{prec\_gvd\_principal\_point} - 31)$ . + +When $\text{exp\_gvd\_principal\_point\_y}[i]$ is not equal to 63, the variable $\text{principalPointY}[i]$ is set equal to $\text{binToFp}(\text{sign\_gvd\_principal\_point\_y}[i], \text{exp\_gvd\_principal\_point\_y}[i], \text{man\_gvd\_principal\_point\_y}[i], v)$ . + +**sign\_gvd\_r[i][j][k]** equal to 0 indicates that the sign of the $(j, k)$ component of the rotation matrix for the $i$ -th camera is positive. **sign\_gvd\_r[i][j][k]** equal to 1 indicates that the sign of the $(j, k)$ component of the rotation matrix for the $i$ -th camera is negative. + +**exp\_gvd\_r[i][j][k]** specifies the exponent part of the $(j, k)$ component of the rotation matrix for the $i$ -th camera. The value of $\text{exp\_gvd\_r}[i][j][k]$ shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. When $\text{exp\_gvd\_r}[i][j][k]$ is equal to 63, the value of rotation matrix is unspecified. + +**man\_gvd\_r[i][j][k]** specifies the mantissa part of the $(j, k)$ component of the rotation matrix for the $i$ -th camera. + +The length $v$ of the $\text{man\_gvd\_r}[i][j][k]$ syntax element in units of bits is determined as follows: + +- If $\text{exp\_gvd\_r}[i][j][k]$ is equal to 0, the length $v$ is set equal to $\text{Max}(0, \text{prec\_gvd\_rotation\_param} - 30)$ . +- Otherwise ( $\text{exp\_gvd\_r}[i][j][k]$ is in the range of 1 to 62, inclusive), the length $v$ is set equal to $\text{Max}(0, \text{exp\_gvd\_r}[i][j][k] + \text{prec\_gvd\_rotation\_param} - 31)$ . + +When $\text{exp\_gvd\_r}[i][j][k]$ is not equal to 63, the variable $r[i][j][k]$ is set equal to $\text{binToFp}(\text{sign\_gvd\_r}[i][j][k], \text{exp\_gvd\_r}[i][j][k], \text{man\_gvd\_r}[i][j][k], v)$ . + +The rotation matrix $R[i]$ for $i$ -th camera is represented as follows: + +$$R[i] = \begin{bmatrix} r[i][0][0] & r[i][0][1] & r[i][0][2] \\ r[i][1][0] & r[i][1][1] & r[i][1][2] \\ r[i][2][0] & r[i][2][1] & r[i][2][2] \end{bmatrix} \quad (\text{H-2})$$ + +**sign\_gvd\_t\_x[i]** equal to 0 indicates that the sign of the horizontal component of the translation vector for the $i$ -th camera is positive. **sign\_gvd\_t\_x[i]** equal to 1 indicates that the sign of the horizontal component of the translation vector for the $i$ -th camera is negative. + +**exp\_gvd\_t\_x[i]** specifies the exponent part of the horizontal component of the translation vector for the $i$ -th camera. The value of $\text{exp\_gvd\_t\_x}[i]$ shall be in the range of 0 to 62, inclusive. The value 63 is reserved for future use by ITU-T | ISO/IEC. When $\text{exp\_gvd\_t\_x}[i]$ is equal to 63, the value of the translation vector is unspecified. + +**man\_gvd\_t\_x[i]** specifies the mantissa part of the horizontal component of the translation vector for the $i$ -th camera. + +The length $v$ of the $\text{man\_gvd\_t\_x}[i]$ syntax element in units of bits is determined as follows: + +- If $\text{exp\_gvd\_t\_x}[i]$ is equal to 0, the length $v$ is set equal to $\text{Max}(0, \text{prec\_gvd\_translation\_param} - 30)$ . +- Otherwise ( $\text{exp\_gvd\_t\_x}[i]$ is in the range of 1 to 62, inclusive), the length $v$ is set equal to $\text{Max}(0, \text{exp\_gvd\_t\_x}[i] + \text{prec\_gvd\_translation\_param} - 31)$ . + +When $\text{exp\_gvd\_t\_x}[i]$ is not equal to 63, the variable $tX[i]$ is set equal to $\text{binToFp}(\text{sign\_gvd\_t\_x}[i], \text{exp\_gvd\_t\_x}[i], \text{man\_gvd\_t\_x}[i], v)$ . + +### H.13.2.7 Depth sampling information SEI message semantics + +The depth sampling information SEI message specifies the depth sample size relative to luma texture sample size. In addition, the depth sampling information SEI message specifies the depth sampling grid position of one or more depth view components of the associated access unit relative to the sampling grid of the texture view components of the same access unit with the same $\text{view\_id}$ value. When present, the depth sampling information SEI message shall be associated with an IDR access unit. The semantics of the message are valid for the current coded video sequence. + +NOTE – The depth sample size and the depth sampling grid position are indicated for frame or field view components that are present in the associated IDR access unit. In subsequent access units in the coded video sequence the depth view components may have different values of $\text{field\_pic\_flag}$ and $\text{bottom\_field\_flag}$ compared to those of the depth view components of the IDR access unit. Likewise, in subsequent access units in the coded video sequence the texture view components may have different values of $\text{field\_pic\_flag}$ and $\text{bottom\_field\_flag}$ compared to those of the texture view components of the IDR access unit. The depth sample size and depth sampling grid position should be modified according to the values of $\text{field\_pic\_flag}$ and $\text{bottom\_field\_flag}$ of the texture and depth view components of an access unit compared to those of the IDR access unit. + +**dttsr\_x\_mul** and **dttsr\_x\_dp** indicate that the width of a depth sample relative to the width of a luma texture sample is approximately $\text{dttsr\_x\_mul} \div 2^{\text{dttsr\_x\_dp}}$ . When $\text{dttsr\_x\_mul}$ is not present, it is inferred to be equal to 1. When $\text{dttsr\_x\_dp}$ is not present, it is inferred to be equal to 0. The value of 0 for $\text{dttsr\_x\_mul}$ is reserved. + +**dttsr\_y\_mul** and **dttsr\_y\_dp** indicate that the height of a depth sample relative to the height of a luma texture sample is approximately $\text{dttsr\_y\_mul} \div 2^{\text{dttsr\_y\_dp}}$ . When **dttsr\_y\_mul** is not present, it is inferred to be equal to 1. When **dttsr\_y\_dp** is not present, it is inferred to be equal to 0. The value of 0 for **dttsr\_y\_mul** is reserved. + +**per\_view\_depth\_grid\_pos\_flag** equal to 0 specifies that the depth sampling grid position information is the same for all depth views for which there is a texture view with the same **view\_id** present. The single occurrence of the **depth\_grid\_position()** syntax structure indicates the depth sampling grid position. **per\_view\_depth\_grid\_pos\_flag** equal to 1 specifies that a **depth\_grid\_position()** syntax structure is present for indicated depth views. + +**num\_video\_plus\_depth\_views\_minus1** (when present) plus 1 specifies the number of views for which the depth sampling grid position information is present in this SEI message. + +**depth\_grid\_view\_id[i]** specifies the i-th **view\_id** value for which the depth sampling grid position information is specified with the **depth\_grid\_position()** structure following in the syntax structure. + +#### H.13.2.7.1 Depth grid position semantics + +**depth\_grid\_pos\_x\_fp**, **depth\_grid\_pos\_x\_dp** and **depth\_grid\_pos\_x\_sign\_flag** indicate that the location of the horizontal position of the top-left sample in the sampling grid for a depth view component, relative to the location of the top-left sample in the sampling grid for the luma component of the texture view component with the same value of **view\_id**, is equal to $(1 - 2 * \text{depth\_grid\_pos\_x\_sign\_flag}) * (\text{depth\_grid\_pos\_x\_fp} \div 2^{\text{depth\_grid\_pos\_x\_dp}})$ . + +When **depth\_grid\_pos\_x\_fp**, **depth\_grid\_pos\_x\_dp**, and **depth\_grid\_pos\_x\_sign\_flag** are not present, they should be inferred to be equal to 0. + +**depth\_grid\_pos\_y\_fp**, **depth\_grid\_pos\_y\_dp** and **depth\_grid\_pos\_y\_sign\_flag** indicate that the location of the vertical position of the top-left sample in the sampling grid for a depth view component, relative to the location of the top-left sample in the sampling grid for the luma component of the texture view component with the same value of **view\_id**, is equal to $(1 - 2 * \text{depth\_grid\_pos\_y\_sign\_flag}) * (\text{depth\_grid\_pos\_y\_fp} \div 2^{\text{depth\_grid\_pos\_y\_dp}})$ . + +When **depth\_grid\_pos\_y\_fp**, **depth\_grid\_pos\_y\_dp**, and **depth\_grid\_pos\_y\_sign\_flag** are not present, they should be inferred to be equal to 0. + +## H.14 Video usability information + +### H.14.1 MVCD VUI parameters extension syntax + +| mvcv_vui_parameters_extension() { | C | Descriptor | +|---------------------------------------------------------------------------------------------|---|------------| +|   vui_mvcv_num_ops_minus1 | 0 | ue(v) | +|   for ( i = 0; i <= vui_mvcv_num_ops_minus1; i++ ) { | | | +|     vui_mvcv_temporal_id[ i ] | 0 | u(3) | +|     vui_mvcv_num_target_output_views_minus1[ i ] | 0 | ue(v) | +|     for ( j = 0; j <= vui_mvcv_num_target_output_views_minus1[ i ]; j++ ) { | | | +|       vui_mvcv_view_id[ i ][ j ] | 0 | ue(v) | +|       vui_mvcv_depth_flag[ i ][ j ] | 0 | u(1) | +|       vui_mvcv_texture_flag[ i ][ j ] | 0 | u(1) | +|     } | | | +|     vui_mvcv_timing_info_present_flag[ i ] | 0 | u(1) | +|     if( vui_mvcv_timing_info_present_flag[ i ] ) { | | | +|       vui_mvcv_num_units_in_tick[ i ] | 0 | u(32) | +|       vui_mvcv_time_scale[ i ] | 0 | u(32) | +|       vui_mvcv_fixed_frame_rate_flag[ i ] | 0 | u(1) | +|     } | | | +|     vui_mvcv_nal_hrd_parameters_present_flag[ i ] | 0 | u(1) | +|     if( vui_mvcv_nal_hrd_parameters_present_flag[ i ] ) | | | +|       hrd_parameters( ) | 0 | | +|     vui_mvcv_vcl_hrd_parameters_present_flag[ i ] | 0 | u(1) | +|     if( vui_mvcv_vcl_hrd_parameters_present_flag[ i ] ) | | | +|       hrd_parameters( ) | 0 | | +|     if( vui_mvcv_nal_hrd_parameters_present_flag[ i ] | | | +|       vui_mvcv_vcl_hrd_parameters_present_flag[ i ] ) | | | +|       vui_mvcv_low_delay_hrd_flag[ i ] | 0 | u(1) | +|       vui_mvcv_pic_struct_present_flag[ i ] | 0 | u(1) | +|     } | | | +|   } | | | + +### H.14.2 MVCD VUI parameters extension semantics + +The MVCD VUI parameters extension specifies VUI parameters that apply to one or more operation points for the coded video sequence. In Annex C it is specified which of the HRD parameter sets specified in the MVCD VUI parameters extension are used for conformance checking. All MVCD VUI parameters extensions that are referred to by a coded video sequence shall be identical. + +Some texture and depth views identified by `vui_mvcv_view_id[ i ][ j ]` may not be present in the coded video sequence. Some temporal subsets identified by `vui_mvcv_temporal_id[ i ]` may not be present in the coded video sequence. + +`vui_mvcv_num_ops_minus1` plus 1 specifies the number of operation points for which timing information, NAL HRD parameters, VCL HRD parameters, and the `pic_struct_present_flag` may be present. The value of `vui_mvcv_num_ops_minus1` shall be in the range of 0 to 1023, inclusive. + +`vui_mvcv_temporal_id[ i ]` indicates the maximum value of `temporal_id` for all VCL NAL units in the representation of the i-th operation point. + +`vui_mvcv_num_target_output_views_minus1[ i ]` plus one specifies the number of target output views for the i-th operation point. The value of `vui_mvcv_num_target_output_views_minus1[ i ]` shall be in the range of 0 to 1023, inclusive. + +`vui_mvcv_view_id[ i ][ j ]` indicates the j-th target output view in the i-th operation point. The value of `vui_mvcv_view_id[ i ][ j ]` shall be in the range of 0 to 1023, inclusive. + +**vui\_mvcd\_depth\_flag[ i ][ j ]** equal to 0 specifies that no depth view with view\_id equal to **vui\_mvcd\_view\_id[ i ][ j ]** is included in the j-th operation point. **vui\_mvcd\_depth\_flag[ i ][ j ]** equal to 1 specifies that the depth view with view\_id equal to **vui\_mvcd\_view\_id[ i ][ j ]** is included in the j-th operation point. + +The value of **vuimvcdOpDepthPresent[ i ]** is derived as follows: + +``` +vuimvcdOpDepthPresent[ i ] = 0 +for( k = 0; k < vui_mvcd_num_target_output_views_minus1[ i ]; k++ ) + vuimvcdOpDepthPresent[ i ] = vuimvcdOpDepthPresent[ i ] | vui_mvcd_depth_flag[ i ][ k ] +``` + +**vui\_mvcd\_texture\_flag[ i ][ j ]** equal to 0 specifies that no texture view with view\_id equal to **vui\_mvcd\_view\_id[ i ][ j ]** is included in the j-th operation point. **vui\_mvcd\_depth\_flag[ i ][ j ]** equal to 1 specifies that the texture view with view\_id equal to **vui\_mvcd\_view\_id[ i ][ j ]** is included in the j-th operation point. When **vui\_mvcd\_depth\_flag[ i ][ j ]** is equal to 0, **vui\_mvcd\_texture\_flag[ i ][ j ]** shall be equal to 1. + +The following syntax elements apply to the coded video sequence that is obtained by the sub-bitstream extraction process as specified in clause H.8.5.3 with **tIdTarget** equal to **vui\_mvcd\_temporal\_id[ i ]**, **viewIdTargetList** containing **vui\_mvcd\_view\_id[ i ][ j ]** for all j in the range of 0 to **vui\_mvcd\_num\_target\_output\_views\_minus1[ i ]**, inclusive, for which **vui\_mvcd\_texture\_flag[ i ][ j ]** is equal to 1, **depthPresentFlagTarget** equal to **vuimvcdOpDepthPresent[ i ]**, and, if **vuimvcdOpDepthPresent[ i ]** is equal to 1, **viewIdDepthTargetList** containing **vui\_mvcd\_view\_id[ i ][ j ]** for all j in the range of 0 to **vui\_mvcd\_num\_target\_output\_views\_minus1[ i ]**, inclusive, for which **vui\_mvcd\_depth\_flag[ i ][ j ]** is equal to 1 as the inputs and the i-th sub-bitstream as the output. + +**vui\_mvcd\_timing\_info\_present\_flag[ i ]** equal to 1 specifies that **vui\_mvcd\_num\_units\_in\_tick[ i ]**, **vui\_mvcd\_time\_scale[ i ]**, and **vui\_mvcd\_fixed\_frame\_rate\_flag[ i ]** for the i-th sub-bitstream are present in the MVCD VUI parameters extension. **vui\_mvcd\_timing\_info\_present\_flag[ i ]** equal to 0 specifies that **vui\_mvcd\_num\_units\_in\_tick[ i ]**, **vui\_mvcd\_time\_scale[ i ]**, and **vui\_mvcd\_fixed\_frame\_rate\_flag[ i ]** for the i-th sub-bitstream are not present in the MVCD VUI parameters extension. + +The following syntax elements for the i-th sub-bitstream are specified using references to Annex E. For these syntax elements the same semantics and constraints as the ones specified in Annex E apply, as if these syntax elements **vui\_mvcd\_num\_units\_in\_tick[ i ]**, **vui\_mvcd\_time\_scale[ i ]**, **vui\_mvcd\_fixed\_frame\_rate\_flag[ i ]**, **vui\_mvcd\_nal\_hrd\_parameters\_present\_flag[ i ]**, **vui\_mvcd\_vcl\_hrd\_parameters\_present\_flag[ i ]**, **vui\_mvcd\_low\_delay\_hrd\_flag[ i ]**, and **vui\_mvcd\_pic\_struct\_present\_flag[ i ]** were present as the syntax elements **num\_units\_in\_tick**, **time\_scale**, **fixed\_frame\_rate\_flag**, **nal\_hrd\_parameters\_present\_flag**, **vcl\_hrd\_parameters\_present\_flag**, **low\_delay\_hrd\_flag**, and **pic\_struct\_present\_flag**, respectively, in the VUI parameters of the active MVCD sequence parameter sets for the i-th sub-bitstream. + +**vui\_mvcd\_num\_units\_in\_tick[ i ]** specifies the value of **num\_units\_in\_tick**, as specified in clause E.2.1, for the i-th sub-bitstream. + +**vui\_mvcd\_time\_scale[ i ]** specifies the value of **time\_scale**, as specified in clause E.2.1, for the i-th sub-bitstream. + +**vui\_mvcd\_fixed\_frame\_rate\_flag[ i ]** specifies the value of **fixed\_frame\_rate\_flag**, as specified in clause E.2.1, for the i-th sub-bitstream. + +**vui\_mvcd\_nal\_hrd\_parameters\_present\_flag[ i ]** specifies the value of **nal\_hrd\_parameters\_present\_flag**, as specified in clause E.2.1, for the i-th sub-bitstream. + +When **vui\_mvcd\_nal\_hrd\_parameters\_present\_flag[ i ]** is equal to 1, NAL HRD parameters (clauses E.1.2 and E.2.2) for the i-th sub-bitstream immediately follow the flag. + +The variable **VuiMvcNalHrdBpPresentFlag[ i ]** is derived as follows: + +- If any of the following is true, the value of **VuiMvcNalHrdBpPresentFlag[ i ]** shall be set equal to 1: + - **vui\_mvcd\_nal\_hrd\_parameters\_present\_flag[ i ]** is present in the bitstream and is equal to 1, + - for the i-th sub-bitstream, the need for presence of buffering periods for NAL HRD operation to be present in the bitstream in buffering period SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of **VuiMvcNalHrdBpPresentFlag[ i ]** shall be set equal to 0. + +**vui\_mvcd\_vcl\_hrd\_parameters\_present\_flag[ i ]** specifies the value of **vcl\_hrd\_parameters\_present\_flag**, as specified in clause E.2.1, for the i-th sub-bitstream. + +When **vui\_mvcd\_vcl\_hrd\_parameters\_present\_flag[ i ]** is equal to 1, VCL HRD parameters (clauses E.1.2 and E.2.2) for the i-th sub-bitstream immediately follow the flag. + +The variable **VuiMvcVclHrdBpPresentFlag[ i ]** is derived as follows: + +- If any of the following is true, the value of `VuiMvcVclHrdBpPresentFlag[ i ]` shall be set equal to 1: + - `vui_mvc_vcl_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, + - for the i-th sub-bitstream, the need for presence of buffering period parameters for VCL HRD operation in the bitstream in buffering period SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of `VuiMvcVclHrdBpPresentFlag[ i ]` shall be set equal to 0. + +The variable `VuiMvcCpbDpbDelaysPresentFlag[ i ]` is derived as follows: + +- If any of the following is true, the value of `VuiMvcCpbDpbDelaysPresentFlag[ i ]` shall be set equal to 1: + - `vui_mvc_nal_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, + - `vui_mvc_vcl_hrd_parameters_present_flag[ i ]` is present in the bitstream and is equal to 1, + - for the i-th sub-bitstream, the need for presence of CPB and DPB output delays in the bitstream in picture timing SEI messages is determined by the application, by some means not specified in this Recommendation | International Standard. +- Otherwise, the value of `VuiMvcCpbDpbDelaysPresentFlag[ i ]` shall be set equal to 0. + +**`vui_mvc_low_delay_hrd_flag[ i ]`** specifies the value of `low_delay_hrd_flag`, as specified in clause E.2.1, for the i-th sub-bitstream. + +**`vui_mvc_pic_struct_present_flag[ i ]`** specifies the value of `pic_struct_present_flag`, as specified in clause E.2.1, for the i-th sub-bitstream. + +## Annex I + +### Multiview and depth video with enhanced non-base view coding + +(This annex forms an integral part of this Recommendation | International Standard.) + +This annex specifies multiview and depth video with enhanced non-base view coding, referred to as 3D-AVC. + +#### I.1 Scope + +Bitstreams and decoders conforming to the profile specified in this annex are completely specified in this annex with reference made to clauses 2 to 9 and Annexes A to E, G, and H. + +#### I.2 Normative references + +The specifications in clause 2 apply. + +#### I.3 Definitions + +For the purpose of this annex, the following definitions apply in addition to the definitions in clause H.3. These definitions are either not present in clause H.3 or replace definitions in clause H.3. + +- I.3.1 MVC texture view component:** A *texture view component* composed of *coded slice NAL units* of *nal\_unit\_type* not equal to 21. +- I.3.2 texture view component:** A *coded representation* of the texture of a *view* in a single *access unit*. A *texture view component* may be a *3D-AVC texture view component* or an *MVC texture view component*. +- I.3.3 view component pair:** A *texture view component* and a *depth view component* of the same *view* within the same *access unit*. +- I.3.4 view synthesis prediction:** A *prediction* derived from samples of *inter-view reference components* using *motion vectors* derived from a *depth view component* for decoding a *texture view component*. +- I.3.5 3D-AVC sequence parameter set:** A collective term for *sequence parameter set* or *subset sequence parameter set*. +- I.3.6 3D-AVC texture view component:** A *texture view component* composed of *coded slice NAL units* of *nal\_unit\_type* equal to 21. +- I.3.7 3DV acquisition parameters:** The closest and farthest depth values. + +#### I.4 Abbreviations + +The specifications in clause 4 apply with the following additions: + +3D-AVC Multiview Video Coding with Depth as specified in this annex + +VSP View Synthesis Prediction + +#### I.5 Conventions + +The specifications in clause 5 apply. + +#### I.6 Source, coded, decoded and output data formats, scanning processes, and neighbouring relationships + +The specifications in clause 6 apply with substitution of 3D-AVC sequence parameter set for sequence parameter set and by replacing references to clause 6.4.2.2 with reference to clause I.6.1. + +##### I.6.1 Inverse sub-macroblock partition scanning process + +Inputs to this process are the index of a macroblock partition *mbPartIdx* and the index of a sub-macroblock partition *subMbPartIdx*. + +Output of this process is the location ( *x*, *y* ) of the upper-left luma sample for the sub-macroblock partition subMbPartIdx relative to the upper-left sample of the sub-macroblock. + +The inverse sub-macroblock partition scanning process is specified as follows: + +- If *mb\_type* is equal to P\_8x8, P\_8x8ref0, or B\_8x8, + +$$x = \text{InverseRasterScan}(\text{ subMbPartIdx, SubMbPartWidth}(\text{ sub\_mb\_type}[\text{ mbPartIdx}]), \text{ SubMbPartHeight}(\text{ sub\_mb\_type}[\text{ mbPartIdx}]), 8, 0) \quad (\text{I-1})$$ + +$$y = \text{InverseRasterScan}(\text{ subMbPartIdx, SubMbPartWidth}(\text{ sub\_mb\_type}[\text{ mbPartIdx}]), \text{ SubMbPartHeight}(\text{ sub\_mb\_type}[\text{ mbPartIdx}]), 8, 1) \quad (\text{I-2})$$ + +- Otherwise, if both of the following are true: + - *mb\_type* is equal to B\_8x8 and *sub\_mb\_type*[ *mbPartIdx* ] is equal to B\_Direct\_8x8, or *mb\_type* is equal to B\_Skip, or *mb\_type* is equal to B\_Direct\_16x16; and + - MbVSSkipFlag is equal to 1 or *mb\_direct\_type\_flag* is equal to 1, + the following applies: + +$$x = \text{InverseRasterScan}(\text{ subMbPartIdx, } 8, 8, 8, 0) \quad (\text{I-3})$$ + +$$y = \text{InverseRasterScan}(\text{ subMbPartIdx, } 8, 8, 8, 1) \quad (\text{I-4})$$ + +- Otherwise, + +$$x = \text{InverseRasterScan}(\text{ subMbPartIdx, } 4, 4, 8, 0) \quad (\text{I-5})$$ + +$$y = \text{InverseRasterScan}(\text{ subMbPartIdx, } 4, 4, 8, 1) \quad (\text{I-6})$$ + +## I.7 Syntax and semantics + +This clause specifies syntax and semantics for coded video sequences that conform to one or more of the profiles specified in this annex. + +### I.7.1 Method of specifying syntax in tabular form + +The specifications in clause H.7.1 apply. + +### I.7.2 Specification of syntax functions, categories, and descriptors + +The specifications in clause H.7.2 apply. + +### I.7.3 Syntax in tabular form + +#### I.7.3.1 NAL unit syntax + +The syntax table is specified in clause H.7.3.1. + +##### I.7.3.1.1 NAL unit header 3D-AVC extension syntax + +| nal_unit_header_3dave_extension() { | C | Descriptor | +|-------------------------------------|-----|------------| +| view_idx | All | u(8) | +| depth_flag | All | u(1) | +| non_idr_flag | All | u(1) | +| temporal_id | All | u(3) | +| anchor_pic_flag | All | u(1) | +| inter_view_flag | All | u(1) | +| } | | | + +### I.7.3.2 Raw byte sequence payloads and RBSP trailing bits syntax + +#### I.7.3.2.1 Sequence parameter set RBSP syntax + +The syntax table is specified in clause H.7.3.2.1. + +##### I.7.3.2.1.1 Sequence parameter set data syntax + +The syntax table is specified in clause H.7.3.2.1.1. + +###### I.7.3.2.1.1.1 Scaling list syntax + +The syntax table is specified in clause H.7.3.2.1.1.1. + +##### I.7.3.2.1.2 Sequence parameter set extension RBSP syntax + +The syntax table is specified in clause H.7.3.2.1.2. + +##### I.7.3.2.1.3 Subset sequence parameter set RBSP syntax + +The syntax table is specified in clause H.7.3.2.1.3. + +##### I.7.3.2.1.4 Sequence parameter set MVC extension syntax + +The syntax table is specified in clause H.7.3.2.1.4. + +##### I.7.3.2.1.5 Sequence parameter set 3D-AVC extension syntax + +| seq_parameter_set_3dvc_extension() { | C | Descriptor | +|---------------------------------------------|---|------------| +| if( NumDepthViews > 0 ) { | | | +| 3dv_acquisition_idc | 0 | ue(v) | +| for( i = 0; i < NumDepthViews; i++ ) | | | +| view_id_3dv[ i ] | 0 | ue(v) | +| if( 3dv_acquisition_idc ) { | | | +| depth_ranges( NumDepthViews, 2, 0 ) | | | +| vsp_param( NumDepthViews, 2, 0 ) | | | +| } | | | +| reduced_resolution_flag | 0 | u(1) | +| if( reduced_resolution_flag ) { | | | +| depth_pic_width_in_mbs_minus1 | 0 | ue(v) | +| depth_pic_height_in_map_units_minus1 | 0 | ue(v) | +| depth_hor_mult_minus1 | 0 | ue(v) | +| depth_ver_mult_minus1 | 0 | ue(v) | +| depth_hor_rsh | 0 | ue(v) | +| depth_ver_rsh | 0 | ue(v) | +| } | | | +| depth_frame_cropping_flag | 0 | u(1) | +| if( depth_frame_cropping_flag ) { | | | +| depth_frame_crop_left_offset | 0 | ue(v) | +| depth_frame_crop_right_offset | 0 | ue(v) | +| depth_frame_crop_top_offset | 0 | ue(v) | +| depth_frame_crop_bottom_offset | 0 | ue(v) | +| } | | | +| grid_pos_num_views | 0 | ue(v) | +| for( i = 0; i < grid_pos_num_views; i++ ) { | | | +| grid_pos_view_id[ i ] | 0 | ue(v) | +| grid_pos_x[ grid_pos_view_id[ i ] ] | 0 | se(v) | +| grid_pos_y[ grid_pos_view_id[ i ] ] | 0 | se(v) | +| } | | | + +| | | | +|----------------------------------------------------|---|-------| +| slice_header_prediction_flag | 0 | u(1) | +| seq_view_synthesis_flag | 0 | u(1) | +| } | | | +| alc_sps_enable_flag | 0 | u(1) | +| enable_rle_skip_flag | 0 | u(1) | +| if( !AllViewsPairedFlag ) { | | | +| for( i = 1; i <= num_views_minus1; i++ ) | | | +| if( texture_view_present_flag[ i ] ) { | | | +| num_anchor_refs_10[ i ] | 0 | ue(v) | +| for( j = 0; j < num_anchor_refs_10[ i ]; j++ ) | | | +| anchor_ref_10[ i ][ j ] | 0 | ue(v) | +| num_anchor_refs_11[ i ] | 0 | ue(v) | +| for( j = 0; j < num_anchor_refs_11[ i ]; j++ ) | | | +| anchor_ref_11[ i ][ j ] | 0 | ue(v) | +| } | | | +| for( i = 1; i <= num_views_minus1; i++ ) | | | +| if( texture_view_present_flag[ i ] ) { | | | +| num_non_anchor_refs_10[ i ] | 0 | ue(v) | +| for( j = 0; j < num_non_anchor_refs_10[ i ]; j++ ) | | | +| non_anchor_ref_10[ i ][ j ] | 0 | ue(v) | +| num_non_anchor_refs_11[ i ] | 0 | ue(v) | +| for( j = 0; j < num_non_anchor_refs_11[ i ]; j++ ) | | | +| non_anchor_ref_11[ i ][ j ] | 0 | ue(v) | +| } | | | +| } | | | +| } | | | + +#### I.7.3.2.2 Picture parameter set RBSP syntax + +The syntax table is specified in clause H.7.3.2.2. + +#### I.7.3.2.3 Supplemental enhancement information RBSP syntax + +The syntax table is specified in clause H.7.3.2.3. + +##### I.7.3.2.3.1 Supplemental enhancement information message syntax + +The syntax table is specified in clause H.7.3.2.3.1. + +#### I.7.3.2.4 Access unit delimiter RBSP syntax + +The syntax table is specified in clause H.7.3.2.4. + +#### I.7.3.2.5 End of sequence RBSP syntax + +The syntax table is specified in clause H.7.3.2.5. + +#### I.7.3.2.6 End of stream RBSP syntax + +The syntax table is specified in clause H.7.3.2.6. + +#### I.7.3.2.7 Filler data RBSP syntax + +The syntax table is specified in clause H.7.3.2.7. + +#### I.7.3.2.8 Slice layer without partitioning RBSP syntax + +The syntax table is specified in clause H.7.3.2.8. + +#### I.7.3.2.9 Slice data partition RBSP syntax + +Slice data partition syntax is not present in coded video sequences conforming to one or more of the profiles specified in + +this annex. + +#### I.7.3.2.10 RBSP slice trailing bits syntax + +The syntax table is specified in clause H.7.3.2.10. + +#### I.7.3.2.11 RBSP trailing bits syntax + +The syntax table is specified in clause H.7.3.2.11. + +#### I.7.3.2.12 Prefix NAL unit RBSP syntax + +The syntax table is specified in clause H.7.3.2.12. + +#### I.7.3.2.13 Depth parameter set RBSP syntax + +| depth_parameter_set_rbsp( ) { | C | Descriptor | +|---------------------------------------------------------------------------------------|----|------------| +| depth_parameter_set_id | 11 | ue(v) | +| pred_direction | 11 | ue(v) | +| if( pred_direction == 0 pred_direction == 1 ) { | | | +| ref_dps_id0 | 11 | ue(v) | +| predWeight0 = 64 | | | +| } | | | +| if( pred_direction == 0 ) { | | | +| ref_dps_id1 | 11 | ue(v) | +| pred_weight0 | 11 | u(6) | +| predWeight0 = pred_weight0 | | | +| } | | | +| num_depth_views_minus1 | 11 | ue(v) | +| depth_ranges( num_depth_views_minus1 + 1, pred_direction,
depth parameter set id ) | | | +| vsp_param_flag | 11 | u(1) | +| if( vsp_param_flag ) | | | +| vsp_param( num_depth_views_minus1 + 1, pred_direction,
depth parameter set id ) | | | +| depth_param_additional_extension_flag | 11 | u(1) | +| nonlinear_depth_representation_num | 11 | ue(v) | +| for( i = 1; i <= nonlinear_depth_representation_num; i++ ) | | | +| nonlinear_depth_representation_model[ i ] | 11 | ue(v) | +| if( depth_param_additional_extension_flag == 1 ) | | | +| while( more_rbsp_data( ) ) | | | +| depth_param_additional_extension_data_flag | 11 | u(1) | +| rbsp_trailing_bits( ) | | | +| } | | | + +#### I.7.3.2.13.1 Depth ranges syntax + +| | | | +|---------------------------------------------------------------------------------------------------------------------|----|------------| +| depth_ranges( numViews, predDirection, index ) { | C | Descriptor | +| z_near_flag | 11 | u(1) | +| z_far_flag | 11 | u(1) | +| if( z_near_flag ) | | | +| 3dv_acquisition_element( numViews, 0, predDirection, 7, index,
ZNearSign, ZNearExp, ZNearMantissa, ZNearManLen ) | | | +| if( z_far_flag ) | | | +| 3dv_acquisition_element( numViews, 0, predDirection, 7, index,
ZFarSign, ZFarExp, ZFarMantissa, ZFarManLen ) | | | +| } | | | + +#### I.7.3.2.13.2 3DV acquisition element syntax + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------|----|------------| +| 3dv_acquisition_element( numViews, predDirection, expLen, index, outSign,
outExp, outMantissa, outManLen ) { | C | Descriptor | +| if( numViews > 1 ) | | | +| element_equal_flag | 11 | u(1) | +| if( element_equal_flag == 0 ) | | | +| numValues = numViews | | | +| else | | | +| numValues = 1 | | | +| for( i = 0; i < numValues; i++ ) { | | | +| if( predDirection == 2 && i == 0 ) { | | | +| mantissa_len_minus1 | 11 | u(5) | +| outManLen[ index, i ] = manLen = mantissa_len_minus1 + 1 | | | +| } | | | +| if( predDirection == 2 ) { | | | +| sign0 | 11 | u(1) | +| outSign[ index, i ] = sign0 | | | +| exponent0 | 11 | u(v) | +| outExp[ index, i ] = exponent0 | | | +| mantissa0 | 11 | u(v) | +| outMantissa[ index, i ] = mantissa0 | | | +| } else { | | | +| skip_flag | 11 | u(1) | +| if( skip_flag == 0 ) { | | | +| sign1 | 11 | u(1) | +| outSign[ index, i ] = sign1 | | | +| exponent_skip_flag | 11 | u(1) | +| if( exponent_skip_flag == 0 ) { | | | +| exponent1 | 11 | u(v) | +| outExp[ index, i ] = exponent1 | | | +| } else | | | +| outExp[ index, i ] = outExp[ ref_dps_id0, i ] | | | +| mantissa_diff | 11 | se(v) | +| if( predDirection == 0 ) | | | +| mantissaPred = (( OutMantissa[ ref_dps_id0, i ] * predWeight0 +
outMantissa[ ref_dps_id1, i ] * ( 64-predWeight0 ) + 32 ) >> 6 ) | | | + +| | | | +|-----------------------------------------------------------|--|--| +| else | | | +| mantissaPred = outMantissa[ ref_dps_id0, i ] | | | +| outMantissa[ index, i ] = mantissaPred + mantissa_diff | | | +| outManLen[ index, i ] = outManLen[ ref_dps_id0, i ] | | | +| } else { | | | +| outSign[ index, i ] = outSign[ ref_dps_id0, i ] | | | +| outExp[ index, i ] = outExp[ ref_dps_id0, i ] | | | +| outMantissa[ index, i ] = outMantissa[ ref_dps_id0, i ] | | | +| outManLen[ index, i ] = outManLen[ ref_dps_id0, i ] | | | +| } | | | +| } | | | +| } | | | +| if( element_equal_flag == 1 ) { | | | +| for( i = 1; i < num_views_minus1 + 1 - deltaFlag; i++ ) { | | | +| outSign[ index, i ] = outSign[ index, 0 ] | | | +| outExp[ index, i ] = outExp[ index, 0 ] | | | +| outMantissa[ index, i ] = outMantissa[ index, 0 ] | | | +| outManLen[ index, i ] = outManLen[ index, 0 ] | | | +| } | | | +| } | | | +| } | | | + +#### I.7.3.2.13.3 View synthesis prediction parameters syntax + +| vsp_param( numViews, predDirection, index ) { | C | Descriptor | +|-----------------------------------------------|---|------------| +| for( i = 0; i < numViews; i++ ) | | | +| for( j = 0; j < i; j++ ) { | | | +| disparity_diff_wji[ j ][ i ] | 0 | ue(v) | +| disparity_diff_oji[ j ][ i ] | 0 | ue(v) | +| disparity_diff_wij[ i ][ j ] | 0 | ue(v) | +| disparity_diff_oij[ i ][ j ] | 0 | ue(v) | +| } | | | +| } | | | +| } | | | + +#### I.7.3.2.14 Slice layer extension RBSP syntax + +The syntax table is specified in clause H.7.3.2.13. + +#### I.7.3.3 Slice header syntax + +The syntax table is specified in clause H.7.3.3. + +##### I.7.3.3.1 Reference picture list modification syntax + +The syntax table is specified in clause H.7.3.3.1. + +###### I.7.3.3.1.1 Reference picture list MVC modification syntax + +The syntax table is specified in clause H.7.3.3.1.1. + +##### I.7.3.3.2 Prediction weight table syntax + +The syntax table is specified in clause H.7.3.3.2. + +##### I.7.3.3.3 Decoded reference picture marking syntax + +The syntax table is specified in clause H.7.3.3.3. + +#### I.7.3.3.4 Slice header in 3D-AVC extension syntax + +| slice_header_in_3davc_extension() { | C | Descriptor | +|------------------------------------------------------------------------------------------------------------------------------------|---|------------| +| first_mb_in_slice | 2 | ue(v) | +| slice_type | 2 | ue(v) | +| pic_parameter_set_id | 2 | ue(v) | +| if( avc_3d_extension_flag && slice_header_prediction_flag != 0 ) { | | | +| pre_slice_header_src | 2 | u(2) | +| if( slice_type == P slice_type == SP
slice_type == B ) { | | | +| pre_ref_lists_src | 2 | u(2) | +| if( !pre_ref_lists_src ) { | | | +| num_ref_idx_active_override_flag | 2 | u(1) | +| if( num_ref_idx_active_override_flag ) { | | | +| num_ref_idx_l0_active_minus1 | 2 | ue(v) | +| if( slice_type == B ) | | | +| num_ref_idx_l1_active_minus1 | 2 | ue(v) | +| } | | | +| ref_pic_list_mvc_modification() /* specified in Annex G */ | 2 | | +| } | | | +| } | | | +| if( ( weighted_pred_flag && ( slice_type == P
slice_type == SP ) )
( weighted_bipred_idc == 1 && slice_type == B ) ) { | | | +| pre_pred_weight_table_src | 2 | u(2) | +| if( !pre_pred_weight_table_src ) | | | +| pred_weight_table() | 2 | | +| if( nal_ref_idc != 0 ) { | | | +| pre_dec_ref_pic_marking_src | 2 | u(2) | +| if( !pre_dec_ref_pic_marking_src ) | | | +| dec_ref_pic_marking() | 2 | | +| } | | | +| slice_qp_delta | 2 | se(v) | +| } else { | | | +| if( separate_colour_plane_flag == 1 ) | | | +| colour_plane_id | 2 | u(2) | +| frame_num | 2 | u(v) | +| if( !frame_mbs_only_flag ) { | | | +| field_pic_flag | 2 | u(1) | +| if( field_pic_flag ) | | | +| bottom_field_flag | 2 | u(1) | +| } | | | +| if( IdrPicFlag ) | | | +| idr_pic_id | 2 | ue(v) | +| if( pic_order_cnt_type == 0 ) { | | | +| pic_order_cnt_lsb | 2 | u(v) | +| if( bottom_field_pic_order_in_frame_present_flag && !field_pic_flag ) | | | +| delta_pic_order_cnt_bottom | 2 | se(v) | +| } | | | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------|---|-------| +| if( pic_order_cnt_type == 1 && !delta_pic_order_always_zero_flag ) { | | | +| delta_pic_order_cnt[ 0 ] | 2 | se(v) | +| if( bottom_field_pic_order_in_frame_present_flag && !field_pic_flag ) | | | +| delta_pic_order_cnt[ 1 ] | 2 | se(v) | +| } | | | +| if( redundant_pic_cnt_present_flag ) | | | +| redundant_pic_cnt | 2 | ue(v) | +| if( slice_type == B ) | | | +| direct_spatial_mv_pred_flag | 2 | u(1) | +| if( slice_type == P slice_type == SP slice_type == B ) { | | | +| num_ref_idx_active_override_flag | 2 | u(1) | +| if( num_ref_idx_active_override_flag ) { | | | +| num_ref_idx_l0_active_minus1 | 2 | ue(v) | +| if( slice_type == B ) | | | +| num_ref_idx_l1_active_minus1 | 2 | ue(v) | +| } | | | +| } | | | +| } | | | +| if( nal_unit_type == 20 nal_unit_type == 21 ) | | | +| ref_pic_list_mvc_modification( ) /* specified in Annex G */ | 2 | | +| else | | | +| ref_pic_list_modification( ) | 2 | | +| if( ( weighted_pred_flag && ( slice_type == P slice_type == SP ) ) ( weighted_bipred_idc == 1 && slice_type == B ) ) | | | +| pred_weight_table( ) | 2 | | +| if( nal_ref_idc != 0 ) | | | +| dec_ref_pic_marking( ) | 2 | | +| if( entropy_coding_mode_flag && slice_type != I && slice_type != SI ) | | | +| cabac_init_idc | 2 | ue(v) | +| slice_qp_delta | 2 | se(v) | +| if( slice_type == SP slice_type == SI ) { | | | +| if( slice_type == SP ) | | | +| sp_for_switch_flag | 2 | u(1) | +| slice_qs_delta | 2 | se(v) | +| } | | | +| if( deblocking_filter_control_present_flag ) { | | | +| disable_deblocking_filter_idc | 2 | ue(v) | +| if( disable_deblocking_filter_idc != 1 ) { | | | +| slice_alpha_c0_offset_div2 | 2 | se(v) | +| slice_beta_offset_div2 | 2 | se(v) | +| } | | | +| } | | | +| if( num_slice_groups_minus1 > 0 && slice_group_map_type >= 3 && slice_group_map_type <= 5 ) | | | +| slice_group_change_cycle | 2 | u(v) | +| if( nal_unit_type == 21 && ( slice_type != I && slice_type != SI ) ) { | | | +| if( DepthFlag ) | | | + +| | | | +|--------------------------------------------------------------------------------|---|-------| +| depth_weighted_pred_flag | 2 | u(1) | +| else if( avc_3d_extension_flag ) { | | | +| dmvp_flag | 2 | u(1) | +| if( seq_view_synthesis_flag ) | | | +| slice_vsp_flag | 2 | u(1) | +| } | | | +| if( 3dv_acquisition_idc != 1 &&
( depth_weighted_pred_flag dmvp_flag ) ) | | | +| dps_id | 2 | ue(v) | +| } | | | +| } | | | +| } | | | + +### I.7.3.4 Slice data syntax + +The syntax table is specified in clause H.7.3.4. + +#### I.7.3.4.1 Slice data in 3D-AVC extension syntax + +| slice_data_in_3davic_extension( ) { | C | Descriptor | +|----------------------------------------------------------------------------------------------------|---|------------| +| if( entropy_coding_mode_flag ) | | | +| while( !byte_aligned( ) ) | | | +| cabac_alignment_one_bit | 2 | f(1) | +| CurrMbAddr = first_mb_in_slice * ( 1 + MbaffFrameFlag ) | | | +| moreDataFlag = 1 | | | +| prevMbSkipped = 0 | | | +| RunLength = 0 | | | +| do { | | | +| if( slice_type != I && slice_type != SI ) | | | +| if( !entropy_coding_mode_flag ) { | | | +| mb_skip_run | 2 | ue(v) | +| prevMbSkipped = ( mb_skip_run > 0 ) | | | +| for( i=0; imb_skip_run > 0 && VspRefExist ) | | | +| mb_skip_type_flag | 2 | u(1) | +| if( mb_skip_run > 0 ) | | | +| moreDataFlag = more_rbsp_data( ) | | | +| } else { | | | +| if( nal_unit_type == 21 && !DepthFlag &&
VspRefExist && leftMbVSSkipped &&
upMbVSSkipped ) { | | | +| mb_vsskip_flag | 2 | ae(v) | +| moreDataFlag = !mb_vsskip_flag | | | +| if( !mb_vsskip_flag ) { | | | +| mb_skip_flag | 2 | ae(v) | +| moreDataFlag = !mb_skip_flag | | | +| } | | | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------|-----------|--------------| +| RunLength = 0 | | | +| } else { | | | +| rleCtx = RLESkipContext( ) | | | +| if( rleCtx && !RunLength ) { | | | +| mb_skip_run_type | 2 | ae(v) | +| RunLength = 16 | | | +| } else if( !rleCtx && RunLength ) | | | +| RunLength = 0 | | | +| if( rleCtx && mb_skip_run_type ) | | | +| RunLength -= 1 | | | +| else | | | +| mb_skip_flag | 2 | ae(v) | +| if( rleCtx && !mb_skip_flag ) | | | +| RunLength = 0 | | | +| moreDataFlag = !mb_skip_flag | | | +| if( nal_unit_type == 21 && !DepthFlag && VspRefExist && !mb_skip_flag ) { | | | +| mb_vsskip_flag | 2 | ae(v) | +| moreDataFlag = !mb_vsskip_flag | | | +| } | | | +| } | | | +| if(alc_sps_enable_flag && nal_unit_type == 21 && slice_type == P && !DepthFlag && !mb_vsskip_flag && mb_skip_flag == 1 ) | | | +| mb_alc_skip_flag | 2 | ae(v) | +| } | | | +| if( moreDataFlag ) { | | | +| if( MbaffFrameFlag && ( CurrMbAddr % 2 == 0 ( CurrMbAddr % 2 == 1 && prevMbSkipped ) ) ) | | | +| mb_field_decoding_flag | 2 | u(1) ae(v) | +| macroblock_layer_in_3dave_extension( ) | 2 3 4 | | +| } | | | +| if( !entropy_coding_mode_flag ) | | | +| moreDataFlag = more_rbsp_data( ) | | | +| else { | | | +| if( slice_type != I && slice_type != SI ) | | | +| prevMbSkipped = mb_skip_flag mb_vsskip_flag | | | +| if( MbaffFrameFlag && CurrMbAddr % 2 == 0 ) | | | +| moreDataFlag = 1 | | | +| else { | | | +| end_of_slice_flag | 2 | ae(v) | +| moreDataFlag = !end_of_slice_flag | | | +| } | | | +| } | | | +| CurrMbAddr = NextMbAddress( CurrMbAddr ) | | | +| } while( moreDataFlag ) | | | +| } | | | + +### I.7.3.5 Macroblock layer syntax + +The syntax table is specified in clause H.7.3.5. + +#### I.7.3.5.1 Macroblock prediction syntax + +The syntax table is specified in clause H.7.3.5.1. + +#### I.7.3.5.2 Sub-macroblock prediction syntax + +The syntax table is specified in clause H.7.3.5.2. + +#### I.7.3.5.3 Residual data syntax + +The syntax table is specified in clause H.7.3.5.3. + +##### I.7.3.5.3.1 Residual luma syntax + +The syntax table is specified in clause H.7.3.5.3.1. + +##### I.7.3.5.3.2 Residual block CAVLC syntax + +The syntax table is specified in clause H.7.3.5.3.2. + +##### I.7.3.5.3.3 Residual block CABAC syntax + +The syntax table is specified in clause H.7.3.5.3.3. + +### I.7.3.6 Macroblock layer in 3D-AVC extension syntax + +| macroblock_layer_in_3davc_extension( ) { | C | Descriptor | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| mb_type | 2 | ue(v) ae(v) | +| if( nal_unit_type == 21 && !DepthFlag
&& slice_type == B
&& direct_spatial_mv_pred_flag && VspRefExist
&& mb_type == B_Direct_16x16 ) | | | +| mb_direct_type_flag | 2 | u(1) ae(v) | +| if( alc_sps_enable_flag && nal_unit_type == 21 &&
slice_type == P && !DepthFlag &&
( mb_type == P_L0_16x16
mb_type == P_L0_L0_16x8
mb_type == P_L0_L0_8x16 ) ) | | | +| mb_alc_flag | 2 | u(1) ae(v) | +| if( mb_type == I_PCM ) { | | | +| while( !byte_aligned( ) ) | | | +| pcm_alignment_zero_bit | 3 | f(1) | +| for( i = 0; i < 256; i++ ) | | | +| pcm_sample_luma[ i ] | 3 | u(v) | +| for( i = 0; i < 2 * MbWidthC * MbHeightC; i++ ) | | | +| pcm_sample_chroma[ i ] | 3 | u(v) | +| } else { | | | +| noSubMbPartSizeLessThan8x8Flag = 1 | | | +| if( mb_type != I_NxN &&
MbPartPredMode( mb_type, 0 ) != Intra_16x16 &&
NumMbPart( mb_type ) == 4 ) { | | | +| sub_mb_pred_in_3davc_extension( mb_type ) | 2 | | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( sub_mb_type[ mbPartIdx ] != B_Direct_8x8 ) { | | | +| if( NumSubMbPart( sub_mb_type[ mbPartIdx ] ) > 1 ) | | | +| noSubMbPartSizeLessThan8x8Flag = 0 | | | +| } else if( !direct_8x8_inference_flag ) | | | +| noSubMbPartSizeLessThan8x8Flag = 0 | | | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---------------| +| } else { | | | +| if( transform_8x8_mode_flag && mb_type == I_NxN ) | | | +| transform_size_8x8_flag | 2 | u(1) ae(v) | +| mb_pred_in_3dave_extension( mb_type ) | 2 | | +| } | | | +| if( MbPartPredMode( mb_type, 0 ) != Intra_16x16 ) { | | | +| coded_block_pattern | 2 | me(v) ae(v) | +| if( ( CodedBlockPatternLuma > 0 mb_alc_flag == 1 ) &&
transform_8x8_mode_flag && mb_type != I_NxN &&
noSubMbPartSizeLessThan8x8Flag &&
( mb_type != B_Direct_16x16
direct_8x8_inference_flag ) ) | | | +| transform_size_8x8_flag | 2 | u(1) ae(v) | +| } | | | +| if( CodedBlockPatternLuma > 0
CodedBlockPatternChroma > 0
MbPartPredMode( mb_type, 0 ) == Intra_16x16 ) { | | | +| mb_qp_delta | 2 | se(v) ae(v) | +| residual( 0, 15 ) | 3 4 | | +| } | | | +| } | | | +| } | | | + +#### I.7.3.6.1 Macroblock prediction in 3D-AVC extension syntax + +| mb_pred_in_3dave_extension( mb_type ) { | C | Descriptor | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| if( MbPartPredMode( mb_type, 0 ) == Intra_4x4
MbPartPredMode( mb_type, 0 ) == Intra_8x8
MbPartPredMode( mb_type, 0 ) == Intra_16x16 ) { | | | +| if( MbPartPredMode( mb_type, 0 ) == Intra_4x4 ) | | | +| for( luma4x4BlkIdx=0; luma4x4BlkIdx<16; luma4x4BlkIdx++ ) { | | | +| prev_intra4x4_pred_mode_flag[ luma4x4BlkIdx ] | 2 | u(1) ae(v) | +| if( !prev_intra4x4_pred_mode_flag[ luma4x4BlkIdx ] ) | | | +| rem_intra4x4_pred_mode[ luma4x4BlkIdx ] | 2 | u(3) ae(v) | +| } | | | +| if( MbPartPredMode( mb_type, 0 ) == Intra_8x8 ) | | | +| for( luma8x8BlkIdx=0; luma8x8BlkIdx<4; luma8x8BlkIdx++ ) { | | | +| prev_intra8x8_pred_mode_flag[ luma8x8BlkIdx ] | 2 | u(1) ae(v) | +| if( !prev_intra8x8_pred_mode_flag[ luma8x8BlkIdx ] ) | | | +| rem_intra8x8_pred_mode[ luma8x8BlkIdx ] | 2 | u(3) ae(v) | +| } | | | +| if( ChromaArrayType == 1 ChromaArrayType == 2 ) | | | +| intra_chroma_pred_mode | 2 | ue(v) ae(v) | +| } else if( MbPartPredMode( mb_type, 0 ) != Direct ) { | | | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( ( num_ref_idx_l0_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
MbPartPredMode( mb_type, mbPartIdx ) != Pred_L1 &&
mb_alc_flag == 0 ) { | | | +| ref_idx_l0[ mbPartIdx ] | 2 | te(v) ae(v) | +| if( VspRefl0Flag[ mbPartIdx ] && slice_vsp_flag ) | | | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| bvsp_flag_10[ mbPartIdx ] | 2 | u(1) ae(v) | +| } | | | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( ( num_ref_idx_11_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
MbPartPredMode( mb_type, mbPartIdx ) != Pred_L0 ) { | | | +| ref_idx_11[ mbPartIdx ] | 2 | te(v) ae(v) | +| if( VspRefL1Flag[ mbPartIdx ] && slice_vsp_flag ) | | | +| bvsp_flag_11[ mbPartIdx ] | 2 | u(1) ae(v) | +| } | | | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( MbPartPredMode( mb_type, mbPartIdx ) != Pred_L1 &&
( !VspRefL0Flag[ mbPartIdx ] !bvsp_flag_10[ mbPartIdx ] ) ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_10[ mbPartIdx ][ 0 ][ compIdx ] | 2 | se(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < NumMbPart( mb_type ); mbPartIdx++ ) | | | +| if( MbPartPredMode( mb_type, mbPartIdx ) != Pred_L0 &&
( !VspRefL1Flag[ mbPartIdx ] !bvsp_flag_11[ mbPartIdx ] ) ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_11[ mbPartIdx ][ 0 ][ compIdx ] | 2 | se(v) ae(v) | +| } | | | +| } | | | + +### I.7.3.6.2 Sub-macroblock prediction syntax + +| sub_mb_pred_in_3dave_extension( mb_type ) { | C | Descriptor | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| sub_mb_type[ mbPartIdx ] | 2 | ue(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( ( num_ref_idx_10_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
mb_type != P_8x8ref0 &&
sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L1 &&
mb_alc_flag == 0 ) { | | | +| ref_idx_10[ mbPartIdx ] | 2 | te(v) ae(v) | +| if( VspRefL0Flag[ mbPartIdx ] && slice_vsp_flag ) | | | +| bvsp_flag_10[ mbPartIdx ] | 2 | u(1) ae(v) | +| } | | | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( ( num_ref_idx_11_active_minus1 > 0
mb_field_decoding_flag != field_pic_flag ) &&
sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L0 ) { | | | +| ref_idx_11[ mbPartIdx ] | 2 | te(v) ae(v) | +| if( VspRefL1Flag[ mbPartIdx ] && slice_vsp_flag ) | | | +| bvsp_flag_11[ mbPartIdx ] | 2 | u(1) ae(v) | +| } | | | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L1 &&
( !VspRefL0Flag[ mbPartIdx ] !bvsp_flag_10[ mbPartIdx ] ) ) | | | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------| +| for( subMbPartIdx = 0;
subMbPartIdx < NumSubMbPart( sub_mb_type[ mbPartIdx ] );
subMbPartIdx++ ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_10[ mbPartIdx ][ subMbPartIdx ][ compIdx ] | 2 | se(v) ae(v) | +| for( mbPartIdx = 0; mbPartIdx < 4; mbPartIdx++ ) | | | +| if( sub_mb_type[ mbPartIdx ] != B_Direct_8x8 &&
SubMbPredMode( sub_mb_type[ mbPartIdx ] ) != Pred_L0 &&
( !VspRefL1Flag[ mbPartIdx ] !bvsp_flag_11[ mbPartIdx ] ) ) | | | +| for( subMbPartIdx = 0;
subMbPartIdx < NumSubMbPart( sub_mb_type[ mbPartIdx ] );
subMbPartIdx++ ) | | | +| for( compIdx = 0; compIdx < 2; compIdx++ ) | | | +| mvd_11[ mbPartIdx ][ subMbPartIdx ][ compIdx ] | 2 | se(v) ae(v) | +| } | | | + +## I.7.4 Semantics + +Semantics associated with the syntax structures and syntax elements within these structures (in clause I.7.3 and in clause H.7.3 by reference in clause I.7.3) are specified in this clause and by reference to clause H.7.4. When the semantics of a syntax element are specified using a table or a set of tables, any values that are not specified in the table(s) shall not be present in the bitstream unless otherwise specified in this Recommendation | International Standard. + +### I.7.4.1 NAL unit semantics + +The semantics for the syntax elements clause I.7.3.1 are specified in clause H.7.3.1. + +#### I.7.4.1.1 NAL unit header MVC extension semantics + +**view\_idx** specifies the view order index for the NAL unit. + +**view\_id** is inferred to be equal to **view\_id[ view\_idx ]**, where **view\_id[ ]** is present in the active sequence parameter set. + +The variable **VOIdx**, representing the view order index of the view identified by **view\_id[ i ]**, is set equal to **view\_idx**. + +**depth\_flag** equal to 1 indicates that the current NAL unit belongs to a depth view component, **depth\_flag** equal to 0 indicates that the current NAL unit belongs to a texture view component. + +**non\_idr\_flag**, **temporal\_id**, **anchor\_pic\_flag**, and **inter\_view\_flag** have the same semantics as those syntax elements with the same names in Annex G. + +#### I.7.4.1.2 Order of NAL units and association to coded pictures, access units, and video sequences + +The specification of clause H.7.4.1.2 applies. + +##### I.7.4.1.2.1 Order of 3D-AVC sequence parameter set RBSPs and picture parameter set RBSPs and their activation + +The specification of clause H.7.4.1.2.1 applies. + +In addition, the following applies for the activation of depth parameter set. + +A depth parameter set includes parameters that can be referred to by the coded slice NAL units of one or more texture view or depth view components of one or more coded pictures. A depth parameter set associated with **depth\_parameter\_set\_id** equal to 0 contains the depth ranges syntax structure and the view synthesis prediction parameter syntax structure included in the active sequence parameter set. A depth parameter set with **depth\_parameter\_set\_id** greater than 0 is a depth parameter set RBSP with that **depth\_parameter\_set\_id** value. + +Each depth parameter set is initially considered not active at the start of the operation of the decoding process. At most one depth parameter set is considered as the active depth parameter set at any given moment during the operation of the decoding process, and when any particular depth parameter set becomes the active depth parameter set, the previously-active depth parameter set (if any) is deactivated. + +When a depth parameter set (with a particular value of **depth\_parameter\_set\_id**) is not the active depth parameter set and it is referred to by a coded slice NAL unit (when **dps\_id** is present in a slice header), it is activated. This depth parameter set is called the active depth parameter set until it is deactivated when another depth parameter set becomes the active + +depth parameter set. A depth parameter set, with that particular value of `depth_parameter_set_id`, shall be available to the decoding process prior to its activation. When a depth parameter set is activated, the same depth parameter set shall remain active for subsequent coded slice NAL units of the same access unit. + +If any depth parameter set is present that is never activated in the bitstream (i.e., it never becomes the active depth parameter set), its syntax elements shall have values that would conform to the specified constraints if it were activated by reference in an otherwise-conforming bitstream. + +#### **I.7.4.1.2.2 Order of access units and association to coded video sequences** + +The specification of clause H.7.4.1.2.2 apply. + +#### **I.7.4.1.2.3 Order of NAL units and coded pictures and association to access units** + +The specification of clause G.7.4.1.2.3 applies with the following modifications. + +The association of VCL NAL units to primary or redundant coded pictures is specified in clause H.7.4.1.2.5. + +#### **I.7.4.1.2.4 Detection of the first VCL NAL unit of a primary coded picture** + +The specification of clause G.7.4.1.2.4 applies. + +#### **I.7.4.1.2.5 Order of VCL NAL units and association to coded pictures** + +Each VCL NAL unit is part of a coded picture. + +Let `voIdx` be the value of `VOIdx` of any particular VCL NAL unit. The order of the VCL NAL units within a coded picture is constrained as follows: + +- For all VCL NAL units following this particular VCL NAL unit, the value of `VOIdx` shall be greater than or equal to `voIdx`. +- All VCL NAL units for a depth view component, if present, shall follow any VCL NAL unit of an MVC texture view component with a same value of `VOIdx`. + +For each set of VCL NAL units within a texture or depth view component, the following applies: + +- If arbitrary slice order, as specified in Annex A, clause G.10, clause H.10 or clause I.10, is allowed, coded slice NAL units of a view component may have any order relative to each other. +- Otherwise (arbitrary slice order is not allowed), coded slice NAL units of a slice group shall not be interleaved with coded slice NAL units of another slice group and the order of coded slice NAL units within a slice group shall be in the order of increasing macroblock address for the first macroblock of each coded slice NAL unit of the same slice group. + +The following applies: + +- If a coded texture view component with a particular `view_id` is the first field view component of a complementary field pair, the depth view component with the same `view_id` value, if present in the access unit, shall be a coded frame view component or the first field view component of a complementary field pair. +- Otherwise, if a coded texture view component with a particular `view_id` is the second field view component of a complementary field pair, the depth view component with the same `view_id` value, if present in the access unit, shall be the second field view component of a complementary field pair. +- Otherwise, if a coded texture view component with a particular `view_id` is a non-paired field, the depth view component with the same `view_id` value, if present in the access unit, shall be a coded frame view component or a non-paired field. +- Otherwise (a coded texture view component with a particular `view_id` is a coded frame), the depth view component with the same `view_id` value, if present in the access unit, shall be a coded frame view component. + +NAL units having `nal_unit_type` equal to 12 may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having `nal_unit_type` equal to 0 or in the range of 24 to 31, inclusive, which are unspecified, may be present in the access unit but shall not precede the first VCL NAL unit of the primary coded picture within the access unit. + +NAL units having `nal_unit_type` in the range of 22 to 23, inclusive, which are reserved, shall not precede the first VCL NAL unit of the primary coded picture within the access unit (when specified in the future by ITU-T | ISO/IEC). + +#### I.7.4.2 Raw byte sequence payloads and RBSP trailing bits semantics + +##### I.7.4.2.1 Sequence parameter set RBSP semantics + +The semantics specified in clause H.7.4.2.1 apply. + +###### I.7.4.2.1.1 Sequence parameter set data semantics + +The semantics specified in clause H.7.4.2.1.1 apply. + +###### I.7.4.2.1.1.1 Scaling list semantics + +The semantics specified in clause H.7.4.2.1.1.1 apply. + +###### I.7.4.2.1.2 Sequence parameter set extension RBSP semantics + +The semantics specified in clause H.7.4.2.1.2 apply. + +###### I.7.4.2.1.3 Subset sequence parameter set RBSP semantics + +The semantics specified in clause H.7.4.2.1.3 apply. + +###### I.7.4.2.1.4 Sequence parameter set MVCD extension semantics + +The semantics specified in clause H.7.4.2.1.4 apply with the substitution of texture view component or depth view component for view component. + +###### I.7.4.2.1.5 Sequence parameter set 3D-AVC extension semantics + +The function ViewCompOrder( depthFlag, viewId ) is specified to return the value of viewCompOrder derived as follows: + +``` +i = 0 +while ( i <= num_views_minus1 && ( view_id[ i ] != viewId || + ( depthFlag && !depth_view_present_flag[ i ] ) || + ( !depthFlag && !texture_view_present_flag[ i ] ) ) ) + i++ +if ( i > num_views_minus1 ) + viewCompOrder = MAX_INT +else + viewCompOrder = 2 * i + depthFlag +``` + +(I-7) + +**3dv\_acquisition\_idc** equal to 0 indicates that no depth ranges or view synthesis prediction parameters syntax structures are present in the sequence parameter set. **3dv\_acquisition\_idc** equal to 1 indicates that depth ranges and view synthesis prediction parameters syntax structures are present in the sequence parameter set and valid for the entire coded video sequence. **3dv\_acquisition\_idc** equal to 2 indicates that depth ranges and view synthesis prediction parameters syntax structures are present in the sequence parameter set and depth parameter sets with **depth\_parameter\_set\_id** greater than 0 may be activated. **3dv\_acquisition\_idc** values greater than 2 are reserved. + +The function ViewIdTo3DVAcquisitionParamIndex( viewId ) is specified to return the value of i for which **view\_id\_3dv[ i ]** is equal to viewId in the active sequence parameter set. + +**reduced\_resolution\_flag** equal to 1 specifies that the depth view components of a view component pair have a lower spatial resolution than the luma component of the texture view component of the same view component pair, and the width and height (as represented by **pic\_width\_in\_mbs\_minus1+1** and **pic\_height\_in\_map\_units\_minus1+1** in the referred subset sequence parameter set) of the depth view components are both half of the width and height of all the texture view components. **reduced\_resolution\_flag** equal to 0 specifies that when both depth view components and texture view components are present, they have the same spatial resolution. + +**depth\_pic\_width\_in\_mbs\_minus1** and **depth\_pic\_height\_in\_map\_units\_minus1**, when present, are used to infer the width and height of depth view components. When **reduced\_resolution\_flag** is equal to 1, the values of **pic\_width\_in\_mbs\_minus1** and **pic\_height\_in\_map\_units\_minus1** are inferred to be equal to **depth\_pic\_width\_in\_mbs\_minus1** and **depth\_pic\_height\_in\_map\_units\_minus1** for depth views for which this 3D-AVC sequence parameter set is an active view 3D-AVC sequence parameter set. + +**depth\_hor\_mult\_minus1**, **depth\_ver\_mult\_minus1**, **depth\_hor\_rsh** and **depth\_ver\_rsh** are used for specifying the depth-based disparity value derivation process (specified in clause I.8.2.1.1). When not present, **depth\_hor\_mult\_minus1** and **depth\_ver\_mult\_minus1** are inferred to be equal to 1, and **depth\_hor\_rsh** and **depth\_ver\_rsh** are inferred to be equal to 0. **depth\_hor\_mult\_minus1** and **depth\_ver\_mult\_minus1** shall be in the range of 0 to 1023, inclusive. **depth\_hor\_rsh** and **depth\_ver\_rsh** shall be in the range of 0 to 31, inclusive. + +**depth\_frame\_cropping\_flag** equal to 0 specifies that the frame cropping offset parameters for depth view components + +follow next in the sequence parameter set. `depth_frame_cropping_flag` equal to 0 specifies that the frame cropping offset parameters for depth view components are not present. + +**`depth_frame_crop_left_offset`**, **`depth_frame_crop_right_offset`**, **`depth_frame_crop_top_offset`** and **`depth_frame_crop_bottom_offset`** specify the samples of the decoded depth view components in the coded video sequence that are output from the decoding process, in terms of a rectangular region specified in frame coordinates for output. + +When `depth_frame_cropping_flag` is equal to 0, the values of `depth_frame_crop_left_offset`, `depth_frame_crop_right_offset`, `depth_frame_crop_top_offset`, and `depth_frame_crop_bottom_offset` are inferred to be equal to 0. + +The values of `frame_crop_left_offset`, `frame_crop_right_offset`, `frame_crop_top_offset`, `frame_crop_bottom_offset` are inferred to be equal to `depth_frame_crop_left_offset`, `depth_frame_crop_right_offset`, `depth_frame_crop_top_offset`, and `depth_frame_crop_bottom_offset` for the decoding and output of depth views for which this 3D-AVC sequence parameter set is an active view 3D-AVC sequence parameter set. + +Let the variables `DepthCropLeftCoord`, `DepthCropRightCoord`, `DepthCropTopCoord` and `DepthCropBottomCoord` be derived from the values of `PicWidthInSamplesL`, `CropUnitX`, `CropUnitY`, `FrameHeightInMBs` that apply to depth view components as follows: + +$$\begin{aligned} \text{DepthCropLeftCoord} &= \text{CropUnitX} * \text{depth\_frame\_crop\_left\_offset} \\ \text{DepthCropRightCoord} &= \text{PicWidthInSamples\_L} - ( \text{CropUnitX} * \text{depth\_frame\_crop\_right\_offset} + 1 ) \\ \text{DepthCropTopCoord} &= \text{CropUnitY} * \text{depth\_frame\_crop\_top\_offset} \\ \text{DepthCropBottomCoord} &= ( 16 * \text{FrameHeightInMBs} ) - ( \text{CropUnitY} * \text{depth\_frame\_crop\_bottom\_offset} + 1 ) \end{aligned} \quad (\text{I-8})$$ + +**`grid_pos_num_views`** specifies the number of views for which `grid_pos_view_id[ i ]`, `grid_pos_x[ grid_pos_view_id[ i ] ]` and `grid_pos_y[ grid_pos_view_id[ i ] ]` are present. `grid_pos_num_views` shall be in the range of 0 to 1024, inclusive. + +**`grid_pos_view_id[ i ]`** specifies a `view_id` value of a texture view. + +**`grid_pos_x[ grid_pos_view_id[ i ] ]`** specifies a horizontal offset of a depth sampling grid relative to the luma texture sampling grid in texture luma sample units. + +**`grid_pos_y[ grid_pos_view_id[ i ] ]`** specifies a vertical offset of a depth sampling grid relative to the luma texture sampling grid in texture luma sample units. + +When no value of `grid_pos_view_id[ i ]` is equal to a `view_id` value of a texture view, `grid_pos_x[ view_id ]` and `grid_pos_y[ view_id ]` are inferred to be equal to 0. + +`grid_pos_x[ grid_pos_view_id[ i ] ]` and `grid_pos_y[ grid_pos_view_id[ i ] ]` are used for specifying the depth-based disparity value derivation process (specified in clause I.8.2.1.1). + +**`slice_header_prediction_flag`** equal to 0 indicates that slice header prediction from texture view component to depth view component or vice versa is disallowed. `slice_header_prediction_flag` equal to 1 indicates that the prediction is used. + +**`seq_view_synthesis_flag`** equal to 1 indicates view synthesis prediction is enabled. `seq_view_synthesis_flag` equal to 0 indicates that view synthesis prediction is disabled for all view components referring the current sequence parameter set. + +**`alc_sps_enable_flag`** equal to 0 specifies that `mb_alc_skip_flag` and `mb_alc_flag` are not present. `alc_sps_enable_flag` equal to 1 specifies that `mb_alc_skip_flag` and `mb_alc_flag` may be present. + +**`enable_rle_skip_flag`** equal to 0 specifies that `mb_skip_run_type` are not present. `enable_rle_skip_flag` equal to 1 specifies that `mb_skip_run_type` may be present. When `enable_rle_skip_flag` is not present, it is inferred to be equal to 0. + +The variable `AllViewsPairedFlag` is derived as follows: + +$$\begin{aligned} \text{AllViewsPairedFlag} &= 1 \\ \text{for } ( i = 1; i \leq \text{num\_views\_minus1}; i++ ) \\ \text{AllViewsPairedFlag} &= ( \text{AllViewsPairedFlag} \&\& \text{depth\_view\_present\_flag}[ i ] \&\& \\ &\quad \text{texture\_view\_present\_flag}[ i ] ) \end{aligned} \quad (\text{I-9})$$ + +For `num_anchor_refs_10[ i ]`, `anchor_ref_10[ i ][ j ]`, `num_anchor_refs_11[ i ]`, `anchor_ref_11[ i ][ j ]`, `num_non_anchor_refs_10[ i ]`, `non_anchor_ref_10[ i ][ j ]`, `num_non_anchor_refs_11[ i ]`, and `non_anchor_ref_11[ i ][ j ]`, the semantics specified in clause G.7.4.2.1.4 is applied with the substitution of texture view component for view component. When `num_anchor_refs_10[ i ]`, `anchor_ref_10[ i ][ j ]`, `num_anchor_refs_11[ i ]`, `anchor_ref_11[ i ][ j ]`, `num_non_anchor_refs_10[ i ]`, `non_anchor_ref_10[ i ][ j ]`, `num_non_anchor_refs_11[ i ]`, and `non_anchor_ref_11[ i ][ j ]` are not present, they are inferred to have the same values as the respective syntax elements in the + +seq\_parameter\_set\_mvcd\_extension() syntax structure in the same subset\_seq\_parameter\_set\_rbsp() syntax structure that also contains this seq\_parameter\_set\_3dave\_extension() syntax structure. + +#### **I.7.4.2.2 Picture parameter set RBSP semantics** + +The semantics specified in clause H.7.4.2.2 apply. + +#### **I.7.4.2.3 Supplemental enhancement information RBSP semantics** + +The semantics specified in clause H.7.4.2.3 apply. + +##### **I.7.4.2.3.1 Supplemental enhancement information message semantics** + +The semantics specified in clause H.7.4.2.3.1 apply. + +#### **I.7.4.2.4 Access unit delimiter RBSP semantics** + +The semantics specified in clause H.7.4.2.4 apply. + +#### **I.7.4.2.5 End of sequence RBSP semantics** + +The semantics specified in clause H.7.4.2.5 apply. + +#### **I.7.4.2.6 End of stream RBSP semantics** + +The semantics specified in clause H.7.4.2.6 apply. + +#### **I.7.4.2.7 Filler data RBSP semantics** + +The semantics specified in clause H.7.4.2.7 apply. + +#### **I.7.4.2.8 Slice layer without partitioning RBSP semantics** + +The semantics specified in clause H.7.4.2.8 apply. + +#### **I.7.4.2.9 Slice data partition RBSP semantics** + +Slice data partition syntax is not present in bitstreams conforming to one or more of the profiles specified in this annex. + +#### **I.7.4.2.10 RBSP slice trailing bits semantics** + +The semantics specified in clause H.7.4.2.10 apply. + +#### **I.7.4.2.11 RBSP trailing bits semantics** + +The semantics specified in clause H.7.4.2.11 apply. + +#### **I.7.4.2.12 Prefix NAL unit RBSP semantics** + +The semantics specified in clause H.7.4.2.12 apply. + +#### **I.7.4.2.13 Depth parameter set RBSP semantics** + +**depth\_parameter\_set\_id** identifies the depth parameter set that is referred to in the slice header. The value of depth\_parameter\_set\_id shall be in the range of 1 to 63, inclusive. + +**pred\_direction** equal to 0 specifies that the closest and farthest depth values for the base view may be predicted from the respective variables of two pictures. pred\_direction equal to 1 specifies that the closest and farthest depth values for the base view may be predicted from the respective variables of one picture. pred\_direction equal to 2 specifies that the closest and farthest depth values for the base view are not predicted. The value of pred\_direction shall be in the range of 0 to 2, inclusive. + +**ref\_dps\_id0** specifies a first reference depth parameter set to be used in prediction of the closest and farthest depth value. The value of ref\_dps\_id0 shall be in the range of 0 to 63, inclusive. + +**ref\_dps\_id1** specifies a second reference depth parameter set to be used in prediction of the closest and farthest depth value. The value of ref\_dps\_id1 shall be in the range of 0 to 63, inclusive. + +**pred\_weight0** specifies a weight associated with the a first reference depth parameter set derived from ref\_dps\_id0. The value of pred\_weight0 shall be in the range of 0 to 63, inclusive. + +**num\_views\_minus1** plus 1 specifies the number of views for which depth parameters are specified in the included 3dv\_acquisition\_element() structure. num\_view\_minus1 shall be in the range of 0 to 1023, inclusive. + +**vsp\_param\_flag** equal to 1 indicates the presence of the vsp\_param() syntax structure. vsp\_param\_flag equal to 0 indicates the absence of the vsp\_param() syntax structure. + +**nonlinear\_depth\_representation\_num** plus 1 specifies the number of piecewise linear segments for mapping of depth values to a scale that is uniformly quantized in terms of disparity. + +**nonlinear\_depth\_representation\_model[ i ]** specifies the piecewise linear segments for mapping of depth values to a scale that is uniformly quantized in terms of disparity. + +NOTE – When **nonlinear\_depth\_representation\_num** is equal to 0, a depth sample represents a disparity normalized to the range of 0 to 255, inclusive, so that 0 corresponds to ZFar value and 255 corresponds to ZNear value. Depending on the value of **nonlinear\_depth\_representation\_num**, a depth view component is composed of either depth samples that can be converted to disparity using a linear equation or non-linearly transformed depth samples. If **nonlinear\_depth\_representation\_num** is equal to 0, depth view component contains directly depth samples that are uniformly quantized in terms of disparity, i.e. depth samples that can be transformed to disparity using a linear equation. If **nonlinear\_depth\_representation\_num** is greater than 0, depth view component contains non-linearly transformed depth samples. + +When **nonlinear\_depth\_representation\_num** is greater than 0, **NdrInverse[ i ]**, as specified below, is used to transform depth sample values from non-linear representation to the linear representation. The shape of this transform is defined by means of line-segment-approximation in two-dimensional linear-disparity-to-non-linear-disparity space. The first (0, 0) and the last (255, 255) nodes of the curve are predefined. Positions of additional nodes are transmitted in form of deviations (**nonlinear\_depth\_representation\_model[ i ]**) from the straight-line curve. These deviations are uniformly distributed along the whole range of 0 to 255, inclusive, with spacing depending on the value of **nonlinear\_depth\_representation\_num**. + +If **nonlinear\_depth\_representation\_num** is equal to 0, variable **NdrInverse[ i ]** for i in the range of 0 to 255, inclusive, is specified as follows: + +``` + +nonlinear_depth_representation_model[ 0 ] = 0 +nonlinear_depth_representation_model[ nonlinear_depth_representation_num + 1 ] = 0 +for( k = 0; k <= nonlinear_depth_representation_num; ++k ) +{ + pos1 = ( 255 * k ) / ( nonlinear_depth_representation_num + 1 ) + pos2 = ( 255 * ( k+1 ) ) / ( nonlinear_depth_representation_num + 1 ) + + x1 = pos1 + y1 = pos1 + x2 = pos2 + y2 = pos2 + + for ( x = Max( x1, 0 ); x <= Min( x2, 255 ); ++x ) + NdrInverse[ x ] = Clip3( 0, 255, Round( ( ( x - x1 ) * ( y2 - y1 ) ) ÷ ( x2 - x1 ) + y1 ) ) +} + +``` + +(I-10) + +Otherwise (**nonlinear\_depth\_representation\_num** is greater than 0), variable **NdrInverse[ i ]** for i in the range of 0 to 255, inclusive, is specified as follows: + +``` + +nonlinear_depth_representation_model[ 0 ] = 0 +nonlinear_depth_representation_model[ nonlinear_depth_representation_num + 1 ] = 0 +for( k = 0; k <= nonlinear_depth_representation_num; ++k ) { + pos1 = ( 255 * k ) / ( nonlinear_depth_representation_num + 1 ) + dev1 = nonlinear_depth_representation_model[ k ] + pos2 = ( 255 * ( k+1 ) ) / ( nonlinear_depth_representation_num + 1 ) + dev2 = nonlinear_depth_representation_model[ k+1 ] + + x1 = pos1 - dev1 + y1 = pos1 + dev1 + x2 = pos2 - dev2 + y2 = pos2 + dev2 + + for ( x = Max( x1, 0 ); x <= Min( x2, 255 ); ++x ) + NdrInverse[ x ] = Clip3( 0, 255, Round( ( ( x - x1 ) * ( y2 - y1 ) ) ÷ ( x2 - x1 ) + y1 ) ) +} + +``` + +(I-11) + +**depth\_param\_additional\_extension\_flag** equal to 0 indicates that no additional data follows within the depth parameter set RBSP prior to the RBSP trailing bits. The value of **depth\_param\_additional\_extension\_flag** shall be equal to 0. The value of 1 for **depth\_param\_additional\_extension\_flag** is reserved for future use by ITU-T | ISO/IEC. Decoders shall ignore all data that follows the value of 1 for **depth\_param\_additional\_extension\_flag** in a depth parameter set RBSP. + +#### I.7.4.2.13.1 Depth ranges semantics + +The contents of the syntax structure are controlled through input variables predDirection and index the semantics of which are as follows: + +- predDirection equal to 2 specifies that the first loop entry of the element is not predicted and coded in the sign, exponent, and mantissa syntax elements. predDirection equal to 0 or 1 specifies that the first loop entry of the element is predicted and a difference relative to a prediction value is coded in the difference syntax element. +- index may be equal to the depth\_parameter\_set\_id of the depth parameter set wherein the parameters are present. + +**z\_near\_flag** equal to 0 specifies that the syntax elements specifying the closest depth value are not present in the syntax structure. z\_near\_flag equal to 1 specifies that the syntax elements specifying the closest depth value are present in the syntax structure. + +**z\_far\_flag** equal to 0 specifies that the syntax elements specifying the farthest depth value are not present in the syntax structure. z\_near\_flag equal to 1 specifies that the syntax elements specifying the farthest depth value are present in the syntax structure. + +#### I.7.4.2.13.2 3DV acquisition element semantics + +The syntax structure specifies the value of an element in the depth ranges syntax structure. The element may contain one or more loop entries i of the order specified by view\_id\_3dv syntax elements. + +The contents of the syntax structure are controlled through input variables predDirection, expLen and index, the semantics of which are as follows: + +- predDirection equal to 2 specifies that the first loop entry of the element is not predicted and coded in the sign, exponent, and mantissa syntax elements. predDirection equal to 0 or 1 specifies that the first loop entry of the element is predicted and a difference relative to a prediction value is coded in the difference syntax element. +- expLen specifies the number of bits in the exponent syntax element. +- index greater than 0 specifies the depth\_parameter\_set\_id of the depth parameter set wherein the parameters are present, and index equal to 0 specifies that the parameters are present in a sequence parameter set. + +The syntax structure uses outSign, outExp, outMantissa and outManLen variables for both input and output, where each variable is indexed by [ index, viewIdc ], index being an identifier (equal to either 0 when decoding depth ranges in sequence parameter set or depth\_parameter\_set\_id value when decoding depth range parameter set) to a depth parameter set and viewIdc being a view indicator (in the order of views for 3DV acquisition parameters). + +**element\_equal\_flag** equal to 0 specifies that the sign, exponent, and mantissa may or may not be identical to respective values for any two loop entries i and j. element\_equal\_flag equal to 1 specifies that the sign, exponent, and mantissa are identical to respective values for any two loop entries i and j. When not present, element\_equal\_flag is inferred to be equal to 0. + +**mantissa\_len\_minus1** plus 1 specifies the number of bits in the mantissa syntax element. The value of mantissa\_len\_minus1 shall be in the range of 0 to 31, inclusive. + +**sign0** equal to 0 indicates that the sign of the value provided in the loop entry is positive. sign0 equal to 1 indicates that the sign is negative. + +**exponent0** specifies the exponent of the value provided by the loop entry. The syntax element exponent0 is represented by expLen bits. The value of exponent0 shall be in the range of 0 to $2^{\text{expLen}} - 2$ , inclusive. The value $2^{\text{expLen}} - 1$ is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value $2^{\text{expLen}} - 1$ as indicating an unspecified value. + +**mantissa0** specifies the mantissa of the value provided by the loop entry. The syntax element mantissa0 is represented by manLen bits. + +**skip\_flag** equal to 0 specifies that syntax elements sign1, exponent\_skip\_flag and mantissa\_diff are present for the loop entry. skip\_flag equal to 1 specifies that elements sign1, exponent\_skip\_flag and mantissa\_diff are not present for the loop entry. + +**sign1** equal to 0 indicates that the sign of the value provided in the loop entry is positive. sign1 equal to 1 indicates that the sign is negative. + +**exponent1**, if present, specifies the exponent of the value provided by the loop entry. The syntax element exponent1 is represented by expLen bits. The value of exponent1 shall be in the range of 0 to $2^{\text{expLen}} - 2$ , inclusive. The value $2^{\text{expLen}} - 1$ is reserved for future use by ITU-T | ISO/IEC. Decoders shall treat the value $2^{\text{expLen}} - 1$ as indicating an unspecified value. + +**mantissa\_diff** specifies the difference of the mantissa of the value provided by the loop entry relative to its prediction value. + +### I.7.4.2.13.3 View synthesis prediction parameters semantics + +The contents of the syntax structure are controlled through input variables predDirection and index the semantics of which are as follows: + +- predDirection equal to 2 specifies that the first loop entry of the element is not predicted and coded in the sign, exponent, and mantissa syntax elements. predDirection equal to 0 or 1 specifies that the first loop entry of the element is predicted and a difference relative to a prediction value is coded in the difference syntax element. +- index identifies a depth parameter set. + +**disparity\_diff\_wji[ j ][ i ]**, **disparity\_diff\_oji[ j ][ i ]**, **disparity\_diff\_wij[ i ][ j ]** and **disparity\_diff\_oij[ i ][ j ]** specify the variables DisparityScale and DisparityOffset as follows: + +``` + +if( predDirection == 2 ) { + DisparityScale[ index ][ j ][ i ] = disparity_diff_wji[ j ][ i ] + DisparityOffset[ index ][ j ][ i ] = disparity_diff_oji[ j ][ i ] + DisparityScale[ index ][ i ][ j ] = disparity_diff_wij[ i ][ j ] - disparity_diff_wji[ j ][ i ] + DisparityOffset[ index ][ i ][ j ] = disparity_diff_oij[ i ][ j ] - disparity_diff_oji[ j ][ i ] +} else { + DisparityScale[ index ][ j ][ i ] = disparity_diff_wji[ j ][ i ] + ( DisparityScale[ ref_dps_id0 ][ j ][ i ] * + predWeight0 + DisparityScale[ ref_dps_id1 ][ j ][ i ] * ( 64 - predWeight0 ) + 32 ) >> 6 + DisparityOffset[ index ][ j ][ i ] = disparity_diff_oji[ j ][ i ] + ( DisparityOffset[ ref_dps_id0 ][ j ][ i ] * + predWeight0 + DisparityOffset[ ref_dps_id1 ][ j ][ i ] * ( 64 - predWeight0 ) + 32 ) >> 6 + DisparityScale[ index ][ i ][ j ] = disparity_diff_wij[ i ][ j ] + ( DisparityScale[ ref_dps_id0 ][ i ][ j ] * + predWeight0 + DisparityScale[ ref_dps_id1 ][ i ][ j ] * ( 64 - predWeight0 ) + 32 ) >> 6 + DisparityOffset[ index ][ i ][ j ] = disparity_diff_oij[ i ][ j ] + ( DisparityOffset[ ref_dps_id0 ][ i ][ j ] * + predWeight0 + DisparityOffset[ ref_dps_id1 ][ i ][ j ] * ( 64 - predWeight0 ) + 32 ) >> 6 +} + +``` + +(I-12) + +### I.7.4.2.14 Slice layer extension RBSP semantics + +The semantics specified in clause H.7.4.2.13 apply. + +## I.7.4.3 Slice header semantics + +The semantics specified in clause H.7.4.3 apply. + +### I.7.4.3.1 Reference picture list modification semantics + +The semantics specified in clause H.7.4.3.1 apply. + +#### I.7.4.3.1.1 Reference picture list MVC modification semantics + +The semantics specified in clause H.7.4.3.1.1 apply. + +### I.7.4.3.2 Prediction weight table semantics + +The semantics specified in clause H.7.4.3.2 apply. + +### I.7.4.3.3 Decoded reference picture marking semantics + +The semantics specified in clause H.7.4.3.3 apply to each view independently, with "sequence parameter set" being replaced by "3D-AVC sequence parameter set", and "primary coded picture" being replaced by "texture view component" for nal\_unit\_type equal to 1, 5, and 20 as well as nal\_unit\_type 21 when DepthFlag is equal to 1, and by "depth view component" for nal\_unit\_type equal to 21 when DepthFlag is equal to 0. + +### I.7.4.3.4 Slice header in 3D-AVC semantics + +The semantics specified in clause G.7.4.3 apply with the substitution of texture view component or depth view component for view component and with the following modifications. + +When nal\_unit\_type is equal to 1, 5, 20, or 21 with DepthFlag equal to 0, all constraints specified in clause G.7.4.3 apply only to the texture view components with the same value of VOIdx. When nal\_unit\_type is equal to 21 and DepthFlag is equal to 1, all constraints specified in clause G.7.4.3 apply only to the depth view components with the same value of VOIdx. + +The value of the following 3D-AVC sequence parameter set syntax elements shall be the same across all coded slice NAL + +units of nal\_unit\_type 1, 5, 20 and 21 with DepthFlag equal to 0 of an access unit: chroma\_format\_idc. + +The value of the following slice header syntax elements shall be the same across all coded slice NAL units of nal\_unit\_type 1, 5, 20 and 21 with DepthFlag equal to 0 of an access unit: field\_pic\_flag and bottom\_field\_flag. + +The value of the following slice header syntax elements shall be the same across all coded slice NAL units of nal\_unit\_type equal to 21 and DepthFlag equal to 1 of an access unit: field\_pic\_flag and bottom\_field\_flag. + +**pre\_slice\_header\_src, pre\_ref\_lists\_src, pre\_pred\_weight\_table\_src and pre\_dec\_ref\_pic\_marking\_src** specify if the respective syntax elements are present in the slice header, and, if not, the slice header from which the values of the respective syntax elements are taken as specified in Table I-1 and Table I-2. + +When a syntax element has an inferred value in the slice header from which its value is taken according to Table I-1 and Table I-2, the syntax element value in the current slice header is equal to this inferred value. When a syntax element is not present and has no inferred value in the slice header from which its value is taken according to Table I-1 and Table I-2, the syntax element is inferred to be absent in the current slice header. + +pre\_slice\_header\_src shall not be equal to 0. + +When ViewCompOrder( DepthFlag, view\_id ) is smaller than ViewCompOrder( !DepthFlag, view\_id ), pre\_slice\_header\_src, pre\_ref\_lists\_src, pre\_pred\_weight\_table\_src and pre\_dec\_ref\_pic\_marking\_src shall not be equal to 2. + +**Table I-1 – Respective syntax elements for pre\_slice\_header\_src, pre\_ref\_lists\_src, pre\_pred\_weight\_table\_src and pre\_dec\_ref\_pic\_marking\_src** + +| Prediction indication syntax element | Respective syntax elements | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pre_slice_header_src | colour_plane_id, frame_num, field_pic_flag, bottom_field_flag, idr_pic_id, pic_order_cnt_lsb, delta_pic_order_cnt_bottom, delta_pic_order_cnt[ 0 ], delta_pic_order_cnt[ 1 ], redundant_pic_cnt, direct_spatial_mv_pred_flag, cabac_init_idc, sp_for_switch_flag, slice_qs_delta, disable_deblocking_filter_idc, slice_alpha_c0_offset_div2, slice_beta_offset_div2, slice_group_change_cycle, depth_weighted_pred_flag, dmvp_flag, slice_vsp_flag, dps_id | +| pre_ref_lists_src | num_ref_idx_active_override_flag, num_ref_idx_l0_active_minus1, num_ref_idx_l1_active_minus1 and reference picture list modification syntax table | +| pre_pred_weight_table_src | pred_weight_table( ) syntax structure | +| pre_dec_ref_pic_marking_src | dec_ref_pic_marking( ) syntax structure | + +**Table I-2 – Semantics of the values of pre\_slice\_header\_src, pre\_ref\_lists\_src, pre\_pred\_weight\_table\_src and pre\_dec\_ref\_pic\_marking\_src** + +| Value of pre_slice_header_src, pre_ref_lists_src, pre_pred_weight_table_src or pre_dec_ref_pic_marking_src | Semantics | +|------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | The respective syntax elements are not predicted but included in the slice header. | +| 1 | The values of the respective syntax elements are taken from the slice header of the first slice of the previous view component in decoding order having the same value of DepthFlag as the current slice, belonging to a dependent view of the current view, and residing in the same access unit. | +| 2 | The values of the respective syntax elements are taken from the first slice header of the first slice of the view component having the same view_id as the current slice and a different value of DepthFlag. | +| 3 | The values of the respective syntax elements are taken from the first slice header of the first slice of the view component in the same access unit having view order index equal to 0 and the same value of DepthFlag as the current slice. | + +**depth\_weighted\_pred\_flag** equal to 0 specifies that no depth-range-based weighted prediction is used for corresponding + +slice RBSP. **depth\_weighted\_pred\_flag** equal to 1 specifies that depth-range-based weighted prediction is used for corresponding slice RBSP. When not present, **depth\_weighted\_pred\_flag** is inferred to be equal to 0. When **depth\_weighted\_pred\_flag** is equal to 1, the process of derivation of prediction weights specified in clause I.8.2.2 applies. + +**dmvp\_flag** is used in the decoding process for inter prediction, inter-view prediction, view synthesis prediction and adaptive luminance compensation as specified in clause I.8.2. + +**slice\_vsp\_flag** together with **bvsp\_flag[ mbPartIdx ]** specify, when **ref\_idx\_IX[ mbPartIdx ]** (with X equal to 0 or 1) refers to an inter-view reference picture, which motion vector derivation process specified in clause I.8.2.1 is in use. + +**dps\_id** specifies the depth parameter set in use. The value of **dps\_id** shall be in the range of 0 to 63, inclusive. When **dps\_id** is equal to 0, depth parameters are set according to syntax elements in **seq\_parameter\_set\_3dave\_extension( )** of the active sequence parameter set. When present, the value of **dps\_id** shall be the same in all slice headers within an access unit. + +#### I.7.4.4 Slice data semantics + +The semantics specified in clause H.7.4.4 apply. + +##### I.7.4.4.1 Slice data in 3D-AVC extension semantics + +The semantics specified in clause H.7.4.4 apply with the following additions. + +When **mb\_skip\_flag** is not present, it is inferred to be equal to 0. + +**mb\_skip\_type\_flag** is used to derive the variable **MbVSSkipFlag**. When **mb\_skip\_type\_flag** is present, the variable **MbVSSkipFlag** is set equal to **mb\_skip\_type\_flag**. + +**mb\_vsskip\_flag** is used to derive the variable **MbVSSkipFlag**. When **mb\_vsskip\_flag** is present, the variable **MbVSSkipFlag** is set equal to **mb\_vsskip\_flag**. + +NOTE – **MbVSSkipFlag** controls whether clause I.8.2.1.2 or I.8.2.1.3 is used for deriving motion vectors for P\_Skip macroblocks and whether clause I.8.2.1.4 or I.8.2.1.6 is used for deriving motion vectors and reference indices for B\_Skip macroblocks. + +**leftMbVSSkipped** is derived to be 1 if the left macroblock adjacent to the current macroblock is available and the **MbVSSkipFlag** of the left macroblock is equal to 1, **leftMbVSSkipped** is derived to be 0 otherwise. + +**upMbVSSkipped** is derived to be 1 if the upper macroblock adjacent to the current macroblock is available and the **MbVSSkipFlag** of the upper macroblock is equal to 1, **upMbVSSkipped** is derived to be 0 otherwise. + +The function **RLESkipContext( )** is specified as follows: + +- The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to **mbAddrA** and **mbAddrB**; +- If all of the following conditions are true, the return value of **RLESkipContext( )** is equal to TRUE. + - **enable\_rle\_skip\_flag** is equal to 1 + - **nal\_unit\_type** is equal to 21 + - **slice\_type** is equal to B + - **mbAddrA** is unavailable or **mb\_skip\_flag** for the macroblock **mbAddrA** is equal to 1 + - **mbAddrB** is unavailable or **mb\_skip\_flag** for the macroblock **mbAddrB** is equal to 1 +- Otherwise, the return value of **RLESkipContext( )** is equal to FALSE. + +**mb\_skip\_run\_type** equal to 0 specifies that **mb\_skip\_run\_type** is not present in the **slice\_data( )** until **mb\_skip\_flag** is equal 0. When **RunLength** is greater than 0 and **mb\_skip\_run\_type** equal to 1, **mb\_skip\_flag** is inferred to be equal to 1. **mb\_skip\_run\_type** shall be equal to 0 or 1. + +**mb\_alc\_skip\_flag** equal to 1 specifies that the adaptive luminance compensation is applied for the current macroblock. **mb\_alc\_skip\_flag** equal to 0 specifies that the adaptive luminance compensation is not applied for the current macroblock. When not present, **mb\_alc\_skip\_flag** is inferred to be equal to 0. When **mb\_alc\_skip\_flag** is equal to 1, the current macroblock shall be coded as P\_Skip. + +#### I.7.4.5 Macroblock layer semantics + +The semantics specified in clause H.7.4.5 apply. + +#### I.7.4.5.1 Macroblock prediction semantics + +The semantics specified in clause H.7.4.5.1 apply. + +#### I.7.4.5.2 Sub-macroblock prediction semantics + +The semantics specified in clause H.7.4.5.2 apply. + +#### I.7.4.5.3 Residual data semantics + +The semantics specified in clause H.7.4.5.3 apply. + +##### I.7.4.5.3.1 Residual luma semantics + +The semantics specified in clause H.7.4.5.3.1 apply. + +##### I.7.4.5.3.2 Residual block CAVLC semantics + +The semantics specified in clause H.7.4.5.3.2 apply. + +##### I.7.4.5.3.3 Residual block CABAC semantics + +The semantics specified in clause H.7.4.5.3.3 apply. + +#### I.7.4.6 Macroblock layer in 3D-AVC extension semantics + +The semantics specified in clause H.7.4.5 apply by replacing Table 7-13 with Table I-3 and with the following additions. + +**mb\_direct\_type\_flag** is used to determine the derivation process for motion vectors and reference indices for B\_Direct\_16x16 macroblocks and B\_Direct\_8x8 sub-macroblocks as specified in clause I.8.2.1. + +**mb\_alc\_flag** equal to 1 specifies that the adaptive luminance compensation mode is in use for the current macroblock. mb\_alc\_flag equal to 0 specifies that the adaptive luminance compensation mode is not in use for the current macroblock. When mb\_alc\_flag is not present, it is inferred to be equal to 0. When mb\_alc\_flag is equal to 1, the current macroblock shall be coded as P\_L0\_16x16, P\_L0\_L0\_16x8, or P\_L0\_L0\_8x16. + +**Table I-3 – Macroblock type values 0 to 4 for P and SP slices** + +| mb_type | Name of mb_type | NumMbPart (mb_type) | MbPartPredMode (mb_type, 0) | MbPartPredMode (mb_type, 1) | MbPartWidth (mb_type) | MbPartHeight (mb_type) | +|----------|------------------------------------------|---------------------|-----------------------------|-----------------------------|-----------------------|------------------------| +| 0 | P_L0_16x16 | 1 | Pred_L0 | na | 16 | 16 | +| 1 | P_L0_L0_16x8 | 2 | Pred_L0 | Pred_L0 | 16 | 8 | +| 2 | P_L0_L0_8x16 | 2 | Pred_L0 | Pred_L0 | 8 | 16 | +| 3 | P_8x8 | 4 | na | na | 8 | 8 | +| 4 | P_8x8ref0 | 4 | na | na | 8 | 8 | +| inferred | P_Skip (when MbVSSkipFlag is equal to 0) | 1 | Pred_L0 | na | 16 | 16 | +| inferred | P_Skip (when MbVSSkipFlag is equal to 1) | 4 | Pred_L0 | na | 8 | 8 | + +#### I.7.4.6.1 Macroblock prediction in 3D-AVC extension semantics + +The semantics specified in clause H.7.4.5.1 apply with the following additions. + +**bvsp\_flag\_IX[ mbPartIdx ]** (X being equal to 0 or 1) equal to 0 specifies, when **ref\_idx\_IX[ mbPartIdx ]** (with X equal to 0 or 1) refers to an inter-view reference picture, which motion vector derivation process specified in clause I.8.2.1 is in use. When **bvsp\_flag\_IX[ mbPartIdx ]** is not present and **VspRefLXFlag[ mbPartIdx ]** is equal to 0, **bvsp\_flag\_IX[ mbPartIdx ]** is inferred to be equal to 0. When **bvsp\_flag\_IX[ mbPartIdx ]** is not present and **VspRefLXFlag[ mbPartIdx ]** is equal to 1, **bvsp\_flag\_IX[ mbPartIdx ]** is inferred to be equal to **slice\_vsp\_flag**. + +#### I.7.4.6.2 Sub-macroblock prediction in 3D-AVC semantics + +The semantics specified in clause H.7.4.5.2 apply with the following additions. + +**bvsp\_flag\_IX[ mbPartIdx ]** has the same semantics as **bvsp\_flag\_IX[ mbPartIdx ]** in clause I.7.4.6.1. + +**sub\_mb\_type** shall be equal to **P\_L0\_8x8** when both of the following apply: + +- The macroblock type is equal to a P macroblock type. +- **bvsp\_flag\_10[ mbPartIdx ]** is equal to 1. + +**sub\_mb\_type** shall be equal to **B\_L0\_8x8**, **B\_L1\_8x8**, or **B\_Bi\_8x8** when both of the following apply: + +- The macroblock type is equal to a B macroblock type. +- **bvsp\_flag\_10[ mbPartIdx ]** is equal to 1 or **bvsp\_flag\_11[ mbPartIdx ]** is equal to 1. + +### I.8 3D-AVC decoding process + +This clause specifies the decoding process for an access unit of a coded video sequence conforming to one or more of the profiles specified in this annex. Specifically, this clause specifies how the decoded picture with multiple texture view components and multiple depth view components is derived from syntax elements and global variables that are derived from NAL units in an access unit when the decoder is decoding the operation point identified by the target temporal level and the target output views. + +The decoding process is specified such that all decoders shall produce numerically identical results for the target output views. Any decoding process that produces identical results for the target output views to the process described here conforms to the decoding process requirements of this Recommendation | International Standard. + +Unless stated otherwise, the syntax elements and derived upper-case variables that are referred to by the decoding process specified in this clause and all child processes invoked from the process specified in this clause are the syntax elements and derived upper-case variables for the current access unit. + +The target output texture and depth views are either specified by external means not specified in this Specification, or, when not specified by external means, there shall be one target output texture view which is the base texture view. + +NOTE – The association of **VOIdx** values to **view\_id** values according to the decoding process of clause H.8 may differ from that of the decoding process of clause G.8. + +A target output view may include only a texture view, only a depth view, or both the texture view and the depth view, which have the same **view\_id** value. + +All sub-bitstreams that can be derived using the sub-bitstream extraction process with **pIdTarget** equal to any value in the range of 0 to 63, inclusive, **tIdTarget** equal to any value in the range of 0 to 7, inclusive, **viewIdTargetList** consisting of any one or more **viewIdTarget**'s identifying the views in the bitstream as inputs as specified in clause I.8.3 shall result in a set of coded video sequences, with each coded video sequence conforming to one or more of the profiles specified in Annex A, Annex G, Annex H and Annex I. + +Let **vOIdxList** be a list of integer values specifying the **VOIdx** values of the view components of the access unit. The variable **VOIdxMax** is set equal to the maximum value of the entries in the list **vOIdxList**, and the variable **vOIdxMin** is set to the minimum value of the entries in the list **vOIdxList**. **VOIdxMax** shall be the same for all access units within a coded video sequence. **vOIdxMin** shall be the same for all anchor access units within a coded video sequence. When the current access unit is an anchor access unit, the variable **VOIdxMin** is set to **vOIdxMin**. + +The 3D-AVC decoding process specified in this clause is repeatedly invoked for each texture and depth view component with **VOIdx** from **vOIdxMin** to **VOIdxMax**, inclusive, which is present in the list **vOIdxList**, in increasing order of **VOIdx** and in decoding order of texture or depth view components as specified in clause I.7.4.1.2.5. + +Outputs of the multiview video decoding process are decoded samples of the current primary coded picture including all decoded texture and depth view components of the target output texture and depth views. + +For each texture view component and each depth view component, **TextureFirstFlag** is set equal to $( \text{NumDepthViews} == 0 \mid\mid ( \text{ViewCompOrder}( 0, \text{view\_idx} ) < \text{ViewCompOrder}( 1, \text{view\_idx} ) ? 1 : 0 ) )$ , and the specifications in clause H.8 apply, with the decoding process for reference picture lists construction being modified in + +clause I.8.1. The 3D-AVC inter prediction, inter-view prediction, view synthesis prediction and inter prediction with adaptive luminance compensation processes are specified in clause I.8.3. The decoding process for depth range parameters is specified in clause I.8.4. Additionally, the specification of sub-bitstreams is specified in clause I.8.2. + +### I.8.1 3D-AVC decoding process for reference picture lists construction + +The specifications of clause H.8.1 apply with the following additions: + +- When DepthFlag is equal to 0, the variable VspRefExist is specified after applying clause G.8.2 as follows: + - If seq\_view\_synthesis\_flag is equal to 0 (view synthesis prediction is disabled), VspRefExist is set to 0. + - Otherwise, if the current slice is a P or SP slice and there exists at least one inter-view reference component in RefPicList0, or if the current slice is a B slice and there exists at least one inter-view reference component in either RefPicList0 or RefPicList1, VspRefExist is set to 1; + - Otherwise, VspRefExist is set to 0. +- The variable VspRefL0Flag[ mbPartIdx ] is specified as follows: + - If VspRefExist is equal to 1, ref\_idx\_l0[ mbPartIdx ] is present, and ref\_idx\_l0[ mbPartIdx ] indicates an inter-view reference component, the variable VspRefL0Flag[ mbPartIdx ] is set to 1. + - Otherwise, the variable VspRefL0Flag[ mbPartIdx ] is set to 0. +- The variable VspRefL1Flag[ mbPartIdx ] is specified as follows: + - If VspRefExist is equal to 1, ref\_idx\_l1[ mbPartIdx ] is present, and ref\_idx\_l1[ mbPartIdx ] indicates an inter-view reference component, the variable VspRefL1Flag[ mbPartIdx ] is set to 1. + - Otherwise, the variable VspRefL1Flag[ mbPartIdx ] is set to 0. + +### I.8.2 3D-AVC inter prediction, inter-view prediction, view synthesis prediction and adaptive luminance compensation + +This process is invoked when decoding P and B macroblock types and when nal\_unit\_type is equal to 21. + +Outputs of this process are Inter prediction samples for the current macroblock that are a 16x16 array predL of luma samples and when ChromaArrayType is not equal to 0 two (MbWidthC)x(MbHeightC) arrays predCb and predCr of chroma samples, one for each of the chroma components Cb and Cr. + +When DepthFlag is equal to 0 and dmvp\_flag or slice\_vsp\_flag is equal to 1, the variables DepthRefPicList0, DepthRefPicList1 for B slices, and DepthCurrPic are specified as follows. The variable DepthRefPicList0 is specified to consist of the depth view components of the view component pairs for which the texture view components are in RefPicList0 in the order that RefPicList0[ i ] and DepthRefPicList0[ i ] form a view component pair for any value of i = 0.. num\_ref\_idx\_l0\_active\_minus1. The variable DepthRefPicList1 is specified for B slices to consist of the depth view components of the view component pairs for which the texture view components are in RefPicList1 in the order that RefPicList1[ i ] and DepthRefPicList1[ i ] form a view component pair for any value of i = 0.. num\_ref\_idx\_l1\_active\_minus1. The variable DepthCurrPic is specified to be the decoded sample array of the depth view component of the view component pair for which the texture view component is the current texture view component when TextureFirstFlag is equal to 0 and it is specified to be the decoded sample array of the depth view component of the view component pair for which the texture view component is the texture view component of the base view when TextureFirstFlag is equal to 1. + +The partitioning of a macroblock is specified by mb\_type. Each macroblock partition is referred to by mbPartIdx. When the macroblock partitioning consists of partitions that are equal to sub-macroblocks, each sub-macroblock can be further partitioned into sub-macroblock partitions as specified by sub\_mb\_type[ mbPartIdx ]. Each sub-macroblock partition is referred to by subMbPartIdx. When the macroblock partitioning does not consist of sub-macroblocks, subMbPartIdx is set equal to 0. + +The following steps are specified for each macroblock partition or for each sub-macroblock partition. + +The functions MbPartWidth( ), MbPartHeight( ), SubMbPartWidth( ), and SubMbPartHeight( ) describing the width and height of macroblock partitions and sub-macroblock partitions are specified in Tables 7-14, 7-17, 7-18, and I-3. For the decoding processes specified in this clause, its subclauses, and any subclauses invoked by the decoding processes specified in this clause or its subclauses, references to Table 7-13 are replaced by references to Table I-3. + +When nal\_unit\_type is equal to 21, DepthFlag is equal to 0, TextureFirstFlag is equal to 1, InterViewRefAvailable is equal to 1 and either dmvp\_flag or seq\_view\_synthesis\_flag is equal to 1, DvMBX is set equal to zero when CurrMbAddr is equal to first\_mb\_in\_slice, and clause I.8.2.1.8 is invoked. + +The range of the macroblock partition index mbPartIdx is derived as follows: + +- If mb\_type is equal to B\_Skip or B\_Direct\_16x16, mbPartIdx proceeds over values 0..3. +- Otherwise (mb\_type is not equal to B\_Skip or B\_Direct\_16x16), mbPartIdx proceeds over values 0..NumMbPart( mb\_type ) – 1. + +For each value of mbPartIdx, the variables partWidth and partHeight for the width and height of each macroblock partition or sub-macroblock partition in the macroblock are derived as follows: + +- If mb\_type is not equal to P\_8x8, P\_8x8ref0, B\_Skip, B\_Direct\_16x16, or B\_8x8, subMbPartIdx is set equal to 0 and the following applies: + +$$\text{partWidth} = \text{MbPartWidth}(\text{mb\_type}) \quad (\text{I-13})$$ + +$$\text{partHeight} = \text{MbPartHeight}(\text{mb\_type}) \quad (\text{I-14})$$ + +- Otherwise, if mb\_type is equal to P\_8x8 or P\_8x8ref0, or mb\_type is equal to B\_8x8 and sub\_mb\_type[ mbPartIdx ] is not equal to B\_Direct\_8x8, subMbPartIdx proceeds over values 0..NumSubMbPart( sub\_mb\_type[ mbPartIdx ] ) – 1, and partWidth and partHeight are derived as: + +$$\text{partWidth} = \text{SubMbPartWidth}(\text{sub\_mb\_type}[\text{mbPartIdx}]) \quad (\text{I-15})$$ + +$$\text{partHeight} = \text{SubMbPartHeight}(\text{sub\_mb\_type}[\text{mbPartIdx}]) \quad (\text{I-16})$$ + +- Otherwise (mb\_type is equal to B\_Skip or B\_Direct\_16x16, or mb\_type is equal to B\_8x8 and sub\_mb\_type[ mbPartIdx ] is equal to B\_Direct\_8x8), the following applies: + +- If either MbVSSkipFlag or mb\_direct\_type\_flag is equal to 1, subMbPartIdx is set to 0 and partWidth and partHeight are derived as: + +$$\text{partWidth} = 8 \quad (\text{I-17})$$ + +$$\text{partHeight} = 8 \quad (\text{I-18})$$ + +- Otherwise (both MbVSSkipFlag and mb\_direct\_type\_flag are equal to 0), subMbPartIdx proceeds over values 0..3, and partWidth and partHeight are derived as: + +$$\text{partWidth} = 4 \quad (\text{I-19})$$ + +$$\text{partHeight} = 4 \quad (\text{I-20})$$ + +When ChromaArrayType is not equal to 0, the variables partWidthC and partHeightC are derived as: + +$$\text{partWidthC} = \text{partWidth} / \text{SubWidthC} \quad (\text{I-21})$$ + +$$\text{partHeightC} = \text{partHeight} / \text{SubHeightC} \quad (\text{I-22})$$ + +Let the variable MvCnt be initially set equal to 0 before any invocation of clause I.8.2.1, I.8.2.3 or 8.4.1 for the macroblock. + +The Inter prediction process for a macroblock partition mbPartIdx and a sub-macroblock partition subMbPartIdx consists of the following ordered steps: + +1. The following applies: + +- If nal\_unit\_type is equal to 21 and DepthFlag is equal to 0, the following applies: + - If mb\_alc\_skip\_flag is equal to 1 or mb\_alc\_flag is equal to 1, clause I.8.2.3 is invoked. + - Otherwise, if dmvp\_flag or slice\_vsp\_flag is equal to 1, clause I.8.2.1 is invoked. + - Otherwise, clause 8.4.1 is invoked. +- Otherwise, the derivation process for motion vector components and reference indices as specified in clause 8.4.1 is invoked. + +Inputs to the processes in clauses I.8.2.1, I.8.2.3 and 8.4.1 are: + +- a macroblock partition mbPartIdx, + +- a sub-macroblock partition subMbPartIdx. + +Outputs of the processes in clauses I.8.2.1, I.8.2.3 and 8.4.1 are: + +- luma motion vectors mvL0 and mvL1 and when ChromaArrayType is not equal to 0, the chroma motion vectors mvCL0 and mvCL1 +- reference indices refIdxL0 and refIdxL1 +- prediction list utilization flags predFlagL0 and predFlagL1 +- the sub-macroblock partition motion vector count subMvCnt. + +2. The variable MvCnt is incremented by subMvCnt. + +3. When (weighted\_pred\_flag is equal to 1 and (slice\_type % 5) is equal to 0 or 3) or (weighted\_bipred\_idc is greater than 0 and (slice\_type % 5) is equal to 1), the following applies: + +- If mb\_alc\_skip\_flag is equal to 1 or mb\_alc\_flag is equal to 1, clause I.8.2.4 is invoked. +- Otherwise, the derivation process for prediction weights as specified in clause 8.4.3 is invoked. + +Inputs to these processes in clauses 8.4.3 and I.8.2.4 are: + +- reference indices refIdxL0 and refIdxL1 +- prediction list utilization flags predFlagL0 and predFlagL1 + +Outputs of these processes in clauses 8.4.3 and I.8.2.4 are variables for weighted prediction logWDC, w0C, w1C, o0C, o1C with C being replaced by L and, when ChromaArrayType is not equal to 0, Cb and Cr. + +4. When (nal\_unit\_type is equal to 21 and depth\_weighted\_pred\_flag is equal to 1 and (slice\_type % 5) is equal to 0 or 3) or (depth\_weighted\_bipred\_flag is equal to 1 and (slice\_type % 5) is equal to 1), the derivation process for prediction weights in depth-range-based weighted prediction in clause I.8.2.2 is invoked. + +5. The decoding process for Inter prediction samples as specified in clause 8.4.2 is invoked. + +Inputs to this process are: + +- a macroblock partition mbPartIdx, +- a sub-macroblock partition subMbPartIdx, +- variables specifying partition width and height for luma and chroma (if available), partWidth, partHeight, partWidthC (if available), and partHeightC (if available), +- luma motion vectors mvL0 and mvL1 and when ChromaArrayType is not equal to 0, the chroma motion vectors mvCL0 and mvCL1, +- reference indices refIdxL0 and refIdxL1, +- prediction list utilization flags predFlagL0 and predFlagL1, +- variables for weighted prediction logWDC, w0C, w1C, o0C, o1C with C being replaced by L and, when ChromaArrayType is not equal to 0, Cb and Cr. + +Outputs of this process are inter prediction samples (pred); which are a (partWidth)x(partHeight) array predPartL of prediction luma samples and when ChromaArrayType is not equal to 0 two (partWidthC)x(partHeightC) arrays predPartCr and predPartCb of prediction chroma samples, one for each of the chroma components Cb and Cr. + +For use in derivation processes of variables invoked later in the decoding process, the following assignments are made: + +$$\text{MvL0[ mbPartIdx ][ subMbPartIdx ]} = \text{mvL0} \quad (\text{I-23})$$ + +$$\text{MvL1[ mbPartIdx ][ subMbPartIdx ]} = \text{mvL1} \quad (\text{I-24})$$ + +$$\text{RefIdxL0[ mbPartIdx ]} = \text{refIdxL0} \quad (\text{I-25})$$ + +$$\text{RefIdxL1[ mbPartIdx ]} = \text{refIdxL1} \quad (\text{I-26})$$ + +$$\text{PredFlagL0[ mbPartIdx ]} = \text{predFlagL0} \quad (\text{I-27})$$ + +$$\text{PredFlagL1[ mbPartIdx ]} = \text{predFlagL1} \quad (\text{I-28})$$ + +The location of the upper-left sample of the macroblock partition relative to the upper-left sample of the macroblock is derived by invoking the inverse macroblock partition scanning process as described in clause 6.4.2.1 with $mbPartIdx$ as the input and $(xP, yP)$ as the output. + +The location of the upper-left sample of the sub-macroblock partition relative to the upper-left sample of the macroblock partition is derived by invoking the inverse sub-macroblock partition scanning process as described in clause I.6.1 with $subMbPartIdx$ as the input and $(xS, yS)$ as the output. + +The macroblock prediction is formed by placing the macroblock or sub-macroblock partition prediction samples in their correct relative positions in the macroblock, as follows. + +The variable $pred_L[xP + xS + x, yP + yS + y]$ with $x = 0..partWidth - 1$ , $y = 0..partHeight - 1$ is derived by: + +$$pred_L[xP + xS + x, yP + yS + y] = predPartL[x, y] \quad (I-29)$$ + +When $ChromaArrayType$ is not equal to 0, the variable $pred_C$ with $x = 0..partWidthC - 1$ , $y = 0..partHeightC - 1$ , and $C$ in $pred_C$ and $predPart_C$ being replaced by $Cb$ or $Cr$ is derived by: + +$$pred_C[xP / SubWidthC + xS / SubWidthC + x, yP / SubHeightC + yS / SubHeightC + y] = predPartC[x, y] \quad (I-30)$$ + +### I.8.2.1 Derivation process for motion vector components and reference indices + +Inputs to this process are: + +- a macroblock partition $mbPartIdx$ , +- a sub-macroblock partition $subMbPartIdx$ . + +Outputs of this process are: + +- luma motion vectors $mvL0$ and $mvL1$ and when $ChromaArrayType$ is not equal to 0, the chroma motion vectors $mvCL0$ and $mvCL1$ , +- reference indices $refIdxL0$ and $refIdxL1$ , +- prediction list utilization flags $predFlagL0$ and $predFlagL1$ , +- a motion vector count variable $subMvCnt$ . + +For the derivation of the variables $mvL0$ and $mvL1$ as well as $refIdxL0$ and $refIdxL1$ , the following applies: + +- If $mb\_type$ is equal to $P\_Skip$ , the following applies: + - If $MbVSSkipFlag$ is equal to 0, the following applies: + - If $nal\_unit\_type$ is equal to 21 and $DepthFlag$ is equal to 0 and $dmvp\_flag$ is equal to 1, the depth-based derivation process for luma motion vectors for skipped macroblock in P and SP slices in clause I.8.2.1.2 is invoked with the output being the luma motion vectors $mvL0$ and reference indices $refIdxL0$ , and $predFlagL0$ is set equal to 1. + - Otherwise ( $nal\_unit\_type$ is not equal to 21 or $DepthFlag$ is equal to 1 or $dmvp\_flag$ is equal to 0), the derivation process for luma motion vectors for skipped macroblock in P and SP slices in clause 8.4.1.1 is invoked with the output being the luma motion vectors $mvL0$ and reference indices $refIdxL0$ , and $predFlagL0$ is set equal to 1. + - Otherwise ( $MbVSSkipFlag$ is equal to 1), the derivation process for luma motion vectors for VSP skipped macroblock in P and SP slices in clause I.8.2.1.3 is invoked with $mbPartIdx$ as input and with the output being the luma motion vectors $mvL0$ and reference indices $refIdxL0$ , and $predFlagL0$ is set equal to 1. + - $mvL1$ and $refIdxL1$ are marked as not available and $predFlagL1$ is set equal to 0. The motion vector count variable $subMvCnt$ is set equal to 1. +- Otherwise, if $mb\_type$ is equal to $B\_Skip$ or $B\_Direct\_16x16$ or $sub\_mb\_type[mbPartIdx]$ is equal to $B\_Direct\_8x8$ , the following applies. + - The variable $vspFlag$ is specified as follows: + +$$\begin{aligned} \text{vspFlag} = & !(\text{sub\_type}[ \text{mbPartIdx} ] == \text{B\_Direct\_8x8} \mid \mid \\ & (\text{mb\_type} == \text{B\_Skip} \&\& \text{MbVSSkipFlag} == 0) \mid \mid \\ & (\text{mb\_type} == \text{B\_Direct\_16x16} \&\& !\text{mb\_direct\_type\_flag} ) ) \end{aligned} \quad (\text{I-31})$$ + +- If $\text{vspFlag}$ is equal to 0 and $\text{nal\_unit\_type}$ is equal to 21 and $\text{DepthFlag}$ is equal to 0 and $\text{dmvp\_flag}$ is equal to 1, the depth-based derivation process for luma motion vectors for $\text{B\_Skip}$ , $\text{B\_Direct\_16x16}$ , and $\text{B\_Direct\_8x8}$ in B slices in clause I.8.2.1.4 is invoked with $\text{mbPartIdx}$ and $\text{subMbPartIdx}$ as the input and the output being the luma motion vectors $\text{mvL0}$ , $\text{mvL1}$ , the reference indices $\text{refIdxL0}$ , $\text{refIdxL1}$ , the motion vector count variable $\text{subMvCnt}$ , and the prediction utilization flags $\text{predFlagL0}$ and $\text{predFlagL1}$ . +- Otherwise, if both of the following are true: + - $\text{vspFlag}$ is equal to 0, and + - $\text{nal\_unit\_type}$ is not equal to 21 or $\text{DepthFlag}$ is equal to 1 or $\text{dmvp\_flag}$ is equal to 0, + +the derivation process for luma motion vectors for $\text{B\_Skip}$ , $\text{B\_Direct\_16x16}$ , and $\text{B\_Direct\_8x8}$ in B slices in clause 8.4.1.2 is invoked with $\text{mbPartIdx}$ and $\text{subMbPartIdx}$ as the input and the output being the luma motion vectors $\text{mvL0}$ , $\text{mvL1}$ , the reference indices $\text{refIdxL0}$ , $\text{refIdxL1}$ , the motion vector count variable $\text{subMvCnt}$ , and the prediction utilization flags $\text{predFlagL0}$ and $\text{predFlagL1}$ . + +- Otherwise ( $\text{vspFlag}$ is equal to 1), the derivation process in clause I.8.2.1.6 is invoked with $\text{mbPartIdx}$ as input and with the output being the luma motion vectors $\text{mvL0}$ and $\text{mvL1}$ and reference indices $\text{refIdxL0}$ and $\text{refIdxL1}$ . +- Otherwise, for X being replaced by either 0 or 1 in the variables $\text{predFlagLX}$ , $\text{mvLX}$ , $\text{refIdxLX}$ , and in $\text{Pred\_LX}$ and in the syntax elements $\text{ref\_idx\_IX}$ and $\text{mvd\_IX}$ , the following applies: + +1. The variables $\text{refIdxLX}$ and $\text{predFlagLX}$ are derived as follows: + +- If $\text{MbPartPredMode}(\text{mb\_type}, \text{mbPartIdx})$ or $\text{SubMbPredMode}(\text{sub\_mb\_type}[ \text{mbPartIdx} ])$ is equal to $\text{Pred\_LX}$ or to $\text{BiPred}$ , + +$$\text{refIdxLX} = \text{ref\_idx\_IX}[ \text{mbPartIdx} ] \quad (\text{I-32})$$ + +$$\text{predFlagLX} = 1 \quad (\text{I-33})$$ + +- Otherwise, the variables $\text{refIdxLX}$ and $\text{predFlagLX}$ are specified by + +$$\text{refIdxLX} = -1 \quad (\text{I-34})$$ + +$$\text{predFlagLX} = 0 \quad (\text{I-35})$$ + +2. The motion vector count variable $\text{subMvCnt}$ is set equal to $\text{predFlagL0} + \text{predFlagL1}$ . + +3. The variable $\text{currSubMbType}$ is derived as follows: + +- If the macroblock type is equal to $\text{B\_8x8}$ , $\text{currSubMbType}$ is set equal to $\text{sub\_mb\_type}[ \text{mbPartIdx} ]$ . +- Otherwise (the macroblock type is not equal to $\text{B\_8x8}$ ), $\text{currSubMbType}$ is set equal to "na". + +4. The following applies: + +- If $\text{VspRefLXFlag}[ \text{mbPartIdx} ]$ is equal to 0 or both $\text{VspRefLXFlag}[ \text{mbPartIdx} ]$ is equal to 1 and $\text{bvsp\_flag\_IX}[ \text{mbPartIdx} ]$ is equal to 0, the following applies: + +- When $\text{predFlagLX}$ is equal to 1 and $\text{DepthFlag}$ is equal to 0 and $\text{dmvp\_flag}$ is equal to 1, the derivation process for luma motion vector prediction in clause I.8.2.1.7 is invoked with $\text{mbPartIdx}$ , $\text{subMbPartIdx}$ , $\text{refIdxLX}$ , and $\text{currSubMbType}$ as the inputs and the output being $\text{mvpLX}$ . +- When $\text{predFlagLX}$ is equal to 1 and either $\text{DepthFlag}$ is equal to 1 or $\text{dmvp\_flag}$ is equal to 0, the derivation process for luma motion vector prediction in clause 8.4.1.3 is invoked with $\text{mbPartIdx}$ , $\text{subMbPartIdx}$ , $\text{refIdxLX}$ , and $\text{currSubMbType}$ as the inputs and the output being $\text{mvpLX}$ . +- The luma motion vectors are derived by + +$$\text{mvLX}[ 0 ] = \text{mvpLX}[ 0 ] + \text{mvd\_IX}[ \text{mbPartIdx} ][ \text{subMbPartIdx} ][ 0 ] \quad (\text{I-36})$$ + +$$\text{mvLX}[ 1 ] = \text{mvpLX}[ 1 ] + \text{mvd\_IX}[ \text{mbPartIdx} ][ \text{subMbPartIdx} ][ 1 ] \quad (\text{I-37})$$ + +- Otherwise (VspReflXFlag[ mbPartIdx ] is equal to 1 and bvsp\_flag\_IX[ mbPartIdx ] is equal to 1), the following applies: + - If TextureFirstFlag is equal to 0, the depth-based disparity value derivation process in clause I.8.2.1.1 is invoked with depthPic equal to DepthCurrPic, (textureX, textureY) equal to the location of the top-left sample of macroblock partition mbPartIdx, tBIWidth equal to the width the macroblock partition mbPartIdx, tBIHeight equal to the height the macroblock partition mbPartIdx, srcViewId equal to view\_id and refViewId equal to the view\_id of refIdxLX as inputs and the output assigned to mvLX[ 0 ] and mvLX[ 1 ] is set equal to 0. + - Otherwise (TextureFirstFlag is equal to 1), the depth-based disparity value derivation process in clause I.8.2.1.1 is invoked with depthPic equal to DepthCurrPic, (textureX, textureY) equal to sum of ( DvMBX >> 2, 0 ) and the location of the top-left sample of current macroblock partition, tBIWidth equal to the width the macroblock partition mbPartIdx, tBIHeight equal to the height the macroblock partition mbPartIdx, srcViewId equal to view\_id and refViewId equal to 0 as inputs and the output assigned to mvLX[ 0 ] and mvLX[ 1 ] is set equal to 0. + +When ChromaArrayType is not equal to 0 and predFlagLX (with X being either 0 or 1) is equal to 1, the derivation process for chroma motion vectors in clause 8.4.1.4 is invoked with mvLX and refIdxLX as input and the output being mvCLX. + +#### I.8.2.1.1 Depth-based disparity value derivation process + +Inputs to this process are: + +- a decoded depth view component depthPic, +- the location (textureX, textureY) of the block in a texture view component for which the disparity value is derived, +- the width tBIWidth and the height tBIHeight of the block in a texture view component for which the disparity value is derived, +- the view\_id value srcViewId of the texture view component for which the disparity value is derived, and +- the view\_id value refViewId of the reference view for the disparity value. + +Output of this process is a disparity value dispVal. + +The derivation of the disparity value dispVal is specified with the following ordered steps. + +1. The variables depthX, depthY, blWidth and blHeight are specified as follows: + +$$\begin{aligned} + \text{dHM} &= \text{depth\_hor\_mult\_minus1} + 1 \\ + \text{dVM} &= \text{depth\_ver\_mult\_minus1} + 1 \\ + \text{depthX} &= \text{Clip3}(\text{DepthCropLeftCoord}, \text{DepthCropRightCoord}, \\ + &\quad ((\text{textureX} + \text{grid\_pos\_x}[\text{srcViewId}]) * \text{dHM}) \gg \text{depth\_hor\_rsh}) \\ + \text{depthY} &= \text{Clip3}(\text{DepthCropTopCoord}, \text{DepthCropBottomCoord}, \\ + &\quad ((\text{textureY} + \text{grid\_pos\_y}[\text{srcViewId}]) * \text{dVM}) \gg \text{depth\_ver\_rsh}) \\ + \text{depthXN} &= \text{Clip3}(\text{DepthCropLeftCoord}, \text{DepthCropRightCoord}, \\ + &\quad ((\text{textureX} + \text{grid\_pos\_x}[\text{srcViewId}] + \text{tBIWidth} - 1) * \text{dHM}) \gg \text{depth\_hor\_rsh}) \\ + \text{depthYN} &= \text{Clip3}(\text{DepthCropTopCoord}, \text{DepthCropBottomCoord}, \\ + &\quad ((\text{textureY} + \text{grid\_pos\_y}[\text{srcViewId}] + \text{tBIHeight} - 1) * \text{dVM}) \gg \text{depth\_ver\_rsh}) \\ + \text{blWidth} &= \text{depthXN} - \text{depthX} + 1 \\ + \text{blHeight} &= \text{depthYN} - \text{depthY} + 1 + \end{aligned} \tag{I-38}$$ + +2. The variable maxDepth is specified as follows: + +$$\begin{aligned} + \text{maxDepth} &= -\infty \\ + \text{for}(j = 0; j < \text{blHeight}; j += (\text{blHeight} - 1)) \\ + \text{for}(i = 0; i < \text{blWidth}; i += (\text{blWidth} - 1)) \\ + \text{if}(\text{depthPic}[\text{depthX} + i, \text{depthY} + j] > \text{maxDepth}) \\ + \text{maxDepth} &= \text{depthPic}[\text{depthX} + i, \text{depthY} + j] + \end{aligned} \tag{I-39}$$ + +3. The variable dispVal is specified as follows: + +$$\begin{aligned} +& \text{log2Div} = \text{BitDepth}_y + 6 \\ +& \text{srcIndex} = \text{ViewIdTo3DVAcquisitionParamIndex}( \text{srcViewId} ) \\ +& \text{refIndex} = \text{ViewIdTo3DVAcquisitionParamIndex}( \text{refViewId} ) \\ +& \text{dispVal} = ( \text{NdrInverse}[ \text{maxDepth} ] * \text{DisparityScale}[ \text{dps\_id} ][ \text{srcIndex} ][ \text{refIndex} ] + \\ +& \quad ( \text{DisparityOffset}[ \text{dps\_id} ][ \text{srcIndex} ][ \text{refIndex} ] \ll \text{BitDepth}_y ) + \\ +& \quad ( 1 \ll ( \text{log2Div} - 1 ) ) ) \gg \text{log2Div} +\end{aligned}$$ + +(I-40) + +#### I.8.2.1.2 Depth-based derivation process for luma motion vectors for skipped macroblocks in P and SP slices + +This process is invoked when mb\_type is equal to P\_Skip, nal\_unit\_type is equal to 21, DepthFlag is equal to 0, dmvp\_flag is equal to 1 and MbVSSkipFlag is equal to 0. + +Outputs of this process are: + +- the motion vector *mvL0*, +- the reference index *refIdxL0*. + +For the derivation of the motion vector *mvL0* and *refIdxL0* of a P\_Skip macroblock type, the following ordered steps are specified: + +1. The process specified in clause I.8.2.1.5 is invoked with mbPartIdx set equal to 0, subMbPartIdx set equal to 0, currSubMbType set equal to "na", and listSuffixFlag equal to 0 as input and the output is assigned to the motion vector *mvL0* and the reference index *refIdxL0*. +2. When *refIdxL0* is equal to -1, the following applies: + - The reference index *refIdxL0* is set to 0. + - The derivation process for luma motion vector prediction in clause I.8.2.1.7 is invoked with mbPartIdx set equal to 0, subMbPartIdx set equal to 0, *refIdxL0*, and currSubMbType = "na" as the inputs and the output being *mvL0*. + +#### I.8.2.1.3 Derivation process for luma motion vectors for VSP skipped macroblocks in P and SP slices + +This process is invoked when mb\_type is equal to P\_Skip, nal\_unit\_type is equal to 21, DepthFlag is equal to 0, and MbVSSkipFlag is equal to 1. + +Inputs to this process are current macroblock partition index mbPartIdx. + +Outputs of this process are the motion vector *mvL0* and the reference index *refIdxL0*. + +The inverse macroblock scanning process as specified in clause 6.4.1 is invoked with CurrMbAddr as the input and the output is assigned to ( x1, y1 ). + +The inverse macroblock partition scanning process specified in clause 6.4.2.1 is invoked with mbPartIdx as the input and the output assigned to ( dx1, dy1 ). + +The reference index *refIdxL0* for a VSP skipped macroblock is derived as the inter-view picture that appears first in RefPicList0. + +If TextureFirstFlag is equal to 0, the variable refViewId is set equal to the view\_id of the inter-view picture *refIdxL0*. Otherwise (TextureFirstFlag is equal to 1) the variable refViewId is set to 0. + +The variable shiftedX is set to ( TextureFirstFlag ? ( DvMBX >> 2 ) : 0 ). + +The depth-based disparity value derivation process in clause I.8.2.1.1 is invoked with depthPic equal to DepthCurrPic, textureX equal to x1 + dx1 + shiftedX, textureY equal to y1 + dy1, tBlWidth equal to 8, tBlHeight equal to 8, srcViewId equal to view\_id and refViewId equal to refViewId as inputs and the output assigned to *mvL0*[ 0 ]. + +*mvL0*[ 1 ] is set equal to 0. + +#### I.8.2.1.4 Derivation process for luma motion vectors for B\_Skip, B\_Direct\_16x16, and B\_Direct\_8x8 + +Inputs to this process are current macroblock partition index mbPartIdx and subMbPartIdx. + +Outputs of this process are the reference indices *refIdxL0*, *refIdxL1*, the motion vectors *mvL0* and *mvL1*, the motion vector count variable subMvCnt, and the prediction list utilization flags, predFlagL0 and predFlagL1. + +For the derivation of output, the following ordered steps are specified: + +1. Let the variable currSubMbType be set equal to sub\_mb\_type[ mbPartIdx ]. + +2. The process specified in clause I.8.2.1.5 is invoked with mbPartIdx set equal to 0, subMbPartIdx set equal to 0, currSubMbType and listSuffixFlag set equal to 0 as input and the output is assigned to the motion vector mvL0 and the reference index refIdxL0. +3. The process specified in clause I.8.2.1.5 is invoked with mbPartIdx set equal to 0, subMbPartIdx set equal to 0, currSubMbType and listSuffixFlag set equal to 1 as input and the output is assigned to the motion vector mvL1 and the reference index refIdxL1. +4. When both reference indices refIdxL0 and refIdxL1 are equal to -1, the following applies: + - The reference index refIdxL0 is set equal to 0. + - The derivation process for luma motion vector prediction in clause I.8.2.1.7 is invoked with mbPartIdx set equal to 0, subMbPartIdx set equal to 0, refIdxLX (with X being 0 or 1), and currSubMbType as the inputs and the output being mvLX. + +#### I.8.2.1.5 Derivation process for the motion vector in inter-view reference + +Inputs to this process are mbPartIdx, subMbPartIdx, and listSuffixFlag. + +Outputs of this process are the motion vector mvCorrespond and the reference index refIdxCorrespond. + +Inter-view reference picture InterViewPic and an offset vector dV are derived as follows: + +- If TextureFirstFlag is equal to 0, the following ordered steps apply: + - The inverse macroblock scanning process as specified in clause 6.4.1 is invoked with CurrMbAddr as the input and the output is assigned to ( x1, y1 ). + - The inverse macroblock partition scanning process specified in clause 6.4.2.1 is invoked with mbPartIdx as the input and the output assigned to ( dx1, dy1 ). + - The inverse sub-macroblock partition scanning process specified in clause I.6.1 is invoked with mbPartIdx and subMbPartIdx as the input and the output assigned to ( dx2, dy2 ). + - The following applies to derive an inter-view reference picture or inter-view only reference picture InterViewPic and to set the variable interViewAvailable: + +``` + +interViewAvailable = 0 +for( cIdx = 0; cIdx <= num_ref_idx_l0_active_minus1 && !interViewAvailable; cIdx++ ) + if( view order index of RefPicList0[ cIdx ] is not equal to view_idx ) { + InterViewPic = RefPicList0[ cIdx ] + interViewAvailable = 1 + } + +``` + +(I-41) + +- When interViewAvailable is equal to 1, the depth-based disparity value derivation process in clause I.8.2.1.1 is invoked with depthPic equal to DepthCurrPic, textureX equal to x1 + dx1 + dx2, textureY equal to y1 + dy1 + dy2, tBIWidth equal to the width the sub-macroblock partition CurrMbAddr\mbPartIdx\subMbPartIdx, tBIHeight equal to the height the sub-macroblock partition CurrMbAddr\mbPartIdx\subMbPartIdx, srcViewId equal to view\_id and refViewId equal to the view\_id of InterViewPic as inputs and the output assigned to dV[ 0 ] and dV[ 1 ] is set to 0. +- Otherwise (TextureFirstFlag is equal to 1), the following ordered steps apply: + - dV is set to (DvMBX, 0) and interViewAvailable is set to InterViewRefAvailable. + - When interViewAvailable is equal to 1, InterViewPic is set to be the texture view component of the base view. + +The refIdxCorrespond and mvCorrespond are set as follows: + +- If interViewAvailable is equal to 0, refIdxCorrespond is set to -1, and mvCorrespond[ 0 ] and mvCorrespond[ 1 ] are both set to 0. +- Otherwise, the following step applies in order. + - The variable xCorrespond is set equal to x1 + 7 + ( dV[ 0 ] >> 2 ), and the variable yCorrespond is set equal to y1 + 7 + ( dV[ 1 ] >> 2 ). + - The variable mbAddrCorrespond is set equal to ( ( CurrMbAddr / PicWidthInMbs ) + ( dV[ 1 ] >> 6 ) ) \* PicWidthInMbs + ( CurrMbAddr % PicWidthInMbs ) + ( dV[ 0 ] >> 6 ). + +- The variable xRelative is set equal to $xCorrespond - ( ( xCorrespond \gg 4 ) \ll 4 )$ , and the variable yRelative is set equal to $yCorrespond - ( ( yCorrespond \gg 4 ) \ll 4 )$ . +- Set mbTypeCorrespond to the syntax element mb\_type of the macroblock with address mbAddrCorrespond inside the picture InterViewPic. When mbTypeCorrespond is equal to P\_8x8, P\_8x8ref0, or B\_8x8, subMbTypeCorrespond is set to be the syntax element sub\_mb\_type of the macroblock with address mbAddrCorrespond inside the picture InterViewPic. +- Set mbPartIdxCorrespond to the macroblock partition index of the corresponding partition and subMbPartIdxCorrespond to the sub-macroblock partition index of the corresponding sub-macroblock partition. The derivation process for macroblock and sub-macroblock partition indices as specified in clause 6.4.13.4 is invoked with the luma location equal to ( xRelative, yRelative ), the macroblock type equal to mbTypeCorrespond, and when mbTypeCorrespond is equal to P\_8x8, P\_8x8ref0, or B\_8x8, the list of sub-macroblock types subMbTypeCorrespond as the inputs and the outputs are the macroblock partition index mbPartIdxCorrespond and the sub-macroblock partition index subMbPartIdxCorrespond. +- The motion vector mvCorrespond and the reference index refIdxCorrespond are derived as follows: + - If the macroblock mbAddrCorrespond is coded as Intra prediction mode, both components of mvCorrespond are set equal to 0 and refIdxCorrespond is set equal to -1. + - Otherwise (the macroblock mbAddrCorrespond is not coded as Intra prediction mode), the prediction utilization flags predFlagLXCorrespond is set equal to PredFlagLX[ mbPartIdxCorrespond ], the prediction utilization flag of the macroblock partition mbAddrCorrespond\mbPartIdxCorrespond of the picture InterViewPic. In addition, the following applies. + - When predFlagLXCorrespond is equal to 1 and RefIdxLX[ mbPartIdxCorrespond ] is less than or equal to num\_ref\_idx\_lX\_active\_minus1, the mvCorrespond and the reference index refIdxCorrespond are set equal to MvLX[ mbPartIdxCorrespond ][ subMbPartIdxCorrespond ] and RefIdxLX[ mbPartIdxCorrespond ], respectively, which are the motion vector mvLX and the reference index refIdxLX that have been assigned to the (sub-)macroblock partition mbAddrCorrespond\mbPartIdxCorrespond\subMbPartIdxCorrespond inside the picture InterViewPic. + +#### 1.8.2.1.6 Derivation process for luma motion vectors for VSP skipped/direct macroblocks in B slices + +Inputs to this process are current macroblock partition index mbPartIdx. + +Outputs of this process are the motion vector mvL0, mvL1 and the reference index refIdxL0, refIdxL1. + +The inverse macroblock scanning process as specified in clause 6.4.1 is invoked with CurrMbAddr as the input and the output is assigned to ( x1, y1 ). + +The inverse macroblock partition scanning process specified in clause 6.4.2.1 is invoked with mbPartIdx as the input and the output assigned to ( dx1, dy1 ). + +The reference index refIdxLX for a VSP skipped/direct macroblock is derived as the inter-view reference component that appears first in the reference picture list X, with X being replaced by 0 or 1. When there is no inter-view picture in the reference picture list X, refIdxLX is set equal to 0. + +The variable refViewIdx is set equal to the view\_id of the inter-view reference component refIdxLX if TextureFirstFlag is equal to 0 and set equal to 0 otherwise. + +The variable shiftedX is set to $( \text{TextureFirstFlag} ? ( \text{DvMBX} \gg 2 ) : 0 )$ . + +The motion vector mvLX, with X being replaced by 0 or 1, is derived as follows: + +- The depth-based disparity value derivation process in clause 1.8.2.1.1 is invoked with depthPic equal to DepthCurrPic, textureX equal to $x1 + dx1 + \text{shiftedX}$ , textureY equal to $y1 + dy1$ , tBIWidth equal to the width the macroblock partition mbPartIdx, tBIHeight equal to the height the macroblock partition mbPartIdx, srcViewId equal to view\_id and refViewId equal to the refViewIdx as inputs and the output assigned to mvLX[ 0 ]. +- mvLX[ 1 ] is set equal to 0. + +#### 1.8.2.1.7 Derivation process for luma motion vector prediction + +Inputs to this process are: + +- the macroblock partition index mbPartIdx, +- the sub-macroblock partition index subMbPartIdx, + +- the reference index of the current partition refIdxLX (with X being 0 or 1), +- the variable currSubMbType. + +Output of this process is the prediction mvpLX of the motion vector mvLX (with X being 0 or 1). + +The specifications of clause 8.4.1.3 apply with the following changes. + +- The following additional sentence is applied + - If refIdxLX is not equal to refIdxLXN for any N = A, B, or C and X equal to 0 or 1, the following applies: + +``` + +mbAddrN\mbPartIdxN\subMbPartIdxN is marked as not available +refIdxLXN = -1 +mvLXN[ 0 ] = 0 +mvLXN[ 1 ] = 0 + +``` + +(I-42) + +after the following paragraph in clause 8.4.1.3: + +- The derivation process for the neighbouring blocks for motion data in clause 8.4.1.3.2 is invoked with mbPartIdx, subMbPartIdx, currSubMbType, and listSuffixFlag = X (with X being 0 or 1 for refIdxLX being refIdxL0 or refIdxL1, respectively) as the input and with mbAddrN\mbPartIdxN\subMbPartIdxN, reference indices refIdxLXN and the motion vectors mvLXN with N being replaced by A, B, or C as the output +- The following additional sentence is applied + - Otherwise, if refIdxLX is a reference index to an inter-view reference component or an inter-view only reference component, the depth-based derivation process for median luma motion vector prediction in clause I.8.2.1.7.1 is invoked with mbAddrN\mbPartIdxN\subMbPartIdxN, mvLXN, refIdxLXN with N being replaced by A, B, or C, and refIdxLX as the inputs and the output is assigned to the motion vector predictor mvpLX. + - Otherwise, if refIdxLX is a reference index to a reference picture which is not an inter-view reference component or an inter-view only reference component, the depth-based derivation process for median luma temporal motion vector prediction in clause I.8.2.1.7.2 is invoked with mbAddrN\mbPartIdxN\subMbPartIdxN, mvLXN, refIdxLXN with N being replaced by A, B, or C, and refIdxLX as the inputs and the output is assigned to the motion vector predictor mvpLX. + +after the following paragraph in clause 8.4.1.3 + +- Otherwise, if MbPartWidth( mb\_type ) is equal to 8, MbPartHeight( mb\_type ) is equal to 16, mbPartIdx is equal to 1, and refIdxLXC is equal to refIdxLX, the motion vector predictor mvpLX is set equal to mvLXC. + +#### I.8.2.1.7.1 Depth-based derivation process for median luma motion vector prediction + +Inputs to this process are: + +- the neighbouring partitions mbAddrN\mbPartIdxN\subMbPartIdxN (with N being replaced by A, B, or C), +- the motion vectors mvLXN (with N being replaced by A, B, or C) of the neighbouring partitions, +- the reference indices refIdxLXN (with N being replaced by A, B, or C) of the neighbouring partitions,, +- the reference index refIdxLX of the current partition. + +Output of this process is the motion vector prediction mvpLX. + +When either partition mbAddrN\mbPartIdxN\subMbPartIdxN is not available or refIdxLXN is not equal to refIdxLX, mvLXN is derived as specified by the following: + +- If TextureFirstFlag is equal to 0, the following steps apply in order: + 1. The inverse macroblock scanning process as specified in clause 6.4.1 is invoked with CurrMbAddr as the input and the output is assigned to ( x1, y1 ). + 2. The inverse macroblock partition scanning process specified in clause 6.4.2.1 is invoked with mbPartIdx as the input and the output assigned to ( dx1, dy1 ). + 3. The inverse sub-macroblock partition scanning process specified in clause I.6.1 is invoked with mbPartIdx and subMbPartIdx as the input and the output assigned to ( dx2, dy2 ). + +4. The modification process of inter-view motion vector in median luma motion vector prediction as specified in clause I.8.2.1.7.1.1 is invoked with depthPic being equal to DepthRefPicList0[ refIdxL0 ], mbx1 being equal to x1 and mby1 being equal to y1 as inputs and the output is assigned to the motion vector mvLXN. + - Otherwise (TextureFirstFlag is equal to 1), mvLXN is set equal to ( DvMBX , 0 ). + +Each component of the motion vector prediction mvpLX is given by the median of the corresponding vector components of the motion vector mvLXA, mvLXB, and mvLXC: + +$$\text{mvpLX}[ 0 ] = \text{Median}( \text{mvLXA}[ 0 ], \text{mvLXB}[ 0 ], \text{mvLXC}[ 0 ] ) \quad (\text{I-43})$$ + +$$\text{mvpLX}[ 1 ] = \text{Median}( \text{mvLXA}[ 1 ], \text{mvLXB}[ 1 ], \text{mvLXC}[ 1 ] ) \quad (\text{I-44})$$ + +#### I.8.2.1.7.1.1 Modification process for inter view motion vector in median luma motion vector prediction + +Inputs to this process are: + +- depth reference view component depthPic, +- the location of a top-left sample ( mbx1, mby1 ) of the current macroblock. + +Output of this process is the motion vector mv. + +Let refViewId be the view\_id value of depthPic. + +The variable mv is derived as follows: + +- The depth-based disparity value derivation process in clause I.8.2.1.1 is invoked with depthPic equal to DepthCurrPic, textureX equal to mbx1, textureY equal to mby1, tBlWidth equal to 16, tBlHeight equal to 16, srcViewId equal to view\_id and refViewId equal to the refViewId as inputs and the output assigned to mv[ 0 ]. +- mv[ 1 ] is set equal to 0. + +#### I.8.2.1.7.2 Depth-based derivation process for median luma temporal motion vector prediction + +Inputs to this process are: + +- the neighbouring partitions mbAddrN\mbPartIdxN\subMbPartIdxN (with N being replaced by A, B, or C), +- the motion vectors mvLXN (with N being replaced by A, B, or C) of the neighbouring partitions, +- the reference indices refIdxLXN (with N being replaced by A, B, or C) of the neighbouring partitions, +- the reference index refIdxLX of the current partition. + +Output of this process is the motion vector prediction mvpLX. + +When either partition mbAddrN\mbPartIdxN\subMbPartIdxN is not available or refIdxLXN is not equal to refIdxLX, mvLXN is derived as specified by the following ordered steps: + +1. When TextureFirstFlag is equal to 0, the inverse macroblock scanning process as specified in clause 6.4.1 is invoked with CurrMbAddr as the input and the output is assigned to ( x1, y1 ). +2. When TextureFirstFlag is equal to 0, the inverse macroblock partition scanning process specified in clause 6.4.2.1 is invoked with mbPartIdx as the input and the output assigned to ( dx1, dy1 ). +3. When TextureFirstFlag is equal to 0, the inverse sub-macroblock partition scanning process specified in clause I.6.1 is invoked with mbPartIdx and subMbPartIdx as the input and the output assigned to ( dx2, dy2 ). +4. When TextureFirstFlag is equal to 0, the process specified in clause I.8.2.1.7.2.1 is invoked with depthPic set to DepthCurrPic, mbx1 set to x1, mby1 set to y1 and listSuffixFlag as input and InterViewPic, an offset vector dV and a variable interViewAvailable as outputs. +5. When TextureFirstFlag is equal to 1, dV is set equal to ( DvMBX , 0 ) and a variable interViewAvailable is set equal to InterViewRefAvailable. +6. The refIdxCorrespond and mvCorrespond are set as follows: + - If interViewAvailable is equal to 0, refIdxCorrespond is set to -1, and mvCorrespond[ 0 ] and mvCorrespond[ 1 ] are both set to 0. + - Otherwise, the following steps apply in order. + - The variable luma4x4BlkIdx is set equal to ( 4 \* mbPartIdx + subMbPartIdx ). + +- The inverse 4x4 luma block scanning process as specified in clause 6.4.3 is invoked with luma4x4BlkIdx as the input and ( x, y ) as the output. In addition, ( xCorrespond, yCorrespond ) is set equal to ( x + ( dV[ 0 ] >> 4 ), y + ( dV[ 1 ] >> 4 ) ) and mbAddrCorrespond is set equal to ( ( CurrMbAddr / PicWidthInMbs ) + ( dV[ 1 ] >> 6 ) ) \* PicWidthInMbs + ( CurrMbAddr % PicWidthInMbs ) + ( dV[ 0 ] >> 6 ). +- Set mbTypeCorrespond to the syntax element mb\_type of the macroblock with address mbAddrCorrespond inside the picture InterViewPic. When mbTypeCorrespond is equal to P\_8x8, P\_8x8ref0, or B\_8x8, subMbTypeCorrespond is set to be the syntax element sub\_mb\_type of the macroblock with address mbAddrCorrespond inside the picture InterViewPic. +- Set mbPartIdxCorrespond to the macroblock partition index of the corresponding partition and subMbPartIdxCorrespond to the sub-macroblock partition index of the corresponding sub-macroblock partition. The derivation process for macroblock and sub-macroblock partition indices as specified in clause 6.4.13.4 is invoked with the luma location equal to ( xCorrespond, yCorrespond ), the macroblock type equal to mbTypeCorrespond, and when mbTypeCorrespond is equal to P\_8x8, P\_8x8ref0, or B\_8x8, the list of sub-macroblock types subMbTypeCorrespond as the inputs and the outputs are the macroblock partition index mbPartIdxCorrespond and the sub-macroblock partition index subMbPartIdxCorrespond. +- The motion vector mvCorrespond and the reference index refIdxCorrespond are derived as follows: + - If the macroblock mbAddrCorrespond is coded as Intra prediction mode, both components of mvCorrespond are set equal to 0 and refIdxCorrespond is set equal to -1. + - Otherwise (the macroblock mbAddrCorrespond is not coded as Intra prediction mode), the prediction utilization flags predFlagLXCorrespond is set equal to PredFlagLX[ mbPartIdxCorrespond ], the prediction utilization flag of the macroblock partition mbAddrCorrespond\mbPartIdxCorrespond of the picture InterViewPic. In addition, the following applies. + - When predFlagLXCorrespond is equal to 1, the mvCorrespond and the reference index refIdxCorrespond are set equal to MvLX[ mbPartIdxCorrespond ][ subMbPartIdxCorrespond ] and RefIdxLX[ mbPartIdxCorrespond ], respectively, which are the motion vector mvLX and the reference index refIdxLX that have been assigned to the (sub-)macroblock partition mbAddrCorrespond\mbPartIdxCorrespond\subMbPartIdxCorrespond inside the picture InterViewPic. + +7. The motion vectors mvLXN is derived as follows: + +- If refIdxCorrespond is equal to refIdxLX, the following applies: + +$$\begin{aligned} \text{mvLXN}[ 0 ] &= \text{mvCorrespond}[ 0 ] \\ \text{mvLXN}[ 1 ] &= \text{mvCorrespond}[ 1 ] \end{aligned} \quad (\text{I-45})$$ + +- Otherwise, the following applies: + +$$\begin{aligned} \text{mvLXN}[ 0 ] &= 0 \\ \text{mvLXN}[ 1 ] &= 0 \end{aligned}$$ + +8. The following applies for the derivation of mvpLX[ 0 ] and mvpLX[ 1 ]: + +$$\text{mvpLX}[ 0 ] = \text{Median}( \text{mvLXA}[ 0 ], \text{mvLXB}[ 0 ], \text{mvLXC}[ 0 ] ) \quad (\text{I-46})$$ + +$$\text{mvpLX}[ 1 ] = \text{Median}( \text{mvLXA}[ 1 ], \text{mvLXB}[ 1 ], \text{mvLXC}[ 1 ] ) \quad (\text{I-47})$$ + +#### I.8.2.1.7.2.1 Derivation process for the disparity vector and the inter-view reference + +Inputs to this process are depth reference view component depthPic, the location of a top-left sample ( mbx1, mby1 ) of the current macroblock and the listSuffixFlag. + +Outputs of this process are a picture InterViewPic, an offset vector dV and a variable interViewAvailable. + +The variable interViewAvailable is set equal to 0. + +The following applies to derive an inter-view reference picture or inter-view only reference picture, InterViewPic, with X set to 1 when listSuffixFlag is 1 or 0 otherwise: + +``` + +for( cIdx = 0; cIdx < num_ref_idx_l0_active_minus1 + 1 && !interViewAvailable; cIdx ++ ) + if ( view order index of RefPicList0[ cIdx ] is not equal to view_idx ) { + InterViewPic = RefPicList0[ cIdx ] + interViewAvailable = 1 + } +} + +``` + +(I-48) + +When interViewAvailable is equal to 1, the depth-based disparity value derivation process in clause I.8.2.1.1 is invoked with depthPic equal to DepthCurrPic, textureX equal to mbx1, textureY equal to mby1, tBIWidth equal to 16, tBIHeight equal to 16, srcViewId equal to view\_id and refViewId equal to view\_id of InterViewPic as inputs and the output assigned to dV. + +#### I.8.2.1.8 Macroblock-level neighbouring block based disparity vector derivation process + +Input to this process is a macroblock currMB. + +Let the variable availableDvFlag equal to 0, ( xP, yP ) be equal to the output of the clause 6.4.2.1 (the location of upper-left luma sample for currMB partition 0). + +The variables dvMBCur and DvMBX are derived as specified by the following ordered steps: + +1. For each X from 0 to 1, the following steps apply in order. + - When availableDvFlag is equal to 0 and RefPicListY[ 0 ] is available (with Y equal to 1-X), the following applies: + - Set refPicListCol0 to the reference picture list 0 of RefPicListY[ 0 ]. + - mvColL0 and refIdxColL0 are set to the motion vector mvL0 and reference index refIdxL0 that have been assigned to the block covering ( xP + 16, yP + 16 ) in picture RefPicListY[ 0 ], respectively. + - When refPicListCol0[ refIdxColL0 ] is available, the view order index of refPicListCol0[ refIdxColL0 ] is unequal to the view\_idx, and mvColL0[ 0 ] is unequal to 0, dvMBCur is set equal to mvColL0[ 0 ] and availableDvFlag is set to 1. +2. The process in clause 6.4.11.7 is invoked with mbPartIdx equal to 0, currSubMbType equal to P\_L0\_16x16, and subMbPartIdx equal to 0 as input and the output is assigned to mbAddrN\mbPartIdxN\subMbPartIdxN with N being replaced by A, B, C, or D. For each N being A, B, C and D, its reference index refIdxL0N and motion vector mvL0N are set equal to RefIdxL0[ mbPartIdxN ] and MvL0[ mbPartIdxN ][ subMbPartIdxN ], respectively, which are the reference index refIdxL0 and motion vector mvL0 that have been assigned to the (sub-)macroblock partition mbAddrN\mbPartIdxN\subMbPartIdxN, and when availableDvFlag is equal to 0, the following applies: + - When RefPicList0[ refIdxL0N ] is available and the view order index of RefPicList0[ refIdxL0N ] is unequal to the view\_idx, and mvL0N[ 0 ] is unequal to 0, dvMBCur is set to mvL0N[ 0 ] and availableDvFlag is set to 1. +3. When availableDvFlag is equal to 0, dvMBCur is set to DvMBX. +4. When seq\_view\_synthesis\_flag is equal to 1, the following steps apply in order. + - The variables currIndex and refIndex are derived by: + +``` + +currIndex = ViewIdTo3DVAcquisitionParamIndex( view_id of the current view ) +refIndex = ViewIdTo3DVAcquisitionParamIndex( view_id of DepthCurrPic ) + +``` + +(I-49) + - The depth-based disparity value derivation process in clause I.8.2.1.1 is invoked with depthPic equal to DepthCurrPic, ( textureX , textureY ) equal to ( xP + ( dvMBCur >> 2 ) , yP ), tBIWidth equal to 16, tBIHeight equal to 16, srcViewId equal to currIndex and refViewId equal to refIndex and the output assigned to dvMBCur. +5. DvMBX is set equal to dvMBCur. + +#### I.8.2.2 Derivation of prediction weights in depth-range-based weighted prediction + +The process specified in this clause is invoked when either or both of the following conditions apply: + +- nal\_unit\_type is equal to 21 and depth\_weighted\_pred\_flag is equal to 1 and ( slice\_type % 5 ) is equal to 0 or 3, +- depth\_weighted\_bipred\_flag is equal to 1 and ( slice\_type % 5 ) is equal to 1 + +Inputs to this process are: + +- the reference indices refIdxL0 and refIdxL1, +- the prediction utilization flags predFlagL0 and predFlagL1. + +Outputs of this process are variables for weighted prediction logWDC, w0C, w1C, o0C, and o1C with C being replaced by L (luma). + +The variables currIndex, refIndex, dpsIdCurr and dpsIdRef are derived as follows: + +$$\text{logWD}_C = 5 \tag{I-50}$$ + +$$\text{currIndex} = \text{ViewIdTo3DVAcquisitionParamIndex}(\text{view\_id of the current view}) \tag{I-51}$$ + +$$\text{refIndex} = \text{ViewIdTo3DVAcquisitionParamIndex}(\text{view\_id of the view of the reference picture}) \tag{I-52}$$ + +$$\text{dpsIdCurr} = \text{dps\_id of the current picture} \tag{I-53}$$ + +$$\text{dpsIdRef} = \text{dps\_id of the reference picture} \tag{I-54}$$ + +When predFlagL0 is equal to 1, the following is applied. + +- The derivation process for a single prediction weight in depth-range-based weighted prediction specified in clause I.8.2.2.1 is invoked with zNearCurr equal to ZNear[ dpsIdCurr, currIndex ], zFarCurr equal to ZFar[ dpsIdCurr, currIndex ], zNearRef equal to ZNear[ dpsIdRef, refIndex ], zFarRef equal to ZFar[ dpsIdRef, refIndex ], and reference list identifier X equal to 0. + +When predFlagL1 is equal to 1 and depth\_weighted\_bipred\_flag is equal to 1, the following is applied. + +- The derivation process for a single prediction weight in depth-range-based weighted prediction specified in clause I.8.2.2.1 is invoked with zNearCurr equal to ZNear[ dpsIdCurr, currIndex ], zFarCurr equal to ZFar[ dpsIdCurr, currIndex ], zNearRef equal to ZNear[ dpsIdRef, refIndex ], zFarRef equal to ZFar[ dpsIdRef, refIndex ], and reference list identifier X equal to 1. + +#### I.8.2.2.1 Derivation of weight and offset parameters + +Inputs of this process are variables zNearCurr, zNearRef, zFarCurr, and zFarRef and the reference list identifier X with X being replaced by 0 or 1. + +Outputs of this process are variables wXC and oXC for weighted prediction. + +The variable wXC with X being replaced by 0 or 1 and C being replaced by L is calculated by the following steps. + +1. scaleW is set equal to 8. +2. Calculate variable wFactorA as follows: + +$$\begin{aligned} k &= \text{zFarRef} - \text{zNearRef} \\ m &= \text{zFarRef} \\ x &= (k + (m \gg 1)) / m \\ \text{signVal} &= ((k - x * m) < 0) ? -1 : 1 \\ \text{wFactorA} &= (x \ll \text{scaleW}) \\ \text{wFactorA} &+= (((k - x * m) \ll \text{scaleW}) + \text{signVal} * (m \gg 1)) / m \end{aligned} \tag{I-55}$$ + +3. Calculate variable wFactorB as follows: + +$$\begin{aligned} k &= \text{zFarCurr} \\ m &= \text{zFarCurr} - \text{zNearCurr} \\ x &= (k + (m \gg 1)) / m \\ \text{signVal} &= ((k - x * m) < 0) ? -1 : 1 \\ \text{wFactorB} &= (x \ll \text{scaleW}) \\ \text{wFactorB} &+= (((k - x * m) \ll \text{scaleW}) + \text{signVal} * (m \gg 1)) / m \end{aligned} \tag{I-56}$$ + +4. Calculate variable wFactorC as follows: + +$$\begin{aligned} k &= \text{zNearCurr} \\ m &= \text{zNearRef} \\ x &= (k + (m \gg 1)) / m \\ \text{signVal} &= ((k - x * m) < 0) ? -1 : 1 \\ \text{wFactorC} &= (x \ll \text{scaleW}) \\ \text{wFactorC} &+= (((k - x * m) \ll \text{scaleW}) + \text{signVal} * (m \gg 1)) / m \end{aligned} \tag{I-57}$$ + +5. Calculate variable wXC: + +$$\begin{aligned} +w_{XC} &= ( wFactorA * wFactorB * wFactorC + ( 1 \ll ( scaleW * 3 - \log WD_C - 1 ) ) ) \\ +&\quad \gg ( scaleW * 3 - \log WD_C ) \\ +w_{XC} &= \text{Clip}( -127, 128, w_{XC} ) +\end{aligned} \tag{I-58}$$ + +The variable $o_{XC}$ is calculated by the following steps: + +1. $scaleO$ is set equal to 8. +2. Calculate variable $oFactorA$ as follows: + +$$oFactorA = ( ( zNearCurr \ll ( scaleO ) ) + ( zFarRef \gg 1 ) ) / zFarRef \tag{I-59}$$ + +3. Calculate variable $oFactorB$ : + +$$\begin{aligned} +k &= zFarCurr - zFarRef \\ +m &= zFarCurr - zNearCurr \\ +signVal &= ( k < 0 ) ? -1 : 1 \\ +x &= ( k + signVal * ( m \gg 1 ) ) / m \\ +signVal &= ( ( k - x * m ) < 0 ) ? -1 : 1 \\ +oFactorB &= ( x \ll scaleO ) \\ +oFactorB &+= ( ( ( k - x * m ) \ll scaleO ) + signVal * ( m \gg 1 ) ) / m +\end{aligned} \tag{I-60}$$ + +4. Calculate variable $o_{XC}$ : + +$$\begin{aligned} +o_{XC} &= ( oFactorA * oFactorB + ( 1 \ll ( scaleO * 2 - 8 - 1 ) ) ) \gg ( scaleO * 2 - 8 ) \\ +o_{XC} &= \text{Clip}( -127, 128, o_{XC} ) +\end{aligned} \tag{I-61}$$ + +### I.8.2.3 Derivation process for motion vectors and reference indices for adaptive luminance compensation + +Inputs to this process are: + +- a macroblock partition $mbPartIdx$ , +- a sub-macroblock partition $subMbPartIdx$ . + +Outputs of this process are: + +- luma motion vectors $mvL0$ and $mvL1$ and when $ChromaArrayType$ is not equal to 0, the chroma motion vectors $mvCL0$ and $mvCL1$ , +- reference indices $refIdxL0$ and $refIdxL1$ , +- prediction list utilization flags $predFlagL0$ and $predFlagL1$ , +- a motion vector count variable $subMvCnt$ . + +The motion vector count variable $subMvCnt$ is set equal to 1. + +Set $interViewAvailable$ equal to 0. + +The reference index $refIdxL0$ for a skipped macroblock is derived as: + +$$\begin{aligned} +&\text{for}( cIdx = 0; cIdx \leq \text{num\_ref\_idx\_l0\_active\_minus1} \ \&\& \ !interViewAvailable; cIdx ++ ) \\ +&\quad \text{if} ( \text{RefPicList0}[ cIdx ] \text{ and the current view component have different values of view order index} ) \{ \\ +&\quad \quad refIdxL0 = cIdx \\ +&\quad \quad interViewAvailable = 1 \\ +&\quad \} +\end{aligned} \tag{I-62}$$ + +If $dmvp\_flag$ is equal to 1 and $mb\_alc\_skip\_flag$ is equal to 1, clause I.8.2.1.7 is invoked and $mvL0$ is set equal to $mvpL0$ , the output of clause I.8.2.1.7. + +Otherwise, if $dmvp\_flag$ is equal to 1 and $mb\_alc\_flag$ is equal to 1, clause I.8.2.1 is invoked for derivation of $mvL0$ . + +Otherwise, clause 8.4.1 is invoked and $mvL0$ is set equal to $mvpL0$ , the output of clause 8.4.1. + +### I.8.2.4 Derivation process for prediction weights in adaptive luminance compensation + +Inputs to this process are: + +- reference index $refIdxL0$ + +- the luma sample array of the selected reference picture refPicL0L. +- the current partition given by its partition index mbPartIdx and its sub-macroblock partition index subMbPartIdx +- Luma4x4BlkIdx +- the width and height partWidth, partHeight of this partition in luma-sample units +- a luma motion vector mvL0 given in quarter-luma-sample units +- array cSL containing already constructed luma samples prior to deblocking filter process. + +Outputs of this process are: + +- variables for weighted prediction of the current partition logWDC, w0C, w1C, o0C, o1C, with C being replaced by L and, when ChromaArrayType is not equal to 0, Cb and Cr. + +The variables W1C, O1C are derived as follows for C equal to L, Cb or Cr: + +$$\text{logWDC} = 0 \tag{I-63}$$ + +$$\text{w1C} = 0 \tag{I-64}$$ + +$$\text{o1C} = 0 \tag{I-65}$$ + +The variables W0C, O0C are derived as follows for C if equal to Cb or Cr: + +$$\text{logWDC} = 0 \tag{I-66}$$ + +$$\text{w0C} = 1 \tag{I-67}$$ + +$$\text{o0C} = 0 \tag{I-68}$$ + +When C is equal to L for luma samples, clauses I.8.2.4.1 through I.8.2.4.5 are invoked sequentially to derive LogWDL, w0C, and o0C. + +#### I.8.2.4.1 Defining of coordinates and sizes of a luma block to be predicted + +Let ( xM, yM ) be equal to the output of clause 6.4.1 (the location of upper-left luma sample for the current macroblock with address mbAddr relative to the upper-left sample of the picture). + +Let ( xP, yP ) be equal to the output of clause 6.4.2.1 (the location of upper-left luma sample for the macroblock partition mbPartIdx). + +Let ( xB, yB ) be equal to the output of clause I.6.1 (the location of upper-left luma sample for the 4x4 luma block defined by Luma4x4BlkIdx that can be 0...15) relative to the top-left sample of the sub-macroblock. + +The variables xT, yT, xBlockWidth, yBlockHeight are set as follows: + +- xT is set equal to xM + xP; +- yT is set equal to yM + yP; +- xBlockWidth is set equal to MbPartWidth( mb\_type ); +- yBlockHeight is set equal to MbPartHeight( mb\_type ); + +If one or more of the following conditions are true, W0C is set equal to 1 and logWDC is set equal to 15. + +- ( mvL0[ 0 ] + ( ( xT - 1 ) << 2 ) ) is smaller than 0; +- ( mvL0[ 1 ] + ( ( yT - 1 ) << 2 ) ) is smaller than 0; +- ( mvL0[ 0 ] + ( ( xT + xBlockWidth ) << 2 ) ) is greater than or equal to ( PicWidthInSamplesL << 2 ); +- ( mvL0[ 1 ] + ( ( yT + yBlockHeight ) << 2 ) ) is greater than or equal to ( PicHeightInSamplesL << 2 ). + +Otherwise LRef, URef, LRec, URec sample values are derived as it is specified in clauses I.8.2.4.2 and I.8.2.4.3 followed by calculation of variables NeighbourRefSum, NeighbourSum and W0L, O0L specified in clauses I.8.2.4.4 and I.8.2.4.5 correspondently. + +#### I.8.2.4.2 Deriving of left and up reference samples of the current block + +LRec and URec blocks belong to an (PicWidthInSamplesL)x(PicHeightInSamplesL) array cSL containing constructed luma samples prior to the deblocking filter process. + +Each luma sample LRec[ 0, yL ] for 0 <= yL < yBlockHeight is specified as follows: + +$$LRec[ 0, y_L ] = cSL[ x_T - 1, y_T + y_L ] \quad (I-69)$$ + +Each luma sample $URec[ x_L, 0 ]$ for $0 \leq x_L < xBlockSize$ is specified as follows: + +$$URec[ x_L, y_L ] = cSL[ x_T + x_L, y_T - 1 ] \quad (I-70)$$ + +#### I.8.2.4.3 Deriving of left and up reference samples of the reference block + +For each luma sample location $(0, y_L)$ such as: $0 \leq y_L < yBlockSize$ inside $LRef$ block, sample value $LRef[ 0, y_L ]$ is derived by the following ordered steps: + +1. The variables $xIntL$ , $yIntL$ , $xFracL$ , and $yFracL$ are derived by: + +$$xIntL = x_T + ( mvL0[ 0 ] \gg 2 ) - 1 \quad (I-71)$$ + +$$yIntL = y_T + ( mvL0[ 1 ] \gg 2 ) + y_L \quad (I-72)$$ + +$$xFracL = mvL0[ 0 ] \& 3 \quad (I-73)$$ + +$$yFracL = mvL0[ 1 ] \& 3 \quad (I-74)$$ + +2. $LRef[ 0, y_L ]$ sample is derived as an output of the process specified in clause 8.4.2.2.1 with $( xIntL, yIntL )$ , $( xFracL, yFracL )$ and $refPicL0L$ given as input. + +For each luma sample location $( x_L, 0 )$ such as: $0 \leq x_L < xBlockSize$ inside $URef$ block sample value $URef[ x_L, 0 ]$ is derived by the following ordered steps: + +1. The variables $xIntL$ , $yIntL$ , $xFracL$ , and $yFracL$ are derived by: + +$$xIntL = x_T + ( mvL0[ 0 ] \gg 2 ) + x_L \quad (I-75)$$ + +$$yIntL = y_T + ( mvL0[ 1 ] \gg 2 ) - 1 \quad (I-76)$$ + +$$xFracL = mvL0[ 0 ] \& 3 \quad (I-77)$$ + +$$yFracL = mvL0[ 1 ] \& 3 \quad (I-78)$$ + +2. $URef[ x_L, y_L ]$ sample is derived as an output of the process specified in clause 8.4.2.2.1 with $( xIntL, yIntL )$ , $( xFracL, yFracL )$ and $refPicL0L$ given as input. + +#### I.8.2.4.4 Derivation of NeighbourRefSum and NeighbourSum + +Both $NeighbourRefSum$ and $NeighbourSum$ are set equal to 1 and further calculated as follows: + +``` +for( j=0; jZNear | z_near_flag | ZNearSign | ZNearExp | ZNearMantissa | ZNearManLen | +| ZFar | z_far_flag | ZFarSign | ZFarExp | ZFarMantissa | ZFarManLen | + +## I.9 Parsing process + +The specifications in clause 9 apply. Additionally, the following modifications are specified and added. + +### I.9.1 Alternative CABAC parsing process for slice data and macroblock layer in depth extension + +Clause I.9.1.1 specifies the initialization process for the alternative CABAC parsing process for slice data and macroblock layer when nal\_unit\_type is equal to 21 and avc\_3d\_extension\_flag is equal to 1. + +Clause I.9.1.2 specifies the binarization process for the alternative CABAC parsing process for slice data and macroblock layer when nal\_unit\_type is equal to 21 and avc\_3d\_extension\_flag is equal to 1 + +Clause I.9.1.3 specifies the decoding process flow for the alternative CABAC parsing process for slice data and macroblock layer when nal\_unit\_type is equal to 21 and avc\_3d\_extension\_flag is equal to 1. + +#### I.9.1.1 Initialization process + +Outputs of this process are the initialized CABAC context variables indexed by ctxIdx. + +Table I-6 contains the values of the variables n and m used in the initialization of context variables that are assigned to syntax elements mb\_vskip\_flag, and mb\_direct\_type\_flag. Table I-7 contains the values of the variables n and m used in the initialization of context variables that are assigned to syntax element mb\_skip\_run\_type, mb\_alc\_skip\_flag, mb\_alc\_flag and mb\_vsp\_flag. The initialization process for two variables pStateIdx and valMPS is the same as other + +syntax elements, as defined in Equation 9-5. For all other syntax elements in clause 7.3.5 the initialization process of context variables as specified in clause 9.3.1 applies. + +**Table I-5 – Association of ctxIdx and syntax elements in the initialization process** + +| Syntax element | Table | Slice type | | | +|---------------------|-----------|------------|--------------|------------| +| | | I | P | B | +| mb_vsskip_flag | Table I-6 | | 1031..1033 | 1034..1036 | +| mb_direct_type_flag | Table I-6 | | | 1037..1039 | +| mb_skip_run_type | Table I-7 | | | 1040 | +| mb_alc_skip_flag | Table I-7 | | 1041 .. 1043 | | +| mb_alc_flag | Table I-7 | | 1044 .. 1046 | | +| mb_vsp_flag | Table I-7 | | 1047..1049 | 1050..1052 | + +**Table I-6 – Values of variables m and n for ctxIdx from 1031 to 1039** + +| Value of cabac_init_idc | Initialization variables | ctxIdx | | | | | | | | | +|-------------------------|--------------------------|--------|------|------|------|------|------|------|------|------| +| | | 1031 | 1032 | 1033 | 1034 | 1035 | 1036 | 1037 | 1038 | 1039 | +| 0 | m | 23 | 23 | 21 | 18 | 9 | 29 | -46 | -20 | 1 | +| | n | 33 | 2 | 0 | 64 | 43 | 0 | 127 | 104 | 67 | +| 1 | m | 22 | 34 | 16 | 26 | 19 | 40 | -45 | -15 | -4 | +| | n | 25 | 0 | 0 | 34 | 22 | 0 | 127 | 101 | 76 | +| 2 | m | 29 | 25 | 14 | 20 | 20 | 29 | -32 | -22 | -2 | +| | n | 16 | 0 | 0 | 40 | 10 | 0 | 127 | -117 | 74 | + +**Table I-7 – Values of variables m and n for ctxIdx from 1040 to 1052** + +| Initialization variables | ctxIdx | | | | | | | | | | | | | +|--------------------------|--------|------|------|------|------|------|------|------|------|------|------|------|------| +| | 1040 | 1041 | 1042 | 1043 | 1044 | 1045 | 1046 | 1047 | 1048 | 1049 | 1050 | 1051 | 1052 | +| m | 18 | 14 | 14 | 10 | 14 | 14 | 10 | 0 | 0 | 0 | 0 | 0 | 0 | +| n | 64 | 4 | 27 | 52 | 4 | 27 | 52 | 64 | 64 | 64 | 64 | 64 | 64 | + +### I.9.1.2 Binarization process + +Input to this process is a request for a syntax element. + +Output of this process is the binarization of the syntax element, maxBinIdxCtx, ctxIdxOffset, and bypassFlag. + +Associated with each binarization or binarization part of a syntax element is a specific value of the context index offset (ctxIdxOffset) variable and a specific value of the maxBinIdxCtx variable as given in Table I-8. + +The use of the DecodeBypass process and the variable bypassFlag is derived as follows: + +- If no value is assigned to ctxIdxOffset for the corresponding binarization or binarization part in Table I-8 labelled as "na", all bins of the bit strings of the corresponding binarization or of the binarization prefix/suffix part are decoded by invoking the DecodeBypass process as specified in clause 9.3.3.2.3. In such a case, bypassFlag is set equal to 1, where bypassFlag is used to indicate that for parsing the value of the bin from the bitstream the DecodeBypass process is applied. + +- Otherwise, for each possible value of binIdx up to the specified value of maxBinIdxCtx given in Table I-8, a specific value of the variable ctxIdx is further specified in clause 9.3.3. bypassFlag is set equal to 0. + +The possible values of the context index ctxIdx are in the range 1031 to 1052, inclusive. The value assigned to ctxIdxOffset specifies the lower value of the range of ctxIdx assigned to the corresponding binarization or binarization part of a syntax element. + +**Table I-8 – Syntax elements and associated types of binarization, maxBinIdxCtx, and ctxIdxOffset** + +| Syntax element | Type of binarization | maxBinIdxCtx | ctxIdxOffset | +|-------------------------------------|----------------------|--------------|--------------| +| mb_vsskip_flag (P slices only) | FL, cMax=1 | 0 | 1031 | +| mb_vsskip_flag (B slices only) | FL, cMax=1 | 0 | 1034 | +| mb_direct_type_flag (B slices only) | FL, cMax=1 | 0 | 1037 | +| mb_skip_run_type (B slices only) | FL, cMax=1 | 0 | 1040 | +| mb_alc_skip_flag | FL, cMax=1 | 0 | 1041 | +| mb_alc_flag | FL, cMax=1 | 0 | 1044 | +| mb_vsp_flag (P slices only) | FL, cMax=1 | 0 | 1047 | +| mb_vsp_flag (B slices only) | FL, cMax=1 | 0 | 1050 | + +### I.9.1.3 Decoding process flow + +Input to this process is a binarization of the requested syntax element, maxBinIdxCtx, bypassFlag and ctxIdxOffset as specified in clause 9.1.2. + +Output of this process is the value of the syntax element. + +This process specifies how each bit of a bit string is parsed for each syntax element. + +After parsing each bit, the resulting bit string is compared to all bin strings of the binarization of the syntax element and the following applies. + +- If the bit string is equal to one of the bin strings, the corresponding value of the syntax element is the output. +- Otherwise (the bit string is not equal to one of the bin strings), the next bit is parsed. + +While parsing each bin, the variable binIdx is incremented by 1 starting with binIdx being set equal to 0 for the first bin. + +The parsing of each bin is specified by the following two ordered steps: + +1. Given binIdx, maxBinIdxCtx and ctxIdxOffset, ctxIdx is derived as specified in clause I.9.1.3.1. +2. Given ctxIdx, the value of the bin from the bitstream as specified in clause 9.3.3.2 is decoded. + +#### I.9.1.3.1 Derivation process for ctxIdx + +Inputs to this process are binIdx, maxBinIdxCtx and ctxIdxOffset. + +Output of this process is ctxIdx. + +Table I-9 shows the assignment of ctxIdx increments (ctxIdxInc) to binIdx for all ctxIdxOffset values for the syntax mb\_vsskip\_flag, mb\_direct\_type\_flag, mb\_alc\_skip\_flag, mb\_alc\_flag and mb\_vsp\_flag. + +The ctxIdx to be used with a specific binIdx is the sum of ctxIdxOffset and ctxIdxInc, which is found in Table I-9. When more than one value is listed in Table I-9 or 9-39 for a binIdx, the assignment process for ctxIdxInc for that binIdx is further specified in the clauses given in parenthesis of the corresponding table entry. + +All entries in Table I-9 labelled with "na" correspond to values of binIdx that do not occur for the corresponding ctxIdxOffset. + +**Table I-9 – Assignment of ctxIdxInc to binIdx for the ctxIdxOffset values related to the syntax elements mb\_vsskip\_flag, mb\_direct\_type\_flag, mb\_alc\_skip\_flag, mb\_alc\_flag and mb\_vsp\_flag** + +| ctxIdxOffset | binIdx | | +|--------------|-----------------------------|------| +| | 0 | >= 1 | +| 1031 | 0,1,2
(clause I.9.1.3.2) | na | +| 1034 | 0,1,2
(clause I.9.1.3.2) | na | +| 1037 | 0,1,2
(clause I.9.1.3.3) | na | +| 1041 | 0,1,2
(clause I.9.1.3.4) | na | +| 1044 | 0,1,2
(clause I.9.1.3.5) | na | +| 1047 | 0,1,2
(clause I.9.1.3.6) | na | +| 1050 | 0,1,2
(clause I.9.1.3.6) | na | + +#### I.9.1.3.2 Derivation process of ctxIdxInc for the syntax element mb\_vsskip\_flag + +Output of this process is ctxIdxInc. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If mbAddrN is not available or mb\_vsskip\_flag for the macroblock mbAddrN is equal to 1, condTermFlagN is set equal to 0. +- Otherwise (mbAddrN is available and mb\_vsskip\_flag for the macroblock mbAddrN is equal to 0), condTermFlagN is set equal to 1. + +The variable ctxIdxInc is derived by: + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (\text{I-81})$$ + +#### I.9.1.3.3 Derivation process of ctxIdxInc for the syntax element mb\_direct\_type\_flag + +Output of this process is ctxIdxInc. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If any of the following conditions is true, condTermFlagN is set to 0: + - If mbAddrN is not available, + - Both mb\_vsskip\_flag and mb\_direct\_type\_flag for the macroblock mbAddrN is equal to 0 +- Otherwise, condTermFlagN is set equal to 1. + +The variable ctxIdxInc is derived by: + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (\text{I-82})$$ + +#### **I.9.1.3.4 Derivation process of ctxIdxInc for the syntax element mb\_alc\_skip\_flag** + +Output of this process is ctxIdxInc. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If mbAddrN is available and mb\_alc\_skip\_flag or mb\_alc\_flag for the macroblock mbAddrN is equal to 1, condTermFlagN is set equal to 1. +- Otherwise (mbAddrN is not available or mb\_alc\_skip\_flag and mb\_alc\_flag for the macroblock mbAddrN is equal to 0), condTermFlagN is set equal to 0. + +The variable ctxIdxInc is derived by + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (\text{I-83})$$ + +#### **I.9.1.3.5 Derivation process of ctxIdxInc for the syntax element mb\_alc\_flag** + +Output of this process is ctxIdxInc. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If mbAddrN is available and mb\_alc\_skip\_flag or mb\_alc\_flag for the macroblock mbAddrN is equal to 1, condTermFlagN is set equal to 1. +- Otherwise (mbAddrN is not available or mb\_alc\_skip\_flag and mb\_alc\_flag for the macroblock mbAddrN is equal to 0), condTermFlagN is set equal to 0. + +The variable ctxIdxInc is derived by: + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (\text{I-84})$$ + +#### **I.9.1.3.6 Derivation process of ctxIdxInc for the syntax element mb\_vsp\_flag** + +Output of this process is ctxIdxInc. + +The derivation process for neighbouring macroblocks specified in clause 6.4.11.1 is invoked and the output is assigned to mbAddrA and mbAddrB. + +Let the variable condTermFlagN (with N being either A or B) be derived as follows: + +- If mbAddrN is not available or mb\_vsp\_flag for the macroblock mbAddrN is equal to 0, condTermFlagN is set equal to 1. +- Otherwise (mbAddrN is available and mb\_vsp\_flag for the macroblock mbAddrN is equal to 1), condTermFlagN is set equal to 0. + +The variable ctxIdxInc is derived by: + +$$\text{ctxIdxInc} = \text{condTermFlagA} + \text{condTermFlagB} \quad (\text{I-85})$$ + +### **I.10 Profiles and levels** + +The specifications in Annex H apply. Additional profiles and specific values of profile\_idc are specified in the following. + +The profiles that are specified in clause I.10.1 are also referred to as the profiles specified in Annex I. + +#### **I.10.1 Profiles** + +All constraints for picture parameter sets that are specified in the following are constraints for picture parameter sets that become the active picture parameter set or an active view picture parameter set inside the bitstream. All constraints for 3D-AVC sequence parameter sets that are specified in the following are constraints for 3D-AVC sequence parameter sets that become the active 3D-AVC sequence parameter set or an active view 3D-AVC sequence parameter set inside the bitstream. + +### I.10.1.1 Enhanced Multiview Depth High profile + +Bitstreams conforming to the Enhanced Multiview Depth High profile shall obey the following constraints: + +- The base view bitstream as specified in clause H.8.5.3 shall obey all constraints of the High profile specified in clause A.2.4 and all active sequence parameter sets shall fulfil one of the following conditions: + - profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1, + - profile\_idc is equal to 100. +- Only I, P, and B slice types may be present. +- NAL unit streams shall not contain nal\_unit\_type values in the range of 2 to 4, inclusive. +- Arbitrary slice order is not allowed. +- Picture parameter sets shall have num\_slice\_groups\_minus1 equal to 0 only. +- Picture parameter sets shall have redundant\_pic\_cnt\_present\_flag equal to 0 only. +- When the profile\_idc is equal to 139 in a sequence parameter set, the frame\_mbs\_only\_flag in the sequence parameter set shall be equal to 1. +- 3D-AVC sequence parameter sets shall have chroma\_format\_idc equal to 0 only. +- 3D-AVC sequence parameter sets shall have bit\_depth\_luma\_minus8 equal to 0 only. +- 3D-AVC sequence parameter sets shall have bit\_depth\_chroma\_minus8 equal to 0 only. +- 3D-AVC sequence parameter sets shall have qpprime\_y\_zero\_transform\_bypass\_flag equal to 0 only. +- For each access unit, the value of level\_idc for all active view 3D-AVC sequence parameter set RBSPs shall be the same as the value of level\_idc for the active 3D-AVC sequence parameter set RBSP. +- The level constraints specified for the Enhanced Multiview Depth High profile in clause I.10.2 shall be fulfilled. + +Conformance of a bitstream to the Enhanced Multiview Depth High profile is indicated by profile\_idc being equal to 139. + +Decoders conforming to the Enhanced Multiview Depth High profile at a specific level shall be capable of decoding all bitstreams in which both of the following conditions are true: + +- a) All active 3D-AVC sequence parameter sets have one or more of the following conditions fulfilled: + - profile\_idc is equal to 139, + - profile\_idc is equal to 138, + - profile\_idc is equal to 128, + - profile\_idc is equal to 118 and constraint\_set5\_flag is equal to 1, + - profile\_idc is equal to 100, + - profile\_idc is equal to 77 or constraint\_set1\_flag is equal to 1. +- b) All active 3D-AVC sequence parameter sets have one or more of the following conditions fulfilled: + - level\_idc or (level\_idc and constraint\_set3\_flag) represent a level less than or equal to the specific level, + - level\_idc[ i ] or (level\_idc[ i ] and constraint\_set3\_flag) represent a level less than or equal to the specific level. + +## I.10.2 Levels + +The specification of clause H.10.2 applies. + +### I.10.2.1 Level limits for Enhanced Multiview Depth High profile + +The specification of clause H.10.2.1 applies. + +### I.10.2.2 Profile specific level limits + +- a) In bitstreams conforming to the Enhanced Multiview Depth High profile, 3D-AVC sequence parameter sets shall have frame\_mbs\_only\_flag equal to 1 for the levels specified in Table A-4. + +## I.11 Byte stream format + +The specifications in Annex B apply. + +## I.12 3D-AVC hypothetical reference decoder + +The specifications in Annex C apply with substituting 3D-AVC sequence parameter set for MVC sequence parameter set. + +## I.13 3D-AVC SEI messages + +The specifications in Annex D and clause H.13 together with the extensions and modifications specified in this clause apply. + +### I.13.1 SEI message syntax + +#### I.13.1.1 Constrained depth parameter set identifier SEI message syntax + +| | | | +|-------------------------------------------------------------|---|------------| +| constrained_depth_parameter_set_identifier( payloadSize ) { | C | Descriptor | +| max_dps_id | 5 | ue(v) | +| max_dps_id_diff | 5 | ue(v) | +| } | | | + +### I.13.2 SEI message semantics + +#### I.13.2.1 Constrained depth parameter set identifier SEI message semantics + +When present, this message shall be associated with an IDR access unit. The semantics of the message are valid for the current coded video sequence. A constrained depth parameter set identifier SEI message indicates that depth\_parameter\_set\_id and dps\_id values present in the coded video sequence are constrained as specified below. + +NOTE 1 – When a constrained depth parameter set identifier SEI message is present, decoders are able to conclude losses of depth parameter set NAL units. + +**max\_dps\_id** plus 1 specifies the maximum allowed depth\_range\_parameter\_set\_id value. + +**max\_dps\_id\_diff** specifies the value range of depth\_range\_parameter\_set\_id values marked as "used". max\_dps\_id\_diff \* 2 shall be less than max\_dps\_id. + +For each coded slice, the following applies: + +- For the first coded slice of an IDR access unit, MaxUsedDpsId is set equal to "no value", UsedDpsIdSet is an empty set of values, and all depth range parameter set RBSPs included in the bitstream or made available to the decoding process through external means prior to the access unit containing the IDR picture are marked unavailable. +- When MaxUsedDpsId is not equal to "no value", the value of dps\_id of the slice header is constrained and the variable updateMaxUsedDpsIdFlag is set as follows: + - If dps\_id is equal to 0, the variable updateMaxUsedDpsIdFlag is set equal to 0. + - Otherwise, the variable zeroBasedDpsId is equal to dps\_id – 1 and dps\_id is constrained so that zeroBasedDpsId fulfils the following: + - If MaxUsedDpsId >= max\_dps\_id\_diff and MaxUsedDpsId <= max\_dps\_id – max\_dps\_id\_diff, zeroBasedDpsId is in the range of MaxUsedDpsId – max\_dps\_id\_diff to MaxUsedDpsId + max\_dps\_id\_diff, inclusive. The variable updateMaxUsedDpsIdFlag is set equal to ( zeroBasedDpsId > MaxUsedDpsId ). + - Otherwise, if MaxUsedDpsId < max\_dps\_id\_diff, zeroBasedDpsId is either in the range of 0 to MaxUsedDpsId + max\_dps\_id\_diff, inclusive, or in the range of max\_dps\_id – ( max\_dps\_id\_diff – MaxUsedDpsId – 1 ) to max\_dps\_id, inclusive. The updateMaxUsedDpsIdFlag is set equal to ( zeroBasedDpsId > MaxUsedDpsId && zeroBasedDpsId < max\_dps\_id – ( max\_dps\_id\_diff – MaxUsedDpsId – 1 ) ). + - Otherwise (MaxUsedDpsId > max\_dps\_id – max\_dps\_id\_diff), zeroBasedDpsId is either in the range of 0 to max\_dps\_id\_diff – ( max\_dps\_id – MaxUsedDpsId ) – 1, inclusive, or in the range of MaxUsedDpsId – max\_dps\_id\_diff to max\_dps\_id, inclusive. The updateMaxUsedDpsIdFlag is set equal to + +( zeroBasedDpsId > MaxUsedDpsId || zeroBasedDpsId < max\_dps\_id\_diff - ( max\_dps\_id - MaxUsedDpsId ) ). + +- When updateMaxUsedDpsIdFlag is equal to 1, depth range parameter set RBSPs are marked as unavailable as follows: + +``` + +prevMinUsedDpsId = MaxUsedDpsId - max_dps_id_diff +if( prevMinUsedDpsId < 0 ) + prevMinUsedDpsId += max_dps_id +minUsedDpsId = dps_id - 1 - max_dps_id_diff +if( minUsedDpsId < 0 ) + minUsedDpsId += max_dps_id +i = prevMinUsedDpsId +do { + Mark depth range parameter set RBSP with depth_range_parameter_set_id equal to i + 1, + if present, as unavailable. + i = ( i + 1 ) % ( max_dps_id + 1 ) +} while( i != minUsedDpsId ) + +``` + +(I-86) + +- When updateMaxUsedDpsIdFlag is equal to 1 or MaxUsedDpsId is equal to "no value", the following applies: + - MaxUsedDpsId is set equal to dps\_id - 1. + - If MaxUsedDpsId is greater than or equal to max\_dps\_id\_diff, UsedDpsIdSet is set to the values in the range of MaxUsedDpsId - max\_dps\_id\_diff to MaxUsedDpsId, inclusive. + - Otherwise (MaxUsedDpsId is smaller than max\_dps\_id\_diff), UsedDpsIdSet is set to the values in the range of 0 to MaxUsedDpsId, inclusive, and in the range of max\_dps\_id - ( max\_dps\_id\_diff - MaxUsedDpsId ) to max\_dps\_id, inclusive. + +Any depth parameter set RBSP included in the bitstream or made available to the decoding process through external means and having depth\_parameter\_set\_id equal to any value included in UsedDpsIdSet + 1 has the same content as the previous depth parameter set RBSP included in the bitstream or made available to the decoding process through external means having the same depth\_range\_parameter\_id value. + +NOTE 2 – If a slice header includes a dps\_id value marked as unavailable, a decoder should infer an unintentional loss of a depth parameter set with depth\_parameter\_set\_id value equal to the dps\_id value of the slice header. + +## I.14 Video usability information + +The specifications in clause H.14 apply. + +## Bibliography + +- Recommendation ITU-T H.222.0 (2021), *Information technology – Generic coding of moving pictures and associated audio information: Systems*. +- Recommendation ITU-T H.261 (1993), *Video codec for audiovisual services at p x 64 kbit/s*. +- Recommendation ITU-T H.262 (2012), *Information technology - Generic coding of moving pictures and associated audio information: Video*. +- Recommendation ITU-T H.263 (2005), *Video coding for low bit rate communication*. +- Recommendation ITU-T H.320 (2004), *Narrow-band visual telephone systems and terminal equipment*. +- Recommendation ITU-T BT.1886-0 (2011), *Reference electro-optical transfer function for flat panel displays used in HDTV studio production*. +- Recommendation ITU-R BT.709-6 (2015), *Parameter values for the HDTV standards for production and international programme exchange*. +- Recommendation ITU-R BT.2100-2 (2018), *Image parameter values for high dynamic range television for use in production and international programme exchange*. +- Recommendation ITU-R BT.1361-0 (1998), *Worldwide unified colorimetry and related characteristics of future television and imaging systems*. +- Recommendation ITU-R BT.2035 (2013), *A reference viewing environment for evaluation of HDTV program material or completed programmes*. +- Recommendation ITU-R BT.470-7 (2005), *Conventional analogue television systems*. +- Recommendation ITU-R BT.601-7(2011), *Studio encoding parameters of digital television for standard 4:3 and wide screen 16:9 aspect ratios*. +- Recommendation ITU-R BT.1358-1 (2007), *Studio parameters of 625 and 525 line progressive television systems*. +- Recommendation ITU-R BT.1700-0 (2005), *Characteristics of composite video signals for conventional analogue television systems*. +- Recommendation ITU-R BT.2100-2 (2018), *Image parameter values for high dynamic range television for use in production and international programme exchange*. +- Recommendation ITU-R BT.2020-2 (2015), *Parameter values for ultra-high definition television systems for production and international programme exchange*. +- ANSI/CTA 861-G-2016, *A DTV Profile for Uncompressed High Speed Digital Interfaces*. +- Association of Radio Industries and Businesses ARIB STD-B67 (2015) *Parameter values for the Hybrid Log-gamma (HLG) High Dynamic Range Television (HDR-TV) System for Programme Production*. +- Consumer Technology Association CTA-861.3, *HDR Static Metadata Extensions (CTA-861.3-A)*. +- Commission Internationale de l'Eclairage CIE 15:2018 *Colorimetry, 4th Edition*. +- Commission Internationale de l'Eclairage CIE 1931, *Standard colorimetric observer*. +- EBU Tech 3213-E (1975), *EBU Standard for Chromaticity Tolerances for Studio Monitors*. +- EG 432-1-2010, SMPTE Standard *Digital Source Processing - Color Processing for D-Cinema (Revision of EG 432-1-2007)*. +- IEC 61966-2-1/AMD 1:2003, *Multimedia systems and equipment – Colour measurement and management – Part 2-1: Colour management – Default RGB colour space – sRGB – Amendment 1*. +- IEC 61966-2-4:2006/AMD22:2021, *Multimedia systems and equipment – Colour measurement and management – Part 2-4: Colour management – Extended-gamut YCC colour space for video applications – xvYCC*. +- IETF RFC 5646 (2009), *Tags for Identifying Languages*. +- ISO 11664-1:2007, *Colorimetry – Part 1: CIE standard colorimetric observers*. + +- ISO/IEC 13818-1:2019, *Information technology – Generic coding of moving pictures and associated audio information – Part 1: Systems.* +- ISO/IEC 14496-10:2020, *Information technology – Coding of audio visual objects – Part 10: Advanced video coding.* +- ISO/CIE 11664-3:2019, *Colorimetry – Part 3: CIE tristimulus values.* +- ISO/IEC 11578:1996, *Information technology – Open Systems Interconnection – Remote Procedure Call (RPC).* +- RP 431-2:2011, SMPTE Standard *D-Cinema Quality - Reference Projector and Environment.* +- RP 177-1993, SMPTE Standard *Derivation of Basic Television Color Equations (R2002).* +- SMPTE 170M-2004, *Television - Composite Analog Video Signal - NTSC for Studio Applications.* +- SMPTE 240M-1999, *Television - 1125-Line High-Definition Production Systems – Signal Parameters.* +- ST 2086:2018, SMPTE Standard - *Mastering Display Color Volume Metadata Supporting High Luminance and Wide Color Gamut Images.* +- ST 428-1:2006, SMPTE Standard *D-Cinema Distribution Master - Image Characteristics.* +- ST 2113:2018, SMPTE Standard *Colorimetry of P3 Color Spaces.* + +- ST 2084:2014, SMPTE Standard *Dynamic Range Electro-Optical Transfer Function of Mastering Reference Displays.* +- ST 2085:2015, SMPTE Standard *Y'D'(Z)D'(X) Color-Difference Computations for High Dynamic Range X'Y'Z' Signals.* +- United States Federal Communications Commission Title 47 Code of Federal Regulations 47 CFR § 73.682 (2016) *TV transmission standards.* + / +[https://www.ecfr.gov/current/title-47/chapter-I/subchapter-C/part-73/subpart-E/section-73.682#p-73.682\(d\)](https://www.ecfr.gov/current/title-47/chapter-I/subchapter-C/part-73/subpart-E/section-73.682#p-73.682(d)) + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.264.1-201602-I_PDF-E/raw.md b/marked/H/T-REC-H.264.1-201602-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1840a07490525b83f9d60ea514af8089b71709cf --- /dev/null +++ b/marked/H/T-REC-H.264.1-201602-I_PDF-E/raw.md @@ -0,0 +1,4008 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.264.1** + +(02/2016) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Coding of moving +video + +--- + +**Conformance specification for ITU-T H.264 +advanced video coding** + +Recommendation ITU-T H.264.1 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. The letters 'ITU' are written in blue below the globe. + +International +Telecommunication +Union + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.264.1 + +# Conformance specification for ITU-T H.264 advanced video coding + +## Summary + +Recommendation ITU-T H.264.1 | International Standard ISO/IEC 14496-4 specifies tests designed to verify whether bitstreams and decoders meet the normative requirements specified in Rec. ITU-T H.264 | ISO/IEC 14496-10: + +- An encoder can claim conformance to Rec. ITU-T H.264 | ISO/IEC 14496-10 if the bitstreams that it generates are conforming bitstreams. +- A decoder can claim conformance to a specified profile and level of Rec. ITU-T H.264 if it can properly decode all bitstreams obeying constraints specified in Rec. ITU-T H.264 | ISO/IEC 14496-10. + +The tests specified in this Recommendation provide methods for (non-exhaustive) testing of whether encoders and decoders meet these requirements. + +This twin text with ISO/IEC has been jointly developed in the context of the ITU-T/ISO/IEC Joint Video Team (JVT) and has been submitted to ISO/IEC JTC 1/SC 29/WG 11 (MPEG) as ISO/IEC 14496-4:2002/Amendment 6 (2005 E), ISO/IEC 14496-4:2004/Amendment 9, ISO/IEC 14496-4:2004/Amendment 30, ISO/IEC 14496-4:2004/Amendment 31, ISO/IEC 14496-4:2004/Amendment 38, ISO/IEC 14496-4:2004/Amendment 41, ISO/IEC 14496-4:2004/Amendment 42, ISO/IEC 14496-4:2004/Amendment 43 and ISO/IEC 14496-4:2004/Amendment 45. + +The first approved version of Recommendation ITU-T H.264.1 (03/2005) included the specification of bitstreams for the testing of decoders for conformance to the Baseline, Extended, Main, High, High 10, and High 4:2:2 profiles specified in Rec. ITU-T H.264 | ISO/IEC 14496-10. + +Corrigendum 1 to Recommendation H.264.1 (09/2005), which was integrated into the first published edition of Rec. ITU-T H.264.1, provided improved synchronization with the technically-aligned twin text in ISO/IEC, removed some errors, and added tests for some required features that were not tested in the previous version. + +The second edition of Recommendation ITU-T H.264.1 (06/2008) provided corrections relative to the previous version of Rec. ITU-T H.264.1 and added additional bitstreams for the testing of decoders for conformance to the High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra profiles specified in Rec. ITU-T H.264 | ISO/IEC 14496-10. + +The third edition of Recommendation ITU-T H.264.1 (04/2010) adds additional bitstreams for the testing of decoders for conformance to the Constrained Baseline, Scalable Baseline, Scalable High, Scalable High Intra, Multiview High, and Stereo High profiles specified in Rec. ITU-T H.264 | ISO/IEC 14496-10. Some of these added bitstreams are also specified for the testing of decoders for conformance to the previously-existing profiles. + +The fourth edition of Recommendation ITU-T H.264.1 (01/2012) corrects minor errors in the bitstreams and associated text specification. + +The fifth edition of Recommendation ITU-T H.264.1 (10/2014) adds additional bitstreams for the testing of decoders for conformance to the Multiview Depth High and MFC (Multi-resolution Frame Compatible) High profiles specified in Rec. ITU-T H.264 | ISO/IEC 14496-10). + +The sixth edition of Recommendation ITU-T H.264.1 (02/2016) adds additional bitstreams for the testing of decoders for conformance to the Enhanced Multiview Depth High and MFC (Multi-resolution Frame Compatible) Depth High profiles specified in Rec. ITU-T H.264 | ISO/IEC 14496-10). + +The conformance bitstreams identified in Recommendation ITU-T H.264.1 are available as an electronic attachment to this Recommendation and can be downloaded from the ITU-T Test Signal Database at . + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-----------------------------|------------|-------------|------------------------------------| +| 1.0 | ITU-T H.264.1 | 2005-03-01 | 16 | 11.1002/1000/2209 | +| 1.1 | ITU-T H.264.1 (2005) Cor. 1 | 2005-09-13 | 16 | 11.1002/1000/8573 | +| 2.0 | ITU-T H.264.1 | 2008-06-13 | 16 | 11.1002/1000/9486 | +| 3.0 | ITU-T H.264.1 | 2010-04-13 | 16 | 11.1002/1000/10636 | +| 4.0 | ITU-T H.264.1 | 2012-01-13 | 16 | 11.1002/1000/11467 | +| 5.0 | ITU-T H.264.1 | 2014-10-14 | 16 | 11.1002/1000/12294 | +| 6.0 | ITU-T H.264.1 (V6) | 2016-02-13 | 16 | 11.1002/1000/12643 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------------------------------------------|-------------| +| 1 Scope ..... | 1 | +| 2 Normative references..... | 1 | +| 2.1 General ..... | 1 | +| 2.2 Identical Recommendations International Standards ..... | 1 | +| 2.3 Paired Recommendations International Standards equivalent in technical content..... | 1 | +| 2.4 Additional references ..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions..... | 2 | +| 6 Conformance for ITU-T H.264 ISO/IEC 14496-10..... | 2 | +| 6.1 Introduction ..... | 2 | +| 6.2 Bitstream conformance ..... | 2 | +| 6.3 Decoder conformance ..... | 2 | +| 6.4 Procedure to test bitstreams..... | 2 | +| 6.5 Procedure to test decoder conformance..... | 3 | +| 6.6 Specification of the test bitstreams..... | 6 | +| 6.7 Normative test suites for ITU-T H.264 ISO/IEC 14496-10 ..... | 84 | + +Electronic attachment: Conformance bitstreams for ITU-T H.264.1 (02/2016). + +# Introduction + +This introduction does not form an integral part of this Recommendation | International Standard. + +This Recommendation | International Standard has been jointly developed by ITU-T Video Coding Experts Group (VCEG) and the ISO/IEC Moving Picture Experts Group (MPEG). It is published as technically-aligned twin text in both organizations (ITU-T and ISO/IEC). + +This Recommendation | International Standard specifies a set of tests designed to indicate whether bitstreams and decoders meet the normative requirements specified in ITU-T H.264 | ISO/IEC 14496-10. An encoder can claim conformance to ITU-T H.264 | ISO/IEC 14496-10 if the bitstreams that it generates are conforming bitstreams. + +Characteristics of coded bitstreams and decoders are specified for ITU-T H.264 | ISO/IEC 14496-10. The characteristics of a bitstream specify the subset of the standard that is exploited in the bitstream. Examples are the applied values or range of the picture size and bit rate parameters. Decoder characteristics specify the properties and capabilities of the applied decoding process. The capabilities of a decoder specify which bitstreams the decoder can decode by specifying the subset of ITU-T H.264 | ISO/IEC 14496-10 that may be exploited in the bitstreams that it will decode. A bitstream can be decoded by a conforming decoder if the characteristics of the bitstream are within the subset of the standard specified by the decoder capabilities. + +Procedures are specified for testing conformance of bitstreams and decoders to the requirements specified in ITU-T H.264 | ISO/IEC 14496-10. Given the set of characteristics claimed, the requirements that shall be met are fully determined by ITU-T H.264 | ISO/IEC 14496-10. This Recommendation | International Standard summarizes the requirements, cross references them to characteristics, and specifies how conformance with them can be tested. Guidelines are given on constructing tests to verify bitstream and decoder conformance. This Recommendation | International Standard gives guidelines on how to construct bitstream test suites to check or verify decoder conformance. In addition, the test bitstreams implemented according to those guidelines are provided as an electronic attachment to this Recommendation | International Standard. When the decoder under test does not satisfy the requirements of the tests, the decoder is not conforming to ITU-T H.264 | ISO/IEC 14496-10. + +These conformance tests make use of test data (bitstream test suites) provided as an electronic attachment to this Recommendation | International Standard, and the reference software decoder specified in ITU-T H.264.2 | ISO/IEC 14496-5 with source code available in electronic format. + +The bitstream files accompanying this Recommendation | International Standard, which require a substantial amount of disk space, can be purchased in physical medium (DVD) from the ITU-T bookshop, or can be directly downloaded from the ITU-T Test Signal Database at . + + + +# Conformance specification for ITU-T H.264 advanced video coding + +# 1 Scope + +This Recommendation | International Standard1 specifies a set of tests and procedures designed to indicate whether encoders or decoders meet the normative requirements specified in ITU-T H.264 | ISO/IEC 14496-10. + +NOTE – This edition includes the text approved 03/2005, its Corrigendum 1 approved 09/2005, conformance tests for professional profiles (approved 06/2008), conformance tests for the Constrained Baseline, Scalable and Multiview profiles (approved 04/2010), conformance tests for the Multiview Depth High and Multi-resolution Frame Compatible High profiles (approved 10/2014), and conformance tests for the Enhanced Multiview Depth High and MFC (Multi-resolution Frame Compatible) Depth High profiles (approved 02/2016). + +# 2 Normative references + +## 2.1 General + +The following Recommendations and International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this Recommendation | International Standard are encouraged to investigate the possibility of applying the most recent edition of the Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently valid ITU-T Recommendations. + +## 2.2 Identical Recommendations | International Standards + +- None. + +## 2.3 Paired Recommendations | International Standards equivalent in technical content + +- ITU-T H.264 (in force), *Advanced video coding for generic audiovisual services*. +ISO/IEC 14496-10: in force, *Information technology – Coding of audio-visual objects – Part 10: Advanced Video Coding*. +- ITU-T H.264.2 (in force), *Reference software for H.264 advanced video coding*. +ISO/IEC 14496-5: in force, *Information technology – Coding of audio-visual objects – Part 5: Reference software*. + +## 2.4 Additional references + +- None. + +# 3 Definitions + +For the purposes of this Recommendation | International Standard, the terms, definitions, abbreviations and symbols specified in ITU-T H.264 | ISO/IEC 14496-10 (particularly in clauses 3, G.3, and H.3) apply. The following terms are further clarified for purposes herein as follows. + +**3.1 bitstream:** An ITU-T H.264 | ISO/IEC 14496-10 video bitstream. A bitstream may contain IDR, I, P, B, SI, SP, EI, EP, and EB slices. + +**3.2 decoder:** An ITU-T H.264 | ISO/IEC 14496-10 video decoder, i.e., an embodiment of the decoding process specified by ITU-T H.264 | ISO/IEC 14496-10. The decoder does not include the display process, which is outside the scope of this Recommendation | International Standard. + +--- + +1 This Recommendation | International Standard includes an electronic attachment containing the conformance bitstreams identified within the text. The bitstreams can also be downloaded from the ITU-T Test Signal Database. + +**3.3 reference software decoder:** The software decoder contained in ITU-T H.264.2 | ISO/IEC 14496-5. + +**3.4 TemporalIdMax:** Maximum value of temporal\_id in the NAL unit header extension for SVC of the coded slice NAL units or prefix NAL units of an ITU-T H.264 | ISO/IEC 14496-10 video bitstream. + +# **4 Abbreviations and acronyms** + +For the purposes of this Recommendation | International Standard, relevant abbreviations and acronyms are specified in clause 4 of ITU-T H.264 | ISO/IEC 14496-10. + +# **5 Conventions** + +For the purposes of this Recommendation | International Standard, relevant conventions are specified in clause 5 in ITU-T H.264 | ISO/IEC 14496-10. + +# **6 Conformance for ITU-T H.264 | ISO/IEC 14496-10** + +## **6.1 Introduction** + +The following clauses specify the normative tests for verifying conformance of video bitstreams as well as decoders. Those normative tests make use of test data (bitstream test suites) provided as an electronic annex to this Recommendation | International Standard and the reference software decoder with source code included in electronic format. + +## **6.2 Bitstream conformance** + +The bitstream conformance of ITU-T H.264 | ISO/IEC 14496-10 is specified by clause C.3, G.12, or H.12 of ITU-T H.264 | ISO/IEC 14496-10. + +## **6.3 Decoder conformance** + +The decoder conformance of ITU-T H.264 | ISO/IEC 14496-10 is specified by clause C.4, G.12, or H.12 of ITU-T H.264 | ISO/IEC 14496-10. + +## **6.4 Procedure to test bitstreams** + +A bitstream that claims conformance with ITU-T H.264 | ISO/IEC 14496-10 shall pass the following normative test: + +The bitstream shall be decoded by processing it with the reference software decoder. When processed by the reference software decoder, the bitstream shall not cause any error or non-conformance messages to be reported by the reference software decoder. This test should not be applied to bitstreams that are known to contain errors introduced by transmission, as such errors are highly likely to result in bitstreams that lack conformance to ITU-T H.264 | ISO/IEC 14496-10. + +Successfully passing the reference software decoder test provides only a strong presumption that the bitstream under test is conforming to the video layer, i.e., that it does indeed meet all the requirements for the video layer (except Annexes C, D and E and clauses G.12, H.12, I.12 and J.12) specified in ITU-T H.264 | ISO/IEC 14496-10 that are tested by the reference software decoder. + +Additional tests may be necessary to more thoroughly check that the bitstream properly meets all the requirements specified in ITU-T H.264 | ISO/IEC 14496-10 including the hypothetical reference decoder (HRD) conformance (based on Annexes C, D and E and clauses G.12, H.12, I.12 and J.12). These complementary tests may be performed using other video bitstream verifiers that perform more complete tests than those implemented by the reference software decoder. + +ITU-T H.264 | ISO/IEC 14496-10 contains several informative recommendations that are not an integral part of that Recommendation | International Standard. When testing a bitstream for conformance, it may also be useful to test whether or not the bitstream follows those recommendations. + +To check correctness of a bitstream, it is necessary to parse the entire bitstream and to extract all the syntax elements and other values derived from those syntactic elements and used by the decoding process specified in ITU-T H.264 | ISO/IEC 14496-10. + +A verifier may not necessarily perform all stages of the decoding process specified in ITU-T H.264 | ISO/IEC 14496-10 in order to verify bitstream correctness. Many tests can be performed on syntax elements in a state prior to their use in some processing stages. + +## **6.5 Procedure to test decoder conformance** + +### **6.5.1 Conformance bitstreams** + +A bitstream has values of profile\_idc, level\_idc, and constraint\_setX\_flag (where X is a number in the range of 0 to 6, inclusive) corresponding to a set of specified constraints on a bitstream for which a decoder conforming to a specified profile and level is required in Annex A, clause G.10, clause H.10, clause I.10, or clause J.10 of ITU-T H.264 | ISO/IEC 14496-10 to properly perform the decoding process. + +### **6.5.2 Contents of the bitstream file** + +The conformance bitstreams are included in this Recommendation | International Standard as an electronic attachment. The following information is included in a single zipped file for each such bitstream. + +- bitstream; +- decoded pictures or hashes of decoded pictures (may not be present); +- short description of the bitstream; +- trace file (the bitstream in ASCII format). + +In cases where the decoded pictures or hashes of decoded pictures are not available, the reference software decoder shall be used to generate the necessary reference decoded pictures from the bitstream. + +### **6.5.3 Requirements on output of the decoding process and timing** + +Two classes of decoder conformance are specified: + +- output order conformance; and +- output timing conformance. + +The output of the decoding process is specified in clauses 8, G.8, G.12, H.8, H.12, I.8, I.12, J.8, J.12 and Annex C of ITU-T H.264 | ISO/IEC 14496-10. + +For output order conformance, it is a requirement that all of the decoded pictures specified for output in Annex C, clause G.12, clause H.12, clause I.12, or clause J.12 of ITU-T H.264 | ISO/IEC 14496-10 shall be output by a conforming decoder in the specified order and that the values of the decoded samples in all of the pictures that are output shall be (exactly equal to) the values specified in clause 8, clause G.8, clause H.8, clause I.8, or clause J.12 of ITU-T H.264 | ISO/IEC 14496-10. + +For output timing conformance, it is a requirement that a conforming decoder shall also output the decoded samples at the rates and times specified in Annex C, clause G.12, clause H.12, clause I.12, or clause J.12 of ITU-T H.264 | ISO/IEC 14496-10. + +The display process, which ordinarily follows the output of the decoding process, is outside the scope of this Recommendation | International Standard. + +### **6.5.4 Recommendations (informative)** + +This clause does not form an integral part of this Recommendation | International Standard. + +In addition to the requirements, it is desirable that conforming decoders implement various informative recommendations specified in ITU-T H.264 | ISO/IEC 14496-10 that are not an integral part of that Recommendation | International Standard. This clause lists some of these recommendations. + +It is recommended that a conforming decoder be able to resume the decoding process as soon as possible after the loss or corruption of part of a bitstream. In most cases it is possible to resume decoding at the next start code or slice header. It is recommended that a conforming decoder be able to perform concealment for the macroblocks or video packets for which all the coded data has not been received. + +### **6.5.5 Static tests for output order conformance** + +Static tests of a video decoder require testing of the decoded samples. This clause will explain how this test can be accomplished when the decoded samples at the output of the decoding process are available. It may not be possible to perform this type of test with a production decoder (due to the lack of an appropriate accessible interface in the design at which to perform the test). In that case this test should be performed by the manufacturer during the design and + +development phase. Static tests are used for testing the decoding process. The test will check that the values of the samples decoded by the decoder under test shall be identical to the values of the samples decoded by the reference decoder. When a hash of the values of the samples of the decoded pictures is attached to the bitstream file, a corresponding hash operation performed on the values of the samples of the decoded pictures produced by the decoder under test shall produce the same results. + +### 6.5.6 Dynamic tests for output timing conformance + +Dynamic tests are applied to check that all the decoded samples are output and that the timing of the output of the decoder's decoded samples conforms to the specification of clauses 8, G.8, G.12, H.8, H.12, I.8, I.12, J.12 and Annex C of ITU-T H.264 | ISO/IEC 14496-10, and to verify that the HRD models (as specified by the CPB and DPB specification in Annex C, clause G.12, clause H.12, clause I.12, or clause J.12 of ITU-T H.264 | ISO/IEC 14496-10) are not violated when the bits are delivered at the proper rate. + +The dynamic test is often easier to perform on a complete decoder system, which may include a systems decoder, a video decoder and a display process. It may be possible to record the output of the display process and to check that display order and timing of fields or frames are correct at the output of the display process. However, since the display process is not within the normative scope of ITU-T H.264 | ISO/IEC 14496-10, there may be cases where the output of the display process differs in timing or value even though the video decoder is conforming. In this case, the output of the video decoder itself (before the display process) would need to be captured in order to perform the dynamic tests on the video decoder. In particular, the field or frame order and timing shall be correct. + +If buffering period SEI and picture timing SEI are included in the test bitstream, HRD conformance shall be verified using the values of `initial_cpb_removal_delay`, `initial_cpb_removal_delay_offset`, `cpb_removal_delay` and `dpb_removal_delay` that are included in the bitstream. + +If buffering period SEI and picture timing SEI are not included in the bitstream, the following inferences shall be made to generate the missing parameters: + +- `fixed_frame_rate_flag` shall be inferred to be 1. +- `low_delay_hrd_flag` shall be inferred to be 0. +- `cbr_flag` shall be inferred to be 0. +- The frame rate of the bitstream shall be inferred to be the frame rate value specified in the corresponding table of clause 6.7, where the bitstream is listed. If this is missing, then a frame rate of either 25 or $30000 \div 1001$ can be inferred. +- `time_scale` shall be set to 90,000 and the value of `num_units_in_tick` shall be computed based on field rate (twice the frame rate). +- The bit rate of the bitstream shall be inferred to be the maximum value for the level specified in Table A-1 in ITU-T H.264 | ISO/IEC 14496-10. +- CPB and DPB sizes shall be inferred to be the maximum value for the level specified in Table A-1 in ITU-T H.264 | ISO/IEC 14496-10. + +With the above inferences, the HRD shall be operated as follows. + +- The CPB is filled starting at time $t = 0$ , until it is full, before removal of the first access unit. This means that the `initial_cpb_removal_delay` shall be inferred to be equal to the total CPB buffer size divided by the bit rate divided by 90000 (rounded downwards) and `initial_cpb_removal_delay_offset` shall be inferred to be equal to zero. +- The first access unit is removed at time $t = \text{initial\_cpb\_removal\_delay} \div 90000$ and subsequent access units are removed at intervals based on the frame distance, i.e., $2 * (90000 \div \text{num\_units\_in\_tick})$ or the field distance, i.e., $(90000 / \text{num\_units\_in\_tick})$ , depending on whether the access unit is coded as a frame picture or field picture. +- Using these inferences, the CPB will not overflow or underflow and the DPB will not overflow. + +### 6.5.7 Decoder conformance test of a particular profile-and-level + +In order for a decoder of a particular profile-and-level to claim output order conformance to ITU-T H.264 | ISO/IEC 14496-10 as specified by this Recommendation | International Standard, the decoder shall successfully pass the static test specified in clause 6.5.5 with all the bitstreams of the normative test suite specified for testing decoders of this particular profile-and-level. + +In order for a decoder of a particular profile and level to claim output timing conformance to ITU-T H.264 | ISO/IEC 14496-10 as specified by this Recommendation | International Standard, the decoder shall successfully pass both the static test specified in clause 6.5.5 and the dynamic test specified in clause 6.5.6 with all the + +bitstreams of the normative test suite specified for testing decoders of this particular profile-and-level. Tables 1 through 5 specify the normative test suites for each profile-and-level combination. The test suite for a particular profile-and level combination is the list of bitstreams that are marked with an 'X' in the column corresponding to that profile-and-level combination. + +'X' indicates that the bitstream is designed to test both the dynamic and static conformance of the decoder. + +The bitstream column specifies the bitstream used for each test. + +A decoder that conforms to the Constrained Baseline profile at a specific level shall be capable of decoding the specified bitstreams in Tables 1 and 4. + +A decoder that conforms to the Baseline, Extended, or Main profile at a specific level shall be capable of decoding the specified bitstreams in Table 1. A decoder that conforms to the Baseline, Extended, or Main profile shall also be capable of decoding all bitstreams that are required to be decoded by a Constrained Baseline profile decoder of the same level. In addition to the specified bitstreams in Table 1, a decoder that conforms to the Baseline, Extended, or Main profile shall be capable of decoding the bitstreams in Table 4 that correspond to this requirement. + +A decoder that conforms to the High, High 10, or High 4:2:2 profile at a specific level shall be capable of decoding the specified bitstreams in Table 2. A decoder that conforms to the High, High 10, or High 4:2:2 profile shall also be capable of decoding all bitstreams that are required to be decoded by a Constrained Baseline or Main profile decoder of the same level. A decoder that conforms to the High 10 or High 4:2:2 profile shall also be capable of decoding all bitstreams that are required to be decoded by a High 10 Intra profile decoder of the same level. A decoder that conforms to the High 4:2:2 profile shall also be capable of decoding all bitstreams that are required to be decoded by a High 4:2:2 Intra profile decoder of the same level. In addition to the specified bitstreams in Table 2, a decoder that conforms to the High, High 10, or High 4:2:2 profile shall be capable of decoding the bitstreams in Tables 1, 3 and 4 that correspond to these requirements. + +A decoder that conforms to the High 10 Intra profile at a specific level shall be capable of decoding the specified bitstreams in Tables 3 and 4. + +A decoder that conforms to the High 4:2:2 Intra, High 4:4:4 Intra, High 4:4:4 Predictive, or CAVLC 4:4:4 Intra profile at a specific level shall be capable of decoding the specified bitstreams in Table 3. A decoder that conforms to the High 4:2:2 Intra, High 4:4:4 Intra, or High 4:4:4 Predictive profile shall also be capable of decoding all bitstreams that are required to be decoded by a High 10 Intra profile decoder of the same level. A decoder that conforms to the High 4:4:4 Predictive profile shall also be capable of decoding all bitstreams that are required to be decoded by a Constrained Baseline, Main, or High profile decoder of the same level. In addition to the specified bitstreams in Table 3, a decoder that conforms to the High 4:2:2 Intra, High 4:4:4 Intra, or High 4:4:4 Predictive profile shall be capable of decoding the bitstreams in Tables 1, 2, and 4 that correspond to these requirements. + +A decoder that conforms to the Scalable Baseline profile at a specific level shall be capable of decoding the specified bitstreams in Table 4. A decoder that conforms to the Scalable Baseline profile shall also be capable of decoding all bitstreams that are required to be decoded by a Constrained Baseline profile decoder of the same level. In addition to the specified bitstreams in Table 4, a decoder that conforms to the Scalable Baseline profile shall be capable of decoding the bitstreams in Table 1 that correspond to this requirement. + +A decoder that conforms to the Scalable High profile at a specific level shall be capable of decoding the specified bitstreams in Table 4. A decoder that conforms to the Scalable High profile shall also be capable of decoding all bitstreams that are required to be decoded by a Constrained Baseline, Main, or High profile decoder of the same level. In addition to the specified bitstreams in Table 4, a decoder that conforms to the Scalable High profile shall be capable of decoding the bitstreams in Tables 1 and 2 that correspond to this requirement. + +A decoder that conforms to the Scalable High Intra profile at a specific level shall be capable of decoding the specified bitstreams in Table 4. + +A decoder that conforms to the Multiview High or Stereo High profile at a specific level shall be capable of decoding the specified bitstreams in Table 5. A decoder that conforms to the Multiview High or Stereo High profile shall also be capable of decoding all bitstreams that are required to be decoded by a Constrained Baseline profile decoder of the same level. A decoder that conforms to the Stereo High profile shall also be capable of decoding all bitstreams that are required to be decoded by a Main or High profile decoder of the same level. In addition to the specified bitstreams in Table 5, a decoder that conforms to the Multiview High or Stereo High profile shall be capable of decoding the bitstreams in Tables 1, 2 and 4 that correspond to these requirements. + +A decoder that conforms to the Multiview Depth High profile at a specific level shall be capable of decoding the specified bitstreams in Table 6. A decoder that conforms to the Multiview Depth High profile shall also be capable of decoding all bitstreams that are required to be decoded by a Main, High or Stereo High profile decoder of the same level. In addition to the specified bitstreams in Table 6, a decoder that conforms to the Multiview Depth High profile shall be capable of decoding the bitstreams in Tables 1, 2 and 5 that correspond to these requirements. + +A decoder that conforms to the MFC High profile at a specific level shall be capable of decoding all bitstreams in which all active MVC sequence parameter sets have any of the following: + +- profile\_idc equal to 134 +- profile\_idc equal to 128 +- profile\_idc is equal to 118 and constraint\_set5\_flag is equal to 1 +- profile\_idc equal to 100 or 77 +- profile\_idc equal to 88 and constraint\_set1\_flag equal to 1 +- profile\_idc equal to 66 and constraint\_set1\_flag equal to 1 + +and in which level\_idc or the combination of level\_idc and constraint\_set3\_flag for all active MVC sequence parameter sets represent a level less than or equal to the specific level. In addition to the bitstreams defined in Table 7, a decoder that conforms to the MFC High profile shall be capable of decoding the Main profile bitstreams specified in Tables 1 and 2. + +A decoder that conforms to the Enhanced Multiview Depth High profile at a specific level shall be capable of decoding the specified bitstreams in Table 8. A decoder that conforms to the Enhanced Multiview Depth High profile shall also be capable of decoding all bitstreams that are required to be decoded by a Main or High profile decoder of the same level. In addition to the specified bitstreams in Table 8, a decoder that conforms to the Enhanced Multiview Depth High profile shall be capable of decoding the bitstreams in Tables 1, 2 and 4 that correspond to these requirements. + +A decoder that conforms to the MFC Depth High profile at a specific level shall be capable of decoding the specified bitstreams in Table 9. A decoder that conforms to the MFC Depth High profile shall also be capable of decoding all bitstreams that are required to be decoded by a Main, High, Stereo High and MFC High profile decoder of the same level. In addition to the specified bitstreams in Table 9, a decoder that conforms to the MFC Depth High profile shall be capable of decoding the bitstreams in Tables 1, 2, 5 and 7 that correspond to these requirements. + +## 6.6 Specification of the test bitstreams + +Some characteristics of each bitstream listed in Tables 1 through 5 are specified in this clause. In Tables 1 through 5, the value "29.97" shall be interpreted as an approximation of an exact value of $30000 \div 1001$ and the value "59.94" shall be interpreted as an approximation of an exact value of $60000 \div 1001$ . + +### 6.6.1 Test bitstreams – General + +#### 6.6.1.1 Test bitstreams AVCNL-1, AVCNL-2 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices. + +**Purpose:** Check that the decoder can properly decode I slices. + +#### 6.6.1.2 Test bitstreams AVCNL-3, AVCNL-4 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices. + +**Purpose:** Check that the decoder can properly decode P slices. + +#### 6.6.1.3 Test bitstream AVCBA-1 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with the deblocking filter process enabled. + +**Purpose:** Check that the decoder can properly decode I slices with the deblocking filter process enabled. + +#### 6.6.1.4 Test bitstream AVCBA-2 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with the deblocking filter process enabled. + +**Purpose:** Check that the decoder can properly decode I slices with the deblocking filter process enabled. + +#### 6.6.1.5 Test bitstream AVCBA-3 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with the deblocking filter process enabled. + +**Purpose:** Check that the decoder can properly decode P slice with the deblocking filter process enabled. + +#### 6.6.1.6 Test bitstream AVCBA-4 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with the deblocking filter process enabled. + +**Purpose:** Check that the decoder can properly decode P slices with the deblocking filter process enabled. + +#### 6.6.1.7 Test bitstreams AVCBA-5, AVCBA-6 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with the deblocking filter process enabled. + +**Purpose:** Check that the decoder can properly decode P slices with the deblocking filter process enabled. + +#### 6.6.1.8 Test bitstream AVCBA-7 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. Macroblock/sub-macroblock partition size is limited to 8x8 and above. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with the deblocking filter process enabled. + +**Purpose:** Check that the decoder can properly decode P slices with the deblocking filter process enabled. + +#### 6.6.1.9 Test bitstream AVCMQ-1 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 1. `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at each MB. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with `mb_qp_delta` not equal to 0. + +**Purpose:** Check that the decoder can properly decode I slices with `mb_qp_delta` not equal to 0. + +#### 6.6.1.10 Test bitstream AVCMQ-2 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 1. `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at each MB. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with `mb_qp_delta` not equal to 0. + +**Purpose:** Check that the decoder can properly decode P slices with mb\_qp\_delta not equal to 0. + +#### 6.6.1.11 Test bitstream AVCMQ-3 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. Spatial direct prediction is used for direct prediction. mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at each MB. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with mb\_qp\_delta not equal to 0. + +**Purpose:** Check that the decoder can properly decode I slices with mb\_qp\_delta not equal to 0. + +#### 6.6.1.12 Test bitstream AVCMQ-4 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. Spatial direct prediction is used for direct prediction. mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some MBs. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with mb\_qp\_delta not equal to 0. + +**Purpose:** Check that the decoder can properly decode P slices with mb\_qp\_delta not equal to 0. + +#### 6.6.1.13 Test bitstream AVCSL-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I and P slices. + +**Purpose:** Check that the decoder can properly decode pictures with multiple slices. + +#### 6.6.1.14 Test bitstream AVCSL-2 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I and P slices. + +**Purpose:** Check that the decoder can properly decode pictures with multiple slices. + +#### 6.6.1.15 Test bitstream AVCSQ-1 + +**Specification:** All slices are coded as I slices. Each picture contains 20 slices. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Spatial direct prediction is used for direct prediction. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with non-zero values of slice\_qp\_delta. + +**Purpose:** Check that the decoder can properly decode I slices with non-zero values of slice\_qp\_delta. + +#### 6.6.1.16 Test bitstream AVCFM-1 + +**Specification:** All slices are coded as I or P slices. The number of slices and slice groups is greater than 1 in each picture. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Multiple parameter sets are included in the bitstream. + +**Functional stage:** Slice groups. + +**Purpose:** Check that the decoder handles multiple slice groups and parameter sets. + +#### 6.6.1.17 Test bitstream AVCFM-2 + +**Specification:** All slices are coded as I or P slices. The number of slices and slice groups is greater than 1 in each picture. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slice groups. + +**Purpose:** Check that the decoder handles multiple slice groups and parameter sets. + +#### 6.6.1.18 Test bitstream AVCFM-3 + +**Specification:** All slices are coded as I or P slices. The number of slices and slice groups is greater than 1 in each picture. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. Recovery point SEI is included in this bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slice groups. + +**Purpose:** Check that the decoder handles multiple slice groups and parameter sets. + +#### 6.6.1.19 Test bitstream AVCCI-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. constrained\_intra\_pred\_flag is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Constrained intra prediction. + +**Purpose:** Check that the decoder handles constrained intra prediction. + +#### 6.6.1.20 Test bitstream AVCCI-2 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. constrained\_intra\_pred\_flag is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Constrained intra prediction. + +**Purpose:** Check that the decoder handles constrained intra prediction. + +#### 6.6.1.21 Test bitstream AVCCI-3 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. constrained\_intra\_pred\_flag is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Constrained intra prediction. + +**Purpose:** Check that the decoder handles constrained intra prediction. + +#### 6.6.1.22 Test bitstream AVCFC-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Decoded pictures are cropped with frame\_cropping\_flag equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I and P slices with frame cropping. + +**Purpose:** Check that the decoder can properly decode I and P slices with frame cropping. + +#### 6.6.1.23 Test bitstream AVCAUD-1 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Access unit delimiter NAL units are included in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with Access unit delimiter NAL units. + +**Purpose:** Check that the decoder can properly decode I slices with Access unit delimiter NAL units. + +#### 6.6.1.24 Test bitstream AVCMIDR-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. IDR is inserted in every two frames. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices and more than one IDR. + +**Purpose:** Check that the decoder can properly decode I slices with more than IDR in bitstream. + +#### 6.6.1.25 Test bitstream AVCNRF-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Two non-reference pictures are present. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I and P slices with non-reference pictures. + +**Purpose:** Check that the decoder can properly decode I and P slices with non-reference pictures. + +#### 6.6.1.26 Test bitstream AVCMPS-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Multiple parameter sets are included in this bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I and P slices with multiple parameter set. + +**Purpose:** Check that the decoder can properly decode I and P slices with multiple parameter set. + +#### 6.6.1.27 Test bitstream AVCBS-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with temporal direct prediction. + +**Purpose:** Check that the decoder can properly decode B slices with temporal direct prediction. + +#### 6.6.1.28 Test bitstream AVCBS-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with spatial direct prediction. + +**Purpose:** Check that the decoder can properly decode B slices with spatial direct prediction. + +#### 6.6.1.29 Test bitstream AVCBS-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with temporal direct prediction. + +**Purpose:** Check that the decoder can properly decode B slices with temporal direct prediction. + +#### 6.6.1.30 Test bitstream AVCBS-4 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with spatial direct prediction. + +**Purpose:** Check that the decoder can properly decode B slices with spatial direct prediction. + +#### 6.6.1.31 Test bitstream AVCBS-5 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Spatial direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with spatial direct prediction. + +**Purpose:** Check that the decoder can properly decode B slices with spatial direct prediction. + +### 6.6.2 Test bitstreams – I\_PCM + +#### 6.6.2.1 Test bitstreams AVCPHM-1, AVCPHM-2 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. mb\_type is equal to I\_PCM for some macroblocks. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of macroblocks with mb\_type equal to I\_PCM. + +**Purpose:** Check that the decoder can properly decode macroblocks with mb\_type equal to I\_PCM. + +### 6.6.3 Test bitstreams – Memory management control operation + +#### 6.6.3.1 Test bitstream AVCMR-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. Reference picture list reordering and memory management control operations are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. + +#### 6.6.3.2 Test bitstream AVCMR-2 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. + +#### 6.6.3.3 Test bitstream AVCMR-3 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and various memory management control operations are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that the decoder handles gaps in frame\_num, reference picture list reordering and memory management control operations. + +#### 6.6.3.4 Test bitstream AVCMR-4 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and various memory management control operations are used. The decoding order is different from the output order. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations and non-increasing PicOrderCnt values. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. Test output order conformance for non-increasing PicOrderCnt values. + +#### 6.6.3.5 Test bitstream AVCMR-5 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and various memory management control operations are used. The decoding order is different from the output order. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operation and non-increasing PicOrderCnt values. + +**Purpose:** Check that the decoder handles gaps\_in\_frame\_num\_value\_allowed\_flag equal to 1, reference picture list reordering and memory management control operation. Test output order conformance for non-increasing PicOrderCnt values. + +#### 6.6.3.6 Test bitstream AVCMR-6 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering is used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering. + +**Purpose:** Check that the decoder handles reference picture list reordering. + +#### 6.6.3.7 Test bitstream AVCMR-7 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Memory management control operations are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Memory management control operations. + +**Purpose:** Check that the decoder handles memory management control operations. + +#### 6.6.3.8 Test bitstreams AVCMR-8, AVCMR-9 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. Reference picture list reordering and memory management control operations are used. direct\_8x8\_inference\_flag is equal to 1. Each slice is a coded field. VUI is included in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. + +#### 6.6.3.9 Test bitstream AVCMR-10 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. Reference picture list reordering and memory management control operations are used. Temporal direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is equal to 1. Each slice is a coded field. VUI is included in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. + +#### 6.6.3.10 Test bitstreams AVCMR-11, AVCMR-12 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering + +and memory management control operations are used. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. + +### 6.6.4 Test bitstreams – Weighted sample prediction process + +#### 6.6.4.1 Test bitstream AVCWP-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. `weighted_pred_flag` is equal to 1. Plural reference indices are assigned to each reference picture. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Weighted sample prediction process for P slices with plural reference indices. + +**Purpose:** Check that the decoder handles weighted sample prediction for P slices with plural reference indexes. + +#### 6.6.4.2 Test bitstream AVCWP-2 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. `weighted_pred_flag` is equal to 1. All NAL units are encapsulated into the byte stream specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Weighted sample prediction process for P slices. + +**Purpose:** Check that the decoder handles weighted sample prediction for P slices. + +#### 6.6.4.3 Test bitstream AVCWP-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `weighted_bipred_idc` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Weighted sample prediction process for B slices with temporal direct prediction. + +**Purpose:** Check that the decoder handles weighted sample prediction for B slices with temporal direct prediction. + +#### 6.6.4.4 Test bitstream AVCWP-4 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `weighted_bipred_idc` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Weighted sample prediction process for B slices with temporal direct prediction. + +**Purpose:** Check that the decoder handles weighted sample prediction for B slices with temporal direct prediction. + +### 6.6.5 Test bitstreams – Slice of coded field + +#### 6.6.5.1 Test bitstream AVCFI-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. Each slice is a coded field. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields. + +**Purpose:** Check that the decoder handles I and P slices of coded fields. + +#### 6.6.5.2 Test bitstream AVCFI-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. Each slice is a coded field. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields with spatial direct prediction. + +**Purpose:** Check that the decoder handles B slices of coded fields with spatial direct prediction. + +#### 6.6.5.3 Test bitstream AVCFI-3 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. Each slice is a coded field. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields. + +**Purpose:** Check that the decoder handles I and P slices of coded fields. + +#### 6.6.5.4 Test bitstream AVCFI-4 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. Each slice is a coded field. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields. + +**Purpose:** Check that the decoder handles I and P slices of coded fields. + +#### 6.6.5.5 Test bitstream AVCFI-5 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. Each slice is a coded field. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. Spatial direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields. + +**Purpose:** Check that the decoder handles B slices of coded fields. + +#### 6.6.5.6 Test bitstream AVCFI-6 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. Each slice is a coded field. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields. + +**Purpose:** Check that the decoder handles I and P slices of coded fields. + +#### 6.6.5.7 Test bitstream AVCFI-7 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. Each slice is a coded field. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Temporal direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields with temporal direct prediction. + +**Purpose:** Check that the decoder handles B slices of coded fields with temporal direct prediction. + +#### 6.6.5.8 Test bitstream AVCFI-8 + +**Specification:** All slices are coded as I slices. Only one slice is contained in each picture. Each slice is a coded field. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields. + +**Purpose:** Check that the decoder handles I slices of coded fields. + +#### 6.6.5.9 Test bitstream AVCFI-9 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. Each slice is a coded field. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields. + +**Purpose:** Check that the decoder handles I and P slices of coded fields. + +#### 6.6.5.10 Test bitstream AVCFI-10 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. Each slice is a coded field. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Temporal direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields with temporal direct prediction. + +**Purpose:** Check that the decoder handles B slices of coded fields with temporal direct prediction. + +#### 6.6.5.11 Test bitstream AVCFI-11 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. Each slice is a coded field. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Spatial direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields with spatial direct prediction. + +**Purpose:** Check that the decoder handles B slices of coded fields with spatial direct prediction. + +#### 6.6.5.12 Test bitstream AVCFI-12 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. The number of motion vectors per two consecutive MBs is equal to the maximum value specified in item m in clause A.3.1 in ITU-T H.264 | ISO/IEC 14496-10. No intra, skip and direct MBs are included in P and B slices. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded fields. + +**Purpose:** Check that the decoder can properly decode slices of coded fields with maximum number of motion vectors per consecutive MBs. + +### 6.6.6 Test bitstreams – Frame/field coding + +#### 6.6.6.1 Test bitstream AVCPA-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 1. Spatial direct prediction is used for direct prediction. Each slice is either a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded frames/fields. + +**Purpose:** Check that the decoder can properly decode slices of coded frames and fields. + +#### 6.6.6.2 Test bitstream AVCPA-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Temporal direct prediction is used for direct prediction. Each slice is either a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded frames/fields. + +**Purpose:** Check that the decoder can properly decode slices of coded frames and fields. + +#### 6.6.6.3 Test bitstream AVCPA-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. Each slice is either a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Slices of coded frames/fields. + +**Purpose:** Check that the decoder can properly decode slices of coded frames and fields. + +### 6.6.7 Test bitstreams – Macroblock adaptive frame/field coding + +#### 6.6.7.1 Test bitstream AVCMA-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.7.2 Test bitstream AVCMA-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.7.3 Test bitstream AVCMA-3 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.7.4 Test bitstream AVCMA-4 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.7.5 Test bitstream AVCMA-5 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. `mb_adaptive_frame_field_coding` is equal to 1. `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some MBs. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.7.6 Test bitstream AVCMA-6 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. `mb_adaptive_frame_field_coding` is equal to 1. `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some MBs. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.7.7 Test bitstream AVCMA-7 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. Some slices are coded as a coded field. `mb_adaptive_frame_field_coding` is equal to 1 in the rest of the frames. `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some MBs. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding and slices of a coded field. + +**Purpose:** Check that the decoder can properly decode both slices of a coded frame with `mb_adaptive_frame_field_flag=1` and slices of a coded field. + +#### 6.6.7.8 Test bitstream AVCMA-8 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.7.9 Test bitstream AVCMA-9 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. The number of motion vectors per two consecutive MBs is equal to the maximum value specified in item m of clause A.3.1 in ITU-T H.264 | ISO/IEC 14496-10. No intra, skip and direct MBs are included in P and B slices. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1` and with maximum number of motion vectors per consecutive MBs. + +### 6.6.8 Test bitstreams – S picture + +#### 6.6.8.1 Test bitstream AVCSP-1 + +**Specification:** All slices are coded as I, P and SP slices. Each picture contains more than one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 1. `memory_management_operation` is set to 5 on SP slice. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of SP slices. + +**Purpose:** Check that the decoder can properly decode SP slices. + +#### 6.6.8.2 Test bitstream AVCSP-2 + +**Specification:** All slices are coded as I, P and SP slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 1. `memory_management_operation` is set to 5 on SP slice. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of SP slices. + +**Purpose:** Check that the decoder can properly decode SP slices with deblocking filter. + +### 6.6.9 Test bitstreams – Long sequence + +#### 6.6.9.1 Test bitstream AVCLS-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of picture order count for long sequence. + +**Purpose:** Check that the decoder can properly decode picture order count for long sequence. + +### 6.6.10 Test bitstreams – SEI/VUI + +#### 6.6.10.1 Test bitstream AVCSE-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. SEI (Buffering period SEI and Picture timing SEI with `pic_struct`) and VUI are included in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of SEI/VUI. + +**Purpose:** Check that the decoder can properly decode SEI/VUI. + +#### 6.6.10.2 Test bitstream AVCSE-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. SEI (Buffering period SEI and Picture timing SEI with `pic_struct`) and VUI are included in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of SEI/VUI. + +**Purpose:** Check that the decoder can properly decode SEI/VUI. + +#### 6.6.10.3 Test bitstream AVCSE-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. SEI (Buffering period SEI and Picture timing SEI with `pic_struct`) and VUI are included in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of SEI/VUI. + +**Purpose:** Check that the decoder can properly decode SEI/VUI. + +### 6.6.11 Test bitstreams – CABAC: Basic features + +#### 6.6.11.1 Test bitstream AVCCANL-1 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode I slices with CABAC parsing. + +#### 6.6.11.2 Test bitstream AVCCANL-2 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode I slices with CABAC parsing. + +#### 6.6.11.3 Test bitstream AVCCANL-3 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode P slices with CABAC parsing. + +#### 6.6.11.4 Test bitstream AVCCANL-4 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode B slices with CABAC parsing. + +#### 6.6.11.5 Test bitstream AVCCANL-5 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode I slices with CABAC parsing. + +#### 6.6.11.6 Test bitstream AVCCANL-6 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode I slices with CABAC parsing. + +#### 6.6.11.7 Test bitstream AVCCANL-7 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode P slices with CABAC parsing. + +#### 6.6.11.8 Test bitstream AVCCANL-8 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode B slices with CABAC parsing. + +#### 6.6.11.9 Test bitstream AVCCABA-1 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with the deblocking filter process enabled and CABAC. + +**Purpose:** Check that the decoder can properly decode I slices with CABAC parsing. + +#### 6.6.11.10 Test bitstream AVCCABA-2 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode P slices with CABAC parsing. + +#### 6.6.11.11 Test bitstream AVCCABA-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode B slices with CABAC parsing. + +#### 6.6.11.12 Test bitstream AVCCABA-4 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode P slices with CABAC parsing. + +#### 6.6.11.13 Test bitstream AVCCABA-5 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with the deblocking filter process enabled and CABAC. + +**Purpose:** Check that the decoder can properly decode I slices with CABAC parsing. + +#### 6.6.11.14 Test bitstream AVCCABA-6 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode P slices with CABAC parsing. + +#### 6.6.11.15 Test bitstream AVCCABA-7 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode B slices with CABAC parsing. + +#### 6.6.11.16 Test bitstream AVCCABA-8 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode B slices with CABAC parsing. + +### 6.6.12 Test bitstreams – CABAC: Initialization + +#### 6.6.12.1 Test bitstream AVCCAIN-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. `cabac_init_idc` is equal to 0, 1, or 2 at slice header. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Initialization of CABAC. + +**Purpose:** Check that the decoder can initialize CABAC with `cabac_init_idc=0, 1, or 2`. + +### 6.6.13 Test bitstreams – CABAC: MB QP Delta + +#### 6.6.13.1 Test bitstream AVCCAQP-1 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 1. `mb_qp_delta` is equal to non-zero value to change the quantizer scale at each MB. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices with `mb_qp_delta` not equal to 0. + +**Purpose:** Check that the decoder can properly decode I slices with `mb_qp_delta` not equal to 0. + +#### 6.6.13.2 Test bitstream AVCCAQP-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. Each slice has a different size. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `mb_qp_delta` is equal to non-zero value to change the quantizer scale at each MB. `disable_deblocking_filter_idc` is equal to 2. `chroma_qp_index_offset` is equal to non-zero value. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I, P, and B slices with `mb_qp_delta` not equal to 0. + +**Purpose:** Check that the decoder can properly decode I slices with `mb_qp_delta` not equal to 0, `disable_deblocking_filter_idc` equal to 2, and non-zero `chroma_qp_index_offset`. + +### 6.6.14 Test bitstreams – CABAC: Slice + +#### 6.6.14.1 Test bitstream AVCCASL-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. Each picture contains more than one slice. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of different slice types in a picture with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode different slice types in a picture with CABAC parsing. + +#### 6.6.14.2 Test bitstream AVCCASL-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. Slices with different slice types are included in a picture. Stored B slices are included in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of different slice types in a picture with CABAC parsing. + +**Purpose:** Check that the decoder can properly decode different slice types in a picture with CABAC parsing. + +### 6.6.15 Test bitstreams – CABAC: I\_PCM + +#### 6.6.15.1 Test bitstream AVCCAPCM-1 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `mb_type` is equal to I\_PCM at some Macroblocks. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of Macroblock with `mb_type` equal to I\_PCM. + +**Purpose:** Check that the decoder can properly decode Macroblock with `mb_type` equal to I\_PCM. + +#### 6.6.15.2 Test bitstream AVCCAPCM-2 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `mb_type` is equal to I\_PCM at some Macroblocks. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of Macroblock with `mb_type` equal to I\_PCM. + +**Purpose:** Check that the decoder can properly decode Macroblock with `mb_type` equal to I\_PCM. + +#### 6.6.15.3 Test bitstream AVCCAPCM-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. `mb_type` is equal to I\_PCM at some Macroblocks. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of Macroblock with `mb_type` equal to I\_PCM. + +**Purpose:** Check that the decoder can properly decode macroblocks with `mb_type` equal to I\_PCM. + +### 6.6.16 Test bitstreams – CABAC: Memory management control operation + +#### 6.6.16.1 Test bitstream AVCCAMR-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 1. Reference picture list reordering and memory management control operations are used. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. Each slice is a coded frame. `mb_adaptive_frame_field_coding` is equal to 1. VUI is included in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. + +#### 6.6.16.2 Test bitstream AVCCAMR-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Reference picture list reordering and memory management control operations are used. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. + +### 6.6.17 Test bitstreams – CABAC: Weighted sample prediction process + +#### 6.6.17.1 Test bitstream AVCCAWP-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. `weighted_pred_flag` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Weighted sample prediction process for P slices. + +**Purpose:** Check that the decoder handles weighted sample prediction for P slices. + +#### 6.6.17.2 Test bitstream AVCCAWP-2 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. `weighted_pred_flag` is equal to 1. Plural reference indices are assigned to each reference picture. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Weighted sample prediction process for P slices with plural reference indices. + +**Purpose:** Check that the decoder handles weighted sample prediction for P slices with plural reference indexes. + +### 6.6.18 Test bitstreams – CABAC: Field coding + +#### 6.6.18.1 Test bitstream AVCCAFI-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. Each slice is a coded field. Stored B slices are included in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of coded fields. + +**Purpose:** Check that the decoder can properly decode slices of coded fields including stored B slices. + +#### 6.6.18.2 Test bitstream AVCCAFI-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of coded fields. + +**Purpose:** Check that the decoder can properly decode slices of coded fields. + +#### 6.6.18.3 Test bitstream AVCCAFI-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of coded fields. + +**Purpose:** Check that the decoder can properly decode slices of coded fields. + +### 6.6.19 Test bitstreams – CABAC: Frame/field decoding + +#### 6.6.19.1 Test bitstream AVCCAPA-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 1. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. Each slice is either a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Picture adaptive frame/field decoding. + +**Purpose:** Check that the decoder can properly decode slices of coded frames and fields with `direct_8x8_inference_flag=1`. + +#### 6.6.19.2 Test bitstream AVCCAPA-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. Each slice is either a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Picture adaptive frame/field decoding. + +**Purpose:** Check that the decoder can properly decode slices of coded frames and fields with `direct_8x8_inference_flag=1`. + +#### 6.6.19.3 Test bitstream AVCCAPA-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. Each slice is either a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Picture adaptive frame/field decoding. + +**Purpose:** Check that the decoder can properly decode slices of coded frames and fields with `direct_8x8_inference_flag=1`. + +### 6.6.20 Test bitstreams – Macroblock adaptive frame/field decoding + +#### 6.6.20.1 Test bitstream AVCCAMA-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.20.2 Test bitstream AVCCAMA-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.20.3 Test bitstream AVCCAMA-3 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `num_ref_frames` is equal to 1. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.20.4 Test bitstream AVCCAMA-4 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.20.5 Test bitstream AVCCAMA-5 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. mb\_adaptive\_frame\_field\_coding is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with mb\_adaptive\_frame\_field\_flag=1. + +#### 6.6.20.6 Test bitstream AVCCAMA-6 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Spatial direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is equal to 1. mb\_adaptive\_frame\_field\_coding is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with mb\_adaptive\_frame\_field\_flag=1. + +#### 6.6.20.7 Test bitstream AVCCAMA-7 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Temporal direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is equal to 1. mb\_adaptive\_frame\_field\_coding is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with mb\_adaptive\_frame\_field\_flag=1. + +#### 6.6.20.8 Test bitstream AVCCAMA-8 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Temporal direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is equal to 1. mb\_adaptive\_frame\_field\_coding is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with mb\_adaptive\_frame\_field\_flag=1. + +#### 6.6.20.9 Test bitstream AVCCAMA-9 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Temporal direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is equal to 1. mb\_adaptive\_frame\_field\_coding is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with mb\_adaptive\_frame\_field\_flag=1. + +#### 6.6.20.10 Test bitstream AVCCAMA-10 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. direct\_8x8\_inference\_flag is equal to 1. mb\_adaptive\_frame\_field\_coding is equal to 1. constrained\_intra\_pred\_flag is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can handle constrained intra prediction with mb\_adaptive\_frame\_field\_flag=1. + +#### 6.6.20.11 Test bitstream AVCCAMA-11 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `direct_8x8_inference_flag` is equal to 1. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. + +#### 6.6.20.12 Test bitstreams AVCCAMA-12 and AVCCAMA-13 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. The number of motion vectors per two consecutive MBs is equal to the maximum value specified in item m in clause A.3.1 in ITU-T H.264 | ISO/IEC 14496-10. No intra, skip and direct MBs are included in P and B slices. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1` and with maximum number of motion vectors per consecutive MBs. + +#### 6.6.20.13 Test bitstream AVCCAPAMA-1 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. Both coded frames and coded fields are included in the bitstream. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding and slices of a coded field. + +**Purpose:** Check that the decoder can properly decode both slices of a coded frame with `mb_adaptive_frame_field_flag=1` and slices of a coded field. + +#### 6.6.20.14 Test bitstream AVCCAPAMA-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. The first field of the first frame only contains I slice and the second field only contains P slice. `mb_adaptive_frame_field_coding` is equal to 1 in the rest of the frames. The indicated display of this bitstream is bottom field first. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding and slices of a coded field. + +**Purpose:** Check that the decoder can properly decode both slices of a coded frame with `mb_adaptive_frame_field_flag=1` and slices of a coded field. + +#### 6.6.20.15 Test bitstream AVCCAPAMA-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. The first field of the first frame only contains I slice and the second field only contains P slice. `mb_adaptive_frame_field_coding` is equal to 1 in the rest of the frames. The indicated display of this bitstream is top field first. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding and slices of a coded field. + +**Purpose:** Check that the decoder can properly decode both slices of a coded frame with `mb_adaptive_frame_field_flag=1` and slices of a coded field. + +#### 6.6.20.16 Test bitstream AVCCAPAMA-4 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. The first field of the first frame only contains I slice and the second field only contains P slice. `mb_adaptive_frame_field_coding` is equal to 1 in the rest of the frames. The indicated display of this bitstream is top field first. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding and slices of a coded field. + +**Purpose:** Check that the decoder can properly decode both slices of a coded frame with `mb_adaptive_frame_field_flag=1` and slices of a coded field. + +#### 6.6.20.17 Test bitstream AVCCAMV-1 + +**Specification:** The bitstream conforms to MP@L3. Frame size is 720x480. All slices are coded as I, P or B slices. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. In P slices, each macroblock is coded as sixteen 4x4 blocks. Each block has one motion vector in 1/4 sample position. In B slices, each macroblock is coded as eight 8x4 blocks. Each block has two motion vectors, one for list0 the other for list1. Both vectors are in 1/4 sample position. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Prediction bandwidth. + +**Purpose:** Check that the decoder handles the worst case of prediction bandwidth. Prediction bandwidth is at maximum due to largest number of motion vectors (in 1/4 sample position) per macroblock pair (32 as specified in standard). Non-integer position motion vectors require using 6-tap filter always. + +#### 6.6.20.18 Test bitstream AVCCVCANLMA-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. Both `entropy_coding_mode_flag` equal to 0, specifying the CAVLC parsing process, and `entropy_coding_mode_flag` equal to 1, specifying the CABAC parsing process are present within the bitstream. `pic_order_cnt_type` is equal to 0. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding using both CAVLC and CABAC. + +**Purpose:** Check that the decoder can properly decode slices with `mb_adaptive_frame_field_flag=1`. Check that the decoder can properly decode both CABAC and CAVLC. + +### 6.6.21 Test bitstreams – Fidelity Range Extensions: 4:2:0 8 bit + +#### 6.6.21.1 Test bitstreams FREH-1, FREH-28 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. Transform mode is set to 8x8 block size only. `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests loading of scaling list in the sequence parameter set and the picture parameter set. Tests 8x8 block size transform mode. Tests decoding of level prefix more than 16 bits in CAVLC entropy coding. Tests deblocking for 8x8 transform. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with 8x8 block size transform for CAVLC and check that scaling list is implemented correctly for frame only coding. + +#### 6.6.21.2 Test bitstreams FREH-2, FREH-29 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 0. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. Tests loading of scaling list in the sequence parameter set and the picture parameter set. Tests deblocking for 4x4 and 8x8 transform. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes and check that scaling list is implemented correctly for CABAC entropy coding for frame only coding. + +#### 6.6.21.3 Test bitstreams FREH-3, FREH-30 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. The value of cabac\_init\_idc is adaptively changed in slice header. Spatial direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. seq\_scaling\_matrix\_present\_flag is set to 1 and default scaling lists are used. Each slice is a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames and fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.4 Test bitstreams FREH-4, FREH-31 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. The value of cabac\_init\_idc is adaptively changed in slice header. pic\_order\_cnt\_type is equal to 0. Spatial direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. seq\_scaling\_matrix\_present\_flag is set to 1 and default scaling lists are used. Each slice is either a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames and fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.5 Test bitstreams FREH-5, FREH-32 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. The value of cabac\_init\_idc is adaptively changed in slice header. pic\_order\_cnt\_type is equal to 0. Spatial direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. seq\_scaling\_matrix\_present\_flag is set to 1 and default scaling lists are used. Each slice is a coded frame. mb\_adaptive\_frame\_field\_coding is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Macroblock adaptive frame field decoding and slices of a coded frame with both 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with mb\_adaptive\_frame\_field\_flag=1 and with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.6 Test bitstreams FREH-6, FREH-33 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Temporal direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is equal to 1. Transform mode is set to 8x8 block size only. seq\_scaling\_matrix\_present\_flag and pic\_scaling\_matrix\_flag are set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is either a coded frame or a coded field. mb\_adaptive\_frame\_field\_coding is equal to 1 in coded frames. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests loading of scaling list in the sequence parameter set and the picture parameter set. Tests 8x8 block size transform mode. Tests decoding of level prefix more than 16 bits in CAVLC entropy coding. Tests deblocking for 8x8 transform. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with 8x8 block size transform for CAVLC and check that scaling list is implemented correctly for both slices of a coded frame with mb\_adaptive\_frame\_field\_flag=1 and slices of a coded field. + +#### 6.6.21.7 Test bitstreams FREH-7, FREH-34 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is either a coded frame or a coded field. `mb_adaptive_frame_field_coding` is equal to 1 in coded frames. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. Tests loading of scaling list in the sequence parameter set and the picture parameter set. Tests deblocking for 4x4 and 8x8 transform. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes and check that scaling list is implemented correctly for CABAC entropy coding for both slices of a coded frame with `mb_adaptive_frame_field_flag=1` and slices of a coded field. + +#### 6.6.21.8 Test bitstream FREH-8 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix` are set to 0. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.9 Test bitstream FREH-9 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix` are set to 0. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.10 Test bitstream FREH-10 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix` are set to 0. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.11 Test bitstream FREH-11 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix` are set to 0. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.12 Test bitstreams FREH-12, FREH-39 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 0. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.13 Test bitstreams FREH-13, FREH-14, FREH-15 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.14 Test bitstream FREH-16 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. 8x8 block size transform mode is used. `seq_scaling_matrix_present_flag` is set to 1. Scaling lists are included in the sequence parameter set. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests loading of scaling list in the sequence parameter set. Tests 8x8 block size transform mode. + +**Purpose:** Check that a decoder can properly decode slices of a coded frame with 8x8 block size transform for CABAC. Check that scaling list is implemented correctly for frame only coding. Check that a decoder can handle temporal direct mode with `direct_8x8_inference_flag=1` for coded frames with 8x8 block size transform. + +#### 6.6.21.15 Test bitstream FREH-17 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. 8x8 block size transform mode is used. `seq_scaling_matrix_present_flag` is set to 1. Scaling lists are included in the sequence parameter set. Each slice is either a coded frame or a coded field. `mb_adaptive_frame_field_coding` is equal to 1 in coded frames. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests loading of scaling list in the sequence parameter set. Tests 8x8 block size transform mode. + +**Purpose:** Check that a decoder can properly decode slices of a coded frame with 8x8 block size transform for CABAC. Check that scaling list is implemented correctly for field coding and MBAFF. Check that a decoder can handle temporal direct mode with `direct_8x8_inference_flag=1` for coded frames with 8x8 block size transform. + +#### 6.6.21.16 Test bitstream FREH-18 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix` are set to 0. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CAVLC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.17 Test bitstream FREH-19 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix` are set to 0. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CAVLC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.18 Test bitstream FREH-20 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix` are set to 0. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CAVLC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.19 Test bitstream FREH-21 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix` are set to 0. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CAVLC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.20 Test bitstream FREH-22 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CAVLC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.21 Test bitstream FREH-23 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. Each slice is either a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CAVLC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.22 Test bitstream FREH-24 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. `mb_adaptive_frame_field_coding` is equal to 1. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CAVLC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.23 Test bitstream FREH-25 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1. Scaling lists are included in the sequence parameter set. Each slice is a coded frame. `chroma_format_idc` is equal to 0, specifying monochrome chroma format. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests monochrome chroma format in CAVLC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frame for monochrome chroma format. + +#### 6.6.21.24 Test bitstream FREH-26 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1. Scaling lists are included in the sequence parameter set. Each slice is a coded frame. `chroma_format_idc` is equal to 0, specifying monochrome chroma format. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests monochrome chroma format in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frame for monochrome chroma format. + +#### 6.6.21.25 Test bitstream FREH-27 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1. Scaling lists are included in the sequence parameter set. Each slice is a coded frame. `second_chroma_qp_index_offset` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests `second_chroma_qp_index_offset`. + +**Purpose:** Check that a decoder can properly decode slices of coded frame with `second_chroma_qp_index_offset`. + +#### 6.6.21.26 Test bitstream FREH-35 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.27 Test bitstream FREH-36 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.28 Test bitstream FREH-37 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.29 Test bitstream FREH-38 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Temporal direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded fields with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.30 Test bitstreams FREH-40, FREH-41 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 0. Reference picture list reordering and memory management control operations are used. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that a decoder handles reference picture list reordering and memory management control operations. + +#### 6.6.21.31 Test bitstream FREH-42 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 0. Reference picture list reordering and memory management control operations are used. `mb_adaptive_frame_field_coding` is equal to 1. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that a decoder handles reference picture list reordering and memory management control operations. + +#### 6.6.21.32 Test bitstream FREH-43 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 0. `mb_adaptive_frame_field_coding` is equal to 1. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CABAC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.33 Test bitstream FREH-44 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_flag` are set to 0. `mb_adaptive_frame_field_coding` is equal to 1. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Tests 4x4 and 8x8 block size transform modes in CAVLC entropy coding. + +**Purpose:** Check that a decoder can properly decode slices of coded frames with both 4x4 and 8x8 block size transform modes. + +#### 6.6.21.34 Test bitstream FREH-45 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is set equal to 1. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and `pic_scaling_matrix_flag` is set to 0. Memory management control operations are used. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Memory management control operations. + +**Purpose:** Check that a decoder handles memory management control operations. + +### 6.6.22 Test bitstreams – Fidelity Range Extensions: 4:2:0 10 bit + +#### 6.6.22.1 Test bitstream FREH10-1 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. `frame_mbs_only_flag` is equal to 1. `chroma_format_idc` is equal to 1. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices for 4:2:0 10-bit. + +**Purpose:** Check that a decoder can properly decode I slices for 4:2:0 10-bit. + +#### 6.6.22.2 Test bitstream FREH10-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. `frame_mbs_only_flag` is equal to 1. `chroma_format_idc` is equal to 1. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I, P, and B slices for 4:2:0 10-bit. + +**Purpose:** Check that a decoder can properly decode I, P and B slices for 4:2:0 10-bit. + +### 6.6.23 Test bitstreams – Fidelity Range Extensions: 4:2:2 + +#### 6.6.23.1 Test bitstream FREH422-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. chroma\_format\_idc is equal to 2, specifying 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are set equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode P slices for 4:2:2 8 bit. + +#### 6.6.23.2 Test bitstream FREH422-2 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Direct prediction is not used in this bitstream. chroma\_format\_idc is equal to 2, specifying 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are set equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode B slices for 4:2:2 8 bit. + +#### 6.6.23.3 Test bitstream FREH422-3 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. chroma\_format\_idc is equal to 2, specifying 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are set equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode P slices with deblocking filter for 4:2:2 8 bit. + +#### 6.6.23.4 Test bitstream FREH422-4 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. chroma\_format\_idc is equal to 2, specifying 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are set equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode I slices for 4:2:2 8 bit without deblocking filter. + +#### 6.6.23.5 Test bitstream FREH422-5 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. chroma\_format\_idc is equal to 2, specifying 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are set equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode P slices for 4:2:2 8 bit without deblocking filter. + +#### 6.6.23.6 Test bitstream FREH422-6 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Spatial direct prediction is used for direct prediction. direct\_8x8\_inference\_flag is equal to 1. chroma\_format\_idc is equal to 2, specifying 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are set equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode B slices for 4:2:2 8 bit without deblocking filter. + +#### 6.6.23.7 Test bitstream FREH422-7 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode P slices for 4:2:2 8 bit with deblocking filter. + +#### 6.6.23.8 Test bitstream FREH422-8 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode I slices for 4:2:2 10 bit without deblocking filter. + +#### 6.6.23.9 Test bitstream FREH422-9 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode P slices for 4:2:2 10 bit without deblocking filter. + +#### 6.6.23.10 Test bitstream FREH422-10 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 1. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode B slices for 4:2:2 10 bit without deblocking filter. + +#### 6.6.23.11 Test bitstream FREH422-11 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode P slices for 4:2:2 10 bit with deblocking filter. + +#### 6.6.23.12 Test bitstream FREH422-12 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 0. Both 4x4 and 8x8 block size + +transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode I slices for 4:2:2 8 bit without deblocking filter. + +#### 6.6.23.13 Test bitstream FREH422-13 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 0. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode P slices for 4:2:2 8 bit without deblocking filter. + +#### 6.6.23.14 Test bitstream FREH422-14 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_Filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 0. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices for 4:2:2 8 bit. + +**Purpose:** Check that a decoder can properly decode B slices for 4:2:2 8 bit without deblocking filter. + +#### 6.6.23.15 Test bitstream FREH422-15 + +**Specification:** All slices are coded as I slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode I slices for 4:2:2 10 bit without deblocking filter. + +#### 6.6.23.16 Test bitstream FREH422-16 + +**Specification:** All slices are coded as I or P slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of P slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode P slices for 4:2:2 10 bit without deblocking filter. + +#### 6.6.23.17 Test bitstream FREH422-17 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. Both 4x4 and 8x8 + +block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1 and default scaling lists are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode B slices for 4:2:2 10 bit without deblocking filter. + +#### 6.6.23.18 Test bitstream FREH422-18 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode B slices of coded fields for 4:2:2 10 bit. + +#### 6.6.23.19 Test bitstream FREH422-19 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is a coded frame. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode B slices of coded frames for 4:2:2 10 bit. + +#### 6.6.23.20 Test bitstream FREH422-20 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is either a coded frame or a coded field. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode B slices of coded frames and fields for 4:2:2 10 bit. + +#### 6.6.23.21 Test bitstream FREH422-21 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains only one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Spatial direct prediction is used for direct prediction. `direct_8x8_inference_flag` is equal to 0. `chroma_format_idc` is equal to 2, specifying 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are set equal to 2, specifying 10 bit video. Both 4x4 and 8x8 block size transform modes are used. `seq_scaling_matrix_present_flag` is set to 1. Scaling lists are included in the sequence parameter set and the picture parameter set. Each slice is a coded frame. `mb_adaptive_frame_field_coding` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of B slices for 4:2:2 10 bit. + +**Purpose:** Check that a decoder can properly decode B slices with `mb_adaptive_frame_field_flag=1` for 4:2:2 10 bit. + +### 6.6.24 Auxiliary coded picture + +#### 6.6.24.1 Test bitstream FREAUX-1 + +**Specification:** Coded slices of an auxiliary coded picture are included in this bitstream. The rest of the slices are coded as either an I slice or a P slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of coded slices of an auxiliary coded picture. + +**Purpose:** Check that the decoder can properly handle coded slices of an auxiliary coded picture. + +### 6.6.25 Test bitstreams – Professional Profiles: High 4:4:4 Predictive Profile + +#### 6.6.25.1 Test bitstream PPH444P-1 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma sample bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I and P slices for 4:4:4 14 bit frames with `separate_colour_plane_flag` equal to 0, using CAVLC. + +**Purpose:** Check that a decoder can properly decode I and P slices of 4:4:4 14 bit coded frames with `separate_colour_plane_flag` equal to 0, using CAVLC. + +#### 6.6.25.2 Test bitstream PPH444P-2 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma sample bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I and P slices for 4:4:4 14 bit frames with `separate_colour_plane_flag` equal to 0, using CABAC. + +**Purpose:** Check that a decoder can properly decode I and P slices of 4:4:4 14 bit coded frames with `separate_colour_plane_flag` equal to 0, using CABAC. + +#### 6.6.25.3 Test bitstream PPH444P-3 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma sample bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I, P and B slices for 4:4:4 14 bit frames with `separate_colour_plane_flag` equal to 0, using CAVLC. + +**Purpose:** Check that a decoder can properly decode I, P and B slices of 4:4:4 14 bit coded frames with `separate_colour_plane_flag` equal to 0, using CAVLC. + +#### 6.6.25.4 Test bitstream PPH444P-4 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma sample bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I, P and B slices for 4:4:4 14 bit frames with `separate_colour_plane_flag` equal to 0, using CABAC. + +**Purpose:** Check that a decoder can properly decode I, P and B slices of 4:4:4 14 bit coded frames with separate\_colour\_plane\_flag equal to 0, using CABAC. + +#### 6.6.25.5 Test bitstream PPH444P-5 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma sample bit depths. separate\_colour\_plane\_flag is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I, P and B slices for 4:4:4 14 bit frames with separate\_colour\_plane\_flag equal to 0, without deblocking filter. + +**Purpose:** Check that a decoder can properly decode I, P and B slices of 4:4:4 14 bit coded frames with separate\_colour\_plane\_flag equal to 0, without deblocking filter. + +#### 6.6.25.6 Test bitstream PPH444P-6 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma sample bit depths. separate\_colour\_plane\_flag is equal to 1. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I and P slices for 4:4:4 14 bit frames with separate\_colour\_plane\_flag equal to 1, using CAVLC. + +**Purpose:** Check that a decoder can properly decode I and P slices of coded frames for 14 bit 4:4:4 coded frames with separate\_colour\_plane\_flag equal to 1, using CAVLC. + +#### 6.6.25.7 Test bitstream PPH444P-7 + +**Specification:** All slices are coded as I or P slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma sample bit depths. separate\_colour\_plane\_flag is equal to 1. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I and P slices for 4:4:4 14 bit frames with separate\_colour\_plane\_flag equal to 1, using CABAC. + +**Purpose:** Check that a decoder can properly decode I and P slices of 4:4:4 14 bit coded frames with separate\_colour\_plane\_flag equal to 1, using CABAC. + +#### 6.6.25.8 Test bitstream PPH444P-8 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma sample bit depths. separate\_colour\_plane\_flag is equal to 1. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I, P and B slices for 4:4:4 14 bit frames with separate\_colour\_plane\_flag equal to 1, using CAVLC. + +**Purpose:** Check that a decoder can properly decode I, P and B slices of 4:4:4 14 bit coded frames with separate\_colour\_plane\_flag equal to 1, using CAVLC. + +#### 6.6.25.9 Test bitstream PPH444P-9 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma sample bit depths. separate\_colour\_plane\_flag is equal to 1. pic\_order\_cnt\_type is + +equal to 0. `direct_8x8_inference_flag` is equal to 1. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I, P and B slices for 4:4:4 14 bit frames with `separate_colour_plane_flag` equal to 1, using CABAC. + +**Purpose:** Check that a decoder can properly decode I, P and B slices of 4:4:4 14 bit coded frames with `separate_colour_plane_flag` equal to 1, using CABAC. + +#### 6.6.25.10 Test bitstream PPH444P-10 + +**Specification:** All slices are coded as I, P or B slices. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma sample bit depths. `qpprime_y_zero_transform_bypass_flag` is equal to 1, specifying transform-bypass coding for macroblocks having $QP'_Y$ equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of I, P and B slices for 4:4:4 14 bit frames with `qpprime_y_zero_transform_bypass_flag` equal to 1. + +**Purpose:** Check that a decoder can properly decode I, P and B slices of 4:4:4 14 bit coded frames with `qpprime_y_zero_transform_bypass_flag` equal to 1. + +### 6.6.26 Test bitstreams – Professional Profiles: High 10 Intra Profile + +#### 6.6.26.1 Test bitstream PPH10I-1 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `chroma_format_idc` is equal to 1, specifying the 4:2:0 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 2, specifying 10 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:0 10 bit IDR frames with `separate_colour_plane_flag` equal to 0, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:2:0 10 bit IDR frames with `separate_colour_plane_flag` equal to 0, using CAVLC. + +#### 6.6.26.2 Test bitstream PPH10I-2 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 1, specifying the 4:2:0 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 2, specifying 10 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:0 10 bit IDR frames with `separate_colour_plane_flag` equal to 0, using CABAC. + +**Purpose:** Check that a decoder can properly decode 4:2:0 10 bit IDR frames with `separate_colour_plane_flag` equal to 0, using CABAC. + +#### 6.6.26.3 Test bitstream PPH10I-3 + +**Specification:** All pictures are IDR pictures. `deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 1, specifying the 4:2:0 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 2, specifying 10 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:0 10 bit IDR frames with `separate_colour_plane_flag` equal to 0, using CABAC. + +**Purpose:** Check that a decoder can properly decode 4:2:0 10 bit IDR frames with `separate_colour_plane_flag` equal to 0, using CABAC. + +#### 6.6.26.4 Test bitstream PPH10I-4 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `chroma_format_idc` is equal to 1, specifying the 4:2:0 chroma format. + +Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 2, specifying 10 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Some pictures are coded frames and some are coded fields. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:0 10 bit IDR frames and fields with `separate_colour_plane_flag` equal to 0, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:2:0 10 bit IDR frames and fields with `separate_colour_plane_flag` equal to 0, using CAVLC. + +#### 6.6.26.5 Test bitstream PPH10I-5 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 1, specifying the 4:2:0 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 2, specifying 10 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Some pictures are coded frames and some are coded fields. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:0 10 bit IDR frames and fields with `separate_colour_plane_flag` equal to 0, using CABAC. + +**Purpose:** Check that a decoder can properly decode 4:2:0 10 bit IDR frames and fields with `separate_colour_plane_flag` equal to 0, using CABAC. + +#### 6.6.26.6 Test bitstream PPH10I-6 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `chroma_format_idc` is equal to 1, specifying the 4:2:0 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 2, specifying 10 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame with `mb_adaptive_frame_field_flag` equal to 1. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:0 10 bit IDR frames with macroblock adaptive frame/field coding. + +**Purpose:** Check that a decoder can properly decode 4:2:0 10 bit IDR frames with macroblock adaptive frame/field coding. + +#### 6.6.26.7 Test bitstream PPH10I-7 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 1, specifying the 4:2:0 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 2, specifying 10 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame with `mb_adaptive_frame_field_flag` equal to 1. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:0 10 bit IDR frames with macroblock adaptive frame/field coding. + +**Purpose:** Check that a decoder can properly decode 4:2:0 10 bit IDR frames with macroblock adaptive frame/field coding. + +### 6.6.27 Test bitstreams – Professional Profiles: High 4:2:2 Intra Profile + +#### 6.6.27.1 Test bitstream PPH422I-1 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `chroma_format_idc` is equal to 2, specifying the 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 2, specifying 10 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:2 10 bit IDR frames with `separate_colour_plane_flag` equal to 0, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:2:2 10 bit IDR frames with `separate_colour_plane_flag` equal to 0, using CAVLC. + +#### 6.6.27.2 Test bitstream PPH422I-2 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 2, specifying the 4:2:2 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 2, specifying 10 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:2 10 bit IDR frames with separate\_colour\_plane\_flag equal to 0, using CABAC. + +**Purpose:** Check that a decoder can properly decode 4:2:2 10 bit IDR frames with separate\_colour\_plane\_flag equal to 0, using CABAC. + +#### 6.6.27.3 Test bitstream PPH4221-3 + +**Specification:** All pictures are IDR pictures. deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. chroma\_format\_idc is equal to 2, specifying the 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 2, specifying 10 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:2 10 bit IDR frames with separate\_colour\_plane\_flag equal to 0, using CABAC. + +**Purpose:** Check that a decoder can properly decode 4:2:2 10 bit IDR frames with separate\_colour\_plane\_flag equal to 0, using CABAC. + +#### 6.6.27.4 Test bitstream PPH4221-4 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 2, specifying the 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 2, specifying 10 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 0. Some pictures are coded frames and some are coded fields. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:2 10 bit IDR frames and fields with separate\_colour\_plane\_flag equal to 0, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:2:2 10 bit IDR frames and fields with separate\_colour\_plane\_flag equal to 0, using CAVLC. + +#### 6.6.27.5 Test bitstream PPH4221-5 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. chroma\_format\_idc is equal to 2, specifying the 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 2, specifying 10 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 0. Some pictures are coded frames and some are coded fields. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:2 10 bit IDR frames and fields with separate\_colour\_plane\_flag equal to 0, using CABAC. + +**Purpose:** Check that a decoder can properly decode 4:2:2 10 bit IDR frames and fields with separate\_colour\_plane\_flag equal to 0, using CABAC. + +#### 6.6.27.6 Test bitstream PPH4221-6 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 2, specifying the 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 2, specifying 10 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 0. Each picture is a coded frame with mb\_adaptive\_frame\_field\_flag equal to 1. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:2 10 bit IDR frames with macroblock adaptive frame/field coding. + +**Purpose:** Check that a decoder can properly decode 4:2:2 10 bit IDR frames with macroblock adaptive frame/field coding. + +#### 6.6.27.7 Test bitstream PPH4221-7 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. chroma\_format\_idc is equal to 2, specifying the 4:2:2 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 2, specifying 10 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 0. Each picture is a coded frame with mb\_adaptive\_frame\_field\_flag equal to 1. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:2:2 10 bit IDR frames with macroblock adaptive frame/field coding. + +**Purpose:** Check that a decoder can properly decode 4:2:2 10 bit IDR frames with macroblock adaptive frame/field coding. + +### 6.6.28 Test bitstreams – Professional Profiles: High 4:4:4 Intra Profile + +#### 6.6.28.1 Test bitstream PPH444I-1 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with `separate_colour_plane_flag` equal to 0. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with `separate_colour_plane_flag` equal to 0. + +#### 6.6.28.2 Test bitstream PPH444I-2 + +**Specification:** All pictures are IDR pictures. `deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with `separate_colour_plane_flag` equal to 0, without deblocking filter. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with `separate_colour_plane_flag` equal to 0, without deblocking filter. + +#### 6.6.28.3 Test bitstream PPH444I-3 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 0. Both `seq_scaling_matrix_present_flag` and `pic_scaling_matrix_present_flag` are equal to 1. A different scaling matrix is applied to each colour plane. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with `separate_colour_plane_flag` equal to 0, applying a different scaling matrix for each colour plane. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with `separate_colour_plane_flag` equal to 0, applying a different scaling matrix for each colour plane. + +#### 6.6.28.4 Test bitstream PPH444I-4 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 1. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with `separate_colour_plane_flag` equal to 1. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with `separate_colour_plane_flag` equal to 1. + +#### 6.6.28.5 Test bitstream PPH444I-5 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `chroma_format_idc` is equal to 3, specifying the 4:4:4 chroma format. Both `bit_depth_luma_minus8` and `bit_depth_chroma_minus8` are equal to 6, specifying 14 bit luma and chroma bit depths. `separate_colour_plane_flag` is equal to 1. `seq_scaling_matrix_present_flag` is equal to 1 and `pic_scaling_matrix_present_flag` is equal to 0. A different scaling matrix is applied to each colour plane. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with `separate_colour_plane_flag` equal to 1, applying a different scaling matrix for each colour plane. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 1, applying a different scaling matrix for each colour plane. + +#### 6.6.28.6 Test bitstream PPH444I-6 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. Slices having different values of colour\_plane\_id are interleaved with each other. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 1. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 1, using slice-level interleaving of colour\_plane\_id values within an access unit. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 1, using slice-level interleaving of colour\_plane\_id values within an access unit. + +#### 6.6.28.7 Test bitstream PPH444I-7 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma bit depths. qpprime\_y\_zero\_transform\_bypass\_flag is equal to 1, specifying transform-bypass coding for macroblocks having QP'y equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with qpprime\_y\_zero\_transform\_bypass\_flag equal to 1. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with qpprime\_y\_zero\_transform\_bypass\_flag equal to 1. + +### 6.6.29 Test bitstreams – Professional Profiles: CAVLC 4:4:4 Intra Profile + +#### 6.6.29.1 Test bitstream PPCV444I-1 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 0, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 0, using CAVLC. + +#### 6.6.29.2 Test bitstream PPCV444I-2 + +**Specification:** All pictures are IDR pictures. deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 0, without deblocking filter, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 0, without deblocking filter, using CAVLC. + +#### 6.6.29.3 Test bitstream PPCV444I-3 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 0. Both seq\_scaling\_matrix\_present\_flag and pic\_scaling\_matrix\_present\_flag are + +equal to 1. A different scaling matrix is applied to each colour plane. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 0, applying a different scaling matrix for each colour plane, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 0, applying a different scaling matrix for each colour plane, using CAVLC. + +#### 6.6.29.4 Test bitstream PPCV444I-4 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 1. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 1, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 1, using CAVLC. + +#### 6.6.29.5 Test bitstream PPCV444I-5 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 1. seq\_scaling\_matrix\_present\_flag is equal to 1 and pic\_scaling\_matrix\_present\_flag is equal to 0. A different scaling matrix is applied to each colour plane. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 1, applying a different scaling matrix for each colour plane, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 1, applying a different scaling matrix for each colour plane, using CAVLC. + +#### 6.6.29.6 Test bitstream PPCV444I-6 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. Slices having different values of colour\_plane\_id are interleaved with each other. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma bit depths. separate\_colour\_plane\_flag is equal to 1. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 1, using slice-level interleaving of colour\_plane\_id values within an access unit, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with separate\_colour\_plane\_flag equal to 1, using slice-level interleaving of colour\_plane\_id values within an access unit, using CAVLC. + +#### 6.6.29.7 Test bitstream PPCV444I-7 + +**Specification:** All pictures are IDR pictures. Each picture contains more than one slice. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. chroma\_format\_idc is equal to 3, specifying the 4:4:4 chroma format. Both bit\_depth\_luma\_minus8 and bit\_depth\_chroma\_minus8 are equal to 6, specifying 14 bit luma and chroma bit depths. qpprime\_y\_zero\_transform\_bypass\_flag is equal to 1, specifying transform-bypass coding for macroblocks having QP'y equal to 0. Each picture is a coded frame. The NAL units are encapsulated in the byte stream format specified in Annex B of ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of 4:4:4 14 bit IDR frames with qpprime\_y\_zero\_transform\_bypass\_flag equal to 1, using CAVLC. + +**Purpose:** Check that a decoder can properly decode 4:4:4 14 bit IDR frames with qpprime\_y\_zero\_transform\_bypass\_flag equal to 1, using CAVLC. + +### 6.6.30 Test bitstreams – SVC Profiles: Scalable Baseline Profile 4:2:0 8 bit + +#### 6.6.30.1 Test bitstream SVCBC-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0 for layer representations with dependency\_id equal to 0, specifying the CAVLC parsing process; and entropy\_coding\_mode\_flag is equal to 1 for layer representations with dependency\_id equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1 for layer representations with dependency\_id equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 1, TemporalIdMax is equal to 4 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. use\_ref\_base\_pic\_flag is equal to 0, specifying that reference base pictures are not used as reference pictures for the inter prediction process. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 0 and store\_ref\_base\_pic\_flag is equal to 0, specifying that the reference base picture are not stored. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying that inter-layer motion and inter-layer intra prediction are enabled. adaptive\_motion\_prediction\_flag is equal to 1, specifying that inter-layer motion prediction is enabled. adaptive\_residual\_prediction\_flag is equal to 1, specifying that inter-layer residual prediction is enabled. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of a quality enhancement layer, 8x8 transform size with inter-layer motion, intra and residual prediction and CABAC parsing. + +**Purpose:** Check that the decoder can properly handle gaps in frame\_num, reference picture list reordering, memory management control operations and EI, EP and EB coded slices of a quality enhancement layer, 8x8 transform size with inter-layer motion, intra and residual prediction and CABAC parsing. + +#### 6.6.30.2 Test bitstream SVCBM-1 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. DependencyIdMax is equal to 0, TemporalIdMax is equal to 0, and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 0, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 0 (with default\_base\_mode\_flag equal to 1), adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a quality enhancement layer. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a quality enhancement layer. + +#### 6.6.30.3 Test bitstream SVCBM-2 + +**Specification:** All slices are coded as I, P, EI or EP slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. DependencyIdMax is equal to 0, TemporalIdMax is equal to 0 and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. adaptive\_tcoeff\_level\_prediction\_flag is equal to 0, specifying that an alternative inter-layer prediction process is applied for the whole sequence. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. default\_base\_mode\_flag is equal to 1, specifying inter-layer motion and intra prediction. default\_residual\_prediction\_flag is equal to 0. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a quality enhancement layer, using an alternative inter-layer prediction process for translation to an AVC bitstream. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a quality enhancement layer, using an alternative inter-layer prediction process for translation to an AVC bitstream. + +#### 6.6.30.4 Test bitstream SVCBM-3 + +**Specification:** All slices are coded as I, P or EP slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. DependencyIdMax is equal to 0, TemporalIdMax is equal to 0 and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. tcoeff\_level\_prediction\_flag is equal to 1, specifying that an alternative inter-layer prediction process is applied on a macroblock basis. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. default\_base\_mode\_flag is equal to 1, specifying inter-layer motion and intra prediction. default\_residual\_prediction\_flag is equal to 0. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a quality enhancement layer, enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a quality enhancement layer, enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream. + +#### 6.6.30.5 Test bitstream SVCBM-4 + +**Specification:** All slices are coded as I, P, EI or EP slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. DependencyIdMax is equal to 0, TemporalIdMax is equal to 0 and DQIdMax is equal to 2. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. tcoeff\_level\_prediction\_flag is equal to 1 for the layer representation with quality\_id equal to 1, specifying that an alternative inter-layer prediction process is applied on a macroblock basis. For the layer representation with quality\_id equal to 2 tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. default\_base\_mode\_flag is equal to 1, specifying inter-layer motion and intra prediction. default\_residual\_prediction\_flag is equal to 0. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a quality enhancement layer and of a quality enhancement layer enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a quality enhancement layer and of a quality enhancement layer enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream. + +#### 6.6.30.6 Test bitstream SVCBM-5 + +**Specification:** All slices are coded as I, P, EI, or EP slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0 for layer representations with quality\_id equal to 0, specifying the CAVLC parsing process. entropy\_coding\_mode\_flag is equal to 1 for layer representations with quality\_id greater than 0, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1 for layer representation with quality\_id greater than 0, specifying that 8x8 transform decoding process may be in use. mb\_qp\_delta is equal to 0. DependencyIdMax is equal to 0, TemporalIdMax is equal to 4 and DQIdMax is equal to 3. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. use\_ref\_base\_pic\_flag is equal to 1 for access units with temporal\_id equal to 0, specifying that reference base pictures may be used as reference pictures for the inter prediction process. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 0 and store\_ref\_base\_pic\_flag is equal to 1 for access units with temporal\_id equal to 0, specifying that reference base pictures are stored for these access units. slice\_skip\_flag is equal to 0. default\_base\_mode\_flag is equal to 1 for layer representations with quality\_id greater than 1, specifying inter-layer motion and intra prediction. default\_residual\_prediction\_flag is equal to 1 for layer representations with quality\_id greater than 1. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI and EP slices of quality enhancement layers, using key pictures and transform coefficient fragmentation, 8x8 transform size with inter-layer motion and intra prediction. + +**Purpose:** Check that the decoder can properly handle gaps in frame\_num, reference picture list reordering, memory management control operations and EI and EP coded slices of quality enhancement layers, using key pictures and transform coefficient fragmentation, 8x8 transform size with inter-layer motion and intra prediction. + +#### 6.6.30.7 Test bitstream SVCBCT-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 0 for layer representation with dependency\_id equal to 0, specifying the CAVLC parsing process, and entropy\_coding\_mode\_flag is equal to 1 for layer representation with dependency\_id equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1 for layer representation with dependency\_id equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 1, TemporalIdMax is equal to 4 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. use\_ref\_base\_pic\_flag is equal to 1, specifying that reference base pictures are not used as reference pictures for the inter prediction process. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 0 and store\_ref\_base\_pic\_flag is equal to 0, specifying that reference base picture are not stored. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying that inter-layer motion and inter-layer intra prediction is enabled. adaptive\_motion\_prediction\_flag is equal to 1, specifying that inter-layer motion prediction is enabled. adaptive\_residual\_prediction\_flag is equal to 1, specifying that inter-layer residual prediction is enabled. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of a quality and temporal enhancement layer, 8x8 transform size with inter-layer motion, intra and residual prediction and CABAC parsing. + +**Purpose:** Check that the decoder can properly handle gaps in frame\_num, reference picture list reordering, memory management control operations and EI, EP and EB coded slices of a quality and temporal enhancement layer, 8x8 transform size with inter-layer motion, intra and residual prediction and CABAC parsing. + +#### 6.6.30.8 Test bitstream SVCBMT-1 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering is used. DependencyIdMax is equal to 0, TemporalIdMax is equal to 3, and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 0, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 0 (with default\_base\_mode\_flag equal to 1), adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and decoding of EI and EP coded slices of a quality enhancement layer. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering and EI and EP coded slices of a quality enhancement layer. + +#### 6.6.30.9 Test bitstream SVCBMT-2 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. DependencyIdMax is equal to 0, TemporalIdMax is equal to 3, and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 0, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 0 (with default\_base\_mode\_flag equal to 1), adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer. + +#### 6.6.30.10 Test bitstream SVCBMT-3 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. `DependencyIdMax` is equal to 0, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 1. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 0, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 0 (with `default_base_mode_flag` equal to 1), `adaptive_motion_prediction_flag` is equal to 0 (with `default_motion_prediction_flag` equal to 1), and `adaptive_residual_prediction_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`. + +#### 6.6.30.11 Test bitstream SVCBMT-4 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 2, specifying enabling of deblocking filter process (without slice boundary deblocking). Additionally, `slice_alpha_c0_offset_div2` and `slice_beta_offset_div2` are not equal to 0. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. `DependencyIdMax` is equal to 0, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 1. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 0, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 0 (with `default_base_mode_flag` equal to 1), `adaptive_motion_prediction_flag` is equal to 0 (with `default_motion_prediction_flag` equal to 1), and `adaptive_residual_prediction_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter. + +#### 6.6.30.12 Test bitstream SVCBMT-5 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice and slice groups greater than 1. `disable_deblocking_filter_idc` is equal to 2, specifying enabling of deblocking filter process (without slice boundary deblocking). Additionally, `slice_alpha_c0_offset_div2` and `slice_beta_offset_div2` are not equal to 0. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 0. Reference picture list reordering is used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. `DependencyIdMax` is equal to 0, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 1. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 0, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 0 (with `default_base_mode_flag` equal to 1), `adaptive_motion_prediction_flag` is equal to 0 (with `default_motion_prediction_flag` equal to 1), and `adaptive_residual_prediction_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter and slice groups. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter and slice groups. + +#### 6.6.30.13 Test bitstream SVCBMT-6 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 2, specifying enabling of deblocking filter process (without slice boundary deblocking). Additionally, slice\_alpha\_c0\_offset\_div2 and slice\_beta\_offset\_div2 are not equal to 0. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering is used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. DependencyIdMax is equal to 0, TemporalIdMax is equal to 3, and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 0, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 1 (with adaptive\_tcoeff\_level\_prediction\_flag equal to 0). slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 0 (with default\_base\_mode\_flag equal to 1), adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer, using an alternative inter-layer prediction process for translation to an AVC bitstream, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer, using an alternative inter-layer prediction process for translation to an AVC bitstream, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter. + +#### 6.6.30.14 Test bitstream SVCBMT-7 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 2, specifying enabling of deblocking filter process (without slice boundary deblocking). Additionally, slice\_alpha\_c0\_offset\_div2 and slice\_beta\_offset\_div2 are not equal to 0. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering is used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. DependencyIdMax is equal to 0, TemporalIdMax is equal to 3, and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 0, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 1 (with adaptive\_tcoeff\_level\_prediction\_flag equal to 1). slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 0 (with default\_base\_mode\_flag equal to 1), adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer, enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer, enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter. + +#### 6.6.30.15 Test bitstream SVCBMT-8 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 2, specifying enabling of deblocking filter process (without slice boundary deblocking). Additionally, `slice_alpha_c0_offset_div2` and `slice_beta_offset_div2` are not equal to 0. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `chroma_qp_index_offset` is not equal to 0. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. `DependencyIdMax` is equal to 0, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 1. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 0, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 0 (with `default_base_mode_flag` equal to 1), `adaptive_motion_prediction_flag` is equal to 0 (with `default_motion_prediction_flag` equal to 1), and `adaptive_residual_prediction_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter, and non-zero `chroma_qp_index_offset`. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter, and non-zero `chroma_qp_index_offset`. + +#### 6.6.30.16 Test bitstream SVCBMT-9 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 2, specifying enabling of deblocking filter process (without slice boundary deblocking). Additionally, `slice_alpha_c0_offset_div2` and `slice_beta_offset_div2` are not equal to 0. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. `DependencyIdMax` is equal to 0, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 1. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 0, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 0 (with `default_base_mode_flag` equal to 1), `adaptive_motion_prediction_flag` is equal to 0 (with `default_motion_prediction_flag` equal to 1), and `adaptive_residual_prediction_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter with CABAC parsing. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter with CABAC parsing. + +#### 6.6.30.17 Test bitstream SVCBMT-10 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 2, specifying enabling of deblocking filter process (without slice boundary deblocking). Additionally, `slice_alpha_c0_offset_div2` and `slice_beta_offset_div2` are not equal to 0. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. `DependencyIdMax` is equal to 0, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 1. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 0, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP skipped slices of a quality enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP skipped slices of a quality enhancement layer with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter. + +#### 6.6.30.18 Test bitstream SVCBMT-11 + +**Specification:** All slices are coded as I, P, EI or EP slices. The first frame and some other frames are coded as IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 2, specifying enabling of deblocking filter process (without slice boundary deblocking). Additionally, slice\_alpha\_c0\_offset\_div2 and slice\_beta\_offset\_div2 are not equal to 0. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. DependencyIdMax is equal to 0, TemporalIdMax is equal to 3, and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 0, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 0 (with default\_base\_mode\_flag equal to 1), adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter and more than one IDR. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter and more than one IDR. + +#### 6.6.30.19 Test bitstream SVCBMT-12 + +**Specification:** All slices are coded as I, P, EI or EP slices. The first frame and some other frames are coded as IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 2, specifying enabling of deblocking filter process (without slice boundary deblocking). Additionally, slice\_alpha\_c0\_offset\_div2 and slice\_beta\_offset\_div2 are not equal to 0. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. DependencyIdMax is equal to 0, TemporalIdMax is equal to 3, and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 0, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. use\_ref\_base\_pic\_flag is equal to 1 and store\_ref\_base\_pic\_flag is equal to 1. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 0 (with default\_base\_mode\_flag equal to 1), adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of a quality enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter, more than one IDR and key pictures. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of a quality enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter, more than one IDR and key pictures. + +#### 6.6.30.20 Test bitstream SVCBMT-13 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering is used. DependencyIdMax is equal to 0, TemporalIdMax is equal to 3, and DQIdMax is equal to 2. extended\_spatial\_scalability is equal to 0, + +SpatialResolutionChangeFlag is equal to 0, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 0 (with default\_base\_mode\_flag equal to 1), adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of two quality enhancement layers. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, and EI and EP coded slices of two quality enhancement layers. + +#### 6.6.30.21 Test bitstream SVCBS-1 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. DependencyIdMax is equal to 1, TemporalIdMax is equal to 0, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 0, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a spatial enhancement layer. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a spatial enhancement layer. + +#### 6.6.30.22 Test bitstream SVCBS-2 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. DependencyIdMax is equal to 1, TemporalIdMax is equal to 0, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 0, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a spatial enhancement layer. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a spatial enhancement layer. + +#### 6.6.30.23 Test bitstream SVCBS-3 + +**Specification:** All slices are coded as I, P, EI or EP slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. num\_ref\_frames is equal to 1. DependencyIdMax is equal to 1, TemporalIdMax is equal to 0 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_motion\_prediction\_flag is equal to 1, specifying enabling an alternative motion vectors prediction process. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a spatial enhancement layer, using inter-layer motion, intra and residual prediction. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a spatial enhancement layer in the bitstream, using inter-layer motion, intra and residual prediction. + +#### 6.6.30.24 Test bitstream SVCBS-4 + +**Specification:** All slices are coded as I, P, EI or EP slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. num\_ref\_frames is equal to 1. DependencyIdMax is equal to 1, TemporalIdMax is equal to 0 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_motion\_prediction\_flag is equal to 1, specifying enabling an alternative motion vectors prediction process. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a spatial enhancement layer, using inter-layer motion, intra and residual prediction. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a spatial enhancement layer in the bitstream, using inter-layer motion, intra and residual prediction. + +#### 6.6.30.25 Test bitstream SVCBS-5 + +**Specification:** All slices are coded as I, P, EI or EP slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. num\_ref\_frames is equal to 1. DependencyIdMax is equal to 1, TemporalIdMax is equal to 0 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_motion\_prediction\_flag is equal to 1, specifying enabling an alternative motion vectors prediction process. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a spatial enhancement layer, using inter-layer motion, intra and residual prediction. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a spatial enhancement layer in the bitstream, using inter-layer motion, intra and residual prediction. + +#### 6.6.30.26 Test bitstream SVCBS-6 + +**Specification:** All slices are coded as I, P, EI or EP slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. num\_ref\_frames is equal to 1. DependencyIdMax is equal to 2, TemporalIdMax is equal to 0 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_motion\_prediction\_flag is equal to 1, specifying enabling an alternative motion vectors prediction process. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of two spatial enhancement layers, using inter-layer motion, intra and residual prediction. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of two spatial enhancement layers in the bitstream, using inter-layer motion, intra and residual prediction. + +#### 6.6.30.27 Test bitstream SVCBS-7 + +**Specification:** All slices are coded as I, P, EI or EP slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. pic\_order\_cnt\_type is equal to 0. num\_ref\_frames is equal to 1. DependencyIdMax is equal to 1, TemporalIdMax is equal to 0 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 1. + +no\_inter\_layer\_pred\_flag is equal to 1, specifying disabling inter-layer prediction. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI and EP coded slices of a spatial enhancement layer without inter-layer prediction. + +**Purpose:** Check that the decoder can properly handle EI and EP coded slices of a spatial enhancement layer without inter-layer prediction. + +#### 6.6.30.28 Test bitstream SVCBS-8 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 0 for dependency layer with dependency\_id equal to 0, specifying the CAVLC parsing process, and entropy\_coding\_mode\_flag is equal to 1 for dependency layer with dependency\_id equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1 for dependency layer with dependency\_id equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 1, TemporalIdMax is equal to 4 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 1. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 0. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying that inter-layer motion and inter-layer intra prediction are enabled. adaptive\_motion\_prediction\_flag is equal to 1, specifying that inter-layer motion prediction is enabled. adaptive\_residual\_prediction\_flag is equal to 1, specifying that inter-layer residual prediction is enabled. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of a spatial enhancement layer, using 8x8 transform size with inter-layer motion, intra and residual prediction and CABAC parsing. + +**Purpose:** Check that the decoder can properly handle gaps in frame\_num, reference picture list reordering, memory management control operations and EI, EP and EB coded slices of a spatial enhancement layer, using 8x8 transform size with inter-layer motion, intra and residual prediction and CABAC parsing. + +#### 6.6.30.29 Test bitstream SVCBST-1 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 0, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta. + +#### 6.6.30.30 Test bitstream SVCBST-2 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. + +DependencyIdMax is equal to 1, TemporalIdMax is equal to 3, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 0, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 1, and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using adaptive inter-layer motion prediction. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using adaptive inter-layer motion prediction. + +#### 6.6.30.31 Test bitstream SVCBST-3 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 1, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, and constrained\_intra\_resampling\_flag equal to 1. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, and constrained\_intra\_resampling\_flag equal to 1. + +#### 6.6.30.32 Test bitstream SVCBST-4 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 1, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, and constrained\_intra\_resampling\_flag equal to 1. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, and constrained\_intra\_resampling\_flag equal to 1. + +#### 6.6.30.33 Test bitstream SVCBST-5 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 1, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 16. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 1, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `constrained_intra_resampling_flag` is equal to 1, `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP skipped slices of a spatial enhancement layer, with CABAC parsing, non-zero values of `slice_qp_delta` and `mb_qp_delta`, and `constrained_intra_resampling_flag` equal to 1. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP skipped slices of a spatial enhancement layer, with CABAC parsing, non-zero values of `slice_qp_delta` and `mb_qp_delta`, and `constrained_intra_resampling_flag` equal to 1. + +#### 6.6.30.34 Test bitstream SVCBST-6 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 2, specifying enabling of the deblocking filter process (without slice boundary deblocking). `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 1, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 16. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 1, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `constrained_intra_resampling_flag` is equal to 1, `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 1, `adaptive_motion_prediction_flag` is equal to 0 (with default motion prediction flag equal to 1), and `adaptive_residual_prediction_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter and `constrained_intra_resampling_flag` equal to 1. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter and `constrained_intra_resampling_flag` equal to 1. + +#### 6.6.30.35 Test bitstream SVCBST-7 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 0, specifying enabling of the deblocking filter process (with slice boundary deblocking). `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 1, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 16. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 1, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `constrained_intra_resampling_flag` is equal to 0, `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 1, `adaptive_motion_prediction_flag` is equal to 0 (with default motion prediction flag equal to 1), and `adaptive_residual_prediction_flag` is equal to 1. + +disable\_inter\_layer\_deblocking\_filter\_idc is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, and use of deblocking filter. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter. + +#### 6.6.30.36 Test bitstream SVCBST-8 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 3, specifying enabling of the deblocking filter process (with second pass slice boundary deblocking). Additionally, slice\_alpha\_c0\_offset\_div2 and slice\_beta\_offset\_div2 are not equal to 0. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 1, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 2. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, using two pass deblocking filter and constrained\_intra\_resampling\_flag equal to 1. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, using two pass deblocking filter and constrained\_intra\_resampling\_flag equal to 1. + +#### 6.6.30.37 Test bitstream SVCBST-9 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 6, specifying enabling of the deblocking filter process for the luma samples (with second pass slice boundary deblocking). Additionally, slice\_alpha\_c0\_offset\_div2 and slice\_beta\_offset\_div2 are not equal to 0. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 1, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 2. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, using two pass deblocking filter for luma samples and constrained\_intra\_resampling\_flag equal to 1. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, using two pass deblocking filter for luma samples and constrained\_intra\_resampling\_flag equal to 1. + +#### 6.6.30.38 Test bitstream SVCBST-10 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 2, specifying enabling of the deblocking filter process (without slice boundary deblocking). `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. `transform_8x8_mode_flag` is equal to 1, specifying that 8x8 transform decoding process may be in use. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 1, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 16. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 1, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `constrained_intra_resampling_flag` is equal to 1, `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 1, `adaptive_motion_prediction_flag` is equal to 0 (with `default_motion_prediction_flag` equal to 1), and `adaptive_residual_prediction_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, using 8x8 transform size, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, and also using deblocking filter and `constrained_intra_resampling_flag` equal to 1. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, using 8x8 transform size, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, and also using deblocking filter and `constrained_intra_resampling_flag` equal to 1. + +#### 6.6.30.39 Test bitstream SVCBST-11 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 2, specifying enabling of the deblocking filter process (without slice boundary deblocking). `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. `weighted_pred_flag` is equal to 1. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 1, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 16. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 1, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `constrained_intra_resampling_flag` is equal to 1, `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 1, `adaptive_motion_prediction_flag` is equal to 0 (with `default_motion_prediction_flag` equal to 1), and `adaptive_residual_prediction_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Weighted sample prediction process for EP slices, reference picture list reordering, memory management control operations, and decoding of SEI message, EI and EP coded slices of a spatial enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter and `constrained_intra_resampling_flag` equal to 1. + +**Purpose:** Check that the decoder can properly handle weighted sample prediction process for EP slices, reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using deblocking filter and `constrained_intra_resampling_flag` equal to 1. + +#### 6.6.30.40 Test bitstream SVCBST-12 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice and slice groups greater than 1. `disable_deblocking_filter_idc` is equal to 3, specifying enabling of the deblocking filter process (with second pass slice boundary deblocking). Additionally, `slice_alpha_c0_offset_div2` and `slice_beta_offset_div2` are not equal to 0. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Reference picture list reordering is used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 1, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 16. `extended_spatial_scalability` + +is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 1, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 2. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter, constrained\_intra\_resampling\_flag equal to 1, and slice groups. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer, with non-zero values of slice\_qp\_delta and mb\_qp\_delta, using deblocking filter, constrained\_intra\_resampling\_flag equal to 1, and slice groups. + +#### 6.6.30.41 Test bitstream SVCBST-13 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering is used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 1, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 1, and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a spatial enhancement layer with SpatialResolutionChangeFlag equal to 3, CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, and constrained\_intra\_resampling\_flag equal to 1. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a spatial enhancement layer with SpatialResolutionChangeFlag equal to 3, CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, and constrained\_intra\_resampling\_flag equal to 1. + +#### 6.6.30.42 Test bitstream SVCBST-14 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering is used. DependencyIdMax is equal to 2, TemporalIdMax is equal to 3, and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1 for the dependency layer with dependency\_id equal to 1, and SpatialResolutionChangeFlag is equal to 1 for the dependency layer with dependency\_id equal to 2. chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 0, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of EI and EP coded slices of spatial enhancement layers with SpatialResolutionChangeFlag equal to 1 and 3. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, EI and EP coded slices of spatial enhancement layers with SpatialResolutionChangeFlag equal to 1 and 3. + +#### 6.6.30.43 Test bitstream SVCBST-15 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 2, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 32. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 1 for the enhancement layers, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `constrained_intra_resampling_flag` is equal to 0, `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 1, `adaptive_motion_prediction_flag` is equal to 1 for the dependency layer with `dependency_id` equal to 1, `adaptive_motion_prediction_flag` is equal to 0 (with `default_motion_prediction_flag` equal to 1) for the dependency layer with `dependency_id` equal to 2, and `adaptive_residual_prediction_flag` equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations and decoding of SEI messages, EI and EP coded slices of spatial enhancement layers, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using adaptive inter-layer motion prediction for layer 1. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of spatial enhancement layers, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using adaptive inter-layer motion prediction for layer 1. + +#### 6.6.30.44 Test bitstream SVCBST-16 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 3, specifying enabling of the deblocking filter process (with second pass slice boundary deblocking). `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 2, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 32. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 1 for the enhancement layers, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `constrained_intra_resampling_flag` is equal to 0, `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 1, `adaptive_motion_prediction_flag` is equal to 1, and `adaptive_residual_prediction_flag` is equal to 1. `disable_inter_layer_deblocking_filter_idc` is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of spatial enhancement layers, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using two pass deblocking filter and adaptive inter-layer motion prediction. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of spatial enhancement layers, with non-zero values of `slice_qp_delta` and `mb_qp_delta`, using two pass deblocking filter and adaptive inter-layer motion prediction. + +#### 6.6.30.45 Test bitstream SVCBST-17 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. `disable_deblocking_filter_idc` is equal to 3, specifying enabling of the deblocking filter process (with second pass slice boundary deblocking). `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 2. Reference picture list reordering and memory management control operations are used. `slice_qp_delta` is equal to a non-zero value to change the quantizer scale at each slice and `mb_qp_delta` is equal to a non-zero value to change the quantizer scale at some macroblocks. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 2, `TemporalIdMax` is equal to 3, and `DQIdMax` is equal to 32. `extended_spatial_scalability` is equal to 0, `SpatialResolutionChangeFlag` is equal to 1 for the enhancement layers, `chroma_phase_x_plus1_flag` is equal to 1, and `chroma_phase_y_plus1` is equal to 1. `constrained_intra_resampling_flag` is equal to 0, `no_inter_layer_pred_flag` is equal to 0, `slice_header_restriction_flag` is equal to 0, `scan_idx_start` is equal to 0, and `scan_idx_end` is equal to 15. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0, `adaptive_base_mode_flag` is equal to 1, `adaptive_motion_prediction_flag` is equal to 0 (with + +default\_motion\_prediction\_flag equal to 1) for the dependency layer with dependency\_id equal to 1, adaptive\_motion\_prediction\_flag is equal to 1 for the dependency layer with dependency\_id equal to 2, and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of spatial enhancement layers, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, using two pass deblocking filter and adaptive inter-layer motion prediction for layer 2. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of spatial enhancement layers, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, two pass deblocking filter and adaptive inter-layer motion prediction for layer 2. + +#### 6.6.30.46 Test bitstream SVCBST-18 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 3, specifying enabling of the deblocking filter process (with second pass slice boundary deblocking). entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice and mb\_qp\_delta is equal to a non-zero value to change the quantizer scale at some macroblocks. weighted\_pred\_flag is equal to 1 and base\_pred\_weight\_table\_flag is equal to 1. SEI messages are included in the bitstream. DependencyIdMax is equal to 2, TemporalIdMax is equal to 3, and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1 for the enhancement layers, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 0, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1) for the dependency layer with dependency\_id equal to 1, adaptive\_motion\_prediction\_flag is equal to 1 for the dependency layer with dependency\_id equal to 2, and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Weighted sample prediction process for EP slices, inference of weighted prediction variables for EP slices, reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of spatial enhancement layers, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, using two pass deblocking filter and adaptive inter-layer motion prediction for layer 2. + +**Purpose:** Check that the decoder can properly handle weighted sample prediction process for EP slices, inference of weighted prediction variables for EP slices, reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of spatial enhancement layers, with CABAC parsing, non-zero values of slice\_qp\_delta and mb\_qp\_delta, using two pass deblocking filter and adaptive inter-layer motion prediction for layer 2. + +#### 6.6.30.47 Test bitstream SVCBST-19 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 0 for dependency layer with dependency\_id equal to 0, specifying the CAVLC parsing process, and entropy\_coding\_mode\_flag is equal to 1 for dependency layer with dependency\_id equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1 for dependency layer with dependency\_id equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 1, TemporalIdMax is equal to 4 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 1. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 0. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying that inter-layer motion and inter-layer intra prediction are enabled. adaptive\_motion\_prediction\_flag is equal to 1, specifying that inter-layer motion prediction is enabled. adaptive\_residual\_prediction\_flag is equal to 1, specifying that inter-layer residual prediction is enabled. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of a spatial and temporal enhancement layer, using 8x8 transform size with inter-layer motion, intra and residual prediction and CABAC parsing. + +**Purpose:** Check that the decoder can properly handle gaps in frame\_num, reference picture list reordering, memory management control operations and EI, EP and EB coded slices of a spatial and temporal enhancement layer, using 8x8 transform size with inter-layer motion, intra and residual prediction and CABAC parsing. + +#### 6.6.30.48 Test bitstream SVCBST-20 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice. DependencyIdMax is equal to 1, TemporalIdMax is equal to 1 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 1, specifying sending geometrical parameters in the sequence parameter set. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_motion\_prediction\_flag is equal to 1, specifying enabling an alternative motion vectors prediction process. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process for inter-layer intra prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI, EP and EB coded slices of a spatial enhancement layer, using inter-layer motion, intra and residual prediction, sequence level geometrical parameters, deblocking filter for inter-layer intra prediction, non-zero values of slice\_qp\_delta. + +**Purpose:** Check that the decoder can properly handle decoding of EI, EP and EB coded slices of a spatial enhancement layer, using inter-layer motion, intra and residual prediction, sequence level geometrical parameters, deblocking filter for inter-layer intra prediction, non-zero values of slice\_qp\_delta. + +#### 6.6.30.49 Test bitstream SVCBMST-1 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 3. entropy\_coding\_mode\_flag is equal to 0. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. SEI messages are included in the bitstream. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 0, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1), and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of quality and spatial enhancement layers, using deblocking filter. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of quality and spatial enhancement layers, using deblocking filter. + +#### 6.6.30.50 Test bitstream SVCBMST-2 + +**Specification:** All slices are coded as I, P, EI or EP slices. Only the first frame is coded as an IDR access unit and each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 3. entropy\_coding\_mode\_flag is equal to 1. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering and memory management control operations are used. SEI messages are included in the bitstream. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3, and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 0, SpatialResolutionChangeFlag is equal to 1, chroma\_phase\_x\_plus1\_flag is equal to 1, and chroma\_phase\_y\_plus1 is equal to 1. constrained\_intra\_resampling\_flag is equal to 0, no\_inter\_layer\_pred\_flag is equal to 0, slice\_header\_restriction\_flag is equal to 0, scan\_idx\_start is equal to 0, and scan\_idx\_end is equal to 15. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0, adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 0 (with default\_motion\_prediction\_flag equal to 1) for the DQ layer with dq\_id equal to 1, adaptive\_motion\_prediction\_flag is equal to 1 for the DQ layer with dq\_id equal to 16, and adaptive\_residual\_prediction\_flag is equal to 1. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, and decoding of SEI messages, EI and EP coded slices of a quality enhancement layer and a spatial enhancement layer, using CABAC parsing, deblocking filter, and adaptive inter-layer motion prediction for the spatial enhancement layer. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations, SEI messages, EI and EP coded slices of a quality enhancement layer and a spatial enhancement layer, using CABAC parsing, deblocking filter, and adaptive inter-layer motion prediction for the spatial enhancement layer. + +#### 6.6.30.51 Test bitstream SVCBMST-3 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 0 for layer representation with DQId equal to 0, specifying the CAVLC parsing process. entropy\_coding\_mode\_flag is equal to 1 for layer representation with DQId equal to 1 and 16, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. transform\_8x8\_mode\_flag is equal to 1 for layer representation with DQId equal to 1 and 16, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 1, TemporalIdMax is equal to 4 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 1. SpatialResolutionChangeFlag is equal to 1 for dependency representation with dependency\_id equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. use\_ref\_base\_pic\_flag is equal to 1 for layer representation with dependency\_id equal to 0 in access units with temporal\_id equal to 0, specifying that reference base pictures may be used as reference pictures for the inter prediction process. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 0. store\_ref\_base\_pic\_flag is equal to 1 for layer representation with dependency\_id equal to 0 in access units with temporal\_id equal to 0, specifying that the reference base pictures are stored. slice\_skip\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying that inter-layer motion and inter-layer intra prediction are enabled. adaptive\_motion\_prediction\_flag is equal to 1, specifying that inter-layer motion prediction is enabled. adaptive\_residual\_prediction\_flag is equal to 1, specifying that inter-layer residual prediction is enabled. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI, EP and EB coded slices of a quality enhancement layer using key pictures and a spatial enhancement layer, with inter-layer motion, intra and residual prediction, using CABAC parsing. + +**Purpose:** Check that the decoder can properly handle EI, EP and EB coded slices of a quality enhancement layer using key pictures and a spatial enhancement layer, with inter-layer motion, intra and residual prediction, using CABAC parsing. + +#### 6.6.30.52 Test bitstream SVCBCTS-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 0 for dependency representation with dependency\_id equal to 0 and 1, specifying the CAVLC parsing process. entropy\_coding\_mode\_flag is equal to 1 for dependency representation with dependency\_id equal to 2, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. transform\_8x8\_mode\_flag is equal to 1 for dependency representation with dependency\_id equal to 2, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 2, TemporalIdMax is equal to 1 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0 for dependency representation with dependency\_id equal to 1. extended\_spatial\_scalability is equal to 1 for dependency representation with dependency\_id equal to 2. SpatialResolutionChangeFlag is equal to 0 for dependency representation with dependency\_id equal to 1. SpatialResolutionChangeFlag is equal to 1 for dependency representation with dependency\_id equal to 2. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 1 and adaptive\_residual\_prediction\_flag is equal to 1 for dependency representation with dependency\_id equal to 1 and 2, specifying enabling inter-layer motion, intra and residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI, EP and EB coded slices of spatial enhancement layers, with inter-layer motion, residual and intra prediction, using CAVLC and CABAC parsing, 8x8 transform size. + +**Purpose:** Check that the decoder can properly handle EI, EP and EB coded slices of spatial enhancement layers, with inter-layer motion, residual and intra prediction, using CAVLC and CABAC parsing, 8x8 transform size. + +#### 6.6.30.53 Test bitstream SVCBCTS-2 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 0 for dependency representation with dependency\_id equal to 0 and 1, specifying the CAVLC parsing process. entropy\_coding\_mode\_flag is equal to 1 for dependency representation with dependency\_id equal to 2, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. transform\_8x8\_mode\_flag is equal to 1 for dependency representation with dependency\_id equal to 2, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 2, TemporalIdMax is equal to 1 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0 for dependency representation with + +dependency\_id equal to 1. extended\_spatial\_scalability is equal to 1 for dependency representation with dependency\_id equal to 2. SpatialResolutionChangeFlag is equal to 0 for dependency representation with dependency\_id equal to 1. SpatialResolutionChangeFlag is equal to 1 for dependency representation with dependency\_id equal to 2. no\_inter\_layer\_pred\_flag is equal to 0. discardable\_flag is equal to 1 for dependency representation with dependency\_id equal to 1. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, adaptive\_motion\_prediction\_flag is equal to 1 and adaptive\_residual\_prediction\_flag is equal to 1 for dependency representation with dependency\_id equal to 1 and 2, specifying enabling inter-layer motion, intra and residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI, EP and EB coded slices of spatial enhancement layers, with inter-layer motion, residual and intra prediction, using CAVLC and CABAC parsing, 8x8 transform size, with discardable\_flag equal to 1. + +**Purpose:** Check that the decoder can properly handle EI, EP and EB coded slices of spatial enhancement layers, with inter-layer motion, residual and intra prediction, using CAVLC and CABAC parsing, 8x8 transform size, with discardable\_flag equal to 1. + +#### 6.6.30.54 Test bitstream SVCBCTS-3 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. DependencyIdMax is equal to 2, TemporalIdMax is equal to 3 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0 for dependency representation with dependency\_id equal to 1. SpatialResolutionChangeFlag is equal to 1 for dependency representation with dependency\_id equal to 2. no\_inter\_layer\_pred\_flag is equal to 0. tcoeff\_level\_prediction\_flag is equal to 1 for dependency representation with dependency\_id equal to 1, specifying that an alternative inter-layer prediction process is applied on a macroblock basis. seq\_tcoeff\_level\_prediction\_flag is equal to 0 for dependency representation with dependency\_id equal to 2. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. default\_base\_mode\_flag is equal to 1, specifying inter-layer motion and intra prediction. default\_residual\_prediction\_flag is equal to 0. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI, EP and EB coded slices of spatial enhancement layers, enabling either an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream or inter-layer motion and intra prediction. + +**Purpose:** Check that the decoder can properly handle EI, EP and EB coded slices of spatial enhancement layers, enabling either an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream or inter-layer motion and intra prediction. + +#### 6.6.30.55 Test bitstream SVCBSTC-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0, specifying the CAVLC parsing process. pic\_order\_cnt\_type is equal to 0. DependencyIdMax is equal to 2, TemporalIdMax is equal to 3 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 1 for dependency representation with dependency\_id equal to 1. SpatialResolutionChangeFlag is equal to 0 for dependency representation with dependency\_id equal to 2. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. default\_base\_mode\_flag is equal to 1, specifying inter-layer motion and intra prediction. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI, EP and EB coded slices of spatial enhancement layers, using inter-layer motion and intra prediction and inter-layer residual prediction in transform and spatial domain. + +**Purpose:** Check that the decoder can properly handle EI, EP and EB coded slices of spatial enhancement layers, using inter-layer motion and intra prediction and inter residual prediction in transform and spatial domain. + +### 6.6.31 Test bitstreams – SVC Profiles: Scalable High Profile 4:2:0 8 bit + +#### 6.6.31.1 Test bitstream SVCHM-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and memory management control operations are used. mb\_qp\_delta is equal to 0. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 0, TemporalIdMax is equal to 4 and DQIdMax is equal to 3. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 0. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1 for layer representations with quality\_id equal to 1, specifying that inter-layer motion and inter-layer intra prediction are enabled. adaptive\_motion\_prediction\_flag is equal to 1 for layer representation with quality\_id equal to 1, specifying that an alternative motion vectors prediction process is enabled. default\_base\_mode\_flag is equal to 1 for layer representations with quality\_id equal to 2 and 3, specifying inter-layer motion and intra prediction. adaptive\_residual\_prediction\_flag is equal to 1 for layer representation with quality\_id equal to 1, specifying enabling inter-layer residual prediction. default\_residual\_prediction\_flag is equal to 1 for layer representations with quality\_id equal to 2 and 3. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of quality enhancement layers, using key pictures, transform coefficient fragmentation and either an alternative motion vectors prediction process with inter-layer residual prediction or inter-layer motion and intra prediction, with non-zero values of mb\_qp\_delta, using 8x8 transform size CABAC parsing. + +**Purpose:** Check that the decoder can properly handle gaps in frame\_num, reference picture list reordering, memory management control operations, EI, EP and EB coded slices of quality enhancement layers, using key pictures, transform coefficient fragmentation and either an alternative motion vectors prediction process with inter-layer residual prediction or inter-layer motion and intra prediction, with non-zero values of mb\_qp\_delta, using 8x8 transform size and CABAC parsing. + +#### 6.6.31.2 Test bitstream SVCHM-2 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 0, TemporalIdMax is equal to 2 and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. adaptive\_tcoeff\_level\_prediction\_flag is equal to 0, specifying that an alternative inter-layer prediction process is applied for the whole sequence. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. default\_base\_mode\_flag is equal to 1, specifying inter-layer motion and intra prediction. default\_residual\_prediction\_flag is equal to 0. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of a quality enhancement layer, using an alternative inter-layer prediction process for translation to an AVC bitstream, with 8x8 transform size CABAC parsing. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of a quality enhancement layer, using an alternative inter-layer prediction process for translation to an AVC bitstream, with 8x8 transform size CABAC parsing. + +#### 6.6.31.3 Test bitstream SVCHM-3 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 0, TemporalIdMax is equal to 2 and DQIdMax is equal to 1. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. tcoeff\_level\_prediction\_flag is equal to 1, specifying that an alternative inter-layer prediction process is applied on a macroblock basis. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. default\_base\_mode\_flag is equal to 1, specifying + +inter-layer motion and intra prediction. default\_residual\_prediction\_flag is equal to 0. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of a quality enhancement layer, enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream, with 8x8 transform size CABAC parsing. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of a quality enhancement layer, enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream, with 8x8 transform size CABAC parsing. + +#### 6.6.31.4 Test bitstream SVCHM-4 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 0, TemporalIdMax is equal to 2 and DQIdMax is equal to 2. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. tcoeff\_level\_prediction\_flag is equal to 1 for layer representation with quality\_id equal to 1, specifying that an alternative inter-layer prediction process is applied on a macroblock basis. seq\_tcoeff\_level\_prediction\_flag is equal to 0 for layer representation with quality\_id equal to 2. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. default\_base\_mode\_flag is equal to 1, specifying inter-layer motion and intra prediction. default\_residual\_prediction\_flag is equal to 0. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of quality enhancement layers, either enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream or using inter-layer motion and intra prediction, with 8x8 transform size CABAC parsing. + +**Purpose:** Check that the decoder can properly handle reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of quality enhancement layers, either enabling an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream or using inter-layer motion and intra prediction, with 8x8 transform size CABAC parsing. + +#### 6.6.31.5 Test bitstream SVCHS-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 0 for the dependency representation with dependency\_id equal to 0, specifying the CAVLC parsing process. entropy\_coding\_mode\_flag is equal to 1 for the dependency representation with dependency\_id equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1 for the dependency representation with dependency\_id equal to 1, specifying that 8x8 transform decoding process may be in use. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 2, specifying sending geometrical parameters in slice headers. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling of inter-layer residual prediction. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process for inter-layer intra prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations, decoding of EI, EP and EB coded slices of a spatial enhancement layer, using inter-layer motion, intra and residual prediction, picture level geometrical parameters, deblocking filter for inter-layer intra prediction, with CABAC parsing, 8x8 transform size and non-zero values of slice\_qp\_delta. + +**Purpose:** Check that the decoder can properly handle decoding of reference picture list reordering, memory management control operations, EI, EP and EB coded slices of a spatial enhancement layer, using inter-layer motion, intra and residual prediction, picture level geometrical parameters, deblocking filter for inter-layer intra prediction, with CABAC parsing, 8x8 transform size and non-zero values of slice\_qp\_delta. + +#### 6.6.31.6 Test bitstream SVCHS-2 + +**Specification:** All slices are coded as I, P, B, EI, EP or EB slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice. mb\_adaptive\_frame\_field\_coding is equal to 1 for dependency representation with dependency\_id equal to 1. DependencyIdMax is equal to 1, TemporalIdMax is equal to 3 and DQIdMax is equal to 16. extended\_spatial\_scalability is equal to 1, specifying sending geometrical parameters in the sequence parameter set. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling of inter-layer residual prediction. disable\_inter\_layer\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process for inter-layer intra prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Progressive-to-interlace inter-layer prediction with mb\_adaptive\_frame\_field\_coding=1, reference picture list reordering, memory management control operations, decoding of EI, EP and EB coded slices of a spatial enhancement layer, using inter-layer motion, intra and residual prediction, sequence level geometrical parameters, deblocking filter for inter-layer intra prediction, with CABAC parsing, 8x8 transform size and non-zero values of slice\_qp\_delta. + +**Purpose:** Check that the decoder can properly handle decoding of progressive-to-interlace inter-layer prediction with mb\_adaptive\_frame\_field\_coding=1, reference picture list reordering, memory management control operations, EI, EP and EB coded slices of a spatial enhancement layer, using inter-layer motion, intra and residual prediction, sequence level geometrical parameters, deblocking filter for inter-layer intra prediction, with CABAC parsing, 8x8 transform size and non-zero values of slice\_qp\_delta. + +#### 6.6.31.7 Test bitstream SVCHST-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 2, TemporalIdMax is equal to 2 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial and temporal enhancement layers, enabling inter-layer motion, intra and residual prediction, using 8x8 transform size with CABAC parsing. + +**Purpose:** Check that the decoder can properly handle gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial and temporal enhancement layers, enabling inter-layer motion, intra and residual prediction, using 8x8 transform size with CABAC parsing. + +#### 6.6.31.8 Test bitstream SVCHST-2 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 2, TemporalIdMax is equal to 2 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0. no\_inter\_layer\_pred\_flag is equal to 0. discardable\_flag is equal to 1 for dependency representation with dependency\_id equal to 1. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1 for dependency representation with dependency\_id equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_residual\_prediction\_flag is equal to 1 for dependency representation with dependency\_id equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial enhancement layers, enabling inter-layer motion, intra and residual prediction, using 8x8 transform size with CABAC parsing, with discardable\_flag equal to 1. + +**Purpose:** Check that the decoder can properly handle gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial enhancement layers, enabling inter-layer motion, intra and residual prediction, using 8x8 transform size with CABAC parsing, with discardable\_flag equal to 1. + +#### 6.6.31.9 Test bitstream SVCHST-3 + +**Specification:** All slices are coded as I, P, B, EI, EP or EB slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice. mb\_adaptive\_frame\_field\_coding is equal to 1 for dependency representation with dependency\_id equal to 0. DependencyIdMax is equal to 2, TemporalIdMax is equal to 4 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 1. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. discardable\_flag is equal to 1 for dependency representation with dependency\_id equal to 1. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_motion\_prediction\_flag is equal to 1, specifying enabling inter-layer motion prediction. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process for inter-layer intra prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Interlace-to-progressive inter-layer prediction with mb\_adaptive\_frame\_field\_coding=1, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial enhancement layers, enabling inter-layer motion, intra and residual prediction, sequence level geometrical parameters, deblocking filter for inter-layer intra prediction, using 8x8 transform size with CABAC parsing and non-zero values of slice\_qp\_delta. + +**Purpose:** Check that the decoder can properly handle interlace-to-progressive inter-layer prediction with mb\_adaptive\_frame\_field\_coding=1, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial enhancement layers, enabling inter-layer motion, intra and residual prediction, sequence level geometrical parameters, deblocking filter for inter-layer intra prediction, using 8x8 transform size with CABAC parsing and non-zero values of slice\_qp\_delta. + +#### 6.6.31.10 Test bitstream SVCHST-4 + +**Specification:** All slices are coded as I, P, B, EI, EP or EB slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. slice\_qp\_delta is equal to a non-zero value to change the quantizer scale at each slice. mb\_adaptive\_frame\_field\_coding is equal to 1 for dependency representation with dependency\_id equal to 0. DependencyIdMax is equal to 2, TemporalIdMax is equal to 2 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 1. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. discardable\_flag is equal to 1 for dependency representation with dependency\_id equal to 1. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_motion\_prediction\_flag is equal to 1, specifying enabling inter-layer motion prediction. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_idc is equal to 0, specifying enabling of the deblocking filter process for inter-layer intra prediction. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Interlace-to-progressive inter-layer prediction with mb\_adaptive\_frame\_field\_coding=1, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial enhancement layers, enabling inter-layer motion, intra and residual prediction, sequence level geometrical parameters, deblocking filter for inter-layer intra prediction, using 8x8 transform size with CABAC parsing and non-zero values of slice\_qp\_delta. + +**Purpose:** Check that the decoder can properly handle interlace-to-progressive inter-layer prediction with `mb_adaptive_frame_field_coding=1`, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial enhancement layers, enabling inter-layer motion, intra and residual prediction, sequence level geometrical parameters, deblocking filter for inter-layer intra prediction, using 8x8 transform size with CABAC parsing and non-zero values of `slice_qp_delta`. + +#### 6.6.31.11 Test bitstream SVCHMTS-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. `disable_deblocking_filter_idc` is equal to 0. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `gaps_in_frame_num_value_allowed_flag` is equal to 1. Reference picture list reordering and memory management control operations are used. `transform_8x8_mode_flag` is equal to 1, specifying that 8x8 transform decoding process may be in use. SEI messages are included in the bitstream. `DependencyIdMax` is equal to 1, `TemporalIdMax` is equal to 2 and `DQIdMax` is equal to 16. `extended_spatial_scalability` is equal to 0. `SpatialResolutionChangeFlag` is equal to 0 for layer representations with `dependency_id` equal to 0 and `quality_id` equal to 1 and 2, and for layer representation with `dependency_id` equal to 1 and `quality_id` equal to 1. `SpatialResolutionChangeFlag` is equal to 1 for layer representations with `dependency_id` equal to 1 and `quality_id` equal to 0. `no_inter_layer_pred_flag` is equal to 0. `use_ref_base_pic_flag` may be equal to 1, specifying that reference base pictures may be used as reference pictures for the inter prediction process. `discardable_flag` is equal to 1 for layer representations with `dependency_id` equal to 1 and `quality_id` equal to 1 and for layer representations with `dependency_id` equal to 0 and `quality_id` equal to 2. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_header_restriction_flag` is equal to 0 and `store_ref_base_pic_flag` may be equal to 1, specifying that the reference base picture may be used for inter prediction of following pictures in decoding order. `slice_skip_flag` is equal to 0. `adaptive_base_mode_flag` is equal to 1, specifying enabling inter-layer motion and intra prediction. `adaptive_residual_prediction_flag` is equal to 1, specifying enabling inter-layer residual prediction. `inter_layer_deblocking_filter_control_present_flag` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Gaps in `frame_num`, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of quality, spatial and temporal enhancement layers, with quality layer information SEI messages and key pictures, enabling inter-layer motion, intra and residual prediction, using 8x8 transform size with CABAC parsing, with `discardable_flag` equal to 1. + +**Purpose:** Check that the decoder can properly handle gaps in `frame_num`, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of quality, spatial and temporal enhancement layers, with quality layer information SEI messages and key pictures, enabling inter-layer motion, intra and residual prediction, using 8x8 transform size with CABAC parsing, with `discardable_flag` equal to 1. + +#### 6.6.31.12 Test bitstream SVCHMTS-2 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. `disable_deblocking_filter_idc` is equal to 1, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. Reference picture list reordering and memory management control operations are used. `transform_8x8_mode_flag` is equal to 1, specifying that 8x8 transform decoding process may be in use. `DependencyIdMax` is equal to 1, `TemporalIdMax` is equal to 2 and `DQIdMax` is equal to 16. `extended_spatial_scalability` is equal to 0. `SpatialResolutionChangeFlag` is equal to 0 for layer representation with `dependency_id` equal to 0 and `quality_id` equal to 1. `SpatialResolutionChangeFlag` is equal to 1 for layer representation with `dependency_id` equal to 1 and `quality_id` equal to 0. `no_inter_layer_pred_flag` is equal to 0. `seq_tcoeff_level_prediction_flag` is equal to 0. `tcoeff_level_prediction_flag` is equal to 1, specifying that an alternative inter-layer prediction process is applied on a macroblock basis. `slice_header_restriction_flag` is equal to 1. `slice_skip_flag` is equal to 0. `default_base_mode_flag` is equal to 1, specifying inter-layer motion and intra prediction. `default_residual_prediction_flag` is equal to 0. `inter_layer_deblocking_filter_control_present_flag` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of quality and spatial enhancement layers, using either an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream or inter-layer motion and intra prediction, using 8x8 transform size with CABAC parsing. + +**Purpose:** Check that the decoder can properly handle gaps in `frame_num`, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of quality and spatial enhancement layers, using either an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream or inter-layer motion and intra prediction, using 8x8 transform size with CABAC parsing. + +#### 6.6.31.13 Test bitstream SVCHCTS-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each dependency representation contains only one slice. disable\_deblocking\_filter\_idc is equal to 0. entropy\_coding\_mode\_flag is equal to 1 for dependency\_id representations with dependency\_id greater than 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering and memory management control operations are used. transform\_8x8\_mode\_flag is equal to 1 for dependency\_id representations with dependency\_id greater than 1, specifying that 8x8 transform decoding process may be in use. DependencyIdMax is equal to 5, TemporalIdMax is equal to 2 and DQIdMax is equal to 80. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 0 for dependency\_id representations with dependency\_id equal to 1, 2 and 4. SpatialResolutionChangeFlag is equal to 1 for dependency representations with dependency\_id equal to 5. no\_inter\_layer\_pred\_flag is equal to 1 for dependency representations with dependency\_id equal to 3. discardable\_flag is equal to 1 for dependency representations with dependency\_id equal to 2, 4 and 5. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 1. slice\_skip\_flag is equal to 1 for dependency\_id representations with dependency\_id equal to 1. Adaptive\_base\_mode\_flag is equal to 1, enabling inter-layer motion and intra prediction. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial enhancement layers, using inter-layer motion, intra and residual prediction, using 8x8 transform size with CABAC parsing, no\_inter\_layer\_pred\_flag and discardable\_flag equal to 1. + +**Purpose:** Check that the decoder can properly handle gaps in frame\_num, reference picture list reordering, memory management control operations and decoding of EI, EP and EB coded slices of spatial enhancement layers, using inter-layer motion, intra and residual prediction, using 8x8 transform size with CABAC parsing, no\_inter\_layer\_pred\_flag and discardable\_flag equal to 1. + +#### 6.6.31.14 Test bitstream SVCHSTC-1 + +**Specification:** All slices are coded as I, P, EI, EP or EB slices. Each layer representation contains only one slice. deblocking\_filter\_control\_present\_flag is equal to 0. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. pic\_order\_cnt\_type is equal to 0. DependencyIdMax is equal to 2, TemporalIdMax is equal to 3 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 1 for dependency representation with dependency\_id equal to 1. SpatialResolutionChangeFlag is equal to 0 for dependency representation with dependency\_id equal to 2. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_header\_restriction\_flag is equal to 0. slice\_skip\_flag is equal to 0. default\_base\_mode\_flag is equal to 1, specifying inter-layer motion and intra prediction. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EI, EP and EB coded slices of spatial enhancement layers, using inter-layer motion and intra prediction and inter-layer residual prediction in transform and spatial domain, with 8x8 transform size and CABAC parsing. + +**Purpose:** Check that the decoder can properly handle EI, EP and EB coded slices of spatial enhancement layers, using inter-layer motion and intra prediction and inter residual prediction in transform and spatial domain, with 8x8 transform size and CABAC parsing. + +### 6.6.32 Test bitstreams – SVC Profiles: Scalable High Intra Profile 4:2:0 8 bit + +#### 6.6.32.1 Test bitstream SVCHIS-1 + +**Specification:** All slices are coded as IDR, or EIDR slices. Each dependency representation can contain more than one slice. disable\_deblocking\_filter\_idc is equal to 1, specifying disabling of the deblocking filter process. entropy\_coding\_mode\_flag is equal to 1, specifying the CABAC parsing process. transform\_8x8\_mode\_flag is equal to 1, specifying that 8x8 transform decoding process may be in use. pic\_order\_cnt\_type is equal to 0. DependencyIdMax is equal to 2, TemporalIdMax is equal to 0 and DQIdMax is equal to 32. extended\_spatial\_scalability is equal to 0. SpatialResolutionChangeFlag is equal to 1. no\_inter\_layer\_pred\_flag is equal to 0. seq\_tcoeff\_level\_prediction\_flag is equal to 0. slice\_skip\_flag is equal to 0. adaptive\_base\_mode\_flag is equal to 1, specifying enabling inter-layer motion and intra prediction. adaptive\_motion\_prediction\_flag is equal to 1, specifying enabling inter-layer motion prediction. adaptive\_residual\_prediction\_flag is equal to 1, specifying enabling inter-layer residual prediction. inter\_layer\_deblocking\_filter\_control\_present\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EIDR coded slices of spatial enhancement layers, 8x8 transform size with inter-layer intra prediction, using CABAC parsing. + +**Purpose:** Check that the decoder can properly handle EIDR coded slices of spatial enhancement layers, 8x8 transform size with inter-layer intra prediction, using CABAC parsing. + +#### 6.6.32.2 Test bitstream SVCHIS-2 + +**Specification:** All slices are coded as IDR, or EIDR slices. Each dependency representation can contain more than one slice. `deblocking_filter_control_present_flag` is equal to 0. `entropy_coding_mode_flag` is equal to 0, specifying the CAVLC parsing process. `transform_8x8_mode_flag` is equal to 1, specifying that 8x8 transform decoding process may be in use. `pic_order_cnt_type` is equal to 0. `DependencyIdMax` is equal to 2, `TemporalIdMax` is equal to 0 and `DQIdMax` is equal to 32. `extended_spatial_scalability` is equal to 1, specifying sending geometrical parameters in the sequence parameter set. `SpatialResolutionChangeFlag` is equal to 1 for the dependency representation with `dependency_id` equal to 1. `SpatialResolutionChangeFlag` is equal to 1 for the dependency representation with `dependency_id` equal to 2. `no_inter_layer_pred_flag` is equal to 0. `seq_tcoeff_level_prediction_flag` is equal to 0. `slice_skip_flag` is equal to 0. `adaptive_base_mode_flag` is equal to 1, specifying enabling inter-layer motion and intra prediction. `adaptive_motion_prediction_flag` is equal to 1, specifying enabling inter-layer motion prediction. `adaptive_residual_prediction_flag` is equal to 1, specifying enabling inter-layer residual prediction. `inter_layer_deblocking_filter_control_present_flag` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EIDR coded slices of spatial enhancement layers, 8x8 transform size with inter-layer intra and residual prediction, sequence level geometrical parameters, with CAVLC parsing. + +**Purpose:** Check that the decoder can properly handle EIDR coded slices of spatial enhancement layers, 8x8 transform size with inter-layer intra, sequence level geometrical parameters, with CAVLC parsing. + +#### 6.6.32.3 Test bitstream SVCHIS-3 + +**Specification:** All slices are coded as IDR, or EIDR slices. Each dependency representation can contain more than one slice. `deblocking_filter_control_present_flag` is equal to 0, specifying disabling of the deblocking filter process. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `transform_8x8_mode_flag` is equal to 1, specifying that 8x8 transform decoding process may be in use. `pic_order_cnt_type` is equal to 0. `DependencyIdMax` is equal to 2, `TemporalIdMax` is equal to 0 and `DQIdMax` is equal to 32. `extended_spatial_scalability` is equal to 1, specifying sending geometrical parameters in the sequence parameter set. `SpatialResolutionChangeFlag` is equal to 1 for the dependency representation with `dependency_id` equal to 1. `SpatialResolutionChangeFlag` is equal to 1 for the dependency representation with `dependency_id` equal to 2. `no_inter_layer_pred_flag` is equal to 1, specifying disabling inter-layer prediction. `seq_tcoeff_level_prediction_flag` is equal to 0. `inter_layer_deblocking_filter_control_present_flag` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EIDR coded slices of spatial enhancement layers, without inter-layer prediction, sequence level geometrical parameters using 8x8 transform size with CABAC parsing. + +**Purpose:** Check that the decoder can properly handle EIDR coded slices of spatial enhancement layers, without inter-layer prediction, sequence level geometrical parameters using 8x8 transform size with CABAC parsing. + +#### 6.6.32.4 Test bitstream SVCHICS-1 + +**Specification:** All slices are coded as IDR, or EIDR slices. Each dependency representation contains only one slice. `deblocking_filter_control_present_flag` is equal to 0. `entropy_coding_mode_flag` is equal to 1, specifying the CABAC parsing process. `pic_order_cnt_type` is equal to 0. `DependencyIdMax` is equal to 2, `TemporalIdMax` is equal to 0 and `DQIdMax` is equal to 32. `extended_spatial_scalability` is equal to 0. `SpatialResolutionChangeFlag` is equal to 0 for dependency representations with `dependency_id` equal to 1 and 3. `SpatialResolutionChangeFlag` is equal to 1 for the dependency representation with `dependency_id` equal to 2. `no_inter_layer_pred_flag` is equal to 0. `tcoeff_level_prediction_flag` is equal to 1 for dependency representation with `dependency_id` equal to 1, specifying that an alternative inter-layer prediction process is applied on a macroblock basis. `seq_tcoeff_level_prediction_flag` is equal to 1 for dependency representation with `dependency_id` equal to 2 and 3. `slice_header_restriction_flag` is equal to 0. `slice_skip_flag` is equal to 0. `default_base_mode_flag` is equal to 1, specifying inter-layer intra prediction. `adaptive_residual_prediction_flag` is equal to 1, specifying inter-layer residual prediction. `inter_layer_deblocking_filter_control_present_flag` is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of EIDR coded slices of quality enhancement layers, using an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream, and spatial enhancement layers, using inter-layer intra and residual prediction, with deblocking filter for inter-layer intra prediction and CABAC parsing. + +**Purpose:** Check that the decoder can properly handle EIDR coded slices of quality enhancement layers, using an alternative inter-layer prediction process by macroblock for translation to an AVC bitstream, and spatial enhancement + +layers, using inter-layer intra and residual prediction, with deblocking filter for inter-layer intra prediction and CABAC parsing. + +### 6.6.33 Test bitstreams – Multiview High Profile + +#### 6.6.33.1 Test bitstream MVCDS-1 + +**Specification:** All slices are coded as I slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. num\_anchor\_refs\_IX and num\_non\_anchor\_refs\_IX are equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of two views without inter-prediction or inter-view prediction. + +**Purpose:** Check that the decoder can properly decode multiple view components. + +#### 6.6.33.2 Test bitstream MVCDS-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. num\_anchor\_refs\_IX and num\_non\_anchor\_refs\_IX are equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of two views with inter-prediction, but without inter-view prediction. + +**Purpose:** Check that the decoder can properly decode multiple view components with inter-prediction. + +#### 6.6.33.3 Test bitstream MVCDS-3 + +**Specification:** All slices are coded as I or P slices. Only the first picture is coded as an IDR access unit with all subsequent pictures coded as anchor access units. Each view component contains only one slice. num\_views\_minus1 is equal to 1. num\_anchor\_refs\_I0 is equal to 1, num\_anchor\_refs\_I1 is equal to 0, and num\_non\_anchor\_refs\_IX is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of two views with inter-view prediction in anchor pictures, but without inter-prediction within views. + +**Purpose:** Check that the decoder can properly decode multiple view components with inter-view prediction in anchor pictures. + +#### 6.6.33.4 Test bitstream MVCDS-4 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. num\_anchor\_refs\_I0 is equal to 1, and num\_non\_anchor\_refs\_I0 is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of two views with inter-prediction, and inter-view prediction in anchor pictures. + +**Purpose:** Check that the decoder can properly decode multiple view components with inter-prediction, as well as inter-view prediction in anchor pictures. + +#### 6.6.33.5 Test bitstream MVCDS-5 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. num\_anchor\_refs\_I0 and num\_non\_anchor\_refs\_I0 are equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of two views with inter-prediction, and inter-view prediction in both anchor pictures and non-anchor pictures. + +**Purpose:** Check that the decoder can properly decode multiple view components with inter-prediction, as well as inter-view prediction in both anchor and non-anchor access units. + +#### 6.6.33.6 Test bitstream MVCDS-6 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. num\_anchor\_refs\_I0 and num\_non\_anchor\_refs\_I0 are equal to 1. inter\_view\_flag is equal to 0 for a subset of non-anchor view components of the base view. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of two views with inter-prediction, and inter-view prediction in both anchor pictures and non-anchor pictures. + +**Purpose:** Check that the decoder can properly decode multiple view components with inter-prediction, as well as inter-view prediction in both anchor and non-anchor access units, with different settings of inter\_view\_flag in different view components. + +#### 6.6.33.7 Test bitstream MVCNV-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2, and the views are denoted as A, B, and C, where view A is the base view, and views B and C are non-base views. View B refers to view A, and view C refers to view B. num\_anchor\_refs\_l0 and num\_non\_anchor\_refs\_l0 for view B and C are equal to 1, respectively. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of three views with inter-prediction and inter-view prediction in anchor access units and non-anchor pictures. + +**Purpose:** Check that the decoder can properly decode three views with inter-prediction, as well as inter-view prediction in anchor access units. + +#### 6.6.33.8 Test bitstream MVCNV-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 7, and the views are denoted as A, B, C, D, E, F, G, H, where view A is the base view, and other views are non-base views. View C refers to view A, view B refers to view A and view C, view E refers to view C, view D refers to view C and view E, view G refers to view E, view F refers to view E and view G, and view H refers to view G. num\_anchor\_refs\_l0 and num\_non\_anchor\_refs\_l0 for view C, E, G, and H are equal to 1, respectively, and num\_anchor\_refs\_lX (X=0,1) and num\_non\_anchor\_refs\_lX (X=0,1) for view B, D, and F are equal to 1, respectively. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of eight views with inter-prediction and inter-view prediction in anchor access units and non-anchor pictures. + +**Purpose:** Check that the decoder can properly decode eight views with inter-prediction, as well as inter-view prediction in anchor access units. + +#### 6.6.33.9 Test bitstream MVCNV-3 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2, and the views are denoted as A, B, and C, where view A is the base view, and views B and C are non-base views. View B refers to view A, and view C does not refer to either view A or B, i.e., it is an independently coded non-base view. num\_anchor\_refs\_l0 and num\_non\_anchor\_refs\_l0 for view C is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of three views including a base view with inter-prediction, a non-base view with inter-prediction but no inter-view prediction, and a non-base view with inter-view prediction from the base view and non-base view without inter-view prediction. + +**Purpose:** Check that the decoder can properly decode a bitstream including a mix of non-base views with and without inter-view prediction. + +#### 6.6.33.10 Test bitstream MVCNV-4 + +**Specification:** All slices are coded as I or P slices. Only the first picture is coded as an IDR access unit with all subsequent pictures coded as anchor access units. Each view component contains only one slice. num\_views\_minus1 is equal to 3, and the views are denoted as A, B, C, and D, where view A is the base view, and views B, C and D are non-base views. View B refers to view A, view C refers to view B, and view D refers to view C. num\_anchor\_refs\_l0 is equal to 1, num\_anchor\_refs\_l1 is equal to 0, and num\_non\_anchor\_refs\_lX is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of four views with inter-view prediction in anchor pictures and subsequent predictions over the views, but without inter-prediction within views. + +**Purpose:** Check that the decoder can properly decode multiple view components with inter-view prediction in anchor pictures for a higher number of views. + +#### 6.6.33.11 Test bitstream MVCRP-1 + +**Specification** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering is used without reordering\_of\_pic\_nums\_idc equal to 4 or 5. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering of reference pictures used for inter-prediction. + +**Purpose:** Check that the decoder handles reference picture list reordering of reference pictures used for inter-prediction. + +## 6.6.33.12 Test bitstream MVCRP-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. pic\_order\_cnt\_type is equal to 0. Memory management control operations are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Memory management control operations in context of decoding multiple view components. + +**Purpose:** Check that the decoder handles memory management control operations. + +#### 6.6.33.13 Test bitstream MVCRP-3 + +**Specification** All slices are coded as I or P slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. pic\_order\_cnt\_type is equal to 0. Reference picture list reordering is used including reordering\_of\_pic\_nums\_idc equal to 4 and 5. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering of reference pictures used for both inter-prediction and inter-view prediction. + +**Purpose:** Check that the decoder handles reference picture list reordering of reference pictures used for both inter-prediction and inter-view prediction. + +#### 6.6.33.14 Test bitstream MVCRP-4 + +**Specification** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. pic\_order\_cnt\_type is equal to 2. Reference picture list reordering including reordering\_of\_pic\_nums\_idc equal to 4 and 5, and memory management control operations, are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering for both inter-prediction and inter-view prediction, and memory management control operations. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. + +#### 6.6.33.15 Test bitstream MVCRP-5 + +**Specification** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. pic\_order\_cnt\_type is equal to 2. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering including reordering\_of\_pic\_nums\_idc equal to 4 and 5, and memory management control operations, are used. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering and memory management control operations. + +**Purpose:** Check that the decoder handles gaps in frame\_num, reference picture list reordering and memory management control operations. + +#### 6.6.33.16 Test bitstream MVCRP-6 + +**Specification:** All slices are coded as I or P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. pic\_order\_cnt\_type is equal to 0. gaps\_in\_frame\_num\_value\_allowed\_flag is equal to 1. Reference picture list reordering including reordering\_of\_pic\_nums\_idc equal to 4 and 5, and memory management control operations, are used. The decoding order is different from the output order. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Reference picture list reordering, memory management control operations and non-increasing PicOrderCnt values. + +**Purpose:** Check that the decoder handles reference picture list reordering and memory management control operations. Test output order conformance for non-increasing PicOrderCnt values. + +#### 6.6.33.17 Test bitstream MVCSPS-1 + +**Specification:** All slices are coded as I or P slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. Value of syntax elements in sequence parameter sets for each view vary. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of multiple views with different values of syntax elements in sequence parameter sets. + +**Purpose:** Check that the decoder handles variation in sequence parameter sets for each view. + +#### 6.6.33.18 Test bitstream MVCSPS-2 + +**Specification:** All slices are coded as I or P slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 7, but only two views in the bitstream. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of sub-bitstream where num\_views\_minus1 does not correspond to actual number of views in bitstream. + +**Purpose:** Check that the decoder handles bitstreams that have undergone sub-bitstream extraction process. + +### 6.6.34 Test bitstreams – Stereo High Profile + +#### 6.6.34.1 Test bitstream MVCICT-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. num\_anchor\_refs\_l0 and num\_non\_anchor\_refs\_l0 are equal to 1. field\_pic\_flag is equal to 1 for each picture. Reference picture list reordering is used with reordering\_of\_pic\_nums\_idc equal to 4 or 5. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of two views with inter-prediction, and each view component is coded as a field picture. + +**Purpose:** Check that the decoder handles reference picture list reordering for field pictures. + +#### 6.6.34.2 Test bitstream MVCICT-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. num\_anchor\_refs\_l0 and num\_non\_anchor\_refs\_l0 are equal to 1. mb\_adaptive\_frame\_field\_flag is equal to 1. field\_pic\_flag is equal to 0 for each picture. Reference picture list reordering is used with reordering\_of\_pic\_nums\_idc equal to 4 or 5. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of two views with inter-prediction, and each view component is coded as a mbaff frame picture. + +**Purpose:** Check that the decoder handles reference picture list reordering for mbaff frame pictures. + +### 6.6.35 Test bitstreams – Multiview Depth High Profile + +#### 6.6.35.1 Test bitstreams MVDDR-1, MVDDR-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. The width and the height of depth view components are half of the texture view components. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of texture view component and depth view component. + +**Purpose:** Check that the decoder can properly decode lower resolution depth view component. + +#### 6.6.35.2 Test bitstreams MVDDR-3, MVDDR-4 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. The width and the + +height of depth view components are equal to the texture view components. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of texture view component and depth view component. + +**Purpose:** Check that the decoder can properly decode the same resolution depth view component. + +#### 6.6.35.3 Test bitstreams MVDVC-1, MVDVC-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of texture view component and depth view component. + +**Purpose:** Check that the decoder can properly decode various view configurations. + +#### 6.6.35.4 Test bitstreams MVDVC-3, MVDVC-4 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of texture view component and depth view component. + +**Purpose:** Check that the decoder can properly decode various view configurations. + +#### 6.6.35.5 Test bitstreams MVDIV-1, MVDIV-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of texture view component and depth view component. + +**Purpose:** Check that the decoder can properly decode texture and depth view components with interview prediction. + +#### 6.6.35.6 Test bitstreams MVDIV-3, MVDIV-4 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of texture view component and depth view component. + +**Purpose:** Check that the decoder can properly decode texture and depth view components with inter frame prediction. + +#### 6.6.35.7 Test bitstream MVDIL-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. field\_pic\_flag is equal to 1 for texture view components. field\_pic\_flag is equal to 0 for depth view components. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of texture view component and depth view component. + +**Purpose:** Check that the decoder can properly decode interlace texture view components and progressive depth components. + +#### 6.6.35.8 Test bitstream MVDIL-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. field\_pic\_flag is equal to 1 for both texture and depth view components. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of texture view component and depth view component. + +**Purpose:** Check that the decoder can properly decode interlace texture and depth view components. + +#### 6.6.35.9 Test bitstream MVDRS-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 2. The width and the height of depth view components are half of the texture view components. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. The byte stream consists of supplemental enhancement information (SEI) metadata describing texture and depth acquisition information and depth representation. + +**Functional stage:** Decoding of texture and depth components, number of texture views is not equal to a number of depth views. + +**Purpose:** Check that the decoder can properly decode MVD with non-equal numbers of views for texture and depth components and decode relevant SEI messages. + +#### 6.6.35.10 Test bitstream #MVPCT-1 + +**Specification:** All slices are coded as I, P or B slices with coding tools specified in the Multiview Depth High profile of ITU-T H.264 | ISO/IEC 14496-10. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Multiview video plus depth (MVD) data is coded with an IPP inter-view prediction structure, with a central view being predicted from a left view (put in list 0), and a right view being predicted from the left and central views (both put in list 0), which utilizes prediction of dependent views from multiple inter-view references. + +**Functional stage:** Decoding of texture and depth view components with coding tools specified in the Multiview Depth High profile of ITU-T H.264 | ISO/IEC 14496-10 with IPP inter-view prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with dependent views which are coded with prediction from multiple inter-view references. + +#### 6.6.35.11 Test bitstream #MVPCT-2 + +**Specification:** All slices are coded as I, P or B slices with coding tools specified in the Multiview Depth High profile of ITU-T H.264 | ISO/IEC 14496-10. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Multiview video plus depth (MVD) data is coded with an IBP inter-view prediction structure, with a right view being predicted from a left view, and a central view being bi-predicted from the left (put in list 0) and right views (put in list 1). + +**Functional stage:** Decoding of texture and depth view components with coding tools specified in the Multiview Depth High profile of ITU-T H.264 | ISO/IEC 14496-10 with IBP inter-view prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with an IBP inter-view prediction structure. + +### 6.6.36 Test bitstreams – MFC High Profile + +#### 6.6.36.1 Test bitstream MFCRFT-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. mfc\_format\_idc is equal to 0. default\_grid\_position\_flag is equal to 1. rpu\_filter\_enabled\_flag is equal to 1. rpu\_field\_processing\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of the base and enhancement view components and reconstruction of the enhanced resolution stereo views with RPU Filter mode, using side-by-side base layer and default grid position. + +**Purpose:** Check that the decoder can properly decode the base and enhancement view components and reconstruct the enhanced resolution stereo views with RPU filter mode. + +#### 6.6.36.2 Test bitstream MFCRFT-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. mfc\_format\_idc is equal to 0. default\_grid\_position\_flag is equal to 1. rpu\_filter\_enabled\_flag is equal to 0. rpu\_field\_processing\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of the base and enhancement view components and reconstruction of the enhanced resolution stereo views with RPU DC mode, using side-by-side base layer and default grid position. + +**Purpose:** Check that the decoder can properly decode the base and enhancement view components and reconstruct the enhanced resolution stereo views with RPU DC mode. + +#### 6.6.36.3 Test bitstream MFCFLD-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. field\_pic\_flag is equal to 1. mfc\_format\_idc is equal to 0. default\_grid\_position\_flag is equal to 1. rpu\_filter\_enabled\_flag is equal to 1. rpu\_field\_processing\_flag is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of the base and enhancement view components and reconstruction of the enhanced resolution stereo views with RPU field processing, using side-by-side base layer, default grid position, RPU filter mode, and each view component is coded as a field picture. + +**Purpose:** Check that the decoder can properly decode the base and enhancement view components and reconstruct the enhanced resolution stereo views with RPU field processing for field pictures. + +#### 6.6.36.4 Test bitstream MFCFLD-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. mb\_adaptive\_frame\_field\_flag is equal to 1. field\_pic\_flag is equal to 0. mfc\_format\_idc is equal to 0. default\_grid\_position\_flag is equal to 1. rpu\_filter\_enabled\_flag is equal to 1. rpu\_field\_processing\_flag is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of the base and enhancement view components and reconstruction of the enhanced resolution stereo views with RPU field processing, using side-by-side base layer, default grid position, RPU filter mode, and each view component is coded as an mbaff frame picture. + +**Purpose:** Check that the decoder can properly decode the base and enhancement view components and reconstruct the enhanced resolution stereo views with RPU field processing for mbaff frame pictures. + +#### 6.6.36.5 Test bitstream MFCFLD-3 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. mb\_adaptive\_frame\_field\_flag is equal to 1. mfc\_format\_idc is equal to 0. default\_grid\_position\_flag is equal to 1. rpu\_filter\_enabled\_flag is equal to 1. rpu\_field\_processing\_flag is equal to 1. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of the base and enhancement view components and reconstruction of the enhanced resolution stereo views with RPU field processing, using side-by-side base layer, default grid position, RPU filter mode, and each view component is coded as an mbaff frame or a field picture. + +**Purpose:** Check that the decoder can properly decode the base and enhancement view components and reconstruct the enhanced resolution stereo views with RPU field processing for mbaff frame or a field picture. + +#### 6.6.36.6 Test bitstream MFCMFM-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. mfc\_format\_idc is equal to 1. default\_grid\_position\_flag is equal to 1. rpu\_filter\_enabled\_flag is equal to 1. rpu\_field\_processing\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of the base and enhancement view components and reconstruction of the enhanced resolution stereo views with top-and-bottom base layer MFC format configuration, using default grid position and RPU filter mode. + +**Purpose:** Check that the decoder can properly decode the base and enhancement view components and reconstruct the enhanced resolution stereo views with top-and-bottom MFC format configuration. + +#### 6.6.36.7 Test bitstream MFCGRD-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. mfc\_format\_idc is equal to 0. default\_grid\_position\_flag is equal to 0. rpu\_filter\_enabled\_flag is equal to 1. rpu\_field\_processing\_flag is equal to 0. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. + +**Functional stage:** Decoding of the base and enhancement view components and reconstruction of the enhanced resolution stereo views with non-default grid position configuration, using side-by-side base layer and RPU filter mode. + +**Purpose:** Check that the decoder can properly decode the base and enhancement view components and reconstruct the enhanced resolution stereo views with non-default grid positions. + +### 6.6.37 Test bitstreams – 3D-AVC Profiles + +#### 6.6.37.1 Test bitstream MVDDR3D-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. The width and the height of the depth view components are a quarter of those of the texture view components. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. The tools specified for the Enhanced Multiview Depth High profile are enabled, including depth-based MVP, VSP, adaptive luminance compensation, run-length encoded skip and slice header prediction. + +**Functional stage:** Decoding of texture and depth view components. + +**Purpose:** Check that the decoder can properly decode lower resolution depth view components. + +#### 6.6.37.2 Test bitstream MVDDR3D-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. The width and the height of the depth view components are equal to those of the texture view components. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. The tools specified for the Enhanced Multiview Depth High profile are enabled, including depth-based MVP, VSP, adaptive luminance compensation, run-length encoded skip and slice header prediction. + +**Functional stage:** Decoding of texture and depth view components. + +**Purpose:** Check that the decoder can properly decode the same resolution depth view components. + +#### 6.6.37.3 Test bitstream MVDC-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. View synthesis prediction (VSP) for dependent texture views is enabled. + +**Functional stage:** Decoding of texture and depth view components. + +**Purpose:** Check that the decoder can properly decode bitstreams when VSP is utilized. + +#### 6.6.37.4 Test bitstream MVDC-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Depth-based motion vector prediction (DMVP) is enabled. + +**Functional stage:** Decoding of texture and depth view components. + +**Purpose:** Check that the decoder can properly decode bitstreams when DMVP is utilized. + +#### 6.6.37.5 Test bitstream MVDC-3 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Adaptive luminance compensation (ALC) is enabled for coded texture views. + +**Functional stage:** Decoding of texture and depth view components. + +**Purpose:** Check that the decoder can properly decode bitstreams when ALC is utilized. + +#### 6.6.37.6 Test bitstream MVDC-4 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Non-linear depth representation (NLDR) is enabled for coded depth views. + +**Functional stage:** Decoding of texture and depth view components. + +**Purpose:** Check that the decoder can properly decode bitstreams when NLDR is utilized. + +#### 6.6.37.7 Test bitstream MVDCT-5 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Slice header prediction (SHP) is enabled for the texture component of dependent views and depth component of the base texture view. + +**Functional stage:** Decoding of texture and depth view components. + +**Purpose:** Check that the decoder can properly decode bitstreams when SHP is utilized. + +#### 6.6.37.8 Test bitstream MVDCT-6 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Multiview video plus depth (MVD) data is coded in an order in which the texture component precedes the depth component of the same view. The NBDV disparity derivation method is utilized for coding of texture components of dependent views. + +**Functional stage:** Decoding of texture and depth view components. + +**Purpose:** Check that the decoder can properly decode bitstreams when texture precedes the depth component and NBDV is used for disparity derivation of dependent texture views. + +#### 6.6.37.9 Test bitstream MVDCT-7 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Multiview video plus depth (MVD) data is coded in an order in which the texture component precedes the depth component of the same view. The depth oriented NBDV (DoNBDV) disparity derivation method is utilized for the coding of the texture component of dependent views. + +**Functional stage:** Decoding of texture and depth view components. + +**Purpose:** Check that the decoder can properly decode bitstreams when the texture component precedes the depth component and DoNBDV is used for disparity derivation of dependent texture views. + +#### 6.6.37.10 Test bitstream MVDCT-8 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Multiview video plus depth (MVD) data is coded with an IPP inter-view prediction structure, with a central view being predicted from a left view (put in list 0), and a right view being predicted from the left and central views (both put in list 0), which utilizes prediction of dependent views from multiple inter-view references. + +**Functional stage:** Decoding of texture and depth view components with IPP inter-view prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with dependent views which are coded with prediction from multiple inter-view references. + +#### 6.6.37.11 Test bitstream MVDCT-9 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Multiview video plus depth (MVD) data is coded with utilization of run-based arithmetic coding of the skip flag (RSAC) for dependent views. + +**Functional stage:** Decoding of texture and depth view components with RSAC enabled. + +**Purpose:** Check that the decoder can properly decode bitstreams with dependent views which are coded with RSAC enabled. + +#### 6.6.37.12 Test bitstream MVDCCT-10 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 2. NumDepthViews is equal to 3. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. Multiview video plus depth (MVD) data is coded with an IBP inter-view prediction structure, with a right view being predicted from a left view, and a central view being bi-predicted from the left view (put in list 0) and right view (put in list 1). + +**Functional stage:** Decoding of texture and depth view components with IBP inter-view prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with IBP inter-view prediction structure. + +### 6.6.38 Test bitstreams – MFC Depth High Profile + +#### 6.6.38.1 Test bitstream MFCDDR-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. The base layer texture view is in side-by-side frame compatible format. field\_pic\_flag is equal to 0 for both the texture and depth view components. The coding order of the texture and depth views are structured as "T0D0D1T1", i.e., texture for view 0, followed by depth for view 0, followed by depth for view 1, and followed by texture for view 1. The width and the height of the depth view components are equal to those of the texture view components. + +**Functional stage:** Decoding of the base and enhancement texture and depth view components and reconstruction of the enhanced resolution stereo texture views. + +**Purpose:** Check that the decoder can properly decode the base and enhancement texture view components and the same resolution depth view components and reconstruct the enhanced resolution stereo texture views. + +#### 6.6.38.2 Test bitstream MFCDDR-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. The base layer texture view is in side-by-side frame compatible format. field\_pic\_flag is equal to 0 for both the texture and depth view components. The coding order of the texture and depth views are structured as "T0D0D1T1", i.e., texture for view 0, followed by depth for view 0, followed by depth for view 1, and followed by texture for view 1. The width and the height of the depth view components are half of those of the texture view components. + +**Functional stage:** Decoding of the base and enhancement texture and depth view components and reconstruction of the enhanced resolution stereo texture views. + +**Purpose:** Check that the decoder can properly decode the base and enhancement texture view components and lower resolution depth view components and reconstruct the enhanced resolution stereo texture views. + +#### 6.6.38.3 Test bitstream MFCDFLD-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. The base layer texture view is in side-by-side frame compatible format. The coding order of the texture and depth views are structured as "T0D0D1T1", i.e., texture for view 0, followed by depth for view 0, followed by depth for view 1, and followed by texture for view 1. field\_pic\_flag is equal to 1 for texture view components. field\_pic\_flag is equal to 0 for depth view components. + +**Functional stage:** Decoding of the base and enhancement field-coded texture view components and frame-coded depth view components and reconstruction of the enhanced resolution stereo texture views. + +**Purpose:** Check that the decoder can properly decode the field-coded base and enhancement texture view components and frame-coded depth components and reconstruct the enhanced resolution stereo texture views. + +#### 6.6.38.4 Test bitstream MFCDFLD-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. The base layer texture view is in side-by-side frame compatible format. The coding order of the texture and depth views are structured as + +"T0D0D1T1", i.e., texture for view 0, followed by depth for view 0, followed by depth for view 1, and followed by texture for view 1. field\_pic\_flag is equal to 1 for both the texture and depth view components. + +**Functional stage:** Decoding of the base and enhancement field-coded texture and depth view components and reconstruction of the enhanced resolution stereo texture views. + +**Purpose:** Check that the decoder can properly decode the field-coded base and enhancement texture and depth view components and reconstruct the enhanced resolution stereo texture views. + +#### 6.6.38.5 Test bitstream MFCDTDC-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. The base layer texture view is in side-by-side frame compatible format. field\_pic\_flag is equal to 0 for both the texture and depth view components. The coding order of the texture and depth views are structured as "T0D0T1D1", i.e., texture for view 0, followed by depth for view 0, followed by texture for view 1, followed by depth for view 1. + +**Functional stage:** Decoding of the base and enhancement texture and depth view components and reconstruction of the enhanced resolution stereo texture views. + +**Purpose:** Check that the decoder can properly decode the base and enhancement texture and depth view components with various coding orders and reconstruct the enhanced resolution stereo texture views. + +#### 6.6.38.6 Test bitstream MFCDTDC-2 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. The base layer texture view is in side-by-side frame compatible format. field\_pic\_flag is equal to 0 for both the texture and depth view components. The coding order of the texture and depth views are structured as "T0T1D0D1", i.e., texture for view 0, followed by texture for view 1, followed by depth for view 0, followed by depth for view 1. + +**Functional stage:** Decoding of the base and enhancement texture and depth view components and reconstruction of the enhanced resolution stereo texture views. + +**Purpose:** Check that the decoder can properly decode the base and enhancement texture and depth view components with various coding orders and reconstruct the enhanced resolution stereo texture views. + +#### 6.6.38.7 Test bitstream MFCDMFC-1 + +**Specification:** All slices are coded as I, P or B slices. Only the first picture is coded as an IDR access unit. Each view component contains only one slice. num\_views\_minus1 is equal to 1. NumDepthViews is equal to 2. All NAL units are encapsulated into the byte stream format specified in Annex B in ITU-T H.264 | ISO/IEC 14496-10. field\_pic\_flag is equal to 0 for both the texture and depth view components. The coding order of the texture and depth views are structured as "T0D0D1T1", i.e., texture for view 0, followed by depth for view 0, followed by depth for view 1, and followed by texture for view 1. mfc\_format\_idc is set to 1, i.e., the base layer texture view is in top-and-bottom frame compatible format. + +**Functional stage:** Decoding of the base and enhancement texture and depth view components and reconstruction of the enhanced resolution stereo texture views. + +**Purpose:** Check that the decoder can properly decode the base and enhancement texture and depth view components with various base layer texture frame compatible format and reconstruct the enhanced resolution stereo texture views. + +### 6.7 Normative test suites for ITU-T H.264 | ISO/IEC 14496-10 + +*Legend:* + +X – Bitstream is for static and dynamic test + +**Table 1 – Bitstreams for the Constrained Baseline, Baseline, Extended and Main profiles** + +| Categories | Bitstream | Donated by | File name | Constrained | Baseline | Extended | Main | Level | Frame rate (Frames/sec) | +|------------|-----------|-----------------|---------------|-------------|----------|----------|------|----------------|-------------------------| +| General | AVCNL-1 | Sony | NL1_Sony_D | X | X | X | X | 1.2 and higher | 15 | +| | AVCNL-2 | SVA | SVA_NL1_B | X | X | X | X | 2.1 and higher | 29.97 | +| | AVCNL-3 | Sony | NL2_Sony_H | X | X | X | X | 3.1 and higher | 15 | +| | AVCNL-4 | SVA | SVA_NL2_E | X | X | X | X | 2.1 and higher | 29.97 | +| | AVCBA-1 | Sony | BA1_Sony_D | X | X | X | X | 1.2 and higher | 15 | +| | AVCBA-2 | SVA | SVA_BA1_B | X | X | X | X | 2.1 and higher | 29.97 | +| | AVCBA-3 | Sony | BA2_Sony_F | X | X | X | X | 3.1 and higher | 15 | +| | AVCBA-4 | SVA | SVA_BA2_D | X | X | X | X | 2.1 and higher | 29.97 | +| | AVCBA-5 | MCubeworks | BA_MW_D | X | X | X | X | 1 and higher | 15 | +| | AVCBA-6 | MCubeworks | BANM_MW_D | X | X | X | X | 1 and higher | 15 | +| | AVCBA-7 | France Telecom | BA1_FT_C | X | X | X | X | 2 and higher | 25 | +| | AVCMQ-1 | JVC | NLMQ1_JVC_C | X | X | X | X | 2 and higher | 25 | +| | AVCMQ-2 | JVC | NLMQ2_JVC_C | X | X | X | X | 2 and higher | 25 | +| | AVCMQ-3 | JVC | BAMQ1_JVC_C | X | X | X | X | 2 and higher | 25 | +| | AVCMQ-4 | JVC | BAMQ2_JVC_C | X | X | X | X | 2 and higher | 25 | +| | AVCSL-1 | SVA | SVA_Base_B | X | X | X | X | 2.1 and higher | 29.97 | +| | AVCSL-2 | SVA | SVA_FM1_E | X | X | X | X | 2.1 and higher | 29.97 | +| | AVCSQ-1 | Sony | BASQP1_Sony_C | X | X | X | X | 2.1 and higher | 15 | +| | AVCFM-1 | British Telecom | FM1_BT_B | | X | X | | 1 and higher | 5 | +| | AVCFM-2 | SVA | FM2_SVA_C | | X | X | | 2.1 and higher | 15 | +| | AVCFM-3 | France Telecom | FM1_FT_E | | X | X | | 2 and higher | 25 | +| | AVCCI-1 | MCubeworks | CI_MW_D | X | X | X | X | 1 and higher | 15 | +| | AVCCI-2 | SVA | SVA_CLI1_E | X | X | X | X | 2.1 and higher | 29.97 | +| | AVCCI-3 | France Telecom | CI1_FT_B | X | X | X | X | 2 and higher | 25 | +| | AVCFC-1 | Sony | CVFC1_Sony_C | X | X | X | X | 3.1 and higher | 29.97 | +| | AVCAUD-1 | Mcubeworks | AUD_MW_E | X | X | X | X | 1 and higher | 15 | + +**Table 1 – Bitstreams for the Constrained Baseline, Baseline, Extended and Main profiles** + +| Categories | Bitstream | Donated by | File name | Constrained | Baseline | Extended | Main | Level | Frame rate (Frames/sec) | +|------------|------------|-----------------|-----------------------|-------------|----------|----------|------|----------------|-------------------------| +| | AVCMIDR-1 | Mcubeworks | MIDR_MW_D | X | X | X | X | 1 and higher | 15 | +| | AVCNRf-1 | Mcubeworks | NRF_MW_E | X | X | X | X | 1 and higher | 15 | +| | AVCMPS-1 | Mcubeworks | MPS_MW_A | X | X | X | X | 1.1 and higher | 15 | +| | AVCBS-1 | Sony | CVBS3_Sony_C | | | X | X | 1.2 and higher | 15 | +| | AVCBS-2 | SVA | BA3_SVA_C | | | X | X | 2.1 and higher | 29.97 | +| | AVCBS-3 | SVA | SL1_SVA_B | | | | X | 2.1 and higher | 29.97 | +| | AVCBS-4 | SVA | NL3_SVA_E | | | X | X | 1.1 and higher | 29.97 | +| | AVCBS-5 | Motorola | cavlc_mot_frm0_full_B | | | X | X | 3 and higher | 29.97 | +| I_PCM | AVCP PCM-1 | SVA | CVPCMNL1_SVA_C | X | X | X | X | 4 and higher | 29.97 | +| | AVCP PCM-2 | SVA | CVPCMNL2_SVA_C | X | X | X | X | 4 and higher | 60 | +| MMCO | AVCMR-1 | British Telecom | MR1_BT_A | X | X | X | X | 1.1 and higher | 20 | +| | AVCMR-2 | Tandberg | MR2_Tandberg_E | | X | X | | 3.1 and higher | 29.97 | +| | AVCMR-3 | Tandberg | MR3_Tandberg_B | | X | X | | 3.1 and higher | 29.97 | +| | AVCMR-4 | Tandberg | MR4_Tandberg_C | | X | X | | 3.1 and higher | 29.97 | +| | AVCMR-5 | Tandberg | MR5_Tandberg_C | | X | X | | 3.1 and higher | 29.97 | +| | AVCMR-6 | Mcubeworks | MR1_MW_A | X | X | X | X | 1.1 and higher | 15 | +| | AVCMR-7 | Mcubeworks | MR2_MW_A | X | X | X | X | 1.1 and higher | 15 | +| | AVCMR-8 | British Telecom | MR6_BT_B | | | X | X | 2.1 and higher | 25 | +| | AVCMR-9 | British Telecom | MR7_BT_B | | | X | X | 2.1 and higher | 25 | +| | AVCMR-10 | British Telecom | MR8_BT_B | | | X | X | 2.1 and higher | 25 | +| | AVCMR-11 | HHI | HCBP1_HHI_A | X | X | X | X | 3.1 and higher | 29.97 | +| | AVCMR-12 | HHI | HCBP2_HHI_A | X | X | X | X | 3.1 and higher | 29.97 | +| WP | AVCWP-1 | Toshiba | CVWP5_TOSHIBA_E | | | X | X | 2 and higher | 7.5 | +| | AVCWP-2 | Toshiba | CVWP1_TOSHIBA_E | | | | X | 2 and higher | 7.5 | +| | AVCWP-3 | Toshiba | CVWP2_TOSHIBA_E | | | | X | 2 and higher | 7.5 | +| | AVCWP-4 | Toshiba | CVWP3_TOSHIBA_E | | | | X | 2 and higher | 7.5 | + +**Table 1 – Bitstreams for the Constrained Baseline, Baseline, Extended and Main profiles** + +| Categories | Bitstream | Donated by | File name | Constrained | Baseline | Extended | Main | Level | Frame rate
(Frames/sec) | +|--------------------|-----------|-----------------|--------------------------|---------------------------|------------------------|------------------------|--------------------|----------------|----------------------------| +| | | | | Constrained
and higher | Baseline
and higher | Extended
and higher | Main
and higher | | | +| Field coding | AVCFI-1 | Sony | CVNLFI1_Sony_C | | | X | X | 3.1 and higher | 29.97 | +| | AVCFI-2 | Sony | CVNLFI2_Sony_H | | | X | X | 3.1 and higher | 29.97 | +| | AVCFI-3 | Sharp Labs | Sharp_MP_Field1_B | | | X | X | 3 and higher | 29.97 | +| | AVCFI-4 | Sharp Labs | Sharp_MP_Field2_B | | | X | X | 3 and higher | 29.97 | +| | AVCFI-5 | Sharp Labs | Sharp_MP_Field3_B | | | X | X | 3 and higher | 29.97 | +| | AVCFI-6 | Sony | CVFI1_Sony_D | | | X | X | 3.1 and higher | 29.97 | +| | AVCFI-7 | Sony | CVFI2_Sony_H | | | | X | 3.1 and higher | 29.97 | +| | AVCFI-8 | Sony | FI1_Sony_E | | | X | X | 2.1 and higher | 29.97 | +| | AVCFI-9 | SVA | CVFI1_SVA_C | | | | X | 3 and higher | 29.97 | +| | AVCFI-10 | SVA | CVFI2_SVA_C | | | X | X | 3 and higher | 29.97 | +| | AVCFI-11 | Motorola | cavlc_mot_fld0_full_B | | | X | X | 2.2 and higher | 29.97 | +| | AVCFI-12 | Motorola | CVMP_MOT_FLD_L30_B | | | X | X | 3 and higher | 29.97 | +| Frame/field coding | AVCPA-1 | Sharp Labs | Sharp_MP_PAFF_1r2 | | | X | X | 3 and higher | 29.97 | +| | AVCPA-2 | Toshiba | CVPA1_TOSHIBA_B | | | X | X | 2.1 and higher | 25 | +| | AVCPA-3 | Motorola | cavlc_mot_picaff0_full_B | | | X | X | 2.2 and higher | 29.97 | +| MBAFF | AVCMA-1 | Toshiba | CVMANL1_TOSHIBA_B | | | X | X | 2.1 and higher | 25 | +| | AVCMA-2 | Toshiba | CVMANL2_TOSHIBA_B | | | X | X | 2.1 and higher | 25 | +| | AVCMA-3 | Sony | CVMA1_Sony_D | | | X | X | 3.1 and higher | 29.97 | +| | AVCMA-4 | Toshiba | CVMA1_TOSHIBA_B | | | X | X | 2.1 and higher | 25 | +| | AVCMA-5 | Sony | CVMAQP2_Sony_G | | | X | X | 3.1 and higher | 29.97 | +| | AVCMA-6 | Sony | CVMAQP3_Sony_D | | | X | X | 2.1 and higher | 29.97 | +| | AVCMA-7 | Sony | CVMAPAQP3_Sony_E | | | X | X | 3.1 and higher | 29.97 | +| | AVCMA-8 | Motorola | cavlc_mot_mbaft0_full_B | | | X | X | 2.2 and higher | 29.97 | +| | AVCMA-9 | Motorola | CVMP_MOT_FRM_L31_B | | | X | X | 3.1 and higher | 29.97 | +| S Picture | AVCSP-1 | British Telecom | SP1_BT_A | | | X | | 1 and higher | 10 | +| | AVCSP-2 | British Telecom | SP2_BT_B | | | X | | 1 and higher | 20 | + +**Table 1 – Bitstreams for the Constrained Baseline, Baseline, Extended and Main profiles** + +| Categories | Bitstream | Donated by | File name | Constrained | Baseline | Extended | Main | Level | Frame rate (Frames/sec) | +|-----------------------|-----------|------------|---------------------|-------------|----------|----------|------|----------------|-------------------------| +| Long sequence | AVCLS-1 | SVA | LS_SVA_D | X | X | X | X | 1.3 and higher | 29.97 | +| SEI/VUI | AVCSE-1 | Sony | CVSE2_Sony_B | | | X | X | 2.1 and higher | 15 | +| | AVCSE-2 | Sony | CVSE3_Sony_H | | | X | X | 2.1 and higher | 15 | +| | AVCSE-3 | Sony | CVSEFDFT3_Sony_E | | | X | X | 2.1 and higher | 15 | +| CABAC | AVCCANL-1 | Toshiba | CANL1_TOSHIBA_G | | | | X | 1.2 and higher | 29.97 | +| | AVCCANL-2 | Sony | CANL1_Sony_E | | | | X | 2.1 and higher | 15 | +| | AVCCANL-3 | Sony | CANL2_Sony_E | | | | X | 2.1 and higher | 15 | +| | AVCCANL-4 | Sony | CANL3_Sony_C | | | | X | 1.2 and higher | 15 | +| | AVCCANL-5 | SVA | CANL1_SVA_B | | | | X | 2.1 and higher | 29.97 | +| | AVCCANL-6 | SVA | CANL2_SVA_B | | | | X | 2.1 and higher | 29.97 | +| | AVCCANL-7 | SVA | CANL3_SVA_B | | | | X | 2.1 and higher | 29.97 | +| | AVCCANL-8 | SVA | CANL4_SVA_B | | | | X | 2.1 and higher | 29.97 | +| | AVCCABA-1 | Sony | CABA1_Sony_D | | | | X | 2.1 and higher | 15 | +| | AVCCABA-2 | Sony | CABA2_Sony_E | | | | X | 2.1 and higher | 15 | +| | AVCCABA-3 | Sony | CABA3_Sony_C | | | | X | 1.2 and higher | 15 | +| | AVCCABA-4 | Toshiba | CABA3_TOSHIBA_E | | | | X | 1.2 and higher | 29.97 | +| | AVCCABA-5 | SVA | CABA1_SVA_B | | | | X | 2.1 and higher | 29.97 | +| | AVCCABA-6 | SVA | CABA2_SVA_B | | | | X | 2.1 and higher | 29.97 | +| | AVCCABA-7 | SVA | CABA3_SVA_B | | | | X | 2.1 and higher | 29.97 | +| | AVCCABA-8 | Motorola | cabac_mot_frm0_full | | | | X | 3 and higher | 29.97 | +| CABAC: Initialization | AVCCAIN-1 | Sony | CABACI3_Sony_B | | | | X | 2.1 and higher | 15 | +| CABAC: MB QP Delta | AVCCAQP-1 | Sony | CAQP1_Sony_B | | | | X | 1.2 and higher | 15 | +| | AVCCAQP-2 | Sony | CACQP3_Sony_D | | | | X | 2.1 and higher | 15 | +| CABAC: Slice | AVCCASL-1 | Sony | CABAST3_Sony_E | | | | X | 2.1 and higher | 29.97 | +| | AVCCASL-2 | Sony | CABASTBR3_Sony_B | | | | X | 2.1 and higher | 29.97 | + +**Table 1 – Bitstreams for the Constrained Baseline, Baseline, Extended and Main profiles** + +| Categories | Bitstream | Donated by | File name | Constrained | Baseline | Extended | Main | Level | Frame rate (Frames/sec) | +|---------------------------|------------|-----------------|------------------------|-------------|----------|----------|------|----------------|-------------------------| +| CABAC: I_PCM | AVCCAPCM-1 | Broadcom | CAPCMNL1_Sand_E | | | | X | 4 and higher | 29.97 | +| | AVCCAPCM-2 | Broadcom | CAPCM1_Sand_E | | | | X | 4 and higher | 29.97 | +| | AVCCAPCM-3 | Sony | CAPM3_Sony_D | | | | X | 2.1 and higher | 15 | +| CABAC: MMCO | AVCCAMR-1 | British Telecom | MR9_BT_B | | | | X | 2.1 and higher | 25 | +| | AVCCAMR-2 | HHI | HCMP1_HHI_A | | | | X | 3 and higher | 29.97 | +| CABAC: WP | AVCCAWP-1 | Toshiba | CAWP1_TOSHIBA_E | | | | X | 2 and higher | 7.5 | +| | AVCCAWP-2 | Toshiba | CAWP5_TOSHIBA_E | | | | X | 2 and higher | 7.5 | +| CABAC: Field coding | AVCCAFI-1 | Broadcom | CABREF3_Sand_D | | | | X | 4 and higher | 29.97 | +| | AVCCAFI-2 | SVA | CAFI_SVA_C | | | | X | 3 and higher | 29.97 | +| | AVCCAFI-3 | Motorola | cabac_mot_fld0_full | | | | X | 2.2 and higher | 29.97 | +| CABAC: Frame/field coding | AVCCAPA-1 | Sharp Labs | Sharp_MP_PAFF_2r | | | | X | 3 and higher | 29.97 | +| | AVCCAPA-2 | Toshiba | CAPA1_TOSHIBA_B | | | | X | 2.1 and higher | 25 | +| | AVCCAPA-3 | Motorola | cabac_mot_paff0_full | | | | X | 2.2 and higher | 29.97 | +| CABAC: MBAFF | AVCCAMA-1 | Toshiba | CAMANL1_TOSHIBA_B | | | | X | 2.1 and higher | 25 | +| | AVCCAMA-2 | Toshiba | CAMANL2_TOSHIBA_B | | | | X | 2.1 and higher | 25 | +| | AVCCAMA-3 | Sony | CANLMA2_Sony_C | | | | X | 3.1 and higher | 29.97 | +| | AVCCAMA-4 | Sony | CANLMA3_Sony_C | | | | X | 3.1 and higher | 29.97 | +| | AVCCAMA-5 | Sony | CAMA1_Sony_C | | | | X | 3.1 and higher | 29.97 | +| | AVCCAMA-6 | Toshiba | CAMA1_TOSHIBA_B | | | | X | 2.1 and higher | 25 | +| | AVCCAMA-7 | Broadcom | CAMANL3_Sand_E | | | | X | 4 and higher | 29.97 | +| | AVCCAMA-8 | Broadcom | CAMA3_Sand_E | | | | X | 4 and higher | 29.97 | +| | AVCCAMA-9 | Sony | CAMASL3_Sony_B | | | | X | 2.1 and higher | 29.97 | +| | AVCCAMA-10 | Sony | CAMACI3_Sony_C | | | | X | 2.1 and higher | 29.97 | +| | AVCCAMA-11 | Motorola | cabac_mot_mbaeff0_full | | | | X | 2.2 and higher | 29.97 | +| | AVCCAMA-12 | Motorola | CAMP_MOT_MBAFF_L30 | | | | X | 3 and higher | 29.97 | +| | AVCCAMA-13 | Motorola | CAMP_MOT_MBAFF_L31 | | | | X | 3.1 and higher | 29.97 | + +**Table 1 – Bitstreams for the Constrained Baseline, Baseline, Extended and Main profiles** + +| Categories | Bitstream | Donated by | File name | Constrained | Baseline | Extended | Main | Level | Frame rate (Frames/sec) | +|-----------------------------|----------------|---------------|------------------|-------------|----------|----------|------|----------------|-------------------------| +| | AVCCAPAM A-1 | Broadcom | CAPAMA3_Sand_F | | | | X | 4 and higher | 29.97 | +| | AVCCAPAM A-2 | VideoTele.com | CAMA1_VTC_C | | | | X | 3 and higher | 29.97 | +| | AVCCAPAM A-3 | VideoTele.com | CAMA2_VTC_B | | | | X | 3 and higher | 25 | +| | AVCCAPAM A-4 | VideoTele.com | CAMA3_VTC_B | | | | X | 3 and higher | 25 | +| CABAC: Prediction bandwidth | AVCCAMV-1 | Broadcom | MV1_BRCM_D | | | | X | 3 and higher | 29.97 | +| CABAC/CAVLC | AVCCVCAN LMA-1 | Sony | CVCANLMA2_Sony_C | | | | X | 3.1 and higher | 29.97 | + +**Table 2 – Bitstreams for the High, High 10, and High 4:2:2 profiles** + +| Categories | Bitstream | Donated by | File name | High | High 10 | High 4:2:2 | Level | Frame rate (Frames/sec) | +|-------------|-----------|--------------------------|--------------------|------|---------|------------|----------------|-------------------------| +| 4:2:0 8 bit | FREH-1 | Panasonic Singapore Lab. | FRExt1_Panasonic_D | X | X | X | 2.1 and higher | 29.97 | +| | FREH-2 | Panasonic Singapore Lab. | FRExt3_Panasonic_E | X | X | X | 2.1 and higher | 29.97 | +| | FREH-3 | HHI | HCAFR1_HHI_C | X | X | X | 3 and higher | 15 | +| | FREH-4 | HHI | HCAFF1_HHI_B | X | X | X | 3 and higher | 15 | +| | FREH-5 | HHI | HCAMFF1_HHI_B | X | X | X | 3 and higher | 15 | +| | FREH-6 | Panasonic Singapore Lab. | FRExt2_Panasonic_C | X | X | X | 2.1 and higher | 29.97 | +| | FREH-7 | Panasonic Singapore Lab. | FRExt4_Panasonic_B | X | X | X | 2.1 and higher | 29.97 | +| | FREH-8 | Broadcom | HPCANL_BRCM_C | X | X | X | 4 and higher | 29.97 | +| | FREH-9 | Broadcom | HPCA_BRCM_C | X | X | X | 4 and higher | 29.97 | +| | FREH-10 | Broadcom | HPCAFLNL_BRCM_C | X | X | X | 4 and higher | 29.97 | +| | FREH-11 | Broadcom | HPCAFL_BRCM_C | X | X | X | 4 and higher | 29.97 | +| | FREH-12 | HHI | HCAFR2_HHI_A | X | X | X | 2 and higher | 15 | +| | FREH-13 | HHI | HCAFR3_HHI_A | X | X | X | 3 and higher | 15 | + +**Table 2 – Bitstreams for the High, High 10, and High 4:2:2 profiles** + +| Categories | Bitstream | Donated by | File name | High | High 10 | High 4:2:2 | Level | Frame rate (Frames/sec) | +|------------|-----------|------------|-------------------|------|---------|------------|----------------|-------------------------| +| | FREH-14 | HHI | HCAFR4_HHI_A | X | X | X | 3 and higher | 15 | +| | FREH-15 | Broadcom | HPCADQ_BRCM_B | X | X | X | 4 and higher | 29.97 | +| | FREH-16 | Broadcom | HPCALQ_BRCM_B | X | X | X | 4 and higher | 29.97 | +| | FREH-17 | Broadcom | HPCAMAPALQ_BRCM_B | X | X | X | 4 and higher | 29.97 | +| | FREH-18 | Broadcom | HPCV_BRCM_A | X | X | X | 4 and higher | 29.97 | +| | FREH-19 | Broadcom | HPCVNL_BRCM_A | X | X | X | 4 and higher | 29.97 | +| | FREH-20 | Broadcom | HPCVFL_BRCM_A | X | X | X | 4 and higher | 29.97 | +| | FREH-21 | Broadcom | HPCVFLNL_BRCM_A | X | X | X | 4 and higher | 29.97 | +| | FREH-22 | Sony | HVLCFI0_Sony_B | X | X | X | 3.1 and higher | 29.97 | +| | FREH-23 | Sony | HVLCFFF0_Sony_B | X | X | X | 3.1 and higher | 29.97 | +| | FREH-24 | Sony | HVLCMFF0_Sony_A | X | X | X | 3.1 and higher | 29.97 | +| | FREH-25 | Broadcom | HPCVMOLQ_BRCM_B | X | X | X | 4 and higher | 29.97 | +| | FREH-26 | Broadcom | HPCAMOLQ_BRCM_B | X | X | X | 4 and higher | 29.97 | +| | FREH-27 | Broadcom | HPCAQ2LQ_BRCM_B | X | X | X | 4 and higher | 29.97 | +| | FREH-28 | Broadcom | brcm_freh1_B | X | X | X | 3 and higher | 29.97 | +| | FREH-29 | Broadcom | brcm_freh2_B | X | X | X | 3 and higher | 29.97 | +| | FREH-30 | Broadcom | brcm_freh3 | X | X | X | 3 and higher | 29.97 | +| | FREH-31 | Broadcom | brcm_freh4 | X | X | X | 3 and higher | 29.97 | +| | FREH-32 | Broadcom | brcm_freh5 | X | X | X | 3 and higher | 29.97 | +| | FREH-33 | Broadcom | brcm_freh6 | X | X | X | 3 and higher | 29.97 | +| | FREH-34 | Broadcom | brcm_freh7_B | X | X | X | 3 and higher | 29.97 | +| | FREH-35 | Broadcom | brcm_freh8 | X | X | X | 3 and higher | 29.97 | +| | FREH-36 | Broadcom | brcm_freh9 | X | X | X | 3 and higher | 29.97 | +| | FREH-37 | Broadcom | brcm_freh10 | X | X | X | 3 and higher | 29.97 | +| | FREH-38 | Broadcom | brcm_freh11 | X | X | X | 3 and higher | 29.97 | +| | FREH-39 | Broadcom | brcm_freh12_B | X | X | X | 3 and higher | 29.97 | + +**Table 2 – Bitstreams for the High, High 10, and High 4:2:2 profiles** + +| Categories | Bitstream | Donated by | File name | High | High 10 | High 4:2:2 | Level | Frame rate (Frames/sec) | +|--------------|------------|------------|---------------------|------|---------|------------|----------------|-------------------------| +| | FREH-40 | HHI | HCHP1_HHI_B | X | X | X | 2.1 and higher | 29.97 | +| | FREH-41 | HHI | HCHP2_HHI_A | X | X | X | 3.1 and higher | 29.97 | +| | FREH-42 | HHI | HCHP3_HHI_A | X | X | X | 4.1 and higher | 29.97 | +| | FREH-43 | JVC | FREXT01_JVC_D | X | X | X | 3.1 and higher | 29.97 | +| | FREH-44 | JVC | FREXT01_JVC_C | X | X | X | 3.1 and higher | 29.97 | +| | FREH-45 | Sony | FREXT_MMCO4_Sony_B | X | X | X | 3.1 and higher | 29.97 | +| 4:2:0 10 bit | FREH10-1 | Dolby | FREH10-1 | | X | X | 4 and higher | 24 | +| | FREH10-2 | Dolby | FREH10-2 | | X | X | 4 and higher | 24 | +| 4:2:2 10 bit | FREH422-1 | Tandberg | FREXT1_TANDBERG_A | | | X | 2.1 and higher | 29.97 | +| | FREH422-2 | Tandberg | FREXT2_TANDBERG_A | | | X | 2.1 and higher | 29.97 | +| | FREH422-3 | Tandberg | FREXT3_TANDBERG_A | | | X | 2.1 and higher | 29.97 | +| | FREH422-4 | Sony | Hi422FREXT1_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-5 | Sony | Hi422FREXT2_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-6 | Sony | Hi422FREXT3_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-7 | Sony | Hi422FREXT4_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-8 | Sony | Hi422FREXT6_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-9 | Sony | Hi422FREXT7_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-10 | Sony | Hi422FREXT8_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-11 | Sony | Hi422FREXT9_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-12 | Sony | Hi422FREXT10_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-13 | Sony | Hi422FREXT11_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-14 | Sony | Hi422FREXT12_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-15 | Sony | Hi422FREXT13_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-16 | Sony | Hi422FREXT14_Sony_A | | | X | 3.1 and higher | 29.97 | +| | FREH422-17 | Sony | Hi422FREXT15_Sony_A | | | X | 3.1 and higher | 29.97 | + +**Table 2 – Bitstreams for the High, High 10, and High 4:2:2 profiles** + +| Categories | Bitstream | Donated by | File name | High | High 10 | High 4:2:2 | Level | Frame rate (Frames/sec) | +|-------------------------|------------|------------|---------------------|------|---------|------------|----------------|-------------------------| +| | FREH422-18 | Sony | Hi422FREXT16_Sony_A | | | X | 4 and higher | 29.97 | +| | FREH422-19 | Sony | Hi422FREXT17_Sony_A | | | X | 4 and higher | 29.97 | +| | FREH422-20 | Sony | Hi422FREXT18_Sony_A | | | X | 4 and higher | 29.97 | +| | FREH422-21 | Sony | Hi422FREXT19_Sony_A | | | X | 4 and higher | 29.97 | +| Auxiliary coded picture | FREAUX-1 | Apple | alphaconformanceG | X | X | X | 2.1 and higher | 29.97 | + +**Table 3 – Bitstreams for the High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, High 4:4:4 Predictive, and CAVLC 4:4:4 Intra profile** + +| Categories | Bitstream | Donated by | File name | High 10 Intra | High 4:2:2 Intra | High 4:4:4 Intra | High 4:4:4 Predictive | CAVLC 4:4:4 Intra | Level | Frame rate (Frames/sec) | +|-------------------------|------------|-------------|------------------------|---------------|------------------|------------------|-----------------------|-------------------|----------------|-------------------------| +| 4:4:4 14 bit Predictive | PPH444-P1 | Thomson | PPH444P1_2008 | | | | X | | 4.1 and higher | 29.97 | +| | PPH444-P2 | Thomson | PPH444P2_2008 | | | | X | | 4.1 and higher | 29.97 | +| | PPH444-P3 | Thomson | PPH444P3_2008 | | | | X | | 4.1 and higher | 29.97 | +| | PPH444-P4 | Thomson | PPH444P4_2008 | | | | X | | 3.2 and higher | 59.94 | +| | PPH444-P5 | Thomson | PPH444P5_2008 | | | | X | | 3.2 and higher | 59.94 | +| | PPH444-P6 | Mitsubishi | PPH444P6_Mitsubishi_A | | | | X | | 4.1 and higher | 29.97 | +| | PPH444-P7 | Mitsubishi | PPH444P7_Mitsubishi_A | | | | X | | 4.1 and higher | 29.97 | +| | PPH444-P8 | Mitsubishi | PPH444P8_Mitsubishi_A | | | | X | | 4.1 and higher | 29.97 | +| | PPH444-P9 | Mitsubishi | PPH444P9_Mitsubishi_A | | | | X | | 4.1 and higher | 59.94 | +| | PPH444-P10 | Sejong Univ | PPH444P10_SejongUniv_A | | | | X | | 3.2 and higher | 59.94 | + +**Table 3 – Bitstreams for the High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, High 4:4:4 Predictive, and CAVLC 4:4:4 Intra profile** + +| Categories | Bitstream | Donated by | File name | High 10 Intra | High 4:2:2 Intra | High 4:4:4 Intra | High 4:4:4 Predictive | CAVLC 4:4:4 Intra | Level | Frame rate (Frames/sec) | +|--------------------|-----------|------------|----------------------|---------------|------------------|------------------|-----------------------|-------------------|----------------|-------------------------| +| 4:2:0 10 bit Intra | PPH10-1 | Panasonic | PPH10I1_Panasonic_A | X | X | X | X | X | 3.2 and higher | 59.94 | +| | PPH10-2 | Panasonic | PPH10I2_Panasonic_A | X | X | X | X | | 3.2 and higher | 59.94 | +| | PPH10-3 | Panasonic | PPH10I3_Panasonic_A | X | X | X | X | | 3.2 and higher | 59.94 | +| | PPH10-4 | Panasonic | PPH10I4_Panasonic_A | X | X | X | X | X | 4.1 and higher | 29.97 | +| | PPH10-5 | Panasonic | PPH10I5_Panasonic_A | X | X | X | X | | 4.1 and higher | 29.97 | +| | PPH10-6 | Panasonic | PPH10I6_Panasonic_A | X | X | X | X | X | 4.1 and higher | 29.97 | +| | PPH10-7 | Panasonic | PPH10I7_Panasonic_A | X | X | X | X | | 4.1 and higher | 29.97 | +| 4:2:2 10 bit Intra | PPH422I-1 | Panasonic | PPH422I1_Panasonic_A | | X | X | X | X | 3.2 and higher | 59.94 | +| | PPH422I-2 | Panasonic | PPH422I2_Panasonic_A | | X | X | X | | 3.2 and higher | 59.94 | +| | PPH422I-3 | Panasonic | PPH422I3_Panasonic_A | | X | X | X | | 3.2 and higher | 59.94 | +| | PPH422I-4 | Panasonic | PPH422I4_Panasonic_A | | X | X | X | X | 4.1 and higher | 29.97 | +| | PPH422I-5 | Panasonic | PPH422I5_Panasonic_A | | X | X | X | | 4.1 and higher | 29.97 | +| | PPH422I-6 | Panasonic | PPH422I6_Panasonic_A | | X | X | X | X | 4.1 and higher | 29.97 | +| | PPH422I-7 | Panasonic | PPH422I7_Panasonic_A | | X | X | X | | 4.1 and higher | 29.97 | +| 4:4:4 14 bit Intra | PPH444I-1 | Thomson | PPH444I1_2008 | | | X | X | | 3.2 and higher | 59.94 | +| | PPH444I-2 | Thomson | PPH444I2_2008 | | | X | X | | 3.2 and higher | 59.94 | +| | PPH444I-3 | Thomson | PPH444I3_2008 | | | X | X | | 3.2 and higher | 59.94 | + +**Table 3 – Bitstreams for the High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, High 4:4:4 Predictive, and CAVLC 4:4:4 Intra profile** + +| Categories | Bitstream | Donated by | File name | High 10 Intra | High 4:2:2 Intra | High 4:4:4 Intra | High 4:4:4 Predictive | CAVLC 4:4:4 Intra | Level | Frame rate (Frames/sec) | +|--------------------------|------------|-------------|------------------------|---------------|------------------|------------------|-----------------------|-------------------|----------------|-------------------------| +| | PPH444I-4 | Mitsubishi | PPH444I4_Mitsubishi_A | | | X | X | | 4.1 and higher | 29.97 | +| | PPH444I-5 | Mitsubishi | PPH444I5_Mitsubishi_A | | | X | X | | 4.1 and higher | 29.97 | +| | PPH444I-6 | Mitsubishi | PPH444I6_Mitsubishi_A | | | X | X | | 4.1 and higher | 29.97 | +| | PPH444I-7 | Sejong Univ | PPH444I7_SejongUniv_A | | | X | X | | 3.2 and higher | 59.94 | +| CAVLC 4:4:4 14 bit Intra | PPCV444I-1 | Thomson | PPCV444I1_2008 | | | | X | X | 3.2 and higher | 59.94 | +| | PPCV444I-2 | Thomson | PPCV444I2_2008 | | | | X | X | 3.2 and higher | 59.94 | +| | PPCV444I-3 | Thomson | PPCV444I3_2008 | | | | X | X | 3.2 and higher | 59.94 | +| | PPCV444I-4 | Mitsubishi | PPCV444I4_Mitsubishi_A | | | | X | X | 4.1 and higher | 29.97 | +| | PPCV444I-5 | Mitsubishi | PPCV444I5_Mitsubishi_A | | | | X | X | 4.1 and higher | 29.97 | +| | PPCV444I-6 | Mitsubishi | PPCV444I6_Mitsubishi_A | | | | X | X | 4.1 and higher | 29.97 | +| | PPCV444I-7 | Sejong Univ | PPCV444I7_SejongUniv_A | | | | X | X | 3.2 and higher | 59.94 | + +**Table 4 – Bitstreams for the Constrained Baseline, High, High 10 Intra, Scalable Baseline, Scalable High, and Scalable High Intra profiles** + +| Categories | Bitstream | Donated by | File name | Constrained Baseline | High | High 10 Intra | Scalable Baseline | Scalable High | Scalable High Intra | Level | Frame rate (Frames/sec) | +|--------------|-----------|------------|-------------|----------------------|------|---------------|-------------------|---------------|---------------------|----------------|-------------------------| +| | | | | | | | | | | | | +| CGS | SVCBC-1 | HHI | SVCBC-1-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBC-1 | HHI | SVCBC-1-L1 | | | | X | | | 2.1 and higher | 29.97 | +| MGS | SVCBM-1 | Vidyo | SVCBM-1-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBM-1 | Vidyo | SVCBM-1-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBM-2 | Sharp | SVCBM-2-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBM-2 | Sharp | SVCBM-2-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBM-3 | Sharp | SVCBM-3-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBM-3 | Sharp | SVCBM-3-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBM-4 | Sharp | SVCBM-4-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBM-4 | Sharp | SVCBM-4-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBM-4 | Sharp | SVCBM-4-L2 | | | | X | | | 2.1 and higher | 29.97 | +| | SVCBM-5 | HHI | SVCBM-5-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBM-5 | HHI | SVCBM-5-L1 | | | | X | | | 2.1 and higher | 29.97 | +| | SVCBM-5 | HHI | SVCBM-5-L2 | | | | X | | | 3 and higher | 29.97 | +| | SVCBM-5 | HHI | SVCBM-5-L3 | | | | X | | | 3 and higher | 29.97 | +| | SVCBCT-1 | HHI | SVCBCT-1-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| CGS/Temporal | SVCBCT-1 | HHI | SVCBCT-1-L1 | | | | X | | | 2.1 and higher | 29.97 | +| MGS/Temporal | SVCBMT-1 | Vidyo | SVCBMT-1-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-1 | Vidyo | SVCBMT-1-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-2 | Vidyo | SVCBMT-2-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-2 | Vidyo | SVCBMT-2-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-3 | Vidyo | SVCBMT-3-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-3 | Vidyo | SVCBMT-3-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-4 | Vidyo | SVCBMT-4-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-4 | Vidyo | SVCBMT-4-L1 | | | | X | | | 1.3 and higher | 29.97 | + +**Table 4 – Bitstreams for the Constrained Baseline, High, High 10 Intra, Scalable Baseline, Scalable High, and Scalable High Intra profiles** + +| Categories | Bitstream | Donated by | File name | Constrained Baseline | High | High 10 Intra | Scalable Baseline | Scalable High | Scalable High Intra | Level | Frame rate (Frames/sec) | +|------------|-----------|------------|--------------|----------------------|------|---------------|-------------------|---------------|---------------------|----------------|-------------------------| +| | | | | | | | | | | | | +| | SVCBMT-5 | Vidyo | SVCBMT-5-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-5 | Vidyo | SVCBMT-5-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-6 | Vidyo | SVCBMT-6-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-6 | Vidyo | SVCBMT-6-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-7 | Vidyo | SVCBMT-7-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-7 | Vidyo | SVCBMT-7-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-8 | Vidyo | SVCBMT-8-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-8 | Vidyo | SVCBMT-8-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-9 | Vidyo | SVCBMT-9-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-9 | Vidyo | SVCBMT-9-L1 | | | | X | | | 2.2 and higher | 29.97 | +| | SVCBMT-10 | Vidyo | SVCBMT-10-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-10 | Vidyo | SVCBMT-10-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-11 | Vidyo | SVCBMT-11-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-11 | Vidyo | SVCBMT-11-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-12 | Vidyo | SVCBMT-12-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-12 | Vidyo | SVCBMT-12-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-13 | Vidyo | SVCBMT-13-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMT-13 | Vidyo | SVCBMT-13-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMT-13 | Vidyo | SVCBMT-13-L2 | | | | X | | | 2.1 and higher | 29.97 | +| Spatial | SVCBS-1 | Vidyo | SVCBS-1-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBS-1 | Vidyo | SVCBS-1-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBS-2 | Vidyo | SVCBS-2-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBS-2 | Vidyo | SVCBS-2-L1 | | | | X | | | 3 and higher | 29.97 | +| | SVCBS-3 | ETRI | SVCBS-3-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBS-3 | ETRI | SVCBS-3-L1 | | | | X | | | 3 and higher | 29.97 | + +**Table 4 – Bitstreams for the Constrained Baseline, High, High 10 Intra, Scalable Baseline, Scalable High, and Scalable High Intra profiles** + +| Categories | Bitstream | Donated by | File name | Constrained Baseline | High | High 10 Intra | Scalable Baseline | Scalable High | Scalable High Intra | Level | Frame rate (Frames/sec) | +|----------------------|-----------|------------|-------------|----------------------|------|---------------|-------------------|---------------|---------------------|----------------|-------------------------| +| | SVCBS-4 | ETRI | SVCBS-4-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBS-4 | ETRI | SVCBS-4-L1 | | | | X | | | 3 and higher | 29.97 | +| | SVCBS-5 | ETRI | SVCBS-5-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBS-5 | ETRI | SVCBS-5-L1 | | | | X | | | 3 and higher | 29.97 | +| | SVCBS-6 | ETRI | SVCBS-6-L0 | X | X | | X | X | | 1.1 and higher | 29.97 | +| | SVCBS-6 | ETRI | SVCBS-6-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBS-6 | ETRI | SVCBS-6-L2 | | | | X | | | 3 and higher | 29.97 | +| | SVCBS-7 | ETRI | SVCBS-7-L0 | X | X | | X | X | | 1.1 and higher | 29.97 | +| | SVCBS-7 | ETRI | SVCBS-7-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBS-8 | HHI | SVCBS-13-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| Spatial/
Temporal | SVCBS-8 | HHI | SVCBS-13-L1 | | | | X | | | 3 and higher | 29.97 | +| | SVCBST-1 | Vidyo | SVCBST-1-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-1 | Vidyo | SVCBST-1-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-2 | Vidyo | SVCBST-2-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-2 | Vidyo | SVCBST-2-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-3 | Vidyo | SVCBST-3-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-3 | Vidyo | SVCBST-3-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-4 | Vidyo | SVCBST-4-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-4 | Vidyo | SVCBST-4-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-5 | Vidyo | SVCBST-5-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-5 | Vidyo | SVCBST-5-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-6 | Vidyo | SVCBST-6-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-6 | Vidyo | SVCBST-6-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-7 | Vidyo | SVCBST-7-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-7 | Vidyo | SVCBST-7-L1 | | | | X | | | 4 and higher | 29.97 | + +**Table 4 – Bitstreams for the Constrained Baseline, High, High 10 Intra, Scalable Baseline, Scalable High, and Scalable High Intra profiles** + +| Categories | Bitstream | Donated by | File name | Constrained Baseline | High | High 10 Intra | Scalable Baseline | Scalable High | Scalable High Intra | Level | Frame rate (Frames/sec) | +|------------|-----------|------------|--------------|----------------------|------|---------------|-------------------|---------------|---------------------|----------------|-------------------------| +| | | | | | | | | | | | | +| | SVCBST-8 | Vidyo | SVCBST-8-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-8 | Vidyo | SVCBST-8-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-9 | Vidyo | SVCBST-9-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-9 | Vidyo | SVCBST-9-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-10 | Vidyo | SVCBST-10-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-10 | Vidyo | SVCBST-10-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-11 | Vidyo | SVCBST-11-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-11 | Vidyo | SVCBST-11-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-12 | Vidyo | SVCBST-12-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-12 | Vidyo | SVCBST-12-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-13 | Vidyo | SVCBST-13-L0 | X | X | | X | X | | 4 and higher | 29.97 | +| | SVCBST-13 | Vidyo | SVCBST-13-L1 | | | | X | | | 5 and higher | 29.97 | +| | SVCBST-14 | Vidyo | SVCBST-14-L0 | X | X | | X | X | | 3 and higher | 29.97 | +| | SVCBST-14 | Vidyo | SVCBST-14-L1 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-14 | Vidyo | SVCBST-14-L2 | | | | X | | | 5 and higher | 29.97 | +| | SVCBST-15 | Vidyo | SVCBST-15-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-15 | Vidyo | SVCBST-15-L1 | | | | X | | | 3 and higher | 29.97 | +| | SVCBST-15 | Vidyo | SVCBST-15-L2 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-16 | Vidyo | SVCBST-16-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-16 | Vidyo | SVCBST-16-L1 | | | | X | | | 3 and higher | 29.97 | +| | SVCBST-16 | Vidyo | SVCBST-16-L2 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-17 | Vidyo | SVCBST-17-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-17 | Vidyo | SVCBST-17-L1 | | | | X | | | 3 and higher | 29.97 | +| | SVCBST-17 | Vidyo | SVCBST-17-L2 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-18 | Vidyo | SVCBST-18-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | + +**Table 4 – Bitstreams for the Constrained Baseline, High, High 10 Intra, Scalable Baseline, Scalable High, and Scalable High Intra profiles** + +| Categories | Bitstream | Donated by | File name | Constrained Baseline | High | High 10 Intra | Scalable Baseline | Scalable High | Scalable High Intra | Level | Frame rate (Frames/sec) | +|------------------------------|-----------|------------|--------------|----------------------|------|---------------|-------------------|---------------|---------------------|----------------|-------------------------| +| | SVCBST-18 | Vidyo | SVCBST-18-L1 | | | | X | | | 3 and higher | 29.97 | +| | SVCBST-18 | Vidyo | SVCBST-18-L2 | | | | X | | | 4 and higher | 29.97 | +| | SVCBST-19 | HHI | SVCBST-19-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBST-19 | HHI | SVCBST-19-L1 | | | | X | | | 3 and higher | 29.97 | +| | SVCBST-20 | Thomson | SVCBST-20-L0 | X | X | | X | X | | 1.1 and higher | 14.98 | +| | SVCBST-20 | Thomson | SVCBST-20-L1 | | | | X | | | 3 and higher | 29.97 | +| MGS/
Spatial/
Temporal | SVCBMST-1 | Vidyo | SVCBMST-1-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMST-1 | Vidyo | SVCBMST-1-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMST-1 | Vidyo | SVCBMST-1-L2 | | | | X | | | 4 and higher | 29.97 | +| | SVCBMST-2 | Vidyo | SVCBMST-2-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMST-2 | Vidyo | SVCBMST-2-L1 | | | | X | | | 1.3 and higher | 29.97 | +| | SVCBMST-2 | Vidyo | SVCBMST-2-L2 | | | | X | | | 4 and higher | 29.97 | +| | SVCBMST-3 | HHI | SVCBMST-3-L0 | X | X | | X | X | | 1.3 and higher | 29.97 | +| | SVCBMST-3 | HHI | SVCBMST-3-L1 | | | | X | | | 2.1 and higher | 29.97 | +| | SVCBMST-3 | HHI | SVCBMST-3-L2 | | | | X | | | 3.1 and higher | 29.97 | +| | SVCBCTS-1 | Orange | SVCBCTS-1-L0 | X | X | | X | X | | 1.2 and higher | 12.5 | +| | SVCBCTS-1 | Orange | SVCBCTS-1-L1 | | | | X | | | 1.3 and higher | 25 | +| | SVCBCTS-1 | Orange | SVCBCTS-1-L2 | | | | X | | | 3 and higher | 25 | +| | SVCBCTS-2 | Orange | SVCBCTS-2-L0 | X | X | | X | X | | 1.2 and higher | 12.5 | +| | SVCBCTS-2 | Orange | SVCBCTS-2-L1 | | | | X | | | 1.3 and higher | 25 | +| | SVCBCTS-2 | Orange | SVCBCTS-2-L2 | | | | X | | | 3 and higher | 25 | +| | SVCBCTS-3 | Sharp | SVCBCTS-3-L0 | X | X | | X | X | | 1.3 and higher | 25 | +| | SVCBCTS-3 | Sharp | SVCBCTS-3-L1 | | | | X | | | 1.3 and higher | 25 | +| | SVCBCTS-3 | Sharp | SVCBCTS-3-L2 | | | | X | | | 3 and higher | 25 | + +**Table 4 – Bitstreams for the Constrained Baseline, High, High 10 Intra, Scalable Baseline, Scalable High, and Scalable High Intra profiles** + +| Categories | Bitstream | Donated by | File name | C | H | I | S | SH | SHI | Level | Frame rate (Frames/sec) | +|----------------------|-----------|------------|--------------|----------------------|------|---------------|-------------------|---------------|---------------------|----------------|-------------------------| +| | | | | Constrained Baseline | High | High 10 Intra | Scalable Baseline | Scalable High | Scalable High Intra | | | +| | SVCBSTC-1 | Sharp | SVCBSTC-1-L0 | X | X | | X | X | | 1.3 and higher | 25 | +| | SVCBSTC-1 | Sharp | SVCBSTC-1-L1 | | | | X | | | 3 and higher | 25 | +| | SVCBSTC-1 | Sharp | SVCBSTC-1-L2 | | | | X | | | 3.1 and higher | 25 | +| MGS | SVCHM-1 | HHI | SVCHM-1-L0 | | X | | | X | | 1.3 and higher | 29.97 | +| | SVCHM-1 | HHI | SVCHM-1-L1 | | | | | X | | 1.3 and higher | 29.97 | +| | SVCHM-1 | HHI | SVCHM-1-L2 | | | | | X | | 3 and higher | 29.97 | +| | SVCHM-1 | HHI | SVCHM-1-L3 | | | | | X | | 3 and higher | 29.97 | +| | SVCHM-2 | Sharp | SVCHM-2-L0 | | X | | | X | | 3 and higher | 25 | +| | SVCHM-2 | Sharp | SVCHM-2-L1 | | | | | X | | 3 and higher | 25 | +| | SVCHM-3 | Sharp | SVCHM-3-L0 | | X | | | X | | 3 and higher | 25 | +| | SVCHM-3 | Sharp | SVCHM-3-L1 | | | | | X | | 3 and higher | 25 | +| | SVCHM-4 | Sharp | SVCHM-4-L0 | | X | | | X | | 3 and higher | 25 | +| | SVCHM-4 | Sharp | SVCHM-4-L1 | | | | | X | | 3 and higher | 25 | +| | SVCHM-4 | Sharp | SVCHM-4-L2 | | | | | X | | 3.1 and higher | 25 | +| Spatial | SVCHS-1 | Thomson | SVCHS-1-L0 | X | X | | X | X | | 2.1 and higher | 25 | +| | SVCHS-1 | Thomson | SVCHS-1-L1 | | | | | X | | 3.1 and higher | 25 | +| | SVCHS-2 | Thomson | SVCHS-2-L0 | | X | | | X | | 1.3 and higher | 25 | +| | SVCHS-2 | Thomson | SVCHS-2-L1 | | | | | X | | 3.1 and higher | 25 | +| Spatial/
Temporal | SVCHST-1 | Orange | SVCHST-1-L0 | | X | | | X | | 3 and higher | 25 | +| | SVCHST-1 | Orange | SVCHST-1-L1 | | | | | X | | 3.2 and higher | 50 | +| | SVCHST-1 | Orange | SVCHST-1-L2 | | | | | X | | 5 and higher | 50 | +| | SVCHST-2 | Orange | SVCHST-2-L0 | | X | | | X | | 3 and higher | 25 | +| | SVCHST-2 | Orange | SVCHST-2-L1 | | | | | X | | 3.2 and higher | 50 | +| | SVCHST-2 | Orange | SVCHST-2-L2 | | | | | X | | 4.2 and higher | 50 | +| | SVCHST-3 | Thomson | SVCHST-3-L0 | | X | | | X | | 3.1 and higher | 25 | + +**Table 4 – Bitstreams for the Constrained Baseline, High, High 10 Intra, Scalable Baseline, Scalable High, and Scalable High Intra profiles** + +| Categories | Bitstream | Donated by | File name | Constrained Baseline | High | High 10 Intra | Scalable Baseline | Scalable High | Scalable High Intra | Level | Frame rate (Frames/sec) | +|------------------------------|-----------|------------|--------------|----------------------|------|---------------|-------------------|---------------|---------------------|----------------|-------------------------| +| | | | | | | | | | | | | +| | SVCHST-3 | Thomson | SVCHST-3-L1 | | | | | X | | 5 and higher | 50 | +| | SVCHST-4 | Thomson | SVCHST-4-L0 | | X | | | X | | 3 and higher | 25 | +| | SVCHST-4 | Thomson | SVCHST-4-L1 | | | | | X | | 3.1 and higher | 50 | +| MGS/
Temporal/
Spatial | SVCHMTS-1 | Orange | SVCHMTS-1-L0 | | X | | | X | | 3 and higher | 25 | +| | SVCHMTS-1 | Orange | SVCHMTS-1-L1 | | | | | X | | 3 and higher | 25 | +| | SVCHMTS-1 | Orange | SVCHMTS-1-L2 | | | | | X | | 3.1 and higher | 25 | +| | SVCHMTS-1 | Orange | SVCHMTS-1-L3 | | | | | X | | 3.1 and higher | 50 | +| | SVCHMTS-1 | Orange | SVCHMTS-1-L4 | | | | | X | | 3.1 and higher | 50 | +| | SVCHMTS-1 | Orange | SVCHMTS-1-L5 | | | | | X | | 4.2 and higher | 25 | +| | SVCHMTS-2 | Sharp | SVCHMTS-2-L0 | | X | | | X | | 1.3 and higher | 29.97 | +| | SVCHMTS-2 | Sharp | SVCHMTS-2-L1 | | | | | X | | 1.3 and higher | 29.97 | +| | SVCHMTS-2 | Sharp | SVCHMTS-2-L2 | | | | | X | | 3.1 and higher | 29.97 | +| CGS/
Temporal/
Spatial | SVCHCTS-1 | Orange | SVCHCTS-1-L0 | | X | | | X | | 1.2 and higher | 12.5 | +| | SVCHCTS-1 | Orange | SVCHCTS-1-L1 | | | | | X | | 1.3 and higher | 25 | +| | SVCHCTS-1 | Orange | SVCHCTS-1-L2 | | | | | X | | 3 and higher | 25 | +| | SVCHCTS-1 | Orange | SVCHCTS-1-L3 | | | | | X | | 3 and higher | 25 | +| | SVCHCTS-1 | Orange | SVCHCTS-1-L4 | | | | | X | | 3.1 and higher | 50 | +| | SVCHCTS-1 | Orange | SVCHCTS-1-L5 | | | | | X | | 3.1 and higher | 50 | +| | SVCHCTS-1 | Orange | SVCHCTS-1-L6 | | | | | X | | 4 and higher | 50 | +| | SVCHCTS-1 | Orange | SVCHCTS-1-L7 | | | | | X | | 4 and higher | 50 | +| Spatial/
Temporal/
CGS | SVCHSTC-1 | Sharp | SVCHSTC-1-L0 | | X | | | X | | 1.3 and higher | 29.97 | +| | SVCHSTC-1 | Sharp | SVCHSTC-1-L1 | | | | | X | | 1.3 and higher | 29.97 | +| | SVCHSTC-1 | Sharp | SVCHSTC-1-L2 | | | | | X | | 3.1 and higher | 29.97 | + +**Table 4 – Bitstreams for the Constrained Baseline, High, High 10 Intra, Scalable Baseline, Scalable High, and Scalable High Intra profiles** + +| Categories | Bitstream | Donated by | File name | Constrained Baseline | High | High 10 Intra | Scalable Baseline | Scalable High | Scalable High Intra | Level | Frame rate (Frames/sec) | +|-----------------|-----------|------------|--------------|----------------------|------|---------------|-------------------|---------------|---------------------|----------------|-------------------------| +| | | | | | | | | | | | | +| Spatial | SVCHIS-1 | Thomson | SVCHIS-1-L0 | | X | X | | X | X | 2.1 and higher | 25 | +| | SVCHIS-1 | Thomson | SVCHIS-1-L1 | | | | | X | X | 3.1 and higher | 25 | +| | SVCHIS-1 | Thomson | SVCHIS-1-L2 | | | | | X | X | 4 and higher | 25 | +| | SVCHIS-2 | Thomson | SVCHIS-2-L0 | | X | X | | X | X | 3 and higher | 25 | +| | SVCHIS-2 | Thomson | SVCHIS-2-L1 | | | | | X | X | 3.1 and higher | 25 | +| | SVCHIS-2 | Thomson | SVCHIS-2-L2 | | | | | X | X | 4.2 and higher | 25 | +| | SVCHIS-3 | Thomson | SVCHIS-3-L0 | | X | X | | X | X | 3 and higher | 25 | +| | SVCHIS-3 | Thomson | SVCHIS-3-L1 | | | | | X | X | 3.1 and higher | 25 | +| | SVCHIS-3 | Thomson | SVCHIS-3-L2 | | | | | X | X | 4 and higher | 25 | +| CGS/
Spatial | SVCHICS-1 | Sharp | SVCHICS-1-L0 | | X | X | | X | X | 1.3 and higher | 29.97 | +| | SVCHICS-1 | Sharp | SVCHICS-1-L1 | | | | | X | X | 1.3 and higher | 29.97 | +| | SVCHICS-1 | Sharp | SVCHICS-1-L2 | | | | | X | X | 3.1 and higher | 29.97 | +| | SVCHICS-1 | Sharp | SVCHICS-1-L3 | | | | | X | X | 3.1 and higher | 29.97 | + +**Table 5 – Bitstreams for the Multiview High and Stereo High profiles** + +| Categories | Bitstream | Donated by | File name | Multiview High | Stereo High | Level | Frame rate (Frame/Sec) | +|-------------------------------------|-----------|------------|-----------|----------------|-------------|----------------|------------------------| +| Dependency Structure | MVCDS-1 | NTT | MVCDS-1 | X | X | 3 and higher | 29.97 | +| | MVCDS-2 | NTT | MVCDS-2 | X | X | 3 and higher | 29.97 | +| | MVCDS-3 | NTT | MVCDS-3 | X | X | 3 and higher | 29.97 | +| | MVCDS-4 | Mitsubishi | MVCDS-4 | X | X | 3.1 and higher | 25 | +| | MVCDS-5 | Mitsubishi | MVCDS-5 | X | X | 3.1 and higher | 25 | +| | MVCDS-6 | Mitsubishi | MVCDS-6 | X | X | 3.1 and higher | 25 | +| Number of Views | MVCNV-1 | NTT | MVCNV-1 | X | | 3 and higher | 29.97 | +| | MVCNV-2 | Mitsubishi | MVCNV-2 | X | | 4 and higher | 25 | +| | MVCNV-3 | Mitsubishi | MVCNV-3 | X | | 3.1 and higher | 25 | +| | MVCNV-4 | NTT | MVCNV-4 | X | | 3 and higher | 29.97 | +| Reference Picture List Construction | MVCRP-1 | Qualcomm | MVCRP-1 | X | X | 3 and higher | 25 | +| | MVCRP-2 | Qualcomm | MVCRP-2 | X | X | 3 and higher | 25 | +| | MVCRP-3 | Qualcomm | MVCRP-3 | X | X | 3 and higher | 25 | +| | MVCRP-4 | Qualcomm | MVCRP-4 | X | X | 3 and higher | 25 | +| | MVCRP-5 | Qualcomm | MVCRP-5 | X | X | 3 and higher | 25 | +| | MVCRP-6 | Qualcomm | MVCRP-6 | X | X | 3 and higher | 25 | +| Subset SPS | MVCSPS-1 | Mitsubishi | MVCSPS-1 | X | X | 3.1 and higher | 25 | +| | MVCSPS-2 | Mitsubishi | MVCSPS-2 | X | | 3.1 and higher | 25 | +| Interlaced Coding Tools | MVCICT-1 | Panasonic | MVCICT-1 | | X | 3.1 and higher | 29.97 | +| | MVCICT-2 | Panasonic | MVCICT-2 | | X | 3.1 and higher | 29.97 | + +**Table 6 – Bitstreams for the Multiview Depth High profiles** + +| Categories | Bitstream | Donated by | File name | Multi-view Depth High | Level | Frame rate (Frame/Sec) | +|---------------------------------------------------|-----------|----------------|------------|-----------------------|----------------|------------------------| +| Depth Resolution | MVDDR-1 | Nokia | MVDDR-1_r2 | X | 3 and higher | 30 | +| | MVDDR-2 | Nokia | MVDDR-2_r2 | X | 4 and higher | 25 | +| | MVDDR-3 | Sony | MVDDR-3_r1 | X | 3 and higher | 30 | +| | MVDDR-4 | Sony | MVDDR-4_r1 | X | 4 and higher | 25 | +| Views Configuration | MVDVC-1 | Sony | MVDVC-1_r1 | X | 3 and higher | 30 | +| | MVDVC-2 | Sony | MVDVC-2_r2 | X | 4 and higher | 25 | +| | MVDVC-3 | Nokia | MVDVC-3_r1 | X | 3 and higher | 30 | +| | MVDVC-4 | Nokia | MVDVC-4_r1 | X | 4 and higher | 25 | +| Inter View Prediction / temporal inter prediction | MVDIV-1 | Nokia | MVDIV-1_r1 | X | 4 and higher | 25 | +| | MVDIV-2 | Sony | MVDIV-2_r1 | X | 3 and higher | 30 | +| | MVDIV-3 | MERL, Qualcomm | MVDIV-3_r1 | X | 5.1 and higher | 25 | +| | MVDIV-4 | MERL, Qualcomm | MVDIV-4_r1 | X | 5.1 and higher | 30 | +| Interlaced Coding Tools | MVDIL-1 | ITRI, Sony | MVDIL-1_r1 | X | 3.1 and higher | 30 | +| | MVDIL-2 | ITRI | MVDIL-2_r1 | X | 4.1 and higher | 15 | +| MVD representation and SEI | MVDRS-1 | Nokia | MVDRS-1_r1 | X | 3 and higher | 30 | +| Three view prediction structure | MVPCT-1 | MERL | MVPCT-1_r1 | X | 3 and higher | 30 | +| | MVPCT-2 | LGE | MVPCT-2 | X | 4 and higher | 25 | + +**Table 7 – Bitstreams for the MFC High profiles** + +| Categories | Bitstream | Donated by | File name | MFC High | Level | Frame rate (Frame/Sec) | +|-----------------------------|-----------|------------|-----------|----------|-------|------------------------| +| RPU Operational Modes | MFCRFT-1 | Dolby | MFCRFT-1 | X | 4.1 | 24p | +| | MFCRFT-2 | Dolby | MFCRFT-2 | X | 4.1 | 24p | +| RPU Interlaced Coding Tools | MFCFLD-1 | Dolby | MFCFLD-1 | X | 4.1 | 50i | +| | MFCFLD-2 | Dolby | MFCFLD-2 | X | 4.1 | 50i | +| | MFCFLD-3 | Dolby | MFCFLD-3 | X | 4.1 | 50i | +| MFC Format | MFCFM-1 | Dolby | MFCFM-1 | X | 4.1 | 24p | +| Grid Position | MFCGRD-1 | Dolby | MFCGRD-1 | X | 4.1 | 24p | + +**Table 8 – Bitstreams for the 3D-AVC High profiles** + +| Categories | Bitstream | Donated by | File Name | Enhanced Multiview Depth High | Level | Frame Rate (Frame/Sec) | +|------------------|-----------|------------|--------------|-------------------------------|--------------|------------------------| +| Depth Resolution | MVDDR3D-1 | Nokia | MVDDR3D-1_r1 | X | 3 and higher | 30 | +| | MVDDR3D-2 | Nokia | MVDDR3D-2_r1 | X | 4 and higher | 25 | +| Coding tools | MVDCT-1 | MERL | MVDCT-1_r2 | X | 3 and higher | 30 | +| | MVDCT-2 | Mediatek | MVDCT-2_r2 | X | 4 and higher | 25 | +| | MVDCT-3 | Samsung | MVDCT-3_r1 | X | 3 and higher | 30 | +| | MVDCT-4 | Poznan | MVDCT-4_r2 | X | 4 and higher | 25 | +| | MVDCT-5 | Qualcomm | MVDCT-5_r1 | X | 4 and higher | 25 | +| | MVDCT-6 | Qualcomm | MVDCT-6_r1 | X | 3 and higher | 30 | +| | MVDCT-7 | Qualcomm | MVDCT-7_r1 | X | 4 and higher | 25 | +| | MVDCT-8 | Qualcomm | MVDCT-8_r2 | X | 3 and higher | 30 | +| | MVDCT-9 | Samsung | MVDCT-9_r1 | X | 4 and higher | 25 | +| | MVDCT-10 | Qualcomm | MVDCT-10_r2 | X | 4 and higher | 25 | + +**Table 9 – Bitstreams for the MFC Depth High profiles** + +| Categories | Bitstream | Donated by | File Name | MFC Depth High | Level | Frame Rate (Frame/Sec) | +|--------------------------------|-----------|------------|-----------|----------------|-------|------------------------| +| Depth Resolution | MFCDDR-1 | Dolby | MFCDDR-1 | X | 4.1 | 25p | +| | MFCDDR-2 | Dolby | MFCDDR-2 | X | 4.1 | 25p | +| Interlaced Coding Tools | MFCDFLD-1 | Dolby | MFCDFLD-1 | X | 4.1 | 50i | +| | MFCDFLD-2 | Dolby | MFCDFLD-2 | X | 4.1 | 50i | +| Texture and Depth Coding Order | MFCDTDC-1 | Dolby | MFCDTDC-1 | X | 4.1 | 25p | +| | MFCDTDC-2 | Dolby | MFCDTDC-2 | X | 4.1 | 25p | +| MFC format | MFCDMFC-1 | Dolby | MFCDMFC-1 | X | 4.1 | 25p | + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.265.1-201810-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.265.1-201810-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f380e60b4f31af2b3873ce60e2ee8b09b152e86b --- /dev/null +++ b/marked/H/T-REC-H.265.1-201810-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07bb4cb4bb9deb953cabe9f28e8e701a29779be242b2eacd7e694bbf9b8d2b8a +size 6849 diff --git a/marked/H/T-REC-H.265.2-201612-I_PDF-E/raw.md b/marked/H/T-REC-H.265.2-201612-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6f3b530b7b6cd274ca0da2730cac75b4052d34fa --- /dev/null +++ b/marked/H/T-REC-H.265.2-201612-I_PDF-E/raw.md @@ -0,0 +1,298 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.265.2** + +(12/2016) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Coding of moving +video + +--- + +**Reference software for ITU-T H.265 high +efficiency video coding** + +Recommendation ITU-T H.265.2 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking through it, symbolizing global communication. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font, with "ITU" in a larger, bold font above it. + +ITU logo + +International +Telecommunication +Union + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Reference software for ITU-T H.265 high efficiency video coding + +## Summary + +Recommendation ITU-T H.265.2 contains an accompanying reference software for Rec. ITU-T H.265 | ISO/IEC 23008-2 *High efficiency video coding*. The reference software includes both encoder and decoder functionality. + +Reference software is useful in aiding users of a video coding standard to establish and test conformance and interoperability, and to educate users and demonstrate the capabilities of the standard. For these purposes, the accompanying software is provided as an aid for the study and implementation of Rec. ITU-T H.265 | ISO/IEC 23008-2. This edition of ITU-T H.265.2 matches the technical descriptions in the second edition of ITU-T H.265 (2014-10). + +The software has been jointly developed by the ITU-T Video Coding Experts Group (VCEG, Question 6 of ITU-T Study Group 16) and the ISO/IEC Moving Picture Experts Group (MPEG, Working Group 11 of Subcommittee 29 of ISO/IEC Joint Technical Committee 1). It was developed jointly with MPEG and corresponds in a technically aligned manner to ISO/IEC 23008-5. + +The Reference source code for ITU-T H.265.2 is found in the electronic attachment to this Recommendation. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.265.2 | 2014-10-14 | 16 | 11.1002/1000/12298 | +| 2.0 | ITU-T H.265.2 | 2016-02-13 | 16 | 11.1002/1000/12645 | +| 3.0 | ITU-T H.265.2 (V3) | 2016-12-22 | 16 | 11.1002/1000/12947 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------------|-------------| +| 0.1 Purpose | iv | +| 0.2 Examples of use | iv | +| 0.3 Warranty disclaimer | iv | +| 1 Scope | 1 | +| 2 References | 1 | +| 2.1 Normative references | 1 | +| 2.2 Additional references | 1 | +| 3 Definitions | 1 | +| 4 Abbreviations | 2 | +| 5 Conventions | 2 | +| 6 Reference software for Rec. ITU-T H.265 ISO/IEC 23008-2 | 2 | + +Electronic attachment: Reference source code + +# Introduction + +## 0.1 Purpose + +The purpose of this Recommendation | International Standard is to provide the following: + +- Reference decoder software capable of decoding bitstreams that conform to Rec. ITU-T H.265 | ISO/IEC 23008-2 in a manner that conforms to the decoding process specified in Rec. ITU-T H.265 | ISO/IEC 23008-2. +- Reference encoder software capable of producing bitstreams that conform to Rec. ITU-T H.265 | ISO/IEC 23008-2. + +## 0.2 Examples of use + +Some examples of use that may be appropriate for the reference decoder software are as follows: + +- As an illustration of how to perform the decoding process specified in Rec. ITU-T H.265 | ISO/IEC 23008-2. +- As the starting basis for the implementation of a decoder that conforms to Rec. ITU-T H.265 | ISO/IEC 23008-2. +- For testing the conformance of a decoder implementation with the decoding process specified in Rec. ITU-T H.265 | ISO/IEC 23008-2 (as the values of the samples in all decoded pictures and the relative ordering of those pictures will be identical from all conforming decoder implementations that support the profile and level used in a bitstream that conforms to Rec. ITU-T H.265 | ISO/IEC 23008-2). +- For testing the conformance of a bitstream to the constraints specified for bitstream conformance in Rec. ITU-T H.265 | ISO/IEC 23008-2, as the software can detect and report many bitstream conformance violations. + +NOTE 1 – However, the lack of the detection of any conformance violation by the reference decoder software should not be considered as definitive proof that the bitstream conforms to all constraints specified for bitstream conformance in Rec. ITU-T H.265 | ISO/IEC 23008-2. + +Some examples of use that may be appropriate for the reference encoder software are as follows: + +- As an illustration of how to perform an encoding process that produces bitstreams that conform to the constraints specified for bitstream conformance in Rec. ITU-T H.265 | ISO/IEC 23008-2. +- As the starting basis for the implementation of an encoder that conforms to Rec. ITU-T H.265 | ISO/IEC 23008-2. +- As a means of generating bitstreams for testing the conformance of a decoder implementation with the decoding process specified in Rec. ITU-T H.265 | ISO/IEC 23008-2. +- As a means of evaluating and demonstrating examples of the quality that can be achieved by an encoding process that conforms to Rec. ITU-T H.265 | ISO/IEC 23008-2. + +NOTE 2 – However, no guarantee of the quality that will be achieved by an encoder is provided by its conformance to Rec. ITU-T H.265 | ISO/IEC 23008-2, as the conformance of an encoder to Rec. ITU-T H.265 | ISO/IEC 23008-2 is defined only in terms of format constraints imposed on the bitstream syntax. Thus, while the reference encoder software may suffice to provide some illustrative examples of what quality can be achieved in conformance to Rec. ITU-T H.265 | ISO/IEC 23008-2, it provides neither an assurance of minimum guaranteed video encoding quality nor maximum achievable video encoding quality. + +## 0.3 Warranty disclaimer + +Regardless of any and all statements made herein or elsewhere regarding the possible uses of the reference software, the following disclaimers of warranty apply to the provided reference software. + +- ITU and ISO/IEC disclaim any and all warranties, whether express, implied, or statutory, including any implied warranties of merchantability or of fitness for a particular purpose. +- In no event shall the contributor(s), ISO/IEC or ITU be liable for any incidental, punitive, or consequential damages of any kind whatsoever arising from the use of these programs. +- This disclaimer of warranty extends to the user of these programs and user's customers, employees, agents, transferees, successors and assignees. +- ITU does not represent or warrant that the programs furnished hereunder are free of infringement of any third-party patents. + +- Commercial implementations of ISO/IEC International Standards | ITU-T Recommendations, including shareware, may be subject to royalty fees to patent holders. +- Information regarding the common patent policy for ITU-T/ITU-R/ISO/IEC is available from the ITU website at . + + + +# Reference software for ITU-T H.265 high efficiency video coding + +# 1 Scope + +This Recommendation | International Standard provides accompanying reference software for Rec. ITU-T H.265 | ISO/IEC 23008-2 as an electronic attachment. The software is an integral part of this Recommendation | International Standard. + +The use of this reference software is not required for making an implementation of an encoder or decoder in conformance to Rec. ITU-T H.265 | ISO/IEC 23008-2. Requirements established in Rec. ITU-T H.265 | ISO/IEC 23008-2 take precedence over the behaviour of the reference software. + +# 2 References + +## 2.1 Normative references + +The following Recommendations and International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this Recommendation | International Standard are encouraged to investigate the possibility of applying the most recent edition of the Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently valid ITU-T Recommendations. + +### 2.1.1 ITU-T Recommendations + +None. + +### 2.1.2 Identical Recommendations | International Standards + +None. + +### 2.1.3 Paired Recommendations | International Standards equivalent in technical content + +- Recommendation ITU-T H.265 (in force), *High efficiency video coding*. +ISO/IEC 23008-2 (in force), *Information technology – High efficiency coding and media delivery in heterogeneous environments – Part 2: High efficiency video coding*. + +## 2.2 Additional references + +None. + +# 3 Definitions + +For the purposes of this Recommendation, the terms, definitions, abbreviations and symbols specified in Rec. ITU-T H.265 | ISO/IEC 23008-2 (particularly in clause 3) apply. Definitions 3.1, 3.2, and 3.3 below replace the corresponding definitions in Rec. ITU-T H.265 | ISO/IEC 23008-2. Definitions 3.4 and 3.5 are additional definitions. + +**3.1 bitstream:** A sequence of bits that may conform to Rec. ITU-T H.265 | ISO/IEC 23008-2. A bitstream that conforms to Rec. ITU-T H.265 | ISO/IEC 23008-2 will contain one or more slices. + +**3.2 decoder:** An embodiment of a process that operates on a bitstream and may conform to the decoding process requirements specified for conformance to Rec. ITU-T H.265 | ISO/IEC 23008-2. The scope of decoder, as considered herein, does not include a display process, which is outside the scope of this Recommendation | International Standard. + +**3.3 encoder:** An embodiment of a process, not specified in this Recommendation | International Standard, that produces a bitstream. + +**3.4 reference software decoder:** The decoding software accompanying this Recommendation | International Standard. + +**3.5 reference software encoder:** The encoding software accompanying this Recommendation | International Standard. + +# **4 Abbreviations** + +For the purposes of this Recommendation | International Standard, relevant abbreviations are specified in clause 4 of Rec. ITU-T H.265 | ISO/IEC 23008-2. + +# **5 Conventions** + +For the purposes of this Recommendation | International Standard, relevant conventions are specified in clause 5 of Rec. ITU-T H.265 | ISO/IEC 23008-2. + +# **6 Reference software for Rec. ITU-T H.265 | ISO/IEC 23008-2** + +The reference software for Rec. ITU-T H.265 | ISO/IEC 23008-2 is found in the electronic attachment to this Recommendation | International Standard. + +The attached software package contains four parts: + +- HM software: Support for the following profiles: + - the Main, Main 10, and Main Still Picture profiles + - the Monochrome, Monochrome 12 and Monochrome 16 profiles + - the Main 12 profile + - the Main 4:2:2 10 and Main 4:2:2 12 profiles + - the Main 4:4:4, Main 4:4:4 10, and Main 4:4:4 12 profiles + - the Main 4:4:4 Still Picture and Main 4:4:4 16 Still Picture profiles + - the Main Intra, Main 10 Intra, Main 12 Intra, Main 4:2:2 10 Intra, Main 4:2:2 12 Intra, Main 4:4:4 Intra, Main 4:4:4 10 Intra, Main 4:4:4 12 Intra, and Main 4:4:4 16 Intra profiles + - the High Throughput 4:4:4 16 Intra profile +- SHM software: Support for the Scalable Main, the Scalable Main 10, Scalable Monochrome, Scalable Monochrome 12, Scalable Monochrome 16, and Scalable Main 4:4:4 profiles +- HTM software: Support for the Multiview Main and 3D Main profiles +- HM+SCC software: Support for the following profiles: + - Screen-Extended Main and Screen-Extended Main 10 profiles + - Screen-Extended Main 4:4:4 and Screen-Extended Main 4:4:4 10 profiles + - Screen-Extended High Throughput 4:4:4, Screen-Extended High Throughput 4:4:4 10, and Screen-Extended High Throughput 14 profiles + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.266.1-202601-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.266.1-202601-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25f8fbfaef317942ed3102c74b40a7d42f80608b --- /dev/null +++ b/marked/H/T-REC-H.266.1-202601-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83cab7dcabfe939b223d97242d8523e461968d21f7c5432693c30a64f2d95521 +size 7050 diff --git a/marked/H/T-REC-H.266.1-202601-I_PDF-E/raw.md b/marked/H/T-REC-H.266.1-202601-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5457419aefff7141c85604051dc7158c1c5dc512 --- /dev/null +++ b/marked/H/T-REC-H.266.1-202601-I_PDF-E/raw.md @@ -0,0 +1,4666 @@ + + +# Recommendation + +## **ITU-T H.266.1 (V3) (01/2026)** + +SERIES H: Audiovisual and multimedia systems + +Infrastructure of audiovisual services – Coding of moving video + +# --- **Conformance specification for ITU-T H.266 versatile video coding** + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circle with a globe-like grid pattern. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +## **Audiovisual and multimedia systems** + +| | | +|-------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| General | H.200-H.219 | +| Transmission multiplexing and synchronization | H.220-H.229 | +| Systems aspects | H.230-H.239 | +| Communication procedures | H.240-H.259 | +| Coding of moving video | H.260-H.279 | +| Related systems aspects | H.280-H.299 | +| Systems and terminal equipment for audiovisual services | H.300-H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350-H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360-H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420-H.439 | +| Supplementary services for multimedia | H.450-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Conformance specification for ITU-T H.266 versatile video coding + +# Summary + +Recommendation ITU-T H.266.1 "Conformance specification for ITU-T H.266 versatile video coding" specifies tests for (non-exhaustive) testing to verify whether bitstreams and decoders meet the normative requirements specified in Rec. ITU-T H.266 | ISO/IEC 23090-3 Versatile video coding (VVC). The bitstreams provided with this document correspond to the 01/2026 (V3) edition of Rec. ITU-T H.266. Relative to the previous (second) edition, this version adds bitstreams for the Multilayer Main 10 profile. + +This Recommendation was developed collaboratively with ISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information, and corresponds with ISO/IEC 23090-15 as technically aligned twin text. + +The conformance bitstreams needed for this Recommendation are available at: +. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|--------------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.266.1 | 2022-04-29 | 16 | 11.1002/1000/14969 | +| 2.0 | ITU-T H.266.1 (V2) | 2023-09-13 | 16 | 11.1002/1000/15649 | +| 3.0 | ITU-T H.266.1 (V3) | 2026-01-13 | 21 | 11.1002/1000/16663 | + +## Keywords + +Conformance, H.266, testing, versatile video coding, VVC. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2026 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | | Page | +|--------|-----------------------------------------------------------------------------------------------------------------|-------------| +| 1 | Scope..... | 1 | +| 2 | Normative references ..... | 1 | +| 2.1 | General..... | 1 | +| 2.2 | Identical Recommendations International Standards ..... | 1 | +| 2.3 | Paired Recommendations International Standards equivalent in technical content ..... | 1 | +| 3 | Definitions..... | 1 | +| 4 | Abbreviations ..... | 2 | +| 5 | Conventions ..... | 2 | +| 6 | Conformance testing for ITU-T H.266 ISO/IEC 23090-3..... | 3 | +| 6.1 | Introduction..... | 3 | +| 6.2 | Bitstream conformance ..... | 3 | +| 6.3 | Decoder conformance ..... | 3 | +| 6.4 | Procedure to test bitstreams ..... | 3 | +| 6.5 | Procedure to test decoder conformance ..... | 3 | +| 6.5.1 | Conformance bitstreams ..... | 3 | +| 6.5.2 | Contents of the bitstream file ..... | 3 | +| 6.5.3 | Requirements on output of the decoding process and timing ..... | 4 | +| 6.5.4 | Static tests for output order conformance ..... | 4 | +| 6.5.5 | Dynamic tests for output timing conformance..... | 4 | +| 6.5.6 | Decoder conformance test for a particular profile, tier, and level..... | 5 | +| 6.6 | Specification of the test bitstreams ..... | 5 | +| 6.6.1 | General..... | 5 | +| 6.6.2 | Test bitstreams – Coding tools for Main 10 profile with 4:2:0 chroma format and 10 bit depth ..... | 5 | +| 6.6.3 | Test bitstreams – High-level syntax features for Main 10 profile with 4:2:0 chroma format and 10 bit depth..... | 29 | +| 6.6.4 | Test bitstreams – Additional chroma formats and bit depths for Main 10 profile ..... | 40 | +| 6.6.5 | Test bitstreams – Coding tools for Main 10 4:4:4 profile for 4:4:4 chroma format and 10 bit depth ..... | 41 | +| 6.6.6 | Test bitstreams – Additional chroma formats and bit depths for Main 10 4:4:4 profile ..... | 44 | +| 6.6.7 | Test bitstreams – Multilayer Main 10 profile ..... | 48 | +| 6.6.8 | Test bitstreams – Multilayer Main 10 4:4:4 profile ..... | 50 | +| 6.6.9 | Test bitstreams – Main 10 Still Picture profile ..... | 50 | +| 6.6.10 | Test bitstreams – Main 10 4:4:4 Still Picture profile ..... | 50 | +| 6.6.11 | Test bitstreams – Main 12 profile ..... | 51 | +| 6.6.12 | Test bitstreams – Main 12 Intra profile..... | 51 | +| 6.6.13 | Test bitstreams – Main 12 Still Picture profile ..... | 51 | +| 6.6.14 | Test bitstreams – Main 12 4:4:4 profile ..... | 51 | +| 6.6.15 | Test bitstreams – Main 12 4:4:4 Intra profile..... | 55 | +| 6.6.16 | Test bitstreams – Main 12 4:4:4 Still Picture profile ..... | 57 | +| 6.6.17 | Test bitstreams – Main 16 4:4:4 profile ..... | 59 | +| 6.6.18 | Test bitstreams – Main 16 4:4:4 Intra profile..... | 64 | +| 6.6.19 | Test bitstreams – Main 16 4:4:4 Still Picture profile ..... | 66 | +| 6.7 | Conformance test suites for Rec. ITU-T H.266 ISO/IEC 23090-3 ..... | 68 | +| 6.7.1 | Bitstreams for Main 10 profile..... | 68 | +| 6.7.2 | Bitstreams for Main 10 4:4:4 profile..... | 72 | +| 6.7.3 | Bitstreams for Multilayer Main 10 profile..... | 73 | +| 6.7.4 | Bitstreams for Multilayer Main 10 4:4:4 profile..... | 73 | +| 6.7.5 | Bitstreams for Main 10 Still Picture profile..... | 73 | +| 6.7.6 | Bitstreams for Main 10 4:4:4 Still Picture profile..... | 73 | +| 6.7.7 | Bitstreams for Main 12 profile..... | 74 | +| 6.7.8 | Bitstreams for Main 12 Intra profile ..... | 74 | +| 6.7.9 | Bitstreams for Main 12 Still Picture profile..... | 74 | +| 6.7.10 | Bitstreams for Main 12 4:4:4 profile..... | 74 | +| 6.7.11 | Bitstreams for Main 12 4:4:4 Intra profile ..... | 74 | +| 6.7.12 | Bitstreams for Main 12 4:4:4 Still Picture profile..... | 75 | +| 6.7.13 | Bitstreams for Main 16 4:4:4 profile..... | 75 | + +| | Page | +|----------------------------------------------------------------|-------------| +| 6.7.14 Bitstreams for Main 16 4:4:4 Intra profile ..... | 75 | +| 6.7.15 Bitstreams for Main 16 4:4:4 Still Picture profile..... | 76 | + +# Conformance specification for ITU-T H.266 versatile video coding + +# 1 Scope + +This Recommendation | International Standard1 specifies a set of tests and procedures designed to indicate whether encoders or decoders meet the normative requirements specified in Rec. ITU-T H.266 | ISO/IEC 23090-3. + +# 2 Normative references + +## 2.1 General + +The following Recommendations and International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this Recommendation | International Standard are encouraged to investigate the possibility of applying the most recent edition of the Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently valid ITU-T Recommendations. + +## 2.2 Identical Recommendations | International Standards + +- None. + +## 2.3 Paired Recommendations | International Standards equivalent in technical content + +- Recommendation ITU-T H.266 (in force), *Versatile video coding*. +ISO/IEC 23090-3:in force, *Information technology – Coded representation of immersive media– Part 3: Versatile video coding*. +- Recommendation ITU-T H.266.2 (in force), *Reference software for ITU-T H.266 Versatile video coding*. +ISO/IEC 23090-16:in force, *Information technology – Coded representation of immersive media – Part 16: Reference software for versatile video coding*. + +# 3 Definitions + +For the purposes of this Recommendation | International Standard, the terms, definitions, abbreviations and symbols specified in Rec. ITU-T H.266 | ISO/IEC 23090-3 (particularly in clause 3) apply. The following modified terms and additional terms are provided for purposes herein: + +- 3.1 **bitstream**: A Rec. ITU-T H.266 | ISO/IEC 23090-3 video bitstream. +- 3.2 **decoder**: A Rec. ITU-T H.266 | ISO/IEC 23090-3 video decoder, i.e., an embodiment of the decoding process specified by Rec. ITU-T H.266 | ISO/IEC 23090-3. The decoder does not include the display process, which is outside the scope of this Recommendation | International Standard. +- 3.3 **encoder**: An embodiment of a process, not specified in this Recommendation | International Standard (except in regard to identification of the reference software encoder), that produces a bitstream. +- 3.4 **reference software decoder**: The software decoder provided in Rec. ITU-T H.266.2 | ISO/IEC 23090-16. +- 3.5 **reference software encoder**: The software encoder provided in Rec. ITU-T H.266.2 | ISO/IEC 23090-16. +- 3.6 **VVCv1 tools**: Coding tools included in the Multilayer Main 10 4:4:4 profile of Versatile Video Coding (VVC), specified in Rec. ITU-T H.266 | ISO/IEC 23090-3. +- 3.7 **VVCv2 tools**: The EPP, ERRc, PRRC, ETSRC and RLSCP coding tools added in the VVC operation range extensions specified in the second edition of Rec. ITU-T H.266 | ISO/IEC 23090-3. + +--- + +1 This Recommendation | International Standard includes an electronic attachment containing the conformance bitstreams identified within the text. The conformance bitstreams needed for this Recommendation are available in the ITU-T Test Signals Database at the following link: . + +# 4 Abbreviations + +For the purposes of this Recommendation | International Standard, relevant abbreviations and acronyms specified in clause 4 of Rec. ITU-T H.266 | ISO/IEC 23090-3 and the following abbreviations apply. + +| | | +|--------|---------------------------------------------------| +| AMVP | Adaptive Motion Vector Prediction | +| CCLM | Cross-Component Linear Model | +| CIIP | Combined Inter/Intra Prediction | +| CST | Chroma Separate Tree | +| CTC | Common Test Conditions | +| DCT | Discrete Cosine Transform | +| DMVR | Decoder-side Motion Vector Refinement | +| DQ | Dependent Quantization | +| DST | Discrete Sine Transform | +| EPP | Extended Precision Processing | +| ERRC | Extended Regular Residual Coding | +| ETSRC | Extended Transform Skip Residual Coding | +| FTP | File Transfer Protocol | +| ISP | Intra Subblock Partitioning | +| JCCR | Joint Coding of Chroma Residuals | +| MMVD | Merge with MVD | +| MPM | Most Probable Mode | +| MRL | Multiple Reference Line | +| MVD | Motion Vector Difference | +| NUT | NAL Unit Type | +| PDPC | Position-Dependent (intra) Prediction Combination | +| PERP | Padded Equirectangular Projection | +| PRRC | Persistent Regular Residual Coding | +| RA | Random Access | +| RLSCP | Reversed Last Significant Coefficient Position | +| RPR | Reference Picture Resampling | +| RRC | Regular Residual Coding | +| SAD | Sum of Absolute Differences | +| SBT | Subblock Transform | +| SbTMVP | Subblock based Temporal Motion Vector Prediction | +| SCC | Screen Content Coding | +| SMVD | Symmetric MVD | +| TMVP | Temporal Motion Vector Prediction | +| TSRC | Transform Skip Residual Coding | +| WPP | Wavefront Parallel Processing | + +# 5 Conventions + +For the purposes of this Recommendation | International Standard, relevant conventions are specified in clause 5 of Rec. ITU-T H.266 | ISO/IEC 23090-3. + +# 6 Conformance testing for ITU-T H.266 | ISO/IEC 23090-3 + +## 6.1 Introduction + +The following clauses specify normative tests for verifying conformance of video bitstreams as well as decoders. These normative tests make use of the reference software decoder specified in Rec. ITU-T H.266.2 | ISO/IEC 23090-16, and the normative tests for decoder conformance also make use of test data (bitstream test suites) provided as an electronic annex to this Recommendation | International Standard. + +## 6.2 Bitstream conformance + +Bitstream conformance for Rec. ITU-T H.266 | ISO/IEC 23090-3 is specified by clause C.4 of Rec. ITU-T H.266 | ISO/IEC 23090-3. + +## 6.3 Decoder conformance + +Decoder conformance for Rec. ITU-T H.266 | ISO/IEC 23090-3 is specified by clause C.5 of Rec. ITU-T H.266 | ISO/IEC 23090-3. + +## 6.4 Procedure to test bitstreams + +A bitstream that is claimed to conform to Rec. ITU-T H.266 | ISO/IEC 23090-3 shall pass the following normative test. This test should not be applied to bitstreams that are known to contain errors introduced by transmission, as such errors are highly likely to result in bitstreams that lack conformance to Rec. ITU-T H.266 | ISO/IEC 23090-3. + +The bitstream under test shall be decoded by processing it with the reference software decoder. When processed by the reference software decoder, the bitstream shall not cause any error or non-conformance messages to be reported by the reference software decoder. When the bitstream under test contains decoded picture hash SEI messages, the hash values signalled in the decoded picture hash SEI messages in the bitstream shall match those calculated by the reference software decoder. + +Successfully passing this test provides only a strong presumption that the bitstream under test does indeed meet all the requirements specified in Rec. ITU-T H.266 | ISO/IEC 23090-3 that are tested by the reference software decoder. + +Additional tests may be necessary to more thoroughly check that the bitstream properly meets all the requirements specified in Rec. ITU-T H.266 | ISO/IEC 23090-3, including hypothetical reference decoder (HRD) conformance (based on Annexes C and D). Such complementary tests may be performed using other video bitstream verifiers that perform more complete tests than those implemented by the reference software decoder. + +Rec. ITU-T H.266 | ISO/IEC 23090-3 contains several informative recommendations that are not an integral part of that Recommendation | International Standard. When testing a bitstream for conformance, it may also be useful to test whether or not the bitstream follows those recommendations. + +To check the correctness of a bitstream, it is necessary to parse the entire bitstream and to extract all the syntax elements and other values derived from those syntactic elements and used by the decoding process specified in Rec. ITU-T H.266 | ISO/IEC 23090-3. + +A bitstream verifier may not necessarily perform all stages of the decoding process specified in Rec. ITU-T H.266 | ISO/IEC 23090-3 in order to verify bitstream correctness. Many tests can be performed on syntax elements in a state prior to their use in some processing stages. + +## 6.5 Procedure to test decoder conformance + +### 6.5.1 Conformance bitstreams + +A bitstream that conforms to Rec. ITU-T H.266 | ISO/IEC 23090-3 has values of general\_profile\_idc, general\_tier\_flag, and general\_level\_idc corresponding to a set of specified constraints on a bitstream for which a decoder conforming to a corresponding specified profile, tier, and level is required in Annex A of Rec. ITU-T H.266 | ISO/IEC 23090-3 to properly perform the decoding process. + +### 6.5.2 Contents of the bitstream file + +The associated conformance testing bitstreams are included with this Recommendation | International Standard as an electronic attachment. The following information is included in a single zipped file for each such bitstream. + +- \*.bit – bitstream (provided for all bitstreams) +- \*.txt – description (provided for all bitstreams) + +- \*.yuv.md5 – MD5 checksum of the complete decoded yuv file (provided for all bitstreams) +- \*.md5 – MD5 checksum of the bitstream file (provided for all bitstreams) +- \*.opl – output picture log (provided for all bitstreams) +- \*.cfg – config file used to generate bitstream with VTM encoder software (not provided for all bitstreams, not applicable if a VTM encoder release version was not used) + +### 6.5.3 Requirements on output of the decoding process and timing + +Two classes of decoder conformance are specified: + +- output order conformance; and +- output timing conformance. + +The output of the decoding process is specified in clause 8 and Annex C of Rec. ITU-T H.266 | ISO/IEC 23090-3. + +For output order conformance, it is a requirement that all of the cropped decoded pictures specified for output in Annex C of Rec. ITU-T H.266 | ISO/IEC 23090-3 shall be output by a conforming decoder in the specified order and that the values of the decoded samples of the cropped decoded pictures that are output shall be (exactly equal to) the values specified in clause 8 of Rec. ITU-T H.266 | ISO/IEC 23090-3. + +For output timing conformance, it is a requirement that a conforming decoder shall also output the cropped decoded pictures at the picture rates and times specified in Annex C of Rec. ITU-T H.266 | ISO/IEC 23090-3. + +The display process, which ordinarily follows the output of the decoding process, is outside the scope of this Recommendation | International Standard. + +### 6.5.4 Static tests for output order conformance + +Static tests of a video decoder require testing of the samples of the cropped decoded pictures that are output from the decoder, and can be accomplished when the decoded samples at the output of the decoding process are available. It may not be possible to perform this type of test with a production decoder (due to the lack of an appropriate accessible interface in the design at which to perform the test). In such a case this test should be performed by the manufacturer during the design and development phase. Static tests are used for testing the decoding process. + +The pictures that are output by the decoder under test are checked to ensure that the following requirements are fulfilled: + +- The cropped decoded pictures that are output by the decoder under test shall correspond to those that are output by the reference software decoder. +- The cropped decoded pictures that are output by the decoder under test shall be output in the same order as those that are output by the reference software decoder. +- The values of the samples of the cropped decoded pictures that are output by the decoder under test shall be identical to those that are output by the reference software decoder. + +To assist with the checking of the decoding process and the cropped decoded pictures, hash values for the cropped decoded pictures that are output by conforming decoders are provided in a corresponding output picture log file for each test bitstream that is used in the specified conformance tests, and most of these test bitstreams also contain decoded picture hash SEI messages that may be used for checking the results of the decoding process of the decoder under test. + +### 6.5.5 Dynamic tests for output timing conformance + +Dynamic tests are applied to check that all the decoded samples of the cropped decoded pictures are output and that the timing of the output of the decoder's decoded samples conforms to the specifications of clause 8 and Annex C of Rec. ITU-T H.266 | ISO/IEC 23090-3, and to verify that the decoder under test can operate according to bitstream flow characteristics prescribed by the specified HRD models (as specified by the CPB and DPB specification in Annex C of Rec. ITU-T H.266 | ISO/IEC 23090-3) when the bits of the bitstream are delivered at the proper rate. + +The dynamic test is often easier to perform on a complete decoding system, which may include a systems decoder, a video decoder and a display process. It may be possible to record the output of the display process and to check that display order and timing of the cropped decoded pictures are correct at the output of the display process. However, since the display process is not within the normative scope of Rec. ITU-T H.266 | ISO/IEC 23090-3, there may be cases where the output of the display process differs in timing or value even though the video decoder is conforming. In this case, the output of the video decoder itself (before the display process) would need to be captured in order to perform the dynamic tests on the video decoder. In particular the output order and timing of the output of the cropped decoded pictures shall be correct. + +If buffering period and picture timing SEI messages are included in the test bitstream, HRD conformance shall be verified using the values of `nal_initial_cpb_removal_delay`, `nal_initial_cpb_removal_offset`, `au_cpb_removal_delay_minus1` and `pic_dpb_output_delay` that are included in the bitstream. + +If buffering period and picture timing SEI messages are not included in the bitstream, the following inferences shall be made to generate the missing parameters: + +- `fixed_pic_rate_general_flag[ i ]` shall be inferred to be equal to 1. +- `low_delay_hrd_flag[ i ]` shall be inferred to be equal to 0. +- `cbr_flag[ subLayerId ][ j ]` shall be inferred to be equal to 0. +- The frame rate of the bitstream shall be inferred to be equal to the frame rate value specified in the .txt file for the bitstream. If this is missing, then a frame rate of either 25 or $30000 \div 1001$ can be inferred. +- The bit rate of the bitstream shall be inferred to be equal to the maximum value for the level specified in Rec. ITU-T H.266 | ISO/IEC 23090-3. +- CPB and DPB sizes shall be inferred to be equal to the maximum value for the level specified in Rec. ITU-T H.266 | ISO/IEC 23090-3. + +With the above inferences, the HRD shall be operated as follows. + +- The CPB is filled starting at time $t = 0$ , until it is full, before removal of the first access unit. This means that the `bp_nal_initial_cpb_removal_delay[ i ][ j ]` shall be inferred to be equal to the total CPB buffer size divided by the bit rate divided by 90000 (rounded downwards) and `bp_vcl_initial_cpb_removal_offset[ i ][ j ]` shall be inferred to be equal to zero. +- The first access unit is removed at time $t = \text{bp\_nal\_initial\_cpb\_removal\_delay}[ i ][ j ] \div 90000$ and subsequent access units are removed at intervals based on the picture distance +- Using these inferences with the accompanying bitstreams, the CPB will not overflow or underflow and the DPB will not overflow. + +### 6.5.6 Decoder conformance test for a particular profile, tier, and level + +In order for a decoder for a particular profile, tier, and level to claim output order conformance to Rec. ITU-T H.266 | ISO/IEC 23090-3, the decoder shall successfully pass the static test specified in clause 6.5.4 with all the bitstreams of the normative test suite specified for testing decoders of this particular profile, tier, and level combination. + +In order for a decoder of a particular profile, tier, and level to claim output timing conformance to Rec. ITU-T H.266 | ISO/IEC 23090-3, the decoder shall successfully pass both the static test specified in clause 6.5.4 and the dynamic test specified in clause 6.5.5 with all the bitstreams of the normative test suite specified for testing decoders of this particular profile, tier, and level. + +Tables 1 through 19 specify the normative test suites. The profile, tier, and level combinations are described in the tables or in the .txt file associated with the bitstream. + +## 6.6 Specification of the test bitstreams + +### 6.6.1 General + +Some characteristics of each bitstream are described in this clause. + +### 6.6.2 Test bitstreams – Coding tools for Main 10 profile with 4:2:0 chroma format and 10 bit depth + +#### 6.6.2.1 Chroma separate tree (CST) + +##### 6.6.2.1.1 Test bitstream CST\_A + +**Specification:** All pictures are coded in I slices with CST enabled. CST is tested with all possible luma and chroma block sizes, and luma-chroma block size combinations (e.g., luma block size is larger than, equal to, or smaller than the corresponding chroma block size). + +**Functional stage:** Reconstruction process. + +**Purpose:** Check that the decoder can properly decode slices with CST enabled. + +#### 6.6.2.2 Dependent quantization (DQ) + +##### 6.6.2.2.1 Test bitstream DQ\_A + +**Specification:** The bitstream consists of three CVSs, with the following properties: + +- The first CVS uses dependent quantization for all pictures, all non-related features (inter tools, ALF, ...) are disabled, and MTS and LFNST are disabled. +- The second CVS uses dependent quantization for all pictures, all non-related features (inter tools, ALF, ...) are disabled, and MTS (for intra) and LFNST are enabled. +- The third CVS exercises a picture-level selection between dependent quantization, sign data hiding, and standard quantization, all non-related features (inter tools, ALF, ...) are disabled, and MTS (for intra) and LFNST are enabled. + +**Functional stage:** Dependent quantization. + +**Purpose:** Check that the decoder can properly decode slices with DQ enabled. + +##### 6.6.2.2.2 Test bitstream DQ\_B + +**Specification:** The bitstream consists of three CVSs of resolution 1920 x 1080, with the following properties: + +- The first CVS uses dependent quantization for all pictures, all non-related features (inter tools, ALF, ...) are disabled, and MTS and LFNST are disabled. +- The second CVS uses dependent quantization for all pictures, all non-related features (inter tools, ALF, ...) are disabled, and MTS (for intra) and LFNST are enabled. +- The third CVS exercises a picture-level selection between dependent quantization, sign data hiding, and standard quantization, all non-related features (inter tools, ALF, ...) are disabled, and MTS (for intra) and LFNST are enabled. + +**Functional stage:** Dependent quantization. + +**Purpose:** Check that the decoder can properly decode slices with DQ enabled. + +#### 6.6.2.3 Cross-component linear model (CCLM) + +##### 6.6.2.3.1 Test bitstream CCLM\_A + +**Specification:** The bitstream exercises corner cases for coding structures using CCLM with the following properties: + +- POC0: Chroma CU size is 64x64. +- POC1: First split of CU is horizontal, i.e., CU size is 64x32. +- POC2: First split of CU is quad, i.e., CU size is 32x32. +- POC3: First and second split of CU are horizontal and vertical, respectively. +- POC4: First split of CU is vertical or ternary, i.e., none of condition is satisfied for CCLM. +- POC5: CU size is 64x64 and ISP is enabled. +- POC6: First luma split is something else than quad. + +**Functional stage:** Intra prediction. + +**Purpose:** Check that the decoder can properly decode slices with CCLM enabled. + +#### 6.6.2.4 Multiple transform set (MTS) + +##### 6.6.2.4.1 Test bitstream MTS\_A + +**Specification:** The bitstream exercises the following transform features: + +- 1st part + - Explicit intra MTS on and explicit inter MTS off with low frequency non-separable transform (LFNST) disabled. + - Include all test cases for ISP, MIP, luma tree, and CST. + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + +- Include all possible block sizes and partitions where all MTS combinations can happen. +- 2nd part + - Implicit MTS on and explicit inter MTS off with LFNST disabled. + - Include all test cases for ISP, MIP, luma tree, and CST. + - Include all possible block sizes and partitions (especially for ISP) for all allowable MTS combinations. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode slices with MTS enabled. + +##### 6.6.2.4.2 Test bitstream MTS\_B + +**Specification:** The bitstream exercises the following transform features: + +- 1st part + - Explicit intra MTS on and explicit inter MTS off with LFNST disabled. + - Include all test cases for SBT, single tree and TU-tiling based on maximum transform size (64). + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all possible block sizes and partitions (especially for SBT) where all MTS combinations can happen. +- 2nd part + - Implicit intra MTS on and explicit inter MTS off with LFNST disabled. + - Include all test cases for SBT, single tree, and TU-tiling based on maximum transform size (64). + - Include all possible block sizes and partitions (especially for SBT) where all MTS combinations can happen. +- 3rd part + - Implicit MTS on and explicit inter MTS off with LFNST disabled. + - Include all test cases for SBT and single tree. + - Include all possible block sizes and partitions (especially for SBT) where all MTS combinations can happen. +- 4th part + - Explicit intra MTS on and explicit inter MTS on with LFNST disabled. + - Include all test cases for SBT and single tree. + - Include all possible block sizes and partitions (especially for SBT) where all MTS combinations can happen. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode slices with MTS enabled. + +#### 6.6.2.5 Adaptive loop filter (ALF) + +##### 6.6.2.5.1 Test bitstream ALF\_A + +**Specification:** This bitstream uses both ALF and virtual boundary, as follows: + +- Applies ALF virtual boundary (VB) at non-CTC CTU sizes (CTU size of 64 is used). +- Positions luma VB at 4 lines (Pos : 60) and chroma VB at 2 lines (Pos : 62) above the CTU height. + +**Functional stage:** Adaptive loop filter. + +**Purpose:** Check that the decoder can properly decode slices with ALF enabled. + +##### 6.6.2.5.2 Test bitstream ALF\_B + +**Specification:** This bitstream uses both ALF and virtual boundary, as follows: + +- Applies ALF virtual boundary (VB) to sequences whose picture height is 1 CTU (CTU size of 128 is used as per CTC). + +- Positions luma VB at 4 lines (Pos : 124) and chroma VB at 2 lines (Pos : 62) above the CTU height. + +**Functional stage:** Adaptive loop filter. + +**Purpose:** Check that the decoder can properly decode slices with ALF enabled. + +##### 6.6.2.5.3 Test bitstream ALF\_C + +**Specification:** Bitstream exercises clipping values of non-linear ALF. + +**Functional stage:** Adaptive loop filter. + +**Purpose:** Check that the decoder can properly decode slices with ALF enabled. + +##### 6.6.2.5.4 Test bitstream ALF\_D + +**Specification:** Bitstream uses multiple ALF APSs with LMCS enabled. + +**Functional stage:** Adaptive loop filter. + +**Purpose:** Check that the decoder can properly decode slices with ALF enabled. + +#### 6.6.2.6 Affine motion model (AFF) + +##### 6.6.2.6.1 Test bitstream AFF\_A + +**Specification:** The bitstream enables 6-parameter affine mode by SPS flag. All allowed blocks sizes of Affine merge mode are exercised multiple times. All allowed blocks sizes of Affine AMVP mode, including 4-parameter and 6-parameter Affine mode, are exercised multiple times. All allowed candidates for Affine merge mode, including two inherited candidates, four 6-parameter constructed candidates, two 4-parameter constructed candidates, and zero padding candidate are exercised multiple times. Inheritance of affine model from top CTU are exercised multiple times. Fallback mode for affine memory bandwidth restriction is triggered multiple times. + +**Functional stage:** Affine mode inter prediction. + +**Purpose:** Check that the decoder can properly decode slices with affine mode enabled. + +##### 6.6.2.6.2 Test bitstream AFF\_B + +**Specification:** The bitstream uses affine mode, with 6-parameter affine mode disabled by SPS flag. All allowed blocks sizes of Affine merge mode are exercised multiple times. All allowed blocks sizes of 4-parameter Affine AMVP mode are exercised multiple times. All allowed candidates for Affine merge mode, including two inherited candidates, two 4-parameter constructed candidates, and zero padding candidate are exercised multiple times. Inheritance of affine model from top CTU are exercised multiple times. Fallback mode for affine memory bandwidth restriction is triggered multiple times. All allowed blocks sizes of Affine merge mode are exercised multiple times. All allowed candidates for Affine merge mode, including two inherited candidates, two 4-parameter constructed candidates, and zero padding candidate are exercised multiple times. Inheritance of affine model from top CTU are exercised multiple times. Fallback mode for affine memory bandwidth restriction is triggered multiple times. + +**Functional stage:** Affine mode inter prediction. + +**Purpose:** Check that the decoder can properly decode slices with affine mode enabled. + +#### 6.6.2.7 Subblock-based temporal merging candidates (SbTMVP) + +##### 6.6.2.7.1 Test bitstream SbTMVP\_A + +**Specification:** The bitstream uses SbTMVP when affine is disabled. + +**Functional stage:** Inter prediction process. + +**Purpose:** Check that the decoder can properly decode PUs with SbTMVP on and affine off. + +##### 6.6.2.7.2 Test bitstream SbTMVP\_B + +**Specification:** This bitstream disables SbTMVP. + +**Functional stage:** Inter prediction process. + +**Purpose:** Check that the decoder can properly decode PUs with SbTMVP off. + +#### 6.6.2.8 Adaptive motion vector resolution (AMVR) + +##### 6.6.2.8.1 Test bitstream AMVR\_A + +**Specification:** The bitstream exercises translational and affine AMVR with different settings. It represents a concatenation of five CVSs with the following properties: + +- The first CVS exercises translational AMVR with amvr\_precision\_idx equal to 1 (i.e., 1 luma sample motion vector resolution). +- The second CVS exercises translational AMVR with amvr\_precision\_idx equal to 2 (i.e., 4 luma samples motion vector resolution). +- The third CVS exercises translational AMVR with amvr\_precision\_idx equal to 0 (i.e., 1/2 luma sample motion vector resolution). This implies application of the Switchable Interpolation Filter (SIF). +- The fourth CVS exercises affine AMVR with amvr\_precision\_idx equal to 0 (i.e., 1/16 luma sample motion vector resolution). +- The fifth CVS exercises affine AMVR with amvr\_precision\_idx equal to 1 (i.e., 1 luma sample motion vector resolution). + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with AMVR enabled. + +##### 6.6.2.8.2 Test bitstream AMVR\_B + +**Specification:** The bitstream exercises AMVR. It cycles frame-by-frame between the following variants: + +- Translational AMVR with amvr\_precision\_idx equal to 1 (i.e., 1 luma sample motion vector resolution). +- Translational AMVR with amvr\_precision\_idx equal to 2 (i.e., 4 luma samples motion vector resolution). +- Translational AMVR with amvr\_precision\_idx equal to 0 (i.e., 1/2 luma sample motion vector resolution), this implies application of the Switchable Interpolation Filter (SIF). +- Affine AMVR with amvr\_precision\_idx equal to 0 (i.e., 1/16 luma sample motion vector resolution). +- Affine AMVR with amvr\_precision\_idx equal to 1 (i.e., 1 luma sample motion vector resolution). + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with AMVR enabled. + +#### 6.6.2.9 Bi-directional optical flow (BDOF) + +##### 6.6.2.9.1 Test bitstream BDOF\_A + +**Specification:** Bitstream exercises all possible implicit BDOF on/off conditions and subblock usages. + +**Functional stage:** Inter prediction process. + +**Purpose:** Check that the decoder can properly decode CUs with BDOF enabled. + +#### 6.6.2.10 Combined intra/inter prediction (CIIP) + +##### 6.6.2.10.1 Test bitstream CIIP\_A + +**Specification:** The bitstream exercises all possible inter direction, block sizes, and combining weights for CIIP. + +**Functional stage:** Inter prediction process. + +**Purpose:** Check that the decoder can properly decode CUs with CIIP enabled. + +#### 6.6.2.11 Merge with MVD (MMVD) + +##### 6.6.2.11.1 Test bitstream MMVD\_A + +**Specification:** The bitstream uses MMVD with different numbers of MMVD distance entries. + +**Functional stage:** Inter prediction process. + +**Purpose:** Check that the decoder can properly decode bitstreams with merge with MMVD enabled. + +#### 6.6.2.12 Bi-predictive with CU weights (BCW) + +##### 6.6.2.12.1 Test bitstream BCW\_A + +**Specification:** The bitstream exercises all possible combining weights for BCW. + +**Functional stage:** Inter prediction process. + +**Purpose:** Check that the decoder can properly decode CUs with BCW enabled. + +#### 6.6.2.13 Multi-reference line prediction (MRLP) + +##### 6.6.2.13.1 Test bitstream MRLP\_A + +**Specification:** The bitstream contains all possible combinations of extended intra reference lines for luma indicated by $\text{intra\_luma\_ref\_idx} = \{1, 2\}$ and most probable modes except the DC, indicated by $\text{intra\_luma\_mpm\_idx} = \{0, 1, 2, 3, 4\}$ . For the CUs at the top border of a CTU, extended references lines are not used in the MRL index is not present in the bitstream. All CTC tools are enabled. + +**Functional stage:** Intra prediction and mode signalling processes. + +**Purpose:** Test all combinations of reference line indices and associated MPM signalling with all tools on. + +##### 6.6.2.13.2 Test bitstream MRLP\_B + +**Specification:** The bitstream contains all possible combinations of extended intra reference lines for luma indicated by $\text{intra\_luma\_ref\_idx} = \{1, 2\}$ and most probable modes except the DC, indicated by $\text{intra\_luma\_mpm\_idx} = \{0, 1, 2, 3, 4\}$ . For the CUs at the top border of a CTU, extended references lines are not used in the MRL index is not present in the bitstream. The following prediction modes have been disabled: Intra: ISP and MIP, Inter: SBT, MMVD, Affine, SubPuMvp, IMV, BCW, BIO, CIIP, GPM, DisFracMMVD, AffineAmvr, DMVR, SMVD, and PROF. + +**Functional stage:** Intra prediction and mode signalling processes. + +**Purpose:** Test all combinations of reference line indices and associated MPM signalling with specific intra and inter tools turned off. + +#### 6.6.2.14 Intra block copy mode (IBC) + +##### 6.6.2.14.1 Test bitstream IBC\_A + +**Specification:** This bitstream exercises general IBC features, merge, skip and AMVP modes. + +**Functional stage:** Intra prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with IBC enabled. + +##### 6.6.2.14.2 Test bitstream IBC\_B + +**Specification:** This bitstream exercises general IBC features, merge, skip and AMVP modes, with BV predictor size equal to 1 ( $\text{MaxNumIBCMergeCand}=1$ ). + +**Functional stage:** Intra prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with IBC enabled. + +##### 6.6.2.14.3 Test bitstream IBC\_C + +**Specification:** This bitstream exercises general IBC features, merge, skip and AMVP modes, with Dual Tree disabled ( $\text{DualITree}=0$ ). + +**Functional stage:** Intra prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with IBC enabled. + +##### 6.6.2.14.4 Test bitstream IBC\_D + +**Specification:** This bitstream exercises general IBC features, merge, skip and AMVP modes, with AMVR disabled. + +**Functional stage:** Intra prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with IBC enabled. + +##### 6.6.2.14.5 *Test bitstream IBC\_E* + +**Specification:** This bitstream exercises general IBC blocks with all possible block sizes. + +**Functional stage:** Intra prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with IBC enabled. + +#### 6.6.2.15 Intra sub-partitioning (ISP) + +##### 6.6.2.15.1 *Test bitstream ISP\_A* + +**Specification:** The bitstream contains various combinations of block sizes, ISP split types, intra modes and LFNST indices. It uses an AI configuration and 34 frames with QP 28. + +**Functional stage:** Intra prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with ISP enabled. + +##### 6.6.2.15.2 *Test bitstream ISP\_B* + +**Specification:** The bitstream contains various combinations of block sizes, ISP split types, intra modes and LFNST indices. It uses a RA configuration and 161 frames with QP 34. + +**Functional stage:** Intra prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with ISP enabled. + +#### 6.6.2.16 Decoder motion vector refinement (DMVR) + +##### 6.6.2.16.1 *Test bitstream DMVR\_A* + +**Specification:** This bitstream exercises DMVR with the following features: + +- All allowed blocks sizes of DMVR are exercised multiple times. +- Motion vector wraparound is enabled where DMVR uses wrapped around reference samples. +- BCW and explicit weighted biprediction is turned on for luma and chroma components, to test disabling of DMVR. +- All integer delta motion vector combinations are exercised multiple times. +- All fractional delta MV are exercised multiple times. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with DMVR enabled. + +##### 6.6.2.16.2 *Test bitstream DMVR\_B* + +**Specification:** This bitstream exercises DMVR with corner cases of SAD variations. + +**Functional stage:** Inter prediction process. + +**Purpose:** Check that the decoder can properly decode bitstreams with DMVR enabled. + +#### 6.6.2.17 Sub-block transform (SBT) + +##### 6.6.2.17.1 *Test bitstream SBT\_A* + +**Specification:** The bitstream exercises SVT with all allowed blocks sizes exercised multiple times (at least once for each SBT mode for each allowed CU size). + +**Functional stage:** Transform process. + +**Purpose:** Check that the decoder can properly decode bitstreams with DMVR enabled. + +#### 6.6.2.18 Luma mapping with chroma scaling (LMCS) + +##### 6.6.2.18.1 Test bitstream LMCS\_A + +**Specification:** This bitstream tests control of LMCS at the slice level, with the picture split into 4 tiles and 4 rectangular slices. + +**Functional stage:** In-loop filter process. + +**Purpose:** Check that the decoder can properly decode bitstreams with LMCS enabled. + +##### 6.6.2.18.2 Test bitstream LMCS\_B + +**Specification:** This bitstream tests control of LMCS at the slice level, with the picture split into 8 rectangular slices, 12 tiles and 2 subpictures. + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with LMCS enabled. + +##### 6.6.2.18.3 Test bitstream LMCS\_C + +**Specification:** This bitstream tests control of LMCS for the entire CVS according to NoLmcsConstraintFlag. + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with LMCS enabled. + +#### 6.6.2.19 Sign data hiding (SDH) + +##### 6.6.2.19.1 Test bitstream SDH\_A + +**Specification:** This bitstream tests SDH on/off control at picture level. + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with LMCS enabled. + +#### 6.6.2.20 Symmetric motion vector difference (SMVD) + +##### 6.6.2.20.1 Test bitstream SMVD\_A + +**Specification:** This bitstream exercises all allowed blocks sizes of SMVD mode multiple times. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with SMVD enabled. + +#### 6.6.2.21 Block-based delta pulse code modulation (BDPCM) + +##### 6.6.2.21.1 Test bitstream BDPCM\_A + +**Specification:** This bitstream exercises BDPCM-coded block of each possible block size, in both luma and chroma. + +**Functional stage:** Intra coding. + +**Purpose:** Check that the decoder can properly decode bitstreams with BDPCM enabled. + +#### 6.6.2.22 Matrix based intra prediction (MIP) + +##### 6.6.2.22.1 Test bitstream MIP\_A + +**Specification:** This bitstream exercises MIP in different combinations with other tools. The bitstream consists of three CVSs with the following properties: + +- First CVS: For each M, N in {4, 8, 16, 32, 64}, the bitstream contains an MxN-luma-intra-block in which the intra-prediction signal is generated by a mip-mode and in which intra\_mip\_transposed\_flag is false and it contains an MxN-luma-intra-block in which the intra-prediction signal is generated by a mip-mode and in which intra\_mip\_transposed\_flag is true. For each mip-matrix occurring in the spec, the bitstream + +contains a luma-intra-block in which the intra-prediction signal is generated by a mip-mode that uses this mip-matrix. + +- Second CVS: MIP is enabled, MTS and intra tools LFNST, ISP, MRL are disabled. Each slice is an intra slice. +- Third CVS: MIP is enabled, all other intra tools are enabled. Each slice is an intra slice. + +**Functional stage:** Intra coding. + +**Purpose:** Check that the decoder can properly decode bitstreams with MIP enabled. + +##### 6.6.2.22.2 *Test bitstream MIP\_B* + +**Specification:** This bitstream exercises MIP with all other CTC tools enabled. + +**Functional stage:** Intra coding. + +**Purpose:** Check that the decoder can properly decode bitstreams with MIP enabled. + +#### 6.6.2.23 Low frequency non-separable transform (LFNST) + +##### 6.6.2.23.1 *Test bitstream LFNST\_A* + +**Specification:** This bitstream exercises LFNST with MTS disabled, as follows: + +- Include all test cases for ISP, MIP, luma tree, and CST with LFNST. +- Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. +- Include all possible block sizes and partitions (especially for ISP) where LFNST can be applied. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode bitstreams with LFNST enabled. + +##### 6.6.2.23.2 *Test bitstream LFNST\_B* + +**Specification:** This bitstream exercises LFNST with MTS disabled, as follows: + +- Include all test cases for single tree with LFNST. +- Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. +- Include all possible block sizes where LFNST can be applied. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode bitstreams with LFNST enabled. + +##### 6.6.2.23.3 *Test bitstream LFNST\_C* + +**Specification:** This bitstream exercises LFNST and its signalling in different combination with other tools. The bitstream consists of four CVSs with the following properties: + +- The first CVS enables LFNST and explicit MTS; ISP and MIP are enabled. +- The second CVS enables LFNST and explicit MTS; ISP and MIP are disabled. +- The third CVS enables LFNST and explicit MTS; ISP is enabled and MIP is disabled. +- The fourth CVS enables LFNST and explicit MTS; ISP is disabled and MIP is enabled. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode bitstreams with LFNST enabled. + +##### 6.6.2.23.4 *Test bitstream LFNST\_D* + +**Specification:** This bitstream exercises LFNST and its signalling in different combination with other tools. The bitstream consists of four CVSs with the following properties: + +- The first CVS enables LFNST and explicit MTS; ISP and MIP are enabled. +- The second CVS enables LFNST and explicit MTS; ISP and MIP are disabled. +- The third CVS enables LFNST and explicit MTS; ISP is enabled and MIP is disabled. +- The fourth CVS enables LFNST and explicit MTS; ISP is disabled and MIP is enabled. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode bitstreams with LFNST enabled. + +#### 6.6.2.24 Transform tool set (MTS\_LFNST) + +##### 6.6.2.24.1 Test bitstream MTS\_LFNST\_A + +**Specification:** This bitstream exercises various types of enabling of MTS and LFNST. The bitstream consists of five parts with the following properties: + +- 1st part + - Explicit intra MTS on and explicit inter MTS off (CTC). + - Include all test cases for ISP, MIP, luma tree, and CST. + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for ISP) where all combinations of MTS and LFNST can happen. +- 2nd part + - Explicit intra MTS on and explicit inter MTS off with maximum transform size set to 32. + - Include all test cases for ISP, MIP, luma tree, CST, and TU-tiling based on maximum transform size (32). + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for ISP) where all combinations of MTS and LFNST can happen. +- 3rd part + - Implicit MTS on and explicit inter MTS off. + - Include all test cases for ISP, MIP, luma tree, and CST. + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for ISP) where all combinations of MTS and LFNST can happen. +- 4th part + - Implicit MTS on and explicit inter MTS on. + - Include all test cases for ISP, MIP, luma tree, and CST. + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for ISP) where all combinations of MTS and LFNST can happen. +- 5th part + - Explicit MTS on and explicit inter MTS on. + - Include all test cases for ISP, MIP, luma tree, and CST. + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for ISP) where all combinations of MTS and LFNST can happen. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode bitstreams with MTS and LFNST enabled. + +##### 6.6.2.24.2 Test bitstream MTS\_LFNST\_B + +**Specification:** This bitstream exercises various types of enabling of MTS and LFNST. The bitstream consists of five parts with the following properties: + +- 1st part + - Explicit intra MTS on and explicit inter MTS off (CTC). + - Include all test cases for SBT, single tree, and TU-tiling based on maximum transform size (64). + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for SBT) where all combinations of MTS and LFNST can happen. +- 2nd part + - Explicit intra MTS on and explicit inter MTS off with maximum transform size set to 32. + - Include all test cases for SBT, single tree, and TU-tiling based on maximum transform size (32). + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for SBT) where all combinations of MTS and LFNST can happen. +- 3rd part + - Implicit MTS on and explicit inter MTS off. + - Include all test cases for SBT, single tree and TU-tiling based on maximum transform size (64). + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for SBT) where all combinations of MTS and LFNST can happen. +- 4th part + - Implicit MTS on and explicit inter MTS on. + - Include all test cases for SBT, single tree and TU-tiling based on maximum transform size (64). + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for ISP) where all combinations of MTS and LFNST can happen. +- 5th part + - Explicit MTS on and explicit inter MTS on. + - Include all test cases for SBT, single tree and TU-tiling based on maximum transform size (64). + - Include all candidates of explicit MTS, i.e., DCT2-DCT2, DST7-DST7, DCT8-DST7, DST7-DCT8, and DCT8-DCT8. + - Include all sets and candidates of LFNST, i.e., 4 sets and 2 candidates per set. + - Include all possible block sizes and partitions (especially for SBT) where all combinations of MTS and LFNST can happen. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode bitstreams with MTS and LFNST enabled. + +#### 6.6.2.25 Joint coding of chroma residuals (JCCR) + +##### 6.6.2.25.1 Test bitstream JCCR\_A + +**Specification:** Bitstream exercises all possible JCCR modes. In addition, different combinations for values of ph\_joint\_cbc\_r\_sign\_flag and sh\_joint\_cbc\_r\_qp\_offset syntax elements are included in the bitstream. Coded video contains three frames at resolution of 416x240. + +**Functional stage:** TU reconstruction. + +**Purpose:** Check that the decoder can properly decode TUs with different JCCR modes, different JCCR QP offsets and different JCCR signs. + +##### 6.6.2.25.2 Test bitstream JCCR\_B + +**Specification:** Bitstream exercises all possible JCCR modes. In addition, different combinations for values of ph\_joint\_cbc\_r\_sign\_flag and sh\_joint\_cbc\_r\_qp\_offset syntax elements are included in the bitstream. Coded video contains three frames at resolution of 1920x1080. + +**Functional stage:** TU reconstruction. + +**Purpose:** Check that the decoder can properly decode TUs with different JCCR modes, different JCCR QP offsets and different JCCR signs. + +##### 6.6.2.25.3 Test bitstream JCCR\_C + +**Specification:** This bitstream exercises joint chroma residual coding in combination with other tools. The bitstream consists of two CVSs with the following properties: + +- The first CVS uses a random selection of the jointCbCr sign flag, forces the usage of all possible jointCbCr modes, non-related features (inter tools, ALF, ...) are disabled, MTS, LFNST, LMCS, and DQ are disabled. +- The first CVS uses a random selection of the jointCbCr sign flag, forces the usage of all possible jointCbCr modes, non-related features (inter tools, ALF, ...) are disabled, MTS (for intra), LFNST, LMCS, and DQ are enabled. + +**Functional stage:** TU reconstruction. + +**Purpose:** Check that the decoder can properly decode TUs with different JCCR modes. + +##### 6.6.2.25.4 Test bitstream JCCR\_D + +**Specification:** This bitstream exercises joint chroma residual coding in combination with other tools. The bitstream consists of two CVSs with the following properties: + +- The first CVS uses a random selection of the jointCbCr sign flag, forces the usage of all possible jointCbCr modes, non-related features (inter tools, ALF, ...) are disabled, MTS, LFNST, LMCS, and DQ are disabled. +- The first CVS uses a random selection of the jointCbCr sign flag, forces the usage of all possible jointCbCr modes, non-related features (inter tools, ALF, ...) are disabled, MTS (for intra), LFNST, LMCS, and DQ are enabled. + +**Functional stage:** TU reconstruction. + +**Purpose:** Check that the decoder can properly decode TUs with different JCCR modes. + +##### 6.6.2.25.5 Test bitstream JCCR\_E + +**Specification:** Bitstream exercises all possible JCCR modes. In addition, different combinations for values of ph\_joint\_cbc\_r\_sign\_flag and sh\_joint\_cbc\_r\_qp\_offset syntax elements are included in the bitstream. Coded video contains three frames at resolution of 416x240. + +**Functional stage:** TU reconstruction. + +**Purpose:** Check that the decoder can properly decode TUs with different JCCR modes, different JCCR QP offsets and different JCCR signs. + +##### 6.6.2.25.6 Test bitstream JCCR\_F + +**Specification:** Bitstream exercises all possible JCCR modes. In addition, different combinations for values of ph\_joint\_cbc\_r\_sign\_flag and sh\_joint\_cbc\_r\_qp\_offset syntax elements are included in the bitstream. Coded video contains three frames at resolution of 1920x1080. + +**Functional stage:** TU reconstruction. + +**Purpose:** Check that the decoder can properly decode TUs with different JCCR modes, different JCCR QP offsets and different JCCR signs. + +#### 6.6.2.26 Temporal motion vector predictor (TMVP) + +##### 6.6.2.26.1 *Test bitstream TMVP\_A* + +**Specification:** Bitstream disables TMVP. Uses scaled 'ParkRunning3' test sequence with QP 32 and random access configuration. + +**Functional stage:** Motion vector prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with temporal motion vector prediction enabled and disabled. + +##### 6.6.2.26.2 *Test bitstream TMVP\_B* + +**Specification:** Bitstream enables TMVP. Uses scaled 'ParkRunning3' test sequence with QP 32 and random access configuration. + +**Functional stage:** Motion vector prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with temporal motion vector prediction enabled and disabled. + +##### 6.6.2.26.3 *Test bitstream TMVP\_C* + +**Specification:** Bitstream disables TMVP. Uses scaled 'ParkRunning3' test sequence with QP 32 and low delay configuration. + +**Functional stage:** Motion vector prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with temporal motion vector prediction enabled and disabled. + +##### 6.6.2.26.4 *Test bitstream TMVP\_D* + +**Specification:** Bitstream enables TMVP. Uses scaled 'ParkRunning3' test sequence with QP 32 and low delay configuration. + +**Functional stage:** Motion vector prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with temporal motion vector prediction enabled and disabled. + +#### 6.6.2.27 Motion vector compression (MVCOMP) + +##### 6.6.2.27.1 *Test bitstream MVCOMP\_A* + +**Specification:** This bitstream includes large motion vectors that are stored in the temporal motion vector buffer and that are later retrieved for motion vector prediction. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with large motion vectors. + +#### 6.6.2.28 Sampled adaptive offset (SAO) + +##### 6.6.2.28.1 *Test bitstream SAO\_A* + +**Specification:** This bitstream uses SAO with ALF and CCALF disabled. + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with various in-loop filter combinations. + +##### **6.6.2.28.2 Test bitstream SAO\_B** + +**Specification:** This bitstream uses SAO with LMCS disabled. + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with various in-loop filter combinations. + +##### **6.6.2.28.3 Test bitstream SAO\_C** + +**Specification:** This bitstream uses SAO with ALF, CCALF, and LMCS disabled. + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with various in-loop filter combinations. + +#### **6.6.2.29 Prediction refinement using optical flow (PROF)** + +##### **6.6.2.29.1 Test bitstream PROF\_A** + +**Specification:** This bitstream contains pictures with high rotation motion. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with PROF enabled. + +##### **6.6.2.29.2 Test bitstream PROF\_B** + +**Specification:** The bitstream contains pictures with high zoom and rotation motion. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with PROF enabled. + +#### **6.6.2.30 Deblocking (DEBLOCKING)** + +##### **6.6.2.30.1 Test bitstream DEBLOCKING\_A** + +**Specification:** This bitstream has luma deblocking filters of lengths (7,7), (7,5), (5,7), (7,3), (3,7), (5,5), (5,3) and (3,5). + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with deblocking filter enabled. + +##### **6.6.2.30.2 Test bitstream DEBLOCKING\_B** + +**Specification:** This bitstream has luma deblocking filters of lengths (3,3) and (1,3). + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with deblocking filter enabled. + +##### **6.6.2.30.3 Test bitstream DEBLOCKING\_C** + +**Specification:** This bitstream tests that luma deblocking is performed on a 4 x 4 deblocking grid and ensures that constrained weak filter ( 1 + 1 ) is applied when one of the blocks sharing the edge has size $\leq 4$ samples in the direction of deblocking. + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with deblocking filter enabled. + +##### **6.6.2.30.4 Test bitstream DEBLOCKING\_E** + +**Specification:** Bitstream exercises all luma and chroma deblocking lengths for deblocking of transform and prediction block and sub-block boundaries. + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with deblocking filter enabled. + +##### **6.6.2.30.5 Test bitstream DEBLOCKING\_F** + +**Specification:** Bitstream exercises deblocking control features luma adaptive deblocking and control of beta and tc for both luma and chroma. + +**Functional stage:** In-loop filter. + +**Purpose:** Check that the decoder can properly decode bitstreams with deblocking filter enabled. + +#### **6.6.2.31 Weighted prediction (WP)** + +##### **6.6.2.31.1 Test bitstream WP\_A** + +**Specification:** The bitstream was encoded in random access configuration. The content has fading to black. WP have been disabled for pictures with Tid equal to 2. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with weighted prediction enabled. + +##### **6.6.2.31.2 Test bitstream WP\_B** + +**Specification:** The bitstream was encoded in low-delay configuration. The content has flashing and fading. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with weighted prediction enabled. + +#### **6.6.2.32 Parallel merge (PMERGE)** + +##### **6.6.2.32.1 Test bitstream PMERGE\_A** + +**Specification:** This bitstream exercises the sps\_log2\_parallel\_merge\_level\_minus2 equals to 1 with luma CTB size 128x128. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with parallel merge control. + +##### **6.6.2.32.2 Test bitstream PMERGE\_B** + +**Specification:** This bitstream exercises the sps\_log2\_parallel\_merge\_level\_minus2 equals to 2 with luma CTB size 128x128. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with parallel merge control. + +##### **6.6.2.32.3 Test bitstream PMERGE\_C** + +**Specification:** This bitstream exercises the sps\_log2\_parallel\_merge\_level\_minus2 equals to 3 with luma CTB size 128x128. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with parallel merge control. + +##### **6.6.2.32.4 Test bitstream PMERGE\_D** + +**Specification:** This bitstream exercises the sps\_log2\_parallel\_merge\_level\_minus2 equals to 4 with luma CTB size 128x128. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with parallel merge control. + +##### **6.6.2.32.5 Test bitstream PMERGE\_E** + +**Specification:** This bitstream exercises the sps\_log2\_parallel\_merge\_level\_minus2 equals to 5 with luma CTB size 128x128. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with parallel merge control. + +#### 6.6.2.33 Intra prediction (IP) + +##### 6.6.2.33.1 Test bitstream IP\_A + +**Specification:** The bitstream exercises luminance intra prediction modes. + +**Functional stage:** Intra sample prediction. + +**Purpose:** Test intra sample reconstruction process. + +##### 6.6.2.33.2 Test bitstream IP\_B + +**Specification:** Bitstream exercises all the intra prediction modes. + +**Functional stage:** Intra sample prediction. + +**Purpose:** Test intra sample reconstruction process, especially wide angle modes in non-square blocks. + +#### 6.6.2.34 Luma intra prediction mode (MPM) + +##### 6.6.2.34.1 Test bitstream MPM\_A + +**Specification:** This bitstream contains MPM candidate for all the sizes of the blocks, i.e., all WxH-sized TUs, where both W and H are equal to one of the following values: {4, 8, 16 or 32}. All intra coding tools except MIP are enabled. + +**Functional stage:** Intra prediction. + +**Purpose:** Check that the decoder can properly decode all MPM modes. + +#### 6.6.2.35 CTU sizes (CTU, CU) + +##### 6.6.2.35.1 Test bitstream CTU\_A + +**Specification:** Bitstream exercises all possible CU sizes when maximum CTU size is set to 128x128. + +**Functional stage:** Partitioning. + +**Purpose:** Check that a decoder can parse and reconstruct correctly when maximum CTU size is set to 128x128. + +##### 6.6.2.35.2 Test bitstream CTU\_B + +**Specification:** Bitstream exercises all possible CU sizes when maximum CTU size is set to 64x64. + +**Functional stage:** Partitioning. + +**Purpose:** Check that a decoder can parse and reconstruct correctly when maximum CTU size is set to 64x64. + +##### 6.6.2.35.3 Test bitstream CTU\_C + +**Specification:** Bitstream exercises all possible CU sizes when maximum CTU size is set to 32x32. + +**Functional stage:** Test the parsing and reconstruction of slices. + +**Purpose:** Check that a decoder can parse and reconstruct correctly when maximum CTU size is set to 32x32. + +#### 6.6.2.36 Trees and partitioning (TREE, QTBTB) + +##### 6.6.2.36.1 Test bitstream TREE\_A + +**Specification:** This bitstream exercises a range of tree size and depths for CTUSize=32. + +**Functional stage:** Partitioning. + +**Purpose:** Check that the decoder can properly decode all partitioning modes. + +##### 6.6.2.36.2 Test bitstream TREE\_B + +**Specification:** This bitstream exercises a range of tree size and depths for CTUSize=64. + +**Functional stage:** Partitioning. + +**Purpose:** Check that the decoder can properly decode all partitioning modes. + +##### 6.6.2.36.3 *Test bitstream TREE\_C* + +**Specification:** This bitstream exercises a range of tree size and depths for CTUSize=128. + +**Functional stage:** Partitioning. + +**Purpose:** Check that the decoder can properly decode all partitioning modes. + +##### 6.6.2.36.4 *Test bitstream QTBT\_T\_A* + +**Specification:** Bitstream exercises all possible range of CU sizes and depths for QTBT partitions. + +**Functional stage:** Test the parsing and reconstruction of slices. + +**Purpose:** Check that a decoder can parse and reconstruct correctly for all exercise range of CU sizes and depth for QTBT partitions. + +#### 6.6.2.37 **Boundary partition (BOUNDARY)** + +##### 6.6.2.37.1 *Test bitstream BOUNDARY\_A* + +**Specification:** This bitstream tests boundary handling on specific resolution with WidthxHeight, where Width = 256+8\*n, Height = 256 + 8\*m, m and n belong to {0...15}. QT depths for boundary blocks are selected as {1, 2, 3, 4} with POC = {1, 2, 3, 4}, respectively. + +**Functional stage:** Partitioning. + +**Purpose:** Check that the decoder can properly decode all partitioning modes. + +#### 6.6.2.38 **Transform (TRANS)** + +##### 6.6.2.38.1 *Test bitstream TRANS\_A* + +**Specification:** The bitstream has size 64 transform off, LFNST off, and DepQuant off for All Intra. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode all transform modes. + +##### 6.6.2.38.2 *Test bitstream TRANS\_B* + +**Specification:** The bitstream has size 64 transform on, LFNST off, and DepQuant off for All Intra. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode all transform modes. + +##### 6.6.2.38.3 *Test bitstream TRANS\_C* + +**Specification:** The bitstream has size 64 transform off, LFNST off, and DepQuant off for random access. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode all transform modes. + +##### 6.6.2.38.4 *Test bitstream TRANS\_D* + +**Specification:** The bitstream has size 64 transform on, LFNST off, and DepQuant off for random access. + +**Functional stage:** Transform. + +**Purpose:** Check that the decoder can properly decode all transform modes. + +#### 6.6.2.39 Quantization (QUANT) + +##### 6.6.2.39.1 Test bitstream QUANT\_A + +**Specification:** This bitstream tests CU level QP adaptation. + +**Functional stage:** Quantization. + +**Purpose:** Check that the decoder can properly decode all quantization modes. + +##### 6.6.2.39.2 Test bitstream QUANT\_B + +**Specification:** This bitstream tests CU level QP adaptation. + +**Functional stage:** Quantization. + +**Purpose:** Check that the decoder can properly decode all quantization modes. + +##### 6.6.2.39.3 Test bitstream QUANT\_C + +**Specification:** This bitstream uses low QP with transform skip, so that deblocking filtering not used. + +**Functional stage:** Quantization, In-loop filtering. + +**Purpose:** Check that the decoder can properly decode all quantization modes. + +##### 6.6.2.39.4 Test bitstream QUANT\_D + +**Specification:** Deblocking filtering is forced to be used by setting LoopFilterTcOffset\_div2 and LoopFilterTcOffset\_div2 to 12. + +**Functional stage:** Quantization, In-loop filtering. + +**Purpose:** Check that the decoder can properly decode all quantization modes. + +##### 6.6.2.39.5 Test bitstream QUANT\_E + +**Specification:** The bitstream use of local chroma QP offsets. It signals a PPS chroma QP offset list of maximal size, making use of maximal QP offset range. + +**Functional stage:** Quantization. + +**Purpose:** Check that the decoder can parse and use local chroma QP offsets. + +#### 6.6.2.40 Scaling list (SCALING) + +##### 6.6.2.40.1 Test bitstream SCALING\_A + +**Specification:** Bitstream uses scaling list in monochrome mode. Composed of 2 concatenated streams. The first one sets scaling lists every 8 frames, the second one sets scaling lists based on temporal ID. + +**Functional stage:** Inverse quantization. + +**Purpose:** Check that decoder can parse and use scaling list quantization matrices. + +##### 6.6.2.40.2 Test bitstream SCALING\_B + +**Specification:** The bitstream uses quantization matrices in colour mode for LFNST blocks. Composed of 2 concatenated streams. The first one sets scaling lists every 8 frames, the second one sets scaling lists based on temporal ID with sps\_scaling\_matrix\_for\_lfnst\_disabled\_flag OFF. + +**Functional stage:** Inverse quantization. + +**Purpose:** Check that decoder can parse and use scaling list quantization matrices. + +##### 6.6.2.40.3 Test bitstream SCALING\_C + +**Specification:** The bitstream uses scaling lists, reuses apsId, sets scaling lists ON and OFF. Uses slices, varying the scaling list enable flag in slice header. + +**Functional stage:** Inverse quantization. + +**Purpose:** Check that decoder can parse and use scaling list quantization matrices. + +##### 6.6.2.4.1 Entropy coding (ENTROPY) + +###### 6.6.2.4.1.1 Test bitstream ENTROPY\_A + +**Specification:** This bitstream uses high bitrate for Low Delay P mode, with MIP enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +###### 6.6.2.4.1.2 Test bitstream ENTROPY\_B + +**Specification:** The bitstream includes all combinations of cabac\_init\_flag in slice header (0, 1, absent). + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +###### 6.6.2.4.1.3 Test bitstream ENTROPY\_C + +**Specification:** Bitstream tests CABAC initialization, sweeping QP from 0 to 63. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +##### 6.6.2.4.2 Entropy coding (ENTMAINTIER) + +###### 6.6.2.4.2.1 Test bitstream ENTMAINTIER\_A + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 4. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +###### 6.6.2.4.2.2 Test bitstream ENTMAINTIER\_B + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 4.1. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +###### 6.6.2.4.2.3 Test bitstream ENTMAINTIER\_C + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 5. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +##### 6.6.2.42.4 *Test bitstream ENTMAINTIER\_D* + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 5.1. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +#### 6.6.2.43 Entropy coding (ENTHIGHTIER) + +##### 6.6.2.43.1 *Test bitstream ENTHIGHTIER\_A* + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 4 for High tier. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +##### 6.6.2.43.2 *Test bitstream ENTHIGHTIER\_B* + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 4.1 for High tier. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +##### 6.6.2.43.3 Test bitstream ENTHIGHTIER\_C + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 5 for High tier. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +##### 6.6.2.43.4 Test bitstream ENTHIGHTIER\_D + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 5.1 for High tier. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +#### 6.6.2.44 All merge modes (MERGE) + +##### 6.6.2.44.1 Test bitstream MERGE\_A + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 1 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 0. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +##### 6.6.2.44.2 Test bitstream MERGE\_B + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 2 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 2. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +##### 6.6.2.44.3 Test bitstream MERGE\_C + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 3 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 3. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +##### 6.6.2.44.4 Test bitstream MERGE\_D + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 4 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 4. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +##### **6.6.2.44.5 Test bitstream MERGE\_E** + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 5 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 5. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +##### **6.6.2.44.6 Test bitstream MERGE\_F** + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 1 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 0. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +##### **6.6.2.44.7 Test bitstream MERGE\_G** + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 2 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 2. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +##### **6.6.2.44.8 Test bitstream MERGE\_H** + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 3 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 3. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +##### **6.6.2.44.9 Test bitstream MERGE\_I** + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 4 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 4. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +##### **6.6.2.44.10 Test bitstream MERGE\_J** + +**Specification:** This bitstream exercises the maximum number of merge candidates (MaxNumMergeCand) = 5 and Maximum number of GPM merge candidates (MaxNumGpmMergeCand) = 5. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder properly decodes all merge modes. + +#### **6.6.2.45 Position dependent prediction combination (PDPC)** + +##### **6.6.2.45.1 Test bitstream PDPC\_A** + +**Specification:** This bitstream tests the clipping function in PDPC for horizontal or vertical intra prediction modes. + +**Functional stage:** Intra coding. + +**Purpose:** Check that the decoder properly decodes the bitstream when PDPC is enabled. + +##### **6.6.2.45.2 Test bitstream PDPC\_B** + +**Specification:** This bitstream uses DPC with various block sizes. + +**Functional stage:** Intra coding. + +**Purpose:** Check that the decoder properly decodes the bitstream when PDPC is enabled. + +##### **6.6.2.45.3 Test bitstream PDPC\_C** + +**Specification:** This bitstream tests the clipping function in PDPC and the PDPC conditional check on the intra prediction mode. In this test each picture is a single I-slice where all the luma blocks are encoded using an identical intra prediction mode. + +**Functional stage:** Intra coding. + +**Purpose:** Check that the decoder properly decodes the bitstream when PDPC is enabled. + +#### **6.6.2.46 Wavefronts (WPP)** + +##### **6.6.2.46.1 Test bitstream WPP\_A** + +**Specification:** The bitstream is encoded with sps\_entropy\_coding\_sync\_enabled\_flag equal to 1. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with wavefront enabled. + +##### **6.6.2.46.2 Test bitstream WPP\_B** + +**Specification:** The bitstream is encoded with rectangular tile and sps\_entropy\_coding\_sync\_enabled\_flag equal to 1 and pictures contain 4 tiles. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with wavefront enabled and tiles. + +#### **6.6.2.47 Lossless and near-lossless, include transform skip (LOSSLESS)** + +##### **6.6.2.47.1 Test bitstream LOSSLESS\_A** + +**Specification:** The coded slices are either I or B, and all blocks employ the transform skip mode and the regular residual coding stage for entropy coding. + +**Functional stage:** Test the parsing and reconstruction of slices. + +**Purpose:** Check that a decoder can parse and reconstruct correctly when the bitstream consists of transform skip mode and the regular residual coding stage operating at the lossless operation point. + +##### **6.6.2.47.2 Test bitstream LOSSLESS\_B** + +**Specification:** The coded slices are either I or B, and most of the blocks employ the transform skip mode and the corresponding residual coding stage for entropy coding. + +**Functional stage:** Test the parsing and reconstruction of slices. + +**Purpose:** Check that a decoder can parse and reconstruct correctly when the bitstream consists of a high amount of transform skip mode but using the transform skip residual coding for entropy coding. + +#### **6.6.2.48 Reference picture resizing (RPR)** + +##### **6.6.2.48.1 Test bitstream RPR\_A** + +**Specification:** This bitstream has 4 pictures. The bitstream contains CUs encoded with inter-prediction mode using reference pictures with a higher resolution than the current picture. The luma resolution is 832x480 for pictures 0 and 1 and 1664x960 for pictures 2 and 3. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with RPR enabled. + +##### 6.6.2.48.2 Test bitstream RPR\_B + +**Specification:** The bitstream contains CUs encoded with inter-prediction mode using reference pictures with a higher resolution than the current picture. The luma resolution is 832x480 for pictures 0 and 1 and of 416x240 for pictures 2 and 3. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with RPR enabled. + +##### 6.6.2.48.3 Test bitstream RPR\_C + +**Specification:** The bitstream contains CUs encoded with inter-prediction mode using reference pictures with a higher resolution than the current picture. The luma resolution is 832x480 for pictures 0 and 1 and of 560x320 for pictures 2 and 3. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with RPR enabled. + +##### 6.6.2.48.4 Test bitstream RPR\_D + +**Specification:** The bitstream uses reference picture resampling with 2x ratio with sps\_chroma\_horizontal\_collocated\_flag = 03. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with RPR enabled. + +#### 6.6.2.49 Cross-component ALF (CCALF) + +##### 6.6.2.49.1 Test bitstream CCALF\_A + +**Specification:** This bitstream enables CCALF with filters that would exceed the output dynamic range and require a clip. + +**Functional stage:** In-loop filtering. + +**Purpose:** Check that the decoder can properly decode bitstreams with CCALF enabled. + +##### 6.6.2.49.2 Test bitstream CCALF\_B + +**Specification:** This bitstream enables CCALF for all CTUs in the bitstream. + +**Functional stage:** In-loop filtering. + +**Purpose:** Check that the decoder can properly decode bitstreams with CCALF enabled. + +##### 6.6.2.49.3 Test bitstream CCALF\_C + +**Specification:** This bitstream changes CCALF filters on a picture-by-picture basis. + +**Functional stage:** In-loop filtering. + +**Purpose:** Check that the decoder can properly decode bitstreams with CCALF enabled. + +##### 6.6.2.49.4 Test bitstream CCALF\_D + +**Specification:** This bitstream enables CCALF for random CTUs in the bitstream (both channels). + +**Functional stage:** In-loop filtering. + +**Purpose:** Check that the decoder can properly decode bitstreams with CCALF enabled. + +#### 6.6.2.50 Geometric partitioning mode (GPM) + +##### 6.6.2.50.1 Test bitstream GPM\_A + +**Specification:** This bitstream contains CUs with all the combinations of geometric partition modes, i.e., all the WxH sized CUs with 0 – 63 geometric partition modes. The value of WxH is equal to one of the following values: {8x8, 8x16, 8x32, 16x8, 16x16, 16x32, 16x64, 32x8, 32x16, 32x32, 32x64, 64x16, 64x32 and 64x64}. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with GPM enabled. + +##### **6.6.2.50.2 Test bitstream GPM\_B** + +**Specification:** This bitstream uses different numbers of GPM candidates, including 2, 3, 4, 5 and 6. Correspondingly, the value of `sps_max_num_merge_cand_minus_max_num_gpm_cand` is set to 4, 3, 2, 1 and 0, respectively. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams with GPM enabled. + +#### **6.6.2.51 Coding tool sets (CodingToolSets)** + +##### **6.6.2.51.1 Test bitstream CodingToolSets\_A** + +**Specification:** This bitstream enables and disables coding tools corresponding to set A in Table 2. + +**Functional stage:** General decoding. + +**Purpose:** Check that a decoder can decode bitstreams using various combinations of coding tools. + +##### **6.6.2.51.2 Test bitstream CodingToolSets\_B** + +**Specification:** This bitstream enables and disables coding tools corresponding to set B in Table 2. + +**Functional stage:** General decoding. + +**Purpose:** Check that a decoder can decode bitstreams using various combinations of coding tools. + +##### **6.6.2.51.3 Test bitstream CodingToolSets\_C** + +**Specification:** This bitstream enables and disables coding tools corresponding to set C in Table 2. + +**Functional stage:** General decoding. + +**Purpose:** Check that a decoder can decode bitstreams using various combinations of coding tools. + +##### **6.6.2.51.4 Test bitstream CodingToolSets\_D** + +**Specification:** This bitstream enables and disables coding tools corresponding to set D in Table 2. + +**Functional stage:** General decoding. + +**Purpose:** Check that a decoder can decode bitstreams using various combinations of coding tools. + +##### **6.6.2.51.5 Test bitstream CodingToolSets\_E** + +**Specification:** This bitstream enables and disables coding tools corresponding to set E in Table 2. + +**Functional stage:** General decoding. + +**Purpose:** Check that a decoder can decode bitstreams using various combinations of coding tools. + +### **6.6.3 Test bitstreams – High-level syntax features for Main 10 profile with 4:2:0 chroma format and 10 bit depth** + +#### **6.6.3.1 Access unit delimiter (AUD)** + +##### **6.6.3.1.1 Test bitstream AUD\_A** + +**Specification:** Pictures may or may not include associated Access Unit Delimiter (AUD) NAL units. The first 10 pictures of this bitstream do not include AUD, the next 10 pictures included AUD, and finally the last 10 pictures do not include AUD. + +**Functional stage:** High-level syntax processing / picture boundary processing. + +**Purpose:** Check that the decoder can handle and transition between pictures with and without associated Access Unit Delimiter NAL units. + +#### 6.6.3.2 Filler (FILLER) + +##### 6.6.3.2.1 Test bitstream FILLER\_A + +**Specification:** Each picture includes associated Filler data NAL units. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when filler data NAL units are present in the bitstream. + +#### 6.6.3.3 Decoding Capability Indication (DCI) + +##### 6.6.3.3.1 Test bitstream DCI\_A + +**Specification:** The bitstream includes a DCI NAL unit. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when DCI NAL unit is present in the bitstream. + +##### 6.6.3.3.2 Test bitstream DCI\_B + +**Specification:** The bitstream does not include a DCI NAL unit. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when DCI NAL unit is not present in the bitstream. + +#### 6.6.3.4 Sequence parameter set (SPS) + +##### 6.6.3.4.1 Test bitstream SPS\_A + +**Specification:** Multiple SPSs are signalled in the same CVS. SPS with SPS ID equal to 0 is used and the other SPSs are never referenced. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when multiple SPSs, including unreferenced ones, are contained in the same CVS. + +##### 6.6.3.4.2 Test bitstream SPS\_B + +**Specification:** Multiple SPSs are signalled in the bitstream. Different SPS IDs are used in the different CVSs. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when different CVSs use different SPSs with different SPS IDs. + +##### 6.6.3.4.3 Test bitstream SPS\_C + +**Specification:** Multiple SPSs are signalled in the bitstream and SPS with SPS ID equal to 0 is used in the bitstream. ALF and BCW are enabled in SPS for the first two CVSs and are disabled in SPS for the third CVS. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when the content of an SPS is replaced while using the same SPS ID in different CVSs. + +#### 6.6.3.5 Video usability information (PQ, HLG) + +##### 6.6.3.5.1 Test bitstream PQ\_A + +**Specification:** This bitstream uses VUI transfer characteristics for PQ content. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder can properly parse the VUI. + +##### 6.6.3.5.2 Test bitstream HLG\_A + +**Specification:** This bitstream uses video usability information transfer characteristics for HLG content. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder can properly parse the VUI. + +##### 6.6.3.5.3 *Test bitstream HLG\_B* + +**Specification:** This bitstream uses VUI to indicate "backward-compatible HLG" which is encoded using transfer characteristics with encoded as 1 and also include the alternative transfer characteristics SEI message with preferred transfer characteristics set to 18. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder can properly parse the VUI. + +#### 6.6.3.6 **Picture parameter set (PPS)** + +##### 6.6.3.6.1 *Test bitstream PPS\_A* + +**Specification:** Multiple PPSs are signalled in the bitstream. PPS with PPS ID equal to 0 is used for each picture and the other PPSs are never referenced. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when multiple PPSs, including unreferenced ones, are contained in the same CVS. + +##### 6.6.3.6.2 *Test bitstream PPS\_B* + +**Specification:** Each picture uses an individual PPS with a different PPS ID. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when PPS IDs are switched for individual pictures in the bitstream. + +##### 6.6.3.6.3 *Test bitstream PPS\_C* + +**Specification:** Multiple PPSs are signalled in the bitstream. PPS with PPS ID equal to 0 is used for the first two CVSs. The content of the PPS is updated and used for all pictures in the second CVS. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when the content of a PPS is replaced while using the same PPS ID in different pictures. + +#### 6.6.3.7 **Mixed NUT (MNUT)** + +##### 6.6.3.7.1 *Test bitstream MNUT\_A* + +**Specification:** The bitstream contains mixed NAL unit types. Encoded subpicture bitstreams were merged into one bitstream using the subpicMergeApp tool that is included in the VTM package. The bitstream contains 4 subpictures arranged in 2x2 formation. The first subpicture bitstream has CRA subpicture every 32th picture while the other 3 subpicture bitstreams don't have IRAP pictures after the first picture. Hence, in every 32th picture there is a mix of CRA subpicture and trailing subpictures. The encoder was slightly modified to ensure that reference picture list syntax is the same for CRA bitstream and non-CRA bitstreams. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams with mixed NAL unit types in the same picture. + +##### 6.6.3.7.2 *Test bitstream MNUT\_B* + +**Specification:** The bitstream contains mixed NAL unit bitstream that contains mixed NAL unit types in some of the pictures and uses the sps\_idr\_rpl\_present\_flag syntax element. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams with mixed NAL unit types in the same picture. + +#### 6.6.3.8 Extension of parameter set (PSEXT) + +##### 6.6.3.8.1 Test bitstream PSEXT\_A + +**Specification:** The extension flag of the following parameter sets is set to one. DCI, VPS, SPS, PPS, APS. + +**Functional stage:** Test the handling when the extension\_flag is set to one and the related extension\_data is absent for the following parameter sets. DCI, VPS, SPS, PPS, APS. + +**Purpose:** Check that the decoder can parse the extension\_flag set to one and handle when the related extension\_data is absent for the following parameter sets. DCI, VPS, SPS, PPS, APS. + +##### 6.6.3.8.2 Test bitstream PSEXT\_B + +**Specification:** The extension flag of the following parameter sets is set to one. DCI, VPS, SPS, PPS, APS. + +**Functional stage:** Test the handling when the extension\_flag is set to one and the related extension\_data has one or more bits for the following parameter sets. DCI, VPS, SPS, PPS, APS. + +**Purpose:** Check that the decoder can parse the extension\_flag set to one and handle when the related extension\_data has one or more bits for the following parameter sets. DCI, VPS, SPS, PPS, APS. + +#### 6.6.3.9 Hypothetical reference decoder (HRD) + +##### 6.6.3.9.1 Test bitstream HRD\_A + +**Specification:** This bitstream tests AU-based HRD operation, using the Buffering Period SEI and Picture Timing SEI messages. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly process HRD data. + +##### 6.6.3.9.2 Test bitstream HRD\_B + +**Specification:** This bitstream tests AU-based HRD operation, using the Buffering Period SEI and Picture Timing SEI messages, with 2 DUs in each AU. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly process HRD data. + +#### 6.6.3.10 Adaptation parameter set (APSALF, APSLMCS, APSMULT, SUFAPS) + +##### 6.6.3.10.1 Test bitstream APSALF\_A + +**Specification:** This bitstream uses multiple ALF APS, with only ALF APS is present in the bitstream (LMCS and scaling list are disabled). + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams using APSs. + +##### 6.6.3.10.2 Test bitstream APSLMCS\_A + +**Specification:** The bitstream uses multiple (3) LMCS APS (APS id = 0, 1 and 2), only LMCS APS is present in the bitstream (ALF is disabled). + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams using APSs. + +##### 6.6.3.10.3 Test bitstream APSLMCS\_B + +**Specification:** The bitstream uses multiple (3) LMCS APS (APS id = 0, 1 and 2), both LMCS APS and ALF APS are present in the bitstream. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams using APSs. + +##### **6.6.3.10.4 Test bitstream APSLMCS\_C** + +**Specification:** The bitstream tests the use of LMCS APS with a large variation of lmcs CW values ([15 ~ 320]) in each of the 16 bins. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams using APSs. + +##### **6.6.3.10.5 Test bitstream APSLMCS\_D** + +**Specification:** The bitstream tests the use of LMCS APS with different min/max bin index. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams using APSs. + +##### **6.6.3.10.6 Test bitstream APSLMCS\_E** + +**Specification:** The bitstream tests the use of LMCS APS with negative CRSOffset value. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams using APSs. + +##### **6.6.3.10.7 Test bitstream APSMULT\_A** + +**Specification:** Multiple scaling list APSs (with scaling list APS ID equal to 0 and 1) are signalled in the bitstream. For each picture, the referenced scaling list APS ID is decided according to the picture's POC number. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when multiple scaling list APSs are contained in the same CVS. + +##### **6.6.3.10.8 Test bitstream APSMULT\_B** + +**Specification:** Multiple scaling list APSs are signalled in the bitstream with the same scaling list APS ID. When a scaling list ASP is signalled, it will overwrite the existing scaling list ASP. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when multiple scaling list APSs are contained in the same CVS, and they can be overwritten by each other. + +##### **6.6.3.10.9 Test bitstream SUFAPS\_A** + +**Specification:** The bitstream contains suffix APS NAL units for ALF. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams containing suffix APSs. + +#### **6.6.3.11 Random access points (RAP)** + +##### **6.6.3.11.1 Test bitstream RAP\_A** + +**Specification:** The bitstream starts with a CRA picture. The CRA picture is followed only by RASL pictures, which are expected to be discarded. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams containing various random access picture types. + +##### **6.6.3.11.2 Test bitstream RAP\_B** + +**Specification:** The bitstream starts with a CRA picture. The CRA picture is followed by RASL and other pictures. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams containing various random access picture types. + +##### 6.6.3.11.3 *Test bitstream RAP\_C* + +**Specification:** The bitstream contains IDR pictures with RADL pictures. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams containing various random access picture types. + +##### 6.6.3.11.4 *Test bitstream RAP\_D* + +**Specification:** The bitstream contains IDR pictures without leading pictures. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams containing various random access picture types. + +#### 6.6.3.12 Picture output (POUT) + +##### 6.6.3.12.1 *Test bitstream POUT\_A* + +**Specification:** This bitstream exercises picture output related syntax, with both values of ph\_pic\_output\_flag. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly output pictures. + +#### 6.6.3.13 Gradual decoder refresh (GDR) + +##### 6.6.3.13.1 *Test bitstream GDR\_A* + +**Specification:** The bitstream starts with GDR pictures with recovery POC = 0. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can decode and handle GDR signalling. + +##### 6.6.3.13.2 *Test bitstream GDR\_B* + +**Specification:** The bitstream starts with GDR picture (POC 10) with ph\_recovery\_poc\_cnt = 51. A second GDR picture starts at POC 70 with ph\_recovery\_poc\_cnt = 51. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can decode and handle GDR signalling. + +##### 6.6.3.13.3 *Test bitstream GDR\_C* + +**Specification:** The bitstream starts with a GDR picture (POC 60) and ph\_recovery\_poc\_cnt = 29 + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can decode and handle GDR signalling. + +##### 6.6.3.13.4 *Test bitstream GDR\_D* + +**Specification:** The bitstream exercises overlapping GDR periods with GDR pictures at POC 5, 6 and 30 with recovery points at POC 26, 33 and 51 respectively. The bitstream starts at POC 5 but conformance starts at POC 26. GDR picture at POC 5 references missing pictures POC 1-4, at POC 26 the refresh period has been completed and a decoder may start output. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can decode and handle GDR signalling. + +#### 6.6.3.14 Picture order count (POC) + +##### 6.6.3.14.1 *Test bitstream POC\_A* + +**Specification:** This bitstream exercises POC derivation, including POC reset, using the sps\_poc\_msb\_cycle\_flag, ph\_poc\_msb\_cycle\_present, ph\_poc\_msb\_cycle\_val and sps\_poc\_msb\_cycle\_len\_minus1 syntax elements. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly derive POC values. + +#### 6.6.3.15 Tiles (TILE) + +##### 6.6.3.15.1 *Test bitstream TILE\_A* + +**Specification:** Each picture contains a single tile and single slice. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode single tile and single slice case. + +##### 6.6.3.15.2 *Test bitstream TILE\_B* + +**Specification:** Each picture contains uniform tile partitioning along both horizontal and vertical directions with each tile containing single slice. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode uniformly partitioned tiles. + +##### 6.6.3.15.3 *Test bitstream TILE\_C* + +**Specification:** Each picture contains tile partitioning with one row and N columns with each tile containing single slice. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when tile partitioning has one row and N columns. + +##### 6.6.3.15.4 *Test bitstream TILE\_D* + +**Specification:** Each picture contains tile partitioning with N rows and one column with each tile containing single slice. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when tile partitioning has N rows and one column. + +##### 6.6.3.15.5 *Test bitstream TILE\_E* + +**Specification:** Each picture contains tile partitioning with M rows and N columns with each tile containing single slice. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when tile partitioning has M rows and N columns. + +##### 6.6.3.15.6 *Test bitstream TILE\_F* + +**Specification:** Each picture contains tile partitioning with M rows and N columns with each tile containing multiple slices. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when tile partitioning has M rows and N columns with each tile containing multiple slices. + +##### 6.6.3.15.7 *Test bitstream TILE\_G* + +**Specification:** Each picture contains tile partitioning with M rows and N columns and the whole picture containing a single slice. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when tile partitioning has M rows and N columns and the whole picture containing a single slice. + +#### 6.6.3.16 Slices (SLICES) + +##### 6.6.3.16.1 *Test bitstream SLICES\_A* + +**Specification:** This bitstream exercises several different slice/tile layouts. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when a variety of slice and tile layouts are used. + +#### 6.6.3.17 Subpictures (SUBPIC) + +##### 6.6.3.17.1 *Test bitstream SUBPIC\_A* + +**Specification:** This bitstream exercises several different subpicture layouts. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when a variety of subpicture layouts are used. + +##### 6.6.3.17.2 *Test bitstream SUBPIC\_B* + +**Specification:** This bitstream exercises several different subpicture and slice layouts. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode when a variety of subpicture layouts with slices are used. + +##### 6.6.3.17.3 *Test bitstream SUBPIC\_C* + +**Specification:** This bitstream exercises signalling of equal size subpictures where each subpicture includes only one tile, slice and CTU. Parameters for RPL, deblocking, SAO, ALF, weighted prediction and delta QP are signalled in the PH. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams with equal size subpictures and parameter information in the PH. + +##### 6.6.3.17.4 *Test bitstream SUBPIC\_D* + +**Specification:** This bitstream exercises signalling of subpictures with varying subpicture IDs using multiple PPSs in a way that demonstrates a panning of the field-of-view. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode subpictures when subpicture IDs vary in the CVS. + +##### 6.6.3.17.5 *Test bitstream SUBPIC\_E* + +**Specification:** Bitstream exercises deblocking control features across subpicture boundaries. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams when a variety of subpicture layouts and deblocking control features are used. + +#### 6.6.3.18 Picture header and slice header (PHSH) + +##### 6.6.3.18.1 *Test bitstream PHSH\_B* + +**Specification:** This bitstream includes two CVSs. In the first CVS, the picture header is included in the slice header. In the second CVS, the picture header is in its own NAL unit. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode a picture header whether included in a slice header or not. + +#### 6.6.3.19 Temporal scalability (TEMPSCAL) + +##### 6.6.3.19.1 *Test bitstream TEMPSCAL\_A* + +**Specification:** This bitstream has 6 temporal sublayers with a GOP size of 32. + +**Functional stage:** High-level syntax processing / GOP processing. + +**Purpose:** Check that the decoder can handle a GOP of 32. + +##### **6.6.3.19.2 Test bitstream TEMPSCAL\_B** + +**Specification:** This bitstream has 5 temporal sublayers with a GOP size of 16 and HRD signalling (including buffering period and picture timing SEI message with timing) for all temporal sublayers. + +**Functional stage:** High-level syntax processing / Hypothetical Reference Decoder. + +**Purpose:** Check the hypothetical reference decoder for temporal sublayers. + +##### **6.6.3.19.3 Test bitstream TEMPSCAL\_C** + +**Specification:** This bitstream has 3 temporal sublayers with a GOP size of 6. + +**Functional stage:** High-level syntax processing / GOP processing. + +**Purpose:** Check that the decoder can properly decode bitstreams with various hierarchy structures. + +#### **6.6.3.20 Inter-layer reference picture lists (ILRPL)** + +##### **6.6.3.20.1 Test bitstream ILRPL\_A** + +**Specification:** This bitstream contains two layers, with layer 1 referencing layer 0. + +**Functional stage:** High-level syntax processing/scalability. + +**Purpose:** Check that the decoder can properly decode bitstreams using inter layer reference prediction. + +#### **6.6.3.21 Reference picture lists (RPL)** + +##### **6.6.3.21.1 Test bitstream RPL\_A** + +**Specification:** RPL in SPS, PH and SH. Active and inactive entries. Maximum RPL length. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode and handle reference picture lists with short term references. + +#### **6.6.3.22 Long term ref picture (LTRP)** + +##### **6.6.3.22.1 Test bitstream LTRP\_A** + +**Specification:** LTRP handling and picture marking. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode and handle reference picture lists with short and long term references. + +#### **6.6.3.23 Number of active ref pics (ACTPIC)** + +##### **6.6.3.23.1 Test bitstream ACTPIC\_A** + +**Specification:** This bitstream contains 1 active picture in list 0, and 1 active picture in list 1. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams containing various numbers of active reference pictures. + +##### **6.6.3.23.2 Test bitstream ACTPIC\_B** + +**Specification:** This bitstream contains 1 active picture in list 0, and up to 2 active frames in list 1. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams containing various numbers of active reference pictures. + +##### **6.6.3.23.3 Test bitstream ACTPIC\_C** + +**Specification:** This bitstream contains 1 active picture in list 0, and up to 2 active frames in list 1. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams containing various numbers of active reference pictures. + +#### 6.6.3.24 Virtual boundaries (VIRTUAL) + +##### 6.6.3.24.1 Test bitstream VIRTUAL\_A + +**Specification:** Virtual boundaries are enabled and signalled in SPS with 3 vertical and 2 horizontal virtual boundaries. + +**Functional stage:** High-level syntax processing and in-loop filter process. + +**Purpose:** Check that the decoder can properly decode and handle the virtual boundaries signalled in the SPS. + +##### 6.6.3.24.2 Test bitstream VIRTUAL\_B + +**Specification:** Virtual boundaries are enabled and signalled in PH only for pictures with an odd POC value. When virtual boundaries are enabled in a picture, 2 vertical and 1 horizontal virtual boundaries are applied. + +**Functional stage:** High-level syntax processing and in-loop filter process. + +**Purpose:** Check that the decoder can properly decode and handle the virtual boundaries signalled in the PH. + +#### 6.6.3.25 Reference wraparound (WRAP) + +##### 6.6.3.25.1 Test bitstream WRAP\_A + +**Specification:** This bitstream uses reference wraparound mode with content using the PERP format for 360° video in random access mode. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams using reference wraparound. + +##### 6.6.3.25.2 Test bitstream WRAP\_B + +**Specification:** This bitstream uses reference wraparound mode with content using the PERP format for 360° video in random access mode. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams using reference wraparound. + +##### 6.6.3.25.3 Test bitstream WRAP\_C + +**Specification:** This bitstream uses reference wraparound mode with content using the PERP format for 360° video in low delay B mode. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams using reference wraparound. + +### 6.6.3.25.4 Test bitstream WRAP\_D + +**Specification:** This bitstream uses reference wraparound mode with content using the PERP format for 360° video in low delay B mode. + +**Functional stage:** Inter prediction. + +**Purpose:** Check that the decoder can properly decode bitstreams using reference wraparound. + +#### 6.6.3.26 360-degree video (CUBEMAP, ERP) + +##### 6.6.3.26.1 Test bitstream CUBEMAP\_A + +**Specification:** A generalized cubemap projection SEI message is signalled in the bitstream with packing type equal to 2, mapping function equal to 2, and guard band flag equal to 0 to indicate that the coded pictures are 3x2-packed non-uniform cubemap projected pictures without guard bands. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can parse the generalized cubemap projection SEI message. + +#### 6.6.3.26.2 Test bitstream CUBEMAP\_B + +**Specification:** A generalized cubemap projection SEI message is signalled in the bitstream with packing type equal to 3, mapping function equal to 1, and guard band flag equal to 1 to indicate that the coded pictures are 6x1-packed equal-angular cubemap projected pictures with guard bands. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can parse the generalized cubemap projection SEI message. + +#### 6.6.3.26.3 Test bitstream CUBEMAP\_C + +**Specification:** A generalized cubemap projection SEI message is signalled in the bitstream with packing type equal to 4, mapping function equal to 0, and guard band flag equal to 1 to indicate that the coded pictures are 5x1-packed hemicylindrical projection pictures with guard bands. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can parse the generalized cubemap projection SEI message. + +#### 6.6.3.26.4 Test bitstream ERP\_A + +**Specification:** An equirectangular projection SEI message is signalled in the bitstream with guard band flag equal to 1 to indicate that the coded pictures are equirectangular projected pictures with guard bands on the left and right sides. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can parse the equirectangular projection SEI message. + +### 6.6.3.27 Conformance cropping window (CROP) + +#### 6.6.3.27.1 Test bitstream CROP\_A + +**Specification:** This bitstream uses large offsets for the conformance cropping window that are not aligned with CTU boundaries. + +**Functional stage:** High-level syntax processing / conformance cropping. + +**Purpose:** Check that the decoder outputs the correct conformance cropped region. + +#### 6.6.3.27.2 Test bitstream CROP\_B + +**Specification:** The bitstream uses odd offset values for the conformance cropping window. + +**Functional stage:** High-level syntax processing / conformance cropping. + +**Purpose:** Check that the decoder outputs the correct conformance cropped region. + +### 6.6.3.28 Bumping (BUMP) + +#### 6.6.3.28.1 Test bitstream BUMP\_A + +**Specification:** This bitstream exercises bumping process in regard to the setting of DPB size and reordering. The bitstream is generated with optimized values for `dpb_max_dec_pic_buffering_minus1[ i ]` and `dpb_max_num_reorder_pics[ i ]`. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams exercising the DPB bumping process. + +#### 6.6.3.28.2 Test bitstream BUMP\_B + +**Specification:** This bitstream exercises bumping process in regard to the setting of DPB size and reordering. The bitstream is generated with optimized value for `dpb_max_num_reorder_pics[ i ]` but with DPB size that is more than the optimal one. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams exercising the DPB bumping process. + +#### 6.6.3.28.3 *Test bitstream BUMP\_C* + +**Specification:** This bitstream exercises bumping process in regard to the setting of DPB size and reordering. The bitstream is generated with non-optimal values for both `dpb_max_dec_pic_buffering_minus1[i]` and `dpb_max_num_reorder_pics[i]`. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams exercising the DPB bumping process. + +#### 6.6.3.29 Decoded picture buffer (DPB) + +##### 6.6.3.29.1 *Test bitstream DPB\_A* + +**Specification:** This bitstream signals sublayer decoded picture buffer (DPB) sizes for multiple sublayers. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that decoder can properly decode bitstreams exercising various DPB parameters. + +##### 6.6.3.29.2 *Test bitstream DPB\_B* + +**Specification:** This bitstream signals sublayer decoded picture buffer (DPB) size for a single sublayer. + +**Functional stage:** High-level syntax processing. + +**Purpose:** Check that the decoder can properly decode bitstreams exercising various DPB parameters. + +#### 6.6.3.30 Field pictures (FIELD) + +##### 6.6.3.30.1 *Test bitstream FIELD\_A* + +**Specification:** This bitstream, contains frame-field information SEI messages for each picture indicating either it is top or bottom field coded. + +**Functional stage:** Test field coding when `sps_field_seq_flag` is equal to 1. + +**Purpose:** Check that the decoder can properly decode pictures coded in field coding. + +##### 6.6.3.30.2 *Test bitstream FIELD\_B* + +**Specification:** This bitstream has `field_seq_flag` in SPS is equal to 1 contains frame-field information SEI messages. Different values of `vui_chroma_sample_loc_type_top_field` and `vui_chroma_sample_loc_type_bottom_field` are tested. + +**Functional stage:** Test field coding when `sps_field_seq_flag` is equal to 1. + +**Purpose:** Check that the decoder can properly decode pictures coded in field coding. + +### 6.6.4 Test bitstreams – Additional chroma formats and bit depths for Main 10 profile + +#### 6.6.4.1 8 bit 4:0:0 (8b400) + +##### 6.6.4.1.1 *Test bitstream 8b400\_A* + +**Specification:** 8-bit 4:0:0 bitstream at a low resolution. + +**Functional stage:** Additional chroma format and bit depth setting. + +**Purpose:** Check that the decoder can properly handle the chroma format of 4:0:0 and `InternalBitDepth` of 8. + +##### 6.6.4.1.2 *Test bitstream 8b400\_B* + +**Specification:** 8-bit 4:0:0 bitstream at a higher resolution. + +**Functional stage:** Additional chroma format and bit depth setting. + +**Purpose:** Check that the decoder can properly handle the chroma format of 4:0:0 and `InternalBitDepth` of 8. + +#### 6.6.4.2 8 bit 4:2:0 (8b420) + +##### 6.6.4.2.1 Test bitstream 8b420\_A + +**Specification:** 8-bit 4:2:0 bitstream at a low resolution. + +**Functional stage:** Additional bit depth setting. + +**Purpose:** Check that the decoder can properly handle the InternalBitDepth of 8. + +##### 6.6.4.2.2 Test bitstream 8b420\_B + +**Specification:** 8-bit 4:2:0 bitstream at a higher resolution. + +**Functional stage:** Additional bit depth setting. + +**Purpose:** Check that the decoder can properly handle the InternalBitDepth of 8. + +#### 6.6.5 Test bitstreams – Coding tools for Main 10 4:4:4 profile for 4:4:4 chroma format and 10 bit depth + +##### 6.6.5.1 10-bit 4:4:4 (10b444) + +###### 6.6.5.1.1 Test bitstream 10b444\_A + +**Specification:** The bitstream is 10-bit 4:4:4, in all intra mode, and does not enable any 4:4:4-specific tools. + +**Functional stage:** Decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +###### 6.6.5.1.2 Test bitstream 10b444\_B + +**Specification:** The bitstream is 10-bit 4:4:4, in random access mode, and does not enable any 4:4:4-specific tools. + +**Functional stage:** Decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +##### 6.6.5.2 Adaptive colour transform (ACT) + +###### 6.6.5.2.1 Test bitstream ACT\_A + +**Specification:** This bitstream tests ACT with CU level adaptation of the colour spaces between RGB and YCoCg, in random access mode. The bitstream is Main 10 4:4:4 profile, Main tier, Level 6. + +**Functional stage:** Adaptive colour transform. + +**Purpose:** Check that the decoder can properly decode bitstreams with ACT enabled. + +###### 6.6.5.2.2 Test bitstream ACT\_B + +**Specification:** This bitstream tests ACT with CU level adaptation of the colour spaces between RGB and YCoCg, in all intra mode. The bitstream is Main 10 4:4:4 profile, Main tier, Level 6. + +**Functional stage:** Adaptive colour transform. + +**Purpose:** Check that the decoder can properly decode bitstreams with ACT enabled. + +##### 6.6.5.3 Palette mode (PALETTE) + +###### 6.6.5.3.1 Test bitstream PALETTE\_A + +**Specification:** This bitstream forces the majority of the CUs to be coded using palette mode in a Random Access configuration. The bitstream conforms to the Main 10 4:4:4 profile, Main tier. + +**Functional stage:** Palette. + +**Purpose:** Check that the decoder can properly decode bitstreams with palette mode enabled. + +#### 6.6.5.3.2 Test bitstream *PALETTE\_B* + +**Specification:** This bitstream forces the majority of the CUs to be coded using palette mode in an All Intra configuration. The bitstream conforms to the Main 10 4:4:4 profile, Main tier. + +**Functional stage:** Palette. + +**Purpose:** Check that the decoder can properly decode bitstreams with palette mode enabled. + +#### 6.6.5.3.3 Test bitstream *PALETTE\_C* + +**Specification:** This bitstream forces the majority of the CUs to be coded using palette mode in a Low Delay B configuration. The bitstream conforms to the Main 10 4:4:4 profile, Main tier. + +**Functional stage:** Palette. + +**Purpose:** Check that the decoder can properly decode bitstreams with palette mode enabled. + +#### 6.6.5.3.4 Test bitstream *PALETTE\_D* + +**Specification:** This bitstream forces the majority of the CUs to be coded using palette mode in an All Intra configuration. The bitstream conforms to the Main 10 4:4:4 profile, Main tier. + +**Functional stage:** Palette. + +**Purpose:** Check that the decoder can properly decode bitstreams with palette mode enabled. + +#### 6.6.5.3.5 Test bitstream *PALETTE\_E* + +**Specification:** This bitstream forces the majority of the CUs to be coded using palette mode in an All Intra configuration. The bitstream use 4:2:0 chroma format but conforms to the Main 10 4:4:4 profile, Main tier, Level 3, which supports use of palette mode for 4:2:0. + +**Functional stage:** Palette. + +**Purpose:** Check that the decoder can properly decode bitstreams with palette mode enabled. + +### 6.6.5.4 Entropy coding (ENT444MAINTIER) + +#### 6.6.5.4.1 Test bitstream *ENT444MAINTIER\_A* + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 4. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +#### 6.6.5.4.2 Test bitstream *ENT444MAINTIER\_B* + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 4.1. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +#### 6.6.5.4.3 Test bitstream ENT444MAINTIER\_C + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 5. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +#### 6.6.5.4.4 Test bitstream ENT444MAINTIER\_D + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 5.1. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +### 6.6.5.5 Entropy coding (ENT444HIGHTIER) + +#### 6.6.5.5.1 Test bitstream ENT444HIGHTIER\_A + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 4 for High tier. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +#### 6.6.5.5.2 Test bitstream ENT444HIGHTIER\_B + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 4.1 for High tier. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +#### 6.6.5.5.3 Test bitstream ENT444HIGHTIER\_C + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 5 for High tier. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +#### 6.6.5.5.4 Test bitstream ENT444HIGHTIER\_D + +**Specification:** The bitstream contains 3 independent CVSs containing one picture, formed from one slice. Each CVS contains the maximum number of bits, given the profile, level and tier, and assuming equal distribution of bits between pictures coded at the maximum luma sample rate for the level, at Level 5.1 for High tier. The 3 concatenated CVSs are as follows: + +- The first picture does not require any CABAC zero words. +- The second picture requires one CABAC zero word. +- The third picture requires a substantial quantity of CABAC zero words (75% of the bitstream is padding). + +All 3 pictures have a very low subjective quality level due to the artificial nature of these bitstreams. All VCL NAL units contain almost (within 3 bytes worth) of the maximum number of allowed bins, for their size. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder properly decodes all entropy coding modes. + +### 6.6.6 Test bitstreams – Additional chroma formats and bit depths for Main 10 4:4:4 profile + +#### 6.6.6.1 8 bit 4:2:2 (8b422) + +##### 6.6.6.1.1 Test bitstream 8b422\_A + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in All Intra mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +##### 6.6.6.1.2 Test bitstream 8b422\_B + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in All Intra mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +##### 6.6.6.1.3 Test bitstream 8b422\_C + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Low Delay P mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.1.4 Test bitstream 8b422\_D*** + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Low Delay P mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.1.5 Test bitstream 8b422\_E*** + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Random Access mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.1.6 Test bitstream 8b422\_F*** + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Random Access mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.1.7 Test bitstream 8b422\_G*** + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in All Intra mode with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.1.8 Test bitstream 8b422\_H*** + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in All Intra mode with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.1.9 Test bitstream 8b422\_I*** + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Low Delay P mode with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.1.10 Test bitstream 8b422\_J*** + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Low Delay P mode with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.1.11 Test bitstream 8b422\_K*** + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Random Access mode with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.1.12 Test bitstream 8b422\_L*** + +**Specification:** 8-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Random Access mode with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:2:2 chroma format. + +#### **6.6.6.2 8 bit 4:4:4 (8b444)** + +##### ***6.6.6.2.1 Test bitstream 8b444\_A*** + +**Specification:** This bitstream uses 8-bit with 4:4:4 for All Intra. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:4:4 chroma format. + +##### ***6.6.6.2.2 Test bitstream 8b444\_B*** + +**Specification:** This bitstream uses 8-bit with 4:4:4 for random access. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 8-bit depth and 4:4:4 chroma format. + +#### **6.6.6.3 10 bit 4:0:0 (10b400)** + +##### ***6.6.6.3.1 Test bitstream 10b400\_A*** + +**Specification:** 10-bit 4:0:0 bitstream at a low resolution. + +**Functional stage:** Additional chroma format setting. + +**Purpose:** Check that the decoder can properly handle the chroma format of 4:0:0. + +##### ***6.6.6.3.2 Test bitstream 10b400\_B*** + +**Specification:** 10-bit 4:0:0 bitstream at a higher resolution. + +**Functional stage:** Additional chroma format setting. + +**Purpose:** Check that the decoder can properly handle the chroma format of 4:0:0. + +#### **6.6.6.4 10 bit 4:2:2 (10b422)** + +##### ***6.6.6.4.1 Test bitstream 10b422\_A*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in All Intra mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +##### ***6.6.6.4.2 Test bitstream 10b422\_B*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in All Intra mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +##### ***6.6.6.4.3 Test bitstream 10b422\_C*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Low Delay P mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +##### ***6.6.6.4.4 Test bitstream 10b422\_D*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Low Delay P mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.4.5 Test bitstream 10b422\_E*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Random Access mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.4.6 Test bitstream 10b422\_F*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Random Access mode. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.4.7 Test bitstream 10b422\_G*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in All Intra mode, with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.4.8 Test bitstream 10b422\_H*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in All Intra mode, with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.4.9 Test bitstream 10b422\_I*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Low Delay P mode, with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.4.10 Test bitstream 10b422\_J*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Low Delay P mode, with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.4.11 Test bitstream 10b422\_K*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Random Access mode, with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +#### ***6.6.6.4.12 Test bitstream 10b422\_L*** + +**Specification:** 10-bit 4:2:2 bitstream for Main 10 4:4:4 profile, in Random Access mode, with screen content coding tools enabled. + +**Functional stage:** Reconstruction. + +**Purpose:** Check that the decoder can properly decode content coded with 10-bit depth and 4:2:2 chroma format. + +## 6.6.7 Test bitstreams – Multilayer Main 10 profile + +### 6.6.7.1 Video parameter set (VPS) + +#### 6.6.7.1.1 Test bitstream VPS\_A + +**Specification:** The bitstream contains two dependent layers. Layer 0 is encoded with 208x120 input video and layer 1 is encoded with 832x480 input video. Inter-layer prediction is enabled for layer 1 (spatial scalability). + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder can properly decode when the VPS is present in the bitstream. + +#### 6.6.7.1.2 Test bitstream VPS\_B + +**Specification:** The bitstream contains a single VPS with three dependent layers. Layer 0 is encoded with 416x240 input video, layer 1 with 640x360 input video and layer 3 with 832x480 input video. Inter-layer prediction is enabled for layer 1 and layer 2. Layer 2 does not reference layer 0. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder can properly decode when the VPS is present in the bitstream and not all reference layers are direct reference layers. + +#### 6.6.7.1.3 Test bitstream VPS\_C + +**Specification:** The bitstream contains a single VPS with two dependent layers that exercises signalling of sublayer levels. Layer 0 is encoded with 176x144 input video and layer 1 with 416x240 input video. Inter-layer prediction is enabled for layer 1. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder can properly decode when the VPS is present in the bitstream and sublayer levels are signalled. + +### 6.6.7.2 Layered coding with OLS (OLS) + +#### 6.6.7.2.1 Test bitstream OLS\_A + +**Specification:** The bitstream is encoded with two layers, disallowing inter-layer prediction. + +**Functional stage:** High-level syntax processing with multi-layers. + +**Purpose:** Check that the decoder can properly decode when two layers are independently coded and extract a sub-bitstream. + +#### 6.6.7.2.2 Test bitstream OLS\_B + +**Specification:** The bitstream is encoded with two layers, allowing inter-layer prediction. + +**Functional stage:** High-level syntax processing with multi-layers. + +**Purpose:** Check that the decoder can properly decode when two layers are coded with layer dependencies, and extract a sub-bitstream. + +#### 6.6.7.2.3 Test bitstream OLS\_C + +**Specification:** The bitstream is encoded with three layers, allowing inter-layer prediction. + +**Functional stage:** High-level syntax processing with multi-layers. + +**Purpose:** Check that the decoder can properly decode when three layers are coded with layer dependencies, and extract a sub-bitstream. + +#### 6.6.7.2.4 Test bitstream OLSMultiProfile\_A + +**Specification:** The bitstream is coded with two layers, where OLS0 including the lower layer specifies the Main 10 profile whereas OLS1 including both layers specifies the Multilayer Main 10 profile. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that a decoder supporting the Main 10 profile can properly decode OLS0 and a decoder supporting the Multilayer Main 10 profile can properly decode both OLS0 and OLS1. + +#### ***6.6.7.2.5 Test bitstream OLSMultiProfile\_B*** + +**Specification:** The bitstream is coded with two layers, where each layer is coded as an independent layer and both OLSs specify the Main 10 profile. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that a decoder supporting the Main 10 profile can properly decode both OLSs. + +#### ***6.6.7.2.6 Test bitstream OLSMultiProfile\_C*** + +**Specification:** The bitstream is coded with three layers, where the lowest independent layer is referenced from the two higher layers, where the OLSs for the higher layers specify the Multilayer Main 10 profile whereas OLS0 specifies the Main 10 profile. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that a decoder supporting the Main 10 profile can properly decode OLS0 and a decoder supporting the Multilayer Main 10 profile can properly decode all the OLSs. + +#### ***6.6.7.2.7 Test bitstream PPSScalWin\_A*** + +**Specification:** The bitstream is coded with two layers, where the base layer is coded with the scaling window disabled and the enhancement layer is coded with the scaling window enabled. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that a decoder supports a scaling window. + +#### ***6.6.7.2.8 Test bitstream PPSScalWin\_B*** + +**Specification:** The bitstream is coded with two layers, where the base layer is coded with a scaling window enabled and the enhancement layer is coded with the scaling window disabled. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder supports a scaling window. + +#### ***6.6.7.2.9 Test bitstream PPSScalWin\_C*** + +**Specification:** The bitstream is coded with two layers, where both the base and enhancement layers are coded with a scaling window enabled. The sizes of the scaling windows are different for the two layers. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder supports scaling windows. + +#### ***6.6.7.2.10 Test bitstream ILRPL\_B*** + +**Specification:** The bitstream is coded with a GOP size of 16 with two layers, where the base layer is a downscaled version of the layer 1 source video, with a ratio (0.5, 0.5). Layer 1 has no intra pictures and has both inter-layer and intra-layer reference pictures. + +**Functional stage:** High-level syntax, reference picture lists. + +**Purpose:** In this bitstream, two features are tested: + +1. Avoiding intra pictures in a dependent layer. +2. Exercising multiple reference pictures with mixed inter-layer and intra-layer dependencies. + +### **6.6.7.3 Operating point information NAL unit (OPI)** + +#### ***6.6.7.3.1 Test bitstream OPI\_A*** + +**Specification:** The bitstream has output layer set and a subset of sublayers compared to the information given in VPS, where the bitstream has been extracted from a two-layer original bitstream. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder can properly decode extracted bitstreams. + +#### 6.6.7.3.2 *Test bitstream OPI\_B* + +**Specification:** The bitstream tests that the decoder can properly infer the OLS index and the highest temporal ID from the VPS when the OPI NAL unit in the bitstream does not contain the OLS index and the highest temporal ID, from a two-layer bitstream. + +**Functional stage:** High-level syntax. + +**Purpose:** Check that the decoder can properly decode extracted bitstreams. + +#### 6.6.7.4 Spatial scalability (SPATSCAL) + +##### 6.6.7.4.1 *Test bitstream SPATSCAL\_A* + +**Specification:** Spatial scalability with noncontinuous 3 layers 0, 30, 50. Scaling ratios are (1.05x, 0.75x), (0.51x, 0.69x), (0.54x, 0.51x). + +**Functional stage:** Spatial scalability. + +**Purpose:** Check that the decoder can properly decode bitstreams with noncontinuous layers and atypical scaling ratios. + +#### 6.6.8 Test bitstreams – Multilayer Main 10 4:4:4 profile + +##### 6.6.8.1 Spatial scalability (SPATSCAL444) + +###### 6.6.8.1.1 *Test bitstream SPATSCAL444\_A* + +**Specification:** Spatial scalability with noncontinuous 3 layers 0, 30, 50. Scaling ratios are (1.05x, 0.75x), (0.51x, 0.69x), (0.54x, 0.51x). + +**Functional stage:** Spatial scalability. + +**Purpose:** Check that the decoder can properly decode bitstreams with noncontinuous layers and atypical scaling ratios. + +#### 6.6.9 Test bitstreams – Main 10 Still Picture profile + +##### 6.6.9.1 Still picture (STILL) + +###### 6.6.9.1.1 *Test bitstream STILL\_A* + +**Specification:** The bitstream contains a single picture and exercises tools defined for the still picture profiles. + +**Functional stage:** Still picture. + +**Purpose:** Check that the decoder can properly decode bitstreams conforming to the still picture profiles. + +###### 6.6.9.1.2 *Test bitstream STILL\_B* + +**Specification:** This bitstream tests a Main 10 Still Picture decoder's capability of decoding the first picture of a bitstream conforming to the Main 10 profile when the first picture of the bitstream is a GDR picture with ph\_recovery\_poc\_cnt equal to 0. + +**Functional stage:** Still picture. + +**Purpose:** Check that a Main 10 Still Picture decoder can decode the first picture of a Main 10 profile bitstream when the first picture of the bitstream is a GDR picture with ph\_recovery\_poc\_cnt equal to 0. + +#### 6.6.10 Test bitstreams – Main 10 4:4:4 Still Picture profile + +##### 6.6.10.1 Still picture (STILL444) + +###### 6.6.10.1.1 *Test bitstream STILL444\_A* + +**Specification:** The bitstream contains a single picture and exercises tools defined for the still picture profiles. + +**Functional stage:** Still picture. + +**Purpose:** Check that the decoder can properly decode bitstreams conforming to the still picture profiles. + +#### **6.6.10.1.2 Test bitstream STILL444\_B** + +**Specification:** This bitstream tests a Main 10 4:4:4 Still Picture decoder's capability of decoding the first picture of a bitstream conforming to the Main 10 4:4:4 profile when the first picture of the bitstream is an IDR picture. + +**Functional stage:** Still picture. + +**Purpose:** Check that a Main 10 4:4:4 Still Picture decoder can decode the first picture of a Main 10 4:4:4 profile bitstream when the first picture of the bitstream is an IDR picture. + +### **6.6.11 Test bitstreams – Main 12 profile** + +#### **6.6.11.1 VVCv1 tools set** + +##### **6.6.11.1.1 Test bitstream 12b420vvc1\_A** + +**Specification:** The bitstream is 12-bit 4:2:0 video data being coded with various random access picture types, VVCv1 tools set is enabled and VVCv2 tools are disabled. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +### **6.6.12 Test bitstreams – Main 12 Intra profile** + +#### **6.6.12.1 VVCv1 tools set** + +##### **6.6.12.1.1 Test bitstream 12b420Ivvc1\_A** + +**Specification:** The bitstream is 12-bit 4:2:0, in all intra mode, VVCv1 tools set is enabled and VVCv2 tools are disabled. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +### **6.6.13 Test bitstreams – Main 12 Still Picture profile** + +#### **6.6.13.1 VVCv1 tools set** + +##### **6.6.13.1.1 Test bitstream 12b420SPvvc1\_A** + +**Specification:** The bitstream contains a single picture in 12-bit 4:2:0 chroma format, VVCv1 tools set is enabled and VVCv2 tools are disabled. + +**Functional stage:** Still picture. + +**Purpose:** Check that the decoder can properly decode bitstreams conforming to the still picture profiles. + +### **6.6.14 Test bitstreams – Main 12 4:4:4 profile** + +#### **6.6.14.1 VVCv1 tools set** + +##### **6.6.14.1.1 Test bitstream 12b444vvc1\_A** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv1 toolset is enabled and no VVCv2 tools (EPP, ERRc, PRRC, ETSRC, RLSCP) are enabled. Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +##### **6.6.14.1.2 Test bitstream 12b444vvc1\_B** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv1 toolset is enabled and no VVCv2 tools (EPP, ERRc, PRRC, ETSRC, RLSCP) are enabled. Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +#### **6.6.14.1.3 Test bitstream 12b444vvc1\_C** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv1 toolset is enabled and no VVCv2 tools (EPP, ERRc, PRRC, ETSRC, RLSCP) are enabled. Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +#### **6.6.14.1.4 Test bitstream 12b444vvc1\_D** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv1 toolset is enabled and no VVCv2 tools (EPP, ERRc, PRRC, ETSRC, RLSCP) are enabled. Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +#### **6.6.14.1.5 Test bitstream 12b444vvc1\_E** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv1 toolset is enabled and no VVCv2 tools (EPP, ERRc, PRRC, ETSRC, RLSCP) are enabled. Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +### **6.6.14.2 Extended precision processing (EPP)** + +#### **6.6.14.2.1 Test bitstream 12b444epp\_A** + +**Specification:** The bitstream is 12-bit 4:4:4 video data being coded with random access picture types and EPP enabled. + +**Functional stage:** Transformation process and entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with EPP enabled. + +### **6.6.14.3 Extended RRC (ERRc)** + +#### **6.6.14.3.1 Test bitstream 12b444errc\_A** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded with random access picture types, testing of the ERRc functionality, PRRC is enabled, Level 4.1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRc enabled. + +#### **6.6.14.3.2 Test bitstream 12b444errc\_B** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded with random access picture types, testing of the ERRc functionality, PRRC is disabled, Level 4.1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRc enabled. + +#### **6.6.14.3.3 Test bitstream 12b444errc\_C** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded with random access picture types, testing of the ERRc functionality, PRRC is enabled, Level 5.1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRc enabled. + +#### 6.6.14.4 Persistent RRC (PRRC) + +##### 6.6.14.4.1 Test bitstream 12b444prrc\_A + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded with random access picture types, testing of the PRRC functionality, ERRRC is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with PRRC enabled. + +#### 6.6.14.5 Extended TSRC (ETSRC) + +##### 6.6.14.5.1 Test bitstream 12b444etsrc\_A + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded with various random access picture types and ETSRC enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### 6.6.14.6 Reversed last significant coefficient position (RLSCP) + +##### 6.6.14.6.1 Test bitstream 12b444rlscp\_A + +**Specification:** The bitstream is 12-bit 4:4:4 video data being coded with various random access picture types and RLSCP enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with RLSCP enabled. + +#### 6.6.14.7 Wavefront parallel process (WPP) + +##### 6.6.14.7.1 Test bitstream 12b444wpp\_A + +**Specification:** The bitstream is 12-bit 4:4:4 video data being coded with various random access picture types and sps\_entropy\_coding\_sync\_enabled\_flag equal to 1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode bitstreams with wavefront enabled. + +#### 6.6.14.8 Chroma format and bit depth + +##### 6.6.14.8.1 Test bitstream 10b444P12\_A + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv2 tools (EPP, ERRRC, PRRC, ETSRC, RLSCP) are not used due to bit depth constraint. Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +##### 6.6.14.8.2 Test bitstream 10b444P12\_B + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv2 tools (EPP, ERRRC, PRRC, ETSRC, RLSCP) are not used due to bit depth constraint. Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +##### 6.6.14.8.3 Test bitstream 10b444P12\_C + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv2 tools (EPP, ERRRC, PRRC, ETSRC, RLSCP) are not used due to bit depth constraint. Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +**6.6.14.8.4 Test bitstream 10b444P12\_D** + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv2 tools (EPP, ERRc, PRRC, ETSRC, RLSCP) are not used due to bit depth constraint. Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +**6.6.14.8.5 Test bitstream 10b444P12\_E** + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 12 4:4:4 profile. VVCv2 tools (EPP, ERRc, PRRC, ETSRC, RLSCP) are not used due to bit depth constraint. Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +**6.6.14.8.6 Test bitstream 12b400P12\_A** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 12 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.14.8.7 Test bitstream 12b400P12\_B** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 12 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.14.8.8 Test bitstream 12b400P12\_C** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 12 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.14.8.9 Test bitstream 12b400P12\_D** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 12 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.14.8.10 Test bitstream 12b400P12\_E** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 12 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.14.8.11 Test bitstream 12b420P12\_A** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 12 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.14.8.12 Test bitstream 12b420P12\_B** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 12 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.14.8.13 Test bitstream 12b420P12\_C** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 12 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.14.8.14 Test bitstream 12b420P12\_D** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 12 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.14.8.15 Test bitstream 12b420P12\_E** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 12 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.14.8.16 Test bitstream 12b422P12\_A** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 12 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.14.8.17 Test bitstream 12b422P12\_B** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 12 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.14.8.18 Test bitstream 12b422P12\_C** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 12 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.14.8.19 Test bitstream 12b422P12\_D** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 12 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.14.8.20 Test bitstream 12b422P12\_E** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 12 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.15 Test bitstreams – Main 12 4:4:4 Intra profile** + +**6.6.15.1 VVCv1 tools set** + +**6.6.15.1.1 Test bitstream 12b444Ivvc1\_A** + +**Specification:** The bitstream is 12-bit 4:4:4, in all intra mode, VVCv1 tools set is enabled and VVCv2 tools are disabled. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +#### **6.6.15.2 Extended precision processing (EPP)** + +##### ***6.6.15.2.1 Test bitstream 12b444Iepp\_A*** + +**Specification:** The bitstream is 12-bit 4:4:4, in all intra mode and EPP enabled. + +**Functional stage:** Transformation process and entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with EPP enabled. + +#### **6.6.15.3 Extended RRC (ERRC)** + +##### ***6.6.15.3.1 Test bitstream 12b444Ierrc\_A*** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in all intra configuration, testing of the ERRC functionality, PRRC is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRC enabled. + +##### ***6.6.15.3.2 Test bitstream 12b444Ierrc\_B*** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in all intra configuration, testing of the ERRC functionality, PRRC is disabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRC enabled. + +#### **6.6.15.4 Persistent RRC (PRRC)** + +##### ***6.6.15.4.1 Test bitstream 12b444Iprrc\_A*** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in all intra configuration, testing of the PRRC functionality, ERRC is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with PRRC enabled. + +#### **6.6.15.5 Extended TSRC (ETSRC)** + +##### ***6.6.15.5.1 Test bitstream 12b444Ietsrc\_A*** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in all intra configuration and ETSRC enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.15.6 Reversed last significant coefficient position (RLSCP)** + +##### ***6.6.15.6.1 Test bitstream 12b444Irlscp\_A*** + +**Specification:** The bitstream is 12-bit 4:4:4, in all intra mode and RLSCP enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with RLSCP enabled. + +#### **6.6.15.7 Wavefront parallel process (WPP)** + +##### ***6.6.15.7.1 Test bitstream 12b444Iwpp\_A*** + +**Specification:** The bitstream is 12-bit 4:4:4, in all intra mode and sps\_entropy\_coding\_sync\_enabled\_flag equal to 1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode bitstreams with wavefront enabled. + +#### **6.6.16 Test bitstreams – Main 12 4:4:4 Still Picture profile** + +##### **6.6.16.1 VVCv1 tools set** + +###### ***6.6.16.1.1 Test bitstream 12b444SPvvc1\_A*** + +**Specification:** The bitstream contains a single picture in 12-bit 4:4:4 chroma format, VVCv1 tools set is enabled and VVCv2 tools are disabled. + +**Functional stage:** Still picture. + +**Purpose:** Check that the decoder can properly decode bitstreams conforming to the still picture profiles. + +##### **6.6.16.2 Extended precision processing (EPP)** + +###### ***6.6.16.2.1 Test bitstream 12b444SPepp\_A*** + +**Specification:** The bitstream contains a single picture in 12-bit 4:4:4 chroma format and EPP enabled. + +**Functional stage:** Transformation process and entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with EPP enabled. + +##### **6.6.16.3 Extended RRC (ERRC)** + +###### ***6.6.16.3.1 Test bitstream 12b444SPerrc\_A*** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, testing of the ERRC functionality, PRRC is enabled, Level 5.1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRC enabled. + +##### **6.6.16.4 Persistent RRC (PRRC)** + +###### ***6.6.16.4.1 Test bitstream 12b444SPprrc\_A*** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, testing of the PRRC functionality, ERRC is enabled, Level 5.1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with PRRC enabled. + +##### **6.6.16.5 Extended TSRC (ETSRC)** + +###### ***6.6.16.5.1 Test bitstream 12b444SPetsrc\_A*** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +###### ***6.6.16.5.2 Test bitstream 12b444SPetsrc\_B*** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.16.5.3 Test bitstream 12b444SPetsrc\_C** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 3. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.16.5.4 Test bitstream 12b444SPetsrc\_D** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 4. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.16.5.5 Test bitstream 12b444SPetsrc\_E** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, ETSRC is enabled and its Rice parameter is set to 5. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.16.5.6 Test bitstream 12b444SPetsrc\_F** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, ETSRC is enabled and its Rice parameter is set to 6. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.16.5.7 Test bitstream 12b444SPetsrc\_G** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, ETSRC is enabled and its Rice parameter is set to 7 + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.16.5.8 Test bitstream 12b444SPetsrc\_H** + +**Specification:** 12 bits video data with 4:4:4 chroma format is being coded in still image profile configuration, ETSRC is enabled and its Rice parameter is set to 8. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +### **6.6.16.6 Reversed last significant coefficient position (RLSCP)** + +#### **6.6.16.6.1 Test bitstream 12b444SPrlscp\_A** + +**Specification:** The bitstream contains a single picture in 12-bit 4:4:4 chroma format and RLSCP enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with RLSCP enabled. + +### **6.6.16.7 Wavefront parallel process (WPP)** + +#### **6.6.16.7.1 Test bitstream 12b444SPwpp\_A** + +**Specification:** The bitstream contains a single picture in 12-bit 4:4:4 chroma format and sps\_entropy\_coding\_sync\_enabled\_flag equal to 1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode bitstreams with wavefront enabled. + +#### 6.6.17 Test bitstreams – Main 16 4:4:4 profile + +##### 6.6.17.1 VVCv1 tools set + +###### 6.6.17.1.1 Test bitstream 16b444vvc1\_A + +**Specification:** The bitstream is 16-bit 4:4:4 video data being coded with various random access picture types, VVCv1 tools set is enabled and VVCv2 tools are disabled. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:4:4 content. + +##### 6.6.17.2 Extended precision processing (EPP) + +###### 6.6.17.2.1 Test bitstream 16b444epp\_A + +**Specification:** 16 bits video data with RGB format is being coded with random access picture types and EPP enabled. + +**Functional stage:** Transformation process and entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with EPP enabled. + +##### 6.6.17.3 Extended RRC (ERRC) + +###### 6.6.17.3.1 Test bitstream 16b444errc\_A + +**Specification:** 16 bits RGB video data with is being coded with random access picture types, testing of the ERRC functionality, PRRC is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRC enabled. + +###### 6.6.17.3.2 Test bitstream 16b444errc\_B + +**Specification:** 16 bits RGB video data with is being coded with random access picture types, testing of the ERRC functionality, PRRC is disabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRC enabled. + +###### 6.6.17.3.3 Test bitstream 16b444errc\_C + +**Specification:** 16 bits RGB video data with is being coded with random access picture types, testing of the ERRC functionality, PRRC is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRC enabled. + +##### 6.6.17.4 Persistent RRC (PRRC) + +###### 6.6.17.4.1 Test bitstream 16b444prrc\_A + +**Specification:** 16 bits RGB video data with is being coded with random access picture types, testing of the PRRC functionality, ERRC is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with PRRC enabled. + +##### 6.6.17.5 Extended TSRC (ETSRC) + +###### 6.6.17.5.1 Test bitstream 16b444etsrc\_A + +**Specification:** 16 bits RGB video data is being coded with various random access picture types and ETSRC enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.17.6 Reversed last significant coefficient position (RLSCP)** + +##### ***6.6.17.6.1 Test bitstream 16b444rlscp\_A*** + +**Specification:** 16 bits video data with 4:4:4 chroma format is being coded with various random access picture types and RLSCP enabled. + +**Functional stage:** Entropy coding + +**Purpose:** Check that the decoder can properly decode slices with RLSCP enabled. + +#### **6.6.17.7 Wavefront parallel process (WPP)** + +##### ***6.6.17.7.1 Test bitstream 16b444wpp\_A*** + +**Specification:** 16 bits video data with 4:4:4 chroma format is being coded with various random access picture types and sps\_entropy\_coding\_sync\_enabled\_flag equal to 1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode bitstreams with wavefront enabled. + +#### **6.6.17.8 Chroma format and bit depth** + +##### ***6.6.17.8.1 Test bitstream 10b444P16\_A*** + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, VVCv2 tools (EPP, ERRc, PRRc, ETSRC, RLSCP) are not used due to bit depth constraint. Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +##### ***6.6.17.8.2 Test bitstream 10b444P16\_B*** + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, VVCv2 tools (EPP, ERRc, PRRc, ETSRC, RLSCP) are not used due to bit depth constraint. Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +##### ***6.6.17.8.3 Test bitstream 10b444P16\_C*** + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, VVCv2 tools (EPP, ERRc, PRRc, ETSRC, RLSCP) are not used due to bit depth constraint. Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +##### ***6.6.17.8.4 Test bitstream 10b444P16\_D*** + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, VVCv2 tools (EPP, ERRc, PRRc, ETSRC, RLSCP) are not used due to bit depth constraint. Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +##### ***6.6.17.8.5 Test bitstream 10b444P16\_E*** + +**Specification:** A random access sequence of 10-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, VVCv2 tools (EPP, ERRc, PRRc, ETSRC, RLSCP) are not used due to bit depth constraint. Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 10-bit 4:4:4 content. + +**6.6.17.8.6 Test bitstream 12b400P16\_A** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.17.8.7 Test bitstream 12b400P16\_B** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.17.8.8 Test bitstream 12b400P16\_C** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.17.8.9 Test bitstream 12b400P16\_D** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.17.8.10 Test bitstream 12b400P16\_E** + +**Specification:** A random access sequence of 12-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +**6.6.17.8.11 Test bitstream 12b420P16\_A** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.17.8.12 Test bitstream 12b420P16\_B** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.17.8.13 Test bitstream 12b420P16\_C** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.17.8.14 Test bitstream 12b420P16\_D** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.17.8.15 Test bitstream 12b420P16\_E** + +**Specification:** A random access sequence of 12-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:0 content. + +**6.6.17.8.16 Test bitstream 12b422P16\_A** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.17.8.17 Test bitstream 12b422P16\_B** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.17.8.18 Test bitstream 12b422P16\_C** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.17.8.19 Test bitstream 12b422P16\_D** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.17.8.20 Test bitstream 12b422P16\_E** + +**Specification:** A random access sequence of 12-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:2:2 content. + +**6.6.17.8.21 Test bitstream 12b444P16\_A** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +**6.6.17.8.22 Test bitstream 12b444P16\_B** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +**6.6.17.8.23 Test bitstream 12b444P16\_C** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +#### ***6.6.17.8.24 Test bitstream 12b444P16\_D*** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:4:4 content. + +#### ***6.6.17.8.25 Test bitstream 12b444P16\_E*** + +**Specification:** A random access sequence of 12-bit 4:4:4 data encoded in the Main 16 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 12-bit 4:0:0 content. + +#### ***6.6.17.8.26 Test bitstream 16b400P16\_A*** + +**Specification:** A random access sequence of 16-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:0:0 content. + +#### ***6.6.17.8.27 Test bitstream 16b400P16\_B*** + +**Specification:** A random access sequence of 16-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:0:0 content. + +#### ***6.6.17.8.28 Test bitstream 16b400P16\_C*** + +**Specification:** A random access sequence of 16-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:0:0 content. + +#### ***6.6.17.8.29 Test bitstream 16b400P16\_D*** + +**Specification:** A random access sequence of 16-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:0:0 content. + +#### ***6.6.17.8.30 Test bitstream 16b400P16\_E*** + +**Specification:** A random access sequence of 16-bit 4:0:0 data encoded in the Main 16 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:0:0 content. + +#### ***6.6.17.8.31 Test bitstream 16b420P16\_A*** + +**Specification:** A random access sequence of 16-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:0 content. + +#### ***6.6.17.8.32 Test bitstream 16b420P16\_B*** + +**Specification:** A random access sequence of 16-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:0 content. + +#### ***6.6.17.8.33 Test bitstream 16b420P16\_C*** + +**Specification:** A random access sequence of 16-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:0 content. + +#### ***6.6.17.8.34 Test bitstream 16b420P16\_D*** + +**Specification:** A random access sequence of 16-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:0 content. + +#### ***6.6.17.8.35 Test bitstream 16b420P16\_E*** + +**Specification:** A random access sequence of 16-bit 4:2:0 data encoded in the Main 16 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:0 content. + +#### ***6.6.17.8.36 Test bitstream 16b422P16\_A*** + +**Specification:** A random access sequence of 16-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 2. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:2 content. + +#### ***6.6.17.8.37 Test bitstream 16b422P16\_B*** + +**Specification:** A random access sequence of 16-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 4.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:2 content. + +#### ***6.6.17.8.38 Test bitstream 16b422P16\_C*** + +**Specification:** A random access sequence of 16-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 5.1, Main Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:2 content. + +#### ***6.6.17.8.39 Test bitstream 16b422P16\_D*** + +**Specification:** A random access sequence of 16-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 4.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:2 content. + +#### ***6.6.17.8.40 Test bitstream 16b422P16\_E*** + +**Specification:** A random access sequence of 16-bit 4:2:2 data encoded in the Main 16 4:4:4 profile, Level 5.1, High Tier. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:2:2 content. + +### **6.6.18 Test bitstreams – Main 16 4:4:4 Intra profile** + +#### **6.6.18.1 VVCv1 tools set** + +##### ***6.6.18.1.1 Test bitstream 16b444Ivvc1\_A*** + +**Specification:** The bitstream is 16-bit 4:4:4, in all intra mode, VVCv1 tools set is enabled and VVCv2 tools are disabled. + +**Functional stage:** Entire decoder. + +**Purpose:** Check that the decoder can properly decode 16-bit 4:4:4 content. + +#### **6.6.18.2 Extended precision processing (EPP)** + +##### ***6.6.18.2.1 Test bitstream 16b444Iepp\_A*** + +**Specification:** The bitstream is 16-bit RGB, in all intra mode and EPP enabled. + +**Functional stage:** Transformation process and entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with EPP enabled. + +#### **6.6.18.3 Extended RRC (ERRC)** + +##### ***6.6.18.3.1 Test bitstream 16b444Ierrc\_A*** + +**Specification:** 16 bits RGB video data with is being coded with intra picture types, testing of the ERRC functionality, PRRC is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRC enabled. + +#### **6.6.18.4 Persistent RRC (PRRC)** + +##### ***6.6.18.4.1 Test bitstream 16b444Iprrc\_A*** + +**Specification:** 16 bits RGB video data with is being coded with intra picture types testing of the PRRC functionality, ERRC is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with PRRC enabled. + +#### **6.6.18.5 Extended TSRC (ETSRC)** + +##### ***6.6.18.5.1 Test bitstream 16b444Ietsrc\_A*** + +**Specification:** 16 bits RGB video data is being coded in all intra configuration and ETSRC enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.18.6 Reversed last significant coefficient position (RLSCP)** + +##### ***6.6.18.6.1 Test bitstream 16b444Irlscp\_A*** + +**Specification:** The bitstream is 16-bit 4:4:4, in all intra mode and RLSCP enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with RLSCP enabled. + +#### **6.6.18.7 Wavefront parallel process (WPP)** + +##### ***6.6.18.7.1 Test bitstream 16b444Iwpp\_A*** + +**Specification:** The bitstream is 16-bit 4:4:4, in all intra mode and sps\_entropy\_coding\_sync\_enabled\_flag equal to 1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode bitstreams with wavefront enabled. + +#### 6.6.19 Test bitstreams – Main 16 4:4:4 Still Picture profile + +##### 6.6.19.1 VVCv1 tools set + +###### 6.6.19.1.1 Test bitstream 16b444SPvvc1\_A + +**Specification:** The bitstream contains a single picture in 16-bit 4:4:4 chroma format, VVCv1 tools set is enabled and VVCv2 tools are disabled. + +**Functional stage:** Still picture. + +**Purpose:** Check that the decoder can properly decode bitstreams conforming to the still picture profiles. + +##### 6.6.19.2 Extended precision processing (EPP) + +###### 6.6.19.2.1 Test bitstream 16b444SPepp\_A + +**Specification:** The bitstream contains a single picture in 16-bit RGB format and EPP enabled. + +**Functional stage:** Transformation process and entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with EPP enabled. + +##### 6.6.19.3 Extended RRC (ERRC) + +###### 6.6.19.3.1 Test bitstream 16b444SPerrc\_A + +**Specification:** 16 bits RGB video data with is being coded with still picture profile configuration, testing of the ERRC functionality, PRRc is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ERRC enabled. + +##### 6.6.19.4 Persistent RRC (PRRC) + +###### 6.6.19.4.1 Test bitstream 16b444SPprrc\_A + +**Specification:** 16 bits RGB video data with is being coded with still picture profile configuration, testing of the PRRc functionality, ERRC is enabled, Level 6.2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with PRRc enabled. + +##### 6.6.19.5 Extended TSRC (ETSRC) + +###### 6.6.19.5.1 Test bitstream 16b444SPetsrc\_A + +**Specification:** 16 bits RGB video data is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +###### 6.6.19.5.2 Test bitstream 16b444SPetsrc\_B + +**Specification:** 16 bits RGB video data is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 2. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +###### 6.6.19.5.3 Test bitstream 16b444SPetsrc\_C + +**Specification:** 16 bits RGB video data is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 3. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.19.5.4 Test bitstream 16b444SPetsrc\_D** + +**Specification:** 16 bits RGB video data is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 4. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.19.5.5 Test bitstream 16b444SPetsrc\_E** + +**Specification:** 16 bits RGB video data is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 5. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.19.5.6 Test bitstream 16b444SPetsrc\_F** + +**Specification:** 16 bits RGB video data is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 6. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.19.5.7 Test bitstream 16b444SPetsrc\_G** + +**Specification:** 16 bits RGB video data is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 7. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +#### **6.6.19.5.8 Test bitstream 16b444SPetsrc\_H** + +**Specification:** 16 bits RGB video data is being coded in still image profile configuration, ETSRC is enabled, and its Rice parameter is set to 8. + +**Functional stage:** Entropy coding + +**Purpose:** Check that the decoder can properly decode slices with ETSRC enabled. + +### **6.6.19.6 Reversed last significant coefficient position (RLSCP)** + +#### **6.6.19.6.1 Test bitstream 16b444SPrlscp\_A** + +**Specification:** The bitstream contains a single picture in 16-bit 4:4:4 chroma format and RLSCP enabled. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode slices with RLSCP enabled. + +### **6.6.19.7 Wavefront parallel process (WPP)** + +#### **6.6.19.7.1 Test bitstream 16b444SPwpp\_A** + +**Specification:** The bitstream contains a single picture in 16-bit 4:4:4 chroma format and sps\_entropy\_coding\_sync\_enabled\_flag equal to 1. + +**Functional stage:** Entropy coding. + +**Purpose:** Check that the decoder can properly decode bitstreams with wavefront enabled. + +## 6.7 Conformance test suites for Rec. ITU-T H.266 | ISO/IEC 23090-3 + +### 6.7.1 Bitstreams for Main 10 profile + +**Table 1 – Coding tool bitstreams for Main 10 profile** + +| Categories | Tool description | Feature name | Bitstream features | +|----------------------------|--------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CTU partition | Chroma separate tree | CST | Test CST on and off | +| Transform and quantization | Dependent quantization | DQ | Dependent quantization enabled for all pictures (with and without enabling MTS and LFNST); picture/slice-level switching between dependent quantization, sign data hiding, and conventional quantization | +| Intra coding | Cross-component linear model | CCLM | Exercise CCLM with different CU sizes | +| Transform and quantization | Multiple transform set | MTS | Include MTS combinations of (intra, inter): (implicit, none), (explicit, none), (implicit, explicit), (explicit, explicit) | +| In-loop filter | Adaptive loop filter | ALF | ALF virtual boundary processing for line buffer reduction; exercise clipping values of non-linear ALF | +| Inter coding | Affine motion model | AFF | Include affine AMVP and affine merge; control flags | +| Inter coding | Subblock-based temporal merging candidates | SbTMVP | Test SbTMVP off and test SbTMVP on when affine is off | +| Inter coding | Adaptive motion vector resolution | AMVR | Include SIF | +| Inter coding | Bi-directional optical flow | BDOF | Test BDOF with different implicit on/off decision and subblock usages | +| Inter coding | Combined intra/inter prediction | CIIP | Test CIIP for different sizes and different combining weights | +| Inter coding | Merge with MVD | MMVD | | +| Inter coding | Bi-predictive with CU weights | BCW | Test BCW with different BCW weights | +| Intra coding | Multi-reference line prediction | MRLP | Test all MRL and MPM indices; CUs at the top border of a CTU do not use extended references lines and the MRL index is not present in the bitstream | +| SCC coding | Intra block copy mode | IBC | Test IBC feature with different options and and combination with CST and AMVR | +| Intra coding | Intra sub-partitioning | ISP | | +| Inter coding | Decoder motion vector refinement | DMVR | Exercise enabling conditions, MV wraparound and MV clip at picture boundary, exercise corner cases of SAD variations | +| Transform and quantization | Sub-block transform | SBT | Different block sizes | +| In-loop filter | Luma mapping with chroma scaling | LMCS | Exercise multiple APSs, slice level LMCS on/off | +| Entropy coding | Sign data hiding | SDH | | +| Inter coding | Symmetric motion vector difference | SMVD | Long-term reference handling, mvd_l1_zero_flag handling | +| Intra coding | Block-based delta pulse code modulation | BDPCM | | +| Intra coding | Matrix based intra prediction | MIP | | +| Transform and quantization | Low frequency non-separable transform | LFNST | Various block sizes /shapes | +| Transform and quantization | Transform tool set | MTS_LFNST | Tool on or off of MTS and LFNST together with implicit or explicit MTS | +| Transform and quantization | Joint coding of chroma residuals | JCCR | Exercise all modes of joint coding of chroma residuals (JCCR) | +| Inter coding | Temporal motion vector predictor | TMVP | | + +**Table 1 – Coding tool bitstreams for Main 10 profile** + +| Categories | Tool description | Feature name | Bitstream features | +|----------------------------|----------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Inter coding | Motion vector compression | MVCOMP | MV compression for temporal storage (including corner cases) | +| In-loop filter | Sampled adaptive offset | SAO | | +| Inter coding | Prediction refinement using optical flow | PROF | Various non-translational motion parameters for PROF | +| In-loop filter | Deblocking | DEBLOCKING | Exercise luma adaptive deblock filter and long tap filter | +| Inter coding | Weighted prediction | WP | Various combinations with other inter tools | +| Inter coding | Parallel merge | PMERGE | Exercise various parallel merge levels | +| Intra coding | Intra prediction | IP | Enable all modes, especially the wide-angle modes. | +| Intra coding | Luma intra prediction mode | MPM | Enable all conditions to generate MPM candidate | +| CTU partition | CTU, CU sizes | CTU | Exercise range of CTU, CU sizes | +| CTU partition | Trees and partitioning | TREE | Exercise range of sizes and depths of TREE, TT, QT | +| CTU partition | Trees and partitioning | QTBT | Exercise range of sizes and depths of QT, TT | +| CTU partition | Boundary partition | BOUNDARY | Boundary are sizes 8...120 samples, all combinations of QT and TREE | +| Transform and quantization | Transform | TRANS | Min and max transform sizes, min number of entropy coded coefficients, max number of coefficients | +| Transform and quantization | Quantization | QUANT | CU level delta QP, CU level chroma delta QP, transform-quantization bypass with DB | +| Transform and quantization | Scaling list | SCALING | Exercise multiple APSs, quantization matrices | +| Entropy coding | Entropy coding | ENTROPY | CABAC initialization: QP sweep to ensure proper initialization for every QP value; disabling signalling of cabac_init_idc | +| Entropy coding | Entropy coding | ENTMAINTIER | Max bins and bits, min bits for Main tier | +| Entropy coding | Entropy coding | ENTHIGHTIER | Max bins and bits for High tier | +| Inter coding | All merge modes | MERGE | Max number of merge candidates | +| Intra coding | Position dependent prediction combination (PDPC) | PDPC | Force clipping different PU sizes and shapes. | +| Entropy coding | Wavefronts | WPP | | +| Transform and quantization | Lossless and near-lossless, include transform skip | LOSSLESS | | +| Inter coding | Reference picture resizing | RPR | Multiple RPR scale factors, RPR cropping window and scaling window offsets | +| In-loop filter | CC-ALF | CCALF | Enable CC-ALF for all CTUs in the bitstream, slice-by-slice adaptation, CTU-by-CTU adaptation, dynamic range exercise (including clip) | +| Inter coding | Geometric partitioning mode | GPM | | + +**Table 2 – Coding tools sets for bitstreams for Main 10 profile** + +| Syntax element | CodingToolsSets | | | | | +|-------------------------------------|-----------------|------|---|------|---------| +| | A | B | C | D | E | +| slice_type | I | I, P | I | I, P | I, P, B | +| bit_depth_minus8 | 0 | 0 | 0 | 0 | 0 | +| separate_colour_plane_flag | 0 | 0 | 0 | 0 | 0 | +| ref_pic_resampling_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_log2_ctu_size_minus5 | 0 | 0 | 1 | 1 | 1 | +| subpics_present_flag | 0 | 0 | 0 | 0 | 1 | +| bit_depth_minus8 | 0 | 0 | 2 | 2 | 2 | +| sps_weighted_pred_flag | 0 | 0 | 0 | 0 | 1 | +| sps_weighted_bipred_flag | 0 | 0 | 0 | 0 | 1 | +| sps_max_luma_transform_size_64_flag | 0 | 0 | 0 | 0 | 1 | +| sps_sao_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_alf_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_transform_skip_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_bdpcm_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_temporal_mvp_enabled_flag | 0 | 0 | 0 | 1 | 1 | +| sps_sbtmvp_enabled_flag | 0 | 0 | 0 | 1 | 1 | +| sps_amvr_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_bdof_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_bdof_pic_present_flag | 0 | 0 | 0 | 0 | 1 | +| sps_smvd_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_dmvr_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_dmvr_pic_present_flag | 0 | 0 | 0 | 0 | 1 | +| sps_mmvd_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_isp_enabled_flag | 0 | 0 | 1 | 1 | 1 | +| sps_mrl_enabled_flag | 0 | 0 | 0 | 1 | 1 | +| sps_mip_enabled_flag | 0 | 0 | 0 | 1 | 1 | +| sps_mts_enabled_flag | 0 | 0 | 1 | 1 | 1 | +| sps_sbt_enabled_flag | 0 | 0 | 0 | 1 | 1 | +| sps_affine_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_bcw_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_ibc_enabled_flag | 0 | 0 | 0 | 1 | 1 | +| sps_ciip_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_fpel_mmvd_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_geo_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_lmcs_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_lfnst_enabled_flag | 0 | 0 | 0 | 1 | 1 | +| sps_ladf_enabled_flag | 0 | 0 | 0 | 0 | 1 | +| sps_scaling_list_enabled_flag | 0 | 0 | 0 | 0 | 1 | + +**Table 3 – High-level syntax features for bitstreams for Main 10 profile** + +| Feature | Feature name | Bitstream features | +|------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Access unit delimiter | AUD | AUD NAL units present | +| Filler data | FILLER | Filler data NAL units present | +| Decoding Capability Information | DCI | DPS present | +| Sequence parameter set | SPS | Multiple SPSs | +| Video usability information | PQ | PQ EOTF | +| Video usability information | HLG | HLG EOTF | +| Picture parameter set | PPS | Multiple PPSs | +| Mixed NUT | MNUT | Mixed NAL unit type within a picture | +| Extension of parameter set | PSEXT | Extension data in DPS, VPS, SPS, PPS, PH, SH | +| Hypothetical reference decoder | HRD | HRD signalling, including HSS, DU, repetition | +| Adaptation parameter set | APSALF | Multiple APSs of each type (ALF) | +| Adaptation parameter set | APSLMCS | Multiple APSs of each type (LMCS) | +| Adaptation parameter set | APSMULT | Multiple APSs of each type (scaling list) | +| Adaptation parameter set | SUFAPS | Suffix APS NAL units | +| Random access point | RAP | IRAP functionality | +| Picture output | POUT | Pic output flag, no output pic | +| Gradual decoder refresh | GDR | Use of GDR pictures | +| Picture order count | POC | POC derivation, POC reset, POC MSB present | +| Tiles | TILE | Pictures partitions in tiles with same and different tile size, slices in tiles, tiles in slices | +| Slices | SLICES | Raster-scan and rectangular slices | +| Subpictures | SUBPIC | Various number of sub-pictures, sub-pictures of varying sizes, multiple tiles in some sub-pictures, mix of independent and non-independent subpictures, use of subpicture ID in PPS and in PH | +| Picture header and slice header | PHSH | Signalling control of syntax elements in PH and SH, bitstream with both picture header in slice header as well as picture header in its own NALU, collocated picture for TMVP signalled in picture header | +| Temporal scalability | TEMPSCAL | Maximum number of temporal layers, varying number of temporal sub-layers | +| Inter-layer reference picture list | ILRPL | Inter-layer ref pic list | +| Reference picture lists | RPL | Reference list modification | +| Long term ref picture | LTRP | LTRP handling | +| Number of active ref pics | ACTPIC | Using default, using different number of active reference pictures in slices | +| Virtual boundaries | VIRTUAL | Loop filters on/off at non-tile/slice boundaries | + +**Table 3 – High-level syntax features for bitstreams for Main 10 profile** + +| Feature | Feature name | Bitstream features | +|-----------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reference wraparound | WRAP | Exercise various wraparound amounts | +| 360° video | CUBEMAP | Cubemap layout and SEI | +| 360° video | ERP | Equirectangular projection layout and SEI | +| Conformance cropping window | CROP | Use of conformance cropping parameters, varying parameters, large offsets, odd offset values for 4:4:4, cropping window signalling in both SPS and PPS | +| Bumping | BUMP | Bumping process | +| Decoded picture buffer | DPB | Sublayer DPB size signalling | +| Field pictures | FIELD | Frame-field information (SPS) | + +**Table 4 – Additional chroma formats and bit depths for Main 10 profile** + +| Tool description | Feature name | Bitstream features | +|------------------|--------------|---------------------------------| +| 8b 4:0:0 | 8b400 | 8-bit 4:0:0 in Main 10 profile | +| 8b 4:2:0 | 8b420 | 8-bit 4:2:0 in Main 10 profile | +| 10b 4:0:0 | 10b400 | 10-bit 4:0:0 in Main 10 profile | + +### 6.7.2 Bitstreams for Main 10 4:4:4 profile + +**Table 5 – Coding tools for Main 10 4:4:4 profile with 4:4:4 10 bit** + +| Categories | Tool description | Feature name | Bitstream features | +|-------------|-----------------------------------------------------|----------------|--------------------------------------------------------| +| Basic 4:4:4 | 10-bit 4:4:4 | 10b444 | No 4:4:4-specific coding tools enabled | +| SCC coding | Adaptive colour transform | ACT | | +| SCC coding | Palette mode | PALETTE | | +| Entropy | Entropy coding for Main 10 4:4:4 profile, Main tier | ENT444MAINTIER | Max bins and bits for Main 10 4:4:4 profile, Main tier | +| Entropy | Entropy coding for Main 10 4:4:4 profile, High tier | ENT444HIGHTIER | Max bins and bits for Main 10 4:4:4 profile, High tier | + +**Table 6 – Additional chroma formats and bit depths Main 10 4:4:4 profile** + +| Tool description | Feature name | Bitstream features | +|------------------|--------------|---------------------------------------| +| 8b 4:2:2 | 8b422 | 8-bit 4:2:2 in Main 10 4:4:4 profile | +| 8b 4:4:4 | 8b444 | 8-bit 4:4:4 in Main 10 4:4:4 profile | +| 10b 4:2:2 | 10b422 | 10-bit 4:2:2 in Main 10 4:4:4 profile | + +### 6.7.3 Bitstreams for Multilayer Main 10 profile + +**Table 7 – Bitstreams for Multilayer Main 10 profile** + +| Feature | Feature name | Bitstream features | +|--------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------| +| Video parameter set | VPS | Single and multiple VPSs | +| Spatial scalability | SPATSCAL | Different resolution layers, including unusual scaling ratios | +| Layered coding with OLS | OLS | Layered coding w/ and w/o inter-layer prediction, with 2 and 3 layers | +| Operating point information NAL unit | OPI | Use OPI NAL unit in bitstream to determine output | +| Layered coding with OLS | OLS | Two-layer coding where each OLS specifies a different profile | +| Layered coding with OLS | OLS | Two-layer coding where each layer is coded as independent layer and both OLSs specify the Main 10 profile | +| Layered coding with OLS | OLS | Three-layer coding where the lowest independent layer is referenced from two higher layers | +| Layered coding with scaling window | PPS | Two-layer coding where the enhancement layer is coded with a scaling window enabled | +| Layered coding with scaling window | PPS | Two-layer coding where the base layer is coded with a scaling window enabled | +| Layered coding with scaling window | PPS | Two-layer coding where the two layers are coded with different scaling windows | +| Layered coding with inter-layer and intra-layer dependencies | ILRPL | No intra pictures in the dependent layer, and multiple reference pictures with mixed inter-layer and intra layer dependencies | + +### 6.7.4 Bitstreams for Multilayer Main 10 4:4:4 profile + +**Table 8 – Bitstreams for Multilayer Main 10 4:4:4 profile** + +| Feature | Feature name | Bitstream features | +|---------------------|--------------|---------------------------------------------------------------| +| Spatial scalability | SPATSCAL444 | Different resolution layers, including unusual scaling ratios | + +### 6.7.5 Bitstreams for Main 10 Still Picture profile + +**Table 9 – Bitstreams for Main 10 Still Picture profile** + +| Feature | Feature name | Bitstream features | +|---------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Still picture | STILL | Single picture using Main 10 Still Picture profile and testing capability of decoding the first picture of a Main 10 profile bitstream | + +### 6.7.6 Bitstreams for Main 10 4:4:4 Still Picture profile + +**Table 10 – Bitstreams for Main 10 4:4:4 Still Picture profile** + +| Feature | Feature name | Bitstream features | +|---------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Still picture | STILL444 | Single picture using Main 10 4:4:4 Still Picture profile and testing capability of decoding the first picture of a Main 10 4:4:4 profile bitstream | + +### 6.7.7 Bitstreams for Main 12 profile + +Table 11 – Bitstreams for Main 12 profile + +| Profile | Category | Tool description | Feature name | Bitstream features | +|---------|------------|------------------|--------------|-------------------------------| +| Main 12 | VVC1 tools | VVC1 tools | 12b420vvc1 | 12-bit 4:2:0, VVCv1 tools set | + +### 6.7.8 Bitstreams for Main 12 Intra profile + +Table 12 – Bitstreams for Main 12 Intra profile + +| Profile | Category | Tool description | Feature name | Bitstream features | +|---------------|------------|------------------|--------------|-------------------------------| +| Main 12 Intra | VVC1 tools | VVC1 tools | 12b420lvvc1 | 12-bit 4:2:0, VVCv1 tools set | + +### 6.7.9 Bitstreams for Main 12 Still Picture profile + +Table 13 – Bitstreams for Main 12 Still Picture profile + +| Profile | Category | Tool description | Feature name | Bitstream features | +|-----------------------|------------|------------------|--------------|-------------------------------| +| Main 12 Still Picture | VVC1 tools | VVC1 tools | 12b420SPvvc1 | 12-bit 4:2:0, VVCv1 tools set | + +### 6.7.10 Bitstreams for Main 12 4:4:4 profile + +Table 14 – Bitstreams for Main 12 4:4:4 profile + +| Profile | Category | Tool description | Feature name | Bitstream features | +|---------------|-----------------------------|------------------|--------------|-------------------------------------| +| Main 12 4:4:4 | VVC1 tools | VVC1 tools | 12b444vvc1 | 12-bit 4:4:4, VVCv1 tools set | +| | ERRC | ERRC | 12b444errc | 12-bit 4:4:4, VVCv2 set, ERRC test | +| | PRRC | PRRC | 12b444prrc | 12-bit 4:4:4, VVCv2 set, PRRC test | +| | ETSRC | ETSRC | 12b444etsrc | 12-bit 4:4:4, VVCv2 set, ETSRC test | +| | EPP | EPP | 12b444epp | 12-bit 4:4:4, VVCv2 set, EPP test | +| | RLSCP | RLSCP | 12b444rlscp | 12-bit 4:4:4, VVCv2 set, RLSCP test | +| | WPP | WPP | 12b444wpp | 12-bit 4:4:4, VVCv2 set, WPP test | +| Main 12 4:4:4 | Chroma format and bit depth | 10b 4:4:4 | 10b444P12 | 10-bit 4:4:4, VVCv1 tools set, RA | +| | | 12b 4:0:0 | 12b400P12 | 12-bit 4:0:0, VVCv2 tools set, RA | +| | | 12b 4:2:0 | 12b420P12 | 12-bit 4:2:0, VVCv2 tools set, RA | +| | | 12b 4:2:2 | 12b422P12 | 12-bit 4:2:2, VVCv2 tools set, RA | + +### 6.7.11 Bitstreams for Main 12 4:4:4 Intra profile + +Table 15 – Bitstreams for Main 12 4:4:4 Intra profile + +| Profile | Category | Tool description | Feature name | Bitstream features | +|---------------------|------------|------------------|--------------|-------------------------------------| +| Main 12 4:4:4 Intra | VVC1 tools | VVC1 tools | 12b444lvvc1 | 12-bit 4:4:4, VVCv1 tools set | +| | ERRC | ERRC | 12b444lerrc | 12-bit 4:4:4, VVCv2 set, ERRC test | +| | PRRC | PRRC | 12b444lprrc | 12-bit 4:4:4, VVCv2 set, PRRC test | +| | ETSRC | ETSRC | 12b444letsrc | 12-bit 4:4:4, VVCv2 set, ETSRC test | +| | EPP | EPP | 12b444lepp | 12-bit 4:4:4, VVCv2 set, EPP test | +| | RLSCP | RLSCP | 12b444lrlscp | 12-bit 4:4:4, VVCv2 set, RLSCP test | +| | WPP | WPP | 12b444lwpp | 12-bit 4:4:4, VVCv2 set, WPP test | + +### 6.7.12 Bitstreams for Main 12 4:4:4 Still Picture profile + +Table 16 – Bitstreams for Main 12 4:4:4 Still Picture profile + +| Profile | Category | Tool description | Feature name | Bitstream features | +|-----------------------------|------------|------------------|---------------|-------------------------------------| +| Main 12 4:4:4 Still Picture | VVC1 tools | VVC1 tools | 12b444SPvvc1 | 12-bit 4:4:4, VVCv1 tools set | +| | ERRC | ERRC | 12b444SPerrc | 12-bit 4:4:4, VVCv2 set, ERRC test | +| | PRRC | PRRC | 12b444SPprrc | 12-bit 4:4:4, VVCv2 set, PRRC test | +| | ETSRC | ETSRC | 12b444SPetsrc | 12-bit 4:4:4, VVCv2 set, ETSRC test | +| | EPP | EPP | 12b444SPepp | 12-bit 4:4:4, VVCv2 set, EPP test | +| | RLSCP | RLSCP | 12b444SPrlscp | 12-bit 4:4:4, VVCv2 set, RLSCP test | +| | WPP | WPP | 12b444SPwpp | 12-bit 4:4:4, VVCv2 set, WPP test | + +### 6.7.13 Bitstreams for Main 16 4:4:4 profile + +Table 17 – Bitstreams for Main 16 4:4:4 profile + +| Profile | Category | Tool description | Feature name | Bitstream features | +|---------------|-----------------------------|------------------|--------------|-------------------------------------| +| Main 16 4:4:4 | VVC1 tools | VVC1 tools | 16b444vvc1 | 16-bit 4:4:4, VVCv1 tools set | +| | ERRC | ERRC | 16b444errc | 16-bit 4:4:4, VVCv2 set, ERRC test | +| | PRRC | PRRC | 16b444prrc | 16-bit 4:4:4, VVCv2 set, PRRC test | +| | ETSRC | ETSRC | 16b444etsrc | 16-bit 4:4:4, VVCv2 set, ETSRC test | +| | EPP | EPP | 16b444epp | 16-bit 4:4:4, VVCv2 set, EPP test | +| | RLSCP | RLSCP | 16b444rlscp | 16-bit 4:4:4, VVCv2 set, RLSCP test | +| | WPP | WPP | 16b444wpp | 16-bit 4:4:4, VVCv2 set, WPP test | +| | Chroma format and bit depth | 10b 4:4:4 | 10b444P16 | 10-bit 4:4:4, VVCv1 tools set, RA | +| | | 12b 4:0:0 | 12b400P16 | 12-bit 4:0:0, VVCv2 tools set, RA | +| | | 12b 4:2:0 | 12b420P16 | 12-bit 4:2:0, VVCv2 tools set, RA | +| | | 12b 4:2:2 | 12b422P16 | 12-bit 4:2:2, VVCv2 tools set, RA | +| | | 12b 4:4:4 | 12b444P16 | 12-bit 4:4:4, VVCv2 tools set, RA | +| | | 16b 4:0:0 | 16b400P16 | 16-bit 4:0:0, VVCv2 tools set, RA | +| | | 16b 4:2:0 | 16b420P16 | 16-bit 4:2:0, VVCv2 tools set, RA | +| | | 16b 4:2:2 | 16b422P16 | 16-bit 4:2:2, VVCv2 tools set, RA | + +### 6.7.14 Bitstreams for Main 16 4:4:4 Intra profile + +Table 18 – Bitstreams for Main 16 4:4:4 Intra profile + +| Profile | Category | Tool description | Feature name | Bitstream features | +|---------------------|------------|------------------|--------------|-------------------------------------| +| Main 16 4:4:4 Intra | VVC1 tools | VVC1 tools | 16b444lvvc1 | 16-bit 4:4:4, VVCv1 tools set | +| | ERRC | ERRC | 16b444lerrc | 16-bit 4:4:4, VVCv2 set, ERRC test | +| | PRRC | PRRC | 16b444lprrc | 16-bit 4:4:4, VVCv2 set, PRRC test | +| | ETSRC | ETSRC | 16b444letsrc | 16-bit 4:4:4, VVCv2 set, ETSRC test | +| | EPP | EPP | 16b444lepp | 16-bit 4:4:4, VVCv2 set, EPP test | +| | RLSCP | RLSCP | 16b444lrlscp | 16-bit 4:4:4, VVCv2 set, RLSCP test | +| | WPP | WPP | 16b444lwpp | 16-bit 4:4:4, VVCv2 set, WPP test | + +## 6.7.15 Bitstreams for Main 16 4:4:4 Still Picture profile + +**Table 19 – Bitstreams for Main 16 4:4:4 Still Picture profile** + +| Profile | Category | Tool description | Feature name | Bitstream features | +|-----------------------------|------------|------------------|---------------|-------------------------------------| +| Main 16 4:4:4 Still Picture | VVC1 tools | VVC1 tools | 16b444SPvvc1 | 16-bit 4:4:4, VVCv1 tools set | +| | ERRC | ERRC | 16b444SPerrc | 16-bit 4:4:4, VVCv2 set, ERRC test | +| | PRRC | PRRC | 16b444SPprrc | 16-bit 4:4:4, VVCv2 set, PRRC test | +| | ETSRC | ETSRC | 16b444SPetsrc | 16-bit 4:4:4, VVCv2 set, ETSRC test | +| | EPP | EPP | 16b444SPepp | 16-bit 4:4:4, VVCv2 set, EPP test | +| | RLSCP | RLSCP | 16b444SPrlscp | 16-bit 4:4:4, VVCv2 set, RLSCP test | +| | WPP | WPP | 16b444SPwpp | 16-bit 4:4:4, VVCv2 set, WPP test | + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.271-200605-I_PDF-E/raw.md b/marked/H/T-REC-H.271-200605-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..eec5f43011fa541476dd387eddb6ccaba0643c99 --- /dev/null +++ b/marked/H/T-REC-H.271-200605-I_PDF-E/raw.md @@ -0,0 +1,701 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.271** + +(05/2006) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Coding of moving +video + +--- + +**Video back-channel messages for conveyance +of status information and requests from a video +receiver to a video sender** + +ITU-T Recommendation H.271 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation H.271** + +# **Video back-channel messages for conveyance of status information and requests from a video receiver to a video sender** + +## **Summary** + +This Recommendation specifies the format of back-channel messages for conveyance of status information and requests from a video receiver to a video sender. + +The message syntax has been designed in a generic way to make it applicable for use with the majority of the existing international video coding standards. The application of the generic messages to ITU-T Recs H.261, H.263, and H.264 | ISO/IEC 14496-10 is specified. + +### **Source** + +ITU-T Recommendation H.271 was approved on 29 May 2006 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +### **Keywords** + +Back-channel message, receiver feedback, reference picture selection, video. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2006 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|-----|---------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | Normative references..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations..... | 2 | +| 5 | Conventions ..... | 2 | +| 5.1 | Arithmetic operators..... | 2 | +| 5.2 | Logical operators ..... | 3 | +| 5.3 | Relational operators..... | 3 | +| 5.4 | Bit-wise operators..... | 3 | +| 5.5 | Assignment operators ..... | 3 | +| 5.6 | Variables, syntax elements, and tables ..... | 4 | +| 5.7 | Text description of logical operations ..... | 4 | +| 5.8 | Method of describing syntax in tabular form ..... | 5 | +| 5.9 | Specification of syntax functions, categories, and descriptors..... | 7 | +| 6 | Message payloads ..... | 8 | +| 6.1 | Syntax ..... | 8 | +| 6.2 | Semantics..... | 9 | +| 7 | Standard specific uses of the messages ..... | 11 | +| 7.1 | H.261 specific use of the messages ..... | 11 | +| 7.2 | H.263 specific use of the messages ..... | 12 | +| 7.3 | H.264 specific use of the messages ..... | 13 | + +# Introduction + +## 0.1 Purpose + +For some applications, the transmission of additional data (in-band or out-of-band) is useful for improving video quality of service. This Recommendation specifies data payloads for use with a variety of video coding technologies. The data payloads are specified in a generic way to make them applicable to prevalent existing video coding standards. The application of the generic messages to ITU-T Recs H.261, H.263, and H.264 is specified. + +## 0.2 Overview + +The following information can be signalled from a video receiver to a video sender using the back-channel message(s) defined in this Recommendation: + +- Status reports: + - One or more pictures that are without detected bitstream error mismatch; + - Picture-level and/or macroblock-level losses; + - Information of important header information. +- Update requests: + - A "reset" request indicating that the sender should completely refresh the video bitstream as if no prior bitstream data had been received. + +The application of the back-channel messages to ITU-T Recs H.261, H.263, and H.264 is specified. + +# ITU-T Recommendation H.271 + +## Video back-channel messages for conveyance of status information and requests from a video receiver to a video sender + +# 1 Scope + +This Recommendation specifies back-channel messages for block-based video coding. + +# 2 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.261 (1993), *Video codec for audiovisual services at $p \times 64$ kbit/s*. +- ITU-T Recommendation H.263 (2005), *Video coding for low bit rate communication*. +- ITU-T Recommendation H.264 (2005), *Advanced video coding for generic audiovisual services*. + +ISO/IEC 14496-10:2005, *Information technology – Coding of audio-visual objects – Part 10: Advanced Video Coding*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 back channel:** A means to convey back-channel messages from a receiver of a video bitstream to a sender of a video bitstream. + +**3.2 back-channel message:** A message that is generated by a receiver of a video *bitstream* that conveys receiver status information or requests. + +**3.3 bitstream:** A sequence of bits that forms the representation of coded *pictures* and associated data forming one or more coded video sequences. + +**3.4 bitstream error:** A corrupted or incomplete *bitstream*. + +**3.5 bitstream error mismatch:** A difference between the values or quantity of decoded *pictures* caused by one or more *bitstream errors* versus the values or quantity of decoded *pictures* generated by the decoding process with a *bitstream* without *bitstream errors*. + +**3.6 block:** An $M \times N$ (M-column by N-row) array of luma samples and the associated chroma samples. + +**3.7 detected bitstream error:** A *bitstream error* that is detected by the receiver. + +**3.8 detected bitstream error mismatch:** A *bitstream error mismatch* that may be present because of *bitstream errors*. + +**3.9 decoding order:** The order in which *syntax elements* are processed by the decoding process specified by a video coding technology. + +**3.10 macroblock:** A 16x16 *block* of luma samples and two corresponding blocks of chroma samples. + +**3.11 parameter set:** A syntax structure that contains a number of *syntax elements* that may be used in the decoding process for one or more *pictures*. + +**3.12 picture:** A collective term for a field or a frame of video that is coded as a distinct unit by a video coding technology. + +**3.13 reference picture:** A *picture* that contains samples that may be used for inter-picture prediction in the decoding process of subsequent *pictures* in the video bitstream. + +**3.14 reserved:** The term reserved, when used in the clauses specifying some values of a particular syntax element, are for future use by ITU-T. These values shall not be used in back-channel messages conforming to this Recommendation, but may be used in future extensions of this Recommendation by ITU-T. + +**3.15 syntax element:** An element of data represented in the *bitstream* or in a back-channel message. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +CRC Cyclic Redundancy Code + +LSB Least Significant Bit + +MSB Most Significant Bit + +# 5 Conventions + +Throughout this Recommendation, statements appearing with the preamble "NOTE –" are informative and are not an integral part of this Recommendation. + +NOTE – The mathematical operators used in this Recommendation are similar to those used in the C programming language. Numbering and counting conventions generally begin from 0. + +## 5.1 Arithmetic operators + +The following arithmetic operators are defined as follows. + +- + Addition +- Subtraction (as a two-argument operator) or negation (as a unary prefix operator) +- \* Multiplication +- / Integer division with truncation of the result toward zero. For example, 7/4 and (–7) / (–4) are truncated to 1 and (–7) / 4 and 7 / (–4) are truncated to –1. +- x % y Modulus. Remainder of x divided by y, defined only for integers x and y with $x \geq 0$ and $y > 0$ . + +When order of precedence is not indicated explicitly by use of parenthesis, the following rules apply: + +- multiplication and division operations are considered to take place before addition and subtraction; +- multiplication and division operations in sequence are evaluated sequentially from left to right; +- addition and subtraction operations in sequence are evaluated sequentially from left to right. + +## 5.2 Logical operators + +The following logical operators are defined as follows: + +`x && y` Boolean logical "and" of x and y + +`x || y` Boolean logical "or" of x and y + +`!` Boolean logical "not" + +`x ? y : z` If x is TRUE or not equal to 0, evaluates to the value of y; otherwise, evaluates to the value of z + +## 5.3 Relational operators + +The following relational operators are defined as follows: + +`>` Greater than + +`>=` Greater than or equal to + +`<` Less than + +`<=` Less than or equal to + +`==` Equal to + +`!=` Not equal to + +## 5.4 Bit-wise operators + +The following bit-wise operators are defined as follows: + +`&` Bit-wise "and". When operating on integer arguments, operates on a two's complement representation of the integer value. When operating on a binary argument that contains fewer bits than another argument, the shorter argument is extended by adding more significant bits equal to 0. + +`|` Bit-wise "or". When operating on integer arguments, operates on a two's complement representation of the integer value. When operating on a binary argument that contains fewer bits than another argument, the shorter argument is extended by adding more significant bits equal to 0. + +`^` Bit-wise "exclusive or". When operating on integer arguments, operates on a two's complement representation of the integer value. When operating on a binary argument that contains fewer bits than another argument, the shorter argument is extended by adding more significant bits equal to 0. + +`x >> y` Arithmetic right shift of a two's complement integer representation of x by y binary digits. This function is defined only for positive integer values of y. Bits shifted into the MSBs as a result of the right shift have a value equal to the MSB of x prior to the shift operation. + +`x << y` Arithmetic left shift of a two's complement integer representation of x by y binary digits. This function is defined only for positive integer values of y. Bits shifted into the LSBs as a result of the left shift have a value equal to 0. + +## 5.5 Assignment operators + +The following arithmetic operators are defined as follows: + +`=` Assignment operator. + +`++` Increment, i.e., `x++` is equivalent to `x = x + 1`, when used in an array index, evaluates to the value of the variable prior to the increment operation. + +`--` Decrement, i.e., `x--` is equivalent to `x = x - 1`; when used in an array index, evaluates to the value of the variable prior to the decrement operation. + +- += Increment by amount specified, i.e., $x += 3$ is equivalent to $x = x + 3$ , and $x += (-3)$ is equivalent to $x = x + (-3)$ . +- Decrement by amount specified, i.e., $x -= 3$ is equivalent to $x = x - 3$ , and $x -= (-3)$ is equivalent to $x = x - (-3)$ . + +## 5.6 Variables, syntax elements, and tables + +Syntax elements in the bitstream are represented in **bold** type. Each syntax element is described by its name (all lower case letters with underscore characters), its one or two syntax categories, and one or two descriptors for its method of coded representation. The decoding process behaves according to the value of the syntax element and to the values of previously decoded syntax elements. When a value of a syntax element is used in the syntax tables or the text, it appears in regular (i.e., not bold) type. + +In some cases, the syntax tables may use the values of other variables derived from syntax elements values. Such variables appear in the syntax tables, or text, named by a mixture of lower case and upper case letters and without any underscore characters. Variables starting with an upper case letter are derived for the decoding of the current syntax structure and all depending syntax structures. Variables starting with an upper case letter may be used in the decoding process for later syntax structures mentioning the originating syntax structure of the variable. Variables starting with a lower case letter are only used within the subclause in which they are derived. + +In some cases, "mnemonic" names for syntax element values or variable values are used interchangeably with their numerical values. Sometimes "mnemonic" names are used without any associated numerical values. The association of values and names is specified in the text. The names are constructed from one or more groups of letters separated by an underscore character. Each group starts with an upper case letter and may contain more upper case letters. + +NOTE – The syntax is described in a manner that closely follows the C-language syntactic constructs. + +Functions are described by their names, which are constructed as syntax element names, with left and right round parentheses including zero or more variable names (for definition) or values (for usage), separated by commas (if more than one variable). + +Binary notation is indicated by enclosing the string of bit values by single quote marks. For example, '01000001' represents an eight-bit string having only its second and its last bits equal to 1. + +Hexadecimal notation, indicated by prefixing the hexadecimal number by "0x", may be used instead of binary notation when the number of bits is an integer multiple of 4. For example, 0x41 represents an eight-bit string having only its second and its last bits equal to 1. + +Numerical values not enclosed in single quotes and not prefixed by "0x" are decimal values. + +A value equal to 0 represents a FALSE condition in a test statement. The value TRUE is represented by any other value different than zero. + +## 5.7 Text description of logical operations + +In the text, a statement of logical operations as would be described in pseudo-code as + +``` + +if( condition 0 ) + statement 0 +else if ( condition 1 ) + statement 1 +... +else /* informative remark on remaining condition */ + statement n + +``` + +may be described in the following manner: + +... as follows / ... the following applies. + +- If condition 0, statement 0 +- Otherwise, if condition 1, statement 1 +- ... +- Otherwise (informative remark on remaining condition), statement n + +Each "If...Otherwise, if...Otherwise, ..." statement in the text is introduced with "... as follows" or "... the following applies" immediately followed by "If ... ". The last condition of the "If...Otherwise, if...Otherwise, ..." is always an "Otherwise, ...". Interleaved "If...Otherwise, if...Otherwise, ..." statements can be identified by matching "... as follows" or "... the following applies" with the ending "Otherwise, ...". + +In the text, a statement of logical operations as would be described in pseudo-code as + +``` +if( condition 0a && condition 0b ) + statement 0 +else if ( condition 1a || condition 1b ) + statement 1 +... +else + statement n +``` + +may be described in the following manner: + +... as follows / ... the following applies. + +- If all of the following conditions are true, statement 0 + - condition 0a + - condition 0b +- Otherwise, if any of the following conditions are true, statement 1 + - condition 1a + - condition 1b +- ... +- Otherwise, statement n + +In the text, a statement of logical operations as would be described in pseudo-code as + +``` +if( condition 0 ) + statement 0 +if ( condition 1 ) + statement 1 +``` + +may be described in the following manner: + +When condition 0, statement 0 + +When condition 1, statement 1 + +## 5.8 Method of describing syntax in tabular form + +The following table lists examples of pseudo code used to describe the syntax. When **syntax\_element** appears, it specifies that a syntax element is parsed from the bitstream and the bitstream pointer is advanced to the next position beyond the syntax element in the bitstream parsing process. + +| | Descriptor | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| /* A statement can be a syntax element with an associated syntax category and descriptor or can be an expression used to specify conditions for the existence, type, and quantity of syntax elements, as in the following two examples */ | | +| syntax_element | ue(v) | +| conditioning statement or structure { | | +| /* A group of statements enclosed in curly brackets is a compound statement and is treated functionally as a single statement. */ | | +| statement | | +| statement | | +| ... | | +| } | | +| /* A "while" structure is a conditioning statement that specifies a test of whether a condition is true, and if true, specifies evaluation of a statement (or compound statement) repeatedly until the condition is no longer true */ | | +| while( condition ) | | +| statement | | +| /* A "do ... while" structure is a conditioning structure that specifies evaluation of a statement once, followed by a test of whether a condition is true, and if true, specifies repeated evaluation of the statement until the condition is no longer true */ | | +| do | | +| statement | | +| while( condition ) | | +| /* An "if ... else" structure specifies a test of whether a condition is true, and if the condition is true, specifies evaluation of a primary statement, otherwise, specifies evaluation of an alternative statement. The "else" part of the structure and the associated alternative statement is omitted if no alternative statement evaluation is needed */ | | +| if( condition ) | | +| primary statement | | +| else | | +| alternative statement | | +| /* A "for" structure specifies evaluation of an initial statement, followed by a test of a condition, and if the condition is true, specifies repeated evaluation of a primary statement followed by a subsequent statement until the condition is no longer true. */ | | +| for( initial statement; condition; subsequent statement ) | | +| primary statement | | + +## 5.9 Specification of syntax functions, categories, and descriptors + +The functions presented here are used in the syntactical description. These functions assume the existence of a bitstream pointer with an indication of the position of the next bit to be read by the decoding process from the bitstream. + +`byte_aligned()` is specified as follows. + +- If the current position in the bitstream is on a byte boundary, i.e., the next bit in the bitstream is the first bit in a byte, the return value of `byte_aligned()` is equal to TRUE. +- Otherwise, the return value of `byte_aligned()` is equal to FALSE. + +`more_msg_data()` is specified as follows. + +- If there is more data in the syntax structure `msg_data()`, the return value of `more_msg_data()` is equal to TRUE. +- Otherwise, the return value of `more_msg_data()` is equal to FALSE. + +The method for enabling determination of whether there is more data in the syntax structure `msg_data()` is specified by the application. + +`next_bits( n )` provides the next bits in the bitstream for comparison purposes, without advancing the bitstream pointer. Provides a look at the next $n$ bits in the bitstream with $n$ being its argument. + +`read_bits( n )` reads the next $n$ bits from the bitstream and advances the bitstream pointer by $n$ bit positions. When $n$ is equal to 0, `read_bits( n )` is specified to return a value equal to 0 and to not advance the bitstream pointer. + +The following descriptors specify the parsing process of each syntax element. + +- `f(n)`: fixed-pattern bit string using $n$ bits written (from left to right) with the left bit first. The parsing process for this descriptor is specified by the return value of the function `read_bits( n )`. +- `u(n)`: unsigned integer using $n$ bits. When $n$ is "v" in the syntax table, the number of bits varies in a manner dependent on the value of other syntax elements. The parsing process for this descriptor is specified by the return value of the function `read_bits( n )` interpreted as a binary representation of an unsigned integer with most significant bit written first. +- `ue(v)`: unsigned integer Exp-Golomb-coded syntax element with the left bit first. The parsing process for this descriptor is specified in the following. + +Syntax elements coded as `ue(v)` are Exp-Golomb-coded. The parsing process for these syntax elements begins with reading the bits starting at the current location in the bitstream up to and including the first non-zero bit, and counting the number of leading bits that are equal to 0. This process shall be equivalent to the following: + +``` +leadingZeroBits = -1; +for( b = 0; !b; leadingZeroBits++ ) + b = read_bits( 1 ) +``` + +The variable `codeNum` is then assigned as follows: + +$$\text{codeNum} = 2^{\text{leadingZeroBits}} - 1 + \text{read\_bits}(\text{leadingZeroBits})$$ + +where the value returned from `read_bits( leadingZeroBits )` is interpreted as a binary representation of an unsigned integer with most significant bit written first. + +The value of the syntax element is equal to `codeNum`. + +# 6 Message payloads + +## 6.1 Syntax + +| | | +|---------------------------|-------------------| +| msg_data( ) { | Descriptor | +| do | | +| message( ) | | +| while( more_msg_data( ) ) | | +| } | | + +| | | +|-----------------------------------------|-------------------| +| message( ) { | Descriptor | +| payloadType = 0 | | +| while( next_bits( 8 ) == 0xFF ) { | | +| ff_byte /* equal to 0xFF */ | f(8) | +| payloadType += 255 | | +| } | | +| last_payload_type_byte | u(8) | +| payloadType += last_payload_type_byte | | +| payloadSize = 0 | | +| while( next_bits( 8 ) == 0xFF ) { | | +| ff_byte /* equal to 0xFF */ | f(8) | +| payloadSize += 255 | | +| } | | +| last_payload_size_byte | u(8) | +| payloadSize += last_payload_size_byte | | +| msg_payload( payloadType, payloadSize ) | | +| } | | + +| | | +|---------------------------------------------|-------------------| +| msg_payload( payloadType, payloadSize ) { | Descriptor | +| if( payloadType <= 4 ) | | +| ref_pic_id | u(32) | +| if( payloadType == 0 ) { | | +| num_ref_pics_minus1 | ue(v) | +| for( i = 1; i <= num_ref_pics_minus1; i++ ) | | +| good_ref_pic_id[ i ] | u(32) | +| } else if( payloadType == 1 ) | | +| delta_ref_pic_id | ue(v) | +| else if( payloadType == 2 ) { | | +| data_partition_idc | ue(v) | +| run_length_flag | u(1) | +| if( run_length_flag ) { | | +| first_blk_lost | ue(v) | + +| | | +|-------------------------------------------------------------|-------| +| num_blks_lost_minus1 | ue(v) | +| } else { | | +| top_left_blk | ue(v) | +| bottom_right_blk | ue(v) | +| } | | +| } else if( ( payloadType == 3 ) ( payloadType == 4 ) ) { | | +| param_set_type | ue(v) | +| param_set_crc | u(16) | +| if( payloadType == 3 ) | | +| param_set_id | ue(v) | +| } | | +| stop_one_bit /* equal to 1 */ | f(1) | +| while( !byte_aligned() ) | | +| alignment_zero_bit /* equal to 0 */ | f(1) | +| } | | + +## 6.2 Semantics + +**ff\_byte** shall be equal to 0xFF. + +**last\_payload\_type\_byte** is the last byte used to specify the payload type of a message. + +**last\_payload\_size\_byte** is the last byte used to specify the size of a message. + +The size of the syntax structure **msg\_payload()** shall be equal to **payloadSize** \* 8 bits. + +Corresponding to the values of **payloadType**, the message types are as shown in Table 6-1. + +**Table 6-1/H.271 – Message types** + +| payloadType | Message | +|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | One or more pictures without detected bitstream error mismatch | +| 1 | One or more pictures that are entirely or partially lost | +| 2 | A set of blocks of one picture that is entirely or partially lost | +| 3 | CRC for one parameter set | +| 4 | CRC for all parameter sets of a certain type | +| 5 | A "reset" request indicating that the sender should completely refresh the video bitstream as if no prior bitstream data had been received | +| > 5 | Reserved for future use by ITU-T | + +Messages having **payloadType** greater than 5 shall be removed and discarded according to the size of the message as indicated by **payloadSize**. + +**ref\_pic\_id** identifies a picture. Depending on the value of **payloadType**, the semantics of **ref\_pic\_id** are as specified in Table 6-2. + +**Table 6-2/H.271 – Semantics of ref\_pic\_id** + +| payloadType | Semantics of ref_pic_id | +|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Specifies a picture without detected bitstream error mismatch. | +| 1 | Specifies a picture that has been entirely or partially lost. | +| 2 | Specifies a picture that has been partially lost. | +| 3 | Specifies a picture. A CRC is present for one parameter set associated with the specified picture. | +| 4 | Specifies a picture. One CRC is present for all parameter sets of a certain type that are stored at the time associated with the decoding of the specified picture. | + +**num\_ref\_pics\_minus1** plus 1 specifies the number of the pictures that are without detected bitstream error mismatch. The value of num\_ref\_pics\_minus1 shall be in the range of 0 to 31, inclusive. + +**good\_ref\_pic\_id[ i ]** specifies the ith picture indicated in the current message that is without detected bitstream error mismatch. + +**delta\_ref\_pic\_id** specifies an increment relative to ref\_pic\_id identifying a set of pictures that are entirely or partially lost. The value of delta\_ref\_pic\_id shall be in the range of 0 to 31, inclusive. + +**data\_partition\_idc** indicates that all data (when data\_partition\_idc is equal to 0) or a partition of the data (when data\_partition\_idc is not equal to 0) for the blocks specified by top\_left\_blk and bottom\_right\_blk is lost. The value of data\_partition\_idc shall be in the range of 0 to 15, inclusive. + +**run\_length\_flag** equal to 1 indicates the presence of the syntax elements first\_blk\_lost and num\_blks\_lost\_minus1. run\_length\_flag equal to 0 indicates the presence of the syntax elements top\_left\_blk and bottom\_right\_blk. + +**first\_blk\_lost** indicates the block address of the first block in raster scan order. A block address is the index of a block in a block raster scan of the picture starting with zero for the top-left block in a picture. + +**num\_blks\_lost\_minus1** plus 1 specifies the number of consecutive blocks in raster scan order with the first block being identified by first\_blk\_lost. + +**top\_left\_blk** and **bottom\_right\_blk** specify the block addresses of the top-left and bottom-right blocks, respectively, of the rectangular region that is entirely or partially lost. The following constraints shall be obeyed by the values of the syntax elements top\_left\_blk and bottom\_right\_blk, where the variable PicWidthInBlks is the picture width in units of blocks. + +- top\_left\_blk shall be less than or equal to bottom\_right\_blk. +- bottom\_right\_blk shall be less than the picture size in units of blocks. +- top\_left\_blk % PicWidthInBlks shall be less than or equal to bottom\_right\_blk % PicWidthInBlks. + +**param\_set\_type** specifies the type of the parameter set(s). The value of param\_set\_type shall be in the range of 0 to 15, inclusive. + +**param\_set\_crc** is the CRC for the parameter set identified by param\_set\_id and param\_set\_type when payloadType is equal to 3 and is the CRC for all the parameter sets of the type specified by param\_set\_type together when payloadType is equal to 4. + +The value of param\_set\_crc shall be equal to the value of crcVal obtained by performing the following pseudo-code process. + +``` + +paramSet[pLen] = 0 +paramSet[pLen + 1] = 0 +crcVal = 0xFFFF +for( bitIdx = 0; bitIdx < ( pLen + 2 ) * 8; bitIdx++ ) { + crcMsb = ( crcVal >> 15 ) & 1 + bitVal = ( paramSet[bitIdx >> 3] >> ( 7 - ( bitIdx & 7 ) ) ) & 1 + crcVal = ( ( ( crcVal << 1 ) + bitVal ) & 0xFFFF ) ^ ( crcMsb * 0x1021 ) +} + +``` + +(6-1) + +where the variable paramSet is a string of bytes containing, at the beginning of the string of bytes, the data for which the CRC is computed; the variable pLen is the number of bytes of the data for which the CRC is computed; and the string of bytes of the variable paramSet is of sufficient length for two additional zero-valued bytes to be appended to the end of the data for which the CRC is computed. + +When payloadType is equal to 3, paramSet contains, in network byte order, the bytes of the received parameter set identified by param\_set\_id and param\_set\_type. + +When payloadType is equal to 4, paramSet contains a concatenation, in network byte order, of the bytes of all parameter sets of the type identified by param\_set\_type, in increasing order of the parameter set identifier. For any parameter set that has never been received, the representation of the parameter set shall be considered to be two bytes long, with the first byte containing the eight MSBs and the second byte containing the eight LSBs of an unsigned 16-bit binary representation of the value of the parameter set identifier. + +**param\_set\_id** specifies the parameter set identifier of the parameter set of the type specified by param\_set\_type for which a CRC is present. The value of param\_set\_id shall be in the range of 0 to 65535, inclusive. + +**stop\_one\_bit** shall be equal to 1. + +**alignment\_zero\_bit** shall be equal to 0. + +# 7 Standard specific uses of the messages + +In this clause, bit n of a variable refers to the nth least significant bit of the binary representation of the variable. The LSB is counted as bit 0. + +## 7.1 H.261 specific use of the messages + +The value of payloadType shall be equal to 0, 1, 2, or 5. Messages with other values of payloadType shall be ignored. + +When ref\_pic\_id or good\_ref\_pic\_id[ i ] are present, the 5 LSBs of these syntax elements indicate the value of TR, which is equal to ref\_pic\_id & 0x1F or good\_ref\_pic\_id[ i ] & 0x1F, of a picture. The remaining bits of ref\_pic\_id or good\_ref\_pic\_id[ i ] are reserved for future use by ITU-T, shall be equal to 0, and shall be ignored. + +Depending on the value of `payloadType`, the following applies. + +- If `payloadType` is equal to 0, the picture having TR equal to `ref_pic_id & 0x1F` or `good_ref_pic_id[ i ] & 0x1F` is without detected bitstream error mismatch. +- Otherwise, if `payloadType` is equal to 1, all pictures, in decoding order, starting with a picture having TR equal to `ref_pic_id & 0x1F`, up to and including a picture having TR equal to $((\text{ref\_pic\_id} \& 0x1F) + \text{delta\_ref\_pic\_id}) \% 32$ , when such pictures were present in the video bitstream, are indicated to have been entirely or partially lost. +- Otherwise, if `payloadType` is equal to 2, the picture having TR equal to `ref_pic_id & 0x1F` has been partially lost. Each block is a macroblock. The value of `data_partition_idc` shall be equal to 0, which indicates that all data of the identified macroblocks is considered lost. All other values of `data_partition_idc` are reserved for future use by ITU-T and shall be ignored. +- Otherwise (`payloadType` is equal to 5), no further specification. + +## 7.2 H.263 specific use of the messages + +The H.263 features that are supported by the present syntax include the following: + +- Long term pictures; +- Data partitioning. + +The following H.263 features are not supported by the present syntax: + +- Interlaced fields. + +The value of `payloadType` shall be equal to 0, 1, 2, or 5. Messages with other values of `payloadType` shall be ignored. + +When `ref_pic_id` or `good_ref_pic_id[ i ]` is present, the 12 LSBs indicate the value of the variable `picIdentifier`, which is equal to `ref_pic_id & 0x0FFF` or `good_ref_pic_id[ i ] & 0x0FFF`. When Annex U/H.263 is in use and `payloadType` is equal to 0, bit 12 indicates whether the stored picture is a long-term picture (when the bit is equal to 1) or a short-term picture (when the bit is equal to 0). Bit 13 shall be equal to 0 unless the optional Temporal, SNR and Spatial Scalability mode (Annex O/H.263) is used. When bit 13 is equal to 1, the message refers to an enhancement layer (rather than the base layer), and bits 14 to 17, inclusive, contain the value of `ELNUM`, which is equal to `ref_pic_id & 0x03C000` or `good_ref_pic_id[ i ] & 0x03C000`. The remaining bits of `ref_pic_id` or `good_ref_pic_id[ i ]` are reserved for future use by ITU-T, shall be equal to 0, and shall be ignored. + +- If Annex U/H.263 is not in use, `picIdentifier` indicates the value of TR of a picture. The value of TR shall be less than `MaxTR` that is equal to the maximum possible value of TR plus 1. Depending on the value of `payloadType`, the following applies. + - If `payloadType` is equal to 0, bit 12 of `ref_pic_id` or `good_ref_pic_id[ i ]` shall be equal to 0. The picture having TR equal to `picIdentifier`, and, when bit 13 of `ref_pic_id` or `good_ref_pic_id[ i ]` is equal to 1, having `ELNUM` equal to `ref_pic_id & 0x03C000` or `good_ref_pic_id[ i ] & 0x03C000`, is without detected bitstream error mismatch. + - Otherwise, if `payloadType` is equal to 1, bit 12 of `ref_pic_id` shall be equal to 0. All pictures, in decoding order and in the base layer or the same enhancement layer with `ELNUM` equal to `ref_pic_id & 0x03C000`, starting with a picture having TR equal to `ref_pic_id & 0x0FFF`, up to and including a picture having TR equal to $((\text{ref\_pic\_id} \& 0x0FFF) + \text{delta\_ref\_pic\_id}) \% \text{MaxTR}$ , when such pictures were present in the video bitstream, are indicated to have been entirely or partially lost. + +- Otherwise, if `payloadType` is equal to 2, bit 12 of `ref_pic_id` shall be equal to 0. The picture having TR equal to `picIdentifier` and, when bit 13 of `ref_pic_id` is equal to 1, having ELNUM equal to `ref_pic_id & 0x03C000`, is partially lost. The value of `data_partition_idc` indicates that all data (when `data_partition_idc` is equal to 0), header data partition (when `data_partition_idc` is equal to 1), motion vector partition (when `data_partition_idc` is equal to 2) or coefficient data partition (when `data_partition_idc` is equal to 3) of the identified macroblocks is lost. All other values of `data_partition_idc` are reserved for future use by ITU-T and shall be ignored. + - Otherwise (`payloadType` is equal to 5), no further specification. +- Otherwise (Annex U/H.263 is in use), depending on the value of `payload type`, the following applies. +- If `payloadType` is equal to 0, `ref_pic_id` or `good_ref_pic_id[ i ]` identifies a stored picture without detected bitstream error mismatch. The variable `picIdentifier` indicates the value of the stored picture's PN (when the stored picture is a short-term picture) or LPIN (when the stored picture is a long-term picture). + - If the picture is a short-term picture, the value of `picIdentifier` shall be less than `MaxPN`, which is the maximum possible value of PN plus 1. + - Otherwise (the picture is a long-term picture), the value of `picIdentifier` shall be less than `MaxLPIN`, which is the maximum possible value of LPIN plus 1. + - Otherwise, if `payloadType` is equal to 1, bit 12 of `ref_pic_id` shall be equal to 0, and `picIdentifier` indicates the value of PN of a picture. The value of PN shall be less than `MaxPN` that is equal to the maximum possible value of PN plus 1. All pictures, in decoding order and in the same enhancement or base layer, starting with a picture having PN equal to `ref_pic_id & 0x0FFF`, up to and including a picture having PN equal to $((\text{ref\_pic\_id} \& 0\text{x0FFF}) + \text{delta\_ref\_pic\_id}) \% \text{MaxPN}$ , when such pictures were present in the video bitstream, are indicated to have been entirely or partially lost. `MaxPN` is equal to the maximum possible value of PN plus 1. + - Otherwise, if `payloadType` is equal to 2, bit 12 of `ref_pic_id` shall be equal to 0, and `picIdentifier` indicates the value of PN of a picture. The value of PN shall be less than `MaxPN` that is equal to the maximum possible value of PN plus 1. The picture having TR equal to `picIdentifier` and, when bit 13 of `ref_pic_id` is equal to 1, having ELNUM equal to `ref_pic_id & 0x03C000`, is partially lost. Each block is a macroblock. The value of `data_partition_idc` indicates that all data (when `data_partition_idc` is equal to 0), header data partition (when `data_partition_idc` is equal to 1), motion vector partition (when `data_partition_idc` is equal to 2) or coefficient data partition (when `data_partition_idc` is equal to 3) of the identified macroblocks is lost. All other values of `data_partition_idc` are reserved for future use by ITU-T and shall be ignored. + - Otherwise (`payloadType` is equal to 5), no further specification. + +## 7.3 H.264 specific use of the messages + +The H.264 features that are supported by the present syntax include the following: + +- Long-term reference pictures; +- Data partitioning; +- Sequence and picture parameter set. + +The following H.264 features are not supported by the present syntax: + +- Frames coded using macroblock-adaptive frame-field coding; +- Field pictures. + +When `ref_pic_id` or `good_ref_pic_id[ i ]` is present, the following applies. The 16 LSBs indicate the value of the variable `picIdentifier`, which is equal to `ref_pic_id & 0xFFFF` or `good_ref_pic_id[ i ] & 0xFFFF`. When `payloadType` is equal to 0, bit 16 indicates whether the reference picture is a long-term reference picture (when the bit is equal to 1) or a short-term reference picture (when the bit is equal to 0). The remaining bits of `ref_pic_id` or `good_ref_pic_id[ i ]` are reserved for future use by ITU-T, shall be equal to 0, and shall be ignored. + +Depending on the value of `payloadType`, the following applies. + +- If `payloadType` is equal to 0, `ref_pic_id` or `good_ref_pic_id[ i ]` identifies a reference picture without detected bitstream error mismatch. The variable `picIdentifier` indicates the value of the reference picture's `FrameNum` (when the reference picture is a short-term reference picture) or `LongTermFrameIdx` (when the reference picture is a long-term reference picture). + - If the picture is a short-term reference picture, the value of `picIdentifier` shall be less than `MaxFrameNum`. + - Otherwise (the picture is a long-term reference picture), the value of `picIdentifier` shall not be greater than `MaxLongTermFrameIdx`. +- Otherwise, if `payloadType` is equal to 1, bit 16 shall be equal to 0, and the variable `picIdentifier` indicates the value of `FrameNum` of a reference picture. The value of `FrameNum` shall be less than `MaxFrameNum`. All pictures, in decoding order, starting with a picture having `FrameNum` equal to `ref_pic_id & 0xFFFF`, up to and including a picture having `FrameNum` equal to $( ( \text{ref\_pic\_id} \& 0xFFFF ) + \text{delta\_ref\_pic\_id} ) \% \text{MaxFrameNum}$ , when such pictures were present in the video bitstream, are indicated to have been entirely or partially lost. +- Otherwise, if `payloadType` is equal to 2, bit 16 shall be equal to 0, and the variable `picIdentifier` indicates the value of `FrameNum` of a reference picture that is partially lost. The value of `FrameNum` shall be less than `MaxFrameNum`. Each block is a macroblock. The value of `data_partition_idc` indicates that all data (when `data_partition_idc` is equal to 0), data partition A (when `data_partition_idc` is equal to 1), data partition B (when `data_partition_idc` is equal to 2) or data partition C (when `data_partition_idc` is equal to 3) of the identified macroblocks is lost. All other values of `data_partition_idc` are reserved for future use by ITU-T and shall be ignored. +- Otherwise, if `payloadType` is equal to 3 or 4, the 16 LSBs of `ref_pic_id` indicate the `FrameNum` which is equal to `ref_pic_id & 0xFFFF`, of a reference picture for which a CRC is present for one or all the associated sequence parameter sets or picture parameter sets. The value of `ref_pic_id & 0xFFFF` shall be less than `MaxFrameNum`. The remaining bits of `ref_pic_id` are reserved for future use by ITU-T, shall be equal to 0, and shall be ignored. A parameter set with `param_set_type` equal to 0 is a sequence parameter set NAL unit. A parameter set with `param_set_type` equal to 1 is a picture parameter set NAL unit. When used in calculation of a CRC, the `forbidden_zero_bit` and `nal_ref_idc` of a sequence or picture parameter set NAL unit are set equal to 0 and 3, respectively. +- Otherwise (`payloadType` is equal to 5), no further specification. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.272-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.272-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/H/T-REC-H.272-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/H/T-REC-H.272-200701-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.272-200701-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e1fd50b326037c9c6f6d4c54bb1fb4a2c7242cc --- /dev/null +++ b/marked/H/T-REC-H.272-200701-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aec65a9adf953b195a184ca473ae3262c8561ae8063486a7889551d3517ee27e +size 27156 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e6ce851721bae2423a32282e21b140bc4f16824 --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d846141e49df1dc7f7bbd2c0176bc6f10039fae360aa0ba4bcb0100b29fa22c5 +size 4705 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c9ac87d1f117671f2efcbaa11d9d742f680afdb --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42beeb77d7d7038b34129980f5d77648f7043948345b17c588674ba89bfd4b25 +size 19457 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..628a470c7c61b1770527b634a38e6ba8e664cc27 --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef2988559b85c098613c8b953977a0116c5887170cfadd56f2e422a8e58cf6a7 +size 25712 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2dc62315ba14fed7ce0a4fa7abf86f088dd864c --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40dc51b4e8afa40f967906c1616fab43f93fc641f8cc10889d2e7ed59bf9aa18 +size 143030 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f318b3b170edaedef731b0afbfd803c03c0e299 --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca55f131f5bf5205a34a8a77eb4b701ce74aa65a8093fb82ffe97a862ac3d9f4 +size 143342 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f9ceb604753be94d28b324581f8e253f05b23eb --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d84aab15b6217753678d66ad8b26dde27d6ec5edae6988febf7ee0edfd079d8 +size 123289 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e334b6d8580ea3861cd8ae928f225c0a126ed799 --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbcd8c2ecf50a462303a1af178bd55ee5b8a5c99a5f708d8a7e396e216805661 +size 10974 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e31bb08bce562976ce1edcbeff5316265b917737 --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76c107a924fd8df336f668828a432ce639cb964cf1a1fc26b725751ef3674431 +size 143931 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..800da3311616dbbf1c181f4f71dbcea10bb448e3 --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec7f9b38733665db5831d0cb66ff7fbb57bbf81b1d5b329294afe5a72a937a0f +size 143964 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cb7455ee43142563c1ab0fdfce8794cef2fb306 --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c5bddd86299bf5cb161247a38cda95c56a3a2483b8999ff4b6ff922340be493 +size 45389 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..311250fff6dd1698d32b8e0022ae3f2e8b75bab0 --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:737d6aac0071187d540f7c6dc69c9fdd617c23358334478cac1160b635d9aef6 +size 142875 diff --git a/marked/H/T-REC-H.273-202407-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.273-202407-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..144cc1d3c85a6770a668cacb76908482269b4768 --- /dev/null +++ b/marked/H/T-REC-H.273-202407-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5268dab5ff586cf89c6512e8d20859ff55f2e4bed347d0be9255562c567778ae +size 145338 diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/raw.md b/marked/H/T-REC-H.281-199411-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ccc19561f8f270aa5b27de55155ac4fc172a5cd6 --- /dev/null +++ b/marked/H/T-REC-H.281-199411-I_PDF-E/raw.md @@ -0,0 +1,340 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**H.281** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(11/94) + +**TRANSMISSION OF NON-TELEPHONE SIGNALS** + +--- + +**A FAR END CAMERA CONTROL PROTOCOL +FOR VIDEOCONFERENCES USING H.224** + +**ITU-T Recommendation H.281** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation H.281 was prepared by ITU-T Study Group 15 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 1st of November 1994. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|----------------------------------------|-------------| +| Summary..... | ii | +| 1 Scope..... | 1 | +| 2 Normative References ..... | 1 | +| 3 Definitions..... | 1 | +| 4 Abbreviations ..... | 2 | +| 5 Elements of Procedure ..... | 2 | +| 5.1 Action messages..... | 3 | +| 5.2 Action message examples ..... | 3 | +| 5.3 Select video source ..... | 4 | +| 5.4 Select video source examples ..... | 4 | +| 5.5 Store preset..... | 4 | +| 5.6 Activate preset ..... | 4 | +| 5.7 General..... | 4 | +| 6 FECC message structure ..... | 5 | +| 6.1 FECC capabilities fields..... | 7 | + +# **SUMMARY** + +The Recommendation describes how a far end camera control system for H.320 terminals can be operated based on H.224 running on LSD, HSD, or MLP as a lower layer for both point-to-point and multipoint operation. + +# A FAR END CAMERA CONTROL PROTOCOL FOR VIDEOCONFERENCES USING H.224 + +(Geneva, 1994) + +# 1 Scope + +This Recommendation covers the elements of procedure and format of fields to support a Far End Camera Control (FECC) protocol layered over the Data Link protocol covered in Recommendation H.224. The FECC protocol is designed to operate in both point-to-point and multipoint simplex modes, using the H.224 link layer protocol. A major requirement of the Far End Camera Control application is for both minimum variation in delay as well as minimal absolute delay. + +This FECC protocol, together with Recommendation H.224, allows each camera in a multipoint video conference to be individually controlled from any video terminal. + +The FECC protocol shall require of the H.224 link layer that, if both the LSD and HSD channels are in use for H.224, all FECC data be transmitted on the LSD channel only. This will ensure that FECC data is received in the order in which it is transmitted. + +# 2 Normative References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation H.224, *A Data Link Layer for simplex applications using the H.221 LSD/HSD/MLP channels.* +- ITU-T Recommendation H.261 (1993), *Video Codec for Audiovisual Services at $p \times 64$ kbit/s.* +- CCITT Recommendation T.50 (1984), *International Alphabet No. 5.* + +# 3 Definitions + +For the purposes of this Recommendation, the following definitions apply: + +**3.1 simplex protocol:** A communication protocol that is purely one-way, and where acknowledgements are not part of any application protocol. Error control is either not provided, or is accomplished via forward error correction. + +**3.2 client:** An entity that uses the data transfer services of the Data Link layer. Far End Camera Control is an example of such a client. + +**3.3 client management entity:** A data link client that uses Client ID $0 \times 00$ to send a complete list of locally registered clients and their optional extra capabilities. See Recommendation H.224 for additional information. + +**3.4 FECC commands:** Atomic requests to act on a remote camera. Examples of FECC Commands include: Start Camera Action, Continue Camera Action, Stop Camera Action and Select Video Source. + +**3.5 PTZF:** Pan, Tilt, Zoom, and Focus – the four basic camera movements supported by this protocol. + +**3.6 room preset:** Information that may be used to select a video source, and then control the video source to provide the desired view. Support for Room Presets is an extra capability and is announced in the extra capabilities message sent by the H.224 CME. The ability to provide presets is optional and may not be supported in all terminals. + +**3.7 activate preset:** A command that requests a terminal switch to the video source specified by the room preset and position the video source to provide the view specified by the room preset. An Activate Preset command may be issued by a user local to a video teleconferencing terminal, or remotely by a user at another terminal. For the purposes of this Recommendation, we assume an Activate Preset is issued remotely. + +**3.8 ASCII:** Characters coded as in International Alphabet No. 5 as defined in Recommendation T.50, with bit 8 set to zero. + +**3.9 normal resolution still image:** A still image transmitted in the H.261 video stream encoded to the same resolution as the previous motion video (i.e. QCIF or FCIF). This mode uses bit 2 “Document Camera Indicator” as defined in 4.2.1.3/H.261. + +**3.10 double resolution still image:** A still image transmitted in the H.261 video stream encoded to twice the horizontal and twice the vertical resolution as the previous motion video (i.e. FCIF or 4\*FCIF). This mode uses bit 5 “Hi\_Res” as defined in 4.2.1.3/H.261 and Annex D/H.261. + +# 4 Abbreviations + +CIF Common Intermediate Format. (See Recommendation H.261 for more information). + +CME Client Management Entity. + +FCIF Full CIF. (This is the same as CIF). + +QCIF Quarter CIF. (See Recommendation H.261 for more information). + +# 5 Elements of Procedure + +The FECC protocol has the following basic messages types: + +- START ACTION – Requests for each of the three camera axis of movement. +- CONTINUE ACTION – Requests for each of the three camera axis of movement. +- STOP ACTION – Requests for each of the three camera axis of movement. +- SELECT VIDEO SOURCE – Requests a switch to the indicated video source for encoding and transmission. +- STORE PRESET – Requests the current video source and its current spatial parameters are stored in the indicated preset number. +- ACTIVATE PRESET – Requests the indicated preset is used to select the video source and set its spatial coordinates. + +## 5.1 Action messages + +START ACTION messages have an associated action parameter and a time out value. The action parameter indicates what camera motion (from the set of PTZF) is desired, and which direction is desired. CONTINUE ACTION messages and STOP ACTION messages also have the same associated action parameter. A CONTINUE ACTION message with an action parameter matching the previous START ACTION shall restart the time out period. A STOP ACTION message with an action parameter matching the previous START ACTION causes the camera positioning to stop. (The minimum duration for the START ACTION command is left to the discretion of the manufacturer based on camera parameters. This minimum duration shall ensure that some motion does occur.) If the time out occurs, the receiving FECC client shall act as though a STOP ACTION message with the appropriate action parameter has been received. Any subsequent CONTINUE or STOP action messages shall be discarded until a new START ACTION message is received. The time out value sent in an initial START ACTION message protects against the possible loss of the final STOP ACTION request. Any CONTINUE ACTION message or STOP ACTION message with an action parameter that does not match the immediately proceeding START ACTION message shall be discarded. + +Continuous camera motion is achieved through use of an initial START ACTION message followed by a series of zero or more CONTINUE ACTION messages, and terminated by a STOP ACTION message. The time interval between transmission of any two consecutive messages in this sequence shall not exceed the time out value specified in the START ACTION message minus 200 milliseconds. If continuous motion is desired, the time out value must therefore be set to 250 milliseconds or greater. + +The action parameter of a START ACTION message may indicate multiple motions in the same command (for example, Pan Right and Tilt Up). Any CONTINUE ACTION message or STOP ACTION message shall have an action parameter matching all the motion attributes of the preceding START ACTION message. After a valid START ACTION message has been received, and possibly followed by any number of matching CONTINUE ACTION messages, a new START ACTION message may be issued with a different action parameter. This new START ACTION message shall be interpreted as a valid STOP ACTION message for any motion that is no longer set, and shall be interpreted as a valid CONTINUE ACTION message for any motion that continues to be set, and shall be interpreted as a valid START ACTION message for any new motion that is indicated by the action parameter. Implementers shall ensure that once a terminal starts acting on camera commands from one remote terminal, camera commands from other remote terminals are discarded until motion from the first camera stops. The data link protocol (see Recommendation H.224) provides both source and destination addresses on messages to allow this interlocking. + +## 5.2 Action message examples + +An example of a valid camera sequence may help to illustrate the proper use of the protocol. A START ACTION message indicating Pan Right and Tilt Up may be issued, followed by any number of CONTINUE ACTION messages also specifying Pan Right and Tilt Up. These messages may be followed by another START ACTION message specifying Pan Right only. Any number of CONTINUE ACTION messages specifying Pan Right may then be issued. Another START ACTION message may then be sent specifying Pan Right and Tilt Down, which in turn is followed by any number of CONTINUE ACTION messages specifying Pan Right and Tilt Down. Finally a STOP ACTION message specifying Pan Right and Tilt Down is issued to terminate far end control of the camera. In this example the Pan Right action is continuous while the Tilt Up action is only valid for the first part of the camera control. Similarly, the Tilt Down action is only valid for the last part of the camera control. The use of multiple camera controls simultaneously is optional for terminals both sending and receiving FECC requests. Any terminal not equipped to handle simultaneous camera motion commands shall operate on one or more of the commands and disregard the others. The choice of axes in which to move is arbitrary. (The far end user will see one or more of the camera requests acted upon and then may send the other motion commands later.) + +## 5.3 Select video source + +A SELECT VIDEO SOURCE message has an associated video source and video mode parameters. On receipt of the SELECT VIDEO SOURCE message the terminal shall check for the validity of the video source and for the validity of the video mode for this source. If either parameter is invalid, the receiving terminal shall discard the message without further action. If the parameters are valid and the chosen video mode is motion video, then the receiving terminal shall change its video selector so the requested video source is sent to the video encoder and transmitted. This selected video source and mode shall remain in effect until another valid SELECT VIDEO SOURCE message is received, or until a user changes the mode locally. If the parameters are valid and the mode requests a still image transmission (either using normal resolution or double resolution), the receiving terminal shall switch the video source and code a single still image frame for transmission in the H.261 video stream. After sending the single still image the video selector is switched back to the previously chosen video source for encoding and transmission. + +## 5.4 Select video source examples + +The use of SELECT VIDEO SOURCE may be best illustrated by examples. In the first example let us assume the main camera is sending motion video to the H.261 encoder for transmission. Receiving a SELECT VIDEO SOURCE message requesting a normal resolution still image from a 35 mm slide projector, would cause acquisition and H.261 encoding of that frame. Automatically the video selector would revert back to the main camera sending motion video when the still image coding and transmission is completed. + +In the next example let us assume the main camera is sending motion video to the H.261 encoder for transmission. Receiving a SELECT VIDEO SOURCE message requesting motion video from a document camera would cause the video selector to choose the document camera for encoding and transmission. A subsequent SELECT VIDEO SOURCE command requesting a double resolution still image from the document camera would cause acquisition and H.261 encoding of that frame in the higher resolution mode. Automatically the video selector would revert back to the document camera sending motion video (as the last selected motion video source) when the still image coding and transmission is complete. + +## 5.5 Store preset + +A STORE PRESET message has an associated preset number as a parameter. If this optional feature is provided, the receiving terminal is requested to store the current video source and information about its spatial coordinates (i.e. pan, tilt, zoom, and focus information) into the preset location indicated by the preset number. (We note that Recommendation H.224 does not guarantee delivery of messages. To help assure reliable message delivery, manufacturers may choose to repeat this message.) + +## 5.6 Activate preset + +An ACTIVATE PRESET message has an associated preset number as a parameter. If this optional feature is provided, the receiving terminal positions the video source associated with the preset to the stored spatial coordinates (i.e. pan, tilt, zoom, and focus), and switches the video selector to choose this video source. + +## 5.7 General + +It is recommended that FECC messages are sent as HIGH PRIORITY datagrams to the underlying Data Link layer. + +All FECC messages are requests with no response required over the communication link. This allows for operation over a simplex transmission link. Visual feedback of the change in camera placement enables the FECC message sender to determine when to stop updating along any specific camera axis. Because visual feedback is used, timely delivery of messages is necessary for proper operation. + +# 6 FECC message structure + +START ACTION type messages (see Figure 1) have an associated time out value octet. A CONTINUE message matching the original START ACTION shall reset the time out period. + +![](562f471e8153729557e6a4ee6343c32c_img.jpg) + +| | | | | | | | | | +|----------------------|----------------|---|----------------|---------|----------------|---|----------------|---------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| START ACTION Request | | | | | | | | Code value = 0 × 01 | +| P | R = 1
L = 0 | T | U = 1
D = 0 | Z | I = 1
O = 0 | F | I = 1
O = 0 | | +| Reserved | | | | Timeout | | | | | + +FIGURE 1/H.281 + +## START ACTION message + +The arguments required for each command are detailed in the following paragraphs: + +A Start Action command: axis to move and direction (i.e. Pan right/left, Tilt up/down or Zoom in/out; set PTZF bits to 1 to start motion on that axis). For example, a START ACTION message with P = 1/L = 0 T = 0/U = 0 Z = 0/I = 0 and F = 0/I = 0 (0 × 80) will cause the remote camera to begin panning to the left. As another example, a START ACTION message with P = 0/R = 0 T = 1/U = 1 Z = 0/I = 0 and F = 0/I = 0 (0 × 30) will cause the remote camera to begin tilting upward. Note that more than one action may be specified to occur at the same time. Note also that if the P/T/Z/F bits are not set, the direction bit is ignored. Thus, in the first example given, P = 1/L = 0 T = 0/U = 1 Z = 0/I = 1 and F = 0/I = 1 (0 × 95) would have the same effect as (0 × 80) since only the Pan(P) bit is evaluated. + +Time out value is a 4-bit binary number expressed in 50 milliseconds intervals. For example, the binary pattern 1000 represents 400 milliseconds. A time out value of zero means 800 milliseconds. + +A Continue Action command (see Figure 2): axis to move and direction. + +![](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +| | | | | | | | | | +|-------------------------|----------------|---|----------------|---|----------------|---|----------------|---------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| CONTINUE ACTION Request | | | | | | | | Code value = 0 × 02 | +| P | R = 1
L = 0 | T | U = 1
D = 0 | Z | I = 1
O = 0 | F | I = 1
O = 0 | | + +FIGURE 2/H.281 + +## CONTINUE ACTION message + +A Stop Action command (see Figure 3): axis to move and direction. + +![](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +| | | | | | | | | | +|---------------------|----------------|---|----------------|---|----------------|---|----------------|---------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Code value = 0 × 03 | +| STOP ACTION Request | | | | | | | | | +| P | R = 1
L = 0 | T | U = 1
D = 0 | Z | I = 1
O = 0 | F | I = 1
O = 0 | | + +FIGURE 3/H.281 + +## **STOP ACTION message** + +Note that the direction bits (R/L, U/D, I/O, I/O) immediately following the action bits (P/T/Z/F) are ignored in the Stop Action command. + +A Select Video Source command (see Figure 4): the number of the video source to use for encoding and transmission. + +![](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +| | | | | | | | | | +|--------------------------------|---|---|---|----------|---|----|----|---------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Code value = 0 × 04 | +| SELECT VIDEO SOURCE Request | | | | | | | | | +| 4-bit encoded
source Number | | | | Reserved | | M1 | M0 | | + +FIGURE 4/H.281 + +## **SELECT VIDEO SOURCE message** + +M1 and M0 convey the binary coding for the mode to be used on activation of the video source (M1 = 0, M0 = 0 for motion video; M1 = 1, M0 = 0 for normal resolution still image; and M1 = 1, M0 = 1 for double resolution still image). + +Optionally a terminal may broadcast that it has switched its video source (see Figure 5), if it has declared that it will do so in the initial FECC capability. + +![](b10763be31553f31cbb795653b731a43_img.jpg) + +| | | | | | | | | | +|----------------------------------|---|---|---|----------|---|----|----|---------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Code value = 0 × 05 | +| VIDEO SOURCE SWITCHED indication | | | | | | | | | +| 4-bit encoded
source Number | | | | Reserved | | M1 | M0 | | + +FIGURE 5/H.281 + +## **VIDEO SOURCE SWITCHED message** + +A Store Preset command (see Figure 6): preset number to hold the video source number and its current spatial coordinates + +![](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +| | | | +|----------------------------------------------------|----------|---------------------| +| 8      7      6      5      4      3      2      1 | | | +| STORE AS PRESET Request | | Code value = 0 × 06 | +| 4-bit encoded
preset Number | Reserved | | + +FIGURE 6/H.281 + +## **STORE AS PRESET message** + +Activate Preset command (see Figure 7): preset number used to select the video source and to change its spatial coordinates + +![](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +| | | | +|----------------------------------------------------|----------|---------------------| +| 8      7      6      5      4      3      2      1 | | | +| ACTIVATE PRESET Request | | Code value = 0 × 07 | +| 4-bit encoded
preset Number | Reserved | | + +FIGURE 7/H.281 + +## **ACTIVATE PRESET message** + +## 6.1 FECC capabilities fields + +The FECC Client capabilities are sent by the H.224 Client Management Entity in the form of a CME Extra Capabilities message. The FECC client at time of registration with the H.224 layer shall submit a data block encoded as per the following field formats. The first field is an octet indicating the number of presets supported by this terminal. This is followed by a description of the capabilities of each camera present at this site. The fields required to describe basic camera capabilities are Camera number, indication of the ability to send motion video using this camera, and indication of the ability to send normal resolution still images using this camera, an indication of the ability to send double resolution still images with this camera, the ability to Pan, the ability to Tilt, the ability to Zoom, and the ability to Focus this camera. Any video source omitted from the capabilities set shall be assumed to not be present. + +Video Sources 0 through 5 are preassigned to the following devices: + +- 0 Default – Current Video Source; +- 1 Main Camera; +- 2 Auxiliary Camera; +- 3 Document Camera; +- 4 Auxiliary Document Camera; +- 5 Video Playback Source (such as a Video Cassette Recorder). + +The first octet (see Figure 8) describes the number of presets supported. + +![](007b053fe94a8348f75128a584503fd0_img.jpg) + +| | | | | | | | | +|----------|---|---|---|---|---------------------------------------|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Reserved | | | | B | Number of presets
(binary encoded) | | | + +FIGURE 8/H.281 + +### **Number of presets octet** + +B bit is set to logic 1 if terminal will broadcast that it has switched video sources. + +To describe these standard video sources in the capabilities message, only the Video Source number and its capabilities need to be specified (see Figure 9). The capabilities that may be specified are motion video, normal resolution still images, double resolution still images, Pan, Tilt, Zoom, Focus, and the number of presets associated with this video source. A 1 in any of these bit positions indicates the camera has this capability. A 0 indicates the camera does not have this capability. + +![](08441fa90c5fd11994626f662ac13f19_img.jpg) + +| | | | | | | | | +|-----------------------------|------|------|-------|----------|-----------------|----------------------------------------|----------------------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 4-bits encoded Video Source | | | | Reserved | Motion
video | Normal
resolution
still
image | Double
resolution
still
image | +| Pan | Tilt | Zoom | Focus | Reserved | | | | + +FIGURE 9/H.281 + +### **Standard video source capabilities** + +Video Sources 6 through 15 may be assigned to other devices. To describe these devices using the capabilities field requires specifying the number of the video source, followed by a variable length ASCII string (with a maximum length of 16 characters) identifying the type of camera (the ASCII string is terminated with all zeros byte), followed by a list of the capabilities (see Figure 10). The capabilities that may be specified are motion video, normal resolution still images, double resolution still images, Pan, Tilt, Zoom, Focus, and the number of presets associated with this video source. + +![](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +| | | | | | | | | +|-----------------------------------|------|------|-------|----------|-----------------|----------------------------------------|----------------------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 4-bits encoded Video Source | | | | Reserved | Motion
video | Normal
resolution
still
image | Double
resolution
still
image | +| Up to 16 ASCII encoded characters | | | | | | | | +| All zeros octet | | | | | | | | +| Pan | Tilt | Zoom | Focus | Reserved | | | | + +FIGURE 10/H.281 + +### **Capabilities for video sources 6 through 15** \ No newline at end of file diff --git a/marked/H/T-REC-H.322-199603-I_PDF-E/raw.md b/marked/H/T-REC-H.322-199603-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..588b53c0f07c1d6b2bdbdbce8d6c4fb76ac00863 --- /dev/null +++ b/marked/H/T-REC-H.322-199603-I_PDF-E/raw.md @@ -0,0 +1,247 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**H.322** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/96) + +**TRANSMISSION OF NON-TELEPHONE SIGNALS** + +--- + +**VISUAL TELEPHONE SYSTEMS AND +TERMINAL EQUIPMENT FOR LOCAL AREA +NETWORKS WHICH PROVIDE A +GUARANTEED QUALITY OF SERVICE** + +**ITU-T Recommendation H.322** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation H.322 was prepared by ITU-T Study Group 15 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 19th of March 1996. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|-------------------------------------------|-------------| +| 1 Scope ..... | 1 | +| 2 References ..... | 3 | +| 3 Definitions and abbreviations..... | 3 | +| 3.1 Definitions ..... | 3 | +| 3.2 Abbreviations..... | 4 | +| 4 Terminal equipment ..... | 4 | +| 5 H.322 gateway..... | 5 | +| 6 Dependency on Recommendation H.320..... | 6 | + +# **SUMMARY** + +This Recommendation covers the technical requirements for narrow-band visual telephone services defined in H.200/AV.120-series Recommendations, in those situations where the transmission path includes one or more Local Area Networks (LAN), each of which is configured and managed to provide a guaranteed Quality of Service (QOS) equivalent to that of N-ISDN such that no additional protection or recovery mechanisms beyond those mandated by Recommendation H.320 need be provided in the terminals. It is noted that projected Recommendation H.323 addresses the use of some other LANs which are unable to provide the underlying performance assumed by this Recommendation. + +# **VISUAL TELEPHONE SYSTEMS AND TERMINAL EQUIPMENT FOR LOCAL AREA NETWORKS WHICH PROVIDE A GUARANTEED QUALITY OF SERVICE** + +*(Geneva, 1996)* + +The ITU-T, + +*considering* + +the widespread adoption of and the increasing use of the H.320 Recommendation for videophony and videoconferencing services over networks conforming to the N-ISDN characteristics specified in the I-Series Recommendations, + +*appreciating* + +the desirability and benefits of enabling the above services to be carried, wholly or in part, over Local Area Networks while also maintaining the capability of interworking with H.320 terminals, + +*and noting* + +the characteristics and performances of the many types of Local Area Network which are of potential interest, + +*recommends* + +that systems and equipment meeting the requirements of the H.322 or H.323 Recommendations are utilized to provide these facilities. + +# **1 Scope** + +This Recommendation covers the technical requirements for narrow-band visual telephone services defined in H.200/AV.120-Series Recommendations, in those situations where the transmission path includes one or more Local Area Networks (LAN), each of which is configured and managed to provide a guaranteed Quality of Service (QOS) equivalent to that of N-ISDN such that no additional protection or recovery mechanisms beyond those mandated by Recommendation H.320 need be provided in the terminals. Pertinent parameters are the data error and loss properties and variation of transit delay this Recommendation also requires that the ISDN clock is available at the terminals. An example of a suitable LAN is: + +IEEE Std 802.9a-1995, IEEE Standard for Local and Metropolitan Area Networks – Supplement to Integrated Services (IS) LAN Interface at the Medium Access Control (MAC) and Physical (PHY) Layers: Specification of ISLAN16-T. + +Recommendation H.323 addresses the use of some other LANs which are unable to provide the underlying performance assumed by this Recommendation. + +Although some LANs offer satisfactory QOS to support this Recommendation, they do not themselves provide standardized means of identifying the intended called terminal. For such LANs the procedures for terminal addressing defined in Recommendation H.323 shall apply in addition to the provisions of this Recommendation. + +This Recommendation does not encompass ATM LANs because they are within the scope of Recommendation H.321. + +Systems and terminal equipment complying with this Recommendation are able to interwork with each other and with those complying with Recommendations H.320, H.321 and H.323. The concept is shown in Figure 1 in which any terminal can be connected to any other. The H.322 gateway unit provides an interconnection between the LAN and the Wide Area Network (WAN) which may be N-ISDN or B-ISDN or both. An H.322 terminal communicates with another H.322 terminal on the same LAN directly. The gateway may be connected via N-ISDN or B-ISDN to other gateways and LANs to provide communication between H.322 or H.323 terminals which are not on the same LAN. + +Although this Recommendation specifically addresses visual telephone systems, the methods used do not depend on the content of the signals carried. Consequently this Recommendation has more general applicability to connecting terminals, originally designed for N-ISDN, over LAN or hybrid LAN and ISDN networks. + +![Diagram showing the scope and interworking capabilities of Recommendation H.322. It illustrates connections between H.322 terminals on a Guaranteed QOS LAN, H.320 and H.321 terminals on N-ISDN and B-ISDN respectively, and H.323 terminals on a Non-guaranteed QOS LAN, all interconnected via a central Rec. I.580 node.](547f726730e589392f239257a833ede3_img.jpg) + +The diagram illustrates the network architecture for Recommendation H.322. At the top, a dashed oval labeled "Scope of Rec. H.322" contains a "Guaranteed QOS LAN" bus. Connected to this bus are an "H.322 Gateway" and three "H.322 Terminal" units. The "H.322 Gateway" is connected to an "N-ISDN" node. The "N-ISDN" node is connected to two "H.320 Terminal" units and to a central "Rec. I.580" node. The "Rec. I.580" node is also connected to a "B-ISDN" node. The "B-ISDN" node is connected to two "H.321 Terminal" units and to an "H.323 Gateway". A note next to the H.321 terminals states "H.310 terminal operating in H.321 mode". The "H.323 Gateway" is connected to a "Non-guaranteed QOS LAN" bus, which is also connected to three "H.323 Terminal" units and an "H.323 Terminal" unit. These components are enclosed in a dashed oval labeled "Scope of Rec. H.323". The text "T1518850-95/d01" is located at the bottom right of the diagram. + +Diagram showing the scope and interworking capabilities of Recommendation H.322. It illustrates connections between H.322 terminals on a Guaranteed QOS LAN, H.320 and H.321 terminals on N-ISDN and B-ISDN respectively, and H.323 terminals on a Non-guaranteed QOS LAN, all interconnected via a central Rec. I.580 node. + +NOTE – A gateway may support only the N-ISDN or B-ISDN connection. + +FIGURE 1/H.322 +**Scope and interworking capabilities of Recommendation H.322** + +## 2 References + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- Recommendation E.164 (1991), *Numbering plan for the ISDN era* (same as Recommendation I.331). +- ITU-T Recommendation H.221 (1995), *Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices*. +- ITU-T Recommendation H.230 (1995), *Frame-synchronous control and indication signals for audiovisual systems*. +- ITU-T Recommendation H.231 (1996), *Multipoint control units for audio-visual systems using digital channels up to 1920 kbit/s*. +- ITU-T Recommendation H.242 (1996), *System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s*. +- ITU-T Recommendation H.261 (1996), *Video codec for audiovisual services at $p \times 64$ kbit/s*. +- ITU-T Recommendation H.320 (1996), *Narrow-band visual telephone systems and terminal equipment*. +- ITU-T Recommendation H.321 (1996), *Adaptation of H.320 visual telephone terminals to B-ISDN environments*. +- ITU-T Recommendation H.3231), *Visual telephone systems and terminal equipment for local area networks which provide a guaranteed quality of service*. +- ITU-T Recommendation H.331 (1993), *Broadcasting type audiovisual multipoint systems and terminal equipment*. +- ITU-T Recommendation I.430 (1995), *Basic user-network interface – Layer 1 specification*. +- ITU-T Recommendation I.431 (1993), *Primary rate user-network interface – Layer 1 specification*. +- ITU-T Recommendation I.432 (1993), *B-ISDN user-network interface – Physical layer specification*. +- ITU-T Recommendation I.580 (1995), *General arrangements for interworking between B-ISDN and 64 kbit/s based ISDN*. + +## 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of this Recommendation, the following definitions apply. + +**3.1.1 local area network (LAN):** A shared or switched medium peer-to-peer communications network that broadcasts information for all stations to receive within a moderate-sized geographic area, such as a single office building or a campus. The network is generally owned, used and operated by a single organization. It provides services including those of the physical layer, the MAC layer, and the transport layer. + +**3.1.2 wide area network (WAN):** A communication network which covers a wide geographical area and accommodates terminals and LANs. It may typically be an N-ISDN or a B-ISDN. + +--- + +1) Presently at the stage of draft. + +## 3.2 Abbreviations + +For the purposes of this Recommendation, the following abbreviations are used: + +| | | +|---------|--------------------------------------------------------| +| ATM | Asynchronous Transfer Mode | +| B-ISDN | Broadband ISDN | +| CSMA/CD | Carrier sense multiple access with collision detection | +| LAN | Local Area Network | +| MAC | Media access control | +| MCU | Multipoint control unit | +| N-ISDN | Narrow-band Integrated Services Digital Network | +| QOS | Quality of Service | +| WAN | Wide Area Network | + +## 4 Terminal equipment + +Figure 2 is a block diagram of the H.322 terminal. All elements are identical to those specified in Recommendation H.320 except for the LAN interface. + +![Block diagram of H.322 terminal elements showing various input/output and control components connected to a central Mux/Demux and a Data formatting and Local Area Network Interface.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +The diagram illustrates the internal architecture of an H.322 terminal. It is enclosed in a dashed box labeled 'Recommendation H.322 Terminal equipment'. Inside, several functional blocks are shown: + +- Video I/O equipment** connects to a **Video Codec** (labeled 'Recommendation H.261'). +- Audio I/O equipment** connects to an **Audio Codec** (labeled 'H.200/AV.250-Series Recommendations'), which then connects to a **Delay** block. +- Telematic equipment** (labeled 'T-series, H.200/AV.270-Series Recommendations, etc.') connects directly to the **Mux/Demux**. +- System Control** connects to **End-to-end signalling C&I** (labeled 'Recommendations H.242, H.230, H.221') and **End-to-network signalling**. +- All the above components (Video Codec, Delay, Telematic equipment, End-to-end signalling C&I, and End-to-network signalling) connect to a central **Mux/Demux** block (labeled 'Recommendation H.221'). +- The **Mux/Demux** block connects to a **Data formatting and Local Area Network Interface** block. + +T1518860-95/d02 + +Block diagram of H.322 terminal elements showing various input/output and control components connected to a central Mux/Demux and a Data formatting and Local Area Network Interface. + +FIGURE 2/H.322 +Block diagram of H.322 terminal elements + +As illustrated in Figure 3, an H.322 terminal may be implemented as an integrated unit or as the combination of an H.320 terminal and an adapter unit. + +![Figure 3/H.322: Alternative H.322 terminal implementations. The diagram shows two configurations. The top configuration shows a single box labeled 'H.322 Terminal' connected to a 'LAN'. The bottom configuration shows a dashed box labeled 'H.322 Terminal' containing two internal components: 'H.320 Terminal' and 'Adapter Unit'. The 'H.320 Terminal' is connected to the 'Adapter Unit', which is then connected to a 'LAN'. Below the diagram is the text 'T1518870-95/d03'.](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +``` +graph LR; subgraph Top [ ]; H322[ H.322 Terminal ] --- LAN1[ LAN ]; end; subgraph Bottom [ H.322 Terminal ]; H320[ H.320 Terminal ] --- Adapter[ Adapter Unit ]; Adapter --- LAN2[ LAN ]; end; style Bottom fill:none,stroke-dasharray: 5 5; +``` + +Figure 3/H.322: Alternative H.322 terminal implementations. The diagram shows two configurations. The top configuration shows a single box labeled 'H.322 Terminal' connected to a 'LAN'. The bottom configuration shows a dashed box labeled 'H.322 Terminal' containing two internal components: 'H.320 Terminal' and 'Adapter Unit'. The 'H.320 Terminal' is connected to the 'Adapter Unit', which is then connected to a 'LAN'. Below the diagram is the text 'T1518870-95/d03'. + +FIGURE 3/H.322 +Alternative H.322 terminal implementations + +NOTE – The Adapter Unit of Figure 3 and the H.322 Gateway of Figure 1 perform no function which is specific to the audiovisual nature of the signals they handle. The same Adapter Unit and Gateway may support the connection of other N-ISDN terminals in place of the H.320 terminal in Figure 3, but such use is outside the scope of this Recommendation. + +# 5 H.322 gateway + +Some LANs have a star topology in which the central hub may be connected to the WAN as a normal feature. In such circumstances, for example IEEE 802.9a LANs, the H.322 gateway is the central hub. For other LANs the H.322 gateway may be an additional device connecting the LAN to the WAN. This is the case shown in Figure 1. + +A block diagram of the H.322 gateway device is shown in Figure 4. There are four principal functions: + +- Interface to the LAN. +- Interface to the WAN (Recommendation I.430 or I.431 for N-ISDN or Recommendation I.432 for B-ISDN). +- Conversion of the destination address of the called H.322 terminal. This is required only if the LAN does not support Recommendation E.164. +- Interworking Adapter if the WAN is B-ISDN. The basic functions required are essentially those specified in Recommendation I.580 for interworking between N-ISDN and B-ISDN. + +The number of simultaneous connections which the H.322 gateway is able to provide is not subject to standardization. + +An H.322 gateway may also contain the functionality of a Multipoint Control Unit (MCU) as specified in Recommendation H.231. This is not a mandatory requirement of this Recommendation. + +An H.322 gateway may also contain the functionality specified in Recommendation H.331 to simultaneously broadcast to a number of terminals. This is not a mandatory requirement of this Recommendation. + +![Block diagram of H.322 gateway elements showing the flow between N-ISDN/B-ISDN Interface, Interworking Adaptor, and LAN Interface, with a Destination Address Converter below.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the architecture of H.322 gateway elements. It consists of three main vertical blocks and one horizontal block at the bottom. + +1. \*\*N-ISDN or B-ISDN Interface\*\*: The leftmost block. It has an input on the left labeled 'Rec. I.430 or Rec. I.431 or Rec. I.432'. It has bidirectional horizontal connections with the 'Interworking Adaptor' block. It also has bidirectional vertical connections with the 'Destination Address Converter' block. + +2. \*\*Interworking Adaptor (Note 1)\*\*: The middle block. It has bidirectional horizontal connections with both the 'N-ISDN or B-ISDN Interface' and the 'LAN Interface' blocks. + +3. \*\*LAN Interface\*\*: The rightmost block. It has a bidirectional horizontal connection with the 'Interworking Adaptor' block. It has an output on the right labeled 'LAN'. It also has bidirectional vertical connections with the 'Destination Address Converter' block. + +4. \*\*Destination Address Converter (Note 2)\*\*: A horizontal block at the bottom. It has bidirectional vertical connections with both the 'N-ISDN or B-ISDN Interface' and the 'LAN Interface' blocks. + +A reference code 'T1518880-95/d04' is located at the bottom right of the diagram. + +Block diagram of H.322 gateway elements showing the flow between N-ISDN/B-ISDN Interface, Interworking Adaptor, and LAN Interface, with a Destination Address Converter below. + +# **NOTES** + +- 1 Not present in some gateways. +- 2 Required only if LAN does not directly support Recommendation E.164. + +**FIGURE 4/H.322** +**Block diagram of H.322 gateway elements** + +# **6 Dependency on Recommendation H.320** + +All the provisions of all clauses subsequent to and including subclause 3.2 of Recommendation H.320 are an integral part of this Recommendation. \ No newline at end of file diff --git a/marked/H/T-REC-H.331-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.331-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..431f7cf6555f330169ff19e3158a5f6f4b136273 --- /dev/null +++ b/marked/H/T-REC-H.331-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5603f29a95a0e06c23a7d999918e378ff6b453c50915bd3f942fba08cc4ba16b +size 8286 diff --git a/marked/H/T-REC-H.331-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/H/T-REC-H.331-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6b7ec8495d804e2dbc85d69fe41853e67626530 --- /dev/null +++ b/marked/H/T-REC-H.331-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e618d61a0cd1da824d055af12098f41e44a98b97942c1037746dea218fb82af +size 25016 diff --git a/marked/H/T-REC-H.331-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/H/T-REC-H.331-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67b2e96be6661a3d76ffa94641f96643b08a4929 --- /dev/null +++ b/marked/H/T-REC-H.331-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4590834cd87732de5094978e5c206f59d8f0225f1fcc74c7c1b40c2a9ed455ff +size 171827 diff --git a/marked/H/T-REC-H.332-199809-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.332-199809-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/H/T-REC-H.332-199809-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae +size 8196 diff --git a/marked/H/T-REC-H.332-199809-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/H/T-REC-H.332-199809-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d444e453359abfebc0710e0c8ed31ba0742dbcb4 --- /dev/null +++ b/marked/H/T-REC-H.332-199809-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:618557f7d258a25e41668b91ee0066668110799eda62ad2dedb11a4d19c19b58 +size 103913 diff --git a/marked/H/T-REC-H.332-199809-I_PDF-E/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/H/T-REC-H.332-199809-I_PDF-E/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4585b83a08294a02421beeb006fe309b5152c64 --- /dev/null +++ b/marked/H/T-REC-H.332-199809-I_PDF-E/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0e8ffda5b4f54e98d77ff4bd38ab70beee796abc833e5c3eae84e5b5c358a7c +size 94362 diff --git a/marked/H/T-REC-H.332-199809-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/H/T-REC-H.332-199809-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d738adebee4ebcd2628a4c4091f997b082a861a4 --- /dev/null +++ b/marked/H/T-REC-H.332-199809-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6562930e4c3932826292c3d1a76812e3b3c79842ae85e7121acb86081a49fc11 +size 25781 diff --git a/marked/H/T-REC-H.350.7-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.350.7-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/H/T-REC-H.350.7-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/H/T-REC-H.350.7-200701-I_PDF-E/raw.md b/marked/H/T-REC-H.350.7-200701-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7c7221cc27ed28d6ebef7ecad33aca98bd5a7d02 --- /dev/null +++ b/marked/H/T-REC-H.350.7-200701-I_PDF-E/raw.md @@ -0,0 +1,631 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.350.7** + +(01/2007) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Directory services +architecture for audiovisual and multimedia services + +# --- **Directory services architecture for XMPP** + +ITU-T Recommendation H.350.7 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|--------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Directory services architecture for XMPP + +## Summary + +The Extensible Messaging and Presence Protocol (XMPP) is an IETF standard protocol for exchanging information between network endpoints using Extensible Markup Language (XML). It is used to enable instant messaging and presence applications and is growing in popularity. This Recommendation includes XMPP in the suite of protocols that is supported in [ITU-T H.350], so that an organization can directory-enable and manage XMPP resources in the same way that other multimedia protocols (e.g., H.320, H.323, SIP) are managed in [ITU-T H.350]. + +## Source + +ITU-T Recommendation H.350.7 was approved on 13 January 2007 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +### Keywords + +Directory services, instant messaging, LDAP, presence, XMPP. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2007 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 1.1 Extending the schema..... | 1 | +| 1.2 Typical use cases ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Object Class definitions..... | 2 | +| 6.1 xmppURIObject Object Class ..... | 3 | +| 6.2 xmppIdentityURI attribute ..... | 3 | +| 6.3 xmppUserId attribute..... | 3 | +| 6.4 xmppPassword attribute ..... | 4 | +| 7 xmppURIObject LDIF Files ..... | 4 | +| 8 ASN.1 representation..... | 6 | +| 9 DSML representation..... | 7 | +| Annex A – Indexing profile ..... | 9 | +| Appendix I – Electronic versions of formal definitions..... | 10 | +| Bibliography..... | 11 | + + + +# Directory services architecture for XMPP + +# 1 Scope + +The Extensible Messaging and Presence Protocol (XMPP) is an IETF standard protocol for exchanging information between network endpoints using Extensible Markup Language (XML). It is used to enable instant messaging and presence applications and is growing in popularity. This Recommendation includes XMPP in the suite of protocols that is supported in [ITU-T H.350], so that an organization can directory-enable and manage XMPP resources in the same way that other multimedia protocols (e.g., H.320, H.323, SIP) are managed in [ITU-T H.350]. The schema provides a method for representing XMPP URIs and user information in the directory. Note that this Recommendation defines representation of URIs and not IRIs, as described in [IETF RFC 4622]. + +The scope of this Recommendation does not include normative methods for the use of the LDAP directory itself or the data it contains. + +## 1.1 Extending the schema + +The xmppURIObject classes may be extended as necessary for specific implementations. See the base [ITU-T H.350] document for a discussion on schema extension. + +### 1.2 Typical use cases + +Many applications external to an XMPP network may need to identify XMPP entities as full URIs; in this case an LDAP directory that needs to store XMPP addresses and non-native user agents (e.g., web browsers, calendaring applications and enterprise white pages) that provide interface to XMPP services. The simplest case is to have a white page lookup where a user is using a web browser to search for other users that are using an XMPP-based client. + +Another use case would be for an XMPP server to use XMPP account credentials (xmppUserId and xmppPassword attributes) stored in an H.350 directory for authenticating requests from XMPP clients. This is useful for environments where there is no backend authentication mechanism available. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.350] ITU-T Recommendation H.350 (2003), *Directory services architecture for multimedia conferencing*. +- [ITU-T H.350.1] ITU-T Recommendation H.350.1 (2003), *Directory services architecture for H.323*. +- [ITU-T H.350.2] ITU-T Recommendation H.350.2 (2003), *Directory services architecture for H.235*. +- [ITU-T H.350.3] ITU-T Recommendation H.350.3 (2003), *Directory services architecture for H.320*. + +- [ITU-T H.350.4] ITU-T Recommendation H.350.4 (2003), *Directory services architecture for SIP*. +- [ITU-T H.350.5] ITU-T Recommendation H.350.5 (2003), *Directory services architecture for non-standard protocols*. +- [IETF RFC 3920] IETF RFC 3920 (2004), *Extensible Messaging and Presence Protocol (XMPP): Core*. +- [IETF RFC 4622] IETF RFC 4622 (2006), *Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)*. + +# 3 Definitions + +This Recommendation uses the following terms defined elsewhere: + +**3.1 Uniform Resource Identifier (URI):** See [IETF RFC 4622] for a discussion of URIs and IRIs in XMPP. + +**3.2 Internationalized Resource Identifier (IRI):** See [IETF RFC 4622] for a discussion of URIs and IRIs in XMPP. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +- LDAP      Lightweight Directory Access Protocol (as defined in [IETF RFC 1777]). +- SASL      Simple Authentication and Security Layer (as defined in [b-IETF RFC 4422]). +- XMPP      Extensible Messaging and Presence Protocol (an IETF standard protocol for exchanging information between network endpoints using Extensible Markup Language (XML). It is commonly used for instant messaging, presence and voice over IP applications.) + +# 5 Conventions + +In this Recommendation, the following conventions are used: + +"Shall" indicates a mandatory requirement. + +"Should" indicates a suggested but optional course of action. + +"May" indicates an optional course of action rather than a recommendation that something take place. + +References to clauses, subclauses, annexes and appendices refer to those items within this Recommendation unless another specification is explicitly listed. + +# 6 Object Class definitions + +The xmppURIObject represents an XMPP URI; that is, the address of an entity that is capable of communicating using the XMPP protocol. Because it is its own unique object class, the directory can be searched for the presence of this attribute. + +Note that XMPP uses Simple Authentication and Security Layer (SASL) for authentication, enabling each deployment to make use of its own backend authentication mechanism such as Kerberos. Because of this, many applications will not need to use the username and password attributes. However, these attributes are included for those implementations which do not use backend authentication, or for implementations which do, but need a small number of static + +identities such as might be associated with server accounts for which there is associated central identity management system in the enterprise. + +## 6.1 xmppURIObject Object Class + +OID: 0.0.8.350.1.1.9.2.1 +objectclasses: (0.0.8.350.1.1.9.2.1 +NAME 'xmppURIObject' +DESC 'XmppURI object' +SUP top AUXILIARY +MAY ( xmppIdentityURI \$ xmppUserId \$ xmppPassword ) +) + +### 6.2 xmppIdentityURI attribute + +OID: 0.0.8.350.1.1.9.1.1 +attributetypes: (0.0.8.350.1.1.9.1.1 +NAME 'xmppIdentityURI' +DESC 'Labeled URI format to represent an XMPP URI' +EQUALITY caseIgnoreMatch +EQUALITY caseIgnoreSubstringsMatch +SYNTAX 1.3.6.1.4.1.1466.115.121.1.15) + +Application utility class + +standard + +Number of values + +multi + +Definition + +Specifies an XMPP URI. + +Permissible values (if controlled) + +Notes + +Implementers should review [IETF RFC 4622] for rules about escaping characters to ensure full international character set compatibility. + +Semantics + +Example applications for which this attribute would be useful + +Example (LDIF fragment) + +### 6.3 xmppUserId attribute + +OID: 0.0.8.350.1.1.9.1.2 +attributetypes: (0.0.8.350.1.1.9.1.2 +NAME 'xmppUserId' +DESC 'Xmpp UserId' +EQUALITY caseIgnoreMatch +EQUALITY caseIgnoreSubstringsMatch +SYNTAX 1.3.6.1.4.1.1466.115.121.1.15) + +Application utility class + +standard + +Number of values + +multi + +#### Definition + +Holds the user ID of an XMPP user for authentication purposes. + +Permissible values (if controlled) + +#### Notes + +Implementers should be aware that if a single H.350 directory serves multiple XMPP domains, it will not be possible to determine to which domain a particular user ID belongs. Care may be taken in the structure of the directory or in controlled access to the directory to ensure that this is deterministic. + +This attribute is not necessary if backend authentication is used. + +#### Semantics + +Example applications for which this attribute would be useful + +XMPP User ID and Password are useful if backend authentication is not used, or if implementation requires that users have multiple XMPP accounts. + +Example (LDIF fragment) + +### 6.4 xmppPassword attribute + +``` +OID: 0.0.8.350.1.1.9.1.3 +attributetypes: (0.0.8.350.1.1.9.1.3 +NAME 'xmppPassword' +DESC 'Xmpp password' +EQUALITY octetStringMatch +SYNTAX 1.3.6.1.4.1.1466.115.121.1.40) +``` + +Application utility class + +standard + +Number of values + +multi + +#### Definition + +Holds the password of an XMPP user for authentication purposes. + +Permissible values (if controlled) + +#### Notes + +Not necessary if backend authentication is used. + +#### Semantics + +Example applications for which this attribute would be useful + +XMPP User ID and Password are useful if backend authentication is not used, or if implementation requires that users have multiple XMPP accounts. + +Example (LDIF fragment) + +## 7 xmppURIObject LDIF Files + +This clause contains a schema configuration file for xmppURIObject that can be used to configure an LDAP server to support this class. + +``` +# XmppURIObject Object Schema +# +# Schema for representing a XmppURIObject Object in an LDAP Directory +``` + +``` + +# +# Abstract +# +# This document defines the schema for representing XmppURIObject +# object in an LDAP directory [LDAPv3]. It defines schema elements +# to represent an xmppURIObject object [xmppURIObject]. +# +# +# .1 = Communication related work +# .1.9 = xmppURIObject +# .1.9.1 = attributes +# .1.9.2 = objectclass +# .1.9.3 = syntax +# +# +# Attribute Type Definitions +# +# The following attribute types are defined in this document: +# +# xmppIdentityURI +# xmppUserId +# xmppPassword +dn: cn=schema +changetype: modify +# +# if you need to change the definition of an attribute, +# then first delete and re-add in one step +# +# if this is the first time you are adding the genericIdentity +# objectclass using this LDIF file, then you should comment +# out the delete attributetypes modification since this will +# fail. Alternatively, if your ldapmodify has a switch to continue +# on errors, then just use that switch -- if you're careful +# +delete: attributetypes +attributetypes: (0.0.8.350.1.1.9.1.1 NAME 'xmppIdentityURI' ) +attributetypes: (0.0.8.350.1.1.9.1.2 NAME 'xmppUserId' ) +attributetypes: (0.0.8.350.1.1.9.1.3 NAME 'xmppPassword' ) +- +# +# re-add the attributes -- in case there is a change of definition +# +# +add: attributetypes +attributetypes: (0.0.8.350.1.1.9.1.1 + NAME 'xmppIdentityURI' + DESC 'Labeled URI format to represent an XMPP URI' + EQUALITY caseIgnoreMatch + EQUALITY caseIgnoreSubstringsMatch + SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 ) +attributetypes: (0.0.8.350.1.1.9.1.2 + NAME 'xmppUserId' + DESC 'Xmpp Userid' + EQUALITY caseIgnoreMatch + EQUALITY caseIgnoreSubstringsMatch + SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 ) +attributetypes: (0.0.8.350.1.1.9.1.3 + NAME 'xmppPassword' + DESC 'Xmpp password' + EQUALITY octetStringMatch + SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 ) +- +# Object Class Definitions +# + +``` + +``` + +# The following object class is defined in this document: +# +# xmppURIObject +# +# xmppURIObject +# +# +delete: objectclasses +objectclasses: (0.0.8.350.1.1.9.2.1 NAME 'xmppURIObject' ) +- +add: objectclasses +objectclasses: (0.0.8.350.1.1.9.2.1 + NAME 'xmppURIObject' + DESC 'XmppURI object' + SUP top AUXILIARY + MAY ( xmppIdentityURI $ xmppUserId $ xmppPassword ) + ) +- +# +# end of LDIF +# + +``` + +## 8 ASN.1 representation + +H.350.7 elements may be used in an X.500 directory architecture by using the ASN.1 representation of the object classes defined here. + +``` + +XmppURIObject{ itu-t(0) recommendation(0) h(8) 350 1 cr(1) xmpp(9) module(4) } +DEFINITIONS ::= +BEGIN + +-- xmppURIObject Object Schema + +-- Schema for representing a xmppURIObject Object in an LDAP Directory + +-- Abstract + +-- This document defines the schema for representing xmppURIObject +-- object in an LDAP directory [LDAPv3]. It defines schema elements +-- to represent an XmppURIObject object [xmppURIObject]. + +-- .1 = Communication related work +-- .1.9 = xmppURIObject +-- .1.9.1 = attributes +-- .1.9.2 = objectclass +-- .1.9.3 = syntax + +IMPORTS + +-- from ITU-T Rec. H.350 + +h350-cr, caseIgnoreIA5Match, caseIgnoreIA5SubstringsMatch + FROM CommURI { itu-t(0) recommendation(0) h(8) 350 1 cr(1) commURI(1) +module(4) } + +-- from ITU-T Rec. X.501 | ISO/IEC 9594-2 + +ATTRIBUTE, OBJECT-CLASS, top + FROM InformationFramework {joint-iso-itu-t ds(5) module(1) +informationFramework(1) 4} + +-- from ITU-T Rec. X.520 | ISO/IEC 9594-6 + +``` + +``` + +DirectoryString {}, caseExactMatch, caseExactSubstringsMatch, caseIgnoreCaseMatch, +caseIgnoreCaseSubstringsMatch, octetStringMatch + FROM SelectedAttributeTypes {joint-iso-itu-t ds(5) module(1) +selectedAttributeTypes(5) 4} ; + +-- Attribute Type Definitions + +-- The following attribute types are defined in this document: + +-- xmppIdentityURI +-- xmppUserId +-- xmppPassword + +xmppIdentityURI ATTRIBUTE ::= { + WITH SYNTAX DirectoryString {32768} + EQUALITY MATCHING RULE caseIgnoreCaseMatch + SUBSTRINGS MATCHING RULE caseIgnoreCaseSubstringsMatch + ID { at 1 } } + +xmppUserId ATTRIBUTE ::= { + WITH SYNTAX DirectoryString {32768} + EQUALITY MATCHING RULE caseIgnoreCaseMatch + SUBSTRINGS MATCHING RULE caseIgnoreCaseSubstringsMatch + ID { at 2 } } + +xmppPassword ATTRIBUTE ::= { + WITH SYNTAX OCTET STRING + EQUALITY MATCHING RULE octetStringMatch + ID { at 3 } } + +-- Object Class Definitions + +-- The following object class is defined in this document: +-- +-- xmppURIObject + +-- xmppURIObject + +xmppURIObject OBJECT-CLASS ::= { + SUBCLASS OF { top } + MAY CONTAIN { xmppIdentityURI | + xmppUserId | + xmppPassword } + ID { oc 1 } } + +call-Id OBJECT IDENTIFIER ::= { h350-cr call-Id(9) } +at OBJECT IDENTIFIER ::= { call-Id at(1) } +oc OBJECT IDENTIFIER ::= { call-Id oc(2) } + +END -- end of ASN.1 + +``` + +# 9 DSML representation + +H.350.7 elements may be described using the Directory Services Markup Language. That description is as follows. + +``` + + + + + + xmppIdentityURI + +``` + +``` + +Labeled URI format to represent an XMPP +URI +0.0.8.350.1.1.9.1.1 +caseIgnoreCaseMatch +caseIgnoreCaseSubstringsMatch +1.3.6.1.4.1.1466.115.121.1.15 + + + + xmppUserId + Xmpp UserId + 0.0.8.350.1.1.9.1.2 + caseIgnoreCaseMatch + caseIgnoreCaseSubstringsMatch + 1.3.6.1.4.1.1466.115.121.1.15 + + + + xmppPassword + Xmpp Password + 0.0.8.350.1.1.9.1.3 + octetStringMatch + 1.3.6.1.4.1.1466.115.121.1.40 + + + + xmppURIObject + XmppURI object + 0.0.8.350.1.1.9.2.1 + + + + + + + + +``` + +## **Annex A** + +### **Indexing profile** + +(This annex forms an integral part of this Recommendation) + +Indexing of attributes is an implementation-specific activity and depends upon the desired application. Non-indexed attributes can result in search times sufficiently long to render some applications unusable. This Annex A indexing profile describes an indexing configuration for xmppIdentityURI attributes that will be optimized for efficient call server lookup. Use of this profile is optional. + +xmppIdentityURI: equality + +xmppUserId: equality + +## Appendix I + +### Electronic versions of formal definitions + +The formal definitions contained in this Recommendation are freely available in electronic format from ITU formal descriptions database at the following addresses: + +#### **LDIF definition:** + +xmppIdentity.ldif: + +#### **ASN.1 definition:** + +xmppIdentity.asn: + +#### **DSML definition:** + +xmppIdentityDSML: + +## Bibliography + +- [b-LDAP 1] HOWES (T.A.), SMITH (M.C.), GOOD (G.S.): Understanding and Deploying LDAP Directory Services, *New Riders Publishing*, 1999, ISBN: 1578700701. +- [b-LDAP 2] HOWES (T.A.), SMITH (M.C.): LDAP Programming Directory-Enabled Applications with Lightweight Directory Access Protocol, *New Riders Publishing*, 1997, ISBN: 1578700000. +- [b-IETF RFC 3921] IETF RFC 3921 (2004), *Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence*. +- [b-IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifier (URI): Generic Syntax*. +- [b-IETF RFC 3987] IETF RFC 3987 (2005), *Internationalized Resource Identifiers (IRIs)*. +- [b-IETF RFC 4422] IETF RFC 4422 (2006), *Simple Authentication and Security Layer (SASL)*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.351-200806-I_PDF-E/raw.md b/marked/H/T-REC-H.351-200806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e0fd4e510f53434895c0e612c9c863b716134b77 --- /dev/null +++ b/marked/H/T-REC-H.351-200806-I_PDF-E/raw.md @@ -0,0 +1,783 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.351** + +(06/2008) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Directory services +architecture for audiovisual and multimedia services + +--- + +**Semantic web interface for multimedia terminal +and system directories (SWIM-D)** + +Recommendation ITU-T H.351 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|--------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T H.351** + +## **Semantic web interface for multimedia terminal and system directories (SWIM-D)** + +## **Summary** + +Recommendation ITU-T H.351 describes a semantic web interface in XHTML that can be used to provide directory lookup and menu capabilities for multimedia terminals and systems. + +## **Source** + +Recommendation ITU-T H.351 was approved on 13 June 2008 by ITU-T Study Group 16 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +Address book, directory, multimedia, web interface, white pages. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|---------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 3 | +| 6 The problem of resource representations in directories..... | 3 | +| 7 SWIM-D architecture ..... | 4 | +| 8 SWIM-D directory pages..... | 6 | +| 8.1 MENU directory pages..... | 7 | +| 8.2 RESULT directory pages ..... | 9 | +| 8.3 DETAIL directory pages ..... | 11 | +| 9 SWIM-D URLs..... | 12 | +| 9.1 MENU directory page URLs..... | 12 | +| 9.2 SEARCH directory page URLs..... | 12 | +| 9.3 DETAIL directory page URLs ..... | 13 | +| 10 General considerations ..... | 13 | +| 10.1 Usage of HTTP..... | 13 | +| 10.2 Authentication and authorization ..... | 13 | +| 10.3 Directory browsing..... | 13 | +| 10.4 Directory searching ..... | 14 | +| 10.5 Extensibility..... | 14 | +| Bibliography..... | 15 | + +## Introduction + +This Recommendation describes a method by which XHTML documents can be accessed by multimedia terminals, systems, web browsers and middleware systems to recognize, navigate, process and display white pages directory structures. It addresses three primary needs: + +- **Representing both people and resources in the directory.** While people are represented in directories in well known formats, there are not good standards for representing resources in the directory, even though those resources have important contact information. For example "help desk" and "conference room 112" are important entities which may contain multimedia conferencing resources that need to be contacted. +- **Diverse display characteristics of systems.** Some multimedia terminals, such as IP telephones, have limited user interface and processing capabilities, necessitating a simplified markup scheme for displaying address books and directory information. Advanced terminals, such as web browsers or video conferencing terminals, may have rich display capabilities yet need to formulate a directory display from the same data. +- **Structured navigation.** It may be that an organization wishes to control the way that white pages applications are served out to terminals and systems. For example, an organization may wish to publish an address book that allows navigation by department, product line, or individual last name. + +## Recommendation ITU-T H.351 + +## Semantic web interface for multimedia terminal and system directories (SWIM-D) + +## 1 Scope + +This Recommendation describes a markup vocabulary for XHTML documents representing white pages directory information for multimedia terminals and systems. It describes a uniform resource locator (URL) syntax that supports directory searching. It also enumerates client and server behaviours necessary to support SWIM-D interaction effectively. The purpose of this Recommendation is to provide a framework for structured directory browsing when the underlying data structures are not known, such as when publishing directories of people, places and virtual organizations. + +This Recommendation does not describe directory structures or directory access protocols. + +This Recommendation is related to other ITU-T H.350-series Recommendations. While Recommendations ITU-T H.350.1 through H.350.7 describe directory schemas for various protocols that can drive call signalling engines directly, this Recommendation is intended for higher level access to directory data for white pages browsing only. [b-ITU-T E.115] describes a computerized directory assistance protocol for information exchange among service providers in support of assistance/inquiry services. + +White pages implementers should review all of these related Recommendations for applicability. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [IETF RFC 2616] IETF RFC 2616 (1999), *Hypertext Transfer Protocol – HTTP/1.1.* +<> +- [IETF RFC 2617] IETF RFC 2617 (1999), *HTTP Authentication: Basic and Digest Access Authentication.* +<> +- [IETF RFC 2818] IETF RFC 2818 (2000), *HTTP Over TLS.* +<> +- [IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifier (URI): Generic Syntax.* +<> +- [W3C XHTML 1.1] W3C Recommendation (2001), *XHTML™ 1.1 – Module-based XHTML.* +<> + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 cascading style sheets (CSS):** [b-W3C HTML 4.01] A simple mechanism for adding style (e.g., fonts, colours, spacing) to web documents (W3C). + +**3.1.2 extensible markup language (XML):** [b-W3C XML 1.0] A generalized text format maintained by the World Wide Web Consortium designed as a meta language to describe other markup languages. + +**3.1.3 hypertext markup language (HTML):** [b-W3C HTML 4.01] The markup language for the world wide web maintained by the World Wide Web Consortium. + +**3.1.4 lightweight directory access protocol (LDAP):** [b-IETF RFC 3377] A directory access protocol defined by the Internet Engineering Task Force to interact with X.500 directories. + +**3.1.5 XHTML:** [W3C XHTML 1.1] An XML-compliant version of HTML designed to be syntactically rigorous in order to support machine-to-machine communication. Maintained by the World Wide Web Consortium. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 client:** An agent that can access a directory page. A client can be a standard HTML browser or a SWIM-D client. + +**3.2.2 directory:** A canonical collection of attributes about people and resources in an organization, including both the enterprise directory and the endpoints directory. + +**3.2.3 directory page:** An XHTML document containing directory information. Directory pages may provide navigation, search and results in addition to other information. + +**3.2.4 directory proxy:** A web server that publishes SWIM-D directory pages. Directory proxies have deep knowledge about the directories they access, and format that information into meaningful and useful directory pages for clients. + +**3.2.5 endpoint directory:** A directory of endpoint information when that information is stored in a standalone directory, such as is the case with [b-ITU-T H.35x]. + +**3.2.6 enterprise directory:** A directory of people and resources within an organization. + +**3.2.7 resource:** A non-human entity represented in a directory that may have with it associated real-time communications account and address data. Resources may be physical, such as "conference room 12" or virtual, such as "help desk", each of which has a voice or video over IP address. + +**3.2.8 semantic web interface for multimedia directories (SWIM-D):** The interface that defines the structure of directory pages and how to access them via their uniform resource locator (URL). + +**3.2.9 SWIM-D client:** A client that is capable of understanding and interpreting SWIM-D directory pages. A SWIM-D client can be an HTML browser that has knowledge of SWIM-D, or it can be an XML-aware agent that processes directory pages for non-HTML purposes, such as an address book or auto-dialler. + +**3.2.10 SWIM-D directory page:** A directory page that is marked up using SWIM-D metadata. + +**3.2.11 SWIM-D URL:** A uniform resource locator (URL) in the format specified to support access to SWIM-D directory pages. + +**3.2.12 web browser:** A software application capable of rendering HTML and XHTML documents. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|---------------------------------------------------| +| CSS | Cascading Style Sheets | +| DNS | Domain Name System | +| HTML | HyperText Markup Language | +| HTTP | HyperText Transfer Protocol | +| LDAP | Lightweight Directory Access Protocol | +| SQL | Structured Query Language | +| SWIM-D | Semantic Web Interface for Multimedia Directories | +| URL | Uniform Resource Locator | +| XML | Extensible Markup Language | +| VoIP | Voice over Internet Protocol | + +## 5 Conventions + +In this Recommendation, the following conventions are used: + +- "Shall" indicates a mandatory requirement. +- "Should" indicates a suggested but optional course of action. +- "May" indicates an optional course of action rather than a Recommendation that something take place. + +References to clauses, annexes and appendices refer to those items within this Recommendation, unless another specification is explicitly listed. + +## 6 The problem of resource representations in directories + +In applications such as voice over IP, video conferencing and instant messaging it is sometimes desirable that many different types of resources have communication accounts. Some examples are listed below: + +- **People:** People may have a SIP or H.323 account which they use for voice over IP. +- **Conference rooms:** Conference rooms may exist which contain H.323 video conferencing equipment to allow for collaboration. +- **Classrooms:** Classrooms may have several different types of audio and video conferencing equipment all operating simultaneously, such as SIP audio conferencing and H.323 video conferencing. +- **Surveillance sites:** H.323, SIP or other remote observation cameras may be deployed throughout an organization to which security staff can connect for remote observation. +- **Medical equipment:** A medical cart may contain multimedia conferencing equipment, along with medical diagnostic equipment. This cart may be mobile and be checked out many times per day and used throughout a hospital. +- **Virtual organizations:** It is desirable for a hospital to be able to publish separate numbers for "main hospital number", "emergency", "paediatrics", "paediatric nursing", and "paediatric doctor on call". Each of these virtual organizations may have a VoIP account + +which is published in both printed and on-line directories, and for which exists unique and complex forwarded and call preference information. + +Ideally, standardized definitions would exist for all resources and virtual organizations. Unfortunately, the diversity of real-world applications makes it impractical to create these standardized definitions. As a result directory schemas such as [b-ITU-T X.500] are specifically constructed to be extensible to allow for this customization. Thus, while *inetOrgPerson* is a widely used class to represent people, it is often extended to incorporate custom attributes required for an enterprise. + +While resources cannot practically be standardized, it is still important that multimedia conferencing applications have knowledge of the types of resources available so that they can be searched and managed. For example, a video conferencing management application might need to display a list of all video room systems. Similarly, a user might wish to search for conference rooms within a particular building that have conferencing capabilities. A white pages application may allow a user to search for "paediatric doctor on call" without knowing precisely which doctor is on call at any given time. A printed directory application may need to print an entire listing of virtual organizations and people to create a paper phone book. + +Applications that access the directory directly, such as those that use H.350, must have direct knowledge of the representation of data in the directory. Specifically, they must be aware of the schemas used to represent people and resources. This is necessary for call signalling and identity management applications. Other applications, such as generic white pages that access inter-domain directories, may not be able to be easily configured for such schema knowledge. + +SWIM-D provides a solution for this problem by defining an XHTML interface to a directory proxy that possesses deep knowledge of the directory. Because the directory proxy manages the complexity of the underlying directory, clients and third party systems can access directory data through the directory proxy simply by browsing SWIM-D directory pages, either with a standard HTML client, or a SWIM-D client that conforms to the SWIM-D markup specifications. + +## 7 SWIM-D architecture + +SWIM-D provides a mechanism by which organizations can publish directory pages that allow users to recognize, navigate, process and display white pages directory structures. + +Figure 1 shows a functional diagram of a complete SWIM-D system. + +![Figure 1 – SWIM-D architectural components diagram](54fabc351eda5228d2fa28cd9ba07971_img.jpg) + +The diagram illustrates the SWIM-D architectural components. On the left, a yellow octagon labeled 'Client' is shown. A dashed box labeled 'SWIM-D' contains two arrows: a blue arrow pointing right labeled 'URL' and a blue arrow pointing left labeled 'Directory Page'. In the center, a purple rounded rectangle labeled 'Directory Proxy' is connected to the SWIM-D box. Below the Directory Proxy, the text 'Directory Access Protocol' is written. On the right, a dashed box labeled '"The Directory"' contains two stacked cylinders: a light blue one labeled 'Enterprise Directory' and a dark blue one labeled 'Endpoint Directory'. A double-headed blue arrow connects the Directory Proxy to the 'The Directory' box. + +Figure 1 – SWIM-D architectural components diagram + +Figure 1 – SWIM-D architectural components + +The **directory** in this example comprises the complete set of directory information used to represent people, resources and endpoints. In many cases, it will consist of an extant enterprise directory along with an associated H.350 directory describing all subscribers and their endpoint information. In other cases, it may represent a proprietary directory type with custom attributes, such as a corporate directory with an extended LDAP schema with endpoint information directly in the people or resource objects. + +The **directory access protocol** is the protocol used to communicate between the directory and the directory proxy. In the case of H.350, it will be LDAP. However, it could be a structured query language (SQL) call or some other protocol. In most cases, there should be a trust relationship between the directory and the directory proxy. This Recommendation does not specify or even require the use of a directory access protocol, though one will be present in many applications. + +The **directory proxy** is a web server that has knowledge, by discovery or configuration, of the directory. It is intended to be straightforward in design, so that it can be easily implemented by an enterprise with knowledge of its own directory structure. It understands the schemas used by the directory to represent people, resources and endpoints and how to search the directory. The directory proxy provides a mapping function between the vocabulary used in the directory schemas and SWIM-D directory pages served out to clients. The directory proxy should authenticate all communications with the directory and with clients. Communications between the directory proxy and the directory and clients should be encrypted. Note that a directory proxy is not required to use a directory access protocol, though it is intended to do so. It could instead serve static SWIM-D directory pages. + +**SWIM-D** is an XHTML over HTTP(S) interface that clients use to access directory information from the directory proxy. SWIM-D describes two elements: **directory pages** and the **SWIM-D URL**. Directory pages are XHTML documents encoded using the metadata described in this Recommendation. These directory pages represent the white pages that users view. The SWIM-D URL is a URL format for directly accessing directory pages and for transmitting information to them to support searching and navigation operations. + +A **client** is any system that accesses directory information through the directory proxy using its SWIM-D. Typically, this will be an IP telephone, video terminal, soft client or white pages web application. There is a great degree of variability in the display capabilities of each of these devices. For example, a mobile phone may have an extremely limited display. A video terminal may have a large and colourful display, but may not be well suited for small text. A soft client may be capable of very rich display functions. A white pages application may be a simple web lookup service, or could be an application intended to produce output for eventual printing, such as business cards or telephone books. SWIM-D is intended to provide the directory information and the associated metadata for each of these devices to be able to display the information in the manner most appropriate to the application. Thus, a client can be an HTTP web browser, or an XML-enabled software application capable of interpreting SWIM-D data and metadata. + +It is a goal of the overall system design that a single directory proxy will provide information to many different endpoint types, so that a variety of clients from multiple vendors and for multiple applications can be supported from a single interface and with a single system. + +Because SWIM-D is a simple HTTP(S) interface, it can be easily implemented on a variety of client types. This architecture simplifies the client's access to the directory because the client does not need to have knowledge of the directory access protocol or the directory itself. This work is off-loaded to the directory proxy. + +**Note on backward compatibility and accessibility:** Because SWIM-D uses XHTML, web browsers that have no knowledge of SWIM-D can still render basic SWIM-D directory pages. This also means that accessibility tools, such as screen readers and speech synthesizers, can operate on SWIM-D directory pages. HTML accessibility guidelines can be supported as well. + +## 8 SWIM-D directory pages + +A SWIM-D directory page consists of metadata describing the page and elements that describe the data contained in the page. There are three types of SWIM-D directory pages: + +- **MENU directory page.** A navigational page that may contain menu options and a search function. MENU pages can be used to construct controlled navigation options for end users. For example, menu options for "sales", "repair" and "customer service" along with a search function for staff member names could represent a useful navigational page for customers. +- **RESULT directory page.** A summary page returned after a search function is executed. RESULT pages display a list of all the elements that match the search and allow the client to choose among them to further refine the search. For example, searching for "Smith" may return a RESULT page containing all individuals in the directory with last name "Smith". The user can then choose which "Smith" is desired. +- **DETAIL directory page.** A page containing detailed information about a specific directory entry. For example, a DETAIL page might contain all information about an individual, including first name, last name and contact information. + +SWIM-D directory pages are intentionally limited in scope to be simple, relatively atomic and single purpose as an aid to support by devices with limited display, memory and processing capabilities and to be backward compatible with non-SWIM-D web browsers. However, advanced applications can be accomplished by powerful clients by combining SWIM-D pages into a single display element. For example, a full display of all users with a last name of "Smith" can be constructed by first obtaining the RESULT page for that search, obtaining the DETAIL page for each entry, and combining that data into a single display. This multiple search capability is non-normative and is up to the implementer as it depends on the capabilities of the client. + +SWIM-D directory pages may contain in-line CSS data to represent a style sheet for display purposes. Clients may and generally will provide their own client-side style sheet or equivalent functionality to match SWIM-D elements to the display capabilities and preferences of the clients. + +SWIM-D defines the following XHTML *class* values to be used to establish a display priority level for marked up data. These values may be interpreted by clients with limited display capability to determine which elements to display and which to ignore. For example, a client with a single line display may be configured to only display elements whose priority equals 1. Note that more than one element may be of a particular class. It is not the responsibility of the directory page to map priorities to display capabilities. Rather, the directory page indicates the relative importance of items it contains, and the SWIM-D client determines how it will display (or not) these items. + +Table 1 shows the XHTML class values that may be used to represent priority. In order to be explicit about describing priority elements, class values shall only be expressed in specific locations within the markup, as described in clauses 8.1, 8.2 and 8.3. Specifically, a SWIM-D element may have a priority attribute only if explicitly stated. + +**Table 1 – Priority class values** + +| Class value | Purpose | +|--------------------|--------------------------------------------------------------------------| +| [h.351.priority_1] | Indicates that an element has display priority 1 (the highest priority). | +| [h.351.priority_2] | Indicates that an element has display priority 2. | +| [h.351.priority_3] | Indicates that an element has display priority 3. | +| [h.351.priority_4] | Indicates that an element has display priority 4. | +| [h.351.priority_5] | Indicates that an element has display priority 5. | +| [h.351.priority_6] | Indicates that an element has display priority 6. | +| [h.351.priority_7] | Indicates that an element has display priority 7. | +| [h.351.priority_8] | Indicates that an element has display priority 8 (the lowest priority). | + +SWIM-D directory pages contain the following metadata elements: + +``` + +``` + +The `h.351_version` property identifies that the directory page is an H.351 page and the version of H.351 supported is version 1.0. + +### 8.1 MENU directory pages + +A MENU directory page contains metadata to indicate that it is a SWIM-D MENU directory page. It also contains SEARCH and MENU\_LINK elements. + +A start directory page is a special case of a MENU directory page that serves as the entry point for SWIM-D browsing. The URL of the start directory page is the only URL that has to be known by the client in order to use the SWIM-D service. It has to be configured on each client and represents a "home" page for that CLIENT. Start page is a non-normative term and is only meant as a convenience and convention. + +#### 8.1.1 Metadata + +A MENU directory page contains the following metadata elements: + +``` + +``` + +The `h.351v1.0` property identifies the page as being of type H.351 SWIM-D and the content indicates that it is a MENU directory page. + +#### 8.1.2 Elements + +A MENU directory page contains one SEARCH, or one MENU\_LINKS element, or one of both. A CLIENT uses the directory page elements to render a search mask or a navigational menu, respectively. + +##### 8.1.2.1 SEARCH elements + +A SEARCH element is an XHTML *forms* construct of one or more XHTML form controls that can be used by the client to create a directory search mask. Each form control has a NAME, a LABEL and a VALUE. + +- **NAME:** The control name of type TEXT signified by the XHTML *name* element. The name shall be a string that is equivalent to the search variable name that the server expects for a query operation. +- **LABEL:** The LABEL is the XHTML *label* element and is used by the client to label the search fields for display purposes. LABEL is used with *for* and *id* elements to associate the label with a particular form NAME as specified in [W3C XHTML 1.1]. + +- **VALUE:** The VALUE is the text entered by the user, and is not included in the markup of a SEARCH element, but is used to construct the SEARCH MASK in the SWIM-D directory page URL as described in clause 9. + +SEARCH elements may have a priority class assigned. Priority is assigned to individual form controls, not to the entire form. + +The following values of *class* are defined for search elements: + +| class value | Purpose | +|--------------------|--------------------------------------------| +| [h.351.search] | Indicates that a form is a search element. | + +##### 8.1.2.2 MENU\_LINK elements + +A MENU\_LINK element is an *unordered list* of one or more MENU\_LINK definitions that include hyperlinks to directory pages. A MENU\_LINK definition consists of exactly one link label and URL pair. + +MENU\_LINK definitions may have a priority class assigned. + +The following values of *class* are defined for MENU\_LINK elements: + +| class value | Purpose | +|-------------------------|------------------------------------------------------------------------| +| [h.351.menu_link] | Indicates that a label/value pair is a menu link element. | +| [h.351.menu_link_label] | Indicates a label that can be used for user-friendly display purposes. | +| [h.351.menu_link_url] | Indicates a value for the entry detail. Typically, a SWIM-D URL. | + +##### Example MENU directory page + +``` + + + + + + SWIM-D Menu Directory Page Example + + + + + + + +

Customer Service Directory

+ + + +

Search for an Individual

+ +
+

+ +
+ +
+ +

+
+ + + + +``` + +### 8.2 RESULT directory pages + +A RESULT directory page contains a table of the search results, allowing the user to further refine the search. + +#### 8.2.1 Metadata + +A MENU directory page contains the following metadata elements: + +``` + + + + + + +``` + +The `h.351` property identifies the page as being of type H.351 SWIM-D and the content indicates that it is a RESULT directory page. + +The `h.351_result_totalnum` property identifies that the search resulted in [integer] results, though not all of them are necessarily contained on the page. + +The `h.351_result_startnum` property states that the entries contained on the page begin at number [integer] of the entire set of results. + +The `h.351_result_listnum` property states that the page contains [integer] results. + +Taken together, the totalnum, startnum and listnum elements can be used to create both client side and server side navigational aides for content browsing, such as the following page display fragment: + +``` +<< 1 2 3 4 5 >> +``` + +#### 8.2.2 RESULT element + +A RESULT element is a *table* representing the result of a directory search operation. A directory entry line contains summary data and a hyperlink pointing to the entry's detail directory page. The number of columns and rows returned is determined by arguments in the search URL. Elements marked with `` and `` tags identify column labels for non-HTML clients. + +Priority may be assigned to table columns. + +The following values of *class* are defined for entry detail elements: + +| class value | Purpose | +|--------------------|---------------------------------------------------| +| [h.351.detail_url] | Indicates that an element is a SWIM-D detail URL. | + +##### Example results directory page + +``` + + + + + + SWIM-D Results Directory Page Example + + + + + + + + + + +

Search Results

+ + + + + + + + + + + + + + + + + + + + + + +
Last NameFirst NameMore Info
SmithJohn + show details
SmithKimberly + show details
SmithLiam + show details
+ + + +``` + +### 8.3 DETAIL directory pages + +A DETAIL directory page displays full details of a directory entry. + +#### 8.3.1 Metadata + +A MENU directory page contains the following metadata elements: + +``` + +``` + +#### 8.3.2 DETAIL element + +An *unordered list* of one or more directory entry elements. An entry detail element contains exactly one label and value pair. + +Priority may be assigned to list items. + +The following values of *class* are defined for entry detail elements: + +| class value | Purpose | +|----------------------------|------------------------------------------------------------------------| +| [h.351.entry_detail] | Indicates that a label/value pair is an entry detail element. | +| [h.351.entry_detail_label] | Indicates a label that can be used for user-friendly display purposes. | +| [h.351.entry_detail_value] | Indicates a value of the entry detail. Typically, a search result. | + +NOTE – In the following example, the text: + +``` +:  +``` + +is used to denote a separator to display, for example: + +``` +Last Name: Smith +``` + +This Recommendation does not define XHTML markup for display purposes. Implementers could choose, for example: + +``` +  +``` + +to generalize the markup for more advanced display options, such as supporting international customization. + +##### Example DETAIL directory page: + +``` + + + + + + SWIM-D Detail Directory Page Example + + + + + + + +

Contact Details

+ +
    +
  • + Last Name:  + Smith +
    • +
+ + +``` + +``` + +
  • + FirstName + :  + John +
    • +
  • + Address:  + + + sip:John_Smith@example.com +
    • + + + + + +``` + +## 9 SWIM-D URLs + +A directory page is uniquely identified by its URL, and a client navigates through directory pages using URL hyperlinks included in the pages. The general syntax of a directory page URL follows the HTTP URI scheme as defined in [IETF RFC 2616] and the HTTPS URI scheme as defined in [IETF RFC 2818]. Both absolute and relative URLs shall be supported by clients and directory proxies. + +There are three types of SWIM-D URLs: + +- **MENU directory page URL.** Instructs the directory proxy to return a MENU directory page. +- **SEARCH directory page URL.** Instructs the directory proxy to return a RESULT directory page. +- **DETAIL directory page URL.** Instructs the directory proxy to return a DETAIL directory page. + +### 9.1 MENU directory page URLs + +The format of a **MENU directory page URL** is defined as: + +``` +http(s): +``` + +- **** The fully qualified hostname of the directory proxy. In case the directory proxy has no DNS entry, an IPv4 or IPv6 address may be used. +- **** This path uniquely identifies a MENU directory page. It consists of path fragments separated by the "/" character similar to a file system path. The directory page path can be an empty string. + +### 9.2 SEARCH directory page URLs + +The format of a **SEARCH directory page URL** is defined as: + +``` +http(s): ? a=search + [ & = ]* + [ & maxcolumns= ] + [ & maxrows= ] + [ & startnum= ] +``` + +- **, ** + +The equals a NAME element from a menu directory page form element. is the value entered by a user in the directory search mask. Required. + +#### – **** + +This value specifies the maximum number of columns that should be returned by the directory proxy. + +#### – **** + +This value specifies the maximum number of rows, representing individual directory search results, that should be returned by the directory proxy. + +#### – **** + +A client can use this parameter to tell the directory proxy the desired result set index. This allows to page through a set of resulting directory entries. + +### 9.3 DETAIL directory page URLs + +The format of a **DETAIL directory page URL** is defined as: + +http(s): +[filename] &or ? [selection\_filter] + +#### – **** + +The name of the detail directory page, such as smith\_liam.html. More typically, a selection filter will be used instead of a specific filename. + +#### – **** + +This optional string is defined and generated by the directory proxy and is used to pass specific variable names between the client and directory proxy. See the results directory page example for an example of this syntax. + +## 10 General considerations + +### 10.1 Usage of HTTP + +A directory proxy shall support both HTTP and HTTP over TLS (HTTPS) following the procedures in [IETF RFC 2818]. Furthermore, a directory proxy shall be able to enforce HTTPS even if a client tries to connect via HTTP. A client should implement HTTPS as specified in [IETF RFC 2818] and use it as the default transport protocol. A client may use HTTP if client resources do not allow for TLS encryption. + +### 10.2 Authentication and authorization + +HTTP digest access authentication as defined in [IETF RFC 2617] is used for client authentication. The directory proxy authorizes a client based on the credentials used during the digest authentication process + +### 10.3 Directory browsing + +To begin the browsing process, a client issues an HTTP GET request with the SWIM-D start directory page URL. A client may use another SWIM-D directory page URL stored locally on the client. This URL can be configured through client provisioning or saved as a bookmark hyperlink by the user. Once the client receives a valid directory page, it uses the page elements to render the directory user interface. + +If the returned directory page includes a SEARCH element, a client with a user interface should render a directory search mask including at least the default search field definition. This search mask MUST allow a user to enter search values according to the SEARCH definitions and to perform a directory search operation. + +If a MENU\_LINKS element is returned, a client with a user interface should present the included hyperlinks to the user and offer a way to select one of the hyperlinks. Selecting a hyperlink shall result in a new SWIM-D request using the selected hyperlink. The client shall execute the rules specified in this clause once a new directory page is returned. + +### 10.4 Directory searching + +A client uses the SEARCH directory page element to render a directory search mask as defined in clause 8.1.2.1. A directory search operation is performed by issuing a new SWIM-D request with a SEARCH directory page URL. This URL shall comply with the SEARCH directory page URL format and is constructed by the following rule: + +- 1) Take the current SWIM-D URL and remove any query terms. +- 2) Add the query term `a=search`. +- 3) If a user has entered values in the directory search mask, add a query term `=` for each search value. +- 4) Optionally, add `maxcolumns=`, `maxrows=` and/or `startnum=`. + +An example SEARCH directory page URL looks like: + +`https://dir.example.com/hr?a=search&fname=peter&sname=smith` + +Note that this process is an implementation of XHTML forms as described in [W3C XHTML 1.1]. Clients may use HTTP GET or HTTP POST methods, but generally should use GET for read-only applications. + +After issuance of a directory search request to a directory proxy, the directory proxy must return a corresponding result directory page. + +### 10.5 Extensibility + +XHTML is designed to be stably extensible and SWIM-D supports this extensibility in the following ways: + +- Implementers may create their own class definitions for use in SWIM-D directory pages. The name space for these extensions shall not conflict with classes already defined for SWIM-D in this Recommendation. As is the case for HTML browsers, non-HTML SWIM-D clients should ignore class definitions that they do not recognize. Thus, proprietary extensions should be ignored by, but not be broken by, unrecognizable attributes and attribute values. +- Implementers may create their own `` tags and assign values to them. The name space for these `` elements shall not conflict with elements already defined for SWIM-D in this Recommendation. +- Implementers may not alter the URL syntax of SWIM-D. + +## Bibliography + +- [b-ITU-T E.115] Recommendation ITU-T E.115 (2007), *Computerized directory assistance*. +- [b-ITU-T H.323] Recommendation ITU-T H.323 (2006), *Packet-based multimedia communications systems*. +- [b-ITU-T H.35x] Recommendation ITU-T H.35x-series (2003), *Directory services architecture for multimedia conferencing*. +- [b-ITU-T X.500] Recommendation ITU-T X.500 (2005) | ISO/IEC 9594-1:2005, *Information technology – Open Systems Interconnection – The Directory: Overview of concepts, models and services*. +- [b-IETF RFC 3261] IETF RFC 3261 (2002), *SIP: Session Initiation Protocol*. +<> +- [b-IETF RFC 3377] IETF RFC 3377 (2002), *Lightweight Directory Access Protocol (v3): Technical Specification*. +<> +- [b-IETF RFC 4510] IETF RFC 4510 (2006), *Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map*. +<> +- [b-W3C HTML 4.01] W3C Recommendation (1999), *HTML 4.01 Specification*. +<> +- [b-W3C XML 1.0] W3C Recommendation (2008), *Extensible Markup Language (XML) 1.0*. +<> + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/0b0dbdb00519a67d96c812ee07da3a1e_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/0b0dbdb00519a67d96c812ee07da3a1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbcf82a5141dcc6c512da9194ad5ab3cdeaf1e81 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/0b0dbdb00519a67d96c812ee07da3a1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f89663bc1c550b1cc3e9fefdcd0563c66dbc24902b4a1451d88b188b56a9a23b +size 9242 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40be35b6494f2518cfaa03a840c46992cb67cb05 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f5916eebb3f8c99790142854d453f2272d8fe6df5d58cc44b0326b13744f1ea +size 57622 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd1264bb8ab50d80c07b10873ff6eb6723e608bc --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b1727df9b67b1218a6dadbdf43d2ace9c12f63c725b21b08060f8b3e34266f0 +size 56585 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e3f230548596fac41279cbcf18230beba64819a --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2687060940a2cdb766d06ec62d328d9fe658dbce51c500254a799f1dda28e3cf +size 40004 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5044b91ef6257b343d02ce982d4b36f92b391fc8 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa95718ba9f4e07a1c49694da52ac4d495b41be0aaee6fd03b2361a5d9d27ae7 +size 35672 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b6f0f1694daa199ef5fac61721addf454c29aa0 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c83a97747549d2d7a28b14427658c3bd2b3ad6295e8d9725952c2eaeb7b64458 +size 26150 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca6c9d5efa4de468960bc340c3a733b84afdc629 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fa2ed1a3a94dbc4aadb418e4f01e592cdb13364863a433d8eba4378fe31b33a +size 38937 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9ae989e71058ebded277122af26e5c29fb5eb41 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bfdc3bd08a8d2903c1eaa01b254e8a6a88944780af50f05a131eb5d4c5df36f +size 38725 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97781b2e08da3ef4e56cd8006ea514125288d939 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c78b17028e2a14f8dd22a11261a0a440dde2635a1554c39689bd83c668009ed2 +size 53062 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75d1ad4b62faee29a283b94b7a1efe32184b3ceb --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15b7bd674b9ed96a85fd1a1bbfbe72a6b33aa4b984d4cfa880545017e75cc904 +size 54243 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6a48ada1d0767348bb3ee0f076617bb6b869885 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92f5b4522e8e71992d746f8dcdbf4a1dc6887c8d751bfb25c6e5f95895d411cc +size 37566 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc881f270fe392e07bdd2cff2e0cf6255a36c6ac --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da32188f6e43090de21d84c306ef31d3d9a0713407302cbb2144f6d742a57b9d +size 36375 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c3cf8f141c87d90fd7329bcae06993da0dd6ee8 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efd499a805651bab98e6cdfd16c1ae59c404148b63afa69d994d77d1db29bcbe +size 35548 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6920a2f9fbce4a1c85ecac245550b01968ab96f5 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:786c18cca47b3c76ce0bfbfcbe1b3216cb0a8189dd4f5be19a3aa9936174a5d8 +size 140021 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c54276ece164ee6011a81c0e6069e0f592a7a8a --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f7ea703ff263d51a545a7a790e65e28257916c8a16dcc089d345f7f1478fd86 +size 55220 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.360-200403-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eec82ea066689a0476841f26e37afa1e38240ea1 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53c1e3305b319427d3f3911a96960648a56841661dd771835b4340a846c09106 +size 45836 diff --git a/marked/H/T-REC-H.360-200403-I_PDF-E/raw.md b/marked/H/T-REC-H.360-200403-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..05e222d268ea8428eb06ea8409c8f544ccb02e99 --- /dev/null +++ b/marked/H/T-REC-H.360-200403-I_PDF-E/raw.md @@ -0,0 +1,628 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.360** + +(03/2004) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Quality of service +architecture for audiovisual and multimedia services + +--- + +**An architecture for end-to-end QoS control and +signalling** + +ITU-T Recommendation H.360 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|--------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.360** + +# **An architecture for end-to-end QoS control and signalling** + +## **Summary** + +End-to-end quality of service (QoS) and service priority require coordination of resources and quality control mechanisms at all points in a multimedia system. Procedures for achieving this entail a combination of information flows and functionality at various levels in the system. This Recommendation provides a reference architecture for defining and analysing mechanisms and procedures for achieving end-to-end QoS and service priority control. + +###### **Source** + +ITU-T Recommendation H.360 was approved on 15 March 2004 by ITU-T Study Group 16 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 2.1 Normative references..... | 1 | +| 2.2 Informative reference ..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Generic QoS architecture..... | 3 | +| 5.1 Functional planes..... | 3 | +| 5.2 Decomposition of MM systems into administrative domains..... | 4 | +| 5.3 QoS classification at service, application and network levels..... | 4 | +| 5.4 QoS budgets..... | 6 | +| 5.5 Functional entities and reference points ..... | 7 | +| 6 QoS control and signalling procedures..... | 9 | +| 6.1 General framework..... | 9 | +| 6.2 Classification of QoS signalling types ..... | 10 | +| 6.3 QoS signalling procedures..... | 13 | + + + +# An architecture for end-to-end QoS control and signalling + +# 1 Scope + +This Recommendation contains a reference architecture for controlling the QoS and service priority of multimedia services in networks which are comprised of combinations of switched circuit and packet domains, wireless and wireline technologies, and conventional and packet-based terminals. The reference architecture is functionally defined. This Recommendation uses a domain-based approach which allows issues of administrative control and security also to be considered. + +This Recommendation is concerned with end-to-end QoS control in multimedia systems made up of multiple and disparate administrative domains and QoS mechanisms. Detailed mechanisms for generic QoS control in individual networks are not described here but may be found in ITU-T Y-series Recommendations. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +## 2.1 Normative references + +- ITU-T Recommendation G.1010 (2001), *End-user multimedia QoS categories*. +- ITU-T Recommendation M.2301 (2002), *Performance objectives and procedures for provisioning and maintenance of IP-based networks*. +- ITU-T Recommendation Y.1540 (2002), *Internet protocol data communication service – IP packet transfer and availability performance parameters*. +- ITU-T Recommendation Y.1541 (2002), *Network performance objectives for IP-based services*. + +## 2.2 Informative reference + +- IEEE Standard 802.1D-1998, *Information technology – Telecommunications information exchange between systems – Local and metropolitan area – Common specifications: Media access control (MAC) bridges*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 application service:** A network-based service involving the transmission and/or processing of multimedia information. + +**3.2 Application Service Provider (ASP):** A Service Provider providing Application Services. + +NOTE – The same business entity may act as both Network Operator and Application Service Provider. + +**3.3 end user:** An entity employing Application Services. + +- 3.4 End User Domain (EUD):** A collection of physical or functional entities, including terminal equipment and network resources under the control of an End User. +- 3.5 Interconnect Function (ICF):** A functional entity that interconnects Network Operator Domains. It provides a policy and/or administrative boundary and may police authorized media flows between two Network Operator Domains to ensure they are consistent with the QoS policies of the Network Operator of that domain. +- 3.6 network operator:** An administrative entity operating a network. +- 3.7 Network Operator Domain (NOD):** A collection of network resources sharing a common set of policies, QoS mechanisms and technologies under the control of a Network Operator. +- 3.8 Network Policy Entity (NPE):** A functional entity residing in a Network Operator Domain that maintains the policies of the Network Operator. +- 3.9 Quality-of-Service Manager (QoSManager):** A functional entity residing in a Service Domain that mediates requests for end-to-end QoS in accordance with policies of the Application Service Provider controlling the Service Domain. It communicates with other QoSManagers and with RMs to determine, establish and control QoS. +- 3.10 Quality-of-Service Policy Entity (QoSPE):** A functional entity residing in a Service Domain that manages the QoS policies of the Application Service Provider controlling the Service Domain. It provides authorization of permitted and default QoS levels. It receives requests from and issues responses to QoSManagers to establish the authorized end-to-end QoS levels. +- 3.11 Service Domain (SD):** A collection of physical or functional entities offering Application Services under the control of an Application Service Provider which share a consistent set of policies and common technologies. +- 3.12 Resource Manager (RM):** A functional entity residing in a Network Operator Domain that applies a set of policies and mechanisms to transport resources within the domain to enable specified QoS levels to be achieved within the domain. +- 3.13 Transport Functionality (TF):** A functional entity representing the collection of transport resources within a Network Operator Domain. +- 3.14 User Equipment (UE):** Equipment under the control of an End User. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations: + +| | | +|----------|--------------------------------| +| ASP | Application Service Provider | +| COPS | Common Open Policy Service | +| DiffServ | Differentiated Services | +| EUD | End User Domain | +| ICF | Interconnect Function | +| IntServ | Integrated Services | +| MM | MultiMedia | +| MPLS | Multi-Protocol Label Switching | +| NOD | Network Operator Domain | +| NPE | Network Policy Entity | +| QoS | Quality of Service | + +| | | +|-------|-----------------------------------| +| QoSM | Quality-of-Service Manager | +| QoSPE | Quality-of-Service Policy Element | +| QST | QoS Signalling Type | +| RM | Resource Manager | +| RSVP | Resource ReSerVation Protocol | +| SD | Service Domain | +| TF | Transport Functionality | +| UE | User Equipment | + +# 5 Generic QoS architecture + +## 5.1 Functional planes + +To achieve end-to-end QoS control in multimedia (MM) systems, the QoS mechanisms operating in the multimedia application must operate together with the QoS mechanisms operating in the packet-based network (e.g., RSVP, DiffServ, MPLS, etc.) which are generic and independent of the application. Furthermore, network management mechanisms may also be involved in controlling and managing QoS. Figure 1 illustrates the relationship between a number of functional planes within which QoS mechanisms reside. + +![Figure 1/H.360 – Relationship between MM application, packet-based network, management, and circuit-switched planes. The diagram shows a 3D perspective view of four planes. The 'Management plane' is a vertical plane on the left. The 'Circuit-switched plane' is a horizontal plane at the top. The 'MM application plane' and 'Packet-based network plane' are horizontal planes stacked vertically in the middle. The label 'H.360_F01' is in the bottom right corner.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +Figure 1/H.360 – Relationship between MM application, packet-based network, management, and circuit-switched planes. The diagram shows a 3D perspective view of four planes. The 'Management plane' is a vertical plane on the left. The 'Circuit-switched plane' is a horizontal plane at the top. The 'MM application plane' and 'Packet-based network plane' are horizontal planes stacked vertically in the middle. The label 'H.360\_F01' is in the bottom right corner. + +**Figure 1/H.360 – Relationship between MM application, packet-based network, management, and circuit-switched planes** + +### 5.1.1 MM application plane + +Within this plane, QoS parameters specific to the MM application (e.g., QoS service class) are requested, authorized, signalled, monitored and controlled. + +### 5.1.2 Packet-based network plane + +Within this plane, general non-application specific traffic parameters effecting QoS (e.g., end-to-end delay, delay variation (jitter), packet loss, and bandwidth) must be controlled and accounted to achieve the QoS requirements requested by the MM application. This plane may be based on IP, MPLS, or other technologies. With connection-oriented MPLS networks, it may be possible to support some QoS services with greater efficiencies than connectionless IP networks. + +### **5.1.3 Circuit-switched plane** + +Within this plane, every call receives the same level of quality. Circuit-switched networks only provide a choice of call acceptance or non-acceptance depending upon the requested and available capacities. Once a call has been accepted, the capacity allocated is constant throughout the connection duration. Circuit-switched networks are engineered to provide acceptable quality levels for interactive communications. Transmission planning guidelines will determine the levels of quality achievable in circuit-switched environments. + +### **5.1.4 Management plane** + +Within this plane, QoS signalling statistics are exchanged with the MM Application Plane and Packet-Based Network Plane. This signalling will include call statistics, network utilization information, network configuration, performance monitoring, and network resource allocation. + +## **5.2 Decomposition of MM systems into administrative domains** + +An MM system will in the general case be made up of a number of separate Administrative Domains, each representing the domain of control of an MM End-User, Application Service Provider or Network Operator. + +### **5.2.1 End user domains** + +An End User Domain is a collection of physical or functional entities, including terminal equipment and network resources under the control of an End User. The End User may be an individual or administrative entity employing Application Services. + +### **5.2.2 Service domains** + +A Service Domain is a collection of physical or functional entities offering Application Services under the control of an Application Service Provider which share a consistent set of policies and common technologies. An MM system will in the general case be made up of a number of separate Service Domains. + +### **5.2.3 Network operator domains** + +A Network Operator Domain is a collection of network resources sharing a common set of policies, QoS mechanisms and technologies under the control of a Network Operator. An MM system will, in general, be made up of a number of separate Network Operator Domains. Network Operator Domains consist largely of transport-related functionality; this includes IP routers, ATM/MPLS switches; however, they may contain application-based elements such as NATs, firewalls, etc. Each Network Operator Domain may have its own QoS policies and/or differ from other domains in terms of administrative control (e.g., Network Operator), QoS mechanisms (RSVP/IntServ, DiffServ, MPLS, etc.), access, metering, addressing schemes (global, local), network protocol (IPv4 or IPv6), etc. + +## **5.3 QoS classification at service, application and network levels** + +A single application such as videoconferencing, telephony, or web browsing can be made of many unique media streams. To provide maximum flexibility and network optimization, not all media streams from one application have to be tagged with the same classifications. Each media stream of an application may be uniquely classified by a priority level as well as a QoS Service Class as shown in Figure 2. + +![Diagram of QoS classification at service, application and network levels. It shows a flow from Service application (Service components: Voice, Video, Data) to QoS service class (A, B, C) to Specific application implementation factors (e.g., Codec selection & packetization jitter buffer design) to Network (Traffic Class A, B, C).](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +**Service application** + +Service components: Voice, Video, Data (Single application) + +QoS service class A, B, C + +Specific application implementation factors (e.g., Codec selection & packetization jitter buffer design) + +QoS traffic parameter or traffic class selection: Traffic Class A, B, C + +**Network** + +Other traffic parameters that are not depicted may be required. + +**Applications:** +Telephony +Videoconferencing +Web browsing +Streaming audio/video + +**QoS Service class & priority** + +**Voice** +**Traffic Class A** (e.g., Y.1541 Class 0) +**or** +**Network QoS parameters** +Maximum delay = (value 1)      Maximum packet loss = (value 2) +Mean delay variation = (value 3)      Maximum bit error rate = (value 4) +Prioritization = (value 5) + +**Video** +**Traffic Class B** (e.g., Y.1541 Class 0) +**or** +**Network QoS parameters** +Maximum delay = (value 6)      Mean delay variation = (unspecified) +Maximum packet loss = (value 7)      Prioritization = (value 8) +Maximum bit error rate = (value 9) + +**Data** +**Traffic Class C** (e.g., Y.1541 Class 5) +**or** +**Network QoS parameters** +Maximum delay = (unspecified)      Mean delay variation = (unspecified) +Maximum packet loss = (unspecified) +Maximum bit error rate = (unspecified) +Prioritization = (value 10) + +H.360\_F02 + +Diagram of QoS classification at service, application and network levels. It shows a flow from Service application (Service components: Voice, Video, Data) to QoS service class (A, B, C) to Specific application implementation factors (e.g., Codec selection & packetization jitter buffer design) to Network (Traffic Class A, B, C). + +**Figure 2/H.360 – QoS classification at service, application and network levels** + +### 5.3.1 Service and application levels + +Any specific application can be broken down into multiple data streams. Each data stream or service component shall be classified into a QoS Service Class. + +#### 5.3.1.1 QoS service classes + +When defining QoS service classes for multimedia applications, it may be useful to define these in terms of traffic characteristics required for different applications. ITU-T Rec. G.1010 defines a number of multimedia application types in this way. + +For a certain QoS service class, at least three parameters including delay, delay variation, and packet loss should have a defined value. For each QoS parameter, the values, when bounded, are restricted on just one direction and can vary arbitrarily. For example, delay should not be larger than the agreed value, and IPDV in ITU-T Rec. Y.1541 should not exceed the requested value. + +NOTE – The statistics of packet loss will need to be accurately defined in order to fully specify the performance of the packet-based network. For example, there are two different types of packet losses: bursty and random packet losses. Two sets of statistics might be appropriate for characterization of bursty and random packet losses, and a clear definition of how to define the statistics is needed. This is for further study. + +#### 5.3.1.2 Priority levels + +To support service priority levels, it may be necessary to allocate network resources according to service priority levels. For example, a call with a high priority level can be treated preferentially by providing guaranteed network resources. Public or authorized emergency calls which need emergency service treatment can be given high priority levels. Even during times of congestion, such emergency calls should be allowed to use adequate network resources. To guarantee the use of adequate network resources for such high priority calls, it may be necessary to reserve a certain amount of buffer space in network elements such as IP routers or ATM/MPLS switches. The + +required buffer size can be determined by the agreed-upon traffic profile based on an agreement between a user and a service provider, and the reservation of buffer space can be achieved using a specific buffer occupancy threshold for a service class with a high priority level. To support multiple service priority levels (e.g., emergency calls, normal/best effort calls, etc.), resource allocation based on logical buffer partitioning may be used. + +#### 5.3.1.3 Application factors + +There are a number of implementation factors that determine the required QoS traffic classes or impairment parameters in the packet-based network plane. These implementation factors should be chosen to optimize performance and will determine the specification of the required transport QoS classes or impairment parameters. For example, highly interactive speech with an MOS rating of 4.0 will require use of a G.711 codec or wideband codecs and will set tight bounds on end-to-end delay, delay variation (jitter), and packet loss. + +### 5.3.2 Packet-based network level + +Bounds must be placed on a number of impairment parameters to achieve the desired QoS Service Level. These bounds must be either specified numerically on a per-stream basis or may be selected from a number of predefined QoS traffic classes. ITU-T Rec. Y.1541 specifies a number of such QoS traffic classes. + +#### 5.3.2.1 QoS traffic classes + +Details of the recommended QoS traffic classes can be found in ITU-T Rec. Y.1541. + +#### 5.3.2.2 QoS network impairment parameters + +The primary network parameters that impact QoS are: + +- **End-to-end delay:** End-to-end delay is the sum of the delays at the different network devices and across the network links through which multimedia traffic passes. End-to-end delay has a significant effect on the user's perception of the multimedia service. +- **Delay variation (Jitter):** Delay variation is the variation in the inter-packet arrival time (leading to gaps, known as jitter, between packets) as introduced by the variable transmission delay over the network. Removing jitter requires collecting packets in buffers and holding them long enough to allow the slowest packets to arrive in time to be played in correct sequence. Jitter buffers cause additional delay, which is used to remove the packet delay variation as each packet transits the network. +- **Packet loss:** In general, IP-based networks do not guarantee delivery of packets. Packets will be dropped under peak loads and during periods of congestion. + +NOTE – In case of multimedia services, when a late packet finally arrives, it will be considered lost. + +Definitions of these parameters are specified more fully in ITU-T Rec. Y.1540. + +## 5.4 QoS budgets + +To achieve the required end-to-end QoS for a particular media stream, mechanisms must exist within the system to ensure that the bounds on individual transport parameters, or the bounds implied by classification of the flow to a particular traffic class, are enforced across the system. + +The combined impairments introduced by all the Network Operator Domains in the system must be maintained within the specified bounds. This leads to the concept of an impairment budget for each domain traversed by the media flow. This is illustrated in Figure 3. + +![Figure 3/H.360 – End-to-end and individual network operator domain impairment budgets. The diagram shows three ovals representing 'Network operator Domain 1', 'Domain 2', and 'Domain 3' connected in a sequence. Below each domain is a horizontal double-headed arrow labeled 'Impairment budget 1', 'Impairment budget 2', and 'Impairment budget 3' respectively. A single long double-headed arrow at the bottom spans across all three domains and is labeled 'End-to-end impairment budget'. The label 'H.360_F.03' is in the bottom right corner.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 3/H.360 – End-to-end and individual network operator domain impairment budgets. The diagram shows three ovals representing 'Network operator Domain 1', 'Domain 2', and 'Domain 3' connected in a sequence. Below each domain is a horizontal double-headed arrow labeled 'Impairment budget 1', 'Impairment budget 2', and 'Impairment budget 3' respectively. A single long double-headed arrow at the bottom spans across all three domains and is labeled 'End-to-end impairment budget'. The label 'H.360\_F.03' is in the bottom right corner. + +**Figure 3/H.360 – End-to-end and individual network operator domain impairment budgets** + +Network planning rules, such as those specified in ITU-T Rec. M.2301, may be used to ensure that the combined effects of impairments within each Network Operator Domain are within end-to-end budgets. Where such static provisioning is not practicable, the QoS control and signalling procedures detailed in clause 6 are intended to permit the signalling of individual impairment budgets to each Network Operator Domain traversed by the media flow. The algorithm and policies for allocating individual budgets to Network Operator Domains are outside the scope of this Recommendation. + +## 5.5 Functional entities and reference points + +A number of functional entities within both service and Network Operator Domains are defined as part of a generic end-to-end QoS control mechanism. The relationship between these functional entities is shown in Figure 4. + +![Figure 4/H.360 – Relationship between QoS functional entities. The diagram is divided into two main domains. The top domain is an oval labeled 'Service domain' containing 'QoSPE' and 'QoSME' boxes, with reference points 'C1', 'C2', 'S4', and 'T2'. The bottom domain is a larger oval labeled 'Network operator domains' containing 'NPE', 'RM', 'ICF', and 'TF' boxes, with reference points 'I1', 'I2', 'I3', 'I4', 'I5', and 'T2'. Arrows show the flow of information and media between these entities. External labels include 'To end user domain' on the left and 'Other service domains' and 'Other network operator domains' on the right. A legend at the bottom shows a double-headed arrow labeled 'Media path'. The label 'H.360_F.04' is in the bottom right corner.](410562339ce067fdc6fa41940c118658_img.jpg) + +Figure 4/H.360 – Relationship between QoS functional entities. The diagram is divided into two main domains. The top domain is an oval labeled 'Service domain' containing 'QoSPE' and 'QoSME' boxes, with reference points 'C1', 'C2', 'S4', and 'T2'. The bottom domain is a larger oval labeled 'Network operator domains' containing 'NPE', 'RM', 'ICF', and 'TF' boxes, with reference points 'I1', 'I2', 'I3', 'I4', 'I5', and 'T2'. Arrows show the flow of information and media between these entities. External labels include 'To end user domain' on the left and 'Other service domains' and 'Other network operator domains' on the right. A legend at the bottom shows a double-headed arrow labeled 'Media path'. The label 'H.360\_F.04' is in the bottom right corner. + +**Figure 4/H.360 – Relationship between QoS functional entities** + +### **5.5.1 Definition of reference points** + +Reference points within a Network Operator Domain, between two Network Operator Domains, and between an End User Domain and a Network Operator Domain are labelled I. Reference points within a Service Domain are labelled S. Reference points between a Service Domain and a Network Operator Domain are labelled T. Reference points between two Service Domains, and between a Service Domain and an End User Domain are labelled C. The example reference points in Figure 4 are defined as follows: + +I1: The reference point between an End User Domain and a Network Operator Domain. + +I2: The reference point between two Network Operator Domains. + +I3: The reference point between a RM and an ICF within a Network Operator Domain. + +I4: The reference point between a NPE and a RM within a Network Operator Domain. + +I5: The reference point between a RM and a TF within a Network Operator Domain. + +C1: The reference point between an End User Domain and a Service Domain. + +C2: The reference point between two Service Domains. + +S4: The reference point between a QoSME and a QoSPE within a Service Domain. + +T2: The reference point between a Service Domain and a Network Operator Domain. + +### **5.5.2 Definition of functional entities** + +#### **5.5.2.1 QoS Service Manager (QoSME)** + +The QoSME is a functional entity that mediates requests for end-to-end QoS in accordance with policies determined by the QoSPE. It communicates with other QoSMEs and with RMs to determine, establish and control the offered QoS. + +#### **5.5.2.2 QoS Policy Entity (QoSPE)** + +The QoSPE is a functional entity that manages application policies and provides authorization of permitted and default QoS levels. It receives requests from and issues responses to QoSMEs to establish the authorized end-to-end QoS levels. + +#### **5.5.2.3 Transport Functionality (TF)** + +The TF is a functional entity representing the collection of transport resources within a Network Operator Domain, which is capable of QoS control. + +#### **5.5.2.4 Network Policy Entity (NPE)** + +The NPE is a functional entity residing in a Network Operator Domain that maintains the policies of the Network Operator. + +#### **5.5.2.5 Resource Manager (RM)** + +The RM is a functional entity residing in a Network Operator Domain that applies a set of policies and mechanisms to transport resources within the domain to enable specified QoS levels to be achieved within the domain. + +#### **5.5.2.6 Interconnect Function (ICF)** + +The ICF is a functional entity that interconnects Network Operator Domains. It provides a policy and/or administrative boundary and may police authorized media flows between two Network Operator Domains to ensure they are consistent with the QoS policies of the Network Operator of that domain. + +# 6 QoS control and signalling procedures + +## 6.1 General framework + +End-to-end QoS control is required to ensure that the desired QoS Service Class and Priority is achieved during an MM session. Each flow during a session may potentially have associated with it a different QoS Service Class and Priority, so the mechanisms used must support this possibility. Furthermore, QoS control must be supported throughout the entire path that the media stream(s) traverses in order to achieve an end-to-end result. + +The general case is illustrated in Figure 5. QoS control flows and media flows are shown separately. There are two primary options for end-to-end QoS control: + +- Option 1 (Figure 5) – Application Service Provider (ASP) Controlled Inter-Domain Routing involving QoS signalling between QoSMS, and between QoSMS and RMs. +- Option 2 (Figure 6) – Network Operator Controlled Inter-Domain Routing involving QoS Signalling between RMs. + +The detailed description of the signalling protocols used is outside the scope of this Recommendation. + +![Diagram illustrating a call involving multiple network operator and service domains (Option 1).](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +The diagram shows a network architecture with two 'Terminal' boxes on the left and right. In the center, there are five domains: 'Service domain 1', 'Service domain 2', 'Network operator domain 1', 'Network operator domain 2', and 'Network operator domain 3'. 'Service domain 1' is connected to the left 'Terminal' and to 'Network operator domain 1'. 'Service domain 2' is connected to the right 'Terminal' and to 'Network operator domain 3'. 'Network operator domain 1' is connected to 'Service domain 1', 'Network operator domain 2', and 'Service domain 2'. 'Network operator domain 2' is connected to 'Network operator domain 1' and 'Network operator domain 3'. 'Network operator domain 3' is connected to 'Service domain 2' and 'Network operator domain 2'. A legend at the bottom left defines the line types: 'QST QoS Signalling type' (solid line with single arrow), 'Media path' (solid line with double arrow), 'QoS Signalling path' (solid line with double arrow), and 'Alternative QoS signalling paths' (dashed line with double arrow). Two alternative paths are shown: 'Option 1a' from 'Service domain 1' to 'Network operator domain 3' and 'Option 1b' from 'Service domain 2' to 'Network operator domain 1'. A note states: 'NOTE – Terminal may also be a gateway.' The diagram is labeled 'H.360\_F05' in the bottom right. + +Diagram illustrating a call involving multiple network operator and service domains (Option 1). + +Figure 5/H.360 – Call involving multiple network operator and service domains (Option 1) + +### 6.1.1 Option 1: ASP controlled inter-domain routing + +ASP Controlled Routing allows for the ASP initiating the call, possibly in conjunction with other ASPs, to select the sequence of Network Operators that will be involved in carrying the media flow. This arrangement permits a variety of business models involving multiple ASPs and multiple Network Operators. This option involves end-to-end QoS control signalling which takes place between Service Domains' QoSMS, and between a Service Domain's QoSMS and a Network Operator Domain's RM. QoS Signalling to End User Domains is the responsibility of the initiating and terminating ASP. + +#### 6.1.1.1 ASP Control: Option 1a + +In Option 1a, the entire end-to-end QoS control is with the initiating ASP. QoS control signalling takes place between the initiating ASP's QoSMS and relevant RMs. + +#### 6.1.1.2 ASP Control: Option 1b + +In Option 1b, the end-to-end QoS control is shared between the initiating ASP and other ASPs. QoS control signalling takes place between QoSMS of ASPs involved and relevant RMs. + +![Diagram of a call involving multiple network operator and service domains (Option 2).](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +This diagram illustrates a network architecture for a call involving multiple domains. At the top, two ovals represent 'Service domain 1' and 'Service domain 2', connected by a double-headed arrow. Below them, three ovals represent 'Network operator domain 1', 'Network operator domain 2', and 'Network operator domain 3', connected sequentially by double-headed arrows. On the left, a rectangle labeled 'Terminal' is connected to 'Service domain 1' and 'Network operator domain 1' by double-headed arrows. On the right, another 'Terminal' rectangle is connected to 'Service domain 2' and 'Network operator domain 3' by double-headed arrows. A legend at the bottom left defines the arrow types: a thin double-headed arrow for 'QST QoS Signalling type', a thick double-headed arrow for 'Media path', and a double-headed arrow with a central dot for 'QoS Signalling path'. A note on the right states 'NOTE – Terminal may also be a gateway.' and the diagram is labeled 'H.360\_F06'. + +Diagram of a call involving multiple network operator and service domains (Option 2). + +**Figure 6/H.360 – Call involving multiple network operator and service domains (Option 2)** + +### **6.1.2 Option 2: Network operator controlled inter-domain routing** + +With Network Operator Controlled Inter-Domain Routing, the selection of the sequence of Network Operators that will be involved in carrying the media flow lies with the Network Operators. This arrangement is the model which is most commonly used for circuit-switched networks. This option involves end-to-end QoS control signalling which takes place only between the initiating ASP and the first Network Operator. Signalling then takes place between Network Operator Domains' RMs to establish end-to-end QoS control. QoS Signalling to End User Domains, in general, will remain the responsibility of the initiating and terminating ASP. + +## **6.2 Classification of QoS signalling types** + +QoS signalling can be classified into several QoS signalling types (QSTs) as shown in Figure 7. + +![Diagram showing QoS signalling types for calls involving multiple network operator and service domains.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +This diagram shows various QoS signalling paths between terminals and domains. Two 'Terminal' rectangles are on the left and right. The left terminal connects to 'Service domain 1' (QST1), 'Network operator domain 1' (QST5), and 'Service domain 1' (QST3). 'Service domain 1' connects to 'Service domain 2' (QST2), 'Network operator domain 1' (QST3), and 'Network operator domain 2' (QST3). 'Network operator domain 1' connects to 'Network operator domain 2' (QST4). 'Network operator domain 2' connects to 'Network operator domain 3' (QST4). 'Service domain 2' connects to 'Network operator domain 3' (QST3) and the right terminal (QST1). The right terminal also connects to 'Network operator domain 3' (QST5). A legend at the bottom left defines the arrow types: a thin double-headed arrow for 'QST QoS Signalling type', a thick double-headed arrow for 'Media path', and a double-headed arrow with a central dot for 'QoS Signalling path'. A note on the right states 'NOTE – Terminal may also be a gateway.' and the diagram is labeled 'H.360\_F07'. + +Diagram showing QoS signalling types for calls involving multiple network operator and service domains. + +**Figure 7/H.360 – QoS signalling types for calls involving multiple network operator and service domains** + +### **6.2.1 QoS Signalling Type 1 (QST1)** + +QST1 describes QoS signalling between an End User and an ASP and corresponds to Reference Point C1. Figure 8 shows the functional relationships between the End User Domain, the (Access) Network Operator Domain, and Initiating Service Domain. A signalling protocol for QoS signalling initiation can be used at the application level in the End User and Service Domains. To initiate QoS signalling, the End User Domain first needs to communicate with the Initiating Service Domain via the (Access) Network Operator Domain. + +![Figure 8/H.360 – Interactions between an end user domain and a service domain via a network operator domain. The diagram shows three domains: End user domain, Network operator domain, and Service domain. The End user domain and Service domain both have five layers: Application, Transport, Network, Data link, and Phy. The Network operator domain has three layers: Network, Data link, and Phy. Dashed lines labeled QST1 connect the Application layer of the End user domain to the Application layer of the Service domain, passing through the Network operator domain. The label H.360_F08 is in the bottom right corner.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +Figure 8/H.360 – Interactions between an end user domain and a service domain via a network operator domain. The diagram shows three domains: End user domain, Network operator domain, and Service domain. The End user domain and Service domain both have five layers: Application, Transport, Network, Data link, and Phy. The Network operator domain has three layers: Network, Data link, and Phy. Dashed lines labeled QST1 connect the Application layer of the End user domain to the Application layer of the Service domain, passing through the Network operator domain. The label H.360\_F08 is in the bottom right corner. + +**Figure 8/H.360 – Interactions between an end user domain and a service domain via a network operator domain** + +### 6.2.2 QoS Signalling Type 2 (QST2) + +QST2 describes QoS signalling between two ASPs and corresponds to Reference Point C2. Figure 9 shows the functional relationships between two Service Domains and interconnecting Network Operator Domain(s). QoS signalling messages are exchanged between two Service Domains via the Network Operator Domain. A resource control function (e.g., QoSME, QoSPE, etc.) can be used at the application level in the Service Domain, and a policy protocol (e.g., COPS) can be used for policy decision in the Service Domain. + +![Figure 9/H.360 – Interactions between service domains via a network operator domain. The diagram shows three domains: Service domain 1, Network operator domain, and Service domain 2. Service domain 1 and Service domain 2 both have five layers: Application, Transport, Network, Data link, and Phy. The Network operator domain has three layers: Network, Data link, and Phy. Dashed lines labeled QST2 connect the Application layer of Service domain 1 to the Application layer of Service domain 2, passing through the Network operator domain. The label H.360_F09 is in the bottom right corner.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +Figure 9/H.360 – Interactions between service domains via a network operator domain. The diagram shows three domains: Service domain 1, Network operator domain, and Service domain 2. Service domain 1 and Service domain 2 both have five layers: Application, Transport, Network, Data link, and Phy. The Network operator domain has three layers: Network, Data link, and Phy. Dashed lines labeled QST2 connect the Application layer of Service domain 1 to the Application layer of Service domain 2, passing through the Network operator domain. The label H.360\_F09 is in the bottom right corner. + +**Figure 9/H.360 – Interactions between service domains via a network operator domain** + +### 6.2.3 QoS Signalling Type 3 (QST3) + +QST3 describes QoS signalling between an ASP and a Network Operator and corresponds to Reference Point T2. Figure 10 shows functional relationships between a Service Domain and a Network Operator Domain. The Service Domain needs to communicate with the Network Operator Domain for the reservation of necessary network resources. In Figure 10, different QoS technologies, for example, RSVP/IntServ, DiffServ, MPLS, etc., can be used at the network level in the Network Operator Domain, and a resource control function (e.g., QoSME, QoSPE, etc.) can be used at the application level in the Service Domain. A policy protocol, for example, COPS, can be used for policy decision and enforcement in the Service and Network Operator Domains. Various QoS technologies, for example, IEEE 802.1D, may also be used at the Data Link level in the Network Operator Domain. All these technologies need to work cooperatively in various strategies to enable end-to-end QoS. + +![Diagram of QoS interactions between a service domain and a network operator domain (QST3).](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +The diagram illustrates the interaction between a Service domain and a Network operator domain for QoS Type 3 (QST3). Both domains are represented by a vertical stack of five layers: Application, Transport, Network, Data link, and Phy. Dashed horizontal lines connect corresponding layers between the two domains. The label 'QST3' is positioned above the connection lines. The diagram is labeled 'H.360\_F10' at the bottom right. + +Diagram of QoS interactions between a service domain and a network operator domain (QST3). + +**Figure 10/H.360 – Interactions between a network operator domain and a service domain** + +### 6.2.4 QoS Signalling Type 4 (QST4) + +QST4 describes QoS signalling between two Network Operators and corresponds to Reference Point I2. Figure 11 shows the functional relationships between two Network Operator Domains. Different QoS technologies, for example, RSVP/IntServ, DiffServ, MPLS, etc., can be used at the network level in the Network Operator Domain. Various QoS technologies, for example, IEEE 802.1D, may also be used at the Data Link level in the Network Operator Domain. + +![Diagram of QoS interactions between two network operator domains (QST4).](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +The diagram illustrates the interaction between two Network operator domains for QoS Type 4 (QST4). Both domains are represented by a vertical stack of five layers: Application, Transport, Network, Data link, and Phy. Dashed horizontal lines connect corresponding layers between the two domains. The label 'QST4' is positioned above the connection lines. The diagram is labeled 'H.360\_F11' at the bottom right. + +Diagram of QoS interactions between two network operator domains (QST4). + +**Figure 11/H.360 – Interactions between network operator domains** + +### 6.2.5 QoS Signalling Type 5 (QST5) + +QST5 describes QoS signalling between an End User and a Network Operator and corresponds to Reference Point I1. Figure 12 shows the functional relationships between an End User Domain and a Network Operator Domain. The End User Domain may communicate with the Network Operator Domain for the reservation of necessary transport resources. In this case, the Service Domain should be involved in the authorization of communication between the End User Domain and the Network Operator Domain. + +![Diagram showing interactions between an end user domain and a network operator domain. Both domains have five layers: Application, Transport, Network, Data link, and Phy. Dashed lines connect corresponding layers between the two domains, labeled QST5. The end user domain is on the left and the network operator domain is on the right. A label H.360_F12 is at the bottom right.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +Diagram showing interactions between an end user domain and a network operator domain. Both domains have five layers: Application, Transport, Network, Data link, and Phy. Dashed lines connect corresponding layers between the two domains, labeled QST5. The end user domain is on the left and the network operator domain is on the right. A label H.360\_F12 is at the bottom right. + +**Figure 12/H.360 – Interactions between an end user domain and a network operator domain** + +## **6.3 QoS signalling procedures** + +Figures 13-15 illustrate the procedures for establishing end-to-end QoS control for an MM application. The QoS signalling may be independent of call or media stream establishment or control signalling or be combined with either of these. In the figures, the signalling required to reserve the necessary resources along the media path is shown. Additional signalling is required to confirm the resource reservation after the reservation phase. This is not shown in the diagrams. + +– Option 1a + +![Sequence diagram for QoS signalling Option 1a. Lifelines: User A, QoSM1, RM1, RM2, QoSM2, RM3, User B. Sequence: User A sends QST1 to QoSM1; QoSM1 sends QST3 to RM1; RM1 sends QST3 to RM2; RM2 sends QST3 to QoSM2; QoSM2 sends QST1 to User B; User B sends QST1 back to QoSM1; finally, Media flows are established between User A and User B. A label H.360_F13 is at the bottom right.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +Sequence diagram for QoS signalling Option 1a. Lifelines: User A, QoSM1, RM1, RM2, QoSM2, RM3, User B. Sequence: User A sends QST1 to QoSM1; QoSM1 sends QST3 to RM1; RM1 sends QST3 to RM2; RM2 sends QST3 to QoSM2; QoSM2 sends QST1 to User B; User B sends QST1 back to QoSM1; finally, Media flows are established between User A and User B. A label H.360\_F13 is at the bottom right. + +**Figure 13/H.360 – QoS signalling Option 1a** + +– Option 1b + +![Sequence diagram for QoS signalling Option 1b showing interactions between User A, QoSMT1, RM1, RM2, QoSMT2, RM3, and User B. It includes messages like QST1, QST2, QST3, and a final 'Media flows' line.](83852ec55d4802521a727926336bedab_img.jpg) + +This sequence diagram illustrates the QoS signalling process for Option 1b. The participants are User A, QoSMT1, RM1, RM2, QoSMT2, RM3, and User B. The sequence of messages is as follows: + + +- User A sends a QST1 message to QoSMT1. +- QoSMT1 sends a QST3 message to RM1. +- RM1 sends a response back to QoSMT1. +- QoSMT1 sends a QST3 message to RM2. +- RM2 sends a response back to QoSMT1. +- QoSMT1 sends a QST2 message to QoSMT2. +- QoSMT2 sends a QST3 message to RM3. +- RM3 sends a response back to QoSMT2. +- QoSMT2 sends a QST1 message to User B. +- User B sends a response back to QoSMT2. +- QoSMT2 sends a QST2 message back to QoSMT1. +- QoSMT1 sends a QST1 message back to User A. +- Finally, a 'Media flows' line is shown between User A and User B. + + The diagram is labeled H.360\_F14 at the bottom right. + +Sequence diagram for QoS signalling Option 1b showing interactions between User A, QoSMT1, RM1, RM2, QoSMT2, RM3, and User B. It includes messages like QST1, QST2, QST3, and a final 'Media flows' line. + +**Figure 14/H.360 – QoS signalling Option 1b** + +– Option 2 + +![Sequence diagram for QoS signalling Option 2 showing interactions between User A, QoSMT1, RM1, RM2, QoSMT2, RM3, and User B. It includes messages like QST1, QST3, QST4, QST1, and a final 'Media flows' line.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +This sequence diagram illustrates the QoS signalling process for Option 2. The participants are User A, QoSMT1, RM1, RM2, QoSMT2, RM3, and User B. The sequence of messages is as follows: + + +- User A sends a QST1 message to QoSMT1. +- QoSMT1 sends a QST3 message to RM1. +- RM1 sends a QST4 message to RM2. +- RM2 sends a QST4 message to RM3. +- RM3 sends a response back to RM2. +- RM2 sends a response back to RM1. +- RM1 sends a QST1 message back to QoSMT1. +- QoSMT1 sends a response to User B. +- QoSMT1 sends another response back to User A. +- Finally, a 'Media flows' line is shown between User A and User B. + + The diagram is labeled H.360\_F15 at the bottom right. + +Sequence diagram for QoS signalling Option 2 showing interactions between User A, QoSMT1, RM1, RM2, QoSMT2, RM3, and User B. It includes messages like QST1, QST3, QST4, QST1, and a final 'Media flows' line. + +**Figure 15/H.360 – QoS signalling Option 2** + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | + +![Barcode with the number 25996 between two asterisks.](0b0dbdb00519a67d96c812ee07da3a1e_img.jpg) + +A barcode consisting of vertical black lines of varying widths. Below the barcode, the number "25996" is printed, flanked by two asterisks: "\* 2 5 9 9 6 \*". + +Barcode with the number 25996 between two asterisks. \ No newline at end of file diff --git a/marked/H/T-REC-H.361-200605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.361-200605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/H/T-REC-H.361-200605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/H/T-REC-H.361-200605-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.361-200605-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..700774e74aa610392d88c2cf64290ea7808c21f6 --- /dev/null +++ b/marked/H/T-REC-H.361-200605-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d5b5a6967f85b2760de086038362d366929e58ba67a830199f6f9a79eabe31c +size 85171 diff --git a/marked/H/T-REC-H.361-200605-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/H/T-REC-H.361-200605-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..481ec6870894da3c06f5b6cf854a5b4f9b836923 --- /dev/null +++ b/marked/H/T-REC-H.361-200605-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fd38cb9d7ac40fa16bc5da4aa4175484eb86f3a432290f0d70a58b9a2782395 +size 69796 diff --git a/marked/H/T-REC-H.361-200605-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.361-200605-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..885c796289d1874a01678fbf3ce9a15211105e0c --- /dev/null +++ b/marked/H/T-REC-H.361-200605-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df96a3aa9d1b3f32f8997c2d883c8ff0073e25e1759b86aafa163c3d2480d41 +size 80645 diff --git a/marked/H/T-REC-H.361-200605-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/H/T-REC-H.361-200605-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5453acd09655ef40d590314794995625afb0a2df --- /dev/null +++ b/marked/H/T-REC-H.361-200605-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37dddd92e6746cd21ad2dd9a838c0c1b891faa2bb1bb5cd28dbc74a4964c3646 +size 59029 diff --git a/marked/H/T-REC-H.361-200605-I_PDF-E/raw.md b/marked/H/T-REC-H.361-200605-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4087c59f62f34a644298bcefd127f5df5253bda2 --- /dev/null +++ b/marked/H/T-REC-H.361-200605-I_PDF-E/raw.md @@ -0,0 +1,580 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.361** + +(05/2006) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Quality of service +architecture for audiovisual and multimedia services + +--- + +**End-to-end quality of service (QoS) and service +priority signalling in H.323 systems** + +ITU-T Recommendation H.361 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|--------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.361** + +# **End-to-end quality of service (QoS) and service priority signalling in H.323 systems** + +## **Summary** + +This Recommendation defines the H.323 Quality of Service (QoS) and Service Priority signalling for exchanging, negotiating and controlling QoS and service priority parameters among the H.323 entities in a call. These calls may involve multiple network operator domains, multiple service domains, and heterogeneous transport mechanisms (e.g., mixed IP, ATM, and MPLS environments). In a single network operator domain or H.323 service domain, the QoS policies and mechanisms are usually homogenous and therefore the negotiation and establishment of QoS for a call is relatively simple. However, the same is relatively more complex when a call has to traverse multiple service or network domains each of which has its own set of policies and mechanisms. This Recommendation describes the QoS and priority signalling to enable a H.323-based call to acquire QoS irrespective of the number of domains it traverses. + +###### **Source** + +ITU-T Recommendation H.361 was approved on 29 May 2006 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2006 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|-----|-----------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 2.1 | Normative References ..... | 1 | +| 2.2 | Informative References ..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations and Acronyms ..... | 2 | +| 5 | Architecture ..... | 3 | +| 5.1 | The H.323 System ..... | 3 | +| 5.2 | Functional Entities..... | 4 | +| 6 | QoS Parameters ..... | 4 | +| 6.1 | Service Priority ..... | 4 | +| 6.2 | QoS Descriptor ..... | 5 | +| 6.3 | Traffic Descriptor ..... | 6 | +| 6.4 | Authorization Parameters ..... | 6 | +| 7 | QoS Negotiation with the Network ..... | 6 | +| 7.1 | Direct QoS Negotiation ..... | 6 | +| 7.2 | Path-Coupled QoS Negotiation ..... | 6 | +| 7.3 | Other QoS Negotiation ..... | 7 | +| 8 | H.323 QoS & Service Priority Procedures ..... | 7 | +| 8.1 | Pre-Call Setup Procedures ..... | 7 | +| 8.2 | Call Setup Procedures..... | 8 | +| 8.3 | Bearer/Media Stream Setup Procedures ..... | 10 | +| 8.4 | Gatekeeper Update ..... | 12 | +| 8.5 | Authorization Procedures ..... | 13 | +| 8.6 | Media Exchange ..... | 13 | + + + +# End-to-end quality of service (QoS) and service priority signalling in H.323 systems + +# 1 Scope + +This Recommendation defines the mechanisms (parameters, message formats and procedures) between H.323 functional entities that may be used for signalling and control of end-to-end QoS and service priority in H.323 systems. ITU-T Rec. H.360 describes the various QoS signalling types in a H.323 system. Since the focus of this Recommendation is QoS signalling between the H.323 entities within a service domain and across multiple service domains, the signalling in this Recommendation maps to QoS types 1 and 2 described in ITU-T Rec. H.360. + +The following is outside the scope of this Recommendation: + +- Other QoS signalling: Signalling between H.323 service domain and network domain is outside the scope of this Recommendation. +- Transport QoS mechanisms: QoS signalling that occurs in the network domain is not within the scope of this Recommendation. In other words, the QoS and service priority mechanisms described in this Recommendation are independent of transport QoS mechanisms that exist in the network domain (e.g., Differentiated Services (DiffServ), Integrated Services (IntServ)/RSVP or ATM QoS mechanisms). +- Security: Security is not within the scope of this Recommendation. This Recommendation shall be compatible with any security mechanisms defined for ITU-T Rec. H.323. +- QoS MIB: Though considered important, support of any QoS MIBs is not within the scope of this Recommendation. +- QoS measurement and monitoring: This Recommendation addresses how QoS can be secured. It does not address the subsequent measurement and monitoring of QoS. + +# 2 References + +## 2.1 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.360 (2004), *An architecture for end-to-end QoS control and signalling*. +- ITU-T Recommendation Y.1221 (2002), *Traffic control and congestion control in IP-based networks*. +- ITU-T Recommendation Y.1541 (2006), *Network performance objectives for IP-based services*. +- IETF RFC 2205 (1997), *Resource Reservation Protocol (RSVP) – Version 1 Functional Specification*. + +- IETF RFC 2474 (1998), *Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers*. +- IETF RFC 3312 (2002), *Integration of Resource Management and Session Initiation Protocol (SIP)*. + +## 2.2 Informative references + +- IETF RFC 2998 (2000), *A Framework for Integrated Services Operation over Diffserv Networks*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 application plane:** The H.323 application plane is made up of one or more H.323 service domains, each under the control of an H.323 end-user or H.323 Service Provider. + +**3.2 end user/endpoint:** An entity employing application services. + +**3.3 network operator:** An administrative entity operating a network. + +**3.4 network operator domain:** A collection of network resources sharing a common set of policies, QoS mechanisms and technologies under the control of a Network Operator. Network domain and network operator domain are used interchangeably. + +**3.5 network policy entity (NPE):** A functional entity residing in a Network Domain that maintains the policies of the Network Operator. + +**3.6 QoS service manager (QoSM):** A functional entity that mediates requests for end-to-end QoS in accordance with the policy determined by the QoSPE. It communicates with other QoSMs and with RMs to determine, establish and control the offered QoS. The QoSM will normally be the functionality within an H.323 gatekeeper and therefore is a H.323 service domain function. + +**3.7 QoS policy entity (QoSPE):** A functional entity that manages H.323 application policies and provides authorization of permitted and default QoS levels. It receives requests from and issues responses to QoSMs to establish the authorized end-to-end QoS levels. QoSPE may reside within the H.323 service domain or reside in a back-end policy server. + +**3.8 service domain:** A Service Domain is a collection of physical or functional entities offering Application Services under the control of an Application Service Provider which share a consistent set of policies and common technologies. + +**3.9 transport functionality (TF):** A functional entity in the Network Domain representing the collection of transport resources within a Network Domain which is capable of QoS control. + +**3.10 transport plane:** A collection of network operator domains. + +**3.11 transport resource manager (RM):** A functional entity in the Network Domain that applies a set of policies and procedures to a set of transport resources to ensure that these are allocated to enable QoS guarantees across the domain of control of the RM. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +| | | +|----------|------------------------------------------| +| ACF | Admission Confirm | +| ARJ | Admission Reject | +| ARQ | Admission Request | +| BCF | Bandwidth Confirm | +| BRJ | Bandwidth Reject | +| BRQ | Bandwidth Request | +| DiffServ | Differentiated Services | +| DSCP | Differentiated Service Code Point | +| IntServ | Integrated Services | +| NPE | Network Policy Entity | +| QoS | Quality of Service | +| QoSM | Quality of Service Manager | +| QoSPE | Quality of Service Policy Entity | +| QST | QoS Signalling Type | +| RCF | Registration Confirm | +| RM | Resource Manager | +| RRJ | Registration Reject | +| RRQ | Registration Request | +| RSVP | Resource ReSerVation Protocol (RFC 2205) | +| TF | Transport Functionality | +| ToS | Type of Service | + +# 5 Architecture + +The architecture for end-to-end QoS control and signalling is described in ITU-T Rec. H.360. The signalling components described in this Recommendation are based on the architecture therein. + +## 5.1 The H.323 system + +In this Recommendation, the H.323 system is defined as the H.323 application plane and the associated transport plane. The H.323 application plane is made up of one or more H.323 service domains, each under the control of an H.323 end-user or H.323 Service Provider. Examples of H.323 entities within the service domain are gatekeepers, gateways, H.323 endpoints, etc. The transport plane includes a number of separate network operator domains. The network operator domain consists of transport-related functionality that includes IP routers, switches, firewalls, etc. Each network domain may have its own QoS policies and/or differ from other domains in terms of administrative control (e.g., network operator), QoS mechanisms (RSVP/IntServ, DiffServ, MPLS, etc.), access, metering, addressing schemes (global or local), transport protocol (IPv4 or IPv6), etc. + +## 5.2 Functional entities + +The different functional entities in a H.323 system have been described in ITU-T Rec. H.360 and shown in Figure 1: + +![Diagram illustrating the relationship between QoS functional entities in an H.323 system. It shows an H.323 endpoint connected to a Network operator domain containing RM, TRF, and NPE, which is further connected to an H.323 service domain containing QoSM and QoSPE. Arrows indicate various signaling paths between these entities.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +The diagram illustrates the functional entities and their interactions in an H.323 system. On the left is an **H.323 endpoint**. A solid double-headed arrow labeled **Media** connects it to the **Network operator domain**. A dashed double-headed arrow labeled **QoS signalling** connects it to the **TRF** entity within the network operator domain. The **Network operator domain** contains three entities: **RM**, **TRF**, and **NPE**. **RM** is connected to **TRF** by a dashed double-headed arrow. **TRF** is connected to **NPE** by a solid double-headed arrow. **TRF** also has a solid double-headed arrow connecting it to the **H.323 service domain** on the right, labeled **H.361(06)\_F01**. The **H.323 service domain** contains **QoSM** and **QoSPE**. **QoSM** is connected to **QoSPE** by a solid double-headed arrow. **QoSM** has a solid double-headed arrow connecting it to the **H.323 endpoint** labeled **H.323 signalling**. **QoSM** also has a solid double-headed arrow connecting it to an **Other service domain** labeled **H.323 Signalling**. A dashed double-headed arrow labeled **Application-transport QoS signalling** connects **QoSM** to **RM**. A legend at the bottom left shows a solid double-headed arrow for **Media** and a dashed double-headed arrow for **QoS signalling**. + +Diagram illustrating the relationship between QoS functional entities in an H.323 system. It shows an H.323 endpoint connected to a Network operator domain containing RM, TRF, and NPE, which is further connected to an H.323 service domain containing QoSM and QoSPE. Arrows indicate various signaling paths between these entities. + +**Figure 1/H.361 – Relationship between QoS functional entities** + +The two functional entities that are important to this discussion are the QoSM and the QoSPE. QoSM is the entity that mediates end-to-end QoS request in accordance with the policy determined by the QoSPE. The QoSPE is the entity that manages the application policies and provides authorization for QoS. The QoSPE and QoSM usually reside in the gatekeeper. The components are not usually called out individually in this Recommendation. + +# 6 QoS parameters + +The QoS parameters necessary for H.323 QoS signalling include four main elements. These elements are: + +- Service priority: Indicates the priority of the stream. +- QoS descriptor: Provides the QoS requirements for the stream. +- Traffic descriptor: Provides the traffic characteristics of the stream. +- Authorization parameters: Policy elements that authorize the request. + +These are described in greater detail below. + +## 6.1 Service priority + +The service priority parameter is used to signal the priority of service to be provided to a bearer stream within an H.323 system. This priority parameter may be signalled between service providers, or between service providers and end users. Media flows categorized as high priority shall take precedence over those categorized lower in priority with respect to the allocation of transport resource. The initiating endpoint/service provider shall determine the priority to be assigned to the media stream in both directions and signal this to other service providers or endpoints involved in the call. + +Service Priority is an optional parameter and need not be included if routine priority is sufficient. If service priority is required, then it is signalled via the service priority parameter. The service priority uses the following format: + +### – **servicePrioritySignalled** (boolean) + +This parameter shall specify whether service priority is to be signalled using the servicePriorityValue parameter. A false value indicates that the service priority is based on a value determined by *a priori* agreement between business entities. + +### – **servicePriorityValue** (enumeration) + +This parameter contains the requested service priority information that is used to signal the service priority between the H.323 entities. The description of this parameter will be further defined in a future annex of this Recommendation. + +The service priority (**servicePriority**) parameter is added to the existing **qosCapability** parameter. + +## 6.2 QoS descriptor + +The QoS descriptor contains the QoS requirements for the bearer stream. It is an optional parameter. If best effort service is sufficient, then the QoS descriptor parameter need not be included. The presence of a QoS descriptor indicates that better-than-best-effort service is required. The QoS descriptor includes a **qoSType** followed by a **qoSValue**. The elements of QoS descriptor are described in detail below. + +### 6.2.1 Parameter QoSType + +The parameter QoSType indicates the strength of the QoS request which guides the action to be taken in case of a QoS failure. In other words, it is used by the H.323 system to decide whether a call is to be continued or failed based on QoS failures. There are two possibilities with respect to the QoS type. They are: + +- **Desired:** This indicates that QoS is desirable but not mandatory for the call. This means that the QoS request should be attempted but the call can continue even if the desired QoS is not granted. +- **Required:** This indicates that QoS is required and the call cannot continue if the required QoS for the stream is unavailable. + +### 6.2.2 Parameter QoSValue + +The parameter QoSValue is used to specify the QoS requirements for the stream. The **qoSValue** values may be left unspecified if they are to be derived from other sources such as static configurations and service level agreements. They are to be signalled via the **qoSValue** parameter if they are to be specified. It is necessary to signal this information end-to-end as it allows the H.323 entities to agree upon the required QoS for the stream as well as it allows intermediary H.323 entities to negotiate these QoS requirements with their respective network domains. The **qoSValue** is described in terms of a QoS class as defined by ITU-T Rec. Y.1541, which provides a list of defined classes from which one that is appropriate for the bearer stream may be selected. Each QoS class defined in ITU-T Rec. Y.1541 contains a specific combination of bounds for end-to-end delay, end-to-end delay variation, and mean packet loss. + +The **qoSDescriptor** parameter is added to the existing **qoSCapability** parameter. + +## 6.3 Traffic descriptor + +The traffic descriptor describes the bearer stream. The traffic descriptor is required for negotiating QoS with the network domain. The network domain utilizes such information for admission control and resource management. The agreed-upon QoS for a stream is guaranteed only if the flow remains conformant to the traffic descriptor provided. + +ITU-T Rec. H.245 has already provided parameters for certain mechanisms such as RSVP and ATM. Hence, these parameters (rsvpParameters and atmParameters) will be reused for providing the traffic descriptor for RSVP and ATM respectively. For other QoS and transport mechanisms, a generic transport parameter is added to the qosCapability parameter. This genericTransport parameter consists of maximum allowed packet size, rate of flow, peak rate and bucketSize as described in ITU-T Rec. Y.1221 for transport parameter. + +## 6.4 Authorization parameters + +These authorization elements are required for authorization with the H.323 service domain and/or with the network domains. These parameters may be used by the gatekeeper for admission control. They may also be shared with the network domain to authorize the request for network resources. + +This parameter will be discussed in detail in a future annex of this Recommendation. A placeholder for authorization elements have been provided in the **qosCapability** parameter. + +# 7 QoS negotiation with the network + +The H.323 QoS signalling is influenced by QoS signalling in the network, QoS authorization mechanisms supported, and network awareness among the H.323 entities. Therefore, a brief discussion of the various options in which the H.323 system can interact with the network entities is provided below. The objective of this Recommendation is not to make a suggestion but to ensure that QoS elements described in this Recommendation are sufficient irrespective of the option selected. + +## 7.1 Direct QoS negotiation + +This type of QoS negotiation is described as option 1 in ITU-T Rec. H.360. This model expects that the H.323 entities have the necessary network awareness to identify the network device/interface that is going to service the bearer stream. Therefore, it can engage with the identified network device/interface to ensure that the bearer stream receives the necessary QoS. The H.323 entity can request the necessary resources from the identified network device/interface and provide the appropriate authorization parameters to ensure that the bearer stream receives the desired QoS. If the network device is unable to meet the QoS request, it may fail the request or return an error. In such a case, the H.323 domain takes necessary actions such as failing the call, re-routing or any other configured failure actions. If the QoS request is granted, then the H.323 system allows the endpoint to initiate the call and exchange media. + +## 7.2 Path-coupled QoS negotiation + +In another model, the network devices that service the media are identified via network-based QoS signalling. This signalling is out-of-band and traverses the same path as that of the bearer stream. Hence, it is referred to as a path-coupled QoS signalling. An example of this type of signalling is RSVP. This is described as option 2 in ITU-T Rec. H.360. + +The path-coupled QoS signalling traverses the network entities along the path requesting resources for the bearer stream. The credentials for authorizing the QoS request may be presented via the same signalling or the network devices may approach the H.323 domain for authorization. This model is usable in large and complex topologies. However, the additional signalling and maintenance of state may be undesirable in some networks. + +## 7.3 Other QoS negotiation + +There are other types of QoS establishment that are a variation or a combination of the above two options. Media relay is one such example. A media relay participates in both call signalling and media transmission. Hence, QoS request and response occurs between the different components in a + +single device. Another example is a variation of the direct QoS mechanism where the H.323 entity communicates with a QoS server in the network which in turn translates the request to the appropriate devices/interfaces. + +Any of these options may be combined with the Differentiated Services QoS mechanism. The Differentiated Services is an implicit in-band signalling mechanism that carries a value in the ToS byte (DSCP value) in an IP header of the bearer packet. The network entities classify, meter and schedule the packets based on the DSCP value thus providing the packets with the necessary QoS. RFC 2998 describes the use of RSVP along with DiffServ. + +# 8 H.323 QoS and service priority procedures + +In this clause, the QoS and service priority procedures are described for the various stages of call establishment. These requirements may vary depending on QoS capabilities and mechanisms supported among the H.323 entities. + +## 8.1 Pre-call setup procedures + +This is the discovery phase of the QoS and service priority setup. The following steps are involved: + +- **System QoS Discovery:** First of all, the endpoints need to discover the QoS and service priority classes supported by the H.323 system and any defaults provided as well. +- **Default Class Selection:** The next step is the endpoint selection of a default H.323 QoS and service priority class applicable to all calls or media streams established from that endpoint. +- **Transport-QoS capabilities negotiation:** In this step, the endpoint indicates its QoS capabilities to the gatekeeper. This is discussed in greater detail in the following subclause. +- **Gatekeeper user profile discovery:** Discovery by a gatekeeper of the profile of a visiting user to the service domain controlled by the gatekeeper. +- **Gatekeeper to Gatekeeper Service Class Discovery:** Gatekeeper discovery of the H.323 QoS and priority classes supported by another gatekeeper or the default QoS and priority levels provided by the system. + +### 8.1.1 Endpoint QoS capabilities registration + +The endpoint indicates its QoS capabilities to the gatekeeper during the RAS phase. This capability is signalled during the endpoint registration using the **transportQoS** field of the RRQ or the ARQ message. The gatekeeper either accepts or rejects the endpoint's selection and indicates its choice. The gatekeeper's choice is binding on the endpoint. If sent in the RRQ, the capabilities expressed in the **transportQoS** field apply to all calls made by the endpoint, unless the endpoint overrides the capability by specifying a **transportQoS** field in an ARQ message. If the endpoint includes **transportQoS** in an ARQ message, the capabilities specified apply only to that particular call. + +The **transportQoS** field is an optional parameter in an RRQ and ARQ message. It indicates whether the endpoint is capable of participating in transport-QoS exchange. The elements of the **transportQoS** parameter are as follows: + +- **Endpoint Controlled:** This option implies that the endpoint will control the transport QoS exchange. +- **Gatekeeper Controlled:** In this option, the endpoint expresses that the gatekeeper will control the transport QoS exchange on behalf of the endpoint. +- **No Control:** This option implies that no QoS exchange is necessary. This option indicates to the gatekeeper that QoS exchange is not necessary for the call. + +- **QoSCapability:** This is a new parameter added by this Recommendation. This parameter provides the details of the endpoint's QoS capability, credentials and service priority as required. If the endpoints are capable of RSVP, then the **qosMode** in the **rsvpParameters** is used. If the endpoint prefers to locally secure QoS within its domain, then it indicates by setting the **localQoS** to TRUE. If a non-routine service priority is required, then this is indicated to the gatekeeper for approval. **transportQoS** as defined earlier is not stream specific. It has been modified by this Recommendation to contain a sequence of QoSCapability each of which will apply to a single stream. + +Since at the time of RAS the H.323 entity does not know which streams will be finally selected in the call, it shall request admission for the different media streams that are being offered in a given call (SimultaneousCapabilitySet). Among the various options given for a single media (alternativeCapabilitySet), the H.323 endpoint shall pick the one that requires the most QoS resources. The bandwidth parameter shall contain the total of the bandwidth requests of all the simultaneous streams. + +Subsequently, if there is change from what was originally admitted, the H.323 can update the QoS admission by sending a new QoSCapability in a BRQ request. + +### 8.1.2 Gatekeeper selection of QoS capabilities + +The gatekeeper decides whether to accept or reject the QoS capabilities received in the ARQ message based on the received information, its knowledge on the state of the network, any defaults configured, etc. The gatekeeper accepts the request by responding with an ACF or a RCF message. It may optionally insert a **transportQoS** if any information needs to be communicated to the H.323 endpoint such as Differentiated Service Code Point (DSCP) value to be used with the stream. If the gatekeeper rejects the selection provided by the H.323 endpoint, then it rejects the request by sending an ARJ or a RRJ. + +The gatekeeper uses the parameters provided by the endpoint to admit or deny a request. The service priority parameter is used to ensure that the endpoint/user is allowed to request priority resources. The authorization credentials, if provided, are used to authorize the request. The gatekeeper also verifies the endpoint's use of the right QoS mechanism such as RSVP, local QoS or a particular QoS strength for the call. The gatekeeper's response may indicate one of the following options: + +- **Endpoint Controlled:** In an ACF message, the presence of this option confirms the endpoint's control of QoS. +- **Gatekeeper Controlled:** In an ACF message, this confirms the gatekeeper's control of QoS. +- **No Control:** If included in an ACF message, then it confirms that no control of QoS is required. + +The gatekeeper's decision relayed in the RCF message applies to all calls made by the endpoint, unless the gatekeeper later supplies a **transportQoS** field in an ACF message. If relayed in the ACF message, the decision applies only to that particular call to which the ACF applies. The endpoint shall accept the gatekeeper's decision in order to place a call. + +## 8.2 Call setup procedures + +In many cases, synchronizing QoS negotiation with call signalling is necessary to implement the required QoS policies and provide consistent QoS quality. To provide synchronization, the QoS negotiation must occur before the endpoint is alerted. Currently, alerting of the called endpoint occurs before media stream setup. Since QoS establishment requires information that is normally available only during media-setup, QoS establishment occurs after media-setup and therefore after alerting. This gives rise to undesirable scenarios such as failing the call if sufficient network + +resources are not available after the called endpoint has been alerted. To avoid such scenarios, it is necessary to perform QoS establishment before alerting the called endpoint. This can be done in the following ways: + +- Fast Start procedures. +- Inclusion of the H.245 address in the Setup message. +- H.245 Tunnelling. + +If the called H.323 endpoint or any intermediary H.323 entity requires a "required" **qosType** and receives the setup messages without any of the above, then the call establishment is failed because the QoS requirements cannot be met. If the calling endpoint wishes a **qosType** of "desired", then it is allowed to perform QoS signalling without requiring that the alerting be withheld. Therefore, it can use the normal H.323 signalling sequence as the call will be established irrespective of the QoS response. + +### 8.2.1 Fast-start procedures + +Fast-start procedures may be used by the H.323 entities to enable QoS establishment before alerting of the called endpoint. In this procedure, a sequence of OpenLogicalStructures is included in the Setup message. To allow for QoS negotiation, these procedures contain the QoS parameters as well. The presence of the QoSCapabilities indicates to the called endpoint that QoS procedures are required. This enables the withholding of the alerting until the QoS procedures are complete. Figure 2 shows an example call flow. + +![Sequence diagram illustrating Fast-start with QoS negotiation between EP1, R1, GK, R2, and EP2.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +``` + +sequenceDiagram + participant EP1 + participant R1 + participant GK + participant R2 + participant EP2 + + EP1->>GK: (1) ARQ + GK-->>EP1: (2) ACF/ARJ + EP1->>EP2: (3) Fast start (includes OLC structures) + Note over EP1, EP2: Called party will withhold alerting until QoS establishment + EP2->>GK: (4) ARQ + GK-->>EP2: (5) ACF/ARJ + Note over EP1, EP2: QoS negotiation + EP2->>EP1: (6) Connect (includes OLC structures) + +``` + +The diagram shows a sequence of messages between five entities: EP1, R1, GK, R2, and EP2. The sequence is as follows: + +- EP1 sends an (1) ARQ message to GK. +- GK responds with a (2) ACF/ARJ message to EP1. +- EP1 sends a (3) Fast start message (including OLC structures) to EP2. +- A horizontal bar indicates: "Called party will withhold alerting until QoS establishment". +- EP2 sends a (4) ARQ message to GK. +- GK responds with a (5) ACF/ARJ message to EP2. +- A horizontal bar indicates: "QoS negotiation". +- EP2 sends a (6) Connect message (including OLC structures) back to EP1, passing through R2 and R1. + +H.361(06)\_F02 + +Sequence diagram illustrating Fast-start with QoS negotiation between EP1, R1, GK, R2, and EP2. + +**Figure 2/H.361 – Fast-start with QoS negotiation** + +### 8.2.2 H.245 address in the setup message + +In this mechanism, the H.323 entity adds the H.245 address in the Setup message. Once the called endpoint receives the H.245 address, it can initiate the H.245 exchange which allows for QoS negotiation. Until the QoS negotiation is complete, alerting is withheld. A Call Proceeding message is sent to prevent timeouts. + +### 8.2.3 H.245 tunnelling + +H.245 tunnelling is another mechanism by which the H.245 information necessary for the QoS procedures can be exchanged during the call-setup process. This allows an endpoint to initiate the QoS procedures and ensures the requested QoS is available before the alerting process. + +## 8.3 Bearer/media stream setup procedures + +The previous clause dealt with how the H.245 exchange can be made possible during the call-setup phase. This clause elaborates the QoS handling within the H.245 exchange. + +### 8.3.1 qosType Negotiation + +The **qosType** indicates whether the call can proceed even if the QoS request failed. Even if a single call leg has a "required" **qosType**, the following rules apply: + +- A stream is said to have a "required" **qosType** even if one of the call-legs has a "required" **qosType** policy. At each H.323 entity, the **qosType** is combined with the **qosType** from the incoming message to derive the **derivedQoSType**. The **derivedQoSType** is the one that is used and is also used in the **QoSDescriptor** that is forwarded onwards. If a "required" **qosType** is combined with a "desired" **qosType**, then the resulting **derivedQoSType** is "required". A "required" **qosType** in any call leg will cause a stream to be failed if QoS is not secured for any leg of the call. +- Any H.323 entity that fails to receive the required QoS must initiate the call teardown in the case of the "required" QoS. +- The called endpoint must not alert the user until the confirmation to the QoS request is received in the case of a "required" **qosType**. This is done to avoid a situation where the user is alerted and the call is failed subsequently. + +All the rules above apply to a single logical channel (stream). The H.323 entities should contain policies that dictate what kind of action is required when there is QoS failure for a subset of streams in a call. + +### 8.3.2 H.245 capability exchange phase + +During the H.245 capability exchange, each endpoint indicates its QoS capabilities to the other endpoint via the **qosCapability** parameter which is included in the **transportCapability** Parameter. Since **transportCapability** is common and does not differentiate between send capabilities and receive capabilities, the QoS capability shall apply to both the send and the receive directions. Since H.245 exchange is not stream specific, there is no value in providing stream specific parameters at this time. The omission of the **qosCapability** parameter in the H.245 capability exchange indicates to the called endpoint that the calling endpoint has either no capability or desire to provide QoS negotiation. + +The following can be signalled to the other endpoint during this phase using the **qosCapability** parameter: + +- Endpoint indicates the strength of the QoS required for the call via the **qosType** in **qosDescriptor** parameter. +- If the endpoint wishes to engage in RSVP, then it is signalled via the **qosMode** in **rsvpParameters**. Since RSVP requires the participation of both the endpoints, if the called endpoint does not support this capability, it may reject the request. +- Endpoint can signal **localQoS** if it wishes to locally secure QoS in its domain. The called endpoint should signal whether it is capable of **localQoS** as well. +- If the calling endpoint requires the use of non-routine service priority, then it signals the service priority in the **qosCapability**. The calling endpoint will use the same priority for its side of the bearer stream. +- If the **qosType** of the different channels is different, then the **qosType** in the H.245 capability exchange should represent the strongest of the values as explained in the above subclause. + +### 8.3.3 Logical channel signalling + +In this phase, the opening of the H.245 logical channel is where the main QoS exchanges happen and reserving of resources are done. Reservations (guaranteed or controlled) are performed only if both H.323 endpoints indicate that they are RSVP capable during capability exchange. + +Figure 3 shows the flow for a call that includes H.245 address in the Setup message and uses path-coupled QoS negotiation. The gatekeeper (GK) shown in the figure may be one or more gatekeepers in one or more service and network domains. In this figure, the calling H.323 endpoint (EP1) sends a Setup message with the H.245 address. In the capability exchange, EP1 indicates that QoS is required. The called H.323 endpoint (EP2) accepts the QoS parameters by responding to the Capability exchange. The OLC exchange includes all the QoS parameters for each logical channel for which end-to-end QoS is required. The parameters are used for QoS negotiation between the endpoints. Once the QoS is confirmed, then the called endpoint (EP2) alerts the users and continues with call establishment. + +If the called endpoint does not receive a fast-start message or a H.245 component in the setup message, it assumes that the calling endpoint is not capable of path-coupled QoS negotiation. The called endpoint can then decide to decline the call based on the configured policies. + +If the **qosType** for the call is "desired", then the called party can alert the user even before the QoS negotiation is complete. The reason for this is that a failure of QoS will not result in a failure of the call. + +![Sequence diagram for H.361 OLC exchange with QoS negotiation. Lifelines: EP1, R1, GK, R2, EP2. The process involves RAS messages (ARQ, ACF/ARJ, Setup), a Capability exchange phase, and a QoS negotiation phase. OLC messages with QoS capability are exchanged between EP1 and EP2 via the GK. Final steps include Alerting and Connect messages.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant EP1 + participant R1 + participant GK + participant R2 + participant EP2 + + Note left of EP1: (1) ARQ + EP1->>GK: (1) ARQ + Note right of GK: (2) ACF/ARJ + GK-->>EP1: (2) ACF/ARJ + Note left of EP1: (3) Setup with H.245 address + EP1->>EP2: (3) Setup with H.245 address + Note right of EP2: (4) ARQ + EP2->>GK: (4) ARQ + Note right of GK: (5) ACF/ARJ + GK-->>EP2: (5) ACF/ARJ + + Note over EP1, EP2: Capability exchange + Note left of EP1: (6) OLC with QoS capability + EP1->>GK: (6) OLC with QoS capability + Note right of GK: (7) OLC with QoS capability + GK-->>EP2: (7) OLC with QoS capability + + Note over EP1, EP2: QoS negotiation + Note right of GK: (8) Alerting (occurs after QoS establishment) + GK-->>EP1: (8) Alerting (occurs after QoS establishment) + Note right of GK: (9) Connect + GK-->>EP1: (9) Connect + +``` + +H.361(06)\_F03 + +Sequence diagram for H.361 OLC exchange with QoS negotiation. Lifelines: EP1, R1, GK, R2, EP2. The process involves RAS messages (ARQ, ACF/ARJ, Setup), a Capability exchange phase, and a QoS negotiation phase. OLC messages with QoS capability are exchanged between EP1 and EP2 via the GK. Final steps include Alerting and Connect messages. + +**Figure 3/H.361 – OLC exchange with QoS negotiation** + +Figure 4 shows a flow for a call that includes H.245 address in the Setup message and uses local (direct) QoS negotiation. In this model, the gatekeeper identifies and pushes down the QoS parameters and authorization elements onto the network device(s) in its domain to request and secure QoS. During RAS exchange, the endpoints and gatekeeper do not have the necessary QoS parameters such as the traffic descriptor to negotiate QoS with the network. Therefore, to implement direct QoS negotiation, the gatekeeper controlled H.245 exchange is suggested. This allows the gatekeeper to be in the path of the OLC exchanges which contain the negotiated QoS parameters that are used to negotiate QoS with the network. The H.245 capability exchange is not shown in the figure for simplicity sake. + +![Sequence diagram illustrating H.323 QoS signalling via direct QoS negotiation between EP1, R1, GK, R2, and EP2. The diagram shows 15 numbered messages exchanged between these entities to establish a call with QoS parameters.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +sequenceDiagram + participant EP1 + participant R1 + participant GK + participant R2 + participant EP2 + + EP1->>GK: (1) ARQ + GK-->>EP1: (2) ACF/ARJ + EP1->>GK: (3) Setup with H.245 address + GK->>EP2: (4) Setup with H.245 address + GK-->>EP2: (5) ARQ + EP2-->>GK: (6) ACF/ARJ + GK->>R2: (7) OLC request (with QoS parameters) + R2->>EP1: (8) OLC request (with QoS parameters) + EP1-->>GK: (9) OLC response (with QoS parameters) + GK->>R1: (10) QoS request + R1-->>GK: (11) QoS response + GK->>R2: (12) QoS request + R2-->>GK: (13) QoS response + GK->>EP2: (14) OLC response (with QoS parameters) + GK-->>EP1: (15) Connect + +``` + +H.361(06)\_F04 + +Sequence diagram illustrating H.323 QoS signalling via direct QoS negotiation between EP1, R1, GK, R2, and EP2. The diagram shows 15 numbered messages exchanged between these entities to establish a call with QoS parameters. + +**Figure 4/H.361 – H.323 QoS signalling via direct QoS negotiation** + +The GK shown in Figure 4 may be one or more gatekeepers in one or more service and network domains. Each gatekeeper is responsible for securing QoS in its local domain. If the called endpoint does not receive a fast-start message or a H.245 component in the setup message, it can consider that the calling endpoint is not capable of QoS synchronization. The called endpoint can then decide to decline the call based on the configured policies. + +## 8.4 Gatekeeper update + +Once the call is established, the endpoint is responsible to register any changes in **transportQoS** with the gatekeeper. For instance, if the average rate of the channel is more than what was originally negotiated in the ARQ message, then the endpoint must provide the correct information in the BRQ message. A revised **transportQoS** is used in the BRQ message to provide the corrected information regarding the channel. The BRQ is necessary even if the changes that occur in multiple streams result in no overall change to the requirements. + +If the gatekeeper receives a BRQ with a new QoSCapability, then the gatekeeper replaces the old QoSCapability with the new one and performs the admission control again for the new parameters. If admitted, then the gatekeeper returns a BCF. The QoSCapability can be optionally included in a BCF for indicating the DSCP value to be used for the stream. The gatekeeper sends a BRJ if it rejects the new BRQ. + +## 8.5 Authorization procedures + +The authorization process depends upon each domain. The authorization processes occur in the H.323 system as well as in the transport system. In the application plane, the **QoS**M, along with **QoS**PE, authorize the call and ensure that the end-user/call is allowed to ask for the level of QoS requested, i.e., the **servicePriority**, the **qosType**, the **qosValue** values, etc., are all within the limits allowed for the particular end-user/call. + +In the transport system, the network device may require authorization to permit the H.323 system to request and be granted the necessary resources. The authorization for the network resource request can be done in a couple of ways. In the direct-QoS method, where the **QoS**M pushes down the authorization along with the requirements to the relevant network entities, no additional authorization may be necessary except a trusted relationship between the **QoS**M and the network entities. The establishment of such trust is outside the scope of this Recommendation. In the path-coupled model, the network entity may be provided with the relevant credentials to authenticate the request. This can be done by including credentials within the QoS signalling message that the network device can trust. Another option is for the network device to approach the **QoS**M to verify if the request is genuine before proceeding. + +These authorization mechanisms will be covered in greater detail in a future annex of this Recommendation. + +## 8.6 Media exchange + +Most of the above procedures pertain to admission control and making sure that necessary resources are available in the network for the call. In addition, the endpoint may also provide in-band QoS signalling by marking the packets with the appropriate DSCP value. These markings help the media packets be classified, policed, queued and scheduled appropriately. More details on this aspect of QoS handling will be discussed further in an annex of this Recommendation. + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/raw.md b/marked/H/T-REC-H.362-201009-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ec704693f70f6b047ff524504e92ddac0011ac9d --- /dev/null +++ b/marked/H/T-REC-H.362-201009-I_PDF-E/raw.md @@ -0,0 +1,701 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.362** + +(09/2010) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Quality of service +architecture for audiovisual and multimedia services + +--- + +**A framework for adaptive end-to-end QoS +control based on variable bit-rate codecs in +wireless networks** + +Recommendation ITU-T H.362 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|--------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T H.362** + +# **A framework for adaptive end-to-end QoS control based on variable bit-rate codecs in wireless networks** + +## **Summary** + +Recommendation ITU-T H.362 describes a framework for adaptive end-to-end quality of service (QoS) control using variable bit-rate codecs in wireless networks. Specifically, this Recommendation describes a reference network architecture, functional entities, references points, a terminal architecture, and signalling flows between functional entities. The framework in this Recommendation can be used for application level QoS support to control the multimedia service quality adaptively in wireless networks where the network status may change over time. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.362 | 2010-09-13 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2011 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Adaptive QoS control framework for wireless networks ..... | 3 | +| 5.1 Reference network architecture ..... | 3 | +| 5.2 Functional entities ..... | 4 | +| 5.3 Interfaces between functional entities ..... | 5 | +| 5.4 Terminal architecture for codec mode control ..... | 5 | +| 5.5 Functional descriptions..... | 7 | + + + +# A framework for adaptive end-to-end QoS control based on variable bit-rate codecs in wireless networks + +# 1 Scope + +There are various wireless networks including 2G/3G/4G mobile networks, wireless LANs, and mobile WiMAX networks. On the other hand, there are various multi-rate codecs including ITU-T G.729.1, ITU-T G.722.2, and ITU-T H.264, which can provide variable bit rates and adaptability in the dynamic environment where the network status may change over time. + +Networks are being evolved toward the converged network where heterogeneous wired/wireless access networks are converged using the IP-based core network. Fixed mobile convergence (FMC) and fixed mobile substitution (FMS) are some examples. In such an environment, many of the QoS control mechanisms are employed in the core/access networks to manage QoS resources efficiently. However, this type of QoS control may not be sufficient to meet the end users' expectation from the end-to-end QoS perspective because QoS control at the application level is not involved. To provide more complete end-to-end QoS, the application level QoS support can be useful. This is particularly important when the network is not able to support QoS. One of the possible application level QoS mechanisms is codec-based QoS control which adjusts encoding parameters such as codec bit rate or codec mode according to the network status, e.g., wireless channel status. + +Various codec-based QoS mechanisms were proposed to control the codec bit rate and call capacity using the wireless channel information in diverse wireless networks. However, in the heterogeneous network environment, it is difficult to control QoS in a unified way and to achieve the desirable service quality. Therefore, it is useful to design a common framework to control the codec mode adaptively, according to the channel status in wireless networks and reflect the users' perceived quality. For achieving the objective, this Recommendation describes a framework for adaptive end-to-end QoS control using variable bit-rate codecs in wireless networks. Specifically, this Recommendation describes a reference network architecture, functional entities, references points, a terminal architecture, and signalling flows between functional entities. The stability of control loop and delayed feedback in the control path which may affect the service quality is important in such an adaptive QoS control; however, it is out of scope of this Recommendation. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T G.711.1] Recommendation ITU-T G.711.1 (2008), *Wideband embedded extension for G.711 pulse code modulation*. + +[ITU-T G.722.2] Recommendation ITU-T G.722.2 (2003), *Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)*. + +[ITU-T G.729.1] Recommendation ITU-T G.729.1 (2006), *G.729-based embedded variable bit-rate coder: An 8-32 kbit/s scalable wideband coder bitstream interoperable with G.729*. + +- [ITU-T H.245] Recommendation ITU-T H.245 (2008), *Control protocol for multimedia communication*. +- [ITU-T H.264] Recommendation ITU-T H.264 (2009), *Advanced video coding for generic audiovisual services*. +- [ITU-T H.323 v7] Recommendation ITU-T H.323 (2009), *Packet-based multimedia communications systems*. +- [ITU-T M.2301] Recommendation ITU-T M.2301 (2002), *Performance objectives and procedures for provisioning and maintenance of IP-based networks*. +- [ITU-T Y.1541] Recommendation ITU-T Y.1541 (2006), *Network performance objectives for IP-based services*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation does not use any particular terms defined elsewhere. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 base station (BS):** A radio receiver/transmitter that serves as the hub of the wireless access network and connects the wireless stations (WSTAs) to the IP-based network. + +**3.2.2 codec mode (CM):** A specific bit-rate of a variable bit-rate codec. + +**3.2.3 quality-of-service control function (QCF):** A service quality control function capable of managing the codec mode to control the amount of traffic from/to WSTAs or packet transfer characteristics such as delay, loss, and jitter. + +**3.2.4 variable bit-rate codec (VBRC):** A multi-mode codec which can support a set of variable bit rates, e.g., ITU-T G.711.1, ITU-T G.722.2, ITU-T G.729.1, and ITU-T H.264. + +**3.2.5 wireless station (WSTA):** A terminal which provides wireless access to the end user and is equipped with one or more variable bit-rate codec(s). + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|----------------------------------------------------| +| BS | Base Station | +| CI | Codec Information | +| CMC | Channel Measurement Command | +| CMC_REQ | Codec Mode Change Request | +| CMC_RESP | Codec Mode Change Response | +| CMCM | Codec Mode Control Module | +| COCM | Codec Operation Control Module | +| CQ | Channel Quality | +| CSMMF | Channel Status Measurement and Management Function | +| MDP | Multimedia Decoding Parameters | +| MEP | Multimedia Encoding Parameters | + +| | | +|--------|----------------------------------------| +| OSS | Operations Support System | +| PCF | Policy Control Function | +| PEM | Packet Evaluation Module | +| PMC | Packet Measurement Command | +| PMP | Packet Measurement Parameters | +| QCF | QoS Control Function | +| QoS | Quality of Service | +| QSF | QoS Signalling Function | +| RSSI | Received Signal Strength Indicator | +| RTP | Real-time Transport Protocol | +| RTSP | Real-time Streaming Protocol | +| RxCMCR | Received Codec Mode Change Request | +| SIP | Session Initiation Protocol | +| SIR | Signal-to-Interference Ratio | +| SQ | Service Quality | +| SQCF | Service Quality Control Function | +| SQMM | Service Quality Measurement Module | +| TxCMCR | Transmitting Codec Mode Change Request | +| VBRC | Variable Bit-Rate Codec | +| WAI | Wireless Access Interface | +| WCMM | Wireless Channel Measurement Module | +| WSTA | Wireless Station | + +# 5 Adaptive QoS control framework for wireless networks + +## 5.1 Reference network architecture + +Figure 1 shows a reference network architecture for adaptive QoS control using variable bit-rate codecs, which consists of wireless stations (WSTAs), base stations (BSs), QoS control functions (QCFs), wireless access networks, and an IP-based core network. + +Variable bit-rate codecs, such as ITU-T G.711.1, ITU-T G.722.2, ITU-T G.729.1, and ITU-T H.264, can be employed at each WSTA for multimedia services and used for adaptive QoS control when the network experiences QoS degradation due to poor wireless channel quality or packet transfer performance, e.g., high packet loss, delay, and jitter. When a WSTA detects the quality of the wireless channel, it can communicate with a QCF in the local site where the WSTA is located and its counterpart WSTA in the remote site to control the codec mode. QCFs in the local and remote sites can communicate with each other to exchange the codec mode information of the WSTAs. + +![Figure 1: Conceptual reference network architecture for adaptive QoS control using variable bit-rate codecs. The diagram shows a network architecture with three main components: Wireless Access Network (1), IP Backbone Network, and Wireless Access Network (2). On the left, a Wireless Station (WSTA) is connected to a Base Station (BS) via a media path (solid line) and a control path (dashed line). The BS is connected to the IP Backbone Network via a media path. The IP Backbone Network contains an IP node (I3). On the right, the IP Backbone Network is connected to another Base Station (BS) via a media path. This BS is connected to another Wireless Station (WSTA) via a media path and a control path. Each BS is associated with a QoS Control Function (QCF). The QCFs are connected to the IP Backbone Network via control paths. The WSTA on the left has four control paths labeled I1, I2, I3, and I4. The legend indicates that a dashed line represents a control path and a solid line represents a media path.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Figure 1: Conceptual reference network architecture for adaptive QoS control using variable bit-rate codecs. The diagram shows a network architecture with three main components: Wireless Access Network (1), IP Backbone Network, and Wireless Access Network (2). On the left, a Wireless Station (WSTA) is connected to a Base Station (BS) via a media path (solid line) and a control path (dashed line). The BS is connected to the IP Backbone Network via a media path. The IP Backbone Network contains an IP node (I3). On the right, the IP Backbone Network is connected to another Base Station (BS) via a media path. This BS is connected to another Wireless Station (WSTA) via a media path and a control path. Each BS is associated with a QoS Control Function (QCF). The QCFs are connected to the IP Backbone Network via control paths. The WSTA on the left has four control paths labeled I1, I2, I3, and I4. The legend indicates that a dashed line represents a control path and a solid line represents a media path. + +**Figure 1 – Conceptual reference network architecture for adaptive QoS control using variable bit-rate codecs** + +## 5.2 Functional entities + +### 5.2.1 Wireless station + +A wireless station (WSTA) is a terminal which provides wireless access to the end user and is equipped with one or more variable bit-rate codecs. The WSTA monitors the signal strength of the downlink channel and measures key performance parameters such as signal-to-interference ratio (SIR). The WSTA also measures perceived service quality by examining received packets and utilizing an objective quality measurement method. Based on the measurement result, the WSTA determines if the codec mode needs to be changed. If it is necessary to change the codec mode for QoS control, the WSTA sends a codec mode change request to the QCF in the local site where the WSTA is associated. It is also possible for the WSTA to have a service quality control function (SQCF) that can control the codec mode, according to the measured wireless channel quality and packet transfer performance and to communicate with the SQCF in the remote WSTA. + +### 5.2.2 Base station + +A base station (BS) is a radio receiver/transmitter that serves as the hub of the wireless access network, which communicates with the WSTA. The BS monitors the signal strength of the uplink channel and measures key performance parameters such as SIR. After measuring the uplink channel quality, the BS calculates the adequate signal power for uplink transmission and commands the WSTA to control the uplink signal power, if necessary. If there is any request from the WSTA to change the downlink signal power, the BS adjusts the downlink signal power for packet transmission. + +### 5.2.3 QoS control function + +A QoS control function (QCF) is a service quality control function which manages the codec mode to control the amount of traffic from/to the WSTA or packet transfer performance such as delay, loss, and jitter, etc. If there is a codec mode change request in the direction of downlink, the QCF communicates with the remote QCF that is located near the remote WSTA to check whether the codec mode change is possible. If it is possible, the remote QCF instructs the remote WSTA to change the codec mode. A SQCF has a similar function to the QCF but it exists in the WSTA. The SQCF can communicate with the QCF in the network or with the SQCF in the remote WSTA to directly control the codec mode. + +### **5.2.4 Variable bit-rate codec (VBRC)** + +A variable bit-rate codec (VBRC) provides variable bit-rates to support multimedia services in the network where the available amount of network resources may vary. Examples include ITU-T G.711.1, ITU-T G.722.2, ITU-T G.729.1, and ITU-T H.264. + +## **5.3 Interfaces between functional entities** + +### **5.3.1 I1** + +I1 is the reference point between a WSTA and a BS. Using the I1, the WSTA and the BS measure the quality of the wireless channel and examine received packets to see if there is any need to change the codec mode. + +### **5.3.2 I2** + +I2 is the reference point between a WSTA and a QCF. The WSTA exchanges the codec mode control messages with the QCF for QoS control through the I2. + +### **5.3.3 I3** + +I3 is the reference point between QCFs which are located in the different wireless access networks. QCFs negotiate the codec mode for packet transmission between WSTAs through the I3. + +### **5.3.4 I4** + +I4 is the reference point between WSTAs which are located in the different wireless access networks. The SQCF of the WSTA is used to negotiate the codec mode with the SQCF of the remote WSTA through the I4. + +## **5.4 Terminal architecture for codec mode control** + +### **5.4.1 Terminal architecture and components** + +As depicted in Figure 2, a WSTA is comprised of wireless access interfaces, codec mode control functions for controlling multimedia service quality, and multimedia terminal components for processing multimedia data. A call server may contain a call processing unit and a policy control function. + +The codec mode control functions in the WSTA include the channel status measurement and management function (CSMMF), the service quality control function (SQCF), and the QoS signalling function (QSF). The policy control function (PCF) in the call server can also be used for codec mode control according to the policy. + +The CSMMF is subdivided into the wireless channel measurement module (WCMM) and the packet evaluation module (PEM). The SQCF is subdivided into the service quality measurement module (SQMM), the codec mode control module (CMCM), and the codec operation control module (COCM). + +![Figure 2 – Terminal architecture for codec mode control. The diagram shows a WSTA (Wireless Station) architecture with internal components and external connections. On the left, a Call server (containing a Call processing unit and Policy control function) is connected to a PCF (Policy Control Function), which is connected to an Internet backbone and a BS (Base Station). The WSTA contains H/W components (wireless access interfaces), a Wireless access interface (receiver), and a Wireless access interface (transmitter). The internal architecture includes a Multimedia packet stream, CSMMF (Channel Status Measurement and Management Function) with Wireless channel measurement module and Packet evaluation module, SQCF (Service Quality Control Function) with Service quality measurement module and Codec operation control module, and QSF (QoS Signalling Function) with QoS signalling function. The MMoIP terminal components include RTP packet decapsulator, Adaptive playout unit, VBR decoder, Multimedia processing units, and Multimedia device interface for decoding. Encoding components include RTP packet encapsulator, VBR encoder, Multimedia processing units, and Multimedia device interface for encoding. A legend at the bottom defines the acronyms: CSMMF, SQCF, QSF, and PCF. Icons for a speaker, monitor, camera, and microphone are shown on the right.](d4af765160d04ecef538e5066006dc77_img.jpg) + +H.362(10)\_F02 + +CSMMF Channel Status Measurement and Management Function + SQCF Service Quality Control Function + QSF QoS Signalling Function + PCF Policy Control Function + +[Codec mode control module] [Multimedia terminal component] + +Figure 2 – Terminal architecture for codec mode control. The diagram shows a WSTA (Wireless Station) architecture with internal components and external connections. On the left, a Call server (containing a Call processing unit and Policy control function) is connected to a PCF (Policy Control Function), which is connected to an Internet backbone and a BS (Base Station). The WSTA contains H/W components (wireless access interfaces), a Wireless access interface (receiver), and a Wireless access interface (transmitter). The internal architecture includes a Multimedia packet stream, CSMMF (Channel Status Measurement and Management Function) with Wireless channel measurement module and Packet evaluation module, SQCF (Service Quality Control Function) with Service quality measurement module and Codec operation control module, and QSF (QoS Signalling Function) with QoS signalling function. The MMoIP terminal components include RTP packet decapsulator, Adaptive playout unit, VBR decoder, Multimedia processing units, and Multimedia device interface for decoding. Encoding components include RTP packet encapsulator, VBR encoder, Multimedia processing units, and Multimedia device interface for encoding. A legend at the bottom defines the acronyms: CSMMF, SQCF, QSF, and PCF. Icons for a speaker, monitor, camera, and microphone are shown on the right. + +**Figure 2 – Terminal architecture for codec mode control** + +### 5.4.2 Functional procedure for codec mode control + +When a call or session set-up is requested by a WSTA, the call server decides admission of the call based on the resource availability and/or the admission policy. After the call is accepted, the WCMM of the WSTA measures the wireless channel quality through the physical interface within the WSTA, and delivers the measurement results to the CMCM. + +The PEM assesses the transfer performance of the received multimedia packets and control packets sent by the remote WSTA, and it delivers the assessment results to the SQMM. Then the SQMM evaluates the quality of the received packets during the call or session, using an objective quality measurement method. + +After receiving the quality assessment results, the CMCM determines the appropriate codec mode of the VBRC using the information on the wireless channel quality received from the WCMM and the service quality assessed by the SQMM. When it is necessary to change the codec mode, the CMCM instructs the QSF to change the codec mode of the remote WSTA. Then, the QSF generates a signalling message which carries the codec mode information. + +When the signalling message is transferred through the configured networks and arrived at the remote WSTA, the PEM of the WSTA delivers the newly received codec mode to the COCM. The COCM finally changes the codec mode of the VBR codec for the multimedia content source. + +## 5.5 Functional descriptions + +### 5.5.1 Channel status measurement and management function (CSMMF) + +The CSMMF measures the wireless channel quality through a wireless interface (PHY/MAC) within a WSTA. It also evaluates the packet transfer performance including delay, jitter, and loss by examining the multimedia packets transmitted by a remote WSTA. The information on the wireless channel quality and the packet transfer performance is delivered to the SQCF to control the codec mode of the remote WSTA during a call or session. + +The CSMMF consists of WCMM and PEM, as shown in Figure 3. + +![Figure 3: Channel status measurement and management function (CSMMF) block diagram. The diagram shows the internal components of the CSMMF and its interaction with the SQCF and the external wireless access interface. The CSMMF contains a Packet evaluation module and a Wireless channel measurement module. The Packet evaluation module receives a multimedia packet stream and sends a packet measurement command to the Wireless channel measurement module. The Wireless channel measurement module sends channel measurement parameters to the PHY/MAC register and receives primitive access from it. The CSMMF also interacts with the SQCF, which contains CMCM, COCM, and SQMM modules. The CSMMF sends channel measurement commands to the CMCM and receives channel quality from it. The CSMMF also sends received codec mode change requests to the COCM and receives multimedia decoding parameters from it. The CSMMF also sends packet measurement parameters to the SQMM. The SQCF sends channel measurement commands to the CMCM and receives channel quality from it. The SQCF also sends received codec mode change requests to the COCM and receives multimedia decoding parameters from it. The SQCF also sends packet measurement parameters to the SQMM. The PHY/MAC frame processing unit and PHY/MAC register are part of the wireless access interface (receiver). The PHY/MAC register receives channel measurement parameters from the Wireless channel measurement module and sends primitive access to it. The PHY/MAC frame processing unit sends a multimedia packet stream to the Packet evaluation module. The diagram is labeled H.362(10)_F03 at the bottom right.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +Figure 3 is a block diagram of the Channel status measurement and management function (CSMMF). The CSMMF is shown as a large dashed box containing two main modules: the Packet evaluation module and the Wireless channel measurement module. The Packet evaluation module receives a 'Multimedia packet stream' from the 'PHY/MAC frame processing unit' (part of the 'Wireless access interface (receiver)'). It sends a 'Packet measurement command' to the Wireless channel measurement module. The Wireless channel measurement module sends 'Channel measurement parameters' to the 'PHY/MAC register' (part of the 'Wireless access interface (receiver)') and receives 'Primitive access' from it. The CSMMF also interacts with the 'Service quality control function (SQCF)', which contains three modules: CMCM (Codec Mode Control Module), COCM (Codec Operation Control Module), and SQMM (Service Quality Measurement Module). The CSMMF sends 'Channel measurement command' to the CMCM and receives 'Channel quality' from it. The CSMMF also sends 'Received codec mode change request' to the COCM and receives 'Multimedia decoding parameters' from it. The CSMMF also sends 'Packet measurement parameters' to the SQMM. The SQCF sends 'Channel measurement command' to the CMCM and receives 'Channel quality' from it. The SQCF also sends 'Received codec mode change request' to the COCM and receives 'Multimedia decoding parameters' from it. The SQCF also sends 'Packet measurement parameters' to the SQMM. The 'External function' is shown as a dashed box containing the 'PHY/MAC frame processing unit' and 'PHY/MAC register'. + +CMCM Codec Mode Control Module +COCM Codec Operation Control Module +SQMM Service Quality Measurement Module + +H.362(10)\_F03 + +Figure 3: Channel status measurement and management function (CSMMF) block diagram. The diagram shows the internal components of the CSMMF and its interaction with the SQCF and the external wireless access interface. The CSMMF contains a Packet evaluation module and a Wireless channel measurement module. The Packet evaluation module receives a multimedia packet stream and sends a packet measurement command to the Wireless channel measurement module. The Wireless channel measurement module sends channel measurement parameters to the PHY/MAC register and receives primitive access from it. The CSMMF also interacts with the SQCF, which contains CMCM, COCM, and SQMM modules. The CSMMF sends channel measurement commands to the CMCM and receives channel quality from it. The CSMMF also sends received codec mode change requests to the COCM and receives multimedia decoding parameters from it. The CSMMF also sends packet measurement parameters to the SQMM. The SQCF sends channel measurement commands to the CMCM and receives channel quality from it. The SQCF also sends received codec mode change requests to the COCM and receives multimedia decoding parameters from it. The SQCF also sends packet measurement parameters to the SQMM. The PHY/MAC frame processing unit and PHY/MAC register are part of the wireless access interface (receiver). The PHY/MAC register receives channel measurement parameters from the Wireless channel measurement module and sends primitive access to it. The PHY/MAC frame processing unit sends a multimedia packet stream to the Packet evaluation module. The diagram is labeled H.362(10)\_F03 at the bottom right. + +Figure 3 – Channel status measurement and management function (CSMMF) + +#### 5.5.1.1 Wireless channel measurement module (WCMM) + +The WCMM evaluates the wireless channel quality by examining packets which are received via the air interface and contain the information on various characteristics, including signal strength and transmission rates. The WCMM delivers the quality evaluation results obtained during a communication session to the SQCF to control the codec mode. + +When a WSTA completes a call set-up procedure and before transmitting the media packets to its remote WSTA, the SQCF of the WSTA instructs the WCMM to collect the wireless channel information with a channel measurement command (CMC). If the WCMM receives the CMC from the CMCM of the SQCF, the WCMM instructs the wireless access interface (WAI) to measure the wireless channel status using a primitive access command. After receiving the primitive access command, the WAI measures the wireless channel quality and reports the measured channel measurement parameters (CMPs) to the WCMM. The WCMM gathers the wireless CMPs such as the SIR of the received frame, frame transmission rate and frame loss ratio through the wireless interface within the WSTA. The WCMM evaluates the channel quality (CQ) using the CMPs and delivers the CQ to the CMCM in the SQCF. + +![Figure 4 – Signalling flow for the wireless channel measurement module (WCMM). The diagram shows three entities: WAI (Receiver) on the left, Wireless channel measurement module in the center, and SQCF (CMCM) on the right. The flow is: 1. A 'Channel measurement command' is sent from the SQCF (CMCM) to the Wireless channel measurement module. 2. The Wireless channel measurement module sends a 'Primitive access' message to the WAI (Receiver). 3. The WAI (Receiver) sends 'Channel measurement parameters' back to the Wireless channel measurement module. 4. Finally, the Wireless channel measurement module sends 'Channel quality' information to the SQCF (CMCM). The diagram is labeled H.362(10)_F04 at the bottom right.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Figure 4 – Signalling flow for the wireless channel measurement module (WCMM). The diagram shows three entities: WAI (Receiver) on the left, Wireless channel measurement module in the center, and SQCF (CMCM) on the right. The flow is: 1. A 'Channel measurement command' is sent from the SQCF (CMCM) to the Wireless channel measurement module. 2. The Wireless channel measurement module sends a 'Primitive access' message to the WAI (Receiver). 3. The WAI (Receiver) sends 'Channel measurement parameters' back to the Wireless channel measurement module. 4. Finally, the Wireless channel measurement module sends 'Channel quality' information to the SQCF (CMCM). The diagram is labeled H.362(10)\_F04 at the bottom right. + +**Figure 4 – Signalling flow for the wireless channel measurement module (WCMM)** + +#### 5.5.1.2 Packet evaluation module (PEM) + +The PEM assesses the packet transfer performance such as delay, jitter, and loss by examining multimedia packets and control packets sent by a remote WSTA. Additionally, the PEM extracts parameters for variable bit-rate codec operation from the received packets to utilize them for service quality control. + +After starting a media session with a remote WSTA, the CMCM of the SQCF in the current WSTA sends the packet measurement command (PMC) to the PEM. When the PEM receives the PMC, the PEM evaluates the packet transfer performance by examining the received multimedia packets through the WAI. As a result, packet measurement parameters (PMPs) such as delay, jitter, and loss are assessed. Then the measured PMPs are delivered to the SQMM of the SQCF and used to measure the multimedia service quality. + +The PEM also extracts the multimedia decoding parameters (MDPs) from the received multimedia packets and delivers them to the COCM of the SQCF. The COCM uses the MDPs to select a sampling rate of the multimedia decoder, a type of media (e.g., mono/stereo), a decoding rate, a compatible mode, and other parameters. + +Another function of the PEM is to capture a codec mode change request (CMC\_REQ) message transmitted from the remote WSTA. When the PEM receives the CMC\_REQ message, it extracts the codec mode control parameters such as a sampling rate, a type of media (e.g., mono/stereo), a coding rate, a compatibility mode, from the CMC\_REQ message, indicates the reception of the CMC\_REQ to the CMCM of the SQCF with the received codec mode change request (RxCMCR) command and delivers the parameters to the CMCM which will decide a proper codec mode for the WSTA. + +![Figure 5: Signalling flow for the packet evaluation module (PEM). The diagram shows a sequence of messages between a WAI (Receiver), a Packet evaluation module, and an SQCF (containing CMCM, SQMM, and COCM).](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +sequenceDiagram + participant WAI as WAI (Receiver) + participant PEM as Packet evaluation module + subgraph SQCF + CMCM + SQMM + COCM + end + WAI->>PEM: Multimedia packet stream + PEM->>CMCM: Packet measurement command + CMCM->>PEM: Packet measurement parameters + PEM->>SQMM: Multimedia decoding parameters + PEM->>COCM: Received codec mode change request (codec mode control parameters) + +``` + +H.362(10)\_F05 + +Figure 5: Signalling flow for the packet evaluation module (PEM). The diagram shows a sequence of messages between a WAI (Receiver), a Packet evaluation module, and an SQCF (containing CMCM, SQMM, and COCM). + +**Figure 5 – Signalling flow for the packet evaluation module (PEM)** + +### 5.5.2 Service quality control function (SQCF) + +The SQCF receives the wireless channel quality information, the packet transfer performance, and the codec-related information from the CSMMF, and then it measures the service quality based on the received quality information and controls the codec mode of the remote WSTA according to the measured service quality. + +When the WSTA determines that it is necessary to change the codec mode of the remote WSTA, the SQCF in the WSTA requests the QSF to transmit a CMC\_REQ message with the transmitting codec mode change request (TxCMCR) command to the remote WSTA in order to change the codec mode of the remote WSTA. When the WSTA receives a CMC\_REQ message, the SQCF instructs the QSF to respond to the remote WSTA with the Response-to-the-CMC\_REQ (RspCMCR) command. + +The SQCF calculates the service quality (SQ) based on the PMPs and CI and reports the quality to the CMCM. The CMCM controls the codec mode of the remote WSTA based on the SQ and the received codec mode control parameters (CMCPs) from the PCF. + +In addition, the SQCF controls the VBR decoder with the MDPs extracted from the received packets during a call or session. The SQCF also applies the codec mode control parameters in the RxCMCR command from the remote WSTA to the VBR encoder. + +The SQCF consists of SQMM, COCM and CMCM, as shown in Figure 6. + +![Figure 6 – Service quality control function (SQCF) block diagram. The diagram shows the internal components of the SQCF and its interactions with external functions. The SQCF contains a Codec mode control module, a Service quality measurement module, and a Codec operation control module. It interacts with the Channel status measurement and management function (CSMMF), the QoS signalling function (QSF), the Policy control function (PCF), and a VBR multimedia codec. Various control signals and parameters are shown between these components.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +The diagram illustrates the Service quality control function (SQCF) and its interactions. The SQCF is a central block containing three main modules: the Codec mode control module, the Service quality measurement module, and the Codec operation control module. The Codec mode control module is connected to the QoS signalling function (QSF) via TxCMCR and RspCMCR signals. It also receives CQ, CMC, PMC, RxRspCMCR, RxCMCR, PMP, and MDP signals from the Channel status measurement and management function (CSMMF). The Service quality measurement module receives SQ from the Codec mode control module and CI from the Policy control function (PCF). The Codec operation control module receives MEP from the Codec mode control module and MDP from the CSMMF. It sends Encoding parameters and Decoding parameters to the VBR multimedia codec. The CSMMF contains the Wireless channel measurement module and the Packet evaluation module. The PCF is an external function that provides CMCP to the Codec mode control module and CI to the Service quality measurement module. The VBR multimedia codec is an external function that receives Encoding parameters and Decoding parameters from the Codec operation control module. + +Legend: + +- CI: Codec Information +- CMC: Channel Measurement Command +- CMCP: Codec Mode Control Parameters +- CQ: Channel Quality +- PMC: Packet Measurement Command +- PMP: Packet Measurement Parameters +- MDP: Multimedia Decoding Parameters +- MEP: Multimedia Encoding Parameters +- SQ: Service Quality +- RxCMCR: Received Codec Mode Change Request +- TxCMCR: Transmitting Codec Mode Change Request +- RspCMCR: Response to the Codec Mode Change Request +- RxRspCMCR: Received RspCMCR + +Figure 6 – Service quality control function (SQCF) block diagram. The diagram shows the internal components of the SQCF and its interactions with external functions. The SQCF contains a Codec mode control module, a Service quality measurement module, and a Codec operation control module. It interacts with the Channel status measurement and management function (CSMMF), the QoS signalling function (QSF), the Policy control function (PCF), and a VBR multimedia codec. Various control signals and parameters are shown between these components. + +**Figure 6 – Service quality control function (SQCF)** + +#### 5.5.2.1 Service quality measurement module (SQMM) + +During a call or session, the SQMM evaluates the service quality using the information on the packet transfer performance and codec information (CI) delivered from the PCF. The quality evaluation occurs in the WSTA using an objective quality measurement method. The assessed service quality information is delivered to the CMCM for the codec mode control, see Figure 7. + +Before measuring the multimedia service quality, the CMCM instructs the PEM of the CSMMF to measure the packet transfer performance with the PMC. When the PEM receives the PMC, it measures the packet transfer performance and reports the PMPs to the SQMM. The SQMM evaluates the service quality by using the PMPs such as delay, jitter, and loss received from the PEM and the CI of the remote WSTA received from the PCF. Then the SQMM delivers the evaluated SQ to the CMCM, and the CMCM utilizes the evaluated quality to control the codec mode of the remote WSTA. + +![Figure 7: Signalling flow to measure the service quality. This sequence diagram shows four lifelines: Policy Control Function (PCF), Service Quality Measurement Module (SQMM), Code Mode Control Module (CMCM), and Packet Evaluation Module (PEM). The flow starts with the PCF sending 'Codec Information' to the SQMM. The SQMM then sends 'Service Quality' to the CMCM. The CMCM sends a 'Packet Measurement Command' to the PEM. The PEM responds with 'Packet Measurement Parameters' to the CMCM, which in turn sends 'Packet Measurement Parameters' to the SQMM.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant PCF as Policy Control Function (PCF) + participant SQMM as Service Quality Measurement Module + participant CMCM as Code Mode Control Module + participant PEM as Packet Evaluation Module + Note left of PCF: + PCF->>SQMM: Codec Information + Note right of SQMM: + SQMM->>CMCM: Service Quality + Note right of CMCM: + CMCM->>PEM: Packet Measurement Command + Note right of PEM: + PEM-->>CMCM: Packet Measurement Parameters + Note right of CMCM: + CMCM->>SQMM: Packet Measurement Parameters + +``` + +Figure 7: Signalling flow to measure the service quality. This sequence diagram shows four lifelines: Policy Control Function (PCF), Service Quality Measurement Module (SQMM), Code Mode Control Module (CMCM), and Packet Evaluation Module (PEM). The flow starts with the PCF sending 'Codec Information' to the SQMM. The SQMM then sends 'Service Quality' to the CMCM. The CMCM sends a 'Packet Measurement Command' to the PEM. The PEM responds with 'Packet Measurement Parameters' to the CMCM, which in turn sends 'Packet Measurement Parameters' to the SQMM. + +Figure 7 – Signalling flow to measure the service quality + +##### 5.5.2.2 Codec mode control module (CMCM) + +The CMCM determines the codec mode of the VBRC of the remote WSTA based on the information on the wireless channel quality received from the CSMMF and the service quality assessed by the SQMM. + +##### Case I: Changing the codec mode of the remote WSTA + +The CMCM sends the CMC to the WCMM in order to measure the wireless channel quality, and dispatches the PMC to the PEM in order to evaluate the packet transfer performance. The CMC and PMC have information on a predetermined interval for which the WCMM and PEM measure the wireless channel quality and packet transfer performance periodically. Upon receiving the CMC, the WCMM extracts information on the measurement interval, and it measures the wireless channel quality during the interval. After finishing the measurement during the interval, the WCMM reports the CQ, which is the result of channel measurement, to the CMCM. This is illustrated in Figure 8. + +![Figure 8: Signalling flow to change the codec mode of the remote WSTA. This sequence diagram shows six lifelines: Policy Control Function (PCF), Wireless Channel Measurement Module (WCMM), Code Mode Control Module (CMCM), Packet Evaluation Module (PEM), Service Quality Measurement Module (SQMM), and QoS Signalling Function (QoS SF). The process starts with a 'TX: Codec Mode Change Request' box. The PCF sends 'Codec Mode Control Parameters' to the WCMM. The WCMM sends a 'Channel Measurement Command' to the CMCM. The CMCM sends a 'Packet Measurement Command' to the PEM. The PEM responds with 'Packet Measurement Parameters' to the CMCM, which then sends 'Packet Measurement Parameters' to the SQMM. The SQMM sends 'Service Quality' to the CMCM. Finally, the CMCM sends a 'Transmitting Codec Mode Change Request' to the QoS SF. The WCMM also sends 'Channel Quality' to the CMCM.](21ad58fee90f2be50708ff541d225507_img.jpg) + +``` + +sequenceDiagram + participant PCF as Policy Control Function (PCF) + participant WCMM as Wireless Channel Measurement Module + participant CMCM as Code Mode Control Module + participant PEM as Packet Evaluation Module + participant SQMM as Service Quality Measurement Module + participant QoS SF as QoS Signalling Function + Note left of PCF: TX: Codec Mode Change Request + PCF->>WCMM: Codec Mode Control Parameters + Note right of WCMM: + WCMM->>CMCM: Channel Measurement Command + Note right of CMCM: + CMCM->>PEM: Packet Measurement Command + Note right of PEM: + PEM-->>CMCM: Packet Measurement Parameters + Note right of CMCM: + CMCM->>SQMM: Packet Measurement Parameters + Note right of SQMM: + SQMM->>CMCM: Service Quality + Note right of CMCM: + CMCM->>QoS SF: Transmitting Codec Mode Change Request + Note right of WCMM: + WCMM->>CMCM: Channel Quality + +``` + +Figure 8: Signalling flow to change the codec mode of the remote WSTA. This sequence diagram shows six lifelines: Policy Control Function (PCF), Wireless Channel Measurement Module (WCMM), Code Mode Control Module (CMCM), Packet Evaluation Module (PEM), Service Quality Measurement Module (SQMM), and QoS Signalling Function (QoS SF). The process starts with a 'TX: Codec Mode Change Request' box. The PCF sends 'Codec Mode Control Parameters' to the WCMM. The WCMM sends a 'Channel Measurement Command' to the CMCM. The CMCM sends a 'Packet Measurement Command' to the PEM. The PEM responds with 'Packet Measurement Parameters' to the CMCM, which then sends 'Packet Measurement Parameters' to the SQMM. The SQMM sends 'Service Quality' to the CMCM. Finally, the CMCM sends a 'Transmitting Codec Mode Change Request' to the QoS SF. The WCMM also sends 'Channel Quality' to the CMCM. + +Figure 8 – Signalling flow to change the codec mode of the remote WSTA + +The PEM assesses the packet transfer performance from the received media packets after receiving the PMC, and conveys the performance evaluation result using the PMPs to the SQMM. The SQMM calculates the SQ based on the PMPs and CI, and reports the SQ to the CMCM. The CMCM controls the codec mode of the remote WSTA based on the CQ from the WCMM, the SQ from the SQMM and the received CMCPs from the PCF. The CMCPs may include a service level and supported codec modes that are available for the remote WSTA. If there is a need to change the codec mode of the remote WSTA, the CMCM requests the QSF to transmit a CMC\_REQ message with the TxCMCR command to a remote WSTA to change the codec mode of the remote WSTA. + +##### Case II: Applying the codec mode change request from the remote WSTA + +When the PEM receives the CMC\_REQ message from the remote WSTA, the PEM extracts the codec mode control parameters from the CMC\_REQ. Then the PEM delivers the RxCMCR command including the codec mode control parameters to the CMCM of the SQCF. Upon receiving the codec mode control parameters, the CMCM conveys the multimedia encoding parameters (MEPs) extracted from the codec mode control parameters to the COCM. The COCM applies the MEPs to the multimedia encoder. See Figure 9. + +![Figure 9: Signalling flow to apply the received codec mode change request. The diagram shows four modules: Codec Mode Control Module, Packet Evaluation Module, Codec Operation Control Module, and Multimedia Encoder. The flow starts with an external 'RX: Codec Mode Change Request' entering the Packet Evaluation Module. From there, 'Received Codec Mode Change Request (codec mode control parameters)' are sent to the Codec Mode Control Module. The Codec Mode Control Module then sends 'Multimedia Encoding Parameters' to the Codec Operation Control Module. Finally, the Codec Operation Control Module sends 'Encoding Parameters' to the Multimedia Encoder.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant External + participant CMCM as Codec Mode Control Module + participant PEM as Packet Evaluation Module + participant COCM as Codec Operation Control Module + participant ME as Multimedia Encoder + + Note over External: RX: Codec Mode Change Request + External->>PEM: + PEM->>CMCM: Received Codec Mode Change Request (codec mode control parameters) + CMCM->>COCM: Multimedia Encoding Parameters + COCM->>ME: Encoding Parameters + +``` + +Figure 9: Signalling flow to apply the received codec mode change request. The diagram shows four modules: Codec Mode Control Module, Packet Evaluation Module, Codec Operation Control Module, and Multimedia Encoder. The flow starts with an external 'RX: Codec Mode Change Request' entering the Packet Evaluation Module. From there, 'Received Codec Mode Change Request (codec mode control parameters)' are sent to the Codec Mode Control Module. The Codec Mode Control Module then sends 'Multimedia Encoding Parameters' to the Codec Operation Control Module. Finally, the Codec Operation Control Module sends 'Encoding Parameters' to the Multimedia Encoder. + +Figure 9 – Signalling flow to apply the received codec mode change request + +#### 5.5.2.3 Codec operation control module (COCM) + +The COCM applies the parameters such as sampling rates, types of media (e.g., mono/stereo), coding rates, and compatibility modes delivered from the PEM and CMCM to the VBRC for encoding and decoding the multimedia content source. + +##### Case I: Media decoding + +Upon receiving a multimedia packet such as an RTP packet from a remote WSTA, the PEM extracts information for media decoding such as a sampling rate, a type of media (e.g., mono/stereo), a decoding rate, a compatibility mode, etc. This decoding information is encapsulated in the MDPs and delivered to the COCM. The COCM which receives the MDPs applies the decoding parameters to the media decoder. This is illustrated in Figure 10. + +![Figure 10: Signalling flow to apply the multimedia decoding parameters. The diagram shows a sequence of four components: RX: Multimedia Packet, Packet Evaluation Module (dashed box), Codec Operation Control Module, and Multimedia Codec (dashed box). Arrows indicate the flow of parameters: 'Multimedia Decoding Parameters' from the Packet Evaluation Module to the Codec Operation Control Module, and 'Decoding Parameters' from the Codec Operation Control Module to the Multimedia Codec.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +sequenceDiagram + participant RX as RX: Multimedia Packet + participant PEM as Packet Evaluation Module + participant COCM as Codec Operation Control Module + participant MC as Multimedia Codec + Note left of PEM: RX: Multimedia Packet + PEM->>COCM: Multimedia Decoding Parameters + COCM->>MC: Decoding Parameters + +``` + +Figure 10: Signalling flow to apply the multimedia decoding parameters. The diagram shows a sequence of four components: RX: Multimedia Packet, Packet Evaluation Module (dashed box), Codec Operation Control Module, and Multimedia Codec (dashed box). Arrows indicate the flow of parameters: 'Multimedia Decoding Parameters' from the Packet Evaluation Module to the Codec Operation Control Module, and 'Decoding Parameters' from the Codec Operation Control Module to the Multimedia Codec. + +**Figure 10 – Signalling flow to apply the multimedia decoding parameters** + +##### **Case II: Media encoding (at the call set-up stage)** + +When a call is set up, the COCM instructs the encoder to operate with the MEPs that include a sampling rate, a type of media (e.g., mono/stereo), an encoding rate, and a compatibility mode, which are decided at the call set-up stage. + +##### **Case III: Media encoding (when receiving the codec mode change request message)** + +When the PEM receives the CMC\_REQ message from the remote WSTA, it extracts the codec mode control parameters from the CMC\_REQ, indicates the reception of the CMC\_REQ with the RxCMCR command, and delivers the parameters to the CMCM. Upon receiving the RxCMCR command including the codec mode control parameters, the CMCM determines whether it should apply the received codec mode. If the CMCM decides to change the codec mode, the MEPs are delivered to the COCM to change the codec mode of the involved WSTA. The COCM which receives the MEPs applies the encoding parameters based on the received codec mode to the media encoder. This is illustrated in Figure 11. + +![Figure 11: Signalling flow to apply the multimedia encoding parameters. The diagram shows four components: TX: Multimedia Packet, Codec Mode Control Module, Packet Evaluation Module (dashed box), Codec Operation Control Module, and Multimedia Codec (dashed box). Arrows indicate the flow: 'Received Codec Mode Change Request (codec mode control parameters)' from the Packet Evaluation Module to the Codec Mode Control Module, 'Multimedia Encoding Parameters' from the Packet Evaluation Module to the Codec Operation Control Module, and 'Encoding Parameters' from the Codec Operation Control Module to the Multimedia Codec.](a734898ce18e972938949637c32a34f4_img.jpg) + +``` + +sequenceDiagram + participant CMCM as Codec Mode Control Module + participant PEM as Packet Evaluation Module + participant COCM as Codec Operation Control Module + participant MC as Multimedia Codec + Note left of CMCM: TX: Multimedia Packet + PEM->>CMCM: Received Codec Mode Change Request (codec mode control parameters) + PEM->>COCM: Multimedia Encoding Parameters + COCM->>MC: Encoding Parameters + +``` + +Figure 11: Signalling flow to apply the multimedia encoding parameters. The diagram shows four components: TX: Multimedia Packet, Codec Mode Control Module, Packet Evaluation Module (dashed box), Codec Operation Control Module, and Multimedia Codec (dashed box). Arrows indicate the flow: 'Received Codec Mode Change Request (codec mode control parameters)' from the Packet Evaluation Module to the Codec Mode Control Module, 'Multimedia Encoding Parameters' from the Packet Evaluation Module to the Codec Operation Control Module, and 'Encoding Parameters' from the Codec Operation Control Module to the Multimedia Codec. + +**Figure 11 – Signalling flow to apply the multimedia encoding parameters** + +#### **5.5.3 QoS signalling function (QSF)** + +As illustrated in Figure 12, after the QSF of a WSTA receives the codec mode change request command, TxCMCR, from the SQCF, the QSF generates a signalling message, CMC\_REQ, which includes the codec mode control parameters to change the codec mode of a remote WSTA. The CMC\_REQ message is transferred to the remote WSTA through the configured networks. At the remote site, the PEM of the remote WSTA receiving the CMC\_REQ message, which is equally considered as the RxCMCR in the receiver, extracts the codec mode control parameters from the RxCMCR and delivers the extracted parameters to the CMCM. + +When the CMCM of the WSTA in the remote site receives the CMC\_REQ message, the CMCM requests the QSF of the WSTA with the RspCMCR command to respond to the CMC\_REQ message. As a result, the QSF of the WSTA transfers a response message, CMC\_RESP, including the current codec mode to the CMC\_REQ message to the WSTA in the local site. Upon receiving the CMC\_RESP message, the WSTA checks the Received-RspCMCR (RxRspCMCR) and whether the codec mode contained in the CMC\_REQ has been adjusted appropriately at the remote WSTA or not. + +![Figure 12: QoS signalling function (QSF) diagram showing message flow between Remote and Home WSTAs.](83852ec55d4802521a727926336bedab_img.jpg) + +The diagram illustrates the QoS signalling function (QSF) between a Remote WSTA and a Home WSTA. The communication path includes a Wireless access network, an IP backbone network, and another Wireless access network. + +**Remote WSTA (Left):** Contains CSMMF-Packet evaluation module (PEM), SQCF-Codec mode control module (CMCM), and WSTA-1-QoS signalling function (QSF). + +**Home WSTA (Right):** Contains SQCF-Codec mode control module (CMCM), WSTA-2-QoS signalling function (QSF), and CSMMF-Packet evaluation module (PEM). + +**Message Sequence:** + +- (1) TxCMCR: From Home CMCM to Home QSF. +- (2) CMC\_REQ: From Home QSF through the network to Remote PEM. +- (3) RxCMCR: From Remote PEM to Remote CMCM. +- (4) RspCMCR: From Remote CMCM to Remote QSF. +- (5) CMC\_RESP: From Remote QSF through the network to Home PEM. +- (6) RxRspCMCR: From Home PEM to Home QSF. + +**Legend:** + +- CSMMF: Channel Status Measurement and Management Function +- SQCF: Service Quality Control Function +- QSF: QoS Signalling Function +- CMCM: Codec Mode Control Module +- RxCMCR: Received Codec Mode Change Request +- TxCMCR: Transmitting Codec Mode Change Request +- RspCMCR: Response to the Codec Mode Change Request +- RxRspCMCR: Received RspCMCR +- CMC\_REQ: Codec Mode Change Request +- CMC\_RESP: Codec Mode Change Response + +Figure 12: QoS signalling function (QSF) diagram showing message flow between Remote and Home WSTAs. + +**Figure 12 – QoS signalling function (QSF)** + +The procedure for QoS signalling message exchange is as follows and is illustrated in Figure 13. It is assumed that WSTA-1 and WSTA-2 are associated with AP-1 and AP-2, respectively, and connected to the IP backbone network through the wireless access network. + +- (1) If the WSTA-1 is ready to communicate with the WSTA-2, the WSTA-1 asks a call server to connect itself to the WSTA-2 that is located in the remote site by using a call signalling protocol such as ITU-T H.323, session initiation protocol (SIP). +- (2) If the call server allows the requested call connection, multimedia packets will be transferred using real-time transport protocol (RTP) or real-time streaming protocol (RTSP) between the WSTA-1 and the WSTA-2. + +![Sequence diagram showing the procedure for QoS signalling message exchange between WSTA-1, AP-1, Call server, AP-2, and WSTA-2. The diagram is divided into six numbered steps: (1) Call setup, (2) Session establishment, (3) Transmitted codec mode decision procedure, (4) QoS signalling, (5) Received codec mode decision procedure, and (6) Modified codec mode. Step (1) involves call setup requests and responses. Step (2) shows multimedia packets being exchanged. Step (3) is a decision procedure on WSTA-2. Step (4) shows codec mode change requests and responses. Step (5) is a decision procedure on WSTA-1. Step (6) shows multimedia packets with a modified codec mode.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +H.362(10)\_F13 + +Sequence diagram showing the procedure for QoS signalling message exchange between WSTA-1, AP-1, Call server, AP-2, and WSTA-2. The diagram is divided into six numbered steps: (1) Call setup, (2) Session establishment, (3) Transmitted codec mode decision procedure, (4) QoS signalling, (5) Received codec mode decision procedure, and (6) Modified codec mode. Step (1) involves call setup requests and responses. Step (2) shows multimedia packets being exchanged. Step (3) is a decision procedure on WSTA-2. Step (4) shows codec mode change requests and responses. Step (5) is a decision procedure on WSTA-1. Step (6) shows multimedia packets with a modified codec mode. + +**Figure 13 – Procedure for QoS signalling message exchange** + +![Sequence diagram showing detailed message exchange sequences for the transmitted codec mode decision procedure. The participants are Policy Control Function (PCF), Wireless Channel Measurement Module, Codec Mode Control Module, Packet Evaluation Module, Service Quality Measurement Module, and QoS Signalling Feature. The sequence starts with PCF sending 'Codec Mode Control Parameters' to the Codec Mode Control Module. The PCF also sends 'Codec Information' to the Service Quality Measurement Module. The Wireless Channel Measurement Module sends 'Channel Measurement Command' to the Codec Mode Control Module and 'Channel Quality' to the Packet Evaluation Module. The Codec Mode Control Module sends 'Packet Measurement Command' to the Packet Evaluation Module. The Packet Evaluation Module sends 'Packet Measurement Parameters' to the Service Quality Measurement Module. The Service Quality Measurement Module sends 'Service Quality' to the Codec Mode Control Module. Finally, the Codec Mode Control Module sends 'Transmitting Codec Mode Change Request' to the QoS Signalling Feature.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +Sequence diagram showing detailed message exchange sequences for the transmitted codec mode decision procedure. The participants are Policy Control Function (PCF), Wireless Channel Measurement Module, Codec Mode Control Module, Packet Evaluation Module, Service Quality Measurement Module, and QoS Signalling Feature. The sequence starts with PCF sending 'Codec Mode Control Parameters' to the Codec Mode Control Module. The PCF also sends 'Codec Information' to the Service Quality Measurement Module. The Wireless Channel Measurement Module sends 'Channel Measurement Command' to the Codec Mode Control Module and 'Channel Quality' to the Packet Evaluation Module. The Codec Mode Control Module sends 'Packet Measurement Command' to the Packet Evaluation Module. The Packet Evaluation Module sends 'Packet Measurement Parameters' to the Service Quality Measurement Module. The Service Quality Measurement Module sends 'Service Quality' to the Codec Mode Control Module. Finally, the Codec Mode Control Module sends 'Transmitting Codec Mode Change Request' to the QoS Signalling Feature. + +**Figure 14 – Detailed message exchange sequences for the transmitted codec mode decision procedure** + +- (3) After commencing the call, the WSTA-2 controls the codec mode of the remote WSTA-1 through the transmitted codec mode decision procedure which is described as follows (see also Figure 14). + +The CMCM instructs the WCMM and the PEM to collect information about the wireless channel quality and packet transfer performance, which is used to control multimedia service quality by sending the CMC and the PMC to the WCMM and the PEM, respectively. + +Upon receiving the CMC, the WCMM measures the wireless channel quality and reports the CQ to the CMCM. In the case of the PEM, upon receiving the PMC, the PEM evaluates the packet transfer performance and delivers the PMPs to the SQMM. The SQMM evaluates the SQ based on the PMPs and the CI from the PCF, and reports the SQ to the CMCM. Then, the CMCM controls the codec mode of the remote WSTA based on the SQ and the CMCPs from the PCF. + +If a WSTA determines to change the codec mode of a remote WSTA, the CMCM sends the TxCMCR to the QSF in order to instruct the QSF to request for the change of the current codec mode of the remote WSTA. + +- (4) After the WSTA-2 decides to change the codec mode of the remote WSTA, the WSTA-1, through the transmitted codec mode decision procedure, the WSTA-2 transmits the CMC\_REQ message to the remote WSTA-1. Upon receiving the CMC\_REQ message, the WSTA-1 decides whether to change the codec mode and transmits the response message to the CMC\_REQ, CMC\_RESP, reporting the current codec mode of the WSTA-1 to the remote WSTA-2. When the WSTA-2 receives the CMC\_RESP, the WSTA-2 checks whether the CMC\_REQ has been adjusted to the WSTA-1 or not. + +- (5) The WSTA-1, which receives the CMC\_REQ message, changes the codec mode through the following procedure. + +Upon receiving the CMC\_REQ message from the remote WSTA, the WSTA-2, the PEM extracts the codec mode control parameters contained in the CMC\_REQ message and delivers the parameters to the CMCM. The CMCM, which receives the codec mode control parameters from the PEM, transmits the MEPs to the COCM. The COCM changes the current codec mode according to the MEPs. The COCM, which receives the MEPs, applies the encoding parameters to the media encoder. + +- (6) After completing the codec mode change, the WSTA-1 and the WSTA-2 communicate with the RTP/RTSP stream which is encoded using an altered codec mode. + +#### 5.5.4 Policy control function (PCF) + +The PCF receives the call control policy information such as a user's service level agreement (SLA), supported codec mode, and codec information through the operations support system (OSS) interface, manages the policy information in the user profile database, and uses it for call admission, modification and rejection. This is described below (see also Figure 15). + +- (0) Through an operations support system (OSS), a call server receives the information on a terminal and a subscriber such as a service level agreement and a supported codec mode. +- (1) The PCF stores the information on the terminal and the subscriber which is received from the OSS into the user profile managed by the call control function. +- (2) A terminal, WSTA, initiates a call set-up request to the call server. For call set-up, an existing signalling protocol, e.g., SIP, ITU-T H.323, can be used. + +![Figure 15 – Policy control function (PCF) diagram. The diagram shows the interaction between a WSTA (Wireless Station) and a Call server. The WSTA contains modules for Call processing, CSMMF-Packet evaluation module (PEM), SQCF - Service quality measurement module (SQMM), SQCF - Codec mode control module (CMCM), and QoS signalling function (QSF). The Call server contains a Call processing unit, Policy control function (PCF), and User profile. The interaction steps are: (0) OSS provides SLA, supported codec mode, etc. to the PCF; (1) PCF accesses the User profile; (2) WSTA sends a Call request to the Call processing unit via the Wireless access network and IP backbone network; (3) Call processing unit accesses the User profile; (4) Call processing unit sends a Call quality control message (Codec mode control parameters, Codec information) to the PEM; (5) PEM sends CMCP to the CMCM and CI to the SQMM; (6) SQMM sends SQ to the CMCM; (7) CMCM sends TxCMCR to the QSF. Reference H.362(12)_F15 is noted.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Figure 15 – Policy control function (PCF) diagram. The diagram shows the interaction between a WSTA (Wireless Station) and a Call server. The WSTA contains modules for Call processing, CSMMF-Packet evaluation module (PEM), SQCF - Service quality measurement module (SQMM), SQCF - Codec mode control module (CMCM), and QoS signalling function (QSF). The Call server contains a Call processing unit, Policy control function (PCF), and User profile. The interaction steps are: (0) OSS provides SLA, supported codec mode, etc. to the PCF; (1) PCF accesses the User profile; (2) WSTA sends a Call request to the Call processing unit via the Wireless access network and IP backbone network; (3) Call processing unit accesses the User profile; (4) Call processing unit sends a Call quality control message (Codec mode control parameters, Codec information) to the PEM; (5) PEM sends CMCP to the CMCM and CI to the SQMM; (6) SQMM sends SQ to the CMCM; (7) CMCM sends TxCMCR to the QSF. Reference H.362(12)\_F15 is noted. + +| | | +|--------|----------------------------------------------------| +| CSMMF | Channel Status Measurement and Management Function | +| SQCF | Service Quality Control Function | +| QSF | QoS Signalling Function | +| PCF | Policy Control Function | +| CMCM | Codec Mode Control Module | +| PEM | Packet Evaluation Module | +| SQMM | Service Quality Measurement Module | +| CMCP | Codec Mode Control Parameters | +| CI | Codec Information | +| SQ | Service Quality | +| TxCMCR | Transmitting Codec Mode Change Request | +| OSS | Operations Support System | + +**Figure 15 – Policy control function (PCF)** + +- (3) Upon receiving the call request message, the call processing unit decides whether it allows the call request or not, according to the service level agreement and available codec mode which are acquired from the user profile database. +- (4) After accepting the call request, the call processing unit transmits the call quality control message, which includes codec mode control parameters and codec information, to the remote WSTA. The codec mode control parameters also include the service level and supported codec mode for the remote WSTA. +- (5) The PEM of the CSMMF, which receives the channel quality control message from the PCF, delivers the codec mode control parameters to the CMCM of the SQCF and transfers the CI to the SQMM of the SQCF. +- (6) The SQMM, which receives the CI, evaluates the SQ and reports the performance to the CMCM. +- (7) The CMCM, which receives the SQ, decides the codec mode of the remote WSTA according to the service control algorithm. If there is a need to change a codec mode, the CMCM instructs the QSF with TxCMCR to change the codec mode of the remote WSTA. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.430.1-201808-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.430.1-201808-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/H/T-REC-H.430.1-201808-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/H/T-REC-H.430.4-201911-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/H/T-REC-H.430.4-201911-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b99e2c4faed955938aad4f2338438e91924560a1 --- /dev/null +++ b/marked/H/T-REC-H.430.4-201911-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7682fbc7219e6328167b27301a147d32d7a8466f9c2564901172740f6f1d0aa +size 29021 diff --git a/marked/H/T-REC-H.430.4-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.430.4-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/H/T-REC-H.430.4-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/H/T-REC-H.430.4-201911-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.430.4-201911-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a142f9cad1bfe045c15b078d51fe289d93d4afd --- /dev/null +++ b/marked/H/T-REC-H.430.4-201911-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4edfd9a5bfbb6ca8d03bb3677bfcf110293021ef645b9b6a53c868bbeebb4911 +size 59329 diff --git a/marked/H/T-REC-H.430.4-201911-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/H/T-REC-H.430.4-201911-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de996a76959cd2f49057c8b580614665c7384573 --- /dev/null +++ b/marked/H/T-REC-H.430.4-201911-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15bc3468731b08ed4813968ee78e052eef8b54d9f2a799eca277e2ad59b0af6c +size 3022 diff --git a/marked/H/T-REC-H.430.4-201911-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/H/T-REC-H.430.4-201911-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2183c70634c4e0be559207ed3945c4326ccfa4c --- /dev/null +++ b/marked/H/T-REC-H.430.4-201911-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faca13696ddfb12727fdda325ec2889ab2b6b73d40aea5c360ffdf8191cd86f1 +size 4388 diff --git a/marked/H/T-REC-H.430.4-201911-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/H/T-REC-H.430.4-201911-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70ea4863ae644f029683d6bb1154fe7256fa17ce --- /dev/null +++ b/marked/H/T-REC-H.430.4-201911-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb4ba96e275fbf8f129d68f61e28a2750abf486ecc5577fee235341f3ebf6a4f +size 37695 diff --git a/marked/H/T-REC-H.430.6-202309-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.430.6-202309-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bdd7bc1d3581fbdc3cf6b035f618693dbe3846 --- /dev/null +++ b/marked/H/T-REC-H.430.6-202309-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75efa8e3513a799767c04a0bb7bcd87a550f2378f5880629068581808c1c9f7f +size 7353 diff --git a/marked/H/T-REC-H.430.6-202309-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/H/T-REC-H.430.6-202309-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d817a3f830361ba1915f1a95954dfa1bba02b523 --- /dev/null +++ b/marked/H/T-REC-H.430.6-202309-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:127a01ba3ead108d3000f79beeba196720fb63d79484439f5ab98b14c089d342 +size 38264 diff --git a/marked/H/T-REC-H.430.6-202309-I_PDF-E/raw.md b/marked/H/T-REC-H.430.6-202309-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dee306c36062b2472d61ca05ab2a882402ef32f6 --- /dev/null +++ b/marked/H/T-REC-H.430.6-202309-I_PDF-E/raw.md @@ -0,0 +1,359 @@ + + +# Recommendation**ITU-T H.430.6 (09/2023)** + +SERIES H: Audiovisual and multimedia systems + +Infrastructure of audiovisual services – Telepresence, immersive environments, virtual and extended reality + +--- + +**Media transport protocols, signalling information of haptic transmission for immersive live experience (ILE) systems** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +### **Audiovisual and multimedia systems** + +| | | +|---------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| General | H.200-H.219 | +| Transmission multiplexing and synchronization | H.220-H.229 | +| Systems aspects | H.230-H.239 | +| Communication procedures | H.240-H.259 | +| Coding of moving video | H.260-H.279 | +| Related systems aspects | H.280-H.299 | +| Systems and terminal equipment for audiovisual services | H.300-H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350-H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360-H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420-H.439 | +| Supplementary services for multimedia | H.450-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.430.6 + +# Media transport protocols, signalling information of haptic transmission for immersive live experience (ILE) systems + +## Summary + +Immersive live experience (ILE) systems may handle haptic information such as vibrotactile and kinaesthetic actions, for increasing more immersiveness in addition to audio and video. Haptic information should be transmitted synchronously with audio, video, and lighting information. Recommendation ITU-T H.430.6 identifies media transport protocol and signalling information of haptic transmission for immersive live experience (ILE) systems, in order to transmit haptic information synchronously to provide ILE services. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.430.6 | 2023-09-13 | 16 | 11.1002/1000/15629 | + +## Keywords + +Haptic, ILE, kinaesthetic actions, media transport protocol, signalling information, vibrotactile. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2023 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Requirements to haptic transmission for ILE systems ..... | 3 | +| 6.1 Haptic information..... | 3 | +| 6.2 Spatial information ..... | 4 | +| 7 Media transport protocols for haptic transmission ..... | 4 | +| 8 Signalling information for haptic transmission ..... | 4 | +| 8.1 Environment descriptor ..... | 5 | +| 8.2 Haptic information and location descriptor ..... | 5 | +| Bibliography..... | 7 | + + + +# Recommendation ITU-T H.430.6 + +## Media transport protocols, signalling information of haptic transmission for immersive live experience (ILE) systems + +## 1 Scope + +Immersive live experience (ILE) systems may handle haptic information such as vibrotactile and kinaesthetic actions, for increasing more immersiveness in addition to audio and video. Haptic information should be transmitted synchronously with audio, video, and lighting information, however [ITU-T H.430.4] does not clearly specify the signalling information about haptic transmission. + +This Recommendation identifies media transport protocol and signalling information for haptic transmission over immersive live experience (ILE) systems. + +The scope of this Recommendation includes: + +- Requirements of haptic transmission for ILE systems; +- Media transport protocol for haptic transmission; +- Signalling information for haptic transmission. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.264] Recommendation ITU-T H.264 (V14) (2021), *Advanced video coding for generic audiovisual services*. +- [ITU-T H.265] Recommendation ITU-T H.265 (V9) (2023), *High efficiency video coding*. +- [ITU-T H.266] Recommendation ITU-T H.266 (V3) (2023), *Versatile video coding*. +- [ITU-T H.430.4] Recommendation ITU-T H.430.4 (2019), *Service configuration, media transport protocols, signalling information of MPEG media transport for immersive live experience (ILE) systems*. +- [ISO/IEC 14496-12] ISO/IEC 14496-12:2022, *Information technology – Coding of audio-visual objects – Part 12: ISO base media file format*. +- [ISO/IEC 23005-2] ISO/IEC 23005-2:2018, *Information technology – Media context and control – Part 2: Control information*. +- [ISO/IEC 23005-3] ISO/IEC 23005-3:2019, *Information technology – Media context and control – Part 3: Sensory information*. +- [ISO/IEC 23008-1] ISO/IEC 23008-1:2023, *Information technology – High efficiency coding and media delivery in heterogeneous environments – Part 1: MPEG media transport (MMT)*. + +- [ISO/IEC 23009-1] ISO/IEC 23009-1:2022, *Information technology – Dynamic adaptive streaming over HTTP (DASH) – Part 1: Media presentation description and segment formats.* +- [ISO 9241-910] ISO 9241-910:2011, *Ergonomics of human-system interaction – Part 910: Framework for tactile and haptic interaction.* +- [ISO 9241-920] ISO 9241-920:2009, *Ergonomics of human-system interaction – Part 920: Guidance on tactile and haptic interactions.* + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 haptics** [ISO 9241-910]: Haptics consists of touch (tactile/cutaneous) and kinaesthesia (kinaesthetic), which are sensory and/or motor activity based in the skin, muscles, joints and tendons. +- 3.1.2 immersive live experience (ILE)** [b-ITU-T H.430.1]: A shared viewing experience which stimulates emotions within audiences at both the event site and remote sites, as if the ones at remote sites wandered into substantial event site and watched actual events in front of them, from high-realistic sensations brought by a combination of multimedia technologies such as sensorial information acquisition, media processing, media transport, media synchronization, and media presentation. +- 3.1.3 kinaesthetic** [ISO 9241-910]: Kinaesthetic appertains to kinaesthesia. +- 3.1.4 kinaesthesia** [ISO 9241-910]: Kinaesthesia is sense and motor activity based on muscles, joints and tendons. +- 3.1.5 tactile** [ISO 9241-910]: Tactile appertains to touch. +- 3.1.6 vibrotactile** [ISO 9241-910]: Vibrotactile is vibration-based stimulation of the skin. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------------| +| 3D | Three Dimensional | +| AAC | Advanced Audio Coding | +| DASH | Dynamic Adaptive Streaming over HTTP | +| ILE | Immersive Live Experience | +| MFU | Media Fragmentation Unit | +| MMT | MPEG Media Transport | +| MMTP | MMT Protocol | +| MPD | Media Presentation Description | +| MPEG | Moving Picture Experts Group | +| MPI | Media Presentation Information | +| PI | Presentation Information | + +| | | +|-----|-----------------------------| +| TS | Transport Stream | +| UTC | Coordinated Universal Time | +| XML | Extensible Mark-up Language | + +## 5 Conventions + +In this Recommendation: + +- The first line of XML is written for document reputation, the keywords "version" is a required attribute, and the keywords "encoding" indicate a coding scheme which tells the parsing engine what character set the current document is using. +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +## 6 Requirements to haptic transmission for ILE systems + +Haptic information, including vibrotactile, may increase immersiveness and reality in immersive live experience (ILE) services. At present there are several standards such as [ITU-T H.264], [ITU-T H.265], [ITU-T H.266] and Moving Picture Experts Group (MPEG)-2 advanced audio coding (AAC) for transmitting audio and video in ITU-T and ISO/IEC JTC1 (MPEG). However, no standards for haptic information transmission were yet considered. ILE services can provide high-realistic sensations at the viewing sites by simultaneous transmission of audio, video lighting and other information. In addition, simultaneous transmission of haptic information with other information increases more realistic sensation at the viewing sites. + +In order to transmit haptic information from the event site to the viewing sites, media transport protocols and signalling information of haptic transmission for ILE systems needs to be clarified. + +### 6.1 Haptic information + +Haptic information normally includes the following: + +- 1) Information on haptic sensors + - Type of sensor (tactile, vibrotactile, kinaesthetic) + - ID of the object the sensor is attached to + - Three dimensional (3D) position sensed, in general sensor position attached to the object + - 3D direction sensed, in general sensor direction attached to the object +- 2) Tactile sensor information + - Machinery information + - Temperature information +- 3) Vibrotactile sensor information + - Frequency information + - Intensity information +- 4) Kinaesthetic sensor information + - Force information + - Torque information + - Stiffness information + +The above information is the basis for describing haptics, and more information might be needed to be transmitted for reconstructing the haptic atmosphere at the viewing sites. + +Tactile sensor information, vibrotactile sensor information and kinaesthetic sensor information are defined in [ISO/IEC 23005-2], [ISO/IEC 23005-3], [ISO 9241-910], and [ISO 9241-920] which include the extensible mark-up language (XML) schema and syntax. In addition, HapticSampleEntry in the ISOBMFF standard [ISO/IEC 14496-12] and encoded haptics to the media presentation description (MPD) segments in an upcoming release of the MPEG-dynamic adaptive streaming over HTTP (DASH) streaming standard [ISO/IEC 23009-1] are under study in ISO/IEC JTC SC29. + +This Recommendation can refer to these existing specifications for representing haptic information. However, 3D position data for the source of haptic information are not defined in these specifications, so this Recommendation needs to define special information about haptic sensors. + +### 6.2 Spatial information + +Haptic information is gathered by sensors in event sites, and the sensors are allocated several points that have spatial information such as the 3D position. In order to reconstruct the atmosphere of the event site at the viewing sites, the spatial information of sensors at the event site needs to be transferred. The information can be transferred by using reference space, as defined in [ITU-T H.430.4]. The reference space is shown in Figure 1. + +![Figure 1: Example of reference space describing the location and size of equipment. The diagram shows a 3D perspective view of a room with a 'Background screen' and a 'Foreground screen'. A 'Sound' source is indicated by a purple hexagon. Two 'Speaker' units are shown on the floor. A coordinate system (x, y, z) is shown at the top left. To the right, a 2D view of the 'Background screen' is shown with dimensions: 4 m (4096 pixels) wide and 2.13 m (2180 pixels) high. The label H.430.6(23) is at the bottom right.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +The diagram illustrates a reference space for haptic equipment. On the left, a 3D perspective shows a room with a large blue 'Background screen' and a smaller 'Foreground screen' in front of it. A purple hexagon labeled 'Sound' is positioned between the screens. Two yellow 'Speaker' units are on the floor. A coordinate system with x, y, and z axes is shown. On the right, a 2D view of the 'Background screen' is shown with its dimensions: a width of 4 m (4096 pixels) and a height of 2.13 m (2180 pixels). The label H.430.6(23) is at the bottom right. + +Figure 1: Example of reference space describing the location and size of equipment. The diagram shows a 3D perspective view of a room with a 'Background screen' and a 'Foreground screen'. A 'Sound' source is indicated by a purple hexagon. Two 'Speaker' units are shown on the floor. A coordinate system (x, y, z) is shown at the top left. To the right, a 2D view of the 'Background screen' is shown with dimensions: 4 m (4096 pixels) wide and 2.13 m (2180 pixels) high. The label H.430.6(23) is at the bottom right. + +Figure 1 – Example of reference space describing the location and size of equipment + +## 7 Media transport protocols for haptic transmission + +Haptic information might be transmitted over several media transport protocols, such as multimedia data in the MPEG media transport (MMT) protocol (MMTP) and MPEG-2 transport stream (TS). Vibration information might be considered as the low frequency audio signals, thus this Recommendation aims to use existing media transport for audio such as MMT, MPEG-2 TS, and other multiplex formats for transmitting vibrotactile sensor information. + +ILE systems using haptic information are required to synchronize haptic signals with audio and video signals for increasing immersive sensation for users. As one of the media transport protocols, MMTP can carry multimedia data synchronously. [ISO/IEC 23008-1] specifies the encapsulation format, but there are some variations of the media fragmentation unit (MFU) format. Since haptic information can be transmitted very similarly with audio signals, the encapsulation method defined in [ITU-T H.430.4] is utilized. When MPEG-2 TS is used, haptic information can be encapsulated and transmitted by one of the audio channels. + +## 8 Signalling information for haptic transmission + +In order to handle assets including spatial information for reconstructing haptic information at viewing sites, the following constraints are applied to the signalling information for media descriptors. + +### 8.1 Environment descriptor + +To reconstruct haptic information at viewing sites of ILE services, a presentation information (PI) content in media presentation information (MPI) tables is required to carry the spatial environment information. To specify the syntax of the environment descriptor of several sensors, which gather information described in clause 6.1, the environment descriptor defined in [ITU-T H.430.4] can be utilized. + +Furthermore, other environmental information such as temperature, humidity, and pressure need to be gathered by tactile sensors in order to make the viewing sites as real as the event site. + +In general, the temperature and pressure can be gathered by the sensors in the atmosphere or water. Temperature can be perceived by a temperature sensor in the unit of Celsius or Fahrenheit. Humidity represents the proportion of water in the air, which can be perceived by the humidity sensor in the unit of percentage, and the value of it indicates the degree of dryness and wetness. Pressure refers to the weight of the atmospheric column per unit area, which can be perceived by the atmospheric pressure sensor in the unit of hectopascal (hPa), and the value of it is closely related with weather and the altitude. In addition, if the event site is in the water, such as a swimming competition or underwater show, the temperature refers to water temperature, and the pressure stands for liquid pressure, its unit is N/mm2 (Newton/millimetre square). The XML schema and syntax of the above environment descriptor are defined in [ISO/IEC 23005-3]. + +### 8.2 Haptic information and location descriptor + +In order to reconstruct haptic information at viewing sites of ILE services, information of haptic sensors mentioned in clause 6.1, especially sensor location data, needs to be transmitted from the event site. Haptic information and location information should be transferred from the event site to viewing sites so that haptic information from the object can be accompanied by the displayed objects at the viewing sites. A haptic information and location descriptor is transferred on media transport protocols. In most cases, objects move around in the event site, so location information of the objects should be captured in each frame. In other words, haptic and location information are necessary to reproduce the event at the viewing sites. + +As one of the media descriptors, the syntax of haptic information and location descriptor contains spatial information of sensors to reconstruct haptic phenomenon aligned with objects at the viewing sites. The information will be processed by media processing functions. + +Sensors attached to objects are moving around in the event site, thus it is required to reconstruct the actual trajectory of the moving objects. For this purpose, the ILE systems need to transport tracking information of objects, as described in clause 7 of [ITU-T H.430.4]. The tracking information can support to specify the location of the haptic sensors. + +The syntax of sensor\_location\_data and XML syntax sample are shown in Tables 1 and 2. + +**Table 1 – Syntax of sensor\_location\_data** + +| Name | Data | Form | Repetition | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------|--------|------------| +| sensor_location_data | Three-dimensional location information of each sensor | | 1 | +| timecode | Time at which location info is consumed, which is denoted by coordinated universal time (UTC) for time synchronization between objects | String | 1 | +| object | Name of the object that anchors the sensor | String | 0..* | +| sensor | Name of the sensor | String | 1 | + +**Table 1 – Syntax of sensor\_location\_data** + +| Name | Data | Form | Repetition | +|------------------|------------------------------------------------------------------------------------|---------|------------| +| label | The label of target sensor, which can be used for sensor and object identification | String | 0..* | +| global_locations | Location of the sensor in the world coordinates | | 0..1 | +| sensor_id | ID of sensor | String | 1 | +| point | Position of the sensor | | 1 | +| x | X-coordinate | Decimal | 1 | +| y | Y-coordinate | Decimal | 1 | +| z | Z-coordinate | Decimal | 1 | +| unit | Unit of the coordinates | String | 1 | +| direction | Direction of the sensor in spherical coordinates | | 1 | +| use | Senor has direction (Yes/No) | String | 1 | +| theta | Angle from X-coordinate in XY plane | Decimal | 1 | +| phi | Angle from Z-coordinate | Decimal | 1 | + +**Table 2 – XML syntax sample of sensor\_location\_data** + +``` + + + + DF9F7CB944EF4217 + + + + + Thouch003 + + 392 + 129 + 6405 + mm + + + Yes + 120 + 60 + + + + + + +``` + +## Bibliography + +- [b-ITU-T H.430.1] Recommendation ITU-T H.430.1 (2018), *Requirements for immersive live experience (ILE) services*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.430.7-202309-I_PDF-E/raw.md b/marked/H/T-REC-H.430.7-202309-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e3b6362f90257f6916702cca4031b90582b431f5 --- /dev/null +++ b/marked/H/T-REC-H.430.7-202309-I_PDF-E/raw.md @@ -0,0 +1,335 @@ + + +# Recommendation**ITU-T H.430.7 (09/2023)** + +SERIES H: Audiovisual and multimedia systems + +Infrastructure of audiovisual services – Telepresence, +immersive environments, virtual and extended reality + +--- + +## **Requirements of interactive immersive services** + +![ITU logo](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +### **Audiovisual and multimedia systems** + +| | | +|---------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| General | H.200-H.219 | +| Transmission multiplexing and synchronization | H.220-H.229 | +| Systems aspects | H.230-H.239 | +| Communication procedures | H.240-H.259 | +| Coding of moving video | H.260-H.279 | +| Related systems aspects | H.280-H.299 | +| Systems and terminal equipment for audiovisual services | H.300-H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350-H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360-H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420-H.439 | +| Supplementary services for multimedia | H.450-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.430.7 + +## Requirements of interactive immersive services + +## Summary + +Recommendation ITU-T H.430.7 provides the definition and requirements of interactive immersive services (IIS). Based on the overview of IIS, the requirements which include interactive capabilities, synchronous transmission of concurrent streams, intelligent distribution of massive multimedia data, media processing for immersive interactive information, and network status awareness with quality of experience (QoE) scheduling, are specified in this Recommendation. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.430.7 | 2023-09-13 | 16 | 11.1002/1000/15630 | + +## Keywords + +Conceptual framework, IIS, ILE, requirements. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2023 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview ..... | 2 | +| 7 High-level requirements of IIS ..... | 3 | +| 7.1 Support for interactive capabilities..... | 4 | +| 7.2 Support for synchronous transmission of concurrent streams..... | 5 | +| 7.3 Distribution of massive multimedia data..... | 5 | +| 7.4 Media processing for immersive interactive information ..... | 5 | +| 7.5 Network status awareness and QoE scheduling ..... | 6 | +| Bibliography..... | 7 | + + + +# Recommendation ITU-T H.430.7 + +## Requirements of interactive immersive services + +## 1 Scope + +This Recommendation provides the requirements of interactive immersive services (IIS) as part of an immersive live experience (ILE). + +The scope of this Recommendation includes: + +- Definition of IIS; +- High-level requirements of IIS. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.1036] Recommendation ITU-T G.1036 (2022), *Quality of experience influencing factors for augmented reality services*. +- [ITU-T H.430.1] Recommendation ITU-T H.430.1 (2018), *Requirements for immersive live experience (ILE) services*. +- [ITU-T H.430.3] Recommendation ITU-T H.430.3 (V2) (2023), *Service scenario of immersive live experience (ILE)*. +- [ITU-T P.1320] Recommendation ITU-T P.1320 (2022), *Quality of experience assessment of extended reality meetings*. + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 haptics** [b-ISO 9241-910]: Haptics consists of touch (tactile/cutaneous) and kinaesthesia (kinaesthetic), which are sensory and/or motor activity based in the skin, muscles, joints and tendons. + +**3.1.2 immersive live experience (ILE)** [ITU-T H.430.1]: A shared viewing experience that stimulates emotions within audiences at both the event sites and the remote sites, as if the audience at the remote sites had wandered into a substantial event venue and had actually watched the events taking place in front of them. This impression is due to high-realistic sensations provided by a combination of multimedia technologies such as sensorial information acquisition, media processing, media transport, media synchronization, and media presentation. + +**3.1.3 quality of experience (QoE)** [b-ITU-T P.915]: The degree of satisfaction of the user of an application or service. It results from the fulfilment of their expectations with respect to the utility or enjoyment of the application or service in the light of the user's personality and current state. + +**3.1.4 vibrotactile** [b-ISO 9241-910]: Vibration-based stimulation of the skin. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 interactive immersive information:** The information is delivered two ways among users and/or objects at the event site(s) and the remote site(s) during immersive interaction, which includes audio, video, text, haptics, etc. + +**3.2.2 interactive immersive services (IIS):** Services which involve in collection, processing and transmission of immersive interactive information to support real-time interactions among immersive service users and/or objects. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------| +| 3D | Three Dimensional | +| CODEC | Coder-Decoder | +| E2E | End-to-End | +| IIS | Interactive Immersive Services | +| ILE | Immersive Live Experience | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| XR | Extended Reality | + +## 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. + +# 6 Overview + +Immersive live experience (ILE) services provide immersive sensations to users by creating high-realistic environments which involve simulating visual, auditory, haptic, and other sensory information. The provision of interactive immersive services (IIS) may involve an interaction of extended reality (XR), three dimensional (3D) images including hologram, haptic communication, digital twin and other multimedia technologies. + +IIS requires the collection, processing and transmission of interactive immersive information (including video, audio, haptic, etc.) to support real-time interactions among users and/or objects. The IIS scenarios may be categorically divided into point-to-point use cases (e.g., telemedicine, prototype experiment, automobile maintenance, remote shopping assistance), and point-to-multipoint use cases (e.g., immersive conference, immersive education, multi-user collaborative design). + +![Figure 1: Conceptual framework of interactive immersive services. The diagram shows five layers of interaction connected by red double-headed arrows. From top to bottom: IIS applications (showing four application icons), IIS system (showing three system icons), Transport network (showing network and cloud icons), Devices (listing Cameras, Sensors, Controllers, HMDs, and Smart phones), and User (showing icons for User, Objects, and Scenes).](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +The diagram illustrates the conceptual framework of interactive immersive services (IIS) through five stacked layers, each enclosed in a rounded rectangle. The layers are connected by vertical red double-headed arrows, indicating bidirectional interaction between adjacent layers. + +- IIS applications:** The top layer contains four small images representing different applications: a person interacting with a hologram, a person in a laboratory setting, a complex 3D visualization, and a person using a head-mounted device. +- IIS system:** The second layer contains three icons: a left-pointing arrow, a central database cylinder, and a right-pointing arrow, representing the core system components. +- Transport network:** The third layer contains icons of a network of buildings and a cloud with nodes, representing the infrastructure for data transmission. +- Devices:** The fourth layer lists five types of input/output devices: Cameras, Sensors, Controllers, HMDs (Head Mounted Devices), and Smart phones, each accompanied by a small icon. +- User:** The bottom layer contains three icons: a group of people representing the user, a bicycle representing objects, and a landscape representing scenes. + +H.430.7(23) + +Figure 1: Conceptual framework of interactive immersive services. The diagram shows five layers of interaction connected by red double-headed arrows. From top to bottom: IIS applications (showing four application icons), IIS system (showing three system icons), Transport network (showing network and cloud icons), Devices (listing Cameras, Sensors, Controllers, HMDs, and Smart phones), and User (showing icons for User, Objects, and Scenes). + +**Figure 1 – Conceptual framework of interactive immersive services** + +The conceptual framework of IIS is illustrated in Figure 1. The devices (e.g., cameras, sensors, controllers, head mounted devices, smartphones, etc.) capture or represent the interactive immersive information from/to users, objects and scenes. The transport network is responsible for the transmission of media from devices to the IIS system and vice versa. The IIS system provides functional capabilities such as coder-decoder (CODEC), rendering, reconstruction, media synchronization, intelligent distribution, media processing, network status awareness and quality of experience (QoE) scheduling. The IIS applications invoke the capabilities of the IIS system to provide various applications such as holographic communication, haptic communication, intelligent interaction, etc. + +# 7 High-level requirements of IIS + +The general and high-level requirements of ILE have been addressed in [ITU-T H.430.1]. Regarding the IIS related scenarios in [ITU-T H.430.3], the requirements of IIS are presented as follows. + +The high-level requirements of IIS in addition to high-level requirements of ILE, include: + +- Support for interactive capabilities. +- Support for synchronous transmission of concurrent streams. +- Distribution of massive multimedia data. + +- Media processing for immersive interactive information. +- Network status awareness and QoE scheduling. + +## 7.1 Support for interactive capabilities + +### (1) Information input and output + +The interactive immersive information contains many forms of multimedia such as movement, expression, audio, video, text, haptic and operation. IIS are required to handle a wide variety of data types corresponding to the interactive immersive information, for example, volumetric visual data, audible data, textual data, and haptic data. + +There are several kinds of capture devices and equipment which include cameras, positioners, sensors, controllers, etc. These devices and equipment should support capturing immersive interactive information. These collected data might be processed for information output, and then the processed data would be output at the other end. + +**High-level requirement 1-1:** IIS requires the devices and equipment to support capturing interactive immersive information including audio, video, text, haptics, and other sensed data. + +**High-level requirement 1-2:** IIS are required to reproduce processed volumetric visual data, audible data, textual data, haptic data, and control signal. + +**High-level requirement 1-3:** When multi-user interacts with virtual objects, IIS are required to time align attribute information of physical users and virtual objects (e.g., status, position and colour) with interactive immersive information (e.g., volumetric visual media, textual, etc.). + +### (2) Haptic interaction + +Some interactive immersive services such as immersive remote surgery, use haptic information in addition to video and audio information. + +**High-level requirement 1-4:** IIS can optionally use haptic or vibrotactile information in addition to video and audio to increase immersiveness. + +**High-level requirement 1-5:** IIS using haptic or vibrotactile information are recommended to have the functionality of suppressing howling, which is similar to acoustic feedbacks. + +**High-level requirement 1-6:** IIS using haptic or vibrotactile information can optionally have the functionality of storing haptic or vibrotactile information. + +### (3) Transport network capability + +Bandwidth requirements for IIS depend on immersive scenarios such as true hologram transmission at normal human size. Extremely low end-to-end (E2E) latency is crucial for truly immersive scenarios to avoid motion sickness. For example, haptic applications impose stringent latency requirements. Moreover, deterministic delay and high reliability should be guaranteed for teleoperations like remote surgery. + +**High-level requirement 1-7:** The transport network of IIS is recommended to transmit true hologram transmission at normal human size. + +**High-level requirement 1-8:** The transport network of IIS is recommended to guarantee deterministic delay and high reliability for teleoperation. + +**High-level requirement 1-9:** The transport network of IIS is recommended to manage transmitting data accurately. + +## 7.2 Support for synchronous transmission of concurrent streams + +IIS involves multiple channels of interactive immersive information in various media. Each channel may map to a separate stream with stringent in-time requirements to ensure an internal consistency. Synchronous transmission of concurrent streams is required to guarantee the QoE of IIS. + +**High-level requirement 2-1:** IIS system is required to support multiple concurrent streams transmitted through multiple channels from multiple terminals or devices. These concurrent streams are required to be synchronized appropriately with limited arrival time differences. + +**High-level requirement 2-2:** When realizing haptic communication, an IIS system is recommended to transmit interactive haptic or vibrotactile information captured by several sensors synchronously with video and audio signals. + +**High-level requirement 2-3:** When realizing real-time multi-user collaboration, an IIS system is required to support synchronous data transmission (e.g., processed media, concurrent stream, control signal) for multiple users, which implements synchronous media representation for multiple users. + +## 7.3 Distribution of massive multimedia data + +In order to provide IIS, massive multimedia data needs processing (rendering and modelling) and transmitting through networks. Edge computing might be used for processing due to its lower E2E latency, especially for holographic representation. + +**High-level requirement 3-1:** IIS system is required to support the distributing policies based on data type and priority. + +## 7.4 Media processing for immersive interactive information + +Due to the different applications and service scenarios, it is required to support media processing (extract, render, reconstruct, etc.) for interactive immersive information in the IIS system. IIS system provides computation and storage resources. Edge computing might be beneficial for providing low latency services by accessing the proximity of the end-users. + +**High-level requirement 4-1:** IIS system is required to process several media interactively that are involved in the ILE requirements such as audio, video streams, lighting, and spatial information defined in [ITU-T H.430.1]. In addition, the support of haptics and control signals are required for the IIS system in order to represent a remote site. + +**High-level requirement 4-2:** IIS system can optionally support the central cloud and edge computing and provide the allocation and schedule of computing resources based on the service requirements. + +**High-level requirement 4-3:** IIS system is required to support real-time media processing so that users may not be aware of any delays in the immersive interactive experience. + +**High-level requirement 4-4:** IIS system is required to support multiple rendering functions to ensure immersive interaction such as multi-channel rendering, distribution rendering, viewport-based rendering, 3D scene or objects rendering, and holographic rendering, which are selected according to the interactive immersive information and service requirements. + +**High-level requirement 4-5:** IIS system is required to support interaction and control processing which combines the different kinds of collection information (e.g., motion information, spatial information) and media content (e.g., virtual object). + +**High-level requirement 4-6:** IIS system is required to support low delay media coding techniques for processed media data (e.g., rendered volumetric visual data) to achieve real-time interaction. + +**High-level requirement 4-7:** IIS can optionally support the CODEC of volumetric visual data, audible data, textual data, and haptic data. The CODEC may include lossless coding such as MPEG-4 audio lossless coding (ALS) for audio and haptic data. + +**High-level requirement 4-8:** Considering personal information protection, an IIS system is required to support the capability of media processing including biometric special handling (e.g., mosaicking), anonymization (e.g., user identity, location, etc.), and other processing (e.g., virtual backgrounds and video filters processing). + +## **7.5 Network status awareness and QoE scheduling** + +QoE of IIS refers to the degree of satisfaction of the user of an interactive immersive service. The degree of QoE can be referenced from the influenced factors defined in [ITU-T P.1320] and [ITU-T G.1036]. + +Network status awareness is the capability to collect quality of service (QoS) and network resource information. QoS scheduling is the capability to update policies based on the collected information. Networks and terminals/devices can make adjustments based on policies. + +**High-level requirement 5-1:** IIS system is required to support collecting QoS and network resource information, and then updating the degree of QoE accordingly. + +## Bibliography + +- [b-ITU-T P.915] Recommendation ITU-T P.915 (2016), *Subjective assessment methods for 3D video quality*. +- [b-ISO 9241-910] ISO 9241-910:2011, *Ergonomics of human-system interaction – Part 910: Framework for tactile and haptic interaction*. +<> + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b585cf96b89f4eef4fe7e51a89a4aa45ac6c3d0 --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4512da51e79d4d74e023b562e30b3ba3e744924f97743f56879dc83ed688e9a4 +size 33057 diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..413ad4555a2a1e1f2360b03769e76232a2df13fc --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbd0f8e4385f8c3cf9bfe472bf34333626a44a45b290d4adee4f1d70007646f7 +size 69730 diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0272b6e5689cabd08432ed53f62079237835ea35 --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8395c31b8e80bba1cf66f60a76d6336e02ad5e3a56d8e8f1aa6465e5a950bbab +size 35277 diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca589129422da776b9c42a8149c8aab0cbe92e46 --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ebd55a2b409552e22b52d05445926ea5846d5c9ebbac5ff6e33fa29cfa0c163 +size 4628 diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f063e5ad6870491ec72ca34fd7411649b28d5d05 --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72689ae37c6d31271abbe0ee4e55c28266de94be7aff0c48a6e6fda019d89ea4 +size 56827 diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1412a2ed8b5f265222fe4531ed37feb0ae8491f9 --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24e10d0852ed66f0300acc71b8d6747fb9129341b9b938580592b7820cc43fa7 +size 82643 diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fb6982966883ba348c5764265508e0f1133130a --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5b08e587834082787aa25ec246c6b64f61589a02854d99193063c92ce20ad76 +size 3645 diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..638cd661794c991717af664ba605da99933b26ce --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33826a75dd07ea30a6834be02e40fc50bc51834177f31d5dd8b3bcb4e0c5465a +size 97696 diff --git a/marked/H/T-REC-H.430.8-202406-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/H/T-REC-H.430.8-202406-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0db0ea34fb1d942606642705f1f983e634dd14e4 --- /dev/null +++ b/marked/H/T-REC-H.430.8-202406-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72b3c6d32575dbdeb55687976c5f115e0cd63c5ac60f95a76902b81bc2a4117e +size 41517 diff --git a/marked/H/T-REC-H.431.1-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.431.1-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4d8969f805414689ab79cfd08c333d454d482b3 --- /dev/null +++ b/marked/H/T-REC-H.431.1-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:636c3839edff955a5b6208530b05fa1c983ab153d90f00216517a7a99478b988 +size 7074 diff --git a/marked/H/T-REC-H.431.1-202401-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/H/T-REC-H.431.1-202401-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6961eeece3195bddbd6443fb04d70e9b35dd151 --- /dev/null +++ b/marked/H/T-REC-H.431.1-202401-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92ad7c3b28c85a16fec850aad216daf2f2740a5b049f054ac1c23a8d7ecf6d4c +size 179647 diff --git a/marked/H/T-REC-H.431.1-202401-I_PDF-E/raw.md b/marked/H/T-REC-H.431.1-202401-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c2d650509a9074865d73e2d73d6eaae0df050a66 --- /dev/null +++ b/marked/H/T-REC-H.431.1-202401-I_PDF-E/raw.md @@ -0,0 +1,799 @@ + + +# Recommendation**ITU-T H.431.1 (01/2024)** + +SERIES H: Audiovisual and multimedia systems + +Infrastructure of audiovisual services – Telepresence, +immersive environments, virtual and extended reality + +## --- **Functional architecture for cloud virtual reality systems** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +### **Audiovisual and multimedia systems** + +| | | +|---------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| General | H.200-H.219 | +| Transmission multiplexing and synchronization | H.220-H.229 | +| Systems aspects | H.230-H.239 | +| Communication procedures | H.240-H.259 | +| Coding of moving video | H.260-H.279 | +| Related systems aspects | H.280-H.299 | +| Systems and terminal equipment for audiovisual services | H.300-H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350-H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360-H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420-H.439 | +| Supplementary services for multimedia | H.450-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.431.1 + +## Functional architecture for cloud virtual reality systems + +## Summary + +Recommendation ITU-T H.431.1, together with its related Recommendation ITU-T F.746.14, specifies the functional architecture of cloud virtual reality systems. It describes the overall functional architecture including control layer, resource layer, network layer, terminal layer, operation, administration and management, and security. This Recommendation also describes the basic functions of each layer, such as unified scheduling/technology integration/content distribution of the control layer, cloud-based operation on the resource layer and high-quality transmission by the network layer. The cloud virtual reality (VR) content can be run concurrently based on the cloud and is distributed to the terminal for presentation. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.431.1 | 2024-01-13 | 16 | 11.1002/1000/15764 | + +## Keywords + +Cloud virtual reality, functional architecture, virtual reality. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|--------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 1 | +| 4 | Abbreviations and acronyms ..... | 1 | +| 5 | Conventions ..... | 2 | +| 6 | Overview..... | 2 | +| 7 | Functional architecture for cloud virtual reality systems ..... | 3 | +| 8 | Functions of the Content layer for cloud virtual reality systems..... | 5 | +| 8.1 | Common functions ..... | 5 | +| 8.2 | Cloud migration functions of VR content based on terminal operation..... | 5 | +| 8.3 | Functions of cloud-native VR applications ..... | 5 | +| 9 | Functions of the Control layer for cloud virtual reality systems ..... | 6 | +| 9.1 | Control coordination..... | 6 | +| 9.2 | Technology integration..... | 7 | +| 9.3 | Content distribution ..... | 12 | +| 10 | Functions of the Resource layer for cloud virtual reality systems..... | 13 | +| 10.1 | Resource configuration/expansion/migration..... | 13 | +| 10.2 | Building computing environments ..... | 13 | +| 10.3 | Data storage/backup/migration..... | 14 | +| 11 | Functions of the network layer for cloud virtual reality systems ..... | 14 | +| 11.1 | Network optimization ..... | 14 | +| 11.2 | QoS service..... | 17 | +| 11.3 | Slicing service ..... | 17 | +| 12 | Functions of the terminals layer for cloud virtual reality systems..... | 17 | +| 12.1 | Build in service..... | 17 | +| 12.2 | Services presentation ..... | 18 | +| 12.3 | Motion processing ..... | 18 | +| 12.4 | Manipulate collection and return..... | 19 | +| 13 | Functions of OA&M for cloud virtual reality systems..... | 19 | +| 13.1 | User management ..... | 19 | +| 13.2 | Content management ..... | 20 | +| 13.3 | Operation management..... | 20 | +| 13.4 | Cooperation management..... | 20 | +| 13.5 | Resource management..... | 21 | +| 13.6 | Technology integration management ..... | 21 | + +| | Page | +|-----------------------------------------------------------------|------| +| 13.7 Network capability binds management ..... | 22 | +| 13.8 Terminal management ..... | 22 | +| 14 Functions of security for cloud virtual reality systems..... | 22 | +| 14.1 Whole-process security ..... | 22 | +| 14.2 Content compliance ..... | 22 | +| 14.3 Service security ..... | 23 | +| 14.4 Data asset security ..... | 23 | +| 14.5 Cloud resource security ..... | 23 | +| 14.6 Network security ..... | 23 | +| 14.7 User experience security..... | 24 | +| Bibliography..... | 25 | + +# Recommendation ITU-T H.431.1 + +## Functional architecture for cloud virtual reality systems + +# 1 Scope + +This Recommendation specifies the functional architecture for cloud virtual reality systems, and includes an overview of the functional architecture for cloud virtual reality systems as well as a description of the respective functions. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T F.746.14] Recommendation ITU-T F.746.14 (2022), *Requirements and reference framework for cloud virtual reality systems*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following term defined elsewhere: + +**3.1.1 operations latency** [ITU-T F.746.14]: The time it takes for the entire process from the terminal issuing a control command to the application content responding to the operation request and completing output. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|---------------------------------| +| AAC | Advanced Audio Coding | +| AI | Artificial Intelligence | +| APP | Application | +| AVI | Audio Video Interleave | +| AVS3 | Audio Video Coding Standard 3 | +| CDN | Content Delivery Network | +| CMAF | Common Media Application Format | +| CPU | Central Processing Unit | +| DRB | Data Radio Bearer | +| FMP4 | Fragmented MP4 | + +| | | +|---------|----------------------------------------------| +| FOV | Field of View | +| gNB | The Next Generation Node B | +| GPU | Graphics Processing Unit | +| HTTPS | Hypertext Transfer Protocol Secure | +| IPsec | Internet Protocol Security | +| L2TP | Layer 2 Tunnelling Protocol | +| MP3 | Moving Picture Experts Group Audio Layer III | +| MPEG | Moving Pictures Experts Group | +| OA&M | Operation, Administration and Management | +| OMAF | Omnidirectional Media Application Format | +| OpenVPN | Open Virtual Private Network | +| PPTP | Point-to-point Tunnelling Protocol | +| QoS | Quality of Service | +| RTMP | Real Time Messaging Protocol | +| SFTP | Secure File Transfer Protocol | +| SLA | Service Level Agreement | +| SRT | Subrip Text | +| STL | Standard Template Library | +| TSP | Truncated Square Pyramid projection format | +| VR | Virtual Reality | +| WAV | Waveform Audio File | +| Webvtt | The Web video text tracks format | + +# 5 Conventions + +None. + +# 6 Overview + +With the concept of the metaverse rising, virtual reality (VR) as one of the basic technologies, has attracted more and more attention from the industry. VR technology is the basis for the construction of panoramic, three-dimensional and smooth interactive digital scenes in the metaverse. For the real-time multi-user remote online interactions and VR applications with large amounts of computation, the cloud mode or cloud operation and terminal collaboration is an optimal way to realize them. Therefore, cloud VR will undertake more and more important tasks for the VR ecosystem. + +Cloud VR, which is based on cloud architecture and utilizes cloud capabilities, can effectively shield terminal differences, reduce the difficulty of application development, lower some specific industry entry barriers and promote the industry business chain cooperation. + +[ITU-T F.746.14] provides a reference framework and basic requirements for cloud VR systems. Based on them, it is necessary to analyse more systematically the functional architecture of cloud VR systems. + +Cloud VR systems are the end-to-end service mode of VR based on cloud. Cloud VR systems are achieved based on unified resource and capacity control scheduling, operation, administration and management (OA&M) and security management, cloud resource computing power supply, low latency, high bandwidth and high security network transmission, and terminal's presentation. It is necessary to clarify the functional architecture of cloud VR systems, including the overall architecture of cloud VR systems and the functional components of cloud VR services. + +This Recommendation can lay the foundation of functional architecture for other related standards of cloud VR systems. + +# 7 Functional architecture for cloud virtual reality systems + +The functional architecture for cloud VR systems is illustrated by Figure 7-1. + +![Figure 7-1: Functional architecture for cloud VR systems. The diagram shows five horizontal layers: Content layer (green), Control layer (blue), Resource layer (yellow), Network layer (grey), and Terminal layer (cyan). Security (orange) and OA&M (brown) are vertical columns on the left and right respectively. The Content layer includes Common functions, Cloud migrated VR applications operated on terminals, and Cloud-native VR applications. The Control layer includes Control coordination (Channel connection, Resource scheduling, Service distribution) and Technology integration (Node dispatch, Rendering, Optimized processing, Encoding and packaging, Live streaming service, On-demand streaming service, Encoding and streaming) and Content distribution (Content aggregation, Application distribution, Content delivery network). The Resource layer includes Resource configuration/expansion/migration, Building computing environments, and Data storage/backup/migration. The Network layer includes Network optimization, QoS service, and Slicing service. The Terminal layer includes Built in services, Services presentation, Motion processing, and Manipulate collection and return. Security includes Whole-process security, Content compliance, Service security, Data asset security, Cloud resource pool security, Network security, and User experience security. OA&M includes User management, Content management, Operation management, Cooperation management, Resource management, Technology integration management, Network capability binds management, and Terminal management.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +H.431.1(24) + +Figure 7-1: Functional architecture for cloud VR systems. The diagram shows five horizontal layers: Content layer (green), Control layer (blue), Resource layer (yellow), Network layer (grey), and Terminal layer (cyan). Security (orange) and OA&M (brown) are vertical columns on the left and right respectively. The Content layer includes Common functions, Cloud migrated VR applications operated on terminals, and Cloud-native VR applications. The Control layer includes Control coordination (Channel connection, Resource scheduling, Service distribution) and Technology integration (Node dispatch, Rendering, Optimized processing, Encoding and packaging, Live streaming service, On-demand streaming service, Encoding and streaming) and Content distribution (Content aggregation, Application distribution, Content delivery network). The Resource layer includes Resource configuration/expansion/migration, Building computing environments, and Data storage/backup/migration. The Network layer includes Network optimization, QoS service, and Slicing service. The Terminal layer includes Built in services, Services presentation, Motion processing, and Manipulate collection and return. Security includes Whole-process security, Content compliance, Service security, Data asset security, Cloud resource pool security, Network security, and User experience security. OA&M includes User management, Content management, Operation management, Cooperation management, Resource management, Technology integration management, Network capability binds management, and Terminal management. + +**Figure 7-1 – Functional architecture for cloud VR systems** + +The main function of the content layer of cloud VR systems is to support the common functions and the cloud-based operation of VR applications. From the perspective of operation modes, cloud VR applications mainly include cloud migrated VR applications operated on terminals and cloud-native VR applications. + +- Cloud migrated VR applications operated on terminals are VR applications installed, loaded, operated, manipulated and displayed in the software and hardware environment of a VR terminal for the purpose of local operation of the VR terminal. To realize cloud-based operation, such VR applications need to carry out operation adaptation to cloud software and + +hardware resource pool, data encapsulation / remote distribution of operation results, and acquisition / response to terminal remote control. + +- Cloud-native VR applications run natively in the cloud, which can effectively connect with common cloud operating environments, and its installation, loading, operation and other related processes can effectively adapt to cloud resources and application data sharing mechanisms. It can effectively improve the utilization of cloud software and hardware resources, and has the advantage of content data resource sharing. Cloud-native VR applications also need to have access to remote control acquisition / response with the terminal side. + +The control layer provides the functions of control coordination, technology integration, content distribution, etc. + +- The control coordination schedules the resource layer including resources like cloud computing power resources according to the cloud VR operation requirements, completes the docks and distribution of various channels of cloud VR services, and connects the cloud VR terminal to realize remote manipulation mapping. +- The technology integration provides various cloud operation capabilities, including two scenarios named video-based scenarios and graphics service-based scenarios, corresponding to cloud VR weak interaction scenarios and strong interaction scenarios respectively. On the video-based scenarios, it involves services including real-time online live broadcast and offline on-demand through adaptive transcoding and encapsulation between different audio and video formats according to different applications' characteristics and terminal requests. Video-based scenarios generally belong to the category of weak interaction scenarios but can also be reflected in some strong interaction scenarios or strong and weak compatible scenarios. On the graphics service-based scenarios, it includes the nearest, efficient and reliable online operation for terminal users through the cloud-side coordinated service node dispatch as online graphics rendering, encoding and streaming, then the media processing results (such as graphics and sound) with audio and video mode transmitting to terminals. +- The content distribution function is a cross function of video-based scenarios and graphics service-based scenarios, which provides content transmission services bridging cloud side and terminal side based on different distribution channels, such as content aggregation, application distribution. At the same time, as one function of content distribution, the content delivery network is necessary for video-based scenarios. + +The resource layer provides computing power for cloud VR based on cloud resource pools. It builds computing environments such as virtual machines, containers or application virtualization to operate on cloud-based VR functions. At the same time, it provides the functions of resource configuration/expansion/migration and data storage/backup/migration which can adapt to changes in operating conditions. + +The network layer provides the communication capabilities for cloud VR, such as quality of service (QoS) service, slicing service, network optimization, etc. + +The terminal layer provides built-in services of cloud VR based on various terminal types such as VR mobile phone, VR all-in-one machine and VR split machine, such as cloud VR service clients/applications (APPs), plug-ins/SDKs, etc. It also provides service presentation on the terminals and collects manipulations of the terminals to return the control layer. + +The OA&M provides centralized operating, management and maintenance functions of cloud VR, such as the managements of content, user, technology integration, operation, resource, network capability docks and terminal. + +The security of cloud VR provides multi-dimensional security mechanisms, such as the securities of content, service, data, cloud resource pool, network and user experience. + +The above only gives a preliminary introduction to the module's functions of each layer of cloud VR. Detailed explanations are given in clause 8. + +# **8 Functions of the Content layer for cloud virtual reality systems** + +## **8.1 Common functions** + +It provides function docks for cloud VR contents, such as security assurance, authentication docks, billing integration, data synchronization and terminal control connection to effectively implement platform-based operation, maintenance and management. + +- Security assurance: It provides compliant copyrights as well as safe and reliable operation mechanisms for the contents. +- Authentication docks: It provides authentication mechanisms for the contents by docks. +- Billing integration: It integrates different payment methods and payment channels, which provide docks for VR contents through interfaces and other methods. +- Data synchronization: It synchronizes operation data through an open data interface to help improve service quality. +- Terminal control connection: It realizes the operation of VR contents according to operation instructions uploaded by the terminal side and parsed by the platform in order to provide real-time experience of cloud VR contents. + +## **8.2 Cloud migration functions of VR content based on terminal operation** + +VR content based on terminal operation have the characteristics of independent terminal operation and data processing. To realize the cloud operation of this type of contents, it is necessary to modify the cloud operation adaptation to support the interception/encapsulation of operation data such as graphics / sound and flexible loading of progress data. + +- Cloud operation adaptation: It changes terminal-based operation mode to cloud-based operation mode which is able to operate VR application based on qualified cloud environment. By removing the restrictions on terminal operation and concurrent operation of such VR applications, it can realize multi-channel concurrent operation and remote operation in the cloud. +- Support interception / encapsulation of running data (such as graphics/sounds): It converts VR applications based on localized result outputs into shielded display mode. It supports interception and encapsulation of operation graphics and sound results, which lays the foundation for subsequent distribution to the terminal side. +- Flexible loading of progress data: It supports cloud VR progress data acquisition and loading across cloud-based operation environments including physical real machines, virtual machines and containers. + +## **8.3 Functions of cloud-native VR applications** + +The cloud-native VR applications do not require cloud operation adaptation, and can provide relevant graphics/sound and other operational data interception/encapsulation and flexible loading of progress data based on cloud native. This type of cloud VR contents can also realize multi-dimensional sharing of computing resources in the cloud resource pool and data processing results, especially for graphics applications. + +- Graphical resource classification processing: The cloud VR applications based on the unified identifiers of the terminal service requests, such as coordinate information, environmental variables and user identity, divide graphics resources into general-purpose graphics resources for multiple people and exclusive graphics resources for personal uses. General-purpose + +graphics resources are resources used by multiple users or multiple scenarios. Exclusive graphics resources include interactive scenes, real-time changing light and shadow properties, etc. + +- General graphics resource processing: Centralized and unified processing by means of real-time or pre offline processing, which obtains the current display screen and surrounding associated graphics resources based on the user terminal request, marks and carries out relevant coordinate information and environmental variables identification for distribution and sharing to multiple user terminals. +- Exclusive graphics resource processing: Based on the mutually independent operating environment, it completes the relevant logic operation and graphics rendering processing for the corresponding user terminals in real time, packs the user identity label, processed graphics resources and the synchronized associated sound effect for distribution to personal user terminal. +- Graphics resource integration: The terminal side integrates the general graphics resources and exclusive graphics resources delivered by the cloud based on the unified service identifier, re-matches the general graphics resources and the exclusive graphics resources for resource scheduling by feeding back relevant operation instructions, thus forming a closed loop processing. + +# **9 Functions of the Control layer for cloud virtual reality systems** + +## **9.1 Control coordination** + +### **9.1.1 Channel connection** + +It implements the platform side docks of publicity and promotion channels and realizes the information synchronization of cloud VR service promotion. There are two ways of realization, such as link through the platform interface and independent completion of channels, so to support publicity and referral. + +- Link through the platform interface: As the promotion channels active docks, the cloud VR platform side provides relevant data synchronization interfaces, the promotion channels reserve relevant publicity and promotion spaces according to agreed specifications, and the cloud VR platform actively publishes the publicity resources to the corresponding channels. +- Independent completion of channels: As the promotion channels independent completion, the cloud VR system provides relevant publicity resources, and then cloud VR service promotion information is independently released by the channel party on its own channel. +- Publicity and referral: After the completion of channel docks, it uploads relevant publicity pictures and texts, association of suggested links and other information to realize the function of publicity and referral. + +### **9.1.2 Resource scheduling** + +It allocates corresponding running server resources in the service node content according to the terminal service request and content resource requirements. + +- Capability matching: According to the resource occupancy of each server and the requirements of cloud VR graphics applications, it matches more suitable servers and selects one of them as the running server. +- Task distribution: It distributes task instructions for running cloud VR graphics applications to the running server which performs subsequent cloud rendering operation. + +### 9.1.3 Service distribution + +Based on cloud edge collaborative deployment, it provides unified management of cloud VR graphics applications and each rendering service node's installation/uninstallation/update. + +- Unified management: It provides unified deployment strategies to realize graphics application deployment and debugging of each rendering node. +- Application deployment: It pushes the cloud VR application to each rendering node and completes the installation of the server to which it belongs. +- Application debugging: It tests and optimizes the entire service process including cloud import, operation, rendering and encoding streaming for the deployed VR application (e.g., graphics application). + +## 9.2 Technology integration + +### 9.2.1 Node dispatch + +#### 9.2.1.1 Service node call + +Under the unified coordination of platform management functions, each node needs to have management and allocation functions of related node resources, such as monitoring operating status of the computing environment, deployment content management. + +- Node resource management: It manages software and hardware resources in the rendering service node, including hardware resource management, software environment management, deployment content management, etc. +- Hardware resource management: It performs operations like statistics, classification, removal, addition and update for the hardware of each server in the node, such as central processing unit (CPU), graphics processing unit (GPU), memory, storage and other hardware resources. +- Software environment management: It performs statistics, version and security management as well as related security hardening, version update and reinstallation operations for the software resources of each server in the node, such as operating system, graphics environment, virtual machine/container, etc. +- Deployment content management: It makes statistics on the content list, version status and capability requirements, and provides operation functions such as version upgrade and content removal for the cloud VR graphics contents deployed on each server in the node. + +#### 9.2.1.2 Data backup and migration + +It is performed during the operation process to ensure the continuity of cloud VR graphics application services in the event of a failure, so that the service can be quickly migrated. + +- Data backup: During the running process of cloud VR graphics applications, related progress files have minute-level real-time storage and other server backup functions. +- Service migration: When the VR graphics application fails, it can quickly migrate the service to other servers and restart it. + +#### 9.2.1.3 Synchronization and coordination + +To reduce the service delay, the platform side adopts the collaboration mode with the central cloud unified scheduling and edge node service. Since it involves the coordination and synchronization of multiple edge nodes, it is necessary to adopt a timing control mechanism for the interaction process of multi-user/multi-edge nodes to ensure the synchronization of remote interaction between multiple VR terminals. + +- Unified interaction and coordination: To accurately schedule the multi-user remote interaction relationship in cloud VR applications, the central cloud formulates the strategy of combining interactive logic information and user-specific logic information. + - The logic with interactive attributes of multi terminals and multi edge nodes is the interactive logic, and the related individual logic of terminal users is regarded as the user-specific logic of the terminal. + - This strategy is distributed to the edge nodes. The interactive associated edge nodes divide the uploaded terminal user logical information into user-specific logic information and interactive logic information according to the above strategy. + - At the same time, relevant edge nodes synchronize associated interaction logic information to the central cloud for unified real-time synchronization. +- Real time synchronization processing: The central cloud periodically predicts the relevant delay in the next period through time series linear programming methods based on the network historical link delay data which the central cloud monitored in the process of sending down interactive logic information to the edge nodes. + - According to the delay length of the prediction results or the network historical link delay data, the central cloud groups the edge nodes and generates the corresponding synchronization time-series rules which are set to different edge nodes group. + - For edge nodes group with short delay, the interactive logic information will be sent later than other edge nodes groups. + - By analysing the interactive logic information, the central cloud identifies the users participating in the interaction and the user related edge nodes, and completes the interactive logic information distribution according to the synchronization timing rules, so that the interactive logic information approximately arrive at related multiple edge nodes synchronously, realizing the synchronization of multi-party interaction. + +### 9.2.2 Rendering + +Rendering process includes graphics application start-up, hardware resource allocation, graphics application running, output data interception, graphics data transmission. + +- Graphics application start-up: In response to the remote concurrent graphics application's service requests including graphics application display/graphics application pause and graphics application exit, then multiple parallel application running instructions are initiated. +- Hardware resource allocation: The GPU hardware resources in the cloud are divided by the GPU hardware driver layer's hardware resources calling interface, according to the requirements of various concurrent applications, so as to allocate independent hardware resources from the same graphics card entity to each application. Among them, according to the running instructions of multiple concurrent applications, the GPU virtual running container is set up and managed. Under the condition that the service request is graphic application display and graphic application pause, a GPU virtual running container of graphic application is constructed; In the case that the service request is that the graphics application exits, the GPU virtual running container allocated for the graphics application is released. +- Running a graphics application: Based on the allocated hardware resources, run multiple parallel applications and complete the rendering of their respective graphics. +- Output data interception: Obtain the hardware resource address used by each application through the path addressing mechanism, and based on the obtained address, the rendered output data is directly intercepted at the bottom of the hardware. +- Graphics data transmission: Streaming the rendered output data, it is transmitted to the remote users who initiated the concurrent graphic applications, so as to directly display the graphics corresponding to the graphic applications on the terminals used by the users. Before + +streaming, in order to achieve the optimal output structure, it is necessary to determine the maximum number of frames and code stream of graphic data transmission according to the user's network conditions before streaming, and package the rendered output data in real time. + +### 9.2.3 Optimized processing + +#### 9.2.3.1 Layered optimization + +It adapts to the focus's change of attention from cloud VR terminal users, and intelligently matches video quality according to the layered partition mode, which can effectively reduce the pressure of cloud deployment and improve network carrying capacity. + +- Focus acquisition: The terminal user sends the focus of the current cloud VR application' attention to the server of control layer on the cloud, so that the cloud server performs video layering and partition processing according to the obtained focus. +- Video layered partition: In order to reduce the transmission pressure of the media stream, the cloud processing server divides the VR video image into the core area associated with the current focus and the surrounding area adjacent to the core area, and performs layered processing of the VR video according to the obtained focus, including low-quality base layer video and high-quality enhancement layer video. The basic layer video range transmitted by cloud includes the core area video of the base layer and the surrounding area video of the base layer; the enhancement layer video range transmitted by cloud includes the core area video of the enhancement layer and the surrounding area video of the enhancement layer. +- Processing result presentation: The terminal obtains the enhancement layer video of the core area and the base layer video of the surrounding area delivered by the cloud server, then splices the enhancement layer video of the core area and the base layer video of the surrounding area in order to get the spliced result, and displays the spliced result on the terminal; at the same time, the edge node near the user terminal obtains the enhanced video of the surrounding area and stores it in the cache for subsequent terminals. +- Change prediction: When the position of the user terminal is offset according to the information collected by the sensor, the terminal predicts the focus' change based on artificial intelligence (AI) and uploads the predicted result of the focus' change to edge node, in order to get the enhancement layer video of the surrounding area from the edge node which correlates the prediction results of the focus' change. + - The edge node obtains the enhancement layer video of the surrounding area which is adjacent to the enhancement layer video of the core area associated with the current focus, and combines the enhancement layer video of the core area with the enhancement layer video of the surrounding area associated with the prediction result from the cloud according to the prediction change, then sends it to the terminal in time, so that the terminal side can get the enhancement layer video of the surrounding area associated with the prediction result from the edge node, combine the core area video of the enhancement layer and the surrounding area video associated with the focus transformation prediction result of the enhancement layer for display. + - Before displaying the combined result, the terminal calls the base layer video of the surrounding area associated with the focus change prediction result from the local cache for display. +- Loops processing: When it is determined that the position of the user terminal stops shifting according to the information collected by the terminal sensor, the new focus of the current user is repeatedly sent to the cloud server, so that the cloud server performs layered and partitioned processing on the video again to form an overall closed loop. + +##### 9.2.3.2 Block optimization + +First, the cloud server of the control layer obtains the target multimedia data to be sent to the terminal; then, the cloud server performs the target multimedia data rendering based on the terminal device information such as the terminal's field of view (FOV), screen refresh rate and screen resolution of the terminal equipment information or the terminal capability and the network status of the terminal status information to get the rendered multimedia data. Finally, the rendered multimedia data will be sent to the terminal. + +- Image blocking: The cloud server first obtains the multimedia data to be sent to the terminal, and divides each frame of the multimedia data into blocks according to the terminal device information, then obtains the data of each frame's multiple blocks. The cloud server selects several central blocks as the central display area according to the terminal's FOV and screen display area, and other blocks as the non-central display area, which is convenient for subsequent optimization processing. +- Tuning process: Based on the original multimedia image resolution and frame rate, the cloud adjusts and optimizes the resolution and frame rate of each frame of the target multimedia data according to the terminal device information, then generates the rendered multimedia data. Especially for the central display area, under the premise of using the network transmission capability, when the display resolution and frame rate of the terminal are higher than the original level, the corresponding quality improvement rendering processing is adopted. If it is lower than the original level, the corresponding quality reduction treatment shall be adopted. + +#### 9.2.4 Encoding and packaging + +##### 9.2.4.1 Encoding + +It supports various common cloud VR projection methods, adopts compliant audio and video encoding formats, to complete the encoding process. + +- Projection methods: It should use supported common projection formats to complete cloud VR panoramic projection, such as omnidirectional media application format (OMAF) ERP, truncated square pyramid projection format (TSP), CUBE, etc. +- Video encoding: It should use compliant video encoding formats to complete video encoding, such as ITU-T H.264 [b-ITU-T H.264], ITU-T H.265 [b-ITU-T H.265], audio video coding standard 3 (AVS3), etc. +- Audio coding: It should use compliant audio encoding formats to complete audio encoding, such as Moving Picture Experts Group Audio Layer III (MP3), advanced audio coding (AAC), waveform audio file (WAV), etc. + +##### 9.2.4.2 Packaging + +It supports the use of compliant packaging formats, packages cloud VR multimedia-related video/audio/subtitles and other information into a single file, and supports large file transfer protocols. + +- Large file transfer: It should support the large file transfer function and encapsulate the corresponding combined transfer protocol, such as real time messaging protocol (RTMP), secure file transfer protocol (SFTP), etc. +- Subtitles addition: It has the function of using compliant formats to complete subtitle addition, such as subrip text (SRT), the web video text tracks format (Webvtt), standard template library (STL), etc. +- Packaging function: It adopts a compliant packaging format to complete the packaging of multimedia files, such as MPEG-2 TS, fragmented MP4 (FMP4), common media application format (CMAF), etc. + +### **9.2.5 Live streaming service** + +#### **9.2.5.1 Material collection** + +In the process of audio and video data material collection, it is necessary to have 360-degree collection, real-time data interaction, etc. + +- 360-degree acquisition: It supports camera multi-camera shooting or VR dome stand-alone shooting methods, and the viewing angle has the ability to cover 360-degree panorama. +- Real-time data interaction: Cameras of cloud VR systems can collect the corresponding audio and video data in real time, combine the corresponding camera position and other information to transmit them to the splicing processing unit in real time. +- Panoramic stitching: The splicing processing unit, including the server where the data source is local or the nearby edge node server, completes the splicing function of live audio and video in accordance with OMAF, TSP, CUBE and other compliant panoramic projection methods. After the panoramic stitching is completed, the encoding and packaging functions are docked. + +#### **9.2.5.2 Live broadcast sharing** + +With 360-degree panoramic images, spatial sound effects, etc., it brings immersive cloud VR live viewing experience, such as real-time ball games, sports meetings, concerts, etc. + +- Live source access: It supports a variety of VR live source access, and provides functions such as video pushing, streaming and output playback. +- Function expansion: In order to adapt to different network conditions and terminal types, it supports functions such as real-time transcoding, multi-bitrate output and content distribution capabilities. In order to facilitate user review, it supports automatic generation of on-demand streaming files. +- Live monitoring: In order to ensure the legality of live streaming content, it should have the function of reviewing the content of the stream, and realize automatic alerts for illegal content such as pornography, gambling, politics, drugs, violence and terrorism. + +### **9.2.6 On-demand streaming service** + +Based on functions such as resource distribution, video transcoding, and screen display range switching, it provides users with cloud VR on-demand services including movies, TV dramas, variety shows, documentaries, sports events, concerts. + +- Resource distribution: Adopting content delivery network (CDN) technology, supporting on-demand resources in different video formats, and utilizing various transmission protocols, it has the function of distributing resources nearby for multiple users. +- Video transcoding: In order to meet the needs of different playback environments, support the transcoding function between cloud VR on-demand video resources with different encoding formats, resolutions and projection formats. +- Screen display range switching: In order to flexibly adapt to terminal processing and network transmission capabilities, it has the processing and transmission capabilities of panoramic and FOV screen range switching. + +### **9.2.7 Encoding and streaming** + +For strong interaction scenarios such as games, it is necessary to obtain the screen resources and audio resources output by the cloud VR content in real time, and then stream/distribute them with the corresponding transport protocol after synchronous encoding of audio and video. + +- Sound resource acquisition: Through corresponding hook mechanism interception, virtual sound cards and other technologies, it supports multi-channel access to real-time audio and + +sound effects resources output by cloud VR applications, ensuring an immersive sound experience. + +- Simultaneous audio and video encoding: For the acquired image and sound resources, the video encoding and audio encoding are completed synchronously in real time by adopting compliant encoding methods. +- Streaming and distribution: For the encoded audio and video resources, they are encapsulated as one or more multimedia streams according to the corresponding transmission protocol, and delivered to users based on network addressing. + +## **9.3 Content distribution** + +### **9.3.1 Content aggregation** + +It supports a variety of different types of cloud VR content and service modes, and completes content deployment with flexible injection methods. + +- Content type: It supports a variety of different cloud VR content such as videos, animations and games, and has the ability to build its cloud operation. +- Service mode: It supports RTMP and other live broadcast protocols, SFTP / hypertext transfer protocol secure (HTTPS) and other offline protocols, and can provide live broadcast, on-demand and other service modes. +- Injection mode: It has a flexible content injection method, such as real-time content injection and offline content injection. +- Content deployment: With one-stop cloud edge deployment capability, it can achieve rapid injection of cloud VR content. + +### **9.3.2 Application distribution** + +In order to achieve cloud VR content and services to quickly reach users, it is necessary to have a variety of distribution mechanisms, distribution channels and service association methods. + +- Distribution mechanisms: As a cloud VR service and content to reach the user's method, it needs to support centralized distribution and distributed distribution. The central distribution is a distribution mode where the control layer is managed uniformly and serves as the content distribution source; the distributed distribution is a distribution model with decentralized multiple sources, and the control layer only provides authentication and supervision. +- Distribution channels: Equipped with various methods such as graphic and text links, download addresses, and page displays, it can be distributed to users through various channels such as websites, social tools, aggregation platforms, and embedded pages. +- Service association methods: It has the function of supporting the interconnection of cloud VR content and cloud VR systems services during the distribution process. + +### **9.3.3 Content delivery network** + +For cloud VR content, CDN adopts cloud-edge collaboration, with central nodes providing functions such as distribution, scheduling and transmission. Edge nodes provide services and accelerate content transmission nearby, functions such as distributed deployment, load balancing, flexible transmission and error correction capability. + +- Distributed deployment: For cloud VR content, it provides distributed networking services, content storage and streaming media services. +- Load balancing: For cloud VR content, it provides load balancing services of streaming media services. +- Flexible transmission: For cloud VR content, it provides functions such as transparent transmission, full-view transmission and FOV transmission. + +- Error correction capability: For cloud VR content, it provides error correction functions such as data integrity and audio/video synchronization. + +# **10 Functions of the Resource layer for cloud virtual reality systems** + +## **10.1 Resource configuration/expansion/migration** + +### **10.1.1 Resource configuration** + +In response to the operation requirements of cloud VR system services or applications, under the unified control of the control layer, the mapping of hardware resources and the call of software resources are realized, laying the foundation for the subsequent construction of the operating environment. + +- Hardware resource mapping: According to the computing power requirements of related cloud VR system services or applications, it needs to call and configure hardware resources such as CPU, GPU and storage space. +- Software resource call: On the basis of the computing power to complete the hardware resource mapping, the corresponding process, virtual machine, container, physical machine are realized to lay the foundation for the subsequent operating environment. + +### **10.1.2 Resource expansion** + +When the configured operating environment is insufficient, more resources need to be allocated to expand related computing power and provide functions such as real-time expansion and on-demand configuration. + +- Real-time expansion: It can respond to resource expansion requirements in real time, timely implement the configuration of related software and hardware resources, and achieve the timely supply of resources without affecting cloud VR functions or application quality. +- On-demand configuration: It can provide relevant expansion resources according to the computing power requirements such as computing, rendering and storage, as well as various software operating environment requirements. + +### **10.1.3 Service migration** + +When a cloud VR service or application runtime environment is abnormal, it is needed to reconfigure new resources to complete the corresponding migration. + +- Resource switchover: When service migration is required, the resources of the original hardware and software running environment need to be released, and the reconfigured resources must be enabled at the same time to switch between the old and new resources. +- Progress synchronization: When switching resources in the running environment, it is necessary to complete the synchronization of the corresponding progress files of the corresponding cloud VR services or applications between the old and new resources in a timely manner to ensure seamless switchover. + +## **10.2 Building computing environments** + +For different service functions and applications of cloud VR systems, it provides multiple operating environments such as virtual machine hosting, container hosting and physical machine hosting. + +- Virtual machine hosting: Based on the virtual machines related to the cloud resource pool, it realizes the concurrent hosting of cloud VR system function modules and applications, and has virtual machine start/migration/shutdown, service and content import/run/pause/exit under the unified control of the control layer, and provides the progress files' storage function. + +- Container hosting: Based on the containers related to the cloud resource pool, it realizes the concurrent hosting of cloud VR system functional modules and applications, and has container start/migration/shutdown, service and content import/run/pause/exit under the unified control of the control layer, and provides the progress files' storage function. +- Physical machine hosting: Cloud VR applications or services with complex computing and graphics rendering need to run in the exclusive mode of physical machines, realize functions such as service and content import/run/pause/exit under the unified control of the control layer, and provide the progress files' storage function. + +## 10.3 Data storage/backup/migration + +- Operation progress storage: According to the set cycle, the running progress files related to cloud VR functions or content are stored for migration in case of failure; when the cloud VR service or application exits, the final progress files are stored so that it can be synchronized when it is rerun. +- Log storage: During the operation of cloud VR, the operation logs related to cloud VR functions or content are needed to store so that it can be tracked relevant alarms and faults. +- Operational data storage: During the operation of cloud VR, data such as the running status of related services or content, and user behaviour without privacy need to be stored in an encrypted manner. +- Data backup: In order to ensure the effectiveness of data storage, it is necessary to provide a domain-specific data backup mechanism to avoid the situation that the data cannot be recovered when the domain fails. +- Data migration: When the service is migrated or rerun, the relevant progress data needs to be synchronized and migrated; when the resource pool related to the resource layer is maintained or shut down, the corresponding data needs to be migrated to the new resource pool. + +# 11 Functions of the network layer for cloud virtual reality systems + +## 11.1 Network optimization + +### 11.1.1 Network acceleration + +To provide end-to-end network acceleration services for users based on network capabilities, it is necessary to complete authority authentication based on the user's application to be accelerated. If the authentication is passed, it performs the manipulation step of providing the acceleration service for the application to be accelerated. In the network acceleration service's process, first, the user side's network equipment monitors the user's application traffic; then, identifies the traffic of the pre-configured application to be accelerated from the monitored application traffic; and then, self-adaption selects acceleration link; finally, the acceleration service is provided for the application to be accelerated based on the acceleration link. + +In the authentication process, the network device on the user side needs to send a service authority authentication request to the management server with the information of the user and the application to be accelerated, so that the management server can confirm whether the user has the authority to enjoy the service of accelerating the related application to be accelerated. And then the network device on the user side receives the service permission authentication response returned by the management server. + +According to the service permission authentication response, the service permission authentication result of the user to accelerate the application is determined. Preconfigure the description information of the application to be accelerated in advance, includes the application name, server address or application type. + +- Network monitoring: The user side's network equipment real-time monitors the user's application traffic, and determines whether the network is congested according to the real-time traffic monitoring result; when the congestion occurs, and then judges whether the traffic on the user side has an abnormal traffic that greater than the preset value. When it is determined that there has no abnormal traffic, the user is prompted that the network is abnormal, or the user is prompted to disconnect the current network connection and reconnect the network. When it is determined that there is an abnormal traffic, speed limiting or closing the abnormal traffic is performed, in order to optimize user network outlet bandwidth. And after limiting the speed or closing the abnormal traffic, the step of providing acceleration service for the application to be accelerated is executed. +- Identify the application to be accelerated: The description information of the application to be accelerated is matched with the description information of the monitored application traffic, so as to identify the pre-configured traffic of the application to be accelerated from the monitored application traffic. +- Select acceleration link: Testing the network service quality of the acceleration link between the user side network equipment and each acceleration proxy server, in order to select acceleration link. +- Provide network acceleration service: The acceleration link with the best network service quality is used as the acceleration link of the application to be accelerated. +- Acceleration execution: Provide acceleration service for that application to be accelerated based on the selected acceleration link, and establishing a link between the user-side network access device and the corresponding acceleration proxy server through point-to-point tunnelling protocol (PPTP), Layer 2 tunnelling protocol (L2TP), Internet protocol security (IPsec) or open virtual private network (OpenVPN). + +### 11.1.2 Network link optimization + +#### 11.1.2.1 Flexible link optimization selection + +For different service types of cloud VR systems, it provides the optimization functions of network links such as shortest path optimization, optimal bandwidth path optimization, and comprehensive optimal path optimization. + +- Shortest path optimization: In the scenarios where extremely low latency is required for latency-sensitive content and remote control instruction upload in cloud VR systems, the shortest path transmission is selected among multiple network links to achieve the lowest transmission delay. +- Optimal bandwidth path optimization: For service scenarios with high bandwidth in cloud VR systems, the link with the most sufficient bandwidth is selected from the multiple network links to meet the requirements of high-channel transmission. +- Comprehensive optimal path optimization: For scenarios with both latency and bandwidth requirements in cloud VR systems, it is necessary to comprehensively integrate the transmission requirements at the service level and the transmission capabilities of the current links of the network, comprehensively consider the indicators such as delay, bandwidth and reliability, to select the comprehensive and optimal link. + +#### 11.1.2.2 Intelligent selection path + +- Determine the shortest path topology: In order to meet the transmission requirements of cloud VR, based on multiple path selection criteria such as latency, reliability and jitter corresponding to the network data flow to be transmitted, the shortest path algorithm is used to search for the shortest path in parallel for each path selection criteria, and multiple shortest network paths corresponding to each path selection criteria are obtained and determined. + +Based on multiple shortest network paths corresponding to each path selection criteria, the shortest path topology corresponding to network data flow are determined. + +- Determine the network transmission path: The breadth-first search algorithm is used to conduct multi-criteria routing search based on the shortest path topology to obtain and determine the target network path. In the process of multi-criteria route selection search based on Breadth-first search algorithm, the network transmission constraints, such as the transmission performance requirements of network data flow, are obtained and used along with the constraints of to each path selection criteria to obtain the target network path. +- Network path transmission: Allocate transmission bandwidth to the target network path of each network data flow according to the network transmission constraints, realize based on the transmission bandwidth allocated for the target network path, the network data flow is transmitted through the target network path. + +### 11.1.3 Multi stream parallel transmission + +#### 11.1.3.1 Multi stream transmission + +For cloud VR systems service scenarios with ultra-large bandwidth requirements, in order to avoid congestion and heavy burden caused by single link transmission, multi-stream parallel transmission is required. At the same time, in order to avoid the user experience problem caused by the loss of key frames of multimedia streams, redundant transmission of key frames is also required. Moreover, in order to provide the utilization rate of network transmission data, it is necessary to have the function of multi-person universal data sharing and multi-stream sharing while multi-stream parallel transmission. + +- Multi-stream parallel transmission: After the control layer of the cloud VR system completes the corresponding multi-stream encoding processing, the network layer needs to allocate the corresponding multiple network links to provide the network parallel transmission function in real time. +- Redundant transmission of key frames: For key frames that play an important role, the network layer provides a corresponding redundant transmission mechanism to realize the transmission of a streamlined data flow with key frames over another link. +- Multi-stream sharing: For multimedia streams with multiple people reused, the network layer provides a multi-stream multi-person addressing mechanism to realize multi-stream sharing transmission. + +#### 11.1.3.2 Optimization of multi-stream hierarchical transmission + +In order to provide an optimized multi-stream transmission mechanism for cloud VR, it is necessary to determine the important service flow and ordinary service flow from the cloud-network service flows which require allocating cloud-network resources. The important service flow, e.g., the flow corresponding to area that the user is currently focusing on; the ordinary service flow refers to other service flows except important service flow. The priority of important service flow is higher than that of the ordinary service flow. + +- Priority resource allocation: From the cloud-network resources, identify priority candidate paths that match the priority requirements of important service flow, such as bandwidth, latency and reliability. The priority target transmission path is also confirmed from the priority candidate paths, and its resource allocation information is determined, as the priority resource allocation information for important service flow. +- Determine the amount of resource redundancy: Determine the excess probability of priority service flow based on the historical network resource usage of important service flow. The excess probability is used to characterize the probability that the actual resource consumption of an important service flow exceeds the priority resource allocation. At the same time, + +according to the excess probability, determine the amount of resource redundancy for important service flow. + +- Obtain remaining resources: According to the priority resources allocate information and resource redundancy of important service flows, and obtain the predicted resource occupation of important service flow. In addition, remove the predicted resource occupation from the cloud-network resources to obtain and determine the remaining resources. +- Allocate other resources: Based on the remaining resources of the cloud-network resources, determine the relevant candidate paths that match the ordinary service requirements of the ordinary service flow. Determine the relevant target path from the candidate paths related to the ordinary service flow, and determine its corresponding the resource allocation information as the resources allocation information for the ordinary service flow. +- Complete multi-stream transmission: allocate relevant cloud-network resources for the important service flow and the ordinary service flow based on the priority resource allocation information of the important service flow and the resource allocation information of the ordinary service flow, and complete related multi-stream transfers. + +## 11.2 QoS service + +- QoS level classification: Based on the different application requirements of cloud VR, and the connection with the access network and bearer network capabilities, complete QoS level identification and labelling, as well as corresponding level classification, etc. +- QoS level guarantee: According to the corresponding QoS level, the corresponding QoS guarantee network transmission service is provided for cloud VR services. + +## 11.3 Slicing service + +Based on the requirements of the control layer, the network layer provides relevant service capabilities to realize network slicing services for the functions of the cloud VR systems, including functions such as slicing full-process service and slicing resource isolation guarantee. + +- Network planning and evaluation: Through the analysis of service level agreement (SLA) requirements and network resources of cloud VR slicing services, the mapping from SLA requirements to resources and features is established, and SLA service capabilities are evaluated. In the evaluation stage, for cellular access networks, it is necessary to comprehensively consider wireless conditions such as signal-to-noise ratio, channel characteristics and other factors, as well as factors such as the geographical distribution of cloud VR terminals and traffic models. +- Differentiated scheduling: The network layer provides differentiated service SLA guarantee capabilities for different cloud VR systems services' requirements. +- Closed-loops guarantee: By evaluating and monitoring the relevant indicators of the cloud VR systems, the network layer can quickly adjust RAN resource scheduling or self-heal faults that affect SLA. +- Slicing resource isolation guarantee: According to the different service requirements of cloud VR systems, the network layer can flexibly provide data radio bearer (DRB) logical resource sharding, air interface spectrum resource sharding, and gNB-level resource sharding. + +# 12 Functions of the terminals layer for cloud virtual reality systems + +## 12.1 Build in service + +Through different built-in methods such as AAP, SDK and H5 pages, the terminal built-in cloud VR services are completed, mainly including built-in identity authentication, built-in service remote call/run/pause/shutdown, and built-in operation and maintenance service. + +- Built-in identity authentication: Through the docks of OA&M related user management and terminal management functions, built-in secure user identity, terminal information and other authentication capabilities to complete user registration/login/service permission authentication, terminal identification/content matching, etc. +- Service remote call/run/pause/shutdown built-in: After completing the relevant authentication, the docks control layer realizes the nearest service node allocated based on the terminal remote access resource layer, and completes the call/run/pause/shutdown operations of each functional module of the relevant cloud VR. +- Built-in OA&M service: Through the docks of OA&M-related OA&M management functions, online problem feedback, question answering, rights protection appeals, personal account management and other operations can be completed based on terminals. + +## 12.2 Services presentation + +After receiving the cloud VR multimedia stream delivered by the cloud, the terminal completes the output of the cloud VR system service through local audio and video decoding, audio and video synchronization, quality enhancement and stereoscopic output. + +- Audio and video decoding: the terminal side supports at least one of the hardware decoding or software decoding methods, and uses ITU-T H.264, ITU-T H.265, audio video interleave (AVI), etc. formats to complete the audio and video decoding processing of multimedia streams. +- Audio and video synchronization: For the decoded video stream and audio stream, the sound and image are synchronized according to the corresponding method of the relevant frame. +- Quality enhancement: In order to achieve the best effect of local display, it is recommended to improve the clarity of cloud VR system services by increasing the number of frames. +- Stereoscopic output: The terminal completes the fusion stereoscopic output of image and sound by splitting the screen left and right. + +## 12.3 Motion processing + +In the process of using cloud VR, when movements such as turning the head and moving are generated, it is necessary to adjust and optimize the picture accordingly. According to the motion sensing data collected by the cloud VR terminal in the early stage of motion, the motion of the related cloud VR terminal is predicted and processed, and the predicted motion data is obtained. Through real-time interaction with the cloud server, the display device of the corresponding cloud VR terminal is controlled to display the target cloud VR display screen determined based on the above predicted motion data. + +- Obtain picture offset: According to the predicted motion data, convert it from the coordinate system corresponding to the cloud VR terminal to the image coordinate system corresponding to the original cloud VR image, and determine/obtain the picture offset data. The picture offset data is used to characterize the offset of the VR picture caused by the motion predicted by the cloud VR terminal. +- Picture offset data processing: It is necessary to determine the conscious attribute of the movement, and carry out subsequent corresponding processing according to this attribute. If the offset of the cloud VR picture is determined to be less than the offset threshold that requires picture adjustment according to the picture offset data, it is determined that the motion of the VR terminal is caused by the user's unconscious movement, and there is no need for screen adjustment processing. If it is determined that the motion of the cloud VR terminal is not caused by the user's unconscious movement according to the picture offset data, it is determined whether the offset of the cloud VR picture is greater than the threshold that needs to be processed by the cloud server according to the picture offset data. If it is + +determined that the offset of the cloud VR picture is greater than the threshold required by the cloud server according to the picture offset data, perform the steps of sending the picture offset data to the cloud server. If it is determined that the offset of the cloud VR picture is less than or equal to the threshold at which the cloud server needs to adjust the screenshot according to the picture offset data, and no need to send the picture offset data to the cloud server. + +- Screen offset processing: Under the premise of meeting the needs of the cloud server to adjust the screenshot picture, the cloud VR terminal sends the picture offset data to the cloud server, in order to instruct the cloud server that adjusts the current screen capture range according to the picture offset data, and intercepts the original cloud VR image based on the adjusted screen capture range, so obtains and returns the adjusted cloud VR image, for the cloud VR terminal to display the corresponding target cloud VR picture on its display device according to the cloud VR image adjusted by the screenshot. + +## 12.4 Manipulate collection and return + +The manipulation process of cloud VR system services is initiated by the terminal, the remote manipulate functions are completed by collecting manipulate information, converting manipulate commands, and uploading manipulate commands in terminal side. + +- Collecting manipulate information: The terminal integrates local sensor value changes and various control commands such as handle, touch screen, gesture, voice control, etc., to complete the collection of moving distance, movement direction/angle, height change and control key value and other information. +- Converting manipulate commands: According to the content and control correspondence set by the cloud VR control layer, the locally collected control information is transformed, including key-value correspondence, position movement and screen display area correspondence. +- Uploading manipulate commands: The terminal obtains the control information collection, control command conversion results, and uploads them to the service node corresponding to the cloud VR systems service in real time to complete the remote control process. + +# 13 Functions of OA&M for cloud virtual reality systems + +## 13.1 User management + +The user side provides an account system for cloud VR services; the terminal side provides verification mechanisms, etc. + +- User-oriented account mechanism: It provides functions including user account registration, service login authentication and service payment management for cloud VR services. +- Terminal access: It collects and analyses the hardware computing capability, VR local operating environment capability, screen display capability and local control capability of the access terminal and updates the terminal resource database at the platform side. By completing the terminal access management, a terminal resource library can be established, which lays the foundation of the subsequent realization of matching cloud VR application contents and cloud VR terminal capabilities. The function of chip computing provides capabilities like logical computing processing, graphics processing and local storage, etc. The function of VR local operating environment provides built-in VR operating framework, or middleware in the terminal with various models and versions. The function of screen display provides VR content display capabilities at the terminal side including resolution, refresh rate and field of view of display screen. The function of local control provides built-in or external capabilities like sensors, gravimeters and so on to compute data of user's action/movements for spatial positioning. + +- Built-in service management: It completes built-in, version detection and optimization update of the cloud VR service by analysing and managing built-in cloud VR services of the terminal. The function of built-in cloud VR service completes localized installation of relevant cloud VR services for terminals that have not completed the cloud VR service built-in; The function of version detection detects and records the relevant version of cloud services built in the terminal; The function of optimization update completes the update of the latest version by automatically delivering the optimized version, when the version of the built-in cloud VR service in the terminal is low. +- Control methods docks: It completes the control and association of terminal-related sensors, peripheral equipment and positioning equipment. It records, synchronizes and associates information related to terminal control through the platform side, laying a solid foundation for remote control. + +## 13.2 Content management + +It provides functions of compliance assessment, content injection and cloud-based processing for cloud VR contents so that they are able to run based on cloud resource pools. + +- Compliance evaluation: It automatically or manually evaluates the copyright legitimacy, user experience effectiveness and functional reliability of relevant cloud VR contents to ensure that they meet the online requirements. +- Content injection: It completes the VR content platform injection process, such as installing files to import into the platform. +- Cloud-based processing: VR contents running in terminals need connection debugging of the cloud operating environment and remote control to ensure that the terminal is able to utilize capabilities of cloud resource pool on the platform side to run VR contents. + +## 13.3 Operation management + +For operation and maintenance personnel of the operation, it provides comprehensive management functions of system configuration, operation and maintenance monitoring, data management, service strategy, etc. + +- System configuration: It provides installation and deployment of management and service related software, software updates, management permission control and other functions for cloud VR platform. +- Operation and maintenance monitoring: It provides management control of platform related software resources, hardware resources and cloud VR service functions, and alarm for various hidden dangers during the operation of the platform. +- Data management: It provides cloud VR related operation data management, including data verification, data processing, data desensitization, data normalization, data mining and result display. +- Service strategy: It provides strategic functions for product packaging, sales pricing, preferential settings and so on for cloud VR services. + +## 13.4 Cooperation management + +For cloud VR content providers, it provides management functions such as operation tracking and market settlement, etc. + +- Operation tracking: It provides the operation status of cloud VR contents to content providers who can modify and improve cloud VR contents according to actual market feedback. +- Market settlement: It provides the actual market revenue of relevant cloud VR contents, and it is recommended to have the function of online settlement on time. + +## 13.5 Resource management + +It provides management functions of computing resources, storage resources, data resources, etc. + +- Computing resource management: It provides real-time monitoring of the current usage and remaining status of resources (such as server resources, virtual machine resources and container resources) to support cloud VR service operation; and provides real-time monitoring of the computing resources related to different computing nodes. +- Storage resource management: It provides monitoring functions for the usage of storage resources related to the current platform in a certain period. +- Data resource management: It provides functions of effective storage, resource allocation and distribution processing for the progress data strongly related to cloud VR contents and users. +- Running status monitoring: it monitors the occupancy of hardware resources such as CPU, GPU, memory and storage of each server, which lays the foundation for resource scheduling. +- Fault alarm monitoring: It monitors operating temperature, hardware faults, software alarms and other related information of each server. + +## 13.6 Technology integration management + +### 13.6.1 Cloud connectivity + +Through the technology integration management function, the technology integration services on the cloud side can be accessed, deployed, updated and uninstalled. + +- Technology integration access: It has a common interface to achieve various compliant cloud VR technology integration service certification and access, and provides cloud VR operation, CDN, cloud coding streaming, cloud rendering and other services. +- Technology integration deployment: For the cloud VR technology integration service that completes the access, the cloud-edge collaborative service deployment based on the cloud resource pool is realized, so that it can provide relevant cloud VR services to users. +- Technology integration update: After the relevant cloud VR technology integration service is deployed, it can support online version upgrades for the purpose of correcting errors and adding functional modules. +- Technology integration uninstall: When the relevant cloud VR technology integration service needs to be stopped, it is equipped to support its online uninstallation of related services in order to achieve the clearing of the corresponding function point. + +### 13.6.2 Terminal binding + +Through the technology integration management function, the technology integration service on the terminal side can be integrated, updated and uninstalled. + +- Technology integration integrate: It has a common interface to realize various compliant cloud VR technology integration services integrated into the terminal side, and realize the functions of service request, service acquisition, service display and control feedback on the terminal side. +- Technology integration update: The cloud VR technology integration service for terminal docking needs to support online version upgrades for the purpose of correcting errors and adding functional modules. +- Technology integration uninstall: When the relevant cloud VR technology integration service needs to be stopped, it supports the uninstallation of services on the terminal side. + +## **13.7 Network capability binds management** + +- Network authentication capability binding: It connects to the relevant authentication systems of network operators to obtain authentication permissions for network QOS services, network slicing services and network acceleration services. +- Network service interconnection: By stacking the capabilities of network operators, it has the ability to call QOS services, network slice services and network acceleration services end-to-end. + +## **13.8 Terminal management** + +- Terminal binding: By obtaining the device information on the terminal side, the terminal is connected to the cloud VR system, and the cloud storage of information such as terminal model, operation capability, decoding capability, screen display capability and control capability is completed synchronously. +- Capability matching: Through unified terminal management, it completes the matching of relevant functions of cloud VR system and built-in network capabilities. + +# **14 Functions of security for cloud virtual reality systems** + +## **14.1 Whole-process security** + +In the process of providing related services for cloud VR systems, it is necessary to provide end-to-end antivirus, process (logical) security assurance, security audit and other services for the whole process. + +- End-to-end antivirus: In the end-to-end service process of cloud VR systems, it is necessary to establish and adopt antivirus mechanisms such as detection, protection, isolation, and removal to complete the protection or deletion of malware and malicious attacks. +- Process (logical) security assurance: For each functional module of cloud VR systems, a security guarantee mechanism is provided to isolate each other during logical processing to ensure that if one of the functional bodies has a problem with the operation, it can be isolated without affecting the service provision of other functions that they are not related to it. +- Security audit: Comprehensive analysis of system access permissions, service acquisition, service quality, and other related logs, combined with AI and other prediction methods, in order to obtain audit functions for discovering, predicting and timely handling related faults. + +## **14.2 Content compliance** + +The content provided by the cloud VR systems needs to provide security mechanisms such as genuine protection, youth protection and fair use guarantees. + +- Genuine protection: The cloud VR systems must provide legitimate authorized application content, and provide a copyright protection mechanism during the issuance and opening process, and prohibit illegal operations such as recompilation, data interception and tampering of application content. +- Youth protection: The application content provided by the cloud VR system needs to have a guarantee mechanism for the physical and mental health of youth, such as reminders of usage time, content suitability descriptions and anti-fraud reminders. +- Fair use mechanism: The application content provided by the cloud VR systems has the function of preventing other non-compliant tools to ensure fairness in the use of content. +- Content data security: For cloud VR content, establish an anti-tampering mechanism to prevent piracy and illegal changes to progress files. For the progress file corresponding to each content for the user, the backup mechanism is adopted to avoid damage or loss. + +## 14.3 Service security + +The cloud VR service system needs to provide mechanisms such as service access/call security, inter-user service security and service node security domain. + +- Service access/call security: Only after service usage permission authentication can access/call permissions for various functional modules of cloud VR systems be obtained. +- Inter-user service security: The related functions of the cloud VR systems provide users with a relatively isolated service security mode, which user services between different service nodes and between different servers of the same node have security isolation attributes to avoid mutual interference and fault correlation. +- Service node security domain: For each service node related to the cloud VR systems, a domain specific security processing mechanism is adopted. Divide security domains according to service nodes, and deploy security measures such as firewalls, intrusion detection, abnormal traffic detection and filtering to ensure that faults within the security domain do not overflow and effectively isolate security issues outside the domain. + +## 14.4 Data asset security + +It provides effective encryption and other mechanisms to ensure the security of user privacy, metadata, operation data and content data security during cloud VR services. + +- User privacy security: The cloud VR systems prohibit the collection and storage of user biometric data, encrypt personal privacy data such as user age, contact information and service usage, and prohibit non-compliant query and storage by operation and maintenance personnel. +- Metadata security: Ensure the stability of the metadata of the cloud VR systems, and have strict permission control for adding, modifying and deleting metadata, and provide a synchronization/update mechanism for the associated database/form during the metadata change process, as well as a rollback mechanism for the failed version. +- Operational data security: According to the industry or business sensitivity, establish a hierarchical processing mechanism for business operation data and the corresponding access level settings to ensure the security attributes of relevant operation data of cloud VR systems. + +## 14.5 Cloud resource security + +Cloud VR systems require cloud resource pools with software and hardware security guarantees, and deploy cloud VR services and call computing, rendering and storage capabilities through secure interactive interfaces. + +## 14.6 Network security + +In the process of network data transmission, relevant encryption processing is carried out to prevent packet splitting, tampering, network attacks and virus intrusion, and ensure that network capabilities call security, data integrity services and data confidentiality services. + +- Network user authentication: Through the authentication and permission verification of identified entities (including users and devices) related to the network system, it can not only prevent unauthorized users from illegally accessing network resources, but also prevent legitimate users from accessing unauthorized users. +- Transmission data integrity service: In order to meet the data integrity requirements of different users and different occasions of the cloud VR systems, different data integrity functions are provided through relevant network transmission protocols and policies, such as connection-oriented data integrity with recovery function, connection-oriented data integrity without recovery function, data integrity facing the selection field connection, data integrity facing the selection field without connection, and data integrity without connection. + +- Transmission data confidentiality services: In order to avoid passive threats such as information leakage and eavesdropping during network transmission, it is necessary to provide security protection and defence measures, such as encryption and other methods to protect information or data in network transmission. + +## **14.7 User experience security** + +In order to prevent simulator sickness and ensure a safe user experience of cloud VR systems, it is necessary to make full use of the cloud-edge system mechanism to reduce the cloud and network processing latency during the computing and rendering process; based on AI and other mechanisms, predict the user's motion trajectory, and use pre-processing to reduce the delay of motion processing; improve the picture quality in the process of using the cloud VR systems through image enhancement processing; in view of the user experience problems that may be caused by long-term use, friendly reminders with a set duration are used to ensure the safety of the experience of the cloud VR system. + +- Cloud-edge collaboration reduces latency: Multimedia resources in areas that are not currently of user's interest are delivered to edge nodes close to users in advance for timely processing during changes, reducing the response delay when FOV changes caused by user motion. +- Pre-processing reduces latency: By collecting and comprehensively processing the motion data of the user's desensitization when the FOV changes, based on the relevant information of the cloud VR terminal sensor, the direction, angle and distance of the motion are predicted in advance, and the cloud performs relevant multimedia processing in advance according to the prediction results, shortening the user's motion acquisition time and improving the timeliness of service. +- Enhanced processing to improve quality: In view of the problem that the multimedia quality of the current user's concern area may be insufficient during the change of user FOV, the AI mechanism can effectively improve the user's experience quality. +- Effective reminder of usage time: When users use the cloud VR system to reach the duration period that affects health or experience quality, provide corresponding friendly reminders, and recommend users to take a break. + +## Bibliography + +- [b-ITU-T H.264] Recommendation ITU-T H.264 (in force), *Advanced video coding for generic audiovisual services*. +- [b-ITU-T H.265] Recommendation ITU-T H.265 (in force), *High efficiency video coding*. + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.450.1-201105-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.450.1-201105-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.450.1-201105-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/098802c99831a6a7d445310d5e874e16_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/098802c99831a6a7d445310d5e874e16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3bdbce7d9ea6a3d6b6539d9836d7a22a4f91c87 --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/098802c99831a6a7d445310d5e874e16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb3dfe2b52478c3f9370c542f42444e0fa98247c17412a02e1f2f114f3ae5dd7 +size 24807 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..285f474c19675a2b1a6104807289e085be5ef38a --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f459bf9e8fa86b6334dd153ec475cb55b1e09a187175ab07d380d655ea7b5481 +size 30211 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..947f724b78ab1cd31b64b7eb4b38598e94fd550c --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50564399c2925936009d0f58c8e5016926822752683053b59f3a5d7f35b8cfb6 +size 98925 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a62286976f3a1ce7fc71ee068e6acab0407f82eb --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8e9f9f45357efaeffb6d884e7e1122c9a73a37c4367ea633d910e258fdaf781 +size 31765 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9baf4dac29a45693f0dadef34676df48064f6e8c --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8e83bce95d2f1a1889ff8f3b55e1163fda18f35c4282b78d03b4730de41259a +size 92190 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c +size 8232 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ab408758d1ff15b365debfc98abf63497feb353 --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2d0ce0718ebc725f73010853c8b3ebe6d9b24a81ef0f14c5cc714fb0a6a0084 +size 58413 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5538ef90415d16b7a4d53435b1fb2df6fd7258c --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad419e403e165a8f1ab961142fea3a3f1e9fdd7af9cd351d3b742d67bfce7550 +size 31620 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3e4f373aa5e73d75580236ea56810cf8155bcb9 --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:918e2e7ff25abce7071bab8a34b689184dea5f0deddcb83c23b99b9df22a7634 +size 25013 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ef456ddc34a4b230d06f29c41cf28097cada4cb --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e4ce5f6d920ae581086fc1c7a7c27d025b5aedaa7001499a7a8e15eb5dfe53f +size 97757 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85e5c6da0d5402664a7e6f196df609922eb5fb05 --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:078470734c66b6c8362c13ba5c6240e57ee66e61e52b11ab859218526aabb7bf +size 88283 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92f5af16afb40a6ff94eaf7d3e4c22026257c1e1 --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9638a328f0c1c8008748dd8e6df98f951cd86ada65447ba24cc5a2ef27be30d +size 39180 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.450.12-200107-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ace945aca0d01ae6bed57fd382ee6a51cfd7a3d --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46ebed8b33908e60ef4aa24be1151c34f5c4310331789edc1da79cd6082a4608 +size 98464 diff --git a/marked/H/T-REC-H.450.12-200107-I_PDF-E/raw.md b/marked/H/T-REC-H.450.12-200107-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..edd46adb7352cb99346c1b318da9badc6f7b1279 --- /dev/null +++ b/marked/H/T-REC-H.450.12-200107-I_PDF-E/raw.md @@ -0,0 +1,1197 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.450.12** + +(07/2001) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Supplementary services for multimedia + +# --- **Common Information Additional Network Feature for H.323** + +ITU-T Recommendation H.450.12 + +(Formerly CCITT Recommendation) + +--- + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| SYSTEMS AND TERMINAL EQUIPMENT FOR AUDIOVISUAL SERVICES | H.300–H.399 | +| SUPPLEMENTARY SERVICES FOR MULTIMEDIA | H.450–H.499 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Common Information Additional Network Feature for H.323** + +## **Summary** + +This Supplementary Service describes the procedures and the signalling protocol for the Common Information Additional Network Feature in ITU-T H.323 (Packet-based Multimedia Communications Systems) networks. + +ANF-CMN enables the exchange of Common Information between ANF-CMN endpoints. This Common Information is a collection of miscellaneous information that relates to the user or equipment at one end of a connection and includes one or more of the following: Feature Identifiers, Party Category. + +This Recommendation makes use of the "Generic functional protocol for the support of supplementary services in ITU-T H.323" as defined in ITU-T H.450.1. + +## **Source** + +ITU-T Recommendation H.450.12 was prepared by ITU-T Study Group 16 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 July 2001. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +###### Page + +| | | | +|--------|---------------------------------------------------------|---| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 1 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | ANF-CMN description ..... | 2 | +| 5.1 | Normal procedures..... | 2 | +| 5.1.1 | Activation/deactivation/registration/interrogation..... | 2 | +| 5.1.2 | Invocation and operation ..... | 2 | +| 5.2 | Exceptional procedures..... | 3 | +| 5.2.1 | Invocation and Operation ..... | 3 | +| 5.3 | Interactions with other supplementary services..... | 3 | +| 5.3.1 | Call Transfer (SS-CT) ..... | 3 | +| 5.3.2 | Call Forwarding Unconditional (SS-CFU)..... | 3 | +| 5.3.3 | Call Forwarding Busy (SS-CFB)..... | 3 | +| 5.3.4 | Call Forwarding on No Reply (SS-CFNR)..... | 3 | +| 5.3.5 | Call Hold..... | 3 | +| 5.3.6 | Call Park/Call Pickup ..... | 3 | +| 5.3.7 | Call Waiting..... | 4 | +| 5.3.8 | Message Waiting Indication ..... | 4 | +| 5.3.9 | Name Presentation..... | 4 | +| 5.3.10 | Completion of Calls on No Reply (SS-CCNR)..... | 4 | +| 5.3.11 | Completion of Calls on Busy Station (SS-CCBS)..... | 4 | +| 5.3.12 | Call Offer (SS-CO)..... | 4 | +| 5.3.13 | Call Intrusion (SS-CI)..... | 4 | +| 6 | Messages and information elements ..... | 4 | +| 6.1 | Feature Identifier List ..... | 4 | +| 6.2 | Feature values ..... | 6 | +| 6.2.1 | SS-CI protection level ..... | 6 | +| 6.2.2 | Party Category ..... | 6 | +| 6.3 | Feature Control ..... | 6 | +| 7 | Procedures..... | 6 | +| 7.1 | Actions at User A's Endpoint..... | 7 | +| 7.1.1 | Normal procedures ..... | 7 | +| 7.1.2 | Exceptional procedures..... | 7 | +| 7.2 | Actions at User B's Endpoint..... | 8 | +| 7.2.1 | Normal procedures ..... | 8 | + +| | Page | +|---------------------------------------------------------------------------------------------------|-------------| +| 7.2.2 Exceptional procedures..... | 8 | +| 8 Primitives..... | 9 | +| 8.1 Common Information Primitives..... | 9 | +| 8.2 Primitive definitions ..... | 9 | +| 8.3 Parameter definitions ..... | 9 | +| 9 Interworking and interactions ..... | 10 | +| 9.1 Interworking with an SCN..... | 10 | +| 9.2 Protocol interaction between ANF-CMN and other supplementary services..... | 10 | +| 9.2.1 Call Transfer (ITU-T H.450.2)..... | 10 | +| 9.2.2 Call Diversion (ITU-T H.450.3)..... | 10 | +| 9.2.3 Call Hold (ITU-T H.450.4)..... | 11 | +| 9.2.4 Call Park and Call Pickup (ITU-T H.450.5)..... | 11 | +| 9.2.5 Call Waiting (ITU-T H.450.6)..... | 11 | +| 9.2.6 Message Waiting (ITU-T H.450.7) ..... | 11 | +| 9.2.7 Name Presentation (ITU-T H.450.8)..... | 11 | +| 9.2.8 Call Completion (ITU-T H.450.9)..... | 11 | +| 9.2.9 Call Offer (SS-CO)..... | 11 | +| 9.2.10 Call Intrusion (SS-CI)..... | 11 | +| 10 Gatekeeper actions..... | 12 | +| 11 Dynamic description ..... | 12 | +| 11.1 Operational model and signal flows ..... | 12 | +| 11.1.1 Operational model ..... | 12 | +| 11.1.2 Example message sequence for normal operation of ANF-CMN for the solicited service ..... | 13 | +| 11.1.3 Example message sequence for normal operation of ANF-CMN for the unsolicited service ..... | 14 | +| 11.2 Timers ..... | 14 | +| 11.2.1 Timer T1 ..... | 14 | +| 12 Operations in support of Common Information Network service ..... | 15 | +| 13 Specification and Description Language (SDL) Diagrams for ANF-CMN ..... | 17 | +| 13.1 Behaviour of the endpoints using explicit primitive exchange..... | 19 | +| 13.2 Behaviour of the Endpoints using implicit application information exchange ..... | 23 | + +# Common Information Additional Network Feature for H.323 + +# 1 Scope + +This Recommendation describes supplementary services the Additional Network Feature Common Information (ANF-CMN), which is applicable to various basic services supported by ITU-T H.323 multimedia endpoints. + +ANF-CMN allows the exchange of Common Information between ANF-CMN endpoints. + +This Recommendation requires ITU-T H.323 version 2 (1998) or later. Version 2 products can be identified by ITU-T H.225.0 messages containing a **protocolIdentifier** = {itu-t (0) recommendation (0) h (8) 2250 version (0) 2} and ITU-T H.245 messages containing a **protocolIdentifier** = {itu-t (0) recommendation (0) h (8) 245 version (0) 3}. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of the Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T H.225.0 Version 4 (2000), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T H.245 Version 6 (2000), *Control protocol for multimedia communication*. +- ITU-T H.323 Version 4 (2000), *Packet-based multimedia communications systems*. +- ITU-T H.450.1 (1998), *Generic functional protocol for the support of supplementary services in H.323*. +- ITU-T H.450.2 (1998), *Call transfer supplementary service for H.323*. +- ITU-T H.450.3 (1998), *Call diversion supplementary service for H.323*. +- ITU-T H.450.4 (1999), *Call hold supplementary service for H.323*. +- ITU-T H.450.5 (1999), *Call park and call pickup supplementary services for H.323*. +- ITU-T H.450.7 (1999), *Message waiting indication supplementary service for H.323*. +- ITU-T H.450.9 (2000), *Call completion supplementary services for H.323*. +- ITU-T H.450.10 (2001), *Call offer supplementary service for H.323*. +- ITU-T H.450.11 (2001), *Call intrusion supplementary service for H.323*. + +# 3 Terms and definitions + +This Recommendation defines the following terms: + +**3.1 Endpoint; gatekeeper; gateway; terminal; user:** See ITU-T H.323. + +**3.2 Forward Direction:** The direction of the connection from the party invoking ANF-CMN to the other party in the call + +**3.3 ITU-T H.323 Call:** Refer to ITU-T H.323. + +- 3.4 Proxy:** An entity that acts on behalf of an endpoint. The proxy may or may not be co-located with the gatekeeper. +- 3.5 Reverse Direction:** The direction opposite to the forward direction. +- 3.6 User A:** Originating user that originated the call or requested the additional network feature. +- 3.7 User B:** The remote user that was initially addressed. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations: + +| | | +|---------|----------------------------------------| +| ANF | Additional Network Feature | +| ANF-CMN | ANF Common Information | +| APDU | Application Protocol Data Unit | +| ASN.1 | Abstract Syntax Notation one | +| IE | Information Element | +| NFE | Network Facility Extension | +| SDL | Specification and Description Language | +| SS | Supplementary Service | + +# **5 ANF-CMN description** + +ANF-CMN is an additional network feature that enables the exchange of Common Information between ANF-CMN endpoints. This Common Information is a collection of miscellaneous information that relates to the endpoint or equipment at one end of a connection and includes one or more of the following: Feature Identifiers, Feature Values, or Feature Controls. This information, when received by an ANF-CMN endpoint, can be used for any purpose, e.g. as the basis for indications to the local user or to another network or in order to filter feature requests. + +A solicited and an unsolicited service can be offered to an ANF-CMN endpoint (which may be located at either end of a connection). + +The solicited service enables the ANF-CMN endpoint to request the Common Information from a peer ANF-CMN endpoint. + +The unsolicited service enables an ANF-CMN endpoint to supply Common Information to a peer ANF-CMN endpoint. + +These services may be combined and are not mutually exclusive. + +## **5.1 Normal procedures** + +### **5.1.1 Activation/deactivation/registration/interrogation** + +ANF-CMN is permanently activated. + +### **5.1.2 Invocation and operation** + +The conditions under which ANF-CMN is invoked is an implementation matter. Also, Common Information offered by an endpoint is an implementation matter. + +An ANF-CMN endpoint may invoke ANF-CMN at any time during a call + +- to send its own Common Information to the peer ANF-CMN endpoint (unsolicited service); +- to request the Common Information of the peer ANF-CMN endpoint (solicited service). + +Sending and requesting the Common Information may be combined. + +NOTE – Typically, the Common Information is exchanged during the establishment phase of a call and after call rearrangement. + +On receiving a request for Common Information, the receiving ANF-CMN user shall respond with its Common Information. + +## **5.2 Exceptional procedures** + +### **5.2.1 Invocation and Operation** + +If no response is received on a request for Common Information (solicited service), the action to be taken shall be implementation dependent. + +## **5.3 Interactions with other supplementary services** + +### **5.3.1 Call Transfer (SS-CT)** + +Common Information relating to the transferred endpoint and the transferred to end point may be sent as part of the transferred call establishment. Otherwise, the information shall be sent subsequent to the transfer. + +### **5.3.2 Call Forwarding Unconditional (SS-CFU)** + +Common Information relating to the originating end of a call sent at the time of the call establishment request shall, if the call is diverted, be diverted to the ANF-CMN user at the terminating end of the diverted call. + +### **5.3.3 Call Forwarding Busy (SS-CFB)** + +Clause 5.3.2 shall apply. + +### **5.3.4 Call Forwarding on No Reply (SS-CFNR)** + +Unsolicited Common Information relating to the originating end of a call sent at the time of the call establishment request shall, if the call is diverted, be diverted to the ANF-CMN user at the terminating end of the diverted call. + +A request for solicited Common Information from the originating end of a call sent at the time of the call establishment request shall not, if the call is diverted, be diverted to the ANF-CMN user at the terminating end of the diverted call. + +### **5.3.5 Call Hold** + +No interaction. + +### **5.3.6 Call Park/Call Pickup** + +Common Information relating to the parked endpoint and the parked to endpoint may be sent as part of the parking call establishment. Otherwise, it shall be sent subsequent to Call Park. + +Common Information relating to the parked endpoint and the unparking endpoint may be sent as part of the unparking call establishment. Otherwise, it shall be sent subsequent to unpark. + +### 5.3.7 Call Waiting + +No interaction. + +### 5.3.8 Message Waiting Indication + +The SS-MWI Callback call indicator should be sent when placing the Callback Call. + +### 5.3.9 Name Presentation + +No interaction. + +### 5.3.10 Completion of Calls on No Reply (SS-CCNR) + +No interaction. + +### 5.3.11 Completion of Calls on Busy Station (SS-CCBS) + +No interaction. + +### 5.3.12 Call Offer (SS-CO) + +No interaction. + +### 5.3.13 Call Intrusion (SS-CI) + +If ANF-CMN is included prior to SS-CI invocation, the Call Intrusion Protection Level of the unwanted user is known, therefore the ciGetCIPL.inv and ciGetCIPL.res APDU exchange is not required. Actual SS-CI actions are implementation dependent. + +# 6 Messages and information elements + +The APDUs of the operations defined in clause 12 shall be conveyed within ITU-T H.450.1 Supplementary Service APDUs included in User-user information elements, as specified in ITU-T H.450.1. + +The operations defined in Abstract Syntax Notation One (ASN.1) in clause 12 shall apply. + +When conveying the invoke APDU of the operations defined in clause 12, the destinationEntity data element of the NFE shall contain the value *endpoint*. + +When conveying the invoke APDU of operation **cmnInform** the Interpretation APDU shall be included with the value discardAnyUnrecognizedInvokePdu. + +When conveying the invoke APDU of operation **cmnRequest**, the Interpretation APDU shall either be omitted or shall be included with the value rejectAnyUnrecognizedInvokePdu. + +## 6.1 Feature Identifier List + +The Feature Identifier list provides capability information related to supplementary services. This feature information about a remote user may for example be used by a user to determine the supplementary service set supported. + +The Feature Identifier list, when used in forward direction, shall include one or more of the Feature Identifiers listed in Table 1. + +**Table 1/H.450.12 – Feature Identifiers List in the Forward Direction** + +| Feature Identifiers | Values | Comments | +|-----------------------------------|---------------|---------------------------------------------------------------------------------------------------------| +| SS-CF rerouting supported | Yes/No | Originating Endpoint supporting Call Forwarding by Rerouting, meaningful only during call establishment | +| SS-CT rerouting supported | Yes/No | Originating Endpoint supporting Call Transfer Reroute | +| SS-CH far end Call Hold Supported | Yes/No | Originating endpoint supporting far end Call Hold (acting as a held endpoint) | +| SS-CP Call Park Supported | Yes/No | Originating endpoint supporting Call Park | + +The Feature Identifier list, when used in backward direction, shall include one or more of the Feature Identifiers listed in Table 2. + +**Table 2/H.450.12 – Feature Identifiers in the Backward Direction** + +| Feature Identifiers | Values | Comments | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SS-CT rerouting supported | Yes/No | Terminating Endpoint supporting Call Transfer Reroute | +| SS-CC CCBS supported | Yes/No | Terminating Endpoint supports Call Completion on Busy Subscriber, meaningful only before receipt of ALERTING/CONNECT | +| SS-CC CCNR supported | Yes/No | Terminating Endpoint supports Call Completion on No Reply, meaningful only before receipt of CONNECT | +| SS-CO supported | Yes/No | Terminating Endpoint supports Call offer, meaningful only before receipt of ALERTING/CONNECT | +| SS-CI supported:
    SS-CI Forced Release available
    SS-CI Isolation available
    SS-CI Wait on Busy available
    SS CI Silent monitor supported
    SS-CI Conference available |
    Yes/No
    Yes/No
    Yes/No
    Yes/No
    Yes/No | Call Intrusion options supported at the Terminating endpoint (i.e. at the wanted user's Endpoint B), meaningful only before receipt of ALERTING/CONNECT for the intruding call | +| SS-CH far end Call Hold Available | Yes/No | Terminating endpoint supporting far end Call Hold when requested by the Originating endpoint | +| SS-MWI Call Back Supported | Yes/No | Terminating endpoint supporting Message Waiting Callback, meaningful only before receipt of ALERTING/CONNECT | +| SS-CP Call Park Supported | Yes/No | Terminating endpoint supporting Call Park | + +NOTE – The feature Identifier list may also be exchanged during the active phase of the call (e.g. after call rearrangements due to supplementary services). In such a case, the classification in "forward direction" and "backward direction" do not apply and all feature indication are applicable. + +## 6.2 Feature values + +### 6.2.1 SS-CI protection level + +The purpose of the SS-CI protection level in ANF-CMN provides for the exchange of protection levels prior to the invocation of SS-CI. This may eliminate the requirement to explicitly exchange this datum following the SS-CI invocation. + +This information may be sent in both directions. + +### 6.2.2 Party Category + +The purpose of the Party Category is to indicate, to another user, the category of a user involved in a call. An Originating endpoint may include an indication of the calling user category in the SETUP message. A Terminating Endpoint may include an indication of the called endpoint category in a backward message. + +Received Party Category information may be used to change the operation at the user's terminal. For example, depending on whether the calling or called party is an extension or an attendant, the internal call handling may invoke different options of a supplementary service related to that call. + +## 6.3 Feature Control + +The Feature Control information allows for additional feature control as indicated in Table 3. + +**Table 3/H.450.12 – Feature Control Information** + +| Feature Identifiers | Values | Comments | +|--------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SS-CH Do not hold | Yes/No | The sending endpoint shall not be put on hold (neither near end nor far end hold). Applicable in forward and backward direction | +| SS-CT Do not transfer | Yes/No | The sending endpoint shall not be transferred. Applicable in forward and backward direction | +| SS-MWI Callback call indicator | Yes/No | Applicable only in SETUP message of a callback call (ITU-T H.450.7) | +| SS-CI Silent monitor permitted | Yes/No | Applicable in forward or backward direction indicating that this endpoint may be silent monitored (applicable for an endpoint that later on becomes an unwanted endpoint as part of an SS-CI Silent monitoring request) | + +# 7 Procedures + +The following procedures are a combination of call related signalling. + +All ANF-CMN control information is exchanged between User A's endpoint and User B's endpoint. + +## 7.1 Actions at User A's Endpoint + +### 7.1.1 Normal procedures + +#### 7.1.1.1 ANF-CMN invocation + +To invoke the solicited service of ANF-CMN, i.e. to request common information from the remote side, the Originating endpoint shall send a **CmnRequest invoke APDU**. For invocation during the establishment phase of a call, the APDU may either be sent within a SETUP message or within a FACILITY message using the call reference of that call. However, the FACILITY message shall not be used before the first end-to-end basic call message (i.e. ALERTING, CONNECT, PROGRESS) has been received. For invocation during the active phase of a call, the APDU shall be sent within a FACILITY message using the call reference of that call. Only if the **CmnRequest invoke APDU** is sent in a FACILITY message, timer T1 shall be started. If the **CmnRequest invoke APDU** is sent in a SETUP message, basic call timers provide sufficient protection. In both cases, after sending the **CmnRequest invoke APDU**, the Originating endpoint shall enter the CMN-Wait-Answer state. + +In the CMN-Wait-Answer state, upon receipt of a **CmnRequest return result APDU** in a basic call message (e.g. ALERTING, CONNECT, PROGRESS) or in a FACILITY message, the Originating endpoint shall stop timer T1, if running, and enter the CMN-Idle state. + +NOTE – The common information contained in the received **CmnRequest return result APDU** should be conveyed to the ANF-CMN user. + +To invoke the unsolicited service of ANF-CMN, i.e. to send unsolicited common information to the remote side, the Originating Endpoint shall send a **CmnInform invoke APDU**. For invocation during the establishment phase of a call, the APDU may either be sent within a SETUP message or within a FACILITY message using the call reference of that call. However, the FACILITY message shall not be used before the first end-to-end basic call message (i.e. ALERTING, CONNECT, PROGRESS) has been received. For invocation during the active phase of a call, the APDU shall be sent within a FACILITY message using the call reference of that call. + +### 7.1.2 Exceptional procedures + +In the CMN-Wait-Answer state, upon receipt of any message containing a **CmnRequest reject APDU**, the Originating Endpoint shall stop timer T1, if running, and enter the CMN-Idle state, and the call shall continue in accordance with ITU-T H.323 and ITU-T H.225.0. + +Upon expiry of timer T1 the Originating Endpoint shall enter the CMN-Idle state and the call shall continue in accordance with ITU-T H.323 and ITU-T H.225.0. + +In the CMN-Wait-Answer state, if timer T1 is not running (i.e. the **CmnRequest invoke APDU** was sent in a SETUP message), the receipt of a CONNECT message that does not contain a **CmnRequest return result or reject APDU** shall cause state CMN-Idle to be entered. + +If the basic call is cleared, while in the CMN-Wait-Answer state, timer T1 shall be stopped and the CMN-Idle state shall be entered. + +NOTE – Failure of ANF-CMN should be indicated to the ANF-CMN user. + +## 7.2 Actions at User B's Endpoint + +### 7.2.1 Normal procedures + +Upon receipt of a **CmnRequest invoke APDU** in a SETUP or a FACILITY message, the Terminating Endpoint, if common information is available, shall send a **CmnRequest return result APDU** in order to send the solicited common information to the remote side and remain in the CMN-Idle state. The **CmnRequest return result APDU** may either be sent within a basic call message (e.g. ALERTING, CONNECT, PROGRESS) or within a FACILITY message using the call reference of that call. However, if the **CmnRequest invoke APDU** was received in a SETUP message, the **CmnRequest return result APDU** shall be sent within the CONNECT message, if not already sent. + +Upon receipt of a **CmnInform invoke APDU** in any message, the Terminating Endpoint shall remain in the current state. + +NOTE 1 – The common information contained in the received **CmnInform invoke APDU** should be conveyed to the ANF-CMN user. + +To invoke the solicited service of ANF-CMN in backward direction, the Terminating Endpoint shall send a **CmnRequest invoke APDU**, start timer T1 and enter the CMN-Wait-Answer state. For invocation during the establishment phase of a call, the APDU may either be sent within a basic call message (e.g. ALERTING, CONNECT, PROGRESS) or within a FACILITY message using the call reference of that call. For invocation during the active phase of a call, the APDU shall be sent within a FACILITY message using the call reference of that call. + +In the CMN-Wait-Answer state, upon receipt of a **CmnRequest return result APDU** in a FACILITY message, the Terminating Endpoint shall stop timer T1 and enter the CMN-Idle state. + +NOTE 2 – The common information contained in the received **CmnRequest return result APDU** should be conveyed to the ANF-CMN user. + +To invoke the unsolicited service of ANF-CMN in backward direction, the Terminating Endpoint shall send a **CmnInform invoke APDU**. For invocation during the establishment phase of a call, the APDU may either be sent within a basic call message (e.g. ALERTING, CONNECT, PROGRESS) or within a FACILITY message using the call reference of that call. For invocation during the active phase of a call, the APDU shall be sent within a FACILITY message using the call reference of that call. + +NOTE 3 – The **CmnInform invoke APDU** contains the common information provided by the ANF-CMN user. + +### 7.2.2 Exceptional procedures + +In the CMN-Wait-Answer state, upon receipt of any message containing a **CmnRequest reject APDU**, the Terminating Endpoint shall stop timer T1 and enter the CMN-Idle state, and the call shall continue in accordance with ITU-T H.323 and ITU-T H.225.0. + +Upon expiry of timer T1 the Terminating Endpoint shall enter the CMN-Idle state and the call shall continue in accordance with ITU-T H.323 and ITU-T H.225.0. + +If the basic call is cleared, while in the CMN-Wait-Answer state, timer T1 shall be stopped and the CMN-Idle state shall be entered. + +NOTE – Failure of ANF-CMN should be indicated to the ANF-CMN user. + +# 8 Primitives + +## 8.1 Common Information Primitives + +See Table 4. + +**Table 4/H.450.12 – Common Information Primitives** + +| Generic Name | Type | | | | +|------------------------------------------------------------------------------|------------|------------|-------------|-------------| +| | request | indication | response | confirm | +| CMNRequest | – | – | PARAMETERS | PARAMETERS | +| CMNInform | PARAMETERS | PARAMETERS | Not defined | Not defined | +| NOTE – "–" means no parameters (manufacturer specific parameters may apply). | | | | | + +## 8.2 Primitive definitions + +The definition of these primitives is as follows: + +- a) the CMNRequest request primitive is used to solicit the common information from the remote end; +- b) the CMNRequest indication primitive is used to indicate that the far end is requesting the common information; +- c) the CMNRequest response primitive is used to return the common information to the far end; +- d) the CMNRequest confirm primitive is used to receive either the common information from the far end or received service failure conditions; +- e) the CMNInform request primitive is used to provide the unrequested common information to the far end; +- f) the CMNInform indication primitive is used to receive the unrequested common information from the far end. + +## 8.3 Parameter definitions + +### CMNRequest.request parameters + +- None + +### CMNRequest.indication parameters + +- None + +### CMNRequest.response parameters + +- featureList, an indication of supported features and services; +- featureControl, control of specific features; +- partyCategory, the category of the user involved in the call. + +### CMNRequest.confirm parameters + +- Parameters related to service failure conditions: + - failure indication, e.g. rejection, error, call cleared, timer expiry, etc.; + - related failure parameters are application defined, but should include information from the related APDU (CMNRequest Reject or CMNRequest Error) if applicable. + +- Parameters related to successful operation: + - featureList, an indication of supported features and services of the remote end; + - featureControl, control of specific features of the remote end; + - partyCategory, the category of the user involved in the call at the remote end. + +### **CMNInform request parameters** + +- featureList, an indication of supported features and services; +- featureControl, control of specific features; +- partyCategory, the category of the user involved in the call. + +### **CMNInform indication parameters** + +- featureList, an indication of supported features and services of the remote end; +- featureControl, control of specific features of the remote end; +- partyCategory, the category of the user involved in the call at the remote end. + +# **9 Interworking and interactions** + +## **9.1 Interworking with an SCN** + +ANF-CMN may interwork with corresponding services as defined by other standards by means of gateway interworking functions. The specification of detailed gateway interworking procedures is beyond the scope of this Recommendation. + +## **9.2 Protocol interaction between ANF-CMN and other supplementary services** + +This clause specifies protocol interactions of ANF-CMN with other supplementary services for which ITU-T H.450.x family of Recommendations had been published at the time of publication of this Recommendation. For interactions with supplementary services for which ITU-T H.450.x family of Recommendations are published subsequent to the publication of this Recommendation, see those other ITU-T H.450.x family of Recommendations. + +### **9.2.1 Call Transfer (ITU-T H.450.2)** + +**SsCTreRoutingSupported** allows an early indication of support for SS-CT. + +**ssCTDoNotTransfer** indicates that an endpoint will not allow itself to be transferred. The actual actions taken by that endpoint in the case of an attempted call transfer is implementation dependent and may include clearing the call. + +NOTE – Common Information may be exchanged between primary endpoint and secondary endpoint during transferred call establishment or subsequent to call transfer. In this case the primary endpoint is considered to be the originating endpoint and the secondary endpoint to be the terminating endpoint. + +### **9.2.2 Call Diversion (ITU-T H.450.3)** + +#### **9.2.2.1 Call Forwarding Unconditional (SS-CFU)** + +**SsCFreRoutingSupported** allows an early indication of support for SS-CFU. + +The following interactions shall apply if SS-CFU is supported in accordance with ITU-T H.450.3. + +##### 9.2.2.1.1 Actions at a SS-CFU Rerouting Endpoint + +When executing SS-CFU, the Rerouting Endpoint, Gatekeeper, or Feature Proxy shall include a CmnRequest invoke APDU (for the ANF-CMN solicited service) and/or a CmnInform invoke APDU (for the unsolicited service) in the SETUP message to the Diverted-to Endpoint if this was included in the SETUP message to the Served User Endpoint. + +#### 9.2.2.2 Call Forwarding Busy (SS-CFB) + +**SsCFreRoutingSupported** allows an early indication of support for SS-CFB. + +If SS-CFB is supported in accordance with ITU-T H.450.3, the procedures specified in clause 9.2.2.1 of this Recommendation shall apply, with SS-CFU replaced by SS-CFB. + +#### 9.2.2.3 Call Forwarding No Reply (SS-CFNR) + +**SsCFreRoutingSupported** allows an early indication of support for SS-CFNR. + +Clause 9.2.2.1 shall apply with "SS-CFU" replaced by "SS-CFNR". + +#### 9.2.2.4 Call Deflection (SS-CD) + +**SsCFreRoutingSupported** allows an early indication of support for SS-CD. + +Clause 9.2.2.1 shall apply with "SS-CFU" replaced by "SS-CD". + +### 9.2.3 Call Hold (ITU-T H.450.4) + +**ssCHDoNotHold** indicates that an endpoint will not allow itself to be held. This refers to both near end hold and far end hold. The actual actions taken by that endpoint in the case of an attempted call hold is implementation dependent and may include clearing the call. + +### 9.2.4 Call Park and Call Pickup (ITU-T H.450.5) + +**SsCPSupported** allows an early indication of support for SS-CP. + +### 9.2.5 Call Waiting (ITU-T H.450.6) + +No protocol interaction. + +### 9.2.6 Message Waiting (ITU-T H.450.7) + +**SsMWICallbackSupported** allows an early indication of support for SS-MWI Call Back activation when SS-MWI Activation follows a non-successful call. + +**SsMWICallbackCall** indicates that the SETUP is for a call that is a Callback Call for SS-MWI. + +### 9.2.7 Name Presentation (ITU-T H.450.8) + +No protocol interaction. + +### 9.2.8 Call Completion (ITU-T H.450.9) + +**SsCCBSPossible** allows an early indication of support for SS-CCBS. + +**SsCCNRPossible** allows an early indication of support for SS-CCNR. + +### 9.2.9 Call Offer (SS-CO) + +**SsCOSupported** allows an early indication of support for SS-CO. + +### 9.2.10 Call Intrusion (SS-CI) + +**SsCIForcedReleaseSupported** allows an early indication of support for the Forced Release feature of SS-CI. + +**SsCIIsolationSupported** allows an early indication of support the Isolation feature of SS-CI. + +**SsCIWaitOnBusySupported** allows an early indication of support for the Wait on Busy feature of SS-CI. + +**SsCISilentMonitorSupported** allows an early indication of support for the Silent Monitor feature of SS-CI. + +**SsCIConferenceSupported** allows an early indication of support for Conference feature of SS-CI. + +**SsCIProtectionLevel** allows an early indication of the endpoints protection level for SS-CI. + +**SsCISilentMonitor** indicates whether the unwanted endpoint allows for silent monitor. The actual actions taken by that endpoint in the case of an attempted to silent monitor is implementation dependent and may include clearing the call. + +# 10 Gatekeeper actions + +In a Gatekeeper Routed Call where the Gatekeeper acts for the endpoint in the execution of supplementary service, all references to the endpoint may be replaced with Gatekeeper. + +# 11 Dynamic description + +## 11.1 Operational model and signal flows + +This clause describes some typical message flows for ANF-CMN. The following conventions are used in the figures of this clause. + +- 1) The following notation is used: + +| | | +|---------|--------------------------------------| +| —————→ | Call-related protocol message | +| SETUP | Message name | +| Cx | Number of connection x | +| xxx.inv | Invoke APDU for operation xxx | +| xxx.rr | Return result APDU for operation xxx | + +- 2) The figures show ITU-T H.225.0 messages exchanged between Endpoints involved in ANF-CMN. Only messages relevant to ANF-CMN are shown. +- 3) Only the relevant information content (e.g. remote operation APDUs) is listed below each message name. Information with no impact on ANF-CMN is not shown. +- 4) Some interactions with users are included in the form of symbolic primitives. The actual protocol at the terminal equipment interface is outside the scope of this Recommendation. + +### 11.1.1 Operational model + +Figure 1 shows the operational model for Common Information. + +![Figure 1/H.450.12 – Operational model for ANF-CMN. The diagram shows three stages: 'Before service', 'During service', and 'After service'. Each stage shows two boxes labeled 'Endpoint A' and 'Endpoint B' connected by a line. Below each stage is the text 'Call from A to B'. A small code 'T1610000-01' is in the bottom right corner.](098802c99831a6a7d445310d5e874e16_img.jpg) + +Before service                      During service                      After service + +Endpoint A — Endpoint B      Endpoint A — Endpoint B      Endpoint A — Endpoint B + +Call from A to B                  Call from A to B                  Call from A to B + +T1610000-01 + +Figure 1/H.450.12 – Operational model for ANF-CMN. The diagram shows three stages: 'Before service', 'During service', and 'After service'. Each stage shows two boxes labeled 'Endpoint A' and 'Endpoint B' connected by a line. Below each stage is the text 'Call from A to B'. A small code 'T1610000-01' is in the bottom right corner. + +**Figure 1/H.450.12 – Operational model for ANF-CMN** + +### 11.1.2 Example message sequence for normal operation of ANF-CMN for the solicited service + +Figures 2 and 3 show successful ANF-CMN request and response scenarios for the solicited service. + +![Sequence diagram for Figure 2 showing ANF-CMN message flow between User A's and User B's endpoints. The sequence starts with 'Normal Basic Call A-B (Idle)', followed by a 'SETUP (C1)' message (cmnRequest.inv) from User A to User B, then an 'ALERT (C1)' message (cmnRequest.rr) from User B to User A, and finally 'Normal Basic Call A-B (Alerting)'. A 'T1' label is present on the left side.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +Sequence diagram illustrating the message flow for ANF-CMN (solicited service) between User A's Endpoint and User B's Endpoint. + +The sequence starts with a **Normal Basic Call A-B (Idle)** state. + +From User A's Endpoint, a **SETUP (C1)** message (*cmnRequest.inv*) is sent to User B's Endpoint. + +From User B's Endpoint, an **ALERT (C1)** message (*cmnRequest.rr*) is sent back to User A's Endpoint. + +The sequence ends with a **Normal Basic Call A-B (Alerting)** state. + +A label **T1** is present on the left side of the diagram. + +Reference: T1610010-01 + +Sequence diagram for Figure 2 showing ANF-CMN message flow between User A's and User B's endpoints. The sequence starts with 'Normal Basic Call A-B (Idle)', followed by a 'SETUP (C1)' message (cmnRequest.inv) from User A to User B, then an 'ALERT (C1)' message (cmnRequest.rr) from User B to User A, and finally 'Normal Basic Call A-B (Alerting)'. A 'T1' label is present on the left side. + +Figure 2/H.450.12 – Example message flow of ANF-CMN (solicited service) + +![Sequence diagram for Figure 3 showing ANF-CMN message flow between User A's and User B's endpoints. The sequence starts with 'Normal Basic Call A-B', followed by a 'FACILITY (C1)' message (cmnRequest.inv) from User A to User B, then another 'FACILITY (C1)' message (cmnRequest.rr) from User B to User A, and finally 'Normal Basic Call A-B'. A 'T1' label is present on the left side.](10781f43062bf3e9601a1e086710556c_img.jpg) + +Sequence diagram illustrating the message flow for ANF-CMN (solicited service) between User A's Endpoint and User B's Endpoint. + +The sequence starts with a **Normal Basic Call A-B** state. + +From User A's Endpoint, a **FACILITY (C1)** message (*cmnRequest.inv*) is sent to User B's Endpoint. + +From User B's Endpoint, another **FACILITY (C1)** message (*cmnRequest.rr*) is sent back to User A's Endpoint. + +The sequence ends with a **Normal Basic Call A-B** state. + +A label **T1** is present on the left side of the diagram. + +Reference: T1610020-01 + +Sequence diagram for Figure 3 showing ANF-CMN message flow between User A's and User B's endpoints. The sequence starts with 'Normal Basic Call A-B', followed by a 'FACILITY (C1)' message (cmnRequest.inv) from User A to User B, then another 'FACILITY (C1)' message (cmnRequest.rr) from User B to User A, and finally 'Normal Basic Call A-B'. A 'T1' label is present on the left side. + +Figure 3/H.450.12 – Example message flow of ANF-CMN (solicited service) + +### 11.1.3 Example message sequence for normal operation of ANF-CMN for the unsolicited service + +Figures 4 and 5 show successful ANF-CMN scenarios for the unsolicited service. + +![Sequence diagram for Figure 4 showing the normal operation of ANF-CMN for an unsolicited service. It starts with 'Normal Basic Call A-B (Idle)', followed by a 'SETUP (C1)' message from User A's Endpoint to User B's Endpoint, and ends with 'Normal Basic Call A-B'. The diagram is labeled T1610030-01.](5445597cceefaca1ac89e710fe339325_img.jpg) + +``` +sequenceDiagram + participant User A's Endpoint + participant User B's Endpoint + Note over User A's Endpoint, User B's Endpoint: Normal Basic Call A-B (Idle) + User A's Endpoint->>User B's Endpoint: SETUP (C1) +cmnInform.inv + Note over User A's Endpoint, User B's Endpoint: Normal Basic Call A-B + Note right of User B's Endpoint: T1610030-01 +``` + +Sequence diagram for Figure 4 showing the normal operation of ANF-CMN for an unsolicited service. It starts with 'Normal Basic Call A-B (Idle)', followed by a 'SETUP (C1)' message from User A's Endpoint to User B's Endpoint, and ends with 'Normal Basic Call A-B'. The diagram is labeled T1610030-01. + +Figure 4/H.450.12 – Example of normal operation of ANF-CMN (unsolicited service) + +![Sequence diagram for Figure 5 showing the normal operation of ANF-CMN for an unsolicited service. It starts with 'Normal Basic Call A-B (Idle)', followed by a 'SETUP (C1)' message from User A's Endpoint to User B's Endpoint, then an 'ALERT (C1)' message from User B's Endpoint back to User A's Endpoint, and ends with 'Normal Basic Call A-B (Alerting)'. The diagram is labeled T1610040-01.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` +sequenceDiagram + participant User A's Endpoint + participant User B's Endpoint + Note over User A's Endpoint, User B's Endpoint: Normal Basic Call A-B (Idle) + User A's Endpoint->>User B's Endpoint: SETUP (C1) +cmnInform.inv + User B's Endpoint->>User A's Endpoint: ALERT (C1) +cmnInform.inv + Note over User A's Endpoint, User B's Endpoint: Normal Basic Call A-B (Alerting) + Note right of User B's Endpoint: T1610040-01 +``` + +Sequence diagram for Figure 5 showing the normal operation of ANF-CMN for an unsolicited service. It starts with 'Normal Basic Call A-B (Idle)', followed by a 'SETUP (C1)' message from User A's Endpoint to User B's Endpoint, then an 'ALERT (C1)' message from User B's Endpoint back to User A's Endpoint, and ends with 'Normal Basic Call A-B (Alerting)'. The diagram is labeled T1610040-01. + +Figure 5/H.450.12 – Example of normal operation of ANF-CMN (unsolicited service) + +## 11.2 Timers + +### 11.2.1 Timer T1 + +Timer T1 shall operate during the CMN-Wait-Answer state, if the CmnRequest invoke APDU was not sent in a SETUP message. Its purpose is to protect against an absence of response to ANF-CMN invocation for the solicited service. + +Timer T1 shall have a value of not less than 30 seconds. + +# 12 Operations in support of Common Information Network service + +The operations defined in Abstract Syntax Notation one (ASN.1) below shall apply. + +``` +Common-Information-Operations +{ itu-t recommendation h 450 12 version1(0) common-information- + operations(0) } + +DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +IMPORTS + OPERATION, ERROR FROM Remote-Operations-Information-Objects + {joint-iso-itu-t remote-operations(4) + informationObjects(5) version1(0)} + EXTENSION, Extension{} FROM + Manufacturer-specific-service-extension-definition + { itu-t recommendation h 450 1 version1(0) msi- + definition(18) } + MixedExtension, undefined FROM Call-Hold-Operations + {itu-t recommendation h 450 4 version1(0) call-hold- + operations(0) } + +H323CommonInformationOperations OPERATION ::= +{cmnRequest | cmnInform} + +cmnRequest OPERATION ::= +{ + ARGUMENT DummyArg OPTIONAL TRUE + RESULT CmnArg + ERRORS { undefined } + CODE local: 84 +} + +cmnInform OPERATION ::= +{ + ARGUMENT CmnArg + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE local: 85 +} + +CmnArg ::= SEQUENCE +{ + featureList FeatureList OPTIONAL, + featureValues FeatureValues OPTIONAL, + featureControl FeatureControl OPTIONAL, + extension SEQUENCE SIZE (0..255) OF MixedExtension + OPTIONAL, + ... +} + +DummyArg ::= SEQUENCE +{ + extensionArg SEQUENCE SIZE (0..255) OF MixedExtension + OPTIONAL +} +``` + +``` + +FeatureList ::= SEQUENCE +{ + -- indicates capabilities of the endpoint sending - + -- the FeatureList + ssCFreRoutingSupported NULL OPTIONAL, -- Call Forwarding rerouting + -- supported meaningful only in + -- forward direction during call + -- establishment + ssCTreRoutingSupported NULL OPTIONAL, -- Call Transfer rerouting + -- supported meaningful both in + -- forward & backward direction + -- during call establishment + ssCCBSPossible NULL OPTIONAL, -- CCBS possible meaningful only + -- in backward direction before + -- receipt of ALERTING/CONNECT + ssCCNRPossible NULL OPTIONAL, -- CCNR possible meaningful only + -- in backward direction before + -- receipt of CONNECT + ssCOSupported NULL OPTIONAL, -- Call Offer supported + -- meaningful only in backward + -- direction during call + -- establishment + + -- Call Intrusion + ssCIForcedReleaseSupported NULL OPTIONAL, -- meaningful only in + -- backward direction + ssCIIsolationSupported NULL OPTIONAL, -- meaningful only in + -- backward direction + ssCIWaitOnBusySupported NULL OPTIONAL, -- meaningful only in + -- backward direction + ssCISilentMonitoringSupported NULL OPTIONAL, -- meaningful only in + -- backward direction + ssCIConferenceSupported NULL OPTIONAL, -- meaningful only in + -- backward direction + + -- Call Hold + ssCHFarHoldSupported NULL OPTIONAL, -- meaningful in both + -- directions + + -- Message Waiting Callback + ssMWICallbackSupported NULL OPTIONAL, -- meaningful in backward + -- direction + -- meaningful both in + -- forward & backward + -- direction during call + -- establishment + + -- Call Park + ssCPCallParkSupported NULL OPTIONAL, -- meaningful in both + -- directions + ... +} + +FeatureValues ::= SEQUENCE +{ + partyCategory PartyCategory OPTIONAL, + + ssCIprotectionLevel SSCIProtectionLevel OPTIONAL, + -- Supplementary Service Call Intrusion Protection level + -- meaningful both in forward and backward direction; inclusion + -- indicates support of SS-CI as an unwanted endpoint (forward + -- direction) or as a Terminating Endpoint (backward direction), + -- as well as the applicable protection level. + ... +} + +``` + +``` + +PartyCategory ::= ENUMERATED +{ + unknown, + extension, + attendant, + emergExt, + ... +} + +SSCIProtectionLevel ::= INTEGER (0..3) + +FeatureControl ::= SEQUENCE +{ + ssCHDoNotHold NULL OPTIONAL, -- meaningful in both directions + + ssCTDoNotTransfer NULL OPTIONAL, -- Sending endpoint shall not be held + -- meaningful in both directions + + ssMWICallbackCall NULL OPTIONAL, -- sending endpoint shall not be transferred + -- meaningful only in SETUP + + ssCISilentMonitorPermitted NULL OPTIONAL, -- indicating a callback call + -- unwanted endpoint + -- allows for + -- silent monitoring + -- meaningful in forward and backward direction + + ... +} + +END -- of Common-Information-Operations + +``` + +# 13 Specification and Description Language (SDL) Diagrams for ANF-CMN + +The procedures for Common Information signalling entities are described in SDL form in two series: + +- Figures 7 through 10 show the procedures where an explicit primitive exchange is performed to respond to a CMNRequest invoke. +- Figures 11 and 12 show the procedure when an explicit exchange is replaced by the processing "Get CMN". + +Since H.450.12 procedures are completely symmetrical, only the procedure for Endpoint A is shown in each case. + +The SDLs only show ANF-CMN specific information transported on an H.225.0 connection. H.245 procedures (e.g. terminal capability exchange, master/slave determination, opening and closing of logical channels, etc.) are not shown. The following abbreviations are used: + +| | | +|------|--------------------| +| BC | Basic Call | +| conn | Connection | +| conf | Confirmation | +| err | Return error APDU | +| ind | Indication | +| inv | Invoke APDU | +| rej | Reject APDU | +| res | Return result APDU | +| sig | Signalling | + +In case of a conflict between SDLs and the text within the previous clauses, the text shall take precedence. + +Specific gatekeeper/proxy SDLs for the model where a gatekeeper/proxy acts on ANF-CMN on behalf of an endpoint are not provided. + +The symbols used in the following SDLs are defined in Figure 6 SDL Symbols. + +![Figure 6/H.450.12 – SDL symbols. A collection of 9 shapes used in State Diagrams (SDLs). The shapes include: 1. A rectangle with a left-pointing chevron on the left side, labeled 'Primitive from endpoint user A or internal event'. 2. A rectangle with a right-pointing chevron on the right side, labeled 'Message to endpoint B'. 3. A rectangle with a left-pointing chevron on the right side, labeled 'Primitive from endpoint user B or internal event'. 4. A rectangle with a right-pointing chevron on the left side, labeled 'Message to endpoint A'. 5. A rectangle with a left-pointing chevron on the left side, labeled 'Primitive to endpoint user A'. 6. A rectangle with a right-pointing chevron on the right side, labeled 'Message form endpoint B'. 7. A rectangle with a left-pointing chevron on the right side, labeled 'Primitive to endpoint user B'. 8. A rectangle with a right-pointing chevron on the left side, labeled 'Message form endpoint A'. 9. A rounded rectangle with vertical lines at the ends, labeled 'Processing' and 'State'.](366a77fdefb0097b3289b4a011911390_img.jpg) + +Primitive from endpoint user A or internal event + +Message to endpoint B + +Primitive from endpoint user B or internal event + +Message to endpoint A + +Primitive to endpoint user A + +Message form endpoint B + +Primitive to endpoint user B + +Message form endpoint A + +Processing + +State + +T1610070-01 + +Figure 6/H.450.12 – SDL symbols. A collection of 9 shapes used in State Diagrams (SDLs). The shapes include: 1. A rectangle with a left-pointing chevron on the left side, labeled 'Primitive from endpoint user A or internal event'. 2. A rectangle with a right-pointing chevron on the right side, labeled 'Message to endpoint B'. 3. A rectangle with a left-pointing chevron on the right side, labeled 'Primitive from endpoint user B or internal event'. 4. A rectangle with a right-pointing chevron on the left side, labeled 'Message to endpoint A'. 5. A rectangle with a left-pointing chevron on the left side, labeled 'Primitive to endpoint user A'. 6. A rectangle with a right-pointing chevron on the right side, labeled 'Message form endpoint B'. 7. A rectangle with a left-pointing chevron on the right side, labeled 'Primitive to endpoint user B'. 8. A rectangle with a right-pointing chevron on the left side, labeled 'Message form endpoint A'. 9. A rounded rectangle with vertical lines at the ends, labeled 'Processing' and 'State'. + +**Figure 6/H.450.12 – SDL symbols** + +## 13.1 Behaviour of the endpoints using explicit primitive exchange + +![SDL diagram showing the behaviour of endpoints using explicit primitive exchange. It starts from a CMN-Idle state and branches into five paths based on input requests or messages. The paths lead to CMN-Idle, CMN-Wait-Answer, or CMN-Wait-Response states.](a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg) + +``` + +graph TD + Idle([CMN-Idle]) + + %% Path 1 + Idle --- Path1_Req[CMNInform Request] + Path1_Req --> Path1_Msg[Message with CMNInform.inv] + Path1_Msg --> Idle_End1([CMN-Idle]) + + %% Path 2 + Idle --- Path2_Msg[Message with CMNInform.inv] + Path2_Msg --> Path2_Ind[CMNInform Indication] + Path2_Ind --> Idle_End1 + + %% Path 3 + Idle --- Path3_Req[CMNInform + CMNRequest Request] + Path3_Req --> Path3_Msg1[Message with CMNInform.inv] + Path3_Msg1 --> Path3_Msg2[Message with CMNRequest.inv] + Path3_Msg2 --> Timer[Start Timer T1, if applicable] + Timer --> WaitAnswer([CMN-Wait-Answer]) + + %% Path 4 + Idle --- Path4_Req[CMNRequest Request] + Path4_Req --> Path4_Msg[Message with CMNRequest.inv] + Path4_Msg --> Timer + + %% Path 5 + Idle --- Path5_Msg[Message with CMNRequest.inv] + Path5_Msg --> Path5_Ind[CMNRequest Indication] + Path5_Ind --> WaitResponse([CMN-Wait-Response]) + + %% Notes + Note1[These may be sent in the same message] + Path3_Msg1 -.-> Note1 + Path3_Msg2 -.-> Note1 + + Note2[T1 only started if CMNRequest.inv is sent in a FACILITY message] + Timer -.-> Note2 + +``` + +These may be sent in the same message + +T1 only started if CMNRequest.inv is sent in a FACILITY message + +SDL diagram showing the behaviour of endpoints using explicit primitive exchange. It starts from a CMN-Idle state and branches into five paths based on input requests or messages. The paths lead to CMN-Idle, CMN-Wait-Answer, or CMN-Wait-Response states. + +**Figure 7/H.450.12 – SDL representation of ANF-CMN at Endpoint A (part 1)** + +![State transition diagram for ANF-CMN at Endpoint A (part 2).](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +``` + +stateDiagram-v2 + [*] --> CMN-Wait-Answer + CMN-Wait-Answer --> CMNRequest.res + CMN-Wait-Answer --> CMNRequest.rej + CMN-Wait-Answer --> Timer T1 Expiry + CMN-Wait-Answer --> CMNRequest.err + CMN-Wait-Answer --> Basic Call Cleared + CMN-Wait-Answer --> CMNInform.inv + CMNRequest.res --> Stop Timer T1 if running + Stop Timer T1 if running --> CMNRequest Confirm-Success + CMNRequest.rej --> Stop Timer T1 if running + Stop Timer T1 if running --> CMNRequest Confirm-Reject + Timer T1 Expiry --> Stop Timer T1 if running + Stop Timer T1 if running --> CMNRequest Confirm-Error + CMNRequest.err --> Stop Timer T1 if running + Stop Timer T1 if running --> CMNRequest Confirm-Error + Basic Call Cleared --> CMNRequest.inv + CMNRequest.inv --> CMNRequest Indication + CMNRequest Indication --> CMN-Wait-Answer-Response + CMNInform.inv --> CMNInform Indication + CMNInform Indication --> CMN-Wait-Answer + CMNRequest Confirm-Success --> CMN-Idle + CMNRequest Confirm-Reject --> CMN-Idle + CMNRequest Confirm-Error --> CMN-Idle + +``` + +The diagram illustrates the state transitions for ANF-CMN at Endpoint A. It begins in the **CMN-Wait-Answer** state. From here, several transitions are possible: + + +- A **Message with CMNRequest.res** leads to **Stop Timer T1 if running**, which then leads to the **CMNRequest Confirm-Success** state, which in turn leads to the **CMN-Idle** state. +- A **Message with CMNRequest.rej** leads to **Stop Timer T1 if running**, which then leads to the **CMNRequest Confirm-Reject** state, which in turn leads to the **CMN-Idle** state. +- Timer T1 Expiry** leads to **Stop Timer T1 if running**, which then leads to the **CMNRequest Confirm-Error** state, which in turn leads to the **CMN-Idle** state. +- A **Message with CMNRequest.err** leads to **Stop Timer T1 if running**, which then leads to the **CMNRequest Confirm-Error** state, which in turn leads to the **CMN-Idle** state. +- Basic Call Cleared** leads to a **Message with CMNRequest.inv**, which leads to the **CMNRequest Indication** state, which then leads to the **CMN-Wait-Answer-Response** state. +- A **Message with CMNInform.inv** leads to the **CMNInform Indication** state, which then leads back to the **CMN-Wait-Answer** state. + +State transition diagram for ANF-CMN at Endpoint A (part 2). + +**Figure 8/H.450.12 – SDL representation of ANF-CMN at Endpoint A (part 2)** + +![SDL diagram showing state transitions for ANF-CMN at Endpoint A. The diagram starts with a state 'CMN-Wait-Response' which branches into three message boxes: 'CMNRequest Response', 'CMNInform Request', and 'Message with CMNInform.inv'. The first message leads to 'Message with CMNRequest.res' which then leads to state 'CMN-Idle'. The second message leads to 'Message with CMNInform.inv' which then leads to state 'CMN-Wait-Response'. The third message leads to 'CMNInform Indication' which also leads to state 'CMN-Wait-Response'.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +``` +stateDiagram-v2 + [*] --> CMN-Wait-Response + CMN-Wait-Response --> CMNRequest_Response[CMNRequest Response] + CMN-Wait-Response --> CMNInform_Request[CMNInform Request] + CMN-Wait-Response --> Message_with_CMNInform_inv[Message with CMNInform.inv] + CMNRequest_Response --> Message_with_CMNRequest_res[Message with CMNRequest.res] + Message_with_CMNRequest_res --> CMN-Idle + CMNInform_Request --> Message_with_CMNInform_inv + Message_with_CMNInform_inv --> CMN-Wait-Response + Message_with_CMNInform_inv --> CMNInform_Indication[CMNInform Indication] + CMNInform_Indication --> CMN-Wait-Response +``` + +SDL diagram showing state transitions for ANF-CMN at Endpoint A. The diagram starts with a state 'CMN-Wait-Response' which branches into three message boxes: 'CMNRequest Response', 'CMNInform Request', and 'Message with CMNInform.inv'. The first message leads to 'Message with CMNRequest.res' which then leads to state 'CMN-Idle'. The second message leads to 'Message with CMNInform.inv' which then leads to state 'CMN-Wait-Response'. The third message leads to 'CMNInform Indication' which also leads to state 'CMN-Wait-Response'. + +**Figure 9/H.450.12 – SDL representation of ANF-CMN at Endpoint A (part 3)** + +![SDL diagram showing state transitions for ANF-CMN at Endpoint A. The diagram starts with a state 'CMN-Wait-Answer-Response' which branches into four message inputs: 'Message with CMNInform.inv', 'Message with CMNRequest.err', 'Message with CMNRequest.res', and 'Message with CMNRequest.rej'. Each message leads to a corresponding output message and a state transition. 'CMNInform.inv' leads to 'CMNRequest Response' output and 'CMNInform Indication' state transition, ending in 'CMN-Wait-Answer'. 'CMNRequest.err' leads to 'Timer T1 Expiry' output and 'Stop Timer T1 if running' state transition, ending in 'CMNRequest Confirm-Error' state transition. 'CMNRequest.res' leads to 'Basic Call Cleared' output and 'Stop Timer T1 if running' state transition, ending in 'CMNRequest Confirm-Success' state transition. 'CMNRequest.rej' leads to 'Stop Timer T1 if running' state transition, ending in 'CMNRequest Confirm-Reject' state transition. The three 'Confirm' state transitions lead to a common 'CMN-Wait-Response' state.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> CMN-Wait-Answer-Response + CMN-Wait-Answer-Response --> CMNRequest Response : Message with CMNInform.inv + CMN-Wait-Answer-Response --> Timer T1 Expiry : Message with CMNRequest.err + CMN-Wait-Answer-Response --> Basic Call Cleared : Message with CMNRequest.res + CMN-Wait-Answer-Response --> Message with CMNRequest.rej + CMNRequest Response --> CMNInform Indication + CMNInform Indication --> Message with CMNRequest.res + Message with CMNRequest.res --> CMN-Wait-Answer + Timer T1 Expiry --> Stop Timer T1 if running + Stop Timer T1 if running --> CMNRequest Confirm-Error + Basic Call Cleared --> Stop Timer T1 if running + Stop Timer T1 if running --> CMNRequest Confirm-Success + Message with CMNRequest.rej --> Stop Timer T1 if running + Stop Timer T1 if running --> CMNRequest Confirm-Reject + CMNRequest Confirm-Error --> CMN-Wait-Response + CMNRequest Confirm-Success --> CMN-Wait-Response + CMNRequest Confirm-Reject --> CMN-Wait-Response + +``` + +SDL diagram showing state transitions for ANF-CMN at Endpoint A. The diagram starts with a state 'CMN-Wait-Answer-Response' which branches into four message inputs: 'Message with CMNInform.inv', 'Message with CMNRequest.err', 'Message with CMNRequest.res', and 'Message with CMNRequest.rej'. Each message leads to a corresponding output message and a state transition. 'CMNInform.inv' leads to 'CMNRequest Response' output and 'CMNInform Indication' state transition, ending in 'CMN-Wait-Answer'. 'CMNRequest.err' leads to 'Timer T1 Expiry' output and 'Stop Timer T1 if running' state transition, ending in 'CMNRequest Confirm-Error' state transition. 'CMNRequest.res' leads to 'Basic Call Cleared' output and 'Stop Timer T1 if running' state transition, ending in 'CMNRequest Confirm-Success' state transition. 'CMNRequest.rej' leads to 'Stop Timer T1 if running' state transition, ending in 'CMNRequest Confirm-Reject' state transition. The three 'Confirm' state transitions lead to a common 'CMN-Wait-Response' state. + +**Figure 10/H.450.12 – SDL representation of ANF-CMN at Endpoint A (part 4)** + +## 13.2 Behaviour of the Endpoints using implicit application information exchange + +![SDL diagram showing the behavior of endpoints using implicit application information exchange. It starts from a CMN-Idle state and branches into five paths based on different request types. The first three paths lead back to CMN-Idle, while the last two lead to a CMN-Wait-Answer state after a timer T1 is started.](2bacc162a73d75c43a7f90715832bd13_img.jpg) + +The diagram illustrates the state transitions and message exchanges for ANF-CMN at Endpoint A. It begins at the **CMN-Idle** state (oval). From here, five different request messages can be sent, each leading to a specific response and subsequent state: + +- CMNInform Request** (trapezoid) leads to **Message with CMNInform.inv** (trapezoid), which returns to the **CMN-Idle** state. +- Message with CMNInform.inv** (trapezoid) leads to **CMNInform Indication** (trapezoid), which returns to the **CMN-Idle** state. +- Message with CMNRequest.inv** (trapezoid) leads to a **Get CMN** process (rectangle), which then leads to **Message with CMNRequest.res** (trapezoid), returning to the **CMN-Idle** state. +- CMNInform + CMNRequest Request** (trapezoid) leads to a sequence of two **Message with CMNInform.inv** (trapezoid) and **Message with CMNRequest.inv** (trapezoid) messages. A note indicates these may be sent in the same message. This sequence leads to a decision point: **T1 only started if CMNRequest.inv is sent in a FACILITY message**. If yes, it leads to **Start Timer T1, if applicable** (rectangle), which then leads to the **CMN-Wait-Answer** state (oval). If no, it returns to the **CMN-Idle** state. +- CMNRequest Request** (trapezoid) leads to **Message with CMNRequest.inv** (trapezoid), which leads to the **CMN-Wait-Answer** state (oval). + +SDL diagram showing the behavior of endpoints using implicit application information exchange. It starts from a CMN-Idle state and branches into five paths based on different request types. The first three paths lead back to CMN-Idle, while the last two lead to a CMN-Wait-Answer state after a timer T1 is started. + +Figure 11/H.450.12 – SDL representation of ANF-CMN at the Endpoint A (part 1) + +![State transition diagram for ANF-CMN at Endpoint A (part 2).](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +``` + +stateDiagram-v2 + [*] --> CMN-Wait-Answer + CMN-Wait-Answer --> CMNRequest.res + CMN-Wait-Answer --> CMNRequest.rej + CMN-Wait-Answer --> CMNRequest.err + CMN-Wait-Answer --> CMNRequest.inv + CMNRequest.res --> StopTimerT1_1[Stop Timer T1 if running] + StopTimerT1_1 --> CMNRequestConfirm-Success + CMNRequest.rej --> StopTimerT1_2[Stop Timer T1 if running] + StopTimerT1_2 --> CMNRequestConfirm-Reject + CMNRequest.err --> StopTimerT1_3[Stop Timer T1 if running] + StopTimerT1_3 --> CMNRequestConfirm-Error + CMNRequest.inv --> GetCMN[Get CMN] + GetCMN --> CMNRequest.res + CMNRequest.res --> CMN-Wait-Answer + CMNRequest.res --> CMNInform.inv + CMNInform.inv --> CMNInform.Indication + CMNInform.Indication --> CMN-Wait-Answer + TimerT1Expiry[Timer T1 Expiry] --> CMNRequestConfirm-Success + TimerT1Expiry --> CMNRequestConfirm-Reject + TimerT1Expiry --> CMNRequestConfirm-Error + BasicCallCleared[Basic Call Cleared] --> CMNRequestConfirm-Success + BasicCallCleared --> CMNRequestConfirm-Reject + BasicCallCleared --> CMNRequestConfirm-Error + BasicCallCleared --> CMN-Wait-Answer + BasicCallCleared --> CMN-Idle + +``` + +The diagram illustrates the state transitions for ANF-CMN at Endpoint A. It begins at the initial state, leading to **CMN-Wait-Answer**. From this state, four possible messages can be received: **Message with CMNRequest.res**, **Message with CMNRequest.rej**, **Message with CMNRequest.err**, and **Message with CMNRequest.inv**. The first three messages lead to a **Stop Timer T1 if running** action, which then leads to **CMNRequest Confirm-Success**, **CMNRequest Confirm-Reject**, and **CMNRequest Confirm-Error** respectively. These three confirmations lead to the **CMN-Idle** state. The **Message with CMNRequest.inv** leads to a **Get CMN** action, which then leads to **Message with CMNRequest.res**. This message leads to the **CMN-Wait-Answer** state and also to a **CMNInform Indication**, which then leads back to the **CMN-Wait-Answer** state. Additionally, **Timer T1 Expiry** and **Basic Call Cleared** events lead to the same three confirmations (**CMNRequest Confirm-Success**, **CMNRequest Confirm-Reject**, and **CMNRequest Confirm-Error**), which lead to the **CMN-Idle** state. The **Basic Call Cleared** event also leads directly to the **CMN-Wait-Answer** state. + +State transition diagram for ANF-CMN at Endpoint A (part 2). + +**Figure 12/H.450.12 – SDL representation of ANF-CMN at Endpoint A (part 2)** + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.450.6-199905-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.450.6-199905-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9625d6ac2a0b8ec6ecdfc8f8e890bd844014ff08 --- /dev/null +++ b/marked/H/T-REC-H.450.6-199905-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bd90c83bb6d4a3aaa4dd03f79a9aa60fc9194182558c3aa8445ca14c21b9f98 +size 7422 diff --git a/marked/H/T-REC-H.450.6-199905-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/H/T-REC-H.450.6-199905-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9824092a51706da74593acf3d6a3400500b3b1d3 --- /dev/null +++ b/marked/H/T-REC-H.450.6-199905-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5782e840cb4ba443fbd7ebd37f851b134bc73846327766521ec23473d3a45a0e +size 44077 diff --git a/marked/H/T-REC-H.450.6-199905-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/H/T-REC-H.450.6-199905-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fac99a39a0bfbf99f8d37dd38ff9ea18bb9bf6e --- /dev/null +++ b/marked/H/T-REC-H.450.6-199905-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd4e0c0fcebed3bf9f8a6d72db8c2fc3fb62ef157b80998f5d016eef50a3d26d +size 52369 diff --git a/marked/H/T-REC-H.450.6-199905-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/H/T-REC-H.450.6-199905-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aba2590162f0f0266ae45787ea3d7c6c798ad4ca --- /dev/null +++ b/marked/H/T-REC-H.450.6-199905-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a9f3f76ec2a087acd06e39e670120671d14fbc97345a4e2a751841507ea3a3f +size 39475 diff --git a/marked/H/T-REC-H.450.6-199905-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/H/T-REC-H.450.6-199905-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be6868c0bf031bb8ccd037dce977f470361fcdc3 --- /dev/null +++ b/marked/H/T-REC-H.450.6-199905-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2d4c62886e375a31a6aa0817998be87c20feef151bd6af27ab68adedab31331 +size 22195 diff --git a/marked/H/T-REC-H.450.6-199905-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/H/T-REC-H.450.6-199905-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b31d7a313f1a3462f510fad821ca38d07ae2defa --- /dev/null +++ b/marked/H/T-REC-H.450.6-199905-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64d463c783b55a9521cdcccdcfd2050c5530b2f8b7dee97cb65ee14bbd9df856 +size 31477 diff --git a/marked/H/T-REC-H.450.6-199905-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.450.6-199905-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..564271a26e31d8f0a72d612c99a1ee978a855a03 --- /dev/null +++ b/marked/H/T-REC-H.450.6-199905-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52d5f4ca20cfd3429ddcad9a36347102192f375ea226271db40fda6e94da271e +size 56234 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ad98c6e45b6c52f074f0054407ca88a640d8f1d --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58019f38be268f19eaa80c6d56d0f6b39d5741569a8f3ccc04117fa95d9c6465 +size 4016 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..deea89d3902d4b84464b4696f7a2df615327e68a --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc9b1e5cbe10eb2bc669e4d5bf2dd3099ede1708c272e4318dfd2365c9c37553 +size 73509 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ee6c29d119ff108b737d627d1c1a71a4a0d3840 --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e12d22d296585141bb48213a42eacb6123b65c8e9486e5a8f14c568ceef8b84 +size 30776 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c3fbc8faf4a1a300b00c3835c638e7776fbcb5c --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dc4c4bf9df09c88913b1621e434096d2380a362bc2be68417314e061d7486e8 +size 72885 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dc22c63a71627bd3a0c638c27a06c2a5a379757 --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6dbe2e4c985b9736c21ea558be15e52867a913bad133cd80292d7c6f20a9092 +size 16688 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b43e275275958a8fe445e12a61b3539aea843a7 --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9f3cac0d388aa6b32532b1fac1066609501ddfe9c065b5ea4a49462af072e5e +size 80078 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..509d62a572b9f01d40215479075164db56a3a5e0 --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59bfaa79ec26fe9ddb2c682614e848d4f60c82345520ed342d19be37f574ab87 +size 72899 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed7cf0ab2e8523f82f8c0df61955c27d096ec508 --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a42d8ace7e834ccc974f515691c648b366e416070d9301c52938c595438c3022 +size 40755 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98accb75b9af9a4407b8662ed8796f3999567dd7 --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edc022d63b2e6663be3aa2b5071c615e64b6b6fdb1e631227212a4761d08138f +size 17548 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..103f2e3db0d87a7676b9794fdd10a74f95d5ec1d --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44d9c19a5d5a550b87f38ec092c85d0d0bd6b09cbb956de4f99b4b3fe89477d7 +size 24203 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/H/T-REC-H.450.7-201303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0833cd3e56fb730819f17429281dc50dadd9991 --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f020d3159d1566c847535e6dde9498432aa084540133d8f48a9b41811efc76b2 +size 23803 diff --git a/marked/H/T-REC-H.450.7-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.450.7-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..25a74b9c345208b1d960034603a39e5bb44d06c4 --- /dev/null +++ b/marked/H/T-REC-H.450.7-201303-I_PDF-E/raw.md @@ -0,0 +1,1168 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.450.7** + +(03/2013) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Supplementary +services for multimedia + +# --- **Message waiting indication supplementary service for ITU-T H.323 systems** + +Recommendation ITU-T H.450.7 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.450.7 + +# Message waiting indication supplementary service for ITU-T H.323 systems + +# Summary + +Recommendation ITU-T H.450.7 specifies the procedures and signalling protocol for the supplementary service for message waiting indication (SS-MWI) in ITU-T H.323 (packet-based multimedia communication systems) networks. + +The SS-MWI enables a served user to be sent a message waiting indication (MWI) and also enables this MWI to be cancelled. The served user may also be permitted to interrogate a message centre for any MWIs. + +The procedures and the signalling protocol of this Recommendation are derived from the SS-MWI as specified in ISO/IEC 15505 and ISO/IEC 15506. + +This Recommendation makes use of the "Generic functional protocol for the support of supplementary services in ITU-T H.323 systems" as defined in Recommendation ITU-T H.450.1. + +This revision introduces editorial and technical changes, clarifications and corrections, in particular those indicated in the Implementers' Guide for Recommendations of the ITU-T H.323 system (2011). + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.450.7 | 1999-05-27 | 16 | +| 2.0 | ITU-T H.450.7 | 2013-03-16 | 16 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-----|--------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 1 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Introduction ..... | 2 | +| 6 | SS-MWI service description..... | 3 | +| 6.1 | Description ..... | 3 | +| 6.2 | Normal procedures ..... | 3 | +| 6.3 | Exceptional procedures ..... | 4 | +| 7 | Signalling protocol for the support of SS-MWI ..... | 4 | +| 7.1 | SS-MWI coding requirements ..... | 4 | +| 7.2 | Definitions of the SS-MWI state ..... | 8 | +| 7.3 | Timers..... | 8 | +| 7.4 | SS-MWI signalling procedures ..... | 8 | +| 7.5 | Gatekeeper interactions ..... | 14 | +| 7.6 | Interactions between SS-MWI and other supplementary services ..... | 14 | +| 7.7 | SS-MWI security considerations ..... | 15 | +| 8 | Signalling flows for SS-MWI..... | 15 | +| 8.1 | Example message sequence for SS-MWI activation..... | 15 | +| 8.2 | Example message sequence for SS-MWI deactivation ..... | 16 | +| 8.3 | Example message sequence for SS-MWI interrogation..... | 17 | +| 9 | Specification and description language (SDL) diagrams ..... | 17 | +| 9.1 | SDL representation of SS-MWI at the message centre endpoint ..... | 17 | +| 9.2 | SDL representation of SS-MWI at the served user ..... | 21 | +| | Bibliography..... | 23 | + +, + + + +# Recommendation ITU-T H.450.7 + +# Message waiting indication supplementary service for ITU-T H.323 systems + +# 1 Scope + +This Recommendation describes the supplementary service for message waiting indication (SS-MWI), which is applicable to ITU-T H.323 multimedia endpoints. The SS-MWI is based on the equivalent supplementary service for the private integrated services network (PISN) as specified in [ISO/IEC 15505] and [ISO/IEC 15506]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.225.0] Recommendation ITU-T H.225.0 (2009), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- [ITU-T H.235.5] Recommendation ITU-T H.235.5 (2005), *ITU-T H.323 security: Framework for secure authentication in RAS using weak shared secrets*. +- [ITU-T H.245] Recommendation ITU-T H.245 (2011), *Control protocol for multimedia communication*. +- [ITU-T H.323] Recommendation ITU-T H.323 (2009), *Packet-based multimedia communications systems*. +- [ITU-T H.450.1] Recommendation ITU-T H.450.1 (2011), *Generic functional protocol for the support of supplementary services in ITU-T H.323 systems*. +- [ISO/IEC 15505] ISO/IEC 15505:1997, *Information technology, Telecommunications and information exchange between systems – Private Integrated Services Network (PISN) – Specification, functional model and information flows – Message waiting indication supplementary service*. +- [ISO/IEC 15506] ISO/IEC 15506:1997, *Information technology, Telecommunications and information exchange between systems – Private Integrated Services Network (PISN) – Inter-exchange signalling protocol – Message waiting indication supplementary service*. + +# 3 Terms and definitions + +This Recommendation defines the following terms: + +**3.1 message centre:** The entity that requests activation or deactivation of the message waiting indication (MWI). + +When a callback request is issued using the mechanism provided by the MWI, the originating user acts as a message centre. + +**3.2 message centre endpoint:** The endpoint that handles the ITU-T H.323 signalling on behalf of the message centre. For example, this may be the message centre itself if it is directly attached to the ITU-T H.323 network, it may be the originating user's endpoint, or it may be a Gateway. + +**3.3 message waiting indication:** An indication to the served user when messages are waiting for the served user. + +**3.4 served user:** The user to whom the message waiting indication (MWI) is sent when initiated by the message centre. + +NOTE – The indication may be a lamp, special tone, display, etc. This is outside the scope of this Recommendation. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|----------------------------------------------------------------------| +| APDU | Application Protocol Data Unit | +| ASN.1 | Abstract Syntax Notation One | +| GK | Gatekeeper | +| MWI | Message Waiting Indication | +| NFE | Network Facility Extension | +| PISN | Private Integrated Services Network | +| RAS | Registration, Admission and Status | +| SDL | Specification and Description Language | +| SS-MWI | Supplementary Service Message Waiting Indication | +| UTC | Coordinated Universal Time (also known as Greenwich Mean Time (GMT)) | + +# **5 Introduction** + +The message waiting indication supplementary service (SS-MWI) provides a general purpose mechanism by which a user can be advised that messages intended for that user are available. A variety of message types are supported, such as voice mail, fax and teletext. + +In one of its simplest forms, when a message is left for a user, a message centre sends a notification to the served user, where a message waiting lamp is lit. + +Additional information provided by the notification mechanism allows the served user to know the number of messages that are waiting, the types of messages, the subjects of the messages, and the priority of the highest priority message. + +In an ITU-T H.323 environment, where endpoints may commonly be directly associated with general purpose computers, applications such as automated message retrieval may be envisioned. + +SS-MWI also provides a mechanism whereby it is possible for an endpoint to issue a callback request to the served user. + +The interrogation mechanism provided by the SS-MWI allows a served user to query message centres known to it, or a known Gatekeeper (GK)/proxy for the MWI activations currently applied to it. A typical usage of this mechanism is by a served user to recreate its MWI status when the endpoint is returned to service, as the status may have changed while it was out of service. + +# **6 SS-MWI service description** + +## **6.1 Description** + +The SS-MWI enables a served user to be sent an MWI and also enables this MWI to be cancelled. An MWI activation may also be used to send a callback request to the served user. + +This service also includes an option to interrogate the MWI stored against the served user. + +A served user can receive separate MWIs for each of the basic services for which there is a message waiting. + +NOTE – A basic service for which there is a message waiting would usually be the basic service used to retrieve that message. + +## **6.2 Normal procedures** + +### **6.2.1 Activation, deactivation and interrogation** + +To activate SS-MWI, the message centre shall supply the endpoint address and the basic service for which there is a message waiting and may, as an implementation option, add any combination of the following pieces of information: the identity of the message centre; the number of messages waiting for the served user for that basic service; the address of the user that left a message; the time when a message was left; and the priority of the highest priority message waiting for that basic service. After activation, the SS-MWI may be activated again whenever the number of waiting messages for a specific basic service changes. + +It is also possible to use SS-MWI activation to request that the served user initiate a call (callback) to a specified endpoint. + +To deactivate the SS-MWI, the message centre shall supply the endpoint address and the basic service for which there are no longer any messages waiting. + +As a result of activation, an MWI shall be sent to the served user. The MWI may include information on the messages waiting, if provided by the message centre. As a result of deactivation, the MWI at the served user, for the basic service concerned, shall be cancelled. + +When the message centre activates or deactivates SS-MWI at the served user, it shall be provided with an indication of acceptance. + +When the served user interrogates the SS-MWI for a particular basic service, the message centre shall provide the served user with an indication of whether the SS-MWI is activated for that basic service and may add, as an implementation option, any of the following information: + +- the identity of the message centre; +- the number of messages waiting; +- the address of the user that left a message; +- the time when a message was left; +- the priority of the highest priority message waiting. + +When the served user interrogates the SS-MWI for all basic services, the message centre shall provide the served user with a list of basic services for which the SS-MWI is active and, as an implementation option, for each basic service, any of the additional information listed above. + +### **6.2.2 Invocation and operation** + +Not applicable. + +## 6.3 Exceptional procedures + +### 6.3.1 Activation, deactivation and interrogation + +If the served user cannot accept SS-MWI activation or deactivation, then the message centre shall be informed and may also be given the reason. If the message centre cannot accept interrogation, then the served user shall be informed and may also be given a reason. + +### 6.3.2 Invocation and operation + +None. + +# 7 Signalling protocol for the support of SS-MWI + +## 7.1 SS-MWI coding requirements + +### 7.1.1 ITU-T H.450.1 supplementary service APDU + +The application protocol data units (APDUs) of MWI operations are transported within user-to-user information elements in call control and FACILITY messages as defined in [ITU-T H.450.1]. The MWI operations are described in clause 7.1.2, Operations. + +When conveying the Invoke APDU of the operations defined in clause 7.1.2, Operations, the destinationEntity data element of the NFE shall contain the value "endpoint". + +When conveying the Invoke APDU of operations mwiActivate, mwiDeactivate, and mwiInterrogate, the interpretation APDU shall be omitted or shall contain the value rejectAnyUnrecognizedInvokePdu. + +### 7.1.2 Operations + +The following operations defined in Abstract Syntax Notation One (ASN.1) shall apply: + +``` +Message-Waiting-Indication-Operations +{itu-t recommendation h 450 7 version1(0) message-waiting-operations(0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS OPERATION, ERROR FROM Remote-Operations-Information-Objects + {joint-iso-itu-t remote-operations(4) informationObjects(5) +version1(0)} + EXTENSION, Extension{} FROM Manufacturer-specific-service- +extension-definition + {itu-t recommendation h 450 1 version1(0) msi-definition(18)} + + userNotSubscribed, invalidServedUserNumber, +basicServiceNotProvided + FROM H4501-General-Error-List + {itu-t recommendation h 450 1 version1(0) general-error- +list(1)} + + EndpointAddress FROM Addressing-Data-Elements + {itu-t recommendation h 450 1 version1(0) addressing-data- +elements(9)} + + MixedExtension FROM Call-Hold-Operations + {itu-t recommendation h 450 4 version1(0) call-hold- +operations(0)}; + +H323-MWI-Operations OPERATION ::= {mwiActivate | mwiDeactivate | +mwiInterrogate } +``` + +``` + +mwiActivate OPERATION ::= +{ + ARGUMENT MWIActivateArg + RESULT DummyRes + ERRORS { userNotSubscribed | +invalidServedUserNumber | + basicServiceNotProvided | undefined } + CODE local: 80 +} + +mwiDeactivate OPERATION ::= +{ + ARGUMENT MWIDeactivateArg + RESULT DummyRes + ERRORS { userNotSubscribed | +invalidServedUserNumber | + basicServiceNotProvided | undefined } + CODE local: 81 +} + +mwiInterrogate OPERATION ::= +{ + ARGUMENT MWIInterrogateArg + RESULT MWIInterrogateRes + ERRORS { userNotSubscribed | +invalidServedUserNumber | + notActivated | invalidMsgCentreId | undefined } + CODE local: 82 +} + +MWIActivateArg ::= SEQUENCE +{ + servedUserNr EndpointAddress, + basicService BasicService, + msgCentreId MsgCentreId OPTIONAL, + nbOfMessages NbOfMessages OPTIONAL, + originatingNr EndpointAddress OPTIONAL, + timestamp Timestamp OPTIONAL, + priority INTEGER (0..9) OPTIONAL, + -- the value 0 means the highest priority and 9 the +lowest + extensionArg SEQUENCE SIZE(0..255) OF MixedExtension +OPTIONAL, + ... +} + +DummyRes ::= SEQUENCE SIZE(0..255) OF MixedExtension + +MWIDeactivateArg ::= SEQUENCE +{ + servedUserNr EndpointAddress, + basicService BasicService, + msgCentreId MsgCentreId OPTIONAL, + callbackReq BOOLEAN OPTIONAL, + extensionArg SEQUENCE SIZE(0..255) OF MixedExtension +OPTIONAL, + ... +} + +MWIInterrogateArg ::= SEQUENCE +{ + servedUserNr EndpointAddress, + basicService BasicService, +} + +``` + +``` + + msgCentreId MsgCentreId OPTIONAL, + callbackReq BOOLEAN OPTIONAL, + extensionArg SEQUENCE SIZE(0..255) OF MixedExtension +OPTIONAL, + + } + +MWIInterrogateRes ::= SEQUENCE SIZE(1..64) OF MWIInterrogateResElt + +MWIInterrogateResElt ::= SEQUENCE +{ + basicService BasicService, + msgCentreId MsgCentreId OPTIONAL, + nbOfMessages NbOfMessages OPTIONAL, + originatingNr EndpointAddress OPTIONAL, + timestamp TimeStamp OPTIONAL, + priority INTEGER (0..9) OPTIONAL, + -- the value 0 means the highest priority and 9 the +lowest + extensionArg SEQUENCE SIZE(0..255) OF MixedExtension +OPTIONAL, + +} + +MsgCentreId ::= CHOICE +{ + -- only partyNumber provides a callable identification + integer INTEGER (0..65535), + partyNumber EndpointAddress, + numericString NumericString (SIZE (1..10)) +} + +NbOfMessages ::= INTEGER (0..65535) + +TimeStamp ::= GeneralizedTime (SIZE (12..19)) +-- a VisibleString representation of date and time +following ISO 8601 +-- containing: +-- - the (local) date in 8 digits (YYYYMMDD), +-- - followed by (local) time of day in 4 or 6 digits +[HHMM(SS)], +-- -optionally followed by the letter "Z" or by a +local time differential +-- from UTC time in 5 digits ("+"HHMM or "-"HHMM); +-- Examples: +-- 1) 19970621194530, meaning 21 June 1997, 19:45:30; +-- 2) 19970621194530Z, meaning the same as 1); +-- 3) 19970621194530-0500, meaning the same as 1), +-- 5 hours retarded in relation to UTC time + +undefined ERROR ::= +{ + PARAMETER SEQUENCE SIZE(0..255) OF MixedExtension + OPTIONAL TRUE + CODE local: 2002 +} + +invalidMsgCentreId ERROR ::= +{ + -- returned by a Message Centre endpoint when an +unknown Message + -- Centre Identifier is specified in a +mwiInterrogate invoke + CODE local: 1018 +} + +``` + +``` + +BasicService ::= ENUMERATED +{ + -- MWI Services: + -- for compatibility among vendors, speech is + recommended for voice mail + -- indications + allServices (0), + speech (1), + unrestrictedDigitalInformation (2), + audio3100Hz (3), + telephony (32), + teletex (33), + telefaxGroup4Class1 (34), + videotexSyntaxBased (35), + videotelephony (36), + telefaxGroup2-3 (37), + reservedNotUsed1 (38), + reservedNotUsed2 (39), + reservedNotUsed3 (40), + reservedNotUsed4 (41), + reservedNotUsed5 (42), + -- + -- MWI Service Classes: + email (51), + video (52), + fileTransfer (53), + shortMessageService (54), + speechAndVideo (55), + speechAndFax (56), + speechAndEmail (57), + videoAndFax (58), + videoAndEmail (59), + faxAndEmail (60), + speechVideoAndFax (61), + speechVideoAndEmail (62), + speechFaxAndEmail (63), + videoFaxAndEmail (64), + speechVideoFaxAndEmail (65), + multimediaUnknown (66), + serviceUnknown (67), + -- + -- Reserved for future additions: + futureReserve1 (68), + futureReserve2 (69), + futureReserve3 (70), + futureReserve4 (71), + futureReserve5 (72), + futureReserve6 (73), + futureReserve7 (74), + futureReserve8 (75) +} + +notActivated ERROR ::= +{ + CODE local: 31 +} + +END -- of Message-Waiting-Indication-Operations + +``` + +## 7.2 Definitions of the SS-MWI state + +### 7.2.1 States at the message centre endpoint + +The procedures for the message centre endpoint are written in terms of the following conceptual states existing within the SS-MWI control entity in that endpoint, in association with an activation or deactivation request from the message centre entity. + +#### 7.2.1.1 State MWI-MC-Idle + +Activation/deactivation is not in progress. The message centre endpoint is ready for receipt of a **mwInterrogate** Invoke APDU. + +#### 7.2.1.2 State MWI-MC-Wait + +A **mwActivate** or **mwDeactivate** Invoke APDU has been sent. The message centre endpoint is waiting for a response. + +### 7.2.2 States at the served user + +The procedures for the served user are written in terms of the following conceptual states existing within the SS-MWI control entity in that endpoint, in association with a particular call-independent signalling connection for the served user. + +#### 7.2.2.1 State MWI-Ser-Idle + +The served user is ready for receipt of a **mwActivate** or **mwDeactivate** Invoke APDU. + +#### 7.2.2.2 State MWI-Ser-Wait + +A **mwInterrogate** Invoke APDU has been sent. The served user is waiting for a response. + +## 7.3 Timers + +### 7.3.1 Timer T1 + +Timer T1 shall operate at the message centre endpoint during state MWI-MC-Wait. Its purpose is to protect against an absence of a response to the **mwActivate** or **mwDeactivate** Invoke APDU. + +Timer T1 shall have a value of not less than 15 seconds. + +### 7.3.2 Timer T2 + +Timer T2 shall operate at the served user during state MWI-Ser-Wait. Its purpose is to protect against an absence of a response to the **mwInterrogate** Invoke APDU. + +Timer T2 shall have a value of not less than 15 seconds. + +## 7.4 SS-MWI signalling procedures + +The SDL representation of procedures at the message centre endpoint is described in clause 9.1. + +The SDL representation of procedures at the served user is described in clause 9.2. + +### 7.4.1 Activation/deactivation + +#### 7.4.1.1 Actions at the message centre endpoint + +##### 7.4.1.1.1 Normal procedures + +On receipt of an activation/deactivation request from the message centre entity, the message centre endpoint shall send a **mwActivate/mwDeactivate** Invoke APDU to the served user in a SETUP message of a new call-independent signalling connection or in a FACILITY message of an already established call-independent signalling connection. If a new call-independent signalling connection is initiated, it shall be established in accordance with the procedures specified in clause 6.2 of + +[ITU-T H.450.1]. Upon sending of the **mwActivate/mwDeactivate** Invoke APDU, the message centre endpoint shall start timer T1 and enter the MWI-MC-Wait state. The **mwActivate/mwDeactivate** Invoke APDU shall contain the endpoint address of the served user and the basic service for which the activation/deactivation applies. + +A message centre may combine several **mwActivate** Invoke APDUs and/or **mwDeactivate** Invoke APDUs in a single ITU-T H.450.1 supplementary service APDU. + +The message centre endpoint may optionally include in the **mwActivate** Invoke APDU any of the following information: + +- an identifier of the message centre, in the element msgCentreId; +- the number of messages for the served user in the element nbOfMessages; +- the endpoint address of the user that has left a message in the element originatingNr; +- the time when a message was left in the element timestamp; +- the priority of the highest priority message for the served user in the element priority. + +If a **mwActivate** Invoke APDU is being used to signal a callback request to the served user, then the nbOfMessages element shall be set to zero and the msgCentreId element shall be set to the Endpoint Address destination for the callback. + +In state MWI-MC-Wait, on receipt of a **mwActivate** or **mwDeactivate** Return Result APDU, the message centre endpoint shall stop timer T1 and enter state MWI-MC-Idle. + +NOTE – The message centre endpoint should indicate acceptance to the message centre entity. + +The message centre endpoint is responsible for clearing the call-independent signalling connection towards the served user. This may occur on receipt of a **mwActivate** or **mwDeactivate** Return Result APDU. Alternatively, the signalling connection may be retained for other applications, if appropriate. + +##### 7.4.1.1.2 Exceptional procedures + +In the state MWI-MC-Wait, on receipt of a **mwActivate/mwDeactivate** Return Error APDU from the served user, the message centre endpoint shall stop timer T1 and enter state MWI-MC-Idle. + +If timer T1 expires, the message centre endpoint shall enter state MWI-MC-Idle. + +NOTE – The message centre endpoint should indicate rejection to the message centre entity. + +#### 7.4.1.2 Actions at the served user + +##### 7.4.1.2.1 Normal procedures + +On receipt of a **mwActivate/mwDeactivate** Invoke APDU using the transfer mode of a call-independent signalling connection (as specified in clause 7.2 of [ITU-T H.450.1]) and if activation/deactivation is possible, the served user shall activate/deactivate the SS-MWI and send back a **mwActivate/mwDeactivate** Return Result APDU to the message centre endpoint and remain in MWI-Ser-Idle state. + +NOTE – The served user shall consider an **mwActivate** Invoke APDU with the nbOfMessages element equal to zero as a request to call back the endpoint specified by the msgCentreId element. + +When used for callback, the basic service specified in the activation would usually be the basic service used for the resultant call. For ITU-T H.323, this would normally be allServices(0) which allows media stream properties to be determined using ITU-T H.245. + +If the optional callbackReq element is not present in the **mwDeactivate** Invoke APDU, the served user shall deactivate all matching SS-MWI activations. If the callbackReq element is present, only matching SS-MWI activations for callbacks shall be deactivated if the callbackReq value is TRUE, + +and only matching SS-MWI activations which are not for callbacks shall be deactivated if the callbackReq value is FALSE. + +##### 7.4.1.2.2 Exceptional procedures + +On receipt of a **mwActivate/mwDeactivate** Invoke APDU and if the activation/deactivation request cannot be accepted, the served user shall send a **mwActivate/mwDeactivate** Return Error APDU with an appropriate error value or a Reject APDU and remain in state MWI-Ser-Idle. + +### 7.4.2 Interrogation + +#### 7.4.2.1 Actions at the message centre endpoint + +##### 7.4.2.1.1 Normal procedures + +In state MWI-MC-Idle, on receipt of a **mwInterrogate** Invoke APDU using the transfer mode of a call-independent signalling connection (as specified in clause 7.2 of [ITU-T H.450.1]) and if the interrogation is possible and the message centre identifier, if received, is correct, the message centre endpoint shall get the status of the SS-MWI, send back a **mwInterrogate** Return Result APDU to the served user and stay in state MWI-MC-Idle. The information that may be included in the Return Result APDU is analogous to the information sent in the **mwActivate** Invoke APDU as described in clause 7.4.2.2.1, Normal procedures. + +If the basicService value specified in the **mwInterrogate** Invoke APDU is allServices, the message centre shall provide the served user with a list of basic services for which SS-MWI is active and, as an implementation option, for each basic service, any of the optional information which is analogous to the information sent in the **mwActivate** Invoke APDU. + +If the optional callbackReq element is not present in the **mwInterrogate** Invoke APDU, the message centre shall provide information for all matching SS-MWI activations. If the callbackReq element is present, only information for matching SS-MWI activations which are for callbacks shall be provided if the callbackReq value is TRUE, and only information for matching SS-MWI activations which are not for callbacks shall be provided if the callbackReq value is FALSE. + +##### 7.4.2.1.2 Exceptional procedures + +On receipt of a **mwInterrogate** Invoke APDU using the transfer mode of a call-independent signalling connection (as specified in clause 7.2 of [ITU-T H.450.1]) and if interrogation is not possible, or an incorrect message centre identifier is included, the message centre endpoint shall send back a **mwInterrogate** Return Error APDU to the served user and stay in state MWI-MC-Idle. + +#### 7.4.2.2 Actions at the served user + +##### 7.4.2.2.1 Normal procedures + +On receipt of an interrogation request from the user, the served user shall send a **mwInterrogate** Invoke APDU to the message centre endpoint using the transfer mode of a call-independent signalling connection (as specified in clause 7.2 of [ITU-T H.450.1]). The served user shall start timer T2 and enter MWI-Ser-Wait state. The **mwInterrogate** Invoke APDU shall contain the endpoint address of the served user, the basic service for which the interrogation applies, and optionally the message centre identifier. + +In state MWI-Ser-Wait, on receipt of a **mwInterrogate** Return Result APDU, the served user shall stop timer T2, and enter state MWI-Ser-Idle. + +NOTE 1 – The served user should indicate the result to the user. + +NOTE 2 – The served user shall consider an MWIInterrogateResElt in an **mwInterrogate** Return Result APDU with nbOfMessages equal to zero as a request to call back the endpoint specified by the msgCentreId. + +The served user is responsible for clearing the call-independent signalling connection towards the message centre endpoint. This may occur on receipt of a **mwIInterrogate** Return Result APDU. Alternatively, the signalling connection may be retained for other applications, if appropriate. + +##### 7.4.2.2.2 Exceptional procedures + +In state MWI-Ser-Wait, on receipt of a **mwIInterrogate** Return Error APDU from the message centre endpoint, the served user shall stop timer T2, and enter state MWI-Ser-Idle. + +If timer T2 expires, the served user shall enter state MWI-Ser-Idle. + +NOTE – The served user should indicate rejection to the user. + +The served user is responsible for clearing the call-independent signalling towards the message centre endpoint. This may occur on receipt of a **mwIInterrogate** Return Error APDU, receipt of a Reject APDU, or on expiry of timer T2. Alternatively, the signalling connection may be retained for other applications, if appropriate. + +### 7.4.3 Primitives + +#### 7.4.3.1 Message centre primitives + +See Table 1. + +**Table 1 – Message centre primitives** + +| Generic Name | Type | | | | +|----------------|-------------|-------------|-------------|-------------| +| | request | indication | response | confirm | +| MWIActivate | PARAMETERS | Not defined | Not defined | – | +| MWIDeactivate | PARAMETERS | Not defined | Not defined | – | +| MWIInterrogate | Not defined | PARAMETERS | PARAMETERS | Not defined | + +NOTE – "–" means no parameters (manufacturer specific parameters may apply). + +#### 7.4.3.2 Primitive definitions + +The definition of these primitives is as follows: + +- The MWIActivate.request primitive is used to activate SS-MWI at a served user. +- The MWIActivate.confirm primitive reports successful or unsuccessful SS-MWI activation at the served user. +- The MWIDeactivate.request primitive is used to deactivate SS-MWI at a served user. +- The MWIDeactivate.confirm primitive reports successful or unsuccessful SS-MWI deactivation at the served user. +- The MWIInterrogate.indication primitive indicates that a served user is querying its SS-MWI status. +- The MWIInterrogate.response primitive is used to convey SS-MWI status in an MWIInterrogate Return Result APDU, or an MWIInterrogate Return Error APDU, to the served user. + +#### 7.4.3.3 Parameter definitions + +##### MWIActivate.request parameters + +- servedUserNr: endpoint address of the served user. +- basicService: service for which the activation applies. +- msgCentreId: identity of the message centre (optional). + +- nbOfMessages: the number of message for the served user (optional). +- originatingNr: endpoint address of user that left a message (optional). +- timestamp: time when a message was left (optional). +- priority: priority of the highest priority message for the served user (optional). + +##### **MWIActivate.confirm (ack and rej)** + +- (rej) userNotSubscribed. +- (rej) invalidServedUserNumber. +- (rej) basicServiceNotProvided. +- (rej) undefined. + +##### **MWIDeactivate.request parameters** + +- servedUserNr: endpoint address of the served user. +- basicService: service for which the deactivation applies. +- msgCentreId: identity of the message centre (optional). +- callbackReq: limit deactivations to callback requests (optional). + +##### **MWIDeactivate.confirm (ack and rej)** + +- (rej) userNotSubscribed. +- (rej) invalidServedUserNumber. +- (rej) basicServiceNotProvided. +- (rej) undefined. + +##### **MWIInterrogate.indication parameters** + +- servedUserNr: endpoint address of the served user. +- basicService: service for which the served user is querying the MWI status. +- msgCentreId: identity of the message centre (optional). +- callbackReq: limit results to callback requests (optional). + +##### **MWIInterrogate.response (ack and rej) parameters** + +- (ack) MWIInterrogateRes: the served user's Message Waiting status; if basicService in the MWIInterrogate.ind was "allServices", the message centre shall provide a list of all basic services for which SS-MWI is active for the served user. +- (rej) userNotSubscribed. +- (rej) invalidServedUserNumber. +- (rej) notActivated. +- (rej) invalidMsgCentreId. +- (rej) undefined. + +#### **7.4.3.4 Served user primitives** + +See Table 2. + +**Table 2 – Served user primitives** + +| Generic Name | Type | | | | +|------------------------------------------------------------------------------|-------------|-------------|-------------|-------------| +| | request | indication | response | confirm | +| MWIActivate | Not defined | PARAMETERS | – | Not defined | +| MWIDeactivate | Not defined | PARAMETERS | – | Not defined | +| MWIInterrogate | PARAMETERS | Not defined | Not defined | PARAMETERS | +| NOTE – "–" means no parameters (manufacturer specific parameters may apply). | | | | | + +#### 7.4.3.5 Primitive definitions + +The definition of these primitives is as follows: + +- a) The MWIActivate.indication primitive signals a request from a message centre to activate SS-MWI. +- b) The MWIActivate.response (ack or rej) primitive acknowledges or rejects an SS-MWI activation by the message centre. +- c) The MWIDeactivate.indication primitive signals a request from a message centre to deactivate SS-MWI. +- d) The MWIDeactivate.response (ack or rej) primitive acknowledges or rejects an SS-MWI deactivation by the message centre. +- e) The MWIInterrogate.request primitive is used to obtain SS-MWI status from a message centre. +- f) The MWIInterrogate.confirm primitive is used to convey SS-MWI status information from the message centre. + +#### 7.4.3.6 Parameter definitions + +##### MWIActivate.indication parameters + +- servedUserNr: endpoint address of the served user. +- basicService: service for which the activation applies. +- msgCentreId: identity of the message centre (optional). +- nbOfMessages: the number of message for the served user (optional). +- originatingNr: endpoint address of user that left a message (optional). +- timestamp: time when a message was left (optional). +- priority: priority of the highest priority message for the served user (optional). + +##### MWIActivate.response (ack and rej) + +- (rej) userNotSubscribed. +- (rej) invalidServedUserNumber. +- (rej) basicServiceNotProvided. +- (rej) undefined. + +##### MWIDeactivate.indication parameters + +- servedUserNr: endpoint address of the served user. +- basicService: service for which the deactivation applies. +- msgCentreId: identity of the message centre (optional). +- callbackReq: limit deactivations to callback requests (optional). + +##### **MWIDeactivate.response (ack and rej)** + +- (rej) userNotSubscribed. +- (rej) invalidServedUserNumber. +- (rej) basicServiceNotProvided. +- (rej) undefined. + +##### **MWIInterrogate.request parameters** + +- servedUserNr: endpoint address of the served user. +- basicService: service for which the served user is querying the MWI status. +- msgCentreId: identity of the message centre (optional). +- callbackReq: limit results to callback requests (optional). + +##### **MWIInterrogate.confirm (ack and rej) parameters** + +- (ack) MWIInterrogateRes: the served user's Message Waiting status (see clause 7.4.3, Primitives). +- (rej) userNotSubscribed. +- (rej) invalidServedUserNumber. +- (rej) notActivated. +- (rej) invalidMsgCentreId. +- (rej) undefined. + +## **7.5 Gatekeeper interactions** + +A gatekeeper (GK) should transparently transport **mwActivate** and **mwDeactivate** Invoke APDUs to the served endpoint. However, a GK or proxy1 may act as a served user for **mwActivate** and **mwDeactivate** Invoke APDUs, for example storing callback requests while the served endpoint is out of service. In such cases, the served endpoint may update its MWI information in a variety of ways: + +- The endpoint may send a **mwInterrogate** Invoke APDU to the GK or its proxy. In this case, the msgCentreId in the **mwInterrogate** Invoke APDU shall identify the Gatekeeper or proxy. +- The GK or its proxy may send **mwActivate** and **mwDeactivate** Invoke APDUs, as required, to the served endpoint (typically following endpoint registration with the GK). +- Using mechanisms outside the scope of this Recommendation: + - A typical use of this capability allows a GK or proxy to store MWI activations and deactivations from unknown message centres sent to an endpoint that is out of service. This will most notably be the case for callback requests. When such an endpoint returns to service, it can interrogate known message centres for the MWI, but has no information about other sources of MWI information. +NOTE – These mechanisms may be used in addition to, or in place of, querying message centres known to the served user using the **mwInterrogate** Invoke APDU. + - Synchronization of the MWI information stored in a GK or proxy with the information stored in the served endpoint is outside the scope of this Recommendation. + +--- + +1 The proxy is an addressable entity either located in a separate endpoint or co-located with a GK. + +## 7.6 Interactions between SS-MWI and other supplementary services + +This clause specifies protocol interactions between the SS-MWI and other supplementary services currently defined by ITU-T H.450-series Recommendations. + +For interactions with supplementary services published subsequent to this Recommendation, see those other Recommendations. + +### 7.6.1 Interaction with call forwarding (SS-CFU, SS-CFNR, SS-CFB) + +No interaction. + +NOTE – An MWI should not be redirected to the diverted-to user. The indication may be given to the served user. + +### 7.6.2 Interaction with call transfer (SS-CT) + +No interaction. + +### 7.6.3 Interaction with call hold (SS-HOLD) + +No interaction. + +### 7.6.4 Interaction with call park (SS-PARK) and call pickup (SS-PICKUP) + +No interaction. + +### 7.6.5 Interaction with call waiting (SS-CW) + +No interaction. + +## 7.7 SS-MWI security considerations + +SS-MWI uses ITU-T H.225.0 call-independent signalling connections for transport of its APDUs. Served users should authenticate the message centre before processing an **mwActivate** or **mwDeactivate** Invoke APDU. Similarly, a message centre endpoint should authenticate a requesting served user before accepting a **mwInterrogate** Invoke APDU. Authentication procedures are described in [ITU-T H.235]. + +Applications that accept callback requests using MWI procedures should provide a means of screening the destination address provided in the **msgCentreId** field of the callback request, prior to initiating the callback. + +# 8 Signalling flows for SS-MWI + +This clause shows example message sequences for MWI supplementary services. + +Interactions of endpoints with their GKs are omitted for clarity. These interactions include registration, admission and status (RAS) messaging for admission, and message relay where GK-routed call signalling is used. GKs are normally transparent for the purposes of SS-MWI. + +## 8.1 Example message sequence for SS-MWI activation + +This clause shows examples of activation of SS-MWI. + +The first example shows a scenario where the call-independent signalling connection is not cleared by the message centre endpoint after the first activation of MWI. This could happen, for example, when the number of messages waiting changes before the message centre endpoint receives the **mwActivate** Return Result APDU. + +The CALL PROCEEDING message is normally not used for APDU return results as they are not sent end-to-end. + +See Figure 1. + +![Sequence diagram for Figure 1: Example of activation of SS-MWI. Lifelines: Message centre endpoint, Served user. Messages: Setup mwiActivate.inv, Connect mwiActivate.res, Facility mwiActivate.inv, Facility mwiActivate.res, ReleaseComplete. Reference: H.450.7(13)_F_01](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +``` + +sequenceDiagram + participant MCE as Message centre endpoint + participant SU as Served user + Note right of SU: H.450.7(13)_F_01 + MCE->>SU: Setup mwiActivate.inv + SU-->>MCE: Connect mwiActivate.res + MCE->>SU: Facility mwiActivate.inv + SU-->>MCE: Facility mwiActivate.res + MCE->>SU: ReleaseComplete + +``` + +Sequence diagram for Figure 1: Example of activation of SS-MWI. Lifelines: Message centre endpoint, Served user. Messages: Setup mwiActivate.inv, Connect mwiActivate.res, Facility mwiActivate.inv, Facility mwiActivate.res, ReleaseComplete. Reference: H.450.7(13)\_F\_01 + +**Figure 1 – Example of activation of SS-MWI** + +It is also possible to use the MWI activation mechanism to request a callback. In this instance, the optional originatingNr and nbOfMessages elements must be present. See Figure 2. + +![Sequence diagram for Figure 2: Example of a callback request using SS-MWI. Lifelines: Message centre endpoint, Served user. Messages: Setup mwiActivate.inv, Connect mwiActivate.res, Facility mwiActivate.inv, Facility mwiActivate.res, ReleaseComplete. Reference: H.450.7(13)_F_02](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant MCE as Message centre endpoint + participant SU as Served user + Note right of SU: H.450.7(13)_F_02 + MCE->>SU: Setup mwiActivate.inv + SU-->>MCE: Connect mwiActivate.res + MCE->>SU: Facility mwiActivate.inv + SU-->>MCE: Facility mwiActivate.res + MCE->>SU: ReleaseComplete + +``` + +Sequence diagram for Figure 2: Example of a callback request using SS-MWI. Lifelines: Message centre endpoint, Served user. Messages: Setup mwiActivate.inv, Connect mwiActivate.res, Facility mwiActivate.inv, Facility mwiActivate.res, ReleaseComplete. Reference: H.450.7(13)\_F\_02 + +**Figure 2 – Example of a callback request using SS-MWI** + +## 8.2 Example message sequence for SS-MWI deactivation + +This clause shows an example of deactivation of SS-MWI. See Figure 3. + +![Sequence diagram for Figure 3: Example of deactivation of SS-MWI. Lifelines: Message centre endpoint, Served user. Messages: Setup mwiDeactivate.inv, Connect mwiDeactivate.res, ReleaseComplete. Reference: H.450.7(13)_F_03](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +``` + +sequenceDiagram + participant MCE as Message centre endpoint + participant SU as Served user + Note right of SU: H.450.7(13)_F_03 + MCE->>SU: Setup mwiDeactivate.inv + SU-->>MCE: Connect mwiDeactivate.res + MCE->>SU: ReleaseComplete + +``` + +Sequence diagram for Figure 3: Example of deactivation of SS-MWI. Lifelines: Message centre endpoint, Served user. Messages: Setup mwiDeactivate.inv, Connect mwiDeactivate.res, ReleaseComplete. Reference: H.450.7(13)\_F\_03 + +**Figure 3 – Example of deactivation of SS-MWI** + +## 8.3 Example message sequence for SS-MWI interrogation + +This clause shows an example of interrogation of SS-MWI. See Figure 4. + +![Sequence diagram showing the interaction between a Message centre endpoint and a Served user for SS-MWI interrogation.](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +``` +sequenceDiagram + participant MCE as Message centre endpoint + participant SU as Served user + Note right of MCE: Setup + MCE->>SU: mwiInterrogate.inv + Note right of SU: Connect + SU->>MCE: mwiInterrogate.res + Note right of MCE: ReleaseComplete + MCE->>SU: ReleaseComplete + Note right of SU: H.450.7(13)_F04 +``` + +Sequence diagram showing the interaction between a Message centre endpoint and a Served user for SS-MWI interrogation. + +Figure 4 – Example of interrogation of SS-MWI + +# 9 Specification and description language (SDL) diagrams + +The procedures for Message Waiting Indication signalling entities are described in SDL form in Figures 6 through 10. For primitives and their meanings, refer to clause 7.4.3. In case of a conflict between the SDLs and the text within the previous clauses, the text shall take precedence. + +The symbols used in the SDLs are defined in Figure 5. + +![Six SDL symbols used in the diagrams. Primitive from endpoint user symbol: a rectangle with a chevron on the left side pointing right. State symbol: a horizontal oval. Message to remote endpoint symbol: a rectangle with a chevron on the right side pointing right. Primitive to endpoint user symbol: a rectangle with a chevron on the left side pointing left. Processing symbol: a rectangle with double vertical lines on its left and right sides. Message from remote endpoint symbol: a rectangle with a chevron on the right side pointing left.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +| | | | +|-------------------------------------|----------------|--------------------------------------------------------| +|
    Primitive from
    endpoint user |
    State |
    Message to
    remote endpoint | +|
    Primitive to
    endpoint user |
    Processing |
    Message from
    remote endpoint
    H.450.7(13)_F05 | + +Six SDL symbols used in the diagrams. Primitive from endpoint user symbol: a rectangle with a chevron on the left side pointing right. State symbol: a horizontal oval. Message to remote endpoint symbol: a rectangle with a chevron on the right side pointing right. Primitive to endpoint user symbol: a rectangle with a chevron on the left side pointing left. Processing symbol: a rectangle with double vertical lines on its left and right sides. Message from remote endpoint symbol: a rectangle with a chevron on the right side pointing left. + +Figure 5 – SDL Symbols + +ITU-T H.450.1 APDUs sent via the network are indicated using bold letters with the following abbreviations: + +- (**.inv**) Invoke APDU +- (**.rr**) Return Result APDU +- (**.re**) Return Error APDU +- (**.rej**) Reject APDU + +## 9.1 SDL representation of SS-MWI at the message centre endpoint + +The figures in this clause show the behaviour of an SS-MWI control entity within the message centre endpoint. See Figures 6, 7 and 8. + +![SDL diagram showing the state transition for SS-MWI activation at the message centre endpoint. It starts at MWI-MC-Idle, receives an activation request, sends an mwiActivate.inv message, starts timer T1, and then waits. From the wait state, it can receive an mwiActivate.res (leading to Stop T1 and Activation accepted), an mwiActivate.err (leading to Stop T1 and Activation rejected), or experience a T1 expiry. Both successful and failed activations lead back to the MWI-MC-Idle state. A reference H.450.7(13)_F06 is noted near the rejection path.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MWI-MC-Idle + MWI-MC-Idle --> Request: Activation request from the message centre + Request --> Inv: Message with mwiActivate.inv + Inv --> StartT1: Start T1 + StartT1 --> MWI-MC-Wait + state "MWI-MC-Wait" as MWI-MC-Wait + MWI-MC-Wait --> Res: Message with mwiActivate.res + MWI-MC-Wait --> Err: Message with mwiActivate.err + MWI-MC-Wait --> T1expiry: T1 expiry + Res --> StopT1_1: Stop T1 + Err --> StopT1_2: Stop T1 + T1expiry --> StopT1_2 + StopT1_1 --> Accepted: Activation accepted + StopT1_2 --> Rejected: Activation rejected + Accepted --> MWI-MC-Idle + Rejected --> MWI-MC-Idle + Note right of Rejected: H.450.7(13)_F06 + +``` + +SDL diagram showing the state transition for SS-MWI activation at the message centre endpoint. It starts at MWI-MC-Idle, receives an activation request, sends an mwiActivate.inv message, starts timer T1, and then waits. From the wait state, it can receive an mwiActivate.res (leading to Stop T1 and Activation accepted), an mwiActivate.err (leading to Stop T1 and Activation rejected), or experience a T1 expiry. Both successful and failed activations lead back to the MWI-MC-Idle state. A reference H.450.7(13)\_F06 is noted near the rejection path. + +Figure 6 – SDL representation of SS-MWI activation at the message centre endpoint + +![SDL diagram showing the state transition for SS-MWI deactivation at the message centre endpoint. The process starts in the MWI-MC-Idle state, receives a deactivation request, sends an mwiDeactivate.inv message, starts timer T1, and then waits. In the MWI-MC-Wait state, it can receive an mwiDeactivate.rr (accepting) or mwiDeactivate.re (rejecting) message, or T1 can expire. Both accept and reject lead to Stop T1 and back to the Idle state. An arrow labeled H.450.7(13)_F07 points from the T1 expiry path to the rejection path.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MWI-MC-Idle + MWI-MC-Idle --> DeactivationRequest[Deactivation request from the message centre] + DeactivationRequest --> mwiDeactivateInv[Message with mwiDeactivate.inv] + mwiDeactivateInv --> StartT1[Start T1] + StartT1 --> MWI-MC-Wait + state "MWI-MC-Wait" as MWI-MC-Wait + MWI-MC-Wait --> mwiDeactivateRr[Message with mwiDeactivate.rr] + MWI-MC-Wait --> mwiDeactivateRe[Message with mwiDeactivate.re] + MWI-MC-Wait --> T1expiry[T1 expiry] + mwiDeactivateRr --> StopT1Rr[Stop T1] + mwiDeactivateRe --> StopT1Re[Stop T1] + T1expiry --> StopT1Re + StopT1Rr --> DeactivationAccepted[Deactivation accepted] + StopT1Re --> DeactivationRejected[Deactivation rejected] + DeactivationAccepted --> MWI-MC-Idle + DeactivationRejected --> MWI-MC-Idle + T1expiry --> StopT1Re : H.450.7(13)_F07 + +``` + +SDL diagram showing the state transition for SS-MWI deactivation at the message centre endpoint. The process starts in the MWI-MC-Idle state, receives a deactivation request, sends an mwiDeactivate.inv message, starts timer T1, and then waits. In the MWI-MC-Wait state, it can receive an mwiDeactivate.rr (accepting) or mwiDeactivate.re (rejecting) message, or T1 can expire. Both accept and reject lead to Stop T1 and back to the Idle state. An arrow labeled H.450.7(13)\_F07 points from the T1 expiry path to the rejection path. + +**Figure 7 – SDL representation of SS-MWI deactivation at the message centre endpoint** + +![SDL diagram of SS-MWI interrogation at the message centre endpoint. The process starts at state MWI-MC-Idle, sends a message with mwiInterrogate.inv, checks if interrogation is possible. If yes, it interrogates MWI and sends a message with mwiInterrogate.res. If no, it sends a message with mwiInterrogate.re. Both messages lead back to state MWI-MC-Idle. Reference H.450.7(13)_F08.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MWI-MC-Idle + MWI-MC-Idle --> mwiInterrogate.inv : Message with mwiInterrogate.inv + mwiInterrogate.inv --> Interrogation possible? + state "Interrogation possible?" as Interrogation possible? + Interrogation possible? --> Yes + Interrogation possible? --> No + Yes --> Interrogate MWI + state "Interrogate MWI" as Interrogate MWI + Interrogate MWI --> mwiInterrogate.res : Message with mwiInterrogate.res + No --> mwiInterrogate.re : Message with mwiInterrogate.re + mwiInterrogate.res --> MWI-MC-Idle + mwiInterrogate.re --> MWI-MC-Idle + +``` + +H.450.7(13)\_F08 + +SDL diagram of SS-MWI interrogation at the message centre endpoint. The process starts at state MWI-MC-Idle, sends a message with mwiInterrogate.inv, checks if interrogation is possible. If yes, it interrogates MWI and sends a message with mwiInterrogate.res. If no, it sends a message with mwiInterrogate.re. Both messages lead back to state MWI-MC-Idle. Reference H.450.7(13)\_F08. + +**Figure 8 – SDL representation of SS-MWI interrogation at the message centre endpoint** + +## 9.2 SDL representation of SS-MWI at the served user + +The figures in this clause show the behaviour of an MWI supplementary service control entity within the served user. See Figures 9 and 10. + +![SDL diagram for SS-MWI activation and deactivation at the served endpoint. The diagram starts with a state 'MWI-Ser-Idle'. It branches into two paths: activation and deactivation. The activation path involves receiving 'mwiActivate.inv', checking if activation is possible, activating MWI if possible, and then sending 'mwiActivate.res' or 'mwiActivate.err' to return to the idle state. The deactivation path follows a similar pattern with 'mwiDeactivate.inv', 'Deactivate MWI', and 'mwiDeactivate.res' or 'mwiDeactivate.err'.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) + +``` +stateDiagram-v2 + [*] --> MWI-Ser-Idle + MWI-Ser-Idle --> mwiActivate.inv + mwiActivate.inv --> ActivationPossible{Activation possible?} + ActivationPossible -- No --> mwiActivate.err + ActivationPossible -- Yes --> ActivateMWI[Activate MWI] + ActivateMWI --> mwiActivate.res + mwiActivate.res --> MWI-Ser-Idle + mwiActivate.err --> MWI-Ser-Idle + MWI-Ser-Idle --> mwiDeactivate.inv + mwiDeactivate.inv --> DeactivationPossible{Deactivation possible?} + DeactivationPossible -- No --> mwiDeactivate.err + DeactivationPossible -- Yes --> DeactivateMWI[Deactivate MWI] + DeactivateMWI --> mwiDeactivate.res + mwiDeactivate.res --> MWI-Ser-Idle + mwiDeactivate.err --> MWI-Ser-Idle +``` + +H.450.7(13)\_F09 + +SDL diagram for SS-MWI activation and deactivation at the served endpoint. The diagram starts with a state 'MWI-Ser-Idle'. It branches into two paths: activation and deactivation. The activation path involves receiving 'mwiActivate.inv', checking if activation is possible, activating MWI if possible, and then sending 'mwiActivate.res' or 'mwiActivate.err' to return to the idle state. The deactivation path follows a similar pattern with 'mwiDeactivate.inv', 'Deactivate MWI', and 'mwiDeactivate.res' or 'mwiDeactivate.err'. + +Figure 9 – SDL representation of SS-MWI activation/deactivation at the served endpoint + +![SDL diagram showing the state transition for SS-MWI interrogation at the served endpoint. It starts at MWI-Ser-Idle, receives an interrogation request, sends an mwilnterrogate.inv message, starts timer T2, and then enters MWI-Ser-Wait. From there, it can receive an mwilnterrogate.rr (accept), an mwilnterrogate.re (reject), or experience a T2 expiry. Accept and reject lead to Stop T2 and then back to MWI-Ser-Idle. T2 expiry also leads to Stop T2 and then back to MWI-Ser-Idle. A label H.450.7(13)_F10 is present near the T2 expiry path.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MWI-Ser-Idle + MWI-Ser-Idle --> Request[Interrogation request from the user] + Request --> MessageInv[Message with mwilnterrogate.inv] + MessageInv --> StartT2[Start T2] + StartT2 --> MWI-Ser-Wait + state "MWI-Ser-Wait" as MWI-Ser-Wait + MWI-Ser-Wait --> MessageRr[Message with mwilnterrogate.rr] + MWI-Ser-Wait --> MessageRe[Message with mwilnterrogate.re] + MWI-Ser-Wait --> T2Expiry[T2 expiry] + MessageRr --> StopT2Rr[Stop T2] + MessageRe --> StopT2Re[Stop T2] + T2Expiry --> StopT2Expiry[Stop T2] + StopT2Rr --> Accepted[Interrogation accepted] + StopT2Re --> Rejected[Interrogation rejected] + StopT2Expiry --> Rejected + Accepted --> MWI-Ser-Idle + Rejected --> MWI-Ser-Idle + +``` + +H.450.7(13)\_F10 + +SDL diagram showing the state transition for SS-MWI interrogation at the served endpoint. It starts at MWI-Ser-Idle, receives an interrogation request, sends an mwilnterrogate.inv message, starts timer T2, and then enters MWI-Ser-Wait. From there, it can receive an mwilnterrogate.rr (accept), an mwilnterrogate.re (reject), or experience a T2 expiry. Accept and reject lead to Stop T2 and then back to MWI-Ser-Idle. T2 expiry also leads to Stop T2 and then back to MWI-Ser-Idle. A label H.450.7(13)\_F10 is present near the T2 expiry path. + +Figure 10 – SDL representation of SS-MWI interrogation at the served endpoint + +# Bibliography + +- [b-ITU-T H.Imp323] ITU-T Implementors' Guide – Series H (2011), *Implementors' Guide for Recommendations of the ITU-T H.323 system (Packet-based multimedia communications systems): H.323, H.225.0, H.245, H.246, H.283, H.341, H.450 Series, H.460 Series, and H.500 Series.* + + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.450.8-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.450.8-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ad98c6e45b6c52f074f0054407ca88a640d8f1d --- /dev/null +++ b/marked/H/T-REC-H.450.8-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58019f38be268f19eaa80c6d56d0f6b39d5741569a8f3ccc04117fa95d9c6465 +size 4016 diff --git a/marked/H/T-REC-H.460.11-200403-I_PDF-E/raw.md b/marked/H/T-REC-H.460.11-200403-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fd295f0dc73e4c5a9321b7d3d0348e2fdbf4ba78 --- /dev/null +++ b/marked/H/T-REC-H.460.11-200403-I_PDF-E/raw.md @@ -0,0 +1,404 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.460.11** + +(03/2004) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Supplementary +services for multimedia + +--- + +**Delayed call establishment within H.323 +systems** + +ITU-T Recommendation H.460.11 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.460.11** + +## **Delayed call establishment within H.323 systems** + +### **Summary** + +This Recommendation defines procedures to provide for delayed call establishment (delayed ringing) functionality within the context of ITU-T Rec. H.323. Delayed call establishment may be used to place a call, query capabilities, perform testing, or perform other functions without alerting the called user. Additionally, it may be used to place a call and guarantee that some condition is satisfied, such as the establishment of bidirectional media, before alerting the called party. + +###### **Source** + +ITU-T Recommendation H.460.11 was approved on 15 March 2004 by ITU-T Study Group 16 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +### INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Terms and definitions ..... | 1 | +| 4 Abbreviations..... | 1 | +| 5 Feature description..... | 2 | +| 6 Capability advertisement ..... | 2 | +| 7 Requesting delayed call establishment ..... | 3 | +| 8 Responding to a Delayed Call Establishment Request..... | 4 | +| 9 Delayed Call Establishment Release ..... | 5 | +| Appendix I – Sample call flows ..... | 7 | + + + +## Delayed call establishment within H.323 systems + +## 1 Scope + +This Recommendation defines the capability and procedures for delayed call establishment (DCE). Delaying the establishment of a call allows an H.323 entity to perform maintenance loops, provide network-based services (e.g., call completion on busy without the use of ITU-T Rec. H.450.9), or other functions without alerting the called user until so desired or when appropriate. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*. +- [2] ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- [3] ITU-T Recommendation H.460.1 (2002), *Guidelines for the use of the generic extensible framework*. +- [4] ITU-T Recommendation H.245 (2003), *Control protocol for multimedia communication*. + +## 3 Terms and definitions + +This Recommendation defines the following terms: + +**3.1 delayed call establishment (DCE):** Allows a call to be initiated, but not progressed to the point where the user is alerted or the call is connected. + +**3.2 delay point (DP):** The point in the call establishment procedures that must be reached before the call may proceed to the Alerting or Connected state. + +**3.3 delay point indicator (DPI):** A specific point of interest to the calling entity in the call establishment process. + +**3.4 DP reached (DPR):** The message transmitted by the called endpoint to the calling entity to indicate that the DP has been reached. + +**3.5 DCE release:** The message transmitted by the calling entity to the called endpoint releasing the endpoint from the DCE procedures and allowing the call to proceed as normal. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +DCE Delayed Call Establishment + +DP Delay Point + +DPI Delay Point Indicator + +DPR Delay Point Reached + +RAS Registration, Admission and Status + +## 5 Feature description + +This Recommendation defines a procedure wherein a calling entity may request that an initiated call be progressed to a specified point, but then progress delayed, without alerting the user to the presence of the call or connecting the call. This allows, for example, for media channels to be established or for other conditions to be met before the user is alerted to the presence of the call. In some cases, it is expected that the call may actually never progress to the point of alerting the user or fully connecting, such as when the called device is being probed for supported capabilities or when the called device is called for the purpose of establishing media channels to be used for testing purposes (e.g., maintenance loop functions of H.245). + +Network-based devices that offer services such as Call Completion on No Answer and Call Completion on Busy may also use this feature. While supplementary services specified in the H.450-series Recommendations may be used for the aforementioned services, these services and other services may be implemented using this generic construct. + +When a called endpoint receives a **Setup** message from a calling entity and when that called endpoint supports the DCE feature, the called endpoint shall not alert the user to the fact that the call has been received and shall not transmit an **Alerting** message or **Connect** message. Instead, the called endpoint shall first notify the calling endpoint when the Delay Point has been reached and proceed with call establishment only if either Implicit DCE Release parameter is signalled in the initial setup or after an explicit DCE Release message is received. This delay may make it necessary for the calling endpoint to cancel or prolong H.225.0 call control timers (e.g., T310). + +The DCE procedures do not preclude the endpoint from carrying out any initial call signalling up to, but not including, alerting the user or connecting the call. That is, terminal capabilities may be exchanged, media channels may be opened, media packets may be sent and received, etc., without violating any part of this Recommendation. + +Special consideration must be given to Gateway devices that perform signalling interworking between H.323 and other networks. Other networks may or may not have the ability to delay call establishment in accordance with this Recommendation. If the other network served by the Gateway supports comparable functionality, the Gateway may advertise support for this capability. Otherwise, the Gateway may elect to not advertise support or may elect to withhold presenting the call to the other network until the Delay Point is reached. Such design choices are considered an implementation matter and are outside the scope of this Recommendation. + +Consideration must also be given to possible security concerns, e.g., to guard against denial-of-service attacks by tying up resources at the called endpoint. Further restrictions may result from the environment in which this service is employed, for instance charging requirements may restrict the usage of media channels before the call is in active state. + +## 6 Capability advertisement + +Endpoints capable of supporting DCE shall advertise this capability via the Generic Extensibility Framework defined in ITU-T Recs H.323 and H.460.1. Endpoints may advertise this capability through RAS or through H.225.0 Call Signalling messages as a supported, desired, or needed feature. Calling entities shall advertise this capability as a needed or desired feature in Call Signalling messages when needing or desiring DCE feature activation at the called party, respectively. Called endpoints that are capable of supporting DCE shall advertise this capability in the list of supported features when responding to the incoming call. The identifier for the delayed call establishment capability is shown in Table 1. + +**Table 1/H.460.11 – Indication of the delayed call establishment feature** + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Feature name: | Delayed call establishment | +| Feature description: | This feature allows an originating endpoint to request a terminating endpoint to delay establishment of a call based on some specified event | +| Feature identifier type: | Standard | +| Feature identifier value: | 11 | + +Parameters associated with the advertisement of this capability are specified in the following clauses. In consideration of backward compatibility with further revisions to this Recommendation, the recipient shall simply ignore any parameters received other than those specified in this Recommendation. + +## 7 Requesting delayed call establishment + +An endpoint may initiate a call and request delayed call establishment by including the capability shown in clause 5 in the outgoing **Setup** message. Along with the capability, the calling entity shall include a parameter or list of parameters called Delay Point Indicators (DPIs), which indicates points of interest to the calling entity in the call establishment process. The DPI parameter definition is shown in Table 2. + +**Table 2/H.460.11 – Delay Point Indicator (DPI) parameter** + +| | | +|-----------------------------|--------------------------------------------------------------------------------------------------------------| +| Parameter name: | Delay Point Indicator (DPI) | +| Parameter description: | Indicates the point of interest to which the call must progress before being delayed | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 1 | +| Parameter type: | number8 | +| Parameter cardinality: | One or more in the initial DCE request, zero or more in the DPR message, and zero in the DCE Release message | + +The possible values of the Delay Point Indicator (DPI) are shown in Table 3: + +**Table 3/H.460.11 – Delay Point Indicator (DPI) values** + +| Value | Meaning | +|----------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------| +| 0 | NULL | +| 1 | Terminal Capabilities are received by the called endpoint. | +| 2 | Master/Slave determination has completed. | +| 3 | Media channels are opened from the called endpoint. | +| 4 | Media channels are opened to the called endpoint. | +| 5 | Media channels are established bidirectionally. | +| NOTE – Additional delay point values may be added in future versions of this Recommendation and are hereby reserved. | | + +The DPI parameters are independent and suggest no ordering of events. For example, it is possible that the calling and called endpoints may utilize Fast Connect to establish bidirectional media before Master/Slave Determination completes. As such, the calling entity shall not assume that, simply because media is established bidirectionally that Master/Slave procedures have completed. + +The calling endpoint shall not include the same DPI more than once and the called device shall ignore any duplicate DPIs received. + +The "Delay Point" (DP) in the call establishment procedure is the point at which all of the DPI events have been satisfied. For example, if the calling entity provides a DPI 2 and DPI 5, the called endpoint shall perform both Master/Slave negotiation and opening bidirectional media flows before notifying the calling party that it has successfully reached the DP. + +The "NULL" DPI (Indicator 0) is used to simply indicate that there are no specific conditions that must be satisfied before reaching the DP, meaning that the DP is reached immediately following the reception of the initial Setup message. This might be useful, for example, in cases where an entity simply wants to test that an endpoint is available to accept a call or to perform some testing that does not require reaching any particular DP. + +Clause 8 explains that an endpoint is normally not permitted to alert the called user until it receives an explicit DCE Release message from the calling endpoint. There are cases wherein the calling endpoint may want to prevent the called endpoint from proceeding until the DP is reached, but may not need the called endpoint to wait for an explicit DCE Release. To allow the called endpoint to proceed with alerting the called user after reaching the DP and without waiting for an explicit DCE Release message, the parameter in Table 4 may be provided. + +**Table 4/H.460.11 – Implicit DCE Release parameter** + +| | | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Implicit DCE Release | +| Parameter description: | Indicates that the called endpoint may alert the user once the DP is reached without waiting for an explicit DCE Release message. Inclusion of this parameter indicates that the calling endpoint will not transmit a DCE Release message. | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 2 | +| Parameter type: | No associated type. | +| Parameter cardinality: | Zero or one in the initial request message, zero in all other messages | + +The "Implicit DCE Release" parameter has a parameter identifier, but has no associated type. As such, the **EnumeratedParameter.content** field shall not be present and shall be ignored if present, as this field is reserved for future use. + +## 8 Responding to a Delayed Call Establishment Request + +When an endpoint receives a request in the **Setup** message to delay the establishment until the specified DP is reached, the called endpoint shall respond to that request in its initial and subsequent messages indicating support or no support for the capability. Calling devices should be aware that initial messages received when placing a call might be those from an intermediate call signalling entity, rather than the called endpoint, such as a Gatekeeper routing call signalling, and may not contain the DCE capability advertisement. The initial messages from the called endpoint shall contain the capability advertisement without parameters to indicate support and acceptance of the DCE request and to indicate that the DP has not been reached. + +Upon accepting the request to delay call establishment, the called endpoint shall progress the call state machine to the specified DP and then notify the calling entity that said point has been reached. For example, if the calling entity requests that the call be delayed until Master/Slave procedures (DPI 2) and bidirectional media channel opening (DPI 5) complete, the called endpoint shall initiate or respond to H.245 messages, exchange capabilities, negotiate Master/Slave, open and accept logical channels and then notify the calling entity that the DP has been reached. As noted in clause 7, there is no assumed order as to when these DPI events may be satisfied. When using Fast Connect, for example, DPI 5 may be satisfied before DPI 2. + +Upon reaching the DP and irrespective of the presence of the "Implicit DCE Release" parameter in the initial request, the called endpoint shall transmit a **Facility** or other appropriate message to the calling entity with the DCE capability advertised and containing the parameter from Table 5. This message is referred to as the Delay Point Reached (DPR) message. + +**Table 5/H.460.11 – Delay Point Reached parameter** + +| | | +|-----------------------------|-----------------------------------------------------------------------| +| Parameter name: | Delay Point Reached (DPR) | +| Parameter description: | Indicates to the calling entity that the Delay Point has been reached | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 3 | +| Parameter type: | No associated type | +| Parameter cardinality: | One when sending a DPR message, zero for any other message | + +The DPR parameter has a parameter identifier, but has no associated type. As such, the **EnumeratedParameter.content** field shall not be present and shall be ignored if present, as this field is reserved for future use. + +After the DP has been reached and the DPR message has been transmitted, the call establishment shall proceed as normal, except that the called endpoint may not alert the user, transmit an **Alerting** message, or transmit a **Connect** message until instructed by the calling entity or unless the "Implicit DCE Release" parameter was provided in the initial call establishment message. For example, if the calling entity signalled DPI 5, the called endpoint may still continue H.245, exchanging terminal capabilities and performing Master/Slave negotiation, even if media channels were opened as part of Fast Connect. If the "Implicit DCE Release" parameter was provided in the initial request from the calling endpoint, the called endpoint must still return a DPR message, but may proceed with alerting the user without waiting for a DCE Release message. + +In the event that the called device cannot reach the requested DP, such as when the calling entity requests the opening of bidirectional channels (DPI 5), but the called endpoint is a receive-only endpoint, or in the case that an unrecognized DPI is received, the called device shall transmit the DPR message after satisfying all of the DPIs that it can satisfy and include in that message all of the DPIs that it could not satisfy, including unrecognized DPIs. It shall not include DPIs that were satisfied. The DPR parameter shall precede the DPI parameters and be part of a single DCE capability parameter in that message. + +## 9 Delayed Call Establishment Release + +Upon receiving the DPR message from the called endpoint and not having provided the "Implicit DCE Release" parameter in the original call establishment message, the calling entity may then send a **Facility** or other appropriate message to the called endpoint to instruct it to proceed with call establishment. To do so, the calling entity shall advertise the DCE capability with the parameter specified in Table 6. This message is referred to as the "DCE Release" message. + +An endpoint shall not transmit nor expect a DCE Release message in the case that the Implicit DCE Release parameter was included in the original Setup message. The text in this clause, therefore, only applies to the signalling scenario wherein an Implicit DCE Release parameter was not provided. + +**Table 6/H.460.11 – DCE Release Parameter** + +| | | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | DCE Release | +| Parameter description: | Indicates to the called entity that the call may proceed to a fully established state (i.e., the calling endpoint is releasing the called endpoint from the DCE state) | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 4 | +| Parameter type: | No associated type | +| Parameter cardinality: | One for the DCE Release message, zero for any other message | + +The DCE Release parameter has a parameter identifier, but has no associated type. As such, the **EnumeratedParameter.content** field shall not be present and shall be ignored if present, as this field is reserved for future use. + +The calling device is not required to wait until the DPR message is received before sending a DCE Release message. The calling endpoint may elect, for whatever reason, to progress the call in spite of the fact that the DP has not been reached (i.e., the DPR message is not received). The called endpoint shall treat the early reception of the DCE Release parameter as a cancellation of the original DCE request and proceed with the call normally. + +Only after receiving the DCE Release message shall the called endpoint progress the call by alerting the user and transmitting an **Alerting** message. It should be understood that, as **Alerting** is an optional message, the called endpoint might elect to skip the transmission of an **Alerting** message and transmit a **Connect** message instead. This is valid and this Recommendation does not attempt to change the rules set forth within ITU-T Rec. H.323 as to the normal call establishment procedures, except to introduce a delay just before the point where the called user would be alerted or the call would be connected. + +The calling endpoint is also not obligated to release the called endpoint from the DCE state. As outlined in clause 5, the calling endpoint may simply desire to call the endpoint to probe for capabilities, perform tests, etc. The called endpoint shall not treat the lack of a DCE Release message as an error. If the calling device does not transmit a DCE Release in a timely manner and there is no other activity to indicate that the call is active, the called device may send a Status Inquiry and wait for a Status message from time to time to ensure that the calling device has not failed. The timing of such messages is up to implementation, but should not be transmitted more frequently than 30 s. + +## Appendix I + +### Sample call flows + +This appendix shows sample call flows of applications that might be made possible through the use of this Recommendation. + +The first call flow demonstrates how a network operator might perform maintenance loop operations on deployed H.323 devices. This flow assumes that the endpoint properly supports the H.245 **MaintenanceLoop** request message + +![Sequence diagram for Continuity and/or QoS testing between a Testing device and a Tested endpoint.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +The diagram illustrates a sequence of messages between a **Testing device** and a **Tested endpoint**. The sequence is as follows: + +- The **Testing device** sends a **SETUP** message to the **Tested endpoint** with the note: "delay ringing until bidirectional media is established". +- The **Tested endpoint** responds with **CALL PROCEEDING**. +- The **Testing device** sends **Terminal Capabilities**. +- The **Tested endpoint** responds with **Terminal Capabilities**. +- There is a **Master/slave** negotiation between the two. +- The **Testing device** sends an **OpenLogicalChannel** message. +- The **Tested endpoint** responds with **OpenLogicalChannel Ack**. +- The **Testing device** sends another **OpenLogicalChannel Ack**. +- A dashed line indicates the establishment of **Bidirectional media**. +- The **Tested endpoint** sends a **FACILITY (DPR)** message. +- The **Testing device** sends a **MaintenanceLoopRequest**. +- The **Tested endpoint** responds with **MaintenanceLoopAck**. +- A block labeled **Perform continuity and/or QoS testing** occurs between the two entities. +- The **Testing device** sends a **MaintenanceLoopOffCommand**. +- The **Tested endpoint** responds with **Release Complete**. + +Two callouts are present: "Do **not** explicitly notify the end point to start alerting" pointing to the **SETUP** message, and "Delay Point reached: Media established" pointing to the start of the **Bidirectional media** dashed line. The diagram is labeled H.460.11\_F01. + +Sequence diagram for Continuity and/or QoS testing between a Testing device and a Tested endpoint. + +**Figure I.1/H.460.11 – Continuity and/or QoS testing** + +The next call flow demonstrates how an intermediate signalling entity might provide call completion on busy subscriber service. + +![Sequence diagram showing successful CCBS GK routed call signalling between User A's endpoint, Gatekeeper/Proxy, and User B's endpoint. The process starts with a busy signal, followed by service activation, setup, release complete, and subsequent successful call establishment with various signalling messages like CALL PROCEEDING, FACILITY, ALERTING, and CONNECT.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +**Successful CCBS GK routed call signalling +GK handles CCBS for Users A and B** + +``` + +sequenceDiagram + participant User A's endpoint + participant Gatekeeper/Proxy + participant User B's endpoint + + Note right of User B's endpoint: B busy, Call from A failed + Note left of User A's endpoint: CCBS Service Activation for User A + Note right of User B's endpoint: User B becomes free + + User A's endpoint->>Gatekeeper/Proxy: SETUP (delay ringing until explicit notification) + Note right of Gatekeeper/Proxy: Tm + Gatekeeper/Proxy->>User B's endpoint: SETUP (delay ringing until explicit notification) + User B's endpoint->>Gatekeeper/Proxy: RELEASE COMPLETE (busy) + Note right of Gatekeeper/Proxy: Tm + Gatekeeper/Proxy->>User B's endpoint: SETUP (delay ringing until explicit notification) + User B's endpoint->>Gatekeeper/Proxy: CALL PROCEEDING (C1) + Gatekeeper/Proxy->>User B's endpoint: FACILITY (B's H.245 address/tunnelled data) + Note left of User A's endpoint: Delay Point Reached: Media established + User A's endpoint->>Gatekeeper/Proxy: SETUP (delay ringing until media is established, add B's H.245 address/tunnelled data) + Gatekeeper/Proxy->>User A's endpoint: CALL PROCEEDING (C2) + User A's endpoint->>Gatekeeper/Proxy: FACILITY (DPR) + Gatekeeper/Proxy->>User A's endpoint: FACILITY (DCE Release) + User A's endpoint->>Gatekeeper/Proxy: ALERTING + Gatekeeper/Proxy->>User A's endpoint: CONNECT + Gatekeeper/Proxy->>User B's endpoint: FACILITY (DCE Release) + User B's endpoint->>Gatekeeper/Proxy: ALERTING + Note right of Gatekeeper/Proxy: Merge Call Legs C1 & C2 + Note right of User B's endpoint: Normal Basic Call A-B + +``` + +H.460.11\_F02 + +Sequence diagram showing successful CCBS GK routed call signalling between User A's endpoint, Gatekeeper/Proxy, and User B's endpoint. The process starts with a busy signal, followed by service activation, setup, release complete, and subsequent successful call establishment with various signalling messages like CALL PROCEEDING, FACILITY, ALERTING, and CONNECT. + +**Figure I.2/H.460.11 – Network-based Call Completion on Busy Subscriber Service** + +NOTE – This example uses a polling method that requires more signalling than ITU-T Rec. H.450.9 and may have billing implications that are addressed in ITU-T Rec. H.450.9. Implementers are advised to give careful consideration to the means used to provide this service. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.460.12-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.460.12-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/H/T-REC-H.460.12-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/H/T-REC-H.460.12-200403-I_PDF-E/raw.md b/marked/H/T-REC-H.460.12-200403-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6894d5aea8c4d5eee88f35719de75b0061af9f38 --- /dev/null +++ b/marked/H/T-REC-H.460.12-200403-I_PDF-E/raw.md @@ -0,0 +1,218 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.460.12** + +(03/2004) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Supplementary +services for multimedia + +--- + +**Glare control indicator within H.323 systems** + +ITU-T Recommendation H.460.12 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.460.12** + +## **Glare control indicator within H.323 systems** + +## **Summary** + +Glare, also known as dual seizure, is a condition in which two entities attempt to select the same circuit within the trunk group; in the context of this Recommendation, the two entities are a H.323 Gatekeeper and a PSTN switch. This Recommendation specifies a mechanism that allows an egress H.323-PSTN Gateway to resolve a glare condition that is detected on the Gateway when circuit selection is done on the Gatekeeper. The Gatekeeper delivers a Glare Control Indicator to the Gateway to inform the Gateway on how to deal with the glare condition. + +###### **Source** + +ITU-T Recommendation H.460.12 was approved on 15 March 2004 by ITU-T Study Group 16 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +# INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Glare Control Indicator..... | 1 | +| 3.1 Delivery of Glare Control Indicator ..... | 2 | +| 3.2 Glare resolution at Gateway ..... | 2 | +| 3.3 Generic Extensibility Framework..... | 2 | +| 4 Glare Control Indicator parameter..... | 3 | + + + +## Glare control indicator within H.323 systems + +# 1 Scope + +This Recommendation specifies a mechanism that allows an egress H.323-PSTN Gateway to resolve a glare condition (also known as "dual seizure") that is detected on the Gateway when circuit selection is done on the Gatekeeper. The Gatekeeper delivers a Glare Control Indicator to the Gateway to inform the Gateway on how to deal with the glare condition. + +For bidirectional (both-way) trunk groups between a H.323-PSTN Gateway and a PSTN switch, various circuit selection algorithms are defined in ITU-T Rec. Q.764 to minimize glare when both the Gateway and the PSTN switch attempt to select the same circuit within the trunk group. + +In addition, various algorithms may be used to specify the action to be taken to resolve the glare condition. For example, if glare occurs on an even-numbered circuit within a trunk group, the outgoing call (from the H.323 network to the PSTN) may be allowed to proceed but the incoming call must be re-attempted on another available circuit. This glare resolution algorithm is normally configured along with the circuit selection algorithm on each device. + +ITU-T Rec. H.323 provides the ability for a Gatekeeper to select the circuit within a trunk group to be used for a call from the H.323 network to a PSTN network through a H.323-PSTN Gateway. The 'group' field in the H.323 **destinationCircuitId** structure may be used to transport the trunk group identifier and the 'member' field in the same structure may be used to transport the circuit identifier from the Gatekeeper to the Gateway. This Recommendation provides a means for the Gatekeeper to also control how a glare condition may be resolved on a Gateway. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*. +- ITU-T Recommendation H.460.8 (2002), *Querying for alternate routes within H.323 systems*. +- ITU-T Recommendation Q.764 (1999), *Signalling system No. 7 – ISDN user part signalling procedures*. + +# 3 Glare Control Indicator + +The Glare Control Indicator determines the action the Gateway should take if it detects glare for the circuit in question. The Glare Control Indicator has two values: + +- 1) Outgoing call from the H.323 network to the PSTN has precedence. +- 2) Incoming call from the PSTN to the H.323 network has precedence. + +## 3.1 Delivery of Glare Control Indicator + +The Gatekeeper includes a Glare Control Indicator along with the circuit selection information (**destinationCircuitId**) that it sends to the Gateway. In the case of direct routed call signalling, the Gatekeeper shall send the Glare Control Indicator with the **destinationCircuitId** in the ACF message that it sends to the calling H.323 Endpoint which shall forward the Glare Control Indicator in the Setup message that it sends to the egress Gateway. In the case of Gatekeeper routed call signalling, the Gatekeeper shall send the Glare Control Indicator with the **destinationCircuitId** in the Setup that it sends to the H.323-PSTN Gateway. + +## 3.2 Glare resolution at Gateway + +If the Glare Control Indicator indicates the outgoing call has precedence, then the Gateway will proceed with the outgoing call from the H.323 network to the PSTN and release the incoming call from the PSTN. + +If the Glare Control Indicator indicates the incoming call has precedence, the Gateway will allow the incoming call from the PSTN to proceed and send another ARQ to the Gatekeeper, so that it can select another available circuit for the outgoing call. The Gateway will use the ARQ ReQuery procedures defined in ITU-T Rec. H.460.8 to inform the Gatekeeper that another circuit must be selected. The Gateway shall send a subsequent ARQ message with an incremented query count and a **CallTerminationCause** structure containing the cause IE set to Q.850 value 'requested circuit/channel not available'. When the Gatekeeper receives a subsequent ARQ with an incremented query count and a **CallTerminationCause** structure containing the cause value set to Q.850 value 'requested circuit/channel not available', it shall select another circuit for the outgoing call and send an ACF back to the Gateway. + +## 3.3 Generic Extensibility Framework + +A Gatekeeper includes the Glare Control Indicator with the **destinationCircuitId** in H.225.0 RAS and call signalling messages. The Glare Control Indicator parameter shall be transported using the generic extensibility framework as described below. + +When sending the Glare Control Indicator parameter in the call signalling messages, the Glare Control Indicator shall be coded in the **genericData** parameter in the H.225.0 H323-UU-PDU in the User-User Information Element. + +When sending the Glare Control Indicator parameter in the RAS messages, the Glare Control Indicator shall be coded in the **genericData** parameter in the request parameter of the H.225.0 **RasMessage**. + +The **genericData** parameter indicates the Glare Control Indicator feature and contains a Glare Control Indicator parameter. + +Table 1 defines the Glare Control Indicator feature. + +**Table 1/H.460.12 – Glare Control Indicator from a Gatekeeper to a Gateway** + +| | | +|---------------------------|----------------------------------------------------------------------------------------------| +| Feature name: | Glare Control Indicator | +| Feature description: | This feature allows an H.323 Gatekeeper to control glare resolution on a H.323-PSTN Gateway. | +| Feature identifier type: | Standard | +| Feature identifier value: | 12 | + +# 4 Glare Control Indicator parameter + +Table 2 defines the Glare Control Indicator parameter. + +**Table 2/H.460.12 – Glare Control Indicator parameter** + +| | | +|-----------------------------|--------------------------------------------------------------------------------------------------------------| +| Parameter name: | Glare Control Indicator Parameter | +| Parameter description: | This is the data sent in H.225.0 RAS and Call Signalling messages to control the glare condition. | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 1 | +| Parameter type: | number8, values:
    1 = Outgoing call to PSTN has precedence.
    2 = Incoming call from PSTN has precedence. | +| Parameter cardinality: | Once and only once | + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.460.13-200403-I_PDF-E/raw.md b/marked/H/T-REC-H.460.13-200403-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2cd0d27ac02cd4bc90989232e2d0f39fc1373d7e --- /dev/null +++ b/marked/H/T-REC-H.460.13-200403-I_PDF-E/raw.md @@ -0,0 +1,331 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.460.13** + +(03/2004) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Supplementary +services for multimedia + +--- + +**Called user release control within H.323 +systems** + +ITU-T Recommendation H.460.13 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.460.13** + +## **Called user release control within H.323 systems** + +### **Summary** + +This Recommendation specifies a mechanism that allows called H.323 Endpoints to signal that only the called user may release the call and that the release of the call by the calling user must be blocked. This is used for emergency call services where the release of calls to an emergency service operator must be under the control of the service operator. In addition, a calling H.323 Endpoint may signal that it is able to support called user release control capability. + +### **Source** + +ITU-T Recommendation H.460.13 was approved on 15 March 2004 by ITU-T Study Group 16 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +### FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +### INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +### CONTENTS + +| | Page | +|--------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Abbreviations..... | 1 | +| 4 Called user release control service description..... | 1 | +| 5 Called user release control procedures ..... | 2 | +| 5.1 Availability indication ..... | 2 | +| 5.2 Called user release control invocation..... | 3 | +| 5.3 Called user release control release ..... | 3 | +| 5.4 Call termination under called user release control ..... | 4 | +| 6 Called user release control indications ..... | 4 | +| 6.1 Called user release control parameter..... | 5 | + + + +## Called user release control within H.323 systems + +### 1 Scope + +Called user release control capability allows a called H.323 Endpoint to control whether the calling H.323 Endpoint is able to initiate release of a connection. In addition, the calling H.323 Endpoint is able to indicate that it can support called user release control capability. Called user release control is invoked during call establishment and may be subsequently released during the active phase of the call. This capability is sometimes called connection hold. + +Called user release control capability will allow calls to an emergency service operator to be under the control of the service operator such that the release of the call from the calling H.323 Endpoint is blocked. + +### 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*. + +### 3 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|------------------------------------| +| ACF | Admission Confirmation | +| ARJ | Admission Reject | +| ARQ | Admission Request | +| CURC | Called User Release Control | +| DRQ | Disengage Request | +| LCF | Location Confirmation | +| LRJ | Location Reject | +| LRQ | Location Request | +| RAS | Registration, Admission and Status | + +### 4 Called user release control service description + +Called user release control provides the ability for called H.323 Endpoints to signal that only the called user may release the call and that the release of the call by the calling user must be blocked at the calling H.323 Endpoint. The calling H.323 Endpoint shall be able to indicate to the called H.323 Endpoint that it can support called user release control capability. + +Called user release control is invoked during call establishment when the called H.323 Endpoint signals a called user release control request in the backward direction. The called H.323 Endpoint may also release called user release control once the call has been established such that the calling H.323 Endpoint is then able to release the connection. + +Called user release control shall only be invoked from a called endpoint that is used as an emergency service operator. + +In addition, while the calling H.323 Endpoint is in the called user release control state, it shall be able to signal to the called H.323 Endpoint whether the calling user has attempted to disconnect (go on-hook) and then, subsequently, to re-connect (go off-hook). The called H.323 Endpoint shall also be able to send an alerting request to the calling H.323 Endpoint while in the called user release control state to deliver a ringing indication to the calling user. + +### 5 Called user release control procedures + +The called user release control procedures to be performed by H.323 Endpoints and intermediate nodes are described below. + +### 5.1 Availability indication + +The availability and invocation procedures are illustrated in Figure 1. A calling H.323 Endpoint shall indicate that it is able to support called user release control capability by including a called user release control availability indication (curcAvailable) in the call establishment (Setup) messages. A calling H.323 Endpoint shall indicate that it is not able to support called user release control capability by including a called user release control availability indication (curcNotAvailable) in the call establishment (Setup) messages. Intermediate signalling entities shall relay any received called user release control availability indication. The called H.323 Endpoint shall proceed as follows: + +- 1) If the call request message contains a curcAvailable indication, it may invoke called user release control procedures. +- 2) If the call request message contains a curcNotAvailable indication, it may not invoke called user release control procedures. +- 3) If the call request message does not contain any called user release control availability indication, it may not invoke called user release control procedures. + +![Sequence diagram illustrating availability and invocation procedures between a Calling Endpoint, Gatekeeper, and Called Endpoint.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +The diagram shows a sequence of messages between three entities: Calling Endpoint, Gatekeeper, and Called Endpoint. The sequence is as follows: + +- The Calling Endpoint sends a **SETUP(curcAvailable)** message to the Gatekeeper. +- The Gatekeeper relays the **SETUP(curcAvailable)** message to the Called Endpoint. +- The Called Endpoint sends a **CONNECT(curcRequestNeedAck)** message back to the Gatekeeper. +- The Gatekeeper relays the **CONNECT(curcRequestNeedAck)** message to the Calling Endpoint. +- The Calling Endpoint sends a **FACILITY(curcAck)** message to the Gatekeeper. +- The Gatekeeper relays the **FACILITY(curcAck)** message to the Called Endpoint. +- Simultaneously with the receipt of the FACILITY message, an **Ack timer** (represented by a shaded triangle) starts at the Called Endpoint. + +The diagram is labeled H.460.13\_F01 at the bottom right. + +Sequence diagram illustrating availability and invocation procedures between a Calling Endpoint, Gatekeeper, and Called Endpoint. + +Figure 1/H.460.13 – Example availability and invocation procedures + +#### 5.2 Called user release control invocation + +A called H.323 Endpoint shall invoke called user release control by including a called user release control request (curcRequest or curcRequestNeedAck) in backward messages (Alerting, Call Proceeding, Progress, Connect and Facility messages). If the called H.323 Endpoint sends a curcRequestNeedAck, it shall start a called user release control acknowledgement timer and await a called user release control acknowledgement (curcAck) from the calling H.323 Endpoint. + +When a calling H.323 Endpoint receives a called user release control request (curcRequest or curcRequestNeedAck) in a backward message, it shall enter a called user release control state in which the calling user's ability to release a call is disabled. If the calling H.323 Endpoint receives a request to release the call (e.g., the calling user goes 'on-hook' at a H.323 terminal), the H.323 Endpoint shall not initiate release procedures. + +If the calling H.323 Endpoint receives a called user release control request with acknowledgement required (curcRequestNeedAck), it shall send a called user release control acknowledgement (curcAck) in any H.225.0 call signalling message to the called H.323 Endpoint. + +When the called H.323 Endpoint receives a curcAck, it shall stop the called user release control acknowledgement timer and consider the invocation as successful. Expiry of the called user release control acknowledgement timer shall be considered as an unsuccessful invocation of called user release control. + +Intermediate signalling entities shall relay any received called user release control request and acknowledgement. + +### 5.3 Called user release control release + +Figure 2 illustrates the Called User Release Control Release Procedures. After successful invocation of called user release control, the called H.323 Endpoint may release the called user release control capability by sending a called user release control release (curcRelease) or a CURC release with acknowledgement required (curcReleaseNeedAck) in any H.225.0 call signalling message to the calling H.323 Endpoint. + +If a called user release control has been invoked for a connection and the calling H.323 Endpoint receives a called user release control release (curcRelease or curcReleaseNeedAck), it shall re-enable the ability to release the call from the calling H.323 Endpoint. If the calling H.323 Endpoint receives a curcReleaseNeedAck, it shall send a called user release control release acknowledgement (curcReleaseAck) in any H.225.0 call signalling message to the called H.323 Endpoint. + +When the called H.323 Endpoint receives a curcAck, it shall consider the called user release control release as successful. + +Intermediate signalling entities shall relay any received called user release control release and release acknowledgement. + +![Sequence diagram illustrating the Called User Release Control Release Procedures. The diagram shows three participants: Calling Endpoint, Gatekeeper, and Called Endpoint. The sequence of messages is: 1. Called Endpoint sends FACILITY(curcReleaseNeedAck) to Gatekeeper. 2. Gatekeeper relays FACILITY(curcReleaseNeedAck) to Calling Endpoint. 3. Calling Endpoint sends FACILITY(curcReleaseAck) to Gatekeeper. 4. Gatekeeper relays FACILITY(curcReleaseAck) to Called Endpoint. The diagram is labeled H.460.13_F02.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) + +``` +sequenceDiagram + participant CE as Calling Endpoint + participant G as Gatekeeper + participant COE as Called Endpoint + Note right of COE: FACILITY(curcReleaseNeedAck) + COE->>G: FACILITY(curcReleaseNeedAck) + G->>CE: FACILITY(curcReleaseNeedAck) + Note left of CE: FACILITY(curcReleaseAck) + CE->>G: FACILITY(curcReleaseAck) + G->>COE: FACILITY(curcReleaseAck) + Note right of COE: H.460.13_F02 +``` + +Sequence diagram illustrating the Called User Release Control Release Procedures. The diagram shows three participants: Calling Endpoint, Gatekeeper, and Called Endpoint. The sequence of messages is: 1. Called Endpoint sends FACILITY(curcReleaseNeedAck) to Gatekeeper. 2. Gatekeeper relays FACILITY(curcReleaseNeedAck) to Calling Endpoint. 3. Calling Endpoint sends FACILITY(curcReleaseAck) to Gatekeeper. 4. Gatekeeper relays FACILITY(curcReleaseAck) to Called Endpoint. The diagram is labeled H.460.13\_F02. + +Figure 2/H.460.13 – Example called user release control release procedures + +### 5.4 Call termination under called user release control + +Figure 3 illustrates the disconnect and reconnect procedures. An intermediate entity may initiate normal call termination procedures regardless of the called user release control state. + +If the calling user attempts to terminate the call (by going on-hook) while the called user release control is invoked, the calling H.323 Endpoint shall block release of the connection and shall send a user disconnect indication (disconnectInd) in any H.225.0 call signalling message to the called H.323 Endpoint. The called user shall be notified of the calling user's disconnect indication. + +If the calling user reconnects to the call (by going off-hook) while the called user release control is invoked, the calling H.323 Endpoint shall send a user reconnect indication (reconnectInd) in any H.225.0 signalling message to the called H.323 Endpoint. The called user shall be notified of the calling user's reconnect indication. + +If the called H.323 Endpoint has received a disconnectInd from the calling H.323 Endpoint, it may send an alerting request (alertRequest) to the calling H.323 Endpoint in any H.225.0 signalling message. When the calling H.323 Endpoint receives the alertRequest, it shall notify the calling user with a ringing tone. + +Intermediate signalling entities shall relay any received disconnect and reconnect indications and alerting requests. + +![Sequence diagram illustrating disconnect and reconnect procedures between a Calling Endpoint, Gatekeeper, and Called Endpoint.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +``` +sequenceDiagram + participant CE as Calling Endpoint + participant G as Gatekeeper + participant C as Called Endpoint + Note right of C: H.460.13_F03 + CE->>G: FACILITY(disconnectInd) + G->>C: FACILITY(disconnectInd) + C->>G: FACILITY(alertReq) + G->>CE: FACILITY(alertReq) + CE->>G: FACILITY(reconnectInd) + G->>C: FACILITY(reconnectInd) +``` + +The diagram shows a sequence of messages between three entities: Calling Endpoint, Gatekeeper, and Called Endpoint. The sequence of messages is as follows: 1. The Calling Endpoint sends a FACILITY(disconnectInd) message to the Gatekeeper. 2. The Gatekeeper relays the FACILITY(disconnectInd) message to the Called Endpoint. 3. The Called Endpoint sends a FACILITY(alertReq) message to the Gatekeeper. 4. The Gatekeeper relays the FACILITY(alertReq) message to the Calling Endpoint. 5. The Calling Endpoint sends a FACILITY(reconnectInd) message to the Gatekeeper. 6. The Gatekeeper relays the FACILITY(reconnectInd) message to the Called Endpoint. The diagram is labeled H.460.13\_F03 in the bottom right corner. + +Sequence diagram illustrating disconnect and reconnect procedures between a Calling Endpoint, Gatekeeper, and Called Endpoint. + +**Figure 3/H.460.13 – Example disconnect and reconnect procedures** + +### 6 Called user release control indications + +Called user release control indications are transported in the H.225.0 RAS and call signalling (Q.931) messages using the generic extensibility framework. + +When sending the called user release control indications in the call signalling messages, they shall be coded in the **genericData** parameter in the H.225.0 H323-UU-PDU in the User-user Information Element. + +When sending the called user release control indications in the RAS messages, they shall be coded in the **genericData** parameter in the request parameter of the H.225.0 **RasMessage**. + +The GenericData parameter indicates the called user release control feature. Table 1 defines the called user release control feature. + +**Table 1/H.460.13 – Called user release control feature** + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Feature name: | Called User Release Control | +| Feature Description: | This feature allows a calling H.323 Endpoint to signal the ability to support release of a call from the called user only. In addition, this feature allows a called H.323 Endpoint to request the release of a call from the called user only. | +| Feature identifier type: | Standard | +| Feature identifier value: | 13 | + +### 6.1 Called user release control parameter + +The called user release control parameter is used to transport called user release control indications. Table 2 defines the called user release control parameter. + +**Table 2/H.460.13 – Called user release control parameter** + +| | | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Called User Release Control | +| Parameter description: | This is the data sent in H.225.0 RAS and Call Signalling messages to control called user release control. | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 1 | +| Parameter type: | number8, values:
    1 = curcAvailable
    2 = curcNotAvailable
    3 = curcRequest
    4 = curcAck
    5 = curcRelease
    6 = curcReleaseAck
    7 = curcRequestNeedAck
    8 = curcReleaseNeedAck
    9 = disconnectInd
    10 = reconnectInd
    11 = alertRequest | +| Parameter cardinality: | Once and only once | + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/raw.md b/marked/H/T-REC-H.460.14-200403-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cfaef9fe9c22702defa43fbe26f86016d144a6cb --- /dev/null +++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/raw.md @@ -0,0 +1,1271 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking across it, and the letters 'ITU' prominently displayed. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.460.14** + +(03/2004) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Supplementary +services for multimedia + +--- + +**Support for Multi-Level Precedence and +Preemption (MLPP) within H.323 systems** + +ITU-T Recommendation H.460.14 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.460.14** + +# **Support for Multi-Level Precedence and Preemption (MLPP) within H.323 systems** + +# **Summary** + +This Recommendation describes the procedures and the signalling protocol for Multi-Level Precedence and Preemption (MLPP), which allow the originator of a call in an H.323 environment to specify a precedence level of the call and for an existing lower precedence call to be preempted to release resources needed to complete that higher precedence call. For the networks and domains that allow this functionality, the H.460.14 mechanism ensures that important calls can be established and can remain connected during periods of congestion. + +These procedures use the H.323 Generic Extensibility Framework (GEF) and therefore do not require any changes to the base standards. + +###### **Source** + +ITU-T Recommendation H.460.14 was approved on 15 March 2004 by ITU-T Study Group 16 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | | Page | +|---------|----------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | Introduction ..... | 1 | +| 2.1 | Direct Endpoint Signalling ..... | 1 | +| 2.2 | Gatekeeper Routed Signalling ..... | 2 | +| 2.3 | Decomposed Gateway ..... | 2 | +| 2.4 | H.248 managed devices ..... | 3 | +| 2.5 | Stimulus device ..... | 3 | +| 3 | References ..... | 4 | +| 4 | Definitions ..... | 4 | +| 5 | Abbreviations ..... | 5 | +| 6 | Multi-level Precedence and Preemption Service description ..... | 5 | +| 6.1 | Provision of precedence levels ..... | 5 | +| 6.2 | Preemption of facilities ..... | 6 | +| 6.3 | Diversion ..... | 6 | +| 6.4 | Interactions with other services ..... | 6 | +| 7 | Signalling elements for MLPP ..... | 9 | +| 7.1 | Feature identifier ..... | 9 | +| 7.2 | Parameter ..... | 10 | +| 8 | Procedures ..... | 10 | +| 8.1 | Registration, Admission and Status (RAS) ..... | 10 | +| 8.2 | Call signalling procedures for H.450 endpoints ..... | 13 | +| 9 | Dynamic description ..... | 15 | +| 9.1 | Operational model ..... | 15 | +| 9.2 | Signalling flows ..... | 15 | +| 9.3 | Call states ..... | 20 | +| 9.4 | Timers ..... | 21 | +| 10 | Specification and Description Language (SDL) diagrams for MLPP ..... | 21 | +| 10.1 | Behaviour of User A's endpoint ..... | 22 | +| 10.2 | Behaviour of User B's endpoint ..... | 23 | +| 10.3 | Behaviour of User C's endpoint ..... | 26 | +| 11 | Protocol interactions with other endpoint features ..... | 26 | +| 11.1 | Functional endpoints ..... | 26 | +| 11.2 | Stimulus-based endpoints ..... | 28 | +| 11.3 | Interworking with Switched Circuit Network ..... | 28 | +| Annex A | – ASN.1 definition ..... | 28 | + + + +# **Support for Multi-Level Precedence and Preemption (MLPP) within H.323 systems** + +# **1 Scope** + +Multi-Level Precedence and Preemption provides a framework for the treatment of calls based on precedence. It supports the preemption of active calls by higher-precedence calls when resources are limited. The system presented here is designed to be adaptable to different models of endpoints within H.323. It may be used to support direct endpoint call signalling or gatekeeper-routed endpoints of varying capabilities. For example, intelligent endpoints may support the MLPP procedures internally, while simple (e.g., stimulus-based) endpoints may require their Gatekeeper to implement the procedures in their stead. In the latter case, MLPP-specific signalling would be used only between Gatekeepers and other Gatekeepers or intelligent Gateways. + +The elements of MLPP signalling are rather simple, hence they are defined using the tabular method described in ITU-T Rec. H.460.1. + +# **2 Introduction** + +This Recommendation applies to H.323 endpoints (including Gateways) and Gatekeepers, and the interactions between them. It may be used with the direct endpoint call signalling model or the gatekeeper-routed model. This Recommendation provides signalling elements that may be used from one end of a call to the other, that is, from a calling endpoint, possibly through one or more Gatekeepers, to a destination endpoint. + +In addition, two types of endpoints may be supported. Functional endpoints (e.g., those supporting H.450-series operations) are expected to support MLPP signalling to the endpoint, and should implement feature negotiation, user interaction, signalling, and timing in the endpoint. Stimulus-driven endpoints (e.g., those supporting Annex L/H.323) may remain ignorant of MLPP since the feature operation and interactions with the user are implemented within the controlling Gatekeeper or feature server. In either case, the elements of MLPP signalling defined herein should be used between Gatekeepers. + +The following configurations are supported by the protocol defined in this Recommendation. It is possible for the various parties involved in an MLPP service to be using different configurations, that is, the following shall interwork. + +## **2.1 Direct Endpoint Signalling** + +The configuration for the Direct Endpoint Signalling is as shown in Figure 1. + +![Diagram showing Direct Endpoint Signalling configuration between Endpoint A and Endpoint B. A solid line labeled H.460.14 connects the two endpoints for signalling. A dashed line labeled Media connects the two endpoints for media flow. The diagram is labeled H.460.14_F01 in the bottom right corner.](c9d8a18a6137ad054b841d7a614afb48_img.jpg) + +The diagram illustrates a direct endpoint signalling configuration. It features two rectangular boxes, 'Endpoint A' on the left and 'Endpoint B' on the right. A solid horizontal line, representing the signalling path, connects the top of Endpoint A to the top of Endpoint B and is labeled 'H.460.14'. A dashed horizontal line, representing the media path, connects the bottom of Endpoint A to the bottom of Endpoint B and is labeled 'Media'. In the bottom right corner of the diagram area, there is a small label 'H.460.14\_F01'. + +Diagram showing Direct Endpoint Signalling configuration between Endpoint A and Endpoint B. A solid line labeled H.460.14 connects the two endpoints for signalling. A dashed line labeled Media connects the two endpoints for media flow. The diagram is labeled H.460.14\_F01 in the bottom right corner. + +**Figure 1/H.460.14 – Direct Endpoint Signalling configuration** + +This Recommendation describes the signalling required to support this configuration. + +## 2.2 Gatekeeper Routed Signalling + +Gatekeeper Routed Signalling has three cases as shown in Figure 2. + +![Figure 2/H.460.14 – Gatekeeper Routed Signalling configurations. The diagram shows three cases (a, b, and c) of gatekeeper routed signalling between Endpoint A and Endpoint B via Gatekeeper A and Gatekeeper B. A dashed line at the bottom of each case represents the Media path.](990567efebf979be51f56d1150012c9d_img.jpg) + +The diagram illustrates three configurations for Gatekeeper Routed Signalling between Endpoint A and Endpoint B, mediated by Gatekeeper A and Gatekeeper B. A dashed line at the bottom of each configuration represents the Media path. + +- a) Transparent Gatekeeper:** Endpoint A is connected to Gatekeeper A, which is connected to Gatekeeper B, which is connected to Endpoint B. All connections are labeled H.460.14. +- b) Gatekeeper performs exchange functions:** Endpoint A is connected to Gatekeeper A via H.460.14. Gatekeeper A is connected to Gatekeeper B via H.460.14. Gatekeeper B is connected to Endpoint B via H.460.14. +- c) Gatekeeper performs exchange functions – non-standard signalling to endpoint:** Endpoint A is connected to Gatekeeper A via non-standard signalling. Gatekeeper A is connected to Gatekeeper B via H.460.14. Gatekeeper B is connected to Endpoint B via non-standard signalling. + +H.460.14\_F02 + +Figure 2/H.460.14 – Gatekeeper Routed Signalling configurations. The diagram shows three cases (a, b, and c) of gatekeeper routed signalling between Endpoint A and Endpoint B via Gatekeeper A and Gatekeeper B. A dashed line at the bottom of each case represents the Media path. + +**Figure 2/H.460.14 – Gatekeeper Routed Signalling configurations** + +For Configuration a, the Gatekeepers are completely transparent and only route the messages. The signalling between the endpoints is the same as for the Direct Endpoint Signalling case. + +For Configuration b, the Gatekeepers terminate the call signalling messages and perform the exchange functions such as routing and feature interactions. The signalling between each Gatekeeper and its connected Endpoint and between the Gatekeepers is the same as for the Direct Endpoint Signalling case; however, the messages on each portion will be different. + +For Configuration c, the Gatekeepers terminate the call signalling messages and perform the exchange functions such as routing and feature interactions. The signalling between the Gatekeepers is the same as for the Direct Endpoint Signalling case. This Recommendation does not address any non-standard protocol which might be used in Configuration c for communications with the endpoints. + +## 2.3 Decomposed Gateway + +As shown in Figure 19/H.323, an endpoint may be a gateway to the PSTN. It may be decomposed and utilize H.248 signalling as shown in Figure 3. + +![Figure 3/H.460.14 – Decomposed Gateway configuration. This diagram shows a 'Gatekeeper B' connected via H.460.14 to a 'Decomposed Gateway'. The 'Decomposed Gateway' is a dashed box containing an 'MGC' (Media Gateway Controller) and an 'MG' (Media Gateway) connected by H.248. The 'MGC' is connected to the 'Gatekeeper B' via H.460.14. The 'MG' is connected to the 'PSTN' via an 'ISDN PRI'. An arrow points from the 'MG' to the 'PSTN' labeled 'ISDN Signalling Channel ](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Figure 3/H.460.14 – Decomposed Gateway configuration. This diagram shows a 'Gatekeeper B' connected via H.460.14 to a 'Decomposed Gateway'. The 'Decomposed Gateway' is a dashed box containing an 'MGC' (Media Gateway Controller) and an 'MG' (Media Gateway) connected by H.248. The 'MGC' is connected to the 'Gatekeeper B' via H.460.14. The 'MG' is connected to the 'PSTN' via an 'ISDN PRI'. An arrow points from the 'MG' to the 'PSTN' labeled 'ISDN Signalling Channel + +**Figure 3/H.460.14 – Decomposed Gateway configuration** + +This Recommendation does not address the H.248 capabilities which may be required for this configuration. + +## 2.4 H.248 managed devices + +As shown in Figure 20/H.323, H.248 may be used to manage (control) the service operation in an endpoint. In this case, the end device functions as the Media Gateway portion of a decomposed Gateway as shown in Figure 4, but without capabilities related to interworking to other signalling systems. + +![Figure 4/H.460.14 – H.248 managed device. This diagram shows a 'Gatekeeper B' connected via H.460.14 to a 'Gateway' (dashed box). The 'Gateway' contains an 'MGC' (Media Gateway Controller) and an 'H.248 managed device (MG)' connected by H.248. The 'MGC' is connected to the 'Gatekeeper B' via H.460.14. The 'MG' is connected to the 'Media' line. An arrow points to the 'MG' with the text: 'Functions as Gateway in the H.323 architecture. The end user's terminal functions as the MG.'](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +Figure 4/H.460.14 – H.248 managed device. This diagram shows a 'Gatekeeper B' connected via H.460.14 to a 'Gateway' (dashed box). The 'Gateway' contains an 'MGC' (Media Gateway Controller) and an 'H.248 managed device (MG)' connected by H.248. The 'MGC' is connected to the 'Gatekeeper B' via H.460.14. The 'MG' is connected to the 'Media' line. An arrow points to the 'MG' with the text: 'Functions as Gateway in the H.323 architecture. The end user's terminal functions as the MG.' + +**Figure 4/H.460.14 – H.248 managed device** + +This Recommendation does not address the H.248 capabilities which may be required for this configuration. + +## 2.5 Stimulus device + +An endpoint may operate using a stimulus protocol in accordance with Annex L/H.323 as shown in Figure 5 and Figure 21/H.323. The Feature Server functional entity may be associated with, or collocated with, a Gatekeeper. + +![Diagram illustrating stimulus signalling using Annex L/H.323. A box labeled 'Feature Server B or Gatekeeper' is connected to a box labeled 'Stimulus Device B (end-user's terminal)' via a vertical line labeled 'H.225.0 with Annex L/H.323'. A horizontal line labeled 'H.460.14' (with '(as above)' to its left) enters the 'Feature Server B or Gatekeeper' box from the left. A dashed horizontal line labeled 'Media' connects the 'Stimulus Device B' box to the left. The diagram is labeled 'H.460.14_F05' at the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +``` + +graph TD + subgraph Left [ ] + direction TB + H460_14[H.460.14 (as above)] + Media[Media] + end + subgraph Right [ ] + direction TB + FSB[Feature Server B or Gatekeeper] + SD[Stimulus Device B (end-user's terminal)] + FSB ---|H.225.0 with Annex L/H.323| SD + end + H460_14 --- FSB + Media -.- SD + style Left fill:none,stroke:none + style Right fill:none,stroke:none + +``` + +Diagram illustrating stimulus signalling using Annex L/H.323. A box labeled 'Feature Server B or Gatekeeper' is connected to a box labeled 'Stimulus Device B (end-user's terminal)' via a vertical line labeled 'H.225.0 with Annex L/H.323'. A horizontal line labeled 'H.460.14' (with '(as above)' to its left) enters the 'Feature Server B or Gatekeeper' box from the left. A dashed horizontal line labeled 'Media' connects the 'Stimulus Device B' box to the left. The diagram is labeled 'H.460.14\_F05' at the bottom right. + +**Figure 5/H.460.14 – Stimulus signalling using Annex L/H.323** + +This Recommendation does not address the signalling between the Feature Server/Gatekeeper and the Stimulus Device which may be required for this configuration. As described in ITU-T Rec. H.323 for interactions with H.450-services, the Feature Server must terminate the H.460 signalling and handle the MLPP operations described in this Recommendation, while using a stimulus protocol to signal via the terminal to the user as described in Annex L/H.323. + +# 3 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is published regularly. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.245 (2003), *Control protocol for multimedia communication*. +- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*. +- ITU-T Recommendations of the H.450.x series, *Supplementary services for multimedia*. +- ITU-T Recommendation H.460.1 (2002), *Guidelines for the Use of the Generic Extensible Framework*. + +# 4 Definitions + +This Recommendation defines the following terms: + +**4.1 alternate party:** A third party to whom an MLPP call may be diverted if it is not accepted or acknowledged by the called user. + +**4.2 diversion:** The operation in which a precedence call is redirected to a pre-assigned alternate party due to (in)action by the called party. + +**4.3 preemption:** The act of forcibly removing a connection in order to free up facilities for another higher-precedence call. + +**4.4 preemption in progress:** The period of time after a party is notified that their existing call is going to be preempted until the preemption actually occurs and is completed by the intended party acknowledging the action. + +- 4.5 served user, user A:** The user who requests to originate a call using MLPP (calling user). +- 4.6 user B:** The wanted user that is subject to the call preemption (called user). +- 4.7 user C:** The other user in the established call, also referred to as the unwanted user. + +# **5 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|------|---------------------------------------| +| ACF | Admission confirmation | +| ARJ | Admission rejection | +| ARQ | Admission request | +| DCF | Disengage confirmation | +| DRQ | Disengage request | +| GCF | Gatekeeper confirmation | +| GK | Gatekeeper | +| GRQ | Gatekeeper request | +| LCF | Location confirmation | +| LRJ | Location rejection | +| LRQ | Location request | +| MLPP | Multi-level precedence and preemption | +| RAS | Registration, admission and status | +| RCF | Registration confirmation | +| RRJ | Registration rejection | +| RRQ | Registration request | + +# **6 Multi-level Precedence and Preemption Service description** + +The basic requirements for MLPP are the ability of call processing equipment to signal the precedence of each call, and for each entity (Gatekeeper, Gateway, or endpoint) which handles a call to properly manage resources for that call according to its precedence. This may well include the termination (preemption) of one or more active calls of lower precedence. + +## **6.1 Provision of precedence levels** + +A maximum precedence level shall be allocated to each user, which shall have a value in the range from 4 (lowest level) to 0 (highest level). Each user shall be provided with a means to select a precedence for each call originated, not greater than the maximum allocated. If a precedence level is not explicitly selected for a call, the lowest value (4) shall be used. All five of the precedence level values shall be supported. + +The Precedence levels are referred to as: + +- 0 Flash Override +- 1 Flash +- 2 Immediate +- 3 Priority +- 4 Routine + +The procedures by which the maximum precedence level is allocated to a user and the criteria by which a user chooses a value of precedence level for a particular call are outside the scope of this Recommendation. + +## **6.2 Preemption of facilities** + +This Recommendation provides a means to identify the priority (precedence) of individual calls as they move through the network. It also defines signalling procedures for handling such calls when resource conflicts arise in the network or at an endpoint. When a facility (network bandwidth or endpoint hardware) is busy, and a call of higher precedence requires that facility, the facility may be preempted by termination of the existing call and establishment of the preempting call. If the facility is an endpoint under the control of a user, the user shall be notified of the presence of a preempting call, and must take action to accept the new call. When a call is preempted, special indication shall be given to all parties of that call to indicate that fact. + +The decision to preempt a call is taken automatically by the call processing equipment and does not require any specific action of the called user. The details of how the existence of a precedence call or impending preemption is presented to the end user, or how the user indicates which actions to take, are beyond the scope of this Recommendation. + +## **6.3 Diversion** + +A precedence call may be redirected (diverted) if an endpoint does not accept it within a specified time interval. The redirecting entity may indicate the new destination for the call. + +## **6.4 Interactions with other services** + +Interactions with specific Supplementary Services defined in the H.450-series of Recommendations shall be as follows. + +### **6.4.1 Call Transfer (CT)** + +User A shall not be able to invoke CT during the preemption in progress state on that call. (This is similar to the CT requirement that the call being transferred shall be answered before transfer can be initiated.) While performing CT, a user shall be allowed to invoke MLPP on the transfer request. + +User B shall not be able to invoke CT during the preemption in progress state on the preempting call, that is, the call cannot be transferred until after the preemption is acknowledged and the new connection is established. + +User C may be able to transfer an established call during preemption. In all cases, the transferred-to user that becomes connected to user B shall become the new user C, and shall receive all future notifications accordingly. + +### **6.4.2 Call Forwarding Unconditional (CFU)** + +At User A: No service interaction. + +At User B: If CFU is active when a call using MLPP arrives, CFU shall take precedence, i.e., the call shall be forwarded regardless of the precedence level of the call. If a call with a precedence level higher than the lowest is forwarded and is not responded to by any forwarded party, then the alternate party option of MLPP (using the alternate party of the original called party) shall apply. + +However, if the network element controlling the call forwarding is aware that it is being used to forward to a voice mail system, it should apply the MLPP alternate party diversion instead of the Call Forwarding Unconditional. + +At User C: No service interaction. + +The precedence level of a call shall be preserved during the forwarding process. At the final diverted-to user (using CFB, CFU, or MLPP diversion), MLPP shall operate if that user is busy. However, if either CFNR or Call Deflection has taken place, the optional alternate party diversion shall not occur. + +### **6.4.3 Call Forwarding Busy (CFB)** + +At User A: No interaction. + +At User B: When a call using MLPP (with a precedence level greater than the lowest) arrives when User B is busy and has CFB active, the following order of preference shall apply: + +- If the new call is of equal or lower precedence, or preemption is not possible for some other reason, CFB shall apply. +- If the new call is of higher precedence than an existing call, MLPP shall apply, i.e., preemption shall be used. +- If no answer is received for the CFB attempt, the alternate party option, if subscribed, shall apply. That is, the alternate party timer shall be used. If not subscribed, the normal failure procedures of CFB shall apply. + +However, if the network element controlling the call forwarding is aware that it is being used to forward to a voice mail system, it should apply the MLPP alternate party diversion instead of the Call Forwarding Busy. + +The precedence level of a call shall be preserved during the forwarding process. At the final diverted-to user (using CFB, CFU, or MLPP diversion), MLPP shall operate if that user is busy. However, if either CFNR or Call Deflection has taken place, the optional alternate party diversion shall not occur. + +### **6.4.4 Call Forwarding on No Reply (CFNR)/Call Deflection (CD)** + +At User A: No interaction + +At User B: When a call using MLPP (with a precedence level greater than the lowest) arrives and User B does not answer, the following shall apply: + +- CFNR takes precedence over the Alternate Party. +- If the forwarded call is not responded to by any forwarded-to party within a specified period of time, the call shall then be diverted using the Alternate Party capability. + +However, if the network element controlling the forwarding is aware that it is being used to forward to a voice mail system, it should apply the MLPP alternate party diversion instead of the Call Forwarding No Reply. + +The precedence level of a call shall be preserved during the forwarding process. If either CFNR or Call Deflection has already taken place on the call, the optional alternate party diversion shall not occur. + +### **6.4.5 Call Hold** + +At User A: There are no additional restrictions on Call Hold other than those defined for the CH service. + +At User B: The preempting call shall not be put on hold. After it has been acknowledged and connected, it may be placed on hold. User B may put the established call to User C on hold as a means of becoming not busy. + +### **6.4.6 Call Park** + +At User A: No service interaction. + +At User B: It shall not be possible to park the preempting call until after it has been acknowledged and connected. User B may park the established call to User C as a means of becoming not busy. + +### **6.4.7 Call Pickup** + +At User A: No service interaction. + +At User B: MLPP shall take precedence over Call Pickup, i.e., if User B is busy, preemption shall occur rather than allowing others in the pickup group to retrieve the call. If User B is not busy, the call shall be placed in the pickup group and any member of that pickup group may answer it. If there is more than one call in the unanswered condition, a pickup attempt shall retrieve the one with the highest precedence level and, within a single level, the one which has been alerting the longest. + +### **6.4.8 Call Waiting** + +At User A: No service interaction. + +At User B: If a new call arrives for which MLPP is invoked and CW is subscribed, the interaction shall be as follows: + +- If the new call is a higher precedence level than an existing call and preemption is possible, MLPP shall be used. +- If the new call is not a higher precedence level or User B is non-preemptable, CW shall be used. + +### **6.4.9 Message Waiting Indication** + +No service interaction. + +### **6.4.10 Name Identification** + +No service interaction. + +### **6.4.11 Completion of Calls on Busy (CCBS)** + +At User A: It shall be possible to invoke MLPP with CCBS, that is, to specify a precedence level on a CCBS invocation. + +At User B: If both MLPP invocation and CCBS are requested in the same call setup request, MLPP shall take precedence at User B, that is, an existing call will be preempted if possible. If not, the alternate party procedures shall be applied. If there is no alternate party specified, then CCBS shall apply. If the limit of number of calls waiting for CCBS has been reached, the new MLPP call may preempt an existing waiting call that is, take its place in the CCBS queue. + +### **6.4.12 Completion of Calls on No Reply (CCNR)** + +At User A: It shall be possible to invoke MLPP with CCNR, that is, to specify a precedence level on a CCNR invocation. + +At User B: If both MLPP and CCNR are requested in the same call setup request, MLPP shall take precedence at User B, that is, the alternate party procedures shall be applied. If there is no alternate party specified, then CCNR shall apply. + +### **6.4.13 Call Offer (CO)** + +At User A: It shall be possible to request both CO and MLPP in the same call setup request. + +At User B: If both MLPP invocation and CO invocation are requested at call set up, precedence shall be given to the MLPP service. + +### 6.4.14 Call Intrusion + +At User A: Call Intrusion and MLPP should not be requested in the same call setup request. + +At User B: If a request for both Call Intrusion and MLPP is received in the same call setup request, the MLPP request shall take precedence. + +### 6.4.15 Common information + +At User A: By exchange of Common Information data, User A may have a priori knowledge of the MLPP capabilities at the called endpoint, e.g., the precedence level of existing calls at User B. + +# 7 Signalling elements for MLPP + +The following tables define the required signalling elements and parameters for MLPP utilizing the Generic Extensible Framework of H.323. The elements are defined in such a way that the MLPP capabilities may be easily extended by the definition of new parameters and no new ASN.1 definitions in ITU-T Rec. H.225.0 are required. + +These parameters may be used in: + +- H.501 Access Request and Service Request messages to perform inter-administrative domain address resolution and service negotiation. +- H.225.0 RAS messages to perform intra-domain address resolution and service negotiation. +- H.225.0 Call Signalling messages to control call setup. + +## 7.1 Feature identifier + +The feature identifier value in Table 1 is used to identify the feature in both the **featureSet** elements of H.225.0 and the **genericData** elements of H.225.0. + +**Table 1/H.460.14 – MLPP feature identifier** + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Feature name: | Multi-Level Precedence and Preemption (MLPP) | +| Feature description: | This feature provides the ability to associate a precedence level with each call, and to signal the preemption of facilities, based on relative call precedences. | +| Feature identifier type: | Standard | +| Feature identifier value: | 14 | + +The **featureSet** element provides the ability for an endpoint or Gatekeeper to indicate whether a feature is required (i.e., service cannot be provided without support for the feature), desired (i.e., the feature will be used if available), or supported (i.e., the feature will be used if the other party so desires) by that endpoint or Gatekeeper. An indication that a feature is required or desired implicitly indicates support. When used in the discovery/registration request/confirm messages (GRQ, GCF, RRQ, and RCF), the MLPP feature shall be specified as "required" or "desired". In all other messages, it shall be specified as "desired" or "supported". MLPP shall not be indicated as a "required" feature in ARQ, LRQ, or Setup because it is better to propagate the call without MLPP support than to have it blocked due to non-support. + +The **genericData** is used to carry the MLPP parameters for a particular endpoint registration. It also provides the ability for an endpoint or Gatekeeper to indicate (in ARQ, LRQ, and Setup) that the MLPP feature is being used for a particular call. It implies support by the entity sending the message. + +## 7.2 Parameter + +This parameter is used to transport information between signalling entities within the MLPP **GenericData** element of requests and responses. In this Recommendation, "MLPP GenericData element" means a GenericData element which contains the MLPP feature identifier defined in Table 1. + +**Table 2/H.460.14 – MLPP information parameter** + +| | | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | MLPP Information | +| Parameter description: | This is the data sent in H.225.0 RAS and Call Signalling messages to indicate the use of MLPP. The contents is a raw field consisting of the ASN.1 encoded MLPPInfo as specified in Annex A. It shall be encoded in the basic aligned variant PER. | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 1 | +| Parameter type: | raw | +| Parameter cardinality: | Once and only once | + +The MLPP information definition used within the MLPP information parameter in the GenericData is shown in Annex A. + +# 8 Procedures + +The elements defined above may be employed in several ways to effect the desired call behaviours under MLPP when operating with the direct endpoint call signalling or the gatekeeper-routed model. + +## 8.1 Registration, Admission and Status (RAS) + +### 8.1.1 Gatekeeper discovery + +When an endpoint attempts to find its Gatekeeper by sending a GatekeeperRequest (GRQ), it may include the **featureSet** element to indicate that it requires or desires support for MLPP. Each Gatekeeper that supports MLPP should respond with a Gatekeeper Confirm (GCF) containing a **featureSet** element which indicates support for MLPP. If the endpoint has not indicated support for MLPP, but the Gatekeeper requires it, the Gatekeeper may reply with GCF, but should indicate the requirement therein. If a Gatekeeper indicates that MLPP is required and the endpoint cannot support it, the endpoint should not attempt to register to that Gatekeeper. + +### 8.1.2 Registration + +When the endpoint registers (sends RRQ), it may include the **featureSet** element to indicate its support for MLPP. The Gatekeeper may respond with RCF if it can provide compatible support, but it shall reject the registration (with an RRJ) if it (the Gatekeeper) requires MLPP support by the endpoint and the endpoint does not indicate support. + +### 8.1.3 Call Admission Control (CAC) + +H.323 supports two types of call admission: ARQ/ACF/ARJ for endpoint-to-Gatekeeper signalling, and LRQ/LCF/LRJ for inter-Gatekeeper signalling. Both sequences are defined as part of RAS, not as part of call signalling, and are quite similar. If a Gatekeeper is to monitor consumption of resources, the use of RAS is necessary in the direct endpoint call-signalling model. It is also useful in the Gatekeeper-routed model, especially between Gatekeepers. Even though any Gatekeeper in the route could simply refuse the Setup request, it is more efficient to reject an ARQ or LRQ. The CAC mechanisms may be illustrated with an MLPP call from endpoint A on Gatekeeper A to + +endpoint B on Gatekeeper B using the direct endpoint call-signalling model. This assumes all parties support MLPP. + +In addition, the Access Request procedures defined in Annex G/H.225.0 may be used for inter-administrative domain address resolution. The parameters defined in this Recommendation may be included in the H.501 Messages. + +Admission may be pre-granted at the time of registration. + +#### **A Direct Endpoint Call Signalling example** + +The first may be illustrated with an MLPP call from endpoint A on Gatekeeper A to endpoint B on Gatekeeper B using the direct endpoint call signalling model. + +- 1) Endpoint A sends ARQ to Gatekeeper A, indicating endpoint B in the **destinationInfo** element and including an MLPP **genericData** element containing **precedence** with the desired value (2 for Immediate in this example). +- 2) Gatekeeper A examines the ARQ, and, if the request is allowed, replies with an ACF message. Gatekeeper A replies to endpoint A with ARJ if no facilities are available for calls of the requested precedence of 2. In that case, the ARJ contains an MLPP **genericData** element containing **mlppReason** with value 46 (callBlocked). The basis for this decision is beyond the scope of this Recommendation. +- 3) Endpoint A then establishes a call signalling channel to the address specified in the ACF (endpoint B's address in the direct endpoint call signalling model) and sends a Setup message to endpoint B as described in 8.2.1 containing an MLPP **genericData** element and **precedence** with value 2. +- 4) If endpoint B supports MLPP and is unable to accept the call (e.g., if it is busy with a higher precedence call), it applies the alternate party procedures if possible. Otherwise, it refuses the call by sending a Release Complete message containing a **reason** of **genericDataReason**, along with an MLPP **genericData** element with **mlppReason** with value 46 (CallBlocked) as described in 8.2.2.2. + +If endpoint B does not support MLPP and is unable to accept the call (e.g., it is busy), then it refuses the call by sending a Release Complete containing a **reason**, e.g., unreachable destination, without the MLPP **genericData** element. + +- 5) If endpoint B is able to accept the offer of the call, it sends an ARQ to Gatekeeper B to gain permission. The ARQ contains an MLPP **genericData** element with **precedence** with the desired value (2 in this example). +- 6) If Gatekeeper B wishes to disallow the call due to precedence restriction, it returns an ARJ with an MLPP **genericData** element containing **mlppReason** with value 46 (call Blocked). The ARJ may contain an **alternateParty** structure. Endpoint B then sends a Release Complete back to endpoint A containing an MLPP **genericData** element with **mlppReason** with value 46 (callBlocked) and **alternateParty** as described in 8.2.2.2. If the call is rejected for some other reason, that reason is indicated by Gatekeeper B in **admissionRejectReason** and mapped back to the **releaseCompleteReason** returned to endpoint A, as appropriate. +- 7) If Gatekeeper B wishes to permit the call, it returns an ACF to endpoint B. If Gatekeeper B is able to identify a call that should be preempted, as might be the case if endpoint B is a trunk Gateway, this ACF contains an MLPP **genericData** element with a **releaseCall** structure which contains B, **releaseReason** set to 9 (preemption – facility reserved), and optionally **releaseDelay**. The Gatekeeper may also include the **alternateParty** structure if an alternate party is designated for endpoint B. + +- 8) At this point, endpoint B is able to accept the call from endpoint A. If endpoint B is busy with another call that needs to be preempted, it carries out the release procedures prior to accepting the call from endpoint A by sending a Release Complete as described in 8.2.2.1. The first response it sends to endpoint A contains a **featureSet** which indicates whether or not endpoint B supports MLPP. + +#### **B Gatekeeper-routed example** + +If the above call were to be Gatekeeper-routed, then the following sequence would be used (assuming that discovery and registration were already done and admission was pre-granted during registration so that ARQ/ACF sequences are not used.) + +- 1) Endpoint A sends a Setup to its Gatekeeper A, containing an MLPP **genericData** element containing **precedence** with the desired value (2 for Immediate, for example). +- 2) If Gatekeeper A cannot support the call at the indicated precedence, it returns a Release Complete with **reason** set to **genericDataReason**, along with an MLPP **genericData** element with **mlppReason** with value 46 (callBlocked). +- 3) If Gatekeeper A is able to support the call, it routes the call toward the destination via facilities that can admit a call of the indicated precedence (e.g., the precedence may be used to favour facilities that can support precedence over others that do not). + +If Gatekeeper A does not know which Gatekeeper will perform the function of Gatekeeper B for this call, it sends an LRQ message via multicast. If Gatekeeper A already knows the identity of the desired Gatekeeper B but not its signalling address, Gatekeeper A sends an LRQ message to Gatekeeper B on its RAS Channel TSAP Identifier. If Gatekeeper A already knows the identity and call signalling address of Gatekeeper B, it may send the Setup to it without first using the LRQ sequence. + +In any of the above three cases, the LRQ or Setup message contains an MLPP **genericData** element containing **precedence** with the desired value (2 for Immediate in this example). + +- 4) When Gatekeeper B receives the LRQ, it determines whether or not it is able to admit a call based on the indicated precedence, and responds back to Gatekeeper A with an LCF if it is able, as defined in 7.2.3/H.323. If Gatekeeper B cannot support the call, it returns an LRJ message with an MLPP **genericData** element containing **mlppReason** with value 46 (callBlocked) or the appropriate **locationRejectReason** (e.g., **invalidPermission**). + +When Gatekeeper A receives the LRJ, it may attempt to route the call in a different manner, e.g., via a different Gatekeeper. If not, it returns a Release Complete to endpoint A with **reason** set to **genericDataReason**, along with an MLPP **genericData** element with **mlppReason** with value 46 (callBlocked). + +- 5) When Gatekeeper A receives the LCF (with a call signalling address for Gatekeeper B and **featureSet** indicating support for MLPP), it sends a Setup message to that address containing an MLPP **genericData** element containing **precedence** with a value 2 (in this example) as described in 8.2.1. +- 6) When Gatekeeper B receives the Setup for the call, its actions depend on whether or not the intended endpoint B supports MLPP, which the Gatekeeper determined during registration. + +If endpoint B supports MLPP, Gatekeeper B sends a Setup to endpoint B and endpoint B performs the functions as described in 8.2.2. The Setup may contain the **releaseCall** structure if there is a call for endpoint B to preempt first and it may contain the **alternateParty** structure if an alternate party is assigned in case user B does not accept the precedence call. + +If endpoint B does not support MLPP, Gatekeeper B first performs any required preemption by sending a Release Complete on the call to be preempted, then sends a Setup, and provides timing for the alternate party as described in 8.2.2. + +### 8.1.4 Call establishment and preemption + +If a Gatekeeper receives a request to establish an MLPP call of a certain precedence, it may be necessary to terminate another call of lower precedence. This may be done by either a Gatekeeper or an endpoint. When terminating a call via a Release Complete, the terminating endpoint or Gatekeeper shall set the **reason** to **genericDataReason** and shall include an MLPP **genericData** element with **mlppReason** set to either 8 (to release all facilities) or 9 (to maintain facility reservations). + +## 8.2 Call signalling procedures for H.450 endpoints + +The procedures described in this clause apply to an endpoint using functional signalling, which is intended for endpoints which provide other Supplementary Services in accordance with the H.450-series of Recommendations. + +These procedures require that the signalling channel for each call be maintained throughout the duration of the call. They also presume that the appropriate RAS procedures (discovery, registration and admission) are performed in the same way as for normal calls, with the addition of the indication of support for MLPP and the precedence level in the RAS messages. RAS actions are not included in this description, but are described in 8.1 and in ITU-T Rec. H.323. + +While the text of this clause is written assuming the direct endpoint call signalling case, the actions stated for the endpoints may instead be performed by their Gatekeepers in the Gatekeeper-routed case. Further, the same signalling may be used between Gatekeepers and endpoints. + +### 8.2.1 Actions at user A's endpoint + +#### 8.2.1.1 Normal procedure + +To invoke MLPP for a new call, endpoint A shall perform the following actions (after any required RAS signalling as described in 8.1): + +- Send a Setup message containing an MLPP **genericData** element with **precedence**, and enter state MLPP-Wait-Ack. The **precedence** shall convey the precedence level requested by the calling user. + +In state MLPP-Wait-Ack, on receipt of a Connect message, endpoint A shall enter state MLPP-Idle. Establishment of media channels shall follow normal H.323 procedures. Normal call timers shall apply. + +#### 8.2.1.2 Exceptional procedure + +In state MLPP-Wait-Ack, on receipt of a Release Complete message with or without any MLPP specific error, the MLPP call setup has failed and endpoint A shall enter state MLPP-Idle. + +Failure of MLPP should be indicated to the calling user and the call shall continue in accordance with basic call procedures. + +#### 8.2.1.3 Procedure for completion of MLPP + +In state MLPP-Wait-Ack, on receipt of Connect, either with or without an MLPP **genericData** element, the state MLPP-Idle shall be entered. If a **genericData** element contains **mlppNotification** with value **preemptionComplete**, the user at endpoint A shall be provided an indication of this. + +#### 8.2.1.4 Optional procedures for invocation of MLPP + +In state MLPP-Wait-Ack, multiple Alerting messages may be received in the case of alternate party diversion at user B's endpoint. No further actions are required at user A's endpoint. + +### **8.2.2 Actions at user B's endpoint** + +#### **8.2.2.1 Normal procedure** + +If, while processing an incoming Setup message containing an MLPP **genericData** element with **precedence**, the called user is found to be busy, endpoint B shall check whether the called user is involved in a compatible active call (in the following, referred to as the "established call"), that the precedence level of that call is lower than the precedence level of the received call, and that there are no other reasons for denying preemption (e.g., if the established call is already being preempted or a requested option cannot be supported). + +NOTE – The method by which endpoint B checks whether an active call is compatible with the new precedence call is outside the scope of this Recommendation. + +If all conditions are met, endpoint B shall provide a notification of an impending preemption to the involved users. Endpoint B shall send on the established call (in a Facility message) and optionally also on the preempting call (in an Alerting message if possible, otherwise in a Progress or Facility message) an MLPP **genericData** element with **mlppNotification** set to value **preemptionPending**, shall start timer T6, and shall enter state MLPP-Dest-Notify. If endpoint B also provides a preemption warning tone, a Progress indicator information element with progress descriptor #8, *In-band information or an appropriate pattern is now available*, should be included in the Alerting or Progress message. If endpoint B does not provide tones, a Facility message should only be used. Execution of preemption shall commence on expiry of timer T6 in state MLPP-Dest-Notify. + +#### **8.2.2.2 Exceptional procedure** + +On receipt of a Setup message containing an MLPP **genericData** element with **precedence**, if the called user is not busy, the call shall continue according to basic call procedures, that is, endpoint B shall return normal Call Proceeding, Alerting, or Connect messages not containing any MLPP **genericData** element and shall remain in state MLPP-Idle. + +If the called user is busy but invocation of MLPP is not possible (including the case where the precedence level of all calls at user B is too high), the preempting call shall be released. Endpoint B shall include an MLPP **genericData** element with **mlppReason** containing value 46 (callBlocked) in the Release Complete message and shall remain in state MLPP-Idle. + +If, in the case of a normal preemption request during state MLPP-Dest-Notify, the called user becomes not busy and presentation of the preempting call becomes possible, normal call processing messages shall be returned to endpoint A, that is, Alerting, Connect, or Facility message, timer T6 shall be stopped, and state MLPP-Idle shall be entered. + +Upon expiry of timer T6, endpoint B shall send a Release Complete message to endpoint C containing a **reason** of **genericDataReason** and an MLPP **genericData** element with **mlppReason** set to 8 (preemptionNoReservation). If an ARQ had been sent when this call was originally set up, endpoint B shall also send a DRQ to the Gatekeeper containing a **disengageReason** of **forcedDrop**, a **terminationReason** containing a **releaseCompleteReason** of **GenericDataReason**, and an MLPP **genericData** element with **mlppReason** containing value 9 (preemptionReservation). + +#### **8.2.2.3 Procedures for completion of MLPP** + +If the preempting call is released in any state, endpoint B shall enter state MLPP-Idle and stop any MLPP timer. If release occurs during state MLPP-Dest-Notify, the established call shall be restored to the state that existed prior to preemption and a Facility message containing an MLPP **genericData** element with **mlppNotification** set to value **preemptionEnd** shall be sent on the established call. + +### 8.2.3 Actions at user C's endpoint + +On receipt of a Facility message on an existing call containing an MLPP **genericData** element with **mlppReason** set to value 8 or 9, endpoint C may indicate the preemption status information to user C. It takes no other action. + +On receipt of a Release Complete message, endpoint C releases the call with normal notification to the user. If the Release Complete contains the MLPP **genericData** element with **mlppReason** set to 8, endpoint C should notify the user of this. + +# 9 Dynamic description + +This clause provides a dynamic description of the operation of MLPP corresponding to the procedures described in 8.2 for the functional signalling case. It describes two cases: + +- Direct endpoint call signalling model with endpoints directly exchanging functional signalling (without intervention by a Gatekeeper); +- Gatekeeper-routed model, with Gatekeepers exchanging functional signalling and performing service operations and signalling to endpoints via non-standardized (maybe stimulus) signalling. + +The case of fully functional signalling between Gatekeepers as well as from Gatekeepers to endpoints is thereby possible using the procedures shown for the above two cases. + +## 9.1 Operational model + +Figure 6 shows the functional model for successful MLPP before and after MLPP invocation. + +![Figure 6/H.460.14 – Operational model for MLPP. The diagram shows four states: State 1 (Before service), State 2 (During preemption), State 3 (After preemption), and State 4 (After service). State 1 shows Endpoint A (idle), Endpoint B (busy), and Endpoint C (busy) with a call between B and C. State 2 shows Endpoint A (waiting), Endpoint B (notified), and Endpoint C (notified) with a call between B and C continuing while A-to-B call waits. State 3 shows Endpoint A (waiting), Endpoint B (notified), and Endpoint C (released) with a call between B and C preempted by pending call from A. State 4 shows Endpoint A (busy), Endpoint B (busy), and Endpoint C (idle) with a call between A and B in progress.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +State 1: Before service. Endpoint A (idle), Endpoint B (busy), Endpoint C (busy). (B-C call in progress) + +State 2: During preemption. Endpoint A (waiting), Endpoint B (notified), Endpoint C (notified). (B-C call continues while A-to-B call waits) + +State 3: After preemption. Endpoint A (waiting), Endpoint B (notified), Endpoint C (released). (B-C call is preempted by pending call from A) + +State 4: After service. Endpoint A (busy), Endpoint B (busy), Endpoint C (idle). (A-B call in progress) + +H.460.14\_F06 + +Figure 6/H.460.14 – Operational model for MLPP. The diagram shows four states: State 1 (Before service), State 2 (During preemption), State 3 (After preemption), and State 4 (After service). State 1 shows Endpoint A (idle), Endpoint B (busy), and Endpoint C (busy) with a call between B and C. State 2 shows Endpoint A (waiting), Endpoint B (notified), and Endpoint C (notified) with a call between B and C continuing while A-to-B call waits. State 3 shows Endpoint A (waiting), Endpoint B (notified), and Endpoint C (released) with a call between B and C preempted by pending call from A. State 4 shows Endpoint A (busy), Endpoint B (busy), and Endpoint C (idle) with a call between A and B in progress. + +**Figure 6/H.460.14 – Operational model for MLPP** + +NOTE – As defined in clause 4, "Preemption in Progress" includes states 2 and 3 in Figure 6. + +## 9.2 Signalling flows + +This clause describes some typical message flows for MLPP. The following conventions are used in the figures of this clause. + +The following notation is used: + +![Legend for sequence diagram symbols Timer that expires symbol Timer that is stopped before it expires symbol](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +—————> Call-related protocol message (mandatory with regard to MLPP) + · — · — · — · — · —> Call-related protocol message (optional with regard to MLPP) + +Timer that expires      Timer that is stopped before it expires + +SETUP      H.225.0 message name + Cx          Number of connection x + +H.460.14\_F9.2 + +Legend for sequence diagram symbols Timer that expires symbol Timer that is stopped before it expires symbol + +### 9.2.1 Successful MLPP – direct endpoint call signalling + +Figures 7 and 8 show example signalling flows for a successful MLPP invocation and operation for the direct endpoint call signalling case. + +![](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant A as User A's endpoint + participant G as Gatekeeper(s) + participant B as User B's endpoint + participant C as User C's endpoint + + Note over A: Idle + Note over B, C: Active call (C1) + A->>G: ARQ (C2) precedence = na) + G->>A: ACF (C2) destCallSignalAddress = B + A->>B: SETUP (C2) precedence = na) + B->>G: ARQ (C2) precedence = na) + G->>B: ACF (C2) releaseCall (C1) + B->>A: ALERTING (C2) mlppNotification = preemptionPending + B->>C: FACILITY (C1) mlppNotification = preemptionPending + Note right of B: T6 starts + B->>C: REL COM (C1) mlppReason = 8 (preemptionNoReservation) + Note over C: Idle + G-->>B: DRQ (C1) (if required) + B-->>G: DCF (C1) (if required) + Note right of B: T7 starts + B->>A: CONNECT (C2) mlppNotification = preemptionComplete + Note left of B: Acknowledge preemption + Note over A, B: Active call (C2) + +``` + +The diagram shows the message exchange for a successful MLPP call from User A to User B, which results in the preemption of an existing call between User B and User C. User A starts in an Idle state. User B and C are in an Active call (C1). User A sends an ARQ for connection C2 with precedence level *n* to the Gatekeeper, which responds with an ACF. User A then sends a SETUP message to User B. User B requests admission (ARQ) from the Gatekeeper, which responds with an ACF and a command to release the existing call (releaseCall (C1)). User B sends an ALERTING message to User A and a FACILITY message to User C, both indicating preemption is pending. Timer T6 is started. User B then sends a REL COM message to User C with reason code 8. Gatekeeper interactions (DRQ/DCF) for releasing C1 occur if required. Timer T7 is started. Finally, User B sends a CONNECT message for C2 to User A, indicating preemption is complete. User A and B are now in Active call (C2), and User C is Idle. + +NOTE – Endpoints A and B may send the ARQs/DRQs to different Gatekeepers. +a) n = 0 .. 4 + +H.460.14\_F07 + +**Figure 7/H.460.14 – Example message flow for successful MLPP – direct endpoint call signalling, established call preempted** + +![Sequence diagram illustrating the message flow for successful MLPP – direct endpoint call signalling, with timeout of acknowledgement and diversion. It shows interactions between User A, User B, User C, and Diverted-to User D.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +sequenceDiagram + participant A as User A's endpoint + participant B as User B's endpoint + participant C as User C's endpoint + participant D as Diverted-to User's Endpoint (D) + + Note over A: Idle + Note over B,C: Active call (C1) + + A->>B: SETUP (C2) +precedence = na) + Note left of A: T303 + B->>C: FACILITY (C1) +mlppNotification = preemptionPending + Note right of B: T6 + B->>A: ALERTING (C2) +mlppNotification = preemptionPending + B->>C: REL COM (C1) +mlppReason = 8 (preemptionNoReservation) + Note right of B: T7 + Note over C: Idle + B->>A: FACILITY (C2) +CallRerouting.Invoke + A->>B: FACILITY (C2) +CallRerouting.ReturnResult + Note over D: Idle + A->>D: SETUP (C3) +precedence = na) + Note left of A: T303 + D->>A: ALERTING (C3) + A->>B: REL COM (C2) +mlppNotification = preemptionEnd + Note over B: Idle + D->>A: CONNECT (C3) + Note over A,D: Active call (C3) A to D + +``` + +Sequence diagram illustrating the message flow for successful MLPP – direct endpoint call signalling, with timeout of acknowledgement and diversion. It shows interactions between User A, User B, User C, and Diverted-to User D. + +H.460.14\_F08 + +a) n = 0 .. 4 + +RAS signalling not shown – same as previous figure + +**Figure 8/H.460.14 – Example message flow for successful MLPP – direct endpoint +call signalling, with timeout of acknowledgement and diversion** + +### 9.2.2 MLPP call without preemption – direct endpoint call signalling + +Figures 9 and 10 show example signalling flows for MLPP invocation to an idle endpoint in the direct endpoint call signalling case. (It should be emphasized that, in the case shown in Figure 9, although the MLPP service is considered "unsuccessful" from the protocol viewpoint, the call setup is successful from the service operation viewpoint.) + +![Sequence diagram showing message flow for MLPP call without preemption. Lifelines: User A's endpoint, Gatekeeper(s), User B's endpoint. The sequence starts with both endpoints in an 'Idle' state. User A sends an ARQ (C2) with precedence = n^a) to the Gatekeeper. The Gatekeeper responds with an ACF (C2) containing destCallSignalAddress = B. User A then sends a SETUP (C2) with precedence = n^a) directly to User B. User B responds with an ARQ (C2) with precedence = n^a) to the Gatekeeper. The Gatekeeper responds with an ACF (C2) to User B. User B then sends an ALERTING/CONNECT (C2) message to User A. An 'etc.' label is present below the ALERTING/CONNECT message. At the bottom, a horizontal bar labeled 'Active call (C2)' spans both User A's and User B's lifelines. The diagram is labeled H.460.14_F09 in the bottom right corner.](366a77fdefb0097b3289b4a011911390_img.jpg) + +``` +sequenceDiagram + participant User A's endpoint + participant Gatekeeper(s) + participant User B's endpoint + + Note left of User A's endpoint: Idle + Note right of User B's endpoint: Idle + + User A's endpoint->>Gatekeeper(s): ARQ (C2) +precedence = na) + Gatekeeper(s)-->>User A's endpoint: ACF (C2) +destCallSignalAddress = B + User A's endpoint->>User B's endpoint: SETUP (C2) +precedence = na) + User B's endpoint->>Gatekeeper(s): ARQ (C2) +precedence = na) + Gatekeeper(s)-->>User B's endpoint: ACF (C2) + User B's endpoint->>User A's endpoint: ALERTING/CONNECT (C2) + Note right of Gatekeeper(s): etc. + Note bottom: Active call (C2) +``` + +Sequence diagram showing message flow for MLPP call without preemption. Lifelines: User A's endpoint, Gatekeeper(s), User B's endpoint. The sequence starts with both endpoints in an 'Idle' state. User A sends an ARQ (C2) with precedence = n^a) to the Gatekeeper. The Gatekeeper responds with an ACF (C2) containing destCallSignalAddress = B. User A then sends a SETUP (C2) with precedence = n^a) directly to User B. User B responds with an ARQ (C2) with precedence = n^a) to the Gatekeeper. The Gatekeeper responds with an ACF (C2) to User B. User B then sends an ALERTING/CONNECT (C2) message to User A. An 'etc.' label is present below the ALERTING/CONNECT message. At the bottom, a horizontal bar labeled 'Active call (C2)' spans both User A's and User B's lifelines. The diagram is labeled H.460.14\_F09 in the bottom right corner. + +a) n = 0 . . 4 + +H.460.14\_F09 + +**Figure 9/H.460.14 – Example message flow for unsuccessful MLPP – +direct endpoint call signalling with User B not busy** + +![Sequence diagram for Figure 10/H.460.14 showing an unsuccessful MLPP call. Lifelines: User A's endpoint, Gatekeeper(s), User B's endpoint, User C's endpoint. The sequence starts with User A in an Idle state. User A sends an ARQ (C2) with precedence = n^c) to the Gatekeeper. The Gatekeeper responds with an ACF (C2) with destCallSignalAddress = B. User A then sends a SETUP (C2) with precedence = n^c) to User B. User B sends an ARQ (C2) with precedence = n^c) to the Gatekeeper. The Gatekeeper responds with an ARJ (C2) with reject reason = resourceUnavailable. User B then sends a REL COM (C2) to User A. User A responds with an mlppReason = 46 (Call blocked). User A then sends a DRQ (C2) to the Gatekeeper. The Gatekeeper responds with an mlppReason = 46 (Call blocked). User A then sends a DCF (C2) to the Gatekeeper. User B and User C are shown in an Active call (C1) state throughout the sequence. A T303 timer is indicated on User A's side between the SETUP and REL COM messages. The diagram is labeled H.460.14_F10.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +Sequence diagram for Figure 10/H.460.14 showing an unsuccessful MLPP call. Lifelines: User A's endpoint, Gatekeeper(s), User B's endpoint, User C's endpoint. The sequence starts with User A in an Idle state. User A sends an ARQ (C2) with precedence = n^c) to the Gatekeeper. The Gatekeeper responds with an ACF (C2) with destCallSignalAddress = B. User A then sends a SETUP (C2) with precedence = n^c) to User B. User B sends an ARQ (C2) with precedence = n^c) to the Gatekeeper. The Gatekeeper responds with an ARJ (C2) with reject reason = resourceUnavailable. User B then sends a REL COM (C2) to User A. User A responds with an mlppReason = 46 (Call blocked). User A then sends a DRQ (C2) to the Gatekeeper. The Gatekeeper responds with an mlppReason = 46 (Call blocked). User A then sends a DCF (C2) to the Gatekeeper. User B and User C are shown in an Active call (C1) state throughout the sequence. A T303 timer is indicated on User A's side between the SETUP and REL COM messages. The diagram is labeled H.460.14\_F10. + +a) The gatekeeper may return ARJ if it knows that the active call is not preemptable. + +b) Endpoint B may immediately return REL COM without first sending ARQ if it knows that the current call cannot be preempted. + +c) $n = 0 \dots 4$ + +**Figure 10/H.460.14 – Example message flow for unsuccessful MLPP – direct endpoint call signalling with insufficient precedence level (without alternate party diversion)** + +In the case shown in Figure 10, if endpoint B knows that it has no preemptable facilities and that there is no alternate party diversion, it may reject the call setup by sending the Release Complete without first sending the ARQ. + +### 9.2.3 Successful MLPP – Gatekeeper – routed call signalling, stimulus signalling to endpoints + +Figure 11 shows an example of the signalling flows for a successful MLPP invocation and operation with terminal endpoints A, B, and C not being capable of MLPP according to this Recommendation (e.g., H.323 terminals with stimulus feature control). In this example, a Gatekeeper or a proxy acts on behalf of each endpoint MLPP. + +The terminal interfaces at endpoints A, B, and C are shown to illustrate the examples only. These interfaces are out of the normative scope of this Recommendation. Only the interfaces between each Gatekeeper/proxy and its associated endpoint are part of the normative scope of this Recommendation. + +![Sequence diagram for Figure 11/H.460.14 showing message flow for successful MLPP. Lifelines: User A's endpoint, User A's Gatekeeper, User B's Gatekeeper, User B's endpoint, User C's Gatekeeper, User C's endpoint. The diagram shows an active call (C1) between User B's endpoint and User C's endpoint. User A's endpoint sends an 'mlpp call request' to User A's Gatekeeper. User A's Gatekeeper sends 'LRQ (C2)' with 'precedence = n' to User B's Gatekeeper. User B's Gatekeeper responds with 'LCF (C2)' and 'SETUP (C2)' with 'precedence = n'. User A's Gatekeeper sends 'ALERTING (C2)' to User A's endpoint, which then sends 'mlpp call impending' to User A's endpoint. User A's Gatekeeper also sends 'mlppNotification = preemptionPending' to User B's endpoint. User B's endpoint sends 'FACILITY (C1)' to User C's Gatekeeper, which sends 'preemption notify' to User C's endpoint. User B's endpoint then sends 'REL COM (C1)' with 'mlppReason = 8 (preemptionNoReservation)' to User C's Gatekeeper, which sends 'call released' to User C's endpoint. User C's endpoint becomes 'Idle'. User A's Gatekeeper sends 'CONNECT (C2)' to User A's endpoint, which sends 'mlpp call confirm' to User A's endpoint. User A's Gatekeeper also sends 'mlppNotification = preemptionComplete' to User B's endpoint. User B's endpoint becomes 'Active call (C2)'. Timeouts T6 and T7 are indicated. The diagram is labeled H.460.14_F11 and n = 0..4.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +Sequence diagram for Figure 11/H.460.14 showing message flow for successful MLPP. Lifelines: User A's endpoint, User A's Gatekeeper, User B's Gatekeeper, User B's endpoint, User C's Gatekeeper, User C's endpoint. The diagram shows an active call (C1) between User B's endpoint and User C's endpoint. User A's endpoint sends an 'mlpp call request' to User A's Gatekeeper. User A's Gatekeeper sends 'LRQ (C2)' with 'precedence = n' to User B's Gatekeeper. User B's Gatekeeper responds with 'LCF (C2)' and 'SETUP (C2)' with 'precedence = n'. User A's Gatekeeper sends 'ALERTING (C2)' to User A's endpoint, which then sends 'mlpp call impending' to User A's endpoint. User A's Gatekeeper also sends 'mlppNotification = preemptionPending' to User B's endpoint. User B's endpoint sends 'FACILITY (C1)' to User C's Gatekeeper, which sends 'preemption notify' to User C's endpoint. User B's endpoint then sends 'REL COM (C1)' with 'mlppReason = 8 (preemptionNoReservation)' to User C's Gatekeeper, which sends 'call released' to User C's endpoint. User C's endpoint becomes 'Idle'. User A's Gatekeeper sends 'CONNECT (C2)' to User A's endpoint, which sends 'mlpp call confirm' to User A's endpoint. User A's Gatekeeper also sends 'mlppNotification = preemptionComplete' to User B's endpoint. User B's endpoint becomes 'Active call (C2)'. Timeouts T6 and T7 are indicated. The diagram is labeled H.460.14\_F11 and n = 0..4. + +a) LRJ (C2) with admissionRejectReason = resourceUnavailable if call cannot be accommodated. + +b) $n = 0 \dots 4$ + +**Figure 11/H.460.14 – Example message flow for successful MLPP – Gatekeeper-routed call signalling, non-standard signalling to endpoints** + +### 9.2.4 Successful MLPP – GK-routed call signalling, standardized functional signalling to endpoints + +In the case of functional signalling to an endpoint, the Gatekeeper to Gatekeeper interactions are as shown in Figure 11 and the Gatekeeper to Terminal interactions are as shown in Figure 7 through Figure 10. In this case, either the Gatekeeper or the endpoint may perform the MLPP operations, for example, control of preemption, timing, and initiation of diversion. + +## 9.3 Call states + +The following states are defined only for the purpose of supporting the procedural descriptions and figures in clauses 8.2 and 10. An implementation is not required to use these actual states. + +### 9.3.1 Call states at endpoint A + +The procedures for endpoint A are written in terms of the following conceptual states existing within the MLPP signalling entity in association with a particular call. + +| MLPP state | Description | +|---------------|-----------------------------------------------------------------------| +| MLPP-Idle | This state exists if MLPP is not active. | +| MLPP-Wait-Ack | This state exists after an MLPP request while waiting for a response. | + +### 9.3.2 Call states at endpoint B + +The procedures for endpoint B are written in terms of the following conceptual states existing within the MLPP signalling entity in association with a particular call. + +| MLPP state | Description | +|-------------------|-----------------------------------------------------------------------------------------------------------------| +| MLPP-Idle | This state exists if MLPP is not active. | +| MLPP-Dest-Notify | This state exists after an impending preemption warning is given while waiting for the preemption to occur. | +| MLPP-Wait-for-Ack | This state exists after releasing the first call and waiting for the called user to acknowledge the preemption. | + +### 9.3.3 Call states at endpoint C + +The procedures for endpoint C are written in terms of the following conceptual states existing within the MLPP signalling entity in association with a particular call. + +| MLPP state | Description | +|------------|------------------------------------------| +| MLPP-Idle | This state exists if MLPP is not active. | + +## 9.4 Timers + +The following timers are required for the implementation of MLPP. Depending on the signalling model used, they may be implemented in endpoints or in controlling gatekeepers. + +### 9.4.1 Origination timers + +None, other than those defined in ITU-T Rec. H.225.0. + +### 9.4.2 Destination timers + +#### - **Timer T6** + +Timer T6 controls the delay between an impending preemption warning notification and the forced release of the established call. + +Timer T6 should have a value not greater than 10 seconds. Immediate release is achieved by setting this timer to 1 second (allowing time for the notification). + +#### - **Timer T7** + +Timer T7 controls the wait for the called party to acknowledge (and accept) the preemption. Upon expiry, diversion to an alternate party occurs, if one has been designated. + +Timer T7 should have a value of 4-20 seconds. + +# 10 Specification and Description Language (SDL) diagrams for MLPP + +The functional signalling procedures for MLPP signalling entities are described in SDL form in Figures 13 through 16. The SDLs only show MLPP specific information transported on an H.225.0 connection. H.245 procedures (e.g., terminal capability exchange, master/slave determination, opening and closing of logical channels, etc.) are not shown. RAS signalling is not shown. In addition, interactions with other services are not shown. + +In case of a conflict between SDLs and the text within the other clauses of this Recommendation, the text shall take precedence. + +The symbols used in the following SDLs, irrespective of the direction of input and output signals, are defined in Figure 12. + +![Figure 12/H.460.14 – SDL symbols. The diagram shows eight symbols arranged in two rows of four. Top row: 1. Input from local endpoint user or internal event (a rectangle with a double line on the left and a chevron pointing right). 2. Output to local endpoint user (a rectangle with a double line on the left and a chevron pointing right). 3. Message to peer endpoint (a rectangle with a chevron pointing right). 4. Message from peer endpoint (a rectangle with a chevron pointing left). Bottom row: 1. Processing (a simple rectangle). 2. State (a rectangle with rounded ends). 3. Connector (a circle). 4. Decision (a diamond). The text 'H.460.14_F12' is located to the right of the Decision symbol.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +Figure 12/H.460.14 – SDL symbols. The diagram shows eight symbols arranged in two rows of four. Top row: 1. Input from local endpoint user or internal event (a rectangle with a double line on the left and a chevron pointing right). 2. Output to local endpoint user (a rectangle with a double line on the left and a chevron pointing right). 3. Message to peer endpoint (a rectangle with a chevron pointing right). 4. Message from peer endpoint (a rectangle with a chevron pointing left). Bottom row: 1. Processing (a simple rectangle). 2. State (a rectangle with rounded ends). 3. Connector (a circle). 4. Decision (a diamond). The text 'H.460.14\_F12' is located to the right of the Decision symbol. + +**Figure 12/H.460.14 – SDL symbols** + +## 10.1 Behaviour of User A's endpoint + +Figure 13 shows the behaviour of user A's endpoint. + +Input signals from the left and output signals to the left represent: + +- inputs from or indications and notifications to the user A; +- internal signals, e.g., timer expiry. + +Input signals from the right and output signals to the right represent: + +- messages from and to the called peer service control entity (i.e., in User A's Gatekeeper or User B's endpoint or Gatekeeper) which carry MLPP control information. + +![State transition diagram for Endpoint A (MLPP-Idle to MLPP-Wait-Ack).](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MLPP-Idle + MLPP-Idle --> SS-MLPP request + SS-MLPP request --> SETUP precedence = na + SETUP precedence = na --> Start T303 (basic call timer) + Start T303 (basic call timer) --> MLPP-Wait-Ack + MLPP-Wait-Ack --> CONNECT mlppNotification = preemptionComp + MLPP-Wait-Ack --> CONNECT (notBusy) + MLPP-Wait-Ack --> RELCOM mlppReason = nb + MLPP-Wait-Ack --> Release preempting call + MLPP-Wait-Ack --> ALERT/PROG /FACILITY + MLPP-Wait-Ack --> Timer T303 expiry + CONNECT mlppNotification = preemptionComp --> MLPP confirmed (preempted) + CONNECT (notBusy) --> MLPP confirmed (normal call) + RELCOM mlppReason = nb --> MLPP rejected + Release preempting call --> REL COM + ALERT/PROG /FACILITY --> Notify user A of impending preemption + Timer T303 expiry --> Normal call failure procedures + MLPP confirmed (preempted) --> Stop T303 + MLPP confirmed (normal call) --> Stop T303 + MLPP rejected --> Stop T303 + REL COM --> Stop T303 + Notify user A of impending preemption --> Stop T303 + Stop T303 --> MLPP-Idle + Stop T303 --> MLPP-Wait-Ack + +``` + +State transition diagram for Endpoint A (MLPP-Idle to MLPP-Wait-Ack). + +a) $n = 0 \dots 4$ + +b) $n \in \text{MlppReason}$ + +Figure 13/H.460.14 – Endpoint A SDL + +## 10.2 Behaviour of User B's endpoint + +Figures 14 and 15 show the behaviour of User B's endpoint. + +Input signals from the left and output signals to the left represent: + +- messages from and to the calling peer service control entity (i.e., in User B's Gatekeeper or User A's endpoint or Gatekeeper) which carry MLPP control information; +- inputs from and indications and notifications to the called user (User B); +- internal signals, e.g., timer expiry. + +Input signals from the right and output signals to the right represent: + +- messages from and to the unwanted user's peer service control entity (i.e., in User B's Gatekeeper or User C's endpoint or Gatekeeper) which carry MLPP control information. + +![Sequence diagram for Endpoint B (sheet 1 of 2) showing MLPP control logic.](fa01531ea2c45beeb4036005da3037a4_img.jpg) + +``` +sequenceDiagram + participant B as Endpoint B + Note left of B: MLPP-Idle + Note left of B: SETUP + Note left of B: user B busy? + Note left of B: ALERT/CONN (notbusy) + Note left of B: MLPP-Idle + Note left of B: preemption possible? + Note left of B: Alternate party? + Note left of B: REL COM mlppReason = 46 (callBlocked) + Note left of B: MLPP-Idle + Note left of B: PL of A-B > PL of B-C + Note left of B: FACILITY (to C) mlppNotification = preemptionPending + Note left of B: ALERTING (to A) mlppNotification = preemptionInProgress + Note left of B: Notify B of impending preemption + Note left of B: Start T6 + Note left of B: MLPP-Dest-Notify +``` + +The sequence diagram illustrates the MLPP control logic at Endpoint B. It begins with an initial state of 'MLPP-Idle'. Upon receiving a 'SETUP' message, it checks if 'user B busy?'. If 'No', it sends an 'ALERT/CONN (notbusy)' message and returns to 'MLPP-Idle'. If 'Yes', it checks if 'preemption possible?'. If 'No', it checks for an 'Alternate party?'. If 'No', it sends a 'REL COM mlppReason = 46 (callBlocked)' message and returns to 'MLPP-Idle'. If 'Yes', it 'Invoke Call Diversion (H.450.3)'. If 'preemption possible?' is 'Yes', it checks if 'PL of A-B > PL of B-C'. If 'No', it returns to the 'preemption possible?' check. If 'Yes', it sends a 'FACILITY (to C) mlppNotification = preemptionPending' message, followed by 'ALERTING (to A) mlppNotification = preemptionInProgress', 'Notify B of impending preemption', and 'Start T6', finally reaching 'MLPP-Dest-Notify'. + +Sequence diagram for Endpoint B (sheet 1 of 2) showing MLPP control logic. + +Figure 14/H.460.14 – Endpoint B SDL (sheet 1 of 2) + +![State transition diagram for Endpoint B (sheet 2 of 2) for MLPP. The diagram shows transitions between states MLPP-Dest-Notify, MLPP-Wait-for-Ack, and MLPP-Idle based on various triggers and actions.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MLPP-Dest-Notify + MLPP-Dest-Notify --> StartT7 : T6 expires + MLPP-Dest-Notify --> StopT6_1 : B release B-C call + MLPP-Dest-Notify --> StopT6_2 : REL COM from C + MLPP-Dest-Notify --> StopT6_3 : REL COM from A + MLPP-Dest-Notify --> StopT6_4 : B accepts preemption + StopT6_1 --> RELCOM_to_C_1 : REL COM (to C) + StopT6_2 --> Notify_user_B_release_C : Notify user B of release of C + StopT6_3 --> FACILITY_to_C : FACILITY (to C) + StopT6_4 --> RELCOM_to_C_2 : REL COM (to C) + RELCOM_to_C_1 --> Notify_user_B_preemption : Notify user B of preemption + StartT7 --> MLPP-Wait-for-Ack + FACILITY_to_C --> Notify_end_impending_preemption : Notify B of end of impending preemption + Notify_end_impending_preemption --> MLPP-Idle + MLPP-Wait-for-Ack --> T7_expires : T7 expires + MLPP-Wait-for-Ack --> B_rejects_preemption : B rejects preemption + MLPP-Wait-for-Ack --> RELCOM_from_A_1 : REL COM from A + MLPP-Wait-for-Ack --> B_accepts_preemption_1 : B accepts preemption + B_rejects_preemption --> StopT7_1 : Stop T7 + StopT7_1 --> Alternate_party_1{Alternate party?} + Alternate_party_1 -- Yes --> Invoke_Call_Diversion : Invoke Call Diversion (e.g., H.450.3) + Alternate_party_1 -- No --> MLPP-Wait-for-Ack + RELCOM_from_A_1 --> StopT7_2 : Stop T7 + StopT7_2 --> Notify_end_preemption_impending : Notify B of end of preemption impending + Notify_end_preemption_impending --> MLPP-Idle + B_accepts_preemption_1 --> StopT7_3 : Stop T7 + StopT7_3 --> Connect_A_B_media_1 : Connect A & B media + Connect_A_B_media_1 --> CONNECT_to_A_1 : CONNECT (to A) + CONNECT_to_A_1 --> MLPP-Idle + Invoke_Call_Diversion --> Alternate_party_2{Alternate party?} + Alternate_party_2 -- Yes --> Invoke_Call_Diversion + Alternate_party_2 -- No --> RELCOM_to_A : RELCOM to A + RELCOM_to_A --> MLPP-Idle + +``` + +State transition diagram for Endpoint B (sheet 2 of 2) for MLPP. The diagram shows transitions between states MLPP-Dest-Notify, MLPP-Wait-for-Ack, and MLPP-Idle based on various triggers and actions. + +Figure 15/H.460.14 – Endpoint B SDL (sheet 2 of 2) + +## 10.3 Behaviour of User C's endpoint + +Figure 16 shows the behaviour of User C's endpoint. + +Input signals from the left and output signals to the left represent: + +- messages from and to the peer service control entity (i.e., in User C's Gatekeeper or User B's endpoint or Gatekeeper) which carry MLPP control information. + +Output signals to the right represent: + +- indications or notifications to the unwanted user (User C). + +![State transition diagram for Endpoint C SDL. The diagram starts at an 'MLPP-Idle' state (oval). Three transitions lead to intermediate states: 'FACILITY mlppNotification = preemptionPending', 'FACILITY mlppNotification = preemptionEnd', and 'REL COM mlppNotification = preemptionComp'. The first two lead to 'call preemption status' (parallelogram) states, which then lead to the final 'MLPP-Idle' state. The third transition leads to 'Normal call release'.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +``` +graph TD; Idle1([MLPP-Idle]) --> F1{FACILITY +mlppNotification = +preemptionPending}; Idle1 --> F2{FACILITY +mlppNotification = +preemptionEnd}; Idle1 --> R{REL COM +mlppNotification = +preemptionComp}; F1 --> CPS1[/call preemption status/]; F2 --> CPS2[/call preemption status/]; CPS1 --> Idle2([MLPP-Idle]); CPS2 --> Idle2; R --> NCR[Normal call release]; +``` + +State transition diagram for Endpoint C SDL. The diagram starts at an 'MLPP-Idle' state (oval). Three transitions lead to intermediate states: 'FACILITY mlppNotification = preemptionPending', 'FACILITY mlppNotification = preemptionEnd', and 'REL COM mlppNotification = preemptionComp'. The first two lead to 'call preemption status' (parallelogram) states, which then lead to the final 'MLPP-Idle' state. The third transition leads to 'Normal call release'. + +Figure 16/H.460.14 – Endpoint C SDL + +# 11 Protocol interactions with other endpoint features + +When other supplementary services are provided according to one or more of the following methods, the interactions of MLPP with the protocol used for those services shall be as follows: + +## 11.1 Functional endpoints + +Endpoints using H.450-series functional signalling for other services may utilize the procedures in this Recommendation to provide the MLPP service. They shall handle interactions with the protocols defined in the applicable Recommendations for those services as follows. + +### 11.1.1 Call Transfer (SS-CT) + +The following protocol interactions shall apply if SS-CT is supported in accordance with ITU-T Rec. H.450.2 and both SS-CT and MLPP are invoked on the same call: + +If User A requests call transfer for two calls and MLPP is invoked on one or both calls, the actions of CT for transfer during alerting shall apply. The transferred-to endpoint may include a *callWaiting* invoke APDU (see ITU-T Rec. H.450.6) when sending the *callTransferSetup* return result APDU in an Alerting message to the transferred endpoint. The transferred-to endpoint may then also send a *remoteUserAlerting* invoke APDU in a Facility message to the transferred endpoint when the transferred-to user becomes not busy. If no *callWaiting* invoke APDU was sent, then also no *remoteUserAlerting* invoke APDU shall be sent. If the transferred-to user answers, a Connect message shall be sent to the transferred endpoint, but no MLPP **genericData** element shall be sent. + +If the secondary call does not exist, the transferred endpoint may request MLPP against a transferred-to user by including in the Setup message an MLPP **genericData** element together with the *callTransferSetup* invoke APDU. The transferred-to endpoint shall then follow the procedures of 8.2. + +### 11.1.2 Call Forwarding Unconditional (SS-CFU) + +The following protocol interactions shall apply if SS-CFU is supported in accordance with ITU-T Rec. H.450.3 and both SS-CFU and MLPP are possible on the same call: + +When executing call forwarding unconditional, the rerouting endpoint shall include in the Setup message to the diverted-to endpoint any **genericData** elements (including the ones for MLPP defined in this Recommendation) that were present in the Setup message received by the diverting endpoint, in addition to the *divertingLegInformation2* invoke APDU. + +### 11.1.3 Call Forwarding Busy (SS-CFB) + +The following protocol interactions shall apply if SS-CFB is supported in accordance with ITU-T Rec. H.450.3 and both SS-CFB and MLPP are possible on the same call: + +When executing call forwarding busy, the rerouting endpoint shall include in the Setup message to the diverted-to endpoint any **genericData** elements (including any for MLPP) that were present in the Setup message received by the diverting endpoint, in addition to the *divertingLegInformation2* invoke APDU. + +If a call including an MLPP **genericData** element arrives at a busy user who has activated SS-CFB, then SS-CFB shall be invoked. + +### 11.1.4 Call Forwarding on No Reply (SS-CFNR)/Call Deflection (SS-CD) + +No protocol interaction. + +NOTE – This means that the rerouting endpoint does not include any MLPP **genericData** element in the new Setup message when executing call diversion (no reply/call deflection). + +### 11.1.5 Call Hold + +No protocol interaction. + +### 11.1.6 Call Park/Call Pickup + +No protocol interaction. + +### 11.1.7 Call Waiting + +No protocol interaction. + +### 11.1.8 Message Waiting Indication + +No protocol interaction. + +### 11.1.9 Name Presentation + +No protocol interaction. + +### 11.1.10 Completion of Calls on Busy (SS-CCBS)/on No Reply (SS-CCNR) + +No protocol interaction. + +### 11.1.11 Call Offer (SS-CO) + +The following protocol interactions shall apply if SS-CO is supported in accordance with ITU-T Rec. H.450.10 and both SS-CO and MLPP are invoked on the same call: + +Endpoint A may include both the *callOfferRequest* and MLPP request in the Setup messages. In state MLPP-Wait-Ack, if a *callWaiting* invoke APDU is received in an Alerting or Progress message, endpoint A shall proceed with the Call Offer invocation procedures as defined in ITU-T Rec. H.450.10 instead of MLPP, as this occurs if the endpoint does not support MLPP. If any return error defined in this Recommendation is returned, endpoint A shall proceed with the procedures of this Recommendation. + +Endpoint B shall respond positively as defined in this Recommendation rather than to the *callOfferRequest* invoke APDU. It shall respond to the *callOfferRequest* invoke APDU by returning a *callOfferRequest* return error APDU with error "supplementaryServiceInteractionNotAllowed" in the resulting Alerting or Connect message. + +### 11.1.12 Call Intrusion (SS-CI) + +No protocol interactions, since both services should not be invoked on the same call setup. + +### 11.1.13 Common Information + +No protocol interaction. + +## 11.2 Stimulus-based endpoints + +Feature interactions for stimulus-based endpoints shall be resolved in the controlling Gatekeeper or feature server. Generally, precedence calls should be forwarded, redirected, or transferred with their original precedence. In most cases, precedence calls follow the normal redirection procedures unless they are able to preempt an existing call at the called destination. Annex L/H.323 further describes the stimulus-based endpoint case. + +## 11.3 Interworking with Switched Circuit Network + +MLPP may interwork with corresponding supplementary services as defined by other standards by means of gateway interworking functions. + +The specification of detailed gateway interworking procedures for MLPP is beyond the scope of this Recommendation and may be defined for various Switched Circuit Networks by other Recommendations. + +# Annex A + +## ASN.1 definition + +``` +MLPP DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +IMPORTS + CallIdentifier, + AliasAddress +FROM H323-MESSAGES; -- defined in H.225.0, Annex H + +MLPPInfo ::= SEQUENCE -- root for MLPP data ASN.1 +{ + precedence MlppPrecedence OPTIONAL, + mlppReason MlppReason OPTIONAL, +} +``` + +``` + + mlppNotification MlppNotification OPTIONAL, + alternateParty AlternateParty OPTIONAL, + releaseCall ReleaseCall OPTIONAL, + ... + } + + MlppPrecedence ::= ENUMERATED + { + flashOverride (0), + flash (1), + immediate (2), + priority (3), + routine (4), + ... + } + + MlppReason ::= ENUMERATED + -- Indicates reasons that call is refused or released. + { + preemptionNoReservation (8), + preemptionReservation (9), + callBlocked (46), + ... + } + + MlppNotification ::= CHOICE + -- Provides various notification events in Call Signalling messages + { + preemptionPending NULL, + preemptionInProgress NULL, + preemptionEnd NULL, + preemptionComplete NULL, + ... + } + + AlternateParty ::= SEQUENCE + { + altID AliasAddress, + altTimer INTEGER (0..255) OPTIONAL, --seconds + ... + } + + ReleaseCall ::= SEQUENCE + -- Identifies other call to be preempted first + { + preemptCallID CallIdentifier, + releaseReason MlppReason, + releaseDelay INTEGER (0..255) OPTIONAL, -- seconds to wait + ... + } + +END + +``` + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.460.15-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.460.15-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/H/T-REC-H.460.15-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/H/T-REC-H.460.15-200403-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.460.15-200403-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1697d9a344c74031165c02d2f98226495092732f --- /dev/null +++ b/marked/H/T-REC-H.460.15-200403-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1db8fd2f30fdab58b6b634cc1ee350532224d41be7288ff3e355ddd2afd3b9f8 +size 142704 diff --git a/marked/H/T-REC-H.460.15-200403-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.460.15-200403-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..719239119125416611fa3f2b9b221610043b9dbe --- /dev/null +++ b/marked/H/T-REC-H.460.15-200403-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a7cec9e00a562ca9ee06e451d1c0bbeeaf001b5ab7f041c1a1b5cf928213fa9 +size 150205 diff --git a/marked/H/T-REC-H.460.15-200403-I_PDF-E/raw.md b/marked/H/T-REC-H.460.15-200403-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ada7d2da19945c3eb50a1fbecb3c88f3bea104f2 --- /dev/null +++ b/marked/H/T-REC-H.460.15-200403-I_PDF-E/raw.md @@ -0,0 +1,449 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.460.15** + +(03/2004) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Infrastructure of audiovisual services – Supplementary +services for multimedia + +--- + +**Call signalling transport channel suspension +and redirection within H.323 systems** + +ITU-T Recommendation H.460.15 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.460.15** + +# **Call signalling transport channel suspension and redirection within H.323 systems** + +## **Summary** + +This Recommendation specifies a mechanism that allows H.323 entities participating in a stable call to temporarily suspend and later resume the call signalling channel. + +Further, using the procedures described in this Recommendation, an intermediate entity (such as a Gatekeeper that routes call signalling messages at the beginning of the call) may remove itself from the call signalling path once the call is stable, and establish the call signalling path directly between the other two entities. + +###### **Source** + +ITU-T Recommendation H.460.15 was approved on 15 March 2004 by ITU-T Study Group 16 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Abbreviations and acronyms ..... | 1 | +| 4 Capability advertisement ..... | 2 | +| 4.1 RAS messages ..... | 2 | +| 4.2 Call signalling messages..... | 2 | +| 5 Feature description..... | 3 | +| 5.1 Transport channel suspend and resume ..... | 3 | +| 5.2 Transport channel redirection..... | 5 | +| 5.3 Operational considerations ..... | 6 | +| 6 Generic Data usage..... | 7 | +| 7 Description of ASN.1 Types and Fields ..... | 7 | +| Annex A – ASN.1 definitions ..... | 7 | + + + +# **Call signalling transport channel suspension and redirection within H.323 systems** + +## **1 Scope** + +This Recommendation describes the procedures and the signalling protocol for temporarily suspending the call signalling transport channel between two H.323 entities on a call-by-call basis. This suspension is performed between the entities after the call reaches a stable state and only after mutual agreement. The signalling channel is resumed when a signalling message needs to be sent. For purposes of procedures in this Recommendation, a call is considered to be in a stable state as defined in R.3.5/H.323. + +The basic suspension and resumption procedure between two entities is further extended to an intermediate entity, such as a Gatekeeper routing call signalling, that can use it to get out of the signalling path and let the signalling flow directly between two endpoints. + +These procedures use the H.323 Generic Extensible Framework (GEF). + +## **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*. +- ITU-T Recommendation H.460.1 (2002), *Guidelines for the Use of the Generic Extensible Framework (GEF)*. +- ITU-T Recommendation H.460.6 (2002), *Extended Fast Connect feature*. +- ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-1:2002, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation*. +- ITU-T Recommendation X.691 (2002) | ISO/IEC 8825-2:2002, *Information technology – ASN.1 encoding rules – Specification of Packed Encoding Rules (PER)*. + +## **3 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations: + +| | | +|-------|--------------------------------| +| ACF | Admission Confirm | +| ARQ | Admission Request | +| ASN.1 | Abstract Syntax Notation No. 1 | +| CRV | Call Reference Value | +| GEF | Generic Extensible Framework | + +| | | +|-----|------------------------------------| +| LCF | Location Confirm | +| LRQ | Location Request | +| PER | Packed Encoding Rules | +| RAS | Registration, Admission and Status | +| RCF | Registration Confirm | +| RRQ | Registration Request | + +## 4 Capability advertisement + +### 4.1 RAS messages + +Endpoints capable of suspending active call signalling channels may advertise that capability in the **featureSet.supportedFeatures** field of the RRQ messages sent to the Gatekeeper. The capability shall not be advertised in lightweight RRQ messages. If the Gatekeeper routes call signalling messages, and supports this capability, then it shall indicate as such in the **featureSet.supportedFeatures** field of the RCF message. + +When initiating a call, an endpoint signals its desire or need for peering with another endpoint that supports this capability by indicating as such in the **featureSet.desiredFeatures** or **featureSet.neededFeature** as appropriate in the ARQ message to its Gatekeeper. + +If the originating endpoint's Gatekeeper is a direct mode Gatekeeper and needs to send one or more LRQs in order to resolve the address, it shall propagate this desired or needed information in the **featureSet** field of the LRQ message(s) that it sends to other Gatekeepers. A direct mode remote Gatekeeper shall select the appropriate endpoint(s) based on endpoints' capabilities. + +If the originating endpoint's Gatekeeper routes call signalling and needs to send one or more LRQs in order to resolve the address, it shall signal its own desire, or need, for peering with another entity that support this capability in the **featureSet** field of the LRQ message(s). A remote Gatekeeper that routes call signalling shall indicate its own capabilities in the LCF message and shall select, based on local policy, the appropriate terminating endpoint. + +An Annex G/H.225.0 Peer Element signals requirement for this capability in the **common.featureSet.desiredFeatures** or **common.featureSet.neededFeatures** fields. + +Once the local Gatekeeper identifies the signalling peer for the call (itself, a remote Gatekeeper or an endpoint), it shall indicate support of this feature in the **featureSet.supportedFeatures** of the ACF message it returns. + +### 4.2 Call signalling messages + +The originating entity shall indicate its support in **supportedFeatures** of the H.225.0 Setup message. Its signalling neighbour shall indicate its support in **supportedFeatures** of the Connect message. + +The capability is indicated with the feature identifier shown in Table 1. + +**Table 1/H.460.15 – Indication of the ability to suspend and redirect signalling transport channel** + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| Feature name: | Call signalling transport channel suspension and redirection | +| Feature description: | This feature allows an H.323 entity to temporarily suspend and subsequently resume an active transport channel opened for call signalling. | +| Feature identifier type: | Standard | +| Feature identifier value: | 15 | + +The following table identifies the parameter contained in the generic data structure. + +**Table 2/H.460.15 – Signalling channel suspend and redirect parameter** + +| | | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Signalling channel suspend and redirect | +| Parameter description: | This is the data sent in H.225.0 RAS and Call Signalling messages to manage suspension, resumption, and redirection of call signalling channel. | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 1 | +| Parameter type: | Raw | +| Parameter cardinality: | Once and only once | + +The ASN.1 structure of this parameter is described in clause 7. + +## 5 Feature description + +### 5.1 Transport channel suspend and resume + +Once both the signalling entities recognize the support by the other, either one may invoke the feature by sending a **StatusInquiry** message and including the **genericData** field in its **h323-uu-pdu** containing **ChannelSuspendRequest** information as described in this Recommendation. The **channelResumeAddress** shall be set to the address(es) to which the connection should be re-established, with multiple addresses listed as an ordered set of alternatives. The **ChannelSuspendRequest** message contains an **immediateResume** flag which, when set to TRUE, indicates that the recipient shall immediately re-establish a new connection upon closure of the current connection. + +The signalling neighbour should reply with a **Status** message with the **ChannelSuspendResponse** in the **genericData** field. If it is agreeable to the suspension of the connection, it should indicate that by setting the **okToSuspend** field to TRUE. The entity that wishes to suspend the connection will then confirm with a **ChannelSuspendConfirm** message and proceed to gracefully shutdown the transport connection, taking care to flush any remaining messages in the sent buffer on both sides of the connection. An entity shall not transmit further messages on that transport connection once it has indicated that it is acceptable to suspend the transport connection, unless the suspension is cancelled by the requesting entity by transmitting a **ChannelSuspendCancel** message. + +When either entity wishes to send a call-related message to its signalling neighbour, the connection needs to be re-established. To re-establish the signalling channel, the entity opens a transport connection to the transport address sent by the signalling neighbour. If there is more than one transport address, the addresses will be tried in the order sent. After opening the connection the entity shall send a **StatusInquiry** message with **ChannelResumeRequest**. This message contains a random number. In case both the entities open a connection and send the **ChannelResumeRequest** at the same time, the entity that has the numerically lower random number shall close its connection. In case the random numbers are the same, both entities shall transmit a new **StatusInquiry** message over the transport connection with a different random number. Creating a new connection may not be necessary if a signalling channel between the entities already exists and may be reused. The entity that receives an acceptable **ChannelResumeRequest** shall reply with a **ChannelResumeResponse** in a **Status** message before commencing regular call signalling messages on the channel. + +A **ChannelSuspendRequest** or a **ChannelResumeRequest** embedded within a **StatusInquiry** that is replied with a **Status** message without the appropriate response (**ChannelSuspendResponse** or **ChannelResumeResponse**) shall be treated as a protocol error and handled as per 8.6/H.323. + +It is possible that an entity may not have sufficient resources to initiate or accept a new transport connection especially if the motivation behind suspending connection is to optimize resource usage. To prevent this condition, it is recommended that each entity set aside a percentage of its resources for the resumption of suspended connections. + +In case of failure to establish the transport connection for resumption, the initiator shall cycle through the list of **channelResumeAddress** for a number of times determined by the implementation. Complete failure to resume a suspended signalling channel should be treated as network failure and the call ended. + +A new CRV for the call that is not in use between the sender and the destination address may need to be selected. This CRV shall be used in the **StatusInquiry** message carrying the **ChannelResumeRequest**. The receiving entity, on receiving the possibly unknown CRV, shall relate it to the call with the **callIdentifier** in the **StatusInquiry-UUIE**. + +Example message flows for channel suspend and resume are shown in Figure 1. + +![Sequence diagram illustrating message flows for channel suspend and resume between entities A, GK, and B. The diagram is divided into four phases: Endpoints Registered, Call Established, Transport Channel Suspended, and Call Signalling Channel Re-established. The sequence of messages is: 1. A and B send RRQ(supportedFeatures(suspend)) to GK. 2. GK responds with RCF to both. 3. A sends ARQ(desiredFeatures(suspend)) to GK. 4. GK responds with ACF(B) to A. 5. GK sends SETUP(supportedFeatures(suspend)) to B. 6. GK sends ALERT(supportedFeatures(suspend)) to B. 7. GK sends CONNECT(supportedFeatures(suspend)) to B. 8. A sends STATUSINQUIRY(ChannelSuspendRequest(A)) to GK. 9. GK responds with STATUS(ChannelSuspendResponse(Ok,B)) to A. 10. GK sends STATUS(ChannelSuspendConfirm) to B. 11. A sends STATUSINQUIRY(ChannelResumeRequest) to GK. 12. GK responds with STATUS(ChannelResumeResponse) to A. 13. Finally, GK sends RELEASECOMPLETE to A.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +sequenceDiagram + participant A + participant GK + participant B + + Note right of B: Endpoints Registered + A->>GK: RRQ(supportedFeatures(suspend)) + GK-->>A: RCF + B->>GK: RRQ(supportedFeatures(suspend)) + GK-->>B: RCF + + Note right of B: Call Established + A->>GK: ARQ(desiredFeatures(suspend)) + GK-->>A: ACF(B) + GK->>B: SETUP(supportedFeatures(suspend)) + GK->>B: ALERT(supportedFeatures(suspend)) + GK->>B: CONNECT(supportedFeatures(suspend)) + + Note right of B: Transport Channel Suspended + A->>GK: STATUSINQUIRY(ChannelSuspendRequest(A)) + GK-->>A: STATUS(ChannelSuspendResponse(Ok,B)) + GK->>B: STATUS(ChannelSuspendConfirm) + + Note right of B: Call Signalling Channel Re-established + A->>GK: STATUSINQUIRY(ChannelResumeRequest) + GK-->>A: STATUS(ChannelResumeResponse) + + Note right of B: Call Signalling Channel Re-established + GK->>A: RELEASECOMPLETE + +``` + +H.460.15\_F01 + +Sequence diagram illustrating message flows for channel suspend and resume between entities A, GK, and B. The diagram is divided into four phases: Endpoints Registered, Call Established, Transport Channel Suspended, and Call Signalling Channel Re-established. The sequence of messages is: 1. A and B send RRQ(supportedFeatures(suspend)) to GK. 2. GK responds with RCF to both. 3. A sends ARQ(desiredFeatures(suspend)) to GK. 4. GK responds with ACF(B) to A. 5. GK sends SETUP(supportedFeatures(suspend)) to B. 6. GK sends ALERT(supportedFeatures(suspend)) to B. 7. GK sends CONNECT(supportedFeatures(suspend)) to B. 8. A sends STATUSINQUIRY(ChannelSuspendRequest(A)) to GK. 9. GK responds with STATUS(ChannelSuspendResponse(Ok,B)) to A. 10. GK sends STATUS(ChannelSuspendConfirm) to B. 11. A sends STATUSINQUIRY(ChannelResumeRequest) to GK. 12. GK responds with STATUS(ChannelResumeResponse) to A. 13. Finally, GK sends RELEASECOMPLETE to A. + +**Figure 1/H.460.15 – Example message flows for channel suspend and resume** + +### 5.2 Transport channel redirection + +A call control entity, such as the Gatekeeper, which may be in the call signalling path (in the "routed" mode) at the beginning of a call, may remove itself from the signalling path (and go to the "direct" mode) by using this procedure. Such a Gatekeeper should send a **ChannelSuspendRequest** message (within the StatusInquiry message) to each of its signalling neighbours with the **channelResumeAddress** set to the other's call signalling address. After receiving positive responses from both, the Gatekeeper should proceed to suspend both the channels. If any of the two entities needs to establish a call signalling path, it has the other's address to which they can open a connection following the procedure as above. + +When a call signalling channel is suspended for the purpose of redirecting the call signalling channel to a different device, one device may attempt to resume the connection before the other device receives the **ChannelSuspendConfirm** message and/or closes its current transport connection. This race condition shall be handled by accepting the new connection and by maintaining the old connection solely for receiving the **ChannelSuspendConfirm** message. + +If one neighbour does not wish to suspend the channel it has with the Gatekeeper and responds with **ChannelSuspendResponse** with **okToSuspend** set to False, the Gatekeeper should abort the procedure by sending a **ChannelSuspendCancel** to the other endpoint. + +Example message flows for channel redirection are shown in Figure 2. + +![Sequence diagram illustrating message flows for channel redirection between endpoints A and B via a Gatekeeper (GK).](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +sequenceDiagram + participant A + participant GK + participant B + + Note left of A: + A->>GK: RRQ(supportedFeatures(suspend)) + GK-->>A: RCF + B->>GK: RRQ(supportedFeatures(suspend)) + GK-->>B: RCF + + Note over A,B: Endpoints Registered + A->>GK: ARQ(desiredFeatures(suspend)) + GK-->>A: ACF(GK) + A->>GK: SETUP + GK->>B: SETUP + A->>GK: ALERTING + GK->>B: ALERTING + A->>GK: CONNECT + GK->>B: CONNECT + + Note over A,B: Call Established + A->>GK: STATUSINQUIRY(ChannelSuspendRequest(B)) + GK-->>A: STATUS(ChannelSuspendResponse(Ack,A)) + GK->>B: STATUSINQUIRY(ChannelSuspendRequest(A)) + GK-->>B: STATUS(ChannelSuspendResponse(Ack,B)) + A->>GK: STATUS(ChannelSuspendConfirm) + GK->>B: STATUS(ChannelSuspendConfirm) + + Note over A,B: Transport Channel Suspended + A->>GK: STATUSINQUIRY(ChannelResumeRequest) + GK-->>A: STATUS(ChannelResumeResponse) + + Note over A,B: Call Signalling Channel Re-routed + A->>GK: RELEASECOMPLETE + + Note right of B: H.460.15_F02 + +``` + +The diagram illustrates the message flows for channel redirection. It begins with endpoints A and B sending RRQ(supportedFeatures(suspend)) to the Gatekeeper (GK), which responds with RCF. This leads to the 'Endpoints Registered' state. Next, A sends ARQ(desiredFeatures(suspend)) to GK, which responds with ACF(GK). Then, A sends SETUP to GK, which forwards it to B. Both A and B send ALERTING and CONNECT messages to GK, leading to the 'Call Established' state. In this state, A sends STATUSINQUIRY(ChannelSuspendRequest(B)) to GK, which responds with STATUS(ChannelSuspendResponse(Ack,A)). GK then sends STATUSINQUIRY(ChannelSuspendRequest(A)) to B, which responds with STATUS(ChannelSuspendResponse(Ack,B)). Both A and B send STATUS(ChannelSuspendConfirm) to GK, leading to the 'Transport Channel Suspended' state. A then sends STATUSINQUIRY(ChannelResumeRequest) to GK, which responds with STATUS(ChannelResumeResponse). This leads to the 'Call Signalling Channel Re-routed' state, where A sends RELEASECOMPLETE to GK. The diagram is labeled H.460.15\_F02. + +Sequence diagram illustrating message flows for channel redirection between endpoints A and B via a Gatekeeper (GK). + +**Figure 2/H.460.15 – Example message flows for channel redirection** + +### 5.3 Operational considerations + +If a separate connection is being used for H.245 Control Channel signalling, it shall also be closed along with the H.225.0 call signalling channel when following the procedures in this Recommendation. + +A Gatekeeper that redirects the call signalling channel and does not pass the H.245 messages through transparently should set the **resetH245** flag in the **ChannelSuspendRequest** message indicating that the endpoints shall restart H.245 procedures. In such a case, after the H.225.0 call signalling channel is resumed, the state of the endpoints' H.245 state machines shall be reset without closing any open media channels. If either endpoint elects to establish an H.245 Control Channel after reestablishing the H.225.0 call signalling channel, the endpoints shall first transmit a TCS message and negotiate master/slave, as per normal H.245 procedures. It should be noted that if the H.245 Control Channel used a separate connection before the connection was suspended and if tunnelling is supported when the H.225.0 call signalling channel is resumed, H.245 tunnelling should be used as per ITU-T Rec. H.323. + +If the Gatekeeper (or other intermediary entity) also routes the media stream and wishes to redirect the call signalling channel, it should first transmit Empty Capability Set messages (as described in 8.4.6/H.323) and allow all media streams to close or follow the procedures in ITU-T Rec. H.460.6 to close all media channels (as described in 4.1.2/H.460.6). It shall then suspend the call signalling channels with the **immediateResume** flag set to TRUE in the + +**ChannelSuspendRequest** message. An endpoint receiving such a suspend request shall immediately re-establish the call signalling channel and open media channels. To avoid a possible unnecessary connection establishment, the intermediate entity may choose to set the **immediateResume** flag on only one of the **ChannelSuspendRequest** messages. + +An endpoint that wishes to restart the H.245 state machine on resumption or redirection of a channel should set the **resetH245** flag in the **ChannelResumeRequest** message. + +## 6 Generic Data usage + +The entities use **genericData** field in the H323-UU-PDU carried in the **Status** and **StatusInquiry** message to negotiate the capability invocation. + +## 7 Description of ASN.1 Types and Fields + +## Annex A + +### ASN.1 definitions + +``` +SIGNALLING-CHANNEL-SUSPEND-REDIRECT DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +IMPORTS + TransportAddress FROM H323-MESSAGES; + +SignallingChannelData ::= SEQUENCE +{ + signallingChannelData CHOICE { + channelSuspendRequest ChannelSuspendRequest, + channelSuspendResponse ChannelSuspendResponse, + channelSuspendConfirm ChannelSuspendConfirm, + channelSuspendCancel ChannelSuspendCancel, + channelResumeRequest ChannelResumeRequest, + channelResumeResponse ChannelResumeResponse, + ... + }, + ... +} + +ChannelSuspendRequest ::= SEQUENCE +{ + channelResumeAddress SEQUENCE OF TransportAddress, + immediateResume BOOLEAN, + resetH245 NULL OPTIONAL, + ... +} + +ChannelSuspendResponse ::= SEQUENCE +{ + okToSuspend BOOLEAN, + channelResumeAddress SEQUENCE OF TransportAddress, + ... +} + +ChannelSuspendConfirm ::= SEQUENCE +{ + ... +} + +ChannelSuspendCancel ::= SEQUENCE +{ + ... +} +``` + +``` + ... +} + +ChannelResumeRequest ::= SEQUENCE +{ + randomNumber INTEGER(0..4294967295), + resetH245 NULL OPTIONAL, + ... +} + +ChannelResumeResponse ::= SEQUENCE +{ + ... +} + +END -- of ASN.1 +``` + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.460.2-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.460.2-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.460.2-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.460.22-201504-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/H/T-REC-H.460.22-201504-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d0ea7699747158bf848ba775c02505173e2368 --- /dev/null +++ b/marked/H/T-REC-H.460.22-201504-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7c86400b77583c7366251b8f7e87ebd240e7eab3f2ed78bc3540e43b8e2000d +size 85562 diff --git a/marked/H/T-REC-H.460.22-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.460.22-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/H/T-REC-H.460.22-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/H/T-REC-H.460.22-201504-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/H/T-REC-H.460.22-201504-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d19ed7d5aade97536ae5185bae3fab0391bd82cc --- /dev/null +++ b/marked/H/T-REC-H.460.22-201504-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9538544d632cefe4c1f83b63de32a2d6bad46ee5f3347dfb9a8c19767cce083b +size 75020 diff --git a/marked/H/T-REC-H.460.22-201504-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/H/T-REC-H.460.22-201504-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13448b6b3e5c4d126efe47ade82afefc1b13647e --- /dev/null +++ b/marked/H/T-REC-H.460.22-201504-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d388af0ebca7a99b2254a00790570acd28f3e53d195f5d12895fe8b77f43c68 +size 55974 diff --git a/marked/H/T-REC-H.460.25-201009-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.460.25-201009-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.460.25-201009-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.460.27-201511-I_PDF-E/raw.md b/marked/H/T-REC-H.460.27-201511-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..533c9694a556cbbd2df9ea76a45ed32f482558b8 --- /dev/null +++ b/marked/H/T-REC-H.460.27-201511-I_PDF-E/raw.md @@ -0,0 +1,394 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.460.27** + +(11/2015) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Infrastructure of audiovisual services – Supplementary +services for multimedia + +--- + +**End-to-end session identifier for ITU-T H.323 +systems** + +Recommendation ITU-T H.460.27 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font, with "ITU" in a larger, bold font above it. + +ITU logo + +International +Telecommunication +Union + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.460.27 + +### End-to-end session identifier for ITU-T H.323 systems + +## Summary + +Recommendation ITU-T H.460.27 describes an end-to-end session identifier for use in IP-based multimedia communication systems that enables endpoints, intermediate devices and management systems to identify a session end-to-end, to associate multiple endpoints with a given multipoint conference, to track communication sessions when they are redirected and to associate one or more media flows with a given communication session. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.460.27 | 2015-11-29 | 16 | 11.1002/1000/12457 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview..... | 2 | +| 7 Identifying a communication session ..... | 3 | +| 8 Session ID components..... | 3 | +| 9 Conveying the session ID ..... | 3 | +| 10 Endpoint behaviour..... | 4 | +| 11 Processing by intermediaries ..... | 5 | +| 12 Multipoint control unit behaviour..... | 6 | +| Bibliography..... | 8 | + + + +## Recommendation ITU-T H.460.27 + +### End-to-end session identifier for ITU-T H.323 systems + +# 1 Scope + +This Recommendation defines the end-to-end session identifier (session ID), signalling syntax and procedures for using the identifier within ITU-T H.323 systems, including endpoints, multipoint control units and Gatekeepers. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.225.0] Recommendation ITU-T H.225.0 (2009), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- [ITU-T H.323] Recommendation ITU-T H.323 (2009), *Packet-based multimedia communications systems*. +- [ITU-T H.460.1] Recommendation ITU-T H.460.1 (2013), *Guidelines for the use of the generic extensible framework*. +- [IETF RFC 3261] IETF RFC 3261 (2002), *SIP: Session Initiation Protocol*. +- [IETF RFC 4122] IETF RFC 4122 (2005), *A Universally Unique Identifier (UUID) URN Namespace*. + +## 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 call** [ITU-T H.323]: Point-to-point multimedia communication between two ITU-T H.323 endpoints. The call begins with the call set-up procedure and ends with the call termination procedure. The call consists of the collection of reliable and unreliable channels between the endpoints. A call may be directly between two endpoints or may include other ITU-T H.323 entities such as a Gatekeeper or an MCU. In case of interworking with some SCN endpoints via a Gateway, all the channels terminate at the Gateway where they are converted to the appropriate representation for the SCN end system. Typically, a call is between two users for the purpose of communication, but may include signalling-only calls. An endpoint may be capable of supporting multiple simultaneous calls. + +**3.1.2 call identifier** [ITU-T H.323]: A globally unique non-zero value created by the calling endpoint and passed in various ITU-T H.225.0 messages. + +**3.1.3 global call identification** [ITU-T H.323]: A value assigned to an end-to-end call to uniquely identify that call from end-to-end. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 communication session:** A communication session, or simply "session", refers to a call or series of calls initiated or received by an endpoint for which the endpoint utilizes the same universally unique identifier (UUID) value in call signalling messages. From a calling user's perspective, this would be all call signalling messages from the time the user initiates a call until the time the call is terminated. From the called user's perspective, this would be all call signalling messages from first message received by the user's terminal until the call is terminated. + +**3.2.2 Session Identifier:** (Also referred to as a Session ID) A globally unique identifier used to identify a session from the point of origin, passing through any number of intermediaries, to the ultimate point of termination. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------| +| GEF | Generic Extensible Framework | +| IP | Internet Protocol | +| MAC | Media Access Control | +| MCU | Multipoint Control Unit | +| SCN | Switched Circuit Network | +| SIP | Session Initiation Protocol | +| UUID | Universally Unique Identifier | + +# 5 Conventions + +None. + +# 6 Overview + +The Session Identifier (Session ID) identifies a communication session from the point of origin, passing through any number of intermediaries, to the ultimate point of termination. The primary motivation for introducing the Session ID into ITU-T H.323 [ITU-T H.323] systems is to assist with troubleshooting network deployments. This includes the ability for network administrators to look at log files on a plurality of devices as well as to make use of a common or related set of identifiers conveyed in signalling messages. However, the Session ID might be used for other purposes, including correlating participants in a multipoint conference, especially one that involves participants using a mixture of [ITU-T H.323] and session initiation protocol (SIP) [IETF RFC 3261] devices, or an association of call signalling messages and media flows. This Recommendation does not prescribe how entities might use the Session ID. Rather, this Recommendation merely describes the syntax and signalling procedures. + +It should be appreciated that, while [ITU-T H.323] defines the concept of a call, which begins with the call setup procedure and ends with the termination procedure, the user's perception of a call and what [ITU-T H.323] defines as a call are not the same. When a user initiates a call, a globally unique identifier, referred to as the call identifier, is assigned to that call. If the call is transferred or forwarded, the endpoint will initiate a new call and assign a new identifier. While this is intended behaviour, from the user's perspective this is a single call. Likewise, any network administrator trying to troubleshoot a network will also view the subsequent call as part of the same overall communication session. + +As it is desirable to be able to associate related calls, [ITU-T H.323] introduced the notion of call linkage (see clause 10.3 of [ITU-T H.323]). This concept is useful in allowing intermediaries, management systems, or other entities to know that a call is in some way related to a different call. However, due to complex service interaction, it is possible that the global call identifier is fully replaced, thus making it challenging to see a complete call history. + +The Session ID aims to solve the problem of identification of a session end-to-end. The syntax and procedures are also defined so that they are compatible with SIP systems (see [b-IETF RFC SIP]). + +# 7 Identifying a communication session + +A session is identified using two universally unique identifier (UUID) values, with each endpoint in a session allocating one of the UUID values. In the interest of brevity, the set of values is written in a set notation such as {A, B}, where "A" refers to the UUID allocated by one endpoint and "B" refers to the UUID allocated by the second endpoint. While directionality information is associated with the conveyance of the Session ID in signalling messages, the Session ID itself does not indicate whether "A" or "B" is the sender or recipient of a message. + +The reason for using two distinct UUID values to identify a communication session is to effectively deal with various complex service interactions and allow for associating one call with another call during such service interactions. As a simple example, if endpoint "Alice" calls endpoint "Bob", Alice will allocate a UUID "A" for that call. Likewise, Bob will allocate a UUID "B". The Session ID for the call between Alice and Bob is {A, B}. If Bob transfers that call to Carol, the call between Alice and Bob is terminated. From the user's perspective, however, the call is merely transferred. Indeed, the "Alice" endpoint will initiate a new call (using a new call ID) to Carol. However, the UUID allocated for the Session ID will remain the same. Carol will allocate a UUID for her contribution to the Session ID. The Session ID between Alice and Carol is, therefore, {A, C}. + +It is important to note that, while the Session ID will change during service interactions, the UUID contributed by an endpoint in a call will remain fixed. In the above example, the value "A" is used in both the calls between Alice and Bob and between Alice and Carol. This property allows a network operator to immediately recognize that these two calls are part of the same communication session, with Alice and Bob being the first two endpoints in that session and Alice and Carol being the second two endpoints in that session. Observation of signalling messages would show that these calls ran serially. + +## 8 Session ID components + +Each endpoint creates a UUID (see [IETF RFC 4122]) for insertion into signalling messages. + +The version number in the UUID indicates the manner in which the UUID is generated, which might contain random values or a MAC address of the endpoint. To ensure confidentiality, endpoints should not use version 1 UUIDs consisting of the MAC address, but should instead generate version 4 (random) UUIDs to address relevant privacy concerns. + +Once an endpoint generates a UUID for a session, the UUID never changes over the life of that session. + +# 9 Conveying the Session ID + +The sender of an ITU-T H.225.0 [ITU-T H.225.0] message shall insert its UUID value into each transmitted message using the generic extensible framework (GEF) [ITU-T H.460.1]. Specifically, the UUID of the sender of the message and the UUID of the intended recipient of the message, if known, shall be inserted into the genericData field of each ITU-T H.225.0 call signalling message. + +The Session ID feature identifier to be utilized is described in Table 1. + +**Table 1 – SessionID feature indication** + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Feature name: | Session Identifier | +| Feature description: | A means of sending the end-to-end Session Identifier, comprising one or two UUID values, each of which is created by the two endpoints in a communication session | +| Feature identifier type: | Standard | +| Feature identifier value: | 27 | + +The associated parameter used to hold the sender's UUID is described in Table 2. + +**Table 2 – Sender's UUID** + +| | | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Sender-UUID | +| Parameter description: | This parameter holds the UUID value of the sender of the message. The UUID shall be presented as a text string using lower-case hexadecimal digits with the most significant octet of the UUID appearing first. Note that while the cardinality allows for this parameter to be absent, only intermediaries sending response messages (e.g., CALL PROCEEDING) prior to learning the remote endpoint's UUID may leave this parameter absent. | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 1 | +| Parameter type: | Text | +| Parameter cardinality: | Zero or one | + +The associated parameter used to hold the recipient's UUID is described in Table 3. + +**Table 3 – Recipient's UUID** + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Recipient-UUID | +| Parameter description: | This parameter holds the UUID value of the recipient of the message. The UUID shall be presented as a text string using lowercase hexadecimal digits with the most significant octet of the UUID appearing first. | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 2 | +| Parameter type: | Text | +| Parameter cardinality: | Zero or one | +| NOTE – [b-IETF RFC SIP] defines a "null" UUID value to use as the recipient UUID when the sender of a message does not know the UUID of the recipient. The "null" UUID was introduced primarily for backward-compatibility with a legacy SIP implementation of the session Identifier and is used in certain provisional responses, but is not used in ITU-T H.323 systems. | | + +## 10 Endpoint behaviour + +Endpoints compliant with this Recommendation shall insert the session Identifier UUIDs into every ITU-T H.225.0 call signalling message transmitted, even if it is determined that the remote endpoint does not support this feature. In the case that the remote endpoint does not support this feature, the Recipient-UUID parameter would be absent. + +For every new communication session, an endpoint shall generate a new, unique UUID that shall persist unchanged for the entire duration of the communication session, including when the call is forwarded, transferred, or put on hold, etc. For any new call placed, the endpoint will not have knowledge of the Recipient-UUID value and therefore would not include that Recipient-UUID value in signalling, as shown in Figure 1. + +![Diagram of Figure 1: SETUP message from Alice to Bob](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +A sequence diagram showing a message from Alice to Bob. Alice is on the left, Bob is on the right. A horizontal arrow points from Alice to Bob with the text "SETUP using {A}" above it. Below Bob's box is the text "H.460.27(15)\_F01". + +Diagram of Figure 1: SETUP message from Alice to Bob + +**Figure 1 – SETUP contains only {A}** + +The called endpoint will include both its UUID and the UUID of the calling endpoint, as shown in Figure 2. + +![Diagram of Figure 2: CONNECT message from Bob to Alice](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +A sequence diagram showing a message from Bob to Alice. Alice is on the left, Bob is on the right. A horizontal arrow points from Bob to Alice with the text "CONNECT using {B, A}" above it. Below Bob's box is the text "H.460.27(15)\_F02". + +Diagram of Figure 2: CONNECT message from Bob to Alice + +**Figure 2 – CONNECT contains both {B, A}** + +Once an endpoint learns the UUID of the remote endpoint, it shall include that UUID value in all subsequent call signalling messages as the Recipient-UUID parameter as shown in Figure 3. Since service interactions can take place in the network, in some cases without the knowledge of the endpoint, the endpoint must inspect every message received to see if the remote endpoint's UUID value has changed. If it has, the endpoint must update the UUID value it has stored internally for the remote endpoint and use that updated value in subsequent messages. + +![Diagram of Figure 3: FACILITY message from Alice to Bob](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +A sequence diagram showing a message from Alice to Bob. Alice is on the left, Bob is on the right. A horizontal arrow points from Alice to Bob with the text "FACILITY using {A, B}" above it. Below Bob's box is the text "H.460.27(15)\_F03". + +Diagram of Figure 3: FACILITY message from Alice to Bob + +**Figure 3 – CONNECT contains both {B, A}** + +It should be noted that messages received by an endpoint may contain a UUID value as the Recipient-UUID that does not match the endpoint's UUID value for the session. This can happen due to various service interactions in the network and shall not be treated as an error. The endpoint will update the remote endpoint with the correct UUID value when sending a subsequent message to the remote endpoint. If the endpoint encounters this situation and has no other need to send an ITU-T H.225.0 call signalling message, the endpoint shall send a FACILITY message to the remote endpoint with forwardedElements as the reason. This is to ensure that all intermediaries along the path and the remote endpoint are aware of the correct UUID for the endpoint. + +## **11 Processing by intermediaries** + +In consideration of the fact that the Session Identifier is constructed in such a way as to not reveal any personal, device, or domain identifying information and in order to ensure the integrity of the end-to-end session identifier, intermediaries, including Gatekeepers and gateways, shall forward any received UUIDs and shall not alter the UUID values received in ITU-T H.225.0 call signalling messages, except as outlined in this clause. A UUID value being forwarded by a gatekeeper intermediary is shown in Figure 4. + +![Diagram showing UUID forwarding by intermediaries. Alice sends a SETUP message using {A} to the GK (Gatekeeper), which then forwards it to Bob using {A}. The diagram is labeled H.460.27(15)_F04.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph LR + Alice[Alice] -- "SETUP using {A}" --> GK[GK] + GK -- "SETUP using {A}" --> Bob[Bob] + style GK fill:black,color:white + subgraph H.460.27(15)_F04 + end + +``` + +Diagram showing UUID forwarding by intermediaries. Alice sends a SETUP message using {A} to the GK (Gatekeeper), which then forwards it to Bob using {A}. The diagram is labeled H.460.27(15)\_F04. + +**Figure 4 – UUIDs forwarded by intermediaries** + +Intermediary devices that transfer a call, such as by joining together two different "call legs", shall properly convey the correct UUID values to the two endpoints that are joined. While endpoints might be able to recover from having received the wrong UUID value, not taking care to ensure that the right values are sent in call signalling messages will make it more difficult to properly troubleshoot networks. + +If an intermediary receives an ITU-T H.225.0 call signalling message that does not contain a Session ID, the intermediary may assign a Sender-UUID for use in that and all subsequent messages. If the intermediary is aware of the recipient's UUID, it shall insert the recipient's UUID into the Recipient-UUID parameter. It is important that an intermediary providing this feature on behalf of the endpoint takes note if a subsequent message received by the intermediary from the originating endpoint does contain a UUID value. In such a case, the intermediary shall use that UUID value for all subsequent message exchanges. Likewise, if the sending endpoint stops sending a Sender-UUID value, the intermediary may once again provide a new UUID value; this new UUID value shall not be the same as any previously used UUID value. + +Intermediaries that generate Session ID UUID values on behalf of an endpoint that does not implement this Recommendation shall take steps to ensure that the same UUID value is used for all signalling messages conveyed on behalf of the endpoint. + +Some intermediary devices have the capability of initiating two separate calls to endpoints and then "joining" those two calls together. For example, Alice might have a gatekeeper that is configured to establish a call between her and Bob. The gatekeeper will send a SETUP message to Alice and to Bob, perhaps simultaneously or serially. For any communication session that such an intermediary initiates, it shall fabricate a UUID for use as the Sender-UUID. However, this UUID will only be used temporarily. Once the UUID of the second endpoint is known, the intermediary shall cease using its fabricated UUID and use the now known UUID of the actual endpoint. + +If an intermediary sends a response message to a calling endpoint (e.g., CALL PROCEEDING) prior to learning the other endpoint's UUID value, the intermediary shall send the message to the endpoint with the known UUID in the Recipient-UUID parameter and shall either omit the Sender-UUID parameter or fabricate a temporary UUID value. + +## 12 Multipoint control unit behaviour + +A reason for introducing the Session ID is to allow for easy association of endpoints engaged in a communication session. This applies equally to the participants in a conference. While [ITU-T H.323] has a conference identifier that can be used to identify all participants in a conference, it is desirable to also use the Session ID for two reasons: Perhaps foremost is the fact that, more often than not, endpoints are completely unaware of the conference identifier for a conference and are directed into a conference via a menu system of some kind. Secondly, it is desirable to have a solution that works equally well with both ITU-T H.323 and SIP endpoints. + +Therefore, multipoint control units (MCUs), including cascaded MCUs, shall use a single UUID value in all signalling messages sent to participants in the same conference as shown in Figure 5. This UUID value may be taken from the ITU-T H.323 conference identifier. Different conferences on the MCU, of course, shall use different UUID values. + +In this way, all participants in a multipoint conference will have a unique UUID value allocated by the endpoint, but will all share one UUID value that helps to establish the association in a conference. + +![Diagram illustrating MCU UUID usage for a conference. A central MCU node is connected to five participants: Alice, Bob, Sue, Carol, and Dave. Each participant is associated with a pair of values: {Participant, MCU}. The pairs are: {A, M} for Alice, {B, M} for Bob, {S, M} for Sue, {C, M} for Carol, and {D, M} for Dave. The diagram is labeled H.460.27(15)_F05.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +``` +graph TD; MCU[MCU] --- Alice[Alice]; MCU --- Bob[Bob]; MCU --- Sue[Sue]; MCU --- Carol[Carol]; MCU --- Dave[Dave]; Alice --- |"{A, M}"| MCU; Bob --- |"{B, M}"| MCU; Sue --- |"{S, M}"| MCU; Carol --- |"{C, M}"| MCU; Dave --- |"{D, M}"| MCU; +``` + +H.460.27(15)\_F05 + +Diagram illustrating MCU UUID usage for a conference. A central MCU node is connected to five participants: Alice, Bob, Sue, Carol, and Dave. Each participant is associated with a pair of values: {Participant, MCU}. The pairs are: {A, M} for Alice, {B, M} for Bob, {S, M} for Sue, {C, M} for Carol, and {D, M} for Dave. The diagram is labeled H.460.27(15)\_F05. + +**Figure 5 – MCU UUID usage for a conference** + +NOTE – It should not be assumed that if two or more calls utilize the same UUID value that the call(s) are a conference call on an MCU. In call transfer scenarios, for example, it is possible that two separate calls exist at the same time where the transferred endpoint, while working to carry out the call transfer, is using the same UUID on two separate calls simultaneously. Such instances are only temporary, but they do exist. It should only be assumed that the use of the same UUID value merely indicates some kind of association. + +# Bibliography + +- [b-IETF RFC SIP] IETF draft-ietf-insipid-session-id-14 (2015), *End-to-End Session Identification in IP-Based Multimedia Communication Networks*. +<> + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.460.3-200211-I_PDF-E/raw.md b/marked/H/T-REC-H.460.3-200211-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ba658895f3e560913c7d2cbbed76b955495009d4 --- /dev/null +++ b/marked/H/T-REC-H.460.3-200211-I_PDF-E/raw.md @@ -0,0 +1,279 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.460.3** + +(11/2002) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Supplementary services for multimedia + +--- + +**Circuit maps within H.323 systems** + +ITU-T Recommendation H.460.3 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| SYSTEMS AND TERMINAL EQUIPMENT FOR AUDIOVISUAL SERVICES | H.300–H.399 | +| SUPPLEMENTARY SERVICES FOR MULTIMEDIA | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.460.3** + +## **Circuit maps within H.323 systems** + +## **Summary** + +This Recommendation specifies a mechanism that allows a PSTN – H.323 Gateway to report circuit service and usage status to a Gatekeeper using the circuit status map parameter. Individual PSTN circuits on the Gateway may be taken out-of-service by a provisioning command from service personnel or when an ISUP out-of-service or blocking message is received from the adjacent PSTN switch. In this case, the Gateway will be able to report the current circuit status to the Gatekeeper so that it may select only from available circuits for outgoing calls through that Gateway. + +###### **Source** + +ITU-T Recommendation H.460.3 was prepared by ITU-T Study Group 16 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 November 2002. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2003 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|---|---------------------------------------------|---| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Abbreviations..... | 1 | +| 4 | Capability advertisement ..... | 2 | +| 5 | Circuit Status report..... | 2 | +| 6 | Circuit Status Map parameter ..... | 3 | +| 7 | Circuit Status Map ASN.1 definition ..... | 3 | +| 8 | Description of ASN.1 types and fields ..... | 4 | + + + +## Circuit maps within H.323 systems + +## 1 Scope + +H.323 provides the ability for a Gateway to report call capacity information in the callCapacity structure to a Gatekeeper to support routing of calls to that Gateway. The H.323 destinationCircuitId field as defined in ITU-T Rec. H.225.0 provided the means for a Gatekeeper to select a trunk group and circuit on a Gateway for the outgoing call through that Gateway. + +However, the service state of individual PSTN circuits in trunk groups on a Gateway cannot be reported to the Gatekeeper. This means that the Gatekeeper cannot do proper circuit selection because it does not know the service state of circuits on the Gateway. Individual PSTN circuits on the gateway may be taken out-of-service by a provisioning command from service personnel, or when an ISUP out-of-service or blocking message is received from the adjacent PSTN switch. In this case, the Gatekeeper will route the call to the Gateway because it knows that circuits are available (from callCapacity) on that Gateway, but not which circuits are in-service. When this occurs, the call will be rejected by the Gateway. This consumes network resources unnecessarily and will potentially increase post-dial delay. To solve the problem, this Recommendation provides the means for a Gateway to send circuit service state and usage status to a Gatekeeper. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation H.323 (2000), *Packet-based multimedia communications systems*. +- [2] ITU-T Recommendation H.225.0 (2000), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- [3] ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*. + +## 3 Abbreviations + +This Recommendation uses the following abbreviations: + +- ISUP ISDN User Part +- PER Packed Encoding Rules +- RAS Registration, Admission and Status +- RCF Registration Confirmation + +## 4 Capability advertisement + +A Gatekeeper signals its support for the capability to accept circuit service and usage status notifications from a Gateway by advertising the capability in the **featureSet.supportedFeatures** field of the RCF message. The capability is indicated with the feature identifier shown in Table 1 as a **supportedFeatures** element and without **parameters**. + +## 5 Circuit Status report + +A PSTN – H.323 Gateway may report circuit service and usage status to a Gatekeeper using the circuit status parameter. The circuit status may be reported when a Gateway registers with the Gatekeeper, when circuit service state changes occur as a result of maintenance actions on the part of operations personnel, or when an ISUP Blocking message is received. + +A Gateway may report its circuit status to a Gatekeeper in H.225.0 RAS and call signalling messages. + +The Circuit Status Map parameter is transported as follows in the H.225.0 RAS and call signalling (Q.931) messages using the generic extensibility framework: + +- When sending the Circuit Status Map parameter in the call signalling messages, the CircuitStatus shall be coded in the genericData parameter in the H.225.0 H323-UU-PDU in the User-user Information Element. +- When sending the Circuit Status Map parameter in the RAS messages, the CircuitStatus shall be coded in the genericData parameter in the request parameter of the H.225.0 RasMessage. + +The genericData parameter indicates the circuitStatus feature and contains a circuitStatus parameter. + +If there are a large number of circuits on a Gateway the circuit status may be sent in several H.225.0 messages. + +Table 1 defines the Circuit Status feature. + +**Table 1/H.460.3 – Report of Circuit Status from a gateway to a gatekeeper** + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------| +| Feature name: | Circuit Status | +| Feature Description: | This feature allows an H.323 Gateway to report circuit service and usage status to a Gatekeeper. | +| Feature identifier type: | Standard | +| Feature identifier value: | 3 | + +## 6 Circuit Status Map parameter + +Table 2 defines the Circuit Status Map parameter. + +**Table 2/H.460.3 – Circuit Status Map parameter** + +| | | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name: | Circuit Status Map | +| Parameter description: | This is the data sent in H.225.0 RAS and Call Signalling messages to indicate circuit status. The content is a raw field consisting of the ASN.1 PER encoded CircuitStatusMap as specified in the ASN.1 below. | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 1 | +| Parameter type: | Raw | +| Parameter cardinality: | Once and only once | + +## 7 Circuit Status Map ASN.1 definition + +The Circuit Status Map definition used within the GenericData is shown below. + +``` +CIRCUIT-STATUS-MAP DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +IMPORTS + CircuitIdentifier + FROM H323-MESSAGES; + +CircuitStatus ::= SEQUENCE -- root for Circuit Status Map ASN.1 +{ + circuitStatusMap SEQUENCE OF CircuitStatusMap OPTIONAL, + ... +} + +CircuitStatusMap ::= SEQUENCE +{ + statusType CircuitStatusType, + baseCircuitID CircuitIdentifier, + range INTEGER (0..4095), + status OCTET STRING, + ... +} + +CircuitStatusType ::= CHOICE +{ + serviceStatus NULL, -- status: 0 = out-of-service, 1 = in-service + busyStatus NULL, -- status: 0 = free, 1 = in-use + ... +} + +END +``` + +## 8 Description of ASN.1 types and fields + +**CircuitStatusMap** – The CircuitStatusMap consists of a statusType field, a baseCircuitId field, a range field and a status field: + +#### a) *statusType* + +This is the type of status represented by the following status field. This includes serviceStatus that indicates whether the circuit is available for service and busyStatus that indicates whether the circuit is currently being used for a connection. + +#### b) *baseCircuitId* + +This identifies the first circuit to which the range of status bits contained in the status field applies. + +#### c) *range* + +The number represented by the range code + 1 indicates the range of circuits affected by the CircuitStatusMap. This is in the range from 0 to 4095. + +#### d) *status* + +The status field contains from 0 to 4096 status bits numbered from 0 to 4095. Status bit 0 is located in the most significant bit position of the first status field octet. Other status bits follow in numerical order. The number of relevant status bits in a given status field is equal to range + 1. + +Each status bit is associated with a circuit such that status bit n is associated with circuit m + n, where m is the circuit identified in the baseCircuitId field. + +If the statusType indicates serviceStatus the circuit status bits are coded as follows: + +- 0 out-of-service; +- 1 in-service. + +If the statusType indicates busyStatus the circuit status bits are coded as follows: + +- 0 free; +- 1 in-use. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.460.8-200211-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.460.8-200211-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/H/T-REC-H.460.8-200211-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/H/T-REC-H.460.8-200211-I_PDF-E/raw.md b/marked/H/T-REC-H.460.8-200211-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6b8f0b34d552956d71b77fdf94dff94a75ddf9dc --- /dev/null +++ b/marked/H/T-REC-H.460.8-200211-I_PDF-E/raw.md @@ -0,0 +1,235 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.460.8** + +(11/2002) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Supplementary services for multimedia + +--- + +**Querying for alternate routes within H.323 +systems** + +ITU-T Recommendation H.460.8 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| SYSTEMS AND TERMINAL EQUIPMENT FOR AUDIOVISUAL SERVICES | H.300–H.399 | +| SUPPLEMENTARY SERVICES FOR MULTIMEDIA | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation H.460.8** + +## **Querying for alternate routes within H.323 systems** + +## **Summary** + +This Recommendation specifies a mechanism that allows endpoints to query a Gatekeeper or Border Element for routes and alternate routes multiple times for a single call. While querying the Gatekeeper or Border Element multiple times may increase the time required to establish the call, it is expected that most calls will establish with a single query. However, this expectation does not always prove to be the case. This Recommendation is focused on the cases where the call cannot complete to the first provided route to a destination. In such cases, the endpoint may query for alternate routes. The alternate routes may also include different source or destination alias information, different security tokens, or other information that may have been expensive or too time consuming to produce and/or provide in the initial query. + +###### **Source** + +ITU-T Recommendation H.460.8 was prepared by ITU-T Study Group 16 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 November 2002. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2003 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|---|--------------------------------------|---| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Abbreviations..... | 1 | +| 4 | Capability advertisement ..... | 2 | +| 5 | Indication of alternate routes ..... | 3 | +| 6 | Querying for alternate routes ..... | 3 | + + + +## Querying for alternate routes within H.323 systems + +## 1 Scope + +Due to the dynamic nature of most packet-based networks and resources on those networks, it is entirely possible that resources that are available at the time that an endpoint queries a Gatekeeper, or that a Border Element is consulted in order to determine a route to a particular destination that the destination (or route to reach said destination), is no longer acceptable or reachable. It is also possible that, due to conditions on the network that are outside the view of the Gatekeeper or Border Element, a particular destination is not reachable, or is out of service, at the time that the route was initially provided to the calling endpoint. + +To address this issue, this Recommendation provides a means for an entity to query a Gatekeeper or Border Element multiple times in order to get alternate routes to destinations. This Recommendation does not replace the "alternate endpoint" facilities within H.323, or the ability to provide multiple routes as part of the route information provided by the Border Element, but is intended to supplement those facilities. + +There are a number of reasons why an entity may wish to take advantage of the ability to perform multiple queries when attempting to establish communication between the calling and called entities. As examples, different destinations may require different source or destination information to appear in the Setup message. In addition, it is possible that unique security information may be required for each destination and generating that security information for each alternate destination upon the initial query may be considered too expensive, especially if calls are expected to usually succeed upon the first query. + +The mechanisms described in this Recommendation are suitable for Gatekeeper or Border Element communication as defined in ITU-T Recs H.323 and H.225.0, respectively. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation H.323 (2000), *Packet-based multimedia communications systems*. +- [2] ITU-T Recommendation H.225.0 (2000), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. + +## 3 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-----|----------------------| +| ACF | Admission Confirm | +| ARQ | Admission Request | +| CRV | Call Reference Value | +| DRQ | Disengage Request | + +| | | +|-----|----------------------| +| LCF | Location Confirm | +| LRQ | Location Request | +| RCF | Registration Confirm | +| RRQ | Registration Request | + +## 4 Capability advertisement + +Endpoints capable of querying the Gatekeeper for alternate routes shall advertise that capability in all RRQ messages sent to the Gatekeeper, except lightweight RRQ messages. The capability shall not be advertised in lightweight RRQ messages. + +A Gatekeeper may signal support for this capability within the LRQ message when sending LRQs to remote Gatekeepers. A Gatekeeper using the direct call model for a particular call should only advertise this capability to its peer Gatekeeper if the endpoint originating that call had indicated support for querying for alternate routes and provided the Call Identifier in the ARQ message. If a Gatekeeper is simply forwarding an LRQ received from another Gatekeeper, it may also include the advertisement of this feature if present in the received LRQ. Advertising this capability in the LRQ when the endpoint does not have a means of querying for alternate routes may result in a smaller route set being returned by the remote Gatekeeper, whereas perhaps alternate endpoint information would have otherwise been provided. + +A Border Element may signal support for this capability in each **AccessRequest** message sent to another Border Element. A Border Element should only advertise this capability if it knows, by some means, that the endpoint that originated the call indicated support for this feature. Support for this capability by the endpoint may be assumed, for example, if the Border Element also has Gatekeeper functionality and/or receives an LRQ that contains this capability. Advertising this capability in the **AccessRequest** message, when the source endpoint does not have a means of querying for alternate routes, may result in smaller routing information being returned by the remote Border Element, whereas more complete route information would have been returned had the capability not been advertised. + +An endpoint signals support by advertising the capability in the **featureSet.supportedFeatures** field of the RRQ message. A Border Element signals support for this capability by advertising this capability in the **common.featureSet.supportedFeatures** field. A Gatekeeper signals support for this capability to another Gatekeeper by advertising the capability in the **featureSet.supportedFeatures** field of the LRQ message. The capability is indicated with the feature identifier shown in Table 1 as a **supportedFeatures** element and without **parameters**. + +**Table 1/H.460.8 – Indication of the ability to Query for Alternate Routes** + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Feature name: | Querying for Alternate Routes | +| Feature Description: | This feature allows an H.323 entity to query a Gatekeeper or Border Element for alternate routes in the event that the previously provided route is not usable. | +| Feature identifier type: | Standard | +| Feature identifier value: | 8 | + +# 5 Indication of alternate routes + +A Gatekeeper or Border Element that wishes to signal the availability of alternate routes for a call to another Gatekeeper, Border Element, or endpoint, as appropriate, and having learned that the peer entity supports the capability of querying for alternate routes, may do so by signalling the capability shown in Table 1 in the ACF, LCF, or **AccessConfirmation** message. The capability shall be signalled in the **genericData** field of the aforementioned messages, not in the **featureSet** field. + +If this capability value is not contained within the **genericData** structure, it indicates that either there are no additional alternate routes, or that the entity does not support the ability to query for alternate routes. In either case, the requesting entity shall not submit new queries for the same call if the route returned cannot be reached for any reason. + +## 6 Querying for alternate routes + +An entity, having learned that its peer may provide an alternate set of routes, and having need to submit a new query, shall send a new request message to its peer. This new request message shall not have the same request sequence number as the previous query. The request shall contain a **genericData** element advertising the capability shown in Table 1 and shall include a **parameters** value, as shown in Table 2. + +**Table 2/H.460.8 – Parameter to indicate Query Count** + +| | | +|-----------------------------|---------------------------------------------------------------| +| Parameter name: | Query Count | +| Parameter description: | This value indicates the number of queries performed thus far | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 1 | +| Parameter type: | number8 | +| Parameter cardinality: | Once and only once | + +When an entity queries a peer for a route for a call the first time, this parameter shall not be present, but an internal value of 0 shall be maintained for the request. In addition, the Call Identifier for the call shall be present. In case the Call Identifier is not available to the Gatekeeper or Border Element, the said entity shall not attempt to utilize the functionality defined within this Recommendation, as the Call Identifier is the key used for associating subsequent queries. + +When an entity issues a subsequent query for a call, the value of the query count shall be incremented by one and shall be present. Thus, the second time a request is made for a call, this parameter shall be included with a value of 1. This value may be used by the recipient as an index value into a table of alternate routes. The requesting entity shall also include the same Call Identifier and, in the case of an ARQ, the same CRV as used in the initial request. + +An endpoint that queries for alternate routes for a call shall not send a DRQ message prior to transmitting subsequent ARQ message(s). A DRQ shall only be transmitted once the call has been completed or once all attempts to establish the call have failed. Additionally, the subsequent ARQ message(s) shall contain, whenever the information is available, a **CallTerminationCause** structure containing the reason for the Release Complete message of the previously failed call attempt. That information may be utilized by the entity providing the routes and should be propagated between Gatekeepers and Border Elements where possible. The Call Termination Cause shall be carried as an element of **parameters** as shown in Table 3. + +**Table 3/H.460.8 – Parameter to contain the Call Termination Cause** + +| | | +|-----------------------------|------------------------------------------------------------------------------------------------------| +| Parameter name: | Call Termination Cause | +| Parameter description: | The CallTerminationCause structure contains the reason for the previously failed call attempt | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 2 | +| Parameter type: | raw | +| Parameter cardinality: | Zero or one | + +All other parameters present, but not listed in this clause, shall be ignored and shall not be treated as errors. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.460.9-200211-I_PDF-E/raw.md b/marked/H/T-REC-H.460.9-200211-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c9c87d23a6bb6b3f0efc61b386949f63fb23ca64 --- /dev/null +++ b/marked/H/T-REC-H.460.9-200211-I_PDF-E/raw.md @@ -0,0 +1,480 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.460.9** + +(11/2002) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +Supplementary services for multimedia + +--- + +**Support for online QoS-monitoring reporting +within H.323 systems** + +ITU-T Recommendation H.460.9 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| SYSTEMS AND TERMINAL EQUIPMENT FOR AUDIOVISUAL SERVICES | H.300–H.399 | +| SUPPLEMENTARY SERVICES FOR MULTIMEDIA | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation H.460.9** + +## **Support for online QoS-monitoring reporting within H.323 systems** + +## **Summary** + +This Recommendation describes the procedures and the signalling protocol for reporting online Quality of Service (QoS) monitoring on a call-by-call basis within the H.323 system. This monitoring is performed by the end-points based on real time traffic statistics and reported to the gatekeeper at periodic intervals, or at call conclusion. These procedures use the H.323 Generic Extensibility Framework (GEF) and therefore do not require any changes to the base standards. + +## **Source** + +ITU-T Recommendation H.460.9 was prepared by ITU-T Study Group 16 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 November 2002. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2003 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|-------------------------------------------------------------------------|---| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 2.1 | Normative references..... | 1 | +| 2.2 | Informative reference ..... | 2 | +| 3 | Abbreviations and Acronyms ..... | 2 | +| 4 | Feature description..... | 2 | +| 4.1 | Negotiation of the feature ..... | 2 | +| 4.2 | The QoS-monitoring reporting endpoint procedure ..... | 3 | +| 4.2.1 | Initiation of the procedure ..... | 3 | +| 4.2.2 | Continuation of the procedure ..... | 3 | +| 4.2.3 | Termination of the procedure ..... | 3 | +| 4.2.4 | Single QoS-monitoring report only at the end of the call ..... | 4 | +| 4.3 | The QoS-monitoring reporting gatekeeper (Annex G/H.225.0) procedure ... | 4 | +| 4.4 | Generic data usage..... | 4 | +| 4.5 | Extensibility..... | 5 | +| 5 | Description of ASN.1 types and fields ..... | 5 | +| 5.1 | End-to-End delay measures ..... | 6 | +| 5.2 | Packet loss measures ..... | 6 | +| 5.3 | Throughput measures ..... | 6 | +| 5.4 | Network jitter measures..... | 6 | +| | Annex A – ASN.1 definitions ..... | 7 | + + + +# Support for online QoS-monitoring reporting within H.323 systems + +# 1 Scope + +This Recommendation describes the procedures and the signalling protocol based on H.225.0/RAS for reporting of per call, online Quality of Service (QoS) monitoring. + +QoS for real-time traffic like Voice over IP (VoIP) relies on the QoS of the underlying IP-network. The VoIP user may experience bad voice quality if the network does not meet the requirements for real-time traffic in respect to end-to-end delay, network jitter, and packet loss. Currently, dedicated network probes have to be installed in the network. This Recommendation proposes that the H.323 endpoints capture QoS-monitoring measures, as provided by means of Real-time Transport Control Protocol (RTCP – RFC 1889) per call for a period of time, and forward this information periodically and/or at the end of the call to the gatekeeper. + +NOTE – RTCP conveys feedback about RTP streams directly between endpoints; the gatekeeper does not get this information. Therefore, the gatekeeper has no way of judging the quality of media channels directly. + +At the gatekeeper this information can be processed and registered per call, e.g. in the Call Detail Record (CDR), or be forwarded to a dedicated network element for post processing. The registration and post processing of these reports are beyond the scope of this Recommendation. Based on this information the service provider can take appropriate actions if these reports show insufficient QoS for real-time traffic at certain communication relations. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +## 2.1 Normative references + +- [1] ITU-T Recommendation H.323 Version 4 (2000), *Packet-based multimedia communications systems*. +- [2] ITU-T Recommendation H.225.0 Version 4 (2000), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- [3] ITU-T Recommendation X.680 (2002), *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation*. +- [4] ITU-T Recommendation X.691 (2002), *Information technology – ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)*. +- [5] ITU-T Recommendation H.460.1 (2002), *Guidelines for the use of the Generic Extensible Framework (GEF)*. +- [6] ITU-T Recommendation H.225.0 Annex G (1999), *Communication between administrative domains*. +- [7] ITU-T Recommendation H.501 (2002), *Protocol for mobility management and intra/inter-domain communication in multimedia systems*. + +[8] IETF RFC 1889 (1996), *RTP: A Transport Protocol for Real-Time Applications*. + +## 2.2 Informative reference + +– IETF RFC 1305 (1992), *Network Time Protocol (Version 3) Specification, Implementation and analysis*. + +# 3 Abbreviations and Acronyms + +This Recommendation uses the following abbreviations: + +| | | +|-------|------------------------------------| +| ACF | (RAS) Admission Confirm | +| ARQ | (RAS) Admission Request | +| ASN.1 | Abstract Syntax Notation One | +| CDR | Call Detail Record | +| DCF | (RAS) Disengage Confirm | +| DRQ | (RAS) Disengage Request | +| GEF | Generic Extensible Framework | +| IETF | Internet Engineering Task Force | +| IRR | (RAS) Information Request Response | +| NTP | Network Time Protocol (RFC 1305) | +| PER | (ASN.1) Packed Encoding Rules | +| QoS | Quality of Service | +| RAS | Registration, Admission and Status | +| RCF | (RAS) Registration Confirm | +| RFC | Request for Comments | +| RR | (RTCP) Receiver Report | +| RRQ | (RAS) Registration Request | +| RTCP | RTP Control Protocol | +| RTP | Real-time Transport Protocol | +| RTT | Round Trip Time | +| SR | (RTCP) Sender Report | +| UDP | User Datagram Protocol | + +# 4 Feature description + +## 4.1 Negotiation of the feature + +Usage of the QoS-monitoring reporting feature is negotiated between endpoint and gatekeeper at call set-up time as part of the admission request procedure. For this purpose, an endpoint that supports this feature shall include the feature descriptor defined in 4.4 (see Table 1) in **featureSet.supportedFeatures** of the ARQ message. + +If the gatekeeper also supports this feature, it may include the same feature descriptor in the **featureSet** of the ACF message, either as **neededFeature** if the feature is required for the call, as **desiredFeature** if the feature is only desired, or as **supportedFeature** if the gatekeeper does not + +care. Omission of the feature indicator from the ACF message means that this feature is not supported or its use is not wanted for this call. + +An endpoint may also indicate support of this feature when registering with a gatekeeper, by including the feature descriptor in the RRQ message in the same way as described above for ARQ. Likewise, a gatekeeper may indicate its support by including the feature descriptor in the RCF message. + +## 4.2 The QoS-monitoring reporting endpoint procedure + +### 4.2.1 Initiation of the procedure + +The procedure is initiated during the H.225.0 Admission procedure. The Admission Confirm (ACF) message contains the following fields that will be set as part of the procedure: + +**featureSet** – Depending on the content of this field the endpoint: + +- shall include QoS-monitoring report parameters in the **genericData** field of IRR message(s) and/or the DRQ/DCF message if the feature is indicated in **neededFeatures**; +- should include QoS-monitoring report parameters in the **genericData** field of IRR message(s) and/or the DRQ/DCF message if the feature is indicated in **desiredFeatures**; +- may include QoS-monitoring report parameters in the **genericData** field of IRR message(s) and/or the DRQ/DCF message if the feature is indicated in **supportedFeatures**; +- shall not include any QoS-monitoring report parameters in IRR or DRQ/DCF message(s) if the feature is not indicated at all in **featureSet**. + +**irrFrequency** – The frequency, in seconds, that the endpoint shall send Information Request Response (IRR) messages to the gatekeeper during a call. The frequency, in seconds, is an implementation – dependent time interval for gathering QoS-monitoring statistics. Since RTCP packets are generated at a rate of one packet per five seconds for unicast point-to-point connections at a random variation of [0.5 ... 1.5] times, the time interval should not be less than eight seconds in order to guarantee that the statistics will be meaningful. + +### 4.2.2 Continuation of the procedure + +For each media connection a unidirectional RTP data flow is generated by the endpoint. At a separate transport address (default: UDP/RTP-port number plus one) RTCP messages are exchanged containing feedback information from which network transport service QoS can be derived. See RFC 1889 for details regarding RTP and RTCP. For the time interval specified in **irrFrequency** of the Admission Confirm (ACF) message and conveyed during the initiation procedure, this information shall be gathered and statistically processed in terms of short-term and long-term measures. The resulting values shall be populated and included in the **genericData** field of Information Request Response (IRR) messages that are issued to the gatekeeper at a frequency of **irrFrequency**. + +If the optional parameter **qosMonitoringFinalOnly** was included when the feature was initiated, then no QoS monitoring reporting data shall be included in any IRR messages. + +NOTE – If no **irrFrequency** value was returned in the ACF message, no unsolicited IRR messages and thus no periodic QoS-monitoring reports will be sent, but a final report will be included in DRQ or DCF if the QoS-monitoring reporting feature was initiated. + +### 4.2.3 Termination of the procedure + +When the call is released, either a Disengage Request (DRQ) message is issued by the endpoint that carries in the **genericData** field the information for the final time interval, or the endpoint includes this information in the DCF message if it received a DRQ message from the gatekeeper. + +### 4.2.4 Single QoS-monitoring report only at the end of the call + +In order to allow an endpoint to send only a summary QoS-monitoring report at the end of the call, regardless of the value of **irrFrequency**, parameter **qosMonitoringFinalOnly** may be included when negotiating the feature. The **genericData** for QoS-monitoring reporting will then be included only in the DRQ or DCF message. + +## 4.3 The QoS-monitoring reporting gatekeeper (Annex G/H.225.0) procedure + +Since one gatekeeper obtains information only from H.323 endpoints registered to it, it is necessary to exchange complementary QoS-monitoring report information for bidirectional media connections between the two gatekeepers involved in a particular call. This can be done by means of the usage information exchange procedures specified in Annex G/H.225.0, by including the **genericData** for QoS-monitoring reporting in **UsageIndication** messages. The data sent by a gatekeeper in a QoS-monitoring report are those gathered by this gatekeeper locally for a specific call from an endpoint's QoS-monitoring reports. + +Exchange of **genericData** for QoS-monitoring reporting is negotiated between gatekeepers on a per-call basis as described in 4.1 above, except that **UsageRequest/UsageConfirmation** messages are used rather than ARQ/ACF. If reports are required in both directions, the usage information exchange procedures are initiated independently for each direction. The gatekeeper requesting QoS-monitoring reports indicates in the **UsageRequest** message when **UsageIndication** messages shall be sent; periodically or only at the end of the call. The interval for sending periodic reports may be different for each direction, and also different from the interval for IRR messages. + +Refer to ITU-T Rec. H.501 for details regarding the usage report messages. + +## 4.4 Generic data usage + +The Generic Extensibility Framework (GEF) shall be used to convey QoS-monitoring reports with H.225.0/RAS between H.323 endpoint and gatekeeper, and/or between gatekeepers as described in tabular form in the following. + +The reports may include: + +- End-to-end delay as sender (estimated from round trip time for RTCP packets); +- Packet Loss and Network Jitter as receiver; +- Optionally additional data, e.g. for a specific profile (see 4.5 for more details). + +Each report consists of a single parameter in raw format, containing a PER-encoded ASN.1 structure as specified in Annex A. + +**Table 1/H.460.9 – Tabular specification of the QoS-monitoring reporting feature** + +| | | +|---------------------------|--------------------------| +| Feature name: | QoS-monitoring Reporting | +| Feature Description: | QoS-monitoring reporting | +| Feature identifier type: | Standard | +| Feature identifier value: | 9: qosMonitoringReportID | + +**qosMonitoringReportID**: Identifies the QoS-monitoring report feature using the standard field of **GenericIdentifier** with a unique integer value. + +**Table 2/H.460.9 – Tabular specification of the qosMonitoringFinalOnly parameter** + +| | | +|-----------------------------|----------------------------------------------------| +| Parameter name: | qosMonitoringFinalOnly | +| Parameter description: | Requests QoS-monitoring report at end of call only | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 0 | +| Parameter type: | no content | +| Parameter cardinality: | Zero or one | + +**qosMonitoringFinalOnly:** If included, QoS-monitoring reports will only be sent in the DRQ/DCF message when the call finishes. + +**Table 3/H.460.9 – Tabular specification of the QoS-monitoring reporting parameter** + +| | | +|-----------------------------|-------------------------------| +| Parameter name: | qosMonitoringReportData | +| Parameter description: | QoS-monitoring reporting data | +| Parameter identifier type: | Standard | +| Parameter identifier value: | 1 | +| Parameter type: | Raw: ASN.1 PER | +| Parameter cardinality: | Zero or one | + +**qosMonitoringReportData:** This data is sent in H.225.0/RAS messages; IRR, DRQ/DCF and optionally also in H.501 **UsageIndication** messages to notify the QoS-monitoring information for all established media connections. The content of this parameter is a raw field consisting of the ASN.1 PER encoded **qosMonitoringReportData** as specified in the ASN.1 notation below (see Annex A). + +## 4.5 Extensibility + +The ASN.1 data structure in Annex A provides for extensibility in three ways: + +- The ASN.1 types are defined as extensible in the usual way, for additions in later versions of this Recommendation. +- Non-standard data may be included in various places, analogous to H.225.0. This allows implementation-specific data to be transparently conveyed. +- An opaque container for extensions may contain additional data, e.g. for specific applications or payload profiles. + +The data that may go into the extensions container can be specified by various means – an annex to this Recommendation, another Recommendation, a non-standard specification etc. Each extension is uniquely identified by a **GenericIdentifier** and contains its data in form of an octet string. Extensions defined in the context of this Recommendation may use **GenericIdentifiers** of type standard, while other extensions will use type oid (i.e. object identifiers). + +# 5 Description of ASN.1 types and fields + +Only fields introduced by this Recommendation are explained here. Other fields are adopted from H.225.0. For the detailed determination of the values, please refer to Annex A/H.225.0. + +Some values can or will only be reported by a media sender or receiver. For bidirectional media connections, the complete picture will be obtained only if the information from each side is combined. + +## 5.1 End-to-End delay measures + +These measurements can only be performed by a media sender. Therefore, this information can only be provided by the media sender. + +**EstimatedEnd2EndDelay** – Value derived from the RTCP RTT (see Figure A.2/H.225.0 for the determination of RTT) divided by 2. Only the middle 32 bits of the 64-bit NTP timestamp are used, as described in A.4/H.225.0. + +**meanEstimatedEnd2EndDelay** – Mean value of **EstimatedEnd2EndDelay** for the currently reported time interval. + +**worstEstimatedEnd2EndDelay** – Worst case value of **EstimatedEnd2EndDelay** for the currently reported time interval. + +## 5.2 Packet loss measures + +This information shall only be provided by the media receiver because it reflects the QoS as perceived by the user receiving the media. + +**cumulativeNumberOfPacketsLost** – Cumulative number of packets lost of last sent RTCP Receiver Report (RR). + +**packetLostRate** – Difference between Cumulative number of packets lost of last sent RR of last time interval and last sent RR of currently reported time interval per second. + +**fractionLostRate** – Sum of Fraction lost of all sent RRs for the currently reported interval per second. + +## 5.3 Throughput measures + +These measurements can only be performed by a media receiver. Therefore, this information can only be provided by a media receiver. + +**estimatedThroughput** – Difference between Sender's packet count of last received RTCP Sender Report (SR) of last time interval and last received SR of currently reported time interval reduced by **packetLostRate** (see 5.2) multiplied with the average packet size of the packet (excluding the link layer protocol) per second. + +NOTE – The packet size may differ during media transmission. Only the maximum number of media samples is fixed. + +## 5.4 Network jitter measures + +This information shall only be provided by the media receiver because it reflects the QoS as perceived by the user receiving the media. + +**CalculatedJitter** – Corresponds to Interarrival Jitter of sent RTCP Receiver Report (RR) in timestamp units presented as 32-bit integer value of 64-bit NTP timestamp (see A.4/H.225.0). + +**meanJitter** – Average value of **CalculatedJitter** calculated from all sent RRs for the currently reported time interval. + +**worstJitter** – Worst case value of **CalculatedJitter** from all sent RRs for the currently reported time interval. + +# Annex A + +## ASN.1 definitions + +``` +QOS-MONITORING-REPORT DEFINITIONS AUTOMATIC TAGS ::= +BEGIN +IMPORTS + NonStandardParameter, + TransportChannelInfo, + CallIdentifier, + CallReferenceValue, + ConferenceIdentifier, + BandWidth, + GenericIdentifier +FROM H323-MESSAGES; + +EstimatedEnd2EndDelay ::= INTEGER (0..4294967295) + -- middle 32 bits of 64 bit NTP timestamp + +CalculatedJitter ::= INTEGER (0..4294967295) + -- measured in timestamp units + +Extension ::= SEQUENCE +{ + extensionId GenericIdentifier, + extensionContent OCTET STRING OPTIONAL, + ... +} + +RTCPMeasures ::= SEQUENCE +{ + rtpAddress TransportChannelInfo, + rtcpAddress TransportChannelInfo, + sessionId INTEGER (1..255), + nonStandardData NonStandardParameter OPTIONAL, + mediaSenderMeasures SEQUENCE + { + worstEstimatedEnd2EndDelay EstimatedEnd2EndDelay OPTIONAL, + meanEstimatedEnd2EndDelay EstimatedEnd2EndDelay OPTIONAL, + ... + } OPTIONAL, + mediaReceiverMeasures SEQUENCE + { + cumulativeNumberOfPacketsLost INTEGER (0..4294967295) OPTIONAL, + packetLostRate INTEGER (0..65535) OPTIONAL, + worstJitter CalculatedJitter OPTIONAL, + estimatedThroughput BandWidth OPTIONAL, -- in 100s of bits + fractionLostRate INTEGER (0..65535) OPTIONAL, + meanJitter CalculatedJitter OPTIONAL, + ... + } OPTIONAL, + extensions SEQUENCE OF Extension OPTIONAL, + ... +} +``` + +``` + +PerCallQoSReport ::= SEQUENCE +{ + nonStandardData NonStandardParameter OPTIONAL, + callReferenceValue CallReferenceValue, + conferenceID ConferenceIdentifier, + callIdentifier CallIdentifier, + mediaChannelsQoS SEQUENCE OF RTCPMeasures OPTIONAL, + -- one element per media channel + extensions SEQUENCE OF Extension OPTIONAL, + ... +} + +QosMonitoringReportData ::= CHOICE +{ + periodic PeriodicQoSMonReport, -- included in IRR messages + final FinalQoSMonReport, -- included in DRQ/DCF message + interGK InterGKQoSMonReport, -- included in usageIndication message + ... +} + +PeriodicQoSMonReport ::= SEQUENCE +{ + perCallInfo SEQUENCE OF PerCallQoSReport, -- one element per call + extensions SEQUENCE OF Extension OPTIONAL, + ... +} + +FinalQoSMonReport ::= SEQUENCE +{ + mediaInfo SEQUENCE OF RTCPMeasures, -- one element per channel + nonStandardData NonStandardParameter OPTIONAL, + extensions SEQUENCE OF Extension OPTIONAL, + ... +} + +InterGKQoSMonReport ::= SEQUENCE +{ + mediaInfo SEQUENCE OF RTCPMeasures, -- one element per channel + nonStandardData NonStandardParameter OPTIONAL, + extensions SEQUENCE OF Extension OPTIONAL, + ... +} + +-- +-- H.460.9 Identifiers: -- +-- +qosMonitoringReportID GenericIdentifier ::= standard:9 +qosMonitoringFinalOnly GenericIdentifier ::= standard:0 +qosMonitoringReportData GenericIdentifier ::= standard:1 + +END -- of ASN.1 + +``` + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.501-200203-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.501-200203-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/H/T-REC-H.501-200203-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/H/T-REC-H.501-200203-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/H/T-REC-H.501-200203-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8550ff087c7b909ae641a50276d5ef84593fe013 --- /dev/null +++ b/marked/H/T-REC-H.501-200203-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6055a70704b66f08640c800f0315e5fc5afb30aa7549a4144823306c035fb27f +size 17813 diff --git a/marked/H/T-REC-H.501-200203-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/H/T-REC-H.501-200203-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86e7b43a3958f3233085c0aa0faff59e8d7bf271 --- /dev/null +++ b/marked/H/T-REC-H.501-200203-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c447f939cae3c9c64e1f611c56020984265ae426981884cfb0cb4196aa6fb5e +size 10933 diff --git a/marked/H/T-REC-H.501-200203-I_PDF-E/raw.md b/marked/H/T-REC-H.501-200203-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dbfaa6a924a311e65467d292e0d2e26fe43a0e5c --- /dev/null +++ b/marked/H/T-REC-H.501-200203-I_PDF-E/raw.md @@ -0,0 +1,1743 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.501** + +(03/2002) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Mobility and Collaboration procedures – Overview of +Mobility and Collaboration, definitions, protocols and +procedures + +--- + +**Protocol for mobility management and +intra/inter-domain communication in multimedia +systems** + +ITU-T Recommendation H.501 + +--- + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|--------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| SYSTEMS AND TERMINAL EQUIPMENT FOR AUDIOVISUAL SERVICES | H.300–H.399 | +| SUPPLEMENTARY SERVICES FOR MULTIMEDIA | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation H.501** + +# **Protocol for mobility management and intra/inter-domain communication in multimedia systems** + +## **Summary** + +The purpose of this Recommendation is to define messages and procedures for mobility management and for communication within and between domains of a mobile or non-mobile multimedia environment for the purpose of address resolution, user authentication, service data exchange, access authorization, call validation and usage reporting. + +## **Source** + +ITU-T Recommendation H.501 was prepared by ITU-T Study Group 16 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 March 2002. + +## **Keywords** + +Address resolution, administrative domains, authentication, authorization, H.225.0 Annex G, mobility management, multimedia systems, usage reporting. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|-----------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | Normative references..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Symbols and abbreviations ..... | 2 | +| 5 | Requirements ..... | 2 | +| 5.1 | Transport requirements..... | 2 | +| 5.2 | Security considerations..... | 3 | +| 5.3 | Addressing conventions..... | 3 | +| 5.4 | Address templates and descriptors ..... | 4 | +| 6 | Message definitions ..... | 4 | +| 6.1 | Descriptor ..... | 5 | +| 6.2 | Descriptor information ..... | 6 | +| 6.3 | Address template ..... | 6 | +| 6.3.1 | Pattern..... | 6 | +| 6.3.2 | Route information..... | 7 | +| 6.3.3 | Pricing information..... | 7 | +| 6.3.4 | Contact information..... | 8 | +| 6.4 | Common structures..... | 9 | +| 6.4.1 | AlternatePE..... | 9 | +| 6.4.2 | PartyInformation..... | 9 | +| 6.4.3 | CallInformation ..... | 10 | +| 6.4.4 | UserInformation ..... | 10 | +| 6.4.5 | Usage specification..... | 10 | +| 6.4.6 | Security Mode ..... | 11 | +| 6.5 | Service relationship ..... | 11 | +| 6.5.1 | Service Request ..... | 11 | +| 6.5.2 | Service Confirmation..... | 12 | +| 6.5.3 | Service Rejection..... | 13 | +| 6.5.4 | Service Release..... | 14 | +| 6.6 | Descriptor distribution..... | 14 | +| 6.6.1 | Descriptor Request ..... | 14 | +| 6.6.2 | Descriptor Confirmation..... | 14 | +| 6.6.3 | Descriptor Rejection..... | 14 | +| 6.6.4 | Descriptor ID Request ..... | 15 | +| 6.6.5 | Descriptor ID Confirmation ..... | 15 | +| 6.6.6 | Descriptor ID Rejection..... | 15 | + +| | Page | +|-----------------------------------------------|-------------| +| 6.6.7 Descriptor Update..... | 16 | +| 6.6.8 Descriptor Update Acknowledgement ..... | 16 | +| 6.7 Address resolution ..... | 16 | +| 6.7.1 Access Request..... | 16 | +| 6.7.2 Access Confirmation ..... | 17 | +| 6.7.3 Access Rejection ..... | 17 | +| 6.8 Request in Process..... | 18 | +| 6.9 Non-standard messages ..... | 18 | +| 6.9.1 Non-Standard Request..... | 18 | +| 6.9.2 Non-Standard Confirmation ..... | 18 | +| 6.9.3 Non-Standard Rejection ..... | 18 | +| 6.10 Unknown Message Response ..... | 19 | +| 6.11 Usage reports ..... | 19 | +| 6.11.1 Usage Request ..... | 19 | +| 6.11.2 Usage Confirmation..... | 19 | +| 6.11.3 Usage Rejection..... | 20 | +| 6.11.4 Usage Indication..... | 20 | +| 6.11.5 Usage Indication Confirmation ..... | 21 | +| 6.11.6 Usage Indication Rejection..... | 21 | +| 6.12 Validations..... | 22 | +| 6.12.1 Validation Request ..... | 22 | +| 6.12.2 Validation Confirmation..... | 22 | +| 6.12.3 Validation Rejection..... | 22 | +| 6.13 Authentication ..... | 23 | +| 6.13.1 Authentication Request ..... | 23 | +| 6.13.2 Authentication Confirmation..... | 23 | +| 6.13.3 Authentication Rejection..... | 23 | +| Annex A – Message Syntax..... | 24 | + +# Protocol for mobility management and intra/inter-domain communication in multimedia systems + +# 1 Scope + +This Recommendation describes a protocol for communication between logical elements of a multimedia packet network to allow the completion of calls to and from users managed by such logical elements. This protocol can be used in mobile and non-mobile environments for the purpose of address resolution, user authentication, service data exchange, access authorization, call validation and usage reporting. These capabilities enable the protocol to be used for mobility management in mobile environments. + +The general procedure is for logical elements to exchange information regarding the location of users or endpoints, in the form of addresses each administrative domain can resolve. Addresses can be specified in a general manner or in an increasingly specific manner. Additional information allows elements within an administrative domain to determine the most appropriate administrative domain to serve as the destination for the call. Logical elements may control access to their exposed addresses, and require reports on the usage made during calls to those addresses. + +Other Recommendations will specify how the protocol defined in this Recommendation is used by particular applications. It is not necessary for an application to implement the full protocol. The application can select from the messages and procedures those relevant to its requirements. + +# 2 Normative references + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation E.164 (1997), *The international public telecommunication numbering plan*. +- ITU-T Recommendation H.225.0 Version 4 (2000), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.235 Version 2 (2000), *Security and encryption for H-series (H.323 and other H.245-based) multimedia terminals*. +- ITU-T Recommendation H.323 Version 4 (2000), *Packet-based multimedia communications systems*. +- ITU-T Recommendation X.680 (1997), *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation*. +- ITU-T Recommendation X.691 (1997), *Information technology – ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)*. +- IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol*. +- IETF RFC 2402 (1998), *IP Authentication Header*. +- IETF RFC 2406 (1998), *IP Encapsulating Security Payload (ESP)*. + +- ISO 4217:2001, *Codes for the representation of currencies and funds*. + +# 3 Definitions + +This Recommendation defines the following terms: + +- 3.1 administrative domain:** An administrative domain is a collection of logical and physical entities administered by one administrative entity. An administrative domain can consist of one or more zones. +- 3.2 gatekeeper:** A logical element that provides specific services (number translation, access control, etc.) to other entities within an administrative domain (see also ITU-T Rec. H.323). +- 3.3 logical element:** An entity with defined functionality in a network. Logical elements do not impose any requirements on their provision; their functionality can be implemented in any suitable way in hard- or software. +- 3.4 peer element:** A logical element which originates or terminates signalling messages defined in this Recommendation. Examples are H.225.0 Annex G border elements or H.323 gatekeepers. +- 3.5 zone:** The subset of entities of an administrative domain under the control of a single gatekeeper. + +# 4 Symbols and abbreviations + +This Recommendation uses the following abbreviations: + +- AD Administrative domain +- DH Diffie-Hellman key agreement protocol (ITU-T Rec. X.509) +- DNS Domain Name System +- IP Internet Protocol +- OID Object Identifier +- PDU Protocol Data Unit +- RAS Registration, Admission and Status protocol +- SCN Switched Circuit Network +- TCP Transmission Control Protocol +- TPKT Transport Packet +- UDP User Datagram Protocol +- URL Uniform Resource Locator +- UTC Universal Time Coordinated + +# 5 Requirements + +## 5.1 Transport requirements + +Messages may be sent over an unreliable transport service (e.g. UDP) or a reliable transport service (e.g. TCP) to a well-known address. On IP networks, the well-known port (2099) should be used for both TCP and UDP, unless another port has been communicated to the sender. Elements shall listen on both TCP and UDP ports. + +When messages are sent over the reliable transport service, whole messages shall be sent within the boundaries defined by the reliable transport protocol data unit (PDU). (In IP implementations, for instance as outlined in H.225.0 Appendix IV, this PDU is defined by TPKT; see Figure 1. Each H.501 PDU contains a single message defined in this Recommendation.) + +![Figure 1/H.501 – TCP transport diagram showing a sequence of alternating TPKT and H.501 PDU blocks.](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +The diagram shows a horizontal sequence of alternating blocks. It starts with an ellipsis '...', followed by a block labeled 'TPKT', then a block labeled 'H.501 PDU', then 'TPKT', then 'H.501 PDU', then 'TPKT', and finally 'H.501 PDU', ending with another ellipsis '...'. + +Figure 1/H.501 – TCP transport diagram showing a sequence of alternating TPKT and H.501 PDU blocks. + +**Figure 1/H.501 – TCP transport** + +When using an unreliable transport service, request messages may be retransmitted. The default value of the retransmission timer should be determined by an adaptive delay sensitive method (such as the one used by the TCP protocol). Exponential backoff shall be used for subsequent retransmissions. The number of retransmissions shall not exceed 5. Responses shall not be retransmitted. + +In UDP IP implementations, messages shall also be prefixed with TPKT headers, to enable multiple messages per packet, see Figure 2. Each H.501 PDU contains a single message defined in this Recommendation. The UDP packet length field shall hold the total length of the payload, including all the messages and their TPKT headers. + +![Figure 2/H.501 – UDP datagram format diagram showing a UDP header followed by a sequence of alternating TPKT and H.501 PDU blocks.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +The diagram shows a horizontal sequence of blocks. It starts with a block labeled 'UDP header', followed by a block labeled 'TPKT', then a block labeled 'H.501 PDU', then 'TPKT', then 'H.501 PDU', then 'TPKT', and finally 'H.501 PDU'. + +Figure 2/H.501 – UDP datagram format diagram showing a UDP header followed by a sequence of alternating TPKT and H.501 PDU blocks. + +**Figure 2/H.501 – UDP datagram format** + +## 5.2 Security considerations + +When authentication, integrity, and encryption on the transport layer is desired for messages exchanged between peer elements, the operation of IP security shall be followed as described in IETF RFC 2401, including either, or both, of IETF RFC 2402, and IETF RFC 2406. + +Where protection on the application layer is required, the procedures and constructs of ITU-T Rec. H.235 shall be utilized to support application-level security. Specifically, the token formats and authentication exchanges shall be used. Tokens and crypto-tokens received in response messages should be used in a subsequent related request. + +## 5.3 Addressing conventions + +In order to provide interoperability between domains, it is important that the addressing formats sent in signalling messages are understood by the receiving system. A peer element shall support all types of *AliasAddress* that an application may globally use. + +At a minimum, the formats *email-id* and *partyNumber* (using *PublicNumber* with *PublicTypeOfNumber* of *internationalNumber*) shall be supported. When communicating with other peer elements, only the *email-id* and *partyNumber* types of *AliasAddress* should be used, unless there has been prior agreement on the use of other formats between the administrative domains concerned. For example, if a group of administrative domains have agreed on the interpretation of a private numbering plan, then these numbers may be used in messages amongst them. + +In a mobile environment, the format *mobileUIM* may be used as a global user identification module upon agreement amongst the administrative domains concerned. This format is described in detail in ITU-T Rec. H.225.0. + +## 5.4 Address templates and descriptors + +An address template ("template", for short) defines a set of *AliasAddress* identifiers, pricing information to complete calls to those addresses, and the protocol to be used in reaching addresses in that set. An administrative domain advertises templates to indicate the calls it can resolve. Templates are grouped together by an identifier known as a "descriptor". Once a template is grouped by a descriptor, any change to a template under that descriptor implies a change to the descriptor "group". Template information may allow the aggregation of addressing information if the addressing scheme is arranged in some hierarchical or routable manner (for example, a given zone might handle 1303538\*, meaning all telephone numbers that begin with 1303538). + +NOTE – Since "\*" is a meaningful character, the template actually includes an explicit field to indicate whether the address is a specific address or a wildcard address. These examples use "\*" to indicate a wild card, but the actual representation in the template is through the explicit field. The "\*" is not sent over the line if it indicates a wild card. + +Template examples include: + +"For 1 555 123 4567 send AccessRequest message to peer element A" +"For 1 555 987 \* send AccessRequest message to peer element B" +"For 1 555 987 6543 send Setup message to gateway X" +"For \*@example.org send AccessRequest message to peer element A" +"For 1 send AccessRequest message to peer element B" +"For private 31\* send AccessRequest message to peer element C" +"For 44 171 112\* doesn't exist" + +# 6 Message definitions + +This clause specifies the messages and elements of the protocol defined in this Recommendation. Annex A contains the corresponding ASN.1 definition according to ITU-T Rec. X.680. Messages shall be encoded using the basic aligned variant of packed encoding rules according to ITU-T Rec. X.691. + +Each message contains a set of common fields in addition to the message-specific information. The common fields are: + +| Field | Description | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sequenceNumber | Each request or update message contains a unique sequence number. The message sent in response to a request message (a confirmation or rejection message) uses the sequence number from the request message. Retransmitted messages shall have the same sequence number. | +| replyAddress | This is the address to which to send the reply to a request message. All request messages shall include a replyAddress except for cases where the address can be derived from the transport layer. On IP networks, if the sender of the request message is listening on the default port (2099), then the reply address need not be included. In such a case, the receiver obtains the transport address of the sender by appending default port (2099) to the IP address of the sender as received in the IP header of the request packet. 1 | +| version | Protocol version in use by the sender of this message. | + +1 Peer elements are assumed not to be hidden behind network address translation (NAT) devices, thus it is not required to prefer the transport address over the replyAddress, as is the case for RAS messages. + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| annexGversion | Protocol version of H.225.0 Annex G (only present for backward compatibility; it shall indicate "Annex G V2"). | +| hopCount | This defines the number of peer elements through which this message may propagate. When a peer element receives this message and decides that the message should be forwarded on to another peer element, it first decrements hopCount . If hopCount is then greater than 0, the peer element inserts the new hop count value into the message to be forwarded. If hopCount has reached 0, the peer element shall not forward the message. If the message is a request, the peer element should respond with a confirmation message with any applicable information. If no information is available, the peer element should respond with a rejection message. | +| integrityCheckValue | Provides improved message integrity/message authentication. The cryptographically based integrity check value is computed by the sender applying a negotiated integrity algorithm and the secret key upon the entire message. Prior to integrityCheckValue computation each byte of this field shall be set to zero. After computation, the sender puts the computed integrity check value in the integrityCheckValue field and transmits the message. | +| tokens | This is some data that may be required to allow the operation. The data shall be inserted into the message if available. | +| cryptoTokens | Encrypted tokens. | +| nonStandard | Non-standard information. | +| serviceID | This identifier identifies a particular service relationship session between two peer elements. Whenever a peer element receives a ServiceRequest message requesting the establishment of a new service relationship (which is indicated by the absence of the service ID field in the ServiceRequest message), it allocates a globally unique service ID and returns it to the sender of the ServiceRequest message in the ServiceConfirmation message.

    Once a service relationship has been established, the service ID is included in all subsequent messages with the peer element (e.g. UsageIndication, DescriptorIDRequest, DescriptorRequest, AccessRequest). This is used by the recipient peer element to check if it has a service relationship with the sender of the message. | +| genericData | Carries any generic data associated with the message. GenericData is described in ITU-T Rec. H.323/ITU-T Rec. H.225.0. | +| featureSet | Used to negotiate generic feature sets. The negotiation scheme is as described for RAS signalling in ITU-T Rec. H.323/ITU-T Rec. H.225.0. | + +--- + +## 6.1 Descriptor + +The Descriptor is not a message, but is rather a message element used to label a set of templates. + +The Descriptor contains the following information: + +| Field | Description | +|----------------|------------------------------------------------------------------------------------------------------------------------| +| descriptorInfo | This holds a unique identifier for the descriptor and the time it was last changed (see Descriptor Information below). | +| templates | This is a set of templates that define the addresses this descriptor can resolve. | + +| | | +|--------------|-----------------------------------------------------------------------------------------------------------------------| +| gatekeeperID | This is a text identifier that indicates the owner of the descriptor (i.e. the gatekeeper that created this message). | +|--------------|-----------------------------------------------------------------------------------------------------------------------| + +--- + +## 6.2 Descriptor information + +Descriptor information uniquely identifies the descriptor and indicates the last time the descriptor changed. + +| Field | Description | +|--------------|-------------------------------------------------------------------------------------------------------------| +| descriptorID | This is a globally unique identifier used to identify this descriptor from among many possible descriptors. | +| lastChanged | This is the UTC date and time this descriptor was last changed. | + +--- + +## 6.3 Address template + +The Address Template describes a set of one or more alias addresses. The Template is not a message, but is an element used as a building block for other elements. The Template consists of other structures, which are described in subsections. + +| Field | Description | +|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pattern | This is a list of patterns (see Pattern below). | +| routeInfo | This is a list of route information for this template (see Route Information below). | +| timeToLive | This indicates the time, expressed in seconds, for which this template is valid. | +| supportedProtocols | Identifies the type of protocols that are supported by this template (e.g. voice, fax). | +| featureSet | Specifies the generic feature sets this addressTemplate supports and what generic features it needs and desires in a remote endpoint. Generic Feature information specified at this level applies to all routeInformation applicable to this AddressTemplate. The Generic Extensible Framework is described in ITU-T Rec. H.323/ITU-T Rec. H.225.0. | + +--- + +### 6.3.1 Pattern + +The *pattern* structure appears in the Address Template. The *pattern* allows specification of an alias address, a wildcarded alias address, or a range of alias addresses: wildcarded addresses assume an hierarchically structured address space, while address ranges are only meaningful for address types that represent an ordered structure. + +| Field | Description | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| specific | This is a specific alias address. | +| wildcard | This is some hierarchical definition that represents possible expansions of the string. For E.164 numbers, this expansion is possible at the end of the number; for email addresses, the expansion is possible at the beginning. For example, if wildcard is "+1 303", the pattern could represent any number in the Denver, Colorado, USA area code. | +| range | This is a range of addresses, including the indicated start and end of range. | + +--- + +### 6.3.2 Route information + +The route information structure found in the *template* (the *routeInfo* field) contains the following: + +| Field | Description | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| messageType | This indicates the type of message to send when attempting to resolve a specific address within this template. Possibilities are sendAccessRequest , sendSetup , or nonExistent (indicates that the address does not exist). | +| callSpecific | If set to TRUE, authorization is requested for each call to this route, implying that the AccessRequest message shall include the call information. This boolean field has meaning only when messageType is sendAccessRequest ; otherwise, callSpecific shall be set to FALSE. | +| usageSpec | If present, this specifies the UsageIndication messages that shall be sent regarding the calls to this route. | +| priceInfo | This is a list of pricing information for this particular route (see Pricing information below). Note that multiple gateways with different pricing structures would be described in multiple RouteInformation structures. | +| contacts | This is contact information for the element that will accept the message as specified in the messageType field of routeInfo . The contact information may be provided as a list of possible contacts (see Contact information description below). | +| type | This indicates the type of endpoint that can serve the call. For gatekeeper routed cases, this indicates the types of endpoints served by the gatekeeper rather than the gatekeeper itself. | +| featureSet | Specifies the generic feature sets this route supports and what generic features it needs and desires in a remote endpoint. Feature information specified at this level applies to all ContactInformation applicable to this RouteInformation element. The Generic Extensible Framework is described in ITU-T Rec. H.323/ITU-T Rec. H.225.0. | +| circuitID | If present, this holds the SCN circuit information that applies to a specific call. Circuit information specified at this level applies to all ContactInformation applicable to this RouteInformation element. | +| supportedCircuits | If present, this holds circuit identifier values for the SCN circuits that are supported in a domain or zone for the destination pattern. This allows a peer element to advertise the support of destination circuit information to remote peer elements. Circuit information specified at this level applies to all ContactInformation applicable to this RouteInformation element. | + +### 6.3.3 Pricing information + +Pricing information appears as an element in the route information structure (the *priceInfo* field). Pricing information is defined through the *PriceInfoSpec* and *PriceElement* structures. + +The *PriceInfoSpec* structure contains the following fields: + +| Field | Description | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| currency | This is an ISO 4217 currency designator. | +| currencyScale | This is the number of places to shift the implied radix point to the left. For example, when currency is specified as USD, a currencyScale of 2 would indicate that the amount in priceElement is expressed in US cents. | + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------| +| validFrom | This is the UTC date and time from which this information is valid. | +| validUntil | This is the UTC date and time at which this information expires. | +| hoursFrom | This is the time of day when this rate starts. | +| hoursUntil | This is the time of day when this rate ends. It may be less than hoursFrom , indicating a rate which spans 0000. | +| priceElement | This is an optional list of PriceElements which sum to effect the pricing. | +| priceFormula | This is an optional string containing a pricing formula used as an alternative to the structured PriceElement . | + +--- + +The *PriceElement* structure contains the following fields: + +| Field | Description | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| amount | This is the meter increment. The meter increments once for each quantum or fraction of quantum . | +| quantum | This is the number of units for which amount applies. For example, a value of 60, with units in seconds, indicates that the call is priced per minute or fraction of minute. If the units field is set to either of initial , minimum or maximum values, then the quantum field is irrelevant, and its value shall be ignored by the recipient. | +| units | This is the type of unit in which quantum is expressed:
    • seconds – seconds of call duration.
    • packets – packets transmitted or received.
    • bytes – bytes transmitted or received.
    • initial – an initial connect charge.
    • minimum – a minimum call charge.
    • maximum – a maximum call charge.
    | + +--- + +### 6.3.4 Contact information + +The contact information structure is an element of the route information structure (the *contacts* field). + +| Field | Description | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| transportAddress | This is the alias address (e.g. transport address or URL) to which to send the message specified in the messageType field of the RouteInformation structure. Whenever possible, a transport address shall be used. | +| priority | When multiple contacts are listed, the priority field specifies the order in which the multiple contacts should be tried. Contacts in the list can share a priority, for example if there is no preference on the order in which the contacts should be tried. A priority of 0 indicates the highest priority (first choice). | +| transportQoS | Indicates where the responsibility lies for resource reservation for a call made through this contact. | +| security | Security mechanism in descending order of preference to be used when communicating with contact. | + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| accessTokens | This is a set of tokens that shall be passed in the message to this contact (Setup or AccessRequest). These tokens shall also be sent in subsequent UsageIndication messages pertaining to the calls using this template. | +| multipleCalls | This field has significance only when the value in the messageType field of the RouteInformation structure is sendSetup. If multipleCalls is TRUE, this indicates that the contact is capable of signalling multiple calls over a single call signalling connection. If FALSE, the contact does not have this capability. | +| featureSet | Specifies the generic feature sets that the entity associated with this ContactInformation element supports and what generic features it needs and desires in a remote endpoint. The Generic Extensible Framework is described in ITU-T Rec. H.323/ITU-T Rec. H.225.0. | +| circuitID | If present, this holds the SCN circuit information that applies to a specific call. Circuit information specified at this level applies to the contact related to this ContactInformation element. | +| supportedCircuits | If present, this holds circuit identifier values for the SCN circuits that are supported in a domain or zone for the destination pattern. This allows a peer element to advertise the support of destination circuit information to remote peer elements. Circuit information specified at this level applies to the contact related to this ContactInformation element. | + +--- + +## 6.4 Common structures + +The structures defined in this clause appear in many of the messages. + +### 6.4.1 AlternatePE + +| Field | Description | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| contactAddress | This is the alternate peer element's transport address (the address to which to send messages of this protocol). | +| priority | When multiple alternates are listed, the priority field specifies the order in which the multiple alternates should be tried. Alternates in the list can share a priority, for example if there is no preference on the order in which the alternates should be tried. A priority of 0 indicates the highest priority (first choice). | +| elementIdentifier | This alternate peer element uses this Unicode string as an identifier. | + +--- + +### 6.4.2 PartyInformation + +This structure contains information about a party of the call (either source or destination). + +| Field | Description | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| logicalAddress | E-mail or E.164 formatted addresses that identify the party. | +| domainIdentifier | An alias address identifying the AD which originated or terminated the call. If multiple domains are involved in placing a call, then the domain that served as the call origination or termination from the sender's perspective should be stated. | +| transportAddress | This is the transport address of the endpoint. | + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| endpointType | This indicates details about the endpoint type and capabilities. | +| userInfo | This is information regarding the user behind the call. See UserInformation below. | +| timeZone | This is the time zone of the party, as relevant for pricing purposes. If the originating party is a gateway, then the time zone of the gateway has to be conveyed. Described in seconds relative to UTC. | + +--- + +### 6.4.3 CallInformation + +This structure contains information for identifying a specific call. + +| Field | Description | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| callIdentifier | This provides unique identification of the call. This shall be the callIdentifier associated with the same call as in RAS and call signalling messages. | +| conferenceID | This provides unique identification of the conference to which the call belongs. This shall be the conferenceID associated with the same call as in RAS and call signalling messages. | +| circuitID | If present, this holds the SCN circuit information that applies to the call. | + +--- + +### 6.4.4 UserInformation + +This structure contains information for identifying the user represented by any party of the call. + +| Field | Description | +|-------------------|--------------------------------------------------| +| userIdentifier | Alias address that uniquely identifies the user. | +| userAuthenticator | Encrypted tokens for secure authentication. | + +--- + +### 6.4.5 Usage specification + +This element describes the required parameters needed to be reported in the UsageIndication messages. The calls for which this specification applies is determined by the context of the message containing the *UsageSpecification* element. + +| Field | Description | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sendTo | Peer element to which the UsageIndication messages are to be sent. If the sender has a service relationship with that peer element, this is the element identifier returned in the ServiceConfirmation message. | +| when | Specifies the stages of the call, and the frequency, at which the indications should be sent:
    • never – stop sending messages.
    • start – when the call begins.
    • end – by the end of the call, or thereafter.
    • period – periodically, during the call lifetime. The period is measured in seconds.
    • failure – report failed call attempts.
    | +| required | A list of identifiers for fields that must be present in the UsageIndication messages. The sender of the usage information shall reject or ignore the message containing this message, if it cannot supply these fields. | +| preferred | A list of identifiers for fields that should be present in the UsageIndication messages. | + +**sendToPEAddress** A resolvable address that, when resolved, specifies the address of a peer element to which UsageIndication messages shall be sent. If the resolution of this field results in more than one address (for example, in the case where a DNS query returns a list of addresses), the peer element shall send the UsageIndication messages to only one peer element from the list. + +If the peer element does not succeed in sending to one address, it may choose another address from the list and attempt to send the UsageIndication messages to the new address. The peer element may continue attempting each additional address in the list until it either receives a UsageIndicationConfirmation, a UsageIndicationRejection, or until there are no further addresses to attempt. + +Note that the "sendToPEAddress" field is different from the "sendTo" field in the UsageSpecification. The "sendTo" field is an identifier. It can be the identifier of a specific peer element (e.g. "border\_element1"), or it can be an identifier that logically represents a set of peer elements (e.g. "border elements of my company"). + +The "sendToPEAddress" field resolves to one or more addresses. + +--- + +### 6.4.6 Security Mode + +This element describes a specific security profile to be used for peer to peer communication. + +| Field | Description | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| authentication | This indicates the authentication mechanism to be used. The authentication mechanism must be chosen from the set provided in the ServiceRequest message. | +| integrity | This indicates the integrity mechanism to be used. If present, all subsequent messages shall populate the integrityCheckValue field, in this case, the AuthenticationMode describes the way the secret keys are generated (DH exchange, or a priori ). | +| algorithmOIDs | This indicates the encryption algorithms for the security mechanism. | + +--- + +## 6.5 Service relationship + +### 6.5.1 Service Request + +A peer element may send a ServiceRequest message to another peer element to establish a service relationship. The relationship defines the security mechanisms to be used between the peer elements and allows identification of alternate, or backup, peer elements. Note that the relationship is a one-way relationship. The security negotiated between the 2-peer elements is used for requests sent by the peer element that sent the ServiceRequest and for responses sent by the recipient of the ServiceRequest. Session keys may be generated during the process of service relationship establishment. The keys will be valid through the lifetime of the service relationship. Tokens may be used for that purpose, as defined in ITU-T Rec. H.235. + +The recipient of the ServiceRequest may indicate alternate peer elements that the sender of ServiceRequest may try for backup service. Establishing a service relationship is an optional procedure, although a peer element's policy may require such a relationship. + +A peer element may send a ServiceRequest message to a peer element with which it has an existing relationship, with the intent that the terms of the original relationship be terminated and replaced with the new terms. Service relationships may have limited time to live. A peer element may refresh the relationship by sending a new Service Request. + +| Field | Description | +|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| elementIdentifier | A string that identifies the peer element that sends the request. | +| domainIdentifier | The AD that requests the service relationship. | +| securityCapability | Set of security mechanisms that this peer element can support. | +| timeToLive | The suggested lifetime in seconds for the service relationship. If not present, infinite lifetime is assumed. | +| usageSpec | This specifies the usage information that the originating peer element requests the receiving peer element to send for all calls between the originating and receiving peer elements. | + +### 6.5.2 Service Confirmation + +A peer element in receipt of a ServiceRequest message responds with a ServiceConfirmation message to indicate that it agrees to establish a service relationship. Every new service relationship is identified by a service identifier. Whenever a peer element receives a ServiceRequest message without a service ID, it allocates a unique service ID and returns it to the sender of the service request message in the ServiceConfirmation message. If the peer element already has a service relationship with the peer element that sent the ServiceRequest message, sending ServiceConfirmation indicates that the terms of the original relationship are terminated and replaced with the new terms. The ServiceConfirmation message shall contain the same service ID that was sent in the ServiceRequest message. A peer element that receives a ServiceRequest message containing a service ID that it does not recognize shall respond with a ServiceRejection message. + +| Field | Description | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| elementIdentifier | This is a string that identifies the peer element. | +| domainIdentifier | The AD that responds to the request. | +| alternates | This is a list of alternate peer elements that may be contacted in the event that this peer element fails to respond. | +| securityMode | This indicates the security mechanism to be used for this service relationship. The security mechanism must be chosen from the set provided in the ServiceRequest message. | +| timeToLive | The lifetime in seconds of the service relationship as determined by the serving peer element. | +| usageSpec | This specifies the usage information that the receiving peer element can support for all calls between the originating and receiving peer elements. | + +### 6.5.3 Service Rejection + +A peer element in receipt of a ServiceRequest message responds with a ServiceRejection message to indicate that it declines to establish a service relationship. If the peer element already has a service relationship with the peer element that sent the ServiceRequest message, sending ServiceRejection indicates that the proposed new terms have been rejected, but the terms of the original relationship remain. + +| Field | Description | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason |

    This is the reason the peer element rejected the ServiceRequest. Choices are:

    • • serviceUnavailable – This peer element is not currently available for service.
    • • serviceRedirected – The list of alternate peer elements should be attempted.
    • • security – This peer element cannot support any of the security mechanisms proposed in the ServiceRequest message.
    • • continue – Indicates the subsequent ServiceRequest message be sent, in order to continue multiple stage key exchange processes.
    • • undefined – The reason for rejecting the ServiceRequest does not match any of the other choices.
    • • unknownServiceID – The serviceID field contained in the ServiceRequest message is not recognized by the peer element
    • • cannotSupportUsageSpec – The peer element cannot comply with the proposed UsageSpecification.
    • • neededFeature – Indicates that the request failed because the requesting entity did not support one or more needed generic features. The features that are needed are indicated in the neededFeatures field in the MessageCommonInfo field of the reply.
    • • genericDataReason – Indicates that the real reason code is contained within the genericData field sent with this message. Note that the genericData may contain more than one reason code.
    • • usageUnavailable – The peer element does not support usage reporting.
    • • unknownUsageSendTo – The sendTo or sendToPEAddress specified in the proposed UsageSpecification could not be resolved.
    | +| alternates |

    This is a list of alternate peer elements that might be able to honour the ServiceRequest. If the reason is serviceRedirected, at least one alternate should be provided.

    | + +### 6.5.4 Service Release + +Either peer element in a service relationship may terminate the relationship by sending the ServiceRelease message. + +| Field | Description | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason | This is the reason this peer element terminated the service relationship. Choices are:
    • • outOfService – The peer element is going out of service.
    • • maintenance – The peer element is being taken out of service for maintenance.
    • • terminated – The peer element has decided to terminate the relationship.
    • • expired – The time-to-live for the service relationship has elapsed.
    | +| alternates | This is a list of alternate peer elements that might be able to establish a service relationship. | + +## 6.6 Descriptor distribution + +### 6.6.1 Descriptor Request + +The DescriptorRequest message allows an entity to query a peer element for specific descriptors. + +| Field | Description | +|--------------|---------------------------------------------------------------------------------------------| +| descriptorID | This identifies one or more particular descriptors requested by the sender of this message. | + +### 6.6.2 Descriptor Confirmation + +The DescriptorConfirmation message is a peer element's positive response to a DescriptorRequest, when the peer element can interpret the request and implementation rules allow information exchange. + +| Field | Description | +|------------|-------------------------------------------------| +| descriptor | This is(are) the descriptor(s) described above. | + +### 6.6.3 Descriptor Rejection + +A peer element can reject a descriptor request for a variety of reasons. + +| Field | Description | +|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason | This is the reason the DescriptorRequest was rejected. Choices are:
    • • packetSizeExceeded – The reply would exceed the maximum packet size, so the requester should send the request using a different transport mechanism (e.g. use TCP instead of UDP).
    • • illegalID – The recipient of the DescriptorRequest has no record of the requested descriptor.
    • • security – The DescriptorRequest did not meet the recipient's security requirements.
    • • hopCountExceeded – The hop count reached zero and no information is available.
    | + +- unavailable – The recipient cannot provide descriptors. Static or out-of-band provisioning method should be used. +- noServiceRelationship – The recipient will exchange this information only after establishment of a service relationship. +- undefined – The reason for rejecting the DescriptorRequest does not match the other choices. +- neededFeature – Indicates that the request failed because the requesting entity did not support one or more needed generic features. The features that are needed are indicated in the neededFeatures field in the MessageCommonInfo field of the reply. +- genericDataReason – Indicates that the real reason code is contained within the genericData field sent with this message. Note that the genericData may contain more than one reason code. +- unknownServiceID – The serviceID field contained in the DescriptorRequest message is not recognized by the peer element + +descriptorID This identifies the specific descriptor for this response. + +--- + +### 6.6.4 Descriptor ID Request + +The DescriptorIDRequest allows an entity to query a peer element for the list of descriptor identifiers within the peer element's administrative domain. + +### 6.6.5 Descriptor ID Confirmation + +A DescriptorIDConfirmation message is a peer element's positive response to the DescriptorIDRequest message. A peer element in receipt of a DescriptorIDConfirmation message may send the DescriptorRequest message to request transmission of the descriptors. + +| Field | Description | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| descriptorInfo | This is a list of descriptor information, where each entry in the list uniquely identifies the descriptor and the time it last changed. | + +--- + +### 6.6.6 Descriptor ID Rejection + +A peer element can reject a DescriptorIDRequest for a variety of reasons. + +| Field | Description | +|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason |

    This indicates the reason for rejecting the request. Choices are:

    • • noDescriptors – This indicates that the peer element has no descriptors to report.
    • • security – The DescriptorIDRequest did not meet the recipient's security requirements.
    • • hopCountExceeded – The hop count reached zero and no information is available.
    • • unavailable – The recipient cannot provide descriptors. Static or out-of-band provisioning method should be used.
    • • noServiceRelationship – The recipient will exchange this information only after establishment of a service relationship.
    • • undefined – The reason for rejecting the DescriptorIDRequest does not match the other choices.
    | + +- neededFeature – Indicates that the request failed because the requesting entity did not support one or more needed generic features. The features that are needed are indicated in the neededFeatures field in the MessageCommonInfo field of the reply. + - genericDataReason – Indicates that the real reason code is contained within the genericData field sent with this message. Note that the genericData may contain more than one reason code. + - unknownServiceID – The serviceID field contained in the DescriptorIDRequest message is not recognized by the peer element. +- + +### 6.6.7 Descriptor Update + +The DescriptorUpdate message is a peer element's notification that address information has changed. A peer element may also send the DescriptorUpdate message during initialization. A peer element in receipt of the DescriptorUpdate may request information from the element identified in the DescriptorUpdate. + +| Field | Description | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sender | An element in receipt of the DescriptorUpdate may send a request to this address (e.g. transport address or URL). | +| updateInfo | This is a list of updates. Each entry in the list provides either the descriptor or the descriptor identifier that was updated. Each entry in the list also indicates whether the descriptor was changed, added or deleted. | + +--- + +### 6.6.8 Descriptor Update Acknowledgement + +A peer element should acknowledge receipt of a DescriptorUpdate message by sending the DescriptorUpdateAck message. The sequence number used in the acknowledgement should be the same as the sequence number received in the DescriptorUpdate message. A peer element should not acknowledge a DescriptorUpdate message that arrives over multicast. + +## 6.7 Address resolution + +### 6.7.1 Access Request + +A peer element can send an AccessRequest message to another peer element to ask for resolution of a specific alias address. + +| Field | Description | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| destinationInfo | This is the address to be resolved. | +| sourceInfo | This is information about the originating party of the call for which access is requested. | +| callInfo | This provides identification of the particular call for which access authorization is requested. If not present, then the request is for indefinite calls to the specified destinations. | +| usageSpec | This indicates the usage messages that the originating party requests the answering party to send regarding the call requested in this message. Applies only if CallInfo is present. | + +| | | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| desiredProtocols | Identifies the type of protocols, in order of preference, the endpoint desires for its call (e.g. voice, fax). A resolving entity may use this field to locate an endpoint that also supports the protocol, giving consideration to the order of preference. The called entity shall ignore the supportedPrefixes field of this structure. | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +--- + +### 6.7.2 Access Confirmation + +A peer element returns in the AccessConfirmation message the information requested in the AccessRequest message. + +| Field | Description | +|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| templates | This is a list of templates which match the attributes of the AccessRequest. | +| partialResponse | If TRUE, this message contains some fraction of the available information. The entire information was not sent because it would exceed the packet size. The entire information should be retrieved using another transport type (e.g. TCP). | +| supportedProtocols | Identifies the type of protocols that are supported (e.g. voice, fax). | +| serviceControl | As defined in ITU-T Rec. H.225.0 for use e.g. as described in Annex K/H.323. | + +--- + +### 6.7.3 Access Rejection + +A peer element can reject an AccessRequest for a variety of reasons. + +| Field | Description | +|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason |

    This is the reason for rejecting the request. Choices are:

    • • noMatch – The destination specified in the AccessRequest cannot be resolved.
    • • packetSizeExceeded – The reply would exceed the maximum packet size, so the requester should send the request using a different transport mechanism (e.g. use TCP instead of UDP).
    • • security – The AccessRequest did not meet the recipient's security requirements.
    • • hopCountExceeded – The hop count reached zero and no information is available.
    • • noServiceRelationship – The recipient will exchange this information only after establishment of a service relationship.
    • • needCallInformation – Specific call information was not present in the request.
    • • undefined – The reason for rejecting the AccessRequest does not match the other choices.
    • • neededFeature – Indicates that the request failed because the requesting entity did not support one or more needed generic features. The features that are needed are indicated in the neededFeatures field in the MessageCommonInfo field of the reply.
    • • genericDataReason – Indicates that the real reason code is contained within the genericData field sent with this message. Note that the genericData may contain more than one reason code.
    • • destinationUnavailable – Destination was resolved but is unavailable.
    | + +- aliasesInconsistent – Multiple aliases identify distinct destinations. +- resourceUnavailable – One or more required resources are unavailable. +- incompleteAddress – Destination cannot be distinctly identified. +- unknownServiceID – The serviceID field contained in the AccessRequest message is not recognized by the peer element. +- usageUnavailable – The peer element does not support usage reporting. +- cannotSupportUsageSpec – The peer element cannot comply with the proposed UsageSpecification. +- unknownUsageSendTo – The sendTo or sendToPEAddress specified in the proposed UsageSpecification could not be resolved. + +serviceControl As defined in ITU-T Rec. H.225.0 for use e.g. as described in Annex K/H.323. + +--- + +## 6.8 Request in Process + +A peer element may return the RequestInProgress message to indicate that the time required by the peer element to respond to a request may exceed normal expected response intervals. The sequence number shall be the same sequence number found in the request for which this message will be sent. + +| Field | Description | +|----------------|------------------------------------------------------------------------------------------------------------------| +| delay | The expected length of time, expressed in milliseconds, for the peer element to respond to the original request. | +| serviceControl | As defined in ITU-T Rec. H.225.0 for use e.g. as described in Annex K/H.323. | + +--- + +## 6.9 Non-standard messages + +### 6.9.1 Non-Standard Request + +The NonStandardRequest may be sent from a peer element to represent a request message not defined in this Recommendation. The non-standard information is carried in the *nonStandard* element of *MessageCommonInfo*. + +### 6.9.2 Non-Standard Confirmation + +The NonStandardConfirmation may be sent from a peer element in response to a NonStandardRequest message. The non-standard information is carried in the *nonStandard* element of *MessageCommonInfo*. + +### 6.9.3 Non-Standard Rejection + +The NonStandardRejection may be sent from a peer element in response to a NonStandardRequest message. The non-standard information is carried in the *nonStandard* element of *MessageCommonInfo*. + +| Field | Description | +|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason | This is the reason for rejecting the request. Choices are:
    • • notSupported – The recipient understands that this is a NonStandardRequest, but does not understand or support the non-standard data.
    | + +- noServiceRelationship – The recipient will exchange this information only after establishment of a service relationship. + - undefined – The reason for rejecting the NonStandardRequest does not match the other choices. + - neededFeature – Indicates that the request failed because the requesting entity did not support one or more needed generic features. The features that are needed are indicated in the neededFeatures field in the MessageCommonInfo field of the reply. + - genericDataReason – Indicates that the real reason code is contained within the genericData field sent with this message. Note that the genericData may contain more than one reason code. + - unknownServiceID – The serviceID field contained in the NonStandardRequest message is not recognized by the peer element. +- + +## 6.10 Unknown Message Response + +A peer element in receipt of a message it does not understand should respond to the transmitter with the UnknownMessageResponse message. The peer element should not use this message if some other message provides an appropriate response (for example, a DescriptorRejection would be the appropriate response to a DescriptorRequest with an illegal descriptor identifier). + +| Field | Description | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| unknownMessage | This is the contents of the unknown message. | +| reason | This is the reason the UnknownMessageResponse was used. Choices are:
    • • notUnderstood – The message was not understood.
    • • undefined – The reason for sending UnknownMessageResponse does not match any of the other choices.
    | + +--- + +## 6.11 Usage reports + +### 6.11.1 Usage Request + +Request the recipient to send UsageIndication messages concerning a specific call. + +| Field | Description | +|--------------|-----------------------------------------------------------------------------| +| CallInfo | The call for which to send the Indication. | +| UsageSpec | Specifies when the indications should arrive, and what they should contain. | + +--- + +### 6.11.2 Usage Confirmation + +The UsageConfirmation message is sent in response to a Usage Request message to indicate that the recipient accepted the request and will send usage indications. + +### 6.11.3 Usage Rejection + +The UsageRejection message is sent in response to a Usage Request message to indicate that the recipient rejected the request and will not send the usage indications subsequently. + +| Field | Description | +|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason |

    This is the reason why the peer element rejected the UsageRequest. Choices are:

    • • invalidCall – The call specified in the UsageRequest is not a recognized call.
    • • security – The UsageRequest did not meet the recipient's security requirements.
    • • unavailable – The recipient does not have usage information for the requested call.
    • • noServiceRelationship – The recipient will exchange this information only after establishment of a service relationship.
    • • undefined – The reason for rejecting the UsageRequest does not match any of the other choices.
    • • neededFeature – Indicates that the request failed because the requesting entity did not support one or more needed generic features. The features that are needed are indicated in the neededFeatures field in the MessageCommonInfo field of the reply.
    • • genericDataReason – Indicates that the real reason code is contained within the genericData field sent with this message. Note that the genericData may contain more than one reason code.
    • • unknownServiceID – The serviceID field contained in the UsageRequest message is not recognized by the peer element.
    | + +### 6.11.4 Usage Indication + +Report call details and usage information. This message is sent with respect to the last *UsageSpecification* element received by the peer element concerning the call. + +| Field | Description | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| callInfo | The call for which the indication applies. | +| accessTokens | The access tokens for the call. These are the tokens that were received in the address template used for the call, and propagated in the AccessRequest/Setup message for the same call. | +| senderRole |

    The role of the sender of the indication:

    • • originator – originating party.
    • • destination – terminating party.
    • • nonStandard – other.
    | +| usageCallStatus |

    The current status of the call:

    • • preConnect.
    • • callInProgress.
    • • callEnded.
    • • registrationLost.
    | + +| | | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| srcInfo | E.164 or e-mail address of the calling party. | +| destAddress | E.164 or e-mail address for the called party. | +| startTime | The time the call started, in UTC format. Relevant only for calls that passed the set-up stage. For multiple media types used in the call, each media type should report a different startTime, corresponding to the time at which that media stream started. For periodic messages, startTime should correspond with the endTime of the previous message. | +| endTime | The time the call ended, in UTC format. Relevant only for ended calls. For multiple media types used in the call, each media type shall report a different endTime corresponding to the time at which that media stream ended. For periodic messages, endTime is the time which ends a reporting period. | +| terminationCause | The reason for the end of the call. Relevant only for ended calls. | +| usageFields | Set of fields of information. Each field is represented by a UsageField which can be a standard or non-standard. Standard UsageFields are for future study. | + +--- + +### 6.11.5 Usage Indication Confirmation + +The UsageIndicationConfirmation message is sent in response to a UsageIndication message, indicating the recipient accepted the indication as reported. + +### 6.11.6 Usage Indication Rejection + +The UsageIndicationRejection message is sent in response to a UsageIndication message, indicating that the recipient rejected the indication and will ignore it. + +| Field | Description | +|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason |

    This is the reason why the peer element rejected the UsageIndication message. Choices are:

    • • unknownCall – The call specified in the UsageIndication is not a recognized call.
    • • incomplete – The UsageIndication did not contain all the information required by the UsageSpecification that applies to this UsageIndication.
    • • security – The UsageIndication did not meet the recipient's security requirements.
    • • noServiceRelationship – The recipient will exchange this information only after establishment of a service relationship.
    • • undefined – The reason for rejecting the UsageIndication does not match any of the other choices.
    • • neededFeature – Indicates that the request failed because the requesting entity did not support one or more needed generic features. The features that are needed are indicated in the neededFeatures field in the MessageCommonInfo field of the reply.
    • • genericDataReason – Indicates that the real reason code is contained within the genericData field sent with this message. Note that the genericData may contain more than one reason code.
    • • unknownServiceID – The serviceID field contained in the UsageIndication message is not recognized by the peer element.
    | + +--- + +## 6.12 Validations + +### 6.12.1 Validation Request + +A peer element that terminates a call can send a ValidationRequest message to another peer element to verify the validity of the origination of the call. + +| Field | Description | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| accessToken | Tokens received from the originator to prove access authorization for the call. | +| destinationInfo | Details about the destination of the call. | +| sourceInfo | This is information about the type of endpoint that originated the call. | +| callInfo | This provides identification of the particular call for which access authorization is requested. | +| usageSpec | If present, indicates a request from the peer element which is sending the message to receive usage indication regarding the validated call. | + +### 6.12.2 Validation Confirmation + +Indicates that the call is validated. The requesting peer element may terminate the call. The validating peer element may indicate aliases to terminate the call. + +| Field | Description | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| destinationInfo | Alternative parameters for the destination to be used by the recipient peer element. | +| usageSpec | If present, indicates a request from the peer element which is sending the confirmation to receive usage indication regarding the validated call. | + +### 6.12.3 Validation Rejection + +Indicates the call is not valid. The requesting peer element may not complete the call. + +| Field | Description | +|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason | This is the reason for rejecting the request. Choices are:
    • • tokenNotValid – The access token supplied is not valid for the call.
    • • security – The ValidationRequest did not meet the recipient's security requirements.
    • • hopCountExceeded – The hop count reached zero and no information is available.
    • • missingSourceInfo – The source information supplied was not sufficient to validate the call.
    • • missingDestInfo – The source information supplied was not sufficient to validate the call.
    • • noServiceRelationship – The recipient will exchange this information only after establishment of a service relationship.
    • • undefined – The reason for rejecting the ValidationRequest does not match the other choices.
    • • neededFeature – Indicates that the request failed because the requesting entity did not support one or more needed generic features. The features that are needed are indicated in the neededFeatures field in the MessageCommonInfo field of the reply.
    | + +- genericDataReason – Indicates that the real reason code is contained within the genericData field sent with this message. Note that the genericData may contain more than one reason code. + - unknownServiceID – The serviceID field contained in the ValidationRequest message is not recognized by the peer element. +- + +## 6.13 Authentication + +### 6.13.1 Authentication Request + +A peer element can send an AuthenticationRequest message to another peer element to authenticate a user. + +| Field | Description | +|--------------------|---------------------------------------------------------------| +| applicationMessage | Contains an application protocol message to be authenticated. | + +### 6.13.2 Authentication Confirmation + +Indicates successful authentication. There are no specific fields defined for this message, the relevant information (tokens, cryptoTokens) is contained in the common part of the message. + +### 6.13.3 Authentication Rejection + +Indicates that authentication has failed. + +| Field | Description | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason |

    This is the reason for rejecting the request. Choices are:

    • • security – The AuthenticationRequest did not meet the recipient's security requirements.
    • • hopCountExceeded – The hop count reached zero and no information is available.
    • • noServiceRelationship – The recipient will exchange this information only after establishment of a service relationship.
    • • undefined – The reason for rejecting the AuthenticationRequest does not match the other choices.
    • • neededFeature – Indicates that the request failed because the requesting entity did not support one or more needed generic features. The features that are needed are indicated in the neededFeatures field in the MessageCommonInfo field of the reply.
    • • genericDataReason – Indicates that the real reason code is contained within the genericData field sent with this message. Note that the genericData may contain more than one reason code.
    • • unknownServiceID – The serviceID field contained in the AuthenticationRequest message is not recognized by the peer element.
    • • securityWrongSyncTime – The sender found a security problem with inappropriate timestamps. This could be due to a problem with the time server, lost synchronization or excessive network delay.
    • • securityReplay – A replay attack has been encountered. This is the case when the same sequence number occurs more than once for a given timestamp.
    | + +- securityWrongGeneralID – Indicates a mismatch of the general ID in the message. This could be caused by wrong addressing. + - securityWrongSendersID – Indicates a mismatch of the sender's ID in the message. This could be caused by erroneous user's entry. + - securityMessageIntegrityFailed – The integrity/signature check failed. This could be caused by a wrong or mistyped password during the initial request or a wrong private/public key applied, or by an encountered active attack. + - securityWrongOID – Indicates any mismatch in token OIDs (clear or crypto token) or crypto algorithm OIDs. Different security algorithms/profiles are implemented. +- + +# Annex A + +## Message Syntax + +``` + +H501-MESSAGES DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +IMPORTS +AuthenticationMechanism, +TimeStamp, +ClearToken + FROM H235-SECURITY-MESSAGES + +AliasAddress, +TransportAddress, +ReleaseCompleteReason, +ConferenceIdentifier, +CallIdentifier, +CryptoH323Token, +CryptoToken, +EndPointType, +GatekeeperIdentifier, +GloballyUniqueID, +NonStandardParameter, +NumberDigits, +PartyNumber, +SupportedProtocols, +TransportQOS, +VendorIdentifier, +IntegrityMechanism, +ICV, +FeatureSet, +GenericData, +EnumeratedParameter, +ServiceControlSession, +CircuitInfo, +CircuitIdentifier + FROM H323-MESSAGES; + +``` + +``` + +Message ::= SEQUENCE +{ + body MessageBody, + common MessageCommonInfo, + ... +} + +MessageBody ::= CHOICE +{ + serviceRequest ServiceRequest, + serviceConfirmation ServiceConfirmation, + serviceRejection ServiceRejection, + serviceRelease ServiceRelease, + descriptorRequest DescriptorRequest, + descriptorConfirmation DescriptorConfirmation, + descriptorRejection DescriptorRejection, + descriptorIDRequest DescriptorIDRequest, + descriptorIDConfirmation DescriptorIDConfirmation, + descriptorIDRejection DescriptorIDRejection, + descriptorUpdate DescriptorUpdate, + descriptorUpdateAck DescriptorUpdateAck, + accessRequest AccessRequest, + accessConfirmation AccessConfirmation, + accessRejection AccessRejection, + requestInProgress RequestInProgress, + nonStandardRequest NonStandardRequest, + nonStandardConfirmation NonStandardConfirmation, + nonStandardRejection NonStandardRejection, + unknownMessageResponse UnknownMessageResponse, + usageRequest UsageRequest, + usageConfirmation UsageConfirmation, + usageIndication UsageIndication, + usageIndicationConfirmation UsageIndicationConfirmation, + usageIndicationRejection UsageIndicationRejection, + usageRejection UsageRejection, + validationRequest ValidationRequest, + validationConfirmation ValidationConfirmation, + validationRejection ValidationRejection, + ..., + authenticationRequest AuthenticationRequest, + authenticationConfirmation AuthenticationConfirmation, + authenticationRejection AuthenticationRejection +} + +MessageCommonInfo ::= SEQUENCE +{ + sequenceNumber INTEGER (0..65535), + annexGversion ProtocolVersion, -- set to "H.225.0 Annex G V2" + hopCount INTEGER (1..255), + replyAddress SEQUENCE OF TransportAddress OPTIONAL, + -- Must be present in request + integrityCheckValue ICV OPTIONAL, + tokens SEQUENCE OF ClearToken OPTIONAL, + cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL, + nonStandard SEQUENCE OF NonStandardParameter OPTIONAL, + ..., + serviceID ServiceID OPTIONAL, + genericData SEQUENCE OF GenericData OPTIONAL, + featureSet FeatureSet OPTIONAL, + version ProtocolVersion -- current H.501 protocol version +} + +``` + +ServiceID ::= GloballyUniqueID + +-- +-- H.501 messages +-- + +ServiceRequest ::= SEQUENCE + +{ +    elementIdentifier       ElementIdentifier OPTIONAL, +    domainIdentifier       AliasAddress OPTIONAL, +    securityMode           SEQUENCE OF SecurityMode OPTIONAL, +    timeToLive             INTEGER (1..4294967295) OPTIONAL, +    ..., +    usageSpec              UsageSpecification OPTIONAL +} + +SecurityMode ::= SEQUENCE + +{ +    authentication         AuthenticationMechanism OPTIONAL, +    integrity              IntegrityMechanism OPTIONAL, +    algorithmOIDs          SEQUENCE OF OBJECT IDENTIFIER OPTIONAL, +    ... +} + +ServiceConfirmation ::= SEQUENCE + +{ +    elementIdentifier       ElementIdentifier, +    domainIdentifier       AliasAddress, +    alternates             AlternatePEInfo OPTIONAL, +    securityMode           SecurityMode OPTIONAL, +    timeToLive             INTEGER (1..4294967295) OPTIONAL, +    ..., +    usageSpec              UsageSpecification OPTIONAL +} + +ServiceRejection ::= SEQUENCE + +{ +    reason                 ServiceRejectionReason, +    alternates             AlternatePEInfo OPTIONAL, +    ... +} + +ServiceRejectionReason ::= CHOICE + +{ +    serviceUnavailable     NULL, +    serviceRedirected      NULL, +    security               NULL, +    continue               NULL, +    undefined              NULL, +    ..., +    unknownServiceID       NULL, +    cannotSupportUsageSpec NULL, -- Cannot comply with proposed spec +    neededFeature          NULL, +    genericDataReason      NULL, +    usageUnavailable       NULL, -- Usage reporting not supported +    unknownUsageSendTo     NULL -- Usage sendTo could not be resolved +} + +``` + +ServiceRelease ::= SEQUENCE +{ + reason ServiceReleaseReason, + alternates AlternatePEInfo OPTIONAL, + ... +} + +ServiceReleaseReason ::= CHOICE +{ + outOfService NULL, + maintenance NULL, + terminated NULL, + expired NULL, + ... +} + +DescriptorRequest ::= SEQUENCE +{ + descriptorID SEQUENCE OF DescriptorID, + ... +} + +DescriptorConfirmation ::= SEQUENCE +{ + descriptor SEQUENCE OF Descriptor, + ... +} + +DescriptorRejection ::= SEQUENCE +{ + reason DescriptorRejectionReason, + descriptorID DescriptorID OPTIONAL, + ... +} + +DescriptorRejectionReason ::= CHOICE +{ + packetSizeExceeded NULL, -- use other transport type + illegalID NULL, -- no descriptor for provided descriptorID + security NULL, -- request did not meet security requirements + hopCountExceeded NULL, + noServiceRelationship NULL, + undefined NULL, + ..., + neededFeature NULL, + genericDataReason NULL, + unknownServiceID NULL -- The serviceID is not recognized by + -- the peer element +} + +DescriptorIDRequest ::= SEQUENCE +{ + ... +} + +``` + +``` + +DescriptorIDConfirmation ::= SEQUENCE +{ + descriptorInfo SEQUENCE OF DescriptorInfo, + ... +} + +DescriptorIDRejection ::= SEQUENCE +{ + reason DescriptorIDRejectionReason, + ... +} + +DescriptorIDRejectionReason ::= CHOICE +{ + noDescriptors NULL, -- no descriptors to report + security NULL, -- request did not meet security requirements + hopCountExceeded NULL, + noServiceRelationship NULL, + undefined NULL, + ..., + neededFeature NULL, + genericDataReason NULL, + unknownServiceID NULL -- The serviceID is not recognized by + -- the peer element +} + +DescriptorUpdate ::= SEQUENCE +{ + sender AliasAddress, + updateInfo SEQUENCE OF UpdateInformation, + ... +} + +UpdateInformation ::= SEQUENCE +{ + descriptorInfo CHOICE + { + descriptorID DescriptorID, + descriptor Descriptor, + ... + }, + updateType CHOICE + { + added NULL, + deleted NULL, + changed NULL, + ... + }, + ... +} + +DescriptorUpdateAck ::= SEQUENCE +{ + ... +} + +``` + +``` + +AccessRequest ::= SEQUENCE +{ + destinationInfo PartyInformation, + sourceInfo PartyInformation OPTIONAL, + callInfo CallInformation OPTIONAL, + usageSpec UsageSpecification OPTIONAL, + ..., + desiredProtocols SEQUENCE OF SupportedProtocols OPTIONAL +} + +AccessConfirmation ::= SEQUENCE +{ + templates SEQUENCE OF AddressTemplate, + partialResponse BOOLEAN, + ..., + supportedProtocols SEQUENCE OF SupportedProtocols OPTIONAL, + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL +} + +AccessRejection ::= SEQUENCE +{ + reason AccessRejectionReason, + ..., + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL +} + +AccessRejectionReason ::= CHOICE +{ + noMatch NULL, -- no template matched the destinationInfo + packetSizeExceeded NULL, -- use other transport type + security NULL, -- request did not meet security requirements + hopCountExceeded NULL, + needCallInformation NULL, -- Call Information must be specified + noServiceRelationship NULL, + undefined NULL, + ..., + neededFeature NULL, + genericDataReason NULL, + destinationUnavailable NULL, -- Destination was resolved but is + -- unavailable + aliasesInconsistent NULL, -- Multiple aliases identify distinct + -- destinations + resourceUnavailable NULL, -- One or more required resources are + -- unavailable + incompleteAddress NULL, -- Destination cannot be distinctly + -- identified + unknownServiceID NULL, -- The serviceID is not recognized by + -- the peer element + usageUnavailable NULL, -- Usage reporting not supported + cannotSupportUsageSpec NULL, -- Cannot comply with proposed spec + unknownUsageSendTo NULL, -- Usage sendTo could not be resolved +} + +UsageRequest ::= SEQUENCE +{ + callInfo CallInformation, + usageSpec UsageSpecification, + ... +} + +``` + +``` + +UsageConfirmation ::= SEQUENCE +{ + ... +} + +UsageRejection ::= SEQUENCE +{ + reason UsageRejectReason, + ... +} + +UsageIndication ::= SEQUENCE +{ + callInfo CallInformation, + accessTokens SEQUENCE OF AccessToken OPTIONAL, + senderRole Role, + usageCallStatus UsageCallStatus, + srcInfo PartyInformation OPTIONAL, + destAddress PartyInformation, + startTime Timestamp OPTIONAL, + endTime Timestamp OPTIONAL, + terminationCause TerminationCause OPTIONAL, + usageFields SEQUENCE OF UsageField, + ... +} + +UsageField ::= SEQUENCE +{ + id OBJECT IDENTIFIER, + value OCTET STRING, + ... +} + +UsageRejectReason ::= CHOICE +{ + invalidCall NULL, + unavailable NULL, + security NULL, + noServiceRelationship NULL, + undefined NULL, + ... + neededFeature NULL, + genericDataReason NULL, + unknownServiceID NULL -- The serviceID is not recognized by + -- the peer element +} + +UsageIndicationConfirmation ::= SEQUENCE +{ + ... +} + +UsageIndicationRejection ::= SEQUENCE +{ + reason UsageIndicationRejectionReason, + ... +} + +``` + +``` + +UsageIndicationRejectionReason ::= CHOICE +{ + unknownCall NULL, + incomplete NULL, + security NULL, + noServiceRelationship NULL, + undefined NULL, + ..., + neededFeature NULL, + genericDataReason NULL, + unknownServiceID NULL -- The serviceID is not recognized by + -- the peer element +} + +ValidationRequest ::= SEQUENCE +{ + accessToken SEQUENCE OF AccessToken OPTIONAL, + destinationInfo PartyInformation OPTIONAL, + sourceInfo PartyInformation OPTIONAL, + callInfo CallInformation, + usageSpec UsageSpecification OPTIONAL, + ... +} + +ValidationConfirmation ::= SEQUENCE +{ + destinationInfo PartyInformation OPTIONAL, + usageSpec UsageSpecification OPTIONAL, + ... +} + +ValidationRejection ::= SEQUENCE +{ + reason ValidationRejectionReason, + ... +} + +ValidationRejectionReason ::= CHOICE +{ + tokenNotValid NULL, + security NULL, -- request did not meet security requirements + hopCountExceeded NULL, + missingSourceInfo NULL, + missingDestInfo NULL, + noServiceRelationship NULL, + undefined NULL, + ..., + neededFeature NULL, + genericDataReason NULL, + unknownServiceID NULL -- The serviceID is not recognized by + -- the peer element +} + +RequestInProgress ::= SEQUENCE +{ + delay INTEGER (1..65535), + ..., + serviceControl SEQUENCE OF ServiceControlSession OPTIONAL +} + +``` + +``` + +NonStandardRequest ::= SEQUENCE +{ + ... +} + +NonStandardConfirmation ::= SEQUENCE +{ + ... +} + +NonStandardRejection ::= SEQUENCE +{ + reason NonStandardRejectionReason, + ... +} + +NonStandardRejectionReason ::= CHOICE +{ + notSupported NULL, + noServiceRelationship NULL, + undefined NULL, + ..., + neededFeature NULL, + genericDataReason NULL, + unknownServiceID NULL -- The serviceID is not recognized by + -- the peer element +} + +UnknownMessageResponse ::= SEQUENCE +{ + unknownMessage OCTET STRING, + reason UnknownMessageReason, + ... +} + +UnknownMessageReason ::= CHOICE +{ + notUnderstood NULL, + undefined NULL, + ... +} + +AuthenticationRequest ::= SEQUENCE +{ + applicationMessage ApplicationMessage, -- e.g. RAS message in + -- ITU-T Rec. H.323 + ... +} + +ApplicationMessage ::= OCTET STRING + +AuthenticationConfirmation ::= SEQUENCE +{ + ... +} + +AuthenticationRejection ::= SEQUENCE +{ + reason AuthenticationRejectionReason, + ... +} + +``` + +``` + +AuthenticationRejectionReason ::= CHOICE +{ + security NULL, + hopCountExceeded NULL, + noServiceRelationship NULL, + undefined NULL, + neededFeature NULL, + genericDataReason NULL, + unknownServiceID NULL, + securityWrongSyncTime NULL, -- time server problem or network delay + securityReplay NULL, -- replay attack encountered + securityWrongGeneralID NULL, -- wrong general ID + securityWrongSendersID NULL, -- wrong senders ID + securityIntegrityFailed NULL, -- integrity check failed + securityWrongOID NULL, -- wrong token OIDs or crypto alg OIDs + +} + +``` + +-- structures common to multiple messages + +``` + +AddressTemplate ::= SEQUENCE +{ + pattern SEQUENCE OF Pattern, + routeInfo SEQUENCE OF RouteInformation, + timeToLive INTEGER (1..4294967295), + , + supportedProtocols SEQUENCE OF SupportedProtocols OPTIONAL, + featureSet FeatureSet OPTIONAL +} + +``` + +Pattern ::= CHOICE + +``` + +{ + specific AliasAddress, + wildcard AliasAddress, + range SEQUENCE + { + startOfRange PartyNumber, + endOfRange PartyNumber + }, + +} + +``` + +RouteInformation ::= SEQUENCE + +``` + +{ + messageType CHOICE + { + sendAccessRequest NULL, + sendSetup NULL, + nonExistent NULL, + + }, + callSpecific BOOLEAN, + usageSpec UsageSpecification OPTIONAL, + priceInfo SEQUENCE OF PriceInfoSpec OPTIONAL, + contacts SEQUENCE OF ContactInformation, + type EndpointType OPTIONAL, + -- must be present if messageType = sendSetup + , + featureSet FeatureSet OPTIONAL, + circuitID CircuitInfo OPTIONAL, +} + +``` + +``` + + supportedCircuits SEQUENCE OF CircuitIdentifier OPTIONAL +} + +ContactInformation ::= SEQUENCE +{ + transportAddress AliasAddress, + priority INTEGER (0..127), + transportQoS TransportQoS OPTIONAL, + security SEQUENCE OF SecurityMode OPTIONAL, + accessTokens SEQUENCE OF AccessToken OPTIONAL, + ..., + multipleCalls BOOLEAN OPTIONAL, + featureSet FeatureSet OPTIONAL, + circuitID CircuitInfo OPTIONAL, + supportedCircuits SEQUENCE OF CircuitIdentifier OPTIONAL +} + +PriceInfoSpec ::= SEQUENCE +{ + currency IA5String (SIZE(3)), -- e.g. "USD" + currencyScale INTEGER(-127..127), + validFrom GlobalTimeStamp OPTIONAL, + validUntil GlobalTimeStamp OPTIONAL, + hoursFrom IA5String (SIZE(6)) OPTIONAL, -- "HHMMSS" UTC + hoursUntil IA5String (SIZE(6)) OPTIONAL, -- "HHMMSS" UTC + priceElement SEQUENCE OF PriceElement OPTIONAL, + priceFormula IA5String (SIZE(1..2048)) OPTIONAL, + ... +} + +PriceElement ::= SEQUENCE +{ + amount INTEGER(0..4294967295), -- meter increment + quantum INTEGER(0..4294967295), -- each or part thereof + units CHOICE + { + seconds NULL, + packets NULL, + bytes NULL, + initial NULL, + minimum NULL, + maximum NULL, + ..., + }, + ... +} + +Descriptor ::= SEQUENCE +{ + descriptorInfo DescriptorInfo, + templates SEQUENCE OF AddressTemplate, + gatekeeperID GatekeeperIdentifier OPTIONAL, + ... +} + +DescriptorInfo ::= SEQUENCE +{ + descriptorID DescriptorID, + lastChanged GlobalTimeStamp, + ... +} + +``` + +``` + +AlternatePEInfo ::= SEQUENCE +{ + alternatePE SEQUENCE OF AlternatePE, + alternateIsPermanent BOOLEAN, + ... +} + +AlternatePE ::= SEQUENCE +{ + contactAddress AliasAddress, + priority INTEGER (1..127), + elementIdentifier ElementIdentifier OPTIONAL, + ... +} + +AccessToken ::= CHOICE +{ + token ClearToken, + cryptoToken CryptoH323Token, + ..., + genericData GenericData +} + +CallInformation ::= SEQUENCE +{ + callIdentifier CallIdentifier, + conferenceID ConferenceIdentifier, + ..., + circuitID CircuitInfo OPTIONAL +} + +UsageCallStatus ::= CHOICE +{ + preConnect NULL, -- Call has not started + callInProgress NULL, -- Call is in progress + callEnded NULL, -- Call ended + ..., + registrationLost NULL -- Uncertain if call ended or not +} + +UserInformation ::= SEQUENCE +{ + userIdentifier AliasAddress, + userAuthenticator SEQUENCE OF CryptoH323Token OPTIONAL, + ... +} + +UsageSpecification ::= SEQUENCE +{ + sendTo ElementIdentifier, + when SEQUENCE + { + never NULL OPTIONAL, + start NULL OPTIONAL, + end NULL OPTIONAL, + period INTEGER(1..65535) OPTIONAL, -- in seconds + failures NULL OPTIONAL, + ... + }, + required SEQUENCE OF OBJECT IDENTIFIER, + preferred SEQUENCE OF OBJECT IDENTIFIER, + ..., +} + +``` + +``` + + sendToPEAddress AliasAddress OPTIONAL + } + + PartyInformation ::= SEQUENCE + { + logicalAddresses SEQUENCE OF AliasAddress, + domainIdentifier AliasAddress OPTIONAL, + transportAddress AliasAddress OPTIONAL, + endpointType EndpointType OPTIONAL, + userInfo UserInformation OPTIONAL, + timeZone TimeZone OPTIONAL, + ... + } + + Role ::= CHOICE + { + originator NULL, + destination NULL, + nonStandardData NonStandardParameter, + ... + } + + TimeZone ::= INTEGER (-43200..43200) -- number of seconds relative to UTC + -- including DST if appropriate + + TerminationCause ::= SEQUENCE + { + releaseCompleteReason ReleaseCompleteReason, + causeIE INTEGER (1..65535) OPTIONAL, + nonStandardData NonStandardParameter OPTIONAL, + ... + } + + ProtocolVersion ::= OBJECT IDENTIFIER + -- shall be set to + -- {itu-t(0) recommendation(0) h(8) h-225-0(2250) annex(1) g(7) + -- version(0) 2} in field annexGversion; + -- {itu-t(0) recommendation(0) h(8) 501 version(0) 1} + -- in field version + + DescriptorID ::= GloballyUniqueID + + ElementIdentifier ::= BMPString (SIZE(1..128)) + + GlobalTimeStamp ::= IA5String (SIZE(14)) + -- UTC, in the form YYYYMMDDHHmmSS + -- where YYYY = year, MM = month, DD = day, + -- HH = hour, mm = minute, SS = second + -- (for example, 19981219120000 for noon + -- 19 December 1998) + + -- + -- REPOSITORY FOR APPLICATION SPECIFIC DATA -- + -- + -- H.225.0 Annex-G profile data + -- + idAnnexGProfiles INTEGER ::= 0 + idAnnexGProfileA INTEGER ::= 1 + +``` + +``` +annexGProfileA EnumeratedParameter ::= +{ + id standard:idAnnexGProfileA +} +``` + +END -- of H501-MESSAGES + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/raw.md b/marked/H/T-REC-H.550-201712-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f98882a6e75ef8801c65a92acf80eaaf3737ad72 --- /dev/null +++ b/marked/H/T-REC-H.550-201712-I_PDF-E/raw.md @@ -0,0 +1,1056 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.550** + +(12/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Vehicular gateways and intelligent transportation systems +(ITS) – Architecture for vehicular gateways + +# --- **Architecture and functional entities of vehicle gateway platforms** + +Recommendation ITU-T H.550 + +![ITU logo: International Telecommunication Union](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a stylized globe with a red lightning bolt striking through it, and the text "ITU International Telecommunication Union" to its right. + +ITU logo: International Telecommunication Union + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.550 + +# Architecture and functional entities of vehicle gateway platforms + +## Summary + +Recommendation ITU-T H.550 describes the architecture, functional architecture framework and functional entities of vehicle gateway platforms (VGPs). Some signalling flows of VGP are also described in Appendix I. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.550 | 2017-12-14 | 16 | 11.1002/1000/13434 | + +## Keywords + +Architecture, functional architecture framework, functional entities, signalling flow, vehicle gateway platforms, VGP. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Introduction..... | 3 | +| 7 Architecture of VGP ..... | 4 | +| 7.1 Functional architecture framework..... | 6 | +| 8 Functional entities of VGP ..... | 8 | +| 8.1 Vehicle gateway ..... | 8 | +| 8.2 Service functionalities ..... | 11 | +| 8.3 Services..... | 14 | +| 8.4 Management ..... | 17 | +| Appendix I – Signalling flows of VGP..... | 19 | +| I.1 Signalling flows for emergency information display in V2V scenario ..... | 19 | +| I.2 Signalling flows for traffic data download in V2I scenario ..... | 20 | +| I.3 Signalling flows of remote UI scenario..... | 21 | +| I.4 Signalling flows of emergency call scenario..... | 22 | +| I.5 Signalling flows of anti-stolen scenario ..... | 23 | +| I.6 Signalling flows of remote software update scenario..... | 24 | +| I.7 Signalling flows of navigation scenario ..... | 25 | +| Bibliography..... | 26 | + + + +# Recommendation ITU-T H.550 + +# Architecture and functional entities of vehicle gateway platforms + +# 1 Scope + +This Recommendation specifies the architecture, functional architecture framework and functional entities for vehicle gateway platforms (VGPs). Some signalling flows of VGP are also described in Appendix I. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T F.749.1] Recommendation ITU-T F.749.1 (2015), *Functional requirements for vehicle gateways*. + +[ITU-T F.749.2] Recommendation ITU-T F.749.2 (2017), *Service requirements for vehicle gateway platforms*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 driver-vehicle interface (DVI)** [ITU-T F.749.2]: The integrated user interface for the vehicle. It includes visual displays, loudspeakers, microphones, manual input controls, etc. + +**3.1.2 functional entity** [b-ITU-T Y.2012]: An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. + +**3.1.3 intelligent transport systems (ITS)** [b-ITU-R handbook]: ITS can be defined as systems utilizing the combination of computers, communications, positioning and automation technologies to improve the safety, management and efficiency of terrestrial transport systems. + +**3.1.4 nomadic devices** [ITU-T F.749.1]: Nomadic devices include all types of information and communication as well as entertainment devices that can be brought into the vehicle by the driver and/or passengers to be used while driving. Examples include mobile phones, portable computers, tablets, mobile navigation devices, portable media players and multi-functional smart phones. + +**3.1.5 remote user interface (UI)** [ITU-T F.749.2]: An approach to realize the interaction between applications in nomadic devices and the driver-vehicle interface (DVI). The UI of applications in nomadic devices can be displayed in the vehicle's touch screen and drivers are able to control the applications through DVIs (touch screen, buttons etc.). A remote UI can help drivers avoid distraction from applications and thus reduce the probability of accidents. + +**3.1.6 telematics** [b-ISO 15638-16]: Telematics is the use of wireless media to obtain and transmit (data) from a distant source. + +**3.1.7 vehicle gateway (VG)** [ITU-T F.749.1]: A VG is a device in a vehicle that enables communications between a device in the vehicle and another device which may be physically located either inside the vehicle or outside the vehicle (e.g., roadside station, cloud-based server, etc.). A VG provides standardized interfaces and protocols, communications across heterogeneous networks, optimized network selection based on application needs and network QoS, arbitration and integration of network communications, security and switching network connections to maintain service continuity. + +**3.1.8 vehicle gateway platform (VGP)** [ITU-T F.749.1]: A VGP is the collection of ICT hardware and software in a vehicle operating as an open platform to provide an integrated runtime environment for delivering the communications services of a VG. A VGP may also provide higher layer communications services such as interaction with the driver through the driver-vehicle access services and so on. Subsystems dedicated solely to vehicle operation are not considered part of the VGP. Supported applications/services include ITS and infotainment. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------------| +| API | Application Programming Interface | +| CAN | Controller Area Network | +| CI | Communication Interface | +| DLL | Data Link Layer | +| DVA | Driver Vehicle Access | +| EAP | Extensible Authentication Protocol | +| ECU | Electronic Control Unit | +| ETC | Electronic Toll Collection | +| GPS | Global Positioning System | +| GRE | Generic Routing Encapsulation | +| HUD | Head Up Display | +| ICT | Information and Communications Technology | +| IP | Internet Protocol | +| ITS | Intelligent Transport System | +| L2TP | Layer 2 Tunnelling Protocol | +| MAC | Medium Access Control | +| MAN | Metropolitan Area Network | +| MIB | Management Information Base | +| NAT | Network Address Translation | +| OSI | Open System Interconnection | +| POI | Point Of Interest | +| PPTP | Point to Point Tunnelling Protocol | + +| | | +|------|-----------------------------------| +| PSAP | Public Service Answering Point | +| QoS | Quality of Service | +| RSU | Roadside Unit | +| SAM | Situational Awareness Management | +| SIM | Subscriber Identification Module | +| SSL | Secure Sockets Layer | +| TCP | Transmission Control Protocol | +| TLS | Transport Layer Security Protocol | +| TSP | Telematics Service Provider | +| UDP | User Datagram Protocol | +| UI | User Interface | +| V2I | Vehicle-to-Infrastructure | +| V2V | Vehicle-to-Vehicle | +| VG | Vehicle Gateway | +| VGP | Vehicle Gateway Platform | +| VPN | Virtual Private Network | +| WLAN | Wireless Local Area Network | +| WPAN | Wireless Personal Area Network | +| WWAN | Wireless Wide Area Network | + +# 5 Conventions + +In this Recommendation: + +- The keywords "shall" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. +- The keywords "should" indicate an optional requirement which is permissible. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the vendor. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +# 6 Introduction + +Figure 1 shows VGP positioning in the intelligent transport system (ITS) reference model: there are six major scenarios, i.e., vehicle to vehicle, vehicle to infrastructure, vehicle to cloud-based server, vehicle to nomadic device, vehicle to pedestrian/bicycle and interaction with in-vehicle network scenarios. + +- The vehicle to vehicle (V2V) scenario mainly describes the safety and auto-driving scenarios in which vehicles communicate with each other. +- The vehicle to infrastructure (V2I) scenario mainly describes the safety, electronic toll collection (ETC) and traffic information exchange scenarios in which vehicles communicate with roadside infrastructures. +- The vehicle to cloud-based server scenario mainly describes the emergency call and telematics scenarios in which vehicles communicate with cloud-based services. + +- The vehicle to nomadic device scenario mainly describes the telecommunication and remote user interface (UI) scenarios in which vehicles connect to nomadic devices. +- The vehicle to pedestrian/bicycle scenario mainly describes the safety warning scenarios in which vehicles communicate with the devices carried by pedestrian/bicycles. +- Interaction with the in-vehicle network scenario mainly describes the vehicle diagnostics, remote data collection and vehicle remote control scenarios in which a VGP communicates with the proprietary in-vehicle network. + +![Diagram illustrating the location of VGP in the ITS reference model. The central component is the VGP (Vehicle Gateway), which is connected to various entities: Cloud-based servers (via WWAN), Infrastructure (via Short-to-medium range wireless), Nomadic device (via Short-to-medium range wireless), Vehicle (via Short-to-medium range wireless), Pedestrian/bicycle (via Short-to-medium range wireless), and Proprietary in-vehicle network (via a bidirectional connection).](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +The diagram shows the VGP (Vehicle Gateway) at the center, connected to several external systems. At the top, 'Cloud-based servers' are connected via a 'WWAN' (Wide Area Network) represented by a satellite icon. To the left, 'Infrastructure' (represented by traffic lights and a road scene) is connected via 'Short-to-medium range wireless' communication. Above the VGP, a 'Nomadic device' (represented by a smartphone and tablet) is also connected via 'Short-to-medium range wireless' communication. To the right, a 'Vehicle' (represented by a car icon) and a 'Pedestrian/bicycle' (represented by a person walking and a person on a bicycle) are connected via 'Short-to-medium range wireless' communication. Below the VGP, it is connected to a 'Proprietary in-vehicle network' (represented by a horizontal line) which is further connected to a car icon. + +Diagram illustrating the location of VGP in the ITS reference model. The central component is the VGP (Vehicle Gateway), which is connected to various entities: Cloud-based servers (via WWAN), Infrastructure (via Short-to-medium range wireless), Nomadic device (via Short-to-medium range wireless), Vehicle (via Short-to-medium range wireless), Pedestrian/bicycle (via Short-to-medium range wireless), and Proprietary in-vehicle network (via a bidirectional connection). + +H.550(17)\_F01 + +**Figure 1 – Location of VGP in the ITS reference model** + +# 7 Architecture of VGP + +Figure 2 presents the high-layer architecture of VGPs. The functionalities in the various subsystems of a VGP include: + +- vehicle gateway +- services +- service functionalities +- management. + +![Figure 2 – High-level architecture of a VGP. The diagram shows a layered architecture. At the top, 'External applications' (Navigation, Notification and message, Audio and video streaming, Others) and a 'SAM' block are connected to the 'Vehicle gateway platform (VGP)'. The VGP is divided into three main functional blocks: (1) 'Services' (Software and application data management service, Other services, Driver-vehicle access (DVA) service), (2) 'Service functionalities' (Session management, In-vehicle resource access management), and (3) 'Management' (Device management, Security management, Wired and wireless access management). Below the VGP is the 'Vehicle gateway (VG)' which contains 'Networking and transport' and 'Communication interfaces' for nomadic devices (USB, Wireless LAN, Short range wireless), external networks (Cellular, Wireless LAN, Short-to-medium range wireless), and in-vehicle devices (In-vehicle bus interfaces). The VG connects to 'Server/service platform/RSUs', 'ECUs and sensors' (Air conditioning, Fuel warning, Security module), and a 'Driver-vehicle interface (DVI)' (Touch panel, Push buttons, Microphone, Display screen). The reference 'H.550(17)_F02' is at the bottom right.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Figure 2 – High-level architecture of a VGP. The diagram shows a layered architecture. At the top, 'External applications' (Navigation, Notification and message, Audio and video streaming, Others) and a 'SAM' block are connected to the 'Vehicle gateway platform (VGP)'. The VGP is divided into three main functional blocks: (1) 'Services' (Software and application data management service, Other services, Driver-vehicle access (DVA) service), (2) 'Service functionalities' (Session management, In-vehicle resource access management), and (3) 'Management' (Device management, Security management, Wired and wireless access management). Below the VGP is the 'Vehicle gateway (VG)' which contains 'Networking and transport' and 'Communication interfaces' for nomadic devices (USB, Wireless LAN, Short range wireless), external networks (Cellular, Wireless LAN, Short-to-medium range wireless), and in-vehicle devices (In-vehicle bus interfaces). The VG connects to 'Server/service platform/RSUs', 'ECUs and sensors' (Air conditioning, Fuel warning, Security module), and a 'Driver-vehicle interface (DVI)' (Touch panel, Push buttons, Microphone, Display screen). The reference 'H.550(17)\_F02' is at the bottom right. + +**Figure 2 – High-level architecture of a VGP** + +The VGP services include software and an application data management service, driver-vehicle access service, and other services (see block (1) in Figure 2). Service functionalities include session management and in-vehicle resource access management (see block (2) in Figure 2). Management includes device management; security management and wired and wireless access management (see block (3) in Figure 2). Services support external applications such as navigation and infotainment to accomplish the session establishment, data format conversion and specific processing. A general description of the services and management of a VGP are presented below. + +- **Vehicle gateway:** The VG functionality covers OSI layers 1 to 4. It includes transport functions, networking functions and network access functions. +- **Services:** Services support basic service capabilities for applications running and data/message processing. It includes the driver-vehicle access (DVA) service, software and application data management service, and other services. +- **Service functionalities:** Service functionalities support service management functions such as session management and in-vehicle resource access management. + +- **Management:** Management supports device management, security management and wired and wireless access management. + +## 7.1 Functional architecture framework + +The functional architecture framework of the VGP is shown in the Figure 3. All independent functional blocks are connected with each other through the reference points. There are two types of reference points in the VGP: media and control. + +![Functional architecture framework of VGP diagram showing layers for Applications, Service, Service functionalities, VG, and Management, with various reference points (Mat, Cdt, Mdt, etc.) connecting them to external entities like SAM, Nomadic devices, RSUs, and ECUs/DVIs.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram illustrates the functional architecture framework of the VGP (Vehicle Gateway Protocol). It is organized into several layers and external entities: + +- External Entities:** + - Applications:** Connected to the Service layer via Media (Mat) and Control (Cat) reference points. + - SAM:** Connected to the Service layer via the Control (Csv) reference point. +- VGP (Vehicle Gateway Protocol) Layer:** + - Service Layer:** Contains three functional blocks: + - DVA service:** Connected to Service functionalities via Media (Mdt) and Control (Cdt) reference points. + - Software and application data management service:** Connected to Service functionalities via Media (Msat) and Control (Csat) reference points. + - Other services:** Connected to Service functionalities via Media (Mot) and Control (Cot) reference points. + - Service functionalities Layer:** Contains two functional blocks: + - Session management:** Connected to the VG layer via Media (Msn) and Control (Csn) reference points. It also has a Media (Msi) reference point connection to In-vehicle resource access management. + - In-vehicle resource access management:** Connected to the VG layer via Media (Mii) and Control (Cii) reference points. + - VG (Vehicle Gateway) Layer:** Contains three functional blocks: + - Communication for nomadic devices:** Connected to external entities (Nomadic device, RSU/Cellular networks) via Media (Mnn, Mnv) and Control (Cnn, Cnv) reference points. + - Communication for the external networks:** Connected to external entities (RSU/Cellular networks, Pedestrian/bicycle) via Media (Cer, Mer, Cep, Mep) and Control (Cer, Mer, Cep, Mep) reference points. + - Communication for in-vehicle devices:** Connected to external entities (Other vehicles, Firewall/gateway ECUs/DVIs) via Media (Mev, Miv) and Control (Cev, Civ) reference points. + - Management Layer:** A dashed box containing three functional blocks: + - Device management:** Connected to the Service layer via the Cms reference point. + - Security management:** Connected to the Service functionalities layer via the Cmsf reference point. + - Wired and wireless access management:** Connected to the VG layer via the Cmvv reference point. +- External Connections:** + - Nomadic device:** Contains Applications; connects to the VG via Mnn, Mnv, Cnn, and Cnv reference points. + - RSU / Cellular networks:** Connects to the VG via Cer, Mer, Cep, and Mep reference points. + - Pedestrian/bicycle:** Connects to the VG via Cep and Mep reference points. + - Other vehicles:** Contains Applications; connects to the VG via Mev, Miv, Cev, and Civ reference points. + - Firewall/gateway ECUs/DVIs:** Connects to the VG via Mev, Miv, Cev, and Civ reference points. + - Cloud server:** Contains Applications; connects to the RSU/Cellular networks block. + +**Legend:** + +- Media reference points are represented by solid arrows. +- Control reference points are represented by dashed arrows. + +H.550(17)\_F03 + +Functional architecture framework of VGP diagram showing layers for Applications, Service, Service functionalities, VG, and Management, with various reference points (Mat, Cdt, Mdt, etc.) connecting them to external entities like SAM, Nomadic devices, RSUs, and ECUs/DVIs. + +**Figure 3 – Functional architecture framework of VGP** + +Media reference points include: + +- Mnn reference point: media reference point between a nomadic device and the VG; +- Mer reference point: media reference point between the roadside unit (RSU)/cellular networks and the VG; +- Mev reference point: media reference point between other vehicles and the VG; +- Mep reference point: media reference point between a pedestrian/bicycle and the VG; +- Miv reference point: media reference point between the electronic control unit (ECU)/DVI and the VG; + +- Msn reference point: media reference point between communication for nomadic devices and session management service functionalities; +- Mat reference point: media reference point between session management service functionality and applications; +- Msc reference point: media reference point between communication for external networks and session management service functionalities; +- Mii reference point: media reference point between communication for in-vehicle devices and in-vehicle resource access management service functionalities; +- Msi reference point: media reference point between session management service functionality and in-vehicle resource access management service functionalities; +- Mdt reference point: media reference point between DVA service and in-vehicle resource access management/Session management service functionalities; +- Msat reference point: media reference point between the software and application data management service and in-vehicle resource access management/session management service functionalities; +- Mot reference point: media reference point between other services and in-vehicle resource access management/session management service functionalities; +- Mvg reference point: media reference point between the entities inside the VG. + +Control reference points include: + +- Cnn reference point: control reference point between a nomadic device and the VG; +- Cer reference point: control reference point between the RSU/cellular networks and the VG; +- Cep reference point: control reference point between a pedestrian/bicycle and the VG; +- Cev reference point: control reference point between other vehicles and the VG; +- Civ reference point: control reference point between the ECU/DVI and the VG; +- Csn reference point: control reference point between communication for nomadic devices and session management service functionality; +- Csc reference point: control reference point between communication for external networks and session management service functionality; +- Cii reference point: control reference point between communication for in-vehicle devices and in-vehicle resource access management service functionality; +- Cat reference point: control reference point between session management service functionality and applications; +- Cdt reference point: control reference point between session management/in-vehicle resource access management service functionality and DVA service; +- Csat reference point: control reference point between in-vehicle resource access management/session management service functionality and the software and application data management service; +- Cot reference point: control reference point between in-vehicle resource access Management/Session management service functionality and other services; +- Csv reference point: control reference point between the VGP and situational awareness management (SAM); +- Cms reference point: control reference point between device management/security management and services; + +- Cmsf reference point: control reference point between device management/security management and service functionalities; +- CmvG reference point: Control reference point between device management/security management/wired and wireless access management and the VG; +- Cvg reference point: control reference point between the entities inside the VG. + +# **8 Functional entities of VGP** + +## **8.1 Vehicle gateway** + +### **8.1.1 Definition of vehicle gateway** + +A VG is a function module of a VGP. VGs are devices in a vehicle that enable real-time two-way communication between an object in the vehicle and another object that may be physically located either inside or outside the vehicle (e.g., roadside station, cloud-based server, etc.). It provides standardized interfaces and protocols, communications across heterogeneous networks, optimized network selection based on application needs and network QoS, arbitration and integration of network communications, security and switching network connections to maintain service continuity. + +A VG includes networking and transport functions and network access functions. + +### **8.1.2 Networking and transport functions** + +The networking and transport functions cover the functions of the network and transport layers in the open system interconnection (OSI) model. + +The VG should support several network protocols in the network layer, including IP (internet protocol) and non-IP protocols. + +- The VG shall support IP protocols, e.g., IPv4 or IPv6 for Internet connectivity including the routing capability to the selected network. +- The VG should support other non-IP network protocols based on the supported interfaces. These protocols are meant to support applications with severe timing constraints and low latency requirements, e.g., time-critical safety-related applications, road safety and traffic efficiency applications. +- The VG should support the establishment of VPN in the network layer, e.g., IP Sec VPN, etc. +- The VG shall support several transport layer protocols in the transport layer, including the transmission control protocol / user datagram protocol (TCP/UDP). The VG should implement data segments and provide end-to-end and reliable/unreliable transportation for the upper layer. In addition, the VG should implement end-to-end flow control and error control in the transport layer. It should also support the network address translation (NAT) function to provide Internet access to every in-vehicle device. + +### **8.1.3 Network access functions** + +#### **8.1.3.1 Description** + +Network access covers the OSI model physical layer (PHY), which connects physically to the communication medium and to the data link layer (DLL). The DLL may be subdivided into the medium access control (MAC) sublayer (managing the access to the communication medium) and the logical link control (LLC) sublayer. + +A VG should provide wired and wireless communication Interfaces (CIs) as follows: + +- wired access (e.g., USB); + +- wireless access (e.g., 2G / 3G / 4G, IEEE 802.11 [b-IEEE 802.11] and legacy dedicated short-range communications), which are used to communicate with devices outside the vehicle. Wireless access such as WLAN and short-range wireless CIs (e.g., wireless personal area networks) are used for communicating with in-vehicle nomadic devices (e.g., smartphones). +- A VG should support the establishment of VPN in DLL, e.g., Layer 2 Tunnelling Protocol (L2TP), Generic Routing Encapsulation (GRE), and Point-To-Point Tunnelling Protocol (PPTP). + +#### 8.1.3.2 Communications with nomadic devices + +A VG should support interfaces for consumers to access in-vehicle modules/network via nomadic devices, such as USB, wireless LAN and short-range wireless CIs. + +#### 8.1.3.3 Communication with external networks + +A VG should support cellular CIs which include CIs for 2G, 3G, 4G and future cellular technologies, wireless LAN CI, short-to-medium range wireless CIs and other CIs. + +A cellular CI shall support the establishment and termination of a medium-dependent session. It is necessary to follow one of the connection establishment procedures defined in cellular communications standards, and the procedures defined in the relevant cellular communications protocols shall be followed. + +A VG shall support the wireless LAN CI to get Internet access via a nomadic device (e.g., mobile phone). A VG connects to the nomadic device using a wireless LAN and uses the device as a gateway to access the Internet. + +These short-to-medium wireless CIs are used to provide vehicle-to-vehicle (V2V) and vehicle to-infrastructure (V2I) communications in order to satisfy time-critical safety-related applications, traffic efficiency applications, cooperative local services and payment services. + +Short-to-medium range wireless CIs may include CIs for IEEE 802.11 or 4G device-to-device. + +Besides the cellular communications and short-to-medium range communications listed above, other outside-vehicle communications include global navigation satellite systems, infrared, mm wave communications, etc. + +#### 8.1.3.4 Communications with in-vehicle devices + +A VGP shall support CIs to connect with the in-vehicle network, e.g., controller area network (CAN) bus interface protocol [b-ISO 11898-1]. + +A VGP should support the collection of (read-only) vehicle information from ECUs and sensors, e.g., engine control, lighting, air conditioning, power locks, active suspension, power seats, airbag, etc. The CI should also support backend servers and nomadic devices to remotely control (read and write) vehicle behaviour while security is guaranteed and communication authorized. + +### 8.1.4 Reference points with other function entities + +The reference points between the VG and other function entities are as follows: + +- The reference points between the VG and session management services are as follows: + - 1) **Reference point Msn:** This reference point is used to transfer media data that is received from nomadic devices through reference point Mnn to session management services. It is also used to receive media data from session management services which is then transferred to nomadic devices. + - 2) **Reference point Csn:** This reference point is used to transfer control messages that are received from nomadic devices through reference point Cnn to session management + +services. It is also used to receive control messages from session management services and then transfer them to nomadic devices. The examples of these control messages include the control messages of the remote UI. + +- 3) **Reference point Msc:** This reference point is used to transfer media data that is received from an external network through reference point Mer/Mep/Mev to session management services. It is also used to receive media data from session management services and then transfer it to the RSU/cloud server, pedestrian/bicycle and other vehicles. +- 4) **Reference point Csc:** This reference point is used to transfer control messages that are received from the RSU/cloud server, pedestrian/bicycle and other vehicles through reference point Cer/Cep/Cev to session management services. It is also used to receive control messages from session management services. The control messages which are received from session management services should include network capabilities request messages (e.g., bandwidth, QoS request) and the messages that will be transferred to the RSU/cloud server, pedestrian/bicycle and other vehicles. + +– The reference points between the VG and in-vehicle resource access management services are as follows: + +- 1) **Reference point Mii:** This reference point is used to transfer data that is received from the in-vehicle network through reference point Miv to in-vehicle resource access management services. Mii is also used to receive media data from in-vehicle resource access management services and then transfer it to the in-vehicle network. +- 2) **Reference point Cii:** This reference point is used to transfer control messages that are received from the in-vehicle network through reference point Civ to in-vehicle resource access management services. It is also used to receive control messages from in-vehicle resource access management services and then transfer them to the in-vehicle network. The examples of these control messages include the vehicle remote control messages, vehicle data collecting control messages and OTA update of ECU control messages. + +– The reference points between the VG and management are as follows: + +- 1) **Reference point Cmv:** This reference point is used to send bidirectional manage messages between the VG and wired and wireless access/security/device management. The control messages should include notifications of connection status in communication networks, indications of handover between the same network and different networks, control of communication connection establish/disconnect. The control messages should include keys/certifications/ciphers acquisition, encryption schemes acquisition and authentication/authorization for the communication process between the VG and external networks/nomadic devices. The control messages should also be used to retrieve the hardware/software running status of the VG. + +– The reference points between the VG and nomadic devices are as follows: + +- 1) **Reference point Cnn:** This reference point is used to send bidirectional control messages between the VG and nomadic devices. The control messages should include application control messages (e.g., remote UI control messages, wireless LAN hotspot control messages etc.). +- 2) **Reference point Mnn:** This reference point is used to send bidirectional media data between the VG and nomadic devices. + +– The reference points between the VG and RSU/cellular networks are as follows: + +- 1) **Reference point Cer:** This reference point is used to send bidirectional control messages between the VG and RSU/cellular networks. Through the RSU/cellular networks, the control messages are forwarded to the cloud server. + +- 2) **Reference point Mer:** This reference point is used to send bidirectional media data between the VG and RSU/cellular networks. Through the RSU/cellular networks, the media data is forwarded to the cloud server. + +– The reference points between the VG and a pedestrian/bicycle are as follows: + +- 1) **Reference point Cep:** This reference point is used to send bidirectional control messages between the VG and pedestrian/bicycle. +- 2) **Reference point Mep:** This reference point is used to send bidirectional media data between the VG and a pedestrian/bicycle. + +– The reference points between the VG and other vehicles are as follows: + +- 1) **Reference point Cev:** This reference point is used to send bidirectional control messages between the VG and other vehicles. +- 2) **Reference point Mev:** This reference point is used to send bidirectional control messages between the VG and other vehicles. + +– The reference points between the VG and in-vehicle network are as follows: + +- 1) **Reference point Civ:** This reference point is used to send bidirectional control messages between VG and in-vehicle network. +- 2) **Reference point Miv:** This reference point is used to send bidirectional media data between the VG and in-vehicle network. + +– The reference points inside the VG are as follows: + +- 1) **Reference point Cvg:** This reference point is used to send bidirectional control messages between the sub-modules inside the VG. +- 2) **Reference point Mvg:** This reference point is used to send bidirectional media data between the sub-modules inside the VG. + +## 8.2 Service functionalities + +### 8.2.1 Session management service functionality + +#### 8.2.1.1 Definition of session management service functionality + +The session management services functionality is a functional module of the VGP. It is in the OSI model session layer and presentation layer. The session management services are the data bus for data exchange between the VG, services, external applications and the security entity. + +The session management services shall support session connection management and data processing functions. The session connection management function includes the establishment/management/termination of session connection, attack detection and alarm generation. The data processing function includes data routing/dispatch, encryption and decryption, compression, data format conversion, data filtering, etc. + +#### 8.2.1.2 Session connection management + +The session management service functionality should implement establishment/management/termination of session connections between services/external applications. Session management services should monitor the status of session connections and select proper communication network cooperation with the VG to provide a secure and high-quality connection. + +The session management service functionality should provide unified APIs (application programming interfaces) for external applications. Session management services should provide proper communication connection according to the requirements (e.g., QoS, security requirements) of applications. + +The session management service functionality should support the establishment of the transport layer security protocol / secure socket layer (TLS/SSL) VPN. + +The session management service functionality should support attack detection and alarm generation (e.g., firewall functions) to guarantee the security of a connection. + +#### **8.2.1.3 Data processing** + +The session management service functionality should process data to guarantee the consistency of the data format, high efficiency and security of data transportation. + +- The session management service functionality should process two-way data format transformation to transport data between the VG and applications. +- The session management service functionality should compress and decompress two-way data to increase the efficiency of data transportation. +- The session management service functionality should support the technologies of data encryption and decryption, and digital signatures to guarantee the safety of data transportation. +- The session management service functionality should support data exchange management, including the data/message route management function and data/message dispatching management function. + - 1) The data/message routing management function supports the routing of the data/message. It selects the appropriate interface and protocol to route data/messages between the VG and external applications according to preconfigured routing tables. + - 2) The data/message dispatching management function should support: + - i. permission/rejection for data/message requests of applications according to the instructions of the security management function; + - ii. real-time processing of high-priority data/message and pause/resume processing of low-priority data/message. + +### **8.2.2 In-vehicle resource access management service functionality** + +#### **8.2.2.1 Definition of in-vehicle resource access management service functionality** + +Because in-vehicle resource access has a strong influence on driving safety, VGP should have an independent and isolated service to implement data exchange between external applications and an in-vehicle network. + +The in-vehicle resource access management service functionality shall support data exchange and connection management between external applications/networks and in-vehicle networks. It shall guarantee security and high-efficiency of data exchange and connection establishment. + +#### **8.2.2.2 Component description** + +The in-vehicle resource access management service functionality should implement data exchange between external applications/devices and the in-vehicle network through the connection to session management services. + +The in-vehicle resource access management service functionality should implement external applications access authentication/authorization, and keys/certifications/ciphers acquisition through the connection to the security entity. + +The in-vehicle resource access management service functionality should support the establishment of a secure connection to the in-vehicle network through the interaction with a firewall/gateway in a vehicle. + +The in-vehicle resource access management service functionality should support data encryption and decryption, data compression, protocol conversion and data format conversion of data exchange between external applications and the in-vehicle network. + +The in-vehicle resource access management service functionality should support the access control function of external applications, such as request frequency control. It also should support the access control function according to the driving state that can be acquired from the external SAM function. + +### 8.2.3 Reference points with other function entities + +The reference points between service functionalities and other function entities are as follows: + +- The reference points between service functionalities and a DVA service are: + - **Reference point Cdt:** This reference point is used to send bidirectional control messages between service functionalities and DVA services. The control messages should support DVI working status update, DVI capability request, etc. + - **Reference point Mdt:** This reference point is used to send bidirectional media data between service functionalities and DVA services. The media data should support audio/video stream or other data formats. +- The reference points between service functionalities and the software and application data management service are: + - 1) **Reference point Csat:** This reference point is used to send bidirectional control messages between service functionalities and the software and application data management service. The control messages should support modify/delete/add request, storage/read request of application data, etc. The control messages should also support software deployment/update/configuration request, etc. + - 2) **Reference point Msat:** This reference point is used to exchange data between service functionalities and the software and application data management service for application data storage/read and software deployment/update. +- The reference points between service functionalities and other services are: + - 1) **Mot reference point:** This is the media reference point between service functionalities and other services. + - 2) **Cot reference point:** This is the control reference point between service functionalities and other services. +- The reference point between session management service functionality and the in-vehicle resource access management service functionality is: + - 1) **Reference point Msi:** This reference point is used to exchange data between the session management service functionality and in-vehicle resource access management service functionality. The data includes vehicle data that is exchanged between external applications and the in-vehicle network (e.g., CAN, [b- ISO 17458-1], [b-MOST]). +- The reference points between the session management service functionality and external applications are: + - 1) **Reference point Mat:** This reference point is used to exchange data between the session management service functionality and external applications which run on the VGP. + - 2) **Reference point Cat:** This reference point is used to send bidirectional control messages between the session management service functionality and external applications which run on the VGP. +- The reference points between service functionalities and the VG are: + +1) **Reference point Msn, Msc, Mii, Csn, Csc, Mii:** These reference points refer to clause 8.1.4. + +– The reference point between service functionalities and management is: + +1) **Reference point Cmsf:** This reference point is used to send bidirectional manage messages between service functionalities and wired and security/device management. The control messages should include keys/certifications/ciphers acquisition, encryption schemes acquisition and authentication/authorization for session connection, data processing and vehicle resource access. The control messages should also be used to retrieve software running the status of service functionalities. + +## 8.3 Services + +### 8.3.1 Driver-vehicle access service + +#### 8.3.1.1 Definition of driver-vehicle access service + +The driver-vehicle access (DVA) service is a functional module of the VGP. The DVA service supports the function of interacting between DVIs inside vehicles and applications, include louder speaker, buttons and visual display equipment (e.g., display screen and head up display). + +#### 8.3.1.2 Component description + +The DVA service should control which DVIs in a vehicle can be used by different applications (e.g., lower voice, disconnect from display or change display mode etc.) depending on the instructions from the external SAM function. + +The DVA service should complete the following functions by interacting with service functionalities: + +- The DVA service should analyse and instruct whether the message/data can be routed, delayed or cancelled according to the driving scene that is received from the external SAM function. +- The DVA service should support retrieve working status of DVIs. And DVA service should support changing the data format (e.g., change from video format to audio format) and re-routing to different DVIs according to the working status of DVIs. +- The DVA service should support remote UI between applications and DVIs. The DVA service should support DVI capability authentication/authorization through security management when the external applications request DVI access. + +### 8.3.2 Software and application data management service + +#### 8.3.2.1 Software management service + +##### 8.3.2.1.1 Description + +The software management service allows the deployment and maintenance of software over the different software-based units located inside or outside the VGP in an efficient, flexible and secure way. This service also takes care of the consistency between the software package versions deployed over the different software-based units. + +##### 8.3.2.1.2 Component description + +The software management service is made up of the following components: + +- A common, fast, secure, safe and flexible interface for software package upload from external devices or servers. This interface is used either by external devices such as a nomadic device connected to the VGP using the wireless LAN interface with specific maintenance applications used on the nomadic interface implementing this interface via a + +specific API. The interface provides a strong authentication scheme in order to prevent unauthorized users from making modifications that may disrupt the vehicle system. The authentication scheme is able to manage some user rights in order to allow the maintenance application to access only some software modules or units inside the vehicle. The software transfer is implemented over a reliable and fast transport layer, preferably with an encryption feature in order to protect code interception by unauthorized people. + +- Several interfaces are used to deploy in a safe way the new software package version on the corresponding updatable modules or software units. These can later be located inside or outside the VGP. Device units inside the vehicle are heterogeneous because of the use of different technologies and communication buses. An IP-based interface is provided to update the different VGP modules or services, and also for IP-based in-vehicle devices such as the head unit or passenger infotainment unit. Some specific interfaces are also provided for non-IP based devices such as ECUs, cameras, etc. As some ECUs may integrate some security modules, it is required that the corresponding non-IP interface shall support the specifications of the underlying secure protocols implemented by these modules. +- A database is used for storing the different software package version, encryption keys, signatures and authorizations for the different updatable modules or software unit. +- There is a management sub-module in charge of checking software packages before deployment, handling their installation, configuration and removal, and providing installation traces (journaling). Journal access is restricted to authorized parties, and it is preferably protected by signature and encryption schemes in order to provide reliability and verifiability of the logs. + +#### **8.3.2.2 Application data management service** + +##### **8.3.2.2.1 Description** + +The application data management service is used by the different VGP components to store some data that shall be kept intact from one software version to another. + +The data can be shared between different components and may also be accessed from external devices (such as nomadic devices or remote servers) for monitoring or maintenance purposes. For instance, a management application running over a nomadic device may require access to the version and publication date of the different navigation maps installed over the head unit. + +Some metadata is associated with each defined data entry (such as access permissions, data type and size) and allows flexible and secure data sharing between different components. + +##### **8.3.2.2.2 Component description** + +The application data management service is made up of the following components: + +- A common, fast, secure, safe and flexible interface for accessing stored data from external devices or servers. This interface may be used either by applications running over external devices such as a nomadic device or cloud servers, and implementing a specific API derived from the interface specification. The interface provides a strong authentication scheme in order to prevent unauthorized users from making modifications that may disrupt the vehicle system. The authentication scheme allows managing some user rights in accordance with the permission rights associated with each data entry. Thanks to this feature, the different applications only have access to some of the shared data, and have limited rights to operate on them. Permissions may include read, modify, delete. +- Several interfaces are available to allow data access from the corresponding updatable modules or software units. These can later be located inside or outside the VGP. Device units inside the vehicle are heterogeneous because of the use of different technologies and communication buses. The application data management service provides different + +"internal access interfaces" to allow the in-vehicle devices, services and applications running over the VGP or outside the VGP to operate on data entries. The type of operations over the data entries and the associated metadata are addition, removal, modifications and reading. An IP-based interface provides data access to the different VGP modules or services, and also for IP-based in-vehicle devices such as a head unit or passenger infotainment unit. Some specific interfaces are provided for non-IP based devices such as ECUs. + +- There is a robust database used for storing data, data version, encryption key, signatures and authorizations for the different updatable modules or software units. This database is used to store the data used by the different software components in a secure way in order to avoid possible intrusion, software leaks or malicious modifications that may be critical for vehicle security. Some extra metadata is associated with each application data entry such as data version number, modification date, data type, size, owner application, permissions, physical location of stored data when data is not physically stored in the VGP, encryption key when data requests encryption. They shall be also stored in the database. +- There is a journaling sub-module in charge of providing data access traces. Journal access is restricted to only authorized parties and is protected with signature and encryption schemes in order to provide reliability and verifiability of the logs. + +##### 8.3.2.2.3 Interaction with software management service + +The application data management service interacts with the software management service described in clause 8.3.2.1 by using the software package management sub-module through the IP-based interface, both being provided by the software management service. In particular, it is useful to get the properties of the in-vehicle components, services and applications that request access to application data. + +### 8.3.3 Reference points with other function entities + +The reference points between services and other function entities are as follows: + +- The reference points between the driver-vehicle access service and service functionalities are: + - 1) **Reference point Mdt:** refer to clause 8.2.3. + - 2) **Reference point Cdt:** refer to clause 8.2.3. +- The reference points between the software and application data management service and service functionalities are: + - 1) **Reference point Msat:** refer to clause 8.2.3. + - 2) **Reference point Csat:** refer to clause 8.2.3. +- The reference point between services and SAM is: + - 1) **Reference point Csv:** This reference point is used to retrieve the driving states from SAM, and SAM can also obtain the vehicle data from VGP. +- The reference point between service functionalities and management is: + - 1) **Reference point Cmsf:** This reference point is used to send bidirectional manage messages between service functionalities and security/device management. The control messages should include keys/certifications/ciphers acquisition, encryption schemes acquisition and authentication/authorization for software deployment/update and application data storage/read. The control messages should also be used to retrieve the software running status of services. + +## **8.4 Management** + +### **8.4.1 Security management** + +#### **8.4.1.1 Description of security management** + +The security entity in the VGP includes access layer security management functions in OSI 1-4 layer and security management for services/applications in OSI 5-7 layer. + +#### **8.4.1.2 Access layer security management** + +The access layer security management covers the transport, networking and network access security. + +The access layer security management shall support functions that prevent non-authorized access or intrusion from external networks and devices. One or several firewall functions, e.g., stateful packet inspection filtering, MAC address filtering, IP address filtering, etc. should be used. + +The access layer security management shall support identity, crypto key and certificate management, e.g., identity add/delete/modification, crypto key create/update/storage, certificate create/update/storage/destroy, etc. A VGP shall guarantee the security of the process of management to avoid tampering and stealing. The security data is implemented in the process of MAC authentication, EAP-SIM (Extensible Authentication Protocol – Subscriber Identity Module) authentication, EAP-PEAP (Protected EAP) authentication and VPN (e.g., L2TP, GRE, IPSec), etc. + +#### **8.4.1.3 Security management for services/applications** + +The security management for services/applications cover the security functions in the OSI 5-7. + +The security management for services/applications shall support the registration, authentication and authorization functions for external applications' access. Security management for services/applications should support registration of service capabilities/user data that an application can use. An application can only use the service capabilities/user data that have been authorized. + +There is some private data about user behaviour which belongs to user privacy, such as location data, driving behaviour data, etc. Besides using encryption technology to protect critical data, a VGP should classify the data according to privacy policy which is managed in security management and allow that only authorized applications can use the private data. + +The security management for services/applications shall support identity, crypto key, digital signature and certificate management, e.g., add/delete/modify identity; create/update/store crypto key; create/update/store/delete certificate; etc. A VGP shall guarantee the security of the process of management to avoid tampering and stealing. A VGP should support the secure data/criteria exchange that is implemented in the process of session management; application data storage encryption and decryption; application access authentication; and VPN (e.g., TLS/SSLVPN). + +### **8.4.2 Wired and wireless access management** + +#### **8.4.2.1 Description** + +The wired and wireless access management entity supports management of multiple wired and wireless access network protocols and can make optimal use of all these resources to support handover between the same communication interface and different communication interfaces. + +#### **8.4.2.2 Component description** + +A VGP should track the status of the dynamically changing mobile network and provide access to the management information base (MIB) containing the configuration and current status information and be notified when the status of the medium changes. + +A VGP should provide functions to manage communication sessions according to the methods specified in the relevant wireless network standards. A VGP should also support mechanisms or strategies to establish, manage and disconnect networks based on user profiles. A strategy profile may be configured based on time, location, preferred communication channels (all accesses are transparent to applications), etc. in the hybrid network environment. + +The VG is in charge of supporting communication layers 1 to 4 and shall control the above listed functions through the Cmvvg reference point. + +### **8.4.3 Device management** + +#### **8.4.3.1 Description** + +The device management entity supports the management of hardware/software running and data communication status, hardware/software parameters configuration and fault management, etc. + +#### **8.4.3.2 Component description** + +A VGP should track the hardware/software running status/data communication status and generate records. A VGP should support the records uploaded to the cloud server through external networks and support the records local storage. + +A VGP should support configuring the MIB and hardware/software parameters remotely/locally. + +A VGP should support hardware/software fault diagnostics and disposal (e.g., restart, recovery). + +### **8.4.4 Reference points with other function entities** + +- The reference point between the VG and management is: + - 1) **Reference point Cmvvg**: refer to clause 8.1.4. +- The reference point between service functionalities and management is: + - 1) **Reference point Cmsf**: refer to clause 8.2.3. +- The reference point between services and management is: + - 1) **Reference point Cms**: refer to clause 8.3.3. + +# Appendix I + +## Signalling flows of VGP + +(This appendix does not form an integral part of this Recommendation.) + +NOTE – The dotted arrows are control messages and the solid arrows are media messages. + +## I.1 Signalling flows for emergency information display in V2V scenario + +![Sequence diagram showing signalling flows for emergency information display in a V2V scenario. The diagram includes lifelines for Vehicle A, VG, Session management, DVA service, In-vehicle resource access management, and DVI (with an Information display). The sequence of messages is: 1. Vehicle A to VG (solid arrow); 2. VG to Session management (dotted arrow); 3. Session management to DVA service (dotted arrow); 4. Session management to In-vehicle resource access management (dotted arrow); 5. In-vehicle resource access management to VG (dotted arrow); 6. VG to DVI (dotted arrow).](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +``` +sequenceDiagram + participant Vehicle A + participant VG + participant Session management + participant DVA service + participant In-vehicle resource access management + participant DVI + Note right of DVI: Information display + + Vehicle A->>VG: 1. Message + VG-->>Session management: 2. Control + Session management-->>DVA service: 3. Control + Session management-->>In-vehicle resource access management: 4. Control + In-vehicle resource access management-->>VG: 5. Control + VG-->>DVI: 6. Control +``` + +Sequence diagram showing signalling flows for emergency information display in a V2V scenario. The diagram includes lifelines for Vehicle A, VG, Session management, DVA service, In-vehicle resource access management, and DVI (with an Information display). The sequence of messages is: 1. Vehicle A to VG (solid arrow); 2. VG to Session management (dotted arrow); 3. Session management to DVA service (dotted arrow); 4. Session management to In-vehicle resource access management (dotted arrow); 5. In-vehicle resource access management to VG (dotted arrow); 6. VG to DVI (dotted arrow). + +H.550(17)\_FI.1 + +**Figure I.1 – Signalling flows for emergency information display in the V2V scenario** + +1. Vehicle A communicates with vehicle B at an intersection. Vehicle A sends a message to the VG. +2. The VG transfers the message to session management. +3. Session management transfers the message to the DVA service with high priority. The DVA service determines which DVI can be used to display the message according to the working status of each DVI. Then the DVA service changes the message format to adapt the DVI. +4. Session management transfers the message to the in-vehicle resource access management. In-vehicle resource access management determines whether the message can be transferred to the vehicle bus. +5. The in-vehicle resource access management transfers the message to the VG. +6. The VG sends the message to the vehicle bus, and the message can be displayed through the DVI. + +## I.2 Signalling flows for traffic data download in V2I scenario + +![Sequence diagram showing signalling flows for traffic data download in V2I scenario. Lifelines: Cloud server, RSU, VG, Session management, Software and application data management service, External application. The diagram shows 9 steps of interaction between these components.](0c08e48c08f96934cd6bc6911f3069dc_img.jpg) + +``` + +sequenceDiagram + participant External application + participant Session management + participant Software and application data management service + participant VG + participant RSU + participant Cloud server + + Note right of Software and application data management service: Storage data + + External application-->>Session management: 1 + Session management-->>VG: 2 + VG-->>RSU: 3 + RSU-->>Cloud server: 4 + Cloud server-->>RSU: 5 + RSU-->>VG: 6 + VG-->>Session management: 7 + Session management-->>Software and application data management service: 8 + Session management-->>External application: 9 + +``` + +Sequence diagram showing signalling flows for traffic data download in V2I scenario. Lifelines: Cloud server, RSU, VG, Session management, Software and application data management service, External application. The diagram shows 9 steps of interaction between these components. + +H.550(17)\_FI.2 + +**Figure I.2 – Signalling flows for traffic data download in the V2I scenario** + +1. An external application applies to download the latest traffic data from the cloud server. The external application initializes a request message to session management. +2. Session management transfers the message to the VG. +3. The VG selects the RSU to download the traffic data. +4. The RSU transfers the message to the cloud server. +5. The cloud server sends the traffic data back to the RSU. +6. The RSU transfers the traffic data to the VG. +7. The VG transfers the traffic data to session management. +8. Session management sends the traffic data to the software and application data management service. The software and application data management service unpacks and checks the traffic data, and then stores the data. +9. Session management sends the metadata of the traffic data to the external application. + +## I.3 Signalling flows of remote UI scenario + +![Sequence diagram illustrating the signalling flows of the remote UI scenario. The diagram shows interactions between a Nomadic device, VG, Session management, DVA service, External application, In-vehicle resource access management, and DVI (Touch screen display). The sequence of messages is: 1. Nomadic device to VG (dashed); 2. VG to Session management (dashed); 3. Session management to External application (dashed); 4. Session management to Nomadic device (dashed); 5. Nomadic device to VG (solid); 6. Session management to DVA service (solid); 7. Session management to In-vehicle resource access management (solid); 8. In-vehicle resource access management to DVI (solid).](043e64d41a3368d138ace3816fd26469_img.jpg) + +``` + +sequenceDiagram + participant ND as Nomadic device + subgraph VGP + participant VG + participant SM as Session management + participant DVA as DVA service + participant EA as External application + participant IRAM as In-vehicle resource access management + end + participant DVI as DVI (Touch screen display) + + ND-->>VG: 1. Request + VG-->>SM: 2. Request + SM-->>EA: 3. Request + SM-->>ND: 4. Response + ND->>VG: 5. Media stream + SM->>DVA: 6. Media stream + SM->>IRAM: 7. Media stream + IRAM->>DVI: 8. Display + +``` + +Sequence diagram illustrating the signalling flows of the remote UI scenario. The diagram shows interactions between a Nomadic device, VG, Session management, DVA service, External application, In-vehicle resource access management, and DVI (Touch screen display). The sequence of messages is: 1. Nomadic device to VG (dashed); 2. VG to Session management (dashed); 3. Session management to External application (dashed); 4. Session management to Nomadic device (dashed); 5. Nomadic device to VG (solid); 6. Session management to DVA service (solid); 7. Session management to In-vehicle resource access management (solid); 8. In-vehicle resource access management to DVI (solid). + +H.550(17)\_FI.3 + +**Figure I.3 – Signalling flows of the remote UI scenario** + +1. A nomadic device sends a request to the remote UI on the screens of the vehicle. The nomadic device connects to the VG and sends the request message. +2. The VG sends the request message to session management. +3. Session management transfers the message to the external application. The external application ensures that the remote UI request is technically feasible. The external application sends the remote UI parameters back to session management. +4. Session management sends the message back to the VG and the nomadic device. +5. The nomadic device sends a media stream to the VG and session management. +6. Session management transfer the media stream to the DVA service. The DVA service determines whether the media stream can be display on the screens according to the driving scene which is obtained from SAM and the running status of the screen. And the DVA service also can change the format and resolution of the media stream. +7. Session management transfers the media stream to in-vehicle resource access management. In-vehicle resource access management determines whether the media stream can be transferred to the vehicle bus. +8. The in-vehicle resource access management transfers the media stream and displays on the screens. + +## I.4 Signalling flows of emergency call scenario + +![Sequence diagram showing signalling flows of an emergency call scenario. The diagram includes lifelines for PSAP, VG, Session management, DVA service, External application, In-vehicle resource access management, DVI, and Vehicle bus. The sequence of messages is: 1. Airbag burst to VG; 2. VG to In-vehicle resource access management; 3. In-vehicle resource access management to Session management; 4. Session management to External application; 5. External application to Session management; 6. Session management to VG; 7. VG to PSAP.](d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg) + +``` +sequenceDiagram + participant PSAP + participant VG + participant SM as Session management + participant DVA as DVA service + participant EA as External application + participant IRAM as In-vehicle resource access management + participant DVI + participant VB as Vehicle bus + + Note right of VB: Airbag burst + VB-->>VG: 1 + VG-->>IRAM: 2 + IRAM-->>SM: 3 + SM-->>EA: 4 + EA-->>SM: 5 + SM-->>VG: 6 + VG-->>PSAP: 7 +``` + +H.550(17)\_F1.4 + +Sequence diagram showing signalling flows of an emergency call scenario. The diagram includes lifelines for PSAP, VG, Session management, DVA service, External application, In-vehicle resource access management, DVI, and Vehicle bus. The sequence of messages is: 1. Airbag burst to VG; 2. VG to In-vehicle resource access management; 3. In-vehicle resource access management to Session management; 4. Session management to External application; 5. External application to Session management; 6. Session management to VG; 7. VG to PSAP. + +**Figure I.4 – Signalling flows of the emergency call scenario** + +1. When an accident happens the airbag bursts. The vehicle bus sends a message to the VG. +2. The VG transfers the message to the in-vehicle resource access management. +3. The in-vehicle resource access management sends the message to session management. +4. Session management transfers the message to an external application with high priority. +5. The external application obtains the global positioning system (GPS) information and vehicle information, and sends the information to session management. +6. Session management sends the message to the VG. +7. The VG cuts off the existing call and establishes a call to the public service answering point (PSAP) with GPS/vehicle information. + +## I.5 Signalling flows of anti-stolen scenario + +![Sequence diagram showing signalling flows for an anti-stolen scenario. Lifelines: Cloud server, VG, Session management, External service, In-vehicle resource access management, and Vehicle bus. The diagram shows 11 numbered messages between these components, leading to the final action 'Cut the engine'.](2bacc162a73d75c43a7f90715832bd13_img.jpg) + +``` + +sequenceDiagram + participant Cloud server + participant VG + participant Session management + participant External service + participant In-vehicle resource access management + participant Vehicle bus + + Note right of Vehicle bus: Cut the engine + Cloud server->>VG: 1 + VG->>Session management: 2 + Session management->>External service: 3 + External service-->>Session management: 4 + External service-->>VG: 4 + VG-->>Cloud server: 5 + Cloud server->>VG: 6 + VG->>Session management: 7 + VG->>External service: 7 + External service-->>Session management: 8 + Session management->>In-vehicle resource access management: 9 + In-vehicle resource access management-->>VG: 10 + VG-->>Vehicle bus: 11 + +``` + +Sequence diagram showing signalling flows for an anti-stolen scenario. Lifelines: Cloud server, VG, Session management, External service, In-vehicle resource access management, and Vehicle bus. The diagram shows 11 numbered messages between these components, leading to the final action 'Cut the engine'. + +**Figure I.5 – Signalling flows of the anti-stolen scenario** + +1. After the vehicle has been stolen, the driver owner calls the telematics server and asks for tracking. The cloud server sends the request message to the VG. +2. The VG transfers the message to session management. +3. Session management transfers the message to an external service. The external service obtains the GPS information of the vehicle. +4. The external service sends the response message to session management and the VG. +5. The VG transfers the message to the cloud server. +6. When the speed of the vehicle turns to 0 km/h, the cloud server sends a message to cut the engine. +7. The VG sends the message to session management and the external service. +8. The external service transfers the message to session management. +9. Session management transfers the message to the in-vehicle resource access management. +10. The in-vehicle resource access management transfers the message to the VG. +11. The VG transfers the message to the vehicle bus and the vehicle cuts the engine. + +## I.6 Signalling flows of remote software update scenario + +![Sequence diagram showing the signalling flows of a remote software update scenario. The diagram includes lifelines for Cloud server, VG, Session management, and Software and application data management service. The VG, Session management, and Software and application data management service are grouped under the heading 'VGP'. The sequence of messages is: 1. Cloud server to VG (dashed arrow); 2. VG to Session management (dashed arrow); 3. Session management to Software and application data management service (dashed arrow); 4. Software and application data management service to VG (dashed arrow); 5. Cloud server to VG (solid arrow); 6. VG to Session management (solid arrow); 7. Session management to Software and application data management service (solid arrow). A dashed box labeled 'Software update' is shown at the bottom right of the Software and application data management service lifeline. The text 'H.550(17)_Fl.6' is at the bottom right of the diagram area.](5414f65867392f05ba0063b208eeb5e1_img.jpg) + +``` +sequenceDiagram + participant Cloud server + participant VG + participant Session management + participant Software and application data management service + Note right of Software and application data management service: VGP + + Cloud server-->>VG: 1 + VG-->>Session management: 2 + Session management-->>Software and application data management service: 3 + Software and application data management service-->>VG: 4 + Cloud server->>VG: 5 + VG->>Session management: 6 + Session management->>Software and application data management service: 7 + Note right of Software and application data management service: Software update +``` + +Sequence diagram showing the signalling flows of a remote software update scenario. The diagram includes lifelines for Cloud server, VG, Session management, and Software and application data management service. The VG, Session management, and Software and application data management service are grouped under the heading 'VGP'. The sequence of messages is: 1. Cloud server to VG (dashed arrow); 2. VG to Session management (dashed arrow); 3. Session management to Software and application data management service (dashed arrow); 4. Software and application data management service to VG (dashed arrow); 5. Cloud server to VG (solid arrow); 6. VG to Session management (solid arrow); 7. Session management to Software and application data management service (solid arrow). A dashed box labeled 'Software update' is shown at the bottom right of the Software and application data management service lifeline. The text 'H.550(17)\_Fl.6' is at the bottom right of the diagram area. + +**Figure I.6 – Signalling flows of the remote software update scenario** + +1. After a new software version is published, the cloud server sends a software update request message to the VG. +2. The VG transfers the message to session management. +3. Session management transfers the message to the software and application data management service. The software and application data management service checks the software version and authenticates the server. +4. The software and application data management service sends the response message to the cloud server. +5. The cloud server sends the software data to the VG. +6. The VG transfers the software data to session management. +7. The session management sends the software data to the software and application data management service. The software and application data management service checks/decrypts the data and deploys the new version software in the VGP or sends the data to the vehicle bus through the in-vehicle resource access management. + +## I.7 Signalling flows of navigation scenario + +![Sequence diagram showing signalling flows for a navigation scenario. Lifelines: Cloud server, VG, Session management, Session management, In-vehicle resource access management, DVI. The diagram shows 8 steps of interaction between these components. A dashed box labeled 'Input POI' is shown next to the DVI lifeline.](5d3455c6c2a37cb3aff761fedeb8644e_img.jpg) + +``` +sequenceDiagram + participant DVI + participant VM as In-vehicle resource access management + participant SM1 as Session management + participant SM2 as Session management + participant VG + participant CS as Cloud server + + Note right of DVI: Input POI + DVI->>VM: 1. POI + VM->>SM1: 2. POI + SM1->>SM2: 3. Request + SM2->>SM1: 4. Response + SM1->>VG: 5. Message + VG->>CS: 6. Request + CS->>VG: 7. Response + VG->>SM2: 8. Message +``` + +Sequence diagram showing signalling flows for a navigation scenario. Lifelines: Cloud server, VG, Session management, Session management, In-vehicle resource access management, DVI. The diagram shows 8 steps of interaction between these components. A dashed box labeled 'Input POI' is shown next to the DVI lifeline. + +H.550(17)\_FI.7 + +**Figure I.7 – Signalling flows of the navigation scenario** + +1. The driver inputs the point of interest (POI) through the DVI. The DVI sends the POI to the in-vehicle resource access management through the VG. +2. The in-vehicle resource access management transfers the POI to session management. +3. Session management transfers the POI to an external service. If the external service cannot find the POI information in the local database, it should search the POI from the cloud server. +4. The external service sends the request message to session management. +5. Session management sends the message to the VG. +6. The VG sends the message to the cloud server. The cloud server searches the POI in the remote database. +7. The cloud server sends the POI to the VG. +8. The VG sends the message to session management/external service. + +# Bibliography + +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*. +- [b-ITU-R handbook] ITU-R Handbook (2006), Land Mobile (including wireless access) – Volume 4: *Intelligent Transport Systems*. +- [b-IEEE 802.11] IEEE 802.11-2016, *IEEE Standard for Information technology – Telecommunications and information exchange between systems Local and metropolitan area networks – Specific requirements – Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications*. +<> +- [b-ISO/IEC 7498-1] ISO/IEC 7498-1 (1994), *Information technology – Open Systems Interconnection – Basic Reference Model: The Basic Model*. +- [b-ISO 11898-1] ISO 11898-1:2015, *Road vehicles – Controller area network (CAN) – Part 1: Data link layer and physical signalling*. +<> +- [b-ISO 15638-16] ISO 15638-16:2014, *Intelligent transport systems – Framework for cooperative telematics applications for regulated vehicles (TARV) – Part 16: Vehicle speed monitoring*. +- [b-ISO 17458-1] ISO 17458-1:2013, *Road vehicles – FlexRay communications system – Part 1: General information and use case definition*. +<> +- [b-ISO 21210] ISO 21210:2012, *Intelligent Transport Systems (ITS) – Communications access for land mobiles (CALM) – IPv6 Networking*. +- [b-ISO 21212] ISO 21212:2008, *Intelligent Transport Systems (ITS) – Communications access for land mobiles (CALM) – 2G Cellular systems*. +- [b-ISO 21213] ISO 21213:2008, *Intelligent Transport Systems (ITS) – Communications access for land mobiles (CALM) – 3G Cellular systems*. +- [b-ISO 21214] ISO 21214:2006, *Intelligent Transport Systems (ITS) – Communications access for land mobiles (CALM) – Infra- red systems*. +- [b-ISO 21216] ISO 21216: 2012, *Intelligent Transport Systems (ITS) – Communication access for land mobiles (CALM) – Millimetre wave air interface* +<> +- [b-ISO 24102-1] ISO 24102-1:2013, *Intelligent transport systems (ITS) – Communications access for land mobiles (CALM) – ITS station management – Part 1: Local management*. +<> +- [b-ISO 29281] ISO 29281:2011, *Intelligent Transport Systems (ITS) – Communications access for land mobiles (CALM) – Non-IP networking*. +- [b-MOST] MOST (2010), *Media Oriented Systems Transport*. +<> + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.551-202201-I_PDF-E/raw.md b/marked/H/T-REC-H.551-202201-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1c510c396286d9d18c355ff78ce3777d97f43e0a --- /dev/null +++ b/marked/H/T-REC-H.551-202201-I_PDF-E/raw.md @@ -0,0 +1,993 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.551** + +(01/2022) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Vehicular gateways and intelligent transportation systems +(ITS) – Architecture for vehicular gateways + +--- + +**Architecture of vehicular multimedia systems** + +Recommendation ITU-T H.551 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a white grid pattern, overlaid by a stylized 'ITU' text in blue. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Content delivery and ubiquitous sensor network applications | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.551 + +# Architecture of vehicular multimedia systems + +## Summary + +Recommendation ITU-T H.551 defines the configuration for vehicle multimedia systems (VMSs), the reference model of VMS architecture, and the reference solution for VMS multimedia applications. VMS security issues and personally identifiable information protection and privacy issues are also described. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.551 | 2022-01-28 | 16 | 11.1002/1000/14811 | + +## Keywords + +Architecture, vehicle multimedia systems. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2022 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|---------|-------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 1 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Background..... | 4 | +| 7 | VMS features and configurations ..... | 4 | +| 7.1 | VMS features..... | 4 | +| 7.2 | VMS configurations ..... | 4 | +| 7.3 | List of VMS features ..... | 5 | +| 8 | VMS architecture..... | 7 | +| 8.1 | VMS functions..... | 7 | +| 8.2 | Deciding factors of VMS architecture..... | 7 | +| 8.3 | Reference model of VMS architecture ..... | 8 | +| 9 | VMS multimedia applications ..... | 9 | +| 9.1 | VMSP reference model ..... | 10 | +| 9.2 | Reference protocol stack for convergence transmission ..... | 11 | +| 9.3 | Reference receiver model ..... | 12 | +| 10 | VMS security ..... | 14 | +| 11 | Personally identifiable information (PII) protection and privacy..... | 14 | +| Annex A | – VMS security..... | 15 | +| A.1 | Overview ..... | 15 | +| A.2 | Assumed threats to VMS and its ecosystem..... | 15 | +| A.3 | Security capabilities based on identified threats ..... | 17 | +| Annex B | – Personally identifiable information (PII) protection and privacy..... | 21 | +| B.1 | Information sources ..... | 21 | +| B.2 | Implementation of PII protection: General considerations ..... | 21 | +| B.3 | Data visibility and transparency ..... | 22 | +| B.4 | Data accuracy and data integrity ..... | 22 | +| B.5 | Confidentiality ..... | 23 | +| B.6 | Data anonymization..... | 23 | +| B.7 | Data availability..... | 24 | +| | Bibliography..... | 25 | + + + +# Recommendation ITU-T H.551 + +## Architecture of vehicular multimedia systems + +# 1 Scope + +This Recommendation defines the features and configurations of vehicle multimedia systems (VMSs) and the reference model of VMS architecture. The reference model of vehicular multimedia service platform, the reference protocol stack for convergence transmission, and the reference receiver model of in-vehicle devices for VMS multimedia applications are also defined. VMS security issues and personally identifiable information protection and privacy issues are described as well. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T F.749.3] Recommendation ITU-T F.749.3 (2020), *Use cases and requirements for vehicular multimedia networks*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 vehicular multimedia networks (VMN)** [ITU-T F.749.3]: The VMN consist of the vehicular multimedia service platform (VMSP), broadcast and communication networks, and the vehicle multimedia system (VMS) in the vehicle. + +**3.1.2 vehicular multimedia service platform (VMSP)** [ITU-T F.749.3]: The VMSP is a platform in the cloud that enables the multimedia service for end-user(s) in the vehicle. + +**3.1.3 vehicle multimedia system (VMS)** [ITU-T F.749.3]: The VMS consists of vehicle multimedia system inputs (VM I/P), vehicle multimedia unit (VMU) and vehicle multimedia system outputs (VM O/P). + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 VMS core function:** A function that deals with the physical, functional and logical data of VMS. + +**3.2.2 VMS associated function:** A function that only receives and displays functional and logical data from other systems or sub-systems. + +**3.2.3 VMS shared function:** A function that is used by other systems or sub-systems to share the physical, functional and logical data and control information. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|---------------------------------------------| +| ADAS | Advanced Driver Assistance System | +| AM | Amplitude Modulation | +| ANC | Active Noise Cancellation | +| APP | Application | +| AR | Augmented Reality | +| AVM | Around View Monitoring | +| bCall | Breakdown Call | +| BGS | Background Scan | +| CA | Conditional Access | +| CDN | Content Distribution Network | +| CDR | Convergent Digital Radio | +| DAB | Digital Audio Broadcasting | +| DASH | Dynamic Adaptive Streaming over HTTP | +| DMS | Driver Monitoring System | +| DNT | Do Not Track | +| DRM | Digital Rights Management | +| DTTB | Digital Terrestrial Television Broadcasting | +| eCall | Emergency Call | +| ECM | Entitlement Control Message | +| ECU | Electronic Control Unit | +| EMM | Entitlement Management Message | +| FM | Frequency Modulation | +| GDPR | General Data Protection Regulation | +| HEO | High Earth Orbit | +| HLS | HTTP Live Streaming | +| HMI | Human Machine Interface | +| HTTP | Hypertext Transfer Protocol | +| HVAC | Heating, Ventilation and Air Conditioning | +| IAM | Identity and Access Management | +| IBOC | In-Band On-Channel | +| iCall | Information Call | +| IP | Internet Protocol | +| LCD | Liquid Crystal Display | +| LED | Light Emitting Diode | +| LEO | Low Earth Orbit | + +| | | +|--------|---------------------------------------| +| MR | Mixed Reality | +| NAT | Network Address Translation | +| OBD | On-Board Diagnostics | +| OEM | Original Equipment Manufacturer | +| OLED | Organic Light Emitting Diode | +| OS | Operating System | +| OTA | Over The Air | +| PD | Phase Diversity | +| PII | Personally Identifiable Information | +| PUF | Physical Unclonable Function | +| RDS | Radio Data System | +| RF | Radio Frequency | +| RVC | Rear View Camera | +| TCP | Transfer Control Protocol | +| TMC | Traffic Message Channel | +| UDP | User Datagram Protocol | +| V2I | Vehicle-to-Infrastructure | +| V2P | Vehicle-to-Person | +| V2V | Vehicle-to-Vehicle | +| V2X | Vehicle-to-Everything | +| VM | Vehicular Multimedia | +| VM I/P | Vehicle Multimedia System Inputs | +| VM O/P | Vehicle Multimedia System Outputs | +| VMN | Vehicular Multimedia Network | +| VMSP | Vehicular Multimedia Service Platform | +| VMS | Vehicle Multimedia System | +| VMU | Vehicle Multimedia Unit | +| VR | Virtual Reality | + +## 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is prohibited from" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +- The keywords "is not recommended" indicate a requirement which is not recommended but which is not specifically prohibited. Thus, conformance with this Recommendation can still be claimed even if this requirement is present. + +# 6 Background + +In this Recommendation, the features and configurations of vehicle multimedia systems (VMSs) and the reference model of VMS architecture are defined in compliance with the requirements in [ITU-T F.749.3]. The reference model of vehicular multimedia service platform (VMSP), the reference protocol stack for convergence transmission, and the reference receiver model of in-vehicle devices for VMS multimedia applications are also defined. VMS security issues, personally identifiable information (PII) protection and privacy issues are defined as well. + +The Recommendation is organized as follows: + +Clause 7 defines the features and configurations of VMS. Clause 8 defines the reference model of VMS architecture. Clause 9 defines the reference model of VMSP, the reference protocol stack for convergence transmission of multimedia contents over heterogeneous networks, and the reference receiver model of in-vehicle devices. Clause 10 addresses VMS security issues. Clause 11 addresses PII protection and privacy issues. + +# 7 VMS features and configurations + +## 7.1 VMS features + +VMS features are determined based on the following principles: + +- User experience, entertainment and information features and applications for the driver and the passenger. +- Market, regional and country specific requirements. +- Legal and mandatory requirements. + +However, VMS features do not describe the overall network architecture of vehicles or the integration of multiple domains in vehicles. + +## 7.2 VMS configurations + +VMS configurations are based on the following principles: + +- VMS configurations define standalone requirements for entertainment and information display to driver and passenger. +- VMS configurations are recommended to be defined at the level of features and functions. +- VMS configurations are recommended to include hardware components within the VMS. +- Multiple VMS configurations are possible. +- VMS configurations are recommended to be highly variable. Both OEM-built and after-market plug-in VMS products are recommended to be considered. + +However, VMS configurations do not describe the overall network architecture of vehicles or the integration of multiple domains in the vehicle. + +#### 7.2.1 Deciding factors + +VMS configurations are determined based on the following deciding factors: + +- Usage requirements. +- Features, functional requirements. +- Interface requirements. + +- Cost requirements. +- Benchmarked requirements. + +### 7.3 List of VMS features + +The reference VMS features are summarized in Table 1. + +**Table 1 – Reference VMS features** + +| Features | Sub-features | Configurable | +|-------------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Human machine interface (HMI) | Display technology | Light emitting diode (LED)/liquid crystal display (LCD)/organic light emitting diode (OLED), etc. | +| | Number of displays | Multiple (front, central, rear, etc.) | +| | Control | Traditional controls: Button / knobs / touch controls, etc. | +| | | Intelligent controls: Voice control, face recognition, voice biometric, gesture, personalization, eye movement control, tactile-flexible feedback touch, etc. | +| | Multi-screen interaction | Push information to different screens | +| | | Video file synchronous or asynchronous display | +| | | Dual navigation display | +| | | Free matching of the display interface | +| | System language | User interface: Different language requirements as mandated by regulations | +| | Display for camera | Rear view camera (RVC) / Around view monitoring (AVM) | +| Broadcast | Terrestrial | Analogue: Amplitude modulation (AM) broadcasting, frequency modulation (FM) broadcasting, FM broadcasting with dual tuner and phase diversity (PD), FM broadcasting with background scan (BGS), Radio data system (RDS), etc. | +| | | Digital: Digital audio broadcasting (DAB), digital terrestrial television broadcasting (DTTB), in-band on-channel (IBOC) technologies, convergent digital radio (CDR), etc. | +| | Satellite | Satellite audio/video services (e.g., satellite audio/video streaming service) | +| External Network Connectivity | Cellular networks | 3G/4G/5G | +| | Satellites bi-directional | Low earth orbit (LEO) satellite bi-directional communication networks | +| | | High earth orbit (HEO) satellite bi-directional communication networks | +| | Vehicle-to-everything (V2X) | Vehicle-to-vehicle (V2V), Vehicle-to-infrastructure (V2I), Vehicle-to-person (V2P) | +| | Wireless local area networks | IEEE 802.11 hotspots | +| | | Hands-free calls and music playing using personal area networks | + +**Table 1 – Reference VMS features** + +| Features | Sub-features | Configurable | +|--------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------| +| In-vehicle Mobile Connectivity | | Web surfing using IEEE 802.11 local area networks | +| | | Screen sharing using short distance communication networks | +| | | Third-party vehicle interface applications | +| Telematics Configurations | Remote | Remote monitoring, control, vehicle data transfer | +| | Calls | Emergency call (eCall), breakdown call (bCall), information call (iCall) | +| Online APP Stores/Suites | APP store | New features downloaded | +| | Theme marketplace | Theme skin replacement | +| Over-the-air (OTA) update | | OTA software | +| Media | Audio | Normal and high fidelity | +| | Image | In different formats | +| | Video | Normal video with various resolutions, augmented reality (AR), virtual reality (VR), mixed reality (MR) | +| Navigation | Local navigation | | +| | Cloud navigation | Data from telematics box (3G/4G/5G) modem / user mobile data | +| | Real-time traffic | Traffic message channel (TMC), Transport Protocol Experts Group (TPEG), real time traffic centre, etc. | +| | Services | Navigation services, real-time weather forecasting services, etc. | +| | Advanced features | Intelligent travel applications such as calendar, planners, etc. | +| Voice Recognition (VR) and Synthesis | Local VR, cloud VR and synthesis | Natural language understanding | +| | | Auto speech recognition | +| | | Text to speech | +| Audio | Audio quality | Volume adjustment of the speed function | +| | | Sound algorithms | +| | | Active noise cancellation (ANC) | +| | | Personalization settings (sound patterns and facial recognition) | +| | | Best listening position adjustment | +| | | Sound quality reduction technology | +| | Amplifier configurations | Multiple channels integrated amplifiers | +| | | Amplifiers with speakers | +| | Sound configuration | Multiple speaker configurations tweeter (treble speaker) / woofer (bass speaker) / full range speakers | +| Security | | Identity and access management, authentication, authorization and transaction audit | +| | | Network security | +| | | Operational security | + +**Table 1 – Reference VMS features** + +| Features | Sub-features | Configurable | +|----------------------|--------------------------------|--------------------------------------------------------------------------------------------------------------------| +| | | Application security | +| | | Software OTA security | +| | | Hardware security | +| | | Cryptography security | +| Privacy | | General data protection considerations | +| | | Personal information protection | +| | | Data visibility protection | +| | | Confidentiality, integrity and availability | +| Intelligent features | Driver monitoring system (DMS) | Fatigue, expression and emotion recognition | +| | Health | Heartbeat monitor, blood pressure monitor | +| | Office environment | Email, video conference calls, holographic projection, gesture recognition, eye movement control, handwritten memo | +| | Games | Voice based interactive quiz games, holographic interacting games, adventure games | +| | Social | Social applications in vehicle | + +NOTE – Security and privacy features are essential to VMs with configurations M1 to M5, but are configurable to VM with configuration M0. Examples of VMs with configuration M0 to M5 are given in Appendix I of [ITU-T F.749.3]. + +# 8 VMS architecture + +This clause defines the classification of VM functions, the deciding factors and the reference model of the VM architecture. + +## 8.1 VM functions + +In general, VM functions can be classified into three categories, namely, VM core functions, VM associated functions and VM shared functions. + +VM core functions are VM functions that deal with the physical, functional and logical data of VM. Examples of VM core functions include tuner, media processing, display functions, etc. + +VM associated functions are VM functions that only receive and display functional and logical data from other systems or sub-systems. Examples of VM associated functions include camera feed from rear vehicle camera, eCall information display initiated by an accident, etc. + +VM shared functions are VM functions that are used by other systems or sub-systems to share the physical, functional and logical data and control information. Examples of VM shared functions include HVAC controls through the vehicle multimedia unit (VMU), etc. + +## 8.2 Deciding factors of VM architecture + +The following are deciding factors of the VM architecture: + +- Technical requirements +- Operating system, memory and hardware requirements +- Features, functional, sub-systems, logical and physical requirements + +- Interface requirements +- Cost requirements +- Usage requirements +- Benchmarked requirements +- Standard compliance requirement + +## 8.3 Reference model of VMS architecture + +The VMS architecture is defined at the interface, the sub-systems and the systems levels. A reference model of VMS architecture is given in Figure 1. + +![Figure 1 – Reference model of VMS architecture. The diagram shows the VMS architecture layers and their interfaces. The VMU (Vehicle Management Unit) is the central component, containing layers for Information, Multimedia, Vehicle control, and Telematics applications, an Application framework, an OS framework, five OS instances (OS1-OS5), a Hypervisor/virtualization layer, a Device drivers and peripherals layer, and a Hardware layer. A Security layer is shown on the right side of the VMU. VM Input includes Camera (Video), Microphone (Audio), Hard keys/touch/VR (Control), Audio/video devices (Audio/video), Broadcast satellite reception antenna (Radiofrequency), Cellular communication reception antenna (Radiofrequency), LEO satellite reception antenna (Radiofrequency), and Short-range communication reception antenna (Radiofrequency). VM Output includes Multiple displays for information, multimedia and controls for VMS, ADAS, HVAC (Video), Speaker (Audio), Cellular communication transmission antenna (Radiofrequency), LEO satellite transmission antenna (Radiofrequency), and Short-range communication transmission antenna (Radiofrequency). External connections include Nomadic devices (Phones, Pads, etc.) connected to Zonal gateway 1, which is connected to the Vehicle central gateway. The Vehicle central gateway is connected to Zonal gateway 2 and an Intra-vehicle network, which is connected to Cloud data.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 1 – Reference model of VMS architecture. The diagram shows the VMS architecture layers and their interfaces. The VMU (Vehicle Management Unit) is the central component, containing layers for Information, Multimedia, Vehicle control, and Telematics applications, an Application framework, an OS framework, five OS instances (OS1-OS5), a Hypervisor/virtualization layer, a Device drivers and peripherals layer, and a Hardware layer. A Security layer is shown on the right side of the VMU. VM Input includes Camera (Video), Microphone (Audio), Hard keys/touch/VR (Control), Audio/video devices (Audio/video), Broadcast satellite reception antenna (Radiofrequency), Cellular communication reception antenna (Radiofrequency), LEO satellite reception antenna (Radiofrequency), and Short-range communication reception antenna (Radiofrequency). VM Output includes Multiple displays for information, multimedia and controls for VMS, ADAS, HVAC (Video), Speaker (Audio), Cellular communication transmission antenna (Radiofrequency), LEO satellite transmission antenna (Radiofrequency), and Short-range communication transmission antenna (Radiofrequency). External connections include Nomadic devices (Phones, Pads, etc.) connected to Zonal gateway 1, which is connected to the Vehicle central gateway. The Vehicle central gateway is connected to Zonal gateway 2 and an Intra-vehicle network, which is connected to Cloud data. + +H.551(22) + +Figure 1 – Reference model of VMS architecture + +#### 8.3.1 Applications + +Applications of VMS include: + +- Information applications, e.g., instrument cluster, head up displays, navigation and weather. +- Multimedia applications, e.g., media, navigation, VR and HMI. +- Vehicle control applications, e.g., HVAC and connected cars. +- Telematics applications, e.g., remote control, diagnostics, and data access. +- Display applications, e.g., front and rear display applications. + +#### 8.3.2 Application framework + +VMS features and functions are accessed via user interface tools designed according to an application framework. + +#### 8.3.3 Operating system (OS) framework + +The OS framework handles system services. It could be a proprietary framework of OEMs and VMS developers. + +#### 8.3.4 OS + +Various embedded operating systems (OSs) and kernels are used depending on processing load, speed and accuracy requirements. + +#### 8.3.5 Hypervisor and virtualization + +Hypervisor and virtualization techniques are used to support multiple OSs and processing tasks by a single high-power processor through computing resource sharing. + +#### 8.3.6 Device drivers and peripherals + +Device drivers include vehicle network interface driver, audio and video drivers, display drivers, inter-processors protocol drivers and intra-processor protocol drivers. + +#### 8.3.7 Hardware + +Hardware includes processors, memory and other components. + +#### 8.3.8 Cloud data + +Cloud data includes: + +- Data for multimedia services +- Data for telematics services, i.e., remote diagnostics services, software OTA update services, bCall / iCall services and navigation services. + +## 9 VMS multimedia applications + +Figure 2 depicts a system for VMS multimedia applications, which consists of vehicular multimedia service platform (VMSP) in the cloud, heterogeneous networks and in-vehicle devices. A convergence transmission scheme is used to improve the transmission efficiency of multimedia contents over heterogeneous networks, i.e., satellite broadcasting networks and mobile communication networks. This clause describes the VMSP reference model (clause 9.1), the reference protocol stack for convergence transmission of multimedia contents over heterogeneous networks (clause 9.2), and the reference receiver model of in-vehicle devices (clause 9.3). + +![Figure 2 – A system diagram for VMS multimedia applications. The diagram shows a cloud-based VMSP connected to a convergence gateway, which is linked to a CDN and a broadcasting network. The VMSP is also connected to a mobile communication network. The broadcasting network is connected to a vehicle's OBD telematic control unit and other telematic devices. The mobile communication network is connected to the vehicle's multimedia system and nomadic devices. The vehicle's multimedia system is connected to the OBD telematic control unit and other telematic devices. The nomadic devices are connected to the vehicle's multimedia system.](220869911a1ecfa1dd4aa6d750319aad_img.jpg) + +The diagram illustrates the system architecture for VMS multimedia applications. On the left, the 'Vehicular multimedia service platform' (VMSP) is shown in the cloud, connected to a 'Convergence gateway'. The gateway is linked to a 'CDN' (Content Delivery Network) and a 'Broadcasting network' (represented by a satellite and tower). The VMSP is also connected to an 'Internet' cloud and a 'Mobile communication network' (represented by a satellite and tower). The 'Broadcasting network' is connected to a vehicle's 'OBD telematic control unit' and 'Other telematic devices'. The 'Mobile communication network' is connected to the vehicle's 'Vehicle multimedia system' and 'Multimedia applications'. The 'Vehicle multimedia system' is connected to the 'OBD telematic control unit' and 'Other telematic devices'. The 'Nomadic devices' (represented by a smartphone and tablet) are connected to the 'Vehicle multimedia system'. The vehicle itself is shown on the right side of the diagram. + +Figure 2 – A system diagram for VMS multimedia applications. The diagram shows a cloud-based VMSP connected to a convergence gateway, which is linked to a CDN and a broadcasting network. The VMSP is also connected to a mobile communication network. The broadcasting network is connected to a vehicle's OBD telematic control unit and other telematic devices. The mobile communication network is connected to the vehicle's multimedia system and nomadic devices. The vehicle's multimedia system is connected to the OBD telematic control unit and other telematic devices. The nomadic devices are connected to the vehicle's multimedia system. + +H.551(22) + +Figure 2 – A system diagram for VMS multimedia applications + +## 9.1 VMSP reference model + +The VMSP consists of content server, licence server (optional) and conditional access (CA) server (optional). Its reference model is illustrated in Figure 3. + +![Figure 3 – Reference model of VMSP. The diagram shows three main server components: Content server, Licence server, and Conditional access server, all connected to a central 'Convergence transmission over vehicle multimedia networks'.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +The diagram illustrates the reference model of VMSP. It consists of three main server components and a central transmission network: + +- Content server:** Contains a **Content repository** (store of clear content) and a **DRM packager**. The DRM packager includes **Encryption** and **Segmenter** blocks. It outputs an **Encrypted stream** to the Conditional access server. +- Licence server:** Contains **Encryption keys**, **Identities**, and **Rights** (each represented by a cylinder icon). These feed into a **DRM Licence management** block. It outputs a **Licence** to the Conditional access server. +- Conditional access server:** Contains a **Scrambler** and an **Entitlement server**. The Scrambler receives the **Encrypted stream** and **Control words** (from a cylinder icon) and outputs a **Scrambled stream**. The Entitlement server contains **ECM Gen.** and **EMM Gen.** blocks, which receive **Secret keys** (from a cylinder icon) and the **Licence** from the Licence server. It outputs **ECM** and **EMM** messages. +- Convergence transmission over vehicle multimedia networks:** A dashed box at the bottom that receives the **Scrambled stream**, **ECM**, **EMM**, and **Licence** from the Conditional access server. + +H.551(22) + +Figure 3 – Reference model of VMSP. The diagram shows three main server components: Content server, Licence server, and Conditional access server, all connected to a central 'Convergence transmission over vehicle multimedia networks'. + +**Figure 3 – Reference model of VMSP** + +The content server consists of the content repository and the digital rights management (DRM) packager. The content repository is used to store the clear contents that the content provider (CP) wants to distribute. Note that the content repository is often built into the DRM solution or is sometimes integrated into a content management system that interfaces to the DRM server. The DRM packager encrypts and packages the multimedia contents for streaming over VMN. The licence server is used to manage the creation, modification, and revocation of the DRM licences. The DRM licence contains identities, rights specification and encryption keys. Usually, DRM clients could acquire their DRM licences from the licence server by using mobile communication network connections. The candidate packaging schemes for streaming in VMN include MPEG-DASH [b-ISO/IEC 23009-1] and HLS [b-IETF RFC 8216]. + +The conditional access (CA) server consists of scrambler and entitlement server. The scrambler is used to scramble the inbound streams using control words. The entitlement server is used to generate the entitlement control message (ECM) and the entitlement management message (EMM). Usually, the outbound scrambled streams, ECMs and EMMs are delivered over satellite broadcast networks. However, there are the following two exceptions: + +- 1) When a user drives to a place with no cell phone coverage, DRM licences cannot be acquired through any mobile communication network. In this case, DRM licences could be integrated into EMMs and be delivered to the user over satellite networks. Thus, service continuity could be achieved. + +- 2) When a service operator starts its business, thousands of new customers may try to activate their devices in a short period of time. However, the bandwidth required for the delivery of EMMs for those devices may not be available in satellite broadcast networks. In such a case, EMMs could be temporally offloaded from satellite broadcast networks to mobile communication networks. Thus, a successful business launch could be guaranteed. + +## 9.2 Reference protocol stack for convergence transmission + +Broadcast is generally regarded as the most cost-effective way to deliver linear programs to a large population over vast geographic areas. Despite the success of Ka- and Ku-band fixed DTV broadcast around the world, service provision via broadcast to vehicles has turned out to be challenging. For example, in an urban environment, the reliability of broadcast communications is rather problematic due to moving receivers and frequent signal blockage by high buildings. Although the broadcast urban coverage issue can be addressed by ground repeater networks that fill up the outage gaps, building the gap-filler infrastructure is both expensive and highly time consuming. Another limitation of broadcast communication is that it can only provide one-way services, thus unable to accommodate personalized services or support user interactions. + +To deal with these challenges, a convergence transmission scheme is proposed for multimedia contents transmission over VMN, where most media contents are delivered to massive users via broadcast networks, and mobile communication networks are used only to recover packets that have been dropped by the broadcast networks. The scrambled streams from the VMSP are sent to the convergence gateways, where the media segments are further packetized into sequenced packets and broadcast to all users over the satellite network. At the terminal, the missing or erroneous packets of broadcast streams can be easily detected. These dropped packets are recovered by retransmission over the mobile communication network. Once the media streams are seamlessly re-assembled, the terminal can not only play these media streams at the cockpit displays and speakers, but also serve as a local infotainment centre to Wi-Fi-share these media streams with all passengers using their personal devices such as smart phones and tablets. The convergence transmission scheme is illustrated in Figure 4. + +![Figure 4: The processing of convergence transmission. The diagram illustrates the flow of data segments and packets through a transmitting system and a receiving terminal. On the left, a vertical bar labeled 'Segment' shows packets 1 through 5 being processed. These are then distributed into two parallel paths: a 'Sending queue for broadcast networks' containing packets 4, 3, 2, and 1; and a 'Media servicer' containing packets 1, 2, 3, 4, 5, 6, 7, and more. The 'Transmitting' stage shows these packets being sent. The 'Broadcast networks' path leads to a 'Terminal' where packets 4, 3, and 1 are shown, with packet 2 missing (indicated by an 'X'). The 'Mobile communication networks' path leads to the same 'Terminal' where packet 2 is received. Finally, the 'Receiving' stage shows the terminal outputting a 'Segment' with packet 2, and the diagram is labeled H.551(22).](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +Figure 4: The processing of convergence transmission. The diagram illustrates the flow of data segments and packets through a transmitting system and a receiving terminal. On the left, a vertical bar labeled 'Segment' shows packets 1 through 5 being processed. These are then distributed into two parallel paths: a 'Sending queue for broadcast networks' containing packets 4, 3, 2, and 1; and a 'Media servicer' containing packets 1, 2, 3, 4, 5, 6, 7, and more. The 'Transmitting' stage shows these packets being sent. The 'Broadcast networks' path leads to a 'Terminal' where packets 4, 3, and 1 are shown, with packet 2 missing (indicated by an 'X'). The 'Mobile communication networks' path leads to the same 'Terminal' where packet 2 is received. Finally, the 'Receiving' stage shows the terminal outputting a 'Segment' with packet 2, and the diagram is labeled H.551(22). + +**Figure 4 – The processing of convergence transmission** + +The convergence transmission scheme takes full advantages of the complementary strengths of broadcast networks and mobile communication networks. Hence, the system efficiency of multimedia streaming services over VMN is optimized. + +The reference protocol stack for convergence transmission of multimedia contents over VMN is given in Figure 5. Note that the convergence transmission protocols are agnostic to the underlying physical-layer standards and are transparent to the upper-layer standards. Thus, minimum modifications to the existing broadcast or mobile communication infrastructures can be guaranteed. + +![Figure 5: Reference protocol stack for convergence transmission. The diagram shows a layered protocol stack. At the top is 'Applications'. Below it, 'Service signalling', 'Non realtime protocol', 'Adaptive bitrate streaming protocols' (with a sub-layer 'DRM'), and another 'Non realtime protocol'. Below these is 'Low level signalling' and 'Convergence transmission protocols'. To the right of the convergence protocols is 'HTTP'. Below the convergence protocols are 'Broadcast network transport layer/network layer' and 'Broadcast network link layer/PHY layer'. To the right of these are 'UDP', 'TCP', and 'IP'. At the bottom are 'Broadcast network link layer/PHY layer' and 'Broadband network link layer/PHY layer'. The label H.551(22) is at the bottom right.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +| | | | | | +|-------------------------------------------------|------------------------------------|----------------------------------------|---------------------------------------------|-----------------------| +| Applications | | | | | +| Low level signalling | Service signalling | Non realtime protocol | Adaptive bitrate streaming protocols
    DRM | Non realtime protocol | +| | Convergence transmission protocols | | | HTTP | +| Broadcast network transport layer/network layer | | UDP | TCP | | +| | | IP | | | +| Broadcast network link layer/PHY layer | | Broadband network link layer/PHY layer | | | + +H.551(22) + +Figure 5: Reference protocol stack for convergence transmission. The diagram shows a layered protocol stack. At the top is 'Applications'. Below it, 'Service signalling', 'Non realtime protocol', 'Adaptive bitrate streaming protocols' (with a sub-layer 'DRM'), and another 'Non realtime protocol'. Below these is 'Low level signalling' and 'Convergence transmission protocols'. To the right of the convergence protocols is 'HTTP'. Below the convergence protocols are 'Broadcast network transport layer/network layer' and 'Broadcast network link layer/PHY layer'. To the right of these are 'UDP', 'TCP', and 'IP'. At the bottom are 'Broadcast network link layer/PHY layer' and 'Broadband network link layer/PHY layer'. The label H.551(22) is at the bottom right. + +**Figure 5 – Reference protocol stack for convergence transmission** + +The general assumption is that the network layer protocol may be based on both versions of the IP protocol (IPv4 and IPv6). It is advisable to select IPv6 [b-IETF RFC 8200] for direct and secure connectivity between VMS and the cloud platforms, for the following reasons: + +- The IETF clearly advises other standards development organizations (SDOs) to prefer IPv6 [b-IAB]. As a result, standardization work is recommended to assume IPv6. +- The IPv4 address space was formally exhausted in January 2011, when the Internet Assigned Numbers Authority (IANA) assigned its last IPv4 top-level address space (i.e., /8). Therefore, adopting IPv6 as the only network protocol represents the only viable solution to guarantee the evolution of network services and applications. +- The transition to IPv6 only is considered a strategic initiative by several governmental agencies. An example, among the others, is represented by [b-USG OMB], where the US Federal Government poses specific deadlines and targets to migrate the National Agencies networks to IPv6. +- User devices located in a vehicle may require end-to-end reachability, e.g., to connect to any applications and platforms. This is a case where network address translation (NAT) [b-IETF RFC 2663] coupled with private IPv4 addressing cannot be employed. Conversely, IPv6 provides full support of a global addressing scheme where the user devices are always reachable. + +Although people are more familiar with IPv4, and IPv6 deployment has certain new challenges, IPv6's user and traffic growth are much faster than those of IPv4. This means that, with all things considered, the collective wisdom of the industry has selected IPv6 for the future [b-ETSI WP35]. + +## 9.3 Reference receiver model + +The reference receiver model of in-vehicle devices is given in Figure 6, where the following functions are identified: + +- Broadcast connections and broadband connections that provide the connectivity for the receiver to receive signalling and data. +- Convergence transmission protocol/UDP/HTTP/TCP/IP stack and HTTP/TCP/IP stack that provide object-oriented transport protocols for the receiver to receive adaptive bit rate streaming (e.g., DASH or HLS) resources for multimedia streaming services. + +- Low-level Signalling: Signalling delivered over broadcast networks that enable the receiver to build a basic service list and bootstrap the discovery of the service signalling for each multimedia service. +- Service signalling: Service-related signalling that enables the receiver to discover and access multimedia streaming services and their content components. +- Cache: Temporary storage and handling of the manifests, initialization segments and media segments whose reception are facilitated by service signalling. +- Adaptive bit rate streaming (i.e., DASH/HLS) server: A local adaptive bit rate streaming server that is used to abstract the underlying layers to the adaptive bit rate streaming client. For the adaptive bit rate streaming client, manifests, initialization segments and media segments are provided through the adaptive bit rate streaming server. +- Adaptive bit rate streaming client: A function that consumes manifests and segments, and communicates with other components in the receiver to personalize the media experience based on platform capabilities, user preferences and user interaction. +- Application: A native or downloaded application that makes use of broadcast or broadband delivered data in order to provide a rich and interactive presentation to the end user. + +![Figure 6 – Reference receiver model of in-vehicle devices. This is a layered architecture diagram. At the top is the 'Applications' layer, which contains a 'Media player', 'DRM engine', and 'Adaptive bitrate streaming client'. Below this is a 'Conditional access engine' and a 'Cache (Manifest, segment, etc.)'. The 'Cache' is connected to an 'Adaptive bitrate streaming server'. Below these components is the 'Transport' layer, which includes 'Broadcast network transport layer/network layer', 'Convergence transmission protocols/UDP/HTTP/TCP/IP', and 'HTTP/TCP/IP'. At the bottom are two network layers: 'Broadcast network link layer/PHY layer' and 'Broadband network link layer/PHY layer'. Arrows indicate the flow of data and control signals between these layers and components. 'Low level signalling' and 'Service signalling' are shown as inputs to the Transport layer. The diagram is labeled H.551(22) in the bottom right corner.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg) + +Figure 6 – Reference receiver model of in-vehicle devices. This is a layered architecture diagram. At the top is the 'Applications' layer, which contains a 'Media player', 'DRM engine', and 'Adaptive bitrate streaming client'. Below this is a 'Conditional access engine' and a 'Cache (Manifest, segment, etc.)'. The 'Cache' is connected to an 'Adaptive bitrate streaming server'. Below these components is the 'Transport' layer, which includes 'Broadcast network transport layer/network layer', 'Convergence transmission protocols/UDP/HTTP/TCP/IP', and 'HTTP/TCP/IP'. At the bottom are two network layers: 'Broadcast network link layer/PHY layer' and 'Broadband network link layer/PHY layer'. Arrows indicate the flow of data and control signals between these layers and components. 'Low level signalling' and 'Service signalling' are shown as inputs to the Transport layer. The diagram is labeled H.551(22) in the bottom right corner. + +**Figure 6 – Reference receiver model of in-vehicle devices** + +A typical bootstrapping sequence of the reference receiver is presented as below: + +- The application requests a pre-configured service list in low level signalling. The service list is delivered to the application, which then provides a user interface for the selection of multimedia streaming services. User chooses a multimedia streaming service to consume. +- The application uses the service signalling entry point information carried in the service list for the selected service to provide access information to the convergence transmission protocol/UDP /HTTP/TCP/IP stack to retrieve the service signalling. Service signalling is delivered to the application. +- By using service signalling, the application provides access information to the convergence transmission protocol/UDP/HTTP/TCP/IP stack for downloading the adaptive bit rate streaming-formatted media components of the selected service, which are sent to the cache to be stored, de-scrambled and subsequently forwarded to the adaptive bit rate streaming server. +- Upon the selection of a service, the application activates the adaptive bit rate streaming client, causing the DASH/HLS client to request and receive media segments from the adaptive bit rate streaming server at or after the media segments availability start times. +- Upon reception of media segments, the composite function comprising the adaptive bit rate streaming client, DRM engine and media player decodes the received media segments, and the decoded media is returned to the application for play out. + +# **10 VMS security** + +The interactions between the VMS and the other components involved in the security of a car (typically the electronic control unit (ECU)) is recommended to be limited to the shared functions mentioned in clause 8.1. + +Details are given in Annex A. + +# **11 Personally identifiable information (PII) protection and privacy** + +VMS is recommended to provide end-to-end protection as vehicles become connected and offer more interactive services. More user data and privacy related information need to be protected to ensure confidentiality and integrity of the user data that is stored in the VMS, in the vehicle and the VMS cloud or backend servers. + +Details are given in Annex B. + +## Annex A + +### VMS security + +(This annex forms an integral part of this Recommendation.) + +### A.1 Overview + +The interactions between the VMS and the other components involved in the security of a car (typically the ECU) is recommended to be limited to the shared functions mentioned in clause 8.1. Indeed, it is recommended that the VMS does not negatively influence the functions of the other components that ensure the required security of a car, notably in the case of autonomous driving vehicles. + +Regarding VMS security, assumed threats to VMS and its eco-system are summarized in clause A.2, and security capabilities against threats are provided as an informative reference in clause A.3. + +### A.2 Assumed threats to VMS and its ecosystem + +#### A.2.1 Threats regarding vehicular multimedia service platform (VMSP) + +In recent years, diversification of connectivity in vehicles has increased remarkably, and in particular, connectivity with various servers located at VMSP is highly required. In the context of VMS, back-end servers are recognized as a VMSP, including OEM-provided servers, supplier-provided servers and ICT service-provided servers to support vehicle eco-system from the remote backend. The following threats can be identified in relation to VMSP: + +- Servers in VMSP used as a means to attack a vehicle or extract data. +- Services provided by VMSP being disrupted +- Data held on servers in VMSP being lost or compromised + +#### A.2.2 Threats to vehicles regarding their communication channels + +Vehicle communication includes external communications through cellular, LEO satellite, broadcast networks and short-range networks. Channels used in the above communications may be targets of attacks like spoofing, eavesdropping, message manipulation, etc. The following threats can be identified in relation to communication channels: + +- Unauthorized manipulation, deletion or other amendments to vehicle-held code/data +- VM interfaces can be used to gain access to further (intelligent) infrastructure within the vehicle (e.g., ECU unrelated to VMS) +- Use of untrusted/unreliable messages and session hijacking/replay attacks +- As VM applications can be updated using over the air, those attacks can apply to VM as well. +- Information disclosure +See clause 9 of [ITU-T F.749.3]. +- Denial of service attacks +- VM itself may not have access to critical infrastructure within the vehicle, but can serve as gateway for those attacks. +- Privileged access by an unprivileged user +- As personalized user accounts can be associated with VM applications, unprivileged access is possible. Unprivileged access via VM may not provide direct access to critical infrastructure (e.g., root access; access to braking system), but can again serve as gateway to access the vehicular infrastructure. +- Malware embedded in communication media + +- Intelligent VM rely on data transfer between the VMS and a VMSP in the cloud. By penetrating this communication channel, attackers might use messages/data transfers from the VMSP to the VMS to deploy malware. +- Messages with malicious content +- Intelligent VM rely on data transfer between the VMS and e.g., a VMSP in the cloud. By penetrating this communication channel, attackers might alter messages/data transfers from the VMSP to the VMS to gain access to VMS and/or ECUs within the targeted intelligent vehicle. + +#### **A.2.3 Threats to vehicles regarding their update procedures** + +There are two ways to update vehicle systems, namely, wired update through an on-board diagnostics (OBD) port, portable devices such as an SD card, or a USB flash drive, and wireless update by over-the-air. The software to be updated can be firmware or configuration data of the vehicle. Most electronic problem and software defects can be updated and solved electronically without physical access, e.g., via OBD tester. Furthermore, over-the-air (wireless) updates help in shortening the update cycle to minimize attack exposure for known vulnerabilities of the software. The following threats can be identified in relation to update procedures: + +- Misuse or compromise of update procedures +Regardless of whether the over-the-air update or local/physical update is used, the update procedure can include threats that use fabricated system update programs or compromised firmware. +The software can be manipulated before the update process, although the update process is intact. The software provider creates/prepares their software for the update, and the software is delivered to the target systems that require the update. Therefore, there can be a serious threat that the software can be manipulated and corrupted before it served. +Especially during the update procedure, cryptographic materials such as cryptographic keys and certificates used in the software update can be compromised and consequently it may cause an invalid or malicious software update. +- Denial of service and denial of a legitimate update +Denial of service attack against the update server or network to prevent the rollout of critical software updates and/or unlocking customer-specific features can be a possible attack in the software update procedure. It is also possible to deny legitimate updates. + +#### **A.2.4 Threats to vehicles regarding their external connectivity and connections** + +For a variety of convenient services, vehicles can be equipped with components to communicate with servers in VMSP, and can communicate to everything enabled by road users over a wireless connection. Besides convenience features, there are safety benefits such as the automatic emergency call functionality and those supported by V2X communication. However, the more vehicles connect to external entities for enhancing connectivity, the more threats and vulnerabilities show up because attack surfaces are expanded due to the additional interfaces. The following threats can be identified in relation to external connectivity and connections: + +- Manipulation of the connectivity of vehicle functions +VMS does not provide direct access to critical vehicle functions but can be used as gateway to access those critical components, e.g., dedicated ECUs. +- Hosted third-party software +VMS applications can be included in the class of "hosted third-party software". +- Devices connected to external interfaces + +As outlined in [ITU-T F.749.3], connectivity can be based on brought-in devices such as smart phones. + +### **A.3 Security capabilities based on identified threats** + +#### **A.3.1 Identity and access management (IAM), authentication, authorization and transaction audit** + +Multiple administrators and users are involved in VMS services, and these services are accessed and used internally and externally. Identity management is needed, not only to protect identities, but also to facilitate the access management, authentication, authorization and transaction audit processes in such a dynamic and open VMS infrastructure. + +One or more common trust models are needed by IAM for the authentication of identities, and by developers, hypervisors and other system components for the authentication of system components such as downloaded software modules, applications or datasets. + +IAM contributes to the confidentiality, integrity and availability of services and resources, and thus becomes essential in VMS. Furthermore, IAM may enable the implementation of single sign-on and identity federation for VMS using different authentication mechanisms or distributed in different security domains. + +Transaction audit protects against repudiation, enables forensic analysis after a security incident, and acts as a deterrent to attacks (both intrusion and insider). Transaction audit implies more than simple logging, but also includes active monitoring to flag up suspicious activities. + +#### **A.3.2 Interface security** + +This capability secures interfaces open to VMS developers and/or other contracted VMSP vendors through which various kinds of VMs are delivered, and secures communications based on these interfaces. Mechanisms available to ensure interface security include, but are not limited to: unilateral/mutual authentication, integrity checksum, end-to-end encryption and digital signature. + +#### **A.3.3 Network security** + +In a VMS environment, network security enables both physical and virtual network isolation, and secures communications among all participants. It enables network security domain partition, network border access controls (e.g., firewall), intrusion detection and prevention, network traffic segregation based on security policies, and it protects the network from attacks in both the physical and virtual network environments. + +#### **A.3.4 Operational security** + +This capability provides security protection for the daily operation and maintenance of VMS and VMSP infrastructure. + +This operational security capability includes: + +- Defining sets of security policies and security activities such as configuration management, patch upgrade, security assessment, incident response; +- Monitoring the VMSP's security measures and their effectiveness and giving appropriate reports to affected VMs. + +In the event that the VMSP's security measures or their effectiveness changes, all downstream VMs will be alerted to such changes. + +These reports and alerts enable authorized VMs to see appropriate incidents, audit information, and configuration data relating to their VMs. + +#### **A.3.5 Software and firmware updates** + +Secure OTA updates need to conform to baseline security standards. It is recommended that the update process take into account operational factors (e.g., timing of updates and encryption/decryption processes). The presence of multiple OEMs and third-party vendors contribute to different sub-system interfaces within a vehicle. As such, any vulnerability or cyber risk-targeted towards these OEMs or suppliers can effectively hijack a legitimate software OTA update, which is then sent as cloud data to be deployed to vehicles. + +Mechanism for updating software and firmware of VMS (ECUs and related systems) is recommended to be designed, implemented and operated. + +In the development of VMS service, mechanism for updating software and firmware of VMS is recommended to be designed and implemented as a basic function. The mechanism for rolling back software and firmware is recommended to also be implemented by design, to be used when an update fails. + +In the utilization and support of VMS service, the software/firmware update package has its digital signature, signing certificates and signing certificate chain verified by the device, before the update process begins. + +Cryptographic keys used to update integrity protection and confidentiality are recommended to be securely managed and appropriately operated. When updates are conducted over the air (OTA), the updates are recommended to be performed over encrypted communication channels. + +Updates using OTA are recommended to either succeed completely or fail in a recoverable manner. In the case of a failed update, the device is recommended to be rolling back to the last known good configuration, and it is recommended to have no ability to disable a device's connection to the update server. + +#### **A.3.6 Application security** + +These security capabilities are often taken to improve the security of a "VMS application" often by finding, fixing and preventing security vulnerabilities in VMS and its eco-system. Different techniques are used to surface such security vulnerabilities at different stages of an applications lifecycle such as design, development, deployment, upgrade, maintenance. + +#### **A.3.7 Incident management** + +Incident management provides incident monitoring, prediction, alerting and response. In order to know whether the VMS is operating as expected through the whole infrastructure, continuous monitoring is necessary (e.g., monitoring the real-time performance of servers used in VMSP). This enables systems to capture the service security status, identify abnormal conditions, and provide early warning of security system overloads, breaches, service discontinuity, etc. After the occurrence of security incidents, the problem is identified and the incident is quickly responded to, either automatically or with the intervention of a human administrator. Closed incidents are logged and analysed for possible underlying patterns which can then be proactively addressed. + +#### **A.3.8 Cryptography** + +This capability ensures confidentiality and integrity of data used and exchanged in VMS and its eco-systems. This is the basic method for storing and transmitting data in a particular form so that only those for whom it is intended can read and process it. This capability not only protects VMS data from theft or alteration but can also be used for user authentication, etc. + +As a good example for implementing cryptography, guidelines on the selection of cryptographic primitives for IPTV systems are given in [b-ITU-T X.1197 Amd1] and can be applied to multimedia streams in vehicular systems, insofar as those are of the same level of importance/criticality as multimedia streams in non-vehicular IPTV systems. Likewise, for vehicles with 5G connectivity, + +[b-ITU-T X.1811] provides further guidance on how to implement the baseline security levels of [b-ITU-T X.1197 Amd1], including but not limited to multimedia streams. + +Furthermore, with a DRM solution based on strong, authenticated encryption, meant to allow only legitimate, copyrighted content to be consumed by the infotainment system, only legitimate line-of-sight external multimedia streams would be taken into account by the infotainment and assisted driving system, therefore allowing traffic to proceed without any disruption. + +#### **A.3.9 Hardware security** + +This capability aims at eliminating the vulnerabilities and security weaknesses inherent to VMS hardware, and provides a secure environment for hardware-level implementation. In particular, it has become essential to implement many fundamental cryptographic functions in hardware, such as cryptographic key management, execution of encryption/decryption, and provision of digital signatures and strong authentication, which are importantly utilized for ensuring security in VMS. For that purpose, it is necessary to securely design and verify the operation of related hardware from the hardware design stage, in consideration of possible threats and attacks. + +For example, to ensure ECU-level security in the VMS architecture, each implemented ECU is recommended to be protected by HSMs and PUFs, which are typical components of hardware security modules. + +#### **A.3.10 General security capabilities** + +NOTE – The following security capabilities are optional for this Recommendation. However, those capabilities can be effectively utilized for improving VMS security. + +##### **– Security assessment and audit** + +This capability enables the security evaluation of VMS. It enables an authorized party to verify that a VMS complies with the applicable security requirements. Security assessment or security audit could be performed by the VMS, VSMP or a third party, and security certification could be performed by an authorized third party. + +Appropriate security criteria are implemented to provide a mutual understanding of the security level between the VMS and VMSP. + +##### **– Trust model** + +A common trust model is necessary for any system where multiple providers cooperate to provide a trustworthy service. + +Because of the highly multi-stakeholder nature of VMS, the VMS environment will need to incorporate an overall trust model. This trust model will enable the creation of islands and/or federations of trusted entities, such that disparate elements of the system will be able to authenticate the identity and authorized rights of other entities and components. Each island or federation of trust will be based on one or more trusted authorities (e.g., a public key infrastructure (PKI) certificate authority). + +##### **– Data isolation and protection** + +##### **a) Data isolation** + +Data isolation may be realized logically or physically, depending on the required isolation granularity and the specific deployment of VMS software and hardware. + +##### **b) Data protection** + +Data protection ensures that VMS data and derived data held in a VMSP are appropriately protected so that it can only be accessed or changed as authorized by the VMS. This protection may include some combination of access control lists, integrity verification, error correction/data recovery, encryption and other appropriate mechanisms. + +When a VMSP provides storage encryption for VMs, this function can be client-side encryption (e.g., within a CSP application) or server-side encryption. + +##### – Security coordination + +Since different VMs imply different implementations of security controls, this security capability coordinates heterogeneous security mechanisms to avoid protection conflicts. + +Parties playing different roles in the VMS ecosystem have different degrees of control over the physical or virtual resources and services, including the control of security. + +For each party, there will be various security mechanisms, including hypervisor isolation, IAM. + +Network protection, etc. Security coordination depends on the interoperability and harmonization of diverse security mechanisms. + +##### – Supply chain security + +A VMSP uses several suppliers to build their services. Some of these will be VMS industry participants, while others will be traditional information technology (IT) equipment or service suppliers, e.g., hardware manufacturers with no direct relationship with VMS. This capability enables the establishment of a trust relationship between the VMSP and all participants in the supply chain by security activities. These supply chain security activities involve identifying and gathering information about the VMSP's acquired components and services that are used to provide VMs and enforcing supply chain security policies. + +For example, typical supply chain security activities in a VMSP may include: + +- a) Confirmation of background information about the participants in the supply chain; +- b) Validation of hardware, software and services employed by the VMSP; +- c) Inspection of the hardware and software purchased by the VMSP to ensure that it was not tampered with while in-transit; +- d) Providing mechanisms to verify the provenance of VMS software, for example, code provided by a software vender. + +This capability is continuous to cover ongoing system evolution and updates. + +##### – Secure development environment and procedures + +This capability is to avoid introduction of insecurity to VMS and its eco-systems during development. A development environment includes people, processes, technology and facilities associated with a system development. The VMS service developer is recommended to assess risks in individual VMS development efforts and establish secure development environments considering: + +- a) Personnel working in the environment; +- b) Applied development methodologies and software and data handling processes; +- c) Use of outsourced products and services; +- d) Physical and network environment; and +- e) Coexistence with other development and operational efforts. + +The VMS service developer also needs to determine development environment and associated procedures to mitigate the risks. The procedures are recommended to be disseminated to individuals involved in the development efforts. + +## Annex B + +## Personally identifiable information (PII) protection and privacy + +(This annex forms an integral part of this Recommendation.) + +VMS is recommended to provide end-to-end protection as vehicles become connected and offer more interactive services. More user data and privacy related information need to be protected to ensure confidentiality and integrity of the user data that is stored in the VMS, in the vehicle and the VMS cloud or backend servers. + +According to National Institute of Standards and Technology (NIST) of the US, PII is 'any representation of information that permits the identity of an individual to whom the information applies to be reasonably inferred by either direct or indirect means' [b-NIST SP 800-79-2]. + +There is no single definition of the term "privacy". The meaning of privacy depends on legal, political, societal, cultural and socio-technological contexts. + +Generally, informational privacy can be defined as follows: + +- 1) An individual has informational privacy if she/he is protected against the penetration, interference or the access to own data by unauthorized others. + +PII protection is one aspect to assure privacy. + +VMS might store PII or might function as a gateway to access PII of the vehicle owner, driver and/or further occupants. + +### B.1 Information sources + +VMS comprises multiple information input sources such as: + +- Sensors (motion detectors, location detectors, etc.), +- Camera (personalization, feature recognition, etc.) +- Microphone – Audio (might be further used for voice recordings and voice recognition, voice biometrics, etc.) +- Network communication protocols identifiers such as IP address, MAC address, etc. +- Media sources such as USB memory stick, Secure Digital card, external hard disk, etc. +- Third party applications, payment gateways, services, devices, accessories, etc. + +VMS stores and share the information with other systems in the vehicle or cloud based on vehicle architecture, regional, legislative, certification requirements. + +### B.2 Implementation of PII protection: General considerations + +Personal data (e.g., in data, text, audio, video or images) is to be protected, as well as any content that users other than the intended customer or any end user (such as remote cloud, stores or processes) using the VMS may request. + +There needs to be agreement for data sharing for personal data relating to each customer, the end users and third parties. Any such customer agreement, or any other relevant agreement governing the use of VMS service is to be based on the following criteria: + +- Personalized access based on user selection of services and interest +- VMS designed to allow for its use in accordance with the privacy regulatory requirements +- VMS software, hardware and network design it to allow only authenticated access. + +- VMS PII and privacy protection is to be designed for private vehicles with one single user, and for shared vehicle with several users. + +### **B.3 Data visibility and transparency** + +Well-known, highly scrutinized security standards are recommended to be implemented. Proprietary encryption algorithms are recommended to be avoided. + +Well-known processes are recommended to be adopted. + +Users are recommended to be notified about the data stored /accessible through the VMS. As transparency enhances user acceptance, user notification is recommended to comprise information about data type, purpose of collection, identity of data processing entities and duration of data storage. + +#### **B.3.1 Privacy-by-default** + +It is recommended that users be able to control the limit of data download, as well as to opt-in/opt-out of data download and storage. Opt-out strategies are more privacy-preserving and align better with the principles of privacy-by-default. Therefore, opt-out strategies are recommended. + +VMS is recommended to identify the list of use cases that fulfils the data privacy requirements and settings. + +Applications might use multiple resources for specific use cases. For example, in the case of location services, Bluetooth, GPS, crowd-sourced Wi-Fi hotspots or cellular tower locations might be used to determine the user's approximate locations. VMS is recommended to provide users with the possibility to turn off specific tracking possibilities. Global settings control might be used to realize this by defining privacy policies for all applications. Alternatively, occupants might be enabled to control data access on a single application level. Privacy controls like PRICON posit approaches, which combine both approaches, can be used. Another option for VMS might be a "Do Not Track" ("DNT") signal that is already used by web browsers. A DNT signal is a HTTP header field indicating user preference for tracking user activities on a service or through cross-site user tracking. + +Applications or controls may request to receive e.g., location data only while the application is being used or to allow it at any time. Occupants may choose not to allow this access and are recommended to be able to change their choice at any time in the settings. If applied to a service that operates also within the European Union, the General Data Protection Regulation (GDPR) demands to enable the user to make informed privacy decisions. An informed privacy decision is possible if the decider is aware of the consequences of data disclosure (who gets what data, for what purpose, and under which conditions) or denial (which specific functions are restricted). + +If an application has been granted access to certain data, and to use them in background mode, users need to be reminded of their approval and be allowed to change the application's access. + +VMS architecture is recommended to be robust to prevent applications from accessing information to which the user has not explicitly granted access permission. + +### **B.4 Data accuracy and data integrity** + +VMS is recommended to maintain all the aspects of the data, such as data upload, download, communication and deletion in specific manner. + +End-to-end security – Full lifecycle protection. Regular code review and rigorous security testing are recommended to be done. Moreover, protection strategies on a broadcasting level, database level and receiver level are recommended to be implemented. + +Software security assurance is recommended to be provided in order to prevent loss, inaccuracy, alteration, unavailability or misuse of the data and resources that are used, controlled and protected. + +Users are recommended to be allowed to verify PII accuracy and the lawfulness of its processing; + +Integrity implies that the consistency, accuracy and trustworthiness of data are maintained over time. Hence, a guard against improper information modification or destruction is recommended to be established. Appropriate measures are recommended to ensure information non-repudiation and authenticity. + +In settings, users are recommended to be able to see which applications they have permitted access to certain information, as well as grant or revoke any future access. + +Additionally, VMS OS is recommended to provide restrictions that prevent data movement between applications and accounts installed by a trustworthy data management solution and those installed by the user. + +Users can request the correction, amendment or deletion of their personally identifiable information if it is inaccurate or if they believe that the processing of their personally identifiable information is in violation of applicable law. + +Systems, applications and procedures should be implemented to secure user personally identifiable information, to minimize the risks of theft, damage, loss of information, or unauthorized access or use of information. + +Any unauthorized changes to PII in VMS or the cloud are recommended to be detected and notified to the user. + +### **B.5 Confidentiality** + +Confidentiality consists in preserving authorized restrictions on access and disclosure, including means for protecting personal privacy and proprietary information. + +#### **B.5.1 Confidentiality impact levels** + +PII is recommended to be evaluated to determine its confidentiality impact level, so that appropriate safeguards can be applied. Not all PII data stored or created is recommended to be treated equally. + +Confidentiality impact levels are recommended to be assessed as low, medium or high depending on identifiability, data sensitivity and obligation to protect according to regulations. + +#### **B.5.2 Confidentiality protection** + +Confidentiality protection is recommended to be realized through the following measures: + +- Implementing an access control mechanism using a password to access the data from VMS. +- Multilayer access to high impact confidential PII. +- Multi-level access control from mobile phones, laptops and personal digital devices. +- Encrypting the PII before transmission. Detailed measures are described in clause A.3.8 (Cryptography). + +Moreover, risk assessments prior to the deployment of new requirements are recommended to be performed. A continuous risk monitoring mechanism for evaluating changes in the VMS or the identification of new risks associated with the VMS is recommended to be implemented. + +### **B.6 Data anonymization** + +Data anonymization is the process of irreversibly altering classified data in order to protect PII data subjects. + +By anonymizing the data handled in the VMS environment, it is possible to realize a wide range of data analysis and data sharing. + +### **B.7 Data availability** + +Availability demands ensuring timely and reliable access to and use of information. + +Authorized occupants are recommended to be given detailed control over system services use of location information. This includes their ability to turn off the inclusion of location information in information collected by internal applications, navigation search history, and Bluetooth and Wi-Fi access information. If the user signs-in to OEM cloud, functionally necessary applications are granted access by default to OEM cloud. Users are recommended to control each application's access to the cloud in settings. + +If PII is accessed remotely by telematics, connected services are recommended to operate with multi-level authentication. + +Since data is available by performing various data processing (calculation, statistical processing, etc.) in an encrypted format (for example, using homomorphic encryption), similar data processing can be performed on the data in VMS. + +## Bibliography + +- [b-ITU-T X.1197 Amd1] Recommendation ITU-T X.1197 Amd.1 (2019), *Guidelines on Criteria for Selecting Cryptographic Algorithms for IPTV Service and Content Protection, Amendment 1*. +- [b-ITU-T X.1811] Recommendation ITU-T X.1811 (2020), *Security Guidelines for Applying Quantum-Safe Algorithms in 5G Systems*. +- [b-ETSI WP35] ETSI White Paper 35 (2020), *IPv6 Best Practices, Benefits, Transition Challenges and the Way Forward*. +[https://www.etsi.org/images/files/ETSIWhitePapers/etsi\\_WP35\\_IPv6\\_Best\\_Practices\\_Benefits\\_Transition\\_Challenges\\_and\\_the\\_Way\\_Forward.pdf](https://www.etsi.org/images/files/ETSIWhitePapers/etsi_WP35_IPv6_Best_Practices_Benefits_Transition_Challenges_and_the_Way_Forward.pdf) +- [b-IEEE 802.11] IEEE 802.11-2020, *IEEE Standard for Information Technology – Telecommunications and Information Exchange between Systems – Local and Metropolitan Area Networks – Specific Requirements – Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications*. +- [b-IETF RFC 2663] IETF RFC 2663 (1999), *IP Network Address Translator (NAT) Terminology and Considerations*. +- [b-IETF RFC 8200] IETF RFC 8200 (July 2017), *Internet Protocol, Version 6 (IPv6) Specification*. +- [b-IETF RFC 8216] IETF RFC 8216 (2017), *HTTP Live Streaming*. +- [b-ISO/IEC 23009-1] ISO/IEC 23009-1:2019, *Information technology – Dynamic adaptive streaming over HTTP (DASH) – Part 1: Media presentation description and segment formats*. +- [b-IAB] Internet Architecture Board (IAB) statement on IPv6 address exhaustion (November 2016). + [Online]. +- [b-NIST SP 800-79-2] NIST Special Publication 800-79-2 (2015), *Guidelines for the Authorization of Personal Identity Verification Card Issues (PCI) and Derived PIV Credential Issuers (DPCI)*. +- [b-USG OMB] US Office of Management and Budget (November 2020), *Memorandum for heads of executive departments and agencies*. + [Online]. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.560-201712-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/H/T-REC-H.560-201712-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f2b874b54ad20ee5fb079a7ee0f03cee5d53304 --- /dev/null +++ b/marked/H/T-REC-H.560-201712-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b0cabfcdeb745b8554d5b1b2c492e5d222ac5d5595c39d31cc1df1f8049d831 +size 150362 diff --git a/marked/H/T-REC-H.560-201712-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.560-201712-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec563d1aa16d3d1c5807ab174d485472a479f411 --- /dev/null +++ b/marked/H/T-REC-H.560-201712-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7adf640c8a4bc1d427815b7d0875c5cb10157c770d408ecfa9973d19f08ba928 +size 155423 diff --git a/marked/H/T-REC-H.560-201712-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/H/T-REC-H.560-201712-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78efd3d774fef60fab6cf6a76bd020278ea3b302 --- /dev/null +++ b/marked/H/T-REC-H.560-201712-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:848901baabd545ad16d3b1f22e3a7cd1961ed1e5b8f47ab31dc3ec5d028a27cc +size 160401 diff --git a/marked/H/T-REC-H.560-201712-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/H/T-REC-H.560-201712-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d41cc2560056fc066383928dff43a459942d45d --- /dev/null +++ b/marked/H/T-REC-H.560-201712-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:862fd30af89a5d2b5b112e5113fe97c1906358b422f853b37224144c445532d9 +size 7311 diff --git a/marked/H/T-REC-H.560-201712-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/H/T-REC-H.560-201712-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b737aa75ed0bf73249bdcf5ea3ca4342d00f612 --- /dev/null +++ b/marked/H/T-REC-H.560-201712-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fd134ae42fad4f81f1b035558216a0fd967a3eac816b567a99d7569e4c8fb0e +size 163502 diff --git a/marked/H/T-REC-H.560-201712-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/H/T-REC-H.560-201712-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcc66bc56e75aa413b715f27d9b5297b00816b33 --- /dev/null +++ b/marked/H/T-REC-H.560-201712-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b464638856fd2b02521612b84f42fb27a4b9b7bb179996fdb98f495ca941189 +size 162511 diff --git a/marked/H/T-REC-H.560-201712-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.560-201712-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f803feca41d3996a4d37799f0d261c6a017756f --- /dev/null +++ b/marked/H/T-REC-H.560-201712-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cde7fa89143383da0efcfa3c7fe1917c8ca7fc96508512d3249ab0ea5cffbfe1 +size 160487 diff --git a/marked/H/T-REC-H.560-201712-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/H/T-REC-H.560-201712-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22bb018cc03ebba2e2fea9e2299071ff449100ac --- /dev/null +++ b/marked/H/T-REC-H.560-201712-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5061fec01ad4a26d995f4c9dba8f9ab03e03bad4761406f4c7b9af2651eb553b +size 41451 diff --git a/marked/H/T-REC-H.560-201712-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/H/T-REC-H.560-201712-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0128f3bf54b56bc38c557334f9e93472d6a1ee36 --- /dev/null +++ b/marked/H/T-REC-H.560-201712-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce5d4e3031f1cd935301ce71d82f3bbe4ca387f5defffded50937e710ece3f80 +size 159616 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03a1479e86e9061cc3f48fdbee2d50616f540f2c --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39e6f46b4d768a19fa592a7bf7254ec1a6466219cb5254b648f2adcc5dfaae0c +size 38943 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/077f85b82901283b4657fd2b45fc0294_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/077f85b82901283b4657fd2b45fc0294_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c725867195aee321f4b2ee3033eca6f7bf68afa --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/077f85b82901283b4657fd2b45fc0294_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e280a57989a9e67b2e75e5ed4449874bdb8aaa444485a4778a070eb55fecdcf2 +size 93246 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/0897c77315bfe37a098f6b4ea39570d2_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/0897c77315bfe37a098f6b4ea39570d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..421035be9f8ce98a5bb43576a341f04e631bab9e --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/0897c77315bfe37a098f6b4ea39570d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:389ffdf9a5ee4b9fcbde2b8cdc9ccab826cc77da7a9ab26cc02904890dd25eed +size 51033 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9f747514d4e63ec7a26cd7398aed09aef614b5a --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95d0f178a57dbb245e5841ca89737eca9e5555b4e79901ec4625f4947ae82a48 +size 81708 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d926f4718ec4ac4cf358b19a2b7f7fc5cba5790 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83d01b9cbe6c42fabe9c3043a0fce315115b3484b85d3bffb3657abd1ea42661 +size 146320 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30fd9e5fa2249b7a9e2093b2de27b600859a5183 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6426d2f8b2d971450bfd027625b9f2e02c0afd8265d3031bd835e1b451ed97a +size 76827 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58415273053e3cf603b000df833bbaaa72f14459 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4148114d429dcbc343fe05f25bad464c56ff460644ba3de03bfd4d4d0250edb0 +size 52576 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/18b914bd6d55df64c6935e65803a3f79_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/18b914bd6d55df64c6935e65803a3f79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c19be60c0e52675649990ac6240338bd946a158d --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/18b914bd6d55df64c6935e65803a3f79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3b690084d44590ad36508cfc573da53de535f008b66a5ed2dcc2ac8f180625f +size 21256 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/1b893df61c2b73b7a85e65fc1f58e203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdaae2a49aa5a673e2062e010248ea6969761277 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/1b893df61c2b73b7a85e65fc1f58e203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb45b5249f0238445d1782c8384c68dd0950c3f8d1460d8a4146ecb0d1d2c393 +size 49266 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/1c20b988e3792ded6d601aca944792a9_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/1c20b988e3792ded6d601aca944792a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be9b5468f0fd7cb5d54a8227f62e3a600d7eb05c --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/1c20b988e3792ded6d601aca944792a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbe251c911d9f5317cb9b84548d9eeafc31b8d3005a1edd0a65ea35920d5722a +size 60179 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a557cc217e48eb37f1193d6294697395aa1b4ed8 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c39c8b683f6651f5b1181182beb1db5cf7ecdcb7dfec7ba6a5bc3a63f662658e +size 122687 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a38f097db73a6d834d9ce0f14b1bc6e86bd6a434 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8397baf50a63d806263d7f9e276827cd78f8ae24179425994dc4104a52e58461 +size 57114 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20530858ffb5fd2fa6f1a85d335556fc6c51b178 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b09c573d052534fe7a59b8805ea655930a1fc4ceb2a6f8f3581931dea7cb865 +size 24331 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e86990ce6ae678e7722fc2e39d7ee07df9a0e8a --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b80f3969921a5dd36fdc72d76eb0ff1aa62baa6456a8ee096c6f7d89b73cbfe +size 48618 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d2c4af65762a2ddddeeb7dccfad02fcab86a139 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eccabd7b79fef63604732b58431fcdb3ff07dabd42690f524c17814040acf512 +size 43081 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dfd09fd0c252da27b413e072807d4ae49216328 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd3dceabae93262e7a7d651c502ed72f4966ac0542c7d5f47304374bd8ea678a +size 37000 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad687c09c37d7bca887d6917ef789727737d1ce7 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f32f5cd8475efac7dcf50c3b1028b5cd34a1b0c1ea8022fb314d4a7a8e67654 +size 81319 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84756269c4a5c6826f03959ae8f2f6340b1a658b --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89c3ef63ec72a1fb9ee86bee90449b3e36aefa7ed8c52464bc5a7e09ff3271ef +size 64163 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ba5869aa7b4665bde1491a5d7d93195e9d98cae --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17cafba94ef103d8bf1d80284adaf07e9ee9999820ed3aa9b2716701dd44db36 +size 50660 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcd0786e5be8e755e1c5e34e25d0d53c0354a914 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22c34c3f90992c85824a460640aa8afeed883fa82d3861949ad7e965f30dfa2b +size 113626 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc84fad63da03c5d772c71aa6003526b3e6ac271 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:759aa548085ad4ff08449557ff830b21d8b891c312cc10471d368e9eb1c8c920 +size 34707 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71a10ebf6171acbd747d286a3965ece707a5b0fe --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3c36479ec54d7c6c1fc3ac25f0e69c633bc3d2438be17fec537b8409911ad9f +size 98790 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..588805640716f2c2b623164665479ea6da0b2051 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7962ddb95d9074c5e0ca5329b2e857912e092171dc117ee1bf511bacbefce5aa +size 39021 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..859403c8c91c9445a7e37a20868c1970db1ee156 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fb2a29f46e879a0f09ab2edaecc3611b4b653bcd8e77a0e0d8b4ad48dcdcc9d +size 52181 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c125c355658bfc4f365c8e821fdb0258443b9e5b --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0d762a6fe486395d4d84cf27585d0214b84018726fb9da7e28ae8dd843efd03 +size 99346 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ac2e46e96093a3c9f13904ea8cf957767d5872b --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd91e307f92211e219544d08243b5216beb1c0c380b056c2013c672974b6e8f0 +size 57125 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fa3333b452dd0f0c1d468be5e93fe9e6455c008 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d8efd74633aa9de12275c393e13e2d94e7350f5e65b4b11c98013ae41d3a88b +size 62595 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1e4073fc9264df49bb4873e083b182dafc4cb03 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6478b3764cf6f923551455c56569bae810621667bdcf1c6c9a8230a2cbb71ad5 +size 118613 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/7c3ecd751b69a0fc7b08633a84822f42_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/7c3ecd751b69a0fc7b08633a84822f42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5d38c569a8dcecaa282b092f0601f5d76a2b7e7 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/7c3ecd751b69a0fc7b08633a84822f42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c29283a63325662e01fbda9fa9aca1170ac8e4686c3563d404a3e6122aacae6 +size 57877 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/7ec36a0a9788e1cb33df5372695498c8_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/7ec36a0a9788e1cb33df5372695498c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe02c8845699298dc12c7f075fb0ce4c9cf526e5 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/7ec36a0a9788e1cb33df5372695498c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49e18583e73f6ac32ed39d7f00729f578e04d872e1a8d2c0852f690d66d8d836 +size 96292 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..195c38eacfbb289c216780a0ab90bf401b178be8 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:130be1951e16a839b960499fb0ce80ed120bf78caaecb7da9cf8372a98aea19a +size 46765 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30a27e4a24ec3fc70ffd32352c27f314c658e120 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a57b2a916839b4d1404ea0e8b8afa51dbb89cb7dbdc8c39fef99e415ef6de27d +size 35101 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df781db0f2cbd387a794bf9c08c89c47ff603b62 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfa671be965f29974b7d384aa9fdbc30103dc3dec530940f705f5214a66b7ede +size 44648 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53ee6f80c2a593ee70859490fdfe9ed6d98232dc --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e23c99c67f1781a5217df73428aafebbe68a7158f9a96aba0ef1c4153ebed535 +size 51965 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86daf120a391dbe99e885128ef8138a5bd1974a5 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3fd5fed854ee74c4766874a95f2a2b71a8187f1f63256e1a2429f4107c364c0 +size 83532 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de0daa842a7f31e66678c19324544008f0574416 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:321dbd2613f7ef3328edeed611c6b115a1c42ad5ca6ac566114cc634f147be4f +size 151612 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/9dc9f41d7d76c1add4b190d348cb1533_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/9dc9f41d7d76c1add4b190d348cb1533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b8c62d5610bae144b47e9c5485481938a70ee3d --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/9dc9f41d7d76c1add4b190d348cb1533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eaa7a6233f915fb7b1a0ad174139f4fc1e13d85db9e653c881b1fc9eb50f292b +size 60275 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5807cf188ce7d9dd4162f26881009a9a8d9f086f --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c1797e87204007d30b2f6cda780ac6b14d846eafb3fc06d4e33e91bdb99499d +size 32095 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b1c8e8d910c03e9692a136beda607d4116d2bde --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b65af654adb8da9847f42133e37e292f9704b32013c3c11b2384503d266ad04 +size 50530 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28fb32528fe5d1ce262445cf2ddd2f2c292c0d2c --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:094d4e7b9161fd48dcc1e253672c316d5d8830dfda149a5e8df657594b0ec2c6 +size 36190 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/a7835229df7a34816e1d35b5bbbc8c9e_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/a7835229df7a34816e1d35b5bbbc8c9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdc55c0dd5eeb6e8657f792bde951d1528ac40f1 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/a7835229df7a34816e1d35b5bbbc8c9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bf27e869e7ded51dcf96d564a87e7aea5aa20fe2232cfe59514337c1b635e35 +size 59275 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3918af8a4def38b0aec030ddf475ea1dae32b2ca --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c2f0a66a7c43c5e413aef8500c11284e9da62d8b0eab7a57f582815743d7d78 +size 52488 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/b550cb515008f6bab9f295adcb28b5f6_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/b550cb515008f6bab9f295adcb28b5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..453b7ca9fd2fa2aaac14910f043759a3df807491 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/b550cb515008f6bab9f295adcb28b5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7b21ee96979b08d8b4d83534f429634877cd170a626175c515c9c7330c900c4 +size 28738 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dead996cb023f535f16f92bc0c5eacb2f0e60153 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2bbc5fcd1691a69f13659e186d14614ce4a111f8c4cefed2f63fb34db2204f4 +size 44609 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60bf3491e9e6cdc89b9c261447d2e9b77596a97f --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fbd2863320cfd1a3f909758ee49c52dcb71bd267b83d144762a001e63c051d8 +size 26011 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/c93c4b33a2b42c8dd6d82a354f2f89f1_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/c93c4b33a2b42c8dd6d82a354f2f89f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8fa377cf33cae310fdcef25ff6688983a474da9 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/c93c4b33a2b42c8dd6d82a354f2f89f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54cb38b705fea534945f05c581aefbc7ecd1e980cdbd711783c9d79112fcde05 +size 89326 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ccc0b585be8f47ca612ffb3253714ad679ccaa1 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbfb8ddc2bbdce50d6129cf92af9bc3c8f1c53cad46298acd7a4a6433d34363f +size 52855 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cc8a0be3508aedfdc68822553d7f0ea6cd48320 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afaba31d39cf5c74d52fc123ff17fc6dcf334fcd62c034b11bfffc21f7d3292b +size 30614 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74d10252596d67b8636d8f2de8c9857bf3e61227 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66716b39b892e693cc0f5f4e59575d1e6563e7e151837542a44ba8d6574308a8 +size 47783 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b84da5bae15278a6cb0915212069dcec78db36b9 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feb41bac3ffe48228cf0cff8e15c9e484a3a96b6cb13a10a866765c60b6c5504 +size 38298 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7386d395f483892c9f9ed3dbf12db3d7c85c789 --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3170d6a4686fd0d8ed171c32c3bb2dc2007976bad11a59ee8a5ebad6e287c481 +size 113209 diff --git a/marked/H/T-REC-H.610-200307-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/H/T-REC-H.610-200307-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a8d3b36cf1279538f7270876b8b4947e3d47ecb --- /dev/null +++ b/marked/H/T-REC-H.610-200307-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1d0de8c8e80b59ba11762fe96e4bc882761a8272ec3ba97473fd4369dd8cf6d +size 82534 diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/raw.md b/marked/H/T-REC-H.622-200806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ae3d8b0885ed3a877dc3de14733fc6d8d3139e72 --- /dev/null +++ b/marked/H/T-REC-H.622-200806-I_PDF-E/raw.md @@ -0,0 +1,910 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.622** + +(06/2008) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Broadband, triple-play and advanced multimedia +services – Advanced multimedia services and applications + +# --- **A generic home network architecture with support for multimedia services** + +Recommendation ITU-T H.622 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T H.622** + +# **A generic home network architecture with support for multimedia services** + +## **Summary** + +Recommendation ITU-T H.622 describes the architectural framework of a home network that supports multimedia services. Definitions of home network elements such as access gateway, domains, terminals and interfaces are introduced with explanations. This Recommendation also provides a comparison with related documents. + +## **Source** + +Recommendation ITU-T H.622 was approved on 13 June 2008 by ITU-T Study Group 16 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +Access gateway, domain, home network, terminal. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | Page | +|--------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Model of the home network..... | 4 | +| 6.1 Concept of layered model..... | 4 | +| 6.2 Transport model of the home network ..... | 5 | +| 6.3 Application model of the home network..... | 5 | +| 7 QoS ..... | 13 | +| 7.1 Class-based QoS..... | 14 | +| 7.2 Session-based QoS ..... | 15 | +| 7.3 QoS in primary and secondary domains..... | 15 | +| 8 Management Functionality ..... | 16 | +| 8.1 IP address management ..... | 16 | +| 9 Security..... | 18 | +| Appendix I – Components in home network documents..... | 19 | +| I.1 Introduction ..... | 19 | +| I.2 Access GW ..... | 19 | +| I.3 Terminal ..... | 21 | +| I.4 Other devices ..... | 21 | +| I.5 Network domain ..... | 22 | +| I.6 Interfaces ..... | 23 | +| Bibliography..... | 25 | + +# Introduction + +The home network is recognized as an important element of multimedia services. Considering the configuration of typical broadband services, the home network has two major roles; an extension of the access network and a transmission medium for data distribution among home devices. A fundamental difference can be found between these two roles. As an extension of the access network, the home network should provide characteristics similar to those of the access network, quality of service (QoS) for example. The home network also inter-connects consumer electronic devices in the same home. For this purpose, this part of the home network may not need to work with the functional entities in the network or service provider. + +To clarify these two different roles of the home network, Recommendation ITU-T H.622 introduces the concept of primary and secondary domains. The primary domain is defined as that part of the home network that works as an extension of the access NW, while the secondary domain is defined as the rest of the home network. Primary and secondary terminals are introduced in the same way. Some key features of the home network such as QoS and management that are defined in other documents are described in this context. + +Since the home network includes various technical areas from physical data transmission to multimedia capability, it is difficult for any single document to cover all issues. This Recommendation and Recommendation ITU-T G.9970, which is an accompanying Recommendation, share the same layered model that consists of transport and application models. This Recommendation mostly focuses on the issues related to the application model. For better understanding of the home network, users of this Recommendation are encouraged to consider Recommendation ITU-T G.9970. + +# A generic home network architecture with support for multimedia services + +# 1 Scope + +This Recommendation describes a generic home network architecture that is applicable to, including but not limited to, fibre-to-the-home (FTTH), xDSL and cable television (CATV). The architecture is designed to support a wide range of multimedia services such as Internet Protocol television (IPTV), IP-telephony and video telephony as well as legacy services, if needed. The goal of the architecture is to define functionalities and interfaces that support these services with the demanded level of quality of service (QoS), security and management capability in the home network domain based on [ITU-T J.190]. + +The home network specific to each access network can be defined based on functional entities and interfaces defined in this Recommendation. + +This Recommendation uses the transmission functionality and demarcation point between the access network and the home network defined in [b-ITU-T G.9970] that contains more details about these aspects. Users of this Recommendation are encouraged to consider both Recommendations for complete understanding of the generic home network architecture. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.610] Recommendation ITU-T H.610 (2003), *Full service VDSL – System architecture and customer premises equipment*. +- [ITU-T J.190] Recommendation ITU-T J.190 (2002), *Architecture of MediaHomeNet that supports cable-based services*. +- [ITU-T X.1111] Recommendation ITU-T X.1111 (2007), *Framework of security technologies for home network*. +- [ATIS 0800002] ATIS 0800002 (2006), *IPTV Architecture Requirements*. +<> +- [DSL TR-094] DSL Forum TR-094 (2004), *Multi-Service Delivery Framework for Home Networks*. +<> +- [HGI] HGI (2006), *Home Gateway Technical Requirements: Release 1*. +<[http://www.homegatewayinitiative.org/publis/HGI\\_V1.0.pdf](http://www.homegatewayinitiative.org/publis/HGI_V1.0.pdf)> + +# 3 Definitions + +This Recommendation defines the following term: + +**3.1 home network:** A home network is the collection of elements that process, manage, transport and store information, thus enabling the connection and integration of multiple computing, control, monitoring, communication and entertainment devices in the home. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------| +| AGAF | Access Gateway Application layer Function | +| AGTF | Access Gateway Transport layer Function | +| AGW | Access Gateway | +| AN | Access Network | +| ASG | Application Service Gateway | +| ASP | Application Service Provider | +| AV | Audio Visual | +| B-NT | Broadband Network Termination | +| CM | Cable Modem | +| CODEC | COder-DECoder | +| DHCP | Dynamic Host Configuration Protocol | +| DNG | Delivery Network Gateway | +| DNGF | Delivery Network Gateway Function | +| DRM | Digital Rights Management | +| DSCP | Differentiated Services Code Point | +| EPG | Electronic Programme Guide | +| EUT | End User Terminal | +| FPD | Functional Processing Device | +| FPD/T | Functional Processing Device and Terminal | +| GW | Gateway | +| HA | Home Access | +| HB | Home Bridge | +| HC | Home Client | +| HD | Home Decoder | +| HE | Head-End | +| HN | Home Network | +| HNS | Home Network Segment | +| IGMP | Internet Group Management Protocol | +| IP | Internet Protocol | +| IPCP | Internet Protocol Control Protocol | + +| | | +|-------|-------------------------------------------------------------------------| +| IPI | Internet Protocol Infrastructure | +| ISP | Internet Service Provider | +| ITF | IPTV Terminal Function | +| LC | Layer-1/2 Converter | +| MLD | Multicast Listener Discovery | +| NAT | Network Address Translation | +| NID | Network Interface Device | +| NSIS | Next Steps In Signalling | +| NT | Network Termination | +| ONT | Optical Network Termination | +| PC | Personal Computer | +| PLC | Power Line Communications | +| PS | Plain old telephone service Splitter | +| QoS | Quality of Service | +| RG | Residential Gateway | +| RQoS | Relative Quality of Service | +| RSVP | Resource ReserVation Protocol | +| SM | Service Module | +| STB | Set-Top Box | +| TCP | Transmission Control Protocol | +| ToS | Type of Service | +| TTL | Time To Live | +| TV | Television set | +| UPnP | Universal Plug and Play | +| VLAN | Virtual Local Area Network | +| VTP/D | VDSL Termination Processing or VDSL Termination Processing and Decoding | +| XSP | Service Provider | +| xTU-R | xDSL remote terminal unit | + +# 5 Conventions + +In this Recommendation: + +- The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. +- The keywords "**is prohibited from**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. + +- The keywords "**is recommended**" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "**is not recommended**" indicate a requirement which is not recommended but which is not specifically prohibited. Thus, conformance with this Recommendation can still be claimed even if this requirement is present. +- The keywords "**can optionally**" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +# 6 Model of the home network + +## 6.1 Concept of layered model + +The home network is an integrated technology ranging from physical transmission to service support. It is difficult to encompass all the aspects of a home network in a single architectural model. This Recommendation adopts a layered model as shown in Figure 6-1. + +![Figure 6-1: The conceptual diagram of layered model. The diagram shows two layers: the Application layer model (top) and the Transport layer model (bottom). The Application layer model includes Primary and Secondary domains, AGW (Access Gateway) with AGAF (Access Gateway Application layer Function), Primary and Secondary terminals, and numbered circles 1-5 representing device functions. The Transport layer model includes IP HN (Home Network) and Non-IP HN, NT (Network Termination), and AGTF (Access Gateway Transport layer Function). A legend defines the symbols: Network category (rectangle), Device (thick rectangle), Device function (option) (dashed circle), and Device function (solid circle). A list on the left defines the numbered circles: 1 Application layer device functions, 2 IP/non-IP terminal, 3 IP terminal, 4 Non IP terminal, 5 Non IP gateway. A code H.622(08)_F6.1 is in the bottom right.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +1 Application layer device functions +2 IP/non-IP terminal +3 IP terminal +4 Non IP terminal +5 Non IP gateway + +**Application layer model** + +Primary domain AGW +AGAF +Secondary domain +Primary terminal +Secondary terminal + +**Transport layer model** + +IP HN +Non-IP HN +NT AGTF + +HN Home Network +NT Network Termination +AGW Access Gateway +AGAF Access Gateway Application layer Function +AGTF Access Gateway Transport layer Function + +□ Network category +▣ Device +○ Device function (option) +● Device function + +H.622(08)\_F6.1 + +Figure 6-1: The conceptual diagram of layered model. The diagram shows two layers: the Application layer model (top) and the Transport layer model (bottom). The Application layer model includes Primary and Secondary domains, AGW (Access Gateway) with AGAF (Access Gateway Application layer Function), Primary and Secondary terminals, and numbered circles 1-5 representing device functions. The Transport layer model includes IP HN (Home Network) and Non-IP HN, NT (Network Termination), and AGTF (Access Gateway Transport layer Function). A legend defines the symbols: Network category (rectangle), Device (thick rectangle), Device function (option) (dashed circle), and Device function (solid circle). A list on the left defines the numbered circles: 1 Application layer device functions, 2 IP/non-IP terminal, 3 IP terminal, 4 Non IP terminal, 5 Non IP gateway. A code H.622(08)\_F6.1 is in the bottom right. + +**Figure 6-1 – The conceptual diagram of layered model** + +The layered function architecture includes two layers: transport function layer and application function layer. The detailed descriptions are presented as follows: + +- The **transport model** describes how the network links clients together and transfers the data packets across the network. The transport model corresponds to three layers: network, data link and physical. That is to say, the functions of physical connection, data link connection and choice of packet switching are realized in this model. +- The **application model** describes the features that allow users to interact with the networks, including defining data formats, designing services and designing interfaces. There are + +many services at present, such as TV gaming, TV education and linear TV. Providing more multimedia services may help drive the widespread adoption of multimedia capabilities, so it is necessary to design more types of services. The data formats of different services vary widely, so data format identification is an important component of the application function model. + +## 6.2 Transport model of the home network + +As shown in Figure 6-2, the home network is composed of IP home network segments using IP and non-IP home network segments using the specific technologies or protocols designed for short-range communication. The gateway between the access network and IP home network segment is called the access GW, while that between the IP home network segment and non-IP home network segment is called the non-IP GW. The terminal may be wireless or wired. + +Refer to [b-ITU-T G.9970] for details of the transport model. + +![Figure 6-2: Transport model of the home network. The diagram shows a flow from left to right: Access Network (orange) connected to a box containing NT (green) and Access GW (green). This is followed by a vertical dashed line labeled IPI-3. Next is the IP Home Network Segment (orange). To its right are vertical dashed lines labeled IPI-1 and IPI-0. Between IPI-1 and IPI-0, there are three parallel paths: the top path has an IP Terminal (green); the middle path has an IP Terminal (green) and a Non-IP GW (green); the bottom path has a Non-IP GW (green). After IPI-0, the middle and bottom paths lead to Non-IP Home Network Segments (orange), which then connect to Non-IP Terminals (green). A direct line from the Access Network (below the NT/Access GW box) connects to a third Non-IP Terminal (green) at the far right.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +Figure 6-2: Transport model of the home network. The diagram shows a flow from left to right: Access Network (orange) connected to a box containing NT (green) and Access GW (green). This is followed by a vertical dashed line labeled IPI-3. Next is the IP Home Network Segment (orange). To its right are vertical dashed lines labeled IPI-1 and IPI-0. Between IPI-1 and IPI-0, there are three parallel paths: the top path has an IP Terminal (green); the middle path has an IP Terminal (green) and a Non-IP GW (green); the bottom path has a Non-IP GW (green). After IPI-0, the middle and bottom paths lead to Non-IP Home Network Segments (orange), which then connect to Non-IP Terminals (green). A direct line from the Access Network (below the NT/Access GW box) connects to a third Non-IP Terminal (green) at the far right. + +Figure 6-2 – Transport model of the home network + +NOTE – The interface "B" between the NT and AGTF is presented in [b-ITU-T G.9970]. + +## 6.3 Application model of the home network + +### 6.3.1 Home network service functional structure + +![Figure 6-3: Application model of the home network. The diagram shows a linear sequence of components: Access NW (text) connected to a green box labeled Access GW, which is connected to a purple box labeled Primary domain, which is connected to a green box labeled Primary terminal, which is connected to a pink box labeled Secondary domain, which is connected to a green box labeled Secondary terminal. Below the Secondary terminal box is the text H.622(08)_F6.3.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +Figure 6-3: Application model of the home network. The diagram shows a linear sequence of components: Access NW (text) connected to a green box labeled Access GW, which is connected to a purple box labeled Primary domain, which is connected to a green box labeled Primary terminal, which is connected to a pink box labeled Secondary domain, which is connected to a green box labeled Secondary terminal. Below the Secondary terminal box is the text H.622(08)\_F6.3. + +Figure 6-3 – Application model of the home network + +For multimedia services on the broadband access network, the service is presented at the terminal device. Usually, this device lies within the home network. Considering that typical multimedia services require network management features such as QoS and security, the same or similar level + +of management and transmission characteristic as the public network such as NGN are required for the network portion connecting terminal devices to the access network. In other words, this portion of the home network, defined as the primary domain, is expected to work as an extension of the access network. + +Many types of consumer electronics devices will also be connected to the home network for exchanging information with other devices or creating services together with other devices; such devices do not need to be considered as a part of the managed public network. For such devices, the home network can be seen as being less integrated with the public network. + +Considering these two cases, there are two major roles for the home network; extending the access network and interconnecting devices in the home network. The portion working as an extension of the access network must be aligned with the technical aspects of the network provider. This Recommendation introduces the concepts of primary and secondary domains to describe these roles. The home network contains two types of terminal devices and network domains as well as the gateway functionality called the access GW. The definition of each device and domain relies on its role rather than its physical configuration. A definition for and explanation of each entity are provided below. + +#### **6.3.1.1 Device** + +A device is a physical entity that implements one or more functions and is sometimes referred to as a "box". There are several types of devices in the home network such as terminal, bridging device and access gateway. + +#### **6.3.1.2 Terminal** + +A terminal is a type of device that can provide a visible service and application, such as presenting content, accepting commands and so on. There are two types of terminals: primary terminals and secondary terminals. The key difference between them is that the former can interact with outside functional entities through the access gateway; the latter needs the support of the former to interact with outside entities. + +##### **6.3.1.2.1 Primary terminal** + +A primary terminal is a terminal device that can interact with the access network or service functionality beyond the access network without being assisted by any other terminal; it is the service end-point where the service from the service provider is terminated. It may present the service to the end user. A primary terminal is required to provide communication capability with a device or function outside the home, thus a set of IP-based protocols is a basic requirement. However, primary terminals need not have IP capability if its communication with outside entities is done through a bridging device that offers protocol translation between IP and non-IP. A terminal device can be categorized as a primary terminal device as long as it has at least application-level transparency and offers synchronized operation with outside functions. + +##### **6.3.1.2.2 Secondary terminal** + +A secondary terminal is a terminal device that has no direct interactive capability with network side entities or needs to rely on a primary terminal to do so. Examples of a secondary terminal are TV displays and cordless telephones. These devices are typically installed by the end user and connected to a primary terminal such as an IPTV-TD and VoIP terminal. + +Even if a secondary terminal does not have IP communication capability, it can communicate and interact with outside functional entities if a primary terminal provides a relay function that bridges the signal between the secondary terminal and the outside function. An AV device that has a digital interface to receive content from IPTV-TD connected to IPTV-NW is an example of this type of interaction with an outside device. + +#### 6.3.1.3 Access gateway + +An access gateway (AGW) is a device that handles traffic to/from the access network as well as transit traffic within the home network. An AGW can optionally terminate or transfer protocols on either side (of the AGW). Some packet header fields such as source/destination address/port, ToS and TTL, can optionally be changed due to, for example, security reasons and/or QoS management at the AGW. + +![Diagram of an Access Gateway (AGW) showing its internal components and external connections.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +The diagram illustrates the internal structure and external connections of an Access Gateway (AGW). The AGW is represented by a large blue rectangle with a dashed red border. Inside, it is divided into two main sections. The top section contains three green boxes labeled 'App.', '...', and '...', and a larger green box labeled 'Network control'. The bottom section contains a grey box labeled 'IP/PPP processing', which is connected to two grey boxes labeled 'WANT' and 'LANT'. External connections include: a yellow box labeled 'Access gateway transport layer function (AGTF)' connected to the top section; a yellow box labeled 'Access gateway application layer function (AGAF)' connected to the 'Network control' box; a teal box labeled 'Access network' containing a white box labeled 'NT' connected to the left side via an interface labeled 'IPI-4'; and a pink box labeled 'IP home network' connected to the right side via an interface labeled 'IPI-3'. A reference code 'H.622(08)\_F6.4' is located at the bottom right. + +NT Network Termination +WANT WAN-side Termination function for layer 1 and 2 +LANT LAN-side Termination function for layer 1 and 2 + +Diagram of an Access Gateway (AGW) showing its internal components and external connections. + +**Figure 6-4 – Definition of access gateway and its component functions** + +Some functions that are typically incorporated into an AGW but not related to traffic handling are not included as access GW functions. A local DHCP server, which provides a local IP address to devices placed in the home network, is an example of this kind of function. + +Since an AGW is typically placed around the demarcation point between the access and home network, it can be implemented as a single device in combination with a network termination. This type of implementation requires the AGW to have the relevant network interface for the access network and makes it difficult to connect the gateway to another access network due to the differences in access network technologies. On the other hand, an AGW can be implemented as a stand-alone device separate from the network termination. While this implementation allows the gateway to be used with various access networks, if the layer 2 and 3 specifications at the user network interface are well harmonized, two separate devices, network termination and AGW, need to be installed in the home. + +Furthermore, the implementation of an AGW could have an impact on the definition of the user network interface. For the AGW combined with the network termination, the position of the user network interface may be limited. Refer to Appendix I and [b-ITU-T G.9970] for more details. + +#### 6.3.1.4 Bridging device + +A bridging device handles traffic within the home network. Since the functionalities of the bridge device are limited below layer 3, a bridging device is almost invisible from the service functional perspective. + +#### 6.3.1.5 Device function + +As defined in this Recommendation, a function is a logically distinguishable entity typically residing within a device, while a device is a physically distinguishable implementation. See Figure 6-5. A device such as a terminal and AGW contains one or more functions. Each function is responsible for a specific layer or category of function such as decoding, security, network control, and so on. + +![Figure 6-5: Device function model. A light blue rounded rectangle labeled 'Device' contains four smaller pink rounded rectangles, each labeled 'Function'.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +A light blue rounded rectangle labeled "Device" contains four smaller pink rounded rectangles, each labeled "Function". + +Figure 6-5: Device function model. A light blue rounded rectangle labeled 'Device' contains four smaller pink rounded rectangles, each labeled 'Function'. + +**Figure 6-5 – Device function model** + +Figure 6-6 shows an example of interaction among the functions within the home network. Each function communicates with a similar function in another physical device. + +![Figure 6-6: Example of a device function in the home network. Three devices are shown: Media Server (dashed border), Primary Terminal, and Secondary Terminal. Functions within each device are connected to corresponding functions in other devices via specific protocols.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +The diagram illustrates three devices: a Media Server (dashed border), a Primary Terminal, and a Secondary Terminal. Each device contains several functions represented by pink rounded rectangles. + +- Media Server:** Contains Media Server, DRM Server, and NW Control functions. +- Primary Terminal:** Contains CODEC, DRM, and Control functions. +- Secondary Terminal:** Contains CODEC, DRM, and Control functions. + +Interactions between functions are as follows: + +- The Media Server's Media Server function sends an "AV stream" to the Primary Terminal's CODEC function. +- The Media Server's DRM Server function sends "DRM control (NW)" to the Primary Terminal's DRM function. +- The Media Server's NW Control function sends "IGMP/MLD" to the Primary Terminal's Control function. +- The Primary Terminal's CODEC function sends data to the Secondary Terminal's CODEC function. +- The Primary Terminal's DRM function sends data to the Secondary Terminal's DRM function. +- The Primary Terminal's Control function sends "UPnP" to the Secondary Terminal's Control function. + +Figure 6-6: Example of a device function in the home network. Three devices are shown: Media Server (dashed border), Primary Terminal, and Secondary Terminal. Functions within each device are connected to corresponding functions in other devices via specific protocols. + +**Figure 6-6 – Example of a device function in the home network** + +A physical device can be defined as a collection of functions. Figure 6-7 shows some devices from this view point. + +![Diagram showing three device configurations: Terminal, Access GW, and Bridge Device. The Terminal contains App., NW Control, NW, and Transmission layers. The Access GW contains App., NW Control, IP/PPP proc., LANT, and WANT layers, with HN and AN interfaces. The Bridge Device contains NW and Trans. layers, with HN interfaces.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +The diagram illustrates three device configurations, each represented by a light blue rectangular box containing several functional layers. + +- Terminal:** A box containing four stacked layers: "App." (three separate boxes), "NW Control", "NW", and "Transmission". +- Access GW:** A box containing five stacked layers: "App." (three separate boxes), "NW Control", "IP/PPP proc.", "LANT", and "WANT". To the left of the box is an arrow labeled "HN" pointing left. To the right of the box is an arrow labeled "AN" pointing right. +- Bridge Device:** A box containing two stacked layers: "NW" (enclosed in a dashed box) and "Trans." (two separate boxes). To the left of the box is an arrow labeled "HN" pointing left. To the right of the box is an arrow labeled "HN" pointing right. + +Diagram showing three device configurations: Terminal, Access GW, and Bridge Device. The Terminal contains App., NW Control, NW, and Transmission layers. The Access GW contains App., NW Control, IP/PPP proc., LANT, and WANT layers, with HN and AN interfaces. The Bridge Device contains NW and Trans. layers, with HN interfaces. + +**Figure 6-7 – Some device configurations** + +##### 6.3.1.5.1 Function decomposition + +Figure 6-8 shows an example of device function decomposition. + +It is not necessary for a function to be the minimum unit within a device. For example, in the case of IPTV, ITF is a comprehensively defined function for IPTV terminal devices. ITF can, however, be divided into more basic functions such as DRM, decoder and EPG. A browser, typically an independent function for Internet services, can be a part of EPG. + +The appropriate level of function granularity may depend on the service. It may be desirable to define more basic functions for some types of services and devices. In other cases, more comprehensive definitions would be better. + +![Figure 6-8: An example of device function decomposition. The diagram shows a hierarchical decomposition of functions within a device (e.g., IPTV-TD). At the top level, the device contains an ITF (Interactive Television Function) block, which is further decomposed into DRM (Digital Rights Management), EPG (Electronic Program Guide), and CODEC (Coder/Decoder). The DRM function is then decomposed into De-SCR (Descrambler) and Key Mngt. (Key Management). Finally, the Key Mngt. function is decomposed into Protocol and Key Storage.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +graph TD + subgraph Device [Device (e.g. IPTV-TD)] + subgraph ITF [ITF] + DRM1[DRM] + EPG[EPG] + CODEC[CODEC] + end + end + DRM1 --> DRM2[DRM] + subgraph DRM2 [DRM] + De-SCR[De-SCR] + KeyMngt1[Key Mngt.] + end + KeyMngt1 --> KeyMngt2[Key Mngt.] + subgraph KeyMngt2 [Key Mngt.] + Protocol[Protocol] + KeyStorage[Key Storage] + end + +``` + +Figure 6-8: An example of device function decomposition. The diagram shows a hierarchical decomposition of functions within a device (e.g., IPTV-TD). At the top level, the device contains an ITF (Interactive Television Function) block, which is further decomposed into DRM (Digital Rights Management), EPG (Electronic Program Guide), and CODEC (Coder/Decoder). The DRM function is then decomposed into De-SCR (Descrambler) and Key Mngt. (Key Management). Finally, the Key Mngt. function is decomposed into Protocol and Key Storage. + +**Figure 6-8 – An example of device function decomposition** + +This Recommendation allows a function to be divided into one or more basic functions. The following are examples of device function decomposition: + +- Comprehensive function: ITF and DNGF. +- Intermediate level of function: DRM. +- Basic functions: Browser and CODEC. + +The function hierarchy may depend on the service. The detailed structure of function hierarchy is for further study. + +#### 6.3.1.6 Domain + +A domain is a logically defined area of the home network. There are two kinds of domain; primary domain and secondary domain, in this model. Each domain can be decomposed into IP sub-domain and non-IP sub-domain, if necessary. + +##### 6.3.1.6.1 Primary domain + +A primary domain is the logically defined area of the home network that interconnects the primary terminal and the access GW. Traffic on the primary domain is associated with traffic to/from the access GW. + +The devices and traffic related to the primary domain are required to be configured to be reachable to/from the access network, directly or indirectly (via NAT). + +The general and fundamental requirement placed on the primary domain is to provide the same level of transmission performance and characteristics such as QoS, security and manageability as provided by the access network, since the primary domain is expected to work as an extension of it. A well-managed and configured network is an important aspect of the primary domain. + +##### 6.3.1.6.2 Secondary domain + +A secondary domain is a logically defined area of the home network that interconnects terminals. + +The devices and traffic dedicated to the secondary domain do not need to be configured to be reachable to/from the access network. For example, local assignment or generation of IP addresses, if IP is used for network transmission, is enough for this domain. + +##### 6.3.1.6.3 Domain overlap + +It is not necessary to physically isolate the domains from each other. Combining domains into the single physical network segment may mitigate the complexity of wiring and cost of deployment, and hence benefit the end users. In particular, considering the proliferation of IP technologies in the area of broadband infrastructure, adopting IP for both primary and secondary domains may be the most likely situation. For this reason, it may be useful to consider the possibility of domain overlap where the same transmission medium and bridging device are shared by the two domains. In this definition, it is not necessary that the domains overlap completely. + +This Recommendation defines domain overlap. Figure 6-9 shows the logical concept of domain overlap. + +![Figure 6-9: Definition of domain overlap. A diagram showing three overlapping domains: a pink 'Primary Domain' on the left, a yellow 'Secondary Domain' on the right, and a green 'Primary & Secondary Domain' in the center that overlaps with both the primary and secondary domains.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Figure 6-9: Definition of domain overlap. A diagram showing three overlapping domains: a pink 'Primary Domain' on the left, a yellow 'Secondary Domain' on the right, and a green 'Primary & Secondary Domain' in the center that overlaps with both the primary and secondary domains. + +Figure 6-9 – Definition of domain overlap + +Figure 6-10 shows an example of domain overlap. The access GW, primary terminal and secondary terminal are connected via a bridging device. The data flow between the access GW and primary terminal (the blue arrow in the figure) is considered to be a part of the primary domain. The data flow between the primary and secondary terminals (the red arrow in the figure) is considered to be a part of secondary domain. In this example, both data flows share the same network link between the bridging device and primary terminal. This part of the network belongs to an overlapped domain, the overlap of primary and secondary domains. + +![Figure 6-10: An example of domain overlap. A network diagram showing a 'Primary Terminal', a 'Secondary Terminal', a 'Bridging Device', and an 'Access GW' connected to an 'AN'. A blue arrow labeled 'Data flow from AN' points from the Access GW to the Primary Terminal. A red arrow labeled 'Data flow between Terminals' points from the Primary Terminal to the Secondary Terminal. A dashed green box labeled 'Overlapped Domain' encloses the Primary Terminal and the link between the Primary Terminal and the Bridging Device, indicating that this part of the network is shared by both domains.](21ad58fee90f2be50708ff541d225507_img.jpg) + +Figure 6-10: An example of domain overlap. A network diagram showing a 'Primary Terminal', a 'Secondary Terminal', a 'Bridging Device', and an 'Access GW' connected to an 'AN'. A blue arrow labeled 'Data flow from AN' points from the Access GW to the Primary Terminal. A red arrow labeled 'Data flow between Terminals' points from the Primary Terminal to the Secondary Terminal. A dashed green box labeled 'Overlapped Domain' encloses the Primary Terminal and the link between the Primary Terminal and the Bridging Device, indicating that this part of the network is shared by both domains. + +Figure 6-10 – An example of domain overlap + +Therefore, placing two domains on the single physical network segment could cause resource contention between traffic belonging to the domains and introduce complexity to the network devices. The performance degradation due to resource contention is one of the issues to be addressed. + +### 6.3.2 Operational model + +There are some cases where functionalities in both primary and secondary domains interact with each other. For example, a secondary terminal is defined to interact with functional entities with the help of a primary terminal. This clause provides three operational models as shown in Figure 6-11. + +![Figure 6-11: Interaction of primary and secondary domains. The diagram shows three models: a) Separated model, b) Proxy model, and c) Transparent model. Each model shows the interaction between an Access network, a Primary domain, and a Secondary domain. The Access network contains an Access GW, Network, and Transportation layers. The Primary domain contains a Primary terminal with Application, Network, and Transportation layers. The Secondary domain contains a Secondary terminal with Application, Network, and Transportation layers. In the Separated model, the Primary terminal acts as a proxy for the Secondary terminal. In the Proxy model, the Primary terminal acts as a proxy for the Secondary terminal. In the Transparent model, the Primary terminal acts as a relay for the Secondary terminal.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates three operational models for the interaction between primary and secondary domains within an access network. At the top, a horizontal bar identifies the components: Access network (Access GW), Primary domain (Primary terminal), and Secondary domain (Secondary terminal). Below this, three sub-diagrams show the internal protocol stacks and interaction paths: + +- a) Separated model:** The Access network (Network/Transportation) connects to the Primary terminal (Application/Network/Transportation), which in turn connects to the Secondary terminal (Application/Network/Transportation). The Primary terminal acts as a proxy for the Secondary terminal. +- b) Proxy model:** Similar to the separated model, but with a curved arrow indicating that the Primary terminal's Application layer is specifically acting as a proxy for the Secondary terminal's Application layer. +- c) Transparent model:** The Access network connects to the Primary terminal, which acts as a relay for the Secondary terminal. The Primary terminal's Network layer is shown passing traffic from the Secondary terminal's Application layer. + +H.622(08)\_F6.11 + +Figure 6-11: Interaction of primary and secondary domains. The diagram shows three models: a) Separated model, b) Proxy model, and c) Transparent model. Each model shows the interaction between an Access network, a Primary domain, and a Secondary domain. The Access network contains an Access GW, Network, and Transportation layers. The Primary domain contains a Primary terminal with Application, Network, and Transportation layers. The Secondary domain contains a Secondary terminal with Application, Network, and Transportation layers. In the Separated model, the Primary terminal acts as a proxy for the Secondary terminal. In the Proxy model, the Primary terminal acts as a proxy for the Secondary terminal. In the Transparent model, the Primary terminal acts as a relay for the Secondary terminal. + +Figure 6-11 – Interaction of primary and secondary domains + +#### 6.3.2.1 Separated model + +In the separated model, the protocol operations in primary and secondary domains run independently. + +#### 6.3.2.2 Proxy model + +In the proxy model, the protocol operations in primary and secondary domains are closely related, but technically run independently. The operations in both domains are synchronized, but the actual protocols are different. This model allows both terminal devices to use their own protocols and terminals, particularly secondary terminals, to interact with functional entities beyond the access network. In this operation, the primary terminal acts as a proxy device to the secondary terminal. The secondary terminal is not required to have global reachability. + +#### 6.3.2.3 Transparent model + +The protocol operations in primary and secondary domains are closely related. For example, primary terminals act as a relay device for secondary terminals or primary terminals simply transfer a protocol to/from secondary terminals. + +### 6.3.3 Interfaces with outside networks + +The home network is generally expected to work with outside networks for establishing communication with outside devices or acquiring contents from outside sources. As shown in + +Figure 6-12, there are two kinds of outside network that are expected to work with the home network. + +![Diagram of interfaces with outside network showing connections between Broadcast Network, Access Network, Access GW, Primary Domain, Primary Terminal, Secondary Domain, and Secondary Terminal.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg) + +The diagram illustrates the interfaces with outside networks. On the left, a green box labeled 'Access Network' is connected to a light blue box labeled 'Access GW'. Above the 'Access Network' is a cyan box labeled 'Broadcast Network'. The 'Access GW' is connected to a pink box labeled 'Primary Domain'. The 'Broadcast Network' has connections to the 'Access GW', the 'Primary Domain', a light blue box labeled 'Primary Terminal', a yellow box labeled 'Secondary Domain', and a light blue box labeled 'Secondary Terminal'. The 'Primary Domain' is connected to the 'Primary Terminal'. The 'Primary Terminal' is connected to the 'Secondary Domain', which is in turn connected to the 'Secondary Terminal'. + +Diagram of interfaces with outside network showing connections between Broadcast Network, Access Network, Access GW, Primary Domain, Primary Terminal, Secondary Domain, and Secondary Terminal. + +**Figure 6-12 – Interfaces with outside network** + +The access network provides basic communication services between the home network and service nodes/functions provided by network operators or service providers. The boundary between the access network and home network is outside the scope of this Recommendation. All traffic coming from/going to the access network shall be transferred through the access GW function. + +The broadcast network includes terrestrial and satellite. These networks provide one-way transmission of broadcast signals into the home network. Since the radio signal is available almost anywhere in the home, a broadcast network can be connected to the access GW function, as well as the primary and secondary terminal functions. + +# 7 QoS + +The functionality that realizes QoS on the IP network is important to accomplish stable quality for the case of offering streaming-based multimedia services on the IP Network. Two methods to provide QoS can be identified: class-based QoS and session-based QoS. [ITU-T J.190] describes UPnP, a kind of session-based QoS mechanism, while [DSL TR-094], [b-DSL TR-133] and [HGI] describe class-based QoS. The applicability of these QoS mechanisms in the IP home network segment needs consideration of application requirements as well as network functions of the access and home network. + +NOTE – It is known that at least [ITU-T J.190] and [DSL TR-094] use different QoS technologies at the time at which this Recommendation was created. Therefore, it is not appropriate to specify a common QoS mechanism without first confirming its necessity. Further study on this issue is needed for the purpose of specifying unique QoS mechanism in the common home network architecture. + +In addition to the above QoS solutions described in existing documents, there may be some emerging solutions as listed below that might be applicable to QoS in the home network: + +- NSIS QoS NSLP. +- UPnP QoS. + +## 7.1 Class-based QoS + +### 7.1.1 Overview of class-based QoS + +Traffic is aggregated into a small number of classes, typically 4-8 classes. The packets belonging to the same class are given the same treatment at the network devices. This means that each packet experiences the same transmission characteristic regardless of the application data contained in it. + +Class-based QoS introduces less complexity to the home network than the session-based QoS mechanism. It can work without signalling among the terminals and network devices. Each device is not required to have QoS signalling capability. Also, no network device is required to maintain application status such as call set-up and teardown. Less complexity helps to minimize the costs of traffic management not only by the network provider but also by the end user. The key features of class-based QoS are summarized below. + +- **Less complexity** +Class-based QoS does not require any signalling mechanism to operate. Packets are sent with relevant marking. The network devices read the information and transfer the packet with relevant priority. Eliminating the signalling mechanism increases the possibility for interoperability with other systems. For example, if there is a network device that is unable to understand the priority information, the packet can be transferred on the best effort basis and it remains possible for other devices to transfer the same packet with appropriate priority. This situation slightly degrades the packet transmission quality; however impacts on the other network segments are limited. +- **Scalability** +Unlike the session-based QoS, the network devices running the class-based QoS mechanism are not required to maintain the session status of each application such as call set-up and teardown. Instead of maintaining each session status, the network devices are simply required to classify packets based on the attached information. +This is an advantage for the network devices placed in the core network since they must deal with a huge number of traffic flows. It is also attractive for the home network in which complicated multimedia applications will transfer many packet streams. +- **Priority-based mechanism** +Class-based QoS can define relative priority among several applications. This means that the traffic given a higher priority can experience better treatment than the traffic with lower priority. Relative priority is reasonable since it is difficult to guarantee the bandwidth requested by an application. In other words, it is sufficient to establish relative priority and have a clear policy or consensus on the service priorities among the applications. + +### 7.1.2 Number of classes + +The number of classes is one of the key parameters of class-based QoS. Standards exist for class-based QoS mechanisms and the typical number of classes ranges from 4 to 8. Among these classes, traffic such as VoIP and streaming video is typically given a higher priority than conventional data service such as Internet and e-mail. Some standards state that some data services are to be given better treatment than best effort traffic. + +The complexity of the home network configuration increases the demand for classes. For example, the home network that handles a number of different types of application needs to have more traffic classes than the home network that handles a single application. In the same way, the home network that handles both downstream traffic from the access network and in-home traffic that circulates only in the home network needs to differentiate the priorities of the two traffic types. + +The number of classes is related to the physical implementation of network devices. The network device assigns packets to its queues according to the priority. For example, higher priority class packets are assigned to queues with higher priority. + +### 7.1.3 Priority marking methods + +The service class of each packet is expressed by the information placed in the header field of the packet. This can be done either in layer 2 or layer 3. + +Layer 2 marking schemes can use techniques such as VLAN priority defined in [b-IEEE 802.1Q]. Transmission technologies such as PLC and wireless LAN have their own technique (Note). DSCP is a layer 3 level technique defined in [b-IETF RFC 2474], [b-IETF RFC 2597] and [b-IETF RFC 2598]. L2 and L3 schemes can be used in combination. This allows network devices that are blind to layer 3 headers to apply the relevant policy. + +There are some discussions about the use of these marking techniques. Refer to documents such as [HGI] and [b-DSL TR-133] for further information. + +NOTE – There is an informative annex describing user priorities and traffic classes in [b-IEEE 802.1D]. It also provides an example of class-based QoS marking. + +## 7.2 Session-based QoS + +In session-based QoS, every terminal or application is required to reserve the necessary resources by the signalling mechanism. RSVP [b-IETF RFC 2205] is a typical example of such a mechanism. + +NOTE – [b-UPnP-QoS] also provides a session-based QoS mechanism. + +It is possible that the terminal or application knows whether the requested resource is available or not. In other words, if the resource reservation process has succeeded, the transmission quality of associated service is guaranteed. Session-based QoS has the following problems: + +- Some network devices are unaware of signalling protocol. +- Network devices need a complicated mechanism. +- Additional session set-up time introduced by the resource reservation process. + +## 7.3 QoS in primary and secondary domains + +Since the primary domain works as an extension of the access network, a QoS mechanism is recommended to be provided for the primary domain. This will help to provide a level of transmission quality as provided in the access NW. Some applications in the secondary domain may require priority higher than best effort traffic. In this case, the secondary domain is recommended to have a relevant QoS mechanism. + +As described in clause 6.3.1.6.3, it is possible that primary and secondary domains share the same physical infrastructure. This means that traffic belonging to these two different domains could compete for network resources, such as bandwidth. This situation causes a problem with QoS management. It is generally believed that a certain type of service (e.g., VoIP) has priority over other services (e.g., data services) in the QoS managed network. In this concept, traffic differentiation for the same service category is not meaningful. In the case of domain overlap, resource management is also necessary between services belonging to different domains even if these services have the same basic characteristics. [HGI] has some requirements on service differentiation based on types of traffic such as downstream, upstream and transit. Among these traffic types, downstream and upstream correspond to the primary domain, while transit corresponds to the secondary domain. These requirements may be applicable to the situation of the overlapped domain. + +The possibility of domain overlap depends on the implementation as well as practice. If domain overlap is likely, each domain is recommended to operate so as not to negatively impact the other. + +NOTE – The relative priority of traffic in primary and secondary domains is an issue that needs to be addressed in future. + +# 8 Management Functionality + +Customer premises equipment in the home network is recommended to be appropriately managed by the network operator, service provider and end user. + +There are two types of devices in the home network, managed device and unmanaged device, if the devices are categorized by the management feature. Managed devices are defined here as devices managed by the network or service provider using a remote management protocol; unmanaged devices are defined as the other devices. In this context, a device managed only by its IP address by the network provider is considered to be an unmanaged device. For managed devices, the type of device managed and management items depends on the case. + +It is recommended that the access GW and primary terminal be managed by the network provider or service provider because these devices are closely related to the network provider or service provider. Since the secondary domain is a more independent part of the home network relative to the access network, it is likely to be managed by the end user rather than the network provider or service provider. + +There are several management protocols and mechanisms available in the industry. [b-DSL TR-069] and SNMP are examples of the remote management protocols. Refer to the related documents for details. + +NOTE – Some different management mechanisms have been identified between [ITU-T J.190] and [DSL TR-094] at the time of creating this Recommendation. Therefore, it is not appropriate to seek a common set of management functions without first identifying the necessity for this. + +## 8.1 IP address management + +IP address management is the foundation of IP communication. If a device is to be IP-reachable from the access network, its address must be managed by the network provider. The IP address of the device is assigned by the network provider directly or by the access GW locally. In the latter case, IP datagrams from the device are translated by the NAT/NAPT functionality in the access GW. + +The secondary domain devices can organize a network segment that is independent of other network segments. Such network segments are isolated from the access NW. In this case, IP address assignment from the access NW is not expected. + +All the equipment/devices, including access GW and non-IP GW connected to IP home network segment, are assigned unique IP addresses. + +### 8.1.1 Network-assigned IP addresses + +In this scheme, the server located in the network provider assigns an IP address to the terminal devices. Indirectly assigned IP address such as RA for IPv6, in which the network provider provides a block of addresses instead of an individual address to the terminal device, is also included in this scheme. The following address assignment mechanisms are available for this scheme: + +- DHCP (IPv4). +- IPCP. +- RA. + +Figure 8-1 shows the network assigned IP address scheme. + +![Diagram of the network assigned IP address scheme. It shows three main components: 'Address Management Function' (left), 'AGW' (center), and 'Terminal & Device' (right). The AGW contains two sub-components: 'AGAF' (top) and 'AGTF' (bottom). A double-headed arrow labeled 'Address Management Protocol' connects the 'Address Management Function' to the 'AGW'. A single-headed arrow points from the 'AGW' to the 'Terminal & Device'.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg) + +Diagram of the network assigned IP address scheme. It shows three main components: 'Address Management Function' (left), 'AGW' (center), and 'Terminal & Device' (right). The AGW contains two sub-components: 'AGAF' (top) and 'AGTF' (bottom). A double-headed arrow labeled 'Address Management Protocol' connects the 'Address Management Function' to the 'AGW'. A single-headed arrow points from the 'AGW' to the 'Terminal & Device'. + +**Figure 8-1 – Network assigned IP address** + +The address management function in the network provider provides an IP address to each terminal or device in the HN. At the AGW, the AGTF handles the address management protocol. It is also possible for the AGAF to handle this assignment if necessary. + +NOTE – The AGW's functions related to these mechanisms, such as the relay agent, are for further study. + +This Recommendation does not recommend static IP address assignment by the user. For applications that require static IP address assignment, the above dynamic mechanisms are recommended to be used. + +### 8.1.2 Locally-assigned IP addresses + +The server installed in the customer premises assigns IP addresses in the locally-assigned IP address scheme. The following address assign mechanism is available for this scheme: + +- DHCP + +This DHCP can optionally be installed within the access GW. If the access GW assigns a local IP address to a terminal or device in the HN, the access GW is required to provide NAT/NAPT functionality to the device. + +This mechanism can be used for assigning private IP addresses but is not recommended to be used for assigning public IP addresses. + +Figure 8-2 shows the locally-assigned IP address scheme. + +![Diagram of the locally-assigned IP address scheme. It shows three main components: 'Address management function' (left, dashed box), 'AGW' (center), and 'Terminal and device' (right). The AGW contains three sub-components: 'AGAF' (top), 'Address repository' (middle), and 'AGTF' (bottom). A single-headed arrow points from the 'AGW' to the 'Terminal and device', labeled 'Address management protocol (HN)'. A small label 'H.622(08)_F8.2' is at the bottom right.](2119293733c74fc64de88aefd597f4bb_img.jpg) + +Diagram of the locally-assigned IP address scheme. It shows three main components: 'Address management function' (left, dashed box), 'AGW' (center), and 'Terminal and device' (right). The AGW contains three sub-components: 'AGAF' (top), 'Address repository' (middle), and 'AGTF' (bottom). A single-headed arrow points from the 'AGW' to the 'Terminal and device', labeled 'Address management protocol (HN)'. A small label 'H.622(08)\_F8.2' is at the bottom right. + +**Figure 8-2 – Locally-assigned IP address** + +IP addresses assigned to the terminals and devices are stored or generated in the address repository in the AGW. Such IP addresses usually fall within the local administration scope. + +# **9 Security** + +The access GW is recommended to provide security functionality, i.e., a firewall, in order to prevent external illegal access to the home network. Moreover, it will improve the security of the customer premises to install NAT in the access GW. + +[ITU-T X.1111], which defines the framework of home network security, identifies security threats and requirements. Please refer to [ITU-T X.1111] and related documents for details. + +# Appendix I + +## Components in home network documents + +(This appendix does not form an integral part of this Recommendation) + +## I.1 Introduction + +Home network standards/Recommendations have already been published by ITU-T SGs and SDOs. The different terminologies, which are sometimes defined or used for the same or similar device/network segment/interface, complicate any comparison of home network architectures and functional components. + +This appendix provides a comparison of these standards/Recommendations and the relevant interpretation of components. + +## I.2 Access GW + +A list of devices corresponding to the AGW as defined in other documents is shown in Tables I.1 and I.2. Figure I.1 gives the comparison of these devices. Table I.3 gives the internal functional entities placed in AGW. + +**Table I.1 – List of devices corresponding to AGW combined with a network termination** + +| Device | Document where defined | Note | +|---------------------|------------------------|--------------------------------------------------| +| VTP | [ITU-T H.610] | – | +| VTP/D | [ITU-T H.610] | Combined with terminal functionality called FPD. | +| HA | [ITU-T J.190] | – | +| Secure home gateway | [ITU-T X.1111] | – | +| HG | [HGI] | – | + +**Table I.2 – List of devices corresponding to AGW not combined with a network termination** + +| Device | Document where defined | Note | +|--------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| DNG | [ATIS 0800002] | DNG is connected to NID, in case of DSL, or ONT, case of optical access network. | +| RG | [DSL TR-094] | RG is connected to B-NT for DSL access network. [DSL TR-094] allows implementation of a combination of B-NT and RG as a single device. | + +![Figure I.1 – Configuration of home gateway in other documents. This figure shows six different network architecture diagrams for home gateways. 1. '[One box model of access GW]': A single box contains 'NT' and 'Access GW'. It connects to a 'U-interface' on the left and an 'IP home network segment' (cloud) on the right via 'IPI-3'. The 'IPI-4' interface is also indicated. 2. '[Two boxes model of access GW]': Two separate boxes, 'NT' and 'Access GW', are connected in series. 'NT' connects to the 'U-interface' and 'Access GW' connects to the 'IP home network segment' via 'IPI-3'. The 'IPI-4' interface is between them. 3. '[ATIS 0800002]': Two boxes, 'NID' and 'ONT', connect to a 'DNG' (Digital Network Gateway). 'DNG' connects to an 'HNS' (Home Network Segment) cloud via 'IPI-3'. The 'U-interface' is on the left and 'IPI-4' is between the ONT and DNG. 4. '[DSL TR-094]': A 'B-NT' (Broadband Network Terminal) box contains 'xTU-R' and 'SM'. It connects to a 'U-R2' interface on the left and an 'RG' (Residential Gateway) on the right via 'T_PDN'. 'RG' connects to a 'Premises distribution' cloud via 'T_CN'. 5. '[ITU-T H.610]': A 'VTP/D' (Voice Terminal Processor/Device) box connects to a 'U-R2' interface on the left and a 'Digital customer premises distribution network' cloud on the right via 'T_CN'. 6. '[ITU-T J.190]': A large box contains four sub-components: 'HA' (Home Automation), 'PS' (Power Supply), 'CM' (Cable Modem), and 'LC' (LAN Controller). It connects to an 'IPNet2Home domain' cloud on the right. A small label 'H.622(08)_FI.1' is at the bottom right of the diagram area.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +Figure I.1 – Configuration of home gateway in other documents. This figure shows six different network architecture diagrams for home gateways. 1. '[One box model of access GW]': A single box contains 'NT' and 'Access GW'. It connects to a 'U-interface' on the left and an 'IP home network segment' (cloud) on the right via 'IPI-3'. The 'IPI-4' interface is also indicated. 2. '[Two boxes model of access GW]': Two separate boxes, 'NT' and 'Access GW', are connected in series. 'NT' connects to the 'U-interface' and 'Access GW' connects to the 'IP home network segment' via 'IPI-3'. The 'IPI-4' interface is between them. 3. '[ATIS 0800002]': Two boxes, 'NID' and 'ONT', connect to a 'DNG' (Digital Network Gateway). 'DNG' connects to an 'HNS' (Home Network Segment) cloud via 'IPI-3'. The 'U-interface' is on the left and 'IPI-4' is between the ONT and DNG. 4. '[DSL TR-094]': A 'B-NT' (Broadband Network Terminal) box contains 'xTU-R' and 'SM'. It connects to a 'U-R2' interface on the left and an 'RG' (Residential Gateway) on the right via 'T\_PDN'. 'RG' connects to a 'Premises distribution' cloud via 'T\_CN'. 5. '[ITU-T H.610]': A 'VTP/D' (Voice Terminal Processor/Device) box connects to a 'U-R2' interface on the left and a 'Digital customer premises distribution network' cloud on the right via 'T\_CN'. 6. '[ITU-T J.190]': A large box contains four sub-components: 'HA' (Home Automation), 'PS' (Power Supply), 'CM' (Cable Modem), and 'LC' (LAN Controller). It connects to an 'IPNet2Home domain' cloud on the right. A small label 'H.622(08)\_FI.1' is at the bottom right of the diagram area. + +**Figure I.1 – Configuration of home gateway in other documents** + +**Table I.3 – Internal functional components related to access GW and NT** + +| Internal functional component | Document where defined | Note | +|-------------------------------|------------------------|-------------------------------------------------------------------------------------| +| DNGF | [ATIS 0800002] | Internal function contained in DNG (access GW). | +| xTU-R | [DSL TR-094] | Network termination function for DSL access network. | +| SM | [DSL TR-094] | – | +| VTU-R | [ITU-T H.610] | Network termination function for VDSL access network. | +| ATM Proc. | [ITU-T H.610] | – | +| Functional processing | [ITU-T H.610] | – | +| CM | [ITU-T J.190] | Network termination function for cable access network. | +| PS | [ITU-T J.190] | This function includes security, management, provisioning and addressing functions. | +| LC | [ITU-T J.190] | Bridging function for IPNet2Home. | + +## I.3 Terminal + +This Recommendation defines two types of terminal, primary and secondary terminals, according to the role and function in the home network. This clause categorizes terminal devices defined in other documents into these two types. Tables I.4 and I.5 are lists for primary and secondary terminals, respectively. + +**Table I.4 – List of terminals that can be primary terminals** + +| Terminal | Document where defined | Note | +|----------|------------------------|-------------------------------------------------| +| HNED | [ATIS 0800002] | – | +| FPD | [DSL TR-094] | FPD needs to have IP communication capability. | +| FPD/T | [DSL TR-094] | – | +| FPD | [ITU-T H.610] | – | +| VTP/D | [ITU-T H.610] | Combined with gateway functionality called VTP. | +| HD | [ITU-T J.190] | – | +| Type A | [ITU-T X.1111] | Controlling capability for type B or C. | +| Type B | [ITU-T X.1111] | Bridge to type C. | + +**Table I.5 – List of terminals that can be secondary terminals** + +| Terminal | Document where defined | Note | +|----------------|------------------------|-----------------------------------------| +| HNED | [ATIS 0800002] | – | +| EUT | [DSL TR-094] | – | +| Home appliance | [ITU-T H.610] | – | +| HD | [ITU-T J.190] | – | +| Type A | [ITU-T X.1111] | Controlling capability for type B or C. | +| Type C | [ITU-T X.1111] | Provide services to other devices. | + +## I.4 Other devices + +Device types are not limited to AGWs and terminals. A typical home network consists of other types such as a gateway device connecting IP and non-IP network segments. Table I.6 gives a list of devices not categorized as either AGW or terminal. + +**Table I.6 – List of other devices** + +| Terminal | Document where defined | Corresponding device | Note | +|----------|------------------------|----------------------|--------------------------------------------------------------------| +| ASG | [DSL TR-094] | Non-IP gateway | It is possible to implement an ASG in a physical device as an RG. | +| HB | [ITU-T J.190] | | Bridging device within IPNet2Home (IP-based home network segment). | +| HC | [ITU-T J.190] | Non-IP gateway | – | + +## I.5 Network domain + +This Recommendation defines two types of domain, primary and secondary domain, according to the role and function in the home network. This clause categorizes network segment/domain defined in other documents into these two types. Tables I.7 and I.8 are lists for primary and secondary domains, respectively. + +**Table I.7 – A list of network segments/domains that can be primary domains** + +| Domain/segment | Document where defined | Note | +|-----------------------|------------------------|----------------------------------------------------------------------------------------------| +| Premises distribution | [DSL TR-094] | – | +| SP managed (M) domain | [DSL TR-094] | M domain can overlap with U domain. | +| Premises distribution | [ITU-T H.610] | – | +| IPNet2Home domain | [ITU-T J.190] | – | +| Proprietary domain | [ITU-T J.190] | – | +| GSD | [ITU-T J.190] | A network segment that ensures QoS for streaming services by [b-UPnP QoS]. | +| ASD | [ITU-T J.190] | A network segment in which devices are required to be authenticated by the network operator. | +| AOD | [ITU-T J.190] | A network segment for the contents on portable/mobile equipment. | +| BED | [ITU-T J.190] | A network segment for non-QoS sensitive contents. | +| M-Domain | [ITU-T J.190] | The set of elements compliant with IPNet2Home provisioning and management specifications. | +| Q-Domain | [ITU-T J.190] | The set of elements compliant with IPNet2Home QoS specifications. | +| S-Domain | [ITU-T J.190] | The set of elements compliant with IPNet2Home security specifications. | +| MP-Domain | [ITU-T J.190] | – | +| QP-Domain | [ITU-T J.190] | – | +| SP-Domain | [ITU-T J.190] | – | + +**Table I.8 – A list of network segments/domains that can be secondary domains** + +| Domain/segment | Document where defined | Note | +|-----------------------------------|------------------------|----------------------------------------------------------------------------------------------| +| Supplementary application network | [DSL TR-094] | [DSL TR-094] allows the use of premises distribution for this purpose. | +| Customer managed (U) domain | [DSL TR-094] | U domain can overlap with M domain. | +| Proprietary domain | [ITU-T J.190] | – | +| GSD | [ITU-T J.190] | A network segment that ensures QoS for streaming services by [b-UPnP QoS]. | +| ASD | [ITU-T J.190] | A network segment in which devices are required to be authenticated by the network operator. | + +**Table I.8 – A list of network segments/domains that can be secondary domains** + +| Domain/segment | Document where defined | Note | +|----------------|------------------------|--------------------------------------------------------------| +| AOD | [ITU-T J.190] | A network segment for contents on portable/mobile equipment. | +| BED | [ITU-T J.190] | A network segment for non-QoS sensitive contents. | +| MP-Domain | [ITU-T J.190] | – | +| QP-Domain | [ITU-T J.190] | – | +| SP-Domain | [ITU-T J.190] | – | + +## I.6 Interfaces + +Table I.9 gives a list of interfaces defined in home network documents. + +**Table I.9 – List of interfaces** + +| Interface | Document where defined | Corresponding device | Note | +|----------------|------------------------|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| U | [ATIS 0800002] | IPI-4 | – | +| IPI-4a/b/c/d | [ATIS 0800002] | IPI-4 | IPI-4a: Defined for copper access network (DSL).
    IPI-4b: Defined for optical access network.
    IPI-4c: Defined for optical access network with coaxial interface.
    IPI-4d: Defined for wireless access network. | +| IPI-3a/b/c/d/e | [ATIS 0800002] | IPI-3 | IPI-3a: Defined for PLC-based home network.
    IPI-3b: Defined for Ethernet.
    IPI-3c: Defined for copper home network (HomePNA).
    IPI-3d: Defined for coaxial home network.
    IPI-3e: Defined for wireless home network. | +| IPI-1a/b/c/d/e | [ATIS 0800002] | IPI-1 | IPI-1a: Defined for PLC-based home network.
    IPI-1b: Defined for Ethernet.
    IPI-1c: Defined for copper home network (HomePNA).
    IPI-1d: Defined for coaxial home network.
    IPI-1e: Defined for wireless home network. | +| IPI-0 | [ATIS 0800002] | IPI-0 | – | +| U-R | [DSL TR-094] | IPI-4 | U-R and U-R2 are distinguishable only when the access network supports both broadband and POTS service. | +| U-R2 | [DSL TR-094] | IPI-4 | U-R and U-R2 are distinguishable only when the access network supports both broadband and POTS service. | + +**Table I.9 – List of interfaces** + +| Interface | Document where defined | Corresponding device | Note | +|------------------|-------------------------------|-----------------------------|------------------------------------------------------------------------------------------| +| T PDN | [DSL TR-094] | – | This interface is visible only when the RG and B-NT are implemented in separate devices. | +| T CN | [DSL TR-094] | IPI-3 | – | +| R | [DSL TR-094] | IPI-0 | – | +| U-R | [ITU-T H.610] | IPI-4 | – | +| U-R2 | [ITU-T H.610] | IPI-4 | – | +| T CN | [ITU-T H.610] | IPI-3 | – | +| R | [ITU-T H.610] | IPI-0 | – | + +# Bibliography + +- [b-ITU-T G.9970] Recommendation ITU-T G.9970 (2009), *Generic home network transport architecture*. +- [b-DSL TR-069] DSL Forum TR-069 (2004), *CPE WAN Management Protocol*. +<> +- [b-DSL TR-133] DSL Forum TR-133 (2005), *DSLHome™ TR-064 Extensions for Service Differentiation*. +<> +- [b-IEEE 802.1D] IEEE 802.1D (2004), *IEEE Standard for Local and metropolitan area networks Media Access Control (MAC) Bridges*. +<> +- [b-IEEE 802.1Q] IEEE 802.1Q (2005), *IEEE standard for local and metropolitan area networks virtual bridged local area networks*. +<> +- [b-IETF RFC 2474] IETF RFC 2474 (1998), *Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers*. +<> +- [b-IETF RFC 2205] IETF RFC 2205 (1997), *Resource ReSerVation Protocol (RSVP) – Version 1 Functional Specification*. +<> +- [b-IETF RFC 2597] IETF RFC 2597 (1999), *Assured Forwarding PHB Group*. +<> +- [b-IETF RFC 2598] IETF RFC 2598 (1999), *An Expedited Forwarding PHB*. +<> +- [b-UPnP-QoS] UPnP (2006), *UPnP QoS Architecture:2*. +<> + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a521b0c6c59ba658d4be29b5a6a0ef0bba68ee29 --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2c31252e893582c3a4c74bfc01c4f5bdbe421b85002556c16e806848d9b44a5 +size 33611 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..478dcc2c87286e478c195de5fddbed7825f3e4ef --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d212b462cebf1a8d864ef90da9b5a6a57c3a60094975ffdb31913982ce3d4a4 +size 42660 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..218a7b6f54f8cf947093273b1a36b2db65c8be48 --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c27bcc2562cd758226062bc7769e8d56b94f35c1f296878845f22cd469c68706 +size 58201 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da30f6f5b0ea1a5c1daaf9efbc174487cf71b298 --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee36fe482a025616e0fe52da7fa6f3dd3beec71a3f579b28cce66a7817d86694 +size 45507 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8154156427e3c921231965a5fea5dc9e34f00da5 --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d3bbbd04c620f2e6fcf73836f80ae579aab33894e0932c0fcce8b9e062f9a88 +size 76974 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1060806b4a671f026870ae0241f845d4ba96de0 --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f1cc33bb519149c06c75f3a27d986060fe9873a0703f28d6d3d9a22f9328dbf +size 70952 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d9abf0756be19c1410779ae8c11d4e3978feec1 --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30955cbb8c15fbfa6742829cf9b901f75affd9b2b40ee6a8347a22d91bd0f7d3 +size 42802 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72f8287c9cd9fe1ac55263765c6c013f1537596e --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6b380a1fa6455de49181d6ef0298fda66f133a453b4b73a38617793bd174010 +size 56218 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5600d21c095011f5680cc818059a6e9833ebdcc3 --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:431620bc0458bcf943fedfd2e0f04c4f6c8a15fc42144e6a3dd3221fe1fe891f +size 39132 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/marked/H/T-REC-H.622.1-200810-I_PDF-E/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33d50fd63056abaa40041f1c0d29ef0bfc98ddf0 --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35922de225d6152bd7706482dde0f166ff860249e8981efe70aa6626ea29a2b8 +size 39531 diff --git a/marked/H/T-REC-H.622.1-200810-I_PDF-E/raw.md b/marked/H/T-REC-H.622.1-200810-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fc857965a7c3bc6c50370e9cbb8d9bfeb8017579 --- /dev/null +++ b/marked/H/T-REC-H.622.1-200810-I_PDF-E/raw.md @@ -0,0 +1,1391 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.622.1** + +(10/2008) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Broadband, triple-play and advanced multimedia +services – Advanced multimedia services and applications + +# --- **Architecture and functional requirements for home networks supporting IPTV services** + +Recommendation ITU-T H.622.1 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T H.622.1** + +# **Architecture and functional requirements for home networks supporting IPTV services** + +## **Summary** + +Recommendation ITU-T H.622.1 describes an architecture for home networks supporting IPTV services and its functional requirements. + +In this Recommendation, home networks and IPTV-related entities are defined, and interfaces between these entities are identified. Functions needed for the home network to support IPTV services are described. Requirements for these functions are also described in this Recommendation. + +## **Source** + +Recommendation ITU-T H.622.1 was approved on 14 October 2008 by ITU-T Study Group 16 (2005-2008) under the Recommendation ITU-T A.8 procedure. + +## **Keywords** + +Delivery network gateway, home network, interoperability, IPTV services, IPTV terminal device, QoS, remote management, residential gateway, security. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +### INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | | Page | +|---------|------------------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 3 | +| 3.1 | Terms defined elsewhere ..... | 3 | +| 3.2 | Terms defined in this Recommendation..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 5 | +| 6 | Home network architecture..... | 6 | +| 7 | Quality of service (QoS)..... | 8 | +| 7.1 | Home network QoS architecture ..... | 8 | +| 7.2 | Quality of service requirements..... | 13 | +| 8 | Security ..... | 17 | +| 8.1 | Home network security threats..... | 18 | +| 8.2 | Home network security requirements..... | 18 | +| 8.3 | Link protection requirements ..... | 18 | +| 9 | Interoperability ..... | 18 | +| 9.1 | Interoperability between the IPTV access network and home network ..... | 18 | +| 9.2 | Interoperability among home network devices ..... | 19 | +| 10 | Delivery network gateway (DNG)..... | 19 | +| 10.1 | DNG functional overview ..... | 19 | +| 10.2 | IPI-4 interfaces ..... | 21 | +| 10.3 | IPI-3 interfaces ..... | 23 | +| 10.4 | Packet processing ..... | 24 | +| 10.5 | Network services support ..... | 25 | +| 10.6 | IGMP functionality..... | 26 | +| 11 | Network management..... | 27 | +| 11.1 | Remote management ..... | 27 | +| 11.2 | QoS management functions on the DNG ..... | 28 | +| 11.3 | Security management functions on the DNG..... | 28 | +| 11.4 | Performance monitoring and diagnostics, and troubleshooting functions
    on the DNG..... | 28 | +| 11.5 | Local management application for the DNG..... | 28 | +| 11.6 | IPTV service information report ..... | 29 | +| Annex A | – Considerations on ISO/IEC 15045-1 for IPTV services ..... | 30 | +| A.1 | Introduction ..... | 30 | +| A.2 | Comparison of terminology..... | 30 | + +| | Page | +|---------------------------------------------------------------------------------------|-------------| +| A.3    Packet processing and interfaces of the DNG ..... | 30 | +| A.4    Security consideration ..... | 31 | +| Appendix I – An explanation of the layered model for the IPTV home network..... | 32 | +| Appendix II – UPnP-based home network for IPTV services ..... | 34 | +| Appendix III – Consideration of retransmission of free-to-air broadcast content ..... | 35 | +| III.1    Middleware aspect..... | 35 | +| III.2    Content protection issue ..... | 35 | +| III.3    Privacy protection issue..... | 35 | +| III.4    Delivery control of retransmission ..... | 35 | +| III.5    Provision of emergency broadcast..... | 35 | +| Appendix IV – Example configurations for an IP-based home network ..... | 36 | +| Bibliography..... | 37 | + +# Recommendation ITU-T H.622.1 + +# Architecture and functional requirements for home networks supporting IPTV services + +## 1 Scope + +This Recommendation describes the relationship between the home network (HN) and IPTV-related entities. It also identifies rules and requirements for functions needed on the home network to support IPTV services. It further sets criteria to verify compliance of home network devices, e.g., IPTV terminal devices, to the identified rules and requirements. + +The architecture and requirements described in this Recommendation are based on current delivery network technology and thus advanced IPTV services and features that are possible with emerging NGN (next generation network) architecture, e.g., multicast control, are not covered. Advanced IPTV features and services in NGN-based home networks are for further study. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.983.x] Recommendation ITU-T G.983.x-series (in force), *Broadband optical access systems*. +<> +- [ITU-T G.984.x] Recommendation ITU-T G.984.x-series (in force), *Gigabit-capable Passive Optical Networks (GPON)*. +<> +- [ITU-T G.992.1] Recommendation ITU-T G.992.1 (1999), *Asymmetric digital subscriber line (ADSL) transceivers*. +<> +- [ITU-T G.992.3] Recommendation ITU-T G.992.3 (2005), *Asymmetric digital subscriber line transceivers 2 (ADSL2)*. +<> +- [ITU-T G.992.5] Recommendation ITU-T G.992.5 (2005), *Asymmetric digital subscriber line (ADSL) transceivers – Extended bandwidth ADSL2 (ADSL2plus)*. +<> +- [ITU-T G.993.2] Recommendation ITU-T G.993.2 (2006), *Very high speed digital subscriber line transceivers 2 (VDSL2)*. +<> +- [ITU-T H.622] Recommendation ITU-T H.622 (2008), *A generic home network architecture with support for multimedia services*. +<> +- [ITU-T J.190] Recommendation ITU-T J.190 (2007), *Architecture of MediaHomeNet*. +<> + +- [ITU-T X.1111] Recommendation ITU-T X.1111 (2007), *Framework of security technologies for home network*. + <> +- [ATIS-0800002] ATIS standard ATIS-0800002 (2006), *IPTV Architecture Requirements*. + <> +- [HGI] HGI-RD001-R1-obs Home Gateway Initiative (2006), *Home Gateway Technical Requirements: Release 1.0*. + <[http://www.homegatewayinitiative.org/publis/HGI\\_V1.0.pdf](http://www.homegatewayinitiative.org/publis/HGI_V1.0.pdf)> +- [IETF RFC 2236] IETF RFC 2236 (1997), *Internet Group Management Protocol, Version 2*. + <> +- [IETF RFC 2710] IETF RFC 2710 (1999), *Multicast Listener Discovery (MLD) for IPv6*. + <> +- [IETF RFC 3376] IETF RFC 3376 (2002), *Internet Group Management Protocol, Version 3*. + <> +- [IEEE 802.1D] IEEE Std. 802.1D (2004), *IEEE standard for local and metropolitan area networks – Media Access Control (MAC) Bridges*. + <> +- [IEEE 802.1Q] IEEE Std. 802.1Q (2005), *IEEE Standard for Local and Metropolitan Area Networks – Virtual Bridged Local Area Networks*. + <> +- [IEEE 802.3] IEEE Std. 802.3 (2005), *IEEE standard for Information technology – Telecommunications and information exchange between systems-Local and metropolitan area networks – Specific requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications*. + <> +- [IEEE 802.11] IEEE Std. 802.11 (2007), *IEEE Standard for Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications*. + <> +- [IEC 62481-1] IEC 62481-1 (2007), *Digital living network alliance (DLNA) home networked device interoperability guidelines – Part 1: Architecture and protocols*. + <> +- [IEC 62481-2] IEC 62481-2 (2007), *Digital living network alliance (DLNA) home networked device interoperability guidelines – Part 2: DLNA media formats*. + <> +- [ISO/IEC 8802-1] ISO/IEC 8802-1 (2001), *Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements – Part 1: Overview of Local Area Network Standards*. + <> +- [ISO/IEC 15045-1] ISO/IEC 15045-1 (2004), *Information technology – Home electronic system (HES) gateway – Part 1: A residential gateway model for HES*. + <> + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 delivery network gateway (DNG)** [ATIS-0800002]: A device implementing the delivery network gateway function (DNGF). + +NOTE – Many terms such as home access (HA) [ITU-T J.190], home gateway, residential gateway, delivery network gateway and so on are used for the same device. + +**3.1.2 home network (HN)** [ITU-T H.622]: A home network is the collection of elements that process, manage, transport and store information, thus enabling the connection and integration of multiple computing, control, monitoring, communication and entertainment devices in the home. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 delivery network gateway functions (DNGF)**: Set of functions that mediate between the network and service provider domains and the IPTV terminal function (ITF). + +NOTE – A device implementing the DNGF is commonly referred to as the residential gateway (RG) or delivery network gateway (DNG). + +**3.2.2 home network (HN) capable IPTV TD**: An IPTV TD which has HN capability. This is typically a server and/or a client to HN devices. + +**3.2.3 HN capable TD**: A TD which has HN capability. This is typically a server and/or a client to HN devices. + +**3.2.4 IPTV TD**: A terminal device which has IPTV terminal function (ITF) functionality, e.g., a set-top box. + +**3.2.5 IPTV terminal function (ITF)**: The end-user function(s) associated with a) receiving and responding to network control channel messages regarding session set-up, maintenance and tear-down, and b) receiving the content of an IP transport from the network and rendering. + +**3.2.6 terminal device (TD)**: A device which typically presents and/or processes content, such as a personal computer, a computer peripheral, a network appliance, a mobile device, a television set, a monitor, a voice over IP terminal or an audiovisual media player. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------| +| ACL | Access Control List | +| ALG | Application Layer Gateway | +| ALL | Application Layer Logic | +| AN | Access Network | +| BC-NW | Broadcast Network | +| DA | Destination Address | +| DHCP | Dynamic Host Configuration Protocol | +| DLNA | Digital Living Network Alliance | +| DMP | Digital Media Player | +| DMS | Digital Media Server | + +| | | +|-------|--------------------------------------------| +| DMZ | Demilitarized Zone | +| DNG | Delivery Network Gateway | +| DNGF | Delivery Network Gateway Function | +| DNS | Domain Name System | +| DoS | Denial of Service | +| DSCP | Differentiated Services Code Point | +| DSL | Digital Subscriber Line | +| DTCP | Digital Transmission Content Protection | +| ECG | Electronic Content Guide | +| EPG | Electronic Programme Guide | +| FEC | Forward Error Correction | +| GUI | Graphical User Interface | +| HA | Home Access | +| HN | Home Network | +| IGMP | Internet Group Management Protocol | +| IP | Internet Protocol | +| IPI | Internet Protocol Interface | +| IPTV | Internet Protocol Television | +| L2 | Layer 2 | +| LAN | Local Area Network | +| MAC | Media Access Control | +| MDI | Medium Dependent Interface | +| MDI-X | Medium Dependent Interface Crossover | +| MLD | Multicast Listener Discovery | +| NAT | Network Address Translation | +| NT | Network Terminal | +| NW | Network | +| OAM | Operations, Administration and Maintenance | +| OLT | Optical Line Terminal | +| ONT | Optical Network Termination | +| OUI | Organizationally Unique Identifier | +| PLT | Power Line Transmission | +| PON | Passive Optical Network | +| PPP | Point-to-Point Protocol | +| PPPoE | Point-to-Point Protocol over Ethernet | +| PVC | Permanent Virtual Circuit | +| PVR | Personal Video Recorder | + +| | | +|------|--------------------------------------------------------------------------------------------| +| QoS | Quality of Service | +| RG | Residential Gateway | +| RTSP | Real-Time Streaming Protocol | +| SA | Source Address | +| SCP | Service and Content Protection | +| SSID | Service Set Identifier | +| SSM | Source-Specific Multicast | +| STUN | Simple Traversal of User Datagram Protocol (UDP) through network address translation (NAT) | +| TCP | Transmission Control Protocol | +| TD | Terminal Device | +| UDP | User Datagram Protocol | +| USB | Universal Serial Bus | +| VC | Virtual Channel | +| VCI | Virtual Channel Identifier | +| VLAN | Virtual Local Area Network | +| VPI | Virtual Path Identifier | +| VoD | Video on Demand | +| VoIP | Voice over IP | +| WAN | Wide Area Network | +| WEP | Wired Equivalent Privacy | +| WPA | Wi-Fi Protected Access | +| WRR | Weighted Round Robin | +| XML | eXtensible Markup Language | + +## 5 Conventions + +In this Recommendation, the following conventions apply. + +The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. + +The keywords "**is recommended**" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +The keywords "**is not recommended**" indicate a requirement which is not recommended but which is not specifically prohibited. Thus, conformance with this specification can still be claimed even if this requirement is present. + +The keywords "**can optionally**" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +Furthermore, [HGI\_Rn] means the n-th requirement as identified in [HGI]. For example, [HGI\_R100] means the R100 requirement identified in [HGI]. + +The items tagged by [HGI\_Rn] have been included in this Recommendations with the kind permission of the Home Gateway Initiative. Readers interested in the most current publication of Home Gateway Initiative should consult the website of that body here: + +. + +## 6 Home network architecture + +The home network has become a preferred environment for many users to receive multimedia services in the home. Thus, IPTV services are likely to be delivered using home networking technology. In order to provide IPTV users with good user experience and to bring down the costs, IPTV devices need to interact seamlessly with the home network and with each other on the home network. For that purpose, a standardized home network architecture supporting IPTV services is essential. + +Figure 6-1 below depicts the home network architecture defined in this Recommendation. + +![Diagram of Home network architecture showing the flow from Broadcast Network (BC-NW) through various components to the Home Network Terminal Device (HN-TD).](08441fa90c5fd11994626f662ac13f19_img.jpg) + +The diagram illustrates the home network architecture. It shows a sequence of components connected by interfaces. From left to right, the components are: BC-NW (Broadcast Network), Access NW (Access Network), NT (Network Terminal), DNG (Device Network Gateway), Home network [primary], IPTV TD (IPTV Terminal Device), Home network [secondary] (IP/non-IP), and HN-TD (Home Network Terminal Device). The interfaces between these components are labeled: IPI-4 between Access NW and NT, IPI-3 between NT and DNG, IPI-1 between DNG and Home network [primary], IPI-0/IPI-1 between Home network [primary] and IPTV TD, and H.622.1(08)\_F6.1 between IPTV TD and Home network [secondary]. A dashed line connects BC-NW to the IPTV TD. A legend at the bottom left indicates that BC-NW stands for Broadcast Network. + +Diagram of Home network architecture showing the flow from Broadcast Network (BC-NW) through various components to the Home Network Terminal Device (HN-TD). + +**Figure 6-1 – Home network architecture** + +The components of the home network architecture are described as follows. + +### Primary domain (IP-HN-P) + +The primary domain deals with IPTV-related IP traffic between the access network and the IPTV terminal device (IPTV TD) including audio and video streams. Traffic in the primary domain is associated with traffic to and from the access network. The devices and traffic related to the primary domain are required to be configured to be reachable to and from the access network, directly or indirectly (e.g., via NAT). Since this domain is expected to work as an extension of the access network, technical coordination such as QoS mapping with the access network is required. + +### Secondary domain + +The secondary domain deals with IPTV-related traffic between the IPTV TD and the home network terminal device (HN-TD). The devices and traffic belonging to the secondary domain do not need to be configured to be reachable to and from the access network. For example, there may be cases where locally assigned IP addresses are enough for this domain. The secondary domain can be divided into two parts, IP and non-IP, depending on the network layer protocol used. + +### IP secondary domain (IP-HN-S) + +The IP secondary domain is a part of the secondary domain based on IP. + +### Non-IP secondary domain (PR-HN-S) + +The non-IP secondary domain is a part of the secondary domain based on non-IP protocols, such as [b-IEEE 1394]. + +### Network termination (NT) + +The network termination resides between network provider's access network and home network. The NT is the termination point of the access network. For example, in the cable broadband service environment, a cable modem is the NT. Likewise, a digital subscriber line (DSL) modem is the NT in the DSL broadband service environment. Another example for NT is an optical network termination (ONT), which is a termination device of an optical access network. + +### Delivery network gateway (DNG) + +The DNG serves as a gateway between the access network and home network. It provides crucial functions for services on the home network. Functions of the DNG are described in detail later in this Recommendation. + +### IPTV terminal device (IPTV TD) + +An IPTV terminal device is used by end-users to receive IPTV services. An IPTV set-top box is an example of an IPTV terminal device. + +### Home network terminal device (HN-TD) + +Terminal devices that do not directly interact with the service or network provider may be used by the end-user to use IPTV services on the home network. These devices are classified as HN-TD. An example of such terminal devices is a traditional digital TV connected to the home network using the IEEE 1394 interface. + +The above architecture contains interfaces between devices and domains. These interfaces are summarized in Table 6-1 below. + +**Table 6-1 – Interfaces within the home network architecture** + +| Interface | | Note | +|-----------|--------|--------------------------------------------------------------------------------------------------------------------| +| IPI-0 | | Interface between IPTV TD and HN-TD that has no direct connection with the DNG. | +| IPI-1 | | Upstream side interface of IPTV TD or HN-TD. In the HN-TD case, the HN-TD has a direct IP connection with the DNG. | +| | IPI-1a | IPI-1 interface used for power line | +| | IPI-1b | IPI-1 interface used for Ethernet (10/100/1000 BASE-T) | +| | IPI-1c | IPI-1 interface used for home PNA | +| | IPI-1d | IPI-1 interface used for coaxial | +| | IPI-1e | IPI-1 interface used for wireless | +| IPI-3 | | Downstream side interface of DNG | +| | IPI-3a | IPI-3 interface used for power line (see clause 10.3.1) | +| | IPI-3b | IPI-3 interface used for Ethernet (10/100/1000 BASE-T) (see clause 10.3.2) | +| | IPI-3c | IPI-3 interface used for home PNA (see clause 10.3.3) | +| | IPI-3d | IPI-3 interface used for coaxial (see clause 10.3.4) | +| | IPI-3e | IPI-3 interface used for wireless (see clause 10.3.5) | + +**Table 6-1 – Interfaces within the home network architecture** + +| Interface | Note | +|-----------|--------------------------------------------------------------------------------------------| +| IPI-4 | Upstream side interface of DNG (see clause 10.2) | +| IPI-4a | IPI-4 interface used for connection with copper access network (see clause 10.2.1) | +| IPI-4b | IPI-4 interface used for connection with NT through Ethernet interface (see clause 10.2.2) | +| IPI-4c | IPI-4 interface used for connection with NT through coaxial interface (see clause 10.2.3) | +| IPI-4d | IPI-4 interface used for connection with wireless access network (see clause 10.2.4) | +| IPI-4e | IPI-4 interface used for connection with optical access network (see clause 10.2.5) | + +NOTE – The layer 2 technologies listed here, e.g., Ethernet and power line, are those that are currently available. This table may be expanded in the future to include new technologies as they become available. + +## 7 Quality of service (QoS) + +In order to provide a good user experience of IPTV services in the home network environment, the QoS aspect of the home network needs to be considered, and necessary QoS mechanisms to ensure good user experiences need to be provided. This clause discusses QoS aspect of the home network in the context of IPTV services. + +There are two main QoS techniques that are being used in an IP network: priority (or class) based QoS and parameterized QoS. With the priority QoS technique, intermediate routing entities between the source and the destination of an IPTV data stream determine how to handle an IP packet from the IPTV data stream according to the priority field in the header of that IP packet. The priority field has been set to a certain value (this is called QoS marking or classification) by the source. With this technique, higher priority IP packets will get better treatment during transit to reach the destination, thus their stream can achieve better QoS than others that have a lower priority. + +In the parameterized QoS technique, the QoS requirements of an IPTV data stream (e.g., bandwidth, delay and jitter) are specified and requested to the network before the first IP packet is sent. The home network then uses these QoS parameters to set up the environment so that IP packets in the IPTV stream are processed in such a way to ensure that QoS requirements of the stream are met. + +The parameterized QoS technique may provide guaranteed QoS as requested for IPTV services but its technology has not yet been widely agreed upon in the industry. For that reason, the QoS aspects of the home network discussed in this Recommendation concern mainly the priority based QoS technique. The application of the parameterized QoS technique to the home network for IPTV services is for further study. + +### 7.1 Home network QoS architecture + +This clause describes a QoS architecture that is based on the home gateway initiative (HGI) and its requirements. + +NOTE – The QoS mechanisms in this clause are also described in [HGI] in the context of bidirectional services like VoIP. Refer to [HGI] for more details. + +#### 7.1.1 Potential congestion points in the home network + +![Diagram of a typical home network showing potential congestion points (CP-1, CP-2, CP-3).](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +The diagram illustrates a typical home network architecture. On the left, an 'Access network' connects to a 'DNG' (Device Network Gateway). The DNG has three interfaces marked with blue circles representing congestion points: CP-1 (upstream interface to the access network), CP-2 (egress interface to the IP-based home network), and CP-3 (interface to a wireless device). The 'IP-based home network' contains an 'Ethernet switch' and an 'Ethernet-PLT bridge'. The switch has four ports connected to 'TD' (Terminal Device) units via '100BASE-TX' and '100BASE-TS' links; its egress port is marked as CP-2. The Ethernet-PLT bridge has one '100BASE-TX' input from the DNG and one 'PLT' output to a 'TD' unit; its bridge point is marked as CP-3. A 'Wireless' link connects the DNG to another 'TD' unit. + +Diagram of a typical home network showing potential congestion points (CP-1, CP-2, CP-3). + +**Figure 7-1 – Potential congestion points in a typical home network** + +The home network QoS function needs to accommodate a variety of both access and home network technologies. There are a number of potential congestion points as shown in Figure 7-1. Note that the degree to which these are actual congestion points will depend on the underlying network technologies used. + +Three potential congestion points are identified in the home network. + +##### - Congestion point CP-1 + +Congestion point CP-1 is on the upstream side interface of the DNG, which is also defined as IPI-4. Because some IP-based access network technologies such as DSL and cable modem have relatively limited capacity for the upstream traffic, it is likely to see traffic congestion at this interface point. + +##### - Congestion point CP-2 + +Congestion point CP-2 is at the egress port of the device in which traffic from two or more network links is collected. A typical example is an Ethernet switch. If combined traffic from several ports or links exceeds a certain amount, the congestion at the egress port will happen. Congestion point CP-2 is also possible at the DNG, if it contains switching capability for traffic on the home network side. + +##### - Congestion point CP-3 + +Congestion point CP-3 is where congestion could be caused by transmission capacity differences. The bridge device interconnecting between different network segments with different capacity between Ethernet and power line transmission (PLT), is a typical example. Congestion point CP-3 is also possible at the DNG because of the difference of transmission capacity between the access network and home network. + +#### 7.1.2 QoS mechanisms + +QoS management described in this Recommendation works on the basis of packet-by-packet service classification. The service classifiers are contained in header fields in the ingress packet and value of these service classifiers are assigned via QoS marking. QoS markings of packets coming from the HN side are generally untrusted, but can be used if a trust relationship is established by some other means, or in combination with other service classifiers. + +The service classification information is used to assign the packet to the appropriate queue, and may be used to set the layer 2 markings for a particular transport technology. It is also possible to drop packets on the basis of classification when necessary. The management function can optionally provide the service classifiers' value as a static policy. Where service instance classification is used (e.g., for the overload protection mechanism described below), the additional classifiers are generated within the DNG itself. There is no session awareness, except for that associated with this overload control mechanism. Class-based queuing is used to queue packets. DSCP markings of the incoming packet at the IPI-3 interface can be overwritten to zero or to a per-service configurable value. There is a QoS mapping table for layer 2 parameters for transit traffic at the DNG. The DNG does not directly support signalled admission control, but the overload protection mechanism can provide some features of admission control by limiting the number of service instances to a pre-configured value. + +NOTE – See clause 5.5.4 of [HGI]. + +#### 7.1.3 QoS marking + +There are several class-based QoS marking schemes such as differentiated services code point (DSCP), VLAN and Ethernet priority scheme that can be used for QoS management in the home network for IPTV services. In these schemes, all traffic of the same type would have the same QoS marking value. For QoS management to be effective, the marking values need to be trusted, but since marking values, particularly in case of upstream and transit, can be set by an end-user's terminal device, they can be spoofed. Thus, the home network is required to provide a mechanism to establish trust with end devices to prevent spoofing of QoS marking values. + +VLAN IDs and priority tags could be used as a QoS marking within the home network. Adding a VLAN header or priority tags increases the Ethernet frame size; and some small, unmanaged Ethernet switches simply drop such frames. Since there are at least some infrastructure devices which will drop tagged frames, the DNG is recommended not to add VLAN headers to any frames. However, it is recognized that certain DLNA devices may send tagged frames. The DNG needs to be able to receive such frames and, in the case of bridged traffic, to forward them transparently. + +NOTE – See clause 5.5.5 of [HGI]. + +#### 7.1.4 Traffic classification + +The key requirement for traffic classification is to be able to identify a service class. Queuing, scheduling and dropping treatments are recommended to be determined based upon the service class of the packet. Each packet is classified by inspecting one or more classifiers contained in its header fields. The combination of classifiers used to identify a service class is known as the classification rule for that service. + +There are in fact rather different requirements for the classification of the three types of traffic flow through the DNG, namely upstream, downstream and transit. + +For basic IPTV services, such as linear TV QoS, downstream traffic is the most important, next transit traffic and lastly upstream traffic. In the downstream direction, the main aim is to maintain the QoS characteristic of incoming traffic and to ensure that it is not compromised by transit traffic. The classifiers are briefly described below with a rationale as to when and how they might be used. + +NOTE 1 – See clause 5.5.6 of [HGI]. + +NOTE 2 – For interactive applications such as gaming, QoS treatment for upstream traffic is also important. + +#### 7.1.5 Downstream classifiers + +The main requirement in the downstream direction is to be able to distinguish IPTV traffic from other traffic. When the DNG is connected to the access network that is managed to provide required QoS for IPTV traffic, it is likely that QoS marking, such as DSCP, is available. Because this QoS marking is set by the network provider, it is trustful and correctly reflects the QoS policy of the + +network provider. Therefore, when QoS marking is set for downstream traffic, using this QoS marking as the QoS classifier is desirable. Other classifiers such as IP DA and SA, physical port, packet length, MAC SA and DA, TCP/UDP port number and protocol type fields, which are identified as upstream classifiers in [HGI] (see clause 5.5.7 of [HGI]), can also be used. + +#### **7.1.6 Transit classification** + +Preventing adverse impacts to IPTV services by transit traffic is a key objective of QoS control of transit traffic. This could be done by giving better priority to the downstream IPTV traffic (relative to transit traffic). + +The service differentiation can be done by using QoS marking. However, as mentioned above, there is a potential problem of using QoS marking of transit traffic. The QoS marking of transit traffic is set by the end-user devices that are typically not controlled by the network provider and thus is not trustful. Also, it is difficult to ensure the consistency of QoS marking policy between end-user devices and the network provider. It is possible to have conflicting QoS policies since they are set by end-user devices and network provider separately without coordination. + +Therefore it is desirable to use a simple transit priority scheme, which is essentially device-based and uses MAC address pairs (SA and DA) to identify traffic which can be given higher priority. Also, the use of other classifiers needs to be considered. Once transit traffic is classified at the DNG, the relevant value of QoS marking is recommended to be set for the packets. This will help bridging devices in the home network to prioritize the packets efficiently. + +NOTE – The text above is imported from clause 5.5.9 of [HGI] with modifications. + +#### **7.1.7 Traffic classifier used in the home network** + +##### **7.1.7.1 IP destination address (IP DA)** + +This is a particularly useful classifier in the case where the required priority is related to its destination address. The destination address in this case does not need to be limited to a unicast address since the use of multicast is likely for IPTV services. The traffic classification based on both unicast and multicast is possible and desirable in some cases. The followings are some advantages of using this approach: + +- It requires a single, initial configuration only. +- It cannot be usefully spoofed, as the traffic would go to an inappropriate destination. +- It can be used for an encrypted service as long as the tunnel address is known. + +NOTE – The text above is imported from clause 5.5.7.1 of [HGI] with modifications. + +##### **7.1.7.2 IP source address (IP SA)** + +The use of the SA as a traffic classifier may be appropriate when there is a large number of DAs associated with a service and the use of the DA as a classifier may cause difficulty. In case of IPTV, the IP SA represents the corresponding video server. If the IP address of such a device is managed in a reliable way and the number of IP SAs is sufficiently small, the use of the IP SA as a traffic classifier might be considered. + +NOTE – The text above is imported from clause 5.5.7.2 of [HGI] with modifications. + +##### **7.1.7.3 MAC source address (MAC SA) and destination address (MAC DA)** + +These can be used to distinguish different physical devices, and therefore different instances of the same service as per clause 5.5.7.5 of [HGI]. + +##### **7.1.7.4 TCP/UDP port number** + +The TCP/UDP port number can be used to identify certain applications as per clause 5.5.7.6 of [HGI]. + +##### 7.1.7.5 Protocol type + +Distinguishing between TCP and UDP protocols can allow a more general distinction between different types of service as per clause 5.5.7.7 of [HGI]. + +##### 7.1.7.6 QoS mapping between different HN technologies + +As in the case of bridging the HN with the access network function, the DNG bridging between different HN technologies needs consideration in order to provide well-harmonized QoS within the home network. Consideration includes mapping between the layer 2 and layer 3 marker (or classifier) and use of marking in the different HN segments. + +NOTE – The details of QoS mapping require further study. + +#### 7.1.8 Downstream and transit queue structure + +The main functional requirements of QoS architecture are to avoid excessive delay and jitter as well as packet loss for multimedia services such as IPTV, to provide sufficient bandwidth for IPTV services, and to prevent best-effort traffic from being completely starved by higher priority queues. + +In the downstream direction, there are two major concerns: 1) ensuring that traffic from the AN is not blocked by transit traffic, and 2) if there is downstream congestion due to a rate mismatch caused by a slow HN technology (congestion point CP-3), ensuring that the value-added traffic gets higher priority. There may be two different types of transit traffic: simple data traffic and streaming traffic, e.g., from a media player. For a better user experience, streaming traffic is recommended to get higher priority than simple data traffic. From a QoS perspective, simple data traffic is considered best effort traffic and streaming traffic is considered managed service traffic. + +Based on these considerations, the downstream would need four queues per IPI-3 interface to manage traffic: 1) managed services from the AN, 2) best effort from the AN, 3) managed services within IP-HN-S/P, and 4) best effort within IP-HN-P/S. + +NOTE – There are three fundamentally different types of traffic within a managed services class with regard to QoS: voice, video and data. Each of these traffic types may require its own queues. Also, there may be a need to further distinguish between two different types of data traffic (e.g., for higher priority control data or to support a premium data service). Further, the overload protection mechanism may require an additional queue. However, it should be noted that the larger number of queues may increase the implementation difficulty of HN devices such as the DNG, and it is technically possible to have a smaller number of queues by merging some of these queues. Further study is needed for queues implementation. + +#### 7.1.9 Class based QoS, sessions and policy + +The QoS approach used here is essentially traffic-class based, i.e., the QoS treatment is the same for all flows belonging to the same class. This approach was chosen for simplicity and scalability. Consequently, there is limited flow awareness to support overload protection mechanisms. Flows are closely related to sessions, which have two possible uses in a QoS scheme: 1) allowing QoS policy to be applied per session, and 2) preventing the establishment of new sessions if they would adversely impact existing ones. + +However, the basic requirement here is to provide the appropriate QoS for a service type; there is no reason to suppose that this should be different on a session by session basis (see Note 1). Therefore, a static policy approach has been adopted. The potential downside of this approach is that there is no mechanism to prevent a new session overloading the class and, as a result, the entire class suffers. + +NOTE 1 – It is possible for different kinds of IPTV services to be given different QoS treatment. For example, the required QoS treatment for a VoD service would be different from a linear TV service. Also, a video coding scheme chosen by the service provider may have an impact on the required bandwidth as well as other QoS parameters. But from a QoS perspective, all sessions that belong to the same service type (e.g., VoD service) are treated in the same manner. + +If overload is a genuine concern (as opposed to a theoretical possibility) then some kind of admission control system is needed. Admission control requires a decision to be made about resource availability before a session is established, and so involves signalling. The DNG is not involved in signalling (except where the service terminates in the DNG itself), and while it could, in principle, snoop on signalling, this cannot be done where the signalling is in an encrypted tunnel. Further, snooping does not provide a graceful means to reject a session request. + +The DNG can support a basic overload protection mechanism which allows a new service instance to be allowed on a trial basis to see whether or not it can be supported without impacting existing traffic. This mechanism works in the following fashion. Within a service class, there is the concept of a recognized and an unrecognized service instance. The simplest way of doing this would be to classify the instance on the basis of the associated IP or MAC address of the IPTV TD. Any packet with the known service class, but unknown instance, would be put into a queue that is different from the recognized instances queue. Each classification rule has an optional pointer to an application layer logic (ALL). For overload protection, the ALL would check if this was a known service instance. If not, it would initiate a procedure which would check (over a relatively short period of time) if this new instance could be accommodated without causing overload as measured by excessive queue length. Further details of this mechanism are given along with the requirements in clause 7.2.3. + +NOTE 2 – The text above is imported from clause 5.5.12 of [HGI] with modifications. + +### 7.2 Quality of service requirements + +This clause specifies the QoS data path functions which are required to be supported by the DNG, and the QoS management objects which are used to configure QoS policy within the DNG. Core QoS traffic management functions include classification, marking, congestion management, queuing, shaping and egress scheduling. + +Figure 7-2 shows a conceptual view of the core QoS traffic management functions as packets are received from the IPI-3 interfaces or from internal DNG sources. Note that this diagram is not meant to determine the implementation structure of the QoS functions nor those of the related data path functions. + +![Figure 7-2: QoS functions from IPI-3 interfaces. This flowchart illustrates the data path for packets entering the DNG from IPI-3 interfaces or internal sources. The process starts with four input sources: IPI-3 ingress (three instances) and Internal traffic source at DNG. These feed into a 'Classification' block. The output of 'Classification' goes to 'DSCP and L2 marking', which then goes to 'Bridging, NAT/routing, firewall'. From 'Bridging, NAT/routing, firewall', one path leads to a 'DNG Traffic sink' and another to 'Upstream congestion management'. 'Upstream congestion management' leads to 'IPI-4 class shaping and queuing', which then leads to 'IPI-4 port scheduler and shaper'. 'IPI-4 port scheduler and shaper' has three outputs: IPI-4 egress 1, IPI-4 egress 2, and IPI-4 egress n. Another path from 'Bridging, NAT/routing, firewall' leads to 'IPI-3 congestion control', which leads to 'IPI-3 queuing', which then leads to 'IPI-3 ports scheduler'. 'IPI-3 ports scheduler' has three outputs: IPI-3 egress 1, IPI-3 egress 2, and IPI-3 egress n. A small note 'H.622.1(08)_F7.2' is present near the bottom right of the diagram.](a734898ce18e972938949637c32a34f4_img.jpg) + +Figure 7-2: QoS functions from IPI-3 interfaces. This flowchart illustrates the data path for packets entering the DNG from IPI-3 interfaces or internal sources. The process starts with four input sources: IPI-3 ingress (three instances) and Internal traffic source at DNG. These feed into a 'Classification' block. The output of 'Classification' goes to 'DSCP and L2 marking', which then goes to 'Bridging, NAT/routing, firewall'. From 'Bridging, NAT/routing, firewall', one path leads to a 'DNG Traffic sink' and another to 'Upstream congestion management'. 'Upstream congestion management' leads to 'IPI-4 class shaping and queuing', which then leads to 'IPI-4 port scheduler and shaper'. 'IPI-4 port scheduler and shaper' has three outputs: IPI-4 egress 1, IPI-4 egress 2, and IPI-4 egress n. Another path from 'Bridging, NAT/routing, firewall' leads to 'IPI-3 congestion control', which leads to 'IPI-3 queuing', which then leads to 'IPI-3 ports scheduler'. 'IPI-3 ports scheduler' has three outputs: IPI-3 egress 1, IPI-3 egress 2, and IPI-3 egress n. A small note 'H.622.1(08)\_F7.2' is present near the bottom right of the diagram. + +Figure 7-2 – QoS functions from IPI-3 interfaces + +Figure 7-3 shows a conceptual view of the core QoS traffic management functions as packets are received from the IPI-4 interfaces. Note that while these are logical IPI-4 interfaces, there is only one physical IPI-4 interface. This diagram is not meant to determine the implementation structure of the QoS functions nor those of the related data path functions. + +![Figure 7-3 – QoS functions from IPI-4 interface. The diagram shows a flow of traffic from three IPI-4 ingress points through a series of processing blocks: Classification, DSCP and L2 marking, Bridging, NAT/routing, firewall, IPI-3 congestion control, IPI-3 queuing, and IPI-3 ports scheduler. The final output is to three IPI-3 egress points (1, 2, and n). A DNG Traffic sink is shown as a separate block connected to the Bridging, NAT/routing, firewall block. The diagram is labeled H.622.1(08)_F7.3.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +graph LR + IPI4_1[IPI-4 ingress] --> C[Classification] + IPI4_2[IPI-4 ingress] --> C + IPI4_3[IPI-4 ingress] --> C + C --> D[DSCP and L2 marking] + D --> B[Bridging, NAT/routing, firewall] + B --> I3CC[IPI-3 congestion control] + I3CC --> I3Q[IPI-3 queuing] + I3Q --> I3PS[IPI-3 ports scheduler] + I3PS --> IPI3_1[IPI-3 egress 1] + I3PS --> IPI3_2[IPI-3 egress 2] + I3PS --> IPI3_n[IPI-3 egress n] + B --> DNG[DNG Traffic sink] + H622_1_08_F7_3[H.622.1(08)_F7.3] + +``` + +Figure 7-3 – QoS functions from IPI-4 interface. The diagram shows a flow of traffic from three IPI-4 ingress points through a series of processing blocks: Classification, DSCP and L2 marking, Bridging, NAT/routing, firewall, IPI-3 congestion control, IPI-3 queuing, and IPI-3 ports scheduler. The final output is to three IPI-3 egress points (1, 2, and n). A DNG Traffic sink is shown as a separate block connected to the Bridging, NAT/routing, firewall block. The diagram is labeled H.622.1(08)\_F7.3. + +**Figure 7-3 – QoS functions from IPI-4 interface** + +These QoS functions are described below. + +NOTE – The text above is imported from clause 6.4 of [HGI]. + +#### 7.2.1 Classification of traffic + +The classifier treats packets on the basis of the ingress interface, layer 2 header fields (VC or VLAN), IP header fields, layer 4 fields and packet length. The output of the classification process is a set of decisions about the subsequent handling of that packet. The classification process determines the layer 3 and layer 2 egress marking, handling by the congestion management function and (in combination with the forwarding decision) the allocation of the packet to an egress queue. + +NOTE – The text above is imported from clause 6.4.1 of [HGI]. + +##### 7.2.1.1 Requirements for classification of packets received upon the IPI-4 interface + +The requirements in this clause pertain to packets received upon the IPI-4 interface: + +- The DNG is required to classify all packets received on the IPI-4 interface [HGI\_R100]. +- The DNG is required to be able to set the home network priority level for each packet by setting the DSCP bits on the basis of the classification result [HGI\_R101]. +- The DNG is required to assign each packet to the appropriate egress queue, drop the packet, or deliver it to an internal sink, on the basis of the classification result combined with the forwarding decision [HGI\_R102]. + +NOTE 1 – The packet drop in this context refers to an ingress function where packets may be dropped as a direct result of classification: + +- The DNG is required to be able to classify packets based upon the relevant classifiers [HGI\_R103r1]. +- The DNG is recommended to be able to classify packets based upon IP packet size [HGI\_R111]. +- The DNG is recommended to be able to classify packets on a combination of the IPI-4 interface classification parameters [HGI\_R113]. + +Where Ethernet is present on the IPI-4 interface to connect NT, the following requirements are applied: + +- The DNG is required to be able to classify packets based upon Ethernet priority, as defined in [IEEE 802.1D] [HGI\_R115]. +- The DNG is required to be able to classify packets based upon VLAN ID, as defined in [IEEE 802.1Q] [HGI\_R116]. +- The DNG is required to be able to classify packets based upon MAC source address [HGI\_R117]. + +- The DNG is required to provide a configurable MAC source address mask, so that classification is performed only upon bit fields within the MAC source address determined by this source address mask [HGI\_R118]. +- The DNG is required to be able to classify packets based upon MAC destination address [HGI\_R119]. +- The DNG is required to provide a configurable MAC destination address mask, so that classification is performed only upon bit fields within the MAC destination address determined by this destination address mask [HGI\_R120]. +- The DNG is required to be able to classify based upon the Ethernet length/type field [HGI\_R121]. + +NOTE 2 – The text above is imported from clause 6.4.1.1 of [HGI]. + +##### 7.2.1.2 Requirements for classification of packets received on the IPI-3 interfaces + +The following requirements pertain to the classification of packets received on the IPI-3 interfaces which are destined for the AN or are bridged to the HN after multi-field classification. There is an alternative, simpler classification set for locally bridged, transit traffic: + +- The DNG is required to classify all packets received on the IPI-3 interfaces [HGI\_R124]. +- For packets bridged to the HN, the DNG is required to be able to set the home network priority level for each packet by setting the DSCP bits on the basis of the classification result [HGI\_R125]. +- For packets sent to the WAN, the DNG is required to be able to set DSCP and L2 egress markings including VLAN QTAG including priority field, for each packet on the basis of the classification result [HGI\_R126]. +- The DNG is required to assign each packet to the appropriate egress queue, drop the packet, deliver it to application layer logic or deliver it to internal sink, on the basis of the classification result combined with the forwarding decision [HGI\_R127]. +- The DNG is required to be able to classify packets based upon the relevant classifiers (e.g., LAN type, physical port, MAC address, Wi-Fi SSID, IP source/destination address, DSCP, the protocol field in the IP header and TCP/UDP port number) [HGI\_R128r1]. +- The DNG is recommended to be able to classify packets based upon IP packet size [HGI\_R143]. +- The DNG is recommended to be able to classify packets received at the IPI-3 interface on a combination of the classification parameters [HGI\_R145]. + +NOTE – The text above is imported from clause 6.4.1.3 of [HGI]. + +#### 7.2.2 VLAN support at IPI-3 interfaces + +The following requirements pertain to VLAN support on an IPI-3 interface: + +- The DNG is required not to add VLAN headers to any frames which are transmitted on an IPI-3 interface [HGI\_R157]. + +The DNG is required to be able to receive VLAN tagged or priority tagged frames on any of its IPI-3 interfaces. Where these frames are locally bridged to the HN, the VLAN ID and priority tag is required to be forwarded unchanged [HGI\_R158]. + +Where VLAN or priority tagged frames received on the WAN are bridged to the LAN, the VLAN ID and priority tag is recommended to either be forwarded unchanged or removed. This is required to be remotely configurable [HGI\_R159]. + +NOTE – The text above is imported from clause 6.4.2 of [HGI] with modifications. + +#### 7.2.3 Overload protection mechanism + +The following requirements relate to the overload protection mechanism described in clause 7.1.9. This mechanism serves as an example of overload protection; alternative protection mechanisms may be employed. + +The overload protection mechanism utilizes an instance table within the DNG. The instance table is used by the DNG to record instances of services which have been recognized by the relevant classification. The formulation of the instance table is out of the scope of this Recommendation. + +- The DNG is recommended to support a mechanism which: + - i) Differentiates instances of a service on the basis of one or more configured parameters (e.g., IP SA). + - ii) Creates a service instance table entry for each newly recognized instance of the specified service, subject to a configurable limit. This allows the maximum number of service instances to be constrained if required. There needs to be an instance table for each service for which this technique is used. + - iii) Increments a packet count every time a recognized service instance packet is classified. + - iv) Performs a real-time check of each service instance packet count against a configurable upper and lower limit (i.e., , ). + - v) Checks whether a configurable queue length threshold (QueueThreshold) has been exceeded during the same SampleInterval time period. + - vi) When the upper limit is exceeded without the queue length threshold being exceeded, adds a new classification rule to the rules table. This rule, which is a copy of the non-instance specific rule, with the appropriate instance identifier added and the queue changed to that appropriate for an established flow. + - vii) When the lower limit is not met, deletes the instance-specific rule from the rules table. + - viii) Marks the most recently established flow in some way. This would be typically used by a separate process to delete this service instance rule in the event of subsequent congestion. [HGI\_R177] + +NOTE – The text above is imported from clause 6.4.4 of [HGI]. + +#### 7.2.4 QoS mappings + +In case of using class based QoS in which a marker such as DSCP is used for traffic prioritization, each service requiring better QoS treatment needs to be associated with the relevant marking. This requires various considerations including, but not limited to, technical requirements and social importance or recognition. [b-ITU-T Y.1541] gives good guidance for these considerations. + +Also, the marking scheme needs to be well aligned with other marking schemes, particularly in case of using different marking techniques in parallel or connecting different network segments using different marking techniques. In this sense, it is important to consider constructing a mapping table giving the association between different mapping schemes. Several documents, for example clause 6.4.5 of [HGI], provide examples and practice of QoS mappings. + +QoS mapping is not described in this Recommendation and is for further study. + +#### 7.2.5 Class queue structure and scheduling + +##### 7.2.5.1 Queuing into the IPI-3 interfaces + +The following requirements pertain to DNG's IPI-3 output interface class queue structures and scheduling from those queues into the port level: + +- The DNG is recommended to support queuing of data from any source into the IPI-3 output interface (as a result of the classifier) [HGI\_R200]. +- The DNG is required to implement at least four class queues for each IPI-3 output interface [HGI\_R201]. +- When all strict priority queues are empty, the weighted round robin (WRR) queues (Note 1) are required to be serviced according to their weighting priority [HGI\_R207]. + +NOTE 1 – One of the WRR queues would typically be used for WAN ingress best effort traffic, and the other for transit best effort traffic. + +NOTE 2 – The text above is imported from clause 6.4.7.2 of [HGI]. + +#### 7.2.6 Bridging devices within IP-HN-S and IP-HN-P + +The following requirements pertain to the use of priority markings for non-integrated wireless or power line access devices that are connected via Ethernet: + +- The wireless or power line device within IP-HN-P or IP-HN-S is recommended to set its native layer 2 markings for packets it receives from wired or wireless Ethernet by translating the received DSCP value to the native layer 2 markings [HGI\_R211]. +- For packets it sends to the Ethernet, the wireless or power line device within IP-HN-P or IP-HN-S is recommended to translate its native layer 2 marking to DSCP using the correspondence between DSCP and native layer 2 markings [HGI\_R212]. + +NOTE 1 – The text above is imported from clause 6.4.9.1 of [HGI]. + +The following requirements pertain to the interpretation of priority markings for bridging devices within IP-HN-S and IP-HN-P that are typically bridges and switches: + +- Bridging devices within IP-HN-S and IP-HN-P are recommended to determine the QoS treatment by internally translating the received DSCP value to user priority. + +NOTE 2 – The text above is imported from clause 6.4.9.2 of [HGI]. + +## 8 Security + +As home networks are connected to a network function, the home network itself as well as devices connected to it are subject to security attacks that may lead to undesired effects such as loss of IPTV services. Examples of security threats on home networks include denial-of-service (DoS) attacks, malicious software on home network devices and attacks on information that flows or that is stored on the home network device. A DoS attack may make the home network unusable to deliver any services, including IPTV, while malicious software attacks, e.g., viruses on a home network device (e.g., a PC) on the home network may make the device unusable. Attacks on information that is exchanged on a home network or stored in a device on the home network also need to be addressed. If not protected, the information may be compromised, may lead to identity theft and may allow other unauthorized use. + +Thus, it is important that security issues in the home network be addressed to ensure a good quality of experience for IPTV end-users. + +Refer to the document "IPTV security aspects" [b-ITU-T X.1191] for more details on security issues and requirements in home networks. + +### **8.1 Home network security threats** + +Home networks that are used to deliver IPTV services have the same characteristics as defined in [ITU-T X.1111]. Thus, security threats identified in [ITU-T X.1111] also apply to home networks supporting IPTV services. For example, if wireless transmission technologies are used, it may lead to eavesdropping, disclosure, modification and interception attacks. + +Refer to [ITU-T X.1111] for more details on home network security threats. + +### **8.2 Home network security requirements** + +The security function for the home network is required to support the following requirements: + +- the DNG is required to be authenticated by the management system; +- the DNG authentication is required to be service independent; +- the DNG is required to support a specified list of ALGs, and the list can be upgraded; +- the DNG is required to provide a firewall function which is remotely configurable; +- the DNG is required to provide a unique hardware identifier which can be read remotely; +- pairing is required for wireless devices. + +Also, [ITU-T X.1111] identifies requirements for security on the home network based on threats analysis. These requirements also apply to home networks supporting IPTV services. + +For detailed information on these security requirements, refer to [ITU-T X.1111]. + +### **8.3 Link protection requirements** + +Some IPTV content is required to be protected on the communication links in the home network. For this purpose, the IPTV TD and HN-TD are required to implement relevant security mechanisms such as encryption and copy protection to protect IPTV contents during transmission between home network devices. Security mechanisms for link protection are recommended to be optionally activated or deactivated for other contents, e.g., user-generated content, when needed. + +There are many existing technologies that can be used to protect IPTV content during transmission in the home network. Considering the differences of the home network recognized as the primary and secondary domains, the use of a security mechanism in the home network is heterogeneous. Between the DNG and IPTV TD, the content is protected by the SCP function applied by the service provider as it is applied in the other parts of the public network. Once the content is received at the IPTV TD, another security mechanism (e.g., DTCP [b-DTCP]) is applied for the protection between the IPTV TD and HN-TD. Selecting or recommending a technology for link protection purposes is for further study. + +## **9 Interoperability** + +### **9.1 Interoperability between the IPTV access network and home network** + +#### **9.1.1 Interfaces** + +Refer to clause 6 for the interface definition. + +#### **9.1.2 Protocols** + +The DNG is connected to the access network and functional entities beyond it by the protocols specified for the IPTV service. + +NOTE – The protocols specifically needed for the DNG still need to be identified. + +### 9.2 Interoperability among home network devices + +#### 9.2.1 IEC 62481 (DLNA) based devices + +The IPTV TD is recommended to support [IEC 62481-1] and [IEC 62481-2] for interconnection with HN-TD devices, such as display devices. The home network area associated with [IEC 62481-1] and [IEC 62481-2] is IP-HN-S (see Note 1). + +In this model, the IPTV TD and HN-TD are recommended to work as the DMS and DMP, respectively (see Note 2). It should be noted that there might be a possibility for the IPTV TD to act as a DMP, but this depends upon the implementation. + +NOTE 1 – The applicability of IEC 62481 to IP-HN-P and beyond the DNG is for further study. It should be noted that there might be a controversial case where content is distributed beyond the access network. + +NOTE 2 – Some types of HN-TD, such as external PVR may act as a DMS. + +![Diagram illustrating the IEC 62481 in the IPTV home network context. The diagram shows a sequence of components: Access NW (teal box) connected to DNG (white box), which is connected to IP-HN-P (dashed box). IP-HN-P is connected to IPTV-TD (DMS) (green box). IPTV-TD (DMS) is connected to a Secondary domain (shaded box). Inside the Secondary domain, there are two stacked boxes: IP-HN-S (pink box) and IEC 62481 applicable area (teal box). Below these is Non-IP (IP-HN-S) (white box). The Secondary domain is connected to HN-TD (DMP) (green box). The label H.622.1(08)_F9.1 is at the bottom right of the diagram.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +H.622.1(08)\_F9.1 + +Diagram illustrating the IEC 62481 in the IPTV home network context. The diagram shows a sequence of components: Access NW (teal box) connected to DNG (white box), which is connected to IP-HN-P (dashed box). IP-HN-P is connected to IPTV-TD (DMS) (green box). IPTV-TD (DMS) is connected to a Secondary domain (shaded box). Inside the Secondary domain, there are two stacked boxes: IP-HN-S (pink box) and IEC 62481 applicable area (teal box). Below these is Non-IP (IP-HN-S) (white box). The Secondary domain is connected to HN-TD (DMP) (green box). The label H.622.1(08)\_F9.1 is at the bottom right of the diagram. + +**Figure 9-1 – IEC 62481 in the IPTV home network context** + +The HN-TD connected to the IPTV TD is recommended to be allowed to control the IPTV TD remotely. The control capability includes changing channel of broadcast TV, requesting content provided by VoD, presenting EPG/ECG and managing internal a PVR residing in the IPTV TD (Notes 3, 4, 5). + +NOTE 3 – There may be other service cases that are enabled by IEC 62481 or technologies based on it. Further study is needed. + +NOTE 4 – There is a possibility that IEC 62481 cannot provide a complete set of functions required for these services. Further analysis on this technology is needed and, if identified, the gap should be filled by the appropriate group/organization. + +NOTE 5 – There are some system use cases defined in IEC 62481 such as 2-box pull system usage, 2-box push system usage and so on. The applicable usage cases should be identified in the IPTV context. + +#### 9.2.2 UPnP based devices + +NOTE – Refer to Appendix II. + +## 10 Delivery network gateway (DNG) + +This clause describes the delivery network gateway which may be used in the home network to support IPTV services. + +### 10.1 DNG functional overview + +The DNG is an always-on, always-connected device, which acts as the central point for distributing IPTV content in the home network environment. It is supposed that there is only one DNG per household which is connected to a single access network (AN). The use of multiple DNGs and ANs, except the case of using with RF-based broadcasting/cable access network, is for further study. + +The DNG is able to monitor and perform actions on IPTV data flows within the home network, as well as on bidirectional communication flows between the home network and the access network. Given the variety of access network technologies, the DNG architecture has to be flexible in terms of providing the support for different IPI-4 interface types, although there will only be one AN connection at a time. + +The home network can support a number of home network technologies, but only one DNG manages the whole network. + +The DNG is typically not an IPTV service end point. IPTV services terminate on the IPTV TD connected to the DNG through the home network. However, service-specific parameters and functionalities are needed in the DNG to improve efficiency and to enable important features related to provisioning and operations, administration and maintenance (OAM), remote management of the DNG, home network device management, QoS control and security. In addition, the DNG may include built-in features in order to offer local services on the home network or to support terminals not having the necessary functionalities to deliver the service (i.e., legacy TV display used for an IPTV service). + +The DNG can be regarded as an expandable system, both from the software and hardware points of view. However, any additional hardware modules will be external, and will be connected to the DNG via one of the integrated IPI-3 interfaces. + +NOTE 1 – The text above is imported from clause 5.3.1 of [HGI] with modifications. + +NOTE 2 – There are several possible implementations of the DNG device. The clauses above are based on [HGI] with some modifications that are specific to IPTV. + +NOTE 3 – [ISO/IEC 15045-1] also provides a generic framework of a DNG device. Annex A describes [ISO/IEC 15045-1] and necessary considerations for IPTV services. + +#### 10.1.1 DNG functionalities + +The DNG architecture is defined as a set of functionalities, each of which is a task or a set of tasks to be performed through a software program and/or a hardware device/interface/component. The actual detailed requirements for the interfaces and tasks are given in clauses 10.2, 10.3, 10.4, 10.5 and 10.6. + +The information flows that need to be handled by the DNG are defined as follows: + +- Data flows provide information to the end-user. +- Control flows perform the communication session control and connection control functions, dealing with the signalling necessary to set up, supervise and release sessions and connections. +- Management flows are related to actions setting up parameters of a more permanent nature than just a communication session and can be related to DNG as a whole and to resources and parameters related to the protocols handled by the DNG itself. OAM information flows are included here. + +The interfaces and functionalities of a DNG are described as follows. + +**IPI-4 interface:** The physical interface towards the access network and the functionalities related to the IPI-4 interface at layers 1 and 2. Different types of IPI-4 interface are possible, but only one interface is supported at a time. + +**IPI-3 interfaces:** The physical interfaces towards the home network and the related functionalities at layer 1 and 2. A number of different interfaces $I_1 \dots I_n$ , are included. A distinction needs to be made between the interfaces corresponding to different home network technologies (Ethernet, Wi-Fi, USB, etc.) and service-specific interfaces. The LAN technologies are handled at the lower layers, while any service-specific functions are described in the service support block. For example, Wi-Fi security (WEP/WPA keys and ACL management) function is included here. + +**Packet processing:** This function provides the interconnection functions at layer 2 and/or layer 3 for upstream, downstream and transit traffic. This means it provides relaying, forwarding, bridging, and also NA(P)T functions where appropriate. The internal connection functions also include the routing of IP traffic which is going to, or coming from, the DNG itself (local traffic). This function also includes the classification and queuing functions related to QoS management and the filtering and encryption functions related to security, as well as specific service-related functions. These tasks are performed only on the basis of information contained on the Ethernet or IP header; this function does not perform any functions involving an analysis of the packet payload. + +**Control functions:** This function consists of the control communication stacks and the control handling. It covers all the functionality needed to control connection addressing and user authentication (via DHCP or PPP and signalling protocols) and device discovery inside the home (using DHCP). For credentials acquisition, it has a relationship with the security function. + +**Security:** All functionalities defining policies related to network security are contained in this function. It covers protection for the user from security attacks and intrusions and for the operators from malicious use of the broadband link. Thus, security mechanisms and policies such as firewall rules and authentication handling functions are all defined here. + +**QoS:** This function implements the policies for QoS management in the DNG and the home network, as well as any mapping between the IPI-3 side and IPI-4 side. It contains the rules to perform classification and queuing, and priority field mappings. + +**Service support:** This function contains a limited set of functions to support IPTV services, e.g. multicast. + +**Management:** This function consists of the management communication stacks and the management handling. It contains all the functionality needed to manage DNG itself (configuration, firmware upgrade, QoS and security management, etc.), DNG services (provisioning, troubleshooting) and also devices (device configuration) and services (service configuration) reachable through the DNG. + +**Maintenance:** This function contains the processes related to performance control and general diagnostics. + +**Basic system features:** This part contains the powering and the processing performance functions. These two functions describe the basic hardware DNG resources to be shared between the various functional blocks with specific reference to available power (and related issues such as dissipation, reliability, etc.) and general capability of the main processor(s) to process traffic flows (both from a data and a control plane point of view) with a defined level of performance. Note that processing performance is not covered by this Recommendation. + +NOTE – The text above is imported from clause 5.3.2 of [HGI] with modifications. + +### 10.2 IPI-4 interfaces + +A number of possible IPI-4 interface types are identified below along with some specific requirements. The actual interface to be implemented is dependent on the specific operator's choice. + +General requirements: + +- DNG's IPI-4 interface is required to be easily identifiable and separated from the IPI-3 interface(s) [HGI\_R1]. +- DNG is recommended to support at least one IPI-4 interface [HGI\_R2]. + +In addition to the above requirements identified by HGI, the following requirements are applied for IPI-4 interface for IPTV services: + +- IPI-4 interface is required to provide sufficient bandwidth for IPTV services. + +The sufficient bandwidth for each channel includes both the required bandwidth for one video stream, which is derived from its resolution and codec, and a sufficiently engineered margin which is supposed to be from 10% to 50% as a provisional value. This margin is used to take into account additional information for IPTV services, such as overhead of packetization, forward error correction (FEC), audio and data services. Further study is needed to establish a better model for the estimation of sufficient bandwidth. + +NOTE – It is desirable to provide two or more channels simultaneously over a single link in an access or home network. A required or recommended number of channels is for further study. + +#### 10.2.1 IPI-4a interface + +The following requirement applies to the IPI-4a interface: + +- The DNG, if IPI-4a interface equipped, is recommended to support one of the relevant IPI-4a interfaces as listed below: + - [ITU-T G.992.5] (Note 1). + - [ITU-T G.992.1] (Note 2). + - [ITU-T G.992.3] (Note 3). + - [ITU-T G.993.2] (Note 4). + +NOTE 1 – This Recommendation supports a net data rate ranging up to 16 Mbit/s downstream and 800 kbit/s upstream. Support of net data rates above 16 Mbit/s downstream and support of net data rates above 800 kbit/s upstream are optional. + +NOTE 2 – This Recommendation supports a net data rate ranging up to 6.1448 Mbit/s downstream and 640 kbit/s upstream. + +NOTE 3 – This Recommendation supports a net data rate ranging up to 8 Mbit/s downstream and 800 kbit/s upstream. Support of net data rates above 8 Mbit/s downstream and support of net data rates above 800 kbit/s upstream are optional. + +NOTE 4 – This Recommendation supports a bidirectional net data rate up to 200 Mbit/s. + +It is well recognized that the performance of DSL depends on the distance of the DSL modem from the local exchange as well as the physical condition of metallic cable. Also, it should be noted that transmission performance, such as packet loss, is affected by electronic and magnetic noise. Applying the nominal performance metrics mentioned in these Recommendations may be problematic in the consideration of service quality. Further study is needed on the operational condition of DSL as well as operational guidelines for it. + +Functional requirements of a non-IPTV nature are defined for each DSL Recommendation. Refer to [HGI] for details. + +#### 10.2.2 IPI-4b interface + +The following requirements apply to the IPI-4b interface: + +- The DNG, if IPI-4b interface equipped, is required to support Ethernet 10BASE-T or 100BASE-TX technology for twisted pair (Cat-5 or Cat-6) [HGI\_R32]. +- The DNG, if IPI-4b interface equipped, is required to support the related Ethernet protocols at layer 2, with VLAN management (support for untagged frames and IEEE 802.1 Q-tagged frames containing priority-tagged information (IEEE 802.1p) and VLAN-ID information) on the IPI-4 interface [HGI\_R33]. + +NOTE – The above requirements are from [HGI]. + +#### **10.2.3 IPI-4c for coaxial interface** + +The following requirement applies to the IPI-4c interface: + +- The DNG is recommended to support the relevant interface for coaxial connection with the NT. + +#### **10.2.4 IPI-4d for wireless interface** + +The following requirement applies to the IPI-4d interface: + +- The DNG is recommended to support the relevant interface for wireless connection with the NT. + +#### **10.2.5 IPI-4e for optical access network** + +The following requirement applies to the IPI-4e interface: + +- The DNG, if it contains an NT function, is required to comply with one of the following optical access networks. + - [ITU-T G.983.x] (Note 1). + - [ITU-T G.984.x] (Note 2) + - [IEEE 802.3] (Note 3). + +NOTE 1 – A typical configuration of [ITU-T G.983.x] considered in this list is to provide 622 Mbit/s downstream for up to 32 ONTs. There are other configurations allowed by this series of Recommendations. + +NOTE 2 – A typical configuration of [ITU-T G.984.x] considered in this list is to provide 2.48 Gbit/s downstream for up to 32 ONTs. There are other configurations allowed by this series of Recommendations. + +NOTE 3 – A typical configuration of [IEEE 802.3] considered in this list is to provide 1.25 Gbit/s downstream, which is decreased to 1 Gbit/s after 8B/10B demodulation, for up to 32 ONTs. There are other configurations allowed by this standard. + +In the PON architecture, a maximum number of ONTs connected to a single OLT depends on the operational condition such as distance between OLT and ONT. For example, a longer optical access fibre may require a restriction on branching of optical fibre in order to provide sufficient optical signal to the ONT. This results in a reduced number of ONTs and thus increased bandwidth for each ONT. In such cases, the available service may be different from the table. + +As with other point-to-multipoint access networks, reduction of the required total bandwidth for an OLT is possible if the access network entity supports multicast packets. This effect depends on the proportion of multicast traffic to the whole IPTV traffic. Service availability taking into account this effect is for further study. + +### **10.3 IPI-3 interfaces** + +#### **10.3.1 IPI-3a interface** + +The following requirement applies to the IPI-3a interface: + +- The DNG is recommended to support the relevant IPI-3a interface for a power line home network. + +#### **10.3.2 IPI-3b interface** + +The following requirement applies to the IPI-3b interface: + +- The DNG is required to contain an Ethernet [IEEE 802.3] and [ISO/IEC 8802-1] switch for IPI-3b with sufficient bandwidth for IPTV services, with at least two ports. These ports are required to support auto-sensing between full or half duplex, auto-sensing between 10 and 100 Mbit/s, and auto-sensing between MDI and MDI-X [HGI\_R39]. + +#### **10.3.3 IPI-3c interface** + +The following requirement applies to the IPI-3c interface: + +- The DNG is recommended to support the relevant IPI-3c interface for a home PNA. + +#### **10.3.4 IPI-3d interface** + +The following requirement applies to the IPI-3d interface: + +- The DNG is recommended to support the relevant IPI-3d interface for a coaxial home network. + +#### **10.3.5 IPI-3e interface requirements** + +If wireless interface is used for IPI-3, the following requirements apply: + +- The DNG, when equipped with an IPI-3e interface, is recommended to support one of the IPI-3e specifications listed below. + - IEEE 802.11a [IEEE 802.11]. + - IEEE 802.11b [IEEE 802.11]. + - IEEE 802.11g [IEEE 802.11]. + +It is well recognized that the performance of a wireless LAN depends on the operational environment such as the distance between transmitter and receivers and may be unstable for IPTV services. Applying the nominal bandwidth mentioned in these specifications for the consideration of relevancy may be problematic. Further study is needed for requirements and guidelines on operational conditions of wireless LANs for IPTV services. + +Functional requirements of a non-IPTV nature are defined for each wireless LAN specification. Refer to [HGI] for details. + +In the following clauses, additional requirements that are needed to support IPTV services are described. Requirements that are not specific to IPTV services can be found in [HGI] + +### **10.4 Packet processing** + +#### **10.4.1 Support of routed model and extensions – IPI-3 side** + +##### **10.4.1.1 NAT function** + +The following requirements apply to the NAT function of the DNG: + +- NAT function is required not to interfere with the interaction between the DNG and functions of the service provider network. +- NAT function is required not to prevent interaction between functions of the server provider network and IPTV terminal devices on the home network. + +Protocols that are used on interfaces between a service provider network and home network are out of scope of this Recommendation. + +##### **10.4.1.2 IPI-3-side DHCP requirements** + +The following requirements apply to the DHCP server function of the DNG: + +- If IPv4 is used in a home network, an IPI-3-side DHCP server is recommended to be available on DNG [HGI\_R81]. +- If IPv4 is used in a home network, the DNG is recommended to support a means to remotely configure the DHCP server [HGI\_R82]. + +- The DHCP server is required to support fixed IP address allocation to specific device names or MAC addresses to be used in combination with port forwarding or DMZ host [HGI\_R85]. +- The DHCP server can optionally provide the same IP address to each device [HGI\_R86]. +- The DNG is required to support the use of public IP addresses (that are within the proper subnet mask defined for the IP connection to the AN) on the HN, and properly route the device traffic [HGI\_R88] (Note 1). + +NOTE 1 – It is assumed that devices with public IP addresses will be manually configured. + +NOTE 2 – The text above is imported from clause 6.3.2.3 of [HGI]. + +#### **10.4.2 Support of hybrid model and extensions** + +The following requirements apply to operation of the DNG: + +- The DNG is required to support configuring and enabling multiple instances of bridging between WAN side logical interfaces (PVC, VLAN, etc.) and LAN side physical interfaces (Ethernet port, SSID, etc.) [HGI\_R90]. +- The DNG is required to support configuring and enabling one or more IPI-4 logical interfaces and one or more physical IPI-3 interfaces [HGI\_R91]. +- The DNG is required to run both bridging and routing simultaneously [HGI\_R92]. +- The DNG is required to be able to forward traffic to the correct connection in the case of having multiple connections such as multiple PVCs, multiple PPPoE sessions, multiple VLANs, etc. [HGI\_R93]. + +NOTE – The text above is imported from clause 6.3.3 of [HGI]. + +#### **10.4.3 Session initiation and support** + +The following requirement applies to operation of the DNG: + +- The DNG is required to operate in an "always-on" mode for connections. If a DSL access network is used, the DNG is required not to time out DSL sessions (IP and PPP) and is required to automatically re-establish any sessions after disconnection, lease expiration or loss and restoration of power [HGI\_R96]. + +NOTE – The text above is imported from clause 6.3.4 of [HGI]. + +### **10.5 Network services support** + +The following requirements apply to network services on the DNG: + +- A dynamic DNS client is recommended to be provided on the DNG to associate DNG IP address to a user-chosen domain in the DNS system [HGI\_R348]. +- As an alternative to the above requirement, the dynamic DNS client can optionally be implemented in the management functions [HGI\_R349]. +- The DNG is required to have a unique hardware ID for authentication and remote management purposes, composed of an organizationally unique identifier (OUI) and serial number [HGI\_R350]. +- The DNG is required to support a time server client to obtain the time and date [HGI\_R351]. +- The DNG is required not to implement any explicit function to reset time and date [HGI\_R355]. + +NOTE – The text above is imported from clause 6.6 of [HGI]. + +#### 10.5.1 Application layer gateway (ALG) functions + +The following requirements apply to ALG functions on the DNG: + +- The DNG is recommended to support an ALG function to support interoperability with NAT mechanisms; however, the protocols to be used are out of the scope of this Recommendation. +- DNG ALGs are required to be able to be switched off in case of conflicts with external devices using STUN for NAT traversal [HGI\_R358]. + +NOTE – The text above is imported from clause 6.6.1 of [HGI]. + +#### 10.5.2 Multicast support + +The following requirements apply to multicast support on the DNG: + +- The DNG is recommended to support IGMP v1/v2 in the IPv4 environment [IETF RFC 2236] or multicast listener discovery (MLD) in the IPv6 environment [IETF RFC 2710]. +- The DNG is recommended to support v3 queries function according to [IETF RFC 3376] [HGI\_R385]. +- If a multicast stream data flow coming from the AN is NOT terminated in the DNG, the DNG is recommended to keep a record of which IPTV-TDs are subscribed to which multicast group [HGI\_R386]. +- If a multicast stream data flow coming from the AN is NOT terminated in the DNG, the DNG is required to forward inbound multicast packets only to those physical interfaces which are connected to devices that have joined the specific multicast group [HGI\_R387]. +- If a multicast stream data flow coming from the AN is terminated in the DNG, the DNG is required to implement a proxy mechanism, which subscribes to appropriate the multicast groups on the AN on behalf of devices on the HN, and realizes a mapping between the AN multicast stream format to the HN-defined stream format [HGI\_R388]. +- Where there is a multicast stream in the home network, the DNG is required to support a capability to perform a link layer multicast to unicast translation [HGI\_R389]. + +NOTE – The text above is imported from clause 6.6.3 of [HGI]. + +### 10.6 IGMP functionality + +#### 10.6.1 IGMP proxy + +An IPTV TD is recommended to support IGMP proxy for IGMP v2 and IGMP v3. If more than one upstream interface is available (e.g., different VLANs) the following rules apply. + +**"Simple mode", only one upstream interface for IGMP/multicast:** If only one upstream interface needs to support multicast/IGMP, it is recommended, if possible, to select the proxy interface by static configuration or a dynamic mechanism such as a multicast default route using the DHCP option 121 (classless static route option). + +**"Extended mode", different upstream interfaces for IGMP/multicast:** More than one upstream interface needs to support multicast/IGMP (e.g., different service VLANs). In this scenario, the multicast groups/multicast channels need to be configured on the corresponding interfaces; e.g., 239/8 on interface #1 and 232/8 on interface #2. The proxy needs to separate the address spaces, e.g., an IGMP report on interface #1 must not include information about multicast groups/channels on interface #2. The device is required to support a mechanism to configure (assign) the multicast groups/channels to the corresponding upstream interfaces. This can be done by using static configuration (pre-configured device, using a GUI, etc.) or a dynamic mechanism. + +**"Forking mode":** In this mode, IGMP reports are sent to more than one upstream interface. Queries will be answered on all upstream interfaces which are configured for "forking mode"; reports include information about all multicast groups/channels the CPE is subscribed to. It is within the responsibility of the receivers of the membership reports to take action on the received reports. In a standard scenario, only one of the receivers will forward multicast traffic to avoid duplicate traffic. Other network components can act on the membership reports (e.g., change filters or QoS settings) without forwarding the traffic (see Figure 10-1). + +![Diagram illustrating IGMP proxy in forking mode. A CPE with IGMP proxy/forking and two upstream interfaces receives an IGMP join (10.1.1.1, 239.1.2.3) from an STB. It forwards the IGMP report to two multicast routers. Multicast router #1 forwards the traffic for (10.1.1.1, 239.1.2.3). Multicast router #2 drops the IGMP and does not forward traffic.](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +The diagram shows a central CPE device labeled "CPE with IGMP proxy/forking and two upstream interfaces". An arrow labeled "IGMP join (10.1.1.1, 239.1.2.3) from STB" points to it from the left. Two arrows labeled "IGMP" point from the CPE to two separate routers. The top router is labeled "Multicast router #1 forwards traffic". An arrow labeled "Traffic for (10.1.1.1, 239.1.2.3)" points from this router. The bottom router is labeled "Multicast router #2 drops IGMP, does not forward traffic". A small text "H.622.1(08)\_F10.1" is at the bottom right. + +Diagram illustrating IGMP proxy in forking mode. A CPE with IGMP proxy/forking and two upstream interfaces receives an IGMP join (10.1.1.1, 239.1.2.3) from an STB. It forwards the IGMP report to two multicast routers. Multicast router #1 forwards the traffic for (10.1.1.1, 239.1.2.3). Multicast router #2 drops the IGMP and does not forward traffic. + +**Figure 10-1 – IGMP proxy in forking mode** + +#### 10.6.2 Source-specific multicast + +The proxy is required to support source-specific multicast (SSM) in the standard SSM address range 232/8. SSM is recommended to be supported in other address ranges as well. All IGMP v3 filter modes are recommended to be supported. + +#### 10.6.3 Filter + +L3 filters for IGMP are recommended to be supported. It is also recommended to allow the exclusion of certain multicast addresses or address ranges from the proxy functionality (e.g., UPnP). Such membership reports are not forwarded to the upstream interface(s) and not reported as answer on an IGMP query from the network. This avoids unnecessary states for multicast groups which have only local relevance. It is also recommended to provide a mechanism to configure the filters (e.g., analogue-to-port forwarding rules or firewall rules). + +## 11 Network management + +### 11.1 Remote management + +When IPTV services are deployed, a large number of IPTV terminal devices (IPTV-TDs) will be managed by the service or network provider, and these devices may need to be managed remotely. IPTV services also need to be managed remotely. Thus, it is very important for service or network providers to have a standardized way to remotely manage numerous IPTV terminal devices and IPTV services in an efficient and economical way. + +Remote management architecture and functional requirements necessary to build standardized systems for remote management of IPTV terminal devices and IPTV services in the home network are for further study. + +### **11.2 QoS management functions on the DNG** + +QoS management is a critical network management aspect for ensuring the correct delivery of the services. Definition and mechanisms of QoS management are covered in QoS clauses 7.1 and 7.2. + +NOTE – The text above is imported from clause 5.4.2 of [HGI]. + +### **11.3 Security management functions on the DNG** + +Security and privacy are critical issues in home environment management. Most end-users are very concerned about unauthorized access 'into' their home and about the privacy of their data. Therefore, the DNG includes manageable security elements to enhance the confidence of the end-user about these concerns. This mainly concerns the remote management of the firewall and NAT capabilities of the DNG. The user may also wish to have the ability to 'hide' some end devices from the service provider, so that the service provider does not have full visibility of the HN. + +NOTE – The text above is imported from clause 5.4.3 of [HGI]. + +### **11.4 Performance monitoring and diagnostics, and troubleshooting functions on the DNG** + +Any DNG system-level fault (e.g., hardware, operating system or software related) can optionally be detected and communicated to the service or network provider. Three scenarios are possible and all are supported: + +- Remote diagnostic tests, to check the state of the different components of the DNG. These tests are either scheduled periodically or launched by system operator requests. +- Performance monitoring will also be available in order to see statistics (for example, at the network level). +- Events are generated on detection of a possible fault within the system. + +Some examples of faults which need to be detected are: + +- Malfunction of hardware modules. +- Malfunction of the main software components of the DNG (to detect failures, partial crashes, etc., that affect the normal operation of the DNG). + +NOTE – The text above is imported from clause 5.4.5 of [HGI]. + +### **11.5 Local management application for the DNG** + +In order to provide better support for the DNG, a local management interface may be needed to complement the remote management. + +The local management interface is the access method the end-user uses to view or make changes to DNG configuration, end-user managed services, end-user managed devices and other 'safe' settings. + +Three levels of management are present in the DNG, with the following precedence (high to low): + +- End-user device management functional block can manipulate all managed objects in the DNG, including lower order user rights. +- Administrator management can manipulate objects that do not interfere with end-user device management functional block or managed service operation. It can manage local user access rights (e.g., additional firewall rules, specific NAT for unmanaged devices). +- Users can only manipulate objects when allowed by the administrator (e.g., URL access). + +The local user interface access is completely controlled by DNG's firmware itself. This will require access control in order to limit this to a local administrator. The administrator will have the ability to change settings for certain managed services or devices, but general users will only have the ability to view (some of) these managed areas. In Figure 11-1, an overview of the local management interface is provided. On the access network side, the end-user device management functional block + +will configure parameters of this interface through the CPE WAN management protocol management interface. + +![Figure 11-1 – Local management interface overview. The diagram shows a 'Management function (end-user device management functional block)' connected via a 'Remote management protocol' to an 'IPI-4 interface' within a 'DNG' (Device Network Gateway). Inside the DNG, the 'IPI-4 interface' connects to an 'RM client', which in turn connects to a 'Local management application' containing an 'LM remote UI server'. Above the DNG is a crossed-out smiley face icon. The 'Local management application' connects to an 'IPI-3 interface' within the DNG, which then connects via 'http + HTML' to an 'LM remote UI client'. This client is connected to a user interface consisting of a monitor, a set-top box, and a smiley face icon. Text labels describe the 'Local management interface' for managing the RM client from the gateway, the 'LM local UI' for managing the RM client from the gateway, and the 'LM remote UI' for managing the RM client on the gateway from a device on the HN. The diagram is labeled H.622.1(08)_F11.1.](85e2327652d513a7fee8fdbf97ad06f1_img.jpg) + +Figure 11-1 – Local management interface overview. The diagram shows a 'Management function (end-user device management functional block)' connected via a 'Remote management protocol' to an 'IPI-4 interface' within a 'DNG' (Device Network Gateway). Inside the DNG, the 'IPI-4 interface' connects to an 'RM client', which in turn connects to a 'Local management application' containing an 'LM remote UI server'. Above the DNG is a crossed-out smiley face icon. The 'Local management application' connects to an 'IPI-3 interface' within the DNG, which then connects via 'http + HTML' to an 'LM remote UI client'. This client is connected to a user interface consisting of a monitor, a set-top box, and a smiley face icon. Text labels describe the 'Local management interface' for managing the RM client from the gateway, the 'LM local UI' for managing the RM client from the gateway, and the 'LM remote UI' for managing the RM client on the gateway from a device on the HN. The diagram is labeled H.622.1(08)\_F11.1. + +**Figure 11-1 – Local management interface overview** + +In the DNG, a local management remote user interface server (LM remote UI server) will host a web-based local management remote user interface, which can be accessed from any end devices equipped with a browser and located in the HN. + +The other possible user interface, the local management local user interface (LM local UI), implies that a user interface is directly accessed on the DNG and therefore the DNG must be able to connect to a display device and some input device (such as an infrared remote control). This is not supported in this Recommendation. + +NOTE – The text above is imported from clause 5.4.6 of [HGI]. + +### 11.6 IPTV service information report + +For operational purposes network management function is recommended to generate and report information regarding IPTV services. + +NOTE – Privacy and security of subscribers/consumers should be considered when implementing IPTV service information reporting functionalities. + +# Annex A + +## Considerations on ISO/IEC 15045-1 for IPTV services + +(This annex forms an integral part of this Recommendation) + +### A.1 Introduction + +[ISO/IEC 15045-1] describes the model and key functions of the DNG. Since the key subject of [ISO/IEC 15045-1] is a generic model applicable to various implementation scenarios, regardless of IP or non-IP environment, some specific considerations are needed for the IPTV service. This annex provides considerations for IPTV-specific issues. + +### A.2 Comparison of terminology + +Since [ISO/IEC 15045-1] is developed by a different standards body, it uses different terminology than that used in this Recommendation. For the convenience of the reader, the following table is provided for comparison of terminology used in both documents. + +**Table A.1 – Comparison of terminology with [ISO/IEC 15045-1]** + +| [ISO/IEC 15045-1] | Corresponding term | Note | +|-----------------------------------|--------------------|-------------------------------------------------------------------------------| +| HAN | Home network (HN) | If it means all the networks and entities placed beyond the DNG. | +| | IP-HN-P | If it means only the network and entities directly connected with the DNG. | +| | IPI-3 interface | If it specifically means the HN-side interface. | +| HGI
    (HAN to gateway interface) | IPI-3 interface | The same term is used for a different meaning (HGI, home gateway initiative). | +| LAN | Home network | | +| PAN | Home network | | +| RG | DNG | | +| WAN | Access NW | If it means the network and related entities connected to the DNG. | +| | IPI-4 interface | If it specifically means the AN-side interface. | +| WGI
    (WAN to gateway interface) | IPI-4 interface | | + +### A.3 Packet processing and interfaces of the DNG + +[ISO/IEC 15045-1] allows the use of both IP and non-IP at the interface, IPI-4 or IPI-3, of the DNG. In the case of IPTV, the network protocol used by the IPTV TD is limited to IP by its definition. Although it is possible to use a non-IP protocol, for example [b-IEEE 1394], beyond the IPTV TD as a part of the secondary domain, as depicted in the architecture, the access and home network around the DNG need to be an IP-based network except in cases where the DNG is incorporated in the IPTV TD. A DNG without IPI-3 and IPI-4, specified in this Recommendation, is not relevant for IPTV services. + +The interface and traffic across the DNG is described in clause 5 of [ISO/IEC 15045-1]. The packet processing in the sense of QoS and multicast at the gateway device, which are important aspects for IPTV, is not mentioned in the standard. The technical information relevant for the home network supporting IPTV services is described in clauses 7 and 10. A [ISO/IEC 15045-1] compliant device is also required to meet these requirements. + +## **A.4 Security consideration** + +In clauses 6 and 7 of [ISO/IEC 15045-1] security issues necessary for the DNG are described. Some considerations are described in the context of remote control of consumer electronic devices from an outside controller. Different from an IPTV TD, some kinds of consumer electronic devices potentially carry a risk caused by physical action that may result in the loss of physical property and, in the worst case, serious damage to the human body. While a security mechanism addressing such risk is important, IPTV requires some additional considerations of, for example, content protection. The risks to which IPTV content and associated information are exposed and the methods addressing them are described in [b-ITU-T X.1191]. + +In addition to the protection of devices and information, designing a DNG product requires the operational aspects of IPTV services. Limiting types of traffic across the DNG is a way of enhancing the security. However, there is a potential risk of intercepting a necessary packet by such a mechanism. Designing the filtering mechanism requires detailed analysis of IPTV traffic and associated protocols. + +# Appendix I + +## An explanation of the layered model for the IPTV home network + +(This appendix does not form an integral part of this Recommendation) + +![Conceptual diagram of the layered model for the IPTV home network. The diagram shows two horizontal layers: the Application model (top) and the Transport model (bottom). Each layer is divided into three columns: a model label column, an 'NW segment category' column, and a 'Device category' column. The Application model's NW segment category includes 'Primary domain' and 'Secondary domain'. Its Device category includes 'Primary terminal' and 'Secondary terminal'. The Transport model's NW segment category includes 'IP-HN' and 'Non-IP-HN'. Its Device category includes 'IP terminal' and 'Non-IP terminal'. A vertical yellow 'Access gateway' is positioned between the NW segment and Device categories, spanning both layers. The diagram is labeled 'H.622.1(08)_FI-1' at the bottom right.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +| | NW segment category | | Device category | | +|-------------------|---------------------|----------------|------------------|--------------------| +| Application model | Primary domain | Access gateway | Primary terminal | Secondary terminal | +| | Secondary domain | | | | +| Transport model | IP-HN | | IP terminal | Non-IP terminal | +| | Non-IP-HN | | | | + +H.622.1(08)\_FI-1 + +Conceptual diagram of the layered model for the IPTV home network. The diagram shows two horizontal layers: the Application model (top) and the Transport model (bottom). Each layer is divided into three columns: a model label column, an 'NW segment category' column, and a 'Device category' column. The Application model's NW segment category includes 'Primary domain' and 'Secondary domain'. Its Device category includes 'Primary terminal' and 'Secondary terminal'. The Transport model's NW segment category includes 'IP-HN' and 'Non-IP-HN'. Its Device category includes 'IP terminal' and 'Non-IP terminal'. A vertical yellow 'Access gateway' is positioned between the NW segment and Device categories, spanning both layers. The diagram is labeled 'H.622.1(08)\_FI-1' at the bottom right. + +**Figure I.1 – Conceptual diagram of the layered model** + +The layered functional architecture includes two layers represented as models. Those are transport and application models. The detailed descriptions are presented as follows: + +- a) The **transport model** is responsible for linking the network clients together and transferring the data packets across the network. The transport model described in this appendix corresponds to lower layers of the OSI reference model (basically, the bottom three layers). Thus, it includes the function of the physical layer, data link layer and network layer. The transport model is for further study. +- b) The **application model** is responsible for allowing users to interact with the networks, including defining the format of data, designing the service and designing the interface. There are many services at present, such as TV gaming, TV education, linear TV, etc. Providing more IPTV services may help drive users toward widespread use of IPTV, so it is necessary to create more new types of service. The format of data in different services can vary widely, so the design of the data format is an important component of the application functional model. The application model is the main subject of [ITU-T H.622]. + +Functional components are relevantly defined for each model. These components can be associated with the home network architecture in this Recommendation as shown in Table I.1 below. + +**Table I.1 – Explanation of components** + +| Architecture of IPTV home network | Application model | Transport model | Note | +|------------------------------------------|--------------------------|---------------------------------------------|-----------------------------------------------------------------| +| DNG | DNG | DNG | | +| Primary domain (IP-HN-P) | Primary domain | IP home network | For IPTV, the primary domain is limited to the IP home network. | +| Secondary domain | Secondary domain | IP home network or proprietary home network | | +| IP secondary domain (IP-HN-S) | Secondary domain | IP home network | A part of secondary domain. | +| Non-IP secondary domain (PR-HN-S) | Secondary domain | Proprietary home network | A part of secondary domain. | +| IPTV TD | Primary terminal | IP terminal | | +| HN-TD | Secondary terminal | IP terminal or proprietary terminal | | + +# Appendix II + +## UPnP-based home network for IPTV services + +(This appendix does not form an integral part of this Recommendation) + +The UPnP audio/video architecture consists of a media renderer, media server and control point (refer to UPnP A/V architecture document, [b-UPnP DA]). + +The media renderer obtains content from the media server and renders it (e.g., displays, decodes). For example, the role of media renderer is playback through a TV set, MP3 player, etc. + +The media server is used to make content available on the home network and transfer it to the terminal devices. It supports multiple transfer protocols and data formats and has the functionality to convert from one format to another one in the real time. + +The main tasks of the control point are synchronization and management of A/V devices in a home network. It allows an end-user to select, play, pause and stop content from a media server and display it on a media renderer. The control point is able to control the media renderer characteristics, e.g., brightness, contrast, volume, etc. An example of a control point is a TV set with remote control. + +All devices that support UPnP should have implemented a basic UPnP terminal device profile. + +Additionally, IPTV TD may be compatible with the UPnP specification for the media server in order to locate and transmit content, for instance, to the HN device and other devices in the home network. Content could be selected remotely from the IPTV NW or locally from a hard disk. The end-user has the possibility of recording A/V files by using the UPnP scheduled recording functionality. IPTV TD also works as a control point in order to allow an end-user to select and control content. When the HN IPTV TD works as a standalone device, it should also have media renderer functionality as an option. + +An HN device should play the role of media renderer and control point. In that case, the HN device uses content delivered from a media server. The connection between the IPTV TD and HN device is established automatically by using UPnP protocols (e.g., SOAP, HTTP) and based on an XML discovery mechanism. Control point functionality allows the end-user to locate, choose and control content flows from the media server. The transport protocol and data format are chosen automatically depending on which of them are supported by the media renderer. The IPTV end system architecture which uses UPnP is shown in Figure II.1. + +![Diagram of UPnP home network architecture for IPTV end system. It shows an IPTV network cloud connected to a DNG box, which is connected to an HN IPTV TD (Media server control point). The HN IPTV TD is connected to an HN TD (Media renderer control point) and an Other UPnP terminal via UPnP communication arrows. Content arrows show data flow from the IPTV network through the DNG and HN IPTV TD to the HN TD and Other UPnP terminal.](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) + +``` +graph LR; IPTV_network[IPTV network] -- Content --> DNG[DNG]; DNG -- Content --> HN_IPTV_TD[HN IPTV TD
    Media server control point]; HN_IPTV_TD -- UPnP communication --> HN_TD[HN TD
    Media renderer control point]; HN_IPTV_TD -- UPnP communication --> Other_UPnP_terminal[Other UPnP terminal]; HN_IPTV_TD -- Content --> HN_TD; HN_IPTV_TD -- Content --> Other_UPnP_terminal; +``` + +Diagram of UPnP home network architecture for IPTV end system. It shows an IPTV network cloud connected to a DNG box, which is connected to an HN IPTV TD (Media server control point). The HN IPTV TD is connected to an HN TD (Media renderer control point) and an Other UPnP terminal via UPnP communication arrows. Content arrows show data flow from the IPTV network through the DNG and HN IPTV TD to the HN TD and Other UPnP terminal. + +H.622.1(08)\_FII-1 + +**Figure II.1 – UPnP home network architecture for IPTV end system** + +NOTE – Since UPnP is not qualified under A.5, this issue is described as an appendix. Considering the importance of UPnP, the content of this appendix will be moved into a relevant part of the main body of this Recommendation when the UPnP specification is approved by another organization such as ISO/IEC. + +# Appendix III + +## Consideration of retransmission of free-to-air broadcast content + +(This appendix does not form an integral part of this Recommendation) + +## III.1 Middleware aspect + +IPTV services can comprise interactive TV applications. [b-ITU-R BT.1699] and [b-ITU-R BT.1722] are Recommendations of harmonization of declarative and procedural content format, respectively, for broadcast content. These Recommendations would enable proper presentation and interactivity for broadcast programme content over IPTV. + +## III.2 Content protection issue + +The following is the consideration for retransmission of free-to-air broadcast content, from the viewpoint of [b-ITU-R BT.1736]: + +- Retransmitted free-to-air broadcast content should be handled such as to conform to the content protection assigned by the content provider. + +### III.3 Privacy protection issue + +[b-ITU-R BT.2052] describes overall analysis of an end-user's privacy protection in an interactive broadcast chain. In the case of retransmission of free-to-air broadcast content, clauses 4 through 6 of this report provide useful information on this issue. + +## III.4 Delivery control of retransmission + +In a case where delivery control for retransmission of free-to-air broadcast content is needed, the IPTV system is required to provide such functionality. [b-ITU-T J.281] describes the requirements for similar control. + +## III.5 Provision of emergency broadcast + +Recognizing the need and the importance of emergency broadcasting, ITU-R has developed the Recommendations [b-ITU-R BT.1774] and [b-ITU-R BO.1774]. Support of this function by IPTV systems may be required depending on national regulations. + +# Appendix IV + +## Example configurations for an IP-based home network + +(This appendix does not form an integral part of this Recommendation) + +Figure IV.1 shows an example of a physical configuration of an IP-based home network. Two home network areas, IP-HN-P and IP-HN-S, can overlap physically as shown in the bottom diagram of Figure IV.1. IPTV-TD deals with IPTV-related traffic only. Devices which do not handle IPTV traffic are required to be connected to IP-HN-S. + +![Diagram of physically separated IP-HN configuration Diagram of logically separated IP-HN configuration](838c31609fac483fa2c01c7896a2fd6d_img.jpg) + +Physically separated IP-HN configuration + +The diagram shows a green box labeled 'DNG' connected to a blue box labeled 'IP-HN-P'. A red arrow points from the DNG to the IP-HN-P. The IP-HN-P is connected to two purple boxes labeled 'IPTV TD'. The first IPTV TD is connected to a purple box labeled 'IP-HN-S', which is in turn connected to a yellow box labeled 'HN TD'. The second IPTV TD is connected to the IP-HN-S box. The IP-HN-P box has a vertical line labeled 'IPI-1' at its bottom. The IP-HN-S box has a vertical line labeled 'IPI-0' at its bottom. + +Logically separated IP-HN configuration + +The diagram shows a green box labeled 'DNG' connected to a blue box labeled 'IP-HN-P'. A red arrow points from the DNG to the IP-HN-P. The IP-HN-P is connected to two purple boxes labeled 'IPTV TD'. The first IPTV TD is connected to a purple box labeled 'IP-HN-S', which is in turn connected to a yellow box labeled 'HN TD'. The second IPTV TD is also connected to the IP-HN-S box. The IP-HN-P box has a vertical line labeled 'IPI-1' at its bottom. The IP-HN-S box has a vertical line labeled 'IPI-0' at its bottom. The text 'H.622.1(08)\_FIV-1' is written to the right of the HN TD box. + +Diagram of physically separated IP-HN configuration Diagram of logically separated IP-HN configuration + +Figure IV.1 – Example configurations for an IP-based home network + +## Bibliography + +- [b-ITU-T J.281] Recommendation ITU-T J.281 (2006), *Requirements for multichannel video signal transmission over IP-based fibre network*. +<> +- [b-ITU-T Y.1541] Recommendation ITU-T Y.1541 (2006), *Network performance objectives for IP-based services*. +<> +- [b-ITU-T X.1191] Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects*. +<> +- [b-ITU-R BO.1774] Recommendation ITU-R BO.1774 (2007), *Use of satellite and terrestrial broadcast infrastructures for public warning, disaster mitigation and relief*. +<> +- [b-ITU-R BT.1699] Recommendation ITU-R BT.1699 (2005), *Harmonization of declarative content format for interactive TV applications*. +<> +- [b-ITU-R BT.1722] Recommendation ITU-R BT.1722 (2007), *Harmonization of the instruction set for the execution engine for interactive TV applications*. +<> +- [b-ITU-R BT.1736] Recommendation ITU-T BT.1736 (2006), *Broadcasting of redistribution signalling for television*. +<> +- [b-ITU-R BT.1774] Recommendation ITU-R BT.1774 (2007), *Use of satellite and terrestrial broadcast infrastructures for public warning, disaster mitigation and relief*. +<> +- [b-ITU-R BT.2052] Report ITU-R BT.2052 (2005), *Protection of end-users' privacy in interactive broadcasting systems*. +<> +- [b-IEEE 1394] IEEE 1394 (1995), *IEEE standard for a high performance serial bus*. +<[http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?tp=&isnumber=11289&arnumber=526693&punumber=3871](http://ieeexplore.ieee.org/xpls/abs_all.jsp?tp=&isnumber=11289&arnumber=526693&punumber=3871)> +- [b-UPnP DA] UPnP Forum (1999), *Device Architecture 1.0*. +<> +- [b-DTCP] Digital Transmission Licensing Administrator (2007), *DTCP Volume 1 Supplement E Mapping DTCP to IP*. +<> + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44572d51d56e5ebca47b7c8af717cad078f6c0d2 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2c19f922fb76ff84569f3fa59327089c7e4e57930abc358fc39f4de2c374f08 +size 66432 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..115ef870cef3cdfb6ff2e4caa471a2b604f0badd --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:534fa441e3bf745e03d3c596e468b945571b10df8428c4acb5712748b3ad9ecd +size 80626 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5e7e030d12bd6e3d7066319e25e6304f6718cd6 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ef3ee6d5e99367a02adf45cae4791061b0e6c6abaa15453c9f16e0729a36805 +size 13173 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055 +size 6859 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0896268cdfd99728a274aadef10996ec33b6cf26 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f35faf4bb8d9ddb659719ce135ba09c574f0403601c87b85984647de87e438d +size 12445 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8cf38f061f132bb97054745bd4e4fa500e0262e --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6b70c7e96eb4706830a50b893f844b11119ab259c4f6cc079a1009a5ffc0973 +size 26529 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1019574291d11d3813ae4feb5331b9e3cb047517 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:026c23275434fbddf507068e845498f50545aad063a769ce11e6db35f9ee2801 +size 21122 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09e94c4f22f849e190f40874fcdf04b46ae3a861 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc26dd5c1539e74e63ca074a061117f1dad2e6cab606c807dd96e2a7e139fd3d +size 101230 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85cef800d28ec2a45afc7afc97c8cbbf854aa15e --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:902f56cd5a56f9852b11aeca8d62e9fded84faa7211128513795078cdd68bdae +size 13270 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0851c4256496c4d89365ccae105402c2a04250d --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50e01e3a357a7bb60928da3021009b6141155a8dc63eaf9d4613aabdd156ace1 +size 39849 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4abc69c003fc7f74adb65cc2ab38428f1becf5eb --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f39c16daddddab3453ea649ad1979ca8d4ff4032d49a592aa62df38144d4cdb9 +size 174455 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6fdb4e2ca4eee0763a250bc199558e31f95f315 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a20ee4af1dba14ebd447b916a1799411bc91e5338e9c376d7ac756c69092df2 +size 153044 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a983ba6654345aed877f89e070d101ca166a269 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfd9318facfeab545c443195727dc8f077171c4ca45b87427e997bc9bbb3c781 +size 43844 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b7ca4bf9162c7dd971503bcc1a350ed1b02d5e9 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff71d064bd1200922d94b0b02e02e7a1280d52432b911c6e58786e50945c5436 +size 63193 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5d8038c7b11f5566c51bd8d6e92fb74cb9f4203 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:549b13580f2fd43e2eb65e60d4bb1edc62998fc8eab6ca593201dccdcc3f21a5 +size 57094 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6d1e3568f105b6b2fa519aaa78c94e46a80a04b --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e450bd8a7b15d73b71d9c57cb398b63270926c82bdcc09e29620b5b21e553f3f +size 33591 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6acc5a28bdbfa4089e8201b0ea1990336af0e14 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:334f23074a02733d4abf18778f416a2ea28346b4abddbe072c904d9948b2eddd +size 155305 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22b6f2bc66741d680f08ffc2da873821fbf29058 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a2e53cf412d70423c6a01845832b1fddfccd7ffed72a5aa9c5e49e77705bb37 +size 48049 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36f33fa4de7b2690df8eb2df4ceef7ad5ea714c8 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1ed332a897e9d5162f10544cface774ed83b594529013ee65639f702fccfdcb +size 26636 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9263ddc175acab8c8f0cae2166f65dfd396a8915 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2685ed481a08cddd5280d11933c75234aeb3aa7ea9ad561a8a49eb070012222 +size 107135 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..033ce6a805ac53f68ebad9468fc28d5770737d0b --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec81bdc2c48a7d95b624f7c7e4dec602a692fff1a61745a633565b8b2551fe2a +size 21191 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d65f79f13168a8dae3d43f9dd4e4fa794d52e2a --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f586bd920d28245721c31ab1432f21974dd4e1ca40d4bfc808bd533c65b87d7 +size 30480 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02931f03ba752ee6d5c42e8fd111ac879acc6b6e --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c395cabf821e4c6ce9d0e4121b5142e80b3f2a5c13c778fdac8cafa3061793b +size 67519 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62218a5e4c48eaeef0e9ffb64d4c9d4ef133ab79 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e060827add21b94ab9893c0396f15dcaa9d66a6039a45db2548097d39be4fc75 +size 21253 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8e15609398b224c7f0d89e392761fdabae2e72c --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a6c7374508eb1290a7a187b2756a86a1d3a6f5666de9b08f1baddcd2883758c +size 21993 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..803a15f79ee3cbba1a795d069875345e11cd42a0 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fade44cb62ea19e154d5fbdc8aad10298b0793a621a8b29e4c0df9ef1567ef49 +size 27357 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d766dc1877abf4c3b7e1a38485fc3755896343f0 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43250f059fea7b26825b5a21334b16b46cdd4ae09e0fb876bcc1426f13d4455a +size 52043 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..928ae008863cacd2bdfa7334c11d2900cb81e39b --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e1b0d6271acb20eda9d47b064b985ff65fed5fa21012bae350ae9ec744b540e +size 20691 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e80500825706d338278f0613e1ddabf0dd15df88 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04997170ced6350bba8591f22102fd05af1753cfeab3079e179661b131453d9a +size 192501 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71fd25acb7a2f45053d8aa7b870a86d00944c0fe --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a88700ff4e53ee6377406ea9158039c7cf873dd429e09aed1165106f226eece +size 142305 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e363d8dcd0cb02d6753e5e3de6d01b2c35daaec0 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ba764f1a0f4921dd591311f40630d543662cedba1bc074222c801e26528f145 +size 53861 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9dcc7d3101e3c5a1c4ca0e92a24bce9fae94156 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0a47e528af8136a71c7d38cba5fe36243f4bc0145c070c8d52ea4dc7514cc4c +size 34891 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c1db3850298736cc7d531d63b7f5d29dce33cf1 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b72377609507ccc39532832130e68d7b257154a9270e84edf8a411eadb87b89c +size 37568 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09f8d34da3a1d7fda7b1b6c57d061044491e8189 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dd88a89cf5913f3f0dff171dd0043a8fdd93059ef421c2d6f86191095f28257 +size 25584 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d9413c5928284e829ba73543d2f75437a8d1906 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4df5cb0d6130b613df35f8d70a80f75ae9c2bde3339ae56f6ef8c6b63414c8a +size 32474 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.625-201703-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11a607515e9e6de3c25ccd75ebf43905006b9c13 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49fdb1e76e2633b8cfed8a8369c1f220d7818b9ab008045e1736ee4c6bae96fd +size 67538 diff --git a/marked/H/T-REC-H.625-201703-I_PDF-E/raw.md b/marked/H/T-REC-H.625-201703-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c304e6e9dc2d54df7d17cb58d950bbb8a67ab6b2 --- /dev/null +++ b/marked/H/T-REC-H.625-201703-I_PDF-E/raw.md @@ -0,0 +1,1843 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.625** + +(03/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Broadband, triple-play and advanced multimedia +services – Advanced multimedia services and applications + +# --- **Architecture for network-based speech-to- speech translation services** + +Recommendation ITU-T H.625 + +**ITU-T** + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "ITU" is written in a bold, blue, sans-serif font. Below "ITU", the words "International Telecommunication Union" are written in a smaller, blue, sans-serif font. + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'. + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.625 + +# Architecture for network-based speech-to-speech translation services + +## Summary + +Recommendation ITU-T H.625 defines the system architecture for network-based speech-to-speech translation (S2ST) on the basis of Recommendation ITU-T F.745 and serves as a technical introduction to the subsequent definitions of detailed system components and protocols. The scope of this Recommendation is to describe the functional architecture and mechanisms of network-based S2ST, interface protocols between S2ST modules, and a workflow of the network-based S2ST system. + +This revision includes additional information to clarify that Recommendation ITU-T H.625 could be applicable to both face-to-face communication and remote communication. The modality conversion markup language (MCML) is also enhanced for adding more flexibility. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.625 | 2010-10-14 | 16 | 11.1002/1000/10992 | +| 2.0 | ITU-T H.625 | 2017-03-01 | 16 | 11.1002/1000/13190 | + +## Keywords + +Automatic speech recognition (ASR), machine translation (MT), modality conversion markup language (MCML), speech-to-speech translation (S2ST), text-to-speech synthesis (TTS). + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-------|--------------------------------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Term defined in this Recommendation ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 3 | +| 6 | System functional architecture ..... | 4 | +| 6.1 | System overview ..... | 4 | +| 6.2 | Functional components..... | 8 | +| 6.3 | Protocols ..... | 9 | +| (1) | MCML root..... | 10 | +| (2) | User..... | 11 | +| (2-1) | Transmitter and Receiver ..... | 12 | +| (3) | Server..... | 14 | +| (3-1) | Request and Response ..... | 15 | +| (3-2) | Routing ..... | 16 | +| (3-3) | InputUserProfile ..... | 17 | +| (3-4) | TargetOutput..... | 19 | +| (3-5) | Input..... | 20 | +| (4) | History ..... | 30 | +| 6.4 | General workflow for modality conversion ..... | 31 | +| | Annex A – MCML 2.0 schema ..... | 34 | +| | Appendix I – Examples of physical level architecture workflow examples of modality conversion using MCP..... | 43 | +| I.1 | Shared S2ST client for two-party communication ..... | 43 | +| I.2 | Personal S2ST client communication..... | 44 | +| I.3 | Cross-modality communication..... | 44 | +| | Bibliography..... | 46 | + +# Introduction + +Speech-to-speech translation (S2ST) technologies, which translate speech in a source language to speech in a target language, are an effective means of facilitating communication beyond language boundaries for those who do not speak a common language. Developing an S2ST system requires the construction of automatic speech recognition (ASR), machine translation (MT) and text-to-speech (TTS) synthesis components. Many ASR, MT and TTS systems for different language pairs have been developed independently all over the world. If these systems could be connected together through a network, then S2ST systems spanning a greater number of language pairs can be achieved. To realize this network-based S2ST technology by connecting various distributed components, this Recommendation describes how to combine those individual S2ST systems and defines architectural requirements for the network-based S2ST system. + +# Recommendation ITU-T H.625 + +# Architecture for network-based speech-to-speech translation services + +# 1 Scope + +This Recommendation defines the following items for designing a platform of the network-based speech-to-speech (S2ST) system: + +- a functional architecture and mechanisms of network-based S2ST; +- interface protocols between S2ST modules; and +- a workflow of the network-based S2ST system. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T F.745] Recommendation ITU-T F.745 (2010), *Functional requirements for network-based speech-to-speech translation services*. +- [IETF RFC 2279] IETF RFC 2279 (1998), *UTF-8, a transformation format of ISO 10646*. +- [IETF RFC 2396] IETF RFC 2396 (1998), *Uniform Resource Identifiers (URI): Generic Syntax*. +- [IETF RFC 2616] IETF RFC 2616 (1999), *Hypertext Transfer Protocol – HTTP/1.1*. +- [IETF RFC 2818] IETF RFC 2818 (2000), *HTTP Over TLS*. +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- [W3C XML1.0] W3C XML1.0 (2008), *Extensible Markup Language (XML) 1.0*. +- [W3C XML Schema] W3C XML Schema Part 2 (2004), *XML Schema Part 2: Datatypes Second Edition*. +- [ISO 639-1] ISO 639-1 (2002), *Codes for the representation of names of languages – Part 1: Alpha-2 code*. +- [ISO 639-2] ISO 639-2 (1998), *Codes for the representation of names of languages – Part 2: Alpha-3 code*. +- [ISO 639-3] ISO 639-3 (2007), *Codes for the representation of names of languages – Part 3: Alpha-3 code for comprehensive coverage of languages*. +- [ISO 639-4] ISO 639-5 (2010), *Codes for the representation of names of languages – Part 4: General principles of coding of the representation of names of languages and related entities, and application guidelines*. +- [ISO 639-5] ISO 639-5 (2008), *Codes for the representation of names of languages – Part 5: Alpha-3 code for language families and groups*. + +NOTE – In this Recommendation, "[ISO 639]" refers collectively to the five parts of ISO 639 listed above. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 adaptive differential pulse code modulation (ADPCM)** [b-ITU-T G.701]: Compression algorithms that achieve bit rate reduction through the use of adaptive prediction and adaptive quantization. + +**3.1.2 machine translation (MT)** [ITU-T F.745]: Text in a source language is converted by computers into text in a target language that has the same meaning as the original text in the source language. + +**3.1.3 modality conversion (MC)** [ITU-T F.745]: The conversion of data to different formats and languages using automatic speech recognition (ASR), machine translation (MT) and text-to-speech (TTS) systems. + +**3.1.4 modality conversion markup language (MCML)** [ITU-T F.745]: An XML schema that serves as a data description for data exchanged among modality conversion modules. + +**3.1.5 modality conversion protocol (MCP)** [ITU-T F.745]: The communication protocol which transfers data between modality conversion (MC) clients and servers using HTTP(S)/RTP as defined in [IETF RFC 2616], [IETF RFC 2818] and [IETF RFC 3550]. This protocol transfers the MCML comprising of Multimodal Information (MI) data which is input into MC clients by users and MC results which are obtained by MC servers. + +**3.1.6 multimodal information (MI)** [ITU-T F.745]: The information input into MC clients by users via multimodal sensors. + +**3.1.7 multipurpose Internet mail extensions (MIME)** [b-ITU-T J.200]: An application layer protocol. It features a content architecture to facilitate multimedia data such as text other than US-ASCII code, sound, image, etc. to be handled in Internet mails. + +**3.1.8 N-best** [ITU-T F.745]: The most likely "N" hypotheses obtained from modality conversion engines. + +**3.1.9 pulse code modulation (PCM)** [b-ITU-T G.701]: A process in which a signal is sampled, and the difference between each sample of this signal and its estimated value is quantized and converted by encoding to a digital signal. + +NOTE – The estimated values of the signal are calculated by a predictor from the quantized difference signal. + +**3.1.10 speech-to-speech translation (S2ST)** [ITU-T F.745]: Speech in a source language is translated into speech in a target language. + +**3.1.11 text-to-speech synthesis (TTS)** [b-ITU-T P.10]: A process generates a speech signal from text codes. It is usually composed of the two parts: + +- a language-dependent text processing part (the high level processing part), which generates from the character string (by reading rules, vocabulary and semantic analysis) a set of phonetic, prosodic, etc., parameters which are used by: + - an acoustical signal generating part, the synthesiser itself, which generates the audible speech. + +## 3.2 Term defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 automatic speech recognition (ASR)**: A system that can recognize continuous speech, often having phoneme-sized references, using lexical, syntactic, semantic, and pragmatic knowledge, and + +reacts appropriately (therefore having interpreted the message and found the corresponding action to be taken). + +NOTE – This definition is the same as that given for *continuous speech understanding system* in [b-ITU-T P.10]. + +**3.2.2 dialogue management (DM):** The process which is capable of managing the states of dialogues as well as creating appropriate responses for input texts and other modalities. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|---------------------------------------------| +| ADPCM | Adaptive Differential Pulse Code Modulation | +| ASR | Automatic Speech Recognition | +| DM | Dialogue Management | +| HTTP | Hypertext Transfer Protocol | +| HTTPS | Hypertext Transfer Protocol Secure | +| ID | Identifier | +| IPA | International Phonetic Alphabet | +| MC | Modality Conversion | +| MCML | Modality Conversion Markup Language | +| MCP | Modality Conversion Protocol | +| MI | Multimodal Information | +| MIME | Multipurpose Internet Mail Extensions | +| MT | Machine Translation | +| PCM | Pulse Code Modulation | +| RTP | Real-time Transport Protocol | +| S2ST | Speech-to-Speech Translation | +| TTS | Text-To-Speech synthesis | +| UCS | Universal Character Set | +| URI | Uniform Resource Identifier | +| UTC | Universal Time, Coordinated | +| UTF-8 | UCS Transformation Format-8 | +| XML | Extensible Markup Language | + +# 5 Conventions + +In this Recommendation: + +- The expression "**is required to**" indicates a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. +- The expression "**is recommended to**" indicates a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +- The expression "**can optionally**" indicates an optional requirement which is permissible, without implying any sense of being recommended. + +# 6 System functional architecture + +## 6.1 System overview + +This clause defines the functional architecture of network-based S2ST systems. Figure 6-1 shows the network-based S2ST system with data flow. The processing steps for network-based S2ST are as follows: + +- Step 1: A user's speech is input into an S2ST client +- Step 2: A speech signal of the user's speech is transferred to an automatic speech recognition (ASR) module +- Step 3: A transcription of the original speech obtained by the ASR module goes back to the original S2ST client and is transferred simultaneously to a machine translation (MT) module +- Step 4: A translation into a target language for the original speech obtained by the MT module goes to a target S2ST client and is transferred simultaneously to a text-to-speech synthesis (TTS) module +- Step 5: A synthesized speech signal in the target language is transferred to the target S2ST client +- Step 6: The synthesized speech is output from the target S2ST client. + +Data can be transferred through the same network, or different ones. To help understand the data flow of network-based S2ST, the case in which all data is transferred using the same network is illustrated in Figure 6-1. + +Figure 6-2 shows the functional model extracted from Figure 6-1. + +The system functional architecture for network-based S2ST requires the following components: S2ST clients, and ASR, MT and TTS servers. The S2ST clients function as MC clients, which request modality conversion (MC) of multimodal information (MI) input by users and which receive the MC results from the MC servers. The ASR, MT and TTS servers function as MC servers that convert the modality of the MI input by users. + +To achieve communication between MC clients and servers, a communication protocol is required, namely the modality conversion protocol (MCP) with the modality conversion markup language (MCML). Focusing on communication via MCP, MCP clients send MCML to the MCP servers, and MCP servers receive MCML from the MCP clients. + +Figure 6-3 shows the logical architecture of MCP client and server. This architecture is specified in a single MCP client and server combination. Each of the engines for ASR, MT and TTS is identified as an MC function in the MCP server. + +The above architecture for the network-based S2ST can also be setup in a standalone system in which MCML is used as an internal interface. + +![Diagram of a network-based S2ST system showing data flow between two speakers (Language A and Language B) through a central network and various servers (ASR, MT, TTS).](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +The diagram illustrates a network-based S2ST (Speech-to-Speech Translation) system. At the top, two speakers are shown: one for Language A (left) and one for Language B (right). The system components and data flow are as follows: + +- S2ST client for language A speaker:** Receives "1. Speech in language A" from the speaker and sends "6. Synthesized speech" back to it. It also interacts with the network via "2. Speech signal", "3. Transcription", "4. Translation", and "5. Synthesized speech signal". +- S2ST client for language B speaker:** Receives "1. Speech in language B" from the speaker and sends "6. Synthesized speech" back to it. It also interacts with the network via "2. Speech signal", "3. Transcription", "4. Translation", and "5. Synthesized speech signal". +- ASR server (Language A):** Contains "Lexicon speech data" for "Language A". It receives "2. Speech signal" and sends "3. Transcription". +- ASR server (Language B):** Contains "Lexicon speech data" for "Language B". It receives "2. Speech signal" and sends "3. Transcription". +- MT server (Language A):** Contains "Parallel corpus lexicon" for "Language A" and "Language B". It receives "3. Transcription" and sends "4. Translation". +- MT server (Language B):** Contains "Parallel corpus lexicon" for "Language B" and "Language A". It receives "3. Transcription" and sends "4. Translation". +- TTS server (Language B):** Contains "Lexicon speech data" for "Language B". It receives "4. Translation" and sends "5. Synthesized speech signal". +- TTS server (Language A):** Contains "Lexicon speech data" for "Language A". It receives "4. Translation" and sends "5. Synthesized speech signal". +- Private/wide area public communication network:** The central hub where all components interact. It is represented by concentric circles and receives data from the clients and servers and sends data back to them. + +The data flow is numbered 1 through 6, showing the sequence from speech input to synthesized speech output for both languages. + +Diagram of a network-based S2ST system showing data flow between two speakers (Language A and Language B) through a central network and various servers (ASR, MT, TTS). + +H.625(17)\_F6-1 + +Figure 6-1 – A network-based S2ST system with data flow + +![Functional model of the network-based S2ST system](d4af765160d04ecef538e5066006dc77_img.jpg) + +This diagram illustrates the functional model of a network-based S2ST system. At the center is a cloud labeled "Wide area public communication network". To the left, two "MC client" boxes are shown. Each contains an "S2ST client for language A speaker" (or "language B speaker") and a "Conversion between speech and speech signal" block. A double-headed arrow between these clients is labeled "Communication between users who speak different languages". To the right, six "MC server" boxes are connected to the network cloud. These servers include: + +- ASR server: Conversion from speech signal to text in language A +- MT server: Conversion from text in language A to text in language B +- TTS server: Conversion from text to speech signal in language B +- ASR server: Conversion from speech signal to text in language B +- MT server: Conversion from text in language B to text in language A +- TTS server: Conversion from text to speech signal in language A + +The text "H.625(17)\_F6-2" is located at the bottom right. + +Functional model of the network-based S2ST system + +Figure 6-2 – Functional model of the network-based S2ST system + +![Logical architecture of MCP client and server](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +This diagram shows the logical architecture of an MCP client and server. On the left, a pink oval labeled "Multimodal information (MI)" is connected to an "MCP client" box. The client box contains an "Input and output processing function" (green) which interacts with "MI processing function" (light green), "MCML processing function" (yellow), and "Communication processing function" (orange). These three functions are connected to a central cloud labeled "Private/wide area public communication network". On the right, an "MCP server" box contains "MI processing function" (light green), "MCML processing function" (yellow), and "Communication processing function" (orange), which all interact with a "Modality conversion (MC) function" (green). The text "H.625(17)\_F6-3" is located at the bottom right. + +Logical architecture of MCP client and server + +Figure 6-3 – Logical architecture of MCP client and server + +To accomplish network-based S2ST, there are two approaches to communication via MCP, namely: MC client-server communication (Figure 6-4), and MC relay communication (Figure 6-5). To realize relay communication between MC servers, each server needs to be switched to MCP client mode from MCP server mode, enabling the information transfer. To confirm the quality of the output from each MCP server, the MCP server output can be sent back to each client using relay communication. + +![Diagram of MC client-server communication for network-based S2ST. It shows an MC client on the left and three MC servers on the right. Each server has a different modality conversion function: ASR engine, MT engine, and TTS engine. All are connected via 'Client-server communication' lines to the client's communication function.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +The diagram illustrates the MC client-server communication architecture for network-based S2ST. On the left, an **MC client** is shown, which contains an **MCP client** layer. This layer includes three functions: **Input and output processing function**, **MI processing function**, **MCML processing function**, and **Communication function**. The **Input and output processing function** is connected to the other three functions. On the right, there are three **MC server** units, each containing an **MCP server** layer. Each **MCP server** layer includes the same four functions as the client: **Input and output processing function**, **MI processing function**, **MCML processing function**, and **Communication function**. The **Communication function** in each server is connected to a specific **Modality conversion function**: the top server has an **ASR engine**, the middle server has an **MT engine**, and the bottom server has a **TTS engine**. All three **Communication functions** in the servers are connected via lines labeled **Client-server communication** to the **Communication function** in the **MCP client** layer of the **MC client**. The diagram is labeled H.625(17)\_F6-4 at the bottom right. + +Diagram of MC client-server communication for network-based S2ST. It shows an MC client on the left and three MC servers on the right. Each server has a different modality conversion function: ASR engine, MT engine, and TTS engine. All are connected via 'Client-server communication' lines to the client's communication function. + +Figure 6-4 – MC client-server communication for network-based S2ST + +![Diagram of MC relay communication for network-based S2ST showing functional components and communication paths.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +The diagram illustrates the functional architecture for network-based S2ST (Speech-to-Speech Translation) using MC relay communication. It features three main communication paths between an MC client and multiple MC servers. + +**MC Client (Left):** Contains an **Input and output processing function** (green) connected to a stack of three functions: **MI processing function** (green), **MCML processing function** (yellow), and **Communication function** (orange). This stack is part of an **MCP client** (light blue) which is situated within an **MC client** (green) and an **MCP server** (purple). + +**MC Server 1 (Top Right):** Contains a stack of **MI processing function** (green), **MCML processing function** (yellow), and **Communication function** (orange). This stack is part of an **MCP client** (light blue) within an **MCP server** (purple) and an **MC server** (blue). It is connected to a **Modality conversion function (ASR engine)** (pink). + +**MC Server 2 (Middle Right):** Contains a similar stack of **MI processing function** (green), **MCML processing function** (yellow), and **Communication function** (orange). This stack is part of an **MCP client** (light blue) within an **MCP server** (purple) and an **MC server** (blue). It is connected to a **Modality conversion function (MT engine)** (green). + +**MC Server 3 (Bottom Right):** Contains a stack of **MI processing function** (green), **MCML processing function** (yellow), and **Communication function** (orange). This stack is part of an **MCP client** (light blue) within an **MCP server** (purple) and an **MC server** (blue). It is connected to a **Modality conversion function (TTS engine)** (dark blue). + +**Communication Paths:** + +- Client-server communication:** Bidirectional arrows connect the **Communication function** of the MC client to the **Communication function** of each MC server. +- Relay communication:** Bidirectional arrows connect the **Input and output processing function** of the MC client to the **Modality conversion function** of each MC server. + +H.625(17)\_F6-5 + +Diagram of MC relay communication for network-based S2ST showing functional components and communication paths. + +**Figure 6-5 – MC relay communication for network-based S2ST** + +## 6.2 Functional components + +The functional architecture of the MC is required to consist of the following components: MC client and MC server. The clients and servers contain a set of MI processing, MCML processing, and communication functions. These clients and servers have an input and output processing function and a modality conversion function, respectively. + +### **6.2.1 MCP client** + +The MCP client function is required to request modality conversion of the MI input by users. The MCP client has two different transfer functions: one is for user and device information as well as MI and MC results; and the other is for MC history through relay services. The MCP client is required to have the component functions described in the following clauses. + +#### **6.2.1.1 Input and output processing function** + +The input and output processing function is required to input MI from users and output MI to users. + +#### **6.2.1.2 Multimodal information processing function** + +The MI processing function is required to encode the MI digitized by the input and output processing function into feature expressions. This function can be implemented either in the MCP client or the MCP server. + +#### **6.2.1.3 Communication processing function** + +The communication processing function is required to handle MCP to send MCML formatted data to the MCP server. + +### **6.2.2 MCP server** + +The MCP server responds to MCP client requests for modality conversion of MI. The MCP server is required to be composed of the functions described in the following clauses. + +#### **6.2.2.1 Communication processing function** + +The communication processing function is required to handle the modality conversion protocol (MCP) to receive the MCP client requests, and to send MC results of MI back to the MCP client from the MC server. + +#### **6.2.2.2 Multimodal information processing function** + +This is the same function described in clause 6.2.1.2. This function is needed in the MCP server, in case it is not implemented in the MCP client. + +#### **6.2.2.3 Modality conversion function** + +The MC function is required to convert the modality of MI in accordance with the MCP client request. Each processor for MC is denoted as an MC engine. + +## **6.3 Protocols** + +Modality conversion is realized by communication between the MCP client and the MCP server, by exchanging MCML using the MCP. The architecture described in clause 6.2 (Figure 6-1) is required to be supported by the communication protocols shown in Figure 6-6. + +![Figure 6-6: Interface between MCP client and MCP server. The diagram shows a 'Multimodal information (MI)' circle on the left connected to an 'MCP client' box. Inside the client box, an 'Input and output processing function' (green) is connected to three stacked boxes: 'MI processing function' (green), 'MCML processing function' (yellow), and 'Communication processing function' (orange). These three boxes connect to a dashed box labeled 'Wide area public communication network'. Inside the network box, a line labeled 'MCP' connects to an 'MCP server' box on the right. Inside the server box, the 'Communication processing function' (orange) is connected to three stacked boxes: 'MCML processing function' (yellow), 'MI processing function' (green), and 'Modality conversion (MC) function' (green). The label 'H.625(17)_F6-6' is at the bottom right.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 6-6: Interface between MCP client and MCP server. The diagram shows a 'Multimodal information (MI)' circle on the left connected to an 'MCP client' box. Inside the client box, an 'Input and output processing function' (green) is connected to three stacked boxes: 'MI processing function' (green), 'MCML processing function' (yellow), and 'Communication processing function' (orange). These three boxes connect to a dashed box labeled 'Wide area public communication network'. Inside the network box, a line labeled 'MCP' connects to an 'MCP server' box on the right. Inside the server box, the 'Communication processing function' (orange) is connected to three stacked boxes: 'MCML processing function' (yellow), 'MI processing function' (green), and 'Modality conversion (MC) function' (green). The label 'H.625(17)\_F6-6' is at the bottom right. + +**Figure 6-6 – Interface between MCP client and MCP server** + +### 6.3.1 MCP + +The MCP is a communication protocol based on HTTP [IETF RFC 2616] or HTTPS [IETF RFC 2818]. The MCML containing MI and MC results is embedded into multipurpose Internet mail extensions (MIME) format with MI binary data attached. Real-time transport protocol (RTP) [IETF RFC 3550] is used as an option. Figure 6-7 shows the MCP structure. + +![Figure 6-7: MCP structure. The diagram shows a blue box labeled 'MCP' containing a teal box labeled 'HTTP(S)/RTP'. Inside the 'HTTP(S)/RTP' box is a dark blue box labeled 'MIME', which contains two white boxes: 'MCML' and 'Binary data'. The label 'H.625(10)_F6-7' is at the bottom right.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +Figure 6-7: MCP structure. The diagram shows a blue box labeled 'MCP' containing a teal box labeled 'HTTP(S)/RTP'. Inside the 'HTTP(S)/RTP' box is a dark blue box labeled 'MIME', which contains two white boxes: 'MCML' and 'Binary data'. The label 'H.625(10)\_F6-7' is at the bottom right. + +**Figure 6-7 – MCP structure** + +### 6.3.2 MCML + +The MCML is an extensible markup language (XML) schema [W3C XML Schema]. The message exchanged between MCP clients and servers is formatted in XML [W3C XML1.0] with the MCML schema. + +MCML includes: + +- user profile, user's demand for output and device information of the MCP client; +- service type and output information of the MCP server; and +- history of the MC process through multiple MCP servers. + +Universal character set (UCS) transformation format-8 (UTF-8) [IETF RFC 2279] encoded text is required for MCML. The MCML schema is defined using the diagram and table representations described below, and its text representation is contained in Annex A. + +#### (1) MCML root + +The root structure of MCML is shown in Figure 6-8. The root element of MCML is annotated as "MCML". An attribute of this element is required to indicate the MCML version information. The MCML element holds three child elements: "User", "Server" and "History". Table 6-1 shows the definition of the attribute and child elements. + +![Figure 6-8: MCML root structure diagram. The MCML element has an 'attributes' box containing 'Version'. It has child elements: 'User' (0..1), 'Server' (1..∞), and 'History' (0..∞).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +graph LR + MCML[MCML] --> attributes[attributes] + subgraph attributes + Version[Version] + end + MCML --> User[User] + MCML --> Server[Server] + MCML --> History[History] + style User fill:none,stroke:none + style Server fill:none,stroke:none + style History fill:none,stroke:none + +``` + +Figure 6-8: MCML root structure diagram. The MCML element has an 'attributes' box containing 'Version'. It has child elements: 'User' (0..1), 'Server' (1..∞), and 'History' (0..∞). + +Figure 6-8 – MCML root structure + +Table 6-1 – Definition of attributes and child elements of an "MCML" element + +| MCML | | | | | +|------------|---------|-----------------------------|-------|-----------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | Version | Version information of MCML | 2.0 | 1 | +| Children | User | See (2) | | 0 or 1 | +| | Server | See (3) | | 1 or more | +| | History | See (4) | | 0 or more | + +#### **(2) User** + +The "User" element contains user and device information for the MC client. The structure of this element is shown in Figure 6-9. The communication between a single transmitter and single/multiple receivers is required to be through MCML. + +![Figure 6-9: Structure of a 'User' element diagram. The User element contains 'Transmitter' (0..1) and 'Receiver' (1..∞) child elements.](21ad58fee90f2be50708ff541d225507_img.jpg) + +``` + +graph LR + User[User] --> Transmitter[Transmitter] + User --> Receiver[Receiver] + style Transmitter fill:none,stroke:none + style Receiver fill:none,stroke:none + +``` + +Figure 6-9: Structure of a 'User' element diagram. The User element contains 'Transmitter' (0..1) and 'Receiver' (1..∞) child elements. + +Figure 6-9 – Structure of a "User" element + +Table 6-2 – Definition of the child elements of a "User" element + +| User | | | | +|------------|-------------|------------|-----------| +| Annotation | Name | Definition | Quantity | +| Children | Transmitter | See (2-1) | 0 or 1 | +| | Receiver | | 0 or more | + +##### (2-1) Transmitter and Receiver + +##### Transmitter: + +This "Transmitter" element contains device and user information for an MC client, which sends MI to MC servers. The child elements are "Device" and "UserProfile", shown below in Figure 6-10 and in Table 6-3. Multiple users' profiles are required when sharing a single device among multiple users. + +![Figure 6-10: Structure of a 'Transmitter' element. The diagram shows a 'Transmitter' box on the left connected by a line with a diamond symbol to a box on the right. This box contains two sub-elements: 'Device' and 'UserProfile'. The 'Device' element has a small '+' sign in its top right corner. The 'UserProfile' element also has a '+' sign in its top right corner and a '1..∞' multiplicity indicator below it. The diagram is labeled 'H.625(10)_F6-10' at the bottom right.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Figure 6-10: Structure of a 'Transmitter' element. The diagram shows a 'Transmitter' box on the left connected by a line with a diamond symbol to a box on the right. This box contains two sub-elements: 'Device' and 'UserProfile'. The 'Device' element has a small '+' sign in its top right corner. The 'UserProfile' element also has a '+' sign in its top right corner and a '1..∞' multiplicity indicator below it. The diagram is labeled 'H.625(10)\_F6-10' at the bottom right. + +Figure 6-10 – Structure of a "Transmitter" element + +Table 6-3 – Definition of child elements of a "Transmitter" element + +| Transmitter | | | | +|-------------|-------------|-------------|-----------| +| Annotation | Name | Definition | Quantity | +| Children | Device | See (2-1-1) | 0 or 1 | +| | UserProfile | See (2-1-2) | 0 or more | + +##### Receiver: + +This "Receiver" element contains the device and user profile information of MC clients which receives MC results. To receive the MC results from MC servers, the receiver device functions as an MCP server. + +The "Receiver" element has the same structure as the "Transmitter" described above in this clause. The MCML is required to handle not only a single "Receiver" but also multiple "Receivers" in order to send MI and MC results to multiple MCP servers. + +##### (2-1-1) Device + +The "Device" element has the MC client's device information. The structure of the "Device" is shown in Figure 6-11. The child element is named "Location" and the attributes of this element are defined in Table 6-4. + +To communicate between MC clients and servers, their addresses in the network are required. The child element of the "Location" element is the "URI" element which has the information of the URI [IETF RFC 2396], and the URI identifies the location of the MC client in the network. + +Since the environment for users may change depending on the user's location, the "GlobalPosition" element is required which contains the physical location of the MC client device in the real world. The "GlobalPosition" has a set of attributes consisting of "Longitude" and "Latitude". + +![Figure 6-11: Structure of 'Device' element. A tree diagram showing 'Device' containing 'URI' and 'Location'. 'Location' contains 'GlobalPosition', which has attributes 'Longitude' and 'Latitude' under a group named 'grp Location'.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +graph LR + Device[Device] --- URI[URI] + Device --- Location[Location] + Location --- GlobalPosition[GlobalPosition] + GlobalPosition --- grpLocation[grp Location] + grpLocation --- Longitude[Longitude] + grpLocation --- Latitude[Latitude] + +``` + +H.625(10)\_F6-11 + +Figure 6-11: Structure of 'Device' element. A tree diagram showing 'Device' containing 'URI' and 'Location'. 'Location' contains 'GlobalPosition', which has attributes 'Longitude' and 'Latitude' under a group named 'grp Location'. + +**Figure 6-11 – Structure of "Device" element** + +**Table 6-4 – Definition of child elements of a "Location" element and attributes of a "GlobalPosition" element** + +| Location | | | | | +|-----------------------|----------------|-------------------------------------------------------------------------------|--------------|-----------------| +| Annotation | Name | Definition | Value | Quantity | +| Children | URI | Uniform resource identifier | string | 0 or 1 | +| | GlobalPosition | See below | | 0 or 1 | +| GlobalPosition | | | | | +| Annotation | Name | Definition | Value | Quantity | +| Attributes | Longitude | The longitude of the physical location of the client device in the real world | float | 1 | +| | Latitude | The latitude of the physical location of the client device in the real world | float | 1 | + +##### **(2-1-2) UserProfile** + +The "UserProfile" element represents personal information about the user as shown in Figure 6-12. The attributes of the "UserProfile" element consists of "ID", "Age" and "Gender". The "ID" attribute enables MC servers to identify the user and enhance the performance of MC engines. Each of the attributes has personal information about the user. The definition of the attributes of the "UserProfile" element is described in Table 6-5. To share a single device by multiple users, a function to handle multiple user profiles is required. + +![Figure 6-12: Structure of 'UserProfile' element. A tree diagram showing 'UserProfile' containing attributes 'ID', 'Age', 'Gender', and 'Option' under a group named 'grp Profile'.](a734898ce18e972938949637c32a34f4_img.jpg) + +``` + +graph LR + UserProfile[UserProfile] --- grpProfile[grp Profile] + grpProfile --- ID[ID] + grpProfile --- Age[Age] + grpProfile --- Gender[Gender] + grpProfile --- Option[Option] + +``` + +H.625(17)\_F6-12 + +Figure 6-12: Structure of 'UserProfile' element. A tree diagram showing 'UserProfile' containing attributes 'ID', 'Age', 'Gender', and 'Option' under a group named 'grp Profile'. + +**Figure 6-12 – Structure of a "UserProfile" element** + +**Table 6-5 – Definition of attributes of a "UserProfile" element** + +| UserProfile | | | | | +|-------------|--------|-------------------------------------------|-----------------|----------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | ID | Identification name or number of the user | string | 1 | +| | Age | User's age | integer | 0 or 1 | +| | Gender | User's gender | "female"/"male" | 0 or 1 | +| | Option | | | | + +#### (3) Server + +The "Server" element contains the type of service provided by MC servers, Request information including MI data input into the MC client and Response information including MC results output from the MC server. The structure of the "Server" element is shown in Figure 6-13. + +The attributes and child elements of the "Server" are defined in Table 6-6. "Request" or "Response" is alternatively selected. When the MC client requests MC servers to convert modality, the MCML that is sent to the MC server contains a "Request" element. When the MCP servers send MC results back to the MC client, the MCML contains a "Response" element. + +To achieve relay communication, MC results are transferred directly to the next MC server. To deal with multiple MC processes sequentially, multiple "Request" elements are to be listed with the associated process order attribute in the MCML sent by the transmitter. In the case where MCML data is directly transferred from an MC server to another MC server through the relay communication, the MCML, including the "Request" element, is sent to another MC server. + +![UML class diagram showing the structure of a 'Server' element. The 'Server' class has an 'attributes' compartment containing a 'grp serviceInfo' group with 'Service' and 'ProcessOrder' attributes. The 'Server' class has a 1..∞ association with 'Request' and 'Response' elements, indicated by a switch symbol.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +``` + +classDiagram + class Server { + +grp serviceInfo { + +Service + +ProcessOrder + } + } + Server "1..∞" --> Request + Server "1..∞" --> Response + note for Request "+" + note for Response "+" + +``` + +H.625(10)\_F6-13 + +UML class diagram showing the structure of a 'Server' element. The 'Server' class has an 'attributes' compartment containing a 'grp serviceInfo' group with 'Service' and 'ProcessOrder' attributes. The 'Server' class has a 1..∞ association with 'Request' and 'Response' elements, indicated by a switch symbol. + +**Figure 6-13 – Structure of a "Server" element** + +**Table 6-6 – Definition of attributes and child elements of a "Server" element** + +| Server | | | | | +|------------|--------------|---------------------------------------------------------------------------------------------------|---------|-----------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | Service | Service type provided by MCP server:
    "ASR", "MT", "TTS", "SignRec", "DM" are reserved for MCML | string | 1 | +| | ProcessOrder | The process order for services accomplished by the combination of multiple MCP servers | integer | 1 | +| Children | Request | See (3-1) | | 0 or more | +| | Response | See (3-1) | | 0 or 1 | + +##### (3-1) Request and Response + +The "Request" element indicates request information with MI data that is sent from the MC client to the MC server. The structure of the "Request" element is shown below in Figure 6-14. The child elements are listed in Table 6-7. The "Response" element includes MC results sent from the MC server. The "Response" element contains: "Routing", "Output" and "Error" as shown in Figure 6-14. These child elements of the "Response" and attributes of the "Error" element are described in Table 6-7. + +![Figure 6-14 shows three diagrams: (a) Request, (b) Response, and (c) Error. (a) Request shows a 'Request' element with a 'Routing' element and a group of elements (InputUserProfile, TargetOutput, Input) with a 0..∞ multiplicity. (b) Response shows a 'Response' element with 'Routing', 'Output' (1..∞ multiplicity, 'Select at least one'), and 'Error' elements. (c) Error shows an 'Error' element with an 'attributes' group containing 'Code', 'Service', and 'Message', and an 'Option' element with a 0..∞ multiplicity.](a3472689858b068ef469213682965325_img.jpg) + +(a) Request + +(b) Response + +(c) Error + +Figure 6-14 shows three diagrams: (a) Request, (b) Response, and (c) Error. (a) Request shows a 'Request' element with a 'Routing' element and a group of elements (InputUserProfile, TargetOutput, Input) with a 0..∞ multiplicity. (b) Response shows a 'Response' element with 'Routing', 'Output' (1..∞ multiplicity, 'Select at least one'), and 'Error' elements. (c) Error shows an 'Error' element with an 'attributes' group containing 'Code', 'Service', and 'Message', and an 'Option' element with a 0..∞ multiplicity. + +H.625(10)\_F6-14 + +**Figure 6-14 – Structure of Request, Response and Error elements** + +**Table 6-7 – Definition of child element of "Request", "Response" and "Error" elements** + +| Request | | | | | +|-------------------|------------------|-----------------------------------------------------------------------------|--------------|-----------------| +| Annotation | Name | Definition | | Quantity | +| Children | Routing | See (3-2) | | 0 or 1 | +| | InputUserProfile | See (3-3) | | 0 or more | +| | TargetOutput | See (3-4) | | 0 or 1 | +| | Input | See (3-5) | | 0 or 1 | +| Response | | | | | +| Annotation | Name | Definition | | Quantity | +| Children | Routing | See (3-2) | | 0 or more | +| | Output | See (3-5)
    The structure of the output is the same as the Request's input | | 0 or more | +| | Error | See below | | 0 or 1 | +| Error | | | | | +| Annotation | Name | Definition | Value | Quantity | +| Attributes | Code | Error type | string | 1 | +| | Service | Service type | string | 1 | +| | Message | Message to be prompted for error type | string | 1 | +| Children | Option | | | | + +**(3-2) Routing** + +The "Routing" element is a child element of "Request" and "Response". The "Routing" element contains the routing information for relay services through multiple MC servers. The child elements indicate "From" and "To" as shown in Figure 6-15. Each of the child elements has an attribute "URI", as explained in Table 6-8. Multiple "To" elements are required to send data to multiple MC clients and servers. + +![Diagram showing the structure of a Routing element. It starts with a 'Routing' box connected to a sequence indicator (three dots). This branches into a 'From' box and a 'To' box. Both 'From' and 'To' boxes have a nested 'attributes' box containing a 'URI' element. The 'To' branch has a multiplicity indicator '1..∞'.](c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg) + +**Figure 6-15 – Structure of a "Routing" element** + +Diagram showing the structure of a Routing element. It starts with a 'Routing' box connected to a sequence indicator (three dots). This branches into a 'From' box and a 'To' box. Both 'From' and 'To' boxes have a nested 'attributes' box containing a 'URI' element. The 'To' branch has a multiplicity indicator '1..∞'. + +16 Rec. ITU-T H.625 (03/2017) + +**Table 6-8 – Definition of attributes and child elements of "Routing" and "From"/"To" elements** + +| Routing | | | | | +|-------------------|-------------|--------------------------------------------------------------------|-----------------|-----------------| +| Annotation | Name | Definition | Quantity | | +| Children | From | The location in the network of the server which sends a request | 0 or 1 | | +| | To | The location in the network of the server which receives a request | 0 or more | | +| From/To | | | | | +| Annotation | Name | Definition | Value | Quantity | +| Attributes | URI | Uniform resource identifier | string | 1 | + +##### (3-3) InputUserProfile + +The element of "InputUserProfile" contains modality information for the user's input into the MC client. The structure of the "InputUserProfile" is as shown in Figure 6-16. The attributes are the same as those in Table 6-5 for "UserProfile". The child element is named "InputModality" and its structure is shown in Figure 6-17. The definition of children of "InputModality" is given in Table 6-9. + +![Figure 6-16: Structure of a 'InputUserProfile' element. The diagram shows an 'InputUserProfile' element box connected to an 'attributes' box. Inside 'attributes' is a 'grp Profile' box containing 'ID' (solid border), 'Age' (dashed border), and 'Gender' (dashed border). Below 'attributes' is a connector box with three dots leading to an 'InputModality' element box. The label 'H.625(10)_F6-16' is at the bottom right.](844077b3034f0030b404207db0ad76b4_img.jpg) + +Figure 6-16: Structure of a 'InputUserProfile' element. The diagram shows an 'InputUserProfile' element box connected to an 'attributes' box. Inside 'attributes' is a 'grp Profile' box containing 'ID' (solid border), 'Age' (dashed border), and 'Gender' (dashed border). Below 'attributes' is a connector box with three dots leading to an 'InputModality' element box. The label 'H.625(10)\_F6-16' is at the bottom right. + +**Figure 6-16 – Structure of a "InputUserProfile" element** + +![Figure 6-17: Structure of a 'InputModality' element. The diagram shows an 'InputModality' element box connected to a connector box with three dots. From the connector, four dashed boxes branch out: 'Speaking', 'Writing', 'Signing', and 'Option'. Each of the first three has a '+' sign in its top right corner. Below the 'Option' box is the cardinality '0..∞'. The label 'H.625(10)_F6-17' is at the bottom right.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +Figure 6-17: Structure of a 'InputModality' element. The diagram shows an 'InputModality' element box connected to a connector box with three dots. From the connector, four dashed boxes branch out: 'Speaking', 'Writing', 'Signing', and 'Option'. Each of the first three has a '+' sign in its top right corner. Below the 'Option' box is the cardinality '0..∞'. The label 'H.625(10)\_F6-17' is at the bottom right. + +**Figure 6-17 – Structure of a "InputModality" element** + +**Table 6-9 – Definition of child elements of "InputModality" element** + +| InputModality | | | | +|----------------------|----------------------|-------------------------------------------------------------------------------------------------------------------|-----------------| +| Annotation | Name | Definition | Quantity | +| Children | Speaking/
    Writing | The modality for communication | 0 or 1 | +| | Signing | The modality for communication. The details of this modality is for further study | 0 or 1 | +| | Option | The additional modalities for communication can be designed under agreement between an MCP client and MCP servers | 0 or more | + +The "InputModality" contains information for each modality. The child elements of "InputModality" are "Speaking", "Writing", "Signing" and "Option". The child element of each modality element is the "Language" element. The structure of the "Language" element associated with the "Speaking" element is shown in Figure 6-18. The definition of each element of the "Language" attribute is described in Table 6-10. The fluency of each language for respective modalities is contained by these child elements of the "InputModality" element and the information of the fluency contributes to the performance of MC engines. The input language for ASR and MT engines is determined by the "ID" of "Language". + +![Diagram showing the structure of a 'Language' element. It shows a 'Speaking' element connected to a 'Language' element via a connector. The 'Language' element has a '1..∞' multiplicity. To the right, an 'attributes' box for 'LanguageSkill' contains 'ID' (solid box), 'Dialect' (dashed box), and 'Fluency' (solid box).](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +H.625(10)\_F6-18 + +Diagram showing the structure of a 'Language' element. It shows a 'Speaking' element connected to a 'Language' element via a connector. The 'Language' element has a '1..∞' multiplicity. To the right, an 'attributes' box for 'LanguageSkill' contains 'ID' (solid box), 'Dialect' (dashed box), and 'Fluency' (solid box). + +**Figure 6-18 – Structure of a "Language" element** + +**Table 6-10 – Definition of attributes of a "Language" element** + +| Language | | | | | +|-------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-----------------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | ID | The identifier for language | ISO 639
    [ISO 639] | 1 | +| | Dialect | The identifier for dialect which is not categorized by ISO 639 [ISO 639] | string | 0 or 1 | +| | Fluency | The fluency level for the modality is rated from "1" to "5", where "5" shows the most fluent level. Level 5 indicates fluency of native speakers. | integer | 0 or 1 | + +NOTE – The languages are identified by ISO 639 codes, which are the set of international standards that list short codes for language names [ISO 639-1,2,3,4,5]. + +If the user's language is linguistically different from the standard language, the information contained in the "Dialect" element aids MC engines. To use the "Dialect" element, MC servers are required to know the meaning of the identifier in this element. + +##### (3-4) TargetOutput + +The "TargetOutput" element contains information about what type of output from the engine is demanded by the MC client as shown in Figure 6-19. The child elements are named "HypothesisFormat", "LanguageType" and "Option" as defined in Table 6-11. The output language of MT and TTS engine is determined by the "ID" of "LanguageType." Additional demands to the MC servers can optionally be added. + +![Diagram showing the structure of a TargetOutput element. TargetOutput contains HypothesisFormat, LanguageType, and Option (0..∞). HypothesisFormat has attribute NofN-best. LanguageType has attributes ID and Dialect. Option has attributes Key and Value.](552265bdbcf6d43d341fd018a9076269_img.jpg) + +``` + +graph LR + TO[TargetOutput] --> HF[HypothesisFormat] + TO --> LT[LanguageType] + TO --> O[Option 0..∞] + HF --> HF_ATTR[attributes: NofN-best] + LT --> LT_ATTR[attributes: ID, Dialect] + O --> O_ATTR[attributes: Key, Value] + +``` + +Diagram showing the structure of a TargetOutput element. TargetOutput contains HypothesisFormat, LanguageType, and Option (0..∞). HypothesisFormat has attribute NofN-best. LanguageType has attributes ID and Dialect. Option has attributes Key and Value. + +H.625(10)\_F6-19 + +Figure 6-19 – Structure of a TargetOutput element + +Table 6-11 – Definition of attribute/child elements of "TargetOutput", "HypothesisFormat" and "LanguageType" elements + +| TargetOutput | | | | | +|------------------|------------------|--------------------------------------------------------------------------|-------------------|-----------| +| Annotation | Name | Definition | Value | Quantity | +| Children | HypothesisFormat | See below | | 0 or 1 | +| | LanguageType | | | 0 or 1 | +| | Option | Another demanded format can be added | | 0 or more | +| HypothesisFormat | | | | | +| Attributes | NofN-best | N of the N-best hypotheses | string | 1 | +| LanguageType | | | | | +| Attributes | ID | The identifier for language | ISO 639 [ISO 639] | 1 | +| | Dialect | The identifier for dialect which is not categorized by ISO 639 [ISO 639] | string | 0 or 1 | + +##### (3-5) Input + +The children of the "Input" element are the "Data" and "AttachedBinary" elements, as illustrated in Figure 6-20. These are defined in Table 6-12. Multiple binary data are attached to MCML. To link each binary data to MI for each modality, the "AttachedBinary" element has information which links the data format described in the child element of the "Data" element with the attached binary data. + +![Diagram illustrating the structure of an 'Input' element. The 'Input' element contains a 'Data' element and an 'AttachedBinary' element. The 'Data' element contains a list of child elements: Text, Audio, Image, Video, Application, and Option, each with a multiplicity of 0..∞. The 'AttachedBinary' element contains an 'attributes' group with 'grp BinaryInfo' containing 'DataID', 'DataType', and 'ChannelID'.](5a1abd59a95fa47ae192807de151e9eb_img.jpg) + +The diagram shows the hierarchical structure of the "Input" element. The "Input" element is the root, containing two child elements: "Data" and "AttachedBinary". The "Data" element is represented by a box with a right-pointing arrow and a dashed box containing three dots. The "AttachedBinary" element is represented by a box with a right-pointing arrow and a dashed box containing three dots. The "Data" element's children are shown in a dashed box on the right, containing "Text", "Audio", "Image", "Video", "Application", and "Option", each with a multiplicity of 0..∞. The "AttachedBinary" element's attributes are shown in a dashed box on the right, containing an "attributes" group with a "grp BinaryInfo" containing "DataID", "DataType", and "ChannelID". The diagram is labeled H.625(17)\_F6-20. + +Diagram illustrating the structure of an 'Input' element. The 'Input' element contains a 'Data' element and an 'AttachedBinary' element. The 'Data' element contains a list of child elements: Text, Audio, Image, Video, Application, and Option, each with a multiplicity of 0..∞. The 'AttachedBinary' element contains an 'attributes' group with 'grp BinaryInfo' containing 'DataID', 'DataType', and 'ChannelID'. + +Figure 6-20 – Structure of an "Input" element + +Table 6-12 – Definition of attributes and child elements of "Input", "Data" and "AttachedBinary" elements + +| Input | | | | | +|------------|----------------------------|-------------------------------------------------|-------|-----------| +| Annotation | Name | Definition | Value | Quantity | +| Children | Data | See (3-5-1) to (3-5-3) | | 1 | +| | AttachedBinary | Another demanded format can be added | | 0 or more | +| Data | | | | | +| Children | Text/Audio/
    Image/Video | See from (3-5-1) to (3-5-3) | | 0 or more | +| | Application | Define an appropriate value for the application | | 0 or more | +| | Option | Additional modalities can be freely added | | 0 or more | + +**Table 6-12 – Definition of attributes and child elements of "Input", "Data" and "AttachedBinary" elements** + +| Input | | | | | +|-----------------------|-------------|------------------------------------------------------------------------------------------------------------|--------------|-----------------| +| Annotation | Name | Definition | Value | Quantity | +| AttachedBinary | | | | | +| Attributes | DataID | The identifier for language | string | 1 | +| | DataType | One of the child elements of the "Data".
    Types "Text", "Audio", "Image", "Video" are reserved for MCML. | string | 1 | +| | ChannelID | Identifier for input channel | integer | 1 | + +##### (3-5-1) Text + +The "Text" element is a child element of the "Data" element. The structure of the "Text" element is shown in Figure 6-21. To cope with multi-channel inputs, the "Text" element has an attribute named "ChannelID" whose value identifies the channel of the text input, as shown in Figure 6-21. The attributes and child elements of "Text" are defined in Table 6-13. + +![Diagram showing the structure of a 'Text' element. It includes an 'attributes' box with 'grp Channel' containing 'ChannelID', 'BeginTimestamp', 'EndTimestamp', and 'EndPoint'. Below the attributes is an ellipsis (...) leading to 'ModelType' and 'SentenceSequence' with a '1..∞' cardinality indicator. The diagram is labeled H.625(10)_F3-21.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +The diagram illustrates the structure of a "Text" element. It consists of a main "Text" box on the left. To its right, an "attributes" box contains a "grp Channel" group, which includes the elements "ChannelID", "BeginTimestamp", "EndTimestamp", and "EndPoint" (the latter is shown with a dashed border). Below the "Text" box, an ellipsis (...) indicates a continuation, leading to a "ModelType" element and a "SentenceSequence" element. The "SentenceSequence" element has a cardinality indicator of "1..∞". The diagram is labeled "H.625(10)\_F3-21" at the bottom right. + +Diagram showing the structure of a 'Text' element. It includes an 'attributes' box with 'grp Channel' containing 'ChannelID', 'BeginTimestamp', 'EndTimestamp', and 'EndPoint'. Below the attributes is an ellipsis (...) leading to 'ModelType' and 'SentenceSequence' with a '1..∞' cardinality indicator. The diagram is labeled H.625(10)\_F3-21. + +**Figure 6-21 – Structure of a "Text" element** + +**Table 6-13 – Definition of attributes and child elements of a "Text" element** + +| Text | | | | | +|------------|------------------|--------------------------------------------------------------------------|----------|-----------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | ChannelID | The identifier for channel | integer | 1 | +| | BeginTimestamp | The timestamp for the audio input universal time, coordinated (UTC) | dateTime | 0 or 1 | +| | EndTimestamp | The timestamp for the stop of audio input (UTC) | dateTime | 0 or 1 | +| | EndPoint | Flag for input of signal, such as "endpoint" indicating the end of input | dateTime | 0 or 1 | +| Children | ModelType | See (3-5-1-1) | | 0 or more | +| | SentenceSequence | See (3-5-1-2) | | 1 or more | + +##### (3-5-1-1) ModelType + +One of the child elements of "Text" is named "ModelType", as shown in Figure 6-22 with its definition in Table 6-14. This element contains target domains in the "Domain" element and user information in the "Personality" element which contribute to enhancing the performance of MC engines. + +When data is input directly to the user device without MC, the "ModelType" is not used for input. This value does not exist in such a case. + +![Figure 6-22 – Structure of a 'ModelType' element. The diagram shows a 'ModelType' element connected to a central node (three dots). From this node, three dashed lines lead to 'Domain', 'Personality', and 'Task' elements, each with a '0..∞' multiplicity. To the right, an 'attributes' box contains a 'grp UserModel' group with 'ID', 'Age', and 'Gender' elements. The 'Personality' element is connected to this 'attributes' box. The diagram is labeled H.625(17)_F6-22.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +Figure 6-22 – Structure of a 'ModelType' element. The diagram shows a 'ModelType' element connected to a central node (three dots). From this node, three dashed lines lead to 'Domain', 'Personality', and 'Task' elements, each with a '0..∞' multiplicity. To the right, an 'attributes' box contains a 'grp UserModel' group with 'ID', 'Age', and 'Gender' elements. The 'Personality' element is connected to this 'attributes' box. The diagram is labeled H.625(17)\_F6-22. + +**Figure 6-22 – Structure of a "ModelType" element** + +**Table 6-14 – Definition of attributes and child elements of "ModelType" and "Personality" elements** + +| ModelType | | | | | +|-------------------|-------------|-------------------------------------------------|--------------|-----------------| +| Annotation | Name | Definition | Value | Quantity | +| Children | Domain | The domain for MI input such as "Travel" domain | string | 0 or more | +| | Personality | See below | | 0 or more | +| | Task | Task for ML input | string | 0 or more | + + + +| Personality | | | | | +|--------------------|-------------|-------------------------------------------|---------------------|-----------------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | ID | Identification name or number of the user | string | 1 | +| | Age | User's age | integer | 0 or 1 | +| | Gender | User's gender | "female"/
    "male" | 0 or 1 | + +##### (3-5-1-2) SentenceSequence + +The "Text" element is required to handle not only plain text but also ASR results. To cope with multiple ASR hypotheses generated from multiple utterances, the child element named "SentenceSequence" has attributes which represent information for ASR results and a child element named "Sentence", as shown in Figure 6-23. The attributes and children are listed in Table 6-15. + +![Diagram showing the structure of a 'SentenceSequence' element. It includes an 'attributes' box with 'grp TextMetaInfo' containing 'Order', 'Score', 'Timestamp', 'BeginTime', 'EndTime', and 'N-bestRank'. It also shows a 'Sentence' child element with a '1..∞' multiplicity.](474a819357587e34949a3e110ff19b30_img.jpg) + +The diagram illustrates the structure of a "SentenceSequence" element. On the left, a box labeled "SentenceSequence" has a line connecting it to a large box labeled "attributes". Inside the "attributes" box, there is a sub-box labeled "grp TextMetaInfo" which contains several elements: "Order", "Score", "Timestamp", "BeginTime", "EndTime", and "N-bestRank". Below the "attributes" box, a line with a small circle and a minus sign connects to a box labeled "Sentence". The "Sentence" box has a plus sign in its top right corner and a multiplicity of "1..∞" below it. The text "H.625(10)\_F6-23" is written at the bottom right of the diagram. + +Diagram showing the structure of a 'SentenceSequence' element. It includes an 'attributes' box with 'grp TextMetaInfo' containing 'Order', 'Score', 'Timestamp', 'BeginTime', 'EndTime', and 'N-bestRank'. It also shows a 'Sentence' child element with a '1..∞' multiplicity. + +**Figure 6-23 – Structure of a "SentenceSequence" element** + +**Table 6-15 – Definition of attributes and child elements of a "SentenceSequence" element** + +| SentenceSequence | | | | | +|-------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | Order | The order of MI input | integer | 1 | +| | Score | Score given by the MC engine such as a confidence score of ASR output | float | 0 or 1 | +| | TimeStamp | The start time of text input or that of ASR output given by user device (UTC) | dateTime | 0 or 1 | +| | BeginTime | The start time of text input or ASR output that is measured from the start of the sentence sequence. For Sentence Sequence, this is set to 0 [msec] | integer | 0 or 1 | +| | EndTime | The stop time of text input or ASR output relative to the BeginTime [msec] | integer | 0 or 1 | +| | N-bestRank | The rank in the ASR N-best hypotheses | integer | 0 or 1 | +| Children | Sentence | See (3-5-1-3) | | 1 or more | + +Although ASR output does not always start from a sentence beginning and ending at a sentence ending, the beginning and the ending of speech input are dealt with as the beginning and the ending of a sentence. MCP servers that use MC results obtained by ASR servers are required to detect the real boundary of sentences. + +##### **(3-5-1-3) Sentence** + +The child element of the "SentenceSequence" is named "Sentence", which contains information of each sentence. The structure of the "Sentence" element is shown in Figure 6-24. The "Sentence" element has three child elements named "Function", "Surface" and "Chunk". The attributes of the "Sentence" element and its child elements are listed in Table 6-16. The "Surface" element contains a sequence of chunk surfaces in a sentence, as defined in Table 6-16. + +![Diagram showing the structure of a 'Sentence' element. The 'Sentence' element has an 'attributes' group named 'TextMetaInfo' containing 'Order', 'Score', 'TimeStamp', 'BeginTime', and 'EndTime'. It has child elements 'Function' (0..∞), 'Surface' (1..∞), and 'Chunk' (0..∞). The 'Surface' element has an 'attributes' group containing 'Delimiter'.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +``` + +graph LR + Sentence[Sentence] --- attr_grp[attributes] + attr_grp --- grp_TextMetaInfo[grp TextMetaInfo] + grp_TextMetaInfo --- Order[Order] + grp_TextMetaInfo --- Score[Score] + grp_TextMetaInfo --- TimeStamp[TimeStamp] + grp_TextMetaInfo --- BeginTime[BeginTime] + grp_TextMetaInfo --- EndTime[EndTime] + + Sentence --- choice{ } + choice --- Function[Function] + Function --- F_card[0..∞] + choice --- Surface[Surface] + Surface --- S_card[1..∞] + Surface --- S_attr[attributes] + S_attr --- Delimiter[Delimiter] + choice --- Chunk[Chunk] + Chunk --- C_card[0..∞] + +``` + +Diagram showing the structure of a 'Sentence' element. The 'Sentence' element has an 'attributes' group named 'TextMetaInfo' containing 'Order', 'Score', 'TimeStamp', 'BeginTime', and 'EndTime'. It has child elements 'Function' (0..∞), 'Surface' (1..∞), and 'Chunk' (0..∞). The 'Surface' element has an 'attributes' group containing 'Delimiter'. + +Figure 6-24 – Structure of a "Sentence" element + +Table 6-16 – Definition of attributes and child elements of a "Sentence" element + +| Sentence | | | | | +|------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------|-----------| +| Annotation | Name | Definition | | Quantity | +| Attributes | Order/Score/
    TimeStamp/
    BeginTime/
    EndTime | The same attributes as those of the "SentenceSequence". The "N-bestRank" is not considered for the "Sentence" element. See (3-5-1-2) | | | +| Children | Function | Class for sentence such as dialog act
    (No attributes and children) | | 0 or more | +| | Surface | See below | | 1 or more | +| | Chunk | See (3-5-1-4) | | 0 or more | +| Surface | | | | | +| Annotation | Name | Definition | Value | Quantity | +| Attributes | Delimiter | Symbols indicating chunk boundary | string | 0 or 1 | + +###### **(3-5-1-4) Chunk** + +The structure of the "Chunk" element is shown in Figure 6-25. The definition of attributes and child elements is given below in Table 6-17. + +![A hierarchical diagram showing the structure of a 'Chunk' element. The 'Chunk' element has an 'attributes' group containing 'grp TextMetaInfo' with sub-attributes: 'Order', 'Score', 'TimeStamp', 'BeginTime', and 'EndTime'. The 'Chunk' element also has child elements: 'Surface' (1..∞), 'POS' (0..∞), 'Pronunciation' (0..∞), 'IPA' (0..∞), 'Accent' (0..∞), and 'Option' (0..∞). A dashed box with three dots indicates additional child elements. The diagram is labeled H.625(1C)_F6-25.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +A hierarchical diagram showing the structure of a 'Chunk' element. The 'Chunk' element has an 'attributes' group containing 'grp TextMetaInfo' with sub-attributes: 'Order', 'Score', 'TimeStamp', 'BeginTime', and 'EndTime'. The 'Chunk' element also has child elements: 'Surface' (1..∞), 'POS' (0..∞), 'Pronunciation' (0..∞), 'IPA' (0..∞), 'Accent' (0..∞), and 'Option' (0..∞). A dashed box with three dots indicates additional child elements. The diagram is labeled H.625(1C)\_F6-25. + +Figure 6-25 – Structure of "Chunk" element + +Table 6-17 – Definition of attributes and child elements of "Chunk" element + +| Chunk | | | | | +|------------|-----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------|-----------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | Order/Score/
    TimeStamp/
    BeginTime/
    EndTime | The same attributes as those of the "SentenceSequence". The "N-bestRank" is not considered for the "Sentence" element. See (3-5-1-3) | | | +| Children | Surface | Surface expression of Chunk | string | 1 or more | +| | POS | Part-of-Speech or its complementary information for Chunk | string | 0 or more | +| | Pronunciation | Pronunciation of Chunk | string | 0 or more | +| | IPA | International phonetic alphabet (IPA) for Chunk | string | 0 or more | +| | Accent | Accent for Chunk | string | 0 or more | +| | Additional information which depends on language can be added when agreements between clients and servers exist | | | | + +###### (3-5-1-5) Surface, POS, Pronunciation, IPA and Accent + +The child elements of the "Chunk" element are named "Surface", "POS", "Pronunciation", "IPA" and "Accent", and all of them have the same attributes. As an example, the attributes of "Surface" are shown in Figure 6-26. The attributes of the child elements are listed in Table 6-18. + +![Figure 6-26: Structure of a 'Surface' element. The diagram shows a 'Surface' element box with a '1..∞' multiplicity indicator. An arrow points from the 'Surface' box to an 'attributes' panel. The 'attributes' panel contains a 'grp Dictionary' group with 'DictionaryID' and 'EntryID' attributes, and an 'Option' attribute.](318886a86a1dcc59e1fc83db6f157c60_img.jpg) + +H.625(10)\_F6-26 + +Figure 6-26: Structure of a 'Surface' element. The diagram shows a 'Surface' element box with a '1..∞' multiplicity indicator. An arrow points from the 'Surface' box to an 'attributes' panel. The 'attributes' panel contains a 'grp Dictionary' group with 'DictionaryID' and 'EntryID' attributes, and an 'Option' attribute. + +Figure 6-26 – Structure of a "Surface" element + +Table 6-18 – Definition of attributes of "Surface", "POS", "Pronunciation" and "Accent" elements + +| Surface/POS/Pronunciation/Accent | | | | | +|----------------------------------|---------------------------------------------------------------------------------------------|--------------------------------------|--------|----------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | DictionaryID | Identifier for chunk dictionary | string | 0 or 1 | +| | EntryID | Identifier for entry in a dictionary | string | 0 or 1 | +| | Optional language information can be added when agreements between clients and server exist | | | | + +Generally, the "Surface" of "Chunk" contains words, while some TTS engines need to use phrases as chunks. This element can be freely designed corresponding to the MCP servers' demands. The tuples of phonemes, sub-words, or words are supposed to be contained by the "Surface" of "Chunk" element. + +##### (3-5-2) Audio + +The "Audio" element is a child element of the "Data" element. The "Audio" element has three child elements: "ModelType", "Signal" and "Feature", as shown in Figure 6-27. The "Feature" element is optional. + +![Structure of an 'Audio' element diagram. The 'Audio' element has an 'attributes' box containing a 'grp Channel' with 'ChannelID', 'BeginTimestamp', 'EndTimestamp', and 'EndPoint' (dashed). It has child elements: 'ModelType' (dashed, 0..1), 'Signal' (1..∞), and 'Feature' (dashed, 0..∞). The 'Feature' element has an 'attributes' box with 'Option' (dashed). Reference H.625(10)_F6-27 is shown at the bottom right.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +Structure of an 'Audio' element diagram. The 'Audio' element has an 'attributes' box containing a 'grp Channel' with 'ChannelID', 'BeginTimestamp', 'EndTimestamp', and 'EndPoint' (dashed). It has child elements: 'ModelType' (dashed, 0..1), 'Signal' (1..∞), and 'Feature' (dashed, 0..∞). The 'Feature' element has an 'attributes' box with 'Option' (dashed). Reference H.625(10)\_F6-27 is shown at the bottom right. + +**Figure 6-27 – Structure of an "Audio" element** + +To cope with multichannel inputs, the "Audio" element has an attribute named "ChannelID", whose value identifies the channel of audio input. The definition of the "Audio" element is described in Table 6-19. The definition of "ModelType" is described in (3-5-1-1). Timestamps are given by user devices. + +**Table 6-19 – Definition of attributes and child elements of an "Audio" element** + +| Audio | | | | +|------------|------------------------------------------------------------|---------------------------------------------------------------------------------------|----------| +| Annotation | Name | Definition | Quantity | +| Attributes | ChannelID/
    BeginTimestamp/
    EndTimestamp/
    EndPoint | These attributes are the same as those of the "Text" element, as shown in Table 6-13. | | +| Children | ModelType | See (3-5-1-1) | 0 or 1 | +| | Signal | See (3-5-2-1) | 1 | +| | Feature | Optional model feature | 0 or 1 | + +###### **(3-5-2-1) Signal** + +The attributes of the "Signal" element are shown in Figure 6-28 and listed in Table 6-20. + +The element "Feature" is not defined in this Recommendation. Any features can be used for this communication when agreements on feature expressions exist between clients and servers. + +![Diagram showing the structure of a 'Signal' element. A 'Signal' box is connected to an 'attributes' panel. The 'attributes' panel contains a 'grp SignalInfo' group with attributes: DataFormat, SamplingRate, BitRate, Endian, ChannelQty, ValueType, and Option. The last six are dashed boxes. Below the diagram is the text 'H.625(17)_F6-28'.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +Diagram showing the structure of a 'Signal' element. A 'Signal' box is connected to an 'attributes' panel. The 'attributes' panel contains a 'grp SignalInfo' group with attributes: DataFormat, SamplingRate, BitRate, Endian, ChannelQty, ValueType, and Option. The last six are dashed boxes. Below the diagram is the text 'H.625(17)\_F6-28'. + +Figure 6-28 – Structure of a "Signal" element + +Table 6-20 – Definition of attributes of a "Signal" element + +| Signal | | | | | +|------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | DataFormat | The format of digitalized speech by Input Method, "raw PCM" and "ADPCM" are reserved for MCML. Use of PCM formatted audio data is required for MCML, while use of ADPCM is optional. | string | 1 | +| | SamplingRate | Sampling rate [Hz] | integer | 0 or 1 | +| | BitRate | Bit rate | integer | 0 or 1 | +| | Endian | Endian type | "little"/ "big" | 0 or 1 | +| | ChannelQty | Number of channels | integer | 0 or 1 | +| | ValueType | Float or integer | "integer"/ "float" | 0 or 1 | +| | Option | Necessary data such as still images or moving pictures can be added accordingly | | | + +###### **(3-5-3) Image and video** + +The "Image" and "Video" elements have the same attributes. The structure of the "Image" element is shown in Figure 6-29. The definitions of the attributes are listed in Table 6-21. To cope with multichannel inputs, the "Image" and "Video" elements have an attribute named "ChannelID", whose value identifies the input channel. + +![Diagram showing the structure of an 'Image' element. It includes an 'attributes' box with 'grp Channel' containing 'ChannelID', 'BeginTimestamp', 'EndTimestamp', and 'EndPoint'. Below the attributes is a connector leading to 'ModelType' and 'Option' child elements. The 'Option' element has a multiplicity of '0..∞' and is labeled 'H.625(1C)_F6-28'.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +Diagram showing the structure of an 'Image' element. It includes an 'attributes' box with 'grp Channel' containing 'ChannelID', 'BeginTimestamp', 'EndTimestamp', and 'EndPoint'. Below the attributes is a connector leading to 'ModelType' and 'Option' child elements. The 'Option' element has a multiplicity of '0..∞' and is labeled 'H.625(1C)\_F6-28'. + +Figure 6-29 – Structure of an "Image" element + +Table 6-21 – Definition of attributes and child elements of "Image" and "Video" elements + +| Image/Video | | | | | +|-------------|------------------------------------------------------------|------------------------------------------------------------------------------|-------|----------| +| Annotation | Name | Definition | Value | Quantity | +| Attributes | ChannelID/
    BeginTimestamp/
    EndTimestamp/
    EndPoint | These attributes are the same ones that the "Text" element has in Table 6-13 | | | +| Children | ModelType | See Figure 6-22 and Table 6-14 | | | +| | Option | Optional signals and features can be added | | | + +#### **(4) History** + +The MCP client requests MC by using the "Request" element. In response to this MCP client request, the MCML server responds using the "Response" element to provide MC results. In order to record all processes through multiple combinations of MCP servers, all the information embedded into both the "Request" and "Response" elements are recorded in element "History". The structure of the "History" element is shown in Figure 6-30. The structure of the "Request" and "Response" elements is described in (3-1). + +![Figure 6-30: Structure of a 'History' element. The diagram shows a 'History' box connected to a 'Request' box and a 'Response' box via a central connector. Above the 'History' box is an 'attributes' box containing a 'grp ServiceInfo' group with 'Service' and 'ProcessOrder' elements. The diagram is labeled H.625(1C)_F6-30.](f57c7b37d7a05a99618104f390089f03_img.jpg) + +Figure 6-30: Structure of a 'History' element. The diagram shows a 'History' box connected to a 'Request' box and a 'Response' box via a central connector. Above the 'History' box is an 'attributes' box containing a 'grp ServiceInfo' group with 'Service' and 'ProcessOrder' elements. The diagram is labeled H.625(1C)\_F6-30. + +Figure 6-30 – Structure of a "History" element + +## 6.4 General workflow for modality conversion + +It is recommended that the MC architecture in Figure 6-3 be controlled according to the data flow and workflow in Figures 6-31 and 6-32. + +![Figure 6-31: Data flow for modality conversion. This diagram illustrates the data flow between a 'Multimodal information (MI)' source, an 'MCP client', and an 'MCP server'. The MCP client contains three stacked boxes: 'Input and output processor', 'Multimodal information processing function', and 'MCML processing function'. The MCP server contains three stacked boxes: 'Multimodal information processing function', 'MCML processing function', and 'Modality conversion engine'. Arrows with labels like (1-1), (1-2-1), (2-7), etc., show the sequence of data processing and transfer between these components. The diagram is labeled H.625(10)_F6-31.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +Figure 6-31: Data flow for modality conversion. This diagram illustrates the data flow between a 'Multimodal information (MI)' source, an 'MCP client', and an 'MCP server'. The MCP client contains three stacked boxes: 'Input and output processor', 'Multimodal information processing function', and 'MCML processing function'. The MCP server contains three stacked boxes: 'Multimodal information processing function', 'MCML processing function', and 'Modality conversion engine'. Arrows with labels like (1-1), (1-2-1), (2-7), etc., show the sequence of data processing and transfer between these components. The diagram is labeled H.625(10)\_F6-31. + +Figure 6-31 – Data flow for modality conversion + +The general data flow and workflow are described with their associated steps in the following list. In this description, a module that has a particular function is denoted as "function" processor. + +- (1-1) MI is input into the MCP client. +- (1-2-1) MI is digitized by the input and output processor and sent to the MI processor or, +- (1-2-2) MI is digitized by the input and output processor and directly sent to the MCML processor. +- (1-3) Digitized MI is encoded by the MI processor and the encoded MI is sent to the MCML processor. +- (1-4) Digitized or encoded MI is embedded in MCML format by the MCML processor and sent to the communication processor. +- (1-5) MCML including digitized or encoded MI is sent to the MCP server using MCP via the communication processor. +- (1-6) Digitized or encoded MI in MCML format is received by the communication processor and sent to the MCML processor. +- (1-7-1) Digitized MI extracted from MCML by the MCML processor is sent to the MI processor. + +- (1-7-2) Encoded MI extracted from MCML by the MCML processor is directly sent to the MC engine. +- (1-8) Digitized MI is encoded by the MI processor and the encoded MI is sent to the MC engine. +- (2-1-1) Digitized or encoded MI is converted in modality by the MC engine and the MC result is sent to the MI processor. +- (2-1-2) The MC result is directly sent to the MCML processor. +- (2-2) The MC result is encoded by the MI processor and the encoded MC result is sent to the MCML processor. +- (2-3) The encoded MC result or the MC result is embedded in MCML format by the MCML processor and sent to the communication processor. +- (2-4) MCML is sent to the MCP client using MCP via the communication processor. +- (2-5) MCML including the MC result and/or the encoded MC result is received by the communication processor and sent to the MCML processor. +- (2-6-1) The MC result is extracted by the MCML processor and sent to the MI processor. +- (2-6-2) The MC result is sent to the input and output processor. +- (2-7) The MC result decoded by the MI processor is sent to the input and output processor. +- (2-8) The MC result is output by the input and output processor of the MCP client. + +MC is accomplished either by a single MCP server, or by a combination of multiple MCP servers. The order of processing by MCP servers is required to be assigned by the MCP client before processing. Even if an undefined MC server may be connected to S2ST servers, communication can be achieved as far as the servers support MCP. + +![Sequence diagram showing the general workflow for modality conversion between an MCP client and an MCP server. The client has four functions: Input and output processing, Multimodal information (MI) processing, MCML processing, and Communication processing. The server has four functions: Communication processing, MCML processing, Multimodal information (MI) processing, and Modality conversion. The process starts with (1-1) MI input, followed by digitization (1-2-1), encoding (1-3), and packaging into MCML (1-4). This is sent to the server (1-5), where it's processed (1-6), extracted (1-7-1), digitized (1-7-2), encoded (1-8), and converted (2-1-1). The result is sent back (2-2), packaged (2-3), sent to the client (2-4), processed (2-5), encoded (2-6-1), decoded (2-6-2), and finally output (2-7) as (2-8) MC result.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +``` + +sequenceDiagram + participant Client as MCP client + participant Server as MCP server + Note left of Client: (1-1) MI + Client->>Client: (1-2-1) Digitized MI + Client->>Client: (1-2-2) Digitized MI + Client->>Client: (1-3) Encoded MI + Client->>Client: (1-4) MCML including digitized/encoded MI + Client->>Server: (1-5) MCML is sent to MCP server + Server->>Server: (1-6) MCML including digitized/encoded MI + Server->>Server: (1-7-1) Encoded MI extracted from MCML + Server->>Server: (1-7-2) Digitized MI extracted from MCML + Server->>Server: (1-8) Encoded MI + Server->>Server: (2-1-1) Converted MI (= MC result) + Server->>Server: (2-1-2) Converted MI (= MC result) + Server->>Server: (2-2) Encoded MC result + Server->>Server: (2-3) MCML including (encoded) MC result + Server->>Client: (2-4) MCML is sent to MCP client + Client->>Client: (2-5) MCML including (encoded) MC result + Client->>Client: (2-6-1) Encoded MC result + Client->>Client: (2-6-2) MC result + Client->>Client: (2-7) Decoded MC result + Note right of Client: (2-8) MC result + +``` + +H.e25(10)\_F6-32 + +Sequence diagram showing the general workflow for modality conversion between an MCP client and an MCP server. The client has four functions: Input and output processing, Multimodal information (MI) processing, MCML processing, and Communication processing. The server has four functions: Communication processing, MCML processing, Multimodal information (MI) processing, and Modality conversion. The process starts with (1-1) MI input, followed by digitization (1-2-1), encoding (1-3), and packaging into MCML (1-4). This is sent to the server (1-5), where it's processed (1-6), extracted (1-7-1), digitized (1-7-2), encoded (1-8), and converted (2-1-1). The result is sent back (2-2), packaged (2-3), sent to the client (2-4), processed (2-5), encoded (2-6-1), decoded (2-6-2), and finally output (2-7) as (2-8) MC result. + +Figure 6-32 – General workflow for modality conversion + +# Annex A + +## MCML 2.0 schema + +(This annex forms an integral part of this Recommendation.) + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +# Appendix I + +## Examples of physical level architecture workflow examples of modality conversion using MCP + +(This appendix does not form an integral part of this Recommendation.) + +This appendix presents three typical examples of modality conversion using MCP defined in [ITU-T F.745]. The application scenarios are as follows. + +### I.1 Shared S2ST client for two-party communication + +S2ST provides two-party communication using a shared application terminal. In this service, S2ST can be performed for two-party communication. Although it is also applicable to multi-party communication, processing of multiple translations is not performed in a simultaneous manner, but in sequential steps. Figure I.1 shows the architectural configuration for this example. This setup can be used for face-to-face communication. + +![Diagram of shared S2ST client for two-party communication architecture.](4346261cc730a1eb683f35e4ce9deacf_img.jpg) + +Face-to-face communication + +The diagram illustrates a shared S2ST client architecture for two-party communication. At the top, an illustration of two men shaking hands is labeled "Face-to-face communication". Below this, a central "S2ST client" block is shown. Two speech input streams enter the client: "Speech of language B" from the left and "Speech of language A" from the right. Each stream passes through an "ASR" (Automatic Speech Recognition) block, which contains "Lexicon speech data" and a "Language" block (Language B on the left, Language A on the right). The output of the ASR block on the left goes to an "MT" (Machine Translation) block, which contains "Parallel corpus lexicon" and "Language" blocks (Language B and Language A). The output of the MT block on the left is "Synthesized speech of language A", which then passes through a "TTS" (Text-to-Speech) block containing "Lexicon speech data" and a "Language" block (Language A). The final output of the TTS block on the left is "Speech of language A", which is sent to the S2ST client. Similarly, the speech input from the right (Language A) is processed through ASR, MT, and TTS blocks to produce "Synthesized speech of language B", which is then sent to the S2ST client. The S2ST client sends synthesized speech back to the users: "Synthesized speech of language A" (dashed yellow arrow) and "Synthesized speech of language B" (dashed green arrow). A small label "H.625(17)\_FI-1" is at the bottom right. + +Diagram of shared S2ST client for two-party communication architecture. + +Figure I.1 – Shared S2ST client for two-party communication + +### I.2 Personal S2ST client communication + +S2ST provides users with both two-party and multi-party communications using personal application terminals. This service can also be performed remotely if the application is used in communication between multiple users, where the speech translation results of one user can be distributed to multiple users in multiple languages at the same time. Figure I.2 shows the architectural configuration for this example. This setup can be used for both face-to-face and remote communication. + +![Diagram of Personal S2ST client communication architecture showing two users communicating via S2ST clients with ASR, MT, and TTS components.](8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg) + +The diagram illustrates the architecture for personal S2ST client communication between two users, labeled 'Face-to-face/remote communication' at the top. Each user has a personal S2ST client stack. The left user's stack consists of an S2ST client, an ASR (Automatic Speech Recognition) unit, an MT (Machine Translation) unit, and a TTS (Text-to-Speech) unit. The right user's stack is identical. The ASR unit contains 'Lexicon speech data' and 'Language B'. The MT unit contains 'Parallel corpus lexicon', 'Language B', and 'Language A'. The TTS unit contains 'Lexicon speech data' and 'Language A'. The right user's stack is mirrored, with 'Language A' in the ASR and 'Language B' in the TTS. Arrows show the flow of communication: 'Speech of language B' from the left user to their ASR, then through MT to the right user's TTS, resulting in 'Synthesized speech of language A' for the right user. Conversely, 'Speech of language A' from the right user is processed through their ASR, MT, and TTS to produce 'Synthesized speech of language B' for the left user. The diagram is labeled H.625(17)\_FI-2 at the bottom right. + +Diagram of Personal S2ST client communication architecture showing two users communicating via S2ST clients with ASR, MT, and TTS components. + +Figure I.2 – Personal S2ST client communication + +### I.3 Cross-modality communication + +S2ST provides different-modality communication between users. For instance, a person who gives spoken utterances can communicate with a counterpart who is using sign language through the S2ST system. Text-input users could also converse with someone who uses sign language. Figure I.3 shows an example between a user who is speaking on a cellular phone and a user who is typing text on a personal computer. + +![Diagram of cross-modality communication showing speech-to-text (ASR) and text-to-speech (TTS) components.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +The diagram illustrates a cross-modality communication system. On the left, an icon of a person talking on a mobile phone is labeled "Cellular phone". A yellow arrow labeled "Speech" points from this icon to a central "Speech-to-text" block. This block contains a pink header "ASR", a white section "Lexicon speech data", and a yellow cylinder "Language A". A dashed yellow arrow labeled "Text" points from the ASR block to an icon on the right labeled "Text chat", which shows a person using a laptop. From the "Text chat" icon, a dashed blue arrow labeled "Text" points to a central "Text-to-speech" block. This block contains a blue header "TTS", a white section "Lexicon speech data", and a yellow cylinder "Language A". A solid blue arrow labeled "Synthesized speech" points from the TTS block back to the "Cellular phone" icon. The text "H.625(17)\_FI-3" is located in the bottom right corner of the diagram area. + +Diagram of cross-modality communication showing speech-to-text (ASR) and text-to-speech (TTS) components. + +**Figure I.3 – Cross-modality communication** + +# Bibliography + +- [b-ITU-T G.701] Recommendation ITU-T G.701 (1993), *Vocabulary of digital transmission and multiplexing, and pulse code modulation (PCM) terms.* +- [b-ITU-T J.200] Recommendation ITU-T J.200 (2001), *Worldwide common core – Application environment for digital interactive television services.* +- [b-ITU-T P.10] Recommendation ITU-T P.10 (1998), *Vocabulary of terms on telephone transmission quality and telephone sets.* + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d074d6fe14076b8a12aa34cd10f03062bb31a17 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e31471b74508ba517458404db04279a6edb310ec11ced17c214ddece837f99e5 +size 39517 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37bbf750abf158e20f1cb5bc8459a95f9666df22 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01d6c8b87d07f36baca3dd9da4886df13d0cf132eff34e0b8d35051cca270644 +size 59451 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60da49cbb79b76ea43f247fbe7a0fdccaff08056 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61376eb43473f8d5d4196919c7c95062a29df06de27a95d397239e587af48100 +size 13570 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81b9f217a1d0fb6f5ddc704d9699ae96f42f318d --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c22b3a62fd42a064d4a78142f3888d2991e0d071d8a78542a20ef233f33b3c2b +size 9382 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df133a0e6b1c88b98b93c320b2648c56ea3caf39 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:525d0597ca0e240e3a59baaf55a259961953691b9fecfe51195923c9bb4d4ee8 +size 8508 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0aec722666f24dc336832350eff4f7df57211b45 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2c75591b13732880259b266118ca13892ad53a68629bd06692b9967ef1c71df +size 22903 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd3367a9bccc9b4f08d17d9d9582ea9c4f7a8931 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ff5740dc4d91a40376796e480abfd41f4d2b4924e9c854c10687eb63adb69f6 +size 19739 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38e764e4fda33d40798ebf87ed2ad57f92d0eca4 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f828180a3092804c6bd3dfddd2026ebaf51c0b5e5b21b2e3d0014e0633b65e2a +size 32881 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0ac21acf7c14dd70128cd860f62d4b660be20a0 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18068aff3a4ec6f6472848d9aea813559f6d22367532d0593bbe61ba9374a5ca +size 16830 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb4ad8987b516ee32e5d80de6bcbf9dfe3fd185b --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6fdc3abbe4d7fb7ab32e9a6016c1847bfe26e712dd44cdf2e0a04a6fca4002a +size 25872 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4def03e74a65007ad7dac07854f1b6f9e0dfcb61 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0f9bdf9a0f8aac81fed579ea467b322a4178f5a95fff7de560a462881dbe62d +size 44222 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f30d0f6fd80f6625f3ca7b63c5eccf245d7c89de --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddc49246286e2ff520f80eb6964a692ecc67676eb63949cfcfd162dbf429e932 +size 18350 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51c9e447d2ddee1411d2a1f7cac58861db086cf9 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f2c4b95f9ed75eeafb8875b90318d36f6af9cc3c07bb8a26f560d6793ea87a5 +size 16432 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56935b82d379ec47c3f1440a73297925b23a822a --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87ee421e182fc7339aac8eea5c369f2bc6b011e8d1f0ed3b11848382d2dab0a0 +size 16177 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62f3895b6fae767725ef4fcb2fc4625541002820 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8393c533813eb3ffa816beb0da8cd371cbfc1d0c6445fddb5cf057a88094c91 +size 12186 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abb9e3ec6dfc8364cedc39a68cf796e9d3ff5529c79a1811eedeb12c6d6e7583 +size 3787 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28e4cb908af02bdc88706e204f4e56c620102155 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f330c1b036fc0ecdb58b44dd40ac619119ab918eacd054eb25a7bf8bcfe0cc7d +size 13132 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..520ae5604703736795359299bd89ce90bdf9e161 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dca9f60e1811504a7ff7ab105c13c75032a0772b54de6c750652c26dfdde50e +size 10006 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8247662082c5d96209d99ea54bf5e5b09c3c4ee --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd42ac3d8a13e9e4341134120be509f945c5cc14f4ff9c8cc45091dee4e58462 +size 35076 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/f20786b603b41e24b5d5899f710b5947_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/f20786b603b41e24b5d5899f710b5947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5e1f60f6d04901d2edc453fa856f1974d36b23d --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/f20786b603b41e24b5d5899f710b5947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cc93ee7fa8af03debddaec69e563e4737410f8a1c87164326661b877fda03ce +size 30936 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/H/T-REC-H.626-201911-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a58984250b0dca78636754fb857c34672e931bce --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dc6e0d9fa6e86c4bb2832a66738d9c7452747bc06be697009487d31853d48f7 +size 17134 diff --git a/marked/H/T-REC-H.626-201911-I_PDF-E/raw.md b/marked/H/T-REC-H.626-201911-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5e71d6965da70120c92108a85e7533a2f499bec7 --- /dev/null +++ b/marked/H/T-REC-H.626-201911-I_PDF-E/raw.md @@ -0,0 +1,953 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.626** + +(11/2019) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Broadband, triple-play and advanced multimedia +services – Advanced multimedia services and applications + +# --- **Architectural requirements for a video surveillance system** + +Recommendation ITU-T H.626 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.626 + +# Architectural requirements for a video surveillance system + +## Summary + +The purpose of Recommendation ITU-T H.626 is to define a video surveillance system based on IP networks. The video surveillance system provides the display and storage functions of the multimedia (such as video, audio and image) captured by multiple remote cameras over an IP network for multiple users. It also provides other functions, such as remote control, alarm and linkage action, recording and playback. + +This Recommendation defines the model, architecture, entities and reference points of the video surveillance system. This Recommendation also describes the hierarchy model for deployment and interworking between the video surveillance system and other multimedia systems. + +This revision updates the title of this Recommendation, deletes requirements and service flows, and revises the architecture and reference points. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.626 | 2011-05-14 | 16 | 11.1002/1000/11306 | +| 2.0 | ITU-T H.626 (V2) | 2019-11-29 | 16 | 11.1002/1000/14109 | + +## Keywords + +Alarming, camera, IP network, PTZ control, recording and playback, video surveillance. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 5 | +| 6 Functional architecture ..... | 5 | +| 6.1 Functional model ..... | 5 | +| 6.2 Functional architecture ..... | 5 | +| 6.3 System interworking models ..... | 11 | +| 7 Reference points ..... | 13 | +| 7.1 Description of related protocols ..... | 13 | +| 7.2 Reference point Pc: CU-PU..... | 15 | +| 7.3 Reference point Mp/Mp': MS-PU ..... | 15 | +| 7.4 Reference point Cm: CCS-MS ..... | 15 | +| 7.5 Reference point Mc/Mc': MS-CU ..... | 15 | +| 7.6 Reference point Ps: CCS-PU..... | 15 | +| 7.7 Reference point Cs: CCS-CU ..... | 15 | +| 7.8 Reference point Ds/Ds': MDU-MSU ..... | 16 | +| 8 Interworking with other multimedia systems ..... | 16 | +| 8.1 Interworking with videoconferencing ..... | 16 | +| 8.2 Interworking with IPTV ..... | 17 | +| Bibliography..... | 18 | + + + +# Architectural requirements for a video surveillance system + +# 1 Scope + +The video surveillance system is a telecommunication system focusing on video (and audio) application technology, which is used to remotely capture multimedia (such as audio, video, image and various alarm signals), and present them to end users in a friendly manner (including accessibility aspects), based on a managed broadband network with ensured quality, security and reliability. + +The objective of this Recommendation is to define the architectural of the video surveillance system, which meets the needs of video surveillance requirements defined in [ITU-T F.743]. This Recommendation defines the model, functional architecture, entities and reference points of video surveillance system. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T F.743] Recommendation ITU-T F.743 (2019), *Requirements and service description for video surveillance*. +- [ITU-T G.711] Recommendation ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies*. +- [ITU-T G.723.1] Recommendation ITU-T G.723.1 (2006), *Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s*. +- [ITU-T G.729] Recommendation ITU-T G.729 (2012), *Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP)*. +- [ITU-T H.264] Recommendation ITU-T H.264 (2019), *Advanced video coding for generic audiovisual services*. +- [ITU-T H.265] Recommendation ITU-T H.265 (2019), *High efficiency video coding*. +- [ITU-T H.626.3] Recommendation ITU-T H.626.3 (2018), *Architecture for visual surveillance system interworking*. +- [IETF RFC 4571] IETF RFC 4571 (2006), *Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented Transport*. +- [IETF RFC 6086] IETF RFC 6086 (2011), *Session Initiation Protocol (SIP) INFO Method and Package Framework*. +- [IETF RFC 6665] IETF RFC 6665 (2012), *SIP-Specific Event Notification*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 application** [b-ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services. + +**3.1.2 centre control server** [ITU-T H.626.3]: A device located at the centre part of the video surveillance system. It is used for centralized system management, service operation management, and access control. + +NOTE – The centre control server consists of centre management unit and service control unit. + +**3.1.3 customer** [b-ITU-T M.60]: An entity which receives services offered by a service provider based on a contractual relationship. It may include the role of a network user. + +NOTE – In this Recommendation, 'customer' has the same meaning as 'end user'. + +**3.1.4 electronic program guide (EPG)** [b-ITU-T J.200]: A program table that is presented electronically. + +**3.1.5 functional architecture** [b-ITU-T Y.2012]: A set of functional entities, and the reference points between them, used to describe the structure of an NGN. These functional entities are separated by reference points, and thus, they define the distribution of functions. + +NOTE 1 – The functional entities can be used to describe a set of reference configurations. These reference configurations identify which reference points are visible at the boundaries of equipment implementation and between administrative domains. + +NOTE 2 – The definition is not only applicable to NGNs, but also to other IP packet switch based networks. + +**3.1.6 functional entity** [b-ITU-T Y.2012]: An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. + +**3.1.7 interface** [b-ITU-T Y.101]: A shared boundary between two functional units. + +NOTE – An interface is defined by various characteristics pertaining to the functions, physical interconnections, signal exchanges, and other characteristics as appropriate. + +**3.1.8 media** [b-ITU-T Y.101]: Plural of medium. + +**3.1.9 medium** [b-ITU-T Y.101]: a) Specific physical support for transmission or storage of information. b) Type of presentation of information (i.e., video, audio, text, etc.). + +**3.1.10 reference point** [b-ITU-T Y.2012]: A conceptual point at the conjunction of two non-overlapping functional entities that can be used to identify the type of information passing between these functional entities. + +NOTE – A reference point may correspond to one or more physical interfaces between pieces of equipment. + +**3.1.11 role** [b-ITU-T Y.110]: The role is a business activity which fits in a value chain. The role is constrained by the smallest scale of business activity which could exist independently in the industry and so a marketplace will exist for every relationship between roles. + +**3.1.12 service** [b-ITU-T Y.101]: A structured set of capabilities intended to support applications. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +- 3.2.1 centre management unit:** A device located at the main part of a video surveillance system. It is used for centralized system management, service operation management, etc. The main functions include management, authorization, accounting, charging, location and presence. +- 3.2.2 customer unit:** A device located at the customer part of a video surveillance system and used to present multimedia information (such as audio, video, image, alarm signal, etc.) to the end user. +- 3.2.3 media distribution unit:** A device located at the centre part of a video surveillance system. It is used to transport media from the premises unit (PU) to the customer unit (CU). The main functions include media receiving, media processing, media routing, media transmission, media forwarding and media replication, etc. +- 3.2.4 media server:** A device located at the centre part of a video surveillance system. It is used to forward real-time media stream as well as store, retrieve and replay historical media stream. The media server receives the media stream from premises unit or other media server and forwards the media stream to other customer unit or media server. It consists of media distribution unit and media storage unit. +- 3.2.5 media storage unit:** A device located at the centre part of a video surveillance system. It is used to retrieve, store media and provide a streaming media serving capability. The main functions include media storage, media serving, media indexing and media downloading, etc. +- 3.2.6 premises unit:** A device located at the remote part of a video surveillance system and used to capture multimedia information (such as audio, video, image, alarm signal, etc.) from a surveilled object. +- 3.2.7 service control unit:** A device located at the main part of a video surveillance system. It is used to access service control and signal call control between the PU and the CU. The main functions include access registration, access authentication, identification, authorization, call control, location, presence, and target media serving function selection. +- 3.2.8 service platform:** A series of devices and subsystems located at the centre part of a video surveillance system. It is used to integrate all of the capabilities and provide video surveillance services to customers. The main functions include service-control function, media switching, distribution, storage, and control and management. +- 3.2.9 surveillant:** The individual performing surveillance. +- 3.2.10 surveilled object:** The target (such as site, human, and related environment) on which surveillance is performed. +- 3.2.11 video surveillance system:** A telecommunication service focusing on video (including audio and image) application technology, which is used to remotely capture multimedia (such as audio, video, image, alarm signal, etc.) and present them to the end user in a user-friendly manner, based on a managed broadband network with ensured quality, security and reliability. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|----------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| AAC | Advanced Audio Coding | +| AVC | Advanced Video Coding | +| CCS | Central Control Server | +| CDN | Content Delivery Network | +| CDR | Charging Data Record | + +| | | +|------|-----------------------------------------| +| CMU | Centre Management Unit | +| CPG | Control Protocol Gateway | +| CU | Customer Unit | +| ECCS | Extended Control Command Set | +| EMCS | Extended Media Command Set | +| EPG | Electronic Programme Guide | +| GUI | Graphical User Interface | +| HEVC | High Efficiency Video Coding | +| HVSS | Heterogeneous Video Surveillance System | +| ID | Identification | +| IP | Internet Protocol | +| IPC | IP Camera | +| IPTV | Internet Protocol Television | +| MCU | Multimedia Control Unit | +| MDU | Media Distribution Unit | +| MG | Media Gateway | +| MOC | Monitor Centre | +| MS | Media Server | +| MSU | Media Storage Unit | +| NGN | Next Generation Network | +| NVR | Network Video Recorder | +| PC | Personal Computer | +| PTZ | Pan/Tilt/Zoom | +| PU | Premises Unit | +| RTP | Real-time Transport Protocol | +| RTCP | RTP Control Protocol | +| SCU | Service Control Unit | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| SRG | Signal Routing Gateway | +| STB | Set-Top Box | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | +| VS | Video Surveillance | +| VSS | Video Surveillance System | + +# 5 Conventions + +None. + +# 6 Functional architecture + +This clause describes the basic functional model, functional architecture, functional entities and system interworking which pertain to video surveillance (VS). + +## 6.1 Functional model + +The basic functional model for VS consists of customer units (CUs), PUs and a service platform. The interface Pi is the interface between PUs and the service platform, and the interface Ci is the interface between CUs and the service platform. This is illustrated in Figure 6-1. + +![Figure 6-1: Functional model of video surveillance system. The diagram shows a central 'Service platform (Application/Service/Media/Network)' connected to multiple 'PU(1)' through 'PU(n)' units via the 'Pi interface' and to multiple 'CU(1)' through 'CU(n)' units via the 'Ci interface'. The entire system is labeled 'VSS' and is flanked by 'Surveilled objects' on the left and a 'Surveillant' on the right. The reference 'H.626(19)_F6-1' is shown in the bottom right corner.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +The diagram illustrates the functional model of a video surveillance system (VSS). A central 'Service platform (Application/Service/Media/Network)' is connected to multiple 'PU(1)' through 'PU(n)' units via the 'Pi interface' and to multiple 'CU(1)' through 'CU(n)' units via the 'Ci interface'. The entire system is labeled 'VSS' and is flanked by 'Surveilled objects' on the left and a 'Surveillant' on the right. The reference 'H.626(19)\_F6-1' is shown in the bottom right corner. + +Figure 6-1: Functional model of video surveillance system. The diagram shows a central 'Service platform (Application/Service/Media/Network)' connected to multiple 'PU(1)' through 'PU(n)' units via the 'Pi interface' and to multiple 'CU(1)' through 'CU(n)' units via the 'Ci interface'. The entire system is labeled 'VSS' and is flanked by 'Surveilled objects' on the left and a 'Surveillant' on the right. The reference 'H.626(19)\_F6-1' is shown in the bottom right corner. + +Figure 6-1 – Functional model of video surveillance system + +## 6.2 Functional architecture + +This clause provides the functional architecture of the video surveillance system (VSS). + +### 6.2.1 Overview of entities + +The VSS functional architecture could be decomposed into eight units: + +- Centre management unit (CMU) +- Service-control unit (SCU) +- Media storage unit (MSU) +- Media distribution unit (MDU) +- Premises unit (PU) +- Customer unit (CU) +- Centre control server (CCS) +- Media server (MS) + +The units shown in Figure 6-2 are described in clauses 6.2.2 to 6.2.9 and the interfaces in clause 7. + +![Functional architecture of VSS diagram showing components: CCS (CMU, SCU), MS (MDU, MSU), PU, and CU. It illustrates media and control signal flows between these units. A legend at the bottom indicates black arrows for Media and red arrows for Control. The diagram is labeled H.626(19)_F6-2.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph TD + subgraph CCS [CCS] + CMU + SCU + end + subgraph MS [MS] + MDU + MSU + end + PU + CU + + %% Control flows (red in original) + PU -- Ps --> CCS + CU -- Cs --> CCS + CCS -- Cm --> MS + PU -- Mp' --> MDU + MDU -- Mp' --> PU + MDU -- Ds' --> MSU + MSU -- Mc' --> CU + + %% Media flows (black in original) + PU -- Mp --> MDU + MDU -- Mp --> PU + MDU -- Ds --> MSU + MSU -- Mc --> CU + PU -- Pc --> CU + +``` + +The diagram illustrates the functional architecture of VSS. It consists of several functional blocks: + +- CCS (Communication Control System)**: Contains **CMU (Centre Management Unit)** and **SCU (Service-Control Unit)**. A bidirectional red control arrow labeled $C_m$ connects CCS to MS. +- MS (Media System)**: Contains **MDU (Media Distribution Unit)** and **MSU (Media Serving Unit)**. They are connected by a black media arrow labeled $D_s$ and a red control arrow labeled $D_s'$ . +- PU (User Equipment)** and **CU (Customer Unit)** are at the bottom. + +Signal flows are as follows: + +- Media (black arrows)**: PU ↔ MDU (labeled $M_p$ ), MDU → MSU (labeled $D_s$ ), MSU → CU (labeled $M_c$ ), and PU ↔ CU (labeled $P_c$ ). +- Control (red arrows)**: PU → CCS (labeled $P_s$ ), CU → CCS (labeled $C_s$ ), CCS ↔ MS (labeled $C_m$ ), PU ↔ MDU (labeled $M_p'$ ), MDU ↔ MSU (labeled $D_s'$ ), and MSU ↔ CU (labeled $M_c'$ ). + +A legend at the bottom shows a black arrow for 'Media' and a red arrow for 'Control'. The diagram is labeled H.626(19)\_F6-2. + +Functional architecture of VSS diagram showing components: CCS (CMU, SCU), MS (MDU, MSU), PU, and CU. It illustrates media and control signal flows between these units. A legend at the bottom indicates black arrows for Media and red arrows for Control. The diagram is labeled H.626(19)\_F6-2. + +**Figure 6-2 – Functional architecture of VSS** + +### 6.2.2 CMU: centre management unit + +The centre management unit (CMU) is used for centralized system management, service operation management, etc. + +Accordingly, the main functions of the CMU include management, authorization, accounting and charging, location and presence. The detailed functional features are: + +- Management: managing content, service, network, PU, etc. +- Authorization: authorizing access right. +- Accounting and charging: providing charging data record (CDR) and charging policy, etc. + +### 6.2.3 SCU: service-control unit + +The service-control unit (SCU) is used to access service control and signal call control between the PU and the CU. + +Accordingly, SCU main functions include access registration, access authentication, identification, authorization, call control, location, presence, and target media serving function selection. The detailed functional features are: + +- Access registration: receiving the access registration request from the CU and the PU, and registering them with the registration management server. +- Access authentication: receiving the access authentication request from the CU and the PU, and as an authentication server function, forward (proxy) authentication signals between the authentication, authorization and accounting (AAA) servers. +- Identification: identifying the CU and the PU, and comparing identities with subscriber data and terminal data to determine matching results. +- Authorization: authorize CU and PU access rights. +- Call control: mediate the call control session with the PU and the CU, establish and maintain media transport path information (media routing table, i.e., MRT). The related session methods could include setup, tear down, update, modify and keep live, in order to access, route and relay. +- Location: Locating the PU, if required, providing the placement information of the PU and the CU. +- Presence: presenting the status of the CU and the PU, such as on-line, offline, active, inactive, etc. +- Clock synchronization: providing unified time criteria and clock synchronization control. + +- Media serving function selection: selecting one media serving function unit (i.e., media distribution unit and related media storage unit) when one SCU controls multiple media serving function units. + +### 6.2.4 CCS: centre control server + +The CCS is used for centralized system management, service operation management, and access control. It consists of the CMU and the SCU. + +### 6.2.5 MDU: media distribution unit + +The media distribution unit (MDU) is used to transport media from the PU to the CU. + +Accordingly, the main functions of the MDU include media receiving, media processing, media routing, media transmission, media forwarding, media replication, etc. The detailed functional features are: + +- Media receiving: receiving media (stream and files) from the PU. +- Media processing: muxing/demuxing, decoding/encoding and transcoding media that is received by the MDU, as required. +- Media routing: seeking media routing information between the PU and the CU in the media routing table in order to decide on the media transport path and destination routing port. +- Media transmission: transmitting media to a CU or multiple CUs on request, according to media routing information. + +NOTE – Transmission from one PU to multiple CUs requires conversion from a unicast media channel to a multicast media channel). + +- Media forwarding: forwarding media from the current MDU (Domain A) to another MDU (Domain B), in order to access the remote CU (Domain B) under the control of the SCU. +- Media replication: replicating media for point-to-multipoint transmission, if required. + +NOTE – The alternative approach is to convert the unicast media channel to a multicast media channel. For this situation, the media replication is not needed. + +The MDU internal process is illustrated in Figure 6-3 and the VS end-to-end media transport process is illustrated in Figure 6-4. + +![Figure 6-3: MDU internal process diagram. The diagram shows a linear flow of media processing: Receiving → Processing → Routing. From the Routing block, the path splits into two dashed boxes: 'Replication' and 'Forwarding'. Both dashed boxes lead to a 'Transmission' block, which then outputs to the right. A label 'H.626(19)_F6-3' is at the bottom right.](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg) + +Figure 6-3: MDU internal process diagram. The diagram shows a linear flow of media processing: Receiving → Processing → Routing. From the Routing block, the path splits into two dashed boxes: 'Replication' and 'Forwarding'. Both dashed boxes lead to a 'Transmission' block, which then outputs to the right. A label 'H.626(19)\_F6-3' is at the bottom right. + +Figure 6-3 – MDU internal process + +![Figure 6-4: VS E2E media-transport process diagram. The diagram shows a PU (Processing Unit) connected to an MDU (Media Distribution Unit). Inside the MDU, the flow is: Receiving → Processing → Routing. From the Routing block, the path splits into two dashed boxes: 'Replication' and 'Forwarding'. Both dashed boxes lead to a 'Transmission' block. The 'Transmission' block outputs to a CU (Control Unit) and another MDU. A label 'H.626(19)_F6-4' is at the bottom right.](f20786b603b41e24b5d5899f710b5947_img.jpg) + +Figure 6-4: VS E2E media-transport process diagram. The diagram shows a PU (Processing Unit) connected to an MDU (Media Distribution Unit). Inside the MDU, the flow is: Receiving → Processing → Routing. From the Routing block, the path splits into two dashed boxes: 'Replication' and 'Forwarding'. Both dashed boxes lead to a 'Transmission' block. The 'Transmission' block outputs to a CU (Control Unit) and another MDU. A label 'H.626(19)\_F6-4' is at the bottom right. + +Figure 6-4 – VS E2E media-transport process + +The four media transport modes among PU, CU and MDU are: + +- Type A: Conversation mode (point-to-point), see Figure 6-5. +- Type B: Distribution mode (point-to-multipoint), see Figure 6-6. +- Type C: Collecting mode (multipoint-to-point), see Figure 6-7. +- Type D: Conferencing mode (multipoint-to-multipoint), see Figure 6-8. + +![Figure 6-5: Type A media transport mode (point-to-point mode). A diagram showing a flow from PU to MDU to CU. Arrows labeled 'Media' connect PU to MDU and MDU to CU. The label H.626(19)_F6-5 is at the bottom right.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +``` +graph LR; PU[PU] -- Media --> MDU[MDU]; MDU -- Media --> CU[CU]; +``` + +Figure 6-5: Type A media transport mode (point-to-point mode). A diagram showing a flow from PU to MDU to CU. Arrows labeled 'Media' connect PU to MDU and MDU to CU. The label H.626(19)\_F6-5 is at the bottom right. + +**Figure 6-5 – Type A media transport mode (point-to-point mode)** + +![Figure 6-6: Type B media transport mode (point-to-multipoint mode). A diagram showing a flow from PU to MDU, which then branches to multiple CUs (CU(1) to CU(n)). Arrows labeled 'Media' connect PU to MDU and MDU to each CU. The label H.626(19)_F6-6 is at the bottom right.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` +graph LR; PU[PU] -- Media --> MDU[MDU]; MDU -- Media --> CU1[CU(1)]; MDU -- Media --> CUn[CU(n)]; +``` + +Figure 6-6: Type B media transport mode (point-to-multipoint mode). A diagram showing a flow from PU to MDU, which then branches to multiple CUs (CU(1) to CU(n)). Arrows labeled 'Media' connect PU to MDU and MDU to each CU. The label H.626(19)\_F6-6 is at the bottom right. + +**Figure 6-6 – Type B media transport mode (point-to-multipoint mode)** + +![Figure 6-7: Type C media transport mode (multipoint-to-point mode). A diagram showing multiple PUs (PU(1) to PU(m)) sending media to a single MDU, which then sends media to a single CU. Arrows labeled 'Media' connect each PU to MDU and MDU to CU. The label H.626(19)_F6-7 is at the bottom right.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +``` +graph LR; PU1[PU(1)] -- Media --> MDU[MDU]; PUm[PU(m)] -- Media --> MDU; MDU -- Media --> CU[CU]; +``` + +Figure 6-7: Type C media transport mode (multipoint-to-point mode). A diagram showing multiple PUs (PU(1) to PU(m)) sending media to a single MDU, which then sends media to a single CU. Arrows labeled 'Media' connect each PU to MDU and MDU to CU. The label H.626(19)\_F6-7 is at the bottom right. + +**Figure 6-7 – Type C media transport mode (multipoint-to-point mode)** + +![Figure 6-8: Type D media transport mode (multipoint-to-multipoint mode). A diagram showing multiple PUs (PU(1) to PU(m)) sending media to a single MDU, which then branches to multiple CUs (CU(1) to CU(n)). Arrows labeled 'Media' connect each PU to MDU and MDU to each CU. The label H.626(19)_F6-8 is at the bottom right.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` +graph LR; PU1[PU(1)] -- Media --> MDU[MDU]; PUm[PU(m)] -- Media --> MDU; MDU -- Media --> CU1[CU(1)]; MDU -- Media --> CUn[CU(n)]; +``` + +Figure 6-8: Type D media transport mode (multipoint-to-multipoint mode). A diagram showing multiple PUs (PU(1) to PU(m)) sending media to a single MDU, which then branches to multiple CUs (CU(1) to CU(n)). Arrows labeled 'Media' connect each PU to MDU and MDU to each CU. The label H.626(19)\_F6-8 is at the bottom right. + +**Figure 6-8 – Type D media transport mode (multipoint-to-multipoint mode)** + +### 6.2.6 MSU: media storage unit + +The media storage unit (MSU) is used to retrieve, store media and provide a streaming media serving capability. + +Accordingly, MSU main functions include media storage, media serving, media indexing, media downloading, etc. The detailed functional features are: + +- Media retrieval: retrieving audio and/or video media streams and image files from PU and/or MDU. +- Media storage: storing recorded audio, video and image files from PU and/or MDU. + +NOTE 1 – The images from the PU can be stored directly in the MSU, without the control of the MDU. + +NOTE 2 – Alternatively, images can be stored by the independent image file storage server (IFSS), which is out of the scope of the MSU. For this situation, IFSS could not be controlled by the MDU. + +- Media serving: serving audio and video to one CU or multiple CUs with media streaming on request of playback service. +- Media indexing: indexing audio, video and images files when stored for further media searching on request. + +The MSU internal process is illustrated in Figure 6-9. + +The VS end-to-end media storage and serving process is illustrated in Figure 6-10. + +The media transport mode for PU and playback service among MDU, MSU and CU is illustrated in Figure 6-11a and Figure 6-11b. + +![Figure 6-9: MSU internal process flowchart showing the sequence: Retrieving, Storing, Indexing, and Serving, with a dashed box for Searching connected to the Indexing and Serving stages. The diagram is labeled H.626(19)_F6-9.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +``` + +graph LR + A[Retrieving] --> B[Storing] + B --> C[Indexing] + C --> D[Serving] + D --> E[H.626(19)_F6-9] + C -.-> F[Searching] + F -.-> D + +``` + +Figure 6-9: MSU internal process flowchart showing the sequence: Retrieving, Storing, Indexing, and Serving, with a dashed box for Searching connected to the Indexing and Serving stages. The diagram is labeled H.626(19)\_F6-9. + +**Figure 6-9 – MSU internal process** + +![Figure 6-10: VS end-to-end media storage and serving process flowchart showing the flow from MDU to MSU (containing internal steps: Retrieving, Storing, Indexing, Searching, and Serving) to CU. The diagram is labeled H.626(19)_F6-10.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +graph LR + MDU[MDU] --> MSU + subgraph MSU [MSU] + R[Retrieving] --> S[Storing] + S --> I[Indexing] + I -.-> Search[Searching] + Search -.-> Serv[Serving] + end + MSU --> CU[CU] + CU --> H626[H.626(19)_F6-10] + +``` + +Figure 6-10: VS end-to-end media storage and serving process flowchart showing the flow from MDU to MSU (containing internal steps: Retrieving, Storing, Indexing, Searching, and Serving) to CU. The diagram is labeled H.626(19)\_F6-10. + +**Figure 6-10 – VS end-to-end media storage and serving process** + +![Figure 6-11a: Media transport mode – PU playback service flowchart showing the flow from PU to MDU to MSU to multiple CUs (CU(1) to CU(n)). The diagram is labeled H.626(19)_F6-11a.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +``` + +graph LR + PU[PU] -- Media --> MDU[MDU] + MDU -- Media --> MSU[MSU] + MSU -- Media --> CU1[CU(1)] + MSU -- Media --> CU2[CU(2)] + MSU -- Media --> CUn[CU(n)] + CU1 -.-> Dots1[...] + CU2 -.-> Dots2[...] + CUn --> H626[H.626(19)_F6-11a] + +``` + +Figure 6-11a: Media transport mode – PU playback service flowchart showing the flow from PU to MDU to MSU to multiple CUs (CU(1) to CU(n)). The diagram is labeled H.626(19)\_F6-11a. + +**Figure 6-11a – Media transport mode – PU playback service** + +![Figure 6-11b: Media transport mode – platform playback service flowchart showing the flow from MSU to multiple CUs (CU(1) to CU(n)). The diagram is labeled H.626(19)_F6-11b.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +``` + +graph LR + MSU[MSU] -- Media --> CU1[CU(1)] + MSU -- Media --> CU2[CU(2)] + MSU -- Media --> CUn[CU(n)] + CU1 -.-> Dots1[...] + CU2 -.-> Dots2[...] + CUn --> H626[H.626(19)_F6-11b] + +``` + +Figure 6-11b: Media transport mode – platform playback service flowchart showing the flow from MSU to multiple CUs (CU(1) to CU(n)). The diagram is labeled H.626(19)\_F6-11b. + +**Figure 6-11b – Media transport mode – platform playback service** + +### 6.2.7 MS: media server + +The MS is used to forward real-time media stream as well as store, retrieve and replay historical media stream. The media server receives the media stream from premises unit or other media server and forwards the media stream to other client unit or media server. It consists of the media distribution unit and the media storage unit. + +### 6.2.8 PU: premises unit + +The PU refers to the premise subsystem within the VSS. It implements the following functions: + +- Captures multimedia information (such as audio, video, image, alarm signals, etc.) from the surveilled object; +- Encodes multimedia (audio, video, image); +- Outputs alarm signal to external linkage device; +- Parses pan/tilt/zoom (PTZ) command codes and transmit them to the devices in order to control remote direction and zoom; +- Provides network transport, and transmits bidirectional media stream to other entities and alarm signals. + +The media storage function is optional for the PU. + +Audio decoding and play function is optional for the PU. + +Figure 6-12 shows the function composition of the PU. + +![Figure 6-12: Function composition of the PU. This block diagram illustrates the internal functional architecture of a Processing Unit (PU). On the left, a vertical stack of seven function blocks is shown: 'Video capture function', 'Audio capture function', 'Audio play function', 'PTZ control function', 'Alarm input function', 'Alarm output function', and 'Media storage function'. Below this stack is a wide block labeled 'Transport function'. To the right is a large vertical block labeled 'Control and management function'. Black arrows represent 'Media' flows: from 'Video capture function' to 'Video encoding function', from 'Audio capture function' to 'Audio encoding function', and from 'Audio decoding function' to 'Audio play function'. Red arrows represent 'Control' flows: from the 'Control and management function' to 'Video encoding function', 'Audio encoding function', 'Audio decoding function', 'PTZ control function', 'Alarm input function', 'Alarm output function', and 'Media storage function'. A legend at the bottom left shows a black arrow labeled 'Media' and a red arrow labeled 'Control'. The diagram is labeled 'H.626(19)_F6-12' in the bottom right corner.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` +graph LR + subgraph Media_Flows + VCF[Video capture function] -- Media --> VEF[Video encoding function] + AC[Audio capture function] -- Media --> AE[Audio encoding function] + AD[Audio decoding function] -- Media --> AP[Audio play function] + end + CMF[Control and management function] -- Control --> VEF + CMF -- Control --> AE + CMF -- Control --> AD + CMF -- Control --> PCF[PTZ control function] + CMF -- Control --> AIF[Alarm input function] + CMF -- Control --> AOF[Alarm output function] + CMF -- Control --> MSF[Media storage function] + TF[Transport function] +``` + +Figure 6-12: Function composition of the PU. This block diagram illustrates the internal functional architecture of a Processing Unit (PU). On the left, a vertical stack of seven function blocks is shown: 'Video capture function', 'Audio capture function', 'Audio play function', 'PTZ control function', 'Alarm input function', 'Alarm output function', and 'Media storage function'. Below this stack is a wide block labeled 'Transport function'. To the right is a large vertical block labeled 'Control and management function'. Black arrows represent 'Media' flows: from 'Video capture function' to 'Video encoding function', from 'Audio capture function' to 'Audio encoding function', and from 'Audio decoding function' to 'Audio play function'. Red arrows represent 'Control' flows: from the 'Control and management function' to 'Video encoding function', 'Audio encoding function', 'Audio decoding function', 'PTZ control function', 'Alarm input function', 'Alarm output function', and 'Media storage function'. A legend at the bottom left shows a black arrow labeled 'Media' and a red arrow labeled 'Control'. The diagram is labeled 'H.626(19)\_F6-12' in the bottom right corner. + +**Figure 6-12 – Function composition of the PU** + +The devices of the PU include video capture devices such as various cameras and audio capture devices like microphones, pan and tilt devices, alarm input and output devices, and audio/video/image encoding devices. + +The PU main reference internal process is as follows. + +After encoding by an encoding device of the video stream captured by a camera, of a voice stream captured by a microphone, and of alarm information collected by an alarm device, the PU sends the compressed information or media stream to the service platform or the customer unit that requests this information for real-time surveillance. Meanwhile, the PU extracts the control signal sent from the service platform, parsing the command code and transmitting the PTZ control command to pan and tilt the device to implement PTZ control. + +### 6.2.9 CU: customer unit + +The CU is the customer unit within the VSS. It is used to present multimedia information (such as audio, video, image, and alarm signal) to the end user. It implements the following functions: + +- Multimedia decoding function; +- Audio play and video/image display function; +- Console interface for the end user to operate the VSS. + +Figure 6-13 shows the CU functional composition. + +![Figure 6-13 – CU functional composition diagram showing three functional blocks: 'Play and display function', 'Console function', and 'Audio/video/image decoding function'. Arrows indicate the flow of media and control signals between these functions. A legend at the bottom indicates that black arrows represent 'Media' and red arrows represent 'Control'. The diagram is labeled H.626(19)_F6-13.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +graph TD + CF[Console function] -- Control --> AVID[Audio/video/image decoding function] + AVID -- Media --> PDF[Play and display function] + style CF fill:#fff,stroke:#000 + style AVID fill:#fff,stroke:#000 + style PDF fill:#fff,stroke:#000 + style MediaLine stroke:black,stroke-width:2px + style ControlLine stroke:red,stroke-width:2px + +``` + +→ Media      → Control +H.626(19)\_F6-13 + +Figure 6-13 – CU functional composition diagram showing three functional blocks: 'Play and display function', 'Console function', and 'Audio/video/image decoding function'. Arrows indicate the flow of media and control signals between these functions. A legend at the bottom indicates that black arrows represent 'Media' and red arrows represent 'Control'. The diagram is labeled H.626(19)\_F6-13. + +**Figure 6-13 – CU functional composition** + +The CU main reference process is as follows. + +After decoding and transcoding the media stream transported from the service platform or the PU by the decoding function entity, the media is output to the play and display function entity for presentation to the end user. The play and display function entity can implement some advanced functions, such as the multi-picture surveillance, multi-screen display, multi-screen alternation (e.g., auto-patrol), caption overlay, and designated-area shielding. + +The console function provides the graphical user interface (GUI) to operate and control the VSS for end use. Through the console function, the authorized end user can, e.g., select and display remote video (audio is optional) of one or more surveilled objects, receive alarm signals and trigger linkage actions, set and control the display model, configure the auto-record or alarm conditions, start or stop recoding, and search and play the recorded file. + +The CU could be based on personal computer (PC), monitor centre (MOC), mobile phone, embedded video decoder, embedded web page client, Internet protocol television (IPTV) set top box (STB), etc. + +## 6.3 System interworking models + +This clause introduces the interworking models for VSS, including interworking model for homogeneous video surveillance systems, interworking model for heterogeneous video surveillance systems, and deployment models for video surveillance interworking. + +### 6.3.1 Interworking for homogeneous video surveillance systems + +Figure 6-14 illustrates the interworking model for homogeneous video surveillance systems. As shown in Figure 6-14, VSS A and VSS B are two homogeneous video surveillance systems, and this means that the two systems have the same architecture, transmission protocol, control signals, and data formats. One video surveillance system is composed of CCS, MS, PU, CU as well as other functional entities. For the interworking of homogeneous video surveillance systems, a new system functional entity, which is signal routing gateway (SRG), is used to route the control signals between the two systems, and the media can be received and forwarded through the MSs of the two systems. + +![Figure 6-14: Interworking model for homogeneous video surveillance systems. The diagram shows two systems, VSS A and VSS B, connected via an IP network. Each system contains a PU (Power Unit), CU (Control Unit), MS (Media Server), SRG (Signaling Resource Group), and CCS (Control Center System). Media streams (black arrows) flow from PU to CU, then to MS, and finally to the IP network. Control signals (red arrows) flow from the IP network to MS, then to SRG, and finally to CCS. Within each system, there are also internal control signal flows between CCS, SRG, and MS. The diagram is labeled H.626(19)_F6-14.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Figure 6-14: Interworking model for homogeneous video surveillance systems. The diagram shows two systems, VSS A and VSS B, connected via an IP network. Each system contains a PU (Power Unit), CU (Control Unit), MS (Media Server), SRG (Signaling Resource Group), and CCS (Control Center System). Media streams (black arrows) flow from PU to CU, then to MS, and finally to the IP network. Control signals (red arrows) flow from the IP network to MS, then to SRG, and finally to CCS. Within each system, there are also internal control signal flows between CCS, SRG, and MS. The diagram is labeled H.626(19)\_F6-14. + +**Figure 6-14 – Interworking model for homogeneous video surveillance systems** + +### 6.3.2 Interworking for heterogeneous video surveillance systems + +Figure 6-15 illustrates the interworking model for heterogeneous video surveillance systems. As shown in Figure 6-15, the heterogeneous video surveillance system (HVSS) has a different architecture, transmission protocol, control signals and data formats from the standardized video surveillance system defined in this Recommendation. The VSS can communicate with the HVSS through the control protocol gateway (CPG) and media gateway (MG). The CPG is used for the switching network transmission protocols, control signals and device addresses between the VSS and the HVSS. The MG is used for switching media transmission protocols and media data coding formats between the VSS and the HVSS. + +![Figure 6-15: Interworking model for heterogeneous video surveillance systems. The diagram shows a VSS (Video Surveillance System) connected to an HVSS (Heterogeneous Video Surveillance System) via two gateways: CPG (Control Protocol Gateway) and MG (Media Gateway). Media streams (black arrows) flow from VSS to MG and then to HVSS. Control signals (red arrows) flow from VSS to CPG and then to HVSS. The diagram is labeled H.626(19)_F6-15.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +Figure 6-15: Interworking model for heterogeneous video surveillance systems. The diagram shows a VSS (Video Surveillance System) connected to an HVSS (Heterogeneous Video Surveillance System) via two gateways: CPG (Control Protocol Gateway) and MG (Media Gateway). Media streams (black arrows) flow from VSS to MG and then to HVSS. Control signals (red arrows) flow from VSS to CPG and then to HVSS. The diagram is labeled H.626(19)\_F6-15. + +**Figure 6-15 – Interworking model for heterogeneous video surveillance systems** + +### 6.3.3 Topology models for video surveillance interworking + +There are two topology models for interworking among different video surveillance systems, including the peer-to-peer topology model and the hierarchical topology model. + +In the peer-to-peer topology model, as shown in Figure 6-16, two adjacent VSSs are in the peer-to-peer relationship. When the surveillance resources need to be shared between two systems, the initiator SRG in one system initiates registration to the target SRG in another system actively. The communication between two systems can only be performed when the initiator SRG has been authenticated by the target SRG. In this flat interworking topology structure model, the signal and media streams are directly forwarded between two systems through SRG and MS respectively. + +![Figure 6-16: Peer-to-peer topology model. The diagram shows three video surveillance systems: VSS_A, VSS_B, and VSS_C. VSS_A is at the top, connected to both VSS_B and VSS_C. VSS_B and VSS_C are at the bottom, connected to each other. All connections are represented by double-headed arrows, indicating peer-to-peer relationships. The diagram is labeled H.626(19)_F6-16.](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +Figure 6-16: Peer-to-peer topology model. The diagram shows three video surveillance systems: VSS\_A, VSS\_B, and VSS\_C. VSS\_A is at the top, connected to both VSS\_B and VSS\_C. VSS\_B and VSS\_C are at the bottom, connected to each other. All connections are represented by double-headed arrows, indicating peer-to-peer relationships. The diagram is labeled H.626(19)\_F6-16. + +**Figure 6-16 – Peer-to-peer topology model** + +In the hierarchical topology model, as shown in Figure 6-17, two adjacent VSSs are in the superior-subordinate relationship. The subordinate SRG in one system initiates registration to the + +superior SRG in another system actively, and communication between the adjacent systems can only be performed when the subordinate SRG has been authenticated by the superior SRG. In this multilevel interworking topology structure model, the signal and media streams are forwarded layer by layer through CPG and MG respectively. + +![Figure 6-17 – Hierarchical topology model. A tree diagram showing VSS_A at the top, connected to VSS_B and VSS_C. VSS_B is connected to VSS_D and VSS_E. VSS_C is connected to VSS_F and VSS_G. All connections are bidirectional arrows.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg) + +``` + +graph TD + VSS_A[VSS_A] <--> VSS_B[VSS_B] + VSS_A <--> VSS_C[VSS_C] + VSS_B <--> VSS_D[VSS_D] + VSS_B <--> VSS_E[VSS_E] + VSS_C <--> VSS_F[VSS_F] + VSS_C <--> VSS_G[VSS_G] + +``` + +H.626(19)\_F6-17 + +Figure 6-17 – Hierarchical topology model. A tree diagram showing VSS\_A at the top, connected to VSS\_B and VSS\_C. VSS\_B is connected to VSS\_D and VSS\_E. VSS\_C is connected to VSS\_F and VSS\_G. All connections are bidirectional arrows. + +**Figure 6-17 – Hierarchical topology model** + +NOTE – [ITU-T H.626.3] describes the architecture and topology models for video surveillance systems interworking in more detail. + +# 7 Reference points + +This clause defines reference points. + +## 7.1 Description of related protocols + +### 7.1.1 General description + +The information transmission, switch and control of information such as command, video, audio, etc., within the VSS shall conform to the communication protocols specified in clause 7.1.1. The structure of communication is shown in Figure 7-1. + +![](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +| Session channel | | | Media stream channel | | +|-----------------|------|------|----------------------|-----------------------------------| +| SDP | ECCS | EMCS | ITU-T H.264/H.265 | ITU-T G.711/G.723.1/
    G.729/AAC | +| SIP | | | RTP/RTCP | | +| TCP/UDP | | | TCP/UDP | | +| IP | | | | | + +H.626(19)\_F7-1 + +**Figure 7-1 – Structure of communication** + +The VSS shall establish two transmission channels, the session channel and the media stream channel, during video and audio transmission and control. The session channel is used for establishing sessions and transmission system control signals among devices. The media stream channel is used for transmitting video and audio stream, and the compressed video and audio stream is transmitted through real-time transport protocol/RTP control protocol (RTP/RTCP). The network layer of the VSS shall support IP, and the transport layer shall support transmission control protocol (TCP) and user datagram protocol (UDP). + +### 7.1.2 Session protocol requirements + +The following are session protocol requirements (SPRs): + +#### **SPR-1: Session initiation protocol** + +The session control of applications as secure registration, live video streaming, historical video and audio playback, etc., adopt the session initiation protocol (SIP) [b-IETF RFC 3261] method, such as REGISTER and INVITE. The historical video and audio playback control is implemented with the INFO method adopt INFO method and package framework [IETF RFC 6086]. The session control of such applications as PU control, information query and alarm event notification and distribution are implemented with the MESSAGE method adopting SIP extensions for instant messaging. SUBSCRIBE and NOTIFY methods adopt SIP specific event notification [IETF RFC 6665]. + +#### **SPR-2: Session description protocol** + +The session negotiation and media negotiation between the relevant devices of the network system in the session establishment process adopt session description protocol (SDP), mainly including the session, media and time related information description. The session negotiation and the media negotiation information shall be carried and transported through SIP messages. + +#### **SPR-3: Extended control command set** + +The control commands of the PU control, alarm messages and device directory information of VSS adopt the extended control command set (ECCS). ECCS is carried and transported within the message body of SIP MESSAGE. + +#### **SPR-4: Extended media command set** + +The historical video and audio playback control commands adopt the extended media command set (EMCS) to control play, fast forward, pause, stop, dragging the mouse and play, etc., of video and audio stream. EMCS is carried and transported within the message body of SIP INFO. + +### 7.1.3 Media protocol requirements + +The following are media protocol requirements (MPRs): + +#### **MPR-1: Media transmission protocol** + +In VSS, the transmission of media stream shall support RTP, and the PU shall be able to control bit rate peak. RTP load shall apply one of the following two formats: video and audio based on PS packaging or video and audio elementary stream. The transmission of the media stream based on the UDP shall adopt the RTP. The transmission of the media stream based on the TCP shall comply with [IETF RFC 4571], providing timestamp information in real-time transmission and synchronization of various streams. It adopts RTCP to provide a reliable guarantee for data package transport in order as well as flow control and congestion control. + +#### **MPR-2: Media compression** + +The video compression adopts [ITU-T H.264] (AVC), [ITU-T H.265] (HEVC) Recommendation, etc. The audio compression adopts [ITU-T G.711], [ITU-T G.723.1], [ITU-T G.729] and advanced audio coding (AAC) Recommendation. + +#### **MPR-3: Media storage and packaging format** + +The storage and packaging of the video and audio media stream in the VSS shall be in PS format. + +### 7.1.4 VSS ID + +All devices (servers, cameras, NVRs, etc.) and user accounts in the VSS should have a unique ID within the network. At the same time, the zone code and device type should be reflected in the ID. The unified ID is 24-digit, which is reflected in Figure 7-2 and adopts the following rules. + +![Diagram of the 24-digit digital character scheme showing five parts: 4-digit country or area code, 8-digit zone code, 2-digit reserved code, 3-digit device type code, and 7-digit serial number. The text H.626(19)_F7-2 is shown below the diagram.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +| | | | | | +|------------------------------|-------------------|-----------------------|--------------------------|-----------------------| +| 4-digit country or area code | 8-digit zone code | 2-digit reserved code | 3-digit device type code | 7-digit serial number | +|------------------------------|-------------------|-----------------------|--------------------------|-----------------------| + +H.626(19)\_F7-2 + +Diagram of the 24-digit digital character scheme showing five parts: 4-digit country or area code, 8-digit zone code, 2-digit reserved code, 3-digit device type code, and 7-digit serial number. The text H.626(19)\_F7-2 is shown below the diagram. + +**Figure 7-2 – 24-digit digital character scheme** + +The ID consists of the following five parts: + +- 1) 4-digit country or area code: Representative of the country or region in which the VSS is deployed. It is recommended to use the international postal code. +- 2) 8-digit zone code: It is recommended to use postal code or customized zone code. +- 3) 2-digit reserved code: It is reserved for industry classification or other usage. +- 4) 3-digit device type code: It is used to distinguish different devices, such as IPC, DVR, NVR, CCS, etc. +- 5) 7-digit serial number: It generally follows numerical order. + +## **7.2 Reference point Pc: CU-PU** + +Reference point Pc lies between the CU and the PU. + +It is used to deliver interaction signals directly between the CU and the PU, as well as media streams from PU to CU. + +## **7.3 Reference point Mp/Mp': MS-PU** + +Reference point Mp/Mp' lies between the MS and the PU. + +It is used by the MS to distribute and store media from the PU using file and streaming methods. + +## **7.4 Reference point Cm: CCS-MS** + +Reference point Cm lies between the CCS and the MS. + +It is used by the CCS to control the MS for media distribution, media selection and media location, media storage and media serving, and related media operations. The MDU is used for media distribution, media selection and media location, while MSU is used for media storage and media serving, and related media operations. + +## **7.5 Reference point Mc/Mc': MS-CU** + +Reference point Mc/Mc' lies between the MS and the CU. + +It is used by the MS to distribute, store and deliver media to, or from the CU, using file and streaming methods. + +## **7.6 Reference point Ps: CCS-PU** + +Reference point Ps lies between CCS and PU. + +It is used by the CCS to control PU registration, access authentication, authorization, and monitoring of the status of the PU (such as online/offline, active/inactive status), and to control PU, such as PTZ control, remote reboot, configure parameters and upgrade the software, etc. + +## **7.7 Reference point Cs: CCS-CU** + +Reference point Cs lies between the CCS and the CU. + +It is used by the CCS to control CU registration, access authentication, authorization, monitoring of the CU status (such as online/offline, active/inactive status), and receiving the PTZ control operation commands from the CU. + +## 7.8 Reference point Ds/Ds': MDU-MSU + +Reference point Ds/Ds' lies between the MDU and the MSU. + +It is used by the CCS to control media scheduling. The MSU captures media streams from the MDU and store them in the storage medium. + +# 8 Interworking with other multimedia systems + +## 8.1 Interworking with videoconferencing + +The interworking and convergence between VS and videoconferencing systems is based on the consideration that surveilled media stream is introduced into videoconferencing system through the media stream server in the service platform, CUs or PUs of the VSS. + +The following are instances of interworking between VS and videoconferencing systems: + +**Instance 1:** A surveilled video stream is introduced into the videoconferencing system through the media stream server in the service platform of the VSS. + +- A streaming server is added between the service platform of the VSS and the videoconferencing system. The streaming server stores the media resource providing for video conferencing from the VSS, and publishes the link addresses of the media resource to an electronic programme guide (EPG) server. +- A videoconferencing terminal accesses the EPG server to select and obtain the media address. +- The videoconferencing terminal initiates sending of the media stream request to the streaming server with the media address, and obtains the media stream from the streaming server. It then transfers it to the multimedia control unit (MCU) or other terminals in the video conferencing system. + +**Instance 2:** A surveilled video stream is introduced into the videoconferencing system through the CU in the VSS. + +- The CU in the VSS creates connections with the videoconferencing terminal, including signalling and media communication. +- The CU decodes the media stream and transfers it from the VSS to the videoconferencing terminal. This media stream is served as one of the input media sources for the videoconferencing terminal. +- The videoconferencing terminal broadcast this media stream within the videoconferencing system. + +**Instance 3:** A surveilled video stream is directly introduced into the videoconferencing system through the PU in the VSS. + +- The PU in the VSS creates connections with the MCU in the videoconferencing system. +- The MCU regards this PU as a virtual videoconferencing terminal and convenes it into the video conferencing. +- The MCU handles the media stream from the PU like from other videoconferencing terminals. + +## 8.2 Interworking with IPTV + +The interworking and convergence between VS and IPTV systems is based on the following considerations: + +- The VSS can provide the VS service to the IPTV end user via interworking with the IPTV system. +- The IPTV end user can access the VSS via IPTV terminal devices (e.g., set-top box), which can act as the end-user functions. +- The IPTV end user can access the VSS via IPTV EPG, which can act as the VS service entry. +- The audio, video and alarm signal information from the VSS can be inserted into the closest related IPTV content delivery network (CDN) system, and be delivered to IPTV terminal devices (e.g., set-top box). +- The IPTV end user can play audio and video and get alert signals information from the VSS, and can also control the PTZ functions of the video camera with authorization. + +The following describes an instance of interworking between VS and IPTV: + +- PUs, the IPTV system and user terminals connect to the same bearer network used for multimedia services. +- PUs capture video and audio information from the surveilled objects, transcode and encode into the media stream. +- PUs send the media stream to media servers in the IPTV system. The media servers process, store and manage the media stream data. +- User terminals connect to the PUs through the IPTV system, view the real-time video and audio information captured by the PUs, and also take remote control of the PUs. +- User terminals can also view the recording media data from PUs stored in media servers in the IPTV system. + +## Bibliography + +- [b-ITU-T H.222.0] Recommendation ITU-T H.222.0 (2018) | ISO/IEC 13818-1:2019, *Information technology-Generic coding of moving pictures and associated audio information: Systems*. +- [b-ITU-T H-Sup.1] ITU-T H-series Recommendations – Supplement 1 (1999), *Application profile – Sign language and lip-reading real-time conversation using low bit rate video communication*. +- [b-ITU-T J.200] Recommendation ITU-T J.200 (2010), *Worldwide common core – Application environment for digital interactive television services*. +- [b-ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions*. +- [b-ITU-T M.3320] Recommendation ITU-T M.3320 (1997), *Management requirements framework for the TMN X-Interface*. +- [b-ITU-T Q.1290] Recommendation ITU-T Q.1290 (1998), *Glossary of terms used in the definition of intelligent networks*. +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions*. +- [b-ITU-T Y.110] Recommendation ITU-T Y.110 (1998), *Global Information Infrastructure principles and framework architecture*. +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*. +- [b-IETF RFC 768] IETF RFC 768 (1980), *User datagram protocol*. +- [b-IETF RFC 793] IETF RFC 793 (1981), *Transmission control protocol*. +- [b-IETF RFC 3428] IETF RFC 3428 (2002), *Session Initiation Protocol (SIP) Extension for Instant Messaging*. +- [b-IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- [b-IETF RFC 4566] IETF RFC 4566 (2006), *SDP: Session Description Protocol*. [b-IETF RFC 3261] IETF RFC 3261 (2002), *SIP: Session Initiation Protocol*. +- [b-ISO/IEC 14496-3] ISO/IEC 14496-3:2009, *Information technology-Coding of audio-video objects-Part 3:Audio*. + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.626.1-201303-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/H/T-REC-H.626.1-201303-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4026e763a536f6eb88bea8653a25cc1340a9f997 --- /dev/null +++ b/marked/H/T-REC-H.626.1-201303-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c9d094fa26732bedc537cc03f26df898ab8eaffed05f5a77757a317d43f3eca +size 72620 diff --git a/marked/H/T-REC-H.626.1-201303-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/H/T-REC-H.626.1-201303-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d38e7d49f049458f78608395cc012379aecaee19 --- /dev/null +++ b/marked/H/T-REC-H.626.1-201303-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f76c606632a5d2b587fffc8865424eef6fa5fce8af57f5b6e4091cc63526e5c7 +size 39712 diff --git a/marked/H/T-REC-H.626.1-201303-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/H/T-REC-H.626.1-201303-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..353d8fe6e352fe532fe375b92a14fbdb938674b6 --- /dev/null +++ b/marked/H/T-REC-H.626.1-201303-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f06492a38bb8e83bf2b98bc6f9f5f6c0dff4c9a443c36fd848cc85090e08d29 +size 64026 diff --git a/marked/H/T-REC-H.626.1-201303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.626.1-201303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bdb0bc8339f4fe3c7d2f9b51a91efb0fa0b5118 --- /dev/null +++ b/marked/H/T-REC-H.626.1-201303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7b24aed78d8867beecff4e44493801d3c5d495c1feefb701fc5b454a6ce5e76 +size 111073 diff --git a/marked/H/T-REC-H.626.1-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.626.1-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.626.1-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.626.1-201303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.626.1-201303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3380ab46dfa62f2b8df8c3fe703b9c120d465b67 --- /dev/null +++ b/marked/H/T-REC-H.626.1-201303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08f39d929a37e55a7b3350142dbda77c49e400c3f12eb87179fb30a5e1839570 +size 31727 diff --git a/marked/H/T-REC-H.626.1-201303-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/H/T-REC-H.626.1-201303-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b24d9ed1a511b2926a9218d0b9627d8eac75c50c --- /dev/null +++ b/marked/H/T-REC-H.626.1-201303-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edb07e36758747f148423c35d9bd23319a1e21e3d8b69e05a918289138649df7 +size 111794 diff --git a/marked/H/T-REC-H.626.2-201712-I_PDF-E/raw.md b/marked/H/T-REC-H.626.2-201712-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..39ecc8aea7e25ddc0c6e2c8209c4122a0dbe600e --- /dev/null +++ b/marked/H/T-REC-H.626.2-201712-I_PDF-E/raw.md @@ -0,0 +1,734 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.626.2** + +(12/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Broadband, triple-play and advanced multimedia +services – Advanced multimedia services and applications + +# --- **Architecture for cloud storage in visual surveillance** + +Recommendation ITU-T H.626.2 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.626.2 + +# Architecture for cloud storage in visual surveillance + +## Summary + +Recommendation ITU-T H.626.2 defines a cloud storage architecture in visual surveillance. Cloud storage enables the service users to have ubiquitous, convenient and on-demand network access to a shared pool of the configurable storage resources, which can be rapidly provisioned and released with the minimal management effort or service-provider interaction. Cloud storage can realize flexible and reliable data storage for large-scale visual surveillance and its components are modularized and allocated dynamically based on the real usage. This Recommendation provides the architecture, entities, reference points and service control flow for cloud storage in visual surveillance. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.626.2 | 2017-12-14 | 16 | 11.1002/1000/13436 | + +## Keywords + +Architecture, cloud storage, entity, reference point, service control flow, visual surveillance. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 3 | +| 6 Overview of cloud storage in visual surveillance..... | 3 | +| 7 Functional architecture for cloud storage in visual surveillance ..... | 3 | +| 7.1 Architectural framework ..... | 3 | +| 7.2 Functional entities ..... | 4 | +| 7.3 Reference points ..... | 6 | +| 7.4 Service control flow ..... | 7 | + + + +## Recommendation ITU-T H.626.2 + +# Architecture for cloud storage in visual surveillance + +## 1 Scope + +This Recommendation describes architecture, functional entities, reference points and service control flow of cloud storage in visual surveillance. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.626] Recommendation ITU-T H.626 (2011), *Architectural requirements for visual surveillance*. +- [ITU-T F.743.2] Recommendation ITU-T F.743.2 (2016), *Requirements for cloud storage in visual surveillance*. +- [ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions*. +- [ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions*. +- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 application** [ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services. + +**3.1.2 cloud storage** [ITU-T F.743.2]: A data storage model for enabling service users to have ubiquitous, convenient and on-demand network access to a shared pool of configurable storage resources, which can be rapidly provisioned and released with minimal management effort or service-provider interaction. In cloud storage systems, the physical and virtual resources can be dynamically assigned and reassigned according to user demand. + +**3.1.3 customer** [ITU-T M.60]: An entity which receives services offered by a service provider based on a contractual relationship. It may include the role of a network user. + +**3.1.4 customer unit** [ITU-T H.626]: A device located at the customer part of a visual surveillance system and used to present multimedia information (such as audio, video, image, alarm signal, etc.) to the end user. + +**3.1.5 functional architecture** [ITU-T Y.2012]: A set of functional entities and the reference points between them, used to describe the structure of an NGN. These functional entities are separated by reference points, and thus, they define the distribution of functions. + +NOTE 1 – The functional entities can be used to describe a set of reference configurations. These reference configurations identify which reference points are visible at the boundaries of equipment implementation and between administrative domains. + +NOTE 2 – The definition is not only applicable to NGNs, but also to other IP packet switch based networks. + +**3.1.6 functional entity** [ITU-T Y.2012]: An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. + +**3.1.7 interface** [ITU-T Y.101]: A shared boundary between two functional units. + +NOTE – An interface is defined by various characteristics pertaining to the functions, physical interconnections, signal exchanges and other characteristics as appropriate. + +**3.1.8 premises unit** [ITU-T H.626]: A device located at the remote part of a visual surveillance system and used to capture multimedia information (such as audio, video, image, alarm signal, etc.) from a surveilled object. + +**3.1.9 reference point** [ITU-T Y.2012]: A conceptual point at the conjunction of two non-overlapping functional entities that can be used to identify the type of information passing between these functional entities. + +NOTE – A reference point may correspond to one or more physical interfaces between pieces of equipment. + +**3.1.10 service** [ITU-T Y.101]: A structure set of capabilities intended to support applications. + +**3.1.11 visual surveillance** [ITU-T H.626]: A telecommunication service focusing on video (but including audio) application technology, which is used to remotely capture multimedia (such as audio, video, image, alarm signal, etc.) and present them to the end user in a user-friendly manner, based on a managed broadband network with ensured quality, security and reliability. + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 cloud storage access unit (CSAU)**: A device located at a cloud storage system in visual surveillance. The CSAU is the key unit for implementing communication between the CSDU and the MDU, PU and the other media data related units defined in visual surveillance. The functions of the CSAU include service control function, media control function and configuration management function. + +**3.2.2 cloud storage data unit (CSDU)**: A series of devices located at a cloud storage system in visual surveillance. The CSDU is the data node in a cloud storage system that is used to store the massive multimodal data produced by the visual surveillance system. A typical visual surveillance cloud storage system consists of a number of CSDUs, which is organized in a distributed way. The CSDU can be dynamically extended according to the user's demand. The CSDU can receive the media data from the CSAU and write the data onto its local storage device. In addition, the CSDU can read and transmit the stored data to the CSAU according to the data reading requests. + +**3.2.3 cloud storage management unit (CSMU)**: A device located at the central part of a cloud storage system in visual surveillance. The CSMU is used to provide the management services of the cloud storage system and respond to the service requests of the visual surveillance system. The main functions of the CSMU include supporting storage resource management, data management, user management, service management, log management and security control. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------| +| CMU | Centre Management Unit | +| CSAU | Cloud Storage Access Unit | +| CSDU | Cloud Storage Data Unit | +| CSMU | Cloud Storage Management Unit | +| CU | Customer Unit | +| IPU | Intelligent Premises Unit | +| MDU | Media Distribution Unit | +| MSU | Media Storage Unit | +| NVR | Network Video Recorder | +| PU | Premises Unit | +| SCU | Service Control Unit | +| VS | Visual Surveillance | + +## **5 Conventions** + +None. + +# **6 Overview of cloud storage in visual surveillance** + +The large-scale deployment of visual surveillance systems has contributed to the explosive growth of surveillance video data. It induces stringent needs for the efficient storage of massive video data and fast access of information of interest to users. Cloud storage is a data storage model for enabling service users to have ubiquitous, convenient and on-demand network access to a shared pool of configurable storage resources, which can be rapidly provisioned and released with minimal management effort or service-provider interaction. In the cloud storage system, the physical and virtual resources can be dynamically assigned and reassigned according to the users' demands. + +# **7 Functional architecture for cloud storage in visual surveillance** + +## **7.1 Architectural framework** + +Figure 7-1 shows the architectural framework for cloud storage in visual surveillance. The cloud storage based visual surveillance platform consists of two parts, which are respectively the traditional visual surveillance (VS) system and the cloud storage system. The cloud storage system can also be integrated with intelligent visual surveillance, mobile visual surveillance and other visual surveillance subsystems and the architecture is similar to that defined in this clause and is not described in this Recommendation. + +![Architectural framework for cloud storage in visual surveillance diagram. The diagram is split into two main sections by a vertical dashed line. The left section, 'Cloud storage system', contains CSMU, a cluster of four CSDUs, and CSAU. The right section, 'VS system defined in ITU-T H.626', contains CMU, SCU, MDU, MSU, PU, and CU. Arrows represent Media (black), Control (red), and Management (blue dashed) flows between these components. Labels include Cms, Csd', Csd, Csm, Csa, Csc, Cc, Pcs, Ss, Mdc, Pm, Dm, Sm, Sc, Dm', Cm, Ps, Sd, Sd', Cs, Pd, Pc, Pc', Cd, Mc, Mc', and H.626.2(17)_F7-1.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Architectural framework for cloud storage in visual surveillance diagram. The diagram is split into two main sections by a vertical dashed line. The left section, 'Cloud storage system', contains CSMU, a cluster of four CSDUs, and CSAU. The right section, 'VS system defined in ITU-T H.626', contains CMU, SCU, MDU, MSU, PU, and CU. Arrows represent Media (black), Control (red), and Management (blue dashed) flows between these components. Labels include Cms, Csd', Csd, Csm, Csa, Csc, Cc, Pcs, Ss, Mdc, Pm, Dm, Sm, Sc, Dm', Cm, Ps, Sd, Sd', Cs, Pd, Pc, Pc', Cd, Mc, Mc', and H.626.2(17)\_F7-1. + +**Figure 7-1 – Architectural framework for cloud storage in visual surveillance** + +The traditional VS service is a telecommunication service focusing on video (and audio) application technology, which is used to remotely capture multimedia (such as audio, video, image and various alarm signals) and present them to end users in a friendly manner (including accessibility aspects). The traditional VS system mainly includes six functional entities, which are the centre management unit (CMU), the service control unit (SCU), the media distribution unit (MDU), the media storage unit (MSU), the premises unit (PU) and the customer unit (CU). The function description of each functional entity is defined in [ITU-T H.626]. + +A visual surveillance cloud storage can provide a shared pool of configurable storage resources and related data storage functions to the VS applications. In a cloud storage system, the storage resources can be dynamically assigned and reassigned according to the users' demands. The cloud storage part mainly includes three functional entities, which are the cloud storage management unit (CSMU), the cloud storage data unit (CSDU) and the cloud storage access unit (CSAU). + +- CSMU is used to provide the management services for the cloud storage system in the VS system. +- CSDU is the data node in a cloud storage system. A number of CSDUs are organized in a distributed way as a storage resource pool by using virtualization technology and the virtualized storage resource can be dynamically provided to the users on demand. The CSDUs are used to store the massive multimodal data produced by the VS system. +- CSAU is the key unit for implementing communication between the CSDU and the media data related units defined in the traditional VS system [ITU-T H.626]. The main functions of the CSAU include: receiving and responding to the control information of the CSMU, receiving and responding to the control information of the SCU, receiving the media data from MDU or PU, sending the media data to the MDU or other related visual surveillance entities, writing the media data into the CSDU cluster and reading the media data from the CSDU cluster. + +## 7.2 Functional entities + +#### 7.2.1 Cloud storage management unit + +The cloud storage management unit (CSMU) is used to provide the management services for the cloud storage system and respond to service requests of the VS system. The main functions of the + +CSMU include storage resource management, data management, user management, service management, log management and security control. The CSMU is used to achieve collaboration among the different storage devices and guarantee better access performance of the multimodal surveillance data. + +#### 7.2.2 Cloud storage data unit + +The cloud storage data unit (CSDU) is the data node in a cloud storage system which is used to store the massive multimodal data produced by the VS system. A typical visual surveillance cloud storage system has a number of CSDUs, which are organized in a distributed way as a storage resource pool by using virtualization technology. The CSDU can be dynamically extended according to the user's demand and the virtualized storage resource can be dynamically provided to the users on demand. The CSDU can receive media data from the CSAU and write the data onto its local storage device. In addition, the CSDU can read and transmit the stored data to the CSAU according to the data reading requests. + +#### 7.2.3 Cloud storage access unit + +The cloud storage access unit (CSAU) is the key unit for implementing communication between the CSDU and the media data related units defined in the VS system [ITU-T H.626]. As shown in Figure 7-2, the functions of the CSAU are divided into three categories, which are the service control function, the media control function and the configuration management function. + +![Diagram of Function components of CSAU showing connections to other entities and internal function blocks.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +The diagram illustrates the functional architecture of the Cloud Storage Access Unit (CSAU). On the left, a box labeled "Other entities" contains six sub-components: CSMU, CSDU, SCU, MDU, MSU, and PU. Two double-headed arrows connect this box to the CSAU's internal components. The top arrow is labeled "Service control" and connects to a box labeled "Service control functions". The bottom arrow is labeled "Media control" and connects to a box labeled "Media control functions". The CSAU itself is a large box titled "Function components of CSAU" which contains three sub-boxes: "Service control functions", "Media control functions", and "Configuration management functions". A small label "H.626.2(17)\_F7-2" is located at the bottom right of the diagram. + +Diagram of Function components of CSAU showing connections to other entities and internal function blocks. + +Figure 7-2 – Function components of CSAU + +##### Service control function + +- initiate, maintain and release the connection with the SCU; +- process the service requests from the CSMU, forward them to the SCU and respond to the CSMU. + +##### Media control function + +- receive media data from the MDU, the PU, the MSU and/or other data source entities of the VS system; +- transmit or forward media data into the CSDU cluster; +- receive media data distributed in the CSDU cluster; +- transmit or forward media data to the MDU, the CU and/or other related entities of the VS system. + +##### **Configuration management function** + +- manage the overall configuration in the CSAU, including the service control, data transmission and other media storage control. + +## **7.3 Reference points** + +#### **7.3.1 Reference point Pcs: PU-CSAU** + +The reference point Pcs is located between the PU and the CSAU. It is used to deliver the media data directly from the PU to the CSAU according to the media storage requests. + +#### **7.3.2 Reference point Mdc: MDU-CSAU** + +The reference point Mdc is located between the MDU and the CSAU. It is used for the media data transmission between the MDU and the CSAU according to the media reading and writing requests. + +#### **7.3.3 Reference point Ss: CSAU-SCU** + +The reference point Ss is located between the CSAU and the SCU. It is used to control the CSAU registration, access authentication, authorization and accounting by the SCU and is used for the control signal transmission between the CSAU and the SCU. + +#### **7.3.4 Reference point Cms: CMU-CSMU** + +The reference point Cms is located between the CMU and the CSMU. It is used for the management signal transmission between the CMU and the CSMU. + +#### **7.3.5 Reference point Csm: CSMU-CSAU** + +The reference point Csm is located between the CSMU and the CSAU. It is used by the CSMU to manage the service control function, the media control function and the configuration management function of the CSAU. + +#### **7.3.6 Reference point Csd: CSMU-CSDU** + +The reference point Csd is located between the CSMU and the CSDU. It is used for the control signal transmission between the CSMU and the CSDU. + +#### **7.3.7 Reference point Csd': CSMU-CSDU** + +The reference point Csd' is located between the CSMU and the CSDU. It is used to support the storage space management. The main functions are as follows. + +- increase or decrease the storage space flexibly according to the users' demands; +- support data management in the CSDU, including data addition, data deletion, data browsing and data retrieval, etc. + +#### **7.3.8 Reference point Csc: CSDU-CSAU** + +The reference point Csc is located between the CSDU and the CSAU. It is used for the media access control signal transmission between the CSAU and the CSDU. + +#### **7.3.9 Reference point Cc: CSDU-CSAU** + +The reference point Cc is located between the CSAU and the CSDU. It is used for the media data transmission between the CSAU and the CSDU. + +#### **7.3.10 Reference point Csa: CSMU-CSAU** + +The reference point Csa is located between the CSAU and the CSMU. It is used for the access control signal transmission between the CSMU and the CSAU. + +## 7.4 Service control flow + +#### 7.4.1 Real-time media storage + +When a user wants to store the real-time media obtained from the PU into the cloud storage system, the CU initiates a storage request and sends it to the SCU to start the media storage. + +![Sequence diagram showing high-level procedural flows for real-time media storage between CU, SCU, CMU, MDU, PU, CSMU, CSAU, and CSDU.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +sequenceDiagram + participant CU + participant SCU + participant CMU + participant MDU + participant PU + participant CSMU + participant CSAU + participant CSDU + + CU->>SCU: Set storage plan + SCU->>CMU: Set storage plan + CMU->>CSMU: Storage plan + CSMU->>CSAU: Request + CSAU-->>CSMU: Response + CSMU->>CMU: Return CSAU information + CMU-->>SCU: Response + SCU-->>CU: Response + Note right of MDU: Start storage + MDU->>CSAU: Request media address + SCU->>MDU: Request media address + MDU-->>SCU: Return media address + MDU->>CSAU: Media address + Note right of MDU: Start storage + MDU->>PU: Request media + PU-->>MDU: Media stream + MDU->>CSAU: Media stream + CSDU->>MDU: Media stream + Note right of MDU: Stop media + MDU->>PU: Stop media + PU-->>MDU: Response + MDU->>CSAU: Disconnect + MDU-->>SCU: Response +``` + +The sequence diagram illustrates the interaction between eight entities: CU, SCU, CMU, MDU, PU, CSMU, CSAU, and CSDU. The process begins with the CU sending a 'Set storage plan' message to the SCU. The SCU then forwards this to the CMU, which sends a 'Storage plan' to the CSMU. The CSMU sends a 'Request' to the CSAU, which returns a 'Response'. The CSMU then sends 'Return CSAU information' to the CMU, which sends a 'Response' to the SCU, which in turn sends a 'Response' to the CU. Next, a 'Start storage' message is sent from the MDU to the CSAU. The MDU sends a 'Request media address' to the CSAU, and the SCU sends a 'Request media address' to the MDU. The MDU returns the 'Media address' to the SCU. The MDU then sends the 'Media address' to the CSAU. Another 'Start storage' message is sent from the MDU to the PU. The MDU sends a 'Request media' to the PU, which returns a 'Media stream'. The MDU then sends the 'Media stream' to the CSAU, which in turn sends it to the CSDU. Finally, a 'Stop media' message is sent from the MDU to the PU, which returns a 'Response'. The MDU sends a 'Disconnect' message to the CSAU, and a 'Response' is sent from the MDU to the SCU. + +Sequence diagram showing high-level procedural flows for real-time media storage between CU, SCU, CMU, MDU, PU, CSMU, CSAU, and CSDU. + +Figure 7-3 – High-level procedural flows for real-time media storage + +Figure 7-3 shows the procedural flows of real-time media storage in a cloud storage system: + +- (1) The CU initiates a storage plan request and sends this request to the SCU. +- (2) The SCU forwards this storage plan request to the CMU. +- (3) The CMU authenticates the storage access permission and then sends this storage plan request to the CSMU. +- (4) The CSMU authenticates the storage access permission and then sends this storage plan request to the CSAU. +- (5) The CSAU returns a response to the CSMU when it is ready for this storage plan. +- (6) The CSMU returns the CSAU information to the CMU. +- (7) The CMU sends a response including the CSAU information to the SCU. +- (8) The SCU forwards this response to the CU. + +- (9) When the CU receives the CSAU information, it sends the real-time media storage request to the CSAU. +- (10) When the CSAU receives the storage request, it sends a request to the SCU for the media address. +- (11) The SCU forwards this request to the MDU. +- (12) The MDU returns the media address to the SCU. +- (13) The SCU transfers the media address to the CSAU. +- (14) After receiving the real-time media address, the CSAU requests the MDU to start transmitting the media stream. +- (15) The MDU sends a request to the PU for initiating a media stream. +- (16) The PU creates a media channel with the MDU and sends the media stream to the MDU. +- (17) The MDU transfers the media stream to the CSAU. +- (18) The CSAU transfers this media stream to the CSDU to store it in the cloud data nodes. +- (19) When the storage plan is completed, the CU sends a stop-media request to the CSAU. +- (20) The CSAU transfers this stop request to the MDU. +- (21) The MDU returns a response to the CSAU. +- (22) The CSAU requests the SCU to disconnect. +- (23) The SCU returns a response to end this real-time media storage. + +#### **7.4.2 Video file storage** + +A network video recorder (NVR) is usually used as a typical MSU for continuously recording the surveillance video from network cameras. When a user wants to upload a video file from the NVR to the cloud storage system, the CU initiates a storage request and sends it to the SCU to start the media storage. + +![Sequence diagram showing high-level procedural flows for video file uploading from NVR. Lifelines: CU, SCU, CMU, MDU, NRV, CSMU, CSAU, CSDU. The process involves setting an uploading plan, authenticating permissions, sending the plan to the CSAU, starting the upload, requesting the video file address, and finally disconnecting.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +sequenceDiagram + participant CU + participant SCU + participant CMU + participant MDU + participant NRV + participant CSMU + participant CSAU + participant CSDU + + CU->>SCU: Set uploading plan + SCU->>CMU: Set uploading plan + CMU->>NRV: Video file uploading plan + NRV->>CSMU: Request + CSMU->>CSAU: Request + CSAU-->>CSMU: Response + CSMU->>CMU: Return CSAU information + CMU-->>SCU: Response + SCU-->>CU: Response + CMU->>CSAU: Start video file uploading + CSAU->>MDU: Request video file address + MDU->>SCU: Request video file address + SCU-->>MDU: Return video file address + MDU->>CSAU: Video file address + CSAU->>NRV: Start video file uploading + NRV->>MDU: Uploading request + MDU->>NRV: Video file + NRV->>CSAU: Video file + CSAU->>CSDU: Video file + CMU->>CSAU: Stop video file uploading request + CSAU->>MDU: Stop video file uploading request + MDU->>NRV: Response + NRV->>CSAU: Disconnect + CSAU-->>MDU: Response + MDU-->>SCU: Response + +``` + +Sequence diagram showing high-level procedural flows for video file uploading from NVR. Lifelines: CU, SCU, CMU, MDU, NRV, CSMU, CSAU, CSDU. The process involves setting an uploading plan, authenticating permissions, sending the plan to the CSAU, starting the upload, requesting the video file address, and finally disconnecting. + +H.826.2(17)\_F7-4 + +**Figure 7-4 – High-level procedural flows for video file uploading from NVR** + +Figure 7-4 shows the procedural flows of video file uploading from the NVR to the cloud storage system: + +- (1) The CU initiates a video file uploading plan request and sends this request to the SCU. +- (2) The SCU forwards this uploading plan request to the CMU. +- (3) The CMU authenticates the uploading access permission and then sends this uploading plan request to the CSMU. +- (4) The CSMU authenticates the uploading access permission and then sends this uploading plan request to the CSAU. +- (5) The CSAU returns a response to the CSMU when it is ready for this video file uploading plan. +- (6) The CSMU returns the CSAU information to the CMU. +- (7) The CMU sends a response to the SCU. +- (8) The SCU forwards this response to the CU. +- (9) When the CU receives the CSAU information, it sends the video file uploading request to the CSAU. +- (10) When the CSAU receives the uploading request, it sends a request to the SCU for the data source address. +- (11) The SCU forwards the request to the MDU. + +- (12) The MDU returns the file address to the SCU. +- (13) The SCU transfers the file address to the CSAU. +- (14) After receiving the file address, the CSAU requests the MDU to start video file uploading from the NVR. +- (15) The MDU sends a request to the NVR for obtaining the video files. +- (16) The NVR creates a video transmission channel with the MDU and sends the video files to the MDU. +- (17) Then MDU transfers the video files to the CSAU. +- (18) The CSAU transfers the video files to the CSDU to store them in the cloud data nodes. +- (19) When the storage plan is completed, the CU sends a stop request to the CSAU. +- (20) The CSAU transfers this stop-media request to the MDU. +- (21) Then MDU returns a response to the CSAU. +- (22) The CSAU requests the SCU to disconnect. +- (23) The SCU returns a response to end this video file uploading. + +#### **7.4.3 Image storage** + +The network cameras continuously capture images. When a user wants to store these images directly into the cloud storage system, the CU initiates a request to the SCU to start the image storage. + +![Sequence diagram showing high-level procedural flows for image uploading from surveillance camera. Lifelines: CU, SCU, CMU, MDU, PU, CSMU, CSAU, CSDU. The process involves setting a storage plan, authenticating permissions, starting image uploading, requesting the image, receiving it, and then stopping media and disconnecting.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant CU + participant SCU + participant CMU + participant MDU + participant PU + participant CSMU + participant CSAU + participant CSDU + + CU->>SCU: Set image storage plan + SCU->>CMU: Set image storage plan + CMU->>CSMU: Storage plan + CSMU->>CSAU: Request + CSAU->>CSMU: Response + CSMU->>CMU: Return CSAU information + CMU->>SCU: Response + SCU->>CU: Response + CMU->>CSAU: Start image uploading + CSAU->>MDU: Request image address + MDU->>SCU: Request image address + SCU->>MDU: Return image address + MDU->>CSAU: Image address + CSAU->>PU: Start image uploading + PU->>MDU: Request image + MDU->>PU: Image + PU->>CSAU: Image + CSAU->>CSDU: Image + CMU->>CSAU: Stop image uploading + CSAU->>MDU: Stop media + MDU->>CSAU: Response + MDU->>SCU: Disconnect + SCU->>MDU: Response + +``` + +Sequence diagram showing high-level procedural flows for image uploading from surveillance camera. Lifelines: CU, SCU, CMU, MDU, PU, CSMU, CSAU, CSDU. The process involves setting a storage plan, authenticating permissions, starting image uploading, requesting the image, receiving it, and then stopping media and disconnecting. + +**Figure 7-5 – High-level procedural flows for image uploading from surveillance camera** + +Figure 7-5 shows the procedural flows of the image uploading from the PU to the cloud storage system: + +- (1) The CU initiates an image storage request and sends this request to the SCU. +- (2) The SCU forwards this image uploading plan request to the CMU. +- (3) The CMU authenticates the uploading access permission and then sends this uploading plan request to the CSMU. +- (4) The CSMU authenticates the uploading access permission and then sends this uploading plan request to the CSAU. +- (5) The CSAU returns a response to the CSMU when it is ready for this uploading plan. +- (6) The CSMU returns the CSAU information to the CMU. +- (7) The CMU sends a response to the SCU. +- (8) The SCU forwards this response to the CU. +- (9) When the CU receives the CSAU information, it sends the image storage request to the CSAU. +- (10) When the CSAU receives the request, it sends a request to the SCU for the data source address. + +- (11) The SCU forwards the request to the MDU. +- (12) The MDU returns the address to the SCU. +- (13) The SCU transfers the data source address to the CSAU. +- (14) After receiving the data source address, the CSAU requests the MDU to start the image uploading from the PU. +- (15) The MDU sends a request to the PU for obtaining the captured images. +- (16) The PU creates an image transmission channel with the MDU and sends the captured images to the MDU. +- (17) The MDU transfers the images to the CSAU. +- (18) The CSAU transfers the images to the CSDU to store the received images in the cloud data nodes. +- (19) When the storage plan is completed, the CU sends a stop request to the CSAU. +- (20) The CSAU transfers this stop request to the MDU. +- (21) The MDU returns a response to the CSAU. +- (22) The CSAU requests the SCU to disconnect. +- (23) The SCU returns a response to end the image uploading from the PU. + +#### **7.4.4 Video metadata or image metadata storage** + +The intelligent visual surveillance system can provide various intelligent services by using video or image analysis technologies. One solution is to implement some intelligent visual analysis algorithms in the PU that is defined as the intelligent premises unit (IPU). When a user wants to store video metadata or image metadata extracted from the original video or image data in the cloud storage system, the CU initiates a request to the SCU to start this procedure. + +![Sequence diagram showing high-level procedural flows for video metadata or image metadata storage. Lifelines: CU, SCU, CMU, MDU, IPU, CSMU, CSAU, CSDU. The process involves setting a storage plan, authenticating, starting storage, requesting metadata, and finally disconnecting.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +sequenceDiagram + participant CU + participant SCU + participant CMU + participant MDU + participant IPU + participant CSMU + participant CSAU + participant CSDU + + CU->>SCU: Set storage plan + SCU->>CMU: Set storage plan + CMU->>CSMU: Storage plan + CSMU->>CSAU: Request + CSAU-->>CSMU: Response + CSMU->>CMU: Return CSAU information + CMU-->>SCU: Response + SCU-->>CU: Response + Note right of CU: Start storage + CSAU->>MDU: Request metadata address + MDU->>SCU: Request metadata address + SCU-->>MDU: Return metadata address + MDU->>CSAU: Metadata address + Note right of MDU: Start storage + MDU->>IPU: Request metadata + IPU-->>MDU: Metadata + Note right of IPU: Metadata + IPU->>CSAU: Metadata + CSAU->>CSDU: Metadata + Note right of MDU: Stop metadata + CSAU->>IPU: Stop metadata + IPU-->>MDU: Response + MDU->>SCU: Disconnect + SCU-->>MDU: Response + +``` + +H.626.2(17)\_F7-8 + +Sequence diagram showing high-level procedural flows for video metadata or image metadata storage. Lifelines: CU, SCU, CMU, MDU, IPU, CSMU, CSAU, CSDU. The process involves setting a storage plan, authenticating, starting storage, requesting metadata, and finally disconnecting. + +**Figure 7-6 – High-level procedural flows for video metadata or image metadata storage** + +Figure 7-6 shows the procedural flows of the video metadata or image metadata storage in cloud storage system: + +- (1) The CU initiates a storage plan request and sends this request to the SCU. +- (2) The SCU forwards this storage plan request to the CMU. +- (3) The CMU authenticates the storage access permission and then sends this storage plan request to the CSMU. +- (4) The CSMU authenticates the storage access permission and then sends this storage plan request to the CSAU. +- (5) The CSAU returns a response to the CSMU when it is ready for this storage plan. +- (6) The CSMU returns the CSAU information to the CMU. +- (7) The CMU sends a response to the SCU. +- (8) The SCU forwards this response to the CU. +- (9) When the CU receives the CSAU information, it sends the video metadata or image metadata storage request to the CSAU. +- (10) When the CSAU receives the storage request, it sends a request to the SCU for the metadata address. +- (11) The SCU forwards the request to the MDU. + +- (12) The MDU returns the metadata address to the SCU. +- (13) The SCU transfers the metadata address to the CSAU. +- (14) After receiving the metadata address, the CSAU requests the MDU to start transmitting the metadata. +- (15) The MDU sends a request to the IPU for the video metadata or image metadata. +- (16) The IPU creates a media channel with the MDU and sends the metadata to the MDU. +- (17) The MDU transfers the metadata to the CSAU. +- (18) The CSAU transfers the metadata to the CSDU to store it in the cloud data nodes. +- (19) When the storage plan is completed, the CU sends a stop request to the CSAU. +- (20) The CSAU transfers this stop request to the MDU. +- (21) The MDU returns a response to the CSAU. +- (22) The CSAU requests the SCU to disconnect. +- (23) The SCU returns a response to end this metadata storage. + +#### 7.4.5 Media acquisition from the cloud storage system + +When a user wants to view the media stored in a cloud storage system, the CU initiates a request to the SCU in order to acquire the media. + +![Sequence diagram showing high-level procedural flows for media acquisition between CU, SCU, CMU, CSMU, CSAU, and CSDU.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant CU + participant SCU + participant CMU + participant CSMU + participant CSAU + participant CSDU + + CU->>SCU: Set media acquisition plan + SCU->>CMU: Set media acquisition plan + CMU->>CSMU: Media request + CSMU->>CSAU: Request + CSAU->>CSMU: Response + CSMU->>CMU: Return CSAU information + CMU->>SCU: Response + SCU->>CU: Response + CU->>CSAU: Start media acquisition + CSAU->>CSDU: Media acquisition + CSDU->>CSAU: Media + CSAU->>CU: Media + CU->>CSAU: Stop media request + CSAU->>CSDU: Stop media + CSDU->>CSAU: Response + CSAU->>SCU: Disconnect + SCU->>CMU: Response + +``` + +H.626.2(17)\_F7-7 + +Sequence diagram showing high-level procedural flows for media acquisition between CU, SCU, CMU, CSMU, CSAU, and CSDU. + +**Figure 7-7 – High-level procedural flows for media acquisition** + +Figure 7-7 shows the procedural flows of the media acquisition from the cloud storage system to the CU: + +- (1) The CU initiates a media acquisition request and sends this request to the SCU. +- (2) The SCU forwards this acquisition request to the CMU. + +- (3) The CMU authenticates the acquisition access permission and then sends this request to the CSMU. +- (4) The CSMU authenticates the acquisition access permission and then sends this request to the CSAU. +- (5) The CSAU returns a response to the CSMU when it is ready for this media acquisition request. +- (6) The CSMU returns the CSAU information to the CMU. +- (7) The CMU sends a response to the SCU. +- (8) The SCU forwards this response to the CU. +- (9) When the CU receives the response, it sends a media acquisition request to the CSAU. +- (10) The CSAU transfers this request to the CSDU. +- (11) After receiving this request, the CSDU creates a media channel with the CSAU to transmit the required media data. +- (12) The CSAU transfers the media data to the CU. +- (13) When the CU stops the media acquisition, it sends a stop request to the CSAU. +- (14) The CSAU transfers this request to the CSDU. +- (15) The CSDU returns a response to the CSAU. +- (16) The CSAU requests the SCU to disconnect. +- (17) The SCU returns a response to end this media acquisition operation. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f5c0bd9c1b83ee9a7cb8f76af979c7568bb0316 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0d50bb1b9760a5800a85d98306d1cf9c32854cce8b1c9b974543517ea807b7c +size 35241 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..757b2c3597fd3e7f9c86229586c92bd168ba35d2 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:224f4ce38c4e478b3a72f41d9a5857975a2e1fad57a165ff3097fb0b7c920723 +size 34659 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cacb86c59c5a5826e54fb961ae425cd86be2dfb0 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8484ab27fd208c7209d0b4ea3c3e4fde0d50b832df76361b425ad798de67914e +size 36641 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2905d3fd9bca5993a6d36b1d539053378cddae67 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df83d1df4f3390c1c33f3bf0cf735ccf918be6b90eed3ebfcccbb8abf9e149b9 +size 33983 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5504aef68fe674f51be8098feeb787c7f51e9eeb --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b49af18a57cce03a830371aac35525811ff402f926ab6aa6fd352b320709dc7e +size 93968 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d5aa4712628581a2cbc9e715a48f81f9d03d2fa --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c4fb68f6f799f289a4b5489b01cfff532cfdc34cf566f0058131027b6da8ddb +size 78040 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a289af3b0b8237123268b85f1af3cc0fdf7eaa6 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ed3f5811a543e07dbd6431ae602f6e57dc3c50c31e0c08ac32d2dd3d8651d46 +size 52469 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c494ffc64cf2f64f25de1fa7d6a5d3340e66ce1 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6071c223ce3184a90fa42ea4658ee979c54089da01581e6d07d66fc4b90e7b8b +size 44015 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b5c90d54a2d24d1d6d2be208669ea40bef9365b --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e11e34fb839f679547d6cb186438bfb0f9c6244af8e5911657ab5909bc85030 +size 53306 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27f3c444c7aea24da8ef7828406a378738c91731 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bf0c7dc043796ff8ff0f48b59389d947dee9e064a7a82bf06e15cb60a6dddee +size 23553 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..614fa09343e6c4a741f085e6bf6d73544a368aa4 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f8cf944425d60b181ff3616fd61c303724b644651ad3183b8dde1ddc318631c +size 75910 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/96b0240f56d14453b5da05ec30fd5c6e_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/96b0240f56d14453b5da05ec30fd5c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..591e8a1fdaf3980074d5d3b159072013db3ebc93 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/96b0240f56d14453b5da05ec30fd5c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54474acaabb86e88472f40a30ead46a1859ffcf71d966fa582170102ee146006 +size 56996 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2efce8957ea1f1abc144541c459e1bfd6a35d26d --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c5a78f302d63dbeb2b7557ba596edcd1d1f5241c11f467c6a1ffcac454c30dc +size 30027 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7134903046e2368bb67bceef12cf34e458e9ed8 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de24bb3b862c33cb7edab8e555e0dee7304b9c72e74e69aae14ab6382c1d267d +size 54454 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7a50fd833d39810e4a2b6391309825dfd7e0003 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c54f282c70dbe6b97d49b2564c11993f81fff4c75dbdeb0cb20b565b74ae9ca5 +size 25013 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaccafbc3721fa1487bb89f92b8ccddb4d188cf2 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:610d7d3b77820ea947a31470f83d861ff8d49ee27a148b576749f9f9bd11e395 +size 38880 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8761d0acb0fb2e505bf8ca2d774964b46e6d2e5f --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:925383da1ab611865b9bd7a264783e924b3d0cd4dcfad7b91b25052f90b54474 +size 77323 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83dbff19cd596785cacb36d34415fe92253d5f97 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:065cf3c74e5b8fee6965bf79715d7f9e99aa065a75ce0a57efc42b629fc6f298 +size 26839 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93bfbbe7fc3ba5d2f984f7f8ca8d74b91a4a681c --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39dc15eb2119d8668fe845649182369806a843cafeaa18af0d0034b17c5879bc +size 41867 diff --git a/marked/H/T-REC-H.626.4-201808-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/H/T-REC-H.626.4-201808-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98af885db2ccf8788be79c667e20f6a74c4c1f92 --- /dev/null +++ b/marked/H/T-REC-H.626.4-201808-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ad8fb4a080bcf53b6051622d243317e1b175f0d9e77733fe8d249b9b06dfd13 +size 19269 diff --git a/marked/H/T-REC-H.626.5-202203-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/H/T-REC-H.626.5-202203-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17666c96b51af6d9164b7dd2e6e4036bd702273f --- /dev/null +++ b/marked/H/T-REC-H.626.5-202203-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:118ec6c669ee7de37887631527e33d405452b04cd59c820142d984349671bbbe +size 48382 diff --git a/marked/H/T-REC-H.626.5-202203-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.626.5-202203-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1 --- /dev/null +++ b/marked/H/T-REC-H.626.5-202203-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c395c4bbde83b1e232652a43f51538278c116f51f710c37e20a073f7333726c8 +size 6134 diff --git a/marked/H/T-REC-H.626.5-202203-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/H/T-REC-H.626.5-202203-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec24115a3190a38cb7836b29cddfefe073c0092b --- /dev/null +++ b/marked/H/T-REC-H.626.5-202203-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d494dc4250b5792e9fa43bd8d526c8b4e45cc2887842c6a660c963aba57730f +size 45183 diff --git a/marked/H/T-REC-H.626.5-202203-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/H/T-REC-H.626.5-202203-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6eaac4cf93d7333c1f1a23f9300af08c05043f8 --- /dev/null +++ b/marked/H/T-REC-H.626.5-202203-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e864a39fe7d2068955be4ce7f8beb53d6e6f8f47188120ef39eed291a863b0c3 +size 70630 diff --git a/marked/H/T-REC-H.626.5-202203-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/H/T-REC-H.626.5-202203-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee64015e83232276005766cc365ebb28a6478ff7 --- /dev/null +++ b/marked/H/T-REC-H.626.5-202203-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abc55374a19471b5f28f840eafdf18f7b109d899970e9aee15b4f2bac546d43e +size 23060 diff --git a/marked/H/T-REC-H.626.5-202203-I_PDF-E/raw.md b/marked/H/T-REC-H.626.5-202203-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..85e7fcd98588813abfcbdfe0024b0d8eb9d027f1 --- /dev/null +++ b/marked/H/T-REC-H.626.5-202203-I_PDF-E/raw.md @@ -0,0 +1,644 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.626.5** + +(03/2022) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Broadband, triple-play and advanced multimedia +services – Advanced multimedia services and applications + +# --- **Architecture for intelligent video surveillance systems** + +Recommendation ITU-T H.626.5 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Content delivery and ubiquitous sensor network applications | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.626.5 + +# Architecture for intelligent video surveillance systems + +## Summary + +Recommendation ITU-T H.626.5 defines an architecture for intelligent video surveillance systems, including the functional requirements, functional architecture and reference points. The intelligent video surveillance system provides intelligent analysis capabilities and services for users based on the images, video slices or video streams from surveillance cameras. Meanwhile, the system also aggregates and stores the video and image information from the intelligent analysis, the surveillance devices, or manual annotation. Based on this aggregation and storage, the system provides application services and sharing services for users through the network, such as query and retrieval about the video and image information, subscription and notification, etc. This Recommendation is based on Recommendation ITU-T F.743.1, *"Requirements for intelligent visual surveillance"*. + +This edition updates the title and functional architecture, deletes the service-control flow and signalling, and revises the references points. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------|------------|-------------|------------------------------------------------------------------------------------------------| +| 1.0 | ITU-T H.626.5 | 2019-05-14 | 16 | 11.1002/1000/13905 | +| 2.0 | ITU-T H.626.5 (V2) | 2022-03-16 | 16 | 11.1002/1000/14951 | + +## Keywords + +Architecture, intelligent, video surveillance systems. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2022 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 4 | +| 6 Functional architecture ..... | 5 | +| 6.1 Intelligent premises unit ..... | 5 | +| 6.2 Intelligent customer unit..... | 6 | +| 6.3 Intelligent video management ..... | 7 | +| 6.4 Intelligent video unit..... | 7 | +| 6.5 Data storage and service..... | 8 | +| 6.6 Intelligent application service..... | 9 | +| 7 Reference points ..... | 9 | +| 7.1 Reference point Ps: IPU – CCS..... | 9 | +| 7.2 Reference point Mp/Mp': IPU – MS ..... | 9 | +| 7.3 Reference point Pc: IPU – ICU ..... | 9 | +| 7.4 Reference point Cs: ICU – CCS..... | 10 | +| 7.5 Reference point Mc/Mc': ICU – MS ..... | 10 | +| 7.6 Reference point Su: IVU – CCS..... | 10 | +| 7.7 Reference point Du: IVU – MS..... | 10 | +| 7.8 Reference point Mu/Mu': IVU – IVM..... | 10 | +| 7.9 Reference point Ma/Ma': IVM – IAS..... | 10 | +| 7.10 Reference point Ad/Ad': DSS – IAS ..... | 11 | +| 7.11 Reference point Id/Id': DSS – IVM..... | 11 | +| 7.12 Reference point Pd/Pd': DSS – IPU ..... | 11 | +| 7.13 Reference point Ac: IAS – CCS..... | 11 | +| Bibliography..... | 12 | + + + +# Recommendation ITU-T H.626.5 + +## Architecture for intelligent video surveillance systems + +## 1 Scope + +This Recommendation specifies architecture for intelligent video surveillance systems. + +The scope of this Recommendation includes: + +- Functional architecture +- Reference points + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T F.743.1] Recommendation ITU-T F.743.1 (2015), *Requirements for intelligent visual surveillance*. +- [ITU-T H.626] Recommendation ITU-T H.626 (V2) (2019), *Architectural requirements for a video surveillance system*. +- [ITU-T H.627] Recommendation ITU-T H.627 (V2) (2020), *Signalling and protocols for a video surveillance system*. +- [IETF RFC 3261] IETF RFC 3261 (2002), *SIP: Session Initiation Protocol*. +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- [IETF RFC 7230] IETF RFC 7230 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 application** [b-ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services. + +**3.1.2 central control server** [b-ITU-T H.626.3]: A device located at the central part of the visual surveillance system. It is used for centralized system management, service operation management and access control. + +NOTE – The centre control server consists of centre management unit and service-control unit. + +**3.1.3 customer unit** [ITU-T H.626]: A device located at the customer part of a video surveillance system and used to present multimedia information (such as audio, video, image, alarm signal, etc.) to the end user. + +**3.1.4 functional architecture** [b-ITU-T Y.2012]: A set of functional entities and the reference points between them used to describe the structure of an NGN. These functional entities are separated by reference points, and thus, they define the distribution of functions. + +**3.1.5 functional entity** [b-ITU-T Y.2012]: An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. + +**3.1.6 media server** [ITU-T H.626]: A device located at the centre part of a video surveillance system. It is used to forward real-time media stream as well as store, retrieve and replay historical media stream. The media server receives the media stream from premises unit or other media server and forwards the media stream to other customer unit or media server. It consists of media distribution unit and media storage unit. + +**3.1.7 premises unit** [ITU-T H.626]: A device located at the remote part of a video surveillance system and used to capture multimedia information (such as audio, video, image, alarm signal, etc.) from a surveilled object. + +**3.1.8 reference point** [b-ITU-T Y.2012]: A conceptual point at the conjunction of two non-overlapping functional entities that can be used to identify the type of information passing between these functional entities. + +**3.1.9 service** [b-ITU-T Y.101]: A structured set of capabilities intended to support applications. + +**3.1.10 service platform** [ITU-T H.626]: A series of devices and subsystems located at the centre part of a video surveillance system. It is used to integrate all of the capabilities and provide video surveillance services to customers. The main functions include service-control function, media switching, distribution, storage, and control and management. + +**3.1.11 surveilled object** [ITU-T H.626]: The target (such as site, human, and related environment) on which surveillance is performed. + +**3.1.12 video surveillance system** [ITU-T H.626]: A telecommunication service focusing on video (but including audio and image) application technology, which is used to remotely capture multimedia (such as audio, video, image, alarm signal, etc.) and present them to the end user in a user friendly manner, based on managed broadband network with ensured quality, security and reliability. + +### **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 centre management unit (CMU)**: The centre management unit (CMU) is located at the centre of the video surveillance (VS) system. Its main functions include centralized system management, service operation management, etc. + +**3.2.2 client intelligent video (CIV)**: An intelligent identification module in the customer unit (CU). It identifies required information from input video and outputs the result and retrieves the recorded video data with specified information. + +**3.2.3 data storage and service (DSS)**: The storage and sharing centre for video and image information within the intelligent video surveillance system. The DSS accepts registration, keepalive reports from the intelligent premises unit (IPU), intelligent video management (IVM) or intelligent application service (IAS) and obtains video and image information from them. It can also provide information network sharing services such as information querying, subscription, guard and alarm, etc. + +**3.2.4 intelligent application service (IAS)**: The intelligent application service (IAS) is located at the application service core of the intelligent video surveillance system. Its main functions include providing application services about the video and image information, such as information query + +and retrieval, subscription and notification, manual annotation, etc.; providing external operations such as the creation and start-up of intelligent analysis tasks based on intelligent video management (IVM); obtaining the list of devices from the central control server (CCS) or data storage and service (DSS) and sharing them with the IVM so that it can schedule intelligent video units (IVUs) for video stream analysis, etc. + +**3.2.5 intelligent customer unit (ICU):** The client subsystem within the intelligent video surveillance system. The client intelligent video (CIV) is added to the customer unit (CU) in order to achieve comprehensive intelligent video analysis. + +**3.2.6 intelligent premises unit (IPU):** The premises subsystem within the intelligent video surveillance system. The premises intelligent video (PIV) module is added to the premises unit (PU) for intelligent video analysis. + +**3.2.7 intelligent video management (IVM):** The intelligent video management (IVM) unit supports strategies configuration of intelligent applications by users and video sources schedules dynamically. The IVM accepts registration, deletion, capability reports from intelligent video units (IVUs) and schedules the IVUs dynamically. It can also store, manage, and schedule those capabilities dynamically. + +**3.2.8 intelligent video unit (IVU):** The intelligent video unit (IVU) identifies specific objects automatically, and outputs recognition results to an intelligent video management (IVM) system. The recognition information includes triggered events and acquired data. One or more intelligent analysis algorithms can be loaded or unloaded on an intelligent video unit (IVU) according to different requirements. + +**3.2.9 media distribution unit (MDU):** The media distribution unit (MDU) is used to transport media from the premises unit (PU) to the customer unit (CU). Its main functions include media receiving, media processing, media routing, media transmission, media forwarding and media replication. + +**3.2.10 media storage unit (MSU):** The media storage unit (MSU) is used to retrieve and store media and provide media serving capability. Its main functions include media storage, media serving, media indexing and media downloading. + +**3.2.11 premises intelligent video (PIV):** An intelligent identification module in the premises unit (PU). It identifies required information from input video and outputs the result. + +**3.2.12 service-control unit (SCU):** The service-control unit (SCU) is located at the centre of the video surveillance (VS) system. It is a distributed network equipment, fulfilling the access functions of the premises unit (PU) and the customer unit (CU). Its main functions include access registration, access authentication, identification, authorization, call control, location, presence and target media serving function selection. + +**3.2.13 video and image information:** Video clips, images, related files and content description information. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-----------------------------------| +| API | Application Programming Interface | +| C/S | Client/Server | +| CCS | Central Control Server | +| CIV | Client Intelligent Video | +| CMU | Centre Management Unit | + +| | | +|------|--------------------------------------| +| CPU | Central Processing Unit | +| CRUD | Create/Read/Update/Delete | +| CU | Customer Unit | +| DSS | Data Storage and Service | +| DVR | Digital Video Recorder | +| HTTP | Hyper Text Transfer Protocol | +| IAS | Intelligent Application Service | +| ICU | Intelligent Customer Unit | +| IPU | Intelligent Premises Unit | +| IVM | Intelligent Video Management | +| IVS | Intelligent Video Surveillance | +| IVU | Intelligent Video Unit | +| MDU | Media Distribution Unit | +| MS | Media Server | +| MSU | Media Storage Unit | +| NTP | Network Time Protocol | +| NVR | Network Video Recorder | +| OCX | OLE Control Extension | +| OLE | Object Linking and Embedding | +| PIV | Premises Intelligent Video | +| PTZ | Pan/Tilt/Zoom | +| PU | Premises Unit | +| RTCP | Real-time Transport Control Protocol | +| RTP | Real-time Transport Protocol | +| SCU | Service-Control Unit | +| SIP | Session Initiation Protocol | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | +| USB | Universal Serial Bus | +| VS | Video Surveillance | + +## 5 Conventions + +In this Recommendation, the following conventions apply: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. + +## 6 Functional architecture + +Figure 6-1 shows the composition of an intelligent video surveillance system. + +![Figure 6-1: Composition of an intelligent video surveillance system. The diagram shows the functional architecture of an intelligent video surveillance system (IVSS). It is divided into two main parts: the IVSS (Intelligent Video Surveillance System) and the external units. The IVSS is enclosed in a blue box and contains four main functional blocks: CCS (Centre Management Unit - CMU and Service-Control Unit - SCU), MS (Media Storage - MDU and MSU), IPU (Intelligent Premises Unit - PIV), and ICU (Intelligent Customer Unit - CIV). The external units are DSS (Data Storage and Service), IAS (Intelligent Application Service), IVM (Intelligent Video Management), and IVU (Intelligent Video Unit). Arrows indicate the flow of Media (black), Control (red), and Video and image information (green).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the functional architecture of an intelligent video surveillance system (IVSS). It is divided into two main parts: the IVSS (Intelligent Video Surveillance System) and the external units. The IVSS is enclosed in a blue box and contains four main functional blocks: CCS (Centre Management Unit - CMU and Service-Control Unit - SCU), MS (Media Storage - MDU and MSU), IPU (Intelligent Premises Unit - PIV), and ICU (Intelligent Customer Unit - CIV). The external units are DSS (Data Storage and Service), IAS (Intelligent Application Service), IVM (Intelligent Video Management), and IVU (Intelligent Video Unit). Arrows indicate the flow of Media (black), Control (red), and Video and image information (green). + +Legend: + +- Media (black arrow) +- Control (red arrow) +- Video and image information (green arrow) + +Reference: H.626.5(22)\_F6-1 + +Figure 6-1: Composition of an intelligent video surveillance system. The diagram shows the functional architecture of an intelligent video surveillance system (IVSS). It is divided into two main parts: the IVSS (Intelligent Video Surveillance System) and the external units. The IVSS is enclosed in a blue box and contains four main functional blocks: CCS (Centre Management Unit - CMU and Service-Control Unit - SCU), MS (Media Storage - MDU and MSU), IPU (Intelligent Premises Unit - PIV), and ICU (Intelligent Customer Unit - CIV). The external units are DSS (Data Storage and Service), IAS (Intelligent Application Service), IVM (Intelligent Video Management), and IVU (Intelligent Video Unit). Arrows indicate the flow of Media (black), Control (red), and Video and image information (green). + +**Figure 6-1 – Composition of an intelligent video surveillance system** + +The functional architecture for the intelligent video surveillance system could be decomposed into ten units: + +- Centre management unit (CMU) +- Service-control unit (SCU) +- Media distribution unit (MDU) +- Media storage unit (MSU) +- Intelligent video unit (IVU) +- Intelligent video management (IVM) +- Intelligent customer unit (ICU) +- Intelligent premises unit (IPU) +- Data storage and service (DSS) +- Intelligent application service (IAS) + +The centre management unit (CMU), service-control unit (SCU), media distribution unit (MDU) and media storage unit (MSU) are defined in [ITU-T H.626]. The rest of units shown in Figure 6-1 are described in clauses 6.1 to 6.6 and the reference point in clause 7. + +### 6.1 Intelligent premises unit + +Intelligent premises unit (IPU) is the premises subsystem within the intelligent video surveillance system, such as video edge gateway, digital video recorder (DVR), network video recorder (NVR), or intelligent camera. The premises intelligent video (PIV) module is added to the premises unit (PU) for intelligent video analysis. The PIV is an intelligent identification module in the PU. It identifies required information from input video and outputs the analysis result. The PIV can search + +designated records from video files. The identifiable information includes triggered events and acquired data. + +The IPU implements the following functions like a normal PU as defined in [ITU-T H.626], it: + +- Captures multimedia information (such as audio, video, image, alarm signals, etc.) from the surveilled object. +- Encodes multimedia (audio, video and image) streams. +- Outputs alarm signals to an external linkage device. +- Parses pan/tilt/zoom (PTZ) commands and transmits them to the devices in order to control the camera. +- Provides network transportation and transmits bidirectional media streams and alarm signals to other entities. + +The IPU also implements some additional functions for intelligent applications, it: + +- Identifies required information from input videos and outputs analysis results. +- Reports the identified results such as triggered events and acquired data to the DSS. + +Figure 6-2 shows the function modules of the IPU based on a PU as defined in [ITU-T H.626]. The premises intelligent video (PIV) module is the only new module to implement intelligent identification functions or corresponding operations. + +![Figure 6-2: Function modules of IPU. The diagram shows a grid of function modules. The left column contains: Audio/video capture function, Audio play function, PTZ control function, Alarm input function, Alarm output function, and Media storage function. The middle column contains: Audio/video encoding function, Audio decoding function, and a large red-outlined box labeled 'PIV module'. The right column contains a single large box labeled 'Control and management function'. The text 'H.626.5(19)_F6-2' is at the bottom right.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +H.626.5(19)\_F6-2 + +Figure 6-2: Function modules of IPU. The diagram shows a grid of function modules. The left column contains: Audio/video capture function, Audio play function, PTZ control function, Alarm input function, Alarm output function, and Media storage function. The middle column contains: Audio/video encoding function, Audio decoding function, and a large red-outlined box labeled 'PIV module'. The right column contains a single large box labeled 'Control and management function'. The text 'H.626.5(19)\_F6-2' is at the bottom right. + +**Figure 6-2 – Function modules of IPU** + +### 6.2 Intelligent customer unit + +Intelligent customer unit (ICU) is the client subsystem within the intelligent video surveillance system. It is used to present multimedia information (such as audio, video, image, alarm signal, etc.) to the end user and trigger the related actions. The client intelligent video (CIV) is added to the CU in order to achieve comprehensive intelligent video analysis. The CIV is an intelligent identification module in the customer unit (CU). It identifies required information from the input video and outputs the analysis result. The CIV can search designated records from video files. The identifiable information includes triggered events and acquired data. + +It implements the following functions like a normal CU as defined in [ITU-T H.626]: + +- Multimedia decoding function. +- Audio play and video/image display function. +- Console interface for end user to operate the video surveillance (VS) system. + +It also implements some additional functions for intelligent applications, it: + +- Identifies required information from input video and outputs the analysis result. +- Retrieves the recorded video data with specified information. +- Reports and presents the analysis result to end users. + +Figure 6-3 shows the function modules of the ICU based on the CU as defined in [ITU-T H.626]. The client intelligent video (CIV) module is the only new module to implement intelligent identification related functions. + +![Figure 6-3 – Function modules of ICU. The diagram shows a box containing four modules: CIV module (highlighted with a red border), Console function, Play and display function, and Audio/video/image decoding function. Arrows indicate flow: Console function points to Audio/video/image decoding function, which points to Play and display function.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +graph TD; subgraph ICU [ICU Function Modules]; CIV[CIV module]; CF[Console function]; AV[Audio/video/image decoding function]; PD[Play and display function]; CF --> AV; AV --> PD; style CIV stroke:#ff0000,stroke-width:2px; style PD fill:#fff,stroke:#000; style AV fill:#fff,stroke:#000; style CF fill:#fff,stroke:#000; end +``` + +H.626.5(19)\_F6-3 + +Figure 6-3 – Function modules of ICU. The diagram shows a box containing four modules: CIV module (highlighted with a red border), Console function, Play and display function, and Audio/video/image decoding function. Arrows indicate flow: Console function points to Audio/video/image decoding function, which points to Play and display function. + +**Figure 6-3 – Function modules of ICU** + +### 6.3 Intelligent video management + +Intelligent video management (IVM) is the premises subsystem within the intelligent video surveillance system. + +The intelligent video unit (IVU) implements some normal functions for intelligent applications, it: + +- Supports configuration of intelligent applications by users and video sources schedules dynamically. +- Accepts registration, deletion, capability report from IVU and schedules IVUs dynamically. +- Stores, manages and schedules the category, supplier and capability of IVU dynamically. +- Manages intelligent analysis tasks such as query, start, pause and stop. +- Manages the licenses of special intelligent analysis tasks. +- Accepts intelligent capabilities queries from the intelligent application service (IAS) and sends the response. +- Accepts intelligent strategies queries from IAS and sends the response. + +It also implements some additional functions for intelligent applications, such as managing the IVU licenses using method such as universal serial bus (USB) keys and software keys. + +### 6.4 Intelligent video unit + +Intelligent video unit (IVU) is the premises subsystem within the intelligent video surveillance system. + +It implements some normal functions for intelligent applications, it: + +- Identifies specific objects automatically and outputs recognition results to the IVM. +- Recognizes information including triggered events and acquired data. +- Loads or unloads one or more intelligent analysis algorithms on IVU according to different requirements. +- Sends capability lists and statuses to the IVM. +- Supports the standard video stream transmission protocols (refer to [ITU-T H.627]). + +- Supports acquiring video streams from the video surveillance platform using application programming interfaces (APIs). +- Support images analysis using hypertext transfer protocol (HTTP), (refer to [IETF RFC 7230] protocol). + +It also implements some additional functions for intelligent application, such as IVU capability extension and IVU virtualization. + +### 6.5 Data storage and service + +Data storage and service (DSS) is the subsystem within the intelligent video surveillance system, it: + +- Obtains the video and image information from the intelligent premises unit (IPU), IVM and manual annotation from the IAS. +- Receives registration and keepalive report from the IVM, IAS, IPU, and synchronizes the status maintained in the system. +- Supports the configuration of different storage strategies to meet the access requirements. +- Manages the video and image information and stores it. +- Provides services to the IAS and IVM such as query, analysis, and sharing of the information. +- Supports information management and access control of the accessed IVM, IAS and IPU. + +Figure 6-4 shows the DSS functional composition. + +![Figure 6-4 – DSS functional composition diagram showing Interface module and Application module components and their interactions.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +The diagram illustrates the functional composition of the Data Storage and Service (DSS) subsystem. It consists of two main modules: the **Interface module** and the **Application module**. + +- Interface module**: Contains two sub-components: **Data obtaining** and **Data sharing**. +- Application module**: Contains four sub-components: **Registration and keepalive function**, **CRUD of video and image information function**, **Subscription and notification function**, and **Guard and alarm function**. + +Interactions are shown with arrows: + +- A red arrow points from **Data obtaining** to **Registration and keepalive function**, indicating **Control** flow. +- A green arrow points from **Data sharing** to **Subscription and notification function**, indicating **Video and image information** flow. + +Legend: +→ Control +→ Video and image information + +H.626.5(22)\_F6-4 + +Figure 6-4 – DSS functional composition diagram showing Interface module and Application module components and their interactions. + +**Figure 6-4 – DSS functional composition** + +The DSS's main process is as follows: + +Firstly, the data obtaining of interface module obtains the information transported from the IPU, IVM or IAS. Then the information is transferred and used by the application module. The data sharing of interface module provides services to the IAS and IVM such as query, analysis, and sharing of the information. + +In the intelligent video surveillance system, when the IPU, IVM, or IAS access the DSS, they need to register with the DSS actively, and de-register from the DSS when it stops running. The keepalive heartbeat interval and timeout times can be configured in the IPU, IVM, IAS and DSS. The IPU, IVM, and IAS are required to send heartbeat messages to the DSS according to the "heartbeat interval" periodically to keep the heartbeat alive. When the continuous timeout of heartbeat messages reaches the "keep-alive timeout times", the unit is considered offline and disconnected. The registration and keepalive function of the DSS processes the registration and keepalive information received by the interface module, performs information authentication on the accessed IPU, IVM, and IAS, and synchronizes their status maintained in the system. + +The DSS is required to support video and image information operations such as adding, modifying, deleting and querying from the IPU, IVM or IAS. After the interface module receives the identification information or manual annotation information, it forwards the request to the create/read/update/delete (CRUD) of the video and image information function. After data verification, cleaning and conversion, the function submits the information to storage. + +The DSS is required to support the IVM or IAS to subscribe or unsubscribe video and image information, such as vehicles, personnel, IPU device lists, etc. When the subscribed resource generates new information data, the DSS is recommended to notify immediately the IVM or IAS for data synchronization. The subscription and notification function implements them. + +The DSS or IVM is required to receive the guard commands of the IAS and should send notification messages to the IAS when the target object is found. After the announcement is sent, if no response is received within 5 seconds, the notification is deemed to have failed and should be retransmitted. If 3 consecutive retransmissions are still unsuccessful, it is deemed that there is a problem with the link, the information is cached, and the registration is performed again. After successful registration, all unannounced data will be retransmitted. The guard and alarm function implements them. + +### 6.6 Intelligent application service + +Intelligent application service (IAS) is the subsystem within the intelligent video surveillance system. + +It implements some normal functions for intelligent applications, it: + +- Supports application services about video and image information such as query, analysis, disposition and subscription. +- Receives IPU device lists from the CCS or the DSS. The updated device lists can be transferred to the DSS or IVM in order to obtain the media stream of these devices from the MS to the IVU. +- Supports application services about the manual annotation of the video and image information and stores the manual annotation to the DSS. +- Obtains video or image information from the DSS and distributes them according to different requirements. +- Creates and invokes intelligent analysis tasks for the IVM. +- Invokes the strategies and capabilities configuration for the IVM. + +# 7 Reference points + +The reference points Cm and Ds and Ds' are defined in [ITU-T H.626]. + +### 7.1 Reference point Ps: IPU – CCS + +The reference point Ps is located between the IPU and the central control server (CCS). It is used as defined in [ITU-T H.626]. + +### 7.2 Reference point Mp/Mp': IPU – MS + +The reference points Mp and Mp' are between the IPU and the media server (MS). They are used by the MS as defined in [ITU-T H.626]. + +### 7.3 Reference point Pc: IPU – ICU + +The reference point Pc is between the IPU and the ICU. It is used as defined in [ITU-T H.626]. + +### **7.4 Reference point Cs: ICU – CCS** + +The reference point Cs is between the ICU and CCS. It is used as defined in [ITU-T H.626]. + +### **7.5 Reference point Mc/Mc': ICU – MS** + +The reference points Mc and Mc' are between the ICU and the MS. They are used as defined in [ITU-T H.626]. + +### **7.6 Reference point Su: IVU – CCS** + +The reference point Su is between the IVU and the CCS. It is used to: + +- Send real-time audio and video requests to the IPU through the CCS. +- Send video storage and video requests to the IPU through the CCS. + +It uses the session initiation protocol (SIP). + +### **7.7 Reference point Du: IVU – MS** + +The reference point Du is between the IVU and the MS. It is used to: + +- Acquire video and audio streams from the MS through real-time transport protocol (RTP) (refer to [IETF RFC 3550])/RTCP protocol. +- Send UDP private network packets to the MS. +- Acquire RTP/RTCP packet from the MS in the TCP mode. + +### **7.8 Reference point Mu/Mu': IVU – IVM** + +The reference points Mu and Mu' are between the IVU and the IVM. Mu is used to: + +- Report the results of the intelligent analysis from the IVU to the IVM. + +Mu' is used to: + +- Register/de-register and keep alive from the IVU to the IVM. +- Send the request of an intelligence analysis task from the IVM to the IVU. +- Report the status of the intelligence analysis task from the IVU to the IVM. +- Report the intelligence analysis capabilities and resource usage status from the IVU to the IVM. +- Manage the license of special intelligent analysis task from the IVM to IVU, IVM loads or releases the IVU according to the license information. + +They use the HTTP+JSON protocol. + +### **7.9 Reference point Ma/Ma': IVM – IAS** + +The reference points Ma and Ma' are between the IVM and the IAS. Ma is used to: + +- Report the results of the intelligent analysis task from the IVM to the IAS. + +Ma' is used to: + +- Register/de-register and keep alive from the IVM to the IAS. +- Send the user request of an intelligence analysis task (such as search target by image, search target by attribute, etc.) from the IAS to the IVM. +- Report the status of the intelligence analysis task from the IVM to the IAS. +- Control the intelligence analysis task from the IVM to the IAS. + +They use the HTTP+JSON protocol. + +### 7.10 Reference point Ad/Ad': DSS – IAS + +The reference points Ad and Ad' are between the DSS and the IAS. Ad is used to: + +- Transmit video and image information from the IAS to the DSS when the manual annotation information captured by the IAS is required to be collected to the DSS. +- Transmit the authorized video and image information, IPU list from the DSS to the IAS when the data stored in the DSS is required to be accessed by the IAS's users. + +Ad' is used to: + +- Register/de-register and keep alive from the DSS to the IAS. +- Send video and image information and IPU list access request from the IAS to the DSS such as information query or subscription, etc. + +They use the HTTP + JSON protocol. + +### 7.11 Reference point Id/Id': DSS – IVM + +The reference points Id and Id' are between the DSS and the IVM. Id is used to: + +- Transmit video and image information from the IVM to the DSS when the recognition information parsed by the IVUs of the IVM is required to be collected to the DSS. +- Transmit the authorized video and image data from the DSS to the IVM when the data stored in the DSS is required to be accessed by the IVM's users. + +Id' is used to: + +- Register/de-register and keep alive from the IVM to the DSS. +- Send data access request from the IVM to the DSS. +- Support information query based on the feature attributes of the video image information from the IVM to the DSS. +- Support the disposition and notification of video image information between the DSS and the IVM. +- Support subscription and notification of video image information, collection device/system lists, etc., between the IVM and the DSS. + +They use the HTTP + JSON protocol. + +### 7.12 Reference point Pd/Pd': DSS – IPU + +The reference points Pd and Pd' are between the DSS and the IPU. Pd is used to: + +- Transmit video and image data from the IPU to the DSS when the recognition information captured by the IPU is required to be collected to the DSS. + +Pd' is used to: + +- Register/de-register and keep alive from the IPU to the DSS. + +They use the HTTP + JSON protocol. + +### 7.13 Reference point Ac: IAS – CCS + +The reference point Ac is between the IAS and the CCS. It is used to: + +- Send the user authentication request from the IAS to the CMU and return the authentication result. +- Acquire the IPU list that the user has been authorized to access, the configuration information of the specified IPU, the alarm information, the status information and the platform video storage information. + +It uses the HTTP+JSON protocol. + +## Bibliography + +- [b-ITU-T H.626.3] Recommendation ITU-T H.626.3 (2018), *Architecture for visual surveillance system interworking*. +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions*. +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68ffb2a2639dfa7aed6cefb5125fc325ab0bf06f --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ca0d99effb1be45bec9596bd99343ae54a5f642f90dd0448af29354ec230549 +size 48558 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6195a748b4376b4aa1ff3a02a5522b430f412ec3 --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0987234c557e158fa4a58f40b77d3ebacc001803312d0d393384e2c865fe21f2 +size 40595 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b94b8303300011f3d5bb64a19e32c66ccbf58de7 --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bef03291f1b4763419bde63b35cafa33412ac46b5a9186a2503f94475ff36b3d +size 18633 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15c0ce5105aef826f33a7a685bb7aef64a20925a --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:667b2f765c704ceefab3b8696977cae27ce604a9c036eff3b0058c6f7860a599 +size 53574 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/7ede87328f6b696dcffa65ebc4570cc8_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/7ede87328f6b696dcffa65ebc4570cc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4284329618a7020e4d1539f16f1fcba1eaf39856 --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/7ede87328f6b696dcffa65ebc4570cc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95b932c4247917cc4496782c9ffadaedb9933a7ef8257b15a53d3a289870e535 +size 20071 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8afef406ba9628e0beacf529fe17e0b433b34794 --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3188c0cf3a7fbd2fe5803fa8b953d156b3cf4ea21d1e57c294ea43b3a04ded36 +size 11629 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0ea8f63fd2c94b1f171c416597a79948a413026 --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9f1f02328caa7fbb279a36d07a4b6312fd363e1ac8811313a7c724dd1bcb590 +size 170376 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8394f739df9f05b3a3b77b0b3591fe381ca2d402 --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40828204660dd7202d19134af9b9bd34c503ddac8c28200641026cfa1ff6c166 +size 16846 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e3d65dbcd3c8382e515a9821702f1cfc64a616e --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d05792c85cbf50d9086bffbcc9eec4366500c5ebf3c7d9d91f096a66a8d004e +size 52377 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c8a6d37931431c7e43b1c480d3203ff01697843 --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2b255d00cd86ece33b2edf6c89f114c55f4382230fc060bc0e288e7ccb09218 +size 14794 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.626.8-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb4acabd906324b97409afa59bd03bd2e862bddd --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab32468cf86e4997839852c73df0ad1be133496483982bbd43aacbc850346693 +size 43472 diff --git a/marked/H/T-REC-H.626.8-202503-I_PDF-E/raw.md b/marked/H/T-REC-H.626.8-202503-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..29df7519ec766bc1939b5eddf20ba46240f47278 --- /dev/null +++ b/marked/H/T-REC-H.626.8-202503-I_PDF-E/raw.md @@ -0,0 +1,874 @@ + + +# Recommendation **ITU-T H.626.8 (03/2025)** + +SERIES H: Audiovisual and multimedia systems + +Broadband, triple-play and advanced multimedia services – +Advanced multimedia services and applications + +--- + +## **Protocols for feature-based distributed intelligent systems** + +![ITU logo](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +## **Audiovisual and multimedia systems** + +| | | +|-----------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| Broadband multimedia services over VDSL | H.610-H.619 | +| Advanced multimedia services and applications | H.620-H.629 | +| Content delivery and ubiquitous sensor network applications | H.640-H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.626.8 + +# Protocols for feature-based distributed intelligent systems + +## Summary + +Recommendation ITU-T H.626.8 specifies detailed protocols of the feature-based distributed intelligent systems, based on the requirements specified in Recommendation ITU-T F.748.21 and the functional architecture specified in Recommendation ITU-T F.748.22. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.626.8 | 2025-03-16 | 21 | 11.1002/1000/16248 | + +## Keywords + +Feature, intelligent system, protocols. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Introduction to functional architecture of FDIS ..... | 3 | +| 7 Overall requirements of protocols and feature stream..... | 5 | +| 7.1 Introduction of related protocols ..... | 5 | +| 7.2 Feature stream keepalive mechanism..... | 5 | +| 7.3 Feature packaging..... | 6 | +| 7.4 TCP-based feature transmission ..... | 7 | +| 8 Workflows and relevant protocols..... | 7 | +| 8.1 Registration and de-registration ..... | 7 | +| 8.2 Real-time feature stream..... | 9 | +| 8.3 Device configuration and control ..... | 11 | +| 8.4 Device information query ..... | 13 | +| 8.5 Status information reporting..... | 14 | +| 8.6 Historical feature file retrieval..... | 15 | +| 8.7 Time calibration..... | 15 | +| 8.8 Data preprocessing ..... | 16 | +| 8.9 Feature stream generation and processing..... | 17 | +| Appendix I – Examples of workflows and relevant protocols..... | 20 | +| I.1 Device information query command example ..... | 20 | +| Bibliography..... | 21 | + + + +# Recommendation ITU-T H.626.8 + +# Protocols for feature-based distributed intelligent systems + +# 1 Scope + +This Recommendation specifies in detail protocols of feature-based distributed intelligent systems (FDIS), based on the functional architecture specified in [ITU-T F.748.22]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T F.748.21] Recommendation ITU-T F.748.21 (2022), *Requirements and framework for feature-based distributed intelligent systems*. +- [ITU-T F.748.22] Recommendation ITU-T F.748.22 (2023), *Functional architecture for feature-based distributed intelligent systems*. +- [ITU-T H.222.0] Recommendation ITU-T H.222.0 v10 (2025), *Information technology - Generic coding of moving pictures and associated audio information: Systems*. +- [ITU-T H.627] Recommendation ITU-T H.627 (2020), *Signalling and protocols for a video surveillance system*. +- [IETF RFC 2250] IETF RFC 2250 (1998), *RTP payload format for MPEG1/MPEG2 video*. +- [IETF RFC 3261] IETF RFC 3261 (2002), *SIP: Session initiation protocol*. +- [IETF RFC 3428] IETF RFC 3428 (2002), *Session initiation protocol (SIP) extension for instant messaging*. +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A transport protocol for real-time applications*. +- [IETF RFC 3551] IETF RFC 3551 (2003), *RTP profile for audio and video conferences with minimal control*. +- [IETF RFC 4571] IETF RFC 4571 (2006), *Framing real-time transport protocol (RTP) and RTP control protocol (RTCP) packets over connection-oriented transport*. +- [IETF RFC 5905] IETF RFC 5905 (2010), *Network time protocol version 4: Protocol and algorithms specification*. +- [IETF RFC 7798] IETF RFC 7798 (2016), *RTP payload format for high efficiency video coding (HEVC)*. +- [IETF RFC 8866] IETF RFC 8866 (2021), *SDP: Session description protocol*. +- [IETF RFC 9112] IETF RFC 9112 (2022), *HTTP/1.1*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 front-end equipment** [b-ITU-T K.142]: Outdoor camera and associated ancillary equipment. + +**3.1.2 premises unit** [b-ITU-T F.743]: A device located at the remote part of a video surveillance system and used to capture multimedia information (such as audio, video, image, alarm signal, etc.) from a surveilled object. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------------------| +| AAC | Advanced Audio Coding | +| AFS | Application Function Set | +| DPFS | Data Processing Function Set | +| ECCS | Extended Control Command Set | +| EMCS | Extended Media Command Set | +| FCM | Feature Coding for Machines | +| FDIS | Feature-based Distributed Intelligent Systems | +| FFS | Front-end Function Set | +| HTTP | Hypertext Transfer Protocol | +| ID | Identifier | +| MFS | Management Function Set | +| ML | Machine Learning | +| NLP | Natural Language Processing | +| NTP | Network Time Protocol | +| OFS | Operation Function Set | +| PES | Packetized Elementary Stream | +| PESA | Packetized Elementary Stream Audio | +| PESF | Packetized Elementary Stream Feature | +| PESV | Packetized Elementary Stream Video | +| PSM | Program Stream Map | +| RTP | Real-Time Protocol | +| RTCP | RTP Control Protocol | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | + +| | | +|-----|-------------------------------| +| SN | Serial Number | +| TCP | Transmission Control Protocol | +| UA | User Agent | +| UDP | User Datagram Protocol | + +# 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus this requirement needs not be present to claim conformance. +- The keywords "can optionally" and "may" indicate an optional requirement which is permissible, without implying any sense of being recommended. These terms are not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +# 6 Introduction to functional architecture of FDIS + +Figure 1 shows the functional architecture of FDIS. + +![Functional architecture of FDIS diagram showing layers A1 through A9 and their components.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the functional architecture of FDIS, organized into layers A1 through A9: + +- Application function set (A4):** Natural language processing, Image and video processing, Biomedical engineering, Financial modelling. +- Service control function set (A5):** Data storage function, Industrial camera SDK, Natural network algorithm models. +- Algorithm function set (A3):** Intelligent video algorithm function, Intelligent audio algorithm function, Natural language processing function. +- Data processing function set (A2):** Feature decoding function, Data storage function, Data preparation function. +- Front-end function set (A1):** + - Video sensor function (B1a) and Audio sensor function (B1b) feed into Data preprocessing function (B2). + - Data preprocessing function (B2) feeds into Feature extraction function (B3). + - Feature extraction function (B3) feeds into Feature compression function (B4). + - Feature encoding function (B4) feeds into Feature compression function (B4). +- Operation function set (A6):** Data transformation, Data aggregation, Data cleansing, Feature selection. +- Security function set (A8):** Data encryption, Data authentication, Data access control, Data integrity check, Network security, Security status, Data masking, Data integrity auditing. +- Management function set (A7):** Camera management, Equipment management, System monitoring, Resource management. +- Development function set (A9):** Model training, Model validation, Model compression, Model visualization. + +Interconnections between layers are labeled A1 through A9. + +Functional architecture of FDIS diagram showing layers A1 through A9 and their components. + +H.626.8(25) + +**Figure 1 – Functional architecture of FDIS** + +NOTE – Figure 1 is adapted from [ITU-T F.748.22] with modifications as necessary for the context of this document. + +A functional architecture of feature-based distributed intelligent systems (FDIS) is composed of a front-end function set, a data processing function set, an algorithm function set, an application function set, a service control function set, an operation function set, a management function set, and a security function set: + +- The front-end function set captures, processes, and compresses the analogue signal from the real-world scenarios. +- The data processing function set provides the ability to pre-process, extract features, and encode/decode data. +- The algorithm function set provides algorithms for machine tasks, data storage, and data evaluation. +- The development function set provides the capability of model training, model validation, model compression and model visualization. +- The application function set provides the capability to implement machine tasks from the real-world scenarios and/or from the feature stream. +- The service control function set provides capabilities for users to control the service of the feature-based distributed intelligent system. + +- The operation function set provides the capability to manage and monitor the operation status of the system. The management function set is required to provide the ability to manage different parts of the feature-based distributed intelligent system. +- The management function set provides the capability to manage and monitor the operation status of the system. +- The security function set provides capabilities for system security. + +# 7 Overall requirements of protocols and feature stream + +## 7.1 Introduction of related protocols + +The structure of communication protocols is illustrated in Figure 2. The FDIS contains three protocol channels, including the session channel, media channel and feature channel. The session channel contains extended control command set (ECCS) and extended media command set (EMCS) defined in [ITU-T H.627] as an extension of session description protocol (SDP). The feature channel may contain a feature stream which can be transmitted in a real-time transmission scenario using RTP/RTCP or in a stable transmission scenario using hypertext transfer protocol (HTTP). A feature stream can be produced in scenarios of feature coding for machines (FCM), which is used for machine tasks as specified in [ITU-T F.748.21] and [ITU-T F.748.22]. The media channel may contain one or both types of video, audio if needed by the system. + +![](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +| Session channel | | | Media channel | | Feature channel | | | +|-----------------|------|------|---------------------------------------------|-----------------------------------------------|-----------------------|-----------------------|------------------| +| SDP | ECCS | EMCS | ITU-T H.264/
    ITU-T H.265/
    ITU-T H.266 | ITU-T G.711/
    ITU-T G.723.1/
    ITU-T G.729 | Signal domain feature | Latent domain feature | Semantic feature | +| SIP | | | RTP/RTCP | | RTP/RTCP | | HTTP | +| TCP/UDP | | | | | | | | +| IP | | | | | | | | + +H.626.8(25) + +**Figure 2 – Structure of communication channels and protocols** + +## 7.2 Feature stream keepalive mechanism + +The keepalive mechanism for the feature stream of FDIS is specified as follows: + +- After the feature link is established, the FDIS shall have the capability of monitoring feature stream losses. If any feature stream loss is monitored, the feature link shall be released, and it shall notify the other interconnected FDISs through BYE messages in the session; +- Status monitoring shall be performed through registration, status information reporting, etc. between the interconnected FDISs and between the FDIS and the management function set (MFS). If the feature stream receiver or feature stream sender is monitored and found to be faulty or off-line, it shall actively release the feature link and stop sending the feature stream; +- The sent stream shall be cleared and judged by the Subject identification. When an MFS sends a call request to another MFS or an MFS sends a call request to a FDIS, it shall carry the Subject header field, and the "feature stream sender ID: sender's media stream SN" in the Subject header field is used as the identification of the feature source, and the identification corresponds to the requested code stream. Upon receiving the call request, the requested FDIS shall judge whether the code stream identified by the feature source is being sent. If it has been sent, the existing feature stream sending link shall be released, and a new feature stream sending link shall be established according to the request. + +## 7.3 Feature packaging + +### 7.3.1 RTP-based PS packaging of feature stream + +The RTP-based program stream (PS) packaging first packages the feature stream into the PS packages in accordance with [ITU-T H.222.0], and then packages the PS packages into the RTP packages in the form of loads. + +While conducting PS packaging, each video frame shall be packaged into a PS packages, and the PS packages of each keyframe shall include a system header and a program stream map (PSM). The system header and the PSM shall be arranged after the PS packages header and before the first packetized elementary stream (PES) packages. + +The typical PS package structure for a keyframe is as shown in Figure 3, showing packetized elementary stream feature (PESF) packages and, if needed, packetized elementary stream video (PESV) and packetized elementary stream audio (PESA), while the PS package structure of a non-keyframe feature usually does not include a system header and a PSM. For the specific data structures of various parts in the PS packages, see the relevant descriptions in [ITU-T H.222.0]. + +![Figure 3: Typical PS package structure for a video keyframe. The diagram shows a sequence of fields in a PS package: PS package header, System header, PSM, PESF, PESV, and PESA. The fields are arranged horizontally in a single row. The label 'H.626.8(25)' is placed below the right side of the diagram.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +| | | | | | | +|-------------------|---------------|-----|------|------|------| +| PS package header | System header | PSM | PESF | PESV | PESA | +|-------------------|---------------|-----|------|------|------| + +H.626.8(25) + +Figure 3: Typical PS package structure for a video keyframe. The diagram shows a sequence of fields in a PS package: PS package header, System header, PSM, PESF, PESV, and PESA. The fields are arranged horizontally in a single row. The label 'H.626.8(25)' is placed below the right side of the diagram. + +**Figure 3 – Typical PS package structure for a video keyframe** + +The system header shall include the descriptions for media stream types in the PS packages, where the values for feature, video and audio stream IDs (stream\_id) are as follows: + +- video stream ID: 0xE0, see the definition in [ITU-T H.627]; +- audio stream ID: 0xC0, see the definition in [ITU-T H.627]; +- feature stream ID: 0xF0. + +For the various feature, video or audio formats specified in this Recommendation, the values for media stream types (stream\_type) in PSM are as follows: + +- ITU-T H.264 video stream: 0x1B, see the definition in [ITU-T H.627]; +- ITU-T H.265 video stream: 0x24, see the definition in [ITU-T H.627]; +- ITU-T G.711A audio stream: 0x90, see the definition in [ITU-T H.627]; +- ITU-T G.711U audio stream: 0x91, see the definition in [ITU-T H.627]; +- ITU-T G.723.1 audio stream: 0x93, see the definition in [ITU-T H.627]; +- ITU-T G.729 audio stream: 0x99, see the definition in [ITU-T H.627]; +- advanced audio coding (AAC) audio stream: 0x0f, see the definition in [ITU-T H.627]; +- feature stream: 0x80. + +For the details of other specific technical specifications for the PS packaging, see [ITU-T H.222.0]. + +For the RTP packaging formats of the PS packages, see [IETF RFC 2250]. The main parameter settings of RTP are as follows: + +- payload type: 96; +- encoding name: PS; +- clock rate: 90 kHz. + +### 7.3.2 RTP-based elementary stream packaging of feature stream + +Information on the packaging of video or audio data can be found in [ITU-T H.627]. + +The feature stream is directly packaged into the RTP packages as payloads. + +The RTP payload format for feature stream shall comply with the relevant provisions of [IETF RFC 7798]. + +Selection of payload type identification number of RTP packages for feature stream: It shall be selected from the dynamic range (96-127) according to Table 5 of [IETF RFC 3551], which is recommended to be set as 101. + +### **7.3.3 HTTP-based elementary stream packaging of feature stream** + +The feature stream is directly packaged into the HTTP packages as payloads. + +The HTTP payload format for feature stream shall comply with the relevant provisions of [IETF RFC 9112]. + +## **7.4 TCP-based feature transmission** + +The transmission control protocol (TCP)-based feature transmission for real-time feature stream, historical feature stream playback and download shall support the feature and, if needed, video and audio PS streams based on the TCP packaging. For the packaging format, see [IETF RFC 4571]. + +The media server (MS) should simultaneously support serving as the server and the client for TCP media transmission. Under the default condition, when the front-end function set (FFS) sends a feature stream to the MS, the FFS shall serve as the client for TCP feature stream transmission, and the MS shall serve as the server for TCP feature stream transmission. In the case of TCP-based feature stream transmission between two MSs, the feature stream receiver should serve as the server for the TCP feature stream transmission. + +The feature stream sender and receiver can extend the SDP parameters for the negotiation of server and client for the TCP feature stream transmission. For the negotiation mechanism, see clause 7.7 in [ITU-T H.627]. + +The TCP feature transmission for real-time feature stream, historical feature stream playback, and download should support the reconnection mechanisms when establishing TCP connections. If the first TCP connection fails, the TCP feature-streaming client should attempt reconnection at intervals. The reconnection attempt interval should be no less than 1 second, and the number of reconnection attempts should be no less than three. + +# **8 Workflows and relevant protocols** + +## **8.1 Registration and de-registration** + +With reference to [ITU-T H.627], the registration and de-registration are specified in clauses 8.1.1, 8.1.2 and 8.1.3 as follows. + +### **8.1.1 Basic requirements** + +- A session initiation protocol (SIP) user agent (UA) is registered and de-registered with the method REGISTER specified in [IETF RFC 3261]. Authentication shall be conducted during registration and de-registration, and the authentication method shall support the digital digest authentication method. +- The SIP UA is required to update the registration in the MFS before the expiry of the registration. The registration message-updating process shall be consistent with the process of registration described in clause 8.1.2 and follow the provisions of [IETF RFC 3261] on registration updating. + +- If the registration fails, the SIP UA is required to initiate the registration process again after a certain time interval, while the time interval from the last registration time shall be adjustable, which shall not be less than 60 seconds generally. +- The registration expiry time of the SIP UA shall be configurable, and the default value is 86 400 seconds (1 day). The registration-updating message shall be sent before the expiry of the registration, thereby leaving a proper registration updating time for the MFS, and the registration expiry time shall not be less than 3 600 seconds. +- If the SIP UA registration is successful, the MFS is deemed online. If the registration fails, the MFS is considered to be offline. The SIP UA is deemed as online by the MFS after the SIP UA registration is successful. If the registration expires, the SIP UA is considered to be offline. +- For the SIP UA and MFS to identify each other's protocol versions, the extension field, in the header of the SIP registration and its response message (whether successful or failure), X-Ver is used to represent the version. After both parties identify the protocol version supported by the other party in the registration process, the party with a higher protocol version shall avoid sending messages that cannot be recognized by the party with the lower version in the subsequent interaction. The version is composed of a string of Arabic numerals and decimal characters. The version number is expressed as m.n, where "m" and "n" are Arabic numerals, such as: X-Ver: 1.0. + +### 8.1.2 Signalling process + +#### 8.1.2.1 Registration + +The registration is in accordance with the challenge responsive security technology based on the digital digest specified in [IETF RFC 3261]. For the specific registration signalling flow, see Figure 4. + +![Sequence diagram showing the signalling flow of registration between MFS and SIP UA. The steps are: 1. REGISTER (SIP UA to MFS), 2. 401 unauthorized (MFS to SIP UA), 3. REGISTER (SIP UA to MFS), 4. 200 OK (MFS to SIP UA).](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +sequenceDiagram + participant SIP UA + participant MFS + Note right of SIP UA: H.626.8(25) + SIP UA->>MFS: 1. REGISTER + MFS-->>SIP UA: 2. 401 unauthorized + SIP UA->>MFS: 3. REGISTER + MFS-->>SIP UA: 4. 200 OK + +``` + +Sequence diagram showing the signalling flow of registration between MFS and SIP UA. The steps are: 1. REGISTER (SIP UA to MFS), 2. 401 unauthorized (MFS to SIP UA), 3. REGISTER (SIP UA to MFS), 4. 200 OK (MFS to SIP UA). + +**Figure 4 – Signalling flow of registration** + +The signalling flow description is as follows: + +- The SIP UA sends the REGISTER request to the MFS. +- The MFS sends the response 401 to the SIP UA, and the authentication mechanism and parameters applicable for the SIP UA are provided in the WWW\_Authenticate field of the response message header. +- The SIP UA resends the REGISTER request to the MFS and provides a trust letter in the authorization field of the request, including authentication information. +- The MFS verifies the request. If the SIP UA identity when checked is legal, it sends the successful response 200 OK to the SIP UA. If the identity is illegal, it sends a denial of service response. + +#### 8.1.2.2 De-registration + +For the de-registration signalling flow, see Figure 5. + +![Sequence diagram showing the de-registration signalling flow between a SIP UA and an MFS. The flow consists of four steps: 1. REGISTER (Expires = 0) from SIP UA to MFS; 2. 401 unauthorized from MFS to SIP UA; 3. REGISTER (Expires = 0) from SIP UA to MFS; 4. 200 OK from MFS to SIP UA. The diagram is labeled H.626.8(25) at the bottom right.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +``` +sequenceDiagram + participant SIP UA + participant MFS + Note left of SIP UA: H.626.8(25) + SIP UA->>MFS: 1. REGISTER (Expires = 0) + MFS-->>SIP UA: 2. 401 unauthorized + SIP UA->>MFS: 3. REGISTER (Expires = 0) + MFS-->>SIP UA: 4. 200 OK +``` + +Sequence diagram showing the de-registration signalling flow between a SIP UA and an MFS. The flow consists of four steps: 1. REGISTER (Expires = 0) from SIP UA to MFS; 2. 401 unauthorized from MFS to SIP UA; 3. REGISTER (Expires = 0) from SIP UA to MFS; 4. 200 OK from MFS to SIP UA. The diagram is labeled H.626.8(25) at the bottom right. + +**Figure 5 – Signalling flow of de-registration** + +The de-registration signalling flow description is as follows: + +- The SIP UA sends the REGISTER request to the MFS, and the value of the Expires field is 0, showing that the SIP UA requests to be de-registered; +- The MFS sends the response 401 to the SIP UA, and the authentication mechanism and parameters applicable for the SIP UA are provided in the WWW\_Authenticate field of the response message header; +- The SIP UA resends the REGISTER request to the MFS and provides a trust letter in the Authorization field of the request, including authentication information, and the value of the Expires field is 0; +- The MFS verifies the request. If the SIP UA identity is checked to be legal, it sends the successful response 200 OK to the SIP UA. If the identity is illegal, it sends the denial of service response. + +### 8.1.3 Protocol interface + +For the protocol interface, see [IETF RFC 3261], which specifies the SIP registration protocol. + +## 8.2 Real-time feature stream + +### 8.2.1 Basic requirements + +- The SIP message of the real-time feature stream is required to be routed and forwarded through the MFS in the FDIS, and the real-time feature stream of the FFS is required to be forwarded to data processing function set (DPFS). +- The session connection of the real-time feature stream is achieved with the INVITE method in the SIP [IETF RFC 3261], and the feature transmission is achieved through the RTP or RTCP [IETF RFC 3550], [IETF RFC 4571]. +- The real-time feature stream is required to support the feature stream keepalive mechanism specified in clause 7.2. + +### 8.2.2 Signalling process + +The signalling flow of the real-time media stream initiated by the media stream receiver is shown in Figure 6. + +![Sequence diagram showing the signalling flow of a real-time feature stream initiated by a feature stream receiver in the DPFS. The diagram involves three entities: DPFS, MFS, and FFS. The sequence of messages is: 1. INVITE (with SDP) from DPFS to MFS; 2. INVITE from MFS to FFS; 3. 200 OK (with SDP) from FFS to MFS; 4. 200 OK (with SDP) from MFS to DPFS; 5. ACK from DPFS to MFS; 6. ACK from MFS to FFS; 7. BYE from DPFS to MFS; 8. 200 OK from MFS to DPFS; 9. BYE from MFS to FFS; 10. 200 OK from FFS to MFS. A 'Real-time feature stream' is indicated between DPFS and FFS after the ACK messages. The diagram is labeled H.626.8(25) at the bottom right.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +sequenceDiagram + participant DPFS + participant MFS + participant FFS + Note right of FFS: H.626.8(25) + DPFS->>MFS: 1. INVITE (with SDP) + MFS->>FFS: 2. INVITE + FFS-->>MFS: 3. 200 OK (with SDP) + MFS-->>DPFS: 4. 200 OK (with SDP) + DPFS->>MFS: 5. ACK + MFS->>FFS: 6. ACK + Note over DPFS, FFS: Real-time feature stream + DPFS->>MFS: 7. BYE + MFS-->>DPFS: 8. 200 OK + MFS->>FFS: 9. BYE + FFS-->>MFS: 10. 200 OK + +``` + +Sequence diagram showing the signalling flow of a real-time feature stream initiated by a feature stream receiver in the DPFS. The diagram involves three entities: DPFS, MFS, and FFS. The sequence of messages is: 1. INVITE (with SDP) from DPFS to MFS; 2. INVITE from MFS to FFS; 3. 200 OK (with SDP) from FFS to MFS; 4. 200 OK (with SDP) from MFS to DPFS; 5. ACK from DPFS to MFS; 6. ACK from MFS to FFS; 7. BYE from DPFS to MFS; 8. 200 OK from MFS to DPFS; 9. BYE from MFS to FFS; 10. 200 OK from FFS to MFS. A 'Real-time feature stream' is indicated between DPFS and FFS after the ACK messages. The diagram is labeled H.626.8(25) at the bottom right. + +**Figure 6 – Signalling flow of real-time feature stream initiated by feature stream receiver in the DPFS** + +In Figure 6: + +- signals 1 and 4 constitute the process of establishing the link between the DPFS and the MFS; +- signals 2 and 3 constitute the process of establishing the link between the MFS and the FFS; +- signals 7 and 8 constitute the process of disconnecting the link between the DPFS and the MFS; +- signals 9 and 10 constitute the process of disconnecting the link between the MFS and the FFS. + +The signalling flow description is as follows: + +- The DPFS sends the Invite message to the MFS, and the message header field carries the subject field, showing such parameters as the source ID of the real-time feature stream, ID of the feature stream receiver in the DPFS and feature stream SN, the s field in the SDP message is "Play", representing the real-time feature stream. +- After the MFS receives the Invite request, the Invite message is sent to the FFS, and this message does not carry the SDP message body. +- After the FFS receives the Invite request of the MFS, it replies with the 200 OK response, carrying the SDP message body in which the Internet protocol (IP), port, feature format, etc., of the feature stream obtained by the FFS are described. The connection between the MFS and the FFS is established. +- The MFS forwards the 200 OK response to the DPFS with the SDP message in the message 3 sent from the FFS. +- After the DPFS receives the 200 OK response, it replies with the ACK message, and the establishment process of the Invite session with MFS is finished. +- The MFS forwards the ACK message from DPFS to the FFS, and the establishment process of the Invite session with the FFS is finished. +- The DPFS sends the BYE message to the MFS, and the Invite session with the DPFS established between the MFS is disconnected. + +- After the MFS receives the BYE message, it replies with the 200 OK response, and the session is disconnected. +- After the MFS receives the BYE message, it sends the BYE message to the FFS, and the Invite session with the FFS is disconnected. +- After the FFS receives the BYE message, it replies with the 200 OK response, and the session is disconnected. + +### 8.2.3 Protocol interface + +With reference to [ITU-T H.627], the protocol interface is specified as follows with minor modifications: + +The detailed specification of the SIP message header field (such as To, From, Cseq, Call-ID, Max-Forwards and Via) complies with the provisions of the IETF RFC document of the relevant SIP message. + +The Allow field of the message header shall support INVITE, ACK, INFO, CANCEL, BYE, OPTIONS and MESSAGE methods, but does not exclude the support of other SIP and SIP extension methods. + +The Content-type field of the message header shall show that the message body is specified in the SDP format. For example: + +Content-type: Application/SDP. + +The source device shall include the t line (see clause 5.9 of [IETF RFC 8866]) in the message body in the SDP format, and the start time and the end time of the t line are both set to 0, representing real-time media stream. + +The request and response message bodies carried in the real-time media stream process are specified in the SDP format. For a detailed description related to SDP, see [IETF RFC 8866]. + +The SDP text message includes session name and intention, session duration, media comprising the session, and information needed to receive those session (address, ports, formats, etc.). + +The message body in the SDP format shall include the o line (see clause 5.2 of [IETF RFC 8866]), and the username in the o line shall be the device code of this device; the c line shall include the device or system IP address; the m line shall include the media receiving port number. + +## 8.3 Device configuration and control + +With reference to [ITU-T H.627], the device configuration and control are specified in clauses 8.3.1, 8.3.2 and 8.3.3 as follows: + +### 8.3.1 Basic requirements + +- The source sends the device configuration command to the target, and the configuration command types include device ID, expiration time of registration, alarm period, heartbeat interval, expiration number of heartbeat, password of device background and management of tunnel information device. The command is achieved by the MESSAGE method of [IETF RFC 3428]. +- The sources include MFS, application function set (AFS), and service control function set (SCFS), and the targets include other function sets in the FDIS. +- After the source sends the configuration command, the target shall send a response command to represent the executive result. + +#### 8.3.1.1 Signalling process + +For the device configuration signalling flow, see Figure 7. + +![Sequence diagram showing the signalling flow of device configuration between Source, MFS, and Target. The flow consists of six steps: 1. Source sends MESSAGE (Device configuration request command) to MFS; 2. MFS responds with 200 OK; 3. MFS sends MESSAGE (Device configuration request command) to Target; 4. Target responds with 200 OK; 5. Target sends MESSAGE (Device configuration response command) to MFS; 6. MFS responds with 200 OK. The diagram is labeled H.626.8(25) at the bottom right.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant Source + participant MFS + participant Target + Note right of Target: H.626.8(25) + Source->>MFS: 1. MESSAGE (Device configuration request command) + MFS-->>Source: 2. 200 OK + MFS->>Target: 3. MESSAGE (Device configuration request command) + Target-->>MFS: 4. 200 OK + Target->>MFS: 5. MESSAGE (Device configuration response command) + MFS-->>Source: 6. 200 OK + +``` + +Sequence diagram showing the signalling flow of device configuration between Source, MFS, and Target. The flow consists of six steps: 1. Source sends MESSAGE (Device configuration request command) to MFS; 2. MFS responds with 200 OK; 3. MFS sends MESSAGE (Device configuration request command) to Target; 4. Target responds with 200 OK; 5. Target sends MESSAGE (Device configuration response command) to MFS; 6. MFS responds with 200 OK. The diagram is labeled H.626.8(25) at the bottom right. + +**Figure 7 – Signalling flow of device configuration** + +The signalling flow description is as follows: + +- The source sends device configuration commands to the MFS, and the device configuration commands are carried in the message body by the MESSAGE method. +- The MFS replies with a 200 OK response after receiving the commands. +- The MFS sends device configuration commands to the target, and the device configuration commands are carried in the message body by the MESSAGE method. +- The target replies with a 200 OK response after receiving the commands. +- The target sends device configuration response commands to the MFS, and the device configuration response commands are carried in the message body by the MESSAGE method. +- The MFS replies with a 200 OK response after receiving the commands. +- The MFS forwards the device configuration response commands to the source, and the device configuration response commands are carried in the message body by the MESSAGE method. +- The source replies with a 200 OK response after receiving the commands. + +#### 8.3.1.2 Protocol interface + +##### a) Request command message body + +The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml, where xml represents extensible markup language. + +The device configuration commands are specified in the extended control command set (ECCS). The device configuration commands shall include command type (CmdType), command serial number (SN), device code (DeviceID) and subcommand, and are carried in the message body by the MESSAGE method. + +The target shall reply with a 200 OK response immediately after receiving a MESSAGE, and the 200 OK response has no message body. + +##### b) Response command message body + +The device configuration response commands shall include command type (CmdType), command serial number (SN), device code (DeviceID) and executive result (Result), and are carried in the message body by the MESSAGE method. + +Device configuration response commands are specified in the ECCS. For a detailed description, see the device configuration response commands in clause A.2.6 of [ITU-T H.627]. + +The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml. + +The target shall reply with a 200 OK response immediately after receiving a MESSAGE, and the 200 OK response has no message body. + +## 8.4 Device information query + +With reference to [ITU-T H.627], the device information query is specified in clauses 8.4.1 and 8.4.2 as follows: + +### 8.4.1 Basic requirements + +- The source sends the information query commands to the target, and the target shall reply with the result to the source through the query response commands. The information query commands of the device include the basic device information query command, device capacity query command, computation resource query command and intelligent application function query command. +- The device information query and response are both achieved by the MESSAGE method specified in [IETF RFC 3428]. +- The sources include MFS, AFS, and SCFS, and the targets include other function sets in the FDIS. + +### 8.4.2 Signalling process + +For the device information query signalling flow, see Figure 8. + +![Sequence diagram showing the signalling flow of device information query between Source, MFS, and Target.](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +``` +sequenceDiagram + participant Source + participant MFS + participant Target + Note right of Target: H.626.8(25) + + Source->>MFS: 1. MESSAGE (Device information query command) + MFS-->>Source: 2: 200 OK + MFS->>Target: 3. MESSAGE (Device information query command) + Target-->>MFS: 4: 200 OK + MFS->>Target: 5. MESSAGE (Device information query response command) + Target-->>MFS: 6: 200 OK + MFS->>Source: 5. MESSAGE (Device information query response command) + Source-->>MFS: 6: 200 OK +``` + +The diagram illustrates the signalling flow for a device information query involving three entities: Source, MFS (Message Forwarding System), and Target. The interaction proceeds as follows: 1. The Source sends a MESSAGE (Device information query command) to the MFS. 2. The MFS responds with a 200 OK. 3. The MFS then forwards the MESSAGE (Device information query command) to the Target. 4. The Target responds with a 200 OK. 5. The MFS receives the response from the Target and sends a MESSAGE (Device information query response command) to the Target. 6. The Target responds with a 200 OK. 7. Finally, the MFS sends the MESSAGE (Device information query response command) to the Source, which responds with a 200 OK. A label 'H.626.8(25)' is present in the bottom right corner of the diagram area. + +Sequence diagram showing the signalling flow of device information query between Source, MFS, and Target. + +**Figure 8 – Signalling flow of device information query** + +The signalling flow description is as follows: + +- The source sends the device information query commands to the MFS, and the device information query commands are carried in the message body by the MESSAGE method. +- The MFS replies with a 200 OK response after receiving the commands. +- The MFS forwards the device information query commands to the target, and the device information query commands are carried in the message body by the MESSAGE method. +- The target replies with a 200 OK response after receiving the commands. + +- The target sends the device information query response commands to the MFS, and the device information query response commands are carried in the message body by the MESSAGE method. +- The MFS replies with a 200 OK response after receiving the commands. +- The MFS forwards the query response commands to the source, and the device information query response commands are carried in the message body by the MESSAGE method. +- The target replies with a 200 OK response after receiving the commands. + +## 8.5 Status information reporting + +With reference to [ITU-T H.627], the status information reporting is specified in clauses 8.5.1, 8.5.2 and 8.5.3 as follows: + +### 8.5.1 Basic requirements + +- If the source, including any function set in the FDIS, is found to be working abnormally, status information shall be sent to the MFS immediately. If there is no abnormality, status information shall be sent to the MFS regularly. The source should carry the descriptive information of the faulty subdevice in the status information. Status information reporting is achieved by the MESSAGE method specified in [IETF RFC 3428]. +- The heartbeat mechanism is to indicate the normal status or to synchronize with other parts of the system by sending a periodic signal, so as to maintain the connection. +- The source and MFS shall configure a unified heartbeat interval parameter, and send heartbeat messages according to the heartbeat interval regularly, with the default heartbeat interval being 60 seconds. The source and MFS shall configure a unified number of heartbeat timeout parameters. If the count of successive heartbeat message timeouts reaches the number of heartbeat timeouts, the other side is considered to be offline, with the default number of heartbeat timeouts being three. +- If the heartbeat receiver detects that the count of successive timeouts of the heartbeat message reaches the agreed number while the heartbeat sender is online, the heartbeat sender is considered to be offline. If the heartbeat sender detects that the count of successive timeouts of the heartbeat message response reaches the agreed number while the heartbeat receiver is online, the heartbeat receiver is considered to be offline. + +### 8.5.2 Signalling process + +For the status information reporting signalling flow, see Figure 9. + +![Sequence diagram showing the signalling flow of status information reporting between a Source and an MFS. The Source sends a '1. MESSAGE (Status information reporting)' to the MFS, and the MFS responds with '2. 200 OK'.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` + +sequenceDiagram + participant Source + participant MFS + Note right of MFS: H.626.8(25) + Source->>MFS: 1. MESSAGE (Status information reporting) + MFS-->>Source: 2. 200 OK + +``` + +Sequence diagram showing the signalling flow of status information reporting between a Source and an MFS. The Source sends a '1. MESSAGE (Status information reporting)' to the MFS, and the MFS responds with '2. 200 OK'. + +**Figure 9 – Signalling flow of status information reporting** + +The signalling flow description is as follows: + +- The source sends the device status information reporting commands to the MFS, and the device status information reporting commands are carried in the message body by the MESSAGE method. +- The MFS replies with a 200 OK response after receiving the commands. + +### 8.5.3 Protocol interface + +The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml. + +The status information reporting commands shall include command type (CmdType), device/FDIS ID (DeviceID) and normal operation or not (Status), and are carried in the message body by the MESSAGE method. + +Both success and error responses of MESSAGE have no message body. + +## 8.6 Historical feature file retrieval + +With reference to [ITU-T H.627], the historical feature file retrieval is specified in clauses 8.6.1, 8.6.2 and 8.6.3 as follows: + +### 8.6.1 Basic requirement + +- File retrieval mainly uses the criteria of area, device, recording time period, place of recording and content of recording for query. MESSAGE is used to send the retrieval request and the query result. + +### 8.6.2 Signalling process + +For the historical feature file retrieval signalling flow, see Figure 10. + +![Sequence diagram showing the signalling flow of historical feature file retrieval between a Source and a Target. The flow consists of four steps: 1. Source sends MESSAGE (File directory query) to Target; 2. Target responds with 200 OK; 3. Target sends MESSAGE (File directory) to Source; 4. Source responds with 200 OK. The diagram is labeled H.626.8(25).](7ede87328f6b696dcffa65ebc4570cc8_img.jpg) + +``` +sequenceDiagram + participant Source + participant Target + Note left of Source: H.626.8(25) + Source->>Target: 1. MESSAGE (File directory query) + Target-->>Source: 2. 200 OK + Target->>Source: 3. MESSAGE (File directory) + Source-->>Target: 4. 200 OK +``` + +Sequence diagram showing the signalling flow of historical feature file retrieval between a Source and a Target. The flow consists of four steps: 1. Source sends MESSAGE (File directory query) to Target; 2. Target responds with 200 OK; 3. Target sends MESSAGE (File directory) to Source; 4. Source responds with 200 OK. The diagram is labeled H.626.8(25). + +**Figure 10 – Signalling flow of historical feature file retrieval** + +The sources include MFS, AFS or operation function set (OFS) and the targets include DPFS. + +The signalling flow description is as follows: + +- The source sends the directory query request MESSAGE to the target, and the message body contains the historical media file retrieval criteria. +- The target sends a 200 OK response to the source, without a message body. +- The target sends the query results to the source, and the message body contains the file directory; when one MESSAGE is unable to send all query results, they are sent with multiple messages. +- The source sends a 200 OK response to the target, without a message body. + +### 8.6.3 Protocol interface + +The detailed specification of the SIP message header field (such as To, From, Cseq, Call-ID, Max-Forwards and Via) complies with the provisions of the IETF RFC document of the relevant SIP message. + +## 8.7 Time calibration + +With reference to [ITU-T H.627], the time calibration is specified in clauses 8.7.1, 8.7.2 and 8.7.3 as follows: + +### 8.7.1 Basic requirement + +– The devices support the network time calibration function based on the SIP or network time protocol (NTP) method, and the standard time is coordinated universal time (UTC). For time calibration based on the SIP method, see the specific description in this clause; for the unified network time calibration service based on NTP, see [IETF RFC 5905]. The network time calibration devices include the clock source and the client, supporting the working mode of the client or server; the clock source shall support TCP or IP, user datagram protocol (UDP) and NTP, and the input or self-produced time signals are output in the standard NTP IP format. + +### 8.7.2 Signalling process + +SIP time calibration is finished in the registration process, see clause 8.1.2.1. + +### 8.7.3 Protocol interface + +The Date header field in the final SIP response message 200 OK of the registration process carries the time information under the condition that the registration succeeded. The adopted format is XML standard format: Date: yyyy-MM-dd'T'HH:mm:ss.SSS. + +If the SIP user agent (UA) performs time calibration with the registration method, the expiration time of the registration should be less than the running time that elapses before an error of 1 second occurs between the SIP UA and the control command set (CCS). + +## 8.8 Data preprocessing + +The functional architecture of the FDIS includes a data pre-processing function set between the video/audio sensor function and feature extraction function. + +### 8.8.1 Background frame separation + +Background frame separation is required to reduce the transmission data and improve the machine learning (ML) speed for some intelligent video sensors. + +After obtaining the frame rate and duration of the original video frame sequence, the sampling interval for the original video frame sequence is determined based on the frame rate and duration. Then frames are sampled from the original video frame sequence at regular intervals depending on the sampling interval and generating the reference frame sequence. + +Determine the pixel value differences for each frame sequence where the position index is greater than 1 relative to the initial reference frame in the reference frame sequence. Then determine at least one frame difference map for each target reference frame relative to the initial reference frame based on the absolute values of these differences. + +Perform greyscale processing on the frame difference map to obtain a greyscale frame difference map. After obtaining the binarization threshold, adjust the greyscale values of the greyscale frame difference map to obtain a binary frame difference map. Subsequently, generate a background mask based on the binary frame difference map and perform denoising processing, ensuring that the background region is smaller than, or equal to, the background region of each respective binary frame difference map. + +Finally, extract the video background frames corresponding to the original video frame sequence based on the background mask, and utilize the video background frames to extract the video foreground frames corresponding to each original video frame within the original video frame sequence. + +## 8.9 Feature stream generation and processing + +### 8.9.1 Feature extraction and concatenation + +The procedure includes a feature extraction network, a feature fusion structure and a post-feature transformation module. The coding structure of the neural network architecture includes a front encoding module, a post-encoding module, a front decoding module and a post-decoding module. + +To generate restored image features, the restored feature map is created by splitting it into feature maps of similar scales. The procedure includes acquiring multiple image features from the target image, where these features are extracted at different scales through a feature extraction network. These multiple image features are then fused using a feature fusion structure in a neural network architecture to produce a fused feature map. Next, the fused feature map is encoded using the encoding structure of the neural network architecture to obtain the encoded features of the target image. + +During the process, fused features are firstly transformed using the front feature transformation module in the neural network, resulting in prior features. These prior features are then further processed using the post-feature transformation module to obtain hyperprior features. + +The obtained hyperprior features from the post-feature transformation module are encoded using the post-encoding module, generating a hyperprior encoding stream. + +The hyperprior encoding stream is subsequently decoded by the post-decoding module of the neural network, producing hyperprior decoding features. The hyperprior decoding features are processed through a feature refinement network, gaining the refined hyperprior decoding features. The post feature transformation module then simultaneously processes both the prior features obtained from the front feature transformation module, and refined hyperprior decoding features through the front encoding module, resulting in the prior encoding stream. The final encoded features are obtained based on both the front and post-encoding streams. + +The front decoding module of the neural network is used to decode the encoding features of the target images, resulting in a restored feature map. This decoding process involves decoding the prior encoding stream using the front decoding module to obtain prior decoding features. Subsequently, the prior decoding features are processed through the final feature transformation module of the neural network to generate the restored image feature map. + +![Flowchart illustrating the procedure of feature extraction and concatenation. The process starts with an input arrow pointing to a 'Feature extraction network'. This network outputs to a 'Feature fusion network', which in turn outputs to a 'Front feature transformation module'. This module outputs to a 'Post feature transformation module'. The 'Post feature transformation module' outputs to a 'Front encoding module', which outputs to a 'Front decoding module'. The 'Front decoding module' outputs to a 'Feature refinement network', which outputs to a 'Post decoding module'. The 'Post decoding module' outputs to an output arrow. There are also arrows from the 'Feature fusion network' to the 'Post encoding module', and from the 'Post encoding module' to the 'Post decoding module'.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg) + +``` +graph TD; Input(( )) --> FEN[Feature extraction network]; FEN --> FFN[Feature fusion network]; FFN --> FFM[Front feature transformation module]; FFM --> PFM[Post feature transformation module]; PFM --> FEM[Front encoding module]; FEM --> FDM[Front decoding module]; FDM --> FRN[Feature refinement network]; FRN --> PDM[Post decoding module]; PDM --> Output(( )); FFN --> PEM[Post encoding module]; PEM --> PDM; +``` + +Flowchart illustrating the procedure of feature extraction and concatenation. The process starts with an input arrow pointing to a 'Feature extraction network'. This network outputs to a 'Feature fusion network', which in turn outputs to a 'Front feature transformation module'. This module outputs to a 'Post feature transformation module'. The 'Post feature transformation module' outputs to a 'Front encoding module', which outputs to a 'Front decoding module'. The 'Front decoding module' outputs to a 'Feature refinement network', which outputs to a 'Post decoding module'. The 'Post decoding module' outputs to an output arrow. There are also arrows from the 'Feature fusion network' to the 'Post encoding module', and from the 'Post encoding module' to the 'Post decoding module'. + +Figure 11 – The procedure of feature extraction and concatenation + +### 8.9.2 Feature for image reconstruction task + +The functional architecture of the FDIS includes the front-end function set and data processing function set to process feature information. The data processing function can receive the feature extracted from the ML backbone network in the front-end function set. The feature has abundant edge, texture and semantic information. In one aspect, it can be further processed for intelligent video, audio and natural language processing (NLP) algorithms. It can also be sent into an image reconstruction network for processing the feature information and obtaining the reconstructed images. The parameters of the feature extraction network and image reconstruction network are trained through the sample images based on the feature task annotation and prediction. + +The sample images with annotation are processed through the deep learning network of machine vision to get the prediction of the feature tasks. The deep learning network includes a preprocessing network, feature extraction network, feature tasks network sequentially. + +The following steps are needed for image reconstruction tasks: + +- Process the sample image through the preprocessing network to obtain the preprocessing output. +- Process the preprocessing output through the trained feature extraction network to obtain the image features. + +NOTE 1 – The feature extraction network includes a convolution unit, normalisation unit, and activation unit. + +- Process the features through the feature encoding module to obtain the feature encoding bitstream. +- Process the feature encoding bitstream through the feature decoding module to obtain the decoding features. +- Process the image features through the image reconstruction network to obtain the reconstructed sample images. + +NOTE 2 – The image reconstruction network includes an image reconstruction unit, sample post processing unit and upsampling unit. The post-processing unit and preprocessing unit maintain the consistent processing methods. The upsampling ratio is the same as the downsampling ratio in the feature extraction network. + +Train the parameters of the image reconstruction network based on the reconstructed images and sample images. + +### 8.9.3 Feature for machine vision task + +The feature has abundant edge, texture and semantic information. It can be further processed for machine vision tasks. + +The following steps to obtain the annotation of feature tasks for sample images are needed for machine vision tasks: + +- Process the sample image through the preprocessing network to obtain the preprocessing output. +- Process the preprocessing output through the feature extraction network to obtain the extracted features of images. +- Process the features through the feature encoding module to obtain the feature encoding bitstream. +- Process the feature encoding bitstream through the feature decoding module to obtain the decoding features. +- Process the decoding features through the feature tasks network to obtain the feature tasks prediction. + +Train the parameters of the feature extraction network based on the annotation of feature tasks and the prediction of feature tasks and adjust the parameters of the machine vision deep learning network including the feature extraction network. + +# Appendix I + +## Examples of workflows and relevant protocols + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Device information query command example + +``` + + + + + + + + +``` + +# Bibliography + +- [b-ITU-T F.743] Recommendation ITU-T F.743 (V2) (2019), *Requirements and service description for video surveillance.* +- [b-ITU-T G.711] Recommendation ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies.* +- [b-ITU-T G.723.1] Recommendation ITU-T G.723.1 (2006), *Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s.* +- [b-ITU-T G.729] Recommendation ITU-T G.729 (2012), *Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP).* +- [b-ITU-T H.264] Recommendation ITU-T H.264 (V15) (2024), *Advanced video coding for generic audiovisual services.* +- [b-ITU-T H.265] Recommendation ITU-T H.265 (V10) (2024), *High efficiency video coding.* +- [b-ITU-T K.142] Recommendation ITU-T K.142 (2019), *Lightning protection and earthing of video surveillance systems.* + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73fba86b29f27c1ecf2bfef6535bbc46d8d7cf98 --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:196d2058426af78d0e20639c7f500bd2dfe48d033371c1174f5a19a4e6f03425 +size 53841 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c2a078e75aee188b5860a5d3fa2bae365bdd0fb --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5d5cababb793a3d6a3abb67982b7646db08d5811fb67852a77a6972472814a9 +size 133541 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e476a92c8f109ae04fb45d7ebcca875f6bd4e54 --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b9ca350a70f88b83723ef49ca9c4ffce49ca9e145eafe6e7482d95d7f81e3b0 +size 22815 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aec757b54600aadac4c74118f435ba45174656de --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dc339dcb9c78982095cc51beea3c74360a63e1b2a4be208f5281938e1e480e2 +size 21685 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4b08dc607db8ee0332382a032be693ce28f3db5 --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d8e42b4d5646d595d9fc46ebf44257a76e497d37350cde45eb32e82ee1a7ee1 +size 68438 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74341c3bf9cc076871338c8d35ece3d8d109f418 --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc7e30fef959d172048fd0d367207113a43cff3992bb40f7b83483b6570fbdd1 +size 128263 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b1a429975c858a7f6f80e7572e9531b63026f86 --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd9a0b856134de4f5fa22aa7fa5d4ea50603ee5136b74e2db04d107716727031 +size 65730 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3cfd00308931eca9cc00782d2d21ea840cf4914 --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fec4ceb936ccdf4c537c8976e3c9103a66bec92c98ba7338a9745a8f0edaece +size 75241 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/H/T-REC-H.627.1-201703-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3628fa239944c88dff609f31bcb88608b48c064 --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a24dae1ce9f05d337ad07a6db0954b241dbf029981dc3fd1a4f6056e5de5291d +size 21945 diff --git a/marked/H/T-REC-H.627.1-201703-I_PDF-E/raw.md b/marked/H/T-REC-H.627.1-201703-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..55a5891b7b5e45685d4bfb0c2af3b1c1b91d260d --- /dev/null +++ b/marked/H/T-REC-H.627.1-201703-I_PDF-E/raw.md @@ -0,0 +1,1379 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.627.1** + +(03/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Broadband, triple-play and advanced multimedia +services – Advanced multimedia services and applications + +# --- **Protocols for mobile visual surveillance** + +Recommendation ITU-T H.627.1 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global connectivity and telecommunications. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo + +International +Telecommunication +Union + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.627.1 + +# Protocols for mobile visual surveillance + +## Summary + +Recommendation ITU-T H.627.1 describes the detailed specification of reference points, message flows control methods and overall protocols of a mobile visual surveillance system based on the requirements described in Recommendation ITU-T F.743 and functional architecture described in Recommendation ITU-T H.626.1. + +This Recommendation focuses on the protocols of a visual surveillance system with mobile units and the services related to mobile units, such as a mobile customer unit accessing real-time video stream from a visual surveillance system. This Recommendation defines reference points, message syntax and semantics and relevant protocols. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.627.1 | 2017-03-01 | 16 | 11.1002/1000/13191 | + +## Keywords + +Message flows, mobile visual surveillance, protocols, reference points. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 4 | +| 6 Message syntax and semantics ..... | 4 | +| 6.1 Reference point Cms: CMU-MSP ..... | 5 | +| 6.2 Reference point Msm: MSP-M_CU ..... | 10 | +| 6.3 Reference point Psm: M_CU- PSS..... | 13 | +| 6.4 Reference point Vm: M_CU- VAU ..... | 15 | +| 6.5 Reference point Mv: M_CU-VAU ..... | 17 | +| 6.6 Reference point Vp: VAU-PSS ..... | 19 | +| 6.7 Reference points Mdv/Pv/Vs:VAU-VS system ..... | 21 | +| 7 Message flows ..... | 21 | +| 7.1 Real-time video/audio acquisition..... | 21 | +| 7.2 Recording and playback ..... | 22 | +| 7.3 PTZ control..... | 26 | +| 7.4 Resource query ..... | 27 | +| 7.5 Service management..... | 28 | +| Bibliography..... | 30 | + + + +# Recommendation ITU-T H.627.1 + +# Protocols for mobile visual surveillance + +# 1 Scope + +This Recommendation focuses on the protocols of a visual surveillance system with mobile units and the services related to mobile units, such as a mobile customer unit accessing real-time video stream from a visual surveillance system. + +This Recommendation defines the reference points and focuses on the protocols for a mobile visual surveillance system, based on the architecture defined in [ITU-T H.626.1]. + +Furthermore, this Recommendation utilizes and extends some existing protocols such as session initiation protocol (SIP), real-time transport protocol (RTP), real-time streaming protocol (RTSP) and hypertext transfer protocol (HTTP) and also defines the message format and text. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T F.743] Recommendation ITU-T F.743 (2009), *Requirements and service description for visual surveillance*. +- [ITU-T H.626] Recommendation ITU-T H.626 (2011), *Architectural requirements for visual surveillance*. +- [ITU-T H.626.1] Recommendation ITU-T H.626.1 (2013), *Architecture for mobile visual surveillance*. +- [ITU-T H.627] Recommendation ITU-T H.627 (2012), *Signalling and protocols for visual surveillance*. +- [IETF RFC 3261] IETF RFC 3261 (2002), *SIP: Session Initiation Protocol*. +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- [IETF RFC 7231] IETF RFC 7231 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content*. +- [IETF RFC 7826] IETF RFC 7826 (2016), *Real-Time Streaming Protocol Version 2.0*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 application** [b-ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services. + +**3.1.2 customer** [b-ITU-T M.60]: A customer is an entity which receives services offered by a service provider based on a contractual relationship. It may include the role of a network user. + +**3.1.3 customer unit** [ITU-T H.626]: A device located at the customer part of a visual surveillance system and used to present multimedia information (such as audio, video, image, alarm signal, etc.) to the end user. + +**3.1.4 functional architecture** [b-ITU-T Y.2012]: A set of functional entities and the reference points between them used to describe the structure of an NGN. These functional entities are separated by reference points, and thus they define the distribution of functions. + +NOTE – The functional entities can be used to describe a set of reference configurations. These reference configurations identify which reference points are visible at the boundaries of equipment implementations and between administrative domains. + +**3.1.5 interface** [b-ITU-T Y.101]: A shared boundary between two functional units. + +**3.1.6 media** [b-ITU-T Y.101]: Plural of medium. + +**3.1.7 medium** [b-ITU-T Y.101]: Specific physical support for transmission or storage of information. Type of presentation of information (i.e., video, audio, text, etc.). + +**3.1.8 mobile customer unit (M\_CU)** [ITU-T H.626.1]: Mobile client software installed in customers' mobile devices. The M\_CU is used to initiate the service and provide customers with video viewing. + +**3.1.9 mobile service portal (MSP)** [ITU-T H.626.1]: A series of devices and subsystems located at the central part of a mobile visual surveillance system. The MSP is the business application platform of the mobile visual surveillance system. Its main functions include a unified access entrance to the business entrance of user authentication and the display list of users' monitoring permissions. The MSP can carry out user authentication, query the list of monitoring permissions, synchronize user account information, and assist service management through the exchange of information with the centre management unit (CMU). + +**3.1.10 reference point** [b-ITU-T Y.2012]: A conceptual point at the conjunction of two non-overlapping functional entities that can be used to identify the type of information passing between these functional entities. + +NOTE – A reference point may correspond to one or more physical interfaces between pieces of equipment. + +**3.1.11 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications. + +**3.1.12 packet-switched streaming service (PSS)** [ITU-T H.626.1]: A device located at the central part of a mobile visual surveillance system. The PSS is the stream media server and processes media stream distribution between the M\_CU and the VAU. The main functions of PSS include responding to the service request message sent by M\_CU, getting the real-time media stream from VAU and distributing the stream to multiple M\_CUs. + +**3.1.13 premises unit** [ITU-T H.626]: A device located at the remote part of a visual surveillance system and used to capture multimedia information (such as audio, video, image, alarm signal, etc.) from a surveilled object. + +**3.1.14 video access unit (VAU)** [ITU-T H.626.1]: A device located at the central part of a mobile visual surveillance system. The VAU is used to implement communication between the mobile customer unit (M\_CU) and the units defined in [ITU-T H.626]. The VAU's main functions include: requesting the CMU for scheduling information to be used to establish the media session between the media distribution unit (MDU) and the packet-switched streaming service (PSS), processing requests from the agent mobile customer unit for control of pan/tilt/zoom (PTZ) and distributing and transcoding multimedia data. + +**3.1.15 visual surveillance** [ITU-T H.626]: A telecommunication service focusing on video (but including audio) application technology, which is used to remotely capture multimedia (such as audio, video, image, alarm signal, etc.) and present them to the end user in a user-friendly manner, based on a managed broadband network with ensured quality, security and reliability. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------------| +| CDMA | Code Division Multi Access | +| CMU | Centre Management Unit | +| CU | Customer Unit | +| GW | Gateway | +| HTTP | HyperText Transfer Protocol | +| ID | Identification | +| IP | Internet Protocol | +| IPC | IP Camera | +| M_CU | Mobile Customer Unit | +| MDN | Mobile Directory Number | +| MDU | Media Distribution Unit | +| MIB | Management Information Base | +| MSP | Mobile Service Portal | +| NGN | Next Generation Network | +| NVR | Network Video Recorder | +| PSS | Packet-switched streaming service | +| PTZ | Pan/Tilt/Zoom | +| PU | Premises Unit | +| PUID | Premises Unit Identifier | +| R/W | Read/Write | +| RTCP | Real-time Transport Control Protocol | +| RTP | Real-time Transport Protocol | +| RTSP | Real-time Streaming Protocol | +| SCU | Service Control Unit | +| SIP | Session Initiation Protocol | +| SOAP | Simple Object Access Protocol | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | +| URL | Uniform Resource Locator | + +| | | +|-------|-------------------------------------| +| UTF-8 | 8-bit Unicode Transformation Format | +| VAU | Video Access Unit | +| VS | Visual Surveillance | +| WAP | Wireless Application Protocol | +| XML | Extensible Markup Language | + +# 5 Conventions + +In this Recommendation, "String" is a data type used to describe a sequence of characters in UTF-8 format. "Integer" is a datum of integral data type that represents an 8-bit subset of mathematical integers. + +# 6 Message syntax and semantics + +[ITU-T H. 626.1] describes the overall architectural framework of mobile visual surveillance as shown in Figure 6-1 and it also introduces reference points of the architecture. This Recommendation gives a more detailed description of these reference points. + +![Functional architecture framework of mobile visual surveillance diagram showing components CMU, MSP, SCU, MDU, MSU, M_CU, VAU, PU, and CU with their interconnections for media, control, and management.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +The diagram illustrates the functional architecture framework of mobile visual surveillance. It consists of several functional blocks and their interconnections: + +- CMU (Central Management Unit)**: Located at the top, it connects to **MSP** (via **Cms**), **SCU** (via **Dm**, **Sc**, **Sm**, **Dm'**), and **CU** (via **Cm**). +- MSP (Mobile Service Platform)**: Connects to **M\_CU** (via **Msm**). +- SCU (Service Control Unit)**: Connects to **MDU** (via **Sd**, **Sd'**), **MSU** (via **Cs**), and **CU** (via **Cm**). +- MDU (Media Distribution Unit)**: Connects to **VAU** (via **Mdv**, **Mp**), **MSU** (via **Ds**, **Ds'**), **PU** (via **Pd**), and **CU** (via **Cd**, **Mc**). +- MSU (Media Storage Unit)**: Connects to **CU** (via **Cd'**, **Mc'**). +- M\_CU (Mobile Client Unit)**: Connects to **VAU** (via **Vm**, **Mv**). +- VAU (Video Access Unit)**: Connects to **PU** (via **Pv**). +- PU (Processing Unit)**: Connects to **CU** (via **Pc**, **Pc'**). +- CU (Central Unit)**: The central processing hub, receiving inputs from **CMU**, **SCU**, **MDU**, **MSU**, **VAU**, and **PU**. + +**Legend:** + +- Media**: Solid black line +- Control**: Solid red line +- Management**: Dashed blue line + +Reference points are indicated by labels on the interfaces: **Cms**, **Msm**, **Mv**, **Vm**, **Psm**, **Vs**, **Mdv**, **Pv**, **Pm**, **Dm**, **Sc**, **Sm**, **Dm'**, **Cm**, **Sd**, **Sd'**, **Cs**, **Ds**, **Ds'**, **Cd**, **Mc**, **Cd'**, **Mc'**, **Pc**, **Pc'**. + +Functional architecture framework of mobile visual surveillance diagram showing components CMU, MSP, SCU, MDU, MSU, M\_CU, VAU, PU, and CU with their interconnections for media, control, and management. + +**Figure 6-1 – Functional architecture framework of mobile visual surveillance** + +The interfaces and protocols involved in mobile video surveillance are listed as follows: + +- 1) Reference point **Cms**: CMU-MSP, uses the Web service interface protocol (SOAP/HTTP) +- 2) Reference point **Msm**: MSP-M\_CU, uses the HTTP protocol +- 3) Reference point **Mv**: M\_CU-VAU, uses the user datagram protocol (UDP) communication protocol +- 4) Reference point **Vm**: VAU-M\_CU, uses the HTTP/RTSP, RTP/RTCP protocol +- 5) Reference point **Psm**: PSS-M\_CU, uses the HTTP/RTSP, RTP/RTCP protocol +- 6) Reference point **Vs**: VAU-SCU, uses the HTTP protocol +- 7) Reference point **Mdv**: MDU-VAU, uses the RTP/RTCP protocol +- 8) Reference point **Pv**: PU-VAU, uses the RTP/RTCP protocol + +- 9) Reference point Vp: VAU-PSS, uses the RTSP protocol. + +## 6.1 Reference point Cms: CMU-MSP + +### 6.1.1 Interface functions + +Reference point Cms is between the centre management unit (CMU) and the mobile service portal (MSP). This interface is used for querying the attributes of the surveillance points when the users log in and to query the information of all surveillance points available for mobile surveillance service: + +- User authentication and surveillance point query: When a user logs into the mobile service portal (MSP) using M\_CU, the MSP gets the User ID and password of the current user (if the user chooses the universal sign-in way, the MSP needs to translate the mobile directory number (MDN) number into the corresponding User ID and password locally), then the MSP authenticates the user to the centre management unit (CMU) of the video surveillance platform via the User ID and password. If authentication fails, the failed message is returned. If it succeeds, the CMU will query the surveillance point information according to the current User ID, the CMU returns the corresponding surveillance point and parameter list under the User ID in the MSP. +- Query the enterprise surveillance points attribution: When an enterprise user logs into the Enterprise Self-Service system through the MSP, the MSP gets the relevant information of the current surveillance point list that the enterprise has activated on the CMU video surveillance platform through the enterprise account. +- RTSP media stream entrance query: When a user queries certain kinds of media streaming from a surveillance point, the CMU returns the RTSP access address that the user gets through internal query scheduling on the platform. + +NOTE – Access to the media requires the access token. + +An authorized user requests resources according to the original interface specification, called "reqUserChannelInfo". + +### 6.1.2 Interface protocols + +This interface uses IP protocol and the Web service interface protocol (SOAP/HTTP). + +### 6.1.3 Message format + +#### 1) The enterprise attribute information query + +The MSP queries the enterprise attribute information according to the corporate identity (customerID) with the parameters indicated in Table 6.1-1. The parameters returned are found in Table 6.1-2. + +**Table 6.1-1 – Interface: MSP→CMU** + +| MSP-CMU interface parameters | | | | +|------------------------------|----------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| CustomerId | Enterprise ID | String | Telecom administrator manually input when the MSP service opened (18 bits). The first six bits of customerID refer to the domain ID (platform domain). | + +**Table 6.1-2 – Interface: CMU→MSP** + +| MSP-CMU interface parameters | | | | +|-------------------------------------|----------------------------------|------------------|-----------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| CustomerName | Customer names | String | | +| CustomerType | Customer type | Integer | Only : Enterprise:1 | +| Address | Customer address | String | | +| PhoneNumber | Customer phone number | String | | +| Fax | Customer fax number | String | | +| ZipCode | Customer zip code | String | | +| Email | Customer E-mail | String | | +| TransactPerson | The operator | String | | +| AdminAccount | Video surveillance admin account | String | | +| ResultCode | Return code | Integer | 0 if enterprise ID does not exist
    1 for access success | + +NOTE – The user uses "adminAccount prefix" to login to the MSP Enterprise Self-Service page, the user ID and user account are in the same format. + +#### **2) Search enterprise information list** + +The MSP queries the enterprise attribute information according to the corporate identity (customer ID) or customer name with the parameters listed in Table 6.1-3. The returned parameters are listed in Table 6.1-4. + +**Table 6.1-3 – Interface: MSP→CMU** + +| MSP-CMU interface parameters | | | | +|-------------------------------------|-----------------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| searchCID | Enterprise ID | String | Telecom administrator manually inputs when the MSP service opened (18). The first six bits of customerID refer to the domain ID (Platform domain). | +| searchCN | Enterprise name | String | Company name | + +**Table 6.1-4 – Interface: CMU→MSP** + +| MSP-CMU interface parameters | | | | +|-------------------------------------|-----------------------|------------------|---------------------| +| Parameter | Parameter name | Data type | Notes | +| CustomerName | Customer names | String | | +| CustomerType | Customer type | Integer | Only : Enterprise:1 | +| Address | Customer address | String | | +| PhoneNumber | Customer phone number | String | | +| Fax | Customer fax number | String | | + +**Table 6.1-4 – Interface: CMU→MSP** + +| MSP-CMU interface parameters | | | | +|-------------------------------------|----------------------------------|------------------|--------------| +| Parameter | Parameter name | Data type | Notes | +| ZipCode | Customer zip code | String | | +| Email | Customer E-mail | String | | +| TransactPerson | The operator | String | | +| AdminAccount | Video surveillance admin account | String | | + +NOTE – User uses "adminAccount prefix" to login to the MSP Enterprise Self Service page, the user ID and user account use the same format. + +#### **3) Accept MSP user authentication** + +The CMU accepts the MSP user authentication, including the user's login through a mobile phone and the enterprise administrator with the parameters listed in Table 6.1-5. The returned parameters are listed in Table 6.1-6. + +**Table 6.1-5 – Interface: MSP→CMU** + +| MSP-CMU interface parameters | | | | +|-------------------------------------|-----------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| Account | User account | String | "username@userdomain", which is the account is the MSP user account or the enterprise administrator accounts which has been previously processed
    NOTE – When the corresponding video surveillance platform does not have the customer domain, only need to fill in the user name. | +| Password | User password | String | Mandatory, 32 uppercase characters for MD5 coding of password, such as: "96E79218965EB72C92A549DD5A330112" | +| AccountType | User account type | Integer | 0 for a user
    1 for enterprise administrator | + +**Table 6.1-6 – Interface: CMU→MSP** + +| MSP-CMU interface parameters | | | | +|-------------------------------------|-----------------------|------------------|--------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| Authorization | Certification results | Integer | 0 for failure, 1 for success | +| The following list of fields | | | | +| CategoryID | Catalogue number | String | | +| CategoryName | Catalogue name | String | | +| PID | The parent ID | String | PID is the parent directory of the CategoryID. The value is null when CategoryID is the root directory | + +#### 4) User account query by the customer + +The enterprise administrator queries for the list of all user accounts opened by the enterprise with the parameters listed in Table 6.1-7. The returned parameters are listed in Table 6.1-8. + +**Table 6.1-7 – Interface: MSP→CMU** + +| MSP-CMU interface parameters | | | | +|------------------------------|----------------|-----------|---------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| CustomerId | Enterprise ID | String | The first six bits of customerID refer to the domain ID | + +**Table 6.1-8 – Interface: CMU→MSP** + +| MSP-CMU interface parameters | | | | +|------------------------------|----------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| ResultCode | Return code | Integer | 0 if enterprise ID does not exist
    1 for success | +| Account | User account | String | "username@userdomain"
    NOTE – When the corresponding video surveillance platform does not contain the customer domain, only the user name is used. | + +#### 5) Attribution query of the common surveillance point user + +A query for the authorized surveillance list under the specific user account is sent using the parameters listed in Table 6.1-9. The returned parameters are listed in Table 6.1-10. + +**Table 6.1-9 – Interface: MSP→CMU** + +| MSP-CMU interface parameters | | | | +|------------------------------|------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| Account | User account | String | "username@userdomain", which is the MSP user account which has previously been processed
    NOTE – When the corresponding video surveillance platform does not contain the customer domain, only the user name is used. | +| Password | User password | String | Mandatory, 32 uppercase characters for MD5 coding of password, such as:
    "96E79218965EB72C92A549DD5A330112" | +| CategoryID | Catalogue number | String | Catalogue numbers is a null value representing the query root directory | + +**Table 6.1-10 – Interface: CMU→MSP** + +| MSP-CMU interface parameters | | | | +|-------------------------------------|-------------------------|------------------|---------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| PuId-ChannelNo | PU Channel Number | String | | +| PuName | PUserName | String | | +| PtzFlag | Control authority flag | Integer | 0: no authorization; 1: authorization | +| PlaybackFlag | Playback authority flag | Integer | 0: no authorization; 1: authorization | +| Online | Online flag | Integer | 0: offline; 1: online | +| ResultCode | Return code | Integer | 0: no user account; 1: success | + +#### **6) Query the VAU and PTZ addresses** + +A query for the RTSP address of video access unit (VAU) entrance and pan/tilt/zoom (PTZ) entrance is sent using the parameters listed in Table 6.1-11. The returned parameters returned from the video surveillance system to MSP are listed in Table 6.1-12. In addition to the VideoPlayUrl VAU/PSS address, the reply also contains the fields in Table 6.1-13. + +**Table 6.1-11 – Interface: reqVauUrlRequest** + +| MSP-CMU interface parameters | | | | +|-------------------------------------|--------------------------------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| Account | User account | String | "username@userdomain"
    NOTE – When the corresponding video surveillance platform does not contain the customer domain, only the user name is used. | +| M_cuIp (Optional) | M_CU's IP address | String | Because VAU can span multiple network deployment. This parameter is provided to CMU and used to determine the return VAU which segment address. By default M_CU fill in 0.0.0.0, CMU returns VAU foreign service public address. | +| Password | User password | String | Mandatory, 32 uppercase characters for MD5 coding of password, such as: "96E79218965EB72C92A549DD5A330112" | +| PuId-ChannelNo | Surveillance point unique identifier | String | | +| PlayMethod | Play type | Integer | 0: Real-time video
    1: Video recording | + +**Table 6.1-12 – Interface: reqVauAddResponse** + +| CMU-MSP interface parameters | | | | +|-------------------------------------|------------------------|------------------|----------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| CMUPtzUrl | CMU PTZ URL address | String | Return CMU PTZ URL address | +| VideoPlayUrl | Direct access entrance | String | Return Direct access entrance URL address (PSS or VAU address) | + +**Table 6.1-13 – VideoPlayUrl parameter fields** + +| Parameter | Parameter name | Data type | Notes | +|----------------|---------------------------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Account | User account | String | "username@userdomain"
    NOTE – When the corresponding video surveillance platform does not contain the customer domain, only the user name is used. | +| PuId-ChannelNo | Unique identifier of the surveillance point | String | | +| PlayMethod | Play type | Integer | 0: real-time video
    (fixed as 0 at present) | +| ExpireTime | Requesting the link failure time | String | 20120406155530
    Year-month-day-hour-min-sec | +| HashToken | MD5 abstract | String | Calculated as the MD5 hash of a string containing user name, password hash, PuID-ChannelNo and ExpireTime, in the form:
    HEX(MD5(Account=xx&Password=HEX(MD5(password))&PuID-ChannelNo=nn&ExpireTime=tt))
    NOTE – Step 1: calculate the MD5 hash of the password and use the hexadecimal uppercase string – HEX(MD5(password)); Step 2: Use the result of step 1 to compose the string "Account=xx&Password=HEX(MD5(password))&PuID-ChannelNo=nn&ExpireTime=tt" (without quotes), then calculate its MD5 hash and use its hexadecimal uppercase string. | + +Hash Token requirements: + +- If the HashToken parameter value in VideoPlayUrl was artificially modified, VAU should deny authentication; +- If the VideoPlayUrl video link request time exceeds the ExpireTime value, the link is invalid; + +However, video streaming could continue to play in the established RTSP media channels, not subject to the ExpireTime time limit. + +## 6.2 Reference point Msm: MSP-M\_CU + +### 6.2.1 Interface functions + +Reference point Psm is between the MSP and the M\_CU. The M\_CU and MSP interface uses Web service interface protocol (SOAP/HTTP), mainly to complete the following functions: + +- Send the service request; realize video surveillance business connecting and authentication through MSP; +- Get control point play entrance; +- Check version. + +### 6.2.2 Interface protocols + +The M\_CU and MSP interface uses the IP protocol and the Web service interface protocol (SOAP/HTTP). + +### 6.2.3 Message format + +Tables 6.2-1 to 6.2-7 describe the message format for M\_CU authentication certification and packet access, MSP-M\_CU, surveillance points list query and response, video surveillance point play entrance query and response and duration statistics for mobile surveillance video. + +**Table 6.2-1 – Parameters for M\_CU authentication certification and packet access** + +| M_CU→MSP | | | | +|------------------|-----------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| Account | User account | String | "username@userdomain" | +| Password | User password | String | Mandatory, 32 uppercase characters for MD5 coding of password, such as:
    "96E79218965EB72C92A549DD5A330112" | +| LoginType | Login type | Integer | 0: Account-password login
    1: Local login | +| Version | M_CU version | String | For example: V1.05.004, larger version needs to be consistent with MSP. If the version of MSP>M_CU that M_CU L / class; if M_CU>MSP version, then prompts the current version of M_CU is too high, please use the low version. | + +**Table 6.2-2 – Return information from MSP to an M\_CU authentication certification and packet access request** + +| MSP→M_CU | | | | +|--------------------|-----------------------|------------------|----------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| Result | Certification results | Integer | 0: Success
    1: User name does not exist
    2: Wrong password
    3: M_CU version too new
    4: M_CU version too old | +| The following list | | | | +| CategoryID | CategoryID | String | | +| CategoryName | CategoryName | String | | +| PID | The parent ID | String | PID is the parent directory of the CategoryID. The value is null when CategoryID is the root directory. | + +**Table 6.2-3 – Parameters for a surveillance points list query** + +| M_CU→MSP | | | | +|------------------|-----------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| M_culp | M_CU's IP address | String | Because VAU can span multiple network deployments. This parameter is provided to CMU and used to determine the return VAU which segment address. By default, M_CU fill in 0.0.0.0, CMU returns VAU foreign service public address. | +| Account | User account | String | "username@userdomain" | +| Password | User password | String | Mandatory, 32 uppercase characters for MD5 coding of password, such as:
    "96E79218965EB72C92A549DD5A330112" | +| CategoryID | Catalogue number | String | Catalogue numbers is a null value representing the query root directory | + +**Table 6.2-4 – Return information for a surveillance point query** + +| MSP→M_CU | | | | +|------------------|------------------------------|------------------|--------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| PuId-ChannelNo | PU number and Channel Number | String | Corresponds to the PU number and channel number. | +| PuProperty | PU ability of PTZ control | Integer | It is the PU ability of PTZ control. If no control ability, default is 0 | +| PuName | Surveillance point name | String | For prompting the user to PU the specific significance in M_CU | +| Online | Online flag | Integer | 0 for offline; 1 for online | + +**Table 6.2-5 –Entrance query parameters for a video surveillance point play** + +| M_CU→MSP | | | | +|------------------|------------------------------|------------------|---------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| Account | User account | String | "username@userdomain" | +| Password | User password | String | Mandatory, 32 uppercase characters for MD5 coding of password, such as:
    "96E79218965EB72C92A549DD5A330112" | +| PuId-ChannelNo | PU number and Channel Number | String | | + +**Table 6.2-6 – Return information to a video surveillance point play entrance query** + +| MSP→M_CU | | | | +|------------------|------------------------|------------------|----------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| CMUPtzUrl | CMU PTZ URL address | String | Return CMU PTZ URL address | +| VideoPlayUrl | Direct access entrance | String | Return Direct access entrance URL address (PSS or VAU address) | + +**Table 6.2-7 – Duration statistics for mobile surveillance video data flow** + +| M_CU→MSP | | | | +|------------------|-----------------------|------------------|------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Notes | +| Account | User account | String | "username@userdomain" | +| Password | User password | String | Mandatory, 32 uppercase characters for MD5 coding of password, such as: "96E79218965EB72C92A549DD5A330112" | +| BRun | Start / end flag | Integer | 0: Start
    1: Process (heartbeat)
    2: Quit | +| NStreamBit | Video data flow | Integer | The unit is Kbyte | +| NStreamTime | Video data time | Integer | The unit is second | + +## 6.3 Reference point Psm: M\_CU- PSS + +### 6.3.1 Interface functions + +Reference point Psm is between the M\_CU and the PSS. + +The interface is used to transmit data through HTTP and RTSP to: + +- Send service request, carrying service and user information +- Establish connection and transmit real-time media stream and real-time video +- Play video according to operations such as pause, continue, forward and other orders. + +### 6.3.2 Interface protocols + +This interface is actually between the terminal and the streaming server. It follows the TCP / IP, RTP / RTSP / RTCP protocol, as shown in Figure 6-2. + +| | | | +|-----|------|------| +| RTP | HTTP | RTSP | +| UDP | TCP | UDP | +| IP | | | + +**Figure 6-2 – Interface protocol** + +### 6.3.3 Message format + +#### 6.3.3.1 HTTP interface + +This interface is realized through the parameters carried by HTTP URL. When a user clicks on the URL generated by the MSP, the parameters listed in Table 6.3-1 are acquired and transferred to PSS without processing. + +See [IETF RFC 7231] for HTTP message. + +**Table 6.3-1 – HTTP parameters from M\_CU to PSS** + +| M_CU→PSS | | | | +|------------------|---------------------------------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Value | +| UserId | User ID | String | | +| PuID-ChannelNo | Unique identification of surveillance point | String | | +| PuProperty | Whether PU has PTZ function | Integer | NOTE – Default value is 0 if PU does not have PTZ function | +| VAUADD | VAU address and PTZ control port | String | Format:
    xxx.xxx.xxx.xxx:xxx(ip: port)
    NOTE – Default value is 0 if PU does not have PTZ function. This parameter is validated only in real-time mode. | + +When a user requests PSS service, the HTTP request format is as follows: + +`http://pssIp:port/service?userid=xx&PuID-ChannelNo=xx&puproperty=xx&vauadd=xx` + +PSS responds to the M\_CU request, and sends the dynamically generated RTSP URL to the end user automatically through html page jumping, the address is as follows: + +``` + + + +``` + +#### 6.3.3.2 RTSP interface + +The RTSP message is for establishment and control of streaming transferring dialog, see [IETF RFC 7826] for details. The RTSP request sent by the M\_CU to the PSS should carry the parameters listed in Table 6.3-2. + +**Table 6.3-2 – RTSP parameters from M\_CU to PSS** + +| M_CU→PSS | | | | +|------------------|---------------------------------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Value | +| UserId | User ID | String | | +| PuID-ChannelNo | Unique identification of surveillance point | String | | +| PlayMethod | Media type | Integer | 0: Real-time
    1: Video record | +| StartTime | Start time of recording | String | Format: 20120406155530
    Year-month-day-hour-min-sec | +| PuProperty | Whether PU has PTZ function | Integer | NOTE – Default value is 0 if PU does not have PTZ function. | +| VAUADD | VAU address and PTZ control port | String | Format:
    xxx.xxx.xxx.xxx:xxx(ip: port)
    NOTE – Default value is 0 if PU does not have PTZ function. This parameter is validate only in realtime mode. | + +**Table 6.3-2 – RTSP parameters from M\_CU to PSS** + +| M_CU→PSS | | | | +|------------------|------------------------------------|------------------|------------------------------------------------------------------------| +| Parameter | Parameter name | Data type | Value | +| hashtoken | For billing authentication request | String | Used by manufactories for anti-stealing-link, not be processed by M_CU | + +Parameters are transmitted through: + +RTSP://localhost:port/service?UserID= XXX & PID= XXX..... + +The server of the RTSP extracts parameters while responding to the request and processes them according to the service logic. + +M\_CU send RTSP requests through VideoPlayUrl CMS querying by MSP. + +This is a sample URL: + +rtsp://VideoPlayUrl/service?Account=xx&PUID-ChannelNo=xx & ExpireTime=xx&HashToken=xx + +## **6.4 Reference point Vm: M\_CU- VAU** + +### **6.4.1 Interface function** + +Reference point Vm is between M\_CU and the video access unit (VAU). + +It is used to transmit the real-time video through RTSP. + +### **6.4.2 Interface protocols** + +This interface uses RTSP protocol, the M\_CU works as the RTSP client, the VAU works as the RTSP server which can be configured freely and the default port is 554. The RTSP message format and parameters are indicated in Tables 6.4-1 and 6.4-2. + +**Table 6.4-1 – Common parameters from M\_CU to VAU** + +| M_CU→VAU | | | | +|------------------|-----------------------|------------------|------------------------------------------| +| Parameter | Parameter name | Data type | Value | +| PlayMethod | Media type | String | 0: Real-time video
    1: Video recording | + +**Table 6.4-2 – Real-time mode parameters from M\_CU to VAU** + +| M_CU→VAU | | | | +|------------------|------------------------------------------------------------------|------------------|--------------| +| Parameter | Parameter name | Data type | Value | +| PuID-ChannelNo | Channel identification, the PUID and channel number in VS system | String | | + +The format of real-time video viewing RTSP URL is as follows: + +rtsp://vauaddress:port/service?PuID-ChannelNo=XXXXXXXXXXXXX-X PlayMethod=0, + +For instance: + +rtsp://172.24.202.190/service?PuID-ChannelNo=320101000200000001-1&PlayMethod=0, + +which refers to accessing the first channel of PU No. 320101000200000001's real-time video stream. + +### **6.4.3 Message format** + +The M\_CU works as the client and the VAU works as the server, the messages are as follows: + +Minimum requirements of client and server basic playback can be found in [IETF RFC 7826]. + +##### **DESCRIBE message** + +- 1) The M\_CU sends DESCRIBE message. +- 2) The VAU returns 200 OK with correct message body to the M\_CU, establishing the session. The message body includes the default video CODEC of the transferred video stream and related profile-level-id, frame rate, frame size and so on. VAU configures the default value. + +##### **SETUP message** + +- 1) The M\_CU sends SETUP message, describing the interface which receives the media streaming. +- 2) The VAU returns 200 OK to the M\_CU, describing the interface which sends the media streaming. + +##### **PLAY message** + +- 1) The M\_CU sends PLAY message. +- 2) The VAU starts to play real-time video or video record. +- 3) The VAU returns 200 OK to M\_CU. +- 4) The VAU starts to send media stream to the M\_CU. + +##### **PAUSE message** + +- 1) The M\_CU sends the correct PAUSE message. +- 2) The VAU pauses the real-time video or video record playing. +- 3) The VAU returns 200 OK to M\_CU. +- 4) The VAU stops sending media stream. + +##### **TEARDOWN message** + +- 1) The M\_CU sends TEARDOWN message. +- 2) The VAU stops the real-time video or video record playing. +- 3) The VAU returns 200 OK to the M\_CU. +- 4) The VAU stops sending media stream. +- 5) The VAU RTSP SOCK stops. + +##### **OPTIONS message** + +- 1) The VAU sends OPTIONS message to the M\_CU (with Session). +- 2) The M\_CU searches for the target Session. +- 3) If the target Session exists, the M\_CU returns 200 OK. If the target Session does not exist, the M\_CU returns 404 error and the VAU disconnects the Session with the CMU and releases the source. + +## 6.5 Reference point Mv: M\_CU-VAU + +### 6.5.1 Interface function + +Reference point Mv is between M\_CU and VAU and it is used to control PTZ when end-users browse real-time video. + +### 6.5.2 Interface protocols + +The communication between the M\_CU and the VAU is according to UDP protocol. The default communication port is 5060. The package for request and response reserves 200 bytes for via fields in the header field of SIP. + +The M\_CU sends the PTZ control messages to VAU without 200 OK response or resend. But if within the specified time period M\_CU does not send the stop message to VAU, VAU will send PTZ stop message to the platform automatically. + +Considering the case where multiple M\_CUs visit one PuID-ChannelNo at the same time, M\_CU will send the PuID-ChannelNo carried by RTSP request to the VAU. The VAU distinguishes PTZ message target devices according to the PTZ message body. + +#### 6.5.2.1 M\_CU + +The M\_CU sends a request and receives a response. When it receives a response, the M\_CU must check the XML file. + +Message\_Type and Sequence\_Number. If the parameter is wrong, the response must be discarded. + +#### 6.5.2.2 VAU + +The VAU should be able to receive a request from any IP address and port and reply to the port from the M\_CU request. + +### 6.5.3 Message format + +The message format follows the following structure: + +``` +generic-message = start-line +*message-header +CRLF +[ message-body ] +``` + +#### 6.5.3.1 start-line + +The start-line is either Request-Line or Status-Line, as follows. + +SIP request: + +``` +Request-Line = Method SP Request-URI SP SIP-Version CRLF +``` + +SIP response: + +``` +Status-Line = SIP-Version SP Status-Code SP Reason-Phrase CRLF +``` + +#### 6.5.3.2 message-header + +Request for message-header: + +``` +INFO sip:xxx +Content-Type: application/global_eye_v10+xml +Content-Length: xxx +To: xxx +From: xxx +CSeq: xxx INFO +Call-ID: xxx +``` + +Max-Forwards: xxx + Via: xxx + Contact: xxx + [CRLF] + +Response to message-header: + +200 OK sip:xxx + Content-Type: application/global\_eye\_v10+xml + Content-Length: xxx + To: xxx + From: xxx + CSeq: xxx INFO + Call-ID: xxx + Max-Forwards: xxx + Via: xxx + Contact: xxx + [CRLF] + +#### 6.5.3.3 Message-body + +PTZ control + +- a) Function: The user platform sends PTZ control messages to another platform. +- b) Message: + +``` + + + + + + +``` + +This message needs no response. + +#### 6.5.3.4 List of codes and parameters + +The list of codes and parameters for PTZ control messages is given in Table 6.5-1. + +**Table 6.5-1 – Codes and parameters for PTZ control messages** + +| | | +|-----------------------|---------------------| +| 1: turn up (1..10) | 11: RESERVED | +| 2: turn down (1..10) | 12: RESERVED | +| 3: turn left (1..10) | 13: RESERVED | +| 4: turn right (1..1) | 14: RESERVED | +| 5: open iris (1..10) | 15: stop | +| 6: close iris (1..10) | 20: scan off | +| 7: zoom in (1..10) | 21: scan on (1..10) | +| 8: zoom out (1..10) | 24: RESERVED | +| 9: focus near (1..10) | 25: RESERVED | +| 10: focus far (1..10) | 26: RESERVED | + +## 6.6 Reference point Vp: VAU-PSS + +### 6.6.1 Interface functions + +Reference point Vp is between the VAU and the PSS. + +It is used to transfer performance data, alarm data and topological data. + +### 6.6.2 Interface protocols + +Interface protocols are HTTP+XML, SOAP or CORBA for different platforms and systems. + +### 6.6.3 Message format + +#### 6.6.3.1 VAU interface + +The VAU interface is used to control and manage the VAU according to the definition of the management information base (MIB). + +The VAU information model is described in Tables 6.6-1, 6.6-2 and 6.6-3. The state management is defined in Table 6.6-3. + +**Table 6.6-1 – VAU interface** + +| Name | Data type | Read/Write | +|--------------------------------|-----------|------------| +| VAU device ID | String | R/W | +| Version number | String | R/W | +| Equipment manufacturer code | String | R/W | +| Equipment manufacturer name | String | R/W | +| IP network parameter | String | R/W | +| Maximum number of video input | Integer | R/W | +| Maximum number of video output | Integer | R/W | +| Transcoding type | String | R/W | +| Platform number | Integer | R/W | + +**Table 6.6-2 – VAU multi-platform data structure** + +| Name | Data type | Read/Write | +|---------------|-----------|------------| +| CMS device ID | String | R/W | +| IP address | String | R/W | +| Port | String | R/W | + +**Table 6.6-3 – VAU state management information data structure** + +| Name | Date type | Read/Write | +|----------------------------|------------------|-------------------| +| VAU device ID | String | R | +| CPU usage | String | R | +| Memory usage | String | R | +| Current processes number | Integer | R | +| Current thread number | Integer | R | +| Registration status | String | R | +| Current video inputs | Integer | R | +| Current video outputs | Integer | R | +| Current transcoding number | Integer | R | +| VAU heartbeat statue | String | R | + +#### **6.6.3.2 PSS interface** + +This is the MIB definition of PSS management, which can be used to control and manage the PSS. + +Configuration management is described in Table 6.6-4. + +State management is described in Table 6.6-5. + +**Table 6.6-4 – PSS configuration management data structure** + +| Name | Data type | Read/Write | +|--------------------------------|------------------|-------------------| +| PSS device ID | String | R/W | +| Version Number | String | R/W | +| Equipment manufacturer code | String | R/W | +| Equipment manufacturer name | String | R/W | +| Maximum number of video input | Integer | R/W | +| Maximum number of video output | Integer | R/W | + +**Table 6.6-5 – PSS state management data structure** + +| Name | Data type | Read/Write | +|----------------------------|------------------|-------------------| +| PSS device ID | String | R | +| CPU usage | String | R | +| Memory usage | String | R | +| Current processes number | Integer | R | +| Current thread number | Integer | R | +| Registration status | String | R | +| Current video inputs | Integer | R | +| Current transcoding number | Integer | R | +| PSS heartbeat statue | String | R | + +## 6.7 Reference points Mdv/Pv/Vs:VAU-VS system + +Reference points Mdv, Pv, Vs are all between the VAU and the visual surveillance (VS) system which are all internal interfaces, there is no specific definition in this Recommendation. + +# 7 Message flows + +In this clause, the message flows of main functions are described, including real-time video/audio acquisition, recording and playback, PTZ control, resource query and service management. The following are illustrative items: + +- The SIP message format should comply with the definition in [IETF RFC 3261] +- The RTSP message format should comply with the definition in [IETF RFC 7826] +- The HTTP message format should comply with HTTP1.1 defined in [IETF RFC 7231] +- RTP/RTCP signalling message refers to [IETF RFC 3550]. + +## 7.1 Real-time video/audio acquisition + +Real-time video/audio acquisition is used to view the real-time surveillance video/audio data by mobile terminals. After the MSP performs authentication and returns the VAU information, the M\_CU chooses and requests the VAU for real-time video/audio data. + +![Sequence diagram illustrating high level procedural flows for real-time media acquisition between M_CU, VAU, and CMU.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +``` +sequenceDiagram + participant M_CU + participant VAU + participant CMU + + M_CU->>VAU: 1. RTSP DESCRIBE (PUID-ChannelNo) + VAU-->>M_CU: 2. RTSP 200OK (Return SDP) + M_CU->>VAU: 3. RTSP SETUP (PUID-ChannelNo) + VAU-->>M_CU: 4. RTSP 200OK + M_CU->>VAU: 5. RTSP PLAY (PUID-ChannelNo) + Note over VAU: 6. Choose CMU according to PUID + VAU->>CMU: 7. Start session request + CMU-->>VAU: 8. Start session response + Note over VAU: 9. Start the connection between PUID-ChannelNo and CallID.Session + VAU-->>M_CU: 10. RTSP 200OK (Session) + CMU->>VAU: Input media + VAU->>M_CU: Output media +``` + +The diagram illustrates the message flows for real-time media acquisition. It involves three main entities: M\_CU (Mobile Client Unit), VAU (Video Acquisition Unit), and CMU (Camera Management Unit). The sequence of messages is as follows: 1. M\_CU sends an RTSP DESCRIBE message (PUID-ChannelNo) to VAU. 2. VAU responds with an RTSP 200OK message (Return SDP). 3. M\_CU sends an RTSP SETUP message (PUID-ChannelNo) to VAU. 4. VAU responds with an RTSP 200OK message. 5. M\_CU sends an RTSP PLAY message (PUID-ChannelNo) to VAU. 6. VAU internally chooses a CMU according to PUID. 7. VAU sends a Start session request to CMU. 8. CMU responds with a Start session response. 9. VAU internally starts the connection between PUID-ChannelNo and CallID.Session. 10. VAU sends an RTSP 200OK message (Session) to M\_CU. At the bottom, 'Input media' flows from CMU to VAU, and 'Output media' flows from VAU to M\_CU. + +H.627.1(17)\_F7-1 + +Sequence diagram illustrating high level procedural flows for real-time media acquisition between M\_CU, VAU, and CMU. + +**Figure 7-1 – High level procedural flows for real-time media acquisition** + +The message flows for real-time video/audio acquisition, illustrated in Figure 7-1, are as follows: + +- 1) The M\_CU sends RTSP DESCRIBE (PuID-ChannelNo) to the VAU. +- 2) The VAU returns response message to the M\_CU according to parameter configuration. + +- 3) The M\_CU sends RTSP SETUP request to the VAU. +- 4) The VAU distributes a channel and returns RTSP 200OK response message to the M\_CU. +- 5) The M\_CU sends RTSP PLAY request to the VAU for real-time video surveillance. +- 6) The VAU chooses the CMU according to premises unit identifier (PUID). +- 7) The VAU starts session request to the CMU. +- 8) The CMU returns session response to the VAU. If the VAU provides video format message body, the CMU chooses a codec that the PU supports and returns the message body to the VAU. If the VAU does not offer message body information, the CMU returns the message body carrying all the capacities that the PU supports to the VAU. +- 9) The VAU judges the media data format and decides whether to start the transcoding process. The VAU starts the connection between PuID-ChannelNo and CallID and creates a RTSP Session NO. +- 10) The VAU sends a session control response message to the M\_CU. + +## **7.2 Recording and playback** + +The playback function is used to play audio and video which has been previously recorded and stored. + +### **7.2.1 Playback in platform** + +When users want to playback the surveillance video using mobile phones, they must log into the MSP by the M\_CU. The MSP performs authentication and returns the playback surveillance list. + +After the users choose one surveillance point name, the M\_CU sends a request for this surveillance video to the VAU and then the VAU returns the media stream to the M\_CU to play. + +![Sequence diagram showing video playback procedural flows between M_CU, MSP, VAU, and CMU. The diagram includes 18 numbered steps: 1. Http videos search request (PUID-ChannelNo) from M_CU to MSP; 2. Http videos search request from MSP to CMU; 3. Return the videos list response from CMU to MSP; 4. HTTP 200OK (Return video resource) from MSP to M_CU; 5. RTSP DESCRIBE (PUID-ChannelNo, Record-No) from M_CU to VAU; 6. RTSP 200OK (Return SDP) from VAU to M_CU; 7. RTSP SETUP (PUID-ChannelNo, Record-No) from M_CU to VAU; 8. RTSP 200OK from VAU to M_CU; 9. RTSP PLAY (PUID-ChannelNo, Record-No) from M_CU to VAU; 10. Choose CMU according to PUID and Record-No, and start channel from VAU; 11. Start session request from VAU to CMU; 12. Start session response from CMU to VAU; 13. Start the connection between PUID-Record-No and CallID.Session from VAU; 14. RTSP 200OK (Session) from VAU to M_CU; 15. RTSP TEARDOWN (Record-No, MSISDN, Session) from M_CU to VAU; 16. Stop session request from VAU to CMU; 17. Stop session response from CMU to VAU; 18. RTSP 200OK (Session) from VAU to M_CU. Media flows are shown as 'Output media' from VAU to M_CU and 'Input media' from CMU to VAU.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +sequenceDiagram + participant M_CU + participant MSP + participant VAU + participant CMU + + Note right of CMU: H.627.1(17)_F7-2 + + M_CU->>MSP: 1. Http videos search request (PUID-ChannelNo) + MSP->>CMU: 2. Http videos search request + CMU-->>MSP: 3. Return the videos list response + MSP-->>M_CU: 4. HTTP 200OK (Return video resource) + M_CU->>VAU: 5. RTSP DESCRIBE (PUID-ChannelNo, Record-No) + VAU-->>M_CU: 6. RTSP 200OK (Return SDP) + M_CU->>VAU: 7. RTSP SETUP (PUID-ChannelNo, Record-No) + VAU-->>M_CU: 8. RTSP 200OK + M_CU->>VAU: 9. RTSP PLAY (PUID-ChannelNo, Record-No) + VAU->>CMU: 10. Choose CMU according to PUID and Record-No, and start channel + VAU->>CMU: 11. Start session request + CMU-->>VAU: 12. Start session response + VAU->>M_CU: 13. Start the connection between PUID-Record-No and CallID.Session + VAU-->>M_CU: 14. RTSP 200OK (Session) + Note right of VAU: Input media + Note left of M_CU: Output media + M_CU->>VAU: 15. RTSP TEARDOWN (Record-No, MSISDN, Session) + VAU->>CMU: 16. Stop session request + CMU-->>VAU: 17. Stop session response + VAU-->>M_CU: 18. RTSP 200OK (Session) + +``` + +Sequence diagram showing video playback procedural flows between M\_CU, MSP, VAU, and CMU. The diagram includes 18 numbered steps: 1. Http videos search request (PUID-ChannelNo) from M\_CU to MSP; 2. Http videos search request from MSP to CMU; 3. Return the videos list response from CMU to MSP; 4. HTTP 200OK (Return video resource) from MSP to M\_CU; 5. RTSP DESCRIBE (PUID-ChannelNo, Record-No) from M\_CU to VAU; 6. RTSP 200OK (Return SDP) from VAU to M\_CU; 7. RTSP SETUP (PUID-ChannelNo, Record-No) from M\_CU to VAU; 8. RTSP 200OK from VAU to M\_CU; 9. RTSP PLAY (PUID-ChannelNo, Record-No) from M\_CU to VAU; 10. Choose CMU according to PUID and Record-No, and start channel from VAU; 11. Start session request from VAU to CMU; 12. Start session response from CMU to VAU; 13. Start the connection between PUID-Record-No and CallID.Session from VAU; 14. RTSP 200OK (Session) from VAU to M\_CU; 15. RTSP TEARDOWN (Record-No, MSISDN, Session) from M\_CU to VAU; 16. Stop session request from VAU to CMU; 17. Stop session response from CMU to VAU; 18. RTSP 200OK (Session) from VAU to M\_CU. Media flows are shown as 'Output media' from VAU to M\_CU and 'Input media' from CMU to VAU. + +**Figure 7-2 – Video playback from the platform procedural flows** + +The message flows for playback in the platform, illustrated in Figure 7-2, are as follows: + +- 1) The M\_CU sends http video search request (PuID-ChannelNo) to the MSP. +- 2) The MSP sends http video search request (PuID-ChannelNo) to the CMU. +- 3) The CMU returns the video list information to the MSP. +- 4) The MSP returns the video list information to the M\_CU. Each video is assigned a unique Record-No in the CMU. +- 5) The M\_CU sends RTSP DESCRIBE (PuID-ChannelNo, Record-No) to the VAU. +- 6) The VAU returns a response message to the M\_CU according to the parameter configuration. +- 7) The M\_CU sends RTSP SETUP request to the VAU. + +- 8) The VAU distributes a channel and returns RTSP 200OK response message to the M\_CU. +- 9) The M\_CU sends RTSP PLAY request to the VAU for videos record (PuID-ChannelNo, Record-No). +- 10) The VAU chooses the CMU according to PUID and Record-No. +- 11) The VAU starts session request to the CMU. The request message carries the message body including the video format which the VAU supports. +- 12) The CMU returns a session response to the VAU. If the VAU provides a video format message body, the CMU chooses the codec which the PU supports and returns the message body to the VAU. If the VAU does not offer message body information, the CMU returns the message body carrying all capabilities which the PU supports to the VAU. +- 13) The VAU decides whether to start the transcoding process according to the media data format. The VAU starts the connection between PuID-ChannelNo, RecordNo and CallID, and creates a RTSP Session No. +- 14) The VAU sends a session response message to the M\_CU. +- 15) The M\_CU sends RTSP TEARDOWN to the VAU in order to remove the real-time session. +- 16) The VAU sends the end request to the CMU to stop the session. +- 17) The CMU sends the end response to the VAU to stop the session. +- 18) The VAU sends the end response to the M\_CU to stop the session. + +### 7.2.2 Playback in PU + +The message flows for playback in the premises unit are illustrated in Figure 7-3. + +![Sequence diagram showing video playback from the PU procedural flows. Lifelines: M_CU, MSP, VAU, CMU, PU. The sequence includes HTTP search requests, RTSP DESCRIBE, SETUP, PLAY, and TEARDOWN messages, as well as SIP INFO and session management messages between the CMU and PU.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +``` + +sequenceDiagram + participant M_CU + participant MSP + participant VAU + participant CMU + participant PU + + Note right of PU: H.627.1(17)_F7-3 + + M_CU->>MSP: 1. Http videos search request (PUID-ChannelNo) + MSP->>CMU: 2. Http videos search request + CMU->>PU: 3. SIP INFO videos search request + PU-->>CMU: 4. Videos list response + CMU-->>MSP: 5. Return the videos list response + MSP-->>M_CU: 6. HTTP 200OK (Return video resource) + M_CU->>VAU: 7. RTSP DESCRIBE (PUID-ChannelNo, Record-No) + VAU-->>M_CU: 8. RTSP 200OK (Return SDP) + M_CU->>VAU: 9. RTSP SETUP (PUID-ChannelNo, Record-No) + VAU-->>M_CU: 10. RTSP 200OK + M_CU->>VAU: 11. RTSP PLAY (PUID-ChannelNo, Record-No) + Note right of VAU: 12. Choose CMU according to PUID and Record-No, and start channel + VAU->>PU: 13. Start session request + PU-->>VAU: 14. Start session response + Note right of VAU: 15. Start the connection between PUID-Record-No and CallID.Session + VAU-->>M_CU: 16. RTSP 200OK (Session) + Note right of VAU: Input media + Note left of VAU: Output media + M_CU->>VAU: 17. RTSP TEARDOWN (Record-No, MSISDN, Session) + VAU->>PU: 18. Stop session request + PU-->>VAU: 19. Stop session response + VAU-->>M_CU: 20. RTSP 200OK (Session) + +``` + +Sequence diagram showing video playback from the PU procedural flows. Lifelines: M\_CU, MSP, VAU, CMU, PU. The sequence includes HTTP search requests, RTSP DESCRIBE, SETUP, PLAY, and TEARDOWN messages, as well as SIP INFO and session management messages between the CMU and PU. + +**Figure 7-3 – Video playback from the PU procedural flows** + +The message flows for playback in the PU, illustrated in Figure 7-3, are as follows: + +- 1) The M\_CU sends a http video search request (PuID-ChannelNo) to the MSP. +- 2) The MSP sends a http video search request (PuID-ChannelNo) to the CMU. +- 3) The CMU sends a SIP(INFO) request to the PU for videos list information (PuID-ChannelNo). +- 4) The PU returns the video list information to the CMU. +- 5) The CMU returns video list information to the MSP. +- 6) The MSP returns the video list information to the M\_CU. The CMU distributes the Record-No to the videos +- 7) The M\_CU sends RTSP DESCRIBE (PuID-ChannelNo, Record-No) to the VAU. + +- 8) The VAU returns a response message to the M\_CU according to parameter configuration. +- 9) The M\_CU sends a RTSP SETUP request to the VAU. +- 10) The VAU distributes a channel and returns RTSP 200OK response message to the M\_CU. +- 11) The M\_CU sends RTSP PLAY request to the VAU for videos record (PuID-ChannelNo, Record-No). +- 12) The VAU chooses the CMU according to PUID and Record-No. +- 13) The VAU starts a session request to the PU. The request message carries message body including the video format which the VAU supports. +- 14) The PU returns a session response to the VAU. If the VAU provides the video format message body, the CMU chooses the codec which the PU supports and returns the message body to the VAU. If the VAU does not offer message body information, the CMU returns the message body carrying all capabilities which the PU supports to the VAU. +- 15) The VAU decides whether to start the transcoding process according to the media data format. The VAU starts the connection between PuID-ChannelNo, RecordNo and CallID and creates a RTSP Session NO. +- 16) The VAU sends a session response message to the M\_CU. +- 17) The M\_CU sends a RTSP TEARDOWN to the VAU in order to disconnect the real-time session. +- 18) The VAU sends a disconnect request to the PU to stop session. +- 19) The PU sends a disconnect response to the VAU to stop session. +- 20) The VAU sends a disconnect response to the M\_CU to stop session. + +## 7.3 PTZ control + +The PTZ control function illustrated in Figure 7-4 is used to pan, tilt and zoom cameras, switch auxiliary peripherals (such as lighting, cooling fan and rain wipers) and to present the position of related physical devices. + +![Sequence diagram illustrating PTZ control procedural flows between M_CU, VAU, and CMU. The diagram shows two main sequences: PTZ control request and PTZ stop request. The PTZ control request sequence involves M_CU sending a request to VAU, VAU sending a request to CMU, CMU returning a response to VAU, and VAU returning a response to M_CU. The PTZ stop request sequence involves M_CU sending a SIP INFO PTZ Stop request to VAU, VAU checking for a response within configuration time, and if none, sending a PTZ stop request to CMU. CMU returns a response to VAU, VAU sends a stop session request to CMU, CMU returns a response to VAU, and finally VAU sends an RTSP 200OK response to M_CU.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant M_CU + participant VAU + participant CMU + + Note right of VAU: No PTZ stop message response within configuration time + + M_CU->>VAU: 1. PTZ control request + VAU->>CMU: 2. PTZ control request + CMU-->>VAU: 3. PTZ control response + M_CU->>VAU: 4. SIP INFO PTZ Stop request (UserID, DestID, Param1, Param2) + Note right of VAU: No PTZ stop message response within configuration time + VAU->>CMU: 5. PTZ stop request + CMU-->>VAU: 6. PTZ stop response + M_CU->>VAU: 7. RTSP TEARDOWN (PUID-ChannelNo, MSISDN, Session) + VAU->>CMU: 8. Stop session request + CMU-->>VAU: 9. Stop session response + VAU-->>M_CU: 10. RTSP 200OK (Session) + +``` + +H.627.1(17)\_F7-4 + +Sequence diagram illustrating PTZ control procedural flows between M\_CU, VAU, and CMU. The diagram shows two main sequences: PTZ control request and PTZ stop request. The PTZ control request sequence involves M\_CU sending a request to VAU, VAU sending a request to CMU, CMU returning a response to VAU, and VAU returning a response to M\_CU. The PTZ stop request sequence involves M\_CU sending a SIP INFO PTZ Stop request to VAU, VAU checking for a response within configuration time, and if none, sending a PTZ stop request to CMU. CMU returns a response to VAU, VAU sends a stop session request to CMU, CMU returns a response to VAU, and finally VAU sends an RTSP 200OK response to M\_CU. + +Figure 7-4 – PTZ control procedural flows + +The message flows for PTZ control, illustrated in Figure 7-4, are as follows: + +- 1) The M\_CU sends a PTZ control request to the VAU. The message body carries UserID and DestID (DestID is PuID-ChannelNo). +- 2) The VAU sends a PTZ code to the CMU. +- 3) The CMU sends a PTZ control response to the VAU. +- 4) The M\_CU sends a SIP INFO PTZ stop request to the VAU. +- 5) If the VAU receives the stop request from the M\_CU within a specified time, the VAU sends a PTZ stop request to the CMU, otherwise, the VAU sends a PTZ stop request to the CMU automatically. +- 6) The CMU sends a PTZ stop response to the VAU. +- 7) The M\_CU sends a RTSP TEARDOWN to the VAU in order to disconnect the real-time session. +- 8) The VAU sends the disconnect request to the CMU to stop session. +- 9) The CMU sends the disconnect response to the VAU to stop session. +- 10) The VAU sends the disconnect response to the M\_CU to stop session. + +## 7.4 Resource query + +The message flows for a user resource query are illustrated in Figure 7-5. + +![Sequence diagram illustrating the User resource query procedural flows between USER, MSP, and CMU.](3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg) + +``` + +sequenceDiagram + participant USER + participant MSP + participant CMU + Note right of CMU: H.627.1(17)_F7-5 + USER->>MSP: 1. USERS log in (MSISDN or USERID and PWD) + MSP->>MSP: 2. TranslateMSI SDN into USERID + MSP->>CMU: 3. USER query (UserID) + CMU->>CMU: 4. USER resource query (UserID) + CMU->>MSP: 5. Return list (PUID-ChannelNo, PUName, PuProperty) + MSP->>MSP: 6. Build page according to USER order mobile service + MSP->>USER: 7. Return the PSS-URL, including PUID-ChannelNo, VAU URL and PuProperty + +``` + +The diagram shows a sequence of interactions between three entities: USER, MSP, and CMU. The flow starts with the USER sending a login request (MSISDN or USERID and PWD) to the MSP. The MSP then performs an internal translation (TranslateMSI SDN into USERID). Next, the MSP sends a USER query (UserID) to the CMU. The CMU performs an internal resource query (UserID) and returns a list (PUID-ChannelNo, PUName, PuProperty) to the MSP. The MSP then builds a page according to the USER order mobile service and finally returns the PSS-URL (including PUID-ChannelNo, VAU URL and PuProperty) to the USER. A label 'H.627.1(17)\_F7-5' is present at the bottom right of the diagram. + +Sequence diagram illustrating the User resource query procedural flows between USER, MSP, and CMU. + +**Figure 7-5 – User resource query procedural flows** + +The message flows for a user resource query, illustrated in Figure 7-5, are as follows: + +- 1) USER logs into the MSP using MSISDN or USERID and password. +- 2) The MSP gets MSISDN-No from MSISDN, and then recognizes user type from MSISDN-No. Finally, the MSP translates the user type and MSISDN-No into UserID. +- 3) The MSP queries UserID in the CMU. +- 4) The CMU queries the user resource list according to UserID. +- 5) The CMU returns the list and user information to the MSP including PuID-ChannelNo, PUName, PuProperty. +- 6) The MSP builds a web page according to the user mobile service subscription. + +- 7) The MSP returns the PSS-URL and user mobile service subscription. + +## 7.5 Service management + +### 7.5.1 VAU registration + +The VAU registers to the CMU with its ID number and the capability information (including the transcoding and distribution capability) and re-registers automatically at regular times according to the configuration of the registration information. This is illustrated in Figure 7-6. + +![Sequence diagram for VAU registration. Lifelines: VAU and CMU. The VAU performs an internal action 'VAU gets the registration information', then sends a 'Registration request' to the CMU, and receives a 'Registration response' from the CMU.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +``` +sequenceDiagram + participant VAU + participant CMU + Note left of VAU: VAU gets the registration information + VAU->>CMU: Registration request + CMU-->>VAU: Registration response + Note right of CMU: H.627.1(17)_F7-6 +``` + +Sequence diagram for VAU registration. Lifelines: VAU and CMU. The VAU performs an internal action 'VAU gets the registration information', then sends a 'Registration request' to the CMU, and receives a 'Registration response' from the CMU. + +Figure 7-6 – VAU registration procedural flows + +### 7.5.2 M\_CU authorization + +The M\_CU sends a request to the MSP. The MSP gets the UserID and the password and sends an authorization request to the CMU. The CMU returns the ok information or the error code. This is illustrated in Figure 7-7. + +![Sequence diagram for M_CU authorization. Lifelines: M_CU, MSP, and CMU. The M_CU sends an 'Authorization request' to the MSP. The MSP sends a 'Verify the User Info' request to the CMU. The CMU returns 'OK or Fail Info' to the MSP. Finally, the MSP returns 'ok or error code' to the M_CU.](836b0790cef5469a167fa8931df4e408_img.jpg) + +``` +sequenceDiagram + participant M_CU + participant MSP + participant CMU + M_CU->>MSP: Authorization request + MSP->>CMU: Verify the User Info + CMU-->>MSP: Return OK or Fail Info + MSP-->>M_CU: Return ok or error code + Note right of CMU: H.627.1(17)_F7-7 +``` + +Sequence diagram for M\_CU authorization. Lifelines: M\_CU, MSP, and CMU. The M\_CU sends an 'Authorization request' to the MSP. The MSP sends a 'Verify the User Info' request to the CMU. The CMU returns 'OK or Fail Info' to the MSP. Finally, the MSP returns 'ok or error code' to the M\_CU. + +Figure 7-7 – M\_CU authorization procedural flows + +### 7.5.3 PU-related parameters query + +The message flows for a PU-related query, illustrated in Figure 7-8, are as follows: + +- 1) The MSP queries the source list of the current UserID. +- 2) The mobile CMU platform transfers the PU list and related information to the MSP. The information includes the PuID-ChannelNo, PUName and PuProperty. +- 3) The MSP processes the information and returns it to the M\_CU for display. + +![Sequence diagram showing procedural flows for querying PU related parameters between M_CU, MSP, and CMU.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +``` +sequenceDiagram + participant M_CU + participant MSP + participant CMU + Note right of CMU: H.627.1(17)_F7-8 + M_CU->>MSP: Authorization + MSP->>CMU: Query the related source + CMU-->>MSP: Return the related information + MSP-->>M_CU: Return the processed Info +``` + +The diagram illustrates a sequence of interactions between three entities: M\_CU, MSP, and CMU. The sequence begins with M\_CU sending an 'Authorization' message to MSP. MSP then sends a 'Query the related source' message to CMU. CMU responds with 'Return the related information' to MSP. Finally, MSP sends 'Return the processed Info' back to M\_CU. A label 'H.627.1(17)\_F7-8' is positioned below the CMU lifeline. + +Sequence diagram showing procedural flows for querying PU related parameters between M\_CU, MSP, and CMU. + +**Figure 7-8 – Procedural flows for querying PU related parameters** + +## Bibliography + +- [b-ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.* +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks.* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.627.4-202512-I_PDF-E/raw.md b/marked/H/T-REC-H.627.4-202512-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..53817d2eb8e79f2bde5428cdf23833bd03709de8 --- /dev/null +++ b/marked/H/T-REC-H.627.4-202512-I_PDF-E/raw.md @@ -0,0 +1,1134 @@ + + +# Recommendation**ITU-T H.627.4 (12/2025)** + +SERIES H: Audiovisual and multimedia systems + +Broadband, triple-play and advanced multimedia services – +Advanced multimedia services and applications + +--- + +## **Protocols of algorithm-training systems for intelligent video surveillance** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circle with a globe-like design. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +### **Audiovisual and multimedia systems** + +| | | +|-----------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| Broadband multimedia services over VDSL | H.610-H.619 | +| Advanced multimedia services and applications | H.620-H.629 | +| Content delivery and ubiquitous sensor network applications | H.640-H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.627.4 + +## Protocols of algorithm-training systems for intelligent video surveillance + +## Summary + +Recommendation ITU-T H.627.4 specifies the protocols of the algorithm-training system (ATS) for intelligent video surveillance (IVS), which meets the requirements, functional architecture and reference points of ATS specified in Recommendation ITU-T F.743.22. The performance of intelligent algorithms affects the intelligence level of IVS systems. The IVS systems deployed in various industry service scenarios can obtain massive visual data. The ATS continuously deploys the iterative algorithms generated by algorithm-training based on visual data to the IVS systems, which can enhance the analysis, computing and inference capabilities of the IVS systems. This Recommendation is intended to guide the design, development, implementation and application of ATS for IVS. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.627.4 | 2025-12-14 | 21 | 11.1002/1000/16602 | + +## Keywords + +Algorithm-training, intelligent video surveillance, interfaces, protocols. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2026 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|---------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Overview of functional architecture and reference points..... | 4 | +| 7 | Overall requirements of protocols ..... | 5 | +| 7.1 | Structure of protocols ..... | 5 | +| 7.2 | REST service and HTTP method ..... | 5 | +| 7.3 | REST service resource access URI ..... | 5 | +| 7.4 | Template of protocol definition..... | 6 | +| 7.5 | Security requirements ..... | 6 | +| 8 | Interface descriptions..... | 6 | +| 8.1 | Common interfaces..... | 6 | +| 8.2 | Interface of reference point Ai ..... | 7 | +| 8.3 | Interfaces of reference point Ms..... | 7 | +| 8.4 | Interfaces of reference point Ta..... | 8 | +| 8.5 | Interfaces of reference point Tu ..... | 8 | +| 8.6 | Interfaces of reference point Md ..... | 8 | +| 8.7 | Interfaces of reference point Mm ..... | 9 | +| 8.8 | Interfaces of reference point Ts..... | 9 | +| 8.9 | Interfaces of reference point Ts' ..... | 9 | +| 8.10 | Interfaces of reference point Tm ..... | 9 | +| 8.11 | Interfaces of reference point Mv ..... | 9 | +| 8.12 | Interfaces of reference point Mi ..... | 9 | +| 9 | Relevant protocol definitions..... | 10 | +| 9.1 | Protocol of interface POST /ATS/Register ..... | 10 | +| 9.2 | Protocol of interface POST /ATS/DeRegister..... | 10 | +| 9.3 | Protocol of interface POST /ATS/Keepalive ..... | 10 | +| 9.4 | Protocol of interface POST /ATS/TimeSync ..... | 11 | +| 9.5 | Protocol of interface GET /ATS/Device ..... | 11 | +| 9.6 | Protocol of interface GET /ATS/Resource..... | 12 | +| 9.7 | Protocol of interface GET /ATS/DataSet..... | 12 | +| 9.8 | Protocol of interface POST /ATS/AnnotationTask..... | 12 | +| 9.9 | Protocol of interface PUT /ATS/AnnotationTask ..... | 13 | + +| | Page | | +|-------------------------------------|-----------------------------------------------------------|----| +| 9.10 | Protocol of interface DELETE /ATS/AnnotationTask..... | 13 | +| 9.11 | Protocol of interface GET /ATS/AnnotationTask..... | 13 | +| 9.12 | Protocol of interface POST /ATS/TrainTask ..... | 14 | +| 9.13 | Protocol of interface PUT /ATS/TrainTask ..... | 14 | +| 9.14 | Protocol of interface DELETE /ATS/TrainTask..... | 14 | +| 9.15 | Protocol of interface GET /ATS/TrainTask ..... | 14 | +| 9.16 | Protocol of interface GET /ATS/Model ..... | 15 | +| 9.17 | Protocol of interface POST /ATS/ModelDeployTask..... | 15 | +| 9.18 | Protocol of interface PUT /ATS/ModelDeployTask..... | 16 | +| 9.19 | Protocol of interface DELETE /ATS/ModelDeployTask ..... | 16 | +| 9.20 | Protocol of interface GET /ATS/ModelDeployTask..... | 16 | +| 9.21 | Protocol of interface POST /ATS/Model ..... | 16 | +| 9.22 | Protocol of interface PUT /ATS/Model//Data..... | 17 | +| 9.23 | Protocol of interface POST /ATS/ModelDeploy ..... | 17 | +| 9.24 | Protocol of interface GET /ATS/Model//Data ..... | 17 | +| Annex A – Object descriptions ..... | | 18 | +| A.1 | ResponseStatus ..... | 18 | +| A.2 | Register..... | 18 | +| A.3 | DeRegister ..... | 18 | +| A.4 | Keepalive..... | 18 | +| A.5 | TimeSync..... | 19 | +| A.6 | Model..... | 19 | +| A.7 | ModelList ..... | 19 | +| A.8 | Device..... | 20 | +| A.9 | DeviceList..... | 20 | +| A.10 | Resource ..... | 20 | +| A.11 | DataSet ..... | 21 | +| A.12 | DataSetList ..... | 21 | +| A.13 | AnnotationTask ..... | 21 | +| A.14 | AnnotationTaskList ..... | 21 | +| A.15 | AnnotationTaskCtrl ..... | 22 | +| A.16 | TrainTask..... | 22 | +| A.17 | TrainTaskList ..... | 22 | +| A.18 | TrainTaskCtrl ..... | 22 | +| A.19 | ModelDeployTask ..... | 23 | +| A.20 | ModelDeployTaskList..... | 23 | +| A.21 | ModelDeployTaskCtrl..... | 23 | +| Bibliography..... | | 24 | + +# Recommendation ITU-T H.627.4 + +## Protocols of algorithm-training systems for intelligent video surveillance + +# 1 Scope + +This Recommendation specifies the protocols of the algorithm-training system (ATS) for intelligent video surveillance, which meets the requirements, functional architecture, and reference points of ATS specified in [ITU-T F.743.22]. + +The scope of this Recommendation includes: + +- Overview of functional architecture and reference points; +- Interface descriptions and relevant protocol definitions. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T F.743.22] Recommendation ITU-T F.743.22 (2022), *Requirements and architecture of an algorithm-training system for intelligent video surveillance*. + +[ITU-T H.626] Recommendation ITU-T H.626 (V2) (2019), *Architectural requirements for a video surveillance system*. + +[ITU-T H.626.5] Recommendation ITU-T H.626.5 (V2) (2022), *Architecture for intelligent video surveillance systems*. + +[ITU-T H.627] Recommendation ITU-T H.627 (2020), *Signalling and protocols for a video surveillance system*. + +[ITU-T H.627.3] Recommendation ITU-T H.627.3 (2022), *Protocols for intelligent video surveillance systems*. + +[IETF RFC 7616] IETF RFC 7616 (2015), *HTTP Digest Access Authentication*. + +[IETF RFC 9110] IETF RFC 9110 (2022), *HTTP Semantics*. + +[ISO 8601-1] ISO 8601-1:2019, *Date and time – Representations for information interchange – Part 1: Basic rules*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 algorithm** [b-ISO/IEC 11557]: A set of rules for transforming the logical representation of data. + +**3.1.2 algorithm management unit (AMU)** [ITU-T F.743.22]: A subsystem unit of the algorithm-training system that provides model warehouse management, model adaptation, model packaging and algorithm deployment. + +**3.1.3 algorithm-training management (ATM)** [ITU-T F.743.22]: A subsystem unit of the algorithm-training system (ATS), which provides the management of the sample management unit (SMU), the training management unit (TMU) and the algorithm management unit (AMU). + +**3.1.4 data storage and service (DSS)** [ITU-T H.626.5]: The storage and sharing centre for video and image information within the intelligent video surveillance system. The DSS accepts registration, keepalive reports from the intelligent premises unit (IPU), intelligent video management (IVM) or intelligent application service (IAS) and obtains video and image information from them. It can also provide information network sharing services such as information querying, subscription, guard and alarm, etc. + +**3.1.5 intelligent application service (IAS)** [ITU-T H.626.5]: The intelligent application service (IAS) is located at the application service core of the intelligent video surveillance system. Its main functions include providing application services about the video and image information, such as information query and retrieval, subscription and notification, manual annotation, etc.; providing external operations such as the creation and start-up of intelligent analysis tasks based on intelligent video management (IVM); obtaining the list of devices from the central control server (CCS) or data storage and service (DSS) and sharing them with the IVM so that it can schedule intelligent video units (IVUs) for video stream analysis, etc. + +**3.1.6 intelligent premises unit (IPU)** [ITU-T H.626.5]: The premises subsystem within the intelligent video surveillance system. The premises intelligent video (PIV) module is added to the premises unit (PU) for intelligent video analysis. + +**3.1.7 intelligent video unit (IVU)** [ITU-T H.626.5]: The intelligent video unit (IVU) identifies specific objects automatically, and outputs recognition results to an intelligent video management (IVM) system. The recognition information includes triggered events and acquired data. One or more intelligent analysis algorithms can be loaded or unloaded on an intelligent video unit (IVU) according to different requirements. + +**3.1.8 media distribution unit (MDU)** [ITU-T H.626.5]: The media distribution unit (MDU) is used to transport media from the premises unit (PU) to the customer unit (CU). Its main functions include media receiving, media processing, media routing, media transmission, media forwarding and media replication. + +**3.1.9 media storage unit (MSU)** [ITU-T H.626.5]: The media storage unit (MSU) is used to retrieve and store media and provide media serving capability. Its main functions include media storage, media serving, media indexing and media downloading. + +**3.1.10 media server (MS)** [ITU-T H.626]: A device located at the centre part of a video surveillance system. It is used to forward real-time media stream as well as store, retrieve and replay historical media stream. The media server receives the media stream from premises unit or other media server and forwards the media stream to other customer unit or media server. It consists of media distribution unit and media storage unit. + +**3.1.11 model** [b-ISO/IEC TR 29119-11]: Output of an [machine learning] algorithm trained with a training dataset that generates predictions using patterns in the input data. + +**3.1.12 sample management unit (SMU)** [ITU-T F.743.22]: A subsystem unit of the algorithm-training system that provides training dataset management, data annotation and annotation information storage. + +**3.1.13 training management unit (TMU)** [ITU-T F.743.22]: A subsystem unit of the algorithm-training system that provides algorithm-training task management, algorithm training, and model verification and evaluation. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------| +| AMU | Algorithm Management Unit | +| ATM | Algorithm Training Management | +| ATS | Algorithm Training System | +| CCS | Central Control Server | +| CIV | Client Intelligent Video | +| CMU | Centre Management Unit | +| CPU | Central Processing Unit | +| DSS | Data Storage and Service | +| GPU | Graphics Processing Unit | +| HTTP | Hypertext Transfer Protocol | +| HTTPS | Hypertext Transfer Protocol Secure | +| IAS | Intelligent Application Service | +| ICU | Intelligent Customer Unit | +| ID | Identifier | +| IP | Internet Protocol | +| IPU | Intelligent Premises Unit | +| IVM | Intelligent Video Management | +| IVS | Intelligent Video Surveillance | +| IVU | Intelligent Video Unit | +| JSON | JavaScript Object Notation | +| MDU | Media Distribution Unit | +| MS | Media Server | +| MSU | Media Storage Unit | +| NTP | Network Time Protocol | +| PIV | Premises Intelligent Video | +| REST | Representational State Transfer | +| SCU | Service Control Unit | +| SMU | Sample Management Unit | +| TMU | Training Management Unit | + +URI Uniform Resource Identifier + +UTP-8 8-bit Unicode Transformation Format + +# 5 Conventions + +In this Recommendation: + +- The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. +- The keywords "**is recommended**" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "**can optionally**" indicate an optional requirement which is permissible, without implying any sense of being recommended. These terms are not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +# 6 Overview of functional architecture and reference points + +Figure 1 shows the functional architecture of the ATS for intelligent video surveillance (IVS) defined in [ITU-T F.743.22]. + +![Functional architecture diagram of the algorithm-training system for intelligent video surveillance (ATS) and intelligent video surveillance (IVS) system.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +The diagram illustrates the functional architecture of the algorithm-training system (ATS) and the intelligent video surveillance (IVS) system. The ATS is enclosed in a dashed box on the left and contains four functional entities: ATM, SMU, TMU, and AMU. The IVS system is enclosed in a dashed box on the right and contains several functional entities: IAS, DSS, IVM, IVU, CCS (containing CMU and SCU), MS (containing MDU and MSU), IPU (containing PIV), and ICU (containing CIV). Reference points are indicated by colored arrows: red for Control, black for Media, green for Video and image information, and blue for Algorithm. The diagram shows various interactions between the ATS and IVS components through these reference points, such as Ai, Ms, Ta, Tu, Md, Mm, Ts/Ts', Tm, Mv, Mi, Ad, Ad', Id, Id', Ma, Ma', Mu, Mu', Su, Ps, Du, Pd, Pd', Mp', Mp, Pc, Mc', Mc, Cs, and Cm. The text H.627.4(25) is present near the ICU entity. + +Functional architecture diagram of the algorithm-training system for intelligent video surveillance (ATS) and intelligent video surveillance (IVS) system. + +**Figure 1 – Functional architecture of the algorithm-training system for intelligent video surveillance defined in [ITU-T F.743.22]** + +Functional architecture, functional entities, and reference points of ATS for IVS systems are defined in [ITU-T F.743.22], including the functional entities algorithm-training management (ATM), sample management unit (SMU), training management unit (TMU), and algorithm management unit (AMU), and reference points Ai, Ms, Ta, Tu, Md, Mm, Ts/Ts', Tm, Mv and Mi. + +The functional architecture, functional entities, and reference points of IVS systems are defined in [ITU-T H.626] and [ITU-T H.626.5], including the functional entities data storage and service (DSS), intelligent application service (IAS), intelligent video management (IVM), intelligent video + +unit (IVU), central control server (CCS) (including centre management unit (CMU) and service control unit (SCU)), media server (MS) (including media distribution unit (MDU) and media storage unit (MSU)), intelligent premises unit (IPU), premises intelligent video (PIV), intelligent customer unit (ICU), and client intelligent video (CIV), reference points PS, Mp/Mp', Pc, Cs, Mc/Mc', Su, Du, Mu/Mu', Ma/Ma', Ad/Ad', Id/Id', Pd/Pd', Ac, Cm, and Ds/Ds'. Protocols of IVS systems are defined in [ITU-T H.627] and [ITU-T H.627.3]. + +This Recommendation defines the protocols of ATS for IVS systems based on [ITU-T F.743.22], [ITU-T H.626], [ITU-T H.626.5], [ITU-T H.627] and [ITU-T H.627.3]. + +# 7 Overall requirements of protocols + +## 7.1 Structure of protocols + +The protocols adopt the representational state transfer (REST) style and are based on hypertext transfer protocol (HTTP). The content-type in the message header is required to be set as application/JSON. The message body is described in JavaScript object notation (JSON) [b-IETF JSON] format, and the character set is 8-bit unicode transformation format (UTF-8). The message response status code is required to comply with the requirements of [IETF RFC 9110]. The protocol interaction and connection method is required to support HTTP long and short connections, and the implementation mechanism is required to comply with the requirements of [IETF RFC 9110]. + +Figure 2 shows the structure of protocols. + +![](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +| | +|--------------------------------------| +| Message body protocols based on JSON | +| HTTP based on REST | +| TCP | +| IP | + +H.627.4(25) + +Figure 2 – The structure of protocols + +## 7.2 REST service and HTTP method + +Table 1 shows the implementation of REST service through HTTP method verbs. + +Table 1 – HTTP method verbs + +| HTTP method verbs | Annotation | +|-------------------|--------------------| +| POST | Resource creation | +| GET | Resource retrieval | +| PUT | Resource update | +| DELETE | Resource deletion | + +## 7.3 REST service resource access URI + +The REST service resource access uniform resource identifier (URI) is: + +**{Protocol}://{Hostname}:{Port}/{BaseURI}{ServiceURI}[?{p1=v1}&{p2=v2}...&{pn=vn}]** + +The variable part is represented by "{ }", and the optional part is represented by "[ ]"; the protocol is required to support HTTP; Hostname refers to the Internet protocol (IP) address or domain name of + +the system; Port can optionally support, pointing to the slogan; BaseURI refers to the name of the system, which is required to be published as "ATS" for algorithm-training systems; ServiceURI refers to the interface resource request URI;?(p1=v1)&(p2=v2)...&(pn=vn) refers to a query string, where each resource defines required or optional query string parameters that appear in key-value pairs. + +## 7.4 Template of protocol definition + +Table 2 shows the template of protocol definition. + +**Table 2 – Template of protocol definition** + +| | | | | | +|-------------------|---------------------|-----------------------------|------------------------------|---------------------| +| URI | | | | | +| Function | | | | | +| Method | Query string | Request message body | Response message body | Query string | +| POST | | | | | +| GET | | | | | +| PUT | | | | | +| DELETE | | | | | +| Annotation | | | | | + +The URI item describes the interface resource request URI; the function item describes the function of the interface; the method item lists the HTTP methods involved in the resource, including POST, GET, PUT and DELETE; the query string describes the key-value pairs of the resources; the request message body item describes the message body of the HTTP request; the response message body describes the response to an HTTP request; the annotation item provides a description of the interface. + +## 7.5 Security requirements + +Both parties involved in information exchange are required to undergo identity authentication. The authentication process is required to comply with the digest authentication specified in [IETF RFC 7616]. The server random number is required to be reset after exceeding 3600 seconds during digest authentication [ITU-T H.627.3]. For systems with high security requirements, it is recommended to comply with hypertext transfer protocol secure (HTTPS) [IETF RFC 9110]. + +# 8 Interface descriptions + +## 8.1 Common interfaces + +Before conducting data exchange, the system is required to register first. When registration fails, a random delay of no more than 300 seconds is required to be allowed before re-registration. Both parties are required to configure a unified "heartbeat interval" (default heartbeat interval of 90 seconds). After successful registration, the registrant is required to regularly send heartbeat messages to the registered party according to the "heartbeat interval" for keep-alive. At the same time, both parties are required to configure the "keep-alive timeout parameter" (default heartbeat timeout of three times). The registrant is required to perform time calibration during the interaction process and proactively de-register when it stops running. Detailed parameters can be found in [ITU-T H.627.3]. + +Table 3 shows the common interfaces. + +**Table 3 – The common interfaces** + +| No. | Method | URI | Function | Protocol clause | +|-----|--------|-----------------|----------------------|-----------------| +| 1 | POST | /ATS/Register | Registration | 9.1 | +| 2 | POST | /ATS/DeRegister | De-registration | 9.2 | +| 3 | POST | /ATS/Keepalive | Keep-alive | 9.3 | +| 4 | POST | /ATS/TimeSync | Time synchronization | 9.4 | + +## 8.2 Interface of reference point Ai + +Table 4 shows the interface of reference point Ai. + +**Table 4 – The interface of reference point Ai** + +| No. | Method | URI | Function | Interface provider | Interface caller | +|-----|--------|-------------|--------------------------------------------------------------------|--------------------|------------------| +| 1 | GET | /ATS/Device | Device (IPU and IVU) list information querying based on conditions | IAS | ATM | + +### 8.3 Interfaces of reference point Ms + +Table 5 shows the interfaces of reference point Ms. + +**Table 5 – The interfaces of reference point Ms** + +| No. | Method | URI | Function | Interface provider | Interface caller | Protocol clause | +|-----|--------|---------------------|---------------------------------------------------------|--------------------|------------------|-----------------| +| 1 | GET | /ATS/Resource | Resource status querying | SMU | ATM | 9.6 | +| 2 | GET | /ATS/DataSet | Dataset information querying based on conditions | SMU | ATM | 9.7 | +| 3 | POST | /ATS/AnnotationTask | Data annotation task creation | SMU | ATM | 9.8 | +| 4 | PUT | /ATS/AnnotationTask | Data annotation task controlling (e.g., start and stop) | SMU | ATM | 9.9 | +| 5 | DELETE | /ATS/AnnotationTask | Data annotation task deletion | SMU | ATM | 9.10 | +| 6 | GET | /ATS/AnnotationTask | Data annotation task querying based on conditions | SMU | ATM | 9.11 | + +### 8.4 Interfaces of reference point Ta + +Table 6 shows the interfaces of reference point Ta. + +**Table 6 – The interfaces of reference point Ta** + +| No. | Method | URI | Function | Interface provider | Interface caller | Protocol clause | +|-----|--------|----------------|--------------------------------------------------|--------------------|------------------|-----------------| +| 1 | GET | /ATS/Resource | Resource status querying | TMU | ATM | 9.6 | +| 2 | POST | /ATS/TrainTask | Training task creation | TMU | ATM | 9.12 | +| 3 | PUT | /ATS/TrainTask | Training task controlling (e.g., start and stop) | TMU | ATM | 9.13 | +| 4 | DELETE | /ATS/TrainTask | Training task deletion | TMU | ATM | 9.14 | +| 5 | GET | /ATS/TrainTask | Training task querying based on conditions | TMU | ATM | 9.15 | + +### 8.5 Interfaces of reference point Tu + +Table 7 shows the interfaces of reference point Tu. + +**Table 7 – The interfaces of reference point Tu** + +| No. | Method | URI | Function | Interface provider | Interface caller | Protocol clause | +|-----|--------|----------------------|----------------------------------------------------------|--------------------|------------------|-----------------| +| 1 | GET | /ATS/Resource | Resource status querying | AMU | ATM | 9.6 | +| 2 | GET | /ATS/Model | Model list querying based on conditions | AMU | ATM | 9.16 | +| 3 | POST | /ATS/ModelDeployTask | Model deployment task creation | AMU | ATM | 9.17 | +| 4 | PUT | /ATS/ModelDeployTask | Model deployment task controlling (e.g., start and stop) | AMU | ATM | 9.18 | +| 5 | DELETE | /ATS/ModelDeployTask | Model deployment task deletion | AMU | ATM | 9.19 | +| 6 | GET | /ATS/ModelDeployTask | Model deployment task querying based on conditions | AMU | ATM | 9.20 | + +### 8.6 Interfaces of reference point Md + +SMU is required to support obtaining video and image information from DSS through the interface defined in [ITU-T H.627.3]. + +### 8.7 Interfaces of reference point Mm + +SMU is required to support obtaining media from MS through the interface defined in [ITU-T H.627]. + +### 8.8 Interfaces of reference point Ts + +TMU is required to support obtaining media from SMU through the interface defined in [ITU-T H.627]. + +### 8.9 Interfaces of reference point Ts' + +TMU is required to support obtaining video and image information from SMU through the interface defined in [ITU-T H.627.3]. + +### 8.10 Interfaces of reference point Tm + +Table 8 shows the interfaces of reference point Tm. + +**Table 8 – The interfaces of reference point Tm** + +| No. | Method | URI | Function | Interface provider | Interface caller | Protocol clause | +|-----|--------|---------------------------|----------------------|--------------------|------------------|-----------------| +| 1 | POST | /ATS/Model | Model creation | AMU | TMU | 9.21 | +| 2 | PUT | /ATS/Model//Data | Model data uploading | AMU | TMU | 9.22 | + +### 8.11 Interfaces of reference point Mv + +Table 9 shows the interfaces of reference point Mv. + +**Table 9 – The interfaces of reference point Mv** + +| No. | Method | URI | Function | Interface provider | Interface caller | Protocol clause | +|-----|--------|---------------------------|---------------------|--------------------|------------------|-----------------| +| 1 | POST | /ATS/ModelDeploy | Model deployment | IVU | AMU | 9.23 | +| 2 | GET | /ATS/Model//Data | Model data download | AMU | IVU | 9.24 | + +## 8.12 Interfaces of reference point Mi + +Table 10 shows the interfaces of reference point Mi. + +**Table 10 – The interfaces of reference point Mi** + +| No. | Method | URI | Function | Interface provider | Interface caller | Protocol clause | +|-----|--------|---------------------------|---------------------|--------------------|------------------|-----------------| +| 1 | POST | /ATS/ModelDeploy | Model deployment | IPU | AMU | 9.23 | +| 2 | GET | /ATS/Model//Data | Model data download | AMU | IPU | 9.24 | + +# 9 Relevant protocol definitions + +## 9.1 Protocol of interface POST /ATS/Register + +Table 11 shows the protocol of interface POST /ATS/Register. + +**Table 11 – Protocol of interface POST /ATS/Register** + +| | | | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/Register | | | +| Function | Registration | | | +| Method | Query string | Request message body | Response message body | +| POST | None | | | +| Annotation | 1) The definition of Register is described in clause A.2.
    2) The definition of ResponseStatus is described in clause A.1.
    3) Registration is required before the service caller send a request command to the service provider; the command can be sent only after successful registration; the regular keep-alive is required to be performed; if the keep-alive fails, the registration is required to be re-performed.
    4) The registration command is required to support redirection; after successfully registering with the new address according to the redirection requirements, subsequent commands is required to be sent to the new address. | | | + +## 9.2 Protocol of interface POST /ATS/DeRegister + +Table 12 shows the protocol of interface POST /ATS/DeRegister. + +**Table 12 – Protocol of interface POST /ATS/DeRegister** + +| | | | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/DeRegister | | | +| Function | De-registration | | | +| Method | Query string | Request message body | Response message body | +| POST | None | | | +| Annotation | 1) The definition of DeRegister is described in clause A.3;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.3 Protocol of interface POST /ATS/Keepalive + +Table 13 shows the protocol of interface POST /ATS/Keepalive. + +**Table 13 – Protocol of interface POST /ATS/Keepalive** + +| | | | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/Keepalive | | | +| Function | Keepalive | | | +| Method | Query string | Request message body | Response message body | +| POST | None | | | +| Annotation | 1) It is required to support regularly keep-alive after successful registration;
    2) It is required to support re-connect registration after unsuccessful keep alive;
    3) The definition of Keepalive is described in clause A.4;
    4) The definition of ResponseStatus is described in clause A.1. | | | + +## 9.4 Protocol of interface POST /ATS/TimeSync + +Table 14 shows the protocol of interface POST /ATS/TimeSync. + +**Table 14 – Protocol of interface POST /ATS/TimeSync** + +| | | | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/TimeSync | | | +| Function | Time synchronization | | | +| Method | Query string | Request message body | Response message body | +| POST | None | | | +| Annotation | 1) Each functional entity is required to keep time synchronization; if there is a time synchronization issue, this command is required to be used to calibrate the system time.
    2) The definition of TimeSync is described in clause A.5.
    3) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.5 Protocol of interface GET /ATS/Device + +Table 15 shows the protocol of interface GET /ATS/Device. + +**Table 15 – Protocol of interface GET /ATS/Device** + +| | | | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|----------------------------------| +| URI | /ATS/Device | | | +| Function | Device list information querying based on conditions | | | +| Method | Query string | Request message body | Response message body | +| GET | DeviceID=xx&Device Name=xx&Manufacturer=xx&DeviceModel=xx&ArchType=xx&Acce lType=xx&AlgType=xx&ModelID=xx&Mode lName=xx&Provider=xx&ModelVersion=xx&Begin=xx&Count=xx | None |
    | +| Annotation | 1) It can optionally support specific fields filtering such as DeviceID, and DeviceName, etc.; these definitions are described in clauses A.6 and A.8; multiple values are required to be supported for each field, separated by commas.
    2) It can optionally support pagination queries, starting from Begin to query the number of Count devices; if the returned DeviceList array size is less than Count, it indicates the end of pagination.
    3) If the query fails, return ResponseStatus; if the query succeeds, return DeviceList.
    4) The definition of DeviceList is described in clause A.9.
    5) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.6 Protocol of interface GET /ATS/Resource + +Table 16 shows the protocol of interface GET /ATS/Resource. + +**Table 16 – Protocol of interface GET /ATS/Resource** + +| | | | | +|-------------------|---------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/Resource | | | +| Function | System resource status querying | | | +| Method | Query string | Request message body | Response message body | +| GET | None | None | | +| Annotation | The definition of Resource is described in clause A.10. | | | + +### 9.7 Protocol of interface GET /ATS/DataSet + +Table 17 shows the protocol of interface GET /ATS/DataSet. + +**Table 17 – Protocol of interface GET /ATS/DataSet** + +| | | | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------------------| +| URI | /ATS/DataSet | | | +| Function | Dataset information querying based on conditions | | | +| Method | Query string | Request message body | Response message body | +| GET | DataSetID=xx&Begin=xx&Count=xx | None |
    | +| Annotation | 1) It can optionally support specific fields filtering through DataSetID, etc.; the definitions are described in clause A.11; multiple values are required to be supported for each field, separated by commas.
    2) It can optionally support pagination queries, starting from Begin to query the number of Count devices; if the returned DeviceSetList array size is less than Count, it indicates the end of pagination.
    3) If the query fails, return ResponseStatus; if the query succeeds, return DeviceSetList.
    4) The definition of DataSetList is described in clause A.12.
    5) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.8 Protocol of interface POST /ATS/AnnotationTask + +Table 18 shows the protocol of interface POST /ATS/AnnotationTask. + +**Table 18 – Protocol of interface POST /ATS/AnnotationTask** + +| | | | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/AnnotationTask | | | +| Function | Data annotation task creation | | | +| Method | Query string | Request message body | Response message body | +| POST | None | | | +| Annotation | 1) The definition of AnnotationTask is described in clause A.13;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.9 Protocol of interface PUT /ATS/AnnotationTask + +Table 19 shows the protocol of interface PUT /ATS/AnnotationTask. + +**Table 19 – Protocol of interface PUT /ATS/AnnotationTask** + +| | | | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/AnnotationTask | | | +| Function | Data annotation task controlling (e.g., start and stop) | | | +| Method | Query string | Request message body | Response message body | +| PUT | None | | | +| Annotation | 1) The definition of AnnotationTaskCtrl is described in clause A.15;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.10 Protocol of interface DELETE /ATS/AnnotationTask + +Table 20 shows the protocol of interface DELETE /ATS/AnnotationTask. + +**Table 20 – Protocol of interface DELETE /ATS/AnnotationTask** + +| | | | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/AnnotationTask | | | +| Function | Data annotation task deletion | | | +| Method | Query string | Request message body | Response message body | +| DELETE | TaskID=xx | None | | +| Annotation | 1) The TaskID is required to be supported; the definition is described in clause A.13;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.11 Protocol of interface GET /ATS/AnnotationTask + +Table 21 shows the protocol of interface GET /ATS/AnnotationTask. + +**Table 21 – Protocol of interface GET /ATS/AnnotationTask** + +| | | | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------------------| +| URI | /ATS/AnnotationTask | | | +| Function | Data annotation task querying based on conditions | | | +| Method | Query string | Request message body | Response message body | +| GET | TaskID=xx&Begin=xx
    &Count=xx | None |
    | +| Annotation | 1) It can optionally support specific fields filtering through TaskID, etc.; the definitions are described in clause A.14; multiple values are required to be supported for each field, separated by commas.
    2) It can optionally support pagination queries, starting from Begin to query the number of Count devices; if the returned AnnotationTaskList array size is less than Count, it indicates the end of pagination.
    3) If the query fails, return ResponseStatus; if the query succeeds, return AnnotationTaskList.
    4) The definition of AnnotationTaskList is described in clause A.14.
    5) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.12 Protocol of interface POST /ATS/TrainTask + +Table 22 shows the protocol of interface POST /ATS/TrainTask. + +**Table 22 – Protocol of interface POST /ATS/TrainTask** + +| | | | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/TrainTask | | | +| Function | Training task creation | | | +| Method | Query string | Request message body | Response message body | +| POST | None | | | +| Annotation | 1) The definition of TrainTask is described in clause A.16;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.13 Protocol of interface PUT /ATS/TrainTask + +Table 23 shows the protocol of interface PUT /ATS/TrainTask. + +**Table 23 – Protocol of interface PUT /ATS/TrainTask** + +| | | | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/TrainTask | | | +| Function | Training task controlling (e.g., start and stop) | | | +| Method | Query string | Request message body | Response message body | +| PUT | None | | | +| Annotation | 1) The definition of TrainTaskCtrl is described in clause A.18;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.14 Protocol of interface DELETE /ATS/TrainTask + +Table 24 shows the protocol of interface DELETE /ATS/TrainTask. + +**Table 24 – Protocol of interface DELETE /ATS/TrainTask** + +| | | | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/TrainTask | | | +| Function | Training task deletion | | | +| Method | Query string | Request message body | Response message body | +| DELETE | TaskID=xx | None | | +| Annotation | 1) The TaskID is required to be supported; the definition is described in clause A.16;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.15 Protocol of interface GET /ATS/TrainTask + +Table 25 shows the protocol of interface GET /ATS/TrainTask. + +**Table 25 – Protocol of interface GET /ATS/TrainTask** + +| | | | | +|-----------------|--------------------------------------------|-----------------------------|-------------------------------------| +| URI | /ATS/TrainTask | | | +| Function | Training task querying based on conditions | | | +| Method | Query string | Request message body | Response message body | +| GET | TaskID=xx&Begin=xx
    &Count=xx | None |
    | + +**Table 25 – Protocol of interface GET /ATS/TrainTask** + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Annotation | 1) It can optionally support specific fields filtering through TaskID, etc.; the definitions are described in clause A.16; multiple values are required to be supported for each field, separated by commas.
    2) It can optionally support pagination queries, starting from Begin to query the number of Count devices; if the returned TrainTaskList array size is less than Count, it indicates the end of pagination.
    3) If the query fails, return ResponseStatus; if the query succeeds, return TrainTaskList.
    4) The definition of TrainTaskList is described in clause A.17.
    5) The definition of ResponseStatus is described in clause A.1. | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### **9.16 Protocol of interface GET /ATS/Model** + +Table 26 shows the protocol of interface GET /ATS/Model. + +**Table 26 – Protocol of interface GET /ATS/Model** + +| | | | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------------| +| URI | /ATS/Model | | | +| Function | Model list querying based on conditions | | | +| Method | Query string | Request message body | Response message body | +| GET | ArchType=xx&accelType=xx&AlgType=xx&ModelID=xx&ModelName=xx&Provider=xx&ModelVersion=xx&Begin=xx&Count=xx | None |
    | +| Annotation | 1) It can optionally support specific fields filtering such as ArchType, and accelType, etc.; the definitions are described in clause A.6; multiple values are required to be supported for each field, separated by commas.
    2) It can optionally support pagination queries, starting from Begin to query the number of Count devices; if the returned ModelList array size is less than Count, it indicates the end of pagination.
    3) If the query fails, return ResponseStatus; if the query succeeds, return ModelList.
    4) The definition of ModelList is described in clause A.7.
    5) The definition of ResponseStatus is described in clause A.1. | | | + +### **9.17 Protocol of interface POST /ATS/ModelDeployTask** + +Table 27 shows the protocol of interface POST /ATS/ModelDeployTask. + +**Table 27 – Protocol of interface POST /ATS/ModelDeployTask** + +| | | | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/ModelDeployTask | | | +| Function | Model deployment task creation | | | +| Method | Query string | Request message body | Response message body | +| POST | None | | | +| Annotation | 1) The definition of ModelDeployTask is described in clause A.19;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.18 Protocol of interface PUT /ATS/ModelDeployTask + +Table 28 shows the protocol of interface PUT /ATS/ModelDeployTask. + +**Table 28 – Protocol of interface PUT /ATS/ModelDeployTask** + +| | | | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/ModelDeployTask | | | +| Function | Model deployment task controlling (e.g., start and stop) | | | +| Method | Query string | Request message body | Response message body | +| PUT | None | | | +| Annotation | 1) The definition of ModelDeployTaskCtrl is described in clause A.21;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.19 Protocol of interface DELETE /ATS/ModelDeployTask + +Table 29 shows the protocol of interface DELETE /ATS/ModelDeployTask. + +**Table 29 – Protocol of interface DELETE /ATS/ModelDeployTask** + +| | | | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/ModelDeployTask | | | +| Function | Model deployment task deletion | | | +| Method | Query string | Request message body | Response message body | +| DELETE | TaskID=xx | None | | +| Annotation | 1) The TaskID is required to be supported; the definition is described in clause A.19;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.20 Protocol of interface GET /ATS/ModelDeployTask + +Table 30 shows the protocol of interface GET /ATS/ModelDeployTask. + +**Table 30 – Protocol of interface GET /ATS/ModelDeployTask** + +| | | | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-------------------------------------------| +| URI | /ATS/ModelDeployTask | | | +| Function | Model deployment task querying based on conditions | | | +| Method | Query string | Request message body | Response message body | +| GET | TaskID=xx&Begin=xx
    &Count=xx | None |
    | +| Annotation | 1) It can optionally support specific fields filtering such as TaskID, etc.; the definition is described in clause A.19; multiple values are required to be supported for each field, separated by commas.
    2) It can optionally support pagination queries, starting from Begin to query the number of Count devices; if the returned ModelDeployTaskList array size is less than Count, it indicates the end of pagination.
    3) If the query fails, return ResponseStatus; if the query succeeds, return ModelDeployTaskList.
    4) The definition of ModelDeployTaskList is described in clause A.20.
    5) The definition of ResponseStatus is described in clause A.1. | | | + +### 9.21 Protocol of interface POST /ATS/Model + +Table 31 shows the protocol of interface POST /ATS/Model. + +**Table 31 – Protocol of interface POST /ATS/Model** + +| | | | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/Model | | | +| Function | Model creation | | | +| Method | Query string | Request message body | Response message body | +| POST | None | | | +| Annotation | 1) The definition of Model is described in clause A.6;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +### **9.22 Protocol of interface PUT /ATS/Model//Data** + +Table 32 shows the protocol of interface PUT /ATS/Model//Data. + +**Table 32 – Protocol of interface PUT /ATS/Model//Data** + +| | | | | +|-------------------|--------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/Model//Data | | | +| Function | Model data uploading | | | +| Method | Query string | Request message body | Response message body | +| PUT | None | | | +| Annotation | The definition of ResponseStatus is described in clause A.1. | | | + +### **9.23 Protocol of interface POST /ATS/ModelDeploy** + +Table 33 shows the protocol of interface POST /ATS/ModelDeploy. + +**Table 33 – Protocol of interface POST /ATS/ModelDeploy** + +| | | | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------| +| URI | /ATS/ModelDeploy | | | +| Function | Model deployment | | | +| Method | Query string | Request message body | Response message body | +| POST | None | | | +| Annotation | 1) The definition of Model is described in clause A.6;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +## **9.24 Protocol of interface GET /ATS/Model//Data** + +Table 34 shows the protocol of interface GET /ATS/Model//Data. + +**Table 34 – Protocol of interface GET /ATS/Model//Data** + +| | | | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------------------| +| URI | /ATS/Model//Data | | | +| Function | Model data download | | | +| Method | Query string | Request message body | Response message body | +| GET | None | None |
    | +| Annotation | 1) If the download fails, return ResponseStatus; if the download succeeds, return Model data;
    2) The definition of ResponseStatus is described in clause A.1. | | | + +# Annex A + +## Object descriptions + +(This annex forms an integral part of this Recommendation.) + +### A.1 ResponseStatus + +Table A.1 shows the object descriptions of ResponseStatus. + +**Table A.1 – Object descriptions of ResponseStatus** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|------------------------------------------------------------------------------------| +| ErrCode | Integer | Required | Error code; 0 indicates success, others indicate failure. | +| ErrMsg | String | Optional | Error message. | +| ObjectID | String | Optional | If the command is to generate an object, return the identifier (ID) of the object. | + +### A.2 Register + +Table A.2 shows the object descriptions of Register. + +**Table A.2 – Object descriptions of Register** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|---------------------------------------------------| +| AppId | String | Required | Provide functional entity ID when registering. | +| AppType | String | Required | Provide functional entity types when registering. | + +### A.3 DeRegister + +Table A.3 shows the object descriptions of DeRegister. + +**Table A.3 – Object descriptions of DeRegister** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|---------------------------------------------------| +| AppId | String | Optional | Provide functional entity ID when de-registering. | + +### A.4 Keepalive + +Table A.4 shows the object descriptions of Keepalive. + +**Table A.4 – Object descriptions of Keepalive** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|-------------------------------------------------| +| AppId | String | Required | Provide functional entity ID during keep-alive. | + +### A.5 TimeSync + +Table A.5 shows the object descriptions of TimeSync. + +**Table A.5 – Object descriptions of TimeSync** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SyncMode | Integer | Required | Time synchronization mode; 1 indicates network time protocol (NTP) service timing, 2 indicates manual timing. | +| NtpServer | String | Required | When SyncMode is set to 1, it is valid and provides the IP address or domain name of the NTP timing server; multiple addresses are separated by comma. | +| DateTime | String | Optional | When SyncMode is set to 2, it is valid and the value is the set time, the format in required to comply with [ISO 8601-1]; for example: YYYY-MM-DDTHH:MM:SS.sss. | + +### A.6 Model + +Table A.6 shows the object descriptions of Model. + +**Table A.6 – Object descriptions of Model** + +| Parameter | Data type | Mandatory | Description | +|--------------|-----------|-----------|----------------------| +| AlgType | String | Required | Algorithm functions. | +| ModelID | String | Required | Model ID. | +| ModelName | String | Optional | Model name. | +| Provider | String | Optional | Model provider. | +| ModelVersion | String | Optional | Model version. | +| Description | String | Optional | Model descriptions. | + +### A.7 ModelList + +Table A.7 shows the object descriptions of ModelList. + +**Table A.7 – Object descriptions of ModelList** + +| Parameter | Data type | Mandatory | Description | +|-----------|------------------|-----------|----------------------------| +| ModelList | Array
    | Required | List of model information. | + +### A.8 Device + +Table A.8 shows the object descriptions of Device. + +**Table A.8 – Object descriptions of Device** + +| Parameter | Data type | Mandatory | Description | +|-------------|------------------|-----------|------------------------------------------| +| DeviceID | String | Required | Device ID. | +| DeviceName | String | Optional | Device name. | +| Manufacture | String | Optional | Device manufacturer. | +| DeviceModel | String | Optional | Device model. | +| IpAddr | String | Required | Device IP addresses. | +| Port | String | Required | Device port. | +| ArchType | String | Optional | Hardware architecture types of device. | +| AccelType | String | Optional | AI hardware accelerator types of device. | +| ModelList | Array
    | Required | Model list under deployment. | + +### A.9 DeviceList + +Table A.9 shows the object descriptions of DeviceList. + +**Table A.9 – Object descriptions of DeviceList** + +| Parameter | Data type | Mandatory | Description | +|------------|-------------------|-----------|-----------------------------| +| DeviceList | Array
    | Required | List of device information. | + +### A.10 Resource + +Table A.10 shows the object descriptions of Resource. + +**Table A.10 – Object descriptions of Resource** + +| Parameter | Data type | Mandatory | Description | +|--------------|-----------|-----------|------------------------------------------------------| +| TotalCpuCore | Integer | Required | Total number of central processing unit (CPU) cores. | +| UsedCpuCore | Integer | Required | Number of used CPU cores. | +| TotalMemory | Float | Optional | Total memory, unit is GB. | +| UsedMemory | Float | Optional | Used memory, unit is GB. | +| TotalGpuCard | Integer | Optional | Total number of graphics processing unit (GPU). | +| UsedGpuCard | Integer | Optional | Number of used GPU. | +| TotalDisk | Float | Optional | Total number of disk, unit is GB. | +| UsedDisk | Float | Optional | Used disk, unit is GB. | + +### A.11 DataSet + +Table A.11 shows the object descriptions of DataSet. + +**Table A.11 – Object descriptions of DataSet** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|------------------------------------------------------| +| DataSetID | String | Required | Dataset ID. | +| Name | String | Optional | Dataset name. | +| Desc | String | Optional | Dataset descriptions. | +| SampleNum | Integer | Optional | Number of sample in dataset, response when querying. | + +### A.12 DataSetList + +Table A.12 shows the object descriptions of DataSetList. + +**Table A.12 – Object descriptions of DataSetList** + +| Parameter | Data type | Mandatory | Description | +|-------------|--------------------|-----------|------------------------------| +| DataSetList | Array
    | Required | List of dataset information. | + +### A.13 AnnotationTask + +Table A.13 shows the object descriptions of AnnotationTask. + +**Table A.13 – Object descriptions of AnnotationTask** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|--------------------------------------------------------------------------------------------------------------------| +| TaskID | String | Required | Annotation task ID. | +| DataSetID | String | Required | Dataset ID for annotation. | +| Status | String | Optional | Task execution status; return task execution status when querying, including running, paused, finished and failed. | +| Progress | Integer | Optional | Percentage of task execution status, valid during query, from 0 to 100. | + +### A.14 AnnotationTaskList + +Table A.14 shows the object descriptions of AnnotationTaskList. + +**Table A.14 – Object descriptions of AnnotationTaskList** + +| Parameter | Data type | Mandatory | Description | +|--------------------|---------------------------|-----------|--------------------------------------| +| AnnotationTaskList | Array
    | Required | List of annotation task information. | + +### A.15 AnnotationTaskCtrl + +Table A.15 shows the object descriptions of AnnotationTaskCtrl. + +**Table A.15 – Object descriptions of AnnotationTaskCtrl** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|------------------------------------------------| +| TaskID | String | Required | Annotation task ID. | +| Cmd | String | Required | Controlling command, including start and stop. | + +### A.16 TrainTask + +Table A.16 shows the object descriptions of TrainTask. + +**Table A.16 – Object descriptions of TrainTask** + +| Parameter | Data type | Mandatory | Description | +|------------|-----------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TaskID | String | Required | Training task ID. | +| DataSetID | String | Required | Training dataset ID. | +| SrcModelID | String | Required | ID of Model before training. | +| DstModelID | String | Required | ID of trained Model. | +| Status | String | Optional | Task execution status; return task execution status when querying, including running, uploading, uploaded, training failed, and uploading failed. | +| Progress | Integer | Optional | Percentage of task execution status, valid during query, from 0 to 100. | + +### A.17 TrainTaskList + +Table A.17 shows the object descriptions of TrainTaskList. + +**Table A.17 – Object descriptions of TrainTaskList** + +| Parameter | Data type | Mandatory | Description | +|---------------|----------------------|-----------|------------------------------------| +| TrainTaskList | Array
    | Required | List of training task information. | + +### A.18 TrainTaskCtrl + +Table A.18 shows the object descriptions of TrainTaskCtrl. + +**Table A.18 – Object descriptions of TrainTaskCtrl** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|------------------------------------------------| +| TaskID | String | Required | Training task ID. | +| Cmd | String | Required | Controlling command, including start and stop. | + +### A.19 ModelDeployTask + +Table A.19 shows the object descriptions of ModelDeployTask. + +**Table A.19 – Object descriptions of ModelDeployTask** + +| Parameter | Data type | Mandatory | Description | +|------------|-------------------|-----------|-------------------------------------------------------------------------------------------------------------| +| TaskID | String | Required | Model deployment task ID. | +| DeviceList | Array
    | Required | List of target devices for deployment. | +| Model | Model | Required | Information of model for deployment. | +| Status | String | Optional | Task execution status; return task execution status when querying, including running, finished, and failed. | +| Progress | Integer | Optional | Percentage of task execution status, valid during query, from 0 to 100. | + +### A.20 ModelDeployTaskList + +Table A.20 shows the object descriptions of ModelDeployTaskList. + +**Table A.20 – Object descriptions of ModelDeployTaskList** + +| Parameter | Data type | Mandatory | Description | +|---------------------|----------------------------|-----------|--------------------------------------------| +| ModelDeployTaskList | Array
    | Required | List of model deployment task information. | + +### A.21 ModelDeployTaskCtrl + +Table A.21 shows the object descriptions of ModelDeployTaskCtrl. + +**Table A.21 – Object descriptions of ModelDeployTaskCtrl** + +| Parameter | Data type | Mandatory | Description | +|-----------|-----------|-----------|------------------------------------------------| +| TaskID | String | Required | Model deployment task ID. | +| Cmd | String | Required | Controlling command, including start and stop. | + +# Bibliography + +- [b-IETF JSON] Internet Engineering Task Force (2022), *JSON schema: A media type for describing JSON documents*. + +- [b-ISO/IEC 11557] ISO/IEC 11557:1992, *Information technology – 3,81 mm wide magnetic tape cartridge for information interchange – Helical scan recording – DDS-DC format using 60 m and 90 m length tapes*. +- [b-ISO/IEC TR 29119-11] ISO/IEC TR 29119-11:2020, *Software and systems engineering – Software testing – Part 11: Guidelines on the testing of AI-based systems*. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/raw.md b/marked/H/T-REC-H.643.1-201905-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..66b41cb3b80af031d5922a10f53451392504c2c4 --- /dev/null +++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/raw.md @@ -0,0 +1,626 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.643.1** + +(05/2019) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Broadband, triple-play and advanced multimedia services – Ubiquitous sensor network applications and Internet of Things + +--- + +**Architecture for the deployment of information-centric networks** + +Recommendation ITU-T H.643.1 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a stylized globe with a red lightning bolt striking across it. The letters "ITU" are prominently displayed in blue and white within the globe. + +ITU logo + +International +Telecommunication +Union + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.643.1 + +# Architecture for the deployment of information-centric networks + +## Summary + +Recommendation ITU-T H.643.1 describes the functional architecture for the deployment of information-centric networks (DICNs), including functional entities, reference points and service control flows. It also describes the required DICN capabilities. This architecture can be used to flexibly support the deployment of any particular information-centric network instance and the coexistence of multiple ICN instances on top of one physical network. It also facilitates the inter-operation between different ICN instances. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.643.1 | 2019-05-14 | 16 | 11.1002/1000/13906 | + +## Keywords + +Architecture, deployment, information-centric networks, inter-operation + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2019 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview..... | 2 | +| 7 Required DICN capabilities..... | 2 | +| 7.1 Name-based content delivery ..... | 2 | +| 7.2 In-network cache ..... | 3 | +| 7.3 Coexistence..... | 3 | +| 7.4 Inter-operation ..... | 3 | +| 7.5 Security ..... | 3 | +| 8 Functional architecture for DICN ..... | 4 | +| 8.1 Functional architecture ..... | 4 | +| 8.2 Functional entities in DICN..... | 5 | +| 8.3 Reference points ..... | 6 | +| 8.4 Service control flows ..... | 7 | +| Bibliography..... | 14 | + + + +# Recommendation ITU-T H.643.1 + +## Architecture for the deployment of information-centric networks + +## 1 Scope + +This Recommendation describes the architecture for the deployment of information-centric networks (DICNs), which satisfies the requirements described in [ITU-T F.746.4]. + +This Recommendation covers the following: + +- functional architecture for DICN; +- functional entities, reference points and service control flows of DICNs. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T F.746.4] Recommendation ITU-T F.746.4 (2017), *Requirements for deployment of information-centric network*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 functional architecture** [b-ITU-T Y.2012]: A set of functional entities, and the reference points between them used to describe the structure of an NGN. These functional entities are separated by reference points, and thus, they define the distribution of functions. + +NOTE 1 – The functional entities can be used to describe a set of reference configurations. These reference configurations identify which reference points are visible at the boundaries of equipment implementation and between administrative domains. + +NOTE 2 – The definition is not only applicable to NGNs but also to other IP packet-switch-based networks. + +**3.1.2 functional entity** [b-ITU-T Y.2012]: An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. + +**3.1.3 interface** [b-ITU-T Y.101]: A shared boundary between two functional units. + +NOTE – An interface is defined by various characteristics pertaining to the functions, physical interconnections, signal exchanges, and other characteristics as appropriate. + +**3.1.4 reference point** [b-ITU-T Y.2012]: A conceptual point at the conjunction of two non-overlapping functional entities that can be used to identify the type of information passing between these functional entities. + +NOTE – A reference point may correspond to one or more physical interfaces between pieces of equipment. + +**3.1.5 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications. + +### 3.2 Terms defined in this Recommendation + +None + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +DICN Deployment of Information-Centric Network + +ICN Information-Centric Network + +## 5 Conventions + +In this Recommendation: + +- The expression "is required to" indicates a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. +- The expression "is recommended" indicates a requirement which is recommended but not absolutely required. Thus, this requirement need not be present to claim conformance. + +## 6 Overview + +This Recommendation describes the architecture for the deployment of information-centric networks (DICNs), which satisfies the requirements described in [ITU-T F.746.4]. This Recommendation includes the required DICN capabilities and functional architecture for DICNs (including functional entities, reference points and service control flows of DICNs). + +Currently, the deployment of information-centric networks (ICNs) has attracted considerable attention. However, there are too many ICN candidates, each of which has its own design principles and technical details in terms of naming, routing, and so on ([b-ITU-T Y.3033], [b-Dannewitz], [b-Jacobson], [b-Sarela], [b-Seskar], [b-Detti]). These ICN candidates have their own pros and cons, each of which is best suited to particular application requirements. Thus, it is highly likely that different ICN service providers will implement their own ICN instants with different ICN candidates to provide specific services to users. However, using dedicated physical resources to deploy each individual ICN instants is a waste of resource. Thus, it is reasonable that various ICN instances will coexist on top of one physical network. What is more, there is a scenario that a client of one ICN instance needs to access the resources provided by the server belongs to another ICN instance. In this case, to provide efficient content delivery services, the inter-operation between different ICN instances is also needed. + +The architecture for deployment of information-centric networks (DICNs) aims to enable multiple ICN instances' coexistence to provide efficient content delivery services to users. + +## 7 Required DICN capabilities + +This clause describes the required DICN capabilities, i.e., name-based content delivery, in-network cache, coexistence, inter-operation and security. + +### 7.1 Name-based content delivery + +The capability of name-based content delivery is responsible for delivering content based on the content name. In an information-centric network a user can directly obtain a content object by its name (or identification), without specifying the location of the content object. For each user's request, the network also needs to find the appropriate holder to provide the content to the user according to the content name. + +### **7.2 In-network cache** + +The capability of in-network cache is responsible for caching content in routers or switches, and for providing the content to the users from a nearby cache. Routers or switches equipped with caches need to store copies of traversed content objects and respond to subsequent content requests with the cached copies, which will significantly reduce bandwidth consumption and server load. + +### **7.3 Coexistence** + +The capability of coexistence is responsible for enabling multiple ICN instances, each of which can employ different ICN architecture candidates to coexist in one physical network. The physical resources are virtualized into different slices, each of which is dedicated to a particular ICN instance. The packets for each ICN instance needs to be delivered according to particular protocols and not be affected by other ICN instances. + +### **7.4 Inter-operation** + +The capability of inter-operation is responsible for enabling an ICN user which adopts one ICN candidate to obtain content from another one which adopts another different ICN candidate. The DICN needs to handle the difference between different ICN protocols, including the difference of packet format, protocol procedure and so on. + +### **7.5 Security** + +The capability of security is responsible for providing a secure service, including authentication and authorization. The DICN needs to verify whether or not the user can access the content. A DICN client can only access the content that it is permitted to access. + +# 8 Functional architecture for DICN + +![Functional architecture for DICN diagram showing Controller and Switch components with ICN instances and their internal managers.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +The diagram illustrates the functional architecture for DICN, divided into two main parts: the Controller and the Switch. + +**Controller supporting the deployment:** This part contains two ICN instances, ICN instance 1 and ICN instance 2, and an ICN instance manager-controller part. + +- ICN instance 1:** Contains Storage manager, Inter-operation manager, Content manager, Routing manager, and Security manager. +- ICN instance 2:** Contains Inter-operation manager, Storage manager, Routing manager, Content manager, and Security manager. +- ICN instance manager-controller part:** A central component that connects to both ICN instances via reference points *lins* (upward) and *lins'* (downward). +- Inter-operation:** A reference point *lint* connects the Inter-operation managers of ICN instance 1 and ICN instance 2. + +**Switch supporting the deployment:** This part is divided into Software and Hardware layers. + +- Software layer:** Contains two ICN instances (labeled ICN instance 1) and an ICN instance manager-switch part. + - Each ICN instance contains Forwarding management, Inter-operation, and Storage management managers. + - Reference points *linss* (upward) and *linss'* (downward) connect each ICN instance to the ICN instance manager-switch part. + - A reference point *lint* connects the Inter-operation managers of the two ICN instances. + - The top ICN instance manager-switch part connects to the bottom one via reference points *Sc* (upward) and *Sc'* (downward). +- Hardware layer:** Contains Forwarding management logic, Forwarding table, Inter-operation logic, Storage management logic, and Storage. +- Interface:** A reference point *lhar* connects the bottom ICN instance manager-switch part to the Hardware layer. + +Functional architecture for DICN diagram showing Controller and Switch components with ICN instances and their internal managers. + +H.643.1(19)\_F8-1 + +**Figure 8-1 – Functional architecture for DICN** + +This clause describes the DICN functional components which are required to perform DICN functionalities. Figure 8-1 shows the functional architecture with the functional entities and reference points between different functional entities. To illustrate the coexistence of ICN instances and demonstrate the reference points for inter-operation there are two ICN instances shown in Figure 8-1. + +### 8.1 Functional architecture + +Figure 8-1 shows the functional architecture for DICNs. The DICN consists of two parts, the DICN controller and DICN switches. The DICN controller consists of the ICN instances manager (controller part) and various ICN instances each of which is created to conform to different ICN protocols. The DICN switch consists of the hardware part which supports the general ICN-related operations and the software part which is used to support the resource virtualization for the implementation and coexistence of multiple ICN instances. The ICN instances manager (switch part) also resides in DICN switches. + +## **8.2 Functional entities in DICN** + +#### **8.2.1 DICN controller** + +The DICN controller is designed to manage virtualized physical network resources for each ICN instance. There are five function modules provided to ICN service providers, as shown in Figure 8-1, including content manager, routing manager, storage manager, security manager and inter-operation manager. With these five function modules, each ICN service provider can deploy its own ICN instance according to the specification of a particular ICN architecture candidate by implementing appropriate modules. + +The content manager is the key unit for DICNs and is used to maintain information about content sources. If one DICN client hosts content, it should register this information to the content manager module in the DICN controller. + +The routing manager is used to maintain the topology of this ICN instance and performs ICN-related routing algorithms. Each ICN service provider can adopt its own routing algorithms to satisfy its own purposes. Then it should configure the DICN switches to perform the routing. + +The storage manager is used to set the policies for managing physical content storage. In DICNs, the content can be cached by intermediate node, i.e., routers and switches. ICN service providers can use this module to guide the DICN switches about where and how to cache this content to ensure DICN clients can retrieve the content from a nearby location. + +The security manager is responsible for providing secure service. As DICN clients can obtain the requested content from nearby routers or switches rather than the original content providers, to ensure that the content is not accessed by undesired users, the ICN service provider defines its own security policies and uses the security manager to verify the permissions. + +The inter-operation manager is used to guide the inter-operation with other ICN instances. Different ICN instances may have different naming schemes and operations. To retrieve content from a node which uses another ICN protocol, the inter-operation manager should establish the mapping between the different names of the same content and guide the DICN switches to deal with the differences of ICN operations. + +A typical ICN instance can be implemented in a centralized or distributed way. In the centralized way, the ICN service provider only selects one DICN controller to deploy its ICN instance. In this case all information, including content sources, topology and so on, should be submitted to this selected DICN controller. Otherwise, several DICN controllers can be used, each of which can hold parts of this information and cooperate to provide the required functions. + +To manage these different ICN instances, there is an ICN instances manager (controller part). It is responsible for creating an ICN instance according to the request of the ICN service provider and reserve resources for the ICN instance in the physical network. It is also used to deliver the packets (including configuration messages, user's request and data packets) to the corresponding ICN instance. + +#### **8.2.2 DICN switch** + +The DICN switch, which is responsible for forwarding packets belonging to different ICN instances, consists of the hardware and software parts. There are six hardware elements in the hardware part: switching element, forwarding table, storage, forwarding management logic, storage management logic and inter-operation logic, which are shared by different ICN instances. Such hardware resources are virtualized into different slices, each of which is dedicated to a particular ICN instance. The switch also provides interfaces, including forwarding management, storage management and inter-operation, to ICN instances to manage the resources allocated to them. The ICN instance manager (switch part) is responsible for distinguishing packets (including configuration messages, user's request, and data + +packets) belonging to different ICN instance received from controller and hardware, and delivering them to the corresponding ICN instance. + +## **8.3 Reference points** + +#### **8.3.1 Reference point Sc: DICN switch – DICN controller** + +The reference point is located between the ICN instance manager of the DICN switch and the ICN instance manager of the DICN controller. It is used to deliver the users' requests and packets from the DICN switch to the DICN controller. + +#### **8.3.2 Reference point Sc': DICN Controller – DICN switch** + +The reference point is located between the ICN instance manager of the DICN controller and the ICN instance manager of the DICN switch. It is used to deliver the configuration messages from the DICN controller to the DICN switch. + +#### **8.3.3 Reference point Iins: ICN instance manager (controller part) – ICN instance** + +The reference point is located between the ICN instance manager (controller part) and the ICN instances. It is used to deliver the users' requests, packets and configuration messages from the ICN instance manager to the corresponding ICN instance. Note that there are several "Iins" points in the DICN. + +#### **8.3.4 Reference point Iins': ICN instance – ICN instance manager (controller part)** + +The reference point is located between the ICN instances and the ICN instance manager (controller part). It is used to deliver the users' requests, packets and configuration messages from the ICN instances to the ICN instance manager. Note that there are several "Iins'" points in the DICN. + +#### **8.3.5 Reference point Iinss: ICN instance manager (switch part) – ICN instance** + +The reference point is located between the ICN instance manager (switch part) and the ICN instances. It is used to deliver the users' requests, packets and configuration messages from the ICN instance manager (switch part) to the corresponding ICN instance. Note that there are several "Iinss" points in the DICN. + +#### **8.3.6 Reference point Iinss': ICN instance – ICN instance manager (switch part)** + +The reference point is located between the ICN instances and the ICN instance manager (switch part). It is used to deliver the users' requests, packets and configuration messages from the ICN instances to the ICN instance manager (switch part). Note that there are several "Iinss'" points in DICN. + +#### **8.3.7 Reference point Iint: ICN instance - ICN instance** + +The reference point is located between different ICN instances. It is used to deliver inter-operation related controller messages. Note that there are several "Iint" points in the DICN. + +#### **8.3.8 Reference point Ihar: ICN instance manager of DICN switch – hardware** + +The reference point is located between the software part and hardware part of the DICN switch. It is used to deliver the users' requests, packets and configuration messages between the software and hardware part. + +### 8.4 Service control flows + +#### 8.4.1 ICN instance initialization + +![Sequence diagram illustrating the procedural flows for ICN instance initialization. The diagram shows three lifelines: DICN switch, DICN controller, and ICN service provider. The sequence of messages is: 1. Send instance initialization request (ICN service provider to DICN controller), 2. Send instance creation command (DICN controller to DICN switch), 3. Creation instance (self-call on DICN switch), 4. Reply with instance created message (DICN switch to DICN controller), 5. Create instance (self-call on DICN controller), 6. Reply with instance created message (DICN controller to ICN service provider).](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +``` +sequenceDiagram + participant ICN service provider + participant DICN controller + participant DICN switch + Note right of ICN service provider: H.643.1(19)_F8-2 + ICN service provider->>DICN controller: 1. Send instance initialization request + DICN controller->>DICN switch: 2. Send instance creation command + DICN switch->>DICN switch: 3. Creation instance + DICN switch->>DICN controller: 4. Reply with instance created message + DICN controller->>DICN controller: 5. Create instance + DICN controller->>ICN service provider: 6. Reply with instance created message +``` + +Sequence diagram illustrating the procedural flows for ICN instance initialization. The diagram shows three lifelines: DICN switch, DICN controller, and ICN service provider. The sequence of messages is: 1. Send instance initialization request (ICN service provider to DICN controller), 2. Send instance creation command (DICN controller to DICN switch), 3. Creation instance (self-call on DICN switch), 4. Reply with instance created message (DICN switch to DICN controller), 5. Create instance (self-call on DICN controller), 6. Reply with instance created message (DICN controller to ICN service provider). + +**Figure 8-2 – Procedural flows for ICN instance initialization** + +Figure 8-2 illustrates the steps for ICN instance initialization: + +- 1) First, the ICN service provider sends the ICN instance initialization request to the instance manager in the DICN controller. +- 2) The controller part of the ICN instances manager will verify the information and check the required resources to determine whether or not to accept this request. If the request is accepted, the controller part of the ICN instance manager will send the create instance command to the DICN switch. +- 3) The switch part of the ICN instance manager will create a new ICN instance and reserve the required resources in the DICN switches. +- 4) The switch part of the ICN instance manager replies with the instance created message to the controller part of the ICN instance manager. +- 5) The controller part of the ICN instance manager receives the response and creates a new ICN instance in the DICN controller. +- 6) The controller part of the ICN instances manager returns the information of the newly created instance to the ICN service provider. + +When the ICN instance is initialized, the ICN service provider sends the configuration information of the ICN instance, which is set based on its own specification, to the ICN instance manager (controller part). Then the ICN instance manager (controller part) configures the ICN instance in the controller which in turn configures the routing and caching policies in the ICN instance resided in the DICN switch. + +#### 8.4.2 Registration of topology information + +![Sequence diagram for topology registration](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg) + +A sequence diagram showing the interaction between a DICN controller (ICN instance) and a DICN switch. The DICN controller contains four internal components: Content manager, Routing manager, Storage manager, and Security manager. The sequence of messages is as follows: 1. The DICN switch sends a 'Send topology registration message' to the Routing manager. 2. The Routing manager replies with a 'Reply with registration success message'. 3. The DICN switch sends a 'Send keep alive message' to the Routing manager. 4. The Routing manager sends a 'Send keep alive message' back to the DICN switch. The diagram is labeled H.643.1(19)\_F8-3. + +Sequence diagram for topology registration + +**Figure 8-3 – Procedural flows for registration of topology information** + +Figure 8-3 shows the procedural flows for registration and deregistration of topology information: + +- 1) A DICN switch registers itself and the connection with its neighbours to the routing manager of the ICN instance in the DICN controller. +- 2) The routing manager replies with a registration success message and saves this topology information. +- 3) The DICN switch sends a "keep alive" message to the routing manager of the ICN instance periodically. If the routing manager cannot receive the "keep alive" message for a long time (e.g., 10s), it will delete the DICN switch from the topology maintained. +- 4) The routing manager also sends a "keep alive" message to the DICN switch. If the DICN switch cannot receive the "keep alive" message for a long time it will inform the network administrator. + +#### 8.4.3 Registration and deregistration of content + +![Sequence diagram for content registration and deregistration](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +A sequence diagram showing the interaction between a Content provider and a DICN controller (ICN instance). The DICN controller contains four internal components: Content manager, Routing manager, Storage manager, and Security manager. The sequence of messages is as follows: 1. The Content provider sends a 'Send content registration request' to the Content manager. 2. The Content manager replies with a 'Reply with registration success message'. 3. The Content provider sends a 'Send content deregistration request' to the Content manager. 4. The Content manager replies with a 'Reply with deregistration success message'. The diagram is labeled H.643.1(19)\_F8-4. + +Sequence diagram for content registration and deregistration + +**Figure 8-4 – Procedural flows for registration and deregistration of content** + +Figure 8-4 shows the procedural flows for registration and deregistration of content: + +- 1) The content provider registers the content which it holds to the content manager of the ICN instance in the DICN controller. +- 2) The content manager replies with the registration success message to the content providers. + +- 3) If the content provider will stop providing some content it can deregister the content by sending the content deregistration request. +- 4) The content manager of the controller replies with a deregistration success message. + +#### 8.4.4 Authentication and authorization + +![Sequence diagram showing procedural flows for authentication and authorization between four entities: Authentication and authorization server, Security manager in DICN controller, DICN switch, and DICN client. The sequence consists of six steps: 1. DICN client sends a verification request to the DICN switch; 2. The switch forwards it to the security manager; 3. The security manager forwards it to the authentication server; 4. The server replies with a basic token to the security manager; 5. The security manager sends an authorization token to the authentication server; 6. The security manager sends the authorization token to the DICN client. The diagram is labeled H.643.1(19)_F8-5.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +``` + +sequenceDiagram + participant AuthServer as Authentication and authorization server + participant SecMgr as Security manager in DICN controller + participant Switch as DICN switch + participant Client as DICN client + + Client->>Switch: 1. Send verification request + Switch->>SecMgr: 2. Send verification request + SecMgr->>AuthServer: 3. Send verification request + AuthServer->>SecMgr: 4. Reply with basic token + SecMgr->>AuthServer: 5. Send authorization token + SecMgr->>Client: 6. Send authorization token + +``` + +H.643.1(19)\_F8-5 + +Sequence diagram showing procedural flows for authentication and authorization between four entities: Authentication and authorization server, Security manager in DICN controller, DICN switch, and DICN client. The sequence consists of six steps: 1. DICN client sends a verification request to the DICN switch; 2. The switch forwards it to the security manager; 3. The security manager forwards it to the authentication server; 4. The server replies with a basic token to the security manager; 5. The security manager sends an authorization token to the authentication server; 6. The security manager sends the authorization token to the DICN client. The diagram is labeled H.643.1(19)\_F8-5. + +**Figure 8-5 – Procedural flows for authentication and authorization** + +Figure 8-5 shows the procedural flows for authentication and authorization: + +- 1) A new DICN client sends a user verification request to the DICN switch to verify whether the DICN client has the right to access the network and what content it can access. The verification request includes the DICN client's identity which identifies the current network location of the DICN client (such as the IP address, MAC address, etc.). +- 2) The DICN switch forwards the verification request to the security manager of the corresponding ICN instance in the DICN controller. +- 3) The security manager of the ICN instance forwards the verification request to the authentication and authorization server. +- 4) The authentication and authorization server performs user verification on the DICN client according to the verification request. If the DICN client passed verification the authentication and authorization server generates an encryption token (called basic token) according to the DICN client's identity and the content list that the DICN client can access, and it sends this token, which includes the identity and the content list, to the security manager of the ICN instance in the ICN controller. +- 5) The security manager extracts and saves the DICN client's identity and the content list that the DICN client can access from the received basic token. The security manager then uses its own key to generate a new encrypted token (called authorization token) based on the obtained information. It sends back this new generated encrypted token to the authentication and authorization server. +- 6) The security manager of the ICN instance also sends the new encrypted token, including the obtained information (i.e., contents list that the DICN client can access), to the DICN client. + +#### 8.4.5 Content delivery + +![Sequence diagram showing content delivery with local cache. Lifelines: DICN controller: ICN instance (containing Content manager, Routing manager, Storage manager, Security manager), DICN switch, and DICN client. The sequence is: 1. DICN client sends a content request with an authorization token to the DICN switch. 2. The DICN switch sends an authorization request to the Security manager in the DICN controller. 3. The Security manager replies with an authorization success message to the DICN switch. 4. The DICN switch replies with the requested content to the DICN client. Reference H.643.1(19)_F8-6 is shown at the bottom right.](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +``` +sequenceDiagram + participant DICN_client as DICN client + participant DICN_switch as DICN switch + subgraph DICN_controller [DICN controller: ICN instance] + Content_manager + Routing_manager + Storage_manager + Security_manager + end + Note right of DICN_client: H.643.1(19)_F8-6 + DICN_client->>DICN_switch: 1. Send a content request (including authorization token) + DICN_switch->>Security_manager: 2. Send authorization request + Security_manager-->>DICN_switch: 3. Reply with authorization success message + DICN_switch-->>DICN_client: 4. Reply with content requested +``` + +Sequence diagram showing content delivery with local cache. Lifelines: DICN controller: ICN instance (containing Content manager, Routing manager, Storage manager, Security manager), DICN switch, and DICN client. The sequence is: 1. DICN client sends a content request with an authorization token to the DICN switch. 2. The DICN switch sends an authorization request to the Security manager in the DICN controller. 3. The Security manager replies with an authorization success message to the DICN switch. 4. The DICN switch replies with the requested content to the DICN client. Reference H.643.1(19)\_F8-6 is shown at the bottom right. + +**Figure 8-6 – Procedural flows for content delivery with local cache** + +Figure 8-6 shows the procedural flows for content delivery when the content is cached at the DICN switch: + +- 1) The DICN client requests content and sends this request and its own authorization token to the DICN switch it is connected to. +- 2) The DICN switch sends the authorization request to the security manager of the corresponding ICN instance in the DICN controller to verify whether or not the user can access the content. +- 3) The security manager verifies the user's identity and replies with an authorization success message. +- 4) As the switch has cached the content it sends back the content to the user. + +![Sequence diagram showing procedural flows for content delivery without local cache. The diagram involves three main entities: Content provider, DICN controller: ICN instance (containing Content manager, Routing manager, Storage manager, and Security manager), DICN switch, and DICN client. The sequence of interactions is: 1. DICN client sends a content request with an authorization token to the DICN switch. 2. The DICN switch sends an authorization request to the Security manager. 3. The Security manager replies with an authorization success message. 4. The DICN switch sends a content request to the Content manager. 5. The Content manager sends back content provider information to the Routing manager. 6. The Routing manager sends back a routing configuration to the DICN switch. 7. The DICN switch sends a content request to the Content provider. 8. The Content provider replies with the requested content to the DICN switch. 9. The DICN switch forwards the content to the DICN client. 10. The DICN switch performs a self-call to cache the content.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant DICN client + participant DICN switch + participant DICN controller as DICN controller: ICN instance + participant Content provider + Note right of DICN controller: Content manager, Routing manager, Storage manager, Security manager + + DICN client->>DICN switch: 1. Send a content request (including authorization token) + DICN switch->>Security manager: 2. Send authorization request + Security manager-->>DICN switch: 3. Reply with authorization success message + DICN switch->>Content manager: 4. Send content request + Content manager-->>Routing manager: 5. Send back content provider information + Routing manager-->>DICN switch: 6. Send back routing configuration + DICN switch->>Content provider: 7. Send content request + Content provider-->>DICN switch: 8. Reply with content requested + DICN switch->>DICN client: 9. Reply with content requested + DICN switch->>DICN switch: 10. Cache content + +``` + +H.643.1(19)\_F8-7 + +Sequence diagram showing procedural flows for content delivery without local cache. The diagram involves three main entities: Content provider, DICN controller: ICN instance (containing Content manager, Routing manager, Storage manager, and Security manager), DICN switch, and DICN client. The sequence of interactions is: 1. DICN client sends a content request with an authorization token to the DICN switch. 2. The DICN switch sends an authorization request to the Security manager. 3. The Security manager replies with an authorization success message. 4. The DICN switch sends a content request to the Content manager. 5. The Content manager sends back content provider information to the Routing manager. 6. The Routing manager sends back a routing configuration to the DICN switch. 7. The DICN switch sends a content request to the Content provider. 8. The Content provider replies with the requested content to the DICN switch. 9. The DICN switch forwards the content to the DICN client. 10. The DICN switch performs a self-call to cache the content. + +**Figure 8-7 – Procedural flows for content delivery without local cache** + +Figure 8-7 shows the procedural flows for content delivery when the content is not cached at the DICN switch: + +- 1) The DICN client requests some content and sends this request and the authorization token to the DICN switch it is connected to. +- 2) The DICN switch sends the authorization information to the security manager of the corresponding ICN instance in the DICN controller to verify whether or not the user can access the content. +- 3) The security manager verifies the user's identity and replies with an authorization success message. +- 4) As the DICN switch does not cache the content it forwards the request to the content manager of the corresponding ICN instance to look up who can provide this content. +- 5) The content manager sends the information of the selected content provider to the routing manager, which will find a route for content delivery. +- 6) The routing manager configures the route for the content delivery. +- 7) The DICN switch forwards the request to the content provider. +- 8) When the content provider receives the request it replies with the content requested to the DICN switch near the DICN client. +- 9) The DICN switch forwards the content to the DICN client. +- 10) The DICN switch determines whether or not to cache this content based on policies configured by the storage manager. + +#### 8.4.6 Inter-operation + +![Sequence diagram illustrating procedural flows for inter-operation between two ICN instances (ICN instance 1 and ICN instance 2) and a DICN switch. The diagram shows the interaction between a Content provider of ICN1, ICN instance 1: Inter-operation manager, ICN instance 2 (containing Inter-operation manager, Content manager, and Security manager), DICN switch, and DICN client of ICN2. The sequence of messages is: 1. DICN client sends content request to DICN switch; 2. DICN switch sends authorization request to Security manager; 3. Security manager replies with success message; 4. DICN switch sends content request to Content manager; 5. Content manager sends inter-operation request to Inter-operation manager of ICN instance 2; 6. Inter-operation manager of ICN instance 2 sends request to Inter-operation manager of ICN instance 1; 7. Inter-operation manager of ICN instance 1 replies with information; 8. Inter-operation manager of ICN instance 2 sends configuration to DICN switch; 9. DICN switch sends content request to Content provider; 10. Content provider replies with content; 11. DICN switch replies with content to client; 12. DICN switch caches content.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +``` + +sequenceDiagram + participant CP1 as Content provider of ICN1 + participant IM1 as ICN instance 1: Inter-operation manager + box ICN instance 2: + participant IM2 as Inter-operation manager + participant CM2 as Content manager + participant SM2 as Security manager + end + participant DS as DICN switch + participant C2 as DICN client of ICN2 + + C2->>DS: 1. Send a content request (including authorization token) + DS->>SM2: 2. Send authorization request + SM2->>DS: 3. Reply with authorization success message + DS->>CM2: 4. Send content request + CM2->>IM2: 5. Send inter-operation request + IM2->>IM1: 6. Send inter-operation request + IM1->>IM2: 7. Reply with inter-operation information + IM2->>DS: 8. Send inter-operation configuration + DS->>CP1: 9. Send content request + CP1->>DS: 10. Reply with content requested + DS->>C2: 11. Reply with content requested + DS->>DS: 12. Cache content + +``` + +H.643.1(19)\_F8-8 + +Sequence diagram illustrating procedural flows for inter-operation between two ICN instances (ICN instance 1 and ICN instance 2) and a DICN switch. The diagram shows the interaction between a Content provider of ICN1, ICN instance 1: Inter-operation manager, ICN instance 2 (containing Inter-operation manager, Content manager, and Security manager), DICN switch, and DICN client of ICN2. The sequence of messages is: 1. DICN client sends content request to DICN switch; 2. DICN switch sends authorization request to Security manager; 3. Security manager replies with success message; 4. DICN switch sends content request to Content manager; 5. Content manager sends inter-operation request to Inter-operation manager of ICN instance 2; 6. Inter-operation manager of ICN instance 2 sends request to Inter-operation manager of ICN instance 1; 7. Inter-operation manager of ICN instance 1 replies with information; 8. Inter-operation manager of ICN instance 2 sends configuration to DICN switch; 9. DICN switch sends content request to Content provider; 10. Content provider replies with content; 11. DICN switch replies with content to client; 12. DICN switch caches content. + +**Figure 8-8 – Procedural flows for inter-operation** + +Figure 8-8 illustrates the procedural flows for inter-operation: + +- 1) A DICN client of ICN instance 2 requests content held by a provider which adopts another ICN protocol, i.e., the ICN instance 1. It sends the content request and authorization token to the DICN switch. +- 2) The DICN switch sends the authorization request to the security manager of ICN instance 2. +- 3) The security manager verifies the users' identities and replies with authorization success message; +- 4) The DICN switch receives the authorization success message and sends the content request to the content manager of the corresponding ICN instance 2 in the DICN controller. +- 5) The content manager of ICN instance 2 finds that no content provider registers this content. It sends this request to the inter-operation manager of the ICN instance 2 in DICN controller. +- 6) The inter-operation manager of ICN instance 2 forwards the request to the inter-operation manager of ICN instance 1. +- 7) The inter-operation manager of ICN instance 1 replies with the inter-operation information, including the inter-operation policy (tunnelling or translation) and the name-mapping of the requested content. +- 8) Based on the returned policies, the inter-operation manager configures the inter-operation API in the DICN switch to perform the inter-operation. +- 9) The DICN switch requests the content from the content provider. + +- 10) The content provider of ICN instance 1 replies with the content requested to the DICN switch. +- 11) The DICN switch sends back the content to the DICN client. +- 12) The DICN switch caches the content based on the caching policies. + +## Bibliography + +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.* +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks.* +- [b-ITU-T Y.2201] Recommendation ITU-T Y.2201 (2009), *Requirements and capabilities for ITU-T NGN.* +- [b-ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1.* +- [b-ITU-T Y.3033] Recommendation ITU-T Y.3033 (2014), *Framework of data aware networking for future networks.* +- [b-Dannewitz] Dannewitz, C. (2009), *NetInf: An Information-Centric Design for the Future Internet*, In Proc. 3rd GI/ITG KuVS Workshop on The Future Internet, May. +- [b-Detti] Detti A, Blefari Melazzi N, Salsano S, et al. (2011), *CONET: a content centric inter-networking architecture*. In Proc. ACM SIGCOMM workshop on Information-Centric Networking, August. +- [b-Jacobson] Jacobson, V., et al. (2009), *Networking Named Content*, In Proc. ACM CoNEXT, December. +- [b-Sarela] Sarela, M., et al. (2008), *RTFM: Publish/Subscribe Internetworking Architecture*, ICT-Mobile Summit, June. +- [b-Seskar] Seskar I, Nagaraja K, Nelson S, et al. (2011), *MobilityFirst future internet architecture project*. In Proc. 7th Asian Internet Engineering Conference, December. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.644.3-202008-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5c9168fad87172b06a11be664838db357caaee4f --- /dev/null +++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/raw.md @@ -0,0 +1,911 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.644.3** + +(08/2020) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +Broadband, triple-play and advanced multimedia services – Ubiquitous sensor network applications and Internet of Things + +# --- **Functional architecture of multimedia content delivery networks** + +Recommendation ITU-T H.644.3 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.644.3 + +# Functional architecture of multimedia content delivery networks + +## Summary + +Recommendation ITU-T H.644.3 specifies the common functional architecture for multimedia content delivery networks. The functions and functional blocks within this common functional architecture and the related reference points are specified in this Recommendation for matching the requirements of various kinds of content ingestion, content distribution and content delivery within different networks and platforms. In addition, this Recommendation also provides some examples of the related service features, workflows, an implementation guide, and the security aspects in appendices. + +This Recommendation is intended to provide the references for multimedia content delivery network (MCDN) providers to help them to build the common infrastructures of a multimedia content delivery network. This Recommendation is of benefit for multimedia content providers who wish to dispatch their content to different types of end-users by taking advantage of a common MCDN capability. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.644.3 | 2020-08-13 | 16 | 11.1002/1000/14340 | + +## Keywords + +Architecture, multimedia content delivery network, reference point. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Introduction ..... | 4 | +| 6.1 An overview of the MCDN functional architecture ..... | 5 | +| 6.2 Functional groups of the external system..... | 6 | +| 7 The high-levelled MCDN functional architecture ..... | 6 | +| 7.1 Content distribution and delivery functions ..... | 7 | +| 7.2 Management functions ..... | 9 | +| 7.3 Content routing/redirecting functions..... | 9 | +| 8 Reference points ..... | 10 | +| 8.1 External reference points ..... | 10 | +| 8.2 Internal reference points ..... | 11 | +| Appendix I – Examples of media transmission and service procedures..... | 13 | +| I.1 Content access ..... | 13 | +| I.2 Content distribution ..... | 16 | +| I.3 Content delivery ..... | 17 | +| Appendix II – Implementation mechanisms related to the functions ..... | 18 | +| II.1 Content access mechanism ..... | 18 | +| II.2 Content distribution mechanism..... | 19 | +| II.3 Content routing mechanism..... | 19 | +| II.4 Multimedia content location and streaming service mechanism..... | 21 | +| Appendix III – Authentication mechanisms ..... | 22 | +| III.1 Authentication mechanism in the edge node..... | 22 | +| III.2 Double authentication mechanism in centre and edge node ..... | 22 | +| Bibliography..... | 24 | + + + +# Recommendation ITU-T H.644.3 + +# Functional architecture of multimedia content delivery networks + +# 1 Scope + +This Recommendation specifies the common functional architecture for multimedia content delivery networks (MCDNs). The functions and functional blocks within that functional architecture and the related reference points are specified in this Recommendation for matching the requirements of various kinds of content ingestion, content distribution and content delivery within different networks and platforms. In addition, this Recommendation also provides some examples of the related service features, workflows, an implementation guide and the security aspects in the Appendices. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T Y.2019] Recommendation ITU-T Y.2019 (2010), *Content delivery functional architecture in NGN*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 content** [b-ITU-T H.780]: A combination of audio, still image, graphic, video, or data. + +**3.1.2 content delivery network (CDN)** [b-ITU-T Y.2084]: A content delivery network (CDN) is a system of distributed servers that deliver content (e.g., web pages, files, videos and audios) to users based on pre-defined criteria such as the geographic locations of users, the status of the content delivery server and the IP network connection. + +**3.1.3 content delivery** [b-ITU-T Y.2080]: In the context of the distributed service networking (DSN) functional architecture, the operation of sending and receiving content between the requested peer and the requesting peer or client. + +NOTE – A client is a service consumer external to DSN. A peer is a node within DSN. + +**3.1.4 content distribution** [b-ITU-T Y.2080]: In the context of the distributed service networking (DSN) functional architecture, the whole process of content sending from one or more content sources, and sharing among DSN nodes. + +NOTE – During the content distribution process, content is often sent to appropriate intermediate nodes to enable subsequent delivery. + +**3.1.5 data encryption** [b-ITU-T J.191]: Data encryption prevents the unauthorized disclosure/access of data. Data encryption does an excellent job at providing data confidentiality and protection against theft of service. Encryption prevents making data unable to read without the correct decryption key; however, it does not validate the source/receiving entities and it does not + +provide copy protection after the data have been decrypted. It also does not prevent denial of service (DoS) attacks. + +**3.1.6 delivery** [b-ITU-T X.609]: The procedures and means employed to provide a user with the required archived material for reuse. + +**3.1.7 distributed service networking (DSN)** [b-ITU-T Y.2206]: An overlay networking which provides distributed and manageable capabilities to support various multimedia services and applications. + +**3.1.8 metadata** [b-ITU-T X.1255]: Structured information that pertains to the identity of users, systems, services, processes, resources, information or other entities. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 content distribution service:** The service provided by content/service providers (CP/SPs) or content delivery network (CDN) vendors/providers with the capability of distributing and delivering the content from content source to the destination by using CDN facilities. + +**3.2.2 distribution:** The unidirectional flow of information from a given point in the network to other (multiple) locations. + +**3.2.3 dynamic content:** Content created on demand when a user uses a web application dynamically. + +**3.2.4 static content:** Content that seldom changes and that does not change with the requests from the users. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|---------------------------------------------------| +| AES | Advanced Encryption Standard | +| AF | Aggregation Functions | +| A/S-MBF | Application/Service Business Management Functions | +| CBR | Constant Bitrate | +| CD&DF | Content Distribution and Delivery Functions | +| CL&DF | Content Location and Distribution Functions | +| CDF | Content Delivery Functions | +| CDN | Content Delivery Network | +| CMS | Content Management System | +| CNAME | Canonical NAME | +| CPF | Content Provider Functions | +| CRF | Content Routing/Redirecting Functions | +| DNS | Domain Name System | +| DoS | Denial of Service | +| EPG | Electronic Programme Guide | +| EUF | End-user Functions | +| FTP | File Transfer Protocol | + +| | | +|------|-------------------------------------| +| GSLB | Global Service Load Balance | +| HLS | HTTP Live Streaming | +| HPD | HTTP Progress Download | +| HTTP | Hypertext Transfer Protocol | +| IPTV | Internet Protocol Television | +| MCDN | Multimedia Content Delivery Network | +| NF | Network Functions | +| NFV | Network Functions Virtualization | +| NFVO | NFV Orchestrator | +| NGN | Next Generation Network | +| OTT | Over The Top | +| QoS | Quality of Service | +| RR | Request Routing | +| RTSP | Real-Time Streaming Protocol | +| SDN | Software Defined Network | +| SLB | Service Load Balance | +| SOAP | Simple Object Access Protocol | +| STB | Set Top Box | +| URL | Uniform Resource Locator | +| VBR | Variable Bitrate | +| VOD | Video On Demand | +| VR | Virtual Reality | +| XML | Extensible Markup language | + +# 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. +- The keywords "is prohibited from" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "is not recommended" indicate a requirement which is not recommended but which is not specifically prohibited. Thus, conformance with this specification can still be claimed even if this requirement is present. +- The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +**Functions:** In the context of MCDN architecture, "functions" are defined as a collection of functionalities. It is represented by the following symbol: + +![A rounded rectangular box containing the word 'Functions'.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +A rounded rectangular box containing the word 'Functions'. + +**Functional block:** In the context of MCDN architecture, a "functional block" is defined as a group of functionalities that has not been further subdivided at the level of detail described in this Recommendation. It is represented by the following symbol: + +![A rectangular box containing the words 'Functional block'.](e6df2733626a85205c1db682e6259c46_img.jpg) + +A rectangular box containing the words 'Functional block'. + +NOTE – In the future, other groups or other Recommendations may possibly further subdivide these functional blocks. + +# 6 Introduction + +The current [ITU-T Y.2019] has defined the functional architecture of content delivery functions in next generation network (NGN). It is a general functional architecture but was built based on the Internet protocol television (IPTV) service. Currently, many additional services such as over the top (OTT) may also apply this functional architecture, but some functional blocks may need to be enhanced to support the various types of service. In order to support those services, some reference points and protocols may also need to be updated accordingly. Moreover, to provide an end-to-end content delivery service, a management and content routing system are also need to be included. Therefore, the current context in [ITU-T Y.2019] may not be sufficient to satisfy those new requirements. + +A multimedia content delivery network (MCDN) as defined in this Recommendation is an integrated networking structure which is able to provide a common multimedia content distribution service to the various end-users by ignoring the difference of content type (e.g., static content, dynamic content), network and service platform, etc. Basically, the functional architecture for MCDN consists of the conventional content delivery network (CDN) functions in common, i.e., the basic functions that all types of CDN service are required to implement, e.g., content ingestion, storage and distribution, etc. However, there are many service feature differences between different types of CDN. For example, for the video service provided by streaming media CDN, a variety of streaming protocols (e.g., RTSP, HLS and Dash) should be supported but it is not required for web CDN which merely supports download protocols (e.g., HTTP and FTP). These differences can be eliminated by adopting the enhanced capability provided by MCDN functions. + +Figure 6-1 provides an overview of the MCDN functional architecture. + +![Figure 6-1: An overview of the MCDN functional architecture. The diagram shows a layered structure. At the top are two grey boxes: 'Application/service business management functions' and 'Content provider functions'. Below them is a dashed box labeled 'MCDN' containing three colored boxes: 'Management functions' (purple), 'Content distribution and delivery functions' (green), and 'Content routing/redirection functions' (blue). Below the MCDN box is a grey box for 'Network functions', and at the bottom is a grey box for 'End-user functions'. Dotted lines with reference points connect these elements across layers.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Figure 6-1: An overview of the MCDN functional architecture. The diagram shows a layered structure. At the top are two grey boxes: 'Application/service business management functions' and 'Content provider functions'. Below them is a dashed box labeled 'MCDN' containing three colored boxes: 'Management functions' (purple), 'Content distribution and delivery functions' (green), and 'Content routing/redirection functions' (blue). Below the MCDN box is a grey box for 'Network functions', and at the bottom is a grey box for 'End-user functions'. Dotted lines with reference points connect these elements across layers. + +**Figure 6-1 – An overview of the MCDN functional architecture** + +NOTE – The functions and reference points represented by the blocks and dotted lines in grey are only introduced as the associated background information in this Recommendation. + +## 6.1 An overview of the MCDN functional architecture + +This clause provides descriptions of each of the functional components in MCDN functional architecture. The related functions and the functional blocks in each function are further broken down in clause 7. + +### 6.1.1 Content distribution and delivery functions + +The content distribution and delivery functions (CD&DF) provide the core functionality of content ingestion, processing and storage. This also provides the content service for the end-user by distributing the content to the MCDN edge node. + +Considering the actual implementation of CD&DF, a nodes deployment with 2-layer-networking or 3-layer-networking are typically used and different types of MCDN node are deployed in each layer. These node types are described as follows: + +#### Centre node + +The centre node receives content from the content provider, stores and pre-processes and distributes it to the downstream nodes using the network functions, under the control of the application/service system management functions. + +#### Relay/middle node + +The relay/middle node acts as the buffer function between centre node and edge node, which is able to provide content service when the content is not in edge nodes. + +NOTE – In some special circumstances, e.g., when the MCDN service coverage is restricted, the relay/middle node may not be applied. + +#### Edge node + +The major function of edge node is to deliver the related content to end-users based on users' requests, the adapted transport protocols, and the server nodes' status. Edge nodes can be designed for different architectures according to the service that a service provider wants to provide. + +### **6.1.2 Content routing/redirecting functions** + +The content routing/redirecting functions (CRF) are responsible for selecting the requested content resource for users. The content resource may be the URL of content or the media server address. + +NOTE – By considering the real implementation of this function with various network situations, e.g., fixed or mobile networks, there may be many approaches for accessing the content routing/redirecting server, e.g., by using DNS recursion/application level redirecting. These approaches are out of scope in this Recommendation but will be specified in the other MCDN related Recommendations. + +### **6.1.3 Management functions** + +The management functions (MF) perform overall system management (e.g., content management, node management, access/ingestion management, network management, distribution policy management, and routing/redirection policy management). The major role of this function is to manage the content, policy and node server to guarantee the CDN running in a highly efficient and secure environment. + +## **6.2 Functional groups of the external system** + +### **6.2.1 Content provider functions** + +The content provider functions (CPF) are provided by the entity that owns or is licensed to provide (e.g., sell, rent or give free usage permission) content or content assets (e.g., owner of the source content, metadata and usage rights). The function of content provider is used to edit, review, release and broadcast control (including advertisement insertion, content switching, content monitoring, etc.) of content injected by content provider. Content provider functions are also responsible for maintaining the customer authorized domain name system (DNS) functions. + +### **6.2.2 Application/service business management functions** + +The application/service business management functions (A/S-MBF) are responsible for business configuration, including user's life cycle management (account opening, account cancellation, account authentication and account change), business ordering information management and billing, and arrangement of the browsing interface for users. + +### **6.2.3 Network functions** + +The network Functions (NF) provide the network resources for data transmission and processing for those functions that are the infrastructure functions and contribute to the provision of the quality of service (QoS) required by the multimedia services. + +### **6.2.4 End-user functions** + +The end-user functions (EUF) perform mediation between the end user and the media service node. + +# **7 The high-levelled MCDN functional architecture** + +This clause describes the functions and functional blocks by considering the multimedia services usage including the content/service provider access, the content ingestion and the content distribution and delivery. Functions and functional blocks described in this clause are common to functional components as detailed in clause 6.1. + +Figure 7-1 provides the high-levelled MCDN functional architecture with detailed information. + +![Figure 7-1: The high-levelled MCDN functional architecture diagram. The diagram shows a layered architecture. At the top are two grey boxes: 'Application/service business management functions' and 'Content provider functions'. Below them is a large dashed blue box labeled 'MCDN'. Inside the MCDN box, on the left, is a purple box 'Management functions' containing 'Content management', 'Node management', 'Network management', and 'Service configuration management'. In the center is a green box 'Content distribution and delivery functions' containing three sub-sections: 'Content location and distribution functions' (with 'Content pre-processing', 'Content ingestion', 'Storage', 'Service load balance', and 'Content distribution'), 'Aggregation functions' (with 'Cache', 'Service load balance', and 'Content distribution'), and 'Content delivery functions' (with 'Content service control', 'Content processing', 'Cache', 'Service load balance', and 'Content service'). On the right is a blue box 'Content routing/redirecting functions' containing 'Global service load balance (GSLB)' and 'Request routing (RR)'. Below the MCDN box is a grey box 'Network functions' and a 'Local DNS' box. At the bottom is a grey box 'End-user functions'. A grey line connects the 'Content provider functions' box to the 'Local DNS' box. A small text 'H.644.3(20)_F7-1' is at the bottom right.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 7-1: The high-levelled MCDN functional architecture diagram. The diagram shows a layered architecture. At the top are two grey boxes: 'Application/service business management functions' and 'Content provider functions'. Below them is a large dashed blue box labeled 'MCDN'. Inside the MCDN box, on the left, is a purple box 'Management functions' containing 'Content management', 'Node management', 'Network management', and 'Service configuration management'. In the center is a green box 'Content distribution and delivery functions' containing three sub-sections: 'Content location and distribution functions' (with 'Content pre-processing', 'Content ingestion', 'Storage', 'Service load balance', and 'Content distribution'), 'Aggregation functions' (with 'Cache', 'Service load balance', and 'Content distribution'), and 'Content delivery functions' (with 'Content service control', 'Content processing', 'Cache', 'Service load balance', and 'Content service'). On the right is a blue box 'Content routing/redirecting functions' containing 'Global service load balance (GSLB)' and 'Request routing (RR)'. Below the MCDN box is a grey box 'Network functions' and a 'Local DNS' box. At the bottom is a grey box 'End-user functions'. A grey line connects the 'Content provider functions' box to the 'Local DNS' box. A small text 'H.644.3(20)\_F7-1' is at the bottom right. + +**Figure 7-1 – The high-levelled MCDN functional architecture** + +NOTE – The definition of functions and the line in grey are outside of the scope of this Recommendation. + +## 7.1 Content distribution and delivery functions + +### 7.1.1 Content location and distribution functions (centre node) + +Content location and distribution functions (CL&DF), acting as a centre node, is mainly responsible for docking with the application/service management system functions to achieve content ingestion, management, storage and active distribution to various media service nodes in MCDN, which includes the function blocks presented in clauses 7.1.1.1 to 7.1.1.5. + +#### 7.1.1.1 Content ingestion + +According to the content ingestion instruction of the content management system (CMS) which may be provided by the content provider, the content ingestion functional block acquires the specified content, ingested into the content storage and registered in the content management functional block. Alternatively, instead of ingesting content through the CMS, the content and metadata sources are accessed by the way of back-to-source. + +#### 7.1.1.2 Content pre-processing + +The content pre-processing functional block allows the ingested content processing, such as content slicing, transcoding, and encapsulation, etc. + +#### 7.1.1.3 Service load balance + +The service load balance (SLB) functional block receives the content location and/or content request from the downstream nodes, and selects the most appropriate media server to provide services based on the load balance strategy inside the centre node. + +#### **7.1.1.4 Content storage** + +The content storage functional block provides the storage resources for online media content according to the strategy in the content management functional block, and updates media content according to the caching strategy. + +#### **7.1.1.5 Content distribution** + +The content distribution functional block is used for content distribution and transmission based on the scheduling strategy in the content management functional block. + +### **7.1.2 Content delivery functions (edge node)** + +Content delivery functions (CDF), acting as an edge node in MCDN service, is responsible for receiving end-user requests, authenticating and then serving cached content to users. If there is a cache miss, the edge node will pull content from the upstream node and cache it, or redirect the request to the upstream node, to serve the content. Edge node includes the functional blocks presented in clauses 7.1.2.1 to 7.1.2.5: + +#### **7.1.2.1 Content service control** + +The content service control functional block locates the node that can serve desired contents, based on the content ID. + +#### **7.1.2.2 Content processing** + +The content processing functional block allows the ingested content to be processed, such as slicing, transcoding, and encapsulation, etc. + +#### **7.1.2.3 Content service** + +The content service functional block supports a variety of multimedia services, such as e-business, web portal service, video on demand, live-streaming, and downloading files including game installation packages, audios/videos, and firmware. + +#### **7.1.2.4 Service load balance** + +The service load balance (SLB) functional block receives the content location and/or content request from the end-user via content routing/redirecting functions, and selects the most appropriate media server to provide services based on the load balance strategy inside each edge node. + +#### **7.1.2.5 Cache** + +The cache functional block provides the capability of temporary storage of the content locally in the Edge node. The content may be added, removed and replaced automatically according to a pre-defined cache policy. Normally, the most popular/hottest content will be cached in the Edge node. + +### **7.1.3 Aggregation functions (relay/middle node)** + +Aggregation functions (AF), acting as a relay/middle node, is an optional function within the functional architecture in this Recommendation. However it is recommended to be implemented as a functional entity in the real MCDN deployment. It is very useful for delivering multimedia service especially within a wide geographical area that covered by the MCDN service. + +The aggregation functions stores and updates multimedia content based on caching strategy. + +#### **7.1.3.1 Service load balance** + +The service load balance (SLB) functional block receives the content location and/or content request from the downstream nodes, and selects the most appropriate media server to provide services based on the load balance strategy inside the relay/middle node. + +#### **7.1.3.2 Cache** + +The cache functional block provides the capability of temporary storage of the content locally in the relay/middle node. The content may be added, removed and replaced automatically according to a pre-defined cache policy. + +#### **7.1.3.3 Content distribution** + +The content distribution functional block is used for content distribution and transmission based on the routing strategy in the content management block. + +## **7.2 Management functions** + +### **7.2.1 Content management** + +The content management functional block registers and manages the attributes of contents in the MCDN, including the content ID, media metadata information, life cycle, content status, and content update policy. + +### **7.2.2 Node management** + +The node management functional block manages all nodes in the MCDN, including node information maintenance, device adding and deleting within the node, the content and service policy maintenance within the node. + +### **7.2.3 Network management** + +The network management functional block manages MCDN network performance, alarms, and topology information. + +NOTE – By considering the applying of the evolved network technology, such as NFV, SDN, the network management functional block can also optionally manage the underlay network, including network performance, alarms and topology information, by co-operating with the other network functions, such as SDN controller, NFVO, etc. + +### **7.2.4 Service configuration management** + +The service configuration management functional block provides the unified management of MCDN service configuration, for example, the management of content injection, content service, the policy of content distribution, routing and dispatching. + +## **7.3 Content routing/redirecting functions** + +The content routing/redirecting functions are further composed of the following two functional blocks. + +### **7.3.1 Global service load balance** + +The global service load balance (GSLB) functional block provides the unified entrance of MCDN service for the user requests and dispatches those requests among MCDN service nodes in the different areas. + +### **7.3.2 Request routing** + +The request routing (RR) functional block provides the entrance of MCDN service within a specific area for the user requests and dispatches those requests among the MCDN service nodes within the same area. + +# 8 Reference points + +This clause describes the general definitions of reference points and the related protocols that are applied on the reference points. The MCDN reference points, based on the system they are interacting with, are classified into external reference points and internal reference points. + +Figure 8-1 shows the reference points among the functions and functional blocks within MCDN functional architecture. + +![Figure 8-1: Reference points within MCDN functional architecture. The diagram shows the interaction between various functional blocks. At the top are 'Application/service business management functions' and 'Content provider functions'. Below them is a large dashed box labeled 'MCDN' containing 'Management functions' (Content, Node, Network, Service configuration management), 'Content distribution and delivery functions' (subdivided into Content location and distribution, Aggregation, and Content delivery), and 'Content routing/redirection functions' (Global server load balance (GSLB) and Request routing (RR)). External reference points are: A (between App/S-BMF and MF), B1 (between CP and Content location and distribution), B2 (between App/S-BMF and Content location and distribution), and c (between Network functions and End-user functions). Internal reference points are: a (between Content management and Content location and distribution), b (between Content location and distribution and Aggregation, and between Aggregation and Content delivery), c (between Node management and Network management), d (between Content routing/redirection and Aggregation), e (between Content location and distribution and Content delivery), and f (between Content location and distribution and Content delivery).](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 8-1: Reference points within MCDN functional architecture. The diagram shows the interaction between various functional blocks. At the top are 'Application/service business management functions' and 'Content provider functions'. Below them is a large dashed box labeled 'MCDN' containing 'Management functions' (Content, Node, Network, Service configuration management), 'Content distribution and delivery functions' (subdivided into Content location and distribution, Aggregation, and Content delivery), and 'Content routing/redirection functions' (Global server load balance (GSLB) and Request routing (RR)). External reference points are: A (between App/S-BMF and MF), B1 (between CP and Content location and distribution), B2 (between App/S-BMF and Content location and distribution), and c (between Network functions and End-user functions). Internal reference points are: a (between Content management and Content location and distribution), b (between Content location and distribution and Aggregation, and between Aggregation and Content delivery), c (between Node management and Network management), d (between Content routing/redirection and Aggregation), e (between Content location and distribution and Content delivery), and f (between Content location and distribution and Content delivery). + +Figure 8-1 – Reference points within MCDN functional architecture + +## 8.1 External reference points + +According to the system and network architecture, MCDN external reference points are defined as indicated in Table 8-1. + +NOTE – There may be other reference points that need to be defined, such as the reference point between the content routing/redirection system and content provider or end-user. Those reference points are outside the scope of this Recommendation. + +Table 8-1 – External reference points + +| Reference point | Definition | Protocol | Notes | +|-----------------|----------------------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| A | Reference point between A/S-BMF and MF | HTTP, FTP | This reference point A for MCDN management system is to receive the management and configuration instruction from the external management platform. | + +**Table 8-1 – External reference points** + +| Reference point | Definition | Protocol | Notes | +|-----------------|------------------------------------------------------------------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| B1 | Reference point between CPF and CD & DF (mostly implemented by centre node) | SOAP+XML | The content provider informs the centre node of MCDN to obtain the information of external content source and metadata into MCDN via the reference point B1. After receiving the ingestion message instruction from the reference point B1, the centre node of MCDN is able to obtain the content and keep it locally through the reference point B2. | +| B2 | Reference point between CPF and CD & DF (mostly implemented by centre node). | HTTP, FTP | When the content requested from the end-user is not cached in any MCDN node, the MCDN centre node will obtain the requested content from the external content source through the reference point B2. | +| C | Reference point between EUF and CDF (edge node). | RTSP, HTTP | This reference point C is used for the MCDN edge node to deliver the content service information and media stream to the end-user. This referent point is also used for redirecting the content request while the content is not cached in the edge node. RTSP protocol is used for RTSP content transmission; HTTP protocol is used for HTTP live streaming (HLS), picture and download content transmission. | + +## 8.2 Internal reference points + +According to the system and network architecture, MCDN internal reference points are defined as indicated in Table 8-2. + +**Table 8-2 – Internal reference points** + +| Reference point | Definition | Protocol | Notes | +|-----------------|-----------------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| a | Reference point between content management functional block in MF and CL&DF | HTTP | The reference point is responsible for the management of content transcoding, slicing, storage injection and deletion. | +| b | Reference point between CL&DF and CDF/AF (if AF is deployed) | SOAP+XML | The upstream MCDN node informs the downstream MCDN node(s) to obtain the content distribution/ ingest information through the reference point b. After receiving the | + +**Table 8-2 – Internal reference points** + +| Reference point | Definition | Protocol | Notes | +|-----------------|--------------------------------------------------------------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | distribution/ingest message instruction, the centre node(s) of MCDN is able to obtain the content and keep it locally through the reference point f. | +| c | Reference point between CD&DF and node management functional block in MF | HTTP | The reference point includes functions for managing all the MCDN nodes by performing adding, deleting, upgrading operations. | +| d | Reference point between CRF and CD&DF | HTTP | The reference point is for MCDN routing/redirecting functions to select the most appropriate MCDN node for the end-user, based on the user's content request. | +| f | Reference point between CL&DF and CDF/AF (if AF is deployed) | HTTP, RTSP, FTP |

    The reference point is used for the downstream node to locate and retrieve content from the upstream node.

    It may have two content retrieving modes:

    Passively: The downstream node only retrieves the content from the upstream node when the content requested from the end-user is not cached in any the downstream node.

    Actively: When the upstream node count of the requests of downstream node(s) exceeds a certain statistic threshold, it actively sends the content distribution request to the downstream node through the reference point b and the downstream node retrieves the content from the upstream node through the reference point f.

    | +| e (optional) | Reference point between CRF and MF | HTTP | The reference point e is an optional interface which is used for content routing/redirecting functions to obtain management information from MCDN management function, e.g., the routing/redirecting policy, network management information, etc. | + +# Appendix I + +## Examples of media transmission and service procedures + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Content access + +#### I.1.1 Content ingestion + +The process of content access by content ingestion is as indicated in Figure I.1. + +![Sequence diagram illustrating the service procedure of content ingestion between a Content provider and a Centre node.](a734898ce18e972938949637c32a34f4_img.jpg) + +``` +sequenceDiagram + participant Content origin + participant CMS + participant Centre node + Note right of Centre node: 1) CP/SP, content access and service configuration + CMS->>Centre node: 2) Send injection request message through B1 + Centre node-->>CMS: 3) Respond to CMS request + Note right of Centre node: 4) Parse and execute operations requested in XML file + CMS->>Content origin: 5) Obtain entity files stored in centre node + Centre node-->>CMS: 6) Return content injection results +``` + +The diagram is a sequence diagram with three lifelines: Content origin, CMS, and Centre node. The Content origin and CMS are grouped under a 'Content provider' box. The sequence of interactions is as follows: 1) A self-call on the Centre node labeled '1) CP/SP, content access and service configuration'. 2) An arrow from CMS to Centre node labeled '2) Send injection request message through B1'. 3) A return arrow from Centre node to CMS labeled '3) Respond to CMS request'. 4) A self-call on the Centre node labeled '4) Parse and execute operations requested in XML file'. 5) An arrow from CMS to Content origin labeled '5) Obtain entity files stored in centre node'. 6) A return arrow from Centre node to CMS labeled '6) Return content injection results'. The diagram is labeled 'H.644.3(20)\_FI.1' at the bottom right. + +Sequence diagram illustrating the service procedure of content ingestion between a Content provider and a Centre node. + +**Figure I.1 – The service procedure of content ingestion** + +In the content ingestion method, the CMS will actively send ingestion request messages to the centre node of MCDN. Then the centre node parses and executes the XML file sent by CMS. Finally, the centre node obtains and stores contents from the content origin. Therefore, MCDN can directly serve contents to end-users upon requests, elevating the end-user experience of the service. Content injected by content ingestion method will be stored in MCDN permanently until being removed by instruction. + +#### I.1.2 Content pre-ingestion + +The process of content access by content pre-ingestion is as indicated in Figure I.2. + +![Sequence diagram illustrating the service procedure of content pre-ingestion between a Content provider and a Centre node.](5445597cceefaca1ac89e710fe339325_img.jpg) + +``` +sequenceDiagram + participant CP as Content provider + subgraph CP [Content provider] + CO[Content origin] + CMS[CMS] + end + participant CN as Centre node + Note right of CN: 1) CP/SP, content access and service configuration + CMS->>CN: 2) Send injection request message through B1 + Note right of CN: 3) Respond to CMS request + CN-->>CMS: 3) Respond to CMS request + Note right of CN: 4) Parse and execute operations requested in XML file + CN-->>CO: 5) Obtain entity files stored in centre node + CN-->>CMS: 6) Return content injection results + Note right of CN: 7) Delete cache based on content popularity file +``` + +The diagram is a sequence diagram showing the interaction between a Content provider and a Centre node. The Content provider is divided into two sub-components: Content origin and CMS. The sequence of messages is as follows: 1) CP/SP, content access and service configuration (internal to Centre node); 2) Send injection request message through B1 (from CMS to Centre node); 3) Respond to CMS request (from Centre node to CMS); 4) Parse and execute operations requested in XML file (internal to Centre node); 5) Obtain entity files stored in centre node (from Centre node to Content origin); 6) Return content injection results (from Centre node to CMS); 7) Delete cache based on content popularity file (internal to Centre node). The diagram is labeled H.644.3(20)\_FI.2 at the bottom right. + +Sequence diagram illustrating the service procedure of content pre-ingestion between a Content provider and a Centre node. + +**Figure I.2 – The service procedure of content pre-ingestion** + +In the content pre-ingestion method, the CMS will actively send ingestion request messages to the centre node of MCDN which parses and executes the XML files sent by CMS to obtain and store contents from the content origin as in the content ingestion method. However, content obtained through pre-ingestion will be deleted based on popularity instead of being permanently stored in MCDN. Pre-ingestion content can have a protection duration to prevent it from being deleted. + +#### I.1.3 Back-to-source + +The process of back to source is as indicated in Figure I.3. + +![Sequence diagram illustrating the service procedure of back-to-source. The diagram shows four steps: 1) Service and content back to source configuration (CDN to Content origin), 2) Request media service (Terminal to CDN), 3) Upstream CDN obtains entity files back to the source through B2 and delivers media service to the downstream CDN at the same time (CDN to Content origin), and 4) Service node provides media service for terminal (CDN to Terminal).](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +``` +sequenceDiagram + participant Content provider + subgraph Content provider + Content origin + CMS + end + participant CDN + participant Terminal + + Note right of CDN: 1) Service and content back to source configuration + Content origin-->CDN: + Terminal->>CDN: 2) Request media service + CDN-->>Content origin: 3) Upstream CDN obtains entity files back to the source through B2 and delivers media service to the downstream CDN at the same time + Content origin-->CDN: + CDN-->>Terminal: 4) Service node provides media service for terminal +``` + +H.644.3(20)\_FI.3 + +Sequence diagram illustrating the service procedure of back-to-source. The diagram shows four steps: 1) Service and content back to source configuration (CDN to Content origin), 2) Request media service (Terminal to CDN), 3) Upstream CDN obtains entity files back to the source through B2 and delivers media service to the downstream CDN at the same time (CDN to Content origin), and 4) Service node provides media service for terminal (CDN to Terminal). + +**Figure I.3 – The service procedure of back-to-source** + +The back-to-source method does not require injecting content into MCDN in advance. Instead, it needs to be configured to access the configuration tables of content providers. Upon receiving a request from an end-user, the centre node of MCDN obtains content from the content origin immediately and distributes media files to the downstream node at the same time to provide media service for end-users. + +### I.2 Content distribution + +The process of content distribution is as indicated in Figure I.4. + +![Sequence diagram of content distribution between a Centre node and a Middle node/edge node.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +``` +sequenceDiagram + participant Centre node + participant Middle node/edge node + Note right of Middle node/edge node: 1) CP/SP, content routing and service configuration + Centre node->>Middle node/edge node: 2) Content distribution request through b when the hotdegree threshold is reached + Note right of Middle node/edge node: 3) Respond to upstream node's request + Note right of Middle node/edge node: 4) Parse and execute operations requested in XML file + Centre node->>Middle node/edge node: 5) Obtain entity files stored in downstream node through f + Centre node->>Middle node/edge node: 6) Return content distribution results +``` + +The diagram illustrates the service procedure of content distribution between a Centre node and a Middle node/edge node. The process consists of six steps: 1) CP/SP, content routing and service configuration (internal to the Middle node/edge node); 2) Content distribution request through b when the hotdegree threshold is reached (Centre node to Middle node/edge node); 3) Respond to upstream node's request (internal to the Middle node/edge node); 4) Parse and execute operations requested in XML file (internal to the Middle node/edge node); 5) Obtain entity files stored in downstream node through f (Centre node to Middle node/edge node); 6) Return content distribution results (Centre node to Middle node/edge node). The diagram is labeled H.644.3(20)\_FI.4. + +Sequence diagram of content distribution between a Centre node and a Middle node/edge node. + +**Figure I.4 – The service procedure of content distribution** + +When the hot degree threshold is reached, the centre node will actively send a distribution request message to the downstream node of MCDN. Then the downstream node parses and executes the XML file sent by the centre node. Finally, the downstream node obtains and stores contents from the centre node. + +### I.3 Content delivery + +The process of content delivery is illustrated in Figure I.5. + +![Sequence diagram of content delivery process](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant GSLB + participant RR + participant CDN + Terminal->>GSLB: 1) Send DNS request + GSLB-->>Terminal: 2) Return IP of SLB + Terminal->>RR: 3) Send media service request + Note right of RR: 4) Check authentication + RR-->>Terminal: 5) Return a redirected URL with authentication token + Terminal->>CDN: 6) Access CDN with authentication token + CDN-->>Terminal: 7) Provide media service + +``` + +The diagram illustrates the service procedure of content delivery through a sequence of interactions between four entities: Terminal, GSLB, RR, and CDN. The process begins with the Terminal sending a DNS request to the GSLB. The GSLB responds with the IP address of the SLB. Next, the Terminal sends a media service request to the RR. The RR performs an internal check for authentication and then returns a redirected URL with an authentication token to the Terminal. The Terminal then accesses the CDN using this token, and the CDN provides the media service. The sequence of steps is as follows: + +- 1) Send DNS request +- 2) Return IP of SLB +- 3) Send media service request +- 4) Check authentication +- 5) Return a redirected URL with authentication token +- 6) Access CDN with authentication token +- 7) Provide media service + +H.644.3(20)\_FI.5 + +Sequence diagram of content delivery process + +**Figure I.5 – The service procedure of content delivery** + +When the terminal requests media service, it requests a domain name resolution from GSLB, and GSLB returns the IP address of RR to the terminal. Then, the terminal sends the media service request to RR, and RR returns to the terminal to select the optimal node to serve the terminal. Finally, the terminal establishes a connection with the streaming service node and starts the media service process. + +# Appendix II + +## Implementation mechanisms related to the functions + +(This appendix does not form an integral part of this Recommendation.) + +This appendix describes possible implementation guidelines for realizing the MCDN functions. It gives the essential procedurals in order to understand how the MCDN works. The detailed solutions and the relationship with the reference points are for future study and are to be specified in the future ITU-T Recommendations. + +Content access is the first step for MCDN to provide services for users. It is the process of content injection from the source server into MCDN, so that the content of the source server can be obtained by the MCDN system. When the user requests the content, the MCDN content routing system optimises the content selection process to the MCDN node closest to the user with the best performance, and finally the node provides services to the user. The following clauses describe the implementation mechanisms of content access, content distribution, content routing and content service. + +### II.1 Content access mechanism + +Content access means the process of ingesting content into MCDN. This clause will introduce three methods for MCDN to access contents, which are content ingestion, content pre-ingestion, and back-to-source method to access content of arbitrary content formats. When MCDN receives a content ingestion request from CMS, or a service request from an end-user while MCDN does not have the required content, it will access referred content from a content and metadata source and store it in MCDN. + +#### II.1.1 Content access methods + +##### II.1.1.1 Content ingestion + +In the content ingestion method, the application/service management system will actively send instructions to centre nodes of MCDN which will acquire and store contents according to the instruction. Therefore, MCDN can directly serve contents to end-users upon requests, elevating the end-user experience of the service. Content ingested using the content ingestion method will be stored in MCDN permanently until removed by instruction. + +MCDN supports different content ingestion methods and strategies for different content providers. It also supports ingested content management, including content addition, deletion, and update. + +##### II.1.1.2 Content pre-ingestion + +The application/service management system can send instructions to MCDN, directing it to acquire content from the content and metadata source, so that MCDN can later directly offer services to end-users nearby for content acquired through pre-ingestion, which will be deleted based on popularity instead of being permanently stored in MCDN. Pre-ingestion content can have a protection duration to prevent it from being deleted. After a content is deleted, MCDN can still serve that content through the back-to-source method. + +##### II.1.1.3 Back-to-source + +The back-to-source method does not require ingesting content into MCDN in advance. Instead, upon receiving a request from an end-user, MCDN acquires content from the content and metadata source in real time, and serves it to the end-user through nearby nodes. To use the back-to-source method, MCDN needs to be configured to access a configuration table of content providers. + +MCDN should support different back-to-source methods and strategies for different content providers. It should support back-to-source requests aggregation inside a node, which means that MCDN will deliver content to all requesting users after retrieving it. MCDN should support a back-to-source method using a service URL or specific back-to-source URL, as well as supporting back-to-source methods for both static and dynamic content. + +##### **II.1.1.4 Unique identification method** + +Considering that MCDN should support multiple content ingestion methods, content ingestion for different application/service management systems, and multiple content ingestion requests in one application/service, it is required to introduce the UniContentID to identify different contents from different content providers. + +### **II.2 Content distribution mechanism** + +#### **II.2.1 Content distribution methods** + +Content distribution refers to the process of content distribution in MCDN network based on a user request or active content management strategy. MCDN content distribution is mainly based on active distribution (PUSH) mode, while passive distribution (PULL) mode is optional. + +##### **II.2.1.1 Active distribution (Push mode)** + +Smart PUSH distribution is necessary for the MCDN. The MCDN can actively adjust the distribution of hot content in the content distribution system and push hot content to the edge nodes according to the current status of content services in the MCDN. + +For PUSH distribution mode, it is necessary to support single or batch manual distribution and automatic distribution. At least, it should support the immediate and regular distribution strategy of new content; support content distribution according to the attribute policy of the content domain of the node; expand support for distribution strategies such as setting distribution threshold according to the amount of visits; support classified and hierarchical content distribution strategy; expand support for distribution priority, and update the frequency and distribution threshold of content. + +##### **II.2.1.2 Passive distribution (Pull mode)** + +For the smart PULL distribution mode, when the content is not hit locally by the request, it is necessary to support real-time access to the upstream MCDN to download content while providing services for users, and the service delay must be bound by service requirements. The edge node should support updating its own storage based on the hotspot to improve the hit rate. + +### **II.3 Content routing mechanism** + +MCDN content routing chooses the appropriate MCDN according to the user content routing strategy to schedule end user's requests, and dispatches the end user's requests to the appropriate MCDN nodes. + +MCDN content routing mainly includes DNS and IP application layer scheduling, which can be deployed separately or in combination. + +#### **II.3.1 DNS routing (GSLB)** + +The MCDN routing server (GSLB) needs to register the domain name and assign a secondary domain name to each business platform that uses a canonical name (CNAME) record to invoke GSLB capabilities. MCDN GSLB can be interpreted by DNS for selecting MCDN edge nodes or MCDN RR for users. GSLB should support the following routing strategies: + +The user content routing strategy based on proximity should be supported, and the user requests should be scheduled to the MCDN near the user's physical location according to IP or IP segment. + +The content routing strategy based on weight should be supported, and user requests should be scheduled to the MCDN with low weight according to node weight strategy. + +IP blacklisting strategy should be supported, which means that a request from any specific IP in the list will be scheduled to a designated MCDN or will be denied of service. + +Partition routing strategy should be supported, which can be scheduled to a designated MCDN node or node groups based on a specific city code. + +Special routing strategy should be supported, meaning applying a specific scheduling strategy request or characteristics of user's request. + +Any combination of the above content routing strategies should be supported. Their priorities in descending order are: IP blacklisting – > content type – > special strategy – > proximity – > partition scheduling – > weight – > load. + +Default strategy should be supported, which means that if a request comes from a terminal IP or LDNS IP outside of any service IP segment, by default it will be scheduled to a designated service node to provide services. + +In order to improve the reliability of the system, the dispatching control subsystem supports the deployment mode of dual-plane network. The two nodes can work based on the main standby mode or load sharing mode. + +- 1) Resolving the whole network request to the main dispatching centre, and the terminal actively switching to the standby dispatching centre in abnormal circumstances. +- 2) Based on the IP address segment, area or service, the terminal uses different dispatching centres according to the URL. + +#### **II.3.2 IP application layer routing (RR)** + +The main function of MCDN routing server (RR) is to schedule service requests from terminals to appropriate MCDN nodes. After receiving the user's terminal service request, RR chooses the appropriate MCDN node (RR node or media service node) for the user according to the user's content routing strategy. RR should support the following routing strategies: + +The user content routing strategy based on proximity should be supported, and the user requests should be scheduled to the node near the user's physical location according to IP or IP segment. + +User content routing strategy based on node load should be supported. User requests should be scheduled to MCDN nodes with good network conditions and light loads (configurable threshold) according to node load (such as node traffic, number of connections, health status, etc.). + +The content routing strategy based on node weight should be supported, and user requests should be scheduled to the node with low weight according to node weight strategy. + +Scheduling based on content domain should be supported. RR supports querying the MCDN service configuration table to obtain the protocol type attribute of the content domain based on the URL from the user's request, and the MCDN node whose content domain attribute is a subset of the protocol type is selected for scheduling. + +IP blacklisting strategy should be supported, which means that requests from any specific IP in the list will be scheduled to a designated MCDN or will be denied of service. + +Partition routing strategy should be supported, which can be scheduled to a designated node or node groups based on a specific city code. + +Special routing strategy should be supported, meaning applying specific scheduling strategy according to URL or characteristics of user's request. + +Any combination of the above content routing strategies should be supported. Their priorities in descending order are: IP blacklisting – > content type – > special strategy – > proximity – > partition scheduling – > weight – > load. + +Default strategy should be supported, which means that if a request comes from a terminal IP or LDNS IP outside of any service IP segment, by default it will be scheduled to a designated service node to provide services. + +Optionally, content-based scheduling can be supported to schedule user service requests to the node with requested content. + +In order to improve the reliability of the system, the dispatching control subsystem supports the deployment mode of dual-plane network. The two nodes can work based on the main standby or load sharing mode. + +- 1) Resolving the whole network request to the main dispatching centre, and terminal actively switching to the standby dispatching centre in abnormal circumstances. +- 2) Based on IP address segment, area or service, the terminal uses different dispatching centres according to the URL. + +In order to improve system security, it is necessary to protect the system from DoS attack by limiting the number of connections from the same IP and some other methods, and to support the configuration of turning on anti-DoS characteristics. + +## **II.4 Multimedia content location and streaming service mechanism** + +Multimedia service refers to the process in which MCDN provides high quality content service to the end user after the end user's request is authenticated according to the reference points protocol, request command and service strategy of the user's requests. If the MCDN does not find the content, it can obtain the content through the content distribution mechanism and provide media services to the user. + +Multimedia services in MCDN must support audio and video streaming services for PC, PAD, mobile devices and other terminals; support video on demand (VOD) and live broadcasting services based on HLS, HTTP progress download (HPD) and other protocols; support virtual reality (VR), 8K, 4K, Blu-ray, HD, SD and other streams; support H.264, H.265, AVS2, CBR, VBR and other coding methods to provide services; and support different media service strategies for different domain content providers. + +# Appendix III + +## Authentication mechanisms + +(This appendix does not form an integral part of this Recommendation.) + +## III.1 Authentication mechanism in the edge node + +In the edge node, authentication adopts an open-loop encryption and decryption mechanism, which supports authentication based on service authentication digest with algorithm and key, and is verified by the MCDN edge service node. It supports a variety of encryption and decryption algorithms and verification strategies, and can flexibly configure and expand new encryption and decryption algorithms and verification strategies. + +A typical authentication mechanism in edge nodes allows a portal (EPG, PC Portal, etc.) and MCDN to share a key, and uses a symmetric algorithm such as advanced encryption standard (AES) to encrypt and decrypt. The portal adds the encrypted service authentication digest (such as authentication key "authInfo" to prevent third-party redirection) to the URL which is then returned to the user. The user uses the URL containing the service authentication information to request content playback from the MCDN. The MCDN decrypts and checks the URL to ensure the legitimacy of the user's service. The key used for the open-loop encryption and decryption mechanism needs to be updated regularly and be synchronized when updating. The specific process is as indicated in Figure III.1. + +![Diagram of the authentication mechanism in the edge node. It shows three main components: Portal (EPG/PC portal), Terminal (PC/STB/mobile), and CDN. The process involves five steps: 1) Terminal requests playlist from Portal; 2) Portal generates URL with anti-theft chain; 3) Portal returns playing URL with anti-theft chain information to Terminal; 4) Terminal requests URL with anti-theft chain information from CDN; 5) CDN checks anti-theft chain.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` +graph TD; Portal[Portal EPG/PC portal]; Terminal[Terminal PC/STB/mobile]; CDN[CDN]; Terminal -- "1) Request playlist" --> Portal; Portal -- "2) Generate URL with anti-theft chain" --> Portal; Portal -- "3) Return the playing URL with anti-theft chain information" --> Terminal; Terminal -- "4) Request URL with anti-theft chain information" --> CDN; CDN -- "5) Check anti-theft chain" --> CDN; +``` + +H.644.3(20)\_FIII.1 + +Diagram of the authentication mechanism in the edge node. It shows three main components: Portal (EPG/PC portal), Terminal (PC/STB/mobile), and CDN. The process involves five steps: 1) Terminal requests playlist from Portal; 2) Portal generates URL with anti-theft chain; 3) Portal returns playing URL with anti-theft chain information to Terminal; 4) Terminal requests URL with anti-theft chain information from CDN; 5) CDN checks anti-theft chain. + +Figure III.1 – Authentication mechanism + +### III.2 Double authentication mechanism in centre and edge node + +In order to further reduce the complexity of the edge node and the difficulty of configuration and maintenance, MCDN can adopt a double authentication mechanism in the centre and edge nodes. + +This authentication is checked twice by the MCDN centre node (such as RR) to verify the authentication information brought by the portal. After checking, the centre node replaces the authentication information with a token, and the terminal carries the token information shared by the centre and edge nodes to the edge node for service. See Figure III.2. + +![Sequence diagram of the double authentication mechanism involving Portal, Centre node, Terminal, and Edge node.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +sequenceDiagram + participant Portal as Portal +EPG/PC portal + participant Centre node as Centre node + participant Terminal as Terminal +(PC/STB/mobile) + participant Edge node as Edge node + + Note right of Centre node: H.644.3(20)_FIII.2 + + Terminal->>Portal: 1) Request playlist + Portal-->>Terminal: 2) Return playlist and anti-theft chain + Terminal->>Centre node: 3) Access to the centre node + Centre node-->>Terminal: 4) Request the anti-theft chain with token after certification + Centre node->>Edge node: 5) Share the token key + Terminal->>Edge node: 6) Request URL with token + Edge node-->>Terminal: 7) Play after the certification has passed + +``` + +The diagram illustrates a 'Double authentication mechanism' involving four entities: Portal (EPG/PC portal), Centre node, Terminal (PC/STB/mobile), and Edge node. The sequence of interactions is as follows: + + +- The Terminal sends a 'Request playlist' (1) to the Portal. +- The Portal responds with 'Return playlist and anti-theft chain' (2) to the Terminal. +- The Terminal then sends 'Access to the centre node' (3) to the Centre node. +- The Centre node replies with 'Request the anti-theft chain with token after certification' (4) to the Terminal. +- Simultaneously, the Centre node sends 'Share the token key' (5) to the Edge node. +- The Terminal sends a 'Request URL with token' (6) to the Edge node. +- Finally, the Edge node sends 'Play after the certification has passed' (7) back to the Terminal. + + A label 'H.644.3(20)\_FIII.2' is present near the Edge node. + +Sequence diagram of the double authentication mechanism involving Portal, Centre node, Terminal, and Edge node. + +**Figure III.2 – Double authentication mechanism** + +# Bibliography + +- [b-ITU-T H.780] Recommendation ITU-T H.780 (2012), *Digital signage: Service requirements and IPTV-based architecture*. +- [b-ITU-T J.191] Recommendation ITU-T J.191 (2004), *IP feature package to enhance cable modems*. +- [b-ITU-T X.609] Recommendation ITU-T X.609 (2015), *Managed peer-to-peer (P2P) communications: Functional architecture*. +- [b-ITU-T X.1255] Recommendation ITU-T X.1255 (2013), *Framework for discovery of identity management information*. +- [b-ITU-T Y.2080] Recommendation ITU-T Y.2080 (2012), *Functional architecture for distributed service networking*. +- [b-ITU-T Y.2084] Recommendation ITU-T Y.2084 (2015), *Distributed service networking content distribution functions*. +- [b-ITU-T Y.2206] Recommendation ITU-T X.2206 (2010), *Requirements for distributed service networking capabilities*. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1 --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c395c4bbde83b1e232652a43f51538278c116f51f710c37e20a073f7333726c8 +size 6134 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf2bf904b2549344d9527deda50c7afb97ce14ea --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d117fd6749a4a845ae3dffbb843fd52310b147b49b758661288838bb4a0db8e1 +size 96885 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcf7e908b51b30ae78cc1f977fe7c2c69e13959e --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca77aa4953c517523ce33a2a85ca8c7eb330122d32d56b841f773b0ccbd4bb9c +size 70391 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73adc34ac1d0fd34500abc3effb2b8926b6f4485 --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bde991352096a42f71c612e2f2f3efab64413186c1f3d377c5bc4786ca1d2070 +size 115655 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..becf19cfcc9f1c84a7b9cb0424ae2910fb534dbc --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:243f379c90f88d27336033982a501abf2c379b06992ea083d8a9f28ce8f762ce +size 47946 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c3f3a3a3960fc30c42257ebe2132ba92ad6dc8a --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1d0dd5ea43879a4fd4593e6b89600ae44c7fbb80fa292f14787fceb664f2123 +size 101148 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/aaec7c7044d764c324cdb35c0201da6f_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/aaec7c7044d764c324cdb35c0201da6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0db5abec813e629ab746e4cea1a61a77185c6025 --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/aaec7c7044d764c324cdb35c0201da6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c84f570eaa28c6ba951a61ef019ebf4f98f000a447ca726020809f6f833fc60 +size 4165 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bd6e25ada1931176e41d07a6b1019f5274315dd --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e19634d2a33c4fa9dbff31ae6127e8e5eeb3b221d37de739b7699c942fec028e +size 56010 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/c37fe03d7cad74ad675a0eb16aa43821_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/c37fe03d7cad74ad675a0eb16aa43821_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c338694926cfb295c1c56e08fafad2eb3af45388 --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/c37fe03d7cad74ad675a0eb16aa43821_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35ef5bc679cfe79c52dfb1e15e5c5dea0aa9f62b61959c4bc6bc43314b668afe +size 3533 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35e9ab0f321ae56c7a641cdba1824d959c2bd189 --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:196abab8af61977a87ccabb4cd49aa8b292fffb3102207d8e5cead717a56f9cc +size 49330 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fbc54813ffd3b9d66f3d73da1c6542852d7bb44 --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64f9c566a9f9f501b17f646ebab6143873bfc46ac3ee5d2a9b8dc5cdb11d0410 +size 48528 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd9a8cef83aa8999f9cc1f351a8567a09fbec5b3 --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31132c733755cfb7f9df8babf6477600a1dbc3f5f6e365636d2fbc19105e010b +size 48757 diff --git a/marked/H/T-REC-H.644.4-202106-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/H/T-REC-H.644.4-202106-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7d86c86e1404fa1114a15f0945b90cfb1e26c16 --- /dev/null +++ b/marked/H/T-REC-H.644.4-202106-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1dbbdd25dfae00f9e9fa55d2eef713949839f6820533661fc332421f15e7225 +size 74152 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e031964d09184dc7046b91ff14b9730eac74ca12 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49969aa08fe5a13d5b6e583d5b8cf9621f74d5790c994ff674b513e368816a9e +size 91543 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bdd7bc1d3581fbdc3cf6b035f618693dbe3846 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75efa8e3513a799767c04a0bb7bcd87a550f2378f5880629068581808c1c9f7f +size 7353 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f43491c3b8a24a3d82959f2e8049939e528ea569 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4aa3098c208d4102e12762d30e5313513c0187a79e8dd6075f9f4573ac1902de +size 58434 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a3fb6ee2128a3305b2aee0003215d379653d509 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9b5edc35ec04afdbb9ca6cd8a4a439b640f342f8510252e91bdf226e560794a +size 64012 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5af85a30ab2f902f8208fd95c7600b8949d1f3a --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94e98e026e7c90981374a87efef63791cc743d2472857a56e99d4a26df798c26 +size 56836 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92506e0ba422af6a049ed0da285adccb85f3f65c --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0af6ba86887725638f976547e0d802fc760922f21eab06776e4dbe37a2a79988 +size 59690 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5753932efd669a291b5b194dbe815ca20582858 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be209865a4b3af79880bf916f079375eb7137ad16a0e09d9712d2cb34a486581 +size 58508 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c5ce622c6ee5d24c5ea89c07f595fe790bcc5de --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:201b5d796112b79064caf193bd4ac5c3ea777c7933a7d12eaed306a1438ad778 +size 56380 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0589e359d8b052b3a00bbd6d6434c8d156e55678 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28ae160aaa5059a883e8d1fbf5afebf08b428ef97d0be8d8c9b14f6d57db9b59 +size 66350 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a280df2dabee367fa8d8f0bfb62f6662c84c1639 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8e9f86bf5b14e17ac3b8c67b79d221cc4d06138ceeb490298aef6c969619229 +size 67516 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dae3685e94031671276e067f035a981ad4ecf3fa --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8044d06c3a8557addcd2cef022f564cba85df451a708dcad81cd8fdc41d5d88c +size 37999 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a6a9a745b6f4e7f8660e4e70dd6ab1c7b4ab0f4 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03183a761fc37a52f268010c718df5aae3e1467cfe7f156090a6f43c0be731b1 +size 34729 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b18964de63db535dd45e6ea45cf71aaede22b1a --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13818229d7cec325e594ef72701a4f82445563aa69a3a22537c000f915282586 +size 52638 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..760fc0d37b596e76ba9879c91f1cd8e30db4c314 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb40c65b0dd3b9872d50f5ff1b43f260e35cf43440bdf753733215bcddbaeac6 +size 55481 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f5ee6e0b27264f5954c2cdbc9cc0db6acd3c4fa --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:581a66938184fd1092c46e8c871c05bb4695e473e46dbec0b986d2244485a2fe +size 53506 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ab21e04969d78bad854a64e383f6d6d96a46ffb --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea54c68fefaa094e244006637d38d2def2583629a2d79bd20de4c32e40dbe418 +size 54198 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87955280d7d9a6c65f56fa94024f637e79afc038 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f019dc10cd9c2a9b6a8fddc0fc7cb64b37d85a8ad944631e057f192043323a93 +size 53089 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/b2f5606b9c7184c1c6070a290080a3e3_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/b2f5606b9c7184c1c6070a290080a3e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9480316e04d0ec15ae657c7b877455fe757b624a --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/b2f5606b9c7184c1c6070a290080a3e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:126c6887f54bd092173213042d09e648f9bf45706c0e75d419d80232a74ba6f9 +size 57538 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e5baeea666e0eca2e4e1417cfd55e7352b72a92 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0c2e4fce20c12c779457f4c8090079076738e4becba66f0b081e7e6b32b8e77 +size 94412 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56c7f97d83ac1e506e78c7ca2c6b3d04146b8cfe --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8a6f87f8dff121a1c1b8c4b6d17dc9991b040bc9d991400a226610c78eb92f1 +size 59585 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75d984f189e3c78ed6b95e835bdfa6d9ca962b75 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b8880eda7a8d2562e535009ba6a8632ce4eda72fbd217291059979affe36bfd +size 56852 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d44c886a6d74e3f409a0e6eeb53feec93038b639 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:281605e7dc305a45149209c9dd8df751bc26b18f7d0205cec94ac86bd939d88f +size 52480 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dac87ff319be10b98c0e831bbe45cd66454c8e7b --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b49128341c17153d8999e880f1ac2065c6b59dccfc1bd4b48c34e26f4e56a836 +size 126165 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15d1b57d150034856fdd7f5f2dca1dd37c584f93 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a9cee4c66755f907e210c9073f2788246c99ec1ba8b5a43c10a408935467f7b +size 33922 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6ed2ae4102cd0e45c0c5758c8cc54e061d9678e --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4513034cfcb06926080f705494f9ee3b9c76ebb17dda1aa2f64d3a776c4ead9c +size 52186 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7344a32faccaf24f745e80f2129737207a95bbf --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fb87f20acf9518e47e5dd2b1b283d13dd2b38d2960c9536f663156e6f1bf03d +size 4404 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbdafd6494abf243f4edd96a5b8c0d4a7fa5d919 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0ef34e998a6bcd92f448d94d493dde8cff1c190b5bc092bf0193bc844b2b440 +size 81898 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..150b2db5217dd54c6697525fb60080564d214df6 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9f5a619684c6607c72f87ca73208349c28d4c755b9c1e1c30566fb9d61a44ea +size 4083 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/f5deee2f3301ee351c4008283ffafbb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7952b81b784ab8793750b2eb253c37da2cacbc79 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/f5deee2f3301ee351c4008283ffafbb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:258bdbf2b1fee91fbf071b532fef43e372cfc4fff939aaf2a4f9fb7abe5becd5 +size 43206 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..282a334eb60d62beffc9475a300ec75bc2a32c18 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6d11463c749e407bc2f7d7a1dcfe23e70d0da7268778221423de6456763cf03 +size 33924 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8893c265eb777d026ebe546ba7110ce98b1a784a --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7513ba6a42c2299538bcf6a59be632e8a17297340497c69409092094adddb90 +size 49872 diff --git a/marked/H/T-REC-H.644.5-202212-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/H/T-REC-H.644.5-202212-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9738b07906e9bbd8536989320cb05147409e191 --- /dev/null +++ b/marked/H/T-REC-H.644.5-202212-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81e678998244147ea9eb796593489a9d738c771819098ae20077229fa7559e4c +size 113598 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd003ca3ddc30be1023c774cc140b81762530af5 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71109f18cd997ff882d8e2cfe800f46cfb4c444aff5d575c55e43bfbf4834dbb +size 42717 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f110a09448ffd64dc02d76bf7c780c14fd386cde --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bbf642be99ec4dde63904b34564571c1e66541b01ab90d9860acd56e18154da +size 41195 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9016d18beced8a7e5aabb300232a838bccd26bb --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35116e9b55f911504e12d95b0f46fb4ad8c1d05fbdaa043f68d617e062e28fb2 +size 43282 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bba8d77f37ceba9a23509057f71199f5b8081dbc --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd62919857e44216ec957ef03243b6096e9cb64d6e00653f5704784d8514045c +size 6856 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3852275e9c9715c59485c1547467d8aed83af85d --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:643af5f76865e511956cf9bff41a66a565e6cc6e569b82164c6311b43dca2c44 +size 42765 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..885093cc41101cd61efd09be686c0571e1f29328 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48fcc3c078d4fab87f2d1c717175965518e214abad58fb4707e7229e00409446 +size 3546 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99b36cbc91414e5b454f10c51031633bd372b9f7 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:763a1a806367a75e22d05162f7394cf7ec3ba24929dc23776f372a6175001170 +size 40892 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ee2363eb2059e0cb9be598d827ca32402423e63 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed73bb229578286c84b12f5258b85ded73380eca15731fdfba1cb669667c5442 +size 4471 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea04592b45b22f50257dda33d8bf37f5a8e98017 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db1fd1523b82146fa5df84f58d6017e16f6988ddf3eb57db36e4e033326e71f7 +size 10322 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9276ff1230a01ff8efd9326578692b42b608068 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99d1e567b9d4cd99ac7e19a3c4ae353973c30f96d47bf47205dc941c8497f11a +size 40589 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cf48bac2c9bd6ff27bc0cb58713abb4e4bd5e5b --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c201af5e2981f616d69052940a3d5aa25eb1fa3b9d13fbdffdc66625a0c634ea +size 86278 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c78c8e896967d677519474424f95bdef06226f6 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b0db249f4a88f6f3ea0e50a2d4d8b09402a252c9d702007079c3c790c2b1f80 +size 32597 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbcfe037d62238ea6c4d8ffa5adf9851dbae77dd --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a45ab3065d8ded0827b634ada77eb87adf6d9f53efe540d23c5bd2db507e026 +size 15710 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/a706c91f074ac2840c161a3d4a7c0f91_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/a706c91f074ac2840c161a3d4a7c0f91_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e19cff0a3076822737a96293008086e33c1091d7 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/a706c91f074ac2840c161a3d4a7c0f91_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9b3f2c5cbe9ad6c8cf73bcd900b7dedc948ed67b828d00fbfb8dfc5a6f2bb8c +size 61709 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8dff9f875d2930fd255662f60beac26f1a2c027 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfeb85c0ff9ca0b2a2dd3cb30f6c2bd421e5a001394dd981412bf59099986808 +size 67477 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b2c97d20b9daf5dc42a32b1d6e66819669cd6c7 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dd0701ba64ac5020d11e9f6356033772a5ebe46a54737a97f62c17333e3a4ef +size 34055 diff --git a/marked/H/T-REC-H.703-201607-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.703-201607-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8140e71dc05f88da42e119434c033237c905f1c6 --- /dev/null +++ b/marked/H/T-REC-H.703-201607-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55d22edb9ac7c6acb67b6e4f3393a72d2b9007a17dcf6088561efcb1e42b7d2c +size 104996 diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/raw.md b/marked/H/T-REC-H.705.1-202309-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cc2eafc632152332ae52d03928792cc2f079a4b2 --- /dev/null +++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/raw.md @@ -0,0 +1,1803 @@ + + +# Recommendation**ITU-T H.705.1 (09/2023)** + +SERIES H: Audiovisual and multimedia systems + +IPTV multimedia services and applications for IPTV – +General aspects + +--- + +### **Layered specification for the IPTV service platform functional architecture based on open service capabilities** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circle with a globe-like design. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +## **Audiovisual and multimedia systems** + +| | | +|-----------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| General aspects | H.700-H.719 | +| IPTV terminal devices | H.720-H.729 | +| IPTV middleware | H.730-H.739 | +| IPTV application event handling | H.740-H.749 | +| IPTV metadata | H.750-H.759 | +| IPTV multimedia application frameworks | H.760-H.769 | +| IPTV service discovery up to consumption | H.770-H.779 | +| Digital Signage | H.780-H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.705.1 + +# Layered specification for the IPTV service platform functional architecture based on open service capabilities + +## Summary + +Recommendation ITU-T H.705.1 describes a layered architecture of Internet protocol television (IPTV) service platform intended to provide open service capabilities for diversified IPTV services. In comparison with the high-level IPTV functional architecture defined in Recommendation ITU-T Y.1910, the layered architecture decouples service logic from data resources and decomposes the functions of the IPTV service platform into more granular modules. This Recommendation specifies the fine-grained functional modules and reference points, by considering the aspects of service offering and operational management. It also defines typical procedural flows on content preparation, service presentation and content consumption in appendices. + +This Recommendation provides a reference for IPTV service providers to construct the open platform of IPTV services and enables automatic deployment and fast iteration of multimedia applications in the platform. It is of benefit in promoting the service capability of IPTV and further enhances user experience on using diversified IPTV services. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.705.1 | 2023-09-13 | 16 | 11.1002/1000/15633 | + +## Keywords + +Fine-grained service module, IPTV, IPTV service platform, layered architecture. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2023 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|-----------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Overview..... | 4 | +| 7 | Layered architecture ..... | 6 | +| 7.1 | Service presentation layer (L3) ..... | 6 | +| 7.2 | Capability encapsulation layer (L2) ..... | 6 | +| 7.3 | Data resource layer (L1)..... | 7 | +| 7.4 | Operation and maintenance management..... | 8 | +| 8 | Functional description of user interface ..... | 8 | +| 9 | Functional description of service access control ..... | 8 | +| 9.1 | Service access ..... | 8 | +| 9.2 | Service capability discovery..... | 9 | +| 10 | Functional description of service capability ..... | 9 | +| 10.1 | Content management service..... | 9 | +| 10.2 | Service navigation service..... | 12 | +| 10.3 | Service control service ..... | 15 | +| 10.4 | Content delivery service ..... | 18 | +| 11 | Functional description of data service ..... | 21 | +| 12 | Functional description of O&M management ..... | 21 | +| 12.1 | Upgrade management..... | 21 | +| 12.2 | Monitoring management ..... | 22 | +| 12.3 | Logging management ..... | 22 | +| 12.4 | Security management ..... | 22 | +| 13 | Reference points ..... | 22 | +| 13.1 | Reference points A ..... | 25 | +| 13.2 | Reference points for implementing service invocation..... | 25 | +| 13.3 | Reference points U ..... | 26 | +| 13.4 | Reference points C ..... | 27 | +| 13.5 | Reference points N ..... | 28 | +| 13.6 | Reference points S..... | 29 | +| 13.7 | Reference points D ..... | 29 | +| 13.8 | Reference points M..... | 30 | + +| | Page | +|------------------------------------------------------------------------------------------------------------------|------| +| 13.9 Reference points Ci ..... | 31 | +| 13.10 Reference points Ni ..... | 32 | +| 13.11 Reference points Si..... | 33 | +| 13.12 Reference points Di ..... | 35 | +| Annex A – Metadata information relating to content distribution..... | 39 | +| Appendix I – Procedural flows relating to IPTV services ..... | 41 | +| I.1 Content preparation flows ..... | 41 | +| I.2 Service/content presentation flow ..... | 42 | +| I.3 Content consumption flow ..... | 43 | +| Appendix II – Mapping relationship of functional modules between [ITU-T Y.1910] and
    this Recommendation ..... | 46 | +| Bibliography..... | 48 | + +# Recommendation ITU-T H.705.1 + +# Layered specification for the IPTV service platform functional architecture based on open service capabilities + +# 1 Scope + +This Recommendation describes a layered specification for the functional architecture of the Internet protocol television (IPTV) service platform intended to provide IPTV services with open service capabilities based on IPTV service requirements [b-ITU-T Y.1901] and architecture framework [ITU-T Y.1910]. It addresses detailed functional requirements that are not considered in the IPTV functional architecture. Starting from a general description of a horizontal layered structure, this Recommendation specifies service-oriented modules and interfaces that provide more granular definitions for the IPTV service platform. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.644.3] Recommendation ITU-T H.644.3 (2020), *Functional architecture of multimedia content delivery networks*. +- [ITU-T H.644.5] Recommendation ITU-T H.644.5 (2022), *Functional architecture of content request routing service in multimedia content delivery networks*. +- [ITU-T H.721] Recommendation ITU-T H.721(V3) (2022), *IPTV terminal devices: Basic model*. +- [ITU-T H.741.5] Recommendation ITU-T H.741.5 (2024), *Overall aspects of personalized IPTV service*. +- [ITU-T H.750] Recommendation ITU-T H.750 (2008), *High-level specification of metadata for IPTV services*. +- [ITU-T H.751] Recommendation ITU-T H.751 (2013), *Metadata for rights information interoperability in IPTV services*. +- [ITU-T H.752] Recommendation ITU-T H.752 (2015), *Multimedia content provisioning interface for IPTV services*. +- [ITU-T H.753] Recommendation ITU-T H.753 (2019), *Scene-based metadata for IPTV services*. +- [ITU-T H.760] Recommendation ITU-T H.760 (2009), *Overview of multimedia application frameworks for IPTV services*. +- [ITU-T H.770] Recommendation ITU-T H.770 (2015), *Mechanisms for service discovery and selection for IPTV services*. +- [ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*. +- [ITU-T Y.2019] Recommendation ITU-T Y.2019 (2010), *Content delivery functional architecture in NGN*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 application** [b-ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services. + +**3.1.2 service** [b-ITU-T T.174]: A set of functions provided by a (server) software or system to a client software or system, usually accessible through an application programming interface. + +**3.1.3 metadata** [b-ITU-T Y.1901]: Structured, encoded data that describe characteristics of information-bearing entities to aid in the identification, discovery, assessment, and management of the described entities. + +**3.1.4 application programming interface (API)** [b-ITU-T Y.110]: This is an implementation interface between equipment and a software module and does not have any physical realization as it is internal to the equipment. + +**3.1.5 content delivery** [b-ITU-T Y.2080]: In the context of the distributed service networking (DSN) functional architecture, the operation of sending and receiving content between the requested peer and the requesting peer or client. + +**3.1.6 content distribution** [b-ITU-T Y.2080]: In the context of the distributed service networking (DSN) functional architecture, the whole process of content sending from one or more content sources, and sharing among DSN nodes. + +**3.1.7 Internet protocol television (IPTV)** [b-ITU-T Y.1901]: Multimedia services such as television/video/audio/text/graphics/data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. + +**3.1.8 linear TV** [b-ITU-T Y.1901]: A television service in which a continuous stream flows in real time from the service provider to the terminal device and where the user cannot control the temporal order in which contents are viewed. + +**3.1.9 reference point** [b-ITU-T Y.2012]: A conceptual point at the conjunction of two non-overlapping functional entities that can be used to identify the type of information passing between these functional entities. + +NOTE – A reference point corresponds to one or more physical interfaces between pieces of equipment. + +**3.1.10 service navigation** [b-ITU-T H.720]: The process of presenting information that allows the end-user to discover, select and consume services. + +**3.1.11 terminal device (TD)** [b-ITU-T Y.1901]: An end-user device which typically presents and/or processes the content, such as a personal computer, a computer peripheral, a mobile device, a TV set, a monitor, a VoIP terminal or an audio-visual media player. + +**3.1.12 user interface (UI)** [b-ITU-T F.902]: Software and hardware components through which a user can interact with a system. + +**3.1.13 video-on-demand (VoD)** [b-ITU-T Y.1901]: A service in which the end-user can, on demand, select and view a video content and where the end-user can control the temporal order in which the video content is viewed (e.g., the ability to start the viewing, pause, fast-forward, rewind, etc.). + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|------------------------------------------| +| AMS | Audience Measurement Service | +| APCS | Access Permission Control Service | +| API | Application Programming Interface | +| APMS | Application Profile Management Service | +| BCMS | Broadcast Content Metadata Service | +| BCPS | Broadcast Content Processing Service | +| BTSS | Back-To-Source Service | +| CAAS | Charging And Accounting Service | +| CAS | Content Acquisition Service | +| CAS | Content Authorization Service | +| CCSS | Content Consumption Statistic Service | +| CDCS | Content Delivery Configuration Service | +| CDMS | Content Distribution Management Service | +| CDS | Content Distribution Service | +| CMS | Cast Metadata Service | +| CPAS | Content Protection Authorization Service | +| CPCS | Content Processing Control Service | +| CPPS | Content Pre-Processing Service | +| CPRS | Content Popularity Ranking Service | +| CPS | Content Protection Service | +| CRM | Customer Relationship Management | +| CRS | Content Rating Service | +| CSS | Content Searching Service | +| DASH | Dynamic Adaptive Streaming over HTTP | +| HTTP | Hypertext Transfer Protocol | +| IPTV | Internet Protocol Television | +| MAFR | Multimedia Application Framework | +| MCDS | Multicast Content Delivery Service | +| MPPS | Metadata Post-Processing Service | +| NCMS | Navigation Category Metadata Service | +| PMS | Picture Metadata Service | +| PRS | Personalized Recommendation Service | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| RTSP | Real-Time Streaming Protocol | + +| | | +|-------|--------------------------------------------| +| SAMS | Service/Application Metadata Service | +| SCSS | Service/Content Subscription Service | +| SMS | Session Management Service | +| SPMS | Service/content Package Management Service | +| TD | Terminal Device | +| UAS | User Authentication Service | +| UCDS | Unicast Content Delivery Service | +| UECSS | User Events Collecting and Sharing Service | +| UI | User Interface | +| UITMS | UI Template Management Service | +| UPMS | User Profile Management Service | +| URL | Universal Resource Locator | +| URSS | User Request Scheduling Service | +| VCMS | VoD Content Metadata Service | +| VCPS | VoD Content Processing Service | +| VOD | Video On Demand | +| VR | Virtual Reality | + +# 5 Conventions + +In this Recommendation: + +**Layer:** In the context of IPTV service platform layered architecture, "layer" is defined as a functional tier with a collection of modules. It is represented by the following symbol: + +![Symbol for Layer: A dashed blue rectangle with the word 'Layer' in blue text inside.](e9b30aeb317ed964fa6de36804acf24c_img.jpg) + +Symbol for Layer: A dashed blue rectangle with the word 'Layer' in blue text inside. + +**Module:** In the context of IPTV service platform layered architecture, "module" is defined as a collection of functionalities. It is represented by the following symbol: + +![Symbol for Module: A solid black rounded rectangle with the word 'Module' in black text inside.](d3f6de4fe9f9138fc6afc584b5104433_img.jpg) + +Symbol for Module: A solid black rounded rectangle with the word 'Module' in black text inside. + +**Fine-grained service module:** In the context of IPTV service platform layered architecture, "service module" is defined as a group of functionalities that cannot be further subdivided at the level of detail in this Recommendation. It is represented by the following symbol: + +![Symbol for Service module: A solid black rectangle with the words 'Service module' in black text inside.](dc22d132f81aafd8d8e2ebae77bdbedd_img.jpg) + +Symbol for Service module: A solid black rectangle with the words 'Service module' in black text inside. + +# 6 Overview + +This Recommendation intends to comply with the existing technical framework of IPTV recommendations and to introduce a new architecture approach to the IPTV service platform, which further breaks down the functions or functional blocks defined in [ITU-T Y.1910] into a horizontal layered structure and more fine-grained modules, and aims at user experience enhancement from + +the platform point of view. It intends to be a supplement of platform functional architecture to [ITU-T Y.1910] and provides references for open platform construction. + +Figure 1 presents the relationship between [ITU-T Y.1910] and this Recommendation. This Recommendation mainly focuses on four functions defined in [ITU-T Y.1910] and further puts forward their modularization requirements in order to facilitate the scalability and performance of IPTV services. How these functions are mapped into physical entities is out of the scope of this Recommendation. Other functions, such as end-user functions, content provider functions and network functions, can be seen as external functions to the IPTV service platform in this Recommendation. The interfaces between the IPTV service platform and external functions, as shown in Figure 1, are kept aligned with [ITU-T Y.1910]. + +![Figure 1: Relationship between [ITU-T Y.1910] and this Recommendation. Part (a) shows the research scope on functions, and part (b) shows the research scope on technical requirements.](e9314c83043183351ed74908e9bf2f90_img.jpg) + +**a) Research scope on functions (From definition of Recommendation ITU-T Y.1910)** + +The diagram illustrates the functional architecture of an IPTV service platform. A central box labeled "IPTV service platform" contains four sub-functions: "Application functions" (blue), "Service control functions" (yellow), "Content delivery functions" (orange), and "Management functions" (grey). This central platform is flanked by "End-user functions" (pink) on the left and "Content provider functions" (grey) on the right. Below the platform is a "Network functions" box (green). A red dashed box labeled "Scope of this Recommendation" encloses the central IPTV service platform. A blue dashed box labeled "Scope of ITU-T Y.1910" encloses the entire system, including the end-user, platform, network, and content provider functions. + +**b) Research scope on technical requirements** + +| | | Functional requirements in ITU-T Y.1910 | | | | +|----------------------------------------------------|--------------------------------|-----------------------------------------|---------------------------|----------------------------|----------------------| +| | | Application functions | Service control functions | Content delivery functions | Management functions | +| Modularization requirements in this Recommendation | Service presentation layer | | | | | +| | Capability encapsulation layer | | | | | +| | Data resource layer | | | | | + +H.705.1(23) + +Figure 1: Relationship between [ITU-T Y.1910] and this Recommendation. Part (a) shows the research scope on functions, and part (b) shows the research scope on technical requirements. + +**Figure 1 – Relationship between [ITU-T Y.1910] and this Recommendation** + +This Recommendation manages to achieve the following objectives: + +- To separate data storage from business logic enabling either resource access or service functions to be expand on-demand horizontally. +- To decompose functional blocks of [ITU-T Y.1910] realizing the encapsulation in units of service capability for fast iteration and automatic deployment of new application functions. +- To discuss the definition of service capabilities considering all possible scenarios in IPTV services. + +- To take into account security design and operational requirements including emergency, log, etc. + +# 7 Layered architecture + +Figure 2 provides an overview of the layered architecture of IPTV service platform. In this figure, the rectangular areas represent functional layers in IPTV service platform layered architecture. The rounded rectangular blocks represent the functional modules or particular grouping of modules, and the dotted lines represent logical associations between functional modules. + +![Figure 2 – Layered architecture of IPTV service platform. The diagram shows three horizontal layers: Service presentation layer (L3) at the top, Capability encapsulation layer (L2) in the middle, and Data resource layer (L1) at the bottom. L3 contains the 'User interface' module. L2 contains two sub-modules: 'Service access control' (with 'Service access' and 'Service capability discovery') and 'Service capability' (with 'Content management', 'Service navigation', 'Service control', and 'Content delivery'). L1 contains the 'Data service' module. A vertical 'Operation and maintenance management' block on the right is connected to all three layers by dotted lines. A dashed blue box encloses the L3 and L2 layers. The label H.705.1(23) is at the bottom right.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 2 – Layered architecture of IPTV service platform. The diagram shows three horizontal layers: Service presentation layer (L3) at the top, Capability encapsulation layer (L2) in the middle, and Data resource layer (L1) at the bottom. L3 contains the 'User interface' module. L2 contains two sub-modules: 'Service access control' (with 'Service access' and 'Service capability discovery') and 'Service capability' (with 'Content management', 'Service navigation', 'Service control', and 'Content delivery'). L1 contains the 'Data service' module. A vertical 'Operation and maintenance management' block on the right is connected to all three layers by dotted lines. A dashed blue box encloses the L3 and L2 layers. The label H.705.1(23) is at the bottom right. + +**Figure 2 – Layered architecture of IPTV service platform** + +The following clauses give a general description of functional layers and functional modules. A detailed breakdown of modules is further illustrated in clause 8. + +## 7.1 Service presentation layer (L3) + +The service presentation layer provides graphical user interface (GUI) or presentation capability needed by GUI for all kinds of IPTV terminal devices defined in the ITU-T H.72x series of Recommendations [b-ITU-T H.72x]. + +This layer acquires data required by the IPTV services presentation from the service access module in the capability encapsulation layer. + +### 7.1.1 User interface + +User interface modules in this layer present organized IPTV services and contents and react to user interactions, either in web-based or application-based presentation mode. + +## 7.2 Capability encapsulation layer (L2) + +The capability encapsulation layer isolates the upper applications from the underlying resources. In this Recommendation, applications for IPTV services are split into a set of fine-grained and collaborating services. Services are mutually independent and the flexible combination of them is used to meet the various business requirements of the upper applications. + +This layer acquires data required by the service offering from data resource layer (L1) and responds to all the requests for service invocation of IPTV. + +### **7.2.1 Service access control** + +Service access control modules in this layer execute routing functionalities for service invocation. + +#### **7.2.1.1 Service access** + +Service access modules aggregate all access to the backend services and act as the single entry point into the IPTV service platform. This module is responsible for distributing requests across the available services under cooperation with the service capability discovery module. It also manages authentication, access control, load balancing and caching. + +#### **7.2.1.2 Service capability discovery** + +The service capability discovery module is essential for the dynamical changes of service capabilities. It is responsible for determining service availability by handling the registration/deregistration, managing the service registry containing network location information and performing health checks of service instances. + +### **7.2.2 Service capability** + +Service modules in this layer are built around business capabilities of IPTV services. Each service module enables a set of distinct features or functionality by encapsulating business logic, computation, data access and other capabilities. Each service module only exposes application programming interfaces (API) to the service access module for capability invocation by any other services or application's clients. + +From the implementation complexity point of view, services can be formed in two levels: + +- Basic services: simple abstraction of service capabilities to enable basic functionalities of IPTV services, such as media playback functionality. +- Advanced services: complicated abstraction of service capabilities by orchestrating one or more basic services to enable extended functionalities of IPTV services, such as content ranking functionality. + +From the functionality point of view, services can be divided into four categories, as shown in Figure 2. + +#### **7.2.2.1 Content management service** + +Content management service modules perform content aggregation, content life-cycle management, metadata processing and content pre-processing. + +#### **7.2.2.2 Service navigation service** + +Service navigation service modules provide metadata of IPTV services and contents required by service navigation. + +#### **7.2.2.3 Service control service** + +Service control service modules perform access control to network and service resources, including registration, authentication, authorization, subscription and other capabilities. + +#### **7.2.2.4 Content delivery service** + +Content delivery service modules provide content processing and content delivery functionalities for IPTV end users, with the aid of service control and network resource allocation. + +## **7.3 Data resource layer (L1)** + +The data resource layer provides data storage and data serving capabilities for IPTV services. It supports diverse kinds of storage technology to meet different requirements of data reading and writing from the upper layer, such as database, cache, file system, etc. + +This layer only expose interfaces to L2 modules for efficient and secure data service. + +### **7.3.1 Data service** + +Data service modules in this layer provide data storage and data access solutions for massive data of IPTV services. IPTV data can be divided into content metadata, media, user data, operational data and so on. + +## **7.4 Operation and maintenance management** + +The operation and maintenance (O&M) management module performs overall configuration and management for achieving securely operating and intelligent maintenance of IPTV services. This module does not include the functionalities that are provided by functional modules (L2) in the user plane. + +# **8 Functional description of user interface** + +The user interface (UI) module provides the presentation of IPTV services and contents for all kinds of IPTV terminal devices and responds to the end user's requests for discovery, selection and consumption of services and contents. + +This module is responsible for the deployment of UI templates and/or multimedia applications [ITU-T H.760] from content providers or service providers, which contain the layout and orchestration information of user interface and business logic of service presentation. It is also responsible for presenting IPTV services and contents by acquiring service-related metadata and content-related metadata from service access modules. For MAFR-based presentation mode, this module distributes multimedia application framework (MAFR) applications of IPTV services to the MAFR engines. For application-based presentation mode, this module distributes metadata as well as rules or constraints of UI framework and business logic to the application-based clients. + +This module supports user interactions by means of remote controller, touch control, gesture control, voice control, etc. + +# **9 Functional description of service access control** + +## **9.1 Service access** + +### **9.1.1 Request routing** + +The request routing module handles all the incoming requests for invoking service capability of IPTV service platform and routes them to the appropriate service instances. It checks the routing criteria and service monitoring data acquired from the service capability discovery module, determines the routing to a particular service instance, and directs the request to the targeted service's API. It authenticates the requests before routing and implements API mapping between the client's request and backend service, according to the API invocation rules. It performs load balancing functionality based on service monitoring data. This module provides support to simply proxy the requests to each service, it also provides support to invoke multiple service modules and aggregate the results. + +### **9.1.2 Flow control** + +The flow control module controls the flow of access requests for service invocation so as to ensure IPTV service platform working in a highly secure and available way. It provides rate limiting functionality to deal with burst traffic, abnormal access or other emergencies. It also provides configuration functionality for flow control policies. + +### **9.1.3 Communication protocol translation** + +The communication protocol translation module is responsible for translating the protocols between the consumers of the APIs (i.e., service modules in L2, user interface modules or external functions) and the providers of APIs (i.e., service modules in L2), which enables the clients to communicate directly with the services. + +## **9.2 Service capability discovery** + +### **9.2.1 Service registration/deregistration** + +The service registration/deregistration module handles the registration or deregistration requests from fine-grained service modules in IPTV service platform and maintains the service registry. Service instance on start is required to be registered and service instance on shutdown is required to be unregistered in the service registry. This module reviews the registration request and assigns an identify for each start-up service. It is also responsible for updating the registration information in the case of service change (e.g., instance termination). The service registry is a database containing dynamic information of the available service instances, including service identify, the number of instances, and locations (i.e., IP address/port). It provides data querying capability to the service access module for service capability discovery. + +### **9.2.2 Routing criteria configuration** + +The routing criteria configuration module handles the requests for the statement of capabilities from the registered services and configures the routing criteria for each service. This module acquires and reviews the information of APIs stated by the service. It configures the routing criteria concerning the service and the validated APIs. The routing criteria contains the mapping information between the service and its APIs as well as the API invocation rules between this service and other services. This configuration will be made when any one of the service, service APIs or invocation rules change and the latest configuration will be conveyed to the service access module for request routing. + +### **9.2.3 Service monitoring** + +The service monitoring module performs health checks and performance monitoring to the registered service instances for the purpose of verifying whether it is able to handle requests. It supports mechanisms to periodically convey the running state of service instances to the service access module, and service registration/deregistration module. + +# **10 Functional description of service capability** + +## **10.1 Content management service** + +The content management service is comprised of service modules with distinct features or functionality on content management. Figure 3 provides the modular structure of the content management service. The rectangular area in white represents content management service capabilities in basic level, and the rectangular area in grey represents content management service capabilities in advanced level. As shown in this figure, service modules across the white area and grey area have content management service capabilities in basic level and advanced level. + +![Diagram of the modular structure of content management service. The diagram shows a large box labeled 'Content management service' containing several smaller boxes representing service modules. The modules are arranged in a grid: 'Content acquisition service' and 'Content processing control service' in the top row; 'Content protection service' and 'Content distribution management service' in the second row; 'UI template management service' in the third row; and 'Content pre-processing service' and 'Metadata post-processing service' in the bottom row. Below the diagram, a legend indicates that white boxes represent 'Basic services' and grey boxes represent 'Advanced services'. The 'Content pre-processing service' and 'Metadata post-processing service' boxes are shaded grey, while the others are white. The reference 'H.705.1(23)' is shown in the bottom right corner of the diagram area.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Diagram of the modular structure of content management service. The diagram shows a large box labeled 'Content management service' containing several smaller boxes representing service modules. The modules are arranged in a grid: 'Content acquisition service' and 'Content processing control service' in the top row; 'Content protection service' and 'Content distribution management service' in the second row; 'UI template management service' in the third row; and 'Content pre-processing service' and 'Metadata post-processing service' in the bottom row. Below the diagram, a legend indicates that white boxes represent 'Basic services' and grey boxes represent 'Advanced services'. The 'Content pre-processing service' and 'Metadata post-processing service' boxes are shaded grey, while the others are white. The reference 'H.705.1(23)' is shown in the bottom right corner of the diagram area. + +**Figure 3 – Modular structure of content management service** + +The following clauses provide descriptive texts for fine-grained service modules of the content management service. + +### 10.1.1 Basic services + +#### 10.1.1.1 Content acquisition service + +The content acquisition service (CAS) module controls the acquisition and aggregation of content and metadata sources from content provider functions. The content and metadata sources include content sources, metadata sources, and content protection rights sources for IPTV services. This service module can optionally provide verification functionality for the contents, such as the validity of content source, normalization of source data, conformance between source content and source metadata, conformance between source content and existing content, etc. It provides the capability of content buffering before the final deployment as well as relevant metadata updates. + +For detailed information on the content provisioning interface, please refer to [ITU-T H.752]. For detailed information on metadata of IPTV services, please refer to [ITU-T H.750]. + +#### 10.1.1.2 Content processing control service + +The content processing control service (CPCS) module controls the processing tasks of content adaptation such as transcoding, packaging, editing and other capabilities, in compliance with commercial agreements with content providers. This service module manages content pre-processing service modules within the content management service or content delivery service. + +#### 10.1.1.3 Content pre-processing service + +The content pre-processing service (CPPS) module performs media content processing under the control of content processing control service modules and generates the processed content and content-related metadata. This service module provides all or some of the following capabilities: + +- Content transcoding: Content transcoding performs the encoding and decoding to media content to achieve bandwidth efficiency and adaptive quality of service (QoS), such as conversions in compression format, aspect ratios, resolution, bit rate, frame rate, etc. +- Content packaging: Content packaging performs the selection and combination of multiple items of content into a specific content to achieve the provision of IPTV service on multiple terminal devices or for user preferences, such as packaging a content for diverse transport protocols (e.g., RTSP/HTTP/DASH), packaging a content with different subtitles/audio tracks, etc. + +- Content editing: Content editing provides the basic capabilities of media editing for enhanced audio-visual perception, such as slicing, captioning, clipping, colour rendering, audio synthesis, advertising-insertion, logo-insertion, keyframe extraction, etc. + +#### **10.1.1.4 Content protection service** + +The content protection service (CPS) module controls the protection of the content in compliance with commercial agreements with content providers and generates the protected content and security-related metadata. It provides keys, performs content encryption and manages the keys for content encryption and decryption. It also provides watermark-embedding functionality for content tracing. + +For detailed information on rights-related metadata, please refer to [ITU-T H.751]. + +#### **10.1.1.5 Metadata post-processing service** + +The metadata post-processing service (MPPS) module controls the aggregation of content-related metadata, before delivering to content distribution management service modules. This service module provides all or some of the following capabilities: + +- Metadata supplement: Metadata supplement complements the missing information in the original metadata (derived from CAS modules, see clause 10.1.1.1), such as the obvious information of title, genre, synopsis or cast. +- Metadata consolidation: Metadata consolidation performs metadata replacement, correlation or consolidation between the original metadata (derived from CAS modules, see clause 10.1.1.1) and the processed metadata (derived from CPCS or CPS modules). + +#### **10.1.1.6 UI template management service** + +The UI template management service (UITMS) module controls the acquisition, configuration and deployment of UI templates. It acquires UI templates from service providers by means of API transmission or local upload. It provides the capability of information configuration concerning the UI template, such as service provider, version, matchable user type, etc. It also controls the deployment of UI templates into user interface modules and data backup into data service modules. + +#### **10.1.1.7 Content distribution management service** + +The content distribution management service (CDMS) module controls the distribution and deployment of the contents. It controls the deployment of content and metadata into data service modules, in order to form the completed content repository for IPTV service. It also controls the distribution of appropriate content and metadata to service navigation service modules, service control service modules and content delivery service modules for content preparation, through pre-defined distribution policies. + +The CDMS module provides configuration capability for content distribution policies. It is recommended to distribute content and metadata to content delivery service modules, service control service modules and service navigation service modules in order, so that the content presented on UI are available for end users. In order to ensure the validity and consistency of metadata among different service modules, this service module has the ability of handling exceptional cases in content distribution procedure, such as applying a retry or rollback mechanism. Further information for metadata manipulation is listed in Annex A. + +### **10.1.2 Advanced services** + +#### **10.1.2.1 Content pre-processing service** + +Besides the descriptions in clause 10.1.1.3, this service module further provides the following capability: + +- Content editing: Content editing provides the advanced capabilities of media editing for augmented or personalized user experience, such as video frames insertion, video super-resolution, scene-based media editing, personalized trailer editing, etc., optionally by using machine learning technology. + +#### 10.1.2.2 Metadata post-processing service + +Besides the descriptions in clause 10.1.1.5, this service module further provides all or some of the following capabilities: + +- Label metadata optimization: Label metadata optimization generates more fine-grained labels of the contents for presentation in elaborate categories or personalized user interface, such as custom genre labels. +- Metadata backwards supplement: Metadata backwards supplement collects complementary information of content-related metadata from other service modules, such as content popularity information through audience measurement. + +## 10.2 Service navigation service + +The service navigation service is comprised of service modules with distinct features or functionality on service navigation. Figure 4 provides the modular structure of the service navigation service. The rectangular area in white represents service navigation service capabilities in basic level, and the rectangular area in grey represents service navigation service capabilities in advanced level. As shown in this figure, service modules across the white area and grey area have service navigation service capability in basic level and advanced level. + +![Figure 4 – Modular structure of service navigation service. The diagram shows a hierarchy of service modules. The top-level box is 'Service navigation service'. Inside it, there are two columns of boxes. The left column contains: 'Service/application metadata service', 'VoD content metadata service', 'Picture metadata service', 'Content searching service', 'Content rating service', and 'Personalized Recommendation service'. The right column contains: 'Broadcast content metadata service', 'Cast metadata service', 'Navigation category metadata service', and 'User events collecting and sharing service'. The bottom two boxes, 'Content rating service' and 'Personalized Recommendation service', are highlighted with a grey background. A legend at the bottom shows a white box for 'Basic services' and a grey box for 'Advanced services'. The text 'H.705.1(23)' is in the bottom right corner.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +Figure 4 – Modular structure of service navigation service. The diagram shows a hierarchy of service modules. The top-level box is 'Service navigation service'. Inside it, there are two columns of boxes. The left column contains: 'Service/application metadata service', 'VoD content metadata service', 'Picture metadata service', 'Content searching service', 'Content rating service', and 'Personalized Recommendation service'. The right column contains: 'Broadcast content metadata service', 'Cast metadata service', 'Navigation category metadata service', and 'User events collecting and sharing service'. The bottom two boxes, 'Content rating service' and 'Personalized Recommendation service', are highlighted with a grey background. A legend at the bottom shows a white box for 'Basic services' and a grey box for 'Advanced services'. The text 'H.705.1(23)' is in the bottom right corner. + +**Figure 4 – Modular structure of service navigation service** + +The following clauses provide descriptive texts for fine-grained service modules of the service navigation service. + +### **10.2.1 Basic services** + +#### **10.2.1.1 Service/application metadata service** + +The service/application metadata service (SAMS) module provides service or application related metadata required by service discovery and selection. Service/application metadata contain the descriptive information on service providers, content providers, service packages, software packages, etc. + +For detailed information on service discovery and selection, please refer to [ITU-T H.770]. + +#### **10.2.1.2 Broadcast content metadata service** + +The broadcast content metadata service (BCMS) module provides content metadata required by service navigation of IPTV broadcast services. It supports various forms of broadcasting services including linear TV (with trick mode), virtual reality (VR) broadcast, live advertising, on-line learning, etc. Broadcast content metadata contain the descriptive information on linear TV channels, TV schedules, live videos, broadcast streams, etc. In response to user interface modules for content presentation, this service module is capable of providing broadcast content metadata of a particular channel/live video or a particular group of channels/live videos matching the filtering rules (e.g., linear TV channels in high-definition). + +#### **10.2.1.3 VoD content metadata service** + +The VoD content metadata service (VCMS) module provides content metadata required by service navigation of IPTV on-demand services. It supports various forms of on-demand services including TV programs, personal recorded videos, on-demand advertising, music videos, etc. Video content metadata contain the descriptive information on movies, TV series, videos, video streams, etc. In response to user interface modules for content presentation, this service module is capable of providing video content metadata of a particular video on demand (VoD) or a particular group of VoDs matching the filtering rules (e.g., movies in historical genre). + +#### **10.2.1.4 Cast metadata service** + +The cast metadata service (CMS) module provides metadata of cast members relevant to IPTV contents. Cast metadata contain the descriptive information on cast roles, personal profiles, etc. In response to user interface modules, this service module is capable of providing cast metadata of a particular individual or a particular group of cast members matching the filtering rules (e.g., the whole cast of a certain TV series). + +#### **10.2.1.5 Picture metadata service** + +The picture metadata service (PMS) module provides picture-related metadata required by the navigation of IPTV static pictures. It supports various types of pictures including thumbnail, poster, photos, icons, logos, background images, etc. Besides the basic information of picture files, picture metadata also contain the descriptive information on mapping relations between pictures and other metadata objects. In response to user interface modules for picture presentation, this service module is capable of providing picture content metadata of a particular picture or a particular group of pictures matching the filtering rules (e.g., movie poster in a given resolution). + +#### **10.2.1.6 Navigation category metadata service** + +The navigation category metadata service (NCMS) module provides navigation category metadata on the orchestration of IPTV services/contents. Besides the information of category items, navigation category metadata also contain the descriptive information on dependency relations between categories or between categories and contents. In response to user interface modules, this service module is capable of providing category metadata of a particular category item or a particular group of categories matching the filtering rules (e.g., all the categories in the second-level). + +For detailed information on service and content metadata involved by the aforementioned metadata services, please refer to [ITU-T H.750] and [ITU-T H.753]. + +#### **10.2.1.7 Content searching service** + +The content searching service (CSS) module responds to end user's content searching requests through user interface and provides content metadata that match the search keywords and search criteria. It constructs and manages the index database based on the IPTV content repository, executes the retrieval algorithms and responses the structured data of a set of sorted contents to user interface modules. This service module is capable of providing searching functionalities on channels, videos, casts, pictures, categories, service/content packages and other types of contents. It also supports multiple searching modes including full search, conditional search, accurate search, fuzzy search, etc. + +#### **10.2.1.8 User events collecting and sharing service** + +The user events collecting and sharing service (UECSS) module controls the collection and data read-write of user behavioural information. It performs data collection of the user's behaviour related to service navigation, content selection, content searching, content rating events, through a certain mechanism. It provides data sharing capability to other service modules or external systems, such as multiple purposes of reporting, administration and maintenance, recommendation services, etc. It also controls the storage of user events data into data service modules. + +### **10.2.2 Advanced services** + +#### **10.2.2.1 Content searching service** + +Besides the descriptions in clause 10.2.1.7, this service module further supports intelligent searching modes including semantic search, personalized search, etc. + +#### **10.2.2.2 Content rating service** + +The content rating service (CRS) module responds to end user's rating requests through user interface and provides the dynamic metadata on content rating. It collects subjective assessment information concerning IPTV contents from the end user and generates the structured metadata of content rating. It also performs data management with user's permission and controls data synchronization and data caching. For the numerical content-rating data, this service module is capable of performing calculation in real-time based on a given algorithm and synchronously conveying to metadata post-processing service (MPPS) modules so that the updated metadata can be presented on user interface in a timely manner. Content rating operations may include but are not limited to likes, shares, grading or comments. + +#### **10.2.2.3 Content popularity ranking service** + +The content popularity ranking service (CPRS) module provides the dynamic metadata on content ranking. It aggregates user behavioural data from user events collecting and sharing service (UECSS) (see clause 10.2.1.8) or AMS (see clause 10.4.10) modules and real-timely generates the structured metadata of ranked contents. It also performs data management and controls data read-write of content ranking information. The factors considered by content ranking may include viewing records, rating records, content release time, configuration weight, etc. Content popularity ranking service may be applied in multiple scenarios of user interface, such as recommendation category or content searching results. + +#### **10.2.2.4 Personalized recommendation service** + +The personalized recommendation service (PRS) module provides the personalized recommendation of IPTV services/contents for the end user with his permission. It makes correlation analysis of service/content metadata and user behavioural data and generates the dynamic metadata of recommended services/contents. It also performs data management and + +controls data read-write of recommendation information. In order to meet the diversified needs of service orchestration, this service module supports configuration management of the recommendation service on the visual interface as well as the implementations of intelligent recommendation algorithms. The factors considered by personalized recommendation may include content labels, content rating, content ranking, user preference, user's favourites, viewing history, terminal attributes, etc. Personalized recommendation service may be applied in multiple scenarios, such as content recommendation, service/content package recommendation, multi-device interactive service or personalized user interface. + +For detailed information on personalized IPTV service, please refer to [ITU-T H.741.5]. + +## 10.3 Service control service + +Service control service is comprised of service modules with distinct features or functionality on service control. Figure 5 provides the modular structure of service control service. As shown in this figure, service control service capabilities provided by the fine-grained service modules are in basic level. + +![Figure 5: Modular structure of service control service. The diagram shows a large box labeled 'Service control service' containing ten smaller boxes arranged in a 5x2 grid. The modules are: User profile management service, Application profile management service, User authentication service, Service/content package management service, Content authorization service, Content protection authorization service, Service/content subscription service, Charging and accounting service, Session management service, and User events collecting and sharing service. The reference H.705.1(23) is noted below the diagram.](a3472689858b068ef469213682965325_img.jpg) + +| Service control service | | +|--------------------------------------|--------------------------------------------| +| User profile management service | Application profile management service | +| User authentication service | Service/content package management service | +| Content authorization service | Content protection authorization service | +| Service/content subscription service | Charging and accounting service | +| Session management service | User events collecting and sharing service | + +H.705.1(23) + +Figure 5: Modular structure of service control service. The diagram shows a large box labeled 'Service control service' containing ten smaller boxes arranged in a 5x2 grid. The modules are: User profile management service, Application profile management service, User authentication service, Service/content package management service, Content authorization service, Content protection authorization service, Service/content subscription service, Charging and accounting service, Session management service, and User events collecting and sharing service. The reference H.705.1(23) is noted below the diagram. + +Figure 5 – Modular structure of service control service + +The following clauses provide descriptive texts for fine-grained service modules of service control service. + +### 10.3.1 User profile management service + +The user profile management service (UPMS) module controls the acquisition, management and data read-write of user profile information. It acquires user information from the end user or external system such as a customer relationship management (CRM) system. It performs data aggregation, classification, correlation and other management functionalities of the user profile. It also controls data storage into data service modules as well as data sharing under permission management. + +This service module manages, but is not limited to, the following user profile information: + +- Service registration information, such as subscribed service package, service entry point, service provider, etc. +- Content subscription information, such as subscribed content package, valid period, etc. +- User private information, such as customer name, contact details, location, etc. +- Network information, such as network access mode, routing configuration, user IP address, etc. + +- Terminal device/multiple terminal devices information, such as device identifier, terminal type, terminal capabilities, etc. +- User account information, such as user account, user type, user status, etc. +- Additional information: bonus points, coupon, etc. + +### 10.3.2 Application profile management service + +The application profile management service (APMS) module controls the acquisition, management and data read-write of application profile information. It acquires application information from the end user and performs data management functionalities. It controls data storage into data service modules as well as data sharing under permission management. + +This service module manages, but is not limited to, the following application profile information: + +- Application settings, such as language, parental control level, etc. +- Lists of favourite contents +- Lists of content bookmarks +- Lists of personal video recorder (PVR) contents + +### 10.3.3 Service/content package management service + +The service/content package management service (SPMS) module performs service/content packaging management and controls data read-write of service/content package information. It provides the capability of generating various service packages and content packages that end users can directly consume, which may be on premise of the packaging principle designated by content providers. It performs the life cycle management of package data. It also controls data storage into data service modules and data access from the end user or other service modules. + +This service module provides the following packaging capabilities: + +- Packaging method: It supports the following packaging methods. + - One service/content package for one single service/content, such as live broadcast of a hockey match is packaged as one content package. + - One service/content package for a combination of service/content, such as linear TV service and VoD service provided by a service provider is bundled as one combined service package of this service provider. + - Multiple service/content packages for one package of services/contents, such as VoD package "new sitcoms" is re-packaged as one content package of 7 days' trial, and the other content package of 3 months' validity. +- Pricing policy: Pricing policy can be configurable, including information on price, validity period, charge model, etc. It supports all or some of the following charge models: + - Charge model: It includes free-of-charge model and for-charge model. For-charge model may further be categorized into pay-per-use, pay-per-time-period model. + - Pay-per-use model: It provides configuration capability of charge unit, such as usage times, network flow, elapsed time, etc. It also supports multiple charging modes, such as regular mode, capping mode, limited mode, etc. + - Pay-per-time-period model: It provides configuration capability of time period, such as daily, monthly, quarterly, half yearly, annual, etc. + - Discount policy: Discount policy can be configurable and applied to a for-charge model, such as promotion by time period, by user type, etc. + +### **10.3.4 User authentication service** + +The user authentication service (UAS) module performs the authentication procedure of access to IPTV services by responding to end user's requests. It performs service access control by authenticating the terminal device and the user, through pre-defined business logic. Only in the case of successful authentication, this service module will provide the necessary information of service initiation. + +This service module provides the following capabilities: + +- The factors considered by authentication may include terminal legality, user identity, user status, purchased service package, network condition, etc. +- Service initiation information provided by this service module may include service entry point (e.g., a form of URL of a specific UI template), user license (e.g., a form of user token), resource information (e.g., network routing information, NTP resource information), audience measurement method (e.g., measurement parameters, reporting period and URL). +- In the case of service protection, this service module performs a mutual authentication procedure and then establishes the secure communication channel for IPTV service. + +### **10.3.5 Content authorization service** + +The content authorization service (CAS) module performs authorization to access IPTV contents by responding to user's requests. It grants the permission for the user to consume the specific content, through pre-defined business logic. Only in the case of successful authorization, the appropriate network and system resources will be subsequently initiated and established. + +This service module provides the following capabilities: + +- The factors considered by authorization may include user license' legality, purchased content package, term of validity, etc. If the requested content is included in more than one purchased content package, the end user will be granted access permission as long as any one of the packages meets the authorization requirements. +- For IPTV service over multiple terminal devices or IPTV service on multiple household terminal devices, the authorization procedure depends on content sharing policy and the corresponding business logic. + +### **10.3.6 Content protection authorization service** + +The content protection authorization service (CPAS) module performs authorization to access IPTV contents with digital rights protection by responding to user's requests. It manages the rights and keys and issues digital rights license containing usage conditions and decryption keys for the authorized user. + +### **10.3.7 Service/content subscription service** + +The service/content subscription service (SCSS) module performs subscriptions or unsubscribe operations of the service/content package by responding to user's requests. It provides the detailed information of available service/content packages containing a given service/content and handles the whole procedure of subscriptions/unsubscribe, purchases/refund and transactions. It supports several types of prepay methods, such as balance payment, points payment, third-party payment, etc. In addition for the case of other payment methods such as post pay or advice of charge, it supports interaction with a charging and accounting service to fulfil the service/content subscription or unsubscribe operation. + +### 10.3.8 Charging and accounting service + +The charging and accounting service (CAAS) module provides charging and accounting capability for service consumption and content consumption. It generates charging information based on the subscription information, pricing policy of the consumed service/content and usage records collected from other service modules. It further generates accounting data by consolidating charging information and applying discount policy. + +### 10.3.9 Session management service + +The session management service (SMS) module manages the interaction connections between the end user and IPTV service platform during the usage of IPTV service. It performs the life cycle management of user session data, including the creation, update and deletion of session data. It controls the buffer of user sessions in a scalable and robust manner. It also provides data query capability of user presence status (e.g., online, offline). + +### 10.3.10 User events collecting and sharing service + +The user events collecting and sharing service (UECSS) module controls the collection and data read-write of user behavioural information. It performs data collection of the user's behaviour related to authentication, authorization, subscription, purchase, payment events, through a certain mechanism (e.g., message mechanism). It provides data sharing capability to other service modules, external systems or the end user under permission management, such as multiple purposes of reporting, administration and maintenance, partner settlements, recommendation services, etc. It also controls the storage of user events data into data service modules. + +## 10.4 Content delivery service + +The content delivery service is comprised of service modules with distinct features or functionality on content delivery. Figure 6 provides the modular structure of the content delivery service. As shown in this figure, content delivery service capabilities provided the fine-grained service modules are in basic level. In practical deployment, any one or a combination of the following service modules can be integrated and built as a service node or cluster of a content delivery service. In addition it supports implementation in a hierarchical architecture and distributed environment. For detailed information on the deployment model and implementation mechanisms, please refer to [ITU-T Y.2019] and [ITU-T H.644.3]. + +![Modular structure of content delivery service diagram](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +The diagram illustrates the modular structure of the content delivery service. It is titled "Content delivery service" and is enclosed in a rectangular box. Inside, there are 11 service modules arranged in a grid. The first five rows each contain two modules side-by-side. The modules are: Content distribution service, User request scheduling service, VoD content processing service, Broadcast content processing service, Access permission control service, Audience measurement service, Unicast content delivery service, Multicast content delivery service, Black-to-source service, Content delivery configuration service, and Content consumption statistic service. The last module is positioned at the bottom left, spanning the width of the first column. + +| Content delivery service | | +|---------------------------------------|----------------------------------------| +| Content distribution service | User request scheduling service | +| VoD content processing service | Broadcast content processing service | +| Access permission control service | Audience measurement service | +| Unicast content delivery service | Multicast content delivery service | +| Black-to-source service | Content delivery configuration service | +| Content consumption statistic service | | + +Modular structure of content delivery service diagram + +H.705.1(23) + +Figure 6 – Modular structure of content delivery service + +The following clauses provide descriptive texts for fine-grained service modules of the content delivery service. + +### **10.4.1 Content distribution service** + +The content distribution service (CDS) module handles content and related metadata from the content management service and controls the distribution and deployment of contents among multiple instances of content delivery. It performs content dispatching or content aging functionality based on a given policy. It also controls the storage of content/segment duplicates and maintains distribution information for the contents within the content delivery service. + +### **10.4.2 VoD content processing service** + +The VoD content processing service (VCPS) module performs media processing for on-demand contents based on a given policy and generates the processed content and related metadata for the needs of network transmission and QoS. This service module provides the processing capabilities of content transcoding, packaging, slicing, indexing, keyframe extraction, encryption, etc. + +### **10.4.3 Broadcast content processing service** + +The broadcast content processing service (BCPS) module performs content recording and media processing for live contents based on a given policy and generates the processed content and related metadata for the needs of network transmission and QoS. This service module provides the processing capabilities of content recording, transcoding, packaging, slicing, indexing, keyframe extraction, encryption, etc. + +### **10.4.4 User request scheduling service** + +The user request scheduling service (URSS) module responds to user's requests for content delivery and redirects it to the appropriate service node. It is responsible for locating the appropriate instance of content delivery based on a given policy. This service module supports multiple scheduling solutions based on user's location, content routing, load balancing, etc. It also supports mechanisms to gather real time information from all the service nodes or instances within its management scope, including service capability, resource utilization, content distribution, etc. For hierarchical deployment architecture, the top-level scheduling node acts as the main entry for the content delivery service. + +### **10.4.5 Access permission control service** + +The access permission control service (APCS) module performs permission control to access service resources of content delivery based on a given policy. It supports different authentication mechanisms against unauthorized using of content delivery resources, including single-point authentication, multi-point authentication, open-loop encryption/decryption, closed-loop encryption/decryption, etc. For detailed information on authentication mechanisms, please refer to [ITU-T H.644.3]. + +### **10.4.6 Unicast content delivery service** + +The unicast content delivery service (UCDS) module responds to the authorized requests and delivers content streams or content downloads to the end user in unicast delivery mode. It manages the content delivery session with the end user, reacts to user interaction and provides the delivery service with guaranteed QoS. When the requested content is unavailable in the local data service module, this service module supports the mode of delivering while downloading. Transmission protocols and coding schemes to be supported by this service module can be found in [ITU-T H.721], [ITU-T H.644.3]. This service module supports mechanisms to report its real-time running status, including health status, number of connections, traffic load, etc. + +### **10.4.7 Multicast content delivery service** + +The multicast content delivery service (MCDS) module responds to the authorized requests and delivers content streams to the end user in multicast delivery mode. It manages the content delivery session with the end user, reacts to user interaction and provides the delivery service with guaranteed QoS. Transmission protocols and coding schemes to be supported by this service module can be found in [ITU-T H.721], [ITU-T H.644.3]. This service module supports mechanisms to report its real-time running status, including health status, number of connections, traffic load, etc. + +### **10.4.8 Back-to-source service** + +The back-to-source service (BTSS) module is responsible for fetching the content when the requested content is not hit in the selected service instance at the request of the end user. It redirects to the content source based on a given policy of back-to-source service [ITU-T H.644.5] and instantly downloads and caches the content in local data service module. This service module supports mechanisms to report its real-time running status, including health status, number of connections, traffic load, etc. + +### **10.4.9 Content delivery configuration service** + +The content delivery configuration service (CDCS) module performs the configuration management and the distribution of configurations and policies, in order to achieve the running in a highly efficient and flexible manner. This service module provides all or some of the following configuration capabilities: + +- Service node management: It manages all the node devices of the content delivery service and configures the topology information among service nodes, such as cascade relationship, cluster relationship, etc. +- Content processing policy: It configures the content processing tasks for service nodes. It supports the processing control from content management service or the configuration in this service module. +- Content distribution policy: It configures the mechanisms of content dispatching and content aging. It supports the configuration of push mode (i.e., distributing contents from upstream nodes to downstream nodes), pull mode (i.e., fetching contents from downstream nodes to upstream nodes, usually depending on the popularity), etc. +- Content caching policy: It configures the mechanisms of content caching. It supports the configuration of caching policies based on criteria of content type, storage space, content popularity, etc. +- Access permission control: It configures the authentication mechanisms and manages the verification keys. +- User scheduling policy: It configures the scheduling mechanisms for user's requests. It supports the configuration of scheduling policies based on one or more criteria of service type, content delivery provider, end user's location, content distribution, resource utilization, service capability of nodes, etc. +- Back-to-source policy: It configures the routing mechanisms for back-to-source requests. +- QoS policy: It configures the quality control mechanisms, such as QoS level, bandwidth control algorithm, etc. + +### **10.4.10 Audience measurement service** + +The audience measurement service (AMS) module controls the collection and data read-write of user behavioural information. It collects user viewership data including operation history of the audience. It provides data sharing capability to other service modules or external systems under + +permission management, such as multiple purposes of reporting, recommendation services, etc. It also controls the storage of user events data into data service modules. + +### **10.4.11 Content consumption statistic service** + +The content consumption statistic service (CCSS) module provides statistical data of access popularity and network flow on a content basis. It collects the user events data for a certain content from all the instances of content delivery and generates the statistical data on content consumption based on a given algorithm. It provides data sharing capability to other service modules or external systems, such as multiple purposes of content caching or aging, traffic billing, partner settlements, reporting, etc. + +# **11 Functional description of data service** + +The data service module provides data storage and data reading/writing service for the IPTV service platform. According to different contents, the data of the IPTV service platform can be divided into metadata, media files, web documents, user data, operational data (e.g., statistical data, log data) and so on. This module is responsible for storing data in a database, cache system, file system or other storage type or hybrid schemes, depending on the characteristics of data change and reading/writing frequency. It is also responsible for encapsulating APIs for data reading/writing and opening to service modules and O&M management modules. It supports mechanisms to guarantee data consistency and access security, while providing data service with high reliability and scalability. + +# **12 Functional description of O&M management** + +## **12.1 Upgrade management** + +The upgrade management module performs version management of application software packages and controls the upgrading/downgrading tasks for the IPTV service platform and IPTV terminal devices. This module provides the following functionalities: + +- Version management: It controls the validation, deployment and release of all the application software packages. It also manages the feature information of released packages, such as version name, version number, problem-solving description, download address, etc. +- Policy configuration: It configures the upgrading/downgrading policies including the settings on initial version/target version, rollback logic, type of upgrade and so on. For IPTV terminal devices, it supports policy configuration based on one or more criteria of terminal type, user's location, hardware version, OS version, device ID, etc. +- Upgrading/downgrading management: It controls and manages the functional modules of IPTV service platform or a batch of terminal devices to upgrade or downgrade, according to the defined policies. The supported types of upgrade include hot update (i.e., dynamic update on partial codes or configuration, without rebooting system), grey scale upgrade (i.e., incremental or gradual upgrade process, usually referring to function or process), silent upgrade (i.e., automatic upgrade process, without user perception and application available), and mandatory upgrade (i.e., automatic upgrade process, application disabled until it succeeds), etc. +- Data statistic and visualization: It provides data statistic functionality as well as a visualized interface for statistical results on upgrading/downgrading tasks. + +## 12.2 Monitoring management + +The monitoring management module performs performance and QoS/QoE monitoring of IPTV functional entities and provides alarm functionality based on the configuration of alarm events. This module provides the following functionalities: + +- Performance monitoring: It collects performance indicators in real-time from the functional entities in the IPTV service platform, including the server hosts, application servers and storage systems. The performance data collected by this module includes the utilization of hardware resources (e.g., CPU load, RAM/ROM usage) and application resources (e.g., number of processes, connections). +- QoS/QoE monitoring: It configures the mechanism of QoS/QoE reporting and collects data from the functional entities where the quality probes are deployed. It supports collection of data concerning quality of content, quality of interaction and quality of user experience. +- Alarm configuration: It configures various types of alarm events by setting the alarm threshold, alarm level, alerting methods and other parameters. It supports giving alarms or early warnings automatically and in a timely manner when the monitored indicators reach the preset conditions. +- Statistical analysis and visualization: It provides real-time or quasi real-time statistical analysis functionality for the aggregated monitoring data. It supports presentation of the statistical results on different dimensions and alarm messages in the forms of tables, graphs, maps, etc., on a visualized interface. The statistical analysis functionality of this module will contribute to fault prediction and fault diagnosis of IPTV end-to-end systems. + +## 12.3 Logging management + +The logging management module controls log recording and collects log data from IPTV functional entities. This module provides the following functionalities: + +- Log collection: It configures the mechanism of log reporting and collects log data concerning application log, system log and operation log. +- Log data management: It performs data cleaning, structured processing and classified storage to the log data. +- Data analysis and visualization: It provides log retrieval and log analysis functionality as well as visualized interface for retrieval and analysis results. The data analysis functionality of this module will contribute to fault diagnosis of IPTV services. +- Logging output: As the output module for log files, it supports generation of log reports as required and export to external systems. + +## 12.4 Security management + +Security management module performs security related configuration and management for IPTV services, such as key management, system disaster recovery solution, and emergency plan. It also supports mechanisms to suspend or recover the service offering of IPTV in order to meet regulatory requirements. + +# 13 Reference points + +Figure 7 identifies the reference points in the IPTV service platform. In this figure, the rounded rectangular blocks of the content management service, service navigation service, service control service and content delivery service represent the combinations of all the fine-grained service modules defined in clause 10, rather than the specific modules shown in this figure. The black dash-dot lines represent direct connection interfaces between functional modules, and the blue dash lines + +represent indirect connection interfaces. Line crossings do not imply connections, unless explicitly stated. + +![Figure 7-a: Reference points A, M. A diagram showing a stack of service layers: User interface, Service access control (with Service capability discovery), Content management service, Service navigation service and Service control service, Content delivery service, and Data service. Reference points Mu, MA, Me, Mn, Ms, Md, and Ma are on the right. Reference points Ad, An, Ac, and As are on the left. A vertical bar on the right is labeled 'Operation and maintenance management'. The diagram is labeled 'Reference points A, M' and 'H.705.1(23)'.](2bacc162a73d75c43a7f90715832bd13_img.jpg) + +Figure 7-a: Reference points A, M. A diagram showing a stack of service layers: User interface, Service access control (with Service capability discovery), Content management service, Service navigation service and Service control service, Content delivery service, and Data service. Reference points Mu, MA, Me, Mn, Ms, Md, and Ma are on the right. Reference points Ad, An, Ac, and As are on the left. A vertical bar on the right is labeled 'Operation and maintenance management'. The diagram is labeled 'Reference points A, M' and 'H.705.1(23)'. + +Figure 7-a – Reference points A, M + +![Figure 7-b: Reference points A, U. A diagram showing a stack of service layers: User interface, Service access control (with Service access), Content management service, Service navigation service and Service control service, Content delivery service, and Data service. Reference points Un, UA, NA, DA, CA, SA, and Ud are on the left. Reference points Us and Ua are on the right. A vertical bar on the right is labeled 'Operation and maintenance management'. The diagram is labeled 'Reference points A, U' and 'H.705.1(23)'.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Figure 7-b: Reference points A, U. A diagram showing a stack of service layers: User interface, Service access control (with Service access), Content management service, Service navigation service and Service control service, Content delivery service, and Data service. Reference points Un, UA, NA, DA, CA, SA, and Ud are on the left. Reference points Us and Ua are on the right. A vertical bar on the right is labeled 'Operation and maintenance management'. The diagram is labeled 'Reference points A, U' and 'H.705.1(23)'. + +Figure 7-b – Reference points A, U + +![Figure 7-c: Reference points C, S. A diagram showing a stack of service layers: User interface, Service access control (with Service access), Content management service (with UITMS, MPPS, CDMS, CPCS), Service navigation service and Service control service (with SMS, CAS, UECSS, CAAS, SPMS), Content delivery service (with CCSS, CDS, CDCS, AMS, BTSS, APCS), and Data service. Reference points Cu, Ca, Cn, Cd1, Cs, Cd2, and Sa are on the left. Reference points Sd is on the right. A vertical bar on the right is labeled 'Operation and maintenance management'. The diagram is labeled 'Reference points C, S' and 'H.705.1(23)'.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +Figure 7-c: Reference points C, S. A diagram showing a stack of service layers: User interface, Service access control (with Service access), Content management service (with UITMS, MPPS, CDMS, CPCS), Service navigation service and Service control service (with SMS, CAS, UECSS, CAAS, SPMS), Content delivery service (with CCSS, CDS, CDCS, AMS, BTSS, APCS), and Data service. Reference points Cu, Ca, Cn, Cd1, Cs, Cd2, and Sa are on the left. Reference points Sd is on the right. A vertical bar on the right is labeled 'Operation and maintenance management'. The diagram is labeled 'Reference points C, S' and 'H.705.1(23)'. + +Figure 7-c – Reference points C, S + +![Figure 7-d: Reference points N, D. A diagram showing a stack of service layers: User interface, Service access control (with Service access), Content management service (with UITMS, MPPS, CDMS, CPCS), Service navigation service (with CPRS, CRS, PRS) and Service control service (with SMS, CAS, UECSS, CAAS, SPMS), Content delivery service (with CCSS, CDS, CDCS, AMS, BTSS, APCS), and Data service. Reference points Na, Nd, Nc, Ns1, Ns2, Ns3, Ds1, Ds2, Da, and Dc are on the left. A vertical bar on the right is labeled 'Operation and maintenance management'. The diagram is labeled 'Reference points N, D' and 'H.705.1(23)'.](55136bc716146672fc680fa05989f1d2_img.jpg) + +Figure 7-d: Reference points N, D. A diagram showing a stack of service layers: User interface, Service access control (with Service access), Content management service (with UITMS, MPPS, CDMS, CPCS), Service navigation service (with CPRS, CRS, PRS) and Service control service (with SMS, CAS, UECSS, CAAS, SPMS), Content delivery service (with CCSS, CDS, CDCS, AMS, BTSS, APCS), and Data service. Reference points Na, Nd, Nc, Ns1, Ns2, Ns3, Ds1, Ds2, Da, and Dc are on the left. A vertical bar on the right is labeled 'Operation and maintenance management'. The diagram is labeled 'Reference points N, D' and 'H.705.1(23)'. + +Figure 7-d – Reference points N, D + +![Diagram of Service access control and Content management service with reference points Ci.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +The diagram shows two stacked service boxes. The top box is 'Service access control' containing 'Service access'. The bottom box is 'Content management service' containing several components: CPCS, CPPS, CAS, CPS, CDMS, and MPPS. Reference points are indicated by red labels and dashed blue lines: Ci1 (between CPCS and CAS), Ci2 (between CPCS and CPPS), Ci3 (between CAS and CPS), Ci4 (between CDMS and MPPS), Ci5 (between CPCS and CPPS), Ci6 (between CPS and MPPS), and Ci8 (between CDMS and MPPS). The text 'Reference points Ci H.705.1(23)' is at the bottom. + +Diagram of Service access control and Content management service with reference points Ci. + +**Figure 7-e – Reference points Ci** + +![Diagram of Service access control and Service navigation service with reference points Ni.](fa01531ea2c45beeb4036005da3037a4_img.jpg) + +The diagram shows two stacked service boxes. The top box is 'Service access control' containing 'Service access'. The bottom box is 'Service navigation service' containing SAMS, BCMS, VCMS, CMS, UECS, CSS, NCMS, CRS, CPRS, and PRS. Reference points are indicated by red labels and dashed blue lines: Ni1 (between SAMS and CMS), Ni2 (between BCMS and UECS), Ni3 (between VCMS and CSS), Ni4 (between CMS and UECS), Ni5 (between UECS and CSS), Ni6 (between NCMS and CPRS), Ni7 (between CRS and PRS), Ni8 (between NCMS and CPRS), Ni9 (between UECS and PRS), and Ni10 (between PRS and CSS). The text 'Reference points Ni H.705.1(23)' is at the bottom. + +Diagram of Service access control and Service navigation service with reference points Ni. + +**Figure 7-f – Reference points Ni** + +![Diagram of Service access control and Service control service with reference points Si.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +The diagram shows two stacked service boxes. The top box is 'Service access control' containing 'Service access'. The bottom box is 'Service control service' containing APMS, SMS, CAAS, CAS, SCSS, UAS, SPMS, UECS, UPMS, and CPAS. Reference points are indicated by red labels and dashed blue lines: Si1 (between APMS and SMS), Si2 (between APMS and CAS), Si3 (between CAS and SCSS), Si4 (between CAS and UECS), Si5 (between SMS and SCSS), Si6 (between SMS and CAAS), Si7 (between UECS and UPMS), Si8 (between SMS and CAAS), Si9 (between UAS and UPMS), Si10 (between SPMS and UECS), Si11 (between SPMS and CAS), and Si12 (between SCSS and UECS). The text 'Reference points Si H.705.1(23)' is at the bottom. + +Diagram of Service access control and Service control service with reference points Si. + +**Figure 7-g – Reference points Si** + +![Figure 7-h: Reference points Di (part I). This diagram shows a top box labeled 'Service access control' containing a smaller box 'Service access'. Below it is a larger box 'Content delivery service'. Inside this box, several functional modules are connected by dashed lines representing indirect connections. The modules are: VCPS, URRS, MCDS, CDS, UCDS, APCS, BCPS, BTSS, and CCSS. Red labels Di1 through Di11 mark the connection points: Di1 (VCPS to CDS), Di2 (VCPS to URRS), Di3 (CDS to UCDS), Di4 (URRS to UCDS), Di5 (CDS to BCPS), Di6 (UCDS to APCS), Di7 (URRS to APCS), Di8 (UCDS to BTSS), Di9 (MCDS to APCS), Di10 (BTSS to CCSS), and Di11 (APCS to CCSS).](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +H.705.1(23) + +Reference points Di (Part I) + +Figure 7-h: Reference points Di (part I). This diagram shows a top box labeled 'Service access control' containing a smaller box 'Service access'. Below it is a larger box 'Content delivery service'. Inside this box, several functional modules are connected by dashed lines representing indirect connections. The modules are: VCPS, URRS, MCDS, CDS, UCDS, APCS, BCPS, BTSS, and CCSS. Red labels Di1 through Di11 mark the connection points: Di1 (VCPS to CDS), Di2 (VCPS to URRS), Di3 (CDS to UCDS), Di4 (URRS to UCDS), Di5 (CDS to BCPS), Di6 (UCDS to APCS), Di7 (URRS to APCS), Di8 (UCDS to BTSS), Di9 (MCDS to APCS), Di10 (BTSS to CCSS), and Di11 (APCS to CCSS). + +**Figure 7-h – Reference points Di (part I)** + +![Figure 7-i: Reference points Di (part II). Similar to Figure 7-h, it shows 'Service access control' with 'Service access' at the top and 'Content delivery service' below. Modules include: CDS, VCPS, BCPS, UCDS, CDCS, URSS, APCS, AMS, BTSS, and MCDS. Red labels Di12 through Di22 mark connections: Di12 (CDS to CDCS), Di13 (VCPS to CDCS), Di14 (BCPS to CDCS), Di15 (UCDS to CDCS), Di16 (CDCS to URSS), Di17 (UCDS to APCS), Di18 (CDCS to AMS), Di19 (URSS to AMS), Di20 (APCS to AMS), Di21 (AMS to BTSS), and Di22 (AMS to MCDS).](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) + +H.705.1(23) + +Reference points Di (Part II) + +Figure 7-i: Reference points Di (part II). Similar to Figure 7-h, it shows 'Service access control' with 'Service access' at the top and 'Content delivery service' below. Modules include: CDS, VCPS, BCPS, UCDS, CDCS, URSS, APCS, AMS, BTSS, and MCDS. Red labels Di12 through Di22 mark connections: Di12 (CDS to CDCS), Di13 (VCPS to CDCS), Di14 (BCPS to CDCS), Di15 (UCDS to CDCS), Di16 (CDCS to URSS), Di17 (UCDS to APCS), Di18 (CDCS to AMS), Di19 (URSS to AMS), Di20 (APCS to AMS), Di21 (AMS to BTSS), and Di22 (AMS to MCDS). + +**Figure 7-i – Reference points Di (part II)** + +![](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +---- Indirect connection (Messages transferred by service access module) + +— · — Direct connection + +H.705.1(23) + +**Figure 7 – Reference points of IPTV service platform layered architecture** + +## 13.1 Reference points A + +The A reference points (see Figure 7-a) are used by service modules to request the service registration/deregistration, and capability statement and to convey its running data to the service access control (specific to service capability discovery) module. + +### 13.1.1 Reference points Ac + +The Ac reference point is between the service access control module (specific to service capability discovery) and the content management service module. + +### 13.1.2 Reference points An + +The An reference point is between the service access control module (specific to service capability discovery) and the service navigation service module. + +### 13.1.3 Reference points As + +The As reference point is between the service access control module (specific to service capability discovery) and the service control service module. + +### 13.1.4 Reference points Ad + +The Ad reference point is between the service access control module (specific to service capability discovery) and the control delivery service module. + +## 13.2 Reference points for implementing service invocation + +The reference points (see Figure 7-b) are used to exchange messages for service invocation, which are necessarily through the service access control (specific to service access) module. These reference points represent a general definition of direct connection interfaces between the service access module and the consumer or provider of service capability, instead of the specific definition of functional interfaces. For detailed information on functional interfaces, please refer to clauses 13.3-13.7 and clauses 13.9-13.12. + +### **13.2.1 Reference point UA** + +The UA reference point is between the user interface module and the service access control module (specific to service access). + +This reference point is used by the user interface to request or respond to service access for service invocation. + +### **13.2.2 Reference point CA** + +The CA reference point is between the content management service module and the service access control module (specific to service access). + +This reference point is used to request or respond to service invocation between content management service and service access. + +### **13.2.3 Reference point NA** + +The NA reference point is between the service navigation service module and the service access control module (specific to service access). + +This reference point is used to request or respond to service invocation between service navigation service and service access. + +### **13.2.4 Reference point SA** + +The SA reference point is between the service control service module and the service access control module (specific to service access). + +This reference point is used to request or respond to service invocation between service control service and service access. + +### **13.2.5 Reference point DA** + +The DA reference point is between the content delivery service module and the service access control module (specific to service access). + +This reference point is used to request or respond to service invocation between content delivery service and service access. + +## **13.3 Reference points U** + +The U reference points (see Figure 7-b) are used by the user interface module to invoke the capabilities of service modules. These reference points represent functional interfaces in an indirect connection case, which are actually implemented by the particular combinations of reference points defined in clause 9.2. + +### **13.3.1 Reference points Un** + +The Un reference point is between the user interface module and the service navigation service module. + +This reference point is used by the user interface to acquire metadata of IPTV services and contents for end user's service/content discovery and selection. It is also used to transfer user's rating data for IPTV contents. + +This functional interface is implemented by reference point UA and reference point NA (UA-NA Rp pair, for short). + +### **13.3.2 Reference points Us** + +The Us reference point is between the user interface module and the service control service module. + +This reference point is used by user interface to transfer user information, application information, service/content package information and exchange messages for service control functionalities. + +This functional interface is implemented by UA-SA Rp pair. + +### **13.3.3 Reference points Ud** + +The Ud reference point is between the user interface module and the content delivery service module. + +This reference point is used by user interface to exchange messages for trick mode play functionality. + +This functional interface is implemented by UA-DA Rp pair. + +### **13.4 Reference points C** + +The C reference points (see Figure 7-c) are used by the content management service module to exchange messages with other functional modules. Some of these reference points represent functional interfaces in indirect connection cases. + +### **13.4.1 Reference points Cn** + +The Cn reference point is between the content management service module (specific to CDMS, see clause 10.1.1.7) and the service navigation service module. + +This reference point is used to distribute content metadata and service/application metadata to service navigation service. + +This functional interface is implemented by CA-NA Rp pair. + +### **13.4.2 Reference points Cs** + +The Cs reference point is between the content management service module (specific to CDMS, see clause 10.1.1.7) and the service control service module. + +This reference point is used to distribute content metadata and service/application metadata to service control service. + +This functional interface is implemented by CA-SA Rp pair. + +### **13.4.3 Reference points Cd1** + +The Cd1 reference point is between the content management service module (specific to CDMS, see clause 10.1.1.7) and the content delivery service module (specific to CDS, see clause 10.4.1). + +This reference point is used by CDMS to distribute contents and content metadata to CDS. + +This functional interface is implemented by CA-DA Rp pair. + +### **13.4.4 Reference points Cd2** + +The Cd2 reference point is between the content management service module (specific to CPCS, see clause 10.1.1.2) and the content delivery service module (specific to CDCS, see clause 10.4.9). + +This reference point is used by CPCS to deliver content processing control policy to CDCS. + +This functional interface is implemented by CA-DA Rp pair. + +### **13.4.5 Reference points Cu** + +The Cu reference point is between content management service module (specific to UITMS, see clause 10.1.1.6) and user interface module. + +This reference point is used to exchange messages for controlling the deployment of UI templates. + +This functional interface is implemented by CA-UA Rp pair. + +### **13.4.6 Reference points Ca** + +The Ca reference point is between the content management service module and the data service module. + +This reference point is used by content management service to read and write data (i.e., contents and metadata) within its functional scope and authority. + +## **13.5 Reference points N** + +The N reference points (see Figure 7-d) are used by the service navigation service module to exchange messages with other functional modules. Some of these reference points represent functional interfaces in indirect connection case. + +### **13.5.1 Reference points Nd** + +The Nd reference point is between the service navigation service module (specific to CPRS, see clause 10.2.2.3) and the content delivery service module (specific to AMS, see clause 10.4.10). + +This reference point is used to exchange messages for collecting user viewership data. + +This functional interface is implemented by NA-DA Rp pair. + +### **13.5.2 Reference points Ns1** + +The Ns1 reference point is between the service navigation service module and the service control service module (specific to SMS, see clause 10.3.9). + +This reference point is used by service navigation service to acquire user information or to request update of session data. + +This functional interface is implemented by NA-SA Rp pair. + +### **13.5.3 Reference points Ns2** + +The Ns2 reference point is between the service navigation service module (specific to PRS, see clause 10.2.2.4) and the service control service module (specific to UECSS, see clause 10.3.10). + +This reference point is used by PRS to acquire user behavioural data (e.g., PVR preferences) from UECSS for generating personalized recommendations on contents. + +This functional interface is implemented by NA-SA Rp pair. + +### **13.5.4 Reference points Ns3** + +The Ns3 reference point is between the service navigation service module (specific to PRS, see clause 10.2.2.4) and the service control service module (specific to SPMS, see clause 10.3.3). + +This reference point is used by PRS to acquire service/content package information from SPMS for generating personalized recommendation on service/content packages. + +This functional interface is implemented by NA-SA Rp pair. + +### **13.5.5 Reference points Nc** + +The Nc reference point is between the service navigation service module (specific to CRS, see clause 10.2.2.2) and the content management service module (specific to MPPS, see clause 10.1.2.2). + +This reference point is used to exchange messages for content rating metadata aggregation. + +This functional interface is implemented by NA-CA Rp pair. + +### **13.5.6 Reference points Na** + +The Na reference point is between the service navigation service module and the data service module. + +This reference point is used by service navigation service to read and write data (i.e., content-related metadata) within its functional scope and authority. + +### **13.6 Reference points S** + +The S reference points (see Figure 7-c) are used by the service control service module to exchange messages with other functional modules. The reference point described in clause 13.6.1 represents the functional interface in an indirect connection case. + +### **13.6.1 Reference points Sd** + +The Sd reference point is between the service control service module (specific to CAS, see clause 10.3.5) and the content delivery service module (specific to CDS, see clause 10.4.1). + +This reference point is used by the content acquisition service (CAS) to acquire the initial information of an accessing content delivery resource (e.g., a content playback URL pointing to URSS) for the authorized requests. + +This functional interface is implemented by SA-DA Rp pair. + +### **13.6.2 Reference points Sa** + +The Sa reference point is between the service control service module and the data service module. + +This reference point is used by service control service to read and write data (i.e., user data and service-related metadata) within its functional scope and authority. + +### **13.7 Reference points D** + +The D reference points (see Figure 7-d) are used by the content delivery service module to exchange messages with other functional modules. Some of these reference points represent functional interfaces in indirect connection cases. + +### **13.7.1 Reference points Dc** + +The Dc reference point is between the content delivery service module (specific to BTSS, see clause 10.4.8) and the content management service module (specific to CDMS, see clause 10.1.1.7). + +This reference point is used by BTSS to fetch the content when CDMS is configured as the content source. + +This functional interface is implemented by DA-CA Rp pair. + +### **13.7.2 Reference points Ds1** + +The Ds1 reference point is between the content delivery service module (specific to CCSS, see clause 10.4.11) and the service control service module (specific to CAAS, see clause 10.3.8). + +This reference point is used to convey network flow data of content consumption for charging information generation. + +This functional interface is implemented by DA-SA Rp pair. + +### **13.7.3 Reference points Ds2** + +The Ds2 reference point is between the content delivery service module (specific to APCS, see clause 10.4.5) and the service control service module (specific to CAS, see clause 10.3.5). + +This reference point is used to exchange messages for permission control when CAS is configured to perform authentication. + +This functional interface is implemented by DA-SA Rp pair. + +### **13.7.4 Reference points Da** + +The Da reference point is between the content delivery service module and the data service module. + +This reference point is used by content delivery service to read and write data (i.e., contents and content-related metadata) within its functional scope and authority. + +### **13.8 Reference points M** + +The M reference points (see Figure 7-a) are used by the O&M management module to exchange messages for configuration and management with other functional modules. + +### **13.8.1 Reference points MA** + +The MA reference point is between the O&M management module and the service access control module. + +This reference point is used to exchange messages for upgrade management, performance monitoring, log collection and security management (e.g., disaster recovery solution). + +### **13.8.2 Reference points Mc** + +The Mc reference point is between the O&M management module and the content management service module. + +This reference point is used to exchange messages for upgrade management, performance monitoring, log collection and security management (e.g., key management). + +### **13.8.3 Reference points Ms** + +The Ms reference point is between the O&M management module and the service control service module. + +This reference point is used to exchange messages for upgrade management, performance monitoring, log collection and security management (e.g., emergency solution). + +### **13.8.4 Reference points Mn** + +The Mn reference point is between the O&M management module and the service navigation service module. + +This reference point is used to exchange messages for upgrade management, performance monitoring, log collection and security management. + +### **13.8.5 Reference points Md** + +The Md reference point is between the O&M management module and the content delivery service module. + +This reference point is used to exchange messages for upgrade management, performance and QoS/QoE monitoring, log collection and security management. + +### **13.8.6 Reference points Mu** + +The Mu reference point is between the O&M management module and the user interface module. + +This reference point is used to exchange messages for upgrade management, performance and QoS/QoE monitoring, log collection and security management (e.g., emergency solution). + +### **13.8.7 Reference points Ma** + +The Ma reference point is between the O&M management module and the data service module. + +This reference point is used by O&M management to read and write data (i.e., monitoring data, log data, software packages and metadata) within its functional scope and authority. + +### **13.9 Reference points Ci** + +The Ci reference points (see Figure 7-e) are used to exchange messages between fine-grained service modules inside the content management service module. These reference points represent functional interfaces in indirect connection cases and they are implemented by reference point CA. + +### **13.9.1 Reference points Ci1** + +The Ci1 reference point is between the CAS module (see clause 10.1.1.1) and the CPCS module (see clause 10.1.1.2). + +This reference point is used by CAS to query content processing policy or task for the acquired contents. + +### **13.9.2 Reference points Ci2** + +The Ci2 reference point is between the CAS module (see clause 10.1.1.1) and the CPPS module (see clauses 10.1.1.3 and 10.1.2.1). + +This reference point is used by CAS to deliver content metadata to CPPS for content pre-processing. + +### **13.9.3 Reference points Ci3** + +The Ci3 reference point is between the CAS module (see clause 10.1.1.1) and the CPS module (see clause 10.1.1.4). + +This reference point is used by CAS to deliver content metadata to CPS for content protection processing. + +### **13.9.4 Reference points Ci4** + +The Ci4 reference point is between the CAS module (see clause 10.1.1.1) and the MPPS module (see clauses 10.1.1.5 and 10.1.2.2). + +This reference point is used by CAS to deliver content metadata to MPPS. + +### **13.9.5 Reference points Ci5** + +The Ci5 reference point is between the CPCS module (see clause 10.1.1.2) and the CPPS module (see clauses 10.1.1.3 and 10.1.2.1). + +This reference point is used by CPCS to deliver control messages of content processing to CPPS. + +### **13.9.6 Reference points Ci6** + +The Ci6 reference point is between the CPPS module (see clause 10.1.1.3 and 10.1.2.1) and the MPPS module (see clauses 10.1.1.5 and 10.1.2.2). + +This reference point is used by CPPS to deliver processed metadata (i.e., content pre-processing) to MPPS for metadata aggregation. + +### **13.9.7 Reference points Ci7** + +The Ci7 reference point is between the CPS module (see clause 10.1.1.4) and the MPPS module (see clauses 10.1.1.5 and 10.1.2.2). + +This reference point is used by CPS to deliver processed metadata (i.e., content protection processing) to MPPS for metadata aggregation. + +### **13.9.8 Reference points Ci8** + +The Ci8 reference point is between the MPPS module (see clauses 10.1.1.5 and 10.1.2.2) and the CDMS module (see clause 10.1.1.7). + +This reference point is used by MPPS to deliver aggregated content metadata to CDMS for content distribution management. + +### **13.10 Reference points Ni** + +The Ni reference points (see Figure 7-f) are used to exchange messages between fine-grained service modules inside the service navigation service module. These reference points represent functional interfaces in indirect connection case and they are implemented by reference point NA. + +### **13.10.1 Reference points Ni1** + +The Ni1 reference point is between the SAMS module (see clause 10.2.1.1) and UECSS module (see clause 10.2.1.8). + +This reference point is used to exchange messages for collecting user behavioural data on service discovery and selection. + +### **13.10.2 Reference points Ni2** + +The Ni2 reference point is between the BCMS module (see clause 10.2.1.2) and the UECSS module (see clause 10.2.1.8). + +This reference point is used to exchange messages for collecting user behavioural data on navigation of broadcast services. + +### **13.10.3 Reference points Ni3** + +The Ni3 reference point is between the VCMS module (see clause 10.2.1.3) and the UECSS module (see clause 10.2.1.8). + +This reference point is used to exchange messages for collecting user behavioural data on navigation of on-demand services. + +### **13.10.4 Reference points Ni4** + +The Ni4 reference point is between the CMS module (see clause 10.2.1.4) and the UECSS module (see clause 10.2.1.8). + +This reference point is used to exchange messages for collecting user behavioural data on navigation of cast members. + +### **13.10.5 Reference points Ni5** + +The Ni5 reference point is between the CSS module (see clauses 10.2.1.7 and 10.2.2.1) and the UECSS module (see clause 10.2.1.8). + +This reference point is used to exchange messages for collecting user behavioural data on content searching events. + +### **13.10.6 Reference points Ni6** + +The Ni6 reference point is between the NCMS module (see clause 10.2.1.6) and the UECSS module (see clause 10.2.1.8). + +This reference point is used to exchange messages for collecting user behavioural data on browsing navigation categories. + +### **13.10.7 Reference points Ni7** + +The Ni7 reference point is between the CRS module (see clause 10.2.2.2) and the UECSS module (see clause 10.2.1.8). + +This reference point is used to exchange messages for collecting user behavioural data on content rating events. + +### **13.10.8 Reference points Ni8** + +The Ni8 reference point is between the CPRS module (see clause 10.2.2.3) and the UECSS module (see clause 10.2.1.8). + +This reference point is used by CPRS to acquire aggregated data of user behaviours from UECSS for generating content popularity ranking. + +### **13.10.9 Reference points Ni9** + +The Ni9 reference point is between the PRS module (see clause 10.2.2.4) and the UECSS module (see clause 10.2.1.8). + +This reference point is used by PRS to acquire aggregated data of user behaviours from UECSS for generating personalized recommendations. + +### **13.10.10 Reference points Ni10** + +The Ni10 reference point is between the CSS module (see clauses 10.2.1.7 and 10.2.2.1) and the PRS module (see clause 10.2.2.4). + +This reference point is used by CSS to acquire personalized recommendations from PRS for generating personalized search results. + +## **13.11 Reference points Si** + +The Si reference points (see Figure 7-g) are used to exchange messages between fine-grained service modules inside the service control service module. These reference points represent functional interfaces in indirect connection cases and they are implemented by reference point SA. + +### **13.11.1 Reference points Si1** + +The Si1 reference point is between the APMS module (see clause 10.3.2) and the SMS module (see clause 10.3.9). + +This reference point is used by APMS to acquire user information or request to update session data for application settings or operations. + +### **13.11.2 Reference points Si2** + +The Si2 reference point is between the CAS module (see clause 10.3.5) and the SMS module (see clause 10.3.9). + +This reference point is used by CAS to acquire user information or request to update session data for authorization. + +### **13.11.3 Reference points Si3** + +The Si3 reference point is between the CAS module (see clause 10.3.5) and the SCSS module (see clause 10.3.7). + +This reference point is used to deliver user's subscribed content packages for content authorization. + +### **13.11.4 Reference points Si4** + +The Si4 reference point is between the SPMS module (see clause 10.3.3) and the SCSS module (see clause 10.3.7). + +This reference point is used to deliver the information of service/content packages for subscription processing. + +### **13.11.5 Reference points Si5** + +The Si5 reference point is between the SCSS module (see clause 10.3.7) and the SMS module (see clause 10.3.9). + +This reference point is used by SCSS to acquire user information or request to update session data for subscription. + +### **13.11.6 Reference points Si6** + +The Si6 reference point is between the SCSS module (see clause 10.3.7) and the CAAS module (see clause 10.3.8). + +This reference point is used by SCSS to deliver subscription/unsubscribe information and service/content package information to CAAS for charging and accounting. + +#### **13.11.7 Reference points Si7** + +The Si7 reference point is between the SCSS module (see clause 10.3.7) and the UPMS module (see clause 10.3.1). + +This reference point is used by SCSS to deliver user's subscription/unsubscribe information to UPMS. + +#### **13.11.8 Reference points Si8** + +The Si8 reference point is between the UAS module (see clause 10.3.4) and the SMS module (see clause 10.3.9). + +This reference point is used by UAS to request to create user session for the successful authentication. + +### **13.11.9 Reference points Si9** + +The Si9 reference point is between the UAS module (see clause 10.3.4) and the UPMS module (see clause 10.3.1). + +This reference point is used by UAS to acquire user information from UPMS for user authentication. + +#### **13.11.10 Reference points Si10** + +The Si10 reference point is between the APMS module (see clause 10.3.2) and the UECSS module (see clause 10.3.10). + +This reference point is used to exchange messages for collecting user behavioural data on recording content bookmarks or favourites. + +### **13.11.11 Reference points Si11** + +The Si11 reference point is between the CAS module (see clause 10.3.5) and the UECSS module (see clause 10.3.10). + +This reference point is used to exchange messages for collecting user behavioural data on authorization events. + +#### **13.11.12 Reference points Si12** + +The Si12 reference point is between the SCSS module (see clause 10.3.7) and the UECSS module (see clause 10.3.10). + +This reference point is used to exchange messages for collecting user behavioural data on subscription events. + +### **13.11.13 Reference points Si13** + +The Si13 reference point is between the CPAS module (see clause 10.3.6) and the UECSS module (see clause 10.3.10). + +This reference point is used to exchange messages for collecting user behavioural data on content protection authorization. + +### **13.11.14 Reference points Si14** + +The Si14 reference point is between the UAS module (see clause 10.3.4) and the UECSS module (see clause 10.3.10). + +This reference point is used to exchange messages for collecting user behavioural data on authentication events. + +### **13.12 Reference points Di** + +The Di reference points (see Figure 7-h and 7-i) are used to exchange messages between fine-grained service modules inside the content delivery service module. These reference points represent functional interfaces in indirect connection cases and they are implemented by reference point DA. + +### **13.12.1 Reference points Di1** + +The Di1 reference point is between the CDS module (see clause 10.4.1) and the VCPS module (see clause 10.4.2). + +This reference point is used by CDS to deliver content metadata to VCPS for VoD content processing (e.g., keyframe extraction). + +### **13.12.2 Reference points Di2** + +The Di2 reference point is between the CDS module (see clause 10.4.1) and the URSS module (see clause 10.4.4). + +This reference point is used to deliver content distribution information for the basis of scheduling decisions. + +### **13.12.3 Reference points Di3** + +The Di3 reference point is between the CDS module (see clause 10.4.1) and the UCDS module (see clause 10.4.6). + +This reference point is used by CDS to distribute content and related metadata to UCDS for content deployment. + +### **13.12.4 Reference points Di4** + +The Di4 reference point is between the UCDS module (see clause 10.4.6) and the VCPS module (see clause 10.4.2). + +This reference point is used by UCDS to deliver content metadata to VCPS for VoD content pre-processing (e.g., transcoding). + +### **13.12.5 Reference points Di5** + +The Di5 reference point is between the UCDS module (see clause 10.4.6) and the BCPS module (see clause 10.4.3). + +This reference point is used by UCDS to deliver content metadata to BCPS for broadcast content processing. + +#### **13.12.6 Reference points Di6** + +The Di6 reference point is between the UCDS module (see clause 10.4.6) and the APCS module (see clause 10.4.5). + +This reference point is used by UCDS to request access permission control from APCS for unicast delivery service. + +### **13.12.7 Reference points Di7** + +The Di7 reference point is between the UCDS module (see clause 10.4.6) and the URSS module (see clause 10.4.4). + +This reference point is used to exchange messages for collecting load data of UCDS. + +### **13.12.8 Reference points Di8** + +The Di8 reference point is between the UCDS module (see clause 10.4.6) and the BTSS module (see clause 10.4.8). + +This reference point is used to exchange messages for fetching contents based on back-to-source policy. + +### **13.12.9 Reference points Di9** + +The Di9 reference point is between the MCDS module (see clause 10.4.7) and the APCS module (see clause 10.4.5). + +This reference point is used by MCDS to request access permission control from APCS for multicast delivery service. + +### **13.12.10 Reference points Di10** + +The Di10 reference point is between the CCSS module (see clause 10.4.11) and the UCDS module (see clause 10.4.6). + +This reference point is used by CCSS to collect network flow data of content consumptions from UCDS. + +### **13.12.11 Reference points Di11** + +The Di11 reference point is between the CCSS module (see clause 10.4.11) and the APCS module (see clause 10.4.5). + +This reference point is used by CCSS to acquire user information from APCS for network flow statistic. + +#### **13.12.12 Reference points Di12** + +The Di12 reference point is between the CDCS module (see clause 10.4.9) and the CDS module (see clause 10.4.1). + +This reference point is used to deliver content distribution policy. + +#### **13.12.13 Reference points Di13** + +The Di13 reference point is between the CDCS module (see clause 10.4.9) and the VCPS module (see clause 10.4.2). + +This reference point is used to deliver VoD content processing policy. + +#### **13.12.14 Reference points Di14** + +The Di14 reference point is between the CDCS module (see clause 10.4.9) and the BCPS module (see clause 10.4.3). + +This reference point is used to deliver broadcast content processing policy. + +#### **13.12.15 Reference points Di15** + +The Di15 reference point is between the CDCS module (see clause 10.4.9) and the UCDS module (see clause 10.4.6). + +This reference point is used to deliver QoS and content caching policy. + +#### **13.12.16 Reference points Di16** + +The Di16 reference point is between the CDCS module (see clause 10.4.9) and the URSS module (see clause 10.4.4). + +This reference point is used to deliver user scheduling policy. + +#### **13.12.17 Reference points Di17** + +The Di17 reference point is between the CDCS module (see clause 10.4.9) and the APCS module (see clause 10.4.5). + +This reference point is used to deliver the authentication mechanism and key. + +#### **13.12.18 Reference points Di18** + +The Di18 reference point is between the CDCS module (see clause 10.4.9) and the BTSS module (see clause 10.4.8). + +This reference point is used to deliver back-to-source policy. + +### **13.12.19 Reference points Di19** + +The Di19 reference point is between the UCDS module (see clause 10.4.6) and the AMS module (see clause 10.4.10). + +This reference point is used to exchange messages for collecting user behavioural data on unicast delivery service. + +#### **13.12.20 Reference points Di20** + +The Di20 reference point is between the APCS module (see clause 10.4.5) and the AMS module (see clause 10.4.10). + +This reference point is used by AMS to acquire user information from APCS for the creation of audience measurement report. + +#### **13.12.21 Reference points Di21** + +The Di21 reference point is between the BTSS module (see clause 10.4.8) and the AMS module (see clause 10.4.10). + +This reference point is used to exchange messages for collecting user behavioural data on back-to-source service. + +### **13.12.22 Reference points Di22** + +The Di22 reference point is between the MCDS module (see clause 10.4.7) and the AMS module (see clause 10.4.10). + +This reference point is used to exchange messages for collecting user behavioural data on multicast delivery service. + +# Annex A + +## Metadata information relating to content distribution + +(This annex forms an integral part of this Recommendation.) + +This annex describes the information of exchanged metadata between the content management service and service navigation service, service control service or content delivery service during the content distribution procedure. + +Table A.1 lists the minimum recommended subset of content metadata and is not intended to be exhaustive or restrictive for practical implementation. All the elements and attributes of metadata shown in this table refer to the definitions in [ITU-T H.750]. + +**Table A.1 – Elements or attributes information of content metadata** + +| Distribution direction | Distributed metadata | +|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| content management service →
    service navigation service |

    Elements for content: includes all the defined attributes in clause 8.1 of [ITU-T H.750] except:

    • – Rights or Copyright information
    • – Codec or format
    • – Acquisition or delivery schedule, protocol and address
    • – File format, file size

    Elements for collective content: includes all the defined attributes in clause 8.1 of [ITU-T H.750] except:

    • – Price and conditions of availability of collective content

    Elements for group of segment: includes all the defined attributes in clause 8.1 of [ITU-T H.750].

    Elements for service (or channel): includes all the defined attributes in clause 8.1 of [ITU-T H.750].

    Elements for content adaptation: includes all the defined attributes in clause 8.1 of [ITU-T H.750] except:

    • – Targeting
    • – Interstitials replacement, replacement rules

    Elements for usage restrictions, usage rules:

    • – Validity period
    • – Output control
    • – Trick mode enabled or not
    • – Maximum buffering size or duration
    • – Schedule (timeslots) for pay-per view
    • – Restricted area
    • – Expiration date or deletion management information
    • – Recordable or not
    | +| content management service →
    service control service |

    Elements for content:

    • – Identifier
    • – Title/name
    • – Rights or Copyright information (for more details, see Appendix V of [ITU-T H.751])
    • – Name of content provider, service provider
    • – Type of content
    | + +**Table A.1 – Elements or attributes information of content metadata** + +| Distribution direction | Distributed metadata | +|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • – Encrypted or not
    • – Content expiration date

    Elements for collective content:

    • – Total number of sub-contents
    • – IDs for sub-contents
    • – IDs for other collections of which this collection is a member

    Elements for content adaptation:

    • – Consumption control parameter

    Elements for usage restrictions, usage rules:

    • – Validity period
    • – DRM type, clearing house or pricing server URL, license identification
    • – Restricted area
    • – Expiration date or deletion management information
    | +| content management service →
    content delivery service |

    Elements for content:

    • – Identifier
    • – Name of content provider, service provider
    • – Codec or format
    • – Aspect ratios, resolution, bit rate, frame rate for video
    • – Mono, stereo, multi-channel indication for audio
    • – Acquisition or delivery schedule, protocol and address
    • – File format, file size
    • – Duration

    Elements for collective content:

    • – IDs for sub-contents

    Elements for describing delivery modes: includes all the defined attributes in clause 8.1 of [ITU-T H.750].

    | + +# Appendix I + +## Procedural flows relating to IPTV services + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Content preparation flows + +This appendix describes some typical scenarios and the corresponding procedural flows of content preparation. The flows show how service capabilities are invoked in order to complete the preparation process of content and metadata. + +#### I.1.1 Content preparation without additional processing + +##### Scenario + +Content and metadata source derived from content provider functions can be directly used to deliver to end user functions. In this scenario, a minimum set of content management service capabilities is required to be adopted. + +##### Sequence + +Figure I.1 illustrates the simplest sequence of content preparation. In this figure, the dotted lines represent logical associations instead of direct interaction between functional modules. + +![Sequence diagram for content preparation without additional processing](d116934392360da963e91d840d1e45a8_img.jpg) + +The diagram illustrates the sequence of content preparation. It starts with 'Content provider functions' on the left, which has a solid arrow pointing to a large box labeled 'Content management service'. Inside this box, there are three numbered steps: ① CAS, ② MPPS, and ③ CDMS, connected by dashed arrows in that order. From the 'CDMS' step, four dotted arrows point to four separate boxes on the right: 'Data service', 'Service navigation service', 'Service control service', and 'Content delivery service'. Below the diagram, the text 'H.705.1(23)' is present. + +Sequence diagram for content preparation without additional processing + +**Figure I.1 – Sequence diagram for content preparation without additional processing** + +- 1) CAS (see clause 10.1.1.1) acquires content and metadata from the content provider, checks data integrity and validity, downloads and buffers the content. +- 2) MPPS (see clauses 10.1.1.5 and 10.1.2.2) checks and supplements metadata information, and conveys data to CDMS. +- 3) CDMS (see clause 10.1.1.7) deploys the content and metadata into data service and then distribute metadata needed for service presentation to service navigation service, metadata needed for service management to service control service, content and metadata needed for delivery to content delivery service, respectively. + +#### I.1.2 Content preparation with additional processing + +##### Scenario + +Content and metadata source derived from content provider functions is used to offer IPTV services on one kind of IPTV terminal device (TD) (e.g., TD Type1). These contents are also authorized by the content provider to another kind of IPTV TD (e.g., TD Type2). In this scenario, content processing service capabilities are required to be adopted. + +##### Sequence + +Figure I.2 illustrates the entire sequence of content preparation. In this figure, the dotted lines represent logical associations instead of direct interaction between functional modules. + +![Sequence diagram for content preparation with additional processing](ec3647789b5c38fb686f2a0833324e79_img.jpg) + +The diagram illustrates the sequence of content preparation. It starts with 'Content provider functions' on the left, which points to a large box labeled 'Content management service'. Inside this box, there are six numbered steps: ① CAS, ② CPCS, ③ CPPS, ④ CPS, ⑤ MPPS, and ⑥ CDMS. Arrows connect these steps in sequence. A dashed line connects step ① to step ⑤. From step ⑥, four dotted lines point to four separate boxes on the right: 'Data service', 'Service navigation service', 'Service control service', and 'Content delivery service'. The text 'H.705.1(23)' is at the bottom right. + +Sequence diagram for content preparation with additional processing + +**Figure I.2 – Sequence diagram for content preparation with additional processing** + +- 1) CAS (see clause 10.1.1.1) acquires content and metadata source (of TD Type1) from the content provider, checks data integrity and validity, downloads and buffers the content, and conveys data to CPCS and MPPS. +- 2) CPCS (see clause 10.1.1.2) generates the processing tasks for the contents and conveys tasks to CPPS. In this scenario, processing tasks may include media transcoding task (e.g., to lower bit rate) and media packaging task (e.g., DASH format for transmission). +- 3) CPPS (see clauses 10.1.1.3 and 10.1.2.1) executes media content processing based on the assigned tasks, generates new content and metadata for TD Type2, buffers the new content, and conveys the data to CPS. +- 4) CPS (see clause 10.1.1.4) executes content encryption based on digital rights information, generates the protected content and security-related metadata, buffers the protected content, and conveys the data to MPPS. +- 5) MPPS (see clauses 10.1.1.5 and 10.1.2.2) performs metadata aggregation of the original contents and processed contents and then conveys data to CDMS. In this scenario, the generated metadata for multiple TD will be correlated with the original metadata. +- 6) CDMS (see clause 10.1.1.7) deploys the content and metadata into data service and then distribute content and metadata to service navigation service, service control service and content delivery service, respectively. + +### I.2 Service/content presentation flow + +This appendix describes the procedural flow of service/content presentation. + +##### Scenario + +The end user is a new user for IPTV services and selects to subscribe a service package. IPTV service and contents are presented in MAFR-based presentation mode [ITU-T H.760]. + +##### Sequence + +Figure I.3 illustrates how service capabilities are invoked in order to complete the presentation process of IPTV services and contents on user interface. In this figure, the dotted lines represent logical associations instead of direct interaction between functional modules, which is actually implemented via service access control. + +![Sequence diagram for service/content presentation. The diagram shows interactions between End-user functions, User interface, Service navigation service, and Service control service. The Service navigation service contains NCMS, SAMS, BCMS, VCMS, CMS, and PMS. The Service control service contains UPMS, SCSS, UAS, and SMS. The sequence of interactions is: 1) Service discovery and selection from User interface to Service navigation service; 2) Service subscription from User interface to Service control service; 3) User authentication from User interface to Service control service; 4) User session creation from User interface to Service control service; 5) Service navigation from User interface to Service navigation service. The diagram is labeled H.705.1(23) at the bottom right.](12c19090355e19922e23044633b9d1ea_img.jpg) + +Sequence diagram for service/content presentation. The diagram shows interactions between End-user functions, User interface, Service navigation service, and Service control service. The Service navigation service contains NCMS, SAMS, BCMS, VCMS, CMS, and PMS. The Service control service contains UPMS, SCSS, UAS, and SMS. The sequence of interactions is: 1) Service discovery and selection from User interface to Service navigation service; 2) Service subscription from User interface to Service control service; 3) User authentication from User interface to Service control service; 4) User session creation from User interface to Service control service; 5) Service navigation from User interface to Service navigation service. The diagram is labeled H.705.1(23) at the bottom right. + +**Figure I.3 – Sequence diagram for service/content presentation** + +- 1) When the end user accesses to IPTV services through user interface for the first time, SAMS (see clause 10.2.1.1) provides service related metadata required by SP service discovery and selection. +- 2) When the end user selects to subscribe a desired IPTV service, UPMS (see clause 10.3.1) acquires user information, terminal device information from the end user for service registration, while acquiring network information of the user and other necessary information from external system. SCSS (see clause 10.3.7) provides the details of service packages and fulfils the subscription of a service provider's package. Then UPMS completes the configuration of service registration information, and user account information for the end user. +- 3) When the end user requests to access the subscribed IPTV service, UAS (see clause 10.3.4) performs user authentication and returns service initiation information to the end user. +- 4) SMS (see clause 10.3.9) creates the user session and manages the session data during the usage of IPTV service of the end user. +- 5) The end user connects to the portal of the IPTV service, then NCMS/BCMS/VCMS/CMS/PMS (see clauses 10.2.1.6, 10.2.1.2, 10.2.1.3, 10.2.1.4 and 10.2.1.5) are invoked as required for the presentation of IPTV contents. + +### I.3 Content consumption flow + +This appendix describes the procedural flows of content consumption. + +##### Scenario + +The end user searches a VoD content of interest on a user interface and subscribes to a content package in which the charging is based on network flow. He requests for content delivery service and it is offered in unicast delivery mode and by back-to-source means. + +##### Sequence + +Figure I.4 illustrates how service capabilities are invoked in order to complete the content delivery and charging process of a particular VoD content. In this figure, the dotted lines represent logical associations instead of direct interaction between functional modules, which is actually implemented via service access control. + +![Sequence diagram for content consumption showing interactions between End-user functions, User interface, Service navigation service (CSS, VCMS), Service control service (CAS, SCSS, CAAS), and Content delivery service (URSS, UCDS, APCS, BTSS, CCSS).](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +``` + +sequenceDiagram + participant End-user functions + participant User interface + participant Service navigation service + subgraph Service navigation service + CSS + VCMS + end + participant Service control service + subgraph Service control service + CAS + SCSS + CAAS + end + participant Content delivery service + subgraph Content delivery service + URSS + UCDS + APCS + BTSS + CCSS + end + + Note left of End-user functions: ① Service searching + End-user functions->>User interface: + User interface->>Service navigation service: + Note left of Service navigation service: ② Service navigation + Service navigation service->>User interface: + Note left of User interface: ③ Content consumption + User interface->>Service control service: + Note left of Service control service: ④ Content subscription + Service control service->>User interface: + Note left of User interface: ⑤ Content consumption + User interface->>Service control service: + Note left of Service control service: ⑥ Service resource request + Service control service->>Content delivery service: + Note left of Content delivery service: ⑦ Service resource request (Redirected) + Content delivery service->>User interface: + Note left of User interface: ⑧ Permission authentication + Content delivery service->>Service control service: + Note left of Service control service: ⑨ Content fetching + Service control service->>Content delivery service: + Note left of Content delivery service: ⑩ Content delivery + Content delivery service->>End-user functions: + Note left of End-user functions: ⑪ Collect user events + Content delivery service->>Service control service: + Note left of Service control service: ⑫ Subscription information + Service control service->>Content delivery service: + Note left of Content delivery service: ⑫ Network flow statistic + Content delivery service->>End-user functions: + Note left of End-user functions: ⑬ Accounting information + +``` + +Sequence diagram for content consumption showing interactions between End-user functions, User interface, Service navigation service (CSS, VCMS), Service control service (CAS, SCSS, CAAS), and Content delivery service (URSS, UCDS, APCS, BTSS, CCSS). + +H.705.1(23) + +**Figure I.4 – Sequence diagram for content consumption** + +- 1) The end user searches for a desired VoD content on user the interface, CSS (see clauses 10.2.1.7 and 10.2.2.1) provides the search result containing this content. +- 2) When the end user selects to browse the details of this VoD, VCMS (see clause 10.2.1.3) provides content related metadata for content presentation on the user interface. +- 3) When the end user requests to consume the content, CAS (see clause 10.3.5) verifies the user license and purchased content package, and returns the failure result of content authorization. +- 4) When the end user selects to subscribe content packages, SCSS (see clause 10.3.7) provides the detailed information of the content packages and fulfils the purchase and payment. +- 5) When the end user requests to consume the content again, CAS (see clause 10.3.5) grants the permission for the user and returns the initiated network/service resource. +- 6) When the end user is routed to the main entry of the content delivery service, URSS (see clause 10.4.4) selects the appropriate service resource based on a scheduling policy. +- 7) The end user is redirected to UCDS (see clause 10.4.6) for the content delivery in unicast mode. +- 8) APCS (see clause 10.4.5) is invoked to perform the permission control and returns the authentication result to UCDS. +- 9) When UCDS finds the requested content is unavailable in the local data service module, it requests BTSS (see clause 10.4.8) to fetch the content. +- 10) UCDS downloads the content from BTSS while delivering it to the end user. It also responds to the user's playback control (e.g., trick mode operations) and provides high-quality streaming service. +- 11) CCSS (see clause 10.4.11) collects user event data from UCDS and generates statistical data on the network flow of consuming of this content. + +- 12) CAAS (see clause 10.3.8) receives the content subscription information from SCSS and the network flow data from CCSS, and generates the charging information concerning this content consumption. +- 13) CAAS conveys the accounting information to the end user. + +# Appendix II + +## Mapping relationship of functional modules between [ITU-T Y.1910] and this Recommendation + +(This appendix does not form an integral part of this Recommendation.) + +This appendix describes the mapping relationship between the defined functions and functional blocks of [ITU-T Y.1910] and the defined modules and fine-grained modules of this Recommendation. It provides a reference for upgrading the conventional IPTV service platform to an open platform. + +Table II.1 lists the minimum set of modules and fine-grained modules (in the right two columns) defined in this Recommendation that can match the functionalities supported by functions and functional blocks (in the left two columns) in [ITU-T Y.1910], by referring to the descriptions in clause 9 and clause 10.3 of [ITU-T Y.1910]. Correspondingly, this Recommendation can cover all the technical requirements of [ITU-T Y.1910] and further offer more enhanced functions than [ITU-T Y.1910]. + +**Table II.1 – Mapping relationship between [ITU-T Y.1910] and this Recommendation** + +| Functions/functional block [ITU-T Y.1910] | | Module/fine-grained module (this Recommendation) | | +|-------------------------------------------|--------------------------------------|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Application functions | IPTV application functions | Service control service | User authentication service
    Content authorization service
    Service/content subscription service
    Session management service | +| | | Service navigation service | Service/application metadata service
    Broadcast content metadata service
    VoD content metadata service
    Cast metadata service
    Picture metadata service
    Navigation category metadata service | +| | | User interface | | +| | | Data service | | +| | Application profile functional block | Service control service | Application profile management service
    User profile management service | +| | | Data service | | +| | Content preparation functions | Content management service | Content acquisition service
    Content processing control service
    Content pre-processing service
    Content protection service
    Metadata post-processing service | +| | | Data service | | +| Service and content protection functions | | Content management service | Content protection service | + +**Table II.1 – Mapping relationship between [ITU-T Y.1910] and this Recommendation** + +| Functions/functional block
    [ITU-T Y.1910]     | | Module/fine-grained module (this Recommendation) | | +|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Service control service | Content protection authorization service
    User authentication service | +| | | Data service | | +| Service control functions | IPTV service control functional block | Service control service | User authentication service
    Content authorization service
    Charging and accounting service | +| | | Data service | | +| | Service user profile functional block | Service control service | User profile management service
    Session management service | +| | | Data service | | +| Content delivery functions | Content distribution and location control functions | Content delivery service | Content distribution service
    User request scheduling service
    Content delivery configuration service | +| | | Data service | | +| | Content delivery and storage functions | Content delivery service | Access permission control service
    Unicast content delivery service
    Multicast content delivery service
    VoD content processing service
    Broadcast content processing service
    Content consumption statistic service | +| | | Data service | | +| | | User interface | | +| Management functions | Application management functional block
    Content delivery management functional block
    Service control management functional block | Operation and maintenance management | Upgrade management
    Monitoring management
    Logging management
    Security management | +| | | Data service | | + +# Bibliography + +- [b-ITU-T F.902] Recommendation ITU-T F.902 (1995), *Interactive services design guidelines*. +- [b-ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems*. +- [b-ITU-T H.72x] ITU-T H.72x series of Recommendations on *IPTV terminal devices*. +- [b-ITU-T J.1306] Recommendation ITU-T J.1306 (2023), *Specification of microservices architecture for audio-visual media in the converged media cloud*. +- [b-ITU-T T.174] Recommendation ITU-T T.174 (1996), *Application programming interface (API) for MHEG-1*. +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions*. +- [b-ITU-T Y.110] Recommendation ITU-T Y.110 (1998), *Global Information Infrastructure principles and framework architecture*. +- [b-ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services*. +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*. +- [b-ITU-T Y.2080] Recommendation ITU-T Y.2080 (2012), *Functional architecture for distributed service networking*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92c54b38f8c7f488d335a805d629b464400ac4ba --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bb6c5346b35c6a6d1e14950e7a126323ed427fef71088e37dffeaf5788c3cf3 +size 56087 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3043a805d4f03dc1e60717e98942a94b336d85a --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80a5add10f1e8fabf3c623a3a32822a086478447385dd8a65e68160a4db0288c +size 32844 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1e58ad1204116f33f565e57f908814825f7417d --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5686bd8cc0506114d621602f29a5f7d7f8951aa188e9d3a9b6088e21ce8a5794 +size 43793 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d8deae6031c18707104a329a7eae044811bbb4b --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f418e2fcf77b057e807e60d0a0a741dd98ab9ee337764072def10cd9ce79d647 +size 5986 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/4d8ec886ccb5f4f6d90fe2c8d0c118bd_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/4d8ec886ccb5f4f6d90fe2c8d0c118bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5219046adb4c7d3abef260a200cba4dab8a9255 --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/4d8ec886ccb5f4f6d90fe2c8d0c118bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:879e7361144bf5fd6dbed74de551adfe13c796fba71ba17aaa3deecff99e377f +size 25588 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13a3f448c9ae9978561c8026fddabd18936d700b --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e54dd6201ee575026556efb709675da1aee280cc8a45deb5bead28d84704111 +size 144759 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6c0ec65704edbdff6bbfe603d0fbeac238fc72d --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79bc26f6d2e4906f7adb7175ed914b0898c4f415556cc54ba3686980c8226d5f +size 55223 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e78306c5e337637cf7190bc3b7c625bb733067ae --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b287582fc50c1ef8f3353c580853931f5187176c6f8b019ad4e4061134867c1b +size 145778 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca7d141b146a3c9df936efe63b8f58e40181fa4b --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ac47d4ebbc1c8f3b69c0794177f67e2e31b59365b105ec65de3318b905970f3 +size 59336 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/a4bfa2343d75076b79f7e33d93915e00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38180284a95b761444838d3279f3d72e544ee424 --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/a4bfa2343d75076b79f7e33d93915e00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:533bc9e466522c268a4708b490e584e42d906e6473edad82cb65e35684d4512d +size 11937 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c924527322df28979be4810c5d07cc03e01bc879 --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:240dae12fcc804039d1ffff978eb56f155d7b42260fed00ed121c9069a6c95e1 +size 145642 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52979553658e3ccfc4ad4c8381cb0c9940f92238 --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43a177e8e8c595aa5b20f840d384b988786ba0e7936fcc51f212a5b06c6ca750 +size 131033 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/f117f4876cd1523b1717f3e38bd74229_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/f117f4876cd1523b1717f3e38bd74229_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80cc6774cc4dbf479feace43fa783a2b9a8355b9 --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/f117f4876cd1523b1717f3e38bd74229_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6539ddf015e2139d1c48c02571a929f7a33e5d67f29023f6568bb95330b5a30d +size 29554 diff --git a/marked/H/T-REC-H.721-202203-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/marked/H/T-REC-H.721-202203-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8514f91aa40fdddfc7784868398778080427a7f1 --- /dev/null +++ b/marked/H/T-REC-H.721-202203-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fa73c2178d25e6172b7c975e1a5b632ed242ce262446dedd865ebe8dad7bef3 +size 139337 diff --git a/marked/H/T-REC-H.722-201401-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/H/T-REC-H.722-201401-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..667395fe37c9c24f877166c893feb8b62b8c7416 --- /dev/null +++ b/marked/H/T-REC-H.722-201401-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:954f4dd53cc64525c4d7d2b83380515701de953f12c8a69bd6071a06844c398a +size 79262 diff --git a/marked/H/T-REC-H.722-201401-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.722-201401-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/H/T-REC-H.722-201401-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/H/T-REC-H.722-201401-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.722-201401-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08f159733f20cd67c9c29e7213379420c73c8a7b --- /dev/null +++ b/marked/H/T-REC-H.722-201401-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b6a73bfe847861ebfad13f260df0aa5667821cac447046e4f2aa4be4a7005be +size 64111 diff --git a/marked/H/T-REC-H.722-201401-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/H/T-REC-H.722-201401-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc3687ba725075742667cd73081f7098af6f9d42 --- /dev/null +++ b/marked/H/T-REC-H.722-201401-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8863e4c156dddaf94fe1dfec55865d91ce96bf76003b9b0693f0cf3c89244fd4 +size 140849 diff --git a/marked/H/T-REC-H.722-201401-I_PDF-E/raw.md b/marked/H/T-REC-H.722-201401-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..de551aaa8328c65bc16dcd4d87029d0187e5be72 --- /dev/null +++ b/marked/H/T-REC-H.722-201401-I_PDF-E/raw.md @@ -0,0 +1,955 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.722** + +(01/2014) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +IPTV terminal devices + +--- + +**IPTV terminal device: Full-fledged model** + +Recommendation ITU-T H.722 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN and WAN) | H.820–H.849 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.722 + +# IPTV terminal device: Full-fledged model + +## Summary + +Recommendation ITU-T H.722 describes the services and key features of the full-fledged Internet Protocol TV terminal device (IPTV TD) defined in Recommendation ITU-T H.720. In comparison with the IPTV TD-basic model defined in Recommendation ITU-T H.721, the full-fledged IPTV TD supports not only such basic services as linear TV and video-on-demand (VoD), but also advanced services such as Internet, medical applications, communications, etc. Based on these services and key features, this Recommendation specifies the architecture of the full-fledged IPTV TD, functional components within its architecture, software architecture for implementation reference and physical interfaces. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------------| +| 1.0 | ITU-T H.722 | 2014-01-13 | 16 | 11.1002/1000/12065-en | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2014 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 5 | +| 6 Overview ..... | 5 | +| 7 Services and key features of a full-fledged IPTV TD ..... | 6 | +| 7.1 Services of a full-fledged IPTV TD ..... | 6 | +| 7.2 Features of full-fledged IPTV TD ..... | 13 | +| 8 Full-fledged IPTV TD functional architecture ..... | 16 | +| 9 Functional components of IPTV full-fledged terminal device..... | 16 | +| 9.1 Terminal transport functions ..... | 16 | +| 9.2 Content delivery client functions..... | 16 | +| 9.3 Media client functions ..... | 17 | +| 9.4 Service, content and application protection (SCAP) client functions ..... | 17 | +| 9.5 Application client functions ..... | 17 | +| 9.6 Control client functions ..... | 17 | +| 9.7 Performance monitory client functions ..... | 18 | +| 9.8 Audience measurement client functions..... | 18 | +| 9.9 Terminal device management..... | 18 | +| 10 Software architecture ..... | 18 | +| 10.1 Resource abstraction layer (RAL) ..... | 18 | +| 10.2 Service logic adaptation layer ..... | 19 | +| 10.3 Presentation engine layer..... | 19 | +| 10.4 User experience skin and customization ..... | 19 | +| 11 Physical interfaces ..... | 19 | +| 11.1 Input interface..... | 20 | +| 11.2 Output interface ..... | 21 | +| 11.3 External data access interface..... | 21 | +| 11.4 Network access interface ..... | 21 | +| Bibliography..... | 22 | + + + +# IPTV terminal device: Full-fledged model + +# 1 Scope + +This Recommendation describes and specifies the functionalities of the IPTV terminal device (IPTV TD) for the IPTV full-fledged services defined in [ITU-T H.720]. This Recommendation is targeted at IPTV TDs that support more than the basic services supported by the IPTV TD-basic model defined in [ITU-T H.721]. The basic services include receiving linear TV services and video-on-demand services, with additional data content (such as text) using a managed content delivery network. The IPTV TD full-fledged model supports advanced services such as Internet services, medical applications, communication services, etc. + +The expected types of IPTV terminal devices are set-top boxes and digital TV sets with embedded IPTV capabilities. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.622.1] Recommendation ITU-T H.622.1 (2008), *Architecture and functional requirements for home networks supporting IPTV services*. +- [ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems*. +- [ITU-T H.721] Recommendation ITU-T H.721 (2009), *IPTV terminal devices: Basic model*. +- [ITU-T H.730] Recommendation ITU-T H.730 (2012), *Web-based terminal middleware for IPTV services*. +- [ITU-T H.741.0] Recommendation ITU-T H.741.0 (2012), *IPTV application event handling: Overall aspects of audience measurement for IPTV services*. +- [ITU-T H.741.1] Recommendation ITU-T H. 741.1 (2012), *IPTV application event handling: Audience measurement operations for IPTV services*. +- [ITU-T H.741.2] Recommendation ITU-T H. 741.2 (2012), *IPTV application event handling: Data structures of audience measurement for IPTV services*. +- [ITU-T H.741.3] Recommendation ITU-T H. 741.3 (2012), *IPTV application event handling: Audience measurement for IPTV distributed content services*. +- [ITU-T H.741.4] Recommendation ITU-T H. 741.4 (2012), *IPTV application event handling: Transport mechanisms for audience measurement*. +- [ITU-T H.750] Recommendation ITU-T H.750 (2008), *High-level specification of metadata for IPTV services*. +- [ITU-T H.760] Recommendation ITU-T H.760 (2009), *Overview of multimedia application frameworks for IPTV services*. + +- [ITU-T H.761] Recommendation ITU-T H.761 (2011), *Nested context language (NCL) and Ginga-NCL*. +- [ITU-T H.762] Recommendation ITU-T H.762 (2011), *Lightweight interactive multimedia environment (LIME) for IPTV services*. +- [ITU-T H.763.1] Recommendation ITU-T H.763.1 (2010), *Cascading style sheets for IPTV services*. +- [ITU-T H.764] Recommendation ITU-T H.764 (2012), *IPTV services enhanced script language*. +- [ITU-T H.770] Recommendation ITU-T H.770 (2009), *Mechanisms for service discovery and selection for IPTV services*. +- [ITU-T X.1191] Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects*. +- [ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services*. +- [ITU-R BT.2052] Recommendation ITU-R BT.2052 (2005), *Protection of end-users privacy in interactive broadcasting systems*. + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 client personal video recorder (cPVR)** [ITU-T Y.1901]: Same as PVR except that the recording device is located at the end-user's premises. + +**3.1.2 distributed PVR (dPVR)** [ITU-T H.720]: Multiple instances of PVR, where a combination of cPVRs and nPVRs can be used to record and store video, audio, and other associated data for subsequent playback. For example, this usually occurs within a home network containing multiple cPVRs in order to distribute storage of video, audio, and other data. + +**3.1.3 end user** [ITU-T Y.1910]: The actual user of the products or services. + +NOTE 1 – The end user consumes the product or service. An end user can optionally be a subscriber. + +**3.1.4 Internet Protocol television (IPTV)** [ITU-T Y.1901]: Multimedia services such as television/video/audio/text/graphics/data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. + +**3.1.5 IPTV terminal device** [ITU-T Y.1901]: A terminal device which has ITF functionality, e.g., an STB. + +**3.1.6 IPTV terminal function (ITF)** [ITU-T Y.1901]: The end user function(s) associated with a) receiving and responding to network control channel messages regarding session set-up, maintenance, and teardown, and b) receiving the content of an IP transport from the network and rendering. + +**3.1.7 linear TV** [ITU-T Y.1901]: A television service in which a continuous stream flows in real time from the service provider to the terminal device and where the user cannot control the temporal order in which contents are viewed. + +**3.1.8 middleware** [ITU-T Y.1901]: A layer of software between applications and resources, which consists of a set of service enablers that allow multiple functionalities running on one or more devices in an IPTV system to interact across a network. + +- 3.1.9 network personal video recorder (nPVR)** [ITU-T Y.1901]: Same as PVR except that the recording device is located at the service provider premises. +- 3.1.10 personal video recorder (PVR)** [ITU-T Y.1901]: An end-user controlled device that records, stores and plays back multimedia content. PVR is also known as personal digital recorder (PDR). +- 3.1.11 picture-in-picture (PIP)** [ITU-T Y.1901]: One programme is displayed on the full-sized IPTV TD screen, one or more other programmes are simultaneously displayed in inset windows. +- 3.1.12 push VoD** [ITU-T Y.1901]: A TV service where multimedia content is packaged and delivered at the discretion of the service provider to the end user's storage system. +- 3.1.13 service and content protection (SCP)** [ITU-T Y.1901]: A combination of service protection and content protection. +- 3.1.14 terminal device (TD)** [ITU-T Y.1901]: An end-user device which typically presents and/or processes the content, such as a personal computer, a computer peripheral, a mobile device, a TV set, a monitor, a VoIP terminal or an audio-visual media player. +- 3.1.15 time shifting** [ITU-T Y.1901]: A function which allows playback of content after its initial transmission. +- 3.1.16 trick mode functionality** [ITU-T Y.1901]: The ability to pause, rewind or forward stored content. +- 3.1.17 TV with trick mode** [ITU-T Y.1901]: TV service with trick mode functionality. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +- 3.2.1 full-fledged IPTV terminal device:** A full-fledged IPTV terminal device (IPTV TD) has the capabilities to support advanced IPTV services as well as the basic IPTV services. +- 3.2.2 full-screen display mode:** In this mode, the whole display area of the display device is occupied by the output content of the IPTV terminal function (ITF) inside the full-fledged IPTV terminal device. The output content of other non-IPTV applications is not displayed in the display device of the full-screen display mode. The input devices are all operating instructions delivered to the IPTV software application. +- 3.2.3 supplementary IPTV service:** An enhanced IPTV service (e.g., gaming, medical services, video telephony, etc.) which needs more capabilities than provided by the basic service components, including metadata, media management, etc. A supplementary IPTV service may be based on a combination of basic service components, additional service components (e.g., text-to-speech and voice recognition), or even directly OS-based resources. +- 3.2.4 window display mode:** In this mode, the output content of the IPTV terminal function (ITF) inside the full-fledged IPTV terminal device occupies a given display area (which is normally a rectangular area) of the display device. The remaining area is used to display the output content of other non-IPTV software applications based on the operating system (OS). + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-------------------------| +| A/V | Audio/Visual | +| ARQ | Automatic Repeat Query | +| CPU | Central Processing Unit | + +| | | +|---------|----------------------------------------------| +| cPVR | client Personal Video Recorder | +| CRL | Copy Right Licence | +| DASH | Dynamic Adaptive Streaming over HTTP | +| DVI | Digital Visual Interface | +| FEC | Forward Error Correction | +| GUI | Graphic User Interface | +| HD | High Definition | +| HDCP | High Definition Content Protection | +| IM | Instant Messaging | +| IP | Internet Protocol | +| IPTV | Internet Protocol Television | +| IPTV TD | Internet Protocol Television Terminal Device | +| ITF | IPTV Terminal Function | +| MAFR | Multimedia Application Framework | +| NDK | Native Development Kit | +| NGN | Next Generation Network | +| nPVR | network Personal Video Recorder | +| NVRAM | Non-Volatile Random Access Memory | +| OS | Operating System | +| OTP | One Time Programming | +| PAN | Personal Area Network | +| PIP | Picture-in-Picture | +| PSTN | Public Switched Telephone Network | +| PVR | Personal Video Recorder | +| QoS | Quality of Service | +| RACF | Resource and Admission Control Function | +| RAL | Resource Abstraction Layer | +| RAM | Random Access Memory | +| RGB | Red Green Blue | +| RSS | Really Simple Syndication | +| RTPCP | RTP Control Protocol | +| RTP | Real-Time Protocol | +| SCAP | Service, Content and Application Protection | +| SCP | Service and Content Protection | +| SD | Standard Definition | +| SDK | Software Development Kit | +| STB | Set-Top Box | + +| | | +|-------|-----------------------------------| +| TD | Terminal Device | +| TD-PD | Terminal Device Peripheral Device | +| UI | User Interface | +| VGA | Video Graphic Array | +| VoD | Video-on-Demand | +| VoIP | Voice over Internet Protocol | + +# 5 Conventions + +In this Recommendation: + +- The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. +- The keywords "**is prohibited from**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. +- The keywords "**is recommended**" indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. +- The keywords "**is not recommended**" indicate a requirement which is not recommended but which is not specifically prohibited. Thus, conformance with this specification can still be claimed even if this requirement is present. +- The keywords "**can optionally**" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +# 6 Overview + +This Recommendation describes and specifies the functionalities of the IPTV terminal devices for the IPTV full-fledged services defined in [ITU-T H.720]. This Recommendation is targeted at IPTV terminal devices not only supporting basic services supported by basic model IPTV terminal devices defined in [ITU-T H.721], which include receiving linear TV service and video-on-demand services, with additional data content (such as text) using a managed content delivery network, but also supporting advanced services such as Internet services, medical services, communication services, etc. + +This Recommendation provides a high-level description of functionalities and software architecture for common communication, configuration of a receiving environment for a service provider, service navigation, acquisition of linear TV service, acquisition of VoD service, acquisition of supplementary IPTV service, functionalities, software architecture and a physical interface which constitute the IPTV full-fledged model terminal device (hereafter referred to as full-fledged IPTV TD). + +# 7 Services and key features of a full-fledged IPTV TD + +### 7.1 Services of a full-fledged IPTV TD + +A full-fledged IPTV TD is required to support all the services available to the IPTV TD-basic model. It is further recommended that the full-fledged IPTV TD provide advanced capabilities, features and interfaces with respect to the IPTV TD-basic model defined in [ITU-T H.721], in order to support all the IPTV service use cases defined in [b-ITU-T Y-Sup.5]. A full-fledged IPTV TD will not be limited to the services provided by the IPTV TD-basic model, but will support the following additional services referred to in clauses 7.1.1 to 7.1.10. + +#### 7.1.1 Broadcast services + +##### 7.1.1.1 Linear TV with trick mode + +To support linear TV with trick mode, it is recommended that a full-fledged IPTV TD provide the following capabilities: + +- provision of the interface for users to access the contents without time limitation, including pause, rewind, fast forward, etc.; +- provision of the interface for users to enable or disable the service of linear TV with trick mode; +- provision of the interface to set the expiration time; +- provision of format and streaming methods defined in clause 7.1.1 of [ITU-T H.721]. It is also recommended that a full-fledged IPTV TD support HTTP-based streaming, such as dynamic adaptive streaming over HTTP (DASH) [b-ISO/IEC 23009-1]. + +##### 7.1.1.2 Personal broadcast service + +The personal broadcast service provides the end user with a way to advertise personal content (possibly including scheduling information) so that other end users can access such content. This service makes the IPTV end user a content provider. + +To support this service, a full-fledged IPTV TD plays a role as content source or for delivery functions. The following capabilities can optionally be provided by a full-fledged IPTV TD: + +- provision of A/V capturing/encoding for the end user to generate broadcasted content; +- provision of protocols for transmission of content, such as RTP/RTCP [b-IETF RFC 3550], and/or DASH [b-ISO/IEC 23009-1]; +- provision of security aspects associated with broadcasting of customer-generated content. + +##### 7.1.1.3 Hybrid: online and off-air TV delivery + +An alternative approach for the delivery of linear TV is to enable the end users' IPTV TD to receive the broadcast signal from the broadcaster, e.g., via traditional distribution techniques such as digital satellite TV or terrestrial digital TV. + +To support this service, it is recommended that a full-fledged IPTV TD provide the following capability: + +- provision for receiving the broadcast signal. + +##### 7.1.1.4 Linear TV with multi-view service + +Linear TV with multi-view is a service that consists of providing scenes with different camera angles. End users can select one angle from which they would like to watch. For example, when an end user watches a linear broadcast of a baseball game, he/she can choose to see the first base, third base, backfield, etc., and not be restricted to the channel director's preferences. + +The linear TV multi-view service might be carried in multiple streams, without being pre-combined into one stream by the broadcasters or the content providers. The end user may therefore watch different scenes from different camera angles at the same time. It is recommended that a full-fledged IPTV TD provide the following capabilities: + +- provision of protocols for multiple streaming of linear TV; +- provision of multi-stream decoding. + +#### **7.1.2 On-demand services** + +Content that has been prepared and delivered by the content provider for retrieval is received and stored by the service provider. If necessary, transcoding functions can be performed to accommodate the storage device characteristics. The end user can then select and retrieve such content from storage at any time, according to the constraints provided by the content protection metadata. + +For A/V-related on-demand services, it is recommended that a full-fledged IPTV TD support the formats and streaming methods defined in clause 7.1.2 of [ITU-T H.721]. It is also recommended that a full-fledged IPTV TD support HTTP-based streaming, such as DASH [b-ISO/IEC 23009-1]. + +##### **7.1.2.1 Reserved delivery service** + +The reserved delivery service can be used in several cases: + +- in VoD when video delivery cannot be carried out immediately following the end user request but will be triggered at a later stage by a wake-up mechanism; +- when an end user has subscribed to a reserved-video delivery service based on certain criteria (e.g., the end user has subscribed for the delivery of new movies from a specific director or with a specific actor, etc.); +- when the service provider offers a network personal video recorder (nPVR) functionality. After an end user record request, the nPVR waits for the event to be recorded. When the content is available in the nPVR, the content can be delivered in some cases to the end user's equipment without waiting for the end user request; +- when the service provider, on the basis of known user preferences, decides to download content that is likely to be requested by the end user to a TD having recording features, in order to avoid later network congestion; +- when the service provider decides to download commercials for insertion at content replay time. + +To support the reserved-content delivery service, it is recommended that a full-fledged IPTV TD provide the following capabilities: + +- provision of remote wake-up/notification mechanisms for content delivery; +- provision of background content downloading/recording mechanisms; +- provision of local or external storage. + +##### **7.1.2.2 On-demand with multi-view service** + +The on-demand with multi-view service provides various camera angles in addition to the one station view provided by the video-on-demand service. End users may select a camera angle from which they would like to watch. For example, when the end user watches a baseball game, he/she can choose to see the first base, third base, backfield, etc., and not only what is predefined by the channel. + +In this service, multiple VoD streams might be delivered to the IPTV TD while the on-demand video is playing via unicast protocols, as described in clause 7.1.1.4 for the linear TV with a multi-view service. It is recommended that a full-fledged IPTV TD provide the following capabilities: + +- provision of protocols for multi-streams of VoD; +- provision of multi-stream decoding. + +#### **7.1.3 Advertising service** + +The traditional advertising service consists of broadcasting commercial advertising or public promotion of goods, services and companies. End users located in a certain region receive the same advertisements, which are usually inserted in A/V programmes. + +It is recommended that a full-fledged IPTV TD support the following additional advertising services. + +##### **7.1.3.1 Targeted advertising** + +Targeted advertising can be defined as automatically matching and delivering relevant content to end users according to certain campaign objectives, the end user can only watch the advertisement without interaction. Targeted advertising usually takes advantage of the end user's profile including user preferences, residence, usage history, personal characteristics (e.g., accessibility) and usage environments (e.g., TDs, networks and natural environmental characteristics, etc.). The details concerning the end user's profile should be consulted in [ITU-T H.750]. + +##### **7.1.3.2 On-demand advertising** + +On-demand advertising delivers business directory information so that the end user can select and navigate through additional information or get additional services and benefits such as a coupon. The end user may press a button (or click on an icon) on the IPTV TD's remote in order to initiate a free A/V call to discuss or purchase a certain product. This type of advertisement is also called an interactive advertisement. + +To support this service, it is recommended that a full-fledged IPTV TD support the following capabilities: + +- provision of end user's preference setting, such as category, location, brand, etc.; +- provision of periodic advertisement delivering service once it has been requested by the end user; +- provision of PVR capability supported for selected advertisement; +- provision of telephony and video communication service. + +#### **7.1.4 Interactive services** + +Interactive services enable end users to send various types of requests and receive feedback with interactivity. According to different security requirements on user privacy, such as home address, credit card information, personal health condition and so on, interactive services may be classified into two types: + +1. Of no security concern. Interactive services for information collecting without user information, like reading newspapers, resident games, etc. +2. Security required. Interactive services that require personal user's information for the service capability, like online shopping, e-health, online games, etc. The details concerning the end user's profile may be consulted in [ITU-T H.750]. + +Because of the service complexity, the services listed hereafter cover both services with no security concern and aspects in certain service types that have security requirements. Instructions will be given in the service description. + +#### **7.1.4.1 Commercial service** + +The commercial service enables the end user to purchase goods and use financial services, such as banking, stocks, shopping, ticketing, auctions, etc. For example, a personal banking service enables + +the end user to view account balances, review past account activity, pay bills and transfer money between accounts via the IPTV TD. + +Since the commercial service is finance-related, it is recommended that a full-fledged IPTV TD provide high security with the following capabilities: + +- provision for protection of end user's privacy; +- provision for protection of end user's financial information, such as bank account, credit card, debit card, etc.; +- support of security software plug-in and multiple cryptographic algorithms; +- support of hardware-related protection such as one-time programming (OTP); +- provision for protection of end user's personal information. + +NOTE – If the commercial service provides browsing of general financial information on the stock market, currency exchange rate, etc., there is no security concern. + +#### **7.1.4.2 Entertainment service** + +The entertainment service is designed to provide content such as games, karaoke, lottery, blogs and photo albums for the end user's amusement. Games can be subdivided into single player and multi-player games, depending on the number of players. Moreover, games can be classified into network games and non-network games, depending on the level of interaction. In the case of a photo album, the end users can view pictures they uploaded or transfer them to other people's IPTV TDs, mobile phones, etc. + +To support these services, it is recommended that a full-fledged IPTV TD support the following capabilities: + +- provision of input interfaces for joysticks, microphone, etc.; +- provision of output interfaces for A/V enhancement devices such as an amplifier; +- provision of A/V capturing. + +NOTE – If the entertainment service is only a non-network game, landscape photos, etc., and there is no personal user information such as details concerning the user's account, password and personal photos, etc., there is no security concern. + +##### **7.1.4.3 Learning service** + +The learning service is instructional services for delivering educational content, e.g., languages, financial skills, etc., to students who are physically located in different geographic areas. Teachers and students can communicate in real time (i.e., both present at the same time) and/or non-real time (i.e., at a time of their own decision using a messaging capability) through video, audio, pictures and text, etc. + +To support these services, it is recommended that a full-fledged IPTV TD support the following capabilities: + +- provision of interfaces for input devices, such as keyboard, mouse, etc.; +- provision of A/V capturing/encoding; +- provision of protocols for transmission of A/V, such as RTP/RTCP [b-IETF RFC 3550] and/or DASH [b-ISO/IEC 23009-1]; +- provision of protocols for multi-stream of linear TV with trick mode; +- provision of multi-stream decoding; +- provision of content protection for copyright. + +NOTE – If no personal information and educational content copyright are concerned, there is no security concern. + +##### **7.1.4.4 Medical service** + +The medical service provides connection between doctors and patients who are in different geographic areas. Doctors can perform health monitoring, remote diagnosis, remote consultation, remote medical examination, remote medical education, etc. + +Since the medical service is in relation with the end users' private information, it is recommended that a full-fledged IPTV TD provide high-level security with the following capabilities: + +- provision of A/V capturing/encoding for remote video diagnosis; +- provision of peripheral devices for medical diagnosis, like electronic blood pressure meter; +- provision of convenient peripheral devices for message input, such as keyboard, mouse, etc. + +NOTE – If the medical service is restricted to giving only medical instruction and does not enter into the user's personal health status, there is no security concern. + +#### **7.1.5 Communication service** + +Communication is the process of transferring information from one source to another. The communication service enables the end user to exchange information such as voice, video and data with other end users. It is a key example of the converged services of telecommunication and broadcasting that compound phone services (VoIP, videophone, multiple videoconference, etc.) and Internet-based communication services (instant messaging (IM), short messaging service, e-mail, the web, etc.) with television services. + +Communication services which require high capabilities of a full-fledged IPTV TD, e.g., video conferencing, may not be supported sufficiently by other kinds of IPTV TDs such as an STB or the mobile phone. + +##### **7.1.5.1 Messaging service** + +The messaging service is one of the communication services that offers telecommunication between individual users. The messaging service may be immediate (e.g., IM) or of a store-and-forward type (e.g., e-mail and voicemail). + +To support the messaging service, it is recommended that the following capabilities be provided by a full-fledged IPTV TD: + +- provision of convenient peripheral devices for message input, such as keyboard, mouse, etc.; +- provision of audio capture/encoding for voicemail; +- provision of speech recognition to simplify text input. + +#### **7.1.5.2 Telephony service** + +The telephony service is a general telephone call service using IPTV TD. One example is VoIP which uses the Internet to transmit digitized voice data packets. With this service, the end user may select another end user from the address book listed by the IPTV TD or dial a direct phone number with the remote controller to create an IP-based communication session to transmit and receive sound only (most commonly the human voice), without knowing if the called party is via PSTN, mobile or the IP network. + +To support the telephony service, it is recommended that a full-fledged IPTV TD provide the following capabilities: + +- provision of TD-PD interface to support a peripheral device to transfer the sound information through a non-IP-based connection; +- provision of audio digitalization for IP-based transmission. + +#### **7.1.5.3 Video communication service** + +The video communication service provides bidirectional symmetric real-time transfer of motion video and voice. These services may include video telephony (a kind of telephony with the video stream data), the multi-party conference call (a telephone call in which more than two users take part) and the videoconference (a service providing real-time transmission of motion video, text and voice between end users in two or more locations). + +To support the video communication service, it is recommended that a full-fledged IPTV TD provide the following capabilities: + +- provision of convenient peripheral devices for message input, such as keyboard, mouse, etc.; +- provision of A/V capturing/encoding; +- audio-video synchronization with best effort delivery; +- provision of multi-channel decoding for video conferencing. + +#### **7.1.6 Personal video recorder (PVR) service** + +It is recommended that the IPTV TD be capable of supporting the PVR service so that end users can retrieve a recording and play it back later. PVR services may include the following capabilities: + +- scheduling recordings; +- displaying a list of stored programmes/content and a list of upcoming recordings; +- ranking recordings according to priority; +- playing back/erasing stored programmes/content; +- copying stored programmes/content to removable or external local storage devices. + +Such services are required to ensure that copyright enforcement mechanisms are preserved. Relevant security issues may be consulted in [ITU-T H.622.1] and [ITU-T X.1191]. + +An advanced PVR will be able to support the personal channel service at the PVR. In such a service, the PVR generates the end user's own preview schedule customized according to his/her preferences or lifestyle. + +##### **7.1.6.1 Client PVR (cPVR)** + +In the case of cPVR, the IPTV TD contains (or is directly connected to) some sort of storage buffer or memory, such as a hard disk drive, removable media, or solid state memory (e.g., flash, RAM, etc.). The end user can interact with the graphic user interface (GUI) in order to schedule, modify, playback and erase local recordings. + +To support the cPVR service, it is recommended that the following capabilities be supported by a full-fledged IPTV TD: + +- provision of programmes/content recorded to removable or external local storage devices; +- provision to play back stored programmes/content with trick mode functionality and programme/content erasing; +- provision of copyright enforcement mechanisms. + +##### **7.1.6.2 Network PVR (nPVR)** + +There might be some cases in which it is not appropriate to save the content locally. For example, if the IPTV TD has a hard drive of limited size, the nPVR is more appropriate. + +The end user will not be able to recognize any difference between using cPVR or nPVR. The PVR service should function identically, the only difference being the location of the storage device. + +To support the nPVR service, it is recommended that the following capabilities be supported by a full-fledged IPTV TD: + +- provision of local storage occupation reports to the nPVR server; +- that preference be given to the storage file format of the end user side as a file of directly captured raw data are transmitted as data; +- automatic retrieval of the network-recorded video once the local storage space is free, with user permission. + +##### **7.1.6.3 Distributed PVR (dPVR)** + +In the case of the distributed PVR, all content is stored within the home network on multiple cPVR services or within a combination of multiple nPVR and cPVR services, with interaction for scheduling, modifying, playback, erasing and recording. + +To support the dPVR service, it is recommended that the following capabilities be supported by IPTV TD: + +- that preference be given to the storage file format of the end user side as a file of directly captured raw data are transmitted as data; +- that preference be given to the network access methods in the case of the dPVR, refer to [ITU-T H.770]. + +### **7.1.7 Audience measurement information** + +Audience measurement information is used for the end user's convenience when watching IPTV content. For example, advertisement services can refer to this information to provide appropriate advertising. The information consists of the channel numbers before and after a channel change, time of the change and user information (e.g., a unique identifier). With the end user's permission, information can be collected by the IPTV TD and the IPTV network can be used to upload the collected information to the relevant server-side applications. + +Refer to [ITU-T X.1191] and [ITU-R BT.2052] for discussions of privacy issues relating to audience measurement information. + +Refer to the [ITU-T H.741.X]-series for the overview and specifications for audience measurement. + +#### **7.1.8 Internet service** + +The Internet service is a service in which the end user can access the Internet with a web-browsing agent installed in the IPTV TD. The web-browsing agent may include e-mail, web browser, instant messaging, really simple syndication (RSS) news, etc. + +To support the Internet service, it is recommended that a full-fledged IPTV TD provide the following capabilities: + +- provision of convenient peripheral devices for message input, such as keyboard, mouse, etc.; +- provision of Internet software and applications such as IM, mail client, etc. + +#### **7.1.9 Application store service** + +The application store service is an online digital application distribution service that allows end users to browse and download applications onto the terminal device. Depending on the application, they are available either for free or at a cost. The applications, which may be IPTV widgets implemented with [b-ITU-T H.IPTV-Widget], can be downloaded directly to a target device, or downloaded onto a personal computer. The application may be provided by a service provider or third-party developers with the software development kit/native development kit (SDK/NDK) supported by the TD, according to its application framework, see clause 7.2.1. + +To support the application store service, it is recommended that the following capabilities be supported by a full-fledged IPTV TD: + +- provision of SDK/NDK for application development, see clause 7.2.1; +- provision of application download, installation, execution and uninstallation. + +#### **7.1.10 Multi-device interactive service** + +The multi-device interactive service provides the user with a different IPTV service-consuming experience over one or more other TDs. Typically, the multi-device interactive service may include content sharing, content transferring, coupled content playing, etc. Moreover, some devices may control media playing on the other device, or transfer inputted text to the other device. In a multi-device environment, the roles defined for the device determine which capability the device should support. + +To support the multi-device service, it is recommended that the following capabilities be supported by a full-fledged IPTV TD: + +- provision of the ability to send announcements to all connected terminal devices for claiming its functional roles; +- provision of devices discovery and inter-connection set-up; +- interworking with different types of TDs, e.g., performing services defined in [b-H.IPTV-TDES.5]. + +## **7.2 Features of full-fledged IPTV TD** + +#### **7.2.1 Application framework** + +The application framework is the functionality to support the end user in installing, un-installing, running and closing the applications sanctioned (signed) by the service providers. For a possible implementation of the application framework, refer to [ITU-T H.730]. + +Value-added IPTV services can be provided by supporting various supplementary IPTV services from third-party application providers or a full-fledged IPTV TD. Through SDK/NDK based on an application framework, a full-fledged IPTV TD enables IPTV users to use an application store service with various supplementary IPTV services effectively. It is recommended that the device support the following features: + +- supplementary IPTV service using, e.g., [b-ITU-T H.IPTV-Widget], etc.; +- application installation, un-installation, running and stop; +- application life-cycle management; +- web-based applications using [ITU-T H.761], [ITU-T H.762], [ITU-T H.763.1] and [ITU-T H.764]. + +#### **7.2.2 Audience measurement** + +The audience measurement of the IPTV TD is used to collect information while the end user's TV-watching behaviour is monitored with user permission. The IPTV network can be used to upload the collected information to the relevant server-side applications. A detailed description on audience measurement is found in the [ITU-T H.741]-series. + +It is recommended that a full-fledged IPTV TD support an audience measurement function (end-user measurement function) to acquire the following audience measurement information: + +- end-user permission information; +- the configuration information of the measurement object configuration function; +- the delivery mechanism information; + +- end-user measurement function update information. + +It is recommended that a full-fledged IPTV TD support an audience measurement function (end-user measurement function) to acquire the following metadata information: + +- in the linear TV service, audience measurement information consisting of the channel numbers before and after a channel change, time of the change, and user information (e.g., a unique Identifier); +- in the push VoD service, audience measurement information which may consist of the content identifier, start time, end time, times of replay, etc.; +- in the PVR service, audience measurement information which may consist of the content identifier, start time, end time, times of replay, etc. + +In the personal broadcast service, audience measurement information consists of the content identifier, start time, end time, etc. + +#### 7.2.3 Codec and display + +##### 7.2.3.1 Codec + +The codecs functional entity is responsible for: + +- decoding the compressed video and audio streams; +- decoding the multiple video and audio streams, e.g., for linear TV and on-demand with multiple-view service or PIP mode; +- decoding textual data, e.g., closed caption; +- decoding other multimedia content, e.g., graphics; +- encoding textual data, audio/video streams, and other multimedia content. + +It is recommended that full-fledged IPTV TD have capabilities to encode and process IPTV multimedia contents using high-capacity storage, high-performance processor, and easy-to-use peripheral devices. For example, IPTV contents may be encoded by a personal computer to provide a personal IPTV broadcast service, one of the advanced IPTV services or to be made suitable for other IPTV TDs such as the mobile phone. However, encoding and distribution of IPTV contents are required to follow a contents protection policy. + +##### 7.2.3.2 Picture-in-picture (PIP) display + +A full-fledged IPTV TD supports not only common video display but also picture-in-picture (PIP) display. In PIP mode, the display screen, which is composed of two or more screens windows, provides the capability to display different media content in separate screens: + +- a full-screen display mode is recommended for the main screen; and a window display mode is recommended for the secondary screen(s); +- it is recommended that the main screen and secondary screen be able to present two different output contents of ITF inside a full-fledged IPTV TD and to switch between each other. It is recommended that the secondary screen(s) be able to be shifted, resized and switched off by the end user within the main screen display area; +- it is recommended that the main screen support HD/SD video decoding and audio decoding. It is recommended that the secondary screen support SD video decoding. + +#### 7.2.4 Local storage + +It is recommended that a full-fledged IPTV TD support local storage. The end user may view the multimedia content downloaded from the network, such as a movie, cPVR, dPVR, music, picture, applications, etc. For A/V content, it is also recommended that a full-fledged IPTV TD support the trick mode such as pause, fast forward, fast rewind, etc. + +#### **7.2.5 Accessories** + +To support interactive services, it is recommended that a full-fledged IPTV TD support peripheral devices to transfer the sound information through a non-IP-based connection. + +#### **7.2.6 Network attachment and service discovery** + +This is the process which enables end users to connect to a particular service and to consume linear TV with trick mode or VoD service, after connecting their IPTV TD to the network. For details of the service discovery, refer to [ITU-T H.770]. + +Via the provisioning operation including network attachment, the IPTV TD automatically obtains the initial information for consumption. When the process is finished, end users can have access to all the IPTV services available. If a promotional linear TV channel is also provided on the network, then such a service is also obtainable. + +The detailed information on "terminal device attachment and initialization", "service provider description entry points" and "service provider discovery and service attachment" is the same as in clause 7.2.1 in [ITU-T H.721] on network attachment and service discovery. + +### **7.2.7 Security** + +A full-fledged IPTV TD is required to support the "service security items" and "content protection items", which are fully described in clause 7.2.2 in [ITU-T H.721] on security, after establishing the network layer connections to receive IPTV services. + +### **7.2.8 Privacy** + +To take into account the cases where the ownership of IPTV TD is transferred to a different end user or is discarded, the IPTV TD is required to have the capability to initialize and delete the private information stored in the non-volatile random access memory (NVRAM), such as flash memory and local storage. + +Moreover, a full-fledged IPTV TD is required to have the capability to delete the configuration involving private information set up by the end user and to initialize to the factory setting. + +It is recommended to ensure that this capability cannot be mistakenly operated and unintentionally activated (e.g., by a limitation for remote operation by the end user). + +#### **7.2.9 Quality of service (QoS)** + +It is recommended that a full-fledged IPTV TD support not only the QoS guarantee as described in clause 7.2.4 in [ITU-T H.721] but also support automatic repeat query (ARQ) and forward error correction (FEC) with an appropriate consideration of the quality of the communication network, to ensure a sustainable and stable delivery of streamed content. + +#### **7.2.10 SDK/NDK** + +Public SDK and/or NDK for applications, which may refer to [ITU-T H.730], are provided by a full-fledged IPTV TD so that third-party developers can develop applications. + +#### **7.2.11 Multi-device interactive function** + +It is recommended that a full-fledged IPTV TD be powerful enough to act as a media centric device. It will play the full functional role when it supports multi-device interactive services. The following functions are recommended: + +- media server: provides the media server and service aggregation capability. For example, this TD may provide the function of media detection, media management, media streaming (push or pull), and media synchronization, etc. It may also provide the function of device management, content protection, security, and user interface (UI) for remote access; + +- media player: provides the capability of media playing for other displayer; +- media renderer: provides the capability of media rendering for other displayer; +- media controller: provides the capability of media control and UI for the control panel. + +## 8 Full-fledged IPTV TD functional architecture + +The full-fledged IPTV TD functional architecture is shown in Figure 8-1. + +![Figure 8-1 – Full-fledged IPTV TD functional architecture diagram. The diagram shows a hierarchical structure of IPTV terminal functions. At the top is a dashed box labeled 'IPTV terminal functions'. Inside, from top to bottom, are: 'Application client functions' (orange box with SADS client, IPTV application client, Supplementary IPTV service client, and Application management functional block), 'SCAP client functions' (green box with Service protection, Content protection, and Application protection functional blocks), and 'Content delivery client functions' (purple box). The 'Content delivery client functions' box contains 'Media client functions' (blue box with Demux/Mux, Storage, Codecs, Media control, and Metadata management), a 'Broadcast demux' block, a 'Multi-device media interactive functional block', and three client functional blocks: 'Unicast content delivery', 'Multicast content delivery', and 'Error recovery client'. A vertical blue bar on the left, labeled 'Accessories management' and 'Terminal device management functions', connects to various functional blocks. At the bottom, outside the main dashed box, is a yellow box labeled 'IPTV terminal transport functions' containing a 'Network attachment client' block. A small label 'H.722(14)_F8-1' is in the bottom right corner.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 8-1 – Full-fledged IPTV TD functional architecture diagram. The diagram shows a hierarchical structure of IPTV terminal functions. At the top is a dashed box labeled 'IPTV terminal functions'. Inside, from top to bottom, are: 'Application client functions' (orange box with SADS client, IPTV application client, Supplementary IPTV service client, and Application management functional block), 'SCAP client functions' (green box with Service protection, Content protection, and Application protection functional blocks), and 'Content delivery client functions' (purple box). The 'Content delivery client functions' box contains 'Media client functions' (blue box with Demux/Mux, Storage, Codecs, Media control, and Metadata management), a 'Broadcast demux' block, a 'Multi-device media interactive functional block', and three client functional blocks: 'Unicast content delivery', 'Multicast content delivery', and 'Error recovery client'. A vertical blue bar on the left, labeled 'Accessories management' and 'Terminal device management functions', connects to various functional blocks. At the bottom, outside the main dashed box, is a yellow box labeled 'IPTV terminal transport functions' containing a 'Network attachment client' block. A small label 'H.722(14)\_F8-1' is in the bottom right corner. + +Figure 8-1 – Full-fledged IPTV TD functional architecture + +## 9 Functional components of IPTV full-fledged terminal device + +### 9.1 Terminal transport functions + +The terminal transport functions are logical blocks that take in data such as video and audio data transmitted via IP packets. The communication interface, communication process, network attachment processing and service discovery procedure of a full-fledged IPTV TD are the same as the functions which are already defined in clause 9.1 "Terminal transport functions" of [ITU-T H.721]. + +## 9.2 Content delivery client functions + +The content delivery client functions receive and control the delivery of the content from the content delivery and storage functions. + +The broadcast demux, multicast content delivery client, unicast content delivery client and error recovery functional blocks of a full-fledged IPTV TD are the same as the functions which are already defined in clause 9.2 "Content delivery client functions" of [ITU-T H.721]. However, when acting as a media-centric device, it is recommended that the full-fledged IPTV TD include a multi-device media interactive function. + +### **9.2.1 Multi-device media interactive functional block** + +The multi-device media interactive functional block provides the media server and service aggregation capability such as media detection, management, rendering, streaming (push or pull), and synchronization and control functions. A full-fledged IPTV TD may act like a streamer but with more strict connection authentication and less connections. + +## **9.3 Media client functions** + +Media client functions receive contents from the content delivery client functions and process contents to the appropriate data formats so as to provide them to the output interface. The media control, demux/mux, codec, storage and metadata management functional blocks of full-fledged IPTV TD are the same as the functions which are already defined in clause 9.3 "Media client functions" of [ITU-T H.721]. + +## **9.4 Service, content and application protection (SCAP) client functions** + +The SCAP client functional entity is an entity that receives and manages rights and keys and that provides content keys and descrambling keys for content consumption. + +The service protection client and content protection client functions of a full-fledged IPTV TD are the same as the functions which are already defined in clause 9.4 of [ITU-T H.721] on SCP client functions. In order to support application store service, it is recommended that the full-fledged IPTV TD provide application protection. + +#### **9.4.1 Application protection client functional block** + +The application protection client with the newest CRL is required to establish a secure communication channel by mutual authentication with an SCAP server during the application downloading procedure. + +The application protection client is required to provide robust and mutual encryption to the application downloaded, e.g., a digital signature. Once the application is installed in an individual IPTV TD, a copy of this application cannot run on another IPTV TD. + +## **9.5 Application client functions** + +The application client functions of a full-fledged IPTV TD are the same as the functions which are already defined in clause 9.5 of [ITU-T H.721] on application client functions. In order to support the application store service, it is recommended that the supplementary IPTV service client functions be provided. + +### **9.5.1 Supplementary IPTV service client functions** + +The supplementary IPTV service client functions interact with the application store, which is a supplementary service for a full-fledged IPTV TD, to perform session management, service authorization and presentation of the application metadata. It is recommended that a full-fledged IPTV TD support not only the presentation of the application store but also the downloading, installation, execution and un-installation of the applications which are programmed with the SDK/NDK of the TD. + +## **9.6 Control client functions** + +In the case of next generation network (NGN) IPTV, the control client functional block can optionally support sessions for resource management with the resource and admission control function (RACF). The requirements of the control client functions are the same as for the functions which are already defined in clause 9.6 of [ITU-T H.721] on control client functions. + +## 9.7 Performance monitory client functions + +The performance monitory client functions monitor the status of a full-fledged IPTV TD, such as the occupancy rate of the central processing unit (CPU), RAM and flash, network speed, package loss, jitter, etc. + +## 9.8 Audience measurement client functions + +The audience measurement client functions collect information during viewing of the end user's TV-watching behaviour, with the user's permission, and upload the collected information to the relevant server-side applications. For details, refer to the *ITU-T H.741.x-series*. + +### 9.9 Terminal device management + +Remote management is closely related to this functional block. Since a full-fledged IPTV TD supports accessories such as the mobile telephone headset and microphone, it is recommended that the terminal device management support accessory management. + +# 10 Software architecture + +The diagram in Figure 10-1 presents the software architecture of a full-fledged IPTV TD. + +![Figure 10-1 – Full-fledged IPTV TD software architecture diagram](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +The diagram illustrates the software architecture of a full-fledged IPTV TD. It is organized into horizontal layers and vertical application blocks. + +**Layers (top to bottom):** + +- User experience and applications:** Contains 'Web-based IPTV application'. +- Application framework:** Contains 'SDK' and 'NDK'. +- Presentation engine layer:** Contains 'Presentation engine'. +- Service logic adaptation:** Contains 'Service components' (System manager, Media manager, Communication, Metadata, ...) and 'Application manager'. +- Resource abstraction layer (RAL):** A thin layer above the hardware. +- Resources (HW and SW):** The base layer. + +**Vertical Blocks:** On the right, 'Legacy IPTV application' and 'OS-based IPTV application' span multiple layers. + +**External Inputs (left side):** Arrows point from external blocks to internal layers: + + +- 'UE skin and customization' points to 'Web-based IPTV application'. +- 'Application framework' (red arrow) points to the SDK. +- 'Presentation engine layer' points to 'Presentation engine'. +- 'Service logic adaptation' points to 'Service components'. +- 'Resource abstraction layer' points to 'RAL'. + + The diagram is labeled *H.722(14)\_F10-1* at the bottom right. + +Figure 10-1 – Full-fledged IPTV TD software architecture diagram + +**Figure 10-1 – Full-fledged IPTV TD software architecture** + +### 10.1 Resource abstraction layer (RAL) + +The IPTV terminal middleware is hardware-agnostic. A specific RAL exists for each specific hardware and operating system – this provides the necessary interface to the lower layers (e.g., RAM, network access, hard drive, etc.). The RAL interface is designed so that device drivers can be written irrespective of the service logic adaptation layer. + +In general, some basic functionalities to support the IPTV service logic adaption layer are implemented by hardware in the IPTV TD-basic model, but these functional entities can optionally be implemented by software in a full-fledged IPTV TD. Therefore, a full-fledged IPTV TD has to implement these functionalities through software. + +### 10.1.1 Media decoder + +The media decoder of a full-fledged IPTV TD can optionally be implemented through software to support the A/V decoding functionality. It can support all the decoders that are required for IPTV + +services and can install, uninstall, or combine any of them if necessary. It may provide the APIs to the media management component for trick mode implementation. + +### **10.1.2 Output display** + +In a full-fledged IPTV TD, the display graphical device may be implemented by software and a device driver which may be called an "output display component". This component receives the output display signal from the media decoder and may implement multiple-layer control including overlap, blending, position and scaling. + +### **10.1.3 Input device control** + +Since it is recommended that a full-fledged IPTV TD support multiple input devices, it is recommended that the software input device control component in this layer be implemented to support the IPTV services requirements from the upper layers. + +### **10.2 Service logic adaptation layer** + +The service logic adaptation layer is made of service components. The service components are pure native components that offer functionalities common to all middleware implementations (e.g., service selection and presentation, service information management, PVR, and security system). They are used and enriched by the application services in order to simplify the development of the service components and applications above it. + +The definition and the scope of services depend on the concrete functionalities deployed in the IPTV service system. + +Nevertheless, some service components can be defined that are generic in nature: + +- system and resource management component; +- media management component; +- communication component; +- security component; +- metadata access component; +- user interaction component. + +All these components can optionally use the functions available on the network. + +## **10.3 Presentation engine layer** + +The presentation engine layer may include various engines along with a set of high-level services. This layer is built on top of the service logic adaptation layer. + +## **10.4 User experience skin and customization** + +The applications are either downloaded or resident. In particular, an application is powered by a presentation engine, such as multimedia application framework (MAFR). An application can either have full or restricted access to the presentation engine layer features. Moreover, some applications may directly access the service logic adaptation layer without using a presentation engine. + +# **11 Physical interfaces** + +The physical interfaces of a full-fledged IPTV TD are described in this clause to meet the requirement of services and features listed in clause 7.2. Figure 11-1 illustrates the physical interfaces of the full-fledged IPTV TD. + +![Diagram of Full-fledged IPTV TD interfaces showing connections to various networks and devices.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +The diagram illustrates the interfaces of a central 'IPTV full-fledged terminal device' (a large blue rectangle). It shows connections to several external entities: + +- Top Left:** An 'IPTV network (e.g., NGN)' cloud is connected to an 'RG' (Router/Gateway) box via a double-headed arrow labeled 'NW-TD-1'. The 'RG' box is connected to a 'Home network' cloud via a double-headed arrow. The 'Home network' cloud is connected to the central device via a double-headed arrow labeled 'TD-HN'. Above the 'IPTV network' cloud, another double-headed arrow labeled 'NW-TD-2' points to the central device. +- Bottom Left:** A 'Broadcast network (e.g., satellite)' cloud is connected to the central device via a double-headed arrow labeled 'BC-TD'. +- Bottom:** Three components are connected to the bottom of the central device: + - 'External storage' (a box) via a double-headed arrow labeled 'TD-PD'. + - 'Media scrambler/descrambler' (a box) via a double-headed arrow labeled 'TD-PD'. + - 'Removable security' (a small icon) via a double-headed arrow labeled 'TD-SM'. +- Right Side:** Three components are connected to the right side of the central device: + - A microphone icon via a double-headed arrow labeled 'TD-PD'. + - 'User interface (e.g., remote control)' (a box) via a double-headed arrow labeled 'TD-PD'. + - A television icon via a double-headed arrow labeled 'TD-OD'. + +H.722(14)\_F 11-1 + +Diagram of Full-fledged IPTV TD interfaces showing connections to various networks and devices. + +**Figure 11-1 – Full-fledged IPTV TD interfaces** + +## 11.1 Input interface + +The input interface of the full-fledged IPTV TD is to support user interaction. It is recommended that the interfaces support not only peripheral devices such as the keyboard, mouse, etc., via actual physical interfaces, but also via a virtual control software application running in a tablet or smart phone. An example is found in [b-H.IPTV-TDES.5]. + +### 11.1.1 Reset button + +It is recommended that the full-fledged IPTV TD support a reset button to manually resolve its hang-up status. + +### 11.1.2 Remote controller + +It is recommended that the full-fledged IPTV TD support a remote controller. The details are outside the scope of this Recommendation. + +#### 11.1.3 Keyboard and mouse + +It is recommended that the full-fledged IPTV TD support a keyboard and mouse for convenient text input and control. The details are outside the scope of this Recommendation. + +#### 11.1.4 Microphone + +It is recommended that the full-fledged IPTV TD support a microphone for voice input. The details are outside the scope of this Recommendation. + +#### 11.1.5 Camera + +It is recommended that the full-fledged IPTV TD support a camera for video communication and other necessary services. The details are outside the scope of this Recommendation. + +#### 11.1.6 Multi-screen interaction devices + +It is recommended that the full-fledged IPTV TD support an IP-based connection from other devices like a smart phone or tablet with a virtual control software application for text input or + +controller simulation. The details are outside the scope of this Recommendation; examples can be found in [b-H.IPTV-TDES.5]. + +## **11.2 Output interface** + +If the full-fledged IPTV TD has a digital visual interface (DVI) or a high-definition multimedia interface, and when it outputs content with copy control or protection, it is required to provide appropriate protection according to the high-definition content protection (HDCP) specification. The details of copy control and output control are outside the scope of this Recommendation. + +#### **11.2.1 RGB analogue interface** + +The full-fledged IPTV TD can optionally support an RGB analogue interface. + +The full-fledged IPTV TD can optionally support a video graphic array (VGA) interface and a digital visual interface (DVI) interface with analogue out. + +### **11.2.2 Digital video interface** + +The full-fledged IPTV TD can optionally support a DVI interface. + +### **11.2.3 Digital audio interface** + +The full-fledged IPTV TD can optionally support a digital audio interface. + +### **11.2.4 High-definition multimedia interface** + +It is recommended that the full-fledged IPTV TD support a high-definition multimedia interface. + +#### **11.2.5 Headset output interface** + +The full-fledged IPTV TD can optionally support a headset audio output interface. + +## **11.3 External data access interface** + +It is recommended that the full-fledged IPTV TD support removable external storage devices. If the contents in the removable storage require copy control or protection, it is required to provide appropriate protection according to the HDCP specification. The details of copy control and output control are outside the scope of this Recommendation. + +## **11.4 Network access interface** + +It is recommended that the full-fledged IPTV TD support wired or wireless data connection for IP-based data transmission. + +It is recommended that the full-fledged IPTV TD support a personal area network (PAN) interface, refer to [b-ITU-T H.810]. + +# Bibliography + +- [b-ITU-T H.810] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T Y-Sup.5] Recommendation ITU-T Y.1900-series (2008), *Supplement on IPTV service use cases*. +- [b-H.IPTV-TDES.5] Draft ITU-T H.IPTV-TDES.5 (2012), *IPTV Terminal Device: Interworking-enabled model of multiple devices*. +<> +- [b-ITU-T H.IPTV-Widget] Draft ITU-T H.IPTV-Widget (2012), *IPTV widget service*. +<> +- [b-IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- [b-ISO/IEC 23009-1] ISO/IEC 23009-1:2012, *Information technology – Dynamic adaptive streaming over HTTP (DASH) – Part 1: Media presentation description and segment formats*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78e52cef39b2d04473d186541f25c3c1cad0325c --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51c7c80b2ae38e071918412144e11b7da7c1b9b31003a3a889da869c52372846 +size 51497 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5caea944d3e1b5f032df3eeb04204676aaf0d55 --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5691f78d53a1e84929a18a93eee0fe6c82f22a08ff44723e7850512f49e82058 +size 38742 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88f3040f0827ceccf897bc0b01b5e56dbc29968a --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeaf39e8078d0196299d66539d6e691a9176ae49ae357ec1f2339c9a21d0d4dc +size 147883 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6875427e73b02b5582bf23a600275980e5c7a11 --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7234f038695e71bfc2be684b3c920fd921d885022b8cf8b5cca8121af398cb50 +size 43357 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96cb9539da49ca719d4f1b0f615def57f8e64a8b --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a484d4424065f59dd1610a45aaf829ce05118afcb5877c75210660d813a61dd +size 38187 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21ded58923e1dd349166d2f41772f938fab13d9d --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a503a83309108715c2ce227ca9b8e16c1edb4e1167d834c9fd69c1b23376115 +size 38336 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5295e5f3b359f1cb7eb589492906ba42372ce460 --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b606969d95fd7f6efdad13ce9473bd814fc626737a78b4ace581548907b98c87 +size 7056 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d764bd7d5b936f399656cbab86735f6b50141ed --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:208cfe32655e394cfe03d66452494f550106dfce4956ed058ed94031550df3b4 +size 65075 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0441cac9ecf35a3c21455bb7a1d7bc58478d4bdc --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38cb539af87aa310c9b3a9035270a847ae1b309f75fb75999fd663befcce0ee4 +size 45813 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..636a02ff3433b7f53c3b6cf8b146817642a35cd9 --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2506092438ce68e91e5eaac2571f21ac1ad87505715cefe5dbf84e9fa31f7bbd +size 58425 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..248e601573bc3c56817415a0d06304899a9b8c46 --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19cba762f06e93945aac37855edffa8b14217f775f613183209d8df85c53095c +size 86322 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/H/T-REC-H.723-201607-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cfb84384af4f339b8b498263b3a58c296496680 --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:889e5fd5c4838fab0a8bc09501c13a4dd2826263ae101bdacf388f129af517b5 +size 141435 diff --git a/marked/H/T-REC-H.723-201607-I_PDF-E/raw.md b/marked/H/T-REC-H.723-201607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..958b3e0c16ce9d17b87f644ba6634526ae8806c1 --- /dev/null +++ b/marked/H/T-REC-H.723-201607-I_PDF-E/raw.md @@ -0,0 +1,1034 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.723** + +(07/2016) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +IPTV terminal devices + +--- + +**IPTV terminal device: Mobile model** + +Recommendation ITU-T H.723 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue, with "ITU" in a larger, bold font above it. + +ITU logo + +International +Telecommunication +Union + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.723 + +# IPTV terminal device: Mobile model + +## Summary + +Recommendation ITU-T H.723 describes the functionalities of the mobile model Internet protocol television (IPTV) terminal device (TD) for IPTV basic services defined in Recommendation ITU-T H.720. This Recommendation describes the required aspects on requirements, capabilities, architecture, and interfaces of mobile model IPTV TD that can consume IPTV services irrespective of changes of the location or technical environment of mobile device. The meaning of mobile model IPTV TD is that the IPTV terminal function (ITF) is implemented on the mobile device such as a smart phone or smart pad, and is connected to the IPTV service provider through wireless or mobile access networks. The quality of IPTV service depends on such parameters as network conditions and terminal capability, etc. The mobile model IPTV TD can access an IPTV service provider via wireless networks or mobile access network in the home as well as out of home environments. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.723 | 2016-07-14 | 16 | 11.1002/1000/12909 | + +## Keywords + +IPTV, IPTV terminal device, mobile IPTV, mobile model. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|----------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Overview..... | 5 | +| 7 | Services and key features of mobile model IPTV terminal device ..... | 7 | +| 7.1 | Services for the IPTV TD mobile model..... | 7 | +| 7.2 | Features of the IPTV TD mobile model..... | 9 | +| 8 | Functional architecture of IPTV terminal device (mobile model)..... | 11 | +| 9 | Specific requirements for mobile model IPTV TD ..... | 13 | +| 9.1 | Functional requirements of terminal transport functions ..... | 14 | +| 9.2 | Functional requirements of content delivery client functions ..... | 14 | +| 9.3 | Functional requirements of media client functions ..... | 15 | +| 9.4 | Functional requirements of control client functional block ..... | 15 | +| 9.5 | Functional requirements of SCP client functions..... | 15 | +| 9.6 | Functional requirements of performance monitoring functions..... | 16 | +| 9.7 | Functional requirements of terminal device management functions..... | 16 | +| 9.8 | Functional requirements of application client functions ..... | 16 | +| 10 | Interfaces for mobile model IPTV terminal device ..... | 16 | +| 10.1 | Network interface ..... | 16 | +| 10.2 | User input interface ..... | 17 | +| 10.3 | Output interface ..... | 17 | +| 10.4 | Peripheral device interface ..... | 17 | +| 10.5 | Security module interface..... | 18 | +| | Annex A – General requirements for mobile IPTV services ..... | 19 | +| | Appendix I – QoS and performance ..... | 20 | +| I.1 | Quality of service ..... | 20 | +| I.2 | Quality and performance assessment ..... | 21 | +| I.3 | Quality and performance monitoring ..... | 22 | +| | Appendix II – Example use cases and service scenarios ..... | 23 | +| II.1 | Linear TV service with terminal mobility (horizontal handover) ..... | 23 | +| II.2 | IPTV broadcast service with personal mobility ..... | 23 | +| II.3 | VoD with terminal mobility (vertical handover)..... | 24 | +| II.4 | Three-screen service with contents sharing..... | 25 | + +| | Page | +|-------------------------------------------------------|-------------| +| II.5 Three-screen service with service mobility ..... | 26 | +| II.6 Location based information service..... | 27 | +| Bibliography..... | 29 | + +# Recommendation ITU-T H.723 + +## IPTV terminal device: Mobile model + +## 1 Scope + +This Recommendation describes and specifies the functionalities of the mobile model Internet protocol television (IPTV) terminal device (TD) for IPTV basic services defined in [ITU-T H.720]. This Recommendation describes the required aspects on requirements, capabilities, architecture, and interfaces of mobile model IPTV TD that can consume IPTV services irrespective of changes of the location or technical environment of the mobile device. In mobile model IPTV TD, the IPTV terminal function (ITF) is implemented on mobile devices such as smart phones or tablets, and is connected to the IPTV service provider through wireless or mobile access networks. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this document. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this document are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.701] Recommendation ITU-T H.701 (2009), *Content delivery error recovery for IPTV services*. +- [ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems*. +- [ITU-T H.721] Recommendation ITU-T H.721 (2015), *IPTV terminal devices: Basic model*. +- [ITU-T H.722] Recommendation ITU-T H.722 (2014), *IPTV terminal device: Full-fledged model*. +- [ITU-T H.770] Recommendation ITU-T H.770 (2015), *Mechanisms for service discovery and selection for IPTV services*. +- [ITU-T X.1191] Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects*. +- [ITU-T Y.1901] Recommendation ITU-T Y.1901 (2008), *Requirements for the support of IPTV services*. +- [ITU-T Y.1903] Recommendation ITU-T Y.1903 (2014), *Functional requirements of mobile IPTV*. +- [ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 captions** [ITU-T Y.1901]: Captions provide a real-time on-screen transcript of the dialogue as well as any sound effects. + +NOTE – This service can be provided by means of either textual or graphical supplementary content. The captions and the dialogue are usually in the same language. The service is primarily to assist users having difficulty hearing the sound. Ideally, users may have some control over the position and size of the presentation. Different speakers are distinguished, usually by different colours. + +**3.1.2 generalized mobility** [b-ITU-T Y.2001]: The ability for the user or other mobile entities to communicate and access services irrespective of changes of the location or technical environment. The degree of service availability may depend on several factors including the Access Network capabilities, service level agreements between the user's home network and the visited network (if applicable), etc. Mobility includes the ability of telecommunication with or without service continuity. + +**3.1.3 IPTV end system** [ITU-T Y.1901]: A single or set of consumer devices that support IPTV Services (e.g., delivery network gateway, display). + +**3.1.4 IPTV terminal device (TD)** [ITU-T Y.1901]: A terminal device which has ITF functionality, e.g., a STB. + +**3.1.5 IPTV terminal function (ITF)** [ITU-T Y.1901]: The end-user function(s) associated with a) receiving and responding to network control channel messages regarding session set-up, maintenance, and teardown, and b) receiving the content of an IP transport from the network and rendering. + +**3.1.6 linear TV** [ITU-T Y.1901]: A television service in which a continuous stream flows in real time from the service provider to the terminal device and where the user cannot control the temporal order in which contents are viewed. + +**3.1.7 mobile IPTV** [ITU-T Y.1903]: An application of IPTV as specified in [ITU-T Y.1901]. It applies to where the IPTV terminal device is connected to the IPTV Service Provider via an IPTV-enabled mobile network. It must be able to communicate and access services irrespective of changes of the location or technical environment. + +NOTE – There are multiple possible levels of mobility, from nomadism, where IPTV service is resumed only after the move is complete, to full mobility, where IPTV service is continuous throughout the movement. + +**3.1.8 mobile network** [b-ITU-T Q.1762]: A network that provides wireless access to its services and supports mobility. + +**3.1.9 nomadism** [b-ITU-T Q.1761]: Ability of the user to change his network access point after moving; when changing the network access point, the user's service session is completely stopped and then started again, i.e., there is no handover possible. It is assumed that the normal usage pattern is that users shutdown their service session before moving to another access point or changing terminal. This is the mobility alluded to in the case of fixed mobile convergence. + +**3.1.10 personal mobility** [b-ITU-T Q.1761]: Ability of a user to access telecommunication services at any terminal on the basis of a personal identifier, and the capability of the network to provide those services according to the user's service profile. Note that personal mobility involves the network capability to locate the terminal associated with the user for the purposes of addressing, routing and charging of the user's calls. + +**3.1.11 service mobility** [b-ITU-T H.510]: The ability of a user to use the particular (subscribed) service irrespective of the location of the user and the terminal that is used for that purpose. + +**3.1.12 sign language interpretation** [ITU-T Y.1901]: A video service showing an interpreter who uses hand gestures and facial expression to convey the main audio content and dialogue to sign language and lip readers. + +NOTE – This service comes in the form of supplementary video content, usually smaller in image size to that the main video content. Ideally the user can control the position, size and background properties (solid or + +transparent and the colour, if solid). It is of sufficient temporal and spatial quality to enable sign reading and lip reading. + +**3.1.13 subtitles** [ITU-T Y.1901]: Subtitles provide a real-time on-screen transcript of dialogue for the purpose of language translation or to clarify speech that is unclear. + +NOTE – This service can be provided by means of either textual or graphical supplementary content. The subtitles and the dialogue are usually in different languages. The assumed audience for subtitling is hearing people who do not understand the language of the dialogue. + +**3.1.14 terminal device (TD)** [ITU-T Y.1901]: An end-user device which typically presents and/or processes the content, such as a personal computer, a computer peripheral, a network appliance, a mobile device, a TV set, a monitor, a VoIP terminal or an audio-visual media player. + +**3.1.15 terminal mobility** [b-ITU-T Q.1761]: Ability of a terminal to access telecommunication services from different locations and while in motion, and the capability of the network to identify and locate that terminal. + +**3.1.16 video-on-demand (VoD)** [ITU-T Y.1901]: A service in which the end-user can , on demand, select and view a video content and where the end-user can control the temporal order in which the video content is viewed (e.g., the ability to start the viewing, pause, fast forward, rewind, etc.). + +**3.1.17 wireless network characteristics** [ITU-T Y.1901]: The characteristics of a wireless network expressed in terms of the current available bandwidth, packet loss and possibly other wireless network information parameters for a specific wireless link type e.g., WLAN, cellular, WPAN or WMAN. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 link characteristics:** Characteristics of the communication path such as bandwidth, delay, latency, error rate, etc. + +**3.2.2 mobile model IPTV TD:** An IPTV terminal device which ITF functionality has been equipped in mobile devices such as smart phone, PDA, PMP, Tablet PC, etc. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------------| +| 2G | Second Generation mobile networks | +| 3G | Third Generation mobile networks | +| 4G | Fourth Generation mobile networks | +| AP | Access Point | +| BER | Bit Error Ratio | +| CoD | Content on Demand | +| DASH | Dynamic Adaptive Streaming over HTTP | +| DNG | Delivery Network Gateway | +| DSCQS | Double Stimulus Continuous Quality Scale | +| DTS | Decode Time Stamp | +| DVI | Digital Visual Interface | +| EAN | Emergency Alert Notification | + +| | | +|--------|-------------------------------------------------| +| FEC | Forward Error Correction | +| GOP | Group of Pictures | +| GPS | Global Positioning System | +| HEVC | High Efficiency Video Coding | +| IPTV | Internet Protocol Television | +| ITF | IPTV Terminal Function | +| LBA | Location Based Advertising | +| LBS | Location Based Service | +| LTE | Long Term Evolution | +| MBMS | Multimedia Broadcast Multicast Service | +| MBS | Multicast and Broadcast Service | +| MMT | MPEG Media Transport | +| PDA | Personal Digital Assistant | +| PMP | Portable Multimedia Player | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| SADS | Service and Application Discovery and Selection | +| SCP | Service and Content Protection | +| SNR | Signal to Noise Ratio | +| SSCQE | Single Stimulus Continuous Quality Evaluation | +| SVC | Scalable Video Coding | +| TD | Terminal Device | +| TDES | Terminal Device and End System | +| UICC | Universal Integrated Circuit Card | +| USIM | Universal Subscriber Identity Module | +| VLR | Visitor Location Register | +| VoD | Video on Demand | +| WiMAX. | Worldwide interoperability for Microwave Access | +| WLAN | Wireless Local Area Network | + +## 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. +- The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally + +enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +## 6 Overview + +The definition of IPTV is described in [ITU-T Y.1901] as a multimedia services such as television, video, audio, text, graphics, data delivered over IP-based networks managed to support the required level of quality of service/quality of experience (QoS/QoE), security, interactivity and reliability. + +[ITU-T Y.1903] describes mobile IPTV as application of IPTV as specified in [ITU-T Y.1901] and applies to where the IPTV terminal device is connected to the IPTV service provider via an IPTV-enabled mobile network. It must be able to communicate and access services irrespective of changes of the location or technical environment of mobile device. There are multiple possible levels of mobility, from nomadism, where IPTV service is resumed only after the move is completed, to full mobility, where IPTV service is continuous throughout the movement of IPTV terminal device. With an IPTV-enabled mobile network, it is intended here that a mobile network connecting mobile IPTV TDs provides resource control capabilities to support the QoS required by the end user of mobile IPTV. + +This Recommendation describes the required aspects on requirements, capabilities, architecture, and interfaces of mobile model IPTV TD that can consume IPTV services irrespective of changes of the location or technical environment of a mobile device. An IPTV TD can be connected to a non-"IPTV-enabled mobile network" (i.e., a mobile network where the QoS is not managed). The service quality of mobile model IPTV TD depends on the terminal capability and the feature of content delivery function over wireless or mobile access networks. Essentially, mobile model IPTV TDs are assumed to implement an IPTV terminal function (ITF) in devices such as smartphones, smart pads, etc.; a particular feature of mobile model IPTV TDs is that they support mobility in out-of-home environments. It may be considered that a complete model is implemented on higher performance computing devices such as desktop PCs, set top boxes, and digital TV sets with embedded IPTV capabilities to provide deluxe service capabilities. + +Figure 1 shows a basic network configuration of mobile model IPTV TD in accordance with the basic network configuration of mobile IPTV TDs with the IPTV domains as described in [ITU-T Y.1903]. Where the mobile device that has ITF functionality (e.g., mobile model IPTV TD) it can be connected to an IPTV service provider via a range of wireless or mobile access networks. The mobile model IPTV TD can be connected to the home gateway (GW) or access point (AP) devices through various wireless local area network (WLAN) connections. Alternatively, the mobile model IPTV TD can be connected to the IPTV service provider through various mobile network technologies provided by mobile network operators. The mobile model IPTV TD can access the IPTV service provider via wireless or mobile access networks in the home as well as out of home environments. + +Figure 2 shows the IPTV architectural overview, described in [ITU-T Y.1910]. + +![Figure 1: Basic network configuration of mobile model IPTV TD with the IPTV domains. The diagram shows four main domains: End-user, Network provider, Service provider, and Content provider. The End-user domain includes an IPTV TD (TV) and a Mobile IPTV TD (smartphone) connected to a Home GW. The Home GW is connected to a Wireless network and a Mobile network. The Network provider domain includes a router and a server. The Service provider domain includes a server. The Content provider domain includes a globe and a server. Arrows indicate the flow of data and control signals between these components.](d4af765160d04ecef538e5066006dc77_img.jpg) + +Figure 1: Basic network configuration of mobile model IPTV TD with the IPTV domains. The diagram shows four main domains: End-user, Network provider, Service provider, and Content provider. The End-user domain includes an IPTV TD (TV) and a Mobile IPTV TD (smartphone) connected to a Home GW. The Home GW is connected to a Wireless network and a Mobile network. The Network provider domain includes a router and a server. The Service provider domain includes a server. The Content provider domain includes a globe and a server. Arrows indicate the flow of data and control signals between these components. + +H.723(16)\_F01 + +Figure 1 – Basic network configuration of mobile model IPTV TD with the IPTV domains + +![Figure 2: IPTV architectural overview. This is a complex block diagram showing the functional architecture of IPTV. It is divided into four main vertical columns: End-user functions, Application functions, Management functions, and Content provider functions. The End-user functions column includes IPTV terminal functions (Application client functions, SCP client functions, IPTV terminal functions, Content delivery client functions, Control client functional block) and Home network functions (Delivery network gateway functional block). The Application functions column includes IPTV application functions, Application profile functional block, Content preparation functions, Service control functions (IPTV service control functional block, Service user profile functional block), and Content delivery functions (Content distribution and location control functions, Content delivery and storage functions). The Management functions column includes Application management functional block, Service control management functional block, Control delivery management functional block, End-user device management functional block, and Transport management functional block. The Content provider functions column includes Content and metadata sources. Horizontal and vertical lines with labels like 'Transaction protocol', 'Metadata', 'Control', 'Content', 'Delivery protocols', 'Authentication and configuration protocol', and 'Content and control' show the interactions between these functional blocks.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 2: IPTV architectural overview. This is a complex block diagram showing the functional architecture of IPTV. It is divided into four main vertical columns: End-user functions, Application functions, Management functions, and Content provider functions. The End-user functions column includes IPTV terminal functions (Application client functions, SCP client functions, IPTV terminal functions, Content delivery client functions, Control client functional block) and Home network functions (Delivery network gateway functional block). The Application functions column includes IPTV application functions, Application profile functional block, Content preparation functions, Service control functions (IPTV service control functional block, Service user profile functional block), and Content delivery functions (Content distribution and location control functions, Content delivery and storage functions). The Management functions column includes Application management functional block, Service control management functional block, Control delivery management functional block, End-user device management functional block, and Transport management functional block. The Content provider functions column includes Content and metadata sources. Horizontal and vertical lines with labels like 'Transaction protocol', 'Metadata', 'Control', 'Content', 'Delivery protocols', 'Authentication and configuration protocol', and 'Content and control' show the interactions between these functional blocks. + +H.723(16)\_F02 + +Figure 2 – IPTV architectural overview + +For mobile model IPTV TD, IPTV terminal function (ITF) can be directly connected to the Transport Functions of Network Service Provider without Home Network Functions. Figure 3 describes the architectural aspects of mobile model IPTV TD. Here, the ITF is connected to the network functions, which can be a home network function in the home domain or a network function for the out-of-home domain. + +This mobile model IPTV TD can be connected to the IPTV service provider through various mobile network technologies such as second generation mobile networks (2G), third generation mobile networks (3G), long term evolution (LTE) and WLAN in the home as well as out-of-home environments. + +In a home network environment, the mobile model IPTV TD can be connected to the home GW or AP using wireless access network interface (e.g., WLAN). In other cases, the mobile model IPTV TD can be connected to a mobile network (e.g., 3G, LTE) directly and this TD can obtain IPTV services using the Internet access feature of mobile network. In an out-of-home environment, the mobile model IPTV TD can enjoy IPTV service over the Internet connection over a wireless or mobile access network even if IPTV TD is moving. For the moving IPTV TD, the service quality depends on the capability of mobility support of IPTV TD. + +The mobile network should provide the capability to identify and locate the IPTV TD. A mobile model IPTV TD can be any of various types of mobile devices such as a personal digital assistant (PDA), portable multimedia player (PMP), tablet PC, mobile phone or smart phone. + +![Figure 3 – Architectural aspects of mobile model IPTV TD. The diagram shows the architecture of a mobile model IPTV terminal device (TD) divided into two main domains: End-user domain and Network/service provider domain. The End-user domain is a large pink box containing two sub-sections: 'Home network functions' and 'Out of home network functions'. Each sub-section contains a 'Mobile ITF' (Interface) connected to a 'Wireless access network functions' block, which is connected to a 'Delivery network gateway functional block'. Below the 'Delivery network gateway functional block' is a 'Mobile access network functions' block. The 'Network/service provider domain' is a large green box containing a 'Resource control functional block' (with an ellipsis) and an 'Access network functions' block. The 'Access network functions' block contains a 'Mobile access network functions' block. Lines connect the 'Mobile ITF' blocks in the End-user domain to the 'Access network functions' block in the Network/service provider domain. The 'Resource control functional block' is also connected to the 'Access network functions' block. The diagram is labeled 'End-user domain' and 'Network/service provider domain' at the bottom. A small text 'H.723(16)_F03' is in the bottom right corner.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +Figure 3 – Architectural aspects of mobile model IPTV TD. The diagram shows the architecture of a mobile model IPTV terminal device (TD) divided into two main domains: End-user domain and Network/service provider domain. The End-user domain is a large pink box containing two sub-sections: 'Home network functions' and 'Out of home network functions'. Each sub-section contains a 'Mobile ITF' (Interface) connected to a 'Wireless access network functions' block, which is connected to a 'Delivery network gateway functional block'. Below the 'Delivery network gateway functional block' is a 'Mobile access network functions' block. The 'Network/service provider domain' is a large green box containing a 'Resource control functional block' (with an ellipsis) and an 'Access network functions' block. The 'Access network functions' block contains a 'Mobile access network functions' block. Lines connect the 'Mobile ITF' blocks in the End-user domain to the 'Access network functions' block in the Network/service provider domain. The 'Resource control functional block' is also connected to the 'Access network functions' block. The diagram is labeled 'End-user domain' and 'Network/service provider domain' at the bottom. A small text 'H.723(16)\_F03' is in the bottom right corner. + +**Figure 3 – Architectural aspects of mobile model IPTV TD** + +## 7 Services and key features of mobile model IPTV terminal device + +The mobile model IPTV TD is required to support basic IPTV services defined in [ITU-T H.720], which are service navigation, linear TV, content on-demand, interactive services, and public interest services (see clause 6.1.1 of [ITU-T H.720]). Most of the basic IPTV services that are supported by the IPTV terminal device's basic model [ITU-T H.721] may be supported by the mobile model IPTV TD. Additionally, enhanced features of basic IPTV services can be provided based on the location information and mobility feature of mobile model IPTV TD. However, due to the lack of service capability of mobile or wireless networks and resource limitations of mobile devices, QoS of mobile model IPTV TD can be degraded compared to the basic model IPTV TD [ITU-T H.721]. + +### 7.1 Services for the IPTV TD mobile model + +#### 7.1.1 Linear TV + +Linear TV is a broadcast TV service that is the same as the classic form of television services that are provided by terrestrial, cable, and direct-to-the-home satellite broadcasting operators, where the programme content is transmitted according to a defined schedule and is intended for real-time consumption by the end-user. + +Broadcast and multicast mechanisms are typically used for efficient contents delivery for providing linear IPTV service. It is especially helpful to support mobile IPTV TD if the mobile network supports broadcast/multicast mechanisms directly. However, there may be some limitations to provide broadcast/multicast mechanisms from specific mobile network technologies. + +Due to the resource limitations of mobile model IPTV TD in general, the quality of video and audio for linear TV service can have a different level of requirements from the quality of fixed IPTV TD. Appropriate media format to support mobile model IPTV TD can be selected by the IPTV service provider or user. + +Table 1 of [ITU-T H.721] includes specifications used for formats and streaming methods used in linear TV services, and they can be applied to the mobile model IPTV TD. However, the specific media types (e.g., ITU-T H.265 high efficiency video coding (HEVC), audio decoding time stamp-high definition (DTS-HD) and multiplex formats (e.g., MPEG multimedia transport (MMT)) of this table may not be available due to the limited resources of the mobile model IPTV TD. Considering rapid enhancement of mobile device capability and the quality of network conditions, the most of audio and video codecs should be supported in the near future. + +#### **7.1.2 Video on-demand** + +The video on-demand service (VoD) enables an end-user to select, acquire, and consume from a library of content stored on a remote or local server. Video on-demand is used as the same term with content on demand (CoD) in this Recommendation. + +Due to the resource limitations of mobile model IPTV TD, the quality of video and audio for VoD service can have a different level of requirement than the quality of fixed IPTV TD. Appropriate media format to support mobile model IPTV TD can be specified. + +Table 2 of [ITU-T H.721] includes specifications used for formats and streaming methods used in VoD services that can be applied to mobile model IPTV TD. However, the specific media types and multiplex formats of this table may not be available due to the same reason as that of the linear TV case. + +#### **7.1.3 Interactive services** + +The IPTV TD is recommended to have the ability to communicate with a remote interactive content server via means such as HTTP or HTTPS protocols. Examples of interactive services are information services and entertainment services. + +Information services are, for example, news, stock and weather services. Entertainment services are, for example, games, karaoke and lottery services. Some types of information services, including weather and traffic information services, can be provided based on the location information of mobile model IPTV TD. + +#### **7.1.4 Public interest services** + +The IPTV TD is required to be compliant with regulatory requirements for accessibility services. Examples of these accessibility services are closed caption and subtitles, audio description, and sign language interpretation. + +The mobile model IPTV TD is also required to be compliant with emergency telecommunications and regulatory information services. The TD notifies the user of an incoming emergency alert notification (EAN) message both visually and audibly or according to the user's preferences and capabilities if specified. + +#### **7.1.5 Advertising services** + +Location-based advertising (LBA) is a form of marketing communication that uses location-tracking technology in mobile networks to target consumers with location-specific advertising on their mobile devices. Location-based advertising, e.g., the advertisement of local restaurants, can be + +provided to the IPTV service user when the mobile model IPTV TD determines its location and sends the location information to the IPTV service provider. + +### **7.2 Features of the IPTV TD mobile model** + +#### **7.2.1 Network attachment and service discovery** + +This process enables end-users to connect to a particular service and to consume a linear TV service or a VoD service, after connecting their IPTV TD to the network. A mobile device that has IPTV TD mobile model functions has to be connected to the IPTV service provider through wireless or mobile access networks. For details of the service discovery, refer to [ITU-T H.770]. + +Through the provisioning operation, including network attachment, the IPTV TD automatically obtains the initial information for consumption. When this process is completed, end-users have access to all available IPTV services. Except for the establishment of wireless or mobile network connectivity, the detailed information on "network attachment and service discovery" is the same as in [ITU-T H.721]. + +##### **7.2.1.1 Terminal device attachment and initialization** + +The detailed information is the same as clause 7.2.1.1 "Terminal device attachment and initialization" of [ITU-T H.721]. + +##### **7.2.1.2 Service provider description entry points** + +The detailed information is the same as clause 7.2.1.2 "Service provider description entry points" of [ITU-T H.721]. + +##### **7.2.1.3 Service provider discovery and service attachment** + +The detailed information is the same as clause 7.2.1.3 "Service provider discovery and service attachment" of [ITU-T H.721]. + +#### **7.2.2 Security** + +A mobile model IPTV TD is required to support the "Service security items" and "Content protection items" described in clause 7.2.2 of [ITU-T H.721] after establishing the network layer connections to receive IPTV services. Specifications used for IPTV TD-basic model service security described in Table 5 of [ITU-T H.721] are also applied to mobile model IPTV TD. + +A mobile model IPTV TD can include the security modules as its internal functionalities or it can also optionally implement the mechanism to download the security modules so that the module update is facilitated [ITU-T Y.1901]. + +#### **7.2.3 Privacy** + +The detailed information about privacy is the same as clause 7.2.3 "Privacy" of [ITU-T H.721]. + +#### **7.2.4 Quality of service** + +The quality of IPTV service of mobile model IPTV TD depends on various situations such as conditions of wireless or mobile networks and the capability of a mobile device with embedded ITF functions. As described in Recommendation [ITU-T Y.1903], when a mobile model IPTV TD is connected to IPTV service provider through an IPTV-enabled mobile network, the QoS of mobile model IPTV TD can be managed in accordance with the QoS capabilities of the mobile network. The level of QoS depends on the service and resource control mechanisms of the mobile network. + +When an IPTV TD is connected to a non-IPTV-enabled wireless or mobile access networks, the QoS cannot be managed. The service quality of mobile model IPTV TD depends on the terminal capability and the content delivery function feature over wireless or mobile access networks. + +The appropriate service and resource control capabilities in the wireless or mobile networks where the mobile IPTV TD is connected are recommended to support the QoS required by the end user of mobile IPTV TD. The details of QoS control mechanisms are out of scope of this Recommendation. + +Appendix I provides a description of QoS-related issues. + +#### **7.2.5 Codecs** + +##### **7.2.5.1 Video decoding** + +The detailed information is the same as clause 9.3.3.1 "Video decoding" in [ITU-T H.721]. However, high quality video codecs would not be supported due to the limited resources of the mobile model IPTV TD. Appropriate video codec for the mobile model IPTV TD can be selected by the IPTV service provider or user. + +Support of one of the categories in Table 8 of [ITU-T H.721] is required. + +##### **7.2.5.2 Audio decoding** + +The detailed information is the same as clause 9.3.3.2 "Audio decoding" in [ITU-T H.721]. However, high quality audio codecs would not be supported due to the limited resources of the mobile model IPTV TD. Appropriate audio codec for the mobile model IPTV TD can be selected by the IPTV service provider or user. + +Support of one of the audio codecs in Table 12 of [ITU-T H.721] is required. + +#### **7.2.6 Location determination** + +Location information indicates the location of the mobile user as accurately as possible with the available information. This could be, for example, cell ID, location area ID, visitor location register (VLR) address, or some type of geographical information [b-ITU-T Q.1721]. Location information of mobile IPTV terminal device can usually be acquired by the network operator. Location information, however, acquired by the mobile TD using global positioning system (GPS) can be more accurate than the location information acquired by the network provider. The IPTV service user can be provided with location-based IPTV services by transferring the location information acquired by the mobile model IPTV TD to the IPTV service provider. + +For providing advanced IPTV services based on location information, it is recommended to provide location information acquired by the mobile model IPTV TD to the IPTV service provider if the mobile model IPTV TD has the location detection capability. + +#### **7.2.7 Multi-device interworking** + +Multi-device service provides the user a different IPTV service consuming experience over one or more other terminal devices. Typically, the multi-device service may include content sharing, e.g., content transferring and coupled content playing. Moreover, some devices can control media playing on the other devices. In a multi-device environment, the roles defined for the device determines which capability the device should support. + +To support the multi-device service, support of the following capabilities by a mobile model IPTV TD is recommended: + +- provide send announcement to all connected terminal devices for claiming its functional roles; +- provide devices discovery and inter-connection setup. + +The details of multi-device services are out of scope of this Recommendation. These will be studied within the context of an interworking-enabled model of multiple devices. + +Mobile model IPTV TD will have more portable capabilities to act as remote media controller and portable player device. It will play the client functional roles when it is working under terminal device interworking mode. The following functional roles are recommended: + +- media controller: provide the capability of remote media control, remote user interface (UI) for control panel; +- media player: provide the capability of media playing; +- optional media renderer: optionally provide media playing capability or media rendering capability for other displays; +- optional media server: optionally provide media server capability to be the media centre device. + +#### 7.2.8 Mobility + +Mobility is the ability for the user or other mobile entities to communicate and access services irrespective of changes of the location or technical environment of the mobile device. There are three different aspects of mobility: personal mobility, terminal mobility, and service mobility. Based on the different aspects of mobility, different mobility feature of mobile model IPTV TD can be taken into account. These mobility-related issues are standardized by the relevant standardization bodies. + +##### 7.2.8.1 Personal mobility + +Personal mobility implies a guarantee that a user can get the service anywhere with any device. It also means the mobility of a network itself, and providing the mobility without connecting to different kinds of networks. For example, if someone watching IPTV content wants to move and continue watching it with a different terminal device, then the IPTV network should support personal mobility so that the user can be guaranteed to continue to get the IPTV service according to the user's service profile. + +To provide personal mobility, IPTV should consider the following aspect: + +- when a user moves to a location where the network connection point is different or the network provider is different from what the has been connecting to, the IPTV TD is required to connect to IP network per the user's service profile to continue accessing the IPTV service. + +##### 7.2.8.2 Terminal mobility + +Terminal mobility implies a guarantee of providing seamless IPTV service when the IPTV terminal device is moving or used at different locations. + +To provide terminal mobility, the network is required to provide a roaming and routing service including handover and automatic routing setup for the IPTV TD. + +The IPTV TD can receive the IPTV services seamlessly without changing its IP address despite a location change. The IPTV TD may have mobility functions at the IP layer. + +##### 7.2.8.3 Service mobility + +Service mobility provides seamless IPTV service irrespective of the location of the user and the IPTV TD. For providing seamless IPTV service, it is required to support seamless handover capability. + +## 8 Functional architecture of IPTV terminal device (mobile model) + +[ITU-T H.720] describes a functional architecture block diagram of IPTV TD based on [ITU-T Y.1910], "IPTV Functional Architecture" as shown in Figure 4 below. See [ITU-T H.720]. + +Some considerations for mobile model IPTV TD are described here for relevant functions of the terminal device. + +![Functional architecture block diagram of an IPTV terminal device. The diagram shows a hierarchy of functions. At the top is 'Application client functions' (orange) with 'SADS client functional block' and 'IPTV application client'. Below it is 'SCP client functions' (green) with 'Service protection client functional block' and 'Content protection client functional block'. Below that are 'Control client functional block' and 'Performance monitoring'. The next level is 'Content delivery client functions' (purple), which contains 'Media client functions' (blue) with 'Broadcast demux', 'Demux/mux', 'Storage', 'Codecs', 'Media control', and 'Metadata management'. Below 'Media client functions' are 'Unicast content delivery client functional block', 'Multicast content delivery client functional block', and 'Error recovery client functional block'. At the bottom is 'IPTV terminal transport functions' (green) with 'Network attachment client'. A vertical 'Terminal device management' bar is on the left, connected to the top three levels.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +**IPTV terminal functions** + +``` + +graph TD + subgraph IPTV_Terminal_Functions [IPTV terminal functions] + subgraph Terminal_Device_Management [Terminal device management] + TDM[Terminal device management] + end + + subgraph Application_Client_Functions [Application client functions] + SADS[SADS client functional block] + IPTV_APP[IPTV application client] + end + + subgraph SCP_Client_Functions [SCP client functions] + SP[Service protection client functional block] + CP[Content protection client functional block] + end + + CC[Control client functional block] + PM[Performance monitoring] + + subgraph Content_Delivery_Client_Functions [Content delivery client functions] + subgraph Media_Client_Functions [Media client functions] + BD[Broadcast demux] + DM[Demux/mux] + ST[Storage] + CD[Codecs] + MC[Media control] + MM[Metadata management] + end + + UCD[Unicast content delivery client functional block] + MCD[Multicast content delivery client functional block] + ERC[Error recovery client functional block] + end + + subgraph IPTV_Terminal_Transport_Functions [IPTV terminal transport functions] + NAC[Network attachment client] + end + + TDM --- Application_Client_Functions + TDM --- SCP_Client_Functions + TDM --- CC + TDM --- Content_Delivery_Client_Functions + end + +``` + +H.723(16)\_F04 + +Functional architecture block diagram of an IPTV terminal device. The diagram shows a hierarchy of functions. At the top is 'Application client functions' (orange) with 'SADS client functional block' and 'IPTV application client'. Below it is 'SCP client functions' (green) with 'Service protection client functional block' and 'Content protection client functional block'. Below that are 'Control client functional block' and 'Performance monitoring'. The next level is 'Content delivery client functions' (purple), which contains 'Media client functions' (blue) with 'Broadcast demux', 'Demux/mux', 'Storage', 'Codecs', 'Media control', and 'Metadata management'. Below 'Media client functions' are 'Unicast content delivery client functional block', 'Multicast content delivery client functional block', and 'Error recovery client functional block'. At the bottom is 'IPTV terminal transport functions' (green) with 'Network attachment client'. A vertical 'Terminal device management' bar is on the left, connected to the top three levels. + +**Figure 4 – Functional architecture block diagram of an IPTV terminal device** + +### – **IPTV terminal transport functions** + +These functions are responsible for handling IP-based connection between an IPTV TD and the mobile network. These functions are responsible for mobility management to provide personal mobility and terminal mobility if such a mobility feature is required. Network attachment clients provide connectivity to the mobile networks through various mobile access network technologies such as 2G, 3G, LTE, and WLAN, etc. + +### – **Content delivery client functions** + +These functions receive and control the delivery of the content from the content delivery and storage functions. The unicast content delivery client functional block and multicast content delivery client functional block could have responsibilities for content reception and control of real time streaming, etc. These functional blocks will interact with the IPTV terminal transport function that is connected to mobile networks. The error recovery client functional block is responsible for improving the QoS/QoE provided by the mobile network. Retransmission, forward error correction (FEC), and hybrid combinations of both are known mechanisms for error recovery. Due to the link characteristics of mobile networks, efficient error recovery is a very important capability for mobile model IPTV TD. FEC is known as an appropriate mechanism to support mobile model IPTV TD. Refer to [ITU-T H.701] for recommended details regarding error recovery. + +### – **Media client functions** + +These functions are responsible for content processing functionalities such as storage, metadata processing, and decoding of audio/video contents. A mobile model IPTV TD may require different codec characteristics compared to another IPTV TD that is connected to a fixed network. + +### – **SCP client functions** + +These functions are responsible for service and content protection (SCP) aspects of the IPTV TD. + +### – **Application client functions** + +These functions are responsible for the basic functions, management functions, and service supporting functions for IPTV TD. The individual functional blocks of the application client functions defined in [ITU-T Y.1910] are divided roughly into two groups based on their nature, as shown in Figure 3. The IPTV application client function consists of service specific functional blocks such as on-demand client functional block, linear TV client functional block and other client functional blocks. Other client functional blocks interact with the other server-side relevant ones for the delivery and presentation of additional IPTV services and their content, e.g., games and distant learning. The service and application discovery and selection (SADS) client functional block provides for the end user's discovery and selection of IPTV services and applications. Power management that is one of the important capabilities of mobile model IPTV TD, which belongs to management function of application client function. + +### – **Terminal device management function** + +This functional entity provides configuration management and remote management of IPTV TD. This functional entity also provides the functions for monitor and control of the mobile model IPTV TD functionality. + +### – **Control client functional block** + +The control client functional block allows the terminal device to initiate service requests to the IPTV service control functional block, in order to prepare for the connection to the content delivery functions. Terminal capability information will be managed to establish and control content delivery over mobile network environments. + +### – **Performance monitoring** + +This function is responsible for monitoring of performance aspects of IPTV TD. + +## 9 Specific requirements for mobile model IPTV TD + +This clause provides additional functional requirements to the general requirements that are described in Appendix I. + +### 9.1 Functional requirements of terminal transport functions + +Various mobile or wireless networks to which mobile model IPTV TDs can connect have their own access network characteristics. A mobile model IPTV TD needs to detect and use these wireless network characteristics to manage QoS/QoE of mobile or wireless network connections. In addition, the mobile model IPTV terminal device may have several different mobile or wireless network interfaces, such as WLAN, 3G and forth generation mobile networks (4G). In this case, signal interference that may be caused by the electromagnetic characteristics of the different interfaces should not be allowed. + +Handover refers to the process that enables a mobile terminal to change network access areas/points within a network or to another network, while maintaining call(s) and/or signalling relationship(s). When the vertical handover occurs to provide seamless IPTV service, transport features such as bandwidth and codec information can be changed due to the link characteristics of the mobile/wireless network. A terminal device needs to take into account these cases. The following functional requirements of terminal transport functions of mobile model IPTV TD take into consideration various transport-related issues: + +- mobile model IPTV TD supporting mobile communications technology is recommended to support horizontal handover; +- mobile model IPTV TD can optionally support vertical handover; +- mobile model IPTV TD is recommended not to allow signal interference among the different mobile/wireless network interfaces; +- mobile model IPTV TD is recommended to support the capability to detect mobile network characteristics; +- mobile model IPTV TD is recommended to support functions to change its transport capabilities such as bandwidth based on the network conditions. + +NOTE – This can take place where the handover occurs to provide seamless mobile IPTV service when the terminal device is moving. + +A mobile model IPTV TD may have multiple network interfaces to enable handover. The following functional requirements can be considered to manage multiple network interfaces of mobile model IPTV TD: + +- mobile model IPTV TD is recommended to have the ability to determine the appropriate interface to be used considering the condition of each network interface when the mobile terminal provides multiple network interfaces; +- mobile model IPTV TD with multiple network interfaces is recommended to have the ability to let the user select the interface to be used; +- mobile model IPTV TD with multiple network interfaces is recommended to efficiently manage its interfaces (e.g., considering power management), whose status are on, off, sleep, etc. + +### 9.2 Functional requirements of content delivery client functions + +Unicast and multicast content delivery client functional block need to interact with relevant transport functions that provide connectivity to mobile network such as 2G, 3G, LTE, WLAN, etc. Relevant technologies such as evolved multimedia broadcast multicast service (MBMS) of 3GPP and enhanced multicast and broadcast service (MBS) of IEEE to support multicast/broadcasting applications should be taken into account. Additionally, the error recovery function is very important to deliver contents to the mobile model IPTV terminal device. The applicable functional requirements are: + +- mobile model IPTV TD is recommended to support FEC error recovery mechanisms; + +- mobile model IPTV TD is recommended to use multicast delivery mechanisms (e.g., MBMS, MBS) if wireless or mobile network provides those capability. + +Specifications used for IP level multicast content delivery is the same as clause 9.2.2 "Multicast content delivery client function block" of [ITU-T H.721]. + +Specifications used for IP level unicast content delivery is the same as clause 9.2.3 "Unicast content delivery client functional block" of [ITU-T H.721]. + +### **9.3 Functional requirements of media client functions** + +It is desirable that the quality provided by mobile model IPTV TD can be degraded, but that it can be maintained without disconnection of the IPTV service. When the IPTV TD is moving, the wireless network characteristics can change. If the quality of the wireless network is degraded due to mobility, it may not be possible to continue to receive the IPTV service of mobile mode IPTV TD with the same quality. If the quality of the media can be adjusted, the IPTV service can be provided by mobile model IPTV TD without service discontinuity. The applicable functional requirement is: + +- mobile model IPTV TD is recommended to support functions to request the IPTV service provider to adjust codec characteristics when wireless network characteristics have been changed. + +The codec functional block decodes video data, audio data, caption data, graphics and image data, textual data, and other multimedia data. + +Specifications used for video decoding are the same as clause 9.3.3.1 "Video decoding" of [ITU-T H.721]. However, there are some limitations to support high quality video codec due to the lower mobile model IPTV TD computing capability. At least Category 0 of Table 8 in clause 9.3.3.1 of [ITU-T H.721] is required to be supported as a basic mode of video decoding. + +Specifications used for audio decoding are the same as clause 9.3.3.2 "Audio decoding" of [ITU-T H.721]. However, there are some limitations to support high quality audio codec due to the lower terminal capability of mobile model IPTV TD. + +### **9.4 Functional requirements of control client functional block** + +The mobile model IPTV TD capability should be managed for efficient content delivery over mobile/wireless network environments. This TD capability information needs to be exchanged between TD and the IPTV network to control content delivery. Also, the TD capability information may need to be modified for the same session for providing seamless mobility service. + +- mobile model IPTV TD is recommended to support the capability to provide the following TD capability information: + - type of network interface and its features; + - capability information of display device. +- mobile model IPTV TD is recommended to support the capability to provide characteristics information (e.g., available bandwidth, SNR, BER) of the link to which the IPTV TD is connected. + +### **9.5 Functional requirements of SCP client functions** + +Requirements for SCP client function of mobile model IPTV terminal device need to be aligned with the relevant detailed security requirements, described in [ITU-T X. 1191]. Detailed security requirements may be described for service security, content protection, device security, and user security. + +### 9.6 Functional requirements of performance monitoring functions + +There are no specific requirements for performance and monitoring functions of mobile model IPTV TD. + +### 9.7 Functional requirements of terminal device management functions + +- mobile model IPTV TD can optionally have environmental adaptation abilities, e.g., making the sound louder with street noise or making the display dimmer as evening approaches; +- mobile model IPTV TD can optionally determine its location and send the location information to the IPTV service provider. + +### 9.8 Functional requirements of application client functions + +No additional functional requirement is needed for the application client function to support mobile model IPTV TD. Requirements specified in [ITU-T Y.1901] are generally applied to mobile model IPTV TD. + +## 10 Interfaces for mobile model IPTV terminal device + +This clause provides an abstract description of mobile model IPTV TD interfaces. Since the realization of physical interfaces may be varied, the diagram of IPTV TD interfaces, as shown in Figure 5, describes possible external TD interfaces and is not meant to indicate required interfaces. + +![Diagram illustrating the interfaces of an IPTV terminal device. The central component is the IPTV terminal device, which connects to various external systems and components via specific interfaces. On the left, it connects to the IPTV network (e.g., NGN) via NW-TT and NW-TD-2; the IPTV network connects to a DNG (Dashed Network Gateway), which in turn connects to the Home network via TD-HN. The Home network also connects to the IPTV terminal device via TD-HN. The IPTV terminal device connects to a Broadcast network (e.g., satellite) via BC-TD. On the right, it connects to a User interface (e.g., remote control) via TD-PD, and to a display via TD-OD. At the bottom, it connects to External storage via TD-PD, to a Media scrambler/descrambler via TD-PD, and to Removable security via TD-SM.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +The diagram shows a central 'IPTV terminal device' connected to various external entities. On the top left, an 'IPTV network (e.g., NGN)' connects to a 'DNG' (Dashed Network Gateway) via 'NW-TT' and 'NW-TD-2'. The 'DNG' connects to a 'Home network' via 'TD-HN'. The 'Home network' also connects to the 'IPTV terminal device' via 'TD-HN'. On the bottom left, a 'Broadcast network (e.g., satellite)' connects to the 'IPTV terminal device' via 'BC-TD'. On the right, the 'IPTV terminal device' connects to a 'User interface (e.g., remote control)' via 'TD-PD', and to a display via 'TD-OD'. At the bottom, the 'IPTV terminal device' connects to 'External storage' via 'TD-PD', to a 'Media scrambler/descrambler' via 'TD-PD', and to 'Removable security' via 'TD-SM'. + +Diagram illustrating the interfaces of an IPTV terminal device. The central component is the IPTV terminal device, which connects to various external systems and components via specific interfaces. On the left, it connects to the IPTV network (e.g., NGN) via NW-TT and NW-TD-2; the IPTV network connects to a DNG (Dashed Network Gateway), which in turn connects to the Home network via TD-HN. The Home network also connects to the IPTV terminal device via TD-HN. The IPTV terminal device connects to a Broadcast network (e.g., satellite) via BC-TD. On the right, it connects to a User interface (e.g., remote control) via TD-PD, and to a display via TD-OD. At the bottom, it connects to External storage via TD-PD, to a Media scrambler/descrambler via TD-PD, and to Removable security via TD-SM. + +Figure 5 – Examples of IPTV terminal device interfaces + +### 10.1 Network interface + +#### 10.1.1 Mobile/wireless network interface + +There are various mobile or wireless access networks for providing IPTV services over mobile model IPTV TD. It will be very useful for users if mobile model IPTV TD supports as many mobile or wireless access network technologies as possible (e.g., 2G, 3G, LTE, WLAN). However, there + +will be limitations to the support of several interfaces simultaneously due to the lack of terminal capability. + +- mobile model IPTV TD is required to equip at least one mobile or wireless interface for providing IPTV service. + +#### **10.1.2 Fixed network interface** + +It will be helpful in the home and enterprise network environments if mobile model IPTV TD provides fixed network interface such as 10BASE-T, 100BASE-T, Gigabit Ethernet LAN. + +- mobile model IPTV TD can optionally support LAN interface. + +### **10.2 User input interface** + +This interface allows user input to handle mobile model IPTV TD. It can be a hardware or software component such as a microphone, remote control device, keyboard or touch screen. + +- mobile model IPTV TD is required to support at least one input interface; +- mobile model IPTV TD can optionally support touchscreen and other various sensors such as accelerometer or position sensor. + +### **10.3 Output interface** + +This interface is between mobile model IPTV TD and output devices such as a speaker, headphone, display, home theatre system or external personal video recorder (PVR). It facilitates transfer of audio and video signals from IPTV terminal device to the output device. + +- mobile model IPTV TD is required to support an audio output interface; +- mobile model IPTV TD can optionally support a video output interface; +- mobile model IPTV TD can optionally support a red, green, blue (RGB) analogue interface (e.g., D, RCA, S or S2 connectors); +- mobile model IPTV TD can optionally support a digital video interface (DVI) interface; +- mobile model IPTV TD can optionally support a high-definition multimedia interface (HDMI) interface; +- mobile model IPTV TD can optionally support a video graphics array (VGA) interface and a DVI interface with analog output; +- mobile model IPTV TD can optionally support vibration. + +If the mobile model IPTV TD has DVI or HDMI, and when it outputs content with copy control or protection, it is required to provide appropriate protection according to the high-bandwidth digital content protection (HDCP) specification. The details of copy control and output control are for further study. + +### **10.4 Peripheral device interface** + +This interface is between mobile model IPTV TD and peripheral device such as a universal serial bus (USB) flash drive or Bluetooth device. Bluetooth and other ad hoc network technologies can be used for IPTV content delivery between mobile model IPTV TD and other Bluetooth devices. Contents protection aspects need to be considered regarding to the content delivery, but it is not dealt with in this clause. + +- mobile model IPTV TD can optionally support USB interface; +- mobile model IPTV TD can optionally support Bluetooth interface. + +### **10.5 Security module interface** + +This interface is between mobile model IPTV TD and a removable security module such as universal integrated circuit card (UICC). + +- mobile model IPTV TD is recommended to support removable security module interface. + +## Annex A + +### General requirements for mobile IPTV services + +(This annex forms an integral part of this Recommendation.) + +[ITU-T Y.1901] describes various aspects of IPTV service requirements. Some of these requirements of [ITU-T Y.1901] are related to mobile IPTV service and it may need to be applied to specify detailed functional requirements and capabilities of mobile IPTV TDs. + +The followings are general requirements for mobile IPTV services, described in [ITU-T Y.1901]. These requirements should be taken into account for mobile IPTV TD as appropriate. + +- R 6.4.3-01: The IPTV architecture is required to support mechanisms for exchanging subscriber-related information between the visited network (where the end-user accesses the IPTV services) and the home IPTV service provider (where the end-user has its subscription to the IPTV services) in case mobility is supported. +- R 6.4.3-02: The IPTV architecture is required to support mechanisms for discovering and selecting the end-user's service profile from the IPTV TD or the home service provider that will be used by the end-user whenever accesses such IPTV services from a visited network in case mobility is supported. +- R 6.4.3-03: The IPTV architecture is required to support mechanisms for discovering and selecting IPTV services provided by the home IPTV service provider for roaming users in case mobility is supported. +- R 6.4.3-04: The IPTV architecture is required to support capturing relevant control context information from the originating terminal device, and transferring them to the target terminal device in case mobility is supported. +- R 6.4.3-05: IPTV architecture is required to support nomadism for both personal mobility and terminal mobility. + +Note: further information concerning nomadism, personal mobility and terminal mobility can be found in [ITU-T Y.2201]. + +- RR 6.1.1-01: The IPTV architecture is recommended to allow seamless IPTV service provision and operation across different networks supporting IPTV services. +- RR 6.1.4-03: The IPTV architecture is recommended to support capabilities for the end-user mobility allowing access to IPTV services by the end-user either in motion or not. +- RR 6.4-03: The IPTV architecture is recommended to support the ability to identify wireless network characteristics information sent by the IPTV terminal device. +- RR 6.4.1-02: The IPTV architecture is recommended to allow the delivery of IPTV services over different access networks (e.g., cable, optical, xDSL, wireless). +- RR 6.4.3-01: Where support for terminal mobility with service continuity exists, such support is also recommended for IPTV. + +## Appendix I + +### QoS and performance + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Quality of service + +Various QoS parameter sets have significant impact on the perceptual quality of transmitted video. These can be related to the duration of the impairment in the video signal, or to the network impairment parameters. They are indispensable for equipment specifications, as well as daily system performance measurement, improvement and monitoring. + +Group of pictures (GOP) length has impacts on transmitted video quality over error-prone networks. It has direct relationship with the error propagation (the error length), the severity of loss (which conceptually refers to the difficulty in lost frame concealment, and can be measured, for example, by the peak signal-to-noise ratio (PSNR) drop following a loss), the loss position (measured by the time to the end of sequence, known as the "forgiveness effect"), the number of loss in a sequence and the loss pattern (random or impulsive). + +From the network provider's point of view, the transmitted compressed video quality can be monitored indirectly by network parameters including: + +- packet arrival time; +- packet delay and jitter; +- network bandwidth; +- impairment duration; +- packet loss (or drop), duplication or out of sequence. + +Other parameters above the IP level can help getting better estimation of the effect of network QoS parameters on video quality. These include: + +- PSI data presence rate; +- payload compression schemes (MPEG-2 video [b-ITU-T H.262], [b-ITU-T H.264], etc.); +- GOP; +- encapsulation schemes (Ethernet/IP/UDP/MPEG-2 TS, Ethernet/IP/UDP/RTP/MPEG-2 TS, Ethernet/MPLS/IP/UDP/RTP/MPEG-2 TS, etc.). + +These network and high-level parameters can be monitored to provide cost-effective indications of the contribution of network behaviour to video quality. + +Optional parameters for diagnostic purposes can be found in the (non-exhaustive) list below: + +- jitter buffer size; +- bit rate (audio and video); +- packet-loss ratio (audio and video); +- packet-discard ratio (audio and video); +- averaged burst packet loss length (audio and video); +- burst packet loss variation range; +- mean packet size; +- delay; +- delay variation range; +- FEC, automatic repeat request (ARQ) and de-jitter buffer. + +### **I.2 Quality and performance assessment** + +#### **I.2.1 Video quality assessment** + +##### **I.2.1.1 Subjective assessment** + +There are a number of subjective video quality measurement methods suggested in [b-ITU-R BT.500-13]. Depending on the impairment being evaluated, the selection of a method requires careful considerations of sequence duration, transmission condition, ecological environment and other factors. The output of the subjective tests is often an average of the quality ratings called mean opinion score (MOS). [b-ITU-R BT.500-13] recommends a five-grade impairment scale: + +- 5 – imperceptible; +- 4 – perceptible, but not annoying; +- 3 – slightly annoying; +- 2 – annoying; +- 1 – very annoying. + +The grading of video quality can also be expressed as a percentage from 0 to 100, with 0 indicating no distortion. The higher the value is, the greater the distortion occurs. + +[b-ITU-R BT.500-13] includes specifications on how to perform different types of subjective test. The double stimulus continuous quality scale (DSCQS) and double stimulus comparison scale (DSCS) are both double stimulus where viewers rate the quality or change in quality of two video streams (reference and impaired). The single stimulus continuous quality evaluation (SSCQE) assesses only one impaired video stream. The DSCQS is claimed to be less sensitive to the context, while SSCQE is claimed to produce more representative estimates for quality monitoring. + +In addition, [b-ITU-T P.910] includes specifications on how to perform a type of subjective test for video. The absolute category rating with hidden reference removal (ACR-HRR) is a single stimulus continuous quality evaluation. + +##### **I.2.1.2 Objective assessment** + +Due to the complexity and time consuming nature of subjective video monitoring, there has been significant development of perceptual video quality measurement (PVQM) algorithms in recent years in an attempt to replicate the scores given by subjects in an objective tool. Objective quality monitoring can be classified into the following categories: + +- techniques based on models of human video perception; +- techniques based on video signal parameters. + +Human video perception models attempt to emulate the characteristics of the human visual system to obtain video quality scores. A good model should yield high correlation to the ratings the actual viewers would provide. Three popular approaches can be used: + +- 1) Full reference (FR) – both the original transmitted and received video are available to determine the video quality; +- 2) Reduced reference (RR) – partial information about transmitted video and full information about received video are available to determine the video quality; +- 3) No reference (NR) – only the received video is available to determine the video quality. + +### **I.3 Quality and performance monitoring** + +#### **I.3.1 Adaptability** + +##### **I.3.1.1 Video/audio adaptation** + +Scalable video coding (SVC) as specified in Annex G of [b-ITU-T H.264] allows the combinations of different video resolutions being supported within the mobile IPTV application platforms. There exist mainly three video scalability modes in SVC: temporal, spatial and quality. Spatial and temporal scalabilities describe respectively the capability of representing the source video using a reduced picture size (spatial resolution) and frame rate (temporal resolution). The quality scalability, also referred to as signal-to-noise ratio scalability, represents the source video with a lower fidelity one (lower SNR) while keeping the spatial-temporal resolution unchanged. Scalable video coding is the key to adapt the content distribution for resource optimization of access networks. It provides efficient means for achieving better video end user QoS/QuE. + +The scalable video is generally coded into one base layer, which represents the minimum quality, and enhanced layers for higher qualities. It is recommended to pre-encode the video in a base layer and multiple enhanced layers, corresponding to multiple network bandwidths. So the server can stream the suitable layer(s) based on the monitored QoS. The video player on the mobile model IPTV TD is recommended to seamlessly switch between different qualities without interrupting the video playback. + +##### **I.3.1.2 Environmental adaptation** + +Environmental adaptation of mobile model IPTV terminal device may improve the service quality by making the sound louder, the display brighter, etc., since service provision environment such as brightness and street noise may change when the IPTV terminal device moves. + +##### **I.3.1.3 Media distribution adaptation** + +Content distribution to a mobile model IPTV TD needs to adapt to the changing of network conditions and terminal devices for better quality of experience. The adaptation may take different forms, such as connection speed, video format, etc. + +Dynamic adaptive streaming over HTTP (DASH) [b-ISO23009-1] defines a way to advertise a range of different streams to a player together with the information it needs to pick which ones to stream. It also defines media file formats suitable for adaptive streaming. The file formats enable efficient and seamless switching between streams, enabling a player to adapt to changing network conditions without pausing playback for re-buffering. The standard considers the differing needs of both on-demand and live services, and it is all based on the use of industry standard HTTP servers. DASH provides flexible deployments of adaptive media distribution for mobile model IPTV TD. + +## Appendix II + +### Example use cases and service scenarios + +(This appendix does not form an integral part of this Recommendation.) + +### II.1 Linear TV service with terminal mobility (horizontal handover) + +Linear TV service is a television service in which a continuous stream flows in real time from the service provider to the terminal device. As one of IPTV basic services, linear TV service can be provided to mobile IPTV service users. This service scenario, as shown in Figure II.1, describes a use case of linear TV service while the service user moves with the mobile IPTV terminal. + +![Diagram illustrating IPTV linear TV service with horizontal handover. A mobile user (cellular phone) moves from base station BS-A to BS-B within a mobile network cloud. The service provider and content provider are connected to the network. The user receives a seamless linear TV service during the handover.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +The diagram shows a mobile network cloud containing two base stations, BS-A and BS-B. A mobile user, represented by a person icon and a cellular phone, is shown moving from BS-A to BS-B. A large arrow labeled 'Seamless linear TV service' indicates the continuous service flow. On the right, a 'Service provider' (represented by a cube icon) and a 'Content provider' (represented by a cylinder icon) are connected to the network cloud. The label 'H.723(16)\_FII.1' is in the bottom right corner. + +Diagram illustrating IPTV linear TV service with horizontal handover. A mobile user (cellular phone) moves from base station BS-A to BS-B within a mobile network cloud. The service provider and content provider are connected to the network. The user receives a seamless linear TV service during the handover. + +**Figure II.1 – IPTV linear TV service with horizontal handover** + +In this scenario, an IPTV user watches news, one of linear TV program, while she moves on foot. While she moves, horizontal handover takes place and the content is provided seamlessly. The service scenario of IPTV linear TV service with horizontal handover is as follows; + +- 1) The cellular phone of IPTV service subscriber Carol accesses the mobile network through base station (BS)-A, the nearest one, while she moves on foot; +- 2) Carol reaches a linear TV service and selects the news content she would like to watch after IPTV service provider discovery and IPTV service discovery procedures; +- 3) The selected news stream starts to deliver to her cellular phone, and she keeps watching the news while she walks; +- 4) After a few minutes, her cellular phone loses the coverage of BS-A and the connected base station is changed from BS-A to BS-B, the one most adjacent to BS-A. Carol keeps watching the news seamlessly. + +### II.2 IPTV broadcast service with personal mobility + +IPTV broadcast service is expected to be available on various kinds of mobile IPTV TDs such as cellular phones and PDAs as one of basic IPTV services. + +![Diagram illustrating IPTV broadcast service with personal mobility. A user (Alice) connects via a cellular phone to a mobile network (BS) and via a laptop computer to an IP network (Wi-Fi AP). Both networks connect to a service provider, which in turn connects to a content provider.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +The diagram shows a user (represented by a person icon) with two devices: a cellular phone and a laptop computer. The cellular phone is connected to a 'Mobile network' cloud via a 'BS' (Base Station) icon. The laptop computer is connected to an 'IP network' cloud via a 'Wi-Fi AP' (Access Point) icon. Both the 'Mobile network' and the 'IP network' clouds are connected to a 'Service provider' (represented by a cube icon). The 'Service provider' is further connected to a 'Content provider' (represented by a cylinder icon). The text 'H.723(16)\_FII.2' is located in the bottom right corner of the diagram area. + +Diagram illustrating IPTV broadcast service with personal mobility. A user (Alice) connects via a cellular phone to a mobile network (BS) and via a laptop computer to an IP network (Wi-Fi AP). Both networks connect to a service provider, which in turn connects to a content provider. + +**Figure II.2 – IPTV broadcast service with personal mobility** + +One service scenario of IPTV broadcast service with personal mobility, shown in Figure II.2, is as follows: + +- 1) The cellular phone of IPTV service subscriber Alice connects to the mobile network; +- 2) Alice accesses an IPTV broadcast service provided by an IPTV service provider with her cellular phone. The IPTV service provider authenticates the subscriber based on the personal identity of Alice to provide the IPTV broadcast service; +- 3) Alice watches TV programs on her cellular phone for some period of time, and then closes the IPTV broadcast service on the cellular phone. The session between the cellular phone and the IPTV service provider is disconnected; +- 4) Alice enters her house and attempts to use an IPTV service with her laptop computer. The laptop computer connects to a Wi-Fi AP and accesses the same IPTV broadcast service that she previously accessed on her cellular phone outside her home. Alice also can consume other IPTV services to which she subscribes. For session establishment between the laptop computer and the IPTV service provider, in the case, Alice is authenticated based on her personal identity, just like the use case of her cellular phone. + +While Alice uses the IPTV broadcast service on various IPTV TDs, personal mobility, the mobility for those scenarios where the user changes the terminal used for network access at different locations, is provided. + +### **II.3 VoD with terminal mobility (vertical handover)** + +VoD is a service in which the end-user can, on demand, select and watch video content and where the end-user can control the temporal order in which the video content is viewed. VoD is also expected to be available on various kinds of mobile IPTV TDs as one of basic IPTV services. + +![Diagram illustrating VoD with terminal mobility. A laptop computer in Wi-Fi mode connects to a Wi-Fi AP inside a house. The Wi-Fi AP is connected to an IP network cloud. The IP network cloud is connected to a Service provider (represented by a cube) and a Content provider (represented by a cylinder). A vertical handover arrow points from the laptop in Wi-Fi mode to the laptop in Mobile WiMAX mode. The laptop in Mobile WiMAX mode connects to a Mobile WiMAX Base station (represented by a tower). The Mobile WiMAX Base station is connected to a Mobile network cloud. The diagram is labeled H.723(16)_FII.3.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +Diagram illustrating VoD with terminal mobility. A laptop computer in Wi-Fi mode connects to a Wi-Fi AP inside a house. The Wi-Fi AP is connected to an IP network cloud. The IP network cloud is connected to a Service provider (represented by a cube) and a Content provider (represented by a cylinder). A vertical handover arrow points from the laptop in Wi-Fi mode to the laptop in Mobile WiMAX mode. The laptop in Mobile WiMAX mode connects to a Mobile WiMAX Base station (represented by a tower). The Mobile WiMAX Base station is connected to a Mobile network cloud. The diagram is labeled H.723(16)\_FII.3. + +**Figure II.3 – VoD with terminal mobility** + +Service scenario of VoD with terminal mobility, shown in Figure II.3, is as follows: + +- 1) A laptop computer of IPTV service subscriber Bob, connects to a Wi-Fi AP at home. +- 2) Bob accesses a VoD service provided via the IPTV service provider to which he has subscribed. +- 3) While Bob watches VoD content, he starts to ride in a car to move to another location. After a few seconds from departing his house, Bob's laptop computer moves out of the coverage range of the Wi-Fi AP to which the laptop computer was initially connected. +- 4) The laptop computer then searches for another signal it can use to get IP connectivity. It finds a signal from a mobile worldwide interoperability for microwave access (WiMAX) base station and connects to this base station. +- 5) The network access mode of the laptop computer is changed from Wi-Fi mode to mobile WiMAX mode. Bob continuously uses the VoD service on the laptop computer. + +While Bob uses a VoD service on his laptop computer with movement, terminal mobility, the mobility for those scenarios where the same terminal equipment is moving or is used at different locations, is provided. To be more concrete, vertical handover, handover between different networks, is supported by the laptop computer. + +Since the network access service which Bob uses changes from Wi-Fi to mobile WiMAX, audio/video (A/V) quality adaptation may be supported by the IPTV service provider considering bandwidth of each network access technology, etc. Service mobility may or may not be provided according to the network access technologies used before and after the vertical handover. + +### **II.4 Three-screen service with contents sharing** + +Three-screen service allows an IPTV service subscriber consume IPTV service contents on TV, PC, and wireless screens. The basic type of three-screen service is sharing the same IPTV service contents on more than one screen among the three types of screens. + +![Diagram of a three-screen service with content sharing. A house contains a Television, a PC, and a Cellular phone, all displaying 'Content A'. The Television and PC are connected to an 'IP network' cloud. The Cellular phone is connected to a 'Mobile network' cloud via a 'BS' (Base Station). The 'IP network' cloud is connected to a 'Service provider' (cube icon), which is connected to a 'Content provider' (cylinder icon). The 'Mobile network' cloud is also connected to the 'Service provider'. A label 'H.723(16)_FII.4' is in the bottom right corner.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +Diagram of a three-screen service with content sharing. A house contains a Television, a PC, and a Cellular phone, all displaying 'Content A'. The Television and PC are connected to an 'IP network' cloud. The Cellular phone is connected to a 'Mobile network' cloud via a 'BS' (Base Station). The 'IP network' cloud is connected to a 'Service provider' (cube icon), which is connected to a 'Content provider' (cylinder icon). The 'Mobile network' cloud is also connected to the 'Service provider'. A label 'H.723(16)\_FII.4' is in the bottom right corner. + +**Figure II.4 – Three-screen service with contents sharing** + +An IPTV service scenario in which many IPTV service users share the same IPTV content, as shown in Figure II.4, is as follows; + +- 1) Eve, an IPTV service subscriber, and her friends want to watch a movie at Eve's home. Eve wants to watch the movie on her cellular phone, and others want to watch the movie on a television and a PC. +- 2) The cellular phone of Eve accesses the mobile network. She reaches the IPTV service to which she is subscribed and reaches a VoD service after IPTV service completion of the discovery procedure. She selects the movie she and her friends plan to watch. +- 3) She requests the IPTV service provider that she wants to use the three-screen service with the selected VoD content, which means that Eve's TV, PC, and cellular phone show the same VoD content simultaneously. +- 4) The IPTV service provider receives capability information of each IPTV terminal, adapt audio and video of the content for these screens, considering these capabilities, and then delivers the content to these IPTV TDs. Eve and her friends watch the same movie on these three screens. + +For the provision of three-screen service in this scenario, capability information of each terminal device needs to be delivered to the IPTV service provider. Then, the IPTV service provider adapts the IPTV contents to the screens considering the capabilities of each terminal device. + +### **II.5 Three-screen service with service mobility** + +Three-screen service allows an IPTV service subscriber to consume IPTV service content on TV, PC, and wireless screens seamlessly. It is considered as one of the representative IPTV services supporting service mobility among three types of screens. + +![Diagram of three-screen service with service mobility. A house contains a Television (in living room), a Laptop (In room A), and a Cellular phone (In room B). A 3-Screen service user is shown. The Television, Laptop, and Cellular phone are connected to a Wi-Fi AP inside the house. The Wi-Fi AP is connected to an IP network cloud. The IP network cloud is connected to a Service provider (cube icon) and a Content provider (cylinder icon). The Cellular phone is also connected to a Mobile network cloud via a BS (Base Station) icon. Arrows indicate the flow of service from the Service provider and Content provider through the IP network and Mobile network to the user's devices. A label H.723(16)_FII.5 is in the bottom right.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +Diagram of three-screen service with service mobility. A house contains a Television (in living room), a Laptop (In room A), and a Cellular phone (In room B). A 3-Screen service user is shown. The Television, Laptop, and Cellular phone are connected to a Wi-Fi AP inside the house. The Wi-Fi AP is connected to an IP network cloud. The IP network cloud is connected to a Service provider (cube icon) and a Content provider (cylinder icon). The Cellular phone is also connected to a Mobile network cloud via a BS (Base Station) icon. Arrows indicate the flow of service from the Service provider and Content provider through the IP network and Mobile network to the user's devices. A label H.723(16)\_FII.5 is in the bottom right. + +**Figure II.5 – Three-screen service with service mobility** + +Service scenario of three-screen service with service mobility, as shown in Figure II.5, is as follows: + +- 1) IPTV service subscriber Charlie, watches a VoD content on a television in his living room. +- 2) After a few minutes, Charlie moves to room A to watch the same VoD content on his laptop computer: + - 2-1) Charlie turns on a laptop in room A and requests the laptop to show the same VoD content continuously which the television in the living room showed; + - 2-2) the laptop connects to Wi-Fi AP; + - 2-3) the laptop is authenticated as part of a three-screen service, and requests the IPTV service provider to send the same VoD content; + - 2-4) the IPTV service provider verifies the information about Charlie and the VoD service which Charlie uses and sends the same content to the laptop computer; + - 2-5) Charlie watches the VoD content seamlessly on the laptop computer. During this process, A/V quality adaptation may be supported by the IPTV service provider considering the capabilities of IPTV TDs and bandwidth of network access technologies. +- 3) After some period of time, Charlie moves to room B and uses his cellular phone to watch the same VoD content continuously. The cellular phone connects to a mobile network and shows the same VoD content through the same process as described above. A/V quality adaptation may also be supported considering the capabilities of the cellular phone and bandwidth of the mobile network. + +While Charlie uses the the IPTV VoD service on a television, a laptop computer and a cellular phone seamlessly, service mobility, which provides seamless IPTV service irrespective of the location of the user and the IPTV terminal device, is provided. Content protection related issues should be taken into consideration when sharing IPTV contents on several IPTV TDs. + +### II.6 Location based information service + +A location-based service (LBS) is an information and entertainment service, accessible with mobile devices through the mobile network and utilizing the ability to make use of the geographical position of the mobile device. LBS can be provided to mobile IPTV service users since mobile IPTV terminal device has mobility. + +![Diagram of a location-based information service architecture. A cellular phone with a USIM Card and GPS receiver is connected to a Base Station (BS) within a Mobile network cloud. The BS is connected to a Service provider, which is connected to a Content provider. Dashed arrows show 'Location-based information' being sent from the Service provider to the phone, and 'Location information' being sent from the phone to the Service provider. A reference code H.723(16)_FII.6 is present in the bottom right of the diagram.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +Diagram of a location-based information service architecture. A cellular phone with a USIM Card and GPS receiver is connected to a Base Station (BS) within a Mobile network cloud. The BS is connected to a Service provider, which is connected to a Content provider. Dashed arrows show 'Location-based information' being sent from the Service provider to the phone, and 'Location information' being sent from the phone to the Service provider. A reference code H.723(16)\_FII.6 is present in the bottom right of the diagram. + +**Figure II.6 – Location-based information service** + +A user wants to receive information about restaurants in an unfamiliar area in which he is staying through a mobile IPTV service. A service scenario of location based information service, as shown in Figure II.6, is as follows: + +- 1) Frank rents a mobile IPTV TD with GPS receiver from a rental shop and put his universal subscriber identity module (USIM) into the terminal. +- 2) The mobile IPTV TD accesses the mobile network and Frank is authenticated by the IPTV service provider to which he has subscribed. +- 3) Frank reaches a location-based information service on the terminal after the IPTV service discovery procedure has completed. +- 4) The mobile IPTV TD determines its location using GPS and sends the location information to the IPTV service provider. +- 5) When Frank select "restaurant" in location-based information service, information about restaurants in the area where Frank is currently located is delivered to him. If he agrees, the delivery of advertisements of some of these restaurants is also possible. +- 6) After Frank receives the information about his favourite restaurant, including exact location and telephone number, the LBS is terminated. + +In the provision of the abovementioned IPTV service, the user is authenticated by the USIM. For the provision of location-based IPTV service, location of the terminal is determined using GPS. Although location information determined by the network operator can also be available, the location information determined by GPS is usually more accurate. + +## Bibliography + +- [b-ITU-T H.262] Recommendation ITU-T H.262 (2012), *Information technology - Generic coding of moving pictures and associated audio information: Video*. +- [b-ITU-T H.264] Recommendation ITU-T H.264 (2016), *Advanced video coding for generic audiovisual services*. +- [b-ITU-T H.510] Recommendation ITU-T H.510 (2002), *Mobility for H.323 multimedia systems and services*. +- [b-ITU-T P.910] Recommendation ITU-T P.910 (2008), *Subjective video quality assessment methods for multimedia applications*. +- [b-ITU-T Q.1221] Recommendation ITU-T Q.1221 (1997), *Introduction to Intelligent Network Capability Set 2*. +- [b-ITU-T Q.1706] Recommendation ITU-T Q.1706/Y.2801 (2006), *Mobility management requirements for NGN*. +- [b-ITU-T Q.1721] Recommendation ITU-T Q.1721 (2000), *Information flows for IMT-2000 capability set 1*. +- [b-ITU-T Q.1761] Recommendation ITU-T Q.1761 (2004), *Principles and requirements for convergence of fixed and existing IMT-2000 systems*. +- [b-ITU-T Q.1762] Recommendation ITU-T Q.1762/Y.2802 (2007), *Fixed-mobile convergence general requirements*. +- [b-ITU-T Y.2001] Recommendation ITU-T Y.2001 (2004), *General overview of NGN*. +- [b-ITU-T Y.2201] Recommendation ITU-T Y.2201 (2007), *NGN release 1 requirements*. +- [b-ITU-R BT.500-13] Recommendation ITU-R BT.500-13 (2012), *Methodology for the subjective assessment of the quality of television pictures*. +- [b-ISO23009-1] ISO/IEC 23009-1:2014, *Information technology – Dynamic adaptive streaming over HTTP (DASH) Part 1: Media presentation description and segment formats*. + + + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.740-201003-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/H/T-REC-H.740-201003-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87439043f695468944a8c08a506938c129fef5bc --- /dev/null +++ b/marked/H/T-REC-H.740-201003-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd55727629e44e0d65be6d7b7317bfa6a3ca444d26131b749cdf945fd0734709 +size 274331 diff --git a/marked/H/T-REC-H.740-201003-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.740-201003-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb19ba4586539f3854a84f079853033a1473be0 --- /dev/null +++ b/marked/H/T-REC-H.740-201003-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:027c19b7ad1fd1114129f475def233bb3c3283520e8a142008237f1eb4f96e4f +size 92312 diff --git a/marked/H/T-REC-H.740-201003-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.740-201003-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04ed0575fb17e6faeb57d9d81b58c3b85f7e21df --- /dev/null +++ b/marked/H/T-REC-H.740-201003-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3223bb567d6cdfacad7ced972fc4eab63d7b0659969b11a4801458bec7649f19 +size 3852 diff --git a/marked/H/T-REC-H.740-201003-I_PDF-E/b0211cee4b20034939d883ac0d70f696_img.jpg b/marked/H/T-REC-H.740-201003-I_PDF-E/b0211cee4b20034939d883ac0d70f696_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10853299b4e35fccdebc04b2f06819e6a26be8b1 --- /dev/null +++ b/marked/H/T-REC-H.740-201003-I_PDF-E/b0211cee4b20034939d883ac0d70f696_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c14f86f765835c292f338cb4e8be0bb238e079742024c2c1421fded672ff8ca +size 14989 diff --git a/marked/H/T-REC-H.740-201003-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/H/T-REC-H.740-201003-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9152c3a7304b9f61470070a64a940f9d274b9359 --- /dev/null +++ b/marked/H/T-REC-H.740-201003-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72f36ea096f34ee02ee03e21aa44a0e18ad6d2e54dfa8b965f2364beffec2e50 +size 62536 diff --git a/marked/H/T-REC-H.740-201003-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/H/T-REC-H.740-201003-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482690d0235bce0f17d6e0930c997c299076f114 --- /dev/null +++ b/marked/H/T-REC-H.740-201003-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02891c3b29655c004fcda6fa2c92eed4c352dc6de2e8c42cd5dded354c9a5567 +size 39797 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1f677bb15c43056833da1313724dbf995a9bfbc --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfe4ca8de201a4ed30f7bfec795f3d181b22128808c017c608ba2e5722851005 +size 3639 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42b0a67c049615a6a765271486c95c4c8d1fe470 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70576a577332c86042ac0f78566dbb301698b88c3012053306a253f3a7983354 +size 4180 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ad98c6e45b6c52f074f0054407ca88a640d8f1d --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58019f38be268f19eaa80c6d56d0f6b39d5741569a8f3ccc04117fa95d9c6465 +size 4016 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e604946947f5e71fa836945223068133a79c2f57 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9c7084cc03742557342a208b3f39c2427d524e2d9ec59fc499b7bb7c9370c77 +size 12140 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a08d3e00518bdde67560b3687f4bf614b529153 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dac149a50ab4906389c98919e2da343813779b720eb50649d89c6955d7456113 +size 29482 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..448e0c36c999e23ca64147b28f0d91cb0b5bde02 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f2af8b553bad7aedeae69c4675f0a724bcb4b9e719f414fc5013b01af7baa44 +size 48060 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..825238fc15c0d0a0ff3b74d2460b07a043ddfd01 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e85e8405c7f8490dc6312366bc07f308e5e7c954f2809301246244ac5a72655b +size 61342 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21afe027849ed9c5ce22efdf58ca8ca4a6b41b21 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbbc79cba82e36226bc15c9d33e3c4e78fb8864c450c64406e20973eb08247dd +size 43716 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f522fcf709f9809c234942f69e7b70f3d8e41a6d --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:500fd13e95d92cee8bdcf1878025d3cecd8520ab4a1ca2775586a519a53fa6e5 +size 65366 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d726f688a483c9a0515651285954dd4d355953fd --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dab998886a9a007a9bb41ab2d90050e6d23ede2e274c2204ff4d255116ade3e8 +size 54197 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69ddf23c6a04ad57e097c4e513d6522d0eeade75 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ab9124c04677163e4aa60f04ab03b8516107622c80e07512217a20a1faac2d1 +size 47643 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aecfaebc70aa46b59405d7af232ab548d7b54681 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db2d418063a957482c3584dd98607f322c15faac7d563edb525af713043758b9 +size 69379 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/H/T-REC-H.741.0-201203-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbd387a6c029ea84be87e5e2fab06e18e6d8b207 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b767f259126280e0c311dc876661b287956666c3f2927f1a1252dd036fdf8db9 +size 94781 diff --git a/marked/H/T-REC-H.741.0-201203-I_PDF-E/raw.md b/marked/H/T-REC-H.741.0-201203-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f29b2345bd3af4d37f5c5d492f77ed88bf8a40e2 --- /dev/null +++ b/marked/H/T-REC-H.741.0-201203-I_PDF-E/raw.md @@ -0,0 +1,757 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.741.0** + +(03/2012) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +IPTV application event handling + +--- + +**IPTV application event handling: Overall +aspects of audience measurement for IPTV +services** + +Recommendation ITU-T H.741.0 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.741.0 + +## IPTV application event handling: Overall aspects of audience measurement for IPTV services + +## Summary + +Recommendation ITU-T H.741.0 defines a foundational platform for audience measurement (AM) of Internet Protocol television (IPTV) services. This Recommendation focuses on the interface between terminal devices (TDs) and an audience measurement aggregation function. + +The AM platform integrates a method for end users to report personal information, and is designed to easily add time-shifted and interactive services, and non-terminal device measurement points. While ITU-T H.741.0 allows the implementation of audience measurement for IPTV services, its mechanism may be equally applicable to non-IPTV services. + +The audience measurement mechanism specified here provides additional benefits when compared to traditional audience measurement. Such benefits include, in particular, a larger audience population sample, more detailed engagement metrics, passive data collection, and feedback for the enhancement of services. + +The design philosophy in ITU-T H.741.0 is focused on scalability, on minimizing the use of resources, on optimizing security, on flexibility to support a variety of service provider deployments, and on a rich set of privacy settings to meet emerging regulations and legislation. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.741.0 | 2012-03-22 | 16 | + +## Keywords + +Audience measurement, audience rating service, contents rating, distributed content service, end-user permission, engagement metrics, interactive services, IPTV application event handling, linear TV, personalized service, privacy protection. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2012 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 5 | +| 5 Conventions ..... | 5 | +| 6 Overview ..... | 6 | +| 7 Requirements ..... | 7 | +| 7.1 Audience measurement architecture requirements..... | 7 | +| 7.2 Recommendations for audience measurement architecture ..... | 8 | +| 7.3 Optional requirements for audience measurement architecture ..... | 9 | +| 7.4 Recommended requirements for end-user permits..... | 9 | +| 7.5 Recommended requirements for operators..... | 9 | +| 7.6 Recommended requirements for IPTV architecture..... | 10 | +| 8 IPTV architecture and audience measurement ..... | 10 | +| 9 Audience measurement lifecycle..... | 11 | +| 10 Configuration of terminal device audience measurement functions ..... | 12 | +| 11 Measurement reporting of TD-AMFs..... | 13 | +| 12 Privacy in audience measurement ..... | 14 | +| 12.1 End-user permission levels..... | 14 | +| 12.2 Permission modes..... | 14 | +| Appendix I – Potential relationships between end users, audience measurement service providers and content distribution service providers..... | 16 | +| I.1 Service provider offering both content distribution and audience measurement services ..... | 16 | +| I.2 Separate audience measurement service and content distribution service providers ..... | 16 | +| I.3 Multiple audience measurement service providers ..... | 17 | +| Appendix II – Context of audience measurement..... | 19 | +| Bibliography..... | 20 | + + + +# Recommendation ITU-T H.741.0 + +# IPTV application event handling: Overall aspects of audience measurement for IPTV services + +## 1 Scope + +This Recommendation describes the overall aspects of audience measurement for Internet Protocol television (IPTV) services. It specifies the requirements and architecture for IPTV audience measurement and describes configuration, measurement reporting, and privacy. + +This Recommendation presents the functions related to audience measurement (AM) that are distributed over the IPTV architecture. Audience measurements are constrained to the communication interface(s) between terminal device audience measurement functions (TD-AMFs) and measurement aggregation functions. Subsequent Recommendations are anticipated to address communication interface(s) with audience measurement functions that are located within other functions of the IPTV architecture. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.740 Amd.1]            Recommendation ITU-T H.740 (2010) Amd.1 (2011), *Application event handling for IPTV services, Amendment 1: New video handling sensor event scenario in Appendix II*. +- [ITU-T X.1191]                Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects*. +- [ITU-T Y.1901]                Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services*. +- [ITU-T Y.1910]                Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 application** [b-ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services. + +**3.1.2 application event** [ITU-T H.740 Amd.1]: An application event is every user interaction or occurrence related with multimedia contents in IPTV applications. It includes an emergency event from event notification services. + +**3.1.3 authorization** [b-ITU-T X.800]: The granting of rights, which includes the granting of access based on access rights. + +- 3.1.4 confidentiality** [b-ITU-T X.800]: The property that information is not made available or disclosed to unauthorized individuals, entities, or processes. +- 3.1.5 content (object)** [b-ITU-T T.174]: Encoded generic value, media or non-media data. +- 3.1.6 electronic program guide (EPG)** [b-ITU-T H.721 Amd.1]: A service navigation application which is used especially for scheduled linear programs. +- NOTE 1 – in some traditional Broadcast Services, EPG is defined as an on-screen guide used to display information on scheduled live broadcast television programs, allowing a viewer to navigate, select, and discover programs by time, title, channel, genre. This traditional definition does not cover "catalogues" for on-demand and download services (sometimes called Electronic Content Guide (ECG), Broadband Content Guide, BCG) and bi-directional interactive service (sometimes called Interactive Program Guide, IPG) for end-user interaction with a server or head-end. +- 3.1.7 end user** [ITU-T Y.1910]: The actual user of the products or services. +- NOTE 2 – The end user consumes the product or service. An end user can optionally be a subscriber. +- 3.1.8 integrity** [IEC/ISO 27001], [IEC/ISO 27002]: Safeguarding the accuracy and completeness of information and processing methods. +- 3.1.9 IPTV** [ITU-T Y.1901]: Multimedia services such as television/video/audio/text/graphics/data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. +- 3.1.10 IPTV terminal device** [ITU-T Y.1901]: A terminal device which has IPTV terminal function (ITF) functionality, e.g., an STB. +- 3.1.11 IPTV terminal function (ITF)** [ITU-T Y.1901]: The end-user function(s) associated with a) receiving and responding to network control channel messages regarding session set-up, maintenance, and tear-down, and b) receiving the content of an IP transport from the network and rendering. +- 3.1.12 key** [b-ITU-T X.800]: A sequence of symbols that controls the operations of encipherment and decipherment. +- 3.1.13 linear TV** [ITU-T Y.1901]: A television service in which a continuous stream flows in real time from the service provider to the terminal device and where the end user cannot control the temporal order in which contents are viewed. +- 3.1.14 metadata** [ITU-T Y.1901]: Structured, encoded data that describe characteristics of information-bearing entities to aid in the identification, discovery, assessment, and management of the described entities. +- NOTE 3 – EPG metadata has many applications and may vary in depth from merely identifying the content package title or information to populate an EPG to providing a complete index of different scenes in a movie or providing business rules detailing how the content package may be displayed, copied, or sold. +- 3.1.15 peer-entity authentication** [b-ITU-T X.800]: The corroboration that a peer entity in an association is the one claimed. +- 3.1.16 privacy** [b-ITU-T X.800 Amd.1]: The right of individuals to control or influence what information related to them may be collected and stored and by whom and to whom that information may be disclosed. +- 3.1.17 repudiation** [b-ITU-T X.800]: Denial by one of the entities involved in a communication of having participated in all or part of the communication. +- 3.1.18 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications. +- 3.1.19 service navigation** [b-ITU-T H.720]: A process of presenting information that allows the end user to discover, select and consume services. + +**3.1.20 service provider** [b-ITU-T M.1400]: A general reference to an operator that provides telecommunication services to customers and other end users either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. + +**3.1.21 set-top box (STB)** [b-ITU-T J.183]: A hardware box that contains digital signal demodulator, de-multiplexer, MPEG-2 decoder, other functionalities and interfaces related to digital signal reception and presentation of the distributed programme at the subscriber's site. + +**3.1.22 stream** [b-ITU-T J.200]: A unidirectional continuous flow of content. + +**3.1.23 subscriber** [b-ITU-T M.3050.1]: The subscriber is responsible for concluding contracts for the services subscribed to and for paying for these services. + +**3.1.24 terminal device (TD)** [ITU-T Y.1901]: An end-user device which typically presents and/or processes the content, such as a personal computer, a computer peripheral, a mobile device, a TV set, a monitor, a VoIP Terminal or an audio-visual media player. + +**3.1.25 video-on-demand (VoD)** [ITU-T Y.1901]: A service in which the end user can, on demand, select and view a video content and where the end user can control the temporal order in which the video content is viewed (e.g., the ability to start the viewing, pause, fast forward, rewind, etc.). + +### **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 aggregation function:** The function that configures audience measurement functions (AMFs), then receives processed events, sample values and end-user information from AMFs. It may participate in the communication of end-user permissions. + +**3.2.2 audience information:** The overall information about end-user behaviour, and the related end-user information, during the time that IPTV audience measurement is inactive. + +**3.2.3 audience measurement:** The measurement of people's engagement with IPTV services. + +**3.2.4 audience measurement data:** End-user behaviour data which is related to a service and content consumption, combined or not with end-user information. + +**3.2.5 audience measurement function (AMF):** The function that, if given permission, measures the end-user behaviour by processing events or samples from IPTV services. AMFs may request and collect end-user information. AMFs transfer processed events, samples and end-user information to aggregation functions. + +**3.2.6 audience measurement service provider:** A service provider providing audience measurement services. An audience measurement service provider configures an audience measurement system to control what audience information the system collects. + +**3.2.7 audience measurement system:** The system which, with end-user permission, measures end-user behaviour by detecting application events within the IPTV service and collecting their data within the IPTV service. + +**3.2.8 audience rating:** The quantitative measurement of the size and composition of an audience that viewed content for given periods of time, throughout transmission of that content. Derived metrics include average audience rating, total audience rating, rating points, and cumulative (unduplicated) audience rating. + +NOTE – Traditionally, ratings have been extrapolated from audience sample surveys. However, passive measurement from digital systems can provide a larger audience sample. Examples of use include support to financial negotiations, determination of estimated costs to reach sizes of audience segments, and scheduling of content distribution. + +**3.2.9 configuration package:** A configuration package is the data structure which specifies the target services to be measured, content filtering, measurement schedule, events and samples to be measured, and measurement report delivery. + +**3.2.10 content consumption:** A series of valid operation actions to complete selecting an IPTV service and consuming the related content based on the procedure flow within the IPTV system. + +**3.2.11 content rating:** Actively asserted opinions evaluating aspects of content, using a position assigned on a defined scale, to communicate those aspects to others. Scales may be industry standard, or not. Example scales include, among others, the Motion Picture Association of America (MPAA), a number of stars, and thumbs up or down. + +NOTE – Examples of use include the indicating of suitability for audience segments, censorship, and levels of entertainment, quality, popularity; content optimization and targeting across audience segments, and content recommendation. + +**3.2.12 controlled information:** A classification of end-user information that can be used alone or easily in combination with other information to uniquely identify, contact, or locate an end user or subscriber, in line with Annex A of [ITU-T X.1191]. + +**3.2.13 digital destination:** The result of navigation across services, including channels, applications, or portals. + +**3.2.14 directive(s):** Instructions that are input as part of an order from stakeholders to the AM system regarding target audiences, what and how to measure, and what to report back to stakeholders. + +**3.2.15 end-user behavioural information:** A part of audience measurement information which includes "application events" and/or "end-user context". An "application event" is information reflecting the behaviour of an IPTV service end user. "End-user context" is information relating to the situation when an "application event" was generated. + +**3.2.16 end-user information:** "End-user info" is information about an IPTV service end user. It includes "identifying end-user information" and "non-identifying generic user information". + +**3.2.17 engagement metric:** A measure of the level of involvement, interaction, sentiment, and promotion that an end user has with content. It provides a more holistic view of end users than audience ratings. Examples of involvement metrics include time spent or frequent watcher. Examples of interaction metrics include replay and requests for information. Examples of sentiment metrics include associated amount of chat and words used. Examples of promotion metrics include forwarding to friends or posting to a blog. + +NOTE – Example uses include focus on acquisition of evangelists, finer granularity audience targeting, and emerging uses. + +**3.2.18 identifying end-user information:** Information including, for example, biographics (birth date, birth location, gender, address, etc.). + +**3.2.19 measurement report:** The data that the audience measurement function (AMF) generates from an end-user behaviour event or sample. + +**3.2.20 non-identifying generic end-user information:** Information such as demographics (race, income, disabilities, education, home ownership, and employment status) and psychographics (interests, activities, opinions, attitudes, and values). + +**3.2.21 sample:** A sample is a periodic action occurring on a configurable schedule time interval, during a service period, which captures specified information values. + +**3.2.22 sample time:** A sample time is when an instance of the periodic action occurs on a configurable schedule time interval, which captures specified information values, during a service period. + +**3.2.23 sample value:** The content of an information field, captured at a specific instance of periodic action occurring on a configurable schedule time interval, during a service period. + +**3.2.24 subscriber information:** Similar to the definition of end-user information, it includes the "user info" of the person responsible for concluding contracts for the services subscribed to and for paying for these services. + +NOTE – The subscriber information may be used as a proxy for another associated user's information. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|------------------------------------------------| +| AM | Audience Measurement | +| AMF | Audience Measurement Function | +| BCG | Broadband Content Guide | +| CD-AMF | Content Delivery Audience Measurement Function | +| c-PVR | consumer Personal Video Recorder | +| EPG | Electronic Program Guide | +| HN-AMF | Home Network Audience Measurement Function | +| IPG | Interactive program guide | +| IPTV | Internet Protocol Television | +| ITF | IPTV Terminal Function | +| N-AMF | Network Audience Measurement Function | +| n-PVR | network Personal Video Recorder | +| PC | Personal Computer | +| PVR | Personal Video Recorder | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| SC-AMF | Service Control Audience Measurement Function | +| SP | Service Provider | +| STB | Set-Top Box | +| TD | Terminal Device | +| TD-AMF | Terminal Device Audience Measurement Function | +| VoD | Video on Demand | +| VoIP | Voice over Internet Protocol | + +## 5 Conventions + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed, and from which no deviation is permitted, if conformance to this document is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and that the feature can be optionally enabled by the network operator/service provider. Rather, it means that the vendor may optionally provide the feature and still claim conformance with the specification. + +The keyword "functions" is defined as a collection of functionalities. It is represented by the following symbol in the context of IPTV architecture: + +![A rounded rectangular box containing the word 'Functions'.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +A rounded rectangular box with a light gray fill and a thin black border. The word "Functions" is centered inside the box in a black, sans-serif font. + +A rounded rectangular box containing the word 'Functions'. + +The keywords "functional block" are defined as a group of functionalities that have not been further subdivided at the level of detail described in this Recommendation. It is represented by the following symbol in the context of IPTV architecture: + +![A rectangular box containing the words 'Functional block'.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +A rectangular box with a light gray fill and a thin black border. The words "Functional block" are centered inside the box in a black, sans-serif font. + +A rectangular box containing the words 'Functional block'. + +NOTE – In the future other groups or other Recommendations may possibly further subdivide these functional blocks. + +## 6 Overview + +Audience measurement (AM) measures end-user behaviour with end-user permission in IPTV services. + +Service providers may use audience measurement data themselves, and choose to provide audience measurement services to others. Measurement services may be provided in real-time or offline. Users of these services may use the audience measurement data to forecast advertising opportunities within content and digital destinations, forecast audience segment visits across digital destinations, craft and optimize programs and playlists, and craft and optimize target-specific advertisements and advertising campaigns for particular audience segments across devices. Offline uses include lead generation, impact analysis (sales uplift due to number of engaged advertisements), and media content planning. + +Audience measurement is implemented by an IPTV application associated with a subset of IPTV services that collects the data of end-user behaviours of these services. For example, in linear TV, audience measurement may inform an audience rating service about the audience presence and engagement during a content provider's content. The targeted IPTV services for audience measurement include: + +- 1) Distributed content services [b-ITU-T Y.Sup5]: examples include linear TV, video on demand (VoD), network personal video recorder (n-PVR), and consumer personal video recorder (c-PVR). +- 2) Interactive services [b-ITU-T Y.Sup5]: examples include games, learning, commerce, and information access. + +Measurement is passively obtained without special end-user interaction as these services are consumed, or it may be actively obtained by requesting end-user interaction (e.g., survey). + +Specific audience measurement requirements and functions for distributed content services are described elsewhere (e.g., see [b-ITU-T H.741.3]). + +The primary audience measurement functions, when permitted by end users, include: + +- 1) collecting end-user behaviour information, as observed by application events related to IPTV services +- 2) collecting end-user information, as disclosed by end users and end-users' devices. + +## **7 Requirements** + +### **7.1 Audience measurement architecture requirements** + +IPTV architecture with audience measurement is called AM architecture. + +- 1) The AM architecture is required to support the audience measurement of IPTV services as permitted by end users. +- 2) The AM architecture is required to have the ability to receive and process multiple audience input orders from multiple stakeholders (content providers, advertisers, audience rating companies, and IPTV service providers). +- 3) The AM architecture is required to have the ability to create requested audience measurement reports for stakeholders, and send those reports to the corresponding stakeholders. +- 4) The AM architecture is required to have the ability to measure audience behaviour by selection of IPTV terminal devices to be measured. +- 5) The AM architecture is required to have the ability to measure audience behaviour by selection of IPTV services to be measured. +- 6) The AM architecture is required to have the ability to measure audience behaviour by selection of behavioural events to be measured. +- 7) The AM architecture is required to have the ability to measure audience behaviour by selection of periodicity for periodic measurements. +- 8) The AM architecture is required to support mechanisms to support policies associated with multiple end-user permission levels which permit disclosure of incremental sets of their audience measurement information. +- 9) The AM architecture is required to support monitoring or communications with IPTV services, for audience measurement. +- 10) The AM architecture is required to support communications with other applications, for audience measurement. +- 11) The AM architecture is required to support an internal configuration procedure for all AM components which directs measurement, reporting, control and processing operations. +- 12) The AM architecture is required to support distributed measurement filtering and summarisation. +- 13) The AM architecture is required to support traffic shaping of measurement reporting. +- 14) The AM architecture is required to ensure confidentiality of end-user's AM data in transit. +- 15) The AM architecture is required to ensure the integrity of AM information communicated between AM entities. +- 16) The AM architecture is required to ensure that there is no direct or indirect leakage of end-users' privacy, protecting against violation of information through leakage to unintended parties while performing AM operations. +- 17) The AM architecture is required to ensure that peer-entity authentication precedes communication between AM peer entities. + +- 18) The AM architecture is required to ensure that there is no unauthorized access to end-user's AM data. +- 19) The AM architecture is required to provide a non-repudiation property to AM information communicated between AM entities. +- 20) The AM architecture is required to ensure that the algorithms or mechanisms for authentication, authorization, confidentiality, privacy, integrity, and repudiation are built using publicly available and standardized cryptographic algorithms. + +### **7.2 Recommendations for audience measurement architecture** + +- 1) The AM architecture is recommended to have the ability to create requested audience measurement reports for other IPTV applications, and to send those IPTV application reports to the appropriate IPTV applications. +- 2) The AM architecture is recommended to support stakeholder input orders, measurements, and stakeholder and other IPTV application reports having measurements of viewing behaviour specified by combinations of: + - a) time of day + - b) end-user behaviour + - c) sample times + - d) end-user information + - e) end-user device information + - f) end-user device location. +- 3) The AM architecture is recommended to support end-user permissions applicable to sets of IPTV devices used by an end user (e.g., all TVs, all PCs, all mobiles, and all devices). +- 4) The AM architecture is recommended to support at least daily or less frequent changes to configuration without measurement service interruption. +- 5) The AM architecture is recommended to support scheduling of configuration changes. +- 6) The AM architecture is recommended to support mechanisms which react to more restrictive end-user permissions being set online within one hour. +- 7) The AM architecture is recommended to support selection of end users to be monitored for audience measurement. +- 8) The AM architecture is recommended to support a broad granularity of measurements. +- 9) The AM architecture is recommended to support recovery from storage congestion. +- 10) The AM architecture is recommended to support recovery from network congestion. +- 11) The AM architecture is recommended to minimize the acquisition, locations and duration of storage, and transmissions of end-user's personal data necessary for delivering the AM services. +- 12) The AM architecture is recommended to classify the end-users' personal data into data that requires control and data that does not require control. +- 13) The AM architecture is recommended to ensure that any end-user's personal data acquired can be completely deleted either by an end user or a service provider. +- 14) The cryptographic algorithms, used in AM architecture, that require use of cryptographic keys are recommended to have sufficiently large key entropy to effectively protect the AM data from cryptanalysis. +- 15) The choice of cryptographic algorithms, used in AM architecture, is recommended to be efficiently implementable for both hardware and/or software implementations. + +- 16) The cryptographic algorithms, used in AM architecture, are recommended to be scalable and future-proof, i.e., cryptographic parameters (such as key-length, key-renewal periods, etc.) or cryptographic modes (such as CBC, OFB, ECB, etc.). + +### **7.3 Optional requirements for audience measurement architecture** + +- 1) The AM architecture can optionally support input orders, measurements, stakeholder and other IPTV application reports having measurements of viewing behaviour specified by combinations of: + - a) day of week + - b) end-user information + - c) distributed content services (linear, VoD, etc.) + - d) content + - e) interactive services (applications). +- 2) The architecture can optionally support the ability to configure on a per user basis, a per content basis, or a combination of both. + +NOTE – Derived from RR.6.1-11 in [ITU-T Y.1901]. + +- 3) The architecture can optionally support the ability to ask for the end user's permission or to check with already captured end-user permission prior to starting measurements. +- 4) The AM architecture can optionally support downloading, installation, updating, and removal of any audience measurement software. +- 5) Audience measurement data can optionally include identification of end users (given end-user permission). +- 6) The AM architecture can optionally support presence detection. + +### **7.4 Recommended requirements for end-user permits** + +- 1) End-user permits are recommended to be granted for a specific duration. +- 2) End-user permits may optionally be based upon: + - a) distributed content services (e.g., linear, VoD, PVR) + - b) content type (e.g., children's TV, adult TV, religious, political, etc.) + - c) event type (e.g., channel change, record, etc.) + - d) interactive application type (e.g., games, educational, informational, commercial, etc.) + - e) end-user type (e.g., children under 13, adults, etc.) + - f) end user (if the AM system is able to confidently distinguish end users) + - g) device (which TVs, computers, mobile phones, etc.) + - h) day-parts (e.g., morning news, morning, day-time, early fringe, early news, access, prime, late news, late fringe, late night, etc.); + - i) end-user context (e.g., at work, location, etc.) + - j) correlation with an operator's subscriber information + - k) correlation with an end-user's voluntarily provided profile information. + +### **7.5 Recommended requirements for operators** + +Operators of AM are recommended to provide end users with clear disclosure and information about data collection and use practices if and when they request end-user permission. + +### 7.6 Recommended requirements for IPTV architecture + +1. The IPTV architecture is recommended to support a mechanism for audience measurement service discovery. +2. The IPTV architecture is recommended to support multiple audience measurement service providers. +3. The IPTV architecture is recommended to allow the IPTV service providers to choose their audience measurement service provider. +4. The IPTV architecture is recommended to allow the end users to choose an audience measurement service provider. +5. The IPTV architecture is recommended to support monitoring or communications with AM functions for audience measurement. + +## 8 IPTV architecture and audience measurement + +Audience measurement components consist of audience measurement functions and aggregation functions. + +The audience measurement functions measure the end-user behaviour and may optionally collect end-user information. This information is transferred to aggregation functions. + +The aggregation functions collect and aggregate the data from the audience measurement functions, optionally enrich data with additional end-user information, and perform data analytics. + +Figure 1 shows the high level architecture of audience measurement within a derivative of IPTV architecture (defined in [ITU-T Y.1910]), including different audience measurement components and their possible locations. + +![Diagram of IPTV architecture showing audience measurement components. The diagram is organized into functional blocks: End-user functions (IPTV terminal functions with TD-AMF and Home network functions with HN-AMF), Application functions (containing Aggregation functions), Service control functions (with SC-AMF), Content delivery functions (with CD-AMF), and Network functions (with N-AMF). Arrows show data flow from TD-AMF, HN-AMF, SC-AMF, and CD-AMF to the Aggregation functions, and from Aggregation functions to N-AMF.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +The diagram illustrates the IPTV architecture with audience measurement components. It is divided into several functional blocks: **End-user functions** (pink box) containing **IPTV terminal functions** (with **TD-AMF**) and **Home network functions** (with **HN-AMF**). **Application functions** (blue box) contain **Aggregation functions** (yellow box). **Service control functions** (yellow box) contain **SC-AMF**. **Content delivery functions** (orange box) contain **CD-AMF**. **Network functions** (green box) contain **N-AMF**. Arrows indicate data flow: from **TD-AMF** and **HN-AMF** to **Aggregation functions**, from **SC-AMF** and **CD-AMF** to **Aggregation functions**, and from **Aggregation functions** to **N-AMF**. A dashed line connects **TD-AMF** and **HN-AMF** to the **Application functions** block. A label **H.741.0(12)\_F01** is at the bottom right. + +Diagram of IPTV architecture showing audience measurement components. The diagram is organized into functional blocks: End-user functions (IPTV terminal functions with TD-AMF and Home network functions with HN-AMF), Application functions (containing Aggregation functions), Service control functions (with SC-AMF), Content delivery functions (with CD-AMF), and Network functions (with N-AMF). Arrows show data flow from TD-AMF, HN-AMF, SC-AMF, and CD-AMF to the Aggregation functions, and from Aggregation functions to N-AMF. + +**Figure 1 – Audience measurement components within IPTV architecture** + +The terminal device audience measurement functions (TD-AMFs) are responsible for audience measurement in IPTV terminal functions. + +The home network audience measurement functions (HN-AMFs) are responsible for audience measurement in home network functions. + +The network audience measurement functions (N-AMFs) are responsible for audience measurement in network functions. + +The service control audience measurement functions (SC-AMFs) are responsible for audience measurement in service control functions. + +The content delivery audience measurement functions (CD-AMFs) are responsible for audience measurement in content delivery functions. + +This Recommendation specifies IPTV audience measurement for TD-AMFs. + +Audience measurement data sent from multiple audience measurement functions may be aggregated by aggregation functions. Those multiple audience measurement functions may be co-located in a home and/or geographically distributed. + +In both cases, certain audience measurement functions may have relationships among them that may cause them to be treated as sets by the aggregation function. In certain circumstances, sets of audience measurement functions may span multiple aggregation functions. + +## 9 Audience measurement lifecycle + +The audience measurement lifecycle consists of eight stages: + +- 1) Input of pre-configuration data: + - a) "Discovery" inputs from the service provider (SP) and AM discovery to TD-AMFs. Includes the available and preferred configuration and permission modes of aggregation functions + - b) "Permission" inputs from end user or SP to TD-AMFs + - c) "Orders" input from content providers, advertisers, audience rating companies, and SPs to aggregation functions + - d) "Terminal devices online" input from SP "server applications" to aggregation functions. +- 2) Aggregation functions configure TD-AMFs per pre-configuration inputs. +- 3) IPTV client applications (e.g., linear TV) provide input to TD-AMFs per configuration. +- 4) TD-AMFs generate audience measurement data per configuration and client applications input. +- 5) TD-AMFs deliver audience measurement data to aggregation functions per configuration. +- 6) IPTV server applications provide input to aggregation functions in order to augment audience measurement data, per "orders". +- 7) Aggregation functions process audience measurement data per "orders". +- 8) Aggregation functions send aggregated reports per "orders" to IPTV server applications and/or content providers, advertisers, audience rating companies, and SPs. + +Figure 2 illustrates the information interfaces associated with the operation of the audience measurement functions and the aggregation functions. + +![Diagram illustrating the information interfaces associated with the operation of Audience Measurement (AM) functions and Aggregation functions.](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +The diagram shows two main functional blocks: "Audience measurement functions" and "Aggregation functions", connected by a double-headed arrow labeled "AM messages". + +- Audience measurement functions** (left box) has three external interfaces: + - An upward arrow labeled "Permission messages from user or SP". + - A downward arrow labeled "Discovery". + - A downward arrow labeled "Client applications". +- Aggregation functions** (right box) has three external interfaces: + - An upward arrow labeled "Orders (order details, directives and management)". + - A downward arrow labeled "Server applications". + - A rightward arrow labeled "Aggregated reports". + +Reference code: H.741.0(12)\_F02 + +Diagram illustrating the information interfaces associated with the operation of Audience Measurement (AM) functions and Aggregation functions. + +**Figure 2 – Information interfaces associated with the operation of AM** + +## 10 Configuration of terminal device audience measurement functions + +Configuration of terminal device audience measurement functions (TD-AMFs) drives the message sequences between the aggregation functions and the TD-AMFs. Configuration may be initiated by either the TD-AMF and/or the aggregation functions. Figure 3 shows how message types are used in configuration sequences. Message sequences starting with a request are termed as "pull", and those that are sent without a request are termed as "push". + +![Figure 3 – AM configuration message sequences. The diagram illustrates three message sequences between Audience measurement functions (TD-AMF) and Aggregation functions. 1. Configuration 'pull' message sequence: TD-AMF sends a 'Configuration request msg' to Aggregation functions. Aggregation functions respond with 'Configuration request error msg' or 'Configuration request response msg'. TD-AMF then sends 'Configuration response error msg'. A note 'One of' is next to the response messages. 2. Configuration 'push' message sequence: Aggregation functions send 'Configuration msg' to TD-AMF. TD-AMF responds with 'Configuration ack msg' or 'Configuration error msg'. A note 'Zero or one of' is next to the response messages. 3. Configuration 'pull and push' message sequence: TD-AMF sends 'Configuration request msg'. Aggregation functions respond with 'Configuration request response msg'. Subsequent 'Configuration msg' messages are sent from Aggregation functions to TD-AMF. A note 'Two or more' is next to these messages. The diagram is labeled H.741.0(12)_F03.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +Figure 3 – AM configuration message sequences. The diagram illustrates three message sequences between Audience measurement functions (TD-AMF) and Aggregation functions. 1. Configuration 'pull' message sequence: TD-AMF sends a 'Configuration request msg' to Aggregation functions. Aggregation functions respond with 'Configuration request error msg' or 'Configuration request response msg'. TD-AMF then sends 'Configuration response error msg'. A note 'One of' is next to the response messages. 2. Configuration 'push' message sequence: Aggregation functions send 'Configuration msg' to TD-AMF. TD-AMF responds with 'Configuration ack msg' or 'Configuration error msg'. A note 'Zero or one of' is next to the response messages. 3. Configuration 'pull and push' message sequence: TD-AMF sends 'Configuration request msg'. Aggregation functions respond with 'Configuration request response msg'. Subsequent 'Configuration msg' messages are sent from Aggregation functions to TD-AMF. A note 'Two or more' is next to these messages. The diagram is labeled H.741.0(12)\_F03. + +**Figure 3 – AM configuration message sequences** + +NOTE – Error and acknowledgement messages are not shown for configuration "pull and push" message sequence + +Error messages may be mandatory or configurable. Acknowledgements may be configurable. + +As indicated in Figure 3, configuration may be done using pull, push, or pull and push (hybrid) sequences. The configuration modes supported and preferred by aggregation functions are discoverable by TD-AMF. The configuration modes supported by TD-AMF are made known to aggregation functions in a configuration request message. + +- 1) Configuration Pull Mode: TD-AMF unicasts the configuration request message to aggregation functions, which responds with either a unicast or multicast configuration request response message. This uses pull message sequences. +- 2) Configuration Push Mode: Aggregation functions periodically send multicast configuration messages to a defined *address:port*. This uses push message sequences. +- 3) Configuration Pull and Push (hybrid) Mode: Subsequent unicast or multicast configuration messages follow the messages of configuration pull mode without subsequent configuration request messages. This uses pull and push message sequences. + +The ITU-T IPTV audience measurement solution provides a rich set of event-driven and time-based measurements. The main features include measurements (if permitted by the end user) configurable by: + +- time +- device type + +- percentage of devices +- service +- restricted content genre. + +## 11 Measurement reporting of TD-AMFs + +The reporting of measurements drives message sequences between the aggregation functions and the terminal device audience measurement functions (TD-AMFs). Reporting may be initiated by either the TD-AMF and/or the aggregation functions. Figure 4 shows how message types are used in reporting sequences. Message sequences starting with a request are termed as "pull", and those that are sent without a request are termed as "push". + +![Figure 4: AM reporting message sequences. The diagram shows two message sequences between Audience measurement functions and Aggregation functions. The 'pull' sequence starts with a 'Measurement report request msg' from Aggregation functions to Audience measurement functions, followed by a 'Measurement report request error msg' (dashed) from Audience measurement functions to Aggregation functions, then a 'Measurement report msg' from Audience measurement functions to Aggregation functions, and finally a 'Measurement report error msg' (dashed) from Aggregation functions to Audience measurement functions. The 'push' sequence starts with a 'Measurement report msg' from Audience measurement functions to Aggregation functions, followed by a 'Measurement report error msg' (dashed) from Aggregation functions to Audience measurement functions. A label 'One or both of' with a curved arrow points to the start of the pull sequence. The diagram is labeled H.741.0(12)_F04.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 4: AM reporting message sequences. The diagram shows two message sequences between Audience measurement functions and Aggregation functions. The 'pull' sequence starts with a 'Measurement report request msg' from Aggregation functions to Audience measurement functions, followed by a 'Measurement report request error msg' (dashed) from Audience measurement functions to Aggregation functions, then a 'Measurement report msg' from Audience measurement functions to Aggregation functions, and finally a 'Measurement report error msg' (dashed) from Aggregation functions to Audience measurement functions. The 'push' sequence starts with a 'Measurement report msg' from Audience measurement functions to Aggregation functions, followed by a 'Measurement report error msg' (dashed) from Aggregation functions to Audience measurement functions. A label 'One or both of' with a curved arrow points to the start of the pull sequence. The diagram is labeled H.741.0(12)\_F04. + +**Figure 4 – AM reporting message sequences** + +Error messages may be mandatory or configurable. + +One of four types of delivery modes is configured: + +- 1) Immediate Push Mode: When a measurement is made, it is optionally grouped with a number of other measurements within a period of time before being sent in a measurement report package message. This uses push message sequences. +- 2) Delayed Push Mode: Measurements are stored until a TD-AMF randomly picked time during a configured delivery window. At that time the TD-AMF groups measurement reports and sends them in a measurement report package message. This uses push message sequences. + +![Figure 5: Delivery window. The diagram shows a horizontal line representing the 'Delivery window' with a double-headed arrow. Below the line, 'Start delivery window time' is marked at the left end, 'Random time' is marked with an upward arrow in the middle, and 'End delivery window time' is marked at the right end. The diagram is labeled H.741.0(12)_F05.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +Figure 5: Delivery window. The diagram shows a horizontal line representing the 'Delivery window' with a double-headed arrow. Below the line, 'Start delivery window time' is marked at the left end, 'Random time' is marked with an upward arrow in the middle, and 'End delivery window time' is marked at the right end. The diagram is labeled H.741.0(12)\_F05. + +**Figure 5 – Delivery window** + +- 3) Pull Mode: Measurements are stored until a measurement report request message is received from the aggregation functions. This message causes selected measurements to be grouped before being sent in a measurement report package message. A configured policy indicates what the TD-AMF should do in case of storage congestion. This mode uses pull message sequences. + +- 4) Delayed Push and Pull Mode: Measurements are stored until either a report request message is received from the aggregation function, or a TD-AMF randomly picked time during the configured delivery window is reached. Whichever trigger is sooner causes measurements to be grouped before being sent in a measurement report package message. This mode uses both push and pull message sequences. + +## 12 Privacy in audience measurement + +End-user permission is required prior to measuring, collecting and using end-users' measurement information. After end-user permission, audience measurement follows defined end-users' privacy policies. + +In addition, local and regional guidelines, specifications, and laws dictate how privacy is to be ensured [ITU-T H.740 Amd.1]. Examples of these include [b-OECD PPTFPD], [b-ISO/IEC 27001], [b-ISO/IEC 27002], [ITU-T X.1191] and [b-ITU-R BT.2052]. + +### 12.1 End-user permission levels + +Four end-user permission levels are specified by audience measurement. These levels define sets of end-user information that are permitted by the end user to be used for audience measurement. + +The end-user information classifications used to define the permission levels are: + +- Permission level 0: No end-user information is included. +- Permission level 1: Only distinguishability from other end users is included. +- Permission level 2: Distinguishability and non-identifying generic end-user information are included. +- Permission level 3: Identifying user information and non-identifying generic end-user information are included. + +Where: + +- Distinguishability is supported by the use of anonymous user identifiers. +- Non-identifying generic end-user information has extensible value ranges without specifying the information values. +- Identifying end-user information may be the identifying information of the actual end user or of the subscriber. It may be easily combined to identify the end user. End-user information is classified either as personal data that require control or those that do not. Identifying end-user information requires control. It has extensible value ranges without specifying the information values, and is identifiable as "controlled" information. + +Permission levels may optionally be used together with further end-user permissions regarding other aspects of audience measurement, e.g., constraining measurement to certain devices, services, and/or content. The default permission level, before end-user input for permission level is obtained for AM, is set to Level 0, which is not configurable by the service provider. End-users' privacy policies may be expressed within end-user permits in AM. + +### 12.2 Permission modes + +User permissions impact audience measurements depending upon one of three modes discovered during the AM discovery process: + +- External permission mode: In this mode, the request and receipt of end-user permission occurs outside of the AM system. It relies upon end-user permissions being managed outside of AM. No end-user permits are used at TD-AMFs. + +- Internal permission mode: In this mode, the request and receipt of end-user permission occurs within the AM system. It relies on AM to manage permissions. Permits are created at TD-AMFs and may be made available to other TD-AMFs. They are delivered to the TD-AMF separately from the configuration package and configuration package request response messages. +- Hybrid permission mode: In this mode, the request and receipt of end-user permissions occur within the SP system. The TD-AMF requests the permit from the SP system, and may use the permit for local filtering, or send it to the aggregation functions to filter configuration packages. It relies on a combination of AM and external entities to manage permissions. Permits are delivered to TD-AMF separately from configuration package and configuration package request response messages. They are delivered to the TD-AMF from the IPTV SP. + +In the internal and hybrid permission modes, the TD-AMF has knowledge of the end-users' privacy policies and may restrict the measurement of certain information requested by configuration. + +## Appendix I + +### Potential relationships between end users, audience measurement service providers and content distribution service providers + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Service provider offering both content distribution and audience measurement services + +A service provider that provides content distribution services, e.g., linear TV, may also provide audience measurement services. One of the audience measurement applications may be a content rating service. The service provider may choose to provide audience measurement content rating services to stakeholders such as content providers. Figure I.1 shows this information flow. + +Multiple end-users' IPTV terminal devices run an audience measurement function which reports "measurement data" to service provider A, which aggregates end-user's measurement data for a content provider. + +![Diagram illustrating the IPTV service provider with audience measurement service. It shows two end users (End user #1 and End user #2) connected to Service provider A, which in turn is connected to a Content provider. End user #1 and End user #2 each have an IPTV TD and AMF. Service provider A has Linear TV services and an Audience measurement service. Content provider has Content A and a Rating of content A. Arrows indicate content flow, measurement data, and content rating reports.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +The diagram illustrates the information flow in an IPTV service provider with an audience measurement service. On the left, two end users, 'End user #1' and 'End user #2', are shown. Each user has an 'IPTV TD' (IPTV Terminal Device) and an 'AMF' (Application Management Function). Arrows labeled 'Content flow' (thin grey) point from 'Service provider A' to the 'IPTV TD' of each user. Arrows labeled 'Measurement data' (thick dark blue) point from the 'AMF' of each user to the 'Audience measurement service' within 'Service provider A'. 'Service provider A' is a central box containing 'Linear TV services' and 'Audience measurement service'. An arrow labeled 'Content flow' (thin grey) points from 'Content provider' to 'Linear TV services'. An arrow labeled 'Content rating reports' (thick light blue) points from the 'Audience measurement service' to the 'Rating of content A' within the 'Content provider'. The 'Content provider' box contains 'Content A' and 'Rating of content A'. A legend at the bottom left defines the arrow types: a thin grey arrow for 'Content flow', a thick dark blue arrow for 'Measurement data', and a thick light blue arrow for 'Content rating reports'. The diagram is labeled 'H.741.0(12)\_Fl.1'. + +Diagram illustrating the IPTV service provider with audience measurement service. It shows two end users (End user #1 and End user #2) connected to Service provider A, which in turn is connected to a Content provider. End user #1 and End user #2 each have an IPTV TD and AMF. Service provider A has Linear TV services and an Audience measurement service. Content provider has Content A and a Rating of content A. Arrows indicate content flow, measurement data, and content rating reports. + +Figure I.1 – IPTV service provider with audience measurement service + +### I.2 Separate audience measurement service and content distribution service providers + +A service provider may not offer audience measurement services itself. Audience measurement may be collected by another service provider having audience measurement capabilities. Figure I.2 shows this scenario. + +Multiple end-users' IPTV terminal devices receive a linear TV service provided by content distribution service provider A. Each terminal device runs an audience measurement function which reports "measurement data" to the audience measurement service provider B, which aggregates end-user's measurement data for a content provider. + +In order for the audience measurement service provider to properly report regarding the content of the content distribution service-only provider, it must gain access to the EPG of the content distribution service-only provider. + +![Figure I.2: Separate audience measurement service and content distribution service providers. The diagram shows two end users (End user #1 and End user #2) each with an IPTV TD and AMF. End user #1 connects to Service provider A (Linear TV services) and End user #2 connects to Service provider B (Audience measurement service). Both users send measurement data (end-user history) to Service provider B. Service provider B sends content rating reports to Content provider A (Content A, Rating of content A). Content flows from Service provider A to the users. A legend indicates: Content flow (thin grey arrow), Measurement data (end-user history) (thick dark blue arrow), and Content rating reports (thick light blue arrow). The diagram is labeled H.741.0(12)_Fl.2.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Figure I.2: Separate audience measurement service and content distribution service providers. The diagram shows two end users (End user #1 and End user #2) each with an IPTV TD and AMF. End user #1 connects to Service provider A (Linear TV services) and End user #2 connects to Service provider B (Audience measurement service). Both users send measurement data (end-user history) to Service provider B. Service provider B sends content rating reports to Content provider A (Content A, Rating of content A). Content flows from Service provider A to the users. A legend indicates: Content flow (thin grey arrow), Measurement data (end-user history) (thick dark blue arrow), and Content rating reports (thick light blue arrow). The diagram is labeled H.741.0(12)\_Fl.2. + +**Figure I.2 – Separate audience measurement service and content distribution service providers** + +### I.3 Multiple audience measurement service providers + +A content distribution service provider may have relationships with more than one audience measurement service provider. In this case, end users may select an audience measurement service provider from among several. In Figure I.3, end user #1 selects an audience measurement service provider from service provider B, and end user #2 selects an audience measurement service provider from service provider C. Content distribution service provider A provides linear TV to the end users. In this scenario the content provider does the aggregation from multiple audience measurement service providers. + +![Figure I.3: Two service providers provide audience measurement service. The diagram shows two end users (End user #1 and End user #2) each with an IPTV TD and AMF. End user #1 connects to Service provider A (Linear TV services) and Service provider B (Audience measurement service). End user #2 connects to Service provider A (Linear TV services) and Service provider C (Audience measurement service). Both users send measurement data (end-user history) to their respective service providers (B and C). Service providers B and C send content rating reports to Content provider (Content A, Rating of content A). Content flows from Service provider A to the users. A legend indicates: Content flow (thin grey arrow), Measurement data (end-user history) (thick dark blue arrow), and Content rating reports (thick light blue arrow). The diagram is labeled H.741.0(12)_Fl.3.](844077b3034f0030b404207db0ad76b4_img.jpg) + +Figure I.3: Two service providers provide audience measurement service. The diagram shows two end users (End user #1 and End user #2) each with an IPTV TD and AMF. End user #1 connects to Service provider A (Linear TV services) and Service provider B (Audience measurement service). End user #2 connects to Service provider A (Linear TV services) and Service provider C (Audience measurement service). Both users send measurement data (end-user history) to their respective service providers (B and C). Service providers B and C send content rating reports to Content provider (Content A, Rating of content A). Content flows from Service provider A to the users. A legend indicates: Content flow (thin grey arrow), Measurement data (end-user history) (thick dark blue arrow), and Content rating reports (thick light blue arrow). The diagram is labeled H.741.0(12)\_Fl.3. + +**Figure I.3 – Two service providers provide audience measurement service** + +End users need not select a single audience measurement service provider for all their terminal devices. In Figure I.4, an end user has two IPTV terminal devices. One terminal device connects to service provider A to consume content A and report audience to service provider B. The same end user connects another terminal device to service provider C to consume the same content A and reports audience to service provider D. In Figure I.4, a content provider provides two or more content distribution service providers with contents and aggregates content rating reports from other audience measurement service providers. + +![Diagram showing a single end user (End user #1) using multiple audience measurement services (Service provider A, B, C, D) to access content (Content A) from a content provider. The diagram illustrates content flow, measurement data, and content rating reports.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +The diagram illustrates the interaction between an end user, multiple service providers, and a content provider. On the left, 'End user #1' is represented by a yellow vertical bar containing two 'IPTV TD' (Terminal Device) units, each with an 'AMF' (Application Management Function). In the center, four service providers are shown in grey boxes: 'Service provider A' (Linear TV services), 'Service provider B' (Audience measurement service), 'Service provider C' (Linear TV services), and 'Service provider D' (Audience measurement service). On the right, a 'Content provider' (pink box) contains 'Content A' and 'Rating of content A'. Arrows indicate the following flows: + + +- Content flow (thin black arrow):** From 'Content A' to 'Service provider A', and from 'Service provider A' to 'IPTV TD #1'. +- Measurement data (thick dark blue arrow):** From 'AMF' in 'IPTV TD #1' to 'Audience measurement service' in 'Service provider B', and from 'AMF' in 'IPTV TD #2' to 'Audience measurement service' in 'Service provider D'. +- Content rating reports (thick light blue arrow):** From 'Audience measurement service' in 'Service provider B' to 'Rating of content A', and from 'Audience measurement service' in 'Service provider D' to 'Rating of content A'. + + A legend at the bottom left defines the arrow types: + + +- Thin black arrow: Content flow +- Thick dark blue arrow: Measurement data +- Thick light blue arrow: Content rating reports + + The diagram is labeled 'H.741.0(12)\_FI.4' in the bottom right corner. + +Diagram showing a single end user (End user #1) using multiple audience measurement services (Service provider A, B, C, D) to access content (Content A) from a content provider. The diagram illustrates content flow, measurement data, and content rating reports. + +**Figure I.4 – A single end user using multiple audience measurement services** + +## Appendix II + +### Context of audience measurement + +(This appendix does not form an integral part of this Recommendation.) + +The following example shows how AM might fit into a larger context. Non-AM elements are shown as examples of a surrounding context. One should note that other non-AM elements and contexts are possible. Five interfaces are identified which are not within the scope of AM. + +![Figure II.1 – Example context of audience measurement overview. The diagram shows the flow of information between stakeholders, a measurements manager, aggregation functions, audience measurement functions, and other IPTV functions within terminal devices. A dashed box labeled 'Scope of [b-ITU-T H.741.x]' contains the aggregation functions and the audience measurement functions. Interfaces are numbered 1 through 5.](e354b57563dae469c00b412b2abdf765_img.jpg) + +The diagram illustrates the context of audience measurement. On the left, Stakeholder 1 and Stakeholder 2 are shown. Stakeholder 1 sends 'Stakeholder orders (order details, directives)' to a 'Measurements manager' (Interface 1). Stakeholder 2 sends 'Stakeholder reports' to the 'Measurements manager'. The 'Measurements manager' sends 'Orders (order details, directives) and management' to 'Aggregation functions' (Interface 3) and receives 'Aggregated reports' from them. The 'Measurements manager' also receives 'Available measurements (audience segments, measurement types, measurement media, etc.) and analytics' from 'Other functions of same SP' (Interface 2). The 'Aggregation functions' send 'Measurement requests' to 'Audience measurement functions' (Interface 4) and receive 'Measurement reports' from them. The 'Audience measurement functions' are divided into two segments: 'Audience segment 1' and 'Audience segment 2'. Each segment is connected to 'Other IPTV functions' (Interface 5) within a 'Terminal device'. A dashed box labeled 'Scope of [b-ITU-T H.741.x]' encloses the 'Aggregation functions' and the 'Audience measurement functions'. + +Figure II.1 – Example context of audience measurement overview. The diagram shows the flow of information between stakeholders, a measurements manager, aggregation functions, audience measurement functions, and other IPTV functions within terminal devices. A dashed box labeled 'Scope of [b-ITU-T H.741.x]' contains the aggregation functions and the audience measurement functions. Interfaces are numbered 1 through 5. + +H.741.0(12)\_FI.1 + +Figure II.1 – Example context of audience measurement overview + +Interface 1 – Stakeholders such as service providers, content providers, advertisers/agencies, programmers, and audience research companies may receive measurement offers, place orders for measurements, and receive reports by communicating with an audience measurement service provider via a measurements manager. A specification which includes the exchange of these orders and reports and that covers communications between a content provider and the SP is currently under study in ITU-T (see ITU-T H.IPTV-CPI at [http://itu.int/ITU-T/workprog/wp\\_item.aspx?isn=7398](http://itu.int/ITU-T/workprog/wp_item.aspx?isn=7398)). + +Interface 2 – A measurements manager may perform many possible functions. It may include responsibility for fulfilment management, audience segmentation, and for managing privacy and permits. These functions could require communications with other functions of the same SP. + +Interface 3 – The measurement manager could manage the orders sent to AM aggregation functions and the resulting aggregated reports. + +Interface 4 – AM aggregation functions may communicate with other IPTV server functions to obtain inputs such as end-user profiles and terminal devices online, and provide outputs to a content recommendation engine, for example. + +Interface 5 – AM audience measurement functions may communicate with other IPTV client functions to obtain inputs such as engagement events and/or permits, and provide outputs to a targeted advertising function, for example. + +## Bibliography + +- [b-ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems*. +- [b-ITU-T H.721 Amd.1] Recommendation ITU-T H.721 Amd.1 (2009), *IPTV terminal devices: Basic model. Amendment 1: New Appendix II on terminal device implementation example*. +- [b-ITU-T H.741.3] Recommendation ITU-T H.741.3 (2012), *IPTV application event handling: Audience measurement for IPTV distributed content services*. +- [b-ITU-T J.183] Recommendation ITU-T J.183 (2001), *Time-division multiplexing of multiple MPEG-2 transport streams over cable television systems*. +- [b-ITU-T J.200] Recommendation ITU-T J.200 (2010), *Worldwide common core – Application environment for digital interactive television services*. +- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2006), *Designations for interconnections among operators' networks*. +- [b-ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2004), *Enhanced Telecom Operations Map (eTOM) – The business process framework*. +- [b-ITU-T T.174] Recommendation ITU-T T.174 (1996), *Application programming interface (API) for MHEG-1*. +- [b-ITU-T X.800 Amd.1] Recommendation ITU-T X.800 Amd.1 (1996), *Security architecture for open systems interconnection for CCITT applications. Amendment 1: Layer Two Security Service and Mechanisms for LANs*. +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions*. +- [b-ITU-T Y.Sup5] ITU-T Y.Sup5 (2008), *ITU-T Y.1900 series – Supplement on IPTV service use cases*. +- [b-ITU-R BT.2052] ITU-R Report BT.2052 (2005), *Protection of end-users' privacy in interactive broadcasting systems*. +- [b-ISO/IEC 27001] ISO/IEC 27001 (2005), *Information technology – Security techniques – Information security management systems – Requirements*. +- [b-ISO/IEC 27002] ISO/IEC 27002 (2005), *Information technology – Security techniques – Code of practice for information security management*. +- [b-OECD PPTFPD] OECD. Document C(80)58(Final) (1980), *OECD recommendation concerning and guidelines governing the protection of privacy and transborder flows of personal data*. +[http://www.oecd.org/document/18/0,3746,en\\_2649\\_34223\\_1815186\\_1\\_1\\_1\\_1\\_00.html#recommendation](http://www.oecd.org/document/18/0,3746,en_2649_34223_1815186_1_1_1_1_00.html#recommendation) + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/raw.md b/marked/H/T-REC-H.741.1-201206-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..830dd21d9d8386442ff91496cc00b5a12c3208de --- /dev/null +++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/raw.md @@ -0,0 +1,3256 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.741.1** + +(06/2012) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +IPTV application event handling + +--- + +**IPTV application event handling: Audience +measurement operations for IPTV services** + +Recommendation ITU-T H.741.1 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.741.1 + +## **IPTV application event handling: Audience measurement operations for IPTV services** + +## **Summary** + +The ITU-T H.741.x series of Recommendations defines a foundational platform for audience measurement (AM) of IPTV services. They focus on the interface between terminal devices and an audience measurement aggregation function. + +The AM platform integrates a method for end users to report personal information, and is designed to easily add time-shifted and interactive services, and non-terminal device measurement points. While the ITU-T H.741.x series allows the implementation of audience measurement for IPTV services, its mechanism may be equally applicable to non-IPTV services. + +The design philosophy in the ITU-T H.741.x series is focused on scalability, minimizing the use of resources, security, flexibility to support a variety of service provider deployments, and rich privacy support to meet emerging regulations and legislation. + +Recommendation ITU-T H.741.1 specifies the operations of AM, including procedures prior to configuration of terminals, configuration of terminals, reporting by terminals, security mechanisms, and recovery from abnormal situations. Informative Appendices I-VII discuss discovery metadata, implementation considerations, examples, permission levels, vendor considerations, alternative privacy schemes, and discuss capabilities and profiles. + +Amendment 1 to Recommendation ITU-T H.741.1 (integrated into this edition) includes XML schema on audience measurement service discovery in Appendix VIII and XML schema instances for TD-AMF configurations, reports and permits in Appendix IX. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|-----------------------------|------------|-------------| +| 1.0 | ITU-T H.741.1 | 2012-06-29 | 16 | +| 1.1 | ITU-T H.741.1 (2012) Amd. 1 | 2013-01-25 | 16 | + +## **Keywords** + +Audience measurement, audience rating service, audience viewership, configuration, contents rating, discovery metadata, distributed content service, end-user permission, engagement metrics, examples, implementation guidelines, interactive services, IPTV application event handling, IPTV service, linear TV, monitoring, personalized service, privacy protection, reporting, service discovery XML schema. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|-------|-----------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 4 | +| 4 | Abbreviations and acronyms ..... | 5 | +| 5 | Conventions ..... | 6 | +| 6 | Preconfiguration ..... | 6 | +| 7 | Effective configuration of TD-AMFs..... | 10 | +| 7.1 | Configuration package..... | 10 | +| 7.2 | End-user permits..... | 19 | +| 8 | Specific aspects of reporting..... | 20 | +| 8.1 | Reporting of services which start or end outside measurement periods ..... | 20 | +| 8.2 | Reporting surrounding restricted content ..... | 20 | +| 8.3 | Reporting of user presence ..... | 21 | +| 8.4 | Reporting changes due to effective permit changes ..... | 21 | +| 8.5 | Reporting of storage congestion ..... | 21 | +| 8.6 | Nothing to report ..... | 21 | +| 9 | Security, privacy and permission mechanisms..... | 21 | +| 9.1 | Security and privacy of AM messages ..... | 21 | +| 9.2 | End-user permission operation modes..... | 28 | +| 10 | Abnormal situations and potential recovery actions..... | 31 | +| | Appendix I – Discovery of audience measurement services by terminal devices ..... | 35 | +| | Appendix II – Considerations on implementation ..... | 40 | +| II.1 | Considerations on whether to implement AM..... | 40 | +| II.2 | Considerations for end-user permission method selection..... | 41 | +| II.3 | Considerations on using content filtering in configuration packages ..... | 45 | +| II.4 | Considerations on using different measurement triggers ..... | 46 | +| II.5 | Considerations for using AM message acknowledgements ..... | 47 | +| II.6 | Considerations for configuration mode selection..... | 47 | +| II.7 | Considerations regarding methods of obtaining end-user permits ..... | 49 | +| II.8 | Considerations for using multicast sub-addressing mechanisms ..... | 50 | +| II.9 | Considerations for requesting error message responses to multicast messages ..... | 52 | +| II.10 | Considerations for delivery mode selection ..... | 53 | +| II.11 | Considerations on using end-user information to filter measurement requests ..... | 54 | + +| | Page | +|-----------------------------------------------------------------------------------------------------------|------| +| Appendix III – Examples of TD-AMF configurations, reports and permits ..... | 56 | +| III.1    Example of use of configuration package data structure for service-
    common measurements ..... | 56 | +| III.2    Example of measurement reports associated with configuration example
    of Figure III.1 ..... | 58 | +| III.3    Examples using end-user information for filtering configuration packages .. | 65 | +| III.4    Example of UserPermit ..... | 67 | +| Appendix IV – Considerations of end-user permission levels..... | 69 | +| Appendix V – Considerations regarding the unlinkability property..... | 71 | +| Appendix VI – Considerations for AM vendors ..... | 74 | +| Appendix VII – Audience measurement capabilities and profiles ..... | 75 | +| Appendix VIII – XML schema on the data structures for audience measurement service
    discovery..... | 76 | +| Appendix IX – XML schema instances for TD-AMF configurations, reports and permits .... | 79 | +| IX.1    Instance based on clause III.1 ..... | 79 | +| IX.2    Instances based on clause III.2 ..... | 81 | +| IX.3    Instances based on Appendix III.3 ..... | 86 | +| IX.4    Instance based on Appendix III.4 ..... | 87 | +| Bibliography..... | 88 | + +# Recommendation ITU-T H.741.1 + +## IPTV application event handling: Audience measurement operations for IPTV services + +## 1 Scope + +This Recommendation describes the operational aspects of audience measurement for IPTV services. It specifies the discovery, configuration, reporting, error handling, and security aspects for IPTV audience measurement. + +Audience measurements are constrained to the communications interface(s) between terminal device audience measurement functions and measurement aggregation functions. Subsequent Recommendations are anticipated to address communications interface(s) with audience measurement functions located within other functions of the IPTV architecture see [ITU-T H.741.0]. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.741.0] Recommendation ITU-T H.741.0 (2012), *IPTV application event handling: Overall aspects of audience measurement for IPTV services.* +- [ITU-T H.741.2] Recommendation ITU-T H.741.2 (2012), *IPTV application event handling: Data structures of audience measurement for IPTV services.* +- [ITU-T H.741.3] Recommendation ITU-T H.741.3 (2012), *IPTV application event handling: Audience measurement for IPTV distributed content services.* +- [ITU-T H.741.4] Recommendation ITU-T H.741.4 (2012), *IPTV application event handling: Transport mechanisms for audience measurement.* +- [ITU-T X.1191] Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects.* +- [IETF RFC 5246] IETF RFC 5246 (2008), *The Transport Layer Security (TLS) Protocol Version 1.2.* + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 aggregation function** [ITU-T H.741.0]: The function that configures audience measurement functions (AMFs), then receives processed events, sample values and end-user information from AMFs. It may participate in the communication of end-user permissions. + +**3.1.2 application** [b-ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services. + +**3.1.3 application event** [b-ITU-T H.740]: An application event is every end-user interaction or occurrence related to multimedia contents in IPTV applications. It includes an emergency event from event notification services. + +**3.1.4 audience information** [ITU-T H.741.0]: The overall information about end-user behaviour, and the related end-user information, during the time IPTV audience measurement is inactive. + +**3.1.5 audience measurement** [ITU-T H.741.0]: The measurement of people's engagement with IPTV services. + +**3.1.6 audience measurement data** [ITU-T H.741.0]: End-user behaviour data which is related to a service and content consumption, combined or not with end-user information. + +**3.1.7 audience measurement function (AMF)** [ITU-T H.741.0]: The function that, if given permission, measures the end-user behaviour by processing events or samples from IPTV services. AMFs may request and collect end-user information. AMFs transfer processed events, samples and end-user information to aggregation functions. + +**3.1.8 audience measurement service provider** [ITU-T H.741.0]: A service provider providing audience measurement services. An audience measurement service provider configures an audience measurement system to control what audience information the system collects. + +**3.1.9 audience measurement system** [ITU-T H.741.0]: The system which, with end-user permission, measures end-user behaviour by detecting application events within the IPTV service and collecting their data within the IPTV service. + +**3.1.10 confidentiality** [b-ITU-T X.800]: The property that information is not made available or disclosed to unauthorized individuals, entities, or processes. + +**3.1.11 configuration package** [ITU-T H.741.0]: A configuration package is the data structure which specifies the target services to be measured, content filtering, measurement schedule, events and samples to be measured, and measurement report delivery. + +**3.1.12 content (object)** [b-ITU-T T.174]: Encoded generic value, media or non-media data + +**3.1.13 content consumption** [ITU-T H.741.0]: A series of valid operation actions to complete selecting an IPTV service and consuming the relate content based on the procedure flow within the IPTV system. + +**3.1.14 content rating** [ITU-T H.741.0]: Actively asserted opinions evaluating aspects of content, using a position assigned on a defined scale, to communicate those aspects to others. Scales may be industry standard, or not. Example scales include, among others, the Motion Picture Association of America (MPAA), a number of stars, and thumbs up or down. + +NOTE – Examples of use include the indicating of suitability for audience segments, censorship, and levels of entertainment, quality, or popularity; content optimization and targeting across audience segments, and content recommendation. + +**3.1.15 controlled information** [ITU-T H.741.0]: A classification of end-user information that can be used alone or easily in combination with other information to uniquely identify, contact, or locate an end user or subscriber, in line with Annex A of [ITU-T X.1191]. + +**3.1.16 digital destinations** [ITU-T H.741.0]: The result of navigation across services, including channels, applications, or portals. + +**3.1.17 directive(s)** [ITU-T H.741.0]: Instructions that are input as part of an order from stakeholders to the AM system regarding target audiences, what and how to measure, and what to report back to stakeholders. + +**3.1.18 electronic programme guide (EPG)** [b-ITU-T H.721]: A service navigation application which is used especially for scheduled linear programmes. + +NOTE – in some traditional broadcast services, EPG is defined as an on-screen guide used to display information on scheduled live broadcast television programmes, allowing a viewer to navigate, select, and discover programmes by time, title, channel, and genre. This traditional definition does not cover "catalogues" for on-demand and download services (sometimes called electronic content guide or broadband content guide) and bi-directional interactive service (sometimes called interactive programme guide) for end-user interaction with a server or head-end. + +**3.1.19 end user** [b-ITU-T Y.1910]: The actual user of the products or services. + +NOTE – The end user consumes the product or service. An end user can optionally be a subscriber. + +**3.1.20 end-user behavioural information** [ITU-T H.741.0]: A part of audience measurement information which includes "application events" and/or "end-user context". An "application event" is information reflecting the behaviour of an IPTV service end user. "End-user context" is information relating to the situation when an "application event" was generated. + +**3.1.21 end-user information** [ITU-T H.741.0]: "End-user info" is information about an IPTV service end user. It includes "identifying end-user information" and "non-identifying generic user information". + +**3.2.22 engagement metric** [ITU-T H.741.0]: A measure of the level of involvement, interaction, sentiment and promotion that an end user has with content. It provides a more holistic view of end users than audience ratings. Examples of involvement metrics include time spent or frequent watcher. Examples of involvement metrics include replay and requests for information. Examples of sentiment metrics include associated amount of chat and words used. Examples of promotion metrics include forwarding to friends or posting to a blog. + +NOTE – Example uses include focus on acquisition of evangelists, finer granularity audience targeting, and emerging uses. + +**3.1.23 integrity** [b-IEC/ISO 27001] and [b-IEC/ISO 27002]: Safeguarding the accuracy and completeness of information and processing methods. + +**3.1.24 Internet Protocol Television (IPTV)** [b-ITU-T Y.1901]: Multimedia services such as television/video/audio/text/graphics/data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. + +**3.1.25 IPTV terminal device** [b-ITU-T Y.1901]: A terminal device which has IPTV terminal function (ITF) functionality, e.g., an STB. + +**3.1.26 IPTV terminal function (ITF)** [b-ITU-T Y.1901]: The end-user function(s) associated with a) receiving and responding to network control channel messages regarding session set-up, maintenance, and tear-down, and b) receiving the content of an IP transport from the network and rendering. + +**3.1.27 linear TV** [b-ITU-T Y.1901]: A television service in which a continuous stream flows in real time from the service provider to the terminal device and where the end user cannot control the temporal order in which contents are viewed. + +**3.1.28 metadata** [b-ITU-T Y.1901]: Structured, encoded data that describe characteristics of information-bearing entities to aid in the identification, discovery, assessment, and management of the described entities. + +NOTE – EPG metadata have many applications and may vary in depth from merely identifying the content package title or information to populate an EPG, to providing a complete index of different scenes in a movie or providing business rules detailing how the content package may be displayed, copied, or sold. + +**3.1.29 measurement report** [ITU-T H.741.0]: The data that the audience measurement function (AMF) generates from an end-user behaviour event or sample. + +**3.1.30 privacy** [b-ITU-T X.800]: The right of individuals to control or influence what information related to them may be collected and stored and by whom and to whom that information may be disclosed. + +**3.1.31 repudiation** [b-ITU-T X.800]: Denial by one of the entities involved in a communication of having participated in all or part of the communication. + +**3.1.32 sample** [ITU-T H.741.0]: A sample is a periodic action occurring on a configurable schedule time interval, during a service period, which captures specified information values. + +**3.1.33 sample set** [ITU-T H.741.1]: A sample set contains one or more information fields, captured at a specific instance of periodic action occurring on a configurable schedule time interval, during a service period. + +**3.1.34 sample time** [ITU-T H.741.0]: A sample time is when an instance of the periodic action occurs on a configurable schedule time interval, which captures specified information values, during a service period. + +**3.1.35 sample value** [ITU-T H.741.0]: The content of an information field, captured at a specific instance of periodic action occurring on a configurable schedule time interval, during a service period. + +**3.1.36 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications. + +**3.1.37 service common** [ITU-T H.741.1]: Qualifier of measurements such as events and elements, and reports to indicate that these measurements and reports are commonly applicable to two or more distributed content or interactive services. + +**3.1.38 service navigation** [b-ITU-T H.720]: A process of presenting information that allows the end user to discover, select and consume services. + +**3.1.39 service provider** [b-ITU-T M.1400]: A general reference to an operator that provides telecommunication services to customers and other end users either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. + +**3.1.40 set-top box (STB)** [b-ITU-T J.183]: A hardware box that contains a digital signal demodulator, de-multiplexer, MPEG-2 decoder, and other functionalities and interfaces related to digital signal reception and presentation of the distributed programme at the subscriber's site. + +**3.1.41 subscriber** [b-ITU-T M.3050.1]: The subscriber is responsible for concluding contracts for the services subscribed to and for paying for these services. + +**3.1.42 terminal device (TD)** [b-ITU-T Y.1901]: An end-user device which typically presents and/or processes the content; such as a personal computer, a computer peripheral, a mobile device, a TV set, a monitor, a VoIP terminal or an audio-visual media player. + +**3.1.43 video-on-demand (VoD)** [b-ITU-T Y.1901]: A service in which the end user can, on demand, select and view a video content and where the end user can control the temporal order in which the video content is viewed (e.g., the ability to start the viewing, pause, fast forward, rewind, etc.). + +### **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 broadcast** (based on [b-ITU-T M.60]): One-way transmission of TV signals from one point to two or more other points. + +**3.2.2 effective measurement period:** An effective measurement period is the time duration when one or more concatenated measurement periods, and a service period overlap. + +**3.2.3 effective permit:** An effective permit is the end-user permit which is in force at a particular time. + +**3.2.4 multicast sub-addressing:** The use of elements in a multicast message to determine if the message is intended for the receiving terminal device audience measurement function (TD-AMF). + +**3.2.5 sender anonymity:** A sender's anonymity is beyond suspicion if, though the attacker can see evidence of a sent message, the sender appears no more likely to be the originator of that message than any other potential sender in the system. + +**3.2.6 unlinkability:** Unlinkability of two or more items of interest (e.g., subjects, messages, actions, etc.) means that within a particular set of information, the attacker cannot distinguish whether these items of interests are related or not (with a high enough degree of probability to be useful). + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|---------------------------------------------------| +| ack | Acknowledge | +| AES | Advanced Encryption Standard | +| AGF | Aggregation Function | +| AM | Audience Measurement | +| AMF | Audience Measurement Function | +| EPG | Electronic Programme Guide | +| HMAC | Hash-based Message Authentication Code | +| HTTP | HyperText Transfer Protocol | +| ID | IDentifier | +| MAC | Media Access Control | +| nPVR | network Personal Video Recorder | +| OTP | One-Time Password | +| PC | Personal Computer | +| PVR | Personal Video Recorder | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| P2P | Peer-to-Peer | +| RSA | Rivest Shamir Adleman public-key encryption | +| SHA | Secure Hash Algorithm | +| SP | Service Provider | +| SRP | Secure Remote Protocol | +| TD-AMF | Terminal Device Audience Measurement Function | +| TLS | Transport Layer Security | +| TLS-SRP | Transport Layer Security – Secure Remote Password | +| URL | Uniform Resource Locator | + +| | | +|-----|----------------------------| +| VoD | Video-on-Demand | +| XML | eXtensible Markup Language | + +## 5 Conventions + +In this Recommendation, the following conventions apply. + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. + +The keywords "is not recommended" indicate a requirement which is not recommended but which is not specifically prohibited. Thus, conformance with this specification can still be claimed even if this requirement is present. + +The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +The keyword "functions" is defined as a collection of functionalities. It is represented by the following symbol in the context of IPTV architecture: + +![A rounded rectangular box containing the word 'Functions'.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +A rounded rectangular box with a thin black border, containing the word "Functions" centered inside it. + +A rounded rectangular box containing the word 'Functions'. + +The keywords "functional block" are defined as a group of functionalities that has not been further subdivided at the level of detail described in this Recommendation. It is represented by the following symbol in the context of IPTV architecture: + +![A rectangular box containing the words 'Functional block'.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +A rectangular box with a thin black border, containing the words "Functional" and "block" stacked vertically and centered inside it. + +A rectangular box containing the words 'Functional block'. + +NOTE – In the future, other groups or other Recommendations may possibly further subdivide these functional blocks. + +## 6 Preconfiguration + +Prior to a terminal device audience measurement function (TD-AMF) being configured to run audience measurement functions, it first discovers, selects and connects to an IPTV service provider. The discovery of service providers and their services are described in [b-ITU-T H.770]. Aggregation functions may obtain information about terminal devices online from other IPTV services. A TD-AMF discovers and selects an audience measurement service; it is then configured for audience measurement before starting measurement of IPTV services. The audience measurement service may be provided: by the connected IPTV service provider, by a different IPTV service provider, or by an independent audience measurement service provider (see Appendix I of [ITU-T H.741.0]). Multiple audience measurement services may be able to measure the services of the connected IPTV service provider; in which case an end user may be given the choice to select which audience measurement service is to be used. + +This Recommendation specifies: + +- 1) Inputs required from discovery process +- 2) Optional inputs of permission information +- 3) AM messages. + +This clause specifies how the AM system operates from start-up until configuration from the perspective of the TD-AMF. + +![Sequence diagram showing the preconfiguration sequence between End user, Audience measurement system (Audience measurement functions and Aggregation functions), and Service provider.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant EU as End user + participant AMF as Audience measurement functions + participant AF as Aggregation functions + participant SP as Service provider + + Note over AMF, AF: Audience measurement system + + SP->>AMF: (1) + AMF->>AMF: (2) + AMF->>EU: (3) + EU->>AMF: (4) + AMF->>AF: (5) + AF->>AMF: (6) + +``` + +The diagram is a sequence diagram illustrating the preconfiguration sequence. It features three main entities: 'End user', 'Audience measurement system' (which contains two sub-components: 'Audience measurement functions' and 'Aggregation functions'), and 'Service provider'. The sequence of interactions is as follows: + +- (1) A message from the Service provider to the Audience measurement functions. +- (2) A self-looping message at the Audience measurement functions. +- (3) A message from the Audience measurement functions to the End user. +- (4) A message from the End user to the Audience measurement functions. +- (5) A message from the Audience measurement functions to the Aggregation functions. +- (6) A message from the Aggregation functions to the Audience measurement functions. + +The diagram is labeled 'H.741.1(12)\_F01' at the bottom right. + +Sequence diagram showing the preconfiguration sequence between End user, Audience measurement system (Audience measurement functions and Aggregation functions), and Service provider. + +- (1) – AM service and attribute discovery +- (2) – Determine compatible AM providers +- (3) – Optional AM service selection +- (4) – Optional input of permission information +- (5) – Authentication +- (6) – AM configuration messages + +**Figure 1 – Preconfiguration sequence** + +Figure 1 shows the sequence of operations leading to configuration of audience measurement functions by aggregation functions following discovery, selection, registration and connection to an IPTV service provider for the first time. + +- 1) The TD-AMF discovers which AM providers are available for this IPTV service provider. Attributes of the AM provider are discovered, including: + - a) Permission mode (internal, external, or hybrid) – available and preferred (mandatory). Defined in clause 7.2. + - b) Address – one of the addresses described in points (i), (ii) or (iii) below is mandatory; multiple are possible: + - (i) Address to which all TD-AMF AM configuration request messages are to be sent. + 1. Optional address for errors to be sent to, otherwise use address of (i). + - (ii) Multicast address/port/source address to which the TD-AMF listens for a multicast configuration request response message. + - (iii) Multicast address/port/source address to which the TD-AMF listens for a multicast configuration message. + +- (iv) Optional addresses for responses to multicast messages. + - 1. Optional address for errors to be sent to, otherwise no error reporting. + - 2. Optional address for multicast configuration message acknowledgments to be sent to, otherwise use address of (iv-1) or no ack reporting. + - c) Configuration push, pull or pull and push (hybrid) mode – available and preferred, for each mode available and preferred transport protocols. Defined in [ITU-T H.741.0] and below. + - d) Available transport protocols for measurement reporting – available and preferred. + - e) Available cryptographic protocols for each of configuration and reporting – available and preferred. +- 2) The TD-AMF determines which of the AM providers matches its audience measurement capability profile. See [ITU-T H.741.2]. + - 3) The end user optionally selects from among compatible AM providers. + - 4) Optional permission messages are received by the TD-AMF: + - a) If internal permission mode, then directly from an end user. + - b) If hybrid permission mode, then from a service provider (SP). + - 5) Authentication between TD-AMF and AGF occurs (see clause 9.1.1). + - 6) The TD-AMF becomes ready for the initial AM message: + - a) If configuration pull, or configuration pull and push (hybrid) mode, then send a "configuration request message". The TD-AMF shall not wait for a response for more than three seconds after the "configuration request message" is sent. + - b) If configuration push mode, then listen to multicast address. + +During initial configuration, TD-AMFs are provided with all the information not already obtained from discovery, to participate in audience measurement. For both the configuration pull and the configuration pull and push (hybrid) modes, a configuration package check delay is defined, which triggers subsequent checks for availability of a new configuration package. Following activation of the first configuration package (see clause 7.1), a timer counts down the "configuration package check delay" in days. + +![Figure 2: Acquisition of the initial configuration package and configuration package checks. The diagram shows a sequence of events over time. It starts with 'AM provider discovery' followed by 'Acquisition of the first configuration package'. A 'First configuration request message' is sent, and a 'First configuration request response message' is received. A 'Configuration package check delay' timer starts. When the terminal becomes 'Terminal active', a 'Subsequent configuration request message' is sent, and a 'Subsequent configuration request response message' is received. Another 'Configuration package check delay' timer starts. The timeline ends with 'Time'.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +The diagram illustrates the sequence of operations for acquiring and checking configuration packages. It begins with a block labeled 'AM provider discovery' followed by 'Acquisition of the first configuration package'. Above this, a 'First configuration request message' is sent upwards, and a 'First configuration request response message' is received downwards. A horizontal arrow labeled 'Configuration package check delay' points to the next stage. The next stage consists of a 'Configuration package check' block, preceded by a 'Subsequent configuration request message' sent upwards and a 'Subsequent configuration request response message' received downwards. Another horizontal arrow labeled 'Configuration package check delay' follows. Below the main sequence, a long horizontal bar labeled 'Terminal active' spans from the start of the first configuration package acquisition to the start of the subsequent configuration package check. The entire timeline is labeled 'Time' at the far right, with the identifier 'H.741.1(12)\_F02' at the bottom right. + +Figure 2: Acquisition of the initial configuration package and configuration package checks. The diagram shows a sequence of events over time. It starts with 'AM provider discovery' followed by 'Acquisition of the first configuration package'. A 'First configuration request message' is sent, and a 'First configuration request response message' is received. A 'Configuration package check delay' timer starts. When the terminal becomes 'Terminal active', a 'Subsequent configuration request message' is sent, and a 'Subsequent configuration request response message' is received. Another 'Configuration package check delay' timer starts. The timeline ends with 'Time'. + +**Figure 2 – Acquisition of the initial configuration package and configuration package checks** + +For the configuration pull mode. When the timer expires, there are two possible situations: + +Situation 1: The terminal device is active; the TD-AMF then issues a configuration request message. Situation 1 is shown in Figure 2. + +Situation 2: The terminal device is not active when the configuration package check delay expires, so it discovers this only after it is switched on again and gets connected to the same IPTV service provider. The TD-AMF then issues a configuration request message. Situation 2 is shown in Figure 3. + +![Sequence diagram illustrating the acquisition of the subsequent configuration package after delayed switch-on. The diagram shows two 'Terminal active' periods. In the first, 'AM provider discovery' is followed by 'Acquisition of the first configuration package', which sends a 'First configuration request message' and receives a 'First configuration request response message'. A 'Configuration package check delay' is indicated. In the second 'Terminal active' period, a 'Configuration package check' occurs, sending a 'Subsequent configuration request message' and receiving a 'Subsequent configuration request response message'. A dashed line connects the end of the first delay to the start of the second check. The diagram is labeled H.741.1(12)_F03.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Sequence diagram illustrating the acquisition of the subsequent configuration package after delayed switch-on. The diagram shows two 'Terminal active' periods. In the first, 'AM provider discovery' is followed by 'Acquisition of the first configuration package', which sends a 'First configuration request message' and receives a 'First configuration request response message'. A 'Configuration package check delay' is indicated. In the second 'Terminal active' period, a 'Configuration package check' occurs, sending a 'Subsequent configuration request message' and receiving a 'Subsequent configuration request response message'. A dashed line connects the end of the first delay to the start of the second check. The diagram is labeled H.741.1(12)\_F03. + +**Figure 3 – Acquisition of the subsequent configuration package after delayed switch-on** + +The time of the initial configuration package acquisition is randomized because it is the time at which the end user connects to the IPTV service provider for the first time. To keep the configuration package check-time randomized, the time for the next configuration package check occurs on a multiple of the configuration package check delay subsequent to the initial configuration package acquisition, as illustrated in Figure 4. + +![Sequence diagram illustrating the use of multiples of configuration package check delay. The diagram shows a 'Terminal active' period starting with 'AM provider discovery' and 'Acquisition of the first configuration package', sending a 'First configuration request message' and receiving a 'First configuration request response message'. A 'Configuration package check delay' is shown. This is followed by a 'Configuration package check' which sends a 'Subsequent configuration request message' and receives a 'Subsequent configuration request response message'. A 'Delay to be computed' is shown between the second check and a third 'Subsequent configuration request message'. Below the timeline, two 'Configuration package check delay' intervals are marked, indicating that the third request occurs at a multiple of the delay. The diagram is labeled H.741.1(12)_F04.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Sequence diagram illustrating the use of multiples of configuration package check delay. The diagram shows a 'Terminal active' period starting with 'AM provider discovery' and 'Acquisition of the first configuration package', sending a 'First configuration request message' and receiving a 'First configuration request response message'. A 'Configuration package check delay' is shown. This is followed by a 'Configuration package check' which sends a 'Subsequent configuration request message' and receives a 'Subsequent configuration request response message'. A 'Delay to be computed' is shown between the second check and a third 'Subsequent configuration request message'. Below the timeline, two 'Configuration package check delay' intervals are marked, indicating that the third request occurs at a multiple of the delay. The diagram is labeled H.741.1(12)\_F04. + +**Figure 4 – Use of multiples of configuration package check delay** + +For pull and push (hybrid) configuration mode, a TD-AMF initially and subsequently requests configuration per the pull mode and receives pushed configuration from aggregation functions. In this mode, when a configuration push occurs the TD-AMF defers the configuration package check time until the next multiple of configuration package check delay. TD-AMF configuration requests do not occur as long as configuration messages are pushed to a TD-AMF. For pull and push (hybrid) configuration mode, the aggregation functions initially responds with a configuration request response message which uses one of the transport protocols supported in the configuration request message. If a unicast configuration request response message is used, then it must use the same transport protocol as the configuration request message. + +For (unicast or multicast) push mode configuration mode, the TD-AMF listens only, and does not request configuration. Multicast configuration messages may be sent in one or more multicast-supporting transport protocols. + +See [ITU-T H.741.2] for metadata elements of configuration package request response, including configuration package check delay. + +## 7 Effective configuration of TD-AMFs + +Configuration of TD-AMFs is accomplished by aggregation functions using the configuration message or configuration request response message. Effective configuration is the result of constraining the received configuration package(s) with an effective end-user permit if present in a TD-AMF. This clause specifies the configuration package and end-user permits. + +### 7.1 Configuration package + +This clause specifies the configuration of the TD-AMF. Data elements and structures are specified in [ITU-T H.741.2] and examples are provided in Appendix III. Default values are used to reduce the size of the configuration package. + +Configuration packages apply to the whole configuration of the audience measurement functions. Partial updates are not directly supported and any configuration change must be made by transmitting a complete configuration package. + +It is not required that the configuration values within the configuration package be validated by audience measurement functions. It is recommended that the aggregation functions validate the values, e.g., bounds checking and self-consistency, which have been placed into configuration packages before transmission. + +Identical configuration packages may be sent to multiple TD-AMFs. + +The configuration package consists of: + +- Package header – package info. +- Measurement requests – including services to be measured, measurement schedule, events and sample values to be measured, and measurement report message delivery schedule. + +#### 7.1.1 Configuration package headers + +Information related to the configuration package is distributed in multiple data structures, at the start of: + +- the configuration package +- unicast and multicast XML transport of configuration messages +- unicast and multicast XML transport of configuration request response messages +- multicast binary transport of configuration and configuration request response messages. + +Certain configuration capabilities are common while others have transport dependencies as follows. + +##### 7.1.1.1 Transport independent capabilities + +A header indicates a message-expiration time, after which the message is not accepted. This is recommended to be set to ten minutes after message-transmission time. The message-expiration time is a security feature to minimize the impact of replay attacks. + +Versioning of the AM message protocol is configurable to support its evolution. Interoperability between versions is indicated by versioning. + +The compression/decompression algorithm applied to the XML payload is indicated in AM message headers. + +Using an identifier, AM management tracks configuration packages. The aggregation functions generate an identifier as an AM service provider unique identifier. Versioning of the package identifier is additionally supported. + +Configuration packages are sent to TD-AMFs for immediate use, or they are sent in advance and scheduled for use when they become effective. When an immediate package is received, or when the effective time arrives, the new configuration becomes effective. Any and all prior stored + +measurements are reported immediately. Two configuration packages may be sent to a TD-AMF at a time, one for immediate use, the other for future use. TD-AMFs are required to handle a maximum of one immediate and one future configuration package at any one time. + +A header may indicate that there is no immediate configuration package, in which case any and all prior stored measurements are reported immediately and audience measurement stops. + +A configuration package check delay may be configured, which triggers subsequent checks for availability of a new configuration package. + +See [ITU-T H.741.2] for metadata elements used in the configuration package header. See [ITU-T H.741.4] for metadata elements used in the delivery of unicast and multicast configuration and configuration request response messages + +##### 7.1.1.2 Multicast dependent capabilities + +AM multicast messages provide four filtering capabilities to define targeted subsets of TD-AMFs which are to process the associated configuration packages. + +- 1) For configuration push mode, a threshold configuration may adjust the subset size of the responding TD-AMFs. This configuration may be helpful for network congestion avoidance as the number of TD-AMFs grows. The threshold is implemented by the TD-AMF generating a random number between 0 and 10000 once at (re)-boot time, and the value is used upon receipt of every configuration message containing a threshold element. + +If the generated random number is between the configured lower and upper thresholds (i.e., the threshold range), the TD-AMF configures its operation mode with the received immediate configuration package depending on end-user permissions and starts audience measurement as soon as an IPTV service is activated. If a future configuration package is also present in the received configuration message, then it is stored until the effective time. + +If the random number is outside the threshold range, then the TD-AMF ignores the configuration message. + +Multiple configuration messages with different threshold ranges can optionally be used to configure multiple TD-AMF subsets. The threshold ranges may be used to "address" each TD-AMF subset. + +- 2) The configuration message header may be configured to specify the TD-AMF device type(s) which are to process the associated configuration package. +- 3) The configuration message header may be configured to specify the MAC addresses of the TD-AMFs which are to process the associated configuration package. +- 4) The configuration message header may be configured to specify a match to information provided by the end user to specify the target TD-AMFs which are to process the associated configuration package. The configuration also specifies whether to ignore the matching rule when the specified end-user data is not available, when the reason for not being available may be due to the end user not providing the information or to a permission restriction. + +When multiples of the above sub-addressing filters are used concurrently, they must all be matched for a TD-AMF to process the associated configuration package. + +Multicast headers include message integrity checks and signatures for authentication. + +The configuration message header may be configured to enable optional acknowledgement messages to the multicast configuration message for operational management. + +The configuration message header may be configured to enable optional error messages to the multicast configuration and multicast request response messages for operational management. + +See [ITU-T H.741.4] for metadata elements of multicast headers. + +#### 7.1.2 Measurement requests + +Measurement requests contain services to be measured, measurement schedules, events and sample values to be measured, and measurement report message delivery schedules. + +A configuration package may contain multiple measurement requests. Some identical values may be used in multiple measurement requests. So to reduce the size of a configuration package, configuration may set values used by multiple measurement requests in a special common structure. Multiple common structures which each relate to a set of measurement requests may be configured. + +A configuration may specify measurement requests which are to be conditionally processed by a TD-AMF dependent upon a match to element values associated with that TD-AMF. The elements used to qualify measurement requests may include generic (uncontrolled) information and/or identifying (controlled) end-user information. Use of this measurement request filtering capability requires that the TD-AMF be associated with a minimum end-user permission level 2 or 3 respectively. The configuration also specifies whether to ignore the matching rule where the specified end-user data is not available, when the reason for not being available may be due to the end user not providing the information or to a permission restriction. When multiple end-user information matching rules are used concurrently, they must all be matched for a TD-AMF to process the associated measurement request(s). Measurement request filtering may be used separately or in conjunction with multicast sub-addressing, including using information provided by end users (see clause 7.1.1.2). + +AM management tracks measurement requests (and associated reports) using an identifier, which is to be generated by aggregation functions as an AM service provider unique identifier. + +See [ITU-T H.741.2] for metadata elements used to configure sets of measurement requests. + +##### 7.1.2.1 Configuration of services to be measured + +Each measurement request may be configured to indicate which specific services are to be measured (Figure 5). + +A service period for each measured service is defined as the period between a service start event and a service end event. These events correspond to service-specific events such as "channel start" in linear TV or "play" in VoD. + +![Figure 5 – Service period definition. A horizontal line with arrows at both ends, labeled 'Service period' above it. Below the left arrow is the text 'Service start event'. Below the right arrow is the text 'Service end event'. At the bottom right, below the 'Service end event' text, is the code 'H.741.1(12)_F05'.](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +The diagram illustrates the definition of a service period. It consists of a horizontal line with arrows at both ends, labeled "Service period" above it. Below the left arrow is the text "Service start event". Below the right arrow is the text "Service end event". At the bottom right, below the "Service end event" text, is the code "H.741.1(12)\_F05". + +Figure 5 – Service period definition. A horizontal line with arrows at both ends, labeled 'Service period' above it. Below the left arrow is the text 'Service start event'. Below the right arrow is the text 'Service end event'. At the bottom right, below the 'Service end event' text, is the code 'H.741.1(12)\_F05'. + +**Figure 5 – Service period definition** + +A session is defined as a period of time for linear TV, VoD and nPVR, in which an end user is connected to a service provider (between end-user log in and log out), see Figure 6. Figure 6 shows how these relate to service periods, using linear TV as an example. + +![Figure 6 – Session definition. A timeline diagram showing a user session across multiple channels (A, B, and C). The session starts when the user logs in and ends when they log out or the TD switch off. The session duration is marked by a long double-headed arrow labeled 'Session'. Within the session, there are 'Service period' markers for each channel. Channel A and B show overlapping service periods, while Channel C shows a single service period. The timeline is labeled 'Time line' and 'H.741.1(12)_F06'.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram illustrates a session definition on a horizontal timeline. The timeline starts with 'User logs in' and ends with 'User logs out or TD switch off'. A long double-headed arrow labeled 'Session' spans from the start to the end. Above the timeline, three channels are shown: Channel A, Channel B, and Channel C. Channel A and B have overlapping service periods, with 'LTV service start' and 'LTV service stop' markers. Channel C has a single service period with 'LTV service start' and 'LTV service stop' markers. Below the timeline, 'Service period' markers with double-headed arrows indicate the duration of service for each channel. The timeline is labeled 'Time line' at the right end and 'H.741.1(12)\_F06' at the bottom right. + +Figure 6 – Session definition. A timeline diagram showing a user session across multiple channels (A, B, and C). The session starts when the user logs in and ends when they log out or the TD switch off. The session duration is marked by a long double-headed arrow labeled 'Session'. Within the session, there are 'Service period' markers for each channel. Channel A and B show overlapping service periods, while Channel C shows a single service period. The timeline is labeled 'Time line' and 'H.741.1(12)\_F06'. + +**Figure 6 – Session definition** + +See [ITU-T H.741.2] for metadata elements used to configure the services to be measured. + +##### 7.1.2.2 Configuration of content classes to be filtered + +Each measurement request may be configured to indicate whether to filter measurements across services based upon specified content classes. + +Examples of content class types are (1) genres as defined by different organizations which may indicate children's TV, adult TV, religious and political programmes, etc., (2) originating studio IDs as defined by different organizations, series, or any other content classification scheme as defined by different organizations. + +If content filtering is configured but a TD-AMF is unable to determine content-class information about particular content, then measurements associated with that content may occur with constraints. Measurements associated with the unclassified content shall be reported with the constraints of permission Level 1, and shall not be batched with other reports for delivery. + +See [ITU-T H.741.2] for metadata elements used to configure content classes to be filtered. + +##### 7.1.2.3 Configuration of measurement schedule + +Each measurement request includes one or more measurement schedules. A measurement schedule specifies when and how a requested service is to be measured. It specifies measurement periods and how generation of a measurement report will be triggered, either periodically and/or on specific events. + +A measurement period is the duration of time during which measurements may occur, as illustrated in Figure 7. + +Each measurement schedule may include multiple measurement periods, as illustrated in Figure 8. + +Each measurement period may specify on which days of the week and at what start-and-end time measurements may occur. Each measurement period may fall within a day, or cross the boundaries of a single day. A measurement period may not be specified, in which case it is defined by the default which is "always". The number, position and duration of measurement periods per day are independent. + +Measurement periods may cross day boundaries, as illustrated in Figure 9. + +If a measurement period is specified to extend into a day which is not configured as a day to start measurement, the measurement period ends at the configured end time. + +See [ITU-T H.741.2] for metadata elements used to configure measurement schedules. + +![Figure 7 – Measurement period definition. A horizontal line with arrows at both ends, labeled 'Measurement period'. Below the left arrow is 'Start time'. Below the right arrow is 'End time' and 'H.741.1(12)_F07'.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +Figure 7 – Measurement period definition. A horizontal line with arrows at both ends, labeled 'Measurement period'. Below the left arrow is 'Start time'. Below the right arrow is 'End time' and 'H.741.1(12)\_F07'. + +**Figure 7 – Measurement period definition** + +![Figure 8 – Measurement schedule definition. Two diagrams side-by-side. The left diagram shows 'Day 1' with 'Measurement period 1' and 'Measurement period n'. The right diagram shows 'Day M' with 'Measurement period 1' and 'Measurement period k'. A reference label 'H.741.1(12)_F08' is at the bottom right.](5445597cceefaca1ac89e710fe339325_img.jpg) + +Figure 8 – Measurement schedule definition. Two diagrams side-by-side. The left diagram shows 'Day 1' with 'Measurement period 1' and 'Measurement period n'. The right diagram shows 'Day M' with 'Measurement period 1' and 'Measurement period k'. A reference label 'H.741.1(12)\_F08' is at the bottom right. + +**Figure 8 – Measurement schedule definition** + +![Figure 9 – Cross-day measurement period. A diagram showing 'Day A' and 'Day A + 1'. 'Measurement period 1' is on Day A, 'Measurement period n' spans the boundary between Day A and Day A + 1, and 'Measurement period k' is on Day A + 1. A reference label 'H.741.1(12)_F09' is at the bottom right.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +Figure 9 – Cross-day measurement period. A diagram showing 'Day A' and 'Day A + 1'. 'Measurement period 1' is on Day A, 'Measurement period n' spans the boundary between Day A and Day A + 1, and 'Measurement period k' is on Day A + 1. A reference label 'H.741.1(12)\_F09' is at the bottom right. + +**Figure 9 – Cross-day measurement period** + +##### 7.1.2.4 Configuration of elements to be measured + +Each measurement request is configured to indicate which events and sample values are to be measured. + +The events and sample values to be measured are classified into two categories: service-common and service specific: + +- "Service-common" events and samples are defined for two or more specific services. They are defined in [ITU-T H.741.2]. +- "Service-specific" events and samples apply to one specific service. They are defined in [ITU-T H.741.3]. + +"Service-common" events and samples in a measurement request are applied to the specific services configured in that measurement request. In the case where no specific services are configured in that measurement request, then the "service-common" events and samples apply to specific services configured in any measurement request. + +There are three measurement methods which may be used separately or in combination. These methods use a measurement trigger of one of the following: + +- 1) An event. One of several defined end-user initiated events. The elements to be measured are specified for each event. +- 2) A scheduled sample time. Measurement by scheduled sampling is defined by a sequence of sample times with configurable periodicity, where periodicity indicates the regular periods between which measurements are to be captured during the measurement period. The elements to be measured are specified by referring to sets of elements. +- 3) A service start. Measurement by scheduling qualified service start times is defined by a configurable interval, where an interval is the period when measurements are triggered at the first service start of a day. The elements to be measured are specified by referring to sets of elements. + +The basic measurement time definitions are illustrated in Figures 10 to 13. + +![Figure 10: Scheduled sample times diagram. A horizontal timeline shows a 'Measurement period' from 'Start time' to 'End time'. Within this period, two 'Sample time' points are marked. The intervals between 'Start time' and the first 'Sample time', and between the first 'Sample time' and the second 'Sample time', are both labeled 'Periodicity'.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 10: Scheduled sample times diagram. A horizontal timeline shows a 'Measurement period' from 'Start time' to 'End time'. Within this period, two 'Sample time' points are marked. The intervals between 'Start time' and the first 'Sample time', and between the first 'Sample time' and the second 'Sample time', are both labeled 'Periodicity'. + +**Figure 10 – Scheduled sample times** + +The effective measurement period is defined to be when both the measurement period and service period overlap, as illustrated in Figures 11 to 13. + +![Figure 11: Effective measurement period definition (1) diagram. A horizontal timeline shows a 'Measurement period' and a 'Service period' that is entirely contained within the measurement period. The 'Effective measurement period' is indicated as the duration of the service period. Reference H.741.1(12)_F11 is shown at the bottom right.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Figure 11: Effective measurement period definition (1) diagram. A horizontal timeline shows a 'Measurement period' and a 'Service period' that is entirely contained within the measurement period. The 'Effective measurement period' is indicated as the duration of the service period. Reference H.741.1(12)\_F11 is shown at the bottom right. + +**Figure 11 – Effective measurement period definition (1)** + +![Figure 12: Effective measurement period definition (2) diagram. A horizontal timeline shows a 'Measurement period' and a 'Service period' that starts at the beginning of the measurement period and extends beyond its end. The 'Effective measurement period' is indicated as the duration of the measurement period. Reference H.741.1(12)_F12 is shown at the bottom right.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +Figure 12: Effective measurement period definition (2) diagram. A horizontal timeline shows a 'Measurement period' and a 'Service period' that starts at the beginning of the measurement period and extends beyond its end. The 'Effective measurement period' is indicated as the duration of the measurement period. Reference H.741.1(12)\_F12 is shown at the bottom right. + +**Figure 12 – Effective measurement period definition (2)** + +An effective measurement period may span many concatenated measurement periods, supporting measurement requests configured differently for each measurement period. In Figure 13, for example, two different sets of measurements (measurement profiles) occur during an effective measurement period. + +![Figure 13: Effective measurement period definition (3) diagram. A horizontal timeline shows two concatenated 'Measurement period 1' and 'Measurement period 2'. A 'Service period' spans across both. The 'Effective measurement period' is the duration of the service period. 'Measurement profile 1' is associated with the first measurement period, and 'Measurement profile 2' with the second. Reference H.741.1(12)_F13 is shown at the bottom right.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +Figure 13: Effective measurement period definition (3) diagram. A horizontal timeline shows two concatenated 'Measurement period 1' and 'Measurement period 2'. A 'Service period' spans across both. The 'Effective measurement period' is the duration of the service period. 'Measurement profile 1' is associated with the first measurement period, and 'Measurement profile 2' with the second. Reference H.741.1(12)\_F13 is shown at the bottom right. + +**Figure 13 – Effective measurement period definition (3)** + +Within the effective measurement period, events and sample values are measured, as depicted in Figure 14. + +![Figure 14: A timeline diagram showing nested measurement periods. The outermost period is 'Measurement period' from 'Start time' to 'End time'. Inside it is 'Service period', then 'Effective measurement period'. Within the effective measurement period, there are two 'Periodicity' intervals. 'Sample time' markers are shown within the periodicities. 'Event' markers are shown at the start of the service period, the start of the second periodicity, and the end of the effective measurement period. The diagram is labeled H.741.1(12)_F14.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +Figure 14: A timeline diagram showing nested measurement periods. The outermost period is 'Measurement period' from 'Start time' to 'End time'. Inside it is 'Service period', then 'Effective measurement period'. Within the effective measurement period, there are two 'Periodicity' intervals. 'Sample time' markers are shown within the periodicities. 'Event' markers are shown at the start of the service period, the start of the second periodicity, and the end of the effective measurement period. The diagram is labeled H.741.1(12)\_F14. + +**Figure 14 – Sample values and events are measured within the effective measurement period** + +Both service-common and service-specific events and samples are measured only during effective measurement periods. + +Service specific measurements occur only during their respective specific service periods. Whereas, service-common measurements occur during the service period associated with any specific service. + +Measurement requests may be configured to include either service-common only measurements, service specific only measurements, or both service-common measurements and service specific measurements. + +Measurement of events and sample values may be configured following declaration of service-common and/or service specific measurements. Events and sample values may be qualified by a configured parameter. When an event or sample occurs that matches those configured for measurement, it triggers generation of a measurement report. + +Most events need to be configured in a measurement request. However there is one common event which does not require configuration. This "focus" event may occur when the focus of an end user or IPTV platform changes among multiple concurrent targeted IPTV services such that the audio of a particular service is presented. + +Certain service specific events and/or samples may not need to be, or be allowed to be, explicitly configured. Declaring a specific service in a measurement request may lead to certain events and/or samples being set as a default. When multiple measurement requests generate similar reports for these events (having only a difference in MeasurementRequestID), then only one report is included in a report package. The report having the lowest MeasurementRequestID is to be reported. Service specific events and samples are defined in [ITU-T H.741.3]. + +Service start measurements are provided for the measurement of slowly changing information. The interval may be configured to generate a measurement every M integer number of days, see Figure 15. If not configured, the default is to measure at each service start as shown in Figure 16. + +![Figure 15: A timeline diagram showing service start measurements over multiple days. It shows 'Service period A' and 'Service period A+1' on 'Day 1', with 'Measurement period 1' and 'Measurement period n' respectively. An ellipsis indicates subsequent days. On 'Day M', 'Service period X' and 'Service period X+1' are shown, with 'Measurement period 1' and 'Measurement period k' respectively. Arrows labeled 'Scheduled service time measurements' point to the start of each measurement period. The diagram is labeled H.741.1(12)_F15.](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +Figure 15: A timeline diagram showing service start measurements over multiple days. It shows 'Service period A' and 'Service period A+1' on 'Day 1', with 'Measurement period 1' and 'Measurement period n' respectively. An ellipsis indicates subsequent days. On 'Day M', 'Service period X' and 'Service period X+1' are shown, with 'Measurement period 1' and 'Measurement period k' respectively. Arrows labeled 'Scheduled service time measurements' point to the start of each measurement period. The diagram is labeled H.741.1(12)\_F15. + +**Figure 15 – Service start measurements with interval M days** + +![Figure 16: Service start measurements with no interval. The diagram shows a timeline for 'Day 1' with four service periods: A, A+1, B, and B+1. Measurement period 1 is shown between the start of service period A and the start of service period A+1. Measurement period n is shown between the start of service period B and the start of service period B+1. Vertical dashed lines mark the start of each service period. Arrows labeled 'Scheduled service time measurements' point to these start points. The diagram is labeled H.741.1(12)_F16.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Figure 16: Service start measurements with no interval. The diagram shows a timeline for 'Day 1' with four service periods: A, A+1, B, and B+1. Measurement period 1 is shown between the start of service period A and the start of service period A+1. Measurement period n is shown between the start of service period B and the start of service period B+1. Vertical dashed lines mark the start of each service period. Arrows labeled 'Scheduled service time measurements' point to these start points. The diagram is labeled H.741.1(12)\_F16. + +**Figure 16 – Service start measurements with no interval** + +The service context of the service start measurement configuration determines which services are used as reporting triggers. When configured with a specific service, the first occurrence of that specific service triggers a measurement every M days, if it occurs during a measurement period. When configured within a service-common context, the first occurrence of any service triggers a measurement every M days, if it occurs during a measurement period. + +Service start measurements may be configured to trigger measurements at multiple service starts within a day. The service context determines which service start trigger measurements. A specific service context causes measurements to be made at each service start of that service. (This includes channel changes for the linear TV service). A service-common context causes measurements to be made at the start of any service. + +When internal or hybrid permission modes are used, the configuration may specify that if an end-user permit constrains the configured measurements due to permission level, device type or service, then that constraint will be reported. If configured, this report may be sent for any permission level, including permission level 0. + +Configuration of recovery actions due to lack of storage of measurements is specified. Storage priority for events and sample values are configurable. In the case of storage congestion, the priority levels of existing stored measurements and new measurement are compared to decide whether to store the new measurement. + +A storage congestion policy may be configured to either immediately push the oldest measurement reports to free up sufficient storage, or to drop enough of the lowest priority events and/or sample values to free space for new higher priority events and/or sample values. For dropping, the age of lowest priority events and/or sample values is to be used as a tie-breaking criterion. If the immediate push fails, then all measurement reports are considered for dropping. This policy may be configured to apply to multiple or to individual measurement requests. + +See [ITU-T H.741.2] for metadata elements used to configure the events and sample values to be measured. + +##### 7.1.2.5 Configuration of filtering and summarization + +Each measurement request may be configured to use TD-AMF filtering and summarization processing, which may filter reporting of specified events or sample values, and/or additionally report the summarized information. Filtering and summarization may apply to service-common or service-specific events and sample values. + +In the cases of both service-common and service-specific time sampling. + +When a sample value is found to be effectively the same as the previous sample value (a duplicate), configuration determines the reporting action to be taken. The duplicate sample value may either be ignored and not reported, reported as empty, or reported normally. When a sample set consists of + +multiple elements and some of the sample values of these elements change, then the TD-AMF reports the subsequent time samples of all elements (including the unchanged ones). + +Reporting of sampled geographic location is considered to be effectively the same if sample values indicate that a subsequent location is within the configured reporting distance threshold. All other timesampled values are effectively the same when their sample values are equal. + +To obtain a count of events without event details, a list of events may be configured. The event counting period is delimited by either configured time periodicity or events which indicate that the user no longer views the same service. Either will terminate the current event count and start a new event count. + +See [ITU-T H.741.2] for metadata used to configure reporting of geographic location and event counts. See [ITU-T H.741.2] for configuration of policy regarding duplicate sample values. See [ITU-T H.741.3] for filtering and summarization of linear TV measurement reports. + +##### 7.1.2.6 Configuration of delivery schedule + +Each measurement request may include a delivery schedule which may have multiple delivery windows scheduled by time of day. One of four types of delivery modes is configured: + +- 1) **Immediate Push Mode:** When a measurement is made, it is optionally grouped with a number of other measurements within a period of time, before being sent in a measurement report package message. +- 2) **Delayed Push Mode:** Measurements are stored until a TD-AMF randomly picked time during the configured delivery window is reached. At that time the TD-AMF groups measurement reports and sends them in a measurement report package message. + +![Diagram of a delivery window. A horizontal line with arrows at both ends is labeled 'Delivery window'. Below the line, three vertical arrows point upwards to specific points: the left arrow is labeled 'Start delivery window time', the middle arrow is labeled 'Random time', and the right arrow is labeled 'End delivery window time'. Below the right label is the text 'H.741.1(12)_F17'.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +The diagram illustrates a 'Delivery window' as a horizontal line segment with arrows at both ends. Below the line, three vertical arrows point upwards to specific points: the left arrow is labeled 'Start delivery window time', the middle arrow is labeled 'Random time', and the right arrow is labeled 'End delivery window time'. Below the right label is the text 'H.741.1(12)\_F17'. + +Diagram of a delivery window. A horizontal line with arrows at both ends is labeled 'Delivery window'. Below the line, three vertical arrows point upwards to specific points: the left arrow is labeled 'Start delivery window time', the middle arrow is labeled 'Random time', and the right arrow is labeled 'End delivery window time'. Below the right label is the text 'H.741.1(12)\_F17'. + +**Figure 17 – Delivery window** + +- 3) **Pull Mode:** Measurements are stored until a measurement report request message is received from the aggregation functions. This message causes selected measurements to be grouped before being sent in a measurement report package message. A configured policy indicates what the TD-AMF does in the eventuality of storage congestion. +- 4) **Delayed Push and Pull Mode:** Measurements are stored until either a report request message is received from the aggregation function, or a TD-AMF time picked at random during the configured delivery window is reached. Whichever trigger is sooner causes measurements to be grouped before being sent in a measurement report package message. + +The following are configurable for all delivery modes: + +- **Delivery address(es)** – Zero or more URLs used by a TD-AMF to send measurement reports to. The value of an URL may provide an indication of the security and/or transport protocol to be used for each address. The TD-AMF will select one URL to send all measurement reports to. When not specified in a delivery schedule, an address is obtained from the special common structure or else from discovery. +- **Retransmit number** – The number of TD-AMF transmission retries when a measurement report message is not acknowledged (at the transport layer) by the aggregation functions. + +When a delivery schedule is not configured, the following default is used: + +- Immediate push mode. +- Delivery address URL to be used to send measurement reports from the TD-AMF as specified in the AM aggregation function discovery process or as configured in the special common structure. +- Retransmit number is configured in the special common structure. +- The storage congestion policy default applies: this is to drop enough of the lowest priority events and/or sample values to free space for new higher priority events and/or sample values. The age of the lowest priority events and/or sample values is to be used as a tie-breaking criterion. + +See [ITU-T H.741.2] for metadata elements used to configure delivery schedules. + +### 7.2 End-user permits + +End-user privacy policies may be expressed within end-user permits in AM. + +Permits are per end user or multiple end users in a subscription. + +An end-user permit may contain an expiration date, a default permission level, and a default content restriction list. An anonymous UserID may be included if there is a permission level in the permit with a value of less than 3. The identifying UserID may be included if there is a permission level in this permit with a value of more than 2. One or more user permission sets may be specified which allow a permission level to be associated with combinations of services, terminal device types and content restrictions. + +User permissions impact audience measurements depending upon one of three modes used: + +- **External permission mode** – relies upon end-user permissions being managed outside of AM. No end-user permits are used at the TD-AMFs. +- **Internal permission mode** – relies on AM to manage permissions. Permits are created at TD-AMFs and may be made available to other TD-AMFs. They are delivered to the TD-AMF separately from the configuration package and configuration package request response messages. +- **Hybrid permission mode** – relies on a combination of AM and external entities to manage permissions. Permits are delivered to the TD-AMF separately from the configuration package and configuration package request response messages. They are delivered to the TD-AMF from the IPTV SP. + +The TD-AMF learns of which permission mode to use from the discovery process. + +Regarding multiple devices for the internal permission mode, it is not specified how permits are made available to the other devices of the same end user. For the hybrid permission mode, permits for each end-user device are made available when an end user logs in. + +An effective permit is the end-user permit which is in force at a particular time. AM obtains the effective permit from functions outside of AM, which are responsible for associating end users with permits. + +The effectiveness of measurement requests may be reduced when end-user permits are used. If internal or hybrid permission modes are used, then measurement reports may be limited by permission levels of the effective permit. Measurement reports may be disallowed by device type and/or service and/or content. + +In internal and hybrid modes, when the TD-AMF obtains a new permit, it must apply that permit immediately to new measurements. Previously stored measurement reports may be sent without application of the new permit. Receipt of a new permit triggers the TD-AMF to send a configuration request message to aggregation functions. + +If content filtering is included in the effective permit, but a TD-AMF is unable to determine content class information about particular content, then measurements associated with that content may occur with constraints. Measurements associated with the unclassified content shall be reported with the constraints of permission level 1, and shall not be batched with other reports for delivery. + +User permits are optionally included in a configuration request, a configuration request response and configuration messages to support the management of permits, the details of which are out of the scope of AM. + +See clause 9.2 for more details regarding permission modes. + +See [ITU-T H.741.2] for the metadata elements of user permits. + +## 8 Specific aspects of reporting + +### 8.1 Reporting of services which start or end outside measurement periods + +A ServiceInstanceID is generated when a service starts, so it may be generated outside of a measurement period. When this service is still being consumed at the start of a measurement period, then a service start event report will be generated with the time of the start of the measurement period, unless the same service start report had previously been generated. When a service end event occurs after a measurement period, then a service end event report will be generated with the time of the end of the previous measurement period. + +![Figure 18: Reporting of services which start or end outside measurement periods. The diagram shows a timeline with five points: A (Service start), B (start of Measurement Period 1), C (start of Measurement Period 2), D (end of Measurement Period 2), and E (Service end). A 'Service period' is indicated by a long double-headed arrow from A to E. 'Effective measurement Period 1' is shown from B to C, and 'Effective measurement Period 2' is shown from C to D. 'Measurement Period 3' is shown starting at D. The label H.741.1(12)_F18 is in the bottom right.](9b686adccf125267a013fa25721231a3_img.jpg) + +Figure 18: Reporting of services which start or end outside measurement periods. The diagram shows a timeline with five points: A (Service start), B (start of Measurement Period 1), C (start of Measurement Period 2), D (end of Measurement Period 2), and E (Service end). A 'Service period' is indicated by a long double-headed arrow from A to E. 'Effective measurement Period 1' is shown from B to C, and 'Effective measurement Period 2' is shown from C to D. 'Measurement Period 3' is shown starting at D. The label H.741.1(12)\_F18 is in the bottom right. + +**Figure 18 – Reporting of services which start or end outside measurement periods** + +In Figure 18, a service start event occurs at A so a ServiceInstanceID is allocated and a report is generated. If or when a measurement period starts which is configured to measure that service, then the start time B of that measurement period is associated with the service start event. The service start event is reported per the associated measurement request. If the service period continues through the time of a subsequent measurement period C, then the service start event is not reported again. If the associated service end event occurs outside a measurement period at time E, then it is associated with the time of the end of the previous measurement period D. The service end event is reported per the associated measurement request. + +### 8.2 Reporting surrounding restricted content + +Changes in genres are monitored by a TD-AMF, when restricted content starts to be played at time A in Figure 19 below, then measurements stop, and a service stop event report shall be generated. When un-restricted content starts to be played after restricted content, then + +measurements may start. A service start event report shall indicate the start time B, of the unrestricted content. + +![Figure 19: Reporting surrounding restricted content. The diagram shows a timeline with three segments: 'Unrestricted content, measurements occur', 'Restricted content, no measurements occur', and 'Unrestricted content, measurements occur'. A double-headed arrow above the segments is labeled 'Effective measurement period'. Below the segments, two circles labeled 'A' and 'B' are positioned under the boundaries between the segments. The text 'H.741.1(12)_F19' is in the bottom right corner.](043e64d41a3368d138ace3816fd26469_img.jpg) + +Figure 19: Reporting surrounding restricted content. The diagram shows a timeline with three segments: 'Unrestricted content, measurements occur', 'Restricted content, no measurements occur', and 'Unrestricted content, measurements occur'. A double-headed arrow above the segments is labeled 'Effective measurement period'. Below the segments, two circles labeled 'A' and 'B' are positioned under the boundaries between the segments. The text 'H.741.1(12)\_F19' is in the bottom right corner. + +**Figure 19 – Reporting surrounding restricted content** + +### 8.3 Reporting of user presence + +The detected presence of end users may only be reported when the effective permit (if provided) grants permission level of 1-3. + +### 8.4 Reporting changes due to effective permit changes + +Measurement permissions may be available to the TD-AMF expressed in an effective permit. When the effective permit changes, reflecting a change in permissions granted, then measurements and reports shall immediately reflect those permission changes. + +### 8.5 Reporting of storage congestion + +In the case where event information and/or sample information has been dropped due to storage congestion and priority in a TD-AMF, indication of the services impacted is reported within the measurement report message. + +### 8.6 Nothing to report + +In the case where pull mode is used and the aggregation functions request measurement reports from a TD-AMF which has nothing to report, then no measurement report is returned by that TD-AMF. + +## 9 Security, privacy and permission mechanisms + +### 9.1 Security and privacy of AM messages + +AM messages, if left unprotected, unverified, and unauthenticated will allow an adversary to compromise the very intention of audience measurement. + +The entities of the AM architecture need to adhere to the AM security requirements in order to achieve audience measurement that is verifiably correct, unadulterated, and preserves end-user privacy – an important aspect which determines the willingness of end users to share their AM data. An algorithm or a set of algorithms can be used to provide security for AM information. The following clauses elaborate implementation considerations for each of the security requirements in the AM architecture, while leaving it to the implementer to implement them in isolation or in combination through a single algorithm/mechanism or a set of algorithms/mechanisms. In the following clauses, multiple algorithm/mechanisms are specified. For interoperability, AGFs and TD-AMFs must use the same algorithm/mechanisms. The methods of communications of choices between the entities are specified. + +#### 9.1.1 Authentication + +In order to guarantee that the TD-AMF is interacting with the intended AGF, and vice versa, the TD-AMF and AGF are required to authenticate each other directly or indirectly via a third-party. This clause describes direct authentication. Indirect authentication is out of the scope of this Recommendation. + +The absence of authentication would allow TD-AMFs to be configured by a rogue entity, or an aggregation function to be fed with modified/stale/garbage AM reports on behalf of TD-AMFs. + +It is recommended to implement an authentication mechanism consisting of two sub-mechanisms: primary and secondary. The primary authentication mechanism must be able to perform authentication on its own. The secondary authentication mechanism is optional. An authentication mechanism requires a TD-AMF or an AGF entity to be authenticated to provide a proof of possession of credentials, e.g., password or digital certificate. Primary authentication mechanisms involve the use of actual credentials in proof generation, whereas secondary authentication mechanisms use pseudo-credentials in proof generation. An authenticator issues pseudo-credentials upon successful primary authentication. Secondary authentication mechanism can be employed for authenticating all successive communications that follow the first successfully authenticated communication. + +In direct authentication mode, a TD-AMF or an AGF entity presents proof of possession of its credentials directly to the other. In indirect authentication mode, a trusted third party is involved which performs entity authentication and issues a token that in turn can be used as proof of possession of credentials. AM may support either or both authentication modes. + +Depending on the use of push, pull, or pull and push (hybrid) message sequences of communication, the role of the authenticator is determined by the TD-AMF or AGF that initiates the message sequence. For example, prior to a configuration push message, the AGF must authenticate itself to the TD-AMFs, or prior to a push report message TD-AMFs must authenticate themselves to the AGF. + +The first instance of authentication between a TD-AMF and an AGF takes place after service discovery but before TD-AMF configuration (see Figure 1). All successive message sequences between previously authenticated entities also need to be authenticated. Secondary authentication may be employed for such successive message sequences. The choices of cryptographic protocols for authentication are indicated in the capabilities profile (see [ITU-T H.741.2]) and in the discovery data structure (see Appendix I). + +**Configuration pull message sequence** – Prior to the configuration request message, the TD-AMF authenticates the AGF using transport layer security (TLS) [IETF RFC 5246] which makes use of ITU-T X.509v3 [ITU-T X.509] digital certificates. TD-AMFs do not accept configuration packages from an AGF without this type of authentication. This requires the AGF to have a valid digital certificate issued by a Certification Authority (CA). TD-AMFs need to authenticate themselves before sending configuration response error messages. TD-AMFs use their digital certificates to authenticate themselves with the AGFs. In the absence of digital certificates issued to TD-AMFs, TD-AMFs must use their respective UserID and corresponding password issued at the time of registration with IPTV SP. A TD-AMF may obtain a token from its IPTV SP, which can be used as a credential for authentication with the AGF. The AGF trusts the IPTV SP in such a type of indirect authentication. To minimize the cost of authentication for successive AM communications between the TD-AMF and AGF, a secondary authentication mechanism one-time password (OTP) [ITU-T X.1153] or hash-based message authentication code (HMAC) [FIPS PUB 198-1] may be communicated outside of AM and used. + +**Configuration push message sequence** – Prior to the configuration message, the AGF authenticates itself to TD-AMFs using transport layer security (TLS) as above. Prior to sending a configuration acknowledgement or configuration error message, TD-AMFs need to authenticate themselves to the AGF as above. + +**Configuration pull and push message sequence** – This requires the authentication combination of the pull message sequences, and may require authentication of the push message sequences, depending upon whether the pull message sequence authentication has expired. + +**Measurement report pull sequence** – If the previous primary authentication has expired, then prior to the measurement report request message, the AGF needs to authenticate itself to the TD-AMFs again using primary mechanism. If the previous primary authentication has not expired, then a measurement report request message can continue to use the secondary authentication mechanism. Prior to sending a measurement report message or measurement report request error message, a TD-AMF needs to authenticate itself to an AGF as above. The measurement report error message may not need separate authentication, depending upon the transport mechanism. + +**Measurement report push sequence** – If the previous primary authentication has not expired, then a measurement report message can continue to use the secondary authentication mechanism. If the previous authentication has expired, then prior to sending a measurement report message, a TD-AMF needs to authenticate itself to an AGF as above. If the previous primary authentication has expired, then prior to responding with a measurement report error message, the AGF needs to authenticate itself. Depending upon the transport mechanism, the measurement report error message may not need separate authentication. + +AM messages that are not authenticated are not accepted. + +All measurement report message sequence authentications must expire at the end of a delivery period. Optionally, implementers can choose an expiration period smaller than the delivery period specified in a configuration package by an AGF. All configuration message sequence authentication must expire at the end of a configuration message sequence. + +A change in internal and hybrid permissions on a TD-AMF will cause the expiration of all on-going communications and reinitiate authentication with an AGF. + +#### 9.1.2 Confidentiality + +In order to safeguard end-user privacy, it is required that all unicast AM messages be encrypted. It is recommended that all multicast AM messages be encrypted. For unicast and multicast messages see [ITU-T H.741.4]. + +The absence of confidentiality would allow an unauthorized entity to understand AM messages. This could lead to theft of information, uncovering of personal end-user information which could contribute to identity theft, etc. In addition, it would make it easier to conduct attacks on the AM system. + +The choices of cryptographic protocols for confidentiality are indicated in the capabilities profile and in the discovery data structure. + +Confidentiality is usually achieved with the help of cryptographic protocols that support encryption/decryption. The TLS protocol [IETF RFC 5246] supports an array of negotiable encryption/decryption methods that require cryptographic keys to perform the encryption or decryption operations on the data. Cryptographic keys are generated and shared between a TD-AMF and an AGF at the end of successful authentication. In the case of digital certificates not being issued to TD-AMFs, it is recommended that the TLS-SRP [b-IETF RFC 5054] protocol be used to establish the cryptographic keys. The choices are indicated in the capabilities profile and in the discovery data structure. + +For TD-AMFs that do not make use of the TLS protocol for key agreement and key distribution, (e.g., smart-card-based TD-AMFs that have pre-shared keys), it is recommended to use AES [b-FIPS PUB 197]. + +In Figure 20, authentication and confidentiality are shown for the configuration pull message sequence. + +In Figure 21, authentication and confidentiality are shown for the configuration push message sequence. If the previous primary authentication has expired, an AGF must authenticate itself before sending a configuration message. + +For configuration of pull and push (hybrid mode), authentication and confidentiality occur as in Figure 20, followed by Figure 21. + +In Figure 22, authentication and confidentiality are shown for the measurement report pull message sequence. + +In Figure 23, authentication and confidentiality are shown for the measurement report push message sequence. + +![Sequence diagram for Figure 20: Security in the configuration 'pull' message sequence. The diagram shows interactions between TD-AMF and AGF. TD-AMF sends a 'Request for AGF authentication' to AGF. AGF responds with 'AGF authentication + key agreement' (symmetric key encrypted unicast AM message). TD-AMF then sends a 'Configuration request message' (symmetric key encrypted unicast AM message). AGF can respond with 'Configuration request response message' (symmetric key encrypted unicast or optionally encrypted multicast AM message) or an error. TD-AMF then performs its own authentication. The sequence ends with 'Configuration response error message' (symmetric key encrypted unicast AM message). A legend indicates that solid black arrows represent symmetric key encrypted unicast AM messages, and hollow arrows represent symmetric key encrypted unicast or optionally encrypted multicast AM messages. The diagram is labeled H.741.1(12)_F20.](6470d350326789d5306eabcb76533951_img.jpg) + +``` + +sequenceDiagram + participant TD-AMF + participant AGF + Note left of TD-AMF: Configuration "pull" +message sequence + TD-AMF->>AGF: Request for AGF authentication + AGF-->>TD-AMF: AGF authentication + key agreement + TD-AMF->>AGF: Configuration request message + rect rgb(240, 240, 240) + Note right of AGF: One of + AGF-->>TD-AMF: Configuration request error message + AGF-->>TD-AMF: Configuration request response message + end + TD-AMF->>AGF: TD-AMF authentication + TD-AMF->>AGF: Configuration response error message + +``` + +H.741.1(12)\_F20 + +⬤→ Symmetric key encrypted unicast AM message +▭→ Symmetric key encrypted unicast or optionally encrypted multicast AM message + +Sequence diagram for Figure 20: Security in the configuration 'pull' message sequence. The diagram shows interactions between TD-AMF and AGF. TD-AMF sends a 'Request for AGF authentication' to AGF. AGF responds with 'AGF authentication + key agreement' (symmetric key encrypted unicast AM message). TD-AMF then sends a 'Configuration request message' (symmetric key encrypted unicast AM message). AGF can respond with 'Configuration request response message' (symmetric key encrypted unicast or optionally encrypted multicast AM message) or an error. TD-AMF then performs its own authentication. The sequence ends with 'Configuration response error message' (symmetric key encrypted unicast AM message). A legend indicates that solid black arrows represent symmetric key encrypted unicast AM messages, and hollow arrows represent symmetric key encrypted unicast or optionally encrypted multicast AM messages. The diagram is labeled H.741.1(12)\_F20. + +**Figure 20 – Security in the configuration "pull" message sequence** + +![Sequence diagram for Figure 21: Security in the configuration 'push' message sequence. The diagram shows interactions between TD-AMF and AGF. TD-AMF sends 'AGF authentication + key agreement, if expired' (symmetric key encrypted unicast AM message) to AGF. AGF responds with 'Configuration message' (symmetric key encrypted unicast or optionally encrypted multicast AM message). TD-AMF then performs its own authentication. TD-AMF can then send 'Configuration ack message' (symmetric key encrypted unicast AM message) or 'Configuration error message' (symmetric key encrypted unicast AM message) to AGF. A legend indicates that solid black arrows represent symmetric key encrypted unicast AM messages, and hollow arrows represent symmetric key encrypted unicast or optionally encrypted multicast AM messages. The diagram is labeled H.741.1(12)_F21.](5b6e139e89c6ce90107ea7d7d77620a0_img.jpg) + +``` + +sequenceDiagram + participant TD-AMF + participant AGF + Note left of TD-AMF: Configuration "push" +message sequence + TD-AMF->>AGF: AGF authentication + key agreement, if expired + AGF-->>TD-AMF: Configuration message + rect rgb(240, 240, 240) + Note left of TD-AMF: Zero or +one of + TD-AMF->>AGF: TD-AMF authentication + TD-AMF->>AGF: Configuration ack message + TD-AMF->>AGF: Configuration error message + end + +``` + +H.741.1(12)\_F21 + +⬤→ Symmetric key encrypted unicast AM message +▭→ Symmetric key encrypted unicast or optionally encrypted multicast AM message + +Sequence diagram for Figure 21: Security in the configuration 'push' message sequence. The diagram shows interactions between TD-AMF and AGF. TD-AMF sends 'AGF authentication + key agreement, if expired' (symmetric key encrypted unicast AM message) to AGF. AGF responds with 'Configuration message' (symmetric key encrypted unicast or optionally encrypted multicast AM message). TD-AMF then performs its own authentication. TD-AMF can then send 'Configuration ack message' (symmetric key encrypted unicast AM message) or 'Configuration error message' (symmetric key encrypted unicast AM message) to AGF. A legend indicates that solid black arrows represent symmetric key encrypted unicast AM messages, and hollow arrows represent symmetric key encrypted unicast or optionally encrypted multicast AM messages. The diagram is labeled H.741.1(12)\_F21. + +**Figure 21 – Security in the configuration "push" message sequence** + +![Sequence diagram for measurement report 'pull' sequence between TD-AMF and AGF. The sequence starts with AGF sending an authentication + key agreement message to TD-AMF. TD-AMF responds with a measurement report request message. AGF replies with TD-AMF authentication, if expired. TD-AMF then sends a measurement report request error message or a measurement report message. AGF responds with a measurement report error message. The diagram is labeled H.741.1(12)_F22. A legend indicates that solid black rectangles represent symmetric key encrypted unicast AM messages, and open rectangles represent symmetric key encrypted unicast or optionally encrypted multicast AM messages. A bracket on the left side of the TD-AMF lifeline, labeled 'Measurement report "pull" sequence' and 'One or both of', encompasses the TD-AMF authentication, measurement report request error message, and measurement report message.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +Sequence diagram for measurement report 'pull' sequence between TD-AMF and AGF. The sequence starts with AGF sending an authentication + key agreement message to TD-AMF. TD-AMF responds with a measurement report request message. AGF replies with TD-AMF authentication, if expired. TD-AMF then sends a measurement report request error message or a measurement report message. AGF responds with a measurement report error message. The diagram is labeled H.741.1(12)\_F22. A legend indicates that solid black rectangles represent symmetric key encrypted unicast AM messages, and open rectangles represent symmetric key encrypted unicast or optionally encrypted multicast AM messages. A bracket on the left side of the TD-AMF lifeline, labeled 'Measurement report "pull" sequence' and 'One or both of', encompasses the TD-AMF authentication, measurement report request error message, and measurement report message. + +**Figure 22 – Security in measurement report "pull" sequence** + +![Sequence diagram for measurement report 'push' sequence between TD-AMF and AGF. The sequence starts with TD-AMF sending a request for AGF authentication, if expired, to AGF. AGF responds with AGF authentication + key agreement, if expired. TD-AMF then sends TD-AMF authentication, if expired, to AGF. AGF responds with a measurement report message. TD-AMF then sends a measurement report error message. The diagram is labeled H.741.1(12)_F23. A legend indicates that solid black rectangles represent symmetric key encrypted unicast AM messages. A bracket on the left side of the TD-AMF lifeline, labeled 'Measurement report "push" sequence', encompasses the TD-AMF authentication, measurement report message, and measurement report error message.](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) + +Sequence diagram for measurement report 'push' sequence between TD-AMF and AGF. The sequence starts with TD-AMF sending a request for AGF authentication, if expired, to AGF. AGF responds with AGF authentication + key agreement, if expired. TD-AMF then sends TD-AMF authentication, if expired, to AGF. AGF responds with a measurement report message. TD-AMF then sends a measurement report error message. The diagram is labeled H.741.1(12)\_F23. A legend indicates that solid black rectangles represent symmetric key encrypted unicast AM messages. A bracket on the left side of the TD-AMF lifeline, labeled 'Measurement report "push" sequence', encompasses the TD-AMF authentication, measurement report message, and measurement report error message. + +**Figure 23 – Security in measurement report "push" sequence** + +#### 9.1.3 Integrity + +In order to ensure that the AM messages are not modified by an attacker, it is required that all AM messages include a proof to ensure that their data is unmodified. In order to ensure that the AM messages are not used in a replay attack, it is required that all AM messages are valid in time. Receivers discard messages for which modification checks or valid time checks fail. + +The absence of modification and valid time indicators will allow attackers to misconfigure TD-AMFs, and to falsely trigger abnormal situation responses. + +Every AM message has its own expiration time. Every multicast message also has its own cryptographic digest (SHA-256) and a digital signature (RSA-1024). + +#### 9.1.4 Non-repudiation (see [b-ITU-T X.800]) + +In order to ensure the authenticity of AM information, it is required to guarantee the authenticity of data received. + +The absence of non-repudiation will allow an authenticated malicious entity to deny its actions. + +The AM messages for which non-repudiation is most important are the measurement reports which are expected to be audited to certify the output of AM. The inclusion of signatures provides non-repudiation for AM reports. + +#### 9.1.5 Privacy + +In order to support privacy, it is recommended that the protection of end-user information and identity, and AM message unlinkability, be supported. + +In the absence of protection over end-user information and identity, an end-user's privacy policy cannot be met. This would effectively restrict the information that the AM system could support due to a lack of end-user trust, e.g., voluntary end-user controlled information. + +The AM system supports mechanisms to protect end-user information and identification within the AM data structures. End-user information elements are classified as "controlled" or "uncontrolled", which supports differentiated handling. End-user permission levels (see [ITU-T H.741.0]) are used to control the reporting by TD-AMFs of end-user information and to choose to use either AnonID vs. UserID (see [ITU-T H.741.2]) for identity control. + +In order to achieve unlinkability between a sender and its AM report, it is recommended to provide sender-anonymity. + +In the absence of unlinkability, a receiver can correlate the sender of the AM report message with other information previously or subsequently obtained. For example, an AGF may use the IP address of a TD-AMF to correlate anonymous AM report messages with stored information to de-anonymize the TD-AMF. + +The AM system relies upon the AGF to remove unintentional linkability information before providing information to higher functions. The details of such filtering are out of the scope of this Recommendation. Further considerations regarding unlinkability are discussed in Appendix V. + +#### **9.1.6 Summary of security methods and corresponding algorithms** + +The security methods and corresponding algorithms used for downstream and upstream AM messages are summarized in Table 1. + +**Table 1 – Security methods and corresponding algorithms** + +| Security capabilities | Security methods and corresponding algorithms | | | | | | | | +|-----------------------|----------------------------------------------------------------------------|--------------------|-----------------------------------------------------------------------------|--------------------|----------------------------------------------------------------------------|---------------------|----------------------------------------------|---------------------| +| | Downstream AM messages | | | | Upstream AM messages | | | | +| | AGF → | | TD-AMF | | TD-AMF → | | AGF | | +| | Method | Algorithm | Method | Algorithm | Method | Algorithm | Method | Algorithm | +| Authentication | Digital certificate | RSA-1024 | Digital certificate verification | RSA-1024 | Digital certificate or password | RSA-1024 or TLS-SRP | Digital certificate or password verification | RSA-1024 or TLS-SRP | +| Confidentiality | (preceded by authentication for key agreement)
    Symmetric key encryption | AES-256 | Symmetric key decryption | AES-256 | (preceded by authentication for key agreement)
    Symmetric key encryption | AES-256 | Symmetric key decryption | AES-256 | +| Integrity | Hash generation + optional digital signature (for multicast) | SHA-256 + RSA-1024 | Hash verification + optional digital signature verification (for multicast) | SHA-256 + RSA-1024 | – | – | – | – | + +### 9.2 End-user permission operation modes + +This Recommendation includes three modes to support the requesting, receipt, and storing of an end-user response and to ensure that measurement happens with end-user permission. A summary description of these modes is provided in the following clauses. + +Deployment considerations of end-user permission modes are discussed in Appendix II. + +#### 9.2.1 External permission mode + +In external permission mode, an IPTV SP is responsible for obtaining permits and is responsible for using those permits. + +The request and receipt of end-user permissions occur within the IPTV SP system. In this mode, AM end-user permissions are part of the end-user information stored by the IPTV service provider. The IPTV SP provides the tool to allow the end users to set their AM end-user permissions for the different services it offers, e.g., telephone, web page or linear TV customer-care channel. The details of the tool are out of the scope of this Recommendation. + +When an IPTV SP obtains end-user permissions, an IPTV SP function may combine one or more end-user permits into an effective permit. The effective permit is used to constrain configuration directives which are inputs to the aggregation functions. The details of configuration directives are out of the scope of this Recommendation. The aggregation functions configure the TD-AMFs with configurations for sets of end users that have given similar permissions. + +In this mode, a TD-AMF does not have access to end-user permits. Figure 24 illustrates the different steps of the IPTV system operation with a focus on the use of the external permission mode. The configuration pull mode message sequence is shown in the figure, however the permission mode is independent of the configuration mode, so either the configuration push mode or the configuration hybrid mode could be used. + +![Sequence diagram illustrating permission flows in external permission mode. The diagram shows interactions between End user, TD-AMF (Default end-user permit), IPTV SP (End-user profile storage including end-user permissions), and Aggregation functions. The sequence starts with the End user sending an 'End-user permission setting' to the IPTV SP. The IPTV SP then sends 'End-user permission constrained configuration directives and SubscriberID' to the Aggregation functions. The TD-AMF sends a 'Configuration request message (ServiceProviderIdentifier, SubscriberID, etc.)' to the Aggregation functions. The Aggregation functions respond with 'Configuration request response message' to the TD-AMF. The TD-AMF then sends 'TD-AMF configuration' to the IPTV SP. The IPTV SP performs 'IPTV service consumption' and sends a 'Measurement report message' to the Aggregation functions. The TD-AMF performs 'IPTV service and AM operation'.](836b0790cef5469a167fa8931df4e408_img.jpg) + +``` +sequenceDiagram + participant End user + participant TD-AMF as TD-AMF +(Default end-user permit) + participant IPTV SP as IPTV SP +(End-user profile storage +including end-user permissions) + participant Aggregation functions + + Note left of TD-AMF: TD-AMF configuration + Note left of IPTV SP: IPTV service and AM operation + + End user->>IPTV SP: End-user permission setting + IPTV SP->>Aggregation functions: End-user permission constrained configuration directives and SubscriberID + TD-AMF->>Aggregation functions: Configuration request message (ServiceProviderIdentifier, SubscriberID, etc.) + Aggregation functions-->>TD-AMF: Configuration request response message + TD-AMF->>IPTV SP: TD-AMF configuration + IPTV SP->>Aggregation functions: IPTV service consumption + IPTV SP->>Aggregation functions: Measurement report message +``` + +Sequence diagram illustrating permission flows in external permission mode. The diagram shows interactions between End user, TD-AMF (Default end-user permit), IPTV SP (End-user profile storage including end-user permissions), and Aggregation functions. The sequence starts with the End user sending an 'End-user permission setting' to the IPTV SP. The IPTV SP then sends 'End-user permission constrained configuration directives and SubscriberID' to the Aggregation functions. The TD-AMF sends a 'Configuration request message (ServiceProviderIdentifier, SubscriberID, etc.)' to the Aggregation functions. The Aggregation functions respond with 'Configuration request response message' to the TD-AMF. The TD-AMF then sends 'TD-AMF configuration' to the IPTV SP. The IPTV SP performs 'IPTV service consumption' and sends a 'Measurement report message' to the Aggregation functions. The TD-AMF performs 'IPTV service and AM operation'. + +**Figure 24 – Permission flows in external permission mode** + +NOTE 1 – The "SubscriberID" is an identifier generated by the IPTV SP. Multiple end-users may be represented by the single SubscriberID and the associated end-user permit. + +NOTE 2 – End-user permission setting is optional before the first connection to the IPTV service provider. The default "AM user permission level" is "no AM permitted". + +NOTE 3 – After connection to the IPTV service provider, the end user may modify its AM end-user permissions at any time, like the other elements of its end-user information stored by the IPTV service provider. When the modification of the end-user permit may have an impact on the previously delivered configuration package, the IPTV SP issues a revised configuration directive. + +Use of the external permission mode may constrain the use of multicast sub-addressing (see clause II.3.1). + +#### 9.2.2 Internal permission mode + +In internal permission mode, an AM SP is responsible for obtaining permits and is responsible for using those permits. + +In this mode, the request and receipt of end-user permission occurs within the AM system. TD-AMFs support the ability to ask for an end user's permission, and store responses. They are capable of autonomously re-asking for an end user's permission just prior to expiration of previously granted permission. The details of the interaction between the end user and the TD-AMF, e.g., interactive pop-up or EPG, are out of the scope of this Recommendation. + +Specific measurements in the received configuration package may be disallowed by the TD-AMF depending upon the end-user permissions. Using this mode, AM enables or disables measurements across multiple-federated (federated opt-in, where end-user consent for audience measurements on one device in a home is extended to cover multiple devices in that home) audience measurement devices via messages relayed by the aggregation functions. Note that messages to support federation of permits between aggregation functions and TD-AMFs are out of the scope of this Recommendation. + +In this mode, the configuration process does not need to know about end-user permissions. Figure 25 illustrates the different steps of the IPTV system operation with a focus on the use of internal permission mode. The configuration pull mode message sequence is shown in Figure 25. However, permission mode is independent of configuration mode, so either configuration push mode or configuration hybrid mode could be used. + +![Sequence diagram illustrating permission flows in internal permission mode. The diagram shows interactions between End user, TD-AMF (Default end-user permit), IPTV SP (End-user profile storage), and Aggregation functions. The sequence starts with the End user sending an 'End-user permission setting' to the TD-AMF. The TD-AMF then sends a 'Configuration request message (ServiceProviderIdentifier, SubscriberID, End-user permit, etc.)' to the IPTV SP. The IPTV SP sends an 'Optional end-user info request (SubscriberID)' to the Aggregation functions, which respond with 'UserID Info'. The IPTV SP then sends a 'Configuration request response message' to the TD-AMF. The TD-AMF sends a 'TD-AMF configuration' message to the End user. The End user then sends an 'IPTV service consumption' message to the IPTV SP. Finally, the IPTV SP sends a 'Measurement report message' to the Aggregation functions. The diagram is labeled H.741.1(12)_F25.](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) + +``` + +sequenceDiagram + participant End user + participant TD-AMF as TD-AMF (Default end-user permit) + participant IPTV SP as IPTV SP (End-user profile storage) + participant Aggregation functions + + Note left of End user: End-user permission setting + TD-AMF->>IPTV SP: Configuration request message (ServiceProviderIdentifier, SubscriberID, End-user permit, etc.) + IPTV SP->>Aggregation functions: Optional end-user info request (SubscriberID) + Aggregation functions-->>IPTV SP: UserID Info + IPTV SP-->>TD-AMF: Configuration request response message + TD-AMF->>End user: TD-AMF configuration + Note left of End user: IPTV service and AM operation + End user->>IPTV SP: IPTV service consumption + IPTV SP-->>Aggregation functions: Measurement report message + +``` + +Sequence diagram illustrating permission flows in internal permission mode. The diagram shows interactions between End user, TD-AMF (Default end-user permit), IPTV SP (End-user profile storage), and Aggregation functions. The sequence starts with the End user sending an 'End-user permission setting' to the TD-AMF. The TD-AMF then sends a 'Configuration request message (ServiceProviderIdentifier, SubscriberID, End-user permit, etc.)' to the IPTV SP. The IPTV SP sends an 'Optional end-user info request (SubscriberID)' to the Aggregation functions, which respond with 'UserID Info'. The IPTV SP then sends a 'Configuration request response message' to the TD-AMF. The TD-AMF sends a 'TD-AMF configuration' message to the End user. The End user then sends an 'IPTV service consumption' message to the IPTV SP. Finally, the IPTV SP sends a 'Measurement report message' to the Aggregation functions. The diagram is labeled H.741.1(12)\_F25. + +**Figure 25 – Permission flows in internal permission mode** + +NOTE 1 – The "SubscriberID" is an identifier generated by the IPTV SP. Multiple end-users may be represented by the single SubscriberID and the associated end-user permit. + +NOTE 2 – End-user permission setting is optional before the first connection to the IPTV service provider. The default "AM user permission level" is "no AM permitted". + +NOTE 3 – The end user may modify its AM end-user permissions at any time. Any impact on measurements is immediate. + +#### 9.2.3 Hybrid permission mode + +In hybrid permission mode, an IPTV SP is responsible for obtaining permits and an AM service provider is responsible for using those permits. + +The request and receipt of end-user permissions occur within the IPTV SP system. In this mode, AM end-user permissions are part of the end-user information stored by the IPTV service provider. The IPTV SP provides the tool to allow the end users to set their AM end-user permissions for the different services it offers. + +The TD-AMF gets the permit from the IPTV SP system, and may use the permit for local filtering, or send it to the aggregation functions to filter configuration packages. The messages to support distribution of permits from the IPTV SP to TD-AMFs are out of the scope of this Recommendation. + +The TD-AMF supports the ability to access and use end-user permits to: + +- get permits from the IPTV service provider. +- send permits to the aggregation functions. +- locally filter audience measurement requested by the AM service provider depending upon these permits. +- report audience measurement with all the elements or part of the elements requested by the AM service provider, depending upon these permits. + +Figure 26 illustrates the different steps of the IPTV system operation with a focus on the use of hybrid permission mode. The configuration pull mode message sequence is shown in the figure. However, permission mode is independent of configuration mode, so either configuration push mode or configuration hybrid mode could be used. + +![Sequence diagram illustrating permission flows in hybrid permission mode. The diagram shows interactions between End user, TD-AMF (Default end-user permit), IPTV SP (End-user profile storage including end-user permissions), and Aggregation functions. The sequence includes: 1. End user sends 'End-user permission setting' to TD-AMF. 2. TD-AMF sends 'End-user permit and subscriberID' to IPTV SP. 3. TD-AMF sends 'Configuration request message (ServiceProviderIdentifier, SubscriberID, End-user permit, etc.)' to Aggregation functions. 4. Aggregation functions send 'Optional end-user info request (SubscriberID)' to IPTV SP. 5. IPTV SP sends 'UserID Info' to Aggregation functions. 6. Aggregation functions send 'Configuration request response message' to TD-AMF. 7. TD-AMF sends 'TD-AMF configuration' to IPTV SP. 8. IPTV SP sends 'IPTV service consumption' to TD-AMF. 9. TD-AMF sends 'IPTV service and AM operation' to IPTV SP. 10. IPTV SP sends 'Measurement report message' to Aggregation functions. The diagram is labeled H.741.1(12)_F26.](409498e57b1f988b2b604d12cd997002_img.jpg) + +Sequence diagram illustrating permission flows in hybrid permission mode. The diagram shows interactions between End user, TD-AMF (Default end-user permit), IPTV SP (End-user profile storage including end-user permissions), and Aggregation functions. The sequence includes: 1. End user sends 'End-user permission setting' to TD-AMF. 2. TD-AMF sends 'End-user permit and subscriberID' to IPTV SP. 3. TD-AMF sends 'Configuration request message (ServiceProviderIdentifier, SubscriberID, End-user permit, etc.)' to Aggregation functions. 4. Aggregation functions send 'Optional end-user info request (SubscriberID)' to IPTV SP. 5. IPTV SP sends 'UserID Info' to Aggregation functions. 6. Aggregation functions send 'Configuration request response message' to TD-AMF. 7. TD-AMF sends 'TD-AMF configuration' to IPTV SP. 8. IPTV SP sends 'IPTV service consumption' to TD-AMF. 9. TD-AMF sends 'IPTV service and AM operation' to IPTV SP. 10. IPTV SP sends 'Measurement report message' to Aggregation functions. The diagram is labeled H.741.1(12)\_F26. + +**Figure 26 – Permission flows in hybrid permission mode** + +NOTE 1 – The "SubscriberID" is an identifier generated by the IPTV SP. Multiple end-users may be represented by the single SubscriberID and the associated end-user permit. + +NOTE 2 – End-user permission setting is optional before the first connection to the IPTV service provider. The default "AM user permission level" is "no AM permitted". + +NOTE 3 – After connection to the IPTV service provider, the end user may modify its AM end-user permissions at any time, like the other elements of its end-user information stored by the IPTV service provider. The distribution of the modified end user permit is out of scope of this Recommendation. When the modification of the end-user permit may have an impact on the configuration package it received, then the TD-AMF sends a configuration request message. + +## 10 Abnormal situations and potential recovery actions + +Abnormal situations happen during the procedures of discovery, configuration, storing, and reporting AM data. Abnormal situations occurring during discovery are beyond the scope of this Recommendation. Abnormal situation types related to configuration, storing and reporting AM data are defined in Table 2, with associated potential recovery actions. + +**Table 2 – Abnormal situations and potential recovery actions** + +| Abnormal situation name | Abnormal situation description | Potential recovery action | +|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message high-level error | A received AM message has high-level errors |

    TD-AMF or aggregation functions responds to the message sender with an error message, and ErrorCode defined by HighLevelErrorCode in Table 8 of [ITU-T H.741.2], e.g., not well-formed XML message (syntax error), or invalid XML message (not compliant with the schema).

    Upon receipt of an error message for push sequence messages, and pull sequence request messages; the message sender may rebuild and resend the message if different.

    After receipt of an error message for pull sequence response messages, if the message sender receives the same request it is not recommended to issue the same response.

    If high level errored messages from a TD-AMF persist following an error response, then aggregation functions may either ignore messages, and/or attempt to re-configure the TD-AMF to correct the problem or turn off AM.

    | +| Configuration message or configuration request response message error | A TD-AMF detects an error in a received configuration request response message or a configuration message (Note) |

    TD-AMF responds to aggregation functions with an error message with ErrorCode defined in ConfigPackageErrorInfo in Table 8 of [ITU-T H.741.2], e.g., element not supported, element information not available, element not permitted, event not supported.

    Upon receipt of the configuration error message, aggregation functions analyses the error message and may rebuild a subset or all of the configuration message and re-sends if different.

    After receipt of a configuration response error message, the aggregation functions are not recommended to issue the same configuration request response to a subsequently received configuration request message.

    | + +**Table 2 – Abnormal situations and potential recovery actions** + +| Abnormal situation name | Abnormal situation description | Potential recovery action | +|------------------------------------------|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | When TD-AMF receives an errored configuration package in either message, it may accept and act upon the non-erroneous part of the configuration package and indicates its behaviour in the error message. | +| Configuration request message error | Aggregation functions detect an error in a configuration request message |

    Aggregation functions may respond to the TD-AMF with an error message and Error code defined in ConfigRequestError in Table 8 of [ITU-T H.741.2]. Or if the aggregation functions can safely continue despite the error then aggregation functions may send a configuration request response message.

    Upon receipt of the error message, a TD-AMF may rebuild a subset or all of the message and re-send if different.

    If the error persists then aggregation functions may either ignore the configuration request messages from that TD-AMF, send an error message, or send a configuration request response message to turn off AM.

    | +| Measurement report request message error | A TD-AMF detects an error in a measurement report request message (Note) |

    In unicast, and if error reporting is requested in multicast, a TD-AMF responds to the aggregation functions with an error message and ErrorCode defined in ReportRequestError in Table 8 of [ITU-T H.741.2].

    If there are reports for non-errored requested MeasurementRequestIDs then the TD-AMF responds in a measurement report message.

    Upon receipt of the error message, aggregation functions may ignore the error message, or analyse the error message and may rebuild a subset and re-send, or rebuild all of the measurement report request message and re-send if different.

    | +| Measurement report message error | Aggregation functions detect an error in a measurement report message |

    Aggregation functions respond to the TD-AMF with an error message and ErrorCode defined in ReportError in Table 8 of [ITU-T H.741.2].

    Upon receipt of the error message, a TD-AMF may stop sending any subsequent reports, or keep sending reports except for the errored elements of individual measurement reports, or ignore the error messages and keep sending reports if different.

    If the error persists then aggregation functions may either ignore the measurement

    | + +**Table 2 – Abnormal situations and potential recovery actions** + +| Abnormal situation name | Abnormal situation description | Potential recovery action | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | |

    report message messages from that TD-AMF, or not send report request message to that TD-AMF, or send a configuration message to turn off AM. Additionally, for cases where configuration push is not supported, then following an error and a subsequent configuration request message the aggregation function may send a configuration request response to turn off AM.

    | +| Storage overrun |

    TD-AMF has no available storage space for a new measurement report to be stored

    |

    TD-AMF action depends upon StorageCongestionPolicy defined in Table 12 of [ITU-T H.741.2], and measurement trigger Priority defined in Table 11 of [ITU-T H.741.2].

    TD-AMF indicates the dropping of events and/or sample measurement in a measurement report message.

    Aggregation functions may take no action, or increase the frequency of measurement report request messages, or reconfigure the TD-AMF to either reduce the amount of data to be stored or to increase the frequency of reporting or both.

    | +| No measurement report message transport ack |

    TD-AMF does not receive a transport protocol acknowledgement from the aggregation functions following transmission of a measurement report message.

    |

    TD-AMF retries transmission of up to N duplicate measurement report messages. Where N is the RetransmitNumber defined in Table 12 of [ITU-T H.741.2].

    If no transport protocol acknowledgement is received after the N retries, then either:

    1. the measurement reports of the measurement report message may be deleted depending upon available storage, StorageCongestionPolicy defined in Table 12 of [ITU-T H.741.2] and measurement trigger Priority defined in Table 11 of [ITU-T H.741.2], or
    2. the measurement report message is kept for later retransmission.
    | +| Delayed push report missed |

    TD-AMF misses the randomly picked reporting time in delayed push mode or delayed push and pull mode.

    This situation is detected when the TD-AMF resumes operation following a period of terminal inactivity or loss of network connectivity to aggregation functions.

    |

    The TD-AMF picks another random time within the delivery window when it will push the stored audience measurement reports or waits for the next delivery window.

    | + +**Table 2 – Abnormal situations and potential recovery actions** + +| Abnormal situation name | Abnormal situation description | Potential recovery action | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Content filtering error | Content genre information is unavailable to support content filtering per configuration or permit. | A TD-AMF that makes measurements associated with the un-classified content shall send reports with the constraints of permission level 1, and shall not be batched with other reports for delivery. | +| TD-AMF sends inappropriate but valid AM messages | A – repetition of a valid AM message (following no error response)
    B – transmission of a valid AM message outside a valid message sequence
    C – transmission of a valid report message outside of valid configured reporting period. | Aggregation functions may either ignore messages, and/or attempt to re-configure the TD-AMF to correct the problem or turn off AM. | +| NOTE – Error message responses to unicast messages are mandatory when an error is detected. Error message responses to multicast messages are configurable. | | | + +When a capability is not supported by a TD-AMF but the configuration message contains directives regarding that capability then the TD-AMF ignores those directives. An error message may be sent. + +# Appendix I + +## Discovery of audience measurement services by terminal devices + +(This appendix does not form an integral part of this Recommendation.) + +There are several possible operational options of the aggregation functions which need to be understood by TD-AMFs. It is therefore necessary for the aggregation functions to declare the available and preferred options they support, to allow the terminal devices to check at the AM service discovery time if they are able to operate with them or not, and how best to operate. + +Table I.1 contains the elements to be included in [b-ITU-T H.770] for the discovery of AM services. + +The notation is used in the following table to facilitate the specification of the corresponding schema: + +- *Support*: 1 = mandatory (one instance), 0-1 = optional (max one instance), 0-\* = (optional and multiple instances possible), 1-\* = mandatory and multiple instances possible). +- *Type*: string, integer, float, etc. +- *Container*: elements are defined to group associated elements. + +An alternative representation is shown in Figure I.1 which illustrates the data structure. In case of discrepancy between the alternative representation and the table, the correct information is to be found in the table. + +**Table I.1 – Elements to be included in [b-ITU-T H.770] for the declaration of AM services** + +| Element | Description | Support/type | Notes or Value domain | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|----------------------------------------------------------------------------------------| +| PermissionOperation Modes | Specifies which end-user permission modes are available and preferred by aggregation functions | 1-*
    xs:string enumeration | Values: 'External', 'Internal', 'Hybrid' | +| Preferred | Attribute of PermissionOperationModes
    The end-user permission mode is preferred | 0-1
    xs:boolean
    Default: False | NOTE – When multiple modes are available, at least one mode is not marked as preferred | +| Addresses | Container specifying which addresses the TD-AMF uses | 1 | | +| Unicast | Element of Addresses
    Container specifying which addresses the TD-AMF uses to send messages which are part of message sequences including only unicast messages | 0-1 | | +| ConfigRequest Address | Element of Unicast
    Address to which all TD-AMF AM configuration request messages are to be sent | 0-1
    URL
    Note 1 | NOTE – For configuration pull or hybrid mode | + +**Table I.1 – Elements to be included in [b-ITU-T H.770] for the declaration of AM services** + +| Element | Description | Support/type | Notes or Value domain | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| ErrorAddress | Element of Unicast
    Address to which all TD-AMF configuration response error messages and configuration error messages are to be sent | 0-1
    URL
    Default:
    ConfigRequest Address | NOTE – For configuration pull, or hybrid, or push mode | +| Multicast | Element of Addresses
    Container specifying which addresses the TD-AMF uses to receive and send messages for message sequences including a multicast transport message | 0-1 | | +| MulticastHybrid Address | Element of Multicast
    This element contains the multicast address to listen to for the multicast configuration request response message | 0-1
    gt:ipAddressType
    Note 1 | NOTE – For configuration pull and multicast push (hybrid) mode | +| MulticastHybrid AddressPort | Attribute of MulticastHybridAddress
    This element contains the multicast port to listen to for the multicast configuration request response message | 1
    xs:unsignedShort | | +| MulticastHybrid SourceAddress | Element of MulticastHybridAddress
    This element contains the multicast source address for the multicast configuration request response message | 1
    gt:ipAddressType | | +| MulticastPush Address | Element of Multicast
    This element contains the multicast address to listen to for the multicast configuration message | 0-1
    gt:ipAddressType
    Note 1 | NOTE – For multicast configuration push mode | +| MulticastPush AddressPort | Attribute of MulticastPushAddress
    This element contains the multicast port to listen to for the multicast configuration message | 1
    xs:unsignedShort | | +| MulticastPush SourceAddress | Element of MulticastPushAddress
    This element contains the multicast source address for the multicast configuration message | 1
    gt:ipAddressType | | +| ErrorAddress | Element of Multicast
    Address to which all TD-AMF configuration response error messages and configuration error messages are to be sent | 0-1
    URL
    Default: No error reporting | NOTE – For error response following multicast configuration response or multicast configuration message | + +**Table I.1 – Elements to be included in [b-ITU-T H.770] for the declaration of AM services** + +| Element | Description | Support/type | Notes or Value domain | +|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AckAddress | Element of Multicast
    Address to which all TD-AMF configuration acknowledge messages are to be sent | 0-1
    URL
    Default:
    ErrorAddress | NOTES –
    – For acknowledgements response following multicast configuration messages
    – if neither AckAddress nor ErrorAddress is present then there will be no ACK responses | +| ConfigurationModes | Container specifying which configuration modes are available and preferred by aggregation functions, and for each mode the available and preferred transport protocols | 1 | | +| Push | Element of ConfigurationModes
    Configuration push mode is available | 0-1
    Note 2 | | +| Preferred | Attribute of Push
    Configuration push mode is preferred | 0-1
    xs:boolean
    Default: False | | +| TransportProtocols | Element of Push
    Indicates the transport protocol available | 1-*
    xs:string
    enumeration | Values are out of the scope of AM | +| Preferred | Attribute of TransportProtocols
    Indicates that the transport protocol indicated by the value is preferred | 0-1
    xs:boolean
    Default: False | | +| Pull | Element of ConfigurationModes
    Internal permission mode is available | 0-1
    Note 2 | | +| Preferred | Attribute of Pull
    Configuration push mode is preferred | 0-1
    xs:boolean
    Default: False | | +| TransportProtocols | Element of Pull
    Indicates the transport protocol available | 1-*
    xs:string
    enumeration | Values are out of the scope of AM | +| Preferred | Attribute of TransportProtocols
    Indicates that the transport protocol indicated by the value is preferred | 0-1
    xs:boolean
    Default: False | | +| Hybrid | Element of ConfigurationModes
    Configuration pull and push (hybrid) mode is available | 0-1
    Note 2 | | + +**Table I.1 – Elements to be included in [b-ITU-T H.770] for the declaration of AM services** + +| Element | Description | Support/type | Notes or Value domain | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Preferred | Attribute of Hybrid
    Configuration pull and push (hybrid) mode is preferred | 0-1
    xs:boolean
    Default: False | | +| TransportProtocols | Element of Hybrid
    Indicates the transport protocol available | 1-*
    xs:string
    enumeration | Values are out of the scope of AM | +| Preferred | Attribute of TransportProtocol
    Indicates that the transport protocol indicated by the value is preferred | 0-1
    xs:boolean
    Default: False | | +| MeasurementReport TransportProtocol | Container specifying which transport protocols for measurement reporting are available and preferred by aggregation functions | 1-*
    xs:string
    enumeration | Values are out of the scope of AM | +| Preferred | Attribute of MeasurementReportTransport Protocol
    The transport protocol is preferred | 0-1
    xs:boolean
    Default: False | | +| Cryptographic Protocol | Specifies which cryptographic protocols for reporting are available and preferred by aggregation functions | 1-*
    xs:string
    enumeration
    Note 3 | Values: 'TLS', 'TLS-SRP', 'OTP', 'HMAC'
    NOTE – 'TLS' is TLS 1.2 [IETF RFC 5246], 'TLS-SRP' is TLS-SRP [b-IETF RFC 5054], 'OTP' is [b-ITU-T X.1153], 'HMAC' is [b-FIPS PUB 198-1]. | +| Preferred | Attribute of CryptoReport
    This cryptographic protocol is preferred | 0-1
    xs:boolean
    Default: False | | +| Compression | Specifies which compression/decompression algorithms are available and preferred by aggregation functions for XML payloads | 0-*
    xs:string
    enumeration
    Default 'EXI' | Values: 'None', 'BiM', 'ZLIB', 'Infoset', or 'EXI'.
    See Note 4. | + +**Table I.1 – Elements to be included in [b-ITU-T H.770] for the declaration of AM services** + +| Element | Description | Support/type | Notes or Value domain | +|-----------|---------------------------------------------------------------------|-------------------------------------|-----------------------| +| Preferred | Attribute of Compression
    This compression algorithm is preferred | 0-1
    xs:boolean
    Default: False | | + +NOTE 1 – One or more of these must be present. +NOTE 2 – One or more of these must be present. +NOTE 3 – 'TLS' or 'TLS-SRP' is required to be present. +NOTE 4 – For BiM see [b-ISO/IEC 23001-1], for ZLIB (including GZIP) see [b-ETSI TS 102 472], for (Fast) Infoset see [b-ITU-T X.891], and for EXI see [b-W3C EXI]. +NOTE 5 – For xs: data types, see [b-W3C XMLSchemaP2]; for the URL data types, see [b-IETF RFC 3986]; for gt: data types, see [b-ATIS 0800026]. + +``` + +PermissionOperationModes (1-*) [Preferred (0-1)] +Addresses (1) +| Unicast (0-1) +| | ConfigRequestAddress (0-1) Note 1 +| | ErrorAddress (0-1) +| Multicast (0-1) +| | MulticastHybridAddress (0-1) [MulticastHybridAddressPort (1)] Note 1 +| | | MulticastHybridSourceAddress (1) +| | MulticastPushAddress (0-1) [MulticastPushAddressPort (1)] Note 1 +| | | MulticastPushSourceAddress (1) +| | ErrorAddress (0-1) +| | AckAddress (0-1) +ConfigurationModes (1) +| Push (0-1) [Preferred (0-1)] Note 2 +| | TransportProtocols (1-*) [Preferred (0-1)] +| Pull (0-1) [Preferred (0-1)] Note 2 +| | TransportProtocols (1-*) [Preferred (0-1)] +| Hybrid (0-1) [Preferred (0-1)] Note 2 +| | TransportProtocols (1-*) [Preferred (0-1)] +MeasurementReportTransportProtocol (1-*) [Preferred (0-1)] +CryptographicProtocol (1-*) [Preferred (0-1)] +Compression (0-*) [Preferred (0-1)] + +``` + +**Figure I.1 – Alternative representation of [b-ITU-T H.770] AM data structure** + +The XML schema that can be exchanged for audience measurement service discovery is in Appendix VIII. + +# Appendix II + +## Considerations on implementation + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides guidance for SPs on whether and how to deploy audience measurement. + +## II.1 Considerations on whether to implement AM + +Deploying audience measurement functions as part of the IPTV architecture provides benefits over traditional audience measurement which uses carefully selected panels to provide end-user information and media engagement measurements. + +Benefits of AM as part of IPTV architecture in comparison to traditional methods include: + +- 1) A larger audience sample – Many AM uses depend upon the statistical extrapolation of a sample: + - a) Given the fragmentation of digital destinations, the number of panel members that visit the long tail may be small or zero. A larger sample increases the statistical likelihood of meaningful measurement of more digital destinations. + - b) Local market characteristics are more likely to be detected. + - c) More stable measurement of small groups of interest. + - d) AM aggregated across service providers amplifies the benefit. +- 2) More detailed engagement measurements – Since AM has direct access to IPTV systems, it is able to measure IPTV engagement events, which are otherwise inaccessible, with greater time accuracy. +- 3) Opportunity for combination with other IPTV services – Since AM has direct access to IPTV systems, it may be used to enhance other systems; for example: + - a) Impact of service degradation – how many viewers leave channels because of a high error rate. + - b) Improve content/advert recommendation services – making recommendations and correlating subsequent choices and engagements. +- 4) Passive data collection – some traditional methods rely upon viewers who may suffer from fatigue or bias to record information. No active action by end users is needed using AM. + +AM limitations in comparison to ideal methods include: + +- 1) AM does not measure all end-user engagements on end-user devices which support IPTV services – End users engage substantially with non-IPTV services depending upon device type. + - a) TV – services provided via alternative input (e.g., game console content and games). + - b) Mobile device – phone, text, navigation, music, web, photography, etc. + - c) PC – web, chat, local programs/apps, etc. +- 2) AM is for IPTV "TV" only, it does not include over-the-air TV, analogue STBs, or uni-directional broadcasts, which additionally may be predominately used by particular audiences. +- 3) The AM audience sample may not be representative of the total viewing population which may be a problem for extrapolation. Optionally provided end-user information could be used to build a representative audience sample. + +- 4) AM TV viewing measurements may be misleading without presence detection to indicate how many viewers are currently engaged. +- 5) AM TV viewing measurements may not be associated with the identity and attributes of those viewers currently engaged. +- 6) TV measurements may be overstated when the TV is powered off and a STB is powered on. +- 7) The measurement analytics and offering/delivery mechanisms to stakeholders are not standardized. +- 8) Integrated measurement of the audience and the quality of experience is not provided; the outputs of these separate systems can be manually combined. + +In comparison to emerging technology, multi-function mobile devices used as remote controls are typically more powerful modern devices than some TV STBs, and so may have advantages as a measurement point. + +## **II.2 Considerations for end-user permission method selection** + +There are three recommended methods to support the requesting, receipt, and storing of end-user responses and to ensure that measurement takes place with end-user permission, summarized in clauses 9.2.1, 9.2.2 and 9.2.3. The following are considerations of the situations for which each method is best suited. + +#### **II.2.1 External permission mode** + +In this method, the request and receipt of end-user permission occurs outside of the AM system, such as in the situation illustrated in Figure II.1. + +Conditions that may lead to this method being selected include: + +- 1) The deployment of a broad customer communications system, which lends itself to integration of end-user permission functions such as directly asking for an end-user's permission, storing responses, reporting on end-user permission status, and aggregating end users into segments based upon permission status. +- 2) A preference to communicate with end users through either a customer-care channel, or a non-resident downloadable application. +- 3) A desire to de-couple the permission system software from the audience measurement software. This may be important if frequent revisions or multiple versions (such as language or legislative zones) are expected. + +![Diagram illustrating the external permission mode for H.IPTV-AM. Stakeholders 1 and 2 send orders and reports to a Measurements manager. The manager sends aggregated reports to Aggregation functions. The Aggregation functions send measurement requests to two audience segments (A and B) within the H.IPTV-AM scope. The audience segments send measurement reports back to the Aggregation functions. The Aggregation functions also send available measurements to an SP customer communications system. End users send end-user permits to the SP customer communications system. The SP customer communications system includes a care channel with user permission functions.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +``` + +graph LR + subgraph H_IPTV_AM_scope [H.IPTV-AM scope] + direction TB + subgraph Audience_A [Permission level "A" audience segment] + AMF_A[Audience measurement function] + end + subgraph Audience_B [Permission level "B" audience segment] + AMF_B[Audience measurement function] + end + end + + Stakeholder1[Stakeholder 1] -- "Orders (order details, directives)" --> MM[Measurements manager] + Stakeholder2[Stakeholder 2] -- "Reports" --> MM + MM -- "Orders (order details, directives) and management" --> AF[Aggregation functions] + AF -- "Aggregated reports" --> MM + AF -- "Measurement requests" --> AMF_A + AF -- "Measurement requests" --> AMF_B + AMF_A -- "Measurement reports" --> AF + AMF_B -- "Measurement reports" --> AF + AF -- "Available measurements (audience segments, measurement types, measurable media, etc.)" --> SP[SP customer communications system including care channel with user permission functions] + EU[End users] -- "End-user permits" --> SP + +``` + +Diagram illustrating the external permission mode for H.IPTV-AM. Stakeholders 1 and 2 send orders and reports to a Measurements manager. The manager sends aggregated reports to Aggregation functions. The Aggregation functions send measurement requests to two audience segments (A and B) within the H.IPTV-AM scope. The audience segments send measurement reports back to the Aggregation functions. The Aggregation functions also send available measurements to an SP customer communications system. End users send end-user permits to the SP customer communications system. The SP customer communications system includes a care channel with user permission functions. + +**Figure II.1 – Example of external permission mode** + +In external permission mode, TD-AMFs do not know the details of permits. Consider that all TD-AMFs might have the same permission level, or that subsets of TD-AMFs might have different permission levels. There are four multicast sub-addressing mechanisms: threshold ranges, device type, device address and end user info. + +- Threshold ranges mechanism – is independent of the permission level; a configuration sent to a random set of TD-AMFs must make an assumption about the permission levels assigned to the TD-AMFs. Consider that all have a single permission level (either 1, 2 or 3) – then a single configuration can be sent according to that permission level. Consider a population of TD-AMFs having different permission levels (1 and 2, 2 and 3, 1 and 3, or 1 and 2 and 3) – then a single configuration appropriate to the lowest permission level present, e.g., permission level 1, would be sent. If the population of TD-AMFs includes permission level 0, then the permission level 0 factor is ignored. For example, in the case of a population having different permission levels of 0, 1, 2 and 3, then a single configuration appropriate to permission level 1 would be sent. +- Device Type mechanism – the considerations are similar as for the threshold ranges mechanism. +- Device addresses mechanism – addresses of the target TD-AMF subsets may be determined by awareness of permission levels 1, 2 or 3. Different subsets as defined by lists of addresses may be sent different appropriate configurations. The formation of these subsets may be implemented outside of AM. +- End-user info mechanism – is dependent upon permission levels 2 or 3. Since the only sub-addressing mechanism which may be permission level aware is device addresses, end user info sub-addressing can only be used in combination with the device addresses mechanism. + +#### II.2.2 Internal permission mode + +With this method, the request and receipt of end-user permission occurs within the AM system, such as in the situation illustrated in Figure II.2. + +Conditions that may lead to this method being selected include: + +- 1) The desire that deployment of a permission system be closely coupled to the deployment of the audience measurement system. + +- 2) A preference to communicate with end users through a resident application which is an integral part of the audience measurement software. +- 3) An alternative real-time audience messaging system is not available. + +![Figure II.2 – Example of internal permission mode. This block diagram illustrates the flow of data and permissions within an audience measurement system. On the left, Stakeholder 1 and Stakeholder 2 send 'Orders (order details, directives)' to a 'Measurements manager'. The manager sends 'Reports' back to Stakeholder 2 and 'Orders (order details, directives) and management' and 'Aggregated reports' to 'Aggregation functions'. Below the manager, 'Other SP systems' provide 'Available measurements (audience segments, measurement types, measurable media, etc.)'. The 'Aggregation functions' send 'Measurement requests' to two end-user measurement functions inside the 'HIPTV-AM scope': 'End-user ](ae0a735d106290c594b0bafb1f5e72e7_img.jpg) + +Figure II.2 – Example of internal permission mode. This block diagram illustrates the flow of data and permissions within an audience measurement system. On the left, Stakeholder 1 and Stakeholder 2 send 'Orders (order details, directives)' to a 'Measurements manager'. The manager sends 'Reports' back to Stakeholder 2 and 'Orders (order details, directives) and management' and 'Aggregated reports' to 'Aggregation functions'. Below the manager, 'Other SP systems' provide 'Available measurements (audience segments, measurement types, measurable media, etc.)'. The 'Aggregation functions' send 'Measurement requests' to two end-user measurement functions inside the 'HIPTV-AM scope': 'End-user + +H.741.1(12)\_FII.2 + +**Figure II.2 – Example of internal permission mode** + +In the above figure, an example flow of end-user permits and effective permits are shown by red and orange arrows. Multiple end-user permits may be input to a TD-AMF which combines them into an effective permit for filtering the configuration package instructions. The aggregation functions may use the effective permit itself, and may send the effective permit to other TD-AMFs of the end user (for federation of permissions) that the end user has specified. + +Using internal permission mode, visibility into the audience segmented by permission levels may be obtained by the Measurements Manager from the AM system. + +#### II.2.3 Hybrid permission mode + +In this mode, illustrated in Figure II.3, the request and receipt of end-user permissions occurs within the SP system. The TD-AMF requests the permit from the SP system, and may use the permit for local filtering, or send it to the aggregation functions to filter configuration packages. + +Conditions that may lead to this mode being selected include: + +- 1) The deployment of a broad customer communications system, which lends itself to integration of end-user permission functions such as directly asking for an end-user's permission, and storing responses (permits). +- 2) A preference to communicate with end users through an SP customer-care channel, rather than through AM. +- 3) The wish for the AM system to be aware of end-user permissions. + +![Figure II.3 – Example of hybrid permission mode. The diagram shows the flow of measurement requests and reports within the H.IPTV-AM scope, involving aggregation functions, end-user audience measurement functions for User device 1 and User device 2, and other IPTV functions. It also shows the flow of user permits from the SP customer communications system to the aggregation functions.](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +The diagram illustrates the hybrid permission mode within the H.IPTV-AM scope. It features two main components: 'Aggregation functions' and 'End-user audience measurement function' (for User device 1 and User device 2). 'Measurement requests' are sent from the 'Aggregation functions' to the 'End-user audience measurement function'. 'Measurement reports' are sent from the 'End-user audience measurement function' to the 'Aggregation functions'. 'Other IPTV functions' are connected to the 'End-user audience measurement function'. 'User permits' are sent from the 'SP customer communications system including care channel with user permission functions' to the 'Aggregation functions'. 'Effective permit' is shown as a red arrow from the 'SP customer communications system' to the 'Aggregation functions'. The diagram is labeled H.741.1(12)\_FII.3. + +Figure II.3 – Example of hybrid permission mode. The diagram shows the flow of measurement requests and reports within the H.IPTV-AM scope, involving aggregation functions, end-user audience measurement functions for User device 1 and User device 2, and other IPTV functions. It also shows the flow of user permits from the SP customer communications system to the aggregation functions. + +**Figure II.3 – Example of hybrid permission mode** + +In the above figure, an example flow of end-user permits and effective permits is shown by red and orange arrows. Multiple end-user permits may be input to a SP which combines them into an effective permit for use in filtering the configuration package instructions. + +Using hybrid permission mode, the end user could specify which devices the end-user permit(s) covers (for federation of permissions) and the SP could forward the effective permit to all specified devices (which would each forward the effective permit to the aggregation functions). + +#### II.2.4 Example method of setting multiple permits in a household + +The method of setting and managing permits is out of the scope of this Recommendation. However, Figure II.4 gives an example to show how end-user permits may be used with AM. + +In this example, the subscriber-administrator allocates rights to household members. The mother: + +- creates an identity for the father, who may set his permissions without further access by the mother; +- creates an identity for Son1, who may set or reduce his permissions only with his mother's approval; +- creates identities for Son2 and Son3, and sets their permissions. + +![Diagram illustrating the method of setting multiple permits in a household. At the top, 'Household audience members' include Mother (Adult-subscriber), Father (Adult), Son1 (Child age 15), Son2 (Child age 10), and Son3 (Child age 5). Arrows show identity creation: Mother and Father create identities with no admin access; Son1, Son2, and Son3 create identities with admin approval and permission setting. Below, 'Sets' and 'Approves' relationships are shown: Mother sets 'AM permit #1'; Father sets 'AM permit #2'; Son1 sets 'AM permit #3' (with a note: 'Sets with approval required, reduces without approval'); Son2 sets 'AM permit #4'; Son3 sets 'AM permit #5'. Blue arrows show approval: Father approves Son1's permit; Mother approves Son2's and Son3's permits. Further, 'Sets' relationships lead to a combined 'Son2 and Son3 permissions (if same) AM permit #6'. All individual permits and the combined permit lead to 'Identification of users present', which then leads to 'Effective permit', which finally leads to 'AM'. A small code 'H.741.1(12)_FI1.4' is at the bottom right.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +Diagram illustrating the method of setting multiple permits in a household. At the top, 'Household audience members' include Mother (Adult-subscriber), Father (Adult), Son1 (Child age 15), Son2 (Child age 10), and Son3 (Child age 5). Arrows show identity creation: Mother and Father create identities with no admin access; Son1, Son2, and Son3 create identities with admin approval and permission setting. Below, 'Sets' and 'Approves' relationships are shown: Mother sets 'AM permit #1'; Father sets 'AM permit #2'; Son1 sets 'AM permit #3' (with a note: 'Sets with approval required, reduces without approval'); Son2 sets 'AM permit #4'; Son3 sets 'AM permit #5'. Blue arrows show approval: Father approves Son1's permit; Mother approves Son2's and Son3's permits. Further, 'Sets' relationships lead to a combined 'Son2 and Son3 permissions (if same) AM permit #6'. All individual permits and the combined permit lead to 'Identification of users present', which then leads to 'Effective permit', which finally leads to 'AM'. A small code 'H.741.1(12)\_FI1.4' is at the bottom right. + +**Figure II.4 – Example method of setting multiple permits in a household** + +The permit input method may occur via an IPTV device end-user interface driven either: + +- internally to AM per clause II.2.2 (internal permission mode), or +- externally of AM per clause II.2.1 (external permission mode), or II.2.3 (hybrid permission mode). + +Rules to determine the effective permit include: + +- 1) If household members are not distinguishable, then only a single household permit is needed. +- 2) If a single household member is identified as being present, then the associated permit would be used. +- 3) Where multiple end users are believed to be engaging with content, the effective permit is the most restrictive combination of permits of identified end users present. + +Only one effective permit is used at any time. + +### II.3 Considerations on using content filtering in configuration packages + +Content filtering may be supported via configuration and user permit mechanisms. + +The configuration of content filtering as set by the AM provider (see clause 7.1.2.2), could be driven by either the AM provider or the end user (in external permission mode). In internal or hybrid modes, a permit may specify content filtering. + +Conditions that may lead to configuration of content filtering being used by an AM provider include: + +- 1) Content genres are available in TD-AMFs to support content filtering. +- 2) The SP believes that end users will be more likely to grant higher permission levels if certain sensitive genres are excluded from measurement. + +- 3) Support of external permission mode which incorporates end user permissions regarding content restrictions. +- 4) Industry guidelines and/or regulations. + +### **II.4 Considerations on using different measurement triggers** + +Audience measurement supports three types of measurement triggers, the following clauses discuss considerations to help decide when to use each type. + +#### **II.4.1 Considerations on using time-based sampling of elements** + +Audience measurement provides a rich set of event-driven measurements, which are the recommended measurement mechanism. However, there are situations under which end-user behaviours do not trigger desired events or reports of those events. Time-based sampling of elements helps capture those end-user behaviours and reports. If these situations occur frequently and/or the missed event reports have a high value, then it is recommended that time-based sampling be configured. + +Time based sampling provides "checkpointing" capabilities for events that would have been measured and reported after event-driven measurement and reporting stopped. For example, if an end user watched a programme then powered down the device, and no channel change event is measured, then sampling informs AM of the programme watched. + +The reporting of time-based sampling can be optimized when a new sample value is found to be effectively the same as a previous sample. Per the `NothingNewReportMode` element, the report of the new sample value can be ignored; an empty report can be sent, or a complete report may be sent. By selecting the option of reporting using an empty report, TD-AMFs will send small periodic messages which can be used to indicate a TD-AMF's health. TD-AMFs can be configured such that a single type of time-based sample value sends an empty report, thus avoiding duplicate health indicators from a single TD-AMF. + +Conditions that may lead to time-driven sampling being selected include: + +- 1) When measured programmes are usually the last programme that is watched prior to device power down. +- 2) When the additional resource overhead of time-driven sampling costs less than the value of missed event based audience measurements. +- 3) When the programmes are of longer duration and need less frequent sampling. +- 4) When the programmes are scheduled such that samples provide strong inferences (e.g., five minutes before the hour for hourly scheduled programmes). + +Multiple measurement requests can be configured to cause the generation of duplicate measurement reports. For example, two measurement requests can both be configured to measure linear and common events, for both the same channel and time. It is recommended that the TD-AMF recognizes duplicate measurement reports awaiting transmission and discards all but one. + +#### **II.4.2 Consideration on using "sample" versus "service start" measurements** + +While event measurements are the recommended main method to measure behaviours, AM's two sampling mechanisms are useful for checkpointing, or for measuring slowly changing information. Consider that the following information from [ITU-T H.741.2], typically changes at different rates: + +- UserID is anticipated to change frequently as the viewing end users change. +- UserIDMethod, and UserIDConfidence elements are anticipated to change slowly since they are associated with the capabilities of the system. + +- Some hardware information such as TVInformation may change slower than others MobileDeviceInformation. +- Some end-user information never changes, such as Birthday and BirthLocation. + +Service start measurements are better suited to collect slowly changing information, since this method does not use device resources to measure elements frequently then discard them if they have not changed or use network resources to send a report during consumption of every service. If it is desired to measure elements each time a service starts during a day, or once every number of days, then service-start measurements are recommended. + +### II.5 Considerations for using AM message acknowledgements + +In a message passing system it is sometimes useful to monitor the health of the system and to enable problem debug using acknowledgments. Some of the supported transport protocols may support acknowledgements that the IP packets holding AM messages have been delivered. These transport acknowledgements do not indicate if the contents of the message were understood. Therefore AM includes an optional, flexible and low overhead acknowledgement request mechanism (response qualifier) for the multicast configuration message. Together with the addressability of AM to sets of devices such as STBs, acknowledgments may be selectively configured on a set of devices which act as device samples for the greater population. + +Conditions that may lead to the use of acknowledgements being requested include: + +- 1) Pre-deployment testing to help gain familiarity with system operations. +- 2) Initial limited deployments to help gain confidence in system operations. +- 3) On-going monitoring of system operations using a subset of TD-AMFs. +- 4) Trouble-shooting system operations. + +When an acknowledge (without requesting an error report) has been requested and none is received, the following causes may be considered: + +- Configuration message was configured incorrectly, not transmitted, or not received by the targeted TD-AMFs. +- The targeted TD-AMF(s) was/were offline, software was not installed/working/compatible, was unable to transmit ACK, or was not received by the aggregation functions. + +Actions that are recommended for consideration include: + +- Re-send same multicast configuration message assuming the problem was temporary. +- Re-send multicast configuration message with an error report request to obtain more information. +- Narrow the subset of TD-AMFs to pin-point and better understand the problem. +- Extend the subset of TD-AMFs assuming it was too small. +- Analyse configuration message for errors; if found, then fix and resend. + +### II.6 Considerations for configuration mode selection + +There are three modes to send configuration packages to TD-AMFs: + +- **Configuration Pull Mode:** TD-AMFs initiate the transfer request for a configuration package from the aggregation functions using the configuration package request message, which may result in a configuration package request response message. +- **Configuration Push Mode:** Aggregation functions initiate and send configuration packages using the configuration message. +- **Configuration Hybrid Mode:** A combination of the pull and push modes. + +For configuration pull mode and for configuration pull and push (hybrid) mode, a configuration package check delay is defined, which triggers subsequent checks for availability of a new configuration package. An initial multicast configuration request response message (e.g., when AM is first turned on) may synchronize subsequent checking by many TD-AMFs. Therefore, it is recommended that the value of the configuration package check delay be configured to vary across TD-AMFs if the multicast configuration request response message is used. + +The following are considerations of the situations for which each mode is best suited. + +#### **II.6.1 Configuration Pull Mode** + +In this mode, TD-AMFs individually send requests to the aggregation functions to check and conditionally receive a new configuration package. + +Conditions that may lead to this method being selected include: + +- 1) Sufficient upstream bandwidth is available for configuration request messages. +- 2) Information regarding TD-AMFs currently online is not otherwise available to AM (it is provided by the configuration request messages). +- 3) A substantial number of TD-AMFs are periodically turned off or disconnected from the network (configuration push messages could be missed). +- 4) A substantial number of TD-AMFs are mobile and the configuration packages are location dependent. + +#### **II.6.2 Configuration Push Mode** + +In this mode, aggregation functions send unicast or multicast configuration package message(s) to TD-AMFs. Aggregation functions may obtain information regarding TD-AMFs that are online from other IPTV services, including but not limited to: + +- TD-AMF unicast reachability information. +- TD-AMF type and MAC addresses for multicast sub-addressing. +- TD-AMF capabilities. + +Configuration push mode provides aggregation functions with autonomy, independent of the receipt of "pull requests" from TD-AMFs. The use cases where aggregation functions are recommended to immediately send a new push configuration include: + +- a) A revised effective permit has just been received in external permission mode. +- b) An unplanned immediate change in a stakeholder AM order has been received. +- c) Potential recovery actions to abnormal situations ("Message high level error", "Configuration message or configuration request response message error", "Configuration request message error", "Storage overrun", and "TD-AMF sends inappropriate but valid AM messages"). + +Conditions that may lead to unicast configuration push being selected include: + +- 1) Minimization of AM configuration pull sequence messages is important. +- 2) A multicast protocol is not supported. +- 3) Information regarding TD-AMFs currently online is available. +- 4) Continuous tracking of configuration error and/or measurement reports is available to modify configuration messages e.g., contents and timing of configuration messages. +- 5) Minimization of TD-AMF multicast sub-addressing processing (especially for handling abnormal situations) by non-target TD-AMFs. + +The advantage of using multicast push mode is that a single message can be sent to configure many TD-AMFs. By using target qualification elements, by MAC address, target device type, and/or percentage of devices, configuration of multiple sets can be achieved by sending few different configuration messages. In addition, multiple multicast transport delivery protocols can be used. Together these capabilities form the basic tools for multicast configuration push mode. + +In practice the number of TD-AMFs responding to any configuration could be tracked and used as feedback to modify the frequency and time of configuration messages. + +Conditions that may lead to this method being selected include: + +- 1) Minimization of AM configuration pull sequence messages is important. +- 2) A multicast protocol is supported. +- 3) Information regarding TD-AMFs currently online is available. +- 4) Continuous tracking of measurement reports is available to modify configuration messages. + +#### **II.6.3 Configuration Hybrid Mode** + +In this mode, TD-AMFs may individually send requests to the aggregation functions to check and conditionally receive a new configuration package. Subsequently aggregation functions may send unicast or multicast configuration package message(s) to TD-AMFs. + +Conditions that may lead to this method being selected include: + +- 1) Sufficient upstream bandwidth is available for a reduced frequency of configuration request messages (limited pull). +- 2) A mixture of some or all of the conditions of clauses II.6.1 and II.6.2 occur. + +### **II.7 Considerations regarding methods of obtaining end-user permits** + +Several methods may be available for AM and/or IPTV service providers to obtain end-user permits. Some methods include: + +- An interactive IPTV customer care channel. +- IPTV audience measurement using internal permission mode. +- Web customer care portal. + +To help select and implement a method, the following three processes are recommended for consideration: + +- 1) Permission requests to an end user to measure, collect and use end-user information may be triggered by the following events: + - a) Initial deployment of services to an end user. + - b) Addition of an end-user measurement function to an existing device associated with services. + - c) Addition of a new device which supports end-user measurement function associated with services. + - d) Before applying any material change to data collection and use policy that is less restrictive to data collected prior to such material change. + - e) Elapse of prior duration-limited permission granted by an end user, which is recommended to be no more than one year. + - f) Request by end user to change permissions. +- 2) The AM service may optionally support an end-user's request to purge prior AM information. + +- 3) To select the same service method to obtain end-user permits as the IPTV service, it is recommended that either an IPTV customer care channel or IPTV AM be selected. +- 4) It is recommended that the language and format of the request be selected to match the end user and device. + +### **II.8 Considerations for using multicast sub-addressing mechanisms** + +When using multicast messages, AM provides four mechanisms which enable addressing subsets of TD-AMFs. A low network traffic method is thereby provided to uniquely configure large subsets of TD-AMFs. + +#### **Threshold ranges** + +The first mechanism is the use of threshold ranges. To efficiently create and control subsets of many TD-AMFs, each TD-AMF generates a random number between 0-10000 at boot-up, which it compares with configurable threshold ranges in the multicast message. Only if the TD-AMF random number matches the range does the TD-AMF accept the message. For example, only three multicast (push) messages are needed to configure three subsets of devices: + +- 1) "normal responders (no error or acknowledgements)" = threshold range 0-4090 +- 2) "positive acknowledge sentries" = threshold range 4100-4190 +- 3) "error responders" = threshold range 4200-4290. + +Here approximately 40% of the total TD-AMF population would not send error or acknowledgement messages. Approximately 1% of the total TD-AMF population would generate error messages following error detection. Approximately 1% of the total TD-AMF population would generate acknowledge messages to provide a health indication. + +In order to limit the network resources used, the total percentage of responding AMFs can optionally be controlled as the total number of TD-AMFs increases. In the above example, the number of "normal responders" could be reduced as the total number of TD-AMFs increases in order to avoid increases in AM network traffic. + +Conditions that may lead to multicast threshold ranges being used include: + +- 1) Network-level multicast or application-level multicast (e.g., XMPP) is supported. +- 2) Network resources need to be controlled as the number of TD-AMFs increase. +- 3) Subsets of TD-AMFs need to have different configurations. + +#### **List of device addresses** + +The second address qualifier mechanism is to specify the list of device addresses (hash of MAC address) for the multicast message, in a binary header. + +Conditions that may lead to the list of device addresses being used include: + +- 1) Network-level multicast or application-level multicast is supported. +- 2) Subsets of TD-AMFs need to have different configurations. +- 3) Subsets of reports from TD-AMFs are desired. + +The threshold ranges and device address list mechanisms may be used in combination for the "multicast configuration message" and/or "multicast measurement report request message". + +This multicast subset addressing mechanism for the device address list may be used in the "multicast configuration request response message". It may be used as a single multicast message to respond to many TD-AMFs simultaneously requesting configuration using unicast, for example, in the case following recovery from a local geographic event such as a power or network outage. + +Sets of TD-AMFs requiring different configuration could distinguish multicast responses by examination of the terminal device target list. TD-AMFs would need to examine all AM multicasts for a certain time to determine if their MAC address is in the list of each response. + +#### Device type + +The third address qualifier mechanism is to specify which type of device the multicast message is for: TV, PC, tablet, mobile or other. This third mechanism is supported in the "multicast configuration message". It may be used in combination with the other three mechanisms. + +Conditions that may lead to multicast subset addressing by type of device being used include: + +- 1) Network level multicast or application-level multicast is supported. +- 2) Subsets of TD-AMFs types need to have different configurations, purely by type, e.g., PC and Tablet. +- 3) A subset of TD-AMFs types needs to have a different configuration, combining type and percentage using threshold ranges, e.g., 50% of STBs. +- 4) A subset of TD-AMFs types needs to have different configurations, combining type and specific MAC address when the type of TD-AMF at a specific MAC address is not known. + +#### End-user information + +The fourth address qualifier mechanism is to specify target values of provider-defined end-user elements, which match those associated with a TD-AMF in order for the configuration to be further processed by that TD-AMF. This mechanism supports whether to ignore the matching rule in the case where the specified end-user data is not available. This fourth mechanism is supported in the "multicast configuration message" and "multicast configuration request response message". It may be used in combination with the other three mechanisms. + +For example, as in Table II.1, a configuration package specifying an end-user info element type "occupation" and associated element value "doctor" will only be processed by the set of TD-AMFs having an end-user info element type of "occupation" and associated element value of "doctor". The TD-AMF will also process the configuration package if it specifies "ignore if unavailable" and the TD-AMF end-user info element type "occupation" is unavailable. + +**Table II.1 – Example of using end-user information for sub-addressing of TD-AMFs** + +| Target end-user info element type | Target end-user info element value | Ignore if unavailable | TD-AMF end-user info element type | TD-AMF end-user info element value | TD-AMF action | +|-----------------------------------|------------------------------------|-----------------------|-----------------------------------|------------------------------------|-----------------------| +| "occupation" | "doctor" | False | "occupation" | "doctor" | Process config | +| "occupation" | "doctor" | True | "occupation" | "doctor" | Process config | +| "occupation" | "doctor" | False | "occupation" | Not "doctor" | Do not process config | +| "occupation" | "doctor" | True | "occupation" | Not "doctor" | Do not process config | +| "occupation" | "doctor" | False | "occupation" not available | – | Do not process config | +| "occupation" | "doctor" | True | "occupation" not available | – | Process config | + +Multiple end-user info elements may be specified within one configuration package. For example, a configuration package can require "occupation" is "doctor" and that "income" is "over 200 000 Euros", in which case they must both be matched for a TD-AMF to process that configuration package. This fourth mechanism may be used with the above three mechanisms, in + +which case, the qualifiers of all used mechanisms must match for the configuration to be processed by a TD-AMF. + +Conditions that may lead to the use of end-user info sub-addressing include: + +- 1) Network-level multicast or application-level multicast is supported. +- 2) End-user permission levels 2 or 3 have been granted for the target TD-AMFs. Where the permission level required depends upon whether the desired match is against generic or controlled end-user information. +- 3) End-user info elements suitable for targeting have been requested by AM stakeholders. +- 4) End users have provided the data for elements suitable for targeting. +- 5) Multiple different configurations for subsets of TD-AMFs are desired. + +The use of the "Ignore if available" option is recommended to be considered when enrichment of a subset population including end users having a particular info element value (trait) is desired. It maximizes the number of TD-AMFs that accept a configuration package having a specific trait even if not made available, with the side effect of including some end users that do not have that trait. + +### **II.9 Considerations for requesting error message responses to multicast messages** + +Error message responses to unicast messages are mandatory when an error is detected; however error message responses to multicast messages are configurable. In particular, a response qualifier which can request error message responses is supported in three messages: + +- Multicast configuration request response message. +- Multicast configuration message. +- Multicast measurement report request message. + +Conditions that may lead to use of error message responses being requested include: + +- 1) Pre-deployment testing to help gain familiarity with system operations. +- 2) Initial limited deployments to help gain confidence in system operations. +- 3) On-going monitoring of system operations using subsets of TD-AMFs. +- 4) Trouble-shooting system operations. + +Error messages (see [ITU-T H.741.2] Table 8) indicate the source AM message, indication of whether the errored message was partially accepted or rejected, error codes and related information. Error types indicated include: + +- Multicast high level errors – not well formed XML message (syntax error), invalid XML message, unrecognized message (not compliant with the schema), or sourced major version is not equal to the receiver's version. +- Multicast configuration errors – element not supported, element information not available, element not permitted, and event not supported. Related information includes errored element and event name. +- Multicast report request errors – Requested measurement request ID which was not previously configured. Related information includes the errored element and measurement request ID. + +Actions that are recommended to be considered include those in Table 2 and the following multicast-specific actions: + +- Narrow the subset of TD-AMFs by the use of multicast sub-addressing, to pin-point and better understand the problem. + +### II.10 Considerations for delivery mode selection + +There are four modes that may be used to deliver measurement reports to aggregation functions. These may be used alone or in combination specified by configuration of measurement requests. + +- 1) **Immediate Push Mode:** When a measurement is made, it is optionally grouped with a number of other measurements within a period of time before being sent in a measurement report package message. +- 2) **Delayed Push Mode:** Measurements are stored until a TD-AMF randomly picked time during the configured delivery window is reached. At that time the TD-AMF groups measurement reports and sends them in a measurement report package message. +- 3) **Pull Mode:** Measurements are stored until a measurement report request message is received from the aggregation functions. This message causes selected measurements to be grouped before being sent in a measurement report package message. A configured policy indicates what the TD-AMF does in case of storage congestion. +- 4) **Delayed Push and Pull Mode:** Measurements are stored until either a report request message is received from the aggregation function, or a TD-AMF randomly picked time during the configured delivery window is reached. Whichever trigger is sooner causes measurements to be grouped before being sent in a measurement report package message. + +The following are considerations of the situations for which each mode is best suited. + +#### II.10.1 Immediate Push Mode + +Conditions that may lead to this mode being selected include: + +- 1) The audience measurement data is of higher value when made available to other applications or stakeholders in near real-time. +- 2) Upstream network resources to aggregation functions are available during an AM measurement period. +- 3) Expected TD-AMF available storage in comparison to the volume of expected measurements is limited, and would likely result in loss of measurements if not reported immediately. + +For example, measurements acquired during non-peak network usage periods might be reported immediately. + +#### II.10.2 Delayed Push Mode + +Conditions that may lead to this mode being selected include: + +- 1) The audience measurement data remains valuable when made available to other applications or stakeholders within a delayed time period. +- 2) Upstream network resources to aggregation functions are expected to be available during a known period after measurement acquisition starts. +- 3) Expected TD-AMF available storage in comparison to the volume of expected measurements until reporting is sufficient, or loss of lower-priority measurements due to storage congestion is acceptable. + +For example, measurements acquired during peak network usage periods might be reported during non-peak periods. + +#### II.10.3 Pull Mode + +Conditions that may lead to this mode being selected include: + +- 1) The audience measurement data remains of value when made available to other applications or stakeholders within a delayed time period, but sooner is more valuable. + +- 2) The availability of upstream network resources to aggregation functions may not be predictable. Upstream and some downstream network availability may be opportunely used to retrieve reports. +- 3) Expected TD-AMF available storage in comparison to the volume of expected measurements until reporting is sufficient, or loss of lower-priority measurements due to storage congestion is acceptable. + +For example, measurements acquired during peak network usage periods might be collected as soon as sufficient network availability is detected. + +#### **II.10.4 Delayed Push and Pull Mode** + +Conditions that may lead to this mode being selected include: + +- 1) The audience measurement data remains valuable when made available to other applications or stakeholders within a delayed time period; however sooner is more valuable. +- 2) The availability of upstream network resources to aggregation functions may not be predictable. Upstream and some downstream network availability may be opportunely used to retrieve reports. If an opportunity does not occur sufficiently in advance, then downstream network consumption can be avoided by waiting for the delayed push. +- 3) Sufficient available storage is anticipated for the TD-AMF as compared to the volume of measurements expected until reporting; or the loss of lower-priority measurements due to storage congestion is acceptable. +- 4) It is desirable that a single delivery mode be configured, but certain triggers will cause aggregation functions to collect audience measurement data sooner than scheduled. Examples of pull mode triggers include: + - a) day of week + - b) content programming event + - c) audience measurement data previously collected by aggregation functions. + +For example, transmission of reports may be scheduled for 0200 hours, but on election evening the measurement reports are collected earlier. + +#### **II.10.5 Mixed delivery modes** + +To process a complete service history, all events and samples prior to and including service stop (or subsequent service start) must be received by the aggregation functions. + +The fastest way to obtain a complete service history is to report all events and samples using immediate delivery mode. However, if it is desired to use mixed delivery in order to obtain a complete service history as soon as possible, then it is recommended that service start and service stop be delivered using immediate delivery mode, and that other events and samples be delivered using pull mode or delayed push and pull mode. When aggregation functions receive a service stop (or subsequent service start) event report from a TD-AMF, it is recommended that they pull all reports from that TD-AMF. + +### **II.11 Considerations on using end-user information to filter measurement requests** + +End user provided information associated with a TD-AMF may be used to filter out specific measurement requests while others are to be processed. The advantage of using measurement request filtering is to be able to deploy fewer configuration packages that are suitable for many TD-AMFs. For example, if in a set of TD-AMFs, an end-user info element type is "occupation" and the associated element value is "doctor", then measurement requests which are associated to "occupation" and "doctor" will only be processed by that set of TD-AMFs. If the "occupation" is not "doctor", then the specified measurement requests are ignored. A single configuration package + +can therefore be extended to qualify different measurement requests by several "occupations" or other end-user info types such as "income", "number of children", etc. Multiple end-user info qualifiers e.g., "doctor" and "over 200 000 Euros" may be associated to measurement requests, in which case they must both be matched for a TD-AMF to process the associated measurement request(s). The configuration also specifies whether to ignore the matching rule in the case where the specified end user data is not available. + +Conditions that may lead to the use of end-user information for filtering measurement requests include: + +- 1) Multiple different configurations are desired. +- 2) Fewer configuration packages are desired. +- 3) End-user permission levels 2 or 3 have been granted for the target TD-AMFs. Where the permission level required depends upon whether the desired match is against generic or controlled information. +- 4) Elements suitable for targeting have been requested by AM stakeholders. +- 5) Elements suitable for targeting have been requested from end users. +- 6) End users have provided the data for elements suitable for targeting. + +The use of the "Ignore if available" option is recommended to be considered when enrichment of a subset population including end users having a particular info element value (trait) is desired. It maximizes the number of TD-AMFs that accept a configuration package having a specific trait, even if not made available, with the side effect of including some end users that do not have that trait. + +# Appendix III + +## Examples of TD-AMF configurations, reports and permits + +(This appendix does not form an integral part of this Recommendation.) + +## III.1 Example of use of configuration package data structure for service-common measurements + +Assuming the following example requirements: + +- 1) General + - a) External permission mode with permission level 3 + - b) Send all reports to the same address + - c) Re-transmit up to five additional times following transport non-acknowledgement from aggregation functions. +- 2) Fast-changing information + - a) Information to be frequently sampled and reported includes: + - i) Active service type + - ii) Content ID info + - iii) Sample times + - iv) End-user ID info (with method and confidence parameters) + - v) End-user presence confidence (with method parameter) + - vi) Current location (if moved over 30 metres since last sample value) + - b) Events to be measured and reported include + - i) Video resize (with parameters) + - c) Measurement times + - i) Measurement period 1 = Event plus time sampling every five minutes between 1400 hours-2300 hours + - ii) Measurement period 2 = Time sampling every ten minutes between 2300 hours-1400 hours + - iii) Ignore the sample if its sample value is the same as the previous sample's value + - d) Reporting + - i) Report events immediately + - ii) Report sample values every ten minutes + - iii) Measurements are stored if the TD-AMF is unable to send reports +- 3) Slowly-changing information + - a) Slowly changing information to be sampled and reported includes: + - i) End user's device information + - ii) End user's biographic information (e.g., gender, birth date, birth location and residential address) + - b) Measurement times + - i) Anytime + - c) Reporting + - i) Report anytime daily, or on demand + +- ii) Store measurements if the TD-AMF is unable to send reports +- iii) Store with lower priority relative to other measurements + +The solution example in Figure III.1 shows values assigned to the configuration package data structure to meet the above requirements. Relevant defaults are shown in *gray*; these are not required to be explicitly included in the configuration. + +``` + +AMFConfigPackage (1) + PackageID (0-1) [ PackageVersion (0-1)] = 12345, 2 + EffectivityDateAndTime (0-1) = 2013-10-10T12:00:00.00 + MeasurementRequestSet (1-*) + DefaultDeliveryAddress (0-*) = http://defaultdeliveryaddress.com + DefaultRetransmitNumber (0-1) = 5 + DefaultDayOfWeekTheWeek (0-*) = 0 (Everyday) + DefaultNothingNewReportMode (0-1) = 0 (send nothing if same value) + DefaultMeasurementReportNumberByPush (0-1) = 1 + DefaultMaxTimeBetweenDelivery (0-1) = 0 (infinite) + DefaultStartTime (0-1) = 00:00:00.00 + DefaultEndTime (0-1) = 23:59:59.99 + DefaultStartDeliveryWindowTime (0-1) = 00:00:00.00 + DefaultEndDeliveryWindowTime (0-1) = 23:59:59.99 + MeasurementRequest (1-*) + MeasurementRequestID (1) = 1 + MeasurementSchedule (1-*) + MeasurementPeriod (0-*) + StartTime (0-1) = 14:00:00.00 + EndTime (0-1) = 23:00:00.00 + EventTrigger (0-*) + Event (0-*) = VideoResize + Priority (0-1) = 5 + TimeTrigger (0-1) + SampleSet (0-*) [SampleSetIdentifier(1)] = "UserList" + SampleSet (0-*) [SampleSetIdentifier(1)] = "UserPresent" + SampleSet (0-*) [SampleSetIdentifier(1)] = "TDLocation" + SampleSetQualifier (0-*) = "30" + Periodicity (1) = 300 + Priority (0-1) = 5 + MeasurementSchedule (1-*) + MeasurementPeriod (0-*) + StartTime (0-*) = 23:00:00.00 + EndTime (0-*) = 14:00:00.00 + TimeTrigger (0-1) + SampleSet (0-*) [SampleSetIdentifier(1)] = "UserList" + +``` + +``` + + SampleSet (0-*) [SampleSetIdentifier(1)] = "UserPresent" + SampleSet (0-*) [SampleSetIdentifier(1)] = "TDLocation" + SampleSetQualifier (0-*) = "30" + Periodicity (1) = 600 + Priority (0-1) = 5 + MeasurementDeliverySchedule (0-1) + ImmediatePush (0-1) +MeasurementRequest (1-*) + MeasurementRequestID (1) = 2 + MeasurementSchedule (1-*) + ServiceStartTrigger (0-1) + Interval (0-1) = 1 + SampleSet (0-*) [SampleSetIdentifier(1)] = "DeviceInfo" + SampleSet (0-*) [SampleSetIdentifier(1)] = "UserBioInfo" + Priority (0-1) = 1 +MeasurementDeliverySchedule (0-1) +DelayedPushAndPull (0-1) + +``` + +**Figure III.1 – Service-common example configuration package** + +NOTE 1 – Active service type: The service-common measurements are only reported when a specific service is active. Correlation between service-common measurements and the active service may be achieved by using service start/end events of the active service. No additional configuration for this is needed. However if there is no service-specific report e.g., linear TV, then the active service type may not be known. + +NOTE 2 – Sample times: MeasurementReportTriggerTime is used to report the time that an element is sampled. No additional configuration for this is needed. + +NOTE 3 – For slowly-changing data, if the random delivery time is generated which is after the ServiceStartTrigger, then the delivery of that data occurs at the next day's random time. + +NOTE 4 – Content ID info could be derived from content source and time for linearTV. + +## **III.2 Example of measurement reports associated with configuration example of Figure III.1** + +Given the configuration example of Figure III.1, examples of end-user behaviours are assumed which, together with the configuration, result in a series of measurement reports being delivered. + +During this two day example, a random delivery time is chosen at 0500 hours. Presence detection is assumed to be supported by key push measurements. The measurement periods and delivery windows of measurement requests 1 (MR1) and 2 (MR2) are shown for reference in Figure III.2. Measurement request 1 uses immediate delivery. Measurement request 2 uses delayed and pull delivery, and has a random delivery time. + +The service-start and service-end events shown in Figure III.2 represent service-specific events described in [ITU-T H.741.3]. Since a TD-AMF may aggregate multiple measurement reports into a measurement package, it is likely that the service-start event would be aggregated into AM report packages (1), (4), (6) and (9). Four service periods labelled A-D occur between associated-service-start and service-end events. + +It is assumed that the remote control has a button per family member which may be pressed when that member watches TV. This is used to indicate UserList change. + +![Figure III.2: Example of end-user behaviours and measurement reports. The diagram shows a timeline for two measurement requests (MR 1 and MR 2) over two days (Day 1 and Day 2). MR 1 has alternating 'Measurement period 1' and 'Measurement period 2'. MR 2 has 'Random time' markers and 'Measurement period and delivery window'. Below the timeline, 'Behaviours' are listed for service periods A, B, C, and D, including service start/end, video resize, key presses, device movement, and UserList change. 'Report packages' are numbered (1) through (11), indicating immediate or delayed reports generated by these behaviors. A reference code H.741.1(12)_FIII.2 is at the bottom right.](352d21d1e740e4a58cb17ab8656cfad8_img.jpg) + +Figure III.2: Example of end-user behaviours and measurement reports. The diagram shows a timeline for two measurement requests (MR 1 and MR 2) over two days (Day 1 and Day 2). MR 1 has alternating 'Measurement period 1' and 'Measurement period 2'. MR 2 has 'Random time' markers and 'Measurement period and delivery window'. Below the timeline, 'Behaviours' are listed for service periods A, B, C, and D, including service start/end, video resize, key presses, device movement, and UserList change. 'Report packages' are numbered (1) through (11), indicating immediate or delayed reports generated by these behaviors. A reference code H.741.1(12)\_FIII.2 is at the bottom right. + +**Figure III.2 – Example of end-user behaviours and measurement reports** + +Eleven report packages indicated in Figure III.2 are delivered as follows: + +- 1) Per measurement request 2, on day one at about 0125 hours, the first measurement of sample values (DeviceInfo, UserBioInfo) is taken due to the occurrence of the first service start of the day. The associated delayed report (3) is delivered at the randomly picked time of 0500 hours. +- 2) During service period A, a video resize event is not measured. Per measurement request 1, UserList and TDLocation periodic samples are measured every ten minutes and pushed immediately if subsequent sample values change. We assume that all sampled values are new in service period A. UserPresent is also sampled every ten minutes and reported immediately for the service start and unmeasured video resize event since it was associated with a remote key press. The first immediate report (1) is delivered at about 0135 hours, with a second UserPresent report (2) following sampling of video resize key press. The UserPresent sample value for service end is not measured since the next sample time is not during a service period. +- 3) During service period B, no events are measured. The sample values of UserList and TDLocation are the same as measured during service period A and therefore are not to be reported. UserPresent is sampled every ten minutes and reported immediately for the service start (4) and an unrecognized remote key push (5). The UserPresent sample value for service end is not measured since the next sample time is not during a service period. +- 4) Between service periods B and C, the TD-AMF device is moved over 30 m, but it is not reported yet since there is no current service period. When service period C starts, the sample value UserList is the same as measured during service period A and therefore is not to be reported. The initial sample values of TDLocation and UserPresent have changed so they are immediately reported (6). A video resize event occurs which is immediately reported (7), followed at the next sample time with a UserPresent immediate report (8) from the video resize key push. The UserPresent sample value for service end is not measured since the next sample time is not during a service period. + +- 5) For day 2, since there are no stored measurements to be reported at the randomly picked time in the delivery window, the associated scheduled delayed report is not sent. +- 6) At about 0750 hours, the first measurement of sample values (DeviceInfo and UserBioInfo) is taken due to the occurrence of the first service start of the day (service period D). The measurement report is stored. +- 7) When service period D starts, the sample values of UserList and TDLocation are the same as measured during service period C and therefore are not to be reported. The sample values of UserPresent have changed so an immediate report is sent (9). A UserList change occurs. The UserList and UserPresent which are sampled every ten minutes cause a report to be sent immediately (10) after the sample time where the change is detected. The UserPresent sample value for service end is not measured since the next sample time is not during a service period. +- 8) A measurement report request received after service period D pulls a report (11) of the stored service start measurements of service period D. + +The contents of the 11 example AM report packages are as follows. + +AM report package (1) immediately upon service start of service period A, due to the first sample TDLocation, UserList and UserPresent value changes. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) +| | MeasurementRequestID (1) = 1 +| | MeasurementReportTriggerTime (1) = 2012-05-30T01:35:00-06:00 +| | TDLocation (0-1) = 49.27 -123.11 +| | UserList (0-1) +| | | UserIDInfo (1-*) +| | | | UserID (0-1) = "34568234" +| | | | UserIDMethod (0-1) = "login" +| | | | UserIDConfidence(0-1) = 100.0 +| | UserPresent (0-*) +| | | PresenceMethod (0-1) = "remotekeypress" +| | | PresenceTime (0-1) = 01:25:00 +| | | PresenceConfidence (0-1) = 100.0 +| MeasurementReport (1-*) for service specific ServiceStart (not shown) + +``` + +**Figure III.3 – Service-common example report package 1** + +AM report package (2) following ten-minute sampling of the video resize keypress. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) + +``` + +``` + +| | MeasurementRequestID (1) = 1 +| | MeasurementReportTriggerTime (1) = 2012-05-30T03:05:00-06:00 +| | TDLocation (0-1) = 49.27 -123.11 +| | UserPresent (0-*) = +| | | PresenceMethod (0-1) = "remotekeypush" +| | | PresenceTime (0-1) = 02:58:00 +| | | PresenceConfidence (0-1) = 100.0 + +``` + +**Figure III.4 – Service-common example report package 2** + +AM report package (3) is a delayed report of DeviceInfo and UserBioInfo. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) +| | MeasurementRequestID (1) = 2 +| | MeasurementReportTriggerTime (1) = 2012-05-30T01:25:00-06:00 +| | DeviceInformation (0-1) +| | | TVandSTBInformation (0-1) +| | | | TVInformation (0-1) +| | | | | TVManuf (0-1) = sam +| | | | | TVModel (0-1) = 3456 +| | | | | TVSerialNum (0-1) = 12345678 +| | | | STBInformation (0-1) +| | | | | STBManuf (0-1) = ABC457 +| | | | | STBModel (0-1) = "3f345" +| | | | | STBSerialNum (0-1) = "142234324" +| | UserBiographicInformation (0-1) +| | | | ControlledUserInfoTypeDate (0-*) = "Birthday"; +ControlledUserInfoValueDate (1) = 1962-09-24 +| | | | ControlledUserInfoTypeString (0-*) = "Gender"; +ControlledUserInfoValueString (1) = "M" +| | | | ControlledUserInfoTypeAddress (0-*) = "BirthLocation"; +ControlledUserInfoValueAddress (1) = FR, 75 +| | | | ControlledUserInfoTypeAddress (0-*) = "UserResidentialAddress"; +ControlledUserInfoValueAddress (1) = FR, 75 + +``` + +**Figure III.5 – Service-common example report package 3** + +AM report package (4) Following the start of service period B. The first sample value of UserPresent changed due to service start remote key press. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) +| | MeasurementRequestID (1) = 1 +| | MeasurementReportTriggerTime (1) = 2012-05-30T07:19:00-06:00 +| | UserPresent (0-*) +| | | PresenceMethod (0-1) = "remotekeypush" +| | | PresenceTime (0-1) = 07:09:00 +| | | PresenceConfidence (0-1) = 100.0 +| MeasurementReport (1-*) for service specific ServiceStart (not shown) + +``` + +**Figure III.6 – Service-common example report package 4** + +AM report package (5) following service start of service period B due to sampling of UserPresent due to an unknown remote key press. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) +| | MeasurementRequestID (1) = 1 +| | MeasurementReportTriggerTime (1) = 2012-05-30T10:09:00-06:00 +| | UserPresent (0-*) +| | | PresenceMethod (0-1) = "remotekeypush" +| | | PresenceTime (0-1) = 09:59:10 +| | | PresenceConfidence (0-1) = 100.0 + +``` + +**Figure III.7 – Service-common example report package 5** + +AM report package (6) following the start of service period C. The first sample values of TDLocation and UserPresent have changed. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) +| | MeasurementRequestID (1) = 1 +| | MeasurementReportTriggerTime (1) = 2012-05-30T15:05:00-06:00 +| | TDLocation (0-1) = 49.27 -123.13 +| | UserPresent (0-*) +| | | PresenceMethod (0-1) = "remotekeypush" +| | | PresenceTime (0-1) = 14:55:00 + +``` + +``` + +| | | PresenceConfidence (0-1) = 100.0 +| MeasurementReport (1-*) for service specific ServiceStart (not shown) + +``` + +**Figure III.8 – Service-common example report package 6** + +AM report package (7) following a video resize event within service period C, an immediate report is sent. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) +| | MeasurementRequestID (1) = 1 +| | MeasurementReportTriggerTime (1) = 2012-05-30T19:00:00-06:00 +| VideoResize (0-1) +| | ServiceInstanceID (1) = 1 +| | ImageWidth (1) = 640 +| | ImageHeight (1) = 480 + +``` + +**Figure III.9 – Service-common example report package 7** + +AM report package (8) following keypress of video resize within service period C, a UserPresent report is sent due to five-minute sampling. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) +| | MeasurementRequestID (1) = 1 +| | MeasurementReportTriggerTime (1) = 2012-05-30T19:05:00-06:00 +| | UserPresent (0-*) +| | | PresenceMethod (0-1) = "remotekeypush" +| | | PresenceTime (0-1) = 19:00:01 +| | | PresenceConfidence (0-1) = 100.0 + +``` + +**Figure III.10 – Service-common example report package 8** + +AM report package (9) Following the start of service period D. The first sample value of UserPresent changed due to service start remote key press. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) + +``` + +``` + +| | MeasurementRequestID (1) = 1 +| | MeasurementReportTriggerTime (1) = 2012-05-31T08:00:00-06:00 +| | UserPresent (0-*) +| | | PresenceMethod (0-1) = "remotekeypush" +| | | PresenceTime (0-1) = 07:50:00 +| | | PresenceConfidence (0-1) = 100.0 +| MeasurementReport (1-*) for service specific ServiceStart (not shown) + +``` + +**Figure III.11 – Service-common example report package 9** + +AM report package (10) A UserList change occurs. The UserList and UserPresent which are sampled every ten minutes cause a report to be sent immediately (10) after the sample time where the change is detected. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) +| | MeasurementRequestID (1) = 1 +| | MeasurementReportTriggerTime (1) = 2012-05-31T09:10:00-06:00 +| | UserList (0-1) +| | | UserIDInfo (1-*) +| | | | UserID (0-1) = "34568233" +| | | | UserIDMethod (0-1) = "login" +| | | | UserIDConfidence (0-1) = 100.0 +| | | UserIDInfo (1-*) +| | | | UserID (0-1) = "34568234" +| | | | UserIDMethod (0-1) = "remote personalisation" +| | | | UserIDConfidence (0-1) = 90.0 +| | UserPresent (0-*) +| | | PresenceMethod (0-1) = "remotekeypush" +| | | PresenceTime (0-1) = 09:06:00 +| | | PresenceConfidence (0-1) = 100.0 + +``` + +**Figure III.12 – Service-common example report package 10** + +AM report package (11) following a measurement report request message, service start time stored sample values of DeviceInfo and UserBioInfo are reported. + +``` + +AMReportPackage (1) +| SubscriberID (0-1) = "WorldspGold012345678" +| TerminalDeviceID (1) = 363566737 +| MeasurementReport (1-*) +| | MeasurementRequestID (1) = 2 + +``` + +``` + +| | MeasurementReportTriggerTime (1) = 2012-05-31T16:30:00-06:00 +| | DeviceInformation (0-1) +| | | TVandSTBInformation (0-1) +| | | | TVInformation (0-1) +| | | | | TVManuf (0-1) = sam +| | | | | TVModel (0-1) = 3456 +| | | | | TVSerialNum (0-1) = 12345678 +| | | | STBInformation (0-1) +| | | | | STBManuf (0-1) = ABC457 +| | | | | STBModel (0-1) = "3f345" +| | | | | STBSerialNum (0-1) = "142234324" +| | UserBiographicInformation (0-1) +| | | ControlledUserInfoTypeDate (0-*) = "Birthday"; +| | | ControlledUserInfoValueDate (1) = 1962-09-24 +| | | ControlledUserInfoTypeString (0-*) = "Gender"; +| | | ControlledUserInfoValueString (1) = "M" +| | | ControlledUserInfoTypeAddress (0-*) = "BirthLocation"; +| | | ControlledUserInfoValueAddress (1) = FR, 75 +| | | ControlledUserInfoTypeAddress (0-*) = "UserResidentialAddress"; +| | | ControlledUserInfoValueAddress (1) = FR, 75 + +``` + +**Figure III.13 – Service-common example report package 11** + +NOTE – The information reported in AM report package (11) refers to the user who started service period D, rather than the one who ended it, identified in AM report package (10). + +## III.3 Examples using end-user information for filtering configuration packages + +When multicast delivery of configuration packages is used, end-user information filtering may be used at the configuration message level, or at the measurement request level, or at both levels. + +This first multicast configuration message (defined in Table 7 of [ITU-T H.741.4]) example uses the example user info values given in clause II.11. Relevant defaults are shown in *gray*; these are not required to be explicitly included in the multicast configuration message. The delivery dependent XML is shown without the configuration packages detail. + +``` + +MulticastConfigurationMsg +| MessageType (1) = 4 (multicast configuration message) +| ExpirationTime (1) +| Digest (1) +| Signature (1) +| ProtocolVersionMajorID (1) = 1 +| ProtocolVersionMinorID (1) = 0 +| MessageID (1) = 562256 +| LowerThreshold (1) = 0 (Thresholds not used) +| UpperThreshold (1) = 0 (Thresholds not used) +| ResponseQualifier (1) = 0 (no acknowledge or error response requested) +| UserInfoTarget (0-*) + +``` + +``` + +| | UserInfoTypeString (1) = "occupation" +| | IgnoreIfUnavailable (0-1) = 0 (do not ignore if "occupation" is +| unavailable) +| | UserInfoValueString (1) = "doctor" +| UserInfoTarget (0-*) +| | UserInfoTypeString (1) = "income" +| | IgnoreIfUnavailable (0-1) = 1 (ignore if "income" is unavailable) +| | UserInfoValueString (1) = "over 200,000 Euros" +| ImmediateAndFutureConfiguration (1) + +``` + +**Figure III.14 – End-user information for configuration packages – Example 1** + +The AMFConfigPackages contained in ImmediateAndFutureConfiguration (ConfigPackageRequestResponse in [ITU-T H.741.2]) will only be processed by TD-AMFs having a permission level of at least 2, and if an end user has provided generic end user info "occupation" = "doctor" and either "income" = "over 200 000 Euros" or has not provided "income". The use of the ignore if unavailable feature with "income" maximizes the number of TD-AMFs that accept the configuration packages having "income" = "over 200 000 Euros" even if "income" is not made available, with the side effect of including some end users not having "income"= "over 200 000 Euros". + +The following configuration package example includes end-user information filtering to qualify individual measurement requests. The details of individual Measurement Requests are not shown. + +``` + +AMFConfigPackage (1) + PackageID (1) = 9345 + MeasurementRequestSet (1-*) + MeasurementRequest (1-*) (Measurement Request 1 - details omitted) + MeasurementRequestID (1-*) = 1 + MeasurementSchedule (1-*) + MeasurementRequest (1-*) (Measurement Request 2 - details omitted) + MeasurementRequestID (1-*) = 2 + MeasurementSchedule (1-*) + MeasurementRequest (1-*) (Measurement Request 3 - details omitted) + MeasurementRequestID (1-*) = 3 + MeasurementSchedule (1-*) + MeasurementRequestSetFilter (0-*) + UserInfoTarget (1-*) + UserInfoTypeString (1) = "language spoken" + IgnoreIfUnavailable (0-1) = 0 (do not ignore if "language spoken" is +| unavailable) + UserInfoValueString (1) = "French" + MeasurementRequestID (1-*) = 2 + MeasurementRequestSetFilter (0-*) + UserInfoTarget (1-*) + UserInfoTypeString (1) = "language spoken" + +``` + +``` + +IgnoreIfUnavailable (0-1) = 0 (do not ignore if "language spoken" is +unavailable) + +UserInfoValueString (1) = "German" + +MeasurementRequestID (1-*) = 3 + +``` + +**Figure III.15 – End-user information filtering of measurement requests – Example 2** + +In this second example, Measurement Request 1 is configured in the receiving TD-AMF unconditionally. Measurement Request 2 is conditionally configured only if "language spoken" = "French". Measurement Request 3 is conditionally configured only if "language spoken" = "German". + +The above two examples could be combined. In which case the filtering at the multicast configuration message level occurs first, then if the TD-AMF processes the configuration package the measurement request filtering will follow. + +## III.4 Example of UserPermit + +The data structure for UserPermit is defined in [ITU-T H.741.2]. In this example, permission level 3 is granted for linear TV channels 150 and 153, on STB and TV, for all content genres except religious or health. Additionally, permission level 2 is granted for all other linear TV channels, on STB, TV and mobile, and for all content genres except religious. Measurements are forbidden when specific permissions are not granted in a permit; in this example, since mobile device measurement is not specified for linear TV channels 150 and 153, this combination must not be measured. + +``` + +UserPermit + + ExpirationDate (0-1) = 2012-09-24 + DefaultPermissionLevel (0-1) = 2 + DefaultAllContentClassExceptList (0-1) + ContentClassDomain (1-*) = "TV-Anytime" + ContentClassID (1-*) = "Religious" + AnonUserID (0-1) = 24566778 + UserID (0-1) = "34568234" + UserPermissionSet (0-*) + PermissionLevel (0-1) = 3 + UserPermission (1-*) + ChannelQualifier (0-1) + ChannelList (0-1) + ServiceIdentifier (1-*) = "channel150" + ServiceIdentifier (1-*) = "channel153" + TerminalDeviceSet (0-1) + TerminalDeviceType (1-*) = 0 + TerminalDeviceType (1-*) = 1 + AllContentClassExceptList (0-1) + ContentClassDomain (1-*) = "TV-Anytime" + ContentClassID (1-*) = "Health" + ContentClassID (1-*) = "Religious" + +``` + +``` + +UserPermissionSet (0-*) + UserPermission (1-*) + ChannelQualifier (0-1) + AllChannelsExceptList (0-1) + ServiceIdentifier (1-*) = "channel150" + ServiceIdentifier (1-*) = "channel153" + TerminalDeviceSet (0-1) + TerminalDeviceType (1-*) = 0 + TerminalDeviceType (1-*) = 1 + TerminalDeviceType (1-*) = 2 + +``` + +**Figure III.16 – Example user permit** + +The XML schema instances for examples of TD-AMF configurations, reports and permits are in Appendix IX. + +# Appendix IV + +## Considerations of end-user permission levels + +(This appendix does not form an integral part of this Recommendation.) + +Table IV.1 relates the measurements, the implications for the AM system, the potential for an end-user's data profile to threaten privacy, and services for the four permission levels of AM. + +**Table IV.1 – AM permission levels, their impact on the AM system, privacy infringement potential and supportable services** + +| | Permission Level 0
    (default)     | Permission Level 1 | Permission Level 2 | Permission Level 3 | +|--------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| End-user permission | Not required | Required | Required | Required | +| Permitted measured data | None | End-user behaviours and device info, distinguishable end user, no end-user information | End-user behaviours and device info, distinguishable end user, and anonymous end-user information | End-user behaviours and device info, distinguishable end user, anonymous end-user information, and identifiable subscriber or end-user information | +| Example data | No data is measured | Channel 5 was watched by anonymous end user #12683304 on mobile device model "X" | Channel 5 was watched by anonymous end user #12683304, interested in gardening, on mobile device model "X" | Channel 5 was watched on mobile device model "X" being used by subscriber or end user "John Smith" who is interested in gardening | +| Other impact on AM system | Prevent or filter out measurements request | Correlation among end-users' devices possible | Correlation among end-users' devices possible | Correlation among end-users' devices possible
    Controlled subscriber/end user information requires special security handling | +| Privacy infringement potential | None | Measured data alone may not influence privacy profile. Measured data plus additional data may influence privacy profile | Measured data alone may not influence privacy profile. Measured data plus additional data may influence privacy profile | Measured data alone may influence privacy profile | + +**Table IV.1 – AM permission levels, their impact on the AM system, privacy infringement potential and supportable services** + +| | Permission Level 0
    (default)     | Permission Level 1 | Permission Level 2 | Permission Level 3 | +|------------------------------------|-----------------------------------------|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Additional SP services supportable | Plain subscription | Targeted advertisement and content recommendation
    Content rating and engagement reporting | Better targeted advertisement and content recommendation
    Content rating and engagement reporting | IPTV end-user engagement driven personalized communications
    Even better targeted advertisement and content recommendation
    Content rating and engagement reporting | + +# Appendix V + +## Considerations regarding the unlinkability property + +(This appendix does not form an integral part of this Recommendation.) + +Clause 9.1.5 briefly explains that the AM system relies upon the AGF to remove unintentional linkability information before providing information to higher functions. However, a network-based approach to provide unlinkability for AM may be possible. This appendix provides considerations for such an approach. + +It is possible to correlate an anonymous end user (either in permission level 2 or permission level 1) with other information previously or subsequently obtained about that user. To avoid such a correlation, unlinkability property for AM report submission is recommended – that is, the AGF may communicate directly with TD-AMFs but TD-AMFs send their AM reports indirectly. Indirection of AM reports is the basis to implement unlinkability which requires the use of additional network bandwidth. + +Following two scenarios highlight the need for the unlinkability property in AM architecture to achieve anonymity for TD-AMF from an AGF: + +- 1) Source IP address: When an end user submits AM reports with permission level 3 (in which all possible end user attributes – controlled or un-controlled information may become part of AM reports) and later changes permission level to either 2 or 1. Even though AM reports with permission level 1 do not have any personally identifiable information of the end user and sent with AnonID, the AGF can correlate AM reports with permission level 2 or 1 to AM reports with permission level 3 based on the source IP address of AM report messages. +- 2) MessageID: In pull delivery mode, an AGF sends a measurement report request with a unique identifier called MessageID. In response to the measurement report request, a TD-AMF generates its AM report consisting of the MessageID provided by the AGF. Assuming that the "source address" unlinkability is supported in AM system, use of persistent identifiers like MessageID undermine the unlinkability property since AGF knows to which TD-AMF a particular MessageID is sent. Even if TD-AMF manages to hide its source address, the MessageID element in the AM report reveals the identity of the TD-AMF. + +There can be other persistent identifiers similar to MessageID which may have potential to de-anonymize end users with permission level 1 or 2. Further study of AM message communications and study of overall AM architecture is needed. + +The unlinkability property can be achieved using privacy enhancing technologies from two broad classes of alternatives: + +- A. TTP (Trusted third party): Employing a trusted third party that acts as a proxy for TD-AMFs to submit AM reports, see Figure V.1. +- B. P2P (peer-to-peer): Collaboration among peer TD-AMFs to forward each other's AM reports to an AGF, see Figure V.2. + +One method from each alternative class is provided below: + +- TOR (The Onion Router [b-TOR]) – In this type of TTP-based method, an intermediary is introduced between an AM report sender (TD-AMF) and the receiver (AGF). The internal designs of this kind of method may vary from each other but the input and output interfaces are similar: they accept a communication from sender and deliver it to intended receiver in such a fashion that the receiver cannot provably find out who the sender is. It is recommended that TD-AMFs choose the TTP instead of AGF suggesting one. To achieve unlinkability from AGF, TD-AMFs (end users) put their trust in a trusted-third-party. + +![Figure V.1: Trusted third-party methods. The diagram shows two scenarios. On the left, labeled 'TTP [b-Anonymagator]', two TD-AMF nodes (one orange, one blue) send reports to a 'Trusted-third-party (proxy)' box, which then forwards them to an AGF box. On the right, labeled 'TTP [b-TOR]', the same two TD-AMF nodes send reports to a 'TOR network nodes' box, which then forwards them to an AGF box. The label 'H.741.1(12)_FV.1' is at the bottom right.](32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg) + +Figure V.1: Trusted third-party methods. The diagram shows two scenarios. On the left, labeled 'TTP [b-Anonymagator]', two TD-AMF nodes (one orange, one blue) send reports to a 'Trusted-third-party (proxy)' box, which then forwards them to an AGF box. On the right, labeled 'TTP [b-TOR]', the same two TD-AMF nodes send reports to a 'TOR network nodes' box, which then forwards them to an AGF box. The label 'H.741.1(12)\_FV.1' is at the bottom right. + +**Figure V.1 – Trusted third-party methods** + +- Crowds [b-Crowds] – In this type of P2P-based method, a set of TD-AMFs becomes part of a group called the anonymous set. The anonymous set may be formed by an AGF or can be formed among TD-AMFs themselves. Each member of the anonymous set forwards its own AM report and other incoming AM reports to a randomly chosen neighbour. The AGF may be allowed to be part of the anonymous set. When the AGF is not part of the anonymous set, the TD-AMFs in the anonymous set submit all the reports directly to the AGF after performing shuffling of their reports for a fixed time period. In Figure V.2 at time $t_1$ the TD-AMFs belonging to an anonymous set exchange their AM reports. Subsequently at time $t_2$ these reports are sent to the AGF. To achieve unlinkability from AGF, TD-AMFs pay a cost in terms of extra inter-TD-AMF computation and temporary local storage. + +![Figure V.2: P2P methods. The diagram shows two time points. At time t1, labeled 'P2P(crowds) at time t1', four TD-AMF nodes (orange, blue, grey, green) are arranged in a row. They are all interconnected with curved double-headed arrows, indicating a fully connected mesh. At time t2, labeled 'P2P(crowds) at time t2', the same four TD-AMF nodes are shown below an AGF box. Each TD-AMF has a straight arrow pointing up to the AGF. The label 'H.741.1(12)_FV.2' is at the bottom right.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +Figure V.2: P2P methods. The diagram shows two time points. At time t1, labeled 'P2P(crowds) at time t1', four TD-AMF nodes (orange, blue, grey, green) are arranged in a row. They are all interconnected with curved double-headed arrows, indicating a fully connected mesh. At time t2, labeled 'P2P(crowds) at time t2', the same four TD-AMF nodes are shown below an AGF box. Each TD-AMF has a straight arrow pointing up to the AGF. The label 'H.741.1(12)\_FV.2' is at the bottom right. + +**Figure V.2 – P2P methods** + +The P2P-based alternative is preferred over the TTP-based alternative. In the P2P-based alternative, the trust of the TD-AMF is spread across peer TD-AMFs whereas in the TTP-based alternative, absolute trust is placed in the trusted-third-party and collusion of such a trusted-third-party with AGF or other stakeholders interested in end-user PII puts the end users' anonymity at stake. Therefore the P2P-based approach limits the scope of an attacker in comparison to the TTP-based approach. + +While choosing among the alternative methods to achieve unlinkability, it is important to consider the required modifications to the AM architecture. P2P-based alternative can achieve unlinkability without introducing any new entity to the AM architecture, whereas TTP-based alternative introduces a trusted-third-party to the AM architecture. It is possible to keep the trusted-third-party + +outside of AM architecture and re-route the AM reports via the trusted-third-party but that will make AM architecture incapable of providing complete anonymity to end users on its own. + +### **Other considerations for unlinkability** + +Even after providing unlinkability property in AM architecture with the help of a P2P/TTP-based alternative, it is possible for an AGF to link end users to their reports. Following are the scenarios that may lead to linkability of end users, if left unaddressed. + +- Correlation with the help of other applications – The end user access terminal may be running other interactive non-AM applications. If other applications running on end-user's terminal are reporting information that is part of AM reports being submitted anonymously, the unlinkability property of AM will be undermined. +- Correlation with the content consumption logs – The IPTV content provider has logs of each subscriber's content access. Such logs correlated with the anonymous reports may reveal identity of the report's generator. + +The impact of unlinkability implementations on AM abnormal situation handling and non-repudiation needs further study, since TD-AMFs which generate incorrect reports need to be addressed. + +The implementation and design of the unlinkability property for AM are recommended to be in line with the current guidelines on privacy per [b-NIST PUB 800-122] and [b-FTC 120326] and is for further study. + +# Appendix VI + +## Considerations for AM vendors + +(This appendix does not form an integral part of this Recommendation.) + +## Aggregation methods + +Analysis of measurements may lead to aggregation by many methods including aggregation: + +- over a subscriber's end-user device +- over a user's end-user device +- over audience measurement functions in end-user functions, network functions and content delivery functions +- over time +- over device types +- over a geography +- over linear channels in the linear service +- over the x-PVR service +- over the VoD service +- over content +- over end-user's behaviours +- over combinations of the above. + +There may be value to multiple stakeholders derivable from each aggregation method. For example, aggregation over a geographic area may be valuable to geographic businesses for location-based advertising; aggregation over time may be valuable to industry metrics that are defined by all viewing that occurs, including live broadcast plus three days; and aggregation across content from the same studio for content providers to guide future content. + +# Appendix VII + +## Audience measurement capabilities and profiles + +(This appendix does not form an integral part of this Recommendation.) + +Table VII.1 lists the capabilities of TD-AMFs. + +**Table VII.1 – TD-AMF capability list** + +| Area of capability | Capability | References | +|-------------------------|--------------------------------------------|-----------------| +| Transport protocols | Specific protocols are out of scope of AM | [ITU-T H.741.4] | +| Transport delivery mode | Unicast | [ITU-T H.741.4] | +| | Multicast | [ITU-T H.741.4] | +| Cryptographic protocols | TLS | Clause 9.1 | +| | TLS-SRP | Clause 9.1 | +| Permission mode | External | Clause 9.2.1 | +| | Internal | Clause 9.2.2 | +| | Hybrid | Clause 9.2.3 | +| Configuration mode | Push | [ITU-T H.741.0] | +| | Pull | [ITU-T H.741.0] | +| | Hybrid | [ITU-T H.741.0] | +| Measurement Triggers | Event | Clause 7.1.2.4 | +| | Time sampling | Clause 7.1.2.4 | +| | Service start sampling | Clause 7.1.2.4 | +| Report delivery mode | Immediate Push | Clause 7.1.2.6 | +| | Delayed Push | Clause 7.1.2.6 | +| | Pull | Clause 7.1.2.6 | +| | Delayed Push and Pull | Clause 7.1.2.6 | +| Operational Management | Multicast Acknowledgements | Clause 7.1.1.2 | +| | Multicast threshold ranges sub-addressing | Clause 7.1.1.2 | +| | Multicast device type sub-addressing | Clause 7.1.1.2 | +| | Multicast end-user info sub-addressing | Clause 7.1.1.2 | +| | Multicast MAC addresses sub-addressing | Clause 7.1.1.2 | +| | Multicast error reporting | Clause 7.1.1.2 | +| | Measurement report end user info filtering | Clause 7.1.2 | +| | Content Filtering | Clause 7.1.2.2 | + +These capabilities are included in the capability data structure (see Table 2 of [ITU-T H.741.2]). + +A set of AM capability profiles as a short-hand way to identify subsets of capability options for TD-AMFs would be useful. Capability profiles would make it easier for vendors, integrators and service providers to understand product capabilities. TD-AMFs could be identified as having AM capability profile 1, or 2, or 3, etc. which would relate to a specific subset of capability options from Table VIII.1 and service-specific capability options listed in an appendix of [ITU-T H.741.3]. The definition of such capability profiles is for further study. + +# Appendix VIII + +## XML schema on the data structures for audience measurement service discovery + +(This appendix does not form an integral part of this Recommendation.) + +This is the XML schema that can be exchanged for audience measurement service discovery. + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + +``` + +# Appendix IX + +## XML schema instances for TD-AMF configurations, reports and permits + +(This appendix does not form an integral part of this Recommendation.) + +These are the XML schema instances for examples of TD-AMF configurations, reports and permits defined in Appendix III. These instances are based on Appendix VIII. + +## IX.1 Instance based on clause III.1 + +Figure III.1 (Service-common example configuration package) shows values assigned to the configuration package data structure. + +Figure IX.1 is an instance based on Figure III.1. + +``` + + + + Everyday + + + CreateCompleteAMSSample + + + http://defaultdeliveryaddress.com + 5 + + AMReportPushedAsSoonAsProduced + 0 + + + + + Everyday + + + 5 + + + + 5 + 300 + + + + + + +``` + +``` + + + + 30 + + + + + + Everyday + + + 5 + 600 + + + + 30 + + + + + + + + + + + 1 + 1 + + + + + + + + + + + +``` + +**Figure IX.1 – Instance for service-common example configuration package** + +## IX.2 Instances based on clause III.2 + +Figure III.2 is an example of end-user behaviours and measurement reports. Eleven figures, Figures III.3 to III.13, are service-common example report packages. + +### IX.2.1 Instance based on Figure III.3 + +Figure IX.2 is an instance based on Figure III.3 (Service-common example report package 1). + +``` + + + + + + login + 100.0 + + + + RemoteKeyPush + 01:25:00 + 100.0 + + + +``` + +**Figure IX.2 – Instance for service-common example report package 1** + +### IX.2.2 Instance based on Figure III.4 + +Figure IX.3 is an instance based on Figure III.4 (Service-common example report package 2). + +``` + + + + + RemoteKeyPush + 02:58:00 + 100.0 + + + +``` + +**Figure IX.3 – Instance for service-common example report package 2** + +### IX.2.3 Instance based on Figure III.5 + +Figure IX.4 is an instance based on Figure III.5 (Service-common example report package 3). + +``` + + + + + ABC457 + 3f345 + 142234324 + + + sam + 3456 + 12345678 + + + + + M + 1962-09- +24 + FR, +75 + FR, +75 + + + + +``` + +**Figure IX.4 – Instance for service-common example report package 3** + +### IX.2.4 Instance based on Figure III.6 + +Figure IX.5 is an instance based on Figure III.6 (Service-common example report package 4). + +``` + + + + RemoteKeyPush + 07:09:00 + 100.0 + + + +``` + +**Figure IX.5 – Instance for service-common example report package 4** + +### IX.2.5 Instance based on Figure III.7 + +Figure IX.6 is an instance based on Figure III.7 (Service-common example report package 5). + +``` + + + + RemoteKeyPush + 09:59:00 + 100.0 + + + +``` + +**Figure IX.6 – Instance for service-common example report package 5** + +#### IX.2.6 Instance based on Figure III.8 + +Figure IX.7 is an instance based on Figure III.8 (Service-common example report package 6). + +``` + + + + + RemoteKeyPush + 14:55:00 + 100.0 + + + +``` + +**Figure IX.7 – Instance for service-common example report package 6** + +#### IX.2.7 Instance based on Figure III.9 + +Figure IX.8 is an instance based on Figure III.9 (Service-common example report package 7). + +``` + + + + + + + +``` + +**Figure IX.8 – Instance for service-common example report package 7** + +#### IX.2.8 Instance based on Figure III.10 + +Figure IX.9 is an instance based on Figure III.10 (Service-common example report package 8). + +``` + + + + RemoteKeyPush + 19:09:01 + 100.0 + + + +``` + +**Figure IX.9 – Instance for service-common example report package 8** + +#### IX.2.9 Instance based on Figure III.11 + +Figure IX.10 is an instance based on Figure III.11 (Service-common example report package 9). + +``` + + + + RemoteKeyPush + 07:50:00 + 100.0 + + + +``` + +**Figure IX.10 – Instance for service-common example report package 9** + +#### IX.2.10 Instance based on Figure III.12 + +Figure IX.11 is an instance based on Figure III.12 (Service-common example report package 10). + +``` + + + + + + login + 100.0 + + + remotepersonalization + 90.0 + + + + RemoteKeyPush + 09:06:00 + 100.0 + + + + +``` + +**Figure IX.11 – Instance for service-common example report package 10** + +#### IX.2.11 Instance based on Figure III.13 + +Figure IX.12 is an instance based on Figure III.13 (Service-common example report package 11). + +``` + + + + + + sam + 3456 + 12345678 + + + ABC457 + 3f345 + 142234324 + + + + + M + 1962-09- +24 + FR, +75 + FR, +75 + + + + + +``` + +**Figure IX.12 – Instance for service-common example report package 11** + +### IX.3 Instances based on Appendix III.3 + +Figure III.14 is an example of end-user information for configuration packages. Figure III.15 is an example of end-user information filtering of measurement requests. + +#### IX.3.1 Instance based on Figure III.14 + +Figure IX.13 is an instance based on Figure III.14 (End-user information for configuration packages). + +``` + + + MulticastConfigurationMsg + + 12 + NoAcknowledge_Or_ErrorResponseRequested + + + doctor + over +200,000 Euros + + +``` + +**Figure IX.13 – Instance for end-user information for configuration packages** + +#### IX.3.2 Instance based on Figure III.15 + +Figure IX.14 is an instance based on Figure III.15 (End-user information filtering of measurement requests). + +``` + + + + + + + + + + + + + + French + + + German + + +``` + +**Figure IX.14 – Instance for end-user information filtering of measurement requests** + +## IX.4 Instance based on Appendix III.4 + +Figure III.16 is an example of user permit. + +Figure IX.15 is an instance based on Figure III.16 (Example user permit). + +``` + + + NoInformation + + Religious + + + OnlyDistinguishabilityInfo + + + STB + TV + + + Health + Religious + + + + + + + + + + STB + TV + Mobile + + + + + + + + +``` + +**Figure IX.15 – Instance for example user permit** + +## Bibliography + +- [b-ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems.* +- [b-ITU-T H.721] Recommendation ITU-T H.721(2009), *IPTV terminal devices: Basic model Amendment 1: New Appendix II on terminal device implementation example.* +- [b-ITU-T H.740 Amd.1] Recommendation ITU-T H.740 Amd.1 (2011), *Application event handling for IPTV services: New video handling sensor event scenario in Appendix II.* +- [b-ITU-T H.770] Recommendation ITU-T H.770 (2009), *Mechanisms for service discovery and selection for IPTV services.* +- [b-ITU-T J.183] Recommendation ITU-T J.183 (2001), *Time-division multiplexing of multiple MPEG-2 transport streams over cable television systems.* +- [b-ITU-T J.200] Recommendation ITU-T J.200 (2010), *Worldwide common core – Application environment for digital interactive television services.* +- [b-ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2006), *Designations for interconnections among operators' networks.* +- [b-ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2004), *Enhanced Telecom Operations Map (eTOM) – The business process framework.* +- [b-ITU-T T.174] Recommendation ITU-T T.174 (1996), *Application programming interface (API) for MHEG-1.* +- [b-ITU-T X.800] Recommendation ITU-T X.800 (1991), *security architecture for open system interconnection for CCIT applications.* +- [b-ITU-T X.891] Recommendation ITU-T X.891 (2005) | ISO/IEC 24824-1 (2007), *Information technology – Generic applications of ASN.1: Fast infoset.* +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology – Terms and definitions.* +- [b-ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services.* +- [b-ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture.* +- [b-Anonymgator] *Anonymity-Preserving Data Aggregation using Anonymgator*, Microsoft Research, Nov. 2009. +<> +- [b-ATIS 0800026] ATIS 0800026 (2010), *Global Types XML Schema Description.* +- [b-Crowds] ACM TISSEC (April 1998), *Michael K. Reiter and Aviel D. Rubin, Crowds: Anonymity for Web Transactions.* +- [b-ETSI TS 102 472] ETSI TS 102 472 V1.3.1 (2009), *Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Content Delivery Protocols.* +- [b-FIPS PUB 197] FIPS PUB 197 (2001), *Advanced Encryption Algorithm (AES).* + +- [b-FIPS PUB 198-1] FIPS PUB 198-1 (2008), *The Keyed-Hash Message Authentication Code (HMAC)*. +- [b-NIST PUB 800-122] NIST Special PUB 800-122 (2010), *Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)*. +- [b-FTC 120326] FTC 120326 (2012), *Protecting Consumer Privacy in an Era of Rapid Change: Recommendations for Businesses and Policymakers*. +- [b-IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifier (URI): Generic Syntax*. +- [b-IETF RFC 5054] IETF RFC 5054 (2007), *Using the Secure Remote Password (SRP) Protocol for TLS Authentication*. +- [b-ISO/IEC 23001-1] ISO/IEC 23001-1:(2006, *Information technology – MPEG systems technologies – Part 1: Binary MPEG format for XML*. +- [b-ISO/IEC 27001] ISO/IEC 27001:2005, *Information technology – Security techniques – Information security management systems – Requirements*. +- [b-ISO/IEC 27002] ISO/IEC 27002:2005, *Information technology – Security techniques – Code of practice for information security management*. +- [b-TOR] *The Onion Routing project*. +See <> +- [b-W3C EXI] W3C Recommendations (2011), *Efficient XML Interchange (EXI) Format 1.0*. +- [b-W3C XMLSchemaP2] W3C Recommendations (2004), *XML Schema Part 2: Datatypes (Second Edition)*. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/raw.md b/marked/H/T-REC-H.742.0-201607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..94a53863492a701c7ca879bdc7c529e598a4546a --- /dev/null +++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/raw.md @@ -0,0 +1,624 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.742.0** + +(07/2016) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +IPTV multimedia services and applications for IPTV – IPTV +application event handling + +# --- **Use of video sensor devices for IPTV services: Architecture and requirements** + +Recommendation ITU-T H.742.0 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.742.0 + +# Use of video sensor devices for IPTV services: Architecture and requirements + +## Summary + +A video sensor is a device used by technology to extract useful information, for example, the number, gender, and age of persons in front of camera, by processing video data captured by camera. Recommendation ITU-T H.742.0 describes an architecture and the requirements of IPTV application events extracted by video sensor devices. The requirements cover general functionalities, delivery mechanisms, metadata, and functions to avoid the risk of privacy infringement. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.742.0 | 2016-07-14 | 16 | 11.1002/1000/12910 | + +## Keywords + +Audience measurement function, AMF, application event handling, Internet protocol television, IPTV, video sensor, video. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation ..... | 2 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 3 | +| 6 Overview..... | 4 | +| 7 Domain and architecture..... | 4 | +| 8 Requirements of application event by video sensor device..... | 6 | +| 8.1 Risks related to IPTV terminal devices used with video sensor device ..... | 6 | +| 8.2 Requirements for avoiding the risks of privacy infringement..... | 6 | +| 9 Functional requirements ..... | 7 | +| 9.1 Video processing functional requirement..... | 7 | +| 9.2 Terminal authentication functional requirement ..... | 7 | +| 9.3 Data output functional requirement..... | 7 | +| 9.4 Transmission functional requirement ..... | 7 | +| 9.5 Data storage functional requirement ..... | 7 | +| 9.6 Service subscribing functional requirement ..... | 7 | +| 9.7 Security functional requirement ..... | 7 | +| 9.8 Metadata functional requirement..... | 7 | +| 10 Requirements for the delivery of audience measurement data with video sensors ..... | 7 | +| Appendix I – Video sensor devices event scenario..... | 9 | +| Appendix II – Video sensor information generation scenario ..... | 11 | +| Appendix III – Use cases of video sensor information..... | 13 | +| III.1 Targeted advertising service..... | 13 | +| III.2 Personalized screen service ..... | 14 | +| III.3 IPTV ratings analysis service ..... | 15 | +| Bibliography..... | 17 | + + + +# Recommendation ITU-T H.742.0 + +# Use of video sensor devices for IPTV services: Architecture and requirements + +## 1 Scope + +This Recommendation describes the requirements of IPTV application events extracted by video sensor devices. It describes an architecture and the requirements for general functionalities, delivery mechanisms, metadata, and functions to avoid the risks of privacy infringement. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.741.0] Recommendation ITU-T H.741.0 (2012), *IPTV application event handling: Overall aspects of audience measurement for IPTV services.* +- [ITU-T H.741.2] Recommendation ITU-T H.741.2 (2012), *IPTV application event handling: Data structures of audience measurement for IPTV services.* +- [ITU-T X.1191] Recommendation ITU-T X.1191 (2008), *Functional requirements and architecture for IPTV security aspects.* +- [ITU-T Y.1901] Recommendation ITU-T Y.1901 (2008), *Requirement for the support of IPTV services.* +- [ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture.* + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 aggregation function** [ITU-T H.741.0]: The function that configure audience management functions (AMFs), then receives processed events, sample values and end-user information from AMFs. It may participate in the communication of end-user permissions. +- 3.1.2 application** [b-ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services. +- 3.1.3 application event** [b-ITU-T H.740]: An application event is every end-user interaction or occurrence related with multimedia contents in IPTV applications. It includes an emergency event from event notification services +- 3.1.4 audience measurement** [ITU-T H.741.0]: The measurement of people's engagement with IPTV services. +- 3.1.5 audience measurement data** [ITU-T H.741.0]: End-user behaviour data which is related to a service and content consumption, combined or not with end-user information. +- 3.1.6 audience measurement function (AMF)** [ITU-T H.741.0]: The function that, if given permission, measures the end-user behaviour by processing events or samples from IPTV services. + +AMFs may request and collect end-user information. AMFs transfer processed events, samples and end-user information to aggregation functions. + +**3.1.7 content provider** [ITU-T Y.1910]: The entity that owns or is licensed to sell content or content assets. + +**3.1.8 delivery** [ITU-T Y.1910]: In the context of IPTV architecture, "delivery" is defined as sending contents to the end user. + +**3.1.9 digital signage** [b-ITU-T H.780]: A system that sends information, advertising and other messages to electronic devices (e.g., displays, speakers) in accordance with the time of day and the location of the display, or the actions of audience. Contents and their relevant information, such as display schedules, are delivered over networks. + +**3.1.10 end user** [ITU-T Y.1910]: The actual user of the products or services. + +NOTE – The end user consumes the product or service. An end user can optionally be a subscriber. + +**3.1.11 IPTV** [ITU-T Y.1901]: Multimedia services such as television/video/audio/text/graphics/data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. + +**3.1.12 metadata** [ITU-T Y.1901]: Structured, encoded data that describe characteristics of information-bearing entities to aid in the identification, discovery, assessment, and management of the described entities. + +NOTE – EPG metadata has many applications and may vary in depth from merely identifying the content package title or information to populate an EPG to providing a complete index of different scenes in a movie or providing business rules detailing how the content package may be displayed, copied, or sold. + +**3.2.13 network provider** [ITU-T Y.1910]: The organization that maintains and operates the network components required for IPTV functionality. + +NOTE 1 – A network provider can optionally also act as service provider. + +NOTE 2 – Although considered as two separate entities, the service provider and the network provider can optionally be one organizational entity. + +**3.1.14 privacy** [b-ITU-T X.800]: The right of individuals to control or influence what information related to them may be collected and stored and by whom and to whom that information may be disclosed. + +NOTE – Because this term relates to the right of individuals, it cannot be very precise and its use should be avoided except as a motivation for requiring security. + +**3.1.15 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications. + +**3.1.16 service provider** [b-ITU-T M.1400]: A general reference to an operator that provides telecommunication services to customers and other end users either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. + +### **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 video data:** A set of digital images captured by a camera. A digital image is a numeric representation of a two-dimensional image. + +**3.2.2 video sensor:** A device that has image processing ability, such as image compression, image manipulation with the video data captured by a camera. A video sensor can generate video sensor information alone, by processing video data when it has enough computational power. Otherwise, some functions of the video sensor are processed through external systems and the video sensor generates intermediate video sensor information. + +**3.2.3 video sensor information:** Extracted and derived information from video data, for example, emotion, number, gender, and age of persons, or movement. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------| +| AMF | Audience measurement function | +| EPG | Electronic program guide | +| IP | Internet protocol | +| IPTV | Internet protocol television | +| QoE | Quality of experience | +| QoS | Quality of service | +| SP | Service provider | +| STB | Set-top box | +| TV | Television | +| UVS | Use of video sensor devices | +| VSI | Video sensor information | +| WAN | Wide area network | + +## 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended, but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. +- The keyword "functions" are defined as a collection of functionalities. It is represented by the following symbol in the context of IPTV architecture: + +![A rounded rectangular box containing the word 'Functions'.](f5aaecb6473222e3d65f65164fab048e_img.jpg) + +A rounded rectangular box with a black border, containing the word "Functions" centered inside it. + +A rounded rectangular box containing the word 'Functions'. + +- The keyword "functional block" is defined as a group of functionalities that has not been further subdivided at the level of detail described in this Recommendation. It is represented by the following symbol in the context of IPTV architecture: + +![A rectangular box containing the words 'Functional Block'.](b7c99649d8de39a814e0bad989d50b12_img.jpg) + +A rectangular box with a black border, containing the words "Functional Block" centered inside it, with "Functional" on the first line and "Block" on the second line. + +A rectangular box containing the words 'Functional Block'. + +NOTE – In the future, other groups or other Recommendations may possibly further subdivide these functional blocks. + +Requirements in clauses 8, 9 and 10 are identified using the following conventions [ITU-T Y.1901]: + +- Mandatory requirement is identified to R; +- Recommended requirement is identified to RR; +- Optional requirement is identified to OR. + +## 6 Overview + +A video sensor is a device used by technology to extract useful information, for example, the number, gender, and age of persons in front of camera, by processing video data captured by camera. + +Through the use of this technology with digital signage system, information about how an audience watches the display can be extracted. It means the effect of the digital signage system can be measured. On the other hand, through the use of this technology with IPTV terminal devices, information on whether or not persons are watching TV can be extracted in the IPTV terminal device side. If home gateway implements the aggregation function of this information, it can collect this information from several IPTV terminal devices and may show their situations on the other terminal screen. For example, a family member may switch off the TV so that nobody can watch it in order to reduce the consumption of electric energy. + +Information, such as end-user presence in front of TV or end-user properties extracted by sensor information is useful for advanced services. However, as this additional information is more detailed personal private information than simple operational histories in audience measurement, it must be treated very carefully by the advanced service system and persons who are working with this service or system. Without careful handling of this information, private information will be stolen, extracted or opened and there may be a risk of serious misuse of private information. + +While the spread of IPTV services across the world, new services based on the above additional information may be developed and spread. Before spreading such services, it is necessary to clarify the risk of privacy infringement, and ensure that this is understood by IPTV service providers, implementers and end-users; also, it is necessary to implement the technologies to avoid such risks. If such technologies will not be implemented and privacy infringement may occur, IPTV services themselves may be viewed as dangerous services where privacy protection is concerned. As a result, the number of IPTV service subscribers may be reduced. + +To mitigate such risk, this Recommendation describes the requirements of IPTV application events extracted by video sensor devices. + +## 7 Domain and architecture + +Figure 7-1 shows the main domains that are involved in the provision of IPTV service with video sensor devices based on [ITU-T Y.1910]. These domains do not define a business model. These domains do not mean video data captured by camera devices are delivered to out of home without permission. This decomposition does not preclude that one provider be involved in the support of any given IPTV service across more than one domain. + +![Diagram of IPTV domains with video sensor devices. The diagram is divided into four vertical panels: End-user, Network provider, Service provider, and Content provider. The End-user panel shows a computer monitor, a set-top box, and a video camera. The Network provider panel shows a router and a server. The Service provider panel shows a server and a globe icon. The Content provider panel shows a globe icon and a stack of documents. A horizontal line connects the panels. The text 'H.742.0(16)_F7-1' is in the bottom right corner.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Diagram of IPTV domains with video sensor devices. The diagram is divided into four vertical panels: End-user, Network provider, Service provider, and Content provider. The End-user panel shows a computer monitor, a set-top box, and a video camera. The Network provider panel shows a router and a server. The Service provider panel shows a server and a globe icon. The Content provider panel shows a globe icon and a stack of documents. A horizontal line connects the panels. The text 'H.742.0(16)\_F7-1' is in the bottom right corner. + +**Figure 7-1 – IPTV domains with video sensor devices** + +Figure 7-2 provides an overview of the IPTV functional architecture with video sensor devices. Functions and functional blocks described in this clause are common to all architectural approaches as detailed in [ITU-T Y.1910] except where stated differently. + +The key applicable concepts are described below and indicated in red in Figure 7-2: + +- The video sensor device functional block in application client functions is added as one of other client functional blocks in [ITU-T Y.1910]. +- In the home network functions in [ITU-T Y.1910], Video Sensor Home Network Functional block is added. +- In the application functions, Video Sensor Application Functional Block is added as one of IPTV application functions in [ITU-T Y.1910]. +- Terminal Device Audience Measurement Functions in application client functions are added as one of other functions in [ITU-T Y.1910]. +- In the application functions, Aggregation Functions are added as one of IPTV application functions in [ITU-T Y.1910]. + +![IPTV video sensor device architectural overview diagram showing functional blocks for Application client functions, IPTV terminal functions, Home network functions, Application functions, Service control functions, Content delivery functions, Network functions, Management functions, and Content provider functions.](d4af765160d04ecef538e5066006dc77_img.jpg) + +The diagram illustrates the IPTV video sensor device architectural overview, organized into several functional blocks: + +- End-user functions (Pink background):** + - Application client functions:** Service and application discovery and selection client functional block, Linear TV client functional block, On demand client functional block, Video sensor client functional block, Terminal device audience measurement functions, Other client functional block(s). + - IPTV terminal functions:** SCP client functions, Client delivery client functions, Control client functional block. + - Home network functions:** Video sensor home network functional block, Delivery network gateway functional block. +- Application functions (Light blue background):** Video sensor application functional block, Aggregation functions. +- Service control functions (Yellow background)** and **Content delivery functions (Orange background)** are positioned centrally. +- Network functions (Green background)** are located at the bottom center. +- Management functions (Grey background)** and **Content provider functions (Grey background)** are located on the right side. + +Connections are shown between the Application client functions and the Application functions, and between the IPTV terminal functions and the Service control functions. + +H.742.0(16)\_F7-2 + +IPTV video sensor device architectural overview diagram showing functional blocks for Application client functions, IPTV terminal functions, Home network functions, Application functions, Service control functions, Content delivery functions, Network functions, Management functions, and Content provider functions. + +**Figure 7-2 – IPTV video sensor device architectural overview** + +## 8 Requirements of application event by video sensor device + +### 8.1 Risks related to IPTV terminal devices used with video sensor device + +The following are the privacy infringement risks: + +- Software errors or virus in the IPTV terminal device with video sensor device may deliver not only extracted information but also the video image itself captured by a camera to the other servers. +- Software errors or virus in the home gateway [b-ITU-T H.622.1] device that controls IPTV terminal device with video sensor device may order it to deliver not only extracted information, but also the video image itself captured by a camera to the other servers. + +If the destination of the above-mentioned data is the server in WAN and it was designed by privacy brokers, the captured video data may be flowed and used for crime and so on. + +### 8.2 Requirements for avoiding the risks of privacy infringement + +It is required that end-users understand the risks of privacy infringement and that they allow the use of their privacy information in order for IPTV architecture to measure the video sensor-based information. (R-1) + +- IPTV terminal devices with video sensor are required to implement functions that avoid delivering data other than the prior designed format. (R-2) + +- The server that collects the information extracted by the video sensor device is required to implement functions that avoid receiving data other than the prior designed format. (R-3) + +## **9 Functional requirements** + +### **9.1 Video processing functional requirement** + +- Video sensors are required to capture the video and output the result of video processing in real-time. It is not necessary to output the result as the same frame rate of video capture. (R-4) + +### **9.2 Terminal authentication functional requirement** + +- Video sensors are required to be authenticated by authentication server for IPTV services. (R-5) +- Video sensors are required to be related with users of IPTV services. (R-6) + +### **9.3 Data output functional requirement** + +- Video sensors are required to output the data in accordance with clause 10. (R-7) + +### **9.4 Transmission functional requirement** + +- Video sensors are required to transmit data as IP data transmission via wired networks or wireless networks. (R-8) + +### **9.5 Data storage functional requirement** + +- If video sensors store the video data or VSI, video sensor must not store the video data that are able to identify the captured user. (R-9) + +### **9.6 Service subscribing functional requirement** + +- Video sensors are required to be equipped with the functionality to change the IPTV services that are to be connected. (R-10) + +### **9.7 Security functional requirement** + +- Video sensors are required not to transmit the data that are able to identify the user captured. (R-11) +- The transmitted data are required to be secured. (R-12) +- Video sensors are required to be equipped with the functionality to stop the function to turn on/off through the remote site. (R-13) +- Video sensors are required to be equipped with the functionality to turn themselves on/off. (R-14) + +### **9.8 Metadata functional requirement** + +- Video sensors are required to deliver metadata that describe VSI. VSI metadata are recommended to be in conformance with audience measurement metadata structure [ITU-T H.741.2]. (R-15) + +## **10 Requirements for the delivery of audience measurement data with video sensors** + +As VSI comprises personal data, video sensor home network functional block (VSHN) must not deliver VSI to outside of home network as a default and must be controlled securely based on the following requirements. + +- It is required that VSHN not deliver VSI to outside of home network without the user's permissions. (R-16) + +- It is required that VSHN be equipped with the functions to register VSs that deliver VSI to outside of home network, and to set permission for the delivery of VSI to outside of home network. (R-17) +- It is required that VSHN be equipped with the function to terminate the communication to deliver VSI to outside of home network by unregistered video sensor devices or video sensor devices without permissions. (R-18) +- It is required that VSHN be equipped with the function to encrypt the communication to deliver VSI to outside of home network. (R-19) + +## Appendix I + +### Video sensor devices event scenario + +(This appendix does not form an integral part of this Recommendation.) + +A video sensor is a device used to generate useful information, for example, the emotion, number, gender, and age of persons, or movement, by processing video data captured by a camera. By combining this device with IPTV terminal devices, IPTV terminal devices can, for example, recognize the state and attributes of the end-user. + +If the end-user permits the collection of such information for use by the sensor server functions, this information is useful for new IPTV services, such as user-specific advertisement, interactive programs. For example, gender information may be useful for gender-specific advertisement to users and motion and gesture recognition, as well as for collecting user response for questionnaires or quizzes (Figure I.1). + +Regarding home use, if an application on the home gateway implements the sensor server functions, tablet terminals, for example, connected with such sensor server functions may show the information on whether end-users are watching TV or not, by counting the number of people watching (Figure I.2). Turning TV sets off whenever they are not being watched is useful for electrical energy management. This application must not deliver the information to outside-of-the-home network without the end-user's permission. + +VSI is not video information, but video-derived information. VSI is private information that is more sensitive than audience measurement based on usage histories of IPTV services. Therefore, it must be treated more securely. Without secure handling of this information, private information will be stolen, extracted or opened and there may be a risk of serious misuse of private information. The following items must be studied: + +- Standardizing metadata between IPTV terminal devices measuring the additional information and the servers aggregating it; +- Clarifying the risks attendant on the processing of the additional information; +- Requirements and functions for avoiding the risks of privacy infringement. + +![Figure I.1: Video sensor device event scenario for audience measurement or bi-directional program. The diagram shows an IPTV PF (Contents delivery PF and Video sensor server) connected to a cloud, which is connected to a Home gateway. The Home gateway is connected to an STB + video sensor (displaying a movie) and a TV + video sensor (displaying a landscape). A Tablet terminal shows 'TV status' with 'Living room: 3' and 'Bedroom: 0'. A callout box states 'Without permission any video sensor outputs must not deliver to outer NW'. A legend indicates: dashed arrow for 'Permission for collecting video sensor outputs. (e.g., audience measurement/participation in bi-directional programme)' and solid arrow for 'Video sensor info if end-user permitted.' The diagram is labeled H.742.0(16)_FI.1.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure I.1: Video sensor device event scenario for audience measurement or bi-directional program. The diagram shows an IPTV PF (Contents delivery PF and Video sensor server) connected to a cloud, which is connected to a Home gateway. The Home gateway is connected to an STB + video sensor (displaying a movie) and a TV + video sensor (displaying a landscape). A Tablet terminal shows 'TV status' with 'Living room: 3' and 'Bedroom: 0'. A callout box states 'Without permission any video sensor outputs must not deliver to outer NW'. A legend indicates: dashed arrow for 'Permission for collecting video sensor outputs. (e.g., audience measurement/participation in bi-directional programme)' and solid arrow for 'Video sensor info if end-user permitted.' The diagram is labeled H.742.0(16)\_FI.1. + +**Figure I.1 – Video sensor device event scenario for audience measurement or bi-directional program** + +![Figure I.2: Video sensor device event scenario for in-house electrical energy management. The diagram shows an IPTV PF (Contents delivery PF and Video sensor server) connected to a cloud, which is connected to a Home gateway. The Home gateway is connected to an STB + video sensor (displaying a movie) and a TV + video sensor (displaying a landscape). A Tablet terminal shows 'TV status' with 'Living room: 3' and 'Bedroom: 0'. A callout box states 'Without permission any video sensor outputs must not deliver to outer NW'. A legend indicates: dashed arrow for 'Video sensor information for home network use'. The diagram is labeled H.742.0(16)_FI.2.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +Figure I.2: Video sensor device event scenario for in-house electrical energy management. The diagram shows an IPTV PF (Contents delivery PF and Video sensor server) connected to a cloud, which is connected to a Home gateway. The Home gateway is connected to an STB + video sensor (displaying a movie) and a TV + video sensor (displaying a landscape). A Tablet terminal shows 'TV status' with 'Living room: 3' and 'Bedroom: 0'. A callout box states 'Without permission any video sensor outputs must not deliver to outer NW'. A legend indicates: dashed arrow for 'Video sensor information for home network use'. The diagram is labeled H.742.0(16)\_FI.2. + +**Figure I.2 – Video sensor device event scenario for in-house electrical energy management** + +## Appendix II + +### Video sensor information generation scenario + +(This appendix does not form an integral part of this Recommendation.) + +It is difficult to generate VSI by a video sensor client alone when the video sensor client has limited computational ability. In this case, the video sensor server may generate VSI with the video sensor client. Depending on the situation, all analysis may be processed by video sensor server alone. + +The above-mentioned cases require not only more careful handling of data, but also the acquisition of the highest level of permission from end-users. Also, it is desired that video sensor server discards the received data, such as original video data or data that are not full analysed, immediately after completing the generation of the VSI to prevent data leakage. + +Overload can occur in the network and server if the video sensor client itself transmits video data to the video sensor server and the video sensor server takes charge of all video data analysis processes that generates VSI (see Figure II.2). Thus, the proper selection about transmission cycle of video data and data encoding should be made. + +If some computational ability of video sensor clients can be used, it can reduce the load of video sensor servers. The video sensor client first performs the task to generate intermediate data, which will be processed by the video sensor server, then the video sensor server generates the final VSI (see Figure II.3). For example, when the video sensor generates binary pixel data and sends them to the video sensor server, the transmission data size is reduced and the VSI is generated with lower load than when the original video data was transmitted. + +Besides, technologies such as difference image extraction and feature detection can be flexibly applied depending on the performance of the video sensor client and the video sensor server. + +![Figure II.1: Video sensor information generation scenario when video sensor clients generate video sensor information only. The diagram shows a flow from an End-user (represented by a camera icon) through a series of functions: Video sensor functions, Video process function, and VSI. Gen. function. These lead to Audience measurement client functions. Simultaneously, Video sensor information (e.g., emotion, number, gender, age, movement) is sent from the Video sensor functions to the Service provider's Video sensor server functions. The Video sensor server functions then send AM messages to the Audience measurement client functions. A dashed box labeled IPTV contents delivery PF is also shown. Above the diagram, a color-coded bar identifies the roles: End-user (red), Network provider (blue), Service provider (green), and Content provider (yellow).](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +The diagram illustrates the flow of information in a video sensor information generation scenario. At the top, a color-coded bar identifies four roles: End-user (red), Network provider (blue), Service provider (green), and Content provider (yellow). Below this, the flow starts with an End-user (represented by a camera icon) connected to a box containing three stacked functions: 'Video sensor functions', 'Video process function', and 'VSI. Gen. function'. An arrow points from 'Video sensor functions' to 'Video sensor server functions' (located under Service provider) with the label 'Video sensor information (e.g., emotion, number, gender, age, movement)'. Another arrow points from 'VSI. Gen. function' down to 'Audience measurement client functions'. From 'Audience measurement client functions', an arrow points to 'Aggregation functions' (located under Service provider) with the label 'AM messages'. A dashed box labeled 'IPTV contents delivery PF' is shown to the right of the 'Video sensor server functions'. + +Figure II.1: Video sensor information generation scenario when video sensor clients generate video sensor information only. The diagram shows a flow from an End-user (represented by a camera icon) through a series of functions: Video sensor functions, Video process function, and VSI. Gen. function. These lead to Audience measurement client functions. Simultaneously, Video sensor information (e.g., emotion, number, gender, age, movement) is sent from the Video sensor functions to the Service provider's Video sensor server functions. The Video sensor server functions then send AM messages to the Audience measurement client functions. A dashed box labeled IPTV contents delivery PF is also shown. Above the diagram, a color-coded bar identifies the roles: End-user (red), Network provider (blue), Service provider (green), and Content provider (yellow). + +Figure II.1 – Video sensor information generation scenario when video sensor clients generate video sensor information only + +![Figure II.2: Video sensor information scenario when video sensor servers generate video sensor information only. The diagram shows a flow from End-user (Video sensor functions: Video encoding) to Service provider (Video sensor server functions: Video process function, VSI. Gen. function) via Video data. The Service provider then sends AM messages to Audience measurement client functions. IPTV contents delivery PF is shown as a dashed box.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +The diagram illustrates the flow of video data and sensor information. At the top, a horizontal bar identifies four roles: End-user (red), Network provider (blue), Service provider (green), and Content provider (yellow). Below this, the End-user's Video sensor functions, which include Video encoding, send Video data (represented by a small image thumbnail) to the Service provider's Video sensor server functions. These server functions consist of a Video process function and a VSI. Gen. function. The Service provider then sends AM messages to the Audience measurement client functions. A dashed box on the right represents the IPTV contents delivery PF. + +Figure II.2: Video sensor information scenario when video sensor servers generate video sensor information only. The diagram shows a flow from End-user (Video sensor functions: Video encoding) to Service provider (Video sensor server functions: Video process function, VSI. Gen. function) via Video data. The Service provider then sends AM messages to Audience measurement client functions. IPTV contents delivery PF is shown as a dashed box. + +H.742.0(16)\_FII.2 + +**Figure II.2 – Video sensor information scenario when video sensor servers generate video sensor information only** + +![Figure II.3: Video sensor information generation scenario when video sensor servers generate video sensor information with video sensor clients. The diagram shows a flow from End-user (Video sensor functions: Video process function, Video encoding) to Service provider (Video sensor server functions: VSI Gen. function) via Processed video data (e.g., Binarized image, Difference image). The Service provider then sends AM messages to Audience measurement client functions. IPTV contents delivery PF is shown as a dashed box.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +This diagram shows a different scenario where the End-user's Video sensor functions (Video process function and Video encoding) send Processed video data (e.g., Binarized image, Difference image) to the Service provider's Video sensor server functions (VSI Gen. function). The Service provider then sends AM messages to the Audience measurement client functions. A dashed box on the right represents the IPTV contents delivery PF. + +Figure II.3: Video sensor information generation scenario when video sensor servers generate video sensor information with video sensor clients. The diagram shows a flow from End-user (Video sensor functions: Video process function, Video encoding) to Service provider (Video sensor server functions: VSI Gen. function) via Processed video data (e.g., Binarized image, Difference image). The Service provider then sends AM messages to Audience measurement client functions. IPTV contents delivery PF is shown as a dashed box. + +H.742.0(16)\_FII.3 + +**Figure II.3 – Video sensor information generation scenario when video sensor servers generate video sensor information with video sensor clients** + +## Appendix III + +### Use cases of video sensor information + +(This appendix does not form an integral part of this Recommendation.) + +### III.1 Targeted advertising service + +#### III.1.1 Overview + +Existing targeted advertising for IPTV is mostly serviced based on location and demographic information. As a result, its preciseness is lower than mobile advertisement, which has constant users. Therefore, more precise targeted advertising service can be provided to advertisers and viewers if VSI is used. + +Generally, advertisements are included when the user selects free VOD content in IPTV. In this case, the video sensor generates VSI which can distinguish the number of users and the part they play through inputting the content selection signal. Using this information, the video sensor is able to supply the advertisements which meets the user's preferences. For example, whenever mothers and fathers are viewing, vehicle and shoes advertisements, respectively, will be provided and if whole family is a viewer, pizza advertisement can be provided. + +VSI has a different destination depending on the targeted advertising management method. If advertisement lists or files are saved in the IPTV terminal, VSI will be used in the IPTV terminal only since advertisements shown should be determined by IPTV terminal. On the other hand, if final discretion is not on the IPTV terminal, VSI will be delivered to the external advertising operator who organizes advertisement dynamically. + +![Diagram illustrating targeted advertising services based on user demographics detected by a TV video sensor.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +The diagram shows a central 'TV + video sensor' unit at the top. To its right is a box labeled 'Targeted advertising'. Below the TV, three dashed lines point to different users, each associated with a specific advertisement icon and label: 'Dad' (represented by a man icon) receives 'Car Ad.' (represented by a red car icon); 'Mom' (represented by a woman icon) receives 'Shoes Ad.' (represented by high-heeled shoes icon); and 'Kid' (represented by a child icon) receives 'Toy Ad.' (represented by an airplane icon). The text 'H.742.0(16)\_FIII.1' is located at the bottom right of the diagram. + +Diagram illustrating targeted advertising services based on user demographics detected by a TV video sensor. + +Figure III.1 – Targeted advertising services + +#### III.1.2 Problems to be solved + +- There are the occasions where advertisements are provided to viewers who advertisers do not want to target. For example, the effectiveness will be reduced in case of showing a sports car advertisement to the people in their eighties. +- In many cases, advertisement is exposed to the same viewer more often than the advertiser intended. + +- Teenagers can be exposed to harmful advertising, such as alcohol and tobacco. + +#### III.1.3 Potential benefits + +- Viewers can avoid tedious advertisements which do not relate to their interests as well as repeating advertisements. +- It can protect minors from harmful advertising. +- Advertisers can expose intended viewers to advertising efficiently. +- It can support IPTV advertising business by improving the accuracy of targeted advertising. + +#### III.1.4 Requirements + +- Permission for the range of VSI related to targeted advertising service provided should be secured. +- In case there is no entry from viewers for instance mid-advertisement, the video sensor should be provided with information about advertisement exposure time in order to enable targeted advertising. +- VSI generation time should not exceed the planned time frame. + +#### III.1.5 Relevant standardization + +- VSI metadata is recommended to be in conformance with audience measurement metadata structure [ITU-T H.741.2]. + +### III.2 Personalized screen service + +#### III.2.1 Overview + +Most of the conventional IPTV provides the identical menu screen with identical initial screen and channel guide, and there can also be a cumbersome login procedure if a distinctive menu can be set by user. Therefore, if actual VSI viewer information is used, a screen customized by the viewer can be provided without any extra login procedure. + +![Diagram illustrating the personalized screen service based on UVS. A TV with a video sensor is at the top, connected by dashed lines to a central box labeled 'Providing personalized screen'. From this box, three dashed lines point to three different personalized screen examples, each associated with a user icon: Dad, Mom, and Kid. The Dad's screen shows a news program, a weather forecast, and a landscape. The Mom's screen shows a fashion show, a cooking show, and a news program. The Kid's screen shows a cartoon, a game, and a children's show.](552ca016af3d6240648ab5a2cad97f60_img.jpg) + +The diagram illustrates the personalized screen service based on UVS. At the top, a TV with a video sensor is shown. Below it, a central box labeled "Providing personalized screen" is connected to three different personalized screen examples, each associated with a user icon: Dad, Mom, and Kid. The Dad's screen shows a news program, a weather forecast, and a landscape. The Mom's screen shows a fashion show, a cooking show, and a news program. The Kid's screen shows a cartoon, a game, and a children's show. The text "H.742.0(16)\_FIII.2" is visible in the bottom right corner of the diagram. + +Diagram illustrating the personalized screen service based on UVS. A TV with a video sensor is at the top, connected by dashed lines to a central box labeled 'Providing personalized screen'. From this box, three dashed lines point to three different personalized screen examples, each associated with a user icon: Dad, Mom, and Kid. The Dad's screen shows a news program, a weather forecast, and a landscape. The Mom's screen shows a fashion show, a cooking show, and a news program. The Kid's screen shows a cartoon, a game, and a children's show. + +Figure III.2 – Personalized screen based on UVS + +For example, whenever the father presses the initial screen button, news and sports content will be listed and activated; any additional information will be related to traffic conditions and the stock market. In the case of the mother, drama and films will be recommended; any activated additional information will be related to shopping and food. If screen service is linked with personal mobile devices, it will be able to access different personal menu screens while identical content is streamed through the TV screen. Also, other IPTVs in the home can provide a personalized menu screen. VSI does not require transmitting externally since it is used only in IPTV terminal. + +#### III.2.2 Problems to be solved + +- In many cases, viewers do not receive preferred recommendation lists or additional information. +- Login procedure using a remote control is inconvenient and it also requires considerable time. + +#### III.2.3 Potential benefits + +- The user can access personalized screen service through simple user interface, such as a video sensor. +- IPTV business can expect revenue increase related to content and advertising consumption by providing personally customized information. + +#### III.2.4 Requirements + +- When providing personalized screen service through TV only, there should be a screen control algorithm for instance of multiple viewers. +- Default screen should be provided in case of error in the video sensor. + +#### III.2.5 Relevant standardization + +- When personalized screen service is provided through a secondary terminal, it can be related to multi-screen or second screen standardization. + +### III.3 IPTV ratings analysis service + +#### III.3.1 Overview + +Generally, ratings analysis has been based on remote control information analysis with TV device units rather than on personal use due to the characteristics of TVs which are viewed by multiple individuals. For example, if certain content is on four TVs among ten, rating may be estimated as 40%. In the case of advertising content, rating indicators would not yet be fixed and advertising expenses would be fixed proportional to TV ratings. + +![Diagram of IPTV ratings analysis service showing data flow from a TV with a video sensor to a cloud, then to a server, and finally to a graph showing ratings for TV content and ad content.](35127fe87029df6f5f0b2ee85f6193f1_img.jpg) + +The diagram illustrates the IPTV ratings analysis service. On the right, a TV with a video sensor is shown, with a label 'The number of viewers: 3' above it. A dashed blue arrow points from the TV to a cloud icon. From the cloud, a dashed blue arrow points to a server icon (a cylinder). Above the server is a box labeled 'Ratings measurement'. From the server, a dashed blue arrow points to a line graph titled 'Heroes' Viewship'. The graph has a y-axis labeled 'Viewship' and an x-axis labeled 'Spots'. The legend indicates two data series: 'TV content' (blue line) and 'Ad. content' (red line). The blue line shows a peak around spot 10, while the red line shows a more gradual decline. The text 'H.742.0(16)\_FIII.3' is in the bottom right corner. + +Diagram of IPTV ratings analysis service showing data flow from a TV with a video sensor to a cloud, then to a server, and finally to a graph showing ratings for TV content and ad content. + +Figure III.3 – IPTV ratings analysis service + +If a video sensor is used, ratings for personal unit as well as advertising content can be measured since the sensor can detect the number of viewers relatively precisely in a short time whenever content is exposed. For example, when assuming that four family members are watching content A and two family members are watching content B, rating will be same if the previous method was used. However, the A content ratings will be higher if detected viewer information is applied. Advertising content ratings can be measured by the same method as broadcasting content if the number of viewers is detected for a certain time during the short exposure time. + +#### **III.3.2 Problems to be solved** + +- Advertisement ratings analysis is difficult to measure and accuracy is less compared to broadcasting ratings analysis. +- It is difficult to determine the number of viewers in ratings analysis based on device unit. + +#### **III.3.3 Potential benefits** + +- The number of viewers can be estimated quite precisely since ratings analysis provides information at the individual user level. +- The video sensor is able to estimate the number of viewers who are exposed to advertising content in addition to ratings. + +#### **III.3.4 Requirements** + +- Preliminary permission from viewers for ratings analysis is required. +- At least one VSI generation should be enabled within the total advertisement content exposure time. + +#### **III.3.5 Relevant standardization** + +- VSI metadata is recommended to be in conformance with audience measurement metadata structure [ITU-T H.741.2] + +## Bibliography + +- [b-ITU-T H.622.1] Recommendation ITU-T H.622.1 (2008), *Architecture and functional requirements for home networks supporting IPTV services.* +- [b-ITU-T H.740] Recommendation ITU-T H.740 (2010), *Application event handling for IPTV services* and its Amendment 1 (2011). +- [b-ITU-T H.780] Recommendation ITU-T H.780 (2012), *Digital signage: Service requirements and IPTV-based architecture.* +- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2015), *Designations for interconnections among operators' networks.* +- [b-ITU-T X.800] Recommendation X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications.* +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.* + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including telecommunication network management and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..288d18fc1f2fc6e431ecfceb534094bf072195b2 --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e304f283a3f95515298b29cd414ca642ccb2767592326b621bbd873a3b92866d +size 43550 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f77e1301e65a2057f1be52d11acf753aef4d594 --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69996d2de13b3bcd3d6751a6123445762469a89563a6d5b7511d0baa102d468e +size 13152 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf1d6706867d0847ec69f77aa06ef877758512ac --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3727b5fbc99e54d825f017f1bc3a02955a095bd1579ba68b9bd34848e6b17992 +size 130500 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a827e101fb59175c210a53ed9907249a53ed128c --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68af59db026101092553838faf59a26153a283984821d6908a91763e24b51d8c +size 162646 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/ac31fdfebb9751f7f10416dfe33bc872_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/ac31fdfebb9751f7f10416dfe33bc872_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ca209844276bbb25ded0cfc67302819316e2603 --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/ac31fdfebb9751f7f10416dfe33bc872_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4aeda44d343bc4555367bb71884316b8dc41705a64e835660ab7cfbbe5ef1c2c +size 103583 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c835c5bbf3f834c5d11060dbc9f6506bfadf5e35 --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdd1c1abb0cbabb24416f2e83537a44970c4905660c6edca8a702ec755521371 +size 34942 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5826b863a8b47d1f3147d99735072d08d9760e8 --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09b6eda590a682c3db396b154ac8b585d34e58b94867722999bde1d3b569ce20 +size 37435 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6886f0a54e7455730da176c4ba1dfe0b67540d4f --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2eeec874775c9ba8d6abbee42b81bba36571cc18b92f286a7ba23543a0da244f +size 156625 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg b/marked/H/T-REC-H.753-201911-I_PDF-E/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afc418a16b71d0994960bdeec51f4bda339c9fa6 --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:876fd86d032b4f1146ede8c8f672ed37631946677e2699e931b4814c5f29f2a4 +size 96518 diff --git a/marked/H/T-REC-H.753-201911-I_PDF-E/raw.md b/marked/H/T-REC-H.753-201911-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bc77757e9e143a917f7c15d5c3bb6c125b740000 --- /dev/null +++ b/marked/H/T-REC-H.753-201911-I_PDF-E/raw.md @@ -0,0 +1,2456 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.753** + +(11/2019) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +IPTV metadata + +# --- **Scene-based metadata for IPTV services** + +Recommendation ITU-T H.753 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font, with "ITU" in a larger, bold font above it. + +ITU logo + +International +Telecommunication +Union + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.753 + +# Scene-based metadata for IPTV services + +## Summary + +Recommendation ITU-T H.753 defines the metadata element and format for content distribution over an Internet protocol television (IPTV) terminal device and describes metadata management functions of scene-based metadata (SBM), which basically support the IPTV multimedia application frameworks that feature in the ITU-T H.760 series of Recommendations. + +Scene-based metadata is based on ITU-T IPTV functional architecture and terminal devices defined in the ITU-T H.720-series and on services defined in Recommendation ITU-T H.750. + +Recommendation ITU-T H.753 also describes the web-based functions for scene-based metadata service and the scene-based service workflow. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.753 | 2019-11-29 | 16 | 11.1002/1000/14112 | + +## Keywords + +IPTV, metadata, SBM, scene, scene-based metadata. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|--------------|-----------------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 3 | +| 6 | Introduction..... | 4 | +| 7 | Scene-based metadata ..... | 7 | +| 7.1 | Content description model..... | 7 | +| 7.2 | Data types for scene-based metadata ..... | 8 | +| 8 | SBM elements and format ..... | 9 | +| 8.1 | Scene-based metadata (SBM) for basic elements ..... | 9 | +| 8.2 | Scene-based metadata (SBM) for location elements ..... | 12 | +| 8.3 | Scene-based metadata (SBM) for music elements ..... | 12 | +| 8.4 | Scene-based metadata (SBM) for object elements ..... | 13 | +| 8.5 | Scene-based metadata (SBM) for statistics elements ..... | 14 | +| 9 | SBM management functions..... | 14 | +| 9.1 | Basic scene information functions..... | 15 | +| 9.2 | Location information functions ..... | 26 | +| 9.3 | Music information functions ..... | 26 | +| 9.4 | Object information functions..... | 27 | +| 9.5 | Statistics information functions ..... | 28 | +| Appendix I | – Examples of SBM for IPTV overall workflow with Recommendation ITU-T H.753 ..... | 29 | +| I.1 | Use case 1: Scene-based VOD clip service workflow ..... | 29 | +| I.2 | Use case 2: Scene-based additional service workflow ..... | 29 | +| Appendix II | – An example of web-based APIs for scene-based metadata service..... | 31 | +| II.1 | Basic scene information functions..... | 31 | +| II.2 | Location information functions ..... | 43 | +| II.3 | Music information functions ..... | 43 | +| II.4 | Object information functions..... | 44 | +| II.5 | Statistics information functions ..... | 45 | +| Appendix III | – RSDL schema..... | 46 | +| Bibliography | ..... | 48 | + + + +# Recommendation ITU-T H.753 + +# Scene-based metadata for IPTV services + +# 1 Scope + +This Recommendation specifies scene-based metadata for Internet protocol television (IPTV) services. Scene-based metadata description, metadata elements and format for content distribution are specified. Furthermore, the high-level interface for scene-based metadata service is also described. + +The scope of this Recommendation includes: + +- Scene-based metadata (SBM) elements +- SBM functions and interface description +- Scenario of IPTV scene-based media service + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems*. +- [ITU-T H.750] Recommendation ITU-T H.750 (2008), *High-level specification of metadata for IPTV services*. +- [ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services*. +- [ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*. +- [IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifier (URI): Generic Syntax*. + +- [W3C XMLSchemaP2] W3C Recommendation (2004) *XML Schema Part 2: Datatypes Second Edition*. + + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 application** [b-ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services. +- 3.1.2 content provider** [ITU-T Y.1910]: The entity that owns or is licensed to sell content or content assets. +- 3.1.3 end-user** [ITU-T Y.1910]: The actual user of the products or services. + +NOTE – The end-user consumes the product or service. An end-user can optionally be a subscriber. + +**3.1.4 functional architecture** [b-ITU-T Y.2012]: A set of functional entities and the reference points between them used to describe the structure of an NGN. These functional entities are separated by reference points, and thus, they define the distribution of functions. + +**3.1.5 functional entity** [b-ITU-T Y.2012]: An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. + +**3.1.6 home network (HN)** [b-ITU-T H.622]: Home network is the collection of elements that process, manage, transport, and store information, thus enabling the connection and integration of multiple computing, control, monitoring, communication and entertainment devices in the home. + +**3.1.7 IPTV terminal device** [ITU-T Y.1901]: A terminal device which has ITF functionality, e.g., STB. + +**3.1.8 IPTV terminal function (ITF)** [ITU-T Y.1901]: The end-user function(s) associated with a) receiving and responding to network control channel messages regarding session set-up, maintenance, and tear-down, and b) receiving the content of an IP transport from the network and rendering. + +**3.1.9 linear TV** [ITU-T Y.1901]: A television service in which a continuous stream flows in real time from the service provider to the terminal device and where the user cannot control the temporal order in which contents are viewed. + +**3.1.10 metadata** [ITU-T Y.1901]: Structured, encoded data that describe characteristics of information-bearing entities to aid in the identification, discovery, assessment and management of the described entities. + +NOTE – EPG metadata has many applications and may vary in depth from merely identifying the content package title or information to populate an EPG to providing a complete index of different scenes in a movie or providing business rules detailing how the content package may be displayed, copied, or sold. + +**3.1.11 service provider** [b-ITU-T M.1400]: A general reference to an operator that provides telecommunication services to customers and other users either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may be a customer of another service provider. + +NOTE – Typically, the service provider acquires or licenses content from content providers and packages this into a service that is consumed by the end-user. + +**3.1.12 subscriber** [b-ITU-T M.3050.1]: The subscriber is responsible for concluding contracts for the services subscribed to and for paying for these services. + +**3.1.13 subtitles** [ITU-T Y.1901]: Subtitles provide a real-time on-screen transcript of dialogue for the purpose of language translation or to clarify speech that is unclear. + +NOTE – This service can be provided by means of either textual or graphical supplementary content. The subtitles and the dialogue are usually in different languages. The assumed audience for subtitling is hearing people who do not understand the language of the dialogue. + +**3.1.14 terminal device (TD)** [ITU-T Y.1901]: An end-user device which typically presents and/or processes the content, such as a personal computer, a computer peripheral, a mobile device, a TV set, a monitor, a VoIP terminal or an audio-visual media player. + +**3.1.15 video on demand (VoD)** [ITU-T Y.1901]: A service in which the end-user can, on demand, select and view a video content and where the end-user can control the temporal order in which the video content is viewed (e.g., the ability to start the viewing, pause, fast forward, rewind, etc.). + +NOTE – The viewing may occur some time after the selection of the video content. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 delivery:** In context of IPTV architecture, "delivery" is defined as sending contents to the end-user. + +**3.2.2 distribution:** In context of IPTV architecture, "distribution" is defined as sending the content to appropriate intermediate locations to enable subsequent delivery. + +**3.2.3 hybrid terminal device:** An IPTV terminal device that can also receive content from different types of transmission systems (e.g., terrestrial, satellite). + +**3.2.4 scene-on-demand (SoD):** A service in which the end-user can, on demand, select and view a scene of video content + +**3.2.5 metadata generator:** An entity generating metadata automatically using script, subtitles, crowdsourced information, and web information. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------------| +| API | Application Programming Interface | +| CDF | Content Delivery Function | +| DVB | Digital Video Broadcasting | +| EPG | Electronic Programme Guide | +| IP | Internet Protocol | +| IPTV | Internet Protocol Television | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| RSDL | RESTful Service Description Language | +| SBM | Scene-Based Metadata | +| SDF | Scene Delivery Function | +| SDCF | Scene Delivery Client Function | +| SoD | Scene on Demand | +| SSF | Scene Storage Function | +| TD | Terminal Device | +| XML | Extensible Mark-up Language | +| URL | Uniform Resource Locator | +| VOD | Video on Demand | + +# 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. + +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement needs not be present to claim conformance. +- The keywords "can optionally" and "may" indicate an optional requirement which is permissible, without implying any sense of being recommended. These terms are not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +# 6 Introduction + +Due to various smart media devices such as smartphones, tablets, Internet protocol television (IPTV) terminal devices and smart TVs, people have started to consume multimedia contents everywhere and at any time. + +Content providers hope that consumers will consume their own video contents more frequently in this environment. In addition, they want opportunities to provide additional services such as advertisements or a complementary information service. + +For example, there are people who only want to watch a scene where a given hero appears. Likewise there are people who want to see a collection of scenes related to a specific topic. Scene-based metadata for IPTV services can satisfy such a desire for such people. + +Scene-based metadata for IPTV services enables a user to receive various additional services by combining information including traditional IPTV services information. The scene-based metadata is able to provide an interactive video clip service or a related additional service by means of a story graph with a semantic clustering technique. Moreover, the scene-based metadata can provide new smart media services such as a media commerce and a context-aware advertising service by using the metadata extracted from a script, subtitles, or crowdsourced information. + +The definition of IPTV is described in [ITU-T Y.1901] as multimedia services such as television, video, audio, text, graphics and data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. The basic services such as broadcast services, on-demand services and portal services for IPTV are described in [ITU-T H.720]. In [ITU-T H.720] a broadcast service is called a linear TV service and an on-demand service is called a content on-demand service. + +Figure 1 shows the IPTV domains, described in [ITU-T H.720], where a content provider is defined as an entity that owns or is licensed to sell content or content assets; a service provider is defined as a general reference to an operator that provides telecommunication services to customers and other users either on a tariff or contract basis; a network provider is defined as the organization that maintains and operates the network components required for IPTV functionality; and an end-user is defined as the actual user of the products or services as described in [ITU-T Y.1901]. + +![Figure 1: IPTV domains diagram showing four domains: End-user, Network provider, Service provider, and Content provider connected in a linear sequence.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +The diagram illustrates the IPTV domains as defined in ITU-T Y.1910. It consists of four distinct domains connected in a linear sequence from left to right: + +- End-user:** Represented by an icon of a computer monitor and keyboard. +- Network provider:** Represented by an icon of a network switch and a server rack. +- Service provider:** Represented by an icon of a server rack and a globe. +- Content provider:** Represented by an icon of a globe and a film strip. + +The domains are connected by lines indicating the flow of data and services between them. + +Figure 1: IPTV domains diagram showing four domains: End-user, Network provider, Service provider, and Content provider connected in a linear sequence. + +H.753(19)\_F01 + +**Figure 1 – IPTV domains [ITU-T Y.1910]** + +Figure 2 shows the IPTV architectural overview, described in [ITU-T Y.1910]. Content provider functions provide the content and associated metadata to content preparation functions. High-level specification of metadata for IPTV services is described in [ITU-T H.750]. IPTV metadata is the information on services and content processed by the service and content delivery infrastructure, providing a descriptive and structural framework for managing IPTV services. The types of metadata for IPTV are service and content metadata, user metadata, metadata for content provisioning and management, metadata aggregation management, and rights and security related metadata. Content metadata is produced by content providers and service providers. Content providers typically supply title, synopsis, genre and other descriptive metadata about the content, while service providers assign the time of delivery, cost and other information about the service as described in [ITU-T H.750]. + +![Figure 2: IPTV architectural overview diagram showing functional blocks and their interactions across different layers.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +The diagram illustrates the IPTV architectural overview, showing the interaction between various functional blocks across different layers: + +- End-user functions (Pink):** + - Application client functions + - SCP client functions + - IPTV terminal functions + - Content delivery client functions + - Control client functional block + - Home network functions + - Delivery network gateway functional block +- Application functions (Blue):** + - IPTV application functions + - Application profile functional block + - Metadata + - Content preparation functions + - Control + - Content + - SCP functions +- Management functions (Grey):** + - Application management functional block + - Content and metadata + - Service control management functional block + - Content delivery management functional block + - End-user device management functional block + - Transport management functional block +- Content provider functions (Grey):** + - Content and metadata sources +- Service control functions (Yellow):** + - IPTV service control functional block + - Service user profile functional block +- Content delivery functions (Orange):** + - Content distribution and location control functions + - Content delivery and storage functions + - Content and control +- Network functions (Green):** + - Authentication and IP allocation functional block + - Resource control functional block + - Access network functions + - Edge functions + - Core transport functions + - Transport functions + +Key interactions and protocols shown: + +- Transaction protocol:** Between End-user functions and Application functions. +- Multicast delivery control protocol:** Between End-user functions and Network functions. +- Authentication and configuration protocol:** Between End-user functions and Network functions. +- Delivery protocols:** Between Service control functions and Content delivery functions. + +Figure 2: IPTV architectural overview diagram showing functional blocks and their interactions across different layers. + +H.753(19)\_F02 + +**Figure 2 – IPTV architectural overview [ITU-T Y.1910]** + +Figure 3 provides updated IPTV architecture with the inclusion of scene-based IPTV services. Functions and functional blocks described in this clause are common to all architectural approaches as detailed in [ITU-T H.720] except where stated differently. + +Key to figures: + +- The dotted elliptical area represents additional sources related to Content. +- The dotted and rounded rectangular areas represent the functional blocks added to the IPTV architecture, as indicated in clause 5 of [ITU-T Y.1910]. + +In Figure 3, the following functions are added for scene-based IPTV services. + +- **Scene delivery functions (SDF)**: perform cache and storage functionalities and deliver the scene according to the request from the end-user functions +- **Scene storage functions (SSF)**: store and cache the scene, process it under the control of content preparation functions +- **Scene delivery client functions (SDCF)**: receive and control the delivery of the scene from the scene delivery and storage functions (SDF and SSF). + +![Figure 3 – Updated IPTV architecture for scene-based IPTV services. The diagram shows four main vertical columns: End-user functions, Application functions, Management functions, and Content provider functions. End-user functions include Application client functions, SCP client functions, IPTV terminal functions (Content delivery client functions, Scene delivery client functions, Control client functional block), and Home network functions. Application functions include IPTV application functions, Content preparation functions, Service control functions, and Content delivery functions (Content delivery and storage functions, Scene delivery and storage functions). Management functions include Content and metadata, and Scene and scene-based metadata. Content provider functions include Content and metadata sources and Scene and scene-based metadata sources. Arrows show data flow: Metadata from IPTV application functions to Content preparation functions; Scene-based metadata from Content preparation functions to Content delivery functions; Content from Content preparation functions to Content delivery functions; Scene from Content delivery functions to IPTV application functions; Content and metadata from Content provider functions to Management functions; Scene and scene-based metadata from Content provider functions to Management functions.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Figure 3 – Updated IPTV architecture for scene-based IPTV services. The diagram shows four main vertical columns: End-user functions, Application functions, Management functions, and Content provider functions. End-user functions include Application client functions, SCP client functions, IPTV terminal functions (Content delivery client functions, Scene delivery client functions, Control client functional block), and Home network functions. Application functions include IPTV application functions, Content preparation functions, Service control functions, and Content delivery functions (Content delivery and storage functions, Scene delivery and storage functions). Management functions include Content and metadata, and Scene and scene-based metadata. Content provider functions include Content and metadata sources and Scene and scene-based metadata sources. Arrows show data flow: Metadata from IPTV application functions to Content preparation functions; Scene-based metadata from Content preparation functions to Content delivery functions; Content from Content preparation functions to Content delivery functions; Scene from Content delivery functions to IPTV application functions; Content and metadata from Content provider functions to Management functions; Scene and scene-based metadata from Content provider functions to Management functions. + +H.753(19)\_F03 + +**Figure 3 – Updated IPTV architecture for scene-based IPTV services** + +The IPTV services architecture can be extended to support scene-based content services. Existing functions in IPTV architecture contains the scene-based functions; the scene delivery client function (SDCF) are part of IPTV terminal functions and the SDF/SSF is placed as a part of content delivery functions (CDF) of the IPTV architecture. Moreover, the scene and scene-based metadata can be provided by content provider functions. Figure 4 illustrates scene-based IPTV services flows between a scene-based metadata (SBM) service platform and client-side SBM applications. + +![Figure 4 – Scene-based IPTV services overview. The diagram shows a flow from left to right: Client-side SBM applications (rectangle) and End-user (oval) on the far left. In the center, four ovals represent a chain: Network provider, Service provider, and Content provider. On the far right is the SBM service platform (rectangle). Arrows indicate the following interactions: Client-side SBM applications send 'Scene-based metadata' and 'Scenes' to the SBM service platform. The SBM service platform sends 'Multimedia content' to the Content provider. The Content provider sends data to the Service provider, which sends data to the Network provider, which finally sends data to the End-user. Vertical dashed lines separate the Client-side SBM applications/End-user from the Network provider, the Network provider from the Service provider, and the Service provider from the Content provider/SBM service platform. A label 'H.753(19)_F04' is in the bottom right corner.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 4 – Scene-based IPTV services overview. The diagram shows a flow from left to right: Client-side SBM applications (rectangle) and End-user (oval) on the far left. In the center, four ovals represent a chain: Network provider, Service provider, and Content provider. On the far right is the SBM service platform (rectangle). Arrows indicate the following interactions: Client-side SBM applications send 'Scene-based metadata' and 'Scenes' to the SBM service platform. The SBM service platform sends 'Multimedia content' to the Content provider. The Content provider sends data to the Service provider, which sends data to the Network provider, which finally sends data to the End-user. Vertical dashed lines separate the Client-side SBM applications/End-user from the Network provider, the Network provider from the Service provider, and the Service provider from the Content provider/SBM service platform. A label 'H.753(19)\_F04' is in the bottom right corner. + +**Figure 4 – Scene-based IPTV services overview** + +The client-side SBM applications can access the SBM service platform with a scene-based metadata function interface, which includes basic scene information, location information, music information, object information, and statics information about the scene. SDCF performs handling the request and receives metadata and scenes between client-side SBM applications and SBM service platform. These endpoints are typically categorized as web-based navigation servers maintained by the service provider or client-side applications running on the IPTV client. The SBM service platform is the entity responsible for aggregating SBM sets and scenes produced by content providers or service providers to describe services and scenes, as well as metadata sets generated or registered by metadata clients to describe context for scenes. These SBM sets are maintained in the database managed by the SBM service platform. The SBM maintained in the SBM service platform's database is accessed by, delivered to, or contributed from metadata clients through metadata delivery network and exchange protocols. The SDF and SSF support the roles of the SBM service platform. Therefore, the metadata information and metadata function interface are necessary to describe the scene-based content distribution service. + +# 7 Scene-based metadata + +This clause specifies the scheme of scene-based metadata and the content description model which the metadata is based on. The possible key factors include e.g., metadata for scene description such as SceneStartTime, SceneEndTime and SceneDuration. + +Scene-based metadata (SBM) can represent a distinct part of an episode, can be identified, and can include time information such as when a scene starts and ends. + +### 7.1 Content description model + +Figure 5 shows the content description model of this Recommendation. This is similar to the content description model described in [b-ETSI TS 102 822-1], where a series of programmes can be ordered (e.g. episodes in a numerical order) and an episode can be divided into several scenes. + +The term "scene" means a part of a logically divided episode. + +Key to figures: + +- The rectangular block represents the set of content and its metadata. +- The rectangular block with a diamond on the right side represents that it has multiple instances of the rectangular block connected with solid line. + +![Figure 5 – Content description model diagram showing a hierarchical relationship: PROGRAM contains EPISODE, which contains SCENE.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph LR + PROGRAM[PROGRAM] -- contains --> EPISODE[EPISODE] + EPISODE -- contains --> SCENE[SCENE] + +``` + +Figure 5 – Content description model diagram showing a hierarchical relationship: PROGRAM contains EPISODE, which contains SCENE. + +H.753(19)\_F05 + +**Figure 5 – Content description model** + +### 7.2 Data types for scene-based metadata + +Table 1 explains the data types used in this Recommendation. + +**Table 1 – Data types used in this Recommendation** + +| Type | Name | Notes/Reference | +|------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| xs:float | Float | Float is based on the IEEE single-precision 32-bit floating point type.
    Defined in [W3C XMLSchemaP2]. | +| xs:ID | Identifier | Represents unique identifier.
    Defined in [W3C XMLSchemaP2]. | +| xs:IDREF | Reference to Identifier | Represents a reference to xs:ID.
    Defined in [W3C XMLSchemaP2]. | +| xs:nonNegativeInteger | Non-negative integer | An integer containing only non-negative values (0,1,2,...)
    Defined in [W3C XMLSchemaP2]. | +| xs:positiveInteger | Positive integer | An integer containing only positive values (1,2,...)
    Defined in [W3C XMLSchemaP2]. | +| xs:NMToken | NMToken | The NMToken data type can contain whitespace (e.g., line feeds, carriage returns, and tab)-replaced and collapsed strings, that have no leading or trailing spaces (#x20) and that have no space may appear within the value itself.
    Defined in [W3C XMLSchemaP2]. | +| xs:NMToken enumeration | NMToken with enumeration restriction | Restricted NMToken values
    Defined in [W3C XMLSchemaP2]. | +| xs:time | Time | The format of time is "hh:mm:ss" where: hh indicates the hour, mm indicates the minute, ss indicates the second.
    Defined in [W3C XMLSchemaP2]. | +| xs:string | String | Used to specify the string value which data type can contains characters, line feeds, carriage returns, and tab characters.
    Defined in [W3C XMLSchemaP2] | +| URL | Uniform Resource Locator (URL) | Used to locate resources by describing its access mechanism. (e.g., its network "location").
    Defined in [IETF RFC 3986] as URI= scheme ":" hier-part ["?" query] ["#" fragment]. | + +# 8 SBM elements and format + +This clause specifies metadata for content distribution to ensure distribution efficacy and metadata interoperability. Contents produced by contents providers have become ubiquitous after the emergence of various devices such as IPTV terminal devices and mobile IPTV devices which provide online services. In this service environment, interoperability and sharing of content metadata is an important basis for content distribution. + +### 8.1 Scene-based metadata (SBM) for basic elements + +Table 2 describes the scene-based metadata (SBM) for basic elements. This SBM references several basic information items for scene identification and definition. + +**Table 2 – Scene-based metadata (SBM) for basic elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|-----------------------|------------------------------------------------------------------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SceneID | Identifies the scene | | e.g. "KBS1_T2017-02-01-10", (channel ID-program ID-episode ID-scene order) | +| SceneOrder | Describes the order of scene | | e.g. "5", "24" | +| SceneStartTime | Describes the time when the scene starts playing | | e.g. "00:53:38", "01:05:22" | +| SceneEndTime | Describes the time when the scene ends playing. | | e.g. "00:43:28", "01:13:45" | +| SceneDuration | Describes the duration of playing time for the scene. | | e.g. "45", "234" with the unit of seconds | +| SceneKeyframeImageURL | Describes the URL of the key frame image representing the scene. | | e.g. http://52.198.166.6:8000/2016-017-KBS1_T2016-02-01-DescendentOfSun-302/SCENE/CLIP/KBS1_T2016-02-01-02-SCENE_KEYFRAME.jpg | +| EpisodeID | Identifies the episode containing the scene. | | e.g. "KBS1_T2017-02-01", (channel ID-program ID-episode ID) | +| ProgramID | Identifies the program containing the scene. | | e.g. "KBS1_T2017-02", (channel ID-program ID) | +| ChannelID | Identifies the channel containing the scene. | | e.g. "KBS1_T2017", "CNN_T2017", "BBC_T2016" | +| ProgramName | Identifies the program name of the scene. | | e.g. "Descendant of Sun" | +| EpisodeNumber | Describes the sequence number of the episode. | | e.g. 42 | +| SceneTitle | Describes the title of the scene. | | describes a scene with short phrase or sentence | +| SceneSynopsis | Describes the synopsis of the scene. | | | + +**Table 2 – Scene-based metadata (SBM) for basic elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|---------------------|----------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SceneSubtitle | Describes the subtitle of the scene | | | +| SceneSearchKeyword | Describes the keyword for searching the scene. | | Several key words can be defined separately with comma. | +| HashTag | Describes hash tag for searching a scene. | | e.g. "#Surgery", "#Paris" | +| SceneURL | Describes the URL of the scene where it is located. | | e.g.
    http://52.198.166.6:8000/2016-017-KBS1_T2016-02-01-DescendentOfSun-302/SCENE/CLIP/KBS1_T2016-02-01-02-SCENE_CLIP.mp4 | +| ProgramHomePageURL | Describes the URL of the program homepage where it is located. | | e.g.
    http://program.sbs.co.kr/builder/programMainList.do?pgm_id=22000006886 | +| SceneResolution | Describes the resolution of the scene. | | e.g.
    31: 270p
    32: 360p
    33: 480p
    34: 720p
    35: 1080p | +| SceneType | Describes the type of the scene. | | e.g. T2: Trailer
    T3: studio sketch TZ: video scene
    TH: Highlights
    TI: Interview | +| SceneCategory | Describes the category of the scene. | | e.g.
    10: Drama
    20: Entertainment
    30: Music
    40: current events
    50: Education
    60: Life
    70: Sports
    80: Games
    90: Child
    100: News | +| SceneSubCategory | Describes the sub-category of the scene. | | e.g.
    71: Baseball
    72: Football
    73: Basketball | + +**Table 2 – Scene-based metadata (SBM) for basic elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|---------------------|-----------------------------------------------------------------------------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TargetNation | Describes the nations to which the scene is targeted. | | e.g.
    KR,JP,CN
    (The national code conforms to ISO 3166-1 two-character country code.) | +| TargetAge | Describes the ages to which the scene is targeted. | | e.g.
    0: Allows all ages
    7: Allows at least 7 years
    12: Allows at least 12 years
    15: Allows at least 15 years
    19: Allows at least 19 years | +| CharacterName | Describes the names of characters who are present in the scene. | | e.g. "Si-Jin", "Dae-Yeong" | +| ActorName | Describes the names of actors who are present in the scene. | | e.g. "Scarlett Ingrid Johansson", "Robert Downey Jr." | +| ServiceCategory | Describes the category of service that is provided with based on the scene. | | e.g.
    01: Online shopping
    02: Location based service
    03: Music service | +| ServiceTimeOffSet | Describes the starting offset of the service. | | e.g. "00:23:13", "01:30:46" | +| SceneUploadingDate | Describes the date of uploading a scene. | | e.g. "2017-07-02" | +| BroadcastingDate | Describes the first broadcasting date of its episode | | e.g. 2017-08-25, 2017-09-15 | +| BroadcastingTime | Describes the broadcasting time of the program containing the scene | | e.g. "00:53:38", "01:05:22" | +| BroadcastingDay | Describes the broadcasting day of the week | | e.g. "Monday", "Thursday" | +| CodecType | Describes the type of Codec for the scene. | | e.g. "MPEG2", "MPEG4", "DivX", "WMA", "ASF" | +| PreviousSceneURL | URL that allows for jumping to the previous scene from the current scene. | | e.g.
    http://52.198.166.6:8000/2016-017-KBS1_T2016-02-01-DescendentOfSun-302/KBS1_T2016-02-01-01 | + +**Table 2 – Scene-based metadata (SBM) for basic elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|---------------------|-----------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------| +| NextSceneURL | URL that allows for jumping to the next scene from the current scene. | | e.g.
    http://52.198.166.6:80
    00/2016-017-
    KBS1_T2016-02-01-
    DescendentOfSun-
    302/KBS1_T2016-02-
    01-02 | + +### 8.2 Scene-based metadata (SBM) for location elements + +Table 3 describes scene-based metadata (SBM) for location elements. This SBM references several items of location information where the scene is present. + +**Table 3 – Scene-based metadata (SBM) for location elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|---------------------|--------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------| +| LocationName | Describes the name of the location where the scene is present. | | e.g.
    "Seoul", "Shanghai",
    "Tokyo" | +| LocationAddress | Describes the address of the location where the scene is present. | | e.g. the Street name | +| LocationURL | Describes the URL of the location linked to the current scene in order to provide more detailed information. | | e.g.
    https://www.whiteho
    use.gov/ | + +### 8.3 Scene-based metadata (SBM) for music elements + +Table 4 describes the scene-based metadata (SBM) for music elements. This SBM references several items of music information where the scene is present. + +**Table 4 – Scene-based metadata (SBM) for music elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|---------------------|----------------------------------------------------------------------|--------------|----------------------------------------------------| +| MusicTitles | Describes the title of the music that is being played in the scene. | | e.g. "You are my
    everything",
    "Who are you?" | +| MusicGenre | Describes the genre of the music that is being played in the scene. | | e.g. "Blues", "Jazz",
    "Hip hop" | +| MusicSinger | Describes the singer of the music that is being played in the scene. | | e.g. the Singer name | + +**Table 4 – Scene-based metadata (SBM) for music elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|---------------------|---------------------------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------| +| MusicURL | Describes the URL of the music that is being played as background music in the scene. | | e.g.
    "http://music.naver.com/album/index.nhn?albumId=623671",
    "http://music.naver.com/artist/home.nhn?artistId=419995" | +| MusicLyrics | Describes the lyrics of the music that is being played as background music in the scene. | | | +| MusicVideoURL | Describes the URL of the music video that is being played as background music in the scene. | | e.g.
    "http://tv.naver.com/v/1943434/list/67096" | + +### 8.4 Scene-based metadata (SBM) for object elements + +Table 5 describes the scene-based metadata (SBM) for object elements. This SBM references several items of object information where the scene is present. + +**Table 5 – Scene-based metadata (SBM) for object elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|---------------------|---------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------| +| ObjectID | Identifies the object. | | | +| ObjectName | Describes the name of the object that is bound to the present scene. | | e.g. "Homeo table",
    "INO earrings" | +| ObjectCategory | Describes the category of the object that is bound to the present scene. | | e.g. "Bag",
    "Clothing",
    "Accessory" | +| ObjectBrand | Describes the brand of the object that is bound to the present scene. | | e.g. "Jtiara", "Paul's Boutique" | +| ObjectCompany | Describes the company of the object that is bound to the present scene. | | e.g. "S&K global", | +| ObjectNumber | Describes the number of the object that is bound to the present scene. | | e.g. the Singer name | +| ObjectColor | Describes the colour of the object that is bound to the present scene. | | e.g. "White",
    "Black" | +| ObjectPrice | Describes the price of the object that is bound to the present scene. | | e.g. "\$45.6", "\$690" | +| ObjectImageURL | Describes the image URL of the object that is bound to the present scene. | | e.g.
    "http://www.ssg.com/item/itemView.ssg?itemId=0000004553455&siteNo=6004&salestrNo=6005" | + +**Table 5 – Scene-based metadata (SBM) for object elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|------------------------|---------------------------------------------------------------------------------------|--------------|----------------------------------------| +| ObjectSteelCutImageURL | Describes the steel cut image of the object that is bound to the present scene. | | e.g. The Thumbnail image | +| ObjectShoppinURL | Describes the shopping URL of the object that is bound to the present scene. | | e.g. online shopping homepage website. | +| ObjectReleaseDate | Describes the released date of the object that is bound to the present scene. | | e.g. 2017-05-25, 2016-09-14 | +| ObjectCountry | Describes the manufacturing country of the object that is bound to the present scene. | | e.g. "KR" or "Korea" | +| ObjectSize | Describes the size of the object that is bound to the present scene. | | e.g. "width" and "height" (real size) | +| WearOnActorName | Describes the name of actor who wears the object. | | e.g. "Hye-kyo Song", "Joon-ki Song" | +| WearOnActorRoleName | Describes the role name of actor who wears the object | | e.g. "Mo-yeon Kang", "Si-jin Rue" | + +### 8.5 Scene-based metadata (SBM) for statistics elements + +Table 6 describes the scene-based metadata (SBM) for statistics elements. This SBM references several items of statistics information where the scene is present. + +**Table 6 – Scene-based metadata (SBM) for statistics elements** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|---------------------|-----------------------------------------------------------------|--------------|-----------------------| +| ClickCount | Describes the number of visits to the scene. | | e.g. 34,498, 456,789 | +| GoodRatingCount | Describes the number giving a positive evaluation of the scene. | | e.g. 792,345, 330,901 | +| BadRatingCount | Describes the number giving a negative evaluation of the scene. | | e.g. 832,316, 140,508 | + +## 9 SBM management functions + +This clause describes metadata management functions of SBM for a media service platform that allows an operator to access to metadata and video contents. + +Figure 6 shows the IPTV terminal device (TD) functional architecture recommended in [ITU-T H.720] updated for the scene delivery client functions that include basic scene, location, music, object and statistics information. + +According to [ITU-T H.720], the media client functions are implicitly described in clause 9.1.1 of [ITU-T Y.1910]. The content delivery client function has responsibility for the content reception, and its logically related function, the content delivery function, has content processing functionalities such as transcoding. Therefore, media client functions are located in content delivery client functions. + +According to [ITU-T H.720], the media control functional entity controls video and audio components and other components such as de-multiplexing, encoding, metadata handling, content storing and play/reproduction of content including streaming data. + +![Figure 6 – Updated functional architecture block diagram of IPTV terminal devices for scene-based IPTV services. The diagram shows a hierarchical structure of functional blocks. At the top is 'Application client functions' (orange) containing 'SADS client functional block' and 'IPTV application client'. Below it is 'SCP client functions' (green) containing 'Service protection client functional block' and 'Content protection client functional block'. Below that are 'Control client functional block' and 'Performance monitoring'. The next level is 'Content delivery client functions' (dark blue) containing 'Broadcast demux', 'Media client functions' (light blue), 'Unicast content delivery client functional block', 'Multicast content delivery client functional block', and 'Error recovery client functional block'. 'Media client functions' contains 'Metadata management' (yellow) with 'Basic scene information', 'Location information', 'Music information', 'Object information', and 'Statistics information', as well as 'Demux/mux', 'Storage', 'Codecs', and 'Media control'. At the bottom is 'IPTV terminal transport functions' (yellow) containing 'Network attachment client'. A vertical 'Terminal device management' block is on the left, connected to the top three levels.](812e188283162af0b54fb3e30ffee51b_img.jpg) + +Figure 6 – Updated functional architecture block diagram of IPTV terminal devices for scene-based IPTV services. The diagram shows a hierarchical structure of functional blocks. At the top is 'Application client functions' (orange) containing 'SADS client functional block' and 'IPTV application client'. Below it is 'SCP client functions' (green) containing 'Service protection client functional block' and 'Content protection client functional block'. Below that are 'Control client functional block' and 'Performance monitoring'. The next level is 'Content delivery client functions' (dark blue) containing 'Broadcast demux', 'Media client functions' (light blue), 'Unicast content delivery client functional block', 'Multicast content delivery client functional block', and 'Error recovery client functional block'. 'Media client functions' contains 'Metadata management' (yellow) with 'Basic scene information', 'Location information', 'Music information', 'Object information', and 'Statistics information', as well as 'Demux/mux', 'Storage', 'Codecs', and 'Media control'. At the bottom is 'IPTV terminal transport functions' (yellow) containing 'Network attachment client'. A vertical 'Terminal device management' block is on the left, connected to the top three levels. + +H.753(19)\_F06 + +**Figure 6 – Updated functional architecture block diagram of IPTV terminal devices for scene-based IPTV services** + +### 9.1 Basic scene information functions + +Basic scene information functions are the functions between SBM service platform and client-side SBM applications. + +The requesting and providing of the basic scene information between IPTV TD and content or service provider, or between the IPTV network and IPTV TD are performed through these interfaces. + +Tables 7 to 42 show function parameters and function return values. The 'M' and 'O' in the 'Support' column of returned values tables denote 'mandatory' and 'optional' respectively. + +#### 9.1.1 Whole program retrieval function (ProgramList) + +ProgramList is the function for requesting the whole program list that a content or service provider can deliver through IP network. + +The content or service provider can provide a channel ID, a program ID or episode ID through this interface. + +**Table 7 – Parameter of the ProgramList function** + +| Parameter | Description | Type | +|-----------|------------------------------------------|------| +| None | There is no parameter for this function. | | + +**Table 8 – Returned values of the ProgramList function** + +| Returned value | Description | Type | Support | +|--------------------|-------------------------------------------------------------------------------------|-----------|---------| +| { | Denotes the starting of the list. | | | +| ProgramID | Identifies the program containing the scene. | | M | +| ProgramName | Identifies the program name of the scene. | | M | +| ChannelID | Identifies the channel containing the scene. | | M | +| EpisodeCount | Describes the total number of episodes. | | M | +| ProgramHomePageURL | Describes the URL of the program homepage where it is located. | | O | +| TargetNation | Describes the nations to which the scene is targeted. | | O | +| TargetAge | Describes the ages to which the scene is targeted. | | O | +| }, ...] | Denotes the set of the returned values that is repeated and the ending of the list. | | | + +#### 9.1.2 Whole episode retrieval function (EpisodeList) + +EpisodeList is the function for requesting the whole episode list that the content or service provider can deliver through IP network. + +The content or service provider can provide an episode ID or sequence number of the episode. + +**Table 9 – Parameter of the EpisodeList function** + +| Parameter | Description | Type | +|-----------|----------------------------------------------|----------| +| ProgramID | Identifies the program containing the scene. | | + +**Table 10 – Returned values of the EpisodeList function** + +| Returned value | Description | Type | Support | +|------------------|--------------------------------------------------------------------------------|---------------|---------| +| { | Denotes the starting of the list. | | | +| EpisodeID | Identifies the episode containing the scene. | | M | +| BroadcastingDate | Describes the first broadcasting date of its episode. | < date> | O | +| BroadcastingTime | Describes the broadcasting time of the program containing the scene. | | O | +| storyline | Describes the story of the corresponding episode. | | O | +| }, ...] | Denotes the set of the returned values is repeated and the ending of the list. | | | + +#### 9.1.3 Whole scene retrieval function (SceneList) + +SceneList is the function for requesting the whole scene ID list of a specific episode that the content or service provider can deliver through IP network. + +The content or service provider can provide scene ID, the order of scene, or the title of the scene. + +**Table 11 – Parameter of the SceneList function** + +| Parameter | Description | Type | +|-----------|----------------------------------------------|---------| +| EpisodeID | Identifies the episode containing the scene. | | + +**Table 12 – Returned values of the SceneList function** + +| Returned value | Description | Type | Support | +|----------------|--------------------------------------------------------------------------------|-------------|---------| +| { | Denotes the starting of the list. | | | +| SceneID | Identifies the scene. | | M | +| SceneTitle | Describes the title of the scene. | < string > | O | +| SceneOrder | Describes the order of scene. | < integer > | M | +| }, ...] | Denotes the set of the returned values is repeated and the ending of the list. | | | + +#### 9.1.4 SBM of a specific episode retrieval function (SceneListByEpisodeID) + +SceneListByEpisodeID is the function for requesting SBM of a specific episode that the content or service provider can deliver through IP network. + +The content or service provider can provide an ID, a title, a synopsis, an URL of a key image, an order, etc. of the scene for the requested episode through this interface. + +**Table 13 – Parameter of the SceneListByEpisodeID function** + +| Parameter | Description | Type | +|-----------|----------------------------------------------|---------| +| EpisodeID | Identifies the episode containing the scene. | | + +**Table 14 – Returned values of the SceneListByEpisodeID function** + +| Returned value | Description | Type | Support | +|----------------|-------------------------------------------------------|---------------|---------| +| { | Denotes the starting of the list. | | | +| SceneID | Identifies the scene. | | M | +| SceneTitle | Describes the title of the scene. | | O | +| SceneOrder | Describes the order of scene. | | M | +| SceneStartTime | Describes the time when the scene starts playing. | | M | +| SceneEndTime | Describes the time when the scene ends playing. | | M | +| SceneDuration | Describes the duration of playing time for the scene. | | M | + +**Table 14 – Returned values of the SceneListByEpisodeID function** + +| Returned value | Description | Type | Support | +|-----------------------|--------------------------------------------------------------------------------|------------|---------| +| SceneKeyFrameImageURL | Describes the URL of the key frame image representing the scene. | | O | +| SceneURL | Describes the URL of the scene where it is located. | | O | +| SceneResolution | Describes the resolution of the scene. | < integer> | O | +| SceneType | Describes the type of the scene. | < string> | O | +| PreviousSceneURL | URL that allows for jumping to the previous scene from the current scene. | | O | +| NextSceneURL | URL that allows for jumping to the next scene from the current scene. | | O | +| ServiceCategory | Describes the category of service that is provided with based on the scene. | | O | +| }, ...] | Denotes the set of the returned values is repeated and the ending of the list. | | | + +#### 9.1.5 SBM of a specific scene retrieval function (SceneBySceneID) + +SceneBySceneID is the function for requesting SBM of a specific scene ID that the content or service provider can deliver through IP network. + +**Table 15 – Parameter of the SceneBySceneID function** + +| Parameter | Description | Type | +|-----------|-----------------------|---------| +| SceneID | Identifies the scene. | | + +**Table 16 – Returned values of the SceneBySceneID function** + +| Returned value | Description | Type | Support | +|-----------------------|------------------------------------------------------------------|---------------|---------| +| SceneOrder | Describes the order of scene. | | M | +| SceneStartTime | Describes the time when the scene starts playing. | | M | +| SceneEndTime | Describes the time when the scene ends playing. | | M | +| SceneDuration | Describes the duration of playing time for the scene. | | M | +| SceneKeyframeImageURL | Describes the URL of the key frame image representing the scene. | | O | +| EpisodeID | Identifies the episode containing the scene. | | M | +| ProgramID | Identifies the program containing the scene. | | M | +| ChannelID | Identifies the channel containing the scene. | | M | +| ProgramName | Identifies the program name of the scene. | | O | +| EpisodeNumber | Describes the sequence number of the episode. | | O | +| SceneTitle | Describes the title of the scene. | | O | + +**Table 16 – Returned values of the SceneBySceneID function** + +| Returned value | Description | Type | Support | +|--------------------|-----------------------------------------------------------------------------|---------------|---------| +| SceneSynopsis | Describes the synopsis of the scene. | | O | +| SceneSubtitle | Describes the subtitle of the scene. | | O | +| SceneSearchKeyword | Describes the keyword for searching the scene. | | O | +| HashTag | Describes hash tag for searching a scene. | | O | +| SceneURL | Describes the URL of the scene where it is located. | | O | +| ProgramHomePageURL | Describes the URL of the program homepage where it is located. | | O | +| SceneResolution | Describes the resolution of the scene. | | O | +| SceneType | Describes the type of the scene. | | O | +| SceneCategory | Describes the category of the scene. | | O | +| SceneSubCategory | Describes the sub-category of the scene. | | O | +| TargetNation | Describes the nations to which the scene is targeted. | | O | +| TargetAge | Describes the ages to which the scene is targeted. | | O | +| CharacterName | Describes the names of characters who are present in the scene. | | O | +| ActorName | Describes the names of actors who are present in the scene. | | O | +| ServiceCategory | Describes the category of service that is provided with based on the scene. | | O | +| ServiceTimeOffSet | Describes the starting offset of the service. | | O | +| SceneUploadingDate | Describes the date of uploading a scene. | | O | +| BroadcastingDate | Describes the first broadcasting date of its episode. | | O | +| BroadcastingTime | Describes the broadcasting time of the program containing the scene. | | O | +| BroadcastingDay | Describes the broadcasting day of the week. | | O | +| CodecType | Describes the type of Codec for the scene. | | O | +| PreviousSceneURL | URL that allows for jumping to the previous scene from the current scene. | | O | +| NextSceneURL | URL that allows for jumping to the next scene from the current scene. | | O | + +#### 9.1.6 Whole SBM retrieval function (SceneList) + +SceneList is the function for requesting of the whole SBM that the content or service provider can deliver through IP network. + +All SBM sets and scenes that are stored in a SBM service platform can be provided through this interface. + +**Table 17 – Parameter of the SceneList function** + +| Parameter | Description | Type | +|-----------|----------------------------------------------|---------| +| EpisodeID | Identifies the episode containing the scene. | | + +**Table 18 – Returned values of the SceneList function** + +| Returned value | Description | Type | Support | +|-----------------------|--------------------------------------------------------------------------------|-----------|---------| +| { | Denotes the starting of the list. | | | +| SceneID | Identifies the scene. | | M | +| SceneTitle | Describes the title of the scene. | | O | +| SceneSubtitle | Describes the subtitle of the scene. | | | +| SceneOrder | Describes the order of the scene. | | M | +| SceneKeyFrameImageURL | Describes the URL of the key frame image representing the scene. | | O | +| SceneType | Describes the type of the scene. | | O | +| }, ...] | Denotes the set of the returned values is repeated and the ending of the list. | | | + +#### **9.1.7 SBM of a specific time retrieval function (SceneByTime)** + +SceneByTime is the function for requesting the SBM for a specific time of a scene that the content or service provider can deliver through IP network. + +The specified time can be a relative time interval from starting playing time. + +**Table 19 – Parameter of the SceneByTime function** + +| Parameter | Description | Type | +|-------------|--------------------------------------------------------------------------------|---------------| +| ProgramID | Identifies the program containing the scene. | | +| EpisodeID | Identifies the episode containing the scene. | | +| ServiceTime | Specifies the time that is in the interval of a specific scene to be searched. | | + +**Table 20 – Returned values of the SceneByTime function** + +| Returned value | Description | Type | Support | +|-----------------------|------------------------------------------------------------------|---------------|---------| +| SceneID | Identifies the scene. | | M | +| SceneOrder | Describes the order of scene. | | M | +| SceneStartTime | Describes the time when the scene starts playing.. | | M | +| SceneEndTime | Describes the time when the scene ends playing. | | M | +| SceneDuration | Describes the duration of playing time for the scene. | | M | +| SceneKeyframeImageURL | Describes the URL of the key frame image representing the scene. | | O | + +**Table 20 – Returned values of the SceneByTime function** + +| Returned value | Description | Type | Support | +|--------------------|-----------------------------------------------------------------------------|---------------|---------| +| EpisodeID | Identifies the episode containing the scene. | | M | +| ProgramID | Identifies the program containing the scene. | | M | +| ChannelID | Identifies the channel containing the scene. | | M | +| ProgramName | Identifies the program name of the scene. | | O | +| EpisodeNumber | Describes the sequence number of the episode. | | M | +| SceneTitle | Describes the title of the scene. | | O | +| SceneSynopsis | Describes the synopsis of the scene. | | O | +| SceneSubtitle | Describes the subtitle of the scene. | | O | +| SceneSearchKeyword | Describes the keyword for searching the scene. | | O | +| HashTag | Describes hash tag for searching a scene. | | O | +| SceneURL | Describes the URL of the scene where it is located. | | O | +| ProgramHomePageURL | Describes the URL of the program homepage where it is located. | | O | +| SceneResolution | Describes the resolution of the scene. | | O | +| SceneType | Describes the type of the scene. | | O | +| SceneCategory | Describes the category of the scene. | | O | +| SceneSubCategory | Describes the sub-category of the scene. | | O | +| TargetNation | Describes the nations to which the scene is targeted. | | O | +| TargetAge | Describes the ages to which the scene is targeted. | | O | +| CharacterName | Describes the names of characters who are present in the scene. | | O | +| ActorName | Describes the names of actors who are present in the scene. | | O | +| ServiceCategory | Describes the category of service that is provided with based on the scene. | | O | +| ServiceTimeOffSet | Describes the starting offset of the service. | | O | +| SceneUploadingDate | Describes the date of uploading a scene. | | O | +| BroadcastingDate | Describes the first broadcasting date of its episode. | | O | +| BroadcastingTime | Describes the broadcasting time of the program containing the scene. | | O | +| BroadcastingDay | Describes the broadcasting day of the week. | | O | +| CodecType | Describes the type of Codec for the scene. | | O | +| PreviousSceneURL | URL that allows for jumping to the previous scene from the current scene. | | O | +| NextSceneURL | URL that allows for jumping to the next scene from the current scene. | | O | + +#### 9.1.8 Scene list with a specific keyword retrieval function (SceneListByKeyword) + +SceneListByKeyword is the function for requesting the scene list with a specific keyword that the content or service provider can deliver through IP network. + +The keyword can be manually produced or automatically generated by a metadata generator. + +**Table 21 – Parameter of the SceneListByKeyword function** + +| Parameter | Description | Type | +|--------------------|------------------------------------------------|----------| +| SceneSearchKeyword | Describes the keyword for searching the scene. | | + +**Table 22 – Returned values of the SceneListByKeyword function** + +| Returned value | Description | Type | Support | +|-----------------------|--------------------------------------------------------------------------------|---------------|---------| +| { | Denotes the starting of the list. | | | +| ProgramID | Identifies the program containing the scene. | | M | +| EpisodeID | Identifies the episode containing the scene. | | M | +| SceneID | Identifies the scene. | | M | +| SceneTitle | Describes the title of the scene. | | O | +| SceneOrder | Describes the order of scene. | | M | +| SceneStartTime | Describes the time when the scene starts playing. | | M | +| SceneEndTime | Describes the time when the scene ends playing. | | M | +| SceneDuration | Describes the duration of playing time for the scene. | | M | +| SceneKeyFrameImageURL | Describes the URL of the key frame image representing the scene. | | O | +| SceneURL | Describes the URL of the scene where it is located. | | O | +| SceneResolution | Describes the resolution of the scene. | | O | +| SceneType | Describes the type of the scene. | | O | +| PreviousSceneURL | URL that allows for jumping to the previous scene from the current scene. | | O | +| NextSceneURL | URL that allows for jumping to the next scene from the current scene. | | O | +| }, ...] | Denotes the set of the returned values is repeated and the ending of the list. | | | + +#### 9.1.9 Related scene retrieval function (SimilarSceneList) + +SimilarSceneList is the function for requesting the related scene for a specific scene that the content or service provider can deliver through IP network. + +The content or service provider can provide SBM of several similar scenes through this interface. + +**Table 23 – Parameter of the SimilarSceneList function** + +| Parameter | Description | Type | +|-----------|-----------------------|---------| +| SceneID | Identifies the scene. | | + +**Table 24 – Returned values of the SimilarSceneList function** + +| Returned value | Description | Type | Support | +|-----------------------|--------------------------------------------------------------------------------|-----------|---------| +| { | Denotes the starting of the list. | | | +| SceneID | Identifies the scene. | | M | +| SceneOrder | Describes the order of scene. | | M | +| SceneKeyframeImageURL | Describes the URL of the key frame image representing the scene. | | O | +| SceneTitle | Describes the title of the scene. | | O | +| SceneURL | Describes the URL of the scene where it is located. | | O | +| Similar_scene_ID | Represents list of identifier information of similar scenes. | | M | +| }, ...] | Denotes the set of the returned values is repeated and the ending of the list. | | | + +#### **9.1.10 Most related SBM retrieval function (BestSceneList)** + +BestSceneList is the function for requesting of the most related scene for a specific scene that the content or service provider can deliver through IP network. + +The content or service provider can provide SBM of most similar scenes through this interface. + +**Table 25 – Parameter of the BestSceneList function** + +| Parameter | Description | Type | +|-----------------|------------------------------------------------------|-----------| +| SceneID | Identifies the scene. | | +| ProgramID | Identifies the program containing the scene. | | +| EpisodeID | Identifies the episode containing the scene. | | +| BestSceneNumber | Specifies the number of most similar scene searches. | | + +**Table 26 – Returned values of the BestSceneList function** + +| Returned value | Description | Type | Support | +|-----------------------|------------------------------------------------------------------|-----------|---------| +| { | Denotes the starting of the list. | | | +| SceneID | Identifies the scene. | | M | +| EpisodeID | Identifies the episode containing the scene. | | M | +| ProgramID | Identifies the program containing the scene. | | M | +| RankingNumber | Represents the sequence number of similarity. | | M | +| SceneOrder | Describes the order of scene. | | M | +| SceneTitle | Describes the title of the scene. | | O | +| SceneKeyFrameImageURL | Describes the URL of the key frame image representing the scene. | | O | +| SceneUploadingDate | Describes the date of uploading a scene. | | O | +| SceneSearchKeyword | Describes the keyword for searching the scene. | | O | +| ClickCount | Describes the number of visits to the scene. | | O | + +**Table 26 – Returned values of the BestSceneList function** + +| Returned value | Description | Type | Support | +|-----------------|--------------------------------------------------------------------------------|-----------|---------| +| GoodRatingCount | Describes the number giving a good evaluation of the scene. | | O | +| BadRatingCount | Describes the number giving a bad evaluation of the scene. | | O | +| }, ...] | Denotes the set of the returned values is repeated and the ending of the list. | | | + +#### **9.1.11 URL of scene clip retrieval function (SceneClipBySceneID)** + +SceneClipBySceneID is the function for requesting the URL of a specific scene clip that the content or service provider can deliver through IP network. + +The content or service provider can provide an URL or a path of the scene clip through this interface. + +**Table 27 – Parameter of the SceneClipBySceneID function** + +| Parameter | Description | Type | +|-----------|-----------------------|---------| +| SceneID | Identifies the scene. | | + +**Table 28 – Returned values of the SceneClipBySceneID function** + +| Returned value | Description | Type | Support | +|-----------------------|---------------------------------------------------------------------------|---------------|---------| +| ProgramID | Identifies the program containing the scene. | | M | +| EpisodeID | Identifies the episode containing the scene. | | M | +| SceneID | Identifies the scene. | | M | +| SceneOrder | Describes the order of scene. | | M | +| SceneTitle | Describes the title of the scene. | | O | +| SceneSynopsis | Describes the synopsis of the scene. | | O | +| SceneStartTime | Describes the time when the scene starts playing. | | M | +| SceneEndTime | Describes the time when the scene ends playing. | | M | +| SceneDuration | Describes the duration of playing time for the scene. | | M | +| SceneKeyFrameImageURL | Describes the URL of the key frame image representing the scene. | | O | +| SceneURL | Describes the URL of the scene where it is located. | | O | +| SceneResolution | Describes the resolution of the scene. | < integer> | O | +| SceneType | Describes the type of the scene. | < string> | O | +| PreviousSceneURL | URL that allows for jumping to the previous scene from the current scene. | | O | + +**Table 28 – Returned values of the SceneClipBySceneID function** + +| Returned value | Description | Type | Support | +|-----------------|-----------------------------------------------------------------------------|-----------|---------| +| NextSceneURL | URL that allows for jumping to the next scene from the current scene. | | O | +| ServiceCategory | Describes the category of service that is provided with based on the scene. | | O | + +#### **9.1.12 URL of scene key frame image retrieval function (KeyFrameImageBySceneID)** + +KeyFrameImageBySceneID is the function for requesting the URL of a specific scene key frame that the content or service provider can deliver through IP network. + +The content or service provider can provide an URL or a path of the scene key frame through this interface. + +**Table 29 – Parameter of the KeyFrameImageBySceneID function** + +| Parameter | Description | Type | +|-----------|-----------------------|---------| +| SceneID | Identifies the scene. | | + +**Table 30 – Returned values of the KeyFrameImageBySceneID function** + +| Returned value | Description | Type | Support | +|-----------------------|------------------------------------------------------------------|-------|---------| +| SceneKeyframeImageURL | Describes the URL of the key frame image representing the scene. | | M | + +#### **9.1.13 Title of a specific scene retrieval function (SceneTitleBySceneID)** + +SceneTitleBySceneID is the function for requesting the title of a specific scene that the content or service provider can deliver through IP network. + +**Table 31 – Parameter of the SceneTitleBySceneID function** + +| Parameter | Description | Type | +|-----------|-----------------------|---------| +| SceneID | Identifies the scene. | | + +**Table 32 – Returned values of the SceneTitleBySceneID function** + +| Returned value | Description | Type | Support | +|------------------|-----------------------------------------------------------------------------|-----------|---------| +| SceneTitle | Describes the title of the scene. | | M | +| SceneSynopsis | Describes the synopsis of the scene. | | O | +| SceneSubtitle | Describes the subtitle of the scene. | | O | +| HashTag | Describes hash tag for searching a scene. | | O | +| SceneCategory | Describes the category of the scene. | | O | +| SceneSubCategory | Describes the sub-category of the scene. | | O | +| ServiceCategory | Describes the category of service that is provided with based on the scene. | | O | +| ChannelID | Identifies the channel containing the scene. | | O | + +### 9.2 Location information functions + +#### 9.2.1 Location information meta retrieval function (LocationMetaBySceneID) + +LocationMetaBySceneID is the function for requesting the location information for a specific scene that the content or service provider can deliver through IP network. + +The content or service provider can provide the name, the address and the URL of the location through this interface. + +**Table 33 – Parameter of the LocationMetaBySceneID function** + +| Parameter | Description | Type | +|-----------|-----------------------|---------| +| SceneID | Identifies the scene. | | + +**Table 34 – Returned values of the LocationMetaBySceneID function** + +| Returned value | Description | Type | Support | +|-----------------|------------------------------------------------------------------------------------------------------------|----------|---------| +| LocationName | Describes the name of location where the scene is present. | | O | +| LocationAddress | Describes the address of location where the scene is present. | | O | +| LocationURL | Describes the URL of the location linked to the current scene in order to provide more detail information. | | O | + +### 9.3 Music information functions + +#### 9.3.1 Music information meta retrieval function (MusicMetaBySceneID) + +MusicMetaBySceneID is the function for requesting the music information for a specific scene that the content or service provider can deliver through IP network. + +The content or service provider can provide the title, the artist and the URL of the music through this interface. + +**Table 35 – Parameter of the MusicMetaBySceneID function** + +| Parameter | Description | Type | +|-----------|-----------------------|---------| +| SceneID | Identifies the scene. | | + +**Table 36 – Returned values of the MusicMetaBySceneID function** + +| Returned value | Description | Type | Support | +|----------------|----------------------------------------------------------------------|----------|---------| +| MusicTitles | Describes the title of the music that is being played in the scene. | | O | +| MusicGenre | Describes the genre of the music that is being played in the scene. | | O | +| MusicSinger | Describes the singer of the music that is being played in the scene. | | O | + +**Table 36 – Returned values of the MusicMetaBySceneID function** + +| Returned value | Description | Type | Support | +|----------------|---------------------------------------------------------------------------------------------|--------|---------| +| MusicURL | Describes the URL of the music that is being played as background music in the scene. | | O | +| MusicLyrics | Describes the lyrics of the music that is being played as background music in the scene. | | O | +| MusicVideoURL | Describes the URL of the music video that is being played as background music in the scene. | | O | + +### 9.4 Object information functions + +#### 9.4.1 Object information meta retrieval function (ObjectBySceneID) + +ObjectBySceneID is the function for requesting the object information for a specific scene that the content or service provider can deliver through IP network. + +The content or service provider can provide the object ID, the name, the colour and the size of the object through this interface. + +**Table 37 – Parameter of the ObjectBySceneID function** + +| Parameter | Description | Type | +|-----------|----------------------------------------------|---------| +| SceneID | Identifies the scene. | | +| ProgramID | Identifies the program containing the scene. | | +| EpisodeID | Identifies the episode containing the scene. | | + +**Table 38 – Returned values of the ObjectBySceneID function** + +| Returned value | Description | Type | Support | +|----------------|----------------------------------------------------------------------|----------|---------| +| SceneID | Identifies the scene. | | O | +| ObjectID | Identifies the object. | | O | +| ObjectName | Describes the name of object that is bound to the present scene. | | O | +| ObjectCategory | Describes the category of object that is bound to the present scene. | | O | +| ObjectColor | Describes the colour of object that is bound to the present scene. | | O | +| ObjectSize | Describes the size of object that is bound to the present scene. | | O | + +#### 9.4.2 SBM of a specific object retrieval function (SceneWithObject) + +SceneWithObject is the function for requesting the SBM for a specific object that the content or service provider can deliver through IP network. + +The content or service provider can provide the scene ID, the title and the starting time of the scene through this interface. + +**Table 39 – Parameter of the SceneWithObject function** + +| Parameter | Description | Type | +|-----------|----------------------------------------------|---------| +| ObjectID | Identifies the object. | | +| ProgramID | Identifies the program containing the scene. | | +| EpisodeID | Identifies the episode containing the scene. | | + +**Table 40 – Returned values of the SceneWithObject function** + +| Returned value | Description | Type | Support | +|-----------------------|------------------------------------------------------------------|-----------|---------| +| SceneID | Identifies the scene. | | O | +| SceneKeyFrameImageURL | Describes the URL of the key frame image representing the scene. | | O | +| SceneOrder | Describes the order of scene. | | O | +| SceneTitle | Describes the title of the scene. | | O | +| SceneSynopsis | Describes the synopsis of the scene. | | O | +| SceneDuration | Describes the duration of playing time for the scene. | | O | +| SceneURL | Describes the URL of the scene where it is located. | | O | + +### 9.5 Statistics information functions + +#### 9.5.1 Statistics information meta retrieval function (StasticsMetaBySceneIDList) + +StasticsMetaBySceneIDList is the function for requesting the statistics information for a specific scene that the content or service provider can deliver through IP network. + +The content or service provider can provide the number of visits, the number giving a positive evaluation and the number giving a negative evaluation of the scene through this interface. + +**Table 41 – Parameter of the StasticsMetaBySceneIDList function** + +| Parameter | Description | Type | +|-----------|-----------------------|---------| +| SceneID | Identifies the scene. | | + +**Table 42 – Returned values of the StasticsMetaBySceneIDList function** + +| Returned value | Description | Type | Support | +|-----------------|----------------------------------------------------------------|-----------|---------| +| ClickCount | Describes the number of visits to the scene. | | O | +| GoodRatingCount | Describes the number of making a good evaluation of the scene. | | O | +| BadRatingCount | Describes the number of making a bad evaluation of the scene. | | O | + +# Appendix I + +## Examples of SBM for IPTV overall workflow with Recommendation ITU-T H.753 + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Use case 1: Scene-based VOD clip service workflow + +These days consumers view TV programmes or movies on the new emerging smart devices such as smart phones or tablets instead of traditional TV. In addition, watching a video on demand (VOD) clip instead of a full video is a new trend. + +Figure I.1 shows a use case of a scene-based VOD clip service. + +**Step 1:** A metadata generator generates SBM by using a script, crowdsourced data and the scene information. + +**Step 2:** The scene extractor divides broadcast contents into a series of shots and it then binds the scenes with semantic units from script analysis. + +**Step 3:** The VOD clip server encodes the split scenes into VOD clips and can generate a video story expressed with a story graph. + +**Step 4:** The contents and the VOD clips are provided to a user via an IPTV network. + +**Step 5:** A user can search a VOD clip on the second screen device. + +![Diagram of Scene-based VOD clip service workflow](df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg) + +The diagram illustrates the scene-based VOD clip service workflow across three main entities: Content/service provider, Network, and End-user. + +- Content/service provider:** This section, labeled 'SBM service platform', contains several components: 'Contents' (represented by a film reel icon), 'Caption extractor', 'Scene extractor', 'Metadata generator', 'SNS manager', 'Crowdsource', and 'VOD clip server'. The workflow steps are numbered: ① 'Metadata generation' (involving Script, SNS manager, and Metadata generator), ② 'Scene split' (involving Contents and Scene extractor), and ③ 'VOD clip generation' (involving Scene extractor and VOD clip server). +- Network:** Represented by a central green cloud-like shape, it acts as a conduit for data flow between the provider and the user. +- End-user:** This section shows the user's interaction. It includes a 'TV' (top) with the text 'User: I want to only watch highlight scenes.', another 'TV' (middle) with a smartphone icon, and 'VOD providers' (bottom). Step ④ 'VOD clip' shows an arrow from the Network to the top TV. Step ⑤ 'VOD clip search' shows an arrow from the middle TV/phone to the VOD providers. + +Diagram of Scene-based VOD clip service workflow + +H.753(19)\_FI.1 + +Figure I.1 – Scene-based VOD clip service + +## I.2 Use case 2: Scene-based additional service workflow + +While consumers watch a TV programme on a traditional TV they survey or search additional information on the second screen. Operators can provide additional services such as product advertisement and mesh-up services using SBM. + +Figure I.2 shows a use case of a scene-based additional service. + +**Step 1:** A metadata generator generates SBM by using a script, crowdsourced data and the scene information. + +**Step 2:** The scene extractor divides broadcast contents into a series of shots and then it binds the scenes with semantic units from script analysis. + +**Step 3:** The VOD clip server encodes the split scenes into VOD clips and can generate a video story expressed with a story graph. + +**Step 4:** The operators binds an additional service based on the SBM. + +**Step 5:** A user can search a SBM and additional service on the second screen device. + +![Diagram of scene-based additional service architecture showing Content/service provider, Network, and End-user domains.](ac31fdfebb9751f7f10416dfe33bc872_img.jpg) + +The diagram illustrates the architecture of a scene-based additional service, organized into three vertical domains: Content/service provider, Network, and End-user. + +- Content/service provider:** This domain contains the **SBM service platform**, which includes several components: + - Contents:** Input video content. + - Scene extractor:** Processes contents to perform **② Scene split**. + - Caption extractor:** Processes contents to perform **① Metadata generation**. + - Script:** Input script for metadata generation. + - SNS manager:** Provides data for metadata generation. + - Metadata generator:** Generates the Scene-based Metadata (SBM). + - Crowdsource:** Provides data for metadata generation. + - VOD clip server:** Processes split scenes to perform **③ VOD clip generation**. +- Network:** Represented by a central green cloud, it facilitates communication between the provider and the user. +- End-user:** This domain includes: + - TV:** The primary viewing device. + - Second screen device (Smartphone/Tablet):** Used for **⑤ SBM search** and viewing additional services. + - VOD providers:** Receive **④ bind additional service** from the operator. + - Operator:** A text label stating "Operator: I want to provide an advertisement service based on metadata". + +Arrows indicate the flow of data and services: Contents and Script feed into the Scene extractor and Caption extractor respectively. The Scene extractor and Caption extractor feed into the Metadata generator. The Metadata generator feeds into the VOD clip server. The VOD clip server feeds into the Network. The Network feeds into the End-user (TV and second screen device). The End-user (second screen device) feeds back into the Network for **⑤ SBM search**. The Network feeds into the VOD providers for **④ bind additional service**. + +Diagram of scene-based additional service architecture showing Content/service provider, Network, and End-user domains. + +H.753(19)\_FI.2 + +**Figure I.2 – Scene-based additional service** + +# Appendix II + +## An example of web-based APIs for scene-based metadata service + +(This appendix does not form an integral part of this Recommendation.) + +As can be seen in Figure II.1, a web-based API for media service allows client-side SBM applications to access an SBM service platform. The APIs can request basic scene information, location information, music information, and object information in the scene through the APIs, which are described with restful service description language (RSDL). + +![Diagram showing client-side SBM applications sending various requests to an SBM service platform via web-based APIs.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +The diagram illustrates the interaction between client-side SBM applications and an SBM service platform. On the left, a box labeled 'Client-side SBM applications' has five horizontal arrows pointing to the right. These arrows are labeled: 'Request basic scene information', 'Request location information in the scene', 'Request music information in the scene', 'Request object information in the scene', and 'Request statistics information in the scene'. Below these five arrows, there are three vertical dots. The arrows point to a vertical box labeled 'Web-based APIs', which is situated within a larger box labeled 'SBM service platform'. At the bottom right of the diagram, the text 'H.753(19)\_FII.1' is present. + +Diagram showing client-side SBM applications sending various requests to an SBM service platform via web-based APIs. + +Figure II.1 – Example of web-based API for IPTV services + +RSDL is an XML vocabulary for designing and documenting hypermedia-driven RESTful services. RSDL takes a purist hypermedia-driven approach to REST design, requiring that a service have a single entry point and focusing the design on resources, links and media types. + +### II.1 Basic scene information functions + +#### II.1.1 Whole programme retrieval function: ProgramList + +``` + + + GET + + + + + ProgramID + + + ProgramName + + + ChannelID + + + EpisodeCount + + + ProgramHomePageURL + + + TargetNation + + + + +``` + +``` + + + + TargetAge + + + ActorName + CharacterName + + + + + +``` + +#### II.1.2 Whole episode retrieval function: EpisodeList + +``` + + + + GET + + + + ProgramID + + + + + + + + EpisodeID + + + BroadcastingDate + + + BroadcastingTime + + + storyline + + + + + +``` + +#### II.1.3 Whole scene retrieval function: SceneList + +``` + + + + GET + + + + EpisodeID + + + + + + + + SceneID + + + SceneTitle + + + SceneOrder + + + + + +``` + +``` + + + + + + +``` + +#### II.1.4 SBM of a specific episode retrieval function: SceneListByEpisodeID + +``` + + + + GET + + + + EpisodeID + + + + + + + + SceneID + + + SceneTitle + + + SceneOrder + + + SceneStartTime + + + SceneEndTime + + + SceneDuration + + + SceneKeyFrameImageURL + + + SceneURL + + + SceneResolution + + + SceneType + + + PreviousSceneURL + + + NextSceneURL + + + ServiceCategory + + + + + +``` + +#### II.1.5 SBM of a specific scene retrieval function: SceneBySceneID + +``` + + + + GET + + + + SceneID + + + + + + + + SceneID + + + SceneOrder + + + SceneStartTime + + + SceneEndTime + + + SceneDuration + + + SceneKeyframeImageURL + + + EpisodeID + + + ProgramID + + + ChannelID + + + ProgramName + + + EpisodeNumber + + + SceneTitle + + + SceneSynopsis + + + SceneSubtitle + + + SceneSearchKeyword + + + HashTag + + + SceneURL + + + + +``` + +``` + + + ProgramHomePageURL + + + SceneResolution + + + SceneType + + + SceneCategory + + + SceneSubCategory + + + TargetNation + + + TargetAge + + + CharacterName + + + ActorName + + + ServiceCategory + + + ServiceTimeOffSet + + + SceneUploadingDate + + + BroadcastingDate + + + BroadcastingTime + + + BroadcastingDay + + + CodecType + + + PreviousSceneURL + + + NextSceneURL + + + + + +``` + +#### II.1.6 Whole SBM retrieval function: SceneList + +``` + + + + GET + + + +``` + +``` + + + EpisodeID + + + + + + + + SceneID + + + SceneTitle + + + SceneSubtitle + + + SceneOrder + + + SceneKeyFrameImageURL + + + SceneType + + + + + +``` + +#### II.1.7 SBM of a specific time retrieval function: SceneByTime + +``` + + + + GET + + + + ProgramID + + + EpisodeID + + + ServiceTime + + + + + + + + SceneID + + + SceneOrder + + + SceneStartTime + + + SceneEndTime + + + SceneDuration + + + + + +``` + +``` + + + + SceneKeyframeImageURL + + + EpisodeID + + + ProgramID + + + ChannelID + + + ProgramName + + + EpisodeNumber + + + SceneTitle + + + SceneSynopsis + + + SceneSubtitle + + + SceneSearchKeyword + + + HashTag + + + SceneURL + + + ProgramHomePageURL + + + SceneResolution + + + SceneType + + + SceneCategory + + + SceneSubCategory + + + TargetNation + + + TargetAge + + + CharacterName + + + ActorName + + +``` + +``` + + + ServiceCategory + + + ServiceTimeOffSet + + + SceneUploadingDate + + + BroadcastingDate + + + BroadcastingTime + + + BroadcastingDay + + + CodecType + + + PreviousSceneURL + + + NextSceneURL + + + + + +``` + +#### II.1.8 Scene list with a specific keyword retrieval function: SceneListByKeyword + +``` + + + + GET + + + + SceneSearchKeyword + + + + + + + + ProgramID + + + EpisodeID + + + SceneID + + + SceneTitle + + + SceneOrder + + + SceneStartTime + + + +``` + +``` + + SceneEndTime + + + SceneDuration + + + SceneKeyFrameImageURL + + + SceneURL + + + SceneResolution + + + SceneType + + + PreviousSceneURL + + + NextSceneURL + + + + + +``` + +#### II.1.9 Related scene retrieval function: SimilarSceneList + +``` + + + + GET + + + + SceneID + + + + + + + + SceneID + + + SceneOrder + + + SceneKeyframeImageURL + + + SceneTitle + + + SceneURL + + + Similar_scene_ID + + + + + +``` + +#### II.1.10 Most related SBM retrieval function: BestSceneList + +``` + + + GET + + + + SceneID + + + ProgramID + + + EpisodeID + + + BestSceneNumber + + + + + + + + SceneID + + + EpisodeID + + + ProgramID + + + RankingNumber + + + SceneOrder + + + SceneTitle + + + SceneKeyFrameImageURL + + + SceneUploadingDate + + + SceneSearchKeyword + + + ClickCount + + + GoodRatingCount + + + BadRatingCount + + + + +``` + +#### II.1.11 URL of scene clip retrieval function: SceneClipBySceneID + +``` + + + GET + + + + SceneID + + + + + + + + ProgramID + + + EpisodeID + + + SceneID + + + SceneOrder + + + SceneTitle + + + SceneSynopsis + + + SceneStartTime + + + SceneEndTime + + + SceneDuration + + + SceneKeyFrameImageURL + + + SceneURL + + + SceneResolution + + + SceneType + + + PreviousSceneURL + + + NextSceneURL + + + ServiceCategory + + + +``` + +``` + +``` + +#### **II.1.12 URL of scene key frame image retrieval function: KeyFrameImageBySceneID** + +``` + + + GET + + + + SceneID + + + + + + + + SceneKeyframeImageURL + + + + +``` + +#### **II.1.13 Title of a specific scene retrieval function: SceneTitleBySceneID** + +``` + + + GET + + + + SceneID + + + + + + + SceneTitle + + + SceneSynopsis + + + SceneSubtitle + + + HashTag + + + SceneCategory + + + SceneSubCategory + + + ServiceCategory + + + ChannelID + + + +``` + +### II.2 Location information functions + +#### II.2.1 Location information meta retrieval function: LocationMetaBySceneID + +``` + + + GET + + + + SceneID + + + + + + + LocationName + + + LocationAddress + + + LocationURL + + + +``` + +### II.3 Music information functions + +#### II.3.1 Music information meta retrieval function: MusicMetaBySceneID + +``` + + + GET + + + + SceneID + + + + + + + MusicTitles + + + MusicGenre + + + MusicSinger + + + MusicURL + + + MusicLyrics + + + MusicVideoURL + + + +``` + +### II.4 Object information functions + +#### II.4.1 Object information meta retrieval function: ObjectBySceneID + +``` + + + GET + + + + SceneID + + + ProgramID + + + EpisodeID + + + + + + + + SceneID + + + ObjectID + + + ObjectName + + + ObjectCategory + + + ObjectColor + + + ObjectSize + + + + +``` + +#### II.4.2 SBM of a specific object retrieval function: SceneWithObject + +``` + + + GET + + + + ObjectID + + + EpisodeID + + + ProgramID + + + + + +``` + +``` + + + + SceneID + + + SceneKeyFrameImageURL + + + SceneOrder + + + SceneTitle + + + SceneSynopsis + + + SceneDuration + + + SceneURL + + + + + +``` + +### II.5 Statistics information functions + +#### II.5.1 Statistics information meta retrieval function: StatisticsMetaBySceneID + +``` + + + + GET + + + + SceneID + + + + + + + + ClickCount + + + GoodRatingCount + + + BadRatingCount + + + + + +``` + +# Appendix III + +## RSDL schema + +(This appendix does not form an integral part of this Recommendation.) + +This XML schema is based on Pasternak's work [b-RSDL] and it was adapted to SBM web-based API. + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +# Bibliography + +- [b-ITU-T H.622] Recommendation ITU-T H.622 (2008), *A generic home network architecture with support for multimedia services.* +- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2015), *Designations for interconnections among operators' networks.* +- [b-ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) - The business process framework.* +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.* +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks.* +- [b-ITU-T IPTVFG] ITU-T IPTV Focus Group Proceedings (2008). + +- [b-ETSI TS 102 822-1] ETSI TS 102 822-1 V1.3.1 (2006), *Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 1: Benchmark Features.* +- [b-RSDL] Balisage: The Markup Conference Proceedings (2013). + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.760-200903-I_PDF-E/raw.md b/marked/H/T-REC-H.760-200903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a2b7929d168ee33e570fd5531f9537d9c15153cd --- /dev/null +++ b/marked/H/T-REC-H.760-200903-I_PDF-E/raw.md @@ -0,0 +1,628 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.760** + +(03/2009) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +IPTV multimedia application frameworks + +# --- **Overview of multimedia application frameworks for IPTV services** + +Recommendation ITU-T H.760 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo + +International +Telecommunication +Union + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T H.760** + +# **Overview of multimedia application frameworks for IPTV services** + +## **Summary** + +Recommendation ITU-T H.760 identifies and describes the relevant standards of multimedia application frameworks for interoperability and harmonization in IPTV services. It gives an overview of standards for declarative application frameworks as well as standards for procedural application frameworks. For declarative application frameworks, standards to be used for IPTV are described (such as HTML, CSS, DOM, ECMAScript, SVG, BML, MHEG-5 and Ginga-NCL), while procedural application frameworks are represented by GEM-based frameworks. It also contains descriptions of ISO/IEC International Standards for application frameworks, namely M3M, BIFS and LASEr. Recommendation ITU-T H.760 also has an annex on common usage of web-related technologies. + +###### **Source** + +Recommendation ITU-T H.760 was approved on 16 March 2009 by ITU-T Study Group 16 (2009-2012) under Recommendation ITU-T A.8 procedures. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|---------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Standards for declarative application frameworks ..... | 3 | +| 5.1 Binary format for scene (BIFS)..... | 3 | +| 5.2 Broadcasting markup language (BML) ..... | 5 | +| 5.3 CEA-2014..... | 6 | +| 5.4 Cascading style sheet (CSS)..... | 7 | +| 5.5 Document object model (DOM)..... | 7 | +| 5.6 Digital video broadcasting hypertext markup language (DVB-HTML) ..... | 7 | +| 5.7 ECMAScript..... | 8 | +| 5.8 Hypertext markup language (HTML) ..... | 8 | +| 5.9 Lightweight application scene representation (LASER) and simple aggregation format..... | 9 | +| 5.10 MHEG-5 ..... | 10 | +| 5.11 Nested context language (NCL) ..... | 10 | +| 5.12 Scalable vector graphics (SVG) ..... | 11 | +| 5.13 Worldwide TV markup language (WTVML) ..... | 12 | +| 6 Standards for procedural application frameworks..... | 12 | +| 6.1 GEM based application frameworks ..... | 13 | +| 7 Other related standards ..... | 15 | +| 7.1 MPEG multimedia middleware (M3W)..... | 15 | +| Annex A – Common usage ..... | 16 | +| A.1 BML profile..... | 16 | +| A.2 CEA-2014..... | 16 | +| A.3 DVB-HTML profile ..... | 16 | +| A.4 SVG profiles..... | 16 | +| Bibliography..... | 17 | + + + +# Overview of multimedia application frameworks for IPTV services + +# 1 Scope + +This Recommendation identifies and describes the relevant standards for interoperability and harmonization among IPTV multimedia application frameworks. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T J.201] Recommendation ITU-T J.201 (2008), *Harmonization of declarative content format for interactive television applications.* +- [ITU-T T.170] Recommendation ITU-T T.170 (1998), *Framework of the T.170-Series of Recommendations.* +- [ITU-T T.172] Recommendation ITU-T T.172 (1998) | ISO/IEC 13522-5:1997, *MHEG-5 – Support for base-level interactive applications.* +- [ITU-T T.175] Recommendation ITU-T T.175 (1998), *Application programming interface (API) for MHEG-5.* +- [ITU-R BT.1699-1] Recommendation ITU-R BT.1699-1 (2009), *Harmonization of declarative application formats for interactive TV.* +- [ITU-R BT.1722-1] Recommendation ITU-R BT.1722-1 (2007), *Harmonization of the instruction set for the execution engine for interactive TV applications.* +- [ANSI/SCTE 90-1] ANSI/SCTE 90-1 (2005), *SCTE Application Platform Standard OCAP 1.0 Profile.* +- [ARIB STD-B24] ARIB STD-B24 Ver5.3 (2009), *Data coding and Transmission Specification for Digital Broadcasting; ARIB, Association of Radio Industries and Businesses (Japan).* +- [ATSC A/101A] ATSC Document A/101 A (2009), *ATSC Standard: Advanced Common Application Platform (ACAP).* +- [CEA-2014] CEA-2014 (2006), *Web-based Protocol and Framework for Remote User Interface on UPnP Networks and the Internet (Web4CE).* +- [ETSI TS 102 322] ETSI TS 102 322 V1.1.1 (2004), *Specification for a Lightweight Microbrowser for interactive TV applications, based on and compatible with WML.* +- [ETSI TS 102 812] ETSI TS 102 812 V1.2.2 (2006), *Digital Video Broadcasting (DVB) – Multimedia Home Platform (MHP) Specification 1.1.1.* +- [ETSI TS 102 819] ETSI TS 102 819 V1.4.1 (2008), *Digital Video Broadcasting (DVB) – Globally Executable MHP version 1.0.3 (GEM 1.0.3).* + +- [ISO/IEC 14496-11] ISO/IEC 14496-11 (2005), *Information technology – Coding of audio-visual objects – Part 11: Scene description and application engine.* +- [ISO/IEC 14496-20] ISO/IEC 14496-20 (2008), *Information technology – Coding of audio-visual objects – Part 20: Lightweight Application Scene Representation (LASEr) and Simple Aggregation Format (SAF).* +- [ISO/IEC 16262] ISO/IEC 16262 (2002), *Information technology – ECMAScript language specification.* +- [ISO/IEC 23004.x] ISO/IEC 23004.x-series (2007), *Information technology – Multimedia Middleware.* +- [W3C CSS1] Cascading Style Sheets, level 1 (2008), *W3C Recommendations: Cascading Style Sheets, level 1.* +- [W3C DOM1] Document Object Model (DOM) Level 1 Specification Version 1.0 (1998), *W3C Recommendation: Document Object Model (DOM) Level 1 Specification.* +- [W3C DOM2] Document Object Model (DOM) Level 2 Core Specification Version 1.0 (2000), *W3C Recommendation: Document Object Model (DOM) Level 2 Core Specification.* +- [W3C SVG 1.1] Scalable Vector Graphics (SVG) 1.1 Specification (2003), *W3C Recommendation: Scalable Vector Graphics (SVC) 1.1 Specification.* +- [W3C XHTML] XHTML 1.0 Second Edition (2002), *W3C Recommendation: XHTML 1.0, The Extensible HyperText Markup Language (Second Edition).* + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This clause is intentionally left blank. + +## 3.2 Terms defined in this Recommendation + +This clause is intentionally left blank. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----------|-----------------------------------------------------| +| ACAP | Advanced Common Application Platform | +| API | Application Programming Interface | +| BD-J | Blu-ray Disc Java | +| BIFS | BInary Format for Scene | +| BIFS-Anim | BIFS Animation | +| BML | Broadcast Markup Language | +| CE | Consumer Electronics | +| CSS | Cascading Style Sheet | +| DASE | Digital television Application Software Environment | +| DDE-T | Declarative Data Essence-Transitional | + +| | | +|---------|---------------------------------------------------------------------------------------------| +| DOM | Document Object Model | +| EE | Execution Engine | +| FBA | Face and Body Animation | +| GEM | Globally Executable MHP | +| HDTV | High-Definition Digital TeleVision | +| ISDB-T | Integrated Services Digital Broadcasting-Terrestrial | +| LASER | Lightweight Application Scene Representation | +| M3W | MPEG Multimedia Middleware | +| MHEG | Multimedia and Hypermedia information coding Experts Group | +| MHP | Multimedia Home Platform | +| NCL | Nested Context Language | +| OCAP | Open Cable Application Platform | +| PE | Presentation Engine | +| S&N | Synthetic and Natural | +| SAF | Simple Aggregation Format | +| SBTVD-T | Sistema Brasileiro de Televisão Digital Terrestre (Terrestrial Brazilian digital TV system) | +| SGML | Standard Generalized Markup Language | +| SMIL | Synchronized Multimedia Integration Language | +| SVG | Scalable Vector Graphics | +| UI | User Interface | +| VCR | VideoCassette Recorder | +| VM | Virtual Machine | +| XHTML | Extensible HyperText Markup Language | +| XML | Extensible Mark-up Language | + +## 5 Standards for declarative application frameworks + +This clause describes the standards for declarative application frameworks in an alphabetical order, without implying any specific order or preference. + +The declarative application platform is a framework on which applications written by a markup language (e.g., HTML) with or without script language (e.g., ECMAScript) can run. + +### 5.1 Binary format for scene (BIFS) + +BIFS [ISO/IEC 14496-11] is the scene description language standardized by ISO as a part of the MPEG-4 family of standards. It is designed to allow for the efficient representation of dynamic and interactive presentations, comprising two and three dimensional (2D & 3D) graphics, images, text and audiovisual material. The representation of such a presentation includes the description of the spatial and temporal organization of the different scene components as well as user-interaction and animations. + +The main features of MPEG-4 BIFS are the following: + +- Seamless embedding of audio/video content: MPEG-4 BIFS allows integration and control of different audio/video objects seamlessly in a scene. +- Rich set of 2D/3D graphical constructs: MPEG-4 BIFS provides a rich set of graphical constructs which enable 2D and 3D graphics. BIFS also provides tools that enable easy authoring of complex face and body animation, tools for 3D mesh encoding, and representation of 2D and 3D natural and synthetic sound models. +- Local and remote interactivity: BIFS defines elements that can interact with the client-side scene as well as with remote servers. Interactive elements allow for text input, mouse events, and other input devices that can trigger a variety of behaviours. +- Local and remote animations: scene properties, such as object positions, colours, and even shapes, etc., can be animated using either predefined scene descriptions or via streams sent from a server. +- Reuse of content: MPEG-4 scenes can contain references to streamed sub-scenes. This means that content can be easily reused, a powerful way to create a very rich user experience from relatively simple building blocks. +- Scripted behaviour: MPEG-4 scenes can have two types of scripted behaviour. A Java API can control and manipulate the scene graph, as well as built-in ECMA script (JavaScript) support that can be used to create complex behaviours, animations, and interactivity. +- Streamable scene-description: the spatial and temporal graphic layout is carried in a BIFS-Command stream. Such a stream operates on the scene-graph through commands which replace, delete and insert elements in the scene-graph. +- Accurate synchronization: audio/visual content can be tightly synchronized with other A/V content, client-side, and server-driven scene animation, due to the underlying MPEG-4 Systems layer. +- Compression: the scene description is converted to binary data and compressed in an efficient way. + +Figure 5-1 summarizes the different components of BIFS. + +![Diagram of MPEG-4 BIFS scene description components](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the components of an MPEG-4 BIFS scene description. On the left, two pink rectangular blocks labeled 'BIFS-Command' and 'BIFS-Anim' have arrows pointing to a central vertical blue block labeled 'COMPOSITOR'. From the 'COMPOSITOR' block, seven arrows point to a stack of seven horizontal blocks on the right. These blocks, from top to bottom, are: '2D Nodes' (light green), 'Audio Nodes' (dark green), '3D Nodes' (dark green), '2D+3D Nodes' (light green), 'Behavior & Inter' (dark green), 'S & N Sound' (light green), and 'FBA' (light green). A legend at the bottom left shows three colored boxes: a dark green box for 'VRML Nodes', a pink box for 'MPEG-4 Streams', and a light green box for 'New MPEG-4 Nodes'. The text 'H.760(09)\_F5-1' is located at the bottom right of the diagram. + +Diagram of MPEG-4 BIFS scene description components + +**Figure 5-1 – MPEG-4 BIFS scene description** + +### 5.2 Broadcasting markup language (BML) + +BML (see [ARIB STD-B24] and [ITU-T J.201]) is a declarative application specification for multimedia broadcasting in Japan, standardized by the Association of Radio Industries and Businesses (ARIB). BML consists of XHTML 1.0, CSS 1 and CSS 2, Document Object Model (DOM) 1 and DOM 2, and ECMA-262. BML was revised to include additional functionalities for receivers with digital storage and for terrestrial digital broadcasting including mobile reception. + +The specification of the terrestrial integrated services digital broadcasting (ISDB-T) multimedia coding scheme was first based on that of multimedia and hypermedia information coding experts group (MHEG). However, since March 1999, ARIB started developing an XML specification for multimedia coding scheme based on the functionalities of MHEG. This contributed to the development of an XML application language, BML, that enables the presentation of an XML file on BML browsers. The ARIB data broadcasting system standards were enacted as BML in October 1999. + +A BML application can be based on synchronization and spatial-temporal relationships of multiple media formats, structural composition, event-action associations, navigation, and user interaction capabilities just as MHEG. BML defines an additional API and object for broadcasting using ECMAScript. + +The semantics of BML is based on the following minimum set of MHEG classes: + +- Application Class +- Scene Class +- Link Class +- Action Class. + +BML is applied to reference model for data broadcasting services that are carried out as part of the digital broadcasting. Figure 5-2 shows the structure of BML, which contains the following blocks: + +- Data coding: + - Coding mono-media (1): Coding system for character string and bit map, etc. used in multimedia. + - Coding of subtitle, superimpose (2): Coding system for subtitle and superimpose. +- XML-based multimedia coding scheme: + - Multimedia coding (3): Coding system of XML based system adopted as multimedia coding system and its profile. +- Data transmission specification: + - Content transmission format (4): Content transmission format of data carousel transmission method, etc. to transmit content. + - Subtitle and superimpose transmission format (5): Independent PES transmission format to transmit subtitle and superimpose. + +![Figure 5-2: System Structure of BML. This block diagram shows the flow from Production system to Viewer. The Production system includes Multi-media content production and AV/subtitle production. Base-band processing includes Program scheduler, EPG information program index generation, Content transmission system, Base-band Control system, AV encoder, and Superimposing. Transmission system includes Service information (Section transmission system), Multimedia coding, Mono-media coding, AV transmission system (PES transmission system), Subtitle superimpose coding system, and Subtitle, superimpose transmission system (independent PES transmission system). A central MPEG-2 TS block is labeled with numbers (1) through (5). The final stage is Multiple / scramble / modulation, which leads to the Viewer (Company A mode receiver, Company B mode receiver, Company C mode receiver).](d4af765160d04ecef538e5066006dc77_img.jpg) + +Figure 5-2: System Structure of BML. This block diagram shows the flow from Production system to Viewer. The Production system includes Multi-media content production and AV/subtitle production. Base-band processing includes Program scheduler, EPG information program index generation, Content transmission system, Base-band Control system, AV encoder, and Superimposing. Transmission system includes Service information (Section transmission system), Multimedia coding, Mono-media coding, AV transmission system (PES transmission system), Subtitle superimpose coding system, and Subtitle, superimpose transmission system (independent PES transmission system). A central MPEG-2 TS block is labeled with numbers (1) through (5). The final stage is Multiple / scramble / modulation, which leads to the Viewer (Company A mode receiver, Company B mode receiver, Company C mode receiver). + +Figure 5-2 – System Structure of BML + +### 5.3 CEA-2014 + +CEA-2014 is a remote user interface specification that allows a user interface to be remotely displayed on devices. It is based on existing web rendering technologies for consumer electronics (CE) browser with Worldwide Web Consortium (W3C) tags, XHTML 1, ECMA-262, CSS TV profile and DOM 2. CEA-2014 is a web-based protocol and framework for remote user interface (UI) on UPnP home network and over Internet. Two service domains are defined, as shown in Figure 5-3. + +![Figure 5-3: Service model of CEA-2014 (remote user interface). This diagram illustrates the service model. On the left, 'Web services' (XHTML, DOM2, ECMAScript) and 'IPTV service' are connected to a central 'Internet' cloud. Below the cloud is a 'Walled garden portal'. On the right, a 'Home network' (containing DTV, IPSTB, PMP, PC, and Printer) is also connected to the 'Internet' cloud. A double-headed arrow at the bottom indicates two domains: 'Internet CEA 2014(CE-HTML)' and 'H/N CEA 2014(CE-HTML)'. A small code 'H.760(09)_F5-3' is in the bottom right corner.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +Figure 5-3: Service model of CEA-2014 (remote user interface). This diagram illustrates the service model. On the left, 'Web services' (XHTML, DOM2, ECMAScript) and 'IPTV service' are connected to a central 'Internet' cloud. Below the cloud is a 'Walled garden portal'. On the right, a 'Home network' (containing DTV, IPSTB, PMP, PC, and Printer) is also connected to the 'Internet' cloud. A double-headed arrow at the bottom indicates two domains: 'Internet CEA 2014(CE-HTML)' and 'H/N CEA 2014(CE-HTML)'. A small code 'H.760(09)\_F5-3' is in the bottom right corner. + +Figure 5-3 – Service model of CEA-2014 +(remote user interface) + +CEA-2014 defines the mechanisms allowing a user interface to be remotely displayed on and controlled by devices or control points other than the one hosting the logic. The basic device operations are based on the UPnP Device Architecture v1.0 for UPnP networks and UPnP devices in the home. The specification also allows the remote display of user interfaces provided by third-party Internet services on UPnP devices in the home, and covers UI capabilities for TVs, mobile phones and portable devices. + +A major component of CEA-2014 is the CE-HTML profile that uses XHTML content to define user interfaces that can be rendered on screens with different resolutions and sizes ranging from HDTV screens to mobile-phone displays. + +### 5.4 Cascading style sheet (CSS) + +CSS is a style sheet language specified by W3C that is used to describe the presentation (e.g., fonts, colours and spacing) of a document written in a markup language. CSS is human readable and writable, and expresses style in common desktop publishing terminology. + +CSS has been in use since October 1995 using the media type **text/css** without registration. + +A CSS can be either linked to a document through a URI or included in the document. + +A superset of [W3C CSS1] and [b-W3C CSS2] includes a number of new capabilities like absolute, relative, and fixed positioning of elements, the concept of media types, support for aural style sheets and bidirectional text, and new font properties such as shadows. + +[b-W3C CSS TV Profile] specifies subsets of [b-W3C CSS2], e.g., colour specifications tailored to TV devices. + +CSS does not constitute by itself a multimedia framework, but is used with some markup languages such as BML, CEA-2014, and SVG. CSS 1 and CSS 2 are used with BML. CSS TV Profile is used with CEA-2014, and CSS 2 is used with SVG and DVB-HTML. + +### 5.5 Document object model (DOM) + +DOM 2.0 [W3C DOM2] defines the Document Object Model Level 2 Core, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content and structure of documents. The Document Object Model Level 2 Core builds on the Document Object Model Level 1 Core. + +The DOM Level 2 Core is made of a set of core interfaces to create and manipulate the structure and contents of a document. The Core also contains specialized interfaces dedicated to XML. + +DOM does not constitute by itself multimedia framework but is used with some markup languages such as BML, CEA-2014, and SVG. DOM 1 and DOM 2 are used with BML and SVG 1.1. SVG Tiny is using uDOM. CEA-2014 and DVB-HTML are using DOM 2. + +### 5.6 Digital video broadcasting hypertext markup language (DVB-HTML) + +Digital video broadcasting hypertext markup language (DVB-HTML) (see [ITU-T J.201]) is a standard for allowing digital televisions to access Internet content. It is an optional part of the larger MHP 1.1 standard of DVB. + +The specification is based around a modularized version of XHTML 1.1, and also includes CSS 2.0, DOM 2.0, and ECMA-262 (also known as ECMAScript). + +Among other things, MHP 1.1 specifies the Internet access profile, in which applications can control the basic operations of Open Internet resident clients (web browser, e-mail and news client). + +Figure 5-4 outlines the basic architecture of MHP 1.1 and the relationship between the DVB-HTML optional application type and the DVB-J application type. + +![Diagram of MHP 1.1 and DVB-HTML architecture showing the interaction between DVB-HTML and DVB-J applications.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +The diagram illustrates the architecture of MHP 1.1 and DVB-HTML. At the top, three application types are shown: DVB-HTML applications, Hybrid applications, and DVB-J applications. Below these, a horizontal bar represents the MHP APIs. The main area is divided into two vertical sections. The left section, labeled 'DOM' and 'DVB-HTML option', contains an oval labeled 'ECMAScript, CSS, DVB-HTML interpreters'. The right section, labeled 'DVB-J', contains an oval labeled 'Java VM'. A double-headed arrow labeled 'Bridge' connects the two sections. At the bottom, a horizontal bar represents 'Platform resources'. The diagram is labeled 'H.760(09)\_F5-4' in the bottom right corner. + +Diagram of MHP 1.1 and DVB-HTML architecture showing the interaction between DVB-HTML and DVB-J applications. + +**Figure 5-4 – MHP 1.1 and DVB-HTML** + +### 5.7 ECMAScript + +ECMAScript [ISO/IEC 16262] is a scripting programming language that is used on the web and is often referred to as JavaScript or JScript, after the two earlier implementations of the specification. + +ECMAScript is supported in many applications. ECMAScript is also included as a component in many presentation engines (PEs) such as BML and DVB-HTML, which are used for digital data broadcasting. Some implementations have a completely different set of libraries; making applications written in one dialect of ECMAScript will not necessarily work in another. + +ECMAScript is an object-oriented programming language for performing computations and manipulating computational objects within a host environment. It was originally designed to be a web scripting language, providing a mechanism to enliven web pages in browsers and to perform server computation as part of a web-based client-server architecture. + +A web browser provides an ECMAScript host environment for client-side computation including, for example, objects that represent windows, menus, pop-ups, dialog boxes, text areas, anchors, frames, history, cookies, and input/output. Further, the host environment provides a means to attach scripting code to events such as change of focus, page and image loading, unloading, error and abort, selection, form submission, and mouse actions. Scripting code appears within the HTML and the displayed page is a combination of user interface elements and fixed and computed text and images. The scripting code is reactive to user interaction and there is no need for a main program. + +A web server provides a different host environment for server-side computation including objects representing requests, clients, and files; and mechanisms to lock and share data. By using browser-side and server-side scripting together, it is possible to distribute computation between the client and server while providing a customized user interface for web-based applications. + +ECMAScript does not constitute by itself a multimedia framework but is used with some markup languages such as BML, CEA-2014, DVB-HTML and SVG. + +### 5.8 Hypertext markup language (HTML) + +HTML (hypertext markup language) is the predominant markup language for web pages. It provides a means to describe the structure of text-based information in a document – by denoting certain text as links, headings, paragraphs, lists, and so on – and to supplement that text with interactive forms, embedded images, and other objects. HTML is written in the form of tags, surrounded by angle brackets. HTML can also describe, to some degree, the appearance and semantics of a document, and can include embedded scripting language code (such as ECMAScript) that can affect the behaviour of web browsers and other HTML processors. + +Elements are the basic structure for HTML markup. Elements have two basic properties: attributes and content. Each attribute and each element's content has certain restrictions that must be followed for an HTML document to be considered valid. An element usually has a start tag (e.g., ****) and an end tag (e.g., ****). The element's attributes are contained in the start tag and content is located between the tags (e.g., **Content**). Some elements, such as **
    **, do not have any content and must not have a closing tag. Listed below are several types of markup elements used in HTML. + +#### 5.8.1 HTML and XHTML + +HTML is also often used to refer to content in specific languages, such as a MIME type **text/html**, or even more broadly as a generic term for HTML, whether in its XML-descended form (such as XHTML 1.0 [W3C XHTML] and later) or its form descended directly from SGML (such as HTML 4.01 and earlier). + +One difference in the latest HTML specifications lies in the distinction between the SGML-based specification and the XML-based specification. The XML-based specification is usually called XHTML to distinguish it clearly from the more traditional definition; however, the root element name continues to be 'html' even in the XHTML-specified HTML. W3C intended XHTML 1.0 to be identical to HTML 4.01 except where limitations of XML over the more complex SGML required workarounds. Because XHTML and HTML are closely related, they are sometimes documented in parallel. In such circumstances, some authors conflate the two names as (X)HTML or X(HTML). + +Aside from the different opening declarations for a document, the differences between an HTML 4.01 and XHTML 1.0 document – in each of the corresponding document type definitions – are largely syntactic. The underlying syntax of HTML allows many shortcuts that XHTML does not, such as elements with optional opening or closing tags, and even EMPTY elements which must not have an end tag. By contrast, XHTML requires all elements to have an opening tag or a closing tag. XHTML, however, also introduces a new shortcut: an XHTML tag may be opened and closed within the same tag, by including a slash before the end of the tag like this: **
    **. The introduction of this shorthand, which is not used in the SGML declaration for HTML 4.01, may confuse earlier software unfamiliar with this new convention. + +#### 5.8.2 Dynamic HTML + +Combined with a client-side scripting language (such as ECMAScript), a presentation definition language (such as CSS) and DOM, HTML is often used to create interactive and animated web sites. Such a use is often called dynamic HTML. + +Dynamic HTML allows a scripting language to change variables in a page's definition language, which in turn affects the look and function of otherwise "static" HTML page content, after the page has been fully loaded and during the viewing process. + +### 5.9 Lightweight application scene representation (LASER) and simple aggregation format + +MPEG-4 Part 20 [ISO/IEC 14496-20] is a specification designed for representing and delivering rich-media services to resource-constrained devices such as mobile phones. It defines two binary formats: lightweight application scene representation (LASER), a binary format for encoding 2D scenes, including vector graphics, and timed modifications of the scene; and simple aggregation format (SAF), a binary format for aggregating in a single stream LASER content with audio/video streams. + +The LASER specification has been designed to allow the representation of 2D scenes describing rich-media services for constrained devices. A rich-media service features a dynamic and interactive presentation comprising 2D vector graphics, images, text and audiovisual material. The + +representation of such a presentation includes describing the spatial and temporal organization of its different elements as well as its possible interactions and animations. + +The SAF specification defines tools to enable the transport of LASER content along with its attached audiovisual material according to these requirements. The SAF specification defines a binary format for a SAF stream, made of a LASER stream with any type of media stream. SAF streams can be delivered using many delivery mechanisms: download-and-play, progressive download, streaming or broadcasting. To achieve reactivity, the SAF specification defines the concept of cache unit which allows sending in advance sub-content which will be used later on in the presentation. + +### 5.10 MHEG-5 + +MHEG-5 (see [ITU-T T.170], [ITU-T T.172], [ITU-T T.175], [b-ETSI ES 202 184]) represents an application as a set of scenes that contain objects common to all scenes. A multimedia application can be conceived as a set of self-contained objects based on synchronization and spatio-temporal relationships of multiple media formats, structural composition, event-action associations, navigation, and user interaction capabilities. Controlling the playback of time-dependent content (like streams of multiplexed audiovisual data) requires specific support. These streams demand video cassette recorder (VCR) control functions (play, pause, fast forward, etc.), as well as the capability to manage events generated during their presentation. For example, rendering text subtitles can be synchronized with timecode events generated during the playback of a stream. + +A scene supports the spatially and temporally coordinated presentation of audiovisual content consisting of graphics, bitmaps, text, and streams (based on the multiplex of audio and video components). Interaction can be performed via graphic elements like buttons, sliders, text entry boxes, and hypertext selections. Every scene, as well as an entire application, is a self-contained entity that can represent its localized behaviour by links that are event-action associations. Events can be generated by users, expiration of timers, playback of streams, and other conditions within the run-time environment. + +The global scope of MHEG-5 is to define the syntax and semantics of a set of object classes that can be used for interoperability of multimedia applications across minimal-resources platforms. The developed applications will reside on a server, and as portions of the application are needed, they will be downloaded to the client. In a broadcast environment, this download mechanism could rely, for instance, on cyclic rebroadcast of all portions of the application. It is the responsibility of the client to have a runtime that interprets the application parts, presents the application to the user, and handles the local interaction with the user. + +### 5.11 Nested context language (NCL) + +Nested context language (NCL) is an XML application language that allows authors to write interactive multimedia presentations [b-ITU-T H.761]. Using this language an author can declaratively describe the spatio-temporal behaviour of a multimedia presentation, associate hyperlinks (viewer interaction) with media objects, define alternatives for content and for content presentation (adaptation), and describe the layout of the presentation on multiple exhibition devices. NCL is part of the data coding specifications of the Terrestrial Brazilian Digital TV System (SBTVD-T), and comprises the declarative language used by the presentation engine Ginga-NCL of the SBTVD-T middleware (Ginga). + +#### 5.11.1 Ginga and Ginga-NCL + +Figure 5-5 depicts an overview of the architecture of the Ginga middleware. It consists of three main modules: the Ginga-cc (common core), the Ginga-NCL declarative environment and the Ginga-J imperative environment. + +![Diagram of Ginga architecture showing layers: Operating system, Ginga – Common core (JVM), Ginga – Specific service, Declarative environment (Ginga-NCL), Bridge, and Imperative environment (Ginga-J).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +The diagram illustrates the Ginga architecture as a layered structure. At the top is a yellow layer labeled 'Operating system'. Below it is a green layer labeled 'Ginga – Common core', with a blue triangle on the right labeled 'JVM'. The next layer is a red layer labeled 'Ginga – Specific service'. The bottom section is a large pink rectangle divided into three parts: 'Declarative environment (Ginga-NCL)' on the left, 'Imperative environment (Ginga-J)' on the right, and a central vertical pink strip labeled 'Bridge' with a double-headed orange arrow. The text 'H.760(09)\_F5-5' is located at the bottom right of the diagram. + +Diagram of Ginga architecture showing layers: Operating system, Ginga – Common core (JVM), Ginga – Specific service, Declarative environment (Ginga-NCL), Bridge, and Imperative environment (Ginga-J). + +**Figure 5-5 – Ginga architecture** + +Ginga-NCL is the logical subsystem of the Ginga system that processes NCL documents. A key component of Ginga-NCL is the declarative content decoding engine (NCL user agent). The NCL engine is in charge of receiving a NCL document and controlling its presentation, trying to guarantee that the specified relationships among media objects are respected. + +#### 5.11.2 NCL and the NCL media players + +[b-ABNT NBR 15606-2] and [b-ABNT NBR 15606-5] specify the NCL application language profile for SBTVD fixed and portable receivers, respectively. + +NCL defines the glue that holds media objects together in a multimedia presentation. Thus, an NCL document only defines how media objects are structured and related, in time and space. As a glue language, it does not restrict or prescribe the media-object content types. In this sense, we can have image objects (GIF, JPEG, etc.), video objects (MPEG, MOV, etc.), audio objects (MP3, WMA etc.), text objects (TXT, PDF etc.), imperative objects (Xlet, Lua, etc.), etc., as NCL media objects. Which media objects are supported depends on the media players that are embedded in the NCL engine (NCL user agent). One of these players could be a main audio/video decoder/player, usually implemented in a digital TV receiver's hardware. In this way, note that the main video and audio streams are treated like all other media objects that can be related using NCL. + +NCL also treats an HTML document as one of its possible media objects. Therefore, Ginga can run any HTML application developed for ISDB, DVB and ATSC, depending only on the XHTML player implementation. Therefore, NCL does not substitute but embed XHTML-based documents. + +NCL also includes support for media objects that contain imperative code, extending the language basic model, adding decision-making features that were otherwise not possible. NCL allows imperative objects with Java code and with Lua code. + +#### 5.11.3 The scripting language Lua + +Lua is the scripting language of NCL. Lua combines simple procedural syntax with powerful data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, runs by interpreting byte-code for a register-based virtual machine, and has automatic memory management with incremental garbage collection. + +Among all these Lua's characteristics and advantages as a scripting language, it should be stressed its efficiency. Lua is an efficient dynamic language (interpreted, dynamic typing). + +Both NCL and Lua engines are available as free software. + +### 5.12 Scalable vector graphics (SVG) + +SVG [W3C SVG 1.1] is a language for describing two-dimensional graphics and graphical applications in XML. SVG allows for three types of graphic objects: vector graphic shapes (e.g., + +paths consisting of straight lines and curves), images and text. Graphical objects can be grouped, styled, transformed and composited into previously rendered objects. The feature set includes nested transformations, clipping paths, alpha masks, filter effects and template objects. + +SVG drawings can be interactive and dynamic. Animations can be defined and triggered either declaratively (i.e., by embedding SVG animation elements in SVG content) or via scripting. Sophisticated applications of SVG are possible by use of a supplemental scripting language which accesses SVG DOM, which provides complete access to all elements, attributes and properties. + +SVG Basic and SVG Tiny are targeted to resource-limited devices and are part of the 3GPP platform for third generation mobile phones. SVG Print is a set of guidelines to produce final-form documents in XML suitable for archiving and printing. + +### **5.13 Worldwide TV markup language (WTVML)** + +Worldwide TV Markup Language (WTVML) [ETSI TS 102 322] is a content format for the delivery of interactive TV applications using Internet servers. A WTVML interactive television technology platform comprises a micro-browser, a markup language, and a significant collection of associated software tools and services. The micro-browser and markup language are both based upon the Open Mobile Alliance WML 1.3 specification. It has all the required elements, attributes and events necessary to describe the user interface and user interaction models for the majority of interactive TV services. + +The format supports key features to enable service-oriented applications and also provides a balance between the explicit layout and design requirements necessary for television and flexibility and dynamic capabilities of the Internet. The format fully describes the rendering and interaction of the interactive TV service in such a manner as to allow its implementation in a number of different mechanisms and technologies. The format assumes a user agent behaviour that is more sophisticated and more stateful than a standard Internet based HTML browser. + +The format combines explicit pixel-perfect control required for TV user interfaces, and the dynamic layout and Internet compatibility requirements necessary for e-business and dynamic content. It provides a good separation between the layout of high-level objects, and the dynamic layout of elements in the main mark-up language. This separation also allows for the default attribute values to be set for a given layout, effectively creating sets of inherited styles. One useful by-product of this separation is the ability to deploy the service in a functionally identical way by interoperating differently or replacing the high-level layout for different device types. + +The format assumes a rich event model and contains explicit state and variable management, allowing the creation of sophisticated user interface effects without the use of scripting. + +It is common to implement WTVML functionality by way of a micro-browser and gateway architecture. In this architecture, the gateway processes the raw WTVML and generates compiled byte-code to be passed to the user agent to execute. It is expected that different networks may implement their own output formats from the gateway, consisting of WTVML byte-codes extended from the standard WAP Forum byte codes, HTML and ECMAScript, Java execution classes or even code that can be run directly on legacy set-top boxes' middleware or APIs. + +## **6 Standards for procedural application frameworks** + +This clause describes the standards for procedural application frameworks in an alphabetical order, without implying any specific order. + +The procedural application platform is a framework on which applications written by APIs based on procedural language (e.g., Java) can run. + +### 6.1 GEM based application frameworks + +Globally Executable MHP (GEM) [ETSI TS 102 819] specifies the core of Blu-ray's BD-J, OCAP and MHP, see Figure 6-1. For broadcast applications, it can best be thought of as the overlap between the MHP and OCAP standards for interactive television. It is a formally standardized Java-based platform for interactive content and applications. GEM has been standardized by DVB, and adopted by ETSI, ITU, CableLabs, ARIB, ACAP and the Blu-ray Disc Association. + +#### 6.1.1 Advanced common application platform (ACAP) + +ACAP, (see [ATSC A/101] and [ITU-T J.201]) is applicable for specifications and standards based on the ACAP APIs, content formats, and semantic guarantees. + +ACAP applications are classified into two categories depending upon whether the initial application content processed is of a procedural or a declarative nature. These categories of applications are referred to as a procedural (ACAP-J) and declarative (ACAP-X) applications, respectively. An example of an ACAP-J application is a Java TV Xlet composed of compiled Java byte code in conjunction with other multimedia content such as graphic, video, and audio. An example of an ACAP-X application is a multimedia document composed of extensible hypertext markup language (XHTML) markup, style rules, scripts, and embedded graphics, video, and audio. + +![Diagram illustrating the GEM based Standards for multimedia application frameworks. The diagram shows the relationship between ACAP, GEM, MHP, ARIB-AE, and OCAP standards. ACAP is shown as a large green box on the left, labeled 'ACAP' and 'Optional ACAP-X'. GEM is the central grey box, labeled 'GEM' and containing 'JavaTV', 'Havi', 'DaviC', and 'others'. MHP is a blue box on the right, labeled 'MHP' and containing 'Service Information' and 'Conditional Access'. ARIB-AE is an orange box at the top, labeled 'ARIB-AE' and containing 'Service Information', 'Conditional Access', 'Data Carousel', and 'Application Signaling'. OCAP is a yellow box at the bottom, labeled 'OCAP' and containing 'Service Information', 'Conditional Access', 'Monitor Application', 'Unbound Applications', and 'Security Extensions'. The GEM box is positioned such that it overlaps with the ACAP, MHP, ARIB-AE, and OCAP boxes. Below the GEM box, there is a light green box containing 'MHP Object Carousel' and 'MHP Application signaling'.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +The diagram illustrates the GEM based Standards for multimedia application frameworks. It features five main colored boxes representing different standards and their components: + +- ACAP (Green Box):** Labeled "ACAP" and "Optional ACAP-X". It is positioned on the left side of the diagram. +- GEM (Grey Box):** The central box, labeled "GEM". It contains the components: "JavaTV", "Havi", "DaviC", and "others". +- MHP (Blue Box):** Positioned on the right, labeled "MHP". It contains "Service Information" and "Conditional Access". +- ARIB-AE (Orange Box):** Positioned at the top, labeled "ARIB-AE". It contains "Service Information", "Conditional Access", "Data Carousel", and "Application Signaling". +- OCAP (Yellow Box):** Positioned at the bottom, labeled "OCAP". It contains "Service Information", "Conditional Access", "Monitor Application", "Unbound Applications", and "Security Extensions". + +Below the GEM box, there is a light green box containing "MHP Object Carousel" and "MHP Application signaling". The GEM box is positioned such that it overlaps with the ACAP, MHP, ARIB-AE, and OCAP boxes. + +Diagram illustrating the GEM based Standards for multimedia application frameworks. The diagram shows the relationship between ACAP, GEM, MHP, ARIB-AE, and OCAP standards. ACAP is shown as a large green box on the left, labeled 'ACAP' and 'Optional ACAP-X'. GEM is the central grey box, labeled 'GEM' and containing 'JavaTV', 'Havi', 'DaviC', and 'others'. MHP is a blue box on the right, labeled 'MHP' and containing 'Service Information' and 'Conditional Access'. ARIB-AE is an orange box at the top, labeled 'ARIB-AE' and containing 'Service Information', 'Conditional Access', 'Data Carousel', and 'Application Signaling'. OCAP is a yellow box at the bottom, labeled 'OCAP' and containing 'Service Information', 'Conditional Access', 'Monitor Application', 'Unbound Applications', and 'Security Extensions'. The GEM box is positioned such that it overlaps with the ACAP, MHP, ARIB-AE, and OCAP boxes. Below the GEM box, there is a light green box containing 'MHP Object Carousel' and 'MHP Application signaling'. + +**Figure 6-1 – GEM based Standards for multimedia application frameworks** + +Application environments are similarly classified into two categories depending upon whether they process procedural or declarative applications. These categories are referred to as ACAP-J and ACAP-X environments, respectively. An example of an ACAP-J environment is a Java Virtual Machine and its associated API implementation. An example of an ACAP-X environment is an XHTML multimedia document browser, also known as a user agent. + +The architecture and facilities of ACAP are intended to apply to broadcast systems and receivers for terrestrial (over-the-air) broadcast and cable TV systems. + +ACAP is primarily based on GEM and digital television application software environment (DASE) and includes additional functionality from OCAP. The following are the relevant specifications which ACAP includes: + +- Globally executable MHP (GEM): ACAP includes GEM 1.0.2 in its entirety, except as explicitly modified by the ACAP. +- Open cable application platform (OCAP): ACAP includes OCAP 1.0 in its entirety, except as explicitly modified by the ACAP for ACAP terminal operating in a terrestrial broadcast environment. +- Addition on non-ACAP Interfaces: terminal specifications based on ACAP may add public interfaces, provided that they are added in a namespace that does not conflict with ACAP. ACAP terminal specifications and ACAP terminals shall not require that such extension interfaces be called by ACAP applications in order to enable behaviour that is normatively required by ACAP. + +#### 6.1.2 Recommendation ITU-R BT.1699 + +[ITU-R BT.1699-1] identifies functional commonality among the declarative application environments for interactive TV application specifications ACAP-X, BML and DVB-HTML. Elements which are common to these three standards are identified as a "common core". The value of the common core is to assist program authors to exchange declarative content internationally using these standards. [ITU-R BT.1699-1] also notes features outside of the common core of the covered standards. The goal of [ITU-R BT.1699-1] is to note these differences to encourage efforts toward increasing commonality between the standards to further improve functionality and enhance economies of scale. + +[ITU-R BT.1699-1] is intended to harmonize the application environment for declarative content for interactive TV. It specifies common elements, media types and APIs at the syntactic level of the declarative application environment to satisfy regional application requirements for the three standards ACAP-X, BML and DVB-HTML as specified in the normative references. It is noted that there are other declarative formats such as MHEG-5 and Society of Motion Picture Television Engineers (SMPTE) DDE-T that are not covered in [ITU-R BT.1699-1]. + +#### 6.1.3 Recommendation ITU-R BT.1722-1 + +[ITU-R BT.1722-1] defines APIs, semantic guarantees and system aspects of platform behaviour for the harmonized instruction set for the execution engines for interactive TV applications. + +[ITU-R BT.1722-1] includes the following updated and newly developed instruction set for the execution engines: GEM, MHP 1.0 and 1.1, OCAP 1.0, ARIB-AE and ACAP. Harmonization is based on GEM 1.0.1 which has been developed with contributions from DVB, SCTE, ARIB and ATSC. GEM 1.0.1 is the normative reference in [ITU-R BT.1722-1]. + +#### 6.1.4 Multimedia home platform (MHP) + +MHP [ETSI TS 102 812] is the set of specifications for multimedia broadcasting that has been developed by the DVB Project. MHP has two functional categories. Version 1.0 series covers the execution engine (EE) environment and version 1.1 series covers the presentation engine (PE) environment in addition to version 1.0. The PE portion of the version 1.1 series is not standalone; it mandates the existence of the EE environment. The first release of the DVB MHP version 1.0 series was in May 2000. The MHP 1.0 specification employs Java technology for an EE environment. + +#### 6.1.5 Open cable application platform (OCAP) + +OCAP [ANSI/SCTE 90-1] is the set of specifications for the interactive multimedia services of digital CATV that has been developed by the OpenCable project. OCAP 1.0 is based on MHP 1.0.2, and includes the extensions for the cable system in the United States. + +# 7 Other related standards + +### 7.1 MPEG multimedia middleware (M3W) + +M3W [ISO/IEC 23004.x] provides, next to the architecture and component model descriptions and the reference software, two sets of APIs: multimedia platform APIs, the functional APIs, and Support platform APIs, the non-functional APIs (see Figure 7-1): + +- The architecture and component model: + - Part-1: Architecture; + - Part-3: Component Model. + - The functional APIs: + - Part-2: Multimedia API. +- The non-functional APIs; +- Part-4: Resource and quality management; + - Part-5: Component download; + - Part-6: Fault management; + - Part-7: System integrity management. +- The reference software: + - Part-8: Reference Software. + +![Diagram illustrating the structure of M3W. It shows four stacked layers: Applications (top), Middleware, Support Platform (yellow), and Computing Platform (bottom). The Support Platform is labeled 'Multimedia Platform' and 'M3W'. Interfaces are labeled 'M3W API' between Applications and Support Platform, and 'API' between Support Platform and Computing Platform.](a3472689858b068ef469213682965325_img.jpg) + +The diagram shows a layered architecture for M3W. At the top is a grey box labeled 'Applications'. Below it is a grey box labeled 'Middleware'. Below that is a yellow box labeled 'Support Platform' on its left side, 'Multimedia Platform' in the center, and 'M3W' in large letters on the right. At the bottom is a grey box labeled 'Computing Platform'. A green line labeled 'M3W API' connects the 'Applications' box to the 'Support Platform' box. A black line labeled 'API' connects the 'Support Platform' box to the 'Computing Platform' box. + +Diagram illustrating the structure of M3W. It shows four stacked layers: Applications (top), Middleware, Support Platform (yellow), and Computing Platform (bottom). The Support Platform is labeled 'Multimedia Platform' and 'M3W'. Interfaces are labeled 'M3W API' between Applications and Support Platform, and 'API' between Support Platform and Computing Platform. + +Figure 7-1 – The structure of M3W + +The M3W multimedia platform APIs define mainly audio and video processing APIs handling front-end, decoders and post-processing of A/V and trust management APIs handling key management, signature management, license management, and certificate management. The M3W multimedia APIs offer a high-level API that is independent of the target hardware. By standardizing things that are common, the multimedia APIs simplify the work of middleware and application developers. + +# Annex A + +## Common usage + +(This annex forms an integral part of this Recommendation) + +For a typical multimedia framework for IPTV based on web-related technologies, the following combinations are considered foundational: + +- one or more markup languages, such as HTML, XHTML, BML, and SVG; +- some profiles of style sheets, that is, CSS; +- some profiles of standard scripting, e.g., ECMAScript; +- DOM. + +The particular combination of these technologies will define a "profile" of a standard. + +The following clauses give profiles used in the standards mentioned in this Recommendation. + +## **A.1 BML profile** + +- XHTML 1.0, CSS 1, CSS 2, DOM 1, DOM 2, ISO/IEC-16262 (ECMAScript). + +## **A.2 CEA-2014** + +- XHTML 1, CSS TV profile, DOM 2, ISO/IEC-16262 (ECMAScript). + +## **A.3 DVB-HTML profile** + +- XHTML 1.0, CSS 2, DOM 2, ISO/IEC-16262 (ECMAScript). + +## **A.4 SVG profiles** + +- SVG 1.1: CSS 2, DOM 1, DOM 2, ISO/IEC-16262 (ECMAScript); +- SVG Tiny: CSS 2, uDOM, ECMA ISO/IEC-16262 (ECMAScript). + +# Bibliography + +- [b-ITU-T H.761] Recommendation ITU-T H.761 (2009), *Nested context language (NCL) and Ginga-NCL for IPTV services.* +- [b-ITU-T J.202] Recommendation ITU-T J.202 (2008), *Harmonization of procedural content formats for interactive TV applications.* +- [b-ABNT NBR 15606-2] ABNT NBR 15606-2 (2007), *Digital terrestrial television – Data coding and transmission specification for digital broadcasting – Part 2: Ginga-NCL for fixed and mobile receivers – XML application language for application coding; Brazilian Association for Technical Standards.* +- [b-ABNT NBR 15606-5] ABNT NBR 15606-5 (2007), *Digital terrestrial television – Data coding and transmission specification for digital broadcasting – Part 5: Ginga-NCL for portable receivers – XML application language for application coding; Brazilian Association for Technical Standards.* +- [b-ETSI ES 102 543] ETSI ES 102 543 (2007), *Digital Video Broadcasting (DVB) Globally Executable MHP (GEM).* +- [b-ETSI TS 202 184] ETSI TS 202 184 (2004), *MHEG-5 Broadcast Profile.* +- [b-W3C CSS TV Profile] W3C Candidate Recommendation. *CSS TV Profile 1.0* (2003). +- [b-W3C CSS2] W3C Candidate Recommendation. *Cascading Style Sheets, Level 2 Revision 1 (CSS2.1) Specification* (2009). + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.765-201504-I_PDF-E/raw.md b/marked/H/T-REC-H.765-201504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9692fa52f9099e012d18a2e53fbeb818a0b4439f --- /dev/null +++ b/marked/H/T-REC-H.765-201504-I_PDF-E/raw.md @@ -0,0 +1,905 @@ + + +International Telecommunication Union + +# **ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **H.765** + +(04/2015) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +IPTV multimedia application frameworks + +# --- **Packaged IPTV application (widget) service** + +Recommendation ITU-T H.765 + +**ITU-T** + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue. + +ITU logo + +International +Telecommunication +Union + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Packaged IPTV application (widget) service + +# Summary + +Packaged internet protocol television (IPTV) applications (IPTV widgets) are lightweight applications, provided with a simple and easily accessible graphical user interface (GUI), that commonly provide a single functionality (e.g., calendars, feed aggregators, etc.) and might stay persistently exhibited. + +IPTV widgets may run on different types of IPTV terminal devices and therefore standardized technologies must be supported by the widget engine in the terminal device. Recommendation ITU-T H.765 describes IPTV widget services that are developed using the technologies defined in the ITU-T H.760 multimedia application framework (MAFR) series, such as nested context language (NCL) (Recommendation ITU-T H.761), LIME (Recommendation ITU-T H.762), HTML (new MAFR ITU-T Recommendation under study), cascading style sheets (CSS) (Recommendation ITU-T H.763.1), Services enhanced scripting language (SESL) (Recommendation ITU-T H.764) and Lua (new MAFR ITU-T Recommendation under study). The widget service also takes advantage of functionalities described in the ITU-T H.721 IPTV terminal device basic model, as well as service discovery protocols and services specified in Recommendation ITU-T H.770. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.765 | 2015-04-29 | 16 | 11.1002/1000/12464 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +# INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2015 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|---------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 3 | +| 6 | Introduction..... | 3 | +| 6.1 | IPTV widgets overview ..... | 4 | +| 7 | IPTV widget service ..... | 4 | +| 7.1 | Widget service end-to-end architecture ..... | 5 | +| 7.2 | IPTV widget service discovery ..... | 6 | +| 7.3 | Protocols for widget service ..... | 7 | +| 8 | IPTV widget engine ..... | 8 | +| 9 | IPTV widgets ..... | 9 | +| 9.1 | IPTV widget packaging ..... | 9 | +| 9.2 | IPTV widget metadata/configuration ..... | 10 | +| 9.3 | IPTV widget security..... | 12 | +| | Appendix I – ITU-T IPTV widgets versus W3C widgets..... | 14 | +| | Appendix II – IPTV widget examples ..... | 15 | +| II.1 | ITU-T H.761 widget example ..... | 15 | +| II.2 | ITU-T H.762 widget example ..... | 17 | + + + +# Packaged IPTV application (widget) service + +# 1 Scope + +This Recommendation specifies the architecture and functional components needed for the provisioning of packaged IPTV application (widget) service. Widgets are lightweight applications, provided with a simple and easily accessible GUI, which commonly provide a single functionality (e.g., calendars, feed aggregators, etc.) and might stay persistently exhibited. The widget service definition relies on the interoperability and harmonization provided by IPTV multimedia application frameworks (MAFRs) [ITU-T H.760]. The scope of the recommendation comprises the definition of the IPTV packaged application model and the definition of essential service components such as service discovery, packaging, metadata and security. + +The target terminal device types range from the basic model as specified in [ITU-T H.721] to full-fledged terminal devices, which are defined in [ITU-T H.722]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.721] Recommendation ITU-T H.721 (2015), *IPTV terminal devices: Basic model*. +- [ITU-T H.722] Recommendation ITU-T H.722 (2014), *IPTV terminal devices: Full-fledged model*. +- [ITU-T H.760] Recommendation ITU-T H.760 (2009), *Overview of multimedia application frameworks for IPTV services*. +- [ITU-T H.761] Recommendation ITU-T H.761 (2014), *Nested context language (NCL) and Ginga-NCL*. +- [ITU-T H.762] Recommendation ITU-T H.762 (2011), *Lightweight interactive multimedia framework for IPTV services*. +- [ITU-T H.763.1] Recommendation ITU-T H.763.1 (2010), *Cascading style sheets for IPTV services*. +- [ITU-T H.764] Recommendation ITU-T H.764 (2012), *IPTV services enhanced script language*. +- [ITU-T H.770] Recommendation ITU-T H.770 (2015), *Mechanisms for service discovery and selection for IPTV services*. +- [ITU-T X.509] Recommendation ITU-T X.509 (2012), *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks*. +- [IETF RFC 5246] IETF RFC 5246 (2008), *The Transport Layer Security (TLS) Protocol Version 1.2*. + +- [IETF RFC 7230] IETF RFC 7230 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing*. +- [W3C Widgets] W3C Recommendation (2012), *Packaged Web Apps (Widgets) – Packaging and XML Configuration (Second Edition)*. +- [W3C WidgetsDigSig] W3C Recommendation (2013), *XML Digital Signatures for Widgets*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 content delivery network (CDN)** [b-ITU-T F.750]: A network optimized for delivering digital content. + +**3.1.2 content provider** [b-ITU-T Y.1910]: The entity that owns or is licensed to sell content or content assets. + +**3.1.3 end-user** [b-ITU-T Y.1910]: The actual user of the products or services. + +NOTE – An end-user consumes the product or service. An end-user can optionally be a subscriber. + +**3.1.4 key** [b-ITU-T X.800]: A sequence of symbols that controls the operations of encipherment and decipherment. + +**3.1.5 IPTV terminal device** [b-ITU-T Y.1901]: A terminal device which has ITF functionality, e.g., a set top box (STB). + +**3.1.6 metadata** [b-ITU-T Y.1901]: Structured, encoded data that describe characteristics of information-bearing entities to aid in the identification, discovery, assessment, and management of the described entities. + +**3.1.7 multimedia** [b-ITU-T J.148]: The combination of multiple forms of media such as audio, video, text, graphics, fax, and telephony in the communication of information. + +**3.1.8 network provider** [b-ITU-T Y.1910]: The organization that maintains and operates the network components required for IPTV functionality. + +NOTE 1 – A network provider can optionally also act as service provider. + +NOTE 2 – Although considered as two separate entities, the service provider and the network provider can optionally be one organizational entity. + +**3.1.9 service** [b-ITU-T Y.1901]: A set of functionalities enabled by a provider for end-users. + +**3.1.10 service provider** [b-ITU-T M.1400]: A general reference to an operator that provides telecommunication services to customers and other users either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. + +NOTE – In the context of IPTV systems, typically, the service provider acquires or licenses content from content providers and packages this into a service that is consumed by the end-user. + +**3.1.11 terminal device (TD)** [b-ITU-T Y.1901]: An end-user device which typically presents and/or processes the content, such as a personal computer, a computer peripheral, a mobile device, a TV set, a monitor, a VoIP terminal or an audio-visual media player. + +**3.1.12 user interface (UI)** [b-ITU-T F.902]: Software and hardware components through which a user can interact with a system. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 IPTV widget:** See packaged IPTV application. + +**3.2.2 packaged IPTV application:** Lightweight application that is intended to be used frequently, such as calendars and news aggregators, with an easily accessible graphical user interface (GUI), often staying on the terminal device display. + +**3.2.3 widget engine:** Software layer that provides features so that widgets can run on a certain user platform (i.e., an IPTV terminal device). + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|----------------------------------------------| +| AES | Advanced Encryption Standard | +| CSS | Cascading Style Sheets | +| EPG | Electronic Program Guide | +| GUI | Graphical User Interface | +| HTTP | Hypertext Transfer Protocol | +| HTTPS | Hypertext Transfer Protocol Secure | +| IPTV | Internet Protocol Television | +| LIME | Lightweight Interactive Multimedia Framework | +| MAFR | Multimedia Application Framework | +| NCL | Nested Context Language | +| RSA | Rivest-Shamir-Adleman | +| SESL | Services Enhanced Script Language | +| SHA | Secure Hash Algorithm | +| SSL | Secure Sockets Layer | +| TLS | Transport Layer Security | + +# 5 Conventions + +None. + +# 6 Introduction + +Widget is the definition used for an interactive element of a GUI that displays an information arrangement. The origin of the term "widget" comes from the short for "window gadget", and it was first applied to user interface elements on documents from Project Athena in 1988 [b-Athena]. The term widget is also commonly used to specify an element different from basic GUI components because it provides a single interaction point for the direct manipulation of data in a particular context, but as visual components, widgets can be combined to form an application, or may be used separately, as individual applications. Interactive buttons, sliders, boxes, menus, and other components may be called widgets [b-WidgetsIntro]. However, recently the term is more often used to name a *lightweight application* (e.g., stock market monitor, weather forecast, calculator, news aggregator, etc.) that is usually packaged into a single file to facilitate its provision, transport, and installation. + +Web widget, as a "packaged web app" [b-W3C WidgetsReqs], is an interactive single-purpose application for displaying and/or updating local data or data on the Web, packaged in a way to allow a single download and installation on a user's system. However, widgets are used on many + +environments and with different applicability – they may be found on computers' desktops, mobile devices, web applications, and digital TV platforms as well. + +A widget engine is the software layer that supports running and displaying widgets on a GUI, such as the graphical layer of an IPTV terminal device. It is common that such widgets provide relevant information graphically and/or provide easy access to frequently used functions on a system. + +## 6.1 IPTV widgets overview + +Packaged IPTV applications, or simply IPTV widgets, are lightweight applications that are used frequently, such as calendars and news aggregators, with an easily accessible GUI that often stay on the display. + +IPTV widgets may be classified by their functionality. The classification below is a non-exhaustive list of categories that has been collected from [b-WidgetsIntro], revised and extended to the IPTV domain: + +- Accessory widgets: self-contained widgets that do not require support from a content provider or from other applications (e.g., clocks, calculators, offline games); +- Application widgets: widgets that just present a different interface for a regular application already present in the terminal device (e.g., mini player, address book, picture frame); +- Information widgets: widgets that display processed data downloaded from a content provider (e.g., news readers, information tickers, weather forecasters); +- Service widgets: Information widgets that are related to IPTV services (channel-specific electronic program guide (EPG), content recommenders, service provider announcers). + +Since an IPTV widget may run on different kinds of terminal devices (like set-top boxes, TV sets, and mobile devices), portability is an important issue and should be addressed based on standardized technologies supported by widget engines in the terminal device. IPTV widgets must be developed using the technologies defined in the ITU-T H.760-series Multimedia Application Framework (MAFR), [ITU-T H.760], such as lightweight interactive multimedia framework (LIME) [ITU-T H.762], CSS [ITU-T H.763.1], SESL [ITU-T H.764], Ginga-NCL [ITU-T H.761], HTML (a new Recommendation is currently under study in ITU-T) and Lua (a new Recommendation is currently under study in ITU-T). + +# 7 IPTV widget service + +The widget service takes advantage of functionalities described in [ITU-T H.721] IPTV terminal device basic model, as well as service discovery protocols and services specified in [ITU-T H.770] and in the family of MAFR specifications including [ITU-T H.761] (Ginga-NCL), [ITU-T H.762] (LIME) and [ITU-T H.764] (SESL). + +Table 7-1 illustrates the main features of the widget service. + +**Table 7-1 – Main features of the widget service** + +| | ITU-T widget service scope | Notes | +|--------------------------|----------------------------|---------------------------------------------------------| +| Widget service discovery | Yes | Refer to clause 7.2, see also [ITU-T H.770] | +| Interactive widgets | Yes | Based on supported MAFR user agent (Note 1) | +| Non interactive widgets | Yes | Based on supported MAFR user agent (Note 1) | +| Media type | A/V, audio, image, text | Depends on client functions of terminal device (Note 2) | + +**Table 7-1 – Main features of the widget service** + +| | ITU-T widget service scope | Notes | +|---------------------------------|----------------------------|--------------------------------------------------------------------------------------------------------| +| Access local data | Yes | Depends on client functions of terminal device (Note 2)
    Based on supported MAFR user agent (Note 1) | +| Access remote web data | Yes | Depends on client functions of terminal device (Note 2)
    Based on supported MAFR user agent (Note 1) | +| Widget packaging (for download) | Yes | Refer to clauses 9.1 and 9.2
    Based on W3C | +| GUI | Yes | Depends on client functions of terminal device (Note 2) | + +NOTE 1 – Currently supported user agents include [ITU-T H.761], [ITU-T H.762] and [ITU-T H.764]. +NOTE 2 – Currently supported terminal devices include [ITU-T H.721] and [ITU-T H.722]. + +## 7.1 Widget service end-to-end architecture + +Figure 7-1 describes the end-to-end configuration for a widget package execution scenario. The main involved elements are highlighted and described below, as well as the interaction among them. + +![Figure 7-1 – End to end configuration diagram showing the flow of widget packages and content from a content provider through service and network providers to an end-user's IPTV widget engine.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +The diagram illustrates the end-to-end configuration for widget package execution. It is divided into four vertical zones by dashed lines: Content provider, Service provider, Network provider, and End-user. + +1. **Content provider:** Contains 'Widget package' and 'Content' blocks. + +2. **Service provider:** Contains a 'Widget package' block. An arrow shows 'Content' moving to this 'Widget package'. + +3. **Network provider:** Acts as a transit zone. Arrows show the 'Widget package' moving from the Service provider through this zone. + +4. **End-user:** Contains a 'Widget engine' block. Inside this engine are five vertical components: 'Packaging', 'Digital signing', 'Media type', 'Configuration document', and 'MAFR (Note)'. Above the engine are three 'Instantiated IPTV widget' blocks. Arrows from the Network provider point to these instantiated widgets and into the Widget engine. + +Figure 7-1 – End to end configuration diagram showing the flow of widget packages and content from a content provider through service and network providers to an end-user's IPTV widget engine. + +H.765(15)\_F7-1 + +NOTE –For more details on supported MAFR user agents, see Figure 8-1. + +**Figure 7-1 – End to end configuration** + +A widget package is received by the end-user terminal device from a content provider through a service provider and a network provider. The service provider is responsible for organizing a collection of widget packages from different content providers with multiple versions of the widget (e.g., for different scenarios and devices) and different mechanisms for accessing (search, deploy, etc.) the widget packages. All data between the service provider and the end-user terminal device is sent over a network provider. The widget package is optionally associated to an audiovisual content, which may be received from any service provider. + +The end-user terminal device is provided with a widget engine, which is the entity responsible for instantiating widgets running on an IPTV terminal device. An IPTV widget engine handles the widget packages, including application unpacking, authenticity and integrity verification, proper configuration of the resources used by the widget, and also the widget's lifecycle control. IPTV widget + +engines are based on the MAFR technologies as defined by [ITU-T H.760] series. Clause 8 provides further information regarding the IPTV widget engine. + +## 7.2 IPTV widget service discovery + +Widget services are discovered using the framework established in [ITU-T H.770]. Widget service metadata can be accessed under the "other services" category defined in [ITU-T H.770]. Metadata semantics specific to the widget service is described in Table 7-2. + +**Table 7-2 – Metadata semantics specific to the widget service** + +| Element/attribute | Description | Example | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Widget Services | | | +| @DomainName | The unique identifier given to the widget provider | WidgetsAnyCompany.net | +| @Version | Version of the offering record | 3 | +| Widget | | | +| @Id | Identifies an instance of the widget allowing the service provider to provide multiple versions of the widget | 231 | +| Name | Name of the specific widget | CalendarWidget | +| Description | Textual description of the widget for potential display. Several textual descriptions are possible, each of them in a specific language | Schedule/calendar service on your IPTV | +| Author | Textual description of the widget author (person, or company) | Any company | +| License | Usage conditions | (Usage conditions) | +| Language | Supported language(s) | en (English) | +| Minver | Minimum version of the widget engine required to run the widget | (minimum version to run the widget) | +| Maxver | Maximum version of the widget engine required to run the widget | (maximum version to run the widget) | +| Rating | Popularity rating of the widget | 2 (popularity ranking) | +| Downloads | Cumulative number of downloads | 1222 (number of downloads) | +| Added | Date of addition | 2008.6.1 (date of addition) | +| Updated | Date of latest update | 2009.1.1 (latest update date) | +| Picked | Flag set by service provider to promote one or more widgets | 1 | +| Tag | Text related to the widget without any predefined taxonomy | (tags describing widget) | +| Locator | Location (e.g. URI or IP addresses) to access the widget | CalendarWidget.
    AnyCompany.com | +| Widget | | | +| @Id | | | + +**Table 7-2 – Metadata semantics specific to the widget service** + +| Element/attribute | | Description | Example | +|-------------------|------|-------------|---------| +| Widget Services | | | | +| | Name | | | +| | ... | | | +| | | | | + +Widget service metadata can be extended by using a separate namespace (XMLNS) with the definition of other XML elements and attributes. Elements outside the widget service namespace are simply ignored during processing. + +The IPTV widget service namespace is . + +## 7.3 Protocols for widget service + +The IPTV widget service comprises the following steps that demand the standardization of communication protocols and data formats: + +- Service discovery: protocols and data formats to announce the IPTV widget service; +- Transaction processing: protocols and data formats to allow the end-user terminal device to list, search, and acquire an IPTV widget. Transaction processing usually involves the exchange of sensitive data; +- Package delivery: protocols and data formats to deliver an IPTV widget package to the end-user terminal device. + +Tables 7-3, 7-4 and 7-5 specify the minimum recommended protocols and data formats that an IPTV widget service is required to support. + +**Table 7-3 – Protocols and data formats for service discovery** + +| Service discovery | Protocol/data format | +|-----------------------------|----------------------| +| Service discovery protocols | See [ITU-T H.770] | +| General service metadata | See [ITU-T H.770] | +| Specific service metadata | See clause 7.2 | + +**Table 7-4 – Protocols and data formats for transaction processing** + +| Transaction processing | Protocol/data format | +|--------------------------------------------------------------------------------------------|--------------------------------------| +| Transaction processing protocols | HTTPS (SSL3/TLS 1.2) [IETF RFC 5246] | +| Certificate format | ITU-T X.509 | +| Key exchange / authentication algorithm | RSA (Note) | +| Key length | 2048 bits | +| Cipher algorithm | AES-256 (Note) | +| Message authentication | SHA-256 (Note) | +| Widget metadata | See clause 7.2 | +| NOTE – See more details in [IETF RFC 5246] – TLS_RSA_WITH_AES_256_CBC_SHA256 cipher suite. | | + +**Table 7-5 – Protocols and data formats for package delivery** + +| Package delivery | Protocol/data format | +|--------------------------------------------------------------------------------------------|--------------------------------------------------------------| +| Package delivery protocols | HTTP [IETF RFC 7230]
    HTTPS (SSL3/TLS 1.2) [IETF RFC 5246] | +| Certificate format | ITU-T X.509 | +| Key exchange / authentication algorithm | RSA (Note) | +| Key length | 2048 bits | +| Cipher algorithm | AES-256 (Note) | +| Message authentication | SHA-256 (Note) | +| Widget package format | See clause 9.1 | +| NOTE – See more details in [IETF RFC 5246] – TLS_RSA_WITH_AES_256_CBC_SHA256 cipher suite. | | + +# 8 IPTV widget engine + +A widget engine is the software layer that provides features so that widgets can run on a certain user platform (i.e., an IPTV terminal device). Also referred as "widget user agents" [b-W3C WidgetsReqs], they make use of a number of technologies that compose an environment to be used by developers to create lightweight applications. To achieve interoperability, widget engines must rely on a set of standards and protocols that enable the rapid development of single-purposed applications that handle multimedia resources (such as images, audio, video, etc.), and are also able to communicate over a network (using hypertext transfer protocol (HTTP), for instance). + +An IPTV widget engine is the entity responsible for instantiating widget(s) in the client side (i.e., the IPTV terminal device). Figure 8-1 illustrates the basic concept of a widget engine. + +An IPTV widget engine is based on the MAFR technologies defined by [ITU-T H.760] series. The IPTV widget engine handles the widget's instantiation (unpacking and configuring), verifies the widget's authenticity and integrity, allocates the proper resources for the widget's execution (players, API, etc.), and controls the widget's execution lifecycle. As presented in Figure 8-1, an IPTV widget package shall contain NCL ([ITU-T H.761]) and/or LIME ([ITU-T H.762]) application(s), along with the resource files (media, scripts, etc.) within its scope. + +![Diagram of IPTV widget architecture showing the flow from a content provider to a terminal device. On the left, three 'Widget package' boxes are stacked vertically, labeled 'Content provider'. An arrow points to the right, where three 'Instantiated IPTV widget' boxes are shown. Below these is a large box labeled 'Terminal device' containing a 'Widget engine'. The engine is divided into layers: 'Packaging', 'Digital signing', 'Media type', and 'Configuration document'. The 'Configuration document' layer contains 'LIME (ITU-T H.762)', 'NCL (ITU-T H.761)', 'HTML (MAFR.13)', 'CSS (ITU-T H.763.1)', 'SESL script (ITU-T H.764)', 'Media objects', and 'Lua (MAFR.14)'. Below this is the 'Editing API (ITU-T H.761 editing commands, ITU-T H.762 LIME-DOM)' layer. The entire engine structure is labeled 'H.765(15)_F8-1'.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Diagram of IPTV widget architecture showing the flow from a content provider to a terminal device. On the left, three 'Widget package' boxes are stacked vertically, labeled 'Content provider'. An arrow points to the right, where three 'Instantiated IPTV widget' boxes are shown. Below these is a large box labeled 'Terminal device' containing a 'Widget engine'. The engine is divided into layers: 'Packaging', 'Digital signing', 'Media type', and 'Configuration document'. The 'Configuration document' layer contains 'LIME (ITU-T H.762)', 'NCL (ITU-T H.761)', 'HTML (MAFR.13)', 'CSS (ITU-T H.763.1)', 'SESL script (ITU-T H.764)', 'Media objects', and 'Lua (MAFR.14)'. Below this is the 'Editing API (ITU-T H.761 editing commands, ITU-T H.762 LIME-DOM)' layer. The entire engine structure is labeled 'H.765(15)\_F8-1'. + +NOTE – MAFR.13 and MAFR.14 are currently under study in ITU-T. + +**Figure 8-1 – Widget and widget engine** + +In an IPTV scenario, due to its flexibility and openness, presentation concurrency between third-party widgets and service platform provided content is foreseeable. This possibility may lead to discussions that are out of ITU-T Recommendations' scope. The definition of good practices and/or system restrictions to deal with that subject are implementation dependent. + +Implementation details dealing with possible resource limitations of the terminal device impacting widget engine performance or behaviour are out of scope. + +# 9 IPTV widgets + +It is desirable that IPTV widgets be lightweight, easy to use, fast, accessible, portable, interoperable, customizable, secure, and shareable. These goals can be used to define a set of guidelines for the development of widgets. The following guidelines are independent of the MAFR technology chosen to develop a widget: + +- Packaging: a widget must be packaged using a standard format recognizable by IPTV widget engines. Widget developers must keep in mind that this package will be distributed to different devices, locations, languages, and depending of the business model, may be required to be signed. +- Metadata and configuration: widget developers shall have the tools to inform the widget engine the configuration information of a widget, comprising: metadata elements about a widget, such as its title, some form of identification, and versioning information; metadata containing authorship information; a bootstrapping mechanism in order to enable the widget user agents to automatically instantiate a widget; environment configuration parameters. +- Security: the development of widgets involves dealing with security issues, so that the execution of the widget does not harm the terminal device nor compromises data privacy. Using functionalities provided by the supporting widget engine, the developer must guarantee that the widget handles sensitive data confidentially and that it verifies data authenticity and integrity when needed. + +## 8.1 IPTV widget packaging + +Widget packaging refers to the technologies related to the encapsulation of all locally necessary resources and metadata required by the widget into a single file so that it can be distributed and deployed. The *de facto* standard for packaging widgets is the packaging format specified in clause 5 of [W3C Widgets]. + +An IPTV widget package includes the application file (e.g., an NCL or LIME application document), which comprises a configuration file and many media files (images, videos, etc.) compressed into a + +single file, using the compression algorithm defined in clause 5 of [W3C Widgets]. The package file extension is recommended to be ".iwp", which stands for [ITU-T IPTV] widget package. In this case, the media type must be "application/x-itu-iptv-widget". + +Any IPTV widget package must contain one configuration file which is an XML document containing metadata information and configuration parameters to be interpreted by the widget engine. The configuration file must be placed in the root level of the package, and it must be named config.xml. The next clause describes the information provided by an IPTV widget configuration file. + +## 9.2 IPTV widget metadata/configuration + +IPTV widget metadata/configuration is related to how the information regarding a widget is stored inside the package, and how this data is made accessible. Information necessary for IPTV widget configuration is provided in the form of an XML document containing relevant metadata. + +Common metadata included in the widget configuration document is shown in Table 9-1. In order to support proprietary extensions of widget metadata, additional elements or attributes to those shown in the table can be included using a separate namespace. If the widget engine supports the corresponding element or attribute, then it is required to process accordingly, otherwise the widget engine is required to ignore. + +The widget namespace is: . + +**Table 9-1 – Common metadata included in the widget configuration document** + +| Element / @Attribute | Description | Value example (explanation) | Optionality | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|-------------| +| Widget | | | M | +| @id | URI that uniquely identifies the widget. Recommended to be an accessible URI for reference purposes, update checking, notifications, etc. | http://example.org/exampleWidget | O | +| @width | Preferred width for the widget exhibition area | 200 | O | +| @height | Preferred height for the widget exhibition area | 320 | O | +| @viewmodes | List of attributes denoting the preferred way of displaying the widget to the end-user. The list contains one or more values, separated by space characters, ordered by preference where the first value denotes the preferred way. Possible values relevant to IPTV terminal devices: windowed; floating; fullscreen; minimized | Windowed floating | O | +| @version | A string that identifies the version of the widget | 2.1 | O | +| name | A human readable string used, for instance, to identify the widget in a menu. Several | Example widget | O | + +**Table 9-1 – Common metadata included in the widget configuration document** + +| Element / @Attribute | Description | Value example (explanation) | Optionality | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| | names are possible, each of them in a specific language. Use attribute xml:lang to specify the name language | | | +| description | A human readable string for a textual description of the widget. Several textual descriptions are possible, each of them in a specific language. Use attribute xml:lang to specify the description language | Example service on your IPTV | O | +| author | Textual description of the widget author (person, or company) | Any Company | O | +| @href | Author's website URI | http://www.anycompany.com | O | +| @email | Author's Email address | widgets@anycompany.com | O | +| license | String containing the copyright information for the widget | Copyright 2010 by Any Company
    This program is free software; you can redistribute... | O | +| language | Supported language(s) | en (English) | O | +| icon@Src | Icon image file for the widget | /media/icon.png | O | +| content | | | M | +| @src | Path to the main application source file | /main.ncl (relative path from the root of the package file system) | M | +| @type | Type of the main application source file | application/x-ginga-ncl | O | +| tag | Text related to the widget without any predefined taxonomy | (tags describing widget) | O | +| feature | URI to be used by the user agent to request a binding to a runtime component | Runtime components needed by the widget (e.g., a video decoder) | O | +| @name | URI attribute | http://www.anycompany.com | O | +| @required | Boolean value to specify if the component is required to function properly | "true": Widget needs to support the feature to function
    "false": Widget can function without supporting the feature
    The default value when the attribute is omitted is "false" | O | +| param | Defines a parameter for the corresponding feature using name-value pair | param is a child of the feature | O | +| @name | String to denote the name of the parameter | name= "Update frequency"
    Useful widget information (e.g., stock or weather widget) | O | + +**Table 9-1 – Common metadata included in the widget configuration document** + +| Element /
    @Attribute | Description | Value example (explanation) | Optionality | +|-------------------------|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------| +| @value | Value of the parameter | value= "Once per hour" | O | +| preference | Persistent storage for preferences using a name-value pair | | O | +| @name | String to denote the name of the preference | name= "Home menu" | O | +| @value | Value of the preference | value= "My preferred skin" | O | +| @readonly | Boolean value to allow, disallow overwriting | "true": cannot be overwritten at runtime
    "false": can be overwritten
    The default value when the attribute is omitted is "false" | O | + +The extension of the configuration document format can be done by using a separate namespace (XMLNS) with the definition of other XML elements and attributes. Elements outside the widget namespace are simply ignored during processing. + +The following is an example illustrating how to include proprietary metadata using an external namespace. In this example, in addition to the standard namespace an external namespace ("http://somecompany.com/") enables the use of proprietary metadata. Proprietary metadata (i.e., not included in Table 9-1 of clause 9.2) can be used as shown in the fragment below. The attribute "src" is defined in the standardized namespace, while the proprietary attribute "role" is defined in the proprietary namespace. + +``` + + + + {'a':'b','c':'d'} + + + +``` + +## 9.3 IPTV widget security + +IPTV widget security mechanisms are required to address two relevant aspects: + +- The protection of the package that contains a widget for a secure installation in terminal devices; +- The protection of sensitive data that widgets exchange with their associated servers. + +### 9.3.1 Package protection + +Packaging function is required to support package protection mechanisms, which ensure the following security aspects: + +- Authentication: the package has been created by the widget's identified content provider; +- Integrity: the package has not been modified from the content provider up to the end-user terminal device; +- Non-repudiation: the content provider cannot at a later time deny having created the package. + +These mechanisms are required to be included during the packaging of a widget under the form of digital signatures. IPTV widget digital signatures are required to be compliant with W3C XML digital signatures for widgets [W3C WidgetsDigSig]. Table 9-2 specifies the minimum recommended set of algorithms and formats for IPTV widget digital signing. + +**Table 9-2 – Specifications for package protection: digital signing** + +| Package protection | Specification | +|-------------------------------------------------|----------------------| +| Certificate format | [ITU-T X.509] | +| Signature algorithm | RSA-SHA256 (Note) | +| Key length | 4096 bits | +| Digest method | SHA-256 (Note) | +| NOTE – See more details in [W3C WidgetsDigSig]. | | + +### 9.3.2 Data exchange protection + +IPTV widgets might exchange sensitive data with their associated servers. Any data exchange is implemented in a widget by using the communication APIs provided by the underlying MAFR technology of a widget engine. Therefore, widget data exchange protection is required to be supported by the chosen MAFR technology. Table 9-3 specifies the minimum recommended set of protocols, algorithms and formats for IPTV widget secure communications. + +**Table 9-3 – Specifications for data exchange protection: secure communications** + +| Data exchange protection | Specification | +|-----------------------------------------------------------------------------------------------|--------------------------------------| +| Secure protocol | HTTPS (SSL3/TLS 1.2) [IETF RFC 5246] | +| Certificate format | [ITU-T X.509] | +| Key exchange / authentication algorithm | RSA (Note) | +| Key length | 2048 bits | +| Cipher algorithm | AES-256 (Note) | +| Message authentication | SHA-256 (Note) | +| NOTE – See more details in [IETF RFC 5246] –
    TLS_RSA_WITH_AES_256_CBC_SHA256 cipher suite. | | + +# Appendix I + +## ITU-T IPTV widgets versus W3C widgets + +(This appendix does not form an integral part of this Recommendation.) + +This appendix is intended to provide a comparison between the definitions for widgets from W3C and ITU-T IPTV. + +**Table I.1 – Comparison between W3C's and ITU-T IPTV's widget definitions** + +| | W3C | This ITU-T IPTV scope | +|------------------------|-------------|-------------------------------------------------------------| +| What is a widget? | Application | Lightweight application | +| Widget service | Not defined | Yes, see clause 7 | +| Interactivity | Yes | Yes, but also widgets without interactivity | +| Single purpose | Yes | Not necessarily, so leave it out of the definition | +| Display data | Yes | Yes, but could be audible data, therefore use "render" data | +| Access local data | Yes | Yes | +| Access remote web data | Yes | Yes | +| Packaged for download | Yes | Yes | +| Easily accessible | No mention | Yes | +| GUI | No mention | Yes | + +# Appendix II + +## IPTV widget examples + +(This appendix does not form an integral part of this Recommendation.) + +## II.1 ITU-T H.761 widget example + +A simple widget example is presented in this clause. The configuration file defines a start NCL application that exhibits news – the content is reloaded when the user presses the "BLUE" key and the application exits when the "RED" key is pressed. The configuration file defines a specific value for the "*service.language*" variable, which shall be used by the execution environment – all configuration parameters set by the configuration file must be also referenced by the application (the NCL application must include the same media objects for the associated parameters). In the example below, the widget (e.g., *news-widget.iwp*) contains the following directory tree: + +- main.ncl +- config.xml +- css/ +- css/style.css +- media/ +- scripts/ +- scripts/counter.lua + +#### config.xml file + +``` + + + + Example Widget + + + A sample widget. + + Marcelo Moreno + + + + Copyright.2010. International Telecommunication Union + + +``` + +#### main.ncl file + +``` + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + +``` + +#### **counter.lua file** + +``` + +counter = 0 +local counterEvt = { + class = 'ncl', + type = 'attribution', + property = 'counter', +} + +function handler (evt) + if evt.class ~= 'ncl' then return end + if evt.type ~= 'attribution' then return end + if evt.property ~= 'inc' then return end + + counter = counter + evt.value + + event.post { + class = 'ncl', + type = 'attribution', + property = 'inc', + action = 'stop' + } + + counterEvt.value = counter + counterEvt.action = 'start'; event.post(counterEvt) + counterEvt.action = 'stop'; event.post(counterEvt) +end + +event.register(handler) + +``` + +## **II.2 ITU-T H.762 widget example** + +An example of a simple ITU-T H.762 widget is presented in this clause. The configuration file `config.xml` follows the conventions defined in clause 7.2 including necessary elements and attributes. In this example the files included in the widget package are listed below. Note that this particular widget example does not require any external script file. + +- config.xml +- startup.bml +- object-element-test1.lime +- media/ +- media/lime-large.jpg +- media/lime-small.jpg +- media/ITU-icon.jpg +- scripts/ + +The content of the files in this example with the exception of the media files are presented below. + +#### **config.xml file** + +``` + + + + Widget sample in LIME + Simple LIME Widget sample, + with two JPEG files. + +``` + +``` + + + + John Doe + +Copyright.2010. International Telecommunication + Union + +English, Japanese + + + images, LIME + + +``` + +#### **startup.bml file** + +``` + + + + + + +startup -- bml version + + + + + + + + +``` + +#### **object-element-test1.lime file** + +``` + + + + + + +Object element test 1:JPEG + + + + +
    + + + + + + +``` + +# Bibliography + +- [b-ITU-T F.750] Recommendation ITU-T F.750 (2005), *Metadata framework*. +- [b-ITU-T F.902] Recommendation ITU-T F.902 (1995), *Interactive services design guidelines*. +- [b-ITU-T J.148] Recommendation ITU-T J.148 (2003), *Requirements for an objective perceptual multimedia quality model*. +- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2015), *Designations for interconnections among operators' networks*. +- [b-ITU-T X.800] Recommendation ITU-T X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*. +- [b-ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services*. +- [b-ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTF functional architecture*. +- [b-Athena] George A. Champine, Daniel E. Geer, and William N. Ruh (1990), 'Project Athena as a Distributed Computer System,' *IEEE Computer* 23(9), pp. 40-50 (September). +- [b-W3C WidgetsReqs] W3C Working Draft (2009) – *Widgets 1.0 Requirements*. +<>. +- [b-WidgetsIntro] C Kaar (2007), *An introduction to Widgets with particular emphasis on Mobile Widgets Computing*, October. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/raw.md b/marked/H/T-REC-H.770-201504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f68d1b42c754b8f2e634dc5a5f0a52996e9bac83 --- /dev/null +++ b/marked/H/T-REC-H.770-201504-I_PDF-E/raw.md @@ -0,0 +1,1753 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.770** + +(04/2015) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +IPTV service discovery up to consumption + +# --- **Mechanisms for service discovery and selection for IPTV services** + +Recommendation ITU-T H.770 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.770 + +# Mechanisms for service discovery and selection for IPTV services + +## Summary + +Recommendation ITU-T H.770 describes the mechanisms for service provider discovery, service discovery and selection for Internet protocol television (IPTV) services. The mechanisms enable IPTV terminal devices to provide the end-users with effective ways for consuming IPTV services. The expected types of IPTV services using service discovery information include linear television (TV), video on demand (VoD), etc. + +This Recommendation identifies service discovery metadata elements and attributes providing information concerning service providers and contents/services, and its delivery protocols covering both unicast and multicast transport mechanisms. + +This 2015 edition of the Recommendation adds notes on how to treat "Web Portal URL" in clause 7.1. It also modifies the examples of "Portal URL" and "Metadata server URL", changing those into "://[:]/". In clause 10 it also adds a text to show the example on "Metadata server URL". Moreover, "Preferred Content Guide Discovery record Location" is changed into "Preferred Content Guide Discovery record" in clauses 10.1 and 10.2, and its example has been changed to a Boolean value. Relevant elements/attributes in Appendix II are also changed. This edition of the Recommendation also adds a new service type, "Widget service", to Table 7.1-4. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.770 | 2009-08-22 | 16 | 11.1002/1000/10035 | +| 1.1 | ITU-T H.770 (2009) Amd.1 | 2009-11-06 | 16 | 11.1002/1000/10655 | +| 1.2 | ITU-T H.770 (2009) Amd.2 | 2010-09-13 | 16 | 11.1002/1000/10994 | +| 2.0 | ITU-T H.770 | 2015-04-29 | 16 | 11.1002/1000/12465 | + +## Keywords + +Delivery protocol, IPTV services, linear TV, metadata, service discovery, service discovery information, service provider, service provider discovery, service provider information. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2015 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|-------|------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 4 | +| 4 | Abbreviations and acronyms ..... | 4 | +| 5 | Introduction..... | 7 | +| 6 | Service provider discovery process ..... | 8 | +| 7 | Service provider information..... | 9 | +| 7.1 | Service provider information record ..... | 9 | +| 7.2 | Service role information ..... | 13 | +| 7.3 | Encoding of service provider information..... | 13 | +| 8 | Service provider information delivery protocol(s) ..... | 13 | +| 9 | Service discovery process..... | 15 | +| 10 | Detailed service offer information..... | 15 | +| 10.1 | Linear TV discovery..... | 15 | +| 10.2 | Package discovery record ..... | 20 | +| 10.3 | Content guide discovery record..... | 22 | +| 10.4 | Service from other service providers record ..... | 23 | +| 10.5 | Other services discovery record ..... | 24 | +| 10.6 | Encoding of detailed service offer information..... | 25 | +| 11 | Detailed service offer information delivery protocol ..... | 25 | +| 12 | Service selection process ..... | 26 | +| | Annex A – Service discovery profile..... | 29 | +| | Appendix I – Multiple service platforms ..... | 30 | +| I.1 | Introduction to service role information..... | 30 | +| I.2 | Multiple service platforms..... | 30 | +| I.3 | Service mobility..... | 31 | +| I.4 | An example of service discovery processes ..... | 32 | +| | Appendix II – Requirements in other standards organizations ..... | 34 | +| II.1 | Service provider discovery information ..... | 34 | +| II.2 | Detailed service offer information..... | 35 | +| | Appendix III – The usage of TS with service discovery information..... | 40 | +| III.1 | Study on the SI tables ..... | 40 | +| III.2 | Classification of TS with SI ..... | 42 | +| III.3 | Variation of the usage of service discovery information..... | 43 | +| | Appendix IV – Alternative methods for entry point handling..... | 44 | + +| | Page | +|------------------------------------------------------------|-------------| +| Appendix V – Service discovery using TR-069 ..... | 45 | +| V.1    Service discovery profile for TR-069 ..... | 45 | +| V.2    Service provider discovery using TR-069 ..... | 45 | +| V.3    Detailed service offer discovery using TR-069 ..... | 47 | +| Bibliography..... | 48 | + +# Recommendation ITU-T H.770 + +# Mechanisms for service discovery and selection for IPTV services + +# 1 Scope + +This Recommendation describes the mechanisms for service provider discovery, service discovery and selection for Internet protocol television (IPTV) services. The mechanisms enable IPTV terminal devices to provide the end-users with effective ways to discover and select IPTV services. The expected types of IPTV services using service discovery information include linear television (TV) and video-on-demand, etc. + +This Recommendation identifies service discovery metadata elements and attributes providing information concerning service providers and contents/services, and its delivery protocols covering both unicast and multicast transport mechanisms. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.222.0] Recommendation ITU-T H.222.0 (2014) | ISO/IEC 13818-1:2015, *Information technology – Generic coding of moving pictures and associated audio information: Systems*. +- [ITU-T H.264] Recommendation ITU-T H.264 (2014) | ISO/IEC 14496-10: 2014, *Advanced video coding for generic audiovisual services*. +- [ITU-T H.610] Recommendation ITU-T H.610 (2003), *Full service VDSL – System architecture and customer premises equipment*. +- [ITU-T H.701] Recommendation ITU-T H.701 (2009), *Content delivery error recovery for IPTV services*. +- [ITU-T H.721] Recommendation ITU-T H.721 (2015), *IPTV terminal devices: Basic model*. +- [ITU-T H.750] Recommendation ITU-T H.750 (2008), *High-level specification of metadata for IPTV services*. +- [ITU-T H.765] Recommendation ITU-T H.765 (2015), *Packaged IPTV Application (Widget) Service*. +- [ITU-T X.891] Recommendation ITU-T X.891 (2005) | ISO/IEC 24824-1:2007, *Information technology – Generic applications of ASN.1: Fast infozet*. +- [ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*. +- [ATIS-0800022] ATIS standard ATIS-0800022.v002 (2011), *IPTV Consumer Domain Device Configuration Metadata*. +- [BBF TR-069] Broadband Forum TR-069 (2007), *CPE WAN Management Protocol v1.1*, plus Amendment 2. +- [BBF TR-135] Broadband Forum TR-135 (2007), *Data Model for a TR-069 enabled STB*. + +- [ETSI EN 300 468] ETSI EN 300 468 V1.14.1 (2014), *Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems.* +- [ETSI TS 101 154] ETSI TS 101 154 V1.11.1 (2012), *Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG-2 Transport Stream.* +- [ETSI TS 102 034] ETSI TS 102 034 V1.5.2 (2014), *Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks.* +- [ETSI TS 102 472] ETSI TS 102 472 V1.3.1 (2009), *Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Content Delivery Protocols.* +- [IETF RFC 768] IETF RFC 768 (1980), *User Datagram Protocol (UDP).* +- [IETF RFC 959] IETF RFC 959 (1985), *File Transfer Protocol.* +- [IETF RFC 2236] IETF RFC 2236 (1997), *Internet Group Management Protocol, Version 2.* +- [IETF RFC 2250] IETF RFC 2250 (1998), *RTP Payload Format for MPEG1/MPEG2 Video.* +- [IETF RFC 2616] IETF RFC 2616 (1999), *Hypertext Transfer Protocol – HTTP/1.1.* +- [IETF RFC 2818] IETF RFC 2818 (2000), *HTTP over TLS.* +- [IETF RFC 3376] IETF RFC 3376 (2002), *Internet Group Management Protocol, Version 3.* +- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications.* +- [IETF RFC 3810] IETF RFC 3810 (2004), *Multicast Listener Discovery Version 2 (MLDv2) for IPv6.* +- [ISO/IEC 23001-1] ISO/IEC 23001-1 (2006), *Information technology – MPEG systems technologies – Part 1: Binary MPEG format for XML.* +- [W3C XML] World Wide Web Consortium (W3C) Recommendation XML1.1 (2008), *Extensible mark-up language (XML) 1.0, Fifth Edition.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 broadcast** [b-ITU-T M.60]: One-way transmission from one point to two or more other points. + +**3.1.2 content** [b-ITU-T T.174]: Encoded generic value, media or non-media data. + +**3.1.3 electronic content guide (ECG)** [ITU-T H.721]: A service navigation application used especially for streamed and downloaded content. ECG deals with metadata unlike service information used in terrestrial broadcasting. + +**3.1.4 electronic program guide (EPG)** [b-ITU-T Y.1901]: A structured set of data, intended to provide information on available content that may be accessed by end-users. + +**3.1.5 end-user** [ITU-T Y.1910]: The actual user of the products or services. + +NOTE – The end-user consumes the product or service. An end-user can optionally be a subscriber. + +**3.1.6 EPG provider** [b-ITU-T J.90]: The entity that collects, collates and assembles the elements of information that constitute the EPG database. + +**3.1.7 home network (HN)** [b-ITU-T H.622]: Home network is the collection of elements that process, manage, transport and store information, thus enabling the connection and integration of multiple computing, control, monitoring, communication and entertainment devices in the home. + +**3.1.8 Internet protocol television (IPTV)** [b-ITU-T Y.1901]: Multimedia services such as television, video, audio, text, graphics, data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. + +**3.1.9 IPTV terminal device** [b-ITU-T Y.1901]: A terminal device which has ITF functionality, e.g., a STB. + +**3.1.10 IPTV terminal function (ITF)** [b-ITU-T Y.1901]: The end-user function(s) associated with a) receiving and responding to network control channel messages regarding session set-up, maintenance, and teardown, and b) receiving the content of an IP transport from the network and rendering. + +**3.1.11 linear TV** [b-ITU-T Y.1901]: A television service in which a continuous stream flows in real time from the service provider to the terminal device and where the user cannot control the temporal order in which contents are viewed. + +**3.1.12 metadata** [b-ITU-T Y.1901]: Structured, encoded data that describe characteristics of information-bearing entities to aid in the identification, discovery, assessment, and management of the described entities. + +NOTE – EPG metadata has many applications and may vary in depth from merely identifying the content package title or information to populate an EPG to providing a complete index of different scenes in a movie or providing business rules detailing how the content package may be displayed, copied, or sold. + +**3.1.13 middleware** [b-ITU-T Y.1901]: A layer of software between applications and resources, which consists of a set of service enablers that allow multiple functionalities running on one or more devices in an IPTV system to interact across a network. + +**3.1.14 multimedia** [b-ITU-T J.148]: The combination of multiple forms of media such as audio, video, text, graphics, fax, and telephony in the communication of information. + +**3.1.15 network provider** [ITU-T Y.1910]: The organization that maintains and operates the network components required for IPTV functionality. + +NOTE 1 – A network provider can optionally also act as service provider. + +NOTE 2 – Although considered as two separate entities, the service provider and the network provider can optionally be one organizational entity. + +**3.1.16 package** [b-ITU-T Y.1901]: A collection of content components that in some combination (either all or a subset) together provide an end-user experience and are intended to be used together. + +NOTE – A package can be instantiated with or without audiovisual content depending on scenarios, in which audiovisual content and package can be tightly associated or can be loosely coupled enough to be handled (generation, delivery, consumption) independently. + +**3.1.17 portal** [ITU-T H.721]: A portal presents information from diverse sources in a unified manner and provides a way to attach the communication services. + +**3.1.18 program specific information (PSI)** [ITU-T H.222.0]: PSI consists of normative data which is necessary for the demultiplexing of Transport Streams and the successful regeneration of programs and is described in clause 2.4.4 of [ITU-T H.222.0]. An example of privately defined PSI data is the non-mandatory network information table. + +**3.1.19 service and content protection (SCP)** [b-ITU-T Y.1901]: A combination of service protection and content protection. + +**3.1.20 service** [b-ITU-T Y.101]: A structured set of capabilities intended to support applications. + +**3.1.21 service information (SI)** [ETSI EN 300 468]: Digital data describing the delivery system, content and scheduling/timing of broadcast data streams, etc. + +NOTE – It includes MPEG-2 PSI together with independently defined extensions. + +**3.1.22 service navigation** [b-ITU-T H.720]: The presentation of information that allows the end-user to discover, select and consume services. + +**3.1.23 service provider** [b-ITU-T M.1400]: A general reference to an operator that provides telecommunication services to customers and other users either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. + +**3.1.24 set-top box (STB)** [b-ITU-T J.183]: A device that contains demodulator, de-multiplexer, decoder, other functionalities and interfaces related to signal reception and presentation of the distributed programme at the subscriber's site. + +**3.1.25 stream** [b-ITU-T J.200]: A unidirectional continuous flow of content. + +**3.1.26 subscriber** [b-ITU-T M.3050.1]: The subscriber is responsible for concluding contracts for the services subscribed to and for paying for these services. + +**3.1.27 telecommunication service** [b-ITU-T F.700]: Set of telecommunication capabilities that work in a complementary and cooperative way in order to let users perform applications. + +**3.1.28 terminal device (TD)** [b-ITU-T Y.1901]: An end-user device which typically presents and/or processes the content, such as a personal computer, a computer peripheral, a mobile device, a TV set, a monitor, a VoIP Terminal or an audiovisual media player. + +**3.1.29 user device** [b-ATIS-0800002]: Also known as home network end-device (HNED), home network device (HND), consumer equipment (CE), terminal and physical device. A piece of hardware equipment running its software and attached to a home network and being identified by a GUID, e.g., a MAC address. A single device can be used by one or more end-users. + +**3.1.30 video on demand (VoD)** [b-ITU-T Y.1901]: A service in which the end-user can, on demand, select and view a video content and where the end-user can control the temporal order in which the video content is viewed (e.g., the ability to start the viewing, pause, fast forward, rewind, etc.). + +NOTE – The viewing may occur sometime after the selection of the video content. + +### **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 application:** A functional implementation realized as software running in one or spread over several interplaying hardware entities. + +**3.2.2 SCP provider:** A service provider that offers service and content protection (SCP) functionalities to the other service providers. + +**3.2.3 service platform:** A set of functions that facilitate telecommunication services provided by the service providers. + +NOTE – In the context of IPTV services, examples of service platform functions are service authentication, content aggregation and content delivery. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +AV Audio Video + +AVC Advanced Video Coding + +| | | +|--------|---------------------------------------------| +| AVD | Audio, Video and Data | +| ASN.1 | Abstract Syntax Notation One | +| BAT | Bouquet Association Table | +| BBF | Broadband Forum | +| BCG | Broadband Content Guide | +| BiM | Binary MPEG format for XML | +| BIT | Broadcaster Information Table | +| CAS | Conditional Access System | +| CBR | Constant Bit Rate | +| CS | Configuration Server | +| DNS | Domain Name System | +| DRM | Digital Rights Management | +| DVBSTP | DVB SD&S Transport Protocol | +| ECG | Electronic Content Guide | +| EIT | Event Information Table | +| EPG | Electronic Program Guide | +| ETT | Extended Text Table | +| FEC | Forward Error Correction | +| FLUTE | File delivery over Unidirectional Transport | +| FQDN | Fully Qualified Domain Name | +| HN | Home Network | +| HNED | Home Network End-Device | +| HTML | Hyper Text Mark-up Language | +| HTTP | Hyper Text Transport Protocol | +| ID | Identifier | +| IGMP | Internet Group Management Protocol | +| IP | Internet Protocol | +| IPG | Interactive Program Guide | +| IPTV | Internet Protocol Television | +| ITF | IPTV Terminal Function | +| MAC | Media Access Control | +| MGT | Master Guide Table | +| MLD | Multicast Listener Discovery | +| MPEG | Moving Picture Experts Group | +| NIT | Network Information Table | +| PAT | Program Association Table | +| PER | Packed Encoding Rules | + +| | | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| PID | Packet Identifier | +| PMT | Program Map Table | +| PSI | Program Specific Information | +| PSIP | Program and System Information Protocol | +| PVR | Personal Video Recorder | +| RF | Radio Frequency | +| RTCP | Real Time Control Protocol, | +| RTP | Real-time Transport Protocol | +| SADS | Service and Application Discovery and Selection | +| SCART | Société des Constructeurs d'Appareils Radiorécepteurs and Televiseurs. A connector standard that supports various common analogue signal types. | +| SCP | Service and Content Protection | +| SDT | Service Description Table | +| SI | Service Information | +| SIP | Session Initiation Protocol | +| SMS | Short Message Service | +| SOAP | Simple Object Access Protocol | +| SP | Service Provider | +| STB | Set-Top Box | +| TD | Terminal Device | +| TFTP | Trivial File Transfer Protocol | +| TLS | Transport Layer Security | +| TS | Transport Stream | +| UDP | User Datagram Protocol | +| URI | Uniform Resource Identifier | +| URL | Uniform Resource Locator | +| VBR | Variable Bit Rate | +| VCT | Virtual Channel Table | +| VoD | Video on Demand | +| XML | extensible Mark-up Language | + +# 5 Introduction + +Service discovery includes a number of steps toward content acquisition, as illustrated in Figure 5-1. The acquisition of the entry point data to start the service discovery process, which is assumed to be architecture-specific, is not part of this Recommendation. + +![Flowchart of service discovery steps: SP discovery, SP service discovery, SP content discovery, and Content selection and acquisition. The first three steps are grouped under 'Scope of this Recommendation'.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +``` +graph LR; + A[SP discovery] --> B[SP service discovery] + B --> C[SP content discovery] + C --> D[Content selection and acquisition] + subgraph Scope_of_this_Recommendation [Scope of this Recommendation] + A + B + C + end + A_desc[Among a number of SPs] + B_desc[Among a number of services
    (Linear TV, VoD, etc.)] + C_desc[Among a number of contents
    on linear TV or VoD] +``` + +The diagram illustrates the service discovery process. It consists of four sequential steps represented by boxes: 'SP discovery', 'SP service discovery', 'SP content discovery', and 'Content selection and acquisition'. Arrows indicate the flow from left to right. Below the first three boxes are descriptive texts: 'Among a number of SPs' for SP discovery; 'Among a number of services (Linear TV, VoD, etc.)' for SP service discovery; and 'Among a number of contents on linear TV or VoD' for SP content discovery. A horizontal bracket spans these first three steps, labeled 'Scope of this Recommendation'. The final step, 'Content selection and acquisition', is outside this scope. A reference code 'H.770(15)\_F5-1' is located at the bottom right of the diagram area. + +Flowchart of service discovery steps: SP discovery, SP service discovery, SP content discovery, and Content selection and acquisition. The first three steps are grouped under 'Scope of this Recommendation'. + +###### NOTE + +- SP discovery: Discovery of the service providers available on the network. +- SP service discovery: Discovery of the services offered by a specific or all service providers. +- SP content discovery: Discovery of the individual services or contents from a specific service provider. +- Content selection and acquisition: At the end of the navigation through the offered services and contents, the end-user selects a service or content and acquires it. This step is not part of this Recommendation. +- End-user and/or devices may be authenticated before service provider attachment or service attachment as part of the security provisions [b-ATIS-0800017]. + +**Figure 5-1 – From service provider discovery to content acquisition** + +Each IPTV architecture has its own way to make the starting entry point(s) available to the IPTV terminal device. + +A starting entry point might be: + +- An IPTV service provider description provider entry point (when there are several IPTV service providers on the network and no specific service provider entry point is provided in the IPTV terminal device configuration data). + +NOTE 1 – IPTV service provider description provider is an organization providing service provider information. + +- An IPTV service provider entry point (when there is only one IPTV service provider on the network or when a specific service provider entry point is provided in the IPTV terminal device configuration data). The IPTV service provider may be running a web-based solution, a metadata-based solution or both of them. +- One of the following: + - a multicast address for delivering the entry point information described above; + - location of service and application discovery and selection (SADS) functions (i.e., fully qualified domain name (FQDN) or unicast IP address). The SADS functional block provides for the discovery and selection of IPTV services and applications [ITU-T Y.1910]. + +The descriptions of the different steps for service discovery are described below. These are independent of any specific IPTV architecture. + +![Figure 5-2: From entry point data to service/content acquisition. The diagram shows the flow from 'Entry point data' to 'Service provider discovery record' (blue box), which then branches into five discovery records (yellow boxes): 'Linear TV discovery record', 'Content guide discovery record', 'Package discovery record', 'Service from other service provider record', and 'Other services discovery record'. These lead to 'Linear TV Channel' (pink bar), 'Guide for specific TV channels', 'Guide for VoD contents', 'Guide for other services', 'Contents' (orange oval), and 'Other services' (green oval). A bracket labeled 'Scope of this Recommendation' covers the discovery records and their immediate guides. A reference 'H.770(09)_F5-2' is in the bottom right.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph LR + EPD[Entry point data] --> SPDR1[Service provider discovery record] + EPD --> SPDR2[Service provider discovery record] + SPDR1 --> LTVDR[Linear TV discovery record] + SPDR1 --> CGDR[Content guide discovery record] + SPDR1 --> PDR[Package discovery record] + SPDR2 --> SO SPR[Service from other service provider record] + SPDR2 --> OSR[Other services discovery record] + LTVDR --> LTC[Linear TV Channel] + CGDR --> GSC[Guide for specific TV channels] + PDR --> GVC[Guide for VoD contents] + SO SPR --> GOS[Guide for other services] + OSR --> OS[Other services] + GSC --> LTC + GVC --> C((Contents)) + GOS --> OS + subgraph Scope [Scope of this Recommendation] + LTVDR + CGDR + PDR + SO SPR + OSR + end + H770F52[H.770(09)_F5-2] + +``` + +Figure 5-2: From entry point data to service/content acquisition. The diagram shows the flow from 'Entry point data' to 'Service provider discovery record' (blue box), which then branches into five discovery records (yellow boxes): 'Linear TV discovery record', 'Content guide discovery record', 'Package discovery record', 'Service from other service provider record', and 'Other services discovery record'. These lead to 'Linear TV Channel' (pink bar), 'Guide for specific TV channels', 'Guide for VoD contents', 'Guide for other services', 'Contents' (orange oval), and 'Other services' (green oval). A bracket labeled 'Scope of this Recommendation' covers the discovery records and their immediate guides. A reference 'H.770(09)\_F5-2' is in the bottom right. + +**Figure 5-2 – From entry point data to service/content acquisition** + +NOTE 2 – Details of each record are explained in clauses 7 and 10. + +There are several solutions for the IPTV terminal device to obtain the "entry point data", but this is part of the network signalling and therefore is not included here. + +Figure 5-2 indicates the boundary between what is outside and inside the scope of this Recommendation. + +In addition, exchange of service discovery information between the SADS functional block and IPTV terminal devices can be performed in push mode or pull mode [ITU-T Y.1910], or a mix of both, as follows: + +- Push mode: the SADS functional block actively sends the service and application discovery information to the IPTV terminal devices. +- Pull mode: the IPTV terminal devices repeatedly request the service and application discovery information from the SADS functional block. + +# 6 Service provider discovery process + +The first step is to discover the IPTV service providers. + +In the case where there is only one IPTV service provider or if the user is directly registered with one particular service provider, this first step is simpler. + +In the case where there are several service providers and there is no preconfigured service provider, it is necessary to provide the end-user device with one or more starting entry point(s) from where to obtain the description of the service providers available on the network, and there are different solutions, depending on the IPTV architecture, to obtain these entry points. + +![Figure 6-1: Service provider discovery with a central IPTV service provider description provider. A terminal device sends a request for IPTV service descriptions to a central IPTV service provider description provider. This provider returns a list of available service providers (A and B). The terminal device then makes a selection (A or B) and sends a request to the corresponding IPTV service description provider (either Service provider A or Service provider B).](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +The diagram illustrates a central IPTV service provider description provider. On the left, a 'Terminal device' is connected to an orange cloud. From this cloud, an arrow labeled 'Description of IPTV service providers A and B' points to a blue box labeled 'IPTV service provider description provider'. From this central provider, two arrows labeled 'A or B selection' point to two separate blue boxes, each labeled 'IPTV service description provider'. These two boxes are associated with 'Service provider A' and 'Service provider B' respectively, each represented by a blue cloud. + +Figure 6-1: Service provider discovery with a central IPTV service provider description provider. A terminal device sends a request for IPTV service descriptions to a central IPTV service provider description provider. This provider returns a list of available service providers (A and B). The terminal device then makes a selection (A or B) and sends a request to the corresponding IPTV service description provider (either Service provider A or Service provider B). + +**Figure 6-1 – Service provider discovery with a central IPTV service provider description provider** + +NOTE – IPTV service description provider is an organization providing information about IPTV services (e.g., EPG provider). + +In Figure 6-1, there is one entry point which allows acquiring information about available service providers; this is the "IPTV service provider description provider" entry point. + +An alternative solution without a central "IPTV service provider description provider" is also possible as described in Figure 6-2. + +![Figure 6-2: Service provider discovery without a central service provider description provider. A terminal device sends a request for IPTV service descriptions to the IPTV service description provider of Service provider A. This provider returns a list of available service providers (A and B). The terminal device then makes a selection (Service provider A or B) and sends a request to the corresponding IPTV service description provider (either Service provider A or Service provider B).](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +This diagram shows a decentralized approach. A 'Terminal device' (blue box) is connected to an orange cloud. From the cloud, an arrow labeled 'Description of IPTV service provider A' points to an 'IPTV service provider description provider' box, which is part of 'Service provider A' (blue cloud). Another arrow labeled 'Service provider A or B selection' points from the orange cloud to an 'IPTV service description provider' box, which is part of 'Service provider B' (blue cloud). A third arrow labeled 'Description of IPTV service provider B' points from the orange cloud to another 'IPTV service description provider' box, which is also part of 'Service provider B'. + +Figure 6-2: Service provider discovery without a central service provider description provider. A terminal device sends a request for IPTV service descriptions to the IPTV service description provider of Service provider A. This provider returns a list of available service providers (A and B). The terminal device then makes a selection (Service provider A or B) and sends a request to the corresponding IPTV service description provider (either Service provider A or Service provider B). + +**Figure 6-2 – Service provider discovery without a central service provider description provider** + +# 7 Service provider information + +## 7.1 Service provider information record + +This clause specifies the first level of information about service providers. + +The information related to a service provider is called a "service provider information" record. + +The service provider information record contains the first level description of a service provider. + +Several service provider information records can be grouped together if there are several service providers to be described. + +Table 7.1-1 lists the elements/attributes identified for the service provider information record. + +Mandatory elements and attributes are shown as "M", optional ones are shown as "O", conditional requirements are shown as "C". + +**Table 7.1-1 – Service provider information record** + +| Element/attribute | Description | M/O/C | Example(s) | +|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------------------| +| Record type | Type of this set of data (See Table 7.1-4). | M | Service provider information | +| Record version | Version of this record. It is incremented with any change to the service provider information record. | M | 1 | +| Record provider identifier | The unique identifier given to the IPTV service provider description provider described in clause 6 (e.g., an Internet DNS domain name, an URI, etc.). | O | itu-t.int
    ://
    / | +| Individual service provider information (one per service provider) | Complex element containing basic information about service providers (see Table 7.1-2).
    Several individual service provider information entries are possible, each of them for a specific service provider. | M | – | + +The elements/attributes described in Table 7.1-2 have been identified to be part of the "individual service provider information". + +**Table 7.1-2 – Individual service provider information elements/attributes** + +| Element/attribute | Description | M/O/C | Example(s) | +|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------------------------| +| Service provider identifier | The unique identifier given to the service provider (e.g., an Internet DNS domain name, an URI, etc.). | M | itu-t.int
    :/// | +| Individual service provider information version | Version of this set of individual service provider information elements. It is incremented with any change to the set of individual service provider information elements. | M | 1 | +| Service provider logo URI | Pointer to a service provider logo for potential display. | O | :/// | +| Service provider name | Usual name of the service provider for display. Several names are possible, each of them in a specific language. | O | GTN | +| Service provider description | Textual description of the service provider for potential display. Several textual descriptions are possible, each of them in a specific language. | O | Geneva Telecommunication News | + +**Table 7.1-2 – Individual service provider information elements/attributes** + +| Element/attribute | Description | M/O/C | Example(s) | +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------| +| Web portal URL (Note) | URL for the portal to discover the service details using a Web-based solution. This portal may provide the direct path to several detailed IPTV services. | O | ://[:]/ | +| Service offer summary (one per offering) | Complex element containing basic information about services offered by the service provider (see Table 7.1-3). Several service offer summary entries are possible, each of them for a specific service. | M | – | + +NOTE – "Web portal URL" should be used either in this table or in Table 7.1-3. + +The elements/attributes described in Table 7.1-3 have been identified to be part of the "service offer summary". + +**Table 7.1-3 – Service offer summary elements/attributes** + +| Element/attribute | Description | M/O/C | Example(s) | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------| +| Push address | Multicast location of the "detailed service offer" record described in clause 10. For details of address description, see Table 10.1-3 (e.g., Port number, IP address, Source). | C (Note 2) | – | +| Pull URL | Unicast location of the "detailed service offer" records described in clause 10. | C (Note 2) | ://[:]/ | +| Web portal URL (Note 1) | URL for the portal to discover the service details using a Web-based solution. This portal may provide the direct path to several detailed IPTV services. | C (Note 2) | ://[:]/ | +| CS location | Location of the IPTV configuration server, which is shown in clause 8, to be used to get the "Detailed Service Offer" records described in clause 10. | C (Note 2) | ://[:]/ | +| Offer type | Type of service discovery offered by a service provider (see Table 7.1-4). | O | Linear TV discovery | + +**Table 7.1-3 – Service offer summary elements/attributes** + +| Element/attribute | Description | M/O/C | Example(s) | +|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------| +| Segment identifier and version (Note 3) | Identification of a segment containing the "detailed service offer" (or a part of it) with the indication of the latest version.

    Several segment identifiers and versions are possible if the detailed service offer is spread over several segments for transmission. | O | . | + +NOTE 1 – "Web portal URL" should be used either in this table or in Table 7.1-2. +NOTE 2 – At least one of them is required to be presented. +NOTE 3 – Segments are small divided units of "detailed service offer" information records. The service discovery information records may be of a substantial size, but only parts of them are needed by an IPTV terminal device at any one time. Also, changes to the records may be localized to part of the records. Segments are defined in the context of a single record type of service discovery information in Table 7.1-4 [ETSI TS 102 034]. + +Classification of metadata records are specified by using "record type". Table 7.1-4 lists the record types a service provider may offer. + +**Table 7.1-4 – Details of record type** + +| Record types | | Reference | +|------------------------------------------------------------------------------------------|------------------------------|-----------------| +| Service provider information | | In this clause | +| Linear TV discovery | | See clause 10.1 | +| Package discovery | | See clause 10.2 | +| Content guide discovery | | See clause 10.3 | +| Service from other service providers discovery | | See clause 10.4 | +| Other services discovery (Note) | E-book | See clause 10.5 | +| | SMS messaging | | +| | E-mail | | +| | Widget service [ITU-T H.765] | | +| NOTE – "Other services discovery" entries are not limited to those listed in this table. | | | + +Figure 7-1 contains a graphical representation of an implementation example of the service provider information records. + +![Figure 7-1: Graphical representation of the service provider information record. The diagram shows a hierarchical structure of nested boxes. The outermost box is labeled 'Record type, version'. Inside it, a box labeled 'Service provider ID, logo, description, etc.' contains two stacked boxes: 'Service offer summary: Linear TV' and 'Service offer summary: Package'. To the right of these two boxes are labels 'etc.' and 'dc'. Below the 'Service provider ID' box is another box labeled 'Service offer summary: Content guide', which contains a box labeled 'Service offer summary: Package'. To the right of this box is a label 'etc.'. Below the 'Service offer summary: Content guide' box is a box labeled 'Service offer summary: Other Services'.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +H.770(09)\_F7-1 + +Figure 7-1: Graphical representation of the service provider information record. The diagram shows a hierarchical structure of nested boxes. The outermost box is labeled 'Record type, version'. Inside it, a box labeled 'Service provider ID, logo, description, etc.' contains two stacked boxes: 'Service offer summary: Linear TV' and 'Service offer summary: Package'. To the right of these two boxes are labels 'etc.' and 'dc'. Below the 'Service provider ID' box is another box labeled 'Service offer summary: Content guide', which contains a box labeled 'Service offer summary: Package'. To the right of this box is a label 'etc.'. Below the 'Service offer summary: Content guide' box is a box labeled 'Service offer summary: Other Services'. + +**Figure 7-1 – Graphical representation of the service provider information record** + +Relevant standards are: + +- Clause 5.2.5 of [ETSI TS 102 034] specifies the service provider discovery information. +- Clause 8 of [ATIS 0800022] also specifies the service provider discovery information. + +## 7.2 Service role information + +A single organization may play various roles. Supplementary elements may be appended to service provider information or to other elements for identifying these roles and for finding service groupings. + +Service role information is necessary for cases such as the following: + +- When a network provider and a service provider are separate organizational entities as shown in Figure 6-1 of [ITU-T Y.1910]; +- When SCP functions [ITU-T Y.1910] are provided by an entity other than the service provider or the network provider. + +While Appendix I shows possible examples using such service role information, the details of service role information are for further study. + +## 7.3 Encoding of service provider information + +The format and encoding of the service provider information record in this clause are: + +- Service provider information is encoded in XML [W3C XML]. +- Service provider information can optionally be compressed by using Fast Infoset [ITU-T X.891], ZLIB including GZIP format [ETSI TS 102 472] or BiM [ISO/IEC 23001-1]. + +# 8 Service provider information delivery protocol(s) + +The recommended transport mechanisms for the delivery of the descriptions of IPTV service providers over IP are as follows: + +- HTTP version 1.1 [IETF RFC 2616] for "Service provider information" delivery over unicast (pull mode); +- HTTP over TLS [IETF RFC 2818] for "Service provider information" delivery over unicast with secure manner (pull mode); +- IGMP version 2 [IETF RFC 2236] for "Service provider information" delivery over IPv4 multicast (push mode); + +- IGMP version 3 [IETF RFC 3376] for "Service provider information" delivery over IPv4 multicast (push mode); +- MLD version 2 [IETF RFC 3810] for "Service provider information" delivery over IPv6 multicast (push mode); +- FLUTE [ETSI TS 102 472] for "Service provider information" delivery over IPv4/IPv6 multicast ("push mode"); +- DVBSTP [ETSI TS 102 034]: a light protocol specified by DVB, used for delivery over multicast (push mode); +- TR-069 [BBF TR-069]: CPE WAN Management Protocol v1.1, Issue 1, Amendment 2, 2007. Appendix V describes how TR-069 is to be used to acquire service provider information and specifies extensions to TR-135 [BBF TR-135] STB data model to store this kind of information. + +![Sequence diagram for Figure 8-1: Unicast request to get the description of the available IPTV service providers. A Terminal device sends a 'Unicast request for IPTV service provider description' to an IPTV service provider description provider, which responds with 'Description of service providers'. A second IPTV service description provider is shown but not involved in the interaction.](83852ec55d4802521a727926336bedab_img.jpg) + +``` + +sequenceDiagram + participant Terminal device + participant IPTV service provider description provider + participant IPTV service description provider + Note right of IPTV service description provider: H.770(09)_F8-1 + Terminal device->>IPTV service provider description provider: Unicast request for IPTV service provider description + IPTV service provider description provider-->>Terminal device: Description of service providers + +``` + +Sequence diagram for Figure 8-1: Unicast request to get the description of the available IPTV service providers. A Terminal device sends a 'Unicast request for IPTV service provider description' to an IPTV service provider description provider, which responds with 'Description of service providers'. A second IPTV service description provider is shown but not involved in the interaction. + +**Figure 8-1 – Unicast request to get the description of the available IPTV service providers** + +In the case of Figure 8-1, the service provider description provider may answer with a set of metadata containing the description of the available service providers. + +![Sequence diagram for Figure 8-2: Multicast request to receive the description of the available IPTV service providers. A Terminal device sends a 'Multicast request' to a Network device, which then receives the 'Description of service providers' from an IPTV service provider description provider. A second IPTV service description provider is shown but not involved in the interaction.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` + +sequenceDiagram + participant Terminal device + participant Network device + participant IPTV service provider description provider + participant IPTV service description provider + Note right of IPTV service description provider: H.770(09)_F8-2 + Terminal device->>Network device: Multicast request + IPTV service provider description provider-->>Network device: Description of service providers + +``` + +Sequence diagram for Figure 8-2: Multicast request to receive the description of the available IPTV service providers. A Terminal device sends a 'Multicast request' to a Network device, which then receives the 'Description of service providers' from an IPTV service provider description provider. A second IPTV service description provider is shown but not involved in the interaction. + +**Figure 8-2 – Multicast request to receive the description of the available IPTV service providers** + +In the case of Figure 8-2, the service provider description provider periodically sends the set of metadata containing the description of the available service providers. + +![Sequence diagram showing the interaction between a Terminal device and a Configuration server using the TR-069 protocol. The Terminal device sends a 'TR-069 session establishment' message to the Configuration server, which responds with a 'Response with SP information'. The diagram is labeled H.770-Amd.2(10)_F8.3.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +sequenceDiagram + participant Terminal device + participant Configuration server + Note left of Terminal device: H.770-Amd.2(10)_F8.3 + Terminal device->>Configuration server: TR-069 session establishment + Configuration server-->>Terminal device: Response with SP information + +``` + +Sequence diagram showing the interaction between a Terminal device and a Configuration server using the TR-069 protocol. The Terminal device sends a 'TR-069 session establishment' message to the Configuration server, which responds with a 'Response with SP information'. The diagram is labeled H.770-Amd.2(10)\_F8.3. + +**Figure 8-3 – Using TR-069 to receive the description of the available IPTV service providers** + +In the case of Figure 8-3, IPTV terminal devices acquire the set of metadata containing the description of the available service providers by using TR-069 protocol. Configuration server in this diagram is a component in the broadband network responsible for auto-configuration of the IPTV terminal devices. + +# 9 Service discovery process + +In the service provider information, the IPTV terminal device discovers all service providers available on the network. + +If a specific service provider is already configured in the IPTV terminal device, the IPTV terminal device can proceed with a request to the service provider for the description of all services offered by this service provider. + +If no specific service provider is already configured in the IPTV terminal device and if several service providers are available, the IPTV terminal device may display information about the available service providers extracted from the service provider information to allow the user to select one of them. + +When the IPTV terminal device knows the service provider to which the end-user wants to connect, it can proceed with a request to the service provider for the description of all services offered by this service provider. + +The access point for this request can be found in the service provider information. + +# 10 Detailed service offer information + +This clause specifies the elements and attributes which could be or must be included in the description of the services offered by a service provider. + +A number of service types which could be offered by service providers have been identified and for each of them, metadata has been defined. + +Here is the list of the specified service offers: + +- linear TV discovery record, +- package (service collection) discovery record, +- content guide discovery record, +- service from other service providers discovery record, +- other services discovery record. + +## 10.1 Linear TV discovery + +The linear TV discovery record provides the necessary information to find available linear TV services. + +With this record, linear TV delivered over MPEG-2 transport stream (TS) can have "service information (SI)" embedded. The SI obtains important information for the process of the service discovery, especially in traditional broadcasting services (e.g., used in up/down channel changing, + +channel selection by channel numbers, or display of EPG). Information about individual services is acquired afterwards from the transport stream itself one by one through classical use of SI. When SI is embedded in TS, IPTV terminal devices need to connect to all services and parse all SI to build a service list [b-ETSI TS 102 542]. For details of the usage of TS with SI, see Appendix IV. + +Table 10.1-1 lists the elements/attributes identified for the linear TV discovery record and Table 10.1-2 lists elements/attributes identified for the "linear TV service(s)" of Table 10.1-1. + +**Table 10.1-1 – Linear TV discovery record** + +| Element/attribute | Description | M/O/C | Example(s) | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------------------| +| Record type | Type of this set of data. | M | Linear TV discovery record type | +| Service provider identifier | The unique identifier given to the service provider (e.g., an Internet DNS domain name, an URI, etc.). | M | itu-t.int:/// | +| Record version | Version of this record. It is incremented with any change to this record. | M | 1 | +| Metadata server URL | URL for the metadata server of the current service (Note). | O | ://[:]/ | +| Portal URL | URL for the portal of the current service. | O | ://[:]/ | +| Purchase information URL | URL for the server that provides the purchasing information for this service. For security reasons, the scheme could be "https". | O | ://[:]/ | +| Linear TV service(s) | For detailed information on individual linear TV services, see Table 10.1-2. | M | – | + +NOTE – For example, metadata is assumed to be used when multi-vendors' IPTV terminal devices existed (e.g., migration of IPTV terminal devices). A request on the "Metadata server URL" shall return a record compliant with a schema that will be specified in a later revision of this Recommendation. + +**Table 10.1-2 – Linear TV services elements/attributes** + +| Element/attribute | Description | M/O/C | Example(s) | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------|-------|------------| +| Service identifier | A unique name for the service within the service provider's domain. | M | Channel 1 | +| Original network Id | Network Id of the originating delivery system. (Note 1) | O | 0 | +| Transport stream Id | Identification of the transport stream. | O | 200 | +| Service Id | Service identification within the TS. The service Id is the same as the program number in the corresponding program map table. | O | 231 | + +**Table 10.1-2 – Linear TV services elements/attributes** + +| Element/attribute | Description | M/O/C | Example(s) | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------| +| Max bit rate | Maximum bit rates (in kbit/s) of the overall stream carrying the service. | O | 4 000 | +| Service location(s) | A number of linear TV service locations. At least one is required to be present. For a detailed description, see Table 10.1-3. | M | – | +| Audio coding | Details of the audio coding algorithms and purpose that the service may use. | O | Audio MPEG-1 Layer II | +| Video coding | Details of the video coding that may be used by the service. | O | Video ITU-T H.264 (AVC) | +| Service availability | It allows each service to have a list of "cells" (regions) with which the service is associated. By default, all the single services are available everywhere. There shall be at most one service availability element for each country code (See Table 10.1-5). | O | – | +| Streaming type | RTP or direct UDP streaming. By default, RTP streaming is assumed. | O | RTP | +| Multiplex mode | MPEG-2 TS or Time-stamped MPEG-2 TS. By default, MPEG-2 TS streaming is assumed. (Note 2) | O | MPEG-2 TS | + +NOTE 1 – Each linear TV service can be identified by the combination of original network Id, transport stream Id and service Id [ETSI TS 102 034]. + +NOTE 2 – For detail information of time-stamped MPEG-2 TS, see Appendix I of [ITU-T H.721]. + +A service location is either a multicast or a unicast location. Table 10.1-3 lists the "service location" elements/attributes identified for service location(s) of Table 10.1-2. + +**Table 10.1-3 – Service location elements/attributes** + +| Element/attribute | Description (Note 1) | M/O/C | Example(s) | +|----------------------|------------------------------------------------------------|---------------|---------------------------------------| +| IP multicast address | IP multicast address at which the service may be accessed. | C
    (Note 2) | 224.1.2.3 | +| IP multicast port | IP multicast port at which the service may be accessed. | C
    (Note 2) | 5 678 | +| IP multicast source | IP multicast address of the source of the service. | C
    (Note 3) | 224.10.102.13 | +| Unicast URL | Unicast location to access the linear TV server. | C
    (Note 2) | ://
    [:] | + +NOTE 1 – When multiple service locations are included in this record, end-users can access one of them (e.g., one location is a main delivery site, and the others are proxy sites). +NOTE 2 – Either multicast address and port or unicast URL is required, at least. +NOTE 3 – Source address is mandatory when IPv6 multicast is deployed. + +Table 10.1-4 lists the forward error correction (FEC) elements/attributes which can be used together with multicast service location(s) in Table 10.1-2. For details of FEC, see [ITU-T H.701]. + +**Table 10.1-4 – FEC elements/attributes** + +| Element/attribute | Description | M/O/C | Example(s) | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------| +| FEC base layer multicast address | IP multicast address for FEC base layer. If the IP multicast address is omitted, then the FEC flow is assumed to be on the same multicast address as the original data. For details of addressing, see Table 10.1-3. | M | – | +| FEC enhancement layer multicast address | IP multicast address for FEC enhancement layer. If the IP multicast address is omitted, then the FEC flow is assumed to be on the same multicast address as the original data. For details of addressing, see Table 10.1-3. | O | – | +| Maximum packet number in blocks | Maximum number of stream source packets that will occur between the first packet of a source block (which is included) and the last packet for that source block (source or repair). | O | 8 | +| Maximum FEC block duration | Maximum transmission duration of any FEC block (source and repair packets). | O | 100 | +| FEC specific information | FEC object transmission information for the FEC enhancement layer. This information contains the maximum source block length and the encoding symbol size. If FEC enhancement layer element is included, then this element is required to be included. | C
    (Note) | – | + +NOTE – This information is required when FEC enhancement layer is used. + +Table 10.1-5 lists the elements/attributes identified for the "service availability" of Table 10.1-2. + +**Table 10.1-5 – Service availability elements/attributes** + +| Element/attribute | Description | M/O/C | Example(s) | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------| +| Country code | Country for which the availability is being defined. | O | Switzerland | +| Availability | Flag to indicate whether the service is available in the country specified by "Country code". The default is true. When true, the service is available in the specified country with the exception of those regions identified by cells. When false, the service is not available in the specified country with the exception of those regions identified by cells. | O | False | +| Region codes | List of string identifiers representing geographical regions in the country identified by "Country code". The cells listed represent the exception to the value supplied by the flag, i.e., the negation of the "Availability" flag applies to any listed cells. | O | Geneva | + +Whereas a linear TV record can provide necessary information for linear TV discovery without SI in MPEG-2 TS, IPTV terminal devices can create a service list only with the received linear TV record. In this case, in order to provide information equivalent to SI, the following "additional linear TV discovery elements/attributes" should be used. + +Table 10.1-6 lists additional linear TV discovery elements/attributes. + +**Table 10.1-6 – Additional linear TV discovery elements/attributes** + +| Element/Attribute | Description | M/O/C | Example(s) | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---------------------------------------| +| Type of service | It shall be coded as per the relevant SI standards. Examples are linear TV service, digital radio sound service, mosaic service, data broadcast service, etc. | M | Linear TV | +| Priority SI source | Source of service information to give priority (XML record or SI) in case SI tables are present within TS. The default value is XML. (Note) | O | XML, SI, SI+XML | +| Service name | Service name for display in one or more languages. | O | Town scenery | +| Service description | Service description for potential display in one or more languages. | O | Video gallery of worldwide life style | + +**Table 10.1-6 – Additional linear TV discovery elements/attributes** + +| Element/Attribute | Description | M/O/C | Example(s) | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------| +| Content guide discovery record identifier(s) | Identifier(s) of the content guide discovery record(s) that carries the information on this service. If this element is present, it shall be used in preference to the service description. | O | Cgd.avd.0001 | +| Preferred content guide discovery record | Property of being preferred content guide discovery record if there are multiple content guide discovery records in linear TV services. | O | True | +| Service genre(s) | One or more genre of the service (not individual programmes). For example, movie/drama channel or news/current affairs channel. | O | Sports, football/soccer | +| Announcement stream | Type of spoken announcements that are supported by the service (for example, emergency flash, road traffic flash, etc.). Furthermore, it informs about the transport method of the announcement and gives the necessary linkage information so that the announcement stream can be monitored. | O | – | +| Secondary service Id | Service replacement service Id which may be selected automatically by the IPTV terminal devices when the service being decoded fails. | O | itu-t.proxy.int | +| Mosaic information | Mosaic description element. It identifies the elementary cells of a mosaic service, groups different elementary cells to form logical cells, and establishes a link between the content of all or part of the logical cell and the corresponding service or package information. | O | – | + +NOTE – Both SI and XML record can be optionally used at the same time without priority. + +## 10.2 Package discovery record + +The package discovery record provides a means for a collection of services to be marketed as, or grouped into, a single entity. + +Table 10.2-1 lists the elements or attributes for this package discovery record. + +**Table 10.2-1 – Package discovery record** + +| Element/attribute | Description | M/O/C | Example(s) | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------| +| Record type | Type of this set of data. | M | Package discovery record type | +| Service provider identifier | The unique identifier given to the service provider (e.g., an Internet DNS domain name, an URI, etc.). | M | itu-t.int
    :// / | +| Record version | Version of this record. It is incremented with any change to this record. | M | 1 | +| Package identifier | Unique package identifier. This identifier is allocated by the service provider. | M | Pkg1011 | +| Displayable | A Boolean value which indicates in combination with the package availability element, whether this package shall be presented to the user. The default value is true. | O | True | +| Package name | Package name for display in one or more languages. | O | AVD topics | +| Package description | Package description for display in one or more languages. | O | Hot technologies about audio, video and data | +| Content guide discovery record identifier | Identifier(s) of the content guide discovery record(s) that carries the information on this service. If this element is present, it shall be used in preference to the service description. | O | Cgd.avd.0001 | +| Preferred content guide discovery record | If there are multiple content guide discovery records, this value indicates preferred content guide discovery record. | O | True | +| Package reference(s) | Identifiers of package(s) included in the current package. A package may include other package(s). | O | Pkg.2009.1012 | +| Individual service(s) | List of services forming the package. For detail of service relevant elements, see Table 10.2-2. | M | – | +| Package availability | Package availability (support for regionalization). It allows each package to have a list of cells (regions) with which the package is associated. By default, the package is available everywhere. There shall be at most one Package availability element for each country code. Refer to service availability elements in Table 10.1-5. | O | – | + +Table 10.2-2 lists the elements/attributes identified for each "individual service" of Table 10.2-1. + +A service may belong to more than one package. A service does not have to be part of any package. + +**Table 10.2-2 – Individual service elements/attributes** + +| Element/attribute | Description | M/O/C | Example(s) | +|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------| +| Individual service provider identifier | Unique identifier for the service provider. If this is omitted, service provider identifier of Table 10.3-1 is used. | O | itu-t.avd.int | +| Service identifier | A unique name for the service within the service provider's domain | M | 0001.0002.0003 | +| Additional service description location | The URI of additional service description provided in the context of a package; this is not required to acquire a service. | O | ://
    [:]/ | +| Logical channel number | The logical channel number of the service. (Note) | O | 12 | + +NOTE – The logical channel number provides a convenient way to select a service by assignment of a preferred number being different from a physical channel number. + +## 10.3 Content guide discovery record + +Content guide in this clause refers to service navigation functionality for the end-users (e.g., ECG, BCG, IPG and EPG). The content guide discovery record provides a means to discover the locations of guides listing the content that is available, either live (e.g., through a linear TV offering) or via content on demand. + +General aspects of metadata concerning the content guide are illustrated in [ITU-T H.750]. Details of the usage of elements and of attributes as the content guide are for further study. + +NOTE – [b-ETSI TS 102 822-3-1] provides important information about content guide schemes. Besides ETSI, other standardization organizations carry out activities in the field of content guide standardization. See [b-ETSI TS 102 323] and [b-ATIS-0800020]. + +Several content guide discovery records can be grouped together if several guides are available. + +Table 10.3-1 lists the elements/attributes identified for the content guide discovery record. + +**Table 10.3-1 – Content guide discovery record** + +| Element/attribute | Description | M/O/C | Example(s) | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------|-------|--------------------------------------| +| Record type | Type of this set of data. | M | Content guide discovery record type | +| Service provider identifier | The unique identifier given to the service provider (e.g., an Internet DNS domain name, an URI, etc.). | M | itu-t.int
    :/// | +| Record version | Version of this record. It is incremented with any change to this record. | O | 1 | +| Content guide discovery record identifier | The identifier of the content guide discovery record. It is allocated by the service provider. | M | Cgd.avd.0001 | + +**Table 10.3-1 – Content guide discovery record** + +| Element/attribute | Description | M/O/C | Example(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------------------| +| Content guide name | The name of this content guide for potential display. Several names are possible, each of them associated with a specific language. | O | Sports channel index | +| Content guide provider name | The name of the provider of this content guide for potential display. Several names are possible, each of them associated with a specific language. | O | World Sports News Corp | +| Content guide description | This is the description of this content guide for potential display. Several descriptions are possible, each of them associated with a specific language. | O | Fun sports: Football, tennis, ski, etc. | +| Content guide locator (Note) | Locator to access the broadband content guide. Several possibilities can be described (e.g., push mode, HTTP pull mode, SOAP [b-W3C SOAP] pull mode, etc.). | M | ://[:]/ | +| Content guide logo URI | Pointer to the logo of this content guide for potential display. | O | ://[:]/ | +| Content guide type | The content guide type. It indicates if the content guide relates to live programs, content on demand, both, or some other form of content. | O | Linear TV | +| Target service provider identifier | This is the identifier of the service provider whose content is described by this content guide. | O | Geneva entertainment channel | +| NOTE – A request on the "content guide locator" shall return a record compliant with a schema that will be specified in a later revision of this Recommendation. | | | | + +## 10.4 Service from other service providers record + +A service provider can reference individual services or a complete offering provided by another service provider. Supplying its textual service identifier references a service. Supplying the service provider's identifier without a service list references an entire service provider's offering. + +Elements and attributes for the "service from other service providers" record are listed in Table 10.4-1. + +**Table 10.4-1 – Service from other service providers record** + +| Element/
    Attribute | Description | M/O/C | Example(s) | +|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------| +| Record type | Type of this set of data. | M | Service from other service provider record type | +| Service provider identifier | The unique identifier given to the service provider (e.g., an Internet DNS domain name, an URI, etc.). | M | itu-t.int
    :/// | +| Record version | Version of this record. It is incremented with any change to this record. | C
    (Note) | 1 | +| Referenced service provider identifier | The unique identifier given to the referenced service provider (e.g., an Internet DNS domain name, an URI, etc.). | O | itu-t.int
    :/// | +| Service identifier(s) | A unique identifier for the service within the referenced service provider's domain for each service from the referenced provider. Not required if the entire set of offerings from the service provider is referenced. | O | 0003.0004.0005 | + +NOTE – Record version is mandatory when the record is provided on request (i.e., "pull mode") and is optional when the record is multicast (i.e., "push mode"). + +## 10.5 Other services discovery record + +In addition to IPTV services (e.g., linear TV, content on demand), a variety of other services (e.g., short message service (SMS), e-mail, e-newspaper) may be offered. + +The discovery record for other services includes at least the following core general information elements or attributes listed in Table 10.5-1. + +Additional specific elements might be needed for each individual service type. + +**Table 10.5-1 – Other services discovery record** + +| Element/
    attribute | Description | M/O/C | Example(s) | +|-----------------------------|--------------------------------------------------------------------------------------------------------|-------|--------------------------------------| +| Record type | Type of this set of data: SMS, e-mail, chat, e-newspaper, etc. | M | Chat discovery record type | +| Service provider identifier | The unique identifier given to the service provider (e.g., an Internet DNS domain name, an URI, etc.). | M | itu-t.int
    :/// | +| Record version | Version of this record. It is incremented with any change to this record. | O | 1 | +| Service name | Name of specific service specified by offer type; brand name provided by the service provider. | O | Geneva AVD chat | + +**Table 10.5-1 – Other services discovery record** + +| Element/attribute | Description | M/O/C | Example(s) | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------------------------| +| Service identifier | It identifies an instance of the service allowing the service provider to provide multiple versions of the application or service. | M | srv.2.4.5 | +| Service description | Textual description of the service for potential display. Several textual descriptions are possible, each of them in a specific language. | O | Chat with worldwide authorities | +| Service locator | Location (e.g., URI or IP addresses) to get access to the service (e.g., URI or IP addresses). | M | itu-t.int
    :/// | + +## 10.6 Encoding of detailed service offer information + +Format and encoding of detailed service offers information in this clause are as follows: + +- Detailed service offer information is encoded in XML [W3C XML]. +- Detailed service offer information can optionally use Fast Infoset [ITU-T X.891], ZLIB including GZIP format [ETSI TS 102 472] or BiM [ISO/IEC 23001-1]. + +# 11 Detailed service offer information delivery protocol + +The recommended transport mechanisms for the delivery of the descriptions of IPTV services offered by an IPTV service provider are: + +- HTTP 1.1 [IETF RFC 2616] for "Detailed Service Offer" delivery over unicast (pull mode); +- HTTP over TLS; +- IGMP version 2 [IETF RFC 2236] for "Detailed Service Offer" delivery over IPv4 multicast (push mode); +- IGMP version 3 [IETF RFC 3376] for "Detailed Service Offer" delivery over IPv4 multicast (push mode); +- MLD version 2 [IETF RFC 3810] for "Detailed Service Offer" delivery over IPv6 multicast (push mode); +- DVBSTP [ETSI TS 102 034]: a light protocol specified by DVB, used for delivery over multicast (push mode); +- FLUTE [ETSI TS 102 472] for "Detailed Service Offer" delivery over IPv4/IPv6 multicast (push mode); +- TR-069 [BBF TR-069]: CPE WAN Management Protocol v1.1, Issue 1, Amendment 2, 2007. Appendix V describes how TR-069 is to be used to acquire detailed service offer information and specifies extensions to TR-135 [BBF TR-135] STB data model to store this kind of information. + +![Sequence diagram for Figure 11-1: Terminal device sends an HTTP(S) request for service description to an IPTV service description provider, which responds with the IPTV service description. A second IPTV service description provider is shown but not involved in this interaction.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +``` + +sequenceDiagram + participant Terminal device + participant IPTV service provider description provider + participant IPTV service description provider + Terminal device->>IPTV service description provider: HTTP(S) request for service description + IPTV service description provider-->>Terminal device: IPTV service description + +``` + +H.770(09)\_F11-1 + +Sequence diagram for Figure 11-1: Terminal device sends an HTTP(S) request for service description to an IPTV service description provider, which responds with the IPTV service description. A second IPTV service description provider is shown but not involved in this interaction. + +**Figure 11-1 – HTTP or HTTP over TLS request for description of the IPTV services offered by a service provider** + +When using HTTP or HTTP over TLS, the service description provider may answer with a set of metadata containing the description of the available services. + +![Sequence diagram for Figure 11-2: Terminal device sends an IGMP join request to a Network device, which then receives the IPTV service description from an IPTV service description provider.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant Terminal device + participant Network device + participant IPTV service provider description provider + participant IPTV service description provider + Terminal device->>Network device: IGMP + IPTV service description provider-->>Terminal device: IPTV service description + +``` + +H.770(09)\_F11-2 + +Sequence diagram for Figure 11-2: Terminal device sends an IGMP join request to a Network device, which then receives the IPTV service description from an IPTV service description provider. + +**Figure 11-2 – IGMP or MLD join request to receive the description of the IPTV services offered by a service provider** + +For multicast, the service provider description provider periodically sends the set of metadata containing the description of the available services. + +![Sequence diagram for Figure 11-3: Terminal device sends a TR-069 session establishment request to a Configuration server, which responds with the IPTV service description.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +``` + +sequenceDiagram + participant Terminal device + participant Configuration server + Terminal device->>Configuration server: TR-069 session establishment + Configuration server-->>Terminal device: Response with IPTV service description + +``` + +H.770-Am.2(10)\_F11.3 + +Sequence diagram for Figure 11-3: Terminal device sends a TR-069 session establishment request to a Configuration server, which responds with the IPTV service description. + +**Figure 11-3 – Using TR-069 to receive the description of the IPTV services** + +In the case of Figure 11-3, IPTV terminal devices acquire the set of metadata containing the description of the available IPTV services by using TR-069 protocol. + +## 12 Service selection process + +By default, the IPTV terminal device may tune directly to the last linear TV channel watched in the past or to a preconfigured TV channel. + +However, through the "detailed service offer" information and any referred guide, the IPTV terminal device may display the IPTV services offered by the selected service provider to allow the end-user to select one of them. Figure 12-1 is an example of service selection through a service guide description. + +![Figure 12-1: Example of live channel selection through a service guide. The diagram shows a flow from 'Entry point data' to two 'Service provider discovery record' boxes. From the top box, a bold line leads to 'Linear TV discovery record', which then leads to a large pink arrow labeled 'Linear TV Channel'. A dotted bold line also connects the top 'Service provider discovery record' to 'Linear TV discovery record'. From the bottom 'Service provider discovery record', a bold line leads to 'Content guide discovery record', which leads to 'Guide for specific TV channels', which then leads to the 'Linear TV Channel' arrow. Another bold line from the bottom 'Service provider discovery record' leads to 'Package discovery record', which leads to 'Guide for VoD contents', which leads to an orange oval labeled 'Contents'. A third bold line from the bottom 'Service provider discovery record' leads to 'Service from other service provider record', which leads to 'Guide for other services', which leads to a green oval labeled 'Other services'. A final bold line from the bottom 'Service provider discovery record' leads to 'Other services discovery record', which also leads to the 'Other services' oval. The text 'H.770(09)_F12-1' is at the bottom right.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +Figure 12-1: Example of live channel selection through a service guide. The diagram shows a flow from 'Entry point data' to two 'Service provider discovery record' boxes. From the top box, a bold line leads to 'Linear TV discovery record', which then leads to a large pink arrow labeled 'Linear TV Channel'. A dotted bold line also connects the top 'Service provider discovery record' to 'Linear TV discovery record'. From the bottom 'Service provider discovery record', a bold line leads to 'Content guide discovery record', which leads to 'Guide for specific TV channels', which then leads to the 'Linear TV Channel' arrow. Another bold line from the bottom 'Service provider discovery record' leads to 'Package discovery record', which leads to 'Guide for VoD contents', which leads to an orange oval labeled 'Contents'. A third bold line from the bottom 'Service provider discovery record' leads to 'Service from other service provider record', which leads to 'Guide for other services', which leads to a green oval labeled 'Other services'. A final bold line from the bottom 'Service provider discovery record' leads to 'Other services discovery record', which also leads to the 'Other services' oval. The text 'H.770(09)\_F12-1' is at the bottom right. + +**Figure 12-1 – Example of live channel selection through a service guide** + +In the example above, the IPTV terminal device proceeds as follows (along the bold line): + +- 1) Acquisition of the "Service Provider Information" related to two service providers ("service provider discovery record" boxes). +- 2) Acquisition of the detailed service offer information of a certain service provider (content guide discovery, package discovery, service from other service provider discovery). +- 3) Access to TV content guide service (see clause 10.3). +- 4) Navigation through the guide. +- 5) Selection of a TV channel. +- 6) Tuning to the selected TV channel. + +Another solution for the IPTV terminal device was to make use of the "linear TV discovery" description and to select from it a linear TV channel (along the dotted bold line). + +For content selection and acquisition, with the exception of linear TV services, the IPTV terminal device proceeds as follows (as illustrated in Figure 12-2): + +- 1) Acquisition of the "Service Provider Information" related to two service providers ("service provider discovery record" boxes). +- 2) Acquisition of the detailed service offer information of certain service provider (content guide discovery, package discovery, service from other service provider discovery, other services discovery). +- 3) Access to VoD guide service. +- 4) Navigation through the guide. +- 5) Selection of a content. +- 6) Request of the content. + +![Flowchart illustrating content selection through a VoD Guide. The process starts with 'Entry point data' leading to two 'Service provider discovery record' boxes. These lead to five discovery record boxes: 'Linear TV discovery record', 'Content guide discovery record', 'Package discovery record', 'Service from other service provider record', and 'Other services discovery record'. The first three lead to 'Linear TV Channel', 'Guide for specific TV channels', and 'Guide for VoD contents' respectively. The last two lead to 'Guide for other services' and 'Other services'. 'Guide for VoD contents' and 'Guide for other services' both lead to 'Contents'. A thick curved arrow highlights the path from 'Entry point data' to 'Service provider discovery record', then to 'Package discovery record', then to 'Guide for VoD contents', and finally to 'Contents'.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +``` + +graph LR + EPD[Entry point data] --> SPDR1[Service provider discovery record] + EPD --> SPDR2[Service provider discovery record] + SPDR1 --> LTVDR[Linear TV discovery record] + SPDR1 --> CGDR[Content guide discovery record] + SPDR1 --> PDR[Package discovery record] + SPDR1 --> SOSPDR[Service from other service provider record] + SPDR1 --> OSDR[Other services discovery record] + SPDR2 --> LTVDR + SPDR2 --> CGDR + SPDR2 --> PDR + SPDR2 --> SOSPDR + SPDR2 --> OSDR + LTVDR --> LTC[Linear TV Channel] + CGDR --> GSTC[Guide for specific TV channels] + PDR --> GVC[Guide for VoD contents] + SOSPDR --> GOS[Guide for other services] + OSDR --> OS[Other services] + GVC --> C((Contents)) + GOS --> C + C -.-> OS + style LTC fill:#d9534f,stroke:#333,stroke-width:2px + style SPDR1 fill:#4a90e2,stroke:#333,stroke-width:1px + style SPDR2 fill:#4a90e2,stroke:#333,stroke-width:1px + style LTVDR fill:#f5e06e,stroke:#333,stroke-width:1px + style CGDR fill:#f5e06e,stroke:#333,stroke-width:1px + style PDR fill:#f5e06e,stroke:#333,stroke-width:1px + style SOSPDR fill:#f5e06e,stroke:#333,stroke-width:1px + style OSDR fill:#f5e06e,stroke:#333,stroke-width:1px + style GSTC fill:#ffffff,stroke:#333,stroke-width:1px + style GVC fill:#ffffff,stroke:#333,stroke-width:1px + style GOS fill:#ffffff,stroke:#333,stroke-width:1px + style OS fill:#92d050,stroke:#333,stroke-width:1px + style C fill:#f4b084,stroke:#333,stroke-width:1px + +``` + +H.770(09)\_F12-2 + +Flowchart illustrating content selection through a VoD Guide. The process starts with 'Entry point data' leading to two 'Service provider discovery record' boxes. These lead to five discovery record boxes: 'Linear TV discovery record', 'Content guide discovery record', 'Package discovery record', 'Service from other service provider record', and 'Other services discovery record'. The first three lead to 'Linear TV Channel', 'Guide for specific TV channels', and 'Guide for VoD contents' respectively. The last two lead to 'Guide for other services' and 'Other services'. 'Guide for VoD contents' and 'Guide for other services' both lead to 'Contents'. A thick curved arrow highlights the path from 'Entry point data' to 'Service provider discovery record', then to 'Package discovery record', then to 'Guide for VoD contents', and finally to 'Contents'. + +**Figure 12-2 – Example of content selection through a VoD Guide** + +# Annex A + +## Service discovery profile + +(This annex forms an integral part of this Recommendation.) + +The profiles in Tables A.1 and A.2 concern linear TV services. Profiles related to other IPTV services are for further study. + +NOTE – These profiles do not prohibit being used in conjunction with SI tables at the same time. + +**Table A.1 – Profile A for linear TV** + +| Items | | Specification | +|------------------------------------------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service provider discovery | Elements/attributes | Service provider discovery information (see clause 7) | +| | Delivery protocols |
    • – HTTP 1.1 or HTTP over TLS as pull mode
    • – DVBSTP as push mode
    | +| Service discovery | Elements/attributes |
    • – Linear TV discovery (see clause 10.1)
    • – Package discovery record (see clause 10.2)
    • – Content guide discovery record (see clause 10.3)
    | +| | Delivery protocols |
    • – HTTP or HTTP over TLS as pull mode
    • – DVBSTP as push mode
    | +| NOTE – Pull mode and push mode are not mandatory simultaneously. | | | + +**Table A.2 – Profile B for linear TV** + +| Items | | Specification | +|------------------------------------------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service provider discovery | Elements/attributes | Service provider discovery information (see clause 7) | +| | Delivery protocols |
    • – HTTP 1.1 or HTTP over TLS as pull mode
    • – FLUTE as push mode
    | +| Service discovery | Elements/attributes |
    • – Linear TV discovery (see clause 10.1)
    • – Package discovery record (see clause 10.2)
    • – Content guide discovery record (see clause 10.3)
    | +| | Delivery protocols |
    • – HTTP or HTTP over TLS as pull mode
    • – FLUTE as push mode
    | +| NOTE – Pull mode and push mode are not mandatory simultaneously. | | | + +# Appendix I + +## Multiple service platforms + +(This appendix does not form an integral part of this Recommendation.) + +This appendix presents two use-cases to illustrate the usage of service role information from clause 7.2. + +### I.1 Introduction to service role information + +A single organization may play various roles. Supplementary elements described in Table I.1-1 may be appended to service provider information or to other elements for identifying these roles and for finding service groupings. + +Possible roles of IPTV service related entities are: + +- Network provider: providing access network infrastructure for IPTV services. +- Service platform: facilitating IPTV services by providing equipment and services. +- SCP provider: providing service providers with SCP functionalities such as authentication, digital rights management (DRM) and conditional access system (CAS) functions. +- Service provider: providing linear TV, VoD, re-transmission, web services, etc., through "service platform". + +**Table I.1-1 – Service role information elements/attributes** + +| Element name | Description | M/O/C | Example(s) | +|-----------------------------|----------------------------------------------------------------------------------------|-------|-----------------------------------| +| Network provider identifier | Information regarding the network provider. | O | Network provider name, unique ID | +| Service platform identifier | Information regarding the organizational entity providing equipment and IPTV services. | O | Platform provider name, unique ID | +| SCP provider identifier | Information regarding SCP systems. | O | SCP provider name, unique ID | + +NOTE 1 – The above elements assist in identifying service providers. The information can be easily handled by existing mechanisms such as those of [b-ETSI TS 183 063] and [b-ATIS-0800017]. Although there is no metadata format, when the service discovery information is transmitted using DVBSTP, the service provider identifier can be inserted into the multicast UDP packet header. + +NOTE 2 – Network\_id may be used as the service platform identifier if SI is transmitted (see Appendix III). + +### I.2 Multiple service platforms + +In this use-case, multiple service platforms provide IPTV services produced by one service provider. The following conditions are assumed: + +- The service provider is a type of "Complementary service provider" which is visible to the end-user (see [b-ITU-T M.3050.4]). +- The end-user can subscribe to any service platform. +- The service provider creates the service discovery information. + +![Diagram illustrating the case of providing different services from one service provider. At the top, an orange box labeled 'SP' contains two yellow octagons labeled 'Service α' and 'Service β'. Below 'Service α' is a green box labeled 'Platform α', and below 'Service β' is a green box labeled 'Platform β'. Both platforms point to a central blue box labeled 'Network provider'. Below the network provider, two white boxes represent 'Service Discovery Information 1' and 'Service Discovery Information 2'. Arrows indicate that 'Service Discovery Information 1' is associated with 'SP', 'PF α', 'NP', and 'Service α', while 'Service Discovery Information 2' is associated with 'SP', 'PF β', 'NP', and 'Service β'. The diagram is labeled H.770(09)_FI-1 at the bottom right.](f57c7b37d7a05a99618104f390089f03_img.jpg) + +Diagram illustrating the case of providing different services from one service provider. At the top, an orange box labeled 'SP' contains two yellow octagons labeled 'Service α' and 'Service β'. Below 'Service α' is a green box labeled 'Platform α', and below 'Service β' is a green box labeled 'Platform β'. Both platforms point to a central blue box labeled 'Network provider'. Below the network provider, two white boxes represent 'Service Discovery Information 1' and 'Service Discovery Information 2'. Arrows indicate that 'Service Discovery Information 1' is associated with 'SP', 'PF α', 'NP', and 'Service α', while 'Service Discovery Information 2' is associated with 'SP', 'PF β', 'NP', and 'Service β'. The diagram is labeled H.770(09)\_FI-1 at the bottom right. + +**Figure I.1 – The case of providing different services from one service provider** + +NOTE – The exact format of service role information elements/attributes is for further study. These may be added to the "Service discovery information" (as indicated in Figure I.1), to the "Service provider discovery information" or distributed among them. + +In this use-case, additional service provider information, such as network provider's service platform described in Table I.1-1, assists in the identification of available services. Arrow lines in Figure I.1 indicate the flows of services relevant to respective service discovery information. If an end-user subscribes only to "Service Platform α", service discovery information 1 is selected by the service platform identifier. + +### I.3 Service mobility + +In this use-case, service mobility is possible through interworking between two different network providers. It is assumed that one service provider provides services through different service platforms. "Network Provider a" is normally accessed as the permanent home-network, and "Network Provider b" is temporarily used as a visited network. + +When an end-user accesses the visited network, the IPTV terminal device checks the item concerning network provider identifier information and changes its configuration to the new network accordingly. Moreover, when an end-user accesses a visited network, the IPTV terminal device can properly select the relevant service discovery information with the service platform identifier. + +In Figure I.2, "Network Provider b" is a visited network. The IPTV terminal has to select "Service Discovery Information 2" or "Service Discovery Information 3". Since the end-user subscribes to "Platform α", the IPTV terminal device would select "Service Discovery Information 2". + +![Figure I.2: The case of service mobility. A Service Provider (SP) box contains a yellow octagon labeled 'Service'. Below it are two green boxes labeled 'Platform α' and 'Platform β'. Below these are two blue boxes: 'Network provider a (Home-network)' and 'Network provider b (Visited-network)'. Arrows point from the SP to both platforms, and from each platform to its respective network provider. Below each network provider is a white box labeled 'Service Discovery Information' with a number (1, 2, or 3). Box 1 (under NP a) lists: .SP, .PF α, .NP a, .Service. Box 2 (under NP a) lists: .SP, .PF α, .NP b, .Service. Box 3 (under NP b) lists: .SP, .PF β, .NP b, .Service. A label 'H.770(09)_FI-2' is at the bottom right.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +Figure I.2: The case of service mobility. A Service Provider (SP) box contains a yellow octagon labeled 'Service'. Below it are two green boxes labeled 'Platform α' and 'Platform β'. Below these are two blue boxes: 'Network provider a (Home-network)' and 'Network provider b (Visited-network)'. Arrows point from the SP to both platforms, and from each platform to its respective network provider. Below each network provider is a white box labeled 'Service Discovery Information' with a number (1, 2, or 3). Box 1 (under NP a) lists: .SP, .PF α, .NP a, .Service. Box 2 (under NP a) lists: .SP, .PF α, .NP b, .Service. Box 3 (under NP b) lists: .SP, .PF β, .NP b, .Service. A label 'H.770(09)\_FI-2' is at the bottom right. + +**Figure I.2 – The case of service mobility** + +### I.4 An example of service discovery processes + +This clause illustrates the processes of service discovery for a case with multiple service entities. Figure I.3 shows a simple case to explain the processes. There are two network providers and two service providers; moreover, service provider S connects to two network providers. In this figure, content provider is the entity that owns or is licensed to sell content or content assets [ITU-T Y.1910], but this entity does not concern the service discovery processes. + +![Figure I.3: Basic IPTV service provider model. Two green boxes at the top are 'Content provider D' and 'Content provider E'. Below them are two orange boxes: 'Service provider P' and 'Service provider S'. At the bottom are two blue boxes: 'Network provider A' and 'Network provider B'. Arrows show Content provider D pointing to Service provider P, which points to Network provider A. Content provider E points to both Service provider P and Service provider S. Service provider P points to Network provider A, and Service provider S points to Network provider B. A label 'H.770(09)_FI-3' is at the bottom right.](04cfca33e3fc26513abe649d7474f733_img.jpg) + +Figure I.3: Basic IPTV service provider model. Two green boxes at the top are 'Content provider D' and 'Content provider E'. Below them are two orange boxes: 'Service provider P' and 'Service provider S'. At the bottom are two blue boxes: 'Network provider A' and 'Network provider B'. Arrows show Content provider D pointing to Service provider P, which points to Network provider A. Content provider E points to both Service provider P and Service provider S. Service provider P points to Network provider A, and Service provider S points to Network provider B. A label 'H.770(09)\_FI-3' is at the bottom right. + +**Figure I.3 – Basic IPTV service provider model** + +The details of the respective service discovery processes shown in Figure I.4 are as follows: + +- 1) The IPTV terminal device, at network connection set-up on one of the network providers (A or B), gets one or more entry points from the network provider. There may be one entry point for each service provider or an entry point for a common service provider description repository. +- 2) From the left-side entry point(s), the terminal device gets the description of the IPTV service providers available on that network provider with a summary of the services offered by these service providers and entry points for detailed service offers. +- 3) From the third entry point for detailed service offer, the terminal device gets a detailed description of each service and can select one of them (e.g., Channel A). + +![Flowchart of the ITU-T H.770 service discovery process showing a sequence of steps from network connection set-up to service access via multiple entry points.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +``` + +graph LR + A[Network connection set-up] --> B[Entry point\(s\)] + B --> C((Entry point)) + C --> D[Service provider description +\(summary of service offers +and entry points for +detailed service offers\)] + D --> E((Entry point)) + E --> F[Detailed service offers +incl. service entry points] + F --> G((Entry point)) + G --> H[Service +\(e.g., channel A\)] + + subgraph " " + direction TB + C -.-> D + E -.-> F + G -.-> H + end + +``` + +H.770(09)\_FI.4 + +Flowchart of the ITU-T H.770 service discovery process showing a sequence of steps from network connection set-up to service access via multiple entry points. + +**Figure I.4 – ITU-T H.770 service discovery process** + +# Appendix II + +## Requirements in other standards organizations + +(This appendix does not form an integral part of this Recommendation.) + +In this part, requirement levels are compared to those of major standards organizations. + +Mandatory elements and attributes are shown as "M", optional ones are shown as "O", conditional requirements are shown as "C" and "—" indicates that there are no corresponding elements/attributes. + +Element and attribute names are the same as in the main text. Exact names of elements and attributes are different between standards; however, the corresponding elements and attributes are compared based on their semantics. + +### II.1 Service provider discovery information + +**Table II.1-1 – Service provider information record** + +| Element/Attribute | DVB | ATIS-IIF | ITU-T | +|-----------------------------------------|-----|----------|-------| +| Record type | M | M | M | +| Record version | M | O | M | +| Individual service provider information | M | M | M | + +**Table II.1-2 – Individual service provider information elements/attributes** + +| Element/Attribute | DVB | ATIS-IIF | ITU-T | +|-------------------------------------------------|-------------|----------|-------| +| Service provider identifier | M
    (Note) | O | M | +| Individual service provider information version | M | O | M | +| Service provider logo URI | O | O | O | +| Service provider name | M | O | O | +| Service provider description | O | O | O | +| Web portal URL | — | O | O | +| Service offer summary(s) | M | — | M | +| NOTE – Uses DNS host name. | | | | + +**Table II.1-3 – Service offer summary elements/attributes** + +| Element/Attribute | DVB-IP | ATIS-IIF | ITU-T | +|-------------------------------------------------------------------------------------------------------|--------|---------------|---------------| +| Push address | M | M
    (Note 1) | C
    (Note 2) | +| Pull URL | O | M
    (Note 1) | C
    (Note 2) | +| Offer type | O | — | O | +| Segment identifier and version | O | — | O | +| NOTE 1 – One of locator information is required.
    NOTE 2 – One of them is required to be presented. | | | | + +### II.2 Detailed service offer information + +**Table II.2-1 – Linear TV discovery record** + +| Element/Attribute | DVB | ATIS | ITU-T | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|-------| +| Record type | M | M | M | +| Service provider identifier | M
    (Note 1) | M | M | +| Record version | C
    (Note 2) | M | M | +| Metadata server URL | O | O | O | +| Portal URL | O | O | O | +| Purchase information URL | – | –
    (Note 3) | O | +| Linear TV service(s) | M | M | M | +| NOTE 1 – Uses DNS host name.
    NOTE 2 – Record version is mandatory when the record is provided on request (i.e., pull mode) and is optional when the record is multicast (i.e., push mode).
    NOTE 3 – Purchase information (e.g., rights owners, publishers) is treated as EPG metadata in ATIS. Requirement level in ATIS is optional [b-ATIS-0800020]. | | | | + +**Table II.2-2 – Linear TV services elements/attributes** + +| Element/Attribute | DVB | ATIS | ITU-T | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|-------| +| Service identifier | M
    (Note 1) | M | M | +| Original network Id | M | O | O | +| Transport stream Id | M | O | O | +| Service Id | M | O | O | +| Max bit rate | O | –
    (Note 2) | O | +| Service location(s) | M | M | M | +| Audio coding | O | O | O | +| Video coding | O | O | O | +| Service availability | O | – | O | +| Streaming type | O | – | O | +| Multiplex mode | – | –
    (Note 3) | O | +| NOTE 1 – Uses DNS host name.
    NOTE 2 – ATIS requires rate type such as constant bit rate (CBR), variable bit rate (VBR).
    NOTE 3 – ATIS handles IP or RF as content source. | | | | + +**Table II.2-3 – Service location elements/attributes** + +| Element/Attribute | DVB | ATIS | ITU-T | +|---------------------------------------------------------------------|-------------|-------------|--------------| +| IP multicast address | M | M | M | +| IP multicast port | M | M | M | +| IP multicast source | O
    (Note) | O
    (Note) | O
    (Note) | +| Unicast URL | O | – | – | +| NOTE – Source address is mandatory when IPv6 multicast is deployed. | | | | + +**Table II.2-4 – FEC elements/attributes** + +| Element/Attribute | DVB | ATIS | ITU-T | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|---------------| +| FEC base layer multicast address | M
    (Note 1) | M | M | +| FEC enhancement layer multicast address | O
    (Note 1) | O | O | +| Maximum packet number in blocks | O | M | O | +| Maximum FEC block duration | O | M | O | +| FEC specific information | C
    (Note 2) | C
    (Note 2) | C
    (Note 2) | +| NOTE 1 – IP multicast port is mandatory for FEC. IP multicast and IP multicast source are optional.
    NOTE 2 – This information is required when FEC enhancement layer is used. | | | | + +**Table II.2-5 – Service availability elements/attributes** + +| Element/Attribute | DVB | ATIS | ITU-T | +|--------------------------|------------|-------------|--------------| +| Country code | M | – | O | +| Availability | O | – | O | +| Region codes | O | – | O | + +**Table II.2-6 – Additional linear TV discovery elements/attributes** + +| Element/Attribute | DVB | ATIS | ITU-T | +|----------------------------------------------|------------|-------------|--------------| +| Type of service | M | M | M | +| Priority SI source | O | – | O | +| Service name | M | O
    (Note) | O | +| Service description | O | O
    (Note) | O | +| Content guide discovery record identifier(s) | O | – | O | +| Preferred content guide discovery record | O | O
    (Note) | O | +| Service genre(s) | O | O
    (Note) | O | + +**Table II.2-6 – Additional linear TV discovery elements/attributes** + +| Element/Attribute | DVB | ATIS | ITU-T | +|---------------------------------------------------|-----|------|-------| +| Announcement stream | O | – | O | +| Secondary service Id | O | – | O | +| Mosaic information | O | – | O | +| NOTE – Provided by EPG metadata [b-ATIS-0800020]. | | | | + +**Table II.3-1 – Package discovery record** + +| Element/Attribute | DVB | ATIS | ITU-T | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|-------| +| Record type | M | M
    (Note 1) | M | +| Service provider identifier | M
    (Note 2) | M
    (Note 1) | M | +| Record version | C
    (Note 3) | M
    (Note 1) | M | +| Package identifier | M | M
    (Note 1) | M | +| Displayable | O | – | O | +| Package name | M | – | O | +| Package description | O | M
    (Note 1) | O | +| Content guide discovery record identifier | O | – | O | +| Preferred content guide discovery record | O | – | O | +| Package reference(s) | O | – | O | +| Individual service(s) (Note 4) | M | M
    (Note 1) | M | +| Package availability | O | – | O | +| NOTE 1 – ATIS handles information regarding linear TV services as "Virtual Channel" related metadata.
    NOTE 2 – Uses DNS domain name.
    NOTE 3 – Record version is mandatory when the record is provided on request (i.e., "pull mode") and is optional when the record is multicast (i.e., "push mode").
    NOTE 4 – At least one individual service element is required. | | | | + +**Table II.3-2 – Individual service elements/attributes** + +| Element name | DVB | ATIS | ITU-T | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|---------------|-------| +| Individual service provider identifier | O | O
    (Note 1) | O | +| Service identifier | M | M | M | +| Additional service description | O | O
    (Note 2) | O | +| Logical channel number | O | M | O | +| NOTE 1 – ATIS can handle "virtual channel" related metadata as the equivalent identifiers [ATIS-0800022].
    NOTE 2 – Provided by EPG metadata [b-ATIS-0800020]. | | | | + +**Table II.4-1 – Content guide discovery record** + +| Element/Attribute | DVB | ATIS | ITU-T | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|------|-------| +| Record type | M | M | M | +| Service provider identifier | M
    (Note 1) | O | M | +| Record version | C
    (Note 2) | O | O | +| Content guide discovery record identifier | M | – | M | +| Content guide name | M | – | O | +| Content guide provider name | O | M | O | +| Content guide description | O | O | O | +| Content guide locator | M | M | M | +| Content guide logo URI | O | O | O | +| Content guide type | O | – | O | +| Target service provider identifier | O | O | O | +| NOTE 1 – Uses DNS domain name.
    NOTE 2 – Record version is mandatory when the record is provided on request (i.e., "pull mode") and is optional when the record is multicast (i.e., "push mode"). | | | | + +**Table II.5-1 – Service from other service provider's record** + +| Element/Attribute | DVB | ATIS | ITU-T | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|------|---------------| +| Record type | M | – | M | +| Service provider identifier | M
    (Note 1) | – | M | +| Record version | C
    (Note 2) | – | C
    (Note 2) | +| Referenced service provider identifier | – | – | O | +| Service identifier(s) | – | – | O | +| NOTE 1 – Uses DNS domain name.
    NOTE 2 – Record version is mandatory when the record is provided on request (i.e., "pull mode") and is optional when the record is multicast (i.e., "push mode"). | | | | + +**Table II.6-1 – Other service discovery record** + +| Element/Attribute | DVB | ATIS | ITU-T | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------|--------------| +| Record type | M | – | M | +| Service provider identifier | M
    (Note 1) | – | M | +| Record version | O
    (Note 2) | – | O | +| Service name | M | – | O | +| Service identifier | O | – | M | +| Service description | O | – | O | +| Service locator | M | – | M | +| NOTE 1 – Uses DNS domain name.
    NOTE 2 – Record version is mandatory when the record is provided on request (i.e., "pull mode") and is optional when the record is multicast (i.e., "push mode"). | | | | + +# Appendix III + +## The usage of TS with service discovery information + +(This appendix does not form an integral part of this Recommendation.) + +### III.1 Study on the SI tables + +Service information (SI) consists of information tables defined by each standard. In order to compare the tables, it is convenient to illustrate the terms and identifiers defined by DVB-SI ([ETSI EN 300 468]) and ARIB-SI ([b-ARIB B10]): + +- network: collection of MPEG-2 transport stream (TS) multiplexes transmitted on a single delivery system. +- original\_network\_id: unique identifier of a delivery system (e.g., specific cable network, satellite network and terrestrial network). +- network\_id: unique identifier of a current delivery system. +- service: sequence of programmes under the control of a broadcaster, which can be broadcast as part of a schedule. +- service\_id: unique identifier of a service within a TS (i.e., channel). +- transport\_stream\_id: unique identifier of a TS within an original network. +- event\_id: unique identifier of a programme within a service. + +ATSC-PSIP ([b-ATSC A/65]) uses the idea of the following virtual channel: + +- virtual channel: A virtual channel is a designation, usually a number, which is recognized by the end-user as a single entity that will provide access to a set of one or more digital elementary streams. It is called "virtual" because its identification (name and number) may be defined independently from its physical location. +- source\_id: unique identifier for a virtual channel, almost the same as service\_id. + +Figure III.1 shows the image of entities carried over a delivery system using each identifier mentioned above. + +![Diagram illustrating network identifiers (Network_id, transport_stream_id, event_id, service_id) across different delivery systems (terrestrial and satellite).](9dc9f41d7d76c1add4b190d348cb1533_img.jpg) + +The diagram illustrates the hierarchy of network identifiers in a digital broadcast system. On the left, a terrestrial tower and a satellite are shown. The terrestrial tower is connected to a large green circle labeled 'Network\_id'. Inside this circle, a yellow cylinder represents a transport stream, labeled 'transport\_stream\_id'. Within this transport stream, three orange cylinders represent events, labeled 'event\_id', with timestamps 19:00, 18:00, and 17:00 above them. Each event cylinder is also labeled 'service\_id'. Below the terrestrial tower, a satellite is shown, connected to a smaller green circle also labeled 'Network\_id'. Inside this satellite's network, two yellow cylinders represent transport streams, both labeled 'transport\_stream\_id'. + +Diagram illustrating network identifiers (Network\_id, transport\_stream\_id, event\_id, service\_id) across different delivery systems (terrestrial and satellite). + +H.770(09)\_FIII-1 + +**Figure III.1 – Network identifiers** + +DVB-SI/ARIB-SI usually specifies services uniquely by using a triplet of original\_network\_id, transport\_stream\_id and service\_id. + +Table III.1-1 shows the usage of the main tables of service information according to the different standards. Details of the tables (e.g., key elements/attributes, relationship among tables) and the usage of the tables are defined by each respective standards organization, except for PAT and PMT which are defined by [ITU-T H.222.0]. For example, ARIB originates broadcast information table (BIT) as a container of broadcaster information. + +Table III.1-2 shows, in a simplistic way, the roles and characteristics of SI tables. For the details of SI tables (mainly original descriptors), see the relevant standard. + +**Table III.1-1 – Comparison of SI tables used in digital terrestrial (Note 1)** + +| | DVB-SI | ARIB-SI | ATSC-PSIP | +|------------------------------------|------------------------|---------|-----------| +| ITU-T H.222.0
    ISO/IEC 13818-1 | PAT | | | +| | PMT | | | +| Individual
    definition | NIT, SDT, BAT (Note 2) | | MGT, VCT | +| | EIT (Note 2) | | EIT, ETT | +| | – | BIT | – | + +NOTE 1 – This table omits some SI tables regarding system time, rights control and parental rating. +NOTE 2 – Exact descriptors contained in SI tables are different between DVB and ARIB. + +**Table III.1-2 – SI tables defined by standards development organizations** + +| Table name | | Information
    conveyed | Typical table identifiers
    (Notes 1, 2) | Looped identifier/
    descriptor
    (Notes 1, 2) | +|------------|-------------------------------|-------------------------------------------------------------------|-------------------------------------------|----------------------------------------------------------------| +| Abbr. | Full name | | | | +| PAT | Program association table | Locations (the Packet identifier (PID)) of corresponding PMT, NIT | TS_id | Program number and program map table PID | +| PMT | Program map table | Locations of streams, program clock reference | program_number, PCR_ID | PID values for components of one or more programs | +| NIT | Network information table | TS and its transmitting path | network_id | original_network_id, TS_id | +| SDT | Service description table | Programmed channel as services within a TS | original_network_id, TS_id, | service_id, channel name | +| EIT | Event information table | TV programs within a programmed channel | original_network_id, TS_id, service_id | event_id, program name/description, broadcasting date and time | +| BAT | Bouquet association table | A set of programmed channels | bouquet_id | original_network_id, TS_id, bouquet name, service list | +| BIT | Broadcaster information table | SI transmission parameter of each broadcaster unit. | original_network_id | Broadcaster identifier/name, circulation periods of tables | + +**Table III.1-2 – SI tables defined by standards development organizations** + +| Table name | | Information conveyed | Typical table identifiers (Notes 1, 2) | Looped identifier/descriptor (Notes 1, 2) | +|------------|-----------------------|-------------------------------------------------------------------------------|----------------------------------------|-------------------------------------------| +| Abbr. | Full name | | | | +| MGT | Master guide table | Top level of PSIP tables. Identifies what PSIP tables are in transport stream | Table_id | PID values for tables, table type | +| VCT | Virtual channel table | Content within a TS, its number as virtual channel | TS_id | Assigned_TS_id, Source_id, channel number | +| ETT | Extended text table | Detailed description of virtual channels and programs | ETT_table_id_extention | Text messages | + +NOTE 1 – Names of identifiers and descriptors are modified in this Recommendation. +NOTE 2 – Looped identifier/descriptor are defined repeatedly in a table. + +### III.2 Classification of TS with SI + +Well-known "TS-Full SI" and "TS-Optional SI" defined by DVB are as follows: + +- TS-Full SI [ETSI TS 102 034]: A transport stream with embedded service information (SI) as defined by broadcasting standards organizations (e.g., ARIB, ATSC and DVB). +- TS-Optional SI [ETSI TS 102 034]: A transport stream with MPEG PSI (PAT and PMT tables) as defined by ISO/IEC; all other MPEG-2 and other tables are optional. + +These definitions are slightly modified for this Recommendation. Based on the definitions, TS-Optional SI includes TS-Full SI (i.e., TS-Full SI is a specific case of TS-Optional SI). + +Linear TV services delivered over MPEG-2 transport stream (TS) can have "service information (SI)" embedded. The SI obtains important information for the process of service discovery, especially in traditional broadcasting services (e.g., used in up/down channel changing, channel selection by channel numbers, or display of EPG). Information on individual services is afterwards acquired from the transport stream itself, one by one, through classical use of SI. When SI is embedded in TS, IPTV terminal devices need to connect all services and parse all SI to build a service list (see [b-ETSI TS 102 542]). + +"TS-Full SI" is compliant with the DVB-SI, ARIB-SI and ATSC-PSIP specifications (with all the SI/PSIP tables), but with a reduced/customized size, carried over IP, just as in retransmission of broadcast channel captured from satellite or terrestrial broadcast. + +"TS-optional SI" is intended for the situation where a service provider wants to present its services, but cannot afford or does not want to use bandwidth for usual service description information ([ETSI TS 102 034]). + +Concrete information contained in TS-Full SI (i.e., SI tables and their descriptors) is different for each standards development organization. For example, TS-Full SI defined by DVB which does not include NIT may be treated as TS-Optional SI in ARIB. + +### III.3 Variation of the usage of service discovery information + +TS-Optional SI allows selecting and using SI tables within a transport stream as mentioned above. The following table shows the case of combination of service discovery information records. The detail of service information may be different for each country because of the details of their specifications. Case 1 may comprise DVB's TS-Full SI ([b-ETSI TS 102 542]). + +**Table III.3-1 – Variation of the TS with service discovery information** + +| Information | SI | Case 1 | Case 2 | Case 3 | +|---------------------------|--------------|------------------------------------|---------------------------------------------|-----------------------------------------| +| Service provider | NIT | Service provider discovery records | NIT plus service provider discovery records | Service provider discovery records | +| Service description | SDT (Note 1) | SDT (Note 1) | SDT (Note 1) | Linear TV discovery records | +| Service location | NIT | Linear TV discovery records | NIT | Linear TV discovery records | +| Program schedule | EIT (Note 2) | EIT (Note 2) | EIT (Note 2) | Content guide discovery record (Note 4) | +| Package | BAT (Note 3) | BAT (Note 3) | Package discovery records | Package discovery records | +| Logical (virtual) channel | (VCT) | (VCT) | Package discovery records | Package discovery records | + +NOTE 1 – In case of ATSC, SDT corresponds to MGT plus EIT. +NOTE 2 – In case of ATSC, EIT corresponds to MGT plus EIT. +NOTE 3 – In case of ATSC, BAT corresponds to VCTs. +NOTE 4 – Content guide discovery record supports discovery of a content guide which includes schedule information. The details of the content guide itself is for further study. + +## Appendix IV + +## Alternative methods for entry point handling + +(This appendix does not form an integral part of this Recommendation.) + +Alternative methods for delivery and handling of entry data are as follows [b-ATIS-0800017], [b-ETSI TS 183 063]: + +- Preconfigured methods + - IPTV terminal devices may be preconfigured or manually configured with service discovery information. +- DHCP-based methods + - DHCP [b-IETF RFC 2131] container option can deliver entry point data information when the IPTV terminal device acquires network information, such as its own IP address, from a DHCP server. + +NOTE 1 – There is substantial variation in the usage of container option and details of these have not been agreed by IETF. + +- Download methods (also known as pull mode). + - IPTV terminal devices may download information using the unicast-based procedure such as trivial file transfer protocol (TFTP) [b-IETF RFC 1350], HTTP. +- TR-069 protocol-based method + - Remote management system can provide addressing information of service providers with the TR-069 protocol ([BBF TR-069]). +- DNS service records (SRV)-based method + - The result of DNS SRV [b-IETF RFC 2782] lookup can provide available IPTV service servers within the specified domain name. + +NOTE 2 – This method is often used when a session initiation protocol (SIP) server finds the locations of services as FQDN. + +# Appendix V + +## Service discovery using TR-069 + +(This appendix does not form an integral part of this Recommendation.) + +### V.1 Service discovery profile for TR-069 + +The profiles in Table V.1 concern service discovery in IPTV services by using TR-069 specifications [BBF TR-069]. + +**Table V.1 – Profile for TR-069** + +| Items | | Specification | +|----------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Service provider discovery | Elements/attributes | Service provider discovery information (see clause 7) | +| | Delivery protocols | TR-069 | +| Service discovery | Elements/attributes | Linear TV discovery (see clause 10.1)
    Package discovery record (see clause 10.2)
    Content guide discovery record (see clause 10.3) | +| | Delivery protocols | TR-069 | + +### V.2 Service provider discovery using TR-069 + +#### V.2.1 Introduction + +When after the network attachment, the search for entry points for IPTV service providers delivers the location of a network provider configuration server, the dialogue between the configuration server and the configuration client in the IPTV terminal device allows to configure in the "STBService" object (defined in [BBF TR-135]) either a list of entry points to get service provider information or directly the service information. + +Entry points are either: + +- Multicast address to get service provider information in push mode (IGMP, MLD, etc.). +- Unicast address to get service provider information in pull mode (HTTP, etc.). +- Unicast address to get service provider information using TR-069. + +If entry points are available, the IPTV terminal device will acquire the service provider information using these entry points using the corresponding acquisition methods (pull or push modes). + +An extension of TR-135 is defined as follows to store the service provider information as specified in clause 7 (Service provider information). + +#### V.2.2 TR-135 extension for service provider discovery + +The "STBService" object structure specified in TR-135 is represented in Figure V.1. + +The TR-135 component "FrontEnd.IP" is extended by the addition of a new parameter "service discovery" as shown in Figure V.2. + +The parameters in Table V.2 are added for service provider discovery. + +![Figure V.1: TR-135 STBService object structure diagram. The diagram shows a hierarchical structure for STBService {i}. It is divided into three main columns: Capabilities, Components, and ServiceMonitoring. Capabilities include FrontEnd (DVBT, IP), PVR, AudioDecoder, VideoDecoder (MPEG2 Part2, MPEG4 Part2, MPEG4 Part10, SMPTE VC1), AudioOutput, VideoOutput (CA, DRM), ServiceMonitoring, and AudienceStats. Applications include AudienceStats and Channel {i}. Components include FrontEnd {i} (DVBT: Modulation, Install, ServiceListDB, LogChannel {i}, Service {i}, ChannelConnect, ServiceConnect; IP: RTCP, IGMP, RTPAVPF, Dejittering, Inbound {i}, Outbound {i}, ServiceConnect), PVR (Storage {i}), SCART {i}, CA {i}, DRM {i}, AudioDecoder {i}, VideoDecoder {i}, AudioOutput {i}, VideoOutput {i}, AVPlayers (AVPlayer {i}), and AVStreams (AVStream {i}). ServiceMonitoring includes MainStream {i} (Total: DejitteringStats, RTPStats, MPEG2TSStats, VideoDecoderStats, AudioDecoderStats, VideoResponseStats; Sample: DejitteringStats, RTPStats, MPEG2TSStats, VideoDecoderStats, AudioDecoderStats, VideoResponseStats, HighLevelMetricStats {i}).](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +Figure V.1: TR-135 STBService object structure diagram. The diagram shows a hierarchical structure for STBService {i}. It is divided into three main columns: Capabilities, Components, and ServiceMonitoring. Capabilities include FrontEnd (DVBT, IP), PVR, AudioDecoder, VideoDecoder (MPEG2 Part2, MPEG4 Part2, MPEG4 Part10, SMPTE VC1), AudioOutput, VideoOutput (CA, DRM), ServiceMonitoring, and AudienceStats. Applications include AudienceStats and Channel {i}. Components include FrontEnd {i} (DVBT: Modulation, Install, ServiceListDB, LogChannel {i}, Service {i}, ChannelConnect, ServiceConnect; IP: RTCP, IGMP, RTPAVPF, Dejittering, Inbound {i}, Outbound {i}, ServiceConnect), PVR (Storage {i}), SCART {i}, CA {i}, DRM {i}, AudioDecoder {i}, VideoDecoder {i}, AudioOutput {i}, VideoOutput {i}, AVPlayers (AVPlayer {i}), and AVStreams (AVStream {i}). ServiceMonitoring includes MainStream {i} (Total: DejitteringStats, RTPStats, MPEG2TSStats, VideoDecoderStats, AudioDecoderStats, VideoResponseStats; Sample: DejitteringStats, RTPStats, MPEG2TSStats, VideoDecoderStats, AudioDecoderStats, VideoResponseStats, HighLevelMetricStats {i}). + +H.770-Amd.2(10)\_F.V.1 + +Figure V.1 – TR-135 STBService object structure + +![Figure V.2: TR-135 Extension of FrontEnd.IP object structure diagram. This diagram shows the internal structure of the IP object within FrontEnd {i}. It includes RTCP, IGMP, RTPAVPF, Dejittering, Inbound {i}, Outbound {i}, ServiceConnect, and Service discovery (highlighted in orange).](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Figure V.2: TR-135 Extension of FrontEnd.IP object structure diagram. This diagram shows the internal structure of the IP object within FrontEnd {i}. It includes RTCP, IGMP, RTPAVPF, Dejittering, Inbound {i}, Outbound {i}, ServiceConnect, and Service discovery (highlighted in orange). + +H.770-Amd.2(10)\_F.V.2 + +Figure V.2 – TR-135 Extension of FrontEnd.IP object structure + +**Table V.2 – Element/attributes for service provider discovery** + +| Name | Type | Write | Description | Default | +|-----------------------------------------------------------------------------------------|--------|-------|--------------------------------------------------------------------------------|---------| +| .STBService.{i}.
    Components.FrontEnd.{i}.
    IP.ServiceDiscovery. | object | | | | +| IptvServiceProviderInfoEntryList | string | – | List of entry points to get service provider information | Empty | +| .STBService.{i}.
    Components.FrontEnd.{i}.
    IP.ServiceDiscovery.ServiceProvider{i}. | object | | | | +| IptvServiceProviderInfoEntry | string | – | Entry point used to get the IptvServiceProviderInfo and to be used for updates | Empty | +| IptvServiceProviderInfo | string | – | Service provider information record as specified in ITU-T H.770 | Empty | + +### V.3 Detailed service offer discovery using TR-069 + +#### V.3.1 Introduction + +When the entry point to get detailed service offers is the location of a configuration server, the terminal device relates with the configuration server using TR-069 to configure service provider services in the STBService object specified in TR-135 extended, as specified below. + +The parameters in Table V.3 are added for detailed service offer discovery. + +**Table V.3 – Element/attributes for detailed service offer discovery** + +| Name | Type | Write | Description | Default | +|--------------------------------------------------------------------------------------------------------|--------|-------|----------------------------------------------------------------------------|---------| +| .STBService.{i}.Components.
    FrontEnd.{i}.IP.
    ServiceDiscovery.
    ServiceProvider{i}.Service{i}. | object | | | | +| IptvServiceInfoEntry | string | – | Entry point used to get the IptvServiceInfo and to be used for updates. | Empty | +| IptvServiceInfo | string | – | Service record (detailed service information) as specified in ITU-T H.770. | Empty | + +# Bibliography + +- [b-ITU-T F.700] Recommendation ITU-T F.700 (2000), *Framework Recommendation for multimedia services.* +- [b-ITU-T H.622] Recommendation ITU-T H.622 (2008), *A generic home network architecture with support for multimedia services.* +- [b-ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems.* +- [b-ITU-T J.90] Recommendation ITU-T J.90 (2000), *Electronic programme guides for delivery by digital cable television and similar methods – Reference operating scenario and requirements.* +- [b-ITU-T J.148] Recommendation ITU-T J.148 (2003), *Requirements for an objective perceptual multimedia quality model.* +- [b-ITU-T J.183] Recommendation ITU-T J.183 (2001), *Time-division multiplexing of multiple MPEG-2 transport streams over cable television systems.* +- [b-ITU-T J.200] Recommendation ITU-T J.200 (2010), *Worldwide common core – Application environment for digital interactive television services.* +- [b-ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2015), *Designations for interconnections among operators' networks.* +- [b-ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) – The business process framework.* +- [b-ITU-T M.3050.4] Recommendation ITU-T M.3050.4 (2007), *Enhanced Telecom Operations Map (eTOM) – B2B integration: Using B2B inter-enterprise integration with the eTOM.* +- [b-ITU-T T.174] Recommendation ITU-T T.174 (1996), *Application programming interface (API) for MHEG-1.* +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.* +- [b-ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services.* +- [b-ARIB B10] ARIB Standard B10 Version 5.4 (2014), *Service Information for Digital Broadcasting System.* +- [b-ATIS-0800002] ATIS standard ATIS-0800002 (2006), *IPTV Architecture Requirements.* +- [b-ATIS-0800013] ATIS standard ATIS-0800013.v002 (2012), *Media Formats and Protocols for IPTV services.* +- [b-ATIS-0800017] ATIS standard ATIS-0800017.v003 (2012), *Network Attachment and Initialization of Devices and Client Discovery of IPTV Services.* +- [b-ATIS-0800020] ATIS standard ATIS-0800020.v002 (2011), *IPTV Electronic Program Guide Metadata Requirements.* + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [b-ATSC A/65] | ATSC Standard A/65 (2013), Program and System Information Protocol for Terrestrial Broadcast and Cable . | +| [b-ETSI TR 101 211] | ETSI TR 101 211 V1.9.1 (2009), Digital Video Broadcasting (DVB); Guidelines on implementation and usage of Service Information (SI) . | +| [b-ETSI TS 102 323] | ETSI TS 102 323 V1.5.1 (2012), Digital Video Broadcasting (DVB); Carriage and signalling of TV-Anytime information in DVB transport streams . | +| [b-ETSI TS 102 542] | ETSI TS 102 542 V1.2.1 (2008), Digital Video Broadcasting (DVB); Guidelines for the implementation of DVB-IP Phase 1 specifications . | +| [b-ETSI TS 102 822-3-1] | ETSI TS 102 822-3-1 V1.8.1 (2012), Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 3: Metadata; Sub-part 1: Phase 1 – Metadata schemas . | +| [b-ETSI TS 102 826] | ETSI TS 102 826 V1.2.1 (2009), Digital Video Broadcasting (DVB); DVB-IPTV Profiles for TS 102 034 . | +| [b-ETSI TS 183 063] | ETSI TS 183 063 V2.8.1 (2011), Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3 specification . | +| [b-IETF RFC 1350] | IETF RFC 1350 (1992), The TFTP Protocol (Revision 2) . | +| [b-IETF RFC 2131] | IETF RFC 2131 (1997), Dynamic Host Configuration Protocol . | +| [b-IETF RFC 2326] | IETF RFC 2326 (1998), Real Time Streaming Protocol (RTSP) . | +| [b-IETF RFC 2782] | IETF RFC 2782 (2000), A DNS RR for specifying the location of services (DNS SRV) . | +| [b-IPTVFJ-0004] | IPTV Forum Japan IPTVFJ STD-0004 Version 1.1 (2008), IPTV Specification – Linear TV Specification (Japanese) . | +| [b-IPTVFJ-0006] | IPTV Forum Japan IPTVFJ STD-0006 Version 1.2 (2009), IPTV Specification – CDN-scope Service Approach Specification (Japanese) . | +| [b-W3C SOAP] | World Wide Web Consortium (W3C) Recommendation SOAP 1.2 (2007), Simple Object Access Protocol (SOAP) 1.2 . | + + + + + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/raw.md b/marked/H/T-REC-H.780-201206-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..56873efa1bac847e02bb34cdc1e19d029a0856ce --- /dev/null +++ b/marked/H/T-REC-H.780-201206-I_PDF-E/raw.md @@ -0,0 +1,1302 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.780** + +(06/2012) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +Digital Signage + +# --- **Digital signage: Service requirements and IPTV-based architecture** + +Recommendation ITU-T H.780 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|-------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.780 + +# Digital signage: Service requirements and IPTV-based architecture + +## Summary + +Recommendation ITU-T H.780 describes a general framework for digital signage (DS) services based on IPTV architecture from the viewpoint of technical and service aspects. First, DS domains, a generic DS architecture and the classification of DS services are introduced. As technical IPTV specifications are close to those of DS, a brief comparison between the two services is provided (e.g., structure of a functional group and detailed media processing). Subsequently, high-level requirements concerning DS services are described. In addition, this Recommendation contains content delivery methods and details of functionalities of both server- and client-side applications for DS services. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T H.780 | 2012-06-29 | 16 | + +## Keywords + +Content delivery, content management, digital signage, DS, DS services, playlist, terminal devices. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|------------|-------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Overview ..... | 5 | +| 6.1 | Digital signage domains ..... | 5 | +| 6.2 | Architecture overview ..... | 6 | +| 6.3 | Examples of services ..... | 8 | +| 6.4 | Types of terminal devices..... | 9 | +| 7 | Requirements ..... | 9 | +| 7.1 | General requirements..... | 9 | +| 7.2 | Content management ..... | 10 | +| 7.3 | Content delivery ..... | 10 | +| 7.4 | Security requirements ..... | 11 | +| 7.5 | Network requirements ..... | 11 | +| 7.6 | Terminal device requirements ..... | 11 | +| 8 | Functional architecture and key features ..... | 13 | +| 8.1 | Functionalities of digital signage applications ..... | 13 | +| 8.2 | Functionalities of terminal devices..... | 15 | +| 8.3 | Transport and control mechanisms..... | 16 | +| 8.4 | Security ..... | 17 | +| 8.5 | Audience measurement ..... | 17 | +| 9 | Metadata ..... | 17 | +| 9.1 | Content information..... | 17 | +| 9.2 | Terminal device information ..... | 18 | +| 9.3 | Ambient information ..... | 19 | +| 9.4 | Results of playing contents..... | 19 | +| 9.5 | Schedule-relevant information ..... | 19 | +| 10 | Terminal device interfaces..... | 20 | +| 10.1 | Input interfaces ..... | 20 | +| 10.2 | Output interfaces ..... | 20 | +| Appendix I | – Digital signage use cases ..... | 21 | +| I.1 | Screen for single content source..... | 21 | +| I.2 | Screen by using multiple content/data sources..... | 21 | + +| | Page | +|-------------------------------------------------------------------------|-------------| +| I.3     Emergency communications ..... | 24 | +| I.4     Interaction amongst audience and terminals ..... | 24 | +| I.5     High-level architecture expansion..... | 25 | +| Appendix II – Codecs and data formats for digital signage services..... | 26 | +| Appendix III – Privacy of digital signage services ..... | 27 | +| III.1    Overview ..... | 27 | +| III.2    Principles for privacy ..... | 27 | +| Appendix IV – Terminal device interfaces ..... | 28 | +| IV.1    Input interface..... | 28 | +| IV.2    Output interfaces ..... | 28 | +| Bibliography..... | 29 | + +## **List of Tables** + +| | Page | +|----------------------------------------------------------------------------|-------------| +| Table 1 – Relations of functional blocks among ITU-T Recommendations ..... | 15 | +| Table 2 – Common content elements/attributes..... | 18 | +| Table 3 – Common terminal device elements/attributes..... | 19 | +| Table 4 – Common ambient information elements/attributes..... | 19 | +| Table 5 – Common elements/attributes regarding play-logs ..... | 19 | +| Table II.1 – Standards of codecs and data formats ..... | 26 | +| Table II.2 – Standards of data wrapping..... | 26 | + +## **List of Figures** + +| | Page | +|------------------------------------------------------------------------------------|-------------| +| Figure 1 – Generic digital signage domains as per [ITU-T Y.1910] ..... | 5 | +| Figure 2 – Overview of digital signage architecture (based on [ITU-T Y.1910])..... | 7 | +| Figure 3 – Details of the server-side digital signage applications ..... | 13 | +| Figure 4 – Details of digital signage client ..... | 15 | +| Figure I.1 – Use case 1A: Flow for DS within an organization..... | 21 | +| Figure I.2 – Use case 2A: Flow for linking different businesses..... | 22 | +| Figure I.3 – Use case 2B: Flow for advertisement services..... | 23 | +| Figure I.4 – Use case 3: Disaster information service ..... | 24 | +| Figure I.5 – Expanded generic DS architecture ..... | 25 | + +# Recommendation ITU-T H.780 + +# Digital signage: Service requirements and IPTV-based architecture + +# 1 Scope + +This Recommendation addresses the high level requirements, architecture and mechanisms for dealing with aspects of digital signage contents, network, metadata and terminal devices on the basis of IPTV architecture [ITU-T Y.1910]. It is expected that requirements and relevant specifications identified in this Recommendation can be applied appropriately according to the digital signage services and their business models. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.1080] Recommendation ITU-T G.1080 (2008), *Quality of experience requirements for IPTV services*. +- [ITU-T G.1081] Recommendation ITU-T G.1081 (2008), *Performance monitoring points for IPTV*. +- [ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems*. +- [ITU-T H.721] Recommendation ITU-T H.721 (2009), *IPTV terminal devices: Basic model*. +- [ITU-T H.750] Recommendation ITU-T H.750 (2008), *High-level specification of metadata for IPTV services*. +- [ITU-T H.760] Recommendation ITU-T H.760 (2009), *Overview of multimedia application frameworks for IPTV*. +- [ITU-T H.770] Recommendation ITU-T H.770 (2009), *Mechanisms for service discovery and selection for IPTV services*. +- [ITU-T X.1191] Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects*. +- [ITU-T Y.1541] Recommendation ITU-T Y.1541 (2002), *Network performance objectives for IP-based services*. +- [ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services*. +- [ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*. +- [ISO/IEC 15938-5] ISO/IEC 15938-5:2003, *Information technology – Multimedia content description interface – Part 5: Multimedia description schemes*. +- [ISO/IEC 15938-5 Amd.2] ISO/IEC 15938-5:2005/Amd.2:2005, *Multimedia description schemes user preference extensions*. + +- [ETSI TS 102-822-3-1] ETSI TS 102 822-3-1 V1.7.1 (2011), *Broadcast and On-line Services: Search, select and rightful use of content on personal storage systems ("TV-Anycast"); Part 3: Metadata; Sub-part 1: Phase 1 – Metadata schemas.* +- [ETSI TS 102 822-3-3] ETSI TS 102 822-3-3 V1.5.1 (2011), *Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anycast"); Part 3: Metadata; Sub-part 3: Phase 2 – Extended Metadata Schema.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 content provider** [ITU-T Y.1910]: The entity that owns or is licensed to sell content or content assets. + +**3.1.2 distribution** [ITU-T Y.1910]: In the context of IPTV architecture, "distribution" is defined as sending the content to appropriate intermediate locations to enable subsequent delivery. + +**3.1.3 end user** [ITU-T Y.1910]: The actual user of the products or services. + +NOTE – The end user consumes the product or service. An end user can optionally be a subscriber. + +**3.1.4 functional architecture** [b-ITU-T Y.2012]: A set of functional entities and the reference points between them used to describe the structure of an NGN. These functional entities are separated by reference points, and thus, they define the distribution of functions. + +NOTE 1 – The functional entities can be used to describe a set of reference configurations. These reference configurations identify which reference points are visible at the boundaries of equipment implementations and between administrative domains. + +NOTE 2 – This definition is taken from [b-ITU-T Y.2012] and therefore relates to NGNs. However, it is also valid for other networks, e.g., networks supporting digital signage terminal devices. + +**3.1.5 functional entity** [b-ITU-T Y.2012]: An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. + +**3.1.6 media** [b-ITU-T Y.2012]: One or more of audio, video, or data. + +**3.1.7 multimedia** [b-ITU-T T.174]: The property of handling several types of representation media. + +**3.1.8 service provider** [b-ITU-T M.1400]: A general reference to an operator that provides telecommunication services to customers and other users either on a tariff or contract basis. A service provider can optionally operate a network. A service provider can optionally be a customer of another service provider. + +NOTE – Typically, the service provider acquires or licenses content from content providers and packages this into a service that is consumed by the end user. + +**3.1.9 terminal device (TD)** [ITU-T Y.1901]: An end-user device which typically presents and/or processes the content, such as a personal computer, a computer peripheral, a mobile device, a TV set, a monitor, a VoIP terminal or an audio-visual media player. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 content**: A combination of audio, still image, graphic, video, or data. + +NOTE – A variety of formats is classified as the "data" (e.g., text, encoded values, multimedia description language introduced by [ITU-T H.760]). + +**3.2.2 delivery:** Sending of contents to terminal devices. + +**3.2.3 digital signage (DS):** A system that sends information, advertising and other messages to electronic devices (e.g., displays, speakers) in accordance with the time of day and the location of the display, or the actions of audience. Contents and their relevant information, such as display schedules, are delivered over networks. + +**3.2.4 network provider:** The organization that maintains and operates the network components required to support a service or set of services. + +**3.2.5 playlist:** Composed of a list of contents. + +NOTE 1 – This data is created and provided by digital service providers. + +NOTE 2 – This data can be selected by an end user when interactivity is supported in a digital signage terminal device. + +NOTE 3 – This data may indicate an order of playing contents. + +**3.2.6 playlist schedule:** Composed of a list of playlists indicated by a specific play date and/or time. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|---------------------------------------------| +| DS | Digital Signage | +| DVI | Digital Visual Interface | +| DVI-A | Digital Visual Interface Analogue | +| DVI-D | Digital Visual Interface Digital | +| DVI-I | Digital Visual Interface Integrated | +| FLUTE | File delivery over unidirectional transport | +| FTP | File Transfer Protocol | +| HDMI | High Definition Multimedia Interface | +| HTTP | Hyper Text Transfer Protocol | +| HTTPS | HTTP over SSL/TLS | +| IPTV | Internet Protocol Television | +| LAN | Local Area Network | +| LCD | Liquid Crystal Display | +| LVDS | Low Voltage Differential Signalling | +| MAC | Media Access Control | +| OLED | Organic Light Emitting Diode display | +| PC | Personal Computer | +| PDA | Personal Digital Assistant | +| PDP | Plasma Display Panel | +| PII | Personally Identifiable Information | +| QoE | Quality of Experience | + +| | | +|--------|-------------------------------------------------| +| QoS | Quality of Service | +| RAM | Random Access Memory | +| RGB | Red-Green-Blue colour model | +| RTP | Real-time Transport Protocol | +| SADS | Service and Application Discovery and Selection | +| SMS | Short Message Service | +| SSL | Secure Socket Layer | +| TCP/IP | Transmission Control Protocol/Internet Protocol | +| TLS | Transport Layer Security | +| TS | Transport Stream | +| TV | Television | +| USB | Universal Serial Bus | + +# 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. +- The keyword "functions" are defined as a collection of functionalities. It is represented by the following symbol in this Recommendation: + +![A rounded rectangular box containing the word 'Functions'.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +A rounded rectangular box with a black border, containing the word "Functions" centered inside it. + +A rounded rectangular box containing the word 'Functions'. + +- The keywords "functional block" are defined as a group of functionalities that has not been further subdivided at the level of detail described in this Recommendation. It is represented by the following symbol in this Recommendation: + +![A rectangular box containing the words 'Functional Block'.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +A rectangular box with a black border, containing the words "Functional" and "Block" stacked vertically and centered inside it. + +A rectangular box containing the words 'Functional Block'. + +NOTE – In the future, other groups or other Recommendations may possibly further subdivide these functional blocks. + +Frame borders of "functions" and "functional block", and relational lines among "functions" and "functional block" are drawn with solid lines or dashed lines. The solid lines mean required + +functionalities or relations. On the other hand, the dashed lines mean optional functionalities or relations. + +# 6 Overview + +## 6.1 Digital signage domains + +Digital signage (DS) is a system that sends information, advertising and other messages to electronic devices (e.g., displays and loudspeakers) in accordance with the time of day and the location of the display, or the actions of audience. Contents and their relevant information, such as display schedules, are delivered over networks. The services are to be closer to people's lives with the advent of broadband and mobile network infrastructures. + +Figure 1 shows the main domains that are involved in the provision of DS services based on [ITU-T Y.1910]. These domains do not define a business model. This decomposition does not preclude that one provider be involved in the support of any given DS services across more than one domain. + +![Figure 1: Generic digital signage domains as per [ITU-T Y.1910]. The diagram shows four domains connected in a linear sequence: Terminal device, Network provider, Service provider, and Content provider. The Terminal device box contains icons of a monitor, a kiosk stand, and a smartphone. The Network provider box contains icons of a router and a server. The Service provider box contains icons of a server and a globe. The Content provider box contains an icon of a globe with a play button. The domains are connected by solid lines, and there are dashed lines between the Terminal device and Network provider, and between the Service provider and Content provider. The text 'H.780(12)_F01' is visible in the bottom right corner of the diagram.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Figure 1: Generic digital signage domains as per [ITU-T Y.1910]. The diagram shows four domains connected in a linear sequence: Terminal device, Network provider, Service provider, and Content provider. The Terminal device box contains icons of a monitor, a kiosk stand, and a smartphone. The Network provider box contains icons of a router and a server. The Service provider box contains icons of a server and a globe. The Content provider box contains an icon of a globe with a play button. The domains are connected by solid lines, and there are dashed lines between the Terminal device and Network provider, and between the Service provider and Content provider. The text 'H.780(12)\_F01' is visible in the bottom right corner of the diagram. + +**Figure 1 – Generic digital signage domains as per [ITU-T Y.1910]** + +The four digital signage domains, the definitions of which are provided in clause 3, are: + +- Content provider +- Service provider +- Network provider +- Terminal device. + +Many of the basic technologies for digital signage are similar to those for IPTV, e.g., image processing and data delivery. There are, however, differences between IPTV and DS. + +A linear TV service, which is one of the typical IPTV services, is premised on broadcasting. On the other hand, DS may be referred to as "digital-out-of-home", "in-store media", "narrowcasting" and "electronic billboards" – reflecting the nature of the DS services. For example, the meaning of narrowcasting is delivery of information to specified audiences as defined by certain values, preferences, or demographic attributes. In analogy with narrowcasting, DS services can offer timely local promotional campaigns through displays aimed at impacting on an audience. In this case, a DS system creates and/or delivers different playlists and contents to individual devices, or to groups of them, according to their detailed geographic attributes. Examples would be device location and region by using audience or location profiles: contents varying depending on the area within a complex; distinction between indoors and outdoors; different contents displayed at the entrance and at the exit of a shopping centre; and differentiation for screens at eye-level and for those above eye-level. In addition to the profile, the delivered contents are played at designated times according to the playlists. As it can be seen, key features of DS are an elaborated, geographic-based content tailoring control, and a detailed scheduling for content delivery and playout (temporal control). + +In addition, particular events may change the contents of DS services along with the geographical and temporal controls. Important examples of this category are alert services for natural disasters and public/building security announcements. + +NOTE 1 – [b-ITU-T TechWatch] provides an outline of DS (e.g., the overview of digital signage relevant technologies and their major applications in the market). + +NOTE 2 – For reference, Appendix of [b-ITU-T E.106] describes the criteria for selection of audience that a national authority may wish to consider for emergency and disaster relief operations (e.g., information on transportation, medical and public utilities). + +From a revenue model viewpoint, there is another difference between IPTV and DS. While IPTV services are mainly provided according to a business-to-consumer subscription-based business model, the DS services are basically offered based on a business-to-business model. + +DS services are categorized into four classes by the number of potential audiences in the services: + +- Class A: services in public spaces (e.g., railways and convention centres) +- Class B: services in major distributors and service industry (e.g., banks and supermarkets) +- Class C: services in relatively small offices and retailer shops; and +- Class D: services in the home as communication tools. + +NOTE 3 – In Classes A and B, services are mainly used for advertisements or information services, and these use cases are relatively clear. On the other hand, a variety of other use cases is expected to emerge in Classes C and D (e.g., effective sales promotion, novelty space production, and communication tools in communities). Common specification of the services in each class, which mainly consist of contents delivery and presentation methods, can be based on the first two classes. + +This Recommendation describes requirements and functionalities of basic DS services (i.e., in the Classes A and B) in order to be used as a foundation for deployment of the services. The functional elements constituting these domains are described in more detail in clause 8. + +## 6.2 Architecture overview + +Figure 2 depicts a general digital signage architecture based on ITU-T IPTV architecture [ITU-T Y.1910]. Major technologies of IPTV services allow a DS system to use methods of contents delivery over a network. + +Figure 2 identifies the principal functional groups for DS services. These functional groups provide a more detailed breakdown of the digital signage domains that are defined in clause 6.1. The content provider and terminal device domains remain the same as in Figure 1. The service provider and network provider domains in Figure 1 are not used in the architecture since commercial and operational boundaries are not appropriate to an architectural decomposition. + +![Figure 2 – Overview of digital signage architecture (based on [ITU-T Y.1910]). The diagram shows five main functional groups: Terminal device functions (pink), Application functions (blue), Content provider functions (grey), Content delivery functions (orange), and Network functions (green). Terminal device functions include Digital signage client, AM client, Security client, and Content delivery client. Application functions include Play log, Config data, Digital signage application, Audience measurement aggregation, Security, Metadata, Content, Report, Delivery schedule, Playlists, and Contents. Content provider functions include Metadata, Content, and Report. Content delivery functions include Content distribution and Content delivery. Network functions include Contents/playlist. Service control functions (yellow) are shown as optional. A legend indicates Required functions (solid line) and Optional functions (dashed line). An arrow points to the Content provider functions with the text 'Out of scope'. The diagram is labeled H.780(12)_F02.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 2 – Overview of digital signage architecture (based on [ITU-T Y.1910]). The diagram shows five main functional groups: Terminal device functions (pink), Application functions (blue), Content provider functions (grey), Content delivery functions (orange), and Network functions (green). Terminal device functions include Digital signage client, AM client, Security client, and Content delivery client. Application functions include Play log, Config data, Digital signage application, Audience measurement aggregation, Security, Metadata, Content, Report, Delivery schedule, Playlists, and Contents. Content provider functions include Metadata, Content, and Report. Content delivery functions include Content distribution and Content delivery. Network functions include Contents/playlist. Service control functions (yellow) are shown as optional. A legend indicates Required functions (solid line) and Optional functions (dashed line). An arrow points to the Content provider functions with the text 'Out of scope'. The diagram is labeled H.780(12)\_F02. + +**Figure 2 – Overview of digital signage architecture (based on [ITU-T Y.1910])** + +### 6.2.1 Functional groups + +The following functional groups in the architecture are derived by grouping-related functions referring to [ITU-T Y.1910]: + +- **Terminal device functions:** Perform mediation between a DS terminal device and a DS service infrastructure. +- **Application functions:** Enable the terminal device functions to select and present a content item. +- **Content delivery functions:** Receive content from the application functions, store, process and deliver it to the terminal device functions using the capabilities of the network functions and the service control functions. +- **Network functions:** Provide IP layer connectivity between the terminal device functions and the other functions. The network functions are shared across all services delivered over IP to the terminal devices. The network functions contribute to the provision of the quality of service (QoS) required by the DS services. +- **Content provider functions:** Are provided by the entity that owns or is licensed to provide contents (i.e., sell, rent or give free usage permission), or content assets (i.e., owner of the content, metadata and usage rights). + +The following is an *optional* functional group in the DS architecture: + +- **Service control functions:** Can request the allocation of system/network/service resources to support DS services. The service control functions can optionally obtain terminal device location information. + +### 6.2.2 Functional blocks + +Many functional blocks for the DS services, except digital signage application functions and digital signage clients, are also derived from [ITU-T Y.1910]. Explanations of each functional block are as follows: + +- **Digital signage application functions:** Manage and/or create content delivery schedules and playlists and playlist schedule (i.e., the functions that control the order and the timing of contents), ingest and distribute contents; +- **Content delivery functions:** Deliver contents to the DS terminal devices. Content delivery depends especially on the schedules in push mode (see clause 8.3); +- **Digital signage client:** Store, decode and display contents. Contents are shown depending on the playlists; +- **Content delivery client functions:** Receive contents over an IP network. + +*Optional* functional blocks relevant to digital signage are as follows: + +- **Content distribution functions:** Send contents to multiple entities of the content delivery functions; +- **Security functions:** Control the protection of the services and content. Content protection includes control of access to contents and the protection of contents using methods such as encryption. Service protection includes authentication and authorization of access to services; +- **Security client functions:** Interact with the security functions to provide service protection and content protection. The client functions verify the usage rights and decrypt content. It is also necessary to consider physical security of the terminal devices under unmanned conditions. +- **Audience measurement aggregation functions:** Aggregate audience measurement information, such as viewership, audience interaction information, and audience related information. They may summarize and report the information to organizational entities in a content provider domain; + +NOTE – Main targets of audience measurement in digital signage are the general public; therefore, identification capabilities for each audience are not always required. For example, there may be a technique that identifies passers-by in order to avoid counting them more than once. + +- **Audience measurement client functions:** Analyse audience information and report to the audience measurement functions (e.g., the number of people in the audience). + +## 6.3 Examples of services + +DS services are deployed in a huge variety of fields. The following list is a summary of DS services: + +- 1) Information services: + - schedule of transportation, map/directory; +- 2) Advertisements/Promotion: + - commercial messages, details of products and services; + - shopping coupons +- 3) Space decoration: + - ornaments/coordination of product samples +- 4) Interactive services: + - user interaction for service navigation such as finding the nearest restaurant; + - information presentations based on audience measurement; + +NOTE – Interactive digital signage service is a type of service provided by a service provider to enable audiences to interact with a content provider. + +- 5) Advanced services: + - Context awareness: Messages are delivered to the terminal devices according to the attributes of an audience (e.g., subscribed specific services, location, date, age, etc.) + +## 6.4 Types of terminal devices + +It is assumed that various types of terminal devices can be used as digital signage terminal devices. Expected types are as follows: + +- 1) Wall screen: wall-mounted/ceiling-mounted/projector. + +NOTE 1 – There is a set of physical displays that are made up as one logical screen. + +- 2) Self-standing screen. + +NOTE 2 – This type of terminal is often with casing for outdoor installation + +- 3) Mobile terminal: + +- Mobile phone/smartphone. +- Portable information terminal. + +- 4) Wall screens and self-standing screens can also be categorized in terms of installation: + +- Separated type: The terminal device is separated from the display screens. +- All-in-one (embedded) type: The display screen includes terminal device functionalities. + +# 7 Requirements + +## 7.1 General requirements + +General requirements for DS architecture are as follows: + +- The DS architecture is required to support a mechanism to configure the DS terminal device and set up a sequence of contents to be displayed. +- The DS architecture is required to support a mechanism to allow the service provider to update the sequence of contents to be displayed. +- The DS architecture is recommended to support a mechanism for the delivery of the same sequence of contents to many DS terminal devices. +- The DS architecture is recommended to support a mechanism for the display of information and contents from different sources (e.g., the architecture receiving detailed exact data such as time tables of transportation schedule and stock exchange information from other systems). +- The DS architecture, when displays are installed in public spaces, is recommended to simultaneously provide emergency alert information in case of disaster (e.g., earthquakes and weather hazards). + +NOTE 1 – See R6.7.2-01, RR6.7.2-04 in [ITU-T Y.1901]. + +- The DS architecture is recommended to support the ability to control audio volume considering the characteristics of the surroundings where DS terminal devices are installed (e.g., in certain areas, regulation may require the audio volume to be less 80 than dB). +- The IPTV architecture is recommended to support the discovery of DS services by terminal devices. + +NOTE 2 – The DS architecture may be used in addition to the ordinary IPTV architecture. If an IPTV service provider wants to apply this Recommendation (i.e., the IPTV service provider + +becomes a DS service provider), then this requirement may become required in addition to the requirements of an ordinary IPTV architecture. [ITU-T H.770] describes general aspects of IPTV service discovery. + +- The DS architecture can optionally provide specific user interfaces (e.g., touch-panels and mobile-phone linking) in order to enable two-way communications with audiences. +- The DS architecture can optionally support QoS network services to avoid latency in case of emergency or specific real-time services (e.g., receiving data through both fixed TCP/IP networks and broadcast communications). + +NOTE 3 – A network in this requirement is assumed to support IP QoS classes specified by [ITU-T Y.1541]. See clause 7.5. + +- The DS architecture can optionally support countermeasure techniques for delivery latency (e.g., buffering, scheduling of sending contents). +- The DS architecture can optionally support audience measurement. + +NOTE 4 – Appendix III introduces general privacy issues of the audience measurement in DS services. + +## 7.2 Content management + +The following requirements of the content management in the DS architecture should be fulfilled: + +- The DS architecture is required to satisfy associated performance requirements when the requirements are specified (e.g., data handling time, total storage size). +- The DS architecture is required to support the ability to create, change and delete the sequences of contents to be presented (e.g., playlist schedules). +- The DS architecture is required to support the ability to register, change and delete content. + +NOTE 1 – See RR6.1.1-04, R6.6.1-01 in [ITU-T Y.1901]. + +- DS metadata, if used in DS services, is required to be able to describe information concerning contents (See clause 9). + +NOTE 2 – See ITU-T Y.1901 R6.6.3.1-03 in [ITU-T Y.1901]. + +- The DS architecture, when content consists of multiple media, can optionally support independent schedule play time for each of the media. + +## 7.3 Content delivery + +The following are requirements regarding contents delivery in the DS services: + +- The DS architecture is required to provide the DS services with the problem-free performance of content delivery in case of large number deployment of terminal devices. + +NOTE 1 – This requirement assumes the condition supporting more than thousands of terminal devices. + +- The DS architecture is required to support at least a pull or a push method of content delivery. + +NOTE 2 – See RR6.6.4.1-04, RR6.6.4.1-08 in [ITU-T Y.1901]. + +- The DS architecture is required to support at least streaming or contents downloading in the case of providing video services. + +NOTE 3 – See RR6.6.4.1-01 in [ITU-T Y.1901]. + +- The DS architecture is required to provide a re-transmission of contents in case of content delivery trouble (e.g., network failure). +- The DS architecture is recommended to support various standardized encapsulation types, including MPEG-2 TS [b-ITU-T H.222.0]. + +- The DS architecture is recommended to support unicast protocol to deliver different sets of contents and playlist schedules to each location setting terminal devices. +- The DS architecture can optionally support multicast protocols for simultaneous data delivery. +- The DS architecture can optionally deliver a set of contents and playlist schedules to individual terminal device or groups of terminal devices. + +## 7.4 Security requirements + +This clause describes security requirements in DS services. + +NOTE 1 – Requirement levels can be stricter depending on the service environments (e.g., characteristics of usage rights of contents and networks and number of terminal devices). + +NOTE 2 – Refer to [ITU-T Y.1901] and [ITU-T X.1191] for security requirement details and security-related issues, respectively. R6.3.2-01, R6.1.4-03, R6.3.1-01, R6.3.5-02, and R6.3.4-02 of [ITU-T Y.1901] are especially relevant to requirements mentioned-below. + +- The DS architecture is recommended to protect against illegal access to the terminal devices and illegal copying and/or alteration of content. +- The DS architecture is recommended to support a means to authenticate the digital signage terminal devices. +- The DS architecture is recommended to support associating contents with content management metadata to permit the expression of its usage rights. + +NOTE 3 – There may be no content rights issues in the services under a certain situation (e.g., rights waiver, self-creation of contents and internal use only). + +- The DS architecture is recommended to support the provision of security means to block illegal or unwanted traffic (e.g., controlling the TCP port access). + +## 7.5 Network requirements + +The requirements as to network aspects in the DS services are as follows: + +- A network for the DS services is required to support IP QoS classes and to satisfy associated performance requirements specified in [ITU-T Y.1541]. + +NOTE 1 – [ITU-T Y.1541] recommended the selection of relevant QoS classes based on application requirements. + +NOTE 2 – See R6.2-02, RR6.2-01 and R6.2-04 in [ITU-T Y.1901]. + +- The DS architecture is recommended to facilitate the ability to detect network failure. + +NOTE 3 – See R6.1.4-03 in [ITU-T Y.1901]. + +- The DS architecture can optionally support a combination of fixed and wireless networks. + +## 7.6 Terminal device requirements + +### 7.6.1 Terminal functions + +The requirements regarding storing/playback of content, physical resistance of the DS terminal devices (e.g., against dust, temperature and humidity) are as follows: + +- The DS terminal device is required to facilitate standardized interfaces between the terminal devices and displays when the terminal devices and displays are physically separated. +- The DS terminal device is required to support the decoding of at least one audio or video format. +- The DS terminal device is recommended to support input interfaces to load contents. + +- The DS terminal device, when content is stored in the device before being played, is required to provide high-reliability storage (e.g., 99.999% availability). +- The DS architecture can optionally select any type of DS terminal device (e.g., dedicated terminal device, personal computer, personal digital assistant, and terminal-embedded-display), depending on the characteristics of the service. + +### 7.6.2 Display functions + +The following are requirements on displays for the DS architecture: + +- Displays in DS services are required to support environment-compatible specifications for their installation and operation (e.g., power-consumption, heat-release, structure strength and maintenance-ability). +- Outdoor displays for DS services are required to support brightness control in order to keep visibility under their environment. +- Outdoor displays for DS services are required to support specifications against their particular operational conditions (e.g., withstand shock and vibration; dust-proof, water-proof; and appropriate range of temperature and moisture). +- The DS architecture is recommended to provide an ability to support a wide variety of displays fitting with its service, including: display type (liquid crystal display, plasma display panel, organic light emitting diode display), size, casing and standing/wall-hanging multi-screens. + +### 7.6.3 Management functions + +Management functionalities in the DS architecture and terminals are as follows: + +- The DS architecture is recommended to support the terminal device operation without any user action, except for switching on the terminal device. +- The DS architecture is recommended to facilitate a mean to confirm the results of content delivery. + +NOTE 1 – See R6.1.4-03 in [ITU-T Y.1901]. + +- The DS terminal device is recommended to support log functions (e.g., creation, storing, reporting play logs). + +NOTE 2 – See RR6.1.4-01, RR6.5.2.7-02 in [ITU-T Y.1901]. + +- The DS architecture is recommended to support the monitoring of the status of the terminal devices by a management server through a network. + +- The DS terminal device is recommended to support a self-diagnostic function. + +NOTE 3 – See RR6.5.2-18 in [ITU-T Y.1901]. + +- The DS architecture is recommended to support terminal management in case there is a change in the number of terminals devices, or a terminal device is replaced. + +NOTE 4 – A certain type of the terminal devices in a specific DS service may automatically acquire the contents like a TV accesses to terrestrial broadcast services. In the case, terminal management can be optionally supported. + +### 7.6.4 Accessibility requirements + +This item is for further study. + +NOTE – For reference, see [b-ITU-T F.790]. + +# 8 Functional architecture and key features + +This clause illustrates details of functionalities in clause 6. The key functionalities of DS applications (i.e., server-side functionalities) are described in clause 8.1, and terminal device functions (i.e., client-side functionalities) are described in clause 8.2. + +## 8.1 Functionalities of digital signage applications + +This diagram shows details of the server-side digital signage applications in Figure 2. The following sub-clauses describe the functional blocks contained in DS applications. + +![Figure 3: Details of the server-side digital signage applications. The diagram shows a 'Digital signage application' box containing several functional blocks. 'Configuration' is a required block receiving 'Parameters'. 'Play logging and reporting' is a required block receiving 'Play log' and sending a 'Report'. 'System management' is an optional block receiving 'Status from control to each functional block'. 'Schedule and delivery management' is a required block sending a 'Delivery-schedule'. 'Content management' is a required block sending 'Metadata' and 'Contents Playlist'. A legend at the bottom indicates that solid boxes are 'Required functional block' and dashed boxes are 'Optional functional block'. The code H.780(12)_F03 is shown in the bottom right.](10781f43062bf3e9601a1e086710556c_img.jpg) + +The diagram illustrates the functional architecture of server-side digital signage applications. A large box labeled 'Digital signage application' contains several functional blocks. On the left, 'Configuration' (a required block) receives 'Parameters'. Below it, 'Play logging and reporting' (a required block) receives 'Play log' and sends a 'Report'. To the right, 'System management' (an optional block) receives 'Status from control to each functional block'. Below 'System management' is 'Content management' (a required block), which sends 'Metadata' and 'Contents Playlist'. To the left of 'Content management' is 'Schedule and delivery management' (a required block), which sends a 'Delivery-schedule'. A legend at the bottom shows a solid box for 'Required functional block' and a dashed box for 'Optional functional block'. The code H.780(12)\_F03 is in the bottom right. + +Figure 3: Details of the server-side digital signage applications. The diagram shows a 'Digital signage application' box containing several functional blocks. 'Configuration' is a required block receiving 'Parameters'. 'Play logging and reporting' is a required block receiving 'Play log' and sending a 'Report'. 'System management' is an optional block receiving 'Status from control to each functional block'. 'Schedule and delivery management' is a required block sending a 'Delivery-schedule'. 'Content management' is a required block sending 'Metadata' and 'Contents Playlist'. A legend at the bottom indicates that solid boxes are 'Required functional block' and dashed boxes are 'Optional functional block'. The code H.780(12)\_F03 is shown in the bottom right. + +Figure 3 – Details of the server-side digital signage applications + +### 8.1.1 Configuration + +The installation location of DS terminal devices is usually far from the DS applications, and the number of terminal devices may be large; therefore, functionalities for remote configuration and/or status monitoring of the terminal devices are key components for DS services. + +The ability of changing system parameters provides the DS system with a way to adapt to a wide variety of service environments (e.g., number of terminal devices, network conditions, and operational restrictions). Typical parameters are terminal devices' properties (e.g., hardware settings or terminal devices identifiers) and transmission-related parameters (e.g., port numbers, available network bandwidth). + +In the case of addition of terminal devices to the system, it is expected that the system provide simple operations for registering terminal devices, without need to reboot or shutdown servers. + +### 8.1.2 System management + +This functional block monitors and records remotely the operating status of other functional blocks (e.g., delivery servers, networks, terminal devices and connected displays), which is necessary for high system availability and operational efficiency. + +The terminal devices and network equipment may be capable of monitoring and reporting IP performance parameters. These parameters are used for administration of the network status. + +NOTE – These parameters can be used to estimate the perceived quality of video and audio by checking the status of QoS/QoE. Details of QoE issues are discussed in [ITU-T G.1080] and [ITU-T G.1081]. + +It is preferable to have the ability of checking afterward both the communication results among functionalities and the status of each individual terminal device. + +When server, terminal device and network malfunction is detected, the functionality should alert system administrators. + +### **8.1.3 Play log aggregation and reporting** + +Play logs are used to verify whether designated contents are presented at proper times according to playlists. Therefore, a play log aggregation function should be provided. The logs can also be treated as performance reporting to other business entities (e.g., an advertiser). + +### **8.1.4 Content management** + +This functional block manages content life-cycle in compliance with commercial agreements with the content owner. Examples of content management functionalities are: data registration and import of multimedia contents, export of contents to the content delivery functions, data processing ability and searching/reviewing contents. + +### **8.1.5 Schedule and delivery management** + +This functional block manages schedules for content export to the delivery function and schedules for content delivery to the terminal devices. In particular, timings of content delivery in push-mode to the DS terminal devices are handled in this functionality. There are various combinations of delivery timings and play timings (e.g., differential content delivery and immediate or scheduled presentation after delivery). + +It is also important to support mechanisms regarding aggregation and management of logs of the individual terminal devices. This allows checking whether designated contents are delivered to the intended terminal devices according to the delivery schedules or not. + +Almost all DS service content presentations orders are designated with playlist schedules and playlists. Therefore, functionalities for inputting and creating schedules and lists may be provided as operation through server consoles, as they impact on total system operation efficiency. + +Playlists, playlist schedules and delivery schedules managed by this functionality may differ from time to time, depending on each terminal device. + +In addition, this functionality may have: + +- a group delivery function that simultaneously delivers contents to multiple terminal devices, according to terminal device installation location information; and +- an interrupted presentation function that terminates the current presentation and indicates presentation of high-priority contents (e.g., emergency notifications of accident). There are also various types of interruption modes (e.g., interruption of a set of contents and appointment of detailed interruption timing). + +### **8.1.6 Summary of system logs** + +The DS architecture has administration and management functions that use several types of log data, as described before. Data is recorded on equipment (e.g., delivery servers and terminal devices), gathered and analysed by the management functionalities. Data can be classified from the viewpoint of its purpose as follows: + +- System administration and troubleshooting: + - Status of servers and terminal devices. + - Status of a network. + - Results of contents delivery recorded within the delivery functionalities. +- Evidence of service: + - Results of playing contents. + +**8.2 Functionalities of terminal devices** +**8.2.1 Digital signage clients** + +Figure 2 details a DS client in terminal devices. Digital signage client functions correspond to the integration of "application client functions" and the "media client function" of the IPTV functional architecture in [ITU-T H.720] and [ITU-T H.721]. The relationship between DS and IPTV clients are shown in Table 1. + +The following clauses describe the functional blocks contained in DS clients. + +![Figure 4 – Details of digital signage client](ebce355620876e10f907f8b71926c112_img.jpg) + +A block diagram showing the 'Digital signage client' containing four functional blocks: 'Play control', 'Media processing', 'Storage' (all required, solid lines), and 'Service discovery' (optional, dashed lines). + - 'Play control' sends 'Play order' to 'Media processing' and receives 'Playlists' and 'Playlist schedule' from 'Storage'. It outputs a 'Play log'. + - 'Media processing' receives 'Contents' and 'Contents information' from 'Storage' and outputs a 'Multimedia presentation'. + - 'Storage' receives 'Contents' and 'Metadata' from an external source. + - A legend indicates solid boxes are 'Required functional block' and dashed boxes are 'Optional functional block'. + +**Figure 4 – Details of digital signage client** + +Figure 4 – Details of digital signage client + +**Table 1 – Relations of functional blocks among ITU-T Recommendations** + +| Digital signage clients functional blocks | IPTV clients functional blocks
    (function name: functional block name)     | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Play control | Application client functions: IPTV application client | +| Media processing |
    • – Media client functions: Codecs
    • – Media client functions: Media control
    • – Media client functions: Metadata management
    • – Application client functions: IPTV application client
    | +| Service discovery | Application client functions: Service and application discovery and selection (SADS) client | +| Storage | Media client functions: Storage | + +**8.2.1.1 Play control** + +The play control functional block controls the play order of multimedia contents, including video, audio and data according to playlist schedules and playlists. Results of play control processes as play logs are sent to the play log aggregation and reporting function (clause 8.1.3). + +**8.2.1.2 Media processing** + +This functional block is a software or hardware process that includes contents decoding to generate a multimedia presentation combining visual and/or audio contents. The process may also include creation of a layout for the visual contents. The results of processing as multimedia presentations are signalled to displays or other electronic signage devices. + +Rec. ITU-T H.780 (06/2012)     15 + +#### 8.2.1.3 Video and audio processing + +The DS client is expected to support standardized video and/or audio formats. + +NOTE – For reference, see Appendix II "Codecs and data formats for digital signage services". + +#### 8.2.1.4 Processing of other data formats + +The DS client is expected to support standardized multimedia formats for data such as text and graphics. + +#### 8.2.1.5 Storage + +The storage functional block is responsible for the caching (e.g., temporary storage in volatile memory such as random access memory) and storage (e.g., persistent storage in non-volatile memory) of contents and other application data. The storage function can be internally or externally implemented. Contents and metadata are stored through the content delivery client functions described in clause 8.2.2, or are input from storage interfaces (see clause 10.1). + +#### 8.2.1.6 Service discovery + +Service discovery is an important function when terminal devices can dynamically change a connection to a content delivery server. Details of service discovery in DS are for further study. + +### 8.2.2 Content delivery client functions + +The content delivery client functions receive contents from the content delivery functions, and can request control of the content delivery by co-operating with the delivery functions. + +## 8.3 Transport and control mechanisms + +There are several classifications of the characteristics of content delivery functionalities. This Recommendation pays attention to the initiation of control of content delivery, content delivery timings and delivery protocols in series. + +### 8.3.1 Mode of content delivery + +There are two modes for requesting content delivery: + +- **Push mode:** Content delivery servers deliver contents, playlists and playlist schedules to DS terminal devices according to the server's orders. +- **Pull mode:** DS terminal devices request content delivery when the terminal devices allow to request. The contents would be downloaded if contents to be shown or updated are in a delivery server. + +NOTE – In case of updating content, the two modes can be combined (e.g., different content updates are delivered in pull mode, while emergency information is delivered in push mode) + +### 8.3.2 Content delivery timing + +Content delivery methods can be classified according to delivery timing. Video contents are relatively larger than other types of contents; therefore, efficient delivery methods are to be selected based on the details of the DS services. + +- **Real-time delivery (streaming):** Video streaming servers deliver contents to DS terminal devices. The terminal devices continuously receive and decode the contents, and transform them into video signals in real-time. + +NOTE – This includes options as such dynamic adaptive streaming in HTTP (DASH) [b-ISO/IEC 23009-1], live streaming, and static streaming. + +- **Pre-stored:** The contents sent from a delivery server are stored in the terminal device in advance of playing. The terminal devices continuously read from the storage and decode + +the contents. This delivery method can be advantageous for stable presentation services since it is independent of network bandwidth and quality. + +- **Event-driven:** High-priority contents can replace or be overlaid on the current presentation, e.g., to notify the audience of significant events. Notification-specific contents such as simple text and/or images can be delivered in this mode. + +### 8.3.3 Content delivery methods over IP networks: + +- **Unicast:** Protocols in this category allow direct one-to-one sessions among a delivery server and terminal devices. HTTP, HTTPS and FTP are well-known protocols for IP unicast delivery. +- **Multicast:** Protocols in this category allow contents to be simultaneously sent to multiple terminal devices. A merit of multicast delivery is the efficient use of network bandwidth when compared to unicast. RTP and FLUTE are well-known protocols for IP multicast delivery. + +NOTE – Content delivery methods are used independently from content delivery timing. + +## 8.4 Security + +There are many security concerns and requirements that need to be addressed and supported by a DS system. Details of security mechanisms in DS are for further study. + +## 8.5 Audience measurement + +Handling viewership information is a value-added feature for DS services. + +There are however many security concerns and requirements need to be addressed and supported by a DS system. Details of audience measurement for DS services are for further study. + +# 9 Metadata + +Metadata can present details of contents and service information in DS. [ITU-T H.750] summarizes metadata specifications for IPTV services defined by various standards development organizations, and those specifications are applicable to DS services. In particular, MPEG-7 of [ISO/IEC 15938-5] and [ISO/IEC 15938-5 Amd.2], and TV Anytime of [ETSI TS 102 822-3-1] and [ETSI TS 102 822-3-3] introduce generic and exhaustive specifications concerning audio and visual services. + +This Recommendation selects basic elements/attributes from these specifications that are applicable to DS services. Names of elements/attributes are quoted as they are in the specifications, in order to keep clear the relationship between the standards. + +NOTE – Just semantics of metadata are illustrated in this clause. Details of metadata specifications, such as schema, are for further study. + +In the tables provided in the sub-clauses below, requirement levels are indicated as mandatory (M) or optional (O), if the metadata is used in the services. + +## 9.1 Content information + +Metadata can treat detailed content information such as title and genre. Many elements/attributes for content handling can be selected from [ISO/IEC 15938-5], [ISO/IEC 15938-5 Amd.2] and [ETSI TS 102 822-3-1]. A set of elements/attributes for DS services are shown in Table 2. + +**Table 2 – Common content elements/attributes** + +| Element / Attribute | Description | Level | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| ContentId | An identifier of content. | M | +| Title | Titles, e.g., in different languages. (Defined as an MPEG-7 datatype, TitleType. See clause 9.2.2 in [ISO/IEC 15938-5] for a detailed specification). | M | +| Synopsis | A simple textual description of the content. | O | +| Explanation | A detailed textual description of the content. | O | +| Keyword | A list of keywords for the programme. A keyword can be a single word or an entire phrase made up of multiple words. | O | +| Genre | A genre for the programme (The thesaurus in annex B in [ETSI TS 102 822-3-1] defines the normative TV-Anytime set of genres). | O | +| PreferenceCondition | A combination of time, place and/or specific parts of contents that can be associated with a particular set for usage restriction. | O | +| Language | Describes one spoken language for the programme. There may be more than one spoken language specified for the content. | O | +| RelatedMaterial | A reference to any other material related to the content. | O | +| ProductionDate | The date or time period when the content was produced (defined as a tva:TVATimeType). | O | +| Release | Information about the region and date of release of the content. | O | +| Duration | Indicates the approximate duration of the programme. | O | +| Availability | This provides information about when the content is scheduled to start or end. | O | +| ContentType | This provides type of media of contents (e.g., video, still image). | O | +| FileSize | Indicates the size, in bytes, of the file where the programme instance is stored. | O | +| PromotionalInformation | Information on the products/service in the content when the content is presented as promotion, advertisement. | O | +| CreationInformation | Information concerning the content creation (e.g., title, creator, classification). | O | + +## 9.2 Terminal device information + +Information regarding terminal devices is necessary for system maintenance/administration. [ETSI TS 102 822-3-3], [ISO/IEC 15938-5] and [ISO/IEC 15938-5 Amd.2] introduce generic specifications concerning terminal device information. The metadata in Table 3 is the basis for DS services. "TerminalId", "AmbientIdRef" and "InstallationDate" are defined in this Recommendation. + +**Table 3 – Common terminal device elements/attributes** + +| Element/Attribute | Description | Level | +|--------------------|---------------------------------------------------------------------------------------------------------------------------|-------| +| TerminalId | An identifier of a terminal device. | M | +| AmbientIdRef | A reference identifier of ambient information (see Table 4). | O | +| Keyword | A list of keywords for the terminal device. A keyword can be a single word or an entire phrase made up of multiple words. | O | +| DisplayInformation | Information of display connected to a terminal device. | O | +| InstallationDate | Describes date of installation of the terminal device. | O | + +## 9.3 Ambient information + +Information regarding terminal device locations is used for controlling of the delivery of DS services. [ETSI TS 102 822-3-3] introduces generic specifications concerning location and preference information. "AmbientId" is defined in this Recommendation. + +NOTE – A mobility aspect of DS services can be also treated by using this information (e.g., the DS services in public transportations). + +**Table 4 – Common ambient information elements/attributes** + +| Element/Attribute | Description | Level | +|---------------------|------------------------------------------------------------------------------------------------------------------------------|-------| +| AmbientId | An identifier of a ambient information. | M | +| AmbientDescription | Describes the spatial information such as name and/or characteristics of locations in which terminal devices have installed. | O | +| Keyword | A list of keywords for the location. A keyword can be a single word or an entire phrase made up of multiple words. | O | +| AgeGroup | Describes the age of the major audience in terms of range. | O | +| GenderGroup | Describes the gender of the major audience. | O | +| PreferenceCondition | A combination of time and/or specific parts of contents that can be associated with a particular set for usage restriction. | O | + +## 9.4 Results of playing contents + +Table 5 contains the minimum set of information that can be used for recording and collecting the results of playing contents in DS services. TerminalIdRef, PlayDateTime and ContentIdRef are defined in this Recommendation. + +**Table 5 – Common elements/attributes regarding play-logs** + +| Element/Attribute | Description | Level | +|-------------------|---------------------------------------------------------------------------------|-------| +| TerminalIdRef | An identifier of a terminal device. | M | +| PlayDateTime | Describes the date and time of showing the contents. | M | +| ContentIdRef | Describes identifiers of the contents which are presented on a terminal device. | M | + +## 9.5 Schedule-relevant information + +Metadata to represent time relevant information (e.g., playlist, play-schedule,) is for further study. + +# **10 Terminal device interfaces** + +DS terminal devices are equipped with various standardized input/output interfaces. Details of specifications of the input interfaces are for further study. + +NOTE – Appendix IV describe possible interface standards for DS. + +## **10.1 Input interfaces** + +DS terminal devices have input interfaces for receiving digital data, terminal control and network access. + +### **10.1.1 Network interfaces** + +DS terminal devices are required to support a wired network interface and/or a wireless network interface. + +## **10.2 Output interfaces** + +DS terminal devices are required to support at least one of type of video or audio output interface. Video interfaces are supported if displays are separated from the terminal device. Terminal devices may support multiple video output interfaces. Specification details for output interfaces are for further study. + +NOTE – For reference, [ITU-T H.721] has specifications for IPTV output interfaces. + +# Appendix I + +## Digital signage use cases + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Screen for single content source + +After initialization, a sequence of contents is displayed on the screen of a terminal device without any user interaction. + +#### Use case 1A: DS within an organization + +The use case illustrated in Figure I.1 delivers contents, which is mainly used to inform events and status relates to organization activities, to a relatively small number of terminal devices. A system in this type, which consists of functions of content creation, digital signage application and delivery mechanism, may be owned and operated by a single organization. + +![Sequence diagram illustrating the flow for DS within an organization (Use case 1A).](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +The diagram is a sequence diagram with four lifelines: Content provider functions, Digital signage application functions, Content delivery functions, and Terminal device functions. The sequence of interactions is as follows: + +1. Content and playlist provisioning: A self-call on the Content provider functions lifeline. +2. Content and playlist: A message from Content provider functions to Digital signage application functions. +3. Schedule management: A self-call on the Digital signage application functions lifeline. +4. Contents and playlist and delivery schedule: A message from Digital signage application functions to Content delivery functions. +5. Content and playlist: A message from Content delivery functions to Terminal device functions. +6. Service consumption: A self-call on the Terminal device functions lifeline. +7. Log: A message from Terminal device functions back to Digital signage application functions. + +H.780(12)\_FI.1 + +Sequence diagram illustrating the flow for DS within an organization (Use case 1A). + +Figure I.1 – Use case 1A: Flow for DS within an organization + +The following processes are assumed in this use case: + +- 1) Content creation: digital signage contents, their relevant metadata and playlists are created. +- 2) Content setting: the contents and relevant data are sent to a digital signage application. +- 3) Schedule management: the digital signage application manages the contents and their delivery schedules. +- 4) Content and schedule setting: a content delivery system receives the contents and their delivery schedules. +- 5) Content delivery: the contents are delivered to digital signage terminal devices on the schedules. +- 6) Service consumption: Contents are shown on the display of the terminal devices based on the playlist. +NOTE – Interactions among the audience, the terminals and other functions are omitted when interactive terminals are provided. +- 7) Log aggregation: service logs are gathered in the digital signage application. + +### I.2 Screen by using multiple content/data sources + +There may be the case that multiple content providers (e.g., an independent information service provider, an advertiser, etc.) and data sources provide several contents or data to display on terminal devices. + +#### Use case 2A: Linking different businesses + +The use case illustrated in Figure I.2 shows a digital signage system that works with independent business sources including business relevant systems, and delivers signage contents that relate to the business sources' activities (e.g., a display shows a waiting list in a reservation desk; and sales promotion contents are altered according to requests from each tenant in a shopping mall). + +NOTE 1 – A business system is different from a well-known term "business support system (BSS)". The role of a BSS is usually specific to telecommunication businesses such as the management of subscribers. + +![Sequence diagram illustrating the flow for linking different businesses in a digital signage system. The diagram shows interactions between five entities: Business functions, Content provider functions, Digital signage application functions, Content delivery functions, and Terminal device functions. The sequence of steps is: 1. Content and playlist provisioning (Business to Content provider), 2. Content and playlist (Content provider to Digital signage application), 3. Schedule and location management (Digital signage application internal loop), 4. Business data (Business to Digital signage application), 5. Processing (Digital signage application internal loop), 6. Contents and playlist and delivery schedule and location (Digital signage application to Content delivery), 7. Content and playlist (Content delivery to Terminal device), 8. Service consumption (Terminal device internal loop), 9. Log (Terminal device to Digital signage application), 10. Report (Digital signage application to Business).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant Business as Business functions + participant ContentProvider as Content provider functions + participant DSApp as Digital signage application functions + participant Delivery as Content delivery functions + participant Terminal as Terminal device functions + + Note left of Business: Business operation + Business->>ContentProvider: 1. Content and playlist provisioning + ContentProvider->>DSApp: 2. Content and playlist + DSApp->>DSApp: 3. Schedule and location management + Business->>DSApp: 4. Business data + DSApp->>DSApp: 5. Processing + DSApp->>Delivery: 6. Contents and playlist and delivery schedule and location + Delivery->>Terminal: 7. Content and playlist + Terminal->>Terminal: 8. Service consumption + Terminal->>DSApp: 9. Log + DSApp->>Business: 10. Report + +``` + +H.780(12)\_FI.2 + +Sequence diagram illustrating the flow for linking different businesses in a digital signage system. The diagram shows interactions between five entities: Business functions, Content provider functions, Digital signage application functions, Content delivery functions, and Terminal device functions. The sequence of steps is: 1. Content and playlist provisioning (Business to Content provider), 2. Content and playlist (Content provider to Digital signage application), 3. Schedule and location management (Digital signage application internal loop), 4. Business data (Business to Digital signage application), 5. Processing (Digital signage application internal loop), 6. Contents and playlist and delivery schedule and location (Digital signage application to Content delivery), 7. Content and playlist (Content delivery to Terminal device), 8. Service consumption (Terminal device internal loop), 9. Log (Terminal device to Digital signage application), 10. Report (Digital signage application to Business). + +**Figure I.2 – Use case 2A: Flow for linking different businesses** + +NOTE 2 – Playlists may be created by the DS application rather than being provided by the content provider. + +The following processes are assumed in business-linking use case: + +- 1) Content creation: digital signage contents, their relevant metadata and playlists are created. One of the contents is a template which has some blanked areas filled in the later process 5). + - 2) Content setting: the contents and relevant data are sent to a digital signage application. + - 3) Schedule and location management: the digital signage application manages the contents and their delivery schedules. The application also manages location data of terminal devices if there are lots of delivery points. + - 4) Business data sending: business-related data to be shown on the terminal devices are provided by business systems. + - 5) Content processing: the business data is embedded into blanked areas in the contents. + - 6) Content and schedule setting: a content delivery system receives the contents, their delivery location and schedules. + - 7) Content delivery: the contents are delivered to the digital signage terminal devices on the schedules. + - 8) Service consumption: Contents are shown on the display of the terminal devices based on the playlist. +- NOTE 3 – This use case omits details of interactions amongst the audience, the terminals and other functions when an interactive digital signage service is provided. +- 9) Log aggregation: service logs are gathered in the digital signage application. + +- 10) Report sending: the application summarizes the logs as a report, and making and sending the report to the business systems. + +#### Use case 2B: Advertisement services + +Traditional advertising consists of broadcasting commercial advertising or public promotion of goods, services, company images and institutional messages. Every digital signage terminal device located in a certain region can receive such advertisements. Each advertising service can be provided on a national basis, or regionally/locally [b-ITU-T Y.Sup5]. This use case is illustrated in Figure I.3. + +Location of the digital signage terminals is one of the key factors for advertisement. Effectiveness of advertisement heavily depends on the number of viewers and location for setting up the terminal devices. Hence, an advertiser finds appropriate locations and makes a contract with owners of locations (e.g., a railway station managing company) to get permission to set up the terminals. + +Location information provided by the location owners may contain a variety of attributes (e.g., physical address, type of location, demographic information of audience, etc.). + +NOTE 4 – Details of advertisement in DS are for future study. + +![Sequence diagram titled 'Figure I.3 – Use case 2B: Flow for advertisement services'. It shows interactions between five lifelines: Content provider functions, Location ownership functions, Digital signage application functions, Content delivery functions, and Terminal device functions. The sequence of messages is: 1. Content and playlist provisioning (self-call on Content provider), 2. Location information (Location ownership to Digital signage), 3. Content and playlist (Content provider to Digital signage), 4. Preview (self-call on Digital signage), 5. Schedule and location management (self-call on Digital signage), 6. Contents and playlist and delivery schedule (Digital signage to Content delivery), 7. Content and playlist (Content delivery to Terminal device), 8. Service consumption (self-call on Terminal device), 9. Log (Terminal device to Digital signage), 10. Report (Digital signage to Content provider and Location ownership). A label 'H.780(12)_FI.3' is at the bottom right.](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +Sequence diagram titled 'Figure I.3 – Use case 2B: Flow for advertisement services'. It shows interactions between five lifelines: Content provider functions, Location ownership functions, Digital signage application functions, Content delivery functions, and Terminal device functions. The sequence of messages is: 1. Content and playlist provisioning (self-call on Content provider), 2. Location information (Location ownership to Digital signage), 3. Content and playlist (Content provider to Digital signage), 4. Preview (self-call on Digital signage), 5. Schedule and location management (self-call on Digital signage), 6. Contents and playlist and delivery schedule (Digital signage to Content delivery), 7. Content and playlist (Content delivery to Terminal device), 8. Service consumption (self-call on Terminal device), 9. Log (Terminal device to Digital signage), 10. Report (Digital signage to Content provider and Location ownership). A label 'H.780(12)\_FI.3' is at the bottom right. + +**Figure I.3 – Use case 2B: Flow for advertisement services** + +The following processes are assumed in the advertisement use case: + +- 1) Content creation: Advertisement contents, their relevant metadata and playlists are created by an advertiser as the content provider functions. +- 2) Location information aggregation: Information concerning candidate locations of advertisements are aggregated from location owners as location ownership functions in advance. +- 3) Content setting: The contents and relevant data are sent to a digital signage application. +- 4) Content preview: Usually advertisement contents are reviewed before delivering as a business manner. +- 5) Schedule and location management: The digital signage application manages the contents and their delivery schedules. The application searches and finds suitable locations to advertise the contents. + +- 6) Content and schedule setting: A content delivery system receives the contents, their deliver location and schedules. + - 7) Content delivery: The contents are delivered to digital signage terminal devices on the schedules. + - 8) Service consumption: Contents are shown on the display of the terminal devices based on the playlist. +- NOTE 5 – This use case omits details of interactions among the audience, the terminals and other functions when an interactive digital signage service is provided. +- 9) Log aggregation: Service logs are gathered in the digital signage application. + - 10) Report sending: The application summarizes the logs as a report, and making and sending the report to the location owners and the advertiser according to contracts between business entities. + +### I.3 Emergency communications + +Public announcement services for disaster relief and early warning in case of major disasters are of paramount importance. Digital signage services can provide a way to deliver such information (e.g., display particular local/regional information to displaced people at different evacuation places, etc.). It is important to consider aspects of widely-adopted and instantaneous information services. + +Such services need to collect accurate information on disaster from reliable sources and to ensure its timely delivery. Figure I.4 shows an example of digital signage service operation in case of disaster. + +![Figure I.4 – Use case 3: Disaster information service. A diagram showing information flow from various sources to a central digital signage platform, which then distributes it to different locations and terminals.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +The diagram illustrates the flow of information for a disaster information service. At the top, **Reliable information sources** include: + +- Public transport** (Railways, Bus, Boats) providing **Traffic report** (Traffic jam, Safety routes). +- Broadcaster** (satellite and tower) providing **News** and **Disaster information**. +- Internet (portal, posting)** providing **Safety confirmation** and **Disaster situation**. + +These sources feed into a central **Digital signage platform for communication under disaster** (represented by three server icons in a cloud). From this platform, information is distributed to various locations and terminals: + +- Metropolitan area**: Includes **Station public building** (with a digital signage screen), **Commercial facilities**, and **Designated shelter** (both with digital signage screens and silhouettes of people). +- Affected area**: Includes **Temporary housing** (with a **Mobile** phone and **Digital signage** screen), and **Evacuation center** (with a digital signage screen and silhouettes of people). + +Information labels for the affected area include **Local news** and **Regional information**. The diagram is labeled H.780(12)\_FI.4. + +Figure I.4 – Use case 3: Disaster information service. A diagram showing information flow from various sources to a central digital signage platform, which then distributes it to different locations and terminals. + +Figure I.4 – Use case 3: Disaster information service + +## I.4 Interaction amongst audience and terminals + +### Use case 4A: Service interactivity between mobile and digital signage + +Mobile interactivity allows network operators to deliver promotional material to users' mobile phones when they send their text message to the screen. + +One of the most basic mobile interactivities is to send text to a digital signage screen and text to vote. These applications allow viewers to send a text message or vote on a poll or question from their mobile phone to a digital signage screen. In this application, viewers send text messages with their opinion or vote for a number listed on the screen. Once the viewers' text messages are received, they are displayed on the digital signage screen. + +## I.5 High-level architecture expansion + +An expanded architecture can contain the following new functional blocks according to the use cases mentioned-above: 1A, 2A and 2B. + +- A "Business functions" block provides business data shown on the digital signage terminal devices. +- A "Location ownership functions" block provides location information for placing the terminals. +- A "Location Profile" block in service control functions group stores location information for setting up the terminals. + +NOTE – Details of business functions and location ownership functions are out of the scope of this Recommendation. + +![Figure I.5 – Expanded generic DS architecture diagram showing functional blocks and their interactions.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +The diagram illustrates the expanded generic DS architecture, organized into several functional blocks and their interactions: + +- Terminal device functions (Pink block):** Contains **Digital signage client** (Required), **AM client** (Optional), **Security client** (Optional), and **Content delivery client** (Required). +- Application functions (Blue block):** Contains **Digital signage application** (Required), **Play log** (Optional), **Audience measurement aggregation** (Optional), **Security** (Optional), **Metadata Content Play reports** (Optional), **Business Data** (Optional), and **Delivery schedule Contents Playlists** (Optional). +- Service control functions (Yellow block):** Contains **Location profile** (Optional). +- Content delivery functions (Orange block):** Contains **Content distribution** (Optional) and **Content delivery** (Required). +- Network functions (Green block):** Contains **Content delivery** (Required). +- External/Out of scope functions:** + - Content provider functions** and **Other business functions** (Grey blocks) are connected to the **Business Data** in the Application functions block. + - Location ownership functions** (Grey block) is connected to the **Location profile** in the Service control functions block and is marked as **Out of scope**. + +**Interactions:** + +- The **Digital signage client** connects to the **Digital signage application**. +- The **AM client** connects to the **Audience measurement aggregation**. +- The **Security client** connects to the **Security** block. +- The **Content delivery client** connects to the **Content delivery** block in the Network functions. +- The **Digital signage application** connects to the **Play log**, **Audience measurement aggregation**, **Security**, **Metadata Content Play reports**, **Business Data**, and **Delivery schedule Contents Playlists**. +- The **Location profile** in Service control functions connects to the **Content delivery** block in the Network functions. +- The **Content distribution** in Content delivery functions connects to the **Content delivery** block in the Network functions. + +**Legend:** + +- Required functional block:** Solid line border. +- Optional functional block:** Dashed line border. + +H.780(12)\_FI.5 + +Figure I.5 – Expanded generic DS architecture diagram showing functional blocks and their interactions. + +Figure I.5 – Expanded generic DS architecture + +# Appendix II + +## Codecs and data formats for digital signage services + +(This appendix does not form an integral part of this Recommendation.) + +Codecs and data formats of presentation media in digital signage services are described by several organizations (e.g., [b-POPAI]). The specifications listed in Table II.1 are provided for reference when considering media coding for use in digital signage services. It should be noted that the codecs and data formats for digital signage services are not limited to the ones listed in Table II.1. + +Wrapper is a container of one or more encoded media files. The specifications listed in Table II.2, which may be used for digital broadcasting, typically contain multiple video and audio streams. + +**Table II.1 – Standards of codecs and data formats** + +| Type | Standards | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Audio | MPEG-1 Audio Layer-3 [b-ISO/IEC 11172-3], Dolby AC3 [b-ETSI TS 102 366], MPEG-2 AAC [b-ISO/IEC 13818-7], MPEG-4 HE AAC v1 [b-ISO/IEC 14496-3], A-law/ $\mu$ -law [b-ITU-T G.711] | +| Still image | JPG [b-ITU-T T.81], PNG [b-ISO/IEC 15948] | +| Vector graphics (Note) | SVG [b-W3C SVG 1.1] | +| Video | MPEG-2 [b-ITU-T H.262], H.264 [b-ITU-T H.264] | + +NOTE – Vector graphics are a means to represent images in computer graphics based on mathematical equations (e.g., points, lines, curves, and shapes or polygons). + +**Table II.2 – Standards of data wrapping** + +| Type | Standards | +|---------|-----------------------------------------------------------------------------| +| Wrapper | MPEG-4 part 14 (MP4) [b-ISO/IEC 14496-14]
    MPEG-2 TS/PS [b-ITU-T H.222.0] | + +# Appendix III + +## Privacy of digital signage services + +(This appendix does not form an integral part of this Recommendation.) + +## III.1 Overview + +Digital signage services can enhance their interactivity by using audience measurement technologies (e.g., facial recognition). Incorporating privacy into digital signage services becomes more important in this context. + +Digital signage service entities may consider creating voluntary privacy guidelines. + +The *OECD Guidelines on the Protection of Privacy and Transborder Flows of Personal Data* [b-OECD] can be considered as an introduction and general guidelines for privacy in audience measurement [b-ITU-T H.740]. + +The Federal Trade Commission [b-FTC] also proposes principles which can be applied broadly to companies engaged in online behavioural advertising, defined as activities for tracking consumers online in order to deliver advertising that targets the individual consumers' interests. The Federal Trade Commission [b-FTC] stresses the principles' applicability to different types of data and different advertising practices; not only for the collection and use of personally identifiable information (PII), but also of non-personally identifiable information (non-PII); collection and use of data; and the applicability to online contextual advertising. + +NOTE 1 – Traditionally, PII has been defined as information that can be linked to a specific individual including, but not limited to, name, postal address, e-mail address, social security number, or driver's license number. Non-PII includes anonymous data that, without more, cannot identify a specific person. + +NOTE 2 – The Digital Signage Federation [b-DSF] divides no-PII into audience measurement data and anonymous information used in other services (e.g., MAC address). + +These audience measurements may be relevant to the scope of the principles (e.g., video recognition systems that identify and counting specific classes of individuals passing-by). + +## III.2 Principles for privacy + +Digital signage service entities are encouraged to refer to the following general principles [b-FTC] for privacy and provide practical ways to avoid privacy issues: + +- **Transparency and consumer control:** This is an important aspect in the services. When consumers' information is collected, the service entities should provide prominent notice to consumers about such practices and should offer consumers the ability to choose whether or not to allow such collection and use. The notice may include policies for collection (e.g., why/where/for what is data collected). [b-FTC] shows the following general principles for consent based on the privacy classes. +- **Choice for non-PII:** Service entities should notify consumers when they are collecting information about consumers' activities for services. + +NOTE – The report [b-FTC] does not specify whether this choice would be opt-in, which is an affirmative express consent, or opt-out, which is prohibition against the treatments. Opt-out has beneficial aspects as it is easy to use and accessible to consumers. + +- **Consent for PII:** Opt-in for uses of data should be requested. + +The report also addresses the principles for use data collection; reasonable security and limited data retention for consumer data; secondary use which is the use of collection data for purposes other than the digital signage services; and other relevant aspects. + +# Appendix IV + +## Terminal device interfaces + +(This appendix does not form an integral part of this Recommendation.) + +There are several industrial standards concerning input/output interfaces. This appendix makes efforts to introduce possible standards relating to the interfaces of the DS terminal devices. + +### IV.1 Input interface + +#### IV.1.1 Storage interfaces + +DS terminal devices are equipped with a communication port to connect among computers and peripherals (e.g., universal serial bus [b-USB Forum]) and/or a flash memory as a means of data storage. + +#### IV.1.2 Control interfaces + +RS-232 [b-TIA 232-F] can be used in DS as a means of terminal device control. + +#### IV.1.3 Network interfaces + +DS terminal devices may support a TCP/IP LAN/Wireless port [b-IEEE 802.3], [b-IEEE 802.11]. + +### IV.2 Output interfaces + +#### IV.2.1 RGB analogue interfaces + +Analogue signal output can be handled through the following specifications: + +- Analogue interfaces complying with the RGB colour codes model of [b-CEA-863]. +NOTE – RGBHV is a variant of RGB model applicable for DS displays as well as PC computer monitors, with five lines: red, green, blue, horizontal sync and vertical sync. +- Digital video interface analogue (DVI-A)/digital video interface integrated (DVI-I) interfaces [b-DDWG DVI]. + +#### IV.2.2 Digital video interfaces + +The following standards are a means to handling digital video output: + +- High-definition multimedia interface (HDMI) [b-CEA 861]. +- Low-voltage differential signalling (LVDS) [b-TIA 644]. +- Digital video interface digital (DVI-D)/DVI-I [b-DDWG DVI]. +- DisplayPort [b-VESA DisplayPort]. + +#### IV.2.3 Digital audio interfaces + +This item is for further study. + +# Bibliography + +- [b-ITU-T E.106] Recommendation ITU-T E.106 (2003), *International Emergency Preference Scheme (IEPS) for disaster relief operations.* +- [b-ITU-T F.790] Recommendation ITU-T F.790 (2007), *Telecommunications accessibility guidelines for older persons and persons with disabilities.* +- [b-ITU-T G.711] Recommendation ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies.* +- [b-ITU-T H.222.0] Recommendation ITU-T H.222.0 (2006) | ISO/IEC 13818-1:2007, *Information technology – Generic coding of moving pictures and associated audio information: Systems.* +- [b-ITU-T H.262] Recommendation ITU-T H.262 (2000) | ISO/IEC 13818-2:2000, *Information technology – Generic coding of moving pictures and associated audio information: Video.* +- [b-ITU-T H.264] Recommendation ITU-T H.264 (2007) | ISO/IEC 14496-10:2008, *Advanced video coding for generic audiovisual services.* +- [b-ITU-T H.740] Recommendation ITU-T H.740 (2010), *Application event handling for IPTV services.* +- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2006), *Designations for interconnections among operators' networks.* +- [b-ITU-T T.81] Recommendation ITU-T T.81 (1992) | ISO/IEC 10918-1:1994, *Information Technology – Digital compression and coding of continuous-tone still images – Requirements and guidelines.* +- [b-ITU-T T.174] Recommendation ITU-T T.174 (1996), *Application programming interface (API) for MHEG-1.* +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks.* +- [b-ITU-T Y.Sup.5] ITU-T Y Suppl. 5 (2008), *ITU-T Y.1900-series – Supplement on IPTV service use cases.* +- [b-ITU-T TechWatch] ITU-T Technology Watch Report (2011), *Digital signage: the right information in all the right places.* +- [b-ISO/IEC 11172-3] ISO/IEC 11172-3:1993, *Information Technology – Coding of Moving Pictures and Associated Audio for Digital Storage Media at up to About 1,5 Mbit/s – Part 2: Video.* +- [b-ISO/IEC 13818-7] ISO/IEC 13818-7:1997, *Information Technology – Generic Coding of Moving Pictures and Associated Audio Information – Part 7:Advanced Audio Coding (AAC).* +- [b-ISO/IEC 14496-3] ISO/IEC 14496-3:2003, *Information technology – Coding of audiovisual objects – Part 3:Audio.* +- [b-ISO/IEC 14496-14] ISO/IEC 14496-14:2003, *Information technology – Coding of audiovisual objects – Part 14:MP4 file format.* + +- [b-ISO/IEC 15948] ISO/IEC 15948:2003, *Information technology – Computer graphics and image processing – Portable Network Graphics (PNG): Functional specification.* +- [b-ISO/IEC 23009-1] ISO/IEC FDIS 23009-1:2011, *Information technology – Dynamic adaptive streaming over HTTP (DASH) – Part 1: Media presentation description and segment formats.* +- [b-CEA 861] CEA Standard CEA-861-E (2008), *A DTV Profile for Uncompressed High Speed Digital Interfaces.* +- [b-CEA 863] CEA Standard CEA/CEDIA-863-B (2011), *Connection Color Codes for Home Theater Systems.* +- [b-DDWG DVI] Digital Display Working Group, (1999), *Digital Video Interface DVI Revision 1.0.* +[http://www.ddwg.org/lib/dvi\\_10.pdf](http://www.ddwg.org/lib/dvi_10.pdf). +- [b-DSF] Digital Signage Federation, *Digital Signage Privacy Standard* (2011). +. +- [b-ETSI TS 102 366] ETSI TS 102 366 V1.2.1 (2008), *Digital Audio Compression (AC-3, Enhanced AC-3) Standard.* +- [b-FTC] Federal Trade Commission (2009), *FTC Staff Report: Self-Regulatory Principles For Online Behavioral Advertising.* +. +- [b-IEEE 802.3] IEEE 802.3-2008, *IEEE Standard for Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks--Specific requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications.* +- [b-IEEE 802.11] IEEE 802.11-2012, *IEEE Standard for Information technology – Telecommunications and information exchange between systems Local and metropolitan area networks – Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specification.* +. +- [b-OECD] Organisation for Economic Co-operation and Development (OECD), OECD Council Recommendation (23 September 1980), *OECD Guidelines on the Protection of Privacy and Transborder Flows of Personal Data.* +. +- [b-POPAI] POPAI, . +- [b-TIA 232-F] TIA/EIA-232-F (2002), *Interface between data terminal equipment and data circuit-terminating equipment employing serial binary data interchange.* +. +- [b-TIA 644] TIA/EIA-644 (2001), *Electrical characteristics of low voltage differential signalling (LVDS) interface circuits.* +. +- [b-USB Forum] USB Implementers Forum. +. + +- [b-VESA DisplayPort] Video Electronics Standard Association, DisplayPort Standard Version 1.2 (2010). +. +- [b-W3C SVG 1.1] W3C Recommendation SVG 1.1 (2009), *Scalable Vector Graphics (SVG) 1.1 Specification*. +. + + + + + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2270f4475d3e5ba3232d9b252241163b1409ba73 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2738f739ad4729065a4284582bd03732f855ca3c12c6397f2135b7c7a6f86c4f +size 35311 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6998d598b908f52b2294df6d4bace9e5d56d552 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dbe29570930bd05e7324f390b2de26ec1a0bf6e92cb729f74f13a12e7c1d685 +size 31653 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b62d5cead7c25920ca93e8d55ba8d63e44675416 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95a313ab34ebe9adae27049a2df37ad52f05deda937219d6647eee38e1d6c129 +size 44105 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bba8d77f37ceba9a23509057f71199f5b8081dbc --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd62919857e44216ec957ef03243b6096e9cb64d6e00653f5704784d8514045c +size 6856 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffcab07a20c115945f5589c1ae3d47f2937316ed --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd339aed51e8a5b63ed7789876333b0e78b80ff1b9ff7622cb4c42930abbe566 +size 110949 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25321c24e928adaab769c6355627328605e04838 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:effc82d075d64e9000c46fafdb930cdce0b6d2d3969d46638ff0dd2c67512ed2 +size 29525 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13326fe13fd619334fb8d38294de503cc4fc0b1b --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3e8b86f01217898dc3db3425a138a6719121bb43652950536e451e04cb6b0dd +size 76979 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fabd43e8c1ddc5ab1e3b880f1072bac3b9000dac --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98f94f42276df27a037647309e4c0e1f62dc0ca32d4703985fb95026b68fe2f1 +size 38152 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31cb1e1617af2ae9817df5e549315aea775df04c --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fff0a912309ce617fa006533ce0ac6c61111000674cb48dbafb6affdffffc864 +size 71323 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa5121b429ea4ddd1c5daf849da3fc9eec75c486 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:806cd849ce2c2ede56d9ea467d6ad754d5f747d4cfed06a4fc562909da5c781b +size 128478 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d0a8f03675f4eb3b4418724af9c1c68496f42a5 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b418a7ba40ddbb43c096821787fb95074724754fd43387878b6e2b6fc6cb5a2c +size 99453 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e3cb78d9f74f6ee8f69ffec1f03fb62fe7579b8 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a8826011c50e1cdc6cfbf06717869eab2d2f7823525f8e6a9521015ecf0a64b +size 83291 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f93fcb6083dfdb4ebeb638ae336b05f35b416bf0 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d57e5e7e084e2017906590cf082c8e0e49f43c6a1f450b5c82d69a450568751 +size 90182 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d38ec102ece2528e43d90d88b792cc1853e488c0 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f923b39bbe2561c711dbf1076c4f7a65a58492cec453cdb49636812c62d832ea +size 59867 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e8cd7e6453afd65ddb212459d6adcfc3e0847d0 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0515465230acf8c42a05dc54b69de5b21e929af99d9ad197f150b061b0b9fe1a +size 70694 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..077d086abe5a277d1553187f4146b4eb60584494 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f969e22ecd09640ec9f367088459f67d58e0cbc26dbe8db382f83dfde90e610 +size 54184 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bad2cace77a93d34b301227a37bb0d8f450997e7 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb901440b8ef81733f8d318f267e78d7fa42f8d92c6d2786e33df50c552688c2 +size 116131 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..158f3303bc082e7749c03ff57a2a5acfe82a8f8f --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8bf6ec64b4bc7a0eaf40a2a8b4e60782df6aff324d9f9e59f2f61c738d6a185 +size 5430 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/f64e1e0997695248c0cd4122c5b1a170_img.jpg b/marked/H/T-REC-H.781-201504-I_PDF-E/f64e1e0997695248c0cd4122c5b1a170_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56b5f5ee12f04765283d6f4c7684ed9854ca7244 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/f64e1e0997695248c0cd4122c5b1a170_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82232c77781294fc939b4e1df27d3b0f4a274e4488ee893e16cd918ff93700b9 +size 57946 diff --git a/marked/H/T-REC-H.781-201504-I_PDF-E/raw.md b/marked/H/T-REC-H.781-201504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..85106d31dd2d64e38af9536828861374f4173cc1 --- /dev/null +++ b/marked/H/T-REC-H.781-201504-I_PDF-E/raw.md @@ -0,0 +1,1153 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.781** + +(04/2015) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +Digital Signage + +# --- **Digital signage: Functional architecture** + +Recommendation ITU-T H.781 + +**ITU-T** + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a stylized globe with a red lightning bolt striking across it. The letters "ITU" are prominently displayed in blue and red. + +ITU logo + +International +Telecommunication +Union + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T H.781 + +# Digital signage: Functional architecture + +## Summary + +Recommendation ITU-T H.781 defines a detailed functional architecture to provide digital signage (DS) services. The functional architecture consists of DS server, DS client, content delivery server and content delivery client. This Recommendation describes how functions in the architecture interact with each other to provide the services according to general information flows and defines reference points that can be considered in specifying detailed protocols. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.781 | 2015-04-29 | 16 | 11.1002/1000/12466 | + +## Keywords + +Digital signage, functional architecture, information flows, reference points. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2015 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Functional architecture of DS services ..... | 4 | +| 6.1 Overview of functional architecture of DS service ..... | 4 | +| 6.2 Functional architecture of a DS client ..... | 8 | +| 6.3 Functional architecture of a content delivery client ..... | 11 | +| 6.4 Functional architecture of DS server ..... | 13 | +| 6.5 Functional architecture of content delivery server ..... | 16 | +| 7 Reference points ..... | 17 | +| 7.1 R1: Digital signage client and digital signage server ..... | 17 | +| 7.2 R2: Digital signage server and content delivery server..... | 18 | +| 7.3 R3: Digital signage client and content delivery client..... | 18 | +| 7.4 R4: Content delivery client and content delivery server ..... | 19 | +| 7.5 R5: Digital signage server and content provider ..... | 19 | +| 8 Information flows ..... | 19 | +| 8.1 Configuration of terminal devices ..... | 19 | +| 8.2 Play of content and its report..... | 20 | +| 8.3 Display of alerting information ..... | 23 | +| 8.4 Interactive services ..... | 24 | +| 8.5 Content delivery ..... | 25 | + + + +# Recommendation ITU-T H.781 + +# Digital signage: Functional architecture + +# 1 Scope + +This Recommendation describes functional architecture for digital signage (DS) services as follows: + +- architectural overview; +- functions and functional entities (FEs); +- reference points; +- information flows to support the services. + +This Recommendation extends the high-level architecture defined in [ITU-T H.780] to accommodate various kinds of underlying transport infrastructures. This expansion covers interactive services amongst audience and terminal devices by using external devices such as touch panels. This Recommendation can be used as a reference for specifying protocols for DS services. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.780] Recommendation ITU-T H.780 (2012), *Digital signage: Service requirements and IPTV-based architecture*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 content** [ITU-T H.780]: A combination of audio, still image, graphic, video, or data. + +NOTE – Variety of formats is classified as the "data" (e.g., text, encoded values, multimedia description language introduced by [b-ITU-T H.760]). + +**3.1.2 delivery** [ITU-T H.780]: Sending of contents to terminal devices. + +**3.1.3 digital signage (DS)** [ITU-T H.780]: A system that sends information, advertising and other messages to electronic devices (e.g., displays, speakers) in accordance with the time of day and the location of the display, or the actions of audience. Content and its relevant information such as display schedules is delivered over networks. + +**3.1.4 network provider** [ITU-T H.780]: The organization that maintains and operates the network components required to support a service or set of services. + +**3.1.5 overlay network** [b-ITU-T X.1162]: An overlay network is a virtual network that runs on top of another network. Like any other network, the overlay network comprises a set of nodes and links between them. Because the links are logical ones, they may correspond to many physical links of the underlying network. + +**3.1.6 peer** [b-ITU-T X.1161]: Communication node on P2P network that functions simultaneously as both "client" and "server" to the other nodes on the network. + +**3.1.7 peer-to-peer (P2P)** [b-ITU-T Y.2206]: A system is considered to be P2P if the nodes of the system share their resources in order to provide the service the system supports. The nodes in the system both provide services to other nodes and request services from other nodes. + +**3.1.8 playlist** [ITU-T H.780]: Composed of a list of contents. + +NOTE 1 – This data is created and provided by digital service providers. + +NOTE 2 – This data can be selected by an end-user when interactivity is supported in a digital signage terminal device. + +NOTE 3 – This data may indicate an order of playing content. + +**3.1.9 playlist schedule** [ITU-T H.780]: Composed of a list of playlists indicated by a specific play date and/or time. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 buffer map:** Messages in peer-to-peer (P2P) networks that peers exchange to indicate which chunks of data a peer currently has buffered and can share with other peers. + +**3.2.2 content delivery schedule:** A schedule that describes time constraints of specific content to be delivered to terminal devices. + +NOTE – Since content needs to be distributed to terminals prior to being displayed, the content delivery schedule may provide alternative ways for content delivery with specific time constraints. + +**3.2.3 proof-of-play (PoP):** Any technique that can identify and prove that the content has been displayed on the screen. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------------|--------------------------------------| +| AM | Audience Measurement | +| CliCnf | Client Configuration | +| CliCnfMgm | Client Configuration Management | +| CliCntMgm | Client Content Management | +| CliInfMgm | Client Information Management | +| CliLogGen | Client Log Generator | +| CliLogMgm | Client Log Management | +| CliPlySch | Client Play Scheduler | +| CntDlvCliCtrl | Content Delivery Client Control | +| CntDlvLogMgm | Content Delivery Log Management | +| CntDlvSchMgm | Content Delivery Schedule Management | +| CntDlvSvrCtrl | Content Delivery Server Control | +| CntIngReg | Content Ingestion and Registration | +| CntMtdMgm | Content Metadata Management | +| CntP2pPeer | Content P2P Peer | + +| | | +|------------|------------------------------| +| CntPly | Content Player | +| CntPrp | Content Pre-process | +| CntPullCli | Content Pull Client | +| CntPullSvr | Content Pull Server | +| CntPushCli | Content Push Client | +| CntPushSvr | Content Push Server | +| DS | Digital Signage | +| DvcCtr | Device Control | +| DvcEvtRcv | Device Event Receiver | +| DvcStsMnr | Device Status Monitor | +| EvtDatCnv | Event Data Converter | +| FE | Functional Entity | +| IPTV | Internet Protocol Television | +| LogRptSch | Log and Report Scheduler | +| LytArr | Layout Arrangement | +| LytMgm | Layout Management | +| LytRnd | Layout Rendering | +| NIC | Network Interface Card | +| P2P | Peer-to-Peer | +| PlyLogGen | Play Log Generator | +| PlyLogMgm | Play Log Management | +| PlySchMgm | Play Schedule Management | +| PoP | Proof-of-Play | +| RegEvtDsp | Registered Event Dispatcher | +| SMS | Short message service | +| SngSvcCtr | Signage Service Control | +| SngSvcMnr | Signage Service Monitor | +| StrMgm | Storage Management | +| SysAltCtr | System Alert Control | +| TTS | Text-to-Speech | + +# 5 Conventions + +In this Recommendation: + +- The keyword "functions" is defined as a collection of functionalities. It is represented by the following symbol in this Recommendation: + +Functions + +- The keyword "functional entity" (FE) is defined as a group of functionalities that has not been further subdivided at the level of detail described in this Recommendation. It is represented by the following symbol in this Recommendation: + +![A rectangular box containing the text 'Functional Entity (FE)'.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +Functional +Entity (FE) + +A rectangular box containing the text 'Functional Entity (FE)'. + +NOTE – In the future, other groups or other Recommendations may possibly further subdivide these FEs. + +Frame borders of "functions" and "FE", and relational lines among "functions" and "FE" are drawn with solid lines or dashed lines. The solid lines mean required functionalities or relations. On the other hand, the dashed lines mean optional functionalities or relations. + +# 6 Functional architecture of DS services + +This clause describes the detailed functional architecture for DS services by extending the high-level architecture defined in [ITU-T H.780] for accommodating various kinds of underlying transport infrastructures and support of various new features described as follows. It is aligned with the requirements that are defined in [ITU-T H.780]: + +- Support of a wide variety of content delivery methods: +While both push and pull modes of content delivery are supported, this Recommendation defines an alternative FE for P2P-based content delivery; +- Support of interaction with user through various peripheral devices: +This Recommendation defines several FEs to support interactions with audiences by making use of external devices that are attached to the terminal devices; +- Definition of reference points: +This Recommendation defines reference points that are for further study for specifying mechanisms and protocols to be used for interoperability. + +## 6.1 Overview of functional architecture of DS service + +Figure 1 shows an overview of functional architecture for DS services. This Recommendation covers interaction among an audience/user, a DS terminal device and a DS service operator. + +NOTE 1 – In this Recommendation, "user" means a person who uses the DS service for the purpose of their business. For example, a retailer can utilise a DS service for sales promotion. + +The interaction between a DS service operator and a content provider is out of scope of this Recommendation. + +![Figure 1 – Architectural overview for DS services. The diagram shows the interaction between an Audience/user, a Digital signage terminal, a Digital signage service operator, and a Content provider or other business system, all connected via Network functions. The Digital signage terminal contains a Digital signage client, a Content delivery client, and optional functions (AM client, Security client, Common alert client). The Digital signage service operator contains a Digital signage server, a Content delivery server, and optional functions (AM aggregation, Security, Common alert server). Arrows indicate the flow of information: Presentation and Interaction between Audience/user and Digital signage client; Digital signage service control and Logs, notifications between Digital signage client and Digital signage server; Content registration (content, metadata) and Report between Digital signage server and Content provider or other business system; Delivery schedule playlists contents between Digital signage server and Content delivery server; and Network functions connecting the Content delivery client and Content delivery server.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +H.781(15)\_F01 + +Figure 1 – Architectural overview for DS services. The diagram shows the interaction between an Audience/user, a Digital signage terminal, a Digital signage service operator, and a Content provider or other business system, all connected via Network functions. The Digital signage terminal contains a Digital signage client, a Content delivery client, and optional functions (AM client, Security client, Common alert client). The Digital signage service operator contains a Digital signage server, a Content delivery server, and optional functions (AM aggregation, Security, Common alert server). Arrows indicate the flow of information: Presentation and Interaction between Audience/user and Digital signage client; Digital signage service control and Logs, notifications between Digital signage client and Digital signage server; Content registration (content, metadata) and Report between Digital signage server and Content provider or other business system; Delivery schedule playlists contents between Digital signage server and Content delivery server; and Network functions connecting the Content delivery client and Content delivery server. + +**Figure 1 – Architectural overview for DS services** + +There are several entities in DS services, including but not limited to the following: + +- **Audience/user:** The audience or user, or his/her own device that interacts with a DS terminal device for exchange of information; +- **DS terminal:** The device that displays content received from a DS service provider. Its behaviour is controlled and managed by the DS service provider; +- **DS service operator:** The business operator that provides DS services. It manages DS terminal devices for displaying content received from a content provider; +- **Content provider or business system:** This entity provides content to the DS provider for a particular purpose, e.g., advertisements, information, alerts. + +NOTE 2 – Use cases linking with other business systems are listed in [b-ITU-T HSTP.DS-UCIS]. + +Main groups of functions within the DS terminal and the DS service operator are as follows: + +- **DS client:** Is responsible for content presentation and interactions with audiences; +- **Content delivery client:** Is responsible for acquiring content through a network; +- **DS server:** Has capabilities for administration of DS system, control of content delivery and management of DS terminal devices; +- **Content delivery server:** Delivers content to the content delivery client. + +The following are optional functionalities: + +- **Security:** Controls the protection of the services and content. Content protection includes control of access to content and the protection of content using methods such as encryption. Service protection includes authentication and authorization of access to services. (See [ITU-T H.780], clause 6.2.2.); +- **Security client:** Interacts with the security functions to provide service protection and content protection. The security client functions verify the usage rights and decrypt content. It is also necessary to consider physical security of the terminal devices under unmanned conditions. (See [ITU-T H.780], clause 6.2.2.); +- **Audience measurement (AM) aggregator:** Aggregates AM information, such as viewership, audience interaction information and audience-related information. It also may + +summarize and report the information to organizational entities in a content provider domain. (See [ITU-T H.780], clause 6.2.2.); + +- **AM client:** Analyses audience information and report to the AM functions (e.g., the number of people in the audience) (See [ITU-T H.780], clause 6.2.2.); +- **Common alert client:** Supports display of alerting messages received from common alerting servers and can send device events from the DS terminal to the common alert server. This client can convert alerting information to other media formats for accessibility; +- **Common alert server:** Supports a common alerting service in DS by managing data relevant to the common alerting service, such as alerting area, list of terminal, exit routing information, etc. This server receives alert information from the alert agency, and delivers it to the common alert client. + +Figure 2 shows functional architecture for DS services between the DS terminal and the DS service operator in a functions level. + +![Figure 2 – Functional architecture of DS services. The diagram shows two main components: the Digital signage terminal device and the Digital signage service operator. The terminal device contains a Digital signage client with Interactive device functions, Device management functions, Content processing functions, and Log and report functions. It also contains a Content delivery client with Content delivery client functions. The service operator contains a Digital signage server with Client management functions, Log management functions, Schedule management functions, and Content management functions. It also contains a Content delivery server with Content delivery server functions. The terminal device is connected to the service operator via lines representing data flow. On the left side of the terminal device, there are icons for Displays, HDD, and Peripherals.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram illustrates the functional architecture of DS services, divided into two main entities: the **Digital signage terminal device** and the **Digital signage service operator**. + +**Digital signage terminal device:** This entity is composed of several functional blocks. At the top, it lists physical components: **Displays**, **HDD**, and **Peripherals**. Below these, the **Digital signage client** is shown, which includes **Interactive device functions**, **Device management functions**, **Content processing functions**, and **Log and report functions**. At the bottom of the terminal device is the **Content delivery client**, which contains **Content delivery client functions**. + +**Digital signage service operator:** This entity includes the **Digital signage server**, which consists of **Client management functions**, **Log management functions**, **Schedule management functions**, and **Content management functions**. A large box labeled **Signage service management functions** is also present. At the bottom is the **Content delivery server**, which contains **Content delivery server functions**. + +Connections between the terminal and the operator are shown as lines: the **Digital signage client** connects to the **Digital signage server**, and the **Content delivery client** connects to the **Content delivery server**. + +Figure 2 – Functional architecture of DS services. The diagram shows two main components: the Digital signage terminal device and the Digital signage service operator. The terminal device contains a Digital signage client with Interactive device functions, Device management functions, Content processing functions, and Log and report functions. It also contains a Content delivery client with Content delivery client functions. The service operator contains a Digital signage server with Client management functions, Log management functions, Schedule management functions, and Content management functions. It also contains a Content delivery server with Content delivery server functions. The terminal device is connected to the service operator via lines representing data flow. On the left side of the terminal device, there are icons for Displays, HDD, and Peripherals. + +**Figure 2 – Functional architecture of DS services** + +A DS terminal consists of two types of clients: A DS client and a content delivery client, as shown in Figure 2. The following is an outline of functionalities: + +- **Client processing functions:** Manage the overall behaviour of the DS terminal. They control the scheduling of the content played, configuration regarding services and interactions with the DS server; +- **Interactive device functions:** Handle interactions between an audience and manipulation devices/sensors of a terminal device; +- **Content processing functions:** Prepare content prior to display to the terminal; +- **Device management functions:** Manage devices that are attached to the terminal such as storage, peripherals and displays; +- **Log and report functions:** Aggregate log messages generated during system operation, and sends them to the signage server according to its policy, such as reporting frequency and time to report. It is possible to store the logs into a local storage for a while. It is also possible to report whenever a log message is generated; +- **Content delivery client functions:** Receive and download content from the content server. They can also distribute content to other terminals. + +NOTE 3 – These functions include *content delivery* functions of Internet protocol television (IPTV)-based terminal device functions (refer to [ITU-T H.780], clause 8.2.2). + +A DS service operator consists of a DS server and a content delivery server. + +- **Client management functions:** Control and monitor the DS terminals; +- **Signage service management functions:** Control and monitor DS services; +- **Log management functions:** Aggregate logs from terminals and store them for further usages such as generating records or remote diagnosis; +- **Content management functions:** Manage content and metadata; +- **Schedule management functions:** Manage scheduling of the DS service which includes play schedule and content delivery schedule; +- **Content delivery server functions:** Deliver content to the DS terminal based on the delivery schedule. + +NOTE 4 – These functions include *content delivery* functions of IPTV-based DS systems (refer to [ITU-T H.780], clauses 6.2.2 and 8.3). + +NOTE 5 – Table 1 shows a relationship of ITU-T H.780 functional blocks with functions/FEs in this Recommendation. + +**Table 1 – Relations of functional blocks of [ITU-T H.780]** + +| DS client functional blocks in [ITU-T H.780] | Functions/FEs in this Recommendation | +|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Play control (clause 8.2.1.1) | Client processing functions:
    – Client play scheduler (CliPlySch) FE
    Log and report functions:
    – Play log generator (PlyLogGen) FE;
    – Log report scheduler FE | +| Media processing (clause 8.2.1.2) | Content processing functions:
    – Content pre-process (CntPrp) FE;
    – Layout arrangement FE;
    – Layout rendering (LytRnd) FE | +| Storage (clause 8.2.1.5) | Device management functions:
    – Storage management (StrMgm) FE | +| Service discovery (for content delivery services) | For further study | + +**Table 1 – Relations of functional blocks of [ITU-T H.780]** + +| DS application functional blocks in [ITU-T H.780] | Functions/FEs in this Recommendations | +|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configuration (clause 8.1.1) | Client management functions:
    – Client configuration management (CliCnfMgm) FE;
    – Client information management (CliInfMgm) FE | +| System management (clause 8.1.2) | Signage service management functions:
    – Signage service control (SngSvcCtr) FE;
    – Signage service monitor (SngSvcMnr) FE | +| Play log aggregation and reporting (clause 8.1.3) | Log management functions:
    – Play log management (PlyLogMgm) FE | +| Schedule and delivery management (clause 8.1.5) | Schedule management functions:
    – Content delivery schedule management (CntDlvSchMgm) FE;
    – Play schedule management (PlySchMgm) FE
    Log management functions;
    – Content delivery log management (CntDlvLogMgm) FE | +| Content management (clause 8.1.4) | Content management functions:
    – Content ingestion and registration (CntIngReg) FE;
    – CntPrp FE;
    – Content metadata management (CntMtdMgm) FE | + +## 6.2 Functional architecture of a DS client + +This clause describes functions for a DS client. The DS client consists of five functions: Client processing functions, content processing functions, device management functions, interactive management functions and log and report functions. + +![Functional architecture of a DS client diagram showing five main functional blocks: Client processing functions, Content processing functions, Device management functions, Interactive device functions, and Log and report functions.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +The diagram illustrates the functional architecture of a Digital Signage Client, organized into five main functional blocks within a 'Digital signage client' container: + +- Client processing functions:** Includes 'Client configuration' and 'Client play scheduler'. +- Content processing functions:** Includes 'Layout arrangement', 'Layout rendering', 'Client contents management', 'Content pre-process', and 'Content player'. +- Device management functions:** Includes 'Storage management', 'Device control', and 'Device status monitor'. +- Interactive device functions:** Includes 'Registered event dispatcher', 'Device event receiver', and 'Event data convert'. +- Log and report functions:** Includes 'Play log generator', 'Client log generator', and 'Log report scheduler'. + +H781(15)\_F03 + +Functional architecture of a DS client diagram showing five main functional blocks: Client processing functions, Content processing functions, Device management functions, Interactive device functions, and Log and report functions. + +**Figure 3 – Functional architecture of a DS client** + +### **6.2.1 Client processing functions** + +Client processing functions control the behaviour of DS terminals. There are two FEs: CliPlySch FE and client configuration (CliCnf) FE. + +#### **6.2.1.1 CliPlySch FE** + +The CliPlySch FE manages schedules regarding play of content/change of layout, and interacts with the PlySchMgm FE of a DS server for retrieving the schedules. + +This FE is also capable of reordering or manipulating the schedule on specific local events, if permitted. For example, when the audience manipulates the terminal by interacting with a touch panel, the schedule of the content or layout may be changed for providing information that the audience has requested. + +#### **6.2.1.2 CliCnf FE** + +The CliCnf FE interacts with the client management functions of the DS server for setting the configuration parameters of a DS terminal device. This FE may handle metadata describing capabilities or characteristics of the terminal. + +NOTE – Details of metadata of terminal device information is for further study. The metadata is defined in [ITU-T H.780], clause 9.2 "Terminal device information", however, it is necessary to extend the specifications to better accommodate detailed characteristics of peripherals. + +### **6.2.2 Content processing functions** + +Content processing functions prepare content prior to sending the stream to output devices (such as display and speaker). They perform transcoding, multimedia decoding, LytRnd, etc. These functions consist of five FEs: content player (CntPly) FE, client content management (CliCntMgm) FE, CntPrp FE, LytRnd FE and layout arrangement (LytArr) FE. + +#### **6.2.2.1 LytRnd FE** + +The LytRnd FE renders layout consisting of multiple kinds of content by interacting with the LytArr FE, CliCntMgm FE and CntPrp FE, and outputs the rendered content to the display. Since the characteristics of display are often different (such as ratio, size and colour), this FE may change layout parameters such as position and size, according to the characteristics. + +#### **6.2.2.2 CliCntMgm FE** + +The CliCntMgm FE manages content which is obtained from a content delivery client. It also maintains content metadata, such as aspect ratio, resolution and sound. Content has its own identifier which will be used within the playlist and playlist schedule. + +#### **6.2.2.3 CntPrp FE** + +The CntPrp FE processes the content received from the server, in order to convert it to the appropriate format for presentation. It performs transcoding, resizing, etc. in order to fit with capabilities of terminal devices. Pre-processing of content by the DS server for all terminals is optional. + +#### **6.2.2.4 LytArr FE** + +The LytArr FE provides layout information to the LytRnd FE. It is possible to display multiple kinds of content on a single screen by arranging positions of the content as a layout. This FE may acquire layout information from the layout management (LytMgm) FE of DS server, and it can keep multiple layouts for rapid switching of layout. For example, this FE can change a pre-specified layout that can be used in a special situation such as an emergency in a unified manner. This FE is optional if the client does not manage layouts locally. + +#### **6.2.2.5 CntPly FE** + +The CntPly FE plays content according to playlists. It can interact with the PlyLogGen FE to report the event related to play of content. + +### **6.2.3 Device management functions** + +Device management functions manage the internal/external data storage and the attached devices including peripherals and display. There are three FEs: storage management (StrMgm) FE, device control (DvcCtr) FE and device status monitor (DvcStsMnr) FE. + +#### **6.2.3.1 StrMgm FE** + +The StrMgm FE stores and manages logs, content and content metadata into a local storage. + +#### **6.2.3.2 DvcCtr FE** + +The DvcCtr FE controls external peripherals that are attached into a DS terminal. Since a DS terminal can use various devices, the DvcCtr FE interacts with each device to get input and probing for the status of peripherals. This FE is optional. + +#### **6.2.3.3 DvcStsMnr FE** + +The DvcStsMnr FE monitors the status of device activities. It is important to keep track of the current status of each device, in particular by periodically probing the status of devices or receiving events to check whether they are operating properly. For example, if there is a network failure due to disconnection of a LAN cable that is attached to the network interface card (NIC) of a terminal device, the failure is detected and recorded as an event by this FE. When the network is recovered, the record may be sent to the client log management (CliLogMgm) FE for reporting to the server as per a pre-defined schedule. This FE is optional if the terminal does not support status monitoring of terminal devices. + +### **6.2.4 Interactive device functions** + +Interactive device functions translate actions of user/audience or sensor data, which are sensed through external/internal devices, into system events processed by client functionalities. There are three FEs: registered event dispatcher (RegEvtDsp) FE, device event receiver (DvcEvtRcv) FE and event data converter (EvtDatCnv) FE. + +#### **6.2.4.1 RegEvtDsp FE** + +The RegEvtDsp FE registers and manages events requested by other functions or FEs. Other functions or FEs can request this FE to inform them of the occurrence of particular events from an indicated device. The indicated device includes touch panel, keyboard, sensor, camera, or any other device in which an event can occur that has significance to the requester. A request from the requester may be in the form of a device identifier and description of the event. This FE registers the request and notifies the requester when the specified event occurs. If an event occurs in which no functions or FE has interest, the event is ignored. This FE is optional if the terminal does not support receiving event data from devices. + +#### **6.2.4.2 DvcEvtRcv FE** + +The DvcEvtRcv FE receives event data in raw data format from the interactive devices. It sends the received data to the EvtDatCnv FE. This FE is optional if the client does not support receiving event data from devices. + +#### **6.2.4.3 EvtDatCnv FE** + +The EvtDatCnv FE converts the event data to an event message that has a consistent format. The format of the raw data is varied depending on the types of interactive devices. This FE is optional if the client does not support receiving event data from devices. + +### 6.2.5 Log and report functions + +Log and report functions keep records of play logs and system logs, and send them to the DS server based on policies regarding the report schedule. It consists of: PlyLogGen FE, client log generator (CliLogGen) FE and log and report scheduler (LogRptSch) FE. + +#### 6.2.5.1 PlyLogGen FE + +The PlyLogGen FE creates a play record for content played in the client, and sends the play log to log and report functions in the DS server. The LogRptSch FE may initiate this reporting procedure. This FE may include information regarding system operation, play of content and audience measurement. The kind of information that should be logged is defined by service providers or system vendors. + +Since the network between the DS server and terminal devices can be a best effort network (i.e., the network does not guarantee reliability), the report message should be stored in a local storage for retransmission. + +When it is requested to confirm the integrity of the report message, such as proof-of-play (PoP), this FE includes PoP in the log data to provide proof of whether particular content has been played or not in the terminal device and provides a method for assuring the integrity of play log record. The PoP data can be acquired from specialized devices, such as a small camera attached in front of the display. Another possible method is to generate data for PoP by adding digital signatures or encrypting the play log data. The content owner may specify the format of data for PoP. This FE is optional if it does not support the functionality of generating records of content played. + +#### 6.2.5.2 CliLogGen FE + +The CliLogGen FE aggregates logs for system maintenance. This FE receives reports from DvcStsMnr FE on various kinds of events that are related to the operation of the client. This FE stacks up log messages until it receives a request from the LogRptSch FE to send a report to the DS server. This FE is optional if it does not support the functionality of handling status log of the terminal device. + +#### 6.2.5.3 LogRptSch FE + +The LogRptSch FE manages reporting. It receives a reporting policy, such as time to report and reporting frequency, from the server CliCnfMgm FE through the client CliCnf FE. When it is time to send a report message, it interacts with the PlyLogGen FE or the CliLogGen FE to request the sending of accumulated log data to a pre-specified address. This FE is optional if it does not support the functionality of scheduled reporting. + +## 6.3 Functional architecture of a content delivery client + +This clause describes the FEs of a content delivery client that acquires content from a content delivery server of a service provider. The content can be delivered in various ways, such as push, pull and P2P. Before the client receives content, it may first receive the content delivery schedule from the content delivery server. If it is specified to receive content with push mode, content is pushed to the content delivery client by the content delivery server. In the case of pull mode, each client requests particular content from the server. Since all DS terminals are connected into a network, it is possible to exchange content with each other. This lowers the load of the content delivery server and enhances distribution performance. Even though P2P-based content distribution can provide efficient and enhanced performance, an alternative delivery method needs to be provided since, while P2P-based delivery is delay-tolerant, the content should be delivered to the terminal device prior to actual display. + +NOTE – A P2P network is an overlay network composed of peers that share their resources with other peers, and it is constructed virtually amongst peers that are built on top of another network. See Figure 4. + +![Figure 4: P2P network diagram showing an overlay network of peers connected via virtual mapping to a physical network of routers and subnets.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +The diagram illustrates a P2P network architecture. At the top, a light blue oval labeled "P2P network" contains ten icons representing "Peer" devices (laptops and desktops) interconnected by orange lines. Below this, a horizontal red line with open circles at each end is labeled "Virtual mapping". Below the mapping line, a larger light blue oval labeled "Physical network" contains three routers, each represented by a circle with a red "X". These routers are connected to three separate subnets, each shown as a cloud containing several device icons. Dashed lines connect each peer in the P2P network to a specific router in the physical network, indicating the virtual mapping. The label "H.781(15)\_F04" is in the bottom right corner. + +Figure 4: P2P network diagram showing an overlay network of peers connected via virtual mapping to a physical network of routers and subnets. + +**Figure 4 – P2P network (b-ISO/IEC TR 20002)** + +When content distribution is done with P2P-based methods, an overlay network is constructed that contains the address of terminals that are currently downloading or have a full or partial copy of the content, and logically slices the content into multiple chunks with pre-specified size. Each terminal acting as a peer exchanges the chunks with multiple peers simultaneously. In general, one overlay network is constructed for one content, but it is possible to create one overlay network for multiple content as well. + +![Figure 5: Functional architecture of a content delivery client diagram.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram shows the functional architecture of a content delivery client. It consists of a main grey box labeled "Content delivery client". Inside this box is a blue box labeled "Content delivery client functions". Within the blue box, there is a white box at the top labeled "Content delivery client control". Below this control box are three separate boxes: "Content push client", "Content pull client", and "Content P2P peer" (the latter has a dashed border). The label "H.781(15)\_F05" is in the bottom right corner. + +Figure 5: Functional architecture of a content delivery client diagram. + +**Figure 5 – Functional architecture of a content delivery client** + +Figure 5 shows the functional architecture of a content delivery client that is composed of content delivery client functions. + +### 6.3.1 Content delivery client functions + +Content delivery client functions receive content from a remote content delivery server according to the delivery schedule. These functions consist of four FEs: Content delivery client control (CntDlvCliCtrl) FE, content push client (CntPushCli) FE, content pull client (CntPullCli) FE and content P2P peer (CntP2pPeer) FE. + +#### **6.3.1.1 CntDlvCliCtrl FE** + +The CntDlvCliCtrl FE interacts with the content delivery server control (CntDlvSvrCtrl) FE to get a content delivery schedule that describes the time, delivery method and network address that has content to be distributed, etc. This FE controls the other FEs for acquiring content according to the schedule. In order to deliver content prior to actual display, the content delivery schedule would have time constraints. If the content delivery client fails to acquire content with specific time constraints, it retries to acquire content. In this case, terminal devices may acquire content from an alternative content server with an alternative method. + +#### **6.3.1.2 CntPushCli FE** + +The CntPushCli FE receives content from the content delivery server with a push-type delivery. When the CntDlvCliCtrl FE requests the CntPushCli FE to prepare for receiving specific content, this FE begins to listen to a specific network interface. It is also possible for it to be ready all the time to receive content from the server. When this FE completes reception of content, the FE checks the integrity of the received content and notifies the result of content delivery to the CntDlvCliCtrl FE. + +#### **6.3.1.3 CntPullCli FE** + +The CntPullCli FE gets content by requesting content as specified in a content delivery schedule. Since the schedule contains the delivery schedule per each terminal, this FE begins to request delivery according to a pre-specified time. When it completes the delivery of a particular content, this FE notifies the CntDlvCliCtrl FE after an integrity check. + +#### **6.3.1.4 CntP2pPeer FE** + +The CntP2pPeer FE receives content with P2P-type delivery. Since a DS service provider manages terminal device information such as its IP address, an overlay network for specific content delivery is pre-constructed. This FE receives the addresses of other CntP2pPeer FEs from the CntDlvCliCtrl FE of the content delivery server, and exchanges the content in parallel with other clients. This FE is optional if the terminal does not support P2P-based content delivery. + +NOTE – In generic P2P-based content delivery, a client is required to explicitly join or leave processes of an overlay network. Since an overlay network for content delivery is pre-constructed in DS services, terminal devices do not need to explicitly join or leave the overlay network. + +## **6.4 Functional architecture of DS server** + +This clause describes the functions of a DS server, which consists of five functions: client management functions, log management functions, schedule management functions, DS service management functions and content management functions. See Figure 6. + +![Functional architecture of DS server diagram showing various management functions grouped within a Digital signage server.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +The diagram illustrates the functional architecture of a Digital signage server, organized into several management function groups: + +- Client management functions**: + - Client configuration management + - Client information management +- Digital signage service management functions**: + - Signage service control + - Signage service monitor + - System alert control +- Log management functions**: + - Play log management + - Client log management + - Content delivery log management +- Content management functions**: + - Content ingestion and registration + - Content metadata management + - Content pre-process + - Layout management +- Schedule management functions**: + - Content delivery schedule management + - Play schedule management + +H.781(15)\_F06 + +Functional architecture of DS server diagram showing various management functions grouped within a Digital signage server. + +**Figure 6 – Functional architecture of DS server** + +### 6.4.1 Client management functions + +Client management functions remotely control and monitor DS terminal devices. Two FEs are defined: CliCnfMgm FE and CliInfMgm FE. + +#### 6.4.1.1 CliCnfMgm FE + +The CliCnfMgm FE controls each DS terminal device's behaviours by managing configurations of the terminal devices through interacting with the clients' CnfMgm FE. It can order the clients to retrieve the latest playlist. + +NOTE – Some types of operations that are dependent on the DS application (such as remote system administration) are out of scope of this Recommendation. + +#### 6.4.1.2 CliInfMgm FE + +The CliInfMgm FE manages information related to terminal devices. When an operator wants to register a new terminal device, the operator provides related information such as location, contact information (e.g., person in charge), terminal identifier, etc. When the terminal device boots up, it registers its information into this FE. This FE is optional. + +#### 6.4.1.3 Signage service management functions + +DS service management functions control DS services on behalf of the system operator and trigger alarms in case of system malfunction. These functions also manage the service profile for controlling the service. + +#### 6.4.1.4 SngSvcCtr FE + +The SngSvcCtr FE controls specific DS services based the on signage service profile. It interacts with other management functions within DS servers: content management, client management, log management and schedule management. + +#### 6.4.1.5 SngSvcMnr FE + +The SngSvcMnr FE monitors the log management functions for specific events. A periodic status report or play report will be delivered to log management functions. If a particular event that should + +be handled immediately occurs, this FE delivers the event message to the system alert control (SysAltCtr) FE. + +#### **6.4.1.6 SysAltCtr FE** + +The SysAltCtr FE alerts DS service administrators in case of a serious problem. In order to make this possible, the DS server should have a method (such as e-mail or short message service (SMS)) to notify to an administrator. + +### **6.4.2 Log management functions** + +Log management functions aggregate logs from DS terminal devices, and keep the records for further usage. These logs and reports can be used for PoP on specific content. + +#### **6.4.2.1 PlyLogMGM FE** + +The PlyLogMgm FE aggregates play logs from DS terminals. According to the policy regarding reporting frequency for the terminal, report from the client may contain multiple log data within it. Hence, this FE can be ready for receiving multiple logs within a record as well as one log within a record. This FE is optional if the system does not support the functionality of keeping records of content play. + +#### **6.4.2.2 CliLogMgm FE** + +The CliLogMgm FE aggregates logs of system status of DS client-side FEs, without play logs and content delivery logs. This FE is optional if it does not support logging of the status of client. + +#### **6.4.2.3 CntDlvLogMgm FE** + +The CntDlvLogMgm FE aggregates logs from content delivery clients and servers. The log message contains detailed information regarding content delivery such as content delivery method, start/end time of delivery, the address of terminal and content identifier. Content sharing activities may also be treated if P2P has been used. This FE is optional if the system does not support the functionality of aggregation of content delivery logs. + +### **6.4.3 Schedule management functions** + +Schedule management functions create and/or manage two types of schedules: a playlist schedule and a content delivery schedule. The content delivery schedule prevents a server or network from collapsing in case multiple clients try simultaneously to acquire content from a server. Therefore, the content delivery schedule may assign different content delivery time slots to each DS terminal device for traffic scattering, and embed additional information such as content information, time constraints, preferred delivery schedule and terminal device lists that are to acquire content. + +#### **6.4.3.1 PlySchMgm FE** + +The PlySchMgm FE creates and stores playlists and sends them to proper functions or FEs. + +#### **6.4.3.2 CntDlvSchMgm FE** + +The CntDlvSchMgm FE manages schedules for content delivery. This FE requests the content delivery client to distribute particular content to multiple DS terminals. + +### **6.4.4 Content management functions** + +Content management functions manage content and metadata. They receive and register content from the content provider or other business systems with detailed descriptions of the content. + +#### **6.4.4.1 LytMgm FE** + +The LytMgm FE creates layout for displaying one or more pieces of content within a single screen, and the layout will be sent to the LytMgm FE of each terminal. Generally, a layout is created and + +managed by a service operator, not terminal. A service operator can create various types of layout and allocate them to appropriate terminal devices. This FE is optional if LytMgm is not supported. + +#### 6.4.4.2 CntPrp FE + +The CntPrp FE pre-processes the content that is received from content providers or other business systems, prior to delivering it to DS terminal devices. This FE has functionalities similar to that of the CntPrp FE of a client that performs transcoding, resizing, etc. Optionality of the client and server CntPrp FEs are described in clause 6.2.2.3. + +#### 6.4.4.3 CntIngReg FE + +The CntIngReg FE receives content and its related metadata from a content provider or other business systems. When registration procedures are completed, this FE sends the content to content delivery server functions and registers metadata into the CntMtdMgm FE. Even though the content is sent to the content delivery server functions, the content is not delivered before the server functions receive the delivery request from CntDlvSchMgm FE. + +#### 6.4.4.4 CntMtdMgm FE + +The CntMtdMgm FE manages the metadata of content. It receives metadata from the content owner or other business systems and processes the metadata. + +## 6.5 Functional architecture of content delivery server + +The content delivery server takes the role of content delivery to remote DS terminal devices in various ways according to delivery schedules. If a massive number of signage terminal devices request content from a particular content server, the server may suffer from bottleneck problems, such as network congestion. Hence, the content delivery servers need to use delivery schedules. + +Figure 7 shows the functional architecture of a content delivery server that is composed of content delivery server functions. + +![Functional architecture of content delivery server diagram](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +The diagram illustrates the functional architecture of a content delivery server. It is structured as a nested box. The outermost box is labeled "Content delivery server". Inside this box is a blue-shaded area labeled "Content delivery server functions". Within this area, at the top, is a box labeled "Content delivery server control". Below this control box are three boxes arranged horizontally: "Content push server", "Content pull server", and "Content P2P peer". The "Content P2P peer" box is distinguished by a dashed border. Below the diagram, the text "H.781(15)\_F07" is displayed. + +Functional architecture of content delivery server diagram + +Figure 7 – Functional architecture of content delivery server + +### 6.5.1 Content delivery server functions + +Content delivery server functions deliver content to DS terminal devices according to a content delivery schedule managed by schedule management functions. It consists of four FEs: CntDlvSvrCtrl FE, content push server (CntPushSvr) FE, content pull server (CntPullSvr) FE and CntP2pPeer FE. + +#### 6.5.1.1 CntDlvSvrCtrl FE + +The CntDlvSvrCtrl FE controls other content delivery-related server FEs and interacts with content delivery client functions. When the content delivery server delivers content by means of P2P, this FE manages the overlay network. + +#### 6.5.1.2 CntPullSvr FE + +The CntPullSvr FE sends content with pull-type delivery, based on requests from terminal devices. This FE waits for the request from a client for specific content. Prior to sending the requested content, it checks whether the requester is authorized to access the content. When it finishes sending the requested content, this FE may notify the CntDlvSvrCtrl FE that interacts with the CntDlvLogMgm FE of the DS server. + +#### 6.5.1.3 CntPushSvr FE + +The CntPushSvr FE pushes content to remote DS terminal devices. This FE pushes content based on a delivery schedule. + +#### 6.5.1.4 CntP2pPeer FE + +The CntP2pPeer FE performs the same functionalities as the CntP2pPeer FE of the content delivery client except that it already has content. This FE is optional if P2P-based content delivery is not supported. + +# 7 Reference points + +This clause describes reference points between related entities, as illustrated in Figure 8. + +![Figure 8: Reference points between related entities. The diagram shows three main entities: Digital signage terminal, Digital signage service operator, and Content provider or Other business system. The Digital signage terminal contains a Digital signage client and a Content delivery client. The Digital signage service operator contains a Digital signage server and a Content delivery server. Reference points R1a, R1b, R1c, R2a, R2b, R2c, R2d, R3a, R3b, R4a, R4b, and R5 are indicated between the client and server functions.](f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg) + +The diagram illustrates the architecture and reference points for a digital signage system. It is divided into three main vertical sections: + +- Digital signage terminal:** On the left, this section includes physical components like Displays, HDD, and Peripherals. It houses two main client-side entities: + - Digital signage client:** Composed of Interactive device functions, Device management functions, Content processing functions, Client processing functions, and Log and report functions. Reference points R1a, R1b, and R1c connect these functions to the server. + - Content delivery client:** Composed of Content delivery client functions. Reference point R4a connects it to the server's content delivery functions. +- Digital signage service operator:** In the center, this section houses two main server-side entities: + - Digital signage server:** Composed of Client management functions, Log management functions, Schedule management functions, Content management functions, and Signage service management functions. Reference points R1a, R1b, R1c, R2a, R2b, R2c, and R2d connect these functions to the client. + - Content delivery server:** Composed of Content delivery server functions. Reference point R4a connects it to the client's content delivery functions. +- Content provider or Other business system:** On the right, this external entity connects to the Signage service management functions via reference point R5. + +Reference points are labeled as follows: R1a, R1b, R1c (between Digital signage client and Digital signage server); R2a, R2b, R2c, R2d (between Digital signage server and Content delivery server); R3a, R3b (within the Digital signage client); R4a, R4b (between Content delivery client and Content delivery server); and R5 (between Digital signage service operator and Content provider or Other business system). + +Figure 8: Reference points between related entities. The diagram shows three main entities: Digital signage terminal, Digital signage service operator, and Content provider or Other business system. The Digital signage terminal contains a Digital signage client and a Content delivery client. The Digital signage service operator contains a Digital signage server and a Content delivery server. Reference points R1a, R1b, R1c, R2a, R2b, R2c, R2d, R3a, R3b, R4a, R4b, and R5 are indicated between the client and server functions. + +Figure 8 – Reference points between related entities + +## 7.1 R1: Digital signage client and digital signage server + +Table 2 lists, for reference point R1, some of the interactions between a DS client and a DS server. + +**Table 2 – Details of reference point R1** + +| Reference point | Category | Operations | +|-----------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| R1a | Terminal registration | When a DS terminal is booted, it performs terminal registration procedures for accessing a DS server. The terminal registers its current status information after terminal authentication, if needed. | +| | Remote control of terminal | The DS server needs to control the operation of terminals such as turning off the display or speaker remotely. | +| R1b | Delivery of playlist schedules | The DS server sends playlist schedule information to each terminal. | +| R1c | Reporting of system/service maintenance information | If the terminal detects particular events, it reports the event information to the remote signage server. The report can be sent immediately or periodically, depending on the urgency of the events. In addition to system maintenance events, the terminal also reports service events such as play of content, completion of content download, etc. | + +## **7.2 R2: Digital signage server and content delivery server** + +Table 3 lists, for reference point R2, some of the interactions between a DS server and a content delivery server. + +**Table 3 – Details of reference point R2** + +| Reference point | Category | Operations | +|-----------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| R2a | Content distribution | Content is distributed from the content management functions to the content delivery server functions before sending content. | +| R2b | Request of delivery | When the DS server decides to deliver content to terminals, it requests the content delivery server to send it through the R2b reference point. | +| R2c | Scheduled delivery | When a content delivery server decides to deliver content to the terminal devices according to a content delivery schedule, the schedule is given through the R2c reference point. | +| R2d | Report of delivery | The content delivery server reports to the DS server regarding the results of content delivery. This information is managed by the DS server. | + +## **7.3 R3: Digital signage client and content delivery client** + +Table 4 lists, for reference point R3, some of the interactions between a DS client and a content delivery client. + +**Table 4 – Details of reference point R3** + +| Reference point | Category | Operations | +|-----------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| R3a | Acquiring of content | The DS client acquires content from the content delivery client. | +| | Request of content delivery | The DS client requests the content delivery client to get the content in pull mode or in P2P mode. | +| R3b | Report of content delivery | The content delivery client notifies when it finishes the reception of specified content. When all terminals try to receive specific content at the same time, it will suffer from a bottleneck problem. Hence, the DS client may specify content download schedules, based on its play schedule. Since content should be ready prior to display of content according to the schedules, time constraints for content delivery may be included. | + +## 7.4 R4: Content delivery client and content delivery server + +Table 5 lists, for reference point R4, some of the interactions between a content delivery client and the content delivery server. + +**Table 5 – Details of reference point R4** + +| Reference point | Category | Operations | +|-----------------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| R4a | Delivery of content delivery schedule | The content delivery server sends a content delivery schedule to the client. This operation can be requested by the server and the client. | +| | Delivery of content | Content is delivered from the content delivery server to the client according to the content delivery schedule. The content is delivered to the client through push/pull/P2P methods. | +| | Report of content delivery | When the client finishes receiving content, it reports the results of content delivery to the server. This information can be reported immediately or can be reported periodically. | +| R4b | Sharing of content | In P2P mode, the content is delivered from a P2P peer to other P2P peers according to the content delivery schedule. | + +## 7.5 R5: Digital signage server and content provider + +In reference R5, the DS server and a content provider interact with each other to selecting time slots for content display and/or target terminals for content delivery, registering content, etc. The details of reference point R5 are out of the scope of this Recommendation. + +# 8 Information flows + +This clause describes generic information flows for providing DS services. + +## 8.1 Configuration of terminal devices + +This method is effective when a DS server gives configuration of DS terminal devices. For example, if a terminal with a speaker is installed in a restricted area where it should not make noise, the signage server can give appropriate terminal behaviour configuration. This flow assumes that the terminal has been already enrolled by a DS operator. + +When the DS terminal boots up, its configuration parameters should be set from the DS server. See Figure 9. + +NOTE – There may be other configuration procedures. Procedures regarding authentication and authorization in DS services are for further study. + +![Sequence diagram illustrating terminal configuration procedures between a Digital signage client and a Digital signage server.](5a1abd59a95fa47ae192807de151e9eb_img.jpg) + +The diagram shows the interaction between a Digital signage client and a Digital signage server. The client contains two functional blocks: 'Device management functions' and 'Client processing functions'. The server contains a 'Client management functions' block. The sequence of interactions is as follows: 1. An arrow labeled '1. Get device status' points from the 'Device management functions' to the 'Client processing functions' within the client. 2. An arrow labeled '2. Request configuration' points from the 'Client processing functions' to the 'Client management functions' on the server. 3. An arrow labeled '3. Set configuration' points from the 'Client management functions' back to the 'Client processing functions' on the client. The diagram is labeled H.781(15)\_F09 in the bottom right corner. + +Sequence diagram illustrating terminal configuration procedures between a Digital signage client and a Digital signage server. + +**Figure 9 – Terminal configuration procedures** + +1. When a DS client application has been launched, client processing functions may initially probe device status from the device management functions of the DS client. +2. Client processing functions of the DS client interact with the client management functions of the DS server in order to register the terminal device. When client processing functions request configuration, the following information may be sent to the server: + - terminal device information (e.g., terminal ID, IP address); + - terminal device status information (e.g., hardware/software errors); + - auxiliary device information (e.g., types of attached external devices); + - venue information (e.g., the address of an installation place); + - client pre-configuration information. +3. Client management functions of the DS server check validation and authentication whether or not the terminal is authorized to access this server. If it is not authorized yet, it returns a failure message. When the authentication procedure finishes, client management functions send configuration to the terminal. The configuration may include, *inter alia*, the following information: + - content delivery server information; + - location of playlist schedule; + - reporting frequency, types of events to be reported, address of a log server when using distributed log servers, etc. + +## 8.2 Play of content and its report + +This clause applies to the case where DS systems are capable of handling logs. When a DS terminal device plays content according to a play schedule, the terminal device may report the play results to the DS server. These records can be used to confirm whether content has been played successfully. + +### 8.2.1 Reporting play log + +When the DS terminal plays content according to the play schedule, it reports the play result to the DS server in the form of a play log. This play log will be used to confirm whether the content has been played successfully. It is possible to display multiple contents simultaneously within a single display. In other words, a single layout can contain multiple contents. In this case, multiple play logs + +will be generated (since a play log records events for one content). This flow shows a procedure for logging a single content being played, and multiple logs will be generated if multiple contents are displayed simultaneously. See Figure 10. + +![Sequence diagram for reporting play logs (Figure 10).](043e64d41a3368d138ace3816fd26469_img.jpg) + +The diagram illustrates the interaction between a Digital signage client and a Digital signage server for reporting play logs. The client contains two internal components: Content processing functions and Log and report functions. The server contains Log and report management. The sequence of messages is as follows: 1. Play start notification from Content processing functions to Log and report functions; 2. Play end notification from Content processing functions to Log and report functions; 3. Report play log from Log and report functions to Log and report management on the server. The diagram is labeled H.781(15)\_F10. + +Sequence diagram for reporting play logs (Figure 10). + +**Figure 10 – Procedures for reporting play logs** + +1. Content processing functions (e.g., CntPly FE) notify log and report functions when a specific content starts to play. If content processing functions fail to play the specific content, it also logs the event. +2. When the play of the content has finished, content processing functions notify log and report functions. +3. Log and report functions generate play log information and send it to log and report management functions of the DS server. + - In general, if the play log event is not an urgent event, the DS terminal may not report the logged event immediately, instead, the terminal temporarily accumulates the log messages and sends the aggregated reports to the server on a pre-defined schedule. + +### 8.2.2 Reporting play log with device status + +It is possible to use external devices, such as a small camera, in front of a display for assuring PoP and status of the display. For example, a monitor blackout problem during content play can be detected by using such devices. Even though there is no external device that detects the status of the monitor, content providers may want to know the history of specific device status while their content is being played if it uses specific features such as user interaction using auxiliary devices like a touch panel. See Figure 11 on procedures for reporting a play log with device status. + +![Sequence diagram for reporting play log with device status (Figure 11).](088921fa3f5a44c8551815122517eefd_img.jpg) + +The diagram illustrates the interaction between a Digital signage client and a Digital signage server for reporting play logs with device status. The client contains three internal components: Device management functions, Content processing functions, and Log and report functions. The server contains Log and report management. The sequence of messages is as follows: 1. Play start notification from Content processing functions to Log and report functions; 2. Fetch device status from Device management functions to Content processing functions; 3. Play end notification from Content processing functions to Log and report functions; 4. Report play log with device status from Log and report functions to Log and report management on the server. The diagram is labeled H.781(15)\_F11. + +Sequence diagram for reporting play log with device status (Figure 11). + +**Figure 11 – Procedures for reporting play log with device status** + +1. Content processing functions notify the log and report functions when specific content starts to play. If it fails to play specific content, it also logs the event. +2. Content processing functions fetch the current status of a specific device, such as a specialized camera for observing the pattern of electronic display. +3. When the content finishes playing, the content processing functions notify the event to the log and report functions. +4. Log and report functions generate play-log information that includes device status information and sends it to the log and report management functions of the DS server. + +### 8.2.3 Reporting confidential play log for PoP + +There is a case where a content owner requests confidential records as PoP (see clause 6.2.5.1). In this case, the content owner may request more reliable proof than a simple play log to confirm that the content has actually been played. DS services can use digital signatures in the play log to provide PoP. + +As an assumption, the content owner has already registered its digital signature and preferences that contain formats of log messages for the play of content. This registration process is made during the content registration procedure as requested by the content owner. See Figure 12. + +![Sequence diagram illustrating the procedures for reporting play log with confidentiality. The diagram shows interactions between a Security client, a Digital signage client, a Digital signage server, and a Content owner. The Digital signage client contains 'Content processing functions' and 'Log and report functions'. The Digital signage server contains 'Log and report management'. The sequence of messages is: 1. Play start notification from Content processing functions to Log and report functions; 2. Play end notification from Content processing functions to Log and report functions; 3. Get certification/preference from Log and report functions to Content processing functions; 4. Certify play log from Log and report functions to Security client; 5. Report certified play log from Log and report functions to Log and report management; 6. Send aggregated play logs from Log and report management to Content owner.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +``` + +sequenceDiagram + participant Security client + subgraph Digital signage client + direction TB + C[Content processing functions] + L[Log and report functions] + end + subgraph Digital signage server + direction TB + M[Log and report management] + end + participant Content owner + + C->>L: 1. Play start notification + C->>L: 2. Play end notification + L->>C: 3. Get certification/preference + L->>Security client: 4. Certify play log + L->>M: 5. Report certified play log + M-->>Content owner: 6. Send aggregated play logs + +``` + +H.781(15)\_F12 + +Sequence diagram illustrating the procedures for reporting play log with confidentiality. The diagram shows interactions between a Security client, a Digital signage client, a Digital signage server, and a Content owner. The Digital signage client contains 'Content processing functions' and 'Log and report functions'. The Digital signage server contains 'Log and report management'. The sequence of messages is: 1. Play start notification from Content processing functions to Log and report functions; 2. Play end notification from Content processing functions to Log and report functions; 3. Get certification/preference from Log and report functions to Content processing functions; 4. Certify play log from Log and report functions to Security client; 5. Report certified play log from Log and report functions to Log and report management; 6. Send aggregated play logs from Log and report management to Content owner. + +**Figure 12 – Procedures for reporting play log with confidentiality** + +1. Content processing functions notify the log and report functions when specific content starts to play. If it fails to play the specific content, it logs the event. +2. Content processing functions fetch the current status of a specific device such as a specialized camera for observing the pattern of electronic display. +3. Log and report functions retrieve certifications such as a digital signature and preferences that include format of log messages for the content being played. + - If there is no preference for the content, log and report functions generate log messages based on a default format that is pre-defined by the service provider. If the digital signature for the content is not assigned, it will skip the remaining procedures, and sends a log message to the DS server. +4. Log and report functions request a security client to certify the play log record with the digital signature of the content. This certification is used for PoP. + - It is also possible to encrypt the play log record for security reasons by using the digital signature. + +5. Log and report functions send the play log with the PoP to the DS server and/or directly to the content owner. + - When sending play logs directly to the content owner, the content owner has the capability to receive them, even if at a high frequency. +6. Log and report management functions of the DS server send the aggregated play logs to the content owner. + +## 8.3 Display of alerting information + +This clause applies when common alerting features are implemented. + +Since a DS service offers rich information in an open area by which many people pass, DS can play a crucial role in providing alerting services. In general, it is useful to provide multimedia-based alerting information through DS terminal devices. It is assumed that a common alerting server has already received an alert from an alert agency, and the alert contains the affected area information. Figure 13 shows the procedures of a common alerting service. + +![Sequence diagram illustrating the procedures for display of alerting information. The diagram shows interactions between a Digital signage client (containing Device management functions and Content processing functions), a Common alerting (CA) client, a Digital signage server operator (containing Client management functions), and a Common alerting (CA) server. The sequence of messages is: 1. Request terminal list of affected area (CA server to Operator), 2. Terminal list of affected area (Operator to CA server), 3. Common alerting message (CA server to CA client), 4. Request display of alerting information (CA client to Content processing functions), 5. Play alerting information (Content processing functions to Device management functions), 6. Additional alerting information (TTS, Sign Language, ...) (Content processing functions to CA client), 7. Control device (speaker, ...) (Content processing functions to Device management functions), 8. Play additional alerting information (Content processing functions to Device management functions).](474a819357587e34949a3e110ff19b30_img.jpg) + +``` + +sequenceDiagram + participant CA_server as Common alerting (CA) server + participant Operator as Digital signage server operator + participant CA_client as Common alerting (CA) client + subgraph DS_client [Digital signage client] + direction TB + DMF[Device management functions] + CPF1[Content processing functions] + CPF2[Content processing functions] + end + + Note right of Operator: Client management functions + Note right of CPF1: Content processing functions + + CA_server-->>Operator: 1. Request terminal list of affected area + Operator-->>CA_server: 2. Terminal list of affected area + CA_server->>CA_client: 3. Common alerting message + CA_client->>CPF2: 4. Request display of alerting information + CPF2->>DMF: 5. Play alerting information + CPF2-->>CA_client: 6. Additional alerting information (TTS, Sign Language, ...) + CPF2->>DMF: 7. Control device (speaker, ...) + CPF2->>DMF: 8. Play additional alerting information + +``` + +H.781(15)\_F13 + +Sequence diagram illustrating the procedures for display of alerting information. The diagram shows interactions between a Digital signage client (containing Device management functions and Content processing functions), a Common alerting (CA) client, a Digital signage server operator (containing Client management functions), and a Common alerting (CA) server. The sequence of messages is: 1. Request terminal list of affected area (CA server to Operator), 2. Terminal list of affected area (Operator to CA server), 3. Common alerting message (CA server to CA client), 4. Request display of alerting information (CA client to Content processing functions), 5. Play alerting information (Content processing functions to Device management functions), 6. Additional alerting information (TTS, Sign Language, ...) (Content processing functions to CA client), 7. Control device (speaker, ...) (Content processing functions to Device management functions), 8. Play additional alerting information (Content processing functions to Device management functions). + +**Figure 13 – Procedures for display of alerting information** + +1. The common alerting server may request a terminal list of the affected area to client management functions of the DS server which manage locations of DS terminals. +2. Client management functions may send the terminal list of the affected area based on step 1. +3. The common alerting server creates a common alerting message and sends it to the common alerting (CA) clients pertaining to DS terminals. + - The common alerting client can select the display mode, such as sole screen, screen division and screen overlay, according to the type and class of alert. +4. The common alerting client requests display of alerting information to the client processing functions of the DS client. + - The common alerting client can provide the pre-arranged emergency exit route information on how to evacuate according to the type and class of alert. If emergency exit route information is provided, the common alerting client uses emergency exit route information with the alerting message. + +- The common alerting client can change play schedules according to the type and class of alert by interacting with the DS client. It requests the change of play schedules to the client processing functions of the DS client. +5. Client processing functions request to display the alert information to the content processing functions. + 6. The common alerting client can convert alerting information into audio or sign language format for universal design presentations by interacting with the DS client. + - If the content processing functions of the DS client have a universal design presentation functionality, the common alerting client can request the conversion of alerting information to the content processing functions. + 7. The common alerting client can control the devices according to the type and class of common alert information by interacting with the DS client. + - The common alerting client can request control of a connected device to the device management functions of the DS client. For example, it can increase the volume of a speaker with a siren. + 8. Client processing functions request to display the additional alerting information such as text-to-speech (TTS) and sign language to content processing functions. + +## 8.4 Interactive services + +A DS system can control interactive devices connected to the DS client. Figure 14 shows the basic flow for interactive services. + +![Figure 14 – Interactive services. A sequence diagram showing the interaction between a User/audience, an Interactive Device, a Digital signage client, and an AM client. The Digital signage client contains Interactive device functions and Client processing functions. The Interactive Device includes icons for Sensor, Micro, Camera, Cam, Keyboard, and Touch panel. The sequence of messages is: 1. Register event (from Client processing functions to Interactive device functions), 2. User interaction (from User/audience to Interactive Device), 3. Event information (from Interactive Device to Interactive device functions), 4. Event notification (from Interactive device functions to Client processing functions and AM client).](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant User/audience + participant Interactive Device + subgraph Digital signage client + participant ID as Interactive device functions + participant CP as Client processing functions + end + participant AM client + + Note right of Interactive Device: Sensor, Micro, Camera, Cam, Keyboard, Touch panel + + CP->>ID: 1. Register event + User/audience->>Interactive Device: 2. User interaction + Interactive Device->>ID: 3. Event information + ID->>CP: 4. Event notification + ID->>AM client: 4. Event notification + +``` + +Figure 14 – Interactive services. A sequence diagram showing the interaction between a User/audience, an Interactive Device, a Digital signage client, and an AM client. The Digital signage client contains Interactive device functions and Client processing functions. The Interactive Device includes icons for Sensor, Micro, Camera, Cam, Keyboard, and Touch panel. The sequence of messages is: 1. Register event (from Client processing functions to Interactive device functions), 2. User interaction (from User/audience to Interactive Device), 3. Event information (from Interactive Device to Interactive device functions), 4. Event notification (from Interactive device functions to Client processing functions and AM client). + +**Figure 14 – Interactive services** + +The content displayed by the DS client may request specific events from interactive devices. For example, content may request an audience to select a service item from a certain menu by using a DS touch screen. Based on the user selection, the content or the playlist that is being displayed can be changed. + +1. Client processing functions request interactive device functions to be notified of particular events with the registered event messages. The events can be registered for each auxiliary device. + +- Other functions such as AM client functions can request to be notified for a particular event with the event registration message. The event can be registered with an auxiliary device. + +NOTE – If different services register the same event, the type of notification can be identical or different, depending upon implementation. + +2. An audience performs some actions to the interactive device to cause events. +3. Upon occurrence of events, interactive device functions receive event notifications from interactive devices. + +Interactive device functions convert raw data to the specified event message. + +- The functions check the list of event requesters which are interested in the received events. If there is no requester that is interested in that particular event, the event message is ignored. + +4. Interactive device functions notify the requester of the events with interactive devices. A single event can be notified to more than one requester. + - Optionally, new content or a new playlist schedule can be displayed afterwards. + +## 8.5 Content delivery + +This clause provides information flows for delivering content from the DS service provider to DS terminal devices. When the DS server constructs a content delivery schedule, the schedule may include varied information that would be used for content delivery, such as content information, content identifier, content delivery method and schedule, alternative content server and additional requirements regarding the delivery procedures. Content will be delivered according to the content delivery schedule. + +### 8.5.1 Push-based content delivery + +Figure 15 shows flows for delivering specific content to DS terminals by use of a push-type delivery method. If the content delivery client is always ready to receive content from a pre-specified content delivery server, step 3 may be omitted. + +![Sequence diagram illustrating the push-type content delivery method between a Content delivery client, a Content delivery server, and a Digital signage server.](f64e1e0997695248c0cd4122c5b1a170_img.jpg) + +``` + +sequenceDiagram + participant DSS as Digital signage server + participant CDS as Content delivery server + participant CDC as Content delivery client + Note right of DSS: Schedule management functions + Note right of CDS: Content delivery server functions + Note right of CDC: Content delivery client functions + Note right of DSS: Log management functions + DSS->>CDS: 1. Content delivery request + CDS-->>CDC: 2. Content delivery schedule + CDC-->>CDS: 3. Ready to receive content + CDS->>CDC: 4. Deliver (push) content + CDC-->>CDS: 5. Content reception notification + CDS->>DSS: 6. Content delivery completion notification + +``` + +The diagram shows the interaction between three main entities: Content delivery client, Content delivery server, and Digital signage server. The Digital signage server contains Schedule management functions and Log management functions. The Content delivery server contains Content delivery server functions. The Content delivery client contains Content delivery client functions. The sequence of messages is: 1. Content delivery request from Schedule management functions to Content delivery server functions; 2. Content delivery schedule from Content delivery server functions to Content delivery client functions; 3. Ready to receive content from Content delivery client functions to Content delivery server functions; 4. Deliver (push) content from Content delivery server functions to Content delivery client functions; 5. Content reception notification from Content delivery client functions to Content delivery server functions; 6. Content delivery completion notification from Content delivery server functions to Log management functions. The diagram is labeled H.781(15)\_F15. + +Sequence diagram illustrating the push-type content delivery method between a Content delivery client, a Content delivery server, and a Digital signage server. + +**Figure 15 – Content delivery through push-type delivery method** + +1. Schedule management functions of the DS server request the content delivery server to send specific content to DS terminals. +2. Content delivery server functions of the content delivery server may send content delivery schedules that may describe a delivery method for specific content. + +3. When it is ready, content delivery client functions may notify the content delivery server based on step 2. +4. Content delivery server functions send the content to the content delivery client functions. +5. Content delivery client functions send a content reception notification. +6. Content delivery server functions send the notification to log management functions of the DS server. + +### 8.5.2 Pull-based content delivery + +Figure 16 shows flows for delivering specific content to the DS terminals by use of pull-type delivery method. + +![Sequence diagram for pull-type content delivery. The diagram shows three main entities: Content delivery client, Content delivery server, and Digital signage server. The client contains 'Content delivery client functions' and two cases: 'Case 1' and 'Case 2'. The server contains 'Content delivery server functions'. The Digital signage server contains 'Schedule management functions', 'Client management functions', and 'Log management functions'. The sequence of messages is: 1. Content delivery request from Schedule management functions to Content delivery server functions; 2. Content delivery schedule from Content delivery server functions to Case 1; 2. Configuration setting from Content delivery server functions to Case 2; 3. Request content from Case 2 to Content delivery server functions; 4. Deliver (pull) content from Content delivery server functions to Case 2; 5. Content reception notification from Case 2 to Content delivery server functions; 6. Content delivery completion notification from Content delivery server functions to Log management functions. The label H.781(15)_F16 is at the bottom right.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Sequence diagram for pull-type content delivery. The diagram shows three main entities: Content delivery client, Content delivery server, and Digital signage server. The client contains 'Content delivery client functions' and two cases: 'Case 1' and 'Case 2'. The server contains 'Content delivery server functions'. The Digital signage server contains 'Schedule management functions', 'Client management functions', and 'Log management functions'. The sequence of messages is: 1. Content delivery request from Schedule management functions to Content delivery server functions; 2. Content delivery schedule from Content delivery server functions to Case 1; 2. Configuration setting from Content delivery server functions to Case 2; 3. Request content from Case 2 to Content delivery server functions; 4. Deliver (pull) content from Content delivery server functions to Case 2; 5. Content reception notification from Case 2 to Content delivery server functions; 6. Content delivery completion notification from Content delivery server functions to Log management functions. The label H.781(15)\_F16 is at the bottom right. + +**Figure 16 – Content delivery through pull-type delivery method** + +1. Schedule management functions of the DS server request the content delivery server to send specific content to DS terminals. + +NOTE – When a massive number of clients tries to receive content at the same time, the server is likely to suffer from a bottleneck problem. This will lead to performance degradation. Hence, a specific delivery schedule is needed for each client in the content delivery schedule. + +2. *Case 1*: Content delivery server functions send the content delivery schedule to content delivery client functions of content delivery clients. +3. *Case 2*: When using periodic polling for acquiring content (i.e., the continuous checking with the content delivery server for the content that it has), polling schedules for the client devices are set as configuration data in the manner described in clause 8.1. +4. Content delivery client functions send a request for specific content according to the content delivery schedule. +5. Content delivery server functions send the requested content. +6. When they complete content delivery, content delivery client functions send a content delivery completion notification. +7. Content delivery server functions send the notification to the log management functions of the DS server. + +### 8.5.3 P2P-based content delivery + +This Recommendation assumes that the P2P delivery method is implemented with either a push or pull delivery method. Figure 16 shows flows for delivering specific content to a DS terminal by use + +of a P2P-type delivery method. Since it is difficult to strictly guarantee timed delivery when using a P2P network, the content delivery schedule for a P2P-based delivery method embeds alternative server addresses that are ready to transfer the content with pull-based or push-based delivery as a backup plan. The flow for content delivery using the P2P-based delivery method is illustrated in Figure 17. + +![Sequence diagram illustrating content delivery through a P2P-based delivery method. The diagram shows four main entities: Content delivery client (B), Content delivery client (A), Content delivery server, and Digital signage server. The process starts with the Digital signage server's Schedule management functions sending a '1. Content delivery request' to the Content delivery server's functions. The server responds with '2. Content delivery schedule', '3. Request peer list', and '4. Buffermap negotiation' to Client A. Client A then initiates '4. Buffermap negotiation' with Client B. A loop labeled 'Repeat' involves Client A sending '5. Chunk request' to Client B, who responds with '6. Chunk data'. Client A also sends '5. Chunk request' and receives '6. Chunk data' from the Content delivery server. Once complete, Client A sends '7. Content reception notification' to the server, which includes 'Case 1. Complete' or 'Case 2. Timeout'. Finally, the server sends '8. Content delivery completion notification' to the Digital signage server's Log management functions.](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +Sequence diagram illustrating content delivery through a P2P-based delivery method. The diagram shows four main entities: Content delivery client (B), Content delivery client (A), Content delivery server, and Digital signage server. The process starts with the Digital signage server's Schedule management functions sending a '1. Content delivery request' to the Content delivery server's functions. The server responds with '2. Content delivery schedule', '3. Request peer list', and '4. Buffermap negotiation' to Client A. Client A then initiates '4. Buffermap negotiation' with Client B. A loop labeled 'Repeat' involves Client A sending '5. Chunk request' to Client B, who responds with '6. Chunk data'. Client A also sends '5. Chunk request' and receives '6. Chunk data' from the Content delivery server. Once complete, Client A sends '7. Content reception notification' to the server, which includes 'Case 1. Complete' or 'Case 2. Timeout'. Finally, the server sends '8. Content delivery completion notification' to the Digital signage server's Log management functions. + +H.781(15)\_F17 + +**Figure 17 – Content delivery through P2P-based delivery method** + +1. Schedule management functions of the DS server request the content delivery server to deliver specific content to DS terminals with a P2P-based delivery method. Content delivery schedule information, such as overlay network identifier, size of chunk, deadline of content delivery, alternative content server information, etc., is used for P2P delivery. +2. Content delivery server functions send the content delivery schedule to the content delivery client functions. +3. Content delivery client functions request the addresses of other clients. +4. Content delivery client functions connect simultaneously to other content delivery client functions, and exchange buffer maps that show the availability of specific chunks of data across the peers in the P2P network. +5. If another client including a server-side peer has a chunk that this client does not have, this client requests another client to deliver the chunk. +6. Content delivery client functions receive the requested chunk from another client and repeat steps 4 to 7 until all whole chunks are received. +7. *Case 1:* When it completes the delivery, the client notifies the content delivery server functions of the content reception. +*Case 2:* When it does not complete the delivery within the defined time limit, it initiates the alternative delivery procedures that are depicted in Figure 14 or Figure 15. +8. Content delivery server functions send a content delivery completion notification to the log management functions of the DS server. + +# Bibliography + +- [b-ITU-T H.760] Recommendation ITU-T H.760 (2009), *Overview of multimedia application frameworks for IPTV services.* +- [b-ITU-T X.1161] Recommendation ITU-T X.1161 (2008), *Framework for secure peer-to-peer communications.* +- [b-ITU-T X.1162] Recommendation ITU-T X.1162 (2008), *Security architecture and operations for peer-to-peer networks.* +- [b-ITU-T Y.2206] Recommendation ITU-T Y.2206 (2010), *Requirements for distributed service networking capabilities.* +- [b-ITU-T HSTP.DS-UCIS] Technical Paper ITU-T HSTP.DS-UCIS (2014), *Digital signage: Use-cases of interactive services.* +- [b-ISO/IEC TR 20002] ISO/IEC TR 20002 (2012), *Information technology – Telecommunications and information exchange between systems – Managed P2P: Framework.* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec9025fad3017c7605ba86c027627f3393eb70d4 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf74b464a3f609f8020a6cce3fcef4832a060e90b6c74730f8da33a2fb74db1e +size 64740 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d74964a58c8f92f3d01e9a2d36202924fbf9d751 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f386e97f51f6d5c5f387ef76c885e30d314d40b5cd4c0ff438d42b20ba669c7c +size 94940 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75d94934f56b0fa00cd4c2f60e711322233d0ed7 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bd02cbddf20bdfe0cc6cc66324cecc5680eb7d7797dbd7185a607bee81c34e1 +size 75109 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfdf01d5e5b0023b8dd6876f09a58ddecdd89189 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9ad2f8386288738fc0d8c9fd557f097a8798c70f4233628e3ed4225849b0e30 +size 23909 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a53075130703e4a914f05f2d7419cf1062040d0b --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33044d669379c02bd07e8aa74af809ec99717d8b15fa5b0569c6bde206a7090d +size 93029 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9484f7a4ec97fa7b18d87573f2c04c902a78a2c --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3be73d5340ac46c9b75c3b7ca16cbb88f8ee1d16e8fd492f4c7dcbca0a80c908 +size 25553 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/327ba94498e3381cf08eb41e3fd3d77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96233075ca5b6e97ca864d9f31fec2547184d171 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/327ba94498e3381cf08eb41e3fd3d77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f23bd97440835fe536ead817bec25a1a8e77f07558e2a3f878302d94b1d0cfb6 +size 13930 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cfab0f078e01098fce8ad52cc452d3b14e275f0 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc5cb2f2c69b65b3e324ad52700e76f7ab9703f242b48a5b53bcfa0880b3aa87 +size 82783 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/3b00a61116faef21d3a6009fd350b46a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9054943fa89a16b74d2f6d38a996fab2b364d7e7 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/3b00a61116faef21d3a6009fd350b46a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d1b5d486e9c4fe74c34a7a7efee1e32a40e9c63dd17f7814031e57b46a7312a +size 72829 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08e6922b6f7ec458b4ba79a19fcdeca3a4b4dea7 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:007dc882e686ec1086d9df734200514d371caf3d1fb683dc8836ab8aafe52523 +size 67406 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..149504f2ae914901df07b0ff37d167f13f1147a5 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e875e6cc7189a1d1d4251f5f0ee5d9a895b10248924e0dc717e4473efb0e05ca +size 86964 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4900dfb3695d071d41e81253a09296ef883ae61 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31004b85b8a16591fe25ba242451161dcaadda847832d65def438c6c7ac61c08 +size 13442 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed799ed8e8ab524b98dc87f363f386563d5aaa1e --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d88b17d380448b4e8292ee3324f96c143452504e6f140e51648304580f2a614b +size 79790 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cd960aec6eb3fe687696fc5229777d9dc1b9975 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea0c6acb09ee5608ae94a1be2f9cbbd0452cab3e8df83a52d63d8b3e30426cc0 +size 73400 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83ff869c84cb142bcd39b6c18804414f31c628de --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42db7896215e459bf2d12e3e3352913e979e999bb64dd3395ef6139e870a2227 +size 53566 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b60d15f5460f02ef3d4ee6ef6501acda694ddcc --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ef1f64d17bb5d756c6f90bba85469771b2330821d843a6edb12c3157bdd318a +size 13259 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..638036a0d39efeb77b55cd059c9d11030184c503 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19f75da790f916212eae20c01c2c180908782ee7128b568833b1ff4d7ad7890d +size 31863 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/94fd137860c16c8dfd75512f10161fe8_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/94fd137860c16c8dfd75512f10161fe8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea06d0e3c8a4f2c3b8a66f9c4bdaaef614bf0eb3 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/94fd137860c16c8dfd75512f10161fe8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69d32497d37fa8b6a413df69d086a6c0e17e75bb17dfb3ab3294418043b0bb00 +size 56792 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/a7585024ebe2bba8ac0757150a12759a_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/a7585024ebe2bba8ac0757150a12759a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b4a8cc57c2c8a414862415b3a377d7d89c0b061 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/a7585024ebe2bba8ac0757150a12759a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b09191d60b6b122f0957ea5a39e2a4b858306367687174e527eb052b672b1590 +size 48571 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f90b57fee92792bdaec59bf78183495125eb765 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3df274610228c1607b7789c075aa34431f7c458b354dea0df484e658e5cb979e +size 151035 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/d29cfbf30a471dc06a78be27f86bd1cf_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/d29cfbf30a471dc06a78be27f86bd1cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c47b0e0d3ce04839fe3940f7427fb5204b5ae2a --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/d29cfbf30a471dc06a78be27f86bd1cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5b44be6f7550410b350facdad1907c3fa60fe612297df803425f9431f87e808 +size 3404 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/H/T-REC-H.783-201905-I_PDF-E/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1842bb9c7631ca4c7b48bac0da5df899888317db --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a679372076631ccef3ee3008e3ee5d5b9d8156ee0e0772ad39b0cbd76918a4ea +size 29496 diff --git a/marked/H/T-REC-H.783-201905-I_PDF-E/raw.md b/marked/H/T-REC-H.783-201905-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f8df1a17ed9e0122dbac0c1e3701563f6e2cf8a7 --- /dev/null +++ b/marked/H/T-REC-H.783-201905-I_PDF-E/raw.md @@ -0,0 +1,1694 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.783** + +(05/2019) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +Digital Signage + +--- + +**Digital signage: Audience measurement +services** + +Recommendation ITU-T H.783 + +ITU-T + +![ITU logo: International Telecommunication Union](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a stylized globe with a red lightning bolt striking across it. The letters "ITU" are prominently displayed in blue, with the full name "International Telecommunication Union" written in smaller blue text to the right. + +ITU logo: International Telecommunication Union + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T H.783 + +# Digital signage: Audience measurement services + +## Summary + +Recommendation ITU-T H.783 describes functional requirements, configuration and operations, and metadata on audience measurement for digital signage services between audience measurement client and audience measurement aggregation. + +Version 2 of this Recommendation adds the extensible markup language (XML) schema on the data structures for message delivery. The addition aims to widen applicability of the specifications at the price of easy XML validation. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.783 | 2018-08-29 | 16 | 11.1002/1000/13692 | +| 2.0 | ITU-T H.783 (V2) | 2019-05-14 | 16 | 11.1002/1000/13908 | + +## Keywords + +Audience measurement, digital signage, metadata. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +### INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2019 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|------------|-----------------------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 3 | +| 6 | Overview of audience measurement of digital signage services ..... | 5 | +| 6.1 | Introduction ..... | 5 | +| 6.2 | Functional blocks related to audience measurement..... | 8 | +| 6.3 | Considerations ..... | 8 | +| 7 | Functional requirements ..... | 9 | +| 7.1 | General requirements..... | 9 | +| 7.2 | Requirements for audience measurement architecture..... | 9 | +| 7.3 | Requirements for interfaces between AM aggregation and stakeholder/DS application ..... | 10 | +| 7.4 | Requirements for controlling AM clients..... | 10 | +| 7.5 | Requirements for interface between AM aggregation and AM clients ..... | 11 | +| 7.6 | Requirements for privacy protection ..... | 11 | +| 8 | Configuration and operations to provide audience measurement data ..... | 13 | +| 8.1 | Configuration for audience measurement data..... | 13 | +| 8.2 | Measurement report request for audience measurement data ..... | 13 | +| 8.3 | Measurement report for audience measurement data ..... | 13 | +| 9 | Metadata to provide audience measurement data ..... | 14 | +| 9.1 | Metadata for audience information ..... | 14 | +| 9.2 | Metadata for environmental information..... | 16 | +| 9.3 | Metadata for configuration information ..... | 16 | +| 9.4 | Metadata for measurement report request information ..... | 21 | +| 9.5 | Metadata for measurement report package information..... | 21 | +| 9.6 | Metadata for measurement report information..... | 22 | +| Annex A | – XML schema on the data structures for message delivery..... | 24 | +| A.1 | Schematic representation of XML schema..... | 24 | +| A.2 | XML schema ..... | 28 | +| Appendix I | – Use cases of digital signage services with audience measurement functionality..... | 37 | +| I.1 | Audience measurement without user interaction from the public users..... | 37 | +| I.2 | Audience measurement with user interaction from the active users ..... | 38 | + +| | Page | +|------------------------------------------------------------------------------------------|------| +| I.3 Audience measurement based on ambient information from digital signage terminal..... | 39 | +| Bibliography..... | 41 | + +# Digital signage: Audience measurement services + +# 1 Scope + +This Recommendation describes functional requirements, configuration and operations, and metadata on audience measurement (AM) for digital signage (DS) services between audience measurement client and audience measurement aggregation. + +This version adds the extensible markup language (XML) schema on the data structures for message delivery between AM client and AM aggregation. The addition aims to widen applicability of the specifications for digital signage audience measurement services through easy XML validation. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.741.0] Recommendation ITU-T H.741.0 (2012), *IPTV application event handling: Overall aspects of audience measurement for IPTV services.* +- [ITU-T H.741.2] Recommendation ITU-T H.741.2 (2012), *IPTV application event handling: Data structures of audience measurement for IPTV services.* +- [ITU-T H.780] Recommendation ITU-T H.780 (2012), *Digital Signage: Service requirements and IPTV-based architecture.* +- [ITU-T H.781] Recommendation ITU-T H.781 (2015), *Digital Signage: Functional architecture.* +- [ITU-T H.782] Recommendation ITU-T H.782 (2018), *Digital Signage: Metadata.* +- [ISO 19136] ISO 19136 (2007), *Geographic information -- Geography Markup Language (GML).* +- [ISO/IEC 8802-11] ISO/IEC 8802-11: 2018, *Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements – Part 11: Wireless LAN medium access control (MAC) and physical layer (PHY) specifications.* +- [IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifier (URI): Generic Syntax.* +- [IETF RFC 5139] IETF RFC 5139 (2008), *Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO).* +- [W3C XMLSchema] W3C Recommendation (2004), *XML Schema Part 2: Datatypes Second Edition.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 audience measurement service provider** [ITU-T H.741.0]: A service provider providing audience measurement services. An audience measurement service provider configures an audience measurement system to control what audience information the system collects. + +**3.1.2 content** [ITU-T H.780]: A combination of audio, still image, graphic, video, or data. + +NOTE – Variety of formats is classified as the "data" (e.g., text, encoded values, multimedia description language like HTML) + +**3.1.3 digital signage (DS)** [ITU-T H.780]: A system that sends information, advertising and other messages to electronic devices (e.g., displays, speakers) in accordance with the time of day and the location of the display, or the actions of audience. Contents and their relevant information such as display schedules are delivered over networks. + +**3.1.4 identification** [b-ITU-T X.1252]: The process of recognizing an entity by contextual characteristics. + +**3.1.5 personally identifiable information (PII)** [b-ITU-T X.1252]: Any information a) that identifies or can be used to identify, contact, or locate the person to whom such information pertains; b) from which identification or contact information of an individual person can be derived; or c) that is or can be linked to a natural person directly or indirectly. + +NOTE – In general, this information contains identifiers such as user's name, social identification number, device id, phone number, RFID codes and so on. + +**3.1.6 playlist** [ITU-T H.780]: Composed of a list of contents. + +NOTE 1 – This data is created and provided by digital service providers. + +NOTE 2 – This data can be selected by an end-user when interactivity is supported in a digital signage terminal device. + +NOTE 3 – This data may indicate an order of playing contents. + +**3.1.7 playlist schedule** [ITU-T H.780]: Composed a list of playlists indicated by specific play date and/or time. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 active audience:** Audience interacting with terminal devices. + +**3.2.2 audience:** Listeners or viewers engaging in multimedia services. + +**3.2.3 audience information:** The overall information about audience behaviour, and the related information, during the time that audience measurement is in active. + +**3.2.4 audience measurement:** The measurement of audience within digital signage services. + +**3.2.5 audience measurement aggregation:** The functions that configures audience measurement client, receive audience measurement data from it. + +**3.2.6 audience measurement client:** The functions that sends audience measurement data to audience measurement aggregation functions. + +**3.2.7 audience measurement data:** Audience behaviour data which is related to a service and contents consumption, combined or not with audience information. Audience measurement data is a result from the audience measurement client delivered to the audience measurement aggregation. The data includes results from the audience measurement metric, ambient information of the terminal, etc. + +- 3.2.8 audience measurement metric:** A set of information that is extracted through analysis of the raw audience data (e.g., the number of audience, gender, rough ages). +- 3.2.9 audience measurement report:** A report from the audience measurement aggregation to the stakeholder or other applications that represents the effect of advertising contents and characteristics of the venue of the terminal installed with statistical analysis on the series of audience measurement data. +- 3.2.10 audience measurement system:** The system which captures audience raw data, extracts audience measurement metrics and analyse for making audience measurement report on audience behaviour by detecting application events and using raw data from input devices such as camera, microphone, sensor devices and so on within the service. +- 3.2.11 location owner:** A person or organization that owns or manages the venue. +NOTE – It is general that digital signage service provider rents a venue for installation of their terminal. +- 3.2.12 passive audience:** Audience without interacting with terminal devices. +- 3.2.13 passer-by:** A person without stopping nearby locations of multimedia services within the predetermined time and distance. +- 3.2.14 raw audience data:** A raw data that is captured by input devices of a terminal device such as camera, microphone, sensor devices, etc. +- 3.2.15 venue:** A place or location that a terminal device is located. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------------------------------| +| AM | Audience Measurement | +| DS | Digital Signage | +| DS-AM | Digital Signage system with Audience Measurement functions | +| GML | Geography Markup Language | +| IPTV | Internet Protocol Television | +| NFC | Near Field Communication | +| PII | Personally Identifiable Information | +| XML | eXtensible Markup Language | + +# 5 Conventions + +In this Recommendation: + +- The keyword "is required to" indicates a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. +- The keyword "is recommended" indicates a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. +- The keyword "can optionally" indicates an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +This Recommendation follows the notation described in clause 5 of [ITU-T H.782]. The notation is used in this Recommendation to facilitate the specification of the corresponding schema: + +- Element/Attribute: Name of element or attribute; +- Definition/Semantics: Definition and semantics of the element / attribute along with notes and value domain; +- Support/Type: Describes the number of occurrence and type of the pertaining instance; +- The notations for number of occurrence are (1) = (one instance), (0-1) = (zero or one instance), (0-\*) = (zero or multiple instances possible), (1-\*) = (one or multiple instances possible). The types of the pertaining instance are defined in Table 1; +- Remarks: Describes the notes and the references. + +Table 1 explains data types used in this Recommendation. + +**Table 1 – Data types used in this Recommendation** + +| Type | Name | Notes/Reference | +|------------------------|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ca:civicAddress | Civic address | Used to specify civic location.
    Defined in [IETF RFC 5139]. | +| gml:Point | GML point | Used to specify simple point geometry in format of geography markup language (GML).
    A point consists of a element with a child element. Within the latitude and longitude values are separated by a space.
    Defined in [ISO 19136]. | +| URL | Uniform Resource Locator (URL) | Used to locate resources by describing its access mechanism. (e.g., its network "location").
    Defined in [IETF RFC 3986] as URI= scheme ":" hier-part ["?" query] ["#" fragment]. | +| xs:date | Date | Used to specify date. The lexical form is CCYY-MM-DD where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day.
    Defined in [W3C XMLSchema]. | +| xs:dateTime | Date and time | Used to specify date and time. The format of dateTime is YYYY-MM-DDThh:mm:ss.s+zzzzz
    Defined in [W3C XMLSchema]. | +| xs:integer | Integer | Used to specify a numeric value without a fractional component.
    Defined in [W3C XMLSchema]. | +| xs:NMTOKEN | Normalized String without spaces | Used to specify string after white space replacement. This is, any occurrence of line feeds, carriage returns, contiguous of spaces, and tab are replaced by a single space along with leading or trailing spaces removed.
    Defined in [W3C XMLSchema]. | +| xs:NMTOKENS | List of NMTOKEN | A whitespace-separated list of NMTOKEN values.
    Defined in [W3C XMLSchema]. | +| xs:NMTOKEN enumeration | NMTOKEN with enumeration restriction | Used to specify restricted NMTOKEN values.
    Defined in [W3C XMLSchema]. | + +**Table 1 – Data types used in this Recommendation** + +| Type | Name | Notes/Reference | +|-----------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| xs:nonNegativeInteger | Non-negative integer | Used to specify integer containing only non-negative values (0,1,2,..)
    Defined in [W3C XMLSchema]. | +| xs:positiveInteger | Positive integer | Used to specify integer containing only positive values (1,2,..)
    Defined in [W3C XMLSchema]. | +| xs:time | Time | Used to specify time. The format of time is "hh:mm:ss" where: hh indicates the hour, mm indicates the minute, ss indicates the second.
    Defined in [W3C XMLSchema]. | + +This Recommendation follows the keyword. + +- The keyword "functions" is defined as a collection of functionalities. It is represented by the following symbol in this Recommendation: + +![A rounded rectangular box containing the word 'Functions'.](d29cfbf30a471dc06a78be27f86bd1cf_img.jpg) + +A rounded rectangular box with a thin black border, containing the word "Functions" centered inside it. + +A rounded rectangular box containing the word 'Functions'. + +Frame borders of "functions", and relational lines among "functions" are drawn with solid lines or dashed lines. The solid lines mean required functionalities or relations. On the other hand, the dashed lines mean optional functionalities or relations. + +# **6 Overview of audience measurement of digital signage services** + +## **6.1 Introduction** + +Figure 1 is the general digital signage architecture defined in [ITU-T H.780] with emphasis on the functional block for audience measurement. + +Figure 2 is the general digital signage architecture defined in [ITU-T H.781] with emphasis on the functional block for audience measurement. + +This Recommendation describes functional requirement, configuration, operations, data structures, and metadata between the audience measurement client and audience measurement aggregation. + +![Figure 1: Audience measurement within digital signage service functional architecture. This diagram shows the functional architecture for audience measurement within a digital signage service. It is divided into three main vertical sections: Terminal device functions, Application functions, and Content provider functions, all connected by a central Network functions layer. Terminal device functions include a Digital signage client (required), AM client (optional), Security client (optional), and Content delivery client (required). Application functions include Play log configuration data, Digital signage application (required), Metadata content, Report, AM aggregation (optional), Security (optional), Service control functions, Content delivery functions (Content distribution and Content delivery), and Contents playlist. Content provider functions are shown as a single block. Data flows include Play log configuration data from Digital signage client to Digital signage application; Metadata content and Report from Digital signage application to Content provider functions; Delivery schedule, Playlists, and Contents from Content delivery functions to Contents playlist; and Contents playlist from Network functions to Content delivery client. A legend at the bottom indicates that solid boxes are Required functions, dashed boxes are Optional functions, and a right-angle arrow indicates Out of scope. The diagram is labeled H.783(19)_F01.](007b053fe94a8348f75128a584503fd0_img.jpg) + +Figure 1: Audience measurement within digital signage service functional architecture. This diagram shows the functional architecture for audience measurement within a digital signage service. It is divided into three main vertical sections: Terminal device functions, Application functions, and Content provider functions, all connected by a central Network functions layer. Terminal device functions include a Digital signage client (required), AM client (optional), Security client (optional), and Content delivery client (required). Application functions include Play log configuration data, Digital signage application (required), Metadata content, Report, AM aggregation (optional), Security (optional), Service control functions, Content delivery functions (Content distribution and Content delivery), and Contents playlist. Content provider functions are shown as a single block. Data flows include Play log configuration data from Digital signage client to Digital signage application; Metadata content and Report from Digital signage application to Content provider functions; Delivery schedule, Playlists, and Contents from Content delivery functions to Contents playlist; and Contents playlist from Network functions to Content delivery client. A legend at the bottom indicates that solid boxes are Required functions, dashed boxes are Optional functions, and a right-angle arrow indicates Out of scope. The diagram is labeled H.783(19)\_F01. + +NOTE – Digital signage service functional architecture as defined in [ITU-T H.780]. + +**Figure 1 – Audience measurement within digital signage service functional architecture** + +![Figure 2: Audience measurement within digital signage service functional architecture. This diagram shows the functional architecture for audience measurement within a digital signage service, focusing on the interaction between the Digital signage terminal and the Digital signage service operator. The Audience/user interacts with the Digital signage client (Presentation and Interaction). The Digital signage terminal contains the Digital signage client (required), AM client (optional), Security client (optional), Common alert client (optional), and Content delivery client (required). The Digital signage service operator contains the Digital signage server (required), AM aggregation (optional), Security (optional), Common alert server (optional), and Content delivery server (required). Data flows include Digital signage service control, Logs, notifications, and Content registration (content, metadata) between the Digital signage client and the Digital signage server; Reports from the Digital signage server to the Content provider; and Delivery schedule, playlists, and contents between the Content delivery server and the Content delivery client. All components are connected via a central Network functions layer. A legend at the bottom right indicates that solid boxes are Required functions and dashed boxes are Optional functions. The diagram is labeled H.783(19)_F02.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +Figure 2: Audience measurement within digital signage service functional architecture. This diagram shows the functional architecture for audience measurement within a digital signage service, focusing on the interaction between the Digital signage terminal and the Digital signage service operator. The Audience/user interacts with the Digital signage client (Presentation and Interaction). The Digital signage terminal contains the Digital signage client (required), AM client (optional), Security client (optional), Common alert client (optional), and Content delivery client (required). The Digital signage service operator contains the Digital signage server (required), AM aggregation (optional), Security (optional), Common alert server (optional), and Content delivery server (required). Data flows include Digital signage service control, Logs, notifications, and Content registration (content, metadata) between the Digital signage client and the Digital signage server; Reports from the Digital signage server to the Content provider; and Delivery schedule, playlists, and contents between the Content delivery server and the Content delivery client. All components are connected via a central Network functions layer. A legend at the bottom right indicates that solid boxes are Required functions and dashed boxes are Optional functions. The diagram is labeled H.783(19)\_F02. + +NOTE – Digital signage service functional architecture audience measurement defined in [ITU-T H.781]. + +**Figure 2 – Audience measurement within digital signage service functional architecture** + +The generic flow for the audience measurement of the digital signage service is shown in Figure 3. This flow is an extension of the Figure I.1 of [ITU-T H.780] to describe the additional flow needed for audience measurement. + +![Figure 3 – Generic flow for the audience measurement of the digital signage service. This sequence diagram illustrates the interaction between five entities: Content provider functions, Digital signage application/server functions, AM aggregation, Content delivery functions, AM client, and Terminal device functions. The process involves 13 steps: 1) AM aggregation assigns permission levels to the AM client; 2) AM aggregation delivers these to the AM client; 3) Content is provisioned; 4) Content is sent to the digital signage application; 5) Schedules are managed; 6) Content and schedules are sent to delivery functions; 7) Content is delivered to terminal devices; 8) Service is consumed; 9) Audience detection information is measured by the AM client; 10) The AM client sends this info to the AM aggregation; 11) AM aggregation collects the info; 12) Statistical analysis is performed; 13) The playlist is re-scheduled based on the analysis.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +``` + +sequenceDiagram + participant Content provider functions + participant Digital signage application/server functions + participant AM aggregation + participant Content delivery functions + participant AM client + participant Terminal device functions + + Note left of Content provider functions: 3. Content and playlist provisioning + Content provider functions-->>Digital signage application/server functions: 4. Content and playlist + Digital signage application/server functions-->>Digital signage application/server functions: 5. Schedule management + Digital signage application/server functions-->>Content delivery functions: 6. Content and playlist and delivery schedule + Content delivery functions-->>Terminal device functions: 7. Content and playlist + Note right of Terminal device functions: 8. Service consumption + AM aggregation->>AM client: 1. Permission level and target user(s) setting + AM client-->>AM aggregation: 2. Delivery of the permission level and target user(s) + AM client-->>AM client: 9. Measurement of the audience detection information + AM client->>AM aggregation: 10. Delivery of the AM information and presence detection method + AM aggregation-->>AM aggregation: 11. Collection of AM Info. + AM aggregation-->>Digital signage application/server functions: 12. Statistical analysis of the AM Info. + Note left of Digital signage application/server functions: 13. Re-schedule of playlist + Digital signage application/server functions-->>Content provider functions: 13. Re-schedule of playlist + +``` + +Figure 3 – Generic flow for the audience measurement of the digital signage service. This sequence diagram illustrates the interaction between five entities: Content provider functions, Digital signage application/server functions, AM aggregation, Content delivery functions, AM client, and Terminal device functions. The process involves 13 steps: 1) AM aggregation assigns permission levels to the AM client; 2) AM aggregation delivers these to the AM client; 3) Content is provisioned; 4) Content is sent to the digital signage application; 5) Schedules are managed; 6) Content and schedules are sent to delivery functions; 7) Content is delivered to terminal devices; 8) Service is consumed; 9) Audience detection information is measured by the AM client; 10) The AM client sends this info to the AM aggregation; 11) AM aggregation collects the info; 12) Statistical analysis is performed; 13) The playlist is re-scheduled based on the analysis. + +**Figure 3 – Generic flow for the audience measurement of the digital signage service** + +- 1) Permission level and target user(s) setting: AM aggregation assigns the permission level, scope and properties of the target user(s) for the digital signage service; +- 2) Delivery of the permission level and target user(s): AM aggregation delivers the permission level, scope and properties of the target user(s) for the digital signage service to the AM client; +- 3) Content creation: digital signage content, their relevant metadata and play lists are created; +- 4) Content setting: the content and relevant data are sent to a digital signage application/digital signage server; +- 5) Schedule management: the digital signage application/digital signage server manages the contents and their delivery schedules; +- 6) Content and schedule setting: a content delivery system receives the contents and their deliver schedules; +- 7) Content delivery: the content is delivered to digital signage terminal devices on the schedules; +- 8) Service consumption: the content is shown on the display of the terminal devices based on the play list; +- 9) Measurement of the audience detection information: AM client measures the audience detection information based on the permission level and target user(s) assigned by the AM aggregation with its available presence detection method (e.g., sensor, touch screen recognition, voice recognition, image recognition, mobile phone interface); + +- 10) Delivery of the audience measurement information and presence detection method: AM client delivers the audience measurement information and the presence detection method to the AM aggregation. It is also possible to deliver its location information; +- 11) Collection of the audience measurement information: AM aggregation collects audience measurement information from AM client(s); +- 12) Statistical analysis of the audience measurement information (out of scope of this Recommendation): AM aggregation can provide statistical analysis to the digital signage application/digital signage server upon request. The statistical analysis can be generated based on the display time, place, or other factors. This feature can be developed in any way needed by the digital signage service provider and is out of scope of this Recommendation; +- 13) Reschedule of playlist (out of scope of this Recommendation): the digital signage application/digital signage server can use the statistical analysis to reschedule the content display time to maximise display effect with request from the content provider. + +## 6.2 Functional blocks related to audience measurement + +AM client functions measures the information of the audience, information about the behaviour of audience and environment information around the terminal according to the measurement request of the AM aggregation, and then transmits the measured information to the AM aggregation functions. AM aggregation functions requests the AM client function to measure which information of a terminal according to a schedule and to which schedule the measured information is to be delivered, and then collects the measurement information report delivered from AM client function. + +## 6.3 Considerations + +This clause describes the consideration of audience measurement services for digital signage compared to audience measurement services for Internet Protocol Television (IPTV). + +- 1) Permission level of audience measurement information: the permission level of audience is determined by the digital signage service provider (or permitted officials). The digital signage does not have the concept of subscriber. Therefore, the specific values or methods of permission level are not covered in this Recommendation; +- 2) Scope and property of the target user(s): the scope and the properties of the target user is public and can be composed of people of various natures. The service provider may or may not know of some properties of the target users. The properties can always change; +- 3) Presence detection method and its detected information: various methods can exist for presence detection (e.g., sensor, touch screen recognition, voice recognition, image recognition, mobile phone interface). The property of the detected information should be determined from the detecting devices; +- 4) Digital signage terminal device location detection method and its usage level: various methods exist for the location detection. The longitude and latitude can be used along with the jurisdiction. + +# 7 Functional requirements + +## 7.1 General requirements + +| No | Requirement | Remarks | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| REQ-GEN-1 | The digital signage system with audience measurement functions (DS-AM) architecture is required to support the audience measurement of digital signage services. | This is a basic and logical requirement for digital signage service that supports audience measurement. | + +## 7.2 Requirements for audience measurement architecture + +| No | Requirement | Remarks | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-ARC-1 | The DS-AM architecture is required to have the ability to receive and process multiple audience inputs from one or more input devices (e.g., camera, touch screen, sensors, keyboard). | - | +| REQ-ARC-2 | The DS-AM architecture is required to have the ability to measure audience behaviour by selection of digital signage terminal devices to be measured. | Refer to requirement 4 in clause 7.1 of [ITU-T H.741.0] | +| REQ-ARC-3 | The DS-AM architecture is required to have the ability to measure audience behaviour by selection of behavioural events to be measured. | Refer to requirement 6 in clause 7.1 of [ITU-T H.741.0] | +| REQ-ARC-4 | The DS-AM architecture is required to have the ability to measure audience behaviour by selection of periodicity for periodic measurements. | Refer to requirement 7 in clause 7.1 of [ITU-T H.741.0] | +| REQ-ARC-5 | The DS-AM architecture is required to support communications with other applications, for audience measurement. | Refer to requirement 10 in clause 7.1 of [ITU-T H.741.0] | +| REQ-ARC-6 | The DS-AM architecture is recommended to support presence detection. | Refer to requirement 6 in clause 7.3 of [ITU-T H.741.0]. In digital signage service, this is recommended because it is an important feature for saving power. | +| REQ-ARC-6.1 | The DS-AM architecture can optionally support presence detection by speech recognition. | - | +| REQ-ARC-6.2 | The DS-AM architecture can optionally support presence detection by body recognition, face recognition, etc. | - | +| REQ-ARC-6.3 | The DS-AM architecture can optionally support capability of understanding the meaning of speech by natural language processing functionality. | - | +| REQ-ARC-7 | The digital signage architecture is recommended to support monitoring or communications with AM functions for audience measurement. | Refer to requirement 5 in clause 7.6 of [ITU-T H.741.0] | + +## 7.3 Requirements for interfaces between AM aggregation and stakeholder/DS application + +| No | Requirement | Remarks | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-ASA-1 | The DS-AM architecture is recommended to have the ability to create requested audience measurement reports for stakeholders, and send those reports to the corresponding stakeholders. | Refer to requirement 3 in clause 7.1 of [ITU-T H.741.0] | +| REQ-ASA-2 | The DS-AM architecture is recommended to support stakeholder input orders, measurements, and stakeholder and other digital signage application reports having measurements of viewing behaviour specified by combinations of:
    a) time of day;
    b) audience behaviour;
    c) measurement interval;
    d) audience information;
    e) ambient information;
    f) digital signage terminal device information;
    g) digital signage terminal device location. | Refer to requirement 2 in clause 7.2 of [ITU-T H.741.0].
    For DS-AM, it is more appropriate to use 'sampling interval' rather than 'sample time', 'audience' rather than 'end-user'. It also needs to include ambient information. | +| REQ-ASA-3 | The DS-AM architecture can optionally support stakeholder input orders, measurements, stakeholder and other digital signage application reports having measurements of viewing behaviour specified by combinations of:
    a) day of week;
    b) content;
    c) interactive services (applications). | Refer to [ITU-T H.741.0], however, end-user information is removed because it may cause some leakage of private information. | +| REQ-ASA-4 | The DS-AM architecture is recommended to have the ability to create requested audience measurement reports for other digital signage applications, and to send those reports to the appropriate digital signage applications. | Refer to requirement 3 in clause 7.1 of [ITU-T H.741.0]. | + +## 7.4 Requirements for controlling AM clients + +| No | Requirement | Remarks | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| REQ-AMC-1 | The DS-AM architecture is required to support monitoring or communications with digital signage services, for audience measurement. | Refer to requirement 9 in clause 7.1 of [ITU-T H.741.0] | +| REQ-AMC-2 | The DS-AM architecture is required to support an internal configuration procedure for all AM components which directs measurement, reporting, control and processing operations. | Refer to requirement 11 in clause 7.1 of [ITU-T H.741.0] | +| REQ-AMC-3 | The DS-AM architecture is required to support measurement filtering and summarisation. | Refer to requirement 12 in clause 7.1 of [ITU-T H.741.0] | +| REQ-AMC-4 | The DS-AM architecture is recommended to support at least daily or less frequent changes to configuration without measurement service interruption. | Refer to requirement 4 in clause 7.2 of [ITU-T H.741.0] | + +| No | Requirement | Remarks | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------| +| REQ-AMC-5 | The DS-AM architecture is recommended to support selection of AM clients to be monitored for audience measurement. | Refer to requirement 7 in clause 7.2 of [ITU-T H.741.0] | +| REQ-AMC-6 | The DS-AM architecture is recommended to support scheduling of configuration changes. | Refer to requirement 5 in clause 7.2 of [ITU-T H.741.0] | +| REQ-AMC-7 | The DS-AM architecture can optionally support downloading, installation, updating, and removal of any audience measurement software. | Refer to requirement 4 in clause 7.3 of [ITU-T H.741.0] | + +## 7.5 Requirements for interface between AM aggregation and AM clients + +| No | Requirement | Remarks | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| REQ-AAC-1 | The DS-AM architecture is required to support traffic shaping of audience measurement data. | Refer to requirement 13 in clause 7.1 of [ITU-T H.741.0] | +| REQ-AAC-2 | The DS-AM architecture is required to ensure the integrity of audience measurement information communicated between AM entities. | Refer to requirement 15 in clause 7.1 of [ITU-T H.741.0] | +| REQ-AAC-3 | The DS-AM architecture is required to provide a non-repudiation property to audience measurement information communicated between AM entities. | Refer to requirement 19 in clause 7.1 of [ITU-T H.741.0] | +| REQ-AAC-4 | The DS-AM architecture is recommended to support recovery from storage congestion. | Refer to requirement 9 in clause 7.2 of [ITU-T H.741.0]. | +| REQ-AAC-5 | The DS-AM architecture is recommended to support recovery from network congestion. | Refer to requirement 10 in clause 7.2 of [ITU-T H.741.0] | + +## 7.6 Requirements for privacy protection + +| No | Requirement | Remarks | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-PRP-1 | The DS architecture is required to handle personally identifiable information (PII) and non-PII separately. | Since PII must be kept confidential, it is essential to handle privacy information in a more robust way. | +| REQ-PRP-2 | Audience measurement data can optionally include identifier with permission from audience. | In case of providing personalized content to audience, it is necessary to acquire audience's identifier. | +| REQ-PRP-3 | The DS-AM architecture is required not to extract PII from digital signage service raw audience data without audience's permission. | It is possible to extract biological information such as hairstyle and skin colour, but it should not try to identify a person with this information without audience's permission. | + +| No | Requirement | Remarks | +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-PRP-4 | The DS terminal is required not to maintain any PII that is acquired by the interaction with user in the local storage of terminal after audience has left. | When an audience leaves terminal after some kind of interaction, their PII should be removed to prevent a leakage of personally identifiable information. | +| REQ-PRP-5 | The DS terminal is recommended to remove information that has been acquired by the interaction with audiences. | In some cases, digital signage service may request more information like preference of audience. Even though this does not contain any PII, it needs to be removed as well. | +| REQ-PRP-6 | The DS-AM architecture is recommended to minimize the acquisition, locations and duration of storage, and transmissions of personal data necessary for delivering the audience measurement services. | Refer to requirement 11 in clause 7.2 of [ITU-T H.741.0] | +| REQ-PRP-7 | The DS-AM architecture is required to acquire PII based on audience's permission. | PII can be acquired by audience's input or audience's smart devices supporting wireless communications such as near field communication (NFC) [ISO/IEC 8802-11]. These procedures shall be performed with audience's permission. | +| REQ-PRP-8 | The DS architecture can optionally ask for the audience's permission | - | +| REQ-PRP-9 | Operators of DS-AM are recommended to provide audiences with clear disclosure and information about data collection and use practices if required by audiences. | Refer to clause 7.5 of [ITU-T H.741.0]. Conditions regarding end-user permission have been removed. | +| REQ-PRP-10 | The DS-AM architecture is recommended to provide notification and permission procedures. | It may request permission to audience directly for further processing with notification regarding what kind of information is gathered, the purpose of gathering, etc. | +| REQ-PRP-11 | The DS-AM architecture is required not to identify a individual without the permission from the audience. | Even though audience does not provide their PII explicitly, technically, it is possible to identify them by use of facial recognition and big data. Hence, identification should be performed based on permission. | +| REQ-PRP-12 | The DS-AM architecture is recommended to support wireless communication technologies, such as NFC and Infrared ray, for identifying audience. | In this case, it may be assumed that audience has given permission on providing their identification information. | +| REQ-PRP-13 | The DS-AM architecture is required to ensure confidentiality of audience measurement data in transit. | Refer to requirement 14 in clause 7.1 of [ITU-T H.741.0] | + +| No | Requirement | Remarks | +|------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| REQ-PRP-14 | The DS-AM architecture is required to audience privacy against the leakage to unintended parties while performing AM operations. | Refer to requirement 16 in clause 7.1 of [ITU-T H.741.0] | +| REQ-PRP-15 | The DS-AM architecture is required to ensure that peer-entity authentication precedes communication between AM peer entities. | Refer to requirement 17 in clause 7.1 of [ITU-T H.741.0] | +| REQ-PRP-16 | The DS-AM architecture is required to ensure that there is no unauthorized access to audience measurement data. | Refer to requirement 18 in clause 7.1 of [ITU-T H.741.0] | +| REQ-PRP-17 | The DS-AM architecture is required to protect information of location owner. | - | + +# 8 Configuration and operations to provide audience measurement data + +## 8.1 Configuration for audience measurement data + +In AMConfiguration(), AM aggregation function transfers configuration information with the MeasurementRequestID element to AM client function. + +Configuration information describes the target terminals to be measured, the categories of the audience or environment information to be measured, the measurement schedule, and the transmission schedule of the measured information. Configuration information is described in detail in clause 9.3. + +![Sequence diagram for AM configuration. It shows two lifelines: 'AM client' on the left and 'AM aggregation' on the right. A message arrow labeled 'AMConfiguration (Configuration)' points from the 'AM aggregation' lifeline to the 'AM client' lifeline. Below the diagram, the text 'H.783(19)_F04' is displayed.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +Sequence diagram for AM configuration. It shows two lifelines: 'AM client' on the left and 'AM aggregation' on the right. A message arrow labeled 'AMConfiguration (Configuration)' points from the 'AM aggregation' lifeline to the 'AM client' lifeline. Below the diagram, the text 'H.783(19)\_F04' is displayed. + +Figure 4 – AM configuration + +## 8.2 Measurement report request for audience measurement data + +In AMReportRequest(), AM aggregation function transfers MeasurementReportRequest information with MeasurementRequestID element to AM client function. + +MeasurementReportRequest information describes the report request of measured information that is related to the MeasurementRequestID element specified in the configuration information. MeasurementReportRequest information is described in detail in clause 9.4. + +![Sequence diagram for AM measurement report request. It shows two lifelines: 'AM client' on the left and 'AM aggregation' on the right. A message arrow labeled 'AMReportRequest (MeasurementReportRequest)' points from the 'AM aggregation' lifeline to the 'AM client' lifeline. Below the diagram, the text 'H.783(19)_F05' is displayed.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +Sequence diagram for AM measurement report request. It shows two lifelines: 'AM client' on the left and 'AM aggregation' on the right. A message arrow labeled 'AMReportRequest (MeasurementReportRequest)' points from the 'AM aggregation' lifeline to the 'AM client' lifeline. Below the diagram, the text 'H.783(19)\_F05' is displayed. + +Figure 5 – AM measurement report request + +## 8.3 Measurement report for audience measurement data + +In AMReport(), AM client function transfers MeasurementReportPackage information which includes several MeasurementReport information with MeasurementRequestID element to AM aggregation function. + +MeasurementReportPackage information describes the collection of measured information that is related the same MeasurementRequestID element. MeasurementReportPackage information is described in detail in clause 9.5. + +MeasurementReport information describes the report of measured information that is related to the MeasurementRequestID element specified in the configuration information. MeasurementReport information is described in detail in clause 9.6. + +![Diagram showing the flow of an AM measurement report from an AM client to an AM aggregation. The AM client sends an AMReport (MeasurementReportPackage) to the AM aggregation. The diagram is labeled H.783(19)_F06.](5445597cceefaca1ac89e710fe339325_img.jpg) + +``` + +sequenceDiagram + participant AM client + participant AM aggregation + Note left of AM client: AM client + Note right of AM aggregation: AM aggregation + AM client->>AM aggregation: AMReport (MeasurementReportPackage) + Note right of AM aggregation: H.783(19)_F06 + +``` + +Diagram showing the flow of an AM measurement report from an AM client to an AM aggregation. The AM client sends an AMReport (MeasurementReportPackage) to the AM aggregation. The diagram is labeled H.783(19)\_F06. + +**Figure 6 – AM measurement report** + +# 9 Metadata to provide audience measurement data + +Annex A shows the XML schema on the data structures for message delivery between AM client and AM aggregation. This aims to widen applicability of the specifications for digital signage audience measurement services through easy XML validation. + +## 9.1 Metadata for audience information + +Table 2 defines the metadata for audience information. + +**Table 2 – Metadata for "audience information"** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|----------------------|------------------------------------------------------------------------|--------------------------------------|---------| +| Audience Information | Container for audience information. | | | +| AgeGroup | Element of AudienceInformation.
    Container for age group type. | 0-1 | | +| ChildNumber | Element of AgeGroup.
    Identifies number of children in audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| YoungAdult Number | Element of AgeGroup.
    Identifies number of young adults in audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| AdultNumber | Element of AgeGroup.
    Identifies number of adults in audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| SeniorNumber | Element of AgeGroup.
    Identifies number of seniors in audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| GenderGroup | Element of AudienceInformation.
    Container for gender group type. | 0-1 | | + +**Table 2 – Metadata for "audience information"** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|----------------| +| MaleNumber | Element of GenderGroup.
    Identifies number of males in audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| FemaleNumber | Element of GenderGroup.
    Identifies number of females in audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| Relation | Element of AudienceInformation.
    Container for relation type. | 0-1 | | +| FamilyGroupNu
    mber | Element of Relation.
    Identifies number of families in audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| FriendsGroupNu
    mber | Element of Relation
    Identifies number of friends in audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| Activity | Element of AudienceInformation.
    Container for Activity. | 0-1 | | +| ActiveAudience
    Number | Element of Activity.
    Identifies number of active audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| PassiveAudience
    Number | Element of Activity.
    Identifies number of passive audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| PasserByNumber | Element of Activity.
    Identifies number of passer-by. | 0-1
    xs:
    nonNegativeInt
    eger | | +| AverageViewing
    Time | Element of Activity.
    Describes the averaged viewing time of the active audience and passive audience. | 0-1
    xs:
    nonNegativeInt
    eger | | +| AudienceDistanc
    e | Element of AudienceInformation.
    Describes averaged distance between digital signage terminal and audience.
    The suggested unit is meters. | 0-1
    xs:nonNegativeI
    nteger | | +| VehicleNumber | Element of AudienceInformation.
    Describes the average number of vehicles passed-by. | 0-1
    xs:
    nonNegativeInt
    eger | | + +## 9.2 Metadata for environmental information + +Table 3 defines the metadata for environmental information. + +**Table 3 – Metadata for "environmental information"** + +| Element / Attribute | Definition/Semantics | Support/type | Remarks | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------| +| EnvironmentInformation | Container for environment information. | | | +| BrightnessLevel | Element of EnvironmentInformation.
    Describes the brightness level of the surrounding. | 0-1
    xs: nonNegativeInteger | | +| SoundLevel | Element of EnvironmentInformation.
    Sound level value of the surrounding and its unit. | 0-1
    xs: nonNegative Integer | | +| unit | Attribute of SoundLevel.
    Unit of SoundLevel.
    Unit can be dB, and other.
    Suggested unit is in dB. | 0-1
    xs:NMTOKEN
    enumeration | | +| Temperature | Element of EnvironmentInformation.
    Temperature value of the surrounding and its unit. | 0-1
    xs:Integer | | +| unit | Attribute of Temperature.
    Unit of Temperature.
    Unit can be Celsius, Fahrenheit, or other.
    Suggested unit is in Celsius. | 0-1
    xs:NMTOKEN
    enumeration | | +| Humidity | Element of EnvironmentInformation.
    Humidity value of the surrounding and its unit. | 0-1
    xs:nonNegativeInteger | | +| unit | Attribute of Humidity.
    Unit of Humidity.
    Unit can be percentage, absolute, and other.
    Suggested unit is in percentage (%). | 0-1
    xs:NMTOKEN
    enumeration | | +| WeatherDescriptionList | Element of EnvironmentInformation.
    Describes the weather condition of the surrounding.
    Values: snowy, rainy, sunny, cloudy, windy. | 0-1
    xs:NMTOKEN
    S | | + +## 9.3 Metadata for configuration information + +Table 4 defines the metadata for configuration information. Configuration describes the information such as target terminal to be measured, category to be measured, schedule of measurement and delivery schedule of measured information. + +**Table 4 – Metadata for "configuration"** + +| Element / Attribute | Description/Semantics | Support/type | Remarks | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------------| +| Configuration | Container for a configuration. | | Refer to Table 9 in clause 6.2.2 of [ITU-T H.741.2] | +| measurementRequestId | Attribute of Configuration.
    Identification of the configuration for measurement request.
    Value is unique in aggregation function. This ID, to be included in the measurement reports, may be used by the aggregation function to identify all measurement reports related to the same configuration. | 1
    xs:NMTOKEN | Refer to Table 9 in clause 6.2.2 of [ITU-T H.741.2] | +| aggregationFunctionIdref | Attribute of Configuration.
    Identification of aggregation function requesting for audience measurement. | 1
    xs:NMTOKEN | | +| MeasurementTarget | Element of Configuration.
    Describes the target terminals for measurement.
    If MeasurmentTarget is not present then configuration is not filtered. | 0-1 | Defined in Table 5 | +| MeasurmentCategory | Element of Configuration.
    Describes the category of audience or ambient information for measurement.
    If MeasurmentCategory is not present then configuration is not filtered. | 0-1 | Defined in Table 6 | +| MeasurementSchedule | Element of Configuration.
    Describes the time period and interval for measurement. | 1-* | Defined in Table 7 | +| MeasurementDeliverySchedule | Element of Configuration.
    Describes the address, timing and method of delivering the measurement report. | 0-1 | Defined in Table 8 | + +Table 5 describes the metadata elements for measurement target to specify which one is to be measured. + +**Table 5 – Metadata for "measurement target"** + +| Element / Attribute | Description/Semantics | Support/Type | Remarks | +|--------------------------|----------------------------------------------------------------------------------------------|--------------------|-------------------------------------------------| +| MeasurementTarget | Element of Configuration.
    Container for measurement target. | | | +| TargetTerminalDeviceList | Element of MeasurementTarget.
    Describes the terminal device list of target for measuring. | 0-1
    xs:NMTOKENS | TerminalID is defined in [ITU-T H.782] | +| TargetTerminalGroupList | Element of MeasurementTarget.
    Describes the terminal group list of target for measuring. | 0-1
    xs:NMTOKENS | GroupID is defined in Table 9 of [ITU-T H.782]. | + +Table 6 describes the metadata elements for measurement category to specify which category of audience or ambient information is to be measured. + +**Table 6 – Metadata for "measurement category"** + +| Element / Attribute | Description/Semantics | Support/Type | Remarks | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| MeasurementCategory | Element of Configuration.
    Container for measurement category. | | | +| MeasurementCategoryAudience | Element of MeasurementCategory.
    Describes the category list of audience for measuring. | 0-* | | +| AudienceCategoryList | Element of MeasurementCategoryAudience
    List of audience category to be measured.
    Values: AgeGroup, GenderGroup, Relation, Activity, AudienceDistance, VehicleNumber, etc. (Category values of audience information can be obtained from Table 1). | 0-1
    xs:NMTOKEN
    S | If AudienceCategoryList and All AudienceCategoryExceptList are not present then measurements are not filtered by audience category. | +| AllAudienceCategoryExceptList | Element of MeasurementCategoryAudience
    List of audience category not to be measured.
    Values: AgeGroup, GenderGroup, Relation, Activity, AudienceDistance, VehicleNumber, etc. (Category values of audience information can be obtained from Table 1). | 0-1
    xs:NMTOKEN
    S | If AudienceCategoryList and All AudienceCategoryExceptList is not present then measurements are not filtered by audience category. | +| MeasurementCategoryAmbient | Element of MeasurementCategory.
    Describes the category list of ambient information for measuring. | 0-* | | +| AmbientCategoryList | Element of MeasurementCategoryAmbient
    List of ambient category to be measured.
    Values: brightness, sound level, temperature, weather, humidity, etc. (Category values of ambient information can be obtained from Table 2). | 0-1
    xs:NMTOKEN
    S | If AmbientCategoryList and All AmbientCategoryExceptList are not present then measurements are not filtered by ambient category. | +| AllAmbientCategoryExceptList | Element of MeasurementCategoryAmbient
    List of ambient category not to be measured.
    Values: brightness, sound level, temperature, weather, humidity, etc. (Category values of ambient information can be obtained from Table 2). | 0-1
    xs:NMTOKEN
    S | If AmbientCategoryList and All AmbientCategoryExceptList are not present then measurements are not filtered by ambient category. | + +**Table 6 – Metadata for "measurement category"** + +| Element / Attribute | Description/Semantics | Support/Type | Remarks | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------| +| MeasurmentLocationInclusion | Element of MeasurementCategory.
    Describes whether to include location measured by digital signage terminal.
    Values: inclusion, exclusion. | 0-1
    xs:NMTOKEN
    enumeration | This element is expected to be used for mobile terminals. | + +Table 7 describes the metadata elements for measurement schedule. MeasurementSchedule allows definition of several measurement periods and the method of how a measurement report is to be triggered, either periodically and/or on specific periods. + +**Table 7 – Metadata for "measurement schedule"** + +| Element / Attribute | Description/Semantics | Support/type | Remarks | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------------| +| MeasurementSchedule | Element of Configuration.
    Container for time period for measurement. | - | Refer to Table 11 in clause 6.2.2 of [ITU-T H.741.2] | +| MeasurementPeriod | Element of MeasurementSchedule.
    Describes the measurement period. | 0-* | Refer to Table 11 in clause 6.2.2 of [ITU-T H.741.2] | +| startDay | Attribute of MeasurementPeriod.
    Start date in which the measurement starts. | 0-1
    xs:date | | +| endDay | Attribute of MeasurementPeriod.
    End date in which the measurement ends. | 0-1
    xs:date | | +| startTime | Attribute of MeasurementPeriod.
    Time of the day at which the measurement starts. | 0-1
    xs:time | Refer to Table 11 in clause 6.2.2 of [ITU-T H.741.2] | +| endTime | Attribute of MeasurementPeriod.
    Time of the day at which the measurement stops.
    Default is at end of day. | 0-1
    xs:time
    Default
    23:59:59.99 | Refer to Table 11 in clause 6.2.2 of [ITU-T H.741.2] | +| AppliedDayOfTheWeekList | Element of MeasurementPeriod.
    Day of the week to which measurement is applied.
    Value list: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday, weekday, weekend, public holiday, everyday, other. | 0-*
    xs:NMTOKENS

    Default:
    Everyday | Refer to Table 11 in clause 6.2.2 of [ITU-T H.741.2] | +| MeasurmentInterval | Element of MeasurementSchedule.
    This is a container for measurement interval value and unit during the measurement period. | 0-1
    xs:nonNegativeInteger | | + +**Table 7 – Metadata for "measurement schedule"** + +| Element / Attribute | Description/Semantics | Support/type | Remarks | +|---------------------|---------------------------------------------------------------------------------------------------------|----------------------------------|---------| +| unit | Attribute of MeasurementInterval.
    Unit of measurement interval.
    Value: hour, minute, second, etc. | 0-1
    xs:NMTOKEN
    enumeration | | + +Table 8 describes the metadata elements for measurement delivery schedule. MeasurementDeliverySchedule allows AM aggregation function to specify how measurement reports are delivered to the AM aggregation function. + +**Table 8 – Metadata for "measurement delivery schedule"** + +| Element / Attribute | Description/Semantics | Support/type | Remarks | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------| +| MeasurementDeliverySchedule | Element of Configuration
    Description of the mechanism to be used to decide on how to make the measurement report available to the AM aggregation function. | | Refer to Table 12 in clause 6.2.2 of [ITU-T H.741.2] | +| DeliveryAddress | Element of MeasurementDeliverySchedule.
    URL to be used to send measurement reports from the AM client function. | 0-*
    URL | Refer to Table 12 in clause 6.2.2 of [ITU-T H.741.2] | +| ImmediatePush | Element of MeasurementDeliverySchedule.
    This element indicates that the measurement delivery takes place immediately with possible grouping of measurement reports. | 0-1
    (Note) | Refer to Table 12 in clause 6.2.2 of [ITU-T H.741.2] | +| MeasurementReportNumberByPush | Element of ImmediatePush.
    This element indicates the number of measurement reports which are to be grouped together before a push delivery is attempted. | 0-1
    xs:positiveInteger | Refer to Table 12 in clause 6.2.2 of [ITU-T H.741.2] | +| DelayedDelivery | Element of MeasurementDeliverySchedule.
    This element indicates that the measurement delivery is to take place during specific delivery windows. | 0-1
    (Note) | Refer to Table 12 in clause 6.2.2 of [ITU-T H.741.2] | +| DeliveryWindow | Element of DelayedDelivery.
    This element is a container for the start and end time of a measurement delivery window. | 0-* | Refer to Table 12 in clause 6.2.2 of [ITU-T H.741.2] | + +**Table 8 – Metadata for "measurement delivery schedule"** + +| Element / Attribute | Description/Semantics | Support/type | Remarks | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------------------------------------------------------| +| startTime | Attribute of DeliveryWindow. Time of the day at which the stored audience measurement reports could start to be delivered. | 0-1
    xs:time | Refer to Table 12 in clause 6.2.2 of [ITU-T H.741.2] | +| endTime | Attribute of DeliveryWindow. Last time of the day at which the audience measurement report could be delivered. | 0-1
    xs:time | Refer to Table 12 in clause 6.2.2 of [ITU-T H.741.2] | +| Pull | Element of MeasurementDeliverySchedule. This element indicates that the measurement reports are to be delivered only on request from the AM aggregation function. | 0-1
    (Note) | Refer to Table 12 in clause 6.2.2 of [ITU-T H.741.2] | + +NOTE – If MeasurementDeliverySchedule is present, one of either ImmediatePush, DelayedDelivery, or Pull may be present. If none of them are present then the default is ImmediatePush mode. + +## 9.4 Metadata for measurement report request information + +Table 9 defines the metadata for measurement information. + +**Table 9 – Metadata for "measurement report request"** + +| Element / Attribute | Description/Semantics | Support/type | Remarks | +|---------------------------|---------------------------------------------------------------------------------------------|----------------------|------------------------------------------------------| +| MeasurementReportRequest | Container for a measurement report request. (Note 1). | 1 | Refer to Table 15 in clause 6.2.5 of [ITU-T H.741.2] | +| measurementRequestIdsRefs | Attribute of MeasurementReportRequest. Identification of the measurement request. (Note 2). | 1
    xs:
    NMTOKENS | Refer to Table 15 in clause 6.2.5 of [ITU-T H.741.2] | + +NOTE 1 – A measurement report request with no MeasurementRequestIDs indicates that a AM client function is to respond with available data from all measurement requests. +NOTE 2 – Indicates that a AM client function is to respond with available data from this specific measurement request. + +## 9.5 Metadata for measurement report package information + +As there may be several measurement reports ready for delivery to the AM aggregation functions, a data structure for measurement reporting is defined to be able to include one or more measurement reports if necessary. Table 10 defines the metadata for this measurement report package. + +**Table 10 – Metadata for "measurement report package"** + +| Element / Attribute | Description/Semantics | Support/type | Remarks | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------------------------------------------------------------------------------------------------------------| +| Measurement Report Package | Container for a set of measurement reports. | 1 | Refer to Table 22 in clause 6.2.11 of [ITU-T H.741.2] | +| terminalDeviceIdref | Attribute of MeasurementReportPackage. This element uniquely identifies the digital signage terminal device based on the device's MAC address. | 1
    xs:NMTOKEN | Refer to Table 22 in clause 6.2.11 of [ITU-T H.741.2]. TerminalID for device is defined in [ITU-T [ITU-T H.782]]. | +| MeasurementReport | Element of MeasurementReportPackage. Container for a measurement report. | 1-* | Refer to Table 22 in clause 6.2.11 of [ITU-T H.741.2] | + +## 9.6 Metadata for measurement report information + +Table 11 defines the metadata for a measurement report. Multiple elements which are associated with a single trigger time may be included in a particular instance of MeasurementReport. + +**Table 11 – Metadata for "measurement report"** + +| Element / Attribute | Description/Semantics | Support/type | Remarks | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-------------------------------------------------------| +| MeasurementReport | Container for a measurement report. | 0-1 | Refer to Table 21 in clause 6.2.11 of [ITU-T H.741.2] | +| MeasurementRequestIdref | Attribute of MeasurementReport. This element identifies the measurement request which generated this measurement report. | 1
    xs:MTOKENS | Refer to Table 21 in clause 6.2.11 of [ITU-T H.741.2] | +| MeasurementReportTriggerTime | Element of MeasurementReport. This element identifies the time at which the measurement report was created or the measurement period ended. | 1
    xs:dateTime | Refer to Table 21 in clause 6.2.11 of [ITU-T H.741.2] | +| MeasuringTime | Element of MeasurementReport. This element identifies the specific date and time measured by terminal device. | 0-1
    xs:dateTime | | +| MeasuringLocation | Element of MeasurementReport. This element identifies the specific location measured by terminal device. | 0-1 | | +| GeoLocation | Element of MeasuringLocation. The geographical location of the terminal device. | 0-1
    gml:Point | | + +**Table 11 – Metadata for "measurement report"** + +| Element / Attribute | Description/Semantics | Support/type | Remarks | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|------------------------------------------------| +| PostalLocation | Element of MeasuringLocation.
    Location of the terminal other than geographic information (e.g., ZIP code, postal address). | 0-1
    ca:civicAddress | | +| MeasuringInformation | Element of MeasurementReport.
    This is a container for audience and environment information. | 1 | | +| AudienceInformation | Element of MeasuringInformation.
    This is a container for audience information. | 0-* | Audience information is defined in Table 1. | +| AudienceDetectionMethod | Element of AudienceInformation.
    Indicates method used to detect audience.
    Values: camera, microphone, touch screen, RFID reader, etc. | 0-1
    xs:NMTOKEN

    Default: camera | | +| EnvironmentInformation | Element of MeasuringInformation.
    This is a container for environment information. | 0-* | Environment information is defined in Table 2. | +| EnvironmentDetectionMethod | Element of EnvironmentInformation.
    Indicates method used to detect environment information surrounding terminal device.
    Values: thermometer, etc. | 0-1
    xs:NMTOKEN | | + +# Annex A + +## XML schema on the data structures for message delivery + +(This annex forms an integral part of this Recommendation.) + +### A.1 Schematic representation of XML schema + +Operations and metadata of this Recommendation are composed of the following three parts: + +- 1) Configuration for audience measurement data, defined in clause 8.1 and clause 9.3; +- 2) Measurement report request for audience data, defined in clause 8.2 and clause 9.4; +- 3) Measurement report for audience measurement data, defined in clause 8.3 and clause 9.5. + +A schematic representation of XML schema for each part is given in the following clauses. + +#### A.1.1 Schematic representation of configuration for audience measurement data + +- Schematic representation for Table 4 (metadata for configuration) + +![Schematic representation of XML schema for Table 4 (metadata for configuration)](7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg) + +The diagram illustrates the XML schema for the **Configuration** element. It is contained within a dashed box labeled **dsam:ConfigurationType**. The **Configuration** element has an **attributes** section containing **measurementRequestId** and **aggregationFunctionIdref**. It also has a sequence of child elements: **dsam:MeasurementTarget**, **dsam:MeasurmentCategory**, **dsam:MeasurementSche...** (with a **1..∞** cardinality indicator), and **dsam:MeasurementDelive...**. + +Schematic representation of XML schema for Table 4 (metadata for configuration) + +- Schematic representation for Table 5 (metadata for measurement target) + +![Schematic representation of XML schema for Table 5 (metadata for measurement target)](a7585024ebe2bba8ac0757150a12759a_img.jpg) + +The diagram illustrates the XML schema for the **dsam:MeasurementTarget** element. It is contained within a dashed box labeled **dsam:MeasurementTargetType**. The element has a sequence of child elements: **dsam:TargetTerminalDevi...** and **dsam:TargetTerminalGro...**. Each of these child elements is associated with a **dsam:IDREFSType** element, which contains an **attributes** section with an **idrefs** attribute. + +Schematic representation of XML schema for Table 5 (metadata for measurement target) + +- Schematic representation for Table 6 (metadata for measurement category) + +![Schematic representation for Table 6 (metadata for measurement category)](5d3455c6c2a37cb3aff761fedeb8644e_img.jpg) + +This diagram shows the structure of **dsam:MeasurmentCategoryType**. The main element is **dsam:MeasurmentCategory**. It branches into three components: + +- dsam:MeasurementCateg...** (0..∞) which leads to **dsam:MeasurementCategoryAudienceType** containing **dsam:AudienceCategoryList** and **dsam:AllAudienceCategor...**. +- dsam:MeasurementCateg...** (0..∞) which leads to **dsam:MeasurementCategoryAmbientType** containing **dsam:AmbientCategoryList** and **dsam:AllAmbientCategoryE...**. +- dsam:MeasurmentLocatio...** + +Schematic representation for Table 6 (metadata for measurement category) + +- Schematic representation for Table 7 (metadata for measurement schedule) + +![Schematic representation for Table 7 (metadata for measurement schedule)](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +This diagram shows the structure of **dsam:MeasurementScheduleType**. The main element is **dsam:MeasurementSche...** (1..∞). It branches into: + +- dsam:MeasurementPeriod** (0..∞) which leads to **dsam:MeasurementPeriodType**. This type has an **attributes** block containing **startDay**, **endDay**, **startTime**, and **endTime**. It also connects to **dsam:AppliedDayOfTheWe...**. +- dsam:MeasurmentInterval** which leads to **dsam:TimeIntervalType**. This type has an **attributes** block containing **unit**. + +Schematic representation for Table 7 (metadata for measurement schedule) + +- Schematic representation for Table 8 (metadata for measurement delivery schedule) + +![Schematic representation for Table 8 (metadata for measurement delivery schedule)](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +This diagram shows the structure of **dsam:MeasurementDeliveryScheduleType**. The main element is **dsam:MeasurementDelive...**. It branches into four components: + +- dsam:DeliveryAddress** (0..∞) +- dsam:ImmediatePush** which leads to **dsam:ImmediatePushType** containing **dsam:MeasurementReport...**. +- dsam:DelayedDelivery** which leads to **dsam:DelayedDeliveryType**. This contains **dsam:DeliveryWindow** (0..∞) which leads to **dsam:TimePeriodType**. The **dsam:TimePeriodType** has an **attributes** block with **startTime** and **endTime**. +- dsam:Pull** + +Schematic representation for Table 8 (metadata for measurement delivery schedule) + +#### A.1.2 Schematic representation of measurement report request for audience data + +- Schematic representation for Table 9 (metadata for measurement report request) + +![Schematic representation of measurement report request for audience data](14252bcd35912bd656e98b16b2ee51c0_img.jpg) + +``` + +graph LR + A[MeasurementReportRequ] --- B[dsam:MeasurementReportRequestType] + subgraph B + direction TB + C[attributes] --- D[measurementRequestIds] + end + +``` + +Schematic representation of measurement report request for audience data + +#### A.1.3 Schematic representation of measurement report for audience measurement data + +- Schematic representation for Table 10 (metadata for measurement report package) + +![Schematic representation of measurement report package](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +``` + +graph LR + A[MeasurementReportPack] --- B[dsam:MeasurementReportPackageType] + subgraph B + direction TB + C[attributes] --- D[terminalDeviceIdref] + E[dsam:MeasurementReport 1..∞] + end + +``` + +Schematic representation of measurement report package + +- Schematic representation for Table 11 (metadata for measurement report) + +![Schematic representation of measurement report](94fd137860c16c8dfd75512f10161fe8_img.jpg) + +``` + +graph LR + A[dsam:MeasurementReport 1..∞] --- B[dsam:MeasurementReportType] + subgraph B + direction TB + C[attributes] --- D[measurementRequestIdref] + E[dsam:MeasurementRepor...] + F[dsam:MeasuringTime] + G[dsam:MeasuringLocation] + H[dsam:MeasuringInformat] + end + +``` + +Schematic representation of measurement report + +![Schematic representation of MeasuringLocation](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +``` + +graph LR + A[dsam:MeasuringLocation] --- B[dsam:MeasuringLocationType] + subgraph B + direction TB + C[dsam:GeoLocation] + D[dsam:PostalLocation] + end + +``` + +Schematic representation of MeasuringLocation + +![Schematic representation of MeasuringInformationType](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +``` + +graph LR + A[MeasuringInformationType] --- B[Type Container] + subgraph B + direction TB + C[dsam:AudienceInformation 0..∞] + D[dsam:EnvironmentInform... 0..∞] + end + +``` + +Schematic representation of MeasuringInformationType + +– Schematic representation for Table 2 (metadata for audience information) + +![UML Class Diagram showing the structure of dsam:AudienceInformationWithDetectionMethodType. The diagram includes classes for AgeGroup, GenderGroup, Relation, Activity, AudienceDistance, VehicleNumber, and AudienceDetection... grouped under dsam:AudienceInformationWithDetectionMethodType. It also shows nested type definitions for AgeGroup, GenderGroup, Relation, Activity, and Distance.](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +``` + +classDiagram + class dsam:AudienceInformation + class dsam:AudienceInformationWithDetectionMethodType + class dsam:AgeGroup + class dsam:GenderGroup + class dsam:Relation + class dsam:Activity + class dsam:AudienceDistance + class dsam:VehicleNumber + class dsam:AudienceDetectionMethod + class dsam:AgeGroupType + class dsam:GenderGroupType + class dsam:RelationType + class dsam:ActivityType + class dsam:DistanceType + + dsam:AudienceInformation "0..∞" --> dsam:AudienceInformationWithDetectionMethodType + dsam:AudienceInformationWithDetectionMethodType --> dsam:AgeGroup + dsam:AudienceInformationWithDetectionMethodType --> dsam:GenderGroup + dsam:AudienceInformationWithDetectionMethodType --> dsam:Relation + dsam:AudienceInformationWithDetectionMethodType --> dsam:Activity + dsam:AudienceInformationWithDetectionMethodType --> dsam:AudienceDistance + dsam:AudienceInformationWithDetectionMethodType --> dsam:VehicleNumber + dsam:AudienceInformationWithDetectionMethodType --> dsam:AudienceDetectionMethod + + dsam:AgeGroup --> dsam:AgeGroupType + dsam:GenderGroup --> dsam:GenderGroupType + dsam:Relation --> dsam:RelationType + dsam:Activity --> dsam:ActivityType + dsam:AudienceDistance --> dsam:DistanceType + + dsam:AgeGroupType { + dsam:ChildNumber + dsam:YoungAdultNumber + dsam:AdultNumber + dsam:SeniorNumber + } + dsam:GenderGroupType { + dsam:MaleNumber + dsam:FemaleNumber + } + dsam:RelationType { + dsam:FamilyGroupNumber + dsam:FriendsGroupNumber + } + dsam:ActivityType { + dsam:ActiveAudienceNu... + dsam:PassiveAudienceN... + dsam:PasserByNumber + dsam:AverageViewingTime + } + dsam:DistanceType { + attributes + unit + } + +``` + +UML Class Diagram showing the structure of dsam:AudienceInformationWithDetectionMethodType. The diagram includes classes for AgeGroup, GenderGroup, Relation, Activity, AudienceDistance, VehicleNumber, and AudienceDetection... grouped under dsam:AudienceInformationWithDetectionMethodType. It also shows nested type definitions for AgeGroup, GenderGroup, Relation, Activity, and Distance. + +- Schematic representation for Table 3 (metadata for environment information) + +![Schematic representation of the XML schema for environment information. The diagram shows a central element 'dsam:EnvironmentInform...' with a multiplicity of '0..∞'. It branches into several sub-elements: 'dsam:BrightnessLevel', 'dsam:SoundLevel', 'dsam:Temperature', 'dsam:Humidity', 'dsam:WeatherDescription...', and 'dsam:EnvironmentDetecti...'. The sub-elements 'dsam:SoundLevel', 'dsam:Temperature', and 'dsam:Humidity' are associated with complex types: 'dsam:SoundPressureLevelType', 'dsam:TemperatureType', and 'dsam:ObservedDataValueType' respectively. Each of these complex types contains an 'attributes' box with a 'unit' sub-element. The sub-elements 'dsam:WeatherDescription...' and 'dsam:EnvironmentDetecti...' are also associated with complex types, indicated by ellipses.](399a5af4f606059626c92c92279d54b7_img.jpg) + +Schematic representation of the XML schema for environment information. The diagram shows a central element 'dsam:EnvironmentInform...' with a multiplicity of '0..∞'. It branches into several sub-elements: 'dsam:BrightnessLevel', 'dsam:SoundLevel', 'dsam:Temperature', 'dsam:Humidity', 'dsam:WeatherDescription...', and 'dsam:EnvironmentDetecti...'. The sub-elements 'dsam:SoundLevel', 'dsam:Temperature', and 'dsam:Humidity' are associated with complex types: 'dsam:SoundPressureLevelType', 'dsam:TemperatureType', and 'dsam:ObservedDataValueType' respectively. Each of these complex types contains an 'attributes' box with a 'unit' sub-element. The sub-elements 'dsam:WeatherDescription...' and 'dsam:EnvironmentDetecti...' are also associated with complex types, indicated by ellipses. + +### A.2 XML schema + +The following is the XML schema on the data structures for message delivery between AM client and AM aggregation. + +``` + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + +``` + +# Appendix I + +## Use cases of digital signage services with audience measurement functionality + +(This appendix does not form an integral part of this Recommendation.) + +This appendix describes some use case for audience measurement in digital signage service. + +### I.1 Audience measurement without user interaction from the public users + +As an assumption, content provider provides the contents and the preferred schedule to be played in the digital signage terminal. + +The digital signage terminal has various sensing capabilities such as voice recognition, image recognition, etc. + +![Sequence diagram showing the generic flow for audience measurement without user interaction (public user).](3b00a61116faef21d3a6009fd350b46a_img.jpg) + +The diagram is a sequence diagram illustrating the interaction between five entities: Content provider functions, Digital signage application/server functions, AM aggregation, Content delivery functions, and Terminal device functions. The sequence of messages is as follows: + +- F1: Content provider functions sends a message to Digital signage application/server functions: "Permission level and target user(s) setting". +- F2: AM aggregation sends a message to Content delivery functions: "Delivery of the permission level and target user(s) (Public user)". +- F3: Digital signage application/server functions sends a message to Terminal device functions: "Delivery of contents and playlist and schedule". +- F4: Terminal device functions sends a message to Digital signage application/server functions: "Display of contents". +- F5: Terminal device functions sends a message to AM client: "Measurement of the audience detection information". +- F6: AM client sends a message to AM aggregation: "Delivery of the AM information and presence detection method". +- F7: AM aggregation sends a message to Digital signage application/server functions: "Collection of AM Info.". There is a self-loop on AM aggregation for this step. +- F8: Digital signage application/server functions sends a message to Content provider functions: "Statistical analysis of the AM Info.". There is a self-loop on Digital signage application/server functions for this step. +- F9: Content provider functions sends a message to Digital signage application/server functions: "Re-schedule of playlist". + +H.783(19)\_FI.1 + +Sequence diagram showing the generic flow for audience measurement without user interaction (public user). + +**Figure I.1 – Generic flow for the audience measurement without user interaction (public user)** + +- F1) Permission level and target user(s) setting: AM aggregation assigns the permission level, scope and properties of the target user(s) for the digital signage service. +- F2) AM aggregation delivers the permission level, scope and properties of the target users to the DS client. The properties may include existence of public user, sex, age of public users. +- F3) Digital signage application/digital signage server delivers contents, playlist, and playlist schedule to the DS terminal. +- F4) DS terminal displays content accordingly to the assigned playlist, and playlist schedule. +- F5) AM client measures the audience properties of the public users with its available presence detection method. +- F6) AM client delivers the audience measurement information and the presence detection method to the AM aggregation. +- F7) AM aggregation collects the audience measurement information from AM client(s). + +- F8) AM aggregation provides statistical analysis to the digital signage application/digital signage server of public users properties. The statistical analysis can be generated based on the display time, place, or other factors. +- F9) The digital signage application/digital signage server can use the statistical analysis to reschedule the content display time to maximise display effect with request from the contents provider. If the contents playlist or playlist schedule is modified, repeat from F3. If not, repeat from F4. + +### I.2 Audience measurement with user interaction from the active users + +As an assumption, content provider provides the contents and the preferred schedule to be played in the digital signage terminal. The contents should include features for user-interaction. + +Digital signage terminal has various sensing capabilities such as touch screen recognition, voice recognition, image recognition, mobile device interface, etc. + +Digital signage terminal also has input device such as touch panel, keyboard, mouse, mobile device interface module, etc. + +![Sequence diagram showing the generic flow for audience measurement with user interaction. Lifelines: Content provider functions, Digital signage application/server functions, AM aggregation, Content delivery functions, AM client, Terminal device functions. Steps: F1 (F1. Permission level and target user(s) setting), F2 (F2. Delivery of the permission level and target user(s) (Active user)), F3 (F3. Delivery of contents and playlist and schedule), F4 (F4. Display of contents), F5 (F5. Measurement of the audience detection information), F6 (F6. Delivery of the AM information and presence detection method), F7 (F7. Collection of AM Info.), F8 (F8. Statistical analysis of the AM Info.), F9 (F9. Re-schedule of playlist).](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) + +``` + +sequenceDiagram + participant Content provider functions + participant Digital signage application/server functions + participant AM aggregation + participant Content delivery functions + participant AM client + participant Terminal device functions + + Note right of AM aggregation: F1. Permission level and target user(s) setting + AM aggregation->>AM client: F2. Delivery of the permission level and target user(s) (Active user) + Digital signage application/server functions->>Terminal device functions: F3. Delivery of contents and playlist and schedule + Digital signage application/server functions->>Terminal device functions: F4. Display of contents + Terminal device functions->>AM client: F5. Measurement of the audience detection information + AM client->>AM aggregation: F6. Delivery of the AM information and presence detection method + Note left of AM aggregation: F7. Collection of AM Info. + AM aggregation->>Digital signage application/server functions: F8. Statistical analysis of the AM Info. + Note left of Digital signage application/server functions: F9. Re-schedule of playlist + +``` + +H.783(19)\_FI.2 + +Sequence diagram showing the generic flow for audience measurement with user interaction. Lifelines: Content provider functions, Digital signage application/server functions, AM aggregation, Content delivery functions, AM client, Terminal device functions. Steps: F1 (F1. Permission level and target user(s) setting), F2 (F2. Delivery of the permission level and target user(s) (Active user)), F3 (F3. Delivery of contents and playlist and schedule), F4 (F4. Display of contents), F5 (F5. Measurement of the audience detection information), F6 (F6. Delivery of the AM information and presence detection method), F7 (F7. Collection of AM Info.), F8 (F8. Statistical analysis of the AM Info.), F9 (F9. Re-schedule of playlist). + +**Figure I.2 – Generic flow for the audience measurement with user interaction (active user)** + +- F1) Permission level and target user(s) setting: AM aggregation assigns the permission level, scope and properties of the target user(s) for the digital signage service. +- F2) AM aggregation delivers the permission level, scope and interaction properties of the active users to the DS client. The interaction properties may include sex, age, preference, etc. +- F3) Digital signage application/digital signage server delivers contents, playlist, and playlist schedule to the DS terminal. +- F4) DS terminal displays content accordingly to the assigned playlist, and playlist schedule. +- F5) AM client measures the audience properties of the active users with its available presence detection method. AM client can also acquire preference information from the active user though interaction from the input device. + +- F6) AM client delivers the audience measurement information and the presence detection method to the AM aggregation. +- F7) AM aggregation collects the audience measurement information from AM client(s). +- F8) AM aggregation provides statistical analysis to the digital signage application/digital signage server of active users properties. The statistical analysis can be generated based on the display time, place, or other factors. +- F9) The digital signage application/digital signage server can use the statistical analysis to reschedule the content display time to maximise display effect with request from the content provider. If the contents playlist or playlist schedule is modified, repeat from F3. If not, repeat from F4. + +### I.3 Audience measurement based on ambient information from digital signage terminal + +As an assumption, content provider provides the contents, the preferred schedule to be played in the digital signage terminal. + +Digital signage terminal has sensing module to collect ambient information such brightness, noise, temperature, weather, traffic. This ambient information can be used to control DS terminal through interaction between AM aggregation and AM client. Also, DS terminal can use this ambient information to control itself. + +The digital signage server will need to provide control condition of the digital signage terminal or displayed contents based on ambient information. + +![Sequence diagram showing the generic flow for audience measurement based on ambient information. Lifelines: Content provider functions, Digital signage application/server functions, AM aggregation, Content delivery functions, AM client, Terminal device functions. The sequence includes steps F1 through F9 involving permission settings, content delivery, ambient information collection, statistical analysis, and playlist rescheduling.](67d03c9e89620d73e3786c869e559752_img.jpg) + +``` + +sequenceDiagram + participant CP as Content provider functions + participant DS as Digital signage application/server functions + participant AA as AM aggregation + participant CD as Content delivery functions + participant AC as AM client + participant TD as Terminal device functions + + Note over AA: F1. Permission level and target user(s) setting + AA->>DS: F2. Delivery of the permission level and target user(s) (Ambient Info.) + DS->>TD: F3. Delivery of contents and playlist and schedule + TD->>TD: F4. Display of contents + TD->>TD: F5. Measurement of the ambient information + TD->>AC: F6. Delivery of the AM information and presence detection method + AC->>AA: F7. Collection of AM Info. + AA->>DS: F8. Statistical analysis of the AM Info. + DS->>DS: F9. Re-schedule of playlist + +``` + +H.783(19)\_FI.3 + +Sequence diagram showing the generic flow for audience measurement based on ambient information. Lifelines: Content provider functions, Digital signage application/server functions, AM aggregation, Content delivery functions, AM client, Terminal device functions. The sequence includes steps F1 through F9 involving permission settings, content delivery, ambient information collection, statistical analysis, and playlist rescheduling. + +**Figure I.3 – Generic flow for the audience measurement based on ambient information** + +- F1) Permission level and target user(s) setting: AM aggregation assigns the permission level, scope and properties of the target user(s) for the digital signage service. +- F2) AM aggregation delivers the permission level, scope and ambient properties to the DS client. The ambient properties may include brightness, noise, temperature, weather, traffic, etc. + +- F3) Digital signage application/digital signage server delivers contents, playlist, and playlist schedule to the DS terminal. +- F4) DS terminal displays content accordingly to the assigned playlist, and playlist schedule. +- F5) AM client measures the ambient properties with its available sensing method. +- F6) AM client delivers the audience measurement information and the presence detection method to the AM aggregation. +- F7) AM aggregation collects the audience measurement information based on the ambient properties from AM client(s). +- F8) AM aggregation provides statistical analysis to the digital signage application/digital signage server of the ambient properties. The statistical analysis can be generated based on the display time, place, or other factors. +- F9) The digital signage application/digital signage server can use the statistical analysis to reschedule the content display time to maximise display effect with request from the content provider. If the contents playlist or playlist schedule is modified, repeat from F3. If not, repeat from F2. + +## Bibliography + +- [b-ITU-T X.1252] Recommendation ITU-T X.1252 (2010), *Baseline identity management terms and definitions*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/H/T-REC-H.785.1-201808-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b59ca580cc2f66d0ad418543c0a777663371db90 --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be9ab7b3434e2f9f48e8cc94e43dc3767511174b53b8edb0e897f53d77b8d7cb +size 91240 diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/H/T-REC-H.785.1-201808-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaa8f54afa9c85896e6cd68be6c507f2e74c7868 --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:596a0cbd0612bf399b3af1612a5b4dfa5a7a42dd6a002d6d37bd38cff40322ac +size 31293 diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.785.1-201808-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed5c92bf95d8f4ad750dd3f2e7a4669a005e9b0d --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b364e469baf8dcf68b25af7ab5bbe2d801425c179aaca6765dff00e23180426 +size 143508 diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.785.1-201808-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e75b335620e9a8787fbd02b6e9a1c651feede746 --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ada6efd1f8023a38f7e374c512f714702c0caba30daefa66e9bf0854ed85558d +size 18404 diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/H/T-REC-H.785.1-201808-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92cdbc270849dfa0d4170a26b6dd21f74696ba38 --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe55c4390d59b0898c2f818e7c59f5e95f07a3dbd6518c0a4f35e58bb2f6304f +size 24451 diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/H/T-REC-H.785.1-201808-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1ef7e03656cdb7a7b847404465d658da05f7b72 --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:132b636101054a70f4a06fae733df6281959b565a4b4cb7b5d4d46b8517ea82c +size 25724 diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.785.1-201808-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2276ba3e7fe391b63763b6f75c1c595b44a11b0 --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d3dd9768eac5178bab8cd747b6c8b19b0782d3d4d63934eb40155ac8177af83 +size 3701 diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/H/T-REC-H.785.1-201808-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a216153bde16ee2456813996644352b57469ade0 --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c8a2abb97d1074f5c160a1f158d0901eb7dbc9eb7cd890e951bd27afd17d7b9 +size 97464 diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.785.1-201808-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18711bb6723e1ddcffbf0b5c35f147c8a7424650 --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:820864343013b511ad60bce13b4d4ef5eda47c25348933b71a57a82040001a08 +size 17230 diff --git a/marked/H/T-REC-H.785.1-201808-I_PDF-E/raw.md b/marked/H/T-REC-H.785.1-201808-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f9532fd9006611fba28b1372d1259e4daaf09a4f --- /dev/null +++ b/marked/H/T-REC-H.785.1-201808-I_PDF-E/raw.md @@ -0,0 +1,854 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.785.1** + +(08/2018) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +IPTV multimedia services and applications for IPTV – +Digital Signage + +--- + +**Digital signage: Service requirements and a +reference model on information services in +public places via an interoperable service +platform** + +Recommendation ITU-T H.785.1 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.785.1 + +# Digital signage: Service requirements and a reference model on information services in public places via an interoperable service platform + +## Summary + +Digital signage (DS) services treat information of relatively common interest. Audiences in public places are typical targets of DS services. An interoperable service platform for DS services plays a key role for content dissemination to large numbers of DS terminal devices. + +Recommendation ITU-T H.785.1 addresses high-level requirements, a reference model, push-based distribution methods and relevant metadata of DS services in public places via the interoperable service platform. This Recommendation is expected to enhance interoperability for DS services in public places for efficient and effective system operation. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|--------------------------------------------------------------------------------------------| +| 1.0 | ITU-T H.785.1 | 2018-08-29 | 16 | 11.1002/1000/13672 | + +## Keywords + +Digital signage, distribution method, interoperable service platform, metadata, public place, reference model, requirement. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2019 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|--------------|--------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 3 | +| 6 | Overview ..... | 4 | +| 6.1 | Information services in public place..... | 4 | +| 6.2 | Domain model..... | 5 | +| 6.3 | Types of services ..... | 6 | +| 6.4 | Interoperable service platform ..... | 7 | +| 6.5 | Quality of DS services ..... | 8 | +| 7 | Requirements ..... | 9 | +| 7.1 | General..... | 9 | +| 7.2 | Interoperable service platform ..... | 9 | +| 7.3 | System..... | 9 | +| 7.4 | Network communication..... | 10 | +| 7.5 | Data..... | 10 | +| 7.6 | Presentation..... | 11 | +| 7.7 | Information security ..... | 11 | +| 7.8 | Operation ..... | 11 | +| 7.9 | Terminal device..... | 12 | +| 7.10 | Accessibility..... | 12 | +| 8 | Data transfer interface ..... | 13 | +| 8.1 | Interfaces for content dissemination..... | 13 | +| 8.2 | Interface for content entry (IF-A)..... | 13 | +| 8.3 | Interface for content distribution (IF-B) ..... | 14 | +| 9 | Metadata ..... | 15 | +| 9.1 | Contents distribution ..... | 16 | +| 9.2 | Contents ..... | 16 | +| Appendix I | – Examples of cloud computing for DS services ..... | 18 | +| I.1 | Dissemination models by using cloud computing..... | 18 | +| Appendix II | – Introduction of requirements regarding cloud computing for DS services ..... | 20 | +| II.1 | Requirements on cloud computing..... | 20 | +| Bibliography | ..... | 21 | + + + +# Recommendation ITU-T H.785.1 + +## Digital signage: Service requirements and a reference model on information services in public places via an interoperable service platform + +## 1 Scope + +This Recommendation addresses high-level requirements, a reference model, push-based distribution methods and relevant metadata of digital signage (DS) services in public places via an interoperable service platform. This Recommendation is expected to enhance interoperability for DS services in public places for efficient and effective system operation. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.780] Recommendation ITU-T H.780 (2012), *Digital signage: Service requirements and IPTV-based architecture*. +- [ITU-T H.781] Recommendation ITU-T H.781 (2015), *Digital signage: Functional architecture*. +- [ITU-T H.782] Recommendation ITU-T H.782 (2018), *Digital signage: Metadata*. +- [ITU-T H.785.0] Recommendation ITU-T H.785.0 (2014), *Digital signage: Requirements of disaster information services*. +- [ITU-T X.1058] Recommendation ITU-T X.1058 (2017), *Information technology – Security techniques – Code of practice for personally identifiable information protection*. +- [ITU-T X.1303 bis] Recommendation ITU-T X.1303 bis (2014), *Common alerting protocol (CAP 1.2)*. +- [IETF RFC 6455] IETF Request for Comment 6455 (2011), *The WebSocket Protocol*. +- [W3C HTML5] W3C Recommendation HTML5.2 (2017), *HTML5.2*. +- [W3C XML] W3C Recommendation XML Schema Part 2 (2004), *XML Schema Part 2: Datatypes Second Edition*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 alert** [b-ITU-T X.674]: A warning or alarm message concerning an impending danger or problem. + +**3.1.2 availability** [b-ISO/IEC 27000]: Property of being accessible and usable upon demand by an authorized entity. + +**3.1.3 cloud computing** [b-ITU-T Y.3500]: Paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand. + +NOTE – Examples of resources include servers, operating systems, networks, software, applications, and storage equipment. + +**3.1.4 cloud service** [b-ITU-T Y.3500]: One or more capabilities offered via **cloud computing** (3.1.3) invoked using a defined interface. + +**3.1.5 content** [ITU-T H.780]: A combination of audio, still image, graphic, video, or data. + +NOTE – Variety of formats is classified as the "data" (e.g., text, encoded values, multimedia description language introduced by [b-ITU-T H.760]). + +**3.1.6 digital signage (DS)** [ITU-T H.780]: A system that sends information, advertising and other messages to electronic devices (e.g., displays, speakers) in accordance with the time of day and the location of the display, or the actions of audience. Contents and their relevant information such as display schedules are delivered over networks. + +**3.1.7 confidentiality** [b-ISO/IEC 27000]: Property that information is not made available or disclosed to unauthorized individuals, entities, or processes. + +**3.1.8 distribution** [b-ITU-T Y.1910]: Sending the content to appropriate intermediate locations to enable subsequent delivery. + +**3.1.9 delivery** [ITU-T H.780]: Sending contents to terminal devices. + +**3.1.10 information security** [b-ISO/IEC 27000]: Preservation of **confidentiality** (3.1.7), **integrity** (3.1.11) and **availability** (3.1.2) of information. + +NOTE – In addition, other properties, such as authenticity, accountability, non-repudiation, and reliability can also be involved. + +**3.1.11 integrity** [b-ISO/IEC 27000]: Property of accuracy and completeness. + +**3.1.12 interoperability** [b-ITU-T Y.101]: The ability of two or more systems or applications to exchange information and to mutually use the information that has been exchanged. + +**3.1.13 multimedia** [b-ITU-T T.174]: The property of handling several types of representation media. + +**3.1.14 personally identifiable information (PII)** [b-ISO 29100]: Any information that (a) can be used to identify the PII principal to whom such information relates, or (b) is or might be directly or indirectly linked to a PII principal. + +NOTE – To determine whether a PII principal is identifiable, account should be taken of all the means which can reasonably be used by the privacy stakeholder holding the data, or by any other party, to identify that natural person. + +**3.1.15 service provider** [b-ITU-T M.1400]: A general reference to an operator that provides telecommunication services to customers and other users either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. + +NOTE – Typically, the service provider acquires or licenses content from content providers and packages this into a service that is consumed by the end-user. + +**3.1.16 symbols, pictograms and icons** [b-ITU-T E.121]: are graphical representations that convey information with a minimum of reliance on language. + +**Pictograms** are typically said to be simplified pictorial representations, used to guide people and tell them how to achieve a certain goal. Pictograms are, as far as possible, self-explanatory, and require little or no learning on the part of users. + +**Symbols**, on the other hand, are usually defined as abstract representations that stand for something but that require learning on the part of users to take on their meaning. + +Symbols and pictograms can be considered to lie at opposite ends of a continuum defined by the degree to which they are pictorial representations of the things they represent. As a practical matter, many of the symbols and pictograms in use today, including many of those found in this Recommendation, lie some distance from either end of that continuum. That is, they may contain some degree of abstraction combined with a degree of pictorial representation. + +**Icons** are similar representations that have become widely used as objects of manipulation in graphical user interfaces for computer applications. They may be entirely abstract, like symbols, or pictorial, like pictograms, or fall at some point between those extremes. The use of this term is growing beyond its origin in computer user interfaces. + +In this Recommendation, the terms "symbol", "pictogram" and "icon" will be used as far as possible in the spirit of the definitions given above. However, it must be realized that the choice of one term or the other is, to some considerable degree, arbitrary in many cases. No effort has been made here to adhere strictly to clearly delineated distinctions between these terms, as distinctions have proved impossible to draw reliably. + +**3.1.17 terminal device (TD)** [b-ITU-T Y.1901]: An end-user device which typically presents and/or processes the content, such as a personal computer, a computer peripheral, a mobile device, a TV set, a monitor, a VoIP terminal or an audio-visual media player. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------| +| API | Application Program Interface | +| CSC | Cloud Service Customer | +| CSP | Cloud Service Provider | +| DS | Digital Signage | +| HTML | HyperText Markup Language | +| ICC | Integrated Circuit Card | +| LAN | Local Area network | +| PII | Personally Identifiable Information | +| SaaS | Software as a Service | +| SLA | Service Level Agreement | +| URI | Uniform Resource Identifier | +| URL | Uniform Resource Locator | +| XML | extensible Markup Language | + +## 5 Conventions + +In clause 7 of this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "can optionally" indicate an optional requirement that is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. + +In clause 9 of this Recommendation: + +- The notations for requirement level are M for mandatory and O for optional. +- Element/attribute names in Tables 9-1 and 9-2, which are relevant to content distribution, use lower camel case (i.e., only the first word starts with a lower case letter and each of the following words starts with an upper case letter (e.g., "lowerCamelCase")). +- Element/attribute names in Table 9-2, which are metadata of content management, use upper camel case (i.e., every word starts with an upper case letter (e.g., "UpperCamelCase")). + +Table 5-1 also shows data types used in this Recommendation and their explanations. + +**Table 5-1 – Data types used in this Recommendation** + +| Type | Name | Notes/Reference | +|-------------|---------------|------------------------------------------------------------------------------------------------------------------------------------| +| xs:dateTime | Date and time | Used to specify date and time. The format of dateTime is YYYY-MM-DDThh:mm:ss.s+zzzzz
    Defined in [W3C XML]. | +| xs:int | Integer | Used to specify a numeric value without a fractional component.
    Defined in [W3C XML]. | +| xs:string | String | Used to specify string value which contains characters, line feeds, carriage returns, and tab characters.
    Defined in [W3C XML]. | + +## 6 Overview + +### 6.1 Information services in public place + +Digital signage (DS) aims to provide information services of relatively common interest. Pedestrians in public places are typical targets of DS services (i.e., audiences of the services). + +A public place is a social space that is generally open and accessible to people (i.e., unspecified individuals). Roads including the pavement, public squares, libraries, museums, schools, railway stations, parks and beaches are considered as typical public places. A privately owned public place can be also included in public places if the private area is generally open to the public (e.g., a place owned by a commercial property developer). From this viewpoint, shopping malls, hospitals, theatres and hotel lobbies are categorized as public places as well. + +Interoperability generally means that a system can access to and work together with other systems without any restriction. It is necessary to set a minimal guideline for interoperability of public + +services, for their effectiveness and efficiency, which are provided by different vendors, service providers and content providers. + +Study items relating to the interoperability point include but are not limited to the following aspects: + +- System aspect: common application program interface (API), service discovery; +- Data aspect: data format, metadata; +- Presentation aspect: colour, intensity, brightness, size, layout, audio, volume, multi-language support for foreign visitors; + +NOTE – For references regarding real-time multi-language support, [b-ITU-T F.745] and [b-ITU-T H.625] address requirements and the architecture of network based speech-to-speech translation individually. + +- Communication aspect: network interfaces, interactions between DS systems and personal devices including mobile phones; +- Operational aspects: update frequency, treatment in emergencies; +- Security aspects. + +In addition, under the current situation wherein global trade, travel and tourism continuously grow, a common method of communication in services in public places using pictograms (i.e., graphic representation) will help both service providers and users, including those with disabilities. + +NOTE – Global standards related symbols and pictograms such as [b-ITU-T E.121], [b-ITU-T F.910] and [b-ISO 7001] can be used as references. + +### 6.2 Domain model + +This clause describes an overview reference model of DS services via an interoperable service platform in a public place. Figure 6-1 shows an overview of the reference model for the DS services using an interoperable service platform. This Recommendation mainly covers distribution processes where the platform receives contents from a content provider or other business system and sends the contents to DS service operators. + +![Figure 6-1 – Domain model with interoperable service platform. The diagram shows four entities in a row: DS terminal device, DS service operator, Interoperable service platform, and Content provider or other business system. Arrows indicate the flow of content: Content registration from the Content provider to the Interoperable service platform, Content distribution from the Interoperable service platform to the DS service operator, and Content delivery from the DS service operator to the DS terminal device.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +``` +graph LR; A[Content provider or other business system] -- "Content registration" --> B[Interoperable service platform]; B -- "Content distribution" --> C[DS service operator]; C -- "Content delivery" --> D[DS terminal device]; +``` + +H.785.1(18)\_F6-1 + +Figure 6-1 – Domain model with interoperable service platform. The diagram shows four entities in a row: DS terminal device, DS service operator, Interoperable service platform, and Content provider or other business system. Arrows indicate the flow of content: Content registration from the Content provider to the Interoperable service platform, Content distribution from the Interoperable service platform to the DS service operator, and Content delivery from the DS service operator to the DS terminal device. + +Figure 6-1 – Domain model with interoperable service platform + +There are several entities in DS services via the interoperable service platform that include but are not limited to the following: + +- **DS terminal device:** The device that displays contents received from a DS service operator and its behaviour is controlled and managed by the DS service operator. In this Recommendation, audience's own devices can be treated as this type of entity; +- **DS service operator:** The business operator that provides DS services. It manages DS terminal devices for displaying contents received from a content provider or other business system via the platform. A DS service provider is a kind of a DS service operator; +- **Interoperable service platform:** The platform performs a role for distribution of contents and pre-processing such as item selection and data format changes of original contents; + +- **Content provider or other business system:** This entity provides contents to the DS service operator via the platform for a particular purpose such as advertisement, information, alerting, etc. + +### 6.3 Types of services + +Information services considered as typical DS services for public interest, include but are not limited to: + +- Place information: guidance facilities including direction finding and tourist information; +- Event notification: announcement of current or forthcoming concerts/events; +- Live feed: video streaming of local or nationwide events such as concerts and sport events; +- Warning: traffic accidents information, natural disaster information, crime prevention and sanitation; +- Advertisement: for commercial purposes; +- Others: news, time signals and weather forecasts. + +Enhancements of the following urban services are also introduced from another viewpoint: + +- Special guidance for foreign visitors, aged persons and persons with disabilities in accordance with universal designs; + +NOTE 1 – The appearance of an aging and aged society is a serious universal issue as is the increasing numbers of domestic and foreign visitors (a.k.a. exchange of population). + +- Space decoration for presenting the attractive aspects of a town. For example, a unified design may be applied to outer package cases of DS terminal devices or to displayed contents or to projected images as interior or exterior decorations of buildings in a town. + +NOTE 2 – These services can be categorized based on information characteristics: i) general announcements, (news, advertisements), ii) tourism information, public information, etc., iii) interactive information (discovery locations, etc.) and iv) warning/alerting information (disaster information, etc.). + +The usage of audience's own terminal devices and personal information can enhance DS services in public places: + +- Cooperative use with the audience's personal devices: a particular DS system enables audiences to browse information on a DS terminal device along with his/her own personal devices according to the recent worldwide popularization of mobile devices such as a smart phone. The personal device can be also receive the information directly from service operators. In the cooperative case, DS services are requested to support various kinds of the personal devices. Acquiring and management of attributes of the personal devices play a key role for this functionality. +- Information provision associated with a personal property: a particular DS system will provide information based on a personal property (e.g., spoken language, dietary habits). Multi-language support is a typical method for providing contents for foreign visitors. The necessity of this support grows ever bigger in light of recent global trends in human mobility. For example, when a tourist asks something of a DS terminal device, the service support function recognizes his/her spoken language by using the language setting in the tourist's terminal device and automatically translates reply contents into the tourist's language. Management of audience's information is key for the personalization. + +NOTE 3 – [b-ITU-T HSTP.DS-UCIS] also introduces several personalized services such as a tourist support based on individual request. Management of audience's information is key for the personalization. Another example is a way finding entrances and exits adapted for physically disabled persons. This can best be achieved by using the disabled person's personal information. + +### 6.4 Interoperable service platform + +Content exchange among DS service operators in standard ways are a key feature in DS services in public places. However, an appropriate set of international standards for the data exchange in DS services have not yet been defined. For example, translation of contents is frequently requested before sending or after receiving contents from different systems. + +The public interest information presented in public places within a specified local area should be immediately processed by an interoperable service platform for realizing interoperability among different DS systems. + +Figure 6-2 shows a model of the interoperable service platform for DS services. The platform mainly executes data handling including content distribution and delivery (a.k.a., dissemination). In addition, the platform can cooperate with other cloud services, which are deemed to be information sources for the services, in order to provide a wide variety of DS services in public places. + +The interoperable service platform provides: + +- i) Key functionalities: are dissemination (i.e., support for content delivery to a large audience), client management (i.e., audience information management, device management and log management), service management, etc. +- ii) Common interface: gives common methods for accessing the platform and for using the platform functions supporting DS services. + +NOTE – In the case of using an interaction among terminal devices, a method linking each terminal device (shown in Figure 6-2 as iii) Link with other devices) is another important study point, but is for further study. + +![Diagram of the Interoperable service platform for DS services. At the top, 'Municipality/enterprise' and 'Retail store' are shown as 'Information sources'. These connect to 'Other clouds services' which include 'Tourism information', 'Traffic information', 'Disaster/crim prevention', and 'SNS'. Below this is the 'Interoperable service platform' which contains 'Audience information management', 'Device information management', 'Dissemination', and 'Multi-language transformation'. A 'Service interface' separates the platform from the 'DS system' layer. Below the DS system are 'Exclusive DS terminal devices' (three public displays) and 'Various types of terminal devices' (Smartphone, Tablet, PC, TV). Annotations include: i) Key functionalities such as information management, content delivery; ii) Common interfaces are provided by the platform; iii) Link with other devices.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +H.785.1(18)\_F6-2 + +Diagram of the Interoperable service platform for DS services. At the top, 'Municipality/enterprise' and 'Retail store' are shown as 'Information sources'. These connect to 'Other clouds services' which include 'Tourism information', 'Traffic information', 'Disaster/crim prevention', and 'SNS'. Below this is the 'Interoperable service platform' which contains 'Audience information management', 'Device information management', 'Dissemination', and 'Multi-language transformation'. A 'Service interface' separates the platform from the 'DS system' layer. Below the DS system are 'Exclusive DS terminal devices' (three public displays) and 'Various types of terminal devices' (Smartphone, Tablet, PC, TV). Annotations include: i) Key functionalities such as information management, content delivery; ii) Common interfaces are provided by the platform; iii) Link with other devices. + +**Figure 6-2 – Interoperable service platform for DS services** + +The dissemination processes are i) important information such as the disaster warning information is registered and stored in the platform, ii) the information is distributed to multiple DS systems by the platform and iii) the systems deliver the information to a large number of DS terminal devices installed in public places. An abstract platform model for dissemination of emergency information is already shown in [ITU-T H.785.0]. Generic functions of DS systems for content delivery are also described in [ITU-T H.780] and [ITU-T H.781]. + +The interoperable service platform has capabilities for not only distributing contents in the common format (e.g., XML [W3C XML]) but also for converting the content for handling by certain DS systems, which can deal with only their defined content format. For example, a given text in XML format is converted into the form of an image file if the systems are not equipped with a XML parser. + +This Recommendation focuses on specifications for the distribution described in clauses 8 and 9. + +### 6.5 Quality of DS services + +For considering requirements of information services in public places, knowledge of the necessary qualities of DS services in a broad sense is useful: + +NOTE – Some examples of necessary aspects of public services are listed below: + +- Reliability: fault tolerant of the systems and services; +- Security: prevention of system and service hacking; +- Visibility: font size, brightness, contrast, duration of presentation and colouring of contents and minimization of optical reflection of display; +- Understandability: multi-language support, consideration of regional expressions or technical terms, avoiding terms that may be difficult to read; +- Health: brightness control, prevention of unnecessary intense blinking and non-healthy patterns; +- Public order and morality: public nature of contents, prevention of uncomfortable feelings and juvenile protection; +- Respect of content rights: respect of privacy rights, portrait rights and copyright; +- Content quality in a narrow sense: attractiveness; +- Image quality: spatial resolution (high-definition), temporal resolution (frame-rate), colour gamut, dynamic range and image size. + +## 7 Requirements + +### 7.1 General + +This clause describes general requirements of DS services in public places. + +- DS systems, which offer disaster information services, are recommended to have the capability to deliver contents in push mode, which means that commercial DS servers send the contents to DS terminal devices. + +NOTE – See clauses 6.3 and clause 7.1 of [ITU-T H.785.0]. + +### 7.2 Interoperable service platform + +This clause describes requirements of an interoperable service platform. + +- The interoperable service platform is required to transform/transcode original contents/data generated by content providers into general formatted contents for enabling DS terminal devices to display the contents. + +NOTE 1 – See relevant requirements on the platform in clause 6.1 of [ITU-T H.785.0]. A well-known content format standard is HTML5 [W3C HTML5]. + +- The interoperable service platform is required to provide content information including locations of contents (i.e., URI/URL) for DS systems by using metadata. +- The interoperable service platform is recommended to provide the latest content information if contents are updated. + +NOTE 2 – See clause 6.1 of [ITU-T H.785.0]. + +### 7.3 System + +This clause describes requirements of DS systems on the aspects of a system such as common API, service discovery. + +- DS systems, which connect to an interoperable service platform to provide dissemination services, are required to have an interface to the interoperable service platform. +- DS systems, which receive contents from the interoperable service platform, are required to deliver the contents to the specified DS terminals according to the delivery rules decided by the content provider and the service operator in advance. + +NOTE 1 – See clause 6.1 of [ITU-T H.785.0] regarding scalability. + +- DS systems, which receive contents from an interoperable service platform, are required to have a mechanism to deliver the contents immediately to the DS terminals according to their emergency levels. + +NOTE 2 – The usage of push mode is a good candidate for meeting this requirement. See clause 8.3.1 of [ITU-T H.780] and clause 6.1 of [ITU-T H.785.0]. + +- DS systems, which support interaction with an audience's own device, are required to provide a way to communicate with the device over a wireless-network. + +NOTE 3 – Wireless LAN [b-IEEE 802.11] is easily deployed for this communication. + +- DS systems are recommended to have the capability to acquire audience information via input devices of exclusive DS terminal devices (e.g., touch panel, video capturing) in order to provide personalized services. + +- DS systems can optionally have the capability to acquire audience information from an audience's own personal device in order to provide personalized services. + +NOTE 4 – Personal information can be obtained by using other input methods such as communication with a smart phone. Integrated circuit card (ICC) is another way to acquire the information. Change of language or character size, etc., can be assumed to be personalized services. + +- DS systems can optionally have the capability to send contents directly to the audience's own personal devices in order to be presented on the personal devices. + +- DS systems, when they can communicate with audience's own devices, are required to have the capability of service discovery, which provides a way to find services. + +NOTE 5 – A captive portal is a well-known technique in Web services. A Web browser is redirected to a specific web page (e.g., a login page). Communications between exclusive DS terminal devices and the audience's own devices are mainly assumed in this context. + +### 7.4 Network communication + +This clause describes requirements of DS systems concerning aspects of network communications such as network interfaces and interactions among DS systems and personal terminal devices including mobile phones. + +- DS services are required to provide unspecified large audiences in their service areas with equal and sufficient network connectivity. + +### 7.5 Data + +This clause describes requirements of an interoperable platform and DS systems concerning aspects of data handling such as data formats and metadata specifications. + +- An interoperable service platform is required to handle domestic or regional alert standards on data format. + +NOTE 1 – See general requirements in clause 7.1 of [ITU-T H.785.0]. + +- DS systems are recommended to treat international standards on content formats for interoperability of DS services in public places. + +NOTE 2 – Appendix II of [ITU-T H.780] lists candidates of standards on media formats. In addition, the markup language HTML5 can be included as a contents format standard for multimedia presentation applicable to a wide variety of device specifications and/or language usages. + +- DS systems, when contents are directly sent to an audience's own device, are recommended to adapt contents design (e.g., layout, media attributes) to the device's specifications. + +NOTE 3 – Refer to the content adaptation use-case in clause 8.10 of [b-ITU-T HSTP.DS-UCIS]. + +### 7.6 Presentation + +This clause describes requirements of DS systems concerning aspects of contents presentation such as colour, size and layout. + +- DS systems are required to have an ability to show contents received from an interoperable service platform on DS terminal devices in the specified geographic areas. +- DS systems are required to have a capability to alter presentation methods according to emergency levels/categories or importance of contents. + +NOTE 1 – See clause 7.7 of [ITU-T H.785.0]. + +- DS systems are required to show disseminated contents according to indicated timing (e.g., immediately present the contents by interrupting the current program, show the contents after the end of the current program). + +NOTE 2 – See clause 8.1.5 of [ITU-T H.780]. + +- DS systems are required to show disseminated contents based on an instructed size and area (e.g., using the whole or part of a display, overlapping contents by the ticker). +- DS systems, are recommended to have the capability to prohibit from presenting expired contents when contents have their expiration date explicitly set. + +NOTE 3 – There is a type of DS system that is equipped with a specific contents update function to manage contents expiration. + +- DS systems, when the system permits acquiring audience information from audience's own personal devices, can optionally have the capability to alter contents according to the information. +- DS systems, when the system directly sends contents to audience's own personal devices in order to be presented on the personal devices, is required to avoid inconsistency among contents displayed on each of the screens of the devices including exclusive DS terminal devices. +- Contents, which aim to call audience's attention to alert information such as disaster information, are recommended to include a siren sound (e.g., the noise of fire engine siren) and/or voice guidance. +- Contents, which aim to prompt a reminder such as disaster information, are recommended to conform to an official design guideline (e.g., layout, colour scheme, which is the choice of colour for certain purposes and a set of pictograms). +- Designs of pictograms are recommended to be easy to understand and uniformly interpreted among audiences without difference based on country of origin. + +NOTE 4 – Refer to clause 5.2 of [b-ITU-T E.121]. + +### 7.7 Information security + +This clause describes security requirements of DS systems in public places. Personally identifiable information (PII) should be carefully taken into account. + +- DS systems are recommended to control personally identifiable information (PII) according to [ITU-T X.1058]. + +### 7.8 Operation + +This clause describes operational requirements of DS systems in public place such as update frequency and treatment in emergencies. + +- DS systems installed within a certain area (e.g., in the same street), regardless of either single vendor or multi vendors, are recommended to have the ability to simultaneously update contents' presentation. + +NOTE – Refer to an interruption method described in clause 7.2 of [ITU-T H.785.0]. Another method is to use the same polling period. + +### 7.9 Terminal device + +This clause describes requirements of DS terminal devices in public places. + +- DS terminal devices are required to have a function to show the dissemination of contents immediately by interrupting the current program. + +NOTE 1 – See clause 8.1.5 of [ITU-T H.780] and clause 7.2 of [ITU-T H.785.0]. + +- DS terminal devices are recommended to have a function to resume the last program after the end of interruption. + +NOTE 2 – See clause 8.1.5 of [ITU-T H.780]. + +- DS terminal devices are recommended to have a function for treating push-mode content delivery in order to show the dissemination of contents immediately. +- DS terminal devices are recommended to keep full-time connections with DS servers via a network for receiving the notification and the dissemination of contents. +- DS terminal devices can optionally have the capability to interact with each other by means of direct communication methods among terminal devices. + +NOTE 3 – [ITU-T H.785.0] limits use this capability to only sharing disaster information; however, the capability can be used for variety of types of services. Communication between exclusive DS terminal devices and audience's own devices are mainly assumed in this context. Wireless LAN [b-IEEE 802.11] is easily deployed in this communication. + +- DS terminal devices, when the terminal devices can communicate with an audience's own devices, can optionally have the capability to continue a communication in the case of a communication breakdown between server-side equipment and the terminal devices. + +NOTE 4 – The requirement level of an exclusive DS terminal device treating disaster information services may be higher. For example, an exclusive DS terminal device may directly send contents to an audience's devices. + +- DS terminal devices, when the terminal devices can communicate with audience's own devices, it can optionally have local storages in order to continue DS services in the case of a communication breakdown between server-side equipment and the terminal devices. + +NOTE 5 – The requirement level of an exclusive DS terminal device treating disaster information services may be higher. + +### 7.10 Accessibility + +Accessibility requirements of DS systems in public places are for further study. + +NOTE – [b-ITU-T F.901], [b-ITU-T F.902], [b-ITU-T F.910] and [b-ITU-T F.921] provide useful information for consideration on accessibility of information services in public places. + +## 8 Data transfer interface + +### 8.1 Interfaces for content dissemination + +![Diagram showing the flow of content between four entities: DS terminal device, DS service operator, Interoperable service platform, and Content provider or other business system. Arrows indicate the direction of content flow: Content registration (IF-A) from provider to platform, Content distribution (IF-B) from platform to operator, and Content delivery (IF-C) from operator to device. A small label H.785.1(18)_F8-1 is at the bottom right.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +``` +graph LR; A[Content provider or other business system] -- "Content registration (IF-A)" --> B[Interoperable service platform]; B -- "Content distribution (IF-B)" --> C[DS service operator]; C -- "Content delivery (IF-C)" --> D[DS terminal device]; +``` + +H.785.1(18)\_F8-1 + +Diagram showing the flow of content between four entities: DS terminal device, DS service operator, Interoperable service platform, and Content provider or other business system. Arrows indicate the direction of content flow: Content registration (IF-A) from provider to platform, Content distribution (IF-B) from platform to operator, and Content delivery (IF-C) from operator to device. A small label H.785.1(18)\_F8-1 is at the bottom right. + +**Figure 8-1 – Interfaces between each entity in the reference model** + +The interfaces between each entity in the domain model described in Figure 8-1 are defined as follows: + +- **Interface-A (IF-A):** The interface that enters the contents from the content provider or other business system to an interoperable service platform; +- **Interface-B (IF-B):** The interface through which the DS service operator receives notifications and the contents from the interoperable service platform; +- **Interface-C (IF-C):** The interface with which the DS service operator provides the contents to DS terminal devices. + +This Recommendation hereafter describes details of interfaces relevant to the interoperable service platform, IF-A and IF-B. + +NOTE – IF-C is the same as the reference point between the DS service operator and DS terminal devices described in [ITU-T H.781] and [ITU-T H.782]. + +### 8.2 Interface for content entry (IF-A) + +This interface is for sending contents from the content provider or other business system, which include an information provider such as a municipality or an emergency services provider, to the interoperable service platform. Each provider or system provides the public information including urgent information for the interoperable service platform in order to disseminate the information over DS systems in a targeted area related to the information. The interoperable service platform can create/transform the contents into specific formats such as HTML5 [W3C HTML5] based on the received data for displaying on the DS terminal devices. + +The interface may provide Web APIs for inputting the data from the content provider or other business system. The specification for sending data is described in Table 8-1. + +**Table 8-1 – Interface specification of IF-A** + +| Item | Specification | +|------------------------|----------------------------------------------------------------------------| +| Communication protocol | HTTP | +| Data Format | XML | +| Direction | PUSH (content provider or other business system to interoperable platform) | + +The data flow is shown in Figure 8-2. + +![Sequence diagram showing data flow in IF-A between an Interoperable service platform and a Content provider or other business system. The steps are: 1. Content registration (from provider to platform), 2. Content process (internal to platform), and 3. Report (from platform to provider).](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +sequenceDiagram + participant Content provider or other business system + participant Interoperable service platform + Note right of Content provider or other business system: H.785.1(18)_F8-2 + Content provider or other business system->>Interoperable service platform: 1. Content registration + activate Interoperable service platform + Interoperable service platform->>Interoperable service platform: 2. Content process + Interoperable service platform->>Content provider or other business system: 3. Report + deactivate Interoperable service platform + +``` + +Sequence diagram showing data flow in IF-A between an Interoperable service platform and a Content provider or other business system. The steps are: 1. Content registration (from provider to platform), 2. Content process (internal to platform), and 3. Report (from platform to provider). + +**Figure 8-2 – Data flow in IF-A** + +Step 1: Content provider or other business system enters (i.e., requests registration of) i) the content which is being delivered to the DS terminal devices and ii) the information on delivery areas, emergency level and importance as metadata. + +Step 2: An interoperable service platform registers and processes the content and the platform may transform the content into a general format such as HTML5 or into an image adapted to the DS terminal devices. + +Step 3: The interoperable service platform reports the result of registration of the content. + +### **8.3 Interface for content distribution (IF-B)** + +This interface is for notification of dissemination from the interoperable service platform to DS service operators. The data may include the contents for displaying the DS terminal devices and the presentation timing. Considering the DS systems used by the DS service operator, there are PUSH and PULL types of receiving data from the interoperable service platform. + +- PUSH type: the DS service operator can receive the notification immediately when the interoperable service platform prepares the message for the dissemination. The DS system should have the mechanism to receive PUSH data transfer. +- PULL type: the DS service operator should check the notification of the interoperable service platform by polling it periodically. + +The specification sending data is described in Table 8-2. + +Data flows of each type are shown in Figures 8-3 and 8-4 respectively. + +**Table 8-2 – Interface specification of IF-B** + +| Item | Specification | | +|------------------------|------------------------------------------------------|------------------------------------------------------| +| | PUSH type | PULL type | +| Communication protocol | WebSocket [IETF RFC 6455] | HTTP | +| Data Format | XML | XML | +| Direction | PUSH (interoperable platform to DS service operator) | PULL (DS service operator to interoperable platform) | + +![Sequence diagram for PUSH type in IF-B. It shows two lifelines: 'DS service platform' on the left and 'Interoperable service platform' on the right. The interaction starts with a '1. Notification' message from the Interoperable service platform to the DS service platform. This is followed by a dashed oval containing the text '(Continue notification in every update timing)'. The diagram is labeled 'H.785.1(18)_F8-3' at the bottom right.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Sequence diagram for PUSH type in IF-B. It shows two lifelines: 'DS service platform' on the left and 'Interoperable service platform' on the right. The interaction starts with a '1. Notification' message from the Interoperable service platform to the DS service platform. This is followed by a dashed oval containing the text '(Continue notification in every update timing)'. The diagram is labeled 'H.785.1(18)\_F8-3' at the bottom right. + +**Figure 8-3 – Data flow of PUSH type in IF-B** + +Step 1: A DS service operator receives the notification from an interoperable service platform at the timing when the dissemination content is registered to the interoperable service platform. + +![Sequence diagram for PULL type in IF-B. It shows two lifelines: 'DS service platform' on the left and 'Interoperable service platform' on the right. The interaction starts with a '1. Request notification' message from the DS service platform to the Interoperable service platform. This is followed by a '2. Notification' message from the Interoperable service platform to the DS service platform. Then, a dashed oval contains the text '3. (Continue request and notification in every specified interval)'. The diagram is labeled 'H.785.1(18)_F8-4' at the bottom right.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Sequence diagram for PULL type in IF-B. It shows two lifelines: 'DS service platform' on the left and 'Interoperable service platform' on the right. The interaction starts with a '1. Request notification' message from the DS service platform to the Interoperable service platform. This is followed by a '2. Notification' message from the Interoperable service platform to the DS service platform. Then, a dashed oval contains the text '3. (Continue request and notification in every specified interval)'. The diagram is labeled 'H.785.1(18)\_F8-4' at the bottom right. + +**Figure 8-4 – Data flow of PULL type in IF-B** + +Step 1: A DS service operator requests the notification. + +Step 2: This DS service operator receives the notification if the dissemination content is registered to the interoperable service platform. + +Step 3: The DS service operator continues to request notification in every specified interval. + +## 9 Metadata + +This clause describes an overview of metadata treated between an interoperable service platform and DS service operators. + +Types of pertaining element/attribute are assumed to conform to the following simple rules: + +- Time-relevant element/attribute: xs:dateTime; +- Numerical-relevant or sentinel element/attribute: xs:int; +- Other element/attribute: xs:string. + +NOTE – A major difference between [ITU-T H.782] and this Recommendation is the assumed usage of metadata. Metadata in clause 9 aims to be primarily used between the platform and service operators for content distribution. On the other hand, [ITU-T H.782] aims to be mainly used for content delivery from the service operators to audiences. + +### 9.1 Contents distribution + +Metadata in this clause is used for contents distribution between an interoperable service platform and service operators. The term "document" is used for contents for distribution via the platform in order to differentiate from contents for delivery controlled and managed by DS systems. + +In this clause, several elements/attributes marked with an asterisk (e.g., xxx \*) are in compliance with [ITU-T X.1303 bis]. + +**Table 9-1 – Metadata elements/attributes on contents distribution** + +| Elements/Attributes | Description | Level | Type | +|-----------------------|-----------------------------------------------------------------------------------|-------|-------------| +| distribution ID* | The identifier of the content document distribution | M | xs:string | +| senderID* | The identifier of the content document distributor | M | xs:string | +| dateTimeSent* | The time and date of the content document distribution | M | xs:dateTime | +| distributionStatus* | The code denoting the appropriate usage of the distributed content document | M | xs:string | +| distributionType* | The code denoting the type of the distributed content document. | M | xs:string | +| areaName | The text denoting the target area for distribution. | M | xs:string | +| areaCode | The code denoting the target area for distribution (e.g., postal address). | O | xs:string | +| contentDescription | The explanatory description of distributed content document. | M | xs:string | +| additionalContentInfo | The supplementary information for conducting the process of content distribution. | O | xs:string | +| documentRevision | The revision of the content document. | M | xs:int | +| documentID | The identifier of the content document. | M | xs:string | +| category* | The code denoting the category of the subject event of the content document. | M | xs:string | +| urgency* | The code denoting the urgency of the subject event of the content document. | M | xs:string | +| severity* | The code denoting the severity of the subject of the content document. | M | xs:string | + +NOTE 1 – Metadata in Table 9-1 starts with the lower case character distinguished from the other metadata in Table 9-2 used as the envelop data for contents distribution. + +NOTE 2 – There is assumed to be two types of identifiers and versions of contents: one is managed by the interoperable service platform (i.e., documentID in this Recommendation) and another is managed by systems of a DS service operator (i.e., contentId [ITU-T H.782]). + +### 9.2 Contents + +Metadata in this clause is used for attributes of distributed contents. It is assumed that these metadata are treated by an interoperable service platform. + +**Table 9-2 – Metadata elements/attributes on contents** + +| Elements/Attributes | Description | Level | Type | +|----------------------------|------------------------------------------------------------|--------------|-------------| +| Text | The text information of the contents (e.g., Headline text) | M | xs:string | +| TickerText | The text of the contents for the ticker | O | xs:string | +| Advertisement | The information whether the contents include advertisement | O | xs:int | +| Language | The language used for the contents | O | xs:string | +| Title | The title of the contents | M | xs:string | +| URI | The URI of the contents | O | xs:string | +| MimeType | Description of encoding used for the contents | O | xs:string | +| OfficeName | The name of office of content publisher. | M | xs:string | +| OrganizationName | The name of organization of content publisher | M | xs:string | +| CreateDateTime | The date and time of production of the contents | M | xs:dateTime | +| TargetDateTime | The date and time of publishing the contents to audiences | M | xs:dateTime | +| ValidDateTime | The date and time of expiration of the contents | O | xs:dateTime | +| FirstCreateDateTime | The date and time of the first creation of the contents | M | xs:dateTime | +| ReportDateTime | The date and time of the publication of the contents | M | xs:dateTime | +| documentID | The identifier of the contents document (See Table 9-1) | M | xs:string | + +## Appendix I + +## Examples of cloud computing for DS services + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Dissemination models by using cloud computing + +Details of functionalities for contents dissemination, which deal with public notification, are reviewed in this clause. Generally, information sources for public notification services including disaster warning are managed by governments and/or public agencies (e.g., disaster information is gathered by a meteorological agency). It is expected that original contents are utilized in multiple information services including broadcasting and telecommunication services. The format of the original contents is not entirely suitable for DS services; therefore, contents transformation is usually indispensable and can be offered as cloud computing. The transformation consists of extracting information relevant to service situations and locations and changing of data format and layout of contents, etc. + +Figure I.1 depicts one case for contents dissemination over cloud, in which both contents transformation and contents delivery are treated by a cloud service provider. In this case, the cloud service provider may need a relatively large amount of investment. + +![Diagram of a cloud service providing both contents transformation and delivery.](171115f072e42b379238ed0dd438e9d7_img.jpg) + +The diagram illustrates a cloud-based disaster service architecture. On the left, four terminal devices (monitors) are connected to a central cloud. Inside the cloud, an 'Operator' (person at a computer) sends 'Program creation - delivery instructions' to a 'DS content delivery system' (server icon). The 'DS content delivery system' is linked to a 'DS transformation system' (server icon), which performs 'Extract relevant info', 'Format change', and 'Layout/design'. The 'DS transformation system' sends 'Alert data' to an 'Aggregate and store' server (icon). This server also receives 'XML format' and 'Information' from external sources. The 'Aggregate and store' server then distributes 'Information' to three external entities: 'Municipalities', 'Counties', and 'Central governments and agencies' (each represented by a person at a computer). At the bottom, a horizontal line divides the diagram into three sections: 'Terminal device' (left), 'Service provider and network provider' (middle, containing the cloud), and 'Content provider' (right, containing the external entities). The text 'H.785.1(18)\_FI.1' is in the bottom right corner. + +Diagram of a cloud service providing both contents transformation and delivery. + +**Figure I.1 – A cloud service provides both contents transformation and delivery** + +Figure I.2 illustrates another case where a cloud service provider deals with only contents transformation. The cloud service provider transforms original contents into specified formats based on specifications of DS systems. In the case of a common alerting service, including disaster alerting for DS, common alerting server functions act as a content transformation system within the cloud service provider. Detailed functional entities within the common alerting server functions have the role of extracting the terminal list for distribution, converting the original content into another format for accessibility and emergency evacuation and managing the playlist schedule and the presentation guideline. + +DS providers respectively present formatted contents after receiving. As a matter of course, even in this case, common formats among the service providers should be used in order to enhance interoperability. + +![Diagram illustrating a cloud service providing content transformation. On the left, four terminal devices are connected to a 'Service operator', a 'Cloud provider' (within a cloud), and a 'Location owner'. The 'Service operator' sends 'Alerts as contents' to the cloud. The 'Cloud provider' sends data to a 'DS transformation system' (containing a server icon) which performs 'Extract relevant info', 'Format change', and 'Layout/design'. The transformed data, labeled 'Alert data', is sent to a 'Content provider' (containing a server icon). The 'Content provider' performs 'Aggregate' and 'Store' operations and outputs 'XML format' and 'Information' to 'Municipalities', 'Counties', and 'Central governments and agencies'. Below the diagram, a 'Domain:' section identifies three categories: 'Terminal device', 'Service provider and network provider', and 'Content provider'. The text 'H.785.1(18)_FI.2' is in the bottom right corner.](a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg) + +**Domain:** + +| | | | +|-----------------|---------------------------------------|------------------| +| Terminal device | Service provider and network provider | Content provider | +|-----------------|---------------------------------------|------------------| + +H.785.1(18)\_FI.2 + +Diagram illustrating a cloud service providing content transformation. On the left, four terminal devices are connected to a 'Service operator', a 'Cloud provider' (within a cloud), and a 'Location owner'. The 'Service operator' sends 'Alerts as contents' to the cloud. The 'Cloud provider' sends data to a 'DS transformation system' (containing a server icon) which performs 'Extract relevant info', 'Format change', and 'Layout/design'. The transformed data, labeled 'Alert data', is sent to a 'Content provider' (containing a server icon). The 'Content provider' performs 'Aggregate' and 'Store' operations and outputs 'XML format' and 'Information' to 'Municipalities', 'Counties', and 'Central governments and agencies'. Below the diagram, a 'Domain:' section identifies three categories: 'Terminal device', 'Service provider and network provider', and 'Content provider'. The text 'H.785.1(18)\_FI.2' is in the bottom right corner. + +**Figure I.2 – A cloud service provides only contents transformation** + +## Appendix II + +## Introduction of requirements regarding cloud computing for DS services + +(This appendix does not form an integral part of this Recommendation.) + +### II.1 Requirements on cloud computing + +Cloud computing provides a way for easy implementation of a DS service in the form of software as a service (SaaS). It is therefore useful to introduce requirements if the deployment of cloud computing for DS in public places is considered. + +[b-ITU-T Y.3501] addresses general requirements on cloud computing and cloud infrastructure, etc. The following requirements are applicable to DS services: + +- **Service life-cycle management:** It is required that cloud computing supports automated service provisioning, modification and termination during the service lifecycle. +- **Regulatory aspects:** It is required that all applicable laws and regulations be respected, including those related to privacy protection. +- **Security:** It is required that the cloud computing environment be appropriately secured to protect the interests of all persons and organizations involved in the cloud computing ecosystem. +- **Accounting and charging:** It is recommended that cloud computing supports various accounting and charging models and policies. +- **Efficient service deployment:** It is recommended that cloud computing enables efficient use of resources for service deployment. +- **Interoperability:** It is recommended that cloud computing systems comply with appropriate specifications and/or standards for allowing these systems to work together. +- **Portability:** It is recommended that cloud computing supports the portability of software assets and data of cloud service customers (CSCs) with minimum disruption. +- **Service access:** Cloud computing is recommended to provide CSCs with access to cloud services from a variety of user devices. It is recommended that CSCs be provided with a consistent experience when accessing cloud services from different devices. +- **Service availability, service reliability and quality assurance:** It is recommended that the cloud service provider (CSP) provides end-to-end quality of service assurance, high levels of reliability and continued availability of cloud services according to the service level agreement (SLA) with the CSC. + +## Bibliography + +- [b-ITU-T E.121] Recommendation ITU-T E.121 (2004), *Pictograms, symbols and icons to assist users of the telephone and telefax services.* +- [b-ITU-T F.745] Recommendation ITU-T F.745 (2016), *Functional requirements for network-based speech-to-speech translation services.* +- [b-ITU-T F.901] Recommendation ITU-T F.901 (1993), *Usability evaluation of telecommunication services.* +- [b-ITU-T F.902] Recommendation ITU-T F.902 (1995), *Interactive services design guidelines.* +- [b-ITU-T F.910] Recommendation ITU-T F.910 (1995), *Procedures for designing, evaluating and selecting symbols, pictograms and icons.* +- [b-ITU-T F.921] Recommendation ITU-T F.921 (2018), *Audio-based network navigation system for persons with vision impairment.* +- [b-ITU-T H.625] Recommendation ITU-T H.625 (2017), *Architecture for network-based speech-to-speech translation services.* +- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2015), *Designations for interconnections among operators' networks.* +- [b-ITU-T T.174] Recommendation ITU-T T.174 (1996), *Application programming interface (API) for MHEG-1.* +- [b-ITU-T X.674] Recommendation ITU-T X.674 (2011), *Procedures for the registration of arcs under the Alerting object identifier arc.* +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.* +- [b-ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirement for the support of IPTV services.* +- [b-ITU-T Y.3500] Recommendation ITU-T Y.3500 | ISO/IEC 17788 (2014), *Information technology – Cloud computing – Overview and vocabulary.* +- [b-ITU-T Y.3501] Recommendation ITU-T Y.3501 (2016), *Cloud computing - Framework and high-level requirements.* +- [b-ITU-T HSTP.DS-UCIS] Technical Paper ITU-T HSTP.DS-UCIS (2014), *Digital signage: Use-cases of interactive services* +- [b-ISO/IEC 27000] ISO/IEC 27000:2014, *Information technology – Security techniques – Information security management systems – Overview and vocabulary.* +- [b-ISO 7001] ISO 7001:2007, *Graphical symbols – Public information symbols.* +- [b-ISO 29100] ISO 29100:2011, *Information and documentation –Security techniques – Privacy framework.* +- [b-IEEE 802.11] IEEE Standards 802.11-2012, *IEEE Standard for Information technology – Telecommunications and information exchange between systems Local and metropolitan area networks – Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specification.* + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ba4636b2a1ca323f28b125fdc8e2f8c609efd66 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ce011af40f61bffba39efe2d6c4aeeac5dfece75b10095bbc08fc13d30b4d01 +size 33770 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..718446d45ea7592aa0c8fc86f142443dceb33224 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8861ace270e9b4b78e5a7603d6573e04d58ca10628cb5d6cc155c15dbe36b258 +size 67130 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9a428836cb265de1cd9100d283d66b4e878b9a4 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8ba156ec7990f86211237b28909e9bb694b408a54ad93c1e76e811b375bffc2 +size 76789 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efddceb6e5d169b33b7fb0057d3c4ca574ceadda --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1521159f7ef8dfcb2f1912965aa170a526bed0215137fe924891bf1646b8909 +size 19065 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fa53f3c1cc9ff71204f05481ac999b9ced2ffb5 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d310704e311d87631f1522a9085da9cf2c648e05fa35091f13719b553992f241 +size 14471 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ece0bc7b4a7f38fbbd339389f71d703154900dd --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43a07cda2771093f07b1d1cd8b0d57db32f46b193582813f1b7a4db773ed6115 +size 62543 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d005e4b9ef6b55472a901ce0304a508abcee796 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3de3206b3121ec668f72c248591c4d38d581caa7ea75ce22d1df08e1199b0fe5 +size 33594 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07ae1f69fb6f7c0084cab7abe3ade84d014d15e9 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be8f76829d2ed5bdabfe6c4ae16e712df344ef8b76b0d67d3dcc511f9ed8ad26 +size 5558 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c95729f006f0883f79dcce32628e393def98b07b --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b07b8a6ba7a67b30651f7208ec2ce55815c35fd5b81319adb3b0a3c4a0edc55c +size 121378 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..429802c1671623cb6d79ac5fc44d373f8738bbb2 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6c0f94ecbb39732926b2ed3a1435c82894282c30f25e8ed81a4b2895d984d21 +size 124091 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aba9d2070bf848fc97055638a18aa58778a4a43f --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:074c1d3bba8ed50f56747e4c8963aa13f570a50d6fc644bcd34ce1d81c8c7ab1 +size 34980 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/8658cfab6a458b4a80ab2e384c61ff89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89e7d38d008881530a4493f210c0cac6ce67ab7b --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/8658cfab6a458b4a80ab2e384c61ff89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f305d41f2f9ea094a0b79bf103779726345fbf227c3435950a451f4e193d7f07 +size 5570 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abb9e3ec6dfc8364cedc39a68cf796e9d3ff5529c79a1811eedeb12c6d6e7583 +size 3787 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..258bc0651857204baec332e4cf34edf18f9fa4ca --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6d1c0dd4f188181308febb75a9cd8ad1562a4bb1c0ec153de29aa8548b539bc +size 5580 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e95387384b6eb276c7f64cb604e23df193131779 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:406b00e7121790ee3df718488d485301ffae4f8ca3edc575a6fdac28a66a2e2c +size 45314 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/f5deee2f3301ee351c4008283ffafbb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb59619ae08b9a07056c88823cd53be749ac1ddd --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/f5deee2f3301ee351c4008283ffafbb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1b24494c5223beca934f5ed7ea26a56d72548ad1eeac9dcc96cc0afbf8af84e +size 74428 diff --git a/marked/H/T-REC-H.810-201911-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/H/T-REC-H.810-201911-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b60c7dc5b29de5de33299767041e71f0705874c7 --- /dev/null +++ b/marked/H/T-REC-H.810-201911-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:268e7644f1580190e98a9496b411afd861ced142415d3f1b2acfd99ed12f349c +size 5600 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44cefbc3960d51de3af41cd2bd8edc96ef5bc130 --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5609538cdba8fc52b62e5e1fbd652058c776d1848d94bb77fb7c5e78dfb5505c +size 35720 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/4537891530c9f6f139a2e1ebf544edc4_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/4537891530c9f6f139a2e1ebf544edc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7382b1f441e04af322ef0b114cf8a947d6e6daab --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/4537891530c9f6f139a2e1ebf544edc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc89d374719d68136a0f47122bd7bfc2c3d4ea24edbdbd9e9d14430c8321e5d0 +size 91736 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0b67003739dcc27a5bfaf7a8c1a82af0d1fd645 --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e86f5c17abdb54034364524ff86b0b54fa007e084299b3353e594fa9f289c43 +size 94139 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd9c50aec689d873fd3dddc30eb3400d14ada0cf --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a31ad98153a5f5dfa30cc78ad4ec0b57a43aea1f3f713bb90ee03a6ccb9da22a +size 182881 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afde64a880b093f9adda042a25c1896ac15d65e3 --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e0c193141cea2bdb1b19ff3672d8a816b2d62d4479fd4ed6d4de6453d9f9502 +size 63159 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f7ee6ea09b7b4b77fa7296f4ffc24f58cc18ecf --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9d9cc4d9ad341d2b1f4121d183adccc6d88bbbee8c6ce8b74459053c688526f +size 92050 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d594920d4c30b6147b10bf69b2977b0f3aab9f9f --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9219ddac8188e2892d60fb70645faf06f4e829dad145100d9a130c9fdf3cbab3 +size 80444 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/7b7596fb5ef925025341a9aacb6f2be7_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/7b7596fb5ef925025341a9aacb6f2be7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83162d1ed3c7b4fa81f34a946474eab55e670fdd --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/7b7596fb5ef925025341a9aacb6f2be7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c2a6dfa4d67c766ba4fad93e60477369a166d056c7be1c87e5a545cc20b09f5 +size 62406 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac90a3edae2f25ceea62aa11d6853dfc6f7a0d59 --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65aff2e4752618e4c933d29c9756584f9a44c6007c6eecee0c9680b66ee20a96 +size 69386 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad12b1d1a4f035e5b46c7aa7b60f9c544498f2ca --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23eaf51c51a0d91aa1cd4259b7f3a26030f451ec426aa566f0b9f7d27631d9c2 +size 96268 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/9c80cf99954eb0142f694456d39fae4b_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/9c80cf99954eb0142f694456d39fae4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2fb88c7a3478c65de4334f43a61d02bcaf4103f --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/9c80cf99954eb0142f694456d39fae4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23d24dec30ae1cb6d7a4c97332486997a81a211b95214a7e6bf0119f42da68de +size 114475 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..974970bd663817895a7c6638e973943a79f1892b --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83f80eee011ba76b22917a44fa45e41677d4ad7375ee8d625705dc62ac1c3935 +size 94280 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..177a6bcff1734989e0e1539897bcc7534ebc6f36 --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a05751ef6e8049846879223bf228a1ba6a1574b0bd540605d8918bacb4223275 +size 174014 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9ac8da64a83c08f11133ba0426016164d54372b --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:433dd8f95ab0f6c8af71a650762fcfdcefa0ee31a0afac61be8dc6977ade21f3 +size 95152 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..039e3cf60bc42700aa5bfd6c5c4887ae6fea0d51 --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66361f2812b80da5df2710b74789bbdd30600ac981701e92a4cd7b736fd0bfed +size 65958 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/e417ae35ab07134888be901c201d54cd_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbefeb37d6bee9f45390e5149628ceb68b49680c --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/e417ae35ab07134888be901c201d54cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80b39fbe07a40b4e98b3f5d3750a2b52a88340290a096aecc6bb4dc2b77f7208 +size 27258 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..436da45afeb447e57e78ece3451cc159ca1ea010 --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:848300dabb824f731342024c6a672aeb6357bb068a70acc42e93445d1e7edb1e +size 3794 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/H/T-REC-H.811-201711-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66f2741059ff21c69ca3864f82ba12c3fb070fee --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d0656097cdf78618ad6cf88d5cd1ed9602407be1806eb9697007f4d9e9d1976 +size 96359 diff --git a/marked/H/T-REC-H.811-201711-I_PDF-E/raw.md b/marked/H/T-REC-H.811-201711-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cfa40c9f8d1d462892461e35f94f890d477d6ea5 --- /dev/null +++ b/marked/H/T-REC-H.811-201711-I_PDF-E/raw.md @@ -0,0 +1,2992 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.811** + +(11/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – Personal +health systems + +--- + +**Interoperability design guidelines for personal +connected health systems: +Personal Health Devices interface** + +Recommendation ITU-T H.811 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.811 + +## Interoperability design guidelines for personal connected health systems: Personal Health Devices interface + +## Summary + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for personal connected health services. The Continua Design Guidelines also contains design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. + +ITU-T H.811 focuses on the Personal Health Devices interface (PHD-IF). + +ITU-T H.811 is part of the "ITU-T H.810 interoperability design guidelines for personal connected health systems" subseries that covers the following areas: + +- ITU-T H.810 – Interoperability design guidelines for personal connected health systems: Introduction +- ITU-T H.811 – Interoperability design guidelines for personal connected health systems: Personal Health Devices interface (this design guidelines document) +- ITU-T H.812 – Interoperability design guidelines for personal connected health systems: Services interface +- ITU-T H.812.1 – Interoperability design guidelines for personal connected health systems: Services interface: Observation Upload capability +- ITU-T H.812.2 – Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability +- ITU-T H.812.3 – Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability +- ITU-T H.812.4 – Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability +- ITU-T H.813 – Interoperability design guidelines for personal connected health systems: Healthcare Information System interface + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.811 | 2015-11-29 | 16 | 11.1002/1000/12652 | +| 2.0 | ITU-T H.811 | 2016-07-14 | 16 | 11.1002/1000/12912 | +| 3.0 | ITU-T H.811 | 2017-11-29 | 16 | 11.1002/1000/13414 | + +### Keywords + +CDG, Continua Design Guidelines, healthcare information systems, personal connected health systems, personal health devices, services. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|--------|----------------------------------------------------------|----| +| 0 | Introduction ..... | 1 | +| 0.1 | Organization ..... | 1 | +| 0.2 | Guideline releases and versioning ..... | 1 | +| 0.3 | What's new? ..... | 2 | +| 1 | Scope ..... | 3 | +| 2 | References ..... | 5 | +| 2.1 | Equivalent IEEE and ISO specifications ..... | 5 | +| 3 | Definitions ..... | 6 | +| 4 | Abbreviations and acronyms ..... | 6 | +| 5 | Conventions ..... | 6 | +| 6 | Common X73 Personal Health Devices guidelines ..... | 6 | +| 6.1 | X73 interface architecture (informative) ..... | 6 | +| 6.1.1 | Introduction to X73 interface ..... | 6 | +| 6.1.2 | Overview of the X73 interface ..... | 7 | +| 6.1.3 | Common data/messaging layer and selected standards ..... | 8 | +| 6.1.4 | Transport protocols and selected standards ..... | 8 | +| 6.2 | Common X73 layer guidelines ..... | 9 | +| 6.2.1 | Applicable interfaces ..... | 9 | +| 6.2.2 | Exchange protocol ..... | 9 | +| 6.2.3 | Standard configuration support ..... | 24 | +| 6.2.4 | Sensor component – communication capabilities ..... | 25 | +| 6.2.5 | Sensor component multi-function devices ..... | 25 | +| 6.3 | X73 devices ..... | 26 | +| 6.3.1 | Pulse oximeter ..... | 26 | +| 6.3.2 | Basic 1-3 lead ECG ..... | 30 | +| 6.3.3 | Heart-rate sensor ..... | 31 | +| 6.3.4 | Blood pressure monitor ..... | 34 | +| 6.3.5 | Thermometer ..... | 34 | +| 6.3.6 | Weighing scales ..... | 35 | +| 6.3.7 | Glucose meter ..... | 35 | +| 6.3.8 | INR meter ..... | 35 | +| 6.3.9 | Body composition analyser ..... | 35 | +| 6.3.10 | Peak expiratory flow monitor ..... | 36 | +| 6.3.11 | Cardiovascular fitness ..... | 36 | + +| | Page | +|---------------------------------------------------------------|-------------| +| 6.3.12 Cardiovascular step counter ..... | 36 | +| 6.3.13 Strength fitness..... | 37 | +| 6.3.14 Activity hub ..... | 37 | +| 6.3.15 Fall sensor ..... | 37 | +| 6.3.16 Motion sensor..... | 38 | +| 6.3.17 Enuresis sensor..... | 38 | +| 6.3.18 Contact closure sensor ..... | 39 | +| 6.3.19 Switch sensor ..... | 39 | +| 6.3.20 Dosage sensor ..... | 40 | +| 6.3.21 Water sensor..... | 40 | +| 6.3.22 Smoke sensor ..... | 41 | +| 6.3.23 Property exit sensor..... | 41 | +| 6.3.24 Temperature sensor ..... | 42 | +| 6.3.25 Usage sensor ..... | 42 | +| 6.3.26 PERS sensor..... | 43 | +| 6.3.27 CO sensor..... | 43 | +| 6.3.28 Gas sensor ..... | 44 | +| 6.3.29 Adherence monitor..... | 44 | +| 6.3.30 Sleep apnoea breathing therapy equipment (SABTE) ..... | 44 | +| 6.3.31 Continuous glucose monitor (CGM) ..... | 44 | +| 6.3.32 Insulin pump (IP) ..... | 45 | +| 6.3.33 Power status monitor (PSM)..... | 45 | +| 7 NFC interface design guidelines ..... | 45 | +| 7.1 NFC interface architecture (informative)..... | 45 | +| 7.1.1 Overview of NFC interface..... | 46 | +| 7.1.2 Transport protocols and selected standards ..... | 47 | +| 7.1.3 Exchange protocols and selected standards ..... | 47 | +| 7.1.4 Device communication styles ..... | 47 | +| 7.1.5 NFC interface security ..... | 47 | +| 7.2 NFC interface guidelines..... | 47 | +| 7.2.1 NFC PHD to PHG linkage ..... | 47 | +| 7.2.2 NFC user experience..... | 48 | +| 7.2.3 NFC Personal Health Device communication ..... | 48 | +| 7.2.4 Multi-function devices ..... | 48 | +| 7.2.5 NFC quality of service ..... | 49 | +| 7.3 NFC Certified Capability Classes ..... | 49 | +| 8 USB interface design guidelines ..... | 51 | +| 8.1 USB interface architecture (informative)..... | 51 | +| 8.1.1 Overview of USB interface..... | 51 | + +| | Page | | +|--------|-------------------------------------------------------------|----| +| 8.1.2 | Exchange protocols and selected standards ..... | 52 | +| 8.1.3 | USB device communication styles ..... | 52 | +| 8.1.4 | USB-IF security ..... | 52 | +| 8.2 | USB device and interface guidelines ..... | 52 | +| 8.2.1 | USB device to PHG linkage ..... | 52 | +| 8.2.2 | USB general requirements ..... | 52 | +| 8.2.3 | USB map to IEEE 11073-20601 ..... | 53 | +| 8.2.4 | Sending metadata via USB PHDC ..... | 54 | +| 8.2.5 | USB quality of service ..... | 55 | +| 8.2.6 | USB multi-function devices ..... | 55 | +| 8.2.7 | USB connectors ..... | 56 | +| 8.2.8 | USB data rates ..... | 57 | +| 8.3 | USB Certified Capability Classes ..... | 57 | +| 9 | Bluetooth BR/EDR interface design guidelines ..... | 59 | +| 9.1 | Bluetooth BR/EDR interface architecture (informative) ..... | 59 | +| 9.1.1 | Overview of Bluetooth BR/EDR interface ..... | 60 | +| 9.2 | Bluetooth BR/EDR interface guidelines ..... | 60 | +| 9.2.1 | Bluetooth BR/EDR PHD to PHG linkage ..... | 60 | +| 9.2.2 | Bluetooth health device profile ..... | 61 | +| 9.2.3 | Discovery and pairing ..... | 61 | +| 9.2.4 | Bluetooth BR/EDR discoverable mode ..... | 65 | +| 9.2.5 | Notifying the user ..... | 66 | +| 9.2.6 | Quality of service ..... | 67 | +| 9.2.7 | Secure simple pairing debug mode ..... | 68 | +| 9.3 | Bluetooth BR/EDR Certified Capability Classes ..... | 68 | +| 10 | ZigBee interface design guidelines ..... | 70 | +| 10.1 | ZigBee interface architecture (informative) ..... | 70 | +| 10.1.1 | Introduction to the ZigBee interface ..... | 70 | +| 10.1.2 | Scope of the ZigBee interface ..... | 71 | +| 10.1.3 | Overview of the ZigBee interface ..... | 72 | +| 10.1.4 | Transport protocol and selected standards ..... | 72 | +| 10.1.5 | Data exchange protocol and selected standards ..... | 73 | +| 10.2 | ZigBee interface guidelines ..... | 73 | +| 10.2.1 | ZigBee transport layer ..... | 73 | +| 10.2.2 | ZigBee data/messaging layer ..... | 74 | +| 10.3 | ZigBee Certified Capability Classes ..... | 78 | +| 11 | Bluetooth low energy (LE) design guidelines ..... | 80 | +| 11.1 | Architecture of Bluetooth LE (informative) ..... | 80 | + +| | Page | +|------------------------------------------------------------------------------------------------|-------------| +| 11.1.1 Introduction..... | 80 | +| 11.1.2 Overview..... | 81 | +| 11.2 Bluetooth LE interface guidelines..... | 83 | +| 11.2.1 Bluetooth LE services and profiles..... | 83 | +| 11.2.2 Device discovery, connection establishment, pairing, service discovery and bonding..... | 83 | +| 11.2.3 User notification..... | 88 | +| 11.2.4 Security, authentication and privacy..... | 89 | +| 11.2.5 Device information requirements..... | 91 | +| 11.2.6 Date and time requirements..... | 92 | +| 11.2.7 Certification and regulatory aspects..... | 92 | +| 11.2.8 Transcoding..... | 93 | +| 11.3 Bluetooth LE PHDs and PHGs..... | 94 | +| 11.3.1 Blood pressure monitor..... | 94 | +| 11.3.2 Thermometer..... | 95 | +| 11.3.3 Heart-rate sensor..... | 95 | +| 11.3.4 Glucose meter..... | 95 | +| 11.3.5 Weighing scale..... | 96 | +| 11.3.6 Continuous glucose monitor..... | 96 | +| 11.3.7 Pulse oximeter..... | 97 | +| 11.4 Bluetooth LE Certified Capability Classes..... | 97 | +| Appendix I Additional Bluetooth BR/EDR information..... | 98 | +| 1.1 Bluetooth terminology..... | 98 | +| 1.2 Bluetooth BR/EDR pairing methods..... | 98 | +| 1.3 Bluetooth BR/EDR legacy pairing procedures..... | 99 | +| 1.4 Supporting Bluetooth OEM subsystems and components..... | 99 | +| 1.5 Quality of service bins for Bluetooth..... | 99 | +| Appendix II Additional ZigBee information..... | 102 | +| II.1 ZigBee networking..... | 102 | +| II.2 ZigBee pairing process/service discovery types..... | 102 | +| II.3 ZigBee security..... | 103 | +| Appendix III Recommendation for use of generic USB drivers..... | 104 | +| Bibliography..... | 105 | + +## List of Tables + +###### Page + +| | | +|-------------------------------------------------------------------------------------------|----| +| Table 6-1 – Applicable interfaces ..... | 9 | +| Table 6-2 –X73 wired/wireless general requirements ..... | 9 | +| Table 6-3 – Minimally supported base protocol version(s) for device specializations ..... | 11 | +| Table 6-4 – Correspondence between 11073-20601 protocol versions and specifications ..... | 11 | +| Table 6-5 – Communication capabilities – General ..... | 12 | +| Table 6-6 – Communication capabilities – Event reporting ..... | 12 | +| Table 6-8 – Communication capabilities – Time setting ..... | 13 | +| Table 6-9 – Device information ..... | 15 | +| Table 6-10 – Unsupported service component ..... | 17 | +| Table 6-12 – Bidirectional transport layer: Message type/QoS bin mapping ..... | 19 | +| Table 6-13 – Regulatory / certification information ..... | 21 | +| Table 6-14 – Manager conformance ..... | 23 | +| Table 6-15 – Nomenclature codes ..... | 23 | +| Table 6-16 – User identification ..... | 23 | +| Table 6-17 – Communication capabilities – general ..... | 24 | +| Table 6-18 – Communication capabilities association and configuration ..... | 25 | +| Table 6-19 – Multi-function devices ..... | 25 | +| Table 6-20 – Pulse oximeter – General requirements ..... | 26 | +| Table 6-21 – Pulse Oximeter PM-Store measurement requirements ..... | 29 | +| Table 6-22 – Pulse Oximeter PM-Store object attributes guideline ..... | 29 | +| Table 6-23 – Basic 1-3 lead ECG – General requirements ..... | 30 | +| Table 6-24 – ECG PM-Store measurement requirements ..... | 31 | +| Table 6-25 – ECG PM-Store object attributes guidelines ..... | 31 | +| Table 6-26 – Heart-rate sensor – General requirements ..... | 32 | +| Table 6-27– Heart-rate sensor PM-Store measurement requirements ..... | 34 | +| Table 6-28 – PM-Store object attributes guidelines ..... | 34 | +| Table 6-29 – Blood pressure monitor – General requirements ..... | 34 | +| Table 6-30 – Thermometer – General requirements ..... | 35 | +| Table 6-31 – Weighing scales – General requirements ..... | 35 | +| Table 6-32 – Glucose meter – General requirements ..... | 35 | +| Table 6-33 – INR meter – General requirements ..... | 35 | +| Table 6-34 – Body composition analyzer – General requirements ..... | 35 | +| Table 6-35 – Peak flow monitor – General requirements ..... | 36 | +| Table 6-36 – Cardiovascular fitness – General requirements ..... | 36 | +| Table 6-37 – Cardiovascular step counter – General requirements ..... | 36 | + +| | Page | +|-----------------------------------------------------------------------|-------------| +| Table 6-38 – Strength fitness – General requirements ..... | 37 | +| Table 6-39 – Activity hub – General requirements ..... | 37 | +| Table 6-40 – Fall sensor – General requirements ..... | 38 | +| Table 6-41 – Motion sensor – General requirements ..... | 38 | +| Table 6-42 – Enuresis sensor – General requirements ..... | 39 | +| Table 6-43 – Contact closure sensor – General requirements ..... | 39 | +| Table 6-44 – Switch use sensor – General requirements ..... | 40 | +| Table 6-45 – Dosage sensor – General requirements ..... | 40 | +| Table 6-46 – Water sensor – General requirements ..... | 41 | +| Table 6-47 – Smoke sensor – General requirements ..... | 41 | +| Table 6-48 – Property exit sensor – General requirements ..... | 42 | +| Table 6-49 – Temperature sensor – General requirements ..... | 42 | +| Table 6-50 – Usage sensor – General requirements ..... | 43 | +| Table 6-51 – PERS sensor – General requirements ..... | 43 | +| Table 6-52 – CO sensor – General requirements ..... | 43 | +| Table 6-53 – Gas sensor – General requirements ..... | 44 | +| Table 6-54 – Adherence monitor – General requirements ..... | 44 | +| Table 6-55 – SABTE – General requirements ..... | 44 | +| Table 6-56 – Continuous Glucose Monitor General Requirements ..... | 45 | +| Table 6-57 – Insulin pump - General requirements ..... | 45 | +| Table 7-1 – NFC PHD to PHG linkage ..... | 47 | +| Table 7-2 – NFC user experience ..... | 48 | +| Table 7-3 – NFC personal health device communication map ..... | 48 | +| Table 7-4 – NFC multi-function devices ..... | 49 | +| Table 7-5 – NFC quality of service ..... | 49 | +| Table 7-6 – NFC Certified Capability Classes ..... | 49 | +| Table 8-1 – USB device to PHG linkage ..... | 52 | +| Table 8-2 – USB personal healthcare capability class v1.0 map ..... | 53 | +| Table 8-3 – ISO/IEEE 11073-20601 messaging layer ..... | 53 | +| Table 8-4 – Using USB PHDC metadata/QoS feature ..... | 54 | +| Table 8-5 – Mapping of USB PHDC QoS bins into Continua QoS bins ..... | 55 | +| Table 8-6 – USB multi-function devices ..... | 56 | +| Table 8-7 – USB connectors ..... | 56 | +| Table 8-8 – USB data rates ..... | 57 | +| Table 8-9 – USB Certified Capability Classes ..... | 58 | +| Table 9-1 – Bluetooth BR/EDR PHD to PHG linkage ..... | 60 | + +| | Page | +|----------------------------------------------------------------------------------|-------------| +| Table 9-2 – Bluetooth health device profile map ..... | 61 | +| Table 9-3 – Bluetooth BR/EDR pairing guidelines ..... | 62 | +| Table 9-4 – Bluetooth BR/EDR pairing in non-discoverable states ..... | 64 | +| Table 9-5 – Bluetooth BR/EDR pairing data ..... | 65 | +| Table 9-6 – Bluetooth BR/EDR discovery disable ..... | 65 | +| Table 9-7 – Bluetooth SDP access ..... | 66 | +| Table 9-8 – Bluetooth SDP record ..... | 66 | +| Table 9-9 – Bluetooth BR/EDR user notification ..... | 67 | +| Table 9-10 – Bluetooth BR/EDR authentication/security failure notification ..... | 67 | +| Table 9-11 – Bluetooth BR/EDR quality of service ..... | 67 | +| Table 9-12 – Bluetooth BR/EDR error detection ..... | 68 | +| Table 9-13 – Bluetooth BR/EDR Certified Capability Classes ..... | 68 | +| Table 10-1 – ZigBee health care profile map ..... | 73 | +| Table 10-2 – ZigBee quality of service ..... | 74 | +| Table 10-3 – ZigBee multiple connections ..... | 74 | +| Table 10-4 – ZigBee dominant association ..... | 75 | +| Table 10-5 – ZigBee time-stamping ..... | 77 | +| Table 10-6 – ZigBee timeout management ..... | 78 | +| Table 10-7 – ZigBee Certified Capability Classes ..... | 78 | +| Table 11-1 – Bluetooth LE transport ..... | 83 | +| Table 11-2 – Bluetooth LE device discovery, pairing and service discovery ..... | 84 | +| Table 11-3 – Bluetooth LE user notification ..... | 88 | +| Table 11-4 – Bluetooth LE authentication ..... | 89 | +| Table 11-5 – Bluetooth LE OEM requirements ..... | 91 | +| Table 11-6 – Bluetooth LE date and time requirements ..... | 92 | +| Table 11-7 – Bluetooth LE certification and regulation ..... | 93 | +| Table 11-8 – Bluetooth LE transcoding ..... | 94 | +| Table 11-9 – Blood pressure general requirements for Bluetooth LE ..... | 94 | +| Table 11-10 – Thermometer general requirements for Bluetooth LE ..... | 95 | +| Table 11-11 – Heart-rate sensor general requirements for Bluetooth LE ..... | 95 | +| Table 11-12 – Glucose meter general requirements for Bluetooth LE ..... | 95 | +| Table 11-13 – Weighing scale general requirements for Bluetooth LE ..... | 96 | +| Table 11-14 – CGM general requirements for Bluetooth LE ..... | 96 | +| Table 11-15 – Pulse Oximeter general requirements for Bluetooth LE ..... | 97 | +| Table 11-16 – Bluetooth LE Certified Capability Classes ..... | 97 | + +## List of Figures + +### Page + +| | | +|-------------------------------------------------------------------------------------|----| +| Figure 1-1 – Personal Health Devices interfaces in the Continua architecture ..... | 3 | +| Figure 6-1 – X73-IF in the Continua E2E architecture ..... | 7 | +| Figure 6-2 – X73-IF protocol stack ..... | 8 | +| Figure 6-3 – ASN.1 definition of Continua certification structures ..... | 21 | +| Figure 6-4 – PM-Store usage for pulse oximeter ..... | 27 | +| Figure 6-5 – Alternate PM-segment organization ..... | 28 | +| Figure 6-6 – PM-store usage example for heart-rate sensor ..... | 33 | +| Figure 7-1 – NFC interface context ..... | 46 | +| Figure 7-2 – NFC interface stack ..... | 46 | +| Figure 8-1 – USB interface context ..... | 51 | +| Figure 8-2 – USB PHDC mapping to IEEE 11073-20601 associations ..... | 56 | +| Figure 9-1 – Bluetooth interface context ..... | 60 | +| Figure 9-2 – Continua Bluetooth BR/EDR pairing process for service components ..... | 64 | +| Figure 9-3 – Continua Bluetooth BR/EDR pairing process for client components ..... | 64 | +| Figure 10-1 – ZigBee interface ..... | 70 | +| Figure 10-2 – ZigBee conceptual set-up ..... | 72 | +| Figure 11-1 – Bluetooth LE interface ..... | 81 | +| Figure 11-2 – Bluetooth LE interface stack ..... | 82 | + +### Interoperability design guidelines for personal connected health systems: Personal Health Devices interface + +#### 0 Introduction + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for personal connected health services. The Continua Design Guidelines also contains design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. These guidelines focus on the Personal Health Devices interface (PHD-IF). + +This design guidelines document is part of the "ITU-T H.810 interoperability design guidelines for personal health systems" subseries. See [ITU-T H.810] for more details. + +#### 0.1 Organization + +This design guidelines document is organized in the following manner: + +- **Clauses 0-5: Introduction and terminology** – These clauses provide useful background information to help understand the structure of the design specifications. +- **Clause 6: Common X73 PHD-IF design guidelines** – This clause provides an overview of the common elements of the PHD-IF architecture with design guidelines that apply to all Personal Health Devices (PHDs) and Personal Health Gateways (PHGs) implementing the PHD-IF and using an IEEE 11073 PHD device specialization (X73 device). +- **Clause 7: NFC design guidelines** – This clause is an overview of the near-field communication (NFC) architecture along with the design guidelines for PHDs and PHGs that use NFC and IEEE 11073 PHD (X73) to implement the PHD-IF. +- **Clause 8: Bluetooth BR/EDR design guidelines** – This clause is an overview of the Bluetooth BR/EDR (basic rate / enhanced data rate) architecture along with the design guidelines for PHDs and PHGs that use Bluetooth BR/EDR and X73 to implement the PHD-IF. +- **Clause 9: USB design guidelines** – This clause is an overview of the universal serial bus (USB) architecture along with design guidelines for PHDs and PHGs that use USB and IEEE 11073 PHD to implement the PHD-IF. +- **Clause 10: ZigBee design guidelines** – This clause is an overview of the ZigBee architecture with design guidelines for PHDs and PHGs that use ZigBee and X73 to implement the PHD-IF. +- **Clause 11: Bluetooth LE design guidelines** – This clause is an overview of the Bluetooth LE (low energy) architecture along with the design guidelines for PHDs and PHGs that use Bluetooth LE to implement the PHD-IF. This clause does not refer to IEEE 11073 PHD. + +#### 0.2 Guideline releases and versioning + +Information on releases and versioning of these guidelines can be found in Table 0-1. + +Note that since 2017-Q2 this design guideline document is released independently of the other Continua design guideline documents mentioned in [ITU-T H.810]. Since that date this design guideline document has its own version number. This version number is used in the communication between a PHD and PHG as defined in the Regulatory Certification data list. See clauses 6.2.2.6 and 11.2.7. + +**Table 0-1 – Guideline releases and corresponding version numbers** + +| Continua ITU-T H.811
    design guidelines –
    external release date     | Also known as | Major
    version     | Minor
    version     | +|-------------------------------------------------------------------------------|------------------------------------------------|--------------------------|--------------------------| +| 1.0 | | 1 | 0 | +| 2010 | 1.5 | 1 | 5 | +| 2010 + Errata | | 1 | 6 | +| 2011 | 2.0, Adrenaline | 2 | 0 | +| 2011 + Errata | | 2 | 1 | +| 2012 | Catalyst | 3 | 0 | +| 2012 + Errata | | 3 | 1 | +| 2014 | Endorphin | 4 | 0 | +| 2014 + Errata | | 4 | 1 | +| 2015 | Genome | 5 | 0 | +| 2015 + Errata | | 5 | 1 | +| 2016 | Iris | 6 | 0 | +| 2016 + Errata | Iris with architectural refresh | 6 | 1 | +| 2017 | Keratin | 7 | 0 | +| 2017-Q2 | Power Status Monitoring update | 8 | 0 | +| 2017-Q3 | Fixes for Bluetooth LE interoperability issues | 8 | 1 | + +### **0.3 What's new?** + +This update (v8.1) includes the following new items compared to v7.0: + +- Support for the power status monitor device specialization. See clause 6.3.33. +- Fixed a bug: the IEEE 11073-10441 cardiovascular fitness and step counter device specialization requires v3 of the IEEE 11073-20601 protocol. +- Made this guideline document more stand-alone from [ITU-T H.810], allowing new releases without having to release a new version of [ITU-T H.810]. +- Fixes for a number of identified Bluetooth LE interoperability issues related to pairing and security. + +## 1 Scope + +This design guidelines focuses on the Personal Health Devices interface (PHD-IF) that consists of the following sub-interfaces: + +- **X73 interface (X73-IF)** – an interface based on ISO/IEEE 11073-20601 and a supported transport technology. Supported transport technologies are: + - NFC + - Bluetooth BR/EDR + - USB + - ZigBee +- **Bluetooth LE interface (BLE-IF)** – an interface based on a Bluetooth LE as transport technology and one or more (application level) services and profiles defined by the Bluetooth Special Interest Group (SIG). + +The PHD-IF and other Continua interfaces are defined in the Continua architecture in [ITU-T H.810]. Figure 1-1 illustrates this architecture and shows the focus on the PHD-IF. + +![Diagram of the Continua architecture showing the flow of data from Personal Health Devices through a Personal Health Gateway to a Health & Fitness service and then to a Healthcare Information System.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +The diagram illustrates the Continua architecture flow. On the left, a box labeled 'Personal Health Device' contains two sub-sections: 'X73 device' (with icons of various sensors) and 'Bluetooth LE device' (with icons of a heart rate monitor and a blood pressure cuff). These connect to a vertical orange box labeled 'Personal Health Devices interface'. This interface is divided into two main sections: 'IEEE ISO X73-IF' which lists 'NFC forum', 'ZigBee', 'Bluetooth', and 'USB'; and 'BLE-IF' which lists 'Bluetooth smart'. Both sections connect to a central box labeled 'Personal Health Gateway (PHG)' containing icons of a smartphone, tablet, and laptop. The PHG connects to a vertical grey box labeled 'Services interface', which lists the protocols 'HL7', 'IHE', 'OASIS', 'IETF', and 'W3C'. This interface connects to a central box labeled 'Health & Fitness service' containing a cloud icon with a building. This service connects to another vertical grey box labeled 'HIS interface', which also lists the protocols 'HL7', 'IHE', 'OASIS', 'IETF', and 'W3C'. Finally, the HIS interface connects to a box labeled 'Healthcare Information System (HIS)' containing icons of a hospital, a blood test tube, and a medical bag. The diagram is labeled 'H.811(17)\_F1-1' in the bottom right corner. + +Diagram of the Continua architecture showing the flow of data from Personal Health Devices through a Personal Health Gateway to a Health & Fitness service and then to a Healthcare Information System. + +**Figure 1-1 – Personal Health Devices interfaces in the Continua architecture** + +These guidelines cover the following X73 devices that can use one of the X73-IF supported transport technologies (ZigBee, NFC, USB and Bluetooth BR/EDR): + +- activity hub +- adherence monitor +- basic 1-3 lead ECG sensor +- blood pressure monitor +- body composition analyser +- cardiovascular fitness +- CO sensor + +- contact closure sensor +- continuous glucose monitor +- dosage sensor +- enuresis sensor +- fall sensor +- gas sensor +- glucose meter +- heart-rate sensor +- INR meter +- insulin pump +- motion sensor +- peak expiratory flow monitor +- PERS sensor +- power status monitor +- property exit sensor +- pulse oximeter +- sleep apnoea breathing therapy equipment (SABTE) +- smoke sensor +- step counter +- strength fitness +- switch sensor +- temperature sensor +- thermometer +- usage sensor +- water sensor +- weighing scales + +These guidelines also cover a second group of Personal Health Device types that use Bluetooth LE technology. This group consists of: + +- blood pressure monitor +- continuous glucose monitor +- glucose meter +- heart-rate sensor +- pulse oximeter +- thermometer +- weighing scales. + +## 2 + +## References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.810] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal connected health systems: Introduction*. + +All other referenced documents can be found in clause 2 of [ITU-T H.810]. + +### 2.1 + +### Equivalent IEEE and ISO specifications + +ISO adopts certain IEEE specifications under the "ISO/IEEE Partner Standards Development Organization Cooperation Agreement". Table 2-1 shows ISO equivalents of IEEE 11073 Personal Health Device specifications referenced by the Continua Design Guidelines (CDG). Typically ISO versions are published one or more years after the IEEE version. + +**Table 2-1 – ISO equivalent specifications for IEEE 11073 Personal Health Device specifications** + +| Description | IEEE 11073 standard | ISO equivalent | +|--------------------------------------------------------|------------------------|--------------------------------------| +| 10101 Nomenclature | IEEE 11073-10101-2004 | ISO/IEEE 11073-10101:2004 | +| 10101 Nomenclature - additions | IEEE 11073-10101a-2015 | - | +| 20601 Protocol (v1) | IEEE 11073-20601-2008 | ISO/IEEE 11073-20601:2010 | +| 20601 Protocol Amendment (v2) | IEEE 11073-20601A-2010 | ISO/IEEE 11073-20601:2010/Amd 1:2015 | +| 20601 Protocol (v3) | IEEE 11073-20601-2014 | - | +| 10404 Pulse oximeter | IEEE 11073-10404-2008 | ISO/IEEE 11073-10404:2010 | +| 10406 Basic Electrocardiograph (ECG) (1 to 3-lead ECG) | IEEE 11073-10406-2011 | ISO/IEEE 11073-10406:2012 | +| 10407 Blood Pressure Monitor | IEEE 11073-10407-2008 | ISO/IEEE 11073-10407:2010 | +| 10408 Thermometer | IEEE 11073-10408-2008 | ISO/IEEE 11073-10408:2010 | +| 10415 Weighing scale | IEEE 11073-10415-2008 | ISO/IEEE 11073-10415:2010 | +| 10417 Glucose meter | IEEE 11073-10417-2015 | - | +| 10418 INR monitor | IEEE 11073-10418-2011 | ISO/IEEE 11073-10418:2014 | +| 10419 Insulin Pump | IEEE 11073-10419-2015 | ISO/IEEE 11073-10419:2016 | +| 10420 Body composition analyser | IEEE 11073-10420-2010 | ISO/IEEE 11073-10420:2012 | +| 10421 Peak expiratory flow monitor | IEEE 11073-10421-2010 | ISO/IEEE 11073-10421:2012 | +| 10424 Sleep Apnoea Breathing Therapy Equipment | IEEE 11073-10424-2014 | ISO/IEEE 11073-10424:2016 | +| 10425 Continuous Glucose Monitor | IEEE 11073-10425-2015 | ISO/IEEE 11073-10425:2016 | +| 10427 Power Status Monitor of Personal Health Devices | IEEE 11073-10427-2016 | - | + +**Table 2-1 – ISO equivalent specifications for IEEE 11073 Personal Health Device specifications** + +| Description | IEEE 11073 standard | ISO equivalent | +|---------------------------------------------------|----------------------------|---------------------------| +| 10441 Cardiovascular Fitness and Activity monitor | IEEE 11073-10441-2013 | ISO/IEEE 11073-10441:2015 | +| 10442 Strength fitness equipment | IEEE 11073-10442-2008 | ISO/IEEE 11073-10442:2015 | +| 10471 Independent living activity hub | IEEE 11073-10471-2008 | ISO/IEEE 11073-10471:2010 | +| 10472 Medication Monitor | IEEE 11073-10472-2010 | ISO/IEEE 11073-10472:2012 | + +### **3 Definitions** + +This design guidelines document uses terms defined in [ITU-T H.810]. + +### **4 Abbreviations and acronyms** + +This design guidelines document uses abbreviations and acronyms defined in [ITU-T H.810]. + +### **5 Conventions** + +This design guidelines document follows the conventions defined in [ITU-T H.810]. + +### **6 Common X73 Personal Health Devices guidelines** + +NOTE – This clause (except for clause 6.2.2.6) does not apply to Bluetooth LE devices. + +#### **6.1 X73 interface architecture (informative)** + +##### **6.1.1 Introduction to X73 interface** + +This clause lists the application layer design guidelines that are common to the X73 PHD. This clause does not apply to the BLE-IF subclass of the PHD-IF (see Figure 6-2). See clauses 7 to 10 for the specific guidelines per supported transport protocol. + +![Diagram of the Continua E2E architecture showing the flow of data from Personal Health Devices through a Personal Health Gateway to a Health & Fitness service and then to a Healthcare Information System (HIS).](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram illustrates the Continua E2E architecture. On the left, two boxes represent 'Personal Health Devices': one for 'X73 device' (containing icons of various sensors) and another for 'Bluetooth LE device'. These connect to a central 'Personal Health Devices interface' box. This interface is divided into two sections: an upper section with standards IEEE, ISO, X73-IF, NFC forum, ZigBee, Bluetooth, USB, and BLE-IF; and a lower section with Bluetooth LE. The upper section is circled in red. The interface connects to a 'Personal Health Gateway (PHG)' box. The PHG connects to a 'Services interface' box, which lists standards HL7, IHE, OASIS, IETF, and W3C. The Services interface connects to a 'Health & Fitness service' box (represented by a cloud icon). This service connects to an 'HIS interface' box, which also lists standards HL7, IHE, OASIS, IETF, and W3C. Finally, the HIS interface connects to a 'Healthcare Information System (HIS)' box (containing icons of a hospital, a blood bag, and a medical professional). A label 'H.811(17)\_FB-1' is at the bottom right. + +Diagram of the Continua E2E architecture showing the flow of data from Personal Health Devices through a Personal Health Gateway to a Health & Fitness service and then to a Healthcare Information System (HIS). + +Figure 6-1 – X73-IF in the Continua E2E architecture + +### 6.1.2 Overview of the X73 interface + +The X73-IF is composed of different layers. Appropriate standards are selected for the individual layers and establish interoperability in the personal health ecosystem. Figure 6-2 gives an overview of the protocol stack for the X73-IF. + +![Figure 6-2 – X73-IF protocol stack diagram showing layers from IEEE 11073 PHD communication down to transport protocols like Bluetooth, USB, ZigBee, and NFC, with various device specializations in between.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +The diagram illustrates the X73-IF protocol stack. At the top is the **IEEE 11073 PHD communication** layer. Below it is a layer for **104xx device specializations**, which includes a vertical list of 18 specific device types: 10404 pulse oximeter, 10406 basic ECG (1-3 lead), 10407 blood pressure monitor, 10408 thermometer, 10415 weighing-scale, 10417 glucose meter, 10418 INR monitor, 10419 insulin pump, 10420 body composition analyser, 10421 peak expiratory flow monitor, 10421 peak expiratory flow monitor, 10424 sleep apnea breathing therapy equipment, 10425 continuous glucose monitor, 10441 cardiovascular fitness and activity monitor, 10442 strength fitness equipment, 10471 independent living activity hub, and 10472 medication monitor. Below this is the **20601 optimized exchange protocol** layer. The bottom layer consists of four transport protocols: **Bluetooth HD profile**, **USB PHD class**, **ZigBee HC profile**, and **NFC PHD class**. To the right of the main stack, there is a vertical column representing the **IEEE 11073 application protocol (ISO layer 6, 7)**, which sits above the **Transport specific adaptation layer (ISO layer 5)** and the **Base transport protocol (ISO layer 4)**. Below the base transport protocol, the text **H.811(16)\_F6-2** is shown. + +Figure 6-2 – X73-IF protocol stack diagram showing layers from IEEE 11073 PHD communication down to transport protocols like Bluetooth, USB, ZigBee, and NFC, with various device specializations in between. + +**Figure 6-2 – X73-IF protocol stack** + +### 6.1.3 Common data/messaging layer and selected standards + +Widely supported transport technologies and profiles have been selected for wireless and wired versions of the X73-IF. In addition for the application level data/messaging there is considerable commonality. A common solution has therefore been selected to serve as the data/messaging layer on top of the supported transport protocols. + +The IEEE 11073-20601 optimized exchange protocol described in [IEEE 11073-20601] has been selected as the basis of the application protocol for the X73-IF. This internationally harmonized standard provides an interoperable messaging protocol and has definitions and structures in place to convert from an abstract data format into a transmission format. Thus, a consistent data exchange layer is enabled for the X73-IF. + +The IEEE 11073-20601 protocol (see [IEEE 11073-20601]) acts as a bridge between device-specific information defined in individual so-called device specializations and the underlying transports to provide a framework for optimized exchange of interoperable data units. The selected device specialization standards specify the data model and nomenclature terms to be used for individual devices. The device specializations are also illustrated in Figure 6-2. + +### 6.1.4 Transport protocols and selected standards + +The following wired and wireless solutions have been selected to serve as CDG transport for the X73-IF: + +- Bluetooth BR/EDR – Bluetooth health device profile +- USB – USB personal healthcare device class +- NFC – NFC Personal Health Device communication +- ZigBee – ZigBee health care profile + +The selected protocols for the transport layer ensure interoperable set-up and tear-down of the communication channel for the transfer of control and data messages across all domains. + +## 6.2 Common X73 layer guidelines + +### 6.2.1 Applicable interfaces + +This clause contains a general design guideline for applicable interfaces. Table 6-1 lists the CDG network interfaces for which the common data/messaging layer guidelines described in clauses 6.2.2 to 6.2.3 are applicable. + +**Table 6-1 – Applicable interfaces** + +| Name | Description | Comments | +|-----------------------------------|---------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_Applicable_Interfaces | Continua X73-IF service and client components shall implement the guidelines in Table 6-2. | The referenced tables contain guidelines on the data/messaging layer, which are consistent for the listed interfaces. The BLE-IF uses a different data/messaging layer (see clause 6.1.4). | + +### 6.2.2 Exchange protocol + +#### 6.2.2.1 X73 component – general requirements + +This clause contains general design guidelines, listed in Table 6-2, on the implementation of the [IEEE 11073-20601] specifications. All requirements in clause 6.2.2 refer to these specifications. + +Table 6-3 shows minimally supported base protocol version(s) for device specializations and Table 6-4 shows the correspondence between 11073-20601 protocol versions and the respective specifications. + +**Table 6-2 –X73 wired/wireless general requirements** + +| Name | Description | Comments | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_Reqt | Continua X73-IF service and client components shall implement at least the version or versions of the [ISO/IEEE 11073-20601] specifications as defined in Table 6-3. | The version or versions of [IEEE 11073-20601] that shall at least be supported for a certified capability class depends on the supported device specializations and on the client or service role. Client and service components are allowed to implement multiple versions, with the minimum version(s) as specified in Table 6-3. | +| 11073-20601-2010-BOT-Restriction | If the client component chooses to use protocol-version 1 in the association phase then the service component shall not use BO-time in the communication with this client. | [ISO/IEEE 11073-20601-2010] (version 1) did not support base offset time, so all device specializations prior to CDG V2012 cannot support this attribute. This requirement guarantees backward | + +**Table 6-2 –X73 wired/wireless general requirements** + +| Name | Description | Comments | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | compatibility and interoperability. The client (the manager) indicates it wants to use version 1 by setting (only) the version 1 bit of the protocol-version field in the association response message. | +| 11073-20601-2010-BOT-Recommended | Continua X73-IF service components using IEEE 11073-20601 protocol version 2 or higher should use BO-time when reporting time and time-stamps in events. | [IEEE 11073-20601A] supports different flavours of time reporting. BO-time is the one that gives the best possibilities on handling local time changes, DST settings, and synchronization with UTC. | +| 11073-20601A_Service_Proto_Version | Continua X73-IF service components using IEEE 11073-20601 protocol version 1 in an association shall adhere to the corrections and clarifications from [ISO/IEEE 11073-20601A] | Components certifying to CDG 2012 (and later) are required to indicate supported protocol versions as per the standards. Since early Continua X73-IF service components require implementation of [ISO/IEEE 11073-20601-2010] version 1 with only the corrections and clarifications from [IEEE 11073-20601A], these interfaces will follow protocol version 1 (with corrections). | +| 11073-20601A_Client_Proto_Version | Continua X73-IF client components using IEEE 11073-20601 protocol version 1 in an association shall adhere to the corrections and clarifications from [ISO/IEEE 11073-20601A] | Responding to an association request (AARQ) with the version 1 bit of the protocol version set indicates that the base offset time (BO-time) is not used. Similar to the Continua X73-IF service components, the Continua X73-IF client component shall nevertheless follow the remaining specifications of [IEEE 11073-20601A] even though the specification requires protocol version bit 2 to be set. | +| 11073-20601A_Client_Other_Proto_Version | Continua X73-IF client components may accept other bit settings in the protocol version than the ones implied by Table 6-3, but would then be operating in a non-Continua certified association | This guideline allows Continua X73-IF client components to implement new technical extensions
    NOTE – This is outside the current Continua Certification Programme. | + +**Table 6-3 – Minimally supported base protocol version(s) for device specializations** + +| IEEE 11073-104xx specification | Device specialization(s) | 20601 protocol version client component (*) | 20601 protocol version service component (*) | specification supports BO-time | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-----------------------------------------------------|---------------------------------------| +| 10404 | pulse oximeter | v1 | v1 | no | +| 10406 | basic 1-3 lead ECG and heart-rate sensor | v2 | v2 | yes | +| 10407 | blood pressure monitor | v1 | v1 | no | +| 10408 | thermometer | v1 | v1 | no | +| 10415 | weighing scales | v1 | v1 | no | +| 10417 | glucose meter | v1, v3 | v3 | yes | +| 10418 | INR meter | v2 | v2 | yes | +| 10419 | insulin pump | v3 | v3 | yes | +| 10420 | body composition analyser | v1 | v1 | no | +| 10421 | peak expiratory flow monitor | v1 | v1 | no | +| 10424 | sleep apnoea breathing therapy equipment | v2 | v2 | yes | +| 10425 | continuous glucose monitor | v3 | v3 | yes | +| 10427 | Power status monitor | v2 | v2 | yes | +| 10441 | cardiovascular fitness and step counter | v3 | v3 | yes | +| 10442 | strength fitness | v1 | v1 | no | +| 10471 | activity hub, fall sensor, motion sensor, enuresis sensor, contact closure sensor, switch sensor, dosage sensor, water sensor, smoke sensor, property exit sensor, temperature sensor, usage sensor, PERS sensor, CO sensor and gas sensor | v1 | v1 | no | +| 10472 | adherence monitor | v1 | v1 | no | + +(\*) The protocol versions "v1", "v2" and "v3" as used in Table 6-3 refer to the protocol version of the 11073-20601 protocol. The supported version(s) are indicated by bits in the "protocol-version" field included in the PHDAssociationInformation structure in the association request (AARQ) and association response (AARE) of the 11073-20601 protocol. + +**Table 6-4 – Correspondence between 11073-20601 protocol versions and specifications** + +| 11073-20601 protocol version | Corresponding specification | +|-------------------------------------|----------------------------------------| +| v1 | [ISO/IEEE 11073-20601:2010] | +| v2 | [ISO/IEEE 11073-20601:2010/Amd 1:2015] | +| v3 | [ISO/IEEE 11073-20601:2016] | + +#### **6.2.2.2 X73 component – Communication capabilities** + +This clause contains guidelines for the general communication capabilities of sensor components in Table 6-5, Table 6-6, Table 6-7 and Table 6-8. + +**Table 6-5 – Communication capabilities – General** + +| Name | Description | Comments | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_Bidirectional | Continua X73-IF service and client components shall support bidirectional transmission (i.e., sending and receiving, of [ISO/IEEE 11073-20601] defined application layer messages) | | +| 11073_Manager_Initiated_Communications | Continua X73-IF service components shall not support the MDS-Data-Request Action for the transfer of CDG data. This prohibits the service component from using manager initiated event reporting as a mechanism of measurement transfer | This guideline prohibits the use of manager-initiated event transmission. Use of this mechanism causes increased implementation and test effort that can be avoided through the use of a scanner.
    CDG data is defined as data from any object normatively defined in a device specialization | +| 11073_DataReqMode_Alignment | Continua X73-IF service components shall ensure that the fields in the Metric-Spec-Small attribute of metric objects are aligned with what was declared in the DataReqModeCapab structure during Association | For example, if the mss-acc-agent-initiated bit is set in Metric-Spec-Small , then data-req-init-agent-count in DataReqModeCapab needs to be set to 1 | +| 11073-20601_FIFO_Store_and_Forward | Continua X73-IF service components that are designed to store and forward temporary measurements shall transmit data in a "First In First Out" sequence | This guideline applies to both temporarily stored measurement events and to measurement data stored in a PM-store | + +**Table 6-6 – Communication capabilities – Event reporting** + +| Name | Description | Comments | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_Config_Changes_Service | Continua X73-IF service components shall report configuration changes to future measurements only | In the context of these guidelines, configuration changes are changes to attributes that provide context for the measurement. The interpretation of the measurement depends on the values of these contextual attributes, or configuration values. An example of configuration change would be changing the unit code of the reported measurement (e.g., from pounds to kilograms) | +| 11073-20601_Config_Changes_Client | Continua X73-IF client components that receive a report of a configuration change shall apply the change to future measurements only | A configuration update does not apply retroactively to data already received by the client component | + +**Table 6-7 – Communication capabilities – Scanner requirements** + +| Name | Description | Comments | +|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_Scanner_Sole_Reporter | Continua X73-IF service components shall send changes to any particular attribute via a single scanner object (if enabled) or the medical device system (MDS) object, but never more than one object (of either the MDS or scanner type) | This guideline assigns responsibility to objects in the system for notifying the manager of changes and updates
    The scanner will report changes for attributes in the Scan-Handle-Attr-Val-Map | +| 11073-20601_Unique_Scanner | Continua X73-IF client components shall not simultaneously turn on multiple scanners that embed the same measurement object provided by a single service component | This guideline assigns responsibility to objects in the system for notifying the manager of changes and updates
    The scanner will report changes for attributes in the Scan-Handle-Attr-Val-Map | + +**Table 6-8 – Communication capabilities – Time setting** + +| Name | Description | Comments | +|--------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_Set-Time | Continua X73-IF client components that receive a report containing the Mds-Time-Info attribute, with the mds-time-mgr-set-time bit set to 1, shall invoke the Set-Time action command within a TOconfig time period in order to set the absolute time on the Continua X73-IF service component that has sent the report. | This guideline ensures the same client behaviour as for the case when the mds-time-mgr-set-time bit is received via a GET MDS response message, see [ISO/IEEE 11073-20601]. | +| 11073-20601_DateAndTimeUpdate_PMSegmentTransfer_Server | Continua X73-IF service components that are in the middle of a PM-segment transfer shall not update the PM-Segment object Date-and-Time-Adjustment attribute regardless of any time changes that occur while the segment continues to be transferred | This guideline ensures that the PM-segment includes measurements from the same, unbroken timeline.
    NOTE: This is somewhat less likely to occur at the USB/NFC/Bluetooth BR/EDR level since there is not programmatic control from another channel, but it could happen that the user interface is still turned on during the transfer so this will cover this case | + +**Table 6-8 – Communication capabilities – Time setting** + +| Name | Description | Comments | +|-------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_
    DateAndTimeUpdate_
    PMSegmentTransfer_Client | Continua X73-IF client components that receive a Date-and-Time update from a Continua X73-IF service component in the middle of a PM-segment transfer shall use the service component's time reference at the time the first segment entry is transmitted as the reference for the full segment regardless of any time changes that occur while the segment continues to be transferred | This guideline accounts for the fact that the service component's PM-segment contains measurements from the same, unbroken timeline. | +| 11073-20601_
    DateAndTimeUpdate_
    PMSegment_LowResource_
    Service | Continua X73-IF service components with limited memory which implement PM-Store and do not implement Base-Offset-Time may maintain measurements across date or time adjustments within a single PM-segment. In this case, the user-facing time of the X73-IF service component at the time of the measurement shall be communicated as the measurement timestamp. See Note below. | In this case, such service components will not be capable of communicating date or time adjustments and cannot fulfil the requirement within [ISO/IEEE 11073-20601] Time Coordination section which states: "If an agent collects PM-store measurements and the Date-and-Time attribute is adjusted, the agent shall ensure that each PM-segment includes only measurements from the same, unbroken timeline." | + +NOTE – This requirement resolves the issue with some configurations of current IEEE device specializations that do use a PM Store with multiple segments and that do not include support for Base Offset time. Support of such a configuration would require an implementation to create new segments on each time or date change and to report on this in a single application protocol data unit (APDU) as response to a GetSegmentInfo request from the manager. The memory needed to store the additional segments and the size of the response APDU both grow significantly with each time or date change. This is seen as an unreasonable requirement on such implementations as they would run out of memory too quickly. + +This affects configurations of the following device specializations that include a PM Store: + +- Medication monitor [ISO/IEEE 11073-10472] +- Pulse oximeter [ISO/IEEE 11073-10404] + +### 6.2.2.3 X73 component – Device information + +This clause contains design guidelines that describe how to map CDG required device information to [ISO/IEEE 11073-20601] defined attributes. These guidelines are covered in Table 6-9. + +**Table 6-9 – Device information** + +| Name | Description | Comments | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_Manufacturer | Continua X73-IF service components shall set the manufacturer field of the System-Model MDS object attribute to the device original manufacturer's name. If this capability is available, the manufacturer field may be overwritten to the customer-facing company's name by the customer-facing company | | +| 11073-20601_Model | Continua X73-IF service components shall set the model-number field of the System-Model MDS object attribute to the device original manufacturer's model number. The model-number field may be overwritten to the customer-facing company's model by the customer-facing company | | +| 11073-20601_OUI | The OUI part of the MDS System-Id attribute in a Continua X73-IF service component shall remain unchanged from the value set by the original manufacturer | This is a unique identifier, which is obtained by the IEEE registration authority and which is associated with a company. This attribute maps to the organizationally unique identifier (OUI) part (first 24 bits) of the EUI-64 attribute | +| 11073-20601_DID | The 40 bit manufacturer defined identifier in the System-Id of the MDS object attribute of a Continua X73-IF service component shall remain unchanged from the value set by the original manufacturer | In combination with the System-Id attribute OUI part, this is a unique identifier associated with the device. It is required in order to facilitate data quality analysis. This attribute maps to the company-defined part (last 40 bits) of the EUI-64 attribute | +| 11073-20601_DID_Bijective | There shall not be multiple different System-Id values that identify the same X73-IF service component | This guideline ensures that the System-Id value is an objective identifier of a device, i.e., in addition to every physical device having a globally unique identifier, each assigned identifier corresponds to a different physical device. As a consequence, a device cannot use multiple different System-Id values | + +**Table 6-9 – Device information** + +| Name | Description | Comments | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_Serial_Number | Continua X73-IF service components shall include a component to the Production-Specification MDS-object attribute with the spec-type field set to serial-number and the prod-spec field set to the serial number of the device | | +| 11073-20601_FW_Revision | Continua X73-IF service components that provide a firmware identifier shall include a component to the Production-Specification MDS-object attribute with the spec-type field set to fw-revision and the prod-spec field set to the firmware identifier of the device | The firmware identifier is the version of the firmware deployed on the X73 device. The firmware release deployed on an X73 device is uniquely identified by the firmware identifier | + +**6.2.2.4 X73 component – Unsupported service component** + +The CDG provides the data and messaging information to enable interoperability between Personal Health Devices. However, there may be regulatory reasons that require some client components to be exclusive about the data they accept. Not all client components will need to be this exclusive. However, the CDG provides the data and the messages for client components that are exclusive to providing the user with a positive experience. + +This clause contains design guidelines, in Table 6-10, that define the expected behaviour when a service-side certified capability is not available. + +**Table 6-10 – Unsupported service component** + +| Name | Description | Comments | +|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073_Unsupported_Device_Rejection | If a Continua service component does not support at least one Continua certified capability class supported by the client component and the client component only accepts Continua Certified Capability Classes, then the Continua X73-IF client components shall request to release the association with a Continua service component using the result field no-more-configurations | If the service component supports any Continua certified capability classes, it supports the corresponding Reg-Cert-Data-List MDS object attribute where the certified capability class will be listed. The client will need to query the MDS to retrieve this attribute. It is recommended that this query is done before the service component enters the operating state to avoid the unwanted transfer of data | +| 11073_Unsupported_Device_Utilize_11073 | Continua X73-IF service and client components that need to selectively accept or reject service or client component data for a specialization they support in order to comply with regulatory requirements shall utilize only [ISO/IEEE 11073-20601] data structures to make the decision to reject or accept data from a client or service component | It will be necessary to simulate "accepted" devices to fully test service and client components. Device manufacturers will need to document and provide 11073 data structures for "accepted" devices for use during interoperability testing. Note that this design guideline is not a testable design guideline. It is simply used to facilitate testing | +| 11073_Unsupported_Device_UserNotification_Client | Continua X73-IF client components shall notify the user of failure of the connection and corresponding reason, if it has released or rejected the association according to requirement 11073-Unsupported-Device-Rejection | This requirement is related to the user interface of the client component. Notification can be done in various ways (e.g., by displaying a text message or by means of a blinking LED) | + +**Table 6-10 – Unsupported service component** + +| Name | Description | Comments | +|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073_Unsupported_Device_UserNotification_Service | Continua X73-IF service components should notify the user of failure of the connection and corresponding reason, if the client has released or rejected the association according to requirement 11073-Unsupported-Device-Rejection | This requirement is related to the user interface of the service/client component. Notification can be done in various ways (e.g., by displaying a text message or by means of a blinking LED) | +| 11073_Unsupported_Device_UserNotification_String_Client | Continua X73-IF client components with appropriate UI capabilities should use the following text string to notify the user of the connection failure in accordance with guideline 11073-Unsupported-Device-UserNotification-Client: "Thank you for choosing Continua certified personal health products. The device you are connecting either has not been Continua certified or the data is not intended for use in this solution. Please see your user manual for more details." | This string may be localized by the manufacturer based on the product and target geography | +| 11073_Unsupported_Device_UserNotification_String_Service | Continua X73-IF service components with appropriate UI capabilities should use the following text string to notify the user of any failure of the connection according to guideline 11073-Unsupported-Device-UserNotification-Service: "Thank you for choosing Continua certified personal health products. The device you are connecting either has not been Continua certified or the data is not intended for use in this solution. Please see your user manual for more details." | This string may be localized by the manufacturer based on the product and target geography | +| 11073_Unsupported_Device_NotificationDocu | Continua X73-IF service and client components shall be shipped with a documentation of the notification mechanism with respect to requirements 11073-Unsupported-Device-UserNotification-Service and 11073-Unsupported-Device-UserNotification-Client | | + +### 6.2.2.5 X73 component – Quality of service + +To send IEEE 11073-20601 data and messages on logical channels based on QoS characteristics, the requirements in Table 6-11 are defined, while the corresponding Continua QoS bins are in Table 6-12. + +**Table 6-11 – X73 QoS implementation** + +| Name | Description | Comments | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------| +| DataMessaging_BiDir_QoS | Continua X73-IF service and client components shall send all messages on the corresponding Continua QoS bins listed in Table 6-12 | | + +**Table 6-12 – Bidirectional transport layer: Message type/QoS bin mapping** + +| Msg Grp | Message type description | APDU type | QoS bin type | +|---------|--------------------------------------------------------------------------------------------|-----------|----------------------------| +| 0 | Association Request | Aarq | best.medium | +| | Association Response | Aare | best.medium | +| | Association Release Request | Rlrq | best.medium | +| | Association Release Response | Rlre | best.medium | +| | Association Abort | Abrt | best.medium | +| 1 | DATA(Invoke-UnconfirmedEventReport (Unbuf-Scan-Report-*), ScanReportInfo* ) | Prst | best.medium or good.medium | +| | DATA(Invoke-UnconfirmedEventReport(Buf-Scan-Report-*), ScanReportInfo* ) | Prst | best.medium or good.medium | +| | DATA(Invoke-UnconfirmedEventReport (MDS-Dynamic-Data-Update-*), ScanReportInfo* ) | Prst | best.medium or good.medium | +| 2 | DATA(Invoke-ConfirmedEventReport(MDS-Configuration-Event), ConfigReport) | Prst | best.medium | +| | DATA(Response-ConfirmedEventReport(MDS-Configuration-Event), ConfigReportRsp) | Prst | best.medium | +| | DATA(Invoke-ConfirmedEventReport(Segment-Data-Event), SegmentDataEvent) | Prst | best.medium | +| | DATA(Response-ConfirmedEventReport(Segment-Data-Event), SegmentDataResult) | Prst | best.medium | +| | DATA(Invoke-ConfirmedEventReport(Unbuf-Scan-Report-*), ScanReportInfo* ) | Prst | best.medium | +| | DATA(Response-ConfirmedEventReport(Unbuf-Scan-Report-*)) | Prst | best.medium | +| | DATA(Invoke-ConfirmedEventReport(Buf-Scan-Report-*), ScanReportInfo* ) | Prst | best.medium | +| | DATA(Response-ConfirmedEventReport(Buf-Scan-Report-*)) | Prst | best.medium | +| | DATA(Invoke-ConfirmedEventReport (MDS-Dynamic-Data-Update-*), ScanReportInfo* ) | Prst | best.medium | +| | DATA(Response-ConfirmedEventReport (MDS-Dynamic-Data-Update-*)) | Prst | best.medium | +| 3 | DATA(Invoke-UnconfirmedAction()):
    <none defined in [ISO/IEEE 11073-20601]> | N/A | N/A | +| 4 | DATA(Invoke-ConfirmedAction(MDS-Data-Request), DataRequest) | Prst | best.medium | + +**Table 6-12 – Bidirectional transport layer: Message type/QoS bin mapping** + +| Msg Grp | Message type description | APDU type | QoS bin type | +|---------|-----------------------------------------------------------------------------|-----------|--------------| +| | DATA(Response-ConfirmedAction(MDS-Data-Request), DataResponse) | Prst | best.medium | +| | DATA(Invoke-ConfirmedAction(Set-Time), SetTimeInvoke) | Prst | best.medium | +| | DATA(Response-ConfirmedAction(Set-Time)) | Prst | best.medium | +| | DATA(Invoke-ConfirmedAction(Get-Segment-Info), SegmSelection) | Prst | best.medium | +| | DATA(Response-ConfirmedAction(Get-Segment-Info), SegmentInfoList) | Prst | best.medium | +| | DATA(Invoke-ConfirmedAction(Trig-Segment-Data-Xfer), TrigSegmDataXferReq) | Prst | best.medium | +| | DATA(Response-ConfirmedAction(Trig-Segment-Data-Xfer), TrigSegmDataXferRsp) | Prst | best.medium | +| | DATA(Invoke-ConfirmedAction(Clear-Segments), SegmSelection) | Prst | best.medium | +| | DATA(Response-ConfirmedAction(Clear-Segments)) | Prst | best.medium | +| | DATA(Invoke-ConfirmedAction(MDS-Data-Request), DataRequest) | Prst | best.medium | +| | DATA(Response-ConfirmedAction(MDS-Data-Request), DataResponse) | Prst | best.medium | +| | DATA(Invoke-ConfirmedAction(MDS-Data-Request), DataRequest) | Prst | best.medium | +| | DATA(Response-ConfirmedAction(MDS-Data-Request)) | Prst | best.medium | +| 5 | DATA(Invoke-UnconfirmedSet() {scanner OperationalState}) | Prst | best.medium | +| 6 | DATA(Invoke-ConfirmedSet() {scanner OperationalState}) | Prst | best.medium | +| | DATA(Response-ConfirmSet() {scanner OperationalState}) | Prst | best.medium | +| 7 | DATA(Invoke-ConfirmedGet() {MDS attributes}) | Prst | best.medium | +| | DATA(Response-ConfirmGet() {MDS attributes}) | Prst | best.medium | +| | DATA(Invoke-ConfirmedGet() {PM-store attributes}) | Prst | best.medium | +| | DATA(Response-ConfirmGet() {PM-store attributes}) | Prst | best.medium | +| 8 | DATA(Error(), ErrorResult) | Prst | best.medium | +| | DATA(Reject(), RejectResult) | Prst | best.medium | + +#### 6.2.2.6 X73 component – Regulatory settings + +This clause contains design guidelines that deal with the Continua requirements for regulatory issues using the IEEE 11073-20601 capabilities. These guidelines are covered in Table 6-13, Table 6-14 and Table 6-15. + +For this purpose, the following abstract syntax notation one (ASN.1) definitions are introduced and referenced in Table 6-13. + +NOTE – This syntax is also used for Bluetooth LE in clause 11.2.7. + +``` + +ContinuaStructType ::= INT-U8 { + continua-version-struct(1), -- auth-body-data is a ContinuaBodyStruct + continua-reg-struct(2) -- auth-body-data is a ContinuaRegStruct +} + +ContinuaBodyStruct ::= SEQUENCE { + major-IG-version INT-U8, + minor-IG-version INT-U8, + certified- capabilities CertifiedCapabilityClassList +} + +CertifiedCapabilityClassList ::= SEQUENCE OF CertifiedCapabilityClassEntry + +-- See guideline 11073-20601_ CapabilityEntry for the algorithm to compute the +-- value +CertifiedCapabilityClassEntry ::= INT-U16 + +ContinuaRegStruct ::= SEQUENCE { + regulation-bit-field RegulationBitFieldType +} + +RegulationBitFieldType ::= BITS-16 { + unregulated-device (0) -- This bit shall be set if the device is not + regulated } + +``` + +**Figure 6-3 – ASN.1 definition of Continua certification structures** + +#### 6.2.2.6.1 Regulatory / certification information + +This clause contains guidelines for the conformance of client components to the usage of regulatory and certification information. The guidelines are contained in Table 6-13. + +**Table 6-13 – Regulatory / certification information** + +| Name | Description | Comments | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601_
    Certification | Continua X73-IF service components shall support the Reg-Cert-Data-List MDS object attribute containing a RegCertData element with the auth-body field set to auth-body-continua and the auth-body-struc-type field set to continua-version-struct from a ContinuaStructType as defined above. The field auth-body-data shall be filled in as a ContinuaBodyStruct as defined above | Continua certification information - This is used to indicate whether a capability is Continua certified and (if so) to which version of the guidelines it is certified to | +| 11073-20601-
    CapabilitiesList | Continua X73-IF service components shall list all implemented and only the implemented Certified Capability Classes in the "certified-capabilities" attribute of the ContinuaBodyStruct structure | | + +**Table 6-13 – Regulatory / certification information** + +| Name | Description | Comments | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601-CapabilityEntry | Continua X73-IF service components shall assign the following CertifiedCapabilityClassEntry to an implemented certified capability class:
    MDC_DEV_*_SPEC_PROFILE_* - 4096 + TCode x 8192, where MDC_DEV_*_SPEC_PROFILE_* denotes the IEEE 11073 PHD nomenclature code for the corresponding device (sub-) specialization, and TCode denotes the corresponding transport standard, with TCode = {1 for USB, 2 for Bluetooth BR/EDR, 3 for ZigBee, 4 for Bluetooth LE, and 5 for NFC}. For backward compatibility with CDG version 1 which did not define TCodes, USB and Bluetooth BR/EDR service components should additionally include the supported MDC_DEV_*_SPEC_PROFILE_* codes along with a TCode of 0 to interoperate with version 1 client components |

    Example 1: For a Bluetooth BR/EDR step counter, the assigned CertifiedCapabilityClassEntry computes as 0x4068 (16488 decimal), where it has been substituted MDC_DEV_*_SPEC_PROFILE_* = MDC_DEV_SUB_SPEC_PROFILE_STEP_COUNTER = 4200 and TCode = 2.

    This gives, 4200 - 4096 + 2 x 8192 = 16488 (0x4068)

    Example 2: For a ZigBee smoke sensor, the assigned CertifiedCapabilityEntry computes as 0x6077 (24,695 decimal), where it has been substituted MDC_DEV_*_SPEC_PROFILE_* = MDC_DEV_SUB_SPEC_PROFILE_SMOKE_SENSOR = 4215 and TCode = 3.

    This gives, 4215 - 4096 + 3 x 8192 = 24,695 (0x6077)

    | +| 11073-20601-DeviceSpecList | Continua X73-IF service components shall list MDC_DEV_SPEC_PROFILE_* value(s) corresponding to each supported Continua certified Capability Class in the System-Type-Spec-List attribute of the MDS object. The attribute may contain additional MDC_DEV_SPEC_PROFILE_* value(s) corresponding to supported IEEE specializations that are not Continua certified | | +| 11073-20601-Regulation | Continua X73-IF service components shall support the Reg-Cert-Data-List MDS object attribute containing a RegCertData element with the auth-body field set to auth-body-continua and the auth-body-struc-type field set to continua-reg-struct from a ContinuaStructType as defined in the sub-clauses below. The field auth-body-data shall be filled in as a ContinuaRegStruct as defined below | Regulation information - This is used to provide a coarse regulatory indication (e.g., "Regulated" or "Not Regulated") | + +#### 6.2.2.6.2 Conformance + +This clause contains guidelines for the conformance of client components to [ISO/IEEE 11073-20601] and [ISO/IEEE 11073-104xx] specifications and capabilities. The guidelines are contained in Table 6-14. + +**Table 6-14 – Manager conformance** + +| Name | Description | Comments | +|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601-Manager-Conformance | Continua X73-IF client components shall appropriately utilize the mandatory measurement objects from compliant device specializations | In the context of these requirements, the term "appropriately utilize" implies that the objects get utilized in accordance with the function of the device. That is, a mandatory measurement object can be displayed, and/or forwarded, and/or used as input for an assessment algorithm, etc. | +| 11073-20601-Utilization-Documentation | Continua X73-IF client components shall provide to the Test and Certification organization documentation on the appropriate utilization of the individual mandatory measurement objects | | + +#### 6.2.2.6.3 Nomenclature codes + +This clause contains guidelines for the use of nomenclature codes by client and service components. The guidelines are contained in Table 6-15. + +**Table 6-15 – Nomenclature codes** + +| Name | Description | Comments | +|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| +| 11073-20601-Continua-Nomenclature-Codes | Continua X73-IF service and client components that use private nomenclature codes shall allocate them from the range 0xF000 through 0xFBFF | The range from 0xFC00 through 0xFFFF is reserved for future use by the CDG | + +#### 6.2.2.7 X73 component – User identification + +This clause contains guidelines for service components on user identification. The guidelines are contained in Table 6-16. + +**Table 6-16 – User identification** + +| Name | Description | Comments | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| 11073-20601-PID-ScanReport | Continua X73-IF service components designed to store and utilize data from multiple users simultaneously and that use agent-initiated measurement data transmission shall identify users and set the person-id field in the corresponding ScanReportPer* structure | Identification means distinguishing between users of the measurement device | + +**Table 6-16 – User identification** + +| Name | | Description | Comments | +|--------------------------|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| 11073-20601-PID-PM-Store | | Continua X73-IF service components designed to store and utilize data from multiple users simultaneously in one or more PM-stores shall identify users and support the PM-Seg-Person-Id PM-segment object attribute and set the pmse-multi-person bit in the PM-Store-Capab PM-Store object attribute | Identification means distinguishing between users of the measurement device | + +### 6.2.3 Standard configuration support + +This clause contains guidelines on the support of standard and extended configurations by X73-IF client and service components to better guarantee interoperability. The guidelines are covered by Table 6-17. + +**Table 6-17 – Communication capabilities – general** + +| Name | Description | Comments | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601-standard-config-support | Continua X73-IF service components shall (always) support one of the pre-defined standard configurations for supported [ISO/IEEE 11073-104xx] device specializations if such configurations are defined in the corresponding [ISO/IEEE 11073-104xx] device specialization. | [ISO/IEEE 11073-20601-2016] and later no longer requires a service component to always support a standard configuration: a service component that supports an extended configuration with a PM store does not need to support a standard configuration. The CDGs do require support for a standard configuration by the service component to maintain interoperability. | +| 11073-20601-extended-config-support | Continua X73-IF client components that support protocol IEEE 11073-20601 protocol v3 should support extended configurations as used by [ISO/IEEE 11073-104xx] device implementations for supported [ISO/IEEE 11073-104xx] device specializations as long as these configurations consist of objects and attributes defined in the corresponding [ISO/IEEE 11073-104xx] specification. | [ISO/IEEE 11073-20601-2016] and later no longer require a service component to always support a standard configuration: a service component that supports an extended configuration with a PM store does not need to support a standard configuration. The CDGs require that such extended configurations should be supported by the Personal Health Gateway (PHG) for improved interoperability. | + +NOTE – the following device specializations do not define standard configurations: + +- 11073-10441 Cardiovascular fitness and activity monitor +- 11073-10442 Strength fitness equipment +- 11073-10471 Independent living activity hub + +#### 6.2.4 Sensor component – communication capabilities + +This clause contains guidelines for general communications capabilities of sensor components, see Table 6-18. + +**Table 6-18 – Communication capabilities association and configuration** + +| Name | Description | Comments | +|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601-Complete-Config-Object-List | Continua X73-IF service components shall always populate the ConfigObjectList of a configuration message with the complete set of objects and attributes supported by the configuration | [ISO/IEEE 11073-20601] allows an agent to send a configuration event with an empty ConfigObjectList if the configuration-id is within the range of standard-config-start and standard-config-end. This mechanism was designed in [ISO/IEEE 11073-20601] to optimize bytes transferred. However this mechanism is likely to cause interoperability problems as the feature is not well known. It is believed that the enhancement to interoperability outweighs the optimization. | + +#### 6.2.5 Sensor component multi-function devices + +This clause describes guidelines for multi-function devices (e.g., how to make combined use of [ISO/IEEE 11073-104xx] to create multi-function devices, or how to use the [ISO/IEEE 11073-20601] mechanisms for association in this case). See Table 6-19. + +**Table 6-19 – Multi-function devices** + +| Name | Description | Comments | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-20601-Multi-Function | A Continua X73-IF service component shall have at most one [ISO/IEEE 11073-20601] association to an X73-IF client component at any point in time regardless of whether the device is a single function or multi-function device | This guideline prohibits the device from having two concurrent associations. The device may provide different configuration options only in subsequent associations only after closing the currently active association | + +## 6.3 X73 devices + +This clause contains guidelines for client and service components that implement specific [ISO/IEEE 11073-104xx] device specializations. There is a subclause per device specialization. + +### 6.3.1 Pulse oximeter + +This clause contains guidelines for client and service components that implement the pulse oximeter device specialization. The guidelines are contained in Table 6-20 and additionally in Table 6-21 and Table 6-22 for implementations supporting PM stores. + +#### 6.3.1.1 Pulse oximeter – general requirements + +**Table 6-20 – Pulse oximeter – General requirements** + +| Name | Description | Comments | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10404-Reqt | Continua X73 pulse oximeter service and client components shall implement [ISO/IEEE 11073-10404] | | +| 11073-Pulse-Oximeter-PM-Store | Continua X73 pulse oximeter service and client components that implement and use the PM-Store model shall implement the guidelines in Table 6-21, and Table 6-22 as well as Table 6-2 or Table 6-3 and subsequent explanatory text. | | + +#### 6.3.1.2 PM-store objects for the pulse oximeter + +The PM-store and PM-segment classes provide a flexible and powerful means for storing large amounts of measurement data for later transmission to a PHD. However, this flexibility could potentially lead to ambiguities that could jeopardize interoperability. This clause describes recommended implementations for the most common use case, the sleep study. + +Figure 6-4 illustrates one arrangement of a PM-store organized into two PM-segments. Each PM-segment stores periodically sampled data from a single contiguous session and each PM-segment entry contains a SpO2 measurement and a pulse rate measurement sampled at a single point in time. + +![](77959075c823bb5169480d7b8ff82a63_img.jpg) + +PM-store +PM store attributes + +Session 1 measurements + +**PM-Segment 1** + +PM-Segment attributes +Fixed-Segment-Data: + +| | | | +|---------|---------------------|---------------------------| +| Entry 1 | Element 1
    (SpO2) | Element 2
    (Pulse rate) | +| Entry 2 | Element 1
    (SpO2) | Element 2
    (Pulse rate) | +| Entry N | Element 1
    (SpO2) | Element 2
    (Pulse rate) | + +Session 2 measurements + +**PM-Segment 2** + +PM-Segment attributes +Fixed-Segment-Data: + +| | | | +|---------|---------------------|---------------------------| +| Entry 1 | Element 1
    (SpO2) | Element 2
    (Pulse rate) | +| Entry 2 | Element 1
    (SpO2) | Element 2
    (Pulse rate) | +| Entry N | Element 1
    (SpO2) | Element 2
    (Pulse rate) | + +H.811(16)\_F6-4 + +**Figure 6-4 – PM-Store usage for pulse oximeter** + +Some situations may not be suitable for the previous approach. For instance, a pulse oximeter may record SpO2 measurements at a different sampling period than pulse rate measurements, or one of the measurements during a session could conceivably be episodic. A PM-segment organization that could be better suited to this situation is illustrated in Figure 6-5. + +![Diagram of alternate PM-segment organization showing two PM-segments (PM-Segment 1 and PM-Segment 2) within a PM-store. PM-Segment 1 is associated with Session 1 measurements and contains entries for Pulse rate. PM-Segment 2 is associated with Session 2 measurements and contains entries for SpO2. The diagram shows the hierarchical structure of PM-segments within a PM-store, with Session 1 and Session 2 measurements grouped under their respective segments.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +PM-store +PM store attributes + +**PM-Segment 1** + +PM-Segment attributes +Fixed-Segment-Data: + +| | | +|---------|---------------------------| +| Entry 1 | Element 1
    (Pulse rate) | +| Entry 2 | Element 1
    (Pulse rate) | +| Entry N | Element 1
    (Pulse rate) | + +**PM-Segment 2** + +PM-Segment attributes +Fixed-Segment-Data: + +| | | +|---------|---------------------| +| Entry 1 | Element 1
    (SpO2) | +| Entry 2 | Element 1
    (SpO2) | +| Entry N | Element 1
    (SpO2) | + +H.811(16)\_F6-5 + +Diagram of alternate PM-segment organization showing two PM-segments (PM-Segment 1 and PM-Segment 2) within a PM-store. PM-Segment 1 is associated with Session 1 measurements and contains entries for Pulse rate. PM-Segment 2 is associated with Session 2 measurements and contains entries for SpO2. The diagram shows the hierarchical structure of PM-segments within a PM-store, with Session 1 and Session 2 measurements grouped under their respective segments. + +**Figure 6-5 – Alternate PM-segment organization** + +This alternate arrangement challenges the notion of measurement association. Given a collection of PM-segments, how can the PHG determine which, if any, segments are associated? + +Time stamps are used to determine whether one or more PM-segments are associated with another. Any measurements within one or more PM-segments in a PM-store are considered to be associated if their start and end segment attributes are overlapping, or if one segment's time range is contained within another segment. Guidelines in Table 6-21 prohibit the storage of associated PM-segments in separate PM-stores, which would add unnecessary complexity for client components to identify associated PM-segments. + +**Table 6-21 – Pulse oximeter PM-Store measurement requirements** + +| Name | Description | Comments | +|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-Pulse_Oximeter_PM_Store_Organization | Continua X73 pulse oximeter service components should organize their stored measurements as shown in Figure 6-4 or Figure 6-5. | The order of SpO2 and pulse rate is defined in the SegEntryMap | +| 11073-Pulse_Oximeter_PM_Store_StartTime_StopTime | Continua X73 pulse oximeter service components shall store the start time and end time in the PM-Segment attributes Segment-Start-Abs-Time and Segment-end-Abs-Time | Enables the PHG to determine whether one or more PM-segments are associated | +| 11073_Pulse_Oximeter_PM_Store_Associated_Measurements_Locations | Continua X73 pulse oximeter service components shall create PM-segments within the same PM-store, if the PM-segments are overlapping in time | PM-segments are considered to be overlapping in time if the time ranges defined by their Segment-Start-Abs-Time and Segment-End-Abs-Time attribute values are overlapping | + +### 6.3.1.3 PM-Store object attributes + +Table 6-22 contains guidelines for pulse oximeter PM-Store object attributes. + +**Table 6-22 – Pulse oximeter PM-Store object attributes guideline** + +| Name | Description | Comments | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------| +| 11073-Pulse-Oximeter-PM-Store-Object-Attributes-PM-Store-Capab-set | Continua X73 pulse oximeter service components shall set the following bit value for the PM-store-Capab attribute of the PM-store Object: pmsc-clear-segm-by-all-sup | | +| 11073-Pulse-Oximeter-PM-Store-Object-Attributes-PM-Store-Capab-clear | Continua X73 pulse oximeter service components shall clear the following bit value for the PM-store-Capab attribute of the PM-Store object: pmsc-clear-segm-by-time-sup | | +| 11073-Pulse-Oximeter-PM-Store-Object-Attributes-PM-Store-Label | Continua X73 pulse oximeter service components, that implement the PM-store-Label attribute of the PM-store object, shall not set a value of size larger than 255 octets | | +| 11073-Pulse-Oximeter-PM-Store-Object-Attributes-Sample-Period-Attribute | Continua X73 pulse oximeter service components shall implement the Sample-Period attribute of a PM-store object, if the stored measurements are periodic and the Sample-Period attribute is not implemented in each of the PM-segment objects created within that PM-store object. If the Sample-Period is defined in both the PM-store and in the PM-segment(s), the PM-segment attribute value shall take precedence | | +| 11073-Pulse-Oximeter-PM-Store-Object-alignment | Continua X73 pulse oximeter service components shall align periodic measurements so that the time of the first measurement is equivalent to Segment-Start-Abs-Time | Need to align events in case two associated PM-segments have | + +**Table 6-22 – Pulse oximeter PM-Store object attributes guideline** + +| Name | Description | Comments | +|------|-------------|-------------------------------| +| | | widely varying sample periods | + +### 6.3.2 Basic 1-3 lead ECG + +This clause contains guidelines for client and service components that implement the ECG device specialization. The guidelines are contained in Table 6-23 and additionally in Table 6-24 and Table 6-24 for implementations supporting PM stores. + +**Table 6-23 – Basic 1-3 lead ECG – General requirements** + +| Name | Description | Comments | +|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-10406-Basic-ECG-Reqt | Continua X73 Basic 1-3 lead ECG service and client components shall implement [IEEE 11073-10406] | | +| 11073-10406-Simple-ECG-Profile | Continua X73 Basic 1-3 lead ECG service and client components shall implement the simple ECG profile defined in [IEEE 11073-10406] | The simple ECG profile defined in [IEEE 11073-10406] mandates implementation of ECG waveform functionality | +| 11073-Basic-ECG-PM-Store | Continua X73 Basic 1-3 lead ECG service and client components that implement and use the PM-Store model shall implement the guidelines in Table 6-24 and Table 6-25, and should follow the storage layout as shown in Figure 7 of [IEEE 11073-10406] | Figure 7 of [IEEE 11073-10406] illustrates the example of a 3-lead Basic 1-3 lead ECG, with measurement data from all leads being contained in each entry preceded by a segment entry header. For a lower number of leads the number of elements in each entry reduces accordingly. The order of elements within an entry is defined in the SegEntryMap attribute | + +#### 6.3.2.1 PM-store objects for the Basic 1-3 lead ECG + +The PM-store and PM-segment classes provide a flexible and powerful means for storing large amounts of measurement data for later transmission to a PHG. However, this flexibility could potentially lead to ambiguities that could jeopardize interoperability. This clause describes recommended implementations for the most common use case involving persistently stored metric data, the storage of ECG waveform data. + +Figure 7 of [IEEE 11073-10406] illustrates one arrangement of a periodic PM-store organized into two PM-segments. Each PM-segment stores periodically sampled data from a single contiguous session and each PM-segment entry contains sample arrays of ECG waveform data for all implemented leads sampled during the same period of time. + +Some situations may not be suitable for the previous approach. For instance, a Basic 1-3 lead ECG may record heart-rate measurements at a different sampling period than ECG waveform measurements, or one of the measurements during a session could conceivably be aperiodic. A PM-segment organization that could be better suited to this situation is to use a separate PM-segment for + +different measurement types. See also Figure 6-5 for a conceptual illustration of this type of PM-segment organization. This alternate arrangement challenges the notion of measurement association, i.e., for the PHG to determine which segments are associated for a given collection of PM-segments. Storage of periodic and aperiodic measurements involves organization in separate aperiodic and periodic PM-stores, respectively. + +Time stamps are used to determine whether one or more PM-segments are associated with another. Any measurements within one or more PM-segments in a PM-store are considered to be associated if their start and end segment attributes are overlapping, or if one segment's time range is contained within another segment. The guidelines contained in Table 6-24 prohibit the storage of associated PM-segments in separate PM-stores, which would add unnecessary complexity for client components to identify associated PM-segments. + +**Table 6-24 – ECG PM-Store measurement requirements** + +| Name | Description | Comments | +|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073_Basic_ECG_Periodic_PM_Store_Associated_Measurements_Locations | For periodic measurements, Continua X73 Basic 1-3 lead ECG service components shall create PM-segments within the same periodic PM-store, if the PM-segments are overlapping in time | PM-segments are considered to be overlapping in time if the time ranges defined by their Segment-Start-Abs-Time and Segment-End-Abs-Time attribute values are overlapping | +| 11073_Basic_ECG_Aperiodic_PM_Store_Associated_Measurements_Locations | For aperiodic measurements, Continua X73 Basic 1-3 lead ECG service components shall create PM-segments within the same aperiodic PM-store, if the PM-segments are overlapping in time | PM-segments are considered to be overlapping in time if the time ranges defined by their Segment-Start-Abs-Time and Segment-End-Abs-Time attribute values are overlapping | + +### 6.3.2.2 PM-store object attributes + +**Table 6-25 – ECG PM-Store object attributes guidelines** + +| Name | Description | Comments | +|-----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| 11073_Basic_ECG_PM_Store_Object_Attributes_PM-Store-Label | Continua X73 Basic 1-3 lead ECG service components, that implement the PM-Store-Label attribute of the PM-Store object, shall not set a value of size larger than 255 octets | | +| 11073_Basic_ECG_PM_Store_Object_alignment | Continua X73 Basic 1-3 lead ECG service components shall align periodic measurements such that the time of the first measurement is equivalent to Segment-Start-Abs-Time | Need to align events in case two associated PM-segments have widely varying sample periods | + +### 6.3.3 Heart-rate sensor + +This clause contains guidelines for client and service components that implement the heart-rate sensor device specialization. The guidelines are contained in Table 6-26 and additionally in Table 6-27 and Table 6-28 for implementations supporting PM stores. + +**Table 6-26 – Heart-rate sensor – General requirements** + +| Name | Description | Comments | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073-10406_Heart_Rate_Reqt | Continua X73 heart-rate sensor service and client components shall implement [IEEE 11073-10406] | | +| 11073-10406_Heart_Rate_Profile | Continua X73 heart-rate sensor service and client components shall implement the heart rate profile defined in [IEEE 11073-10406] | The heart rate profile defined in [IEEE 11073-10406] mandates the implementation of heart-rate functionality | +| 11073_Heart_Rate_PM_Store | Continua X73 heart-rate sensor service and client components that implement and use the PM-Store model shall implement the guidelines in Table 6-27 and Table 6-28 | For simple heart-rate sensors PM-Store functionality is typically not implemented. This guideline provides guidance for the case that PM-Store functionality is implemented | + +### 6.3.3.1 PM-store objects for the heart-rate sensor + +The PM-store and PM-segment classes provide a flexible and powerful means for storing large amounts of measurement data for later transmission to a PHG. For simple heart-rate sensors this functionality is typically not implemented. However, if implemented this clause provides guidance to ensure interoperability. + +A common use case involves persistently stored R-R interval data. Figure 6-6 illustrates a simple arrangement of an aperiodic PM-store containing PM-segments for storing R-R interval data from different measurement sessions. The entries of a PM-segment each contain an element of R-R interval data. + +![](e8e818455bb0d1a6153299a388b94868_img.jpg) + +Aperiodic PM-store +PM store attributes + +**PM-Segment 1** + +PM-Segment attributes +Fixed-Segment-Data: + +| | | | +|---------|-------------------------|-----------------------------| +| Entry 1 | SegmentEntryHeader(opt) | Element 1
    (R-R interval) | +| Entry 2 | SegmentEntryHeader(opt) | Element 1
    (R-R interval) | +| ⋮ | | | +| Entry n | SegmentEntryHeader(opt) | Element 1
    (R-R interval) | + +⋮ + +**PM-Segment m** + +PM-Segment attributes +Fixed-Segment-Data: + +| | | | +|---------|-------------------------|-----------------------------| +| Entry 1 | SegmentEntryHeader(opt) | Element 1
    (R-R interval) | +| Entry 2 | SegmentEntryHeader(opt) | Element 1
    (R-R interval) | +| ⋮ | | | +| Entry n | SegmentEntryHeader(opt) | Element 1
    (R-R interval) | + +H.811(17)\_F6-6 + +**Figure 6-6 – PM-store usage example for heart-rate sensor** + +Time stamps are used to determine whether one or more PM-segments are associated with another. Any measurements within one or more PM-segments in a PM-store are considered to be associated if their start and end segment attributes are overlapping, or if one segment's time range is contained within another segment. The guidelines contained in Table 6-27 prohibit the storage of associated PM-segments in separate PM-stores, which would add unnecessary complexity for client components to identify associated PM-segments. + +**Table 6-27– Heart-rate sensor PM-Store measurement requirements** + +| Name | Description | Comments | +|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11073_Heart_rate_Periodic_PM_Store_Associated_Measurements_Locations | For periodic measurements, Continua X73 heart-rate sensor service components shall create PM-segments within the same periodic PM-store, if the PM-segments are overlapping in time | PM-segments are considered to be overlapping in time if the time ranges defined by their Segment-Start-Abs-Time and Segment-End-Abs-Time attribute values are overlapping | +| 11073_Heart_Rate_Aperiodic_PM_Store_Associated_Measurements_Locations | For aperiodic measurements, Continua X73 heart-rate sensor service components shall create PM-segments within the same aperiodic PM-store, if the PM-segments are overlapping in time | PM-segments are considered to be overlapping in time if the time ranges defined by their Segment-Start-Abs-Time and Segment-End-Abs-Time attribute values are overlapping | + +### 6.3.3.2 PM-store object attributes + +Table 6-28 contains guidelines for PM-Store object attributes. + +**Table 6-28 – PM-Store object attributes guidelines** + +| Name | Description | Comments | +|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| 11073_Heart_Rate_PM_Store_Object_Attributes_PM-Store-Label | Continua X73 heart-rate sensor service components, that implement the PM-Store-Label attribute of the PM-Store object, shall not set a value of size larger than 255 octets | | +| 11073_Heart_Rate_PM_Store_Object_alignment | Continua X73 heart-rate sensor service components shall align periodic measurements such that the time of the first measurement is equivalent to Segment-Start-Abs-Time | Need to align events in case two associated PM-segments have widely varying sample periods | + +### 6.3.4 Blood pressure monitor + +This clause contains guidelines for client and service components that implement the blood pressure monitor device specialization. The guidelines are contained in Table 6-29. + +**Table 6-29 – Blood pressure monitor – General requirements** + +| Name | Description | Comments | +|------------------|-----------------------------------------------------------------------------------------------------------------|----------| +| 11073-10407_Reqt | Continua X73 blood pressure monitor service and client components shall implement [ISO/IEEE 11073-10407] | | + +### 6.3.5 Thermometer + +This clause contains guidelines for client and service components that implement the thermometer device specialization. The guidelines are contained in Table 6-30. + +**Table 6-30 – Thermometer – General requirements** + +| Name | Description | Comments | +|------------------|------------------------------------------------------------------------------------------------------|----------| +| 11073-10408_Reqt | Continua X73 thermometer service and client components shall implement [ISO/IEEE 11073-10408] | | + +**6.3.6 Weighing scales** + +This clause contains guidelines for client and service components that implement the weighing scales device specialization. The guidelines are contained in Table 6-31. + +**Table 6-31 – Weighing scales – General requirements** + +| Name | Description | Comments | +|------------------|----------------------------------------------------------------------------------------------------------|----------| +| 11073-10415_Reqt | Continua X73 weighing scales service and client components shall implement [ISO/IEEE 11073-10415] | | + +**6.3.7 Glucose meter** + +This clause contains guidelines for client and service components that implement the glucose meter device specialization. The guidelines are contained in Table 6-32. + +**Table 6-32 – Glucose meter – General requirements** + +| Name | Description | Comments | +|------------------|----------------------------------------------------------------------------------------------------|----------| +| 11073-10417_Reqt | Continua X73 glucose meter service and client components shall implement [IEEE 11073-10417] | | + +**6.3.8 INR meter** + +This clause contains guidelines for client and service components that implement the INR meter device specialization. The guidelines are contained in Table 6-33. + +**Table 6-33 – INR meter – General requirements** + +| Name | Description | Comments | +|------------------|------------------------------------------------------------------------------------------------|----------| +| 11073-10418_Reqt | Continua X73 INR meter service and client components shall implement [IEEE 11073-10418] | | + +**6.3.9 Body composition analyser** + +This clause contains guidelines for client and service components that implement the body composition analyser device specialization. The guidelines are contained in Table 6-34. + +**Table 6-34 – Body composition analyser – General requirements** + +| Name | Description | Comments | +|------------------|----------------------------------------------------------------------------------------------------------------|----------| +| 11073-10420_Reqt | Continua X73 Body composition analyser service and client components shall implement [IEEE 11073-10420] | | + +### 6.3.10 Peak expiratory flow monitor + +This clause contains guidelines for client and service components that implement the peak expiratory flow monitor device specialization. The guidelines are contained in Table 6-35. + +**Table 6-35 – Peak expiratory flow monitor – General requirements** + +| Name | Description | Comments | +|------------------|-----------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10421_Reqt | Continua X73 peak expiratory flow monitor service and client components shall implement [ISO/IEEE 11073-10421] | | + +### 6.3.11 Cardiovascular fitness + +This clause contains guidelines for client and service components that implement the cardiovascular fitness device specialization. The guidelines are contained in Table 6-36. + +**Table 6-36 – Cardiovascular fitness – General requirements** + +| Name | Description | Comments | +|------------------|-------------------------------------------------------------------------------------------------------------|----------| +| 11073-10441_Reqt | Continua X73 cardiovascular fitness service and client components shall implement [IEEE 11073-10441] | | + +### 6.3.12 Cardiovascular step counter + +There is no IEEE 11073 device specialization dedicated to a cardiovascular step counter. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10441] to create an X73 cardiovascular step counter. The guidelines are contained in Table 6-37. + +**Table 6-37 – Cardiovascular step counter – General requirements** + +| Name | Description | Comments | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| 11073_10441_Reqt | Continua X73 cardiovascular step counter service and client components shall implement [IEEE 11073-10441] | | +| 11073_Step_Counter_Service_Max_APDU | Continua X73 cardiovascular step counter service components shall be able to support a maximum APDU size of 224 octets from Continua X73 client components | These are consistent with weighing scales, thermometer, glucose meter, blood pressure monitor and independent living activity hub | +| 11073_Step_Counter_Client_Max_APDU | Continua X73 cardiovascular step counter client components shall be able to support a maximum APDU size of 6624 octets from Continua X73 service components | | +| 11073_Step_Counter_Service_Mandatory_Objects | Continua X73 cardiovascular step counter service components shall support the session and distance object in units of steps | | + +**Table 6-37 – Cardiovascular step counter – General requirements** + +| Name | Description | Comments | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073_Step_Counter_Client_Mandatory_Objects | Continua X73 cardiovascular step counter client components shall support the session and distance object (all unit codes) | | +| 11073_Step_Counter_Service_Optional_Objects | Continua X73 cardiovascular step counter service components may support the subsession, cadence, speed, distance (in metres and/or feet), stride length, or energy expended objects as defined in [IEEE 11073-10441] | | +| 11073_Step_Counter_Client_Optional_Objects | Continua X73 cardiovascular step counter client components may support the subsession, cadence, speed, stride length, or energy expended objects as defined in [ISO/IEEE 11073-10441] | | +| 11073_Step_Counter_MDC_Code | Continua X73 step counter service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_STEP_COUNTER = 4200 (0x1068) | | + +### 6.3.13 Strength fitness + +This clause contains guidelines for client and service components that implement the strength fitness device specialization. The guidelines are contained in Table 6-38. + +**Table 6-38 – Strength fitness – General requirements** + +| Name | Description | Comments | +|------------------|-----------------------------------------------------------------------------------------------------------|----------| +| 11073-10442_Reqt | Continua X73 strength fitness service and client components shall implement [ISO/IEEE 11073-10442] | | + +### 6.3.14 Activity hub + +This clause contains guidelines for client and service components that implement the activity hub device specialization. The guidelines are contained in Table 6-39. + +**Table 6-39 – Activity hub – General requirements** + +| Name | Description | Comments | +|------------------|-------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Reqt | Continua X73 activity hub service and client components shall implement [ISO/IEEE 11073-10471] | | + +### 6.3.15 Fall sensor + +There is no IEEE 11073 device specialization dedicated to a fall sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create a PHD fall sensor. The guidelines are covered by Table 6-40. + +**Table 6-40 – Fall sensor – General requirements** + +| Name | Description | Comments | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Fall_Reqt | Continua X73 fall sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Fall_Sensor_Object | Continua X73 fall sensor service and client components shall implement the fall sensor enumeration object | | +| 11073_Fall_Sensor_MDC_Code | Continua X73 fall sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_FALL_SENSOR = 4213 (0x1075) | | + +### 6.3.16 Motion sensor + +There is no IEEE 11073 device specialization dedicated to a motion sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create a PHD motion sensor. The guidelines are covered by Table 6-41. + +**Table 6-41 – Motion sensor – General requirements** + +| Name | Description | Comments | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Motion_Reqt | Continua X73 motion sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Motion_Sensor_Object | Continua X73 motion sensor service and client components shall implement the motion sensor enumeration object | | +| 11073_Motion_Sensor_MDC_Code | Continua X73 motion sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_MOTION_SENSOR = 4219 (0x107B) | | + +### 6.3.17 Enuresis sensor + +There is no IEEE 11073 device specialization dedicated to an enuresis sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 enuresis sensor. The guidelines are covered by Table 6-42. + +**Table 6-42 – Enuresis sensor – General requirements** + +| Name | Description | Comments | +|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Enuresis_Reqt | Continua X73 enuresis sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Enuresis_Sensor_Object | Continua X73 enuresis sensor service and client components shall implement the enuresis sensor enumeration object | | +| 11073_Enuresis_Sensor_MDC_Code | Continua X73 enuresis sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_ENURESIS_SENSOR = 4221 (0x107D) | | + +**6.3.18 Contact closure sensor** + +There is no IEEE 11073 device specialization dedicated to a contact closure sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 contact closure sensor. The guidelines are covered by Table 6-43. + +**Table 6-43 – Contact closure sensor – General requirements** + +| Name | Description | Comments | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Contact_Reqt | Continua X73 contact closure sensor service and client components shall implement ISO/IEEE 11073-10471-2008 | | +| 11073_Contact_Closure_Sensor_Object | Continua X73 contact closure sensor service and client components shall implement the contact closure sensor enumeration object | | +| 11073_Contact_Closure_Sensor_MDC_Code | Continua X73 contact closure sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_CONTACTCLOSURE_SENSOR = 4222 (0x107E) | | + +**6.3.19 Switch sensor** + +There is no IEEE 11073 device specialization dedicated to a switch use sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 switch sensor. The guidelines are covered by Table 6-44. + +**Table 6-44 – Switch use sensor – General requirements** + +| Name | Description | Comments | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| 11073-10471_Switch_Reqt | Continua X73 switch sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Switch_Sensor_Object | Continua X73 switch sensor service and client components shall implement the Switch use sensor enumeration object | | +| 11073_Switch_Sensor_MDC_Code | Continua X73 switch sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_SWITCH_SENSOR = 4224 (0x1080) | | + +**6.3.20 Dosage sensor** + +There is no IEEE 11073 device specialization dedicated to a medication dosage sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 dosage sensor. The guidelines are covered by Table 6-45. + +**Table 6-45 – Dosage sensor – General requirements** + +| Name | Description | Comments | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| 11073-10471_Dosage_Reqt | Continua X73 dosage sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Dosage_Sensor_Object | Continua X73 dosage sensor service and client components shall implement the medication dosage sensor enumeration object | | +| 11073_Dosage_Sensor_MDC_Code | Continua X73 dosage sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_DOSAGE_SENSOR = 4225 (0x1081) | | + +**6.3.21 Water sensor** + +There is no IEEE 11073 device specialization dedicated to a water sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 water sensor. The guidelines are covered by Table 6-46. + +**Table 6-46 – Water sensor – General requirements** + +| Name | Description | Comments | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Water_Reqt | Continua X73 Water Sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Water_Sensor_Object | Continua X73 water sensor service and client components shall implement the water sensor enumeration object | | +| 11073_Water_Sensor_MDC_Code | Continua X73 water sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_WATER_SENSOR = 4217 (0x1079) | | + +**6.3.22 Smoke sensor** + +There is no IEEE 11073 device specialization dedicated to a smoke sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 smoke sensor. The guidelines are covered by Table 6-47. + +**Table 6-47 – Smoke sensor – General requirements** + +| Name | Description | Comments | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Smoke_Reqt | Continua X73 smoke sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Smoke_Sensor_Object | Continua X73 smoke sensor service and client components shall implement the smoke sensor enumeration object | | +| 11073_Smoke_Sensor_MDC_Code | Continua X73 smoke sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_SMOKE_SENSOR = 4215 (0x1077) | | + +**6.3.23 Property exit sensor** + +There is no IEEE 11073 device specialization dedicated to a property exit sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 property exit sensor. The guidelines are covered by Table 6-48. + +**Table 6-48 – Property exit sensor – General requirements** + +| Name | Description | Comments | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Exit_Reqt | Continua X73 property exit sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Property_Exit_Sensor_Object | Continua X73 property exit sensor service and client components shall implement the property exit sensor enumeration object | | +| 11073_Property_Exit_Sensor_MDC_Code | Continua X73 property exit sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_PROPEXIT_SENSOR = 4220 (0x107C) | | + +### 6.3.24 Temperature sensor + +There is no IEEE 11073 device specialization dedicated to a temperature sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 temperature sensor. The guidelines are covered in Table 6-49. + +**Table 6-49 – Temperature sensor – General requirements** + +| Name | Description | Comments | +|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Temperature_Reqt | Continua X73 temperature sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Temperature_Sensor_Object | Continua X73 temperature sensor service and client components shall implement the temperature sensor enumeration object | | +| 11073_Temperature_Sensor_MDC_Code | Continua X73 temperature sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_TEMP_SENSOR = 4226 (0x1082) | | + +### 6.3.25 Usage sensor + +There is no IEEE 11073 device specialization dedicated to a usage sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 usage sensor. The guidelines are covered in Table 6-50. + +**Table 6-50 – Usage sensor – General requirements** + +| Name | Description | Comments | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Usage_Reqt | Continua X73 usage sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Usage_Sensor_Object | Continua X73 usage sensor service and client components shall implement the usage sensor enumeration object | | +| 11073_Usage_Sensor_MDC_Code | Continua X73 usage sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_USAGE_SENSOR = 4223 (0x107F) | | + +**6.3.26 PERS sensor** + +There is no IEEE 11073 device specialization dedicated to a PERS sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 PERS sensor. The guidelines are covered in Table 6-51. + +**Table 6-51 – PERS sensor – General requirements** + +| Name | Description | Comments | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_PERS_Reqt | Continua X73 PERS sensor service and client components shall implement ISO/IEEE 11073-10471-2008 | | +| 11073_PERS_Sensor_Object | Continua X73 PERS sensor service and client components shall implement the PERS sensor enumeration object | | +| 11073_PERS_Sensor_MDC_Code | Continua X73 PERS sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_PERS_SENSOR = 4214 (0x1076) | | + +**6.3.27 CO sensor** + +There is no IEEE 11073 device specialization dedicated to a carbon monoxide sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 CO sensor. The guidelines are covered in Table 6-52. + +**Table 6-52 – CO sensor – General requirements** + +| Name | Description | Comments | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_CO_Reqt | Continua X73 CO Sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_CO_Sensor_Object | Continua X73 CO sensor service and client components shall implement the CO sensor enumeration object | | +| 11073_CO_Sensor_MDC_Code | Continua X73 CO sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_FALL_SENSOR = 4216 (0x1078) | | + +### 6.3.28 Gas sensor + +There is no IEEE 11073 device specialization dedicated to a gas sensor. This clause gives guidelines on how to make use of the generic functionality of [ISO/IEEE 11073-10471] to create an X73 gas sensor. The guidelines are covered by Table 6-53. + +**Table 6-53 – Gas sensor – General requirements** + +| Name | Description | Comments | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 11073-10471_Gas_Reqt | Continua X73 gas sensor service and client components shall implement [ISO/IEEE 11073-10471] | | +| 11073_Gas_Sensor_Object | Continua X73 gas sensor service and client components shall implement the gas sensor enumeration object | | +| 11073_Gas_Sensor_MDC_Code | Continua X73 gas sensor service components shall set the MDC_DEV_*_SPEC_PROFILE_* code to MDC_DEV_SUB_SPEC_PROFILE_GAS_SENSOR = 4218 (0x107A) | | + +### 6.3.29 Adherence monitor + +This clause contains guidelines for client and service components that implement the adherence monitor device specialization. The guidelines are contained in Table 6-54. + +**Table 6-54 – Adherence monitor – General requirements** + +| Name | Description | Comments | +|------------------|------------------------------------------------------------------------------------------------------------|----------| +| 11073-10472_Reqt | Continua X73 adherence monitor service and client components shall implement [ISO/IEEE 11073-10472] | | + +### 6.3.30 Sleep apnoea breathing therapy equipment (SABTE) + +This clause contains guidelines for client and service components that implement the SABTE device specialization. The guidelines are contained in Table 6-55. + +**Table 6-55 – SABTE – General requirements** + +| Name | Description | Comments | +|------------------|------------------------------------------------------------------------------------------------|----------| +| 11073-10424_Reqt | Continua X73 SABTE service and client components shall implement [ISO/IEEE 11073-10424] | | + +### 6.3.31 Continuous glucose monitor (CGM) + +This clause contains guidelines for client and service components that implement the CGM device specialization. The guidelines are contained in Table 6-56. + +**Table 6-56 – Continuous glucose monitor – General requirements** + +| Name | Description | Comments | +|------------------|----------------------------------------------------------------------------------------------|-----------------| +| 11073-10425-Reqt | Continua X73 CGM service and client components shall implement [ISO/IEEE 11073-10425] | | + +### **6.3.32 Insulin pump (IP)** + +This clause contains guidelines for client and service components that implement the insulin pump device specialization. The guidelines are contained in Table 6-57. + +**Table 6-57 – Insulin pump - General requirements** + +| Name | Description | Comments | +|------------------|---------------------------------------------------------------------------------------------|-----------------| +| 11073-10419-Reqt | Continua X73 IP service and client components shall implement [ISO/IEEE 11073-10419] | | + +### **6.3.33 Power status monitor (PSM)** + +This clause contains guidelines for client and service components that implement the power status monitor device specialization. The guidelines are contained in Table 6-58. + +**Table 6-58 – Power status monitor - General requirements** + +| Name | Description | Comments | +|------------------|------------------------------------------------------------------------------------------|-----------------| +| 11073-10427-Reqt | Continua X73 PSM service and client components shall implement [IEEE 11073-10427] | | + +## **7 NFC interface design guidelines** + +### **7.1 NFC interface architecture (informative)** + +This clause lists the design guidelines specific for interoperability of Personal Health Devices and Personal Health Gateways using the NFC interface. The position of the NFC interface in the Continua architecture is illustrated in Figure 7-1. + +![Figure 7-1: NFC interface context diagram showing the flow of data from Personal Health Devices (X73, Bluetooth LE) through a Personal Health Gateway (PHG) to Health & Fitness services and then to a Healthcare Information System (HIS).](c0b9e5fc63e19306394e0d4249da62cd_img.jpg) + +The diagram illustrates the context of the NFC interface. On the left, a 'Personal Health Device' box contains icons for an 'X73 device' and a 'Bluetooth LE device'. An orange vertical bar labeled 'Personal Health Devices interface' lists protocols: IEEE, ISO, X73-IF, **NFC forum** (circled in red), ZigBee, Bluetooth, USB, BLE-IF, and Bluetooth LE. This bar connects to a 'Personal Health Gateway (PHG)' box containing device icons. The PHG connects to a 'Services interface' bar listing HL7, IHE, OASIS, IETF, and W3C. This interface connects to a 'Health & Fitness service' box with a cloud icon. This service connects to an 'HIS interface' bar listing the same protocols (HL7, IHE, OASIS, IETF, W3C). The HIS interface connects to a 'Healthcare Information System (HIS)' box containing icons for a hospital, a blood test, and a medical bag. The code 'H.811(17)\_F7-1' is in the bottom right. + +Figure 7-1: NFC interface context diagram showing the flow of data from Personal Health Devices (X73, Bluetooth LE) through a Personal Health Gateway (PHG) to Health & Fitness services and then to a Healthcare Information System (HIS). + +Figure 7-1 – NFC interface context + +### 7.1.1 Overview of NFC interface + +NFC enables a Continua Personal Health Device (PHD) to communicate with a Continua Personal Health Gateway (PHG) by touch. A user brings the two devices into close proximity for a short period of time – typically by touching one device with the other. While the devices are touching, data may be exchanged bidirectionally. In a typical use case a user would transfer blood pressure readings from their blood pressure meter (Continua PHD) to a mobile phone (Continua PHG) by simply touching the two devices together. Figure 7-2 illustrates the structure of the NFC interface stack. + +![Figure 7-2: NFC interface stack diagram showing the layers of the NFC protocol stack.](e417ae35ab07134888be901c201d54cd_img.jpg) + +The diagram shows the NFC interface stack as a vertical stack of layers. From top to bottom: a yellow box for 'IEEE 11073 application protocol (ISO layer 6, 7)' containing two sub-layers: '1104xx device specialization' and '20601 optimized exchange protocol'; a purple oval for 'NFC PHD class (ISO layer 5)'; and a blue oval for 'NFC (ISO layer 4)'. The code 'H.811(16)\_F7-2' is at the bottom. + +Figure 7-2: NFC interface stack diagram showing the layers of the NFC protocol stack. + +Figure 7-2 – NFC interface stack + +### 7.1.2 Transport protocols and selected standards + +[NFC PHDC] has been selected to serve as the transport protocol for the NFC interface (NFC-IF). + +The selected protocol for the transport layer ensures interoperable set-up and tear-down of the communication channel for the transfer of control and data messages across all domains. Note that NFC works over a range of up to 10 centimetres, so that actual touching of devices might not even be required. + +### 7.1.3 Exchange protocols and selected standards + +For the data and messaging layer of the NFC-IF, the IEEE 11073 Personal Health Device family of standards has been selected. For the detailed list of selected data/messaging layer standards see clause 6.1.3. + +### 7.1.4 Device communication styles + +NFC is intended for a batch communication style. This style requires the transport between the device and the PHG to communicate previously collected data points at a later time. The user chooses the moment of communication by touching the devices. + +In QoS terms explained in clause 6.1.7 of [ITU-T H.810], NFC is best.medium. Communication is acknowledged and must be complete or the transaction is rejected. Latency is typically <1 second for a NFC application. + +### 7.1.5 NFC interface security + +For a NFC solution, it is assumed that the physical action of the user touching two devices provides a suitable level of security to prevent inadvertent leakage of data to a different PHG. + +Designers of NFC PHDs should take normal care for NFC systems to ensure a robust design that cannot be easily intercepted or interrogated by an antenna that is not in very close physical contact or touching. Typically this is done by managing power and physically shielding components to ensure that only two antennas that are in very close contact are capable of communication exchange. + +Note that such measures help to increase the security of the system, but they cannot prevent the effects of all security threats that are inherent to the nature of NFC. It is advised that PHD manufacturers implement suitable security controls and mechanisms based on a security risk analysis. + +## 7.2 NFC interface guidelines + +This clause contains design guidelines that apply to NFC physical devices. These can be Personal Health Devices implementing service components or Personal Health Gateways implementing client components. + +### 7.2.1 NFC PHD to PHG linkage + +This clause contains a guideline for NFC-IF service components to limit connections to one client component. The guideline is covered by Table 7-1. + +**Table 7-1 – NFC PHD to PHG linkage** + +| Name | Description | Comments | +|------------------------|----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| NFC-Device-PHG-Linkage | A Continua NFC-IF service component shall connect with only one Continua NFC-IF client component at any given time. | The Continua reference topology as described in [ITU-T H.810] restricts communication to a single client component. | + +### 7.2.2 NFC user experience + +NFC PHDs and PHGs communicate in close proximity which is normally caused by the user bringing a NFC-IF service component PHD close to a NFC-IF client component PHG, or vice versa. This clause contains design guidelines that strongly recommend specific device behaviour to ensure a satisfying user experience. The guidelines are covered by Table 7-2. + +**Table 7-2 – NFC user experience** + +| Name | Description | Comments | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TAN_Device_Taptime | A Continua NFC-IF service component should complete data exchange within 3 seconds | Completion of data exchange within an acceptable amount of time is specifically important where the user must hold NFC service and client components in proximity for the duration of the data exchange | +| TAN_User_Notification | Continua NFC-IF service and client components with appropriate UI capabilities should notify the user when data exchange is completed | Appropriate user notifications are specifically important where the user must hold NFC service and client components in proximity for the duration of the data exchange | + +### 7.2.3 NFC Personal Health Device communication + +This clause contains a general design guideline that points to [NFC PHDC]. All subsequent requirements in clause 7.2.3 refer to this specification. The guideline is covered in Table 7-3. + +**Table 7-3 – NFC Personal Health Device communication map** + +| Name | Description | Comments | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| TAN_NFC_PHDC_Map | Continua NFC-IF wireless service and client components shall implement NFC Personal Health Device communication version 1.0 subject to the design guidelines described in the sub-clauses below. | | + +### 7.2.4 Multi-function devices + +This clause defines how devices that implement more than one IEEE 11073 PHD device specialization are represented via [NFC PHDC]. These guidelines require that all multi-function devices expose all device specializations via a single IEEE 11073-20601 association. In NFC, a single IEEE 11073-20601 association maps best to a single NFC PHDC agent interface. Thus, a Continua-certified NFC PHDC device has only one NFC PHDC agent interface for Continua functionality, regardless of whether it exposes a single device specialization or multiple device specializations. The guideline is covered in Table 7-4. + +**Table 7-4 – NFC multi-function devices** + +| Name | Description | Comments | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TAN_11073-20601_
    Multi-Function | A Continua NFC-IF service component shall have at most one IEEE 11073-20601 association to a NFC-IF client component at any point in time regardless of whether the device is a single function or multi-function device | This guideline prohibits the device from having two concurrent associations. The device may provide different configuration options in subsequent associations only after closing the currently active association | + +### 7.2.5 NFC quality of service + +The requirements in Table 7-5 describe how quality of service (QoS) attributes are used for Continua NFC-IF service and client components. + +**Table 7-5 – NFC quality of service** + +| Name | Description | Comments | +|------------------------------|---------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| +| NFC-PHDC-QoS-
    Best.Medium | Continua NFC-IF service and client components shall provide the Continua best.medium QoS bin | NFC PHDC transport does exchange all data on best.medium QoS bin | +| NFC-PHDC-QoS-
    Good.Medium | Continua NFC-IF service and client components shall not provide the Continua good.medium QoS bin | NFC PHDC transport does exchange all data on best.medium QoS bin | + +### 7.3 NFC Certified Capability Classes + +Table 7-6 shows the Certified Capability Classes defined for the NFC interface design guidelines. A certification program run by the Personal Connected Health Alliance exists for devices that implement the CDG. For NFC devices, the certification testing will be performed on an integrated device, meaning the testing and certification is applied to the hardware and software of the device. Changes to components of the device may require a re-certification. Table 7-6 also references the guidelines (clause numbers) that are applicable for each of the Certified Capability Classes. An empty table entry would indicate that there is currently no certified capability class defined. + +**Table 7-6 – NFC Certified Capability Classes** + +| Certified Capability Classes | Relevant guidelines | +|---------------------------------------------------------------------------------------------------|---------------------| +| NFC Activity Hub service
    NFC Activity Hub client | 6.2, 6.3.14, 7.2 | +| NFC Adherence Monitor service
    NFC Adherence Monitor client | 6.2, 6.3.29, 7.2 | +| NFC Basic 1-3 Lead ECG service
    NFC Basic 1-3 Lead ECG client | 6.2, 6.3.2, 7.2 | +| NFC Blood Pressure Monitor service
    NFC Blood Pressure Monitor client | 6.2,, 6.3.4, 7.2 | +| NFC Cardiovascular Fitness service
    NFC Cardiovascular Fitness client | 6.2, 6.3.11, 7.2 | +| NFC Cardiovascular Fitness Step Counter service
    NFC Cardiovascular Fitness Step Counter client | 6.2, 6.3.12, 7.2 | + +**Table 7-6 – NFC Certified Capability Classes** + +| Certified Capability Classes | Relevant guidelines | +|-------------------------------------------------------------------------------------|----------------------------| +| NFC CO Sensor service
    NFC CO Sensor client | 6.2, 6.3.27, 7.2 | +| NFC Contact Closure Sensor service
    NFC Contact Closure Sensor client | 6.2, 6.3.18, 7.2 | +| NFC Continuous Glucose Monitor service
    NFC Continuous Glucose Monitor client | 6.2, 6.3.31, 7.2 | +| NFC Enuresis Sensor service
    NFC Enuresis Sensor client | 6.2, 6.3.17, 7.2 | +| NFC Fall Sensor service
    NFC Fall Sensor client | 6.2, 6.3.15, 7.2 | +| NFC Gas Sensor service
    NFC Gas Sensor client | 6.2, 6.3.28, 7.2 | +| NFC Glucose Meter service
    NFC Glucose Meter client | 6.2, 6.3.7, 7.2 | +| NFC Heart-rate Sensor service
    NFC Heart-rate Sensor client | 6.2, 6.3.3, 7.2 | +| NFC INR Meter service
    NFC INR Meter client | 6.2, 6.3.8, 7.2 | +| NFC Insulin Pump service
    NFC Insulin Pump client | 6.2, 6.3.32, 7.2 | +| NFC Medication Dosage Sensor service
    NFC Medication Dosage Sensor client | 6.2, 6.3.20, 7.2 | +| NFC Motion Sensor service
    NFC Motion Sensor client | 6.2, 6.3.16, 7.2 | +| NFC peak expiratory flow monitor service
    NFC peak expiratory flow monitor client | 6.2, 6.3.10, 7.2 | +| NFC PERS Sensor service
    NFC PERS Sensor client | 6.2, 6.3.26, 7.2 | +| NFC Power Status Monitor service
    NFC Power Status Monitor client | 6.2, 6.3.33, 7.2 | +| NFC Property Exit Sensor service
    NFC Property Exit Sensor client | 6.2, 6.3.23, 7.2 | +| NFC Pulse Oximeter service
    NFC Pulse Oximeter client | 6.2, 6.3.1, 7.2 | +| NFC Smoke Sensor service
    NFC Smoke Sensor client | 6.2, 6.3.22, 7.2 | +| NFC Strength Fitness service
    NFC Strength Fitness client | 6.2, 6.3.13, 7.2 | +| NFC Switch Sensor service
    NFC Switch Sensor client | 6.2, 6.3.19, 7.2 | + +**Table 7-6 – NFC Certified Capability Classes** + +| Certified Capability Classes | Relevant guidelines | +|-----------------------------------------------------------------|---------------------| +| NFC Temperature Sensor service
    NFC Temperature Sensor client | 6.2, 6.3.24, 7.2 | +| NFC Thermometer service
    NFC Thermometer client | 6.2, 6.3.5, 7.2 | +| NFC Usage Sensor service
    NFC Usage Sensor client | 6.2, 6.3.25, 7.2 | +| NFC Water Sensor service
    NFC Water Sensor client | 6.2, 6.3.21, 7.2 | +| NFC Weighing scales service
    NFC Weighing scales client | 6.2, 6.3.6, 7.2 | + +**8 USB interface design guidelines** + +**8.1 USB interface architecture (informative)** + +This clause lists the design guidelines specific for interoperability between certified PHDs and PHGs when using USB across the Personal Health Devices interface (PHD-IF). + +![Figure 8-1 – USB interface context. A diagram showing the flow of data from Personal Health Devices (X73 and Smart devices) through a Personal Health Gateway (PHG) to a Health & Fitness service, and finally to a Healthcare Information System (HIS). The diagram highlights the USB interface within the PHD-IF stack.](4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg) + +The diagram illustrates the USB interface context. On the left, two boxes represent 'X73 device' and 'Smart device', both categorized under 'Personal Health Device'. These devices connect to a central 'Personal Health Devices interface' box. This box lists several protocols: 'IEEE ISO X73-IF', 'NFC forum ZigBee Bluetooth', 'USB' (circled in red), 'BLE-IF', and 'Bluetooth LE'. The 'USB' connection leads to a 'Personal Health Gateway (PHG)' box, which contains icons of a smartphone, tablet, and laptop. From the PHG, a green line connects to a 'Services interface' box, which lists 'HL7', 'IHE', 'OASIS', 'IETF', and 'W3C'. This interface connects to a 'Health & Fitness service' box (containing a cloud and server icons). From this service, a blue line connects to an 'HIS interface' box, which also lists 'HL7', 'IHE', 'OASIS', 'IETF', and 'W3C'. The HIS interface connects to a 'Healthcare Information System (HIS)' box, which contains icons of a hospital, a medical chart, and a doctor's bag. The text 'H.811(17)\_F8-1' is in the bottom right corner. + +Figure 8-1 – USB interface context. A diagram showing the flow of data from Personal Health Devices (X73 and Smart devices) through a Personal Health Gateway (PHG) to a Health & Fitness service, and finally to a Healthcare Information System (HIS). The diagram highlights the USB interface within the PHD-IF stack. + +**Figure 8-1 – USB interface context** + +**8.1.1 Overview of USB interface** + +The connectivity in the USB interface (USB-IF) is tailored to satisfying three basic requirements that are uniform across the application domains serviced by CDG-certified products: + +- allow bidirectional sensor control + +- allow bidirectional sensor information exchange +- allow appropriate linkage between a Personal Health Device and a Personal Health Gateway + +The interface is further structured into three distinct layers, with appropriate standards selected to represent the individual layers and establish interoperability in the personal health ecosystem. Figure 8-1 illustrates the USB interface context. + +### 8.1.2 Exchange protocols and selected standards + +For the data and messaging layer of the standard USB-IF, the standards from the IEEE 11073 Personal Health Device family of standards have been selected. For the detailed list of selected data/messaging layer standards, see clause 6.2.3. + +### 8.1.3 USB device communication styles + +The protocols selected in the USB-IF permits the device to transfer data in the following three communication styles: + +- Transaction communication style: When it is required that the transport between the PHD and the PHG communicates a single data point immediately. +- Streaming communication style: When it is required that the transport between the PHD and the PHG communicates several data points continuously. +- Batch communication style: When it is required that the transport between the PHD and the PHG communicates previously collected data points at a later time. + +The specific requirements pertaining to the QoS for USB for the various communication styles are outlined in clause 8.2.5. + +### 8.1.4 USB-IF security + +For a USB solution, it is assumed that the physical action of the user connecting a USB PHD to the PHG provides the necessary security to prevent inadvertent leakage of data to a different PHG. + +## 8.2 USB device and interface guidelines + +This clause contains design guidelines that apply to USB physical devices. These can be Personal Health Devices or Personal Health Gateways. + +### 8.2.1 USB device to PHG linkage + +Table 8-1 shows USB device to PHG linkage. + +**Table 8-1 – USB device to PHG linkage** + +| Name | Description | Comments | +|------------------------|----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| USB-Device-PHG-Linkage | A Continua USB-IF service component shall connect with only one Continua USB-IF client component at any given time. | The Continua reference topology as described in [ITU-T H.810] restricts communication to a single client component. | + +### 8.2.2 USB general requirements + +This clause contains a general design guideline that points to the USB personal healthcare device class (PHDC) v1.0 [USB DevClass]. All subsequent requirements in clause 8.2 refer to this specification. + +For more information about [USB DevClass] device drivers please see Appendix III and in [b-CHA USB-PHDC]. + +**Table 8-2 – USB personal healthcare device class v1.0 map** + +| Name | Description | Comments | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| USB-Personal Healthcare-v1.0 | Continua USB-IF service and client components shall implement the USB personal healthcare device class v1.0 plus the Feb. 15, 2008 errata, subject to the requirements listed in the sub-clauses below. | | + +### 8.2.3 USB map to IEEE 11073-20601 + +This clause requires that a Continua-compliant device send only IEEE 11073-20601 data and messages over USB PHDC. In addition, driver software implementing the USB PHDC transport should not need to parse the IEEE 11073-20601 data to fully function. + +**Table 8-3 – ISO/IEEE 11073-20601 messaging layer** + +| Name | Description | Comments | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| USB-PHDC-20601-Map-Service | Continua USB-IF service components shall set the USB PHDC v1.0 bPHDCDataCode field of the PHDC Class Function descriptor equal to PHDC_11073_20601 | | +| USB-PHDC-20601-Map-Client | Continua USB-IF client components shall accept PHDC Class Function descriptors with the USB PHDC v1.0 bPHDCDataCode field equal to PHDC_11073_20601 | | +| USB-PHDC-20601-Device-Spec-Cert-Dev-Classes | Continua USB-IF service components shall set the wDevSpecializations field(s) to the corresponding [ISO/IEEE 11073-20601] MDC_DEV_SPEC_PROFILE_* value(s) corresponding to the certified Capability Class(es) that the component supports | | +| USB-PHDC-20601-Device-Spec-Not-Cert | Continua USB-IF service components may add additional [ISO/IEEE 11073-20601] MDC_DEV_SPEC_PROFILE_* value(s) corresponding to supported IEEE specializations that are not Continua certified in the wDevSpecializations array | | + +**Table 8-3 – ISO/IEEE 11073-20601 messaging layer** + +| Name | Description | Comments | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| USB-PHDC-20601-10101-Client | Continua USB-IF client components shall not pre-filter and reject a service component based on the wDevSpecializations field(s) value(s) | The rejection of unsupported device specializations happens in the higher layers via the [ISO/IEEE 11073-20601] optimized exchange protocol | +| USB-EndOfTransfer | Continua USB-IF service and client components shall signify the end of a bulk transfer by transferring a payload of size less than wMaxPacketSize or a zero-length packet | USB-IF service and client components are not required to read the [ISO/IEEE 11073-20601] data to obtain the length | + +#### 8.2.4 Sending metadata via USB PHDC + +The USB PHDC specification [USB DevClass] contains a feature to enable the sending of QoS information with IEEE 11073-20601 [ISO/IEEE 11073-20601] data and messages. The USB PHDC specification states that this feature is optional for service components to support and mandatory for client components to support. + +It is not expected that Continua USB-IF service components will implement the feature or Continua USB-IF client components will enable the feature; however, if a service component or client component chooses to make use of the feature, the design guidelines contained in Table 8-4 apply. + +**Table 8-4 – Using USB PHDC metadata/QoS feature** + +| Name | Description | Comments | +|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| USB-PHDC-Enable-Meta-Data-Preamble | Continua USB-IF client components that choose to enable the USB PHDC Meta-Data Message Preamble feature shall attempt to enable the feature by sending the USB PHDC SET_FEATURE (FEATURE_PHDC_METADATA A) request after the [ISO/IEEE 11073-20601] Association Request message has been received and before it sends the [ISO/IEEE 11073-20601] Association Response message | | + +**Table 8-4 – Using USB PHDC metadata/QoS feature** + +| Name | Description | Comments | +|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| USB-PHDC-Disable-Meta-Data-Preamble | Continua USB-IF client components that choose to enable the USB PHDC Meta-Data Message Preamble feature shall disable the feature when in the Unassociated state only by sending the USB PHDC CLEAR_FEATURE (FEATURE_PHDC_METADATA) request | | +| USB-bQoSEncodingVersionOOB | Continua USB-IF client components that receive a bQoSEncodingVersion field that is not 01h shall ignore the bmLatencyReliability bitmap as it could have a different meaning in a future version of the specification | This replaces the text "In order to remain forward compatible, if a host implementing 01h QoS information encoding receives a bQoSEncodingVersion field that is not 01h, it shall ignore the descriptor." on page 22, 1st paragraph, of [USB DevClass] | + +### 8.2.5 USB quality of service + +The requirements contained in Table 8-5 describe how QoS attributes are used for Continua USB-IF service and client components. + +**Table 8-5 – Mapping of USB PHDC QoS bins into Continua QoS bins** + +| Name | Description | Comments | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| USB-QoS-Best.Medium | Continua USB-IF service and client components that implement the Continua best.medium QoS bin shall utilize the USB PHDC best.medium QoS bin to do this | | +| USB-QoS-Good.Medium | Continua USB-IF service and client components that implement the Continua good.medium QoS bin shall utilize the USB PHDC good.medium QoS bin to do this | | + +### 8.2.6 USB multi-function devices + +This clause defines how devices that implement more than one IEEE 11073 PHD device specialization are represented via USB PHDC. The Continua CDG requires that all multi-function devices expose all device specializations via a single IEEE 11073-20601 association. In USB, a single IEEE 11073-20601 association maps best to a single USB PHDC interface. Thus, a Continua-certified USB PHDC device has only one USB PHDC interface for CDG functionality, regardless of whether it exposes a single device specialization or multiple device specializations. This is shown in Figure 8-2. + +![Diagram showing the mapping of IEEE 11073-20601 associations to a single USB interface. On the left, a box labeled 'Single 11073 communication' contains multiple boxes for '11073 device specialization #1', '11073 device specialization #2', and '11073 device specialization #n'. On the right, a box labeled 'Single USB interface' contains boxes for 'Endpoint 0', 'Endpoint 1', and 'Endpoint 2' (dashed border), with vertical ellipsis between them. A horizontal line connects the two boxes.](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +H.811(18)\_F8-2 + +Diagram showing the mapping of IEEE 11073-20601 associations to a single USB interface. On the left, a box labeled 'Single 11073 communication' contains multiple boxes for '11073 device specialization #1', '11073 device specialization #2', and '11073 device specialization #n'. On the right, a box labeled 'Single USB interface' contains boxes for 'Endpoint 0', 'Endpoint 1', and 'Endpoint 2' (dashed border), with vertical ellipsis between them. A horizontal line connects the two boxes. + +**Figure 8-2 – USB PHDC mapping to IEEE 11073-20601 associations** + +Table 8-6 contains the design guidelines for USB multi-function devices. + +**Table 8-6 – USB multi-function devices** + +| Name | Description | Comments | +|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| USB-PHDC-Multi-Function-Single-Interface | Continua USB-IF service components, whether multi-function or single function, shall implement one and only one USB PHDC interface for the component's IEEE 11073-20601 association | CDG requires that all USB multi-function devices expose all functions via a single IEEE 11073-20601 association. See 11073-20601-Multi-Function. | + +## 8.2.7 USB connectors + +USB contains a few connector options on the service and client side. The design guidelines contained in Table 8-7 give guidance on connector choices for implementation. + +**Table 8-7 – USB connectors** + +| Name | Description | Comments | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| USB-B-Connector-Connectivity | A Continua USB PHD should be shipped with a mechanism for connecting itself to a PHG assuming a standard-A connector to the PHG | Example connectivity mechanisms include a cable that connects to the device and exposes a standard-A connector and an integral cable on the device that exposes a standard-A connector | +| USB-B-Connector-Mechanism-to-Obtain-Connectivity | If a Continua USB PHD does not ship with a mechanism for connectivity as defined in USB-B-Connector-Connectivity, it shall ship with a mechanism for obtaining such connectivity | Example mechanisms for obtaining connectivity include documentation on the type of cable needed and possibly, a phone number, mail in the form or website for requesting and/or purchasing that cable | + +**Table 8-7 – USB connectors** + +| Name | Description | Comments | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| USB-A-Connector-Connectivity | Continua USB PHGs that do not accept a standard-A female connector should be shipped with a mechanism for converting to accept a standard-A female connector | Example mechanisms include a converter from the A connector on the PHG to standard-A | +| USB-A-Connector-Mechanism-to-Obtain-Connectivity | If a Continua USB PHG that does not accept a Standard-A female connector does not ship with a mechanism for converting to standard-A female connector, it shall be shipped with a mechanism for obtaining a conversion to accept a standard-A female connector | Example mechanisms include documentation on the necessary converter and possibly, a phone number, mail in the form or website for requesting and/or purchasing that converter | + +### 8.2.8 USB data rates + +USB 2.0 provides full speed and high speed data rates. USB 1.1 provides low speed and full speed data rates. Table 8-8 describes the requirements CDG places on the data rates to be used. + +**Table 8-8 – USB data rates** + +| Name | Description | Comments | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| USB-Low-Speed | Continua USB-IF service and client components shall not use low speed | Low speed is mostly used for keyboards, mice and joysticks. Low speed does not support all data rates required by the CDG. Max packet size for low-speed is 8 bytes. Low-speed also has behavioural differences with full and high speed.

    NOTE - Low speed is only available in USB 1.1 | +| USB-USB-2.0 | Continua USB-IF service and client components should implement USB 2.0 | | +| USB-USB-1.1 | Continua USB-IF service and client components shall implement at least USB 1.1 or any superior version compatible with USB 1.1 | | + +### 8.3 USB Certified Capability Classes + +Table 8-9 shows the Certified Capability Classes defined for the USB-IF design guidelines. A certification program run by Continua Health Alliance exists for devices that implement the CDG. For USB PHDs and PHGs, the certification testing will be performed on an integrated device, + +meaning the testing and certification is applied to the hardware and software of the device. Changes to components of the device may require a re-certification. Table 8-9 also references the guidelines (clause numbers) that are applicable for each of the Certified Capability Classes. + +**Table 8-9 – USB Certified Capability Classes** + +| Certified Capability Classes | USB (relevant guidelines) | +|---------------------------------------------------------------------------------------------------|----------------------------------| +| USB Activity Hub service
    USB Activity Hub client | 6.2, 6.3.14, 8.2 | +| USB Adherence Monitor service
    USB Adherence Monitor client | 6.2, 6.3.29, 8.2 | +| USB Basic 1-3 Lead ECG service
    USB Basic 1-3 Lead ECG client | 6.2, 6.3.2, 8.2 | +| USB Blood Pressure Monitor service
    USB Blood Pressure Monitor client | 6.2, 6.3.4, 8.2 | +| USB Cardiovascular Fitness service
    USB Cardiovascular Fitness client | 6.2, 6.3.11, 8.2 | +| USB Cardiovascular Fitness Step Counter service
    USB Cardiovascular Fitness Step Counter client | 6.2, 6.3.12, 8.2 | +| USB CO Sensor service
    USB CO Sensor client | 6.2, 6.3.27, 8.2 | +| USB Contact Closure Sensor service
    USB Contact Closure Sensor client | 6.2, 6.3.18, 8.2 | +| USB Continuous Glucose Monitor service
    USB Continuous Glucose Monitor client | 6.2, 6.3.31, 8.2 | +| USB Enuresis Sensor service
    USB Enuresis Sensor client | 6.2, 6.3.17, 8.2 | +| USB Fall Sensor service
    USB Fall Sensor client | 6.2, 6.3.15, 8.2 | +| USB Gas Sensor service
    USB Gas Sensor client | 6.2, 6.3.28, 8.2 | +| USB Glucose Meter service
    USB Glucose Meter client | 6.2, 6.3.7, 8.2 | +| USB Heart-rate Sensor service
    USB Heart-rate Sensor client | 6.2, 6.3.3, 8.2 | +| USB INR Meter service
    USB INR Meter client | 6.2, 6.3.8, 8.2 | +| USB Insulin Pump service
    USB Insulin Pump client | 6.2, 6.3.32, 8.2 | +| USB Medication Dosage Sensor service
    USB Medication Dosage Sensor client | 6.2, 6.3.20, 8.2 | +| USB Motion Sensor service
    USB Motion Sensor client | 6.2, 6.3.16, 8.2 | +| USB peak expiratory flow monitor service
    USB peak expiratory flow monitor client | 6.2, 6.3.10, 8.2 | + +**Table 8-9 – USB Certified Capability Classes** + +| Certified Capability Classes | USB (relevant guidelines) | +|---------------------------------------------------------------------|----------------------------------| +| USB PERS Sensor service
    USB PERS Sensor client | 6.2, 6.3.26, 8.2 | +| USB Power Status Monitor service
    USB Power Status Monitor client | 6.2, 6.3.33, 8.2 | +| USB Property Exit Sensor service
    USB Property Exit Sensor client | 6.2, 6.3.23, 8.2 | +| USB Pulse Oximeter service
    USB Pulse Oximeter client | 6.2, 6.3.1, 8.2 | +| USB SABTE service
    USB SABTE client | 6.2, 6.3.30, 8.2 | +| USB Smoke Sensor service
    USB Smoke Sensor client | 6.2, 6.3.22, 8.2 | +| USB Strength Fitness service
    USB Strength Fitness client | 6.2, 6.3.13, 8.2 | +| USB Switch Sensor service
    USB Switch Sensor client | 6.2, 6.3.19, 8.2 | +| USB Temperature Sensor service
    USB Temperature Sensor client | 6.2, 6.3.24, 8.2 | +| USB Thermometer service
    USB Thermometer client | 6.2, 6.3.5, 8.2 | +| USB Usage Sensor service
    USB Usage Sensor client | 6.2, 6.3.25, 8.2 | +| USB Water Sensor service
    USB Water Sensor client | 6.2, 6.3.21, 8.2 | +| USB Weighing scales service
    USB Weighing scales client | 6.2, 6.3.6, 8.2 | + +## **9 Bluetooth BR/EDR interface design guidelines** + +### **9.1 Bluetooth BR/EDR interface architecture (informative)** + +This clause lists the design guidelines specific for interoperability between certified PHDs and PHGs when using Bluetooth BR/EDR across the Personal Health Devices interface. + +![Figure 9-1 – Bluetooth interface context diagram. The diagram shows the flow of data from Personal Health Devices (X73 device, Smart device) through a Personal Health Gateway (PHG) to a Health & Fitness service, and finally to a Healthcare Information System (HIS). The interfaces are categorized into Personal Health Devices interface, Services interface, and HIS interface. The Bluetooth interface is highlighted with a red circle.](a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg) + +The diagram illustrates the Bluetooth interface context within a personal health ecosystem. On the left, two boxes represent 'Personal Health Devices': an 'X73 device' (containing icons of various sensors) and a 'Smart device' (containing icons of a smartphone and a sensor). These connect to a central 'Personal Health Gateway (PHG)' box. The connection between the devices and the PHG is labeled 'Personal Health Devices interface' and lists several standards: IEEE, ISO, X73-IF, NFC forum, ZigBee, **Bluetooth** (circled in red), USB, BLE-IF, and Bluetooth LE. The PHG connects to a 'Health & Fitness service' (represented by a cloud icon with server symbols). This connection is labeled 'Services interface' and lists standards: HL7, IHE, OASIS, IETF, and W3C. The 'Health & Fitness service' then connects to a 'Healthcare Information System (HIS)' (represented by icons of a hospital, a test tube, and a medical professional). This final connection is labeled 'HIS interface' and lists the same standards as the services interface: HL7, IHE, OASIS, IETF, and W3C. A small label 'H.811(17)\_F9-1' is in the bottom right corner. + +Figure 9-1 – Bluetooth interface context diagram. The diagram shows the flow of data from Personal Health Devices (X73 device, Smart device) through a Personal Health Gateway (PHG) to a Health & Fitness service, and finally to a Healthcare Information System (HIS). The interfaces are categorized into Personal Health Devices interface, Services interface, and HIS interface. The Bluetooth interface is highlighted with a red circle. + +Figure 9-1 – Bluetooth interface context + +### 9.1.1 Overview of Bluetooth BR/EDR interface + +The connectivity in the Bluetooth BR/EDR interface (BR/EDR-IF) is tailored to satisfying three basic requirements that are uniform across the application domains serviced by CDG-certified products: + +- allow bidirectional sensor control +- allow bidirectional sensor information exchange +- allow appropriate linkage between a Personal Health Device and a Personal Health Gateway + +The interface is further structured into three distinct layers, with appropriate standards selected to represent the individual layers and establish interoperability in the personal health ecosystem. Figure 9-1 illustrates the the Bluetooth interface context. + +## 9.2 Bluetooth BR/EDR interface guidelines + +### 9.2.1 Bluetooth BR/EDR PHD to PHG linkage + +Table 9-1 contains a guideline for Bluetooth BR/EDR PHD to PHG linkage. + +Table 9-1 – Bluetooth BR/EDR PHD to PHG linkage + +| Name | Description | Comments | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| ContinuaStructType | A Continua BR/EDR-IF service component shall connect with only one Continua BR/EDR-IF client component at any given time. | The Continua reference topology as described in [ITU-T H.810] restricts communication to a single client component. | + +## 9.2.2 Bluetooth health device profile + +This clause contains general design guidelines covered in Table 9-2 that point to [Bluetooth HDPv1.1]. All subsequent requirements in clause 9.2 refer to this specification. For further guidance on implementing the Bluetooth health device profile the reader is referred to the white paper [b-Bluetooth HDPIP]. + +Throughout this clause, some common Bluetooth terms are used: + +When the term "discovery" is used, this is meant to describe use of the Bluetooth inquiry substate to learn of the existence of other Bluetooth devices within transmission range. This is sometimes called "device discovery" to distinguish from service discovery. A Bluetooth device is discoverable if it periodically enters the inquiry scan substate. A discoverable device will respond to inquiry procedures (usually a general inquiry) from any device that wants to search. + +A Bluetooth device enters the inquiry substate to discover other Bluetooth devices. Discoverable devices will periodically enter the inquiry scan substate. + +Service discovery creates a baseband connection to a specific device (may be paired, but does not need to be) to discover details about services offered on that device. + +When the term "pairing" is used, this is meant to describe the exchange of link keys to establish a future trust relationship with a known device. Except in legacy cases, this is performed with secure simple pairing (SSP). + +When the term "connectable" is used, this is meant to describe a previously paired device that is periodically entering the page scan substate and responds to pages from devices that address it specifically (by Bluetooth MAC address). For a device to be connected, it must first be paired. + +**Table 9-2 – Bluetooth health device profile map** + +| Name | Description | Comments | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-BR/EDR-Map | Continua BR/EDR-IF service and client components shall be compliant with Bluetooth 2.1. | Later versions of the Bluetooth specification can be used as long as version 2.1 functionality is fully supported. | +| Bluetooth-BR/EDR-HDP-Map | Continua BR/EDR-IF service and client components shall be compliant with Bluetooth Health Device Profile version 1.1, subject to the design guidelines described in the sub-clauses below. | Later versions of the Bluetooth HDP specification can be used as long as version 1.1 functionality is fully supported. | + +## 9.2.3 Discovery and pairing + +Continua X73 Bluetooth BR/EDR devices transfer measurement data to partner devices. These partnerships are formed either following a search initiated by the client component that will receive the data or through an out-of-band configuration. + +This specification requires a process of discovery of the service component by the client component for all Bluetooth CDG devices. This ensures a consistent and user-friendly pairing procedure. + +The guidelines throughout this clause create a single and universally supported technique for pairing devices that give a minimum of surprise or inconvenience to users. These guidelines contained in Table 9-3 apply to Bluetooth versions 2.0 and 2.1. + +**Table 9-3 – Bluetooth BR/EDR pairing guidelines** + +| Name | Description | Comments | +|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-BR/EDR-Discovery-Initiation-Client | Continua BR/EDR-IF client components shall initiate discovery (a Bluetooth "Inquiry") | | +| Bluetooth-BR/EDR-Discovery-Initiation-Service | Continua BR/EDR-IF service components should not initiate discovery (a Bluetooth "Inquiry") | | +| Bluetooth-BR/EDR-Pairing-Service | Continua BR/EDR-IF service components shall have a documented way (decided by the vendor) to initiate a mode of "discoverable by the client component"
    Once a service component has been made discoverable in this way, it shall support pairing with compatible client components, as shown in Figure 9-2 | The words 'compatible client components' refer to client components that share the same device specialization as the service component | +| Bluetooth-BR/EDR-Pairing-Client | Continua BR/EDR-IF client components shall have a documented way (decided by the vendor) to initiate a search for service components that are "discoverable"
    Once the client component has discovered such service component, it shall support pairing with compatible service components, as shown in Figure 9-3 | The words 'compatible service components' refer to service components that share the same device specialization as the client component
    Client components may be pre-configured to pair with a specific service component; however, they are required to provide support for discovery and pairing of any compatible service component. | +| Bluetooth-BR/EDR-All-Pairing-Client | Continua BR/EDR-IF client components shall support all pairing methods for Bluetooth 2.1, including Just Works, Numeric Comparison, and Passkey Entry, if the client component has the appropriate I/O capabilities | I/O capabilities include display, keyboard, yes/no. See the Bluetooth core specification [Bluetooth CS2.1] and secure simple pairing white papers for further information.
    This pairing guideline is necessary to ensure interoperability and give reasonable assurance that a service component's chosen pairing method will be supported by client components | +| Bluetooth-BR/EDR-Legacy-Pairing-Client | Continua BR/EDR-IF client components shall support legacy (Bluetooth 2.0) pin entry pairing | This guideline is necessary to ensure backward compatibility with existing Continua BT 2.0 service components | + +**Table 9-3 – Bluetooth BR/EDR pairing guidelines** + +| Name | Description | Comments | +|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-BR/EDR-Pairing-Service-2 | Continua BR/EDR-IF service components shall support at least one of the following Bluetooth 2.1 pairing methods depending on their I/O capabilities and appropriate security for the service component device type: Just Works, Numeric Comparison, or Passkey Entry | I/O capabilities include display, keyboard, yes/no. See the Bluetooth core specification [Bluetooth CS2.1] and secure simple pairing white papers for further information | +| Bluetooth-BR/EDR-Re-Pairing | Once a Continua BR/EDR-IF service component has been paired with a client component, it shall remain possible to re-initiate the mode "discoverable by the client component" | | +| Bluetooth-BR/EDR-Data-Exchange-Service | Continua BR/EDR-IF service component data (not including HDP service discovery record or static information like capabilities, service names, etc.) shall not be exchanged with client components for which a pairing has not been established | | +| Bluetooth-BR/EDR-Discoverability-Mode-Service | By default, Continua BR/EDR-IF service components should not be discoverable unless put in that mode as documented above | | +| Bluetooth-BR/EDR-Discoverability-Mode-Client | Continua BR/EDR-IF client components should not be discoverable unless put in that mode as documented above | | +| Bluetooth-BR/EDR-Discoverability-Duration | Continua BR/EDR-IF service components should provide a documented minimum duration (decided by the vendor) for this discoverable mode, once initiated, after which it ceases to be discoverable | | +| Bluetooth-BR/EDR-Paired | When a Continua BR/EDR-IF service component is discoverable and successfully completes a pairing procedure, it should immediately become undiscoverable | | + +![Figure 9-2: Continua Bluetooth BR/EDR pairing process for service components. The diagram shows four states: 'Not discoverable, no pairing, not connected' (initial state, reached from 'Clean' service component), 'Discoverable, no pairing, not connected' (reached via 'Become discoverable', returns via 'Timeout or cancel'), 'Not discoverable, paired, not connected' (reached via 'Complete first pairing'), and 'Discoverable, paired, not connected' (reached via 'Complete additional pairing timeout or cancel', returns via 'Become discoverable'). Transitions between the last two states are 'Connect' and 'Disconnect'. A 'Pre-paired' service component is shown as an external entity.](e2dad48ec062e71202459a9ab82261e4_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S0: "Clean" service component + S0 --> S1: Become discoverable + S1 --> S0: Timeout or cancel + S1 --> S2: Complete first pairing + S2 --> S3: Complete additional pairing timeout or cancel + S3 --> S2: Become discoverable + S2 --> S3: Connect + S3 --> S2: Disconnect + PrePaired[Pre-paired service component] --> S2 + +``` + +H.811(10)\_F9-2 + +Figure 9-2: Continua Bluetooth BR/EDR pairing process for service components. The diagram shows four states: 'Not discoverable, no pairing, not connected' (initial state, reached from 'Clean' service component), 'Discoverable, no pairing, not connected' (reached via 'Become discoverable', returns via 'Timeout or cancel'), 'Not discoverable, paired, not connected' (reached via 'Complete first pairing'), and 'Discoverable, paired, not connected' (reached via 'Complete additional pairing timeout or cancel', returns via 'Become discoverable'). Transitions between the last two states are 'Connect' and 'Disconnect'. A 'Pre-paired' service component is shown as an external entity. + +Figure 9-2 – Continua Bluetooth BR/EDR pairing process for service components + +![Figure 9-3: Continua Bluetooth BR/EDR pairing process for client components. The diagram shows four states: 'Not in inquiry state, no pairing, not connected' (initial state, reached from 'Clean' client component), 'Discoverable, no pairing, not connected' (reached via 'Initiate device discovery (inquiry)', returns via 'Timeout or cancel'), 'Not discoverable, paired, not connected' (reached via 'Complete first pairing'), and 'Discoverable, paired, not connected' (reached via 'Complete additional pairing timeout or cancel', returns via 'Initiate device discovery (inquiry)'). Transitions between the last two states are 'Connect' and 'Disconnect'. A 'Pre-paired' client component is shown as an external entity.](8ab30dbff406204a68c59ae7c1b77413_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S0: "Clean" client component + S0 --> S1: Initiate device discovery (inquiry) + S1 --> S0: Timeout or cancel + S1 --> S2: Complete first pairing + S2 --> S3: Complete additional pairing timeout or cancel + S3 --> S2: Initiate device discovery (inquiry) + S2 --> S3: Connect + S3 --> S2: Disconnect + PrePaired[Pre-paired client component] --> S2 + +``` + +H.811(10)\_F9-3 + +Figure 9-3: Continua Bluetooth BR/EDR pairing process for client components. The diagram shows four states: 'Not in inquiry state, no pairing, not connected' (initial state, reached from 'Clean' client component), 'Discoverable, no pairing, not connected' (reached via 'Initiate device discovery (inquiry)', returns via 'Timeout or cancel'), 'Not discoverable, paired, not connected' (reached via 'Complete first pairing'), and 'Discoverable, paired, not connected' (reached via 'Complete additional pairing timeout or cancel', returns via 'Initiate device discovery (inquiry)'). Transitions between the last two states are 'Connect' and 'Disconnect'. A 'Pre-paired' client component is shown as an external entity. + +Figure 9-3 – Continua Bluetooth BR/EDR pairing process for client components + +The diagram in Figure 9-2 shows the behaviour of a Continua BR/EDR-IF service component in the pairing process and the diagram in Figure 9-3 shows the behaviour of a BR/EDR-IF client component in the pairing process. Some Bluetooth BR/EDR devices may permit pairing from non-discoverable states, if the partner device knows the MAC address of the service component (either through out-of-band configuration or from a previous device discovery operation). These transitions although technically possible are not shown, for reasons of simplicity. Because they represent a non-standard operation of the device, they may present a security vulnerability for some applications. + +Table 9-4 – Bluetooth BR/EDR pairing in non-discoverable states + +| Name | Description | Comments | +|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-BR/EDR-Non-Discovery-Service | If a Continua BR/EDR-IF service component is able to prevent pairing while in non-discoverable states, it should do so | | + +Table 9-4 contains the guideline for Bluetooth BR/EDR pairing in non-discoverable states. The reason for this procedure is to provide security and privacy for users while optimizing the ease of use by providing predictable behaviour and by minimizing the time and effort required to execute the pairing. + +Another ease-of-use issue is the frequency required for a user to go through the pairing procedure. To avoid unnecessary re-pairings following battery replacements or power failures, persistent storage on sensors is important. Table 9-5 contains guidelines for Bluetooth BR/EDR pairing data. + +**Table 9-5 – Bluetooth BR/EDR pairing data** + +| Name | Description | Comments | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-BR/EDR-Pairing-Data-Service | Continua BR/EDR-IF service components shall store the pairing data from at least the most recently paired device in such a way that the data will be retained through normal power interruptions, including battery replacement | | +| Bluetooth-BR/EDR-Pairing-Data-Client | Continua BR/EDR-IF client components shall store the pairing data from at least the most recently paired device in such a way that the data will be retained through normal power interruptions, including battery replacement
    Continua BR/EDR-IF client components should store pairing data for at least the number of devices for which they are intended to simultaneously support | | + +#### 9.2.4 Bluetooth BR/EDR discoverable mode + +The requirements in clause 9.2.3 refer to a mode where a device is "discoverable by the client component". In Bluetooth terms, this means the device is in both "discoverable mode" and "pairable mode" (also known as "bondable mode"). When a device is in Bluetooth "discoverable mode", other devices can perform inquiries to learn its MAC address. From a CDG point of view, since all communication is between paired devices, it does not make sense for a service component to be discoverable unless it is willing to pair with devices that discover it. + +Leaving a device in the discoverable (and pairable) state opens the device to hackers who may attempt to connect. Being discoverable is a security risk, as well as a privacy risk. Table 9-6 contains the guideline for the Bluetooth BR/EDR discovery disable mechanism. + +**Table 9-6 – Bluetooth BR/EDR discovery disable** + +| Name | Description | Comments | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-BR/EDR-Discovery-Disable | Continua BR/EDR-IF service components that may become discoverable in the course of normal use should offer users a mechanism to disable this behaviour | | + +To avoid pairing with devices that cannot be used, it is helpful for devices to allow access to their HDP service discovery protocol (SDP) record to enable a connecting device, to query the capability of devices and identify the device specializations supported. Table 9-7 contains the guideline for Bluetooth SDP access. + +**Table 9-7 – Bluetooth SDP access** + +| Name | Description | Comments | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-BR/EDR-SDP-Access | When possible, Continua BR/EDR-IF service components in "discoverable mode" should allow access to their SDP entries without first requiring a pairing to be established | | + +The Bluetooth HDP SDP record includes a list of supported [ISO/IEEE 11073-104xx] specializations under the SDP attribute "MDEP Data Type". This list is used to filter devices for suitability and is required by the Bluetooth HDP specification [Bluetooth HDPv1.1] to match the list of [ISO/IEEE 11073-104xx] specializations actually supported by the implementation. Table 9-8 contains the guidelines for the Bluetooth SDP record. + +**Table 9-8 – Bluetooth SDP record** + +| Name | Description | Comments | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-BR/EDR-SDP-Record | The specializations claimed in Continua certification shall match the list of specializations advertised in the Continua BR/EDR-IF service component HDP SDP record | | +| Bluetooth-BR/EDR-SDP-Extensions | The Continua BR/EDR-IF service component HDP SDP record may contain additional specialization identifiers that are not Continua certified | | + +### 9.2.5 Notifying the user + +Establishing a new pairing relationship is an important event. Because of the potential for confusion, extreme care should be used before automating the pairing procedure. To allow users reasonable control of their Continua systems, PHGs are required to provide a facility for alerting users of significant events, see Table 9-9. Because discovery may be difficult for users to understand, it is important to inform them of new pairings and reasons for failure. The design guidelines in this clause intentionally leave the nature of notifying and informing the user to be defined by the manufacturer. + +**Table 9-9 – Bluetooth BR/EDR user notification** + +| Name | Description | Comments | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-BR/EDR-Pairing-Creation-Alert-Client | Continua BR/EDR-IF client components shall inform the user when a new pairing relationship is created | | +| Bluetooth-BR/EDR-Pairing-Creation-Alert-Service | Continua BR/EDR-IF service components should notify the user, whenever possible, when a new pairing relationship is created | | +| Bluetooth-BR/EDR-Pairing-Failure-Alert-Client | When a pairing fails, Continua BR/EDR-IF client components shall inform the user whether the failure was because no service component was found (discovery failed), no data types are supported in common by both the client component and service component (incompatible device), or the pairing failed (pairing failure) | | +| Bluetooth-BR/EDR-Pairing-Failure-Alert-Service | Whether or not pairing fails, Continua BR/EDR-IF service components should inform the user, whenever possible, if no data types are supported in common by both the client component and service component (incompatible device), or the pairing failed (pairing failure) | | + +Actual use of devices varies widely and it is not always clear which device is more physically convenient to the user during these pairing events. For this reason and also to increase the chance that a user will notice improper use of a device, pairing notifications should be made as noticeable as possible. Table 9-10 contains guidelines for Bluetooth BR/EDR authentication/security failure notification. + +**Table 9-10 – Bluetooth BR/EDR authentication/security failure notification** + +| Name | Description | Comments | +|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-BR/EDR-Security-Failure-Client | When any authentication/security failure is encountered by Continua BR/EDR-IF client components, client components shall notify the user | | +| Bluetooth-BR/EDR-Security-Failure-Service | When any authentication/security failure is encountered by Continua BR/EDR-IF service components, service components should notify the user whenever possible | | + +## 9.2.6 Quality of service + +Table 9-11 contains guidelines for Bluetooth BR/EDR quality of service. + +**Table 9-11 – Bluetooth BR/EDR quality of service** + +| Name | Description | Comments | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| +| Bluetooth-BR/EDR-QoS-Best.Medium | Continua BR/EDR-IF service and client components that implement the Continua best.medium QoS bin shall utilize the HDP reliable data channel type to do this | See clause 6.1.7.2 in [ITU-T H.810] for a definition of the QoS bins. | +| Bluetooth-BR/EDR-QoS-Good.Medium | Continua BR/EDR-IF service and client components that implement the Continua good.medium QoS bin shall utilize the HDP streaming data channel type to do this | See clause 6.1.7.2 in [ITU-T H.810] for a definition of the QoS bins | + +While the Bluetooth core specification [Bluetooth CS2.1] specifies the use of a 16-bit FCS by default, it is optional in HDP [Bluetooth HDPv1.1] for "Reliable" and "Streaming" data channel + +types to disable the frame check sequence (FCS) if both sides agree during negotiation. The baseband already uses a CRC to detect bit errors in the data frames and FCS implements a second CRC to increase the probability of error detection. While devices that can tolerate an occasional error (e.g., a pedometer counting the number of steps walked) and have limited processor or battery resources may opt not to use FCS, FCS is recommended for all other cases. This will significantly improve (estimated to be on the order of thousands of times) the probability that an error is detected. Table 9-12 contains the guideline for Bluetooth BR/EDR error detection. + +**Table 9-12 – Bluetooth BR/EDR error detection** + +| Name | Description | Comments | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-BR/EDR-FCS | When possible and appropriate to the device, Continua BR/EDR-IF service and client components should use FCS for all data channels | | + +### 9.2.7 Secure simple pairing debug mode + +If a device compliant with Bluetooth version 2.1 connects to another device also compliant with Bluetooth version 2.1, the use of secure simple pairing (SSP) in Bluetooth is mandatory. SSP results in an encrypted link requiring a private key to decrypt packets. To make the decryption of over-air packets possible for the purposes of test and debug when SSP is used (e.g., via a sniffer or protocol analyser), devices compliant with Bluetooth 2.1 would need to implement the SSP debug mode. Debug mode only needs to be supported by one of the two sides of the link for over-air decryption to be possible. + +### 9.3 Bluetooth BR/EDR Certified Capability Classes + +Table 9-13 shows the Certified Capability Classes defined for the BR/EDR-IF design guidelines. A certification program run by Continua Health Alliance exists for devices that implement the CDG. For Bluetooth BR/EDR devices, the certification testing will be performed on an integrated device, meaning the testing and certification is applied to the hardware and software of the device. Changes to components of the device may require a re-certification. Table 9-13 also references the guidelines (clause numbers) that are applicable for each of the Certified Capability Classes. + +**Table 9-13 – Bluetooth BR/EDR Certified Capability Classes** + +| Certified Capability Class | Relevant guidelines | +|-----------------------------------------------------------------------------------------------------------------------------|---------------------| +| Bluetooth BR/EDR Activity Hub service
    Bluetooth BR/EDR Activity Hub client | 6.2, 6.3.14, 9.2 | +| Bluetooth BR/EDR Adherence Monitor service
    Bluetooth BR/EDR Adherence Monitor client | 6.2, 6.3.29, 9.2 | +| Bluetooth BR/EDR Basic 1-3 Lead ECG service
    Bluetooth BR/EDR Basic 1-3 Lead ECG client | 6.2, 6.3.2, 9.2 | +| Bluetooth BR/EDR Blood Pressure Monitor service
    Bluetooth BR/EDR Blood Pressure Monitor client | 6.2, 6.3.4, 9.2 | +| Bluetooth BR/EDR Cardiovascular Fitness service
    Bluetooth BR/EDR Cardiovascular Fitness client | 6.2, 6.3.11, 9.2 | +| Bluetooth BR/EDR Cardiovascular Fitness Step Counter service
    Bluetooth BR/EDR Cardiovascular Fitness Step Counter client | 6.2, 6.3.12, 9.2 | +| Bluetooth BR/EDR CO Sensor service
    Bluetooth BR/EDR CO Sensor client | 6.2, 6.3.27, 9.2 | + +**Table 9-13 – Bluetooth BR/EDR Certified Capability Classes** + +| Certified Capability Class | Relevant guidelines | +|---------------------------------------------------------------------------------------------------------------|----------------------------| +| Bluetooth BR/EDR Contact Closure Sensor service
    Bluetooth BR/EDR Contact Closure Sensor client | 6.2, 6.3.18, 9.2 | +| Bluetooth BR/EDR Continuous Glucose Monitor service
    Bluetooth BR/EDR Continuous Glucose Monitor client | 6.2, 6.3.31, 9.2 | +| Bluetooth BR/EDR Enuresis Sensor service
    Bluetooth BR/EDR Enuresis Sensor client | 6.2, 6.3.17, 9.2 | +| Bluetooth BR/EDR Fall Sensor service
    Bluetooth BR/EDR Fall Sensor client | 6.2, 6.3.15, 9.2 | +| Bluetooth BR/EDR Gas Sensor service
    Bluetooth BR/EDR Gas Sensor client | 6.2, 6.3.28, 9.2 | +| Bluetooth BR/EDR Glucose Meter service
    Bluetooth BR/EDR Glucose Meter client | 6.2, 6.3.7, 9.2 | +| Bluetooth BR/EDR Heart-rate Sensor service
    Bluetooth BR/EDR Heart-rate Sensor client | 6.2, 6.3.3, 9.2 | +| Bluetooth BR/EDR INR Meter service
    Bluetooth BR/EDR INR Meter client | 6.2, 6.3.8, 9.2 | +| Bluetooth BR/EDR Insulin Pump service
    Bluetooth BR/EDR Insulin Pump client | 6.2, 6.3.32, 9.2 | +| Bluetooth BR/EDR Medication Dosage Sensor service
    Bluetooth BR/EDR Medication Dosage Sensor client | 6.2, 6.3.20, 9.2 | +| Bluetooth BR/EDR Motion Sensor service
    Bluetooth BR/EDR Motion Sensor client | 6.2, 6.3.16, 9.2 | +| Bluetooth BR/EDR peak expiratory flow monitor service
    Bluetooth BR/EDR peak expiratory flow monitor client | 6.2, 6.3.10, 9.2 | +| Bluetooth BR/EDR PERS Sensor service
    Bluetooth BR/EDR PERS Sensor client | 6.2, 6.3.26, 9.2 | +| Bluetooth BR/EDR power status monitor service
    Bluetooth BR/EDR power status monitor client | 6.2, 6.3.33, 9.2 | +| Bluetooth BR/EDR Property Exit Sensor service
    Bluetooth BR/EDR Property Exit Sensor client | 6.2, 6.3.23, 9.2 | +| Bluetooth BR/EDR Pulse Oximeter service
    Bluetooth BR/EDR Pulse Oximeter client | 6.2, 6.3.1, 9.2 | +| Bluetooth BR/EDR SABTE service
    Bluetooth BR/EDR SABTE client | 6.2, 6.3.30, 9.2 | +| Bluetooth BR/EDR Smoke Sensor service
    Bluetooth BR/EDR Smoke Sensor client | 6.2, 6.3.22, 9.2 | +| Bluetooth BR/EDR Strength Fitness service
    Bluetooth BR/EDR Strength Fitness client | 6.2, 6.3.13, 9.2 | +| Bluetooth BR/EDR Switch Sensor service
    Bluetooth BR/EDR Switch Sensor client | 6.2, 6.3.19, 9.2 | + +**Table 9-13 – Bluetooth BR/EDR Certified Capability Classes** + +| Certified Capability Class | Relevant guidelines | +|-------------------------------------------------------------------------------------------|---------------------| +| Bluetooth BR/EDR Temperature Sensor service
    Bluetooth BR/EDR Temperature Sensor client | 6.2, 6.3.24, 9.2 | +| Bluetooth BR/EDR Thermometer service
    Bluetooth BR/EDR Thermometer client | 6.2, 6.3.5, 9.2 | +| Bluetooth BR/EDR Usage Sensor service
    Bluetooth BR/EDR Usage Sensor client | 6.2, 6.3.25, 9.2 | +| Bluetooth BR/EDR Water Sensor service
    Bluetooth BR/EDR Water Sensor client | 6.2, 6.3.21, 9.2 | +| Bluetooth BR/EDR Weighing scales service
    Bluetooth BR/EDR Weighing scales client | 6.2, 6.3.6, 9.2 | + +## 10 ZigBee interface design guidelines + +### 10.1 ZigBee interface architecture (informative) + +#### 10.1.1 Introduction to the ZigBee interface + +This clause lists the design guidelines specific to interoperability between Continua certified PHDs and PHGs using the ZigBee across the Personal Health Devices interface. Figure 10-1 illustrates the ZigBee interface in the context of the Continua E2E architecture. The ZigBee interface is a particular sub-class of the Continua PHD-IFs and connects ZigBee PHDs to PHGs across all three CDG domains, disease management, ageing independently, and health and fitness. + +![Figure 10-1 – ZigBee interface diagram showing the flow from Personal Health Devices (X73 and Bluetooth LE) through a Personal Health Gateway (PHG) to a Health & Fitness service, and finally to a Healthcare Information System (HIS).](4537891530c9f6f139a2e1ebf544edc4_img.jpg) + +The diagram illustrates the ZigBee interface architecture. On the left, a 'Personal Health Device' box contains icons for an 'X73 device' and a 'Bluetooth LE device'. These devices connect to a 'Personal Health Devices interface' box, which lists standards: IEEE, ISO, X73-IF, NFC forum, ZigBee (circled in red), Bluetooth, USB, BLE-IF, and Bluetooth LE. This interface connects to a 'Personal Health Gateway (PHG)' box. The PHG connects to a 'Services interface' box, which lists standards: HL7, IHE, OASIS, IETF, and W3C. The Services interface connects to a 'Health & Fitness service' box (represented by a cloud icon). This service connects to an 'HIS interface' box, which also lists standards: HL7, IHE, OASIS, IETF, and W3C. The HIS interface connects to a 'Healthcare Information System (HIS)' box, which contains icons for a hospital, a blood test, and a medical kit. The diagram is labeled H.811(17)\_F10-1. + +Figure 10-1 – ZigBee interface diagram showing the flow from Personal Health Devices (X73 and Bluetooth LE) through a Personal Health Gateway (PHG) to a Health & Fitness service, and finally to a Healthcare Information System (HIS). + +**Figure 10-1 – ZigBee interface** + +### 10.1.2 Scope of the ZigBee interface + +The ZigBee interface enables sensors (or actuators) to send their measured data to (or to be controlled by) one or many Continua PHGs that are placed around the same house, building, facility or campus. In this respect, the ZigBee interface provides wireless infrastructure based connectivity in an area around a location. The network coverage area can scale up to several hundreds of metres, with several tens and up to several thousands of devices being a part of that network. The location of sensors/actuators (PHDs) connected via the ZigBee interface can be fixed as well as mobile, with the latter case referring to devices (e.g., body worn) roaming throughout the network up to walking/running speed. Furthermore, many years of battery lifetime is enabled for PHDs connected via the ZigBee interface. See Figure 10-2 for a high-level illustrative diagram of the ZigBee conceptual set-up. In Figure 10-2(a), ZigBee PHDs utilize an existing wireless infrastructure network for communication and, in Figure 10-2(b), ZigBee PHDs are part of and are contributing to the wireless infrastructure network. + +The use of the ZigBee interface is not limited to large-scale, long-range networks, but can also be used to establish direct short-range connections between PHDs and PHGs as well. + +In the 2010 version of the CDG, the scope of the ZigBee interface was restricted to many-to-one connectivity. According to this, a PHG may connect to one or more ZigBee PHDs at the same time, but a Continua ZigBee PHD was allowed to connect to a single Continua PHG at the same time only. In this version of the CDG, the extension to many-to-many connectivity is defined, i.e., the simultaneous connection of a ZigBee PHD to multiple PHGs at the same time is supported. + +![Figure 10-2 – ZigBee conceptual set-up. The diagram is divided into two rows, A and B, showing different ZigBee network topologies. Row A shows PHD devices connected to an existing wireless infrastructure. Row B shows PHD devices extending the wireless infrastructure. Both rows show data flow from PHD devices through a Personal Health Gateway to Health & Fitness services in the BackEnd infrastructure.](5e05915b2a93a3b404422e0966a7c924_img.jpg) + +The diagram illustrates the ZigBee conceptual set-up, organized into two rows (A and B) and three columns representing different components of the system. + +- Top Headers:** + - Home environment:** A large box containing the Zigbee infrastructure and Personal Health Gateway components. + - BackEnd infrastructure:** A box containing the Health & Fitness services component. +- Row A: PHD devices utilizing existing ZigBee wireless infrastructure** + - Zigbee infrastructure (wireless):** Four "Continua Zigbee PHD device" icons are shown. Two are connected to a central "Existing wireless infrastructure" node (represented by two red circles with white diagonal lines). The other two are connected to the first two devices. + - Personal Health Gateway:** Two desktop computer icons. Blue arrows point from the top and bottom PHD devices to these gateways. Text between the gateways states: "The PHD devices can transmit measurements to one or more PHGs". + - Health & Fitness services:** A cloud icon containing a server rack. A yellow arrow points from the gateways to the services. +- Row B: PHD devices helping to form the ZigBee (wireless) infrastructure** + - Zigbee infrastructure (wireless):** Four "Continua Zigbee PHD device" icons are shown. Two are connected to the "Existing wireless infrastructure" node. The other two are labeled as "Continua Zigbee PHD devices extending wireless infrastructure" and are connected to each other and the existing infrastructure nodes. + - Personal Health Gateway:** Two desktop computer icons. Blue arrows point from the top and bottom PHD devices to these gateways. Text between the gateways states: "The PHD devices can transmit measurements to one or more PHGs". + - Health & Fitness services:** A cloud icon containing a server rack. A yellow arrow points from the gateways to the services. + +H.811(17)\_F10-2 + +Figure 10-2 – ZigBee conceptual set-up. The diagram is divided into two rows, A and B, showing different ZigBee network topologies. Row A shows PHD devices connected to an existing wireless infrastructure. Row B shows PHD devices extending the wireless infrastructure. Both rows show data flow from PHD devices through a Personal Health Gateway to Health & Fitness services in the BackEnd infrastructure. + +**Figure 10-2 – ZigBee conceptual set-up** + +### 10.1.3 Overview of the ZigBee interface + +The interface is structured into distinct layers. Appropriate standards are selected for the individual layers to establish interoperability in the personal health ecosystem. See Figure 6-2 for an overview of the protocol stack of the ZigBee interface. + +### 10.1.4 Transport protocol and selected standards + +The ZigBee health care profile version 1.0 has been selected as the wireless lower layer protocol to serve as the transport for the ZigBee interface. The selected protocol for the transport layer ensures + +interoperable set-up and teardown of the communication network for transfer of control information and transfer of data messages across all domains. + +#### **10.1.5 Data exchange protocol and selected standards** + +For the data and messaging layer of the ZigBee interface, the standards from the IEEE 11073 Personal Health Device family of standards have been selected. For the detailed list of selected data/messaging layer standards please see clause 6. + +#### **10.2 ZigBee interface guidelines** + +##### **10.2.1 ZigBee transport layer** + +###### **10.2.1.1 ZigBee health care profile** + +This clause contains a general design guideline that points to the ZigBee health care (HC) profile version 1.0 [ZigBee HCP]. All subsequent requirements in clause 10.2.1 refer to this specification. + +Because the commissioning of ZigBee devices can be challenging, in particular for large-scale networks due to the wireless nature of the connections, it is important to specify the proper procedures for the commissioning of ZigBee PHDs, which include network-joining and application pairing of devices and device discovery, as well as security mechanisms. It is equally important to inform the users and installers of relevant events related to commissioning, such as the successful application pairing of PHDs and the reasons for failure. These required procedures and notifications are defined in the ZigBee healthcare profile version 1.0. Table 10-1 shows the ZigBee health care profile map. + +**Table 10-1 – ZigBee health care profile map** + +| Name | Description | Comments | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| ZigBee-HC-Map | Continua ZigBee service and client components shall implement ZigBee Health Care Profile version 1.0, subject to the design guidelines described in the sub-clauses below. | | + +###### **10.2.1.2 Quality of service** + +The requirements contained in Table 10-2 describe how QoS attributes are used for Continua ZigBee components. + +**Table 10-2 – ZigBee quality of service** + +| Name | Description | Comments | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| ZigBee-QoS-Best.Medium | Continua ZigBee service and client components that implement the Continua best.medium QoS bin shall utilize ZigBee APS acknowledgements | | +| ZigBee-QoS-Good.Medium | Continua ZigBee service and client components that implement the Continua good.medium QoS bin shall not utilize ZigBee APS acknowledgements | | + +**10.2.1.3 ZigBee multiple connections** + +The requirement contained in Table 10-3 describes how the ZigBee health care profile is used for multiple concurrent ZigBee interface connections. + +**Table 10-3 – ZigBee multiple connections** + +| Name | Description | Comments | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| ZigBee-MultipleConnections | Continua ZigBee service components that establish multiple ZigBee interface connections as described in Clause 10.2.2.1 shall use a separate ZigBee endpoint for each | | + +**10.2.2 ZigBee data/messaging layer** + +This clause contains data/messaging layer design guidelines that are specific to the ZigBee interface, and thus it is not part of the set of common data/messaging layer design guidelines in clause 6.2. + +**10.2.2.1 ZigBee component one-to-many connectivity** + +This clause describes guidelines for a sensor entering a one-to-many connectivity relationship, i.e., a ZigBee service component establishing multiple concurrent ZigBee interface connections at the same instant in time. Example scenarios include multi-function sensors providing different functionality to multiple PHGs, as well as single-function sensors providing its single functionality to multiple PHGs at the same instant in time. How to use the IEEE 11073-20601 mechanisms for association, sensor time control and PM-store usage in a one-to-many connectivity scenario are described. + +**10.2.2.1.1 ZigBee dominant association** + +The 'dominant association' concept is introduced for managing on the service component multiple simultaneous associations with one or more client components. Only through a dominant association, is a service component granting a client component control over its clock and persistently stored data. A service component can have zero or one dominant association. In this way, potential conflicts of multiple client components trying to control these resources on the agent are prevented. Client components are largely unaffected by the dominant association concept. Almost all the guidelines in Table 10-4 apply to service components only. + +**Table 10-4 – ZigBee dominant association** + +| Name | Description | Comments | +|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ZigBee-11073-20601-One-to-Many-Connect | Any Continua ZigBee service component that establishes more than one, simultaneous connection to one or more ZigBee client components at the same point in time shall create an ISO/IEEE 11073-20601 association to a ZigBee client component per connection and follow the guidelines in the remainder of this table | This guideline provides guidance for a device to establish multiple concurrent ZigBee connections | +| ZigBee-11073-20601-One-to-Many-SinglePHG | A Continua ZigBee service component that connects to a single ZigBee client component may create a single connection or multiple connections for providing its functions | The use of multiple connections allows turning on and off the connection of individual functions of the agent without affecting the connection of the other functions.
    However, in some cases, using a single connection only can be required, e.g., in case the ZigBee client component rejects the request for more than a single connection due to the fact that it is compliant to the 2010 CDG release and does not expect multiple connection requests from a single ZigBee service component | +| ZigBee-11073-20601-One-to-Many-ConnectionSetup | Continua ZigBee service components that establish more than one, simultaneous connection to one ZigBee client components at the same point in time shall create a new association to that ZigBee client component, if and only if, all other connections are in the Unassociated or Operating state | This guideline ensures that connection set-up is completed before the creation of an additional connection, and thus reduces unnecessary complexity on the client side to deal with multiple associations simultaneously | +| ZigBee-11073-20601-DominantAssoc | Continua ZigBee service components shall have at most a single dominant ISO/IEEE 11073-20601 association at a single point in time | A ZigBee service component provides the PHG control of its resources (e.g., setting of real time clock and removal of PM-Store data) via its dominant association only. An ISO/IEEE 11073-20601 association becomes the dominant association if one or more of the following MDS-Time-Info attribute bits or PM-Store-Capab attribute bits are set: mds-time-mgr-set-time , mds-time-capab- | + +**Table 10-4 – ZigBee dominant association** + +| Name | Description | Comments | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove, pmsc-clear-segm-all-sup | +| ZigBee-11073-20601-DominantAssoc-ControlBits | Continua ZigBee service components shall not set any of following MDS-Time-Info attribute bits or PM-Store-Capab attribute bits for other than its dominant association: mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove, pmsc-clear-segm-all-sup | | +| ZigBee-11073-20601-DominantAssoc-SetTime | Continua ZigBee service components that modified their clock based on the reception of a Set-Time action via its dominant association shall send an event report that contains the new Date-and-Time attribute value for all their non-dominant associations prior to sending any temporarily stored measurements and prior to starting a new transfer of a PM-Segment | In case the service component receives the Set-Time action during an ongoing PM-Segment transfer, see ZigBee-11073-20601-DateAndTimeUpdate-PMSegmentTransfer-* for further guidance | +| ZigBee-11073-20601-DominantAssoc-Closing | Continua ZigBee service components may close their dominant association | | +| ZigBee-11073-20601-DominantAssoc-Downgrading | Continua ZigBee service components may downgrade their dominant association to become a non-dominant association | Downgrading of the dominant association to a non-dominant association is achieved by sending an event report containing corresponding updates for the MDS-Time-Info attribute bits, so that the conditions of ZigBee-11073-20601-DominantAssoc-ControlBits for non-dominant associations are met.

    Note that the PM-Store-Capab attribute is static. Changing its bit values requires releasing the association and associating again, using a different configuration | +| ZigBee-11073-20601-DominantAssoc-Upgrading | Continua ZigBee service components that do not have a dominant association may upgrade an existing non- | Upgrading an existing association to a dominant association is achieved by sending an event report containing corresponding | + +**Table 10-4 – ZigBee dominant association** + +| Name | Description | Comments | +|------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | dominant association to become the dominant association | updates for the MDS-Time-Info attribute bits.
    Note that the PM-Store-Capab attribute is static. Changing its bit values requires releasing the association and associating again, using a different configuration | + +**10.2.2.1.2 ZigBee time-stamping** + +This clause describes additional requirements for the use of time stamps as specified in [ISO/IEEE 11073-20601]. Table 10-5 contains guidelines for ZigBee timestamping. + +**Table 10-5 – ZigBee time-stamping** + +| Name | Description | Comments | +|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ZigBee-11073-20601-DataDuplicate-Timestamping | Continua ZigBee service components shall time-stamp data that is intended to be sent multiple times, over different connections | Sending the same data multiple times can be done over the same connection or over different connections. If time stamps were missing and if the same data was sent multiple times over different connections to separate PHGs, then those PHGs would be responsible for timestamping and might have different notions of time.
    To cover such scenarios, this guideline sets more restrictions for the timestamping of data sent multiple times. According to [ISO/IEEE 11073-20601] data needs to be time-stamped only if it is locally stored or persistently stored on an agent before being transmitted | +| ZigBee-11073-20601-FixedTimeStamps | Continua ZigBee service components shall use the same time stamp for data that is transmitted multiple times | An example scenario where this guideline applies is the case that a service component sends the same data to multiple different clients and assigns time stamps while transmitting the data instead of while sampling the data. According to this guideline, the time stamps used for the same data are required to be identical | + +### 10.2.2.1.3 ZigBee Timeout management + +This clause describes additional requirements improving interoperability in cases where timeouts as specified in [ISO/IEEE 11073-20601] are not met. Table 10-6 contains guidelines for ZigBee timeout management. + +**Table 10-6 – ZigBee timeout management** + +| Name | Description | Comments | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ZigBee-11073-20601-TimeoutIndication | Continua ZigBee service components shall not cause a timeout on a particular connection, due to activity related to another existing connection | Here, timeouts caused by service components relate to an expected response to a GET request, a confirmed SET command, or a confirmed Action command, invoked by a ZigBee client component being in the operating state | +| ZigBee-11073-20601-PM-Store-TransferTimeout | Continua ZigBee service components that implement and use the PM-Store model should correctly initialize the PM-Segment object Transfer-Timeout attribute to a value accounting for the maximum number of entries stored in the segment, as well as the maximum number of supported ongoing segment transfers via other associations | The size of a segment, as well as the amount of traffic due to potential concurrent segment transfer via other connections affects the time needed for transferring a complete PN-Segment | + +### 10.3 ZigBee Certified Capability Classes + +Table 10-7 shows the Certified Capability Classes defined for the ZigBee interface design guidelines. A certification program run by Personal Connected Health Alliance exists for devices that implement the CDG. For ZigBee PHDs and PHGs, the certification testing will be performed on an integrated device, meaning the testing and certification is applied to the hardware and software of the device. Changes to components of the device may require a re-certification. + +Table 10-7 also references the guidelines (clause numbers) that are applicable for each of the Certified Capability Classes on the service as well as the client side. + +**Table 10-7 – ZigBee Certified Capability Classes** + +| Certified Capability Class | Relevant guidelines | +|-----------------------------------------------------------------------------------|---------------------| +| ZigBee Activity Hub service, ZigBee Activity Hub client | 6.2, 6.3.14, 10.2 | +| ZigBee Adherence Monitor service, ZigBee Adherence Monitor client | 6.2, 6.3.29, 10.2 | +| ZigBee Basic 1-3 Lead ECG service, ZigBee Basic 1-3 Lead ECG client | 6.2, 6.3.2, 10.2 | +| ZigBee Blood Pressure Monitor service, ZigBee Blood Pressure Monitor client | 6.2, 6.3.4, 10.2 | +| ZigBee Body Composition Analyser service, ZigBee Body Composition Analyser client | 6.2, 6.3.9, 10.2 | + +**Table 10-7 – ZigBee Certified Capability Classes** + +| Certified Capability Class | Relevant guidelines | +|------------------------------------------------------------------------------------------|----------------------------| +| ZigBee Cardiovascular Fitness service,
    ZigBee Cardiovascular Fitness client | 6.2, 6.3.11, 10.2 | +| ZigBee Cardiovascular Step Counter service,
    ZigBee Cardiovascular Step Counter client | 6.2, 6.3.12, 10.2 | +| ZigBee CO Sensor service,
    ZigBee CO Sensor client | 6.2, 6.3.27, 10.2 | +| ZigBee Contact Closure Sensor service,
    ZigBee Contact Closure Sensor client | 6.2, 6.3.18, 10.2 | +| ZigBee Continuous Glucose Monitor service,
    ZigBee Continuous Glucose Monitor client | 6.2, 6.3.31, 10.2 | +| ZigBee Dosage Sensor service,
    ZigBee Dosage Sensor client | 6.2, 6.3.20, 10.2 | +| ZigBee Enuresis Sensor service,
    ZigBee Enuresis Sensor client | 6.2, 6.3.17, 10.2 | +| ZigBee Fall Sensor service,
    ZigBee Fall Sensor client | 6.2, 6.3.15, 10.2 | +| ZigBee Gas Sensor service,
    ZigBee Gas Sensor client | 6.2, 6.3.28, 10.2 | +| ZigBee Glucose Meter service,
    ZigBee Glucose Meter client | 6.2, 6.3.7, 10.2 | +| ZigBee Heart-rate Sensor service,
    ZigBee Heart-rate Sensor client | 6.2, 6.3.3, 10.2 | +| ZigBee INR Meter service,
    ZigBee INR Meter client | 6.2, 6.3.8, 10.2 | +| ZigBee Insulin Pump service
    ZigBee Insulin Pump client | 6.2, 6.3.32, 10.2 | +| ZigBee Motion Sensor service,
    ZigBee Motion Sensor client | 6.2, 6.3.16, 10.2 | +| ZigBee Pulse Oximeter service,
    ZigBee Pulse Oximeter client | 6.2, 6.3.1, 10.2 | +| ZigBee Peak Flow Monitor service,
    ZigBee Peak Flow Monitor client | 6.2, 6.3.10, 10.2 | +| ZigBee PERS Sensor service,
    ZigBee PERS Sensor client | 6.2, 6.3.26, 10.2 | +| ZigBee Power Status Monitor service
    ZigBee Power Status Monitor client | 6.2, 6.3.33, 10.2 | +| ZigBee Property Exit Sensor service,
    ZigBee Property Exit Sensor client | 6.2, 6.3.23, 10.2 | +| ZigBee Smoke Sensor service,
    ZigBee Smoke Sensor client | 6.2, 6.3.22, 10.2 | +| ZigBee Strength Fitness service,
    ZigBee Strength Fitness client | 6.2, 6.3.13, 10.2 | +| ZigBee Switch Sensor service,
    ZigBee Switch Sensor client | 6.2, 6.3.19, 10.2 | + +**Table 10-7 – ZigBee Certified Capability Classes** + +| Certified Capability Class | Relevant guidelines | +|------------------------------------------------------------------------|----------------------------| +| ZigBee Temperature Sensor service,
    ZigBee Temperature Sensor client | 6.2, 6.3.24, 10.2 | +| ZigBee Thermometer service,
    ZigBee Thermometer client | 6.2, 6.3.5, 10.2 | +| ZigBee Usage Sensor service,
    ZigBee Usage Sensor client | 6.2, 6.3.25, 10.2 | +| ZigBee Water Sensor service,
    ZigBee Water Sensor client | 6.2, 6.3.21, 10.2 | +| ZigBee Weighing scales service,
    ZigBee Weighing scales client | 6.2, 6.3.6, 10.2 | + +## **11 Bluetooth low energy (LE) design guidelines** + +### **11.1 Architecture of Bluetooth LE (informative)** + +#### **11.1.1 Introduction** + +This clause lists the design guidelines specific for interoperability between Continua Certified PHDs and PHGs using Bluetooth Low Energy across the Personal Health Devices interface. Figure 11-1 illustrates the Bluetooth Low Energy interface (BLE-IF) in the context of the Continua E2E architecture. The BLE-IF is a particular sub-class of the Continua PHD-IFs and connects Bluetooth Low Energy PHDs to PHGs across all three Continua domains, disease management, ageing independently, and health and fitness. + +![Diagram illustrating the Bluetooth LE interface within the Continua Health Alliance architecture. The diagram shows the flow of data from various Personal Health Devices (X73 and Bluetooth LE) through a Personal Health Gateway (PHG) to a Health & Fitness Service, and finally to a Healthcare Information System (HIS). The Bluetooth LE interface is highlighted with a red circle.](9c80cf99954eb0142f694456d39fae4b_img.jpg) + +The diagram illustrates the Continua Health Alliance architecture, showing the flow of data from various Personal Health Devices (PHDs) through a Personal Health Gateway (PHG) to a Health & Fitness Service, and finally to a Healthcare Information System (HIS). + +**Components and Interfaces:** + +- Personal Health Devices (PHDs):** + - X73 Device:** Includes icons for a keyboard, mouse, and other sensors. + - Bluetooth LE Device:** Includes icons for a heart rate monitor and other sensors. +- Personal Health Devices Interface (PHD-IF):** + - X73-IF:** Supported by IEEE, ISO, NFC Forum, ZigBee, Bluetooth, and USB. + - BLE-IF:** Supported by Bluetooth. This interface is highlighted with a red circle. +- Personal Health Gateway (PHG):** Represented by icons of a smartphone, tablet, and laptop. +- Services Interface:** Supported by HL7, IHE, OASIS, IETF, and W3C. +- HIS Interface:** Supported by HL7, IHE, OASIS, IETF, and W3C. +- Health & Fitness Service:** Represented by a cloud icon with a smartphone. +- Healthcare Information System (HIS):** Represented by icons of a hospital building, medical tests, and a doctor. + +**Data Flow:** + +- PHDs connect to the PHG via the PHD-IF. +- The PHG connects to the Health & Fitness Service via the Services Interface. +- The Health & Fitness Service connects to the HIS via the HIS Interface. + +Diagram illustrating the Bluetooth LE interface within the Continua Health Alliance architecture. The diagram shows the flow of data from various Personal Health Devices (X73 and Bluetooth LE) through a Personal Health Gateway (PHG) to a Health & Fitness Service, and finally to a Healthcare Information System (HIS). The Bluetooth LE interface is highlighted with a red circle. + +Figure 11-1 – Bluetooth LE interface + +### 11.1.2 Overview + +The Bluetooth Low Energy protocol is also a Continua-supported transport technology for the PHD-IF as a widely supported low-energy, low-bandwidth, limited range wireless protocol. The Bluetooth Special Interest Group (SIG) has defined device specific profiles and services on top of the Bluetooth low energy attribute profile that are supported by the PHD-IF. This is illustrated in Figure 11-2. + +![Figure 11-2 – Bluetooth LE interface stack. The diagram shows a stack of layers for a Bluetooth LE device. On the left, a vertical stack of three boxes: the top box is 'Bluetooth LE device profiles' containing a list of seven profiles (Blood pressure, Continuous glucose monitor, Glucose meter, Heart rate, Pulse oximeter, Thermometer, Weight scale); the middle box is 'Bluetooth LE attribute profile'; and the bottom box is 'Bluetooth LE'. To the right of this stack are three corresponding layers: 'BLE application protocol (ISO layer 6, 7)' at the top, 'Transport specific adaptation layer (ISO layer 5)' in the middle, and 'Base transport protocol (ISO layer 4)' at the bottom. The label 'H.811(16)_F11-1' is at the bottom right.](7b7596fb5ef925025341a9aacb6f2be7_img.jpg) + +Figure 11-2 – Bluetooth LE interface stack. The diagram shows a stack of layers for a Bluetooth LE device. On the left, a vertical stack of three boxes: the top box is 'Bluetooth LE device profiles' containing a list of seven profiles (Blood pressure, Continuous glucose monitor, Glucose meter, Heart rate, Pulse oximeter, Thermometer, Weight scale); the middle box is 'Bluetooth LE attribute profile'; and the bottom box is 'Bluetooth LE'. To the right of this stack are three corresponding layers: 'BLE application protocol (ISO layer 6, 7)' at the top, 'Transport specific adaptation layer (ISO layer 5)' in the middle, and 'Base transport protocol (ISO layer 4)' at the bottom. The label 'H.811(16)\_F11-1' is at the bottom right. + +**Figure 11-2 – Bluetooth LE interface stack** + +The Bluetooth LE interface does not utilize the IEEE 11073-20601 protocol for data exchange. The Bluetooth LE interface utilizes the Bluetooth LE protocol with data types compatible to the IEEE 11073-10101 nomenclature and the IEEE 11073-20601 domain information model. For the characteristics defined in the Bluetooth low energy profiles, the *Personal Health Devices Transcoding White Paper* describes how to transcode into an equivalent IEEE DIM and/or nomenclature representation. At a minimum, this covers the mandatory attributes from the supported [ISO/IEEE 11073-104xx] device specializations. + +The following Bluetooth LE device-specific specifications from the Bluetooth SIG apply to the Bluetooth LE interface. + +- Blood pressure profile and Blood pressure service (e.g., blood pressure measurement, intermediate cuff pressure) +- Continuous glucose monitor profile and Continuous glucose monitor service (e.g., glucose measurements) +- Current time service (e.g., local time) +- Device information service (e.g. manufacturer name, model number, serial number, hardware revision, firmware revision, software revision, system ID) +- Glucose profile and Glucose service (e.g., glucose measurement) +- Health thermometer profile and Health thermometer service (e.g., temperature) +- Heart rate profile and Heart rate service (e.g., heart rate, R-R interval) +- *Personal Health Devices Transcoding White Paper* describes how to transcode Bluetooth low energy data structures and format into an equivalent IEEE 11073 PHD data representation regarding DIM and/or nomenclature +- Pulse oximeter profile and Pulse oximeter service (e.g., SpO2 measurement) +- Weight scale profile, Weight scale service and Body composition service (e.g., weight measurement, BMI, body fat mass percentage). + +## 11.2 Bluetooth LE interface guidelines + +### 11.2.1 Bluetooth LE services and profiles + +Bluetooth LE technology has been selected as the low-power (LP) wireless technology. The specifications relating to Bluetooth LE are in version 4.0 (or later) of the core Bluetooth specification [Bluetooth CS4.0]. Any related profile specifications are detailed in separate documents. Bluetooth PHDs and PHGs that support Bluetooth LE can be either a dual mode device, which is a device that supports both standard BR/EDR Bluetooth and Bluetooth LE, or a single mode device, which is a device that supports Bluetooth LE only. It is envisioned that service components (PHDs) supporting Bluetooth LE will mostly be single mode devices. Table 11-1 shows the guideline for Bluetooth LE transport. + +**Table 11-1 – Bluetooth LE transport** + +| Name | Description | Comments | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| Bluetooth-LE-Map-minimum | Continua Bluetooth LE service and client components shall implement Bluetooth LE as described in Bluetooth Specification Version 4.0 [Bluetooth CS4.0] or a later version as long as compatibility with Version 4.0 is maintained, and subject to the design guidelines described in the sub-clauses below. | | +| Bluetooth-LE-Map-recommended | Continua Bluetooth LE service and client components should implement Bluetooth LE as described in Bluetooth Specification Version 4.2 [Bluetooth CS4.2], subject to the design guidelines described in the sub-clauses below. | Version 4.2 comes with improved security (LE Secure Connections) making Bluetooth LE as secure as Bluetooth BR/EDR. | + +### 11.2.2 Device discovery, connection establishment, pairing, service discovery and bonding + +Continua Bluetooth LE service devices (PHDs) transfer measurement data to client devices (PHGs). Continua Bluetooth LE client and service components are required to pair with each other, either following a search initiated by the client component that obtains a list of compatible devices or through an out-of-band configuration. + +Bluetooth LE pairing is the process to establish a secure connection. Bonding is the process to store the security keys on both sides to speed up the reconnection process. Pairing can be done without bonding, but bonding cannot be done without previous pairing. Although end-users may be unaware of the difference and often consider pairing and bonding to be the same, these guidelines distinguish between pairing and bonding and follow the definitions of [Bluetooth CS4.0]. + +Continua Bluetooth LE client and service components are not required to support bonding. + +A process of discovery of the service component by the client component is required for all Continua Bluetooth LE devices. This ensures a consistent and user-friendly pairing and bonding procedure. + +The guidelines throughout this clause and contained in Table 11-2, create a single and universally supported technique for pairing devices that give a minimum of surprise or inconvenience to users and implementers. + +**Table 11-2 – Bluetooth LE device discovery, pairing and service discovery** + +| Name | Description | Comments | +|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-LE-Pairing-Start-Client | Once a Continua Bluetooth LE client component has discovered a Continua Bluetooth LE service component that supports a compatible service, it shall support pairing with that Continua Bluetooth LE service component. | | +| Bluetooth-LE-Enter-Discoverability-Service | A Continua Bluetooth LE service component shall have a documented way to be set to be discoverable and a documented way to pair with a Continua Bluetooth LE client component. | | +| Bluetooth-LE-Enter-Advertise-Service | When discoverable, a Continua Bluetooth LE service component shall advertise at least the UUIDs of the service(s) the service component for which it is certified. | This allows client components to initiate pairing with just the service components with which they can and want to work. | +| Bluetooth-LE-Initiate-Discovery-Pairing-Client | A Continua Bluetooth LE client component shall have a documented way to initiate a search for discoverable Continua Bluetooth LE service component and a documented way of initiating pairing with a Continua Bluetooth LE service component. | | +| Bluetooth-LE-Discoverability-Mode-Service | A Continua Bluetooth LE service component shall not be discoverable unless initiated by a user. | | +| Bluetooth-LE-Discoverable-Mode-Bits-Service | A Continua Bluetooth LE service component shall set the General Discoverable Mode bit or the Limited Discoverable Mode bit when in Discoverable Mode. The bit should be chosen as appropriate for the usage of the device. | See [Bluetooth CS4.0] or later for implementation details on the General and Limited Discoverable Mode bits.
    Limited discoverability may be most appropriate for devices for personal usage such as most medical measurement devices. General discoverability may be most appropriate for devices for public usage, such as gym and fitness equipment. | +| Bluetooth-LE-Discoverable-Mode-Client | A Continua Bluetooth LE client component shall only attempt to connect to a service component advertising in General or Limited Discoverable Modes if the client component is intending to pair with | This will improve pairing operation by eliminating client components not intending to pair from interfering with other client components intending to | + +**Table 11-2 – Bluetooth LE device discovery, pairing and service discovery** + +| Name | Description | Comments | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | this service component. | pair with a service component in Discoverable Mode. | +| Bluetooth-LE-Delete-Pairing-Service | A Continua Bluetooth LE service component should have a way to delete stored pairings (bonds). | Note that on commercial platforms this may be called "pairing" or "paired devices" in the user interface. | +| Bluetooth-LE-Delete-Pairing-Client | A Continua Bluetooth LE client component should have a way to delete stored pairings (bonds). | | +| Bluetooth-LE-Additional-Pairing-Service | A Continua Bluetooth LE service component shall support replacing its stored pairing (bonds). | Bonding is not exclusive for the lifetime of the service component to enhance interoperability.
    Note also that simple devices may not have a UI that supports deleting of bonds, but also such devices must allow replacing bonds. | +| Bluetooth-LE-No-Data-Exchange-Before-Pairing-Service | Continua Bluetooth LE service component data (other than service discovery and related data or capability or service name from the advertising packet) shall not be exchanged with a Continua Bluetooth LE client component prior to pairing with that client component. | The Bluetooth Device Information Service [Bluetooth DIS] characteristics may be read without pairing and are considered to be part of the service discovery related data. | +| Bluetooth-LE-Disc-Mode-Max-Duration-Service | A Continua Bluetooth LE service component intended for personal use should have a documented maximum duration for discoverable mode whereby after the maximum time, the Continua Bluetooth LE service component ceases to be discoverable until put back into that mode by the user. | This guideline implies that the use of "Limited Discoverable Mode" is the recommended option for personal use devices. | +| Bluetooth-LE-After-Pairing-Undiscoverable-Service | After a Continua Bluetooth LE service component is successfully paired, it shall immediately (e.g., within 1 second) become undiscoverable until made discoverable again by the user. | | +| Bluetooth-LE-Bonding-Service | Continua Bluetooth LE service components should bond (i.e., store the pairing data) with at least the most recently paired device such that the data is persistent (e.g., with loss of power, including removal of a battery). | | +| Bluetooth-LE-Bonding-Client | Continua Bluetooth LE client | | + +**Table 11-2 – Bluetooth LE device discovery, pairing and service discovery** + +| Name | Description | Comments | +|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | components should bond (i.e., store pairing data) with at least the most recently bonded device such that the data is persistent (e.g., with loss of power including removal of a battery). | | +| Bluetooth-LE-Number-of-Bonds-Client | Continua Bluetooth LE client components should bond (store pairing data) with at least the number of devices they are intended to simultaneously support. | | +| Bluetooth-LE-Supported-Services-Service | Continua Bluetooth LE service component's Attribute database shall list all supported Bluetooth LE services claimed in Continua certification documentation. | | +| Bluetooth-LE-Stay-Connected-Period-Service |

    When connected, a Continua Bluetooth LE service component should stay connected for a period of at least 5 seconds when being idle.

    This period is not applicable if the client explicitly wants to terminate the connection for a good reason.

    "Idle" means not receiving any GATT messages from the connected client.

    "Staying connected" means NOT executing the GAP Terminate Connection Procedure or an equivalent GATT service procedure resulting in a disconnect.

    |

    This time-out period before disconnecting allows connected client components to discover service component services and characteristics, configure characteristics for indications/notifications; it also allows them to read the current time from the device and/or to start the pairing/bonding process.

    A good reason for a service component to disconnect is for example avoiding of interference with the execution of a higher priority task such as taking a measurement or interacting with the user.

    This period applies when the service component has just completed sending all (stored) measurements via indications or notifications to the client component.

    This period also applies when the service component has sent a recoverable error message to the client such as a security error message ("Insufficient Authentication", "Insufficient Authorization" or "Insufficient Encryption Key Size") or a service

    | + +**Table 11-2 – Bluetooth LE device discovery, pairing and service discovery** + +| Name | Description | Comments | +|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | |

    discovery error message in response to a GATT service request. See [BT CS 4.0] volume 3, part F and G, Security Considerations.

    A client component is expected not to misuse this time-out to stay connected without useful data exchange.

    | +| Bluetooth-LE-Stay-Connected-Period-Client |

    When connected, a Continua Bluetooth LE client component should stay connected for a period of at least 5 seconds when being idle.

    This period is not applicable if the service explicitly wants to terminate the connection for a good reason, e.g., by using the GAP Terminate Connection Procedure or an equivalent GATT service procedure resulting in a disconnect.

    "Idle" and "Staying connected" are defined as in the Bluetooth-LE-Pairing-Stay-Connected-Period-Service guideline above.

    |

    An example of data that the service may want to collect from the client in this period is the name of the client device. Note that Device Name support is mandatory for LE Peripheral and Central roles. See [Bluetooth CS4.2] Part C, Section 12.

    A good reason for a client component to disconnect is for example avoiding of interference with the execution of a higher priority task such as interacting with the user.

    | +| Bluetooth-LE-Service-Changed-Service |

    A Continua Bluetooth LE service component supporting the Service Changed characteristic shall send indications of this characteristic, when appropriate, after reconnecting with a trusted (bonded) client component before sending any other indications or notifications to this client component.

    |

    The Service Changed characteristic must be supported on Bluetooth service components for which the service definitions as exposed by service discovery can change. When the service definition changes and a client that enabled Service Changed indications earlier reconnects, an indication must be given to trigger service discovery of these changes in order to avoid using e.g., incorrect handles.

    The Bluetooth Core Specification does specify when the Service Changed indications will be sent, but does not clearly specify the timing of this behaviour, which is needed to be able

    | + +**Table 11-2 – Bluetooth LE device discovery, pairing and service discovery** + +| Name | Description | Comments | +|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| | | to understand indications properly. | +| Bluetooth-LE-Service-Changed-Client | A Continua Bluetooth LE client component shall enable indications on the Service Changed characteristic when supported by a Bluetooth service component to which this client is bonded before enabling any other indications or notifications on the service component. | Just to be safe, this is required to be done before enabling other indications or notifications. | + +### 11.2.3 User notification + +Establishing a new pairing relationship is an important event. Because of the potential for confusion, extreme care should be used before automating the pairing and bonding procedures. To allow users reasonable control of their Continua systems, PHGs are required to provide a facility for alerting users of significant events. Because discovery may be difficult for users to understand, it is important to inform them of new pairings, bondings and reasons for failure. The guidelines in this clause and contained in Table 11-3, intentionally leave the nature of notifying and informing the user to be defined by the manufacturer. + +**Table 11-3 – Bluetooth LE user notification** + +| Name | Description | Comments | +|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-LE-Inform-Pairing-Success-Service | If supported by the UI, Continua Bluetooth LE service components should inform the user that pairing and authentication were successful. | | +| Bluetooth-LE-Inform-Pairing-Success-Client | If supported by the UI, Continua Bluetooth LE client components shall inform the user that pairing and authentication were successful. | | +| Bluetooth-LE-Filter-Compatible-Client | Continua Bluetooth LE client components in a mode of device discovery should filter discovered Continua Bluetooth LE service components to include only those that have compatible services. | | +| Bluetooth-LE-Inform-User-Pairing-Failure-Client | If there is a failure during the discovery, pairing and authentication process, and if supported by the UI, the Continua Bluetooth LE client component shall inform the user whether the failure is because 1) no compatible Continua Bluetooth LE service components was found (compatible device not found) or 2) the pairing failed (pairing failure) or 3) the authentication process timed out (authentication time-out) or 4) the user entered the incorrect passkey (incorrect PIN). | | + +## 11.2.4 Security, authentication and privacy + +In Bluetooth LE profiles referenced in these guidelines, the service component chooses the mode of security it desires and the client component is required to accept this. Bluetooth LE profiles can mandate Just Works authentication, Passkey Entry of a six-digit PIN, Numeric Comparison or an out-of-band obtained passkey. While in Bluetooth Low Energy there are various authentication options, Continua places more requirements on security, authentication and privacy features to ensure interoperability. Table 11-4 contains guidelines on Bluetooth LE authentication and a high level of security. + +**Table 11-4 – Bluetooth LE authentication** + +| Name | Description | Comments | +|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-LE-Authentication-Support-Service | Continua Bluetooth LE service components shall support at least one of the following Bluetooth 4.0 pairing methods (association models) depending on its I/O capabilities and the appropriate security for the service component device type: Just Works or Passkey Entry. | I/O capabilities include display, keyboard, yes/no. See Bluetooth Core Specification 4.0 [Bluetooth CS4.0] for further information. The association models from Bluetooth LE in CS 4.0 are called "LE Legacy Pairing" in CS 4.2 [Bluetooth CS4.2]. | +| Bluetooth-LE-Authentication-Support-Client | Continua Bluetooth LE client components shall support Just Works and Passkey Entry pairing methods (association models) for Bluetooth 4.0 if the client component has the appropriate I/O capabilities. | I/O capabilities include display, keyboard, yes/no. See Bluetooth Core Specification 4.0 [Bluetooth CS4.0] for further information. This guideline is necessary to ensure interoperability and give reasonable assurance that a service component's chosen pairing method (association model) will be supported by client components. | +| Bluetooth-LE-Secure-Connections | Continua Bluetooth LE client and service components shall support LE Secure Connections if they support Bluetooth 4.2 [Bluetooth CS4.2] or later. | "LE Secure Connections" are defined in CS4.2. With LE Secure Connections the key generation scheme is made more robust and equivalent to that of Bluetooth BR/EDR. | +| Bluetooth-LE-Authentication-Support-Service-v42 | Continua Bluetooth LE service components supporting Bluetooth 4.2 [Bluetooth CS4.2] or later shall support at least one of the following Bluetooth 4.2 association models depending on its I/O capabilities and the appropriate security for the service component device type: Just Works, Passkey Entry or Numeric Comparison. | I/O capabilities include display, keyboard, yes/no. See Bluetooth Core Specification 4.2 [Bluetooth CS4.2] for further information. These association models are the successors of the "legacy" models from older versions of the CS. | + +**Table 11-4 – Bluetooth LE authentication** + +| Name | Description | Comments | +|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-LE-Authentication-Support-Client-v42 | Continua Bluetooth LE client components shall support Just Works, Passkey Entry and Numeric Comparison association models if supporting Bluetooth 4.2 [Bluetooth CS4.2] or later and if the client component has the appropriate I/O capabilities. | This pairing guideline is necessary to ensure interoperability and give reasonable assurance that a service component's chosen association model will be supported by client components. | +| Bluetooth-LE-Link-Layer- Privacy- Recommended-Service | Continua Bluetooth LE service components that are implemented in devices that support BT v4.2 or later and that may reveal information on the use of a device, such as the location of the user by regular advertising, should implement the Link Layer Privacy as defined by [BT CS v4.2] Volume 6, part B, section 6. | Link Layer Privacy prevents a user being tracked by changing the MAC address used by a Bluetooth LE device randomly, while maintaining the capability to pair and bond with known devices.
    For a device like a fitness machine shared by multiple users, this may not be a useful feature. | +| Bluetooth-LE-Link-Layer- Privacy- Recommended-Client | Continua Bluetooth LE client components that are implemented in devices that support BT v4.2 or later and that may reveal information on the use of a device, such as the location of the user by regular advertising, should implement the Link Layer Privacy as defined by [BT CS v4.2] Volume 6, part B, section 6. | Similar to the service component, a Bluetooth LE client component could reveal information that should stay private. This can be avoided using Link Layer Privacy. Recent smart phones models typically implement this feature out of the box. | +| Bluetooth-LE-Link-Layer- Privacy- Required-Service | Continua Bluetooth LE service components that support BT v4.2 or later shall be able to connect to client components using the Link Layer Privacy as defined by [BT CS v4.2] Volume 6, part B, and section 6. | For service components to work with client components using Link Layer Privacy means that they shall support decoding randomly generated resolvable private addresses in connection and scan requests. | +| Bluetooth-LE-Link-Layer- Privacy- Required-Client | Continua Bluetooth LE client components that support BT v4.2 or later shall be able to connect to service components using the Link Layer Privacy as defined by [BT CS v4.2] Volume 6, part B, section 6. | For client components to work with service components using Link Layer Privacy means that they shall support decoding randomly generated resolvable private addresses in advertisements. | + +**Table 11-4 – Bluetooth LE authentication** + +| Name | Description | Comments | +|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| Bluetooth-LE-Link-Layer- Privacy-Restricted-Advertising-Service | Continua Bluetooth LE service components using Link Layer Privacy should not include any device-traceable information in the advertising data or in the scan response data. | Examples of such data would be the device name, or a device specific service UUID. | + +**11.2.5 Device information requirements** + +Bluetooth LE profiles referenced in these guidelines define some characteristics within the Bluetooth SIG device information service as optional. This clause describes the guidelines that are targeted at the Device Information characteristics, see Table 11-5. All of the fields defined in this clause are from the Bluetooth SIG device information service. + +**Table 11-5 – Bluetooth LE OEM requirements** + +| Name | Description | Comments | +|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-LE-11073-20601-Manufacturer | Continua Bluetooth LE service components shall support and set the manufacturer name string defined in the Bluetooth SIG device information service to the device's original manufacturer's name. If this capability is available, the manufacturer name string may be overwritten to the customer facing company's name by the customer facing company. | | +| Bluetooth-LE-11073-20601-Model | Continua Bluetooth LE service components shall set the model number string defined in the Bluetooth SIG device information service to the device's original manufacturer's model number. The model number string field may be overwritten to the customer facing company's model by the customer facing company. | | +| Bluetooth-LE-11073-20601-SYSID | Continua Bluetooth LE service components shall include the System ID characteristic defined in the Bluetooth SIG device information service. | | +| Bluetooth-LE-11073-20601-OUI | The organizationally unique identifier (OUI) field of the System ID characteristic defined in the Bluetooth SIG device information service in a Continua Bluetooth LE service component shall be set and remain unchanged from the value set by the original manufacturer. | This is a unique identifier, which is obtained by the IEEE registration authority and which is associated with a company. This attribute maps to the OUI part (first 24 bits) of the EUI-64 attribute | + +**Table 11-5 – Bluetooth LE OEM requirements** + +| Name | Description | Comments | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-LE-11073-20601-DID | The 40 bit manufacturer defined identifier field in the System ID characteristic defined in the Bluetooth SIG device information service of a Continua Bluetooth LE service component shall be set and remain unchanged from the value set by the original manufacturer. | In combination with the OUI part above, this is a unique identifier associated with the device. It is required in order to facilitate data quality analysis. This attribute maps to the company defined part (last 40 bits) of the EUI-64 attribute | +| Bluetooth-LE-11073-20601-Serial-Number | Continua Bluetooth LE service components shall set the serial number string characteristic defined in the Bluetooth SIG device information service to the serial number of the device. | | +| Bluetooth-LE-11073-20601-FW-Revision | Continua Bluetooth LE service components that provide a firmware identifier shall set the firmware revision string characteristic defined in the Bluetooth SIG device information service to the firmware identifier of the device. | The firmware identifier is the version of the firmware deployed on the PAN device. The firmware release deployed on a PAN device is uniquely identified by the firmware identifier | + +### 11.2.6 Date and time requirements + +Bluetooth LE devices which report time-stamped measurements must provide the means to report the current date and time of the device. The following guidelines are intended to provide the means for this support. Table 11-6 covers Bluetooth LE date and time requirements. + +**Table 11-6 –Bluetooth LE date and time requirements** + +| Name | Description | Comments | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-LE-Date-Time | Continua Bluetooth LE service components that report time-stamped measurements shall support the Current Time Service [Bluetooth CTS] or shall include the "Date Time" characteristic in the service component for the purpose of reporting the current date and time of the service component. | Transcoding of time specified in the Personal Health Devices Transcoding White Paper from the Bluetooth SIG [Bluetooth PHDT v1.5] (or later). Newer versions of this whitepaper require support of CTS by the service component when reporting time-stamped measurements. For newer designs the use of CTS is the preferred choice.
    Continua still allows use of the Date-Time characteristic for legacy devices that report time-stamped measurements as described in [Bluetooth PHDT V1.4]. | + +### 11.2.7 Certification and regulatory aspects + +Since Bluetooth LE profiles referenced in these guidelines define as optional the IEEE 11073-20601 Regulatory Certification Data List characteristic within the Bluetooth SIG device + +information service, this clause describes the guidelines that are targeted at certification and regulatory aspects including those specific to this characteristic. + +For this purpose, the ASN-1 definitions from Figure 6-3 are referenced in Table 11-7. + +**Table 11-7 – Bluetooth LE certification and regulation** + +| Name | Description | Comments | +|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-LE-Support-Reg-Cert-Data-Service | Continua Bluetooth LE service components shall support and fill the IEEE 11073-20601 Regulatory Certification Data List characteristic defined in the Bluetooth SIG device information service with an MDER encoded version of the IEEE 11073-20601 RegCertDataList data structure. The RegCertDataList data structure shall contain a RegCertData element with the auth-body-continua and the auth-body-struc-type field set to continua-version-struct from a ContinuaStructType as defined above. The field auth-body-data shall be filled in as a ContinuaBodyStruct as defined in Figure 11-2 | This is used to indicate whether a device is Continua certified and (if so) to which version of the Continua Design Guidelines it is certified. | +| Bluetooth-LE-CapabilityList | Continua Bluetooth LE service components shall list all implemented and only the implemented Certified Capability Classes in the IEEE 11073-20601 Regulatory Certification Data List characteristic within the Bluetooth SIG device information service. | | +| Bluetooth-LE-CapabilityEntry | Continua Bluetooth LE service components shall assign the following certified Capability Class field value within the IEEE 11073-20601 Regulatory Certification Data List characteristic within the Bluetooth SIG device information service to an implemented Certified Capability Class:
    MDC_DEV_*_SPEC_PROFILE_* - 4096 + TCode x 8192, where MDC_DEV_*_SPEC_PROFILE_* denotes the IEEE 11073 PHD nomenclature code for the corresponding device (sub-) specialization, and TCode denotes the corresponding transport standard, with TCode = {4 for LP wireless PAN} | See [Bluetooth PHDT 1.5] (or later) | +| Bluetooth-LE-Report-Regulated-Service | All Continua BLE service components shall report information on whether or not they are regulated. This is a single Boolean entitled unregulated-device, which is set to 1 if not regulated and 0 if regulated and contained as part of IEEE 11073-20601 Regulatory Certification Data List defined in the Bluetooth SIG device information service. | | + +## 11.2.8 Transcoding + +Bluetooth LE profiles referenced in these guidelines are designed to be compatible with the IEEE 11073 device information model (DIM) and nomenclature of a corresponding IEEE 11073-20601 device specialization. The Bluetooth SIG published document [Bluetooth PHDT v1.5] (or later) contains the information showing how the applicable Bluetooth LE characteristics can be mapped to the device information model (DIM) and nomenclature of the corresponding IEEE 11073-20601 + +device specializations. From a Bluetooth LE profile perspective this mapping information is included as informative text for profiles targeted for usage in the Continua context CDG. However, when Bluetooth LE profiles are used within the CDG and transcoding is required, this mapping information is normative for implementations that transcode Bluetooth LE data. Table 11-8 covers the guideline for Bluetooth LE transcoding. + +**Table 11-8 – Bluetooth LE transcoding** + +| Name | Description | Comments | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bluetooth-LE-Transcode |

    The guidelines for interfaces in the Continua E2E architecture assume that data coming from the X73 interface are IEEE 11073 nomenclature and DIM representations and then specify necessary data conversions for each of the interfaces. Any solution that interacts with the Bluetooth LE interface and passes the data over other Continua interfaces shall follow [Bluetooth PHDT 1.5] (or later) during the translation process from Bluetooth LE data to final representation for the supported interface(s). Transcoded data shall be compliant to the IEEE 11073 nomenclature and DIM corresponding specifically with [ISO/IEEE 11073-20601].

    |

    [Bluetooth PHDT v1.5] (or later) is informative from the Bluetooth SIG perspective, but is normative for the purposes of these guidelines. This white paper specifies how to convert the Bluetooth LE data into full IEEE 11073 compliant data, which then supports the use of the data for the Continua Services and HIS interfaces.

    Note that this guideline does not require a PHG to actually create the DIM, objects, and attributes indicated by the white paper. However, the data generated for transmission over the subsequent Continua interface must match the data that would have been generated from such a DIM

    | + +### 11.3 Bluetooth LE PHDs and PHGs + +#### 11.3.1 Blood pressure monitor + +Table 11-9 shows blood pressure general requirements for Bluetooth LE. + +**Table 11-9 – Blood pressure general requirements for Bluetooth LE** + +| Name | Description | Comments | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-LE-Blood Pressure-Service |

    Continua Bluetooth LE blood pressure service components shall implement the blood pressure sensor role as defined by the blood pressure profile and service – [Bluetooth BPP] and [Bluetooth BPS].

    | | +| Bluetooth-LE-Blood Pressure-Client |

    Continua Bluetooth LE blood pressure client components shall implement the collector role as defined by blood pressure profile from [Bluetooth BPP].

    | | + +### 11.3.2 Thermometer + +Table 11-10 shows thermometer general requirements for Bluetooth LE. + +**Table 11-10 – Thermometer general requirements for Bluetooth LE** + +| Name | Description | Comments | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-LE-Thermometer-Service | Continua Bluetooth LE thermometer service components shall implement the health thermometer sensor role as defined by the health thermometer profile and service – [Bluetooth HTP] and [Bluetooth HTS]. | | +| Bluetooth-LE-Thermometer-Client | Continua Bluetooth LE thermometer client components shall implement the collector role as defined by the health thermometer profile from [Bluetooth HTP]. | | + +### 11.3.3 Heart-rate sensor + +Table 11-11 shows heart-rate sensor general requirements for Bluetooth LE. + +**Table 11-11 – Heart-rate sensor general requirements for Bluetooth LE** + +| Name | Description | Comments | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-LE-Heart-rate-Sensor-Service | Continua Bluetooth LE heart-rate sensor service components shall implement the heart-rate sensor role as defined by the heart rate profile and service – [Bluetooth HRP] and [Bluetooth HRS]. | | +| Bluetooth-LE-Heart-Rate-Sensor-Client | Continua Bluetooth LE heart-rate client components shall implement the collector role as defined by the heart rate profile from [Bluetooth HRP]. | | + +### 11.3.4 Glucose meter + +Table 11-12 shows glucose meter general requirements for Bluetooth LE. + +**Table 11-12 – Glucose meter general requirements for Bluetooth LE** + +| Name | Description | Comments | +|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-LE-Glucose-Meter-Service | Continua Bluetooth LE glucose meter service components shall implement the glucose sensor role as defined by the glucose profile and service – [Bluetooth GLP] and [Bluetooth GLS]. | | +| Bluetooth-LE-Glucose-Meter-Client | Continua Bluetooth LE glucose meter client components shall implement the collector role as defined by the glucose meter profile from [Bluetooth GLP]. | | + +### 11.3.5 Weighing scale + +Table 11-13 shows weighing scale general requirements for Bluetooth LE. + +**Table 11-13 – Weighing scale general requirements for Bluetooth LE** + +| Name | Description | Comments | +|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-LE-Weight-Scale-Service | Continua Bluetooth LE weight scale meter service components shall implement the weight scale sensor role as defined by the weight scale profile and service from the Bluetooth SIG – [Bluetooth WSP] and [Bluetooth WSS]. | | +| Bluetooth-LE-Weight-Scale-Body-Composition-Service | Continua Bluetooth LE weight scale service components may implement the body composition service from the Bluetooth SIG [Bluetooth BCS]. | | +| Bluetooth-LE-Weight-Scale-Client | Continua Bluetooth LE weight scale client components shall implement the collector role as defined by the the weight scale profile from the Bluetooth SIG [Bluetooth WSP]. | | + +### 11.3.6 Continuous glucose monitor + +Table 11-14 shows continuous glucose monitor (CGM) general requirements for Bluetooth LE. + +**Table 11-14 – CGM general requirements for Bluetooth LE** + +| Name | Description | Comments | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-LE-CGM-Service | Continua Bluetooth LE CGM service components shall implement the CGM sensor role as defined by the CGM profile and service – [Bluetooth CGMP] and [Bluetooth CGMS]. | | +| Bluetooth-LE-CGM-Client | Continua Bluetooth LE CGM client components shall implement the collector role from the CGM profile from the Bluetooth SIG [Bluetooth CGMP]. | | + +### 11.3.7 Pulse oximeter + +Table 11-15 shows pulse oximeter general requirements for Bluetooth LE. + +**Table 11-15 – Pulse Oximeter general requirements for Bluetooth LE** + +| Name | Description | Comments | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bluetooth-LE-POX-Service | Continua Bluetooth LE pulse oximeter service components shall implement the pulse oximeter sensor role as defined by the pulse oximeter profile and service – [Bluetooth POXP] and [Bluetooth POXS]. | | +| Bluetooth-LE-POX-Client | Continua Bluetooth LE pulse oximeter client components shall implement the collector role from the pulse oximeter profile from the Bluetooth SIG [Bluetooth POXP]. | | + +## 11.4 Bluetooth LE Certified Capability Classes + +Table 11-16 shows the Certified Capability Classes defined for the Bluetooth LE interface design guidelines. A certification program run by Personal Connected Health Alliance exists for PHDs and PHGs that implement the CDG. For Bluetooth LE PHDs and PHGs, the certification testing will be performed on an integrated device, meaning the testing and certification is applied to the hardware and software of the device. Changes to components of the device may require a re-certification. Table 11-16 also references the guidelines that are applicable for each of the Certified Capability Classes. + +**Table 11-16 – Bluetooth LE Certified Capability Classes** + +| Certified Capability Classes | Relevant guidelines | +|---------------------------------------------------------------------------------------------------|---------------------| +| Bluetooth LE blood pressure monitor service
    Bluetooth LE blood pressure monitor client | 11.2, 11.3.1 | +| Bluetooth LE continuous glucose monitor service
    Bluetooth LE continuous glucose monitor client | 11.2, 11.3.6 | +| Bluetooth LE glucose meter service
    Bluetooth LE glucose meter client | 11.2, 11.3.4 | +| Bluetooth LE heart-rate sensor service
    Bluetooth LE heart-rate sensor client | 11.2, 11.3.3 | +| Bluetooth LE pulse oximeter service
    Bluetooth LE pulse oximeter client | 11.2, 11.3.7 | +| Bluetooth LE thermometer service
    Bluetooth LE thermometer client | 11.2, 11.3.2 | +| Bluetooth LE weighing scales service
    Bluetooth LE weighing scales client | 11.2, 11.3.5 | + +## Appendix I + +### Additional Bluetooth BR/EDR information + +(This appendix does not form an integral part of this Recommendation.) + +#### I.1 Bluetooth terminology + +**Bonding:** Storing a common link key to establish a future trust relationship with a known device. The link key is created and exchanged during pairing. + +**BR/EDR:** Abbreviation for Basic Rate/Enhanced Data Rate. BR/EDR is usually used as a way to describe "Classic" Bluetooth, as opposed to Bluetooth high speed or Bluetooth low energy. + +**Connectable:** A Bluetooth device is connectable if it is periodically entering the Page Scan substate. Page Scan requires an active receiver for about 11.25 ms (default) and can be entered continuously or periodically. Normal periods are in the one second range (modes R2 $\leq$ 2.56 s, R1 $\leq$ 1.28 s, R0 is continuous). If a device is connectable, it will respond to pages from devices that address it specifically (by Bluetooth MAC). + +**(Device) Discovery:** Using the Inquiry substate to learn of the existence of other Bluetooth devices within transmission range. May take up to thirty seconds. Sometimes called "device discovery" to distinguish from service discovery. + +**Discoverable:** A Bluetooth device is discoverable if it is periodically entering the Inquiry Scan substate. Inquiry Scan requires an active receiver for about 11.25 ms (default) and is entered at least once every 2.56 s. If a device is discoverable, it will respond to Inquiry procedures (usually a general Inquiry) from any device that wants to search. + +**Limited discoverable:** A Bluetooth term for devices that are discoverable only for a limited period of time, and otherwise not discoverable. Typically, user interaction triggers discoverability.. + +**Pairing:** Creating and exchanging link key(s) to establish a trust relationship with a known device. Performed with secure simple pairing (SSP), except in legacy cases. + +**Out-of-band connection:** A data link other than the Bluetooth connection. This may include Bluetooth near-field communication (NFC), patch cables, removable media, or any other mechanism for transferring data between the two devices. + +**Service discovery:** Creating a baseband connection to a specific device (may be paired, but does not need to be) to discover details about services offered on that device. + +See Bluetooth Core Specification 4.0 [Bluetooth CS4.0] or later for further definitions. + +#### I.2 Bluetooth BR/EDR pairing methods + +Starting with Bluetooth 2.1+EDR, pairing uses secure simple pairing (SSP) which (as the name implies) improved both the security and the simplicity of the Bluetooth pairing procedure. Older devices use a legacy pairing procedure. Both of these procedures result in a shared "link key" that is unique to the pair of devices and can be used both to authenticate future connections and to create session keys for encrypting traffic over the air. + +Whichever procedure is used, the user experience will depend heavily on how it is implemented. To produce an adequate level of trust between the two devices while also giving a good user experience, the following factors are particularly relevant: + +**Security against eavesdropping** refers to the required protection from listening devices that are present during the pairing procedure. Legacy pairing offers moderate protection only if long PINs + +are used (at least six digits), although attacks are still possible. SSP is always secure against eavesdropping. + +**Security against active man-in-the-middle (MITM)** refers to the required protection from a device that inserts itself between the two parties on the physical link, so instead of pairing with each other (as intended), they both pair with the attacker. The attacker may relay data as if the connection were working correctly, but would be able to intercept or even change that data during transmission. Legacy pairing is not secure against this type of attack. SSP may be secure against it. + +**Security against confusion** refers to the required protection against allowing a device to pair with a device other than the intended partner. + +For additional information on Bluetooth discovery and pairing, including device user interface input/output capabilities, see the following Bluetooth SIG documentation as formally referenced in clause 2 and the Bibliography of [ITU-T H.810]. + +- Bluetooth Core Specification, v2.1 or later, Vol. 3, Part C: Generic Access Profile [Bluetooth CS2.1] +- Bluetooth Discovery White Paper [b-Bluetooth Discovery] +- Bluetooth Secure Simple Pairing User Terminology White Paper [b-Bluetooth SSP UT] +- Bluetooth User Interface Flow Diagrams for Bluetooth Secure Simple Pairing Devices White Paper [b-Bluetooth SSP UI] +- Bluetooth Secure Simple Pairing Usability Metric White Paper [b-Bluetooth SSP UM] + +### I.3 Bluetooth BR/EDR legacy pairing procedures + +Legacy pairing requires keys from both devices. If a device has a user interface, a unique PIN can be entered. It is recommended that well-known values (like "0000") not be used for groups of devices, as this may cause erroneous pairings. PINs should be at least six digits long and selected in such a way that each individual PIN will be re-used only about once in 1 000 000 devices (or less). The PIN for each device should be clearly identified on the device packaging, although that identification may be made removable. + +### I.4 Supporting Bluetooth OEM subsystems and components + +The Bluetooth SIG currently allows the certification of "profile subsystems" devices that completely implement a profile, but are not themselves an "End Product". It is expected that some implementers will develop and market HDP modules that include the entire HDP implementation with the exception of the ISO/IEEE 11073-20601 data layer and ISO/IEEE 11073-104xx device specializations. Others may develop the ISO/IEEE 11073-20601 data layer and device specializations such that when the two implementations are combined, they form an End Product. The Bluetooth Qualification System allows for two partial implementations to be combined forming an "End Product" through the combination of appropriate subsystems or through the use of "subsetting". However, some testing of the combined implementations may be required. Refer to the Bluetooth SIG for further information regarding the Bluetooth qualification process. + +### I.5 Quality of service bins for Bluetooth + +For Bluetooth, the expected quality of service (QoS) for a data connection is identified through the use of the two recognized QoS bins (see clause 9.2.6). Achieving this QoS (knowing what is expected from a channel, policing what is being delivered and flagging exceptional situations) is the responsibility of both ends of the connection. + +In the case where a connection is point-to-point, this can often be delegated to the underlying transport layer implementation. For example, when a Bluetooth connection is established between + +two devices (by a successful pairing procedure), the link manager protocol can request the "supported features" of the partner device. These features would include information about which enhanced data rate modes are supported and therefore allow the local device (which already knows its own capabilities) to make a good guess at the throughput it can expect over that link. This is the recommended method for this version of the Continua Design Guidelines. + +When the data is routed via intermediate nodes, but the QoS is important from end-to-end, some higher-layer function is required to accumulate and correlate the QoS expected from the various components, or at least to assign expected bounds to each hop. This will require communication of QoS characteristics at the end-to-end (transport layer). This version of the CDG support, at maximum, two cascaded transport technologies: USB/Bluetooth and ZigBee. The overall end-to-end latency is statically managed by splitting the end-to-end transport latency budget between these two transports. + +See clause 6.1.7.2 in [ITU-T H.810] for a definition of the QoS bins supported by this version of the Continua Design Guidelines. + +The two channel types provided for in the Bluetooth HDP specification [Bluetooth HDPv1.1] are reliable and streaming. On the reliable channel, latency will be most sensitive to retransmission times. On the streaming channel (which never retransmits data), it will be most sensitive to buffer sizes and local latency. A 10% margin is reasonable to include when making latency calculations to account for the software latency for handling of messages. The latency expected on the streaming channel can be calculated from the poll interval taking software latency into consideration. + +The poll interval is the maximum number of slots that will normally be allowed to separate consecutive opportunities for a slave to begin a transmission. A slave may request a new poll interval from the master (by sending an LMP\_quality\_of\_service\_req packet) and will be informed of its value. However, the master sets that value. Legal values are any even number of slots in the range 6 through 4096 (3.75 ms - 2.56 s) and the default value is 40 (25 ms). + +The streaming channel may be configured to have a polling interval short enough that, when combined with the actual transmission duration, will provide "Low" latency. However, in some particular configurations this may not be possible. For example, if the device is itself a slave and connects to a master that does not support polling intervals other than the default, it may have the opportunity to start a new data packet only once every 25 ms. + +"Medium" or longer latency should always be possible (for reasonable packet sizes) on the streaming channel. + +Latency on the reliable data channel depends on retransmission. If an out-of-sequence packet is received, it will trigger retransmission of the intervening lost packets reasonably quickly. In the worst case, however, the last packet of the message may be lost (for example, if only one L2CAP packet were transmitted). In this case, retransmission would not occur until the retransmission timeout period had elapsed. This time is communicated in the option configuration information for L2CAP Enhanced Retransmission mode option and may be in the hundreds of milliseconds range. If the retransmit timer expires in the sending device and unacknowledged frames exist, they will be retransmitted. + +Over a normal connection, loss of the same packet twice should be unusual, so a reliable connection should be able to deliver an average latency in the "Medium" range, if its retransmission timeout is around 100 ms. Setting the MaxTransmit value to 2 would require the connection to be closed if the same packet were ever lost twice. However, very few scenarios would benefit from using this feature and MaxTransmit should usually be larger than 2. + +For reliability, the Bluetooth channel has a basic bit error rate of less than 0.1% and the data packets are protected with a 16-bit CRC. The SDU (recombined higher-layer data packet) is further + +protected by another 16-bit CRC (the FCS). This is true on both the reliable and streaming channels, so the probability of a bit-error in any packet should be less than $10^{-9}$ . + +The streaming channel may lose packets (particularly due to buffer overflows) but the reliable channel will not lose packets. + +Either channel may be broken due to range or extreme interference. Neither the Bluetooth health device profile, nor these guidelines currently require devices to seek a reconnection following an unintentional disconnect, although the possibility is provided for in the protocols. + +Before committing to an upper layer that any of these QoS bins is supported by a particular channel, an implementation shall check the relevant configuration parameters of the actual L2CAP channel (once it is established) to verify its commitment is supported. + +## Appendix II + +### Additional ZigBee information + +(This appendix does not form an integral part of this Recommendation.) + +#### II.1 ZigBee networking + +The 802.15.4/ZigBee network provides facilities for commissioning, data transfer and maintenance. Use of a certified ZigBee platform provides a robust self-healing mesh network. The ZigBee health care profile mandates use of the 11073 protocol tunnel and reuses components of the ZigBee cluster library. + +Commissioning details depend on the deployment scenario. Three deployment scenarios are addressed by this profile, as follows: + +1. Service provider scenario. In this scenario, a service provider that provides patient monitoring services is responsible for providing all the devices that are part of the network and preloading these devices with all the information that they need to securely join the network and work together. +2. In-house commissioning scenario. In this scenario, the network owner (e.g., a medical care facility) has its own in-house commissioning facility, to configure the devices with all the information that they need to securely join the network and work together. +3. Consumer scenario. This scenario covers the case of small networks, where the network owner does not have a service provider and wishes to purchase devices from multiple providers and install them himself. This case is typical of the home environment. + +For example, in the consumer scenario, a typical deployment may be as follows: + +1. The coordinator or router sends a command to the ZigBee network to allow joining of new device for a limited period. +2. A ZigBee healthcare device will first do a scan for networks and build a list of available networks that allow joining. +3. The ZigBee healthcare device will then pick a network and associate to the nearest node (router or coordinator) that allows joining and start the security authentication process. +4. The router/coordinator parent will now send an update-device (device joined) message to the ZigBee security trust centre in encrypted form. +5. The trust centre will now determine if it will allow the device in the network or not. +6. If the device is allowed in the network the trust centre will send the network security key to the device. Note this is done using a predefined link key. +7. The device is now an active participant in the network. + +#### II.2 ZigBee pairing process/service discovery types + +A ZigBee device consists of one or more ZigBee device descriptions (e.g., thermometer and pulse oximeter) and their corresponding application profile(s), optionally on a separate endpoint, that share a single physical IEEE802.15.4 radio. Each device has a unique 64-bit IEEE address and contains a collection of clusters and associated functionality implemented on a ZigBee endpoint. Device descriptions are defined in the scope of the ZigBee health care application profile. Each device description has a unique identifier that is exchanged as part of the discovery process. + +The ZigBee specification [ZigBee Spec] provides the facility for devices to find out information about other nodes in a network, such as their addresses, which types of applications are running on them, their power source and sleep behaviour. This information is stored in descriptors on each node and is used by the requesting node to tailor its behaviour to the requirements of the network. + +Discovery is typically used when a node is being introduced into a health care network. Once the device has joined the network, its integration into the network may require the user to start the integration process by pressing a button or similar, in order to discover other devices that it can talk to. For example, a device implementing a weigh scale conforming to the ZHC profile tries to find devices containing ZHC aggregation devices (similar to the Continua PHG) to which it could potentially send its measurement data. + +The ZigBee pairing process allows for fast and easy association between devices. There are a variety of routing algorithms for data packets to find the correct destination, including neighbour and table-based routing. These approaches result in a high degree of flexibility and stability ensuring that devices in the network stay connected and that network performance remains constant even as it is dynamically changing. ZigBee health care offers several way of "pairing" devices. + +- End device bind + - This is a simple push button pair when a button is pressed on 2 devices within a time window and if their services match a "binding" is created +- Service discovery + - A health care device can build a list of health care devices on the network, for example by listening for new devices to join the network, or by sending a service discovery broadcast to which matching device will respond. The device can now pick which device it would like to communicate with +- Commissioning tool + - Mandatory primitives in the ZigBee stack allow for a device to query other devices for their services and set up "bindings" and relationships between devices + +### II.3 ZigBee security + +ZigBee security [ZigBee HCP], which is based on a 128-bit advanced encryption standard (AES) algorithm, adds to the security model provided by [b-IEEE 802.15.4]. ZigBee's security services include methods for key establishment and transport, device management and frame protection. Security for health care applications is specified as part of the default ZigBee stack profiles, with support for a network key and link keys for point-to-point secure links. In a health care network, the aggregator device (often the Continua PHG) will contain a function called the trust centre. The trust centre decides whether to allow or disallow new devices into its network. The trust centre may periodically update and switch to a new network key and controls deployment of link keys. The trust centre is usually also the network coordinator. + +## Appendix III + +### Recommendation for use of generic USB drivers + +(This appendix does not form an integral part of this Recommendation.) + +It is recommended that managers for USB PHDC that provide a USB PHDC driver based on a generic USB driver use the following values in the setup information (INF) file: + +| Attribute | INF file element | WinUSB value | LibUSB value | +|-------------------|----------------------------------------|----------------------------------------|----------------------------------------| +| Device Class GUID | [Version]/ ClassGUID | {182A3B42-D570-4066-8D13-C72202B40D78} | {EB781AAF-9C70-4523-A5DF-642A87ECA567} | +| Device Class Text | [Version]/Class
    [Strings]/ClassName | PHDC | libusb-win32 devices | +| Interface GUID | [Dev_AddReg] | {B8B610DE-FB41-40A1-A4D6-AB28E87C5F08} | N/A | +| Device GUID | [Strings]/DeviceGUID | N/A | {D0C36FAA-CE6D-4887-A3AA-6FC42D3037E5} | + +For more information see [b-CHA USB-PHDC]. + +## **Bibliography** + +For a list of non-normative references and publications that contain further background information, see [ITU-T H.810]. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.812-201711-I_PDF-E/raw.md b/marked/H/T-REC-H.812-201711-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b7cce81ed9b4d2c89b28aef8c54f871c37bd66f7 --- /dev/null +++ b/marked/H/T-REC-H.812-201711-I_PDF-E/raw.md @@ -0,0 +1,1156 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.812** + +(11/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – Personal +health systems + +--- + +**Interoperability design guidelines for personal +connected health systems: +Services interface** + +Recommendation ITU-T H.812 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.812 + +# Interoperability design guidelines for personal connected health systems: Services interface + +## Summary + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for personal connected health services. The Continua Design Guidelines also contains design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. + +ITU-T H.812 contains an overview of the Services interface (Services-IF), common design guidelines for all Services-IF Certified Capability Classes (CCC) and the design guidelines for Consent Enabled Personal Health Gateway (PHG) and Services CCCs. + +The design guidelines which support the following Certified Capability Classes (CCC) are defined in separate guidelines documents, as follows: + +- Observation Upload capability in ITU-T H.812.1 (2017) +- Questionnaire capability in ITU-T H.812.2 (2017) +- Capability Exchange capability in ITU-T H.812.3 (2017) +- Authenticated Persistent Session capability in ITU-T H.812.4(2017) + +ITU-T H.812 is part of the "ITU-T H.810 interoperability design guidelines for personal connected health systems" subseries that covers the following areas: + +- ITU-T H.810 – Interoperability design guidelines for personal connected health systems: Introduction +- ITU-T H.811 – Interoperability design guidelines for personal connected health systems: Personal Health Devices interface +- ITU-T H.812 – Interoperability design guidelines for personal connected health systems: Services interface (this design guidelines document) +- ITU-T H.812.1 – Interoperability design guidelines for personal connected health systems: Services interface: Observation upload capability +- ITU-T H.812.2 – Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability +- ITU-T H.812.3 – Interoperability design guidelines for personal connected health systems: Services interface: Capability exchange capability +- ITU-T H.812.4 – Interoperability design guidelines for personal connected health systems: Services interface: Authenticated persistent session capability +- ITU-T H.813 – Interoperability design guidelines for personal connected health systems: Healthcare information system interface + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.812 | 2015-11-29 | 16 | 11.1002/1000/12653 | +| 2.0 | ITU-T H.812 | 2016-07-14 | 16 | 11.1002/1000/12913 | +| 3.0 | ITU-T H.812 | 2017-11-29 | 16 | 11.1002/1000/13415 | + +## Keywords + +CDG, Continua Design Guidelines, healthcare information systems, personal connected health systems, personal health devices, services. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# Table of Contents + +###### Page + +| | | | +|-------|----------------------------------------------------------------------|----| +| 0 | Introduction..... | vi | +| 0.1 | Organization ..... | vi | +| 0.2 | Guideline releases and versioning..... | vi | +| 0.3 | What's new..... | vi | +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 2 | +| 6 | Architecture ..... | 2 | +| 7 | Use cases..... | 6 | +| 7.1 | Consent management use cases ..... | 6 | +| 7.1.1 | Upload consent to the server ..... | 6 | +| 7.1.2 | Retrieve the already completed patient consent from the server ..... | 7 | +| 7.1.3 | Upload updated consent to the server ..... | 7 | +| 7.2 | Consent enforcement use case..... | 7 | +| 7.2.1 | Content encryption before upload ..... | 7 | +| 7.3 | Other CCC use cases ..... | 7 | +| 8 | Behavioural models ..... | 7 | +| 8.1 | Common Services-IF message exchange behaviour ..... | 8 | +| 8.2 | Common security model for REST based CCC implementations ..... | 8 | +| 8.3 | Consent management behavioural model..... | 9 | +| 8.4 | Consent enforcement behavioural model ..... | 10 | +| 9 | Implementation ..... | 10 | +| 9.1 | Consent representation ..... | 10 | +| 9.2 | Transport protocols..... | 11 | +| 9.2.1 | Transport protocol using data over HTTP..... | 11 | +| 9.2.2 | Transport protocol using IHE XDR ..... | 11 | +| 9.3 | Consent enforcement ..... | 11 | +| 9.3.1 | Consent enforcement using XML encryption ..... | 11 | +| 9.3.2 | Consent enforcement using IHE DEN ..... | 11 | +| | Annex A Normative guidelines overview..... | 12 | + +###### **Page** + +| | | +|--------------------------------------------------------------------------|----| +| Annex B General security guidelines for Services-IF CCCs..... | 14 | +| Annex C Normative guidelines for consent management ..... | 16 | +| Appendix I ATOM feed elements for consent management ..... | 24 | +| I.1 Information for consent in the root.xml ..... | 24 | +| Appendix II Examples of consent management using SOAP..... | 25 | +| Appendix III OAuth example ..... | 28 | +| Appendix IV Consent Enabled PHG Questionnaire response association ..... | 30 | +| Bibliography..... | 32 | + +## **List of Tables** + +###### **Page** + +| | | +|--------------------------------------------------------------------------------------------------------------------|----| +| Table A.1 – Certified Capability Classes..... | 12 | +| Table A.2 – Guidelines for Certified Capability Classes..... | 12 | +| Table A.3 – Requirements common to all CCCs..... | 13 | +| Table B.1 – PHG security guidelines using REST ..... | 14 | +| Table B.2 – Health & Fitness service security guidelines using REST ..... | 15 | +| Table B.3 – Services-IF transport security guidelines ..... | 15 | +| Table C.1 – Consent management guidelines using REST for the Consent Enabled PHG..... | 16 | +| Table C.2 – Consent management guidelines using REST for Consent Enabled Health & Fitness service ..... | 17 | +| Table C.3 – Consent enforcement guidelines using data for the Consent Enabled PHG ..... | 18 | +| Table C.4 – Consent enforcement guidelines using data for Consent Enabled Health & Fitness service ..... | 19 | +| Table C.5 – Consent management guidelines using SOAP for the Consent Enabled PHG ..... | 20 | +| Table C.6 – Consent management guidelines using SOAP for Consent Enabled Health & Fitness service ..... | 21 | +| Table C.7 – Consent enforcement guidelines using SOAP for the Consent Enabled PHG..... | 21 | +| Table C.8 – Consent enforcement guidelines using SOAP for Consent Enabled Health & Fitness service ..... | 22 | +| Table I.1 – ATOM feed child elements for consent management..... | 24 | +| Table IV.1 – The elements of the confidentiality code system..... | 30 | +| Table IV.2 – The elements of the Continua Consent Directive code system ..... | 30 | +| Table IV.3 – The translation of the confidentiality code system to the Continua Consent Directive code system..... | 30 | + +| | | +|----------------------------------------------------------------------------|----| +| Table IV.4 – OID distribution for Personal Connected Health Alliance ..... | 31 | +|----------------------------------------------------------------------------|----| + +# List of Figures + +| | | +|---------------------------------------------------------------------------------------------------------------------------|----| +| Figure 1-1 – Services interface in the Continua architecture..... | 1 | +| Figure 6-1 – Services interface in the Continua E2E architecture..... | 2 | +| Figure 6-2 – Services-IF example..... | 3 | +| Figure 6-3 – Continua Services-IF showing the Services-IF Certified Capability Classes ..... | 4 | +| Figure 6-4 – Services-IF reference model..... | 5 | +| Figure 8-1 – All connections are initiated from PHG ..... | 8 | +| Figure 8-2 – Security behaviour for authorized RESTful CCC behaviour (Questionnaire use case is taken as an example)..... | 9 | +| Figure 8-3 – Transactions between PHG and Health & Fitness service related to consent management ..... | 10 | +| Figure 8-4 – Consent enforcement at the Services-IF..... | 10 | +| Figure II.1 – The PCD-01 transaction with un-encrypted payload..... | 25 | +| Figure II.2 – Encrypted PCD-01 transaction – public key based..... | 26 | +| Figure II.3 – Encrypted PCD-01 transaction – symmetric key based..... | 27 | + +# 0 Introduction + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for personal connected health services. The Continua Design Guidelines also contains additional design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. + +This design guidelines document contains additional design guidelines (DGs) for interoperability that further clarify or reduce the options or add features missing from underlying standards or specifications. + +This design guidelines document contains a Services-IF overview, common design guidelines for all Services-IF Certified Capability Classes (CCC) and the design guidelines for Consent Enabled Personal Health Gateway (PHG) and Health & Fitness Service CCCs. + +The design guidelines which support the following Certified Capability Classes (CCC) are defined in separate design guidelines documents as follows: + +- [ITU-T H.812.1] *Interoperability design guidelines for personal connected health systems: Services interface: Observation upload capability.* +- [ITU-T H.812.2] *Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability.* +- [ITU-T H.812.3] *Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability.* +- [ITU-T H.812.4] *Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability.* + +This design guidelines document is part of the "ITU-T H.810 interoperability design guidelines for personal health systems" subseries. See [ITU-T H.810] for more details. + +## 0.1 Organization + +This design guidelines document is organized in the following manner. + +**Clauses 0-5: Introduction and terminology** – These clauses provide Services-IF specific information to help understand the structure of the design specifications. + +**Clause 6: Services-IF overview** – This clause provides an overview of the Services-IF CCCs. + +**Clause 7: Use cases** – This clause provides practical examples. + +**Clause 8: Behavioural model** – This clause provides an overview of sequences of interactions under Services interface common CCCs and summarizes typical interactions, constraints and exceptions. + +**Clause 9: Implementation** – This clause details the use of common payload content and simple object access protocol (SOAP) vs representational state transfer (REST) based transport methodology in the common Services-IF Certified Capability Classes. + +## 0.2 Guideline releases and versioning + +See clause 0.2 of [ITU-T H.810] for release and versioning information. + +## 0.3 What's new + +To see what is new in this release of the design guidelines refer to clause 0.3 of [ITU-T H.810]. + +# Interoperability design guidelines for personal connected health systems: Services interface + +# 1 Scope + +This design guidelines document focuses on the following interface: + +- **Services-IF** The interface between a Personal Health Gateway (PHG) and Services. + +This interface is defined in the Continua architecture as described in clause 6 of [ITU-T H.810] and is shown in Figure 1-1. + +![Diagram of the Services interface in the Continua architecture showing the flow from Personal Health Devices through a Personal Health Gateway (PHG) to a Health and fitness service, and finally to a Healthcare Information System (HIS).](dbe553cf16dd14073b89a8263a428664_img.jpg) + +The diagram illustrates the flow of data and services in the Continua architecture. On the left, two boxes represent 'X73 device' and 'Smart device', both labeled as 'Personal Health Device'. These devices connect to a 'Personal Health Gateway (PHG)' via the 'Personal Health Devices interface'. This interface is supported by a stack of protocols: IEEE, ISO, X73-IF, NFC forum, ZigBee, Bluetooth, USB, Ble-IF, and Bluetooth smart. The PHG then connects to a 'Health and fitness service' via the 'Services interface'. This interface is supported by a stack of protocols: HL7, IHE, OASIS, IETF, and W3C. The 'Health and fitness service' is represented by a cloud icon with server symbols. Finally, the service connects to a 'Healthcare Information System (HIS)' via the 'HIS interface'. This interface is supported by a stack of protocols: HL7, IHE, OASIS, IETF, and W3C. The HIS is represented by icons of a hospital, a person, and a medical bag. + +Diagram of the Services interface in the Continua architecture showing the flow from Personal Health Devices through a Personal Health Gateway (PHG) to a Health and fitness service, and finally to a Healthcare Information System (HIS). + +H.812(17)\_F1-1 + +**Figure 1-1 – Services interface in the Continua architecture** + +There are a number of Certified Capability Classes (CCC) related to the Services-IF. This design guidelines document contains interoperability design guidelines that are applicable to several CCCs. Security interoperability design guidelines are one such example. In addition, this design guidelines document contains the design guidelines for the Consent Enabled PHG and Services interface CCCs. These CCCs may be grouped with multiple other Services-IF related CCCs, such as for example, Observation Upload CCCs or Questionnaire enabled CCCs. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +Other referenced documents can be found in clause 2 of [ITU-T H.810]. + +# 3 Definitions + +This design guidelines document uses terms defined in [ITU-T H.810]. + +# 4 Abbreviations and acronyms + +This design guidelines document uses abbreviations and acronyms defined in [ITU-T H.810]. + +# 5 Conventions + +This design guidelines document follows the conventions defined in [ITU-T H.810]. + +# 6 Architecture + +In this end-to-end (E2E) reference architecture, the Services interface (Services-IF) connects a Personal Health Gateway (PHG) to a Health & Fitness service (HFS). Figure 6-1 shows the Services interface in the Continua E2E architecture and Figure 6-2 shows an example of a Services-IF. + +The Services-IF design guidelines are focused on enabling the interoperable exchange of information across a Services interface. A set of Services-IF related Certified Capability Classes is defined for the PHG and the Health & Fitness service to enable interoperability for a number of different use cases, including the uploading of measurement data, completing of questionnaires and executing of commands. + +![Figure 6-1: Services interface in the Continua E2E architecture. The diagram shows a flow from Personal Health Devices (X73 device, Smart device) through a Personal Health Gateway (PHG) to a Health & Fitness service, and finally to a Healthcare Information System (HIS). The PHG connects to the Health & Fitness service via the Services interface, which uses protocols like HL7, IHE, OASIS, IETF, and W3C. The Health & Fitness service connects to the HIS via the HIS interface, which also uses protocols like HL7, IHE, OASIS, IETF, and W3C.](fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg) + +The diagram illustrates the Continua E2E architecture flow. On the left, two boxes represent 'X73 device' and 'Smart device', both labeled as 'Personal Health Device'. These connect to a 'Personal Health Gateway (PHG)' box via a 'Personal Health Devices interface'. This interface lists protocols: IEEE ISO X73-IF, NFC forum, ZigBee, Bluetooth, USB, Ble-IF, and Bluetooth smart. The PHG connects to a 'Health & Fitness service' box via a 'Services interface'. This interface lists protocols: HL7, IHE, OASIS, IETF, and W3C. The 'Health & Fitness service' connects to a 'Healthcare Information System (HIS)' box via a 'HIS interface'. This interface also lists protocols: HL7, IHE, OASIS, IETF, and W3C. The HIS box contains icons for a hospital, a person with a stethoscope, and a medical bag. + +Figure 6-1: Services interface in the Continua E2E architecture. The diagram shows a flow from Personal Health Devices (X73 device, Smart device) through a Personal Health Gateway (PHG) to a Health & Fitness service, and finally to a Healthcare Information System (HIS). The PHG connects to the Health & Fitness service via the Services interface, which uses protocols like HL7, IHE, OASIS, IETF, and W3C. The Health & Fitness service connects to the HIS via the HIS interface, which also uses protocols like HL7, IHE, OASIS, IETF, and W3C. + +H.812(17)\_F6-1 + +Figure 6-1 – Services interface in the Continua E2E architecture + +![Diagram illustrating the Services-IF example. On the left, a 'Facility-Office-Home-Mobile' section contains a 'Personal Health Gateway' (PHG) connected to an 'X73 device' via 'X73-IF' and a 'SMART device' via 'BLE-IF'. The PHG is labeled as a 'Services observation sender'. On the right, a 'Backend' section contains a 'Services observation receiver' which includes a 'Health & Fitness service' and a 'Healthcare Information System (HIS)'. The PHG connects to the Health & Fitness service via 'Services-IF'. The Health & Fitness service connects to the HIS via 'HIS-IF'. The HIS is associated with 'EHRs', 'PHRs', 'Physician', and 'EMRs'. A small figure of a person is shown next to the HIS. The diagram is labeled H.812(17)_F6-2.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Diagram illustrating the Services-IF example. On the left, a 'Facility-Office-Home-Mobile' section contains a 'Personal Health Gateway' (PHG) connected to an 'X73 device' via 'X73-IF' and a 'SMART device' via 'BLE-IF'. The PHG is labeled as a 'Services observation sender'. On the right, a 'Backend' section contains a 'Services observation receiver' which includes a 'Health & Fitness service' and a 'Healthcare Information System (HIS)'. The PHG connects to the Health & Fitness service via 'Services-IF'. The Health & Fitness service connects to the HIS via 'HIS-IF'. The HIS is associated with 'EHRs', 'PHRs', 'Physician', and 'EMRs'. A small figure of a person is shown next to the HIS. The diagram is labeled H.812(17)\_F6-2. + +**Figure 6-2 – Services-IF example** + +In addition to the Services-IF, the end-to-end reference architecture also defines the Healthcare Information System interface (HIS-IF). The Services-IF is designed to enable granular information exchange between a PHG (typically a PC, laptop, tablet, mobile phone or other type of embedded device), which is a device close to the user/patient and a Health & Fitness service (typically a backend cloud based service) which collects the information from such users and makes it available for further usage. In contrast the HIS-IF is designed to enable aggregated information exchange between two backend systems, e.g., a disease management system and an electronic health record (EHR)1. The HIS-IF is defined in [ITU-T H.813]. + +It is also expected that a PHG may be deployed to in-home or user-carried applications, which places a number of constraints on the Services-IF design. Due to the difficulty in maintaining and/or upgrading these devices "in the field", a PHG should be robust and stand-alone and simple enough to keep costs low and technical operational experience or expertise requirements to a minimum. Because of this focus, the Services-IF allows the majority of the contextual metadata associated with the exchange of observations to reside outside of the PHG. + +On the other hand, it is expected that a Health & Fitness service will be hosted by a more capable system such as a server or personal computer. Therefore, the design of the Services-IF aims to push complexity and maintainability issues to the Health & Fitness service as this means that the issues can be avoided on the PHG. + +The Services-IF is an abstract channel composed of one or more CCC pairs that connect a PHG application with a Health & Fitness service application. Each CCC pair has a component that resides in the Health & Fitness service application and a component that resides in the PHG application. Continua defines Certified Capability Classes on both sides of the Services-IF. + +This version of the Services-IF guidelines enables the following Certified Capability Classes: + +- the uploading of observations from the PHG to the Health & Fitness service in two different styles: web services (SOAP) and REST (data) [ITU-T H.812.1]; + +1 NOTE – Within the end-to-end architecture, both the Services and the Healthcare Information System (HIS) interfaces can be implemented on a device close to the user/patient (PC, laptop, mobile phone, etc.) in order to exchange information with entities that are geographically distant from such devices. The guidelines place no restrictions on the deployment of Certified Capability Classes on specific hardware. + +- the uploading of consent information from the PHG to the Health & Fitness service in two different styles: web services (SOAP) and REST (data) [ITU-T H.812]; +- the downloading of to-be-completed questionnaires from the Health & Fitness service to the PHG and the uploading of completed questionnaires from the PHG to the Health & Fitness service [ITU-T H.812.2]; +- the exchange of information (e.g., unsolicited commands) between the Health & Fitness service and the PHG over an authenticated persistent session [ITU-T H.812.4]; +- the exchange of supported Certified Capability Class information (capability exchange) between the PHG and the Health & Fitness service as an enabler for the other use cases [ITU-T H.812.3]. + +A PHG can support one or more applications that each implement one or more Continua Certified Capability Classes. Figure 6-3 depicts the Continua Services-IF, showing a PHG application and a Health & Fitness service application in which all of the possible Services-IF Certified Capability Classes are implemented. + +![Diagram of Continua Services-IF showing a PHG application and a Services application connected via a Service interface. The PHG application (Black box of Personal Health Gateway) contains Application logic with seven capability classes: SOAP observation upload-PHG, hData observation upload-PHG, SOAP consent enabled-PHG, hData consent enabled-PHG, Questionnaire-PHG, Authenticated persistent session-PHG, and Capability exchange-PHG. The Services application (Black box of Health & Fitness service) contains Service logic with seven corresponding capability classes: SOAP observation upload-services, hData observation upload-services, SOAP consent enabled-services, hData consent enabled-services, Questionnaire-services, Authenticated persistent session-services, and Capability exchange-services. Arrows connect each PHG capability class to its corresponding services capability class through the central Service interface.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +Diagram of Continua Services-IF showing a PHG application and a Services application connected via a Service interface. The PHG application (Black box of Personal Health Gateway) contains Application logic with seven capability classes: SOAP observation upload-PHG, hData observation upload-PHG, SOAP consent enabled-PHG, hData consent enabled-PHG, Questionnaire-PHG, Authenticated persistent session-PHG, and Capability exchange-PHG. The Services application (Black box of Health & Fitness service) contains Service logic with seven corresponding capability classes: SOAP observation upload-services, hData observation upload-services, SOAP consent enabled-services, hData consent enabled-services, Questionnaire-services, Authenticated persistent session-services, and Capability exchange-services. Arrows connect each PHG capability class to its corresponding services capability class through the central Service interface. + +H.812(17)\_F6-3 + +**Figure 6-3 – Continua Services-IF showing the Services-IF Certified Capability Classes** + +The intent of these guidelines is to specify system behaviour in enough detail to achieve an acceptable level of interoperability for a particular use case. A use case is encapsulated in a Certified Capability Class (CCC). The guidelines make normative statements about how the network interface of the components of the CCC functions. For the Services-IF these components exist in the context of applications or services that reside on a PHG or on a Health & Fitness service. + +Common platforms often limit the manner in which applications can communicate with each other to ensure the stability of the overall platform. This limited interaction between applications is called sandboxing. In order to support sandboxed applications this version of the Services-IF uses a reference model that defines an application as a container for one or more CCC components. Interactions between the components within the application container do not have normative + +requirements and are fully up to the developer of the application. Interactions on the Services-IF between the application's CCCs on the PHG and the corresponding CCCs on the Health & Fitness service are visible and do have normative requirements in order to pass certification. + +The reference model allows multiple applications to exist in a PHG or a Health & Fitness service, but applications do not interact with other applications except through network interfaces. In these guidelines applications that run on a Health & Fitness service are often referred to as services since Health & Fitness services are commonly web service platforms. A Health & Fitness service is conceptually the same as a PHG application. + +These guidelines document mechanisms by which components may communicate with each other through an internal application programming interface (API). Future versions of the Services-IF may use these mechanisms to enable interoperability between components within an application. + +In Figure 6-4 the concepts of the Services-IF reference model are used to depict a PHG with two independent applications communicating with a Services application. One PHG application supports three CCCs and the other supports a single CCC. Normative requirements are made on the network interfaces between the PHG and the Health & Fitness service. The interactions between the CCC components within an application container are not normative and are shown as red dashed lines coordinated by application internal processing that are out of the scope of these guidelines. + +![Figure 6-4 – Services-IF reference model diagram showing two PHG applications on the left (AHD device) and a Services application on the right (Health & Fitness service) connected via a central Service interface. The top PHG application contains Application logic, Capability exchange PHG component, Questionnaire PHG component, and APS PHG component. The bottom PHG application contains Application logic and Observation upload PHG component. The Services application contains Server logic, Capability exchange services component, Questionnaire services component, APS services component, and Observation upload services component. All PHG components connect to the Services components through Network interfaces across the Service interface.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +The diagram illustrates the Services-IF reference model. On the left, an 'AHD device' contains two 'PHG application' containers. The top PHG application includes 'Application logic' (yellow oval) connected by red dashed lines to three components: 'Capability exchange PHG component', 'Questionnaire PHG component', and 'APS PHG component'. The bottom PHG application includes 'Application logic' connected to 'Observation upload PHG component'. On the right, a 'Health & Fitness service' contains a 'Services application' container. It includes 'Server logic' (yellow oval) connected by red dashed lines to five components: 'Capability exchange services component', 'Questionnaire services component', 'APS services component', and 'Observation upload services component'. A central vertical yellow bar labeled 'Service interface' separates the two sides. Horizontal double-headed arrows labeled 'Network interface' connect each PHG component to its corresponding services component across the interface. The labels 'PHG application' and 'Services application' are placed at the top of their respective containers. The labels 'AHD device' and 'Health & Fitness service' are placed at the bottom of their respective containers. + +Figure 6-4 – Services-IF reference model diagram showing two PHG applications on the left (AHD device) and a Services application on the right (Health & Fitness service) connected via a central Service interface. The top PHG application contains Application logic, Capability exchange PHG component, Questionnaire PHG component, and APS PHG component. The bottom PHG application contains Application logic and Observation upload PHG component. The Services application contains Server logic, Capability exchange services component, Questionnaire services component, APS services component, and Observation upload services component. All PHG components connect to the Services components through Network interfaces across the Service interface. + +H.812(17)\_F6-4 + +**Figure 6-4 – Services-IF reference model** + +Communications that use the Services-IF start with the PHG's Capability Exchange component. This component sends a request to its peer component on the Health & Fitness service. The request asks the Health & Fitness service to specify the different Certified Capability Classes that it supports. In common language the PHG application is asking "What things can you do?" The Health & Fitness service application answers this in terms of the CCCs it supports. In the case of Figure 6-4 the Health & Fitness service application would say "I support Capability Exchange, + +Questionnaires, SOAP Observation Upload and Authenticated Persistent Sessions (APSs)". When the Capability Exchange component of the services application answers the PHG application, it will typically provide the PHG with additional information, such as an URL, which enables the PHG application to take the next step in communication with a particular CCC. A PHG that only supports observation uploading using SOAP does not need to implement Capability Exchange. Capability Exchange does not need to be invoked if the PHG is already aware of the capabilities of the Health & Fitness service. + +# **7 Use cases** + +## **7.1 Consent management use cases** + +A consent directive is a record of a healthcare client's privacy policy that grants or withholds consent to the individually identifiable health information (IIHI) [HL7 CDA IG]. + +The user consent requirement is derived from different regulations such as the Health Information and Portability Accountability Act (HIPAA), EU Directives 95/46, etc. These privacy laws define and assign specific rights to patients with respect to the collection, access, use and disclosure of their health information. The laws mandate that the patient consent must be obtained before his/her health information may be accessed, used or shared. For example, a patient during registration with a disease management organization (DMO) may be required to fill in a consent form. This consent form captures the patient's acknowledgment and/or signature for a predefined set of policies that specify who is allowed to access his/her IIHI, for what purpose and how they can use it. This clause introduces the capturing and transferring of consent policy in electronic form on the Services-IF. Digital consent contributes to improved patient empowerment and efficient handling to comply with consent. Examples of patient consent include basic opt-in/opt-out to IIHI, allowing emergency override, limiting access to functional roles (e.g., direct care providers), specific documents to be used for specific research projects, etc. + +In a basic scenario a patient will define his consent during or after registering with the Health & Fitness service application. How he precisely specifies his consent is out-of-scope for these guidelines, but it could involve selection and possibly adaptation of a default policy using a user interface on his PHG which translates it to a machine readable consent policy representation. Such policies typically contain a reference to the parties involved, data objects and actions that are authorized or not. A Health & Fitness service application that receives consent for a particular patient will store it and enforce it for health data that it receives for the patient. + +The use cases below are focused on the needs identified for patient consent management. + +### **7.1.1 Upload consent to the server** + +Adam Everyman registers with an organization e.g., a disease management organization (DMO) which remotely monitors patients at home and collects health information from health measurement devices installed at Adam's home. At the time of registration, Adam fills in an eConsent form on the Personal Health Gateway (PHG) application. The eConsent form consists of options regarding who will be able to access, use, update and disclose different types of vital signs that are collected through a remote patient monitoring system. After specifying preferences, Adam then hits the "submit" button on his telehealth hub. The hub compiles his preferences into a privacy consent directives document which is based on the HL7 CDA R2 standard and is then sent from his PHG to the DMO which provides a remote patient monitoring service. The consent directive then governs access to patient data at the DMO and if Adam's data is sent to third parties which assuming that this is allowed may include the patient's personal health record (PHR), electronic health records (EHRs) and electronic medical records (EMRs). Adam's privacy consent directive will then be associated with the data via the patient identifier. + +### **7.1.2 Retrieve the already completed patient consent from the server** + +Adam may want to update his privacy preferences e.g., allowing his fitness coach to get access to his data as he has recently registered with a fitness service as suggested by a nurse at the DMO. His PHG provides a link to his latest version of the privacy consent directive document. Adam clicks on the link and PHG then retrieves the latest version of his privacy consent directives from the server and renders it to Adam. + +### **7.1.3 Upload updated consent to the server** + +Adam reviews his privacy consent preferences and updates them if his fitness coach does not have access to his data. After updating consent preferences, he hits the "submit" button on his PHG which then compiles his preferences into a privacy consent directive document that is sent to the DMO. The DMO replaces the old consent with the updated privacy consent directive document. + +## **7.2 Consent enforcement use case** + +Consent enforcement through encryption protects the privacy of the patient in an efficient manner and makes sure that the content (e.g., observations or response to a Questionnaire) is viewed only by the intended recipient. This prevents viewing of the content by other individuals who may be working in the same organization e.g., administrative staff. The Consent Enabled Health & Fitness service should evaluate consent before decrypting the content. Consent is evaluated in order to determine whether the recipient is able to view the content. For example, the process of consent evaluation results in "Success-1" or "Failure-0". The Consent enabled Health & Fitness service should enforce the consent preferences expressed in a consent document. + +### **7.2.1 Content encryption before upload** + +Adam Everyman registers with the DMO which remotely monitors him at home and collects health information from health measurement devices installed at his home. Adam Everyman has also registered with a fitness coach as suggested by a nurse at the DMO. Adam Everyman wants his fitness coach to view his activity data and not data from other measurement devices such as a blood pressure monitor (BPM). Adam configures his PHG such that now only the nurse at the DMO organization has access to the data from the BPM and activity monitors while the fitness coach only has access to the data from the activity monitors. This is enabled through encryption. + +## **7.3 Other CCC use cases** + +See clause 6 in the following design guidelines for their respective CCC use cases: + +- [ITU-T H.812.1] Observation Upload +- [ITU-T H.812.2] Questionnaire +- [ITU-T H.812.3] Capability Exchange +- [ITU-T H.812.4] Authenticated Persistent Session + +# **8 Behavioural models** + +This clause includes: + +- Services-IF message exchange behaviour +- Security behaviour of REST based CCCs +- Consent management and enforcement of CCC behaviour + +## 8.1 Common Services-IF message exchange behaviour + +Due to security and privacy concerns, as well as the technical feasibility of the overall system, the Services-IF requires that all connections be initiated from the PHG. This is illustrated in Figure 8-1. See each design guideline for its message payload and other specifics. + +![Sequence diagram showing message exchange between PHG and Health & Fitness service. The PHG initiates the connection, and the Health & Fitness service responds. A dashed line indicates a shoulder tap from the Health & Fitness service to the PHG.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +``` +sequenceDiagram + participant PHG + participant HFS as Health & Fitness service + Note right of HFS: H&S service shoulder tap if needed – APS only (see ITU-T H.812.4 – APS) + PHG->>HFS: PHG initiates connection + HFS-->>PHG: PHG receives response as appropriate + Note right of HFS: H.812(17)_F8-1 +``` + +Sequence diagram showing message exchange between PHG and Health & Fitness service. The PHG initiates the connection, and the Health & Fitness service responds. A dashed line indicates a shoulder tap from the Health & Fitness service to the PHG. + +**Figure 8-1 – All connections are initiated from PHG** + +When transport level security (TLS) is required for point to point content security, the use of mutual certificate validation in the TLS handshake is up to the security policy of the Health & Fitness service. + +When authentication is required: + +- in the SOAP case, the authentication is a SAML 2.0 token and +- for data, an OAuth 2.0 bearer token. + +How the PHG obtains these tokens is not specified in these guidelines as it depends upon the trust relationship established between the parties. The Health & Fitness service application may support one or more WS-Trust options to obtain SAML 2.0 tokens or it may support an OAuth 2.0 authorization framework server using one or more grant types, for example the resource owner password credentials grant type. The Health & Fitness service may support both services if it supports both data and SOAP uploads. In either of these cases, an out-of-band operation must take place where the user of the PHG establishes some type of account on the Health & Fitness service application allowing the client to obtain these tokens. The Health & Fitness service token service generates these tokens customized for the recipient which it can validate when it receives the content. On the other hand, the Health & Fitness service may require that these tokens be obtained from a third party authorization service (such as a CA) with which the PHG has established a trust relationship. In this case, the Health & Fitness service is letting the third party authorization service validate the client. The Health & Fitness service may then choose to accept any token that comes from this third party service, or it may additionally choose to pass any received token to the third party authorization service for confirmation before acceptance. The trust relationship details are determined by the security policy of the Health & Fitness service. + +## 8.2 Common security model for REST based CCC implementations + +Figure 8-2 provides an interaction diagram for authorized RESTful transactions based on data (REST) over HTTP. The authorization is realized using OAuth 2.0 authorization framework using resource owner password credentials as the authorization grant type. Resource owner password credentials are usually used when there is a high degree of trust between the resource owner (patient) and client (for example, a trusted application running on the application hosting device). In future versions of design guidelines other credential types may be needed based on the use cases where third party applications (less privileged) may be used to get access to patient's data. The resource owner credentials are used for a single request and are exchanged for an access token. The access token is then used to perform a RESTful transaction on a resource. All interactions with the authorization and resource server are performed in a secure session using [IETF RFC 4366]. + +![Sequence diagram illustrating the security behaviour for authorized RESTful CCC behaviour for a questionnaire use case. The diagram shows interactions between a Resource owner (patient), a Public client user agent, an Authorization server, and a Resource server. The Public client user agent is part of a PHG application, and the Resource server is part of a Health & Fitness Service application. The Resource owner is out of scope.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant RO as Resource owner (patient) + participant PCUA as Public client user agent + participant AS as Authorization server + participant RS as Resource server + + Note left of RO: Out of scope + Note right of PCUA: PHG application + Note right of RS: Health & Fitness Service application + + PCUA->>AS: Resource owner credentials + AS-->>PCUA: Access token (type = bearer) + PCUA->>RS: HTTP GET w/access token for questionnaire list + RS-->>PCUA: Atom feed with list of questionnaires + PCUA->>RS: HTTP GET of questionnaire doc [include access token] + RS-->>PCUA: Questionnaire document + PCUA->>RO: Questionnaire presentation + RO-->>PCUA: Response information + PCUA->>RS: HTTP POST of response doc [includes access token] + RS-->>PCUA: Response to POST + +``` + +H.812(17)\_F8-2 + +Sequence diagram illustrating the security behaviour for authorized RESTful CCC behaviour for a questionnaire use case. The diagram shows interactions between a Resource owner (patient), a Public client user agent, an Authorization server, and a Resource server. The Public client user agent is part of a PHG application, and the Resource server is part of a Health & Fitness Service application. The Resource owner is out of scope. + +**Figure 8-2 – Security behaviour for authorized RESTful CCC behaviour (Questionnaire use case is taken as an example)** + +See Table B.1 and Table B.2 for REST CCC security guidelines. + +## 8.3 Consent management behavioural model + +The following exchange mechanisms are specified for the consent management service: + +- Create a *new* consent document on the server. +- Retrieve *already* specified consent document from the server. +- Upload *updated* consent document to the server. + +Figure 8-3 illustrates transactions related to the consent management use cases described in this content profile. + +![Sequence diagram showing transactions between PHG and Health & Fitness service related to consent management. The diagram shows four steps: 1. PHG sends 'Upload consent document' to Service. 2. Service sends 'Retrieve existing consent document' to PHG. 3. PHG performs 'Update content' internally. 4. PHG sends 'Upload updated consent document' to Service. Lifelines are 'Consent Enabled PHG' and 'Consent Enabled Health & Fitness service'. Reference H.812(17)_F8-3.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant PHG as Consent Enabled PHG + participant Service as Consent Enabled Health & Fitness service + Note left of PHG: Consent document + PHG->>Service: Upload consent document + Service->>PHG: Retrieve existing consent document + Note left of PHG: Update content + PHG->>Service: Upload updated consent document + Note right of Service: H.812(17)_F8-3 + +``` + +Sequence diagram showing transactions between PHG and Health & Fitness service related to consent management. The diagram shows four steps: 1. PHG sends 'Upload consent document' to Service. 2. Service sends 'Retrieve existing consent document' to PHG. 3. PHG performs 'Update content' internally. 4. PHG sends 'Upload updated consent document' to Service. Lifelines are 'Consent Enabled PHG' and 'Consent Enabled Health & Fitness service'. Reference H.812(17)\_F8-3. + +**Figure 8-3 – Transactions between PHG and Health & Fitness service related to consent management** + +See Table C.1 and Table C.2 for consent management guidelines. + +## 8.4 Consent enforcement behavioural model + +The following function is specified for the consent enforcement: + +- Encrypt to-be uploaded content + +Figure 8-4 illustrates consent enforcement functionality. + +![Sequence diagram showing consent enforcement at the Services-IF. The diagram shows two steps: 1. PHG performs 'Encrypt content' internally. 2. PHG sends 'Encrypted content' to Service. Lifelines are 'Consent Enabled PHG' and 'Consent Enabled Health & Fitness service'. Reference H.812(17)_F8-4.](77464a47f104d0d647b2414591137b64_img.jpg) + +``` + +sequenceDiagram + participant PHG as Consent Enabled PHG + participant Service as Consent Enabled Health & Fitness service + Note left of PHG: Encrypt content + Note left of PHG: Encrypted content + PHG->>Service: Encrypted content + Note right of Service: H.812(17)_F8-4 + +``` + +Sequence diagram showing consent enforcement at the Services-IF. The diagram shows two steps: 1. PHG performs 'Encrypt content' internally. 2. PHG sends 'Encrypted content' to Service. Lifelines are 'Consent Enabled PHG' and 'Consent Enabled Health & Fitness service'. Reference H.812(17)\_F8-4. + +**Figure 8-4 – Consent enforcement at the Services-IF** + +See Table C.3 and Table C.4 for consent enforcement guidelines. + +# 9 Implementation + +## 9.1 Consent representation + +The consent preferences are represented according to the HL7 Implementation Guide for CDA Release 2.0: Consent Directive in [HL7 CDA IG]. + +The sample files for a consent document can be found in the submission package for the above mentioned standard. + +## **9.2 Transport protocols** + +### **9.2.1 Transport protocol using data over HTTP** + +In this case, data over HTTP is used as the transport protocol for the exchange of consent documents across the Services-IF and it supports all use cases that are mentioned in clauses 7.1 and 7.2. For the detailed requirements on the use of data over HTTP protocol between PHG and Health & Fitness services consult Annex A, Table C.1, Table C.2, Table C.3 and Table C.4. + +### **9.2.2 Transport protocol using IHE XDR** + +In this case, [IHE ITI TFS XDR] is used as transport protocol for the exchange of consent documents across the Services-IF and supports only uploading consent to the server use case. Consent documents are linked to the health information (PCD-01 message) via the patient identifier. This way the consent is associated to the health information and thereby controls its use. + +## **9.3 Consent enforcement** + +### **9.3.1 Consent enforcement using XML encryption** + +In the case of the transport protocol using [IHE ITI TFS XDR], XML encryption standard [W3C XMLLENC] is used to enable the consent enforcement through encryption. The XML encryption standard enables encryption of the payload of the PCD-01 transaction for a specific recipient (e.g., doctor or nurse) at the Consent Enabled Health & Fitness service. + +The XML encryption standard is used to enable consent enforcement through encryption. + +### **9.3.2 Consent enforcement using IHE DEN** + +In the case of the transport protocol using data over HTTP, consent enforcement is enabled through the use of the IHE DEN profile [IHE ITI DEN]. + +# Annex A + +## Normative guidelines overview + +(This annex forms an integral part of this Recommendation.) + +The services Certified Capability Classes are listed in Table A.1. + +**Table A.1 – Certified Capability Classes** + +| Name of Certified Capability Classes | Certified Capability Classes | Logo-ed capability classes | +|-------------------------------------------------------------|------------------------------|----------------------------| +| SOAP Observation Upload - PHG | Yes | Yes | +| SOAP Observation Upload - Health & Fitness service | Yes | Yes | +| data Observation Upload - PHG | Yes | Yes | +| data Observation Upload - Health & Fitness service | Yes | Yes | +| SOAP Consent Enabled - PHG | Yes | Yes | +| SOAP Consent Enabled - Health & Fitness service | Yes | Yes | +| data Consent Enabled - PHG | Yes | Yes | +| data Consent Enabled - Health & Fitness service | Yes | Yes | +| Questionnaire -PHG | Yes | Yes | +| Questionnaire - Health & Fitness service | Yes | Yes | +| Capability Exchange - PHG | Yes | Yes | +| Capability Exchange - Health & Fitness service | Yes | Yes | +| Authenticated Persistent Session - PHG | Yes | * | +| Authenticated Persistent Session - Health & Fitness service | Yes | * 2 | + +The guidelines that are applicable for each of the Certified Capability Classes are referenced in Table A.2 below. + +**Table A.2 – Guidelines for Certified Capability Classes** + +| Certified Capability Classes | Relevant guidelines | +|----------------------------------------------------|-------------------------------------------------------------| +| SOAP Observation Upload - PHG | See [ITU-T H.812.1], and [ITU-T H.812] Table A.3, Table B.3 | +| SOAP Observation Upload - Health & Fitness service | See [ITU-T H.812.1], and [ITU-T H.812] Table A.3, Table B.3 | +| data Observation Upload - PHG | See [ITU-T H.812.1], and [ITU-T H.812] Table A.3, Table B.1 | + +2 \* These cells are intentionally blank. + +**Table A.2 – Guidelines for Certified Capability Classes** + +| Certified Capability Classes | Relevant guidelines | +|-------------------------------------------------------------|--------------------------------------------------------------------------------------| +| data Observation Upload - Health & Fitness service | See [ITU-T H.812.1] and [ITU-T H.812] Table A.3, Table B.2 | +| SOAP Consent Enabled - PHG | See [ITU-T H.812.1] and [ITU-T H.812] Table A.3, Table B.3, Table C.5, Table C.7 | +| SOAP Consent Enabled - Health & Fitness service | See [ITU-T H.812.1], and [ITU-T H.812] Table A.3, Table B.3, Table C.6, Table C.8 | +| data Consent Enabled - PHG | See [ITU-T H.812] Table A.3, Table C.1, Table C.3, Table B.1 | +| data Consent Enabled - Health & Fitness service | See [ITU-T H.812] Table A.3, Table C.2, Table C.4, Table B.2 | +| Questionnaire - PHG | See [ITU-T H.812.2] Table A.1 and [ITU-T H.812] Table A.3, Table B.1 | +| Questionnaire - Health & Fitness service | See [ITU-T H.812.2] Table A.2 and [ITU-T H.812] Table A.3, Table B.2 | +| Capability Exchange - PHG | See [ITU-T H.812.3] Table A.2 and [ITU-T H.812] Table A.3, Table B.1 | +| Capability Exchange - Health & Fitness service | See [ITU-T H.812.3] Table A.1, and [ITU-T H.812] Table A.3, Table B.2 | +| Authenticated Persistent Session - PHG | See [ITU-T H.812.4] Tables A.1, A.2, A.3, A.5 and [ITU-T H.812] Table A.3, Table B.1 | +| Authenticated Persistent Session - Health & Fitness service | See [ITU-T H.812.4], Tables A.1, A.4, A.6 and [ITU-T H.812] Table A.3, Table B.2 | + +**Table A.3 – Requirements common to all CCCs** + +| Name | Description | Comments | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CapX-HFS-Universality | All Health & Fitness services shall support Capability Exchange except SOAP based Observation Upload or Consent Enabled -Health & Fitness service CCCs | A Health & Fitness Service that implements only SOAP based Observation Upload or Consent Enabled -Health & Fitness service CCCs is not required to support the Capability Exchange-Health & Fitness service CCC. | +| HFS-Transport_Connection_Initiation | All Health & Fitness service connections shall be initiated from the Health & Fitness service PHG application and shall not be initiated from the Health & Fitness Service | | + +# Annex B + +## General security guidelines for Services-IF CCCs + +(This annex forms an integral part of this Recommendation.) + +**Table B.1 – PHG security guidelines using REST** + +| Name | Description | Comments | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PHG-Grant_Type | A PHG may use Resource Owner Password Credential as Authorization Grant Type as defined in section 1.3.3 of OAuth v2.0 [IETF RFC 6749]. | A PHG may use other means to get authorization token from the authorization server. | +| PHG-authorization_request | A PHG may obtain authorization token from the authorization server according to sections 4.3 and 4.3.2 of OAuth v2.0 [IETF RFC 6749]. | See examples in Appendix III for the wire format of the authorization request.
    See guideline Health & Fitness service-authorization_request_response for the response | +| PHG-bearer_token | A PHG shall use "bearer" token according to [IETF RFC 6750] when requesting access to a protected resource on the Health & Fitness service [IETF RFC 6750]. | See the related guideline Health & Fitness service-authorization_request_response. | +| PHG-Token_Transmit | A PHG shall use the Authorization Request Header Field Method when sending the bearer token as defined in section 2.1 of [IETF RFC 6750]. | | +| PHG-Confidentiality | A PHG shall at minimum use TLS protocol v1.1 for secure point-to-point communication with the authorization server and Health & Fitness service [IETF RFC 4346]. | | +| PHG-Cipher | A PHG should use an encryption cipher suite of TLS_RSA_WITH_AES_128_CBC_SHA | | + +**Table B.2 – Health & Fitness service security guidelines using REST** + +| Name | Description | Comments | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HFS-authorization_request_response | A Health & Fitness service implementing the authorization server shall return authorization token of type "bearer" after validating the access token request according to the section 4.3.3 of the OAuth v2.0 [IETF RFC 6749]. | See the guideline PHG-authorization_request for the request format.
    Authorization could be a separate entity and does not need to be the part of the Health & Fitness service. | +| HFS-refresh_token | A Health & Fitness service implementing the authorization server shall return refresh token. | | +| HFS-Token_Evaluation | A Health & Fitness service shall evaluate the authorization token and its scope before granting access to a record on the Health & Fitness service. | | + +**Table B.3 – Services-IF transport security guidelines** + +| Name | Description | Comments | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HFS-Security_Transport | A Health & Fitness service application and PHG applications shall at minimum support the TLS protocol v1.1 [IETF RFC 4346] from WS-I BSP v1.0 for secure communication | This guideline is consistent with the IHE ATNA profile when encryption is enabled.
    Continua guidelines depend on the guidance in TLS v1.1 [IETF RFC 4346] for mutual authentication | +| HFS-Security_Transport_Cipher | A Health & Fitness service application and PHG applications shall support AES cipher as specified in [IETF RFC 3268] | IHE ATNA requires the optional use of the following cipher suit:
    TLS_RSA_WITH_AES_128_CBC_SHA
    HIS guidelines use the following cipher suite for security:
    TLS_RSA_WITH_AES_128_CBC_SHA
    Other cipher suites are allowed but would need to be negotiated between PHG and Health & Fitness service | +| HFS-Confidentiality | A Health & Fitness service shall use TLS protocol v1.1 for secure point-to-point communication with the authorization server and Questionnaire enabled Health & Fitness service [IETF RFC 4346]. | | +| HFS-Cipher | A Health & Fitness service should support TLS_RSA_WITH_AES_128_CBC_SHA encryption cipher suite. | | + +# Annex C + +## Normative guidelines for consent management + +(This annex forms an integral part of this Recommendation.) + +**Table C.1 – Consent management guidelines using REST for the Consent Enabled PHG** + +| Name | Description | Comments | +|------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PHG-Consent_Enabled | Consent Enabled PHG shall comply with HL7 CDA R2 Consent Directive standard for the representation of patient consent preference [HL7 CDA IG]. | | +| PHG-Consent_Enabled_Transport_Standards | Consent Enabled PHG shall comply to the following transport standards:
    HL7 Version 3 Specification: data Record Format, Release 1 [HL7 hRF]
    OMG data REST Binding for RLUS [OMG/data BIND]
    OMG Retrieve, Locate, and Update Service (RLUS) Specification 1.0.1 [OMG/data RLUS] | | +| PHG-Post_Consent | Consent Enabled PHG shall use HTTP POST with the following URL for posting consent to the Health & Fitness service:
    baseURL/continua/consent | See the use case in clause 7.1
    For retrieve, locate and update service (RLUS) data over REST transport, this is performed by performing an HTTP POST request without query parameters at this URL with the privacy consent document in the body of the request. | +| Consent_Enabled-PHG-Observation_Association | The consent document transmitted by the Consent Enabled PHG shall contain the same patient identifier as the health and fitness service observation measurement message(s). | This is to associate the consent document to the Health & Fitness service observation measurement messages. | +| Consent_Enabled-PHG-Observation-Association_Value | The "Patient ID" field in the consent document header shall be set to the PID-3 value.
    Subfields CX-1 and CX-4 shall be present and subfield CX-5 shall not be present. | | +| Consent_Enabled-PHG-Questionnaire_Response_Confidentiality | Consent Enabled PHG shall set the confidentiality code value to "R" in the header of the Questionnaire response document. | | + +**Table C.1 – Consent management guidelines using REST for the Consent Enabled PHG** + +| Name | Description | Comments | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Consent_Enabled-PHG-Questionnaire
    Response_Association_Value | To associate Questionnaire response documents(s) with a patient consent document, Consent Enabled PHG shall use the translation element of the confidentiality code system as defined in Table IV.3 | See Table IV.1, Table IV.2, and Table IV.4 | +| Retrieving_Consent | Consent Enabled PHG shall use HTTP GET with the following URL for retrieving consent from the Health & Fitness service:
    baseURL/continua/consent
    Consent Enabled PHG shall use HTTP GET with the value of the link element from the ATOM feed entry for retrieving actual consent document from the Health & Fitness Service and shall validate that it is a valid HL7 CDA R2 Consent Directive document [HL7 CDA IG]. | See the use case in clause 7.1
    For RLUS data over REST transport, this is performed by performing an HTTP GET request without query parameters at the URL representing patient's consent data section path which returns the ATOM feed entry.
    For further information on the Atom feed entry element consult Table I.1 | + +**Table C.2 – Consent management guidelines using REST for Consent Enabled Health & Fitness service** + +| Name | Description | Comments | +|--------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Consent_Enabled-Health-&-Fitness-Service | Consent Enabled Health & Fitness service shall be able to receive, HL7 CDA R2 Consent Directive consent document(s) [HL7 CDA IG]. | | +| Health-&-Fitness Service-Consent_Enabled_Transport_Standards | Consent Enabled PHG shall comply to the following transport standards:
    HL7 Version 3 Specification: data Record Format, Release 1 [HL7 hRF]
    OMG data REST Binding for RLUS [OMG/data BIND]
    OMG Retrieve, Locate, and Update Service (RLUS) Specification 1.0.1 [OMG/data RLUS] | | + +**Table C.2 – Consent management guidelines using REST for Consent Enabled Health & Fitness service** + +| Name | Description | Comments | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| HFS-Consent_Root |

    Consent Enabled Health & Fitness service shall include the following elements for Questionnaire content in the root.xml file:

    1. 1. profile
      1. a. id="consent"
      2. b. reference="http://handle.itu.int/11.1002/3000/hData/Consent/2017/01/H.812.pdf"
    2. 2. section
      1. a. path="consent"
      2. b. profileID= "consent"
      3. c. resourceTypeId="consent"
    3. 3. resourceType
      1. a. resourceTypeId="consent"
      2. b. reference="http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=63"
      3. c. representation
      4. d. mediaType="application/xml2"
    | Note: The URL given for 1.b reference is an example only | +| HFS-Consent_Validate | Consent Enabled Health & Fitness service shall validate the consent document that it is a valid HL7 CDA R2 Consent Directive document and send the HTTP 200 as a response if it is a valid document. | | +| HFS-Post_Consent-Response | Consent Enabled health a fitness service shall create a consent document record after receiving POST message from the Consent Enabled PHG and send the HTTP 201 as a response. | See the PHG-Post_Consent above | +| PHG-Delete_Consent_Response | Consent Enabled Health & Fitness service shall not support the deletion of an existing consent document record and shall return HTTP 405 Method Not Allowed as a response to HTTP DELETE request on a consent URL. | | + +**Table C.3 – Consent enforcement guidelines using data for the Consent Enabled PHG** + +| Name | Description | Comments | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| Consent_Enabled-PHG-Content-Encryption_Actor | Consent Enabled PHG shall encrypt the content in compliance with IHE Document Encryption (DEN) Profile [IHE ITI DEN]. | The content here could be the payload of the PCD-01 transaction or Questionnaire response document. | +| Consent_Enabled-PHG-Questionnaire-Response_MIMEtype_ | Consent Enabled PHG shall set the MIME type to "application/xml" in case the encrypted content is Questionnaire response. | The purpose is to indicate the type of the payload that is encrypted. | +| Consent_Enabled-PHG-Observation - Upload_MIMEtype_ | Consent Enabled PHG shall set the MIME type to "application/txt" in case the encrypted content is Observation Upload. | The purpose is to indicate the type of the payload that is encrypted. | + +**Table C.3 – Consent enforcement guidelines using data for the Consent Enabled PHG** + +| Name | Description | Comments | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Consent_Enabled-PHG-Content-Encryption_Algorithm | Consent Enabled PHG shall use AES-128 CBC for encryption of the content. | The algorithm used is identified through the ContentEncryptionAlgorithmIdentifier in CMS (cryptographic message syntax) which is further profiled by IHE DEN. | +| Consent_Enabled-PHG-Encryption-Recipient_Binding_PKI | Consent Enabled PHG shall use PKI based key management method from IHE DEN Profile [IHE ITI DEN]. | PKI based content key management method uses KeyTransRecipientInfo as CMS RecipientInfoType. This point to the public key or x.509 v3 certificate of the recipient | + +**Table C.4 – Consent enforcement guidelines using data for Consent Enabled Health & Fitness service** + +| Name | Description | Comments | +|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| HFS-Device_HTTP_Ack | Consent Enabled Health & Fitness service shall send the HTTP 202 as a response after successful reception of the encrypted content. | | +| Consent_Enabled-HFS-Content-Decryption_Actor_XDR | Consent Enabled Health & Fitness service shall comply with IHE DEN Profile to decrypt the encrypted content [IHE ITI DEN]. | | +| Consent_EnabledKey_Management | Consent Enabled Health & Fitness service shall use PKI based key management method as specified by the IHE DEN Profile [IHE ITI DEN]. | | +| Consent_Enabled-HFS-Decryption-Algorithm | Consent Enabled Health & Fitness service shall use AES.128 CBC decryption algorithm for the decryption of the payload. | The algorithm used is identified through the ContentEncryptionAlgorithmIdentifier in CMS (cryptographic message syntax) | +| Consent_Enabled-HFS-Consent_Enforcement_ | Consent Enabled Health & Fitness service shall enforce consent preferences expressed in consent document. | For example prevents further disclosure of the content to the unauthorized entities | + +**Table C.5 – Consent management guidelines using SOAP for the Consent Enabled PHG** + +| Name | Description | Comments | +|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Services-Observation-PHG-Consent | Consent Enabled services observation PHG shall comply with [HL7 CDA IG] Consent Directive to represent patient consent in a consent document | | +| Services-Observation-PHG-Consent-Transport | Consent Enabled services observation PHG shall implement the Document Source actor of IHE XDR to send a consent document using the ITI 41 Provide and Register Document Set-b transaction | | +| Services-Observation-PHG-Consent-Frequency | Consent Enabled services observation PHG shall send the consent document at least once to the Observation Health & Fitness service |

    The consent document is e.g., first sent during registration with the service.

    It is recommended to send consent at least once during the lifetime of connection to observation Health & Fitness service. Also supports the use cases such as updating consent preferences.

    The updated consent document is a replacement of the existing consent document at the Consent Enabled observation Health & Fitness service.

    | +| HFS-Observation_Measurement_Consent_Document_Association | The consent document transmitted by the Consent Enabled services observation PHG shall contain the same patient identifier as the services observation measurement message(s) | This is to associate the consent document to the Health-&-Fitness-Services observation measurement messages. | +| HFS-Observation_Measurement_Consent_Document_Association_Value |

    The "Patient ID" field in the consent document header shall be set to the PID-3 value.

    Subfields CX-1 and CX-4 shall be present and subfield CX-5 shall not be present

    | | + +**Table C.6 – Consent management guidelines using SOAP for Consent Enabled Health & Fitness service** + +| Name | Description | Comments | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Observation-Health-&-Fitness-Service-Consent | Consent Enabled observation Health & Fitness service shall be able to receive, [HL7 CDA IG] Consent Directive consent document(s) | | +| Observation-HFS-Consent_Transport | Consent Enabled observation Health & Fitness service shall implement the Document Recipient actor of IHE XDR to receive a consent document using the ITI 41 Provide and Register Document Set-b transaction | The Observation Health & Fitness service replaces the existing consent document if a new version was received as indicated by XDS metadata of the consent document | + +**Table C.7 – Consent enforcement guidelines using SOAP for the Consent Enabled PHG** + +| Name | Description | Comments | +|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HFS-PHG-Content_Encryption_Actor | Consent Enabled Health & Fitness services observation PHG shall encrypt the payload (Annex D of [ITU-T H.812.1]) of the PCD-01 transaction in compliance with the encryption processing rules defined in clause 4.1 of the XML Encryption Specification [W3C XMLENC] | | +| HFS-PHG-Content_Encryption_MIME Type | Consent Enabled Health & Fitness services observation PHG shall set the MIME type to "application/hl7-v2+xml" | The purpose is to indicate the type of payload that is encrypted | +| HFS-Services-PHG-Content_Encryption_Algorithm | Consent Enabled Health & Fitness services observation PHG shall use AES-128 CBC as the payload encryption algorithm from the XML Encryption Specification. | The AES-128 CBC algorithm is identified through the use of the following identifier:
    http://www.w3.org/2001/04/xmlenc#aes128-cbc [W3C XMLENC] | +| HFS-PHG-Encryption_Recipient_Binding_PKI | For the content key transport, Consent Enabled Health & Fitness services observation PHG shall support RSA Version 1.5 from the XML Encryption Specification | The key transport based on RSA v1.5 is identified through the use of the following identifier [W3C XMLENC]:
    http://www.w3.org/2001/04/xmlenc#rsa-1_5 .
    For detailed information about RSA v1.5, consult [b-RFC 2437]
    RSA v1.5 based key transport is also used in CMS (cryptographic message syntax) standard used on the HIS-IF. To find out more, consult [b-RFC 3370] and the consent enforcement guidelines for the HIS-IF | + +**Table C.7 – Consent enforcement guidelines using SOAP for the Consent Enabled PHG** + +| Name | Description | Comments | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HFS-PHG-Encryption_Recipient_Binding_Symmetric | For the content key transport, the Consent Enabled Health & Fitness services observation PHG should use AES-128 symmetric key wrap algorithm from the XML Encryption Specification.
    In case of password based encryption, the Consent Enabled Health & Fitness services observation PHG may use PBKDF2 as the key derivation algorithm from [IETF RFC 3211] | The identifier used for AES-128 symmetric key wrap is http://www.w3.org/2001/04/xmlenc#kw-aes128 [W3C XMLENC]. The key used in wrapping is referred as KEK, which may be derived from a password or a long term shared secret key | +| HFS-PHG-Integrity_Payload_PCD-01_Create | Consent Enabled Health & Fitness services observation PHG shall compute the digest of the encrypted payload using SHA256 (clause 5.7.2) algorithm according to the XML Encryption Specification | The SHA256 algorithm is identified through the use of the following URL: http://www.w3.org/2001/04/xmlenc#sha256 [W3C XMLENC]. | +| HFS-Encrypted_Payload_PCD-01_transaction | Consent Enabled Health & Fitness services observation PHG shall wrap the encrypted payload inside the element | In case of the un-encrypted payload the content is wrapped inside the element . See the example in Figure II.1. | +| HFS-Encrypted_Payload_PCD-01_Transaction_Header | In case of the encrypted payload, the SOAP header shall contain "urn:ihe:continua:enc:pcd:dec:2012:CommunicateEncPCDData" instead of "urn:ihe:pcd:dec:2010:CommunicatePCDData" | The plain PCD-01 transaction contains "urn:ihe:pcd:dec:2010:CommunicatePCDData". See the example in Figure II.1, Figure II.2, and Figure II.3 | + +**Table C.8 – Consent enforcement guidelines using SOAP for Consent Enabled Health & Fitness service** + +| Name | Description | Comments | +|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HFS-HTTP-Ack | Consent Enabled observation Health & Fitness service shall send the SOAP HTTP response with the status code equal to 202 after the successful reception of the encrypted message.
    Consent Enabled observation Health & Fitness service should not send the PCD-01 application level acknowledgement | The reason is that the observation Health & Fitness service may not be in possession of the decryption key as the content may be encrypted for a specific recipient on the Health & Fitness Service | +| HFS-Payload-PCD-01-Verify-Integrity | Consent Enabled observation Health & Fitness service shall verify the message digest of the encrypted payload | | +| HFS-Payload-PCD-01-Verify-Integrity-Algorithm | Consent Enabled observation Health & Fitness service shall support the SHA256 algorithm | | + +**Table C.8 – Consent enforcement guidelines using SOAP for Consent Enabled Health & Fitness service** + +| Name | Description | Comments | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HFS-Content-Decryption-Actor | Consent Enabled observation Health & Fitness service shall comply with decryption rules specified in clause 4.2 of the XML Encryption Specification [W3C XMLENC]. | | +| HFS-Key-Transport-RSA | Consent Enabled observation Health & Fitness service shall support RSA Version 1.5 from the XML Encryption Specification [W3C XMLENC]. | | +| HFS-Key-Transport-Symmetric | Consent Enabled observation Health & Fitness service shall support AES-128 symmetric key wrap algorithm from the XML Encryption Specification [W3C XMLENC].
    The Consent Enabled observation Health & Fitness service shall support PBKDF2 as the key derivation algorithm from [IETF RFC 3211] | The identifier used for AES-128 symmetric key wrap is http://www.w3.org/2001/04/xmlenc#kw-aes128 [W3C XMLENC]. The key used in wrapping is referred as KEK, which may be derived from a password or a long term shared secret key. | +| HFS-Content-Decryption-Algorithm | Consent Enabled observation Health & Fitness service shall use AES-128 CBC decryption algorithm from the XML Encryption Specification [W3C XMLENC]. | The AES-128 CBC algorithm is identified through the use of the following identifier:
    http://www.w3.org/2001/04/xmlenc#aes128-cbc [W3C XMLENC]. | + +# Appendix I + +## ATOM feed elements for consent management + +(This appendix does not form an integral part of this Recommendation.) + +The following ATOM feed child elements of the entry element have a specific usage for the purpose of consent documents. + +**Table I.1 – ATOM feed child elements for consent management** + +| Element | Usage | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Author | Person construct that indicates who provided the information in the consent document.
    i.e., who filled consent | +| Title | Title of the patient consent document (e.g., Adam's consent authorization) | +| link | Reference to the Adam's consent directive document which shall be a valid HL7 CDAR2 Consent Directive IG document.
    The link shall be relative and the privacy consent document shall be in the consent section of the data record. | +| Published | The published element shall be set to the date and time at which the privacy consent document was posted to the server. | + +### I.1 Information for consent in the root.xml + +``` + + consent + + + +
    + consent + consentId + consent +
    + + consent + + http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=63 + + + application/xml + + +``` + +# Appendix II + +## Examples of consent management using SOAP + +(This appendix does not form an integral part of this Recommendation.) + +``` + + + + + + https://localhost:8443/WanReceiver/services/DeviceObservationConsumer_Service>/wsa:To> + + http://www.w3.org/2005/08/addressing/anonymous + + urn:uuid:BC4B55779CD53E3F0C1333967505413 + urn:ihe:pcd:2010:CommunicatePCDData + + + + MSH|^~\&|AT4_PHG^123456789ABCDEF^EUI- + 64|||20120409103145+0000||ORU^R01^ORU_R01|MSGID2848518|P|2.6|||NE|AL|||||IHE PCD ORU- + R012006^HL7^2.16.840.1.113883.9.n.m^HL7 PID|||789567^^^Imaginary + Hospital^PI||Doe^John^Joseph^^^L + OBR|1|POTest^AT4_PHG^1234567890ABCDEF^EUI-64|POTest^AT4_PHG^1234567890ABCDEF^EUI- + 64|182777000^monitoring of patient^SNOMED-CT|||20100903124015+0000 + OBX|1|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|0.0.0.1|532224^MDC_Time_SYNC_NONE^MDC|||||R + OBX|2|CWE|68220^MDC_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.2|1^auth-body-continua(2)|||||R + OBX|3|ST|588800^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|0.0.0.3|1.5|||||R + OBX|4||528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC|1|||||X|||||1234567890ABCDEF^EUI-64 + OBX|5|ST|531696^MDC_ID_MODEL_NUMBER^MDC|PulseOx v1.5|||||R + OBX|6|ST|531970^MDC_ID_MANUFACTURER^MDC|1.0.0.2|AT4 Wireless|||||R + OBX|7|DTM|67975|^MDC_ATTR_TIME_ABS^MDC|1.0.0.3|20100903124015+0000|||||R20100903124015+ + 0000 + OBX|8|CWE|68218^MDC_CERT_DATA_AUTH_BODY^MDC|1.0.0.4|1^auth-body-continua(2)|||||R + OBX|9|ST|588800^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|1.0.0.5|||||R + OBX|10|NA|588801^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|1.0.0.6|16388|||||R + OBX|11|CWE|588802^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC|1.0.0.7|0^unregulated- + device(0)|||||R + OBX|12|NM|150456^MDC_DIM_PERCENT^MDC|||||R|||20100903124015+0000 + OBX|13|NM|149520^MDC_PULS_OXIM_RATE^MDC|1.0.0.9|71|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||R + |||20100903124015+0000 + + +``` + +Figure II.1 – The PCD-01 transaction with un-encrypted payload + +``` + + + + + + https://localhost:8443/WanReceiver/services/DeviceObservationConsumer_Services/DeviceObservationCon +sumer_Service + + http://www.w3.org/2005/08/addressing/anonymous + + urn:uuid:BC4B55779CD53E3F0C1333967505413 + urn:ihe:pcd:2010:CommunicatePCDData + + + + + + + + + + John Smith + + + Encrypted Key... + + + + + Enc.OBX Message goes here... + + + + + + +``` + +**Figure II.2 – Encrypted PCD-01 transaction – public key based** + +In Figure II.2, PCD-01 transaction is shown with encrypted payload using XML encryption standard. The content key is encrypted with the public key of the recipient. + +``` + + + + + + https://localhost:8443/WanReceiver/services/DeviceObservationConsumer_Services/DeviceObservationCon +sumer_Service + + http://www.w3.org/2005/08/addressing/anonymous + + urn:uuid:BC4B55779CD53E3F0C1333967505413 + urn:ihe:pcd:2010:CommunicatePCDData + + + + + + + + + + John Smith + + + Encrypted Key... + + + + + Enc.OBX Message goes here... + + + + + + +``` + +**Figure II.3 – Encrypted PCD-01 transaction – symmetric key based** + +Figure II.3 shows PCD-01 transaction with encrypted payload using XML encryption standard. In this example, the content key is assumed to be known to both the sender and recipient and is read only. + +# Appendix III + +## OAuth example + +(This appendix does not form an integral part of this Recommendation.) + +### Example 1: + +- Request for access token + +In order to obtain an access token, a Questionnaire-enabled PHG makes the following HTTP POST request to the authorization server. + +``` +POST http://localhost:3000/oauth2/token HTTP/1.1 +User-Agent: Fiddler +Host: localhost:3000 +Authorization: Basic +MTIwMDk0NTc0NjczNzY3OmI1NGRjODI0NzZhZjI4MTRINjIwYjg2Nzc2YzQyYzBl +Content-Type: application/x-www-form-urlencoded +Content-Length: 59 + +grant_type=password&username=john@example.com&password=test +``` + +#### Where + +- is the URL for reaching authorization server and must be known to the Questionnaire enabled PHG. +- Authorization: Basic +MTIwMDk0NTc0NjczNzY3OmI1NGRjODI0NzZhZjI4MTRINjIwYjg2Nzc2YzQyYzBl +- This is a basic HTTP authorization header that is generated by Questionnaire enabled PHG using its given identifier and secret word by encoding them into Base64 hash string +Base64("120094574673767:b54dc82476af2814e620b86776c42c0e") = +- "MTIwMDk0NTc0NjczNzY3OmI1NGRjODI0NzZhZjI4MTRINjIwYjg2Nzc2YzQyYzBl" +- grant\_type indicates the authorization code. In this authorization code is username and password. +- Access Token Response + +The authorization server validates an access token request and if authorized, it generates an access token of type "bearer" and an optional refresh token. + +``` +HTTP/1.1 200 OK +Content-Length: 141 +Content-Type: application/json +X-Ua-Compatible: IE=Edge +X-Runtime: 0.273027 +Server: WEBrick/1.3.1 (Ruby/1.9.3/2013-02-22) +Date: Wed, 03 Apr 2013 08:54:57 GMT +Connection: Keep-Alive + +{"access_token":"f779da766bfd1b9164b0fd6d280d52f1","refresh_token":"789f3daf81a302e0636325114113e4b4","token_type":"bearer","expires_in":899} +``` + +#### Where + +- "f779da766bfd1b9164b0fd6d280d52f1" is access token that would be used by PHG when accessing a resource on the server. + +- "789f3daf81a302e0636325114113e4b4" is refresh token which can be used to obtain a new token. +- The token type in the above example is "bearer". +- The lifetime of the token is 899 seconds. +- Requesting a resource using access token of type "bearer". + +### **Example 2:** + +In the example below the PHG uses a bearer token in order to request a protected resource e.g., Questionnaire. + +``` +GET http://localhost:3000/hdata/root.xml HTTP/1.1 +User-Agent: Fiddler +Host: localhost:3000 +Authorization: Bearer f779da766bfd1b9164b0fd6d280d52f1 +``` + +## Appendix IV + +## Consent Enabled PHG Questionnaire response association + +(This appendix does not form an integral part of this Recommendation.) + +**Table IV.1 – The elements of the confidentiality code system** + +| Name | Value | Comments | +|----------------|------------------------|----------| +| Code | "R" | | +| codeSystem | 2.16.840.1.113883.5.25 | | +| codeSystemName | "Confidentiality" | | +| displayName | "Restricted" | | + +**Table IV.2 – The elements of the Continua Consent Directive code system** + +| Name | Value | Comments | +|----------------|------------------------------------------------------------------|----------| +| Code | The value shall be the same as specified by [HL7 CDA IG]. | | +| codeSystem | 2.16.840.1.113883.3.1817
    .1.2.1 | | +| codeSystemName | "Continua Consent Directive" | | +| displayName | ID of the consent document | | + +**Table IV.3 – The translation of the confidentiality code system to the Continua Consent Directive code system** + +| Name | Value | Comments | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| Code | "R" | | +| codeSystem | 2.16.840.1.113883.5.25 | | +| codeSystemName | "Confidentiality" | | +| displayName | "Restricted" | | +| translation | code=""
    codeSystem=2.16.840.1.113883.3.1817.
    .1.2.1
    codeSystemName="Continua Consent
    Directive"
    displayName=ID of the consent
    document | "<>" is a placeholder for the ID of the consent document.
    Consult Table IV.2 for the elements of the Continua Consent Directive code system. | + +**Table IV.4 – OID distribution for Personal Connected Health Alliance** + +| OID | Description | Comments | +|--------------------------------|------------------------------------------------------------------------------|-----------------| +| 2.16.840.1.113883.3.1817 | Organization OID: Personal Connected Health Alliance | | +| 2.16.840.1.113883.3.1817.1 | Root OID for the Continua E2E architecture V1.0 | | +| 2.16.840.1.113883.3.1817.1.2 | Root OID for the E2E Security and Privacy | | +| 2.16.840.1.113883.3.1817.1.3 | Root OID for the Personal Health Device-IF | | +| 2.16.840.1.113883.3.1817.1.4 | Root OID for the ZigBee Personal Health Device-IF | | +| 2.16.840.1.113883.3.1817.1.5 | Root OID for the NFC Personal Health Device-IF | | +| 2.16.840.1.113883.3.1817.1.6 | Root OID for the Services-IF | | +| 2.16.840.1.113883.3.1817.1.7 | Root OID for the HIS-IF | | +| 2.16.840.1.113883.3.1817.1.2.1 | E2E Security and Privacy: OID for the Continua Consent Directive code system | | + +# **Bibliography** + +For a list of non-normative references and publications that contain further background information, see [ITU-T H.810]. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.812.2-201711-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.812.2-201711-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b --- /dev/null +++ b/marked/H/T-REC-H.812.2-201711-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3f7510ab78ce9e9cb2d4e8558b0de5ac645aba1e095a2b999841612076a60c4 +size 4136 diff --git a/marked/H/T-REC-H.812.2-201711-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/H/T-REC-H.812.2-201711-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74637b3cf7d7f685e431830c51df6f6c9ef461c5 --- /dev/null +++ b/marked/H/T-REC-H.812.2-201711-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa432d8673e8c452b7891146855797164e995623f5ae59ae2d75ebd30a7e04f5 +size 119194 diff --git a/marked/H/T-REC-H.812.2-201711-I_PDF-E/raw.md b/marked/H/T-REC-H.812.2-201711-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1e045f35cac245c2fd3bdd237f12b741078f16a2 --- /dev/null +++ b/marked/H/T-REC-H.812.2-201711-I_PDF-E/raw.md @@ -0,0 +1,479 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.812.2** + +(11/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – Personal +health systems + +--- + +**Interoperability design guidelines for personal +connected health systems: +Services interface: Questionnaire capability** + +Recommendation ITU-T H.812.2 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T H.812.2** + +# **Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability** + +## **Summary** + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for personal connected health services. The Continua Design Guidelines also contains design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. + +Patient reported outcome measures (PROMs) are increasingly needed to improve the cost effectiveness and quality of health services. ITU-T H.812.2 defines design guidelines for the Certified Capability Class (CCC) Questionnaire, the function of which is to enable the interoperable exchange of PROMs (also known as Questionnaires) across the Services-IF of the Continua end-to-end architecture. + +The Questionnaires are represented according to the HL7 Implementation Guide (IG) for the CDA R2 Questionnaire Form Definition (QFD) document [HL7 CDA QFD]. The QFD document captures the health survey questions or question sets to be administered to a patient. The QFD document enables the definition of questions for surveying the patients' perception on their health and the impact that any treatments or adjustments to lifestyle have had on their quality of life. QFD documents may carry a variety of clinical and non-clinical questions and branching logic in order to present the patient with a dynamic health survey for assessing health status including, but not limited to, the patient's functional, cognitive and physiological characteristics. Authors of the QFD documents may include information about disease management organizations, primary care physicians, health and fitness coaches, chronic condition monitors and post-acute and long-term care organizations. + +The response to a Questionnaire is then represented according to the HL7 Implementation Guide (IG) for the CDA R2 Questionnaire Response (QR) document [HL7 CDA QRD]. Authors of the QR documents may include the patients who are under the care of disease management organizations, primary care physicians, health and fitness coaches, chronic condition monitors and post-acute and long-term care providers or their agents. + +For the exchange of QFD and QR documents, this design guidelines document specifies and profiles the use of the HL7 hData record format and OMG hData REST Binding for RLUS. For security, this design guidelines document further profiles the use of OAuth 2.0 and TLS v1.1. + +ITU-T H.812.2 is part of the "ITU-T H.810 interoperability design guidelines for personal connected health systems" subseries, that covers the following areas: + +- ITU-T H.810 – Interoperability design guidelines for personal connected health systems: Introduction +- ITU-T H.811 – Interoperability design guidelines for personal connected health systems: Personal Health Devices interface +- ITU-T H.812 – Interoperability design guidelines for personal connected health systems: Services interface +- ITU-T H.812.1 – Interoperability design guidelines for personal connected health systems: Services interface: Observation Upload capability +- ITU-T H.812.2 – Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability (this design guidelines document) +- ITU-T H.812.3 – Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability +- ITU-T H.812.4 – Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability +- ITU-T H.813 – Interoperability design guidelines for personal connected health systems: Healthcare Information System interface + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|------------------------------------| +| 1.0 | ITU-T H.812.2 | 2015-11-29 | 16 | 11.1002/1000/12655 | +| 2.0 | ITU-T H.812.2 | 2016-07-14 | 16 | 11.1002/1000/12915 | +| 3.0 | ITU-T H.812.2 | 2017-11-29 | 16 | 11.1002/1000/13417 | + +## Keywords + +CDG, Continua Design Guidelines, healthcare information systems, personal connected health systems, personal health devices, questionnaire capability, services + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-----|---------------------------------------------------------------------------|-----| +| 0 | Introduction..... | vi | +| 0.1 | Organization ..... | vi | +| 0.2 | CCC guideline releases and versioning ..... | vii | +| 0.3 | What's new..... | vii | +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations and acronyms ..... | 1 | +| 5 | Conventions ..... | 1 | +| 6 | Use cases..... | 1 | +| 6.1 | Retrieve a list of Questionnaires to-be-completed by a patient..... | 1 | +| 6.2 | Retrieve a specific Questionnaire and let the patient fill it in ..... | 2 | +| 6.3 | Upload the completed Questionnaire to the patient record ..... | 2 | +| 6.4 | Retrieve a list of completed Questionnaires from the patient record ..... | 2 | +| 6.5 | Retrieve a specific Questionnaire response from the server ..... | 2 | +| 7 | Behavioural models ..... | 2 | +| 8 | Implementation ..... | 3 | +| 8.1 | Content representation..... | 3 | +| 8.2 | Transport protocol ..... | 4 | +| | Annex A Normative guidelines..... | 5 | +| | Appendix I ATOM feed information elements..... | 9 | +| I.1 | Information for Questionnaire in the root.xml ..... | 10 | +| I.2 | Information for Questionnaire response in the root.xml ..... | 11 | +| | Bibliography..... | 12 | + +## **List of Tables** + +| | Page | +|------------------------------------------------------------------------------------------|-------------| +| Table A.1 – Normative guidelines for Questionnaire-enabled PHG ..... | 5 | +| Table A.2 – Normative guidelines for Questionnaire-enabled Health & Fitness service..... | 7 | +| Table I.1 – ATOM feed child elements for Questionnaires..... | 9 | +| Table I.2 – ATOM feed child elements for Questionnaire responses..... | 10 | + +## **List of Figures** + +| | Page | +|----------------------------------------------------------------------------------------------------------------|-------------| +| Figure 7-1 – Transactions between a PHG and a Health & Fitness service related to Questionnaire use cases..... | 3 | + +# 0 Introduction + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for applications monitoring personal connected health services. The CDG also contains design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. + +Patient reported outcome measures (PROMs) are increasingly needed to improve the cost effectiveness and quality of health services. This design guidelines document defines design guidelines for the Questionnaire Certified Capability Class (CCC), the function of which is to enable the interoperable exchange of PROMs (also known as Questionnaires) across the Services-IF of the Continua end-to-end architecture. + +The Questionnaires are represented according to the HL7 Implementation Guide (IG) for the CDA R2 Questionnaire Form Definition (QFD) document [HL7 CDA QFD]. The QFD document captures the health survey questions or question sets to be administered to a patient. The QFD document enables the definition of questions for surveying the patients' perception on their health and the impact that any treatments or adjustments to lifestyle have had on their quality of life. QFD documents may carry a variety of clinical and non-clinical questions and branching logic in order to present the patient with a dynamic health survey for assessing health status including, but not limited to, the patient's functional, cognitive and physiological characteristics. Authors of the QFD documents may include information about disease management organizations, primary care physicians, health and fitness coaches, chronic condition monitors, and post-acute and long-term care organizations. + +The response to a Questionnaire is then represented according to the HL7 Implementation Guide (IG) for the CDA R2 Questionnaire Response (QR) document [HL7 CDA QRD]. Authors of the QR documents may include the patients who are under the care of disease management organizations, primary care physicians, health and fitness coaches, chronic condition monitors and post-acute and long-term care providers or their agents. + +For the exchange of QFD and QR documents, this design guidelines document specifies and profiles the use of the HL7 hData record format and OMG hData REST Binding for the retrieve, locate and update service (RLUS). For security, this design guidelines document further profiles the use of OAuth 2.0 and TLS v1.1. + +This design guidelines document is part of the "H.810 interoperability design guidelines for personal health systems" subseries. See [ITU-T H.810] for more details. + +## 0.1 Organization + +This design guidelines document is organized in the following manner. + +**Clauses 0 to 5: Introduction and terminology** – These clauses provide overview information which help to understand the structure of the design specifications. + +**Clause 6: Use cases** – This clause provides practical use cases for the Questionnaire Certified Capability Class (CCC) specified in this design guidelines document. + +**Clause 7: Behavioural models** – This clause provides an overview of interactions between Personal Health Gateways (PHGs) and Health & Fitness services that are specified by the Questionnaire CCC. + +**Clause 8: Implementation** – This clause provides implementation specific details for the Questionnaire CCC. + +### **Annex A:** + +**Normative** guidelines – This annex specifies the normative requirements that must be followed by the Questionnaire CCC. + +## **0.2            CCC guideline releases and versioning** + +See clause 0.2 of [ITU-T H.810] for release and versioning information. + +## **0.3            What's new** + +To see what is new in this release of the design guidelines, refer to clause 0.3 of [ITU-T H.810]. + + + +# Recommendation ITU-T H.812.2 + +# Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability + +# 1 Scope + +This design guidelines document specifies the design guidelines for the Questionnaire enabled PHG and Questionnaire enabled services CCCs. The design guidelines specify the testable requirements that must be implemented by the PHG in order to classify it as a Questionnaire enabled PHG. The Questionnaire enabled PHG shall be able to retrieve Questionnaires from the Health & Fitness service and shall be able to validate that those Questionnaires conform to the HL7 CDA R2 IG for QFD documents [HL7 CDA QFD]. In addition, the design guidelines specify testable requirements for a Health & Fitness service which details how a Questionnaire enabled Health & Fitness service shall respond to the requests from a Questionnaire enabled PHG and shall be able to validate that the QR documents conform to the HL7 CDA R2 IG for QR documents [HL7 CDA QFD]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.810] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal connected health systems: Introduction*. + +All other referenced documents can be found in clause 2 of [ITU-T H.810]. + +# 3 Definitions + +This design guidelines document uses terms defined in [ITU-T H.810]. + +## 4 Abbreviations and acronyms + +This design guidelines document uses abbreviations and acronyms defined in [ITU-T H.810]. + +## 5 Conventions + +This design guidelines document follows the conventions defined in [ITU-T H.810]. + +# 6 Use cases + +The use cases below are focused on the needs identified for retrieving Questionnaires and posting Questionnaire responses by patients. + +### 6.1 Retrieve a list of Questionnaires to-be-completed by a patient + +Adam Everyman has heart failure and has recently been hospitalized for a decompensation event. As part of the discharge from the hospital he was enrolled in a telehealth programme that monitors his vitals at home and asks him regularly to provide subjective information about his condition. + +The telehealth hub that is installed in Adam's home will regularly check with the telehealth server if there are any new Questionnaires that Adam should fill in. When a Questionnaire is scheduled for Adam by his care provider the telehealth hub will download the information about the + +Questionnaire, including the due date for completing it and a short message from Adam's care provider explaining what the Questionnaire is for and who he can call in case of questions. The telehealth hub then shows on the start screen that a new Questionnaire is available and when it is due for and also enables Adam to check the note from his care provider related to this Questionnaire. + +### **6.2 Retrieve a specific Questionnaire and let the patient fill it in** + +When Adam checks his telehealth hub in the morning he sees that there is a new Questionnaire that he is asked to complete. The hub tells him that the Questionnaire is about his heart failure symptoms and it also shows a brief note from his heart failure nurse where she writes that she hopes he has slept well and asks him to complete this symptom Questionnaire preferably before lunch time. She also tells him to give her a call directly in case his symptoms are worse than normal. + +Adam grabs a cup of tea and starts the Questionnaire. He knows the Questionnaire well as he is asked to fill in this Questionnaire once per week. It asks about any signs of breathlessness or swelling that could signal a worsening of his heart failure. Luckily Adam feels pretty good and he can answer the questions by indicating that he has no problematic symptoms at this moment. + +### **6.3 Upload the completed Questionnaire to the patient record** + +Adam finishes answering the questions in the Questionnaire and hits the "submit" button on his telehealth hub. The hub compiles his answers into a Questionnaire response document and posts the document to Adam's health record at the telehealth server. The server analyses Adam's responses and determines that there are no problematic symptoms at this moment so there is no need to alert Adam's heart failure nurse. She can still review his answers if she would like to do so, for instance before she calls him for a regular check-up. + +As Adam has now completed the Questionnaire, the server will also remove this specific Questionnaire from the list of Questionnaires to-be-completed by Adam. The next time Adam's telehealth hub checks with the server for Questionnaires to-be-completed it will not find this Questionnaire in the to-do list anymore. + +### **6.4 Retrieve a list of completed Questionnaires from the patient record** + +As all completed Questionnaires by Adam are stored in his health record at the telehealth server he can also see a list of all the Questionnaires he has completed on his telehealth hub. This can be useful for him to be able to look back how he answered the symptom Questionnaire a few weeks ago or review other Questionnaires he has completed. + +### **6.5 Retrieve a specific Questionnaire response from the server** + +Adam may want to look back on how he answered the symptom Questionnaire a few weeks ago or review other Questionnaires he has completed. He can also see a brief description of each completed Questionnaire (title, description, link, etc.) on his telehealth hub, hence he clicks on the link and the telehealth hub then retrieves the completed Questionnaire response from the server. + +## **7 Behavioural models** + +The following exchange mechanisms are specified for Questionnaires and Questionnaire responses: + +- Retrieve a list of Questionnaires to-be-completed from the server. +- Retrieve a specific Questionnaire from the server. +- Create a new Questionnaire response on the server. +- Retrieve a list of completed Questionnaire responses from the server. +- Retrieve a specific Questionnaire response from the server. + +Creating a to-be completed Questionnaire on the server is not defined in this design guidelines document as that is currently seen as taking place outside of this Questionnaire service and the Continua E2E architecture. + +Figure 7-1 illustrates transactions related to the Questionnaire use cases mentioned in this content profile. + +![Sequence diagram showing transactions between Patient (Adam), Questionnaire client, and Questionnaire server. The diagram is divided into three vertical lifelines. The Patient (Adam) lifeline is on the left, labeled 'Out of scope' at the bottom. The Questionnaire client lifeline is in the middle, labeled 'PHG application' at the bottom. The Questionnaire server lifeline is on the right, labeled 'Services application' at the bottom. The sequence of messages is: 1. Retrieve list of questionnaires to be completed (client to server), 2. Atom feed containing list of questionnaires to be completed (server to client), 3. Retrieve questionnaire document (client to server), 4. Questionnaire document (server to client), 5. Questionnaire presentation (client to patient), 6. Response information (patient to client), 7. Upload completed questionnaire document (client to server), 8. Resource created (server to client), 9. Retrieve list of completed questionnaires (client to server), 10. Atom feed containing list of completed questionnaires (server to client), 11. Retrieve questionnaire response document (client to server), 12. Questionnaire response document (server to client), 13. Review response document (client to patient). The diagram is labeled H.812.2(16)_F7-1 at the bottom right.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +Sequence diagram showing transactions between Patient (Adam), Questionnaire client, and Questionnaire server. The diagram is divided into three vertical lifelines. The Patient (Adam) lifeline is on the left, labeled 'Out of scope' at the bottom. The Questionnaire client lifeline is in the middle, labeled 'PHG application' at the bottom. The Questionnaire server lifeline is on the right, labeled 'Services application' at the bottom. The sequence of messages is: 1. Retrieve list of questionnaires to be completed (client to server), 2. Atom feed containing list of questionnaires to be completed (server to client), 3. Retrieve questionnaire document (client to server), 4. Questionnaire document (server to client), 5. Questionnaire presentation (client to patient), 6. Response information (patient to client), 7. Upload completed questionnaire document (client to server), 8. Resource created (server to client), 9. Retrieve list of completed questionnaires (client to server), 10. Atom feed containing list of completed questionnaires (server to client), 11. Retrieve questionnaire response document (client to server), 12. Questionnaire response document (server to client), 13. Review response document (client to patient). The diagram is labeled H.812.2(16)\_F7-1 at the bottom right. + +**Figure 7-1 – Transactions between a PHG and a Health & Fitness service related to Questionnaire use cases** + +## 8 Implementation + +### 8.1 Content representation + +The Questionnaire and Questionnaire response content is represented according to the following HL7 standards: + +- *HL7 Implementation Guide for CDA Release 2.0: Questionnaire Form Definition Document, Release 1 [HL7 CDA QFD]* +- *HL7 Implementation Guide for CDA Release 2.0: Questionnaire Response Document, Release 1 [HL7 CDA QRD]* + +The sample files for Questionnaire and Questionnaire response documents can be found in the submission packages for the above-mentioned standards. + +### **8.2 Transport protocol** + +The Questionnaire-enabled PHG and Health & Fitness services uses hData over HTTP as a transport protocol for the exchange of Questionnaire and Questionnaire response documents across the Services-IF. For the detailed requirements on the use of hData over HTTP protocol between PHG and Health & Fitness services consult Annex A. + +## Annex A + +### Normative guidelines + +(This annex forms an integral part of this Recommendation.) + +**Table A.1 – Normative guidelines for Questionnaire-enabled PHG** + +| Name | Description | Comments | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Questionnaire_AHD_Content_Standard | Questionnaire enabled PHG shall comply to the following standards for the representation of Questionnaire and Questionnaire response:
    • – Questionnaire Form Definition Document [HL7 CDA QFD]
    • – Questionnaire Response Document [HL7 CDA QRD]
    | | +| Questionnaire-PHG-Transport-Standards | Questionnaire enabled PHG shall comply to the following transport standards:
    HL7 Version 3 Specification: hData Record Format, Release 1 [HL7 V3 HRF]
    OMG hData REST Binding for RLUS [OMG/hData BIND]
    OMG Retrieve, Locate, and Update Service (RLUS) Specification 1.0.1 [OMG/hData RLUS] | | +| PHG-Retrieve-List-Questionnaire | Questionnaire enabled PHG shall use HTTP GET with the following URL for retrieving a to-be-completed Questionnaire's list from the Health & Fitness service:
    baseURL/continua/questionnaire | See the use case in clause 6.1. For RLUS hData over REST transport, this is performed by performing an HTTP GET request without query parameters at the URL representing the patient's Questionnaire hData root section path. | +| PHG-Questionnaire-dueDate | The Atom entry element shall contain the dueDate extension element in the Continua namespace, the content of which shall conform to the "date-time" production in [IETF RFC 3339]. | dueDate is used to indicate a precise moment in time before which the patient must complete the Questionnaire.
    For further information on this element and content of the Atom feed entry element, consult Table I.1 | +| PHG-Retrieve-Specific-Questionnaire | Questionnaire enabled PHG shall use the link element from the Atom feed entry to retrieve the actual Questionnaire document and shall validate that it is a valid HL7 CDA R2 QFD document. | See the use case in clause 6.2. An example of the URL of a Questionnaire that is in the Questionnaire section of the hData record:
    baseURL/continua/questionnaire/e | + +**Table A.1 – Normative guidelines for Questionnaire-enabled PHG** + +| Name | Description | Comments | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | |

    example.xml

    For RLUS hData over REST transport, this is performed by performing an HTTP GET request without query parameters at this URL to retrieve the questionnaire document.

    | +| PHG-Post-Questionnaire-Response |

    Questionnaire enabled PHG shall use HTTP POST with the following URL for posting questionnaire response to the Health & Fitness service:
    baseURL/continua/questionnaireResponse

    |

    See the use case in clause 6.3.

    | +| PHG-Retrieve-List-Questionnaire-Response |

    Questionnaire enabled PHG shall use the following URL for retrieving completed questionnaires list from the Health & Fitness service:
    baseURL/continua/questionnaireResponse

    |

    See the use case in clause 6.4.

    For RLUS hData over REST transport, this is performed by performing an HTTP GET request without query parameters at the URL representing the patient's questionnaire response hData path.

    | +| PHG-Retrieve-Specific-Questionnaire-Response |

    Questionnaire enabled PHG shall use the link element from the Atom feed entry to retrieve the actual Questionnaire response document and shall validate that it is a valid HL7 CDA R2 QR document.

    |

    See the use case in clause 6.5.

    For further information on Atom feed entry element consult Table I.2.

    As a result of PHG-Retrieve-Questionnaire-Response, Questionnaire Enabled PHG receives ATOM feed.

    An example of the URL of a Questionnaire response that is in the Questionnaire response section of the hData record:
    baseURL/continua/questionnaireResponse/abc123.xml

    For RLUS hData over REST transport, this is performed by performing an HTTP GET request without query parameters at this URL to retrieve the Questionnaire response document.

    | + +**Table A.2 – Normative guidelines for Questionnaire-enabled Health & Fitness service** + +| Name | Description | Comments | +|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Services-Questionnaire-Content-Standard |

    Questionnaire enabled Health & Fitness service shall comply to the following standards for the representation of Questionnaire and Questionnaire response:

    • – Questionnaire Form Definition Document [HL7 CDA QFD]
    • – Questionnaire Response Document [HL7 CDA QRD]
    | | +| Services-Questionnaire-Transport-Standards |

    Questionnaire enabled Health & Fitness service shall comply to the following transport standards:

    • – HL7 Version 3 Specification: hData Record Format, Release 1 [HL7 V3 HRF]
    • – OMG hData REST Binding for RLUS [OMG/hData BIND]
    • – OMG Retrieve, Locate, and Update Service (RLUS) Specification 1.0.1 [OMG/hData RLUS]
    | | +| Services-Questionnaire-Root |

    Questionnaire enabled Health & Fitness service shall include the following elements for Questionnaire content in the root.xml file:

    1. 1.profile
      1. a. id="questionnaire"
      2. b. reference="http://handle.itu.int/11.1002/3000/hData/Questionnaire/2017/01/H.812.2.pdf"
    2. 2.section
      1. a. path=" questionnaires"
      2. b. profileID= "questionnaire"
      3. c. resourceTypeID= "questionnaire"
    3. 3.resourceType
      1. a. resourceTypeID= "questionnaire"
      2. b. reference="http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=116"
      3. c. representation
        1. i. mediaType="application/xml"
    | | +| Services-Questionnaire-Response-Root |

    Questionnaire enabled Health & Fitness service shall include the following elements for Questionnaire response content in the root.xml file:

    1. 1.profile
      1. a. id="questionnaireResponse"
      2. b. reference="http://handle.itu.int/11.1002/3000/hData/Questionnaire/2017/01/H.812.2.pdf"
    2. 2.section
      1. a. path="questionnaireResponses"
      2. b. profileID="questionnaireResponse"
      3. c. resourceTypeID="questionnaireResponse"
    3. 3.resourceType
      1. a. resourceTypeID="questionnaireResponse"
      2. b. reference="http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=117"
      3. c. representation
        1. i. mediaType="application/xml"
    | | + +**Table A.2 – Normative guidelines for Questionnaire-enabled Health & Fitness service** + +| Name | Description | Comments | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Services-Questionnaire-Response-Validate | Questionnaire enabled Health & Fitness service shall validate the Questionnaire response document that it is a valid HL7 CDAR2 Questionnaire response document and send the HTTP 201 as a response if it is a valid document. | | +| Services-Creation-Questionnaire | Questionnaire enabled Health & Fitness service shall not support the creation of new Questionnaire record via the hData interface and shall return HTTP 405 Method Not Allowed as a response to HTTP POST request on Questionnaire section path. | One record covers a single Questionnaire or Questionnaire response document. For the creation of a new Questionnaire response document consult PHG-Post-Questionnaire-Response guideline. | +| Services-Modification-Questionnaire-Response | Questionnaire enabled Health & Fitness service shall not support the modification of an existing Questionnaire or Questionnaire response record and shall return HTTP 405 Method Not Allowed as a response to HTTP PUT request on Questionnaire or Questionnaire response section path. | | +| PHG-Delete-Questionnaire-Response | Questionnaire enabled Health & Fitness service shall not support the deletion of an existing Questionnaire or Questionnaire response record and shall return HTTP 405 Method Not Allowed as a response to HTTP DELETE request on Questionnaire or Questionnaire response section path. | | + +## Appendix I + +### ATOM feed information elements + +(This appendix does not form an integral part of this Recommendation.) + +The following ATOM feed child elements of the entry element have a specific usage for the purpose of Questionnaires. + +**Table I.1 – ATOM feed child elements for Questionnaires** + +| Element | Usage | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| author | Person construct that indicates the person who requested that the patient complete this Questionnaire. | +| Id | Must be a globally unique identifier, which must be included in the Questionnaire response document (InFulfillmentOf field) that is created upon completing the referenced Questionnaire, so that the server knows the relationship between the request to complete the Questionnaire document and the posted Questionnaire response document. | +| Title | Title of the Questionnaire. | +| Summary | More detailed statement on the request to complete this Questionnaire, e.g.
    "Dear Mr. Everyman,
    Could you complete this survey on heart failure symptoms before lunch time?
    In case your symptoms are worse than normal, please call me directly.
    Have a nice day.
    Best regards,
    Nurse Betty" | +| link | Reference to the Questionnaire document which must be a valid HL7 CDAR2 Form Definition IG document.
    The link can be relative if the Questionnaire can be retrieved via the Questionnaire section of the hData record, but it can also be an absolute link if the Questionnaire is located outside of the current hData record, e.g., at https://www.example.org/surveys/QoL.xml | +| dueDate | This element is not part of the normal atom namespace and is an extension in the CDG for a Questionnaire use case. It is used to contain the due date for completing the Questionnaire by the patient and can be used by the SC to convey a sense of urgency to the patient. The content shall conform to the "date-time" production in [IETF RFC 3339]. In addition, an uppercase "T" character shall be used to separate date and time, and an uppercase "Z" character shall be present in the absence of a numeric time zone offset.
    The dueDate element is defined in the Continua namespace. The atom:entry element in "The Atom Syndication Format" schema shall then refer to the dueDate element in the following way:
    <xs:element ref="continua:dueDate" minOccurs="1" maxOccurs="1"/>
    The schema for defining the continua:dueDate element shall then contain the following statement:
    <xs:element name="dueDate" type="atom:dateTimeType"/>
    The content of the dueDate is represented in the same manner as date-time is | + +**Table I.1 – ATOM feed child elements for Questionnaires** + +| Element | Usage | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| | represented in "The Atom Syndication Format" schema. As an example consult the "The Atom Syndication Format" schema defined here [b-ATOM Schema]. | + +The following ATOM feed child elements of the entry element have a specific usage for the purpose of Questionnaire responses. + +**Table I.2 – ATOM feed child elements for Questionnaire responses** + +| Element | Usage | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| author | Person construct that indicates who provided the information in the Questionnaire response i.e. who completed the Questionnaire. | +| Title | Title of the original Questionnaire to which this Questionnaire response belongs. | +| Link | Reference to the Questionnaire response document which must be a valid HL7 CDAR2 Questionnaire Response IG document.
    The link shall be relative and the Questionnaire response document shall be in the Questionnaire response section of the hData record. | +| Published | The published element shall be set to the data/time at which the Questionnaire response document was posted to the server. | + +### I.1 Information for Questionnaire in the root.xml + +``` + + questionnaire + +http://handle.itu.int/11.1002/3000/hData/Questionnaire/2017/01/H.812.2.pdf + + +
    + questionnaires + questionnaire + questionnaire +
    + + questionnaire + +http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=116 + + application/xml + + +``` + +### I.2 Information for Questionnaire response in the root.xml + +``` + + questionnaireResponse + +http://handle.itu.int/11.1002/3000/hData/Questionnaire/2017/01/H.812.2.pdf + +
    + questionnaireResponses + questionnaireResponse + questionnaireResponse +
    + + questionnaireResponse + +http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=117 + + application/xml + + +``` + +## **Bibliography** + +For a list of non-normative references and publications that contain further background information, see [ITU-T H.810]. + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.812.3-201711-I_PDF-E/raw.md b/marked/H/T-REC-H.812.3-201711-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3f907279e68055a88b6241cc9a155d12e0ca1370 --- /dev/null +++ b/marked/H/T-REC-H.812.3-201711-I_PDF-E/raw.md @@ -0,0 +1,713 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.812.3** + +(11/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – Personal +health systems + +--- + +**Interoperability design guidelines for personal +connected health systems: +Services interface: Capability Exchange +capability** + +Recommendation ITU-T H.812.3 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T H.812.3** + +# **Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability** + +## **Summary** + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for personal connected health services. The Continua Design Guidelines also contains design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. + +ITU-T H.812.3 defines the additional design guidelines for the Capability Exchange-enabled Personal Health Gateway (PHG) and Health & Fitness services Certified Capability Class (CCC). The purpose of the Capability Exchange is to reduce the amount of information that must be pre-configured on a device in order to obtain plug and play interoperability. Specifically, Capability Exchange enables application hosting devices, such as a Personal Health Gateway (PHG) to know what types of messages it can send to the Health & Fitness services, by identifying its Continua CCCs. Likewise, Capability Exchange provides a mechanism for the PHG to inform the Health & Fitness services of its capabilities. This enables the Health & Fitness services to tailor its communication with the PHG. Capability Exchange is mandatory for all Health & Fitness services while it is optional for PHGs. + +It is assumed that the PHG is pre-provisioned with a URL, or a set of URLs, denoting the service endpoint of one or more Health & Fitness services. The Capability Exchange process takes place when the PHG first contacts the Health & Fitness services. It may also take place intermittently, to update the information received in the first Capability Exchange. In most cases, the set of Continua CCCs implemented at the Health & Fitness services changes slowly, if at all. Therefore, it is expected that the PHG can store the information about services capabilities and optionally, implement a policy for periodically updating that cache. A PHG might identify several Health & Fitness services in this way and communicate with one or more of these for different purposes. + +The Health & Fitness service describes the information about its supported CCCs in a file called "root file". The root file is a special resource that describes the properties of CCCs and how a PHG can start information exchange with these CCCs. The root file and other features of the exchange come from an HL7 standard called hData. hData not only defines the root file format, but also defines the operations for exchanging root files, using HTTP using GET and POST operations, often referred to as "REST" (for representational state transfer). + +Each Continua CCC (in addition to the Capability Exchange capability) will use the root file to document information relevant to that capability, including the capability name, the information that can be exchanged under the capability and its format and URLs for REST operations, if supported by that capability. Details are given in the documentation for the respective Continua CCCs. + +ITU-T H.812.3 is part of the "ITU-T H.810 interoperability design guidelines for personal connected health systems" subseries that covers the following areas: + +- ITU-T H.810 – Interoperability design guidelines for personal connected health systems: +Introduction +- ITU-T H.811 – Interoperability design guidelines for personal connected health systems: +Personal Health Devices interface +- ITU-T H.812 – Interoperability design guidelines for personal connected health systems: +Services interface + +- ITU-T H.812.1 – Interoperability design guidelines for personal connected health systems: Services interface: Observation Upload capability +- ITU-T H.812.2 – Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability +- ITU-T H.812.3 – Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability (this design guidelines document) +- ITU-T H.812.4 – Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability +- ITU-T H.813 – Interoperability design guidelines for personal connected health systems: Healthcare Information System interface design guidelines + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.812.3 | 2015-11-29 | 16 | 11.1002/1000/12656 | +| 2.0 | ITU-T H.812.3 | 2016-07-14 | 16 | 11.1002/1000/12916 | +| 3.0 | ITU-T H.812.3 | 2017-11-29 | 16 | 11.1002/1000/13418 | + +## Keywords + +CDG, Continua Design Guidelines, capability exchange, healthcare information systems, personal connected health systems, personal health devices, services. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-----|------------------------------------------------------------------|-----| +| 0 | Introduction..... | vi | +| 0.1 | Organization ..... | vi | +| 0.2 | Guideline releases and versioning ..... | vii | +| 0.3 | What's new..... | vii | +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations and acronyms ..... | 1 | +| 5 | Conventions ..... | 1 | +| 6 | Use cases..... | 1 | +| 6.1 | PHG obtains Health & Fitness services information..... | 1 | +| 6.2 | Health & Fitness services receive PHG information..... | 2 | +| 7 | Behavioural models ..... | 2 | +| 8 | Implementation ..... | 3 | +| 8.1 | Overview ..... | 3 | +| 8.2 | Root file exchange ..... | 3 | +| 8.3 | Contents of the root file ..... | 4 | +| 8.4 | Optional JSON version of root file..... | 5 | +| | Annex A Normative guidelines..... | 6 | +| | Appendix I Root file inclusions for Capability Exchange ..... | 10 | +| I.1 | Required root file inclusions for Health & Fitness services..... | 10 | +| I.2 | Schema for the root.xml ..... | 10 | +| I.3 | Required root file inclusions for PHG..... | 12 | +| | Appendix II hData..... | 13 | +| | Bibliography..... | 16 | + +## **List of Tables** + +| | Page | +|----------------------------------------------------------------------|-------------| +| Table A.1 – Normative guidelines for Health & Fitness services ..... | 6 | +| Table A.2 – Normative guidelines for PHG device ..... | 9 | +| Table II.1 – Types of operations ..... | 14 | + +## **List of Figures** + +| | Page | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Figure 7-1 – Transactions between PHG and Health & Fitness services related to root file exchange for determining the capabilities of the Health & Fitness service and the PHG ..... | 2 | +| Figure II.1 – hData interoperability framework ..... | 15 | + +# 0 Introduction + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for personal connected health services. The Continua Design Guidelines also contains additional design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. + +This design guidelines document defines the additional design guidelines for the Capability Exchange-enabled Personal Health Gateway (PHG) and Health & Fitness service Certified Capability Class (CCC). The purpose of the Capability Exchange is to reduce the amount of information that must be pre-configured on a device in order to obtain plug and play interoperability. Specifically, Capability Exchange enables a PHG to know what types of messages it can send to the Health & Fitness service, by identifying its Continua CCCs. Likewise, Capability Exchange provides a mechanism for the PHG to inform the Health & Fitness service of its capabilities. This enables the Health & Fitness service to tailor its communication with the PHG. Capability Exchange is mandatory for all Health & Fitness services while it is optional for PHGs. + +It is assumed that the PHG is pre-provisioned with a URL, or a set of URLs, denoting the service endpoint of one or more Health & Fitness services. The Capability Exchange process takes place when the PHG first contacts the Health & Fitness services. It may also take place intermittently, to update the information received in the first Capability Exchange. In most cases, the set of Continua CCCs implemented at a Health & Fitness service changes slowly, if at all. Therefore, it is expected that the PHG can store the information about services capabilities and optionally, implement a policy for periodically updating that cache. A PHG might identify several Health & Fitness services in this way and communicate with one or more for different purposes. + +The Health & Fitness services describes the information about its supported CCCs in a file called "root file". The root file is a special resource that describes the properties of CCCs and how a PHG can start information exchange with those CCCs. The root file and other features of the exchange come from an HL7 standard called hData [HL7 V3 HRF], [OMG/hData RESTful Trans]. hData not only defines the root file format, but also defines the operations for exchanging root files, using HTTP using GET and POST operations, often referred to as "REST" (for representational state transfer). + +Each Continua CCC (in addition to Capability Exchange capability) will use the root file to document information relevant to that capability, including the capability name, the information that can be exchanged under the capability and its format and URLs for REST operations, if supported by that capability. Details are given in the documentation for the respective Continua CCCs. + +This design guidelines document is part of the "ITU-T H.810 interoperability design guidelines for personal health systems" subseries. See [ITU-T H.810] for more details. + +## 0.1 Organization + +This design guidelines document is organized in the following manner: + +**Clauses 0 to 5: Introduction and terminology** – These clauses provide useful background information to help understand the structure of the design specifications. + +**Clause 6: Use cases** – This clause provides practical examples. + +**Clause 7: Behavioural model** – This clause is an overview of sequences of interactions and summarizes typical iterations, constraints and exceptions. + +**Clause 8: Implementation guidance** – This clause provides an informative description of the implementation of the Capability Exchange CCC. + +**Annex A: Normative guidelines** – This clause specifies the normative requirements that must be followed by the Capability Exchange CCC. + +## **0.2            Guideline releases and versioning** + +See clause 0.2 of [ITU-T H.810] for release and versioning information. + +## **0.3            What's new** + +To see what is new in this release of the design guidelines refer to clause 0.3 of [ITU-T H.810]. + + + +# **Recommendation ITU-T H.812.3** + +# **Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability** + +# **1 Scope** + +This design guidelines document specifies design guidelines for the Capability Exchange-enabled PHG and Capability Exchange-enabled services CCCs. The design guidelines specify the testable requirements that must be implemented by the PHG in order to classify it as a Capability Exchange-enabled PHG. The Capability Exchange-enabled PHG shall be able to retrieve a root file from the Health & Fitness services and be able to validate that the root file conforms to the HL7 hData hRF document. In addition, the design guidelines specify testable requirements for Health & Fitness services which detail how Capability Exchange-enabled Health & Fitness services shall respond to the requests from a Capability Exchange-enabled PHG and shall be able to validate that the root document conforms to the HL7 hData hRF document. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.810] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal connected health systems: Introduction*. + +All other referenced documents can be found in clause 2 of [ITU-T H.810]. + +# **3 Definitions** + +This design guidelines document uses terms defined in [ITU-T H.810]. + +## **4 Abbreviations and acronyms** + +This design guidelines document uses abbreviations and acronyms defined in [ITU-T H.810]. + +# **5 Conventions** + +This design guidelines document follows the conventions defined in [ITU-T H.810]. + +# **6 Use cases** + +The use cases below are focused on the needs identified for Capability Exchange. + +## **6.1 PHG obtains Health & Fitness services information** + +Outpatient Adam Everyman is provided with health measurement devices that interact wirelessly with a smart phone application (the PHG). Adam's health practitioner provides a URL in the form of a QR Code (for example) that can be scanned by the smart phone application during the configuration process, directing the PHG to the disease management organization (DMO), a remote monitoring site. The DMO remotely monitors patients at home and collects health information from health measurement devices installed at Adam's home. During configuration, the smart phone application (the PHG) contacts the URL and downloads an XML file (the "root file") containing + +information about the DMO's services. By parsing the root file, the PHG determines the Continua CCCs supported by the DMO. In this case, the DMO can receive Observation Uploads and Questionnaires using RESTful HTTP and can participate in authenticated persistent sessions. + +## 6.2 Health & Fitness services receive PHG information + +Having discovered that the DMO can support authenticated persistent sessions, the smart phone application (the PHG) now wants to inform the DMO that it also has the capability of supporting authenticated persistent sessions. To do so, the PHG must first authenticate with the DMO. After authentication, the PHG may use an HTTP POST operation to send its root file (which is different to the DMO root file) to the DMO, using the designated URL supplied in the DMO's root file. The PHG's root file contains information on the PHG's capabilities, including the fact that the PHG can support authenticated persistent sessions. If the PHG subsequently initiates an authenticated persistent session with the Health & Fitness services, the Health & Fitness services will use the information in the PHG's root file to send unsolicited commands to the PHG. + +# 7 Behavioural models + +The following exchange mechanisms are specified for the Capability Exchange service: + +- the PHG retrieves the Health & Fitness service root file from the Health & Fitness service; +- the PHG sends its root file to the Health & Fitness service. + +Figure 7-1 illustrates transactions related to the Capability Exchange use cases described in clause 6. + +![Sequence diagram showing transactions between PHG and Health and fitness service for root file exchange.](853f59c89931a666c07903b31d098277_img.jpg) + +``` +sequenceDiagram + participant PHG + participant HFS as Health and fitness service + Note left of PHG: Base URL of Health and fitness service is pre-provisioned + PHG->>HFS: HTTP GET of root.xml using TLS v1.1 and optionally OAuth v2.0 bearer token + HFS-->>PHG: root.xml of Health and fitness service + Note left of PHG: PHG determines CCDCs supported by parsing the Health and fitness service root file + Note left of PHG: PHG may POST its root file to location identified from base URL and path element in Health and fitness service root file. + PHG->>HFS: HTTP POST of root.xml using TLS v1.1 and OAuth v2.0 bearer token + HFS-->>PHG: HTTP response +``` + +The diagram illustrates the interaction between the PHG and the Health and fitness service. It begins with a note indicating that the base URL of the Health and fitness service is pre-provisioned. The PHG sends an HTTP GET request for root.xml to the service, which responds with the root.xml file. The PHG then parses this file to determine the supported CCDCs. Next, the PHG sends an HTTP POST request of its own root.xml file to the service, which responds with an HTTP response. The diagram is labeled H.812.3(17)\_F7-1. + +Sequence diagram showing transactions between PHG and Health and fitness service for root file exchange. + +**Figure 7-1 – Transactions between PHG and Health & Fitness services related to root file exchange for determining the capabilities of the Health & Fitness service and the PHG** + +# 8 Implementation + +## 8.1 Overview + +A PHG supporting Capability Exchange obtains information from the Health & Fitness services and vice versa, in the form of a document called the "root file". The "root file" is so named because it exists at the top of the hData hierarchy [HL7 V3 HRF]. The format of the root file is defined in the hData Record Format specification [HL7 V3 HRF]. Health & Fitness services (except SOAP based Health & Fitness services) must have the capability to provide the root file in XML format and can optionally provide it in JSON format. Similarly, the PHG must be able to process the root.xml file it receives from the services interface (Services-IF) and optionally, can also process the JSON equivalent. + +The Health & Fitness services root file contains several different types of information useful to the PHG: + +- a list of the Continua Certified Capability Classes that the Health & Fitness services support, +- a list of the resource types that may be exchanged with the Health & Fitness services in one or both directions, +- information about the available representations of exchangeable resources, +- the location of the resources in terms of partial URLs, +- any additional information required by a CCC listed in the root file. + +In the above description, the term "resource" is used in the REST sense: a logical entity that may have multiple representations. + +Once the Health & Fitness services root file has been obtained, the PHG may optionally communicate information back to the Health & Fitness services in the form of another root file. The root file sent from the PHG to the Health & Fitness services represents the PHG's capabilities, resource types, representations and other parameters defined by specific CCCs. This step of sending the PHG root file to the services interface requires authentication, so the services interface can positively identify the PHG that is the source of the root file. The authentication process is not discussed here. Because this step is optional, the PHG root file is not required. + +Once capability information has been exchanged, the devices are able to invoke the appropriate protocols in an interoperable fashion. Capability Exchange reduces the amount of information that must be pre-configured on a device in order to obtain plug and play interoperability. + +## 8.2 Root file exchange + +The root file is exchanged using the following REST mechanism: + +- The PHG performs an HTTP GET using a TLS v1.1 secure channel, OAuth v2.0 authorization token of type bearer (use of OAuth is optional in the case where an PHG implements only SOAP based Observation Upload or consent enabled-PHG CCCs) and a pre-configured URL (the "base URL") to obtain the root.xml file from the Health & Fitness services. The PHG is expected to be able to parse the root file and determine the capabilities of the Health & Fitness services. +- Optionally, the PHG performs an HTTP POST of its root file to the Health & Fitness services, using TLS v1.1 secure channel, OAuth v2.0 authorization token of type bearer (use of OAuth is optional in the case where a Health & Fitness services implements only SOAP based Observation Upload or consent enabled services CCCs) and the relative URL indicated by the Health & Fitness services root file. (The PHG is not assumed to support HTTP server capability, so an HTTP POST is used, rather than a Health & Fitness services HTTP GET operation.) + +More information about root files and REST methods is available in the hData specifications. + +## 8.3 Contents of the root file + +The root file format is described in the HL7 hData Record Format Version 1 Specification [HL7 V3 HRF]. The root files of the Health & Fitness services and the PHG will conform to HRF version 1 and validate with the XSD provided with that specification. In this clause, the elements of the root.xml file are profiled. Elements not specifically mentioned in this profile follow the element definitions in the HRF standard. The root file contains the following sub-elements under the top-level element: + +- version (xs:integer, 1..1) – The version of the hData Record Format used within the root file. The version number for root files complying with this version of the specification is 1. +- profile (0..\*) – This element represents a CCC supported by the Health & Fitness services or PHG application that owns the root file. Each CCC is described by one element using the following sub-elements: + - id (xs:string, 1..1) – The id is the formal name of the CCC represented by the profile element. For Capability Exchange, the formal name is "CapabilityExchange". For other device classes, the version-specific formal name will be given in the Continua documentation for that CCC. + - reference(xs:string, 1..1) – A reference to the Continua documentation for the CCC represented by this profile element. The reference string is composed of the URL to the Continua Guidelines repository, along with a string that identifies the name of the document. For Capability Exchange, the reference string is . +- resourceType (1..\*) – This element represents a resource type associated with one or more of the profiles listed in the root file. A specific resource type can be used in one or more CCC. A resource type is represented by the following sub-elements: + - id (xs:string,1..1) – This attribute contains the name for the resourceType. For Capability Exchange, the only resourceType is "root". For other CCCs, the resource id(s) are given in the CCC documentation. + - reference(xs:string, 1..1) – A version-specific reference to the semantic definition of the resource type. For the root resource type used by Capability Exchange, the reference is "". + - representation (0..\*) – This element represents each serialization format of the resource available for "on the wire" communication. + - mediaType (xs:string, 1..1) – Contains the media type of the resource. For Capability Exchange, the required media type is "application/xml". An optional second representation is "application/json". + - validator(xs:string, 0..\*) – An optional reference to a validator for this representation, such as an XML schema definition (XSD) or schematron. +- section (1..\*) – A section represents a "virtual file folder" where instances of a certain resource type are found. A section is identified by partial URL, relative to the base URL. Each CCC may define one or more sections. For Capability Exchange, there is one required section in the Health & Fitness services root file. + - path (xs:string, 1..1) – This text attribute is a path segment, used to construct the full path to the section. For Capability Exchange, the path is "roots". + - profileID(xs:string, 0..\*) – The of the CCC defining this section. The value of this element MUST be equal to the id attribute of a element. + +- resourcePrefix(xs:boolean, 0..1) – This element is omitted. +- resourceTypeID (xs:string, 0..1) – The value of this element MUST be equal to the id attribute of a element. Only resources whose type matches the resourceTypeID element can appear in the section. If no resourceTypeID is given, the section may not contain resources, only other sections. +- metadataSupport(xs:boolean, 0..1) – This element is omitted. +- section (section, 0..\*) – The subsections belonging to the current section, if any. + +In addition to these elements, each CCC may define extensions to the root file. The required extension elements, if any, will be present when the corresponding CCC is declared in the element. + +## **8.4            Optional JSON version of root file** + +The Services-IF may optionally support a JavaScript object notation (JSON) version of the root.xml file. If the PHG requests "application/json" in the HTTP accept header and the Services-IF supports JSON, the Services-IF should return the JSON version of the root file. + +The JSON version of the root file contains the same information as the XML version. The transform from XML to JSON and the JSON root file format is discussed in [HL7 V3 HRF]. + +## Annex A + +### Normative guidelines + +(This annex forms an integral part of this Recommendation.) + +Table A.1 shows normative guidelines for Health & Fitness services. + +**Table A.1 – Normative guidelines for Health & Fitness services** + +| Name | Description | Comments | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CapX-HFS-Root-Standard | Root file of the Health & Fitness services shall comply with [HL7 V3 HRF]. | | +| CapX-HFS-Root-Security | Health & Fitness services shall support TLS v1.1 as defined in [ITU-T H.812]. All hData based Health & Fitness services shall support OAuth authorization token of type bearer as defined in [ITU-T H.812]. | A Health & Fitness services that implements only SOAP based Observation Upload or consent enabled- HFS CCCs is not required to support the Capability Exchange-HFS CCC. | +| CapX-HFS-Root-Profile | The root file of the Health & Fitness services shall contain a profile element for each CCC it supports. | | +| CapX-HFS-Root-XML-Version | The Health & Fitness services shall support an XML version of its root file. | | +| CapX-HFS-Root-JSON-Version | The Health & Fitness services may support a JSON version of its root file. | Note that the [HL7 V3 HRF] specification document does not specify a schema for validating JSON formatted root file. | +| CapX-HFS-Root-Validation | The XML root file of the Health & Fitness service shall validate against the hData Version 1 root.xsd | | +| CapX-HFS-Root-CCC-Conformance | A Health & Fitness services listing a particular CCC in its root file shall conform to the normative guidelines for that CCC. | | +| CapX-HFS-Root-Version | The version number in the Health & Fitness services root file conforming to this specification shall be 1 | | +| CapX-HFS-Root-Profile-Element | The Health & Fitness service root file shall contain a profile element with the id "CapabilityExchange" and reference http://handle.itu.int/11.1002/3000/hData/CX/2017/01/H.812.3.pdf | | +| CapX-HFS-Root-ResourceType-Element | The Health & Fitness services root file shall contains a resourceType with id "root" and reference http://www.hl7.org/implement/standards/product-brief.cfm?product-id=261 | | + +**Table A.1 – Normative guidelines for Health & Fitness services** + +| Name | Description | Comments | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| CapX-HFS-Root-MediaType-XML | The Health & Fitness services root file shall have a representation element under the "root" resourceType with mediaType "application/xml". | | +| CapX-HFS-Root-MediaType-JSON | The Health & Fitness services root file may have a representation element under the "root" resourceType with mediaType "application/json" | | +| CapX-HFS-Root-Section-Element-Inclusions | The Health & Fitness services root file shall have a section element with the path "roots", the profileID "CapabilityExchange", the resourceTypeID of "root", and shall not specify the resourcePrefix or metadataSupport elements. | | +| CapX-HFS-Root-Section-Element-Exclusions | The Health & Fitness services root file section element with the path "roots" shall not specify the resourcePrefix or metadataSupport elements. | | +| CapX-HFS-REST-Standard | The Services-IF responses to HTTP method calls shall comply to OMG hData REST Binding for RLUS [OMG/hData RESTful Trans]. | | +| CapX-HFS-REST-GET-XML-Response | By default, the Health & Fitness services shall respond to a root file GET request (i.e., an HTTP GET on [baseURL]/root) by returning the XML version of the Health & Fitness services' root file. | | +| CapX-HFS-REST-GET-JSON-Response | A Health & Fitness services which has an "application/json" representation element under the "root" resource type in its root file shall return the JSON version of its root file in response to a PHG's GET request that specifies "application/json" in the HTTP accept header. If the Health & Fitness services does not have the JSON version then it shall return HTTP status code 501 Not Implemented. | | +| CapX-HFS-REST-POST-Response | The Health & Fitness services shall accept a HTTP POST at the URL (baseURL)/roots only if the sending PHG has a valid authorization token of type bearer as defined in [ITU-T H.812]. | | +| CapX-HFS-REST-POST-Unauthenticated-Sender | If any content is posted to the Health & Fitness services by an unauthorized sender, then the Health & Fitness services shall respond with a HTTP 401 Unauthorized error. | | + +**Table A.1 – Normative guidelines for Health & Fitness services** + +| Name | Description | Comments | +|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| CapX-HFS-REST-POST-XML-Validation | When an XML file is POSTed to the URL [baseURL]/roots, the Health & Fitness services shall validate the file against the hData Version 1 root.xsd and return HTTP 201 if the file is validated, and in case of validation failure, return HTTP 422 Unprocessable Entity. | | +| CapX-HFS-REST-POST-JSON-Validation | When a JSON file is POSTed to the URL [baseURL]/roots, the Health & Fitness services shall return HTTP 422 Unprocessable Entity if the JSON does not conform to the hData root file specification and otherwise return HTTP 201. | Note that the [HL7 V3 HRF] specification document does not specify schema for validating JSON formatted root file. | +| CapX-HFS-REST-POST-Response | In response to a successful POST of the PHG root file to [baseURL]/roots, the Health & Fitness services shall return the unique URL of the newly-created root resource. | | + +Table A.2 shows normative guidelines for PHG device. + +**Table A.2 – Normative guidelines for PHG device** + +| Name | Description | Comments | +|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| CapX-PHG-REST-XML-Request | Given the URL of a Health & Fitness services complying with Capability Exchange ("baseURL"), the PHG device may obtain the root file of the Health & Fitness services using an HTTP GET operation. | | +| CapX-PHG-REST-Services-Root-security | PHG shall obtain root file of the Health & Fitness services using TLS v1.1 secure channel as defined in [ITU-T H.812]. All hData based PHGs shall support OAuth authorization token of type bearer as defined in [ITU-T H.812]. | A PHG that implements only SOAP based Observation Upload or consent enabled-PHG CCCs is not required to support the Capability Exchange-PHG CCC. | +| CapX-PHG-REST-XML-Request | The PHG device shall be able to request the Health & Fitness services root file in XML format by specifying "application/xml" in the HTTP accept header. | | +| CapX-PHG-REST-JSON-Request | The PHG device may request the Health & Fitness services root file in JSON format by specifying "application/JSON" in the HTTP accept header. | Note that the HL7 hRF specification document does not specify schema for validating JSON formatted root file. | +| CapX-PHG-Root-POST | PHG may do an HTTP POST of its root file at the URL [baseURL]/roots using TLS v1.1 secure channel as defined in [ITU-T H.812] and a valid authorization token of the type bearer as defined in [ITU-T H.812]. The authorization token shall be obtained according to the guidelines described in [ITU-T H.812]. | | +| CapX-PHG-Root-Standards | Root file of the PHG shall comply with [HL7 V3 HRF]. | | +| CapX-PHG-Root-Profile | The root file of the Health & Fitness services shall contain a profile element for each CCC it supports. | | +| CapX-PHG-Root-CCC-Conformance | A PHG listing a particular CCC in its root file shall conform to the normative guidelines for that CCC. | For example profile and section info in the root file for a CCC are defined by that specific CCC. | + +## Appendix I + +### Root file inclusions for Capability Exchange + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Required root file inclusions for Health & Fitness services + +``` + + CapabilityExchange + http://handle.itu.int/11.1002/3000/hData/CX/2017/01/H.812.3.pdf + + + + +
    + roots + CapabilityExchange + root +
    + + + root + http://www.hl7.org/implement/standards/product-brief.cfm?product- +id=261 + + + application/xml + + + application/json + + +``` + +### I.2 Schema for the root.xml + +``` + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +### I.3 Required root file inclusions for PHG + +There are no required root file inclusions, however a PHG device listing a particular CCC in its root file (as a profile element) **shall** conform to the normative guidelines for that CCC. + +## Appendix II + +### hData + +(This appendix does not form an integral part of this Recommendation.) + +hData is a lightweight, web-based specification for exchanging electronic health data. Created in 2009 by US non-profit MITRE Corporation and evolved in cooperation with leaders in the health care industry, hData is the first RESTful standard for health data exchange. The hData specifications have been approved by Health Layer 7 (HL7) and the Object Management Group (OMG). + +hData uses representational state transfer (REST) over HTTP in a way that separates content, transport and security. REST is a design pattern that is simple, scalable and widely adopted. + +hData is used in all Continua Certified Capability Classes, either as the only mechanism, or as an alternative to SOAP based exchange. + +**Resources** are a central concept in REST and in hData. A resource can be any piece of information: data about a patient, a device, a prescription, a plan of care, an imaging study, a problem or condition, or a complete medical document such as a Consolidated CDA [b-HL7 CDA IHE HSC]. For purposes of information exchange, resources can have multiple representations, such as XML or JSON. + +**Sections** represent a virtual arrangement of resources in hData. Sections are analogous to directories in a hierarchical file system, and are defined by paths consisting of one or more forward-slash delimited sub-levels. Each section is associated with a specific type of resource (called *resourceTypes* in hData). For example, resources that represent a person's allergies may be found in a section called *allergy*. The allergy section may contain zero or more instances of an allergy resource. The arrangement of sections forms a tree structure, called the hData Hierarchy (HDH). + +**URLs** uniquely identify each resource. The URL of a resource is a combination of a base URL, a section path and a resource ID, as follows: + +``` +resource URL = (baseURL) / (sectionPath) / (resourceID) +``` + +The baseURL is the location of the hData service endpoint, and consists of the protocol (in this case, HTTP or HTTPS), a host identifier (IP address or domain name), and optionally a port. The resourceID is defined arbitrarily by the resource owner, subject to the constraint that the resource URL is unique. + +**Root files** are provided by hData service endpoints to advertise the resource types (extensions) and the section paths (sections) provided by that service. The format of the root file is described in [HL7 V3 HRF]. The root file is accessed by a HTTP GET operation on the following URL: + +``` +root file URL = (baseURL) / root +``` + +**Content profiles** are the means to achieve interoperability between hData service endpoints. Content profiles are implementation guides that describe an application of hData that promote information interoperability. If every hData service endpoint were to arbitrarily define its own resource types and hData hierarchy, the result would be an ecosystem with no predictability or consistency, with naming conflicts and incompatible resource schemas. To counteract this potentially chaotic situation, hData calls for the creation of content profiles which provide standard section naming and resource schemas for a specific business need or technical capability. For example, pharmacy domain experts have provided a Content Profile for Medication Statements + +[b-HL7 V3IG MSSP]. Conforming to this content profile assures interoperability of medication statements among providers and consumers of this type of information. + +Each Certified Capability Class (CCC) defines one or more resource types and associated section paths in an hData content profile. If an hData service endpoint supports more than one CCC, then its root file will effectively be a union of those extensions and section paths. To create a root file from multiple HCPs, the implementer should copy and combine the information in the example root files from each HCP to create a single root file, creating a combined list of profiles, sections, and resourceTypes. The result is an HDH that combines multiple CCCs. + +**REST operations**, summarized in Table II.1, are at the heart of hData. There are three types of operations: resource operations, section operations and base operations, corresponding to the target being a resource (baseURL/sectionPath/resourceID), a section (baseURL/sectionPath), or the base (baseURL), respectively. hData represents a REST binding of a retrieve, location and updating service (RLUS). For details, including information on required and optional behaviours and parameters, and return arguments, see [OMG/hData RESTful Trans] the hData RESTful transport specification. + +**Table II.1 – Types of operations** + +| Operation | Operation description | HTTP implementation | Requirement | +|---------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|--------------------------------------------------------| +| Read | Get the current version of the resource | GET ( resourceURL ) | Required | +| Version Read | Get a specific version of the resource | GET ( resourceURL )/history/( versionId ) | Optional | +| Update | Update an existing resource | PUT ( resourceURL ) | Optional | +| Delete | Delete a resource | DELETE ( resourceURL ) | Optional | +| List | Gets a list of subsections and resources in the section as an ATOM feed | GET ( baseURL or sectionURL ) | Required | +| Create | Create a new resource or subsection in a section | POST ( baseURL or sectionURL ) | Optional | +| Batch Create/Update | Create or update multiple resources in a section | POST ( baseURL or sectionURL ) using Atom feed | Optional | +| Search | Gets a list of section resources matching the query parameters | GET ( baseURL or sectionURL )/?search( queryString ) | Optional | +| Validate | Validate a proposed creation action, prior to commit | POST ( sectionURL )/validate | Optional | +| Capability Read | Gets root file for Capability Exchange | GET ( baseURL )/root | Required | +| Metadata | Gets service metadata; returns security mechanisms available and a list of supported hData content profiles | GET ( baseURL )/metadata, optionally OPTIONS ( baseURL ) | Required without prior authentication or authorization | +| Update Metadata | Replaces metadata on document | POST ( resourceURL ) | Optional | + +The hData interoperability framework is depicted in Figure II.1. + +![Diagram of the hData interoperability framework showing the relationship between PHG applications, Services applications, and Content profiles.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +The diagram illustrates the hData interoperability framework. On the left, a yellow box labeled "PHG application *optional Root.xml*" is shown. Below it, two dashed yellow boxes labeled "Content profile A" and "Content profile B" are connected to a dashed "Union" box, which in turn points to the PHG application box. On the right, a large yellow box labeled "Services application" contains a "Root.xml" file. The Root.xml file is described as "Describes sections and types" and contains the following structure: + +/section 1 + +    *{resources of section 1}* + +/section 2 + +    *{resources of section 2}* + +/section 3 + +    *{resources of section 3}* + +etc. + +Above the Services application box, several yellow boxes labeled "Content profile 1", "Content profile 2", "...", and "Content profile N" are connected to a "Union" box, which points to the Root.xml file. Two arrows connect the PHG application box to the Root.xml file: + +1. An arrow labeled "Capability exchange operations:" with sub-points "• Read," and "• optional create". + +2. An arrow labeled "Section and resource operations:" with sub-points "• Read," "• Update," "• Create," and "• etc.". + +The text "H.812.3(17)\_FI1.1" is located in the bottom right corner of the diagram area. + +Diagram of the hData interoperability framework showing the relationship between PHG applications, Services applications, and Content profiles. + +**Figure II.1 – hData interoperability framework** + +(NOTE – The PHG application and Health & Fitness services application root.xml files are **not** the same.) + +## **Bibliography** + +For a list of non-normative references and publications that contain further background information, see [ITU-T H.810]. + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.812.4-201711-I_PDF-E/raw.md b/marked/H/T-REC-H.812.4-201711-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..832436c569080ee9650559333c7e7a0a8e01f44b --- /dev/null +++ b/marked/H/T-REC-H.812.4-201711-I_PDF-E/raw.md @@ -0,0 +1,1533 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.812.4** + +(11/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia services and applications – Personal +health systems + +--- + +**Interoperability design guidelines for personal +connected health systems: +Services interface: Authenticated Persistent +Session capability** + +Recommendation ITU-T H.812.4 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.812.4 + +# Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability + +## Summary + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for personal connected health services. The Continua Design Guidelines also contains design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. + +ITU-T H.812.4 defines the additional design guidelines for the Authenticated Persistent Session (APS), whose function is to provide a secure, long-lived, persistent bidirectional data channel between the Health & Fitness services application and a Personal Health Gateway (PHG) application, suitable for sending unsolicited commands to the PHG or to devices connected via the PHG. + +ITU-T H.812.4 is part of the "ITU-T H.810 interoperability design guidelines for personal connected health systems" subseries that covers the following areas: + +- ITU-T H.810 – Interoperability design guidelines for personal connected health systems: Introduction +- ITU-T H.811 – Interoperability design guidelines for personal connected health systems: Personal Health Devices interface +- ITU-T H.812 – Interoperability design guidelines for personal connected health systems: Services interface +- ITU-T H.812.1 – Interoperability design guidelines for personal connected health systems: Services interface: Observation Upload capability +- ITU-T H.812.2 – Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability +- ITU-T H.812.3 – Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability +- ITU-T H.812.4 – Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability (this design guidelines document) +- ITU-T H.813 – Interoperability design guidelines for personal connected health systems: Healthcare Information System interface. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.812.4 | 2015-11-29 | 16 | 11.1002/1000/12657 | +| 2.0 | ITU-T H.812.4 | 2016-07-14 | 16 | 11.1002/1000/12917 | +| 3.0 | ITU-T H.812.4 | 2017-11-29 | 16 | 11.1002/1000/13419 | + +## Keywords + +CDG, Continua Design Guidelines, healthcare information systems, persistent session, personal connected health systems, personal health devices, services. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-------|-----------------------------------------------------------------------------------------|----| +| 0 | Introduction..... | vi | +| 0.1 | Organization ..... | vi | +| 0.2 | Guideline releases and versioning ..... | vi | +| 0.3 | What's new..... | vi | +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations and acronyms ..... | 1 | +| 5 | Conventions ..... | 1 | +| 6 | Authenticated Persistent Session use case ..... | 1 | +| 7 | Authenticated Persistent Session (APS) overview ..... | 1 | +| 7.1 | Support for multiple CCCs..... | 3 | +| 7.2 | Topics used in MQTT ..... | 4 | +| 7.3 | Shoulder tap..... | 5 | +| 8 | APS management..... | 5 | +| 8.1 | APB resources ..... | 6 | +| 8.2 | APS behaviour ..... | 11 | +| 8.2.1 | APS session state..... | 11 | +| 8.2.2 | Authenticated persistent binding identifiers (APBI)..... | 11 | +| 8.2.3 | Authenticated persistent binding establishment..... | 12 | +| 8.2.4 | Accepting an authenticated persistent binding..... | 12 | +| 8.2.5 | Authenticated persistent binding and session termination ..... | 12 | +| 8.2.6 | APS-CCC diagnostic message ..... | 13 | +| 9 | Behavioural model: MQTT ..... | 15 | +| 9.1 | Overview of operation..... | 15 | +| 9.1.1 | Graceful APS termination ..... | 16 | +| 9.2 | Interaction of the Health & Fitness services application with the PHG application ..... | 17 | +| 9.3 | State of the PHG's connection to the HFS MQTT server..... | 17 | +| 9.3.1 | Interaction of a PHG application with the MQTT server..... | 18 | +| 10 | Behavioural model: SMS shoulder tap capability ..... | 21 | +| 10.1 | Shoulder tap overview ..... | 21 | +| 10.2 | Scope ..... | 22 | + +| | Page | +|-------------------------------------------------------------------------------------|------| +| 10.3 Shoulder tap invocation determination..... | 22 | +| 10.4 PHG SMS information ..... | 23 | +| 10.5 SMS message structure..... | 23 | +| 10.6 PHG application requirements ..... | 24 | +| 10.7 Semantic behaviour of the PHG application relative to ST reception..... | 24 | +| Annex A – Normative guidelines for the APS-CCC ..... | 25 | +| A.1 Guidelines for the APS components in capabilities exchange ..... | 25 | +| A.2 Guidelines for PHG APS management (APS-CCC-PHG)..... | 26 | +| A.3 Guidelines for the PHG application interactions with the MQTT server ..... | 28 | +| A.4 Guidelines for HFS application APS management..... | 31 | +| A.5 Guidelines for the PHG application SMS shoulder tap ..... | 36 | +| A.6 Guidelines for the Health & Fitness services application SMS shoulder tap ..... | 36 | +| Annex B – XML schema for the APB resource..... | 37 | +| Appendix I – APS details..... | 39 | +| I.1 APS information in the root.xml ..... | 39 | +| I.2 APS authentication: Resource owner password credentials approach..... | 39 | +| I.3 APS establishment: PHG application POST with partial APB..... | 40 | +| I.3.1 APS establishment: PHG GET for completed APB ..... | 40 | +| I.3.2 APS establishment: PHG setup with MQTT server..... | 42 | +| I.3.3 MQTT: PHG application subscribes to commands ..... | 42 | +| I.3.4 MQTT: PHG Application Publishes "CONNECTED" ..... | 42 | +| I.4 APS establishment: PHG application enables APS ..... | 42 | +| I.5 Operation ..... | 42 | +| Appendix II – Example Health & Fitness service root.xml file..... | 44 | +| Bibliography..... | 45 | + +# List of Tables + +| | Page | +|-----------------------------------------------------------------------------------------------|-------------| +| Table 7-1 – Topics used in MQTT..... | 4 | +| Table 8-1 – APB xml elements provided by PHG application ..... | 7 | +| Table 8-2 – APB xml elements provided by Health & Fitness application ..... | 9 | +| Table 8-3 – Fields of the APS-CDC diagnostic message ..... | 13 | +| Table 9-1 – State table for the status topic..... | 17 | +| Table 9-2 – Information contained in the PHG application's MQTT connect message ..... | 19 | +| Table 9-3 – Information contained in MQTT SUBSCRIBE message..... | 20 | +| Table 9-4 – Information contained in the PHG's Publish Status message ..... | 20 | +| Table 9-5 – Information contained in the PHG application's MQTT Publish Response message .... | 21 | +| Table 10-1 – Structure of payload..... | 24 | +| Table 10-2 – Continua information elements ..... | 24 | +| Table A-1 – APS elements of capabilities exchange ..... | 25 | +| Table A-2 – APS management PHG..... | 26 | +| Table A-3 – PHG-MQTT exchanges ..... | 28 | +| Table A-4 – APS management requirements for the Health & Fitness services application ..... | 31 | +| Table A-5 – SMS shoulder tap PHG..... | 36 | +| Table A-6 – HFS application SMS shoulder tap..... | 36 | + +# List of Figures + +| | Page | +|-------------------------------------------------------------------------------------------------|-------------| +| Figure 7-1 – APS framework ..... | 2 | +| Figure 7-2 – Example of payload delivery to different message handlers..... | 4 | +| Figure 8-1 – Profile element indicating capability..... | 6 | +| Figure 8-2 – ResourceType element describing APB content..... | 7 | +| Figure 8-3 – Section element describing where to POST ..... | 7 | +| Figure 8-4 – Example of PHG application supporting MQTT and an SMS shoulder tap ..... | 11 | +| Figure 9-1 – PHG application and Health & Fitness services application MQTT client interactions | 16 | +| Figure 9-2 – State diagram for the status topic ..... | 17 | +| Figure 10-1 – Shoulder tap overview..... | 22 | +| Figure 10-2 – Payload of binary SMS message ..... | 23 | +| Figure I-1 – Example APB posted by PHG application ..... | 40 | +| Figure I-2 – APB created by Health & Fitness service application ..... | 41 | + +# 0 Introduction + +The Continua Design Guidelines (CDG) defines a framework of underlying standards and criteria that ensure the interoperability of devices and data used for personal connected health services. The Continua Design Guidelines also contain additional design guidelines that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. + +This design guidelines defines the additional design guidelines for the Authenticated Persistent Session (APS), whose function is to provide a secure, long-lived, persistent bidirectional data channel between the Health & Fitness services application and a Personal Health Gateway (PHG) application, suitable for sending unsolicited commands to the PHG or to devices connected via the PHG. + +This design guidelines is part of the "ITU-T H.810 interoperability design guidelines for personal health systems" subseries. See [ITU-T H.810] for more details. + +## 0.1 Organization + +This design guidelines document is organized in the following manner: + +**Clauses 0 to 5: Introduction and terminology** – These clauses provide useful background information to help understand the structure of the design specifications. + +**Clause 6: Use cases** – This clause provides a descriptive scenario that motivates the class of problems that the APS is addressing. + +**Clause 7: Authenticated Persistent Session overview** – This clause provides a technical overview of the operation of the Authenticated Persistent Session (APS). + +**Clause 8: Authenticated Persistent Session management** – This clause describes the interactions between the information exchange parties. + +**Clause 9: Behavioural model: MQTT** – This clause is an overview of sequences of interactions under this Certified Capability Class (CCC) and summarizes typical iterations, constraints and exceptions. + +**Clause 10: Behavioural model: SMS shoulder tap capability** – This clause defines an SMS-based capability that facilitates operation of the APS with networks that remove IP infrastructure for inactive connections. + +**Annex A:** The guidelines that document the normative elements for the Authenticated Persistent Session are presented in a tabular format in this annex. The annex references other locations with normative content. + +**Annex B:** root file for an Authenticated Persistent Session. + +**Appendix I:** APS details. + +**Appendix II:** APB resource schema. + +## 0.2 Guideline releases and versioning + +See clause 0.2 of [ITU-T H.810] for release and versioning information. + +## 0.3 What's new + +To see what is new in this release of the design guidelines, refer to clause 0.3 of [ITU-T H.810]. + +###### Recommendation ITU-T H.812.4 + +# Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability + +# 1 Scope + +This design guidelines document defines two Certified Capability Classes. Both Certified Capability Classes contain guidelines that document a secure mechanism by which a services application can initiate communications with an application residing within a transient piece of customer premises equipment known as a Personal Health Gateway (PHG). The two Certified Capability Classes are respectively for the services application (APS-CCC-Services) and for the PHG application (APS-CCC-PHG). + +The mechanism addresses: (1) the establishment and management of a persistent long term session between the services application and the PHG application, (2) the use of the message queuing telemetry transport (MQTT) protocol for message exchange and (3) the use of short message service (SMS) to re-establish IP level connectivity with transient PHGs that have a cellular interface. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.810] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal connected health systems: Introduction*. + +All other referenced documents can be found in clause 2 of [ITU-T H.810]. + +# 3 Definitions + +This design guidelines document uses terms defined in [ITU-T H.810]. + +# 4 Abbreviations and acronyms + +This design guidelines document uses abbreviations and acronyms defined in [ITU-T H.810]. + +# 5 Conventions + +This design guidelines document follows the conventions defined in [ITU-T H.810]. + +# 6 Authenticated Persistent Session use case + +The Authenticated Persistent Session provides a mechanism by which future Continua Certified Capability Classes (CCCs) can initiate communications from cloud based services to the PHG. + +# 7 Authenticated Persistent Session (APS) overview + +The Authenticated Persistent Session Certified Capability Class defines a long lived, persistent context for exchanging messages between a Health & Fitness services application and a PHG application. The context is persistent in that it maintains operational state across TCP connections, pausing when the underlying TCP connection is lost and resuming when it is re-established. The session is long lived in that applications maintain the session for whatever time duration is required. + +Long lived persistent sessions support applications that send occasional messages requiring a timely response. + +NOTE 1 – These guidelines define an Authenticated Persistent Session Certified Capability Class for a PHG application (APS-CCC-PHG) and for a Health & Fitness services application (APS-CCC-Services Interface). The notation APS-CCC is used as a shorthand when it is not necessary to disambiguate between the actual service and PHG CCCs. + +The APS-CCC is optimized for sending messages over networks where bandwidth, power, and IP resources are limited. The optimization is obtained by eliminating PHG application based polling. The APS-CCC defines an optional wake up capability based on the short message service (SMS) for use when the PHG has cellular network connectivity. This capability allows the Health & Fitness services application to wake up a PHG application that no longer has IP connectivity due to the cellular network reallocating inactive resources. Implementations that support SMS may be able to take advantage of this optional capability in order to minimize their network utilization. + +The term *Authenticated Persistent Session* (APS) describes the concept of the persistent session as defined in this design guidelines document. A related term, *authenticated persistent binding* (APB) is used to describe the information resource exchanged during persistent session establishment. We qualify *persistent session* and *persistent binding* with *authenticated* to emphasize a relationship that the Health & Fitness services application creates between the APB resource and a PHG application security credential in order to ensure proper authentication when the PHG application resumes a persistent session. + +Figure 7-1 depicts the framework of the APS. + +![Figure 7-1 – APS framework diagram showing the interaction between a PHG application and Services applications through various network interfaces.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +The diagram illustrates the APS framework, divided into two main vertical sections: **PHG application** (left) and **Services applications** (right). + +- PHG application section:** + - Contains an **Application logic API client** (yellow oval). + - Below it, a dashed box labeled **APS-PHG** contains: + - An **APS service component (API)**. + - A **PHG-MQTT client**. + - An **HTTP client**. + - To the left of the APS-PHG box is a **Capability exchange service component (API)**. + - At the bottom is a **Black box of PHG**. +- Services applications section:** + - Contains a **Service logic API client** (yellow oval). + - Below it, a dashed box labeled **APS-Services** contains: + - An **APS service component (API)**. + - An **HTTP server**. + - A **Service-MQTT server**. + - To the right of the APS-Services box is a **Capability exchange service component (API)**. + - At the bottom is a **Black box of services device**. + +**Network Interfaces and Connections:** + +- Capability exchange-PHG network interface** (green line) connects the PHG application's capability exchange component to the **Capability exchange of root.xml (HTTP)** at the bottom. +- APS-CDC-PHG network interface** (blue line) connects the PHG application's APS service component to the **Message exchange (MQTT)** at the bottom. +- APS-CDC-services network interface** (blue line) connects the Services application's APS service component to the **Message exchange (MQTT)** at the bottom. +- Capability exchange-services network interface** (green line) connects the Services application's capability exchange component to the **Capability exchange of root.xml (HTTP)** at the bottom. +- Internal connections within the PHG application include: + - A red line from the **PHG-MQTT client** to a **Shoulder tap message (SMS)** label. + - A red line from the **HTTP client** to an **APB resource exchange (HTTP)** label. + +Figure 7-1 – APS framework diagram showing the interaction between a PHG application and Services applications through various network interfaces. + +H.812.4(16)\_F7-1 + +**Figure 7-1 – APS framework** + +An Authenticated Persistent Session (APS) is a binding between two *APS service components*, one in the *Health & Fitness services application* and one in the *PHG application*, which enables the *API clients* to behave as if there is an always connected pipe between them. In Figure 7-1 the *APS API service components* are the peer entities that implement these guidelines in order to deliver the persistent session service to their *API clients*. The *Health & Fitness services application* using the *APS API client* component (see clause 6.1.1 *Devices, components, applications and interfaces* of [ITU-T H.810]) can securely issue commands to the PHG application, across service disruptions, without needing to manage the connectivity or authenticity of the peer. + +NOTE 2 – Figure 7-1 represents an architectural model and does not mandate a particular implementation. + +NOTE 3 – The existence of an APS between two components does not mean that messages can be exchanged between the components at a given point in time. Message delivery is only possible when there is connectivity at the transport layer. + +The APB resource that defines the APS is based on exchanged security credentials using a given source of authentication information. Any entity that provides the appropriate authentication information may gain access to the APS and continue the persistent session. + +NOTE 4 – It is possible for an APS to move from one physical device to a different physical device as long as the PHG implementation presents the same credentials. Therefore, a Health & Fitness services application should not assume that an APS represents a connection to a particular PHG hardware platform; the APS is bound to a security credential such as an X.509 certificate, an OAuth token, or SAML token. + +There are three steps involved in creating and exchanging a message using an APS. Once the APS is in place only the final step is needed to send additional messages. The three steps, in order are: + +- Capability Exchange, see [ITU-T H.812.3] – In this phase the PHG application obtains information from the Health & Fitness services application using HTTP. The information identifies if the Health & Fitness services application has support for APS-CCC-Services. The information is contained in the root.xml file of the Health & Fitness services application and includes the URL to use for APS establishment. See clause 8.1. +- APS establishment – The PHG application, using a secure HTTPS connection, creates the APB resource on the Health & Fitness services application indicating its desire to establish a persistent session. During this phase the PHG application authenticates itself to the Health & Fitness services application and is provided with APB resource information. When this phase completes the PHG has either established the APS and is ready to exchange messages with the Health & Fitness services application, or has terminated the APS establishment process causing the APB resource to be removed. See clause 8.2.3. +- Message exchange using MQTT (see clause 9) – In this phase a transport level security (TLS) connection is established by the PHG application connecting it to the MQTT server exposed by the Health & Fitness services application. This connection is used for the normal exchange of messages. In an APS the management information is contained in the APB resource, which is manipulated using RESTful operations over HTTPS. The data flow associated with the operation of the APS is carried in messages flowing over the MQTT connection. Once an APS has been created there is typically no additional management activity, so all activity is over MQTT. + +## 7.1 Support for multiple CCCs + +A PHG application in the future may contain multiple CCCs (or vendor specific components) that make use of the APS. An example of this might be a CCC for remote PHG configuration. These CCCs will have message handlers to process the received messages. Each message that is transmitted from the services application is addressed to one of these message handlers via the topic name used in the MQTT PUBLISH command. It is the responsibility of the APS implementer to ensure that messages received by the PHG application are dispatched to the correct message handler. + +NOTE 1 – The dispatcher does not use any information in the MQTT payload. The payload is opaque to the dispatcher. + +Figure 7-2 shows an example of delivering the payload in an MQTT message to different message handlers. There are two message handlers in this example: 1) the APS management message handler which supports the ECHO message; 2) an undefined future CCC or vendor specific message handler. The MQTT message is received by the Network-IF component which forwards it to the dispatcher. The dispatcher extracts the MQTT header. The MQTT header contains the topic name which identifies the message handler to which the payload needs to be delivered. The topic name is a string that uniquely identifies the CCC that is expected to process the message. + +NOTE 2 – This description is illustrative and does not proscribe a particular method of implementation. + +![Figure 7-2 – Example of payload delivery to different message handlers](398674b42e3466add6d47f420c136494_img.jpg) + +``` + +graph TD + subgraph PHG_application [PHG application] + subgraph Black_box_of_PHG [Black box of PHG] + MMH[Management message handler supporting ECHO] + FCCC[Future CCCs or vendor specific message handlers] + EM[ECHO message] + VDM[Vendor defined messages] + D[dispatcher] + + D --> EM + D --> VDM + EM --> MMH + VDM --> FCCC + end + end + + NI[Network-IF component] --> D + MH[MQTT header] --- MP[MQTT payload] + MP --> NI + +``` + +**Figure 7-2 – Example of payload delivery to different message handlers** + +Figure 7-2 – Example of payload delivery to different message handlers + +### 7.2 Topics used in MQTT + +Continua compliant entities implementing the APS-CCC **shall** support the use of the MQTT protocol to publish and subscribe to messages. The MQTT protocol uses a topic-based addressing mechanism, and this standard specifies three kinds of topics to be used by an APS. They are shown in Table 7-1. + +**Table 7-1 – Topics used in MQTT** + +| Name used in this document | Format of the topic string used in MQTT | Description | +|----------------------------|-------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| Message topics | pcha/message/<HFS APBI>/<PHG APBI>/<mh> | Topics used to transmit messages to the APS API client components in the PHG application. | +| Status topic | pcha/status/<HFS APBI>/<PHG APBI> | Topic used to track status of the APS | +| Response topics | pcha/response/<HFS APBI>/<PHG APBI>/<mh> | Topic used to receive responses from the PHG application | + +4 Rec. ITU-T H.812.4 (11/2017) + +Each APS is identified by a pair of APB identifiers (APBIs) in the corresponding APB resource, and these APBIs **shall** be inserted in the topic strings in place of the characters and . See clause 8.2.2 for more details on the APBIs. The **shall** be replaced by an identifier specified by the CCC that is using the APS exchange mechanism. The identifier allows different CCC peers to exchange messages in the context of a single APS. An example of a message topic for an APS might appear as follows: + +pcha/message/1/34521ee41da2eff/APS. + +The MQTT server **shall** control access to these topics using the following rules: + +- A Health & Fitness services application **shall** have write access to any message topics containing its Services APBI. +- A Health & Fitness services application **shall** have read access to the status and response topics containing its Services APBI. +- A PHG application **shall** have read access to any message topics containing its PHG APBI. +- A PHG application **shall** have write access to any status topics containing its PHG APBI. +- A PHG application **shall** have write access to any response topics containing its PHG APBI. +- Suitably authenticated management applications MAY have read access to any topic. +- All other access **shall** NOT be permitted. + +In general the above requirements are stating that an APS-CCC shall only have access to topics defined for that APS-CCC. A similar relationship holds, in theory, between the Health & Fitness services application and MQTT server, but how the Health & Fitness services application and MQTT server actually interact is implementation dependent. In many implementations the Health & Fitness services application is also the authenticated management application. + +## 7.3 Shoulder tap + +If the Health & Fitness services application needs to send a message to the PHG application and the PHG application is no longer connected to the MQTT server, the Health & Fitness services application can use one of the shoulder tap methods supported by the PHG application to alert it that a message is waiting. The PHG application, upon reception of the shoulder tap, reconnects to the MQTT server. The PHG is then able to receive messages from the Health & Fitness services application. Currently the only defined shoulder tap method is binary SMS messaging. + +# 8 APS management + +An authenticated persistent session (APS) is a long term association between two mutually authenticated peer entities, one associated with the Health & Fitness services application and the other with the PHG application. Authentication is performed using TLS in conjunction with OAUTH as outlined in Annex B of [ITU-T H.812]. + +The Health & Fitness services application, after it has successfully authenticated the PHG application allocates a resource, called the authenticated persistent binding (APB). The APB contains a set of attributes that both define the APS and provide the basis for its management. It is the responsibility of the Health & Fitness services application to ensure that for a given OAUTH bearer token: (1) the same APB **shall** be returned on repeated requests for the APS resource, and that (2) if a different OAUTH bearer token is provided a different APS resource (or an error) **shall** be returned. + +The APB resource is an XML document with a set of elements as defined in Table 8-1 and Table 8-2. The management of APB resources is covered in this clause. + +The Health & Fitness services application implementing the APS-CCC uses hData to present to the PHG application three items relating to APSs in the root.xml file. The first item is a *profile*. The profile is an entry that indicates that the Health & Fitness services application supports the APS-CCC. The second item, *resourceType*, describes the content of the APB resource and contains a reference to a XML schema that can be used to validate it. The third item, *section*, is an entry that indicates to the PHG application where to POST its contribution to the APB resource when first establishing the APS. + +The initial content of the APB resource is jointly established by the PHG and Health & Fitness services applications. The PHG application provides an APB resource structured in accordance with the XML schema identified in the *resourceType* element of the root.xml file. The PHG application provides values for a subset of the APB elements as identified in Table 8-1. The Health & Fitness services application when it receives the APB resource from the PHG application fills in the remaining elements as defined in Table 8-1. + +During the establishment of an APS, a pair of identifiers is allocated by the Health & Fitness services application. These identifiers are part of the APB resource. One identifier in the pair is associated with the PHG application (PHG APBI) and the other identifier is associated with the Health & Fitness services application (services APBI). The services APBI together with the PHG APBI identify the APB instance and **shall** be unique across all the APSs being managed by the Health & Fitness services application. + +## 8.1 APB resources + +The APS-CCC-Services defines a management interface that uses HTTPS and hData. These mechanisms prescribe a RESTful and secure access mechanism to information defining the APS, which is contained in the APB resource. The starting point for the hData layout of this interface is the root.xml file. For a Health & Fitness services application implementing the APS-CCC-Services the root.xml file **shall** contain the entries as specified in Figure 8-1, Figure 8-2 and Figure 8-3. + +``` + + + APS-CCC-Services + + http:// handle.itu.int/11.1002/3000/hData/APS/2017/01/H.812.4.pdf + + +``` + +**Figure 8-1 – Profile element indicating capability** + +The entry in Figure 8-1 indicates to the PHG application that the Health & Fitness services application supports the APS message transfer infrastructure (APS-CCC-Services). This entry **shall** appear exactly as shown in Figure 8-1. + +``` + + + APB + + + http://handle.itu.int/11.1002/3000/hData/APS/2017/01/H.812.4.pdf + + + application/xml + + + http://handle.itu.int/11.1002/3000/hData/APS/2017/01/APBConfigResource.xsd + + + + +``` + +**Figure 8-2 – ResourceType element describing APB content** + +The entry in Figure 8-2 provides a description and the structure (such as a schema) of the APB. The entry **shall** appear exactly as shown in Figure 8-2. + +``` + +
    + + path/to/post/folder + APS-CAC-Services + + true + APB +
    + +``` + +**Figure 8-3 – Section element describing where to POST** + +The entry in Figure 8-3 identifies a URL to which the PHG application performs the initial POST in the APS establishment. The element value **shall** be that of the element value in the element and the value **shall** be APB. The element **shall** be present in this specification and it **shall** be set to true (it is optional in the hData specification). The element **shall** be present but the URL value is determined by the application. + +Table 8-1 and Table 8-2 describe the contents of the APB resource that characterizes the APS. + +The APB resource is expressed as an xml document, an example of which is shown in Figure 8-4. The example in Figure 8-4 shows a PHG application supporting MQTT and an SMS shoulder tap. See Appendix II for the APB resource schema. + +**Table 8-1 – APB xml elements provided by PHG application** + +| Element | Usage | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedMH | Mandatory – A space-separated list identifying the message handlers that are supported by the PHG application. All PHG applications that support APS message transfer shall support the APS diagnostic handler as denoted below.
    • – The three uppercase characters "APS"
    This value shall be ignored by the PHG application whenever the APB resource is obtained from the Health & Fitness services application. | + +**Table 8-1 – APB xml elements provided by PHG application** + +| Element | Usage | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Note – If a vendorspecific message handler is used, the identifying string should have properties that minimize the potential for a collision with another uncoordinated vendor message handler. | +| exchangeMechanism | Mandatory – A space-separated list identifying the underlying technologies that are being used by the PHG application to support message exchanges. The PHG application shall identify each technology that it supports in an ordered list with the first entry in the list being its preferred choice. The only currently supported exchange mechanism is MQTT.
    This value shall be ignored by the PHG application whenever the APB resource is obtained from the Health & Fitness services application. | +| shoulderTapMechanism | Mandatory – A space-separated list identifying the underlying technologies that the PHG application uses to accept a shoulder tap. The shoulder tap enables the Health & Fitness services application to re-establish a TCP connection with the PHG application in the event that the resources used to maintain that connection have been removed. The PHG application identifies each technology that it supports in an ordered list with the first entry in the list being its preferred choice. The Health & Fitness services application shall select the first technology that it supports from the list. If the PHG application does not support a shoulder tap it shall provide an empty list. SMS is currently the only defined mechanism for performing a shoulder tap.
    This value shall be ignored by the PHG application whenever the APB resource is obtained from the Health & Fitness services application. | +| SMS | Conditionally required – This element shall be present if a shoulder tap mechanism of SMS is selected. The SMS element contains the information that the Health & Fitness services application will use in order to perform the shoulder tap operation. The SMS element is the parent element for SMSHeaderDstPort, SMSApplicationId, and MSISDN.
    This value shall be ignored by the PHG application whenever the APB resource is obtained from the Health & Fitness services application. | +| MSISDN | Mandatory SMS Child – The MSISDN is the SMS number used to reach the PHG application (the PHG application's 'phone number'). It shall be composed of the numeric digits [0-9] with an optional leading "+". The total string shall be 15 characters of less.
    This value shall be ignored by the PHG application whenever the APB resource is obtained from the Health & Fitness services application. | +| SMSHeaderDstPort | Mandatory SMS Child – The SMSHeaderDstPort gives the value to be used as the 16-bit destination port in the SMS User Data Header (UDH information element identifier value of 0x05). See clause 9.3.1 for additional information. The information shall be represented in this element as a decimal number.
    This value shall be ignored by the PHG application whenever the APB resource is obtained from the Health & Fitness services application. | +| SMSApplicationId | Optional SMS Child – The SMSApplicationID shall be a sequence of Unicode characters. The length of this string, when encoded using UTF8, shall not exceed 148 octets. This string shall be sent in the payload of a Shoulder Tap. The purpose of the element is to provide an application identifier in the shoulder tap which can be used to route the shoulder tap message to the appropriate PHG application The exact semantics associated | + +**Table 8-1 – APB xml elements provided by PHG application** + +| Element | Usage | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | with how this routing takes place on a given PHG platform is not defined by these guidelines. If the APS is being formed by an application on a platform in which other applications may create APSs the value of SMSApplicationId may need to be managed.
    This value shall be ignored by the PHG application whenever the APB resource is obtained from the Health & Fitness services application. | +| APSState | See description of the element in Table 8-2 | + +**Table 8-2 – APB xml elements provided by Health & Fitness application** + +| Element | Usage | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HFSAPBI | Mandatory – The identifier for the HFS component of the authenticated persistent binding resource that was created. The HFSAPBI shall be represented as a string of size less than 2048 UTF-8 characters. The following characters shall not be present in the string: "/", "#", "+", "*". The Unicode NULL character may not be used.
    This value shall be ignored by the Health & Fitness services application whenever the APB resource is obtained from the PHG application. | +| PHGAPBI | Mandatory – The identifier for the PHG application component of the authenticated persistent binding resource that was created. The PHGAPBI shall be represented as a string of size less than 2048 UTF-8 characters. The following characters shall not be present in the string: "/", "#", "+", "*". The Unicode NULL character may not be used.
    This value shall be ignored by the Health & Fitness services application whenever the APB resource is obtained from the PHG application. | +| APExchangeURL | Mandatory – The URL to use when establishing the TLS session on which MQTT messages will be exchanged. The URI scheme shall be mqtt. The PHG application may need to change the URI scheme to work with a given MQTT client.
    This value shall be ignored by the Health & Fitness services application whenever the APB resource is obtained from the PHG application. | +| APSState | Mandatory – The state of the APS. The Health & Fitness services application shall set this element to NEW in response to a PHG application POST operation if the APS does not exist. If the Health & Fitness services application already has an existing APS in place with the PHG application, as determined by the authentication of the security credential, this value shall be set to ENABLED. The PHG shall set this value to TERMINATED to close and remove the persistent session with the Health & Fitness services application. The Health & Fitness services application shall support a valid XPath representation of the APSState element of the APS when setting the value of APSState. | +| expirationTime | Mandatory – The maximum time period that may elapse after the last POST to the APB resource by the PHG application, or the last activity on the message channel in which the peer PHG application was known to be active. If this time period is exceeded the Health & Fitness services application Should terminate the APS. However, if the APB resource is in the ENABLED state the Health & Fitness services application shall attempt | + +**Table 8-2 – APB xml elements provided by Health & Fitness application** + +| Element | Usage | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | to issue the ECHO management message before terminating the APS. The Health & Fitness services application Should not terminate the APS if a response is received to the ECHO message. (Note that the Health & Fitness services application may terminate an APS at any time though that action may not represent graceful behaviour.). This element shall be expressed as an ISO8601 duration – for example a 12 hour expirationTime is represented as PT12H. | +| requiredResponseTime | Mandatory – The maximum delay in seconds that the Health & Fitness services application can tolerate for a response to the ECHO message. This value provides the PHG application with information that it can use to determine how to best allocate APS resources. A PHG application Should Not establish an APS with a Health & Fitness services application if it is unable or unwilling to meet, in normal operation, the requiredResponseTime for an ECHO message. This element shall be expressed as an ISO8601 duration – for example a 10 second requiredResponseTime is represented as PT10S.
    This value shall be ignored by the Health & Fitness services application whenever the APB resource is obtained from the PHG application. | +| clientId | Conditionally required – This element shall be present if an exchangeMechanism of MQTT is selected. The clientId shall be used by the PHG application when it issues an MQTT CONNECT. The value of the clientId is generated by the Health & Fitness services application.
    This value shall be ignored by the Health & Fitness services application whenever the APB resource is obtained from the PHG application. | +| PHGCredential | Conditionally required – This element shall be present if an exchangeMechanism of MQTT is selected. The PHGCredential shall be used by the PHG application as the password when it issues a MQTT CONNECT.
    This value shall be ignored by the Health & Fitness services application whenever the APB resource is obtained from the PHG application. | + +``` + + + + + + APS lampreynetworks.com/private + MQTT privateMessageProtocol + SMS + + 441111223344 + 1234 + 4827351 + + + + HFSAPBI_1 + 5468233453aae3fd224 + mqtt://example.org:1883 + + + + NEW + PT50H + PT30S + RestPHG + PHGCredential55555 + + +``` + +**Figure 8-4 – Example of PHG application supporting MQTT and an SMS shoulder tap** + +## 8.2 APS behaviour + +### 8.2.1 APS session state + +An APS is in one of three states: NEW, ENABLED, or TERMINATED. A Health & Fitness services application **shall** only issue messages to a PHG application when the state of the APS is ENABLED. An APS is in the NEW state when it is first created during the APS establishment procedure. Once the PHG application agrees to establish the APS the PHG application moves the APS into the ENABLED state where it remains until either the PHG application or Health & Fitness application capability terminates it. See Table 8-2 for additional information on the APSState element in the APB resource. + +### 8.2.2 Authenticated persistent binding identifiers (APBI) + +During the establishment of an APS between a PHG application and a Health & Fitness services application, the Health & Fitness services application allocates and maintains a pair of identifiers for the life of the APS. One identifier in the pair is associated with an APS instance on the PHG application (PHG APBI) and the other identifier is associated with the APS instance in the Health & Fitness services application (Services APBI). The pair of identifiers is used, to bind the sending and receiving APS endpoints together. It is the responsibility of the Health & Fitness services application to manage the allocation of both the Services APBI and the PHG API such that every distinct APS that is created by the Health & Fitness services application can be uniquely identified by the pair of APBIs alone. Further, the Health & Fitness services application must assure that this unique APB resource is only exchanged with a PHG application possessing the security credential + +that was used when the APS was first created. The PHG APBI must be unique across the full set of existing APSs maintained by the Health & Fitness services application. + +### **8.2.3 Authenticated persistent binding establishment** + +APB establishment refers to the process by which the PHG application and the Health & Fitness services application exchange information in order to enable and configure the APS. An APB must be established before messages can be exchanged. The PHG initiates APS establishment after it completes capability exchange with a Health & Fitness services application and determines that the Health & Fitness services application supports the APS CCC. + +APB establishment requires that the PHG application authenticate itself to the Health & Fitness services application (acting as an OAUTH Authorization server) using some method that results in the PHG obtaining an authorized OAUTH bearer token. A successfully authenticated TLS connection in which the PHG application possesses a valid OAUTH access token represents mutual authentication for the purposes of an APS. + +When there has been mutual authentication the Health & Fitness services application has the required security credentials it needs in order to identify and associate an APS with a given PHG application, in this and all subsequent transactions. How the Health & Fitness services application uses the certificate to link the APS to a PHG application is up to the implementation. + +Within this mutually authenticated context, the PHG application establishes the APS by performing an HTTP POST to the Health & Fitness services application. The resource posted is an xml document containing the APB resource but the PHG application fills in only those elements as specified in Table 8-1. + +The element values provide the Health & Fitness services application with the information it needs to configure and allocate the internal resources needed to support the APS. The reply to this POST contains a URL to a modified version of the APB resource containing the Services-provided elements of Table 8-2. The PHG application then retrieves the APB resource via an HTTP GET to the provided URL. The Health & Fitness services application may refuse to establish an APS due to resource limitations. + +### **8.2.4 Accepting an authenticated persistent binding** + +The PHG application examines the response of the GET. If the parameters are acceptable to the PHG application, it establishes a secured connection to the MQTT server and sets up the MQTT link performing the necessary subscription and publishing actions. Upon successful completion of these steps, the PHG application shall indicate that it accepts the APS by performing an HTTP PUT to the Health & Fitness services application, using the URL provided in the POST response with APSState appended to it (URL/APSState). The value of the APSState element identified by the URL in the PUT operations shall be set to ENABLED. See clause I.4 for details. At this point the APS is enabled and the PHG application can receive messages. The Health & Fitness services application shall only update the APSState of its APB resource in this transaction. Should the PHG application provide an XPath that references something other than the Health & Fitness services application shall return an appropriate HTTP error. A PHG application may perform additional PUT operations to update the APSState of the APS as needed. + +### **8.2.5 Authenticated persistent binding and session termination** + +A PHG application may terminate the APS at any time by setting the APSState value to TERMINATED (see clause I.5). The PHG application should then perform appropriate operations to release resources used in association with the APS, including clearing the MQTT server (see clause 9.1.1). The APBI is no longer valid after the PHG application terminates the APS. The Health & Fitness services application may terminate the APS session if the PHG application has failed to renew the APS within the specified expirationTime interval, or due to a decision by the + +application logic. The Health & Fitness services application does not remove the APS session due to a termination of a transport connection. + +The Health & Fitness services application removes information that associated the APS with the authentication key such that if the PHG application initiated another APS capability exchange with the same authentication credential, the Health & Fitness services application can release resources associated with a terminated APS. Terminating an APS is an abortive process that may cause a currently in operation command to fail. + +An APS can be terminated by administrative procedures. + +### 8.2.6 APS-CCC diagnostic message + +The APS-CCC provides the basic framework by which application oriented CCCs can initiate message exchange from the Health & Fitness services application. These application oriented CCCs are expected to have well defined operations that are specific to the application's needs. These operations are out of scope for the APS-CCC + +The APS-CCC does define a message structure in order to support managing the APS-CCC itself. Only one command is defined for supporting the APS-CCC, the ECHO command. In future releases, other commands may be added. All entities implementing the APS-CCC **shall** support the management message ECHO command. + +#### 8.2.6.1 Diagnostic message structure for the APS-CCC message exchange + +##### 8.2.6.1.1 Payload + +The APS-CCC message exchange facility (MQTT) supports a diagnostic message format that defines a small set of commands that can be exchanged between APS-CCC peer entities. These commands are carried in the payload section of the diagnostic message. A diagnostic message shall contain only one command. The content of the payload depends upon the command. The diagnostic message shall be sent in Network Byte Order and has the layout shown in Table 8-3. + +**Table 8-3 – Fields of the APS-CDC diagnostic message** + +| Field Name | Description | Size in Bits | Values | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------| +| Operation
    Octet 0 | Identifies the operation to be performed. The two MSB bits in the operation field are reserved and shall be sent as 0 and ignored on reception. Responses to commands shall be formed by performing a logical OR of the command with 0x40. Thus a command of 0x03 causes a value of 0x43 to be returned in the operation field. | 8 | 0x00 – 0x3F: command
    0x40 – 0x7F: response
    0x80 – 0xFF: reserved | +| Handle
    Octet 1-4 | A handle shall be provided by the sender of the command and returned by the receiver. The handle is opaque to the receiver of the command. The sender shall not reuse a handle that is associated with an outstanding command. | 32 | | +| Status
    Octet 5 | The status field shall be present in both command and response messages. In commands it shall be | 8 | The validity of fields after the status field may not be reliable when the status | + +**Table 8-3 – Fields of the APS-CDC diagnostic message** + +| Field Name | Description | Size in Bits | Values | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | set to 0x00 by the sender, and ignored by the receiver. If the status field is not 0x00 in a response message the sender should not process the rest of the message. | | field is not 0x00. | +| Length
    Octet 6-7 | The payload length shall be present in all diagnostic messages. The length field shall be given in octets and represents the number of octets in the message payload from the first octet after the length field through the last octet of the message payload. | 16 | Since the payload field includes the 21 octets used to represent time the minimum value of length is 21. | +| Payload |

    The payload shall start with a fixed length subfield of 21 octets. This subfield holds the current value of time as being reported by the sender or responder to the command. The payload May contain additional octets of echo data. The sender of the ECHO command shall ensure that the length field properly identifies the number of octets of ECHO data.

    The time subfield shall be encoded as a string of UTF-8 characters and formatted in accordance with [ITU-T H.812.1] clause D.1.5 (Timestamping and time synchronization).

    Since the timestamp is reported in a fixed length field the fractions of a second component is NULL padded for each level of accuracy not reported in the timestamp.

    | Depends upon the command.
    Specified in the length field | If a receiver is able to detect a mismatch between the number of octets of data in the message and the length of the payload is should return an appropriate error code | + +NOTE – the term payload can be confusing since it is used in several contexts in this design guidelines document. The diagnostic message itself is the payload of an MQTT message. The payload here refers to the set of bytes that are associated with a given command instruction. For example, the payload of an ECHO command diagnostic message is a timestamp followed by an arbitrary string of bytes that is returned by the recipient. + +##### 8.2.6.1.2 Supported diagnostic message commands + +All diagnostic messages defined by these design guidelines have associated responses. The responding entity shall form a reply to a command by structuring the fields as documented in Table 8-3. The commands supported are identified below: + +###### ECHO + +(Operation field value of 0x01 for command and 0x41 for response) + +The ECHO command enables the Health & Fitness services application to determine if the PHG application is able to receive and respond to diagnostic messages and allows the Health & Fitness services application to obtain the PHG application's sense of time. + +The entity sending the ECHO command shall provide a payload in which the first 21bytes contain the time of the sender as defined above in Table 8-3. The remaining bytes, if any, may be set to any value of interest to the sender. The length field is set to the length of the ECHO payload. + +The responder to the ECHO command shall set the operation field to 0x81. + +The ECHO response shall contain the handle provided by the Health & Fitness services application from the corresponding ECHO command, the status field, the length field and the payload received from the ECHO command with the time field replaced by the time of the ECHO responder using the same format as defined for the sender. The ECHO response should be sent in an expeditious manner. The responder to the ECHO message shall examine the length field to determine if the sent value exceeds the implementation defined limit. If it does, it shall set the status code appropriately, and return the local time and the maximum number of additional bytes supported by the implementation. The payload length field shall reflect the number of bytes in the returned payload. If the implementation can support the number of bytes sent in the ECHO command it shall return the sent payload. All implementations shall support ECHO payloads that are less than or equal to 256 bytes. + +##### 8.2.6.1.3 Status field + +The status field is composed of a bit indicating valid time and a status code. The most significant bit in the status field is the time synchronized bit. It shall be set to indicate that valid NTP synchronized time, or equivalent, is being reported in the time field of the payload, and shall be cleared otherwise. + +The following status codes values are defined for the ECHO response + +- 0x0000 – Success – No error was detected in processing the command +- 0x0001 – Unknown Failure – The requested command was not successfully performed. The length field may be set to a positive value. When the length field is a positive value the payload contains a message of length bytes that may provide additional insight as to the error encountered. +- 0x0002 – Command not supported. The responding entity shall return this value whenever the value in the operation field (byte 0) of a received diagnostic message is not supported. +- 0x0003 – Length of command exceeds maximum supported value +- 0x0004 – Error in field values + +# 9 Behavioural model: MQTT + +MQTT [OASIS MQTT] is a required capability for applications that support the APS-CCC. This clause describes the usage of MQTT in supporting the transmission of messages in the context of an APS. + +## 9.1 Overview of operation + +The Health & Fitness services application for APS implements an MQTT server. The hostname or IP address and TCP port number of the server is provided in the APB resource. The exchange of messages between the PHG application and the Health & Fitness services application uses an MQTT server that is associated with the Health & Fitness services application, using the topics defined in clause 7.2. The following figure provides an overview of the exchanges between the PHG application and the Health & Fitness services application. The topic strings, as shown in Figure 9-1, are dependent on the PHG APBI, the services APBI and the message handlers used by different CCCs as described in the following clause. + +![Sequence diagram showing MQTT interactions between PHG MQTT client, Services MQTT server, and Services MQTT client. The diagram illustrates the connection, subscription, and message exchange process between the PHG and the services.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +The diagram illustrates the MQTT interactions between three entities: PHG MQTT client, Services MQTT server, and Services MQTT client. The sequence of events is as follows: + +- PHG MQTT client** establishes a secure TCP/IP connection based on the PHG being used. The login credentials and the connection ID are those specified by the PHG. +- PHG MQTT client** sends a **CONNECT** message to the **Services MQTT server**. +- PHG MQTT client** sends a **SUBSCRIBE** message for **topic =** to the **Services MQTT server**. +- PHG MQTT client** sends a **PUBLISH** message for **topic = payload = "CONNECTED"** to the **Services MQTT server**. +- Services MQTT client** sends a **CONNECT** message to the **Services MQTT server**. +- Services MQTT client** sends a **SUBSCRIBE** message for **topic =** to the **Services MQTT server**. +- Services MQTT client** sends a **SUBSCRIBE** message for **topic =** to the **Services MQTT server**. +- Services MQTT client** sends a **PUBLISH** message for **topic = payload = "CONNECTED"** to the **Services MQTT server**. +- A note indicates: **Services service is now aware that PHG is listening for unsolicited commands**. +- Services MQTT server** sends a **PUBLISH** message for **topic =** to the **PHG MQTT client**. +- A note indicates: **PHG processes the command internally**. +- PHG MQTT client** sends a **PUBLISH** message for **topic =** to the **Services MQTT server**. +- Services MQTT server** sends a **PUBLISH** message for **topic =** to the **Services MQTT client**. +- A note states: **NOTE – Exchanges between the services MQTT server and services MQTT client are for informative purposes and may not be present in a given implementation**. +- The diagram is labeled **H.812.4(16)\_F9-1**. + +Sequence diagram showing MQTT interactions between PHG MQTT client, Services MQTT server, and Services MQTT client. The diagram illustrates the connection, subscription, and message exchange process between the PHG and the services. + +**Figure 9-1 – PHG application and Health & Fitness services application MQTT client interactions** + +In clause 8.2, interactions are described from the point of view, respectively, of the PHG application and the Health & Fitness services application. It is important to note that how the Health & Fitness services application communicates with its MQTT server is up to the application. The only normative components of the APS interface are the exchanges between the PHG application and the Health & Fitness and MQTT services. + +### 9.1.1 Graceful APS termination + +When possible, a PHG application should terminate an APS gracefully. + +To terminate an APS gracefully the following steps shall be taken by the PHG application: + +- Establish a connection with the Health & Fitness services application that owns the APB resource defining the APS that is to be terminated +- Perform a PUT operation of an APB resource with the element set to TERMINATED to disable further use of the APS by the Health & Fitness services application. +- CLOSE any active connection used by the APS to exchange messages over MQTT. +- Perform an MQTT CONNECT with the clean session flag set to true (clears the PHG's subscriptions on the MQTT server), the state of the retained Will flag to cleared, and the Will topic and Will message absent (prevents the allocation of any resources to send a status message when the connection to the PHG application is lost). + +- Publish a zero length message to the status topic with the retain flag set to true to release the status resource. +- Disconnect from the MQTT server. + +## 9.2 Interaction of the Health & Fitness services application with the PHG application + +The Health & Fitness services application interacts with the PHG application via its associated MQTT server component. The precise way in which the Health & Fitness services application interfaces with its MQTT server is not specified in these guidelines. + +The Health & Fitness services application, if it has determined that a message is to be sent using the APS, sends this message by issuing a PUBLISH packet to the appropriate message topic. The MQTT server uses a QoS level of 2 when issuing the PUBLISH packet. + +If the Health & Fitness services application has a message to send and the status topic indicates that the PHG application is not connected, it may attempt to bring the connection back up (if the PHG application supports shoulder tapping) by sending the out of band shoulder tap. + +Informative Note: The Health & Fitness services application may subscribe to any APS response topics of interest. It may also subscribe to status topics, should it wish to track the online/offline status of its APSs. To listen for status updates from all APSs it can subscribe to the following wildcarded topic expression: + +``` +pcha/status//# +``` + +## 9.3 State of the PHG's connection to the HFS MQTT server + +Figure 9-1 documents the states that the status topic can be in and the events that cause transitions between states. + +![State diagram for the status topic showing three states: Inactive, Lost, and Closed, and one main state: Connected. Transitions are labeled with events like 'connect', 'terminate', 'lost', and 'close'.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Inactive + Inactive --> Lost : terminate + Inactive --> Connected : connect + Inactive --> Closed : terminate + Lost --> Inactive : lost + Lost --> Connected : connect + Closed --> Inactive : terminate + Closed --> Connected : connect + Connected --> Closed : close + +``` + +H.812.4(16)\_F9-2 + +State diagram for the status topic showing three states: Inactive, Lost, and Closed, and one main state: Connected. Transitions are labeled with events like 'connect', 'terminate', 'lost', and 'close'. + +Figure 9-2 – State diagram for the status topic + +Table 9-1 is a normative table that documents the states and state transitions of the status topic. The status topic is used by the Health & Fitness services application to track the status of the PHG application's connectivity to the APS. + +Table 9-1 – State table for the status topic + +| State | Event | Next state | Description | +|----------|---------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| INACTIVE | connect | CONNECTED | The PHG application has established an MQTT session by logging in with a new client ID and a clean session flag set to false. The PHG application publishes a message to the status topic with a payload content of CONNECTED. | + +**Table 9-1 – State table for the status topic** + +| State | Event | Next state | Description | +|-----------|-----------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CONNECTED | lost | LOST | The Health & Fitness (MQTT) service has detected a TCP disconnection or a timeout event due to the absence of MQTT ping messages. The Health & Fitness (MQTT) service will publish a Will message to the status topic containing a payload of LOST. | +| CONNECTED | close | CLOSED | The PHG application closes the MQTT connection (sends an MQTT DISCONNECT control packet) but does not terminate the MQTT session. The PHG application publishes a message to status topic with a payload of CLOSED prior to disconnecting. | +| LOST | connect | CONNECTED | The PHG application has reconnected to an MQTT session by logging in with its existing client ID and a clean session flag set to false. The PHG application publishes a message to status topic with a payload content of CONNECTED. | +| LOST | terminate | INACTIVE | The PHG application has decided to terminate the APS by logging in with its existing client id and setting the clean session flag to true. It signals this condition by publishing a zero length message to the status topic. It then logs out by sending an MQTT DISCONNECT control packet. | +| CLOSED | connect | CONNECTED | The PHG application has reconnected to an MQTT session by logging in with its existing client ID and a clean session flag set to false. The PHG application publishes a message to status topic with a payload content of CONNECTED. | +| CLOSED | terminate | INACTIVE | The PHG application has decided to terminate the APS by logging in with its existing client id and setting the clean session flag to true. It signals this condition by publishing a zero length message to the status topic. It then logs out by sending an MQTT DISCONNECT control packet. | + +### 9.3.1 Interaction of a PHG application with the MQTT server + +The PHG application establishes the APS session by performing an HTTP POST to the Health & Fitness services application in the context of a secure connection providing some security credential. Once the PHG application has received this information, it interacts with the Health & Fitness services application by creating a TLS connection with the MQTT server component associated with the Health & Fitness services application. + +Once it has established a TLS connection, the PHG application sends an MQTT CONNECT control packet to the MQTT server on that connection. The PHG application waits for a response from the MQTT server. If it receives a data packet that is not an MQTT connection acknowledgement, then the PHG application closes the TCP/IP connection. + +The PHG application sets the following fields in its MQTT connect message (normal connection). + +**Table 9-2 – Information contained in the PHG application's MQTT connect message** + +| Information element | Value set by the PHG | Comments | +|---------------------|---------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Flags | 0xEC |
    • – User name and password are present
    • – Retained Will message requested (with QoS 2)
    • – Clean session not requested
    | +| Keep Alive | Chosen by the PHG implementation | If no activity has taken place during a given keep alive time period the PHG application should send an MQTT PING to keep the connection open. It may set a value of 0 to indicate that it doesn't commit to send any PING messages | +| Client Identifier | A string provided by the Health & Fitness services application in the APB resource. | The MQTT server uses the client identifier to identify the MQTT session. When operating in the context of a particular APS the PHG application must always use the string specified by the Health & Fitness services application in the APB resource | +| Will Topic | The PHG's status topic | Topic used to track the status of the connection | +| Will Message | The string "LOST" | Payload of MQTT message that is to be generated (internal to the Health & Fitness services application) indicating that the PHG has gone offline unexpectedly. | +| User Name | The PHG APBI provided by the Health & Fitness services application in the APB resource | Used to authorize PHG application access to topics. | +| Password | The PHGCredential provided by the Health & Fitness services application in the APB resource | Used to authenticate the PHG application | + +The Will flag, Will Retain flag and Will Message ensure that the Health & Fitness services application is informed when communications with the PHG are unexpectedly disrupted. This notification process is internal to the implementation of the Health & Fitness services application, but is controlled by these parameters. The PHG application is required to set them to the values specified above. + +The MQTT Keep Alive value determines how quickly the MQTT server will detect the loss of connectivity to the PHG application. It also commits the PHG application to periodically send an MQTT PING packet if there has been no other activity. + +When it has received a positive connection acknowledgement from the MQTT server, the PHG application then proceeds to send MQTT SUBSCRIBE requests to its command topics. These command topics are qualified by the CCC message handler as shown in clause 7.2. The PHG application **shall** subscribe on behalf of all the message handlers it has advertised in the APB resource. It sets the information in the MQTT SUBSCRIBE request indicated in Table 9-3. + +**Table 9-3 – Information contained in MQTT SUBSCRIBE message** + +| Information element | Value | Comments | +|---------------------|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Topic | The command topic name | A set of topics from which the PHG application wishes to receive PUBLISH messages | +| Requested QoS | 2 | This allows the Health & Fitness services application to define the QoS level based on the value of QoS selected in the PUBLISH control packet | + +When it has received a positive SUBSCRIBE Acknowledgement from the MQTT server, the PHG application sends a PUBLISH control packet to update the *status* topic to show that it has come online. The publish status is sent with QoS 2. The message parameters are shown in Table 9-4. + +**Table 9-4 – Information contained in the PHG's Publish Status message** + +| Information element | Value | Comments | +|---------------------|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Retain Flag | True | Message is to be retained by the MQTT server so that later subscribers can be informed of the PHG application's current connection status | +| Topic | The status topic name | Topic that is tracking the connection state of the APS | +| QoS | 2 | | +| Payload | The string
    "CONNECTED"
    Or
    "CLOSED" | Status information to be sent to the Health & Fitness services application indicating that the PHG application associated with the APS is online
    Or
    Status information to be sent to the Health & Fitness services application indicating that the PHG application is disconnecting from the MQTT server but maintaining the APS enabled | + +There is a second type of publish status message defined in this standard. This message is used only when the PHG application is in the process of terminating the APS. The publish status message in this case has the retain flag set to true and an empty payload. The purpose of this message is to clear resources associated with the APS on the MQTT server. + +After the PHG application has completed the SUBSCRIBE operation it is ready to receive messages from the Health & Fitness services application. + +At this point the PHG application enables the APS performing an HTTP PUT operation to the URL provided by the Health & Fitness services application during APS establishment. The HTTP PUT contains the APB resource with the element value set to ENABLED. No message can be received before the PHG application enables the APS. + +When the PHG application has processed a message, it responds by sending an MQTT PUBLISH control packet indicated in Table 9-5. + +**Table 9-5 – Information contained in the PHG application's MQTT Publish Response message** + +| Information element | Value | Comments | +|---------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| Retain Flag | False | Message does not need to be retained once it has been delivered to the Health & Fitness services application | +| Topic | The response topic name | See Table 7-1. | +| QoS | 2 | The response shall be delivered exactly once | +| Payload | Dependent on entity using the APS service | Response to be sent to the Health & Fitness services application | + +If the PHG application detects loss of its MQTT connection, or loss of the underlying TCP/IP connection then it may attempt to reconnect immediately, following the process described at the beginning of this clause. If it is able to tell that the disconnection happened because of a total loss of network connectivity, then it should defer a reconnection attempt until the network is restored. + +The PHG application may elect to disconnect the MQTT connection while still maintaining the APS. In this case, the PHG application should publish a status update message, but with a payload of CLOSED rather than CONNECTED, prior to sending the MQTT DISCONNECT message. It may reconnect at a future time of its choosing. + +If the PHG application supports a shoulder tap mechanism it must attempt to reconnect when it receives a shoulder tap. + +Upon reconnection, the PHG application should be prepared to handle incoming messages immediately, since some messages might have been queued up for it during the time when it was disconnected. + +# 10 Behavioural model: SMS shoulder tap capability + +These guidelines define a capability that facilitates operation of the APS with networks that remove IP infrastructure for inactive connections. This capability is based on the short message service (SMS) as defined in [b-GSM/UMTS] and [TIA-637-C]. Future versions of these guidelines may provide different mechanisms to implement this capability as cellular network providers deploy additional services. + +## 10.1 Shoulder tap overview + +When there is no data exchanged between a Health & Fitness services application and a PHG application, both wireless network resources and PHG energy consumption can be reduced by tearing down the wireless data connection, resulting in a loss of IP connectivity. A wireless data connection can also be lost due to coverage issues, or lack of energy (available battery capacity) on a PHG. The loss of IP connectivity does not terminate the APS and when IP connectivity is re-established, the software entities bound by the APS can once again use the IP network to exchange information. + +This clause defines an out-of-band mechanism called a shoulder tap (ST), which the Health & Fitness services application can use to accelerate the re-establishment of IP connectivity. The mechanism can be used with any PHG application that has a cellular interface supporting SMS. + +Figure 10-1 presents a high level overview of the sequence of events in a shoulder tap. + +The first step of the ST process is an exchange of information between the PHG application and the Health & Fitness services application. This takes place during APS establishment. At some subsequent point in time, the network connection between the PHG application and the Health & Fitness services application is discontinued causing the underlying exchange mechanism to mark + +the connection as being lost. When an application activity using the APS-CCC requires the Health & Fitness services application to send a message, the Health & Fitness services application recognizes the fact that the IP connectivity to the PHG application has been lost. At this point it transmits a Shoulder Tap message to the PHG application using an out-of-band capability such as SMS to wake up the PHG. Receipt of the shoulder tap message informs the PHG application that the Health & Fitness services application wishes to exchange a message with it. The PHG application then re-establishes IP data connectivity and resumes message exchange with the Health & Fitness services application in the context of the APS. + +![Sequence diagram titled 'Shoulder tap overview' showing the interaction between a PHG device and a Services device. The sequence starts with the Services device sending 'Shoulder tap values communicated to WAN service (APB establishment)' to the PHG device. The PHG device then experiences an 'Event: APB TCP connection dropped at AHD interface'. The Services device then experiences an 'Event: Services service required to send unsolicited command'. It then detects that the APB status is in a LOST state. The Services device generates an out-of-band shoulder tap. The PHG application initiates activity to restore message exchange capability. Finally, the PHG receives the unsolicited command. The diagram is labeled H.812.4(16)_F10-1.](5414f65867392f05ba0063b208eeb5e1_img.jpg) + +``` + +sequenceDiagram + participant PHG device + participant Services device + Note right of Services device: Shoulder tap values communicated to WAN service (APB establishment) + PHG device->>PHG device: Event: APB TCP connection dropped at AHD interface + Note right of Services device: Event: Services service required to send unsolicited command + Note right of Services device: Services service detects that APB status is in LOST state + Services device->>PHG device: Services service generates out of band shoulder tap + PHG device->>Services device: PHG application initiates activity to restore message exchange capability + PHG device->>PHG device: PHG receives unsolicited command + Note right of Services device: H.812.4(16)_F10-1 + +``` + +Sequence diagram titled 'Shoulder tap overview' showing the interaction between a PHG device and a Services device. The sequence starts with the Services device sending 'Shoulder tap values communicated to WAN service (APB establishment)' to the PHG device. The PHG device then experiences an 'Event: APB TCP connection dropped at AHD interface'. The Services device then experiences an 'Event: Services service required to send unsolicited command'. It then detects that the APB status is in a LOST state. The Services device generates an out-of-band shoulder tap. The PHG application initiates activity to restore message exchange capability. Finally, the PHG receives the unsolicited command. The diagram is labeled H.812.4(16)\_F10-1. + +**Figure 10-1 – Shoulder tap overview** + +## 10.2 Scope + +The availability of an out-of-band shoulder tap mechanism is a function of the capabilities of the networks that the PHG application and the Health & Fitness services application are associated with, the capability of the Health & Fitness services application to initiate the shoulder tap and the capability of the PHG application to receive and process the shoulder tap. This implies that all entities including the Health & Fitness services application, the network, and the PHG application, must be able to operate in accordance with these guidelines to implement shoulder tap functionality. However, these guidelines only document the interface behaviour between the PHG application and the Health & Fitness services application as seen at the PHG's interface to the network. It is the responsibility of the system integrator to ensure that the required network infrastructure is in place to enable the Health & Fitness services application to meet the interface requirements defined here. + +## 10.3 Shoulder tap invocation determination + +It is possible that an active data connection is currently available to the PHG application so that a shoulder tap does not need to be invoked by the Health & Fitness services application. This can be determined by looking at the status of the connection state in the underlying message exchange facility. When using MQTT the connection state is maintained in the status topic. The shoulder tap should not be performed if the status topic already indicates that the connection is operational (CONNECTED state). + +## 10.4 PHG SMS information + +When a PHG application uses SMS shoulder tapping the PHG application communicates the following information to the Health & Fitness services application during APS establishment: + +- The supported types of shoulder tapping, which must include SMS +- The address (MSISDN) to which the SMS message is to be sent +- The port number used in the SMS user data header (UDH) to identify the UDH defined end point (port) that will receive the SMS message. +- A PHG application specified identifier that is returned to the PHG in the SMS payload. + +The Health & Fitness services application uses the PHG provided information to generate the SMS message as defined in this clause. In the event that a third party SMS provider is used to generate or deliver the SMS message to the PHG, the third party SMS provider is considered to be part of the Health & Fitness services application and proper behaviour at the PHG interface is determined by the structure of the SMS message delivered to the PHG by the third party provider. + +## 10.5 SMS message structure + +The Health & Fitness services application creates a SMS message as defined herein and sends the message toward the PHG. The following bullet points describe the SMS message as it is delivered to the PHG. + +- The message is a binary SMS message +- The message is delivered to the MSISDN provided by the PHG application. +- The SMS message contains a User Data Header and the transfer layer protocol data header indicator (TP-UDHI) bit is set. +- The layout of the SMS payload is shown in Figure 10-2. +- The SMSHeaderDstPort is encoded into the UDH + +NOTE – The corresponding source port associated with information element 0x04 in the UDH is not used by the PHG application. + +![Figure 10-2 – Payload of binary SMS message. The diagram illustrates the structure of an SMS payload, showing the User Data Header (UDH) and the User Data (UD) payload. The UDH is composed of a 'Fixed header always present' (Length, Format, IE) and 'SMSHeaderDstPort (from APB)' (Destination port, Source port). The UD payload consists of a 'Continua payload prefix' and 'Continua defined information elements' (CIE, CIE length, Payload).](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg) + +The diagram shows the structure of an SMS payload. At the top, a box contains 'UDH' (User Data Header) and 'UD payload' (User Data). Below this, a horizontal line labeled 'SMS payload' spans the entire width. The next section shows the 'User data header (UDH)' structure. It is divided into two main parts: 'Fixed header always present' and 'SMSHeaderDstPort (from APB)'. The 'Fixed header always present' part contains three fields: 'Length (0x6)', 'Format (0x5)', and 'IE (0x5)'. The 'SMSHeaderDstPort (from APB)' part contains two fields: 'Destination port' and 'Source port'. Below the UDH, the 'UD payload' is shown. It starts with 'Continua payload prefix (0x124D)' and 'Length'. The remaining part is 'Continua defined information elements', which includes 'CIE', 'CIE length', and 'Payload (length octets)'. + +Figure 10-2 – Payload of binary SMS message. The diagram illustrates the structure of an SMS payload, showing the User Data Header (UDH) and the User Data (UD) payload. The UDH is composed of a 'Fixed header always present' (Length, Format, IE) and 'SMSHeaderDstPort (from APB)' (Destination port, Source port). The UD payload consists of a 'Continua payload prefix' and 'Continua defined information elements' (CIE, CIE length, Payload). + +Figure 10-2 – Payload of binary SMS message + +The UDH is six octets long with the information in the header formatted in hexadecimal (0x05). The header contains one information element (value 0x05 – Application port addressing scheme, 16 bit addressing). + +The payload contains a Continua defined prefix value of 0x124D and a repeating sequence of Continua information elements (CIE) as defined in Table 10-2. + +**Table 10-1 – Structure of payload** + +| Field | Length | +|-------------------------------------------------------------------|-----------------| +| Continua Prefix '0001001001001101'b'0001001001001101'b
    =0x124D | 2 octets | +| Length of Shoulder tap payload excluding first three octets | 1 octet | +| Type of Information-element "A" | 1 octet | +| Length of Information-element "A" | 1 octet | +| Value of Information-element "A" | 0 to "n" octets | +| (repeated for other information elements as needed) | | + +**Table 10-2 – Continua information elements** + +| CIE type | Length | Requirement | MEANING | +|----------|--------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | 1-148 | optional | Shoulder tap application identifier – This value is communicated to the Health & Fitness services application in the APB element . In the SMS message it is encoded using UTF-8. | +| 01 | 1 | optional | Shoulder Tap Semantic – This value indicates the action that the PHG application should take upon reception of the shoulder tap. Currently defined values are:
    0x01: Re-establish transport level connectivity – The Health & Fitness services application wishes to send a message to the PHG application and is waiting for the transport level connectivity to be re-established. | + +## 10.6 PHG application requirements + +When the PHG application is running on an OS platform that processes the arriving SMS message, that platform will need to provide an interface to the PHG application that allows the PHG application to be notified when the binary SMS message arrives. The mechanisms used to notify the PHG application are not specified by these guidelines. + +## 10.7 Semantic behaviour of the PHG application relative to ST reception + +Upon receipt of a shoulder tap with Reason 'Re-establish connection to message exchange server', the PHG application shall re-establish its TCP connection to the HFS MQTT server and submit a CONNECT message. This procedure may need re-establishment of the connection to the packet-switched network. + +# Annex A + +## Normative guidelines for the APS-CCC + +(This annex forms an integral part of this Recommendation.) + +The tables in this annex list the guideline specifications for Continua certification of a PHG application and Health & Fitness services application that support Authenticated Persistent Sessions. + +## A.1 Guidelines for the APS components in capabilities exchange + +A Health & Fitness services application that supports an Authenticated Persistent Session (APS-CCC-Services) **shall** provide a root.xml file in accordance with Table A-1. A PHG application that supports an Authenticated Persistent Session (APS-CCC-PHG) is also required to support Table A-1. + +**Table A-1 – APS elements of capabilities exchange** + +| Name | Description | Comments | +|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC-Services
    _Root_Support | A Health & Fitness services application shall indicate that it supports the APS-CCC- Services by providing a profile with the value of the id element set to APS-CCC-Services in the root.xml file. | See Table 8-1 | +| APS-CCC-PHG_Root_Support | A PHG application that POSTs a root.xml file to a Health & Fitness services application during capability exchange shall provide a profile with the id element set to APS-CCC-PHG in the root.xml file. | See Figure 8-1. Note that APS-CCC- Services is replaced by APS-CCC-PHG. | +| APS-CCC- Services
    _Description_Information | A Health & Fitness services application shall describe the content of the APB resource using a entry in the root.xml in accordance with Figure 8-2. | This entry in the root.xml describes the content of the APB resource as well as referencing a validator for the formatting of the APB resource. | +| APS-CCC- Services
    POST_Location | A Health & Fitness services application shall provide a URL where the PHG application is to perform the initial POST to establish an APS in a
    entry in the root.xml in accordance with Figure 8-3. | | +| APS-CCC- Services
    _Resource_Prefix | The child element of the
    entry shall be present and the value shall be set to true. | The resource prefix is required to be present and true in this specification though it is optional in the hData specification. | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------| +| APS-CCC- Services _Profile_ID | The value of the
    described in Figure 8-3 and the value of the described in Figure 8-1 shall be set to APS-CCC. | The profileID element value of the section identifies the profile to which it is associated. | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------| + +## A.2 Guidelines for PHG APS management (APS-CCC-PHG) + +A PHG application that supports the Authenticated Persistent Session Certified Capability Class **shall** operate in accordance with Table A-2. + +**Table A-2 – APS management PHG** + +| Name | Description | Comments | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC-PHG_Initiate_APS_Establishment | If a PHG application indicates support for an APS during capability exchange then it shall initiate APB establishment by POSTing its APB resource. | These guidelines do not define the exact time by which the APS is to be established. However management services of the APS-CCC should be made available to the Health & Fitness service in a timely manner | +| _APS-CCC-PHG_POST_Location | A PHG application establishing an APS session shall POST the APB resource to the URL specified in the child element of the
    defined in Figure 8-3. | The PHG application obtains the URL for the POST in a
    element of the root.xml. Since there may be many sections in the root.xml, the element value identifies the correct
    . | +| APS-CCC-PHG_APB_POST_XML | A PHG application establishing an APS session shall POST the APB resource as an xml document | The APS is described by an APB resource which is expressed as an xml document. | +| APS-CCC-PHG_APB_Schema | A PHG application establishing an APS session shall always transmit APB resources in accordance with the APB resource schema of Appendix II. | | +| APS-CCC-PHG_APB_FILL | A PHG application establishing an APS session shall fill in elements of the APB resource in accordance with Table 8-1. | | +| APS-CCC-PHG_Supported_MH_List | The entries in the element shall be a space separated list. | The list may contain proprietary entries. | +| APS-CCC-PHG_APS_MH | A PHG application APSs shall include the string "APS" as one of the list entries in the supportedMH element of the APB resource. | This implies that all PHG applications will respond to APS-CCC defined management messages from the Health & Fitness services application. | +| APS-CCC-PHG_Supported_MX_List | The entries in shall be a space separated list ordered from the most desired to the least desired with the first element being the most desired by the PHG. | This guideline specifies the format of the listing in the element value | + +**Table A-2 – APS management PHG** + +| Name | Description | Comments | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC-PHG_MQTT_
    MX | The PHG application shall specify "MQTT" in its list of supported exchange mechanisms. | Continua compliant PHG applications implementing the APS-CCC must support MQTT. | +| APS-CCC-PHG_Supported_
    ST_list | The entries in shall be a space separated list ordered from the most desired to the least desired with the first element being the most desired by the PHG. | This guideline specifies the format of the listing in the element value | +| APS-CCC-PHG_ST_BASE | The PHG application shall provide an empty list for shoulderTapMechanism if it does not support a should tap mechanism | | +| APS-CCC-PHG_ST_SMS | If the PHG application supports SMS as a shoulder tap mechanism then the PHG application shall include the element in the APB resource | | +| APS-CCC-PHG_SMS_
    MSISDN | If the PHG application supports SMS as a shoulder tap mechanism then the PHG application shall include the number to reach the PHG application in the child element of the element in the APB resource | | +| APS-CCC-PHG_SMS_
    Destination_Port | If the PHG application supports SMS as a shoulder tap mechanism the PHG application shall include the port associated with the PHG application in the child element of the element in the APB resource | The source port and the source number do not need to be specified in the APB since the PHG application never sends an SMS message to the Health & Fitness services application. | +| APS-CCC-PHG_SMS_APP_
    ID | If the PHG application supports SMS as a shoulder tap mechanism the PHG application may include the child element of the element in the APB resource | This message contains an identifier that the PHG application can use to identify the received SMS message as being for itself. | +| APS-CCC-PHG_SMS_APP_
    ID_Limit | The PHG application shall not provide a string that when encoded in UTF-8 will exceed 148 octets for | | +| APS-CCC-PHG_SMS_
    APB_GET | A PHG application shall obtain the completed APB resource by invoking an HTTP GET using the URL provided by the Health & Fitness services application in response to the PHG application's successful POST request. | The PHG application gets a URL in the POST return. This URL identifies the location of the APB resource which the PHG application can obtain using an HTTP GET. | + +**Table A-2 – APS management PHG** + +| Name | Description | Comments | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC-PHG_Ignore_XML | A PHG application shall ignore any XML elements it does not understand in the APB. | Supports migration to future versions of the APB | +| APS-CCC-PHG_Process_HFS_Elements | On receipt of an APB resource from the Health & Fitness services application the PHG application shall only process the elements defined in Table 8-2. | The PHG application is defined to provide values for particular elements in the APB. If a Health & Fitness services application incorrectly updates the values for these elements the PHG should ignore them. | +| APS-CCC-PHG_APS_ENABLE | The PHG application shall invoke an HTTP PUT of the APB/APSSState resource with the value set to ENABLED to indicate it is ready to accept messages | | +| APS-CCC-PHG_APS_Termination | A PHG application shall indicate that the APS is terminated by invoking an HTTP PUT on the current APB resource with the element value set to TERMINATED. | This action is the first step taken in APS termination. | +| APS-CCC-PHG_immutable | An APB resource obtained from a Health & Fitness services application shall not be modified except for the element | The PHG cannot modify fields of the APB resource and communicate those back to the Health & Fitness services application | + +## **A.3 Guidelines for the PHG application interactions with the MQTT server** + +Table A-3 covers the interaction of the PHG application with respect to MQTT exchanges. A PHG application implementing the APS-CCC-PHG shall operate in accordance with Table A-3. + +**Table A-3 – PHG-MQTT exchanges** + +| Name | Description | Comments | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC-PHG_Message_Exchange | A PHG application shall support the use of MQTT as a method of message exchange | Future versions of these guidelines may support other methods of message exchange. | +| APS-CCC-PHG_MQTT_conformance | A PHG application shall be compliant with the requirement for a client as specified in MQTT | | +| APS-CCC-PHG_MQTT_Connect_URL | A PHG application's MQTT client shall use the information identified in the element of the APB resource in order to establish the transport connection to the MQTT server. | The Health & Fitness services application indicates to the PHG application the URL that allows it to connect to the MQTT server in the element value. See Table 8-2. | + +**Table A-3 – PHG-MQTT exchanges** + +| Name | Description | Comments | +|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC-PHG_MQTT
    APS_Connect_Setup | The MQTT client component of the PHG application shall issue the MQTT CONNECT control packet in accordance with Table 9-2. | The APS requires specific MQTT settings to be used in a CONNECT control packet. | +| APS-CCC-PHG_MQTT
    Connect_User_Name | A PHG application shall use the value of the element provided by the Health & Fitness services application in the APB resource as the user name in the MQTT connect message. | See Table 8-2 | +| APS-CCC-PHG_MQTT_
    Connect_Password | A PHG application shall use the value of the element provided by the Health & Fitness services application in the APB resource as the password in the MQTT connect message. | See Table 8-2 | +| APS-CCC-PHG_MQTT_
    Client_Identifier | A PHG application shall use the value of the element provided by the Health & Fitness services application in the APB resource as the client identifier in the MQTT connect message. | See Table 8-2 | +| APS-CCC-PHG_MQTT_
    Connect_Will_Topic | A PHG application shall set the Will topic of the connect message to the status topic for this APS as defined in Table 7-1. | The setting tells the MQTT server to publish the Will Message on the status topic when the connection to the PHG application is lost. | +| APS-CCC-PHG_MQTT
    APS_Connect_Will_
    Message | A PHG application shall set the Will message of the connect message to "LOST" | A LOST message will be sent to the Health & Fitness services application if connection to the PHG application is lost. | +| APS-CCC-PHG_MQTT_
    Normal_Connect_Flags | A PHG application shall set the flags field of the connect control packet to indicate that the user name and password are present, that a clean session is NOT requested, and that a retained WILL message is requested. | The MQTT connection is to require a user name and password login, a retained WILL message, with no clean session. The latter indicates that any messages for the PHG application will be received once the connection is complete and the PHG application has completed its subscription to the command topic | +| APS-CCC-PHG_PHG_
    Command_Subscribe | A PHG application shall subscribe to the message topics as defined in Table 7-1. | | +| APS-CCC-PHG_Subscribe_
    QoS | A PHG application shall set the QoS of the message topic subscription requests to 2 in accordance with Table 9-3. | | + +**Table A-3 – PHG-MQTT exchanges** + +| Name | Description | Comments | +|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC-PHG_PHG
    Subscribe_All_Supported_
    mh | A PHG application shall subscribe to all message topics for message handlers that it has indicated support for in its element value. | Since the PHG application does not know which CCCs are supported by the Health & Fitness services application, it needs to subscribe to all of them. | +| APS-CCC-PHG_Publish_
    Status_Topic | A PHG application shall publish on the status topic for this APS as defined in Table 7-1. | | +| APS-CCC-PHG_Status
    Publish_Retain | A PHG application shall issue a PUBLISH control packet in accordance with Table 9-4 when writing values to the status topic. | In the case where the PHG is retaining the APS in the enabled state, publishing is done with the retain flag true. | +| APS-CCC-PHG_Clear_
    Queue | A PHG application shall set the retain flag of the PUBLISH control packet to true when setting the payload to a zero-length message. | In the case where the PHG is terminating the APS, publishing is done with the retain flag true since the publishing is to clear any outstanding status messages. See clause 9.1.1. | +| APS-CCC-PHG_Status_
    Publish_QoS | A PHG application shall set the QoS level of the PUBLISH control packet on the status topic message to 2 | A QoS of 2 applies to all PUBLISH control packets | +| APS-CCC-PHG_Status_
    Publish_Payload_Values | A PHG application shall set the Payload of the PUBLISH control packet on the status topic to one of either "CONNECTED" or "CLOSED" or be of zero-length. | In these Guidelines the status message payload published by the PHG application may take on one of the following values "CONNECTED", "CLOSED" or of zero length, the last of which is used only in the case of clearing MQTT when the APS is terminated by the PHG application. | +| APS-CCC-PHG_Response_
    Publish_Topic | A PHG application shall PUBLISH on the response topic in accordance with Table 9-4. | The response topic is specified in Table 7-1. The proper substitutions must be made. | +| APS-CCC-PHG_Response_
    Publish_Retain | A PHG application shall set the retain flag to false when publishing on a response topic | The message does not need to be retained since it has been delivered to the Health & Fitness services application. The MQTT server is internal to the Health & Fitness services application. | +| APS-CCC-PHG_Response_
    Publish_QoS | A PHG application shall set the QoS level of the PUBLISH control packet on a response topic message to 2 | A QoS of 2 applies to all PUBLISH control packets | +| APS-CCC-PHG_ECHO_
    Support | A PHG application shall support the APS-CCC-HFS diagnostic message ECHO command as described in clause 8.2.6. | | +| APS-CCC-PHG_Status_ | A PHG application shall manage the status topic in accordance with Table | | + +**Table A-3 – PHG-MQTT exchanges** + +| Name | Description | Comments | +|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Behaviour | 9-5. | | +| APS-CCC-PHG_Status_Publish_Clear_MQTT | A PHG application shall set the status topic to INACTIVE when it successfully connects to the MQTT server under the conditions of setting the clean session flag to true with a payload of zero-length and a retain flag set to true. | This guideline defines the publish action of the PHG after connecting to MQTT server to clear it of resources. This status update is part of a sequence of events that take place when the PHG has terminated the APS. | +| APS-CCC-PHG_Graceful_APS_Termination_Procedure | A PHG application shall terminate an APS following the procedure in clause 9.1.1. | This guideline intends to validate that the graceful APS termination procedure follows all the steps in clause 9.1.1 in order; terminate the APS on the APS management connection, put the MQTT server into the LOST or CLOSED state if not already in the LOST or CLOSED state, connect using the clear-connect configuration, publish using the clear-status configuration, and close the MQTT connection. | + +## A.4 Guidelines for HFS application APS management + +The Health & Fitness services application configures several elements of the APB resource for the APS. It is also responsible for assuring that a given APS is associated with a given security credential where the security credential identifies the PHG that is authenticated to use the APS. A Health & Fitness services application implementing the APS-CCC-HFS shall operate in accordance with Table A-4. + +**Table A-4 – APS management requirements for the Health & Fitness services application** + +| Name | Description | Comments | +|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC- Services_Enforce_Authorized_APS_Access | A Health & Fitness services application shall assure that the APB resource created to represent a given APS can only be accessed by an entity possessing the security credential that was used to establish the APS. | This guideline requires that the Health & Fitness services application assure that any reconnection made by the PHG application for APS management is only able to operate within the APS authorized for the PHG application. | +| APS-CCC- Services_Enforce_Topic_Space_Access | A Health & Fitness services application shall enforce access control to the topic space as defined in clause 7.2. | | +| APS-CCC- Services_XPath | A Health & Fitness services application shall support references to the element defined in the APB when this reference is expressed in accordance with [XPath 2.0]. | | + +**Table A-4 – APS management requirements for the Health & Fitness services application** + +| Name | Description | Comments | +|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC- Services _ MQTT_Support | A Health & Fitness services application shall support the use of MQTT as a mechanism for APS message exchange. | How the Health & Fitness services application interacts with the MQTT server is implementation dependent but the interface exposed to the PHG application is that specified by the MQTT standard. | +| APS-CCC- Services _ APS_Management_Support | A Health & Fitness services application supporting the APS-CCC shall support the APS management messages defined in clause 8.2.6.1.1. | | +| APS-CCC- Services _ APB_POST_RESPONSE_APB_CREATED | If a Health & Fitness services application creates an APS with the PHG application it shall set the return code to 201 | | +| APS-CCC- Services _ APB_POST_RESPONSE_APB_NOT_CREATED | If a Health & Fitness services application does not create or update an APB on a client request to do so, it shall return an appropriate status code in either the 400 group or 500 group. | | +| APS-CCC- Services _ Process_Services_Elements | On receipt of an APB resource from the PHG application the Health & Fitness services application shall only process the elements defined in Table 8-1. | | +| APS-CCC- Services _ Ignore_XML | A Health & Fitness services application shall ignore any XML elements it does not understand in the APB. | Supports migration to future versions of the APB | +| APS-CCC- Services _ No_Modify | A Health & Fitness services application shall not modify any elements in Table 8-1 when presenting or processing the elements of the APB. | | +| APS-CCC- Services _ APB_Schema | A Health & Fitness services application establishing an APS session shall always transmit APB resources in accordance with the APB Resource Schema of Appendix II. | | +| APS-CCC- Services _ Unique_PHGAPBI | A Health & Fitness services application shall create an element value that is unique across all APSs that are known to be valid for the Health & Fitness services application. | At any given time, if the Health & Fitness services application has N APSs, the value of each one of the N associated APB resources must be unique. This requirement does not exclude the reuse of a value from an APS that was terminated. | + +**Table A-4 – APS management requirements for the Health & Fitness services application** + +| Name | Description | Comments | +|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC-Services _
    PHGAPBI _
    Constraints | The Health & Fitness services application shall restrict the element's value according to the PHGAPBI entry in Table 8-2. | | +| APS-CCC-Services _
    HFSAPBI _
    Constraints | The Health & Fitness services application shall restrict the element's value according to the HFSAPBI entry in Table 8-2. | | +| APS-CCC-Services _
    Unique_ClientId | A Health & Fitness services application shall create a value that is unique across all APSs currently in service. | Recall that this value serves as the MQTT PHG client identifier. | +| APS-CCC-Services _
    ClientId_Constraints | A Health & Fitness services application shall restrict the value according to the clientId entry in Table 8-2. | The current MQTT specification restricts the length of the string to be 23 UTF-8 characters. | +| APS-CCC-Services _
    NEW_APSState | The Health & Fitness services application shall set the value to NEW if the PHG application does an HTTP POST and there exists no APS for the given security credential. | When the Health & Fitness services application handles a POST from the PHG application and no APS currently exists for that security credential, the Health & Fitness services application will need to complete the APB resource POSTed by the PHG and in that case the state is set to NEW. | +| APS-CCC-Services _
    ExpirationTime | A Health & Fitness services application shall provide an expiration time in the element value which represents the time duration for which the Health & Fitness services application will tolerate inactivity. | This value represents the length of time the Health & Fitness services application will accept no activity from the PHG application within the APS before testing the PHG application to see if it is still engaged. After this time if the Health & Fitness services application receives no timely response to a APS "ECHO" management message after a shoulder tap wake up OR the PHG application does not respond to the shoulder tap wake up, the Health & Fitness services application may terminate the APS | +| APS-CCC-Services _
    ResponseTime | A Health & Fitness services application shall provide a required response time to a APS "ECHO" management message in the element value which represents the duration in time for which it is prepared to wait for a response to the ECHO. | This value represents how long a PHG application has to respond to a UC "ECHO" message before the Health & Fitness services application considers the PHG application out of service at which time the Health & Fitness services application may terminate the APS. | + +**Table A-4 – APS management requirements for the Health & Fitness services application** + +| Name | Description | Comments | +|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-SUPPORT-TERMINATE | A Health & Fitness services application shall support the termination of an APS as defined in clause 8.2.5. | | +| APS-CCC-Services _MQTT_URL | A Health & Fitness services application shall provide the URL to the Health & Fitness service MQTT end point in the element value. | | +| APS-CCC-Services _APB_EXISTS | If the PHG application invokes an HTTP POST and an APS already exists for the security credential the Health & Fitness services application shall ignore the contents of the POST and return the URL to the existing APB. |

    A PHG application that performs a POST to recover an APB using a security credential associated with an existing APB will get the already existing APB resource. The value of the APSState element in this case is set to ENABLED. It is advisable to check the state of APSState to ensure the expected value is returned.

    Note that when an APB already exists on the Health & Fitness service device, it will ignore all information the PHG includes in the APB POST. Therefore, when the PHG receives an APB with APSState set to ENABLED, it should check that all PHG related details in the APB are still correct. If the PHG related details are not correct anymore the PHG will first need to terminate this existing APB and subsequently create a new APB with updated information.

    | +| APS-CCC-Services _APB_URL | A Health & Fitness services application shall respond to a HTTP POST that successfully created an APB resource with a URL that points to the APB resource | | +| APS-CCC- Services _Provide_APB | A Health & Fitness services application shall provide the completed APB resource when the PHG application performs a GET using the POST URL. The POST URL is the URL returned by the Health & Fitness services application in response to the PHG applications POST operation. | When the PHG application does an HTTP GET for the APB resource, the Health & Fitness services application delivers the APB resource that the PHG application has been authenticated to operate with. | + +**Table A-4 – APS management requirements for the Health & Fitness services application** + +| Name | Description | Comments | +|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APS-CCC-Services _ NO_APB_GET | If a PHG does an HTTP GET for the APB resource but the Health & Fitness services application finds no APB resource that is authorized for use by this PHG application, the Health & Fitness services application shall respond with code 404 resource not found. | This case could happen, for example, when a trusted PHG has neglected to do a POST but still has the correct URL to point to the resource. | +| APS-CCC-Services _ APSState_Update | A Health & Fitness services application shall update the element value of the APB resource to the element value sent by the PHG application in an HTTP PUT transaction if the value is either ENABLED or TERMINATED, otherwise it shall return the status code 403 | | +| APS-CCC- Services _ APSState_Only | A Health & Fitness services application shall ignore all values in the APB resource except the element value sent by the PHG application in an HTTP PUT transaction. | | +| APS-CCC-Services _ NO_APB_PUT | If a PHG application does an HTTP PUT of an APB resource but the Health & Fitness services application finds no existing APB resource authenticated for use by the PHG application, the Health & Fitness services application shall respond with code 404 resource not found | | +| APS-CCC-Services _ WAIT_FOR_ENABLE | A Health & Fitness services application shall refrain from sending messages to a PHG application until the is set to ENABLED | Though the PHG application is technically able to receive messages as soon as it has connected and subscribed to the message topic, no message are sent until the APS state has been set to enabled. Only the PHG application can set the state. The PHG application does not set the state to enabled until it is ready to handle messages. | +| APS-CCC-Services _ APB_Remove_On_Terminate | A Health & Fitness services application shall terminate the APS associated with the APB when the PHG sets the to TERMINATED. The Health & Fitness services application shall ensure that a MQTT connection based on the terminated APB resource will fail | | + +**Table A-4 – APS management requirements for the Health & Fitness services application** + +| Name | Description | Comments | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| APS-CCC-Services _ ExpirationTime | A Health & Fitness services application shall operate in accordance to Table 8-2 relative to inactivity exceeding | See Table 8-2, | + +## A.5 Guidelines for the PHG application SMS shoulder tap + +A PHG application implementing the APS-CCC-PHG **shall** operate in accordance with Table A-5. + +**Table A-5 – SMS shoulder tap PHG** + +| Name | Description | Comments | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| APS-CCC-PHG_ST_Missing_ID | If the PHG application supports a shoulder tap using SMS, and it provides a SMSApplicationId then it shall ignore all messages that do not contain the application identifier it set in the APB resource. | The identifier is a number the PHG application created in order to identify the SMS message as being for itself. | +| APS-CCC-PHG_ST_Reestablish | If the PHG application supports shoulder tap using SMS, then it shall attempt to re-establish TCP connectivity with the Health & Fitness services application when a SMS message containing the CEI of 01 (Re-establish transport level connectivity) is received. | This guideline assumes the message is addressed to the address and port specified in the APB resource. | + +## A.6 Guidelines for the Health & Fitness services application SMS shoulder tap + +A Health & Fitness services application implementing the APS-CCC-Services shall operate in accordance with Table A-6. + +**Table A-6 – HFS application SMS shoulder tap** + +| Name | Description | Comments | +|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| APS-CCC- Services _ST_Send_Contents | If the Health & Fitness services application supports shoulder tap using SMS, then when generating the shoulder tap message it shall : a) use the MSISDN and SMSHeaderDstPort elements within the APB resource, and b) include the shoulder tap payload. | | +| APS-CCC- Services _ST_Format | A Health & Fitness services application shall format the Shoulder Tap payload as specified in clause 10.5. | This guideline specifies details such as the presence of the Continua header and TLV messages | +| APS-CCC- Services _ST_Include_APP_ID | A Health & Fitness services application shall include the element value of the APB resource in the payload of the SMS in accordance with clause 10.5. | This value is a means for the PHG application to identify the SMS message as being for itself. | + +# Annex B + +## XML schema for the APB resource + +(This annex forms an integral part of this Recommendation.) + +The XML structure as seen by the PHG application performing the GET of the APB is as follows. + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +# Appendix I + +## APS details + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 APS information in the root.xml + +A PHG obtains information regarding the capabilities supported by a Health & Fitness services application through examining the Health & Fitness services application's hData defined resource layout. This information is obtained through the root.xml file that is made available by the Health & Fitness services application using the capability exchange facility documented in [ITU-T H.812.3]. + +A Health & Fitness services application that supports the APS includes three entries related to the APS in its root.xml. The first entry indicates to the PHG application that the APS capability is supported. This entry is provided in a profile element and appears as shown in Figure 8-1. + +A second entry provides both a reference to and a validator (such as an xml schema) for the APB descriptor (such as an xml schema). This entry is provided in a resourceType element and appears as shown in Figure 8-2. + +The third entry provides the URL the PHG application is to use when it wishes to establish an APS with the Health & Fitness services application. This URL is where the PHG application POSTs a description of its APS related capabilities. This entry is provided in a section element and appears as shown in Table 8-3. + +NOTE – The Continua Certified Capability Classes (CCC) documented in the root.xml are not the message handlers supported by the PHG application. These are found in the APB resource. The Health & Fitness services application does not expose which protocols will use the APS service. + +## I.2 APS authentication: Resource owner password credentials approach + +There are several techniques for associating an APS with a security credential. The following description illustrates the use of the resource owner password credentials as a method of obtaining access to the APB resource associated with the APS. For additional details see Annex B of [ITU-T H.812]. + +Once the PHG application determines that the Health & Fitness services application supports creating an APS through capability exchange, the PHG application can initiate the process of APS establishment. The first step in this process is for the PHG application to validate the Health & Fitness services application through establishing a TLS connection with the Health & Fitness services application. The PHG application may be aware of several different URLs associated with the Health & Fitness services application. In this case we assume that the PHG application and Health & Fitness services application have exchanged information relative to an authentication service. The login service accepts a username/password (resource owner credentials) from the PHG application and if these match returns an OAUTH access token of type bearer. With this access token in hand the PHG application is able to perform HTTPS operations to obtain the APB resource associated with the Authenticated Persistent Session service advertised in the root.xml file. + +### I.3 APS establishment: PHG application POST with partial APB + +Once the connection has been established the PHG application does a POST to the URL provided in the root.xml of the Health & Fitness services application. The POST contains an xml document describing the PHG application's APS capabilities (Table 8-1) as shown in Figure I-1. + +``` + + + + APS lampreynetworks.com/private + MQTT privateMessageProtocol + SMS + + 441111223344 + 1234 + 4827351 + + +``` + +**Figure I-1 – Example APB posted by PHG application** + +The Health & Fitness services application can examine the space separated list of supported message handlers in the element to see if the PHG application supports services that the Health & Fitness services application can issue message to. The Health & Fitness services application can also inspect the space separated list of exchange mechanisms and the space separated list of shoulder tap mechanisms. If the Health & Fitness services application supports a transfer mechanism advertised by the PHG application, the Health & Fitness services application will be able to establish an APS. In this case the Health & Fitness services application responds with an appropriate HTTP code such as 201 CREATED and provides a URL to the authenticated persistent binding (APB) resource. If the PHG application does not support any CCCs or transfer mechanisms that the Health & Fitness services application supports, the Health & Fitness services application responds with an HTTP error code such as 501 (Not Implemented). + +#### I.3.1 APS establishment: PHG GET for completed APB + +The PHG application can then issue a GET request for the APB resource. The PHG application must properly format the resource path according to the entry in the root.xml. The Health & Fitness services application creates the APB resource for the APS. The APB resource created is associated with the authentication credentials of the PHG application. The Health & Fitness services application fills in the remaining elements of the xml document describing the APB resource in accordance with Table 8-2. + +The resulting APB, as would be obtained by the PHG using the GET operation, is outlined in Figure I-2. + +``` + + + + + + APS lampreynetworks.com/private + MQTT privateMessageProtocol + SMS + + 441111223344 + 1234 + 4827351 + + + + HFSAPBI + + PHGAPBI + + address to the MQTT server + + NEW + + expirationTime + + requiredResponseTime + + clientId + + PHGCredential + + +``` + +NOTE – This example includes a private message handler (lampreynetworks.com/private) as well as the required APS message handler. + +###### Figure I-2 – APB created by Health & Fitness service application + +The Health & Fitness services application may want to configure the MQTT software component at this time. This standard does not specify how the Health & Fitness services application interacts with the MQTT server. The PHG application will publish on the response and status topics. How the Health & Fitness services application obtains this information is out of the scope of this design guidelines document. + +#### **I.3.2 APS establishment: PHG setup with MQTT server** + +Once the PHG application receives the APB resource, it needs to establish a secured connection with the MQTT server. The address of the MQTT server is provided in the APB resource. + +The MQTT CONNECT command flags are used in a manner to indicate that a username and password are present, that the Will message will be retained, and that the session is not to be cleaned (this means that undelivered messages will be persisted across teardowns of the TCP connection) as defined in Table 9-2. These settings allow a previously published message on a topic to be received once the PHG application subscribes to that topic. The user name and password are the PHGAPBI and PHGCredential, respectively, provided in the APB resource. The MQTT protocol requires that the PHG application provide a client identifier. The client identifier is provided in the clientID element of the APB resource. The PHG application also specifies a keep alive time which states how long it may remain inactive before issuing an MQTT PING. Specifying a 0 indicates that the PHG application will not send PING packets. The PHG application also sets the WILL message flag. This parameter indicates what the MQTT server will do when the connection to the PHG application is lost. The PHG application sets the WILL parameters to use the status topic with a payload "LOST". Thus when the connection to the PHG application is lost, the MQTT server will publish a message to the status topic with the payload "LOST". + +#### **I.3.3 MQTT: PHG application subscribes to commands** + +Once connected, the PHG application subscribes to the message topic for each CCC it is interested in receiving messages from. A single message topic is specified as follows: + +``` +pcha/message/HFSAPBI/PHGAPBI/mh +``` + +where the HFSAPBI and PHGAPBI are provided in the APB resource and the 'mh' parameter is the CCC that is to receive the message. An example message topic may appear as follows: + +``` +pcha/message/HFSAPBI/6d296e99-e5dc-43d0-b455-7c1f3eb35d83/APS +``` + +#### **I.3.4 MQTT: PHG Application Publishes "CONNECTED"** + +When all the subscriptions are completed the PHG application publishes a message on the status topic + +``` +pcha/status/HFSAPBI/6d296e99-e5dc-43d0-b455-7c1f3eb35d83 +``` + +with the payload "CONNECTED". At this time, the PHG application is technically able to receive commands from the Health & Fitness services application. However, there is an additional requirement that the Health & Fitness services application refrain from sending any messages until the PHG application enables the APS. + +### **I.4 APS establishment: PHG application enables APS** + +Enabling the APS requires that the PHG application perform a PUT operation to the URL provided in the POST response (response\_URL) appended with the XPath representation of the APSState element. (e.g. created\_APS\_resource\_URL/APSState). The mime type is set to application/text and the http body contains the text ENABLED. + +The Health & Fitness services application responds with success (200 OK) if it is able to change the APSState. + +### **I.5 Operation** + +At this point, the PHG application can receive messages for all message strings it has subscribed handlers to receive messages for. The PHG application is able to identify which CCC the message payload is for by examining the 'mh' component of the message topic. After handling the message, + +the PHG application responds by publishing a response-topic message with the payload returned from the CCC (if any). + +The PHG application is allowed to disconnect from the MQTT server maintaining the APS session; the APS session is still enabled but the PHG application will not be able to receive messages. The Health & Fitness services application will discover that the connection is in the "CLOSED" state by the reception of a CLOSED message on the status topic. The PHG application can re-establish the connection at any time by re-invoking the MQTT connect sequence. The PHG application will publish "CONNECTED" on the status topic when it successfully establishes the MQTT client connection. + +However the more likely situation for the PHG application reconnecting is that the Health & Fitness services application wakes up the PHG application using one of the mutually supported shoulder-tap mechanisms because the Health & Fitness services application needs to send a message. + +If there has been no activity for the APB resource for , the PHG application may receive an ECHO ('APS') management message from the Health & Fitness services application. The PHG application informs the Health & Fitness services application that it is still alive and connected by publishing on the response topic the response to the "ECHO" command. The Health & Fitness services application expects to be notified of this response within the specified in the APB resource. If the PHG application is not connected at the time the Health & Fitness services application may choose to use the shoulder tap process in order to re-establish transport level connectivity. + +At any time the PHG application can terminate an APS by performing a PUT operation in the same manner as when it enabled the APS but in this case setting the element value of the APB resource to TERMINATED. The PHG application terminates the APS by clearing the MQTT server of any outstanding commands and UNSUBSCRIBES to associated response and status topics. Both sides may terminate the APS for administrative (out of band) reasons. + +Once terminated, the Health & Fitness services application removes information that associated the APB resource with the PHG application's authentication credential so that if the PHG application initiated another APS establishment procedure with the same authentication credential, the Health & Fitness services application would return NEW for the APSState element value. + +# Appendix II + +## Example Health & Fitness service root.xml file + +(This appendix does not form an integral part of this Recommendation.) + +The following XML code is an example of a Health & Fitness service root.xml file. + +``` + + + APS-CCC-HFS + + http://handle.itu.int/11.1002/3000/hData/APS/2017/01/H.812.4.pdf + + + + + APB + + + http://handle.itu.int/11.1002/3000/hData/APS/2017/01/H.812.4.pdf + + + application/xml + + + http://handle.itu.int/11.1002/3000/hData/APS/2017/01/APBConfigResource.xsd + + + + +
    + APB/ + APS-CCC-HFS + + true + APB +
    +``` + +# **Bibliography** + +For a list of non-normative references and publications that contain further background information, see [ITU-T H.810]. + + + + + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.820-201808-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.820-201808-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bcda2c01451dbc3cddbdce7f60f1edcb3cde5e9 --- /dev/null +++ b/marked/H/T-REC-H.820-201808-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e18e4f38b75cc1dacb67027b5abc017d0596259f8f138890e9c4ea02887a12b +size 4177 diff --git a/marked/H/T-REC-H.820-201808-I_PDF-E/raw.md b/marked/H/T-REC-H.820-201808-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3db43bea2024e2ad9d7a1d05e862598600577cd5 --- /dev/null +++ b/marked/H/T-REC-H.820-201808-I_PDF-E/raw.md @@ -0,0 +1,575 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.820** + +(08/2018) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +# --- **Conformance of ITU-T H.810 personal health system: Conformity assessment test plan** + +Recommendation ITU-T H.820 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.820 + +# Conformance of ITU-T H.810 personal health system: Conformity assessment test plan + +## Summary + +Recommendation ITU-T H.820 provides a top-level overview of the test specifications and test profiles used to verify product conformance to the Continua Design Guidelines (CDG) that are defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2017) is the base Recommendation. It outlines the scope of the conformance and interoperability tests, test suite structures (TSS) and test purposes (TP), the test case reference list and the Continua test tool, which in turn are specified in detail in the Recommendations of the ITU-T H.820-H.850 series. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.820 | 2018-08-29 | 16 | 11.1002/1000/13673 | + +## Keywords + +ITU-T H.810, Continua Design Guidelines, e-health, personal connected health system. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 3 | +| 3.1 Terms defined elsewhere ..... | 3 | +| 3.2 Terms defined in this Recommendation ..... | 3 | +| 4 Abbreviations and acronyms ..... | 4 | +| 5 Conventions ..... | 5 | +| 6 Application ..... | 5 | +| 7 Test case reference list..... | 5 | +| 8 Device profile ..... | 5 | +| 9 Test descriptions ..... | 6 | +| 9.1 Results system ..... | 7 | +| 9.2 Acceptance results ..... | 7 | +| 10 Conformance assessment test specification..... | 7 | +| 10.1 Transport test requirements ..... | 8 | +| 10.1.1 Required transport test suites ..... | 8 | +| 10.2 IEEE 11073-20601 features test requirements ..... | 8 | +| 10.2.1 Required test suites for ISO/IEEE 11073-20601 features..... | 8 | +| 10.3 Certified Capability Class test requirements ..... | 8 | +| 10.4 PHD test suite structure and test purposes specification ..... | 9 | +| 10.5 USB host test suite structure and test purposes specification..... | 9 | +| 10.6 Services test suite structure & test purposes specification ..... | 9 | +| 10.7 HIS test suite structure and test purposes specification..... | 10 | +| 10.8 Non-Continua hardware/software test requirements ..... | 10 | +| 10.9 PHD interfaces..... | 10 | +| 10.10 Inconclusive results ..... | 10 | +| 10.11 Self-testing..... | 11 | +| 11 Interoperability assessment test specification..... | 11 | +| 11.1 Personal Health Devices interface functional test procedures ..... | 11 | +| 11.2 Services interface functional test procedures ..... | 11 | +| 12 Test reports ..... | 12 | +| 12.1 Detailed test report ..... | 12 | +| 12.2 Summary test report ..... | 12 | +| 13 Continua test tool..... | 12 | +| Bibliography..... | 13 | + +# Introduction + +This Recommendation provides an overview of the conformance and interoperability testing that is performed to ensure products conform to the Continua Design Guidelines [ITU-T H.810] and its underlying standards and demonstrate interoperability between conforming products. + +Continua test descriptions are written in the form of test suite structure (TSS) and test procedures (TP) documents to guide execution of conformance tests using the Continua test tool (CTT) [b-Continua Test Tool]. These test descriptions also describe precisely the possible results of a given procedure such that the result is deterministic. Device profiles are employed to survey and describe features implemented on a product that are then used to configure the Continua test tool to execute all test cases applicable to that product's feature set. + +Conformance testing verifies compliance with: + +- Personal Health Devices interface (or PHD-IF) requirements for transport, exchange protocols, certified capability classes and device specializations; +- Services interface (or Services IF) requirements for web services interoperability, SOAP/ATNA, PCD-01 HL7 messages, consent management, hData observation upload and questionnaires; +- Health Information System interface (or HIS-IF) sender and receiver. + +Interoperability testing verifies basic personal health device (PHD) and Services functionality of typical use cases for a device specialization against a test bed of Continua certified devices. + +Test report templates are employed to document test results at detailed level and summary level. Detailed test reports are confidential to the product vendor. They may be presented to a customer to self-declare compliance to the Continua Design Guidelines (CDG) or provided to the Continua certification administrator (CertAdmin) as part of the Continua certification process [b-CDG Certification]. Summary level (passing) test results are available to the public. All Continua certified products are listed on the ITU Product Conformity Database at . + +The Continua test tool provides a user interface by which product features are identified and mapped to the appropriate test cases to generate the test plan used to verify conformance to the Continua Design Guidelines and ISO/IEEE 11073-20601 family of specifications. + +The test specifications herein are published by the ITU as the ITU-T H.820-H.850 series of Recommendations "Conformance of ITU-T H.810 personal health systems" [ITU-T H.820-H.850]. + +# Conformance of ITU-T H.810 personal health system: Conformity assessment test plan + +# 1 Scope + +The purpose of the conformity assessment test plan in this Recommendation is to provide an overview of the conformance and interoperability testing that is performed to ensure products conform to the Continua Design Guidelines (CDG) and its underlying standards and to demonstrate interoperability between conforming products. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal connected health systems: Introduction*. +- [ITU-T H.820-H.850] Recommendation ITU-T H.820-H.850 sub-series, *Conformance of ITU-T H.810 personal health devices*. List at . +- [ISO/IEEE 11073-20601-2016] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized Exchange Protocol*. . Same publication as . +- [ISO/IEEE 11073-10404] ISO/IEEE 11073-10404:2010, *Health informatics – Personal health device communication – Part 10404: Device specialization – Pulse oximeter*. . Same publication as . +- [ISO/IEEE 11073-10406] IEEE 11073-10406-2012, *Health informatics – Personal health device communication – Part 10406: Device specialization – Basic Electrocardiograph (ECG) (1 to 3-lead ECG)*. . Same publication as . +- [ISO/IEEE 11073-10407] ISO/IEEE 11073-10407:2010, *Health informatics – Personal health device communication – Part 10407: Device specialization – Blood pressure monitor*. . Same publication as . + +- [ISO/IEEE 11073-10408] ISO/IEEE 11073-10408:2010, *Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer*. . Same publication as . +- [ISO/IEEE 11073-10415] ISO/IEEE 11073-10415:2010, *Health informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale*. . Same publication as . +- [ISO/IEEE 11073-10417] ISO/IEEE 11073-10417:2017, *Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter*. . Same publication as . +- [ISO/IEEE 11073-10418] ISO/IEEE 11073-10418:2011, *Health informatics – Personal health device communication – Part 10418: Device specialization – International Normalized Ratio (INR) monitor*. . Same publication as . +- [ISO/IEEE 11073-10419] ISO/IEEE 11073-10419:2016, *Health informatics - Personal health device communication – Part 10419: Device specialization– Insulin pump*. . Same publication as . +- [ISO/IEEE 11073-10420] ISO/IEEE 11073-10420 (2012), *Health informatics – Personal health device communication – Part 10420: Device specialization – Body composition analyzer*. . Same publication as . +- [ISO/IEEE 11073-10421] ISO/IEEE 11073-10421:2012, *Health informatics – Personal health device communication – Part 10421: Device specialization – Peak expiratory flow monitor (peak flow)*. . Same publication as . +- [ISO/IEEE 11073-10424] ISO/IEEE 11073-10424:2016, *Health informatics – Personal health device communication – Part 10424: Device specialization – Sleep apnoea breathing therapy equipment (SABTE)*. . Same publication as . +- [ISO/IEEE 11073-10425] ISO/IEEE 11073-10425:2016, *Health informatics – Personal health device communication – Part 10425: Device specialization – Continuous glucose monitor (CGM)*. . Same publication as . + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [ISO/IEEE 11073-10427] | ISO/IEEE 11073-10427:2018, Health informatics – Personal health device communication – Part 10427: Device specialization – Power status monitor of personal health devices . https://www.iso.org/standard/73759.html . Same publication as https://standards.ieee.org/findstds/standard/11073-10427-2016.html . | +| [ISO/IEEE 11073-10441] | ISO/IEEE 11073-10441:2015, Health informatics – Personal health device communication – Part 10441: Device specialization – Cardiovascular fitness and activity monitor . https://www.iso.org/standard/64868.html . Same publication as http://standards.ieee.org/findstds/standard/11073-10441-2013.html . | +| [ISO/IEEE 11073-10442] | ISO/IEEE 11073-10442:2015, Health informatics – Personal health device communication – Part 10442: Device specialization – Strength fitness equipment . https://www.iso.org/standard/66212.html . Same publication as https://standards.ieee.org/findstds/standard/11073-10442-2008.html . | +| [ISO/IEEE 11073-10471] | ISO/IEEE 11073-10471:2010, Health informatics – Personal health device communication – Part 10471: Device specialization – Independent living activity hub . https://www.iso.org/standard/54328.html . Same publication as https://standards.ieee.org/findstds/standard/11073-10471-2008.html . | +| [ISO/IEEE 11073-10472] | ISO/IEEE 11073-10472:2012, Health informatics – Personal health device communication – Part 10472: Device specialization – Medication Monitor . https://www.iso.org/standard/54364.html . Same publication as https://standards.ieee.org/findstds/standard/11073-10472-2010.html . | + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 Continua Personal Health Devices interface (PHD-IF)** [ITU-T H.810]: The Continua PHD-IF connects one or more Personal Health Device (e.g., sensor/actuator) client components to one or more Personal Health Device (sensor/actuator) service components using transport media such as USB, Bluetooth LE, Bluetooth BR/EDR, ZigBee or NFC. Examples of sensor service components include glucose meters, weighing scales and heart rate monitors. + +**3.1.2 Personal Health Devices interface (PHD-IF)** [ITU-T H.810]: Interface between a Personal Health Device (PHD) and Personal Health Gateway (PHG). See Continua PHD interface. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 CDG certification:** The process by which a certification body verifies, through conformance testing, that a personal health device complies with the ITU-T H.810 Continua Design Guidelines (CDG) and specifications and is able to interoperate with other personal health devices compliant with the ITU-T H.810 CDG. A certification body may provide a certificate of compliance and/or a logo to provide proof of certification. There are four types of certification: + +- Type A: certification of a totally new product; +- Type D: certification of a derivative product; + +- Type U: certification of an updated product; and +- Type O: certification of a Type A or Type D certified product relabelled by a second vendor. + +**3.2.2 Certified Capability Class:** Entity in the ITU-T H.810 Continua end-to-end (E2E) architecture for which a complete set of guidelines has been defined such that a device or application can be certified to comply with that set of guidelines via the Continua certification programme. + +**3.2.3 CDG compliance:** The state of being in accordance with [ITU-T H.810] Continua Design Guidelines (CDG). Compliance with the CDG and specifications is assessed through conformance testing performed during the certification process. + +**3.2.4 CDG component:** A logical entity in the Continua Design Guidelines (CDG) ecosystem. In general, for any *Interface*, there is a service component, with a well-defined set of functions depending on its type, on one side of the interface and one (or more) client components on the other side. Each component is realized within a physical device. + +**3.2.5 CDG conformance:** An affirmative indication, through testing, that a personal health device (PHD) was built and functionally behaves according to a certification body's interoperability specifications and Continua Design Guidelines (CDG). Conformance with a certification body interoperability guidelines and specifications is assessed via conformance testing performed during the certification process. + +**3.2.6 device:** A physical entity (box) and contains one or more functional components and capabilities. + +**3.2.7 interoperability:** The ability of a client component in a device to communicate and share data with a variety of server components in an unambiguous and predictable manner, to exchange data accurately, effectively and consistently and to understand and use the information that is exchanged. The ITU-T H.820-H.850 series is used to certify devices and specifies the technical scope and requirements by which a device is considered compliant with interoperability. + +**3.2.8 Personal Health Gateway (PHG):** A Continua reference capability class that contains a number of client components that use Personal Health Devices interfaces (PHD-IFs) and Service interfaces (Service-IFs) to access one or more services on other devices to coordinate data collection, data analysis, data sharing and alerting. + +**3.2.9 plugfest:** An organized event for product vendors to gather together and implement the cross-vendor interoperability test. + +**3.2.10 product vendor:** Product vendors are creators of personal health devices (PHDs). + +**3.2.11 Services interface (Services IF):** An interface between Personal Health Gateway (e.g., smart phone, tablet and dedicate hub) and Health & Fitness Service applications (e.g., disease management service, ageing independently service and wellness service). The Health & Fitness Service application could be hosted in the cloud. IP based connectivity is assumed between the Personal Health Gateway and the Health & Fitness Service application and Continua focuses on defining the behaviour of the OSI layers above IP. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------| +| AG | Agent | +| ATNA | Audit Trail and Node Authentication | +| BLE | Bluetooth Low Energy | + +| | | +|-----------|-------------------------------------------| +| CertAdmin | Certification Administrator | +| CDG | Continua Design Guidelines | +| CTT | Continua Test Tool | +| DIM | Device Information Model | +| E2E | End-to-End | +| EPL | End Product Listing | +| HF | Health & Fitness | +| HFS | Health & Fitness Service | +| HIS | Healthcare Information System | +| HIS-IF | Health Information System Interface | +| ICT | Information and Communications Technology | +| PCD | Patient Care Device | +| PHD | Personal Health Devices | +| PHD-IF | Personal Health Devices Interface | +| PHG | Personal Health Gateway | +| PLT | PAN-LAN-TAN | +| SOAP | Simple Object Access Protocol | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | + +# 5 Conventions + +None. + +# 6 Application + +This Recommendation familiarizes the reader with device profiles, test descriptions, conformance and interoperability test specifications, test report formats and the Continua test tool (CTT) as they are used to verify product conformance and compliance. + +# 7 Test case reference list + +A list of all test cases is to be maintained with traceability back to the CDG. For each test case, this reference list contains applicability logic to determine mandatory and optional test cases based on product features, the date the test case becomes active, test specifications and test tool versions and any bug fixes addressed by that release. This reference list is available as part of the Continua test tool (CTT) for download [b-Continua Test Tool]. + +# 8 Device profile + +A device profile is a document used to describe a device under test (DUT). The profile is a survey of features implemented on a device. It is created using the certification web site. The user fills in a form indicating the features of the device under test. The tool then generates an XML device profile document. The device profile document contains enough information to determine every part of the + +specification that applies to the DUT. This device profile document is used for multiple purposes in Continua. + +- Used by the CTT to select test suites and test cases that are applicable to the DUT. +- Used in the certified device database as a record of what the certified device implements for features. +- Used as part of the certification documentation so that third parties can determine what other devices will be interoperable with this device. +- Used by Continua to create reports of which features of the Continua products are present in certified products. + +# 9 Test descriptions + +Continua test descriptions are created to guide execution of conformance tests that are part of a test suite implemented in the CTT. Interoperability procedures may be divergent from this format. + +Test descriptions provide documentation for both the test developer and the executor of the test. Test descriptions are written such that a person with an architectural understanding of the network protocols involved can follow the discussion and procedure. Test descriptions are always written for black box testing. A test description contains at a minimum the following elements: + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test label | A title for the document. This often has taxonomic information embedded. For example, a suggested syntax could be 20601.Scanner.Buf-Scan-Report-Var.1 where the notation includes from left to right the standard name, the test spec name, the subsection of the test spec and a test number. | +| Device type | A label indicating the type of Certified Capabilities Class this test case applies to (see clause 6.1.3 of [ITU-T H.810] "Reference capability classes and system topology"). | +| Compliance classifier | Indicates the requirement level as stated in the Continua interoperability test suite. Either Mandatory, Recommended or Optional. | +| Purpose | An executive summary of the requirement. | +| Discussion | Narrative text that outlines the requirement and the approach to testing. This statement should include the reasoning of the test designer for choosing the approach for testing and mention other approaches that were not taken and why. This section can also mention possible problems in the specification or in the procedure. | +| References | References to the relevant external specifications being tested in this test procedure. | +| Configuration | Assumptions about the topology of the network and configuration of the devices necessary before beginning the procedure. | +| Procedure | A testing procedure written in outline form that details the behaviour of the testing tool as well as the expected behaviour for the device under test. | +| Observable results | A table mapping possible outcomes of the procedure with a result (see clause 9.1). The observable results table should try to enumerate all possible reasons for exiting the procedure. Logged results from the test tool should be indexed in the observable results table to aid in failure isolation. | +| Device under test (DUT) | The vendor product being tested. It is a common shorthand used in black box testing and in test descriptions. | + +## 9.1 Results system + +Test description documents describe precisely the possible results of a given procedure such that the results are deterministic. A requirement is considered to have a mandatory, recommended, optional or optional normative requirement level. This system provides sufficient variation to identify the outcome of any test for each of the requirement levels as compliant or non-compliant. Further it creates added value in the test suites by giving the developer information about what features are implemented on their device. Finally, compliance for certification purposes can still be easily determined, by applying the rule that "Compliant devices must not **FAIL** any mandatory tests." + +The six result system is enumerated as follows: + +| | | +|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PASS | Compliance with the requirement is demonstrated by the DUT exhibiting the expected behaviour. | +| FAIL | Non-compliance with the requirement is demonstrated by the DUT failing to exhibit a required behaviour or exhibiting an incorrect behaviour. | +| INCONC (inconclusive) | Test tool is unable to determine if DUT PASSed or FAILed the test procedure. INCONCs shall be evaluated by the test lab to determine whether the test procedure has PASSed or FAILed. The test lab may need to use special tools, such as sniffers, manual procedures, or reference devices to determine whether the test procedure has PASSed or FAILed. Continua test lab personnel and Continua Certified Experts maintain a document that outlines the alternative approaches to achieve a conclusive verdict. | +| ERROR | There is an error in the test harness (transport, drivers, operating system, etc.) and the test case is not able to be run. | +| NA | The requirement does not apply to the DUT. | +| NT | The recommended or optional behaviour could be not invoked when testing the DUT. This is not a valid result for mandatory items. | + +NOTE – To ensure consistency in the case of INCONC results, the procedure used by the test lab to generate a conclusive result will be shared with all other test labs. This is typically done by modifying the test tool and/or test procedures to generate a conclusive result. Information is typically communicated via email and sent to the Certification Administrator (CertAdmin) and other test labs for use in future certifications. + +## 9.2 Acceptance results + +The test descriptions are the primary source of documentation for the test tool. Because of this relationship they are written primarily by the test tool vendor. The certification body reviews the test descriptions written by the test tool vendor on a regular interval before the test descriptions are implemented. This process has multiple benefits. First, it fulfils the requirement of an acceptance process. Second, it will bring to light omissions, ambiguities or common misunderstandings in the specification in a timely manner. This prevents implementation of test cases that might perpetuate misinterpretations and prevent a duplication of effort if the standards or test descriptions need to be changed. + +# 10 Conformance assessment test specification + +This document provides a test plan for each Certified Capability Class in the Continua Design Guidelines (CDG). Devices applying for certification must demonstrate successful completion of the test plan, by providing test logs for the test suites indicated in this document. Additionally, this document lists supplemental information that must be submitted as part of the application for certification. The certification body CertAdmin verifies compliance with the requirements of this + +document. Certified test labs adhere to the test plans contained in this document. Applicants should use this test plan to prepare an application and coordinate testing needs with a test lab. + +## **10.1 Transport test requirements** + +This clause contains requirements for personal health devices (PHDs) implementing transport technologies for passing CDG data. Products applying for certification must test all transport interfaces that will carry CDG data. There are test suites that are specific to each transport technology. Test logs must be submitted for each interface. + +### **10.1.1 Required transport test suites** + +USB Design Guidelines (TP/PAN/PHD/TR/UDG/\* for Personal Health Devices (PHDs), TP/PAN/PHG/TR/UDG/\* for Personal Health Gateways (PHGs)) + +USB Host Test Suite (TP/PHDC/HOS/\* for PHGs) + +Bluetooth Design Guidelines (TP/PAN/PHD/TR/BDG/\* for PHDs, TP/PAN/PHG/TR/BDG/\* for PHGs) + +Bluetooth Low Energy Design Guidelines (TP/PAN/PHD/TR/BLEDG/\* for PHDs, TP/PAN/PHG/TR/BLEDG/\* for PHGs) + +ZigBee Design Guidelines (TP/LAN/PHD/TR/ZDG/\* for PHDs, TP/LAN/PHG/TR/ZDG/\* for PHGs) + +## **10.2 IEEE 11073-20601 features test requirements** + +All devices must implement the required elements of [ISO/IEEE 11073-20601-2016], which is a framework specification of features and mechanisms, and the device specialization documents select which features of the framework to use to synthesize a device class. All devices must also implement the applicable CDG that apply to ISO/IEEE 11073-20601 as well as the applicable general design guidelines. The test suites corresponding to these required features are listed in the following clauses. + +### **10.2.1 Required test suites for ISO/IEEE 11073-20601 features** + +Design Guidelines: Common (TP/PLT/AG/TR/DGC/\* for Agents, TP/PLT/MAN/TR/DGC/\* for Managers) + +PHD Domain Information Model (TP/PLT/AG/OXP/DIM/\* for Agents, TP/PLT/MAN/OXP/DIM/\* for Managers) + +PHD Service Model (TP/PLT/AG/OXP/SER/\* for Agents, TP/PLT/MAN/OXP/SER/\* for Managers) + +PHD Communication Model (TP/PLT/AG/OXP/COM/\* for Agents, TP/PLT/MAN/OXP/COM/\* for Managers) + +## **10.3 Certified Capability Class test requirements** + +This clause contains the certification requirements for each Certified Capability Class. A device must implement one or more Certified Capability Classes at the time it applies for a Type A Certification, as required in the CDG. If a device implements multiple certifiable device classes, then the test plan for all device classes must be executed. + +- IEEE 11073-10415 – Weighing scale [ISO/IEEE 11073-10415] +- IEEE 11073-10417 – Glucose meter [ISO/IEEE 11073-10417] +- IEEE 11073-10404 – Pulse oximeter [ISO/IEEE 11073-10404] +- IEEE 11073-10406 – Basic electrocardiograph [ISO/IEEE 11073-10406] + +- IEEE 11073-10407 – Blood pressure monitor [ISO/IEEE 11073-10407] +- IEEE 11073-10408 – Thermometer [ISO/IEEE 11073-10408] +- IEEE 11073-10472 – Body composition analyser [ISO/IEEE 11073-10472] +- IEEE 11073-10421 – Peak expiratory flow monitor [ISO/IEEE 11073-10421] +- IEEE 11073-10441 – Cardiovascular [ISO/IEEE 11073-10441] +- IEEE 11073-10442 – Strength [ISO/IEEE 11073-10442] +- IEEE 11073-10471 – Activity hub [ISO/IEEE 11073-10471] +- IEEE 11073-10472 – Adherence monitor [ISO/IEEE 11073-10472] +- IEEE 11073-10418 – INR monitor [ISO/IEEE 11073-10418] +- IEEE 11073-10424 – Sleep apnoea breathing therapy equipment (SABTE) [ISO/IEEE 11073-10424] +- IEEE 11073-10419 – Insulin pump [ISO/IEEE 11073-10419] +- IEEE 11073-10425 – Continuous glucose monitor [ISO/IEEE 11073-10425] +- IEEE 11073-10427 – Power status monitor [ISO/IEEE 11073-10427] + +## **10.4 PHD test suite structure and test purposes specification** + +The scope of the ITU-T H.840-series set is to provide test suite structure and test purposes (TSS & TP) for Personal Health Devices interfaces based on the requirements defined in Continua specifications. The objective is to provide a high probability of air interface interoperability between different devices. + +TSS & TP for the Personal Health Devices Interface document set includes the following ten parts: + +- Part 1: Optimized Exchange Protocol Personal Health Device +- Part 2: Optimized Exchange Protocol Personal Health Gateway +- Part 3: Continua Design Guidelines Personal Health Device +- Part 4: Continua Design Guidelines Personal Health Gateway +- Part 5: Device Specializations Personal Health Device +- Part 6: Device Specializations Personal Health Gateway +- Part 7: Continua Design Guidelines Personal Health Device BLE +- Part 8: Continua Design Guidelines Personal Health Gateway BLE +- Part 9: Personal Health Devices Transcoding White paper Personal Health Device +- Part 10: Personal Health Devices Transcoding White paper Personal Health Gateway + +## **10.5 USB host test suite structure and test purposes specification** + +The scope of [ITU-T H.840] is to provide test suite structure and test purposes (TSS & TP) for USB Host based on the requirements defined in USB Personal Healthcare Device Class specification that has been selected for the PHD interface (see [ITU-T H.810]). + +Group 1 Descriptors (DESC) + +Group 2 Meta-Data, Message Preamble, (MDMP) + +## **10.6 Services test suite structure & test purposes specification** + +The scope of the ITU-T H.830 series is to provide test suite structure and test purposes (TSS & TP) for the Services interface based on the requirements defined in Continua Specifications. The objective is to provide a high probability of air interface interoperability between different devices. + +TSS & TP for the Services interface document set includes the following 16 parts: + +- Part 1: Web Services Interoperability. HFS sender +- Part 2: Web Services Interoperability. HFS receiver +- Part 3: SOAP/ATNA. HFS sender +- Part 4: SOAP/ATNA. HFS receiver +- Part 5: PCD-01 HL7 Messages. HFS sender +- Part 6: PCD-01 HL7 Messages. HFS receiver +- Part 7: Consent Management. HFS sender +- Part 8: Consent Management. HFS receiver +- Part 9: hData Observation Upload. HFS sender +- Part 10: hData Observation Upload. HFS receiver +- Part 11: Questionnaires. HFS sender +- Part 12: Questionnaires. HFS receiver +- Part 13: Capability Exchange: Health & Fitness Service sender +- Part 14: Capability Exchange: Health & Fitness Service receiver +- Part 15: FHIR Observation Upload: Health & Fitness Service sender +- Part 16: HIR Observation Upload: Health & Fitness Service receiver + +## **10.7 HIS test suite structure and test purposes specification** + +The scope of [ITU-T H.821] is to provide test suite structure and test purposes (TSS & TP) for the healthcare information system (HIS) interface based on the requirements defined in Continua Specifications. The objective is to provide a high probability of air interface interoperability between different devices via the healthcare information system (HIS) interface to transfer patient information from a Health & Fitness Service (HIS sender) to a healthcare information system (HIS receiver). + +This document only focuses on the TSS & TP for HIS sender because, at this moment, HIS Receiver is out of the scope of Continua Certification Program. + +The set of HIS interface test purposes includes two groups: + +Group 1 HIS sender + +Group 2 HIS receiver + +## **10.8 Non-Continua hardware/software test requirements** + +In general, changes to non-Continua hardware or software are considered Type U (changes are superficial, or identification related not requiring software or hardware modifications). However, if the size or format of the data changes, the timing changes, the CPU changes or the message changes, then retesting for such changes is required. + +## **10.9 PHD interfaces** + +This clause defines retesting certification procedures. + +## **10.10 Inconclusive results** + +All devices going through testing are required to receive passing results for the Certified Device Classes claimed and for each applicable test within the test plan. A waiver may be pursued if a device does not receive a PASS verdict (instead it receives either an INCONC or FAIL) yet the member believes they are compliant with the respective standard, guideline or specialization. + +## 10.11 Self-testing + +Members should provide the XML output from running the test procedure for all applicable test procedures. If a test procedure does not apply, the reason why it does not should be included in the Statement of Compliance (for self-declaration) or provided to the CertAdmin (for Certification by a certification body). + +# 11 Interoperability assessment test specification + +In general, the set of interoperability procedures that are used for certification is a subset of the set of procedures that are used at a plugfest. The interoperability procedures used for certification are designed around the basic functionality of typical use cases for a device specialization. This is in contrast to interoperability procedures for plugfests, which may exercise error paths, simulate error conditions or try to cause devices to exhibit non-compliant behaviour (known as negative testing). + +Interoperability testing for conformity assessment is conducted by test labs. Test labs are required to keep a test bed of certified Continua devices. Test labs conducting interoperability testing will perform the interoperability procedures specified in the certification specification using the DUT and each of the three pair devices. The DUT must pass all the required test cases when paired with each of the devices. + +In the case where an interoperability procedure fails, the test lab will need to determine if the DUT or the paired device is at fault. If the paired device is at fault, the test lab must report the failure to the CertAdmin. The CertAdmin will notify the device manufacturer and help guide them to take appropriate corrective action. + +If at the time of the certification there are not three certified Continua devices for a device specialization, the test lab will run interoperability pair testing against all available certified devices (if any). + +Note that the interoperability program against certified Continua devices will not go into effect until: + +- 1) Approved interoperability procedures exist for the DUT, and +- 2) The test lab or the plugfest program has certified Continua devices that can pair with the DUT. + +## 11.1 Personal Health Devices interface functional test procedures + +The following test procedures document a process that starts by having an application that is controlling a manager issue a request to enter the *Unassociated* state defined within Figure 10 of [ISO/IEEE 11073-20601-2016] (Manager state machine diagram). If the application does not have explicit control over this process, it should use a power on sequence to reach this state. + +- General procedures +- Temporary measurements +- PM store +- Scanner + +## 11.2 Services interface functional test procedures + +The following Services interface test procedures document a process that starts by having an application, the Health & Fitness Service (HFS) sender, which typically resides on a personal health gateway (PHG) and is responsible for sending the appropriate HL7 messaging representing the desired measurements taken. The HFS sender then transmits the measurements to a HFS receiver, which typically resides on a HFS hosting server and is responsible for receiving and handling the desired measurements and performing any further and more intelligent processes. + +- General procedures +- Batch measurements +- Continuous measurements +- Multiple connections – HFS receivers + +# **12 Test reports** + +Both detailed and summary test reports are used to communicate results of conformity assessment tests. These reports follow the requirements of ISO/IEC regarding test report content. + +## **12.1 Detailed test report** + +The detailed test report states the results of each test and is confidential between the test lab and the vendor providing the product under test. This report is provided to the CertAdmin when applying for Continua Certification. + +## **12.2 Summary test report** + +The summary test report documents and highlights test results sufficiently to clearly qualify and document the Certified Capability Classes being declared compliant to the Continua Design Guidelines and identify the product under test. This report is intended to be made public but is made so at the discretion of the vendor. + +# **13 Continua test tool** + +A Continua test tool provides two major functions: user interface and test case database. + +A user manual is useful to provide a detailed description of the usage and features of the test tool and to guide the test operator through all the steps: parameters, test execution and result reporting. + +The Continua test tool also contains a database of test cases from which product specific test procedures are generated based on PIX/PICIT. + +# Bibliography + +- [b-CDG Certification] Continua certification Process. + +- [b-Continua Test Tool] Continua Test Tool (CTT). + + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.830.15-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.830.15-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e5375f76616af38255d070eeca950f8d1abb9aa --- /dev/null +++ b/marked/H/T-REC-H.830.15-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0dfe5049741080b2c80208f89e1f3723554dcdfc5617b62c231c5f0ffd5822a +size 3962 diff --git a/marked/H/T-REC-H.830.17-202106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.830.17-202106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fc0ce00090f66b87404c12debf099b47a838ec0 --- /dev/null +++ b/marked/H/T-REC-H.830.17-202106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0efd3ea366c9c151bbcfa01a99d20b4bfbdb579443e1a9dd88122c3e286dae51 +size 6108 diff --git a/marked/H/T-REC-H.830.17-202106-I_PDF-E/raw.md b/marked/H/T-REC-H.830.17-202106-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..58b8459921ad938b208d7883d5bc7b5cb7fa8a4b --- /dev/null +++ b/marked/H/T-REC-H.830.17-202106-I_PDF-E/raw.md @@ -0,0 +1,694 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.830.17** + +(06/2021) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Services interface Part 17: Personal +Health Device Observation Upload (POU) +Sender** + +Recommendation ITU-T H.830.17 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Content delivery and ubiquitous sensor network applications | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.830.17 + +## Conformance of ITU-T H.810 personal health system: Services interface Part 17: Personal Health Device Observation Upload (POU) Sender + +## Summary + +Recommendation ITU-T H.830.17 provides a test suite structure (TSS) and the test purposes (TPs) for Personal Health Device Observation Upload (POU) sender in the Services interface, based on the requirements defined in the Recommendations of the ITU-T H.810 subseries, of which Recommendation ITU-T H.810 (2019) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.830.17 includes an electronic attachment with the protocol implementation conformance statements (PICSs) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.830.17 | 2021-06-13 | 16 | 11.1002/1000/14687 | + +## Keywords + +Capability exchange, conformance testing, continua design guidelines, e-health, Health & Fitness service, ITU-T H.810, personal connected health devices, POU, services interface. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2021 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Test suite structure..... | 5 | +| 7 Electronic attachment ..... | 7 | +| Annex A Test procedures..... | 8 | +| A.1 Test purpose definition conventions..... | 8 | +| A.2 Subgroup 1.10.1: General (GEN)..... | 9 | +| Bibliography..... | 17 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICSs) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# Introduction + +The table below shows the revision history of this test specification. + +| Version | Date | Revision history | +|---------|------------|----------------------------------------------------------------------------------------------| +| 1.0 | 2020-12-21 | Initial release for the inclusion of Personal Health Device Observation Upload (POU) sender. | + +# Recommendation ITU-T H.830.17 + +## Conformance of ITU-T H.810 personal health system: Services interface Part 17: Personal Health Device Observation Upload (POU) Sender + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TPs) for the Services interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2019)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TPs for the Services interface have been divided into the parts specified below. This Recommendation covers Part 17. + +- Part 1: Web services interoperability. Health & Fitness Service sender +- Part 2: Web services interoperability. Health & Fitness Service receiver +- Part 3: SOAP/ATNA. Health & Fitness Service sender +- Part 4: SOAP/ATNA. Health & Fitness Service receiver +- Part 5: PCD-01 HL7 Messages. Health & Fitness Service sender +- Part 6: PCD-01 HL7 Messages. Health & Fitness Service receiver +- Part 7: Consent Management. Health & Fitness Service sender +- Part 8: Consent Management. Health & Fitness Service receiver +- Part 9: hData Observation Upload. Health & Fitness Service sender +- Part 10: hData Observation Upload. Health & Fitness Service receiver +- Part 11: Questionnaires. Health & Fitness Service sender +- Part 12: Questionnaires. Health & Fitness Service receiver +- Part 13: Capability Exchange. Health & Fitness Service sender +- Part 14: Capability Exchange. Health & Fitness Service receiver +- Part 15: FHIR Observation Upload. Health & Fitness Service sender +- Part 16: FHIR Observation Upload. Health & Fitness Service receiver. +- **Part 17: POU. Health & Fitness Service sender.** +- Part 18: POU. Health & Fitness Service receiver. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a standalone document, the status of a Recommendation. + +[ITU-T H.810 (2019)] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal health systems: Introduction*. + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# **3 Definitions** + +## **3.1 Terms defined elsewhere** + +None. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|-------------------------------------------------------| +| AHD | Application Hosting Device | +| API | Application Programming Interface | +| ATNA | Audit Trail and Node Authentication | +| BLE | Bluetooth Low Energy | +| BT HDP | Bluetooth Health Device Profile | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DOC | Device Observation Consumer | +| DOR | Device Observation Reporter | +| DUT | Device Under Test | +| FHIR | Fast Healthcare Interoperability Resources | +| HFS | Health & Fitness Service | +| HFSR | Health & Fitness Service Receiver | +| HFSS | Health & Fitness Service Sender | +| HL7 | Health Level 7 | +| HTTP | Hypertext Transfer Protocol | +| IHE | Integrating the Healthcare Enterprise | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| JSON | JavaScript Object Notation | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PCD | Patient Care Device | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PHI | Personal Health Information | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | + +| | | +|-------|------------------------------------------------| +| POU | Personal Health Device Observation Upload | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SOAP | Simple Object Access Protocol | +| TLS | Transport Level Security | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| URI | Uniform Resource Identifier | +| WS | Web Service | +| WSI | Web Services Interoperability | +| XDR | Cross-Enterprise Document Reliable Interchange | +| XML | extensible Markup Language | +| ZB | Zigbee | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-IHE\_PCD\_Suppl\_POU]. + +- SHALL is equivalent to "must" or "'itis required to". +- SHALL NOT is equivalent to "must not" or "it is not allowed to". +- SHOULD is equivalent to "it is recommended to". +- SHOULD NOT is equivalent to "it is not recommended to". +- MAY is equivalent to "is permitted". +- MAY NOT is equivalent to "it is not required that". + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of designations that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|--------------------|------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| 2019 | – | 8.0 | Release 2019 of the CDG including maintenance updates of the CDG 2017 and additional guidelines that cover new functionalities. | – | +| 2017 | – | 7.0 | Release 2017 of the CDG including maintenance updates of the CDG 2016 and additional guidelines that cover new functionalities. | – | +| 2016 plus errata | [b-ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of [ITU-T H.810] is split into eight parts in the ITU-T H.810 series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata. | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure + +The test procedures (TPs) for the Services interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 1.7.1 and 1.7.2 (shown in bold): + +- Group 1: HFS sender (HFSS) + - Group 1.1: Web services interoperability (WSI) + - Subgroup 1.1.1: Basic profile (BP) + - Subgroup 1.1.2: Basic security profile (BSP) + - Subgroup 1.1.3: Reliable messaging (RM) + - Group 1.2: Simple object access protocol (SOAP) + - Subgroup 1.2.1: SOAP headers (HEAD) + - Group 1.3: Audit trail and node authentication (ATNA) + - Subgroup 1.3.1: General (GEN) + - Subgroup 1.3.2: PCD-01 (PCD-01) + - Subgroup 1.3.3: Consent Management (CM) + - Group 1.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 1.4.1: General (GEN) + - Subgroup 1.4.2: Design guidelines (DG) + - Subgroup 1.4.3: Pulse oximeter (PO) + - Subgroup 1.4.4: Blood pressure monitor (BPM) + - Subgroup 1.4.5: Thermometer (TH) + - Subgroup 1.4.6: Weighing scales (WEG) + - Subgroup 1.4.7: Glucose meter (GL) + - Subgroup 1.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 1.4.9: Strength fitness equipment (ST) + - Subgroup 1.4.10: Independent living activity hub (HUB) + - Subgroup 1.4.11: Adherence monitor (AM) + - Subgroup 1.4.12: Peak expiratory flow monitor (PF) + - Subgroup 1.4.13: Body composition analyser (BCA) + - Subgroup 1.4.14: Basic electrocardiograph (ECG) + - Subgroup 1.4.15: International normalized ratio (INR) + - Subgroup 1.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.4.17: Insulin pump (IP) + - Subgroup 1.4.18: Continuous glucose monitor (CGM) + - Group 1.5: Consent Management (CM) + - Subgroup 1.5.1: HFS XDR transaction (TRANS) + - Subgroup 1.5.2: HFS metadata validation (META) + - Subgroup 1.5.3: HFS consent directive validation (CDV) + - Group 1.6: hData Observation Upload (HDATA) + - Subgroup 1.6.1: General (GEN) + - Group 1.7: Questionnaires (QUE) + - Subgroup 1.7.1: General (GEN) + - Subgroup 1.7.2: CDA validation (CDA) + +- Group 1.8: Capability Exchange (CE) + - Subgroup 1.8.1: General (GEN) + - Subgroup 1.8.2: hData record format (HRF) +- Group 1.9: FHIR Observation Upload (FHIR) + - Subgroup 1.9.1: General (GEN) + - Subgroup 1.9.2: FHIR Encoding Guidelines (ENC) +- **Group 1.10: Personal Health Device Observation Upload (POU)** + - Subgroup 1.10.1: General (GEN) + +– Group 2: HFS receiver (HFSR) + +- Group 2.1: Web service interoperability (WSI) + - Subgroup 2.1.1: Basic profile (BP) + - Subgroup 2.1.2: Basic security profile (BSP) + - Subgroup 2.1.3: Reliable messaging (RM) +- Group 2.2: SOAP (SOAP) + - Subgroup 2.2.1: SOAP headers (HEAD) +- Group 2.3: Audit (ATNA) + - Subgroup 2.3.1: General (GEN) + - Subgroup 2.3.2: PCD-01 (PCD-01) + - Subgroup 2.3.3: Consent Management (CM) +- Group 2.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 2.4.1: General (GEN) + - Subgroup 2.4.2: Design guidelines (DG) + - Subgroup 2.4.3: Pulse oximeter (PO) + - Subgroup 2.4.4: Blood pressure monitor (BPM) + - Subgroup 2.4.5: Thermometer (TH) + - Subgroup 2.4.6: Weighing scales (WEG) + - Subgroup 2.4.7: Glucose meter (GL) + - Subgroup 2.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 2.4.9: Strength fitness equipment (ST) + - Subgroup 2.4.10: Independent living activity hub (HUB) + - Subgroup 2.4.11: Adherence monitor (AM) + - Subgroup 2.4.12: Peak expiratory flow monitor (PF) + - Subgroup 2.4.13: Body composition analyser (BCA) + - Subgroup 2.4.14: Basic electrocardiograph (ECG) + - Subgroup 2.4.15: International normalized ratio (INR) + - Subgroup 2.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.4.17: Insulin pump (IP) + - Subgroup 2.4.18: Continuous glucose monitor (CGM) +- Group 2.5: Consent Management (CM) + - Subgroup 2.5.1: HFS XDR transaction (TRANS) + - Subgroup 2.5.2: HFS service validation (SER) + +- Group 2.6: hData Observation Upload (HDATA) + - Subgroup 2.6.1: General (GEN) + - Subgroup 2.6.2: hData record format (HRF) +- Group 2.7: Questionnaires (QUE) + - Subgroup 2.7.1: General (GEN) + - Subgroup 2.7.2: CDA validation (CDA) + - Subgroup 2.7.3: hData record format (HRF) +- Group 2.8: Capability Exchange (CE) + - Subgroup 2.8.1: General (GEN) + - Subgroup 2.8.2: hData record format (HRF) +- Group 2.9: FHIR Observation Upload (FHIR) + - Subgroup 2.9.1: General (GEN) +- Group 2.10: Personal Health Device Observation Upload (POU) + - Subgroup 1.10.1: General (GEN) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICSs) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . See [b-HFSR PICS & PIXIT] and [b-HFSS PICS & PIXIT]. + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICSs" and "PIXIT", respectively, during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICSs, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +## Test procedures + +(This annex forms an integral part of this Recommendation.) + +## A.1 Test purpose definition conventions + +The TPs are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: +Each TP identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - HFS: Health & Fitness Services Interface + - : This is the device under test. + - SEN: HFS sender + - REC: HFS receiver + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the TP. +- **TP label:** This is title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if a test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the DUT within that scope of the test (specialization, transport used, etc.). +- **Other PICSs:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of test case execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 1.10.1: General (GEN) + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------| +| TP Id | TP/HFS/SEN/POU/GEN/BV-000 | | | | +| TP label | POU Profile – Actors and Transactions (DOR) | | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | | +| | Testable items | IHETrans;M | DORReq 6;M | POUActorTrans:M | +| | | CommPCH-01MessSem 3;M | CommPCH-02MessSem 2;M | | +| Test purpose | Check that:
    A Device Observation Reporter (DOR) supports the following required transactions to claim compliance with the POU.
    1. 1. Communicate fast healthcare interoperability resources (FHIR) Personal Health Device (PHD) Data (PCH-01)
    2. 2. Communicate RESTful FHIR PHD Data (PCH-02)
    | | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_009 AND C_SEN_GEN_010 | | | | +| Other PICSS | | | | | +| Initial condition |

    Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU application programming interface (API) that can accept a POU that requires transport level security (TLS) and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02).

    | | | | +| Test procedure |
    1. 1. Ask the DOR under test to upload an Observation resource as a complete bundle to the simulated Receiver using a FHIR PHD Data (PCH-01) transaction.
    2. 2. Ask the DOR under test to upload an Observation resource as a complete bundle to the simulated Receiver using a RESTful FHIR PHD Data (PCH-02) transaction.
    | | | | +| Pass/fail criteria |
    • • Receiver correctly retrieves a first complete bundle.
    • • The first transaction is a FHIR PHD Data (PCH-01) transaction.
    • • Receiver correctly retrieves a second complete bundle.
    • • The second transaction is a RESTful FHIR PHD Data (PCH-02) transaction.
    | | | | +| Notes | | | | | + +| | | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------|--| +| TP Id | TP/HFS/SEN/POU/GEN/BV-001 | | | | +| TP label | DOR Requirements. Time source | | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | | +| | Testable items | DORReq 1;M | DORReq 2;M | | +| | | | | | +| Test purpose | Check that:
    A DOR is synchronized to a time source.
    [AND]
    A DOR ensures correct time stamps in the PHD Data that are aligned with the timeline of this time source. | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_SEN_000 AND C_SEN_GEN_009 | +| Other PICSSs | | +| Initial condition | Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02). | +| Test procedure |
    1. 1. Ask the DOR under test to upload an Observation resource as a complete bundle to the simulated Receiver.
    2. 2. Ask the DOR under test to upload another Observation resource as a complete bundle to the simulated Receiver.
    | +| Pass/fail criteria |
    • • The time in the received bundle in step 2 is correct.
    • • The timestamps of the bundles received in steps 1 and 2 are aligned with the timeline of this time source.
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/HFS/SEN/POU/GEN/BV-002 | | | +| TP label | DOR Requirements. Duplicate bundle | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | DORReq 5;M | | +| Test purpose | Check that:
    The DOR prevents duplication of data when using the RESTful FHIR API. | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_010 | | | +| Other PICSSs | | | | +| Initial condition | Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02). | | | +| Test procedure |
    1. 1. Ask the DOR under test to upload an Observation resource (create) as a complete bundle to the simulated Receiver using transaction PCH-02.
    2. 2. Ask the DOR under test to upload an Observation resource (conditional create) as a complete bundle to the simulated Receiver using transaction PCH-02.
    | | | +| Pass/fail criteria |
    • • Only one bundle was received, with no duplicate data.
    | | | +| Notes | | | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/HFS/SEN/POU/GEN/BV-003_A | | | +| TP label | PCH-01 Message Semantics. OAuth identity token (PCH-01) | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | CommPCH-01MessSem 1;M | | +| Test purpose |

    Check that:

    The OAuth identity token is recognized by the Device Observation Consumer for acceptance of the message but how that identity token is obtained is a business trust relationship decision.

    | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_009 AND C_SEN_GEN_011 | | | +| Other PICSSs | | | | +| Initial condition |

    Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02).

    | | | +| Test procedure |
    1. Send a FHIR Bundle by DOR under test to simulated receiver using transaction PCH-01.
    | | | +| Pass/fail criteria |
    • The OAuth identity token was recognized by the Device Observation Consumer (DOC) upon receiving a valid response.
    | | | +| Notes | | | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/HFS/SEN/POU/GEN/BV-003_B | | | +| TP label | PCH-02 Message Semantics. OAuth identity token PCH-02 | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | CommPCH-02MessSem 1;M | | +| Test purpose |

    Check that:

    The OAuth identity token is recognized by the DOC for acceptance of the message but how that identity token is obtained is a business trust relationship decision.

    | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_010 AND C_SEN_GEN_011 | | | +| Other PICSSs | | | | +| Initial condition |

    Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02).

    | | | +| Test procedure |
    1. Send a FHIR Bundle by DOR under test to simulated receiver using transaction PCH-02.
    | | | +| Pass/fail criteria |
    • The OAuth identity token was recognized by the DOC upon receiving a valid response.
    | | | +| Notes | | | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/POU/GEN/BV-004 | | | | +| TP label | PCH-01 Message Semantics. Bundle elements | | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | | +| | Testable items | CommPCH-01MessSem 4;M | CommPCH-01MessSem 5;M | CommPCH-01MessSem 6;M | +| | | CommPCH-01MessSem 7;M | | | +| Test purpose |

    Check that:

    Only the create, conditional create and conditional update FHIR transactions are specified in the Bundle using the PCH-01 transaction.

    [AND]

    The Patient, PHD Device, PHG Device, are sent every time.

    [AND]

    The Patient, PHD Device, and PHG Device resource entries specify the conditional create FHIR transaction or conditional update on the identifier value and system elements.

    [AND]

    Observation resource entries created from stored data specify the conditional create FHIR transaction on the identifier value element.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_009 | | | | +| Other PICSSs | | | | | +| Initial condition |

    Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02).

    | | | | +| Test procedure |
    1. Ask the DOR under test to upload an Observation resource as a complete bundle to the simulated Receiver using transaction PCH-01.
    | | | | +| Pass/fail criteria |
    • The create, conditional create and conditional update FHIR transactions are specified in the Bundle.
    • The Patient, PHD Device and PHG Device are specified in the Bundle.
    • The Patient, PHD Device and PHG Device resource entries specify the conditional create FHIR transaction or conditional update on the identifier value and system elements.
    • Observation resource entries created from stored data specify the conditional create FHIR transaction on the identifier value element.
    | | | | +| Notes | | | | | + +| | | | | +|-----------------|--------------------------------------------------------------------|-----------------------|------------| +| TP Id | TP/HFS/SEN/POU/GEN/BV-005 | | | +| TP label | PCH-02 RESTful FHIR PHD Data TLS security and OAuth authentication | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | CommPCH-02;M | DORReq 4;M | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    The DOR Actors support TLS security and OAuth authentication for this Integrating the Healthcare Enterprise (IHE) transaction. | +| Applicability | C_SEN_000 AND C_SEN_GEN_009 AND C_SEN_GEN_010 AND C_SEN_GEN_011 AND C_SEN_GEN_012 | +| Other PICSSs | | +| Initial condition | Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02). | +| Test procedure | 1. Ask the DOR under test to upload an Observation resource as a complete bundle to the simulated Receiver using transaction PCH-02. | +| Pass/fail criteria |
    • The DOR supports TLS security and OAuth authentication for this IHE transaction.
    | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/POU/GEN/BV-006 | | | +| TP label | PCH-02 Message Semantics | | | +| Coverage | Spec | [IHE_PCD_Suppl_POU] | | +| | Testable items | CommPCH-02MessSem 2;M | CommPCH-02MessSem 3;M | +| | | CommPCH-02MessSem 5;M | CommPCH-02MessSem 4;M | +| Test purpose | Check that:

    The DOR either ensures that the Patient, PHD Device, and PHG Device resource do not exist on the server (perhaps by doing a GET) or uses the conditional create or conditional update transaction on the identifier value.
    [AND]
    Observation resource entries created from stored data specify the conditional create FHIR transaction on the identifier value element.
    [AND]
    The upload attempts to filter duplicate resources instead of relying on the conditional create and conditional update FHIR transactions. | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_010 | | | +| Other PICSSs | | | | +| Initial condition | Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02). | | | +| Test procedure | 1. Ask the DOR under test to upload an Observation resource as a complete bundle to the simulated Receiver using transaction PCH-02.

    2. Ask the DOR under test to upload an Observation resource (conditional create) as a complete bundle to the simulated Receiver using transaction PCH-02. | | | +| Pass/fail criteria |
    • The resource has not been created in step 2.
    | | | +| Notes | | | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/POU/GEN/BV-007 | | | | +| TP label | RESTful FHIR API. FHIR version | | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | | +| | Testable items | A2-FHIRResource 1;M | | | +| Test purpose |

    Check that:

    The DOR supporting the Communicate RESTful FHIR PHD Data (PCH-02) transaction uses the Patient, Device, Observation and optionally the Bundle resources. The elements used in these resources are compatible with FHIR version 4.0.0.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_010 | | | | +| Other PICSSs | | | | | +| Initial condition |

    Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02).

    | | | | +| Test procedure |
    1. Ask the DOR under test to upload an Observation resource as a complete bundle to the simulated Receiver using transaction PCH-02.
    | | | | +| Pass/fail criteria |
    • The elements used in these resources are compatible with FHIR version 4.0.0.
    | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/HFS/SEN/POU/GEN/BV-008 | | | | +| TP label | RESTful FHIR API. Operations | | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | | +| | Testable items | A2-RESTfulFHIR-API 1;M | | | +| Test purpose |

    Check that:

    DORs following the POU only use the following RESTful FHIR operations for uploading:

    • Create
    • Conditional Create
    • Conditional Update
    | | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_010 | | | | +| Other PICSSs | | | | | +| Initial condition |

    Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02).

    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. Ask the DOR under test to create an Observation resource as a complete bundle to the simulated Receiver using transaction PCH-02.
    2. Ask the DOR under test to use conditional create to upload an Observation resource as a complete bundle to the simulated Receiver using transaction PCH-02.
    3. Ask the DOR under test to use conditional update to upload an Observation resource as a complete bundle to the simulated Receiver using transaction PCH-02.
    | +| Pass/fail criteria |
    • Step 1 creates the resource correctly.
    • Step 2 does not create the resource as it is already on the server.
    • Step 3 correctly updates the resource.
    | +| Notes | DOR is responsible for converting patient measurement data into FHIR resources and uploading it to a DOC using the RESTful FHIR API. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/HFS/SEN/POU/GEN/BV-009 | | | +| TP label | RESTful FHIR API. Resources | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | A2-RESTfulFHIR-API 2;M | | +| Test purpose | Check that:
    Health and Fitness Servers supporting the Communicate RESTful FHIR PHD Data transaction support the Patient, Device and Observation resources as well as the FHIR transaction Bundle. | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_010 | | | +| Other PICSSs | | | | +| Initial condition | Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02). | | | +| Test procedure |
    1. Upload patient resource. The first transaction is a FHIR PHD Data transaction PCH-02.
    2. Upload device resource. The second transaction is a FHIR PHD Data transaction PCH-02.
    3. Upload observation resource. The third transaction is a FHIR PHD Data transaction PCH-02.
    | | | +| Pass/fail criteria |
    • The RESTful FHIR PHD data transaction supports patient, device, and observation resources as well as the FHIR transaction bundle.
    | | | +| Notes | | | | + +| | | | | +|-----------------|----------------------------------|------------------------|--| +| TP Id | TP/HFS/SEN/POU/GEN/BV-010 | | | +| TP label | PHD Patient Resource. Logical Id | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | A2.1PHD-PatientRes 1;M | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    DOR does not upload a Patient resource. It uses the logical Id in all resources that require a reference to a Patient resource. | +| Applicability | C_SEN_000 AND C_SEN_GEN_010 | +| Other PICSS | | +| Initial condition | Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02). | +| Test procedure | 1. The DOR is given the logical Id of a Patient resource by the service provider. | +| Pass/fail criteria |
    • • The DOR will not load a patient resource, but rather the logical identification of a resource that requires a reference to a patient resource.
    | +| Notes | Patient information is a highly sensitive issue. To support protection of Personal Health Information (PHI) the POU Profile supports an option where the DOR is given the logical Id (not the identifier) of a Patient resource by the service provider. How this logical Id is obtained is not specified by the POU Profile. In that case, the DOR shall not upload a Patient resource. It shall use the logical Id in all resources that require a reference to a Patient resource. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------| +| TP Id | TP/HFS/SEN/POU/GEN/BV-011 | | | +| TP label | PHD Patient Resource. Duplicate data | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | A2.1PHD-PatientRes 3;M | A2.2PHD-DevRes 1;M | +| | | A2.4PHD-BOP;M | A2.2PHD-DevRes 2;M | +| Test purpose | Check that:
    The DOR either ensures the resource does not exist on the server before using a create operation or uses a conditional create or conditional update operation on the identifier system and value elements. | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_010 | | | +| Other PICSS | | | | +| Initial condition | Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02). | | | +| Test procedure | 1. The simulated receiver uses a GET resource operation.
    2. The same resource is uploaded using a conditional create or update conditional operation. | | | +| Pass/fail criteria |
    • • Step 2 returns a fail verdict.
    | | | +| Notes | | | | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2017)] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.811] Recommendation ITU-T H.811 (2017), *Interoperability design guidelines for personal connected health systems: Personal Health Devices interface*. +- [b-ITU-T H.812.1] Recommendation ITU-T H.812.1 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Observation Upload certified*. +- [b-ITU-T H.812.2] Recommendation ITU-T H.812.2 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability*. +- [b-ITU-T H.812.3] Recommendation ITU-T H.812.3 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability*. +- [b-ITU-T H.812.4] Recommendation ITU-T H.812.4 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability*. +- [b-ITU-T H.813] Recommendation ITU-T H.813 (2017), *Interoperability design guidelines for personal connected health systems: Healthcare Information System interface*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003), *ETSI drafting rules*. + + +- [b-HFSR PICS & PIXIT] HFS Receiver PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.8. + +- [b-HL7 V3 HRF] Health Level Seven (2014), *HL7 Version 3 Specification: hData Record Format, Release 1*. +[http://www.hl7.org/documentcenter/private/standards/v3/V3\\_ITS\\_HDATA\\_RF\\_R1\\_2014JUN.pdf](http://www.hl7.org/documentcenter/private/standards/v3/V3_ITS_HDATA_RF_R1_2014JUN.pdf) +- [b-HSTP-H812-FHIR] Technical Paper ITU-T HSTP-H812-FHIR (2019), *Interoperability design guidelines for personal health systems: Services interface: FHIR Observation Upload for trial implementation*. +- [b-IETF RFC 3339] IETF RFC 3339 (2002), *Date and Time on the Internet: Timestamps*. + +- [b-IHE\_PCD\_Suppl\_POU] IHE Patient Care Device Technical Framework Supplement (2020), *Personal Health Device Observation Upload (POU)*. +[https://www.ihe.net/uploadedFiles/Documents/PCD/IHE\\_PCD\\_Suppl\\_POU.pdf](https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_Suppl_POU.pdf) + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.830.18-202106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.830.18-202106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1 --- /dev/null +++ b/marked/H/T-REC-H.830.18-202106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c395c4bbde83b1e232652a43f51538278c116f51f710c37e20a073f7333726c8 +size 6134 diff --git a/marked/H/T-REC-H.830.18-202106-I_PDF-E/raw.md b/marked/H/T-REC-H.830.18-202106-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..41bc5ff78ea086525754f9b8c7a4ecfc65fe4dcb --- /dev/null +++ b/marked/H/T-REC-H.830.18-202106-I_PDF-E/raw.md @@ -0,0 +1,543 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.830.18** + +(06/2021) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Services interface Part 18: Personal +Health Device Observation Upload (POU) +Receive** + +Recommendation ITU-T H.830.18 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Content delivery and ubiquitous sensor network applications | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.830.18 + +# Conformance of ITU-T H.810 personal health system: Services interface Part 18: Personal Health Device Observation Upload (POU) Receiver + +## Summary + +Recommendation ITU-T H.830.18 provides a test suite structure (TSS) and the test purposes (TPs) for the Personal Health Device Observation Upload (POU) receiver in the Services interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2019) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.830.18 includes an electronic attachment with the protocol implementation conformance statements (PICSs) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.830.18 | 2021-06-13 | 16 | 11.1002/1000/14688 | + +## Keywords + +Capability exchange, conformance testing, continua design guidelines, e-health, health & fitness service, ITU-T H.810, personal connected health devices, POU, services interface. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2021 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|--------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Test suite structure ..... | 5 | +| 7 | Electronic attachment ..... | 7 | +| Annex A | Test procedures..... | 8 | +| A.1 | Test purpose definition conventions..... | 8 | +| A.2 | Subgroup 1.10.1: General (GEN)..... | 9 | +| | Bibliography..... | 11 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICSs) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# Introduction + +The table below shows the revision history of this test specification. + +| Version | Date | Revision history | +|---------|------------|------------------------------------------------------------------------------------------------| +| 1.0 | 2020-12-21 | Initial release for the inclusion of Personal Health Device Observation Upload (POU) receiver. | + +# Recommendation ITU-T H.830.18 + +# Conformance of ITU-T H.810 personal health system: Services interface Part 18: Personal Health Device Observation Upload (POU) Receiver + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TPs) for the Services interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2019)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TPs for the Services interface have been divided into the parts specified below. This Recommendation covers Part 18. + +- Part 1: Web services interoperability. Health & Fitness Service sender +- Part 2: Web services interoperability. Health & Fitness Service receiver +- Part 3: SOAP/ATNA. Health & Fitness Service sender +- Part 4: SOAP/ATNA. Health & Fitness Service receiver +- Part 5: PCD-01 HL7 Messages. Health & Fitness Service sender +- Part 6: PCD-01 HL7 Messages. Health & Fitness Service receiver +- Part 7: Consent Management. Health & Fitness Service sender +- Part 8: Consent Management. Health & Fitness Service receiver +- Part 9: hData Observation Upload. Health & Fitness Service sender +- Part 10: hData Observation Upload. Health & Fitness Service receiver +- Part 11: Questionnaires. Health & Fitness Service sender +- Part 12: Questionnaires. Health & Fitness Service receiver +- Part 13: Capability Exchange. Health & Fitness Service sender +- Part 14: Capability Exchange. Health & Fitness Service receiver +- Part 15: FHIR Observation Upload. Health & Fitness Service sender +- Part 16: FHIR Observation Upload. Health & Fitness Service receiver. +- Part 17: POU. Health & Fitness Service sender. +- **Part 18: POU. Health & Fitness Service receiver.** + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a standalone document, the status of a Recommendation. + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICSs) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# **3 Definitions** + +### **3.1 Terms defined elsewhere** + +None. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|-------------------------------------------------------| +| AHD | Application Hosting Device | +| ATNA | Audit Trail and Node Authentication | +| BLE | Bluetooth Low Energy | +| BT HDP | Bluetooth Health Device Profile | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DOC | Device Observation Consumer | +| DUT | Device Under Test | +| FHIR | Fast Healthcare Interoperability Resources | +| HFS | Health & Fitness Service | +| HFSR | Health & Fitness Service Receiver | +| HFSS | Health & Fitness Service Sender | +| HL7 | Health Level 7 | +| HTTP | Hypertext Transfer Protocol | +| IHE | Integrating the Healthcare Enterprise | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| JSON | JavaScript Object Notation | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PCD | Patient Care Device | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | + +| | | +|-------|------------------------------------------------| +| POU | Personal Health Device Observation Upload | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SOAP | Simple Object Access Protocol | +| TLS | Transport Level Security | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| URI | Uniform Resource Identifier | +| WS | Web Service | +| WSI | Web Services Interoperability | +| XDR | Cross-Enterprise Document Reliable Interchange | +| XML | extensible Markup Language | +| ZB | Zigbee | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-IHE\_PCD\_Suppl\_POU]. + +- SHALL is equivalent to "must" or "it is required to". +- SHALL NOT is equivalent to "must not" or "it is not allowed". +- SHOULD is equivalent to "it is recommended to". +- SHOULD NOT is equivalent to "it is not recommended to". +- MAY is equivalent to "is permitted". +- MAY NOT is equivalent to "it is not required that". + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of designations that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2019 | – | 8.0 | Release 2019 of the CDG including maintenance updates of the CDG 2017 and additional guidelines that cover new functionalities. | – | +| 2017 | – | 7.0 | Release 2017 of the CDG including maintenance updates of the CDG 2016 and additional guidelines that cover new functionalities. | – | +| 2016 plus errata | [b-ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of [ITU-T H.810] is split into eight parts in the ITU-T H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata. | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure + +The test procedures (TPs) for the Services interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 1.7.1 and 1.7.2 (shown in bold): + +– Group 1: HFS sender (HFSS) + +- Group 1.1: Web services interoperability (WSI) + - Subgroup 1.1.1: Basic profile (BP) + - Subgroup 1.1.2: Basic security profile (BSP) + - Subgroup 1.1.3: Reliable messaging (RM) +- Group 1.2: Simple object access protocol (SOAP) + - Subgroup 1.2.1: SOAP headers (HEAD) +- Group 1.3: Audit trail and node authentication (ATNA) + - Subgroup 1.3.1: General (GEN) + - Subgroup 1.3.2: PCD-01 (PCD-01) + - Subgroup 1.3.3: Consent Management (CM) +- Group 1.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 1.4.1: General (GEN) + - Subgroup 1.4.2: Design guidelines (DG) + - Subgroup 1.4.3: Pulse oximeter (PO) + - Subgroup 1.4.4: Blood pressure monitor (BPM) + - Subgroup 1.4.5: Thermometer (TH) + - Subgroup 1.4.6: Weighing scales (WEG) + - Subgroup 1.4.7: Glucose meter (GL) + - Subgroup 1.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 1.4.9: Strength fitness equipment (ST) + - Subgroup 1.4.10: Independent living activity hub (HUB) + - Subgroup 1.4.11: Adherence monitor (AM) + - Subgroup 1.4.12: Peak expiratory flow monitor (PF) + - Subgroup 1.4.13: Body composition analyser (BCA) + - Subgroup 1.4.14: Basic electrocardiograph (ECG) + - Subgroup 1.4.15: International normalized ratio (INR) + - Subgroup 1.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.4.17: Insulin pump (IP) + - Subgroup 1.4.18: Continuous glucose monitor (CGM) +- Group 1.5: Consent Management (CM) + - Subgroup 1.5.1: HFS XDR transaction (TRANS) + - Subgroup 1.5.2: HFS metadata validation (META) + - Subgroup 1.5.3: HFS consent directive validation (CDV) +- Group 1.6: hData Observation Upload (HDATA) + - Subgroup 1.6.1: General (GEN) + +- Group 1.7: Questionnaires (QUE) + - Subgroup 1.7.1: General (GEN) + - Subgroup 1.7.2: CDA validation (CDA) +- Group 1.8: Capability Exchange (CE) + - Subgroup 1.8.1: General (GEN) + - Subgroup 1.8.2: hData record format (HRF) +- Group 1.9: FHIR Observation Upload (FHIR) + - Subgroup 1.9.1: General (GEN) + - Subgroup 1.9.2: FHIR Encoding Guidelines (ENC) +- Group 1.10: Personal Health Device Observation Upload (POU) + - Subgroup 1.10.1: General (GEN) + +### – Group 2: HFS receiver (HFSR) + +- Group 2.1: Web service interoperability (WSI) + - Subgroup 2.1.1: Basic profile (BP) + - Subgroup 2.1.2: Basic security profile (BSP) + - Subgroup 2.1.3: Reliable messaging (RM) +- Group 2.2: SOAP (SOAP) + - Subgroup 2.2.1: SOAP headers (HEAD) +- Group 2.3: Audit (ATNA) + - Subgroup 2.3.1: General (GEN) + - Subgroup 2.3.2: PCD-01 (PCD-01) + - Subgroup 2.3.3: Consent Management (CM) +- Group 2.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 2.4.1: General (GEN) + - Subgroup 2.4.2: Design guidelines (DG) + - Subgroup 2.4.3: Pulse oximeter (PO) + - Subgroup 2.4.4: Blood pressure monitor (BPM) + - Subgroup 2.4.5: Thermometer (TH) + - Subgroup 2.4.6: Weighing scales (WEG) + - Subgroup 2.4.7: Glucose meter (GL) + - Subgroup 2.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 2.4.9: Strength fitness equipment (ST) + - Subgroup 2.4.10: Independent living activity hub (HUB) + - Subgroup 2.4.11: Adherence monitor (AM) + - Subgroup 2.4.12: Peak expiratory flow monitor (PF) + - Subgroup 2.4.13: Body composition analyser (BCA) + - Subgroup 2.4.14: Basic electrocardiograph (ECG) + - Subgroup 2.4.15: International normalized ratio (INR) + - Subgroup 2.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.4.17: Insulin pump (IP) + - Subgroup 2.4.18: Continuous glucose monitor (CGM) + +- Group 2.5: Consent Management (CM) + - Subgroup 2.5.1: HFS XDR transaction (TRANS) + - Subgroup 2.5.2: HFS service validation (SER) +- Group 2.6: hData Observation Upload (HDATA) + - Subgroup 2.6.1: General (GEN) + - Subgroup 2.6.2: hData record format (HRF) +- Group 2.7: Questionnaires (QUE) + - Subgroup 2.7.1: General (GEN) + - Subgroup 2.7.2: CDA validation (CDA) + - Subgroup 2.7.3: hData record format (HRF) +- Group 2.8: Capability Exchange (CE) + - Subgroup 2.8.1: General (GEN) + - Subgroup 2.8.2: hData record format (HRF) +- Group 2.9: FHIR Observation Upload (FHIR) + - Subgroup 2.9.1: General (GEN) +- **Group 2.10: Personal Health Device Observation Upload (POU)** + - **Subgroup 1.10.1: General (GEN)** + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICSs) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . See [b-HFSR PICS & PIXIT] and [b-HFSS PICS & PIXIT]. + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICSs" and "PIXIT", respectively, during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICSs, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +## Test procedures + +(This annex forms an integral part of this Recommendation.) + +### A.1 Test purpose definition conventions + +The TPs are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: +Each TP identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - HFS: Health & Fitness Services Interface + - : This is the device under test. + - SEN: HFS sender + - REC: HFS receiver + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the TP. +- **TP label:** This is title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if a test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the DUT within that scope of the test (specialization, transport used, etc.). +- **Other PICSs:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of test case execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 1.10.1: General (GEN) + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/HFS/REC/POU/GEN/BV-000 | | | +| TP label | POU Profile – Actors and Transactions (DOC) | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | IHETrans;M | DOCReq 2;M | +| | | CommPCH-01MessSem 3;M | POUActorTrans;M | +| Test purpose |

    Check that:

    To claim compliance with the POU, a Device Observation Consumer (DOC) supports all required transactions.

    1. 1. Communicate fast healthcare interoperability resources (FHIR) Personal Health Device (PHD) Data (PCH-01)
    2. 2. Communicate RESTful FHIR PHD Data (PCH-02)

    [AND]

    Supports one of the two transactions.

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_009 AND C_REC_GEN_010 | | | +| Other PICSSs | | | | +| Initial condition |

    Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a Personal Health Device Observation Upload (POU) that requires transport level security (TLS) and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02).

    | | | +| Test procedure |
    1. 1. Ask the DOC under test to receive an observation resource as a complete package (FHIR PHD Data (PCH-01) transaction) from the simulated sender and wait for the response.
    2. 2. Ask the DOC under test to receive an observation resource as a complete package (RESTful FHIR PHD Data (PCH-02) transaction) from the simulated sender and wait for the response.
    | | | +| Pass/fail criteria |
    • • The first response uses transaction FHIR PHD Data (PCH-01).
    • • The second response uses transaction RESTful FHIR PHD Data (PCH-02).
    | | | +| Notes | | | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| TP Id | TP/HFS/REC/POU/GEN/BV-001 | | | +| TP label | DOC Requirements. Transaction and bundle | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | CommPCH-01ExpActions;M | A2.1PHD-PatientRes 2;M | +| | | | | +| Test purpose |

    Check that:

    The DOC transfers the FHIR Bundle to a grouped Device Observation Reporter that dispatches the information using another Integrating the Healthcare Enterprise (IHE) transaction, for example, a PCD transaction containing a V2 message or any other IHE actor that can make use of this data and dispatch it to consumer actors.

    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [AND]
    The DOC does not reject such a resource due to the Patient resource reference. The referenced Patient resource is not accessible from the DOC. | +| Applicability | C_REC_000 AND C_REC_GEN_009 | +| Other PICSS | | +| Initial condition | Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data PCH-01 and RESTful FHIR PHD Data (PCH-02). | +| Test procedure | 1. Ask the DOC under test to upload an Observation resource as a complete bundle to the simulated Receiver using transaction PCH-01. | +| Pass/fail criteria |
    • The transaction of the FHIR Bundle is correct.
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------| +| TP Id | TP/HFS/REC/POU/GEN/BV-002 | | | +| TP label | DOC Requirements. TLS security and OAuth authentication | | | +| Coverage | Spec | [b-IHE_PCD_Suppl_POU] | | +| | Testable items | CommPCH-02;M | DOCReq 1;M | +| Test purpose | Check that:
    The DOC Actor shall support TLS security and OAuth authentication for this IHE transaction. | | | +| Applicability | C_REC_000 AND C_REC_GEN_009 AND C_REC_GEN_010 AND C_REC_GEN_011 AND C_REC_GEN_012 | | | +| Other PICSS | | | | +| Initial condition | Simulated HFS supports POU Server and Capability Exchange Continua Certified Capability Classes, so it has an POU API that can accept a POU that requires TLS and an authentication token. The HFS supports all available OAuth 2.0 authorization grant types (so they are listed in the grantTypes element of its OAuthDescriptor). Simulated HFS has no previously stored resources and supports both transactions: FHIR PHD data (PCH-01) and RESTful FHIR PHD Data (PCH-02). | | | +| Test procedure | 1. Ask the DOC under test to upload an Observation resource as a complete bundle to the simulated Receiver. | | | +| Pass/fail criteria |
    • The DOC supports TLS security and OAuth authentication for this IHE transaction.
    | | | +| Notes | | | | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2017)] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal health systems: Introduction*. +- [b-ITU-T H.811] Recommendation ITU-T H.811 (2017), *Interoperability design guidelines for personal connected health systems: Personal Health Devices interface*. +- [b-ITU-T H.812.1] Recommendation ITU-T H.812.1 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Observation Upload certified*. +- [b-ITU-T H.812.2] Recommendation ITU-T H.812.2 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability*. +- [b-ITU-T H.812.3] Recommendation ITU-T H.812.3 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability*. +- [b-ITU-T H.812.4] Recommendation ITU-T H.812.4 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability*. +- [b-ITU-T H.813] Recommendation ITU-T H.813 (2017), *Interoperability design guidelines for personal connected health systems: Healthcare Information System interface*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003), *ETSI drafting rules*. + + +- [b-HL7 V3 HRF] Health Level Seven (2014), *HL7 Version 3 Specification: hData Record Format, Release 1*. +[http://www.hl7.org/documentcenter/private/standards/v3/V3\\_ITS\\_HDATA\\_RF\\_R1\\_2014JUN.pdf](http://www.hl7.org/documentcenter/private/standards/v3/V3_ITS_HDATA_RF_R1_2014JUN.pdf) +- [b-HSTP-H812-FHIR] Technical Paper ITU-T HSTP-H812-FHIR (2019), *Interoperability design guidelines for personal health systems: Services interface: FHIR Observation Upload for trial implementation*. +- [b-IETF RFC 3339] IETF RFC 3339 (2002), *Date and Time on the Internet: Timestamps*. + +- [b-IHE\_PCD\_Suppl\_POU] IHE Patient Care Device Technical Framework Supplement (2020), *Personal Health Device Observation Upload (POU)*. +[https://www.ihe.net/uploadedFiles/Documents/PCD/IHE\\_PCD\\_Suppl\\_POU.pdf](https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_Suppl_POU.pdf) +- [b-HFSR PICS & PIXIT] HFS Receiver PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.8. + +- [b-HFSS PICS & PIXIT] HFS Sender PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.8. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.830.2-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.830.2-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..045c2f68931c7b52011d1a1f734b907130922698 --- /dev/null +++ b/marked/H/T-REC-H.830.2-201704-I_PDF-E/raw.md @@ -0,0 +1,1384 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.830.2** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Services interface Part 2: Web services +interoperability: Health & Fitness Service +receiver** + +Recommendation ITU-T H.830.2 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.830.2 + +# Conformance of ITU-T H.810 personal health system: Services interface Part 2: Web services interoperability: Health & Fitness Service receiver + +## Summary + +Recommendation ITU-T H.830.2 provides a test suite structure (TSS) and the test purposes (TP) for Web services interoperability for messages through the Health & Fitness Service (HFS) receiver in the Services interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.830.2 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 2: Web Services Interoperability. HFS Receiver (Version 1.5, 2017-03-14), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.832 | 2015-01-13 | 16 | 11.1002/1000/12250 | +| 1.0 | ITU-T H.830.2 | 2015-01-13 | 16 | 11.1002/1000/12588 | +| 2.0 | ITU-T H.830.2 | 2016-07-14 | 16 | 11.1002/1000/12922 | +| 3.0 | ITU-T H.830.2 | 2017-04-13 | 16 | 11.1002/1000/13202 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, Health & Fitness Service receiver, ITU-T H.810, personal connected health devices, Services Interface, Web services interoperability. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|----------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Test suite structure (TSS) ..... | 5 | +| 7 | Electronic attachment ..... | 7 | +| Annex A | Test purposes ..... | 8 | +| A.1 | TP definition conventions..... | 8 | +| A.2 | Subgroup 2.1.1 – Basic profile (BP) ..... | 9 | +| A.3 | Subgroup 2.1.2 – Basic security profile (BSP)..... | 25 | +| A.4 | Subgroup 2.1.3 – Reliable messaging (RM) ..... | 32 | +| | Bibliography..... | 54 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 2: Web Services Interoperability. HFS Receiver (Version 1.5, 2017-03-14), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.1 | 2012-10-05 | Initial release for Test Tool DG2011. It is the same version as "TSS&TP_1.5_WAN_PART_2_(REC WS-I)_v1.1.doc" because new features included in [b-CDG 2011] do not affect the test procedures specified in this document. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. It is the same version as "TSS&TP_DG2011_WAN_PART_2_(REC WS-I)_v1.1.doc" because new features included in [b-CDG 2012] do not affect the test procedures specified in this document. | +| 1.1 | 2014-01-24 | Initial release for Test Tool DG2013. It is the same version as "TSS&TP_DG2012_WAN_PART_2_(REC WS-I)_v1.1.doc" because new features included in CDG 2013 [b-ITU-T H.810 (2013)]/[b-CDG 2013] do not affect the test procedures specified in this document. | +| 1.2 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_WAN_PART_2_(REC WS-I)_v1.1.doc" as baseline and it adds new features included in Documentation Enhancements:
    • "Other PICS" row has been added
    | +| 1.3 | 2015-07-01 | Initial release for Test Tool DG2015:
    • Test suite structure modified
    • Applicability modified due to the inclusion of hData OU
    | +| 1.4 | 2016-09-20 | Initial release for Test Tool DG2016. It implements changes according to [ITU-T H.810 (2016)]/[b-CDG 2016] (Iris + Errata) refreshments. | +| 1.5 | 2017-03-14 | Editorial: added insulin pump and continuous glucose monitor specializations to the TSS list in clause 6. | + +## Recommendation ITU-T H.830.2 + +## Conformance of ITU-T H.810 personal health system: Services interface Part 2: Web services interoperability: Health & Fitness Service receiver + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Services interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Services interface have been divided into the parts specified below. This Recommendation covers Part 2. + +- Part 1: Web services interoperability Health & Fitness Service sender +- **Part 2: Web services interoperability Health & Fitness Service receiver** +- Part 3: SOAP/ATNA. Health & Fitness Service sender +- Part 4: SOAP/ATNA. Health & Fitness Service receiver +- Part 5: PCD-01 HL7 messages. Health & Fitness Service sender +- Part 6: PCD-01 HL7 messages. Health & Fitness Service receiver +- Part 7: Consent Management. Health & Fitness Service sender +- Part 8: Consent Management. Health & Fitness Service receiver +- Part 9: hData Observation Upload. Health & Fitness Service sender +- Part 10: hData Observation Upload. Health & Fitness Service receiver +- Part 11: Questionnaires. Health & Fitness Service sender +- Part 12: Questionnaires. Health & Fitness Service receiver + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. + +[ITU-T H.812] Recommendation ITU-T H.812 (2016), *Interoperability design guidelines for personal health systems: Services interface: Common certified capability class*. + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- [ITU-T H.812.1] Recommendation ITU-T H.812.1 (2016), *Interoperability design guidelines for personal health systems: Services interface: Observation upload certified capability class.* +- [ITU-T H.812.2] Recommendation ITU-T H.812.2 (2016), *Interoperability design guidelines for personal health systems: Services interface: Questionnaires certified capability class.* +- [ITU-T H.812.3] Recommendation ITU-T H.812.3 (2016), *Interoperability design guidelines for personal health systems: Services interface: Capability exchange certified capability class.* +- [ITU-T H.812.4] Recommendation ITU-T H.812.4 (2016), *Interoperability design guidelines for personal health systems: Services interface: Authenticated persistent session certified capability class.* +- [OASIS/WS-I BP] OASIS/WS-I (2006), *Basic Profile Version 1.1.* + +- [OASIS/WS-I BSP] OASIS/WS-I (2007), *Basic Security Profile Version 1.0.* + +- [OASIS WS-I RM] OASIS (2007), *Web Services Reliable Messaging (WS-Reliable Messaging) Version 1.1.* + + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------| +| AHD | Application Hosting Device | +| ATNA | Audit Trail and Node Authentication | +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| HFS | Health & Fitness Service | +| HFSS | Health & Fitness Service Sender | +| HFSR | Health & Fitness Service Receiver | +| HL7 | Health Level 7 | +| HTTP | Hypertext Transfer Protocol | +| HTTPS | Hypertext Transfer Protocol Secure | + +| | | +|-------|-------------------------------------------------------| +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| URI | Uniform Resource Identifier | +| USB | Universal Serial Bus | +| WAN | Wide Area Network | +| WDM | Windows Driver Model | +| WS | Web Service | +| WSDL | Web Service Description Language | +| XML | extensible Markup Language | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Services interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 2.1.1 to 2.1.3 (shown in bold). + +- Group 1: HFS sender (HFSS) + - Group 1.1: Web services interoperability (WSI) + - Subgroup 1.1.1: Basic profile (BP) + - Subgroup 1.1.2: Basic security profile (BSP) + - Subgroup 1.1.3: Reliable messaging (RM) + - Group 1.2: Simple object access protocol (SOAP) + - Subgroup 1.2.1: SOAP headers (HEAD) + - Group 1.3: Audit trail and node authentication (ATNA) + - Subgroup 1.3.1: General (GEN) + - Subgroup 1.3.2: PCD-01 (PCD-01) + - Subgroup 1.3.3: Consent Management (CM) + - Group 1.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 1.4.1: General (GEN) + - Subgroup 1.4.2: Design guidelines (DG) + - Subgroup 1.4.3: Pulse oximeter (PO) + - Subgroup 1.4.4: Blood pressure monitor (BPM) + - Subgroup 1.4.5: Thermometer (TH) + - Subgroup 1.4.6: Weighing scales (WEG) + - Subgroup 1.4.7: Glucose meter (GL) + - Subgroup 1.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 1.4.9: Strength fitness equipment (ST) + - Subgroup 1.4.10: Independent living activity hub (HUB) + - Subgroup 1.4.11: Adherence monitor (AM) + - Subgroup 1.4.12: Peak expiratory flow monitor (PF) + - Subgroup 1.4.13: Body composition analyser (BCA) + - Subgroup 1.4.14: Basic electrocardiograph (ECG) + - Subgroup 1.4.15: International normalized ratio (INR) + - Subgroup 1.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.4.17: Insulin pump (IP) + - Subgroup 1.4.18: Continuous glucose monitor (CGM) + - Group 1.5: Consent Management (CM) + - Subgroup 1.5.1: HFS XDR transaction (TRANS) + - Subgroup 1.5.2: HFS metadata validation (META) + - Subgroup 1.5.3: HFS consent directive validation (CDV) + - Group 1.6: hData Observation Upload (HDATA) + - Subgroup 1.6.1: General (GEN) + - Group 1.7: Questionnaires (QUE) + - Subgroup 1.7.1: General (GEN) + +- Subgroup 1.7.2: CDA validation (CDA) + +– Group 2: HFS receiver (HFSR) + +- **Group 2.1: Web service interoperability (WSI)** + - **Subgroup 2.1.1: Basic profile (BP)** + - **Subgroup 2.1.2: Basic security profile (BSP)** + - **Subgroup 2.1.3: Reliable messaging (RM)** +- Group 2.2: SOAP (SOAP) + - Subgroup 2.2.1: SOAP headers (HEAD) +- Group 2.3: Audit (ATNA) + - Subgroup 2.3.1: General (GEN) + - Subgroup 2.3.2: PCD-01 (PCD-01) + - Subgroup 2.3.3: Consent Management (CM) +- Group 2.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 2.4.1: General (GEN) + - Subgroup 2.4.2: Design guidelines (DG) + - Subgroup 2.4.3: Pulse oximeter (PO) + - Subgroup 2.4.4: Blood pressure monitor (BPM) + - Subgroup 2.4.5: Thermometer (TH) + - Subgroup 2.4.6: Weighing scales (WEG) + - Subgroup 2.4.7: Glucose meter (GL) + - Subgroup 2.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 2.4.9: Strength fitness equipment (ST) + - Subgroup 2.4.10: Independent living activity hub (HUB) + - Subgroup 2.4.11: Adherence monitor (AM) + - Subgroup 2.4.12: Peak expiratory flow monitor (PF) + - Subgroup 2.4.13: Body composition analyser (BCA) + - Subgroup 2.4.14: Basic electrocardiograph (ECG) + - Subgroup 2.4.15: International normalized ratio (INR) + - Subgroup 2.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.4.17: Insulin pump (IP) + - Subgroup 2.4.18: Continuous glucose monitor (CGM) +- Group 2.5: Consent Management (CM) + - Subgroup 2.5.1: HFS XDR transaction (TRANS) + - Subgroup 2.5.2: HFS service validation (SER) +- Group 2.6: hData Observation Upload (HDATA) + - Subgroup 2.6.1: General (GEN) + - Subgroup 2.6.2: hData record format (HRF) +- Group 2.7: Questionnaires (QUE) + - Subgroup 2.7.1: General (GEN) + - Subgroup 2.7.2: CDA validation (CDA) + - Subgroup 2.7.3: hData record format (HRF) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP" + - : This is the test tool that will be used in the test case. + - HFS: Health & Fitness Services Interface + - : This is the device under test. + - SEN: HFS sender + - REC: HFS receiver + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose (TP). +- **TP label:** This is the title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP are included. + - Testable item: This contains testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 2.1.1 – Basic profile (BP) + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--| +| TP Id | TP/HFS/REC/WSI/BP/BI-000 | | | +| TP label | SOAP Envelope Namespace | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable items | BP-R1015; M | | +| Test purpose |

    Check that:

    An HFS receiver must generate a fault if they encounter an envelope whose document element is not soap:Envelope

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender has a SOAP message [b-SOAP 1.2] whose document element is not a soap:Envelope, ready to be sent | | | +| Test procedure |
    1. 1. The simulated HFS sender sends the SOAP message.
    2. 2. The HFS receiver generates a fault.
    | | | +| Pass/Fail criteria | Check that the HFS receiver generates a fault and does not discard the message. | | | +| Notes | | | | + +| | | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-000 | | | | +| TP label | SOAP Envelopes Structure | | | | +| Coverage | Spec | [OASIS/WS-I BP] | | | +| | Testable items | BP-R9980; M | BP-R9981; M | BP-R1014; M | +| | | BP-R1008; M | BP-R1009; M | BP-R1033; R | +| | | BP-R1017; M | BP-R1032; M | | +| Test purpose |

    Check that:

    An Envelope must conform to the structure specified in SOAP1.2 Section 5.1, “SOAP Envelope”

    [AND]

    an Envelope must have exactly zero or one child elements of the soap:Body element

    [AND]

    the children of the soap:body element in an Envelope must be namespace qualified

    [AND]

    an Envelope must not contain a Document Type Declaration (DTD) nor Processing Instructions

    [AND]

    an Envelope should not contain the namespace declaration
    xmlns:xml="http://www.w3.org/XML/1998/namespace"

    [AND]

    An HFS receiver must not mandate the use of the xsi:type attribute in envelopes except as required in order to indicate a derived type

    [AND]

    the soap:envelope, soap:header and soap:body elements in an Envelope must not have attributes in the namespace “http://schemas.xmlsoap.org/soap/envelope/”

    | | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | | +| Other PICS | | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender has a SOAP message ready to be sent. | +| Test procedure |
    1. The simulated HFS sender sends a SOAP message to the HFS receiver under test.
    2. The HFS receiver responds with another SOAP message. Check that the captured message has the following structure 
      <soap:Envelope 'namespace'>   <soap:Header>     ...   </soap:Header>   <soap:Body>     The children of the soap:envelope are here   </soap:Body> </soap:Envelope>

      where soap:Header is optional and it is recommended that the namespace is not "http://www.w3.org/XML/1998/namespace".

    | +| Pass/Fail criteria |

    Check that:

    • the message contains, in this order, an envelope, an optional header and a body.
    • each namespace that appears in the soap message is qualified.
    • the soap:envelope, soap:header and soap:body do not have attributes in the namespace "http://schemas.xmlsoap.org/soap/envelope/".
    • there is no DTD or processing instructions in the envelope.
    • an xsi:type is used only if a derived type is indicated (see [b-XML Schema Part 1], clause 2.6.1)
    • the namespace is "http://www.w3.org/2003/05/soap-envelope" to support SOAP 1.2.
    | +| Notes |

    BP-R2201 and BP-R2210 imply that there may be at most one child element of the soap:Body.

    The referenced errata, NE05, would not be allowed by Continua (as it is not compliant with the WS-I Basic Profile).

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-001 | | | +| TP label | SOAP encodingStyle Attribute | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable Items | BP-R1005; M | BP-R1006; M | +| Test purpose |

    Check that:

    An Envelope must not contain soap:encodingStyle attributes on any of the elements whose namespace name is "http://schemas.xmlsoap.org/soap/envelope/"

    [AND]

    An Envelope must not contain soap:encodingStyle attributes on any element that is a child of soap:body.

    [AND]

    an Envelope described in an rpc-literal binding must not contain soap:encodingStyle attribute on any element that is a grandchild of soap:Body

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | C_REC_WSI_003 | | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender has a SOAP message, with a correct soap:encodingStyle attribute in one of the elements, ready to be sent. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated HFS sender sends the SOAP message.
    2. 2. The HFS receiver responds with another SOAP message:
      1. a. If a soap:encodingStyle attribute is present in any element:
        • Namespace is not "http://schemas.xmlsoap.org/soap/envelope/"
        • The element is not a child of soap:Body
        • If PICS C_REC_WSI_003 is declared, the element is not a grandchild of soap:body
    | +| Pass/Fail criteria | In step 2, if the soap:encodingStyle attribute is present, it is as specified. | +| Notes | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|---------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-002 | | | | +| TP label | Use of SOAP in HTTP | | | | +| Coverage | Spec | [OASIS/WS-I BP] | | | +| | Testable items | BP-R1127; M | BP-R1140; M | CommonReq1; M | +| Test purpose | Check that:
    An HFS receiver must not rely on the value of the SOAPAction HTTP header to correctly process the message.
    [AND]
    A Message shall be sent using HTTP/1.1 | | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | | +| Other PICS | | | | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender has a SOAP message ready to be sent that contains a SOAPAction field not quoted in its HTTP header. | | | | +| Test procedure |
    1. 1. The simulated HFS sender sends a message using HTTP/1.1 with a SOAPAction HTTP Header field not quoted without using security.
    2. 2. The HFS receiver processes the message (it responds with the fault wsse:InvalidSecurity).
    | | | | +| Pass/Fail criteria | Check that in step 2 the message has been processed. | | | | +| Notes | | | | | + +| | | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-003 | | | | +| TP label | HTTP Status Codes | | | | +| Coverage | Spec | [OASIS/WS-I BP] | | | +| | Testable items | BP-R1124; M | BP-R1111; R | BP-R1112; R | +| | | BP-R1125; M | BP-R1113; R | BP-R1114; R | +| | | BP-R1115; R | | | +| Test purpose | Check that:
    An instance must use a 2xx HTTP status code on a response message that indicates the successful outcome of a HTTP request
    [AND]
    An instance should use a "200 OK" HTTP status code on a response message that contains an envelope that is not a fault
    [AND]
    An Instance should use either a "200 OK" or "202 Accepted" HTTP status code for a response message that does not contain a SOAP envelope but indicates the successful | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | outcome of a HTTP request
    [AND]
    An instance must use a 4xx HTTP status code for a response that indicates a problem with the format of a request
    [AND]
    An instance should use a "400 Bad Request" HTTP status code, if a HTTP request message is malformed
    [AND]
    An instance should use a "405 Method not Allowed" HTTP status code if a HTTP request message's method is not "POST".
    [AND]
    An instance should use a "415 Unsupported Media Type" HTTP status code if a HTTP request message's Content-Type header field-value is not permitted by its WSDL description | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send a HTTP request with an envelope permitted by the SUT | +| Test procedure |
    1. 1. The simulated HFS sender sends a HTTP request to the HFS receiver under test with an envelope permitted by the SUT.
    2. 2. The HFS receiver responds with "2xx" as status code, which is recommended to be: "200 OK" if the response contains an envelope that is not a fault; and "200 OK" or "202 Accepted" if the response does not contain a SOAP envelope but indicates the successful outcome of the HTTP Request.
    3. 3. The simulated HFS sender sends a HTTP request with a malformed message.
    4. 4. The HFS receiver responds with "4xx" as status code. It is recommended to be "400 Bad Request".
    5. 5. The simulated HFS sender sends a HTTP request with a method that is not "POST"
    6. 6. The HFS receiver responds with "4xx" as status code. It is recommended to be "405 Method not Allowed".
    7. 7. The simulated HFS sender sends a HTTP request with a Content-Type header field not permitted by the HFS receiver's WSDL description.
    8. 8. The HFS receiver responds with "4xx" as status code. It is recommended to be "415 Unsupported Media Type".
    | +| Pass/Fail criteria | Check that status codes are as specified. | +| Notes | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-004 | | | +| TP label | Messages using WSDL descriptions | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable items | BP-R2211; M | BP-R2212; M | +| | | BP-R2214; M | BP-R2213; M | +| Test purpose | Check that:
    An Envelope described with an rpc-literal binding must not have the xsi:nil attribute with a value of "1" or "true" on the part accessors
    [AND]
    an Envelope must contain exactly one part accessor element for each of the wsdl:parts in the same wsdl:message that are referred to by its soapbind:body element(s)
    [AND]
    in a doc-literal description where the value of the parts attribute of soapbind:body is an empty string, the corresponding envelope must have no element content in the soap:Body element | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [AND]
    in a rpc-literal description where the value of the parts attribute of soapbind:body is an empty string, the corresponding envelope must have no part accessor elements. | +| Applicability | C_REC_000 AND (C_REC_WSI_003 OR C_REC_WSI_004) AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send any SOAP message. | +| Test procedure |
    1. 1. The simulated HFS sender sends a SOAP message.
    2. 2. The HFS receiver under test responds with another SOAP message.
    3. 3. Look into the WSDL of the service and check in the captured message that:
      • If C_REC_WSI_003:
        1. a. If the value of the parts attribute of the soapbind:body element of the description is an empty string, there is no part accessor element.
        2. b. If the value of the parts attribute of the soapbind:body element of the description is not empty, check that the part accessor of the envelope is present and that the value of the xsi:nil attribute, if it is present, is not "1" or "true".
      • If C_REC_WSI_004:
        1. a. If the value of the parts attribute of the soapbind:body is an empty string, the envelope does not have element content in the soap:Body element.
    | +| Pass/Fail criteria | Check that the envelope is as specified in step 3. | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--| +| TP Id | TP/HFS/REC/WSI/BP/BV-005 | | | +| TP label | Port Types | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable items | BP-R2301; M | | +| Test purpose | Check that:
    The order of the elements in the soap:Body of an envelope must be the same as that of the wsdl:parts in the wsdl:message that describes it for each of the wsdl:part elements bound to the envelope's corresponding soapbind:body element | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS Sender is ready to send any SOAP message. | | | +| Test procedure |
    1. 1. The simulated HFS Sender sends a SOAP message to the HFS receiver under test.
    2. 2. The HFS receiver under test responds with a SOAP message.
    3. 3. Check the wsdl:parts elements in the wsdl:message of the WSDL of the HFS receiver under test.
    4. 4. Compare them with the soap:Body elements.
    | | | +| Pass/Fail criteria | In step 4, check that the order of the wsdl:parts are the same as the order of the elements in the soap:Body | | | +| Notes | | | | + +| | | | | +|-----------------|--------------------------|-----------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-006 | | | +| TP label | SOAP Binding | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable | BP-R2742; O | BP-R2743; O | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | items | | | +| Test purpose |

    Check that:

    An envelope may contain fault with a detail element that is not described by a soapbind:fault element in the corresponding WSDL description

    [AND]

    An envelope may contain the details of a header processing related fault in a SOAP header block that is not described by a soapbind:headerfault element in the corresponding WSDL description

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send a SOAP message that causes a fault in the HFS receiver response. | | | +| Test procedure |
    1. 1. The simulated HFS sender sends a SOAP message that causes a fault at the HFS receiver.
    2. 2. The HFS receiver under test responds with a fault message.
    3. 3. Check the detail element and the SOAP header block.
    | | | +| Pass/Fail criteria |

    Look into the WSDL description of the web service and check that:

    • • in step 2, it is optional that the detail element is not described by the soapbind:fault element of the description and that the header block is not described by a soapbind:headerfault element.
    | | | +| Notes |

    A simulated HFS sender can cause a fault at the HFS receiver in many different ways:

    • • If the HFS receiver uses security, the HFS sender sends a SOAP envelope without the security header.
    • • If the HFS sender sends something that is not a SOAP envelope.
    • • If the HFS receiver uses WSRM, the HFS sender sends something incorrect about the WSRM, such as an unknown sequence, or something like that.
    | | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-006_B | | | +| TP label | SOAP Binding 2 | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable items | BP-R2712; M | BP-R2729; M | +| | | BP-R2755; M | BP-R2737; M | +| | | BP-R2739; O | BP-R2752; O | +| Test purpose |

    Check that:

    A document-literal binding must be serialized as an envelope with a soap:Body whose child element is an instance of the global element declaration referenced by the corresponding wsdl:message part

    [AND]

    An envelope described with an rpc-literal binding that is a response must have a wrapper element whose name is the corresponding wsdl:operation name suffixed with the string "Response".

    [AND]

    An envelope described with an rpc-literal binding must place the part accessor elements for parameters and return value in no namespace

    [AND]

    The part accessor elements in a message described with an rpc-literal binding must have a local name of the same value as the name attribute of the corresponding wsdl:part element

    [AND]

    An envelope described with an rpc-literal binding must namespace qualify the descendants of part accessor elements for the parameters and the return value, as defined by the schema in

    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    which the part accessor types are defined

    [AND]

    An envelope must include all soapbind:headers specified on a wsdl:input or wsdl:output of a wsdl:operation of a wsdl:binding that describes it

    [AND]

    An envelope containing SOAP header blocks that are not described in the appropriate wsdl:binding may have the mustUnderstand attribute on such SOAP header blocks set to '1'.

    [AND]

    An Envelope may contain SOAP header blocks that are not described in the wsdl:binding that describes it

    [AND]

    An envelope may contain more than one instance of each SOAP header block for each soapbind:header element in the appropriate child of soapbind:binding in the corresponding description

    | +| Applicability | C_REC_000 AND (C_REC_WSI_003 OR C_REC_WSI_004) AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send any SOAP message. | +| Test procedure |
    1. The simulated HFS sender sends a SOAP message to the HFS receiver under test.
    2. The HFS receiver responds with a SOAP message.
    3. Check the captured message.
    | +| Pass/Fail criteria |

    Look into the WSDL description of the web service and check:

    • In step 2,
      • If the SOAP header block is not described in wsdl:binding, it can be present and it is optional that the mustUnderstand attribute is present and equal to "1" and that the envelope has more than one instance for each header block.
      • All soapbind:headers specified in wsdl:input or wsdl:output of a wsdl:operation of a wsdl:binding are included in the envelope.
      • If C_REC_WSI_003, the part accessor of the envelope has a local name equal to the name of the attribute of the wsdl:part element, it is placed in no namespace and its descendants have a namespace qualified by the schema in which the part accessor types are defined. In addition the envelope has a wrapper element whose name is the corresponding wsdl:operation name suffixed with the string "Response".
      • If C_REC_WSI_004, the child element of the soap:Body is an instance of the global element declaration referenced by the corresponding wsdl:message part.
    | +| Notes | | + +| | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-007 | | | +| TP label | Use of HTTPS | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable items | BP-R5000; O | BP-R5001; M | +| Test purpose |

    Check that:

    An Instance may require the use of HTTPS

    [AND]

    if an instance requires the use of HTTPS, the location attribute of the soapbind:address element in its wsdl:port description must be a URI whose scheme is "https"; otherwise it must be a URI whose scheme is "http"

    [AND]

    an instance may require the use of HTTPS with mutual authentication

    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send any HTTP request. | +| Test procedure |
    1. 1. The simulated HFS sender sends a HTTP request.
    2. 2. Wait until the HFS receiver under test responds using a HTTP instance.
    3. 3. Check the value of the location attribute of the soapbind:address element in its wsdl:port description.
    | +| Pass/Fail criteria | In step 2, if this value is "https", the instance requires HTTPS, otherwise, if it is "http", the instance requires HTTP. | +| Notes | Applicability is ALL because although TI says that HTTPS is optional, the CDG states that HTTPS with TLS must be used. | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-008 | | | +| TP label | SOAP Processing Model | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable items | BP-R1025; M | BP-R1028; R | +| | | BP-R1030; R | BP-R1027; M | +| Test purpose |

    Check that:

    An HFS receiver must handle envelopes in such a way that it appears that all checking of mandatory header blocks is performed before any actual processing
    [AND]

    When a fault is generated by an HFS receiver, further processing should not be performed on the SOAP envelope aside from that which is necessary to rollback, or compensate for, any effects of processing the envelope prior to the generation of the fault.
    [AND]

    Where the normal outcome of processing a SOAP envelope would have resulted in the transmission of a SOAP response, but rather a fault is generated instead, an HFS receiver must transmit a fault in place of the response.
    [AND]

    An HFS receiver that generates a fault should notify the end user that a fault has been generated when practical, by whatever means is deemed appropriate to the circumstance.
    [AND]

    An HFS receiver must generate a "soap:MustUnderstand" fault when an envelope contains a mandatory header block (i.e., one that has a soap:mustUnderstand attribute with the value "1") targeted at the HFS receiver (via soap:actor) that the HFS receiver does not understand.

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send a SOAP message with a header block with soap:MustUnderstand='1' 'true' that the HFS receiver does not understand. | | | +| Test procedure |
    1. 1. The simulated HFS sender sends the SOAP message.
    2. 2. The HFS receiver under test generates a soap:MustUnderstand fault.
    3. 3. The HFS receiver responds with that fault.
    4. 4. Check that, when HFS receiver generates the fault, the simulated HFS sender is notified of the fault by the HFS receiver.
    | | | +| Pass/Fail criteria | In step 3, the HFS receiver responds with a soap:MustUnderstand fault and no other messages. | | | +| Notes | If the HFS receiver does not send another message besides a soap:MustUnderstand fault, then it is considered that further processing is not performed prior to the generation of the fault. | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|--| +| TP Id | TP/HFS/REC/WSI/BP/BV-009 | | | | +| TP label | SOAP Faults | | | | +| Coverage | Spec | [OASIS/WS-I BP] | | | +| | Testable items | BP-R1107; M | BP-R1002; M | | +| Test purpose |

    Check that:

    An HFS receiver must interpret a SOAP message as a Fault when the soap:Body of the message has a single soap:Fault child

    [AND]

    An HFS receiver must accept faults that have any number of elements, including zero, appearing as children of the detail element. Such children can be qualified or unqualified

    | | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | | +| Other PICS | | | | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send a SOAP message with a soap:Fault in the soap:Body. | | | | +| Test procedure |
    1. The simulated HFS sender sends an envelope with a single soap:fault child in the soap:Body.
    2. Wait for any response from the HFS receiver under test.
    3. The simulated HFS sender sends a soap:fault message with zero elements as child of the detail element.
    4. Wait for any response of HFS receiver.
    5. The simulated HFS sender sends a soap:fault with zero attributes in the detail element.
    6. Wait for any response from the HFS receiver.
    | | | | +| Pass/Fail criteria | In steps 2, 4 and 6, the HFS receiver must not report any error because all the messages are accepted. | | | | +| Notes | | | | | + +| | | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-010 | | | | +| TP label | WSDL Description | | | | +| Coverage | Spec | [OASIS/WS-I BP] | | | +| | Testable items | BP-R1034; R | BP-R2028; M | BP-R2029; M | +| | | BP-R4004; M | BP-R4005; R | BP-R4002; R | +| | | BP-R4003; M | BP-R2030; O | BP-R2026; R | +| | | BP-R2101; M | BP-R2102; M | BP-R2105; M | +| | | BP-R2110; M | BP-R2111; M | BP-R2112; R | +| | | BP-R2114; R | BP-R2302; O | BP-R2303; M | +| | | BP-R2304; M | BP-R2305; M | BP-R2709; O | +| | | BP-R2711; R | | | +| Test purpose |

    Check that:

    A Description should not contain the namespace declaration
    xmlns:xml="http://www.w3.org/XML/1998/namespace"

    [AND]

    A Description using the WSDL namespace must be valid according to the XML Schema found at "http://ws-i.org/profiles/basic/1.1/wsdl11.xsd".

    [AND]

    A Description using the WSDL SOAP binding namespace must be valid according to the XML

    | | | | + +Schema found at "http://ws-i.org/profiles/basic/1.1/wsdlsoap2004-08-24.xsd" + +[AND] + +A Description must use version 1.0 of the eXtensible Markup Language W3C Recommendation + +[AND] + +A Description may include the Unicode Byte Order Mark (BOM) + +[AND] + +A Description must use either UTF-8 or UTF-16 encoding + +[AND] + +In a Description the wsdl:documentation element may be present as the first child element of wsdl:import, wsdl:part and wsdl:definitions in addition to the elements cited in the WSDL1.1 specification + +[AND] + +A Description should not include extension elements with a wsdl:required attribute value of "true" on any WSDL construct (wsdl:binding, wsdl:portType, wsdl:message, wsdl:types or wsdl:import) that claims conformance to the Profile + +[AND] + +A Description must not use QName references to WSDL components in namespaces that have been neither imported, nor defined in the referring WSDL document + +[AND] + +A QName reference to a Schema component in a Description must use the namespace defined in the targetNamespace attribute on the xsd:schema element, or to a namespace defined in the namespace attribute on an xsd:import element within the xsd:schema element + +[AND] + +All xsd:schema elements contained in a wsdl:types element of a Description must have a targetNamespace attribute with a valid and non-null value, unless the xsd:schema element has xsd:import and/or xsd:annotation as its only child element(s). + +[AND] + +In a Description, declarations must not extend or restrict the soapenc:Array type + +[AND] + +In a Description, declarations must not use wsdl:arrayType attribute in the type declaration + +[AND] + +In a Description, elements should not be named using the convention ArrayOfXXX + +[AND] + +The target namespace for WSDL definitions and the target namespace for schema definitions in a Description may be the same + +[AND] + +A Description may use the parameterOrder attribute of an wsdl:operation element to indicate the return value and method signatures as a hint to code generators + +[AND] + +A Description must not use Solicit-Response and Notification type operations in a wsdl:portType definition + +[AND] + +A wsdl:portType in a Description must have operations with distinct values for their name attributes + +[AND] + +A wsdl:operation element child of a wsdl:portType element in a Description must be constructed so that the parameterOrder attribute, if present, omits at most 1 wsdl:part from the output message + +[AND] + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    A wsdl:portType in a Description may have zero or more wsdl:bindings that refer to it, defined in the same or other WSDL documents

    [AND]

    A Description should not have more than one wsdl:port with the same value for the location attribute of the soapbind:address element

    | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver has published its WSDL description. | +| Test procedure |
    1. 1. Look up the WSDL description using the corresponding URL given by the HFS receiver under test. Check that:
      1. a. xmlns:xml≠ "http://www.w3.org/XML/1998/namespace"
      2. b. XML version = "1.0"
      3. c. UTF-8 or UTF-16 encoding are used and the unicode byte order mark (BOM) is optional.
      4. d. if wsdl:documentation is present, check that it is the first child element of wsdl:import, wsdl:part or wsdl:definitions.
      5. e. the targetNamespace attribute of an xsd:schema contained in wsdl:types element, has a valid non-null value, unless the xsd:schema has xsd:import and/or xsd:annotation as its only child element(s) 
        <types>   <xsd:schema targetNamespace="http://example.org/foo/"     ... >
      6. f. the wsdl:portType definition does not use Solicit-Response or Notification Type operations and has operations with distinct values for their name attributes: 
        <portType name="BarPortType">   <operation name="BarOperation">     <input message="bar:BarMsg"/>   </operation> </portType>
      7. g. if present, the parameterOrder attribute of the wsdl:operation (that is a child of wsdl:portType) omits at most one wsdl:part from the output message.
      8. h. the wsdl:ArrayType is not present on type declaration.
      9. i. the soapenc:ArrayType is not extended or restricted.
      10. j. the description does not contain any extension elements with a wsdl:required attribute value of "true" on any WSDL construct (wsdl:binding, wsdl:portType, wsdl:message, wsdl:types or wsdl:import) as is recommended.
      11. k. The namespace of a QName reference to a schema component is defined in the targetNamespace attribute on the xsd:schema element or is the namespace of the xsd:import element.
      12. l. aQName reference to WSDL components in namespaces that have been neither imported nor defined on the referring WSDL Document, is not used.
      13. m. wsdl:bindings are optional
      14. n. that more than one wsdl:port with the same value for the location attribute of the soapbind:address element are not used as is recommended.
    | +| Pass/Fail criteria |

    Check that:

    • • in step 1, the HFS sender can access the WSDL description.
    • • all elements and attributes are as specified.
    • • the description using the wsdl namespace is valid according to the XML schema found at http://ws-i.org/profiles/basic/1.1/wsdl11.xsd.
    • • the description using the WSDL SOAP Bind namespace is valid according to the XML
    | + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| | schema found at http://ws-i.org/profiles/basic/1.1/wsdlsoap-2004-08-24.xsd . | +| Notes | BP-R4005 is the same that BP-R1034 | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-011 | | | +| TP label | WSDL Description: wsdl:binding | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable items | BP-R2209; R | BP-R2202; O | +| | | BP-R2205; M | BP-R2701; M | +| | | BP-R2705; M | BP-R2706; M | +| | | BP-R2716; M | BP-R2717; M | +| | | BP-R2718; M | BP-R2719; O | +| | | BP-R2741; R | BP-R2720; M | +| | | BP-R2721; M | BP-R2754; M | +| | | BP-R2723; M | BP-R2707; M | +| | | | BP-R2710; M | +| | | | BP-R2726; M | +| | | | BP-R2740; R | +| | | | BP-R2749; M | +| | | | BP-R2722; O | +| | | | BP-R2751; M | +| Test purpose |

    Check that:

    A wsdl:binding in a Description should bind every wsdl:part of a wsdl:message in the wsdl:portType to which it refers with a binding extension element.

    [AND]

    A wsdl:binding in a Description may contain soapbind:body element(s) that specify that zero parts form the soap:Body

    [AND]

    A binding in a Description may contain soapbind:header element(s) that refer to wsdl:parts in the same wsdl:message that are referred to by its soapbind:body element(s).

    [AND]

    A wsdl:binding in a Description must refer, in each of its soapbind:header, soapbind:headerfault and soapbind:fault elements, only to wsdl:part element(s) that have been defined using the element attribute

    [AND]

    The wsdl:binding element in a Description must be constructed so that its soapbind:binding child element specifies the transport attribute.

    [AND]

    A wsdl:binding element in a Description must specify the HTTP transport protocol with SOAP binding. Specifically, the transport attribute of its soapbind:binding child must have the value "http://schemas.xmlsoap.org/soap/http".

    [AND]

    A wsdl:binding in a Description must either be a rpc-literal binding or a document-literal binding.

    [AND]

    The operations in a wsdl:binding in a Description must result in operation signatures that are different from one another

    [AND]

    A wsdl:binding in a Description must use the value of "literal" for the use attribute in all soapbind:body, soapbind:fault, soapbind:header and soapbind:headerfault elements

    [AND]

    A document-literal binding in a Description must not have the namespace attribute specified on contained soapbind:body, soapbind:header, soapbind:headerfault and soapbind:fault elements

    [AND]

    An rpc-literal binding in a Description must have the namespace attribute specified, the value

    | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    of which must be an absolute URI, on contained soapbind:body elements

    [AND]

    An rpc-literal binding in a Description must not have the namespace attribute specified on contained soapbind:header, soapbind:headerfault and soapbind:fault elements

    [AND]

    A wsdl:binding in a Description must have the same set of wsdl:operations as the wsdl:portType to which it refers

    [AND]

    A wsdl:binding in a Description may contain no soapbind:headerfault elements if there are no known header faults

    [AND]

    A wsdl:binding in a Description should contain a soapbind:fault describing each known fault

    [AND]

    A wsdl:binding in a Description should contain a soapbind:headerfault describing each known header fault

    [AND]

    A wsdl:binding in a Description must use the part attribute with a schema type of "NMTOKEN" on all contained soapbind:header and soapbind:headerfault elements

    [AND]

    A wsdl:binding in a Description must not use the parts attribute on contained soapbind:header and soapbind:headerfault elements

    [AND]

    A wsdl:binding in a Description must have the name attribute specified on all contained soapbind:fault elements

    [AND]

    In a Description, the value of the name attribute on a soapbind:fault element must match the value of the name attribute on its parent wsdl:fault element

    [AND]

    A wsdl:binding in a Description may specify the use attribute on contained soapbind:fault elements

    [AND]

    If in a wsdl:binding in a Description the use attribute on a contained soapbind:fault element is present, its value must be "literal".

    [AND]

    A wsdl:binding in a Description that contains one or more soapbind:body, soapbind:fault, soapbind:header or soapbind:headerfault elements that do not specify the use attribute must be interpreted as though the value "literal" had been specified in each case

    [AND]

    The order of soapbind:header elements in soapbind:binding sections of a Description must be considered independent of the order of SOAP header blocks in the envelope

    | +| Applicability | C_REC_000 AND (C_REC_WSI_003 OR C_REC_WSI_004) AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver has published its WSDL description. | +| Test procedure |
    1. 1. Look up the WSDL description using the corresponding URL given by the HFS receiver under test. If wsdl:binding is present, check that:
      1. a. the Soapbind:binding child element specifies the transport attribute and transport="http://schemas.xmlsoap.org/soap/http".
      2. b. the soapbind:header and soapbind:body elements are optional.
      3. c. the wsdl:binding refers in soapbind:headerfault, soapbind:header, soapbind:fault elements only to wsdl:parts that has been defined using the element attribute.
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. the operations resulted in operation signatures that are different from one another.

    e. the "use" attribute in soapbind:header, soapbind:body, soapbind:headerfault and soapbind:fault, if they are present, is "literal".

    f. the wsdl:binding has the same wsdl:operations as wsdl:portType.

    g. the part attribute of soapbind:header and soapbind:headerfault elements, if they are present, have the schema type of "NMTOKEN".

    h. the soapbind:headerfault elements are optional if there are no known header faults.

    i. all soapbind:fault elements have the name attribute specified and its value matches the value of the name attribute on its parent wsdl:fault element. The "use" attribute is optional.

    j. the order of the soapbind:header element, if it is present, is independent of the order of SOAP header blocks.

    k. if C_REC_WSI_003, the namespace attribute is specified only on a contained soapbind:body and its value is an absolute URI.

    if C_REC_WSI_004, the namespace attribute is not specified.

    | +| Pass/Fail criteria | The HFS sender can access the WSDL description and if wsdl:binding is present, elements and attributes are as specified above. | +| Notes |

    The profile defines the "operation signature" to be the fully qualified name of the child element of SOAP body of the SOAP input message described by an operation in a WSDL binding.

    In the case of rpc-literal binding, the operation name is used as a wrapper for the part accessors. In the document-literal case, since a wrapper with the operation name is not present, the message signatures must be correctly designed.

    | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-012 | | | +| TP label | WSDL Description. Imported Descriptions | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable items | BP-R2001; M | BP-R2803; M | +| | | BP-R2003; M | BP-R2004; M | +| | | BP-R2010; M | BP-R2011; M | +| | | BP-R2022; M | BP-R2023; M | +| Test purpose |

    Check that:

    A Description must only use the WSDL "import" statement to import another WSDL description

    [AND]

    In a Description, the namespace attribute of the wsdl:import must not be a relative URI

    [AND]

    To import XML Schema Definitions, a Description must use the XML Schema "import" statement

    [AND]

    A Description must use the XML Schema "import" statement only within the xsd:schema element of the types section

    [AND]

    In a Description the schemaLocation attribute of an xsd:import element must not resolve to any document whose root element is not "schema" from the namespace "http://www.w3.org/2001/XMLSchema"

    [AND]

    An XML Schema directly or indirectly imported by a Description may include the Unicode Byte Order Mark (BOM).

    [AND]

    An XML Schema directly or indirectly imported by a Description must use either UTF-8 or

    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    UTF-16 encoding

    [AND]

    An XML Schema directly or indirectly imported by a Description must use version 1.0 of the eXtensible Markup Language W3C Recommendation

    [AND]

    A Description must specify a non-empty location attribute on the wsdl:import element

    [AND]

    When they appear in a Description, wsdl:import elements must precede all other elements from the WSDL namespace except wsdl:documentation

    [AND]

    When they appear in a Description, wsdl:types elements must precede all other elements from the WSDL namespace except wsdl:documentation and wsdl:import

    [AND]

    The targetNamespace attribute on the wsdl:definitions element of a description that is being imported must have same the value as the namespace attribute on the wsdl:import element in the importing Description

    | +| Applicability | C_REC_000 AND C_REC_WSI_002 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver has published its WSDL description. | +| Test procedure |
    1. 1. Look up the WSDL description using the corresponding URL given by the HFS receiver under test. If the wsdl:import element is present, check that:
      1. a. the wsdl:import is only used to import another wsdl description.
      2. b. the namespace of the wsdl:import is not a relative URI.
      3. c. the XML schema "import" statement is used to import the XML schema definitions within the xsd:schema element.
      4. d. an imported XML schema definitions is version 1.0.
      5. e. the schemaLocation attribute of the xsd:import element is resolved to a document whose root element is a schema from the namespace "http://www.w3.org/2001/XMLSchema"
      6. f. UTF-8 or UTF-16 encoding is used and it is optional that it includes the unicode byte order mark (BOM).
      7. g. the location attribute of the wsdl:import element is not empty.
      8. h. the wsdl:import precedes all other elements from the WSDL, except wsdl:documentation.
      9. i. wsdl:types precedes all other elements from the WSDL, except wsdl:documentation and wsdl:import.
      10. j. the targetNamespace attribute of the description being imported is the same as the namespace attribute on the wsdl:import element in the importing description.
    | +| Pass/Fail criteria | The HFS sender can access the WSDL description and elements and attributes of wsdl:import that are specified above. | +| Notes | | + +| | | | | +|---------------------|--------------------------------------|-----------------|-------------| +| TP Id | TP/HFS/REC/WSI/BP/BV-013 | | | +| TP label | WSDL Description: wsdl:parts element | | | +| Coverage | Spec | [OASIS/WS-I BP] | | +| | Testable items | BP-R2201; C | BP-R2210; C | +| | | BP-R2207; O | BP-R2204; C | +| | | BP-R2306; M | BP-R2203; C | +| | | | BP-R2206; M | +| Test purpose | Check that: | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    A document-literal binding in a Description must, in each of its soapbind:body element(s), have at most one part listed in the parts attribute, if the parts attribute is specified

    [AND]

    If a document-literal binding in a Description does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message must define zero or one wsdl:parts

    [AND]

    If a rpc-literal binding in a Description must refer, in its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the type attribute

    [AND]

    A wsdl:message in a Description may contain wsdl:parts that use the elements attribute provided those wsdl:parts are not referred to by a soapbind:body in an rpc-literal binding

    [AND]

    A document-literal binding in a Description must refer, in each of its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the element attribute

    [AND]

    A wsdl:message in a Description containing a wsdl:part that uses the element attribute must refer, in that attribute, to a global element declaration

    [AND]

    A wsdl:message in a Description must not specify both type and element attributes on the same wsdl:part

    | +| Applicability | C_REC_000 AND (C_REC_WSI_003 OR C_REC_WSI_004) AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver has published its WSDL description. | +| Test procedure |

    1. Look up the WSDL description using the corresponding URL given by the HFS receiver under test.

    An example of a part element in a description is shown below:

    <message name="GetTradePriceInput">   <part name="body" element="tns:SubscribeToQuotes"/> </message>
    | +| Pass/Fail criteria |

    Check that:

    • • if C_REC_WSI_004 is supported and the HFS receiver does not specify the parts attribute on a soapbind:body element, the wsdl:message defines zero or one wsdl:parts.
      • ○ If the HFS receiver does specify the doc-literal binding, it has at most one part listed in the parts attribute and it is defined using the element attribute, that refers to a global element declaration.
    • • if C_REC_WSI_003 is supported, the HFS receiver refers in its soapbind:body element(s) only to a wsdl:part element(s) defined using the type attribute. wsdl:parts that uses the elements attribute and this provided those wsdl:parts are not referred to by a soapbind:body are optional.
    • • in either case above, the wsdl:message does not specify both type and element attributes on the same wsdl:part.
    | +| Notes | | + +## A.3 Subgroup 2.1.2 – Basic security profile (BSP) + +| | | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------|--|--| +| TP Id | TP/HFS/REC/WSI/BSP/BV-000 | | | | | +| TP Label | TLS and SSL | | | | | +| Coverage | Spec | [OASIS/WS-I BSP] | | | | +| | Testable items | BSP-322; R | BSP-323; R | | | +| | Spec | [ITU-T H.812] | | | | +| | Testable items | SecGuidelines2; M | | | | +| Test purpose |

    Check that:

    As the AES encryption algorithm is intended to supersede the 3DES algorithm, it is recommended that TLS-capable implementations implement TLS_RSA_WITH_AES_128_CBC_SHA or the FIPS equivalent

    [AND]

    The ciphersuites defined in the TLS specifications that use anonymous Diffie-Hellman (i.e. those that have DH_anon in their symbolic name) are vulnerable to man-in-the-middle attacks. It is also recommended that ciphersuites that include MD5 (i.e. those that have MD5 in their symbolic name) be avoided, due to known security weaknesses of the MD5 algorithm. It is recommended that such ciphersuites be avoided.

    The Profile recommends against the use of the following ciphersuites due to their lack of confidentiality services:

    • - TLS_RSA_WITH_NULL_SHA
    • - TLS_RSA_WITH_NULL_MD5

    It is also recommended that ciphersuites that use 40 or 56 bit keys be avoided, due to their relative ease of compromise through brute-force attack.

    [AND]

    Continua HFS client and service components shall support AES cipher as specified in RFC 3268.

    | | | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | | | +| Other PICS | C_REC_WSI_005, C_REC_WSI_029, C_REC_WSI_030, C_REC_WSI_031, C_REC_WSI_032 | | | | | +| Initial condition | The simulated HFS sender and the HFS receiver under test have never been partners in a message exchange. | | | | | +| Test procedure |
    1. 1. If instance is FIPS compliant (C_REC_WSI_005=true):
      1. a. Load the simulated HFS sender supporting TLS_RSA_FIPS_WITH_AES_128_CBC_SHA
      2. b. Make the HFS receiver under test establish a TLS connection.
      3. c. Check in TLS handshake that the HFS receiver under test SHOULD not support:
        • Any cipher-suites with an DH_anon in their symbolic name
        • Any cipher-suites with a MD5 in their symbolic name
        • Any of the following cipher-suites:
          • • TLS_RSA_WITH_NULL_SHA
          • • TLS_RSA_WITH_NULL_MD5
        • Any cipher-suites that use 40 or 56 bit keys
      4. d. Check that the HFS receiver under test supports TLS_RSA_FIPS_WITH_AES_128_CBC_SHA
      5. e. Close the connection.
    2. 2. If an instance is not FIPS compliant (C_REC_WSI_005=false):
    | | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. a. Load the simulated HFS sender supporting TLS_RSA_WITH_AES_128_CBC_SHA.
    2. b. Make the HFS receiver under test establish a TLS connection.
    3. c. Check in the TLS handshake that the HFS receiver under test SHOULD not support:
      • any cipher-suites with a DH_anon in their symbolic name.
      • any cipher-suites with a MD5 in their symbolic name.
      • any of the following cipher-suites:
        • • TLS_RSA_WITH_NULL_SHA
        • • TLS_RSA_WITH_NULL_MD5
      • any cipher-suites that use 40 or 56 bit keys.
    4. d. Check that the HFS receiver under test MUST support TLS_RSA_WITH_AES_128_CBC_SHA.
    5. e. Close the connection.
    | +| Pass/Fail criteria |
    • • If C_REC_WSI_005, the HFS receiver under test must support TLS_RSA_FIPS_WITH_AES_128_CBC_SHA.
    • • If not C_REC_WSI_005, the HFS receiver under test must support TLS_RSA_WITH_AES_128_CBC_SHA.
    • • The cipher-suites supported must match with these PICS: C_REC_WSI_029, C_REC_WSI_030, C_REC_WSI_031, C_REC_WSI_032.
    | +| Notes | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------| +| TP Id | TP/HFS/REC/WSI/BSP/BV-003 | | | +| TP label | Basic Profile Clarification | | | +| Coverage | Spec | [OASIS/WS-I BSP] | | +| | Testable items | BSP-R5814; O | BSP-R5801; M | +| | | BSP-R5805; M | BSP-R5807; M | +| | | BSP-R5811; M | BSP-R5813; M | +| Test purpose |

    Check that:

    Where the normal outcome of processing a SECURE_ENVELOPE would have resulted in the transmission of a SOAP Response, but rather a fault is generated instead, an HFS receiver may transmit a fault or silently discard the message

    [AND]

    bp11:R2301 must be true after any SOAP Message Security has been reversed for the Envelope

    [AND]

    bp11:R2710 must be true after SOAP Message Security processing has been reversed for the Envelope

    [AND]

    bp11:R2712 must be true after any SOAP Message Security has been reversed for the Envelope

    [AND]

    For bp11:R2724 "Inconsistent" must be taken to mean "Inconsistent after SOAP Message security has been reversed", for the Envelope

    [AND]

    With respect to bp11:R2725 the Instance must check for consistency of the Envelope per BP 1.1 after reversing SOAP Message Security

    [AND]

    With respect to bp11:R2729 the verification of the wrapper element name of the Envelope must be performed after reversing SOAP Message Security.

    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [AND]
    With respect to bp11:R2738 verification of an Envelope must occur after SOAP Message Security has been reversed | +| Applicability | C_REC_000 AND C_REC_WSI_006 AND C_REC_GEN_003 | +| Other PICS | C_REC_WSI_003, C_REC_WSI_004 | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send a SOAP message using the same security policy as the HFS receiver. | +| Test procedure |
    1. 1. The simulated HFS sender sends a message using SOAP message security.
    2. 2. The HFS receiver under test responds using SOAP message security.
    3. 3. The simulated HFS sender takes the WSDL description and after reversing the SOAP message security of the response, check that:
      1. a. the order of the elements in the soap:body is the same as that of the wsdl:parts in the wsdl:message.
      2. b. operations in wsdl:binding result in operations signatures that are different from one another.
      3. c. the envelope includes all the soapbind:headers specified on a wsdl:input or wsdl:output of a wsdl:operation of a wsdl:binding.
      4. d. if C_REC_WSI_003, the envelope has a wrapper element whose name is the corresponding wsdl:operation name suffixed with the string "Response".
      5. e. if C_REC_WSI_004, the binding is serialized as an envelope with a soap:Body whose child element is an instance of the global element declaration referenced by the corresponding wsdl:message part.
    4. 4. The simulated HFS sender sends an envelope with an incorrect namespace.
    5. 5. The HFS receiver generates a soap:Fault with a faultcode= "VersionMismatch".
    6. 6. The simulated HFS sender sends an envelope with an incorrect namespace and a soap:MustUnderstand attribute value of "1".
    7. 7. The HFS receiver generates a soap:Fault with a faultcode= "VersionMismatch".
    8. 8. The simulated HFS sender sends an envelope with a correct namespace and soap:MustUnderstand attribute value of "1" using security that the HFS receiver is not going to understand.
    9. 9. The HFS receiver generates a soap:Fault with a faultcode="MustUnderstand".
    10. 10. The simulated HFS sender sends an envelope with a correct namespace, soap:MustUnderstand attribute value of "0" and that is inconsistent with its WSDL description.
    11. 11. The HFS receiver generates a soap:Fault with a faultcode="Sender".
    | +| Pass/Fail criteria | All steps are as specified. When the HFS receiver generates a soap:Fault, it can transmit it or discard the message. | +| Notes |

    "Reverse" means to remove impacts of applying SOAP message security that has been applied to an envelope created according to BP 1.1

    • • bp11:R1029 states "Where the normal outcome of processing a SOAP Envelope would have resulted in the transmission of a SOAP response, but rather a fault is generated instead, an HFS receiver MUST transmit a fault place of the response"
    • • bp11:R2301 states "The order of the elements in the soap:body of an ENVELOPE MUST be the same as that of the wsdl:parts in the wsdl:message that describes it."
    • • bp11:R2710 states "The operations in a wsdl:binding in a DESCRIPTION MUST result in operation signatures that are different from one another."
    • • bp11:R2712 states "A document-literal binding MUST be serialized as an ENVELOPE with a soap:Body whose child element is an instance of the global element declaration referenced by the corresponding wsdl:message part."
    • • bp11:R2724 states "If an INSTANCE receives an envelope that is inconsistent with its WSDL description, it SHOULD generate a soap:Fault with a faultcode of 'Client', unless a 'MustUnderstand' or 'VersionMismatch' fault is generated."
    • • bp11:R2725 states "If an INSTANCE receives an envelope that is inconsistent with its
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    WSDL description, it MUST check for "VersionMismatch", "MustUnderstand" and "Client" fault conditions in that order."

    • bp11:R2729 states "An ENVELOPE described with an rpc-literal binding that is a response MUST have a wrapper element whose name is the corresponding wsdl:operation name suffixed with the string 'Response'."
    • bp11:R2738 states "An ENVELOPE MUST include all soapbind:headers specified on a wsdl:input or wsdl:output of a wsdl:operation of a wsdl:binding that describes it."
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------| +| TP Id | TP/HFS/REC/WSI/BSP/BV-004 | | | +| TP label | Timestamp element | | | +| Coverage | Spec | [OASIS/WS-I BSP] | | +| | Testable items | BSP-R3227; M | BSP-R3203; M | +| | | BSP-R3221; M | BSP-R3222; M | +| | | BSP-R3229; R | BSP-R3213; M | +| | | BSP-R3225; M | BSP-R3226; M | +| | | BSP-R3223; M | BSP-R3217; M | +| Test purpose |

    Check that:

    A SECURITY_HEADER must not contain more than one Timestamp

    [AND]

    A Timestamp must contain exactly one Created

    [AND]

    Any Timestamp must not contain more than one Expires

    [AND]

    Any Timestamp containing an Expires must contain a Created that precedes its sibling Expires

    [AND]

    Any Timestamp must not contain anything other than Created or Expires elements

    [AND]

    Any Created should not contain a seconds value with more than three digits to the right of the decimal (milliseconds).

    [AND]

    Any Expires should not contain a seconds value with more than three digits to the right of the decimal (milliseconds).

    [AND]

    Any Created containing second values must specify seconds values less than 60

    [AND]

    Any Expires containing second values must specify seconds values less than 60

    [AND]

    Any Created must not include a ValueType attribute

    [AND]

    Any Expires must not include a ValueType attribute

    [AND]

    Any Created must contain time values in UTC format as specified by the XML Schema type (dateTime).

    [AND]

    Any Expired must contain time values in UTC format as specified by the XML Schema type (dateTime).

    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_REC_000 AND C_REC_WSI_007 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send a SOAP message with a Timestamp | +| Test procedure |
    1. 1. The simulated HFS sender sends the message using a Timestamp element.
    2. 2. The HFS receiver under test responds to the message.
    3. 3. Check in the response message that:
      1. a. the Timestamp is present and there is only one. For example: 
        <wsu:Timestamp wsu:Id="timestamp">   <wsu:Created>2001-09-13T08:42:00Z</wsu:Created>   <wsu:Expires>2001-10-13T09:00:00Z</wsu:Expires> </wsu:Timestamp>
      2. b. only one created element is present and inside it:
        • ValueType attribute is not included
        • UTC format is used in time values
        • seconds values are less than 60 and its decimal values are recommended to be less than 3 digits to the right
      3. c. if an Expires element is present, there is only one and it comes after the created element and:
        • ValueType attribute is not included
        • UTC format is used in time values
        • the seconds values are less than 60 and its decimal values are recommended to be less than 3 digits to the right
    | +| Pass/Fail criteria | The elements in step 3 are as specified. | +| Notes | | + +| | | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------|--------------| +| TP Id | TP/HFS/REC/WSI/BSP/BV-005 | | | | +| TP label | Security Token References - Direct References | | | | +| Coverage | Spec | [OASIS/WS-I BSP] | | | +| | Testable items | BSP-R3061; M | BSP-R3057; M | BSP-R3064; M | +| | | BSP-R3059; M | BSP-R3058; M | BSP-R3062; M | +| | | BSP-R3027; M | BSP-R3211; M | | +| Test purpose | Check that:
    A SECURITY_TOKEN_REFERENCE must provide exactly one token reference
    [AND]
    Any STR_REFERENCE must not reference a SECURITY_TOKEN_REFERENCE
    [AND]
    Any STR_REFERENCE must not reference an STR_EMBEDDED
    [AND]
    Any STR_REFERENCE must specify a ValueType attribute
    [AND]
    Any STR_REFERENCE ValueType attribute must contain a value for the referenced SECURITY_TOKEN specified by the corresponding security token profile.
    [AND]
    Any STR_REFERENCE must specify a URI attribute | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [AND]
    Any SECURITY_TOKEN_REFERENCE must not contain an STR_KEY_NAME
    [AND]
    Any SECURITY_TOKEN_REFERENCE must not reference a ds:KeyInfo element | +| Applicability | C_REC_000 AND C_REC_WSI_019 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send a SOAP message with the same security policy as the HFS receiver. | +| Test procedure |
    1. 1. The simulated HFS sender sends a message using a security token reference (STR) with an STR reference.
    2. 2. The HFS receiver under test responds with a message including a SecurityTokenReference with a direct reference: 
      <wsse:SecurityTokenReference wsu:Id="...">   <wsse:Reference URI="..." ValueType="..."> </wsse:SecurityTokenReference>
    3. 3. Check in the captured message that:
      1. a. there is only one STR_Reference to the SECURITY_TOKEN_REFERENCE
      2. b. the STR_Reference does not reference another STR or an STR_Embedded.
      3. c. a URI Attribute is present.
      4. d. a ValueType attribute is present and it contains a value for the referenced security token specified by the corresponding security token profile (e.g., an X.509 certificate token).
      5. e. the STR does not contain an STR_KEY_NAME and does not reference a ds:KeyInfo element.
    | +| Pass/Fail criteria | Check that the STR is as specified in steps 2 and 3. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------| +| TP Id | TP/HFS/REC/WSI/BSP/BV-006 | | | +| TP label | Security Token References - Key Identifier References | | | +| Coverage | Spec | [OASIS/WS-I BSP] | | +| | Testable items | BSP-R3054; M
    BSP-R3071; M | BSP-R3063; M
    BSP-R3070; M | +| Test purpose | Check that:
    Any STR_KEY_IDENTIFIER must specify a ValueType attribute
    [AND]
    Any STR_KEY_IDENTIFIER ValueType attribute must contain a value specified within the security token profile associated with the referenced SECURITY_TOKEN
    [AND]
    Any STR_KEY_IDENTIFIER that refers to a SECURITY_TOKEN other than a SAML_TOKEN must specify an EncodingType attribute
    [AND]
    Any STR_KEY_IDENTIFIER EncodingType attribute must have a value of "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary". | | | +| Applicability | C_REC_000 AND C_REC_WSI_020 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send a SOAP message with the same security policy as the HFS receiver. | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated HFS sender sends a message using a security token reference (STR) with a key identifier reference.
    2. 2. The HFS receiver under test responds with a message including a SecurityTokenReference with a key identifier reference: 
      <wsse:SecurityTokenReference>   <wsse:KeyIdentifier wsu:Id="..."     ValueType="..."     EncodingType="...">     ...   </wsse:KeyIdentifier> </wsse:SecurityTokenReference>
    3. 3. Check in the captured message that:
      1. a. ValueType is present and contains a value specified within the security token profile associated with the referenced security token.
      2. b. if SAML Token is referenced, an encodingType attribute is not present. If SAML Token is not referenced, encodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary".
    | +| Pass/Fail criteria | In step 3, the attributes are as specified. | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--| +| TP Id | TP/HFS/REC/WSI/BSP/BV-024 | | | +| TP label | SoapAction Header | | | +| Coverage | Spec | [OASIS/WS-I BSP] | | +| | Testable items | BSP-C2010; R | | +| Test purpose | Check that:

    In a Description, the soapAction attribute of a soapbind:operation element should be either omitted, or have as its value an empty string | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The HFS receiver under test has a WebService enabled and its WSDL description is available. | | | +| Test procedure |
    1. 1. Take the wsdl description using the URL provided by the HFS receiver under test (I_REC_WSI_001).
    2. 2. Check that in soapbind:operation element, the soapAction attribute is omitted or its value is an empty string.
    | | | +| Pass/Fail criteria | In step 2, it is recommended that the soapAction attribute is omitted or that its value is an empty string, if it is present and includes any value, a warning is issued. | | | +| Notes | This test case verifies a recommended behaviour and therefore it will never result in a fail. | | | + +## A.4 Subgroup 2.1.3 – Reliable messaging (RM) + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|--| +| TP Id | TP/HFS/REC/WSI/RM/BV-000_A | | | | +| TP label | Protocol Preconditions | | | | +| Coverage | Spec | [OASIS WS-I RM] | | | +| | Testable items | Namespace; M | | | +| Test purpose |

    Check that:

    The XML namespace URI that MUST be used by implementations of this specification is:
    http://docs.oasis-open.org/ws-rx/wsrm/200702

    | | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | | +| Other PICS | | | | | +| Initial condition | The simulated HFS sender and the HFS receiver under test are in the "None" sequence state. | | | | +| Test procedure |
    1. 1. The simulated HFS sender sends a CreateSequence with an offer element to the HFS receiver.
    2. 2. The HFS receiver under test responds with a CreateSequenceResponse accepting the offer.
    3. 3. The simulated HFS sender sends a sequence.
    4. 4. The HFS receiver under test responds with its sequence and a SequenceAcknowledgement element.
    5. 5. The simulated HFS sender sends a SequenceAcknowledgement element.
    | | | | +| Pass/Fail criteria |

    Check that in every wsrm element its XML namespace is:
    xmlns:wsrm="http://docs.oasis-open.org/ws-rx/wsrm/200702"

    | | | | +| Notes | | | | | + +| | | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------|--| +| TP Id | TP/HFS/REC/WSI/RM/BV-000_B | | | | +| TP label | Delivery Assurances | | | | +| Coverage | Spec | [OASIS WS-I RM] | | | +| | Testable items | DelivAssurance 4; C | DelivAssurance 7; C | | +| | Spec | [ITU-T H.812] | | | +| | Testable items | CommonReq 2; O | CommonReq 3; R | | +| Test purpose |

    Check that:

    AtMostOnce assertion sets that each message is to be delivered at most once. The RM Source MAY retry transmission of unacknowledged messages, but is NOT REQUIRED to do so.

    [AND]

    The requirement on an RM Source using ExactlyOnce assertion is that it SHOULD retry transmission of every message sent by the Application Source until it receives an acknowledgement from the RM Destination

    [AND]

    Continua HFS client and service components may transmit messages from the Continua better QoS bin using a WS-ReliableMessaging sequence configured to use 'AtMostOnce' message delivery.

    [AND]

    Continua HFS client and service components should transmit messages from the Continua best QoS bin using a WS-ReliableMessaging sequence configured to use 'ExactlyOnce'

    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | message delivery. | +| Applicability | C_REC_000 AND (C_REC_WSI_025 OR C_REC_WSI_026) AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The simulated HFS sender and the HFS receiver under test are in the "None" sequence state. | +| Test procedure |
    1. 1. The simulated HFS sender sends a CreateSequence message with an offer element.
    2. 2. The HFS receiver under test responds with CreateSequenceResponse.
    3. 3. The HFS sender sends a sequence message indicating that it is the last message. Note that when the HFS receiver acknowledges that sequence, the HFS sender and HFS receiver switch WSRM roles: the HFS sender becomes an RM destination and the HFS receiver becomes an RM source.
    4. 4. The HFS receiver responds with the SequenceAcknowledgement and a sequence message indicating that it is the last message.
    5. 5. The HFS sender does not send the SequenceAcknowledgement.
    6. 6. If C_REC_WSI_025, the HFS receiver may retry transmission.
    7. 7. If C_REC_WSI_026, the HFS receiver should retry transmission.
    | +| Pass/Fail criteria | All steps are as indicated. | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--| +| TP Id | TP/HFS/REC/WSI/RM/BV-001 | | | +| TP label | Considerations on the Use of Extensibility Points | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | ExtensPoints 2; R | | +| Test purpose | Check that:

    If an HFS receiver does not recognize an extension, the HFS receiver SHOULD ignore the extension | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The simulated HFS sender and the HFS receiver under test are in the "None" sequence state. | | | +| Test procedure |
    1. 1. The simulated HFS sender sends a CreateSequence message using an extensibility point that the HFS receiver does not recognize, such as <myExtensibilityPoint/>.
    2. 2. The HFS receiver under test should respond, ignoring the extensibility point, with CreateSequenceResponse.
    | | | +| Pass/Fail criteria | All step are as indicated. | | | +| Notes | An attribute extensibility point is referred to using @{any} in place of the attribute name. This indicates that any attribute name can be used, from any namespace other than the wsrn: namespace. | | | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-002 | | | +| TP label | Consideration on the Use of "Piggy-Backing" | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | PiggyBack 1; O | PiggyBack 2; M | +| Test purpose | Check that:

    Some RM Protocol Header Blocks MAY be added to messages that are targeted to the same Endpoint to which those headers are to be sent (a concept often referred to as "piggy-backing"), thus saving the overhead of an additional message exchange. | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    Reference parameters MUST be considered when determining whether two endpoint references (EPRs) are targeted to the same Endpoint

    [AND]

    In order to ensure optimal and successful processing of RM Sequences, endpoints that receive RM-related messages SHOULD be prepared to process RM Protocol Header Blocks that are included in any message it receives.

    | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The simulated HFS sender and the HFS receiver under test are in the "None" sequence state. | +| Test procedure |
    1. 1. The simulated HFS sender sends a CreateSequence with an offer element.
    2. 2. The HFS receiver under test responds with CreateSequenceResponse.
    3. 3. The HFS sender sends a sequence message.
    4. 4. The HFS receiver responds including a SequenceAcknowledgement header block.
      • If the SOAP message also contains a sequence header block (piggy-backing), all the header blocks have the same EPR.
      • If not, any other header block is sent in the same SOAP message, the HFS receiver under test sends a message for every other RM-element (not piggy-backing).
    5. 5. The HFS sender responds using a SequenceAcknowledgement header block.
    | +| Pass/Fail criteria | In step 4, if the HFS receiver sends only one message with more than one header block (piggy-backing), the EPR is the same for every header block. | +| Notes |

    See the sections of the WS-RM that define each RM Protocol header block for indications on which ones may be considered for piggy-backing.

    An endpoint reference is made using a "wsa:To" element. The way to test that every header block is targeted to the same endpoint is to check that there is only one "wsa:To" element in the soap:header.

    | + +| | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-003 | | | +| TP label | Sequence Creation | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | WSAddress 1; C | SeqCreation 1; M | +| | | SeqCreation 6; M | SeqCreation 13; M | +| | | SeqCreation 17; M | SeqCreation 18; C | +| | | SeqCreation 20; O | SeqCreation 21; O | +| | | SeqRefused 1; M | Faults 3; M | +| Test purpose |

    Check that:

    When an Endpoint generates a message that carries an RM protocol element in the body of a SOAP envelope that Endpoint MUST include in that envelope a wsa:Action SOAP header block whose value is an IRI that is a concatenation of the WS-RM namespace URI, followed by a "/", followed by the value of the local name of the child element of the SOAP body.

    [AND]

    The RM Source MUST request creation of an outbound Sequence by sending a CreateSequence element in the body of a message to the RM Destination which in turn responds either with a message containing CreateSequenceResponse or a CreateSequenceRefused fault

    [AND]

    An offer is either accepted or rejected by the RM Destination in the CreateSequenceResponse message.

    [AND]

    | | | + +| | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    The RM Destination MUST respond either with a CreateSequenceResponse response message or a CreateSequenceRefused fault

    [AND]

    An RM Destination MUST NOT accept (via the /wsrm:CreateSequenceResponse/wsrm:Accept element) an offer that contains the "http://www.w3.org/2005/08/addressing/anonymous" IRI as its address

    [AND]

    The RM Destination MUST NOT send wsrm:CreateSequenceResponse element as a header block. This element is sent in the body of the response message in response to a CreateSequence request message

    [AND]

    The RM Destination MUST include wsrm:Identifier element within any CreateSequenceResponse message it sends. The RM Destination MUST set the value of this element to the absolute URI (conformant with RFC3986) that uniquely identifies the Sequence that has been created by the RM Destination

    [AND]

    wsrm:Expires element, if present, of type xs:duration accepts or refines the RM Source's requested duration for the Sequence. It specifies the amount of time after which any resources associated with the Sequence SHOULD be reclaimed thus causing the Sequence to be silently terminated

    [AND]

    The RM Destination MUST set the value of wsrm:Expires element to be equal to or less than the value requested by the RM Source in the corresponding CreateSequence message.

    [AND]

    wsrm:IncompleteSequenceBehaviour element, if present in wsrm:CreateSequenceResponse element, specifies the behavior that the destination will exhibit upon the closure or termination of an incomplete Sequence. For the purposes of defining the values used, the term "discard" refers to behavior equivalent to the Application Destination never processing a particular message.

    A value of "DiscardEntireSequence" indicates that the entire Sequence MUST be discarded if the Sequence is closed, or terminated, when there are one or more gaps in the final SequenceAcknowledgement.

    A value of "DiscardFollowingFirstGap" indicates that messages in the Sequence beyond the first gap MUST be discarded when there are one or more gaps in the final SequenceAcknowledgement.

    The default value of "NoDiscard" indicates that no acknowledged messages in the Sequence will be discarded.

    [AND]

    wsrm:Accept element, if present, enables an RM Destination to accept the offer if a corresponding Sequence for the reliable exchange of messages Transmitted from RM Destination to RM Source

    [AND]

    The RM Destination MUST include wsrm:AcksTo element within wsrm:Accept.

    [AND]

    CreateSequenceRefused properties:

    [Code] HFS Sender or HFS Receiver

    [Subcode] wsrm:CreateSequenceRefused

    [Reason] The Create Sequence request has been refused by the RM Destination.

    [Detail] xs:any

    [AND]

    Entities that generate WS-ReliableMessaging faults MUST include as the [action] property the default fault action IRI: http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.

    | +| Applicability | C_REC_000 AND C_REC_GEN_003 | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The simulated HFS Sender and the HFS receiver under test are in the "None" sequence state. | +| Test procedure |
    1. 1. The simulated HFS Sender sends a CreateSequence, with an offer element message to the HFS receiver under test.
    2. 2. The HFS receiver responds with a CreateSequenceResponse or a CreateSequenceRefused fault message.

    If the response is CreateSequenceResponse:

    1. 3. The received message has the following properties:
      1. a. In the header block:
        • ❑ wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequenceResponse.
        • ❑ wsrm:CreateSequenceResponse is not present.
      2. b. In the body of the message:
        • ❑ the wsrm:Identifier value is an absolute URI that uniquely identifies the sequence created by the RM destination
        • ❑ the wsrm:Expires element, if present:
          • • its type is xs:duration
          • • is value is equal or less than the value requested by the RM source in the corresponding CreateSequence message
          • • it is recommended that any resources associated with the sequence are reclaimed before this time. Otherwise, the sequence will be silently terminated after this time.
        • ❑ the wsrm:IncompleteSequenceBehaviour element may be present. Possible values are: "discard", "DiscardEntireSequence", "DiscardFollowingFirstGap" and "NoDiscard"
        • ❑ if the offer element contains the "http://www.w3.org/2005/08/addressing/anonymous" IRI as its address, the HFS receiver does not accept this offer.
        • ❑ if wsrm:Accept is present, wsrm:AcksTo is present within the Accept element, and the HFS receiver is able to send sequences messages
        • ❑ if wsrm:Accept is not present, the HFS receiver is NOT able to send sequences messages.

    If the response is a CreateSequenceRefused fault:

    1. 4. the received message has the following properties:
      • ❑ wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/fault
      • ❑ Code = HFS Sender or HFS Receiver
      • ❑ Subcode = wsrm:CreateSequenceRefused
      • ❑ Reason = "The create sequence request has been refused by the RM destination".
      • ❑ Detail = xs:any.
    | +| Pass/Fail criteria | All the elements are as specified and only if the offer is accepted by the HFS receiver, can it send sequence messages. | +| Notes | | + +| | | | | +|-----------------|--------------------------|-----------------|-----------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-004 | | | +| TP label | Closing a Sequence | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | WSAddress 1; C | SeqClosing 1; O | +| | | SeqClosing 3; M | SeqClosing 4; R | +| | | SeqClosing 2; M | SeqClosing 5; O | + +| | | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|------------------| +| | | SeqClosing 6; M | SeqClosing 8; O | SeqClosing 9; M | +| | | SeqClosing 10; R | SeqClosing 11; M | SeqClosing 12; M | +| | | SeqClosing 7; R | | | +| Test purpose |

    Check that:

    When an Endpoint generates a message that carries an RM protocol element in the body of a SOAP envelope that Endpoint MUST include in that envelope a wsa:Action SOAP header block whose value is an IRI that is a concatenation of the WS-RM namespace URI, followed by a "/", followed by the value of the local name of the child element of the SOAP body.

    [AND]

    To ensure that the Sequence ends with a known final state either the RM Source or RM Destination MAY choose to close the Sequence before terminating it.

    [AND]

    If the RM Source wishes to close the Sequence, then it sends a CloseSequence element, in the body of a message, to the RM Destination. This message indicates that the RM Destination MUST NOT accept any new messages for the specified Sequence, other than those already accepted at the time the CloseSequence element is interpreted by the RM Destination

    [AND]

    Upon receipt of CloseSequence message, or subsequent to the RM Destination closing the Sequence of its own volition, the RM Destination MUST include a final SequenceAcknowledgement (within which the RM Destination MUST include the Final element) header block on any messages associated with the Sequence destined to the RM Source, including the CloseSequenceResponse message or on any Sequence fault Transmitted to the RM Source

    [AND]

    To allow the RM Destination to determine if it has received all of the messages in a Sequence, the RM Source SHOULD include the LastMsgNumber element in any CloseSequence messages it sends. The value of the LastMsgNumber element MUST be the same in all the CloseSequence messages for the closing Sequence

    [AND]

    If the RM Destination decides to close a Sequence of its own volition, it MAY inform the RM Source of this event by sending a CloseSequence element, in the body of a message, to the AcksTo EPR of that Sequence. The RM Destination MUST include a final SequenceAcknowledgement (within which the RM Destination MUST include the Final element) header block in this message and any subsequent messages associated with the Sequence destined to the RM Source

    [AND]

    While the RM Destination MUST NOT accept any new messages for the specified Sequence it MUST still process Sequence Lifecycle Messages and Acknowledgement Requests

    [AND]

    /wsrm:CloseSequence. This element MAY be sent by an RM Source to indicate that the RM Destination MUST NOT accept any new messages for this Sequence This element MAY also be sent by an RM Destination to indicate that it will not accept any new messages for this Sequence

    [AND]

    The RM Source or RM Destination MUST include wsrm:Identifier element in any CloseSequence messages it sends. The RM Source or RM Destination MUST set the value of this element to the absolute URI (conformant with RFC3986) of the closing Sequence

    [AND]

    The RM Source SHOULD include wsrm:LastMessageNumber element in any CloseSequence message it sends.

    [AND]

    A wsrm:CloseSequenceResponse element is sent in the body of a message in response to receipt of a CloseSequence request message. It indicates that the responder has closed the Sequence

    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    The responder (RM Source or RM Destination) MUST include wsrn:Identifier element in any CloseSequenceResponse messages it sends. The responder MUST set the value of this element to the absolute URI (conformant with RFC3986) of the closing Sequence.

    [AND]

    In the case where the RM Destination wishes to discontinue use of a Sequence it is RECOMMENDED that it close the Sequence. Whenever possible the SequenceClosed fault SHOULD be used in place of the SequenceTerminated fault to allow the RM Source to still Receive Acknowledgements.

    | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | C_REC_WSI_033 | +| Initial condition | The simulated HFS sender has created a sequence with an offer element. The simulated HFS sender and the HFS receiver under test are in the "Created" sequence state. | +| Test procedure |
    1. 1. The simulated HFS sender sends a sequence message including an AckRequested element in its header block or indicating that it is the last one.
    2. 2. The HFS receiver under test responds using a SequenceAcknowledgement header block.
    3. 3. If C_REC_WSI_033 = TRUE, the HFS receiver under test sends a CloseSequence element in the body of the message before the simulated HFS sender does, check that the received message includes:
      1. a. In the header block:
        • a SequenceAcknowledgement element and a wsrn:Final element within it are present.
        • wsa:Action = http://docs.oasis-open.org/ws-rx/wsrn/200702/CloseSequence.
      2. b. In the body of the message, within the CloseSequence element:
        • the wsrn:Identifier value is an absolute URI of the closing sequence
        • it is recommended that a LastMsgNumber element is present and that in this case, it specifies the highest assigned message number of all the sequence traffic messages for the closing sequence.
    4. 4. If the HFS receiver under test sends the CloseSequence element in the body of the message before the simulated HFS sender, the simulated HFS sender responds with a CloseSequenceResponse message, including its Identifier element as an absolute URI, then goes to step 7 below.
    5. 5. If C_REC_WSI_033 = FALSE, the simulated HFS sender sends a CloseSequence element in the body of the message including a correct LastMsgNumber.
    6. 6. The HFS receiver responds with a message including:
      1. a. In the header block:
        • A SequenceAcknowledgement header block including a Final element is present.
        • wsa:Action = http://docs.oasis-open.org/ws-rx/wsrn/200702/CloseSequenceResponse.
      2. b. In the body of the message:
        • A CloseSequenceResponse element with a wsrn:Identifier element that is an absolute URI of the closing sequence.
    7. 7. Once the sequence is closed, the HFS sender sends a new sequence message referencing that closed sequence.
    8. 8. The HFS receiver under test does not accept that message. It is recommended that HFS receiver responds with a SequenceClosed fault.
    | +| Pass/Fail criteria | All fields are as specified. | +| Notes | | + +| | | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|----------------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-005 | | | | +| TP label | Sequence Termination | | | | +| Coverage | Spec | [OASIS WS-I RM] | | | +| | Testable items | WSAddress 1; C | SeqTermination 1; R | SeqTermination 2; M | +| | | SeqTermination 3; O | SeqTermination 4; O | SeqTermination 5; M | +| | | SeqTermination 7; M | SeqTermination 8; O | SeqTermination 9; M | +| | | SeqTermination 10; M | SeqTermination 11; M | SeqTermination 12; R | +| | | SeqTermination 13; M | SeqTermination 14; M | SeqTermination 15; M | +| Test purpose |

    Check that:

    When an Endpoint generates a message that carries an RM protocol element in the body of a SOAP envelope that Endpoint MUST include in that envelope a wsa:Action SOAP header block whose value is an IRI that is a concatenation of the WS-RM namespace URI, followed by a "/", followed by the value of the local name of the child element of the SOAP body.

    [AND]

    To allow the RM Destination to determine if it has received all of the messages in a Sequence, the RM Source SHOULD include the LastMsgNumber element in any TerminateSequence messages it sends

    [AND]

    The value of the LastMsgNumber element in the TerminateSequence message MUST be equal to the value of the LastMsgNumber element in any CloseSequence message(s) sent by the RM Source for the same Sequence

    [AND]

    If the RM Destination decides to terminate a Sequence of its own volition, it MAY inform the RM Source of this event by sending a TerminateSequence element, in the body of a message, to the AcksTo EPR for that Sequence. The RM Destination MUST include a final SequenceAcknowledgement (within which the RM Destination MUST include the Final element) header block in this message

    [AND]

    A wsrm:TerminateSequence element MAY be sent by an RM Source to indicate it has completed its use of the Sequence

    [AND]

    The RM Source MUST NOT send wsrm:TerminateSequence element as a header block

    [AND]

    Once wsrm:TerminateSequence element is sent, other than this element, the RM Source MUST NOT send any additional message to the RM Destination referencing this Sequence

    [AND]

    A wsrm:TerminateSequence element MAY also be sent by the RM Destination to indicate that it has unilaterally terminated the Sequence

    [AND]

    Upon sending wsrm:TerminateSequence message the RM Destination MUST NOT accept any additional messages (with the exception of the corresponding TerminateSequenceResponse) for this Sequence

    [AND]

    Upon receipt of a TerminateSequence the RM Source MUST NOT send any additional messages (with the exception of the corresponding TerminateSequenceResponse) for this Sequence

    [AND]

    The RM Source or RM Destination MUST include wsrm:Identifier element in any TerminateSequence message it sends. The RM Source or RM Destination MUST set the value of this element to the absolute URI (conformant with RFC3986) of the terminating Sequence

    [AND]

    | | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    /wsmr:TerminateSequence/wsmr:LastMsgNumber. The RM Source SHOULD include this element in any TerminateSequence message it sends. The LastMsgNumber element specifies the highest assigned message number of all the Sequence Traffic Messages for the terminating Sequence.

    [AND]

    TerminateSequenceResponse element is sent in the body of a message in response to receipt of a TerminateSequence request message. It indicates that the responder has terminated the Sequence. The responder MUST NOT send this element as a header block

    [AND]

    The responder (RM Source or RM Destination) MUST include wsmr:Identifier element in any TerminateSequenceResponse message it sends. The responder MUST set the value of this element to the absolute URI (conformant with RFC3986) of the terminating Sequence.

    [AND]

    On receipt of a TerminateSequence message the HFS receiver (RM Source or RM Destination) MUST respond with a corresponding TerminateSequenceResponse message or generate a fault UnknownSequenceFault if the Sequence is not known.

    | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | C_REC_WSI_035 | +| Initial condition | The simulated HFS sender has created a sequence with an offer element. The simulated HFS sender and the HFS receiver under test are in the "Created" sequence state. | +| Test procedure |
    1. 1. The simulated HFS sender sends a sequence message including an AckRequested element in its header block or indicating that it is the last one.
    2. 2. The HFS receiver under test responds using a SequenceAcknowledgement header block.
    3. 3. If C_REC_WSI_035 = TRUE, the HFS receiver under test sends a TerminateSequence element in the body of the message before the simulated HFS sender does so. The received message includes:
      1. a. In the header block:
      2. b. In the body of the message, within the TerminateSequence element:
        • The wsmr:Identifier value is an absolute URI of the terminating sequence.
        • It is recommended that LastMsgNumber is present, and in that case, its value must be equal to the value of the LastMsgNumber element in any CloseSequence message(s) sent for the same sequence.
    4. 4. If the HFS receiver sends a TerminateSequence, the simulated HFS sender responds with a TerminateSequenceResponse message, including its Identifier element as an absolute URI.
    5. 5. If C_REC_WSI_035 = FALSE, the simulated HFS sender sends a TerminateSequence element in the body of the message and it is recommended that the TerminateSequence element includes a correct LastMsgNumber.
    6. 6. If the simulated HFS sender has sent a TerminateSequence, the HFS receiver generates an UnknownSequence fault or responds with a message including:
      1. a. In the header block:
      2. b. In the body of the message within the TerminateSequenceResponse element:
        • wsmr:Identifier value = an absolute URI of the terminating sequence.
    7. 7. Once the sequence is terminated, the simulated HFS sender sends a sequence message referencing the terminated sequence.
    | + +| | | +|---------------------------|--------------------------------------------------------------| +| | 8. The HFS receiver under test does not accept that message. | +| Pass/Fail criteria | All fields and messages exchanged are as specified. | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|----------------|----------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-006 | | | | +| TP label | Sequences | | | | +| Coverage | Spec | [OASIS WS-I RM] | | | +| | Testable items | ProtocolInv 1; M | Sequences 1; M | Sequences 2; M | +| | | Sequences 3; M | Sequences 4; M | Sequences 5; M | +| | | Sequences 6; M | Sequences 7; M | Sequences 8; M | +| Test purpose |

    Check that:

    The RM Source MUST assign each message within a Sequence a message number beginning at 1 and increasing by exactly 1 for each subsequent message. These numbers MUST be assigned in the same order in which messages are sent by the Application Source.

    [AND]

    The RM Source MUST include a Sequence header block in all messages for which reliable transfer is REQUIRED

    [AND]

    The RM Source MUST identify Sequences with unique Identifier elements and the RM Source MUST assign each message within a Sequence a MessageNumber element that increments by 1 from an initial value of 1

    [AND]

    The RM Source MUST NOT include more than one Sequence header block in any message

    [AND]

    The RM Destination MUST understand the Sequence header block

    [AND]

    The RM Source MUST assign a mustUnderstand attribute with a value 1/true (from the namespace corresponding to the version of SOAP to which the Sequence SOAP header block is bound) to the Sequence header block element.

    [AND]

    An RM Source that includes a Sequence header block in a SOAP envelope MUST include wsrn:Identifier element in that header block

    [AND]

    The RM Source MUST set the value of wsrn:Identifier element to the absolute URI (conformant with RFC3986) that uniquely identifies the Sequence

    [AND]

    The RM Source MUST include wsrn:MessageNumber element within any Sequence headers it creates. This element is of type MessageNumberType.

    | | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | | +| Other PICS | | | | | +| Initial condition | The simulated HFS sender has created a sequence with an offer element. The simulated HFS sender and the HFS receiver under test are in the "Created" sequence state. | | | | +| Test procedure |
    1. The simulated HFS sender sends a sequence message including an AckRequested element in its header block or indicates that it is the last one.
    2. The HFS receiver under test responds using a SequenceAcknowledgement header block.
    3. If an offer element was sent in the CreateSequence and the HFS receiver accepts that offer:
      • Wait until the HFS receiver starts to send sequence messages.
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | In the received messages, check that:
    • The wsm:MessageNumber element is of type MessageNumberType and starts at 1 and increments by 1 for every sequential message.
    • There is only one sequence header block in each message.
    • The wsm:Identifier element must be present in the header block and must be an absolute URI that uniquely identifies the sequence.
    • The mustUnderstand attribute = "1" or "true".
    | +| Pass/Fail criteria | All elements in step 3 are as specified. | +| Notes | | + +| | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|----------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-007 | | | +| TP label | Request Acknowledgement | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | ProtocolInv 6; R | WSAddress 3; C | +| | | ReqAck 2; O | ReqAck 7; M | +| | | SeqAck 3; R | SeqAck 4; M | +| | | SeqAck 23; R | ReqAck 1; O | +| Test purpose |

    Check that:

    While the Sequence is not closed or terminated, the RM Source SHOULD retransmit unacknowledged messages.

    [AND]

    When an Endpoint generates an Acknowledgement Request that has no element content in the SOAP body, then the value of the wsa:Action IRI MUST be: http://docs.oasis-open.org/ws-rx/wsrm/200702/AckRequested.

    [AND]

    The RM Source MAY request an Acknowledgement Message from the RM Destination at any time by independently transmitting an AckRequested header block

    [AND]

    Alternatively the RM Source MAY include an AckRequested header block in any message targeted to the RM Destination

    [AND]

    An RM Source that includes an AckRequested header block in a SOAP envelope MUST include wsm:Identifier element in that header block

    [AND]

    The RM Source MUST set the value of wsm:Identifier element to the absolute URI, (conformant with RFC3986), that uniquely identifies the Sequence to which the request applies.

    [AND]

    The RM Source SHOULD process SequenceAcknowledgement header blocks that are included in any message it receives.

    [AND]

    If a non-mustUnderstand fault occurs when processing a SequenceAcknowledgement header that was piggy-backed, a fault MUST be generated, but the processing of the original message MUST NOT be affected

    [AND]

    Upon the receipt of a Nack, an RM Source SHOULD retransmit the message identified by the Nack.

    [AND]

    The RM Source SHOULD ignore a SequenceAcknowledgement containing a Nack for a

    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | message that has previously been acknowledged within an AcknowledgementRange. | +| Applicability | C_REC_000 AND C_REC_WSI_036 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The simulated HFS sender and the HFS receiver under test are in the "None" sequence state. | +| Test procedure |
    1. 1. The simulated HFS sender sends a CreateSequence message with an offer element.

    If the HFS receiver accepts the offer:

    1. 2. The HFS receiver responds with a CreateSequenceResponse including an accept element.
    2. 3. The simulated HFS sender sends a sequence message indicating that it is the last one.
    3. 4. The HFS receiver under test sends a SequenceAcknowledgement and starts to send sequence messages and sends its first AckRequested element in the header block of one message.
    4. 5. In the header block of that received message, check that:
      • ❏ wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/AckRequested (if soap body is empty).
      • ❏ wsrm:Identifier = absolute URI that uniquely identifies the sequence.
    5. 6. The simulated HFS sender does not validate any message with a SequenceAcknowledgement header block with a None element.
    6. 7. The HFS receiver should retransmit the messages.
    7. 8. If the HFS receiver retransmits the messages, the simulated HFS sender does not validate any message using a Nack element within a SequenceAcknowledgement header block.
    8. 9. The HFS receiver should retransmit the messages.
    9. 10. If the HFS receiver retransmits the messages, the simulated HFS sender validates the messages using a SequenceAcknowledgement header block.
    10. 11. The simulated HFS sender sends a Nack element with the MessageNumber of one of the previous messages received.
    11. 12. The HFS receiver should ignore the Nack element.
    | +| Pass/Fail criteria |

    All elements are as specified.

    If a non-mustUnderstand fault occurs when processing a SequenceAcknowledgement header that was piggy-backed, a fault is generated, but the processing of the original message is not affected.

    | +| Notes | | + +| | | | | | +|---------------------|--------------------------|------------------|------------------|------------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-008 | | | | +| TP label | Sequence Acknowledgement | | | | +| Coverage | Spec | [OASIS WS-I RM] | | | +| | Testable items | ProtocolInv 2; M | ProtocolInv 3; M | ProtocolInv 4; M | +| | | ProtocolInv 5; O | WSAddress 2; C | ReqAck 3; R | +| | | ReqAck 4; M | ReqAck 5; M | SeqAck 1; O | +| | | SeqAck 2; O | SeqAck 5; O | SeqAck 6; M | +| | | SeqAck 7; R | SeqAck 8; M | SeqAck 9; M | +| | | SeqAck 10; M | SeqAck 11; O | SeqAck 12; M | +| | | SeqAck 13; M | SeqAck 14; M | SeqAck 15; M | +| | | SeqAck 16; M | SeqAck 17; M | SeqAck 18; O | +| | | SeqAck 19; M | SeqAck 20; O | SeqAck 22; M | +| Test purpose | Check that: | | | | + +Within every Acknowledgement Message it issues, the RM Destination MUST include one or more AcknowledgementRange child elements that contain, in their collective ranges, the message number of every message accepted by the RM Destination. + +[AND] + +The RM Destination MUST exclude, in the AcknowledgementRange elements, the message numbers of any messages it has not accepted. + +[AND] + +If no messages have been received the RM Destination MUST return None instead of an AcknowledgementRange(s). + +[AND] + +The RM Destination MAY transmit a Nack for a specific message or messages instead of an AcknowledgementRange(s). + +[AND] + +When an Endpoint generates an Acknowledgement Message that has no element content in the SOAP body, then the value of the wsa:Action IRI MUST be: + +[AND] + +The RM Destination SHOULD process AckRequested header blocks that are included in any message it receives + +[AND] + +If a non-mustUnderstand fault occurs when processing an AckRequested header block that was piggy-backed, a fault MUST be generated, but the processing of the original message MUST NOT be affected. + +[AND] + +An RM Destination that Receives a message that contains an AckRequested header block MUST send a message containing a SequenceAcknowledgement header block to the AcksTo endpoint reference for a known Sequence or else generate an UnknownSequence fault + +[AND] + +The RM Destination MAY Transmit the SequenceAcknowledgement header block independently (i.e. as a header of a SOAP envelope with an empty body) + +[AND] + +Alternatively, an RM Destination MAY include a SequenceAcknowledgement header block on any SOAP envelope targeted to the endpoint referenced by the AcksTo EPR + +[AND] + +During creation of a Sequence the RM Source MAY specify the WS-Addressing anonymous IRI as the address of the AcksTo EPR for that Sequence + +[AND] + +When the RM Source specifies the WS-Addressing anonymous IRI as the address of the AcksTo EPR, the RM Destination MUST Transmit any SequenceAcknowledgement headers for the created Sequence in a SOAP envelope to be Transmitted on the protocol binding-specific back-channel + +[AND] + +When the RM Destination receives an AckRequested header, and the AckTo EPR for that sequence is the WS-Addressing anonymous IRI, the RM Destination SHOULD respond on the protocol binding-specific back-channel provided by the Received message containing the AckRequested header block + +[AND] + +An RM Destination that includes a SequenceAcknowledgement header block in a SOAP envelope MUST include wsrm:Identifier element in that header block + +[AND] + +The RM Destination MUST set the value of wsrm:Identifier element to the absolute URI (conformant with RFC3986) that uniquely identifies the Sequence + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    The RM Destination MUST NOT include multiple SequenceAcknowledgement header blocks that share the same value for Identifier within the same SOAP envelope

    [AND]

    The RM Destination MAY include one or more instances of wsrm:AcknowledgementRange element within a SequenceAcknowledgement header block

    [AND]

    The ranges in wsrm:AcknoledgementRange MUST NOT overlap.

    [AND]

    The RM Destination MUST NOT include wsrm:AcknowledgementRange element if a sibling Nack or None element is also present as a child of SequenceAcknowledgement

    [AND]

    The RM Destination MUST set the value of upper attribute (in wsrm:AcknoledgementRange) equal to the message number of the highest contiguous message in a Sequence range accepted by the RM Destination

    [AND]

    The RM Destination MUST set the value of Lower attribute (in wsrm:AcknowledgementRange) equal to the message number of the lowest contiguous message in a Sequence range accepted by the RM Destination

    [AND]

    The RM Destination MUST include wsrm:None element within a SequenceAcknowledgement header block if the RM Destination has not accepted any messages for the specified Sequence

    [AND]

    The RM Destination MUST NOT include wsrm:None element if a sibling AcknowledgementRange or Nack element is also present as a child of the SequenceAcknowledgement

    [AND]

    The RM Destination MAY include wsrm:Final element within a SequenceAcknowledgement header block. This element indicates that the RM Destination is not receiving new messages for the specified Sequence

    [AND]

    The RM Destination MUST include wsrm:Final element when the Sequence is closed. The RM Destination MUST NOT include this element when sending a Nack; it can only be used when sending AcknowledgementRange elements or a None

    [AND]

    The RM Destination MAY include wsrm:Nack element within a SequenceAcknowledgement header block. If used, the RM Destination MUST set the value of this element to a MessageNumberType representing the MessageNumber of an unreceived message in a Sequence. The RM Destination MUST NOT include a Nack element if a sibling AcknowledgementRange or None element is also present as a child of SequenceAcknowledgement

    [AND]

    The RM Destination MUST NOT issue a SequenceAcknowledgement containing a Nack for a message that it has previously acknowledged within an AcknowledgementRange

    | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The simulated HFS sender has created a sequence with an offer. The simulated HFS sender and the HFS receiver under test are in the "Created" sequence state. | +| Test procedure |
    1. The simulated HFS sender transmits 3 messages with its respective sequence header block and in the last one it includes an AckRequest.
    2. The HFS receiver under test responds including a SequenceAcknowledgement header block or an UnknownSequence fault.
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    3. If the response has a SequenceAcknowledgement header block:

    • ❑ If AcksTo field of any message to be acknowledged is an anonymous IRI, the HFS receiver must transmit the SequenceAcknowledgement on the channel provided by the context of the received message containing a SOAP envelope that contains a sequence header block and/or an AckRequested header block for that same sequence identifier.
    • ❑ If the soap body of the message is empty, the wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/SequenceAcknowledgement
    • ❑ The wsrm:Identifier = absolute URI. It cannot be used in another SequenceAcknowledgement in the same message.
    • ❑ Only one of these elements is present: one or more AcknowledgementRange, a None or a Nack.
    • ❑ The final element is present when the sequence is closed, but it is not included when a Nack is sent.
    • ❑ If an AcknowledgementRange element is present:
      • • the lower attribute is equal to or less than the upper attribute,
      • • the lower attribute is equal to the message number of the lowest contiguous message in a sequence range accepted by the HFS receiver,
      • • the upper attribute is equal to the message number of the highest contiguous message in a sequence range accepted by the HFS receiver.
    • ❑ If a None element is present then no messages have been accepted or received.
    • ❑ If a Nack element is present a specific message has not been received and it cannot be included in a SequenceAcknowledgement header block for a message that it had previously acknowledged within an AcknowledgementRange.
    | +| Pass/Fail criteria |

    All elements are as specified.

    If a non-mustUnderstand fault occurs when processing an AckRequested header block that was piggy-backed, a fault is generated, but the processing of the original message is not affected.

    | +| Notes | | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-009 | | | +| TP label | Sequence Terminated Fault | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | SeqTerminatedFault 2; M | SeqTerminatedFault 3; M | +| | | Faults 1; R | Faults 2; M | +| | | | SeqTerminatedFault 4; M | +| | | | Faults 3; M | +| Test purpose |

    Check that:

    SequenceTerminated has the following properties:

    [Code] HFS Sender or HFS Receiver

    [Subcode] wsrm:SequenceTerminated

    [Reason] The Sequence has been terminated due to an unrecoverable error.

    [Detail] <wsrm:Identifier ...> xs:anyURI </wsrm:Identifier>

    [AND]

    An Endpoint MUST generate a SequenceTerminated fault when encountering an unrecoverable condition or detection of violation of the protocol

    [AND]

    An Endpoint that receives a SequenceTerminated fault MUST terminate the Sequence if not otherwise terminated

    [AND]

    Destinations that generate faults related to known sequences SHOULD transmit those faults.

    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    If transmitted, faults MUST be transmitted to the same [destination] as Acknowledgement messages

    [AND]

    Entities that generate WS-ReliableMessaging faults MUST include as the [action] property the default fault action IRI: http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.

    | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | C_REC_WSI_035 | +| Initial condition | The simulated HFS sender and the HFS receiver under test are in the "None" sequence state. The simulated HFS sender is able to send a sequence message when the sequence has been terminated. | +| Test procedure |
    1. 1. The simulated HFS sender sends a CreateSequence message with an offer element.
    2. 2. The HFS receiver under test responds with a CreateSequenceResponse message accepting the offer.
    3. 3. The simulated HFS sender sends a sequence indicating that it is the last message.
    4. 4. The HFS receiver responds with a SequenceAcknowledgement with the element AcknowledgementRange Lower=1 and Upper=1.
    5. 5. IF C_REC_WSI_035=TRUE, wait until the HFS receiver under test sends a TerminateSequence or force it to terminate the sequence and the simulated HFS sender responds with TerminateSequenceResponse. ELSE, the simulated HFS sender sends a TerminateSequence message and the HFS receiver under test responds with TerminateSequenceResponse.
    6. 6. The simulated HFS sender transmits a sequence with the message number within the range, for example, Message Number=2.
    7. 7. The HFS receiver generates a SequenceTerminated fault. It is recommended that the fault is transmitted to the HFS sender.
    8. 8. If the fault is transmitted by the HFS receiver under test, the message includes the following properties:
    9. 9. The simulated HFS sender terminates the sequence and passes to the "None" sequence state.
    | +| Pass/Fail criteria | All elements are as specified in step 8 | +| Notes | | + +| | | | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-010 | | | +| TP label | Unknown Sequence Fault | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | UnknownSeq 1; M | UnknownSeq 2; M | +| | | Faults 1; R | Faults 2; M | +| | | UnknownSeq 3; M | | +| | | Faults 3; M | | +| Test purpose | Check that:
    UnknownSequence has the following properties:
    [Code] HFS Sender
    [Subcode] wsrm:UnknownSequence
    [Reason] The value of wsrm:Identifier is not a known Sequence identifier
    [Detail] xs:anyURI | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    An Endpoint MUST generate an UnknownSequence fault in response to a message containing an unknown or terminated Sequence identifier

    [AND]

    An Endpoint that receives an UnknownSequence fault MUST terminate the Sequence if not otherwise terminated

    [AND]

    Destinations that generate faults related to known sequences SHOULD transmit those faults.

    [AND]

    If transmitted, faults MUST be transmitted to the same [destination] as Acknowledgement messages

    [AND]

    Entities that generate WS-ReliableMessaging faults MUST include as the [action] property the default fault action IRI: http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.

    | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The simulated HFS sender and the HFS receiver under test are in the "None" sequence state. The simulated HFS sender is able to send a sequence message when it is in the "None" sequence state. | +| Test procedure |
    1. 1. The simulated HFS sender transmits a sequence message to the HFS receiver under test.
    2. 2. The HFS receiver generates an UnknownSequence fault. It is recommended that the fault is transmitted to the HFS sender.
    3. 3. If the fault is transmitted by the HFS receiver under test, that message includes the following properties:
    4. 4. Wait until the HFS receiver terminates the sequence.
    | +| Pass/Fail criteria | All elements are as specified in step 3 | +| Notes | | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-011 | | | +| TP label | Invalid Acknowledgement Fault | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | InvalidAck 1; M | InvalidAck 2; M | +| | | Faults 2; M | Faults 3; M | +| Test purpose |

    Check that:

    InvalidAcknowledgement fault has the following properties:

    [Code] HFS Sender

    [Subcode] wsrm:InvalidAcknowledgement

    [Reason] The SequenceAcknowledgement violates the cumulative Acknowledgement invariant.

    [Detail] <wsrm:SequenceAcknowledgement ...> ... </wsrm:SequenceAcknowledgement>

    [AND]

    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    RM Source MUST generate an InvalidAcknowledgement in response to a SequenceAcknowledgement that violate the invariants stated in 2.3 or any of the requirements in 3.9 about valid combinations of AckRange, Nack and None in a single SequenceAcknowledgement element or with respect to already Received such elements.

    [AND]

    Destinations that generate faults related to known sequences SHOULD transmit those faults.

    [AND]

    If transmitted, faults MUST be transmitted to the same [destination] as Acknowledgement messages

    [AND]

    Entities that generate WS-ReliableMessaging faults MUST include as the [action] property the default fault action IRI: http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.

    | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The simulated HFS sender and the HFS receiver under test are in the "None" sequence state. Simulated HFS sender is able to include a wrong AckRange and None and Nack elements in a SequenceAcknowledgement message. | +| Test procedure |
    1. The simulated HFS sender creates a sequence with an offer.
    2. The HFS receiver under test responds using a CreateSequenceResponse message accepting the offer.
    3. After the simulated HFS sender has sent its sequences and the HFS receiver acknowledges them, the HFS receiver under test sends a sequence message with its respective message number.
    4. If the last sequence message is not labelled as the last one, wait until the HFS receiver sends an AckRequested. Otherwise, go to next step.
    5. The simulated HFS sender responds with a SequenceAcknowledgement with the wrong AckRange element and None and Nack elements.
    6. The HFS receiver generates an InvalidAcknowledgement fault. It is recommended that the fault is transmitted to the HFS sender.
    7. If the fault is transmitted by the HFS receiver under test, that message includes the following properties:
    | +| Pass/Fail criteria | All elements are as specified in step 7. | +| Notes | | + +| | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-012 | | +| TP label | Message Number Rollover | | +| Coverage | Spec | [OASIS WS-I RM] | +| | Testable items | MessageNumrRoll 4; R | +| Test purpose |

    Check that:

    RM Source SHOULD continue to retransmit undelivered messages until the Sequence is closed or terminated.

    | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | +| Other PICS | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated HFS sender has created a sequence with an offer element. The simulated HFS sender and the HFS receiver under test are in the "Created" sequence state. The simulated HFS sender is able to send a message number rollover fault instead of a SequenceAcknowledgement message. | +| Test procedure |
    1. 1. The simulated HFS sender under test transmits a sequence message indicating that it is the last one.
    2. 2. The HFS receiver under test sends its sequence and the SequenceAcknowledgement.
    3. 3. The simulated HFS sender generates a message number rollover fault and this is transmitted to the HFS receiver.
    4. 4. The HFS receiver should retransmit undelivered messages until the HFS sender closes or terminates the sequence.
    5. 5. The simulated HFS sender closes the sequence.
    | +| Pass/Fail criteria | Step 4 must be as indicated. | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-------------------------------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-012_B | | | +| TP label | Message Number Rollover2 | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | MessageNumrRoll 1; M
    Faults 1; R | MessageNumrRoll 2; M
    Faults 2; M | +| Test purpose |

    Check that:

    Message Number Rollover fault has the following properties:

    [Code] HFS Sender

    [Subcode] wsrm:MessageNumberRollover

    [Reason] The maximum value for wsrm:MessageNumber has been exceeded.

    [Detail] <wsrm:Identifier ...> xs:anyURI </wsrm:Identifier>

    <wsrm:MaxMessageNumber> wsrm:MessageNumberType </wsrm:MaxMessageNumber>

    [AND]

    RM Destination MUST generate a MessageNumberRollover fault when Message number in /wsrm:Sequence/wsrm:MessageNumber of a Received message exceeds the internal limitations of an RM Destination or reaches the maximum value of 9,223,372,036,854,775,807

    [AND]

    RM Destination SHOULD continue to accept undelivered messages until the Sequence is closed or terminated

    [AND]

    Destinations that generate faults related to known sequences SHOULD transmit those faults.

    [AND]

    If transmitted, faults MUST be transmitted to the same [destination] as Acknowledgement messages

    [AND]

    Entities that generate WS-ReliableMessaging faults MUST include as the [action] property the default fault action IRI: http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The simulated HFS sender has created a sequence with an offer element. The simulated HFS sender and the HFS receiver under test are in the "Created" sequence state. The simulated HFS sender is able to change the message number of its sequence message. | | | +| Test procedure |
    1. 1. The simulated HFS sender sends a sequence message with a MessageNumber=1
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The HFS receiver under test responds with its sequence message and may include a SequenceAcknowledgement header block.
    2. 3. The simulated HFS sender transmits a sequence message with a message number outside the range (bigger than 9,223,372,036,854,775,807 or its internal limitation).
    3. 4. The HFS receiver generates a message number rollover fault. It is recommended that the fault is transmitted to the HFS sender.
    4. 5. If the fault is transmitted by the HFS receiver under test, that message includes the following properties:
      • wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.
      • Code = HFS Sender
      • Subcode = MessageNumberRollover
      • Reason = The maximum value for wsrm:MessageNumber has been exceeded
      • Detail = <wsrm:Identifier ...> xs:anyURI </wsrm:Identifier>
                          <wsrm:MaxMessageNumber> wsrm:MessageNumberType
                          </wsrm:MaxMessageNumber>
    5. 6. The simulated HFS sender retransmits its undelivered messages.
    6. 7. The HFS receiver should accept undelivered messages until the sequence is closed or terminated.
    7. 8. The simulated HFS sender closes the sequence.
    | +| Pass/Fail criteria | All elements are as specified in step 5 and steps 2, 4 and 7 must be as indicated. | +| Notes | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------|-------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-013 | | | | +| TP label | Sequence Closed Fault | | | | +| Coverage | Spec | [OASIS WS-I RM] | | | +| | Testable items | SeqClosedFault 1; M | SeqClosedFault 2; M | Faults 1; R | +| | | Faults 2; M | Faults 3; M | | +| Test purpose |

    Check that:

    SequenceClosed fault MUST be generated by an RM Destination when it is asked to accept a message for a Sequence that is closed

    [AND]

    SequenceClosed properties:

    [Code] HFS Sender

    [Subcode] wsrm:SequenceClosed

    [Reason] The Sequence is closed and cannot accept new messages.

    [Detail] <wsrm:Identifier...> xs:anyURI </wsrm:Identifier>

    [AND]

    Destinations that generate faults related to known sequences SHOULD transmit those faults.

    [AND]

    If transmitted, faults MUST be transmitted to the same [destination] as Acknowledgement messages

    [AND]

    Entities that generate WS-ReliableMessaging faults MUST include as the [action] property the default fault action IRI: http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.

    | | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | | +| Other PICS | | | | | +| Initial condition |

    The simulated HFS sender has created a sequence with an offer element. The simulated HFS sender and HFS receiver under test are in the "Created" sequence state. The simulated

    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | HFS sender is able to send a sequence message as long as the sequence has not yet been closed. | +| Test procedure |
    1. 1. The simulated HFS sender sends a sequence to the HFS receiver under test with MessageNumber=1 and indicating that it is the last one.
    2. 2. The HFS receiver responds with a SequenceAcknowledgement with an AcknowledgementRange Lower=1 Upper=1, and a sequence message
    3. 3. The simulated HFS sender sends a CloseSequence.
    4. 4. The HFS receiver responds with CloseSequenceResponse.
    5. 5. The simulated HFS sender transmits a sequence with a message number within the range, for example, MessageNumber=2.
    6. 6. The HFS receiver generates a SequenceClosed fault. It is recommended that the fault is transmitted to the HFS sender.
    7. 7. If the fault is transmitted by the HFS receiver under test, that message includes the following properties:
      • wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.
      • Code = HFS Sender
      • Subcode = SequenceClosed
      • Reason = The Sequence is closed and cannot accept new messages
      • Detail = <wsrm:Identifier ...> xs:anyURI </wsrm:Identifier>
    | +| Pass/Fail criteria | All elements are as specified in step 7. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------| +| TP Id | TP/HFS/REC/WSI/RM/BV-014 | | | +| TP label | WSRM Required Fault | | | +| Coverage | Spec | [OASIS WS-I RM] | | +| | Testable items | WSRMReq 1; C | WSRMReq 2; M | +| | | Faults 2; M | Faults 3; M | +| Test purpose |

    Check that:

    If an RM Destination requires the use of WS-RM, WSRMRequired fault is generated when it Receives an incoming message that did not use this protocol.

    [AND]

    WSRM Required properties:

    [Code] HFS Sender

    [Subcode] wsrm:WSRMRequired

    [Reason] The RM Destination requires the use of WSRM

    [Detail] xs:any

    [AND]

    Destinations that generate faults related to known sequences SHOULD transmit those faults.

    [AND]

    If transmitted, faults MUST be transmitted to the same [destination] as Acknowledgement messages

    [AND]

    Entities that generate WS-ReliableMessaging faults MUST include as the [action] property the default fault action IRI: http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.

    | | | +| Applicability | C_REC_000 AND C_REC_WSI_034 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The simulated HFS sender and the HFS receiver under test are in the "None" sequence state. The simulated HFS sender is able to send a message without using WSRM protocol. | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated HFS sender transmits a SOAP message without using any element of the WSRM protocol.
    2. 2. The HFS receiver generates a WSRMRequired fault. It is recommended that the fault is transmitted to the HFS sender.
    3. 3. If the fault is transmitted by the HFS receiver under test, that message includes the following properties:
      • wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/fault.
      • Code = HFS Sender
      • Subcode = WSRMRequired
      • Reason = The RM Destination requires the use of WSRM
      • Detail = xs:any
    | +| Pass/Fail criteria | All elements are as specified in step 3. | +| Notes | | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0. (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin" *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003), *ETSI drafting rules*. + +- [b-HFSR PICS & PIXIT] Services HFS Receiver DG2016 PICS and PIXIT excel sheet v1.7 + +- [b-HFSS PICS & PIXIT] Services HFS Sender DG2016 PICS and PIXIT excel sheet v1.7 + +- [b-SOAP 1.2] W3C SOAP 1.2 (2007), *SOAP Version 1.2 (Second Edition)*. + +- [b-XML Schema Part 1] W3C Recommendation (2004), *XML Schema Part 1: Structures (Second Edition)*. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.830.3-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.830.3-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca0dce65df64f4fb10a81b8f87284f793e4b1d3d --- /dev/null +++ b/marked/H/T-REC-H.830.3-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e92e387e62cb6d86114f61d012b89bb4f66ab5171494a2177d9dfd36f6a2a566 +size 4206 diff --git a/marked/H/T-REC-H.830.3-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.830.3-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..72ff11554d0454acfde76c47431b089c5c6a20a9 --- /dev/null +++ b/marked/H/T-REC-H.830.3-201704-I_PDF-E/raw.md @@ -0,0 +1,1260 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.830.3** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Services interface Part 3: SOAP/ATNA: +Health & Fitness Service sender** + +Recommendation ITU-T H.830.3 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.830.3 + +# Conformance of ITU-T H.810 personal health system: Services interface Part 3: SOAP/ATNA: Health & Fitness Service sender + +## Summary + +Recommendation ITU-T H.830.3 provides a test suite structure (TSS) and the test purposes (TP) for SOAP/ATNA messages through the Health & Fitness Service (HFS) sender in the Services interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.830.3 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 3: SOAP/ATNA. HFS Sender (Version 1.8, 2017-03-14), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.833 | 2015-01-13 | 16 | 11.1002/1000/12251 | +| 1.0 | ITU-T H.830.3 | 2015-01-13 | 16 | 11.1002/1000/12589 | +| 2.0 | ITU-T H.830.3 | 2016-07-14 | 16 | 11.1002/1000/12923 | +| 3.0 | ITU-T H.830.3 | 2017-04-13 | 16 | 11.1002/1000/13203 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, personal connected health devices, Services interface, SOAP/ATNA: Health & Fitness Service sender. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Test suite structure (TSS) ..... | 5 | +| 7 Electronic attachment ..... | 7 | +| Annex A Test purposes ..... | 8 | +| A.1 TP definition conventions..... | 8 | +| A.2 Subgroup 1.2.1: SOAP headers (HEAD) ..... | 9 | +| A.3 Subgroup 1.3.1: ATNA general (GEN)..... | 9 | +| A.4 Subgroup 1.3.2: ATNA PCD-01 (PCD-01) ..... | 10 | +| A.5 Subgroup 1.3.3: ATNA consent management (CM)..... | 17 | +| Annex B Schema for IETF RFC 3881 verification..... | 21 | +| Bibliography..... | 28 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 3: SOAP/ATNA. HFS Sender (Version 1.8, 2017-03-14), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.3 | 2012-10-05 | Initial release for Test Tool DG2011. It uses "TSS&TP_1.5_WAN_PART_3_(SEN GEN)_v1.2.doc" as a baseline and adds new features included in [b-CDG 2011]. | +| 1.4 | 2013-05-24 | Initial release for Test Tool DG2012. It uses "TSS&TP_DG2011_WAN_PART_3_(SEN GEN)_v1.3.doc" as a baseline and fixes a typo error in ATNA Reliable Syslog Test Cases. It does not include technical changes in the test procedures because new features included in [b-CDG 2012] do not affect the test procedures specified in this document. | +| 1.4 | 2014-01-24 | Initial release for Test Tool DG2013. It is the same version as "TSS&TP_DG2012_WAN_PART_3_(SEN GEN)_v1.4.doc" because new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013] do not affect the test procedures specified in this document. | +| 1.5 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_WAN_PART_3_(SEN GEN)_v1.5.doc" as a baseline and adds new features included in Documentation Enhancements:
    • "Other PICS" row has been added
    | +| 1.6 | 2015-07-01 | Initial release for Test Tool DG2015:
    • Test suite structure modified
    • Applicability and Other PICS modified due to the inclusion of hData OU
    | +| 1.7 | 2016-09-20 | Initial release for Test Tool DG2016. It implements changes according to [ITU-T H.810 (2016)]/[b-CDG 2016] (Iris + Errata) refreshments. | +| 1.8 | 2017-03-14 | Editorial: added insulin pump and continuous glucose monitor specializations to the TSS list in clause 6. | + +## Recommendation ITU-T H.830.3 + +## Conformance of ITU-T H.810 personal health system: Services interface Part 3: SOAP/ATNA: Health & Fitness Service sender + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Services interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Services interface have been divided into the parts specified below. This Recommendation covers Part 3. + +- Part 1: Web services interoperability Health & Fitness Service sender +- Part 2: Web services interoperability Health & Fitness Service receiver +- **Part 3: SOAP/ATNA. Health & Fitness Service sender** +- Part 4: SOAP/ATNA. Health & Fitness Service receiver +- Part 5: PCD-01 HL7 Messages. Health & Fitness Service sender +- Part 6: PCD-01 HL7 Messages. Health & Fitness Service receiver +- Part 7: Consent Management. Health & Fitness Service sender +- Part 8: Consent Management. Health & Fitness Service receiver +- Part 9: hData Observation Upload. Health & Fitness Service sender +- Part 10: hData Observation Upload. Health & Fitness Service receiver +- Part 11: Questionnaires. Health & Fitness Service sender +- Part 12: Questionnaires. Health & Fitness Service receiver + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)]            Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [ITU-T H.812]                    Recommendation ITU-T H.812 (2016), *Interoperability design guidelines for personal health systems: Services interface: Common certified capability class*. + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A + +- [ITU-T H.812.1] Recommendation ITU-T H.812.1 (2016), *Interoperability design guidelines for personal health systems: Services interface: Observation upload certified capability class.* +- [ITU-T H.812.2] Recommendation ITU-T H.812.2 (2016), *Interoperability design guidelines for personal health systems: Services interface: Questionnaires certified capability class.* +- [ITU-T H.812.3] Recommendation ITU-T H.812.3 (2016), *Interoperability design guidelines for personal health systems: Services interface: Capability exchange certified capability class.* +- [ITU-T H.812.4] Recommendation ITU-T H.812.4 (2016), *Interoperability design guidelines for personal health systems: Services interface: Authenticated persistent session certified capability class.* +- [IETF RFC 3195] IETF RFC 3195 (2001), *Reliable Delivery for syslog.* +- [IETF RFC 3881] IETF RFC 3881 (2004), *Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications.* +- [IHE ITI TF-2] IHE ITI TF 2 (2010), *IHE IT Infrastructure Technical Framework, Volume 2 (ITI TF-2), Revision 7.0.* It comprises three sub-volumes: 2a (Transactions Part A), 2b (Transactions Part B) and 2x (Appendices). +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_TF\\_Rev7-0\\_Vol2a\\_FT\\_2010-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2a_FT_2010-08-10.pdf) +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_TF\\_Rev7-0\\_Vol2b\\_FT\\_2010-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2b_FT_2010-08-10.pdf) +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_TF\\_Rev7-0\\_Vol2x\\_FT\\_2010-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2x_FT_2010-08-10.pdf) + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------| +| ATNA | Audit Trail and Node Authentication | +| ATS | Abstract Test Suite | +| DUT | Device Under Test | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| GUI | Graphical User Interface | +| HFS | Health & Fitness Service | +| HFSS | Health & Fitness Service Sender | + +| | | +|-------|-------------------------------------------------------| +| HFSR | Health & Fitness Service Receiver | +| HL7 | Health Level 7 | +| HTTP | Hypertext Transfer Protocol | +| HTTPS | Hypertext Transfer Protocol Secure | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| NFC | Near Field Communication | +| MDS | Medical Device System | +| PCD | Patient Care Device | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TLS | Transport Level Security | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WAN | Wide Area Network | +| WDM | Windows Driver Model | +| WS | Web Service | +| WSDL | Web Service Description Language | +| XML | extensible Markup Language | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. + +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|-------------|---------------|---------|------------------------------------------------|-------------| +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Services interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 1.2 and 1.3 (shown in bold): + +- Group 1: HFS sender (HFSS) + - Group 1.1: Web services interoperability (WSI) + - Subgroup 1.1.1: Basic profile (BP) + - Subgroup 1.1.2: Basic security profile (BSP) + - Subgroup 1.1.3: Reliable messaging (RM) + - **Group 1.2: Simple object access protocol (SOAP)** + - **Subgroup 1.2.1: SOAP headers (HEAD)** + - **Group 1.3: Audit trail and node authentication (ATNA)** + - **Subgroup 1.3.1: General (GEN)** + - **Subgroup 1.3.2: PCD-01 (PCD-01)** + - **Subgroup 1.3.3: Consent Management (CM)** + - Group 1.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 1.4.1: General (GEN) + - Subgroup 1.4.2: Design guidelines (DG) + - Subgroup 1.4.3: Pulse oximeter (PO) + - Subgroup 1.4.4: Blood pressure monitor (BPM) + - Subgroup 1.4.5: Thermometer (TH) + - Subgroup 1.4.6: Weighing scales (WEG) + - Subgroup 1.4.7: Glucose meter (GL) + - Subgroup 1.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 1.4.9: Strength fitness equipment (ST) + - Subgroup 1.4.10: Independent living activity hub (HUB) + - Subgroup 1.4.11: Adherence monitor (AM) + - Subgroup 1.4.12: Peak expiratory flow monitor (PF) + - Subgroup 1.4.13: Body composition analyser (BCA) + - Subgroup 1.4.14: Basic electrocardiograph (ECG) + - Subgroup 1.4.15: International normalized ratio (INR) + - Subgroup 1.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.4.17: Insulin pump (IP) + - Subgroup 1.4.18: Continuous glucose monitor (CGM) + - Group 1.5: Consent Management (CM) + - Subgroup 1.5.1: HFS XDR transaction (TRANS) + +- Subgroup 1.5.2: HFS metadata validation (META) +- Subgroup 1.5.3: HFS consent directive validation (CDV) +- Group 1.6: hData Observation Upload (HDATA) + - Subgroup 1.6.1: General (GEN) +- Group 1.7: Questionnaires (QUE) + - Subgroup 1.7.1: General (GEN) + - Subgroup 1.7.2: CDA validation (CDA) + +### – Group 2: HFS receiver (HFSR) + +- Group 2.1: Web service interoperability (WSI) + - Subgroup 2.1.1: Basic profile (BP) + - Subgroup 2.1.2: Basic security profile (BSP) + - Subgroup 2.1.3: Reliable messaging (RM) +- Group 2.2: SOAP (SOAP) + - Subgroup 2.2.1: SOAP headers (HEAD) +- Group 2.3: Audit (ATNA) + - Subgroup 2.3.1: General (GEN) + - Subgroup 2.3.2: PCD-01 (PCD-01) + - Subgroup 2.3.3: Consent Management (CM) +- Group 2.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 2.4.1: General (GEN) + - Subgroup 2.4.2: Design guidelines (DG) + - Subgroup 2.4.3: Pulse oximeter (PO) + - Subgroup 2.4.4: Blood pressure monitor (BPM) + - Subgroup 2.4.5: Thermometer (TH) + - Subgroup 2.4.6: Weighing scales (WEG) + - Subgroup 2.4.7: Glucose meter (GL) + - Subgroup 2.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 2.4.9: Strength fitness equipment (ST) + - Subgroup 2.4.10: Independent living activity hub (HUB) + - Subgroup 2.4.11: Adherence monitor (AM) + - Subgroup 2.4.12: Peak expiratory flow monitor (PF) + - Subgroup 2.4.13: Body composition analyser (BCA) + - Subgroup 2.4.14: Basic electrocardiograph (ECG) + - Subgroup 2.4.15: International normalized ratio (INR) + - Subgroup 2.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.4.17: Insulin pump (IP) + - Subgroup 2.4.18: Continuous glucose monitor (CGM) +- Group 2.5: Consent Management (CM) + - Subgroup 2.5.1: HFS XDR transaction (TRANS) + - Subgroup 2.5.2: HFS service validation (SER) +- Group 2.6: hData Observation Upload (HDATA) + +- Subgroup 2.6.1: General (GEN) +- Subgroup 2.6.2: hData record format (HRF) +- Group 2.7: Questionnaires (QUE) + - Subgroup 2.7.1: General (GEN) + - Subgroup 2.7.2: CDA validation (CDA) + - Subgroup 2.7.3: hData record format (HRF) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - HFS: Health & Fitness Services Interface + - : This is the device under test. + - SEN: HFS sender + - REC: HFS receiver + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 1.2.1: SOAP headers (HEAD) + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|---------------| +| TP Id | TP/HFS/SEN/SOAP/HEAD/BV-001 | | | +| TP label | Requirements for Transactions which do not use HL7 V3 Messages | | | +| Coverage | Spec | [IHE ITI TF-2], Volume 2x, Appendix V | | +| | Testable items | IHE-WSA101; M | IHE-WSA102; M | +| Test purpose | Check that:
    All elements shall have the mustUnderstand attribute set (mustUnderstand='1')
    [AND]
    The element of the initiating message shall be present and shall have the mustUnderstand attribute set (mustUnderstand='1'). | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The simulated HFS receiver has published a WebService that allows a TLS v1.0 connection and supports SAML 2.0 as an authentication token only and the HFS sender under test is ready to send a SOAP message. | | | +| Test procedure |
    1. The HFS sender under test sends a SOAP message to the HFS receiver using addressing header blocks.
    2. Check that:
      • All <wsa:Action> elements have the mustUnderstand attribute set (mustUnderstand='1' or 'true').
      • The <wsa:ReplyTo> element of the initiating message shall be present and shall have the mustUnderstand attribute set (mustUnderstand='1').
    | | | +| Pass/Fail criteria | All elements are as specified in step 2. | | | +| Notes | | | | + +## A.3 Subgroup 1.3.1: ATNA general (GEN) + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--| +| TP Id | TP/HFS/SEN/ATNA/GEN/BV-006 | | | +| TP label | Reliable Syslog ATNA Actor behaviour | | | +| Coverage | Spec | [IHE ITI TF-2] | | +| | Testable items | Audit_MT-1; M | | +| Test purpose | Check that:
    If Audit Record repository is not available, the HFS actor shall store the Audit Record in a local buffer until the Audit Record Repository is available again | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_001 AND C_SEN_ATNA_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has a WebService enabled for PCD-01 message reception; if needed, another WebService is enabled for consent document reception; the simulated audit repository with reliable syslog transport is intentionally disabled; and the HFS sender under test is shutdown. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The HFS sender application under test is started and it sends the corresponding audit record message to the audit repository. Since the simulated audit repository receiver is disabled, the message will not be delivered.
    2. 2. Wait for one minute.
    3. 3. The test tool starts the simulated audit repository.
    4. 4. Force the HFS sender under test to send a SOAP message (PCD-01 message, consent document or both).
    5. 5. The test tool receives the SOAP messages and the audit record messages sent by HFS sender under test.
    | +| Pass/Fail criteria |
    • • At least 2 audit record messages must be received by the simulated audit repository, one for the HFS sender start action (step 1) and another for the SOAP message sent in step 4.
    • • There is at least one audit record with attribute "code" of the element EventID set to "110106" (PHI-export) and the EventDateTime attribute of the EventIdentification element is set to the expedition time of the SOAP message sent in step 4.
    • • There is one audit record with attribute "code" of the element EventID set to "110120" (start action) and the EventDateTime attribute of the EventIdentification element is set to at least one minute before the expedition time of the SOAP message sent in step 4.
    | +| Notes | In step 4 the way to force the WAN sender to send the pendant audit record that was not delivered in step 1, depends on the vendor implementation. A typical strategy could be to send another WAN message and its corresponding ATNA record. In this way, when the HFS sender under test sends the ATNA record PHI-export then it would send the pendant audit record along with the newer one. | + +## A.4 Subgroup 1.3.2: ATNA PCD-01 (PCD-01) + +| | | | | | +|-----------------|-------------------------------------------|--------------------|------------------|-----------------| +| TP Id | TP/HFS/SEN/ATNA/PCD-01/BV-000 | | | | +| TP label | PCD-01 – Reliable Syslog ATNA Actor Start | | | | +| Coverage | Spec | [IHE ITI TF-2] | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-1; M | Audit_RF-1; M | +| | | Rel_Syslog-1; M | Rel_Syslog-2; M | | +| | Spec | [ITU-T H.812] | | | +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------|----------------| +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | +| Test purpose | Check that:
    When SUT starts the application then audit log start message is received from the SUT and it is conformant to the ATNA specifications | | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_001 AND C_SEN_ATNA_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has a WebService enabled for PCD-01 message reception and a simulated audit repository with reliable syslog transport is running. The WAN sender under test is shutdown. | | | | +| Test procedure | 1. The WAN sender application under test is started and it sends the corresponding audit record message to the audit repository.
    2. The audit repository receives the audit record message and verifies that:
    • a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA
    • b. It conforms to reliable syslog's cooked profile [IETF RFC 3195]
    | | | | +| Pass/Fail criteria |
    • • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • • In the audit record, the attribute "code" of the element EventID is set to "110120" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • • The received audit message conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    | | | | +| Notes | | | | | + +| | | | | | +|-----------------|--------------------------------------|--------------------|------------------|-----------------| +| TP Id | TP/HFS/SEN/ATNA/PCD-01/BV-001 | | | | +| TP label | PCD-01 – BSD Syslog ATNA Actor Start | | | | +| Coverage | Spec | [IHE ITI TF-2] | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-1; M | Audit_RF-1; M | +| | | BSD_Syslog-1; O | BSD_Syslog-2; M | BSD_Syslog-3; M | +| | | BSD_Syslog-4; M | BSD_Syslog-5; R | BSD_Syslog-6; O | +| | Spec | [ITU-T H.812] | | | +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------|----------------| +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | +| Test purpose | Check that:
    When SUT starts the application then audit log start message is received from the SUT and it is conformant to the ATNA specifications | | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_001 AND C_SEN_ATNA_002 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has a WebService enabled for PCD-01 message reception and a simulated audit repository with BSD syslog transport is running. The HFS sender under test is shutdown. | | | | +| Test procedure | 1. The HFS sender application under test is started and it sends the corresponding audit record message to the audit repository.
    2. The audit repository receives the audit record message and verifies that it conforms to BSD syslog [b-IETF RFC 3164]. | | | | +| Pass/Fail criteria |
    • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • In the audit record, the attribute "code" of the element EventID is set to "110120" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • The received audit message conforms to BSD syslog [b-IETF RFC 3164].
    | | | | +| Notes | | | | | + +| | | | | | +|-----------------|------------------------------------------------|--------------------|-------------------|-----------------| +| TP Id | TP/HFS/SEN/ATNA/PCD-01/BV-002 | | | | +| TP label | PCD-01 – Reliable Syslog ATNA Actor PHI-export | | | | +| Coverage | Spec | [IHE ITI TF-2] | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-15; M | Audit_RF-1; M | +| | | Rel_Syslog-1; M | Rel_Syslog-2; M | | +| | Spec | [ITU-T H.812] | | | +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------|----------------| +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | +| Test purpose | Check that:
    When SUT sends a PCD-01 ORU message, then an audit log PHI-export message is received from the SUT and it is conformant to the ATNA specifications | | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_001 AND C_SEN_ATNA_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has a WebService enabled for PCD-01 message reception and a simulated audit repository with reliable syslog transport is running. The HFS sender under test has a PCD-01 message ready to be sent. | | | | +| Test procedure |
    1. 1. The HFS sender application under test sends a PCD-01 message to the simulated HFS receiver and the corresponding audit record message to the audit repository.
    2. 2. The simulated HFS receiver receives the PCD-01 message.
    3. 3. The audit repository receives the audit record message and verifies that:
      1. a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA
      2. b. It conforms to the reliable syslog's cooked profile [IETF RFC 3195]
    | | | | +| Pass/Fail criteria |
    • • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • • In the audit record, the attribute "code" of the element EventID is set to "110106" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • • In the audit record, the value of the attribute EventDateTime of the element EventIdentification is inside a one minute interval of the Date and Time indicated in the MSH-7 field of the received PCD-01 message.
    • • The received audit message conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    | | | | +| Notes | | | | | + +| | | | | | +|-----------------|-------------------------------------------|-----------------|-------------------|-----------------| +| TP Id | TP/HFS/SEN/ATNA/PCD-01/BV-003 | | | | +| TP label | PCD-01 – BSD Syslog ATNA Actor PHI-export | | | | +| Coverage | Spec | [IHE ITI TF-2] | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-15; M | Audit_RF-1; M | +| | | BSD_Syslog-1; O | BSD_Syslog-2; M | BSD_Syslog-3; M | +| | | BSD_Syslog-4; M | BSD_Syslog-5; R | BSD_Syslog-6; O | + +| | | | | | +|---------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------| +| | Spec | [ITU-T H.812] | | | +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| SAAAM-DD-13; O | | SAAAM-DD-14; M | SAAAM-DD-15; O | | +| SAAAM-DD-16; O | | SAAAM-DD-17; O | SAAAM-DD-18; O | | +| SAAAM-DD-19; M | | SAAAM-DD-20; O | SAAAM-DD-21; M | | +| Test purpose | | Check that:
    When SUT sends a PCD-01 ORU message, then an audit log PHI-export message is received from the SUT and it is conformant to the ATNA specifications | | | +| Applicability | | C_SEN_000 AND C_ C_SEN_GEN_001 AND SEN_ATNA_002 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has a WebService enabled for PCD-01 message reception and a simulated audit repository with BSD syslog transport is running. The HFS sender under test has a PCD-01 message ready to be sent. | | | +| Test procedure | | 1. The HFS sender application under test sends a PCD-01 message to the simulated HFS receiver and the corresponding audit record message to the audit repository.
    2. The simulated HFS receiver receives the PCD-01 message.
    3. The audit repository receives the audit record message and verifies that it conforms to BSD syslog [b-IETF RFC 3164]. | | | +| Pass/Fail criteria | |
    • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • In the audit record, the attribute "code" of the element EventID is set to "110106" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • In the audit record, the value of the attribute EventDateTime of the element EventIdentification is inside a one minute interval of the Date and Time indicated in the MSH-7 field of the received PCD-01 message.
    • The received audit message conforms to the BSD syslog [b-IETF RFC 3164].
    | | | +| Notes | | | | | + +| | | | | | +|-----------------|------------------------------------------|----------------|----------------|---------------| +| TP Id | TP/HFS/SEN/ATNA/PCD-01/BV-004 | | | | +| TP label | PCD-01 – Reliable Syslog ATNA Actor Stop | | | | +| Coverage | Spec | [IHE ITI TF-2] | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | + +| | | | | | +|---------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------| +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-1; M | Audit_RF-1; M | +| | | Rel_Syslog-1; M | Rel_Syslog-2; M | | +| | Spec | [ITU-T H.812] | | | +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | +| Test purpose | |

    Check that:

    When SUT stops the application then audit log stop message is received from the SUT and it is conformant to the ATNA specifications

    | | | +| Applicability | | C_SEN_000 AND C_SEN_GEN_001 AND C_SEN_ATNA_001 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has a WebService enabled for PCD-01 message reception and a simulated audit repository with reliable syslog transport is running. The HFS sender under test is running. | | | +| Test procedure | |
    1. 1. The HFS sender application under test shuts down the application and sends the corresponding audit record message to the audit repository.
    2. 2. The audit repository receives the audit record message and verifies that:
      1. a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA
      2. b. It conforms to the reliable syslog's cooked profile [IETF RFC 3195]
    | | | +| Pass/Fail criteria | |
    • • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • • In the audit record, the attribute "code" of the element EventID is set to "110121" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • • The received audit message conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    | | | +| Notes | | | | | + +| | | +|-----------------|-------------------------------------| +| TP Id | TP/HFS/SEN/ATNA/PCD-01/BV-005 | +| TP label | PCD-01 – BSD Syslog ATNA Actor Stop | + +| | | | | | | +|---------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------|--| +| Coverage | Spec | [IHE ITI TF-2] | | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | | +| | | DirectCert-3; M | Trigg_Event-1; M | Audit_RF-1; M | | +| | | BSD_Syslog-1; O | BSD_Syslog-2; M | BSD_Syslog-3; M | | +| | | BSD_Syslog-4; M | BSD_Syslog-5; R | BSD_Syslog-6; O | | +| | Spec | [ITU-T H.812] | | | | +| | Testable items | SecGuidelines 3; O | | | | +| | Spec | [IETF RFC 3881] | | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | | +| Test purpose | | Check that:
    When SUT stops the application then audit log stop message is received from the SUT and it is conformant to the ATNA specifications | | | | +| Applicability | | C_SEN_000 AND C_SEN_GEN_001 AND C_SEN_ATNA_002 | | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | | The simulated HFS receiver has a WebService enabled for PCD-01 message reception and a simulated audit repository with BSD syslog transport is running. The HFS sender under test is running. | | | | +| Test procedure | |
    1. The HFS sender application under test shuts down the application and sends the corresponding audit record message to the audit repository.
    2. Audit repository receives the Audit Record Message and verifies that it conforms to BSD syslog [b-RFC 3164].
    | | | | +| Pass/Fail criteria | |
    • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • In the audit record, the attribute "code" of the element EventID is set to "110121" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • The received audit message conforms to BSD Syslog [b-IETF RFC 3164].
    | | | | +| Notes | | | | | | + +## A.5 Subgroup 1.3.3: ATNA consent management (CM) + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------|-----------------| +| TP Id | TP/HFS/SEN/ATNA/CM/BV-000 | | | | +| TP label | CM – Reliable Syslog ATNA Actor PHI-Export | | | | +| Coverage | Spec | [IHE ITI TF-2], Volume 2a | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-15; M | Audit_RF-1; M | +| | | Rel_Syslog-1; M | Rel_Syslog-2; M | | +| | Spec | [IHE ITI TF-2], Volume 2b | | | +| | Testable items | ProvideAudit1; O | | | +| | | | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | +| | | | | | +| Test purpose |

    Check that:

    When SUT sends a Consent Document, then an audit log PHI-export message is received from the SUT and it is conformant to the ATNA specifications

    | | | | +| Applicability | C_SEN_000 AND C_SEN_GEN_001 AND C_SEN_ATNA_001 AND C_SEN_GEN_002 AND C_SEN_GEN_003 | | | | +| Other PICS | | | | | +| Initial condition |

    The simulated HFS receiver has a WebService enabled for PCD-01 message and consent document reception and a simulated audit repository with reliable syslog transport is running. The HFS sender under test has a consent document ready to be sent.

    | | | | +| Test procedure |
    1. 1. The HFS sender application under test sends a consent document and the corresponding audit record message to the audit repository.
    2. 2. The audit repository receives the audit record message and verifies that:
      1. a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA
      2. b. It conforms to the reliable syslog's cooked profile [IETF RFC 3195]
    3. 3. The audit record includes the following elements:
      1. a. EventIdentification element that contains:
        • the "EventActionCode" attribute set to "R"
        • the EventID sub-element with attributes "code" set to "110106" and
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    "displayName" set to "Export"

    • the EventTypeCode sub-element with attributes "code" set to "ITI-41", "displayName" set to "Provide and Register Document Set-b" and "codeSystemName" set to "IHE Transactions"

    b. An ActiveParticipant element that contains:

    • the "UserIsRequestor" attribute set to "true"
    • the "NetworkAccessPointTypeCode" attribute set to "1" or "2"
    • the "AlternativeUserID" attribute is present
    • the RoleIDCode sub-element with attributes "code" set to "110153" and "displayName" set to "Source"

    c. An ActiveParticipant element that contains:

    • the "UserIsRequestor" attribute set to "false"
    • the "NetworkAccessPointTypeCode" attribute set to "1" or "2"
    • the RoleIDCode sub-element with attributes "code" set to "110152" and "displayName" set to "Destination"

    d. A ParticipantObjectIdentification element that contains:

    • the "ParticipantObjectID" attribute is present and not empty
    • the "ParticipantObjectTypeCode" attribute set to "1"
    • the "ParticipantObjectTypeCodeRole" attribute set to "1"
    • the ParticipantObjectIDTypeCode sub-element with attributes "code" set to "2", "displayName" set to "Patient Number" and "codeSystemName" set to "RFC-3881"

    e. A ParticipantObjectIdentification element that contains:

    • the "ParticipantObjectID" attribute is present and not empty
    • the "ParticipantObjectTypeCode" attribute set to "2"
    • the "ParticipantObjectTypeCodeRole" attribute set to "20"
    • the ParticipantObjectIDTypeCode sub-element with attributes "code" set to "urn:uuid:a54d6aa5-d40d-43f9-88c5-b4633d873bdd", "displayName" set to "submission set classificationNode" and "codeSystemName" set to "IHE XDS Metadata"
    | +| Pass/Fail criteria |
    • • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • • The audit record content is according to values described in step 4.
    • • The received audit message conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    | +| Notes | | + +| | | | | | +|-----------------|---------------------------------------|---------------------------|-------------------|-----------------| +| TP Id | TP/HFS/SEN/ATNA/CM/BV-001 | | | | +| TP label | CM – BSD Syslog ATNA Actor PHI-Export | | | | +| Coverage | Spec | [IHE ITI TF-2], Volume 2a | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-15; M | Audit_RF-1; M | +| | | BSD_Syslog-1; O | BSD_Syslog-2; M | BSD_Syslog-3; M | + +| | | | | | | +|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|--| +| | | BSD_Syslog-4; M | BSD_Syslog-5; R | BSD_Syslog-6; O | | +| | Spec | [IHE ITI TF-2], Volume 2b | | | | +| | Testable items | ProvideAudit1; O | | | | +| | Spec | [IETF RFC 3881] | | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | | +| | | | | | | +| Test purpose | |

    Check that:

    When SUT sends a Consent Document, then an audit log PHI-export message is received from the SUT and it is conformant to the ATNA specifications

    | | | | +| Applicability | | C_SEN_000 AND C_SEN_GEN_001 AND C_SEN_ATNA_002 AND C_SEN_GEN_002 AND C_SEN_GEN_003 | | | | +| Other PICS | | | | | | +| Initial condition | |

    The simulated HFS receiver has a WebService enabled for PCD-01 message and consent document reception and a simulated audit repository with BSD syslog transport is running. The HFS sender under test has a consent document ready to be sent.

    | | | | +| Test procedure | |
    1. 1. The HFS sender application under test sends a consent document and the corresponding audit record message to the audit repository.
    2. 2. The audit repository receives the audit record message and verifies that it conforms to BSD syslog [b-IETF RFC 3164].
    3. 3. The audit record includes the following elements:
      1. a. the EventIdentification element that contains:
        • the "EventActionCode" attribute set to "R"
        • the EventID sub-element with attributes "code" set to "110106" and "displayName" set to "Export"
        • the EventTypeCode sub-element with attributes "code" set to "ITI-41", "displayName" set to "Provide and Register Document Set-b" and "codeSystemName" set to "IHE Transactions"
      2. b. An ActiveParticipant element that contains:
        • the "UserIsRequestor" attribute set to "true"
        • the "NetworkAccessPointTypeCode" attribute set to "1" or "2"
        • the "AlternativeUserID" attribute is present
        • the RoleIDCode sub-element with attributes "code" set to "110153" and "displayName" set to "Source"
      3. c. An ActiveParticipant element that contains:
        • the "UserIsRequestor" attribute set to "false"
        • the "NetworkAccessPointTypeCode" attribute set to "1" or "2"
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • the RoleIDCode sub-element with attributes "code" set to "110152" and "displayName" set to "Destination"
    1. d. A ParticipantObjectIdentification element that contains:
      • the "ParticipantObjectID" attribute is present and not empty
      • the "ParticipantObjectTypeCode" attribute set to "1"
      • the "ParticipantObjectTypeCodeRole" attribute set to "1"
      • the ParticipantObjectIDTypeCode sub-element with attributes "code" set to "2", "displayName" set to "Patient Number" and "codeSystemName" set to "RFC-3881"
    2. e. A ParticipantObjectIdentification element that contains:
      • the "ParticipantObjectID" attribute is present and not empty
      • the "ParticipantObjectTypeCode" attribute set to "2"
      • the "ParticipantObjectTypeCodeRole" attribute set to "20"
      • the ParticipantObjectIDTypeCode sub-element with attributes "code" set to "urn:uuid:a54d6aa5-d40d-43f9-88c5-b4633d873bdd", "displayName" set to "submission set classificationNode" and "codeSystemName" set to "IHE XDS Metadata"
    | +| Pass/Fail criteria |
    • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • The audit record content is according to values described in step 4.
    • The received audit message conforms to the BSD syslog [b-IETF RFC 3164].
    | +| Notes | | + + 20 **Rec. ITU-T H.830.3 (04/2017)** + +# Annex B + +## Schema for IETF RFC 3881 verification + +(This annex forms an integral part of this Recommendation.) + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + Create + + + + + Read + + + + + Update + + + + + Delete + + + + + Execute + + + + + + + +``` + +``` + + + + + + + + + + + + + Success + + + + + Minor failure + + + + + Serious failure + + + + + + Major failure; action made unavailable + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + Machine Name, including DNS name + + + + + + IP Address + + + + + Telephone Number + + + + + + + + + + + + + + + + + + + + + + Person + + + + + System object + + + + + Organization + + + + + Other + + + + + + + + +``` + +``` + + + + + Patient + + + + + Location + + + + + Report + + + + + Resource + + + + + Master file + + + + + User + + + + + List + + + + + Doctor + + + + + Subscriber + + + + + Guarantor + + + + + + Security User Entity + + + + + + Security User Group + + + + +``` + +``` + + + Security Resource + + + + + + Security Granularity Definition + + + + + + Provider + + + + + Report Destination + + + + + Report Library + + + + + Schedule + + + + + Customer + + + + + Job + + + + + Job Stream + + + + + Table + + + + + Routing Criteria + + + + + Query + + + + + + +``` + +``` + + + + + + + + Origination / Creation + + + + + + + Import / Copy from original + + + + + + Amendment + + + + + Verification + + + + + Translation + + + + + Access / Use + + + + + De-identification + + + + + + Aggregation, summarization, derivation + + + + + + Report + + + + + + Export / Copy to target + + + + + + +``` + +``` + + Disclosure + + + + + + Receipt of disclosure + + + + + + Archiving + + + + + Logical deletion + + + + + + Permanent erasure / Physical destruction + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0. (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003), *ETSI drafting rules*. + +- [b-IETF RFC 3164] IETF RFC 3164 (2001), *The BSD Syslog Protocol*. +- [b-HFSR PICS & PIXIT] Services HFS Receiver DG2016 *PICS and PIXIT excel sheet v1.7*. + +- [b-HFSS PICS & PIXIT] Services HFS Sender DG2016 *PICS and PIXIT excel sheet v1.7*. + + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including telecommunication network management and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.830.4-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.830.4-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827609df9ad8667ae079f875841506349f063390 --- /dev/null +++ b/marked/H/T-REC-H.830.4-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d2afb537db9f3588854962a991eb1178220b2bbb8ff3cea6712979a53a864b +size 4107 diff --git a/marked/H/T-REC-H.830.4-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.830.4-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8e706344e718d9bb2b3343bdf0e92995c24df10a --- /dev/null +++ b/marked/H/T-REC-H.830.4-201704-I_PDF-E/raw.md @@ -0,0 +1,1297 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.830.4** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Services interface Part 4: SOAP/ATNA: +Health & Fitness Service receiver** + +Recommendation ITU-T H.830.4 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.830.4 + +# Conformance of ITU-T H.810 personal health system: Services interface Part 4: SOAP/ATNA: Health & Fitness Service receiver + +## Summary + +Recommendation ITU-T H.830.4 provides a test suite structure (TSS) and the test purposes (TP) for SOAP/ATNA messages through the Health & Fitness Service (HFS) receiver in the Services interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.830.4 is the transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 4: SOAP/ATNA. HFS Receiver (Version 1.7, 2017-03-14), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.834 | 2015-01-13 | 16 | 11.1002/1000/12252 | +| 1.0 | ITU-T H.830.4 | 2015-01-13 | 16 | 11.1002/1000/12590 | +| 2.0 | ITU-T H.830.4 | 2016-07-14 | 16 | 11.1002/1000/12924 | +| 3.0 | ITU-T H.830.4 | 2017-04-13 | 16 | 11.1002/1000/13211 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, personal connected health devices, Services interface, SOAP/ATNA, Health & Fitness Service receiver. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Test suite structure (TSS) ..... | 5 | +| 7 Electronic attachment ..... | 7 | +| Annex A Test purposes ..... | 8 | +| A.1 TP definition conventions..... | 8 | +| A.2 Subgroup 2.2.1: SOAP headers (HEAD) ..... | 9 | +| A.3 Subgroup 2.3.1: ATNA general (GEN)..... | 12 | +| A.4 Subgroup 2.3.2: ATNA PCD-01 (PCD-01) ..... | 13 | +| A.5 Subgroup 2.3.3: ATNA consent management (CM)..... | 18 | +| Annex B Schema for IETF RFC 3881 verification..... | 22 | +| Bibliography..... | 29 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 4: SOAP/ATNA. HFS Receiver (Version 1.7, 2017-03-14), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.2 | 2012-10-05 | Initial release for Test Tool DG2011. This uses "TSS&TP_1.5_WAN_PART_4_(REC GEN)_v1.1.doc" as a baseline and adds new features included in [b-CDG 2011]:
    • • Consent management
    | +| 1.3 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_WAN_PART_4_(REC GEN)_v1.2.doc" as a baseline and fixes a typo error in ATNA reliable syslog test cases. It does not include technical changes in test procedures because new features included in [b-CDG 2012] do not affect the test procedures specified in this document. | +| 1.3 | 2014-01-24 | Initial release for Test Tool DG2013. This is the same version as "TSS&TP_DG2012_WAN_PART_4_(REC GEN)_v1.3.doc" because new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013] do not affect the test procedures specified in this document. | +| 1.4 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_WAN_PART_4_(REC GEN)_v1.3.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row has been added
    | +| 1.5 | 2015-07-01 | Initial release for Test Tool DG2015:
    • • Test suite structure modified
    • • Applicability modified due to the inclusion of hData OU
    | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It implements changes according to [ITU-T H.810 (2016)]/[b-CDG 2016] (Iris + Errata) refreshments. | +| 1.7 | 2017-03-14 | Editorial: added insulin pump and continuous glucose monitor specializations to the TSS list in clause 6. | + +## Recommendation ITU-T H.830.4 + +## Conformance of ITU-T H.810 personal health system: Services interface Part 4: SOAP/ATNA: Health & Fitness Service receiver + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Services interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Services interface have been divided into the parts specified below. This Recommendation covers Part 4. + +- Part 1: Web services interoperability. Health & Fitness Service sender +- Part 2: Web services interoperability. Health & Fitness Service receiver +- Part 3: SOAP/ATNA. Health & Fitness Service sender +- **Part 4: SOAP/ATNA. Health & Fitness Service receiver** +- Part 5: PCD-01 HL7 Messages. Health & Fitness Service sender +- Part 6: PCD-01 HL7 Messages. Health & Fitness Service receiver +- Part 7: Consent Management. Health & Fitness Service sender +- Part 8: Consent Management. Health & Fitness Service receiver +- Part 9: hData Observation Upload. Health & Fitness Service sender +- Part 10: hData Observation Upload. Health & Fitness Service receiver +- Part 11: Questionnaires. Health & Fitness Service sender +- Part 12: Questionnaires. Health & Fitness Service receiver + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)]                Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [ITU-T H.812]                        Recommendation ITU-T H.812 (2016), *Interoperability design guidelines for personal health systems: Services interface: Common certified capability class*. + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +| | | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [ITU-T H.812.1] | Recommendation ITU-T H.812.1 (2016), Interoperability design guidelines for personal health systems: Services interface: Observation upload certified capability class. | +| [ITU-T H.812.2] | Recommendation ITU-T H.812.2 (2016), Interoperability design guidelines for personal health systems: Services interface: Questionnaires certified capability class. | +| [ITU-T H.812.3] | Recommendation ITU-T H.812.3 (2016), Interoperability design guidelines for personal health systems: Services interface: Capability exchange certified capability class. | +| [ITU-T H.812.4] | Recommendation ITU-T H.812.4 (2016), Interoperability design guidelines for personal health systems: Services interface: Authenticated persistent session certified capability class. | +| [IETF RFC 3195] | IETF RFC 3195 (2001), Reliable Delivery for syslog.
    https://datatracker.ietf.org/doc/rfc3195 | +| [IETF RFC 3881] | IETF RFC 3881 (2004), Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications.
    https://datatracker.ietf.org/doc/rfc3881 | +| [IHE ITI TF-2] | IHE ITI TF 2 (2010), IHE IT Infrastructure Technical Framework, Volume 2 (ITI TF-2), Revision 7.0. It comprises three sub-volumes: 2a (Transactions Part A), 2b (Transactions Part B) and 2x (Appendices).
    http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2a_FT_2010-08-10.pdf
    http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2b_FT_2010-08-10.pdf
    http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2x_FT_2010-08-10.pdf | + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +None. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------| +| AHD | Application Hosting Device | +| ATNA | Audit Trail and Node Authentication | +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| HFS | Health & Fitness Service | + +| | | +|-------|-------------------------------------------------------| +| HFSS | Health & Fitness Service Sender | +| HFSR | Health & Fitness Service Receiver | +| HL7 | Health Level 7 | +| HTTP | Hypertext Transfer Protocol | +| HTTPS | Hypertext Transfer Protocol Secure | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PCD | Patient Care Device | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| URI | Uniform Resource Identifier | +| USB | Universal Serial Bus | +| WAN | Wide Area Network | +| WD | WAN Device | +| WDM | Windows Driver Model | +| WS | Web Service | +| WSDL | Web Service Description Language | +| XML | extensible Markup Language | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|-------------|---------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Services interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 2.2 and 2.3 (shown in bold). + +- Group 1: HFS sender (HFSS) + - Group 1.1: Web services interoperability (WSI) + - Subgroup 1.1.1: Basic profile (BP) + - Subgroup 1.1.2: Basic security profile (BSP) + - Subgroup 1.1.3: Reliable messaging (RM) + - Group 1.2: Simple object access protocol (SOAP) + - Subgroup 1.2.1: SOAP headers (HEAD) + - Group 1.3: Audit trail and node authentication (ATNA) + - Subgroup 1.3.1: General (GEN) + - Subgroup 1.3.2: PCD-01 (PCD-01) + - Subgroup 1.3.3: Consent Management (CM) + - Group 1.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 1.4.1: General (GEN) + - Subgroup 1.4.2: Design guidelines (DG) + - Subgroup 1.4.3: Pulse oximeter (PO) + - Subgroup 1.4.4: Blood pressure monitor (BPM) + - Subgroup 1.4.5: Thermometer (TH) + - Subgroup 1.4.6: Weighing scales (WEG) + - Subgroup 1.4.7: Glucose meter (GL) + - Subgroup 1.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 1.4.9: Strength fitness equipment (ST) + - Subgroup 1.4.10: Independent living activity hub (HUB) + - Subgroup 1.4.11: Adherence monitor (AM) + - Subgroup 1.4.12: Peak expiratory flow monitor (PF) + - Subgroup 1.4.13: Body composition analyser (BCA) + - Subgroup 1.4.14: Basic electrocardiograph (ECG) + - Subgroup 1.4.15: International normalized ratio (INR) + - Subgroup 1.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.4.17: Insulin pump (IP) + +- Subgroup 1.4.18: Continuous glucose monitor (CGM) +- Group 1.5: Consent Management (CM) + - Subgroup 1.5.1: HFS XDR transaction (TRANS) + - Subgroup 1.5.2: HFS metadata validation (META) + - Subgroup 1.5.3: HFS consent directive validation (CDV) +- Group 1.6: hData Observation Upload (HDATA) + - Subgroup 1.6.1: General (GEN) +- Group 1.7: Questionnaires (QUE) + - Subgroup 1.7.1: General (GEN) + - Subgroup 1.7.2: CDA validation (CDA) + +### – Group 2: HFS receiver (HFSR) + +- Group 2.1: Web service interoperability (WSI) + - Subgroup 2.1.1: Basic profile (BP) + - Subgroup 2.1.2: Basic security profile (BSP) + - Subgroup 2.1.3: Reliable messaging (RM) +- **Group 2.2: SOAP (SOAP)** + - **Subgroup 2.2.1: SOAP headers (HEAD)** +- **Group 2.3: Audit (ATNA)** + - **Subgroup 2.3.1: General (GEN)** + - **Subgroup 2.3.2: PCD-01 (PCD-01)** + - **Subgroup 2.3.3: Consent Management (CM)** +- Group 2.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 2.4.1: General (GEN) + - Subgroup 2.4.2: Design guidelines (DG) + - Subgroup 2.4.3: Pulse oximeter (PO) + - Subgroup 2.4.4: Blood pressure monitor (BPM) + - Subgroup 2.4.5: Thermometer (TH) + - Subgroup 2.4.6: Weighing scales (WEG) + - Subgroup 2.4.7: Glucose meter (GL) + - Subgroup 2.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 2.4.9: Strength fitness equipment (ST) + - Subgroup 2.4.10: Independent living activity hub (HUB) + - Subgroup 2.4.11: Adherence monitor (AM) + - Subgroup 2.4.12: Peak expiratory flow monitor (PF) + - Subgroup 2.4.13: Body composition analyser (BCA) + - Subgroup 2.4.14: Basic electrocardiograph (ECG) + - Subgroup 2.4.15: International normalized ratio (INR) + - Subgroup 2.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.4.17: Insulin pump (IP) + - Subgroup 2.4.18: Continuous glucose monitor (CGM) +- Group 2.5: Consent Management (CM) + +- Subgroup 2.5.1: HFS XDR transaction (TRANS) + - Subgroup 2.5.2: HFS service validation (SER) +- Group 2.6: hData Observation Upload (HDATA) + - Subgroup 2.6.1: General (GEN) + - Subgroup 2.6.2: hData record format (HRF) +- Group 2.7: Questionnaires (QUE) + - Subgroup 2.7.1: General (GEN) + - Subgroup 2.7.2: CDA validation (CDA) + - Subgroup 2.7.3: hData record format (HRF) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - HFS: Health & Fitness Services Interface + - : This is the device under test. + - SEN: HFS sender + - REC: HFS receiver + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose (TP). +- **TP label:** This is the title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable Item: This contains testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 2.2.1: SOAP headers (HEAD) + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|---------------| +| TP Id | TP/HFS/REC/SOAP/HEAD/BV-000 | | | +| TP label | Requirements for Transactions which don't use HL7 V3 Messages | | | +| Coverage | Spec | [IHE ITI TF-2], Volume 2x, Appendix V | | +| | Testable items | Namespaces; M | IHE-WSP201; M | +| | | IHE-WSP203; M | IHE-WSP205; M | +| | | IHE-WSP207; M | IHE-WSP208; M | +| | | IHE-WSP212; M | IHE-WSP300; M | +| | | | IHE-WSA101; M | +| Test purpose |

    Check that:

    Table V.2.4-1 lists XML namespaces that are used in this appendix.

    [AND]

    IHE requires the profile writers and recommends the implementors to use the following naming convention for WSDL artifacts:

    • - message request -> {Transaction Name}_Message
    • - message response -> {Transaction Name}_Response_Message
    • - portType -> {NAME}_PortType
    • - Operation -> {NAME}_{Transaction Name}[_OperationID]
    • - SOAP 1.2 binding -> {NAME}_Binding_Soap12
    • - SOAP 1.2 port -> {NAME}_Port_Soap12

    [AND]

    The targetNamespace of the example WSDL shall be

    urn:ihe:{DOMAIN}:{PROFILE}:{YEAR}

    and may be extended to

    urn:ihe:{DOMAIN}:{PROFILE}:{YEAR}:{TYPE}

    [AND]

    The WSDL shall include XML Schema Definition references for the transactions payloads.

    [AND]

    Two WSDL messages shall be defined for a request-response transaction

    [AND]

    In the example WSDL provided by an IHE specification a single WSDL part named Body shall be defined for each WSDL message and the part type shall refer to an element defined in the Schema Definition required in IHE-WSP203

    [AND]

    For each input and output message defined in the WSDL portType operation an attribute wsaw:Action shall be included

    [AND]

    WSDL operations shall use wsd:operation/wsd:input/@wasw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}" and wsd:operation/wsd:output/@wsaw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}Response"

    [AND]

    For each operation defined in the WSDL portType a wsoap:operation/@soapAction attribute shall be provided. The value of wsoap:operation/@soapAction shall be consistent with the name for the corresponding WSDL operation defined in the WSDL portType

    [AND]

    The WSDL provided with an IHE specification shall use the SOAP Binding described in WSDL 1.1 Chapter 3 and the binding extension for SOAP 1.2

    [AND]

    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | All elements shall have the mustUnderstand attribute set (mustUnderstand='1') | +| Applicability | C_REC_000 AND C_REC_GEN_003 | +| Other PICS | | +| Initial condition | The HFS receiver under test has a WebService published and the simulated HFS sender is ready to send a SOAP message. | +| Test procedure |
    1. 1. The simulated HFS sender takes the WSDL description of the WebService provided by the HFS receiver and checks:
      1. a. Namespaces:
        • wsdl: "http://schemas.xmlsoap.org/wsdl/"
        • soap12: "http://schemas.xmlsoap.org/wsdl/soap12"
        • xsd: "http://www.w3.org/2001/XMLSchema"
        • wsaw: "http://www.w3.org/2006/05/addressing/wsdl"
      2. b. WSDL artifacts:
        • message request -> {Transaction Name}_Message
        • message response -> {Transaction Name}_Response_Message
        • portType -> {NAME}_PortType
        • Operation -> {NAME}_{Transaction Name}_{OperationID}
        • SOAP 1.2 binding -> {NAME}_Binding_Soap12
        • SOAP 1.2 port -> {NAME}_Port_Soap12

        where NAME is the value of the /wsdl:definitions/@name attribute and Transaction Name represents the formal IHE transaction name for this particular web-service exchange with spaces omitted from the name.

      3. c. The targetNamespace is urn:ihe:{DOMAIN}:{PROFILE}:{YEAR} and can be extended to urn:ihe:{DOMAIN}:{PROFILE}:{YEAR}:{TYPE}
      4. d. Two WSDL messages are defined, one for the request transaction and another for the response transaction.
      5. e. A single WSDL part named Body is defined for each WSDL message and the part type refers to an element defined in the schema definition included in the xsd reference.
      6. f. For each input and output message defined in the WSDL portType operation an attribute wsaw:Action is included and:
        • wsdl:operation/wsdl:input/@wsaw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}"
        • wsdl:operation/wsdl:output/@wsaw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}Response"
      7. g. For each operation defined in the WSDL portType a wsoap:operation/@soapAction attribute is provided and its value is consistent with the name for the corresponding WSDL operation defined in the WSDL portType
      8. h. WSDL provided with an IHE specification uses the binding extension for SOAP 1.2
    2. 2. The simulated HFS sender sends a SOAP message to the HFS receiver using addressing header blocks.
    3. 3. The HFS receiver responds with another SOAP message. Check that all <wsa:Action> elements have the mustUnderstand attribute set (mustUnderstand='1' or 'true')
    | +| Pass/Fail criteria |

    In step 1, all elements are in the WSDL description.

    In step 3, the response messages are as specified.

    | +| Notes | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--------------------| +| TP Id | TP/HFS/REC/SOAP/HEAD/BV-001 | | | +| TP label | Security Guidelines | | | +| Coverage | Spec | [ITU-T H.812] | | +| | Testable items | CommonReq 4; M | SecGuidelines 1; M | +| Test purpose | Check that:

    All Continua HFS connections shall be initiated from the HFS client component and shall not be initiated from the HFS service component.
    [AND]
    Continua HFS client and service components shall support the TLS protocol v1.0 (RFC 2246) from WS-I BSP v1.0 for secure communication
    [AND]
    Continua HFS client and service components shall support transfer of entity assertion information via SAML 2.0 token through WS-Security Header according to the Web Services Security: SAML Token Profile 1.1 | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The HFS receiver under test has a WebService published and the simulated HFS sender is ready to establish a connection using TLS [b-IETF RFC 2246] and SAML 2.0 as an authentication token [b-OASIS SAMLTP]. | | | +| Test procedure | 1. The simulated HFS sender starts a connection with the HFS receiver using HTTP over TLS v1.0.
    2. The HFS receiver under test allows the connection.
    3. The HFS sender sends a message using an SAML 2.0 token as an authentication token.
    4. The HFS receiver accepts the token and responds to the message without a security error. | | | +| Pass/Fail criteria | All steps are as specified above. If the HFS receiver responds with an error in step 4, it shall not be provoked by security reasons. | | | +| Notes | | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------| +| TP Id | TP/HFS/REC/SOAP/HEAD/BV-002 | | | +| TP label | HFS Observation Receiver Requirements | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ReceiverReq 2; M | ReceiverReq 3; M | +| Test purpose | Check that:

    A Continua HFS service component shall support WS-ReliableMessaging as an RM Destination for CommunicatePCDDataResponse messages
    [AND]
    A Continua HFS service component shall support WS-ReliableMessaging as an RM Source for CommunicatePCDDataResponse messages | | | +| Applicability | C_REC_000 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The simulated HFS sender is using WS-RM and the HFS receiver under test are in a none sequence state. | | | +| Test procedure | 1. The simulated HFS sender sends a CreateSequence message to the HFS receiver | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    with an offer element.

    1. 2. The HFS receiver under test responds with CreateSequenceResponse or with CreateSequenceRefused.
    2. 3. If the sequence created is not refused, the simulated HFS sender sends an HL7 message within the soap body of a sequence message indicating that it is the last one.
    3. 4. The HFS receiver responds with a SequenceAck header block message, a sequence header block and an HL7 message in the body.
    4. 5. The simulated HFS sender sends a SequenceAcknowledgement.
    | +| Pass/Fail criteria | All steps are as specified above. | +| Notes | The HFS receiver acts as an RM source in step 4 and as an RM destination in the other steps. | + +## A.3 Subgroup 2.3.1: ATNA general (GEN) + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--| +| TP Id | TP/HFS/REC/ATNA/GEN/BV-006 | | | +| TP label | Reliable Syslog ATNA Actor behaviour | | | +| Coverage | Spec | [IHE ITI TF-2] | | +| | Testable items | Audit_MT-1; M | | +| Test purpose |

    Check that:

    If the Audit Record repository is not available, the HFS actor shall store the audit record in a local buffer until the audit record repository is available again.

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_001 AND C_REC_ATNA_001 | | | +| Other PICS | C_REC_GEN_003, C_REC_GEN_004 | | | +| Initial condition | The HFS receiver under test is shutdown. The simulated HFS sender has a SOAP message (a PCD-01 message or a consent document) ready to be sent and the Simulated Audit Repository with Reliable Syslog transport is intentionally disabled. | | | +| Test procedure |
    1. 1. The HFS receiver application under test is started and it sends the corresponding audit record message to the audit repository. As the simulated audit repository receiver is disabled, the message will not be delivered.
    2. 2. Wait for one minute.
    3. 3. The test tool starts the simulated audit repository.
    4. 4. If C_REC_GEN_002 = FALSE (the SUT does not support consent management) THEN the simulated HFS sender sends a PCD-01 message to the HFS receiver under test.

      IF C_REC_GEN_002 = TRUE (the SUT supports consent management) THEN the simulated HFS sender sends a consent document to the HFS receiver under test.
    5. 5. The test tool receives the SOAP message (a PCD-01 message or a consent document) acknowledge and the audit record messages sent by the HFS receiver under test.
    | | | +| Pass/Fail criteria |
    • • Two audit record messages must be received by the simulated audit repository: One for the HFS receiver start action (step 1) and the other for the SOAP message sent in step 4.
    • • There is one audit record with the attribute "code" of the element EventID set to "110107" (PHI-import) and the EventDateTime attribute of the EventIdentification element is set to the expedition time of the SOAP message sent in step 4.
    • • There is one audit record with the attribute "code" of the element EventID set to "110120" (start action) and the EventDateTime attribute of the EventIdentification element is set at least one minute before the expedition time of the SOAP message sent in step 4.
    | | | +| Notes | In step 4, the way to force the HFS receiver to send the pending audit record not delivered in step 1 depends on the vendor implementation. A typical strategy could be to send | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | another HFS message and its corresponding ATNA record; in this way, when the HFS receiver under test sends the ATNA record PHI-import, then it would send the pending audit record along with the newer one. | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## A.4 Subgroup 2.3.2: ATNA PCD-01 (PCD-01) + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|------------------|-----------------| +| TP Id | TP/HFS/REC/ATNA/PCD-01/BV-000 | | | | +| TP label | PCD-01 - Reliable Syslog ATNA Actor Start | | | | +| Coverage | Spec | [IHE ITI TF-2] | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-1; M | Audit_RF-1; M | +| | | Rel_Syslog-1; M | Rel_Syslog-2; M | | +| | Spec | [ITU-T H.812] | | | +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | +| Test purpose | Check that:
    When SUT starts the application then audit log start message is received from the SUT and it is conformant to the ATNA specifications | | | | +| Applicability | C_REC_000 AND C_REC_GEN_001 AND C_REC_ATNA_001 | | | | +| Other PICS | C_REC_GEN_003, C_REC_GEN_004 | | | | +| Initial condition | The HFS receiver under test is shut down and a simulated audit repository with reliable syslog transport is running. | | | | +| Test procedure | 1. The HFS receiver application under test is started and sends the corresponding audit record message to the audit repository.

    2. The audit repository receives the audit record message and verifies that:
    a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA
    b. It conforms to the reliable syslog's cooked profile [IETF RFC 3195] | | | | +| Pass/Fail criteria |
    • • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • • In the audit record, the attribute "code" of the element EventID is set to "110120" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • • The received audit message conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    | | | | +| Notes | | | | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|------------------| +| TP Id | TP/HFS/REC/ATNA/PCD-01/BV-001 | | | +| TP label | PCD-01 - BSD Syslog ATNA Actor Start | | | +| Coverage | Spec | [IHE ITI TF-2] | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | +| | | ActTrans-6; O | ATNA_IP-2; O | +| | | ChainTrust-2; M | DirectCert-1; M | +| | | DirectCert-3; M | Trigg_Event-1; M | +| | | BSD_Syslog-1; O | BSD_Syslog-2; M | +| | | BSD_Syslog-4; M | BSD_Syslog-5; R | +| | Spec | [ITU-T H.812] | | +| | Testable items | SecGuidelines 3; O | | +| | Spec | [IETF RFC 3881] | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | +| Test purpose |

    Check that:

    When SUT starts the application then audit log start message is received from the SUT and it is conformant to the ATNA specifications

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_001 AND C_REC_ATNA_002 | | | +| Other PICS | C_REC_GEN_003, C_REC_GEN_004 | | | +| Initial condition | The HFS receiver under test is shut down and a simulated audit repository with BSD syslog transport is running. | | | +| Test procedure |
    1. The HFS receiver application under test is started and sends the corresponding audit record message to the audit repository.
    2. The audit repository receives the audit record message and verifies that it conforms to BSD Syslog [b-IETF RFC 3164].
    | | | +| Pass/Fail criteria |
    • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • In the audit record, the attribute "code" of the element EventID is set to "110120" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • The received audit message conforms to the BSD Syslog [b-IETF RFC 3164].
    | | | +| Notes | | | | + +| | | | | +|-----------------|------------------------------------------------|-----------------|-------------------| +| TP Id | TP/HFS/REC/ATNA/PCD-01/BV-002 | | | +| TP label | PCD-01 - Reliable Syslog ATNA Actor PHI-import | | | +| Coverage | Spec | [IHE ITI TF-2] | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | +| | | ActTrans-6; O | ATNA_IP-2; O | +| | | ChainTrust-2; M | DirectCert-1; M | +| | | DirectCert-3; M | Trigg_Event-16; M | + +| | | | | | +|---------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------| +| | | Rel_Syslog-1; M | Rel_Syslog-2; M | | +| | Spec | [ITU-T H.812] | | | +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | +| Test purpose | | Check that:

    When SUT receives a PCD-01 ORU message, then an audit log PHI-import message is received from the SUT and it is conformant to the ATNA specifications | | | +| Applicability | | C_REC_000 AND C_REC_GEN_001 AND C_REC_ATNA_001 | | | +| Other PICS | | C_REC_GEN_003, C_REC_GEN_004 | | | +| Initial condition | | The HFS receiver under test has a WebService enabled for PCD-01 message reception, the simulated HFS sender has a PCD-01 message ready to be sent and a simulated audit repository with reliable syslog transport is running. | | | +| Test procedure | | 1. The simulated HFS sender sends a PCD-01 message to the HFS receiver under test.
    2. The HFS receiver under test replies with PCD-01 ACK message and it sends the corresponding audit record message to the audit repository.
    3. The audit repository receives the audit record message and verifies that:
    a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA
    b. It conforms to the reliable syslog's cooked profile [IETF RFC 3195]. | | | +| Pass/Fail criteria | |
    • • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • • In the audit record, the attribute "code" of the element EventID is set to "110107" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • • In the audit record, the value of the attribute EventDateTime of the element EventIdentification is inside a one minute interval of the Date and Time indicated in the MSH-7 field of the PCD-01 ACK message sent by the HFS receiver under test.
    • • The received audit message conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    | | | +| Notes | | | | | + +| | | | | | +|-----------------|-------------------------------------------|-----------------|-------------------|-----------------| +| TP Id | TP/HFS/REC/ATNA/PCD-01/BV-003 | | | | +| TP label | PCD-01 - BSD Syslog ATNA Actor PHI-import | | | | +| Coverage | Spec | [IHE ITI TF-2] | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-16; M | Audit_RF-1; M | +| | | BSD_Syslog-1; O | BSD_Syslog-2; M | BSD_Syslog-3; M | +| | | BSD_Syslog-4; M | BSD_Syslog-5; R | BSD_Syslog-6; O | +| | Spec | [ITU-T H.812] | | | + +| | | | | | +|---------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------| +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-01; M | SAAAM-DD-01; M | +| | | SAAAM-DD-04; M | SAAAM-DD-04; M | SAAAM-DD-04; M | +| | | SAAAM-DD-07; O | SAAAM-DD-07; O | SAAAM-DD-07; O | +| | | SAAAM-DD-10; O | SAAAM-DD-10; O | SAAAM-DD-10; O | +| | | SAAAM-DD-13; O | SAAAM-DD-13; O | SAAAM-DD-13; O | +| | | SAAAM-DD-16; O | SAAAM-DD-16; O | SAAAM-DD-16; O | +| | | SAAAM-DD-19; M | SAAAM-DD-19; M | SAAAM-DD-19; M | +| Test purpose | | Check that:
    When SUT receives a PCD-01 ORU message, then an audit log PHI-import message is received from the SUT and it is conformant to the ATNA specifications | | | +| Applicability | | C_REC_000 AND C_REC_GEN_001 AND C_REC_ATNA_002 | | | +| Other PICS | | C_REC_GEN_003, C_REC_GEN_004 | | | +| Initial condition | | The HFS receiver under test has a WebService enabled for PCD-01 message reception, the simulated HFS sender has a PCD-01 message ready to be sent and a simulated audit repository with BSD syslog transport is running. | | | +| Test procedure | | 1. The simulated HFS sender sends a PCD-01 message to the HFS receiver under test.
    2. The HFS receiver under test replies with a PCD-01 ACK message and sends the corresponding audit record message to the audit repository.
    3. The audit repository receives the Audit Record Message and verifies that it conforms to the BSD Syslog [b-IETF RFC 3164]. | | | +| Pass/Fail criteria | |
    • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • The attribute "code" of the element EventID is set to "110107" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • In the audit record, the value of the attribute EventDateTime of the element EventIdentification is inside a one-minute interval of the Data and Time indicated in the MSH-7 field of the PCD-01 ACK message sent by the HFS receiver under test.
    • The received audit message conforms to the BSD Syslog [b-IETF RFC 3164].
    | | | +| Notes | | | | | + +| | | | | | +|-----------------|------------------------------------------|--------------------|------------------|-----------------| +| TP Id | TP/HFS/REC/ATNA/PCD-01/BV-004 | | | | +| TP label | PCD-01 - Reliable Syslog ATNA Actor Stop | | | | +| Coverage | Spec | [IHE ITI TF-2] | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-1; M | Audit_RF-1; M | +| | | Rel_Syslog-1; M | Rel_Syslog-2; M | | +| | Spec | [ITU-T H.812] | | | +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------|----------------| +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | +| Test purpose | Check that:
    When SUT stops the application then audit log stop message is received from the SUT and it is conformant to the ATNA specifications | | | | +| Applicability | C_REC_000 AND C_REC_GEN_001 AND C_REC_ATNA_001 | | | | +| Other PICS | C_REC_GEN_003, C_REC_GEN_004 | | | | +| Initial condition | The HFS receiver under test has a WebService enabled and a simulated audit repository with reliable syslog transport is running. | | | | +| Test procedure |
    1. The HFS receiver application under test shuts down the application and sends the corresponding audit record message to the audit repository.
    2. The audit repository receives the audit record message and verifies that:
      1. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA
      2. It conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    | | | | +| Pass/Fail criteria |
    • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • In the audit record, the attribute "code" of the element EventID is set to "110121" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • The received audit message conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    | | | | +| Notes | | | | | + +| | | | | | +|---------------------|-------------------------------------|--------------------|------------------|-----------------| +| TP Id | TP/HFS/REC/ATNA/PCD-01/BV-005 | | | | +| TP label | PCD-01 - BSD Syslog ATNA Actor Stop | | | | +| Coverage | Spec | [IHE ITI TF-2] | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | +| | | DirectCert-3; M | Trigg_Event-1; M | Audit_RF-1; M | +| | | BSD_Syslog-1; O | BSD_Syslog-2; M | BSD_Syslog-3; M | +| | | BSD_Syslog-4; M | BSD_Syslog-5; R | BSD_Syslog-6; O | +| | Spec | [ITU-T H.812] | | | +| | Testable items | SecGuidelines 3; O | | | +| | Spec | [IETF RFC 3881] | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | SAAAM-DD-03; M | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | SAAAM-DD-06; M | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | SAAAM-DD-09; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | SAAAM-DD-12; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | SAAAM-DD-15; O | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | SAAAM-DD-18; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | SAAAM-DD-21; M | +| Test purpose | Check that: | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | When SUT stops the application then audit log stop message is received from the SUT and it is conformant to the ATNA specifications | +| Applicability | C_REC_000 AND C_REC_GEN_001 AND C_REC_ATNA_002 | +| Other PICS | C_REC_GEN_003, C_REC_GEN_004 | +| Initial condition | The HFS receiver under test has a WebService enabled and a simulated audit repository with BSD syslog transport is running. | +| Test procedure |
    1. The HFS receiver application under test shuts down the application and sends the corresponding audit record message to the audit repository.
    2. The audit repository receives the audit record message and verifies that it conforms to BSD Syslog [b-IETF RFC 3164].
    | +| Pass/Fail criteria |
    • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • The attribute "code" of the element EventID is set to "110121" and the attribute "displayName" of the EventTypeCode element is set to "Communicate PCD Data".
    • The received audit message conforms to the BSD Syslog [b-IETF RFC 3164].
    | +| Notes | | + +## A.5 Subgroup 2.3.3: ATNA consent management (CM) + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------| +| TP Id | TP/HFS/REC/ATNA/CM/BV-000 | | | +| TP label | CM - Reliable Syslog ATNA Actor PHI-import | | | +| Coverage | Spec | [IHE ITI TF-2], Volume 2a | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | +| | | ActTrans-6; O | ATNA_IP-2; O | +| | | ChainTrust-2; M | DirectCert-1; M | +| | | DirectCert-3; M | Trigg_Event-16; M | +| | | Rel_Syslog-1; M | Rel_Syslog-2; M | +| | Spec | [IHE ITI TF-2], Volume 2b | | +| | Testable items | ProvideAudit1; O | | +| | Spec | [IETF RFC 3881] | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-02; O | +| | | SAAAM-DD-04; M | SAAAM-DD-05; O | +| | | SAAAM-DD-07; O | SAAAM-DD-08; O | +| | | SAAAM-DD-10; O | SAAAM-DD-11; O | +| | | SAAAM-DD-13; O | SAAAM-DD-14; M | +| | | SAAAM-DD-16; O | SAAAM-DD-17; O | +| | | SAAAM-DD-19; M | SAAAM-DD-20; O | +| | | | SAAAM-DD-21; M | +| Test purpose |

    Check that:

    When SUT receives a Consent Document, then an audit log PHI-import message is received from the SUT and it is conformant to the ATNA specifications

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_001 AND C_REC_ATNA_001 AND C_REC_GEN_002 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The HFS receiver under test has a WebService enabled for consent document reception. The simulated HFS sender has a consent message ready to be sent and a simulated audit repository with reliable syslog is running. | | | +| Test procedure |
    1. The simulated HFS sender sends the consent document to the HFS receiver under
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    test.

    1. 2. When the HFS receiver under test receives the consent document it then sends the corresponding audit record message to the audit repository.
    2. 3. The audit repository receives the audit record message and verifies that:
      1. a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA
      2. b. It conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    3. 4. The audit record includes the following elements:
      1. a. An EventIdentification element that contains:
        • "EventActionCode" attribute set to "C"
        • EventID sub-element with attributes "code" set to "110107" and "displayName" set to "Import"
        • EventTypeCode subelement with attributes "code" set to "ITI-41", "displayName" set to "Provide and Register Document Set-b" and "codeSystemName" set to "IHE Transactions"
      2. b. An ActiveParticipant element that contains:
        • "UserIsRequestor" attribute set to "true"
        • "NetworkAccessPointTypeCode" attribute set to "1" or "2"
        • RoleIDCode sub-element with attributes "code" set to "110153" and "displayName" set to "Source"
      3. c. An ActiveParticipant element that contains:
        • "UserIsRequestor" attribute set to "false"
        • "NetworkAccessPointTypeCode" attribute set to "1" or "2"
        • "AlternativeUserID" attribute is present
        • RoleIDCode subelement with attributes "code" set to "110152" and "displayName" set to "Destination"
      4. d. A ParticipantObjectIdentification element that contains:
        • "ParticipantObjectID" attribute is present and not empty
        • "ParticipantObjectTypeCode" attribute set to "1"
        • "ParticipantObjectTypeCodeRole" attribute set to "1"
        • ParticipantObjectTypeCode sub-element with attributes "code" set to "2", "displayName" set to "Patient Number" and "codeSystemName" set to "RFC-3881"
      5. e. A ParticipantObjectIdentification element that contains:
        • "ParticipantObjectID" attribute is present and not empty
        • "ParticipantObjectTypeCode" attribute set to "2"
        • "ParticipantObjectTypeCodeRole" attribute set to "20"
        • ParticipantObjectTypeCode sub-element with attributes "code" set to "urn:uuid:a54d6aa5-d40d-43f9-88c5-b4633d873bdd", "displayName" set to "submission set classificationNode" and "codeSystemName" set to "IHE XDS Metadata"
    | +| Pass/Fail criteria |
    • • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • • The audit record content conforms to the values described in step 4.
    • • The received audit message conforms to the reliable syslog's cooked profile [IETF RFC 3195].
    | +| Notes | | + +| | | +|-----------------|---------------------------------------| +| TP Id | TP/HFS/REC/ATNA/CM/BV-001 | +| TP label | CM - BSD Syslog ATNA Actor PHI-import | + +| | | | | | | +|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------|--| +| Coverage | Spec | [IHE ITI TF-2], Volume 2a | | | | +| | Testable items | AuditMess-2; R | AuditMess-3; M | ActTrans-8; O | | +| | | ActTrans-6; O | ATNA_IP-2; O | ATNA_PF-1; M | | +| | | ChainTrust-2; M | DirectCert-1; M | DirectCert-2; M | | +| | | DirectCert-3; M | Trigg_Event-16; M | Audit_RF-1; M | | +| | | BSD_Syslog-1; O | BSD_Syslog-2; M | BSD_Syslog-3; M | | +| | | BSD_Syslog-4; M | BSD_Syslog-5; R | BSD_Syslog-6; O | | +| | Spec | [IHE ITI TF-2], Volume 2b | | | | +| | Testable items | ProvideAudit1; O | | | | +| | Spec | [IETF RFC 3881] | | | | +| | Testable items | SAAAM-DD-01; M | SAAAM-DD-01; M | SAAAM-DD-01; M | | +| | | SAAAM-DD-04; M | SAAAM-DD-04; M | SAAAM-DD-04; M | | +| | | SAAAM-DD-07; O | SAAAM-DD-07; O | SAAAM-DD-07; O | | +| | | SAAAM-DD-10; O | SAAAM-DD-10; O | SAAAM-DD-10; O | | +| | | SAAAM-DD-13; O | SAAAM-DD-13; O | SAAAM-DD-13; O | | +| | | SAAAM-DD-16; O | SAAAM-DD-16; O | SAAAM-DD-16; O | | +| | | SAAAM-DD-19; M | SAAAM-DD-19; M | SAAAM-DD-19; M | | +| Test purpose | | Check that:
    Audit log message is received from the SUT and it is conformant to the ATNA specifications | | | | +| Applicability | | C_REC_000 AND C_REC_GEN_001 AND C_REC_ATNA_002 AND C_REC_GEN_002 AND C_REC_GEN_003 | | | | +| Other PICS | | | | | | +| Initial condition | | The HFS receiver under test has a WebService enabled and the simulated HFS sender has a consent message and an audit repository with BSD syslog transport is running. | | | | +| Test procedure | |
    1. 1. The HFS sender application under test sends an audit record message to the audit repository.
    2. 2. The audit repository receives the audit record message and verifies that it conforms to BSD syslog [b-IETF RFC 3164].
    3. 3. The audit record includes the following elements:
      1. a. An EventIdentification element that contains:
        • "EventActionCode" attribute set to "C"
        • EventID subelement with attributes "code" set to "110107" and "displayName" set to "Import"
        • EventTypeCode subelement with attributes "code" set to "ITI-41", "displayName" set to "Provide and Register Document Set-b" and "codeSystemName" set to "IHE Transactions"
      2. b. An ActiveParticipant element that contains:
        • "UserIsRequestor" attribute set to "true"
        • "NetworkAccessPointTypeCode" attribute set to "1" or "2"
        • RoleIDCode subelement with attributes "code" set to "110153" and "displayName" set to "Source"
      3. c. An ActiveParticipant element that contains:
        • "UserIsRequestor" attribute set to "false"
        • "NetworkAccessPointTypeCode" attribute set to "1" or "2"
        • "AlternativeUserID" attribute is present
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
      • RoleIDCode subelement with attributes "code" set to "110152" and "displayName" set to "Destination"
    • d. A ParticipantObjectIdentification element that contains:
      • "ParticipantObjectID" attribute is present and not empty
      • "ParticipantObjectTypeCode" attribute set to "1"
      • "ParticipantObjectTypeCodeRole" attribute set to "1"
      • ParticipantObjectTypeCode subelement with attributes "code" set to "2", "displayName" set to "Patient Number" and "codeSystemName" set to "RFC-3881"
    • e. A ParticipantObjectIdentification element that contains:
      • "ParticipantObjectID" attribute is present and not empty
      • "ParticipantObjectTypeCode" attribute set to "2"
      • "ParticipantObjectTypeCodeRole" attribute set to "20"
      • ParticipantObjectTypeCode subelement with attributes "code" set to "urn:uuid:a54d6aa5-d40d-43f9-88c5-b4633d873bdd", "displayName" set to "submission set classificationNode" and "codeSystemName" set to "IHE XDS Metadata"
    | +| Pass/Fail criteria |
    • • The ATNA XML log file conforms to the [IETF RFC 3881] schema included in Annex B.
    • • The audit record content conforms to values described in step 4.
    • • The received audit message conforms to the BSD Syslog [b-IETF RFC 3164].
    | +| Notes | | + +# Annex B + +## Schema for IETF RFC 3881 verification + +(This annex forms an integral part of this Recommendation.) + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + Create + + + + + Read + + + + + Update + + + + + Delete + + + + + Execute + + + + + + + +``` + +``` + + + + + +     + + + + + + + Success + + + + + Minor failure + + + + + Serious failure + + + + + + Major failure; action made unavailable + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + Machine Name, including DNS name + + + + + + IP Address + + + + + Telephone Number + + + + + + + + + + + + + + + + + + + + + + Person + + + + + System object + + + + + Organization + + + + + Other + + + + + + + +``` + +``` + + + + + + Patient + + + + + Location + + + + + Report + + + + + Resource + + + + + Master file + + + + + User + + + + + List + + + + + Doctor + + + + + Subscriber + + + + + Guarantor + + + + + + Security User Entity + + + + + + Security User Group + + + + + +``` + +``` + + + + Security Resource + + + + + + Security Granularity Definition + + + + + + Provider + + + + + Report Destination + + + + + Report Library + + + + + Schedule + + + + + Customer + + + + + Job + + + + + Job Stream + + + + + Table + + + + + Routing Criteria + + + + + Query + + + + + +``` + +``` + + + + + + + + + Origination / Creation + + + + + + + Import / Copy from original + + + + + + Amendment + + + + + Verification + + + + + Translation + + + + + Access / Use + + + + + De-identification + + + + + + Aggregation, summarization, derivation + + + + + + Report + + + + + + Export / Copy to target + + + + + +``` + +``` + + + Disclosure + + + + + + Receipt of disclosure + + + + + + Archiving + + + + + Logical deletion + + + + + + Permanent erasure / Physical destruction + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003): *ETSI drafting rules*. +- [b-HFSR PICS & PIXIT] Services HFS Receiver DG2016 PICS and PIXIT excel sheet v1.7. +- [b-HFSS PICS & PIXIT] Services HFS Sender DG2016 PICS and PIXIT excel sheet v1.7. +- [b-IETF RFC 2246] IETF RFC 2246 (1999), *The TLS Protocol version 1.0*. +- [b-IETF RFC 3164] IETF RFC 3164 (2001), *The BSD Syslog Protocol*. +- [b-OASIS SAMLTP] OASIS (2006), *Web Services Security: SAML Token Profile 1.1*. +- [b-OASIS SAML 2.0] OASIS SAML 2.0 (2005), *Security Assertion Markup Language 2.0*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.830.5-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.830.5-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c782dc3af81438e5fbc63d620f4518c5cbbf057d --- /dev/null +++ b/marked/H/T-REC-H.830.5-201704-I_PDF-E/raw.md @@ -0,0 +1,9797 @@ + + +**ITU-T** + +**H.830.5** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Services interface Part 5: PCD-01 HL7 +messages: Health & Fitness Service sender** + +Recommendation ITU-T H.830.5 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.830.5 + +## Conformance of ITU-T H.810 personal health system: Services interface Part 5: PCD-01 HL7 messages: Health & Fitness Service sender + +## Summary + +Recommendation ITU-T H.830.5 provides a test suite structure (TSS) and the test purposes (TP) for PCD-01 HL7 messages through the Health & Fitness Service (HFS) sender in the Services interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.830.5 is the transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 5: PCD-01 HL 7 Messages. HFS Sender (Version 1.8, 2017-03-14), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-----------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.835 | 2015-01-13 | 16 | 11.1002/1000/12253 | +| 1.0 | ITU-T H.830.5 | 2015-01-13 | 16 | 11.1002/1000/12591 | +| 2.0 | ITU-T H.830.5 | 2016-07-14 | 16 | 11.1002/1000/12925 | +| 3.0 | ITU-T H.830.5 | 2017-04-13 | 16 | 11.1002/1000/13204 | +| 3.1 | ITU-T H.830.5 (2017) Cor. 1 | 2017-11-29 | 16 | 11.1002/1000/13424 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, Services interface, personal connected health devices, PCD-01 HL7 messages, Health & Fitness Service sender. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|--------------|---------------------------------------------------------------------------|-----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Test suite structure (TSS) ..... | 4 | +| 7 | Electronic attachment ..... | 6 | +| Annex A | – Test purposes ..... | 8 | +| A.1 | TP definition conventions..... | 8 | +| A.2 | Subgroup 1.4.1: General (GEN)..... | 9 | +| A.3 | Subgroup 1.4.2: Design guidelines (DG) ..... | 30 | +| A.4 | Subgroup 1.4.3: Pulse oximeter (PO)..... | 31 | +| A.5 | Subgroup 1.4.4: Blood pressure monitor (BPM)..... | 50 | +| A.6 | Subgroup 1.4.5: Thermometer (TH)..... | 60 | +| A.7 | Subgroup 1.4.6: Weighing scales (WEG) ..... | 68 | +| A.8 | Subgroup 1.4.7: Glucose meter (GL) ..... | 78 | +| A.9 | Subgroup 1.4.8: Cardiovascular fitness and activity monitor (CV) ..... | 102 | +| A.10 | Subgroup 1.4.9: Strength fitness equipment (ST) ..... | 155 | +| A.11 | Subgroup 1.4.10: Independent living activity hub (HUB) ..... | 174 | +| A.12 | Subgroup 1.4.11: Adherence monitor (AM) ..... | 207 | +| A.13 | Subgroup 1.4.12: Peak expiratory flow monitor (PF) ..... | 220 | +| A.14 | Subgroup 1.4.13: Body composition analyser (BCA)..... | 233 | +| A.15 | Subgroup 1.4.14: Basic electrocardiograph (ECG)..... | 249 | +| A.16 | Subgroup 1.4.15: International normalized ratio (INR) ..... | 263 | +| A.17 | Subgroup 1.4.16: Sleeping apnoea breathing therapy equipment (SABTE)..... | 276 | +| A.18 | Subgroup 1.4.17: Insulin pump ..... | 339 | +| A.19 | Subgroup 1.4.18: Continuous glucose monitor (CGM) ..... | 362 | +| Bibliography | ..... | 387 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 5: PCD-01 HL 7 Messages. HFS Sender (Version 1.8, 2017-03-14), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.2 | 2012-10-05 | Initial release for Test Tool DG2011. This is the same version as "TSS&TP_1.5_WAN_PART_5_(SEN PCD-01)_v1.2.doc" because new features included in [b-CDG 2011] do not affect the test procedures specified in this document. | +| 1.3 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_WAN_PART_5_(SEN PCD-01)_v1.2" as a baseline and adds new features included in [b-CDG 2012]:
    • Addition of glucose meter new spec. version
    • Addition of body composition analyser device specialization
    • Addition of basic electrocardiograph device specialization
    | +| 1.4 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_WAN_PART_5_(SEN PCD-01)_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • Addition of glucose meter BLE
    • Addition of BLE SSP support
    • Addition of NFC new transport
    • Addition of INR device specialization
    | +| 1.5 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_WAN_PART_5_(SEN PCD-01)_v1.4.doc" as a baseline and adds new features included in Documentation Enhancements:
    • "Other PICS" row added
    | +| 1.6 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_WAN_PART_5_(SEN PCD-01)_v1.5.doc" as a baseline and it adds new features included in Continua DG 2015:
    • Changes in test suite structure.
    • Add international normalized ratio device specialization
    • Add sleeping apnoea breathing therapy equipment device specialization
    • Added support for hData observation upload
    | +| 1.7 | 2016-09-20 | Initial release for Test Tool DG2016. It implements changes according to [ITU-T H.810 (2016)]/[b-CDG 2016] (Iris + Errata) refreshments. | +| 1.8 | 2017-03-14 | Added insulin pump and continuous glucose monitor specializations support. | + +# **Recommendation ITU-T H.830.5** + +## Conformance of ITU-T H.810 personal health system: Services interface Part 5: PCD-01 HL7 messages: Health & Fitness Service sender + +# **1 Scope** + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Services interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Services interface have been divided into the parts specified below. This Recommendation covers Part 5. + +- Part 1: Web Services Interoperability. Health & Fitness Service sender +- Part 2: Web Services Interoperability. Health & Fitness Service receiver +- Part 3: SOAP/ATNA. Health & Fitness Service sender +- Part 4: SOAP/ATNA. Health & Fitness Service receiver +- **Part 5: PCD-01 HL7 Messages. Health & Fitness Service sender** +- Part 6: PCD-01 HL7 Messages. Health & Fitness Service receiver +- Part 7: Consent Management. Health & Fitness Service sender +- Part 8: Consent Management. Health & Fitness Service receiver +- Part 9: hData Observation Upload. Health & Fitness Service sender +- Part 10: hData Observation Upload. Health & Fitness Service receiver +- Part 11: Questionnaires. Health & Fitness Service sender +- Part 12: Questionnaires. Health & Fitness Service receiver + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [ITU-T H.810 (2016)] | Recommendation ITU-T H.810 (2016), Interoperability design guidelines for personal health systems . | +| [ITU-T H.812.1] | Recommendation ITU-T H.812.1 (2016), Interoperability design guidelines for personal health systems: Services interface: Observation upload certified capability class . | +| [IHE PCD TF 2] | IHE PCD TF 2 (2011), Integrating the Healthcare Enterprise, IHE Patient Care Device (PCD) Technical Framework, Volume 2 (PCD | + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## **3 Definitions** + +### **3.1 Terms defined elsewhere** + +None. + +### **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-----------------------------------------------| +| AHD | Application Hosting Device | +| ATNA | Audit Trail and Node Authentication | +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| HFS | Health & Fitness Service | +| HFSS | Health & Fitness Service Sender | +| HFSR | Health & Fitness Service Receiver | +| HL7 | Health Level 7 | +| HTTP | Hypertext Transfer Protocol | +| HTTPS | Hypertext Transfer Protocol Secure | +| LAN | Local area network | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal area network | +| PCD | Patient Care Device | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | + +| | | +|-------|-------------------------------------------------------| +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TLS | Transport Level Security | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| URI | Uniform Resource Identifier | +| USB | Universal Serial Bus | +| WAN | Wide Area Network | +| WDM | Windows Driver Model | +| WS | Web Service | +| WSDL | Web Service Description Language | +| XML | extensible Markup Language | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TP) for the Services interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 1.4.1 to 1.4.18 (shown in bold). + +- Group 1: HFS sender (HFSS) + - Group 1.1: Web services interoperability (WSI) + +- Subgroup 1.1.1: Basic profile (BP) + - Subgroup 1.1.2: Basic security profile (BSP) + - Subgroup 1.1.3: Reliable messaging (RM) + - Group 1.2: Simple object access protocol (SOAP) + - Subgroup 1.2.1: SOAP headers (HEAD) + - Group 1.3: Audit trail and node authentication (ATNA) + - Subgroup 1.3.1: General (GEN) + - Subgroup 1.3.2: PCD-01 (PCD-01) + - Subgroup 1.3.3: Consent Management (CM) + - Group 1.4: PCD-01 HL7 messages (PCD-01-DATA) + - **Subgroup 1.4.1: General (GEN)** + - **Subgroup 1.4.2: Design guidelines (DG)** + - **Subgroup 1.4.3: Pulse oximeter (PO)** + - **Subgroup 1.4.4: Blood pressure monitor (BPM)** + - **Subgroup 1.4.5: Thermometer (TH)** + - **Subgroup 1.4.6: Weighing scales (WEG)** + - **Subgroup 1.4.7: Glucose meter (GL)** + - **Subgroup 1.4.8: Cardiovascular fitness and activity monitor (CV)** + - **Subgroup 1.4.9: Strength fitness equipment (ST)** + - **Subgroup 1.4.10: Independent living activity hub (HUB)** + - **Subgroup 1.4.11: Adherence monitor (AM)** + - **Subgroup 1.4.12: Peak expiratory flow monitor (PF)** + - **Subgroup 1.4.13: Body composition analyser (BCA)** + - **Subgroup 1.4.14: Basic electrocardiograph (ECG)** + - **Subgroup 1.4.15: International normalized ratio (INR)** + - **Subgroup 1.4.16: Sleep apnoea breathing therapy equipment (SABTE)** + - **Subgroup 1.4.17: Insulin pump (IP)** + - **Subgroup 1.4.18: Continuous glucose monitor (CGM)** + - Group 1.5: Consent Management (CM) + - Subgroup 1.5.1: HFS XDR transaction (TRANS) + - Subgroup 1.5.2: HFS metadata validation (META) + - Subgroup 1.5.3: HFS consent directive validation (CDV) + - Group 1.6: hData Observation Upload (HDATA) + - Subgroup 1.6.1: General (GEN) + - Group 1.7: Questionnaires (QUE) + - Subgroup 1.7.1: General (GEN) + - Subgroup 1.7.2: CDA validation (CDA) +- Group 2: HFS receiver (HFSR) +- Group 2.1: Web service interoperability (WSI) + - Subgroup 2.1.1: Basic profile (BP) + - Subgroup 2.1.2: Basic security profile (BSP) + +- Subgroup 2.1.3: Reliable messaging (RM) +- Group 2.2: SOAP (SOAP) + - Subgroup 2.2.1: SOAP headers (HEAD) +- Group 2.3: Audit (ATNA) + - Subgroup 2.3.1: General (GEN) + - Subgroup 2.3.2: PCD-01 (PCD-01) + - Subgroup 2.3.3: Consent management (CM) +- Group 2.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 2.4.1: General (GEN) + - Subgroup 2.4.2: Design guidelines (DG) + - Subgroup 2.4.3: Pulse oximeter (PO) + - Subgroup 2.4.4: Blood pressure monitor (BPM) + - Subgroup 2.4.5: Thermometer (TH) + - Subgroup 2.4.6: Weighing scales (WEG) + - Subgroup 2.4.7: Glucose meter (GL) + - Subgroup 2.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 2.4.9: Strength fitness equipment (ST) + - Subgroup 2.4.10: Independent living activity hub (HUB) + - Subgroup 2.4.11: Adherence monitor (AM) + - Subgroup 2.4.12: Peak expiratory flow monitor (PF) + - Subgroup 2.4.13: Body composition analyser (BCA) + - Subgroup 2.4.14: Basic electrocardiograph (ECG) + - Subgroup 2.4.15: International normalized ratio (INR) + - Subgroup 2.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.4.17: Insulin pump (IP) + - Subgroup 2.4.18: Continuous glucose monitor (CGM) +- Group 2.5: Consent Management (CM) + - Subgroup 2.5.1: HFS XDR transaction (TRANS) + - Subgroup 2.5.2: HFS service validation (SER) +- Group 2.6: hData Observation Upload (HDATA) + - Subgroup 2.6.1: General (GEN) + - Subgroup 2.6.2: hData record format (HRF) +- Group 2.7: Questionnaires (QUE) + - Subgroup 2.7.1: General (GEN) + - Subgroup 2.7.2: CDA validation (CDA) + - Subgroup 2.7.3: hData record format (HRF) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - HFS: Health & Fitness Services Interface + - : This is the device under test: + - SEN: HFS Sender + - REC: HFS receiver + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing: + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP are included. + - Testable item: This contains testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 1.4.1: General (GEN) + +| | | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GEN/BV-000 | | | | +| TP label | Object Hierarchy and Message Construction | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | ObjectHierarchy 1; M | ObjectHierarchy 2; M | ObjectHierarchy 3; M | +| | | ObjectHierarchy 4; M | ObjectHierarchy 5; M | ObjectHierarchy 6; R | +| | | ObjectHierarchy 7; M | ObjectHierarchy 8; M | ObjectHierarchy 9; M | +| | | ObjectHierarchy 10; O | HierarchyAssig 2; M | MessageConst 3; M | +| | | MessageConst 4; M | MessageConst 5; M | MessageConst 6; M | +| | | MessageConst 7; M | MessageConst 8; M | MessageConst 9; M | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | PCD-OBX3-1; M | PCD-OBX3-2; M | PCD-OBX3-3; C | +| Test purpose |

    Check that:

    The devices each have a unique (within the message) MDS number assigned for the hierarchy notation (OBX-4)

    [AND]

    Observations from multiple devices may appear within the scope of the same OBR segment.

    [AND]

    A HFS message must contain a separate OBX specifically for the MDS object of each originating PHD agent

    [AND]

    The MDS-level OBX shall contain the Device's SystemId in OBX-18

    [AND]

    The MDS value '0' is reserved for observations related to the AHD itself

    [AND]

    Virtual Medical Device is not used by the Continua and it must appear as a 0 to signify an anonymous value

    [AND]

    If Channel-level is used, it should be a number that is unique to the specified MDS. If it is not used, it should appear as a 0 to signify an anonymous value

    [AND]

    A Metric element must be used for the individual measurements

    [AND]

    The value of the Metric element must be unique for each instance of a Metric observation

    [AND]

    Facet element must be used for relating values to the core Metric, like measurement status or supplemental type information.

    [AND]

    Each OBX shall be assigned a unique Observation Sub-ID (OBX-4) such that the contextual hierarchy is maintained

    [AND]

    The Continua Services interface requires that an AHD include its own time synchronization information and its certification material, which is accomplished through an OBX with an OBX-4 value of 0.0.0.x

    [AND]

    | | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    The OBX segments shall add the OBXs for the MDS (device) and its relevant attributes

    [AND]

    MDS-level OBX segments shall use the 'X' status code to denote that it is not a physiological 'result'

    [AND]

    The OBX segments may add the OBXs for the device's channel(s) and their relevant attributes

    [AND]

    If it is present, Channel-level OBX segments shall use the 'X' status code to denote that it is not a physiological 'result'

    [AND]

    The OBX segments shall add the OBXs for the device and/or channel's metrics to be reported

    [AND]

    The OBX segments may add FACET-level OBXs for the metric's desired extraneous attributes

    [AND]

    MDS.MODEL is used to provide device vendor/model and shall be mapped at the MDS level in the OBX with the value described by OBX-3.

    [AND]

    MDS.DEVICE TYPE is used to describe the type of the PCD such as monitor, ventilator, infusion pump and shall be mapped at the MDS level in the OBX with the value described by OBX-3.

    [AND]

    For PCDs with complex operation states such as an infusion pump with a set of states like "Stopped", "Infusing Primary", "Infusing Secondary", "Bolus", etc.. or a ventilator with states "Standby", "Ventilating", etc. the Device Operational Status Enumeration Object is mapped to OBX-3.

    | +| Applicability | C_SEN_000 | +| Other PICS | C_SEN_DATA_001, C_SEN_DATA_002, C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. MDS object is contained in a separate OBX segment:
        • OBX-11 = 'X' in MDS-level OBX
        • MDS-level OBX contains in OBX-18 the device's system Id
      2. b. If the CHANNEL-level OBX is present, OBX-11 = 'X'.
      3. c. OBX-3 of the MDS level has the value of the MDS Model and MDS Device Type or the Device Operational Status Enumeration Object (PCD has complex operation states)
      4. d. OBX-4 in each OBX segment indicates the following hierarchy:
        MDS[.VMD[.CHANNEL[.METRIC[.FACET[.SUBFACET]]]]]
        where:
        • The MDS value '0' is reserved for observations related to the AHD itself: its own time synchronization information, its certification material and OBX-4 = 0.0.0.x, where x could be any integer value.
        • The VMD value is '0' because it is not used by Continua.
    | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • CHANNEL-level is used to report compound metrics, and if it is used, it is recommended that it has a unique number value. If CHANNEL-level is not used, it has a '0' value.
    • METRIC is used for individual measurements and its value is unique for each instance of a metric observation.
    • FACET is used for relating values to the core metric.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GEN/BV-001 | | | +| TP label | MSH Segment | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MSH-1; M | MSH-2; M | +| | | MSH-4; M | MSH-5; M | +| | | MSH-7; M | MSH-8; M | +| | | MSH-10; M | MSH-11; M | +| | | MSH-13; M | MSH-14; M | +| | | MSH-16; M | MSH-17; M | +| | | MSH-19; M | MSH-20; M | +| | | MSH-22; M | MSH-23; M | +| | | MSH-25; M | HL7Concept 2; M | +| | | CWEDataType 2; M | CWEDataType 3; C | +| | | DateTimeDataType 1; M | NumericDataType 1; M | +| | | IDDataType 1; M | ISDataType 1; M | +| | | EIDataType 2; O | EIDataType 3; O | +| | | EIUse1; C | EIUse2; C | +| | | EIUse4; C | EIUse3; C | +| | Spec | [IHE PCD TF 2] | | +| | Testable items | HDUse1; M | HDUse2; C | +| | | HD-1; M | HD-2; M | +| | | | HD-3; M | +| Test purpose | Check that:
    The elements of MSH segment of the message
    [AND]
    The data type of each element. | | | +| Applicability | C_SEN_000 | | | +| Other PICS | C_SEN_DATA_001, C_SEN_DATA_002 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a supported device specialization using SOAP or hData observation upload.
    2. Check in the captured message that:
    a. Only one MSH segment is present and that:
    • The character ' ' is the separator element.
    • MSH-2 = '^~\\&' (for the encoding characters element).
    • MSH-3 = <Namespace ID (data type IS)>^<Universal ID (data type ST)>^<Universal Type (data type ID)>
    | | | + +- If C\_SEN\_DATA\_001=TRUE, Namespace ID (HD-1) is optional and may contain a locally unique name for the application implementing PCD actor(s). Universal ID (HD-2) contains the EUI-64 identifier as a hexadecimal string. The IEEE defined 64-bit extended unique identifier (EUI-64) is a concatenation of the 24-bit company\_id value assigned by the IEEE registration authority and a 40-bit extension identifier assigned by the organization having that company\_id assignment. Universal ID (HD-2) contains all three components, Third component (required): EUI-64. + - If C\_SEN\_DATA\_002=TRUE, "Namespace ID" (HD-1) containing the name of the assigning authority, "Universal ID" (HD-2) containing its universal OID, and "Universal ID Type" (HD-3) containing the value ISO. + - Otherwise, if the Universal Type (HD-3) is valued, it takes one of the following values: + - 'DNS' - An Internet dotted name. Either in ASCII or as integers. + - 'GUID' - Same as UUID. + - 'HCD' - The CEN healthcare coding scheme designator. (Identifiers used in DICOM follow this assignment scheme.) + - 'HL7' - Reserved for future HL7 registration schemes. + - 'L','M','N' - These are reserved for locally defined coding schemes. + - 'Random' - Usually a base64 encoded string of random bits. The uniqueness depends on the length of the bits. Mail systems often generate ASCII string "unique names", from a combination of random bits and system names. Obviously, such identifiers will not be constrained to the base64 character set. + - 'URI' - Uniform resource identifier + - 'UUID' - The DCE universal unique identifier + - 'x400' - An X.400 MHS format identifier + - 'x500' - An X.500 directory name. +- ❑ MSH-4, MSH-5 and MSH-6 may be empty, but if they are not empty, they have the same encoding as MSH-3: ^^. +- ❑ MSH-7 is encoded as **YYYYMMDDHHMMSS[.S[S[S[S]]]] [+/-ZZZZ]** (required items in bold) +- ❑ MSH-8 is empty +- ❑ MSH-9 = 'ORU^R01^ORU\_R01' +- ❑ MSH-10 is a string (that uniquely identifies the message) +- ❑ MSH-11 = ^ +- where 'Processing ID' can be one of the following values: +- 'D' for Debugging + - 'P' for Processing + - 'T' for Training. +- and 'Processing Mode', can be one of the following values: +- 'A' for archive + - 'I' for initial load + - 'R' for restore from archive + - 'T' for current processing, transmitted at intervals + - Not present (empty), meaning current processing. +- ❑ MSH-12 = 2.6 + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • MSH-13 should not be valued, but if it is valued, it is a sequence number (it is allowed to have any of these characters: '+','-' and '.')
    • MSH-14 is empty
    • MSH-15 = 'NE'
    • MSH-16 = 'AL'
    • MSH-17 may be empty, but if it is valued, it uses a 3-character (alphabetic) form of ISO 3166.
    • MSH-18 may be empty, but if it is valued, it has one or more of these codes:
      • • 'ASCII' (the default)
      • • '8859/1'
      • • '8859/2'
      • • '8859/3'
      • • '8859/4'
      • • '8859/5'
      • • '8859/6'
      • • '8859/7'
      • • '8859/8'
      • • '8859/9'
      • • '8859/15'
      • • 'ISO IR14'
      • • 'ISO IR87'
      • • 'ISO IR159'
      • • 'GB 18030-2000'
      • • 'KS X 1001'
      • • 'CNS 11643-1992'
      • • 'BIG-5'
      • • 'UNICODE'
      • • 'UNICODE UTF-8'
      • • 'UNICODE UTF-16'
      • • 'UNICODE UTF-32'
    • MSH-19 may be empty, but if it is valued, it is encoded as CWE data type:
      <Identifier (ST)>^<Text (ST)>^< Name of Coding System (ID)> ^<Alternate Identifier (ST)>^<Alternate Text (ST)>^<Name of Alternate Codind System (ID)>^<Coding System Version ID (ST)>^<Alternate Coding System Version ID (ST)>^<Original Text (ST)>
      where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.
    • MSH-20 is empty
    • MSH-21 = <Entity Identifier (data type ST)> ^ <Namespace ID (data type IS)> ^ <Universal ID (data type ST)> ^ <Universal ID Type (data type ID)>, where NamespaceID and UniversalID are 'HL7'
    • MSH-22, MSH-23, MSH-24, MSH-25 are empty
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GEN/BV-002 | | | | +| TP label | PID Segment | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | | | | +| | | PID-1; M | PID-2; M | PID-3; M | +| | | PID-4; M | PID-5; M | PID-6; R | +| | | PID-7; M | PID-8; M | PID-9; M | +| | | PID-10; M | PID-11; M | PID-12; M | +| | | PID-13; M | PID-14; M | PID-15; R | +| | | PID-16; R | PID-17; R | PID-18; R | +| | | PID-19; M | PID-20; M | PID-21; R | +| | | PID-22; R | PID-23; R | PID-24; R | +| | | PID-25; R | PID-26; R | PID-27; R | +| | | PID-28; M | PID-29; R | PID-30; R | +| | | PID-31; R | PID-32; R | PID-33; R | +| | | PID-34; R | PID-35; M | PID-36; M | +| | | PID-37; M | PID-38; M | PID-39; M | +| | | HL7Concept 3; M | CWEDataType 1; M | CWEDataType 2; M | +| | | CWEDataType 3; C | CWEDataType 4; R | DateTimeDataType 1; M | +| | | NumericDataType 1; M | StringDataType 1; M | XADDataType 1; M | +| | | XADDataType 2; O | XADDataType 3; M | XADDataType 4; M | +| | | XADDataType 5; M | XADDataType 6; O | XADDataType 7; M | +| | | XADDataType 8; O | XPNDDataType 1; M | XPNDDataType 2; M | +| | | XPNDDataType 3; M | XPNDDataType 4; M | XPNDDataType 5; M | +| | | XPNDDataType 6; M | XPNDDataType 7; M | XPNDDataType 8; M | +| | | XPNDDataType 9; R | XPNDDataType 10; M | XPNDDataType 11; R | +| | | XPNDDataType 12; R | XPNDDataType 13; R | XPNDDataType 14; R | +| | | CXDataType 1; M | CXDataType 2; R | CXDataType 3; R | +| | | CXDataType 4; M | CXDataType 5; M | CXDataType 6; R | +| | | IDDataType 1; M | ISDataType 1; M | XTNDataType 1; M | +| | | XTNDataType 2; M | XTNDataType 3; M | XTNDataType 4; M | +| | | XTNDataType 5; M | XTNDataType 6; M | XTNDataType 7; M | +| | | XTNDataType 8; M | XTNDataType 9; M | XTNDataType 10; M | +| | | XTNDataType 11; M | | | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | HDUse1; M | HDUse2; C | HDUse3; C | +| | | HD-1; M | HD-2; M | HD-3; M | +| Test purpose | Check that:
    The elements of PID segment of the message
    [AND]
    The data type of each element. | | | | +| Applicability | C_SEN_000 | | | | +| Other PICS | C_SEN_DATA_001, C_SEN_DATA_002, C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | | | | + +| | | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

    Test procedure

    |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a supported device specialization using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Only one PID segment is present and:
        • PID-1 and PID-2 are empty
        • PID-3 is of CX data type: <ID Number (ST)> ^ <Identifier Check Digit (ST)> ^ <Check Digit Scheme (ID)> ^ <Assigning Authority (HD)> ^ <Identifier Type Code (ID)> ^ <Assigning Facility (HD)> ^ <Effective Date (DT)> ^ <Expiration Date (DT)> ^ <Assigning Jurisdiction (CWE)> ^ <Assigning Agency or Department (CWE)>
          • • Subcomponents for assigning authority (HD): <Namespace ID (IS)> & <Universal ID (ST)> & <Universal ID Type (ID)>
          • • Subcomponents for assigning facility (HD): <Namespace ID (IS)> & <Universal ID (ST)> & <Universal ID Type (ID)>
          • • Subcomponents for assigning jurisdiction (CWE): <Identifier (ST)> & <Text (ST)> & <Name of Coding System (ID)> & <Alternate Identifier (ST)> & <Alternate Text (ST)> & <Name of Alternate Coding System (ID)> & <Coding System Version ID (ST)> & <Alternate Coding System Version ID (ST)> & <Original Text (ST)>

          where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.

          • • Subcomponents for assigning agency or department (CWE): <Identifier (ST)> & <Text (ST)> & <Name of Coding System (ID)> & <Alternate Identifier (ST)> & <Alternate Text (ST)> & <Name of Alternate Coding System (ID)> & <Coding System Version ID (ST)> & <Alternate Coding System Version ID (ST)> & <Original Text (ST)>

          where CX-1, CX-4 and CX-5 are required.

        • PID-4 is empty
        • PID-5 is encoded as XPN data type: <Family Name (FN)> ^ <Given Name (ST)> ^ <Second and Further Given Names or Initials Thereof (ST)> ^ <Suffix (e.g., JR or III) (ST)> ^ <Prefix (e.g., DR) (ST)> ^ <DEPRECATED-Degree (e.g., MD) (IS)> ^ <Name Type Code (ID)> ^ <Name Representation Code (ID)> ^ <Name Context (CWE)> ^ <DEPRECATED-Name Validity Range (DR)> ^ <Name Assembly Order (ID)> ^ <Effective Date (DTM)> ^ <Expiration Date (DTM)> ^ <Professional Suffix (ST)>
          • • Subcomponents for family name (FN): <Surname (ST)> & <Own Surname Prefix (ST)> & <Own Surname (ST)> & <Surname Prefix from Partner/Spouse (ST)> & <Surname from Partner/Spouse (ST)>
          • • Subcomponents for name context (CWE): <Identifier (ST)> & <Text (ST)> & <Name of Coding System (ID)> & <Alternate Identifier (ST)> & <Alternate Text (ST)> & <Name of Alternate Coding System (ID)> & <Coding System Version ID (ST)> & <Alternate Coding System Version ID (ST)> & <Original Text (ST)>

          where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.

          • • Subcomponents for name validity range (DR): <Range Start Date/Time (DTM)> & <Range End Date/Time (DTM)>

          where XPN-7 is the only element that needs to be filled, and if it is an 'L' (legal name), it occurs first. Other possible values are:

          • - 'A' - Alias name
          • - 'B' - Name at birth
          • - 'C' - Adopted name
          • - 'D' - Display name
          • - 'I' - Licensing name
          • - 'K' - Artist name
    | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +- 'L' - Legal name +- 'M' - Maiden name +- 'N' - Nickname /"Call me" name/street name +- 'R' - Registered name (animals only) +- 'S' - Coded pseudo-name to ensure anonymity +- 'T' - Indigenous/tribal/community name +- 'U' - Unspecified + +The remaining fields or PID-5 are required but may be empty, except the deprecated one, that must be empty. + +PID-6 should not be valued, but if it is valued, it is encoded as XPN data type, like PID-5. + +PID-7 may be empty. If it is valued, it is encoded as YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ] + +PID-8 may be empty or its value is one of these values: + +- 'A' – Ambiguous +- 'F' – Female +- 'M' – Male +- 'N' – Not applicable +- 'O' – Other +- 'U' – Unknown + +PID-9 is empty + +PID-10 may be empty or its value is of CWE data type: ^ ^ ^ ^ ^ ^ ^ ^ + +and takes one of these values: + +- '1002-5' - American indian or Alaska native +- '2028-9' - Asian +- '2054-5' - Black or African American +- '2076-8' - Native Hawaiian or Other Pacific islander +- '2106-3' - White +- '2131-1' - Other race + +The second triplet of the CWE data type for race (alternate identifier, alternate text, and name of alternate coding system) is reserved for governmentally assigned codes. + +PID-11 may be empty or its value is of XAD data type: ^ ^ ^ ^ ^ ^
    ^ ^ ^ ^
    ^ ^ ^ ^ ^ ^ ^
    ^ ^ ^ ^ ^
    + +- Subcomponents for street address (SAD): & & +- Subcomponents for address validity range (DR): & + +- Subcomponents for expiration reason (CWE): & & & & & & & & +- Subcomponents for protection code (CWE): & & & & & & & & +- Subcomponents for address identifier (EI): & & & + +where XAD-1, XAD-3, XAD-4, XAD-5, XAD-7 are required. The remaining elements are optional. + +PID-12 is empty + +If PID-13 is valued, PCD-01 limits this to two or fewer repetitions with the primary phone number to be the first. It is of XTN data type: ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ + +- Subcomponents for expiration reason (CWE): & & & & & & & & +- Subcomponents for protection code (CWE): & & & & & & & & +- Subcomponents for Shared Telecommunication Identifier (EI): & & & + +where XTN-2 and XTN-3 are required and XTN-4 to XTN-10 are required but may be empty. The rest are not supported. + +PID-14 is empty. + +PID-15 should not be valued + +PID-16 should not be valued, but if it is valued, it takes a value from table 0002 HL7 V2.6 + +PID-17 should not be valued, but if it is valued, it takes a value from table 0006 HL7 V2.6 + +PID-18 should not be valued. + +PID-19 and PID-20 are empty. + +PID-21 should not be valued + +PID-22 should not be valued, but if it is valued, it takes one of these values: + +- 'H' - Hispanic or Latino +- 'N' - Not Hispanic or Latino +- 'U' - Unknown + +PID-23 should not be valued + +PID-24 should not be valued, but if it is valued, it takes one of these values: + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • 'N' - No
    • • 'Y' - Yes

    ❑ PID-25 to PID-29 should not be valued

    ❑ PID-30 and PID-31 should not be valued, but if it is valued, it takes one of these values:

    • • 'N' - No
    • • 'Y' - Yes

    ❑ PID-32 should not be valued, but if it is valued, it takes one of these values:

    • • 'AL' - Patient/Person name is an alias
    • • 'UA' - Unknown/Default address
    • • 'UD' - Unknown/Default date of birth
    • • 'US' - Unknown/Default social security number

    ❑ PID-33 should not be valued

    ❑ PID-34 should not be valued, but if it is valued, PID-34 = <Namespace ID (data type IS)>^<Universal ID (data type ST)>^<Universal Type (data type ID)>

    • • If C_SEN_DATA_001=TRUE, Namespace ID (HD-1) is optional and may contain a locally unique name for the application implementing PCD actor(s). Universal ID (HD-2) contains the EUI-64 identifier as a hexadecimal string. The IEEE defined 64-bit extended unique identifier (EUI-64) is a concatenation of the 24-bit company_id value assigned by the IEEE Registration Authority, and a 40-bit extension identifier assigned by the organization having that company_id assignment. Universal ID (HD-2) contains all three components, third component (required): EUI-64
    • • If C_SEN_DATA_002=TRUE, "Namespace ID" (HD-1) containing the name of the assigning authority, "Universal ID" (HD-2) containing its universal OID, and "Universal ID Type" (HD-3) containing the value ISO
    • • Otherwise, if universal type (HD-3) is valued, it takes one of the following values:
      • - 'DNS' - An Internet dotted name. Either in ASCII or as integers
      • - 'GUID' - Same as UUID.
      • - 'HCD' - The CEN healthcare coding scheme designator. (Identifiers used in DICOM follow this assignment scheme.)
      • - 'HL7' - Reserved for future HL7 registration schemes
      • - 'L','M','N' - These are reserved for locally defined coding schemes.
      • - 'Random' - Usually a base64 encoded string of random bits. The uniqueness depends on the length of the bits. Mail systems often generate ASCII string "unique names", from a combination of random bits and system names. Obviously, such identifiers will not be constrained to the base64 character set.
      • - 'URI' - Uniform resource identifier
      • - 'UUID' - The DCE universal unique identifier
      • - 'x400' - An X.400 MHS format identifier
      • - 'x500' - An X.500 directory name

    ❑ PID-35 to PID-39 are empty, so they cannot be present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GEN/BV-003 | | | +| TP label | PV1 and ORC Segment | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | HL7Concept 4; O | PV1-1; M | +| | Spec | [IHE PCD TF 2] | | +| | Testable items | ORUStaticDefinition4; M | ORCUse; M | +| Test purpose |

    Check that:

    Only one PV1 segment may be sent.

    [AND]

    It is unlikely that this segment will be required for the Services interface so the details have been omitted

    [AND]

    Order Common (ORC) segment shall not be present

    [AND]

    In PCD-03, the Common Order segment (ORC) is used to transmit fields that are common to all orders (all types of services that are requested). In PCD-01, ORC segments are not sent.

    | | | +| Applicability | C_SEN_000 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of a supported device specialization using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. A PV1 segment may be present
      2. An ORC segment is not present.
    | | | +| Pass/Fail criteria | Check that an ORC segment is not present. | | | +| Notes | | | | + +| | | | | +|-----------------|-----------------------------------|-----------------------|------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GEN/BV-004 | | | +| TP label | OBR Segment | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | HL7Concept 5; M | OBR-1; M | +| | | OBR-3; M | OBR-4; M | +| | | OBR-6; M | OBR-9; M | +| | | NTE-1; M | NTE-2; M | +| | | NTE-4; M | NTE-5; O | +| | | NTE-7; M | NTE-8; M | +| | | CWEDataType 2; M | CWEDataType 3; C | +| | | DateTimeDataType 1; M | EIDataType 1; M | +| | | EIDataType 3; O | EIDataType 4; O | +| | | EIUse2; C | EIUse3; C | +| | | IDDataType 1; M | ISDataType 1; M | +| | | | SIDataType 1; M | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    The elements of OBR segment of the message and its respective NTE optional segment
    [AND]
    The data type of each element.

    | +| Applicability | C_SEN_000 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a supported device specialization using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. An OBR segment is present, but there may be more than one and:
        • OBR-1 starts with 1 and increases sequentially in following OBR segments if there are more than one.
        • OBR-2 is of EI data type encoded as: <Entity Identifier (ST)> ^ <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>
          If there is an existing order, OBR-2 is set to the identifier of the system that has placed that order. If there is no order or a standing one:
          • • The first component is the order ID that is simply an arbitrary string.
          • • The second component contains an HD that identifies the application which implements the HFS client component.
          • • The third component contains the EUI-64 of the device which implements the HFS client component.
        • OBR-3 is of EI data type encoded as: <Entity Identifier (ST)> ^ <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>
          • • The first component is an arbitrary order ID string,
          • • The second, third and fourth components are used like an HD to identify the application which implements the HFS client component and shall contain the EUI-64 of this device. For "standing orders", this value should match OBR-2.
        • OBR-4 is of CWE data type encoded as: <Identifier (ST)> ^ <Text (ST)> ^ <Name of Coding System (ID)> ^ <Alternate Identifier (ST)> ^ <Alternate Text (ST)> ^ <Name of Alternate Coding System (ID)> ^ <Coding System Version ID (ST)> ^ <Alternate Coding System Version ID (ST)> ^ <Original Text (ST)>, where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.
          It contains the identifier code for the requested observation/test/battery. This can refer to specific existing orders, or nonspecific "standing" orders.
          When reporting events related to "standing" orders, these codes will likely describe a generic service such as:
          • • '266706003^continuous ECG monitoring^SNOMED-CT'
          • • '359772000^glucose monitoring at home^SNOMED-CT'
          • • '182777000^monitoring of patient^SNOMED-CT'.
        • OBR-5, OBR-6 and OBR-9 through to OBR-50 are empty
        • If valued, OBR-7 is of DTM data type encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • If valued, OBR-8 is of DTM data type encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      2. b. If the NTE segment is present:
        • NTE-1 is a non-negative number required for distinguishing when multiple NTE segments appear in a message.
    | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • NTE-2 is empty
    • NTE-3 may be empty, but if it is valued, it is a text comment.
    • NTE-4 is empty
    • If NTE-5 is present, it is of type XCN encoded as: <ID Number (ST)>^<Family Name (FN)>^<Given Name (ST)>^<Second and Further Given Names or Initials Thereof (ST)>^<Suffix (ST)>^<Prefix (ST)>^<DEPRECATED-Degree (IS)>^<Source Table (IS)>^<Assigning Authority (HD)>^<Name Type Code (ID)>^<Identifier Check Digit (ST)>^<Check Digit Scheme (ID)>^<Identifier Type Code (ID)>^<Assigning Facility (HD)>^<Name Representation Code (ID)> ^ <Name Context (CWE)> ^ <DEPRECATED-Name Validity Range (DR)> ^ <Name Assembly Order (ID)> ^ <Effective Date (DTM)> ^ <Expiration Date (DTM)> ^ <Professional Suffix (ST)> ^ <Assigning Jurisdiction (CWE)> ^ <Assigning Agency or Department (CWE)>
      • • Subcomponents for family name (FN): <Surname (ST)> & <Own Surname Prefix (ST)> & <Own Surname (ST)> & <Surname Prefix from Partner/Spouse (ST)> & <Surname from Partner/Spouse (ST)>
      • • Subcomponents for assigning authority (HD): <Namespace ID (IS)> & <Universal ID (ST)> & <Universal ID Type (ID)>
      • • Subcomponents for assigning facility (HD): <Namespace ID (IS)> & <Universal ID (ST)> & <Universal ID Type (ID)>
      • • Subcomponents for name context (CWE): <Identifier (ST)> & <Text (ST)> & <Name of Coding System (ID)> & <Alternate Identifier (ST)> & <Alternate Text (ST)> & <Name of Alternate Coding System (ID)> & <Coding System Version ID> & <Alternate Coding System Version ID (ST)> & <Original Text (ST)>, where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.
      • • Subcomponents for name validity range (DR): <Range Start Date/Time (DTM)>&<Range End Date/Time>
      • • Subcomponents for assigning jurisdiction (CWE): <Identifier (ST)> & <Text (ST)> & <Name of Coding System (ID)> & <Alternate Identifier (ST)> & <Alternate Text (ST)> & <Name of Alternate Coding System (ID)> & <Coding System Version ID> & <Alternate Coding System Version ID (ST)> & <Original Text (ST)>, where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.
      • • Subcomponents for assigning agency or department (CWE): <Identifier (ST)> & <Text (ST)> & <Name of Coding System (ID)> & <Alternate Identifier (ST)> & <Alternate Text (ST)> & <Name of Alternate Coding System (ID)> & <Coding System Version ID> & <Alternate Coding System Version ID (ST)> & <Original Text (ST)>, where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.

    NTE-6, NTE-7 and NTE-8 are empty

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------|-----------------|----------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GEN/BV-005 | | | +| TP label | TQ1 Segment | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | HL7Concept 6; R | TQ1-1; M | +| Test purpose | Check that:
    Timing/Quality (TQ1) segment should not be used on the Services interface | | | +| Applicability | C_SEN_000 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a supported device specialization using SOAP or hData observation upload.
    2. Check in the captured message that:
    a. It is recommended that a TQ1 segment is not present. | +| Pass/Fail criteria | It is recommended that a TQ1 segment is not present. If it is present, issue a warning trace log message. | +| Notes | | + +| | | | | | +|--------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------| +| TP Id | | TP/HFS/SEN/PCD-01-DATA/GEN/BV-006 | | | +| TP label | | OBX Segment | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | HL7Concept 8; M | HL7Concept 9; O | OBR-7; M | +| | | OBR-8; M | OBX-1; M | OBX-2; M | +| | | OBX-3; M | OBX-4; M | OBX-6; M | +| | | OBX-7; M | OBX-8; M | OBX-9; M | +| | | OBX-10; M | OBX-11; M | OBX-12; M | +| | | OBX-13; M | OBX-14; M | OBX-15; M | +| | | OBX-16; M | OBX-17; M | OBX-18; M | +| | | OBX-19; M | OBX-20; M | OBX-21; M | +| | | NTE-1; M | NTE-2; M | NTE-3; M | +| | | NTE-4; M | NTE-5; O | NTE-6; M | +| | | NTE-7; M | NTE-8; M | CWEDataType 1; M | +| | | CWEDataType 2; M | CWEDataType 3; C | CWEDataType 4; R | +| | | DateTimeDataType 1; M | NumericDataType 1; M | StringDataType 1; M | +| | | EIDataType 1; M | EIDataType 2; O | EIDataType 3; O | +| | | EIDataType 4; O | EIUse1; C | EIUse2; C | +| | | EIUse3; C | EIUse4; C | IDDataType 1; M | +| | | ISDataType 1; M | SIDataType 1; M | | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | PCD-OBX2; M | | | +| Test purpose | | Check that:
    The elements of OBX segment of the message and its respective NTE optional segment
    [AND]
    The data type of each element. | | | +| Applicability | | C_SEN_000 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | | | +| Test procedure | | 1. Make the HFS sender under test send a HL7 message containing an observation of a supported device specialization using SOAP or hData observation upload.
    2. Check in the captured message that:
    a. An OBX segment is present, but there may be more than one and:
    OBX-1 is a sequence number of the OBX in the message. | | | + +- ❑ OBX-2 is one of these values: CWE, CF, DT, DTM, ED, FT, NA, NM, SN, ST, TM, TX, XAD, XCN, XON, XPN, or may be empty; and matches with the data type of the value of OBX-5. +- ❑ OBX-3 is of CWE data type encoded as: ^ ^ ^ ^ ^ ^ ^ ^ , where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present. +- ❑ OBX-4 is a string of type a[.b[.c[.d[.e]]]] +- ❑ OBX-6, if valued, is of CWE data type encoded as: ^ ^ ^ ^ ^ ^ ^ ^ , where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present. +- ❑ OBX-7 is of ST data type, but may be empty. +- ❑ OBX-8 is one of these values: L, H, LL, HH, <, >, N, A, AA, null, U, D, B, W, S, R, I, MS, VS, or may be empty. +- ❑ OBX-9 is empty. +- ❑ OBX-10 is recommended to be empty, but if it is valued, it is one of these values: A, N, R, S, SP, B or ST. +- ❑ OBX-11 is one of these values: C, D, F, I, N, O, P, R, X, U or W. +- ❑ OBX-12 and OBX-13 are empty. +- ❑ OBX-14 may be empty, but if it is valued, it is of DTM data type encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]. This timestamp is greater than or equal to OBR-7 and less than OBR-8, if they are valued. +- ❑ OBX-15 is recommended to be empty, but if it is valued, it is of CWE data type, encoded as: ^ ^ ^ ^ ^ ^ ^ ^ , where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present. +- ❑ OBX-16 may be empty, but if it is valued, it is of XCN data type, encoded as: ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ + - Subcomponents for family name (FN): & & & & + - Subcomponents for assigning authority (HD): & & + - Subcomponents for assigning facility (HD): & & + - Subcomponents for name context (CWE): & & & & & & & & + - Subcomponents for name validity range (DR): & + +- Subcomponents for assigning jurisdiction (CWE): & & & & & & & & + - Subcomponents for assigning agency or department (CWE): & & & & & & & & +- ❑ OBX-17 may be empty, but if it is valued, it is of CWE data type, encoded as: ^ ^ ^ ^ ^ ^ ^ ^ , where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present. + - ❑ If valued, OBX-18 is of EI data type, encoded as: ^ ^ ^ , where "Namespace ID" is recommended to be EUI-64. + - ❑ OBX-19 is recommended to be empty, but if it is valued, OBX-19 = OBX-14. + - ❑ OBX-20 may be empty, but if it is valued, it is of type CWE with an appropriate MDC code for the observation. + - ❑ OBX-21 to OBX-25 are strongly recommended to be empty. +- b. If the NTE segment is present: +- ❑ NTE-1 is a non-negative number required for distinguishing when multiple NTE segments appear in a message + - ❑ NTE-2 is empty + - ❑ NTE-3 may be empty, but if it is valued, it is a text comment + - ❑ NTE-4 is empty + - ❑ If NTE-5 is present, it is of type XCN encoded as: ^^^^^^^^^^^^^^ ^ ^ ^ ^ ^ ^ ^ ^ + - Subcomponents for family name (FN): & & & & + - Subcomponents for assigning authority (HD): & & + - Subcomponents for assigning facility (HD): & & + - Subcomponents for name context (CWE): & & & & & & & & , where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present. + - Subcomponents for name validity range (DR): & + - Subcomponents for assigning jurisdiction (CWE): & & & & & (ID) & <Coding System Version ID> & <Alternate Coding System Version ID (ST)> & <Original Text (ST)>, where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.

    • Subcomponents for assigning agency or department (CWE): <Identifier (ST)> & <Text (ST)> & <Name of Coding System (ID)> & <Alternate Identifier (ST)> & <Alternate Text (ST)> & <Name of Alternate Coding System (ID)> & <Coding System Version ID> & <Alternate Coding System Version ID (ST)> & <Original Text (ST)>, where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.

    NTE-6, NTE-7 and NTE-8 are empty

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | OBX-5 is avoided and tested in each specialization because it can have any data type value. | + +| | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-----------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GEN/BV-007 | | | | | +| TP label | Timestamping and Time Synchronization | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | Timestamp 3; M | Timestamp 4; C | | | +| | | Timestamp 9; O | Timestamp 10; M | | | +| | | Timestamp 12; O | Timestamp 13; O | | | +| | | Timestamp 16; O | Timestamp 17; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22, M | | | | +| Test purpose |

    Check that:

    Time synchronization elements from the AHD are as required.

    | | | | | +| Applicability | C_SEN_000 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of a supported device specialization using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. In OBX segments:
        • Each MDC code using a CWE data type is encoded as:
          <refIdValue>^<refIdName>^<refIdCodeSystem>
          where:
          • refIdValue: is a 32 bit integer (required)
          • refIdName: is the normative nomenclature name for the unique code point (recommended)
          • refIdCodeSystem = "MDC" (required).
        • MDC_TIME_SYNC_PROTOCOL is present as an independent OBX segment with:
          • OBX-2 = 'CWE'
          • OBX-3 = '68220^MDC_TIME_SYNC_PROTOCOL^MDC'
          • OBX-4 = 0.x.y.z, where x, y, z could be any integer value
          • OBX-5 = One of these values:
            532224^MDC_TIME_SYNC_NONE^MDC
    | | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    532225^MDC_TIME_SYNC_NTPV3^MDC

    532226^MDC_TIME_SYNC_NTPV4^MDC

    532227^MDC_TIME_SYNC_SNTPV4^MDC

    532228^MDC_TIME_SYNC_SNTPV4330^MDC

    532229^MDC_TIME_SYNC_BTV1^MDC

    532230^MDC_TIME_SYNC_RADIO^MDC

    532231^MDC_TIME_SYNC_HL7_NCK^MDC

    532232^MDC_TIME_SYNC_CDMA^MDC

    532233^MDC_TIME_SYNC_GSM^MDC

    532234^MDC_TIME_SYNC_EBWW^MDC

    532235^MDC_TIME_SYNC_USB_SOF^MDC

    • If another MDC_TIME_SYNC_PROTOCOL is present, it has an OBX-4 with an MDS-level different to 0, the rest of the elements of the OBX segment are the same as above.
    • If MDC_TIME_SYNC_PROTOCOL is MDC_TIME_SYNC_NONE, MDC_TIME_SYNC_ACCURACY is not present
    • If MDC_TIME_SYNC_ACCURACY is present and the synchronization protocol used is NTP, the value of the accuracy, OBX-5, is calculated using this formula: (\text{root dispersion} + 1/2 * \text{root delay}) * \text{clock drift}
    • If relative time or Hi-Res Relative time are present as an AHD observation (OBX-4 = 0.0.0.x), where x could be any integer value:
      • • if the time synchronization between this relative or high-resolution relative clock is known relative to UTC, it is disclosed in OBX-14
      • • OBX-18 contains a Timebase Id.
      • • their respective resolution can be present: MDC_TIME_RES_REL or MDC_TIME_RES_HI_REL
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GEN/BV-008 | | | +| TP label | HFS Client Regulatory Information | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | AHDObject 2; M | AHDObject 3; M | +| | | AHDObject 5; M | AHDObject 6; M | +| | | AHDObject 8; M | AHDObject 10; M | +| | | AHDObject 12; M | AHDObject 13; M | +| | | AHDObject 15; M | AHDObject 16; M | +| | | AHDObject 18; M | AHDObject 19; M | +| | | AHDObject 21; M | AHDObject 22; M | +| | | MeasureStatus 3; M | ObjectHierarchy 4; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 10; M | DataGuidelines 21; M | +| Test purpose | Check that:
    HFS client components shall include their regulatory information as a subcomponent (METRIC) of the AHD-level OBX in a special set of zero-level OBX segments. | | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_SEN_000 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a supported device specialization using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The set of zero-level OBX segments for the AHD occurs only once in a PCD-01 document after the first OBR entry.
      2. b. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      3. c. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit.
      4. d. Specific AHD shall follow this OBX encoding:
        • OBX-2 shall be empty
        • OBX-3 = 531981^ MDC_MOC_VMS_MDS_AHD^MDC
        • OBX-4 = 0
        • OBX-11 = 'X' or 'R'
        • OBX-18 (System-Id attribute) = <Entity Identifier (ST)>^EUI-64
      5. e. Time-Sync-Protocol attribute shall be sent as an independent OBX segment with the following mandatory fields:
        • OBX-2 = 'CWE'
        • OBX-2 = '68220^MDC_TIME_SYNC_PROTOCOL^MDC'
        • OBX-4 = 0.0.0.a, being 'a' a number indicating the metric level.
        • OBX-5 = A valid nomenclature code from nom-part-infrastruct partition.
        • OBX-11 = 'X' or 'R'
      6. f. Time-Sync-Accuracy attribute, if present, shall be sent as an independent OBX segment with the following mandatory fields:
        • OBX-2 = 'NM'
        • OBX-3 = 68221^MDC_TIME_SYNC_ACCURACY^MDC
        • OBX-4 = 0.0.0.b, being 'b' a number indicating the metric level.
        • OBX-5 = NM data type value
        • OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC
        • OBX-11 = 'X' or 'R'
      7. g. Time-Resolution-Abs-Time attribute, if present, shall be sent as an independent OBX segment with the following mandatory fields:
        • OBX-2 = 'NM'
        • OBX-3 = 68222^MDC_TIME_RES_ABS^MDC
        • OBX-4 = 0.0.0.c, being 'c' a number indicating the metric level.
        • OBX-5 = NM data type value
    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC
    • OBX-11 = 'X' or 'R'

    h. Relative-Time attribute, if present, shall be sent as an independent OBX segment with the following mandatory fields:

    • OBX-2 = 'NM'
    • OBX-3 = 67983^MDC_ATTR_TIME_REL^MDC
    • OBX-4 = 0.0.0.d, being 'd' a number indicating the metric level.
    • OBX-5 = NM data type value
    • OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC
    • OBX-11 = 'X' or 'R'
    • OBX-18 = A unique identifier for the given time base.

    i. Time-Resolution-Rel-Time attribute, if present, shall be sent as an independent OBX segment with the following mandatory fields:

    • OBX-2 = 'NM'
    • OBX-3 = 68223^MDC_TIME_RES_REL^MDC
    • OBX-4 = 0.0.0.e, being 'e' a number indicating the metric level.
    • OBX-5 = NM data type value
    • OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC
    • OBX-11 = 'X' or 'R'

    j. HiRes-Relative-Time attribute, if present, shall be sent as an independent OBX segment with the following mandatory fields:

    • OBX-2 = 'NM'
    • OBX-3 = 68072^MDC_ATTR_TIME_REL_HI_RES^MDC
    • OBX-4 = 0.0.0.f, being 'f' a number indicating the metric level.
    • OBX-5 = NM data type value
    • OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC
    • OBX-11 = 'X' or 'R'
    • OBX-18 = A unique identifier for the given time base.

    k. Time-Resolution-High-Res-Time attribute shall be sent as an independent OBX segment with the following mandatory fields:

    • OBX-2 = 'NM'
    • OBX-3 = 68224^MDC_TIME_RES_REL_HI_RES^MDC
    • OBX-4 = 0.0.0.g, being 'g' a number indicating the metric level.
    • OBX-5 = NM data type value
    • OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC
    • OBX-11 = 'X' or 'R'

    l. AHD-Reg-Cert-Data-List is sent as an attribute of the device using three separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields:

    • OBX-2 = 'CWE'
    • OBX-3 = 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC
    • OBX-4 = 0.0.0.h, being 'h' a number indicating the metric level.
    • OBX-5 = One of:
                0^auth-body-empty,
                1^auth-body-ieee-11073,
                2^auth-body-continua,
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    254^auth-body-experimental,
    255^auth-body-reserved

    ❑ OBX-11 = 'X' or 'R'

    m. AHD-Reg-Cert-Data-List will be sent using four separate attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments:

    ❑ Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'ST'
    • • OBX-3 = 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC
    • • OBX-4 = 0.0.0.y.a, where 'y' is a number indicating the metric level of one of the three Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 =<major-IG-version>.<minor-IG-version>,
    • • OBX-11 = 'X' or 'R'

    ❑ Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'NA'
    • • OBX-3 = 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC
    • • OBX-4 = 0.0.0.x.b, where 'x' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry and 'b' is a number indicating the facet level of that segment.
    • • OBX-5 = NA value listing the certified devices.
    • • OBX-11 = 'X' or 'R'

    ❑ Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'CWE'
    • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
    • • OBX-4 = 0.0.0.y.a, where 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute or the Regulation-Certification-Continua-AHD-Cert-List attribute as a Facet entry, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    ❑ Regulation- Certification-Continua-AHD-Cert-List attribute shall be sent as an independent OBX segment with the following mandatory fields:

    • • OBX-2 = 'CWE'
    • • OBX-3 = 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST ^MDC
    • • OBX-4 = 0.0.0.z.a, where 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute or the Regulation-Certification-Continua-Regulation-Status attribute as a facet entry and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = a list of AHD certification properties: 0~1
    • • OBX-11 = 'X' or 'R'
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +## A.3 Subgroup 1.4.2: Design guidelines (DG) + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/DG/BV-000 | | | +| TP label | DataGuidelines | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 4; M | DataGuidelines 6; M | +| | | DataGuidelines 22; M | DataGuidelines 7; M | +| Test purpose |

    Check that:

    Continua HFS client component observations shall use the Medical Device Communication (MDC) coding system for all Observation Identifiers (OBX-3, OBX-20).

    [AND]

    All Observation Result segments should terminate after their last non-empty sequence.

    [AND]

    For observations which originate from a Continua PHD, the HFS client component shall include an MDS-level OBX segment with an Observation Identifier equal to the MDC Device Specialization Profile reported by the PHD.

    [AND]

    When encoding MDC codes using the HL7 CWE data type, HFS client components shall use the format of <refldValue>^<refldName><refldCodeSystem>

    Where:

    • - refldValue: is the 32 bit integer that corresponds to the unique code point
    • - refldName: the normative nomenclature name for the unique code point
    • - refldCodeSystem: the value shall always be "MDC"

    The values for refldValue and refldCodeSystem shall always be present and the value for refldName should be present.

    | | | +| Applicability | C_SEN_000 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a supported device specialization using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. It is recommended that each segment terminates when the last non-empty element appears.
      2. b. In the OBX segment of MDS-level:
        • each MDC code using a CWE data type is encoded as:
          <refldValue>^<refldName><refldCodeSystem>
          where:
          • • refldValue: is a 32 bit integer (required)
          • • refldName: is the normative nomenclature name for the unique code point (recommended)
          • • refldCodeSystem = "MDC" (required).
        • OBX-3 uses one of these observation Ids, corresponding to the specific Continua PHD used:
          • • Pulse oximeter:
            528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC
          • • Blood pressure monitor: 528391^MDC_DEV_SPEC_PROFILE_BP^MDC
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Thermometer: 528392^MDC_DEV_SPEC_PROFILE_TEMP^MDC
    • Weighing scales: 528399^MDC_DEV_SPEC_PROFILE_SCALE^MDC
    • Glucose meter: 528401^MDC_DEV_SPEC_PROFILE_GLUCOSE^MDC
    • Cardiovascular:
      528425^MDC_DEV_SPEC_PROFILE_HF_CARDIO^MDC
    • Strength fitness:
      528426^MDC_DEV_SPEC_PROFILE_HF_STRENGTH^MDC
    • Independent living hub:
      528455^MDC_DEV_SPEC_PROFILE_AI_ACTIVITY_HUB^MDC
    • Adherence monitor:
      528456^MDC_DEV_SPEC_PROFILE_AI_MED_MINDER^MDC
    • Peak expiratory flow monitor:
      528405^MDC_DEV_SPEC_PROFILE_PEFM^MDC
    • Body composition analyser:
      528404^MDC_DEV_SPEC_PROFILE_BCA^MDC
    • Basic electrocardiograph:
      528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC and OBX-5 of System-Type-Spec-List attribute = 528390^MDC_DEV_SPEC_PROFILE_ECG^MDC and at least one of the following two profile values:
      528524^MDC_DEV_SUB_SPEC_PROFILE_ECG^MDC
      528525^MDC_DEV_SUB_SPEC_PROFILE_HR^MDC
    • International Normalized Ratio:
      528406^MDC_DEV_SPEC_PROFILE_COAG^MDC
    • Sleep Apnoea Breathing Therapy Equipment:
      528409^MDC_DEV_SPEC_PROFILE_SABTE^MDC
    • Insulin Pump:
      528403^MDC_DEV_SPEC_PROFILE_INSULIN_PUMP^MDC
    • Continuous Glucose Monitor:
      528410^MDC_DEV_SPEC_PROFILE_CGM^MDC
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +## A.4 Subgroup 1.4.3: Pulse oximeter (PO) + +| | | | | +|-----------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PO/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MDSCClassAttr 1; M
    MDSCClassAttr 4; M
    MDSCClassAttr 7; O
    MDSCClassAttr 10; C
    MDSCClassAttr 13; M
    MDSCClassAttr 16; M
    MDSSObject 1; M
    MDSSObject 4; M
    MDSSObject 7; M
    MDSSObject 10; M
    MDSSObject 13; O
    MDSSObject 16; M | MDSCClassAttr 2; C
    MDSCClassAttr 5; M
    MDSCClassAttr 8; M
    MDSCClassAttr 11; C
    MDSCClassAttr 14; M
    MDSCClassAttr 17; C
    MDSSObject 2; M
    MDSSObject 5; M
    MDSSObject 8; M
    MDSSObject 11; M
    MDSSObject 14; O
    MDSSObject 17; M | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|----------------------| +| | | MDSObject 19; M | MDSObject 20; M | MDSObject 21; M | +| | | MDSObject 22; M | MDSObject 23; M | MDSObject 24; M | +| | | MDSObject 25; M | MDSObject 26; M | MDSObject 27; M | +| | | MDSObject 28; M | MDSObject 29; M | MDSObject 30; M | +| | | MDSObject 31; M | MDSObject 32; M | PulseOx 4; M | +| | | Timestamp 13; O | Timestamp 14; O | Timestamp 15; O | +| | | Timestamp 17; M | | | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | DeviceTimeSync1; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values | | | | +| Applicability | C_SEN_000 AND C_SEN_PO_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a pulse oximeter device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a pulse oximeter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present.
      2. b. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32-bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      3. c. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit.
      4. d. In MDS-level OBX:
        • OBX-2 is empty
        • If the System-Type attribute is valued, OBX-3 = 528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC
        • If System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3
        • If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC and the specialization list is reported as an attribute of the device.
        • If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD
        • OBX-11 = 'X'
    | | | | + +- OBX-18 (System Id attribute) = ^^^EUI-64, where the System Id is 16 characters given by the PIXIT I\_SEN\_PO\_001. + +e. System model attribute is sent in two different OBX segments: + +- System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = a string representing the model number portion of the MDC\_ATTR\_ID\_MODEL attribute +- System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = a string representing the model manufacturer portion of the MDC\_ATTR\_ID\_MODEL attribute. + +f. Production-Specification attribute is sent as a series of attributes: + +- Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = a string representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + +- OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) +- Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) + +- ❑ Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-2 = 'NM'
    • • OBX-3 = 68222^MDC_TIME_RES_ABS^MDC
    • • OBX-5 = NM data type value
    • • OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC

    Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment:

    • • OBX-2 = 'NM'
    • • OBX-3 = 68223^MDC_TIME_RES_REL^MDC
    • • OBX-5 = NM data type value
    • • OBX-6 = 264320^MDC_DIM_SEC^MDC

    Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment:

    • • OBX-2 = 'NM'
    • • OBX-3 = 68224^MDC_TIME_RES_HI_RES^MDC
    • • OBX-5 = NM data type value
    • • OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC

    h. Date-and-Time-Adjustment attribute is not present.

    i. If the Power-Status attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'ST'
    • OBX-3 = 67925^MDC_ATTR_POWER_STAT^MDC
    • OBX-5 = One or more of:
      • <0 or 1>^onMains(0),
      • <0 or 1>^onBattery(1),
      • <0 or 1>^chargingFull(8),
      • <0 or 1>^chargingTrickle(9),
      • <0 or 1>^chargingOff(10)

    j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'NM'
    • OBX-3 = 67996^MDC_ATTR_VAL_BATT_CHARGE^MDC
    • OBX-5 = NM data type value
    • OBX-6 = 262688^MDC_DIM_PERCENT^MDC

    k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'NM'
    • OBX-3 = 67976^MDC_ATTR_TIME_BATT_REMAIN^MDC
    • OBX-5 = Use the value contained in the BatMeasure object
    • OBX-6 = Use the OID contained in the BatMeasure object

    l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields:

    • OBX-2 = 'CWE'
    • OBX-3 = 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC
    • OBX-5 = One of:
      • 0^auth-body-empty,
      • 1^auth-body-ieee-11073,
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2^auth-body-continua,
    254^auth-body-experimental,
    255^auth-body-reserved

    m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments:

    • Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding:
      • • OBX-2 = 'ST'
      • • OBX-3 = 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC
      • • OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the Facet level of that segment.
      • • OBX-5 = <major-IG-version>.<minor-IG-version>.
    • Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding:
      • • OBX-2 = 'NA'
      • • OBX-3 = 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC
      • • OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'b' is a number indicating the facet level of that segment.
      • • OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 4 (PO v1.0), 16388 (PO v1.5 Wireless PAN), 8196 (PO v1.5 Wired PAN), or 24580 (PO v1.5 Sensor LAN)
    • Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding:
      • • OBX-2 = 'CWE'
      • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
      • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
      • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If the System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'CWE'
    • OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | +|-----------------|----------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PO/BV-001 | +| TP label | SpO2 Numeric Object | + +| | | | | | +|--------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | PulseOx 1; M | PulseOx 5; M | PulseOx 6; M | +| | | PulseOx 7; M | PulseOx 8; M | PulseOx 9; M | +| | | PulseOx 10; M | PulseOx 11; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | MeasureStatus 1; M | MeasureStatus 2; M | MeasureStatus 3; M | +| | | MeasureStatus 4; R | MeasureStatus 5; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | | Check that:
    The presence of the attributes of the SpO2 Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_PO_001 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a pulse oximeter device. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a pulse oximeter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one SpO2 object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present.
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit.
      5. e. The SpO2 object follows this OBX encoding:
        • OBX-2 = 'NM'
    | | | + +- OBX-3 = 150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC +- OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the SpO2 object respectively. +- OBX-5 = Numeric value +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC +- OBX-11 has one of the following values: + - 'X', in the case of invalid, not-available or ongoing measurements (specified in the Measurement Status attribute) + - 'F', in the case where a validated-data Measurement Status bit is set + - 'R', in the other case (even if the Measurement Status is not present) + +f. If the SpO2 Modality attribute is present, it follows this OBX encoding: + +- OBX-2 = 'CWE' +- OBX-3 = 68193^MDC\_ATTR\_SUPPLEMENTAL\_TYPES^MDC +- OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the SpO2 object. +- OBX-5 = 150580^MDC\_MODALITY\_FAST^MDC or 150584^MDC\_MODALITY\_SLOW^MDC or 150588^MDC\_MODALITY\_SPOT^MDC + +g. If SpO2 Accuracy attribute is present, it follows this OBX encoding: + +- OBX-2 = 'NM' +- OBX-3 = 67914^MDC\_ATTR\_NU\_ACCUR\_MSMT^MDC +- OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the SpO2 object. +- OBX-5 = Numeric value +- OBX-6 = 264320^MDC\_DIM\_SEC^MDC + +h. If SpO2 Alert-Op-State attribute is present, it follows this OBX encoding: + +- OBX-2 = 'CWE' +- OBX-3 = 67846^MDC\_ATTR\_AL\_OP\_STAT^MDC +- OBX-4 = y.0.0.x.c, where 'c' is a number indicating the facet level of the SpO2 object. +- OBX-5 = One of the values: + - <0 or 1>^lim-alert-off(0), + - <0 or 1>^lim-low-off(1), or + - <0 or 1>^lim-high-off(2) +- OBX-6 = empty + +i. If SpO2 Current-Limits attribute is present, it follows this OBX encoding: + +- OBX-2 = 'NM' +- OBX-3 = 67892^MDC\_ATTR\_LIMIT\_CURR^MDC +- OBX-4 = y.0.0.x.d, where 'd' is a number indicating the facet level of the SpO2 object. +- OBX-5 = ~ +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC + +j. If SpO2 Alert-Op-Text-String attribute is present, it follows this OBX encoding: + +- OBX-2 = 'ST' +- OBX-3 = 68014^MDC\_ATTR\_AL\_OP\_TEXT\_STRING^MDC +- OBX-4 = y.0.0.x.e, where 'e' is a number indicating the facet level of the SpO2 object. + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    OBX-5 = <lower limit text (ST)> ~ <upper limit text (ST)>

    k. If SpO2 Measurement Status attribute is present, it follows this OBX encoding:

    OBX-2 = 'CWE'

    OBX-3 = 67911^MDC_ATTR_MSMT_STAT^MDC

    OBX-4 = y.0.0.x.f, where 'f' is a number indicating the facet level of the SpO2 object.

    OBX-5 = One of the values:

    <0 or 1>^invalid(0),
    <0 or 1>^questionable(1),
    <0 or 1>^not-available(2),
    <0 or 1>^calibration-ongoing(3),
    <0 or 1>^test-data(4),
    <0 or 1>^demo-data(5),
    <0 or 1>^validated-data(8),
    <0 or 1>^early-indication(9),
    <0 or 1>^msmt-ongoing(10),
    <0 or 1>^msmt-state-in-alarm(14),
    <0 or 1>^msmt-state-al-inhibited(15)

    l. If the SpO2Measurement Status attribute is present, OBX-8 of the SpO2 object has one of these values depending of the active flag in the attribute:

    invalid(0) → OBX-8 = 'INV',

    questionable(1) → OBX-8 = 'QUES',

    not-available(2) → OBX-8 = 'NAV',

    calibration-ongoing (3) → OBX-8 = 'CAL',

    test-data (4) → OBX-8 = 'TEST',

    demo-data (5) → OBX-8 = 'DEMO',

    validated-data (8) → OBX-8 = (empty),

    early-indication (9) → OBX-8 = 'EARLY',

    msmt-ongoing (10) → OBX-8 = 'BUSY',

    msmt-state-in-alarm (14) → OBX-8 = 'ALACT',

    msmt-state-al-inhibited(15) → OBX-8 = 'ALINH'.

    m. No PM-Store, PM-Segment or Scanner attributes are present.

    n. One of the timestamp attributes can be present:

    MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]

    MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:

    • • OBX-5 = Numeric value
    • • OBX-18 has a timebase ID.

    MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.

    • • OBX-5 = Numeric value
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PO/BV-002 | | | | | +| TP label | PulseRate Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | PulseOx 1; M | PulseOx 12; M | | | +| | | PulseOx 14; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | | | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | | | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | | | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the PulseRate Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_PO_001 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a pulse oximeter device. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a pulse oximeter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one PulseRate object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. PulseRate object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 149530^MDC_PULS_OXIM_PULS_RATE^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the PulseRate object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264864^MDC_DIM_BEAT_PER_MIN^MDC
    | | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    e. If a PulseRate Modality attribute is present, it follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the PulseRate object.
    • OBX-5 = 150580^MDC_MODALITY_FAST^MDC or 150584^MDC_MODALITY_SLOW^MDC or 150588^MDC_MODALITY_SPOT^MDC

    f. If a PulseRate Accuracy attribute is present, it follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 67914^MDC_ATTR_NU_ACCUR_MSMT^MDC
    • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the Facet level of the PulseRate object.
    • OBX-5 = Numeric value
    • OBX-6 = 264320^MDC_DIM_SEC^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PO/BV-003 | | | | +| TP label | Plethysmographic Waveform RT-SA Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | PulseOx 1; M | PulseOx 16; M | PulseOx 17; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | RTSAClassAttr 1; M | RTSAClassAttr 2; M | RTSAClassAttr 3; M | +| | | RTSAClassAttr 4; M | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | | ScannerAttr 4; M | NumArrayDataType 1; O | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    The presence of the attributes of the Plethysmographic Waveform Object, the Metric and RT-SA attributes and their respective values.

    | +| Applicability | C_SEN_000 AND C_SEN_PO_001 AND C_SEN_PO_002 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a pulse oximeter device with a plethysmographic waveform object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a pulse oximeter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The plethysmographic waveform object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Plethysmographic waveform object follows this OBX encoding:
        • OBX-2 = 'NA'
        • OBX-3 = 150452^MDC_PULS_OXIM_PLETH^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the plethysmographic waveform object respectively.
        • OBX-5 = a numeric array value (i.e., 1~2~3~4~5...)
        • OBX-6 = 262656^MDC_DIM_DIMLESS^MDC or 268738^MDC_DIM_MICRO_ABSORBANCE^MDC
      5. e. If the Plethysmographic Waveform Sample Period attribute is present, it follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 67981^MDC_ATTR_TIME_PD_SAMP^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the plethysmographic waveform object.
        • OBX-5 = a numeric value
        • OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = a numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = a numeric value
    | + +| | | +|---------------------------|-------------------------------------------------------------------------------| +| |
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PO/BV-004 | | | | +| TP label | Pulsatile Quality Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | PulseOx 1; M | PulseOx 15; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Pulsatile Quality Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_PO_001 AND C_SEN_PO_003 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a pulse oximeter device with a pulsatile quality object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a pulse oximeter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one pulsatile quality object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • ❑ refIdValue: is a 32-bit integer (required)
        • ❑ refIdName: is the normative nomenclature name for the unique code point (recommended)
        • ❑ refIdCodeSystem = "MDC" (required).
      4. d. Pulsatile Quality object follows this OBX encoding:
        • ❑ OBX-2 = 'NM'
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-3 = 150448^MDC_PULS_OXIM_PERF_REL^MDC or 150320^MDC_SAT_O2_QUAL^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Pulsatile Quality object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = when OBX-2 is MDC_PULS_OXIM_PERF_REL then units are 262656^MDC_DIM_DIMLESS^MDC or when OBX-2 is MDC_SAT_O2_QUAL then units are 262688^MDC_DIM_PERCENT^MDC

    e. No PM-Store, PM-Segment or Scanner attributes are present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PO/BV-005 | | | | +| TP label | Pulsatile Occurrence Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | PulseOx 1; M | PulseOx 2; M | PulseOx 18; M | +| | | PulseOx 19; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Pulsatile Occurrence Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_PO_001 AND C_SEN_PO_004 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a pulse oximeter device with a pulsatile occurrence object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a pulse oximeter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Pulsatile Occurrence object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32-bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Pulsatile Occurrence object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 184322^MDC_TRIG^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the pulsatile occurrence object respectively
        • OBX-5 = 184323^MDC_TRIG_BEAT^MDC or 184331^MDC_TRIG_BEAT_MAX_INRUSH^MDC or 192511^MDC_METRIC_NOS^MDC
      5. e. If the Pulsatile Occurrence Source-Handle-Reference attribute is present, it follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the pulsatile occurrence object
        • OBX-5 = OBX-4 of the pulsatile quality numeric object or the plethysmogram RT-SA object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PO/BV-006 | | | +| TP label | Pulsatile Characteristic Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | PulseOx 1; M | PulseOx 2; M | +| | | PulseOx 21; M | MetricClassAttr 1; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the Pulsatile Characteristic Object, the Metric and Enumeration attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_PO_001 AND C_SEN_PO_005 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a pulse oximeter device with a pulsatile characteristic object. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a pulse oximeter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The pulsatile characteristic object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Pulsatile characteristic object follows this OBX encoding:
        • OBX-2 = 'CWE'
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-3 = 150584^MDC_PULS_OXIM_PULS_CHAR^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the pulsatile characteristic object respectively.
    • OBX-5 = One of these values:
      <0 or 1>^pulse-qual-nominal(0),
      <0 or 1>^pulse-qual-marginal(1),
      <0 or 1>^pulse-qual-minimal(2),
      <0 or 1>^pulse-qual-unacceptable(3)

    f. If the pulsatile characteristic Source-Handle-Reference attribute is present, it follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the pulsatile characteristic object.
    • OBX-5 = OBX-4 of the pulsatile amplitude numeric object or the plethysmogram RT-SA object

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PO/BV-007 | | | | +| TP label | Device and Sensor Annunciation Status Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | PulseOx 1; M | PulseOx 2; M | PulseOx 22; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|--| +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Device and Sensor Annunciation Status Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_PO_001 AND C_SEN_PO_006 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a pulse oximeter device with a device and sensor annunciation status object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a pulse oximeter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The device and sensor annunciation object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Device and sensor annunciation status object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 150604^MDC_PULS_OXIM_DEV_STATUS^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the device and sensor annunciation status object respectively.
        • OBX-5 = One of these values:
          • <0 or 1>^sensor-disconnected(0),
          • <0 or 1>^sensor-malfunction(1),
          • <0 or 1>^sensor-displaced(2),
          • <0 or 1>^sensor-unsupported(3),
          • <0 or 1>^sensor-off(4),
          • <0 or 1>^sensor-interference(5),
          • <0 or 1>^signal-searching(6),
          • <0 or 1>^signal-pulse-questionable(7),
          • <0 or 1>^signal-non-pulsatile(8),
          • <0 or 1>^signal-erratic(9),
          • <0 or 1>^signal-low-perfusion(10),
          • <0 or 1>^signal-poor(11),
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    <0 or 1>^signal-inadequate(12),

    <0 or 1>^signal-processing-irregularity(13),

    <0 or 1>^device-equipment-malfunction(14),

    <0 or 1>^device-extended-update(15)

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +### A.5 Subgroup 1.4.4: Blood pressure monitor (BPM) + +| | | | | +|-----------------|-----------------------------------|---------------------|---------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BPM/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | +| | | MDSObject 1; M | MDSObject 2; M | +| | | MDSObject 4; M | MDSObject 5; M | +| | | MDSObject 7; M | MDSObject 8; M | +| | | MDSObject 10; M | MDSObject 11; M | +| | | MDSObject 13; O | MDSObject 14; O | +| | | MDSObject 16; M | MDSObject 17; M | +| | | MDSObject 19; M | MDSObject 20; M | +| | | MDSObject 22; M | MDSObject 23; M | +| | | MDSObject 25; M | MDSObject 26; M | +| | | MDSObject 28; M | MDSObject 29; M | +| | | MDSObject 31; M | MDSObject 32; M | +| | | Timestamp 13; O | Timestamp 14; O | +| | | Timestamp 17; M | | +| | Spec | [IHE PCD TF 2] | | +| | Testable items | DeviceTimeSync1; M | | +| | Spec | [ITU-T H.812.1] | | + +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|----------------------| +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_BPM_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a blood pressure device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a blood pressure device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      3. c. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      4. d. In MDS-level OBX:
        • OBX-2 is empty
        • If the System-Type attribute is valued, OBX-3 = 528391^MDC_DEV_SPEC_PROFILE_BP^MDC
        • If the System-Type-Spec-List attribute contains a single value and the System-Type is not valued, this value is reported as the OBX-3
        • If the System-Type-Spec-List contains multiple values and the System-Type is not valued, OBX-3 = 528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC and the specialization list is reported as an attribute of the device
        • If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD
        • OBX-11 = 'X'
        • OBX-18 (System Id attribute) = <Entity Identifier (ST)>^^<System_Id>^EUI-64, where the System_Id is 16 characters given by the PIXIT I_SEN_BPM_001.
      5. e. System-Model attribute is sent in two different OBX segments:
        • System-Model attribute:
          • • OBX-2 = 'ST'
          • • OBX-3 = 531969^MDC_ID_MODEL_NUMBER^MDC
          • • OBX-5 = String representing the model number portion of the MDC_ATTR_ID_MODEL attribute
        • System-Manufacturer attribute:
          • • OBX-2 = 'ST'
          • • OBX-3 = 531970^MDC_ID_MODEL_MANUFACTURER^MDC
    | | | | + +- OBX-5 = String representing the model manufacturer portion of the MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: +- ❑ Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + +- OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) +- Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) +- Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + +532224^MDC\_TIME\_SYNC\_NONE^MDC + 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + 532229^MDC\_TIME\_SYNC\_BTV1^MDC + 532230^MDC\_TIME\_SYNC\_RADIO^MDC + 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + 532232^MDC\_TIME\_SYNC\_CDMA^MDC + 532233^MDC\_TIME\_SYNC\_GSM^MDC + 532234^MDC\_TIME\_SYNC\_EBWW^MDC + 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC + +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC + +- Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If Power-Status attribute is valued, it is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + - OBX-5 = NM data type value + - OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC +- k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC + - OBX-5 = Use the value contained in the BatMeasure object + - OBX-6 = Use the OID contained in the BatMeasure object +- l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + - OBX-2 = 'CWE' + - OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC + - OBX-5 = One of: + - 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + - 254^auth-body-experimental, + - 255^auth-body-reserved +- m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + - Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + - OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <major-IG-version>.<minor-IG-version>.

    ❑ Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'NA'
    • • OBX-3 = 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC
    • • OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment.
    • • OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 7 (BPM v1.0), 16391 (BPM v1.5 Wireless PAN), 8199 (BPM v1.5 Wired PAN), 24583 (BPM v1.5 Sensor LAN), or 32775 (BPM v2.0 LP Wireless PAN)

    ❑ Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'CWE'
    • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
    • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If the System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • ❑ OBX-2 = 'CWE'
    • ❑ OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • ❑ OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------|--------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BPM/BV-001 | | | | | | | | | | | | | | | | | | | | | | | | | | +| TP label | Systolic, Diastolic, MAP Compound Numeric Object | | | | | | | | | | | | | | | | | | | | | | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | | | | | | | | | | | | | | | | | | | | | | +| | Testable items |
    BloodPressure 1; M BloodPressure 2; M BloodPressure 4; M
    BloodPressure 5; M BloodPressure 6; M BloodPressure 7; M
    MetricClassAttr 1; M MetricClassAttr 2; M MetricClassAttr 3; O
    MetricClassAttr 4; M MetricClassAttr 5; M MetricClassAttr 6; O
    MetricClassAttr 7; O MetricClassAttr 8; O MetricClassAttr 9; M
    MetricClassAttr 10; O MetricClassAttr 11; M MetricClassAttr 12; O
    MetricClassAttr 13; O MetricClassAttr 14; O MetricClassAttr 15; C
    MetricClassAttr 16; C MetricClassAttr 17; C MetricClassAttr 18; O
    | | BloodPressure 1; M | BloodPressure 2; M | BloodPressure 4; M | BloodPressure 5; M | BloodPressure 6; M | BloodPressure 7; M | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| BloodPressure 1; M | BloodPressure 2; M | BloodPressure 4; M | | | | | | | | | | | | | | | | | | | | | | | | | +| BloodPressure 5; M | BloodPressure 6; M | BloodPressure 7; M | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | NumericClassAttr 7; O | MetricRelGroup 1; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| Spec | | [ITU-T H.812.1] | | | +| Testable items | | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Systolic, Diastolic, MAP Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_BPM_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a blood pressure device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a blood pressure device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Systolic, Diastolic, MAP object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Systolic, Diastolic, MAP object follows this OBX encoding:
        • OBX-2 is empty
        • OBX-3 = 150020^MDC_PRESS_BLD_NONINV^MDC
        • OBX-4 = y.0.x., where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the channel-level for the Systolic, Diastolic, MAP object respectively.
        • OBX-5 is empty
        • OBX-11 = 'X'
      5. e. Systolic part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 150021^MDC_PRESS_BLD_NONINV_SYS^MDC
        • OBX-4 = y.0.x.a., where 'a' is a number indicating the component of the compound object
        • OBX-5 = Numeric value
        • OBX-6 = 266016^MDC_DIM_MMHG^MDC or 265987^MDC_DIM_KILO_PASCAL^MDC
      6. f. Diastolic part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 150022^MDC_PRESS_BLD_NONINV_DIA^MDC
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.x.b, where 'b' is a number indicating the component of the compound object
    • OBX-5 = Numeric value
    • OBX-6 = 266016^MDC_DIM_MMHG^MDC or 265987^MDC_DIM_KILO_PASCAL^MDC

    g. Mean arterial pressure part of the compound object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 150023^MDC_PRESS_BLD_NONINV_MEAN^MDC
    • OBX-4 = y.0.x.c, , where 'c' is a number indicating the component of the compound object
    • OBX-5 = Numeric value
    • OBX-6 = 266016^MDC_DIM_MMHG^MDC or 265987^MDC_DIM_KILO_PASCAL^MDC

    h. No PM-Store, PM-Segment or Scanner attributes are present.

    i. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|---------------------|-----------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BPM/BV-002 | | | +| TP label | PulseRate Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | BloodPressure 2; M | BloodPressure 8; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that: | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The presence of the attributes of the PulseRate Object, the Metric and Numeric attributes and their respective values. | +| Applicability | C_SEN_000 AND C_SEN_BPM_001 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a blood pressure device with a pulse rate object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a blood pressure device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The PulseRate object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. PulseRate object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 149546^MDC_PULS_RATE_NON_INV^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the PulseRate object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264864^MDC_DIM_BEAT_PER_MIN^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +## A.6 Subgroup 1.4.5: Thermometer (TH) + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/TH/BV-000 | | | | +| TP label | MDS Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | MDSClassAttr 1; M | MDSClassAttr 2; C | MDSClassAttr 3; M | +| | | MDSClassAttr 4; M | MDSClassAttr 5; M | MDSClassAttr 6; M | +| | | MDSClassAttr 7; O | MDSClassAttr 8; M | MDSClassAttr 9; C | +| | | MDSClassAttr 10; C | MDSClassAttr 11; C | MDSClassAttr 12; M | +| | | MDSClassAttr 13; M | MDSClassAttr 14; M | MDSClassAttr 15; M | +| | | MDSClassAttr 16; M | MDSClassAttr 17; C | MDSClassAttr 18; M | +| | | MDSObject 1; M | MDSObject 2; M | MDSObject 3; M | +| | | MDSObject 4; M | MDSObject 5; M | MDSObject 6; M | +| | | MDSObject 7; M | MDSObject 8; M | MDSObject 9; M | +| | | MDSObject 10; M | MDSObject 11; M | MDSObject 12; M | +| | | MDSObject 13; O | MDSObject 14; O | MDSObject 15; O | +| | | MDSObject 16; M | MDSObject 17; M | MDSObject 18; M | +| | | MDSObject 19; M | MDSObject 20; M | MDSObject 21; M | +| | | MDSObject 22; M | MDSObject 23; M | MDSObject 24; M | +| | | MDSObject 25; M | MDSObject 26; M | MDSObject 27; M | +| | | MDSObject 28; M | MDSObject 29; M | MDSObject 30; M | +| | | MDSObject 31; M | MDSObject 32; M | Thermometer 3; M | +| | | Timestamp 13; O | Timestamp 14; O | Timestamp 15; O | +| | | Timestamp 17; M | | | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | DeviceTimeSync1; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +| | Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_TH_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a thermometer device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a thermometer device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
    | | | | + +- refldName: is the normative nomenclature name for the unique code point (recommended) + - refldCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: + - OBX-2 is empty + - If the System-Type attribute is valued, OBX-3 = 528392^MDC\_DEV\_SPEC\_PROFILE\_TEMP^MDC + - If the System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System Id is 16 characters given by the PIXIT I\_SEN\_TH\_001. +- e. System model attribute is sent in two different OBX segments: + - System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. + +g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) + +- ❑ Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) +- ❑ Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC +- Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If the Power-Status attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + +- OBX-5 = NM data type value +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC + +k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC +- OBX-5 = Use the value contained in the BatMeasure object +- OBX-6 = Use the OID contained in the BatMeasure object + +l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + +- OBX-2 = 'CWE' +- OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC +- OBX-5 = One of: + - 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + - 254^auth-body-experimental, + - 255^auth-body-reserved + +m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + +- Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + - OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC + - OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the Facet level of that segment. + - OBX-5 = .. +- Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'NA' + - OBX-3 = 532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC + - OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment. + - OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 8 (TH v1.0), 16392 (TH v1.5 Wireless PAN), 8200 (TH v1.5 Wired PAN), 24584 (TH v1.5 Sensor LAN), or 32776 (TH v2.0 LP Wireless PAN) +- Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'CWE' + - OBX-3 = 532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'a' is a number indicating the Facet level of that segment.
    • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If the System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'CWE'
    • OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/TH/BV-001 | | | +| TP label | Temperature Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Thermometer 1; M | Thermometer 2; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 7; O | PM-StoreAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 4; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that:

    The presence of the attributes of the Temperature Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C SEN_000 AND C SEN_TH_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a thermometer device. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a thermometer device using SOAP or hData observation upload.

    2. Check in the captured message that:
    a. The temperature object has sent at least one observation.

    b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • refIdValue: is a 32-bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Temperature object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 188452^MDC_TEMP_AXILLA^MDC or
      150364^MDC_TEMP_BODY^MDC or
      188428^MDC_TEMP_EAR^MDC or
      188432^MDC_TEMP_FINGER^MDC or
      188456^MDC_TEMP_GIT^MDC or
      188424^MDC_TEMP_ORAL^MDC or
      188420^MDC_TEMP_RECT^MDC or
      188448^MDC_TEMP_TOE^MDC or
      150392^MDC_TEMP_TYMP^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the temperature object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 268192^MDC_DIM_DEGC^MDC or
      266560^MDC_DIM_FAHR^MDC

    e. No PM-Store, PM-Segment or Scanner attributes are present.

    f. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +### A.7 Subgroup 1.4.6: Weighing scales (WEG) + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/WEG/BV-000 | | | | +| TP label | MDS Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | MDSClassAttr 1; M | MDSClassAttr 2; C | MDSClassAttr 3; M | +| | | MDSClassAttr 4; M | MDSClassAttr 5; M | MDSClassAttr 6; M | +| | | MDSClassAttr 7; O | MDSClassAttr 8; M | MDSClassAttr 9; C | +| | | MDSClassAttr 10; C | MDSClassAttr 11; C | MDSClassAttr 12; M | +| | | MDSClassAttr 13; M | MDSClassAttr 14; M | MDSClassAttr 15; M | +| | | MDSClassAttr 16; M | MDSClassAttr 17; C | MDSClassAttr 18; M | +| | | MDSObject 1; M | MDSObject 2; M | MDSObject 3; M | +| | | MDSObject 4; M | MDSObject 5; M | MDSObject 6; M | +| | | MDSObject 7; M | MDSObject 8; M | MDSObject 9; M | +| | | MDSObject 10; M | MDSObject 11; M | MDSObject 12; M | +| | | MDSObject 13; O | MDSObject 14; O | MDSObject 15; O | +| | | MDSObject 16; M | MDSObject 17; M | MDSObject 18; M | +| | | MDSObject 19; M | MDSObject 20; M | MDSObject 21; M | +| | | MDSObject 22; M | MDSObject 23; M | MDSObject 24; M | +| | | MDSObject 25; M | MDSObject 26; M | MDSObject 27; M | +| | | MDSObject 28; M | MDSObject 29; M | MDSObject 30; M | +| | | MDSObject 31; M | MDSObject 32; M | WeighingScale 3; M | +| | | Timestamp 13; O | Timestamp 14; O | Timestamp 15; O | +| | Timestamp 17; M | | | | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | DeviceTimeSync1; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_WEG_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a weighing scales device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a weighing scales device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>

        where:
        • refIdValue: is a 32 bit integer (required)
    | | | | + +- refIdName: is the normative nomenclature name for the unique code point (recommended) + - refIdCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: + - OBX-2 is empty + - If the System-Type attribute is valued, OBX-3 = 528399^MDC\_DEV\_SPEC\_PROFILE\_SCALE^MDC + - If the System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System\_Id is 16 characters given by the PIXIT I\_SEN\_WEG\_001. +- e. System model attribute is sent in two different OBX segments: + - System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of the MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of the MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + +- OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. + +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a Timestamp, its respective resolution may be sent, but not other than this.) +- Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) + - Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC + - Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + +- OBX-14 = UTC value + - ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase + - ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase + - ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - ❑ Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC + - ❑ Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If the Power-Status attribute is valued, it is sent as an independent OBX segment: +- ❑ OBX-2 = 'ST' + - ❑ OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - ❑ OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC +- OBX-5 = NM data type value +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC + +k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC +- OBX-5 = Use the value contained in the BatMeasure object +- OBX-6 = Use the OID contained in the BatMeasure object + +l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + +- OBX-2 = 'CWE' +- OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC +- OBX-5 = One of: + 0^auth-body-empty, + 1^auth-body-ieee-11073, + 2^auth-body-continua, + 254^auth-body-experimental, + 255^auth-body-reserved + +m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + +- Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + +- OBX-2 = 'ST' +- OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC +- OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment. +- OBX-5 = .. + +- Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + +- OBX-2 = 'NA' +- OBX-3 = 532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC +- OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment. +- OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 15 (WEG v1.0), 16399 (WEG v1.5 Wireless PAN), 8207 (WEG v1.5 Wired PAN), or 24591 (WEG v1.5 Sensor LAN) + +- Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding: + +- OBX-2 = 'CWE' + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
    • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
    • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If the System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'CWE'
    • OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/WEG/BV-001 | | | | | +| TP label | Body Weight Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | WeighingScale 1; M | WeighingScale 2; M | | | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | | | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | | | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | | | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | | | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | | | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | | | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | | | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | | | +| | | NumericClassAttr 7; O | PM-StoreAttr; M | | | +| | | ScannerAttr 1; M | ScannerAttr 2; M | | | +| | | ScannerAttr 4; M | | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Body Weight Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_WEG_001 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a weighing scales device. | | | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a weighing scales device using SOAP or hData observation upload.
    2. Check in the captured message that:
    a. The body weight object has sent at least one observation. | | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • ❑ refIdValue: is a 32 bit integer (required)
    • ❑ refIdName: is the normative nomenclature name for the unique code point (recommended)
    • ❑ refIdCodeSystem = "MDC" (required).

    d. Body weight object follows this OBX encoding:

    • ❑ OBX-2 = 'NM'
    • OBX-3 = 188736^MDC_MASS_BODY_ACTUAL^MDC
    • ❑ OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the body weight object respectively.
    • ❑ OBX-5 = Numeric value
    • ❑ OBX-6 = 263875^MDC_DIM_KILO_G^MDC

    e. No PM-Store, PM-Segment or Scanner attributes are present.

    f. One of the timestamp attributes can be present:

    • ❑ MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|-----------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/WEG/BV-002 | | | | +| TP label | Body Height Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | WeighingScale 1; M | WeighingScale 2; M | WeighingScale 5; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | NumericClassAttr 7; O | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--| +| | | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Body Height Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_WEG_001 AND C_SEN_WEG_002 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a weighing scales device with a Body Height object. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a weighing scales device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Body Height object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Body Height object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 188740^MDC_LEN_BODY_ACTUAL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the body height object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263441^MDC_DIM_CENTI_M^MDC or 263520^MDC_DIM_INCH^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | | | +| Pass/Fail criteria | All elements in each segment are as specified. | | | +| Notes | | | | + +| | | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/WEG/BV-003 | | | | | +| TP label | Body Mass Index Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | WeighingScale 1; M | WeighingScale 2; M | | | +| | | WeighingScale 7; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | | | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Body Mass Index Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_WEG_001 AND C_SEN_WEG_003 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a weighing scales device with a Body Mass Index object. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a weighing scales device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Body Mass Index object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Body Mass Index object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 188752^MDC_RATIO_MASS_BODY_LEN_SQ^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Body Mass Index object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264096^MDC_DIM_KG_PER_M_SQ^MDC
    | | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    e. If the Body Mass Index Source-Handle-Reference attribute is present, it follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Body Mass Index object.
    • OBX-5 = OBX-4 of the Body Weight object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +### A.8 Subgroup 1.4.7: Glucose meter (GL) + +| | | | | | +|-----------------|----------------------------------|---------------------|---------------------|---------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-000 | | | | +| TP label | MDS Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | MDSCClassAttr 3; M | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | MDSCClassAttr 6; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | MDSCClassAttr 9; C | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | MDSCClassAttr 12; M | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | MDSCClassAttr 15; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | MDSCClassAttr 18; M | +| | | MDSObject 1; M | MDSObject 2; M | MDSObject 3; M | +| | | MDSObject 4; M | MDSObject 5; M | MDSObject 6; M | +| | | MDSObject 7; M | MDSObject 8; M | MDSObject 9; M | +| | | MDSObject 10; M | MDSObject 11; M | MDSObject 12; M | +| | | MDSObject 13; O | MDSObject 14; O | MDSObject 15; O | +| | | MDSObject 16; M | MDSObject 17; M | MDSObject 18; M | +| | | MDSObject 19; M | MDSObject 20; M | MDSObject 21; M | +| | | MDSObject 22; M | MDSObject 23; M | MDSObject 24; M | +| | | MDSObject 25; M | MDSObject 26; M | MDSObject 27; M | +| | | MDSObject 28; M | MDSObject 29; M | MDSObject 30; M | +| | | MDSObject 31; M | MDSObject 32; M | GlucoseMeter 3; M | +| | | Timestamp 13; O | Timestamp 14; O | Timestamp 15; O | +| | | Timestamp 17; M | | | +| | Spec | [IHE PCD TF 2] | | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|----------------------| +| | Testable items | DeviceTimeSync1; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      3. c. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      4. d. In the MDS-level OBX:
        • OBX-2 is empty
        • If the System-Type attribute is valued, OBX-3 = 528401^MDC_DEV_SPEC_PROFILE_GLUCOSE^MDC
        • If the System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3
        • If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC and the specialization list is reported as an attribute of the device
        • If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD
        • OBX-11 = 'X'
        • OBX-18 (System Id attribute) = <Entity Identifier (ST)>^^<System_Id>^EUI-64, where the System_Id is 16 characters given by the PIXIT I_SEN_GL_001.
      5. e. System model attribute is sent in two different OBX segments:
        • System-Model attribute:
          • • OBX-2 = 'ST'
          • • OBX-3 = 531969^MDC_ID_MODEL_NUMBER^MDC
          • • OBX-5 = String representing the model number portion of the MDC_ATTR_ID_MODEL attribute
        • System-Manufacturer attribute:
    | | | | + +- OBX-2 = 'ST' +- OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC +- OBX-5 = String representing the model manufacturer portion of the MDC\_ATTR\_ID\_MODEL attribute. + +f. Production-Specification attribute is sent as a series of attributes: + +- ❑ Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + +- OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) +- ❑ Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) +- ❑ Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + +- OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + +- OBX-6 = 264320^MDC\_DIM\_SEC^MDC +- ❑ Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If the Power-Status attribute is valued, it is sent as an independent OBX segment: + - ❑ OBX-2 = 'ST' + - ❑ OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - ❑ OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: + - ❑ OBX-2 = 'NM' + - ❑ OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + - ❑ OBX-5 = NM data type value + - ❑ OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC +- k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + - ❑ OBX-2 = 'NM' + - ❑ OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC + - ❑ OBX-5 = Use the value contained in the BatMeasure object + - ❑ OBX-6 = Use the OID contained in the BatMeasure object +- l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + - ❑ OBX-2 = 'CWE' + - ❑ OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC + - OBX-5 = One of: + - 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + - 254^auth-body-experimental, + - 255^auth-body-reserved +- m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + - ❑ Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + - OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <major-IG-version>.<minor-IG-version>.

    ❑ Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'NA'
    • • OBX-3 = 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC
    • • OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'b' is a number indicating the facet level of that segment.
    • • OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 17 (GL v1.0), 16401 (GL v1.5 Wireless PAN), 8209 (GL v1.5 Wired PAN), or 24593 (GL v1.5 Sensor LAN)

    ❑ Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'CWE'
    • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
    • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If the System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • ❑ OBX-2 = 'CWE'
    • ❑ OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • ❑ OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-001 | | | | +| TP label | Glucose Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | GlucoseMeter 2; M | GlucoseMeter 4; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | + +| | | | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------|------------------|--|--|--| +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | | | | +| | Spec | [ITU-T H.812.1] | | | | | | +| | Testable items | DataGuidelines 22; M | | | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Glucose Object, the Metric and Numeric attributes and their respective values.

    | | | | | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 | | | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device. | | | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The glucose object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Glucose object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 160184^MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD^MDC or 160188^MDC_CONC_GLU_CAPILLARY_PLASMA^MDC or 160192^MDC_CONC_GLU_VENOUS_WHOLEBLOOD^MDC or 160196^MDC_CONC_GLU_VENOUS_PLASMA^MDC or 160200^MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD^MDC or 160204^MDC_CONC_GLU_ARTERIAL_PLASMA^MDC or 160364^MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD or 160368^MDC_CONC_GLU_UNDETERMINED_PLASMA or 160212^MDC_CONC_GLU_ISF^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Glucose object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264274^MDC_DIM_MILLI_G_PER_DL^MDC or 266866^MDC_DIM_MILLI_MOLE_PER_L^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
    | | | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = Numeric value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-002 | | | | | +| TP label | Context Exercise Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | GlucoseMeter 1; M | GlucoseMeter 2; M | | | +| | | GlucoseMeter 6; M | GlucoseMeter 7; M | | | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | | | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | | | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | | | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | | | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | | | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | | | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | | | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | | | +| | | ScannerAttr 1; M | ScannerAttr 2; M | | | +| | | ScannerAttr 4; M | | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Context Exercise Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_002 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a Context Exercise object. | | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. The Context Exercise object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        refldValue: is a 32 bit integer (required)
        refldName: is the normative nomenclature name for the unique code point (recommended)
        refldCodeSystem = "MDC" (required).
    | | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. Context Exercise object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8417760^MDC_CTXT_GLU_EXERCISE^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Context Exercise object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 262688^MDC_DIM_PERCENT^MDC

    e. If the Context Exercise Source-Handle-Reference attribute is present, it follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Context Exercise object.
    • OBX-5 = OBX-4 of the Glucose object

    f. If the Context Exercise Measure Active Period attribute is present, it follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC
    • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the Facet level of the Context Exercise object.
    • OBX-5 = Numeric Value

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-003 | | | +| TP label | Context Medication Numeric Object | | | +| Coverage | [ITU-T H.812.1] | | | +| | Spec

    Testable items | GlucoseMeter 1; M
    GlucoseMeter 9; M
    MetricClassAttr 3; O
    MetricClassAttr 6; O
    MetricClassAttr 9; M
    MetricClassAttr 12; O
    MetricClassAttr 15; C
    MetricClassAttr 18; O | GlucoseMeter 2; M
    MetricClassAttr 1; M
    MetricClassAttr 4; M
    MetricClassAttr 7; O
    MetricClassAttr 10; O
    MetricClassAttr 13; O
    MetricClassAttr 16; C
    NumericClassAttr 1; M | + +| | | | | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------|--|--|--| +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 2; O | | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | | | | +| | Spec | [ITU-T H.812.1] | | | | | | +| | Testable items | DataGuidelines 22; M | | | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Context Medication Object, the Metric and Numeric attributes and their respective values.

    | | | | | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_003 | | | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a Context Medication object.

    | | | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Context Medication object has sent at least one observation
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Context Medication object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8417796^MDC_CTXT_MEDICATION^MDC or 8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC or 8417804^MDC_CTXT_MEDICATION_SHORTACTING^MDC or 8417808^MDC_CTXT_MEDICATION_INTERMEDIATEACTING^MDC or 8417812^MDC_CTXT_MEDICATION_LONGACTING^MDC or 8417816^MDC_CTXT_MEDICATION_PREMIX^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Context Medication object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263890^MDC_DIM_MILLI_G^MDC or 263762^MDC_DIM_MILLI_L^MDC
      5. e. If the Context Medication Source-Handle-Reference attribute is present, it follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Context Medication object.
        • OBX-5 = OBX-4 of the Glucose object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
    | | | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-004 | | | | | +| TP label | Context Carbohydrates Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | GlucoseMeter 1; M | GlucoseMeter 2; M | | | +| | | GlucoseMeter 11; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | | | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Context Carbohydrates Object, the Metric and Numeric attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_004 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a Context Carbohydrates object. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Context Carbohydrates object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    | | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Context Carbohydrates object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8417764^MDC_CTXT_GLU_CARB^MDC is the generic code or if specific Metric-Id is specified use it:
      8417768^MDC_CTXT_GLU_CARB_BREAKFAST^MDC or
      8417772^MDC_CTXT_GLU_CARB_LUNCH^MDC or
      8417776^MDC_CTXT_GLU_CARB_DINNER^MDC or
      8417780^MDC_CTXT_GLU_CARB_SNACK^MDC or
      8417784^MDC_CTXT_GLU_CARB_DRINK^MDC or
      8417788^MDC_CTXT_GLU_CARB_SUPPER^MDC or
      8417792^MDC_CTXT_GLU_CARB_BRUNCH^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Context Carbohydrates object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 263872^MDC_DIM_G^MDC

    e. If the Context Carbohydrates Source-Handle-Reference attribute is present, it follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Context Carbohydrates object.
    • OBX-5 = OBX-4 of the Glucose object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|----------------------------------------------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-005 | | | +| TP label | Device and Sensor Annunciation Status Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | GlucoseMeter 2; M | GlucoseMeter 12; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | | MetricClassAttr 4; M | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | ScannerAttr 3; M | ScannerAttr 4; M | | +| Spec | [ITU-T H.812.1] | | | +| Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Device and Sensor Annunciation Status Object, the Metric and Enumeration attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_005 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a Device and Sensor Annunciation Status object.

    | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Device and Sensor Annunciation Status object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Device and Sensor Annunciation Status object follows this OBX encoding:
        • OBX-2 = 'CWE'
          OBX-3 = 8417752^MDC_GLU_METER_DEV_STATUS^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Device and Sensor Annunciation Status object respectively.
        • OBX-5 = Any of these values:
          <0 or 1>^device-battery-low(0),
          <0 or 1>^sensor-malfunction(1),
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    <0 or 1>^sensor-sample-size-insufficient(2)

    <0 or 1>^sensor-strip-insertion(3),

    <0 or 1>^sensor-strip-type-incorrect(4),

    <0 or 1>^sensor-result-too-high(5),

    <0 or 1>^sensor-result-too-low(6),

    <0 or 1>^sensor-temp-too-high(7),

    <0 or 1>^sensor-temp-too-low(8),

    <0 or 1>^sensor-read-interrupt(9),

    <0 or 1>^device-gen-fault(10)

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-006 | | | | +| TP label | Context Meal Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | GlucoseMeter 1; M | GlucoseMeter 2; M | GlucoseMeter 13; M | +| | | GlucoseMeter 14; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Context Meal Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_006 | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a Context Meal object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Context Meal object has sent at least one observation
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Context Meal object follows this OBX encoding:
        • OBX-2 = 'CWE'
          OBX-3 = 8417864^MDC_CTXT_GLU_MEAL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Context Meal object respectively.
        • OBX-5 = 8417868^MDC_CTXT_GLU_MEAL_PREPRANDIAL^MDC or 8417872^MDC_CTXT_GLU_MEAL_POSTPRANDIAL^MDC or 8417876^MDC_CTXT_GLU_MEAL_FASTING^MDC or 8417880^MDC_CTXT_GLU_MEAL_CASUAL^MDC or 8417908^MDC_CTXT_GLU_MEAL_BEDTIME^MDC
      5. e. If the Context Meal Source-Handle-Reference attribute is present, it follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Context Meal object.
        • OBX-5 = OBX-4 of the Glucose object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-007 | | | | | +| TP label | Context Sample Location Enumeration Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | GlucoseMeter 1; M | GlucoseMeter 2; M | | | +| | | GlucoseMeter 16; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | | | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | | | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | | | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | | | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] – | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Context Sample Location Object, the Metric and Enumeration attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_007 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a Context Sample Location object.

    | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Context Sample Location object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Context Sample Location object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8417844^MDC_CTXT_GLU_SAMPLELOCATION^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Context Sample Location object respectively.
    | | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = 8417848^MDC_CTXT_GLU_SAMPLELOCATION_FINGER^MDC or 8417852^MDC_CTXT_GLU_SAMPLELOCATION_AST^MDC or 8417856^MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE^MDC or 8417860^MDC_CTXT_GLU_SAMPLELOCATION_CTLSOLUTION^MDC

    e. If the Context Sample Location Source-Handle-Reference attribute is present, it follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Context Sample Location object.
    • OBX-5 = OBX-4 of the Glucose object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-008 | | | | | +| TP label | Context Tester Enumeration Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | GlucoseMeter 1; M | GlucoseMeter 2; M | | | +| | | GlucoseMeter 18; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | | | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | | | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | | | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | | | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Context Tester Object, the Metric and Enumeration attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_008 | | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a Context Tester object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Context Tester object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Context Tester object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8417884^MDC_CTXT_GLU_TESTER^MDC
          is the generic code or if specific Metric-Id is specified use it:
          8417888^MDC_CTXT_GLU_TESTER_SELF^MDC or
          8417892^MDC_CTXT_GLU_TESTER_HCP^MDC or
          8417896^MDC_CTXT_GLU_TESTER_LAB^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Context Tester object respectively.
        • OBX-5 is empty
      5. e. If the Context Tester Source-Handle-Reference attribute is present, it follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Context Tester object.
        • OBX-5 = OBX-4 of the Glucose object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-009 | | | | | +| TP label | Context Health Enumeration Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | GlucoseMeter 1; M | GlucoseMeter 2; M | | | +| | | GlucoseMeter 20; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | | | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | | | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | | | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | | | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| | | | | | | +| Test purpose | Check that:
    The presence of the attributes of the Context Health Object, the Metric and Enumeration attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_009 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a Context Health object. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Context Health object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Context Health object follows this OBX encoding:
        • OBX-2 = 'CWE'
          OBX-3 = 8417820^MDC_CTXT_GLU_HEALTH^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Context Health object respectively.
    | | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = 8417824^MDC_CTXT_GLU_HEALTH_MINOR^MDC or 8417828^MDC_CTXT_GLU_HEALTH_MAJOR^MDC or 8417832^MDC_CTXT_GLU_HEALTH_MENSES^MDC or 8417836^MDC_CTXT_GLU_HEALTH_STRESS^MDC or 8417840^MDC_CTXT_GLU_HEALTH_NONE^MDC

    e. If the Context Health Source-Handle-Reference attribute is present, it follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Context Health object.
    • OBX-5 = OBX-4 of the Glucose object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-010 | | | +| TP label | HbA1c Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | GlucoseMeter 2; M | GlucoseMeter 21; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the HbA1c Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_010 | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a HbA1c object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The HbA1c object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • ❑ refIdValue: is a 32 bit integer (required)
        • ❑ refIdName: is the normative nomenclature name for the unique code point (recommended)
        • ❑ refIdCodeSystem = "MDC" (required).
      4. d. HbA1c object follows this OBX encoding:
        • ❑ OBX-2 = 'NM'
        • ❑ OBX-3 = 160220^MDC_CONC_HBA1C^MDC
        • ❑ OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the HbA1c object respectively
        • ❑ OBX-5 = Numeric value
        • ❑ OBX-6 = 262688^MDC_DIM_PERCENT^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
        • ❑ MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------|----------------------|----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/GL/BV-011 | | | | +| TP label | Control Solution Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | GlucoseMeter 2; M | GlucoseMeter 22; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | + +| | | | | | +|--------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | |

    Check that:

    The presence of the attributes of the Control Solution Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | | C_SEN_000 AND C_SEN_GL_001 AND C_SEN_GL_011 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a glucose meter device with a Control Solution object.

    | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a glucose meter device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Control Solution object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Control Solution object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 160208^MDC_CONC_GLU_CONTROL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Control Solution object respectively.
        • OBX-5 = Numeric value
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-5 = Numeric value
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +### A.9 Subgroup 1.4.8: Cardiovascular fitness and activity monitor (CV) + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-000 | | | | +| TP label | MDS Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | MDSClassAttr 1; M | MDSClassAttr 2; C | MDSClassAttr 3; M | +| | | MDSClassAttr 4; M | MDSClassAttr 5; M | MDSClassAttr 6; M | +| | | MDSClassAttr 7; O | MDSClassAttr 8; M | MDSClassAttr 9; C | +| | | MDSClassAttr 10; C | MDSClassAttr 11; C | MDSClassAttr 12; M | +| | | MDSClassAttr 13; M | MDSClassAttr 14; M | MDSClassAttr 15; M | +| | | MDSClassAttr 16; M | MDSClassAttr 17; C | MDSClassAttr 18; M | +| | | MDSObject 1; M | MDSObject 2; M | MDSObject 3; M | +| | | MDSObject 4; M | MDSObject 5; M | MDSObject 6; M | +| | | MDSObject 7; M | MDSObject 8; M | MDSObject 9; M | +| | | MDSObject 10; M | MDSObject 11; M | MDSObject 12; M | +| | | MDSObject 13; O | MDSObject 14; O | MDSObject 15; O | +| | | MDSObject 16; M | MDSObject 17; M | MDSObject 18; M | +| | | MDSObject 19; M | MDSObject 20; M | MDSObject 21; M | +| | | MDSObject 22; M | MDSObject 23; M | MDSObject 24; M | +| | | MDSObject 25; M | MDSObject 26; M | MDSObject 27; M | +| | | MDSObject 28; M | MDSObject 29; M | MDSObject 30; M | +| | | MDSObject 31; M | MDSObject 32; M | Cardiovascular 3; M | +| | | Timestamp 13; O | Timestamp 14; O | Timestamp 15; O | +| | Timestamp 17; M | | | | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | DeviceTimeSync1; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device. | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
    | | | | + +- refIdName: is the normative nomenclature name for the unique code point (recommended) + - refIdCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: + - OBX-2 is empty + - If the System-Type attribute is valued, OBX-3 = 528425^MDC\_DEV\_SPEC\_PROFILE\_HF\_CARDIO^MDC + - If the System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System Id is 16 characters given by the PIXIT I\_SEN\_CV\_001. +- e. System model attribute is sent in two different OBX segments: + - System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. + +g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) + +- ❑ Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) +- ❑ Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC +- Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If the Power-Status attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + +- OBX-5 = NM data type value +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC + +k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC +- OBX-5 = Use the value contained in the BatMeasure object +- OBX-6 = Use the OID contained in the BatMeasure object + +l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + +- OBX-2 = 'CWE' +- OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC +- OBX-5 = One of: + - 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + - 254^auth-body-experimental, + - 255^auth-body-reserved + +m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + +- Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + - OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC + - OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment. + - OBX-5 = .. +- Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'NA' + - OBX-3 = 532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC + - OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment. + - OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 41 (CV v1.0), 16425 (CV v1.5 Wireless PAN), 8233 (CV v1.5 Wired PAN), or 24617 (CV v1.5 Sensor LAN) +- Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'CWE' + - OBX-3 = 532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If the System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • ❑ OBX-2 = 'CWE'
    • ❑ OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • ❑ OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-001 | | | | +| TP label | Session Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 2; M | Cardiovascular 4; M | Cardiovascular 5; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Session Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device. | | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. Check in the captured message that:
    1. At least one Session object has sent at least one observation
    2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    | | | | + +- c. Each MDC code using a CWE data type is encoded as: +^^ + +where: + +- refldValue: is a 32 bit integer (required) +- refldName: is the normative nomenclature name for the unique code point (recommended) +- refldCodeSystem = "MDC" (required). + +- d. Session object follows this OBX encoding: + +- OBX-2 = 'CWE' +OBX-3 = 8454267^MDC\_HF\_SESSION^MDC +- OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Session object respectively. +- OBX-5 = One of the values: +8455144^MDC\_HF\_ACT\_AMB^MDC +8455145^MDC\_HF\_ACT\_REST^MDC +8455146^MDC\_HF\_ACT\_MOTOR^MDC +8455147^MDC\_HF\_ACT\_LYING^MDC +8455148^MDC\_HF\_ACT\_SLEEP^MDC +8455149^MDC\_HF\_ACT\_PHYS^MDC +8455150^MDC\_HF\_ACT\_SUS\_PHYS^MDC +8455151^MDC\_HF\_ACT\_UNKNOWN^MDC +8455152^MDC\_HF\_ACT\_MULTIPLE^MDC +8455153^MDC\_HF\_ACT\_MONITOR^MDC +8455154^MDC\_HF\_ACT\_SKI^MDC +8455155^MDC\_HF\_ACT\_RUN^MDC +8455156^MDC\_HF\_ACT\_BIKE^MDC +8455157^MDC\_HF\_ACT\_STAIR^MDC +8455158^MDC\_HF\_ACT\_ROW^MDC +8455159^MDC\_HF\_ACT\_HOME^MDC +8455160^MDC\_HF\_ACT\_WORK^MDC +8455161^MDC\_HF\_ACT\_WALK^MDC + +- e. If Session Measure Active Period attribute is present, it follows this OBX encoding: + +- OBX-2 = 'NM' +- OBX-3 = 68185^MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE^MDC +- OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Session object. +- OBX-5 = Numeric value +- OBX-6 = 264320^MDC\_DIM\_SEC^MDC + +- f. No PM-Store, PM-Segment or Scanner attributes are present. + +- g. One of these timestamp attributes can be present: + +- MDC\_ATTR\_TIME\_STAMP\_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ] +- MDC\_ATTR\_TIME\_STAMP\_REL, transmitted as a facet of the observation: + - OBX-5 = Numeric value + - OBX-18 has a timebase ID. + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
    • • OBX-5 = Numeric value
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-002 | | | | +| TP label | Sub-Session Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 2; M | Cardiovascular 6; M | Cardiovascular 7; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Sub-Session Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_030 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Sub-Session object. | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. At least one Sub-Session object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • ❑ refldValue: is a 32 bit integer (required)
        • ❑ refldName: is the normative nomenclature name for the unique code point (recommended)
        • ❑ refldCodeSystem = "MDC" (required).
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. Sub-Session object follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8454268^MDC_HF_SUBSESSION^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Sub-Session object respectively.
    • OBX-5 = One of the values:
      • 8455144^MDC_HF_ACT_AMB^MDC
      • 8455145^MDC_HF_ACT_REST^MDC
      • 8455146^MDC_HF_ACT_MOTOR^MDC
      • 8455147^MDC_HF_ACT_LYING^MDC
      • 8455148^MDC_HF_ACT_SLEEP^MDC
      • 8455149^MDC_HF_ACT_PHYS^MDC
      • 8455150^MDC_HF_ACT_SUS_PHYS^MDC
      • 8455151^MDC_HF_ACT_UNKNOWN^MDC
      • 8455152^MDC_HF_ACT_MULTIPLE^MDC
      • 8455153^MDC_HF_ACT_MONITOR^MDC
      • 8455154^MDC_HF_ACT_SKI^MDC
      • 8455155^MDC_HF_ACT_RUN^MDC
      • 8455156^MDC_HF_ACT_BIKE^MDC
      • 8455157^MDC_HF_ACT_STAIR^MDC
      • 8455158^MDC_HF_ACT_ROW^MDC
      • 8455159^MDC_HF_ACT_HOME^MDC
      • 8455160^MDC_HF_ACT_WORK^MDC
      • 8455161^MDC_HF_ACT_WALK^MDC

    e. If the Sub-Session Measure Active Period attribute is present, it follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Sub-Session object.
    • OBX-5 = Numeric value
    • OBX-6 = 264320^MDC_DIM_SEC^MDC

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-003 | | | | | +| TP label | Altitude Gain Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | | | +| | | Cardiovascular 9; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | | | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Altitude Gain Object, the Metric and Numeric attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_002 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with an Altitude Gain object.

    | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Altitude Gain object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Altitude Gain object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454244^MDC_HF_ALT_GAIN^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Altitude Gain object respectively.
        • OBX-5 = Numeric value
    | | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-6 = 263424^MDC_DIM_M^MDC or 263488^MDC_DIM_FOOT^MDC

    e. Altitude Gain Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Altitude Gain object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-004 | | | | | +| TP label | Altitude Loss Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | | | +| | | Cardiovascular 11; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | | | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Altitude Loss Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_003 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with an Altitude Loss object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Altitude Loss object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Altitude Loss object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454245^MDC_HF_ALT_LOSS^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Altitude Loss object respectively.
        • OBX-5 = Numeric Value
        • OBX-6 = 263424^MDC_DIM_M^MDC or 263488^MDC_DIM_FOOT^MDC
      5. e. Altitude Loss Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Altitude Loss object.
        • OBX-5 = OBX-4 of Session or Subsession object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | +|-----------------|----------------------------------|-----------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-005 | | +| TP label | Altitude Numeric Object | | +| Coverage | Spec | [ITU-T H.812.1] | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 12; M | +| | Cardiovascular 13; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 2; O | +| | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| Spec | [ITU-T H.812.1] – | | | +| Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Altitude Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_004 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with an Altitude object. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Altitude object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Altitude object follows this OBX encoding:
        • OBX-2 = 'NM'
          OBX-3 = 8454246^MDC_HF_ALT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Altitude object respectively.
        • OBX-5 = Numeric Value
        • OBX-6 = 263424^MDC_DIM_M^MDC or 263488^MDC_DIM_FOOT^MDC
      5. e. Altitude Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Altitude object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-006 | | | | | +| TP label | Distance Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | | | +| | | Cardiovascular 15; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | | | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Distance Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_027 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Distance object. | | | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. Check in the captured message that: | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. At least one Distance object has sent at least one observation.

    b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Distance object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8454247^MDC_HF_DISTANCE^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Distance object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 263424^MDC_DIM_M^MDC or 263488^MDC_DIM_FOOT^MDC or 268800^MDC_DIM_STEP^MDC

    e. Distance Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Distance object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|-----------------------------------------|----------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-007 | | | | +| TP label | Ascent Time and Distance Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 16; M | +| | | Cardiovascular 17; M | Cardiovascular 18; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | MetricRelGroup 2; O | PM-StoreAttr; M | PM-SegmentAttr; M | +| | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | ScannerAttr 4; M | | | +| Spec | [ITU-T H.812.1] | | | +| Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Ascent Time and Distance Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_028 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with an Ascent Time object. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Ascent Time and Distance object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Ascent Time and Distance object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454248^MDC_HF_ASC_TIME_DIST^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Ascent Time and Distance object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263424^MDC_DIM_M^MDC or 263488^MDC_DIM_FOOT^MDC or 268800^MDC_DIM_STEP^MDC
      5. e. If the Ascent Time and Distance Measure Active Period attribute is present, it follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Ascent Time and Distance object.
    • OBX-5 = Numeric value
    • OBX-6 = 264320^MDC_DIM_SEC^MDC

    f. Ascent Time and Distance Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Ascent Time and Distance object.
    • OBX-5 = OBX-4 of Session or Subsession object

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|---------------------|------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-008 | | | | +| TP label | Descent Time and Distance Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 19; M | +| | | Cardiovascular 20; M | Cardiovascular 21; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] – | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that: | | | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The presence of the attributes of the Descent Time and Distance Object, the Metric and Numeric attributes and their respective values. | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_029 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Descent Time object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Descent Time and Distance object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Descent Time and Distance object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454249^MDC_HF_DESC_TIME_DIST^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Descent Time and Distance object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263424^MDC_DIM_M^MDC or 263488^MDC_DIM_FOOT^MDC or 268800^MDC_DIM_STEP^MDC
      5. e. If the Descent Time and Distance Measure Active Period attribute is present, it follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Descent Time and Distance object.
        • OBX-5 = Numeric value
        • OBX-6 = 264320^MDC_DIM_SEC^MDC
      6. f. Descent Time and Distance Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Descent Time and Distance object.
        • OBX-5 = OBX-4 of Session or Subsession object
      7. g. No PM-Store, PM-Segment or Scanner attributes are present.
      8. h. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-009 | | | | +| TP label | Latitude Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 22; M | +| | | Cardiovascular 23; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 2; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Latitude Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_026 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Latitude object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Latitude object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • reIdValue: is a 32 bit integer (required)
    • reIdName: is the normative nomenclature name for the unique code point (recommended)
    • reIdCodeSystem = "MDC" (required).

    d. Latitude object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8454250^MDC_HF_LATITUDE^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Latitude object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 262880^MDC_DIM_ANG_DEG^MDC

    e. Latitude Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Latitude object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-010 | | | | +| TP label | Longitude Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M
    Cardiovascular 25; M
    MetricClassAttr 3; O
    MetricClassAttr 6; O
    MetricClassAttr 9; M
    MetricClassAttr 12; O
    MetricClassAttr 15; C
    MetricClassAttr 18; O
    NumericClassAttr 3; M
    NumericClassAttr 6; M
    PM-StoreAttr; M | Cardiovascular 2; M
    MetricClassAttr 1; M
    MetricClassAttr 4; M
    MetricClassAttr 7; O
    MetricClassAttr 10; O
    MetricClassAttr 13; O
    MetricClassAttr 16; C
    NumericClassAttr 1; M
    NumericClassAttr 4; M
    NumericClassAttr 7; O
    PM-SegmentAttr; M | Cardiovascular 24; M
    MetricClassAttr 2; M
    MetricClassAttr 5; M
    MetricClassAttr 8; O
    MetricClassAttr 11; M
    MetricClassAttr 14; O
    MetricClassAttr 17; C
    NumericClassAttr 2; M
    NumericClassAttr 5; M
    MetricRelGroup 2; O
    ScannerAttr 1; M | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|------------------| +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| Spec | [ITU-T H.812.1] | | | | +| Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Longitude Object, the Metric and Numeric attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_025 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Longitude object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Longitude object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Longitude object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454251^MDC_HF_LONGITUDE^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Longitude object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 262880^MDC_DIM_ANG_DEG^MDC
      5. e. Longitude Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Longitude object.
        • OBX-5 = OBX-4 of Session or Subsession object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = Numeric value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-011 | | | | | +| TP label | Slopes Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | | | +| | | Cardiovascular 27; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | | | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | | | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | | | +| | | ScannerAttr 1; M | ScannerAttr 2; M | | | +| | | ScannerAttr 4; M | | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Slopes Object, the Metric and Numeric attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_024 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Slopes object.

    | | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. At least one Slopes object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
    | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. Slopes object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8454253^MDC_HF_SLOPES^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Slopes object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 262656^MDC_DIM_DIMLESS^MDC

    e. Slopes Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Slopes object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|----------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-012 | | | +| TP label | Speed Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | +| | | Cardiovascular 29; M | Cardiovascular 30; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable | DataGuidelines 22; M | | + +| | Items | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| Test purpose | Check that:
    The presence of the attributes of the Speed Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_023 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Speed object. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Speed object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Speed object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454254^MDC_HF_SPEED^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Speed object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 268704^MDC_DIM_M_PER_MIN^MDC, or 268832^MDC_DIM_FOOT_PER_MIN^MDC, or 268864^MDC_DIM_INCH_PER_MIN^MDC, or 268896^MDC_DIM_STEP_PER_MIN^MDC
      5. e. Speed Measurement Type attribute follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 67883^MDC_ATTR_ID_PHYSIO^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Speed object.
        • OBX-5 = 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC or 8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC or 8456146^MDC_HF_MAX^MDC or 8456147^MDC_HF_MIN^MDC
      6. f. Speed Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Speed object.
        • OBX-5 = OBX-4 of Session or Subsession object
      7. g. No PM-Store, PM-Segment or Scanner attributes are present.
      8. h. One of these timestamp attributes can be present:
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ❑ MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-013 | | | | +| TP label | Cadence Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 31; M | +| | | Cardiovascular 32; M | Cardiovascular 33; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Cadence Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_022 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Cadence object. | | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. Check in the captured message that:
    • a. At least one Cadence object has sent at least one observation.
    • b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. Each MDC code using a CWE data type is encoded as:
    <refldValue>^<refldName>^<refldCodeSystem>

    where:

    • refldValue: is a 32 bit integer (required)
    • refldName: is the normative nomenclature name for the unique code point (recommended)
    • refldCodeSystem = "MDC" (required).

    d. Cadence object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8454255^MDC_HF_CAD^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Cadence object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 268960^MDC_DIM_RPM^MDC

    e. Cadence Measurement Type attribute follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 67883^MDC_ATTR_ID_PHYSIO^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Cadence object.
    • OBX-5 = 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC or 8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC or 8456146^MDC_HF_MAX^MDC or 8456147^MDC_HF_MIN^MDC

    f. Cadence Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Cadence object.
    • OBX-5 = OBX-4 of Session or Subsession object

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|----------------------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-014 | | | +| TP label | Incline Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | +| | | Cardiovascular 35; M | Cardiovascular 36; M | +| | | | MetricClassAttr 1; M | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | MetricRelGroup 2; O | PM-StoreAttr; M | PM-SegmentAttr; M | +| | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | ScannerAttr 4; M | | | +| Spec | [ITU-T H.812.1] | | | +| Testable items | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Incline Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_021 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with an Incline object.

    | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Incline object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Incline object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454256^MDC_HF_INCLINE^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Incline object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 262688^MDC_DIM_PERCENT^MDC or 262880^MDC_DIM_ANG_DEG^MDC
      5. e. Incline Measurement Type attribute follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 67883^MDC_ATTR_ID_PHYSIO^MDC
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Incline object.
    • OBX-5 = 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC or 8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC or 8456146^MDC_HF_MAX^MDC or 8456147^MDC_HF_MIN^MDC

    f. Incline Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Incline object.
    • OBX-5 = OBX-4 of Session or Subsession object

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|---------------------|----------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-015 | | | +| TP label | Heart Rate Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | +| | | Cardiovascular 38; M | Cardiovascular 39; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that: | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The presence of the attributes of the Heart Rate Object, the Metric and Numeric attributes and their respective values. | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_020 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Heart Rate object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Heart Rate object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Heart Rate object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454258^MDC_HF_HR^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Heart Rate object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264864^MDC_DIM_BEAT_PER_MIN^MDC
      5. e. Heart Rate Measurement Type attribute follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 67883^MDC_ATTR_ID_PHYSIO^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Heart Rate object.
        • OBX-5 = 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC or 8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC or 8456146^MDC_HF_MAX^MDC or 8456147^MDC_HF_MIN^MDC
      6. f. Heart Rate Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Heart Rate object.
        • OBX-5 = OBX-4 of Session or Subsession object
      7. g. No PM-Store, PM-Segment or Scanner attributes are present.
      8. h. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-016 | | | | +| TP label | Max User Heart Rate Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 40; M | +| | | Cardiovascular 41; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 2; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Max User Heart Rate Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_019 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Max User Heart Rate object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Max User Heart Rate object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • ❑ refldValue: is a 32 bit integer (required)
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Max User Heart Rate object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8454257^MDC_HF_HR_MAX_USER^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Max User Heart Rate object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 264864^MDC_DIM_BEAT_PER_MIN^MDC

    e. Max User Heart Rate Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Max User Heart Rate object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-017 | | | | +| TP label | Power Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 42; M | +| | | Cardiovascular 43; M | Cardiovascular 44; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | PM-SegmentAttr; M | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------|------------------| +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Power Object, the Metric and Numeric attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_018 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Power object.

    | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Power object has sent at least one observation..
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Power object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454259^MDC_HF_POWER^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Power object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 266176^MDC_DIM_WATT^MDC
      5. e. Power Measurement Type attribute follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 67883^MDC_ATTR_ID_PHYSIO^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Power object.
        • OBX-5 = 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC or 8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC or 8456146^MDC_HF_MAX^MDC or 8456147^MDC_HF_MIN^MDC
      6. f. Power Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Power object.
        • OBX-5 = OBX-4 of Session or Subsession object
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-018 | | | +| TP label | Resistance Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | +| | | Cardiovascular 46; M | Cardiovascular 47; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Resistance Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_017 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Resistance object. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Resistance object has sent at least one observation.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Resistance object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8454260^MDC_HF_RESIST^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Resistance object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = Leave blank or use 262656^MDC_DIM_DIMLESS^MDC

    e. Resistance Measurement Type attribute follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 67883^MDC_ATTR_ID_PHYSIO^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Resistance object.
    • OBX-5 = 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC or 8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC or 8456146^MDC_HF_MAX^MDC or 8456147^MDC_HF_MIN^MDC

    f. Resistance Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Resistance object.
    • OBX-5 = OBX-4 of Session or Subsession object

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | +|-----------------|----------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-019 | +| TP label | Stride Length Numeric Object | + +| | | | | | +|--------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 48; M | +| | | Cardiovascular 49; M | Cardiovascular 50; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | | Check that:
    The presence of the attributes of the Stride Length Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_016 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Stride Length object. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Stride Length object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Stride Length object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454261^MDC_HF_STRIDE^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Stride Length object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263424^MDC_DIM_M^MDC or 263520^MDC_DIM_INCH^MDC
      5. e. Stride Length Measurement Type attribute follows this OBX encoding:
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-2 = 'CWE'
    • OBX-3 = 67883^MDC_ATTR_ID_PHYSIO^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Stride Length object.
    • OBX-5 = 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC or 8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC or 8456146^MDC_HF_MAX^MDC or 8456147^MDC_HF_MIN^MDC

    f. Stride Length Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Stride Length object.
    • OBX-5 = OBX-4 of Session or Subsession object

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-020 | | | | +| TP label | Breathing Rate Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 51; M | +| | | Cardiovascular 52; M | Cardiovascular 53; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | MetricRelGroup 2; O | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    The presence of the attributes of the Breathing Rate Object, the Metric and Numeric attributes and their respective values.

    | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_015 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Breathing Rate object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Breathing Rate object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Breathing Rate object follows this OBX encoding:
        • OBX-2 = 'NM'
          OBX-3 = 151562^MDC_RESP_RATE^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Breathing Rate object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264928^MDC_DIM_RESP_PER_MIN^MDC
      5. e. Breathing Rate Measurement Type attribute follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 67883^MDC_ATTR_ID_PHYSIO^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Breathing Rate object.
        • OBX-5 = 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC or 8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC or 8456146^MDC_HF_MAX^MDC or 8456147^MDC_HF_MIN^MDC
      6. f. Breathing Rate Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Breathing Rate object.
        • OBX-5 = OBX-4 of Session or Subsession object
      7. g. No PM-Store, PM-Segment or Scanner attributes are present.
      8. h. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = Numeric value
    • OBX-18 has a timebase ID.
    MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
    • OBX-5 = Numeric value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-021 | | | +| TP label | Energy Expended Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | +| | | Cardiovascular 55; M | MetricClassAttr 1; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Energy Expended Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_014 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with an Energy Expended object. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. Check in the captured message that:
    1. At least one Energy Expended object has sent at least one observation.
    2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    3. Each MDC code using a CWE data type is encoded as:
      <refldValue>^<refldName>^<refldCodeSystem>
      where:
      refldValue: is a 32 bit integer (required)
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Energy Expended object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8454263^MDC_HF_ENERGY^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Energy Expended object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 268928^MDC_DIM_CAL^MDC or 266112^MDC_DIM_JOULES^MDC

    e. Energy Expended Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Energy Expended object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|----------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-022 | | | +| TP label | Calories Ingested Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | +| | | Cardiovascular 57; M | MetricClassAttr 1; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | | | Cardiovascular 56; M | +| | | | MetricClassAttr 2; M | +| | | | MetricClassAttr 5; M | +| | | | MetricClassAttr 8; O | +| | | | MetricClassAttr 11; M | +| | | | MetricClassAttr 14; O | +| | | | MetricClassAttr 17; C | +| | | | NumericClassAttr 2; M | +| | | | NumericClassAttr 5; M | +| | | | MetricRelGroup 2; O | +| | | | ScannerAttr 1; M | +| | | | ScannerAttr 4; M | + +| | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--|--| +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Calories Ingested Object, the Metric and Numeric attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_013 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Calories object. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Calories Ingested object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Calories Ingested object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454264^MDC_HF_CAL_INGEST^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Calories Ingested object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 268928^MDC_DIM_CAL^MDC
      5. e. Calories Ingested Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Calories Ingested object.
        • OBX-5 = OBX-4 of Session or Subsession object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
    | | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------| +| |
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-023 | | | | +| TP label | Carbohydrate Calories Ingested Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 58; M | +| | | Cardiovascular 59; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 2; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Carbohydrate Calories Ingested Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_012 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Calories Ingested object. | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. At least one Carbohydrate Calories Ingested object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. Carbohydrate Calories Ingested object follows this OBX encoding:
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-2 = 'NM'
    • OBX-3 = 8454265^MDC_HF_CAL_INGEST_CARB^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Carbohydrate Calories Ingested object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 268928^MDC_DIM_CAL^MDC

    e. Carbohydrate Calories Ingested Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Carbohydrate Calories Ingested object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|--------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-024 | | | +| TP label | Sustained Phys Activity Threshold Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | +| | | Cardiovascular 61; M | MetricClassAttr 1; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    The presence of the attributes of the Sustained Phys Activity Threshold Object, the Metric and Numeric attributes and their respective values.

    | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_011 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Sustained Phys Activity Threshold object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Sustained Phys Activity Threshold object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Sustained Phys Activity Threshold object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454266^MDC_HF_SUST_PA_THRESHOLD^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Sustained Phys Activity Threshold object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264352^MDC_DIM_MIN^MDC
      5. e. Sustained Phys Activity Threshold Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Sustained Phys Activity Threshold object.
        • OBX-5 = OBX-4 of Session or Subsession object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | + +| | | +|---------------------------|------------------------------------------------| +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-025 | | | | +| TP label | Activity Intensity Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 62; M | +| | | Cardiovascular 63; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 2; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Activity Intensity Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_010 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with an Activity Intensity object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Activity Intensity object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Activity Intensity object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454271^MDC_HF_ACTIVITY_INTENSITY^MDC
    | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Activity Intensity object respectively.
    • OBX-5 = Numeric Value
    • OBX-6 = 262688^MDC_DIM_PERCENT^MDC

    e. Activity Intensity Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Activity Intensity object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-026 | | | +| TP label | Body Weight Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | +| | | Cardiovascular 65; M | MetricClassAttr 1; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| | | | | +| Test purpose | Check that:
    The presence of the attributes of the Body Weight Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_009 | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Body Weight object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Body Weight object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Body Weight object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 188736^MDC_MASS_BODY_ACTUAL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Body Weight object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263872^MDC_DIM_G^MDC or 263904^MDC_DIM_LB^MDC
      5. e. Body Weight Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Body Weight object.
        • OBX-5 = OBX-4 of Session or Subsession object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | +|-----------------|----------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-027 | +| TP label | Height Numeric Object | + +| | | | | | +|--------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 66; M | +| | | Cardiovascular 67; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 2; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | | Check that:
    The presence of the attributes of the Height Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_008 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Height object. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Height object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Height object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 188740^MDC_LEN_BODY_ACTUAL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Height object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263424^MDC_DIM_M^MDC or 263488^MDC_DIM_FOOT^MDC
      5. e. Height Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Height object.
    • OBX-5 = OBX-4 of Session or Subsession object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-028 | | | +| TP label | Age Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | +| | | Cardiovascular 69; M | MetricClassAttr 1; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| | | | | +| Test purpose | Check that:
    The presence of the attributes of the Age Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_007 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with an Age object. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload. | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 2. | Check in the captured message that:
    1. At least one Age object has sent at least one observation.
    2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    3. Each MDC code using a CWE data type is encoded as:
      <refIdValue>^<refIdName>^<refIdCodeSystem>
      where:
      • refIdValue: is a 32 bit integer (required)
      • refIdName: is the normative nomenclature name for the unique code point (recommended)
      • refIdCodeSystem = "MDC" (required).
    4. Age object follows this OBX encoding:
      • OBX-2 = 'NM'
      • OBX-3 = 8454270^MDC_HF_AGE^MDC
      • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Age object respectively.
      • OBX-5 = Numeric value
      • OBX-6 = 264512^MDC_DIM_YR^MDC
    5. Age Source-Handle-Reference attribute follows this OBX encoding:
      • OBX-2 = 'ST'
      • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
      • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Age object.
      • OBX-5 = OBX-4 of Session or Subsession object
    6. No PM-Store, PM-Segment or Scanner attributes are present.
    7. One of these timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------|----------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-029 | | | | +| TP label | Activity Time Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 70; M | +| | | Cardiovascular 71; M | Cardiovascular 72; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | MetricRelGroup 2; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Activity Time Object, the Metric and Enumeration attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_006 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with an Activity Time object.

    | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Activity Time object has sent at least one observation. Each one conforms to the following steps.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Activity Time object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8454269^MDC_HF_ACTIVITY_TIME^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Activity Time object respectively.
        • OBX-5 = 8455144^MDC_HF_ACT_AMB^MDC or 8455145^MDC_HF_ACT_REST^MDC or 8455146^MDC_HF_ACT_MOTOR^MDC or 8455147^MDC_HF_ACT_LYING^MDC or 8455148^MDC_HF_ACT_SLEEP^MDC or 8455149^MDC_HF_ACT_PHYS^MDC or 8455150^MDC_HF_ACT_SUS_PHYS^MDC or 8455151^MDC_HF_ACT_UNKNOWN^MDC
      5. e. Activity Time Measure Active Period attribute follows this OBX encoding:
        • OBX-2 = 'NM'
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-3 = 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Activity Time object.
    • OBX-5 = Numeric value
    • OBX-6 = 264320^MDC_DIM_SEC^MDC

    f. Activity Time Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.b, where 'b' is a number indicating the facet level of the Activity Time object.
    • OBX-5 = OBX-4 of Session or Subsession object

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CV/BV-030 | | | | +| TP label | Program Identifier Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | Cardiovascular 1; M | Cardiovascular 2; M | Cardiovascular 73; M | +| | | Cardiovascular 74; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | ScannerAttr 3; M | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | +| Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Program Identifier Object, the Metric and Enumeration attributes and their respective values. | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_SEN_000 AND C_SEN_CV_001 AND C_SEN_CV_005 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a cardiovascular device with a Program Identifier object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a cardiovascular device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Program Identifier object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Program Identifier object follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 8454252^MDC_HF_PROGRAM_ID^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Program Identifier object respectively.
          OBX-5 = String value
      5. e. Program Identifier Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Program Identifier object.
        • OBX-5 = OBX-4 of Session or Subsession object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +## A.10 Subgroup 1.4.9: Strength fitness equipment (ST) + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ST/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | +| | | MDSObject 1; M | MDSObject 2; M | +| | | MDSObject 4; M | MDSObject 5; M | +| | | MDSObject 7; M | MDSObject 8; M | +| | | MDSObject 10; M | MDSObject 11; M | +| | | MDSObject 13; O | MDSObject 14; O | +| | | MDSObject 16; M | MDSObject 17; M | +| | | MDSObject 19; M | MDSObject 20; M | +| | | MDSObject 22; M | MDSObject 23; M | +| | | MDSObject 25; M | MDSObject 26; M | +| | | MDSObject 28; M | MDSObject 29; M | +| | | MDSObject 31; M | MDSObject 32; M | +| | | Timestamp 13; O | Timestamp 14; O | +| | | Timestamp 17; M | Timestamp 15; O | +| | Spec | [IHE PCD TF 2] | | +| | Testable items | DeviceTimeSync1; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_ST_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a Strength Fitness device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a strength fitness device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        refldValue: is a 32 bit integer (required)
    | | | + +- refldName: is the normative nomenclature name for the unique code point (recommended) +- refldCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: + - OBX-2 is empty + - If the System-Type attribute is valued, OBX-3 = 528426^MDC\_DEV\_SPEC\_PROFILE\_HF\_STRENGTH^MDC + - If the System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System Id is 16 characters given by the PIXIT I\_SEN\_ST\_001. +- e. System model attribute is sent in two different OBX segments: + - System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. + +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) + +- ❑ Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) +- ❑ Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC +- Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If the Power-Status attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + +- OBX-5 = NM data type value +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC + +k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC +- OBX-5 = Use the value contained in the BatMeasure object +- OBX-6 = Use the OID contained in the BatMeasure object + +l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + +- OBX-2 = 'CWE' +- OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC +- OBX-5 = One of: + - 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + - 254^auth-body-experimental, + - 255^auth-body-reserved + +m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + +- Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + - OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC + - OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment. + - OBX-5 = .. +- Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'NA' + - OBX-3 = 532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC + - OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment. + - OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 42 (ST v1.0), 16426 (ST v1.5 Wireless PAN), 8234 (ST v1.5 Wired PAN), or 24618 (ST v1.5 Sensor LAN) +- Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'CWE' + - OBX-3 = 532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • ❑ OBX-2 = 'CWE'
    • ❑ OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • ❑ OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ST/BV-001 | | | | +| TP label | Set Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | StrengthFitness 2; M | StrengthFitness 4; M | StrengthFitness 5; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Set Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_ST_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a Strength Fitness device. | | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a Strength Fitness device using SOAP or hData observation upload.
    2. Check in the captured message that:
    1. At least one Set object has sent at least one observation.
    2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Set object follows this OBX encoding:

    • OBX-2 is empty
    • OBX-3 = 8454344^MDC_HF_SET^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Set object respectively.
    • OBX-5 is empty
    • OBX-20 = Any of the muscle sites defined in 10442. For example 459284^MDC_MUSC_THORAX_PECTORAL_MAJOR^MDC

    e. Set Measure Active Period attribute follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Set object.
    • OBX-5 = Numeric value
    • OBX-6 = 264320^MDC_DIM_SEC^MDC

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the muscle the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 7 (MDC_PART_SITES)

    Number of the attribute is given in 10442

    For example:

    MDC_MUSC_THORAX_PECTORAL_MAJOR = 532 → 7*216+532 = 459284

    There is an errata in Appendix J Table J-24 in [b-CDG 2010]. Set object OBX-2 must be empty and not 'NM' as indicated, because OBX-5 is empty.

    NOTE – [b-CDG 2010] Table J-24 corresponds to Table VIII.24 in [ITU-T H.810 (2015)]; see Table 2.

    | + +| | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ST/BV-002 | | | | | +| TP label | Repetition Count Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | StrengthFitness 1; M | StrengthFitness 2; M | | | +| | | StrengthFitness 7; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | | | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Repetition Count Object, the Metric and Numeric attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_ST_001 AND C_SEN_ST_002 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a strength fitness device with a Repetition Count object.

    | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a strength fitness device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Repetition Count object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Repetition Count object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454346^MDC_HF_REPETITION_COUNT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Repetition Count object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = Leave blank or 262656^MDC_DIM_DIMLESS^MDC
    | | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    e. Repetition Count Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Repetition Count object.
    • OBX-5 = OBX-4 of Set object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ST/BV-003 | | | | | +| TP label | Resistance Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | StrengthFitness 1; M | StrengthFitness 2; M | | | +| | | StrengthFitness 9; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | | | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | | | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Resistance Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_ST_001 AND C_SEN_ST_003 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a strength fitness device with a Resistance object. | | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a strength fitness device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Resistance object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Resistance object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454347^MDC_HF_RESISTANCE^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Resistance object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 262656^MDC_DIM_DIMLESS^MDC or 263872^MDC_DIM_G^MDC or 263904^MDC_DIM_LB^MDC
      5. e. Resistance Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Resistance object.
        • OBX-5 = OBX-4 of Set object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|----------------------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ST/BV-004 | | | +| TP label | Repetition Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable | StrengthFitness 1; M | StrengthFitness 2; M | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| items | StrengthFitness 11; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 2; O | +| | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| Spec | [ITU-T H.812.1] | | | +| Testable items | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Repetition Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_ST_001 AND C_SEN_ST_004 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a strength fitness device with a Repetition object.

    | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a strength fitness device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Repetition object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Repetition object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8454345^MDC_HF_REPETITION ^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Repetition object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263424^MDC_DIM_M^MDC or 263520^MDC_DIM_INCH^MDC
      5. e. Repetition Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Repetition object.
    • OBX-5 = OBX-4 of Set object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ST/BV-005 | | | +| TP label | Exercise Position Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | StrengthFitness 1; M | StrengthFitness 2; M | +| | | StrengthFitness 13; M | MetricClassAttr 1; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| | | | | +| Test purpose | Check that:
    The presence of the attributes of the Exercise Position Object, the Metric and Enumeration attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_ST_001 AND C_SEN_ST_005 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a strength fitness device with an Exercise Position object. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a strength fitness device using SOAP or hData observation upload.
    2. Check in the captured message that: | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. a. At least one Exercise Position object has sent at least one observation.
    2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    3. c. Each MDC code using a CWE data type is encoded as:
      <refIdValue>^<refIdName>^<refIdCodeSystem>
      where:
      • ❑ refIdValue: is a 32 bit integer (required)
      • ❑ refIdName: is the normative nomenclature name for the unique code point (recommended)
      • ❑ refIdCodeSystem = "MDC" (required).
    4. d. Exercise Position object follows this OBX encoding:
      • ❑ OBX-2 = 'CWE'
      • ❑ OBX-3 = 8454348^MDC_HF_EXERCISE_POSITION^MDC
      • ❑ OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Exercise Position object respectively.
      • ❑ OBX-5 = One of the values: 8455347^MDC_HF_POSITION_INCLINE^MDC
        8455348^MDC_HF_POSITION_DECLINE^MDC
        8455349^MDC_HF_POSITION_SEATED^MDC
        8455350^MDC_HF_POSITION_STANDING^MDC
        8455351^MDC_HF_POSITION_KNEELING^MDC
        8455352^MDC_HF_POSITION_BENTOVER^MDC
        8455353^MDC_HF_POSITION_HANGING^MDC
        8455354^MDC_HF_POSITION_OVERHEAD^MDC
        8455355^MDC_HF_POSITION_LYING^MDC
    5. e. Exercise Position Source-Handle-Reference attribute follows this OBX encoding:
      • ❑ OBX-2 = 'ST'
      • ❑ OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
      • ❑ OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Exercise Position object.
      • ❑ OBX-5 = OBX-4 of Set object
    6. f. No PM-Store, PM-Segment or Scanner attributes are present.
    7. g. One of these timestamp attributes can be present:
      • ❑ MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
      • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ST/BV-006 | | | | | +| TP label | Exercise Laterality Enumeration Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | StrengthFitness 1; M | StrengthFitness 2; M | | | +| | | StrengthFitness 15; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | | | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | | | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | | | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | | | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Exercise Laterality Object, the Metric and Enumeration attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_ST_001 AND C_SEN_ST_006 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a strength fitness device with an Exercise Laterality object.

    | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a strength fitness device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Exercise Laterality object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Exercise Laterality object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8454349^MDC_HF_EXERCISE_LATERALITY^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Exercise Laterality object respectively.
        • OBX-5 = One of the values: 8455344^MDC_HF_LATERALITY_BOTH^MDC
          8455345^MDC_HF_LATERALITY_RIGHT^MDC
    | | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    8455346^MDC_HF_LATERALITY_LEFT^MDC

    e. Exercise Laterality Source-Handle-Reference attribute follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Exercise Laterality object.
    • OBX-5 = OBX-4 of Set object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ST/BV-007 | | | | | +| TP label | Exercise Grip Enumeration Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | StrengthFitness 1; M | StrengthFitness 2; M | | | +| | | StrengthFitness 17; M | MetricClassAttr 1; M | | | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | | | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | | | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | | | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | | | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | | | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | | | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | | | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | | | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | | | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Exercise Grip Object, the Metric and Enumeration attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_ST_001 AND C_SEN_ST_007 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a strength fitness device with an Exercise Grip object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a strength fitness device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Exercise Grip object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Exercise Grip object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8454350^MDC_HF_EXERCISE_GRIP^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Exercise Grip object respectively.
        • OBX-5 = One of the values: 8455544^MDC_HF_GRIP_PARALLEL^MDC
          8455545^MDC_HF_GRIP_OVERHAND^MDC
          8455546^MDC_HF_GRIP_UNDERHAND^MDC
          8455547^MDC_HF_GRIP_CLOSE^MDC
          8455548^MDC_HF_GRIP_WIDE^MDC
          8455549^MDC_HF_GRIP_GRIPLESS^MDC
      5. e. Exercise Grip Source-Handle-Reference attribute follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Exercise Grip object.
        • OBX-5 = OBX-4 of Set object
      6. f. No PM-Store, PM-Segment or Scanner attributes are present.
      7. g. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ST/BV-008 | | | +| TP label | Exercise Movement Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | StrengthFitness 1; M | StrengthFitness 2; M | +| | | StrengthFitness 17; M | MetricClassAttr 1; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 6; M | MetricRelGroup 2; O | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Exercise Movement Object, the Metric and Enumeration attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_ST_001 AND C_SEN_ST_008 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a strength fitness device with an Exercise Movement object.

    | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a strength fitness device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Exercise Movement object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Exercise Movement object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8454351^MDC_HF_EXERCISE_MOVEMENT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Exercise Movement object respectively.
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
      • OBX-5 = One of the values:
        8455444^MDC_HF_MOVEMENT_FLEXION^MDC
        8455445^MDC_HF_MOVEMENT_EXTENSION^MDC
        8455446^MDC_HF_MOVEMENT_ROTATION^MDC
        8455447^MDC_HF_MOVEMENT_ABDUCTION^MDC
        8455448^MDC_HF_MOVEMENT_ADDUCTION^MDC
    • e. Exercise Movement Source-Handle-Reference attribute follows this OBX encoding:
      • OBX-2 = 'ST'
      • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
      • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Exercise Movement object.
      • OBX-5 = OBX-4 of Set object
    • f. No PM-Store, PM-Segment or Scanner attributes are present.
    • g. One of these timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +### A.11 Subgroup 1.4.10: Independent living activity hub (HUB) + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | +| | | MDSObject 1; M | MDSObject 2; M | +| | | MDSObject 4; M | MDSObject 5; M | +| | | MDSObject 7; M | MDSObject 8; M | +| | | MDSObject 10; M | MDSObject 11; M | +| | | MDSObject 13; O | MDSObject 14; O | +| | | MDSObject 16; M | MDSObject 17; M | +| | | MDSObject 19; M | MDSObject 20; M | +| | | MDSObject 22; M | MDSObject 23; M | +| | | MDSObject 25; M | MDSObject 26; M | +| | | MDSObject 28; M | MDSObject 29; M | +| | | MDSObject 31; M | ActivityHub 5; M | +| | | Timestamp 13; O | Timestamp 14; O | +| | | Timestamp 17; M | Timestamp 15; O | +| | Spec | [IHE PCD TF 2] | | +| | Testable items | DeviceTimeSync1; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living Hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        refIdValue: is a 32 bit integer (required)
    | | | + +- refIdName: is the normative nomenclature name for the unique code point (recommended) +- refIdCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: + - OBX-2 is empty + - If the System-Type attribute is valued, OBX-3 = 528455^MDC\_DEV\_SPEC\_PROFILE\_AI\_ACTIVITY\_HUB^MDC + - If the System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System\_Id is 16 characters given by the PIXIT I\_SEN\_HUB\_001. +- e. System model attribute is sent in two different OBX segments: + - System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + +- OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. + +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) +- Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) + - Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC + - Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + +- OBX-14 = UTC value + - ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase + - ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase + - ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - ❑ Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC + - ❑ Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If the Power-Status attribute is valued, it is sent as an independent OBX segment: +- ❑ OBX-2 = 'ST' + - ❑ OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - ❑ OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC +- OBX-5 = NM data type value +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC + +k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC +- OBX-5 = Use the value contained in the BatMeasure object +- OBX-6 = Use the OID contained in the BatMeasure object + +l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + +- OBX-2 = 'CWE' +- OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC +- OBX-5 = One of: + 0^auth-body-empty, + 1^auth-body-ieee-11073, + 2^auth-body-continua, + 254^auth-body-experimental, + 255^auth-body-reserved + +m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + +- Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + +- OBX-2 = 'ST' +- OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC +- OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment. +- OBX-5 = .. + +- Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + +- OBX-2 = 'NA' +- OBX-3 = 532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC +- OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment. +- OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 71 (HUB v1.0), 16455 (HUB v1.5 Wireless PAN), 8263 (HUB v1.5 Wired PAN), or 24647 (HUB v1.5 Sensor LAN) + +- Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding: + +- OBX-2 = 'CWE' + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
    • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If the System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • □ OBX-2 = 'CWE'
    • □ OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • □ OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-001 | | | +| TP label | Fall Sensor Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | +| | | ActivityHub 4; M | ActivityHub 6; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the Fall Sensor Object, the Metric and Enumeration attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_002 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a Fall Sensor object. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. Check in the captured message that:
    a. At least one Fall Sensor object has sent at least one observation. | | | + +- b. Handle attribute (MDC\_ATTR\_ID\_HANDLE), Metric-Spec-Small attribute (MDC\_ATTR\_METRIC\_SPEC\_SMALL) and Metric-Structure-Small (MDC\_ATTR\_METRIC\_STRUCT\_SMALL) attribute and Attribute-Value-Map (MDC\_ATTR\_ATTRIBUTE\_VALUE\_MAP) are not present +- c. Each MDC code using a CWE data type is encoded as: +^^ +where: + - refIdValue: is a 32 bit integer (required) + - refIdName: is the normative nomenclature name for the unique code point (recommended) + - refIdCodeSystem = "MDC" (required). +- d. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- e. Fall Sensor object follows this OBX encoding: + - OBX-2 = 'CWE' + - OBX-3 = 8519681^MDC\_AI\_TYPE\_SENSOR\_FALL^MDC + - OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Fall Sensor object respectively. + - OBX-5 = One of the following flags: +<0 or 1>^fall-detected(0) +Additionally, optionally, any of the general sensor health flags: +<0 or 1>^auto-presence-received(16), +<0 or 1>^auto-presence-failed(17), +<0 or 1>^low-battery(18), +<0 or 1>^fault(19), +<0 or 1>^end-of-life(20) +- f. Fall Sensor Location attribute follows this OBX encoding: + - OBX-2 = 'CWE' + - OBX-3 = 8520703^MDC\_AI\_LOCATION^MDC or 68193^MDC\_ATTR\_SUPPLEMENTAL\_TYPES^MDC + - OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Fall Sensor object. + - OBX-5 = Any of the 10471 location codes that are specified in the Supplemental-Types. +For example: 8523328^MDC\_AI\_LOCATION\_LIVINGROOM^MDC +- g. No PM-Store, PM-Segment or Scanner attributes are present. +- h. One of these timestamp attributes can be present: + - MDC\_ATTR\_TIME\_STAMP\_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ] + - MDC\_ATTR\_TIME\_STAMP\_REL, transmitted as a facet of the observation: + - OBX-5 = Numeric value + - OBX-18 has a timebase ID. + - MDC\_ATTR\_TIME\_STAMP\_HI\_RES, transmitted as a facet of the observation. + - OBX-5 = Numeric value + - OBX-18 has a timebase ID. + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*216+3648 = 8523328.

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-002 | | | +| TP label | PERS Sensor Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | +| | | ActivityHub 4; M | ActivityHub 8; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose |

    Check that:

    The presence of the attributes of the PERS Sensor Object, the Metric and Enumeration attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_003 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a PERS Sensor object.

    | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living Hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one PERS Sensor object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • refIdValue: is a 32 bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:

    • <bitValue> = <0 or 1>
    • <bitName> is recommended to be the ASN.1 name for the bit
    • <bitPosition> is the normative position of the bit

    e. PERS Sensor object follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8519682^MDC_AI_TYPE_SENSOR_PERS^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the PERS Sensor object respectively.
    • OBX-5 = One of the following flags:
      <0 or 1>^pers-activated(0)
      Additionally, optionally, any of the general sensor health flags:
      <0 or 1>^auto-presence-received(16),
      <0 or 1>^auto-presence-failed(17),
      <0 or 1>^low-battery(18),
      <0 or 1>^fault(19),
      <0 or 1>^end-of-life(20)

    f. PERS Sensor Location attribute follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the PERS Sensor object.
    • OBX-5 = Any of the 10471 location codes that are specified in the Supplemental-Types.
      For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130 \cdot 2^{16} + 3648 = 8523328.

    | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-003 | | | | +| TP label | Environmental Sensor - Smoke Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | ActivityHub 3; M | +| | | ActivityHub 4; M | ActivityHub 10; M | ActivityHub 11; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Environmental Sensor – Smoke Object, the Metric and Enumeration attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_004 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with an Environmental Sensor - Smoke object.

    | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Environmental Sensor – Smoke object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • • refIdValue: is a 32 bit integer (required)
        • • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • <bitValue> = <0 or 1>
    • <bitName> is recommended to be the ASN.1 name for the bit
    • <bitPosition> is the normative position of the bit

    e. Environmental Sensor – Smoke object follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8519683^MDC_AI_TYPE_SENSOR_SMOKE^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Environmental Sensor – Smoke object respectively.
    • OBX-5 = One of the following flags:
      <0 or 1>^condition-detected(0)
      Additionally, optionally, any of the general sensor health flags:
      <0 or 1>^auto-presence-received(16),
      <0 or 1>^auto-presence-failed(17),
      <0 or 1>^low-battery(18),
      <0 or 1>^fault(19),
      <0 or 1>^end-of-life(20)

    f. Environmental Sensor – Smoke Location attribute follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Environmental Sensor – Smoke object.
    • OBX-5 = Any of the 10471 location codes that are specified in the supplemental-types.
      For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*216+3648 = 8523328.

    | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-004 | | | | +| TP label | Environmental Sensor - CO Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | ActivityHub 3; M | +| | | ActivityHub 4; M | ActivityHub 12; M | ActivityHub 13; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Environmental Sensor – CO Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_005 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with an Environmental Sensor - Smoke object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Environmental Sensor – CO object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • □ refIdValue: is a 32 bit integer (required)
        • □ refIdName: is the normative nomenclature name for the unique code point (recommended)
        • □ refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • □ <bitValue> = <0 or 1>
        • □ <bitName> is recommended to be the ASN.1 name for the bit
        • □ <bitPosition> is the normative position of the bit
      5. e. Environmental Sensor – CO object follows this OBX encoding:
        • □ OBX-2 = 'CWE'
    | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-3 = 8519684^MDC_AI_TYPE_SENSOR_CO^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Environmental Sensor – CO object respectively.
    • OBX-5 = One of the following flags:
      <0 or 1>^condition-detected(0)
      Additionally, optionally, any of the general sensor health flags:
      <0 or 1>^auto-presence-received(16),
      <0 or 1>^auto-presence-failed(17),
      <0 or 1>^low-battery(18),
      <0 or 1>^fault(19),
      <0 or 1>^end-of-life(20)

    f. Environmental Sensor – CO Location attribute follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Environmental Sensor – CO object.
    • OBX-5 = Any of the 10471 location codes that are specified in the supplemental-types.
      For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*216+3648 = 8523328.

    | + +| | | | | +|-----------------|-------------------------------------------------|------------------|----------------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-005 | | | +| TP label | Environmental Sensor - Water Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable | ActivityHub 1; M | ActivityHub 2; M      ActivityHub 3; M | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| items | ActivityHub 4; M | ActivityHub 14; M | ActivityHub 15; M | +| | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| Spec | [ITU-T H.812.1] | | | +| Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Environmental Sensor – Water Object, the Metric and Enumeration attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_006 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with an Environmental Sensor – Water object. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Environmental Sensor – Water object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Environmental Sensor – Water object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 88519685^MDC_AI_TYPE_SENSOR_WATER^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Environmental Sensor – Water object respectively.
        • OBX-5 = One of the following flags:
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    <0 or 1>^condition-detected(0)

    Additionally, optionally, any of the general sensor health flags:

    <0 or 1>^auto-presence-received(16),

    <0 or 1>^auto-presence-failed(17),

    <0 or 1>^low-battery(18),

    <0 or 1>^fault(19),

    <0 or 1>^end-of-life(20)

    f. Environmental Sensor – Water Location attribute follows this OBX encoding:

    • ❑ OBX-2 = 'CWE'
    • ❑ OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • ❑ OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Environmental Sensor – Water object.
    • ❑ OBX-5 = Any of the 10471 location codes that are specified in the Supplemental-Types.

    For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • ❑ MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*2^{16}+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*2^{16}+3648 = 8523328.

    | + +| | | | | | | | | | | | | | | | | | | | | | | +|-----------------------|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------------------|------------------|------------------|------------------|-------------------|-------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-006 | | | | | | | | | | | | | | | | | | | | | +| TP label | Environmental Sensor - Gas Enumeration Object | | | | | | | | | | | | | | | | | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | | | | | | | | | | | | | | | | | +| | Testable items |
    ActivityHub 1; M ActivityHub 2; M ActivityHub 3; M
    ActivityHub 4; M ActivityHub 16; M ActivityHub 17; M
    MetricClassAttr 1; M MetricClassAttr 2; M MetricClassAttr 3; O
    MetricClassAttr 4; M MetricClassAttr 5; M MetricClassAttr 6; O
    MetricClassAttr 7; O MetricClassAttr 8; O MetricClassAttr 9; M
    MetricClassAttr 10; O MetricClassAttr 11; M MetricClassAttr 12; O
    | | ActivityHub 1; M | ActivityHub 2; M | ActivityHub 3; M | ActivityHub 4; M | ActivityHub 16; M | ActivityHub 17; M | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| ActivityHub 1; M | ActivityHub 2; M | ActivityHub 3; M | | | | | | | | | | | | | | | | | | | | +| ActivityHub 4; M | ActivityHub 16; M | ActivityHub 17; M | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | | | | | | | | | | | | | | | | | | | | + +| | | | | | +|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | |

    Check that:

    The presence of the attributes of the Environmental Sensor – Gas Object, the Metric and Enumeration attributes and their respective values.

    | | | +| Applicability | | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_007 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with an Environmental Sensor – Gas object.

    | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Environmental Sensor – Gas object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Environmental Sensor – Gas object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8519686^MDC_AI_TYPE_SENSOR_GAS^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Environmental Sensor – Gas object respectively.
        • OBX-5 = One of the following flags:
          <0 or 1>^condition-detected(0)
          Additionally, optionally, any of the general sensor health flags:
          <0 or 1>^auto-presence-received(16),
          <0 or 1>^auto-presence-failed(17),
          <0 or 1>^low-battery(18),
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    <0 or 1>^fault(19),
    <0 or 1>^end-of-life(20)

    f. Environmental Sensor – Gas Location attribute follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Environmental Sensor – Gas object.
    • OBX-5 = Any of the 10471 location codes that are specified in the supplemental-types.

    For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*216+3648 = 8523328.

    | + +| | | | | +|-----------------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-007 | | | +| TP label | Motion Sensor Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ActivityHub 1; M
    ActivityHub 4; M
    MetricClassAttr 1; M
    MetricClassAttr 4; M
    MetricClassAttr 7; O
    MetricClassAttr 10; O
    MetricClassAttr 13; O
    MetricClassAttr 16; C
    EnumClassAttr 1; M
    EnumClassAttr 4; M
    PM-StoreAttr; M | ActivityHub 2; M
    ActivityHub 18; M
    MetricClassAttr 2; M
    MetricClassAttr 5; M
    MetricClassAttr 8; O
    MetricClassAttr 11; M
    MetricClassAttr 14; O
    MetricClassAttr 17; C
    EnumClassAttr 2; M
    EnumClassAttr 5; O
    PM-SegmentAttr; M | + +| | | | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|----------------------|------------------|--|--| +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | | | +| Spec | [ITU-T H.812.1] | | | | | | +| Testable items | DataGuidelines 21; M | | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Motion Sensor Object, the Metric and Enumeration attributes and their respective values. | | | | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_008 | | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a Motion Sensor object. | | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Motion Sensor object has sent at least one observation
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Motion Sensor object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8519687^MDC_AI_TYPE_SENSOR_MOTION^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Motion Sensor object respectively.
        • OBX-5 = One of the following flags:
          <0 or 1>^motion-detected(0),
          <0 or 1>^motion-detected-delayed(1),
          <0 or 1>^tamper-detected(2)
          Additionally, optionally, any of the general sensor health flags:
          <0 or 1>^auto-presence-received(16),
          <0 or 1>^auto-presence-failed(17),
          <0 or 1>^low-battery(18),
          <0 or 1>^fault(19),
          <0 or 1>^end-of-life(20)
      6. f. Motion Sensor Location attribute follows this OBX encoding:
        • OBX-2 = 'CWE'
    | | | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Motion Sensor object.
    • OBX-5 = Any of the 10471 location codes that are specified in the supplemental-types.

    For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC

    • g. No PM-Store, PM-Segment or Scanner attributes are present.
    • h. One of these timestamp attributes is present:
      • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*216+3648 = 8523328.

    | + +| | | | | +|-----------------|-----------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-008 | | | +| TP label | Property Exit Sensor Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | +| | | ActivityHub 4; M | ActivityHub 20; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    The presence of the attributes of the Property Exit Sensor Object, the Metric and Enumeration attributes and their respective values. | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_009 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a Property Exit Sensor object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Property Exit Sensor object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Property Exit Sensor object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 8519688^MDC_AI_TYPE_SENSOR_PROPEXIT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Property Exit Sensor object respectively.
        • OBX-5 = One of the following flags:
          <0 or 1>^occupant-exit-property(0),
          <0 or 1>^exit-door-left-open(1)
          Additionally, optionally, any of the general sensor health flags:
          <0 or 1>^auto-presence-received(16),
          <0 or 1>^auto-presence-failed(17),
          <0 or 1>^low-battery(18),
          <0 or 1>^fault(19),
          <0 or 1>^end-of-life(20)
      6. f. Property Exit Sensor Location attribute follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Property Exit Sensor object.
    | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = Any of the 10471 location codes that are specified in the supplemental-types.
      For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC
    • g. No PM-Store, PM-Segment or Scanner attributes are present.
    • h. One of these timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation:
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*216+3648 = 8523328.

    | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-009 | | | +| TP label | Enuresis Sensor Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | +| | | ActivityHub 4; M | ActivityHub 22; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose |

    Check that:

    The presence of the attributes of the Enuresis Sensor Object, the Metric and Enumeration attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_010 | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a Enuresis Sensor object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Enurisis Sensor object has sent at least one observation
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Enuresis Sensor object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8519689^MDC_AI_TYPE_SENSOR_ENURESIS^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Enuresis Sensor object respectively.
        • OBX-5 = One of the following flags:
          <0 or 1>^enuresis-detected(0)
          Additionally, optionally, any of the general sensor health flags:
          <0 or 1>^auto-presence-received(16),
          <0 or 1>^auto-presence-failed(17),
          <0 or 1>^low-battery(18),
          <0 or 1>^fault(19),
          <0 or 1>^end-of-life(20)
      6. f. Enuresis Sensor Location attribute follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Enuresis Sensor object.
        • OBX-5 = Any of the 10471 location codes that are specified in the Supplemental-Types.
          For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC
      7. g. No PM-Store, PM-Segment or Scanner attributes are present.
      8. h. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    ❏ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:

    • • OBX-5 = Numeric value
    • • OBX-18 has a timebase ID.

    ❏ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.

    • • OBX-5 = Numeric value
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*216+3648 = 8523328.

    | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-010 | | | | +| TP label | Contact Closure Sensor Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | ActivityHub 3; M | +| | | ActivityHub 4; M | ActivityHub 24; M | ActivityHub 25; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Contact Closure Sensor Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_011 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a Contact Closure Sensor object. | | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. Check in the captured message that: | | | | + +- a. At least one Contact Closure Sensor object has sent at least one observation. +- b. Handle attribute (MDC\_ATTR\_ID\_HANDLE), Metric-Spec-Small attribute (MDC\_ATTR\_METRIC\_SPEC\_SMALL) and Metric-Structure-Small (MDC\_ATTR\_METRIC\_STRUCT\_SMALL) attribute and Attribute-Value-Map (MDC\_ATTR\_ATTRIBUTE\_VALUE\_MAP) are not present +- c. Each MDC code using a CWE data type is encoded as: +`^^` +where: + - refIdValue: is a 32 bit integer (required) + - refIdName: is the normative nomenclature name for the unique code point (recommended) + - refIdCodeSystem = "MDC" (required). +- d. A bit flag value is encoded as `^()`, where: + - `` = `<0 or 1>` + - `` is recommended to be the ASN.1 name for the bit + - `` is the normative position of the bit +- e. Contact Closure Sensor object follows this OBX encoding: + - OBX-2 = 'CWE' + - OBX-3 = 8519690^MDC\_AI\_TYPE\_SENSOR\_CONTACTCLOSURE^MDC + - OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Contact Closure Sensor object respectively. + - OBX-5 = One of the following flags: +`<0 or 1>^contact-opened(0),` +`<0 or 1>^contact-closed(1)` +Additionally, optionally, any of the general sensor health flags: +`<0 or 1>^auto-presence-received(16),` +`<0 or 1>^auto-presence-failed(17),` +`<0 or 1>^low-battery(18),` +`<0 or 1>^fault(19),` +`<0 or 1>^end-of-life(20)` +- f. Contact Closure Sensor Location attribute follows this OBX encoding: + - OBX-2 = 'CWE' + - OBX-3 = 8520703^MDC\_AI\_LOCATION^MDC or 68193^MDC\_ATTR\_SUPPLEMENTAL\_TYPES^MDC + - OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Contact Closure Sensor object. + - OBX-5 = Any of the 10471 location codes that are specified in the supplemental-types. +For example: 8523328^MDC\_AI\_LOCATION\_LIVINGROOM^MDC +- g. No PM-Store, PM-Segment or Scanner attributes are present. +- h. One of these timestamp attributes can be present: + - MDC\_ATTR\_TIME\_STAMP\_ABS, mapped in OBX-14 of the observation metric-level and encoded as: `YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]` + - MDC\_ATTR\_TIME\_STAMP\_REL, transmitted as a facet of the observation: + - OBX-5 = Numeric value + - OBX-18 has a timebase ID. + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
    • • OBX-5 = Numeric value
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*2^{16}+3648 = 8523328.

    | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-011 | | | | +| TP label | Usage Sensor Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | ActivityHub 3; M | +| | | ActivityHub 4; M | ActivityHub 26; M | ActivityHub 27; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Usage Sensor Object, the Metric and Enumeration attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_012 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a Usage Sensor object. | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. At least one Usage Sensor object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small
    | | | | + +(MDC\_ATTR\_METRIC\_STRUCT\_SMALL) attribute and Attribute-Value-Map (MDC\_ATTR\_ATTRIBUTE\_VALUE\_MAP) are not present + +- c. Each MDC code using a CWE data type is encoded as: +^^ + +where: + +- refIdValue: is a 32 bit integer (required) +- refIdName: is the normative nomenclature name for the unique code point (recommended) +- refIdCodeSystem = "MDC" (required). + +- d. A bit flag value is encoded as ^(), where: + +- = <0 or 1> +- is recommended to be the ASN.1 name for the bit +- is the normative position of the bit + +- e. Usage Sensor object follows this OBX encoding: + +- OBX-2 = 'CWE' +- OBX-3 = 8519691^MDC\_AI\_TYPE\_SENSOR\_USAGE^MDC +- OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Usage Sensor object respectively. +- OBX-5 = One of the following flags: +<0 or 1>^usage-started(0), +<0 or 1>^usage-ended(1), +<0 or 1>^expected-use-start-violation(2), +<0 or 1>^expected-use-stop-violation(3), +<0 or 1>^absence-violation(4) +Additionally, optionally, any of the general sensor health flags: +<0 or 1>^auto-presence-received(16), +<0 or 1>^auto-presence-failed(17), +<0 or 1>^low-battery(18), +<0 or 1>^fault(19), +<0 or 1>^end-of-life(20) + +- f. Usage Sensor Location attribute follows this OBX encoding: + +- OBX-2 = 'CWE' +- OBX-3 = 8520703^MDC\_AI\_LOCATION^MDC or 68193^MDC\_ATTR\_SUPPLEMENTAL\_TYPES^MDC +- OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Usage Sensor object. +- OBX-5 = Any of the 10471 location codes that are specified in the Supplemental-Types. + +For example: 8523328^MDC\_AI\_LOCATION\_LIVINGROOM^MDC + +- g. No PM-Store, PM-Segment or Scanner attributes are present. + +- h. One of these timestamp attributes can be present: + +- MDC\_ATTR\_TIME\_STAMP\_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ] +- MDC\_ATTR\_TIME\_STAMP\_REL, transmitted as a facet of the observation: + - OBX-5 = Numeric value + - OBX-18 has a timebase ID. +- MDC\_ATTR\_TIME\_STAMP\_HI\_RES, transmitted as a facet of the observation. + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = Numeric value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*216+3648 = 8523328.

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-012 | | | +| TP label | Switch Sensor Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | +| | | ActivityHub 4; M | ActivityHub 28; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Switch Sensor Object, the Metric and Enumeration attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_013 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a Switch Sensor object. | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. At least one Switch Sensor object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:

    • <bitValue> = <0 or 1>
    • <bitName> is recommended to be the ASN.1 name for the bit
    • <bitPosition> is the normative position of the bit

    e. Switch Sensor object follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8519692^MDC_AI_TYPE_SENSOR_SWITCH^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Switch Sensor object respectively.
    • OBX-5 = One of the following flags:
      <0 or 1>^switch-on(0),
      <0 or 1>^switch-off(1)
      Additionally, optionally, any of the general sensor health flags:
      <0 or 1>^auto-presence-received(16),
      <0 or 1>^auto-presence-failed(17),
      <0 or 1>^low-battery(18),
      <0 or 1>^fault(19),
      <0 or 1>^end-of-life(20)

    f. Switch Sensor Location attribute follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Switch Sensor object.
    • OBX-5 = Any of the 10471 location codes that are specified in the supplemental-types.
      For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | + +| | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*2^{16}+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)
    Number of the attribute is given in 10471

    For example:

    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130 \cdot 2^{16} + 3648 = 8523328.

    | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-013 | | | | +| TP label | Medication Dosage Sensor Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | ActivityHub 3; M | +| | | ActivityHub 4; M | ActivityHub 30; M | ActivityHub 31; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Medication Dosage Sensor Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_014 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a Medication Dosage Sensor object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Medication Dosage Sensor object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:

    • <bitValue> = <0 or 1>
    • <bitName> is recommended to be the ASN.1 name for the bit
    • <bitPosition> is the normative position of the bit

    e. Medication Dosage Sensor object follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8519693^MDC_AI_TYPE_SENSOR_DOSAGE^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Medication Dosage Sensor object respectively.
    • OBX-5 = One of the following flags:
      • <0 or 1>^dosage-taken(0),
      • <0 or 1>^dosage-missed(1)
      Additionally, optionally, any of the general sensor health flags:
      • <0 or 1>^auto-presence-received(16),
      • <0 or 1>^auto-presence-failed(17),
      • <0 or 1>^low-battery(18),
      • <0 or 1>^fault(19),
      • <0 or 1>^end-of-life(20)

    f. Medication Dosage Sensor Location attribute follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Medication Dosage Sensor object.
    • OBX-5 = Any of the 10471 location codes that are specified in the supplemental-types.
      For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*2^{16}+Number of the attribute

    where:

    | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Number of the partition code = 130 (MDC_PART_PHD_AI)
    Number of the attribute is given in 10471
    For example:
    MDC_AI_LOCATION_LIVINGROOM = 3648 → $130 \cdot 2^{16} + 3648 = 8523328$ . | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/HUB/BV-014 | | | +| TP label | Temperature Sensor Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ActivityHub 1; M | ActivityHub 2; M | +| | | ActivityHub 4; M | ActivityHub 32; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the Temperature Sensor Object, the Metric and Enumeration attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_HUB_001 AND C_SEN_HUB_015 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a HUB device with a Temperature Sensor object. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an independent living hub device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Temperature Sensor object has sent at least one observation. Each one conforms to the following steps.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:

    • ❑ <bitValue> = <0 or 1>
    • ❑ <bitName> is recommended to be the ASN.1 name for the bit
    • ❑ <bitPosition> is the normative position of the bit

    e. Temperature Sensor object follows this OBX encoding:

    • ❑ OBX-2 = 'CWE'
    • ❑ OBX-3 = 8519694^MDC_AI_TYPE_SENSOR_TEMP^MDC
    • ❑ OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Temperature Sensor object respectively.
    • ❑ OBX-5 = One of the following flags:
      <0 or 1>^high-temperature-detected(0),
      <0 or 1>^low-temperature-detected(1),
      <0 or 1>^rate-of-change-too-fast(2)
      Additionally, optionally, any of the general sensor health flags:
      <0 or 1>^auto-presence-received(16),
      <0 or 1>^auto-presence-failed(17),
      <0 or 1>^low-battery(18),
      <0 or 1>^fault(19),
      <0 or 1>^end-of-life(20)

    f. Temperature Sensor Location attribute follows this OBX encoding:

    • ❑ OBX-2 = 'CWE'
    • ❑ OBX-3 = 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC
    • ❑ OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the Temperature Sensor object.
    • ❑ OBX-5 = Any of the 10471 location codes that are specified in the supplemental-types.
      For example: 8523328^MDC_AI_LOCATION_LIVINGROOM^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • ❑ MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    To calculate the number situated before the MDC name of the location the following function is used:

    Number of the partition code*216+Number of the attribute

    where:

    Number of the partition code = 130 (MDC_PART_PHD_AI)

    Number of the attribute is given in 10471

    | + +| | | +|--|------------------------------------------------------------------------------------------| +| | For example:
    MDC_AI_LOCATION_LIVINGROOM = 3648 → 130*2 16 +3648 = 8523328. | +|--|------------------------------------------------------------------------------------------| + +## A.12 Subgroup 1.4.11: Adherence monitor (AM) + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/AM/BV-000 | | | | +| TP label | MDS Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | MDSCClassAttr 3; M | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | MDSCClassAttr 6; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | MDSCClassAttr 9; C | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | MDSCClassAttr 12; M | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | MDSCClassAttr 15; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | MDSCClassAttr 18; M | +| | | MDSObject 1; M | MDSObject 2; M | MDSObject 3; M | +| | | MDSObject 4; M | MDSObject 5; M | MDSObject 6; M | +| | | MDSObject 7; M | MDSObject 8; M | MDSObject 9; M | +| | | MDSObject 10; M | MDSObject 11; M | MDSObject 12; M | +| | | MDSObject 13; O | MDSObject 14; O | MDSObject 15; O | +| | | MDSObject 16; M | MDSObject 17; M | MDSObject 18; M | +| | | MDSObject 19; M | MDSObject 20; M | MDSObject 21; M | +| | | MDSObject 22; M | MDSObject 23; M | MDSObject 24; M | +| | | MDSObject 25; M | MDSObject 26; M | MDSObject 27; M | +| | | MDSObject 28; M | MDSObject 29; M | MDSObject 30; M | +| | | MDSObject 31; M | MDSObject 32; M | AdherenceMon 2; M | +| | | Timestamp 13; O | Timestamp 14; O | Timestamp 15; O | +| | | Timestamp 17; M | | | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | DeviceTimeSync1; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_AM_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of an adherence monitor device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an adherence monitor device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    | | | | + +- b. Each MDC code using a CWE data type is encoded as: +`^^` +where: +- refIdValue: is a 32 bit integer (required) + - refIdName: is the normative nomenclature name for the unique code point (recommended) + - refIdCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as `^()`, where: +- `` = <0 or 1> + - `` is recommended to be the ASN.1 name for the bit + - `` is the normative position of the bit +- d. In MDS-level OBX: +- OBX-2 is empty + - If the System-Type attribute is valued, OBX-3 = 528456^MDC\_DEV\_SPEC\_PROFILE\_AI\_MED\_MINDER^MDC + - If the System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = `^^^EUI-64`, where the System\_Id is 16 characters given by the PIXIT I\_SEN\_AM\_001. +- e. System model attribute is sent in two different OBX segments: +- System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of the MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of the MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: +- Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + +- OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + +- OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) +- Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) + - Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC + - Date and Time attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- Relative-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC +- Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If the Power-Status attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + +<0 or 1>^chargingFull(8), +<0 or 1>^chargingTrickle(9), +<0 or 1>^chargingOff(10) + +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + - OBX-5 = NM data type value + - OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC +- k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC + - OBX-5 = Use the value contained in the BatMeasure object + - OBX-6 = Use the OID contained in the BatMeasure object +- l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + - OBX-2 = 'CWE' + - OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC + - OBX-5 = One of: +0^auth-body-empty, +1^auth-body-ieee-11073, +2^auth-body-continua, +254^auth-body-experimental, +255^auth-body-reserved +- m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + - Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + - OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC + - OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment. + - OBX-5 = .. + - Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'NA' + - OBX-3 = 532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC + - OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment. + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 16456 (AM v1.5 Wireless PAN), 8264 (AM v1.5 Wired PAN), or 24648 (AM v1.5 Sensor LAN)

    Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'CWE'
    • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
    • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'CWE'
    • OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/AM/BV-001 | | | | | +| TP label | Fixed Dosage Dispensed Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | AdherenceMon 1; M | AdherenceMon 3; M | | | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | | | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | | | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | | | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | | | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | | | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | | | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Fixed Dosage Dispensed Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_AM_001 AND C_SEN_AM_002 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of an adherence monitor device with a Fixed Dosage Dispensed object. | | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an adherence monitor device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Fixed Dosage Dispensed object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Fixed Dosage Dispensed object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8532992^MDC_AI_MED_DISPENSED_FIXED^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Fixed Dosage Dispensed object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = Leave blank or 262656^MDC_DIM_DIMLESS^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------------|-------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/AM/BV-002 | | | | | | | | | | | | | | | | | | | | | | | +| TP label | Variable Dosage Dispensed Numeric Object | | | | | | | | | | | | | | | | | | | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | | | | | | | | | | | | | | | | | | | +| | Testable items |
    AdherenceMon 1; M AdherenceMon 4; M MetricClassAttr 1; M
    MetricClassAttr 2; M MetricClassAttr 3; O MetricClassAttr 4; M
    MetricClassAttr 5; M MetricClassAttr 6; O MetricClassAttr 7; O
    MetricClassAttr 8; O MetricClassAttr 9; M MetricClassAttr 10; O
    MetricClassAttr 11; M MetricClassAttr 12; O MetricClassAttr 13; O
    MetricClassAttr 14; O MetricClassAttr 15; C MetricClassAttr 16; C
    MetricClassAttr 17; C MetricClassAttr 18; O NumericClassAttr 1; M
    | | AdherenceMon 1; M | AdherenceMon 4; M | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| AdherenceMon 1; M | AdherenceMon 4; M | MetricClassAttr 1; M | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------|--|--|--| +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | | | | +| | Spec | [ITU-T H.812.1] | | | | | | +| | Testable items | DataGuidelines 22; M | | | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Variable Dosage Dispensed Object, the Metric and Numeric attributes and their respective values.

    | | | | | | | +| Applicability | C_SEN_000 AND C_SEN_AM_001 AND C_SEN_AM_003 | | | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of an adherence monitor device with a Variable Dosage Dispensed object.

    | | | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an adherence monitor device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Variable Dosage Dispensed object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Variable Dosage Dispensed object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8532993^MDC_AI_MED_DISPENSED_VARIABLE^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Variable Dosage Dispensed object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263762^MDC_DIM_MILLI_L^MDC or 263890^MDC_DIM_MILLI_G^MDC or 267616^MDC_DIM_INTL_UNIT^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
    | | | | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-5 = Numeric value
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/AM/BV-003 | | | | +| TP label | User Feedback Channel Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | AdherenceMon 1; M | AdherenceMon 5; M | AdherenceMon 6; M | +| | | AdherenceMon 7; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | NumArrayDataType 1; O | +| | | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | | +| | Test purpose | Check that:
    The presence of the attributes of the User Feedback Channel Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_AM_001 AND C_SEN_AM_004 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of an adherence monitor device with a User Feedback Channel object. | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of an adherence monitor device using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. The User Feedback Channel object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. User Feedback Channel object follows this OBX encoding:
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-2 = 'NA'
    • OBX-3 = 8532995^MDC_AI_MED_FEEDBACK^MDC
    • OBX-4 = y.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the channel level for the User Feedback Channel object respectively.
    • OBX-5 = Numeric array value
    • OBX-6 = Leave blank or 262656^MDC_DIM_DIMLESS^MDC
    • OBX-11 = 'X'

    e. User Feedback Location attribute follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8532996^MDC_AI_MED_UF_LOCATION^MDC
    • OBX-4 = y.0.x.a, where 'a' is a number indicating the metric level of the User Feedback Channel object
    • OBX-5 = Numeric value
    • OBX-6 = Leave blank or 262656^MDC_DIM_DIMLESS^MDC

    f. User Feedback Response attribute follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8532997^MDC_AI_MED_UF_RESPONSE^MDC
    • OBX-4 = y.0.x.b, where 'b' is a number indicating the metric level of the User Feedback Channel object
    • OBX-5 = Numeric value
    • OBX-6 = Leave blank or 262656^MDC_DIM_DIMLESS^MDC

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    In [b-CDG 2010], Step 2.d shows the expected OBX segment as specified in Appendix J, Table J-29 [b-CDG 2010]. Based on the similarity between the BPM and AM compound values, it is understood that the correct OBX segment should be:

    User Feedback Channel object follows this OBX encoding:

    • OBX-2 is empty
    • OBX-3 = 8532995^MDC_AI_MED_FEEDBACK^MDC
    • OBX-4 = y.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the channel level for the User Feedback Channel object respectively.
    • OBX-5 is empty
    • OBX-11 = 'X'

    NOTE – [b-CDG 2010] Table J-29 corresponds to Table VIII.29 in [ITU-T H.810 (2015)]; see Table 2.

    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/AM/BV-004 | | | +| TP label | Status Reporter Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | AdherenceMon 1; M | AdherenceMon 8; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | EnumClassAttr 1; M | EnumClassAttr 2; M | +| | | EnumClassAttr 4; M | EnumClassAttr 5; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose |

    Check that:

    The presence of the attributes of the Status Reporter Object, the Metric and Enumeration attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_AM_001 AND C_SEN_AM_005 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of an adherence monitor device with a Status Reporter object.

    | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of an adherence monitor device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Status Reporter object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Status Reporter object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8532994^MDC_AI_MED_STATUS^MDC
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Status Reporter object respectively.
    • OBX-5 = Any of the status flags:
      • <0 or 1>^medication-not-dispensed-as-expected(0)
      • <0 or 1>^medication-dispensed-unexpectedly(1)
      • <0 or 1>^medication-unfit(2)
      • <0 or 1>^medication-expiration(3)
      • <0 or 1>^medication-course-complete(4)
      • <0 or 1>^medication-taken-incorrectly(5)
      • <0 or 1>^medication-course-reloaded(6)
      • <0 or 1>^monitor-tamper(7)
      • <0 or 1>^monitor-environmental-exceeded-high(8)
      • <0 or 1>^monitor-environmental-exceeded-low(9)
      • <0 or 1>^monitor-inoperable(10)
      • <0 or 1>^consumer-non-compliant-yellow(11)
      • <0 or 1>^consumer-non-compliant-red(12)
    • f. If valued, Context Key attribute follows this OBX encoding:
      • OBX-2 = 'EI'
      • OBX-3 = 68216^MDC_ATTR_CONTEXT_KEY^MDC
      • OBX-4 = y.0.0.x.z, where 'z' is a number indicating the metric level of the Context Key attribute.
      • OBX-5 = <Entity Identifier (ST)>^EUI-64
    • g. No PM-Store, PM-Segment or Scanner attributes are present.
    • h. One of these timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes |

    In [b-CDG 2010], Step 2.e shows the expected OBX segment based on IEEE 11073-10472 Context-Key attribute specification. Appendix J, Table J-29 in [b-CDG 2010] shows this attribute as directly dependent of MDS Object and IEEE 11073-10472 shows this attribute as part of Status Reporter Object.

    NOTE – [b-CDG 2010] Table J-29 corresponds to Table VIII.29 in [ITU-T H.810 (2015)]; see Table 2.

    | + +## A.13 Subgroup 1.4.12: Peak expiratory flow monitor (PF) + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PF/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | +| | | MDSObject 1; M | MDSObject 2; M | +| | | MDSObject 4; M | MDSObject 5; M | +| | | MDSObject 7; M | MDSObject 8; M | +| | | MDSObject 10; M | MDSObject 11; M | +| | | MDSObject 13; O | MDSObject 14; O | +| | | MDSObject 16; M | MDSObject 17; M | +| | | MDSObject 19; M | MDSObject 20; M | +| | | MDSObject 22; M | MDSObject 23; M | +| | | MDSObject 25; M | MDSObject 26; M | +| | | MDSObject 28; M | MDSObject 29; M | +| | | MDSObject 31; M | MDSObject 32; M | +| | | Timestamp 13; O | Timestamp 14; O | +| | | Timestamp 17; M | Timestamp 15; O | +| | Spec | [IHE PCD TF 2] | | +| | Testable Items | DeviceTimeSync1; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable Items | DataGuidelines 9; M | DataGuidelines 21; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_PF_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a peak flow device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a peak flow device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        refIdValue: is a 32 bit integer (required)
    | | | + +- refIdName: is the normative nomenclature name for the unique code point (recommended) +- refIdCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: + - OBX-2 is empty + - If the System-Type attribute is valued, OBX-3 = 528405^MDC\_DEV\_SPEC\_PROFILE\_PEFM^MDC + - If the System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System Id is 16 characters given by the PIXIT I\_SEN\_PF\_001. +- e. System model attribute is sent in two different OBX segments: + - System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of the MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of the MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. + +g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) + +- ❑ Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) +- ❑ Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC +- Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If the Power-Status attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + +- OBX-5 = NM data type value +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC + +k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC +- OBX-5 = Use the value contained in the BatMeasure object +- OBX-6 = Use the OID contained in the BatMeasure object + +p. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + +- OBX-2 = 'CWE' +- OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC +- OBX-5 = One of: + - 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + - 254^auth-body-experimental, + - 255^auth-body-reserved + +q. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + +- Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + - OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC + - OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment. + - OBX-5 = .. +- Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'NA' + - OBX-3 = 532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC + - OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment. + - OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 16405 (PF v1.5 Wireless PAN), 8213 (PF v1.5 Wired PAN), or 24597 (PF v1.5 Sensor LAN) +- Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'CWE' + - OBX-3 = 532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
    • OBX-5 = <0 or 1>^unregulated-device(0)

    l. If the System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'CWE'
    • OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    m. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PF/BV-001 | | | +| TP label | PEF Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | PeakFlow 1; M | PeakFlow 3; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 7; O | MeasureStatus 1; M | +| | | MeasureStatus 3; M | MeasureStatus 4; R | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the PEF Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_PF_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a peak flow device. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a peak flow device using SOAP or hData observation upload.
    2. Check in the captured message that:
    a. The PEF object has sent at least one observation.
    b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • ❑ refIdValue: is a 32 bit integer (required)
    • ❑ refIdName: is the normative nomenclature name for the unique code point (recommended)
    • ❑ refIdCodeSystem = "MDC" (required).

    d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:

    • ❑ <bitValue> = <0 or 1>
    • ❑ <bitName> is recommended to be the ASN.1 name for the bit
    • ❑ <bitPosition> is the normative position of the bit

    e. PEF object follows this OBX encoding:

    • ❑ OBX-2 = 'NM'
    • OBX-3 = 152584^MDC_FLOW_AWAY_EXP_FORCED_PEAK^MDC
    • ❑ OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the PEF object respectively.
    • ❑ OBX-5 = Numeric Value
    • ❑ OBX-6 = 264992^MDC_DIM_L_PER_MIN^MDC
    • ❑ OBX-11 has one of the following values:
      • • 'X', in case of invalid, not-available or ongoing measurements (specified in the Measurement Status attribute)
      • • 'F', in case of validated-data Measurement Status bit is set
      • • 'R', in other case (even if Measurement status is not present)

    f. If valued, the PEF Measurement Status attribute follows this OBX encoding:

    • ❑ OBX-2 = 'CWE'
    • OBX-3 = 67911^MDC_ATTR_MSMT_STAT^MDC
    • ❑ OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the PEF object
    • ❑ OBX-5 = Any of the following flags:
      • <0 or 1>^msmt-stat-post-med(0) or
      • <0 or 1>^msmt-stat-cough(1) or
      • <0 or 1>^msmt-stat-short-effort(2) or
      • <0 or 1>^msmt-stat-long-time-to-peak(3)

    g. No PM-Store, PM-Segment or Scanner attributes are present.

    h. One of these timestamp attributes can be present:

    • ❑ MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | + +| | | +|-------|--| +| Notes | | +|-------|--| + +| | | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PF/BV-002 | | | | | +| TP label | Personal Best Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | PeakFlow 1; M | PeakFlow 5; M | | | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | | | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | | | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | | | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | | | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | | | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | | | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Personal Best Object, the Metric and Numeric attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_PF_001 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a peak flow device. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a peak flow device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Personal Best object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Personal Best object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 152585^MDC_FLOW_AWAY_EXP_FORCED_PEAK_PB^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Personal Best object respectively.
        • OBX-5 = Numeric Value
    | | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-6 = 264992^MDC_DIM_L_PER_MIN^MDC

    e. No PM-Store, PM-Segment or Scanner attributes are present.

    f. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PF/BV-003 | | | +| TP label | FEV1 Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | PeakFlow 1; M | PeakFlow 6; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 7; O | MeasureStatus 1; M | +| | | MeasureStatus 3; M | MeasureStatus 4; R | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the FEV1 Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_PF_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a peak flow device. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a peak flow device using SOAP or hData observation upload.
    2. Check in the captured message that:
    a. The FEV1 object has sent at least one observation. | | | + +- b. Handle attribute (MDC\_ATTR\_ID\_HANDLE), Metric-Spec-Small attribute (MDC\_ATTR\_METRIC\_SPEC\_SMALL) and Metric-Structure-Small (MDC\_ATTR\_METRIC\_STRUCT\_SMALL) attribute and Attribute-Value-Map (MDC\_ATTR\_ATTRIBUTE\_VALUE\_MAP) are not present +- c. Each MDC code using a CWE data type is encoded as: +`^^` + where: + - refIdValue: is a 32 bit integer (required) + - refIdName: is the normative nomenclature name for the unique code point (recommended) + - refIdCodeSystem = "MDC" (required). +- d. A bit flag value is encoded as `^()`, where: + - `` = `<0 or 1>` + - `` is recommended to be the ASN.1 name for the bit + - `` is the normative position of the bit +- e. FEV1 object follows this OBX encoding: + - OBX-2 = 'NM' + OBX-3 = 152586^MDC\_FLOW\_AWAY\_EXP\_FORCED\_PEAK\_1S^MDC + - OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the FEV1 object respectively. + - OBX-5 = Numeric Value + - OBX-6 = 263744^MDC\_DIM\_L ^MDC + - OBX-11 has one of the following values: + - 'X', in case of invalid, not-available or ongoing measurements (specified in Measurement Status attribute) + - 'F', in the case of validated-data Measurement Status bit is set + - 'R', in the other case (even if the Measurement Status is not present) +- f. If valued, FEV1 Measurement Status attribute follows this OBX encoding: + - OBX-2 = 'CWE' + OBX-3 = 67911^MDC\_ATTR\_MSMT\_STAT^MDC + - OBX-4 = y.0.0.x.a, where 'a' is a number indicating the facet level of the FEV1 object + - OBX-5 = Any of the following flags: +`<0 or 1>^msmt-stat-post-med(0)` or +`<0 or 1>^msmt-stat-cough(1)` or +`<0 or 1>^msmt-stat-short-effort(2)` or +`<0 or 1>^msmt-stat-long-time-to-peak(3)` +- g. No PM-Store, PM-Segment or Scanner attributes are present. +- h. One of these timestamp attributes can be present: + - MDC\_ATTR\_TIME\_STAMP\_ABS, mapped in OBX-14 of the observation metric-level and encoded as: `YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]` + - MDC\_ATTR\_TIME\_STAMP\_REL, transmitted as a facet of the observation: + - OBX-5 = Numeric value + - OBX-18 has a timebase ID. + - MDC\_ATTR\_TIME\_STAMP\_HI\_RES, transmitted as a facet of the observation. + - OBX-5 = Numeric value + +| | | +|---------------------------|-------------------------------------------------------------------------------| +| |
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/PF/BV-004 | | | | +| TP label | FEV6 Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | PeakFlow 1; M | PeakFlow 8; M | PeakFlow 9; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | NumericClassAttr 7; O | MeasureStatus 1; M | MeasureStatus 2; M | +| | | MeasureStatus 3; M | MeasureStatus 4; R | MeasureStatus 5; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the FEV6 Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_PF_001 AND C_SEN_PF_002 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a peak flow device with a FEV6 object. | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an observation of a peak flow device using SOAP or hData observation upload.
    2. Check in the captured message that:
      1. The FEV6 object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • ❑ refIdValue: is a 32 bit integer (required)
        • ❑ refIdName: is the normative nomenclature name for the unique code point (recommended)
        • ❑ refIdCodeSystem = "MDC" (required).
      4. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • <bitValue> = <0 or 1>
    • <bitName> is recommended to be the ASN.1 name for the bit
    • <bitPosition> is the normative position of the bit

    e. FEV6 object follows this OBX encoding:

    • OBX-2 = 'NM'
      OBX-3 = 152587^MDC_FLOW_AWAY_EXP_FORCED_PEAK_6S^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the FEV6 object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 263744^MDC_DIM_L ^MDC
    • OBX-11 has one of the following values:
      • • 'X', in the case of invalid, not-available or ongoing measurements (specified in Measurement Status attribute)
      • • 'F', in the case of validated-data Measurement Status bit is set
      • • 'R', in the other case (even if Measurement status is not present)

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. If valued, the FEV6 Measurement Status attribute follows this OBX encoding:

    • OBX-2 = 'CWE'
      OBX-3 = 67911^MDC_ATTR_MSMT_STAT^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the FEV6 object
    • OBX-5 = Any of the following flags:
      <0 or 1>^msmt-stat-post-med(0) or
      <0 or 1>^msmt-stat-cough(1) or
      <0 or 1>^msmt-stat-short-effort(2) or
      <0 or 1>^msmt-stat-long-time-to-peak(3)

    h. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +## A.14 Subgroup 1.4.13: Body composition analyser (BCA) + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BCA/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | +| | | MDSObject 1; M | MDSObject 2; M | +| | | MDSObject 4; M | MDSObject 5; M | +| | | MDSObject 7; M | MDSObject 8; M | +| | | MDSObject 10; M | MDSObject 11; M | +| | | MDSObject 13; O | MDSObject 14; O | +| | | MDSObject 16; M | MDSObject 17; M | +| | | MDSObject 19; M | MDSObject 20; M | +| | | MDSObject 22; M | MDSObject 23; M | +| | | MDSObject 25; M | MDSObject 26; M | +| | | MDSObject 28; M | MDSObject 29; M | +| | | MDSObject 31; M | MDSObject 32; M | +| | | Timestamp 13; O | Timestamp 14; O | +| | | Timestamp 17; M | Timestamp 15; O | +| | Spec | [IHE PCD TF 2] | | +| | Testable items | DeviceTimeSync1; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_BCA_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a body composition analyser device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a body composition analyser device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        refIdValue: is a 32 bit integer (required)
    | | | + +- refIdName: is the normative nomenclature name for the unique code point (recommended) +- refIdCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: + - OBX-2 is empty + - If the System-Type attribute is valued, OBX-3 = 528404^MDC\_DEV\_SPEC\_PROFILE\_BCA^MDC + - If the System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If the System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System\_Id is 16 characters given by the PIXIT I\_SEN\_BCA\_001. +- e. System model attribute is sent in two different OBX segments: + - System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of the MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of the MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + +- OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. + +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) +- Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11) + - Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC + - Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + +- OBX-14 = UTC value + - ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase + - ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase + - ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - ❑ Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC + - ❑ Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If the Power-Status attribute is valued, it is sent as an independent OBX segment: +- ❑ OBX-2 = 'ST' + - ❑ OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - ❑ OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC +- OBX-5 = NM data type value +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC + +k. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC +- OBX-5 = Use the value contained in the BatMeasure object +- OBX-6 = Use the OID contained in the BatMeasure object + +l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + +- OBX-2 = 'CWE' +- OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC +- OBX-5 = One of: + 0^auth-body-empty, + 1^auth-body-ieee-11073, + 2^auth-body-continua, + 254^auth-body-experimental, + 255^auth-body-reserved + +m. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + +- Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + +- OBX-2 = 'ST' +- OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC +- OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the facet level of that segment. +- OBX-5 = .. + +- Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + +- OBX-2 = 'NA' +- OBX-3 = 532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC +- OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment. +- OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 16404 (BCA v1.5 Wireless PAN), 8212 (BCA v1.5 Wired PAN), or 24596 (BCA v1.5 Sensor LAN) + +- Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding: + +- OBX-2 = 'CWE' + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
    • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment.
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If the System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • □ OBX-2 = 'CWE'
    • □ OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • □ OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BCA/BV-001 | | | | | +| TP label | Body Fat Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | BodyComp 1; M | BodyComp 3; M | | | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | | | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | | | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | | | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | | | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | | | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | | | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| Spec | [ITU-T H.812.1] | | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Body Fat Object, the Metric and Numeric attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_BCA_001 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a body composition analyser device. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a body composition analyser device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Body Fat object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) Metric-Structure-Small attribute
    | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Body Fat object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 188748^MDC_BODY_FAT^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Body Fat object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 262688^MDC_DIM_PERCENT^MDC or 263875^MDC_DIM_KILO_G^MDC or 263904^MDC_DIM_LB^MDC

    e. No PM-Store, PM-Segment or Scanner attributes are present.

    f. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|-----------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BCA/BV-002 | | | +| TP label | Body Height Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | BodyComp 1; M | BodyComp 4; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--| +| | Testable items | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Body Height Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_BCA_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a body composition analyser device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a body composition analyser device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Body Height object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute(MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • ❑ refIdValue: is a 32 bit integer (required)
        • ❑ refIdName: is the normative nomenclature name for the unique code point (recommended)
        • ❑ refIdCodeSystem = "MDC" (required).
      4. d. Body Height object follows this OBX encoding:
        • ❑ OBX-2 = 'NM'
        • ❑ OBX-3 = 188740^MDC_LEN_BODY_ACTUAL^MDC
        • ❑ OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Body Height object respectively.
        • ❑ OBX-5 = Numeric value
        • ❑ OBX-6 = 263441^MDC_DIM_CENTI_M^MDC or 263520^MDC_DIM_INCH^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
        • ❑ MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | | | +| Pass/Fail criteria | All elements in each segment are as specified. | | | +| Notes | | | | + +| | | +|-----------------|-----------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BCA/BV-003 | +| TP label | Body Weight Numeric Object | + +| | | | | | +|--------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | BodyComp 1; M | BodyComp 5; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | |

    Check that:

    The presence of the attributes of the Body Weight Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | | C_SEN_000 AND C_SEN_BCA_001 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a body composition analyser device. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a body composition analyser device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Body Weight object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Body Weight object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 188736^MDC_MASS_BODY_ACTUAL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Body Weight object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263875^MDC_DIM_KILO_G^MDC or 263904^MDC_DIM_LB^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BCA/BV-004 | | | +| TP label | Body Mass Index Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | BodyComp 1; M | BodyComp 6; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 7; O | MetricRelGroup 2; O | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| | | | | +| Test purpose | Check that:
    The presence of the attributes of the Body Mass Index Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_BCA_001 AND C_SEN_BCA_002 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a body composition analyser device with a Body Mass Index object. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a body composition analyser device using SOAP or hData observation upload.
    2. Check in the captured message that:
    1. a. The Body Mass Index object has sent at least one observation.
    2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    | | | + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +|

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Body Mass Index object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 188752^MDC_RATIO_MASS_BODY_LEN_SQ^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Body Mass Index object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 264096^MDC_DIM_KG_PER_M_SQ^MDC

    e. If the Body Mass Index Source-Handle-Reference attribute is present, it follows this OBX encoding:

    • OBX-2 = 'ST'
    • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
    • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Body Mass Index object.
    • OBX-5 = OBX-4 of the Body Weight object

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|-----------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BCA/BV-005 | | | | +| TP label | Fat Free Mass Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | BodyComp 1; M | BodyComp 8; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | + +| | | | | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------|--|--|--| +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | | | | +| | Spec | [ITU-T H.812.1] | | | | | | +| | Testable items | DataGuidelines 22; M | | | | | | +| Test purpose | Check that:
    The presence of the attributes of the Fat Free Mass Object, the Metric and Numeric attributes and their respective values. | | | | | | | +| Applicability | C_SEN_000 AND C_SEN_BCA_001 AND C_SEN_BCA_003 | | | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a body composition analyser device with a Fat Free Mass object. | | | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a body composition analyser device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Fat Free Mass object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Fat Free Mass object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 188756^MDC_MASS_BODY_FAT_FREE^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Fat Free Mass object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 263875^MDC_DIM_KILO_G^MDC or 263904^MDC_DIM_LB^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | | | | | | | +| Pass/Fail criteria | All elements in each segment are as specified. | | | | | | | + +| | | +|-------|--| +| Notes | | +|-------|--| + +| | | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BCA/BV-006 | | | | | +| TP label | Soft Lean Mass Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | BodyComp 1; M | BodyComp 9; M | | | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | | | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | | | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | | | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | | | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | | | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | | | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Soft Lean Mass Object, the Metric and Numeric attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_BCA_001 AND C_SEN_BCA_004 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a body composition analyser device with a Soft Lean Mass object.

    | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a body composition analyser device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Soft Lean Mass object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Soft Lean Mass object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 188760^MDC_MASS_BODY_SOFT_LEAN^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Soft Lean Mass object respectively.
        • OBX-5 = Numeric value
    | | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-6 = 263875^MDC_DIM_KILO_G^MDC or 263904^MDC_DIM_LB^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/BCA/BV-007 | | | | +| TP label | Body Water Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | BodyComp 1; M | BodyComp 10; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Body Water Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_BCA_001 AND C_SEN_BCA_005 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a body composition analyser device with a Body Water object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a body composition analyser device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. At least one Body Water object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: is the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Body Water object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 188764^MDC_BODY_WATER^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Body Water object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 263875^MDC_DIM_KILO_G^MDC or 263904^MDC_DIM_LB^MDC or 262688^MDC_DIM_PERCENT^MDC

    e. No PM-Store, PM-Segment or Scanner attributes are present.

    f. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +## A.15 Subgroup 1.4.14: Basic electrocardiograph (ECG) + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ECG/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | +| | | MDSObject 1; M | MDSObject 2; M | +| | | MDSObject 4; M | MDSObject 5; M | +| | | MDSObject 7; M | MDSObject 8; M | +| | | MDSObject 10; M | MDSObject 11; M | +| | | MDSObject 13; O | MDSObject 14; O | +| | | MDSObject 16; M | MDSObject 18; M | +| | | MDSObject 20; M | MDSObject 21; M | +| | | MDSObject 23; M | MDSObject 24; M | +| | | MDSObject 26; M | MDSObject 27; M | +| | | MDSObject 29; M | MDSObject 30; M | +| | | MDSObject 32; M | ElectroCardio 2; M | +| | | ElectroCardio 4; M | Timestamp 13; O | +| | | Timestamp 15; O | Timestamp 17; M | +| | Spec | [IHE PCD TF 2] | | +| | Testable items | DeviceTimeSync1; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 7; M | DataGuidelines 9; M | +| | | DataGuidelines 22; M | DataGuidelines 21; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_ECG_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a basic electrocardiograph device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a basic electrocardiograph device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        refIdValue: is a 32 bit integer (required)
    | | | + +- refIdName: is the normative nomenclature name for the unique code point (recommended) +- refIdCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: + - OBX-2 is empty + - If the System-Type attribute is valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC + - If the Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System Id is 16 characters given by the PIXIT I\_SEN\_ECG\_001 +- e. System-Type-Spec-List attribute shall follow this OBX encoding: + - OBX-2 = 'CWE' + - OBX-3 = 68186^MDC\_ATTR\_SYS\_TYPE\_SPEC\_LIST^MDC + - OBX-5 = 528390^MDC\_DEV\_SPEC\_PROFILE\_ECG^MDC and at least one of the following two profile values: +528524^MDC\_DEV\_SUB\_SPEC\_PROFILE\_ECG^MDC +528525^MDC\_DEV\_SUB\_SPEC\_PROFILE\_HR^MDC +- f. Tick-Resolution attribute, if present, shall follow this OBX encoding: + - OBX-2 = 'NM' + - OBX-3 = 68229^MDC\_ATTR\_TICK\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 265842^MDC\_DIM\_PER\_SEC^MDC +- g. System model attribute is sent in two different OBX segments: + - System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of the MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of the MDC\_ATTR\_ID\_MODEL attribute +- h. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + +- OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + +- Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'ST' +- OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC +- OBX-5 = String representing the value portion of the Production-Specification GMDN entry +- OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. + +i. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) + +- Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'CWE' +- OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC +- OBX-5 = One or more of: +<0 or 1>^mds-time-capab-real-time-clock(0), +<0 or 1>^mds-time-capab-set-clock(1), +<0 or 1>^mds-time-capab-relative-time(2), +<0 or 1>^mds-time-capab-high-res-relative-time(3), +<0 or 1>^mds-time-capab-sync-abs-time(4), +<0 or 1>^mds-time-capab-sync-rel-time(5), +<0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), +<0 or 1>^mds-time-state-abs-time-synced(8), +<0 or 1>^mds-time-state-rel-time-synced(9), +<0 or 1>^mds-time-state-hi-res-relative-time-synced(10), +<0 or 1>^mds-time-mgr-set-time(11) + +- Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC +- OBX-5 = NM data type value +- OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + +- Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'CWE' +- OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC +- OBX-5 = One of these values: +532224^MDC\_TIME\_SYNC\_NONE^MDC +532225^MDC\_TIME\_SYNC\_NTPV3^MDC +532226^MDC\_TIME\_SYNC\_NTPV4^MDC +532227^MDC\_TIME\_SYNC\_SNTPV4^MDC +532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC +532229^MDC\_TIME\_SYNC\_BTV1^MDC +532230^MDC\_TIME\_SYNC\_RADIO^MDC +532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC +532232^MDC\_TIME\_SYNC\_CDMA^MDC + +532233^MDC\_TIME\_SYNC\_GSM^MDC + +532234^MDC\_TIME\_SYNC\_EBWW^MDC + +532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC + +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Base-Offset-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 68225^MDC\_ATTR\_TIME\_BO^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = DTM data type value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = 0.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + +or + + - OBX-2 = 'NM' + - OBX-3 = 68226^MDC\_TIME\_RES\_BO^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + +- OBX-5 = NM data type value +- OBX-6 = 264320^MDC\_DIM\_SEC^MDC +- ❑ Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- j. Date-and-Time-Adjustment attribute is not present +- k. If the Power-Status attribute is valued, it is sent as an independent OBX segment: + - ❑ OBX-2 = 'ST' + - ❑ OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - ❑ OBX-5 = One or more of: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- l. If the Battery-Level attribute is valued, it is sent as an independent OBX segment: + - ❑ OBX-2 = 'NM' + - ❑ OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + - ❑ OBX-5 = NM data type value + - ❑ OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC +- m. If the Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + - ❑ OBX-2 = 'NM' + - ❑ OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC + - ❑ OBX-5 = Use the value contained in the BatMeasure object + - ❑ OBX-6 = Use the OID contained in the BatMeasure object +- n. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different facet-level entries and the following mandatory fields: + - ❑ OBX-2 = 'CWE' + - ❑ OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC + - OBX-5 = One of: + - 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + - 254^auth-body-experimental, + - 255^auth-body-reserved. +- o. Observations from Continua-compliant source devices are sent using three attributes as facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + - ❑ Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-3 = 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC
    • • OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments and 'a' is a number indicating the facet level of that segment
    • • OBX-5 = <major-IG-version>.<minor-IG-version>.

    ❑ Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'NA'
    • • OBX-3 = 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC
    • • OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a facet entry, and 'b' is a number indicating the facet level of that segment
    • • OBX-5 = NA value listing the certified devices. At least it shall contain one of these profiles: 8332 (ECG profile v1.5 Wired PAN), 8333 (HR profile v1.5 Wired PAN), 16524 (ECG profile v1.5 Wireless PAN), 16525 (HR profile v1.5 Wireless PAN), 24716 (ECG profile v1.5 Sensor LAN), or 24717 (HR profile v1.5 Sensor LAN), and the corresponding specialization for each one: 8204 (ECG v1.5 Wired PAN), 16396 (ECG v1.5 Wireless PAN) or 24588 (ECG v1.5 Sensor LAN).

    ❑ Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'CWE'
    • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
    • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a facet entry, and 'a' is a number indicating the facet level of that segment
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    p. Confirm-Timeout attribute is not present

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|-----------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ECG/BV-001 | | | +| TP label | Heart Rate Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ElectroCardio 1; M | ElectroCardio 5; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | | MetricClassAttr 1; M | +| | | | MetricClassAttr 4; M | +| | | | MetricClassAttr 7; O | +| | | | MetricClassAttr 10; O | +| | | | MetricClassAttr 13; O | +| | | | MetricClassAttr 16; C | +| | | | NumericClassAttr 1; M | +| | | | NumericClassAttr 4; M | +| | | | NumericClassAttr 7; O | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------|------------------| +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Heart Rate Object, the Metric and Numeric attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_ECG_001 AND C_SEN_ECG_002 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a basic electrocardiograph device with a Heart Rate object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a basic electrocardiograph device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Heart Rate object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: is the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Heart Rate object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 147842^MDC_ECG_HEART_RATE^MDC or 8410590^MDC_ECG_HEART_RATE_INSTANT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Heart Rate object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264864^MDC_DIM_BEAT_PER_MIN^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | | | | +| Pass/Fail criteria | All elements in each segment are as specified. | | | | +| Notes | | | | | + +| | | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ECG/BV-002 | | | | | +| TP label | R-R Interval Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | ElectroCardio 1; M | ElectroCardio 6; M | | | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | | | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | | | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | | | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | | | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | | | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | | | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the R-R Interval Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_ECG_001 AND C_SEN_ECG_003 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a basic electrocardiograph device with an R-R Interval object. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a basic electrocardiograph device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The R-R Interval object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. R-R Interval object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 147240^MDC_ECG_TIME_PD_RR_GL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the R-R Interval object respectively.
        • OBX-5 = Numeric value
    | | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-6 = 264338^MDC_DIM_MILLI_SEC^MDC or 268992^MDC_DIM_TICK^MDC
    • e. No PM-Store, PM-Segment or Scanner attributes are present.
    • f. One of these timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
        • • OBX-5 = Numeric value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ECG/BV-003 | | | | +| TP label | ECG Waveform RT-SA Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | ElectroCardio 1; M | ElectroCardio 7; M | ElectroCardio 8; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | NumericClassAttr 7; O | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the ECG Waveform Object, the Metric and RT-SA attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_ECG_001 AND C_SEN_ECG_004 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a basic electrocardiograph device with a ECG Waveform object. | | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an observation of a basic electrocardiograph device using SOAP or hData observation upload.
    2. Check in the captured message that:
    • a. At least one ECG Waveform object has sent at least one observation.
    | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute(MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present

    c. Each MDC code using a CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    where:

    • ❑ refIdValue: is a 32 bit integer (required)
    • ❑ refIdName: is the normative nomenclature name for the unique code point (recommended)
    • ❑ refIdCodeSystem = "MDC" (required).

    d. ECG Waveform object follows this OBX encoding:

    • ❑ OBX-2 = 'NA'
    • ❑ OBX-3 = 131328^MDC_ECG_ELEC_POTL^MDC or
      131329^MDC_ECG_ELEC_POTL_I^MDC or
      131330^MDC_ECG_ELEC_POTL_II^MDC or
      131389^MDC_ECG_ELEC_POTL_III^MDC or
      131390^MDC_ECG_ELEC_POTL_AVR^MDC or
      131391^MDC_ECG_ELEC_POTL_AVL^MDC or
      131392^MDC_ECG_ELEC_POTL_AVF^MDC or
      131331^MDC_ECG_ELEC_POTL_V1^MDC or
      131332^MDC_ECG_ELEC_POTL_V2^MDC or
      131333^MDC_ECG_ELEC_POTL_V3^MDC or
      131334^MDC_ECG_ELEC_POTL_V4^MDC or
      131335^MDC_ECG_ELEC_POTL_V5^MDC or
      131336^MDC_ECG_ELEC_POTL_V6^MDC
    • ❑ OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the ECG Waveform object respectively.
    • ❑ OBX-5 = Numeric array value (i.e., 11^22^33^44^55^66^77^88^99~...)
    • ❑ OBX-6 = 266418^MDC_DIM_MILLI_VOLT^MDC

    e. ECG waveform Sample-Period attribute of ECG waveform object shall be sent and shall follow this OBX encoding:

    • ❑ OBX-2 = 'NM'
    • ❑ OBX-3 = 67981^MDC_ATTR_TIME_PD_SAMP^MDC
    • ❑ OBX-5 = Numeric Value
    • ❑ OBX-6 = 264339^MDC_DIM_MICRO_SEC^MDC

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • ❑ MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ECG/BV-004 | | | +| TP label | Device Status Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ElectroCardio 1; M | ElectroCardio 9; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose |

    Check that:

    The presence of the attributes of the Device Status Object, the Metric and Enumeration attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_ECG_001 AND C_SEN_ECG_005 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a basic electrocardiograph device with a Device Status object.

    | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a basic electrocardiograph device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Device Status object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present.
      3. c. Each MDC code using a CWE data type is encoded as: <refldValue>^<refldName>^<refldCodeSystem>

        where:

        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Device Status object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8410584^MDC_ECG_DEV_STAT^MDC
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Device Status object respectively.
    • OBX-5 = One of the values:
      • <0 or 1>^leadwire-loss(0),
      • <0 or 1>^leadsignal-loss(1),
      • <0 or 1>^leadwire-loss-first-lead(2),
      • <0 or 1>^leadsignal-loss-first-lead(3),
      • <0 or 1>^leadwire-loss-second-lead(4),
      • <0 or 1>^leadsignal-loss-second-lead(5),
      • <0 or 1>^leadwire-loss-third-lead(6),
      • <0 or 1>^leadsignal-loss-third-lead(7)

    f. No PM-Store, PM-Segment or Scanner attributes are present.

    g. One of these timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
      • • OBX-5 = Numeric value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/ECG/BV-005 | | | +| TP label | Context Data Trigger Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | ElectroCardio 1; M | ElectroCardio 10; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Context Data Trigger Object, the Metric and Enumeration attributes and their respective values. | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_SEN_000 AND C_SEN_ECG_001 AND C_SEN_ECG_006 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a basic electrocardiograph device with a Context Data Trigger object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an observation of a basic electrocardiograph device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Context Data Trigger object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute(MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present.
      3. c. Each MDC code using a CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        where:
        • refldValue: is a 32 bit integer (required)
        • refldName: is the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Context Data Trigger object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8410585^MDC_ECG_EVT_CTXT_GEN^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Context Data Trigger object respectively.
        • OBX-5 = One of the values: 8410586^MDC_ECG_EVT_CTXT_USER^MDC or 8410587^MDC_ECG_EVT_CTXT_PERIODIC^MDC or 8410588^MDC_ECG_EVT_CTXT_DETECTED^MDC or 8410589^MDC_ECG_EVT_CTXT_EXTERNAL^MDC
      5. e. No PM-Store, PM-Segment or Scanner attributes are present.
      6. f. One of these timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of the observation metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a facet of the observation:
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a facet of the observation.
          • • OBX-5 = Numeric value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +## A.16 Subgroup 1.4.15: International normalized ratio (INR) + +| | | | | +|----------------------|----------------------------------------------------------------------------------------------|---------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/INR/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | +| | | MDSObject 1; M | MDSObject 2; M | +| | | MDSObject 4; M | MDSObject 5; M | +| | | MDSObject 7; M | MDSObject 8; M | +| | | MDSObject 10; M | MDSObject 11; M | +| | | MDSObject 13; O | MDSObject 14; O | +| | | MDSObject 16; M | MDSObject 17; M | +| | | MDSObject 19; M | MDSObject 20; M | +| | | MDSObject 22; M | MDSObject 23; M | +| | | MDSObject 25; M | MDSObject 26; M | +| | | MDSObject 28; M | MDSObject 29; M | +| | | MDSObject 31; M | MDSObject 32; M | +| | | INR 2; M | Timestamp 13; O | +| | | Timestamp 15; O | Timestamp 17; M | +| | Spec | [IHE PCD TF 2] | | +| | Testable items | DeviceTimeSync1; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_INR_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an International Normalized Ratio device. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a International Normalized Ratio device.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      3. c. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      4. d. In MDS-level OBX:
        • OBX-2 is empty
        • If System-Type attribute is valued, OBX-3 = 528406^MDC_DEV_SPEC_PROFILE_COAG^MDC
        • If System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3
        • If System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC and the specialization list is reported as an attribute of the device.
        • If Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD
        • OBX-11 = 'X'
        • OBX-18 (System Id attribute) = <Entity Identifier (ST)>^^<System_Id>^EUI-64, where the System_Id is 16 characters given by the PIXIT I_SEN_INR_001.
      5. e. System model attribute is sent in two different OBX segments:
        • System-Model attribute:
          • • OBX-2 = 'ST'
          • • OBX-3 = 531969^MDC_ID_MODEL_NUMBER^MDC
          • • OBX-5 = String representing the model number portion of MDC_ATTR_ID_MODEL attribute
        • System-Manufacturer attribute:
          • • OBX-2 = 'ST'
          • • OBX-3 = 531970^MDC_ID_MODEL_MANUFACTURER^MDC
          • • OBX-5 = String representing the model manufacturer portion of MDC_ATTR_ID_MODEL attribute.
      6. f. Production-Specification attribute is sent as a series of attributes:
        • Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment:
          • • OBX-2 = 'ST'
          • • OBX-3 = 531971^MDC_ID_PROD_SPEC_UNSPECIFIED^MDC
    | + +- OBX-5 = String representing the value portion of the Production-Specification entry +- OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + +- OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent a Timestamp, its respective resolution may be sent, but not other than this.) +- ❑ Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of these values: + <0 or 1>^mds-time-capab-real-time-clock(0), + <0 or 1>^mds-time-capab-set-clock(1), + <0 or 1>^mds-time-capab-relative-time(2), + <0 or 1>^mds-time-capab-high-res-relative-time(3), + <0 or 1>^mds-time-capab-sync-abs-time(4), + <0 or 1>^mds-time-capab-sync-rel-time(5), + <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + <0 or 1>^mds-time-capab-bo-time (7), + <0 or 1>^mds-time-state-abs-time-synced(8), + <0 or 1>^mds-time-state-rel-time-synced(9), + <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + <0 or 1>^mds-time-mgr-set-time(11), + <0 or 1>^mds-time-capab-sync-bo-time(12), + <0 or 1>^mds-time-state-bo-time-synced(13), + <0 or 1>^mds-time-state-bo-time-UTC-aligned(14), + <0 or 1>^mds-time-dst-rules-enabled(15) +- ❑ Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + 532224^MDC\_TIME\_SYNC\_NONE^MDC + 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + +532226^MDC\_TIME\_SYNC\_NTPV4^MDC + 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + 532229^MDC\_TIME\_SYNC\_BTV1^MDC + 532230^MDC\_TIME\_SYNC\_RADIO^MDC + 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + 532232^MDC\_TIME\_SYNC\_CDMA^MDC + 532233^MDC\_TIME\_SYNC\_GSM^MDC + 532234^MDC\_TIME\_SYNC\_EBWW^MDC + 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC + +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Base-Offset-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 68225^MDC\_ATTR\_TIME\_BO^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = DTM data type value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + +or + + - OBX-2 = 'NM' + +- OBX-3 = 68226^MDC\_TIME\_RES\_BO^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC +- ❑ If valued, Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If Power-Status attribute is valued, it is sent as an independent OBX segment: +- ❑ OBX-2 = 'ST' + - ❑ OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - ❑ OBX-5 = One or more of these values: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If Battery-Level attribute is valued, it is sent as an independent OBX segment: +- ❑ OBX-2 = 'NM' + - ❑ OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + - ❑ OBX-5 = NM data type value + - ❑ OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC +- k. If Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: +- ❑ OBX-2 = 'NM' + - ❑ OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC + - ❑ OBX-5 = Use the value contained in the BatMeasure object + - ❑ OBX-6 = Use the OID contained in the BatMeasure object +- l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different Facet-level entries and the following mandatory fields: +- ❑ OBX-2 = 'CWE' + - ❑ OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC + - OBX-5 = One of these values: + - 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    254^auth-body-experimental,
    255^auth-body-reserved

    m. Observations from Continua-compliant source devices are sent using three attributes as Facet-level entries of the Regulation-Certification-Auth-Body OBX segments:

    • Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding:
      • • OBX-2 = 'ST'
      • • OBX-3 = 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC
      • • OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the Facet level of that segment.
      • • OBX-5 = <major-IG-version>.<minor-IG-version>.
    • Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding:
      • • OBX-2 = 'NA'
      • • OBX-3 = 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC
      • • OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'b' is a number indicating the Facet level of that segment.
      • • OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 16404 (BCA v1.5 Wireless PAN), 8212 (BCA v1.5 Wired PAN), or 24596 (BCA v1.5 Sensor LAN)
    • Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding:
      • • OBX-2 = 'CWE'
      • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
      • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'a' is a number indicating the Facet level of that segment.
      • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'CWE'
    • OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/INR/BV-001 | | | +| TP label | INR Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | INR 1; M | INR 3; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the INR Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_INR_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an International Normalized Ratio device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an International Normalized Ratio device.
    2. 2. Check in the captured message that:
      1. a. The INR Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. INR Numeric object follows this OBX encoding:
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-2 = 'NM'
    • OBX-3 = 160260^MDC_RATIO_INR_COAG^MDC or 160264^MDC_TIME_PD_COAG^MDC or 160268^MDC_QUICK_VALUE_COAG^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the INR Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 268752^MDC_DIM_INR^MDC or 264320^MDC_DIM_SEC^MDC or 262688^MDC_DIM_PERCENT^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|-----------------|-----------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/INR/BV-002 | | | +| TP label | Control Solution Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | INR 1; M | INR 4; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--| +| | Testable items | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Control Solution Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_INR_001 AND C_SEN_INR_002 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an International Normalized Ratio device with a Control Solution Numeric Object | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an International Normalized Ratio device.
    2. 2. Check in the captured message that:
      1. a. The Control Solution Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Control Solution Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 160276^MDC_CONC_INR_CONTROL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Control Solution Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 268752^MDC_DIM_INR^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | | | | +| Pass/Fail criteria | All elements in each segment are as specified | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/INR/BV-003 | | | | +| TP label | ISI Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | INR 1; M | INR 5; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the ISI Numeric Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_INR_001 AND C_SEN_INR_003 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an International Normalized Ratio device with an ISI Numeric Object | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an International Normalized Ratio device.
    2. 2. Check in the captured message that:
      1. a. The ISI Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • ❑ refIdValue: is a 32 bit integer (required)
        • ❑ refIdName: the normative nomenclature name for the unique code point (recommended)
    | | | | + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +|
    • refIdCodeSystem = "MDC" (required).
    • d. ISI Numeric object follows this OBX encoding:
      • OBX-2 = 'NM'
      • OBX-3 = 160272^MDC_COAG^MDC
      • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the ISI Numeric object respectively.
      • OBX-5 = Numeric value
      • OBX-6 = 262656^MDC_DIM_DIMLESS^MDC
    • e. Any PM-Store, PM-Segment or Scanner attributes are not present.
    • f. One of the timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
    | | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|----------|----------|----------|----------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|---------------------|-----------------|-------------------|------------------|------------------|------------------|------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/INR/BV-004 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TP label | Context Tester Enumeration Object | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Testable items |
    ISI 1; M ISI 6; M ISI 7; M
    ISI 8; M MetricClassAttr 1; M MetricClassAttr 2; M
    MetricClassAttr 3; O MetricClassAttr 4; M MetricClassAttr 5; M
    MetricClassAttr 6; O MetricClassAttr 7; O MetricClassAttr 8; O
    MetricClassAttr 9; M MetricClassAttr 10; O MetricClassAttr 11; M
    MetricClassAttr 12; O MetricClassAttr 13; O MetricClassAttr 14; O
    MetricClassAttr 15; C MetricClassAttr 16; C MetricClassAttr 17; C
    MetricClassAttr 18; O EnumClassAttr 1; M EnumClassAttr 2; M
    EnumClassAttr 3; M EnumClassAttr 4; M EnumClassAttr 5; O
    EnumClassAttr 6; M MetricRelGroup 2; O PM-StoreAttr; M
    PM-SegmentAttr; M ScannerAttr 1; M ScannerAttr 2; M
    ScannerAttr 3; M ScannerAttr 4; M
    | | ISI 1; M | ISI 6; M | ISI 7; M | ISI 8; M | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | EnumClassAttr 5; O | EnumClassAttr 6; M | MetricRelGroup 2; O | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| ISI 1; M | ISI 6; M | ISI 7; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISI 8; M | MetricClassAttr 1; M | MetricClassAttr 2; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 18; O | EnumClassAttr 1; M | EnumClassAttr 2; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EnumClassAttr 3; M | EnumClassAttr 4; M | EnumClassAttr 5; O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EnumClassAttr 6; M | MetricRelGroup 2; O | PM-StoreAttr; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ScannerAttr 3; M | ScannerAttr 4; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--|--| +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Context Tester Object, the Metric and Enumeration attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_INR_001 AND C_SEN_INR_005 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an International Normalized Ratio device with a Context Tester object.

    | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an International Normalized Ratio device.
    2. 2. Check in the captured message that:
      1. a. The Context Tester object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Context Tester object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8417924^MDC_CTXT_INR_TESTER^MDC is the generic code; or, if specific Metric-Id is specified, use one of the following:
          8417925^MDC_CTXT_INR_TESTER_SELF^MDC or
          8417926^MDC_CTXT_INR_TESTER_HCP^MDC or
          8417927^MDC_CTXT_INR_TESTER_LAB^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Context Tester object respectively.
        • OBX-5 is empty
      5. e. If Context Tester Source-Handle-Reference attribute is present, it follows this OBX encoding:
        • OBX-2 = 'ST'
        • OBX-3 = 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC
        • OBX-4 = y.0.0.x.a, where 'a' is a number indicating the Facet level of the Context Tester object.
        • OBX-5 = OBX-4 of the INR object
      6. f. Any PM-Store, PM-Segment or Scanner attributes are not present.
      7. g. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
    | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-5 = Numeric Value
    • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
    • • OBX-5 = Numeric Value
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +## A.17 Subgroup 1.4.16: Sleeping apnoea breathing therapy equipment (SABTE) + +| | | | | +|-----------------|-------------------------------------|---------------------|---------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | MDSCClassAttr 1; M | MDSCClassAttr 2; C | +| | | MDSCClassAttr 4; M | MDSCClassAttr 5; M | +| | | MDSCClassAttr 7; O | MDSCClassAttr 8; M | +| | | MDSCClassAttr 10; C | MDSCClassAttr 11; C | +| | | MDSCClassAttr 13; M | MDSCClassAttr 14; M | +| | | MDSCClassAttr 16; M | MDSCClassAttr 17; C | +| | | MDSObject 1; M | MDSObject 2; M | +| | | MDSObject 4; M | MDSObject 5; M | +| | | MDSObject 7; M | MDSObject 8; M | +| | | MDSObject 10; M | MDSObject 11; M | +| | | MDSObject 13; O | MDSObject 14; O | +| | | MDSObject 16; M | MDSObject 17; M | +| | | MDSObject 19; M | MDSObject 20; M | +| | | MDSObject 22; M | MDSObject 23; M | +| | | MDSObject 25; M | MDSObject 26; M | +| | | MDSObject 28; M | MDSObject 29; M | +| | | MDSObject 31; M | MDSObject 32; M | +| | | SABTE 2; M | Timestamp 13; O | +| | | Timestamp 15; O | Timestamp 17; M | +| | Spec | [IHE PCD TF 2] | | +| | Testable items | DeviceTimeSync1; M | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|----------------------| +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of Sleeping Apnoea Breathing Therapy Equipment device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Sleeping Apnoea Breathing Therapy Equipment device.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      2. b. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      3. c. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      4. d. In MDS-level OBX:
        • OBX-2 is empty
        • If System-Type attribute is valued, OBX-3 = 528409^MDC_DEV_SPEC_PROFILE_SABTE^MDC
        • If System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3
        • If System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC and the specialization list is reported as an attribute of the device.
        • If Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD
        • OBX-11 = 'X'
        • OBX-18 (System Id attribute) = <Entity Identifier (ST)>^^<System_Id>^EUI-64, where the System_Id is 16 characters given by the PIXIT I_SEN_SABTE_001.
      5. e. System model attribute is sent in two different OBX segments:
        • System-Model attribute:
          • • OBX-2 = 'ST'
          • • OBX-3 = 531969^MDC_ID_MODEL_NUMBER^MDC
          • • OBX-5 = String representing the model number portion of MDC_ATTR_ID_MODEL attribute
    | | | | + +- System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + +- OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent a Timestamp, its respective resolution may be sent, but not other than this.) +- ❑ Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + - OBX-5 = One or more of these values: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-capab-bo-time (7), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11), + - <0 or 1>^mds-time-capab-sync-bo-time(12), + - <0 or 1>^mds-time-state-bo-time-synced(13), + - <0 or 1>^mds-time-state-bo-time-UTC-aligned(14), + - <0 or 1>^mds-time-dst-rules-enabled(15) +- ❑ Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: +- OBX-2 = 'NM' + +- OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC +- OBX-5 = NM data type value +- OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Base-Offset-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 68225^MDC\_ATTR\_TIME\_BO^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = DTM data type value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + +- OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase + - ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + or + - OBX-2 = 'NM' + - OBX-3 = 68226^MDC\_TIME\_RES\_BO^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - ❑ Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC + - ❑ If valued, Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- h. Date-and-Time-Adjustment attribute is not present +- i. If Power-Status attribute is valued, it is sent as an independent OBX segment: +- ❑ OBX-2 = 'ST' + - ❑ OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - ❑ OBX-5 = One or more of these values: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If Battery-Level attribute is valued, it is sent as an independent OBX segment: +- ❑ OBX-2 = 'NM' + - ❑ OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + - ❑ OBX-5 = NM data type value + - ❑ OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC +- k. If Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: +- ❑ OBX-2 = 'NM' + - ❑ OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC + +- OBX-5 = Use the value contained in the BatMeasure object + - OBX-6 = Use the OID contained in the BatMeasure object +- l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different Facet-level entries and the following mandatory fields: +- OBX-2 = 'CWE' + - OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC +- OBX-5 = One of these values: +- 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + - 254^auth-body-experimental, + - 255^auth-body-reserved +- m. Observations from Continua-compliant source devices are sent using three attributes as Facet-level entries of the Regulation-Certification-Auth-Body OBX segments: +- Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + - OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC + - OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the Facet level of that segment. + - OBX-5 = .. + - Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'NA' + - OBX-3 = 532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC + - OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'b' is a number indicating the Facet level of that segment. + - OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 16404 (BCA v1.5 Wireless PAN), 8212 (BCA v1.5 Wired PAN), or 24596 (BCA v1.5 Sensor LAN) + - Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'CWE' + - OBX-3 = 532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC + - OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'a' is a number indicating the Facet level of that segment. + - OBX-5 = <0 or 1>^unregulated-device(0) +- n. If System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment: +- OBX-2 = 'CWE' + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • OBX-5 = one or more MDC_DEV_SPEC_PROFILE values
    • o. Confirm-Timeout attribute is not present.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-001 | | | +| TP label | PHD DM Device status Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 2; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:
    The presence of the attributes of the PHD DM Device status Object, the Metric and Enumeration attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_002 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device with a PHD DM Device status object. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. Check in the captured message that:
    • a. The PHD DM Device status object has sent at least one observation.
    • b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small
    | | | + +(MDC\_ATTR\_METRIC\_STRUCT\_SMALL) attribute and Attribute-Value-Map (MDC\_ATTR\_ATTRIBUTE\_VALUE\_MAP) are not present + +- c. Each MDC code using CWE data type is encoded as: +^^ + +Where: + +- refIdValue: is a 32 bit integer (required) +- refIdName: the normative nomenclature name for the unique code point (recommended) +- refIdCodeSystem = "MDC" (required). + +- d. A bit flag value is encoded as ^(), where: + +- = <0 or 1> +- is recommended to be the ASN.1 name for the bit +- is the normative position of the bit + +- e. PHD DM Device status object follows this OBX encoding: + +- OBX-2 = 'CWE' +OBX-3 = 8408608^MDC\_PHD\_DM\_DEV\_STAT^MDC +- OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Device and PHD DM Device status object respectively. +- OBX-5 = Any of these values: +<0 or 1>^device-status-undetermined(0), +<0 or 1>^device-status-reset(1), +<0 or 1>^device-status-error(5), +<0 or 1>^device-status-error-mechanical(6), +<0 or 1>^device-status-error-electronic(7), +<0 or 1>^device-status-error-software(8), +<0 or 1>^device-status-error-battery(9), +<0 or 1>^device-status-service(15), +<0 or 1>^device-status-service-time-sync-required(16), +<0 or 1>^device-status-service-calibration-required(17), +<0 or 1>^device-status-service-replenishment-required(18), +<0 or 1>^device-status-battery-low(25), +<0 or 1>^device-status-battery-depleted(26), +<0 or 1>^device-status-battery-replaced(27), +<0 or 1>^device-status-battery-interrupted(28) + +- f. Any PM-Store, PM-Segment or Scanner attributes are not present. + +- h. One of the timestamp attributes can be present: + +- MDC\_ATTR\_TIME\_STAMP\_ABS or MDC\_ATTR\_TIME\_STAMP\_BO, mapped in OBX-14 of Observation Metric-level and encoded as: +YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ] +- MDC\_ATTR\_TIME\_STAMP\_REL, transmitted as a Facet of the observation: + - OBX-5 = Numeric Value + - OBX-18 has a timebase ID. +- MDC\_ATTR\_TIME\_STAMP\_HI\_RES, transmitted as a Facet of the observation. + - OBX-5 = Numeric Value + - OBX-18 has a timebase ID. + +| | | +|---------------------------|-----------------------------------------------| +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-002 | | | | | +| TP label | Duration of flow generation Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | SABTE 1; M | SABTE 4; M | | | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | | | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | | | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | | | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | | | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | | | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | | | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:

    The presence of the attributes of the Duration of flow generation Numeric Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Duration of flow generation Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        refldValue: is a 32 bit integer (required)
    | | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • reIdName: the normative nomenclature name for the unique code point (recommended)
    • reIdCodeSystem = "MDC" (required).

    d. Duration of flow generation Numeric object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8410708^MDC_SABTE_TIME_PD_FLOW_GEN_TOTAL^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Duration of flow generation Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 264352^MDC_DIM_MIN^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|-----------------|----------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-003 | | | +| TP label | Duration of patient use Numeric Object | | | +| Coverage | [ITU-T H.812.1] | | | +| | Spec | | | +| | Testable items | SABTE 1; M | SABTE 5; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | + +| | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--|--| +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Duration of patient use Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device. | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Duration of patient use Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Duration of patient use Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410712^MDC_SABTE_TIME_PD_USAGE_TOTAL^MDC or 8410716^MDC_SABTE_TIME_PD_USAGE_W_HUM^MDC or 8410720^MDC_SABTE_TIME_PD_USAGE_WO_HUM^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Duration of patient use Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264352^MDC_DIM_MIN^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | | | | | + +| | | +|---------------------------|-----------------------------------------------| +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-004 | | | | | +| TP label | Snoring duration Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | SABTE 1; M | SABTE 6; M | | | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | | | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | | | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | | | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | | | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | | | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | | | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:

    The presence of the attributes of the Snoring duration Numeric Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_003 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Snoring duration Numeric Object | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Snoring duration Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>

        Where:
    | | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • reflowValue: is a 32 bit integer (required)
    • reflowName: the normative nomenclature name for the unique code point (recommended)
    • reflowCodeSystem = "MDC" (required).

    d. Snoring duration Numeric object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8410724^MDC_SABTE_TIME_PD_SNORING_TOTAL^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Snoring duration Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 264352^MDC_DIM_MIN^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|-----------------|---------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-005 | | | +| TP label | Cheyne-Stokes respiration (CSR) duration Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 7; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | | MetricClassAttr 1; M | +| | | | MetricClassAttr 4; M | +| | | | MetricClassAttr 7; O | +| | | | MetricClassAttr 10; O | +| | | | MetricClassAttr 13; O | +| | | | MetricClassAttr 16; C | +| | | | NumericClassAttr 1; M | +| | | | NumericClassAttr 4; M | +| | | | NumericClassAttr 7; O | +| | | | ScannerAttr 1; M | + +| | | | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|------------------|--|--| +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | | | +| Spec | [ITU-T H.812.1] | | | | | | +| Testable items | DataGuidelines 22; M | | | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Cheyne-Stokes respiration (CSR) duration Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_004 | | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Cheyne-Stokes respiration (CSR) duration Numeric Object

    | | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Cheyne-Stokes respiration (CSR) duration Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Cheyne-Stokes respiration (CSR) duration Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410728^MDC_SABTE_TIME_PD_CSR_TOTAL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Cheyne-Stokes respiration (CSR) duration Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264352^MDC_DIM_MIN^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
    | | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = Numeric Value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-006 | | | +| TP label | Ramp duration setting Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 8; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Ramp duration setting Numeric Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_005 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Ramp duration setting Numeric Object | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. Check in the captured message that:
    • The Ramp duration setting Numeric object has sent at least one observation.
    • Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. Each MDC code using CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    Where:

    • ❑ refIdValue: is a 32 bit integer (required)
    • ❑ refIdName: the normative nomenclature name for the unique code point (recommended)
    • ❑ refIdCodeSystem = "MDC" (required).

    d. Ramp duration setting Numeric object follows this OBX encoding:

    • ❑ OBX-2 = 'NM'
    • ❑ OBX-3 = 8410744^MDC_SABTE_TIME_PD_RAMP_SET^MDC
    • ❑ OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Ramp duration setting Numeric object respectively.
    • ❑ OBX-5 = Numeric value
    • ❑ OBX-6 = 264352^MDC_DIM_MIN^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • ❑ MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|-----------------|-----------------------|-------------------------------------|-----------------------|-----------------------| +| TP Id | | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-007 | | | +| TP label | | Airflow waveform RT-SA Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 9; M | SABTE 10; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | + +| | | | | | +|--------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | NumericClassAttr 7; O | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | | Check that:
    The presence of the attributes of the Airflow waveform Object, the Metric and RT-SA attributes and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_006 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device with an Airflow waveform object. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Airflow waveform object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute(MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Airflow waveform object follows this OBX encoding:
        • OBX-2 = 'NA'
        • OBX-3 = 8410748^MDC_SABTE_FLOW_TOTAL^MDC or 8410752^MDC_SABTE_FLOW_WO_PURGE^MDC or 8410756^MDC_SABTE_FLOW_RESP^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Airflow waveform object respectively.
        • OBX-5 = Numeric Array value (i.e. 11^22^33^44^55^66^77^88^99~...)
        • OBX-6 = 264992^MDC_DIM_L_PER_MIN^MDC
      5. e. Airflow waveform Sample-Period attribute of Airflow waveform object shall be sent and shall follow this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 67981^MDC_ATTR_TIME_PD_SAMP^MDC
        • OBX-5 = Numeric Value
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-6 = 264320^MDC_DIM_SEC^MDC or 264339^MDC_DIM_MICRO_SEC^MDC
    • f. Any PM-Store, PM-Segment or Scanner attributes are not present.
    • g. One of the timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|---------------------|------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-008 | | | | +| TP label | Apnoea-Hypopnoea-Index (AHI) Compound Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 11; M | SABTE 12; M | +| | | SABTE 13; M | SABTE 14; M | | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | NumericClassAttr 7; O | MetricRelGroup 1; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that: | | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The presence of the attributes of the Apnoea-Hypopnoea-Index (AHI) Compound Object, the Metric and Numeric attributes and their respective values. | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_007 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device with a Apnoea-Hypopnoea-Index (AHI) Compound Object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device
    2. 2. Check in the captured message that:
      1. a. The Apnoea-Hypopnoea-Index (AHI) Compound object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Apnoea-Hypopnoea-Index (AHI) Compound object follows this OBX encoding:
        • OBX-2 is empty
        • OBX-3 = 8410788^MDC_SABTE_AHI^MDC
        • OBX-4 = y.0.x., where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the Channel-level for the uAHI, oAHI, cAHI object respectively.
        • OBX-5 is empty
        • OBX-11 = 'X'
      5. e. uAHI part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410796^MDC_SABTE_AHI_UNCLASS^MDC
        • OBX-4 = y.0.x.a., where 'a' is a number indicating the component of the compound object
        • OBX-5 = Numeric Value
        • OBX-6 = 266876^MDC_DIM_EVT_PER_HR^MDC
      6. f. oAHI part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410800^MDC_SABTE_AHI_OBSTRUC^MDC
        • OBX-4 = y.0.x.b, where 'b' is a number indicating the component of the compound object
        • OBX-5 = Numeric Value
        • OBX-6 = 266876^MDC_DIM_EVT_PER_HR^MDC
      7. g. cAHI part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410804^MDC_SABTE_AHI_CENT^MDC
    | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.x.c, , where 'c' is a number indicating the component of the compound object
    • OBX-5 = Numeric Value
    • OBX-6 = 266876^MDC_DIM_EVT_PER_HR^MDC

    h. Any PM-Store, PM-Segment or Scanner attributes are not present.

    h. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-009 | | | | +| TP label | Apnoea-Hypopnoea-Index (AHI) Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 15; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:

    The presence of the attributes of the Apnoea-Hypopnoea-Index (AHI) Numeric Object, the Metric and Numeric attributes and their respective values. | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_008 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Apnoea-Hypopnoea-Index (AHI) Numeric Object | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Apnoea-Hypopnoea-Index (AHI) Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Apnoea-Hypopnoea-Index (AHI) Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410792^MDC_SABTE_AHI_TOTAL^MDC or 8410796^MDC_SABTE_AHI_UNCLASS^MDC or 8410800^MDC_SABTE_AHI_OBSTRUC^MDC or 8410804^MDC_SABTE_AHI_CENT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Apnoea-Hypopnoea-Index (AHI) Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 266876^MDC_DIM_EVT_PER_HR^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-010 | | | +| TP label | Humidifier level setting Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 16; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Humidifier level setting Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_009 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Humidifier level setting Numeric Object | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Humidifier level setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. Humidifier level setting Numeric object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8410828^MDC_SABTE_LVL_HUMID_STAGE_SET^MDC or 8410832^MDC_SABTE_LVL_HUMID_TEMP_SET^MDC or 8410836^MDC_SABTE_LVL_HUMID_HUM_SET^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Humidifier level setting Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 262688^MDC_DIM_PERCENT^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|-----------------|--------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-011 | | | +| TP label | Trigger sensitivity setting Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 17; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--| +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Trigger sensitivity setting Numeric Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_010 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Trigger sensitivity setting Numeric Object | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Trigger sensitivity setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>

        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Trigger sensitivity setting Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410840^MDC_SABTE_LVL_TRIG_SENS_SET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Trigger sensitivity setting Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 262688^MDC_DIM_PERCENT^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | | | | +| Pass/Fail criteria | All elements in each segment are as specified | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-012 | | | | +| TP label | Inspiration pressure rise setting Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 18; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Inspiration pressure rise setting Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_011 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with an Inspiration pressure rise setting Numeric Object | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Inspiration pressure rise setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • ❑ refIdValue: is a 32 bit integer (required)
        • ❑ refIdName: the normative nomenclature name for the unique code point (recommended)
    | | | | + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +|
    • refIdCodeSystem = "MDC" (required).

    d. Inspiration pressure rise setting Numeric object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8410844^MDC_SABTE_LVL_INSP_PRESS_RISE_SET^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Inspiration pressure rise setting Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 262688^MDC_DIM_PERCENT^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|-----------------|------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-013 | | | | +| TP label | Pressure adaption level setting Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 19; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--| +| | Testable items | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Pressure adaption level setting Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_012 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Pressure adaption level setting Numeric Object | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Pressure adaption level setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>

        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Pressure adaption level setting Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410848^MDC_SABTE_LVL_ADAPT_SET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Pressure adaption level setting Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 262688^MDC_DIM_PERCENT^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | | | +| Pass/Fail criteria | All elements in each segment are as specified | | | + +| | | +|--------------|--| +| Notes | | +|--------------|--| + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-014 | | | | +| TP label | Pressure adaption freeze setting Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 20; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Pressure adaption freeze setting Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_013 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device with a Pressure adaption freeze setting object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Pressure adaption freeze setting object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • refIdName: the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:

    • <bitValue> = <0 or 1>
    • <bitName> is recommended to be the ASN.1 name for the bit
    • <bitPosition> is the normative position of the bit

    e. Pressure adaption freeze setting object follows this OBX encoding:

    • OBX-2 = 'CWE'
    • OBX-3 = 8410868^MDC_SABTE_MODE_ADAPT_FREEZE_SET^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for Pressure adaption freeze setting object respectively.
    • OBX-5 = 8410869^MDC_SABTE_MODE_ADAPT_FREEZE_OFF^MDC or
    • 8410870^MDC_SABTE_MODE_ADAPT_FREEZE_ON^MDC

    f. Any PM-Store, PM-Segment or Scanner attributes are not present.

    i. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|-----------------|--------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-015 | | | +| TP label | Autostart/-stop setting Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 21; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | | MetricClassAttr 1; M | +| | | | MetricClassAttr 4; M | +| | | | MetricClassAttr 7; O | +| | | | MetricClassAttr 10; O | +| | | | MetricClassAttr 13; O | +| | | | MetricClassAttr 16; C | +| | | | EnumClassAttr 1; M | +| | | | EnumClassAttr 4; M | + +| | | | | | +|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------| +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | |

    Check that:

    The presence of the attributes of the Autostart/-stop setting Object, the Metric and Enumeration attributes and their respective values.

    | | | +| Applicability | | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_014 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device with an Autostart/-stop setting object.

    | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Autostart/-stop setting object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:

        <refIdValue>^<refIdName>^<refIdCodeSystem>

        Where:

        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Autostart/-stop setting object follows this OBX encoding:
        • OBX-2 = 'CWE'
        • OBX-3 = 8410872^MDC_SABTE_MODE_AUTOSTARTSTOP_SET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Autostart/-stop setting object respectively.
        • OBX-5 = One of these values:

          <0 or 1>^sabte-autostart-on(0),

          <0 or 1>^sabte-autostop-on(1)

      6. f. Any PM-Store, PM-Segment or Scanner attributes are not present.
      7. g. One of the timestamp attributes can be present:
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-016 | | | | +| TP label | Device mode setting Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 22; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| | | | | | +| Test purpose | Check that:

    The presence of the attributes of the Device mode setting Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device. | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Device mode setting object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Device mode setting object follows this OBX encoding:
        • OBX-2 = 'CWE'
          OBX-3 = 8410876^MDC_SABTE_MODE_DEV_SET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Device mode setting object respectively.
        • OBX-5 = 8410877^MDC_SABTE_MODE_DEV_UNDETERMINED^MDC or 8410878^MDC_SABTE_MODE_DEV_STANDBY^MDC or 8410879^MDC_SABTE_MODE_DEV_THERAPY^MDC or 8410880^MDC_SABTE_MODE_DEV_MASK_FITTING^MDC or 8410881^MDC_SABTE_MODE_DEV_DRYING^MDC or 8410882^MDC_SABTE_MODE_DEV_EXPORTING^MDC
      6. f. Any PM-Store, PM-Segment or Scanner attributes are not present.
      7. g. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | +|-----------------|-----------------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-017 | +| TP label | Therapy mode setting Enumeration Object | + +| | | | | | +|--------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 23; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | | Check that:

    The presence of the attributes of the Therapy mode setting Object, the Metric and Enumeration attributes and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_SABTE_001 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Therapy mode setting object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
    | | | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +|

    e. Therapy mode setting object follows this OBX encoding:

    • OBX-2 = 'CWE'
      OBX-3 = 8410888^MDC_SABTE_MODE_THERAPY_SET^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Therapy mode setting object respectively.
    • OBX-5 = 8410889^MDC_SABTE_MODE_THERAPY_UNDETERMINED^MDC or 8410890^MDC_SABTE_MODE_THERAPY_CPAP^MDC or 8410891^MDC_SABTE_MODE_THERAPY_CPAP_AUTO^MDC or 8410892^MDC_SABTE_MODE_THERAPY_BPAP_S^MDC or 8410893^MDC_SABTE_MODE_THERAPY_BPAP_T^MDC or 8410894^MDC_SABTE_MODE_THERAPY_BPAP_ST^MDC or 8410895^MDC_SABTE_MODE_THERAPY_BPAP_S_AUTO^MDC or 8410896^MDC_SABTE_MODE_THERAPY_BPAP_T_AUTO^MDC or 8410897^MDC_SABTE_MODE_THERAPY_BPAP_ST_AUTO^MDC or 8410898^MDC_SABTE_MODE_THERAPY_ACSV^MDC

    f. Any PM-Store, PM-Segment or Scanner attributes are not present.

    g. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|-----------------|-------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-018 | | | | +| TP label | Compliance annotations Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 24; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|------------------| +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Compliance annotations Object, the Metric and Enumeration attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_015 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device with a Compliance annotations object. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Compliance annotations object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Compliance annotations object follows this OBX encoding:
        • OBX-2 = 'CWE'
          OBX-3 = 8410908^MDC_SABTE_PATT_COMPLIANCE_CLS^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Compliance annotations object respectively.
        • OBX-5 = One of these values:
          <0 or 1>^sabte-annotation-session-undetermined-start(0),
          <0 or 1>^sabte-annotation-session-undetermined-stop(1),
          <0 or 1>^sabte-annotation-session-therapy-start(2),
          <0 or 1>^sabte-annotation-session-therapy-stop(3),
          <0 or 1>^sabte-annotation-session-usage-start(4),
          <0 or 1>^sabte-annotation-session-usage-stop(5)
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | f. Any PM-Store, PM-Segment or Scanner attributes are not present.
    g. One of the timestamp attributes can be present:
    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-019 | | | | +| TP label | Efficacy annotations Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 25; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 21; M | DataGuidelines 22; M | | +| | | | | | +| Test purpose | Check that:
    The presence of the attributes of the Efficacy annotations Object, the Metric and Enumeration attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_016 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device with an Efficacy annotations object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Efficacy annotations object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL) and Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Efficacy annotations object follows this OBX encoding:
        • OBX-2 = 'CWE'
          OBX-3 = 8410916^MDC_SABTE_PATT_EFFICACY_CLS^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Efficacy annotations object respectively.
        • OBX-5 = One of these values:
          <0 or 1>^sabte-annotation-epoch-undetermined-start(0),
          <0 or 1>^sabte-annotation-epoch-undetermined-stop(1),
          <0 or 1>^sabte-annotation-epoch-breathing-artifact-start(2),
          <0 or 1>^sabte-annotation-epoch-breathing-artifact-stop(3),
          <0 or 1>^sabte-annotation-epoch-breathing-spontaneous-start(4),
          <0 or 1>^sabte-annotation-epoch-breathing-spontaneous-stop(5),
          <0 or 1>^sabte-annotation-epoch-breathing-timed-start(6),
          <0 or 1>^sabte-annotation-epoch-breathing-timed-stop(7),
          <0 or 1>^sabte-annotation-epoch-snoring-start(8),
          <0 or 1>^sabte-annotation-epoch-snoring-stop(9),
          <0 or 1>^sabte-annotation-epoch-csr-start(10),
          <0 or 1>^sabte-annotation-epoch-csr-stop(11),
          <0 or 1>^sabte-annotation-event-undetermined-start(12),
          <0 or 1>^sabte-annotation-event-undetermined-stop(13),
          <0 or 1>^sabte-annotation-event-flow-limitation-start(14),
          <0 or 1>^sabte-annotation-event-flow-limitation-stop(15),
          <0 or 1>^sabte-annotation-event-hypopnoea-unclassified-start(16),
          <0 or 1>^sabte-annotation-event-hypopnoea-unclassified-stop(17),
          <0 or 1>^sabte-annotation-event-hypopnoea-obstructive-start(18),
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    <0 or 1>^sabte-annotation-event-hypopnoea-obstructive-stop(19),
    <0 or 1>^sabte-annotation-event-hypopnoea-central-start(20),
    <0 or 1>^sabte-annotation-event-hypopnoea-central-stop(21),
    <0 or 1>^sabte-annotation-event-apnoea-unclassified-start(22),
    <0 or 1>^sabte-annotation-event-apnoea-unclassified-stop(23),
    <0 or 1>^sabte-annotation-event-apnoea-obstructive-start(24),
    <0 or 1>^sabte-annotation-event-apnoea-obstructive-stop(25),
    <0 or 1>^sabte-annotation-event-apnoea-mixed-start(26),
    <0 or 1>^sabte-annotation-event-apnoea-mixed-stop(27),
    <0 or 1>^sabte-annotation-event-apnoea-central-start(28),
    <0 or 1>^sabte-annotation-event-apnoea-central-stop(29)

    f. Any PM-Store, PM-Segment or Scanner attributes are not present.

    g. One of the timestamp attributes can be present:

    • ❑ MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|-----------------|----------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-020 | | | | +| TP label | Therapy pressure waveform RT-SA Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 26; M | SABTE 27; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | NumericClassAttr 7; O | PM-StoreAttr; M | PM-SegmentAttr; M | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------|------------------| +| | | ScannerAttr 1; M | ScannerAttr 2; M | ScannerAttr 3; M | +| | | ScannerAttr 4; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Therapy pressure waveform Object, the Metric and RT-SA attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_017 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device with a Therapy pressure waveform object.

    | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Therapy pressure waveform object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute(MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Therapy pressure waveform object follows this OBX encoding:
        • OBX-2 = 'NA'
        • OBX-3 = 8410948^MDC_SABTE_PRESS^MDC or 8410968^MDC_SABTE_PRESS_TARGET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Therapy pressure waveform object respectively.
        • OBX-5 = Numeric Array value (i.e. 11^22^33^44^55^66^77^88^99~...)
        • OBX-6 = 265986^MDC_DIM_HECTO_PASCAL^MDC
      5. e. Sample-Period attribute of Therapy pressure waveform object shall be sent and shall follow this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 67981^MDC_ATTR_TIME_PD_SAMP^MDC
        • OBX-5 = Numeric Value
        • OBX-6 = 264320^MDC_DIM_SEC^MDC or 264339^MDC_DIM_MICRO_SEC^MDC
      6. f. Any PM-Store, PM-Segment or Scanner attributes are not present.
      7. g. One of the timestamp attributes can be present:
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-021 | | | | +| TP label | Therapy pressure Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 28; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Therapy pressure Numeric Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_018 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Therapy pressure Numeric Object | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Therapy pressure Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Therapy pressure Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410949^MDC_SABTE_PRESS_MIN^MDC or 8410950^MDC_SABTE_PRESS_MAX^MDC or 8410951^MDC_SABTE_PRESS_MEAN^MDC or 8410955^MDC_SABTE_PRESS_P50^MDC or 8410957^MDC_SABTE_PRESS_P90^MDC or 8410958^MDC_SABTE_PRESS_P95^MDC or 8410959^MDC_SABTE_PRESS_INSTANT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Therapy pressure Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 265986^MDC_DIM_HECTO_PASCAL^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | +|-----------------|---------------------------------------------------------------------|-----------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-022 | | +| TP label | Continuous positive airway pressure (P CPAP) setting Numeric Object | | +| Coverage | Spec | [ITU-T H.812.1] | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| Testable items | SABTE 1; M | SABTE 29; M | MetricClassAttr 1; M | +| | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| Spec | [ITU-T H.812.1] | | | +| Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Continuous positive airway pressure (P CPAP) setting Numeric Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_019 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Continuous positive airway pressure (P CPAP) setting Numeric Object | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Continuous positive airway pressure (P CPAP) setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Continuous positive airway pressure (P CPAP) setting Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410972^MDC_SABTE_PRESS_CPAP_SET^MDC
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Continuous positive airway pressure (P CPAP) setting Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 265986^MDC_DIM_HECTO_PASCAL^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|---------------------|-------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-023 | | | | +| TP label | Minimal automatic positive airway pressure (Pmin APAP) setting Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 30; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that: | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The presence of the attributes of the Minimal automatic positive airway pressure (Pmin APAP) setting Numeric Object, the Metric and Numeric attributes and their respective values. | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_020 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Minimal automatic positive airway pressure (Pmin APAP) setting Numeric Object | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Minimal automatic positive airway pressure (Pmin APAP) setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Minimal automatic positive airway pressure (Pmin APAP) setting Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410976^MDC_SABTE_PRESS_CPAP_AUTO_MIN_SET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Minimal automatic positive airway pressure (Pmin APAP) setting Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 265986^MDC_DIM_HECTO_PASCAL^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-024 | | | +| TP label | Maximal automatic positive airway pressure (Pmax APAP) setting Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 31; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Maximal automatic positive airway pressure (Pmax APAP) setting Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_021 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Maximal automatic positive airway pressure (Pmax APAP) setting Numeric Object | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Maximal automatic positive airway pressure (Pmax APAP) setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        refldValue: is a 32 bit integer (required)
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • refIdName: the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Maximal automatic positive airway pressure (Pmax APAP) setting Numeric object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8410980^MDC_SABTE_PRESS_CPAP_AUTO_MAX_SET^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Maximal automatic positive airway pressure (Pmax APAP) setting Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 265986^MDC_DIM_HECTO_PASCAL^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|-----------------|----------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-025 | | | +| TP label | Inspiratory positive airway pressure (P IPAP) setting Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 32; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | | ScannerAttr 1; M | + +| | | | | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------|------------------|--|--|--| +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | | | | +| | Spec | [ITU-T H.812.1] | | | | | | +| | Testable items | DataGuidelines 22; M | | | | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Inspiratory positive airway pressure (P IPAP) setting Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_022 | | | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Inspiratory positive airway pressure (P IPAP) setting Numeric Object

    | | | | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Inspiratory positive airway pressure (P IPAP) setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Inspiratory positive airway pressure (P IPAP) setting Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8410984^MDC_SABTE_PRESS_IPAP_SET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Inspiratory positive airway pressure (P IPAP) setting Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 265986^MDC_DIM_HECTO_PASCAL^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
    | | | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = Numeric Value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--|--| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-026 | | | | | +| TP label | Expiratory positive airway pressure (P EPAP) setting Numeric Object | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | +| | Testable items | SABTE 1; M | SABTE 33; M | | | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | | | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | | | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | | | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | | | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | | | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | | | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | | | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | | | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | | | +| | | ScannerAttr 2; M | ScannerAttr 3; M | | | +| | Spec | [ITU-T H.812.1] | | | | +| | Testable items | DataGuidelines 22; M | | | | +| Test purpose | Check that:
    The presence of the attributes of the Expiratory positive airway pressure (P EPAP) setting Numeric Object, the Metric and Numeric attributes and their respective values. | | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_023 | | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with an Expiratory positive airway pressure (P EPAP) setting Numeric Object | | | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. Check in the captured message that:
      1. The Expiratory positive airway pressure (P EPAP) setting Numeric object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    | | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. Each MDC code using CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    Where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Expiratory positive airway pressure (P EPAP) setting Numeric object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8410988^MDC_SABTE_PRESS_EPAP_SET^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Expiratory positive airway pressure (P EPAP) setting Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 265986^MDC_DIM_HECTO_PASCAL^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|-----------------|--------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-027 | | | | +| TP label | Ramp start pressure setting Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 34; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | + +| | | | | | +|--------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | |

    Check that:

    The presence of the attributes of the Ramp start pressure setting Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_024 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Ramp start pressure setting Numeric Object | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Ramp start pressure setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Ramp start pressure setting Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8411004^MDC_SABTE_PRESS_RAMP_START_SET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Ramp start pressure setting Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 265986^MDC_DIM_HECTO_PASCAL^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
    • • OBX-5 = Numeric Value
    • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-028 | | | | +| TP label | Respiratory rate Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 35; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| | | | | | +| Test purpose | Check that:
    The presence of the attributes of the Respiratory rate Numeric Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_025 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Respiratory rate Numeric Object | | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. Check in the captured message that:
    1. a. The Respiratory rate Numeric object has sent at least one observation.
    2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute
    | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present

    c. Each MDC code using CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    Where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Respiratory rate Numeric object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8411009^MDC_SABTE_RESP_RATE_MIN^MDC or 8411010^MDC_SABTE_RESP_RATE_MAX^MDC or 8411011^MDC_SABTE_RESP_RATE_MEAN^MDC or 8411015^MDC_SABTE_RESP_RATE_P50^MDC or 8411017^MDC_SABTE_RESP_RATE_P90^MDC or 8411018^MDC_SABTE_RESP_RATE_P95^MDC or 8411019^MDC_SABTE_RESP_RATE_INSTANT^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Respiratory rate Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 264928^MDC_DIM_RESP_PER_MIN^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|-----------------|-----------------------------------------|----------------------|----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-029 | | | | +| TP label | Respiratory rate setting Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 36; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | + +| | | | | | +|--------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | |

    Check that:

    The presence of the attributes of the Respiratory rate setting Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_026 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Respiratory rate setting Numeric Object | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Respiratory rate setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Respiratory rate setting Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8411044^MDC_SABTE_RESP_RATE_SET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Respiratory rate setting Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264928^MDC_DIM_RESP_PER_MIN^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-030 | | | | +| TP label | I:E ratio Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 37; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the I:E ratio Numeric Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_027 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a I:E ratio Numeric Object | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The I:E ratio Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. I:E ratio Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8411049^MDC_SABTE_RATIO_IE_MIN^MDC or 8411050^MDC_SABTE_RATIO_IE_MAX^MDC or 8411051^MDC_SABTE_RATIO_IE_MEAN^MDC or 8411055^MDC_SABTE_RATIO_IE_P50^MDC or 8411057^MDC_SABTE_RATIO_IE_P90^MDC or 8411058^MDC_SABTE_RATIO_IE_P95^MDC or 8411059^MDC_SABTE_RATIO_IE_INSTANT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the I:E ratio Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 262688^MDC_DIM_PERCENT^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|-----------------|-------------------------------------|-----------------|-------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-031 | | | | +| TP label | I:E ratio setting Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable | SABTE 1; M | SABTE 38; M | MetricClassAttr 1; M | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| items | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| Spec | [ITU-T H.812.1] | | | +| Testable items | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the I:E ratio setting Numeric Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_028 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a I:E ratio setting Numeric Object | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The I:E ratio setting Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. I:E ratio setting Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8411084^MDC_SABTE_RATIO_IE_SET^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the I:E ratio setting Numeric object respectively.
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-5 = Numeric value
    • OBX-6 = 262688^MDC_DIM_PERCENT^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-032 | | | +| TP label | Leakage waveform RT-SA Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 39; M | +| | | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 7; O | PM-StoreAttr; M | +| | | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 4; M | | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Leakage waveform Object, the Metric and RT-SA attributes and their respective values. | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_029 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a SABTE device with a Leakage waveform object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Leakage waveform object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute(MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Leakage waveform object follows this OBX encoding:
        • OBX-2 = 'NA'
        • OBX-3 = 8411088^MDC_SABTE_VOL_LEAK^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Leakage waveform object respectively.
        • OBX-5 = Numeric Array value (i.e. 11^22^33^44^55^66^77^88^99~...)
        • OBX-6 = 264992^MDC_DIM_L_PER_MIN^MDC
      5. e. Sample-Period attribute of Leakage waveform object shall be sent and shall follow this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 67981^MDC_ATTR_TIME_PD_SAMP^MDC
        • OBX-5 = Numeric Value
        • OBX-6 = 264320^MDC_DIM_SEC^MDC or 264339^MDC_DIM_MICRO_SEC^MDC
      6. f. Any PM-Store, PM-Segment or Scanner attributes are not present.
      7. g. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | + +| | | +|--------------|--| +| Notes | | +|--------------|--| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-033 | | | +| TP label | Leakage Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 41; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Leakage object Numeric Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_030 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Leakage Numeric Object | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. Check in the captured message that:
    a. The Leakage Numeric object has sent at least one observation.
    b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    c. Each MDC code using CWE data type is encoded as:
    ^^
    Where:
    refldValue: is a 32 bit integer (required) | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • refIdName: the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Leakage Numeric object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8411089^MDC_SABTE_VOL_LEAK_MIN^MDC or 8411090^MDC_SABTE_VOL_LEAK_MAX^MDC or 8411091^MDC_SABTE_VOL_LEAK_MEAN^MDC or 8411095^MDC_SABTE_VOL_LEAK_P50^MDC or 8411097^MDC_SABTE_VOL_LEAK_P90^MDC or 8411098^MDC_SABTE_VOL_LEAK_P95^MDC or 8411099^MDC_SABTE_VOL_LEAK_INSTANT^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Leakage Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 264992^MDC_DIM_L_PER_MIN^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | | +|-----------------|------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-034 | | | | +| TP label | Respiratory minute volume Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | SABTE 1; M | SABTE 42; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | + +| | | | | | +|--------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 22; M | | | +| Test purpose | |

    Check that:

    The presence of the attributes of the Respiratory minute volume Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_031 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Respiratory minute volume Numeric Object

    | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device.
    2. 2. Check in the captured message that:
      1. a. The Respiratory minute volume Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Respiratory minute volume Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8411129^MDC_SABTE_VOL_MINUTE_MIN^MDC or 8411130^MDC_SABTE_VOL_MINUTE_MAX^MDC or 8411131^MDC_SABTE_VOL_MINUTE_MEAN^MDC or 8411135^MDC_SABTE_VOL_MINUTE_P50^MDC or 8411137^MDC_SABTE_VOL_MINUTE_P90^MDC or 8411138^MDC_SABTE_VOL_MINUTE_P95^MDC or 8411139^MDC_SABTE_VOL_MINUTE_INSTANT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Respiratory minute volume Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264992^MDC_DIM_L_PER_MIN^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
    • OBX-5 = Numeric Value
    • OBX-18 has a timebase ID.
    MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
    • OBX-5 = Numeric Value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/SABTE/BV-035 | | | +| TP label | Tidal volume Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | SABTE 1; M | SABTE 43; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | Spec | [ITU-T H.812.1] | | +| | Testable items | DataGuidelines 22; M | | +| Test purpose | Check that:
    The presence of the attributes of the Tidal volume Numeric Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_SABTE_001 AND C_SEN_SABTE_032 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an SABTE device with a Tidal volume Numeric Object | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an Observation of a SABTE device. | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. Check in the captured message that:

    • a. The Tidal volume Numeric object has sent at least one observation.
    • b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    • c. Each MDC code using CWE data type is encoded as:
      <refIdValue>^<refIdName>^<refIdCodeSystem>
      Where:
      • refIdValue: is a 32 bit integer (required)
      • refIdName: the normative nomenclature name for the unique code point (recommended)
      • refIdCodeSystem = "MDC" (required).
    • d. Tidal volume Numeric object follows this OBX encoding:
      • OBX-2 = 'NM'
      • OBX-3 = 8411169^MDC_SABTE_VOL_TIDAL_MIN^MDC or 8411170^MDC_SABTE_VOL_TIDAL_MAX^MDC or 8411171^MDC_SABTE_VOL_TIDAL_MEAN^MDC or 8411175^MDC_SABTE_VOL_TIDAL_P50^MDC or 8411177^MDC_SABTE_VOL_TIDAL_P90^MDC or 8411178^MDC_SABTE_VOL_TIDAL_P95^MDC or
      • 8411179^MDC_SABTE_VOL_TIDAL_INSTANT^MDC
      • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Tidal volume Numeric object respectively.
      • OBX-5 = Numeric value
      • OBX-6 = 264992^MDC_DIM_L_PER_MIN^MDC
    • e. Any PM-Store, PM-Segment or Scanner attributes are not present.
    • f. One of the timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified | +| Notes | | + +## A.18 Subgroup 1.4.17: Insulin pump + +| | | +|-----------------|----------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-000 | +| TP label | MDS Object | + +| | | | | | +|--------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------| +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | MDSClassAttr 1; M | MDSClassAttr 2; C | MDSClassAttr 3; M | +| | | MDSClassAttr 4; M | MDSClassAttr 5; M | MDSClassAttr 6; M | +| | | MDSClassAttr 7; O | MDSClassAttr 8; M | MDSClassAttr 9; C | +| | | MDSClassAttr 10; C | MDSClassAttr 11; C | MDSClassAttr 12; M | +| | | MDSClassAttr 13; M | MDSClassAttr 14; M | MDSClassAttr 15; M | +| | | MDSClassAttr 16; M | MDSClassAttr 17; C | MDSClassAttr 18; M | +| | | MDSObject 1; M | MDSObject 2; M | MDSObject 3; M | +| | | MDSObject 4; M | MDSObject 5; M | MDSObject 6; M | +| | | MDSObject 7; M | MDSObject 8; M | MDSObject 9; M | +| | | MDSObject 10; M | MDSObject 11; M | MDSObject 12; M | +| | | MDSObject 13; O | MDSObject 14; O | MDSObject 15; O | +| | | MDSObject 16; M | MDSObject 17; M | MDSObject 18; M | +| | | MDSObject 19; M | MDSObject 20; M | MDSObject 21; M | +| | | MDSObject 22; M | MDSObject 23; M | MDSObject 24; M | +| | | MDSObject 25; M | MDSObject 26; M | MDSObject 27; M | +| | | MDSObject 28; M | MDSObject 29; M | MDSObject 30; M | +| | | MDSObject 31; M | MDSObject 32; M | MDSObject 33; M | +| | | IP 2; M | Timestamp 13; O | Timestamp 14; O | +| | | Timestamp 15; O | Timestamp 17; M | | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | DeviceTimeSync1; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_IP_001 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device. | | | +| Test procedure | |
    1. Make the HFS sender under test send an HL7 message containing an Observation of an Insulin Pump device.
    2. Check in the captured message that:
    | | | + +- a. Handle attribute (MDC\_ATTR\_ID\_HANDLE), Dev-Config-Id attribute (MDC\_ATTR\_DEV\_CONFIG\_ID) and Attribute-Value-Map (MDC\_ATTR\_ATTRIBUTE\_VALUE\_MAP) are not present +- b. Each MDC code using CWE data type is encoded as: +^^ +Where: + - refIdValue: is a 32 bit integer (required) + - refIdName: the normative nomenclature name for the unique code point (recommended) + - refIdCodeSystem = "MDC" (required). +- c. A bit flag value is encoded as ^(), where: + - = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: + - OBX-2 is empty + - If System-Type attribute is valued, OBX-3 = 528403^MDC\_DEV\_SPEC\_PROFILE\_INSULIN\_PUMP^MDC + - If System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System Id is 16 characters given by the PIXIT I\_SEN\_IP\_001. +- e. System model attribute is sent in two different OBX segments: + - System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: + - Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + +- ❑ Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + - OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype +- ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'ST' +- OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC +- OBX-5 = String representing the value portion of the Production-Specification GMDN entry +- OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. + +g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent as a timestamp, its respective resolution may be sent, but not other than this.) + +Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'CWE' +- OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC +- OBX-5 = One or more of these values: + <0 or 1>^mds-time-capab-real-time-clock(0), + <0 or 1>^mds-time-capab-set-clock(1), + <0 or 1>^mds-time-capab-relative-time(2), + <0 or 1>^mds-time-capab-high-res-relative-time(3), + <0 or 1>^mds-time-capab-sync-abs-time(4), + <0 or 1>^mds-time-capab-sync-rel-time(5), + <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + <0 or 1>^mds-time-capab-bo-time (7), + <0 or 1>^mds-time-state-abs-time-synced(8), + <0 or 1>^mds-time-state-rel-time-synced(9), + <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + <0 or 1>^mds-time-mgr-set-time(11), + <0 or 1>^mds-time-capab-sync-bo-time(12), + <0 or 1>^mds-time-state-bo-time-synced(13), + <0 or 1>^mds-time-state-bo-time-UTC-aligned(14), + <0 or 1>^mds-time-dst-rules-enabled(15) + +Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC +- OBX-5 = NM data type value +- OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + +Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'CWE' +- OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC +- OBX-5 = One of these values: + 532224^MDC\_TIME\_SYNC\_NONE^MDC + 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + +532229^MDC\_TIME\_SYNC\_BTV1^MDC +532230^MDC\_TIME\_SYNC\_RADIO^MDC +532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC +532232^MDC\_TIME\_SYNC\_CDMA^MDC +532233^MDC\_TIME\_SYNC\_GSM^MDC +532234^MDC\_TIME\_SYNC\_EBWW^MDC +532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC + +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + - OBX-14 = UTC value +- ❑ Base-Offset-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 68225^MDC\_ATTR\_TIME\_BO^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = DTM data type value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDCor + - OBX-2 = 'NM' + - OBX-3 = 68226^MDC\_TIME\_RES\_BO^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + +- Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC +- OBX-5 = NM data type value +- OBX-6 = 264320^MDC\_DIM\_SEC^MDC + +- If valued, Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC +- OBX-5 = NM data type value +- OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + +h. Date-and-Time-Adjustment attribute is not present + +i. If Power-Status attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'ST' +- OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC +- OBX-5 = One or more of these values: +<0 or 1>^onMains(0), +<0 or 1>^onBattery(1), +<0 or 1>^chargingFull(8), +<0 or 1>^chargingTrickle(9), +<0 or 1>^chargingOff(10) + +j. If Battery-Level attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC +- OBX-5 = NM data type value +- OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC + +k. If Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + +- OBX-2 = 'NM' +- OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC +- OBX-5 = Use the value contained in the BatMeasure object +- OBX-6 = Use the OID contained in the BatMeasure object + +l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different Facet-level entries and the following mandatory fields: + +- OBX-2 = 'CWE' +- OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC + +OBX-5 = One of these values: + +- 0^auth-body-empty, +- 1^auth-body-ieee-11073, +- 2^auth-body-continua, +- 254^auth-body-experimental, +- 255^auth-body-reserved + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    m. Observations from Continua-compliant source devices are sent using three attributes as Facet-level entries of the Regulation-Certification-Auth-Body OBX segments:

    • ❑ Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding:
      • • OBX-2 = 'ST'
      • • OBX-3 = 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC
      • • OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the Facet level of that segment.
      • • OBX-5 = <major-IG-version>.<minor-IG-version>.
    • ❑ Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding:
      • • OBX-2 = 'NA'
      • • OBX-3 = 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC
      • • OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'b' is a number indicating the Facet level of that segment.
      • • OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 16403 (IP Wireless PAN), 8211 (IP Wired PAN), 24595 (IP Sensor LAN) or 40979 (IP TAN).
    • ❑ Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding:
      • • OBX-2 = 'CWE'
      • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
      • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'a' is a number indicating the Facet level of that segment.
      • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • ❑ OBX-2 = 'CWE'
    • ❑ OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • ❑ OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|----------------------------------|-----------------|-----------------------------------------------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-001 | | | +| TP label | Bolus Delivered Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable | IP 1; M | IP 3; M MetricClassAttr 1; M | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| items | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Bolus Delivered Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_IP_001 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test to send a HL7 message containing an Observation of an Insulin Pump device.
    2. 2. Check in the captured message that:
      1. a. The Bolus Delivered Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Bolus Delivered Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8418344^MDC_INS_BOLUS^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Bolus Delivered Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 267616^MDC_DIM_X_INTL_UNIT^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | f. One of the timestamp attributes can be present:
    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-002 | | | | +| TP label | Current Basal Rate Setting Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | IP 1; M | IP 4; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Current Basal Rate Setting Numeric Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_IP_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device. | | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an Observation of an Insulin Pump device. | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. Check in the captured message that:

    • a. The Current Basal Rate Setting Numeric object has sent at least one observation.
    • b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    • c. Each MDC code using CWE data type is encoded as:
      <refIdValue>^<refIdName>^<refIdCodeSystem>
      Where:
      • refIdValue: is a 32 bit integer (required)
      • refIdName: the normative nomenclature name for the unique code point (recommended)
      • refIdCodeSystem = "MDC" (required).
    • d. Current Basal Rate Setting Numeric object follows this OBX encoding:
      • OBX-2 = 'NM'
      • OBX-3 = 8418300^MDC_INS_BASAL_RATE_SETTING^MDC
      • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Current Basal Rate Setting Numeric object respectively.
      • OBX-5 = Numeric value
      • OBX-6 = 267840^MDC_DIM_X_INTL_UNIT_PER_HR^MDC
    • e. Any PM-Store, PM-Segment or Scanner attributes are not present.
    • f. One of the timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
        YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|----------------------------------|----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-003 | | | +| TP label | PHD DM Status Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | IP 1; M | IP 5; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | | MetricClassAttr 4; M | +| | | | MetricClassAttr 7; O | +| | | | MetricClassAttr 10; O | + +| | | | | | +|--------------------------|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose | | Check that:
    The presence of the attributes of the PHD DM Status Object, the Metric and Enumeration attributes and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_IP_001 AND C_SEN_IP_002 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device with a PHD DM Status object. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an Insulin Pump device.
    2. 2. Check in the captured message that:
      1. a. The PHD DM Status object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) attribute are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. PHD DM Status object follows this OBX encoding:
        • OBX-2 = 'CWE'
          OBX-3 = 8408608^MDC_PHD_DM_DEV_STAT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Device and PHD DM Status object respectively.
        • OBX-5 = Any of these values:
          <0 or 1>^device-status-undetermined(0),
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    <0 or 1>^device-status-reset(1),

    <0 or 1>^device-status-error(5),

    <0 or 1>^device-status-error-mechanical(6),

    <0 or 1>^device-status-error-electronic(7),

    <0 or 1>^device-status-error-software(8),

    <0 or 1>^device-status-error-battery(9),

    <0 or 1>^device-status-service(15),

    <0 or 1>^device-status-service-time-sync-required(16),

    <0 or 1>^device-status-service-calibration-required(17),

    <0 or 1>^device-status-service-replenishment-required(18),

    <0 or 1>^device-status-battery-low(25),

    <0 or 1>^device-status-battery-depleted(26),

    <0 or 1>^device-status-battery-replaced(27),

    <0 or 1>^device-status-battery-interrupted(28)

    f. Any PM-Store, PM-Segment or Scanner attributes are not present.

    j. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-004 | | | | +| TP label | Insulin Pump Status Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | IP 1; M | IP 6; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--------------------|----------------------| +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | DataGuidelines 21; M | +| | | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Insulin Pump Status Object, the Metric and Enumeration attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_IP_001 AND C_SEN_IP_003 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device with a Insulin Pump Status object.

    | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an Insulin Pump device.
    2. 2. Check in the captured message that:
      1. a. The Insulin Pump Status object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) attribute are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Insulin Pump Status object follows this OBX encoding:
        • OBX-2 = 'CWE'
          OBX-3 = 8418444^MDC_INS_PUMP_DEV_STAT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for Device and the Insulin Pump Status object respectively.
        • OBX-5 = Any of these values:
          <0 or 1>^air-pressure-out-of-range(0),
          <0 or 1>^bolus-canceled(1),
          <0 or 1>^delivery-max(2),
          <0 or 1>^infusion-set-detached(3),
          <0 or 1>^infusion-set-incomplete(4),
          <0 or 1>^occlusion-detected(5),
          <0 or 1>^power-insufficient(6),
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    <0 or 1>^priming-issue(7),
    <0 or 1>^reservoir-empty(8),
    <0 or 1>^reservoir-issue(9),
    <0 or 1>^reservoir-low(10),
    <0 or 1>^reservoir-attached(11),
    <0 or 1>^temp-basal-canceled(12),
    <0 or 1>^temp-basal-expired(13),
    <0 or 1>^temperature-out-of-range(14)

    f. Any PM-Store, PM-Segment or Scanner attributes are not present.

    g. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|-------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-005 | | | | +| TP label | Operational and Therapy Conditions Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | IP 1; M | IP 7; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | DataGuidelines 21; M | +| | | DataGuidelines 22; M | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    The presence of the attributes of the Operational and Therapy Conditions Object, the Metric and Enumeration attributes and their respective values.

    | +| Applicability | C_SEN_000 AND C_SEN_IP_001 AND C_SEN_IP_004 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device with an Operational and Therapy Conditions object. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an Insulin Pump device.
    2. 2. Check in the captured message that:
      1. a. The Operational and Therapy Conditions object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) attribute are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
        • <bitValue> = <0 or 1>
        • <bitName> is recommended to be the ASN.1 name for the bit
        • <bitPosition> is the normative position of the bit
      5. e. Operational and Therapy Conditions object follows this OBX encoding:
        • OBX-2 = 'CWE'
          OBX-3 = 8418412^MDC_INS_PUMP_OP_STAT^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Device and the Operational and Therapy Conditions object respectively.
        • OBX-5 = Any of these values:
          <0 or 1>^insulin-device-op-undetermined(0),
          <0 or 1>^insulin-device-op-off(1),
          <0 or 1>^insulin-device-op-standby(2),
          <0 or 1>^insulin-device-op-preparing(3),
          <0 or 1>^insulin-device-op-priming(4),
          <0 or 1>^insulin-device-op-waiting(5),
          <0 or 1>^insulin-device-op-ready(6),
          <0 or 1>^insulin-device-therapy-undetermined(7),
          <0 or 1>^insulin-device-therapy-stop(8),
          <0 or 1>^insulin-device-therapy-pause(9),
          <0 or 1>^insulin-device-therapy-run(10)
      6. f. Any PM-Store, PM-Segment or Scanner attributes are not present.
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    g. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-006 | | | +| TP label | Current Bolus Setting Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | IP 1; M | IP 8; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the Current Bolus Setting Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | C_SEN_000 AND C_SEN_IP_001 AND C_SEN_IP_005 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an Insulin Pump device.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. Check in the captured message that:

    • a. The Current Bolus Setting Numeric object has sent at least one observation.
    • b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
    • c. Each MDC code using CWE data type is encoded as:
      <refIdValue>^<refIdName>^<refIdCodeSystem>
      Where:
      • refIdValue: is a 32 bit integer (required)
      • refIdName: the normative nomenclature name for the unique code point (recommended)
      • refIdCodeSystem = "MDC" (required).
    • d. Current Bolus Setting Numeric object follows this OBX encoding:
      • OBX-2 = 'NM'
      • OBX-3 = 8418332^MDC_INS_BOLUS_SETTING^MDC
      • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Current Bolus Setting Numeric object respectively.
      • OBX-5 = Numeric value
      • OBX-6 = 267616^MDC_DIM_X_INTL_UNIT^MDC or 267840^MDC_DIM_X_INTL_UNIT_PER_HR^MDC
    • e. Any PM-Store, PM-Segment or Scanner attributes are not present.
    • f. One of the timestamp attributes can be present:
      • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
        YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
      • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
      • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
        • • OBX-5 = Numeric Value
        • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|------------------------------------|----------------------|----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-007 | | | | +| TP label | Pending Bolus Delay Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | IP 1; M | IP 9; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | + +| | | | | | +|--------------------------|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 22; M | | | +| Test purpose | | Check that:

    The presence of the attributes of the Pending Bolus Delay Numeric Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_IP_001 AND C_SEN_IP_006 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an Insulin Pump device.
    2. 2. Check in the captured message that:
      1. a. The Pending Bolus Delay Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>

        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Pending Bolus Delay Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8418355^MDC_INS_BOLUS_PENDING_DELAY^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Pending Bolus Delay Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264352^MDC_DIM_MIN^MDC or 264320^MDC_DIM_SEC^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
    • OBX-5 = Numeric Value
    • OBX-18 has a timebase ID.
    MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
    • OBX-5 = Numeric Value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-008 | | | +| TP label | Basal Delivered Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | IP 1; M | IP 10; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | | DataGuidelines 22; M | | +| Test purpose | Check that:

    The presence of the attributes of the Basal Delivered Numeric Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_IP_001 AND C_SEN_IP_007 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an Observation of an Insulin Pump device.

    2. Check in the captured message that:
    a. The Basal Delivered Numeric object has sent at least one observation. | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present

    c. Each MDC code using CWE data type is encoded as:
    <refIdValue>^<refIdName>^<refIdCodeSystem>

    Where:

    • ❑ refIdValue: is a 32 bit integer (required)
    • ❑ refIdName: the normative nomenclature name for the unique code point (recommended)
    • ❑ refIdCodeSystem = "MDC" (required).

    d. Basal Delivered Numeric object follows this OBX encoding:

    • ❑ OBX-2 = 'NM'
    • ❑ OBX-3 = 8418288^MDC_INS_BASAL^MDC
    • ❑ OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Basal Delivered Numeric object respectively.
    • ❑ OBX-5 = Numeric value
    • ❑ OBX-6 = 267616^MDC_DIM_X_INTL_UNIT^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • ❑ MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|-----------------|--------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-009 | | | | +| TP label | Insulin Reservoir Remaining Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | IP 1; M | IP 11; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | + +| | | | | | +|--------------------------|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 22; M | | | +| Test purpose | |

    Check that:

    The presence of the attributes of the Insulin Reservoir Remaining Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | +| Applicability | | C_SEN_000 AND C_SEN_IP_001 AND C_SEN_IP_008 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of an Insulin Pump device.
    2. 2. Check in the captured message that:
      1. a. The Insulin Reservoir Remaining Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Insulin Reservoir Remaining Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8418388^MDC_INS_RESERVOIR^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Insulin Reservoir Remaining Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 267616^MDC_DIM_X_INTL_UNIT^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
    • OBX-5 = Numeric Value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/IP/BV-010 | | | +| TP label | Insulin Concentration Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | IP 1; M | IP 12; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | | DataGuidelines 22; M | | +| Test purpose | Check that:

    The presence of the attributes of the Insulin Concentration Numeric Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_IP_001 AND C_SEN_IP_009 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of an Insulin Pump device. | | | +| Test procedure |
    1. Make the HFS sender under test send a HL7 message containing an Observation of an Insulin Pump device.
    2. Check in the captured message that:
      1. The Insulin Concentration Numeric object has sent at least one observation.
      2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Where:

    • refIdValue: is a 32 bit integer (required)
    • refIdName: the normative nomenclature name for the unique code point (recommended)
    • refIdCodeSystem = "MDC" (required).

    d. Insulin Concentration Numeric object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8418390^MDC_INS_CONC^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Insulin Concentration Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 267712^MDC_DIM_X_INTL_UNIT_PER_L^MDC or 267744^MDC_DIM_X_INTL_UNIT_PER_ML^MDC or 267680^MDC_DIM_X_INTL_UNIT_PER_M_CUBE^MDC or 267648^MDC_DIM_X_INTL_UNIT_PER_CM_CUBE^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +## A.19 Subgroup 1.4.18: Continuous glucose monitor (CGM) + +| | | | | +|-----------------|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-000 | | | +| TP label | MDS Object | | | +| Coverage | [ITU-T H.812.1] | | | +| | Spec

    Testable items | MDSCClassAttr 1; M
    MDSCClassAttr 4; M
    MDSCClassAttr 7; O
    MDSCClassAttr 10; C
    MDSCClassAttr 13; M
    MDSCClassAttr 16; M | MDSCClassAttr 2; C
    MDSCClassAttr 5; M
    MDSCClassAttr 8; M
    MDSCClassAttr 11; C
    MDSCClassAttr 14; M
    MDSCClassAttr 17; C | + +| | | | | | +|--------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------| +| | | MDSObject 1; M | MDSObject 2; M | MDSObject 3; M | +| | | MDSObject 4; M | MDSObject 5; M | MDSObject 6; M | +| | | MDSObject 7; M | MDSObject 8; M | MDSObject 9; M | +| | | MDSObject 10; M | MDSObject 11; M | MDSObject 12; M | +| | | MDSObject 13; O | MDSObject 14; O | MDSObject 15; O | +| | | MDSObject 16; M | MDSObject 17; M | MDSObject 18; M | +| | | MDSObject 19; M | MDSObject 20; M | MDSObject 21; M | +| | | MDSObject 22; M | MDSObject 23; M | MDSObject 24; M | +| | | MDSObject 25; M | MDSObject 26; M | MDSObject 27; M | +| | | MDSObject 28; M | MDSObject 29; M | MDSObject 30; M | +| | | MDSObject 31; M | MDSObject 32; M | MDSObject 33; M | +| | | CGM 2; M | Timestamp 13; O | Timestamp 14; O | +| | | Timestamp 15; O | Timestamp 17; M | | +| | Spec | [IHE PCD TF 2] | | | +| | Testable items | DeviceTimeSync1; M | | | +| | Spec | [ITU-T H.812.1] | | | +| | Testable items | DataGuidelines 9; M | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | | Check that:
    The presence of the attributes of the MDS Object and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_CGM_001 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a Continuous Glucose Monitor device. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device.
    2. 2. Check in the captured message that:
      1. a. Handle attribute (MDC_ATTR_ID_HANDLE), Dev-Config-Id attribute (MDC_ATTR_DEV_CONFIG_ID) and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) attribute are not present
      2. b. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      3. c. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:
    | | | + +- = <0 or 1> + - is recommended to be the ASN.1 name for the bit + - is the normative position of the bit +- d. In MDS-level OBX: +- OBX-2 is empty + - If System-Type attribute is valued, OBX-3 = 528410^MDC\_DEV\_SPEC\_PROFILE\_CGM^MDC + - If System-Type-Spec-List attribute contains a single value and System-Type is not valued, this value is reported as the OBX-3 + - If System-Type-Spec-List contains multiple values and System-Type is not valued, OBX-3 = 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC and the specialization list is reported as an attribute of the device. + - If Date-and-Time attribute is valued, OBX-14 is valued with the UTC coordinated time of the AHD + - OBX-11 = 'X' + - OBX-18 (System Id attribute) = ^^^EUI-64, where the System Id is 16 characters given by the PIXIT I\_SEN\_CGM\_001. +- e. System model attribute is sent in two different OBX segments: +- System-Model attribute: + - OBX-2 = 'ST' + - OBX-3 = 531969^MDC\_ID\_MODEL\_NUMBER^MDC + - OBX-5 = String representing the model number portion of MDC\_ATTR\_ID\_MODEL attribute + - System-Manufacturer attribute: + - OBX-2 = 'ST' + - OBX-3 = 531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC + - OBX-5 = String representing the model manufacturer portion of MDC\_ATTR\_ID\_MODEL attribute. +- f. Production-Specification attribute is sent as a series of attributes: +- Production-Specification-Unspecified attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531971^MDC\_ID\_PROD\_SPEC\_UNSPECIFIED^MDC + - OBX-5 = String representing the value portion of the Production-Specification entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Serial attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC + - OBX-5 = String representing the value portion of the Production-Specification serial entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - Production-Specification-Part attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531973^MDC\_ID\_PROD\_SPEC\_PART^MDC + +- OBX-5 = String representing the value portion of the Production-Specification part entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-Hardware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531974^MDC\_ID\_PROD\_SPEC\_HW^MDC + - OBX-5 = String representing the value portion of the Production-Specification hardware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-Software attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531975^MDC\_ID\_PROD\_SPEC\_SW^MDC + - OBX-5 = String representing the value portion of the Production-Specification software entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-Firmware attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531976^MDC\_ID\_PROD\_SPEC\_FW^MDC + - OBX-5 = String representing the value portion of the Production-Specification firmware entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531977^MDC\_ID\_PROD\_SPEC\_PROTOCOL^MDC + - OBX-5 = String representing the value portion of the Production-Specification protocol entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype + - ❑ Production-Specification-GMDN group attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 531978^MDC\_ID\_PROD\_SPEC\_GMDN^MDC + - OBX-5 = String representing the value portion of the Production-Specification GMDN entry + - OBX-18 = The component portion of the Production-Specification entry encoded as an EI datatype. +- g. Mds-Time-Info attribute is sent as a series of attributes, as follows. (When it is sent a Timestamp, its respective resolution may be sent, but not other than this.) +- ❑ Mds-Time-Cap-State attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68219^MDC\_TIME\_CAP\_STATE^MDC + +- OBX-5 = One or more of these values: + - <0 or 1>^mds-time-capab-real-time-clock(0), + - <0 or 1>^mds-time-capab-set-clock(1), + - <0 or 1>^mds-time-capab-relative-time(2), + - <0 or 1>^mds-time-capab-high-res-relative-time(3), + - <0 or 1>^mds-time-capab-sync-abs-time(4), + - <0 or 1>^mds-time-capab-sync-rel-time(5), + - <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6), + - <0 or 1>^mds-time-capab-bo-time (7), + - <0 or 1>^mds-time-state-abs-time-synced(8), + - <0 or 1>^mds-time-state-rel-time-synced(9), + - <0 or 1>^mds-time-state-hi-res-relative-time-synced(10), + - <0 or 1>^mds-time-mgr-set-time(11), + - <0 or 1>^mds-time-capab-sync-bo-time(12), + - <0 or 1>^mds-time-state-bo-time-synced(13), + - <0 or 1>^mds-time-state-bo-time-UTC-aligned(14), + - <0 or 1>^mds-time-dst-rules-enabled(15) +- ❑ Time-Sync-Accuracy attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68221^MDC\_TIME\_SYNC\_ACCURACY^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Sync-Protocol attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'CWE' + - OBX-3 = 68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC + - OBX-5 = One of these values: + - 532224^MDC\_TIME\_SYNC\_NONE^MDC + - 532225^MDC\_TIME\_SYNC\_NTPV3^MDC + - 532226^MDC\_TIME\_SYNC\_NTPV4^MDC + - 532227^MDC\_TIME\_SYNC\_SNTPV4^MDC + - 532228^MDC\_TIME\_SYNC\_SNTPV4330^MDC + - 532229^MDC\_TIME\_SYNC\_BTV1^MDC + - 532230^MDC\_TIME\_SYNC\_RADIO^MDC + - 532231^MDC\_TIME\_SYNC\_HL7\_NCK^MDC + - 532232^MDC\_TIME\_SYNC\_CDMA^MDC + - 532233^MDC\_TIME\_SYNC\_GSM^MDC + - 532234^MDC\_TIME\_SYNC\_EBWW^MDC + - 532235^MDC\_TIME\_SYNC\_USB\_SOF^MDC +- ❑ Date and Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 67975^MDC\_ATTR\_TIME\_ABS^MDC + - OBX-5 = DTM data type value + +- OBX-14 = UTC value +- ❑ Base-Offset-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'DTM' + - OBX-3 = 68225^MDC\_ATTR\_TIME\_BO^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = DTM data type value +- ❑ Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67983^MDC\_ATTR\_TIME\_REL^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ HiRes-Relative-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68072^MDC\_ATTR\_TIME\_REL\_HI\_RES^MDC + - OBX-4 = m.0.0.x, where 'x' is any integer value + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + - OBX-18 = A unique identifier for the given timebase +- ❑ Time-Resolution-Abs-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68222^MDC\_TIME\_RES\_ABS^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + +or + + - OBX-2 = 'NM' + - OBX-3 = 68226^MDC\_TIME\_RES\_BO^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC +- ❑ Time-Resolution-Rel-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68223^MDC\_TIME\_RES\_REL^MDC + - OBX-5 = NM data type value + - OBX-6 = 264320^MDC\_DIM\_SEC^MDC +- ❑ If valued, Time-Resolution-High-Res-Time attribute, if valued, is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 68224^MDC\_TIME\_RES\_HI\_RES^MDC + - OBX-5 = NM data type value + - OBX-6 = 264339^MDC\_DIM\_MICRO\_SEC^MDC + +- h. Date-and-Time-Adjustment attribute is not present +- i. If Power-Status attribute is valued, it is sent as an independent OBX segment: + - OBX-2 = 'ST' + - OBX-3 = 67925^MDC\_ATTR\_POWER\_STAT^MDC + - OBX-5 = One or more of these values: + - <0 or 1>^onMains(0), + - <0 or 1>^onBattery(1), + - <0 or 1>^chargingFull(8), + - <0 or 1>^chargingTrickle(9), + - <0 or 1>^chargingOff(10) +- j. If Battery-Level attribute is valued, it is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC + - OBX-5 = NM data type value + - OBX-6 = 262688^MDC\_DIM\_PERCENT^MDC +- k. If Remaining-Battery-Time attribute is valued, it is sent as an independent OBX segment: + - OBX-2 = 'NM' + - OBX-3 = 67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC + - OBX-5 = Use the value contained in the BatMeasure object + - OBX-6 = Use the OID contained in the BatMeasure object +- l. Reg-Cert-Data-List is sent as an attribute of the device using two separate Regulation-Certification-Auth-Body OBX segments with different Facet-level entries and the following mandatory fields: + - OBX-2 = 'CWE' + - OBX-3 = 68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC + - OBX-5 = One of these values: + - 0^auth-body-empty, + - 1^auth-body-ieee-11073, + - 2^auth-body-continua, + - 254^auth-body-experimental, + - 255^auth-body-reserved +- m. Observations from Continua-compliant source devices are sent using three attributes as Facet-level entries of the Regulation-Certification-Auth-Body OBX segments: + - Regulation-Certification-Continua-Version attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'ST' + - OBX-3 = 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC + - OBX-4 = x.0.0.y.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of one of the two Regulation-Certification-Auth-Body attribute segments, and 'a' is a number indicating the Facet level of that segment. + - OBX-5 = .. + - Regulation-Certification-Continua-Certified-Device-List attribute shall be sent as an independent OBX segment and shall use the following encoding: + - OBX-2 = 'NA' + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • OBX-3 = 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC
    • • OBX-4 = x.0.0.y.b, where 'x' is a number indicating the OBX-4 of the MDS-level, 'y' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which has the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'b' is a number indicating the Facet level of that segment.
    • • OBX-5 = NA value listing the certified device, at least it shall contain one of these values: 16410 (CGM Wireless PAN), 8218 (CGM Wired PAN), 24602 (CGM LAN), 32794 (CGM BLE) or 40986 (CGM TAN)

    Regulation-Certification-Continua-Regulation-Status attribute shall be sent as an independent OBX segment and shall use the following encoding:

    • • OBX-2 = 'CWE'
    • • OBX-3 = 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC
    • • OBX-4 = x.0.0.z.a, where 'x' is a number indicating the OBX-4 of the MDS-level, 'z' is a number indicating the metric level of the Regulation-Certification-Auth-Body attribute segment which does not have the Regulation-Certification-Continua-Version attribute as a Facet entry, and 'a' is a number indicating the Facet level of that segment.
    • • OBX-5 = <0 or 1>^unregulated-device(0)

    n. If System-Type-Spec-List attribute is valued, it is sent as an independent OBX segment:

    • OBX-2 = 'CWE'
    • OBX-3 = 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC
    • OBX-5 = one or more MDC_DEV_SPEC_PROFILE values

    o. Confirm-Timeout attribute is not present.

    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|-----------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-001 | | | +| TP label | Glucose Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | CGM 1; M | CGM 3; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | MetricClassAttr 1; M | | +| | | MetricClassAttr 4; M | | +| | | MetricClassAttr 7; O | | +| | | MetricClassAttr 10; O | | +| | | MetricClassAttr 13; O | | +| | | MetricClassAttr 16; C | | +| | | NumericClassAttr 1; M | | +| | | NumericClassAttr 4; M | | +| | | NumericClassAttr 7; O | | +| | | ScannerAttr 1; M | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------|------------------| +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the CGM Numeric Object, the Metric and Numeric attributes and their respective values. | | | | +| Applicability | C_SEN_000 AND C_SEN_CGM_001 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a Continuous Glucose Monitor device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device.
    2. 2. Check in the captured message that:
      1. a. The Glucose Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Glucose Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 160212^MDC_CONC_GLU_ISF^MDC or 160184^MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD^MDC or 160188^MDC_CONC_GLU_CAPILLARY_PLASMA^MDC or 160192^MDC_CONC_GLU_VENOUS_WHOLEBLOOD^MDC or 160196^MDC_CONC_GLU_VENOUS_PLASMA^MDC or 160200^MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD^MDC or 160204^MDC_CONC_GLU_ARTERIAL_PLASMA^MDC or 160208^MDC_CONC_GLU_CONTROL^MDC or 160364^MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD^MDC or 160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Glucose Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264274^MDC_DIM_MILLI_G_PER_DL^MDC or 266866^MDC_DIM_MILLI_MOLE_PER_L^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
    • OBX-5 = Numeric Value
    • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-002 | | | +| TP label | PHD DM Status Enumeration Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | CGM 1; M | CGM 4; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 21; M | DataGuidelines 22; M | +| Test purpose | Check that:

    The presence of the attributes of the PHD DM Status Object, the Metric and Enumeration attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_CGM_001 AND C_SEN_CGM_002 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a Continuous Glucose Monitor device with a PHD DM Status object. | | | +| Test procedure | 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device.

    2. Check in the captured message that:
    1. The PHD DM Status object has sent at least one observation.
    2. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) attribute are not present
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. Each MDC code using CWE data type is encoded as:
    <refldValue>^<refldName>^<refldCodeSystem>

    Where:

    • refldValue: is a 32 bit integer (required)
    • refldName: the normative nomenclature name for the unique code point (recommended)
    • refldCodeSystem = "MDC" (required).

    d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:

    • <bitValue> = <0 or 1>
    • <bitName> is recommended to be the ASN.1 name for the bit
    • <bitPosition> is the normative position of the bit

    e. PHD DM Status object follows this OBX encoding:

    • OBX-2 = 'CWE'
      OBX-3 = 8408608^MDC_PHD_DM_DEV_STAT^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Device and the PHD DM Device status object respectively.
    • OBX-5 = Any of these values:
      <0 or 1>^device-status-undetermined(0),
      <0 or 1>^device-status-reset(1),
      <0 or 1>^device-status-error(5),
      <0 or 1>^device-status-error-mechanical(6),
      <0 or 1>^device-status-error-electronic(7),
      <0 or 1>^device-status-error-software(8),
      <0 or 1>^device-status-error-battery(9),
      <0 or 1>^device-status-service(15),
      <0 or 1>^device-status-service-time-sync-required(16),
      <0 or 1>^device-status-service-calibration-required(17),
      <0 or 1>^device-status-service-replenishment-required(18),
      <0 or 1>^device-status-battery-low(25),
      <0 or 1>^device-status-battery-depleted(26),
      <0 or 1>^device-status-battery-replaced(27),
      <0 or 1>^device-status-battery-interrupted(28)

    f. Any PM-Store, PM-Segment or Scanner attributes are not present.

    g. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | + +| | | +|--------------|--| +| Notes | | +|--------------|--| + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-003 | | | | +| TP label | CGM Status Enumeration Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | CGM 1; M | CGM 5; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | EnumClassAttr 1; M | +| | | EnumClassAttr 2; M | EnumClassAttr 3; M | EnumClassAttr 4; M | +| | | EnumClassAttr 5; O | EnumClassAttr 6; M | PM-StoreAttr; M | +| | | PM-SegmentAttr; M | ScannerAttr 1; M | ScannerAttr 2; M | +| | | ScannerAttr 3; M | ScannerAttr 4; M | | +| | | DataGuidelines 21; M | DataGuidelines 22; M | | +| Test purpose |

    Check that:

    The presence of the attributes of the CGM Status Object, the Metric and Enumeration attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_CGM_001 AND C_SEN_CGM_003 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a Continuous Glucose Monitor device with a CGM Status object.

    | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device.
    2. 2. Check in the captured message that:
      1. a. The CGM Status object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small (MDC_ATTR_METRIC_STRUCT_SMALL) attribute and Attribute-Value-Map (MDC_ATTR_ATTRIBUTE_VALUE_MAP) attribute are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. A bit flag value is encoded as <bitValue>^<bitName>(<bitPosition>), where:

    • <bitValue> = <0 or 1>
    • <bitName> is recommended to be the ASN.1 name for the bit
    • <bitPosition> is the normative position of the bit

    e. CGM Status object follows this OBX encoding:

    • OBX-2 = 'CWE'
      OBX-3 = 8418060^MDC_CGM_DEV_STAT^MDC
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Device and PHD DM Device status object respectively.
    • OBX-5 = Any of these values:
      • <0 or 1>^sensor-session-stopped(0),
      • <0 or 1>^sensor-type-incorrect(2),
      • <0 or 1>^sensor-malfunction(3),
      • <0 or 1>^device-specific-alert(4),
      • <0 or 1>^sensor-calibration-not-allowed(7),
      • <0 or 1>^sensor-calibration-not-recommended(8),
      • <0 or 1>^sensor-calibration-not-required(9),
      • <0 or 1>^sensor-temp-too-high(10),
      • <0 or 1>^sensor-temp-too-low(11),
      • <0 or 1>^sensor-result-below-patient-low(12),
      • <0 or 1>^sensor-result-above-patient-high(13),
      • <0 or 1>^sensor-low-hypo(14),
      • <0 or 1>^sensor-low-hyper(15),
      • <0 or 1>^sensor-rate-decrease-exceeded(16),
      • <0 or 1>^sensor-rate-increase-exceeded(17),
      • <0 or 1>^sensor-result-too-low(18),
      • <0 or 1>^sensor-result-too-high(19),
      • <0 or 1>^sensor-com-out-of-range(20)

    f. Any PM-Store, PM-Segment or Scanner attributes are not present.

    g. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-004 | | | | +| TP label | Sensor Calibration Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | CGM 1; M | CGM 6; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Sensor Calibration Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_CGM_001 AND C_SEN_CGM_004 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a Continuous Glucose Monitor device. | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device.
    2. 2. Check in the captured message that:
      1. a. The Sensor Calibration Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • ❑ refIdValue: is a 32 bit integer (required)
        • ❑ refIdName: the normative nomenclature name for the unique code point (recommended)
        • ❑ refIdCodeSystem = "MDC" (required).
      4. d. Sensor Calibration Numeric object follows this OBX encoding:
        • ❑ OBX-2 = 'NM'
        • ❑ OBX-3 = 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Sensor Calibration Numeric object respectively.
    • OBX-5 = Numeric value
    • OBX-6 = 264274^MDC_DIM_MILLI_G_PER_DL^MDC or 266866^MDC_DIM_MILLI_MOLE_PER_L^MDC

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-005 | | | +| TP label | Sensor Run-Time Numeric Object | | | +| Coverage | Spec | [ITU-T H.812.1] | | +| | Testable items | CGM 1; M | CGM 7; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | +| | | DataGuidelines 22; M | | +| Test purpose | Check that:

    The presence of the attributes of the Sensor Run-Time Numeric Object, the Metric and Numeric attributes and their respective values. | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_SEN_000 AND C_SEN_CGM_001 AND C_SEN_CGM_005 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a Continuous Glucose Monitor device. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device.
    2. 2. Check in the captured message that:
      1. a. The Sensor Run-Time Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Sensor Run-Time Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8418040^MDC_CGM_SENSOR_RUN_TIME^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Sensor Run-Time Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264384^MDC_DIM_HR^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | +|-----------------|----------------------------------------|-----------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-006 | | +| TP label | Glucose Sample Interval Numeric Object | | +| Coverage | Spec | [ITU-T H.812.1] | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| Testable items | CGM 1; M | CGM 8; M | MetricClassAttr 1; M | +| | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Glucose Sample Interval Numeric Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | C_SEN_000 AND C_SEN_CGM_001 AND C_SEN_CGM_006 | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a Continuous Glucose Monitor device. | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device.
    2. 2. Check in the captured message that:
      1. a. The Glucose Sample Interval Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Glucose Sample Interval Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8418044^MDC_CGM_SENSOR_SAMPLE_INTERVAL^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Glucose Sample Interval Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 264352^MDC_DIM_MIN^MDC
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    e. Any PM-Store, PM-Segment or Scanner attributes are not present.

    f. One of the timestamp attributes can be present:

    • ❑ MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
      YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • ❑ MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • ❑ MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-007 | | | | +| TP label | Glucose Trend Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | CGM 1; M | CGM 9; M | MetricClassAttr 1; M | +| | | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | +| | | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | +| | | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | +| | | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | +| | | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | +| | | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | +| | | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Glucose Trend Numeric Object, the Metric and Numeric attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_CGM_001 AND C_SEN_CGM_007 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a message with an Observation of a Continuous Glucose Monitor device. | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device.
    2. 2. Check in the captured message that:
      1. a. The Glucose Trend Numeric object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Glucose Trend Numeric object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8418008^MDC_CONC_GLU_TREND^MDC
        • OBX-4 = y.0.0.x, where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the metric level for the Glucose Trend Numeric object respectively.
        • OBX-5 = Numeric value
        • OBX-6 = 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC or 266872^MDC_DIM_MILLI_MOLE_PER_L_PER_MIN^MDC
      5. e. Any PM-Store, PM-Segment or Scanner attributes are not present.
      6. f. One of the timestamp attributes can be present:
        • MDC_ATTR_TIME_STAMP_ABS or MDC_ATTR_TIME_STAMP_BO, mapped in OBX-14 of Observation Metric-level and encoded as:
          YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
        • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
        • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
          • • OBX-5 = Numeric Value
          • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | +|-----------------|-----------------------------------------------------|----------------------|----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-008 | | | +| TP label | Patient Low/High Thresholds Compound Numeric Object | | | +| Coverage | [ITU-T H.812.1] | | | +| | Spec | | | +| | Testable items | CGM 1; M | CGM 10; M | +| | | CGM 12; M | MetricClassAttr 1; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | +| | | | MetricClassAttr 5; M | + +| | | | | | +|--------------------------|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 1; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 22; M | | | +| Test purpose | | Check that:

    The presence of the attributes of the Patient Low/High Thresholds Object, the Metric and Numeric attributes and their respective values. | | | +| Applicability | | C_SEN_000 AND C_SEN_CGM_001 AND C_SEN_CGM_008 | | | +| Other PICS | | C_SEN_GEN_003, C_SEN_GEN_004 | | | +| Initial condition | | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an observation of a Continuous Glucose Monitor device. | | | +| Test procedure | |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Patient Low/High Thresholds object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Patient Low/High Thresholds object follows this OBX encoding:
        • OBX-2 is empty
        • OBX-3 = 8418012^MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH^MDC
        • OBX-4 = y.0.x., where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the Channel-level for Patient Low/High Thresholds object respectively.
        • OBX-5 is empty
        • OBX-11 = 'X'
      5. e. Patient low threshold part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-3 = 8418013^MDC_CONC_GLU_PATIENT_THRESHOLD_LOW^MDC
    • OBX-4 = y.0.x.a, , where 'a' is a number indicating the component of the compound object
    • OBX-5 = Numeric Value
    • OBX-6 = 264274^MDC_DIM_MILLI_G_PER_DL^MDC or 266866^MDC_DIM_MILLI_MOLE_PER_L^MDC

    f. Patient high threshold part of the compound object follows this OBX encoding:

    • OBX-2 = 'NM'
    • OBX-3 = 8418014^MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH^MDC
    • OBX-4 = y.0.x.b, where 'b' is a number indicating the component of the compound object
    • OBX-5 = Numeric Value
    • OBX-6 = 264274^MDC_DIM_MILLI_G_PER_DL^MDC or 266866^MDC_DIM_MILLI_MOLE_PER_L^MDC

    g. Any PM-Store, PM-Segment or Scanner attributes are not present.

    h. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|----------|-----------|-----------|-----------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-009 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TP label | Device Hypo/Hyper Thresholds Compound Numeric Object | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Testable items |
    CGM 1; M CGM 13; M CGM 14; M
    CGM 15; M MetricClassAttr 1; M MetricClassAttr 2; M
    MetricClassAttr 3; O MetricClassAttr 4; M MetricClassAttr 5; M
    MetricClassAttr 6; O MetricClassAttr 7; O MetricClassAttr 8; O
    MetricClassAttr 9; M MetricClassAttr 10; O MetricClassAttr 11; M
    MetricClassAttr 12; O MetricClassAttr 13; O MetricClassAttr 14; O
    MetricClassAttr 15; C MetricClassAttr 16; C MetricClassAttr 17; C
    MetricClassAttr 18; O NumericClassAttr 1; M NumericClassAttr 2; M
    NumericClassAttr 3; M NumericClassAttr 4; M NumericClassAttr 5; M
    NumericClassAttr 6; M NumericClassAttr 7; O MetricRelGroup 1; M
    | | CGM 1; M | CGM 13; M | CGM 14; M | CGM 15; M | MetricClassAttr 1; M | MetricClassAttr 2; M | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | NumericClassAttr 6; M | NumericClassAttr 7; O | +| CGM 1; M | CGM 13; M | CGM 14; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CGM 15; M | MetricClassAttr 1; M | MetricClassAttr 2; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 1; M | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------|------------------| +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 22; M | | | +| Test purpose |

    Check that:

    The presence of the attributes of the Device Hypo/Hyper Thresholds Object, the Metric and Numeric attributes and their respective values.

    | | | | +| Applicability | C_SEN_000 AND C_SEN_CGM_001 AND C_SEN_CGM_009 | | | | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | | | | +| Initial condition |

    The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an Observation of a Continuous Glucose Monitor device.

    | | | | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Device Hypo/Hyper Thresholds object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refIdValue>^<refIdName>^<refIdCodeSystem>
        Where:
        • refIdValue: is a 32 bit integer (required)
        • refIdName: the normative nomenclature name for the unique code point (recommended)
        • refIdCodeSystem = "MDC" (required).
      4. d. Device Hypo/Hyper Thresholds object follows this OBX encoding:
        • OBX-2 is empty
        • OBX-3 = 8418016^MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER^MDC
        • OBX-4 = y.0.x., where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the Channel-level for Device Hypo/Hyper Thresholds object respectively.
        • OBX-5 is empty
        • OBX-11 = 'X'
      5. e. Device hypo threshold part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8418017^MDC_CONC_GLU_THRESHOLD_HYPO^MDC
        • OBX-4 = y.0.x.a., where 'a' is a number indicating the component of the compound object
        • OBX-5 = Numeric Value
        • OBX-6 = 264274^MDC_DIM_MILLI_G_PER_DL^MDC or 266866^MDC_DIM_MILLI_MOLE_PER_L^MDC
      6. f. Device hyper threshold part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8418018^MDC_CONC_GLU_THRESHOLD_HYPER^MDC
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • OBX-4 = y.0.x.b, where 'b' is a number indicating the component of the compound object
    • OBX-5 = Numeric Value
    • OBX-6 = 264274^MDC_DIM_MILLI_G_PER_DL^MDC or 266866^MDC_DIM_MILLI_MOLE_PER_L^MDC

    g. Any PM-Store, PM-Segment or Scanner attributes are not present.

    h. One of the timestamp attributes can be present:

    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +| | | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/HFS/SEN/PCD-01-DATA/CGM/BV-010 | | | | +| TP label | Glucose Rate of Charge Thresholds Compound Numeric Object | | | | +| Coverage | Spec | [ITU-T H.812.1] | | | +| | Testable items | CGM 1; M | CGM 16; M | CGM 17; M | +| | | CGM 18; M | MetricClassAttr 1; M | MetricClassAttr 2; M | +| | | MetricClassAttr 3; O | MetricClassAttr 4; M | MetricClassAttr 5; M | +| | | MetricClassAttr 6; O | MetricClassAttr 7; O | MetricClassAttr 8; O | +| | | MetricClassAttr 9; M | MetricClassAttr 10; O | MetricClassAttr 11; M | +| | | MetricClassAttr 12; O | MetricClassAttr 13; O | MetricClassAttr 14; O | +| | | MetricClassAttr 15; C | MetricClassAttr 16; C | MetricClassAttr 17; C | +| | | MetricClassAttr 18; O | NumericClassAttr 1; M | NumericClassAttr 2; M | +| | | NumericClassAttr 3; M | NumericClassAttr 4; M | NumericClassAttr 5; M | +| | | NumericClassAttr 6; M | NumericClassAttr 7; O | MetricRelGroup 1; M | +| | | PM-StoreAttr; M | PM-SegmentAttr; M | ScannerAttr 1; M | +| | | ScannerAttr 2; M | ScannerAttr 3; M | ScannerAttr 4; M | +| | | DataGuidelines 22; M | | | +| Test purpose | Check that:
    The presence of the attributes of the Glucose Rate of Charge Thresholds Object, the Metric and Numeric attributes and their respective values. | | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_SEN_000 AND C_SEN_CGM_001 AND C_SEN_CGM_010 | +| Other PICS | C_SEN_GEN_003, C_SEN_GEN_004 | +| Initial condition | The simulated HFS receiver has published a WebService and the HFS sender under test is ready to send a SOAP or hData message with an Observation of a Continuous Glucose Monitor device. | +| Test procedure |
    1. 1. Make the HFS sender under test send a HL7 message containing an Observation of a Continuous Glucose Monitor device using SOAP or hData observation upload.
    2. 2. Check in the captured message that:
      1. a. The Glucose Rate of Charge Thresholds object has sent at least one observation.
      2. b. Handle attribute (MDC_ATTR_ID_HANDLE), Metric-Spec-Small attribute (MDC_ATTR_METRIC_SPEC_SMALL), Metric-Structure-Small attribute (MDC_ATTR_METRIC_STRUCT_SMALL) and Attribute-Value-Map attribute (MDC_ATTR_ATTRIBUTE_VALUE_MAP) are not present
      3. c. Each MDC code using CWE data type is encoded as:
        <refldValue>^<refldName>^<refldCodeSystem>
        Where:
        • refldValue: is a 32 bit integer (required)
        • refldName: the normative nomenclature name for the unique code point (recommended)
        • refldCodeSystem = "MDC" (required).
      4. d. Glucose Rate of Charge Thresholds object follows this OBX encoding:
        • OBX-2 is empty
        • OBX-3 = 8391520^MDC_CONC_GLU_RATE_THRESHOLDS^MDC
        • OBX-4 = y.0.x., where 'y' and 'x' are numbers indicating the OBX-4 of the MDS-level and the Channel-level Glucose Rate of Charge Thresholds object respectively.
        • OBX-5 is empty
        • OBX-11 = 'X'
      5. e. Glucose rate of change increase threshold part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8391521^MDC_CONC_GLU_RATE_THRESHOLD_INCREASE^MDC
        • OBX-4 = y.0.x.a., where 'a' is a number indicating the component of the compound object
        • OBX-5 = Numeric Value
        • OBX-6 = 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC or 266872^MDC_DIM_MILLI_MOLE_PER_L_PER_MIN^MDC
      6. f. Glucose rate of change decrease threshold part of the compound object follows this OBX encoding:
        • OBX-2 = 'NM'
        • OBX-3 = 8391522^MDC_CONC_GLU_RATE_THRESHOLD_DECREASE^MDC
        • OBX-4 = y.0.x.b, where 'b' is a number indicating the component of the compound object
        • OBX-5 = Numeric Value
        • OBX-6 = 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC or 266872^MDC_DIM_MILLI_MOLE_PER_L_PER_MIN^MDC
      7. g. Any PM-Store, PM-Segment or Scanner attributes are not present.
      8. h. One of the timestamp attributes can be present:
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • MDC_ATTR_TIME_STAMP_ABS, mapped in OBX-14 of Observation Metric-level and encoded as: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]
    • MDC_ATTR_TIME_STAMP_REL, transmitted as a Facet of the observation:
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    • MDC_ATTR_TIME_STAMP_HI_RES, transmitted as a Facet of the observation.
      • • OBX-5 = Numeric Value
      • • OBX-18 has a timebase ID.
    | +| Pass/Fail criteria | All elements in each segment are as specified. | +| Notes | | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003): *ETSI drafting rules*. + +- [b-SOAP 1.2] W3C SOAP 1.2 (2007), *SOAP Version 1.2 (Second Edition)*. + +- [b-HFSS PICS & PIXIT] Services HFS Sender DG2016 PICS and PIXIT excel sheet v1.7. + +- [b-HFSR PICS & PIXIT] Services HFS Receiver DG2016 PICS and PIXIT excel sheet v1.7. + + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.830.8-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.830.8-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e16d7a0c7782d3a522c31a5cae00b132dcdf6371 --- /dev/null +++ b/marked/H/T-REC-H.830.8-201704-I_PDF-E/raw.md @@ -0,0 +1,564 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.830.8** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Services interface Part 8: Consent +Management: Health & Fitness Service receiver** + +Recommendation ITU-T H.830.8 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.830.8 + +# Conformance of ITU-T H.810 personal health system: Services interface Part 8: Consent Management: Health & Fitness Service receiver + +## Summary + +Recommendation ITU-T H.830.8 provides a test suite structure (TSS) and the test purposes (TP) for Consent Management through the Health & Fitness Service (HFS) receiver in the Services interface based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.830.8 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 8: Consent Management. HFS Receiver (Version 1.4, 2017-03-14), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.838 | 2015-01-13 | 16 | 11.1002/1000/12256 | +| 1.0 | ITU-T H.830.8 | 2015-01-13 | 16 | 11.1002/1000/12594 | +| 2.0 | ITU-T H.830.8 | 2016-07-14 | 16 | 11.1002/1000/12928 | +| 3.0 | ITU-T H.830.8 | 2017-04-13 | 16 | 11.1002/1000/13209 | + +## Keywords + +Conformance testing, Consent Management, Continua Design Guidelines, e-health, Health & Fitness Service receiver, ITU-T H.810, personal connected health devices, Services Interface. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|----------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Test suite structure (TSS) ..... | 5 | +| 7 | Electronic attachment ..... | 7 | +| Annex A | Test purposes ..... | 8 | +| A.1 | TP definition conventions..... | 8 | +| A.2 | Subgroup 2.5.1: HFS XDR Transaction (TRANS) ..... | 9 | +| A.3 | Subgroup 2.5.2: HFS Service Validation (SER) ..... | 10 | +| | Bibliography..... | 13 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 8: Consent Management. HFS Receiver (Version 1.4, 2017-03-14), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2012-10-05 | Initial release for Test Tool DG2011 based on the requirements in [b-CDG 2011]. | +| 1.0 | 2013-05-24 | Initial release for Test Tool DG2012. This is the same version as "TSS&TP_DG2012_WAN_PART_8 (REC CM) v1.0.doc" because new features included in [b-CDG 2012] do not affect the test procedures specified in this document. | +| 1.0 | 2014-01-24 | Initial release for Test Tool DG2013. This is the same version as "TSS&TP_DG2012_WAN_PART_8 (REC CM) v1.0.doc" because new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013] do not affect the test procedures specified in this document. | +| 1.1 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_WAN_PART_8 (REC CM)_v1.0.doc" as baseline and it adds new features included in Documentation Enhancements:
    • "Other PICS" row added
    | +| 1.2 | 2015-07-01 | Initial release for Test Tool DG2015:
    • Test suite structure and applicability modified
    | +| 1.3 | 2016-09-20 | Initial release for Test Tool DG2016. It implements changes according to [ITU-T H.810 (2016)]/[b-CDG 2016] (Iris + Errata) refreshments. | +| 1.4 | 2017-03-14 | Editorial: added insulin pump and continuous glucose monitor specializations to the TSS list in clause 6. | + +## Recommendation ITU-T H.830.8 + +## Conformance of ITU-T H.810 personal health system: Services interface Part 8: Consent Management: Health & Fitness Service receiver + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Services interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Services interface have been divided into the parts specified below. This Recommendation covers Part 8. + +- Part 1: Web services interoperability Health & Fitness Service sender +- Part 2: Web services interoperability Health & Fitness Service receiver +- Part 3: SOAP/ATNA. Health & Fitness Service sender +- Part 4: SOAP/ATNA. Health & Fitness Service receiver +- Part 5: PCD-01 HL7 messages. Health & Fitness Service sender +- Part 6: PCD-01 HL7 messages. Health & Fitness Service receiver +- Part 7: Consent Management. Health & Fitness Service sender +- **Part 8: Consent Management. Health & Fitness Service receiver** +- Part 9: hData Observation Upload. Health & Fitness Service sender +- Part 10: hData Observation Upload. Health & Fitness Service receiver +- Part 11: Questionnaires. Health & Fitness Service sender +- Part 12: Questionnaires. Health & Fitness Service receiver + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. + +[ITU-T H.812] Recommendation ITU-T H.812 (2016), *Interoperability design guidelines for personal health systems: Services interface: Common certified capability class*. + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- [ITU-T H.812.1] Recommendation ITU-T H.812.1 (2016), *Interoperability design guidelines for personal health systems: Services interface: Observation upload certified capability class.* +- [ITU-T H.812.2] Recommendation ITU-T H.812.2 (2016), *Interoperability design guidelines for personal health systems: Services interface: Questionnaires certified capability class.* +- [ITU-T H.812.3] Recommendation ITU-T H.812.3 (2016), *Interoperability design guidelines for personal health systems: Services interface: Capability exchange certified capability class.* +- [ITU-T H.812.4] Recommendation ITU-T H.812.4 (2016), *Interoperability design guidelines for personal health systems: Services interface: Authenticated persistent session certified capability class.* +- [IHE ITI TF-2] IHE ITI TF 2 (2010), Integrating the Healthcare Enterprise, *IHE IT Infrastructure Technical Framework, Volume 2 (ITI TF-2)*, Revision 7.0. It comprises three sub-volumes: 2a (Transactions Part A), 2b (Transactions Part B) and 2x (Appendices). +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_TF\\_Rev7-0\\_Vol2a\\_FT\\_2010-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2a_FT_2010-08-10.pdf) +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_TF\\_Rev7-0\\_Vol2b\\_FT\\_2010-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2b_FT_2010-08-10.pdf) +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_TF\\_Rev7-0\\_Vol2x\\_FT\\_2010-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2x_FT_2010-08-10.pdf) + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +None. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------------------------| +| ATNA | Audit Trail and Node Authentication | +| ATS | Abstract Test Suite | +| CDA | Clinical Document Architecture | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| ebXML | electronic business using extensible Markup Language | +| EHR | Electronic Health Record | +| HFS | Health & Fitness Service | +| HFSS | Health & Fitness Service Sender | +| HFSR | Health & Fitness Service Receiver | + +| | | +|--------|-------------------------------------------------------| +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| MTOM | Message Transmission Optimization Mechanism | +| NFC | Near Field Communication | +| PCD | Patient Care Device | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| S/MIME | Secure/Multipurpose Internet Mail Extensions | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| URI | Uniform Resource Identifier | +| USB | Universal Serial Bus | +| WAN | Wide Area Network | +| WDM | Windows Driver Model | +| WS | Web Service | +| WSDL | Web Service Description Language | +| XDR | cross-enterprise Document Reliable interchange | +| XDS.b | cross-enterprise Document Sharing-b | +| XML | extensible Markup Language | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +– SHALL is equivalent to 'must' or 'it is required to'. + +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with | 1.5 | + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|-------------|---------------|---------|-----------------------------------------------------------------------------------------------------------------|-------------| +| | | | maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Services interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 2.5.1 and 2.5.2 (shown in bold). + +- Group 1: HFS sender (HFSS) + - Group 1.1: Web services interoperability (WSI) + - Subgroup 1.1.1: Basic profile (BP) + - Subgroup 1.1.2: Basic security profile (BSP) + - Subgroup 1.1.3: Reliable messaging (RM) + - Group 1.2: SOAP (SOAP) + - Subgroup 1.2.1: SOAP headers (HEAD) + - Group 1.3: Audit (ATNA) + - Subgroup 1.3.1: General (GEN) + - Subgroup 1.3.2: PCD-01 (PCD-01) + - Subgroup 1.3.3: Consent Management (CM) + - Group 1.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 1.4.1: General (GEN) + - Subgroup 1.4.2: Design guidelines (DG) + - Subgroup 1.4.3: Pulse oximeter (PO) + - Subgroup 1.4.4: Blood pressure monitor (BPM) + - Subgroup 1.4.5: Thermometer (TH) + - Subgroup 1.4.6: Weighing scales (WEG) + - Subgroup 1.4.7: Glucose meter (GL) + - Subgroup 1.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 1.4.9: Strength fitness equipment (ST) + - Subgroup 1.4.10: Independent living activity hub (HUB) + - Subgroup 1.4.11: Adherence monitor (AM) + - Subgroup 1.4.12: Peak expiratory flow monitor (PF) + - Subgroup 1.4.13: Body composition analyser (BCA) + - Subgroup 1.4.14: Basic electrocardiograph (ECG) + - Subgroup 1.4.15: International normalized ratio (INR) + - Subgroup 1.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.4.17: Insulin pump (IP) + +- Subgroup 1.4.18: Continuous glucose monitor (CGM) +- Group 1.5: Consent Management (CM) + - Subgroup 1.5.1: HFS XDR transaction (TRANS) + - Subgroup 1.5.2: HFS metadata validation (META) + - Subgroup 1.5.3: HFS consent directive validation (CDV) +- Group 1.6: hData Observation Upload (HDATA) + - Subgroup 1.6.1: General (GEN) +- Group 1.7: Questionnaires (QUE) + - Subgroup 1.7.1: General (GEN) + - Subgroup 1.7.2: CDA validation (CDA) + +###### – Group 2: HFS receiver (HFSR) + +- Group 2.1: Web service interoperability (WSI) + - Subgroup 2.1.1: Basic profile (BP) + - Subgroup 2.1.2: Basic security profile (BSP) + - Subgroup 2.1.3: Reliable messaging (RM) +- Group 2.2: SOAP (SOAP) + - Subgroup 2.2.1: SOAP headers (HEAD) +- Group 2.3: Audit (ATNA) + - Subgroup 2.3.1: General (GEN) + - Subgroup 2.3.2: PCD-01 (PCD-01) + - Subgroup 2.3.3: Consent Management (CM) +- Group 2.4: PCD-01 HL7 messages (PCD-01-DATA) + - Subgroup 2.4.1: General (GEN) + - Subgroup 2.4.2: Design guidelines (DG) + - Subgroup 2.4.3: Pulse oximeter (PO) + - Subgroup 2.4.4: Blood pressure monitor (BPM) + - Subgroup 2.4.5: Thermometer (TH) + - Subgroup 2.4.6: Weighing scales (WEG) + - Subgroup 2.4.7: Glucose meter (GL) + - Subgroup 2.4.8: Cardiovascular fitness and activity monitor (CV) + - Subgroup 2.4.9: Strength fitness equipment (ST) + - Subgroup 2.4.10: Independent living activity hub (HUB) + - Subgroup 2.4.11: Adherence monitor (AM) + - Subgroup 2.4.12: Peak expiratory flow monitor (PF) + - Subgroup 2.4.13: Body composition analyser (BCA) + - Subgroup 2.4.14: Basic electrocardiograph (ECG) + - Subgroup 2.4.15: International normalized ratio (INR) + - Subgroup 2.4.16: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.4.17: Insulin pump (IP) + - Subgroup 2.4.18: Continuous glucose monitor (CGM) +- Group 2.5: Consent Management (CM) + +- **Subgroup 2.5.1: HFS XDR transaction (TRANS)** + - **Subgroup 2.5.2: HFS service validation (SER)** +- Group 2.6: hData Observation Upload (HDATA) + - Subgroup 2.6.1: General (GEN) + - Subgroup 2.6.2: hData record format (HRF) +- Group 2.7: Questionnaires (QUE) + - Subgroup 2.7.1: General (GEN) + - Subgroup 2.7.2: CDA validation (CDA) + - Subgroup 2.7.3: hData record format (HRF) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C2", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - HFS: Health & Fitness Services Interface + - : This is the device under test. + - SEN: HFS sender + - REC: HFS receiver + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose (TP). +- **TP label:** This is the title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP are included. + - Testable Item: This contains testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 2.5.1: HFS XDR Transaction (TRANS) + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------------------------------------------------| +| TP Id | TP/HFS/REC/CM/TRANS/BV-000 | | | +| TP label | Provide and Register Document Set-b Transaction Response | | | +| Coverage | Spec | [ITU-T H.812] | | +| | Testable items | ConsentReceiver1; M | | +| | Spec | [IHE ITI TF-2], Volume 2b | | +| | Testable items | ProvideResponse1; M
    ProvideProtocol10; M | ProvideResponse2; M
    ProvideProtocol11; M
    ProvideProtocol2; M | +| Test purpose |

    Check that:

    Consent Enabled HFS Observation receiver shall be able to receive, HL7 CDA R2 Consent Directives consent document(s)

    [AND]

    The Document Repository shall send a Provide and Register Document Set-b Response when the processing of a Provide and Register Document Set-b Request is complete

    [AND]

    The Provide and Register Document Set-b Response message shall carry the status of the requested operation and an error message if the requested operation failed.

    [AND]

    The Provide and Register Document Set-b transaction shall use SOAP12 and MTOM with XOP encoding.

    [AND]

    The Document Repository shall accept documents in a Provide and Register Document Set-b transaction in MTOM/XOP format.

    [AND]

    The response message shall use MTOM/XOP format

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_002 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The receiver under test has published the document recipient service and is ready to receive a "Provide and Register Document Set-b Request" sent by the simulated HFS sender. | | | +| Test procedure |
    1. The simulated HFS sender sends a "Provide and Register Document Set-b Request" with a clinical document architecture (CDA) using MTOM/XOP.
    2. The receiver under test responds with a "Provide and Register Document Set-b Response" with status = "urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success" using SOAP12 [b-SOAP 1.2].
    | | | +| Pass/Fail criteria | All steps are as specified within the test procedure above. | | | +| Notes | | | | + +### A.3 Subgroup 2.5.2: HFS Service Validation (SER) + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---------------------| +| TP Id | TP/HFS/REC/CM/SER/BV-000 | | | +| TP label | Service WSDL | | | +| Coverage | Spec | [IHE ITI TF-2], Volume 2b | | +| | Testable items | ProvideProtocol3; M | ProvideProtocol4; M | +| | | ProvideProtocol6; M | ProvideProtocol7; M | +| | | | ProvideProtocol5; M | +| | | | ProvideProtocol8; M | +| Test purpose |

    Check that:

    The following types shall be imported (xsd:import) in the /definitions/types section of the WSDL:

    • - namespace="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0", schema="rs.xsd"
    • - namespace="urn:ihe:iti:xds-b:2007", schemaLocation="IHEXDS.xsd"

    [AND]

    The /definitions/message/part/@element attribute of the Provide and Register Document Set-b Request message of the WSDL shall be defined as "ihe:ProvideAndRegisterDocumentSetRequest"

    [AND]

    The /definitions/message/part/@element attribute of the Provide and Register Document Set-b Response message of the WSDL shall be defined as "ihe:RegistryResponse"

    [AND]

    The /definitions/portType/operation/input/@wsaw:Action attribute for the Provide and Register Document Set-b Request message of the WSDL shall be defined as "urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b"

    [AND]

    The /definitions/portType/operation/output/@wsaw:Action attribute for the Provide and Register Document Set-b Response message of the WSDL shall be defined as "urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse"

    [AND]

    The /definitions/portType/operation/soap12:operation/@soapAction attribute of the WSDL shall be defined as "urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b"

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_002 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The receiver under test has published its WSDL description for a Consent Management service | | | +| Test procedure |
    1. 1 Look up the WSDL description using the corresponding URL given by the receiver under test (I_REC_CM_001). Check that:
      1. a. There are two xsd:import elements in the definitions/types section for which the namespaces are:
        • o namespace="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
        • o namespace="urn:ihe:iti:xds-b:2007"
      2. b. /definitions/message/part/@element = "ihe:ProvideAndRegisterDocumentSetRequest" for the "Provide and Register Document Set-b Request"
      3. c. /definitions/message/part/@element = "ihe:RegistryResponse" for the "Provide and Register Document Set-b Response"
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. /definitions/portType/operation/input/@wsaw:Action = "urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b" for the "Provide and Register Document Set-b Request"

    e. /definitions/portType/operation/input/@wsaw:Action = "urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse" for the "Provide and Register Document Set-b Response"

    f. /definitions/portType/operation/soap12:operation/@soapAction = "urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b"

    | +| Pass/Fail criteria | All steps are as specified within the test procedure above. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------| +| TP Id | TP/HFS/REC/CM/SER/BV-001 | | | +| TP label | Service Metadata Validation | | | +| Coverage | Spec | [IHE ITI TF-2], Volume 2b | | +| | Testable items | ProvideRecipient3; M | ProvideRecipient5; O      ProvideRecipient7; C | +| Test purpose |

    Check that:

    A Document Repository shall validate the following metadata elements received as part of a Provide and Register transaction:

    • - XDSDocumentEntry.uniqueId
    • - XDSSubmissionSet.sourceId

    [AND]

    If a XDSSubmissionSet.sourceId element is received, a Document Repository may choose to accept submissions only from certain sources and use this field to perform the filtering.

    [AND]

    If the attributes "hash" and "size" are received in a Provide and Register Document Set-b [ITI-41] transaction, they shall be ignored.

    | | | +| Applicability | C_REC_000 AND C_REC_GEN_002 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The receiver under test has published the document recipient service and is ready to receive a "Provide and Register Document Set-b Request" sent by the simulated sender. | | | +| Test procedure |
    1. 1 The Simulated HFS sender sends a "Provide and Register Document Set-b Request" message including XDSSubmissionSet.sourceId, XDSDocumentEntry.uniqueId, XDSDocumentEntry.hash and XDSDocumentEntry.size elements with correct values.
    2. 2 The HFS receiver under test responds with a "Provide and Register Document Set-b Response" with status Success
    3. 3 The simulated HFS sender sends a "Provide and Register Document Set-b Request" message including an XDSDocumentEntry.hash element with a wrong value
    4. 4 The receiver under test responds with a "Provide and Register Document Set-b Response" with status Success
    5. 5 The simulated HFS sender sends a "Provide and Register Document Set-b Request" message including an XDSDocumentEntry.size element with a wrong value
    6. 6 The receiver under test responds with a "Provide and Register Document Set-b Response" with status Success
    7. 7 The simulated HFS sender sends a "Provide and Register Document Set-b Request" message including a different XDSSubmissionSet.sourceId element
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------| +| | 8 The receiver under test may accept or may not accept the message. | +| Pass/Fail criteria | All steps are as specified within the test procedure above. | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------| +| TP Id | TP/HFS/REC/CM/SER/BV-002 | | | +| TP label | Multiple Documents and Errors | | | +| Coverage | Spec | [IHE ITI TF-2], Volume 2b | | +| | Testable items | ProvideReqActions3; M | ProvideRecipient1; M | +| Test purpose | Check that:

    A detected failure it shall result in an error message being returned to the Document Source thus terminating this transaction.

    [AND]

    A Document Repository shall be capable of accepting submissions containing multiple documents. | | | +| Applicability | C_REC_000 AND C_REC_GEN_002 AND C_REC_GEN_003 | | | +| Other PICS | | | | +| Initial condition | The receiver under test has published the document recipient service and is ready to receive a "Provide and Register Document Set-b Request" sent by the simulated sender. | | | +| Test procedure | 1 The simulated HFS sender sends a "Provide and Register Document Set-b Request" with two documents using MTOM/XOP

    2 The receiver under test responds with a "Provide and Register Document Set-b Response" with status = "urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success"

    3 The simulated HFS sender sends a "Provide and Register Document Set-b Request" without attaching a document using MTOM/XOP

    4 The receiver under test responds with a "Provide and Register Document Set-b Response" with status = "urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure". | | | +| Pass/Fail criteria | All steps are as specified within the test procedure above. | | | +| Notes | | | | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline" *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003): *ETSI drafting rules*. + +- [b-HL7 CDA IG] Health Level Seven (2011), Health Level Seven, *HL7 Implementation Guide for Clinical Document Architecture, Release 2: Consent Directives, Release 1, HL7 Draft Standard for Trial Use*. +[http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2\\_IG%20\\_CONSENTPDIR\\_DSTU\\_2011JAN.pdf](http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2_IG%20_CONSENTPDIR_DSTU_2011JAN.pdf) +- [b-HFSR PICS & PIXIT] Services HFS Receiver DG2016 PICS and PIXIT excel sheet v1.7. + +- [b-HFSS PICS & PIXIT] Services HFS Sender DG2016 PICS and PIXIT excel sheet v1.7. + +- [b-SOAP 1.2] W3C SOAP 1.2 (2007), SOAP Version 1.2 (Second Edition). + + + + + + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.840-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.840-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..21a8f053592a31737f38fd01de2e9fc070183e8b --- /dev/null +++ b/marked/H/T-REC-H.840-201704-I_PDF-E/raw.md @@ -0,0 +1,746 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.840** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface: USB +host** + +Recommendation ITU-T H.840 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.840 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface: USB host + +## Summary + +Recommendation ITU-T H.840 provides a test suite structure (TSS) and the test purposes (TP) for the universal serial bus (USB) host in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.840 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface: USB Host (Version 1.4, 2017-03-14), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.840 | 2015-01-13 | 16 | 11.1002/1000/12257 | +| 2.0 | ITU-T H.840 | 2016-07-14 | 16 | 11.1002/1000/12933 | +| 3.0 | ITU-T H.840 | 2017-04-13 | 16 | 11.1002/1000/13214 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, touch area network, USB host. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-----|------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Test suite structure (TSS) ..... | 5 | +| 7 | Electronic attachment ..... | 5 | +| | Annex A Test purposes ..... | 6 | +| A.1 | TP definition conventions..... | 6 | +| A.2 | Group 1: Descriptors (DESC) ..... | 7 | +| A.3 | Subgroup 2.1: Metadata message preamble feature (FEAT) ..... | 13 | +| A.4 | Subgroup 2.2: Get Data Status before setting / clearing (GDS)..... | 14 | +| A.5 | Subgroup 2.3: Set/Clear Metadata message preamble feature (SC)..... | 15 | +| A.6 | Subgroup 2.4: Metadata message preamble transfer (TRANS) ..... | 18 | +| A.7 | Subgroup 2.5: Metadata message preamble feature error conditions (ERR) ..... | 20 | +| | Bibliography..... | 24 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface: USB Host (Version 1.4, 2017-03-14), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.1 | 2012-10-05 | Initial release for Test Tool DG2011. It is the same version as "TSS&TP_1.5_USBHost_v1.1.pdf" because new features included in [b-CDG 2011] do not affect the test procedures specified in this document. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. It is the same version as "TSS&TP_DG2011_USBHost_v1.1.pdf" because new features included in [b-CDG 2012] do not affect the test procedures specified in this document. | +| 1.1 | 2014-01-24 | Initial release for Test Tool DG2013. It is the same version as "TSS&TP_DG2012_USBHost_v1.1.pdf" because the new features included in [b-CDG 2013] do not affect the test procedures specified in this document. | +| 1.2 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_USBHost_v1.1.doc" as a baseline and adds new features included in Documentation Enhancements:
    • "Other PICS" row has been added
    | +| 1.2 | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_USBHost_v1.2.pdf" because new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015] do not affect to Test Procedures specified in this document. | +| 1.3 | 2016-09-20 | Initial release for Test Tool DG2016. It implements changes according to [ITU-T H.810 (2016)]/[b-CDG 2016] (Iris + Errata) refreshments. | +| 1.4 | 2017-03-14 | Editorial - missing nomenclature refreshments. | + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface: USB host + +## 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the USB host based on the requirements defined in the USB Personal Healthcare Device Class specification that has been selected for use in the Personal Health Device (PHD) interface of the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [ISO/IEEE 11073-10419] ISO/IEEE 11073-10419:2016, *Health informatics - Personal health device communication - Part 10419: Device specialization - Insulin pump*. + +- [ISO/IEEE 11073-10424] ISO/IEEE 11073-10424:2016, *Health informatics --Personal health device communication - Part 10424: Device specialization - Sleep apnoea breathing therapy equipment (SABTE)*. + +- [ISO/IEEE 11073-10425] ISO/IEEE 11073-10425:2016, *Health informatics - Personal health device communication - Part 10425: Device specialization - Continuous glucose monitor (CGM)*. + +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd. 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073- + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +20601:2016/Cor.1:2016. + + with + + +| | | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [USB DevClass] | USB Implementers Forum (2007-11), Universal Serial Bus Device Class Definition for Personal Healthcare Devices , Release 1.0, plus Errata (15 February 2008), Personal Healthcare section.
    http://www.usb.org/developers/docs/devclass_docs/Personal_Healthcare_1.zip | +| [USB 2.0] | USB Implementers Forum (2000), Universal Serial Bus Specification 2.0 .
    http://www.usb.org/developers/docs/usb20_docs/usb_20_112614.zip | + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|------------------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CESL | Continua Enabling Software Library | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| PAN | Personal Area Network | +| PCT | Protocol Conformance Testing | +| PCO | Point of Control and Observation | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | + +| | | +|-------|-------------------------------------------------------| +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SDP | Service Discovery Protocol | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SOAP | Simple Object Access Protocol | +| SUT | System Under Test | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +## 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|--------------------|------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure (TSS) + +The test purposes (TPs) of this Recommendation are found in Annex A and have been divided into two main groups: + +- Group 1: Descriptors (DESC) +- Group 2: Metadata message preamble (MDMP) + - Subgroup 2.1: Metadata message preamble feature (FEAT) + - Subgroup 2.2: Get data status before setting/clearing metadata message preamble feature (GDS) + - Subgroup 2.3: Set/Clear Metadata message preamble feature (SC) + - Subgroup 2.4: Metadata message preamble transfer (TRANS) + - Subgroup 2.5: Metadata message preamble feature error conditions (ERR) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PHDC: USB host personal health device class + - : This is the device under test. + - HOS: PHDC host + - DEV: PHDC device (not used because it is out of the scope of the developed test tool) + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable Item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Group 1: Descriptors (DESC) + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|--| +| TP Id | TP/PHDC/HOS/DESC/BV-000_A | | | | +| TP label | Device class in interface descriptor | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | DeviceDesc 1; M | | | +| Test purpose | Check that:
    USB Host acknowledges the simulated device descriptors
    [AND]
    It recognizes PHDC device class when it is set in device descriptor | | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | +| Test procedure |
    1. Connect the host under test and simulated device, then the enumeration process shall start automatically. During this process, the host will issue a GetDescriptor() request to the test tool device. On the test tool device the bDeviceClass field of the device descriptor is set to 00h and bInterfaceClass of the interface descriptor is set to 0Fh.
    2. The simulated device issues an "Association Request" message to the host under test.
    3. The host under test shall reply with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message.
    | | | | +| Pass/Fail criteria | In step 3, the host under test replies with an "Association Response"(accepted, accepted-unknown-config or rejected) or an "Association Abort" message. | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|--| +| TP Id | TP/PHDC/HOS/DESC/BV-000_B | | | | +| TP label | Device class in device descriptor | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | DeviceDesc 1; M | | | +| Test purpose | Check that:
    USB Host acknowledges the simulated device descriptors
    [AND]
    It recognizes PHDC device class when it is set in interface descriptor | | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Connect the host under test and simulated device, then the enumeration process shall start automatically. During this process, the host will issue a GetDescriptor() request to the test tool device. On the test tool device the bDeviceClass field of the device descriptor is set to 0Fh and bInterfaceClass of the interface descriptor is set to 00h.
    2. 2. The simulated device issues an "Association Request" message to the host under test.
    3. 3. The host under test shall reply with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message.
    | +| Pass/Fail criteria | In step 3, the host under test replies with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message. | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------| +| TP Id | TP/PHDC/HOS/DESC/BV-001_A | | | +| TP label | Verify class-defined USB descriptors (no PHDC metadata descriptor, data format code defined by vendor) | | | +| Coverage | Spec | [USB DevClass] | | +| | Testable items | ClassFunDesc 1; M | ClassFunDesc 2; M | +| | | ClassFunDesc 4; M | ClassFunDesc 6; M | +| | | ClassFunExtDesc 3; M | ClassFunExtDesc 4; M | +| | | ClassFunExtDesc 7; M | ClassFunExtDesc 8; M | +| | | MetaDataDesc 1; M | MetaDataDesc 2; M | +| Test purpose | Check that:
    USB Host acknowledges the simulated device descriptors
    [AND]
    It recognizes PHDC device class if PHDC Meta-Data Descriptor is not sent and data format code is defined by vendor. | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | +| Test procedure |
    1. 1. Connect the host under test and simulated device, then the enumeration process shall start automatically. During this process, the host will issue a GetDescriptor() request to the test tool device. On the test tool device the PHDC Metadata descriptor will not be included because it is optional and the bPHDCDataCode field of the PHDC class function descriptor will be set to 01h (PHDC_VENDOR).
    2. 2. The test tool shows a pop-up message asking the test operator to verify that the host continues to function normally (i.e., keyboard and mouse still function, system still up and running).
    | | | +| Pass/Fail criteria | In step 2, the host does not shut down or stop accepting input from other USB devices (keyboard, mouse). | | | +| Notes | | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|----------------------| +| TP Id | TP/PHDC/HOS/DESC/BV-001_B | | | | +| TP label | Verify class-defined USB descriptors (PHDC Metadata descriptor, data format code following ISO/IEEE 11073-20601) | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | ClassFunDesc 1; M | ClassFunDesc 2; M | ClassFunDesc 3; M | +| | | ClassFunDesc 4; M | ClassFunDesc 6; M | ClassFunExtDesc 1; M | +| | | ClassFunExtDesc 3; M | ClassFunExtDesc 4; M | ClassFunExtDesc 5; M | +| | | ClassFunExtDesc 7; M | ClassFunExtDesc 8; M | ClassFunExtDesc 9; M | +| | | MetaDataDesc 1; M | MetaDataDesc 2; M | MetaDataDesc 3; M | +| | | MetaDataDesc 4; M | | | +| Test purpose | Check that:
    USB Host acknowledges the simulated device descriptors
    [AND]
    It recognizes PHDC device class if PHDC Meta-Data Descriptor is sent and data format code follows ISO/IEEE 11073-20601. | | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | +| Test procedure |
    1. Connect the host under test and simulated device, then the enumeration process shall start automatically. During this process, the host will issue a GetDescriptor() request to the test tool device. On the test tool device the PHDC Metadata descriptor will be included because it is optional and the bPHDCDataCode field of the PHDC class function descriptor will be set to 02h (PHDC_11073_20601).
    2. The simulated device issues an "Association Request" message to the host under test.
    3. The host under test shall reply with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message.
    | | | | +| Pass/Fail criteria | In step 3, the host under test replies with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message. | | | | +| Notes | | | | | + +| | | | | | +|-----------------|---------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|----------------------| +| TP Id | TP/PHDC/HOS/DESC/BV-001_C | | | | +| TP label | Verify class-defined USB descriptors (no PHDC Metadata descriptor, data format code following ISO/IEEE 11073-20601) | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | ClassFunDesc 1; M | ClassFunDesc 2; M | ClassFunDesc 3; M | +| | | ClassFunDesc 4; M | ClassFunDesc 6; M | ClassFunExtDesc 1; M | +| | | ClassFunExtDesc 3; M | ClassFunExtDesc 4; M | ClassFunExtDesc 5; M | +| | | ClassFunExtDesc 7; M | ClassFunExtDesc 8; M | ClassFunExtDesc 9; M | +| | | MetaDataDesc 1; M | MetaDataDesc 2; M | MetaDataDesc 3; M | +| | | MetaDataDesc 4; M | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    USB Host acknowledges the simulated device descriptors
    [AND]
    It recognizes PHDC device class if PHDC Meta-Data Descriptor is not sent and data format code follows ISO/IEEE 11073-20601. | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | +| Other PICS | | +| Initial condition | The simulated device is plugged into the host under test. | +| Test procedure |
    1. 1. Connect the host under test and simulated device, then the enumeration process shall start automatically. During this process, the host will issue a GetDescriptor() request to the test tool device. On the test tool device the PHDC Metadata descriptor will not be included because it is optional and the bPHDCDataCode field of the PHDC class function descriptor will be set to 02h (PHDC_11073_20601).
    2. 2. The simulated device issues an "Association Request" message to the host under test.
    3. 3. The host under test shall reply with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message.
    | +| Pass/Fail criteria | In step 3, the host under test replies with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message. | +| Notes | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--------------| +| TP Id | TP/PHDC/HOS/DESC/BV-002 | | | +| TP label | Verify Valid bQoSEncoding Version | | | +| Coverage | Spec | [USB DevClass] | | +| | Testable items | QoSDesc 1; M | QoSDesc 2; M | +| | | QoSDesc 4; M | QoSDesc 5; M | +| | | QoSDesc 7; M | QoSDesc 3; M | +| Test purpose | Check that:
    If a USB Host implementing 01h QoS information encoding receives a bQoSEncodingVersion that is not 01h, then it ignores the descriptor. | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | +| Test procedure |
    1. 1. Connect the host under test and simulated device, then the enumeration process shall start automatically. During this process, the host will issue a GetDescriptor() request to the test tool device. On the test tool device there will be one QoS descriptor with bQoSEncodingVersion=02h. The host under test shall ignore the descriptor.
    2. 2. The simulated device issues an "Association Request" message to the host under test.
    3. 3. The host under test shall reply with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message.
    | | | +| Pass/Fail criteria | In step 3, the host under test replies with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message.

    If there are issues when running this test procedure, see bugzilla 55 and potentially issue a waiver. http://continua.plugfest.com/show_bug.cgi?id=55 . | | | +| Notes | | | | + +| | | +|-----------------|----------------------------------------| +| TP Id | TP/PHDC/HOS/DESC/BV-003 | +| TP label | Verify communication on bulk endpoints | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------|-----------| +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | Arch 1; M | Arch 2; M | Arch 4; M | +| | | Arch 5; M | | | +| Test purpose | Check that:
    USB Host and simulated device send information over endpoints declared in endpoint descriptors. | | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | +| Test procedure |
    1. 1. Connect the host under test and simulated device, then the enumeration process shall start automatically. During this process, the host will issue a GetDescriptor() request to the test tool device. On the test tool device there will be 3 endpoint descriptors: BULK IN, BULK OUT and INTERRUPT IN.
    2. 2. The simulated device issues an "Association Request" message to the host under test via the BULK IN endpoint.
    3. 3. The host under test shall reply with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message over the BULK OUT endpoint.
    | | | | +| Pass/Fail criteria | In step 3, the host under test replies with an " Association Response " (accepted, accepted-unknown-config or rejected) or an " Association Abort " in BULK OUT endpoint number. | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/PHDC/HOS/DESC/BV-004 | | | | +| TP label | PHD with two interfaces. Connect it after PHG application is running and USB Transport is activated | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | DeviceDesc 2; M | | | +| | Spec | [b-CDG 2012] | | | +| | Testable items | Wired_PAN_USB_USB_2.0 | | | +| | Spec | [USB 2.0] | | | +| | Testable items | USB 2.0 ch 9.2.1 | | | +| Test purpose | Check that:
    The Personal Health Gateway (PHG) under test recognizes PHDC device class if simulated Personal Health Device (PHD) has two interfaces: PHDC and another one (such HID) and the simulated PHD is connected to the PHG under test after the PHG under test application is running and USB Transport is activated | | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test application has just been restarted (computer rebooted or application exited and opened) and USB Transport is activated.
    The simulated device is *not* plugged into the PHG under test. | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Connect the host under test and simulated device, then the enumeration process shall start automatically. During this process, the host will issue a GetDescriptor() request to the test tool device. On the test tool device the bNumInterfaces field of the configuration descriptor is set to 02h; two interface descriptors will be sent: PHDC and HID, where the HID interface is sent first.
    2. 2. The simulated device issues an "Association Request" message to the host under test.
    3. 3. The host under test shall reply with an "Association Response" message if it recognizes the PHDC interface.
    | +| Pass/Fail criteria | In step 3, the host under test replies with an "Association Response" or another valid response to an "Association Request" message. | +| Notes | Due to CESL restrictions, this test case has to be executed manually using a real PHD with two interfaces. | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/PHDC/HOS/DESC/BV-005 | | | | +| TP label | PHD with two interfaces. Connect it before the PHG application is running and USB Transport is activated | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | DeviceDesc 2; M | | | +| | Spec | [b-CDG 2012] | | | +| | Testable items | Wired_PAN_USB_USB_2.0 | | | +| | Spec | [USB 2.0] | | | +| | Testable items | USB 2.0 ch 9.2.1 | | | +| Test purpose |

    Check that:

    The PHG under test recognizes a PHDC device when the simulated PHD has two interfaces: PHDC and another one (such HID) and the simulated PHD is connected to the PHG under test before the PHG under test application is running and USB Transport is activated

    | | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition |

    The PHG under test application is stopped and USB Transport is deactivated.

    The simulated device is *not* plugged into the PHG under test.

    | | | | +| Test procedure |
    1. 1. Plug simulated device into the PHG under test. The enumeration process should start automatically.
      The host should issue a GetDescriptor() request to the test tool device. On the test tool device the bNumInterfaces field of configuration descriptor is set to 02h; two interface descriptors will be sent: PHDC and HID, where the HID interface is sent first.
    2. 2. Start the PHG under test application and activate USB Transport.
    3. 3. The simulated device issues an "Association Request" message to the host under test.
    4. 4. The host under test shall reply with an "Association Response" message if it recognizes the PHDC interface.
    | | | | +| Pass/Fail criteria | In step 4, the host under test replies with an "Association Response" or another valid response to an "Association Request" message. | | | | +| Notes | Due to CESL restrictions, this test case has to be executed manually using a real PHD with two interfaces. | | | | + +## A.3 Subgroup 2.1: Metadata message preamble feature (FEAT) + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| TP Id | TP/PHDC/HOS/MDMP/FEAT/BV-000 | | | +| TP label | Metadata Message Preamble feature is supported and it shall initially be disabled. | | | +| Coverage | Spec | [USB DevClass] | | +| | Testable items | SendMetaData 1; M | SendMetaData 2; M | +| | | ReqMetaDataPream 3; M | DetQoS 1; M | +| Test purpose | Check that:
    USB Host supports Meta-Data Message Preamble feature
    [AND]
    Initially, Meta-Data Message Preamble feature is disabled | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | +| Test procedure |
    1. Connect the host under test and simulated device, then the enumeration process shall start automatically. The simulated device will inform the host under test that it supports the Metadata message preamble feature setting bit0 of the bmCapability field of the PHDC class function descriptor to 1.
    2. Upon the reception and confirmation of descriptors, if the host under test recognizes the PHDC device class, it shall send a SET_CONFIGURATION request to the simulated device as the last step of the enumeration process.
    3. The simulated device issues an "Association Request" without a preceding Metadata message preamble to the host under test.
    4. The host under test could reply with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message without a preceding Metadata message preamble or with a SET_FEATURE(META-DATA); it will mean that the Metadata message preamble is not yet enabled.
    | | | +| Pass/Fail criteria | In step 4, the host under test replies with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message without a preceding Metadata message preamble or a SET_FEATURE(META-DATA). | | | +| Notes | | | | + +## A.4 Subgroup 2.2: Get Data Status before setting / clearing (GDS) + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--| +| TP Id | TP/PHDC/HOS/MDMP/GDS/BV-000 | | | | +| TP label | USB Host supports the class-defined Get Data Status Request | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | ReqGetDataStatus 1; M | ReqGetDataStatus 2; M | | +| Test purpose | Check that:
    USB Host supports the class-defined Get Data Status request
    [AND]
    Get Data Status request fulfils the right syntax. | | | | +| Applicability | C_HOST_PHDC_002 AND C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | +| Test procedure |
    1. 1. Connect the host under test and simulated device, then the enumeration process shall start automatically. The simulated device will inform the host under test that it supports the Metadata message preamble feature setting bit0 of the bmCapability field of the PHDC class function descriptor to 1.
    2. 2. Upon the reception and confirmation of descriptors, if the host under test recognizes the PHDC device class, it shall send a SET_CONFIGURATION request to the simulated device as the last step of the enumeration process.
    3. 3. Follow the instructions given by the vendor in PIXIT I_HOST_PHDC_003 to cause the SUT to send a Get Data Status request.
    4. 4. The host under test shall send a Get Data Status request.
    5. 5. The simulated device responds with the correct status.
    | | | | +| Pass/Fail criteria | In step 4, the host under test replies with a Get Data Status message with the right syntax fields of the Get Data Status message, which will be listed as bmRequestType (A1h), bRequest (00h), wValue (0000h), wIndex (PHDC Interface), wLength (0002h). | | | | +| Notes | | | | | + +## A.5 Subgroup 2.3: Set/Clear Metadata message preamble feature (SC) + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/PHDC/HOS/MDMP/SC/BV-000 | | | | +| TP label | Enabling/Disabling Metadata Message Preamble. Syntax of SET_FEATURE and CLEAR_FEATURE | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | SendMetaData 3; M | ReqMetaDataPream 1; M | ReqMetaDataPream 4; M | +| | | ReqMetaDataPream 6; M | ReqMetaDataPream10; M | FeatTypes 1; M | +| Test purpose |

    Check that:

    USB Host enables Meta-Data Message Preamble sending a SET_FEATURE(META-DATA) message

    [AND]

    If USB Host chooses to disable the Meta-Data Message Preamble, it shall send a CLEAR_FEATURE(META-DATA) message.

    [AND]

    These messages fulfil the right syntax

    | | | | +| Applicability | C_HOST_PHDC_003 AND C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | +| Test procedure |
    1. Connect the host under test and simulated device, then the enumeration process shall start automatically. The simulated device will inform the host under test that it supports the Metadata message preamble feature setting bit0 of the bmCapability field of the PHDC class function descriptor to 1.
    2. Upon the reception and confirmation of descriptors, if the host under test recognizes the PHDC device class, it shall send a SET_CONFIGURATION request to the simulated device as the last step of the enumeration process.
    3. Perform an action on the host that enables the Metadata message preamble feature (as defined in the PIXIT I_HOST_PHDC_001).
    4. The simulated device issues an "Association Request" without a preceding Metadata message preamble to the host under test.
    5. The host under test will send a SET_FEATURE(META-DATA) message. The syntax will be verified.
    6. The host under test will send a Metadata message preamble because this feature has been enabled.
    7. After this, the host under test will send an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message.
    8. The tester inquires operator whether it is possible to disable the Metadata message preamble feature (as defined in the PIXIT I_HOST_PHDC_002).
    9. The simulated device will send an "Association Abort" message in order to move the host under test to the Unassociated State.
    10. If the host under test chooses to disable the Metadata message preamble feature, it will send a CLEAR_FEATURE(META-DATA) message. The syntax will be verified.
    | | | | +| Pass/Fail criteria |
    • In step 5, the host under test sends a SET_FEATURE(META-DATA) message with the right syntax in order to enable the Metadata message preamble feature. Fields of this message will be listed as :
      • bmRequestType =21
      • bRequest = 03
      • wValue = 0101
      • wIndex = PHDC interface
    | | | | + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • wLength=0000
    • ▪ In step 6, the host under test sends a Metadata message preamble; it proves that the feature has been enabled.
    • ▪ In step 10, if the host under test chooses to disable the Metadata message preamble, it shall send a CLEAR_FEATURE(META-DATA) message with the right syntax. Fields of this message will be listed as:
      • • bmRequestType = 21
      • • bRequest = 01
      • • wValue = 0001
      • • wIndex = PHDC interface
      • • wLength = 0000
    | +| Notes | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--|--| +| TP Id | TP/PHDC/HOS/MDMP/SC/BV-001 | | | | +| TP label | If Metadata Preamble Feature is not supported by a PHD, PHG shall not try to enable or disable the feature | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | ReqMetaDataPream
    2; M | | | +| Test purpose | Check that:
    If the simulated device indicates to Host under test that it does not support Meta-Data Message Preamble feature, then the Host should not issue the SET_FEATURE or CLEAR_FEATURE commands | | | | +| Applicability | C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | +| Test procedure |
    1. 1. Connect the host under test and simulated device, then the enumeration process shall start automatically. The simulated device will inform the host under test that it does not support the Metadata message preamble feature setting bit0 of the bmCapability field of the PHDC class function descriptor to 0.
    2. 2. Upon the reception and confirmation of descriptors, if the host under test recognizes the PHDC device class, it shall send a SET_CONFIGURATION request to the simulated device as the last step of the enumeration process.
    3. 3. The simulated device issues an "Association Request" without a preceding Metadata message preamble to the host under test.
    4. 4. The host under test will respond with an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort". It shall be verified that the host does not send either the SET_FEATURE(META-DATA) message or the Metadata message preamble before.
    5. 5. The simulated device will send an "Association Abort" message in order to move the host under test to the Unassociated State.
    6. 6. After this, it shall be verified that the host under test does not send a CLEAR_FEATURE (META-DATA) message.
    | | | | +| Pass/Fail criteria |
    • ▪ In step 4, the host under test sends an "Association Response" after receiving the "Association Request".
    • ▪ In step 6, the host under test does not send a CLEAR_FEATURE(META-DATA) message.
    | | | | +| Notes | | | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--| +| TP Id | TP/PHDC/HOS/MDMP/SC/BV-002 | | | | +| TP label | PHG only supports bQoSEncodingVersion=01h | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | ReqMetaDataPream 7; M | ReqMetaDataPream 8; M | | +| Test purpose |

    Check that:

    If the Host only supports a bQoSEncodingVersion of 01h, then it sets the high-order byte of wValue field of the SET_FEATURE message to 01h in order to enforce this QoS

    | | | | +| Applicability | C_HOST_PHDC_001 AND C_HOST_PHDC_003 AND C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | +| Test procedure |
    1. Connect the host under test and simulated device, then the enumeration process shall start automatically. The simulated device will inform the host under test that it supports the Metadata message preamble feature setting bit0 of the bmCapability field of the PHDC class function descriptor to 1. Furthermore, it will send one BULK IN endpoint descriptor, followed by a QoS descriptor (field bQoSEncodingVersion=02h).
    2. Upon the reception and confirmation of descriptors, if the host under test recognizes the PHDC device class, it shall send a SET_CONFIGURATION request to the simulated device as the last step of the enumeration process.
    3. Perform an action on the host that enables the Metadata message preamble feature (as defined in the PIXIT I_HOST_PHDC_001).
    4. The simulated device issues an "Association Request" without a preceding Metadata message preamble to the host under test.
    5. The host under test will send a SET_FEATURE(META-DATA) message. It will be verified that the high-order byte of the wValue field of the SET_FEATURE message is set to 01h.
    | | | | +| Pass/Fail criteria |

    In step 5, wValue field of the SET_FEATURE(META-DATA) message is checked:

    • bmRequestType = 21
    • bRequest = 03
    • wValue = 0101
    • wIndex = PHDC interface
    • wLength = 0000
    | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/PHDC/HOS/MDMP/SC/BV-003 | | | | +| TP label | PHD only supports bQoSEncodingVersion=01h | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | ReqMetaDataPream 9; M | | | +| Test purpose |

    Check that:

    If the simulated device only supports a bQoSEncodingVersion of 01h, then the Host under test sets the high-order byte of wValue field of the SET_FEATURE message to 01h in order to enforce this QoS

    | | | | +| Applicability | C_HOST_PHDC_003 AND C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Connect the host under test, simulated device, then the enumeration process shall start automatically. The simulated device will inform the host under test that it supports the Metadata message preamble feature setting bit0 of the bmCapability field of the PHDC class function descriptor to 1. Furthermore, the field bQoSEncodingVersion of the PHDC QoS descriptor will be set to 01h.
    2. 2. Upon the reception and confirmation of descriptors, if the host under test recognizes the PHDC device class, it shall send a SET_CONFIGURATION request to the simulated device as the last step of the enumeration process.
    3. 3. Perform an action on the host that enables the Metadata message preamble feature (as defined in the PIXIT I_HOST_PHDC_001).
    4. 4. The simulated device issues an "Association Request" without a preceding Metadata message preamble to the host under test.
    5. 5. The host under test will send a SET_FEATURE(META-DATA) message. It will be verified that the high-order byte of the wValue field of the SET_FEATURE message is set to 01h.
    | +| Pass/Fail criteria |
    • ▪ In step 5, check that the wValue field of the SET_FEATURE(META-DATA) message is as specified in the test procedure.
      • • bmRequestType = 21
      • • bRequest = 03
      • • wValue = 0101
      • • wIndex = PHDC interface
      • • wLength = 0000
    | +| Notes | | + +## A.6 Subgroup 2.4: Metadata message preamble transfer (TRANS) + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------|--------------------| +| TP Id | TP/PHDC/HOS/MDMP/TRANS/BV-000_A | | | | +| TP label | Number of transfers after a Metadata Message Preamble (PHG to PHD) | | | | +| Coverage | Spec | [USB DevClass] | | | +| | Testable items | SendMetaData 4; M | MetaDataPream 1; M | MetaDataPream 2; M | +| | | MetaDataPream 3; M | MetaDataPream 4; M | MetaDataPream 5; M | +| | | MetaDataPream 6; M | MetaDataPream 7; M | MetaDataPream 8; M | +| | | MetaDataPream 9; M | | | +| Test purpose | Check that:

    After the Host issues a Meta-Data Message Preamble, it sends a count of bNumTransfers data transfers

    [AND]

    Meta-Data Message Preamble fulfil the right syntax | | | | +| Applicability | C_HOST_PHDC_003 AND C_MAN_OXP_038 AND C_MAN_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | | +| Test procedure |
    1. 1. Wait until the Metadata message preamble feature is enabled.
      1. a. Connect the host under test and simulated device.
      2. b. Wait until the end of the enumeration process.
      3. c. Perform an action on the host that enables the Metadata message preamble feature as defined in the PIXIT I_HOST_PHDC_001.
      4. d. The simulated device sends an "Association Request"; it includes a standard configuration supported by the PHG under test (in case of TH, PO, GM, BPM, WS, AM, IP or PF specializations) or an extended configuration with one optional object (in case of HUB, ST or CV specializations)
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    e. The host under test sends a SET_FEATURE(META-DATA) in order to enable the Metadata message preamble feature.

    2. The host under test will send an "Association Response" preceded by a Metadata message preamble (the value of the bNumTransfers field is captured).

    a. If the PHG under test replies with an Association Response (accepted), the simulated PHD will start the confirmed data sending. The quantity of confirmed data transfers will be equal to the bNumTransfers field of the Metadata message preamble that the PHG under test sent.

    b. If the PHG under test replies with an Association Response (accepted-unknown-config), the simulated PHD will send the configuration. This configuration should be accepted by the PHG, and the simulated PHD will start the confirmed data sending. The quantity of confirmed data transfers will be equal to the bNumTransfers field of the Metadata message preamble that the PHG under test sent -1.

    3. The PHG under test acknowledges each simulated PHD message by sending a rors-cmip-confirmed-event-report (in case 2.a) or a result = accepted-unknown-config message plus bNumTransfers-1 rors-cmip-confirmed-event-reports (in case 2.b).

    4. The acknowledging of the last confirmed data will be preceded by a new Metadata message preamble.

    | +| Pass/Fail criteria |
    • ▪ In step 2, the Metadata message preamble has been sent and the syntax of the Metadata message preamble fulfils the spec:
      • • aSignature field: "PhdcQoSsignature" (50 68 64 63 51 6F 53 53 69 67 6E 61 74 75 72 65 in hexadecimal)
      • • bNumtransfers>0
      • • bQoSencodingVersion=01h
      • • bmLatencyReliability contains 8 (medium.best) since medium.best is required for all transfers from a PHG to a PHD.
      • • bOpaqueDataSize between 0 and EP max packet size minus 21)
    • ▪ In step 4, a new Metadata message preamble is detected after "bNumTransfers" messages are sent by the host.
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------| +| TP Id | TP/PHDC/HOS/MDMP/TRANS/BV-000_B | | | +| TP label | Number of transfers after a Metadata Message Preamble (PHD to PHG) | | | +| Coverage | Spec | [USB DevClass] | | +| | Testable items | SendMetaData 4; M | MetaDataPream 8; M | +| Test purpose |

    Check that:

    After the simulated device issues a Meta-Data Message Preamble, Host acknowledges the next count of bNumTransfers data transfers and the next Meta-Data Message Preamble

    | | | +| Applicability | C_HOST_PHDC_003 AND C_MAN_OXP_038 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | +| Test procedure |

    1. Wait until the Metadata message preamble feature is enabled

    a. Connect the host under test and simulated device.

    b. Wait until the end of the enumeration process.

    c. Perform an action on the host that enables the Metadata message preamble feature as defined in the PIXIT I_HOST_PHDC_001.

    d. The simulated device sends an "Association Request". It includes a standard configuration supported by the PHG under test (in case of TH, PO, GM, BPM, WS, AM, IP or PF specializations) or an extended configuration with one optional object (in case of HUB, ST or CV specializations).

    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    e. The host under test sends a SET_FEATURE(META-DATA) in order to enable the Metadata message preamble feature.

    2. The host under test will send an "Association Response" preceded by a Metadata message preamble.

    a. If the PHG under test replies with an Association Response (accepted), the simulated PHD will start the confirmed data sending. The first data will be preceded by a Metadata message preamble with bNumTransfers=5.

    b. If the PHG under test replies with an Association Response (accepted-unknown-config), the simulated PHD will send the configuration preceded by a Metadata message preamble with bNumTransfers=5. This configuration should be accepted by the PHG and the simulated PHD will start the confirmed data sending.

    3. The PHG under test acknowledges each simulated PHD message by sending a rors-cmip-confirmed-event-report (in cases 2.a and 2.b) or a result = accepted-unknown-config message in case 2.b).

    4. After the simulated PHD has sent five transfers (i.e., five confirmed data messages (2a) or one configuration plus four confirmed data messages (2b)), the simulated PHD will send a Metadata preamble followed by another confirmed data message.

    5. The PHG under test shall acknowledge this last confirmed data message that is preceded by a Metadata message preamble by sending a rors-cmip-confirmed-event-report preceded by a Metadata preamble (if bNumTransfers have already been sent by the PHG).

    | +| Pass/Fail criteria |
    • ▪ In step 3, the PHG under test acknowledges each simulated PHD message.
    • ▪ In step 5, the PHG under test acknowledges the last message sent by the simulated PHD that is preceded by a Metadata message preamble.
    | +| Notes | | + +## A.7 Subgroup 2.5: Metadata message preamble feature error conditions (ERR) + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------| +| TP Id | TP/PHDC/HOS/MDMP/ERR/BV-000 | | | +| TP label | Metadata Message Preamble expected but not received | | | +| Coverage | Spec | [USB DevClass] | | +| | Testable items | MetaDataPreamError 2; M | MetaDataPreamError 5; M | +| Test purpose | Check that if a Meta-Data Message Preamble is expected but not received by Host under test, it shall send a SET_FEATURE ENDPOINT_HALT request and later a CLEAR_FEATURE ENDPOINT_HALT message to the simulated device. | | | +| Applicability | C_HOST_PHDC_003 AND C_MAN_OXP_038 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | +| Test procedure |
    1. 1. Wait until the Metadata message preamble feature is enabled.
      1. a. Connect the host under test and simulated device.
      2. b. Wait until the end of the enumeration process.
      3. c. Perform an action on the Host that enables the Metadata message preamble feature as defined in the PIXIT I_HOST_PHDC_001.
      4. d. The simulated device sends an "Association Request".
      5. e. The host under test sends a SET_FEATURE(META-DATA) in order to enable the Metadata message preamble.
    2. 2. The host under test will send an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message preceded by a Metadata message preamble.
    3. 3. The simulated device will send a message to the host under test. This message should be preceded by a Metadata message preamble, but it will be omitted in order to check the response of the host. The type of message will depend on the Association Response sent by the host:
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. a. If the host under test sends an "Association Response (accepted)", then the simulated device will send confirmed data.
    2. b. If the host under test sends an "Association Response (accepted-unknown-config)", then the simulated device will send a configuration.
    1. 4. As the host expects to receive a Metadata message preamble, it shall send 2 messages: SET_FEATURE ENDPOINT_HALT and CLEAR_FEATURE ENDPOINT_HALT.
    2. 5. Now, the simulated PHD will send a valid Metadata message preamble that precedes confirmed data (if the PHG under test sent an Association Response (accepted) in step 2) or a configuration (if the PHG under test sent an Association Response (accepted-unknown-config) in step 2).
    3. 6. The host under test shall acknowledge that transmission.
    | +| Pass/Fail criteria |
    • ▪ In step 4, the host under test sends a SET_FEATURE ENDPOINT_HALT and a CLEAR_FEATURE ENDPOINT_HALT.
    • ▪ In step 6, the host acknowledges a new Metadata message preamble after sending a CLEAR_FEATURE ENDPOINT_HALT by sending a data confirmation (if the simulated PHD sent a confirmed data) or a configuration confirmation (if the PHD sent its configuration).
    | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------------------------------| +| TP Id | TP/PHDC/HOS/MDMP/ERR/BV-001 | | | +| TP label | Metadata Message Preamble received with invalid bmLatencyReliability value. | | | +| Coverage | Spec | [USB DevClass] | | +| | Testable items | MetaDataPreamError 3; M | MetaDataPreamError 5; M
    MetaDataPreamError 6; M | +| Test purpose |

    Check that:

    If a Meta-Data Message Preamble with an invalid bmLatencyReliability value is received by Host under test, then it sends a SET_FEATURE ENDPOINT_HALT request and later a CLEAR_FEATURE ENDPOINT_HALT message to the simulated device.

    | | | +| Applicability | C_HOST_PHDC_003 AND C_MAN_OXP_038 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | +| Test procedure |
    1. 1. Wait until the Metadata message preamble feature is enabled.
      1. a. Connect the host under test and simulated device.
      2. b. Wait until the end of the enumeration process.
      3. c. Perform an action on the host that enables the Metadata message preamble feature as defined in the PIXIT I_HOST_PHDC_001.
      4. d. The simulated device sends an "Association Request".
      5. e. The host under test sends a SET_FEATURE(META-DATA) in order to enable the Metadata message preamble.
    2. 2. The host under test will send an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message preceded by a Metadata message preamble.
    3. 3. The simulated device will send a message to the host under test. This message will be preceded by a Metadata message preamble with an invalid bmLatencyReliability value (for example, bit 6 set to 1). The type of message will depend on the Association Response sent by the host:
      1. a. If the host under test sends an "Association Response (accepted)", then the simulated device will send a confirmed data.
      2. b. If the host under test sends an "Association Response (accepted-unknown-config)", then the simulated device will send a configuration.
    4. 4. As the host has received a Metadata message preamble with an invalid
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    bmLatencyReliability value, it shall send 2 messages: SET_FEATURE ENDPOINT_HALT and CLEAR_FEATURE ENDPOINT_HALT.

    5. Now, the simulated PHD will send a valid Metadata message preamble that precedes confirmed data (if the PHG under test sent an Association Response (accepted) in step 2) or a configuration (if the PHG under test sent an Association Response (accepted-unknown-config) in step 2).

    6. The host under test shall acknowledge that transmission.

    | +| Pass/Fail criteria |
    • ▪ In step 4, the host under test sends a SET_FEATURE ENDPOINT_HALT and a CLEAR_FEATURE ENDPOINT_HALT.
    • ▪ In step 6, the host acknowledges a new Metadata message preamble after sending a CLEAR_FEATURE ENDPOINT_HALT by sending a data confirmation (if the simulated PHD sent a confirmed data) or a configuration confirmation (if the PHD sent its configuration).
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------| +| TP Id | TP/PHDC/HOS/MDMP/ERR/BV-002 | | | +| TP label | Metadata Message Preamble received with invalid bNumTransfers value. | | | +| Coverage | Spec | [USB DevClass] | | +| | Testable items | MetaDataPreamError 4; M | MetaDataPreamError 5; M | +| Test purpose |

    Check that:

    If a Meta-Data Message Preamble with an invalid bNumTransfers value is received by Host under test, then it sends a SET_FEATURE ENDPOINT_HALT request and later a CLEAR_FEATURE ENDPOINT_HALT message to the simulated device.

    | | | +| Applicability | C_HOST_PHDC_003 AND C_MAN_OXP_038 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated device is plugged into the host under test. | | | +| Test procedure |
    1. 1. Wait until the Metadata message preamble feature is enabled.
      1. a. Connect the host under test and simulated device.
      2. b. Wait until the end of the enumeration process.
      3. c. Perform an action on the host that enables the Metadata message preamble feature as defined in the PIXIT I_HOST_PHDC_001.
      4. d. The simulated device sends an "Association Request".
      5. e. The host under test sends a SET_FEATURE(META-DATA) in order to enable the Metadata message preamble.
    2. 2. The host under test will send an "Association Response" (accepted, accepted-unknown-config or rejected) or an "Association Abort" message preceded by a Metadata message preamble.
    3. 3. The simulated device will send a message to the host under test. This message will be preceded by a Metadata message preamble with an invalid bNumTransfers value (bNumTransfers = 0). The type of message will depend on the Association Response sent by the host:
      1. a. If the host under test sends an "Association Response (accepted)", then the simulated device will send a confirmed data.
      2. b. If the host under test sends an "Association Response (accepted-unknown-config)", then the simulated device will send a configuration.
    4. 4. As the host has received a Metadata message preamble with an invalid bNumTransfers value, it shall send 2 messages: SET_FEATURE ENDPOINT_HALT and CLEAR_FEATURE ENDPOINT_HALT.
    5. 5. Now, the simulated PHD will send a valid Metadata message preamble that precedes confirmed data (if the PHG under test sent an Association Response (accepted) in step 2) or a configuration (if the PHG under test sent an Association Response (accepted-unknown-config) in step 2).
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 6. The host under test shall acknowledge that transmission. | +| Pass/Fail criteria |
    • ▪ In step 4, the host under test sends a SET_FEATURE ENDPOINT_HALT and a CLEAR_FEATURE ENDPOINT_HALT.
    • ▪ In step 6, the host acknowledges a new Metadata message preamble after sending a CLEAR_FEATURE ENDPOINT_HALT by sending a data confirmation (if the simulated PHD sent a confirmed data) or a configuration confirmation (if the PHD sent its configuration).
    | +| Notes | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] Personal Health Device DG2016 PICS and PIXIT excel sheet v1.9. + +- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.843-201808-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.843-201808-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bcda2c01451dbc3cddbdce7f60f1edcb3cde5e9 --- /dev/null +++ b/marked/H/T-REC-H.843-201808-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e18e4f38b75cc1dacb67027b5abc017d0596259f8f138890e9c4ea02887a12b +size 4177 diff --git a/marked/H/T-REC-H.843-201808-I_PDF-E/raw.md b/marked/H/T-REC-H.843-201808-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a53b3677f7b311ee5403c4d2546988994a961065 --- /dev/null +++ b/marked/H/T-REC-H.843-201808-I_PDF-E/raw.md @@ -0,0 +1,1539 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.843** + +(08/2018) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 3: Continua Design Guidelines: Personal +Health Device** + +Recommendation ITU-T H.843 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.843 + +### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 3: Continua Design Guidelines: Personal Health Device + +## Summary + +Recommendation ITU-T H.843 provides a test suite structure (TSS) and the test purposes (TP) for personal health devices in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2017) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.843 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 3: Continua Design Guidelines. Personal Health Device (Version 1.11, 2017-07-18), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.843 | 2015-01-13 | 16 | 11.1002/1000/12260 | +| 2.0 | ITU-T H.843 | 2016-07-14 | 16 | 11.1002/1000/12936 | +| 3.0 | ITU-T H.843 | 2017-04-13 | 16 | 11.1002/1000/13217 | +| 4.0 | ITU-T H.843 | 2018-08-29 | 16 | 11.1002/1000/13680 | + +## Keywords + +Conformance testing, continua design guidelines, e-health, ITU-T H.810, personal area network, personal connected health devices, personal health devices interface, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|--------------|-------------------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 4 | +| 3.1 | Terms defined elsewhere ..... | 4 | +| 3.2 | Terms defined in this Recommendation..... | 4 | +| 4 | Abbreviations and acronyms ..... | 4 | +| 5 | Conventions ..... | 5 | +| 6 | Test suite structure (TSS) ..... | 7 | +| 7 | Electronic attachment ..... | 9 | +| Annex A | Test purposes ..... | 10 | +| A.1 | TP definition conventions..... | 10 | +| A.2 | Subgroup 1.1.1 – Design guidelines: Common (DGC)..... | 12 | +| A.3 | Subgroup 1.1.2 – USB design guidelines (UDG)..... | 23 | +| A.4 | Subgroup 1.1.3 – Bluetooth design guidelines (BDG)..... | 26 | +| A.5 | Subgroup 1.1.4 – Pulse oximeter device specialization design guidelines (PODG)..... | 36 | +| A.6 | Subgroup 1.1.5 – Cardiovascular design guidelines (CVDG) ..... | 40 | +| A.7 | Subgroup 1.1.6 – Activity hub design guidelines (HUBDG)..... | 41 | +| A.8 | Subgroup 1.1.7 – ZigBee design guidelines (ZDG) ..... | 43 | +| A.9 | Subgroup 1.1.10 – Basic electrocardiograph design guidelines (ECGDG) ... | 57 | +| A.10 | Subgroup 1.1.11 – NFC design guidelines (NDG)..... | 60 | +| Bibliography | ..... | 63 | + +Electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 3: Continua Design Guidelines. Personal Health Device (Version 1.11, 2017-07-18), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.4 | 2012-10-05 | Initial release for Test Tool DG2011. This uses "TSS&TP_1.5_PAN-LAN_PART_3_v1.3.doc" as a baseline and adds new features included in [b-CDG 2011]:
    • • ZigBee One-to-Many and Errata
    | +| 1.5 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_1.5_PAN-LAN_PART_3_v1.4.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • • Updates test procedures according to new requirements included in [b-CDG 2012] (e.g., SSP requirements)
    • • Adds body composition analyser device specialization
    • • Adds basic electrocardiograph device specialization
    | +| 1.6 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_3_v1.5.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.7 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_3_v1.6.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row has been added
    | +| 1.8 | 2015-07-01 | Initial Release for Test Tool DG2015. It uses "TSS&TP_DG2013_PLT_PART_3_v1.7.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015] | +| 1.9 | 2016-01-26 | First Maintenance Release for Test Tool DG2015. It uses "TSS&TP_DG2015_LP-PAN_PART_3_v1.8.doc" as a baseline and adds some updates according to the Maintenance 2015 activity. | +| 1.10 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_3_v1.9.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016] | +| 1.11 | 2017-07-18 | Second maintenance release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_3_v1.10.doc" as a baseline to correct minor typos. | +| 1.12 | 2018-02-27 | Updates related to the inclusion of the power status monitor of Personal Health Devices device specialization [ISO/IEEE 11073-10427]
    Updates related to the changes included in the glucose meter device specialization ([ISO/IEEE 11073-10417]) | + +## Recommendation ITU-T H.843 + +### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 3: Continua Design Guidelines: Personal Health Device + +## 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2017)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 3. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- **Part 3: Continua design guidelines. Personal Health Device** +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Device. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) + - Part 5Q: Power status monitor (PSM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.810 (2017)] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal health systems*. + +[ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd.1:2015. + with + + +[ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + + +[ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization*. +NOTE – This is shorthand used to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. + +[ISO/IEEE 11073-10404] ISO/IEEE 11073-10404:2010, *Health informatics – Personal health device communication – Part 10404: Device specialization – Pulse oximeter*. + + +[ISO/IEEE 11073-10406] ISO/IEEE 11073-10406-2012, *Health informatics – Personal health device communication – Part 10406: Device specialization – Basic electrocardiograph (ECG) (1- to 3-lead ECG)*. + + +[ISO/IEEE 11073-10407] ISO/IEEE 11073-10407:2010, *Health informatics – Personal health device communication – Device specialization – Blood pressure monitor, version 1.0*. + + +[ISO/IEEE 11073-10408] ISO/IEEE 11073-10408:2010, *Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer*. + + +- [ISO/IEEE 11073-10415] ISO/IEEE 11073-10415:2010, *Health informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale*. + +- [ISO/IEEE 11073-10417] ISO/IEEE 11073-10417:2017, *Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter*. + +- [ISO/IEEE 11073-10418C] ISO/IEEE 11073-10418-2014, *Health informatics – Personal health device communication – Part 10418: Device specialization – International Normalized Ratio (INR) monitor*, including ISO/IEEE 11073-10418:2014/Cor. 1:2016. + with + +- [ISO/IEEE 11073-10419] ISO/IEEE 11073-10419:2016, *Health informatics – Personal health device communication – Part 10419: Device specialization – Insulin pump*. + +- [ISO/IEEE 11073-10420] ISO/IEEE 11073-10420-2012, *Health informatics – Personal health device communication – Part 10420: Device specialization – Body composition analyzer*. + +- [ISO/IEEE 11073-10421] ISO/IEEE 11073-10421:2012, *Health informatics – Personal health device communication – Part 10421: Device specialization – Peak expiratory flow monitor (peak flow)*. + +- [ISO/IEEE 11073-10424] ISO/IEEE 11073-10424:2016, *Health informatics – Personal health device communication – Part 10424: Device specialization – Sleep apnoea breathing therapy equipment (SABTE)*. + +NOTE – equivalent to IEEE 11073-10424-2014, Health informatics – Personal health device communication – Part 10424: Device Specialization – Sleep Apnoea Breathing Therapy Equipment (SABTE). + +- [ISO/IEEE 11073-10425] ISO/IEEE 11073-10425:2016, *Health informatics – Personal health device communication – Part 10425: Device specialization – Continuous glucose monitor (CGM)*. + +- [ISO/IEEE 11073-10427] ISO/IEEE 11073-10427:2018, *Health informatics – Personal health device communication – Part 10427: Device specialization – Power status monitor of personal health devices*. +. Same publication as +. +- [ISO/IEEE 11073-10441] ISO/IEEE 11073-10441-2015, *Health informatics – Personal Health Device Communication – Part 10441: Device Specialization – Cardiovascular fitness and activity monitor*. + + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [ISO/IEEE 11073-10442] | ISO/IEEE 11073-10442:2015, Health informatics – Personal health device communication – Part 10442: Device specialization – Strength fitness equipment .
    http://standards.ieee.org/findstds/standard/11073-10442-2008.html | +| [ISO/IEEE 11073-10471] | ISO/IEEE 11073-10471:2010, Health informatics – Personal health device communication – Part 10471: Device specialization – Independent living activity hub .
    https://www.iso.org/standard/54328.html | +| [ISO/IEEE 11073-10472] | ISO/IEEE 11073-10472:2012, Health informatics – Personal health device communication – Part 10472: Device specialization – Medication monitor .
    https://www.iso.org/standard/54364.html | + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|------------------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| CESL | Continua Enabling Software Library | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | + +| | | +|-------|-------------------------------------------------------| +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| PSM | Power Status Monitor | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| SSP | Secure Simple Pairing | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +## 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2017 | – | 7.0 | Release 2017 of the CDG including maintenance updates of the CDG 2016 and additional guidelines that cover new functionalities. | – | +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.10, 1.1.11 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - **Subgroup 1.1.1: Design guidelines: common (DGC)** + - **Subgroup 1.1.2: USB design guidelines (UDG)** + - **Subgroup 1.1.3: Bluetooth design guidelines (BDG)** + - **Subgroup 1.1.4: Pulse oximeter design guidelines (PODG)** + - **Subgroup 1.1.5: Cardiovascular design guidelines (CVDG)** + - **Subgroup 1.1.6: Activity hub design guidelines (HUBDG)** + - **Subgroup 1.1.7: ZigBee design guidelines (ZDG)** + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - **Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG)** + - **Subgroup 1.1.11: NFC design guidelines (NDG)** + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Subgroup 1.3.17: Power status monitor (PSM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + +- Subgroup 1.4.2: Whitepaper thermometer requirements (TH) +- Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +###### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) + - Subgroup 2.3.17: Power status monitor (PSM) + +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + - Subgroup 2.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +## 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . See [b-PHD PICS & PIXIT], [b-PHG PICS & PIXIT] and [b-TI]. + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case: + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth Low Energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test: + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing: + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 1.1.1 – Design guidelines: Common (DGC) + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------| +| TP Id | TP/PLT/PHD/TR/DGC/BI-000 | | | +| TP label | PAN Device AHD Linkage | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Linkage 1; M | NFCDev 1; M | +| Test purpose | Check that:
    Device cannot actively communicate with a second AHD | | | +| Applicability | C_AG_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The Personal Health Device (PHD) under test and simulated Personal Health Gateway (PHG) are in the Operating state. | | | +| Test procedure |
    1. 1. IF the PHD is currently using a USB as a connection mode:
      1. a. If the device allows for a second type-B connector, connect the device to a new simulated PHG using that connector and attempt to associate it.
      2. b. If the device allows for a Bluetooth connection (in addition to the currently used USB connection), attempt to associate it to a new simulated PHG using the Bluetooth connection.
      3. c. If the device allows for an NFC connection (in addition to the currently used USB connection), attempt to associate it with a new simulated PHG using the NFC connection.
    2. 2. IF the device is currently using a Bluetooth as a connection mode:
      1. a. If the device allows for a Bluetooth connection, attempt to associate it with a new simulated PHG using the BT connection.
      2. b. If the device allows for a USB connector, connect the device to a new simulated PHG using that connector and attempt to associate it.
      3. c. If the device allows for an NFC connection, attempt to associate it with a new simulated PHG using the NFC connection.
    3. 3. IF the device is currently using an NFC as a connection mode:
      1. a. If the device allows for a Bluetooth connection, attempt to associate it with a new simulated PHG using the BT connection.
      2. b. If the device allows for a USB connector, connect the device to a new simulated PHG using that connector and attempt to associate it.
      3. c. If the device allows for a NFC connection, attempt to associate it with a new simulated PHG using the NFC connection.
    | | | +| Pass/Fail criteria | The PHD shall not be able to associate with a second AHD in any of the cases tested. | | | +| Notes | | | | + +| | | | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/TR/DGC/BI-001 | | | +| TP label | Manager-initiated communications | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 3; M | | +| Test purpose | Check that:
    Service component does not support manager-initiated event reporting as a mechanism of measurement transfer | | | +| Applicability | C_AG_OXP_000 | | | +| Other PICS | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The service under test and the simulated PHG are in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an Association request from the PHD under test.
    2. 2. The simulated PHG sends an Association Response with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event type to send its configuration to the PHG.
    4. 4. The PHG sends a Remote Operation Response Confirmed Event report to accept the configuration.
    5. 5. The attributes of interest for this test are:
      1. a. In the Association request message: Data-Req-Mode-Capab:
        • field- type = DataReqModeCapab
        • field-length = 4 bytes
        • data-req-init-manager-count = 0
      2. b. In the Configuration report message: Check the mss-acc-manager-initiated parameter in the Metric-Spec-Small attribute for every metric derived object declared in the configuration report
    6. 6. The simulated PHG issues an MDS-Data-Req to the PHD, with any metric-derived data attribute supported by the PHD.
    | +| Pass/Fail criteria |
    • • mss-acc-manager-initiated (bit 8) must be set to 0 in the Metric-Spec-Small field of all the metric derived objects and
    • • the PHD must respond with an error to step 6 (roer message = 0x0300, RoerErrorValue = no-such-action), indicating this procedure is not supported.
    | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/TR/DGC/BV-002 | | | +| TP label | DataReqMode Alignment | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 4; M | | +| Test purpose | Check that:

    The fields in the Metric-Spec-Small attribute of metric objects are aligned with what was declared in the DataReqModeCapab structure during Association for the Service | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_040 OR C_AG_OXP_042 OR C_AG_OXP_043) | | | +| Other PICS | | | | +| Initial condition | The service under test and the simulated PHG are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG sends an Association Response with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The PHG sends a Remote Operation Response Confirmed Event report to accept the configuration.
    5. 5. The attributes of interest for this test are:
      1. a. In the Association request message:Data-Req-Mode-Capab:
        • field- type = DataReqModeCapab
        • field-length = 2 bytes
        • field- value =SEQUENCE { data-req-mode-flags
          DataReqModeFlags,
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    data-req-init-agent-count INT-U8, -- maximum number of parallel agent-initiated data requests

    data-req-init-manager-count INT-U8, -- maximum number of parallel manager-initiated data requests

    b. In the Configuration report message: Check the mss-acc-manager-initiated parameter in the Metric-Spec-Small attribute for every metric derived object declared in the configuration report.

    | +| Pass/Fail criteria |

    The fields of the attribute must be aligned with what was previously declared. Specifically:

    In Metric-Spec-Small, the parameter mss-acc-manager-initiated shall be =0, and the parameter mss-acc-agent-initiated shall be =1 for all the metric derived objects,

    In the Association request message, the field data-req-init-manager-count shall be =0.

    and the field data-req-init-agent-count shall be =1;

    In addition, the parameter DataReqModeFlags shall contain the data-req-supp-init-agent (bit 15) set to 1.. All unassigned DataReqModeFlags bit values are reserved for future expansion and shall be set to zero.

    | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/TR/DGC/BV-003 | | | +| TP label | FIFO store and forward | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable Items | Communication 5; C | | +| Test purpose |

    Check that:

    Service component designed to store and forward temporary measurements transmits data in a First-In First-Out sequence

    | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_032 OR C_AG_OXP_041) | | | +| Other PICS | C_AG_DGC_009, C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_032, C_AG_OXP_041, C_AG_OXP_182, C_AG_OXP_183, C_AG_OXP_184, C_AG_OXP_189, C_AG_OXP_293 | | | +| Initial condition |

    The service under test and the simulated PHG are disconnected.

    This may be achieved by physically disconnecting the USB cable between the PHD and PHG (USB) or by moving the PHD out of range of the PHG (BT).

    | | | +| Test procedure |
    1. 1. Take some measurements of different values with the PHD under test. Record the measurements in order.
    2. 2. Connect the PHD under test to the simulated PHG.
    3. 3. Wait for the PHD and simulated PHG to associate:
      1. a. The simulated PHG receives an association request from the PHD under test.
      2. b. The simulated PHG sends an Association Response with a result = accepted-unknown-config.
      3. c. The PHD sends a Remote roiv-cmip-confirmed-event-report message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
      4. d. The simulated PHG sends a rors-cmip-confirmed-event-report with reason "accepted" to accept the PHD's configuration.
      5. e. IF C_AG_OXP_293 THEN:
        1. i. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
        2. ii. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
        3. iii. IF the mds-time-mgr-set-time bit is set:
          • The PHG moves to Configuring/Sending Set Time substate and:
            • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
    • ❑ Once its internal time setting operation is completed, the PHD responds to the PHG.
    1. 4. If the PHD under test supports a fixed or variable format MDS event report, the simulated PHG waits to receive the measurements from the PHD under test. The measurements that are transferred through the MDS event report are recorded.
    2. 5. If the PHD under test supports PM-Store, the simulated PHG performs a Get-Segment-Info and forces the PHD to send the information stored in the PM-Segments (Trig-Segment-Data-Xfer). The PHD under test sends the measurements stored in the PM-Segment (Segment-Data-Event). The measurements that are transferred through the Segment-Data-Event are recorded.
    3. 6. A pop-up shows the stored data in steps 4 and 5.
    4. 7. IF C_AG_OXP_032, check that the temporarily stored measurements are sent in a FIFO way.
    5. 8. IF NOT C_AG_OXP_032, check that the stored measurements are NOT sent, so the measurements received by the PHG are new measurements.
    | +| Pass/Fail criteria |

    If Store and Forward measurements PICS is supported (C_AG_OXP_032), the temporary stored measurements shall be sent in a FIFO way (in the same order as they were taken).

    If the PICS (C_AG_OXP_032) is not set, the device shall not be capable of storing temporary measurements, or shall not transmit them, so the first event reports with measurements are with new data (not stored data).

    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/TR/DGC/BV-008 | | | +| TP label | Updating attributes previously defined | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 11; M | | +| Test purpose |

    Check that:

    Continua PAN/LAN service components shall send changes to any particular attribute via a single Scanner object (if enabled) or the MDS object, but never more than one object (of either MDS or Scanner type)

    | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_046 OR C_AG_OXP_047) | | | +| Other PICS | C_AG_OXP_180 | | | +| Initial condition | The service under test and the simulated PHG are in the Operating state | | | +| Test procedure |
    1. 1. Make changes to an attribute of any metric that is collected by a scanner object.
    2. 2. Check and record the attributes for metric objects that have been reported using MDS event reports.
    3. 3. Set the Operational State to 1 for the Scanner object.
    4. 4. Wait until the PHD under test starts to send its data using Scanner event reports and record it.
    5. 5. Set the Operational State to 0 for the Scanner object.
    6. 6. Repeat steps 3 to 5 for all scanner objects.
    | | | +| Pass/Fail criteria | Check that all attributes for metric objects reported using Scanner event reports in step 4 have not been reported via MDS event reports. | | | +| Notes | | | | + +| | | +|-----------------|---------------------------------------| +| TP Id | TP/PLT/PHD/TR/DGC/BV-009 | +| TP label | MDS Device and Regulatory information | + +| | | | | | +|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------| +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Dev.Information 1; M | Dev.Information 2; O | Dev.Information 3; M | +| | | Dev.Information 4; O | Dev.Information 5; M | Dev.Information 6; M | +| | | Dev.Information 7; M | Dev.Information 8; C | Regulatory 1; M | +| | | Regulatory 2; M | Regulatory 3; M | Regulatory 6; M | +| | | Regulatory 7; M | Regulatory 9; M | Cardio_DG 7; M | +| | | Hub_DG 2; M | Hub_DG 4; M | Hub_DG 6; M | +| | | Hub_DG 8; M | Hub_DG 10; M | Hub_DG 12; M | +| | | Hub_DG 14; M | Hub_DG 16; M | Hub_DG 18; M | +| | | Hub_DG 20; M | Hub_DG 22; M | Hub_DG 24; M | +| | | Hub_DG 26; M | Hub_DG 28; M | Versioning 1; M | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | | +| | Testable items | MDSClassAttr 8; O | ConfNormalProc 23; M | | +| Test purpose | | Check that:
    Device information fields of an Service component's MDS object are correct | | | +| Applicability | | C_AG_OXP_000 | | | +| Other PICS | | C_AG_OXP_185 | | | +| Initial condition | | The service under test and the simulated PHG are in the Unassociated state. | | | +| Test procedure | |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG sends an association response with a result = accepted-unknown-config.
    3. 3. The PHD sends a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The simulated PHG issues a remote Operation Response Confirmed Event Report message with result code = "accepted".
    5. 5. The simulated PHG issues a roiv-cmip-get with handle=0 and attribute list=empty, to request for all the attributes supported by the PHD.
    6. 6. The attributes of interest to be checked (obtained from the Configuration event report and the GET request are):
      1. a. Mandatory attribute System-Id
        1. OUI = OUI assigned to the original manufacturer
        2. 40-bit manufacturer part = device ID set by the original manufacturer. Check the value declared by manufacturer in the PIXIT list.
      2. b. Mandatory attribute System-Model
        1. Manufacturer = (original manufacturer OR customer facing company). Check the value declared by the manufacturer in the PIXIT list.
        2. Model-number = (original manufacturer OR customer facing company). Check the value declared by the manufacturer in the PIXIT list.
      3. c. Mandatory attribute Product-Specification
        1. Spec-type = serial-number
        2. Prod-spec = (serial number of the device). Check the value declared by the manufacturer in the PIXIT list.

          IF a firmware number is declared in the Product-Specification attribute

          1. Mandatory attribute Product-Specification
            1. 1. Spec-type = fw-revision
            2. 2. Prod-spec = (firmware revision of the device)
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    IF a firmware number is not declared in the Product-Specification attribute, THEN it is not present in Product-Specification attribute.

    d. Mandatory attribute Reg-Cert-Data-List:

    • attribute-id = MDC_ATTR_REG_CERT_DATA_LIST
    • attribute-type = RegCertDataList

    Search for the RegCertData element that contains:

    • • auth-body = auth-body-continua
    • • auth-body-struc-type = continua-version-struct
    • • auth-body-data = ContinuaBodyStruct
      Within ContinuaBodyStruct:
      major-IG-version = 6
      minor-IG-version = 1
      certified-devices = <CDC list matches all implemented and only the implemented Certified Device Classes and value for CertifiedDeviceClassEntry is: MDC_DEV_*_SPEC_PROFILE_* - 4096 + TCode x 8192 with TCode =
      • ▪ It is recommended to include the supported MDC_DEV_*_SPEC_PROFILE_* codes along with a TCode of 0 to interoperate with version 1 client components.
      • ▪ IF C_AG_UDG_001=TRUE, THEN TCode=1 (Wired PAN)
      • ▪ IF C_AG_BDG_001=TRUE, THEN TCode=2 (Wireless PAN)
      • ▪ IF C_AG_ZDG_001=TRUE, THEN TCode=3 (Wireless LAN)

    And the RegCertData element that contains:

    • • auth-body = auth-body-continua
    • • auth-body-struc-type = continua-reg-struct
    • • auth-body-data = ContinuaRegStruct
      Within ContinuaRegStruct:
      regulation-bit-field = 0 if device is listed as regulated in certification application, 1 otherwise

    e. Mandatory attribute System-Type-Spec-List

    • <CDC list matches those declared in the certification application → Note this only needs to list the CDCs that will be utilized concurrently. If the device is a hub, this list may be a subset of the full CDC list.>
      <It is acceptable for the CDC list to include additional specializations not part of the application.>
    | +| Pass/Fail criteria |

    All checked values are as specified in the test procedure:

    • • If the PHD supports Step Counter sub-specialization (profile):MDC_DEV_*_SPEC_PROFILE_* is MDC_DEV_SUB_SPEC_PROFILE_STEP_COUNTER = 4200 (0x1068)
    • • If the PHD supports Fall Sensor sub-specialization (profile): MDC_DEV_*_SPEC_PROFILE_* is MDC_DEV_SUB_SPEC_PROFILE_FALL_SENSOR = 4213 (0x1075)
    • • If the PHD supports Motion Sensor sub-specialization (profile): MDC_DEV_*_SPEC_PROFILE_* is MDC_DEV_SUB_SPEC_PROFILE_MOTION_SENSOR = 4219 (0x107B)
    • • If the PHD supports Enuresis Sensor sub-specialization (profile): MDC_DEV_*_SPEC_PROFILE_* is MDC_DEV_SUB_SPEC_PROFILE_ENURESIS_SENSOR = 4221 (0x107D).
    • • If the PHD supports Contact Closure Sensor sub-specialization (profile):MDC_DEV_*_SPEC_PROFILE_* is MDC_DEV_SUB_SPEC_PROFILE_CONTACTCLOSURE_SENSOR = 4222 (0x107E)
    • • If the PHD supports Switch Sensor sub-specialization (profile): MDC_DEV_*_SPEC_PROFILE_* is MDC_DEV_SUB_SPEC_PROFILE_SWITCH_SENSOR = 4224 (0x1080).
    | + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • If the PHD supports Dosage Sensor sub-specialization (profile):
      MDC_DEV_*_SPEC_PROFILE_* is
      MDC_DEV_SUB_SPEC_PROFILE_DOSAGE_SENSOR = 4225 (0x1081)
    • If the PHD supports Water Sensor sub-specialization (profile):
      MDC_DEV_*_SPEC_PROFILE_* is
      MDC_DEV_SUB_SPEC_PROFILE_WATER_SENSOR = 4217 (0x1079).
    • If the PHD supports Smoke Sensor sub-specialization (profile):
      MDC_DEV_*_SPEC_PROFILE_* is
      MDC_DEV_SUB_SPEC_PROFILE_SMOKE_SENSOR = 4215 (0x1077)
    • If the PHD supports Property Exit Sensor sub-specialization (profile):
      MDC_DEV_*_SPEC_PROFILE_* is
      MDC_DEV_SUB_SPEC_PROFILE_PROPEXIT_SENSOR = 4220 (0x107C) (0x107B)
    • If the PHD supports Temperature Sensor sub-specialization (profile):
      MDC_DEV_*_SPEC_PROFILE_* is
      MDC_DEV_SUB_SPEC_PROFILE_TEMP_SENSOR = 4226 (0x1082).
    • If the PHD supports Usage Sensor sub-specialization (profile):
      MDC_DEV_*_SPEC_PROFILE_* is
      MDC_DEV_SUB_SPEC_PROFILE_USAGE_SENSOR = 4223 (0x107F).
    • If the PHD supports PERS Sensor sub-specialization (profile):
      MDC_DEV_*_SPEC_PROFILE_* is
      MDC_DEV_SUB_SPEC_PROFILE_PERS_SENSOR = 4214 (0x1076)
    • If the PHD supports CO Sensor sub-specialization (profile):
      MDC_DEV_*_SPEC_PROFILE_* is
      MDC_DEV_SUB_SPEC_PROFILE_CO_SENSOR = 4216 (0x1078)
    • If the PHD supports Gas Sensor sub-specialization (profile):
      MDC_DEV_*_SPEC_PROFILE_* is
      MDC_DEV_SUB_SPEC_PROFILE_GAS_SENSOR = 4218 (0x107A).
    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/TR/DGC/BV-010 | | | +| TP label | Unsupported Service Component 1 | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Unsupport 8; R | Unsupport 10; R | +| | | Unsupport_LAN 6; R | | +| Test purpose |

    Check that:

    Service component should notify the user of failure of the connection and corresponding reason, if the client has released or rejected the association due to service component does not support at least one Continua certified device class supported by the client component

    [AND]

    Service component with appropriate UI capabilities should use the following text string to notify the user of failure of the connection: "Thank you for choosing Continua certified personal health products. The device you are connecting either has not been Continua certified or the data is not intended for use in this solution. Please see your user manual for more details."

    This test procedure covers the scenario in which the simulated PHG does not request MDS attributes while they are in Waiting Approval state.

    | | | +| Applicability | C_AG_OXP_000 AND (C_AG_DGC_013 OR C_AG_DGC_014) | | | +| Other PICS | | | | +| Initial condition | The service under test and the simulated PHG are in the Unassociated state. | | | +| Test procedure |
    1. The simulated PHG receives an association request from the PHD under test.
    2. The PHG sends an association response with a result = accepted-unknown-config.
    3. The PHD sends with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. The PHG sends a Release Request (RLRQ) APDU the with reason "no-more-configurations".

    5. The PHD shall send a Release response (RLRE) with the reason "normal".

    6. Visual inspection of the PHD.

    | +| Pass/Fail criteria |

    IF C_AG_DCG_013 is supported: The error display should look something like the following (exact text not required): "Thank you for choosing Continua certified personal health products. The device you are connecting to either has not been Continua certified or the data is not intended for use in this solution. Please see your user manual for more details."

    IF C_AG_DGC_014 is supported (product has no text-based UI), some other visual indication is provided.

    In all the cases, the PHD shall respond to the RLRQ message with the reason "no-more-configs" by sending a RLRE.

    | +| Notes | | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|--------------------| +| TP Id | TP/PLT/PHD/TR/DGC/BV-010_A | | | | +| TP label | Unsupported Service Component 2 | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Unsupport 8; R | Unsupport 10; R | Unsupport_LAN 4; R | +| Test purpose |

    Check that:

    Service component should notify the user of failure of the connection and corresponding reason, if the client has released or rejected the association due to service component does not support at least one Continua certified device class supported by the client component

    [AND]

    Service component with appropriate UI capabilities should use the following text string to notify the user of failure of the connection: "Thank you for choosing Continua certified personal health products. The device you are connecting either has not been Continua certified or the data is not intended for use in this solution. Please see your user manual for more details."

    This test procedure covers the scenario in which the PHG does request MDS attributes in Waiting Approval state.

    | | | | +| Applicability | C_AG_OXP_000 AND (C_AG_DGC_013 OR C_AG_DGC_014) | | | | +| Other PICS | | | | | +| Initial condition | The service under test and the simulated PHG are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The PHG sends an association response with a result = accepted-unknown-config.
    3. 3. The PHD sends with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. IF NOT C_AG_OXP_293 THEN
      1. a. The PHG sends a roiv-cmip-get message with handle 0 and an empty list of attributes (to request all the attributes of the MDS object).
      2. b. The PHD responds to the Get request by sending a rors-cmip-get with all the supported attributes of the MDS.
    5. 5. The PHG sends a Release Request (RLRQ) APDU with the reason "no-more-configurations".
    6. 6. The PHD shall send a Release response (RLRE) with the reason "normal".
    7. 7. Visual inspection of the PHD.
    | | | | +| Pass/Fail criteria |

    IF C_AG_DCG_013 is supported: The error display should look something like the following (exact text not required): "Thank you for choosing Continua certified personal health products. The device you are connecting to either has not been Continua certified or the data is not intended for use in this solution. Please see your user manual for more details"

    IF C_AG_DGC_014 is supported (product has no text-based UI), some other visual indication

    | | | | + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------| +| | is provided.
    In all the cases, the PHD shall respond to the RLRQ message with the reason "no-more-configs" by sending a RLRE. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHD/TR/DGC/BV-011 | | | +| TP label | DataMessaging BiDIR QoS | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | QoS 1; M | | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | SysContext 1; M | | +| Test purpose | Check that:
    Service component supports to send the following messages with the desired QoS bins:
    • - DATA(Response-ConfirmSet()) {scanner OperationalState}
    • - DATA(Invoke-UnconfirmedEventReport(Buf-Scan-Report-*), ScanReportInfo*)
    • - DATA(Invoke-ConfirmedEventReport(Buf-Scan-Report-*), ScanReportInfo*)
    • - DATA(Response-ConfirmSet()) {scanner OperationalState}
    • - DATA(Invoke-UnconfirmedEventReport(Unbuf-Scan-Report-*), ScanReportInfo*)
    • - DATA(Invoke-ConfirmedEventReport(Unbuf-Scan-Report-*), ScanReportInfo*)
    • - DATA(Response-ConfirmGet()) {PM-Store attributes}
    • - DATA(Response-ConfirmedAction(Get-Segment-Info), SegmentInfoList)
    • - DATA(Response-ConfirmedAction(Trig-Segment-Data-Xfer), TrigSegmDataXferRsp)
    • - DATA(Invoke-ConfirmedEventReport(Segment-Data-Event), SegmentDataEvent)
    • - DATA(Response-ConfirmedAction(Clear-Segments)) DATA(Invoke-UnconfirmedEventReport (MDS-Dynamic-Data-Update-*), ScanReportInfo*)
    • - DATA(Invoke-ConfirmedEventReport (MDS-Dynamic-Data-Update-*), ScanReportInfo*)
    • - DATA(Response-ConfirmedAction(Set-Time))
    | | | +| Applicability | (C_AG_OXP_053 OR C_AG_OXP_008 OR C_AG_OXP_041 OR C_AG_OXP_046 OR C_AG_OXP_047) AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_071, C_AG_OXP_180 | | | +| Initial condition | The service under test and the simulated PHG are in the Operating state. | | | +| Test procedure | 1. IF the PHD under test supports fixed or variable format MDS event reports, it is forced to send a variable or fixed format MDS event report: roiv-cmip-confirmed-event-report with event-type:
    MDC_NOTI_SCAN_REPORT_FIXED
    MDC_NOTI_SCAN_REPORT_VAR
    MDC_NOTI_SCAN_REPORT_MP_VAR
    MDC_NOTI_SCAN_REPORT_MP_FIXED
    2. If the PHD supports Episodic Scanner objects, the simulated PHG sets to enable the Operational-State for the scanner object. IF the PHD supports confirmed Set, the PHD will send the response for the Set command: rors-cmip-confirmed-set. When the scanner object is enabled, the PHD under test will send a scanner object events roiv-cmip-confirmed-event-report with event-type:
    MDC_NOTI_UNBUF_SCAN_REPORT_GROUPED
    MDC_NOTI_UNBUF_SCAN_REPORT_MP_GROUPED
    MDC_NOTI_UNBUF_SCAN_REPORT_FIXED | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    MDC_NOTI_UNBUF_SCAN_REPORT_MP_FIXED

    MDC_NOTI_UNBUF_SCAN_REPORT_VAR

    MDC_NOTI_UNBUF_SCAN_REPORT_MP_VAR

    3. If the PHD supports Periodic Scanner objects, the simulated PHG sets to enable the Operational-State scanner object. IF the PHD supports confirmed Set, the PHD will send the response for the Set command: rors-cmip-confirmed-set. When the scanner object is enabled, the PHD under test will send a scanner object events roiv-cmip-confirmed-event-report with event-type:

    MDC_NOTI_BUF_SCAN_REPORT_GROUPED

    MDC_NOTI_BUF_SCAN_REPORT_MP_GROUPED

    MDC_NOTI_BUF_SCAN_REPORT_FIXED

    MDC_NOTI_BUF_SCAN_REPORT_MP_FIXED

    MDC_NOTI_BUF_SCAN_REPORT_VAR

    MDC_NOTI_BUF_SCAN_REPORT_MP_VAR

    4. If the PHD supports Set-Time", the simulated PHG sends a roiv-cmip-confirmed-action with action-type = MDC_ACT_SET_TIME. The PHD shall reply with a rors-cmip-confirmed-action with action-type=MDC_ACT_SET_TIME.

    5. If the PHD supports PM-Store:

    • The simulated PHG will perform a Get-Segment-Info action, the PHD under test shall reply with rors-confirmed-action with action-type= MDC_ACT_SEG_GET_INFO.
    • The simulated PHG will perform a Trig-Segment-Data-Xfer action, the PHD under test shall reply with rors-confirmed-action with action-type= MDC_ACT_SEG_TRIG_XFER, and the PHD under test will send Segment-Data-Event, roiv-cmip-confirmed-event report with event-type=MDC_NOTI_SEGMENT_DATA

    6. If the PHD supports PM-Store and Clear-Segment action, the simulated PHG will perform a Get request for the PM-Store attributes to read Clear-Timeout attribute. After this, it will perform the Clear-Segments. Then, the simulated PHG will perform a Clear-Segment action, and the PHD shall reply with rors-cmip-confirmed-action with action-type=MDC_ACT_SEG_CLR.

    | +| Pass/Fail criteria | The PHD shall use a reliable channel (QoS best.medium) for the messages sent by it and specified in the test procedure. | +| Notes | Roer and Rorj messages are checked in TP/PLT/PHD/OXP/BV-003_D and TP/PLT/PHD/OXP/BV-003_F. | + +| | | | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHD/TR/DGC/BV-013 | | | +| TP label | Continua_Nomenclature_Codes | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Conformance 3; M | | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | InfoExt 3; O | | +| Test purpose |

    Check that:

    Service component that use private nomenclature codes allocates them from the range 0xF000 through 0xFBFF

    [AND]

    Vendor specified classes may be defined. Vendor specified objects may be created from those classes or any classes defined in this series of standards

    | | | +| Applicability | C_AG_OXP_000 | | | +| Other PICS | C_AG_DGC_009, C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_189, C_AG_OXP_293 | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The service under test and the simulated PHG are in the Unassociated state. | +| Test procedure |
    1. 1. The PHD sends an association request (AarqApdu) from the PHD under test.
    2. 2. The simulated PHG sends an association response (AareApdu) with a result = accepted-unknown-config.
    3. 3. The PHD sends a roiv-cmip-confirmed-event-report message with an MDC_NOTI_CONFIG event to send its configuration to the PHG. Check all object types and attribute types to ensure they are not in the range 0xFC00 to 0xFFFF.
    4. 4. The PHG accepts the configuration by sending a rors-cmip-confirmed-event-report with reason=accepted.
    5. 5. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    6. 6. IF C_AG_OXP_189 is supported: PHD sends a roiv-cmip-event-report message (or roiv-cmip-confirmed-event-report) with event-type=MDC_NOTI_SCAN_REPORT_*, with measurements. Check that none of the attribute types are in the range 0xFC00 to 0xFFFF.
    | +| Pass/Fail criteria | In steps 1, 3 and 6, if the PHD uses Private Nomenclature Codes (C_AG_DGC_009 = TRUE), Private Nomenclature values must be between 0xF000 through 0xFBFF, otherwise, nomenclature values must be between 0x0000 through 0xEFFF (no Private Nomenclature values must be present). | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/PLT/PHD/TR/DGC/BV-014 | | | +| TP label | PM-Store Date-and-Time adjustment while transfer PM-Segment | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | | Communication 15; M | +| Test purpose | Check that:

    Continua PAN service components that are in the middle of a PM-Segment transfer shall not update the PM-Segment object Date-and-Time-Adjustment attribute regardless of any time changes that occur while the segment continues to be transferred | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_036 | | | +| Other PICS | | | | +| Initial condition | The service under test and the simulated PHG are in the Operating state. The PHD must have stored measurements in the PM-Store object to transfer it. | | | +| Test procedure |
    1. 1. The simulated PHG issues a Get-Segment-Info with SegmSelection set to all-segments.
    2. 2. Inform the operator that the simulated PHG is going to trigger a Segment Data event and ask the operator to force the PHD to make a noticeable change in the Date or Time while it is transferring the PM-Segment.
    3. 3. The simulated PHG sends a request for the PM-Segment Data to one of the PM-Segments that contains data:
      1. a. Data APDU
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Type = Invoke Confirmed Action
    • HANDLE = obj-handle
    • Action = MDC_ACT_SEG_TRIG_XFER
    • TrigSegmDataXferReq = <Instance number of the selected PM-Segment that contains the data>

    4. The PHD issues an action response:

    • a. Data APDU
      • Type = Invoke Confirmed Action
      • HANDLE = obj-handle
    • b. Action = MDC_ACT_SEG_TRIG_XFER
      • TrigSegmDataXferRsp = <Same Instance number> tsxr-successful (0x00 0x00)

    5. The PHD under Test starts Data transfer:

    • a. Data APDU
      • Invoke CfmEventReport
      • Action = MDC_NOTI_SEGMENT_DATA
      • SegmentDataEvent

    6. The simulated PHG response to transferred data APDU's:

    • a. Data APDU
      • Type = Invoke Confirmed Action
      • HANDLE = obj-handle
      • Action = MDC_NOTI_SEGMENT_DATA
      • SegmentDataResult

    7. Wait until all the data is transferred by the PHD under test.

    8. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.

    9. The PHD shall respond to the Get-Segment-Info, indicating the attributes of the PM-Segment:

    • ▪ Date-and-Time adjustment attribute is not present,

    10. Repeat from step 2 to step 9 until every PM-Store and segment instance has been checked.

    | +| Pass/Fail criteria | In step 9, the Date-and-Time adjustment attribute must not be present. | +| Notes | | + +### A.3 Subgroup 1.1.2 – USB design guidelines (UDG) + +| | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------| +| TP Id | TP/PAN/PHD/TR/UDG/BV-000 | | | +| TP label | Association process | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Data_mess 1; M | Data_mess 3;M | +| | | Multi 1; M | Data_mess 4; O | +| Test purpose | Check that:

    Service component sets the USB PHDC v1.0 bPHDCDataCode field of the PHDC Class Function descriptor equal to PHDC_11073_20601

    [AND]

    Service component sets the wDevSpecializations field(s) to the corresponding ISO/IEEE 11073-20601-2008 and ISO/IEEE 11073-20601A-2010 MDC_DEV_SPEC_PROFILE_* value(s) corresponding to the Certified Device Class(es) the component supports

    [AND] | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Service component may add additional ISO/IEEE 11073-20601-2008 and ISO/IEEE 11073-20601A-2010 MDC_DEV_SPEC_PROFILE_* value(s) corresponding to supported IEEE specializations that are not Continua certified in the wDevSpecializations array

    [AND]

    Service component, whether multi-function or single function, implements one and only one USB PHDC interface for the component's ISO/IEEE 11073 -20601-2008 and ISO/IEEE 11073-20601A-2010 association

    | +| Applicability | C_AG_OXP_000 AND C_AG_UDG_001 | +| Other PICS | C_AG_DGC_016 | +| Initial condition | The service under test is in in the Disconnected state. | +| Test procedure |
    1. 1. Connect the USB connector of the PHD to the simulated PHG through the USB sniffer.
    2. 2. Capture the descriptors. Check that:
      1. a. In the PHDC Class Function descriptor (20h), the bPHDCDataCode field is equal to 02h (PHDC_11073_20601).
      2. b. In the PHDC 11073 PHD Function Extension descriptor (30h), the wDevSpecializations field(s) of the is set to the corresponding ISO/IEEE 11073-20601 version 1.0 MDC_DEV_SPEC_PROFILE_* value(s) corresponding to the Certified Device Class or Classes the component supports, as defined in the certification application (values below are in decimal format):
        • • Pulse oximeter (MDC_DEV_SPEC_PROFILE_PULS_OXIM 4100)
        • • Blood pressure monitor (MDC_DEV_SPEC_PROFILE_BP 4103)
        • • Temperature (MDC_DEV_SPEC_PROFILE_TEMP 4104)
        • • Weighing scales (MDC_DEV_SPEC_PROFILE_SCALE 4111)
        • • Glucose meter (MDC_DEV_SPEC_PROFILE_GLUCOSE 4113)
        • • Cardiovascular (MDC_DEV_SPEC_PROFILE_HF_CARDIO 4137)
        • • Strength (MDC_DEV_SPEC_PROFILE_HF_STRENGTH 4138)
        • • Activity hub (MDC_DEV_SPEC_PROFILE_AI_ACTIVITY_HUB 4167)
        • • Adherence monitor (MDC_DEV_SPEC_PROFILE_AI_MED_MINDER 4168)
        • • Peak flow (MDC_DEV_SPEC_PROFILE_PEFM 4117)
        • • Body composition analyser (MDC_DEV_SPEC_PROFILE_BCA 4116)
        • • Basic electrocardiograph specialization/Heart rate profile or basic electrocardiograph Specialization/Simple ECG profile (MDC_DEV_SPEC_PROFILE_ECG 4102)
        • • International normalized ratio (MDC_DEV_SPEC_PROFILE_COAG 4114)
        • • Sleep apnoea breathing therapy equipment (MDC_DEV_SPEC_PROFILE_SABTE 4121)
        • • Insulin pump (MDC_DEV_SPEC_PROFILE_INSULIN_PUMP 4115)
        • • Continuous glucose monitor (MDC_DEV_SPEC_PROFILE_CGM 4122)
        • • Power status monitor specialization with Simple PSM or Advanced PSM profile (MDC_DEV_SPEC_PROFILE_PSM 4124)
      3. c. If (C_AG_DGC_016), some other additional device specializations may be contained in the wDevSpecializations array.
    3. 3. If the device has multiple interfaces, only one interface implements the USB PHDC device class (i.e., bInterfaceClass = 0x0F in the interface descriptor preceding the descriptors above or bDeviceClass = 0x0F in the device descriptor preceding the descriptors above).
    | +| Pass/Fail criteria | The above fields are as requested. | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------| +| TP Id | TP/PAN/PHD/TR/UDG/BV-001 | | | +| TP label | QoS management | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | QoS 1; C | QoS 2; C | +| Test purpose | Check that:

    Service component that implements the Continua best.medium QoS bin utilizes the USB PHDC best.medium QoS bin to do this

    [AND]

    Service component that implements the Continua good.medium QoS bin utilizes the USB PHDC good.medium QoS bin to do this | | | +| Applicability | C_AG_OXP_000 AND C_AG_UDG_001 | | | +| Other PICS | C_AG_DGC_011 | | | +| Initial condition | The service under test is in the Disconnected state. | | | +| Test procedure | 1. Connect the USB connector of the PHD to the simulated PHG, through the USB sniffer.
    2. Capture the descriptors.
    3. The field bmLatencyReliability of each BULK endpoint descriptor received is analysed.
    4. If C_AG_DGC_011, the good.medium bit (1) is active.
    5. The best.medium bit (3) is active. | | | +| Pass/Fail criteria | The above fields are as requested. | | | +| Notes | The rest of this test procedure is tested in TP/PLT/PHD/TR/DGC/BV-011. | | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------| +| TP Id | TP/PAN/PHD/TR/UDG/BV-002 | | | +| TP label | USB Data rates | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Data_Rate 1; M | Data_Rate 2; R | +| Test purpose | Check that:

    Service component does not use low speed (USB 1.1)

    [AND]

    Continua PAN wired USB components should implement USB 2.0

    [AND]

    Continua PAN wired USB components shall implement at least USB 1.1 or any superior version compatible with USB 1.1 | | | +| Applicability | C_AG_OXP_000 AND C_AG_UDG_001 | | | +| Other PICS | | | | +| Initial condition | The service under test is in the Disconnected state. | | | +| Test procedure | 1. Connect the USB connector of the PHD to the simulated PHG, through the USB sniffer.
    2. Capture the negotiation process and the device descriptor.
    3. Check the data rate of the PHD during negotiation.
    4. Inspect the device descriptor and check the field bcdUSB. | | | +| Pass/Fail criteria | In step 3, the data rate must be set to Full Speed (FS) or High Speed (HS), but never Low Speed (LS)

    In step 4, indicate the value of the bcdUSB. A value of 0200h or greater (=USB2.0) is recommended, but a value of 0110h (USB1.1) or greater is also accepted. | | | +| Notes | | | | + +### A.4 Subgroup 1.1.3 – Bluetooth design guidelines (BDG) + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PAN/PHD/TR/BDG/BI-000 | | | +| TP label | Service component is not allowed to initiate discovery | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 2; R | | +| Test purpose | Check that:
    PHD should not be allowed to initiate a discovery procedure | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in the Disconnected state and they have not been paired before. | | | +| Test procedure | NOTE: This test case must be executed manually. Bluetooth sniffer is needed to perform the verification required in this test case.
    1. Turn on the PHD under test and enable Bluetooth transport.
    2. With the simulated PHG and the Bluetooth sniffer, check if the PHD under test initiates a discovery process within 5 minutes. | | | +| Pass/Fail criteria | The PHD under test should not initiate a discovery process within 5 minutes If it has initiated a discovery process, the test operator must include a warning message in the manual verdict. | | | +| Notes | Due to CESL restrictions, this test case has to be executed manually.
    A Bluetooth sniffer is needed for this test case. | | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PAN/PHD/TR/BDG/BI-001 | | | +| TP label | Abnormal cases management - Change of information without pairing | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 8; M | | +| Test purpose | Check that:
    The PHD does not exchange data (except HDP SPD record and static information) with PHG for which a pairing has not been established | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in the Disconnected state and they have not been paired before. | | | +| Test procedure | 1. Reset the PHD under test to the default configuration and turn it on.
    2. The simulated PHG initiates discovery, it finds the PHD under test, but it does not start the pairing process.
    3. The simulated PHG waits until a 2 minute timeout expires. During this time, the PHD under test shall not exchange data (except HDP SDP record and static information) with the simulated PHG. | | | +| Pass/Fail criteria | The PHD under test does not exchange data without pairing. | | | +| Notes | | | | + +| | | | | +|-----------------|---------------------------------------------|------------------------|-------------| +| TP Id | TP/PAN/PHD/TR/BDG/BI-002 | | | +| TP label | Abnormal cases management - Pairing failure | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Notify 4; R | Notify 6; R | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    When a pairing fails, the PHD should inform the user, whenever possible, whether the failure was because no data types are supported in common by both client component and service component (incompatible device), or the pairing failed (pairing failure)

    [AND]

    When any authentication/security failure is encountered by the PHD, it should notify the user whenever possible

    | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 AND C_AG_BDG_002 | +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in the Disconnected state and they have not been paired before. | +| Test procedure |
    1. Configure the simulated PHG with a supported device specialization different to the device specialization supported by the PHD under test.
    2. Enable pairable mode in the simulated PHG.
    3. Reset the PHD under test to the default configuration and turn it on.
    4. The simulated PHG initiates a discovery process, it finds the PHD under test and starts a pairing process with it. The PHD under test should notify an error due to both devices not having any device specialization in common.
    5. Configure the simulated PHG with a supported device specialization that matches the PHD under test device specialization.
    6. Disable the pairable mode in the simulated PHG.
    7. Turn off the PHD under test and reset it to the default configuration and turn it on.
    8. The simulated PHG initiates a discovery process, it finds the PHD under test and starts a pairing process with it. The PHD under test should notify an error as the pairing cannot be completed.
    9. Check if the PHD under test has notified the two previous errors using different procedures/indications.
    | +| Pass/Fail criteria |

    In step 3, the PHD under test should notify a pairing error. If this notification is not indicated, the test tool gives a Warning message.

    In step 8, the PHD under test should notify a pairing error. If this notification is not indicated, the test tool gives a Warning message.

    The PHD under test should issue different kind of indications for both pairing errors. If both indications are not different, the test tool gives a Warning message.

    | +| Notes | | + +| | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------------| +| TP Id | TP/PAN/PHD/TR/BDG/BV-000 | | | +| TP label | Successfully Discovery and Pairing process | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 4; M | Discovery_Pairing 12; R | +| Test purpose |

    Check that:

    Once the PHD has been made discoverable, it shall support pairing with compatible PHGs.

    [AND]

    If a new pairing relationship is created, then the PHD should notify to the user whenever possible

    [AND]

    When the PHD is discoverable and successfully completes a pairing procedure, then it should immediately become undiscoverable

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 | | | +| Other PICS | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHD under test and the simulated PHG support the same device specialization, they are in the Disconnected state and they have not been paired before. | +| Test procedure |
    1. Turn on the PHD under test and configure it as a discoverable Bluetooth device, as stated in the product documentation.
    2. The test tool simulated PHG initiates a discovery process, it discovers the PHD under test and it starts a pairing process with PHD under test.
    3. When the PHD under test is paired, check if it notifies the user (by any procedure defined in the user manual).
    4. The simulated PHG initiates a new discovery process. Check if the PHD under test is discoverable or not.
    | +| Pass/Fail criteria |

    In step 3, the PHD under test should show any indication to the user indicating a pairing has succeeded. If this notification is not indicated, the test tool gives a Warning message.

    In step 4, the PHD under test should not be discoverable. If it is discoverable, the test tool gives a Warning message.

    | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PAN/PHD/TR/BDG/BV-001_A | | | +| TP label | Service component timer for discoverable mode | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 11; R | | +| Test purpose |

    Check that:

    The PHD should provide a documented minimum duration for discoverable mode (decided by the vendor), once initiated, after which it ceases to be discoverable.

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG support the same device specialization, they are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. Turn on the PHD under test and configure it as a discoverable Bluetooth device.
    2. The simulated PHG waits a quantity of time Twait1:
      Twait1 = Tdiscoverable - Tguard
    3. When Twait1 expires, the simulated PHG initiates a discovery process. Check if the simulated PHG finds the PHD under test.
    4. The simulated PHG waits a quantity of time Twait2 (from initial time = 0):
      Twait2 = Tdiscoverable + Tguard
    5. When Twait2 expires, the simulated PHG initiates a new discovery process. Check if the simulated PHG finds the PHD under test.
    | | | +| Pass/Fail criteria |

    In step 3, the PHD under test is discoverable.

    In step 5, the PHD under test should not be discoverable. If it is discoverable, the test tool gives a Warning message.

    | | | +| Notes |

    Tdiscoverable is defined in PIXIT I_AG_BDG_001

    Tguard = Tdiscoverable/2

    | | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PAN/PHD/TR/BDG/BV-001_B | | | +| TP label | Pairing prevented in non-discoverable state | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 13; R | | +| Test purpose | Check that:
    If the PHD is able to prevent pairing while in non-discoverable states, then it does so | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 AND C_AG_BDG_003 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG support the same device specialization, they are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. Turn on the PHD under test and configure it as non-discoverable Bluetooth device.
    2. The simulated PHG initiates a discovery process, it does not find the PHD under test.
    3. The simulated PHG initiates a pairing process with the PHD under test (although it has not been discovered).
    | | | +| Pass/Fail criteria | In step 3, the PHD under test and the simulated PHG cannot be paired. If the pairing process can be completed successfully, the test tool gives a Warning message. | | | +| Notes | | | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| TP Id | TP/PAN/PHD/TR/BDG/BV-002 | | | +| TP label | Service component mode of "discoverable by client component" | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 7; M | Discovery_Pairing 9; R | +| Test purpose | Check that:
    Once PHD has been paired with a PHG, it shall remain possible to re-initiate the mode "discoverable by the client component (manager)"
    [AND]
    By default, PHD under test should not be discoverable unless it puts in that mode | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG support the same device specialization, they are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. Reset the PHD under test to the default configuration and turn it on.
    2. The simulated PHG initiates discovery. Check if the PHD under test is discoverable.
    3. Set the PHD under test to "discoverable by the client (manager)" as defined in the product documentation.
    4. The simulated PHG initiates a discovery process, it finds the PHD under test and it establishes a pairing with PHD under test.
    5. Disconnect PHD under test and the simulated PHG
    6. In the PHD under test, re-initiate the mode "discoverable by the client (manager)" as it is described in the product documentation.
    7. The simulated PHG initiates another discovery process. Check if the simulated PHG finds the PHD under test.
    | | | +| Pass/Fail criteria | In step 2, the PHD under test should not be discoverable. If it is discoverable, the test tool gives a Warning message.
    In step 7, the PHD under test shall be discoverable. | | | + +| | | +|--------------|--| +| Notes | | +|--------------|--| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| TP Id | TP/PAN/PHD/TR/BDG/BV-003 | | | +| TP label | HDP SDP Record contents | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discoverable_mode 2; R | Discoverable_mode 3; M | +| Test purpose |

    Check that:

    When possible, the PHD in "discoverable mode" should allow access to their SDP entries without first requiring a pairing to be established

    [AND]

    The specializations claimed in Continua certification shall match the list of specializations advertised in the PHD HDP SDP record

    [AND]

    PHD HDP SDP record may contain additional specialization identifiers that are not Continua certified

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG support the same device specialization, they are in the Disconnected state and they have not been paired before. | | | +| Test procedure |

    NOTE: This test case must be executed manually. A Bluetooth sniffer is needed to perform the verification required in this test case.

    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device.
    2. 2. The simulated PHG initiates a discovery process, it finds the device, but it does not start the pairing process.
    3. 3. The simulated PHG accesses the PHD under test SDP record and recovers the Supported Features (MDEP List) attribute
    4. 4. If it is not possible to access the SDP record before pairing (step 3 cannot be executed), pair the PHD under test with the simulated PHG and then the simulated PHG accesses the PHD under test SDP record and recovers the Supported Features (MDEP List) attribute.
    5. 5. Check for each entry of the MDEP List attribute the MDEP Data Type element value. The MDEP List shall contain an entry per device specialization claimed in the Continua certification and the corresponding MDEP Data Type element value shall match with the Bluetooth Assigned number for each device specialization:
      • • If Glucose meter specialization is going to be certified (C_AG_OXP_233 = TRUE) then MDEP Data Type element = 0x1011 (4113 decimal).
      • • If Thermometer specialization is going to be certified (C_AG_OXP_234 = TRUE) then MDEP Data Type element= 0x1008 (4104 decimal)
      • • If Pulse oximeter specialization is going to be certified (C_AG_OXP_235 = TRUE) then MDEP Data Type element = 0x1004 (4102 decimal)
      • • If Blood pressure monitor specialization is going to be certified (C_AG_OXP_236 = TRUE) then MDEP Data Type element = 0x1007 (4103 decimal).
      • • If Weighing scales specialization is going to be certified (C_AG_OXP_237 = TRUE) then MDEP Data Type element = 0x100F (4111 decimal)
      • • If Cardiovascular specialization is going to be certified (C_AG_OXP_238 = TRUE) then MDEP Data Type element = 0x1029 (4137 decimal)
      • • If Step counter sub-specialization (profile) is going to be certified (C_AG_OXP_239 = TRUE) then MDEP Data Type element = 0x1068 (4200 decimal).
      • • If Strength fitness specialization is going to be certified (C_AG_OXP_240 = TRUE) then MDEP Data Type element = 0x102A (4138 decimal)
    | | | + +- If Adherence monitor specialization is going to be certified (C\_AG\_OXP\_241 = TRUE) then MDEP Data Type element = 0x1048 (4168 decimal) + - If Peak flow specialization is going to be certified (C\_AG\_OXP\_243 = TRUE) then MDEP Data Type element = 0x1015 (4117 decimal) + - If Activity hub specialization is going to be certified (C\_AG\_OXP\_244 = TRUE) then MDEP Data Type element = 0x1047 (4167 decimal) + - If Fall sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_245 = TRUE) then MDEP Data Type element = 0x1075 (4213 decimal) + - If Motion sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_246 = TRUE) then MDEP Data Type element = 0x107B (4219 decimal) + - If Enuresis sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_247 = TRUE) then MDEP Data Type element = 0x107D (4221 decimal) + - If Contact closure sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_248 = TRUE) then MDEP Data Type element = 0x107E (4222 decimal) + - If Switch Sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_249 = TRUE) then MDEP Data Type element = 0x1080 (4224 decimal) + - If Dosage sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_250 = TRUE) then MDEP Data Type element = 0x1081 (4225 decimal) + - If Water sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_251 = TRUE) then MDEP Data Type element = 0x1079 (4217 decimal) + - If Smoke sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_252 = TRUE) then MDEP Data Type element = 0x1077 (4215 decimal) + - If Property exit sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_253 = TRUE) then MDEP Data Type element = 0x107C (4220 decimal) + - If Temperature sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_254 = TRUE) then MDEP Data Type element = 0x1082 (4226 decimal) + - If Usage sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_255 = TRUE) then MDEP Data Type element = 0x107F (4223 decimal) + - If PERS sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_256 = TRUE) then MDEP Data Type element = 0x1076 (4214 decimal) + - If CO sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_257 = TRUE) then MDEP Data Type element = 0x1078 (4216 decimal) + - If Gas sensor sub-specialization (profile) is going to be certified (C\_AG\_OXP\_258 = TRUE) then MDEP Data Type element = 0x107A (4218 decimal) + - If Body Composition Analyser specialization is going to be certified (C\_AG\_OXP\_259 = TRUE) then MDEP Data Type element = 0x1014 (4116 decimal) + - If Basic electrocardiograph specialization/Simple ECG profile (C\_AG\_OXP\_261 = TRUE) is going to be certified then MDEP Data Type element = 0x1006 (4102 decimal) + - If Basic electrocardiograph specialization/Heart rate profile (C\_AG\_OXP\_262 = TRUE) is going to be certified then MDEP Data Type element = 0x1006 (4102 decimal) +6. Check for each entry of the MDEP List attribute the MDEP Data Type element value. The MDEP List may contain an entry per Continua device specialization that is not claimed in the Continua certification but it is supported by the PHD under test and the corresponding MDEP Data Type element value shall match with the Bluetooth Assigned number for each device specialization +- If the PHD supports Glucose meter specialization (C\_AG\_OXP\_204 = TRUE) and (C\_AG\_OXP\_233 = FALSE) then MDEP Data Type element may contain 0x1011 (4113 decimal) value. + +- If the PHD supports Thermometer specialization (C\_AG\_OXP\_205 = TRUE) and (C\_AG\_OXP\_234 = FALSE) then MDEP Data Type element may contain 0x1008 (4104 decimal) value. +- If the PHD supports Pulse oximeter specialization (C\_AG\_OXP\_206 = TRUE) and (C\_AG\_OXP\_235 = FALSE) then MDEP Data Type element may contain 0x1004 (4102 decimal) value. +- If the PHD supports Blood pressure monitor specialization (C\_AG\_OXP\_207 = TRUE) and (C\_AG\_OXP\_236 = FALSE) then MDEP Data Type element may contain 0x1007 (4103 decimal) value. +- If the PHD supports Weighing scales specialization (C\_AG\_OXP\_208 = TRUE) and (C\_AG\_OXP\_237 = FALSE) then MDEP Data Type element may contain 0x100F (4111 decimal) value. +- If the PHD supports Cardiovascular specialization (C\_AG\_OXP\_209 = TRUE) and (C\_AG\_OXP\_238 = FALSE) then MDEP Data Type element may contain 0x1029 (4137 decimal) value. +- If the PHD supports Step counter sub-specialization (profile) (C\_AG\_OXP\_210 = TRUE) and (C\_AG\_OXP\_239 = FALSE) then MDEP Data Type element may contain 0x1068 (4200 decimal) value. +- If the PHD supports Strength fitness specialization (C\_AG\_OXP\_211 = TRUE) and (C\_AG\_OXP\_240 = FALSE) then MDEP Data Type element may contain 0x102A (4138 decimal) value. +- If the PHD supports Adherence monitor specialization (C\_AG\_OXP\_212 = TRUE) and (C\_AG\_OXP\_241 = FALSE) then MDEP Data Type element may contain 0x1048 (4168 decimal) value. +- If the PHD supports Peak flow specialization (C\_AG\_OXP\_214 = TRUE) and (C\_AG\_OXP\_243 = FALSE) then MDEP Data Type element may contain 0x1015 (4117 decimal) value. +- If the PHD supports Activity hub specialization (C\_AG\_OXP\_215 = TRUE) and (C\_AG\_OXP\_244 = FALSE) then MDEP Data Type element may contain 0x1047 (4167 decimal) value. +- If the PHD supports Fall sensor sub-specialization (profile) (C\_AG\_OXP\_216 = TRUE) and (C\_AG\_OXP\_245 = FALSE) then MDEP Data Type element may contain 0x1075 (4213 decimal) value. +- If the PHD supports Motion sensor sub-specialization (profile) (C\_AG\_OXP\_217 = TRUE) and (C\_AG\_OXP\_246 = FALSE) then MDEP Data Type element may contain 0x107B (4219 decimal) value. +- If the PHD supports Enuresis sensor sub-specialization (profile) (C\_AG\_OXP\_218 = TRUE) and (C\_AG\_OXP\_247 = FALSE) then MDEP Data Type element may contain 0x107D (4221 decimal) value. +- If the PHD supports Contact closure sensor sub-specialization (profile) (C\_AG\_OXP\_219 = TRUE) and (C\_AG\_OXP\_248 = FALSE) then MDEP Data Type element may contain 0x107E (4222 decimal) value. +- If the PHD supports Switch sensor sub-specialization (profile) (C\_AG\_OXP\_220 = TRUE) and (C\_AG\_OXP\_249 = FALSE) then MDEP Data Type element may contain 0x1080 (4224 decimal) value. +- If the PHD supports Dosage sensor sub-specialization (profile) (C\_AG\_OXP\_221 = TRUE) and (C\_AG\_OXP\_250 = FALSE) then MDEP Data Type element may contain 0x1081 (4225 decimal) value. +- If the PHD supports Water sensor sub-specialization (profile) (C\_AG\_OXP\_222 = TRUE) and (C\_AG\_OXP\_251 = FALSE) then MDEP Data Type element may contain 0x1079 (4217 decimal) value. +- If the PHD supports Smoke sensor sub-specialization (profile) (C\_AG\_OXP\_223 = TRUE) and (C\_AG\_OXP\_252 = FALSE) then MDEP Data Type element may contain 0x1077 (4215 decimal) value. +- If the PHD supports Property exit sensor sub-specialization (profile) (C\_AG\_OXP\_224 = TRUE) and (C\_AG\_OXP\_253 = FALSE) then MDEP Data Type element may contain 0x107C (4220 decimal) + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • If the PHD supports Temperature sensor sub-specialization (profile) (C_AG_OXP_225 = TRUE) and (C_AG_OXP_254 = FALSE) then MDEP Data Type element may contain 0x1082 (4226 decimal) value.
    • • If PHD supports Usage sensor sub-specialization (profile) (C_AG_OXP_226 = TRUE) and (C_AG_OXP_255 = FALSE) then MDEP Data Type element may contain 0x107F (4223 decimal) value.
    • • If the PHD supports PERS sensor sub-specialization (profile) (C_AG_OXP_227 = TRUE) and (C_AG_OXP_256 = FALSE) then MDEP Data Type element may contain 0x1076 (4214 decimal) value.
    • • If the PHD supports CO sensor sub-specialization (profile) (C_AG_OXP_228 = TRUE) and (C_AG_OXP_257 = FALSE) then MDEP Data Type element may contain 0x1078 (4216 decimal) value.
    • • If the PHD supports Gas sensor sub-specialization (profile) (C_AG_OXP_229 = TRUE) and (C_AG_OXP_258 = FALSE) then MDEP Data Type element may contain 0x107A (4218 decimal) value.
    • • If the PHD supports Body composition analyser specialization (C_AG_OXP_283 = TRUE) and (C_AG_OXP_259 = FALSE) then MDEP Data Type element may contain 0x1014 (4116 decimal)
    • • If the PHD supports Basic electrocardiograph specialization/Simple ECG profile (C_AG_OXP_281 = TRUE) (C_AG_OXP_261 = FALSE) then MDEP Data Type element may contain 0x1006 (4102 decimal)
    • • If the PHD supports Basic electrocardiograph specialization/Heart rate profile (C_AG_OXP_282 = TRUE) and (C_AG_OXP_262 = FALSE) is going to be certified then MDEP Data Type element may contain 0x1006 (4102 decimal)
    | +| Pass/Fail criteria |

    In step 3, the PHD should allow access to its SDP record. If it is not allowed the test operator must include a warning message in the manual verdict.

    In step 5 the specializations claimed in the Continua certification shall match the list of specializations advertised in the PHD under test HDP SDP record

    In step 6, the PHD under test HDP SDP record may contain other Continua device specializations that the PHD supports but are not going to be certified.

    | +| Notes | Bluetooth MDEP assigned numbers are available at https://www.bluetooth.org/Technical/AssignedNumbers/host_operating.htm | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PAN/PHD/TR/BDG/BV-004 | | | +| TP label | Pairing data storage | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 14; M | | +| Test purpose |

    Check that:

    PHD shall store the pairing data from at least the most recently paired device in such a way that the data will be retained through normal power interruptions, including battery replacement

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. 1. Reset the PHD under test to the default configuration and turn it on.
    2. 2. The simulated PHG initiates a discovery process, it finds the PHD under test and it establishes a pairing with PHD under test.
    3. 3. Turn the PHD under test off by removing the batteries or unplugging the power supply.
    4. 4. Turn on the PHD under test again.
    5. 5. The simulated PHG initiates a Bluetooth connection with the PHD under test. Check if the pairing process is dispatched again.
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | In Step 5, the pairing process shall not be dispatched again because both devices have stored the pairing data from the previous pairing process. | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PAN/PHD/TR/BDG/BV-005 | | | +| TP label | FCS Data Channel | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | QoS 3; R | | +| Test purpose | Check that:

    When possible and appropriate to the device, Continua PAN wireless service components should use FCS for all data channel | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 | | | +| Other PICS | C_AG_BDG_004, C_AG_BDG_005 | | | +| Initial condition | The service under test and the simulated PHG are in the Disconnected state. | | | +| Test procedure | Check PICS: C_AG_BDG_004 and C_AG_BDG_005 | | | +| Pass/Fail criteria |
    • If one of these PICS or both PICS are set to TRUE, the test case gives a warning message: "The Continua requirement that Continua wireless service components should use FCS for all data channels is probably not being met. It is recommended that you assess whether FCS is possible and appropriate for your device and enable it if so."
    • If both PICS are set to FALSE, the test case will not give a warning message.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PAN/PHD/TR/BDG/BV-006 | | | +| TP label | Secure Simple Pairing support | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 19; M | | +| Test purpose | Check that:

    PHD shall support at least one of the following Bluetooth 2.1 pairing methods depending on its I/O capabilities and appropriate security for the PHD device type: Just Works, Numeric Comparison, or Passkey Entry | | | +| Applicability | C_AG_OXP_000 AND C_AG_BDG_001 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG support the same device specialization, they are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. Check the PHD under test secure simple pairing (SSP) support declared in PIXIT I_AG_BDG_004.
    2. Check the PHD under test IO capabilities declared in PIXIT I_AG_BDG_005, the Man In The Middle (MITM) protection declared in PIXIT I_AG_BDG_006 and the Association Model declared in PIXIT I_AG_BDG_007
      1. IF the PHD under test does not support MITM protection (PIXIT I_AG_BDG_006 = FALSE) THEN
        • IF the PHD under test supports Just Works Association Model (PIXIT I_AG_BDG_007 = 0) THEN the test tool simulated PHG is configured with NoInputOutput capabilities and without MITM support
        • IF the PHD under test supports the Numeric Comparison or the Passkey Entry Association Model (PIXIT I_AG_BDG_007 = 1 or 2) THEN the combination of IO capabilities, the Association Model and MITM support declared by the PHD under test in PIXITs is not feasible and the test case ends giving a FAIL verdict
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    due to inconsistency among the PHD under test SSP features declared in PIXITs

    b. IF the PHD under test supports MITM protection (PIXIT I_AG_BDG_006 = TRUE) THEN

    • • IF the PHD under test supports the Just Works Association Model (PIXIT I_AG_BDG_007 = 0) THEN the combination of IO capabilities, Association Model and MITM support declared by the PHD under test in PIXITs is not feasible and the test case ends giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs
    • • IF the PHD under test supports the Numeric Comparison Association Model (PIXIT I_AG_BDG_007 = 1) and DisplayYesNo capabilities (PIXIT I_AG_BDG_005 = 1) THEN the test tool simulated PHG is configured with DisplayYesNo capabilities and with MITM support
    • • IF the PHD under test supports the Numeric Comparison Association Model (PIXIT I_AG_BDG_007 = 1) and DisplayOnly or KeyboardOnly capabilities (PIXIT I_AG_BDG_005 = 0 or 2) THEN the combination of IO capabilities, Association Model and MITM support declared by the PHD under test in PIXITs is not feasible and the test case ends giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs
    • • IF the PHD under test supports the Passkey Entry Association Model (PIXIT I_AG_BDG_007 = 2) and DisplayOnly capabilities (PIXIT I_AG_BDG_005 = 0) THEN the test tool simulated PHG is configured with KeyboardOnly capabilities and with MITM support
    • • IF the PHD under test supports the Passkey Entry Association Model (PIXIT I_AG_BDG_007 = 2) and DisplayYesNo capabilities (PIXIT I_AG_BDG_005 = 1) THEN the test tool simulated PHG is configured with KeyboardOnly capabilities and with MITM support
    • • IF the PHD under test supports the Passkey Entry Association Model (PIXIT I_AG_BDG_007 = 2) and KeyboardOnly capabilities (PIXIT I_AG_BDG_005 = 2) THEN the test tool simulated PHG is configured with DisplayOnly capabilities and with MITM support
    • • IF the PHD under test supports the Numeric Comparison or Passkey Entry Association Model (PIXIT I_AG_BDG_007 = 1 or 2) and NoInputNoOutput capabilities (PIXIT I_AG_BDG_005 = 3) THEN the combination of IO capabilities, Association Model and MITM support declared by the PHD under test in PIXITs is not feasible and the test case ends giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs

    3. Turn on the PHD under test and configure it as a discoverable Bluetooth device, as stated in the product documentation.

    4. The test tool simulated PHG initiates a discovery process, it discovers the PHD under test and starts a pairing process with PHD under test.

    | +| Pass/Fail criteria |

    In step 1, the PHD under test supports secure simple pairing (PIXIT I_AG_BDG_004 = TRUE).

    In step 2, the PHD under test SSP features declared in PIXIT are consistent.

    In step 4, the PHD under test completes the pairing process successfully.

    | +| Notes | | + +### A.5 Subgroup 1.1.4 – Pulse oximeter device specialization design guidelines (PODG) + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--------------------| +| TP Id | TP/PLT/PHD/CLASS/PODG/BV-000 | | | | +| TP label | Pulse Oximeter: PM-Store attributes | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | PODG PM_Store 4; M | PODG PM_Store 5; M | PODG PM_Store 6; M | +| | | PODG General 2; C | | | +| Test purpose |

    Check that:

    PM-Store object contains the specified attributes PM-Store Capab and PM-Store Label for Extended Configuration.

    | | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_041 AND C_AG_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure |
    1. 1. The simulated PHG issues a "Remote Operation Invoke Get" command with the handle set to the PM-Store and the attribute-id-list set to 0 to indicate all attributes.
    2. 2. The PHD response must contain:
      1. a. Mandatory attribute PM-Store-Capab
        • attribute-id = MDC_ATTR_PM_STORE_CAPAB
        • attribute-type = PmStoreCapab
        • attribute-value.lenght=BITS-16
        • attribute-value=
          • ▪ Bit 8 (pm-sc-clear-seg-by-time-sup (8)) has to be clear.(This bit indicates that clearing by time range is supported).
          • ▪ Bit 10 (pm-sc-clear-segm-all-sup (10)) has to be set. (This bit indicates that clearing all segments is supported).
      2. b. Optional attribute PM-Store-Label
        • attribute-id = MDC_ATTR_PM_STORE_LABEL_STRING
        • attribute-type = OCTET STRING
        • attribute-value.length <= 255 octets
        • attribute-value = <Not relevant for this Test>
    | | | | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | | | | +| Notes | | | | | + +| | | | | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--| +| TP Id | TP/PLT/PHD/CLASS/PODG/BV-001 | | | | +| TP label | Pulse Oximeter: PM-Store, PM-Segment attributes | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | PODG PM_Store 7; C | PODG PM_Store 8; C | | +| | | | | | +| Test purpose |

    Check that:

    Continua PAN/ Sensor-LAN Pulse Oximeter service components shall implement the Sample-Period attribute of a PM-Store object, if the stored measurements are periodic and the Sample-Period attribute is not implemented in each of the PM-Segment objects created within that PM-Store object.

    [AND]

    If the Sample-Period is defined in both the PM-Store and in the PM-Segment(s), the PM-Segment attribute value shall take precedence

    | | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_041 AND C_AG_OXP_000 | | | | +| Other PICS | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | +| Test procedure |
    1. 1. The simulated PHG issues a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.
    2. 2. The PHD issues a GET response with the PM-Store attributes it supports:
      1. a. Conditional attribute Sample-Period
        1. attribute-id = MDC_ATTR_TIME_PD_SAMP
        2. attribute-type = RelativeTime
        3. attribute-value.length= 4 bytes
        4. attribute-value= <Not relevant for this Test>
    3. 3. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments
      1. a. Conditional attribute Sample-Period
        1. attribute-id = MDC_ATTR_TIME_PD_SAMP
        2. attribute-type = RelativeTime
        3. attribute-value.length= 4 bytes
        4. attribute-value= <Not relevant for this test>
    | +| Pass/Fail criteria | The Attribute Sample-Period shall be implemented in PM-Store if it is not implemented in every PM-Segment. | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------| +| TP Id | TP/PLT/PHD/CLASS/PODG/BV-002 | | | +| TP label | Pulse Oximeter: PM-Segment attributes | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | PODG PM_Store 1; R | PODG PM_Store 2; M | +| | | | PODG General 2; C | +| Test purpose | Check that:
    PM-Segment contain the specified attributes for Extended Configuration. | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_041 AND C_AG_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHG shall send a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.
    2. 2. The PHD issues a GET response with the PM-Store attributes.
    3. 3. The simulated PHG shall send a Get-Segment-Info object action for the PM-Segment object with SegmSelection = all-segments to indicate the PM-Segments attributes of all available PM-Segments.
    4. 4. The PHD issues a response with the PM-Segment attributes it supports, the attributes of interest are:
      1. a. Attribute Segment-Start-Abs-Time is mandatory:
        1. attribute-id = MDC_ATTR_TIME_START_SEG
        2. attribute-type = AbsoluteTime
        3. attribute-value.length = 8 bytes
        4. attribute-value =
          1. ▪ century =
          2. ▪ year ≤ 99
    | | | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ month ≤ 12
    • ▪ day ≤ 31
    • ▪ hour ≤ 24
    • ▪ minute ≤ 60
    • ▪ second ≤ 60
    • ▪ sec-fractions ≤ 100

    b. Attribute Segment-End-Abs-Time is mandatory

    • attribute-id = MDC_ATTR_TIME_END_SEG
    • attribute-type = AbsoluteTime
    • attribute-value.length = 8 bytes
    • attribute-value =
      • ▪ century =
      • ▪ year ≤ 99
      • ▪ month ≤ 12
      • ▪ day ≤ 31
      • ▪ hour ≤ 24
      • ▪ minute ≤ 60
      • ▪ second ≤ 60
      • ▪ sec-fractions ≤ 100

    c. Mandatory attribute PM-Segment-Entry-Map.

    • attribute-id = MDC_ATTR_PM_SEG_MAP
    • attribute-type = PmSegmentEntryMap
    • attribute-value = Recommended values
      • ▪ SegmEntryElemList.count = 2
        • i. SegmEntryElem #1: SpO2
          • - obj-class = MDC_MOC_VMO_METRIC_NU
          • - metric-type = MDC_PART_SCADA
            MDC_PULS_OXIM_SAT_O2
          • - HANDLE (shall be set to appropriate handle-id for SpO2)
        • ii. SegmEntryElem #2: Pulse rate
          • - obj-class = MDC_MOC_VMO_METRIC_NU
          • - metric-type = MDC_PART_SCADA
            MDC_PULS_OXIM_PULS_RATE
          • - HANDLE (shall be set to appropriate handle-id for Pulse rate)
      • ▪ OR SegmEntryElemList.count = 1
        • i. SegmEntryElem #1: SpO2 or Pulse rate
          • - obj-class = MDC_MOC_VMO_METRIC_NU
          • - metric-type = MDC_PART_SCADA
            MDC_PULS_OXIM_SAT_O2 or
            MDC_PULS_OXIM_PULS_RATE
          • - HANDLE (shall be set to appropriate handle-id for SpO2 or Pulse Rate)
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |

    All attribute values are as specified in the test procedure.

    In the case that the PM-Segment-Entry-Map contains only one element (SpO2 or Pulse Rate object), there should be another segment with a PM-Segment-Entry-Map that contains (Pulse Rate if the first segment contains SpO2 measurement or SpO2 if the first segment contains Pulse Rate measurement).

    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/PODG/BV-003 | | | +| TP label | Pulse Oximeter: Overlapped PM-Segments | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | PODG PM_Store 3; M | | +| Test purpose |

    Check that:

    Continua PAN/Sensor-LAN Pulse Oximeter service components shall create PM-segments within the same PM-store, if the PM-segment are overlapping in time

    | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_041 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_009 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |

    For each PM-Store object:

    1. 1. The simulated PHG shall send a Get-Segment-Info object action for the PM-Segment object with SegmSelection = all-segments to indicate the PM-Segments attributes of all available PM-Segments.
    2. 2. The PHD issues a response with the PM-Segment attributes it supports, the attributes of interest are:
      • • Conditional attribute Segment-Start-Abs-Time
        • attribute-id = MDC_ATTR_TIME_START_SEG
        • attribute-type = AbsoluteTime
        • attribute-value = <Record value for future comparison>
      • • Conditional attribute Segment-End-Abs-Time
        • attribute-id = MDC_ATTR_TIME_END_SEG
        • attribute-type = AbsoluteTime
        • attribute-value = <Record value for future comparison>
    3. 3. Check all PM-Segments time intervals (Segment-Start-Abs-Time and Segment-End-Abs-Time).
    | | | +| Pass/Fail criteria |
    • • In Step 3, overlapped PM-Segments must be included in the same PM-Store object.
    | | | +| Notes | | | | + +### A.6 Subgroup 1.1.5 – Cardiovascular design guidelines (CVDG) + +| | | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------|--|--| +| TP Id | TP/PLT/PHD/CLASS/CVDG/BV-000 | | | | | +| TP label | Cardiovascular: Step Counter sub-specialization (profile) | | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | | +| | Testable items | Cardio_DG 3; M | Cardio_DG 5; O | | | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | | | +| | Testable items | ConfEventRep 35; M | | | | +| Test purpose |

    Check that:

    Continua PAN/Sensor-LAN step counter service components shall support the Session and Distance object in units of steps.

    [AND]

    Continua PAN/Sensor-LAN step counter service components may support the Subsession, Cadence, Speed, Distance (in meters and/or feet), Stride Length, or Energy Expended objects as defined in [ISO/IEEE 11073-10441].

    [AND]

    Objects that are mandatory or conditional in the specialization remain mandatory or conditional in a profile

    Objects that are optional in the specialization may either remain optional or become mandatory within a profile

    | | | | | +| Applicability | C_AG_OXP_172 AND C_AG_CV_001 AND C_AG_OXP_000 | | | | | +| Other PICS | | | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. A Session object and a Distance object shall be present.
    5. 5. A Distance object shall be present, with the Unit-Code attribute:
      1. a. Mandatory attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type (INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = MDC_DIM_X_STEP
    6. 6. Subsession, Cadence, Speed, Stride Length and Energy Expended and additional Distance object may be present.
    | | | | | +| Pass/Fail criteria | In steps 4, 5 and 6 checked values are as specified. | | | | | +| Notes | | | | | | + +### A.7 Subgroup 1.1.6 – Activity hub design guidelines (HUBDG) + +| | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------|--|--| +| TP Id | TP/PLT/PHD/CLASS/HUBDG/BV-000 | | | | | +| TP label | Activity Hub sub-specializations (profiles) | | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | | +| | Testable items | Hub_DG 1; M | Hub_DG 3; M | | | +| | | Hub_DG 7; M | Hub_DG 9; M | | | +| | | Hub_DG 13; M | Hub_DG 15; M | | | +| | | Hub_DG 19; M | Hub_DG 21; M | | | +| | | Hub_DG 25; M | Hub_DG 27; M | | | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | | | +| | Testable items | ConfEventRep 35; M | | | | +| Test purpose |

    Check that:

    An independent living activity hub that follows a profile supports the appropriate object.

    [AND]

    Objects that are mandatory or conditional in the specialization remain mandatory or conditional in a profile

    Objects that are optional in the specialization may either remain optional or become mandatory within a profile

    | | | | | +| Applicability | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000 AND (C_AG_HUB_001 OR C_AG_HUB_002 OR C_AG_HUB_003 OR C_AG_HUB_004 OR C_AG_HUB_005 OR C_AG_HUB_006 OR C_AG_HUB_007 OR C_AG_HUB_008 OR C_AG_HUB_009 OR C_AG_HUB_010 OR C_AG_HUB_011 OR C_AG_HUB_012 OR C_AG_HUB_013 OR C_AG_HUB_014) | | | | | +| Other PICS | | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG. Check the ConfigObjectList:
      1. a. obj-class ( ConfigReport then ConfigObjectList (ConfigObject))
        • • field- type = OID-Type
        • • field-length = 2 bytes
        • • field- value= MDC_MOC_VMO_METRIC_ENUM
      2. b. obj-handle ( ConfigReport then ConfigObjectList (ConfigObject))
        • • field- type = HANDLE
        • • field-length = 2 bytes
        • • field- value= 0x00
      3. c. attribute-id ( ConfigReport then ConfigObjectList (ConfigObject)then AttributeList then attribute-id
        • • field- type = OID-Type
        • • field-length = 2 bytes
        • • field- value= MDC_ATTR_ID_TYPE (0x09 0x2F) then This attribute let us know the type of measurement
      4. d. attribute-value(ConfigReport then ConfigObjectList (ConfigObject) then Attribute
    | | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    List), this value depends on the attribute type. The values we have to check are:

    • IF the PHD supports Fall Sensor Specialization THEN the Fall Sensor object shall be present.
    • IF the PHD supports Motion Sensor Specialization THEN the Motion Sensor object shall be present.
    • IF the PHD supports Enuresis Sensor Specialization THEN the Enuresis Sensor object shall be present.
    • IF the PHD supports Contact Closure Sensor Specialization THEN the Contact Closure Sensor object shall be present.
    • IF the PHD supports Switch Sensor Specialization THEN the Switch Sensor object shall be present.
    • IF the PHD supports Dosage Sensor Specialization THEN the Dosage Sensor object shall be present.
    • IF the PHD supports Water Sensor Specialization THEN the Water Sensor object shall be present.
    • IF the PHD supports Smoke Specialization THEN the Smoke object shall be present.
    • IF the PHD supports Property Exit Sensor Specialization THEN the Property Exit Sensor object shall be present.
    • IF the PHD supports Ambient Temperature Sensor Specialization THEN the Temperature Sensor object shall be present.
    • IF the PHD supports Usage Sensor Specialization THEN the Usage Sensor object shall be present.
    • IF the PHD supports PERS Sensor Specialization THEN the PERS Sensor object shall be present.
    • IF the PHD supports CO Sensor Specialization THEN the CO Sensor object shall be present.
    • IF the PHD supports Gas Sensor Specialization THEN the Gas Sensor object shall be present.
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +### A.8 Subgroup 1.1.7 – ZigBee design guidelines (ZDG) + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-000 | | | +| TP label | ZigBee QoS best.medium | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | ZQoS 1; M | | +| Test purpose |

    Check that:

    Continua Sensor-LAN service components that implement the Continua best.medium QoS bin shall utilize ZigBee APS acknowledgements

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. The simulated PHG sends a GET request for an MDS object.
    2. Check that the PHD utilizes APS-ack when it receives the GET message from the simulated PHG.
    | | | +| Pass/Fail criteria | The service shall use APS-ack when it receives the GET message. | | | +| Notes | | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-001 | | | +| TP label | ZigBee One-to-Many. Endpoints and Associations | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | ZB Multiple Connections 1; M | Dominant Assoc 1; M | +| Test purpose |

    Check that:

    PHD that establish multiple Sensor-LAN interface connections (ZigBee One-to-Many) shall use a separate ZigBee endpoint for each

    [AND]

    Any PHD that establishes more than one, simultaneous connection to one or more PHGs at the same point in time shall create a ISO/IEEE 11073- 20601 Association to a PHG per connection

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 | | | +| Other PICS | | | | +| Initial condition | Simulated PHG #1 (Coordinator), simulated PHG #2 and the PHD under test are disconnected. | | | +| Test procedure |
    1. Start simulated PHG #1 as ZigBee coordinator.
    2. Start simulated PHG #2 and join it to the simulated PHG #1 network.
    3. Start the PHD under test and join it to the simulated PHG #1 network.
    4. Simulated PHG #1 performs a Discovery in ZigBee network. It gets all endpoints available in this network.
    5. Simulated PHG #1 selects one Continua End Point available in the PHD under test and creates a 11073 Protocol Tunnel with the PHD under test.
    6. Force the PHD under test to associate with simulated PHG #1 and complete the association procedure until both reach the Operating state.
    7. Simulated PHG #2 performs a Discovery in the ZigBee network. It gets all endpoints available in this network.
    8. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | is a different End Point than that still used by Simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test.
    9. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state.
    10. Check the Continua End Points used by the PHD in both associations. | +| Pass/Fail criteria | In Step 4, simulated PHG #1 discovers at least two End Points with Continua device specializations (Continua End Points) in the PHD under test.
    In Step 6, in the association with simulated manager #1 the PHD under test reaches the Operating state.
    In Step 9, in the association with simulated manager #2 the PHD under test reaches the Operating state.
    In Step 10, the PHD under test uses two different Continua End Points to associate with the simulated PHGPHGs #1 and #2. | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-002 | | | +| TP label | ZigBee One-to-Many. New Association 1 | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Dominant Assoc 3; M | | +| Test purpose | Check that:
    PHDs that establish more than one, simultaneous connection to one PHG at the same point in time shall create a new association to that PHG if and only if all other connections are in the Unassociated or Operating state | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 | | | +| Other PICS | | | | +| Initial condition | Simulated PHG #1 (Coordinator), simulated PHG #2 and the PHD under test are disconnected. | | | +| Test procedure |
    1. 1. Start simulated PHG #1 as ZigBee coordinator.
    2. 2. Start simulated PHG #2 and join it to the simulated PHG #1 network.
    3. 3. Start the PHD under test and join it to the simulated PHG #1 network.
    4. 4. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
    5. 5. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
    6. 6. Simulated PHG #1 selects one Continua End Point available in the PHD under test and creates a 11073 Protocol Tunnel with the PHD under test.
    7. 7. Force the PHD under test to associate with simulated PHG #1, but when the PHD under test sends the AARQ then simulated manager #1 does not respond (the PHD under test will try to associate with simulated PHG #1 during 3*TOassoc = 30 seconds).
    8. 8. In parallel with step 7, during the 3*TOassoc period:
      1. a. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than that still being used by simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test
      2. b. Force the PHD under test to associate with simulated PHG #2.
    | | | +| Pass/Fail criteria | In Step 4, simulated PHG #1 discovers at least two End Points with Continua device specializations (Continua End Points) in the PHD under test.
    In Step 7, simulated PHG #1 receives an AARQ message 4 times (RCassoc + 1 = 4).
    In parallel, in Step 8b, simulated PHG #2 does not receive the AARQ message within the 3*TOassoc period. | | | +| Notes | | | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-003 | | | +| TP label | ZigBee One-to-Many. New Association 2 | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Dominant Assoc 3; M | | +| Test purpose |

    Check that:

    PHDs that establish more than one, simultaneous connection to one PHG at the same point in time shall create a new association to that PHG if and only if all other connections are in the Unassociated or Operating state

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 | | | +| Other PICS | | | | +| Initial condition | Simulated PHG #1 (Coordinator), Simulated PHG #2 and the PHD under test are disconnected. | | | +| Test procedure |
    1. 1. Start simulated PHG #1 as a ZigBee coordinator.
    2. 2. Start simulated PHG #2 and join it to simulated PHG #1 network.
    3. 3. Start the PHD under test and join it to simulated PHG #1 network.
    4. 4. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
    5. 5. Simulated PHG #1 selects one Continua End Point available in the PHD under test and it creates a 11073 Protocol Tunnel with the PHD under test.
    6. 6. Force the PHD under test to associate with simulated PHG #1 and complete the association procedure until both reach the Operating state.
    7. 7. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
    8. 8. Once the PHD under test and simulated PHG #1 are in the Operating state:
      1. a. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
      2. b. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than the End Point that simulated PHG #1 is still using) and it creates a 11073 Protocol Tunnel with the PHD under test.
      3. c. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state.
    | | | +| Pass/Fail criteria |

    In Step 4, simulated PHG #1 discovers at least two End Points with Continua device specializations (Continua End Points) in the PHD under test.

    In Step 7, in the association with simulated PHG #1 the PHD under test reaches the Operating state.

    In Step 8b, in the association with simulated PHG #2 the PHD under test reaches the Operating state.

    | | | +| Notes | | | | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-004 | | | +| TP label | ZigBee One-to-Many. Dominant Association 1 (Set Time) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Dominant Assoc 4; M | Dominant Assoc 5; M | +| Test purpose |

    Check that:

    PHDs shall have at most a single dominant ISO/IEEE Association at a single point in time

    AND

    PHDs shall not set any of following MDS-Time-Info attribute bits or PM-Store-Capab attribute

    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | bits for other than its dominant association: mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove, pmsc-clear-segm-all-sup | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 AND C_AG_OXP_008 | +| Other PICS | | +| Initial condition | Simulated PHG #1 (Coordinator), Simulated PHG #2 and the PHD under test are connected to the same ZigBee network. | +| Test procedure |
    1. 1. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. Simulated PHG #1 selects one Continua End Point available in the PHD under test and creates a 11073 Protocol Tunnel with the PHD under test.
    2. 2. Force the PHD under test to associate with simulated PHG #1 and complete the association procedure until both reach the Operating state (Association #1).
    3. 3. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
    4. 4. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than that being used by Simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test.
    5. 5. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state (Association #2).
    6. 6. Through Association #1:
      1. a. Simulated PHG #1 sends a "Remote Operation Invoke Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object. The attribute of interest of this test is MDSTimeInfo:
        • attribute-id = MDC_ATTR_MDS_TIME_INFO (0x0A 0x45)
        • attribute-type = MdsTimeInfo
        • attribute-value = Record bits mds-time-mgr-set-time and mds-time-capab-set-clock values
    7. 7. Through Association #2:
      1. a. Simulated PHG #2 sends a "Remote Operation Invoke Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object. The attribute of interest of this test is MDSTimeInfo:
        • attribute-id = MDC_ATTR_MDS_TIME_INFO (0x0A 0x45)
        • attribute-type = MdsTimeInfo
        • attribute-value = Record bits mds-time-mgr-set-time and mds-time-capab-set-clock values
    8. 8. Compare the bits mds-time-mgr-set-time and mds-time-capab-set-clock values between Association #1 and Association #2:
      1. a. IF bits mds-time-mgr-set-time and/or mds-time-capab-set-clock are set to 1 in Association #1 THEN bits mds-time-mgr-set-time and mds-time-capab-set-clock both are set to 0 in Association #2
      2. b. IF bits mds-time-mgr-set-time and/or mds-time-capab-set-clock are set to 1 in Association #2 THEN bits mds-time-mgr-set-time and mds-time-capab-set-clock both are set to 0 in Association #1
    | +| Pass/Fail criteria | In Step 8, mds-time-mgr-set-time and mds-time-capab-set-clock bits values in both Associations are as specified in test procedure. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-005 | | | +| TP label | ZigBee One-to-Many. Dominant Association 2 (PM-Store Clear Segment) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Dominant Assoc 4; M | Dominant Assoc 5; M | +| Test purpose |

    Check that:

    PHDs shall have at most a single dominant ISO/IEEE 11073 Association at a single point in time

    AND

    PHDs shall not set any of following MDS-Time-Info attribute bits or PM-Store-Capab attribute bits for other than its dominant association: mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove, pmsc-clear-segm-all-sup

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 AND C_AG_OXP_041 AND C_AG_OXP_071 | | | +| Other PICS | | | | +| Initial condition | Simulated PHG #1 (Coordinator), Simulated PHG #2 and the PHD under test are connected to the same ZigBee network. | | | +| Test procedure |
    1. 1. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. Simulated PHG #1 selects one Continua End Point available in the PHD under test and creates a 11073 Protocol Tunnel with the PHD under test.
    2. 2. Force the PHD under test to associate with simulated PHG #1 and complete the association procedure until both reach the Operating state (Association #1).
    3. 3. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
    4. 4. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than that being used by Simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test.
    5. 5. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state (Association #2).
    6. 6. Through Association #1:
      1. a. Simulated PHG #1 sends a "Remote Operation Invoke Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object. The attribute of interest of this test is MDSTimeInfo:
        • attribute-id = MDC_ATTR_MDS_TIME_INFO (0x0A 0x45)
        • attribute-type = MdsTimeInfo
        • attribute-value = Record bits mds-time-mgr-set-time and mds-time-capab-set-clock values
      3. c. Simulated PHG #1 sends a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.
      4. d. The PHD under test responds with the PM-Store attribute list. The attribute of interest of this test is PMStoreCapab:
        • attribute-id = MDC_ATTR_PM_STORE_CAPAB (0x0A 0x4D)
        • attribute-type = PmStoreCapab
        • attribute-value = Record bits pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup values
    7. 7. Through Association #2:
      1. a. Simulated PHG #2 sends a "Remote Operation Invoke Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    all attributes.

    b. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object. The attribute of interest of this test is MDSTimeInfo:

    • attribute-id = MDC_ATTR_MDS_TIME_INFO (0x0A 0x45)
    • attribute-type = MdsTimeInfo
    • attribute-value = Record bits mds-time-mgr-set-time and mds-time-capab-set-clock values

    c. Simulated PHG #2 sends a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.

    d. The PHD under test responds with the PM-Store attribute list. The attribute of interest of this test is PMStoreCapab:

    • attribute-id = MDC_ATTR_PM_STORE_CAPAB (0x0A 0x4D)
    • attribute-type = PmStoreCapab
    • attribute-value = Record bits pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup values

    8. Compare bits mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup values between Association #1 and Association #2

    a. IF any of bits mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove or pmsc-clear-segm-all-sup is set to 1 in Association #1 THEN all bits mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup are set to 0 in Association #2

    b. IF any of bits mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove or pmsc-clear-segm-all-sup is set to 1 in Association #2 THEN all bits mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup are set to 0 in Association #1

    | +| Pass/Fail criteria | In step 8, mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup bits values in both associations are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-006 | | | +| TP label | ZigBee One-to-Many. Set Time and Date-and-Time update | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Dominant Assoc 6; M | | +| Test purpose |

    Check that:

    PHDs that modified their clock based on the reception of a Set-Time action via its dominant association shall send an event report that contains the new Date-and-Time attribute value for all their non-dominant associations prior to sending any temporarily stored measurements and prior to starting a new transfer of a PM-Segment

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 AND C_AG_OXP_008 | | | +| Other PICS | | | | +| Initial condition | Simulated PHG #1 (Coordinator), Simulated PHG #2 and the PHD under test are connected to the same ZigBee network. | | | +| Test procedure |
    1. 1. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. Simulated PHG #1 selects one Continua End Point available in the PHD under test and it creates a 11073 Protocol Tunnel with the PHD under test.
    2. 2. Force the PHD under test to associate with simulated PHG #1 and complete the
    | | | + +association procedure until both reach the Operating state (Association #1). + +3. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. +4. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than that being used by Simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test. +5. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state (Association #2). +6. Through Association #1: + - a. Simulated PHG #1 sends a "Remote Operation Invoke | Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes. + - b. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object. The attribute of interest of this test is MDSTimeInfo: + - attribute-id = MDC\_ATTR\_MDS\_TIME\_INFO (0x0A 0x45) + - attribute-type = MdsTimeInfo + - attribute-value = Record bit mds-time-capab-set-clock value +7. Through Association #2: + - a. Simulated PHG #2 sends a "Remote Operation Invoke | Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes. + - b. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object. The attribute of interest of this test is MDSTimeInfo: + - attribute-id = MDC\_ATTR\_MDS\_TIME\_INFO (0x0A 0x45) + - attribute-type = MdsTimeInfo + - attribute-value = Record bit mds-time-capab-set-clock value +8. Check bit mds-time-capab-set-clock value in Association #1 and Association #2. It must be set to 1 in one, and only one, Association +9. IF bit mds-time-capab-set-clock is set to 1 in Association #1 (dominant association) THEN + - a. Simulated PHG #1 sends a SET action through Association #1: + - CHOICE = SetTimeInvoke + - action-type = MDC\_ACT\_SET\_TIME + - the action-info-args are SetTimeInvoke + - date-time = century $\leq$ 99, year $\leq$ 99, month $\leq$ 12, day $\leq$ 31, hour $\leq$ 24, minute $\leq$ 60, second $\leq$ 60, sec-fractions $\leq$ 100 + - accuracy = 0 + - b. The PHD under test responds through Association #1 with rors-cmip-confirmed-action with action-info-args empty. + - c. Force the PHD under test to acquire a new measurement and report it through Association #2. + - d. The PHD under test sends through Association #2 (non-dominant association) an event report (fixed or variable format) containing the new Date-and-Time attribute value of the MDS object. +10. IF bit mds-time-capab-set-clock is set to 1 in Association #2 (Dominant Association) THEN + - a. Simulated PHG #2 sends a SET action through Association #2: + - CHOICE = SetTimeInvoke + - action-type = MDC\_ACT\_SET\_TIME + - the action-info-args are SetTimeInvoke + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • date-time = century ≤ 99, year ≤ 99, month ≤ 12, day ≤ 31, hour ≤ 24, minute ≤ 60, second ≤ 60, sec-fractions ≤ 100
    • accuracy = 0

    b. The PHD under test responds through Association #2 with rors-cmip-confirmed-action with action-info-args empty.

    c. Force the PHD under test to acquire a new measurement and report it through Association #1.

    d. The PHD under test sends through Association #1 (non-dominant association) an event report (fixed or variable format) containing the new Date-and-Time attribute value of the MDS object.

    | +| Pass/Fail criteria | In step 9.d or 10.d, the PHD sends through a Non-Dominant Association an event report (fixed or variable format) containing the new Date-and-Time attribute value of the MDS object. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-008 | | | +| TP label | ZigBee One-to-Many. Close Dominant Association | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Dominant Assoc 9; O | | +| Test purpose | Check that:
    PHDs may close their dominant association | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 AND C_AG_ZDG_003 | | | +| Other PICS | C_AG_OXP_008, C_AG_OXP_071 | | | +| Initial condition | Simulated PHG #1 (Coordinator), simulated PHG #2 and the PHD under test are connected to the same ZigBee network. | | | +| Test procedure |
    1. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. Simulated PHG #1 selects one Continua End Point available in the PHD under test and creates a 11073 Protocol Tunnel with the PHD under test.
    2. Force the PHD under test to associate with simulated PHG #1 and complete the association procedure until both reach the Operating state (Association #1).
    3. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than that being used by Simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test.
    4. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state (Association #2).
    5. Through Association #1:
      1. IF C_AG_OXP_008 THEN
        • Simulated PHG #1 sends a "Remote Operation Invoke Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
        • The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
        • Record bits mds-time-mgr-set-time and mds-time-capab-set-clock values from MdsTimeInfo attribute.
      2. IF (C_AG_OXP_041 AND C_AG_OXP_071) THEN
        • Simulated PHG #1 sends a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.
        • The PHD under test responds with the PM-Store attribute list.
        • Record bits pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup values from PmStoreCapab
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    attribute.

    6. Through Association #2:

    a. IF C_AG_OXP_008 THEN

    • Simulated PHG #2 sends a "Remote Operation Invoke Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
    • The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    • Record bits mds-time-mgr-set-time and mds-time-capab-set-clock values from MdsTimeInfo attribute.

    b. IF (C_AG_OXP_041 AND C_AG_OXP_071) THEN

    • Simulated PHG #2 sends a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attribute.
    • The PHD under test responds with the PM-Store attribute list.
    • Record bits pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup values from PmStoreCapab attribute.

    7. Compare bits mds-time-mgr-set-time, mds-time-capab-set-clock, pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup values between Association #1 and Association #2 and determine the dominant association (it is the association that has one of these bits set to 1).

    8. Force the PHD under test to release the dominant association.

    9. Check that the message sent by PHD under test sends through dominant association.

    | +| Pass/Fail criteria |

    In Step 9, the PHD under test sends one of the following messages:

    • Release Request with reason = normal (0)
    • Release Request with reason = configuration-change (2)
    • Abort with reason = undefined (0)
    | +| Notes | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|--| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-009 | | | | +| TP label | ZigBee One-to-Many. Downgrade/Upgrade Dominant Association 1 (Set Time) | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Dominant Assoc 10; O | Dominant Assoc 11; O | | +| Test purpose |

    Check that:

    PHDs may downgrade their dominant association to become a non-dominant association

    [AND]

    PHDs that do not have a dominant association may upgrade an existing non-dominant association to become the dominant association

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 AND C_AG_ZDG_004 AND C_AG_OXP_008 | | | | +| Other PICS | | | | | +| Initial condition | Simulated PHG #1 (Coordinator), simulated PHG #2 and the PHD under test are connected to the same ZigBee network. | | | | +| Test procedure |
    1. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. Simulated PHG #1 selects one Continua End Point available in the PHD under test and creates a 11073 Protocol Tunnel with the PHD under test.
    2. Force the PHD under test to associate with simulated PHG #1 and complete the association procedure until both reach the Operating state (Association #1).
    3. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    available in this network. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than that being used by simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test.

    1. 4. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state (Association #2).
    2. 5. Through Association #1:
      1. a. Simulated PHG #1 sends a "Remote Operation Invoke Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object. The attribute of interest of this test is MDSTimeInfo:
        • ❑ attribute-id = MDC_ATTR_MDS_TIME_INFO (0x0A 0x45)
        • ❑ attribute-type = MdsTimeInfo
        • ❑ attribute-value = Record bit mds-time-capab-set-clock value
    3. 6. Through Association #2:
      1. a. Simulated PHG #2 sends a "Remote Operation Invoke Get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object. The attribute of interest of this test is MDSTimeInfo:
        • ❑ attribute-id = MDC_ATTR_MDS_TIME_INFO (0x0A 0x45)
        • ❑ attribute-type = MdsTimeInfo
        • ❑ attribute-value = Record bit mds-time-capab-set-clock value
    4. 7. Check bit mds-time-capab-set-clock value in Association #1 and Association #2. It must be set to 1 in one, and only one, association. The association with bit mds-time-capab-set-clock set to 1 is the Dominant Association
    5. 8. Force the PHD under test to change the Dominant Association to the other association (i.e., if the Dominant Association is association #1, the PHD under test must downgrade association #1 and upgrade association #2 or if the Dominant Association is association #2, the PHD under test must downgrade association #2 and upgrade association #1).
    6. 9. IF bit mds-time-capab-set-clock is set to 1 in association #1 (Dominant Association) THEN
      1. a. The PHD under test sends through association #1 (Dominant Association) a variable format event report containing the new Mds-Time-Info attribute value of MDS Object. Bits mds-time-mgr-set-time and mds-time-capab-set-clock are both set to 0 and association #1 becomes a Non-Dominant Association
      2. b. The PHD under test sends through association #2 (Non-Dominant Association) a variable format event report containing the new Mds-Time-Info attribute value of the MDS object. At least bit mds-time-capab-set-clock is set to 1 and association #2 becomes a Dominant Association.
    7. 10. IF bit mds-time-capab-set-clock is set to 1 in association #2 (Dominant Association) THEN
      1. a. The PHD under test sends through association #2 (Dominant Association) a variable format event report containing the new Mds-Time-Info attribute value of the MDS object. Bits mds-time-mgr-set-time and mds-time-capab-set-clock are both set to 0 and association #2 becomes a Non-Dominant Association
      2. b. The PHD under test sends through association #1 (Non-Dominant Association) a variable format event report containing the new Mds-Time-Info attribute value of the MDS object. At least bit mds-time-capab-set-clock is set to 1 and association #1 becomes a Dominant Association.
    | +| Pass/Fail criteria | In step 9 or 10, the PHD under test sends through Dominant and Non-Dominant Associations the messages detailed in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|--| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-010 | | | | +| TP label | ZigBee One-to-Many. Downgrade/Upgrade Dominant Association 2 (PM-Store Clear Segment) | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Dominant Assoc 10; O | Dominant Assoc 11; O | | +| Test purpose |

    Check that:

    PHDs may downgrade their dominant association to become a non-dominant association

    [AND]

    PHDs that do not have a dominant association may upgrade an existing non-dominant association to become the dominant association

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 AND C_AG_ZDG_004 AND C_AG_OXP_041 AND C_AG_OXP_071 | | | | +| Other PICS | | | | | +| Initial condition | Simulated PHG #1 (Coordinator), simulated PHG #2 and the PHD under test are connected to the same ZigBee network. | | | | +| Test procedure |
    1. 1. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. Simulated PHG #1 selects one Continua End Point available in the PHD under test and creates a 11073 Protocol Tunnel with the PHD under test.
    2. 2. Force the PHD under test to associate with simulated PHG #1 and complete the association procedure until both reach the Operating state (association #1).
    3. 3. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
    4. 4. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than that being used by simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test.
    5. 5. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state (association #2).
    6. 6. Through Association #1:
      1. a. Simulated PHG #1 sends a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes
      2. b. The PHD under test responds with the PM-Store attribute list. The attribute of interest of this test is PMStoreCapab:
        • attribute-id = MDC_ATTR_PM_STORE_CAPAB (0x0A 0x4D)
        • attribute-type = PmStoreCapab
        • attribute-value = Record bits pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup values
    7. 7. Through Association #2:
      1. a. Simulated PHG #2 sends a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.
      2. b. The PHD under test responds with the PM-Store attribute list. The attribute of interest of this test is PMStoreCapab:
        • attribute-id = MDC_ATTR_PM_STORE_CAPAB (0x0A 0x4D)
        • attribute-type = PmStoreCapab
        • attribute-value = Record bits pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup values
    8. 8. Check bits pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup values in Association #1 and Association #2. One or more of these bits must be set to 1 in one, and only one association. The association with one or more of these bits set is the Dominant Association.
    9. 9. Force the PHD under test to change the Dominant Association to the other association (i.e., if the Dominant Association is association #1, the PHD under test must downgrade
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Association #1 and upgrade association #2 or if the Dominant Association is association #2, the PHD under test must downgrade association #2 and upgrade association #1).

    10. IF one or more bits pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup are set to 1 in Association #1 (Dominant Association) THEN

    a. The PHD under test sends through Association #1 (Dominant Association) one of the following messages:

    • • Release Request with reason = normal (0)
    • • Release Request with reason = configuration-change (2)
    • • Abort with reason = undefined (0)

    b. The PHD under test sends through Association #2 (Non-Dominant Association) one of the following messages:

    • • Release Request with reason = normal (0)
    • • Release Request with reason = configuration-change (2)
    • • Abort with reason = undefined (0)

    11. IF one or more bits pmsc-clear-segm-by-list-sup, pmsc-clear-segm-by-time-sup, pmsc-clear-segm-remove and pmsc-clear-segm-all-sup are set to 1 in association #2 (Dominant Association) THEN

    a. The PHD under test sends through association #1 (Dominant Association) one of the following messages:

    • • Release Request with reason = normal (0)
    • • Release Request with reason = configuration-change (2)
    • • Abort with reason = undefined (0)

    b. The PHD under test sends through Association #2 (Non-Dominant Association) one of the following messages:

    • • Release Request with reason = normal (0)
    • • Release Request with reason = configuration-change (2)
    • • Abort with reason = undefined (0)
    | +| Pass/Fail criteria | In step 10 or 11, the PHD under test sends through Dominant and Non-Dominant Associations the messages detailed in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-011 | | | +| TP label | ZigBee One-to-Many. Timestamps | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | TimeStamp 1; M | TimeStamp 2; M | +| Test purpose |

    Check that:

    PHDs shall do timestamping for data that is intended to be sent multiple times over different connections

    AND

    PHDs shall use the same timestamp for data that is transmitted multiple times

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189) | | | +| Other PICS | | | | +| Initial condition | Simulated PHG #1 (Coordinator), simulated PHG #2 and the PHD under test are connected to the same ZigBee network. | | | +| Test procedure |

    1. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. Simulated PHG #1 selects one Continua End Point available in

    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    the PHD under test and it creates a 11073 Protocol Tunnel with the PHD under test.

    1. 2. Force the PHD under test to associate with simulated PHG #1 and complete the association procedure until both reach the Operating state (association #1).
    2. 3. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
    3. 4. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than that being used by simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test.
    4. 5. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state (association #2).
    5. 6. Force the PHD under test to acquire a new measurement and report it through association #1 and association #2.
    6. 7. The PHD under test sends through association #1 an event report containing the measurement value and the timestamp.
    7. 8. The PHD under test sends through association #2 an event report containing the measurement value and the timestamp.
    | +| Pass/Fail criteria | In steps 7 and 8 the PHD under test reports the same measurement value and the same timestamp value. | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| TP Id | TP/LAN/PHD/TR/ZDG/BV-012 | | | +| TP label | ZigBee One-to-Many. Timeout | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | TimeoutManagement 1; M | TimeoutManagement 2; R | +| Test purpose |

    Check that:

    PHDs shall not cause a timeout on a particular connection, due to activity related to another existing connection

    AND

    PHDs that implement and use the PM-Store model should properly initialize the PM-Segment object Transfer-Timeout attribute to a value accounting for the maximum number of entries stored in the segment as well as the maximum number of supported ongoing segment transfers via other associations

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_ZDG_001 AND C_AG_ZDG_002 AND C_AG_OXP_041 | | | +| Other PICS | | | | +| Initial condition | Simulated PHG #1 (Coordinator), simulated PHG #2 and the PHD under test are connected to the same ZigBee network. | | | +| Test procedure |
    1. 1. Simulated PHG #1 performs a discovery in the ZigBee network. It gets all the endpoints available in this network. Simulated PHG #1 selects one Continua End Point available in the PHD under test and it creates a 11073 Protocol Tunnel with the PHD under test.
    2. 2. Force the PHD under test to associate with simulated PHG #1 and complete the association procedure until both reach the Operating state (association #1).
    3. 3. Simulated PHG #2 performs a discovery in the ZigBee network. It gets all the endpoints available in this network.
    4. 4. Simulated PHG #2 selects another Continua End Point available in the PHD under test (it is a different End Point than that being used by simulated PHG #1) and it creates a 11073 Protocol Tunnel with the PHD under test.
    5. 5. Force the PHD under test to associate with simulated PHG #2 and complete the association procedure until both reach the Operating state (Association #2).
    6. 6. Through association #1:
      1. a. Simulated PHG #1 sends through association #1 a "Get-Segment-Info".
      2. b. The PHD under test responds through association #1 with a rors-cmip-confirmed-
    | | | + +action with the PM-Segments attributes. The attribute of interest of this test is Transfer-Timeout: + +- attribute-id = MDC\_ATTR\_TRANSFER\_TIMEOUT (0x0A 0x64) +- attribute-type = RelativeTime +- attribute-value = Record attribute value + +#### 7. Through association #2: + +- a. Simulated PHG #2 sends through association #2 a "Get-Segment-Info" +- b. The PHD under test responds through association #2 with a rors-cmip-confirmed-action with the PM-Segments attributes. The attribute of interest of this test is Transfer-Timeout: + - attribute-id = MDC\_ATTR\_TRANSFER\_TIMEOUT (0x0A 0x64) + - attribute-type = RelativeTime + - attribute-value = Record attribute value + +#### 8. At the same point in time (i.e., concurrently): + +##### a. Through Association #1: + +1. Simulated PHG #1 sends through association #1 a request for the PM-Segment Data to one of the PM-Segments that contains data: + - Data APDU + - Type = Invoke | Confirmed Action + - Handle = obj-handle + - action-type = MDC\_ACT\_SEG\_TRIG\_XFER + - TrigSegmDataXferReq = +2. The PHD under test responds through association #1 with a rors-cmip-confirmed-action: + - Data APDU + - Type = Invoke | Confirmed Action + - Handle = obj-handle + - action-type = MDC\_ACT\_SEG\_TRIG\_XFER + - TrigSegmDataXferReq = | tsxr-successful (0x00 0x00) +3. The PHD under test starts the PM-Segment data transfer through association #1. +4. Simulated PHG #1 waits until PM-Segment Transfer-Timeout to receive the complete PM-Segment. + +##### b. Through association #2: + +1. Simulated PHG #2 sends through association #2 a request for the PM-Segment Data to one of the PM-Segments that contains data: + - Data APDU + - Type = Invoke | Confirmed Action + - Handle = obj-handle + - action-type = MDC\_ACT\_SEG\_TRIG\_XFER + - TrigSegmDataXferReq = +2. The PHD under test responds through association #2 with rors-cmip-confirmed-action: + - Data APDU + - Type = Invoke | Confirmed Action + - Handle = obj-handle + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • action-type = MDC_ACT_SEG_TRIG_XFER
      • ❑ TrigSegmDataXferReq = <Same Instance number> tsxr-successful (0x00 0x00)
    • 3. The PHD under test starts the PM-Segment data transfer through association #2.
    • 4. Simulated PHG #2 waits until PM-Segment Transfer-Timeout to receive the complete PM-Segment.
    | +| Pass/Fail criteria |

    In step 8.a the PM-Segment is transferred completely through association #1 and simulated PHG #1 timeout does not expire.

    In Step 8.b the PM-Segment is transferred completely through association #2 and simulated PHG #2 timeout does not expire.

    | +| Notes | | + +### A.9 Subgroup 1.1.10 – Basic electrocardiograph design guidelines (ECGDG) + +| | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHD/CLASS/ECGDG/BV-000 | | +| TP label | Basic ECG/Simple ECG: Recommended Layout for PM-Store | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | ECG_DG 3; C | +| Test purpose |

    Check that:

    Continua PAN Basic 1-3 Lead ECG service components should follow the storage layout as shown in Figure 7 of IEEE Std 11073-10406-2011

    | | +| Applicability | C_AG_OXP_165 AND C_AG_OXP_041 AND C_AG_OXP_000 | | +| Other PICS | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | +| Test procedure |
    1. 1. The simulated PHG shall send a Get-Segment-Info object action for the PM-Segment object with SegmSelection = all-segments to indicate the PM-Segments attributes of all available PM-Segments.
    2. 2. The PHD issues a response with the PM-Segment attributes it supports, the attributes of interest are:
      1. a. Mandatory attribute PM-Segment-Entry-Map.
        • ❑ attribute-id = MDC_ATTR_PM_SEG_MAP
        • ❑ attribute-type = PmSegmentEntryMap
        • ❑ attribute-value = Recommended values
          • ▪ SegmEntryElemList.count = 3
            1. i. SegmEntryElem #1: Lead I
              • - class-id = MDC_MOC_VMO_METRIC_SA_RT
              • - metric-type = {MDC_PART_SCADA (2), MDC_ECG_ELEC_POTL_I (257)}
              • - handle = Handle of Lead I object
              • - attr-val-map = MDC_MOC_VMO_METRIC_SA_RT
            2. ii. SegmEntryElem #2: Lead II
              • - class-id = MDC_MOC_VMO_METRIC_SA_RT
              • - metric-type = {MDC_PART_SCADA (2), MDC_ECG_ELEC_POTL_II (258)}
              • - handle = Handle of Lead II object
              • - attr-val-map = MDC_MOC_VMO_METRIC_SA_RT
    | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | iii. SegmEntryElem #3: Lead III
    • - class-id = MDC_MOC_VMO_METRIC_SA_RT
    • - metric-type = {MDC_PART_SCADA (2),
      MDC_ECG_ELEC_POTL_III (317)}
    • - handle = Handle of Lead III object
    • - attr-val-map = MDC_MOC_VMO_METRIC_SA_RT
    | +| Pass/Fail criteria | The PM-Segment-Entry-Map should be implemented as specified in the test procedure. If the PM-Segment-Entry-Map is not implemented as recommended, by IEEE specification, then the test tool issues a Warning message. | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/ECGDG/BV-001 | | | +| TP label | Basic ECG: PM-Store-Label attribute | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | ECG_DG 6; M | HeartRate_DG 6; M | +| Test purpose | Check that:

    PM-Store-Label attribute of the PM-Store object, shall not set a value of size larger than 255 octets | | | +| Applicability | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_041 AND C_AG_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. The simulated PHG issues a "Remote Operation Invoke Get" command with the handle set to the PM-Store and the attribute-id-list set to 0 to indicate all attributes.

    2. The PHD response must contain:
    a. Optional attribute PM-Store-Label
    attribute-id = MDC_ATTR_PM_STORE_LABEL_STRING
    attribute-type = OCTET STRING
    attribute-value.length <= 255 octets
    attribute-value = | | | +| Pass/Fail criteria | If the PHD implements the PM-Store-Label attribute then it shall not have a size larger than 255. | | | +| Notes | | | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/ECGDG/BV-002 | | | +| TP label | Basic ECG: Overlapped PM-Segments | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | ECG_DG 4; M | ECG_DG 5; M | +| | | HeartRate_DG 6; M | HeartRate_DG 5; M | +| Test purpose | Check that:

    For periodic measurements, Continua PAN Basic 1-3 Lead ECG and Heart Rate PHD shall create PM-segments within the same periodic PM-store, if the PM-segments are overlapping in time

    [AND]

    For aperiodic measurements, Continua PAN Basic 1-3 Lead ECG and Heart Rate PHD shall create PM-segments within the same aperiodic PM-store, if the PM-segments are overlapping in time | | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_041 AND C_AG_OXP_000 | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    5. 5. Record the handle for the PM-Store objects and check the PM-Store-Capab attribute of each PM-Store:
      1. a. Mandatory attribute PM-Store-Capab
        • attribute-id = MDC_ATTR_PM_STORE_CAPAB
        • attribute-type = PmStoreCapab
        • attribute-value.length = 2 bytes
        • attribute-value =
          • • For Periodic PM-Store objects = Bit 4 (pmsc-epi-seg-entries) is set to FALSE and Bit 5 (pmsc-peri-seg-entries) must be set to TRUE
          • • For Aperiodic PM-Store objects = Bit 4 (pmsc-epi-seg-entries) is set to TRUE and Bit 5 (pmsc-peri-seg-entries) must be set to FALSE
    6. 6. For each Periodic PM-Store object:
      1. a. The simulated PHG shall send a Get-Segment-Info object action for the PM-Segment object with SegmSelection = all-segments to indicate the PM-Segments attributes of all available PM-Segments.
      2. b. The PHD issues a response with the PM-Segment attributes it supports, the attributes of interest are:

        IF the PHD supports Absolute Time THEN

        • • Conditional attribute Segment-Start-Abs-Time
          • attribute-id = MDC_ATTR_TIME_START_SEG
          • attribute-type = AbsoluteTime
          • attribute-value = <Record value for future comparison>
        • • Conditional attribute Segment-End-Abs-Time
          • attribute-id = MDC_ATTR_TIME_END_SEG
          • attribute-type = AbsoluteTime
          • attribute-value = <Record value for future comparison>

        ELSE (the PHD supports Base Offset Time)

        • • Conditional attribute Segment-Start-BO-Time
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id = MDC_ATTR_TIME_START_SEG_BO
    • attribute-type = BaseOffsetTime
    • attribute-value = <Record value for future comparison>
    • • Conditional attribute Segment-End-BO-Time
      • attribute-id = MDC_ATTR_TIME_END_SEG_BO
      • attribute-type = BaseOffsetTime
      • attribute-value = <Record value for future comparison>

    c. Check all PM-Segments time intervals (Segment-Start-Abs-Time/Segment-Start-BO-Time and Segment-End-Abs-Time/Segment-End-BO-Time)

    7. For each Aperiodic PM-Store object

    • a. The simulated PHG shall send a Get-Segment-Info object action for the PM-Segment object with SegmSelection = all-segments to indicate the PM-Segments attributes of all available PM-Segments.
    • b. The PHD issues a response with the PM-Segment attributes it supports, the attributes of interest are:
      IF the PHD supports Absolute Time THEN
      • • Conditional attribute Segment-Start-Abs-Time
        • attribute-id = MDC_ATTR_TIME_START_SEG
        • attribute-type = AbsoluteTime
        • attribute-value = <Record value for future comparison>
      • • Conditional attribute Segment-End-Abs-Time
        • attribute-id = MDC_ATTR_TIME_END_SEG
        • attribute-type = AbsoluteTime
        • attribute-value = <Record value for future comparison>
      ELSE (the PHD supports Base Offset Time)
      • • Conditional attribute Segment-Start-BO-Time
        • attribute-id = MDC_ATTR_TIME_START_SEG_BO
        • attribute-type = BaseOffsetTime
        • attribute-value = <Record value for future comparison>
      • • Conditional attribute Segment-End-BO-Time
        • attribute-id = MDC_ATTR_TIME_END_SEG_BO
        • attribute-type = BaseOffsetTime
        • attribute-value = <Record value for future comparison>

    c. Check all PM-Segments time intervals (Segment-Start-Abs-Time/Segment-Start-BO-Time and Segment-End-Abs-Time/Segment-End-BO-Time)

    | +| Pass/Fail criteria |
    • • In step 6.c, overlapped PM-Segments must be included in the same Periodic PM-Store object.
    • • In step 7.c, overlapped PM-Segments must be included in the same Aperiodic PM-Store object.
    | +| Notes | | + +### A.10 Subgroup 1.1.11 – NFC design guidelines (NDG) + +| | | | | +|-----------------|-----------------------------------------------------------------|------------------------|--------------| +| TP Id | TP/TAN/PHD/TR/NDG/BV-000 | | | +| TP label | Completion of data exchange within an acceptable amount of time | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable | NFCUser 1; O | NFCUser 2; O | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--| +| | items | | | | +| Test purpose | Check that:
    A Continua TAN service component should complete data exchange within 3 seconds
    [AND]
    Continua TAN service component with appropriate UI capabilities should notify the user when data exchange is completed | | | | +| Applicability | C_AG_OXP_000 AND C_AG_NDG_001 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The simulated PHG responds with a rors-cmip-confirmed-event-report with result "accepted".
    5. 5. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          1. 1. IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          2. 2. IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    6. 6. Once in the Operating state, the simulated PHG issues roiv-cmip-get command with the handle set to 0 (to request an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
    7. 7. The PHD responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    8. 8. The PHD under test takes a measurement and sends it to the simulated PHG.
    9. 9. The simulated PHG sends a Release Request to the PHD under test with reason = normal(0).
    10. 10. The PHD under test responds with a Release Response.
    11. 11. The PHD under test notifies the user that the data Exchange is completed.
    | | | | +| Pass/Fail criteria |
    • • In step 10, the data exchange should be completed within 3 seconds.
    • • In step 11, the PHD under test should notify the user when the data exchange is completed.
    | | | | +| Notes | | | | | + +| | | | | | +|---------------------|--------------------------|------------------------|------------|--| +| TP Id | TP/TAN/PHD/TR/NDG/BV-001 | | | | +| TP label | NFC_QoS | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | NFCQoS 1;M | NFCQoS 2;M | | +| Test purpose | Check that: | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NFC PHDC transport does exchange all data on best.medium QoS bin | +| Applicability | C_AG_OXP_000 AND C_AG_NDG_001 | +| Other PICS | C_AG_OXP_008, C_AG_OXP_009, C_AG_OXP_014 | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | +| Test procedure |

    NOTE – This test case must be executed manually. NFC sniffer is needed to perform the verification required in this test case.

    1. 1. The simulated PHG receives an association request from the PHD under test on the best.medium QoS bin.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG on the best.medium QoS bin.
    4. 4. The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0 (to request an MDS object) and an empty attribute-id-list to indicate all attributes.
    5. 5. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object on the best.medium QoS bin.
    6. 6. If the PHD supports Set-Time, the simulated PHG sends a roiv-cmip-confirmed-action with action-type = MDC_ACT_SET_TIME (IF C_AG_OXP_009) or MDC_ACT_SET_BO_TIME (IF C_AG_OXP_014).
    7. 7. The PHD shall reply with rors-cmip-confirmed-action with action-type=MDC_ACT_SET_TIME (IF C_AG_OXP_009) or MDC_ACT_SET_BO_TIME (IF C_AG_OXP_014) on the best.medium QoS bin.
    8. 8. Make the PHD send at least one measurement on the best.medium QoS bin.
    9. 9. The simulated PHG sends an Association Release Request (Rlrq) message to the PHD under test, with reason =0 (normal).
    10. 10. The PHD under test shall respond with an Association Release Response (Rlre) message with reason =0 (normal) on the best.medium QoS bin.
    | +| Pass/Fail criteria | The PHD under test issues all responses on the best.medium QoS bin as defined by the steps above. | +| Notes | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*. +- [b-ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements*. +- [b-Bluetooth PHDT v1.5] Bluetooth SIG, *Personal Health Devices Transcoding White Paper*, v1.5. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=272346&\\_ga=1.171745760.1702697206.1475755459](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=272346&_ga=1.171745760.1702697206.1475755459) +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI 300 406] ETSI ETS 300 406, *Methods for Testing and Specifications (MTS); Protocol and profile conformance testing specifications; Standardization methodology*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v7.0.0.0 – Excel sheet v1.12. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v7.0.0.0 – Excel sheet v1.10. + +- [b-TI] Testable items. Test Tool v7.0.0.0 – Excel sheet v1.9. + + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.844-201911-I_PDF-E/raw.md b/marked/H/T-REC-H.844-201911-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f84148153846af258bc299e00b32a34888186574 --- /dev/null +++ b/marked/H/T-REC-H.844-201911-I_PDF-E/raw.md @@ -0,0 +1,1205 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.844** + +(11/2019) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 4: Continua Design Guidelines: Personal +Health Gateway** + +Recommendation ITU-T H.844 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.844 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 4: Continua Design Guidelines: Personal Health Gateway + +## Summary + +Recommendation ITU-T H.844 provides a test suite structure (TSS) and the test purposes (TP) for Personal Health Gateways (PHGs) in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2017) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.844 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 4: Continua Design Guidelines. Personal Health Gateway (Version 1.8, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.844 | 2015-01-13 | 16 | 11.1002/1000/12261 | +| 2.0 | ITU-T H.844 | 2016-07-14 | 16 | 11.1002/1000/12937 | +| 3.0 | ITU-T H.844 | 2017-04-13 | 16 | 11.1002/1000/13218 | +| 4.0 | ITU-T H.844 | 2018-08-29 | 16 | 11.1002/1000/13681 | +| 5.0 | ITU-T H.844 | 2019-11-29 | 16 | 11.1002/1000/14117 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, Personal Health Gateway, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|-----------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 4 | +| 3.1 | Terms defined elsewhere ..... | 4 | +| 3.2 | Terms defined in this Recommendation..... | 4 | +| 4 | Abbreviations and acronyms ..... | 4 | +| 5 | Conventions ..... | 5 | +| 6 | Test suite structure (TSS) ..... | 6 | +| 7 | Electronic attachment ..... | 9 | +| Annex A | Test purposes ..... | 10 | +| A.1 | TP definition conventions..... | 10 | +| A.2 | Subgroup 2.1.1 – Design guidelines: Common (DGC)..... | 12 | +| A.3 | Subgroup 2.1.2 – USB design guidelines (UDG)..... | 14 | +| A.4 | Subgroup 2.1.3 – Bluetooth design guidelines (BDG)..... | 17 | +| A.5 | Subgroup 2.1.4 – Cardiovascular device specialization design guidelines
    (CVDG) ..... | 24 | +| A.6 | Subgroup 2.1.5 – Activity hub device specialization design guidelines
    (HUBDG) ..... | 28 | +| A.7 | Subgroup 2.1.6 – ZigBee design guidelines (ZDG)..... | 43 | +| A.8 | Subgroup 2.1.8 – NFC design guidelines (NDG)..... | 43 | +| | Bibliography..... | 46 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 4: Continua Design Guidelines: Personal Health Gateway (Version 1.8, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.4 | 2012-10-05 | Initial release for Test Tool DG2011. This uses "TSS&TP_1.5_PAN-LAN_PART_4_v1.3.doc" as a baseline and adds new features included in [b-CDG 2011]:
    • • PM-Store and Errata
    | +| 1.5 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_1.5_PAN-LAN_PART_4_v1.4.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • • Updates test procedures to new requirements included in [b-CDG 2012] (e.g., SSP requirements)
    • • Adds body composition analyser device specialization
    • • Adds basic electrocardiograph device specialization
    | +| 1.6 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_4_v1.5.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.7 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_4_v1.6.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row has been added
    | +| 1.7 | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_4_v1.6.doc" because the new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015] do not affect the test procedures specified in this document. | +| 1.8 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_4_v1.7.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2016)]/[b-CDG 2016] | +| 1.9 | 2018-02-27 | Updates related to the inclusion of the power status monitor of Personal Health Devices device specialization [ISO/IEEE 11073-10427]
    Updates related to the inclusion of the updates included in the glucose meter device specialization [ISO/IEEE 11073-10427] | +| 1.10 | 2019-06-13 | Second maintenance release for Test Tool DG2017. It uses ITU-T H.844 (08/2018) as a baseline and adds some updates according to the 2018/2019 maintenance activity. | + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 4: Continua Design Guidelines: Personal Health Gateway + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2017)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 4. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- **Part 4: Continua design guidelines. Personal Health Gateway** +- Part 5: Device specializations. Personal Health Device. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) + - Part 5Q: Power status monitor (PSM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. Personal Health Device BLE +- Part 8: Continua Design Guidelines. Personal Health Gateway BLE +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Device + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2017)] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal health systems*. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd.1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization*. +NOTE – This is shorthand used to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. +- [ISO/IEEE 11073-10404] ISO/IEEE 11073-10404:2010, *Health informatics – Personal health device communication – Part 10404: Device specialization – Pulse oximeter*. + +- [ISO/IEEE 11073-10406] ISO/IEEE 11073-10406-2012, *Health informatics – Personal health device communication – Part 10406: Device specialization – Basic electrocardiograph (ECG) (1- to 3-lead ECG)*. + +- [ISO/IEEE 11073-10407] ISO/IEEE 11073-10407:2010, *Health informatics – Personal health device communication – Device specialization – Blood pressure monitor, version 1.0*. + +- [ISO/IEEE 11073-10408] ISO/IEEE 11073-10408:2010, *Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer*. + +- [ISO/IEEE 11073-10415] ISO/IEEE 11073-10415:2010, *Health informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale*. + + +| | | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [ISO/IEEE 11073-10417] | ISO/IEEE 11073-10417:2017, Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter.
    https://www.iso.org/standard/61896.html | +| [ISO/IEEE 11073-10418C] | ISO/IEEE 11073-10418-2014, Health informatics – Personal health device communication – Part 10418: Device specialization – International Normalized Ratio (INR) monitor, including ISO/IEEE 11073-10418:2014/Cor.1:2016.
    https://www.iso.org/standard/61897.html with
    https://www.iso.org/standard/70740.html | +| [ISO/IEEE 11073-10419] | ISO/IEEE 11073-10419:2016, Health informatics – Personal health device communication – Part 10419: Device specialization – Insulin pump.
    https://www.iso.org/standard/69528.html | +| [ISO/IEEE 11073-10420] | ISO/IEEE 11073-10420-2012, Health informatics – Personal health device communication – Part 10420: Device specialization – Body composition analyzer.
    https://www.iso.org/standard/61055.html | +| [ISO/IEEE 11073-10421] | ISO/IEEE 11073-10421:2012, Health informatics – Personal health device communication – Part 10421: Device specialization – Peak expiratory flow monitor (peak flow).
    https://www.iso.org/standard/61056.html | +| [ISO/IEEE 11073-10424] | ISO/IEEE 11073-10424:2016, Health informatics – Personal health device communication – Part 10424: Device specialization – Sleep apnoea breathing therapy equipment (SABTE).
    https://www.iso.org/standard/68906.html
    NOTE – equivalent to IEEE 11073-10424-2014, Health informatics – Personal health device communication – Part 10424: Device Specialization – Sleep Apnoea Breathing Therapy Equipment (SABTE) ,
    http://dx.doi.org/10.1109/IEEESTD.2014.6911927 | +| [ISO/IEEE 11073-10425] | ISO/IEEE 11073-10425:2016, Health informatics – Personal health device communication – Part 10425: Device specialization – Continuous glucose monitor (CGM).
    https://www.iso.org/standard/67821.html | +| [ISO/IEEE 11073-10427] | ISO/IEEE 11073-10427:2018, Health informatics – Personal health device communication – Part 10427: Device specialization – Power status monitor of personal health devices.
    https://www.iso.org/standard/73759.html . Same publication as
    https://standards.ieee.org/findstds/standard/11073-10427-2016.html . | +| [ISO/IEEE 11073-10441] | ISO/IEEE 11073-10441-2015, Health informatics – Personal Health Device Communication – Part 10441: Device Specialization – Cardiovascular Fitness and Activity Monitor.
    https://www.iso.org/standard/64868.html | +| [ISO/IEEE 11073-10442] | ISO/IEEE 11073-10442:2015, Health informatics – Personal health device communication – Part 10442: Device specialization – Strength fitness equipment.
    http://standards.ieee.org/findstds/standard/11073-10442-2008.html | + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [ISO/IEEE 11073-10471] | ISO/IEEE 11073-10471:2010, Health informatics – Personal health device communication – Part 10471: Device specialization – Independent living activity hub.
    https://www.iso.org/standard/54328.html | +| [ISO/IEEE 11073-10472] | ISO/IEEE 11073-10472:2012, Health informatics – Personal health device communication – Part 10472: Device specialization – Medication monitor.
    https://www.iso.org/standard/54364.html | + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +None. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------------------| +| ATS | Abstract Test Suite | +| DUT | Device Under Test | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IUT | Implementation Under Test | +| IP | Insulin Pump | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCHA | Personal Connected Health Alliance | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| PSM | Power Status Monitor | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | + +| | | +|------|--------------------------------------| +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| SSP | Secure Simple Pairing | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | + +## 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2017 | – | 7.0 | Release 2017 of the CDG including maintenance updates of the CDG 2016 and additional guidelines that cover new functionalities. | – | +| 2016 plus errata | [b-ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810] | 4.1 | Release 2013 plus errata noting all ratified | – | + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|---------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| | (2013)] | | bugs [b-CDG 2013]. | | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6 and 2.1.8 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + +- Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) +- Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Subgroup 1.3.17: Power status monitor (PSM) +- Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 1.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 1.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +– Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - **Subgroup 2.1.1: Design guidelines: Common (DGC)** + - **Subgroup 2.1.2: USB design guidelines (UDG)** + - **Subgroup 2.1.3: Bluetooth design guidelines (BDG)** + - **Subgroup 2.1.4: Cardiovascular design guidelines (CVDG)** + - **Subgroup 2.1.5: Activity hub design guidelines (HUBDG)** + - **Subgroup 2.1.6: ZigBee design guidelines (ZDG)** + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - **Subgroup 2.1.8: NFC design guidelines (NDG)** + +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) + - Subgroup 2.3.17: Power status monitor (PSM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + - Subgroup 2.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of this Annex can be downloaded from . See [b-PHD PICS & PIXIT] and [b-PHG PICS & PIXIT] and [b-TI]. + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case: + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth Low Energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test: + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing: + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 2.1.1 – Design guidelines: Common (DGC) + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/TR/DGC/BV-002_B | | | +| TP label | Unsupported_Device: Unsupported Class | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Unsupport 1;M | Unsupport 7;M | +| Test purpose |

    Check that:

    If a Continua service component does not support at least one Continua certified device class supported by the client component and the client component only accepts Continua certified devices, then the Continua PAN/ Sensor-LAN client components shall request to release association with a Continua service component using a result field no-more-configurations

    [AND]

    Continua PAN/ Sensor-LAN client components shall notify the user of failure of the connection and corresponding reason, if it has released or rejected the association according to requirement 11073_Unsupported_Device_Rejection

    [AND]

    Continua PAN/ Sensor-LAN client components with appropriate UI capabilities should use the following text string to notify the user of the connection failure in accordance with guideline 11073_Unsupported_Device_UserNotification_Client: "Thank you for choosing Continua certified personal health products. The device you are connecting either has not been Continua certified or the data is not intended for use in this solution. Please see your user manual for more details."

    | | | +| Applicability | (C_MAN_OXP_000) AND (NOT(C_MAN_OXP_047)) AND ((NOT(C_MAN_OXP_052)) OR (NOT(C_MAN_OXP_054)) OR (NOT(C_MAN_OXP_055)) OR (NOT(C_MAN_OXP_056)) OR (NOT(C_MAN_OXP_057)) OR (NOT(C_MAN_OXP_058)) OR (NOT(C_MAN_OXP_059)) OR (NOT(C_MAN_OXP_060)) OR (NOT(C_MAN_OXP_061)) OR (NOT(C_MAN_OXP_062)) OR (NOT(C_MAN_OXP_051)) OR (NOT(C_MAN_OXP_066)) OR (NOT(C_MAN_OXP_070)) OR (NOT(C_MAN_OXP_072)) OR (NOT(C_MAN_OXP_074)) OR (NOT(C_MAN_OXP_075)) OR (NOT ((C_MAN_OXP_064) OR (C_MAN_OXP_065)))) AND (C_MAN_DGC_004) | | | +| Other PICS | | | | +| Initial condition | The client under test is in the Unassociated state. The simulated service RegCertDataList and SystemTypeSpecList do not contain any Continua device class. | | | +| Test procedure |
    1. The simulated service sends an AARQ to the client under test.
    2. The client responds with an AARE.
    3. The client sends a GET MDS service request.
    4. The simulated service responds with the MDS object.
    | | | +| Pass/Fail criteria |
    • After step 4 a Release Request must be sent.
    • The reason for the Release Request must be "no-more-configurations".
    • The client must show an Association Failure message as shown in the documentation, it is recommended to be "Thank you for choosing Continua certified personal health products. The device you are connecting either has not been Continua certified or the data is not intended for use in this solution. Please see your user manual for more details."
    | | | +| Notes | This TP assumes that a GET MDS service is performed by the client to retrieve the data from the supported device classes. See bug http://continua.plugfest.com/show_bug.cgi?id=67 | | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/TR/DGC/BV-004 | | | +| TP label | Simultaneous Scanners | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 13;M | | +| Test purpose |

    Check that:

    Continua PAN client components shall not simultaneously turn on multiple scanners that embed the same measurement object provided by a single service component

    | | | +| Applicability | (C_MAN_OXP_000) AND (C_MAN_OXP_001 OR C_MAN_OXP_006) | | | +| Other PICS | | | | +| Initial condition | The client under test is in the Operating state. The Personal Health Device (PHD) has in its configurations two scanner objects that refer to the same metric object. | | | +| Test procedure |
    1. Make the simulated Personal Health Gateway (PHG) start the transfer of one of the scanner objects.
    2. Then force the PHG under test to start the transfer of the other scanner object.
    | | | +| Pass/Fail criteria |

    Check that both scanners are not simultaneously turned on by the simulated PHG:

    • If after step 2, the PHG sends a Set Operational State disabling the first scanner and then it sends a Set Operational State to enable the second scanner, the verdict is pass.
    • If after step 2, the PHG does not send any message, the verdict is pass.
    • If after step 2, the PHG sends a Set Operational State enabling the second scanner, the verdict is fail.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/TR/DGC/BV-005 | | | +| TP label | PM-Store Date-and-Time adjustment | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 16; M | | +| Test purpose |

    Check that:

    Continua PAN client components that receive a Date-and-Time update from a Continua PAN service component in the middle of a PM-Segment transfer shall use the service component's time reference at time the first segment entry is transmitted as the reference for the full segment regardless of any time changes that occur while the segment continues to be transferred

    | | | +| Applicability | (C_MAN_OXP_000) AND (C_MAN_OXP_003) | | | +| Other PICS | | | | +| Initial condition | The client under test is in the Operating state. The PHD has in its configuration a PM-Store object. | | | +| Test procedure |
    1. Make the PHG under test perform a Trig-Segment-Data-Xfer.
    2. The simulated PHD responds to the message with a "TrigSegmDataXferRsp".
    3. The simulated PHD sends a Confirmed event report:
      1. Data APDU
        • Type = Remote Operation Invoke Confirmed Event ReportAction
        • HANDLE = PM-Store obj-handle
        • Action = 0x0D 0x21 (MDC_NOTI_SEGMENT_DATA)
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • SegmentDataEvent.SegmDataEventDescr = SEQUENCE:
      • ▪ segm-instance
      • ▪ segmt-evt-entry-index
      • ▪ segmt-evt-entry-count
      • ▪ segmt-evt-status = Bit 0 must be set

    4. The PHG under test sends a response to the previous message.

    5. The simulated PHD sends a confirmed variable format event report to update the Date-and-Time attribute on the MDS.

    6. The PHG under test sends the confirmation response for the previous message.

    7. The simulated PHD sends a Confirmed event report:

    • a. Data APDU
      • Type = Remote Operation Invoke Confirmed Event ReportAction
      • HANDLE = PM-Store obj-handle
      • Action = 0x0D 0x21 (MDC_NOTI_SEGMENT_DATA)
      • SegmentDataEvent.SegmDataEventDescr = SEQUENCE:
        • ▪ segm-instance
        • ▪ segmt-evt-entry-index
        • ▪ segmt-evt-entry-count
        • ▪ segmt-evt-status = Bit 0 is set to 0 and bit 1 set to 1 (this segment contains the last segment entry).

    8. The PHG under test sends a response to the previous message.

    | +| Pass/Fail criteria |
    • • Check that the PHG sends the response in steps 6 and 7.
    • • Ask the operator to check if the PHG under test uses the PHD's time reference at the time the first segment entry is transmitted as the reference for the full segment.
    | +| Notes | | + +## A.3 Subgroup 2.1.2 – USB design guidelines (UDG) + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PAN/PHG/TR/UDG/BI-000 | | | +| TP label | PAN_USB_PHDC_20601_10101_Client | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Data_mess 5;M | | +| Test purpose | Check that:
    Continua PAN wired USB client components shall not pre-filter and reject a service component based on the wDevSpecializations field(s) value(s) | | | +| Applicability | (C_MAN_OXP_000) AND (C_MAN_OXP_038) AND ((NOT(C_MAN_OXP_052)) OR (NOT(C_MAN_OXP_054)) (NOT(C_MAN_OXP_055)) OR (NOT(C_MAN_OXP_056)) OR (NOT(C_MAN_OXP_057)) OR (NOT(C_MAN_OXP_058)) OR (NOT(C_MAN_OXP_059)) OR (NOT(C_MAN_OXP_060)) OR (NOT(C_MAN_OXP_061)) OR (NOT(C_MAN_OXP_062)) OR (NOT(C_MAN_OXP_051)) OR (NOT(C_MAN_OXP_070)) OR (NOT(C_MAN_OXP_072)) OR (NOT(C_MAN_OXP_074)) OR (NOT(C_MAN_OXP_075)) OR (NOT ((C_MAN_OXP_064) OR (C_MAN_OXP_065)))) | | | +| Other PICS | | | | +| Initial condition | The client under test is in the Disconnected state. | | | +| Test procedure | 1. Connect the USB connector of the simulated PHD to the PHG.
    2. The simulated PHD implements a device specialization that the PHG does not support. The simulated PHD sends a PHDC Class Function Descriptor where the | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    wDevSpecializations field includes the ISO/IEEE 11073-20601 version 1.0 MDC_DEV_SPEC_PROFILE_* value for a device specialization that is not supported by the PHG.

    3. The enumeration process finishes successfully.

    4. The simulated PHD sends an Association Request message.

    5. The PHG under test shall reply with a 20601 APDU.

    | +| Pass/Fail criteria |

    In step 3, the enumeration process shall finish successfully although the simulated PHD implements a device specialization that the PHG under test does not support, because the rejection shall occur in the higher layers.

    In step 5, the PHG under test sends a 20601 APDU.

    | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------| +| TP Id | TP/PAN/PHG/TR/UDG/BV-002 | | | +| TP label | Quality of Service | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | QoS 1;C | QoS 2;C | +| Test purpose |

    Check that:

    Continua PAN wired USB service and client components that implement the Continua best.medium QoS bin shall utilize the USB PHDC best.medium QoS bin to do this.

    [AND]

    Continua PAN wired USB service and client components that implement the Continua good.medium QoS bin shall utilize the USB PHDC good.medium QoS bin to do this

    | | | +| Applicability | (C_MAN_OXP_038) AND (C_MAN_OXP_000) AND (C_HOST_PHDC_003) | | | +| Other PICS | C_MAN_OXP_001, C_MAN_OXP_006 | | | +| Initial condition | The client under test is in the Disconnected state. | | | +| Test procedure |
    1. Plug-in the host under test and the simulated device, the enumeration process shall then start automatically. The simulated device will inform the host under test that it supports the Meta-Data Message Preamble Feature setting bit0 of the bmCapability field of the PHDC Class Function Descriptor to 1. Furthermore the bmLatencyReliability field of the QoS Descriptor of the OUT BULK endpoint is set to 0x0A; this means that good.medium and best.medium QoS can be sent across that endpoint.
    2. Upon reception and confirmation of descriptors, if the host under test recognizes the PHDC device class, it shall send a SET_CONFIGURATION request to the simulated device as a last step of the enumeration process.
    3. Perform the action on the host that enables the Meta-Data Message Preamble feature.
    4. The simulated device issues an "Association Request" without a preceding Meta-Data Message Preamble to the host under test.
    5. The host under test will send a SET_FEATURE(META-DATA) message in order to enable the Meta-Data Message Preamble.
    6. The host under test will send a Meta-Data Message Preamble that precedes the Association Response, because this feature has been enabled. The bmLatencyReliability field shall be set to 0x08, indicating best.medium QoS in the next "bNumTransfers" messages. Furthermore, the bNumTransfers field is captured.
    7. Then the host under test will send an "Association Response" (accepted or accepted-unknown-config).
    8. The simulated device issues a "bNumTransfers-1" confirmed event report if the host under test has sent an Association Response (accepted), or a configuration and "bNumTransfers -2" confirmed event report if the host has sent an Association Response (accepted-unknown-config).
    9. If during this process the host under test has not sent a Get MDS message, it will be required.
    10. The host under test will send a new Meta-Data Message Preamble that precedes the Get
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    MDS message. The bmLatencyReliability field shall be set to 0x08, indicating best.medium QoS in the next "bNumTransfers" messages. Furthermore, the bNumTransfers field is captured.

    11. The simulated device issues a "bNumTransfers -1" confirmed event report.

    12. A Set Time message is required for the host under test.

    13. The host under test will send a new Meta-Data Message Preamble that precedes the Set Time message. The bmLatencyReliability field shall be set to 0x08, indicating best.medium QoS in the next "bNumTransfers" messages. Furthermore, the bNumTransfers field is captured.

    14. The simulated device issues a "bNumTransfers -1" confirmed event report.

    15. If the host under test has not sent a Set Scanner message yet, this will be required.

    16. The host under test will send a new Meta-Data Message Preamble that precedes the Set Scanner message. The bmLatencyReliability field shall be set to 0x08, indicating best.medium QoS in the next "bNumTransfers" messages.

    | +| Pass/Fail criteria | In steps 6, 10, 13 and 16, the bmLatencyReliability field of the Meta-Data Message Preamble is set to 0x08. | +| Notes | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------| +| TP Id | TP/PAN/PHG/TR/UDG/BV-004_A | | | +| TP label | Wired_PAN_USB_1_1 | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | data_rate 1;M | data_rate 3; M | +| Test purpose |

    Check that:

    Continua PAN wired USB client components shall not use low speed

    [AND]

    Continua PAN wired USB components shall implement at least USB 1.1 or any superior version compatible with USB 1.1

    | | | +| Applicability | C_MAN_OXP_038 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The client under test is in the Disconnected state. | | | +| Test procedure |
    1. Connect the USB connector of the simulated PHD to the PHG under test. The simulated PHD has set the bcdUSB field to 0x0110.
    2. Send an "Association Request" from the simulated PHD to the PHG.
    3. The PHG responds with a valid response ("Association Response", "Association Abort").
    4. Disconnect the PHG and the simulated PHD.
    | | | +| Pass/Fail criteria | In step 3, the PHG under test sends a valid response to the simulated PHD. | | | +| Notes | | | | + +| | | | | +|--------------------------|------------------------------------------------------------|------------------------|--| +| TP Id | TP/PAN/PHG/TR/UDG/BV-004_B | | | +| TP label | Wired_PAN_USB_2_0 | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | data_rate 2;R | | +| Test purpose | Continua PAN wired USB components should implement USB 2.0 | | | +| Applicability | C_MAN_OXP_038 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The client under test is in the Disconnected state. | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Connect the USB connector of the simulated PHD to the PHG under test. The simulated PHD has set the bcdUSB field to 0x0200.
    2. 2. Send an "Association Request" from the simulated PHD to the PHG.
    3. 3. The PHG responds with a valid response ("Association Response", "Association Abort").
    4. 4. Disconnect the PHG and the simulated PHD.
    | +| Pass/Fail criteria | In steps 2 and 3, if the PHG supports USB 2.0, then it will post a read request to get the PHD's Association Request. Since this is a recommended behaviour, issue a warning if the PHG does not do this. | +| Notes | | + +## A.4 Subgroup 2.1.3 – Bluetooth design guidelines (BDG) + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------| +| TP Id | TP/PAN/PHG/TR/BDG/BV-000 | | | +| TP label | Wireless_PAN_BT_Discovery_and_Pairing | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 1;M | Discovery_Pairing 5;M | +| | | Discovery_Pairing 10;R | Discovery_Pairing 6;M | +| Test purpose | Check that:
    PHG should not be discoverable unless put in that mode
    [AND]
    The PHG shall initiate discovery (a Bluetooth “inquiry”)
    [AND]
    The PHG shall have a documented way (decided by the vendor) to initiate a search for service components that are “discoverable”
    [AND]
    Once a PHG has discovered an PHD, it shall support pairing with compatible PHDs. | | | +| Applicability | C_MAN_OXP_039 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. 1. Reset the PHG under test to the default configuration and turn it on.
    2. 2. The simulated PHD starts a discovery process.
    3. 3. Once that discovery process is completed, verify that the PHG under test has not been discovered by the test tool.
    4. 4. Set the test tool simulated PHD in discoverable mode.
    5. 5. Follow the steps listed in the product documentation to ask the PHG to initiate a search for discoverable service components.
    6. 6. The PHG under test initiates a search for discoverable service components.
    7. 7. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | | | +| Pass/Fail criteria | In step 3, the PHG is not discovered by the PHD. If it is discovered by the test tool, the test tool gives a Warning message.
    In step 7, the PHG under test is paired with the simulated PHD. | | | +| Notes | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------|--| +| TP Id | TP/PAN/PHG/TR/BDG/BV-002 | | | | +| TP label | Wireless_PAN_BT_Pairing_Data_Client | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Discovery_Pairing 15; M | Discovery_Pairing 16; R | | +| Test purpose |

    Check that:

    PHG shall store the pairing data from at least the most recently paired device in such a way that the data will be retained through normal power interruptions, including battery replacement

    [AND]

    PHG should store pairing data for at least the number of devices for which they are intended to simultaneously support

    | | | | +| Applicability | C_MAN_OXP_039 AND (C_MAN_OXP_000) | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Disconnected state and they have not been paired before. | | | | +| Test procedure |
    1. Reset the PHG under test to default configuration and turn it on.
    2. Set the simulated PHD in discoverable and pairable mode.
    3. The PHG initiates a discovery process, it finds the simulated PHD. It establishes a pairing with it and starts a Bluetooth connection.
    4. Turn off the PHG under test and remove the batteries or unplug the power supply.
    5. Turn on the PHG under test again.
    6. Set the simulated PHD in discoverable and pairable mode.
    7. The PHG under test initiates a discovery process, it finds the simulated PHD and starts a Bluetooth connection with it.
    | | | | +| Pass/Fail criteria | In step 7, the pairing process shall not be dispatched again because both devices have stored the pairing data from a previous pairing process. | | | | +| Notes | | | | | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PAN/PHG/TR/BDG/BV-003 | | | | +| TP label | Wireless_PAN_BT_Pairing_Creation_Alert_Client | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Notify 1;M | | | +| Test purpose |

    Check that:

    PHG shall inform the user when a new pairing relationship is created

    | | | | +| Applicability | C_MAN_OXP_039 AND (C_MAN_OXP_000) | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Disconnected state and they have not been paired before. | | | | +| Test procedure |
    1. Set the simulated PHD in discoverable and pairable mode.
    2. The PHG under test initiates discovery process as stated in the product documentation.
    3. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    4. Check the information shown by the PHG under test about the pairing.
    | | | | +| Pass/Fail criteria | The PHG under test must inform the user when a new pairing relationship is created as stated in the documentation. | | | | +| Notes | | | | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PAN/PHG/TR/BDG/BV-004 | | | +| TP label | Wireless_PAN_BT_Security_Failure_Client | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Notify 3;M | Notify 5;M | +| Test purpose |

    Check that:

    When a pairing fails, PHG shall inform the user whether the failure was because no PHD was found (discovery failed), no data types are supported in common by both PHD and PHG (incompatible device), or the pairing failed (pairing failure)

    [AND]

    When any authentication/security failure is encountered by the PHG, it shall notify the user

    | | | +| Applicability | (C_MAN_OXP_000) AND (C_MAN_OXP_039) AND ((NOT(C_MAN_OXP_052)) OR (NOT(C_MAN_OXP_054)) OR (NOT(C_MAN_OXP_055)) OR (NOT(C_MAN_OXP_056)) OR (NOT(C_MAN_OXP_057)) OR (NOT(C_MAN_OXP_058)) OR (NOT(C_MAN_OXP_059)) OR (NOT(C_MAN_OXP_060)) OR (NOT(C_MAN_OXP_061)) OR (NOT(C_MAN_OXP_062)) OR (NOT(C_MAN_OXP_051)) OR (NOT(C_MAN_OXP_070)) OR (NOT(C_MAN_OXP_072)) OR (NOT(C_MAN_OXP_074)) OR (NOT(C_MAN_OXP_075)) OR (NOT((C_MAN_OXP_064) OR (C_MAN_OXP_065)))) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. 1. Disable the simulated PHD (it is not discoverable).
    2. 2. The PHG under test initiates discovery as stated in the product documentation.
    3. 3. The simulated PHD is not discovered because it has not been initialized yet. Check the PHG under test for error messages.
    4. 4. Configure the simulated PHD with a device specialization not supported by the PHG under test.
    5. 5. Set the simulated PHD in discoverable mode.
    6. 6. The PHG under test starts a discovery and pairing process with the simulated PHD.
    7. 7. Check the PHG under test for error messages.
    8. 8. Restart the simulated PHD.
    9. 9. Restart the PHG under test.
    10. 10. Configure simulated PHD with a device specialization supported by the PHG under test.
    11. 11. Disable the pairable mode in the simulated PHD.
    12. 12. The PHG under test starts a discovery and pairing process with the simulated PHD.
    13. 13. Check the PHG under test for error messages.
    14. 14. Compare the three error messages.
    | | | +| Pass/Fail criteria |
    • • In step 3, the PHG under test shall inform the user that the pairing process cannot be completed (the simulated PHD has not been found).
    • • In step 7, the PHG under test shall inform the user that pairing process cannot be completed (the simulated PHD implements an unsupported specialization).
    • • In step 13, the PHG under test shall inform the user that the pairing process cannot be completed (the simulated PHD is not in pairable mode).
    • • In step 14, the three error messages shall be different.
    | | | +| Notes | | | | + +| | | +|-----------------|--------------------------| +| TP Id | TP/PAN/PHG/TR/BDG/BV-006 | +| TP label | Wireless_PAN_BT_QoS | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------| +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | QoS 1;C | QoS 2;C | +| Test purpose | Check that:
    PHG that implement the Continua best.medium QoS bin shall utilize the HDP reliable data channel type to do this
    [AND]
    PHG that implement the Continua good.medium QoS bin shall utilize the HDP streaming data channel type to do this | | | +| Applicability | C_MAN_OXP_039 AND (C_MAN_OXP_000) | | | +| Other PICS | C_MAN_OXP_001, C_MAN_OXP_006 | | | +| Initial condition | The PHG under test is in the Disconnected state. | | | +| Test procedure | NOTE – This test case must be executed manually. Bluetooth sniffer is needed to perform the verification required in this test case.
    1. 1. Put the simulated PHD in discoverable mode.
    2. 2. Follow the steps listed in the product documentation to ask the PHG to initiate a search for discoverable service components.
    3. 3. The PHG under test initiates a search for discoverable service components as stated in the product documentation.
    4. 4. Once the simulated PHD has been discovered, the simulated PHD issues an "Association Request" to the PHG under test.
    5. 5. The PHG under test issues an "Association response" on the HDP reliable data channel.
    6. 6. IF C_MAN_OXP_085 THEN:
      1. a. The PHG under test issues a roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The simulated PHD issues a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    7. 7. The PHG under test sends a Set Time message on the HDP reliable data channel.
    8. 8. The simulated PHD issues a Set Time response.
    9. 9. The simulated PHD issues a confirmed event report.
    10. 10. The PHG under test sends a confirmation on the HDP reliable data channel.
    11. 11. If the PHG under test supports scanners, the PHG issues a confirmed set (scanner) on the HDP reliable data channel and the simulated PHD sends a set (scanner) response.
    12. 12. The simulated PHD issues an "Association Release Request".
    13. 13. The PHG under test sends an "Association Release Response" on the HDP reliable data channel.
    | | | +| Pass/Fail criteria | The PHG under test issues all responses on the best.medium QoS bin as defined by the steps above. | | | +| Notes | | | | + +| | | | | +|----------------------|--------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PAN/PHG/TR/BDG/BV-007 | | | +| TP label | Support for legacy Bluetooth 2.0 PIN entry pairing | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 18;M | | +| Test purpose | Check that:
    PHG shall support legacy (BT 2.0) Pin Entry pairing | | | +| Applicability | C_MAN_OXP_039 AND C_MAN_OXP_000 | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in the Disconnected state and they have not been paired before. | +| Test procedure |
    1. 1. The test tool simulated PHD is configured without secure simple pairing (SSP) support, it supports legacy PIN pairing only. The simulated PHD PIN is as specified in PIXIT I_MAN_BDG_003.
    2. 2. Set the test tool simulated PHD in discoverable and pairable mode.
    3. 3. The PHG under test initiates discovery process as stated in the product documentation.
    4. 4. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | +| Pass/Fail criteria | In step 4, the PHG under test completes the pairing process successfully. | +| Notes | | + +| | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PAN/PHG/TR/BDG/BV-008 | | +| TP label | Secure Simple Pairing with PHD with NoInputNoOutput capabilities | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | Discovery_Pairing 17;M | +| Test purpose |

    Check that:

    PHG shall support all pairing methods for Bluetooth 2.1, including Numeric Comparison, and Passkey Entry, if the PHG has the appropriate I/O capabilities

    | | +| Applicability | C_MAN_OXP_039 AND C_MAN_OXP_000 | | +| Other PICS | | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in the Disconnected state and they have not been paired before. | | +| Test procedure |
    1. 1. Check the PHG under test Secure Simple Pairing support declared in PIXIT I_MAN_BDG_004.
    2. 2. Check PHG under test IO capabilities declared in PIXIT I_MAN_BDG_005 and the Man In The Middle (MITM) protection declared in PIXIT I_MAN_BDG_006
      1. a. IF the PHG under test does not support MITM protection (PIXIT I_MAN_BDG_006 = FALSE) THEN the test tool simulated PHD is configured with Secure Simple Pairing, NoInputNoOutput capabilities and without MITM protection. The Just Works Association Model shall be used during the pairing process and the generated link key will be unauthenticated (without MITM protection).
      2. b. IF the PHG under test supports MITM protection (PIXIT I_MAN_BDG_006 = TRUE) THEN
        • • IF the PHG under test supports NoInputNoOutput capabilities (PIXIT I_MAN_BDG_005 = 3) THEN the combination of IO capabilities and MITM support declared by the PHG under test in PIXITs is not feasible and the Test Case ends giving a FAIL verdict due to inconsistency among the PHG under test SSP features declared in PIXITs
        • • IF the PHG under test supports other IO capabilities (PIXIT I_MAN_BDG_005 = 0 or 1 or 2) it will not pair with PHDs with NoInputNoOutput capabilities because they do not fulfil the security level required (i.e. MITM protection) and the Test Case execution ends giving a PASS verdict
    3. 3. Set the test tool simulated PHD in discoverable and pairable mode.
    4. 4. The PHG under test initiates the discovery process as stated in the product documentation.
    5. 5. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | In step 1, the PHG under test supports Secure Simple Pairing (PIXIT I_MAN_BDG_004 = TRUE).
    In step 5, the PHG under test completes the pairing process successfully. | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PAN/PHG/TR/BDG/BV-009 | | | +| TP label | Secure Simple Pairing with PHD with DisplayOnly capabilities | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 17;M | | +| Test purpose | Check that:
    PHG shall support all pairing methods for Bluetooth 2.1, including Numeric Comparison, and Passkey Entry, if the PHG has the appropriate I/O capabilities | | | +| Applicability | C_MAN_OXP_039 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. 1. Check the PHG under test Secure Simple Pairing support declared in PIXIT I_MAN_BDG_004
    2. 2. Check the PHG under test IO capabilities declared in PIXIT I_MAN_BDG_005 and the Man In The Middle (MITM) protection declared in PIXIT I_MAN_BDG_006
      1. a. IF the PHG under test does not support MITM protection (PIXIT I_MAN_BDG_006 = FALSE) THEN the test tool simulated PHD is configured with Secure Simple Pairing, NoInputNoOutput capabilities and without MITM protection and the Just Works Association Model shall be used during the Pairing process and the generated link key will be unauthenticated (without MITM protection).
      2. b. IF the PHG under test supports MITM protection (PIXIT I_MAN_BDG_006 = TRUE) THEN
        • • IF the PHG under test supports KeyboardOnly capabilities (PIXIT I_MAN_BDG_005 = 2) THEN the test tool simulated PHD is configured with Secure Simple Pairing, DisplayOnly capabilities and with MITM protection and the Passkey Entry Association Model shall be used during the Pairing process and the generated link key will be authenticated (with MITM protection).
        • • IF the PHG under test supports DisplayOnly or DisplayYesNo capabilities (PIXIT I_MAN_BDG_005 = 0 or 1) THEN it will not pair with the PHDs with DisplayOnly capabilities because they do not fulfil the security level required (i.e. MITM protection) and the test case execution ends giving a PASS verdict.
        • • IF the PHG under test supports NoInputNoOutput capabilities (PIXIT I_MAN_BDG_005 = 3) THEN the combination of IO capabilities and MITM support declared by the PHG under test in PIXITs is not feasible and the test case ends giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs.
    3. 3. Set the test tool simulated PHD in discoverable and pairable mode.
    4. 4. The PHG under test initiates a discovery process as stated in the product documentation.
    5. 5. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | | | +| Pass/Fail criteria | In step 1, the PHG under test supports Secure Simple Pairing (PIXIT I_MAN_BDG_004 = TRUE).
    In step 5, the PHG under test completes the pairing process successfully. | | | +| Notes | | | | + +| | | +|-----------------|---------------------------------------------------------------| +| TP Id | TP/PAN/PHG/TR/BDG/BV-010 | +| TP label | Secure Simple Pairing with PHD with DisplayYesNo capabilities | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing 17;M | | +| Test purpose | Check that:
    PHG shall support all pairing methods for Bluetooth 2.1, including Numeric Comparison, and Passkey Entry, if the PHG has the appropriate I/O capabilities | | | +| Applicability | C_MAN_OXP_039 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. 1. Check the PHG under test Secure Simple Pairing support declared in PIXIT I_MAN_BDG_004.
    2. 2. Check the PHG under test IO capabilities declared in PIXIT I_MAN_BDG_005 and the Man In The Middle (MITM) protection declared in PIXIT I_MAN_BDG_006
      1. a. IF the PHG under test does not support MITM protection (PIXIT I_MAN_BDG_006 = FALSE) THEN the test tool simulated PHD is configured with Secure Simple Pairing, NoInputNoOutput capabilities and without MITM protection and the Just Works Association Model shall be used during the Pairing process and the generated link key will be unauthenticated (without MITM protection).
      2. b. IF the PHG under test supports MITM protection (PIXIT I_MAN_BDG_006 = TRUE) THEN
        • • IF the PHG under test supports DisplayYesNo capabilities (PIXIT I_MAN_BDG_005 = 1) THEN the test tool simulated PHD is configured with Secure Simple Pairing, DisplayYesNo capabilities and with MITM protection and the Numeric Comparison Association Model shall be used during the Pairing process and the generated link key will be authenticated (with MITM protection).
        • • IF the PHG under test supports KeyboardOnly capabilities (PIXIT I_MAN_BDG_005 = 2) THEN the test tool simulated PHD is configured with Secure Simple Pairing, DisplayYesNo capabilities and with MITM protection and the Passkey Entry Association Model shall be used during the Pairing process and the generated link key will be authenticated (with MITM protection).
        • • IF the PHG under test supports DisplayOnly capabilities (PIXIT I_MAN_BDG_005 = 0) THEN it will not pair with PHDs with DisplayYesNo capabilities because they do not fulfil the security level required (i.e. MITM protection) and the test case execution ends giving a PASS verdict.
        • • IF the PHG under test supports NoInputNoOutput capabilities (PIXIT I_MAN_BDG_005 = 3) THEN the combination of IO capabilities and MITM support declared by the PHG under test in PIXITs is not feasible and the test case ends giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs.
    3. 3. Set the test tool simulated PHD in discoverable and pairable mode.
    4. 4. The PHG under test initiates the discovery process as stated in the product documentation.
    5. 5. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | | | +| Pass/Fail criteria | In step 1, the PHG under test supports Secure Simple Pairing (PIXIT I_MAN_BDG_004 = TRUE).
    In step 5, the PHG under test completes the pairing process successfully. | | | +| Notes | | | | + +| | | | | +|-----------------|---------------------------------------------------------------|------------------------|--| +| TP Id | TP/PAN/PHG/TR/BDG/BV-011 | | | +| TP label | Secure Simple Pairing with PHD with KeyboardOnly capabilities | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable | Discovery_Pairing 17;M | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | items | | | +| Test purpose | Check that:

    The PHG shall support all pairing methods for Bluetooth 2.1, including Numeric Comparison, and Passkey Entry, if the PHG has the appropriate I/O capabilities | | | +| Applicability | C_MAN_OXP_039 AND C_MAN_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in the Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. 1. Check the PHG under test Secure Simple Pairing support declared in PIXIT I_MAN_BDG_004
    2. 2. Check the PHG under test IO capabilities declared in PIXIT I_MAN_BDG_005 and the Man In The Middle (MITM) protection declared in PIXIT I_MAN_BDG_006
      1. a. IF the PHG under test does not support MITM protection (PIXIT I_MAN_BDG_006 = FALSE) THEN the test tool simulated PHD is configured with Secure Simple Pairing, NoInputNoOutput capabilities and without MITM protection and the Just Works Association Model shall be used during the Pairing process and the generated link key will be unauthenticated (without MITM protection).
      2. b. IF the PHG under test supports MITM protection (PIXIT I_MAN_BDG_006 = TRUE) THEN
        • • IF the PHG under test supports DisplayOnly capabilities (PIXIT I_MAN_BDG_005 = 0) THEN the test tool simulated PHD is configured with Secure Simple Pairing, KeyboardOnly capabilities and with MITM protection and the Passkey Entry Association Model shall be used during the Pairing process and the generated link key will be authenticated (with MITM protection).
        • • IF the PHG under test supports DisplayYesNo capabilities (PIXIT I_MAN_BDG_005 = 1) THEN the test tool simulated PHD is configured with Secure Simple Pairing, KeyboardOnly capabilities and with MITM protection and the Passkey Entry Association Model shall be used during the Pairing process and the generated link key will be authenticated (with MITM protection).
        • • IF the PHG under test supports KeyboardOnly capabilities (PIXIT I_MAN_BDG_005 = 2) THEN the test tool simulated PHD is configured with Secure Simple Pairing, KeyboardOnly capabilities and with MITM protection and the Passkey Entry Association Model shall be used during the Pairing process and the generated link key will be authenticated (with MITM protection).
        • • IF the PHG under test supports NoInputNoOutput capabilities (PIXIT I_MAN_BDG_005 = 3) THEN the combination of IO capabilities and MITM support declared by the PHG under test in PIXITs is not feasible and the test case ends giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs.
    3. 3. Set the test tool simulated PHD in discoverable and pairable mode.
    4. 4. The PHG under test initiates a discovery process as stated in the product documentation.
    5. 5. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | | | +| Pass/Fail criteria | In step 1, the PHG under test supports Secure Simple Pairing (PIXIT I_MAN_BDG_004 = TRUE).

    In step 5, the PHG under test completes the pairing process successfully. | | | +| Notes | | | | + +## A.5 Subgroup 2.1.4 – Cardiovascular device specialization design guidelines (CVDG) + +| | | | | +|-----------------|------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CVDG/BV-000 | | | +| TP label | Step Counter PHG Maximum APDU size | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Cardio_DG 2; M | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    Continua PAN/Sensor- LAN step counter client components shall be able to support a maximum APDU size of 6624 octets from Continua PAN/Sensor-LAN service components. | +| Applicability | C_MAN_OXP_023 AND C_MAN_CV_030 AND (C_MAN_OXP_000) | +| Other PICS | | +| Initial condition | The PHG and the simulated PHD are in the Operating state. | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • ▪ Count =2
        • ▪ Length = 6586
         ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 61441             attribute-value:                 '00.....( 6562 bytes)..... 00'O         }     } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • ▪ Count =2
        • ▪ Length = 64490
         ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 61441             attribute-value:                 '00.....( 64464 bytes)..... 00'O         }     } }
    | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 
     obj-handle: 1 attributes: AttributeList ::= {     AVA-Type ::= {         attribute-id: 2633         (MDC_ATTR_ENUM_OBS_VAL_SIMP _OID)         attribute-value: 1017 (MDC_HF_ACT_WALK)     } } }
    | +| | 4. Check the response of the PHG under test. | +| Pass/Fail criteria |
    • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • In step 4 the PHG under test must respond with a roer with reason = "protocol-violation".
    | +| Notes | | + +| | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/CVDG/BV-001 | | +| TP label | Step Counter PHG sub-specialization(profile) 1 | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | Cardio_DG 4; M | +| Test purpose | Check that:
    Continua PAN/ Sensor-LAN step counter client components shall support the Session and Distance object (all unit codes). | | +| Applicability | C_MAN_OXP_023 AND C_MAN_CV_030 AND (C_MAN_OXP_000) | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using a configuration that supports a Session and two Distance objects. The Unit-code for the first Distance object is MDC_DIM_X_STEP and for the second Distance object it is MDC_DIM_X_M. | | +| Test procedure |
    1. Send a confirmed variable format event report using a measurement for the second Distance object in meters.
    2. The simulated PHD waits until it receives a confirmation.
    | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data properly and applies meters to the observation (e.g. if there is a UI verify the measurement and date are displayed properly even if they are converted to a different set of units). | | +| Notes | | | + +| | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/CVDG/BV-002 | | +| TP label | Step Counter PHG sub-specialization(profile) 2 | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | Cardio_DG 4; M | +| Test purpose | Check that:
    Continua PAN/Sensor-LAN step counter client components shall support the Session and Distance object (all unit codes). | | +| Applicability | C_MAN_OXP_023 AND C_MAN_CV_030 AND (C_MAN_OXP_000) | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using a configuration that supports a Session and two Distance objects. The Unit-code for the first Distance object is MDC_DIM_X_STEP and for the second Distance object it is MDC_DIM_X_FOOT. | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Send a confirmed variable format event report using a measurement for the second Distance object in feet.
    2. 2. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data properly and applies feet to the observation (e.g. if there is a UI verify the measurement and date are displayed properly even if they are converted to a different set of units). | +| Notes | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CVDG/BV-003 | | | +| TP label | Step Counter PHG sub-specialization(profile) 3 | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Cardio_DG 4; M | | +| Test purpose | Check that:
    Continua PAN/Sensor-LAN step counter client components shall support the Session and Distance object (all unit codes). | | | +| Applicability | C_MAN_OXP_023 AND C_MAN_CV_030 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using a configuration that supports a Session and Distance object, and the unit-code for the Distance object is MDC_DIM_X_STEP. | | | +| Test procedure |
    1. 1. Send a confirmed variable format event report using a measurement for the Distance object in steps.
    2. 2. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data properly and applies steps to the observation (e.g. if there is a UI verify the measurement and date are displayed properly even if they are converted to a different set of units). | | | +| Notes | | | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CVDG/BV-004 | | | +| TP label | Step Counter PHG sub-specialization(profile) 4 | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Cardio_DG 6; M | | +| Test purpose | Check that:
    Continua PAN/ Sensor-LAN step counter client components may support the Subsession, Cadence, Speed, Stride Length, or Energy Expended objects as defined in [ISO/IEEE 11073-10441] | | | +| Applicability | C_MAN_OXP_023 AND C_MAN_CV_030 AND (C_MAN_CV_027 OR C_MAN_CV_010 OR C_MAN_CV_011 OR C_MAN_CV_017 OR C_MAN_CV_019) AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using a configuration that supports Session, Distance object, and optional objects supported by the PHG. (Unit-code for Distance object is MDC_DIM_X_STEP). | | | +| Test procedure |
    1. 1. Send a confirmed variable format event report using a measurement for every object in the configuration.
    2. 2. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data properly (e.g. if there is a UI verify that the measurement and date are displayed properly even if they are converted to a different set of units). | | | + +| | | +|-------|--| +| Notes | | +|-------|--| + +## A.6 Subgroup 2.1.5 – Activity hub device specialization design guidelines (HUBDG) + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-000 | | | +| TP label | Fall Sensor PHG sub-specialization (profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 1; M | | +| Test purpose |

    Check that:

    Continua PAN/ Sensor-LAN Fall Sensor client components shall implement the Fall Sensor enumeration object.

    | | | +| Applicability | C_MAN_HUB_016 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports a Fall Sensor object. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)
      IF the result of the Association Response was "accepted-unknown-config":
      1. 3. The simulated PHD sends a configuration event report, supporting a Fall Sensor object.
      2. 4. The PHG under test must respond with:
        1. a. APDU Type
          • – field-length = 2 bytes
          • – field-value = 0xE7 0x00 (PrstAdpu)
        2. b. Invoke-id
          • – field- type = INT-U16
          • – field-length = 2 bytes
          • – field-value = it must be the same as the invoke-id of the simulated PHD's message.
        3. c. Obj-Handle:
          • – field- type = HANDLE
          • – field-length = 2 bytes
          • – field-value = 0x00 0x00
        4. d. Event-time:
          • – field- type = INT-U32
          • – field-length = 4 bytes
          • – field-value = 0xXX 0xXX
        5. e. Event-type:
          • – field-length = 2 bytes
          • – field-value = MDC_NOTI_CONFIG
        6. f. The following six bytes indicate:
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • – Event-replay-info.length (2 bytes)
    • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
    ConfigReportRsp.config-result: accepted-config: 0x00 0x00 | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-001 | | | +| TP label | Motion Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 3; M | | +| Test purpose | Check that:

    Continua PAN/Sensor-LAN Motion Sensor client components shall implement the Motion Sensor enumeration object. | | | +| Applicability | C_MAN_HUB_017 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports a Motion Sensor object. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)
      IF the result of the Association Response was "accepted-unknown-config":
    3. 3. The simulated PHD sends a configuration event report, supporting a Motion Sensor object.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        • – field-length = 2 bytes
        • – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        • – field- type = HANDLE
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00
      4. d. Event-time:
        • – field- type = INT-U32
        • – field-length = 4 bytes
        • – field-value = 0xXX 0xXX
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • e. Event-type:
      • – field-length = 2 bytes
      • – field-value = MDC_NOTI_CONFIG
    • f. The following six bytes indicates:
      • – Event-replay-info.length (2 bytes)
      • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
      • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-002 | | | +| TP label | Enuresis Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 5; M | | +| Test purpose | Check that:
    Continua PAN/Sensor-LAN Enuresis Sensor client components shall implement the Enuresis Sensor enumeration object. | | | +| Applicability | C_MAN_HUB_018 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports an Enuresis Sensor object. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)
      IF the result of the Association Response was "accepted-unknown-config":
    3. 3. The simulated PHD sends a configuration event report, supporting an Enuresis Sensor object.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        • – field-length = 2 bytes
        • – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        • – field- type = HANDLE
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. Event-time:

    • – field- type = INT-U32
    • – field-length = 4 bytes
    • – field-value = 0xXX 0xXX

    e. Event-type:

    • – field-length = 2 bytes
    • – field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • – Event-replay-info.length (2 bytes)
    • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
    • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config" | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-003 | | | +| TP label | Contact Closure Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 7; M | | +| Test purpose |

    Check that:

    Continua PAN/Sensor-LAN Contact Closure Sensor client components shall implement the Contact Closure Sensor enumeration object.

    | | | +| Applicability | C_MAN_HUB_019 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports a Contact Closure Sensor object. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    IF the result of the Association Response was "accepted-unknown-config":

    1. 3. The simulated PHD sends a configuration event report, supporting a Contact Closure Sensor object.
    2. 4. The PHG under test must respond with:
      1. a. APDU Type
        • – field-length = 2 bytes
        • – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = it must be the same as the invoke-id of the simulated PHD's message.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • c. Obj-Handle:
      • – field- type = HANDLE
      • – field-length = 2 bytes
      • – field-value = 0x00 0x00
    • d. Event-time:
      • – field- type = INT-U32
      • – field-length = 4 bytes
      • – field-value = 0xXX 0xXX
    • e. Event-type:
      • – field-length = 2 bytes
      • – field-value = MDC_NOTI_CONFIG
    • f. The following six bytes indicates:
      • – Event-replay-info.length (2 bytes)
      • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
      • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-004 | | +| TP label | Switch Sensor PHG sub-specialization(profile) | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | Hub_DG 9; M | +| Test purpose | Check that:
    Continua PAN/Sensor-LAN Switch Sensor client components shall implement the Switch Sensor enumeration object. | | +| Applicability | C_MAN_HUB_020 AND (C_MAN_OXP_000) | | +| Other PICS | | | +| Initial condition | The simulated PHD supports a Switch Sensor object. | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    IF the result of the Association Response was "accepted-unknown-config":

    1. 3. The simulated PHD sends a configuration event report, supporting a Switch Sensor object.
    2. 4. The PHG under test must respond with:
      1. a. APDU Type
        • – field-length = 2 bytes
        • – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
    | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • – field- type = INT-U16
    • – field-length = 2 bytes
    • – field-value = it must be the same as the invoke-id of the simulated PHD's message.

    c. Obj-Handle:

    • – field- type = HANDLE
    • – field-length = 2 bytes
    • – field-value = 0x00 0x00

    d. Event-time:

    • – field- type = INT-U32
    • – field-length = 4 bytes
    • – field-value = 0xXX 0xXX

    e. Event-type:

    • – field-length = 2 bytes
    • – field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicates:

    • – Event-replay-info.length (2 bytes)
    • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
    • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-005 | | +| TP label | Dosage Sensor PHG sub-specialization(profile) | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | Hub_DG 11; M | +| Test purpose | Check that:

    Continua PAN/Sensor-LAN Dosage Sensor client components shall implement the Dosage Sensor enumeration object. | | +| Applicability | C_MAN_HUB_021 AND (C_MAN_OXP_000) | | +| Other PICS | | | +| Initial condition | The simulated PHD supports a Dosage Sensor object. | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    IF the result of the Association Response was "accepted-unknown-config":

    1. 3. The simulated PHD sends a configuration event report, supporting a Dosage Sensor object.
    2. 4. The PHG under test must respond with:
    | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • a. APDU Type
      • – field-length = 2 bytes
      • – field-value = 0xE7 0x00 (PrstAdpu)
    • b. Invoke-id
      • – field- type = INT-U16
      • – field-length = 2 bytes
      • – field-value = it must be the same as the invoke-id of the simulated PHD's message.
    • c. Obj-Handle:
      • – field- type = HANDLE
      • – field-length = 2 bytes
      • – field-value = 0x00 0x00
    • d. Event-time:
      • – field- type = INT-U32
      • – field-length = 4 bytes
      • – field-value = 0xXX 0xXX
    • e. Event-type:
      • – field-length = 2 bytes
      • – field-value = MDC_NOTI_CONFIG
    • f. The following six bytes indicates:
      • – Event-replay-info.length (2 bytes)
      • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
      • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-006 | | | +| TP label | Water Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 13; M | | +| Test purpose | Check that:
    Continua PAN /Sensor-LAN Water Sensor client components shall implement the Water Sensor enumeration object. | | | +| Applicability | C_MAN_HUB_022 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports a Water Sensor object. | | | +| Test procedure | 1. The simulated PHD sends an Association Request to the PHG under test.
    2. The PHG under test responds with an Association Response, the field of interest is:
    a. Result
    • – field- type = INT-U16
    • – field-length = 2 bytes
    • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    IF the result of the Association Response was "accepted-unknown-config":

    1. 3. The simulated PHD sends a configuration event report, supporting a Water Sensor object.
    2. 4. The PHG under test must respond with:
      1. a. APDU Type
        • – field-length = 2 bytes
        • – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        • – field- type = HANDLE
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00
      4. d. Event-time:
        • – field- type = INT-U32
        • – field-length = 4 bytes
        • – field-value = 0xXX 0xXX
      5. e. Event-type:
        • – field-length = 2 bytes
        • – field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicates:
        • – Event-replay-info.length (2 bytes)
        • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
        • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-007 | | | +| TP label | Smoke Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 15; M | | +| Test purpose |

    Check that:

    Continua PAN/Sensor-LAN Smoke Sensor client components shall implement the Smoke Sensor enumeration object.

    | | | +| Applicability | C_MAN_HUB_023 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports a Smoke Sensor object. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. Result

    • – field- type = INT-U16
    • – field-length = 2 bytes
    • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    IF the result of the Association Response was "accepted-unknown-config":

    3. The simulated PHD sends a configuration event report, supporting a Smoke Sensor object.

    4. The PHG under test must respond with:

    a. APDU Type

    • – field-length = 2 bytes
    • – field-value = 0xE7 0x00 (PrstAdpu)

    b. Invoke-id

    • – field- type = INT-U16
    • – field-length = 2 bytes
    • – field-value = it must be the same as the invoke-id of the simulated PHD's message.

    c. Obj-Handle:

    • – field- type = HANDLE
    • – field-length = 2 bytes
    • – field-value = 0x00 0x00

    d. Event-time:

    • – field- type = INT-U32
    • – field-length = 4 bytes
    • – field-value = 0xXX 0xXX

    e. Event-type:

    • – field-length = 2 bytes
    • – field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicates:

    • – Event-replay-info.length (2 bytes)
    • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
    • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-008 | | | +| TP label | Property Exit Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 17; M | | +| Test purpose |

    Check that:

    Continua PAN/Sensor-LAN Property Exit Sensor client components shall implement the Property Exit Sensor enumeration object.

    | | | +| Applicability | C_MAN_HUB_024 AND (C_MAN_OXP_000) | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The simulated PHD supports a Property Exit Sensor object. | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        1. – field- type = INT-U16
        2. – field-length = 2 bytes
        3. – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    IF the result of the Association Response was "accepted-unknown-config":

    1. 3. The simulated PHD sends a configuration event report, supporting a Property Exit Sensor object.
    2. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. – field-length = 2 bytes
        2. – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        1. – field- type = INT-U16
        2. – field-length = 2 bytes
        3. – field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. – field- type = HANDLE
        2. – field-length = 2 bytes
        3. – field-value = 0x00 0x00
      4. d. Event-time:
        1. – field- type = INT-U32
        2. – field-length = 4 bytes
        3. – field-value = 0xXX 0xXX
      5. e. Event-type:
        1. – field-length = 2 bytes
        2. – field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicates:
        1. – Event-replay-info.length (2 bytes)
        2. – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
        3. – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|-----------------|------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-009 | | | +| TP label | Ambient Temperature Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 19; M | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    Continua PAN/Sensor-LAN Ambient Temperature Sensor client components shall implement the Temperature Sensor enumeration object. | +| Applicability | C_MAN_HUB_025 AND (C_MAN_OXP_000) | +| Other PICS | | +| Initial condition | The simulated PHD supports a Temperature Sensor object. | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        1. – field- type = INT-U16
        2. – field-length = 2 bytes
        3. – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    IF the result of the Association Response was "accepted-unknown-config":

    1. 3. The simulated PHD sends a configuration event report, supporting a Temperature Sensor object.
    2. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. – field-length = 2 bytes
        2. – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        1. – field- type = INT-U16
        2. – field-length = 2 bytes
        3. – field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. – field- type = HANDLE
        2. – field-length = 2 bytes
        3. – field-value = 0x00 0x00
      4. d. Event-time:
        1. – field- type = INT-U32
        2. – field-length = 4 bytes
        3. – field-value = 0xXX 0xXX
      5. e. Event-type:
        1. – field-length = 2 bytes
        2. – field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicates:
        1. – Event-replay-info.length (2 bytes)
        2. – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
        3. – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-010 | | | +| TP label | Usage Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 21; M | | +| Test purpose |

    Check that:

    Continua PAN/Sensor-LAN Usage Sensor client components shall implement the Usage Sensor enumeration object.

    | | | +| Applicability | C_MAN_HUB_026 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports a Usage Sensor object. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        1. – field- type = INT-U16
        2. – field-length = 2 bytes
        3. – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      IF the result of the Association Response was "accepted-unknown-config":

    3. 3. The simulated PHD sends a configuration event report, supporting a Usage Sensor object.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. – field-length = 2 bytes
        2. – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        1. – field- type = INT-U16
        2. – field-length = 2 bytes
        3. – field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. – field- type = HANDLE
        2. – field-length = 2 bytes
        3. – field-value = 0x00 0x00
      4. d. Event-time:
        1. – field- type = INT-U32
        2. – field-length = 4 bytes
        3. – field-value = 0xXX 0xXX
      5. e. Event-type:
        1. – field-length = 2 bytes
        2. – field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicates:
        1. – Event-replay-info.length (2 bytes)
        2. – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
        3. – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-011 | | | +| TP label | PERS Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 23; M | | +| Test purpose |

    Check that:

    Continua PAN/Sensor-LAN PERS Sensor client components shall implement the PERS Sensor enumeration object.

    | | | +| Applicability | C_MAN_HUB_027 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports a PERS Sensor object. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        1. – field- type = INT-U16
        2. – field-length = 2 bytes
        3. – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      IF the result of the Association Response was "accepted-unknown-config":

    3. 3. The simulated PHD sends a configuration event report, supporting a PERS Sensor object.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. – field-length = 2 bytes
        2. – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        1. – field- type = INT-U16
        2. – field-length = 2 bytes
        3. – field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. – field- type = HANDLE
        2. – field-length = 2 bytes
        3. – field-value = 0x00 0x00
      4. d. Event-time:
        1. – field- type = INT-U32
        2. – field-length = 4 bytes
        3. – field-value = 0xXX 0xXX
      5. e. Event-type:
        1. – field-length = 2 bytes
        2. – field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicates:
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • – Event-replay-info.length (2 bytes)
    • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
    • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-012 | | | +| TP label | CO Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 25; M | | +| Test purpose | Check that:

    Continua PAN/Sensor-LAN CO Sensor client components shall implement the CO Sensor enumeration object. | | | +| Applicability | C_MAN_HUB_028 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports a CO Sensor object. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)
      IF the result of the Association Response was "accepted-unknown-config":
    3. 3. The simulated PHD sends a configuration event report, supporting a CO Sensor object.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        • – field-length = 2 bytes
        • – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        • – field- type = HANDLE
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00
      4. d. Event-time:
        • – field- type = INT-U32
        • – field-length = 4 bytes
        • – field-value = 0xXX 0xXX
      5. e. Event-type:
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • – field-length = 2 bytes
    • – field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicates:

    • – Event-replay-info.length (2 bytes)
    • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
    • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUBDG/BV-013 | | | +| TP label | Gas Sensor PHG sub-specialization(profile) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Hub_DG 27; M | | +| Test purpose | Check that:
    Continua PAN/Sensor-LAN Gas Sensor client components shall implement the Gas Sensor enumeration object. | | | +| Applicability | C_MAN_HUB_029 AND (C_MAN_OXP_000) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD supports a Gas Sensor object. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test.
    2. 2. The PHG under test responds with an Association Response, the field of interest is:
      1. a. Result
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)
      IF the result of the Association Response was "accepted-unknown-config".
    3. 3. The simulated PHD sends a configuration event report, supporting a Gas Sensor object.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        • – field-length = 2 bytes
        • – field-value = 0xE7 0x00 (PrstAdpu)
      2. b. Invoke-id
        • – field- type = INT-U16
        • – field-length = 2 bytes
        • – field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        • – field- type = HANDLE
        • – field-length = 2 bytes
        • – field-value = 0x00 0x00
      4. d. Event-time:
        • – field- type = INT-U32
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • – field-length = 4 bytes
    • – field-value = 0xXX 0xXX

    e. Event-type:

    • – field-length = 2 bytes
    • – field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicates:

    • – Event-replay-info.length (2 bytes)
    • – ConfigReportRsp.config-report-id: it must be the same as the config-report-id of the simulated PHD's message
    • – ConfigReportRsp.config-result: accepted-config: 0x00 0x00
    | +| Pass/Fail criteria | The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config". | +| Notes | | + +## A.7 Subgroup 2.1.6 – ZigBee design guidelines (ZDG) + +| | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/LAN/PHG/TR/ZDG/BV-000 | | +| TP label | ZigBee QoS best.medium | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | ZQoS 1; M | +| Test purpose | Check that:
    Continua Sensor-LAN client components that implement the Continua best.medium QoS bin shall utilize ZigBee APS acknowledgements | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_063 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | +| Test procedure |
    1. 1. The simulated PHD sends an AARQ message.
    2. 2. Check that PHG utilizes APS-ack when it receives the AARQ message
    | | +| Pass/Fail criteria | Client shall use APS-ack when it receives an AARQ message. | | +| Notes | | | + +## A.8 Subgroup 2.1.8 – NFC design guidelines (NDG) + +| | | | +|--------------------------|---------------------------------------------------------------------------------|----------------------------| +| TP Id | TP/TAN/PHG/TR/NDG/BV-000 | | +| TP label | NFC_QoS | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | NFCQoS 1;M      NFCQoS 2;M | +| Test purpose | Check that:
    NFC PHDC transport does exchange all data on best.medium QoS bin | | +| Applicability | C_MAN_OXP_082 AND (C_MAN_OXP_000) | | +| Other PICS | C_MAN_OXP_001, C_MAN_OXP_006, C_MAN_OXP_085 | | +| Initial condition | The PHG under test is in the Disconnected state. | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |

    NOTE – This test case must be executed manually. NFC sniffer is needed to perform the verification required in this test case.

    1. 1. Enable the NFC transport of the simulated PHD.
    2. 2. Follow the steps listed in the product documentation to ask the PHG to initiate communication with service components.
    3. 3. Once the simulated PHD has been discovered, the simulated PHD issues an "Association Request" to the PHG under test.
    4. 4. The PHG under test issues an "Association response" on the best.medium QoS bin.
    5. 5. IF C_MAN_OXP_085 THEN:
      1. a. PHG under test sends a roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. Simulated PHD issues a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object
    6. 6. The PHG under test sends a Set Time message on the best.medium QoS bin.
    7. 7. The simulated PHD issues a Set Time response.
    8. 8. The simulated PHD issues a confirmed event report.
    9. 9. The PHG under test sends a confirmation on the on the best.medium QoS bin.
    10. 10. The simulated PHD issues an "Association Release Request".
    11. 11. The PHG under test sends an "Association Release Response" on the best.medium QoS bin.
    | +| Pass/Fail criteria | The PHG under test issues all responses on the best.medium QoS bin as defined by the steps above. | +| Notes | In step 6, if the PHG under test does not perform the Set-Time automatically a pop-up will appear asking for the operator to force the PHG to issue a Set-Time. | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/TAN/PHG/TR/NDG/BV-001 | | | +| TP label | Notification when data exchange is completed | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | NFCUser 2; O | | +| Test purpose |

    Check that:

    Continua TAN client component with appropriate UI capabilities should notify the user when data exchange is completed

    | | | +| Applicability | C_MAN_OXP_082 AND (C_MAN_OXP_000) | | | +| Other PICS | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085 | | | +| Initial condition | The PHG under test is in the Disconnected state. | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG.
    2. 2. Association Response
      1. a. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report. The PHG under test accepts that configuration and moves to Operating state.
        1. i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN it moves to Operating state.
        2. ii. IF C_MAN_OXP_085 THEN
          1. 1) PHG under test sends a roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
          2. 2) Simulated PHD issues a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    3) The PHG moves to Operating state.

    b. IF the PHG under test responds with an Association Response (accepted) THEN the PHG moves to Operating state.

    • i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.
    • ii. IF C_MAN_OXP_085 THEN
      • 1) PHG under test sends a roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      • 2) Simulated PHD issues a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      • 3) The PHG moves to Operating state.

    3. The simulated PHD sends a confirmed fixed event report with one measurement.

    4. The PHG under test confirms the event report.

    5. The simulated PHD sends a Release Request to the PHD under test with reason = normal(0).

    6. The PHG under test responds with a Release Response.

    7. The PHG under test notifies the user that the data Exchange is completed.

    | +| Pass/Fail criteria |
    • • In step 7, the PHG under test should notify the user when data exchange is completed.
    | +| Notes | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*. +- [b-ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI 300 406] ETSI ETS 300 406 (1995), *Methods for Testing and Specifications (MTS); Protocol and profile conformance testing specifications; Standardization methodology*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.13. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.11. + +- [b-TI] PHD testable items. Test Tool v7.0.2.0 – Excel sheet v1.10. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.845.11-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.845.11-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827609df9ad8667ae079f875841506349f063390 --- /dev/null +++ b/marked/H/T-REC-H.845.11-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d2afb537db9f3588854962a991eb1178220b2bbb8ff3cea6712979a53a864b +size 4107 diff --git a/marked/H/T-REC-H.845.11-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.11-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6b7b09f8c3c407fa39ed4f7943b1dc61cfb9289c --- /dev/null +++ b/marked/H/T-REC-H.845.11-201704-I_PDF-E/raw.md @@ -0,0 +1,1234 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.845.11** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 5K: Peak expiratory flow monitor** + +Recommendation ITU-T H.845.11 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.845.11 + +# Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5K: Peak expiratory flow monitor + +## Summary + +Recommendation ITU-T H.845.11 provides a test suite structure (TSS) and the test purposes (TP) for peak expiratory flow monitors in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.845.11 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5K: Device Specializations. Personal Health Device (Peak expiratory flow monitor) (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.845.11 | 2015-01-13 | 16 | 11.1002/1000/12271 | +| 2.0 | ITU-T H.845.11 | 2016-07-14 | 16 | 11.1002/1000/12948 | +| 3.0 | ITU-T H.845.11 | 2017-04-13 | 16 | 11.1002/1000/13228 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, IEEE 11073 device specialization, ITU-T H.810, peak expiratory flow monitor, personal area network, personal connected health devices, Personal Health Devices interface, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|----------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Test suite structure (TSS) ..... | 4 | +| 7 | Electronic attachment ..... | 7 | +| Annex A | Test purposes ..... | 8 | +| A.1 | TP definition conventions..... | 8 | +| A.2 | Subgroup 1.3.11: Peak expiratory flow monitor (PF) ..... | 10 | +| | Bibliography..... | 39 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is the transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5K: Device Specializations. Personal Health Device (Peak expiratory flow monitor) (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.2 | 2012-10-05 | Initial release for Test Tool DG2011. This is the same version as "TSS&TP_1.5_PAN-LAN_PART_5K_v1.2.doc" because new features included in [b-CDG 2011] do not affect the test procedures specified in this document. | +| 1.3 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_PAN-LAN_PART_5K_v1.2.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • • Max APDU size for GM, BCA and ECG
    | +| 1.4 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5K_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.5 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5K_v1.4.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row added
    | +| 1.5 | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_5K_v1.4.doc" because new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015] do not affect the test procedures specified in this document. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5K_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016] | + +## Recommendation ITU-T H.845.11 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5K: Peak expiratory flow monitor + +## 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 5, subpart 5K. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - **Part 5K: Peak expiratory flow monitor** + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [ISO/IEEE 11073-10421] ISO/IEEE 11073-10421-2010, *Health informatics – Personal health device communication – Part 10421: Device specialization – Peak expiatory flow monitor (peak flow)*. + +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|----------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | + +| | | +|-------|-------------------------------------------------------| +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +## 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 1.3.11 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + +- Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) +- Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) +- Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - **Subgroup 1.3.11: Peak flow (PF)** + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) +- Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 1.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 1.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +- Group 2: Personal Health Gateway (PHG) + - Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) + - Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) + - Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) + - Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + - Subgroup 2.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +## 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of this Annex can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case: + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth low energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test: + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing: + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 1.3.11: Peak expiratory flow monitor (PF) + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-000 | | | +| TP label | Get MDS Object for peak expiratory flow monitor specialization: Mandatory, Conditional and Optional Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | PF_MDSAttr1; C | PF_MDSAttr2; M | +| | | PF_MDSAttr4; M | PF_MDSAttr5; O | +| | | PF_GETServ1; M | PF_GETServ3; M | +| Test purpose | Check that:
    The PHD supports a Get command that requests all attributes
    [AND]
    The MDS Object contains the attributes specified for a peak expiratory flow monitor PHD. | | | +| Applicability | C_AG_OXP_170 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_181 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0 (to request for an MDS object) and the attribute-id-list set to 0 to indicate all attributes.
    2. 2. The PHD under test responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object:
      MDS Attributes:
      1. a. Conditional attribute System-Type shall not be present.
        • attribute-id = MDC_ATTR_SYS_TYPE
        • attribute-type = TYPE
        • attribute-value.length = 4 bytes
        • attribute-value =<not relevant >
      2. b. Mandatory attribute System-Type-Spec_List
        • attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST
        • attribute-type = TypeVerList
        • attribute-value.length = 4 bytes attribute-value = MDC_DEV_SPEC_PROFILE_PEFM, 1
      3. c. Mandatory attribute System-model
        • attribute-id = MDC_ATTR_ID_MODEL
        • attribute-type = SystemModel
        • attribute-value.length =<variable>
        • attribute-value ={Manufacturer, Model}
      4. d. Mandatory attribute Dev-Configuration-Id
        • attribute-id = MDC_ATTR_DEV_CONFIG_ID
        • attribute-type = ConfigId
        • attribute-value.length = 2 bytes
        • attribute-value =
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • – IF NOT C_AG_OXP_181 then attribute-value = 0x08 0x34
    • – ELSE attribute-value = < between 0x4000 and 0x7FFF>
    e. Optional attribute Power-Status
    • attribute-id = MDC_ATTR_POWER_STAT
    • attribute-type = PowerStatus (BITS-16)
    • attribute-value.length = 2 bytes
    • attribute-value =
      ON_MAINS (0x8000) or ON_BATTERY(0x4000)
    Only one of the following may be active:
    • ▪ chargingFull(8),
    • ▪ chargingTrickle(9),
    • ▪ chargingOff(10).
    • ▪ The rest of the bits must not be set.
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|--|--| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-001 | | | | | +| TP label | MDS Configuration objects events for peak expiratory flow monitor PHD | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | | +| | Testable items | PF_MDSEvent1; M | PF_GenNumObj1; O | | | +| | | PersBest1; M | FEV1S1;M | | | +| | | ReadStatus1;M | PF_ExtRules2; M | | | +| | | PEF1; M | | | | +| | | FEV6S1; O | | | | +| | | PF_ConfProc1;M | | | | +| Test purpose | Check that:
    A peak expiratory flow monitor PHD shall send the MDS-Configuration-Event using a Confirmed event report. The MDS-Configuration-Event shall include the event-info ConfigReport.
    [AND]
    Check objects supported by the PHD (standard /extended configuration) | | | | | +| Applicability | C_AG_OXP_170 AND C_AG_OXP_000 | | | | | +| Other PICS | C_AG_OXP_010, C_AG_OXP_181, C_AG_PF_001 | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with a result = accepted-unknown-config.
    3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG:
    1. a. APDU Type
      • field- type = PrstApdu
      • field-length =2 bytes
      • field-value =0xE7 0x00
    2. b. invoke-id
    | | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field- type = InvokeIDType
    • field-length =INT-U16
    • field- value=<Not relevant for this test>

    c. message

    • field- type = roiv-cmip-confirmed-event-report
    • field-length =two bytes
    • field- value=0x01 0x01 (EventReportArgumentSimple)

    d. obj-handle (EventReportArgumentSimple)

    • field- type = HANDLE
    • field-length =INT-U16

    e. event-time (EventReportArgumentSimple)

    • field- type = Relative Time
    • field-length =INT-U32
    • field-value =
      • • IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF

    f. event-type (EventReportArgumentSimple)

    • field- type = OID-Type
    • field-length =INT-U16
    • field- value=0x 0D 0x 1C (MDC_NOTI_CONFIG)

    g. config-report-id (ConfigReport)

    • field- type = ConfigId
    • field-length = INT-U16
    • field- value =
      • – IF NOT C_AG_OXP_181 then attribute-value = 0x08 0x34
      • – ELSE attribute-value = < between 0x4000 and 0x7FFF >

    h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject)). To check the objects that are supported by the PHD, Type Attribute will be checked in AttributeList.

    • field- type = OID-Type
    • field-length = INT-U16
    • field- value =
      • – Three simple numeric objects for PEF, Personal Best and FEV1 shall be present.
      • – One enumeration object, Reading status shall be present.
      • – IF NOT C_AG_OXP_181 and C_AG_PF_001 FEV6 shall be present ELSE FEV6 shall not be present.
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|-----------------|-------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-002 | | | +| TP label | MDS objects events Peak expiratory flow monitor | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable | PF_MDSEvent3; M | PF_MDSEvent4; M | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------|---------------------| +| | items | PF_MDSEvent6; M | PF_EventRepServ1; M | PF_EventRepServ2; M | +| | | PF_EventRepServ3; O | PF_OperProc4; M | PF_OperProc8; M | +| | | PF_OperProc9; O | | | +| Test purpose |

    Check that:

    The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed.

    [AND/OR]

    The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar.

    [AND]

    Event reports shall be used in confirmed mode.

    [AND]

    Agent-initiated mode shall be supported for measurement data transmission.

    [AND]

    A peak expiratory flow monitor PHD may support only single-person event reports

    [AND]

    A peak expiratory flow monitor PHD with standard configuration shall use the fixed format data update messages method for transmitting measurement data

    [AND]

    A peak expiratory flow monitor PHD with extended configuration may use either fixed or variable format data update messages for transmitting measurement data.

    | | | | +| Applicability | C_AG_OXP_170 AND C_AG_OXP_000 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189) | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_181, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD under test responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to the tested configuration. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to tested configuration is received.
    5. 5. Record the PHD configuration.
    6. 6. IF C_AG_OXP_293:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 it issues the Set-Time action command.
          • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    7. Take Measurements for every supported object in the PHD under test.

    8. Wait to receive every event report and check:

    • field- type = Event Report
    • field-length = 2 bytes
    • field- value=0x01 0x01 (EventReportArgumentSimple, confirmed). This field identifies the type of message sent by the PHD, for the confirmed event configuration, roiv-cmip-confirmed-event-report.
    | +| Pass/Fail criteria |
    • • Check that every received MDS Event report is one of the following Data APDU and that it is confirmed.
    • • For Standard Configuration (NOT C_AG_OXP_181): An MDS Event Report is sent by the PHD under test to report measurements for every object:
      • MDC_NOTI_SCAN_REPORT_FIXED
      • MDC_NOTI_SCAN_REPORT_MP_FIXED
    • • For Extended Configuration, an MDS Event Report is sent by the PHD under test to report measurements for every object:
      • MDC_NOTI_SCAN_REPORT_FIXED
      • MDC_NOTI_SCAN_REPORT_MP_FIXED
      • MDC_NOTI_SCAN_REPORT_VAR
      • MDC_NOTI_SCAN_REPORT_MP_VAR
    | +| Notes | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------|------------------------|----------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-003 | | | | +| TP label | PEF Object for Standard Configuration (0x0834) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | PEF2; M | PEF3; M | PEF4; R | +| | | PEF5; M | PEF6; R | PEF7; R | +| | | PEF8; R | PEF9; R | PEF10; R | +| | | PEF11; M | PEF12; M | PEF13; R | +| | | PEF14; O | PEF15; O | PEF16; M | +| | | PEF17; C | PEF18; C | PEF19; R | +| | | PEF20; C | PEF21; R | PEF22; R | +| | | PEF23; R | PEF24; R | PEF25; R | +| | | PEF26; R | PEF45; M | PF_ConfProc2; M | +| Test purpose | Check that:
    PEF Numeric Object contains the attributes specified for Standard Configuration (0x0834) | | | | +| Applicability | C_AG_OXP_170 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x0834. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to 0x0834 is received.
    5. 5. Once the PHD under test sends a standard configuration, check the PEF object.
    6. 6. The PEF object contents shall be:
      1. a. Mandatory attribute Handle
        1. attribute-id = MDC_ATTR_ID_HANDLE
        2. attribute-type = HANDLE
        3. attribute-value = 0x00 0x01
      2. b. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_SCADA,
          MDC_FLOW_AWAY_EXP_FORCED_PEAK
      3. c. Mandatory attribute Metric-Spec-Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall
        3. attribute-value.length = 2 bytes
        4. attribute-value = 0xD0 0x40
          • • Bit 0 (mss-avail-intermittent(0)) is set.
          • • Bit 1 (mss-avail-stored-data(1)) is set.
          • • Bit 3 (mss-msmt-aperiodic(3)) is set.
          • • Bit 9 (mss-acc-agent-initiated(9)) is set.
      4. d. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_X_L_PER_MIN
      5. e. Mandatory attribute Attribute-Value-Map
        1. attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP
        2. attribute-type = AttrValMap
        3. attribute-count = 2
        4. attribute-value = (MDC_ATTR_NU_VAL_OBS_SIMP,4
          MDC_ATTR_TIME_STAMP_ABS, 8)
    7. 7. Check that no other attributes are present in the initial configuration.
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | +|-----------------|---------------------------------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-004 | +| TP label | PEF Object for Extended Configuration | + +| | | | | | | +|--------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|--| +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | | +| | Testable items | PEF27; M | PEF28; R | PEF29; M | | +| | | PEF30; R | PEF31; R | PEF32; R | | +| | | PEF33; R | PEF34; R | PEF35; M | | +| | | PEF37; R | PEF38; R | PEF39; R | | +| | | PEF40; R | PEF41; R | PEF42; R | | +| | | PEF43; R | PEF44; R | | | +| Test purpose | | Check that:
    PEF Numeric Object contains the attributes specified for Extended Configuration | | | | +| Applicability | | C_AG_OXP_170 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | | +| Other PICS | | | | | | +| Initial condition | | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure | |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD under test responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to the tested extended configuration. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to the extended configuration is received.
    5. 5. Once the PHD under test sends the tested configuration, check the PEF object.
    6. 6. The PEF object contents shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_SCADA,
          MDC_FLOW_AWAY_EXP_FORCED_PEAK
      2. b. IF Not Recommended attribute Supplemental-Types
        1. attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES
        2. attribute-type = SupplementalTypeList
        3. attribute-value.length = <variable>Sequence of TYPE (TYPE.length= 4 bytes)
        4. attribute-value = <Not relevant for this test>
      3. c. Mandatory attribute Metric-Spec-Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall
        3. attribute-value.length = 2 bytes
        4. attribute-value = 0xD0 0x40
          • • Bit 0 (mss-avail-intermittent(0)) is set.
          • • Bit 1 (mss-avail-stored-data(1)) is set.
          • • Bit 3 (mss-msmt-aperiodic(3)) is set.
          • • Bit 9 (mss-acc-agent-initiated(9)) is set.
    | | | | + +- d. IF Not recommended attribute Metric-Structure-Small is present + - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL + - attribute-type = MetricStructureSmall + - attribute-length = 2 bytes + - attribute-value = +- e. IF Not recommended attribute Measurement-Status is present + - attribute-id = MDC\_ATTR\_MSMT\_STAT + - attribute-type = MeasurementStatus + - attribute-value.length = 2 bytes + - attribute-value = +- f. IF Not recommended attribute Metric-Id is present + - attribute-id = MDC\_ATTR\_ID\_PHYSIO + - attribute-type = OID-Type(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- g. IF Not Recommended attribute Metric-Id-List is present + - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS + - attribute-type = MetricIdList + - attribute-value = +- h. IF Not recommended attribute Metric-Id-Partition is present + - attribute-id = MDC\_ATTR\_METRIC\_ID\_PART + - attribute-type = NomPartition(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- i. Mandatory attribute Unit-Code + - attribute-id = MDC\_ATTR\_UNIT\_CODE + - attribute-type = OID-Type + - attribute-value.length = 2 bytes + - attribute-value = MDC\_DIM\_X\_L\_PER\_MIN +- j. IF Not recommended attribute Source-Handle-Reference is present + - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF + - attribute-type = HANDLE(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- k. IF Not recommended attribute Measure-Active-Period + - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE + - attribute-type = FLOAT-Type (INT-U32) + - attribute-value.length = 4 bytes + - attribute-value = +- l. IF Not recommended Compound-Simple-Nu-Observed-Value is present + - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP + - attribute-type = SimpleNuObsValueCmp + - attribute-value.length = + - attribute-value = + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    m. IF Not recommended attribute Basic-Nu-Observed-Value is present

    • attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC
    • attribute-type = BasicNuObsValue
    • attribute-value.length = 2bytes
    • attribute-value = <Not relevant for this test>

    n. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present

    • attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC
    • attribute-type = BasicNuObsValueCmp
    • attribute-value.length = <variable>
    • attribute-value = <Not relevant for this test>

    o. IF Not recommended attribute Nu-Observed-Value is present

    • attribute-id = MDC_ATTR_NU_VAL_OBS
    • attribute-type = NuObsValue
    • attribute-value.length = 10bytes
    • attribute-value = <Not relevant for this test>

    p. Not recommended attribute Compound-Nu-Observed-Value

    • attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP
    • attribute-type = NuObsValueCmp
    • attribute-value.length = <variable>
    • attribute-value = <Not relevant for this test>

    q. IF Not Recommended attribute Accuracy is present

    • attribute-id = MDC_ATTR_NU_ACCUR_MSMT
    • attribute-type = FLOAT-Type (INT-U32)
    • attribute-value.length = 4 bytes
    • attribute-value = <Not relevant for this test>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|-----------------|----------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-005 | | | +| TP label | Personal Best Object for Standard Configuration (0x0834) | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | PersBest2; M | PersBest3; M | +| | | PersBest5; M | PersBest6; R | +| | | PersBest8; R | PersBest9; R | +| | | PersBest11; M | PersBest12; M | +| | | PersBest14; O | PersBest15; O | +| | | PersBest17; R | PersBest18; C | +| | | PersBest20; C | PersBest21; R | +| | | | PersBest4; R | +| | | | PersBest7; R | +| | | | PersBest10; R | +| | | | PersBest13; R | +| | | | PersBest16; C | +| | | | PersBest19; R | +| | | | PersBest22; R | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|-----------------| +| | | PersBest23; R | PersBest24; R | PersBest25; R | +| | | PersBest26; R | PersBest40; M | PF_ConfProc2; M | +| Test purpose | Check that:
    Personal Best Numeric Object contains the attributes specified for Standard Configuration (0x0834) | | | | +| Applicability | C_AG_OXP_170 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x0834. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to 0x0834 is received.
    5. 5. Once the PHD under test sends a standard configuration, check the Personal Best object.
    6. 6. The Personal Best object contents shall be:
      1. a. Mandatory attribute Handle
        1. attribute-id = MDC_ATTR_ID_HANDLE
        2. attribute-type = HANDLE
        3. attribute-value = 0x00 0x02
      2. b. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_SCADA,
          MDC_FLOW_AWAY_EXP_FORCED_PEAK_PB
      3. c. Mandatory attribute Metric-Spec-Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall
        3. attribute-value.length = 2 bytes
        4. attribute-value = 0xC0 0x44
          1. • Bit 0 (mss-avail-intermittent(0)) is set.
          2. • Bit 1 (mss-avail-stored-data(1)) is set.
          3. • Bit 9 (mss-acc-agent-initiated(9)) is set.
          4. • Bit 13 (mss-cat-setting (13)) is set.
      4. d. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_X_L_PER_MIN
      5. e. Mandatory attribute Attribute-Value-Map
        1. attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP
        2. attribute-type = AttrValMap
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-count = 2
    • attribute-value = (MDC_ATTR_NU_VAL_OBS_SIMP,4
      MDC_ATTR_TIME_STAMP_ABS, 8)
    7. Check that no other attributes are present in the initial configuration. | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-006 | | | | +| TP label | Personal Best Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | PersBest27; M | PersBest28; R | PersBest29; M | +| | | PersBest30; R | PersBest31; R | PersBest32; R | +| | | PersBest33; R | PersBest34; R | PersBest35; M | +| | | PersBest37; R | PersBest38; R | PersBest39; R | +| Test purpose | Check that:
    Personal Best Numeric Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_170 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to the tested extended configuration. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to the extended configuration is received.
    5. 5. Once the PHD under test sends the tested configuration, check Personal Best object.
    6. 6. The Personal Best object contents shall be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        attribute-value = MDC_PART_SCADA,
        MDC_FLOW_AWAY_EXP_FORCED_PEAK_PB
      2. b. IF Not Recommended attribute Supplemental-Types
        • attribute-id = MDC_ATTR_SPPLEMENTAL_TYPES
        • attribute-type = SupplementalTypeList
        • attribute-value.length = <variable>Sequence of TYPE (TYPE.length= 4 bytes)
        • attribute-value = <Not relevant for this test>
    | | | | + +- c. Mandatory attribute Metric-Spec-Small +- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL + - attribute-type = MetricSpecSmall + - attribute-value.length = 2 bytes + - attribute-value = 0xC0 0x44 + - Bit 0 (mss-avail-intermittent(0)) is set. + - Bit 1 (mss-avail-stored-data(1)) is set. + - Bit 9 (mss-acc-agent-initiated(9)) is set. + - Bit 13 (mss-cat-setting (13)) is set. +- d. IF Not recommended attribute Metric-Structure-Small is present +- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL + - attribute-type = MetricStructureSmall + - attribute-length = 2 bytes + - attribute-value = +- e. IF Not recommended attribute Measurement-Status is present +- attribute-id = MDC\_ATTR\_MSMT\_STAT + - attribute-type = MeasurementStatus + - attribute-value.length = 2 bytes + - attribute-value = +- f. IF Not recommended attribute Metric-Id is present +- attribute-id = MDC\_ATTR\_ID\_PHYSIO + - attribute-type = OID-Type(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- g. IF Not Recommended attribute Metric-Id-List is present +- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS + - attribute-type = MetricIdList + - attribute-value = +- h. IF Not recommended attribute Metric-Id-Partition is present +- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART + - attribute-type = NomPartition(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- i. Mandatory recommended attribute Unit-Code +- attribute-id = MDC\_ATTR\_UNIT\_CODE + - attribute-type = OID-Type(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = MDC\_DIM\_X\_L\_PER\_MIN +- j. IF Not recommended attribute Source-Handle-Reference is present +- attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF + - attribute-type = HANDLE(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    k. IF Not recommended attribute Measure-Active-Period

    • attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE
    • attribute-type = FLOAT-Type (INT-U32)
    • attribute-value.length = 4 bytes
    • attribute-value = <Not relevant for this test>

    l. IF Not Recommended attribute Accuracy is present

    • attribute-id = MDC_ATTR_NU_ACCUR_MSMT
    • attribute-type = FLOAT-Type (INT-U32)
    • attribute-value.length = 4 bytes
    • attribute-value = <Not relevant for this test>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-007 | | | +| TP label | FEV1 for Standard Configuration (0x0834) | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | FEV1S2; M | FEV1S3; M | +| | | FEV1S5; M | FEV1S6; R | +| | | FEV1S8; R | FEV1S9; R | +| | | FEV1S11; M | FEV1S12; M | +| | | FEV1S14; O | FEV1S15; O | +| | | FEV1S17; C | FEV1S18; C | +| | | FEV1S20; C | FEV1S21; R | +| | | FEV1S23; R | FEV1S24; R | +| | | FEV1S26; R | FEV1S45; M | +| | | | PF_ConfProc2; M | +| Test purpose | Check that:
    FEV1 Numeric Object contains the attributes specified for Standard Configuration (0x0834) | | | +| Applicability | C_AG_OXP_170 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x0834. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to 0x0834 is received.
    5. 5. Once the PHD under test sends a standard configuration, check the FEV1 object.
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    6. The FEV1 contents shall be:

    a. Mandatory attribute Handle

    • attribute-id = MDC_ATTR_ID_HANDLE
    • attribute-type = HANDLE
    • attribute-value = 0x00 0x03

    b. Mandatory attribute Type

    • attribute-id = MDC_ATTR_ID_TYPE
    • attribute-type = TYPE
    • attribute-value = MDC_PART_SCADA MDC_VOL_AWAY_EXP_FORCED_1S

    c. Mandatory attribute Metric-Spec-Small

    • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
    • attribute-type = MetricSpecSmall
    • attribute-value.length = 2 bytes
    • attribute-value = 0xD0 0x40
      • • Bit 0 (mss-avail-intermittent(0)) is set.
      • • Bit 1 (mss-avail-stored-data(1)) is set.
      • • Bit 3 (mss-msmt-aperiodic(3)) is set.
      • • Bit 9 (mss-acc-agent-initiated(9)) is set.

    d. Mandatory recommended attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type(INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_X_L

    e. Mandatory attribute Attribute-Value-Map

    • attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP
    • attribute-type = AttrValMap
    • attribute-count = 2
    • attribute-value = (MDC_ATTR_NU_VAL_OBS_SIMP, 4
      MDC_ATTR_TIME_STAMP_ABS, 8)

    7. Check that no other attributes are present in the initial configuration.

    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------------|------------------------|------------|------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-008 | | | | +| TP label | FEV1 Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | FEV1S27; M | FEV1S28; R | FEV1S29; R | +| | | FEV1S30; M | FEV1S31; R | FEV1S32; R | +| | | FEV1S33; R | FEV1S34; R | FEV1S35; M | +| | | FEV1S37; R | FEV1S38; R | FEV1S39; R | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|------------| +| | | FEV1S40; R | FEV1S41; R | FEV1S42; R | +| | | FEV1S43; R | FEV1S44; R | | +| Test purpose | Check that:
    FEV1 Numeric Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_170 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to the tested extended configuration. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to the extended configuration.
    5. 5. Once the PHD under test sends the tested configuration, check the FEV1 object.
    6. 6. The FEV1 object contents shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_SCADA MDC_VOL_AWAY_EXP_FORCED_1S
      2. b. IF Not Recommended attribute Supplemental-Types
        1. attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES
        2. attribute-type = SupplementalTypeList
        3. attribute-value.length = <variable>Sequence of TYPE (TYPE.length= 4 bytes)
        4. attribute-value = <Not relevant for this test>
      3. c. Mandatory attribute Metric-Spec-Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall
        3. attribute-value.length = 2 bytes
        4. attribute-value = 0xD0 0x40
          • • Bit 0 (mss-avail-intermittent(0)) is set.
          • • Bit 1 (mss-avail-stored-data(1)) is set.
          • • Bit 3 (mss-msmt-aperiodic(3)) is set.
          • • Bit 9 (mss-acc-agent-initiated(9)) is set.
      4. d. IF Not recommended attribute Metric-Structure-Small is present
        1. attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL
        2. attribute-type = MetricStructureSmall
        3. attribute-length = 2 bytes
        4. attribute-value = <Not relevant for this test>
      5. e. IF Not recommended attribute Measurement-Status is present
        1. attribute-id = MDC_ATTR_MSMT_STAT
        2. attribute-type = MeasurementStatus
        3. attribute-value.length = 2 bytes
    | | | | + +- attribute-value = +- f. IF Not recommended attribute Metric-Id is present + - attribute-id = MDC\_ATTR\_ID\_PHYSIO + - attribute-type = OID-Type(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- g. IF Not Recommended attribute Metric-Id-List is present + - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS + - attribute-type = MetricIdList + - attribute-value = +- h. IF Not recommended attribute Metric-Id-Partition is present + - attribute-id = MDC\_ATTR\_METRIC\_ID\_PART + - attribute-type = NomPartition(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- i. Mandatory attribute Unit-Code + - attribute-id = MDC\_ATTR\_UNIT\_CODE + - attribute-type = OID-Type + - attribute-value.length = 2 bytes + - attribute-value = MDC\_DIM\_X\_L +- j. IF Not recommended attribute Source-Handle-Reference is present + - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF + - attribute-type = HANDLE(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- k. IF Not recommended attribute Measure-Active-Period + - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE + - attribute-type = FLOAT-Type (INT-U32) + - attribute-value.length = 4 bytes + - attribute-value = +- l. IF Not recommended Compound-Simple-Nu-Observed-Value is present + - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP + - attribute-type = SimpleNuObsValueCmp + - attribute-value.length = + - attribute-value = +- m. IF Not recommended attribute Basic-Nu-Observed-Value is present + - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS\_BASIC + - attribute-type = BasicNuObsValue + - attribute-value.length = 2bytes + - attribute-value = +- n. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present + - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_BASIC + - attribute-type = BasicNuObsValueCmp + - attribute-value.length = + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value = <Not relevant for this test>
    • o. IF Not recommended attribute Nu-Observed-Value is present
      • attribute-id = MDC_ATTR_NU_VAL_OBS
      • attribute-type = NuObsValue
      • attribute-value.length = 10bytes
      • attribute-value = <Not relevant for this test>
    • p. Not recommended attribute Compound-Nu-Observed-Value
      • attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP
      • attribute-type = NuObsValueCmp
      • attribute-value.length = <variable>
      • attribute-value = <Not relevant for this test>
    • q. IF Not Recommended attribute Accuracy is present
      • attribute-id = MDC_ATTR_NU_ACCUR_MSMT
      • attribute-type = FLOAT-Type (INT-U32)
      • attribute-value.length = 4 bytes
      • attribute-value = <Not relevant for this test>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-009 | | | | +| TP label | FEV6 Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | FEV6S2; M | FEV6S3; R | FEV6S4; R | +| | | FEV6S5; M | FEV6S6; R | FEV6S7; R | +| | | FEV6S8; R | FEV6S9; R | FEV6S10; M | +| | | FEV6S12; R | FEV6S14; R | FEV6S15; R | +| | | FEV6S16; R | FEV6S17; R | FEV6S18; R | +| | | FEV6S19; R | FEV6S20; R | | +| Test purpose | Check that:
    FEV6 Numeric Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_170 AND C_AG_OXP_181 AND C_AG_PF_001 AND C_AG_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to the tested extended configuration. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.
    | | | | + +Repeat this step until a Dev-config-Id equal to the extended configuration is received. + +5. Once the PHD under test sends the tested configuration, check the FEV6 object. + +6. The FEV6 object contents shall be: + +a. Mandatory attribute Type + +- attribute-id = MDC\_ATTR\_ID\_TYPE +- attribute-type = TYPE +- attribute-value = MDC\_PART\_SCADA | MDC\_VOL\_AWAY\_EXP\_FORCED\_6S + +b. IF Not Recommended attribute Supplemental-Types + +- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES +- attribute-type = SupplementalTypeList +- attribute-value.length = Sequence of TYPE (TYPE.length= 4 bytes) +- attribute-value = + +c. Mandatory attribute Metric-Spec-Small + +- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL +- attribute-type = MetricSpecSmall +- attribute-value.length = 2 bytes +- attribute-value = 0xD0 0x40 + - Bit 0 (mss-avail-intermittent(0)) is set. + - Bit 1 (mss-avail-stored-data(1)) is set. + - Bit 3 (mss-msmt-aperiodic(3)) is set. + - Bit 9 (mss-acc-agent-initiated(9)) is set. + +d. IF Not recommended attribute Metric-Structure-Small is present + +- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL +- attribute-type = MetricStructureSmall +- attribute-length = 2 bytes +- attribute-value = + +e. IF Not recommended attribute Measurement-Status is present + +- attribute-id = MDC\_ATTR\_MSMT\_STAT +- attribute-type = MeasurementStatus +- attribute-value.length = 2 bytes +- attribute-value = + +f. IF Not recommended attribute Metric-Id is present + +- attribute-id = MDC\_ATTR\_ID\_PHYSIO +- attribute-type = OID-Type(INT-U16) +- attribute-value.length = 2 bytes +- attribute-value = + +g. IF Not Recommended attribute Metric-Id-List is present + +- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS +- attribute-type = MetricIdList +- attribute-value = + +h. IF Not recommended attribute Metric-Id-Partition is present + +- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART +- attribute-type = NomPartition(INT-U16) +- attribute-value.length = 2 bytes + +- attribute-value = +- i. Mandatory attribute Unit-Code + - attribute-id = MDC\_ATTR\_UNIT\_CODE + - attribute-type = OID-Type + - attribute-value.length = 2 bytes + - attribute-value = MDC\_DIM\_X\_L +- j. IF Not recommended attribute Source-Handle-Reference is present + - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF + - attribute-type = HANDLE(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- k. IF Not recommended attribute Measure-Active-Period + - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE + - attribute-type = FLOAT-Type (INT-U32) + - attribute-value.length = 4 bytes + - attribute-value = +- l. IF Not recommended Compound-Simple-Nu-Observed-Value is present + - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP + - attribute-type = SimpleNuObsValueCmp + - attribute-value.length = + - attribute-value = +- m. IF Not recommended attribute Basic-Nu-Observed-Value is present + - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS\_BASIC + - attribute-type = BasicNuObsValue + - attribute-value.length = 2bytes + - attribute-value = +- n. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present + - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_BASIC + - attribute-type = BasicNuObsValueCmp + - attribute-value.length = + - attribute-value = +- o. IF Not recommended attribute Nu-Observed-Value is present + - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS + - attribute-type = NuObsValue + - attribute-value.length = 10bytes + - attribute-value = +- p. Not recommended attribute Compound-Nu-Observed-Value + - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP + - attribute-type = NuObsValueCmp + - attribute-value.length = + - attribute-value = +- q. IF Not Recommended attribute Accuracy is present + - attribute-id = MDC\_ATTR\_NU\_ACCUR\_MSMT + - attribute-type = FLOAT-Type (INT-U32) + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| | attribute-value.length = 4 bytes
    attribute-value = | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-010 | | | +| TP label | Reading status Object for Standard Configuration (0x0834) | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | ReadStatus2; M | ReadStatus3; M | +| | | ReadStatus5; M | ReadStatus6; R | +| | | ReadStatus8; R | ReadStatus9; R | +| | | ReadStatus11; R | ReadStatus12; M | +| | | ReadStatus14; O | ReadStatus15; O | +| | | ReadStatus17; R | ReadStatus18; C | +| | | ReadStatus20; R | ReadStatus21; M | +| | | ReadStatus23; R | ReadStatus24; R | +| | | PF_ConfProc2; M | ReadStatus41; M | +| Test purpose | Check that:

    Reading status Enumeration Object contains the attributes specified for Standard Configuration (0x0834) | | | +| Applicability | C_AG_OXP_170 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x0834. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to 0x0834 is received.
    5. 5. Once the PHD under test sends a standard configuration, check the Reading status object.
    6. 6. The Reading status object contents shall be:
      1. a. Mandatory attribute Handle attribute-id = MDC_ATTR_ID_HANDLE
        attribute-type = HANDLE
        attribute-value = 0x00 0x05
      2. b. Mandatory attribute Type attribute-id = MDC_ATTR_ID_TYPE
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = TYPE
    • attribute-value = MDC_PART_PHD_DM, MDC_PEF_READING_STATUS

    c. Mandatory attribute Metric-Spec-Small

    • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
    • attribute-type = MetricSpecSmall (BITS-16)
    • attribute-value = 0xD0 0x40
      • • Bit 0 (mss-avail-intermittent(0)) is set.
      • • Bit 1 (mss-avail-stored-data(1)) is set.
      • • Bit 3 (mss-msmt-aperiodic(3)) is set.
      • • Bit 9 (mss-acc-agent-initiated(9)) is set.

    d. Mandatory attribute Attribute-Value-Map

    • attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP
    • attribute-type = AttrValMap
    • attribute-count = 2
    • attribute-value= (MDC_ATTR_ENUM_VAL_OBS_BASIC_BIT_STRING, 2 MDC_ATTR_TIME_STAMP_ABS, 8)

    7. Check that no other attributes are present in the initial configuration.

    8. IF C_AG_OXP_293:

    • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    • c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    9. Take a measurement with the PHD.

    10. Wait for the PHD to send an event report and check:

    • a. Mandatory attribute Enum-Observed-Value-Basic-Bit-Str
      • attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_OID
      • attribute-type = OID-Type
      • attribute-value.length = 2 bytes
      • attribute-value= One of the following bits may be active:
        • • pefm-read-stat-post-medication(0)
        • • pefm-read-stat-cough(1)
        • • pefm-read-stat-short-effort(2)
        • • pefm-read-stat-long-time-to-peak(3)
        • • The rest of the bits must not be set
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-011 | | | +| TP label | Reading status Object for Extended Configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | ReadStatus25; M | ReadStatus26; R | +| | | ReadStatus28; M | ReadStatus29; R | +| | | ReadStatus31; R | ReadStatus32; R | +| | | ReadStatus34; R | ReadStatus35; O | +| | | ReadStatus37; M | ReadStatus38; R | +| | | ReadStatus40; R | ReadStatus41; M | +| Test purpose | Check that:
    Reading status Enumeration Object contains the attributes specified for Extended Configuration | | | +| Applicability | C_AG_OXP_170 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to extended configuration. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to tested extended configuration is received.
    5. 5. Once the PHD under test sends the tested configuration, check the Reading status object.
    6. 6. The Reading status object contents shall be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_DM, MDC_PEF_READING_STATUS
      2. b. IF Not Recommended attribute Supplemental-Types
        • attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES
        • attribute-type = SupplementalTypeList
        • attribute-value.length = <variable>Sequence of TYPE (TYPE.length= 4 bytes)
        • attribute-value = <Not relevant for this test>
      3. c. Mandatory attribute Metric-Spec-Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value =0xD0 0x40
          • • Bit 0 (mss-avail-intermittent(0)) is set.
          • • Bit 1 (mss-avail-stored-data(1)) is set.
          • • Bit 3 (mss-msmt-aperiodic(3)) is set.
    | | | + +- Bit 9 (mss-acc-agent-initiated(9)) is set. + +- d. IF Not recommended attribute Metric-Structure-Small is present + - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL + - attribute-type = MetricStructureSmall + - attribute-length = 2 bytes + - attribute-value = +- e. IF Not recommended attribute Measurement-Status is present + - attribute-id = MDC\_ATTR\_MSMT\_STAT + - attribute-type = MeasurementStatus + - attribute-value.length = 2 bytes + - attribute-value = +- f. IF Not recommended attribute Metric-Id is present + - attribute-id = MDC\_ATTR\_ID\_PHYSIO + - attribute-type = OID-Type(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- f. IF Not Recommended attribute Metric-Id-List is present + - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS + - attribute-type = MetricIdList + - attribute-value = +- g. IF Not recommended attribute Metric-Id-Partition is present + - attribute-id = MDC\_ATTR\_METRIC\_ID\_PART + - attribute-type = NomPartition(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- h. IF Not recommended attribute Unit-Code is present + - attribute-id = MDC\_ATTR\_UNIT\_CODE + - attribute-type = OID-Type(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- i. IF Not recommended attribute Source-Handle-Reference is present + - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF + - attribute-type = HANDLE(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- j. IF Optional attribute Enum-Observed-Value-Simple-OID is present + - attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_OID + - attribute-type = OID-Type (INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = +- k. IF Not Recommended attribute Enum-Observed-Value-Simple-Bit-Str is present + - attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_BIT\_STR + - attribute-type = BITS-32 + - attribute-value.length = BITS-32 + +- attribute-value= + - l. Mandatory attribute Enum-Observed-Value-Basic-Bit-Str is present + - attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR + - attribute-type = BITS-16 + - attribute-value.length = 2 bytes + - attribute-value = One of the following bits may be active: + - pefm-read-stat-post-medication(0) + - pefm-read-stat-cough(1) + - pefm-read-stat-short-effort(2) + - pefm-read-stat-long-time-to-peak(3) + - The rest of the bits must not be set + - m. IF Not Recommended attribute Enum-Observed-Value-Simple-Str is present + - attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_STR + - attribute-type = EnumPrintableString + - attribute-value.length = + - attribute-value = + - n. IF Not Recommended attribute Enum-Observed-Value is present + - attribute-id= MDC\_ATTR\_VAL\_ENUM\_OBS + - attribute-type = EnumObsValue + - attribute-value.length = + - attribute-value = + - o. IF Not recommended attribute Enum-Observed-Value-Partition is present + - attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_PART + - attribute-type = NomPartition (INT-U16) + - attribute-value.length=2 bytes + - attribute-value = +7. IF C\_AG\_OXP\_293: +- a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes. + - b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object. + - c. IF the mds-time-mgr-set-time bit is set: + - The PHG moves to Configuring/Sending Set Time substate and: + - IF C\_AG\_OXP\_009 it issues the Set-Time action command. + - IF C\_AG\_OXP\_014 it issues the Set-Base-Offset-Time action command. + - Once its internal time setting operation is completed, the PHD responds to the PHG. +8. Take a measurement with the PHD +9. Wait for the PHD to send an event report and check: +- a. Mandatory attribute Enum-Observed-Value-Basic-Bit-Str + - attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR + - attribute-type = OID-Type + - attribute-value.length = 2 bytes + - attribute-value= One of the following bits may be active: + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • pefm-read-stat-post-medication(0)
    • • pefm-read-stat-cough(1)
    • • pefm-read-stat-short-effort(2)
    • • pefm-read-stat-long-time-to-peak(3)
    • • The rest of the bits must not be set
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|------------------| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-012 | | | | +| TP label | Association Peak expiratory flow monitor PHD | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | PF_AssocReq1; M | PF_AssocReq2; M | PF_AssocReq3; M | +| | | PF_AssocReq4; M | PF_AssocReq5; M | PF_AssocReq6; M | +| | | PF_AssocReq7; M | PF_AssocReq8; M | PF_AssocReq9; M | +| | | PF_AssocReq10; M | PF_AssocReq11; M | PF_AssocReq12; M | +| | | PF_MDSMethod4; M | | | +| Test purpose | Check that:
    During the association procedure, Peak expiratory flow monitor PHD sends the correct association request to the simulated PHG | | | | +| Applicability | C_AG_OXP_170 AND C_AG_OXP_000 | | | | +| Other PICS | C_AG_OXP_002, C_AG_OXP_017 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure | 1. The PHD sends a message to associate to the simulated PHG, the expected fields sent by the PHD are:

    a. APDU Type
    field- type = AarqApdu
    field-length =2 bytes
    field-value =0xE2 0x00.
    b. assoc-version
    field- type = AssociationVersion
    field-length =BITS-32
    field- value=0x80 0x00 0x00 0x00
    c. data-proto-id
    field- type = DataProtoId(INT-U16)
    field-length =2 bytes
    field- value=0x50 0x79 (20601)
    d. protocol-version
    field- type = Protocol Version | | | | + +- field-length = 4 bytes +- field- value=0x80 0x00 0x00 0x00 + +#### e. encoding rules + +- field- type = EncodingRules +- field-length = 2 bytes +- field- value= + - Bit 0 must be set (support MDER) + - Bits 1 and 2 may be set + - The rest of the bits must be 0 + +#### f. nomenclature version + +- field- type = NomenclatureVersion +- field-length = 4 bytes +- field- value=0x80 0x00 0x00 0x00 +- This value indicates version1 is supported (nom-version1(0) is set). + +#### g. functional-units + +- field- type = FunctionalUnits +- field-length = 4 bytes +- field-value = + - Bit 0 must no be set, only bit 1 or 2 may be set to 1. + +#### h. System type + +- field- type = SystemType +- field-length = 4 bytes +- field- value = 0x00 0x80 0x00 0x00 (sys-type-agent) + +#### i. System-Id + +- field- type = OCTET STRING +- field-length = 8 bytes +- field- value = 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX (octet string length = 8 | UI-64 manufacturer and device ) +- This value will be the System Id attribute of the MDS object and the received value will be compared with the value defined in PIXIT I\_AG\_OXP\_001 and I\_AG\_OXP\_002. + +#### j. dev-config-id + +- field- type = ConfigId(INT-U16) +- field-length = 2 bytes +- field- value = + - <0x0834> for standard configuration + - for extended configuration. + +#### k. data-req-mode-flags (DataReqModeCapab) + +- field- type = DataReqModeFlags +- field-length = 2 bytes +- If PHD supports only Peak expiratory flow monitor specialization → Bit 15 is set (data-req-supp-init-agent(15)) + +#### l. data-req-init-agent-count (DataReqModeCapab) + +- field- type = INT-U8 +- field-length = 2 bytes + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | field.value = 0x01
    m. data-req-init-manager-count (DataReqModeCapab)
    • field- type = INT-U8
    • field-length = 2 bytes
    • field.value = 0x00
    | +| Pass/Fail criteria | All checked attributes have proper values. | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-013 | | | +| TP label | Set Time Peak expiratory flow monitor PHD | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | PF_MDSMethod2; C | | +| Test purpose | Check that:
    If the PHD supports the Absolute-Time-Stamp attribute, this method (Set Time) shall be implemented | | | +| Applicability | C_AG_OXP_170 AND C_AG_OXP_000 AND C_AG_OXP_009 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. The simulated PHG sends a SET action:
    • CHOICE = SetTimeInvoke
    • action-type = MDC_ACT_SET_TIME
    • the action-info-args are SetTimeInvoke
      • ▪ date-time = <century, year ≤ 99 month ≤ 12 day ≤ 31 hour ≤ 24 minute ≤ 60 s ≤ 60 sec-fractions ≤ 100>
      • ▪ accuracy = 0
    2. The PHD under test response shall be a rors-cmip-confirmed-action:
    • action-type = MDC_ACT_SET_TIME
    • action-info-args shall be empty.
    | | | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | | | +| Notes | | | | + +| | | | | +|-----------------|-----------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/PF/BV-014 | | | +| TP label | Operating State. PHG to PHD Maximum APDU Size | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 3; M | | +| | Spec | [ISO/IEEE 11073-10421] | | + +| | Testable items | PF_ComModel1;M | PF_ComModel2;M | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------|--| +| Test purpose | Check that:
    The total size of the response do not exceed of the maximum APDU size established by the specialization
    [AND]
    A PHD according to this definition shall be capable of receiving an APDU up to the size of at least Nrx. For this standard it is Nrx = 224 octets | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_170 | | | | +| Other PICS | C_AG_OXP_041, C_AG_OXP_100 | | | | +| Initial condition | The simulated PHG and the PHD are in the Operating state. | | | | +| Test procedure | 1. The simulated PHG issues "Remote Operation Invoke Get" command with:
    a. Obj-handle set to 0 (to request for MDS object)
    b. attribute-id-list.count = 103
    c. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 34 times followed by an additional MDC_ATTR_ID_MODEL
    2. Check the response of the PHD.
    3. The simulated PHG issues a "Remote Operation Invoke Get" command with the handle set to 0 (to request for an MDS object) and an empty attribute-id-list to indicate all attributes.
    4. Check the response of the PHD. | | | | +| Pass/Fail criteria |
    • • In step 2, the PHD under test may respond with a rors-cmip-get listing all the requested attributes, or with a roer message. If PICS C_AG_OXP_100 = TRUE and the PHD does not respond with a rors-cmip-get message, it responds with a roer message or rorj (resource-limitation) message, a WARNING will appear.
    • □ If the response is a get response, the total size of the response cannot exceed the sum of the APDU sizes of the supported specializations (limited to an absolute limit of 64512 octets):
      • ▪ Pulse oximeter -> 9216 octets
      • ▪ Weighing scales -> 896 octets
      • ▪ Glucose meter -> 5120 octets or 64512 octets if the PHD supports PM-Store
      • ▪ Blood pressure -> 896 octets
      • ▪ Thermometer -> 896 octets
      • ▪ Independent activity hub -> 5120 octets
      • ▪ Cardiovascular -> 64512 octets or 6624 octets if the PHD under test only supports Step Counter Profile
      • ▪ Strength -> 64512 octets:
      • ▪ Adherence monitor -> 1024 octets
      • ▪ Peak flow -> 2030 octets
      • ▪ Body composition analyser -> 7730 octets
      • ▪ Basic ECG/Simple ECG -> 7168 octets or 64512 octets if the PHD supports PM-Store
      • ▪ Basic ECG/Heart rate -> 1280 octets or 64512 octets if the PHD supports PM-Store
      • ▪ International normalized ratio -> 896 octets or 64512 if the PHD supports PM-Store
    | | | | + +| | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • In the case where it responds with a roer, the reason must not be protocol-violation (23).
    • • In step 4, the PHD must respond with a rors-cmip-get message.
    | +| Notes | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. +- [b-PHD PICS & PIXIT] Personal Health Device DG2016 PICS and PIXIT excel sheet v1.11. + +- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9. + +- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8. + +- [b-TCRL] Test Case Reference List\_DG2016\_v1.11. + + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.845.16-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.845.16-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71ed3c0020d190a2d540306cfa27958ba9631e0e --- /dev/null +++ b/marked/H/T-REC-H.845.16-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa0958fa01dbc1a49b82df2d67f8f7fe3d8c908be26a9aa58bbd633a65d02c76 +size 3952 diff --git a/marked/H/T-REC-H.845.16-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.16-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ffdae2bb283db59188fb351e3a886a3cb51450aa --- /dev/null +++ b/marked/H/T-REC-H.845.16-201704-I_PDF-E/raw.md @@ -0,0 +1,1276 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.845.16** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface Part +5P: Continuous glucose monitor** + +Recommendation ITU-T H.845.16 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.845.16 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5P: Continuous glucose monitor + +## Summary + +Recommendation ITU-T H.845.16 provides a test suite structure (TSS) and the test purposes (TP) for the continuous glucose monitor in the Personal Health Device (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.845.16 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface, Part 5P: Device Specializations. Personal Health Device, Continuous Glucose Monitor (CGM), Version 1.1 (2017-03-14). + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.845.16 | 2017-04-13 | 16 | 11.1002/1000/13235 | +| 1.1 | ITU-T H.845.16 (2017) Cor. 1 | 2017-11-29 | 16 | 11.1002/1000/13426 | + +## Keywords + +Conformance testing, Continua Design Guidelines, continuous glucose monitor, e-health, ITU-T H.810, IEEE 11073 device specialization, Personal Health Devices interface, personal area network, personal connected health devices, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|---------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Test suite structure (TSS) ..... | 5 | +| 7 | Electronic attachment ..... | 7 | +| Annex A | Test purposes ..... | 8 | +| A.1 | TP definition conventions..... | 8 | +| A.2 | Subgroup 1.3.16: Continuous glucose monitor (CGM) ..... | 10 | +| | Bibliography..... | 46 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is the transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface, Part 5P: Device Specializations. Personal Health Device, (Continuous Glucose Monitor -CGM-), Version 1.1 (2017-03-14) that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2016-09-20 | Initial release for Test Tool DG2016 based on the requirements in [ITU-T H.810 (2016)]/[b-CDG 2016]. | +| 1.1 | 2017-03-14 | This uses "TSS&TP_DG2016_PHD_PART_5P_v1.0.doc" as a baseline and adds new features included in Continua DG 2016 + Errata and it adds some updates according to the maintenance 2016 activity. | + +## Recommendation ITU-T H.845.16 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5P: Continuous glucose monitor + +## 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface has been divided into the parts specified below. This Recommendation covers Part 5, subpart 5P. + +- Part 1: Optimized Exchange Protocol. Personal Health Device +- Part 2: Optimized Exchange Protocol. Personal Health Gateway +- Part 3: Continua Design Guidelines. Personal Health Device +- Part 4: Continua Design Guidelines. Personal Health Gateway +- Part 5: Device Specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - **Part 5P: Continuous glucose monitor (CGM)** +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [ITU-T H.811] Recommendation ITU-T H.811 (2016), *Interoperability design guidelines for personal health systems: TAN/PAN/LAN interface*. +- [ITU-T H.812] Recommendation ITU-T H.812 (2016), *Interoperability design guidelines for personal health systems: WAN interface*. +- [ITU-T H.812.1] Recommendation ITU-T H.812.1 (2016), *Interoperability design guidelines for personal health systems: WAN interface: Observation upload*. +- [ITU-T H.812.2] Recommendation ITU-T H.812.2 (2016), *Interoperability design guidelines for personal health systems: WAN interface: Questionnaires*. +- [ITU-T H.812.3] Recommendation ITU-T H.812.3 (2016), *Interoperability design guidelines for personal health systems: WAN interface: Capability exchange*. +- [ITU-T H.812.4] Recommendation ITU-T H.812.4 (2016), *Interoperability design guidelines for personal health systems: WAN interface: Authenticated persistent session*. +- [ITU-T H.813] Recommendation ITU-T H.813 (2016), *Interoperability design guidelines for personal health systems: HRN interface*. +- [ISO/IEEE 11073-10425] ISO/IEEE 11073-10425:2016, *Health informatics – Personal health device communication – Part 10425: Device specialization – Continuous glucose monitor (CGM)*. + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol, including ISO/IEEE 11073-20601:2016/Cor.1:2016*. + with + + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### **3.2 Terms defined in this Recommendation** + +None. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCT | Protocol Conformance Testing | +| PCO | Point of Control and Observation | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation eXtra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +## 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this document are to be interpreted as in [ETSI SR 001 262] + +- SHALL is equivalent to: MUST; or it is required to. +- SHALL NOT is equivalent to: MUST NOT or it is not allowed +- SHOULD is equivalent to: it is recommended to +- SHOULD NOT is equivalent to: it is not recommended to +- MAY is equivalent to: is permitted +- MAY NOT is equivalent to: it is not required that + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Generic reference to the ITU-T H.810 series (listed in clause 2) is made through the label [ITU-T H.810 series. + +Reference is made in the ITU-T H.820-H.850-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|---------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata. | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 1.3.16 (shown in bold): + +The Test Purposes (TP) has been divided in two main groups: + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + +- Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - **Subgroup 1.3.16: Continuous glucose monitor (CGM)** +- Group 1.4: Personal Health Device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 1.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 1.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +###### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) + +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose Meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal Health Device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 2.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +## 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) - Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth Low Energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases + - : This identifies a subgroup of test cases + - : This identifies the type of testing + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 + +### Subgroup 1.3.16: Continuous glucose monitor (CGM) + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-000_A | | | +| TP label | Get MDS Object for Continuous Glucose Monitor specialization: Mandatory, Conditional and Optional Attributes. | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | MDSAttrCGM 3; M | MDSAttrCGM 4; M | +| | | MDSAttrCGM 7; M | MDSAttrCGM 12; R | +| | | MDSAttrCGM 16; R | MDSAttrCGM 17; R | +| Test purpose | Check that:
    The MDS Object contains the attributes specified for a Continuous Glucose Monitor agent | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 | | | +| Other PICS | C_AG_OXP_181 | | | +| Initial condition | The simulated Personal Health Gateway (PHG) and the Personal Health Device (PHD) under test are in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHG issues "roiv-cmip-get" command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. 2. The PHD responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object:
      MDS Attributes:
      1. a. Attribute System-Type must not be present.
      2. b. Mandatory attribute System-Type-Spec_List
        1. attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST
        2. attribute-type = TypeVerList
        3. attribute-value.length = 4 bytes for each configuration supported
        4. attribute-value = { MDC_DEV_SPEC_PROFILE_CGM, 1} must be found in the list
      3. c. Mandatory attribute System-model
        1. attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)
        2. attribute-type = SystemModel
        3. attribute-value.length = <Variable>
        4. attribute-value =
          • • Manufacturer = Check against PIXIT I_AG_OXP_003
          • • Model = Check against PIXIT I_AG_OXP_004
      4. d. Mandatory attribute Dev-Configuration-Id
        1. attribute-id = MDC_ATTR_DEV_CONFIG_ID
        2. attribute-type = ConfigId
        3. attribute-value.length = 2 bytes
        4. attribute-value =
          • • IF NOT C_AG_OXP_181 then attribute-value = 0x 09C4
          • • ELSE attribute-value = < between 0x4000 and 0x7FFF>
      5. e. If recommended attribute Base-Offset-Time is present
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id = MDC_ATTR_TIME_BO (0x0A 0x81)
    • attribute-type = BaseOffsetTime
    • attribute-value.length = 8 bytes
    • attribute-value = <not relevant>

    f. If recommended attribute Date-and-Time-Adjustment is present

    • attribute-id = MDC_ATTR_TIME_ABS_ADJUST (0x0A 0x62)
    • attribute-type = AbsoluteTimeAdjust
    • attribute-value.length = 6 bytes
    • attribute-value = <not relevant>

    g. If recommended attribute Power-Status is present

    • attribute-id = MDC_ATTR_POWER_STAT
    • attribute-type = PowerStatus (BITS-16)
    • attribute-value.length = 2 bytes
    • attribute-value =
      • • ON_BATTERY(0x4000)
      • • ON_MAINS (0x8000)

    h. If recommended attribute Battery-Level is present

    • attribute-id = MDC_ATTR_VAL_BATT_CHARGE (0x09 0x9C)
    • attribute-type = INT-U16
    • attribute-value.length = 2 bytes
    • attribute-value = <not relevant>

    i. If recommended attribute Remain-Battery-Time is present

    • attribute-id = MDC_ATTR_TIME_BATT_REMAIN (0x09 0x88)
    • attribute-type = BatMeasure
    • attribute-value.length = 6 bytes
    • attribute-value = <not relevant>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-000_B | | | +| TP label | MDS Configuration objects events for Continuous Glucose Monitor specialization. | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | MDSEventsCGM 1; M | | +| Test purpose | Check that:
    A Continuous Glucose Monitor agent shall send the [MDS-Configuration-Event] using a [Confirmed] event report.
    The [MDS-Configuration-Event] shall include the event-info [ConfigReport] | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 | | | +| Other PICS | C_AG_OXP_010, C_AG_OXP_181 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a “Remote Operation Invoke Confirmed Event Report” message with an MDC_NOTI_CONFIG event to send its configuration to the PHG:
      1. a. APDU Type
        1. field- type = PrstApdu
        2. field-length =2 bytes
        3. field-value =0xE7 0x00
      2. b. invoke-id
        1. field- type = InvokeIDType
        2. field-length =INT-U16
        3. field- value =<Not relevant for this test>
      3. c. message
        1. field- type = roiv-cmip-confirmed-event-report
        2. field-length =two bytes
        3. field- value =0x01 0x01 (EventReportArgumentSimple)
      4. d. obj-handle (EventReportArgumentSimple)
        1. field- type = HANDLE
        2. field-length =INT-U16
      5. e. event-time (EventReportArgumentSimple)
        1. field- type = Relative Time
        2. field-length =INT-U32
        3. field-value =
          • • IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF
      6. f. event-type (EventReportArgumentSimple)
        1. field- type = OID-Type
        2. field-length =INT-U16
        3. field- value=0x0D 0x1C (MDC_NOTI_CONFIG)
      7. g. config-report-id (ConfigReport)
        1. field- type = ConfigId
        2. field-length = INT-U16
        3. field value = <It matches the tested configuration>
          • • IF NOT C_AG_OXP_181 THEN attribute-value = 0x09C4 (2500)
          • • ELSE attribute-value = <between 0x40 0x00 and 0x7F 0xFF > for extended configuration.
      8. h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject))
        1. field- type = OID-Type
        2. field-length = INT-U16
        3. field- value = At least one MDC_MOC_VMO_METRIC_NU
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--------------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-000_C | | | | +| TP label | MDS objects events for Continuous Glucose Monitor specialization. | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | MDSEventsCGM 3; M | MDSEventsCGM 4; M | MDSEventsCGM 5; M | +| | | MDSEventsCGM 6; M | MDSEventsCGM 7; M | MDSEventsCGM 8; M | +| | | MDSEventsCGM 9; M | MDSEventsCGM 10; M | ObjAccServCGM 1; M | +| | | ObjAccServCGM 2; M | | | +| Test purpose |

    Check that:

    MDS Event reports shall be used in confirmed mode

    [AND]

    Agent-initiated mode shall be supported for measurement data transmission

    [AND]

    A Continuous Glucose Monitor PHD shall send the [MDS-Dynamic-Data-Update-Fixed] using a [Confirmed] event report. The [MDS-Dynamic-Data-Update-Fixed] shall include the event-info [ScanReportInfoFixed]

    [OR]

    A Continuous Glucose Monitor PHD shall send the [MDS-Dynamic-Data-Update-Var] using a [Confirmed] event report. The [MDS-Dynamic-Data-Update-Var] shall include the event-info [ScanReportInfoVar]

    [OR]

    A Continuous Glucose Monitor PHD shall send the [MDS-Dynamic-Data-Update-MP-Fixed] using a [Confirmed] event report. The [MDS-Dynamic-Data-Update-MP-Fixed] shall include the event-info [ScanReportInfoMPFixed]

    [OR]

    A Continuous Glucose Monitor PHD shall send the [MDS-Dynamic-Data-Update-MP-Var] using a [Confirmed] event report. The [MDS-Dynamic-Data-Update-MP-Var] shall include the event-info [ScanReportInfoMPVar]

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189) | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure |
    1. 1. Take Measurements for every supported Object in the PHD under test.
    2. 2. Wait to receive every event report and check:
      1. a. APDU Type
        • field- type = Event Report
        • field-length = 2 bytes
        • field- value=0x01 0x01 (EventReportArgumentSimple, confirmed)

        This field identifies the type of message sent by the PHD, for the confirmed event configuration, roiv-cmip-confirmed-event-report.

    | | | | +| Pass/Fail criteria |

    Check that every received report is one of the following confirmed Data APDU

    • • MDC_NOTI_SCAN_REPORT_FIXED
    • • MDC_NOTI_SCAN_REPORT_MP_FIXED
    • • MDC_NOTI_SCAN_REPORT_VAR
    | | | | + +| | | +|--------------|-------------------------------------------------------------------------------| +| |
    • MDC_NOTI_SCAN_REPORT_MP_VAR
    | +| Notes | | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|------------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-001 | | | | +| TP label | Objects for Continuous Glucose Monitor specialization - Standard Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | Glucose 1; M | SensCal 2; M | SensRun 2; M | +| | | GluSampInt 2; M | GluTrend 2; M | PHighLow 2; M | +| | | DevHypoHyper 2; M | GluRateChange 2; M | PHDDMStatus 2; M | +| | | CGMStatus 2; M | | | +| Test purpose |

    Check that:

    The Glucose Numeric object with Type {MDC_PART_SCADA MDC_CONC_GLU_ISF} is supported by a Continuous Glucose Monitor PHD with Standard Configuration 2500 (0x09C4).

    [AND]

    No more objects are supported by a Continuous Glucose Monitor (CGM) PHD with Standard Configuration 2500 (0x09C4).

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND (NOT C_AG_OXP_181) | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a “Remote Operation Invoke Confirmed Event Report” message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x09C4 (2500), if it is not, PHG responds with a “unsupported-config” and waits for a new configuration.
    5. 5. Once the PHD under test sends a standard configuration, Check that:
      Attribute-List:
      1. a. attribute-value (ConfigReport → ConfigObjectList (ConfigObject) → Attribute List), this value depends on the attribute Type. Values to be checked are:
        • The Glucose numeric object is present once → MDC_PART_SCADA (0x00 0x02), MDC_CONC_GLU_ISF (0x71 0xD4)
    | | | | +| Pass/Fail criteria | All checked values are as specified in the test procedure and no other object is listed. | | | | +| Notes | | | | | + +| | | | | | +|-----------------|--------------------------------------------------------------------------------|------------------------|--------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-002 | | | | +| TP label | Objects for Continuous Glucose Monitor specialization - Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable | Glucose 1; M | SensCal 1; O | SensRun 1; O | + +| | | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------|------------------| +| | items | GluSamplInt 1; O | GluTrend 1; O | PHighLow 1; O | +| | | DevHypoHyper 1; O | GluRateChange 1; O | PHDDMStatus 1; O | +| | | CGMStatus 1; O | | | +| Test purpose |

    Check that:

    The Glucose numeric object with Type {MDC_PART_SCADA MDC_CONC_GLU_ISF or MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD or MDC_CONC_GLU_CAPILLARY_PLASMA or MDC_CONC_GLU_VENOUS_WHOLEBLOOD or MDC_CONC_GLU_VENOUS_PLASMA or MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD or MDC_CONC_GLU_ARTERIAL_PLASMA or MDC_CONC_GLU_CONTROL or MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD or MDC_CONC_GLU_UNDETERMINED_PLASMA} is supported by a Continuous Glucose Monitor PHD with extended configuration. Only one object is allowed.

    [AND]

    The Sensor calibration numeric object with Type {MDC_PART_PHD_DM MDC_CGM_SENSOR_CALIBRATION} may be present in the CGM extended configuration. Only one object is allowed.

    [AND]

    The Sensor run-time numeric object with Type {MDC_PART_PHD_DM MDC_CGM_SENSOR_RUN_TIME} may be present in the CGM extended configuration. Only one object is allowed.

    [AND]

    The Glucose Sampling Interval numeric object with Type {MDC_PART_PHD_DM MDC_CGM_SENSOR_SAMPLE_INTERVAL} may be present in the CGM extended configuration. Only one object is allowed.

    [AND]

    The Glucose Trend numeric object with Type {MDC_PART_PHD_DM MDC_CONC_GLU_TREND} may be present in the CGM extended configuration. Only one instance is allowed.

    [AND]

    The Patient low/high threshold compound numeric object with Type {MDC_PART_PHD_DM MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH} may be present in the CGM extended configuration. Only one instance is allowed.

    [AND]

    The Device hypo/hyper thresholds compound numeric object with Type {MDC_PART_PHD_DM MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER} may be present in the CGM extended configuration. Only one instance is allowed.

    [AND]

    The Glucose rate of change thresholds compound numeric object with Type {MDC_PART_PHD_DM MDC_CONC_GLU_RATE_THRESHOLDS} may be present in the CGM extended configuration. Only one instance is allowed.

    [AND]

    The PHD DM status enumeration object with Type {MDC_PART_PHD_DM MDC_PHD_DM_DEV_STAT} may be present in the CGM extended configuration. Multiple PHD DM status enumeration are allowed if they have different [Supplemental-Types] attribute values.

    [AND]

    | | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The CGM status enumeration object with Type {MDC_PART_PHD_DM MDC_CGM_DEV_STAT} may be present in the CGM extended configuration. Only one instance is allowed. | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 | +| Other PICS | C_AG_CGM_001, C_AG_CGM_002, C_AG_CGM_003, C_AG_CGM_004, C_AG_CGM_005, C_AG_CGM_006, C_AG_CGM_007, C_AG_CGM_008, C_AG_CGM_009, C_AG_CGM_010, C_AG_CGM_011, C_AG_CGM_012, C_AG_CGM_013, C_AG_CGM_014, C_AG_CGM_015, C_AG_CGM_016, C_AG_CGM_017, C_AG_CGM_018, C_AG_CGM_019 | +| Initial condition | The simulated PHG and PHD under test are in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a “Remote Operation Invoke Confirmed Event Report” message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is in the extended range; if it is not, PHG responds with a “unsupported-config” and waits for a new configuration.
    5. 5. Once the PHD under test sends an extended configuration, Check that:
      Attribute-List:
      1. a. attribute-value( ConfigReport → ConfigObjectList (ConfigObject)→Attribute List), this value depends on the attribute type. The values we have to check are:
        • • The Glucose numeric object is present once → MDC_PART_SCADA (0x00 0x02), MDC_CONC_GLU_ISF (0x71 0xD4)
        • θ Any of these objects may be present:
          • • IF C_AG_CGM_001 THEN the Sensor calibration numeric Object is present once → MDC_PART_PHD_DM (0x00 0x80), MDC_CGM_SENSOR_CALIBRATION (0x72 0xF4)
          • • IF C_AG_CGM_002 THEN the Sensor run-time numeric Object is present at least once → MDC_PART_PHD_DM (0x00 0x80), MDC_CGM_SENSOR_RUN_TIME (0x72 0xF8)
          • • IF C_AG_CGM_003 THEN one instance of the Glucose Sampling Interval numeric object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_CGM_SENSOR_SAMPLE_INTERVAL (0x72 0xFC)
          • • IF C_AG_CGM_004 THEN the Glucose Trend numeric Object is present once → MDC_PART_PHD_DM (0x00 0x80), MDC_CONC_GLU_TREND (0x72 0xD8)
          • • IF C_AG_CGM_005 THEN the Insulin to Patient low/high threshold compound numeric Object is present once → MDC_PART_PHD_DM (0x00 0x80), MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH (0x72 0xDC)
          • • IF C_AG_CGM_006 THEN the Device hypo/hyper thresholds compound numeric Object is present once → MDC_PART_PHD_DM (0x00 0x80), MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER (0x72 0xE0)
          • • IF C_AG_CGM_007 THEN the Glucose rate of change thresholds compound numeric Object is present once → MDC_PART_PHD_DM (0x00 0x80), MDC_CONC_GLU_RATE_THRESHOLDS (0x72 0xE4)
          • • IF C_AG_CGM_008 THEN the PHD DM status enumeration object is present at least once → MDC_PART_PHD_DM (0x00 0x80), MDC_PHD_DM_DEV_STAT (0x4E 0x20). If multiple PHD DM status enumeration objects are present, check that they have different [Supplemental-Types] attribute values.
          • • IF C_AG_CGM_009 THEN the CGM status enumeration object is present once → MDC_PART_PHD_DM (0x00 0x80), MDC_CGM_DEV_STAT (0x73 0x0C)
    | + +| | | +|---------------------------|------------------------------------------------------------| +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-003 | | | | +| TP label | Glucose Numeric Object - Standard configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | Glucose 2; M | Glucose 4; M | Glucose 6; M | +| | | Glucose 8; M | Glucose 10; M | Glucose 12; M | +| | | Glucose 14; M | Glucose 16; M | Glucose 18; M | +| | | Glucose 20; NR | Glucose 22; NR | Glucose 27; M | +| Test purpose | Check that:
    The Glucose Numeric object contains the attributes specified for Standard Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND (NOT C_AG_OXP_181) | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a “Remote Operation Invoke Confirmed Event Report” message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. 3. Check that the field Dev-Config-Id is set to 0x09C4 (2500). If it is not, PHG responds with a “unsupported-config” and waits for a new configuration.
    4. 4. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    5. 5. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test.
    6. 6. Once the PHD under test sends a standard configuration and a measurement, check that the Glucose Numeric Object attributes are:
      1. a. Mandatory attribute Handle
        • attribute-id = MDC_ATTR_ID_HANDLE
        • attribute-type = HANDLE
        • attribute-value = 0x00 0x01
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b. Mandatory attribute Type

    • attribute-id = MDC_ATTR_ID_TYPE
    • attribute-type = TYPE
    • attribute-value = MDC_PART_SCADA (0x00 0x02) MDC_CONC_GLU_ISF (0x71 0xD4)

    c. Mandatory attribute Supplemental-Types

    • attribute-id = MDC_ATTR_ID_TYPE
    • attribute-type = MDC_ATTR_SUPPLEMENTAL_TYPES
    • attribute-value.length = SEQUENCE OF (SIZE (4) )
    • attribute-value = { MDC_PART_PHD_DM (0x00 0x80),
      MDC_CTXT_GLU_SAMPLELOCATION_SUBCUTANEOUS (0x72 0x39) }

    d. Mandatory attribute Metric-Spec-Small

    • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
    • attribute-type = MetricSpecSmall (BITS-16)
    • attribute-value.length = 2 bytes
    • attribute-value ≠ 0x00 0x00
      • • Bit 0 (mss-avail-intermittent(0)), must be set
      • • Bit 1 (mss-avail-stored-data(1)), must be set
      • • Bit 9 (mss-acc-agent-initiated(9)), must be set
      • • Bit 14 (mss-cat-calculation(14)), must be set
      • • Rest shall be set to 0.

    e. Mandatory attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type(INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_MILLI_G_PER_DL (0x08 0x52)

    f. Mandatory attribute Attribute-Value-Map

    • attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP
    • attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )
    • attribute-value.length=<variable>
    • attribute-value= MDC_ATTR_NU_VAL_OBS_BASIC, then
      MDC_ATTR_TIME_STAMP_BO

    g. If not recommended attribute Measurement-Confidence-95 is present

    • attribute-id = MDC_ATTR_MSMT_CONFIDENCE_95 (0x0A 0x8C)
    • attribute-type = MeasurementConfidence95
    • attribute-value.length = 4 bytes
    • attribute-value = <not relevant>

    h. If not recommended attribute Threshold-Notification-Text-String is present

    • attribute-id = MDC_ATTR_THRES_NOTIF_TEXT_STRING (0x0A 0x88)
    • attribute-type = OCTET STRING
    • attribute-value.length = <variable>
    • attribute-value = <Text not relevant>

    i. No other attribute shall be present at configuration

    | +| Pass/Fail criteria |
    • • All checked values are as specified in the test procedure.
    | + +| | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • The Attribute-Value-Map attribute SHALL contain the attribute ID and attribute length information of the Basic-Nu-Observed-Value and Base-Offset-Time-Stamp attribute in the same order as indicated in f.
    | +| Notes | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-004 | | | | +| TP label | Glucose Numeric Object - Extended configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | Glucose 5; M | Glucose 7; O | Glucose 9; M | +| | | Glucose 11; R | Glucose 13; M | Glucose 17; R | +| | | Glucose 19; R | Glucose 21; O | Glucose 23; O | +| | | Glucose 24; C | | | +| Test purpose | Check that:
    The Glucose Numeric Object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with "unsupported-config" and waits for a new configuration.
    4. IF C_AG_OXP_293 THEN:
      1. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. IF the mds-time-mgr-set-time bit is set:
        • ❑ The PHG moves to Configuring/Sending Set Time substate and:
          • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • ❑ Once its internal time setting operation is completed, the PHD responds to the manager.
    5. pHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test.
    6. Once the PHD under test sends an extended configuration and a measurement, check that the Glucose Numeric Object attributes are:
      1. Mandatory attribute Type
        • ❑ attribute-id = MDC_ATTR_ID_TYPE
        • ❑ attribute-type = TYPE
    | | | | + +- attribute-value = MDC\_PART\_SCADA (0x00 0x02) | MDC\_CONC\_GLU\_ISF (0x71 0xD4) or MDC\_CONC\_GLU\_CAPILLARY\_WHOLEBLOOD (0x71 0xB8) or MDC\_CONC\_GLU\_CAPILLARY\_PLASMA (0x71 0xBC) or MDC\_CONC\_GLU\_VENOUS\_WHOLEBLOOD (0x71 0xC0) or MDC\_CONC\_GLU\_VENOUS\_PLASMA (0x71 0xC4) or MDC\_CONC\_GLU\_ARTERIAL\_WHOLEBLOOD (0x71 0xC8) or MDC\_CONC\_GLU\_ARTERIAL\_PLASMA (0x71 0xCC) or MDC\_CONC\_GLU\_CONTROL (0x71 0xD0) or MDC\_CONC\_GLU\_UNDETERMINED\_WHOLEBLOOD (0x72 0x6C) or MDC\_CONC\_GLU\_UNDETERMINED\_PLASMA (0x72 0x70) + +#### b. If optional attribute Supplemental-Types is present + +- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES +- attribute-type = SupplementalTypeList +- attribute-value.length = SEQUENCE OF (SIZE (4) ) +- attribute-value = { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_CTXT\_GLU\_SAMPLELOCATION\_FINGER (0x72 0x38) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_AST (0x72 0x3C) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_EARLOBE (0x72 0x40) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_CTRL SOLUTION (0x72 0x44) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_SUBCUTANEOUS (0x72 0x39) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_UNDETERMINED (0x72 0x35) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_OTHER (0x72 0x36) } + +#### c. Mandatory attribute Metric-Spec-Small + +- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL +- attribute-type = MetricSpecSmall (BITS-16) +- attribute-value.length = 2 bytes + - Bit 0 (mss-avail-intermittent(0)), must be set + - Bit 1 (mss-avail-stored-data(1)), must be set + - Bit 9 (mss-acc-agent-initiated(9)), must be set + - Bit 14 (mss-cat-calculation(14)), must be set + - Rest of bits set to 0 + +#### d. If recommended attribute Measurement-Status is present + +- attribute-id = MDC\_ATTR\_MSMT\_STAT +- attribute-type = MeasurementStatus +- attribute-value.length = 2 bytes +- attribute-value = + - Bit msmt-state-in-alarm(14) may be set to indicate that the measurement is outside threshold boundaries. + - Bit msmt-state-al-inhibited(15) may be set to indicate that the threshold indication is disabled and should not cause a displayed annunciation +- If thresholding is to be used, this attribute is mandatory + +#### e. Mandatory attribute Unit-Code + +- attribute-id = MDC\_ATTR\_UNIT\_CODE +- attribute-type = OID-Type(INT-U16) +- attribute-value.length = 2 bytes +- attribute-value = one of: + - MDC\_DIM\_MILLI\_G\_PER\_DL (0x08 0x52) + - MDC\_DIM\_MILLI\_MOLE\_PER\_L (0x12 0x72) + +#### f. If recommended attribute Base-Offset-Time-Stamp is present + +- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = BaseOffsetTime
    • attribute-value.length = 8 bytes
    • g. If recommended attribute Basic-Nu-Observed-Value is present
      • attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC
      • attribute-type = BasicNuObsValue
      • attribute-value.length = 2 bytes
    • h. If optional attribute Threshold-Notification-Text-String is present
      • attribute-id = MDC_ATTR_THRES_NOTIF_TEXT_STRING (0x0A 0x88)
      • attribute-type = OCTET STRING
      • attribute-value.length = <variable>
      • attribute-value = <Text related to the current threshold notification>
      • If this attribute is present (thresholding is to be used), Measurement-Status attribute is mandatory
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-005 | | | +| TP label | Sensor Calibration Numeric Object - Extended configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | SensCal 3; M | SensCal 4; O | +| | | SensCal 6; R | SensCal 7; M | +| | | SensCal 9; R | SensCal 5; M | +| Test purpose | Check that:
    The Sensor Calibration Numeric Object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 AND C_AG_CGM_001 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | | | +| Initial condition | The simulated PHG and PHD under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with "unsupported-config" and waits for a new configuration.
    4. 4. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
    | | | + +- The PHG moves to Configuring/Sending Set Time substate and: + - IF C\_AG\_OXP\_009 THEN it issues the Set-Time action command. + - IF C\_AG\_OXP\_014 THEN it issues the Set-Base-Offset-Time action command. +- Once its internal time setting operation is completed, the PHD responds to the manager. + +5. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test. + +6. Once the PHD under test sends an extended configuration and a measurement, check that the Sensor Calibration Numeric Object attributes are: + +a. Mandatory attribute Type + +- attribute-id = MDC\_ATTR\_ID\_TYPE +- attribute-type = TYPE +- attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) | +MDC\_CGM\_SENSOR\_CALIBRATION (0x72 0xF4) + +b. If optional attribute Supplemental-Types is present + +- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES +- attribute-type = SupplementalTypeList +- attribute-value.length = SEQUENCE OF (SIZE (4) ) +- attribute-value = { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_CTXT\_GLU\_SAMPLELOCATION\_FINGER (0x72 0x38) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_AST (0x72 0x3C) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_EARLOBE (0x72 0x40) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_SUBCUTANEOUS (0x72 0x39) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_UNDETERMINED (0x72 0x35) or +MDC\_CTXT\_GLU\_SAMPLELOCATION\_OTHER (0x72 0x36) } + +c. Mandatory attribute Metric-Spec-Small + +- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL +- attribute-type = MetricSpecSmall (BITS-16) +- attribute-value.length = 2 bytes + - Bit 1 (mss-avail-stored-data(1)), must be set + - Bit 2 (mss-upd-aperiodic(2)), must be set + - Bit 9 (mss-acc-agent-initiated(9)), must be set + - Bit 12 (mss-cat-manual(12)), must be set if the reading is manually entered + - Bit 13 (mss-cat-setting(13)), must be set + - Rest of bits set to 0 + +d. If recommended attribute Measurement-Status is present + +- attribute-id = MDC\_ATTR\_MSMT\_STAT +- attribute-type = MeasurementStatus +- attribute-value.length = 2 bytes + +e. Mandatory attribute Unit-Code + +- attribute-id = MDC\_ATTR\_UNIT\_CODE +- attribute-type = OID-Type(INT-U16) +- attribute-value.length = 2 bytes +- attribute-value = one of: + - MDC\_DIM\_MILLI\_G\_PER\_DL (0x08 0x52) + - MDC\_DIM\_MILLI\_MOLE\_PER\_L (0x12 0x72) + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    f. If recommended attribute Base-Offset-Time-Stamp is present

    • attribute-id = MDC_ATTR_TIME_STAMP_BO
    • attribute-type = BaseOffsetTime
    • attribute-value.length = 8 bytes

    g. If recommended attribute Basic-Nu-Observed-Value is present

    • attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC
    • attribute-type = BasicNuObsValue
    • attribute-value.length = 2 bytes
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-006 | | | | +| TP label | Sensor run-time Numeric Object - Extended configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | SensRun 3; M | SensRun 4; M | SensRun 5; M | +| | | SensRun 6; R | SensRun 7; R | | +| Test purpose |

    Check that:

    The Sensor runtime Numeric Object contains the attributes specified for Extended Configuration.

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 AND C_AG_CGM_002 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a “Remote Operation Invoke Confirmed Event Report” message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with “unsupported-config” and waits for a new configuration.
    4. 4. IF C_AG_OXP_293 THEN:
      • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      • c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    5. 5. The PHD under test sends an Event Report to the simulated PHG including a
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement reported by the object under test.

    6. Once the PHD under test sends an extended configuration and a measurement, check that the Sensor run-time Numeric Object attributes are:

    • a. Mandatory attribute Type
      • attribute-id = MDC_ATTR_ID_TYPE
      • attribute-type = TYPE
      • attribute-value = MDC_PART_PHD_DM (0x00 0x80) MDC_CGM_SENSOR_RUN_TIME (0x72 0xF8)
    • b. Mandatory attribute Metric-Spec-Small
      • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
      • attribute-type = MetricSpecSmall (BITS-16)
      • attribute-value.length = 2 bytes
        • • Bit 1 (mss-avail-stored-data(1)), must be set
        • • Bit 2 (mss-upd-aperiodic(2)), must be set
        • • Bit 3 (mss-msmt-aperiodic(3)), must be set
        • • Bit 9 (mss-acc-agent-initiated(9)), must be set
        • • Bit 13 (mss-cat-setting(13)), must be set
        • • Bit 14 (mss-cat-calculation(14)), must be set
        • • Rest of bits set to 0
    • c. Mandatory attribute Unit-Code
      • attribute-id = MDC_ATTR_UNIT_CODE
      • attribute-type = OID-Type(INT-U16)
      • attribute-value.length = 2 bytes
      • attribute-value = MDC_DIM_HR (0x08 0xC0)
    • d. If recommended attribute Base-Offset-Time-Stamp is present
      • attribute-id = MDC_ATTR_TIME_STAMP_BO
      • attribute-type = BaseOffsetTime
      • attribute-value.length = 8 bytes
    • e. If recommended attribute Basic-Nu-Observed-Value is present
      • attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC
      • attribute-type = BasicNuObsValue
      • attribute-value.length = 2 bytes
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------|-------------------------------------------------------------------|------------------------------------|------------------------------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-007 | | | +| TP label | Glucose sampling interval Numeric Object - Extended configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | GluSampInt 3; M
    GluSampInt 6; R | GluSampInt 4; M
    GluSampInt 7; R | +| Test purpose | Check that: | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The Glucose sampling interval Numeric Object contains the attributes specified for Extended Configuration. | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 AND C_AG_CGM_003 | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a “Remote Operation Invoke Confirmed Event Report” message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with “unsupported-config” and waits for a new configuration.
    4. 4. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    5. 5. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test.
    6. 6. Once the PHD under test sends an extended configuration and a measurement, check that the Glucose sampling interval Numeric Object attributes are:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_DM (0x00 0x80) MDC_CGM_SENSOR_SAMPLE_INTERVAL (0x72 0xFC)
      2. b. Mandatory attribute Metric-Spec-Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value.length = 2 bytes
          • • Bit 1 (mss-avail-stored-data(1)), must be set
          • • Bit 2 (mss-upd-aperiodic(2)), must be set
          • • Bit 9 (mss-acc-agent-initiated(9)), must be set
          • • Bit 12 (mss-cat-manual(12)), must be set
          • • Bit 13 (mss-cat-setting(13)), must be set
          • • Rest of bits set to 0
      3. c. Mandatory attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type(INT-U16)
    | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_MIN (0x08 0xA0)
    • d. If recommended attribute Base-Offset-Time-Stamp is present
      • attribute-id = MDC_ATTR_TIME_STAMP_BO
      • attribute-type = BaseOffsetTime
      • attribute-value.length = 8 bytes
    • e. If recommended attribute Basic-Nu-Observed-Value is present
      • attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC
      • attribute-type = BasicNuObsValue
      • attribute-value.length = 2 bytes
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHDCLASS/CGM/BV-008 | | | +| TP label | Glucose trend Numeric Object - Extended configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | GluTrend 3; M | GluTrend 4; M | +| | | GluTrend 6; R | GluTrend 7; R | +| Test purpose | Check that:

    The Glucose trend Numeric Object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 AND C_AG_CGM_004 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a “Remote Operation Invoke Confirmed Event Report” message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with “unsupported-config” and waits for a new configuration.
    4. 4. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action
    | | | + +command. + +- Once its internal time setting operation is completed, the PHD responds to the PHG. +5. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test. + 6. Once the PHD under test sends an extended configuration and a measurement, check that the Glucose trend Numeric Object attributes are: + - a. Mandatory attribute Type + - attribute-id = MDC\_ATTR\_ID\_TYPE + - attribute-type = TYPE + - attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) | +MDC\_CONC\_GLU\_TREND (0x72 0xD8) + - b. Mandatory attribute Metric-Spec-Small + - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL + - attribute-type = MetricSpecSmall (BITS-16) + - attribute-value.length = 2 bytes + - c. Mandatory attribute Unit-Code + - attribute-id = MDC\_ATTR\_UNIT\_CODE + - attribute-type = OID-Type(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = one of: + - MDC\_DIM\_MILLI\_G\_PER\_DL\_PER\_MIN (0x12 0x74) + - MDC\_DIM\_MILLI\_MOLE\_PER\_L\_PER\_MIN (0x12 0x78) + - d. If recommended attribute Base-Offset-Time-Stamp is present + - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO + - attribute-type = BaseOffsetTime + - attribute-value.length = 8 bytes + - e. If recommended attribute Basic-Nu-Observed-Value is present + - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS\_BASIC + - attribute-type = BasicNuObsValue + - attribute-value.length = 2 bytes + - f. If optional attribute Threshold-Notification-Text-String is present + - attribute-id = MDC\_ATTR\_THRES\_NOTIF\_TEXT\_STRING (0x0A 0x88) + - attribute-type = OCTET STRING + - attribute-value.length = + - attribute-value = + - If this attribute is present (thresholding is to be used), Measurement-Status attribute is mandatory + - g. If conditional attribute Measurement-Status is present + - attribute-id = MDC\_ATTR\_MSMT\_STAT + - attribute-type = MeasurementStatus + - attribute-value.length = 2 bytes + - attribute-value = + - Bit msmt-state-in-alarm(14) may be set to indicate that the measurement is outside threshold boundaries. + - Bit msmt-state-al-inhibited(15) may be set to indicate that the threshold + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| | indication is disabled and should not cause a displayed annunciation
    If thresholding is to be used, this attribute is mandatory | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/CGM/BV-009 | | | +| TP label | Patient low/high thresholds Compound Numeric Object - Extended configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | PHighLow 3; M | PHighLow 4; M | +| | | PHighLow 6; M | PHighLow 7; M | +| | | PHighLow 9; R | PHighLow 8; R | +| Test purpose | Check that:
    The Patient low/high thresholds Compound Numeric Object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 AND C_AG_CGM_005 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with "unsupported-config" and waits for a new configuration.
    4. 4. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    5. 5. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test.
    6. 6. Once the PHD under test sends an extended configuration and a measurement, check that the Patient low/high thresholds Compound Numeric Object attributes are:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value = MDC_PART_PHD_DM (0x00 0x80)
      MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH (0x72 0xDC)
    • b. Mandatory attribute Metric-Spec-Small
      • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
      • attribute-type = MetricSpecSmall (BITS-16)
      • attribute-value.length = 2 bytes
    • c. Mandatory attribute Metric-Structure-Small
      • attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL
      • attribute-type = MetricStructureSmall
      • attribute-value = {ms-struct-compound-fix, 2}
    • d. Mandatory attribute Metric-Id-List
      • attribute-id = MDC_ATTR_ID_PHYSIO_LIST
      • attribute-type = MetricIdList
      • attribute-value.length = SEQUENCE OF (SIZE 2)
      • attribute-value = MDC_CONC_GLU_PATIENT_THRESHOLD_LOW (0x72 0xDD), then MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH (0x72 0xDE)
    • e. Mandatory attribute Unit-Code
      • attribute-id = MDC_ATTR_UNIT_CODE
      • attribute-type = OID-Type(INT-U16)
      • attribute-value.length = 2 bytes
      • attribute-value = one of:
        • • MDC_DIM_MILLI_G_PER_DL (0x08 0x52)
        • • MDC_DIM_MILLI_MOLE_PER_L (0x12 0x72)
    • f. If recommended attribute Base-Offset-Time-Stamp is present
      • attribute-id = MDC_ATTR_TIME_STAMP_BO
      • attribute-type = BaseOffsetTime
      • attribute-value.length = 8 bytes
    • g. If recommended attribute Compound-Basic-Nu-Observed-Value is present
      • attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC
      • attribute-type = BasicNuObsValueCmp
      • attribute-value.length = SEQUENCE OF (SIZE(4))
      • attribute-value = it shall include first the patient low threshold (MDC_CONC_GLU_PATIENT_THRESHOLD_LOW) followed by the patient high threshold (MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH).
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|-----------------|-------------------------------------------------------------------------------|------------------------|-------------------|-------------------| +| TP Id | TP/PLT/PHDCLASS/CGM/BV-010 | | | | +| TP label | Device hypo/hyper thresholds Compound Numeric Object - Extended configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | DevHypoHyper 3; M | DevHypoHyper 4; M | DevHypoHyper 5; M | +| | | DevHypoHyper 6; M | DevHypoHyper 7; M | DevHypoHyper 8; R | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--|--| +| | | DevHypoHyper 9; R | | | +| Test purpose |

    Check that:
    The Device hypo/hyper thresholds Compound Numeric Object contains the attributes specified for Extended Configuration.

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 AND C_AG_CGM_006 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with "unsupported-config" and waits for a new configuration.
    4. 4. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    5. 5. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test.
    6. 6. Once the PHD under test sends an extended configuration and a measurement, check that the Device hypo/hyper thresholds Compound Numeric Object attributes are:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_DM (0x00 0x80) MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER (0x72 0xE0)
      2. b. Mandatory attribute Metric-Spec-Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value.length = 2 bytes
      3. c. Mandatory attribute Metric-Structure-Small
        • attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL
        • attribute-type = MetricStructureSmall
        • attribute-value = {ms-struct-compound-fix, 2}
      4. d. Mandatory attribute Metric-Id-List
        • attribute-id = MDC_ATTR_ID_PHYSIO_LIST
        • attribute-type = MetricIdList
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value.length = SEQUENCE OF (SIZE 2)
    • attribute-value = MDC_CONC_GLU_THRESHOLD_HYPO (0x72 0xE1), then MDC_CONC_GLU_THRESHOLD_HYPER (0x72 0xE2)

    e. Mandatory attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type(INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = one of:
      • • MDC_DIM_MILLI_G_PER_DL (0x08 0x52)
      • • MDC_DIM_MILLI_MOLE_PER_L (0x12 0x72)

    f. If recommended attribute Base-Offset-Time-Stamp is present

    • attribute-id = MDC_ATTR_TIME_STAMP_BO
    • attribute-type = BaseOffsetTime
    • attribute-value.length = 8 bytes

    g. If recommended attribute Compound-Basic-Nu-Observed-Value is present

    • attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC
    • attribute-type = BasicNuObsValueCmp
    • attribute-value.length = SEQUENCE OF (SIZE(4))
    • attribute-value = it shall include first the device hypo threshold (MDC_CONC_GLU_PATIENT_THRESHOLD_HYPO) followed by the device hyper threshold (MDC_CONC_GLU_PATIENT_THRESHOLD_HYPER).
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--------------------| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-011 | | | | +| TP label | Glucose rate-of-change thresholds Compound Numeric Object - Extended configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | GluRateChange 3; M | GluRateChange 4; M | GluRateChange 5; M | +| | | GluRateChange 6; M | GluRateChange 7; M | GluRateChange 8; R | +| | | GluRateChange 9; R | | | +| Test purpose | Check that:
    The Glucose rate-of-change thresholds Compound Numeric Object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 AND C_AG_CGM_007 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG. | | | | + +3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with “unsupported-config” and waits for a new configuration. +4. IF C\_AG\_OXP\_293 THEN: + - a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes. + - b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object. + - c. IF the mds-time-mgr-set-time bit is set: + - The PHG moves to Configuring/Sending Set Time substate and: + - IF C\_AG\_OXP\_009 THEN it issues the Set-Time action command. + - IF C\_AG\_OXP\_014 THEN it issues the Set-Base-Offset-Time action command. + - Once its internal time setting operation is completed, the PHD responds to the PHG. +5. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test. +6. Once the PHD under test sends an extended configuration and a measurement, check that the Glucose rate-of-charge thresholds Compound Numeric Object attributes are: + - a. Mandatory attribute Type + - attribute-id = MDC\_ATTR\_ID\_TYPE + - attribute-type = TYPE + - attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_CONC\_GLU\_RATE\_THRESHOLDS (0x72 0xE4) + - b. Mandatory attribute Metric-Spec-Small + - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL + - attribute-type = MetricSpecSmall (BITS-16) + - attribute-value.length = 2 bytes + - c. Mandatory attribute Metric-Structure-Small + - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL + - attribute-type = MetricStructureSmall + - attribute-value = {ms-struct-compound-fix, 2} + - d. Mandatory attribute Metric-Id-List + - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST + - attribute-type = MetricIdList + - attribute-value.length = SEQUENCE OF (SIZE 2) + - attribute-value = MDC\_CONC\_GLU\_RATE\_THRESHOLD\_INCREASE (0x72 0xE5), then MDC\_CONC\_GLU\_RATE\_THRESHOLD\_DECREASE (0x72 0xE6) + - e. Mandatory attribute Unit-Code + - attribute-id = MDC\_ATTR\_UNIT\_CODE + - attribute-type = OID-Type(INT-U16) + - attribute-value.length = 2 bytes + - attribute-value = one of: + - MDC\_DIM\_MILLI\_G\_PER\_DL\_PER\_MIN (0x12 0x74) + - MDC\_DIM\_MILLI\_MOLE\_PER\_L\_PER\_MIN (0x12 0x78) + - f. If recommended attribute Base-Offset-Time-Stamp is present + - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = BaseOffsetTime
    • attribute-value.length = 8 bytes

    g. If recommended attribute Compound-Basic-Nu-Observed-Value is present

    • attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC
    • attribute-type = BasicNuObsValueCmp
    • attribute-value.length = SEQUENCE OF (SIZE(4))
    • attribute-value = it shall include first the glucose rate increase threshold (MDC_CONC_GLU_RATE_THRESHOLD_INCREASE) followed by the glucose rate decrease threshold (MDC_CONC_GLU_RATE_THRESHOLD_DECREASE).
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|------------------| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-012 | | | | +| TP label | PHD DM Status Enumeration Object - Extended configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | PHDDMStatus 3; M | PHDDMStatus 4; R | PHDDMStatus 5; M | +| | | PHDDMStatus 6; R | PHDDMStatus 7; M | | +| Test purpose |

    Check that:

    The PHD DM Status Enumeration Object contains the attributes specified for Extended Configuration.

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 AND C_AG_CGM_008 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with "unsupported-config" and waits for a new configuration.
    4. 4. IF C_AG_OXP_293 THEN:
      • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      • c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    | | | | + +5. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test +6. Once the PHD under test sends an extended configuration and a measurement, check that the PHD DM Status Enumeration Object attributes are: + - a. Mandatory attribute Type + - attribute-id = MDC\_ATTR\_ID\_TYPE + - attribute-type = TYPE + - attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_PHD\_DM\_DEV\_STAT (0x4E 0x20) + - b. If recommended attribute Supplemental-Types is present + - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES + - attribute-type = SupplementalTypeList + - attribute-value.length = SEQUENCE OF (SIZE (4) ) + - attribute-value = { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_CGM\_DEV\_TYPE\_SENSOR (0x73 0x14) or MDC\_CGM\_DEV\_TYPE\_TRANSMITTER (0x73 0x15) or MDC\_CGM\_DEV\_TYPE\_RECEIVER (0x73 0x16) or MDC\_CGM\_DEV\_TYPE\_OTHER (0x73 0x17) } + - c. Mandatory attribute Metric-Spec-Small + - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL + - attribute-type = MetricSpecSmall (BITS-16) + - attribute-value.length = 2 bytes + - attribute-value ≠ 0x00 0x00 + - Bit 0 must be set (mss-avail-intermittent(0)) + - Bit 1 must be set (mss-avail-stored-data(1)) + - Bit 2 must be set (mss-upd-aperiodic (2)) + - Bit 9 must be set (mss-acc-agent-initiated(9)) + - d. If recommended attribute Base-Offset-Time-Stamp is present + - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO + - attribute-type = BaseOffsetTime + - attribute-value.length = 8 bytes + - e. If recommended attribute Enum-Observed-Value-Simple-Bit-Str is present + - attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_SIMP\_BIT\_STR + - attribute-type = BITS-32 + - attribute-value.length = 4 bytes + - attribute-value = + - device-status-undetermined (Bit 0) may be set + - device-status-reset (Bit 1) may be set + - device-status-error (Bit 5) may be set + - device-status-error-mechanical (Bit 6) may be set + - device-status-error-electronic (Bit 7) may be set + - device-status-error-software (Bit 8) may be set + - device-status-error-battery (Bit 9) may be set + - device-status-service (Bit 15) may be set + - device-status-service-time-sync-required (Bit 16) may be set + - device-status-service-calibration-required (Bit 17) may be set + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ device-status-service-replenishment-required (Bit 18) may be set
    • ▪ device-status-battery-low (Bit 25) may be set
    • ▪ device-status-battery-depleted (Bit 26) may be set
    • ▪ device-status-battery-replaced (Bit 27) may be set
    • ▪ device-status-battery-interrupted (Bit 28) may be set
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|----------------| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-013 | | | | +| TP label | CGM status Enumeration Object - Extended configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | CGMStatus 3; M | CGMStatus 4; M | CGMStatus 5; R | +| | | CGMStatus 6; R | | | +| Test purpose | Check that:
    The CGM status Enumeration Object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_181 AND C_AG_CGM_009 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with "unsupported-config" and waits for a new configuration.
    4. 4. IF C_AG_OXP_293 THEN:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • ❑ The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 THEN it issues the Set-Time action command.
          • • IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.
        • ❑ Once its internal time setting operation is completed, the PHD responds to the PHG.
    5. 5. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test
    6. 6. Once the PHD under test sends an extended configuration and a measurement, check that the CGM status Enumeration Object attributes are:
      1. a. Mandatory attribute Type
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id = MDC_ATTR_ID_TYPE
    • attribute-type = TYPE
    • attribute-value = MDC_PART_PHD_DM (0x00 0x80) MDC_CGM_DEV_STAT (0x73 0x0C)
    • b. Mandatory attribute Metric-Spec-Small
      • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
      • attribute-type = MetricSpecSmall (BITS-16)
      • attribute-value.length = 2 bytes
      • attribute-value ≠ 0x00 0x00
        • ▪ Bit 0 must be set (mss-avail-intermittent(0))
        • ▪ Bit 1 must be set (mss-avail-stored-data(1))
        • ▪ Bit 2 must be set (mss-upd-aperiodic (2))
        • ▪ Bit 3 must be set (mss-msmt-aperiodic (3))
        • ▪ Bit 9 must be set (mss-acc-agent-initiated(9))
    • c. If recommended attribute Base-Offset-Time-Stamp is present
      • attribute-id = MDC_ATTR_TIME_STAMP_BO
      • attribute-type = BaseOffsetTime
      • attribute-value.length = 8 bytes
    • d. If recommended attribute Enum-Observed-Value-Simple-Bit-Str is present
      • attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR
      • attribute-type = BITS-32
      • attribute-value.length = 4 bytes
      • attribute-value =
        • ▪ sensor-session-stopped (Bit 0) may be set
        • ▪ sensor-type-incorrect (Bit 2) may be set
        • ▪ sensor-malfunction (Bit 3) may be set
        • ▪ device-specific-alert (Bit 4) may be set
        • ▪ sensor-calibration-not-allowed (Bit 7) may be set
        • ▪ sensor-calibration-recommended (Bit 8) may be set
        • ▪ sensor-calibration-required (Bit 9) may be set
        • ▪ sensor-temp-too-high (Bit 10) may be set
        • ▪ sensor-temp-too-low (Bit 11) may be set
        • ▪ sensor-result-below-patient-low (Bit 12) may be set
        • ▪ sensor-result-above-patient-high (Bit 13) may be set
        • ▪ sensor-low-hypo (Bit 14) may be set
        • ▪ sensor-high-hyper (Bit 15) may be set
        • ▪ sensor-rate-decrease-exceeded (Bit 16) may be set
        • ▪ sensor-rate-increase-exceeded (Bit 17) may be set
        • ▪ sensor-result-too-low (Bit 18) may be set
        • ▪ sensor-result-too-high (Bit 19) may be set
        • ▪ sensor-com-out-of-range (Bit 20) may be set
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|----------------------| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-014 | | | | +| TP label | PM-Store Attributes for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | PMStrObjAttCGM 2; M | PMStrObjAttCGM 4; M | PMStrObjAttCGM 5; M | +| | | PMStrObjAttCGM 6; M | PMStrObjAttCGM 8; NR | PMStrObjAttCGM 9; M | +| | | PMStrObjAttCGM 10; M | PMStrObjAttCGM 11; C | PMStrObjAttCGM 12; M | +| | | PMStrObjAttCGM 13; M | | | +| Test purpose | Check that:
    PM-Store Object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_041 AND C_AG_OXP_181 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a “Remote Operation Invoke Confirmed Event Report” message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The simulated PHG shall send a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.
    5. 5. The PHD issues a GET response with the PM-Store attributes it supports:
      1. a. Mandatory attribute PM-Store-Capab
        1. attribute-id = MDC_ATTR_PM_STORE_CAPAB
        2. attribute-type = PmStoreCapab
        3. attribute-value.length = 2 bytes
        4. attribute-value
          1. ▪ pmsc-var-no-of-segm (bit 0) shall be set If the agent creates new segments either due to storing data of multiple sessions or due to time changes
          2. ▪ pmsc-epi-seg-entries (bit 4) shall be set
          3. ▪ pmsc-peri-seg-entries (bit 5) shall not be set
          4. ▪ All other bits are agent-specific
      2. b. Mandatory Store-Capacity-Count
        1. attribute-id = MDC_ATTR_METRIC_STORE_CAPAC_CNT
        2. attribute-type = INT-U32
        3. attribute-value.length = 4 bytes
        4. attribute-value = See relation with next attribute
      3. c. Mandatory attribute Store-Usage-Count
        1. attribute-id = MDC_ATTR_METRIC_STORE_USAGE_CNT
        2. attribute-type = INT-U32
        3. attribute-value.length = 4 bytes
        4. attribute-value = consistent with actual number of segments present and always \leq than Storage-Capacity-Count
    | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. Mandatory attribute Operational-State

    • attribute-id = MDC_ATTR_OP_STAT
    • attribute-type = OperationalState
    • attribute-value.length = 2 bytes
    • attribute-value = One of the next
      • ▪ disabled (0x00 0x00)
      • ▪ enabled (0x00 0x01)
      • ▪ notAvailable (0x00 0x02)

    e. If not Recommended attribute Sample-Period is present

    • attribute-id = MDC_ATTR_TIME_PD_SAMP
    • attribute-type = RelativeTime
    • attribute-value.length = 4 bytes
    • attribute-value = <Not relevant in this test>

    f. Mandatory attribute Number-Of-Segments

    • attribute-id = MDC_ATTR_NUM_SEG
    • attribute-type = INT-U16
    • attribute-value.length = 2 bytes
    • attribute-value = <Not relevant in this test>

    g. Mandatory attribute Clear-Timeout

    • attribute-id = MDC_ATTR_CLEAR_TIMEOUT
    • attribute-type = RelativeTime
    • attribute-value.length = 4 bytes
    • attribute-value = <Not relevant in this test>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--------------------| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-015 | | | | +| TP label | PM-Segment Attributes for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | PMStoreObjCGM 4; M | PMStoreObjCGM 5; O | PMStoreObjCGM 6; M | +| | | PMSegObjCGM 2; M | PMSegObjCGM 4; M | PMSegObjCGM 12; M | +| Test purpose |

    Check that:

    PM-Segment objects contain the attributes specified for Extended Configuration.

    [AND]

    A segment holding blood glucose measurements shall be present if a PM-store is implemented.

    [AND]

    The other segments are optional and hold observations from the further objects that are instantiated.

    [AND]

    Each entry shall include one of the time formats in the segm-entry-header so a PHG can correlate entries across the different segments.

    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_041 AND C_AG_OXP_181 | +| Other PICS | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | +| Test procedure |
    1. 1. The simulated PHG shall send a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.
    2. 2. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection = all-segments to indicate the PM-Segments attributes of all available PM-Segments.
    3. 3. The PHD issues a response with the PM-Segment attributes it supports:
      1. a. Mandatory attribute PM-Segment-Entry-Map
        • SegmentEntryHeader.value = One of the next must be set:
          • • seg-elem-hdr-relative-time(1)
          • • seg-elem-hdr-hires-relative-time(2)
          • • seg-elem-hdr-bo-time(3)
        • SegmentEntryElem: <Record the fields for later comparison>
      2. b. Mandatory attribute Segment-Usage-Count
        • attribute-id = MDC_ATTR_SEG_USAGE_CNT
        • attribute-type = INT-U32
        • attribute-value.length = 4 bytes
        • attribute-value = <not relevant in this test>
    4. 4. Repeat for every PM-Segment object
    | +| Pass/Fail criteria |
    • • All checked values are as specified in the test procedure
    • • Every segm-entry-header must contain one of the time formats
    • • At least one PM-Segment must reference the Glucose Numeric object in its PM-Segm-Entry-Map
    • • If there are more PM-Segment objects, the rest of them must reference one of the objects defined in the spec in its PM-Segm-Entry-Map
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-016 | | | +| TP label | PM-Segment Object for Extended Configuration.MDS Event Reports | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | PMStoreObjCGM 3; M | | +| Test purpose | Check that:
    Any configuration with a PM-store for persistent storage shall enable access to the PM-store transmissions. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_041 AND C_AG_OXP_181 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHG shall send a Get request for the PM-Store object with an attribute-
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    id-list set to 0 to indicate all PM-Store attributes.

    2. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection = all-segments to indicate the PM-Segments attributes of all available PM-Segments.

    3. The simulated PHG asks for a measurement.

    4. Check event reports that are sent by the PHD.

    | +| Pass/Fail criteria | In step 4, the PHD shall not send the data with MDS event reports. | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-017 | | | +| TP label | Communication Model: Association Procedure | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | AgProcAsCGM 1; M | AgProcAsCGM 2; M | +| | | AgProcAsCGM 4; M | AgProcAsCGM 5; M | +| | | AgProcAsCGM 7; M | AgProcAsCGM 8; M | +| | | AgProcAsCGM 10; M | AgProcAsCGM 11; M | +| | | AgProcAsCGM 13; O | | +| Test purpose |

    Check that:

    The association procedure data exchange is correct

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 | | | +| Other PICS | C_AG_OXP_002, C_AG_OXP_017 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | +| Test procedure |

    1. The PHD sends a message to associate to the simulated PHG, the expected fields sent by the PHD are:

    a. APDU Type

    • field- type = AarqApdu
    • field-length =2 bytes
    • field-value =0xE2 0x00.

    b. assoc-version

    • field- type = AssociationVersion
    • field-length =BITS-32
    • field- value=0x80 0x00 0x00 0x00 (assoc-version1)

    c. data-proto-id

    • field- type = DataProtoId(INT-U16)
    • field-length =2 bytes
    • field- value=0x50 0x79 (20601)

    d. protocol-version

    • field- type = Protocol Version
    • field-length = 4 bytes
    • field- value= At least bit protocol-version2(1) is set to 1 (0x80 0x00 0x00 0x00)
    | | | + +OR 0x40 0x00 0x00 0x00 OR 0x12 0x00 0x00 0x00) + +#### e. encoding rules + +- field- type = EncodingRules +- field-length = 2 bytes +- field- value= + - Bit 0 must be set (support for MDER) + - Bits 1 (XER) and 2 (PER) may be set + - All other bits must be 0. + +#### f. nomenclature version + +- field- type = NomenclatureVersion +- field-length = 4 bytes +- field- value=0x80 0x00 0x00 0x00 +- This value indicates version1 is supported (nom-version1(0) is set). + +#### g. functional – units + +- field- type = FunctionalUnits +- field-length = 4 bytes + - Bit 0 must be 0. + - Bits 1 and 2 may be set + - The rest of the bits must not be set + +#### h. System type + +- field- type = SystemType +- field-length = 4 bytes +- field- value = 0x00 0x80 0x00 0x00 (sys-type-agent) + +#### i. System-Id + +- field- type = OCTET STRING +- field-length = 8 bytes +- field- value = 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX (octet string length = 8 | UI-64 manufacturer and device ) +- This value will be System Id attribute of MDS Object. + +#### j. dev-config-id + +- field- type = ConfigId(INT-U16) +- field-length = 2 bytes +- field- value = + - 0x09 0xC4 for standard configuration (2500). + - for extended configuration. + +#### k. data-req-mode-flags (DataReqModeCapab) + +- field- type = DataReqModeFlags +- field-length = 2 bytes +- field.value = IF NOT C\_AG\_OXP\_017 -> 0x00 0x01 (data-req-supp-init-agent) + +#### l. data-req-init-agent-count (DataReqModeCapab) + +- field- type = INT-U8 +- field-length = 2 bytes +- field.value = IF NOT C\_AG\_OXP\_017 -> 0x01 + +#### m. data-req-init-manager-count (DataReqModeCapab) + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | field- type = INT-U8
    field-length = 2 bytes
    field.value = IF NOT C_AG_OXP_017 -> 0x00 | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-----------------| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-018 | | | +| TP label | Operating State. PHG to PHD Maximum APDU Size | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 3; M | | +| | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | ComCharCGM 2; M | ComCharCGM 3; M | +| Test purpose | Check that:

    Check that the total size of the response does not exceed of the maximum APDU size established by the specialization

    [AND]

    A CGM PHD implementing only this device specialization shall be capable of receiving any APDU up to the size of Nrx. For this standard, Nrx shall be 224 octets | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 | | | +| Other PICS | C_AG_OXP_041, C_AG_OXP_100 | | | +| Initial condition | The simulated PHG and the PHD are in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHG issues “Remote Operation Invoke Get” command with:
      1. a. Obj-handle set to 0 (to request for MDS object)
      2. b. attribute-id-list.count = 103
      3. c. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 34 times followed by an additional MDC_ATTR_ID_MODEL
    2. 2. Check the response of the PHD.
    3. 3. The simulated PHG issues “Remote Operation Invoke Get” command with handle set to 0 (to request for MDS object) and an empty attribute-id-list to indicate all attributes.
    4. 4. Check the response of the PHD.
    | | | +| Pass/Fail criteria |
    • • In step 2, the PHD under test may respond with a rors-cmip-get listing all the requested attributes, or with a roer message. If PICS C_AG_OXP_100 = TRUE and PHD does not respond with a rors-cmip-get message, and it responds with a roer message or roj(resource-limitation) message, a WARNING will appear.
      • ○ If the response is a get response, the total size of the response can not exceed the following APDU sizes:
        • ▪ Continuous Glucose Monitor without PM-Store -> 896 octets
        • ▪ Continuous Glucose Monitor with PM-Store -> 5120 octets
      • ○ In case it responds with a roer, the reason must not be protocol-violation (23)
    • • In step 4, the PHD must respond with a rors-cmip-get message.
    | | | + +| | | +|--------------|--| +| Notes | | +|--------------|--| + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-019 | | | +| TP label | Glucose measurement above the capabilities of the device sensor | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | Glucose 25; M | | +| Test purpose | Check that:
    For a CGM PHD with standard configuration, a glucose measurement that is above the capabilities of the device sensor shall be indicated with an observed value of +INFINITY | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND (NOT C_AG_OXP_181) | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Place in the device sensor a blood sample with a blood glucose level above the capabilities of the device sensor and acquire a measurement with the PHD under test.
    2. Test Tool simulated PHG waits to receive an event report from the PHD under test. The event report shall contain the following value:
    a. Data APDU
    event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)
    obj-handle = 1 (1st Measurement is Glucose)
    obs-val-data =
    • • Basic-Nu-Observed-Value = 0x07FE (+INFINITY)
    • • Base-Offset-Time-Stamp = <Not relevant for this Test Case>
    | | | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | | | +| Notes | Vendor must provide a blood sample (or a simulated blood glucose solution) with a glucose level above the capabilities of the device sensor. | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-020 | | | +| TP label | Glucose measurement below the capabilities of the device sensor | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | Glucose 26; M | | +| Test purpose | Check that:
    For a CGM PHD with standard configuration, a glucose measurement that is below the capabilities of the device sensor shall be indicated with an observed value of -INFINITY | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND (NOT C_AG_OXP_181) | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Place in the device sensor a blood sample with a blood glucose level below the | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    capabilities of the device sensor and acquire a measurement with the PHD under test.

    2. Test Tool simulated PHG waits to receive an event report from the PHD, under test. The even report shall contain the following value:

    a. Data APDU

    • event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)
    • obj-handle = 1 (1st Measurement is Glucose)
    • obs-val-data =
      • • Basic-Nu-Observed-Value = 0x0802 (-INFINITY)
      • • Base-Offset-Time-Stamp = <Not relevant for this Test Case>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Vendor must provide a blood sample (or a simulated blood glucose solution) with a glucose level below the capabilities of the device sensor. | + +| | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-021 | | +| TP label | Set Time (Absolute Time) Continuous Glucose Monitor | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | +| | Testable items | MDSMethodsCGM 1; M | +| Test purpose |

    Check that:

    If the PHD supports the [Absolute-Time-Stamp] attribute, the Set -Time method shall be implemented

    | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_155 AND C_AG_OXP_009 | | +| Other PICS | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | +| Test procedure |

    1. The simulated PHG sends a SET action:

    • CHOICE = SetTimeInvoke
    • action-type = MDC_ACT_SET_TIME
    • the action-info-args are SetTimeInvoke
      • ▪ date-time = <century, year ≤ 99, month ≤ 12, day ≤ 31, hour ≤ 24, minute ≤ 60, second ≤ 60, sec-fractions ≤ 100>
      • ▪ accuracy = 0

    2. The PHD under test response shall be a rors-cmip-confirmed-action:

    • action-type = MDC_ACT_SET_TIME
    • action-info-args shall be empty.
    | | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | | +| Notes | | | + +| | | | +|-----------------|--------------------------------------------------------|------------------------| +| TP Id | TP/PLT/AG/CLASS/CGM/BV-022 | | +| TP label | Set Time (Base Offset Time) Continuous Glucose Monitor | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--|--| +| | Testable items | MDSMethodsCGM 2; M | | | +| Test purpose | Check that:
    If the PHD supports the [Base-Offset-Time-Stamp] attribute, the Set-Base-Offset-Time method shall be implemented | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_157 AND C_AG_OXP_014 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure | 1. The simulated PHG sends a SET action:
    • CHOICE = SetBOTimeInvoke
    • action-type = MDC_ACT_SET_BO_TIME
    • the action-info-args are SetBOTimeInvoke
      • ▪ date-time = bo-seconds = 0x00 0x00 0x00 0x00, bo-fractions = 0x00 0x00, bo-time-offset = 0x3C
    2. The PHD under test response shall be a rors-cmip-confirmed-action:
    • action-type = MDC_ACT_SET_BO_TIME
    • action-info-args shall be empty.
    | | | | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | | | | +| Notes | | | | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. +- [b-PHD PICS & PIXIT] Personal Health Device DG2016 PICS and PIXIT excel sheet v1.11. + +- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9. + +- [b-TCRL] Test Case Reference List\_DG2016\_v1.11. + +- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.845.17-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.845.17-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36aea427f866a61784190c24d32ec0bcde125b5f --- /dev/null +++ b/marked/H/T-REC-H.845.17-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c943614f40ce1fe046b26d3fc8f2f40eb61fcb30133618cb532fb6603ded9709 +size 4267 diff --git a/marked/H/T-REC-H.845.17-201911-I_PDF-E/raw.md b/marked/H/T-REC-H.845.17-201911-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7af32c276fdf11617fa6087439638b564f60f7a6 --- /dev/null +++ b/marked/H/T-REC-H.845.17-201911-I_PDF-E/raw.md @@ -0,0 +1,954 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.845.17** + +(11/2019) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface Part +5Q: Power status monitor** + +Recommendation ITU-T H.845.17 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.845.17 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5Q: Power status monitor + +## Summary + +Recommendation ITU-T H.845.17 provides a test suite structure (TSS) and the test purposes (TPs) for the power status monitor (PSM) of personal health devices in the Personal Health Device (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2017) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.845.17 | 2018-08-29 | 16 | 11.1002/1000/13683 | +| 2.0 | ITU-T H.845.17 | 2019-11-29 | 16 | 11.1002/1000/14118 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, Personal Health Devices interface, personal area network, personal connected health devices, touch area network, IEEE 11073 device specialization, power status monitor. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Test suite structure..... | 5 | +| 7 Electronic attachment ..... | 7 | +| Annex A Test purposes ..... | 8 | +| A.1 Test purpose definition conventions..... | 8 | +| A.2 Subgroup 1.3.17: Power status monitor (PSM)..... | 10 | +| Bibliography..... | 34 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# Introduction + +| Version | Date | Revision history | +|----------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2018-02-27 | Initial release for the inclusion of the Power Status Monitor of Personal Health Devices device specialization (ISO/IEEE 11073-10427:2018) | +| 1.1 | 2018-10-17 | Updates due to the inclusion of the Power Status Monitor of Personal Health Devices device specialization (ISO/IEEE 11073-10427:2018) test cases | +| 1.2 | 2019-06-13 | Second maintenance release for Test Tool DG2017. It uses ITU-T H.845.17 (08/2018) as a baseline and adds some updates according to the 2018/2019 maintenance activity. | + +# Recommendation ITU-T H.845.17 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5Q: Power status monitor + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TPs) for the Personal Health Devices interface based on the requirements defined in Continua Design Guidelines (CDG) [ITU-T H.810 (2017)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TPs for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 5, subpart 5Q. + +- Part 1: Optimized Exchange Protocol. Personal Health Device +- Part 2: Optimized Exchange Protocol. Personal Health Gateway +- Part 3: Continua Design Guidelines. Personal Health Device +- Part 4: Continua Design Guidelines. Personal Health Gateway +- Part 5: Device Specializations. Personal Health Device. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak flow + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) + - **Part 5Q: Power status monitor (PSM)** +- Part 6: Device Specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. Personal Health Device BLE +- Part 8: Continua Design Guidelines. Personal Health Gateway BLE + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 9: Personal Health Devices Transcoding White paper. Personal Health Device +- Part 10: Personal Health Devices Transcoding White paper. Personal Health Gateway + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2017)] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal connected health systems: Introduction*. +- [ISO/IEEE 11073-10427] ISO/IEEE 11073-10427:2018, *Health informatics – Personal health device communication – Part 10427: Device specialization – Power status monitor of personal health devices*. +. Same publication as +. +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol, including ISO/IEEE 11073-20601:2016/Cor.1:2016*. + with + + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. +- 3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|--------------------------------| +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| INR | International Normalized Ratio | +| IP | Insulin Pump | + +| | | +|-------|-------------------------------------------------------| +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PHD | Personal Health Device | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| PSM | Power Status Monitor | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this document are to be interpreted as in [b-ETSI SR 001 262] + +- SHALL is equivalent to: MUST; or it is required to. +- SHALL NOT is equivalent to: MUST NOT or it is not allowed +- SHOULD is equivalent to: it is recommended to +- SHOULD NOT is equivalent to: it is not recommended to +- MAY is equivalent to: is permitted +- MAY NOT is equivalent to: it is not required that + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Generic reference to the ITU-T H.810 series is made through the label [ITU-T H.810 series], as listed in clause 2. + +Reference is made in the ITU-T H.820-H.850-series of Recommendations to different versions of the CDG by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2017 | - | 7.0 | Release 2017 of the CDG including maintenance updates of the CDG 2016 and additional guidelines that cover new functionalities. | – | +| 2016 plus errata | [b-ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure + +The TPs for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 1.3.17 (shown in bold): + +The TPs have been divided into two main groups: + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601: Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - **Subgroup 1.3.17: Power status monitor (PSM)** + - Group 1.4: Personal Health Device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + +- Subgroup 1.4.2: Whitepaper thermometer requirements (TH) +- Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601: Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) + - Subgroup 2.3.17: Power status monitor (PSM) + +- Group 2.4: Personal Health Device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 2.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICSs) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . See [b-PHD PICS & PIXIT], [b-PHG PICS & PIXIT] and [b-TI]. + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICSs" and "PIXIT", respectively, during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICSs, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 Test purpose definition conventions + +The TPs are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each TP identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth low energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: valid behaviour test + - BI: invalid behaviour test + - : This is a sequential number that identifies the TP. +- **TP label:** This is the title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable Item: This contains testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if a test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the DUT within that scope of the test (specialization, transport used, etc.). +- **Other PICSs:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row is used within the test case implementation. + +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 1.3.17: Power status monitor (PSM) + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-000_A | | | +| TP label | Get MDS Object for Power Status Monitor specialization: Mandatory, Conditional and Optional Attributes. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | MDSAttrPSM 2; NR | MDSAttrPSM 3; M | +| | | MDSAttrPSM 6; M | MDSAttrPSM 7; M | +| | | MDSAttrPSM 16; M | MDSAttrPSM 17; M | +| | | Capacity 55; M | Capacity 56; M | +| | | SimplePSMProf 2; M | SimplePSMProf 3; M | +| | | AdvPSMProf 4; M | AdvPSMProf 5; M | +| Test purpose | Check that:
    The MDS Object contains the attributes specified for a Power Status Monitor agent | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_155 OR C_AG_OXP_156) | | | +| Other PICs | C_AG_OXP_181 | | | +| Initial condition | The simulated Personal Health Gateway (PHG) and Personal Health Device (PHD) under test are in Operating State. | | | +| Test procedure |
    1. 1. The PHD reports values of its objects as a new association has already been established.
    2. 2. The PHG saves the value of the [Compound-Nu-Observed-Value] of all the Battery Capacity objects of the PHD.
    3. 3. The simulated PHG issues "roiv-cmip-get" command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    4. 4. The PHD responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object:
      MDS Attributes:
      1. a. System-Type attribute shall not be present (as System-Type-Spec-List attribute is mandatory)
      2. b. Mandatory attribute System-Type-Spec-List
        • attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST
        • attribute-type = TypeVerList
        • attribute-value.length = 4 bytes for each configuration supported
        • attribute-value = {MDC_DEV_SPEC_PROFILE_PSM, 1} and
          • • IF C_AG_OXP_155 THEN {MDC_DEV_SUB_SPEC_PROFILE_EIGHT_OR_LESS_BATTERIES, 1}
          • • IF C_AG_OXP_156 THEN {MDC_DEV_SUB_SPEC_PROFILE_MORE_THAN_EIGHT_BATTERIES, 1}
      3. c. Mandatory attribute System-model
        • attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)
        • attribute-type = SystemModel
        • attribute-value.length = <Variable>
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value =
      • • Manufacturer = Check against PIXIT I_AG_OXP_003
      • • Model = Check against PIXIT I_AG_OXP_004

    d. Mandatory attribute Dev-Configuration-Id

    • attribute-id = MDC_ATTR_DEV_CONFIG_ID
    • attribute-type = ConfigId
    • attribute-value.length = 2 bytes
    • attribute-value =
      • • IF (NOT C_AG_OXP_181) AND (C_AG_OXP_155) then attribute-value = 0x0A8C OR 0x0A8D OR 0x0A8E OR 0x0A8F OR 0x0A90 OR 0x0A91 OR 0x0A92 OR 0x0A93
      • • ELSE attribute-value = < between 0x4000 and 0x7FFF>

    e. If recommended attribute Base-Offset-Time is present

    • attribute-id = MDC_ATTR_TIME_BO (0x0A 0x81)
    • attribute-type = BaseOffsetTime
    • attribute-value.length = 8 bytes
    • attribute-value = <not relevant>

    f. Mandatory attribute Power-Status

    • attribute-id = MDC_ATTR_POWER_STAT
    • attribute-type = PowerStatus (BITS-16)
    • attribute-value.length = 2 bytes
    • attribute-value =
      • • ON_BATTERY(0x4000)
      • • ON_MAINS (0x8000)

    g. Mandatory attribute Battery-Level

    • attribute-id = MDC_ATTR_VAL_BATT_CHARGE (0X09 0X9C)
    • attribute-type = INT-U16
    • attribute-value.length = 2 bytes
    • attribute-value = the summation of the remaining capacities of each battery (obtained in step 2) divided by the summation of the current full charge capacities of each battery expressed as a percentage

    h. Mandatory Remain-Battery-Time

    • attribute-id = MDC_ATTR_TIME_BATT_REMAIN (0X09 0X88)
    • attribute-type = BatMeasure
    • attribute-value.length = 6 bytes
    • attribute-value = the sum of the remaining battery time of all the batteries of the device, obtained in step 2.
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | +|-----------------|---------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-000_B | | +| TP label | MDS Configuration objects events for Power Status Monitor specialization. | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--|--| +| | Testable items | MDSEventsPSM 1; M | | | +| Test purpose |

    Check that:

    A Power Status Monitor agent shall send the [MDS-Configuration-Event] using a [Confirmed] event report.

    The [MDS-Configuration-Event] shall include the event-info [ConfigReport]

    | | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_155 OR C_AG_OXP_156) | | | | +| Other PICs | C_AG_OXP_010, C_AG_OXP_181 | | | | +| Initial condition | The simulated PHG and PHD under test are in Unassociated State. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG:
      1. a. APDU Type
        1. field- type = PrstApdu
        2. field-length =2 bytes
        3. field-value =0xE7 0x00
      2. b. invoke-id
        1. field- type = InvokeIDType
        2. field-length =INT-U16
        3. field- value =<Not relevant for this test>
      3. c. message
        1. field- type = roiv-cmip-confirmed-event-report
        2. field-length =two bytes
        3. field- value =0x01 0x01 (EventReportArgumentSimple)
      4. d. obj-handle (EventReportArgumentSimple)
        1. field- type = HANDLE
        2. field-length =INT-U16
      5. e. event-time (EventReportArgumentSimple)
        1. field- type = Relative Time
        2. field-length =INT-U32
        3. field-value =
          • • IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF
      6. f. event-type (EventReportArgumentSimple)
        1. field- type = OID-Type
        2. field-length =INT-U16
        3. field- value=0x0D 0x1C (MDC_NOTI_CONFIG)
      7. g. config-report-id (ConfigReport)
        1. field- type = ConfigId
        2. field-length = INT-U16
        3. field value = <It matches the tested configuration>
          • • IF NOT C_AG_OXP_181 THEN attribute-value = 0x0A8C (2700) OR 0x0A8D (2701) OR 0x0A8E (2702) OR 0x0A8F (2703) OR 0x0A90 (2704) OR 0x0A91 (2705) OR 0x0A92 (2706) OR 0x0A93 (2707)
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ELSE attribute-value = <between 0x40 0x00 and 0x7F 0xFF > for extended configuration.

    h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject))

    • field- type = OID-Type
    • field-length = INT-U16
    • field- value = At least one MDC_MOC_VMO_METRIC_NU
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-000_C | | | +| TP label | MDS objects events for Power Status Monitor specialization. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | MDSEventsPSM 3; M | MDSEventsPSM 4; M | +| | | MDSEventsPSM 6; M | ObjAccServPSM 1; M | +| | | | MDSEventsPSM 5; M | +| | | | ObjAccServPSM 2; M | +| Test purpose |

    Check that:

    MDS Event reports shall be used in confirmed mode

    [AND]

    Agent-initiated mode shall be supported for measurement data transmission

    [AND]

    A Power Status Monitor PHD shall send the [MDS-Dynamic-Data-Update-Fixed] using a [Confirmed] event report. The [MDS-Dynamic-Data-Update-Fixed] shall include the event-info [ScanReportInfoFixed]

    [AND]

    A Continuous Glucose Monitor PHD shall send the [MDS-Dynamic-Data-Update-Var] using a [Confirmed] event report. The [MDS-Dynamic-Data-Update-Var] shall include the event-info [ScanReportInfoVar]

    | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_155 OR C_AG_OXP_156) AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_189) | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and PHD under test are in Operating State. | | | +| Test procedure |
    1. The PHD reports values of its objects as a new association has been established.
    2. Check:
      1. APDU Type
        • field- type = Event Report
        • field-length = 2 bytes
        • field- value=0x01 0x01 (EventReportArgumentSimple, confirmed)

        This field identifies the type of message sent by the PHD, for the confirmed event configuration, roiv-cmip-confirmed-event-report.

    | | | +| Pass/Fail criteria |

    Check that every received report is one of the following confirmed Data APDU

    • MDC_NOTI_SCAN_REPORT_FIXED
    • MDC_NOTI_SCAN_REPORT_VAR
    | | | + +| | | +|--------------|--| +| Notes | | +|--------------|--| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-001 | | | +| TP label | Objects for Power Status Monitor specialization - Standard Configurations | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | Capacity 1; M | BattStatus 1; M | +| Test purpose |

    Check that:

    The Battery Capacity Numeric object with Type {MDC_PART_PHD_DM MDC_BATTERY_CAPACITY} is supported by a Power Status Monitor PHD with Standard Configurations 0x0A8C (2700) OR 0x0A8D (2701) OR 0x0A8E (2702) OR 0x0A8F (2703) OR 0x0A90 (2704) OR 0x0A91 (2705) OR 0x0A92 (2706) OR 0x0A93 (2707).

    [AND]

    The Battery Capacity Numeric object is present as many times as required by the [Dev-Configuration-Id] attribute value

    [AND]

    The Battery Status Enumeration object with Type {MDC_PART_PHD_DM MDC_BATTERY_STATUS} is supported by a Power Status Monitor PHD with Standard Configurations 0x0A8C (2700) OR 0x0A8D (2701) OR 0x0A8E (2702) OR 0x0A8F (2703) OR 0x0A90 (2704) OR 0x0A91 (2705) OR 0x0A92 (2706) OR 0x0A93 (2707).

    [AND]

    The Battery Status Enumeration object is present as many times as required by the [Dev-Configuration-Id] attribute value

    [AND]

    No more objects are supported by a Power Status Monitor (PSM) PHD with Standard Configurations 0x0A8C (2700) OR 0x0A8D (2701) OR 0x0A8E (2702) OR 0x0A8F (2703) OR 0x0A90 (2704) OR 0x0A91 (2705) OR 0x0A92 (2706) OR 0x0A93 (2707).

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_155 AND (NOT_C_AG_OXP_181) | | | +| Other PICSs | | | | +| Initial condition | The simulated PHG and PHD are in Unassociated State. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG
    4. 4. Check that the field Dev-Config-Id is set to 0x0A8C (2700) OR 0x0A8D (2701) OR 0x0A8E (2702) OR 0x0A8F (2703) OR 0x0A90 (2704) OR 0x0A91 (2705) OR 0x0A92 (2706) OR 0x0A93 (2707). if it is not, PHG responds with a "unsupported-config" and waits for a new configuration
    5. 5. Once the PHD under test sends a standard configuration, Check that:
      Attribute-List:
      1. a. attribute-value (ConfigReport → ConfigObjectList (ConfigObject) → Attribute List), this value depends on the attribute Type. Values to be checked are:
        • • The Battery Capacity Numeric object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_CAPACITY (0x74 0xCC), and
          • • IF the [Dev-Configuration-Id] attribute is 0x0A8C (2700) the Battery Capacity Numeric object is present once
          • • IF the [Dev-Configuration-Id] attribute is 0x0A8D (2701) the Battery
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Capacity Numeric object is present twice

    • • IF the [Dev-Configuration-Id] attribute is 0x0A8E (2702) the Battery Capacity Numeric object is present three times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A8F (2703) the Battery Capacity Numeric object is present four times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A90 (2704) the Battery Capacity Numeric object is present five times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A91 (2705) the Battery Capacity Numeric object is present six times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A92 (2706) the Battery Capacity Numeric object is present seven times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A93 (2707) the Battery Capacity Numeric object is present eight times

    The Battery Status Enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_STATUS (0x74 0xD0), and

    • • IF the [Dev-Configuration-Id] attribute is 0x0A8C (2700) the Battery Status Enumeration object is present once
    • • IF the [Dev-Configuration-Id] attribute is 0x0A8D (2701) the Battery Status Enumeration object is present twice
    • • IF the [Dev-Configuration-Id] attribute is 0x0A8E (2702) the Battery Status Enumeration object is present three times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A8F (2703) the Battery Status Enumeration object is present four times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A90 (2704) the Battery Status Enumeration object is present five times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A91 (2705) the Battery Status Enumeration object is present six times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A92 (2706) the Battery Status Enumeration object is present seven times
    • • IF the [Dev-Configuration-Id] attribute is 0x0A93 (2707) the Battery Status Enumeration object is present eight times
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure and no other object is listed. | +| Notes | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-002 | | | +| TP label | Objects for Power Status Monitor specialization - Extended Configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | Capacity 3; M | BattStatus 2; M | +| | | AdvPSMProf 2; M | AdvPSMProf 6; M | +| | | MDSAttrPSM 3; M | Capacity 8; M | +| Test purpose |

    Check that:

    The Battery Capacity Numeric object with Type {MDC_PART_PHD_DM MDC_BATTERY_CAPACITY} is supported by a Power Status Monitor PHD with Extended Configuration.

    [AND]

    The Battery Status Enumeration object with Type {MDC_PART_PHD_DM MDC_BATTERY_STATUS} is supported by a Power Status Monitor PHD with Extended

    | | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Configuration

    [AND]

    There are the same number of Battery Capacity and Battery Status objects, which ranges from 1 to 16

    [AND]

    The number of Battery Capacity and Battery Status objects is coherent with the device profile and the MDS System-Type-Spec-List attribute

    [AND]

    If a Battery Status Enumeration object is placed in recommended handle (2i), where "i" is the battery number, then it is recommended that its Supplemental Type attribute value is the same to that in the Battery Capacity Numeric object in recommended handle (2i-1)

    | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_155 OR C_AG_OXP_156) AND C_AG_OXP_181 | +| Other PICs | C_AG_OXP_155, C_AG_OXP_156 | +| Initial condition | The simulated PHG and PHD are in Unassociated State. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG
    4. 4. Check that the field Dev-Config-Id is in the extended range; if it is not, PHG responds with a "unsupported-config" and waits for a new configuration
    5. 5. Once the PHD under test sends an extended configuration and a measurement, Check that:
      Attribute-List:
      1. a. attribute-value( ConfigReport → ConfigObjectList (ConfigObject)→Attribute List), this value depends on the attribute type. The values we have to check are:
        • The Battery Capacity object is present at least once→ MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_CAPACITY (0x74 0xCC).
        • The Battery Status enumeration object is present at least once→ MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_STATUS (0x74 0xD0)
        • There is the same number of Battery Capacity and Battery Status object, equal to the number of supported batteries.
    6. 6. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    7. 7. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    8. 8. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    9. 9. IF C_AG_OXP_155, check that:
      • The number of supported batteries is equal or less than eight
      • System-Type-Spec-List MDS attribute is {MDC_DEV_SPEC_PROFILE_PSM, 1} and {MDC_DEV_SUB_SPEC_PROFILE_EIGHT_OR_LESS_BATTERIES, 1}
      IF C_AG_OXP_156, check that:
      • The number of supported batteries is more than eight and less than sixteen
      • System-Type-Spec-List MDS attribute is {MDC_DEV_SPEC_PROFILE_PSM, 1} and {MDC_DEV_SUB_SPEC_PROFILE_EIGHT_OR_LESS_BATTERIES, 1}
    10. 10. Check if the Supplemental-Types attribute values of Battery Capacity objects with handle
    | + +| | | +|---------------------------|-----------------------------------------------------------------| +| | (2i) matches those of Battery Status objects with handle (2i-1) | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-003 | | | | +| TP label | Battery Capacity Numeric Object - Standard configurations | | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | | +| | Testable items | Capacity 2; M | Capacity 5; M | Capacity 7; M | +| | | Capacity 9; M | Capacity 11; NR | Capacity 13; NR | +| | | Capacity 15; NR | Capacity 17; NR | Capacity 19; NR | +| | | Capacity 21; NR | Capacity 23; NR | Capacity 25; NR | +| | | Capacity 27; NR | Capacity 31; NR | Capacity 33; NR | +| | | Capacity 35; M | Capacity 37; NR | Capacity 39; NR | +| | | Capacity 41; NR | Capacity 43; NR | Capacity 45; NR | +| | | Capacity 47; NR | Capacity 49; NR | Capacity 51; M | +| | | Capacity 53; NR | Capacity 57; M | Capacity 58; M | +| Test purpose | Check that:
    The Battery Capacity Numeric object contains the attributes specified for the Standard Configurations. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_155 AND (NOT C_AG_OXP_181) | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and PHD under are in Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG
    3. 3. Check that the field Dev-Config-Id is set to 0x0A8C (2700) OR 0x0A8D (2701) OR 0x0A8E (2702) OR 0x0A8F (2703) OR 0x0A90 (2704) OR 0x0A91 (2705) OR 0x0A92 (2706) OR 0x0A93 (2707). If it is not, PHG responds with a "unsupported-config" and waits for a new configuration
    4. 4. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    5. 5. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    6. 6. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    7. 7. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test using MDS-Dynamic-Data-Update-Var
    | | | | + +8. Once the PHD under test sends a standard configuration and a measurement, check that the Battery Capacity Numeric Object attributes are: + +a. Mandatory attribute Handle + +attribute-id = MDC\_ATTR\_ID\_HANDLE + +attribute-type = HANDLE + +attribute-value = + +- IF the Dev-Config-Id is 0x0A8C (2700): 0x00 0x01 +- IF the Dev-Config-Id is 0x0A8D (2701): 0x00 0x01 OR 0x00 0x03 +- IF the Dev-Config-Id is 0x0A8E (2702): 0x00 0x01 OR 0x00 0x03 OR 0x00 0x05 +- IF the Dev-Config-Id is 0x0A8F (2703): 0x00 0x01 OR 0x00 0x03 OR 0x00 0x05 OR 0x00 0x07 +- IF the Dev-Config-Id is 0x0A90 (2704): 0x00 0x01 OR 0x00 0x03 OR 0x00 0x05 OR 0x00 0x07 OR 0x00 0x09 +- IF the Dev-Config-Id is 0x0A91 (2705): 0x00 0x01 OR 0x00 0x03 OR 0x00 0x05 OR 0x00 0x07 OR 0x00 0x09 OR 0x00 0x0B +- IF the Dev-Config-Id is 0x0A92 (2706): 0x00 0x01 OR 0x00 0x03 OR 0x00 0x05 OR 0x00 0x07 OR 0x00 0x09 OR 0x00 0x0B OR 0x00 0x0D +- IF the Dev-Config-Id is 0x0A93 (2707): 0x00 0x01 OR 0x00 0x03 OR 0x00 0x05 OR 0x00 0x07 OR 0x00 0x09 OR 0x00 0x0B OR 0x00 0x0D OR 0x00 0x0F + +b. Mandatory attribute Type + +attribute-id = MDC\_ATTR\_ID\_TYPE + +attribute-type = TYPE + +attribute-value = MDC\_PART\_PHD\_DM (128 / 0x0080) | +MDC\_BATTERY\_CAPACITY (29900 / 0x74CC) + +c. Mandatory attribute Supplemental-Types + +attribute-id = MDC\_ATTR\_ID\_TYPE + +attribute-type = MDC\_ATTR\_SUPPLEMENTAL\_TYPES + +attribute-value.length = SEQUENCE OF (SIZE (4) ) + +attribute-value = + +- IF Handle value= 1 { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_BATTERY\_1 (29912 / 0x74D8) } +- IF Handle value= 3 { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_BATTERY\_2 (29920 / 0x74E0) } +- IF Handle value= 5 { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_BATTERY\_3 (29928 / 0x74E8) } +- IF Handle value= 7 { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_BATTERY\_4 (29936 / 0x74F0) } +- IF Handle value= 9 { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_BATTERY\_5 (29944 / 0x74F8) } +- IF Handle value= 11 { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_BATTERY\_6 (29952 / 0x7500) } +- IF Handle value= 13 { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_BATTERY\_7 (29960 / 0x7508) } +- IF Handle value= 15 { MDC\_PART\_PHD\_DM (0x00 0x80), +MDC\_BATTERY\_8 (29968 / 0x7510) } + +d. Mandatory attribute Metric-Spec-Small + +attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = MetricSpecSmall (BITS-16)
    • attribute-value.length = 2 bytes
    • attribute-value ≠ 0x00 0x00
      • • Bit 0 (mss-avail-intermittent(0)) must be set
      • • Bit 2 (mss-upd-aperiodic(2)) must be set
      • • Bit 3 (mss-msmt-aperiodic(3)) must be set
      • • Bit 9 (mss-acc-agent-initiated(9)) must be set
      • • Rest shall be set to 0.

    e. Mandatory attribute Base-Offset-Time-Stamp

    • attribute-id = MDC_ATTR_TIME_STAMP_BO
    • attribute-type = BaseOffsetTime
    • attribute-value.length = 8 bytes

    f. Mandatory attribute Compound-Nu-Observed-Value

    • attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS
    • attribute-type = NuObsValueCmp
    • attribute-value.length = <not relevant in this test>
    • attribute-value = <not relevant in this test>

    g. Not recommended attributes should not be present at configuration

    h. No other attribute shall be present at configuration

    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-004 | | | +| TP label | Battery Capacity Numeric Object - Extended configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | Capacity 4; R | Capacity 6; M | +| | | Capacity 12; NR | Capacity 14; NR | +| | | Capacity 18; NR | Capacity 20; NR | +| | | Capacity 24; NR | Capacity 26; NR | +| | | Capacity 32; NR | Capacity 34; NR | +| | | Capacity 38; NR | Capacity 40; NR | +| | | Capacity 42; NR | Capacity 46; NR | +| | | Capacity 50; NR | Capacity 52; M | +| | | Capacity 57; M | Capacity 58; M | +| Test purpose | Check that:
    The Battery Capacity Numeric object contains the attributes specified for the Standard Configurations. | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_155 OR C_AG_OXP_156) AND C_AG_OXP_181 | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICs | | +| Initial condition | The simulated PHG and PHD under are in Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with "unsupported-config" and waits for a new configuration.
    4. 4. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    5. 5. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    6. 6. IF the mds-time-mgr-set-time bit is set:
      1. The PHG moves to Configuring/Sending Set Time substate and it issues the Set-Base-Offset-Time action command.
      2. Once its internal time setting operation is completed, the PHD responds to the PHG.
    7. 7. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test using MDS-Dynamic-Data-Update-Var.
    8. 8. Once the PHD under test sends a standard configuration and a measurement, check that the Battery Capacity Numeric Object attributes are:
      1. a. Mandatory attribute Handle
        1. attribute-id = MDC_ATTR_ID_HANDLE
        2. attribute-type = HANDLE
      2. b. attribute-value = recommended value is (2i-1) for each battery i, where i can take on value 1...n where n is the maximum number of batteries that can be present in the agent
      3. c. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_PHD_DM (128 / 0x0080) MDC_BATTERY_CAPACITY (29900 / 0x74CC)
      4. d. Mandatory attribute Supplemental-Types
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = MDC_ATTR_SUPPLEMENTAL_TYPES
        3. attribute-value.length = SEQUENCE OF (SIZE (4) )
          attribute-value =
          { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_1 (29912 / 0x74D8)}
          OR
          { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_2 (29920 / 0x74E0)}
          OR
          { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_3 (29928 / 0x74E8)}
          OR
          { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_4 (29936 / 0x74F0)}
          OR
          { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_5 (29944 / 0x74F8)}
          OR
          { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_6 (29952 / 0x7500)}
          OR
          { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_7 (29960 / 0x7508)}
          OR
          { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_8 (29968 / 0x7510)}
          OR
          { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_9 (29976/ 0x7518)}
    | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    OR
    { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_10 (29984/ 0x7520)}
    OR
    { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_11 (29992/ 0x7528)}
    OR
    { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_12 (30000/ 0x7530)}
    OR
    { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_13 (30008/ 0x7438)}
    OR
    { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_14 (30016/ 0x7540)}
    OR
    { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_15 (30024/ 0x7548)}
    OR
    { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_16 (30032/ 0x7550)}

    The "i" in MDC_BATTERY_i shall be ((value of the handle attribute)+1)/2

    e. Mandatory attribute Base-Offset-Time-Stamp

    • attribute-id = MDC_ATTR_TIME_STAMP_BO
    • attribute-type = BaseOffsetTime
    • attribute-value.length = 8 bytes

    f. Mandatory attribute Compound-Nu-Observed-Value

    • attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS
    • attribute-type = NuObsValueCmp
    • attribute-value.length = <not relevant in this test>
    • attribute-value = <not relevant in this test>

    g. Not recommended attributes should not be present at configuration

    h. No other attribute shall be present at configuration

    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-005 | | | +| TP label | Battery Status Enumeration Object - Standard configurations | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 3; M | BattStatus 7; M | +| | | BattStatus 11; M | BattStatus 17; NR | +| | | BattStatus 21; NR | BattStatus 23; NR | +| | | BattStatus 27; NR | BattStatus 29; NR | +| | | BattStatus 37; M | BattStatus 39; NR | +| | | BattStatus 43; NR | BattStatus 45; NR | +| | | BattStatus 49; M | BattStatus 51; NR | +| | | BattStatus 55; NR | BattStatus 57; M | +| | | BattStatus 61; M | BattStatus 62; M | +| Test purpose | Check that:
    The Battery Status Enumeration Object contains the attributes specified for Standard Configurations. | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_AG_OXP_000 AND C_AG_OXP_155 AND NOT C_AG_OXP_181 | +| Other PICS | C_AG_OXP_183, C_AG_OXP_189 | +| Initial condition | The simulated PHG and PHD under test are in Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG
    3. 3. Check that the field Dev-Config-Id is set to 0x0A8C (2700) OR 0x0A8D (2701) OR 0x0A8E (2702) OR 0x0A8F (2703) OR 0x0A90 (2704) OR 0x0A91 (2705) OR 0x0A92 (2706) OR 0x0A93 (2707). If it is not, PHG responds with a "unsupported-config" and waits for a new configuration
    4. 4. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    5. 5. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    6. 6. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    7. 7. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test using MDS-Dynamic-Data-Update-Var or MDS-Dynamic-Data-Update-Fixed
    8. 8. Once the PHD under test sends an extended configuration and a measurement, check that the Battery Status Enumeration Object attributes are:
      1. a. Mandatory attribute Handle
        • attribute-id = MDC_ATTR_ID_HANDLE
        • attribute-type = HANDLE
        • attribute-value =
          • • IF the Dev-Config-Id is 0x0A8C (2700): 0x00 0x02
          • • IF the Dev-Config-Id is 0x0A8D (2701): 0x00 0x02 OR 0x00 0x04
          • • IF the Dev-Config-Id is 0x0A8E (2702): 0x00 0x02 OR 0x00 0x04 OR 0x00 0x06
          • • IF the Dev-Config-Id is 0x0A8F (2703): 0x00 0x02 OR 0x00 0x04 OR 0x00 0x06 OR 0x00 0x08
          • • IF the Dev-Config-Id is 0x0A90 (2704): 0x00 0x02 OR 0x00 0x04 OR 0x00 0x06 OR 0x00 0x08 OR 0x00 0x0A
          • • IF the Dev-Config-Id is 0x0A91 (2705): 0x00 0x02 OR 0x00 0x04 OR 0x00 0x06 OR 0x00 0x08 OR 0x00 0x0A OR 0x00 0x0C
          • • IF the Dev-Config-Id is 0x0A92 (2706): 0x00 0x02 OR 0x00 0x04 OR 0x00 0x06 OR 0x00 0x08 OR 0x00 0x0A OR 0x00 0x0C OR 0x00 0x0E
          • • IF the Dev-Config-Id is 0x0A93 (2707): 0x00 0x02 OR 0x00 0x04 OR 0x00 0x06 OR 0x00 0x08 OR 0x00 0x0A OR 0x00 0x0C OR 0x00 0x0E OR 0x00 0x10
      2. b. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_DM (128 / 0x0080) MDC_BATTERY_STATUS (29904 / 0x74D0)
      3. c. Mandatory attribute Supplemental-Types
    | + +- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES +- attribute-type = SupplementalTypeList +- attribute-value.length = SEQUENCE OF (SIZE (4) ) +- attribute-value = + - IF Handle value= 2 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_1 (29912 / 0x74D8) } + - IF Handle value= 4 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_2 (29920 / 0x74E0) } + - IF Handle value= 6 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_3 (29928 / 0x74E8) } + - IF Handle value= 8 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_4 (29936 / 0x74F0) } + - IF Handle value= 10 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_5 (29944 / 0x74F8) } + - IF Handle value= 12 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_6 (29952 / 0x7500) } + - IF Handle value= 14 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_7 (29960 / 0x7508) } + - IF Handle value= 16 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_8 (29968 / 0x7510) } + +#### d. Mandatory attribute Metric-Spec-Small + +- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL +- attribute-type = MetricSpecSmall (BITS-16) +- attribute-value.length = 2 bytes +- attribute-value ≠ 0x00 0x00 + - Bit 0 (mss-avail-intermittent(0)) must be set + - Bit 2 (mss-upd-aperiodic (2)) must be set + - Bit 3 (mss-msmt-aperiodic(3)) must be set + - Bit 9 (mss-acc-agent-initiated(9)) must be set + +#### e. Mandatory attribute Attribute-Value-Map + +- attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP +- attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16)) +- attribute-value.length = +- attribute-value = MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR, then MDC\_ATTR\_TIME\_STAMP\_BO + +#### f. Mandatory attribute Base-Offset-Time-Stamp + +- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO +- attribute-type = BaseOffsetTime +- attribute-value.length = 8 bytes + +#### g. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str + +- attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_SIMP\_BIT\_STR +- attribute-type = BITS-32 +- attribute-value.length = 4 bytes +- attribute-value = + - Battery-statusUndetermined (Bit 0) may be set + - Battery-present (Bit 1) may be set + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ Battery-active (Bit 2) may be set
    • ▪ Battery-charging (Bit 3) may be set
    • ▪ Battery-fullyCharged (Bit 4) may be set
    • ▪ Battery-disposable (Bit 5) may be set
    • ▪ Battery-rechargeable (Bit 6) may be set
    • ▪ Battery-overTemperature (Bit 7) may be set
    • ▪ Battery-faulty (Bit 8) may be set
    • ▪ Battery-incompatible (Bit 9) may be set
    • ▪ Bits 10 to 15 are reserved for future extension

    h. Mandatory attribute Capability-Mask-Basic

    • attribute-id = MDC_ATTR_ENUM_CAPABILITY_MASK_BASIC
    • attribute-type = CapabMaskBasic (BITS-16)
    • attribute-value.length = 2 bytes
    • attribute-value = <not relevant in this test>

    i. Mandatory attribute State-Flag-Basic

    • attribute-id = MDC_ATTR_ENUM_STATE_FLAG_BASIC
    • attribute-type = StateFlagBasic (BITS-16)
    • attribute-value.length = 2 bytes
    • attribute-value = <not relevant in this test>

    j. Not recommended attributes should not be present at configuration

    k. No other attribute shall be present at configuration

    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-006 | | | | +| TP label | Battery Status Enumeration Object - Extended configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | | +| | Testable items | BattStatus 4; M | BattStatus 5; M | BattStatus8; M | +| | | BattStatus 10; M | BattStatus 18; NR | BattStatus 29; NR | +| | | BattStatus 22; NR | BattStatus 24; NR | BattStatus 28; M | +| | | BattStatus 30; NR | BattStatus 36; NR | BattStatus 38; M | +| | | BattStatus 40; M | BattStatus 42; NR | BattStatus 44; NR | +| | | BattStatus 46; NR | BattStatus 48; NR | BattStatus 52; NR | +| | | BattStatus 54; NR | BattStatus 56; NR | BattStatus 58; M | +| | | BattStatus 60; M | BattStatus 61; M | BattStatus 62; M | +| Test purpose | Check that:
    The Battery Status Enumeration Object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_155 OR C_AG_OXP_156) AND C_AG_OXP_181 | | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | C_AG_OXP_183, C_AG_OXP_189 | +| Initial condition | The simulated PHG and PHD under test are in Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test
    2. 2. The simulated PHG responds with a result = accepted-unknown-config. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG
    3. 3. Check that the field Dev-Config-Id is set in the extended range; if it is not, PHG responds with "unsupported-config" and waits for a new configuration.
    4. 4. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    5. 5. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    6. 6. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    7. 7. The PHD under test sends an Event Report to the simulated PHG including a measurement reported by the object under test using MDS-Dynamic-Data-Update-Var or MDS-Dynamic-Data-Update-Fixed
    8. 8. Once the PHD under test sends an extended configuration and a measurement, check that the Battery Status Enumeration Object attributes are:
      1. a. Mandatory attribute Handle
        • attribute-id = MDC_ATTR_ID_HANDLE
        • attribute-type = HANDLE
        • attribute-value = recommended values are (2i) for each battery i, where i can take on value 1...n, where n is the maximum number of batteries that can be present in the agent.
      2. b. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_DM (128 / 0x0080) MDC_BATTERY_STATUS (29904 / 0x74D0)
      3. c. Mandatory attribute Supplemental-Types
        • attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES
        • attribute-type = SupplementalTypeList
        • attribute-value.length = SEQUENCE OF (SIZE (4) )
        • attribute-value =
          • • IF Handle value= 2 { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_1 (29912 / 0x74D8) }
          • • IF Handle value= 4 { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_2 (29920 / 0x74E0) }
          • • IF Handle value= 6 { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_3 (29928 / 0x74E8) }
          • • IF Handle value= 8 { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_4 (29936 / 0x74F0) }
          • • IF Handle value= 10 { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_5 (29944 / 0x74F8) }
          • • IF Handle value= 12 { MDC_PART_PHD_DM (0x00 0x80), MDC_BATTERY_6 (29952 / 0x7500) }
    | + +- IF Handle value= 14 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_7 (29960 / 0x7508) } +- IF Handle value= 16 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_8 (29968 / 0x7510) } +- IF Handle value= 18 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_9 (29976 / 0x7518) } +- IF Handle value= 20 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_10 (29984 / 0x7520) } +- IF Handle value= 22 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_11 (29992 / 0x7528) } +- IF Handle value= 24 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_12 (30000 / 0x7530) } +- IF Handle value= 26 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_13 (30008 / 0x7538) } +- IF Handle value= 28 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_14 (30016 / 0x7540) } +- IF Handle value= 30 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_15 (30024 / 0x7548) } +- IF Handle value= 32 { MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_BATTERY\_16 (30032 / 0x7550) } + +d. Mandatory attribute Base-Offset-Time-Stamp is present + +- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO +- attribute-type = BaseOffsetTime +- attribute-value.length = 8 bytes + +e. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str + +- attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_SIMP\_BIT\_STR +- attribute-type = BITS-32 +- attribute-value.length = 4 bytes +- attribute-value = + - Battery-statusUndetermined (Bit 0) may be set + - Battery-present (Bit 1) may be set + - Battery-active (Bit 2) may be set + - Battery-charging (Bit 3) may be set + - Battery-fullyCharged (Bit 4) may be set + - Battery-disposable (Bit 5) may be set + - Battery-rechargeable (Bit 6) may be set + - Battery-overTemperature (Bit 7) may be set + - Battery-faulty (Bit 8) may be set + - Battery-incompatible (Bit 9) may be set + - Bits 10 to 15 are reserved for future extension + +f. Mandatory attribute Capability-Mask-Basic + +- attribute-id = MDC\_ATTR\_ENUM\_CAPABILITY\_MASK\_BASIC +- attribute-type = CapabMaskBasic (BITS-16) +- attribute-value.length = 2 bytes +- attribute-value = + +g. Mandatory attribute State-Flag-Basic + +- attribute-id = MDC\_ATTR\_ENUM\_STATE\_FLAG\_BASIC + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = StateFlagBasic (BITS-16)
    • attribute-value.length = 2 bytes
    • attribute-value = <not relevant in this test>

    h. Not recommended attributes should not be present at configuration

    i. No other attribute shall be present at configuration

    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-007 | | | +| TP label | PM-Store Attributes for Extended Configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | PMStrObjAttPSM 2; M | PMStrObjAttPSM 4; M | +| | | PMStrObjAttPSM 6; M | PMStrObjAttPSM 8; NR | +| | | PMStrObjAttPSM 10; M | PMStrObjAttPSM 11; C | +| | | PMStrObjAttPSM 13; M | | +| Test purpose | Check that:
    PM-Store Object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_156 AND C_AG_OXP_041 AND C_AG_OXP_181 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and PHD under test are in Unassociated State. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG
    4. 4. The simulated PHG shall send a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.
    5. 5. The PHD issues a GET response with the PM-Store attributes it supports:
      1. a. Mandatory attribute PM-Store-Capab
        • attribute-id = MDC_ATTR_PM_STORE_CAPAB
        • attribute-type = PmStoreCapab
        • attribute-value.length = 2 bytes
        • attribute-value
          • ▪ pmsc-var-no-of-segm (bit 0) shall be set If the agent creates new segments either due to storing data of multiple sessions or due to time changes
          • ▪ pmsc-epi-seg-entries (bit 4) shall be set
          • ▪ pmsc-peri-seg-entries (bit 5) shall not be set
          • ▪ All other bits are agent-specific
      2. b. Mandatory Store-Capacity-Count
        • attribute-id = MDC_ATTR_METRIC_STORE_CAPAC_CNT
        • attribute-type = INT-U32
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value.length = 4 bytes
    • attribute-value = See relation with next attribute

    c. Mandatory attribute Store-Usage-Count

    • attribute-id = MDC_ATTR_METRIC_STORE_USAGE_CNT
    • attribute-type = INT-U32
    • attribute-value.length = 4 bytes
    • attribute-value = consistent with actual number of segments present and always less than or equal to Storage-Capacity-Count

    d. Mandatory attribute Operational-State

    • attribute-id = MDC_ATTR_OP_STAT
    • attribute-type = OperationalState
    • attribute-value.length = 2 bytes
    • attribute-value = One of the next
      • ▪ disabled (0x00 0x00)
      • ▪ enabled (0x00 0x01)
      • ▪ notAvailable (0x00 0x02)

    e. If NOT RECOMMENDED attribute Sample-Period is present

    • attribute-id = MDC_ATTR_TIME_PD_SAMP
    • attribute-type = RelativeTime
    • attribute-value.length = 4 bytes
    • attribute-value = <Not relevant in this test>

    f. Mandatory attribute Number-Of-Segments

    • attribute-id = MDC_ATTR_NUM_SEG
    • attribute-type = INT-U16
    • attribute-value.length = 2 bytes
    • attribute-value = <Not relevant in this test>

    g. Mandatory attribute Clear-Timeout

    • attribute-id = MDC_ATTR_CLEAR_TIMEOUT
    • attribute-type = RelativeTime
    • attribute-value.length = 4 bytes
    • attribute-value = <Not relevant in this test>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure | +| Notes | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------|------------------------|------------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-008 | | | +| TP label | PM-Segment Attributes for Extended Configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | PMStoreObjPSM 3; M | PMSegObjPSM 2; M | +| Test purpose | Check that:
    PM-Segment objects contain the attributes specified for Extended Configuration. | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [AND]
    The Battery Capacity and Battery Status PM-segments shall be implemented. | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_156 AND C_AG_OXP_041 AND C_AG_OXP_181 | +| Other PICS | | +| Initial condition | The simulated PHG and PHD under test are in Operating State. | +| Test procedure |
    1. 1. The simulated PHG shall send a Get request for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Store attributes.
    2. 2. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection = all-segments to indicate the PM-Segments attributes of all available PM-Segments.
    3. 3. The PHD issues a response with the PM-Segment attributes it supports:
      1. a. Mandatory attribute PM-Segment-Entry-Map
        1. SegmentEntryHeader.value = One of the next must be set:
          • • seg-elem-hdr-relative-time(1)
          • • seg-elem-hdr-hires-relative-time(2)
          • • seg-elem-hdr-bo-time(3)
        2. SegmEntryElem: <Record the fields for later comparison>
      2. b. Mandatory attribute Operational-State
        1. attribute-id = MDC_ATTR_OP_STAT
        2. attribute-type = OperationalState
        3. attribute-value.length 2 bytes
        4. attribute-value = One of:
          • • disabled (0x00 0x00)
          • • enabled (0x00 0x01)
          • • notAvailable (0x00 0x02)
      3. c. Recommended attribute Segment-Start-BO-Time
        1. attribute-id = MDC_ATTR_TIME_START_SEG_BO
        2. attribute-type = BaseOffsetTime
        3. attribute-value.length = 8 bytes
        4. attribute-value = <Not relevant for this test>
      4. d. Recommended attribute Segment-End-BO-Time
        1. attribute-id = MDC_ATTR_TIME_END_SEG_BO
        2. attribute-type = BaseOffsetTime
        3. attribute-value.length = 8 bytes
        4. attribute-value = <Not relevant for this test>
      5. e. Mandatory attribute Segment-Usage-Count
        1. attribute-id = MDC_ATTR_SEG_USAGE_CNT
        2. attribute-type = INT-U32
        3. attribute-value.length = 4 bytes
        4. attribute-value = <not relevant in this test>
    4. 4. Repeat for every PM-Segment object
    | +| Pass/Fail criteria |
    • • All checked values are as specified in the test procedure
    • • The Battery Capacity PM-Segment and Battery Status PM-Segment are present
    | + +| | | +|-------|--| +| Notes | | +|-------|--| + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-009 | | | | +| TP label | Communication Model: Association Procedure | | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | | +| | Testable items | AgProcAsPSM 1; M | AgProcAsPSM 2; M | AgProcAsPSM 3; M | +| | | AgProcAsPSM 4; M | AgProcAsPSM 5; M | AgProcAsPSM 6; M | +| | | AgProcAsPSM 7; M | AgProcAsPSM 8; M | AgProcAsPSM 9; M | +| | | AgProcAsPSM 10; M | AgProcAsPSM 11; M | AgProcAsPSM 12; M | +| | | AgProcAsPSM 13; O | | | +| Test purpose | Check that:
    The association procedure data exchange is correct | | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_155 OR C_AG_OXP_156) | | | | +| Other PICS | C_AG_OXP_002, C_AG_OXP_017 | | | | +| Initial condition | The simulated PHG and PHD under test are in Unassociated State. | | | | +| Test procedure |
    1. 1. The PHD sends a message to associate to the simulated PHG, the expected fields sent by the PHD are:
      1. a. APDU Type
        1. field- type = AarqApdu
        2. field-length =2 bytes
        3. field-value =0xE2 0x00.
      2. b. assoc-version
        1. field- type = AssociationVersion
        2. field-length =BITS-32
        3. field- value=0x80 0x00 0x00 0x00 (assoc-version1)
      3. c. data-proto-id
        1. field- type = DataProtoId(INT-U16)
        2. field-length =2 bytes
        3. field- value=0x50 0x79 (20601)
      4. d. protocol-version
        1. field- type = Protocol Version
        2. field-length = 4 bytes
        3. field- value= protocol-version2(1) AND protocol-version3(2) are set to 1 (0x60 0x00 0x00 0x00)
      5. e. encoding rules
        1. field- type = EncodingRules
        2. field-length = 2 bytes
        3. field- value=
          • • Bit 0 must be set (support for MDER)
          • • Bits 1 (XER) and 2 (PER) may be set
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • All other bits must be 0.

    f. nomenclature version

    • field- type = NomenclatureVersion
    • field-length = 4 bytes
    • field- value=0x80 0x00 0x00 0x00
    • This value indicates version1 is supported (nom-version1(0) is set).

    g. functional – units

    • field- type = FunctionalUnits
    • field-length = 4 bytes
    • • Bit 0 must be 0.
    • • Bits 1 and 2 may be set
    • • The rest of the bits must not be set

    h. System type

    • field- type = SystemType
    • field-length = 4 bytes
    • field- value = 0x00 0x80 0x00 0x00 (sys-type-agent)

    i. System-Id

    • field- type = OCTET STRING
    • field-length = 8 bytes
    • field- value = 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX (octet string length = 8 UI-64 manufacturer and device )
    • This value will be System Id attribute of MDS Object.

    j. dev-config-id

    • field- type = ConfigId(INT-U16)
    • field-length = 2 bytes
    • field- value =
    • • 0x0A 0x8C (2700) OR 0x0A 0x8D (2701) OR 0x0A 0x8E (2702) OR 0x0A 0x8F (2703) OR 0x0A 0x90 (2704) OR 0x0A 0x91 (2705) OR 0x0A 0x92 (2706) OR 0x0A 0x93 (2707) for standard configurations.
    • • <between 0x40 0x00 and 0x7F 0xFF> for extended configuration.

    k. data-req-mode-flags (DataReqModeCapab)

    • field- type = DataReqModeFlags
    • field-length = 2 bytes
    • field.value = IF NOT C_AG_OXP_017 -> 0x00 0x01 (data-req-supp-init-agent)

    l. data-req-init-agent-count (DataReqModeCapab)

    • field- type = INT-U8
    • field-length = 2 bytes
    • field.value = IF NOT C_AG_OXP_017 -> 0x01

    m. data-req-init-manager-count (DataReqModeCapab)

    • field- type = INT-U8
    • field-length = 2 bytes
    • field.value = IF NOT C_AG_OXP_017 -> 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-010 | | | +| TP label | Operating State. PHG to PHD Maximum APDU Size | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 3; M | | +| | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | ComCharPSM 2; M | SimplePSMProf 7; M | +| Test purpose |

    Check that:

    Check that the total size of the response does not exceed of the maximum APDU size established by the specialization

    [AND]

    A PSM PHD implementing only this device specialization shall be capable of receiving any APDU up to the size of Nrx. For this standard, Nrx shall be 46 octets

    | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_155 OR C_AG_OXP_156) | | | +| Other PICS | C_AG_OXP_100 | | | +| Initial condition | The simulated PHG and PHD are in Operating State | | | +| Test procedure |
    1. 1. The simulated PHG issues "Remote Operation Invoke Get" command with:
      1. a. Obj-handle set to 0 (to request for MDS object)
      2. b. attribute-id-list.count = 28
      3. c. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 9 times followed by an additional MDC_ATTR_ID_MODEL
    2. 2. Check the response of the PHD.
    3. 3. The simulated PHG issues "Remote Operation Invoke Get" command with handle set to 0 (to request for MDS object) and an empty attribute-id-list to indicate all attributes
    4. 4. Check the response of the PHD.
    | | | +| Pass/Fail criteria |
    • • In step 2, the PHD under test may respond with a rors-cmip-get listing all the requested attributes, or with a roer message. If PICS C_AG_OXP_100 = TRUE and PHD does not respond with a rors-cmip-get message, and it responds with a roer message or rorj (resource-limitation) message, a WARNING will appear.
      • ○ If the response is a get response, the total size of the response cannot exceed the following APDU size, given by the formula Ntx(i) = 28 + (102 + S) \times i, where "i" is the number of batteries and "S" is the maximally supported OCTET STRING.length for the Label-String attribute of the battery capacity object.
        • ▪ If C_AG_OXP_155 = TRUE (Power Status Monitor with Simple PSM profile) with i=8 and S=12 -> 940 octets
        • ▪ If C_AG_OXP_156 = TRUE (Power Status Monitor with Advanced PSM profile) with i=16 and S=12 -> 1660 octets
      • ○ In case it responds with a roer, the reason must not be protocol-violation (23)
    • • In step 4, the PHD must respond with a rors-cmip-get message.
    | | | +| Notes | | | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/PSM/BV-011 | | | +| TP label | Set Time (Base Offset Time) Power Status Monitor | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | MDSMethodsPSM 2; M | | +| Test purpose | Check that:
    The Set-Base-Offset-Time method shall be implemented | | | +| Applicability | C_AG_OXP_000 AND (C_AG_OXP_155 OR C_AG_OXP_156) | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and PHD under test are in Operating state. | | | +| Test procedure | 1. The simulated PHG sends a SET action:
    • CHOICE = SetBOTimeInvoke
    • action-type = MDC_ACT_SET_BO_TIME
    • the action-info-args are SetBOTimeInvoke
      • ▪ date-time = bo-seconds = 0x00 0x00 0x00 0x00, bo-fractions = 0x00 0x00, bo-time-offset = 0x3C
    2. The PHD under test response shall be a rors-cmip-confirmed-action:
    • action-type = MDC_ACT_SET_BO_TIME
    • action-info-args shall be empty.
    | | | +| Pass/Fail criteria | All checked values are as specified in the test procedure | | | +| Notes | | | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.811] Recommendation ITU-T H.811 (2017), *Interoperability design guidelines for personal connected health systems: Personal Health Devices interface*. +- [b-ITU-T H.812] Recommendation ITU-T H.812 (2017), *Interoperability design guidelines for personal connected health systems: Services interface*. +- [b-ITU-T H.812.1] Recommendation ITU-T H.812.1 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Observation Upload capability*. +- [b-ITU-T H.812.2] Recommendation ITU-T H.812.2 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Questionnaire capability*. +- [b-ITU-T H.812.3] Recommendation ITU-T H.812.3 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Capability Exchange capability* +- [b-ITU-T H.812.4] Recommendation ITU-T H.812.4 (2017), *Interoperability design guidelines for personal connected health systems: Services interface: Authenticated Persistent Session capability*. +- [b-ITU-T H.813] Recommendation ITU-T H.813 (2017), *Interoperability design guidelines for personal connected health systems: Healthcare Information System interface*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), *Adrenaline, Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance CDG, Continua Design Guidelines (2012), *Catalyst, Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), *Endorphin, Continua Design Guidelines*. +- [b-CDG 2015] Personal Connected Health Alliance, Continua Design Guidelines (2015), *Genome, Continua Design Guidelines*. + +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), *Iris, Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.13. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.11. + +- [b-TI] PHD Testable items. Test Tool v7.0.2.0 – Excel sheet v1.10. + + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.845.3-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.3-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..31b4a61e96b6a94843c8a7301e6dd46b96f195b4 --- /dev/null +++ b/marked/H/T-REC-H.845.3-201704-I_PDF-E/raw.md @@ -0,0 +1,1410 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.845.3** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 5C: Pulse oximeter** + +Recommendation ITU-T H.845.3 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.845.3 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5C: Pulse oximeter + +## Summary + +Recommendation ITU-T H.845.3 provides a test suite structure (TSS) and the test purposes (TP) for pulse oximeters in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.845.3 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5C: Device Specializations. Personal Health Device (Pulse oximeter) (Version 1.7, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.845.3 | 2015-01-13 | 16 | 11.1002/1000/12264 | +| 2.0 | ITU-T H.845.3 | 2016-07-14 | 16 | 11.1002/1000/12940 | +| 3.0 | ITU-T H.845.3 | 2017-04-13 | 16 | 11.1002/1000/13221 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, IEEE 11073 device specialization, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, pulse oximeter, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Test suite structure (TSS) ..... | 5 | +| 7 Electronic attachment ..... | 7 | +| Annex A Test purposes ..... | 8 | +| A.1 TP definition conventions..... | 8 | +| A.2 Subgroup 1.3.3: Pulse oximeter (PO)..... | 9 | +| Bibliography..... | 42 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5C: Device Specializations. Personal Health Device (Pulse oximeter) (Version 1.7, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.3 | 2012-10-05 | Initial release for Test Tool DG2011. This is the same version as "TSS&TP_1.5_PAN-LAN_PART_5C_v1.3.doc" because new features included in [b-CDG 2011] do not affect the test procedures specified in this document. | +| 1.4 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_PAN-LAN_PART_5C_v1.3.doc" as a baseline and adds new features included in [b-CDG 2012]
    • max APDU size for GM, BCA and ECG
    | +| 1.5 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5C_v1.4.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • Adds glucose meter BLE
    • Adds BLE SSP support
    • Adds NFC new transport
    • Adds INR device specialization
    | +| 1.6 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5C_v1.5.doc" as a baseline and adds new features included in Documentation Enhancements:
    • "Other PICS" row added
    | +| 1.6 | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_5C_v1.5.doc" because the new features included in [ITU-T H.810 (2015)]/[b-CDG 2015] do not affect the test procedures specified in this document. | +| 1.7 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5C_v1.6.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016] | + +## Recommendation ITU-T H.845.3 + +### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5C: Pulse oximeter + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 5, subpart 5C. + +- Part 1: Optimized exchange protocol Personal Health Device +- Part 2: Optimized exchange protocol Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - **Part 5C: Pulse oximeter** + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + +- [ISO/IEEE 11073-10404] ISO/IEEE 11073-10404:2010, *Health informatics – Personal health device communication – Device specialization – Pulse oximeter*. + + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. +- 3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|---------------------| +| ATS | Abstract Test Suite | +| DUT | Device Under Test | + +| | | +|-------|-------------------------------------------------------| +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCT | Protocol Conformance Testing | +| PCO | Point of Control and Observation | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +In this document, "0x" denotes a number in hexadecimal format and a B after a number enclosed by single quotation marks (e.g. '0100'B) denotes a number in binary format. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 1.3.3 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - **Subgroup 1.3.3: Pulse oximeter (PO)** + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +###### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + +- Subgroup 2.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 2.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) - Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth Low Energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases + - : This identifies a subgroup of test cases + - : This identifies the type of testing + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 1.3.3: Pulse oximeter (PO) + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-000 | | | +| TP label | Get MDS Object for pulse oximeter specialization: Mandatory, Conditional and Optional Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | MDSPulseattr1; M | MDSPulseattr2; C | +| | | MDSPulseattr4; M | MDSPulseattr5; M | +| | | MDSPulseattr7; R | MDSPulseattr8; R | +| | | MDSPulseattr10; M | MDSPulseEvent1 ; M | +| Test purpose | Check that:
    The PHD supports a Get command that requests all attributes
    [AND]
    The MDS Object contains the attributes specified for a Pulse Oximeter PHD. | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_PO_001, C_AG_PO_003, C_AG_OXP_181 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHG issues the "roiv-cmip-get" command with the handle set to 0 (to request for MDS object) and the attribute-id-list set to 0 to indicate all attributes.
    2. 2. The PHD responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object:
      MDS Attributes:
      1. a. Mandatory attribute Dev-Configuration-Id:
        • IF C_AG_PO_001 then attribute-value = 0x01 0x91
        • IF C_AG_PO_003 then attribute-value = 0x01 0x90
        • ELSE then attribute-value = < between 0x4000 and 0x7FFF >
      2. b. Attribute System-Type not present.
      3. c. Mandatory attribute System-model
        • attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)
        • attribute-type = SystemModel
        • attribute-value.length = <Variable>
        • attribute-value ={Manufacturer, Model}
      4. d. IF Recommended Power-Status attribute is present:
        • attribute-id = MDC_ATTR_POWER_STAT
        • attribute-type = PowerStatus
        • attribute-value.length = 2 bytes
        • attribute-value = ON_MAINS (0x8000) or ON_BATTERY (0x4000).
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Only one of the following may be active:

    1. 1. chargingFull(8),
    2. 2. chargingTrickle(9),
    3. 3. chargingOff(10).

    The rest of the bits must not be set.

    e. IF Recommended Battery-Level attribute is present:

    • attribute-id = MDC_ATTR_VAL_BATT_CHARGE
    • attribute-type = BITS-16
    • attribute-value.length = 2 bytes
    • attribute-value = <value between 0 and 100> If value >100, the meaning of the value is "undefined"

    f. IF Recommended Remaining-Battery-Time attribute is present:

    • attribute-id = MDC_ATTR_TIME_BATT_REMAIN
    • attribute-type = BatMeasure
    • attribute-value.length = 6 bytes
    • attribute-value = <4 bytes to define the value. 2 remaining bytes to define the units, which shall be set to one of: MDC_DIM_MIN (0x08 0xA0), MDC_DIM_HR (0x08 0xC0), MDC_DIM_DAY (0x08 0xE0) >

    g. Mandatory attribute System-Type-Spec_List:

    • attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST
    • attribute-type = TypeVerList
    • attribute-value.length = length 4
    • attribute-value = MDC_DEV_SPEC-PROFILE_PULS_OXIM (0x10 0x04), 1
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|---------------------|-----------------------------------------------------------------------------------------|------------------------|----------------------|----------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-001 | | | | +| TP label | SPO2 Object for Standard Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 1; M | SpO2NumObjAttr 2; M | SpO2NumObjAttr 3; M | +| | | SpO2NumObjAttr 4; R | SpO2NumObjAttr 5; M | SpO2NumObjAttr 6; R | +| | | SpO2NumObjAttr 7; R | SpO2NumObjAttr 8; R | SpO2NumObjAttr 9; R | +| | | SpO2NumObjAttr 10; M | SpO2NumObjAttr 11; M | SpO2NumObjAttr 12; R | +| | | SpO2NumObjAttr 13; C | SpO2NumObjAttr 14; R | SpO2NumObjAttr 15; C | +| | | SpO2NumObjAttr 16; C | SpO2NumObjAttr 17; R | SpO2NumObjAttr 18; R | +| | | SpO2NumObjAttr 19; R | SpO2NumObjAttr 20; R | SPO2StandConf 1; C | +| | | SPO2StandConf 2; C | SPO2StandConf 4; M | | +| Test purpose | Check that:
    SPO2 Object contains the attributes specified for Standard Configuration | | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_AG_OXP_173 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000 | +| Other PICS | C_AG_PO_001, C_AG_PO_003, C_AG_PO_010 | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x0190 OR 0x0191. If it is not, the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to 0x0190 or 0x0191 is received.
    5. 5. Once the PHD under test sends a standard configuration, check the SPO2 object:
    6. 6. SPO2 Object contents shall be:
      1. a. Mandatory attribute Handle
        1. attribute-id = MDC_ATTR_ID_HANDLE (0x09 0x21)
        2. attribute-type = HANDLE
        3. attribute-value = 0x00 0x01
      2. b. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE (0x09 0x2F)
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_SCADA (0x00 0x02), MDC_PULS_OXIM_SAT_O2 (0x4B 0xB8)
      3. c. If Conditional attribute Supplemental-Types is present:
        • • IF C_AG_PO_003 then:
        • • Not Recommended attribute Supplemental-Types
          1. attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES (0x0A 0x61 )
          2. attribute-type = SupplementalTypeList
          3. attribute-value.length =Sequence of TYPE (TYPE.length= 4 bytes)
          4. attribute-value: If PHD uses Spot Check Modality the value is MDC_MODALITY_SPOT, otherwise the value is not MDC_MODALITY_SPOT.
        • • IF C_AG_PO_001 then:
        • • Mandatory attribute Supplemental-Types
          1. attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES (0x0A 0x61 )
          2. attribute-type = SupplementalTypeList
          3. attribute-value.length =Sequence of TYPE (TYPE.length= 4 bytes)
          4. attribute-value = MDC_MODALITY_SPOT (0x4C 0x3C)
      4. d. Mandatory attribute Metric-Spec-Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL (0x0A 0x46)
        2. attribute-type = MetricSpecSmall
        3. attribute-value.length = 2 bytes
        4. attribute-value ≠ 0x00 0x00
          • ▪ bit 1 must be set (mss-avail-stored-data(1))
          • ▪ bit 9 must be set(mss-acc-agent-initiated(9))
      5. e. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE (0x09 0x96)
    | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = OID-Type
    • attribute-value.length = 2 bytes
    • attribute-value = 0x02 0x20 (MDC_DIM_PERCENT)

    f. IF Metric-Structure-Small attribute is present

    • attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL (0x0A 0x73)
    • attribute-type = MetricStructureSmall
    • attribute-value.length = 2 bytes
    • attribute-value =
      • ▪ ms-struct = one of the following:
        • ○ ms-struct-simple (0x01)
        • ○ ms-struct-compound (0x02)
        • ○ ms-struct-reserved (0x03)
        • ○ ms-struct-compound-simple (0x04)
      • ▪ ms-compound-no = one of the following:
        • ○ IF ms-struct = ms-struct-simple THEN = 0
        • ○ ELSE = maximum number of components in a compound value

    g. Mandatory attribute Attribute-Value-Map

    • attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP (0x0A 0x55)
    • attribute-type = AttrValMap
    • attribute-count = M (record for next step)
    • attribute-length = M *4 bytes
    • attribute-value = <check that M attributes are defined here>
    • IF the Attribute-Value-Map attribute needs to accommodate information pertaining to threshold status information, in addition to other attributes such as the observed value and timestamp information
    • IF C_AG_PO_003 then
      • ▪ attribute-value.length = N*4 bytes
      • ▪ attribute-value = MDC_ATTR_NU_VAL_OBS_BASIC (0x0A 0x4C), 2 (0x00 0x02)
    • IF C_AG_PO_001 then
      • ▪ attribute-value.length = N*4 bytes
      • ▪ attribute-value = MDC_ATTR_NU_VAL_OBS_BASIC (0x0A 0x4C), 2 (0x00 0x02) 0x09 0x90 0x00 0x08 MDC_ATTR_TIME_STAMP_ABS
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|-----------------|----------------------------------------|------------------------|----------------------|----------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-002 | | | | +| TP label | SPO2 Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 1; M | SpO2NumObjAttr 22; M | SpO2NumObjAttr 23; C | +| | | SpO2NumObjAttr 24; M | SpO2NumObjAttr 25; R | SpO2NumObjAttr 26; C | +| | | SpO2NumObjAttr 27; R | SpO2NumObjAttr 28; R | SpO2NumObjAttr 29; R | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---------------------------| +| | SpO2NumObjAttr 30; M | SpO2NumObjAttr 31; C | SpO2NumObjAttr 32; R | +| | SpO2NumObjAttr 33; R | SpO2NumObjAttr 34; R | SpO2NumObjAttr 35; O | +| | SpO2NumObjAttr 36; O | SpO2NumObjAttr 37; O | SpO2NumObjExt 1; M | +| | SpO2NumObjExt 2; M | SpO2NumObjExt 3; M | SpO2NumObjExt 4; M | +| | SpO2NumObjExt 5; M | SpO2NumObjExt 6; R | SpO2NumObjExt 7; R | +| | SpO2NumObjExt 8; R | SpO2NumObjExt 10; C | SpO2NumObjExt 11; C | +| | SpO2NumObjExt 12; C | SpO2NumObjExt 13; O | SpO2NumObjExt 14; C | +| | SpO2NumObjExt 15; C | SpO2NumObjExt 16; C | SpO2NumObjExt 19; C | +| | SpO2ThresSetStatAttr 1; M | SpO2ThresSetStatAttr 2; C | SpO2ThresSetStatAttr 3; C | +| | SpO2ThresSetStatAttr 4; C | SpO2ThresSetStatAttr 5; O | SpO2ThresSetStatAttr 6; C | +| | SpO2ThresSetStatAttr 7; C | SpO2ThresSetStatAttr 8; C | SpO2StandConf 4; M | +| | SpO2NumObjAttr 21; M | | | +| Test purpose | Check that:
    SPO2 Object contains the attributes specified for Extended Configuration | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_PO_010, C_AG_PO_011, C_AG_PO_012 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is in the extended range. If it is not, the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received.
    5. 5. Once the PHD under test sends an extended configuration, check the SPO2 object:
    6. 6. The SPO2 object contents must be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE (0x09 0x2F)
        • attribute-type = TYPE
        • attribute-value = MDC_PART_SCADA (0x00 0x02)),
          MDC_PULS_OXIM_SAT_O2 (0x4B 0xB8)
      2. b. IF Conditional attribute Supplemental-Types is present:
        • • IF there is no desire to distinguish modality, this attribute is not used.
        • attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES (0x0A 0x61 )
        • attribute-type = SupplementalTypeList
        • attribute-count = n
        • attribute-value.length =Sequence of TYPE (TYPE.length= 4 bytes then partition (NomPartition 2 bytes) and code (OID-Type))
        • IF the modality for SPO2 measurement is 'fast' then attribute-value= MDC_MODALITY_FAST (0x4C 0x34)
    | | | + +- IF the modality for SPO2 is 'slow' then attribute-value= MDC\_MODALITY\_SLOW (0x4C 0x38) +- IF the modality for SPO2 is 'spot-check' then attribute-value= MDC\_MODALITY\_SPOT (0x4C 0x3C) +- IF the modality for SpO2 measurement is Fast and Spot Check then attribute-value= MDC\_MODALITY\_SPOT (0x4C 0x3C) and MDC\_MODALITY\_FAST (0x4C 0x34)(Recommended) +- IF the modality for SpO2 measurement is Slow and Spot Check then attribute-value= MDC\_MODALITY\_SPOT (0x4C 0x3C) and MDC\_MODALITY\_SLOW (0x4C 0x38) (Recommended) +- It is NOT recommended to combine the values MDC\_MODALITY\_SLOW (0x4C 0x38) and MDC\_MODALITY\_FAST. + +#### c. Mandatory attribute Metric-Spec\_Small + +- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL (0x0A 0x46) +- attribute-type = MetricSpecSmall (2 bytes) +- attribute-value ≠ 0x00 0x00 + - IF bit 1 is set(mss-avail-stored-data(1)) is set, PHD may store and send multiple historical values. + - IF Spot-check modality is used then bit 3 is set(mss-msmt-aperiodic(3)) is set, otherwise, this bit may be set. + - bit 8 shall NOT set(mss-acc-manager-initiated(8)) + - bit 9 shall be set(mss-acc-agent-initiated(9)) + +#### d. IF Metric-Structure-Small attribute is present for SPO2 object + +- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL (0x0A 0x73) +- attribute-type = MetricStructureSmall +- attribute-value.length = 2 bytes + +#### e. Conditional attribute Measurement-Status + +- IF thresholding is to be used, this attribute is mandatory. +- attribute-id = MDC\_ATTR\_MSMT\_STAT (0x09 0x47) +- attribute-type = MeasurementStatus +- attribute-value.length = 2 bytes + +#### f. Only one attribute of Metric-Id and Metric-Id-List shall be present + +#### g. IF Metric-Id attribute is present in SPO2 object + +- attribute-id = MDC\_ATTR\_ID\_PHYSIO (0x09 0x2B) +- attribute-type = OID-Type +- attribute-value.length = 2 bytes +- attribute-value = + +#### h. IF Metric-Id-List attribute is present for SPO2 object + +- attribute-id = PHYSIOMDC\_ATTR\_ID\_PHYSIO\_LIST (0x0A 0x76) +- attribute-type = MetricIdList +- attribute-value.length= SEQUENCE OF OID-Type (2 bytes) +- attribute-value = +- The [Metric-Id-List] attribute shall be used if a compound observed value is used, which does not incorporate the Metric-Id directly. The order of the Metric-Id-List shall correspond to the order of the elements in the compound observed value. + +#### i. IF Metric-Id-Partition is present in SPO2 object + +- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART (0x0A 0x5F) +- attribute-type = NomPartition + +attribute-value.length = 2 bytes + +attribute-value = + +#### j. Mandatory attribute Unit-Code + +attribute-id = MDC\_ATTR\_UNIT\_CODE (0x09 0x96) + +attribute-type = OID-Type + +attribute-value.length = 2 bytes + +attribute-value = 0x02 0x20 (MDC\_DIM\_PERCENT) + +#### k. IF Attribute-Value-Map attribute is present in SPO2 object + +attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP (0x0A 0x55) + +attribute-type = AttrValMap + +attribute-count = M (record for next step) + +attribute-length = M \*4 bytes + +attribute-value = + +IF thresholding is to be used, the Attribute-Value-Map attribute needs to accommodate information pertaining to threshold status information, in addition to other attributes such as the observed value and timestamp information + +#### l. IF Source-Handle-Reference attribute is present for the SPO2 object + +attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF (0x4A 0x47) + +attribute-type = HANDLE + +attribute-value.length = 2 bytes + +attribute-value = + +#### m. IF Measure-Active-Period attribute is present in the SPO2 object + +attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE (0x0A 0x59) + +attribute-type = FLOAT-Type + +attribute-value.length = 4 bytes + +attribute-value = + +#### n. IF C\_AG\_PO\_011 then + +#### 1. Alert-Op-State is mandatory + +attribute-id = MDC\_ATTR\_AL\_OP\_STAT (0x09 0x06) + +attribute-type = CurLimAlStat + +attribute-value.length = 2 bytes + +attribute-value = One of the following:'1110000000000000'B or '0000000000000000'B or '0100000000000000'B or '0010000000000000'B + +- lim-alert-off (0) +- lim-low-off (1) +- lim-high-off (2) + +#### 2. Optional attribute Current-Limits + +attribute-id = MDC\_ATTR\_LIMIT\_CURR (0x09 0x34) + +attribute-type = CurLimAlVal + +attribute-value = + +IF Basic-Nu-Observed value is used the precision for CurrentLimit will be SFLOAT (2 bytes) .Basic-Nu-observed-Value is mandatory + +#### 3. Optional attribute Alert-Op-text-String + +attribute-id = MDC\_ATTR\_AL\_OP\_TEXT\_STRING (0x09 0xAE) + +attribute-type = AlertOpTextString + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value.length = <Variable>
    • attribute-value = <Two fields with printable ASCII>

    o. IF Accuracy attribute is present in SPO2 object

    • attribute-id = MDC_ATTR_NU_ACCUR_MSMT (0x09 0x4A)
    • attribute-type = FLOAT-Type (4 bytes)
    • attribute-value.length = 4 bytes
    • attribute-value = <Maximum deviation>

    p. IF Spot-Check modality is used then Conditional attribute Absolute-Time-Stamp:

    • attribute-id = MDC_ATTR_TIME_STAMP_ABS
    • attribute-type = AbsoluteTime
    • attribute-value.length = 8 bytes
    | +| Pass/Fail criteria |

    All checked values are as specified in the test procedure.

    If the PHD uses Spot Check Modality (C_AG_PO_010=TRUE) Supplemental-Type value is MDC_MODALITY_SPOT at least for one object, ELSE the value is not MDC_MODALITY_SPOT.

    | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-003 | | | +| TP label | Pulse Rate Object for Standard Configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | PulseRateNumObjAttr 1; M | PulseRateNumObjAttr 2; M | +| | | PulseRateNumObjAttr 4; R | PulseRateNumObjAttr 12 ; M | +| | | PulseRateNumObjAttr 23; R | PulseRateNumObjAttr 24; R | +| | | PulseRateNumObjAttr 26; R | PulseRateNumObjAttr 27; M | +| | | PulseRateNumObjAttr 29; R | PulseRateNumObjAttr 30; C | +| | | PulseRateNumObjAttr 32; C | PulseRateNumObjAttr 33; C | +| | | PulseRateNumObjAttr 35; R | PulseRateNumObjAttr 36; R | +| | | PulseRateStandConf 1; C | PulseRateStandConf 2; C | +| Test purpose |

    Check that:

    Pulse Rate Object contains the attributes specified for Standard Configuration

    | | | +| Applicability | C_AG_OXP_173 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000 | | | +| Other PICS | C_AG_PO_001, C_AG_PO_003, C_AG_PO_010 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x0190 OR 0x0191. If it is not, the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step
    | | | + +until a Dev-config-Id equal to 0x0190 or 0x0191 is received. + +5. Once the PHD under test sends a standard configuration, check the Pulse Rate object: + +6. Pulse Rate Object contents shall be: + +a. Mandatory attribute Handle + +- attribute-id = MDC\_ATTR\_ID\_HANDLE (0x09 0x21) +- attribute-type = HANDLE +- attribute-value = 0x00 0x0A (10) + +b. Mandatory attribute Type + +- attribute-id = MDC\_ATTR\_ID\_TYPE (0x09 0x2F) +- attribute-type = TYPE +- attribute-value = 0x00 0x02 (MDC\_PART\_SCADA), 0x48 0x1A (MDC\_PULS\_OXIM\_PULSE\_RATE) + +c. If conditional attribute Supplemental-Types is present + +- IF C\_AG\_PO\_003 then: +- Not Recommended attribute Supplemental-Types + - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES (0x0A 0x61 ) + - attribute-type = SupplementalTypeList + - attribute-value.length = Sequence of TYPE (TYPE.length= 4 bytes) + - attribute-value= If PHD uses Spot Check Modality the value is MDC\_MODALITY\_SPOT, otherwise the value is not MDC\_MODALITY\_SPOT. +- IF C\_AG\_PO\_001 Then: +- Mandatory attribute Supplemental-Types + - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES (0x0A 0x61 ) + - attribute-type = SupplementalTypeList + - attribute-value.length = Sequence of TYPE (TYPE.length= 4 bytes) + - attribute-value = MDC\_MODALITY\_SPOT (0x4C 0x3C) + +d. Mandatory attribute Metric-Spec-Small + +- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL (0x0A 0x46) +- attribute-type = MetricSpecSmall +- attribute-value.length = 2 bytes +- attribute-value ≠ 0x00 0x00 + - IF bit 1 is set(mss-avail-stored-data(1)) is set, PHD may store and send multiple historical values. + - bit 9 must be set(mss-acc-agent-initiated(9)) + +e. Mandatory attribute Unit-Code + +- attribute-id = MDC\_ATTR\_UNIT\_CODE (0x09 0x96) +- attribute-type = OID-Type +- attribute-value.length = 2 bytes +- attribute-value = 0x0A 0xA0 (MDC\_DIM\_BEAT\_PER\_MIN) + +f. Mandatory attribute Attribute-Value-Map + +- attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP (0x0A 0x55) +- attribute-type = AttrValMap +- attribute-count = M (record for next step) +- attribute-length = M \*4 bytes + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value = <check that M attributes are defined here>
    • IF the Attribute-Value-Map attribute needs to accommodate information pertaining to threshold status information, in addition to other attributes such as the observed value and timestamp information
    • IF C_AG_PO_003 then
      • ▪ attribute-value.length = N*4 bytes
      • ▪ attribute-value = MDC_ATTR_NU_VAL_OBS_BASIC (0x0A 0x4C), 2 (0x00 0x02)
    • IF C_AG_PO_001 then
      • ▪ attribute-value.length = N*4 bytes
      • ▪ attribute-value = MDC_ATTR_NU_VAL_OBS_BASIC (0x0A 0x4C), 2 (0x00 0x02) 0x09 0x90 0x00 0x08 MDC_ATTR_TIME_STAMP_ABS, 8
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------|--------------------------------|--------------------------------|--------------------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-004 | | | | +| TP label | Pulse Rate Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | PulseRateNumObjAttr 1; M | PulseRateNumObjAttr 3; M | PulseRateNumObjAttr 5; C | +| | | PulseRateNumObjAttr 6; C | PulseRateNumObjAttr 7; C | PulseRateNumObjAttr 8; M | +| | | PulseRateNumObjAttr 9; R | PulseRateNumObjAttr 10; R | PulseRateNumObjAttr 11; R | +| | | PulseRateNumObjAttr 14; C | PulseRateNumObjAttr 15; M | PulseRateNumObjAttr 16; C | +| | | PulseRateNumObjAttr 17; M | PulseRateNumObjAttr 18; M | PulseRateNumObjAttr 19; M | +| | | PulseRateNumObjAttr 20; M | PulseRateNumObjAttr 23; R | PulseRateNumObjAttr 24; R | +| | | PulseRateNumObjAttr 25; R | PulseRateNumObjAttr 26; R | PulseRateNumObjAttr 27; M | +| | | PulseRateNumObjAttr 29; R | PulseRateNumObjAttr 31; R | PulseRateNumObjAttr 34; R | +| | | PulseRateNumObjAttr 38; O | PulseRateNumObjAttr 39; O | PulseRateNumObjAttr 40; O | +| | | PulseRateNumObjAttr 41; C | PulseRateNumObjAttr 42; C | PulseRateNumObjAttr 43; O | +| | | PulseRateNumObjAttr 44; C | PulseRateThresSetStatAttr 1; M | PulseRateThresSetStatAttr 2; C | +| | | PulseRateThresSetStatAttr 3; C | PulseRateThresSetStatAttr 4; C | PulseRateThresSetStatAttr 5; C | +| Test purpose | Check that:
    Pulse Rate Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | | +| Other PICS | C_AG_PO_010, C_AG_PO_011, C_AG_PO_012 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test. | | | | + +2. The simulated PHG responds with a result = accepted-unknown-config. +3. The PHD responds with a "Remote Operation Invoke | Confirmed Event Report" message with an MDC\_NOTI\_CONFIG event to send its configuration to the PHG. +4. Check that the field Dev-Config-Id is in the extended range. If it is not, the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received. +5. Once the PHD under test sends an extended configuration, check Pulse Rate object: +6. Pulse Rate Object contents must be: + - a. Mandatory attribute Type + - attribute-id = MDC\_ATTR\_ID\_TYPE (0x09 0x2F) + - attribute-type = TYPE + - attribute-value = MDC\_PART\_SCADA (0x00 0x02), +MDC\_PULS\_OXIM\_PULSE\_RATE (0x48 0x1A) + - b. IF Conditional Supplemental-Types Attribute is present: + - IF there is no desire to distinguish modality, this attribute is not used. + - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES (0x0A 0x61 ) + - attribute-type = SupplementalTypeListq + - attribute-count = n + - attribute-value.length =Sequence of TYPE (TYPE.length= 4 bytes) then partition (NomPartition 2 bytes) and code (OID-Type)) + - IF the modality for Pulse Rate measurement is 'fast' then attribute-value= MDC\_MODALITY\_FAST (0x4C 0x34) + - IF the modality for Pulse Rate measurement is 'slow' then attribute-value= MDC\_MODALITY\_SLOW (0x4C 0x38) + - IF the modality for Pulse Rate measurement is 'Spot Check' then attribute-value= MDC\_MODALITY\_SPOT (0x4C 0x3C) + - IF the modality for SpO2 measurement is Fast and Spot Check then attribute-value= MDC\_MODALITY\_SPOT (0x4C 0x3C) and MDC\_MODALITY\_FAST (0x4C 0x34)(Recommended) + - IF the modality for SpO2 measurement is Slow and Spot Check then attribute-value= MDC\_MODALITY\_SPOT (0x4C 0x3C) and MDC\_MODALITY\_SLOW (0x4C 0x38) (Recommended) + - It is NOT recommended to combine the values MDC\_MODALITY\_SLOW (0x4C 0x38) and MDC\_MODALITY\_FAST. + - c. Mandatory attribute Metric-Spec\_Small + - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL (0x0A 0x46) + - attribute-type = MetricSpecSmall + - attribute-value.length = 2 bytes + - attribute-value ≠ 0x00 0x00 + - IF bit 1 is set(mss-avail-stored-data(1)) is set, the PHD may store and send multiple historical values. + - bit 8 shall NOT beset(mss-acc-manager-initiated(8)) + - bit 9 shall be set(mss-acc-agent-initiated(9)) + - IF Spot-Check modality is used, then bit 3 (mss-msmt-aperiodic(3)) has to be set + - d. IF Metric-Structure-Small attribute is present for Pulse Rate object + - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL (0x0A 0x73) + - attribute-type = MetricStructureSmall + - attribute-value.length = 2 bytes + +- attribute-value = + +#### e. Conditional attribute Measurement-Status + +- IF thresholding is to be used, this attribute is mandatory. + - attribute-id = MDC\_ATTR\_MSMT\_STAT (0x09 0x47) + - attribute-type = MeasurementStatus + - attribute-value.length = 2 bytes + +#### f. Only one attribute of Metric-Id and Metric-Id-List shall be present + +#### g. IF Metric-Id attribute is present in Pulse Rate object + +- attribute-id = MDC\_ATTR\_ID\_PHYSIO (0x09 0x2B) +- attribute-type = OID-Type +- attribute-value.length = 2 bytes +- attribute-value = + +#### h. IF Metric-Id-List attribute is present for Pulse Rate object + +- attribute-id = PHYSIOMDC\_ATTR\_ID\_PHYSIO\_LIST (0x0A 0x76) +- attribute-type = MetricIdList +- attribute-value.length= SEQUENCE OF OID-Type (2 bytes) +- attribute-value = +- The [Metric-Id-List] attribute shall be used if a compound observed value is used which does not incorporate the Metric-Id directly. The order of the Metric-Id-List shall correspond to the order of the elements in the compound observed value. + +#### i. IF Metric-Id-Partition is present in Pulse Rate object + +- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART (0x0A 0x5F) +- attribute-type = NomPartition +- attribute-value.length = 2 bytes +- attribute-value = + +#### j. Mandatory attribute Unit-Code + +- attribute-id = MDC\_ATTR\_UNIT\_CODE (0x09 0x96) +- attribute-type = OID-Type +- attribute-value.length = 2 bytes +- attribute-value = 0x0A 0xA0 (MDC\_DIM\_BEAT\_PER\_MIN) + +#### k. IF Attribute-Value-Map attribute is present in Pulse Rate object + +- attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP (0x0A 0x55) +- attribute-type = AttrValMap +- attribute-count = M (record for next step) +- attribute-length = M \*4 bytes +- attribute-value = +- IF thresholding is to be used, the Attribute-Value-Map attribute needs to accommodate information pertaining to threshold status information, in addition to other attributes such as the observed value and timestamp information + +#### l. IF Source-Handle-Reference attribute is present for Pulse Rate object + +- attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF (0x4A 0x47) +- attribute-type = HANDLE +- attribute-value.length = 2 bytes +- attribute-value = + +#### m. IF Measure-Active-Period attribute is present in Pulse Rate object + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE (0x0A 0x59)
    • attribute-type = FLOAT-Type
    • attribute-value.length = 4 bytes
    • attribute-value = <Period of time that the measure is active>

    n. IF C_AG_PO_012 then:

    • Alert-Op-State is mandatory
      • ▪ attribute-id = MDC_ATTR_AL_OP_STAT (0x09 0x06)
      • ▪ attribute-type = CurLimAlStat
      • ▪ attribute-value.length = 2 bytes
      • ▪ attribute-value = One of the following: '1110000000000000'B or '0000000000000000'B or '0100000000000000'B or '0010000000000000'B
        • ○ lim-alert-off (0)
        • ○ lim-low-off (1)
        • ○ lim-high-off (2)
    • Optional attribute Current-Limits
      • ▪ attribute-id = MDC_ATTR_LIMIT_CURR (0x09 0x34)
      • ▪ attribute-type = CurLimAlVal
      • ▪ attribute-value = <limits of the Threshold>
      • ▪ IF Basic-Nu-Observed value is used the precision for CurrentLimit will be SFLOAT (2 bytes) .Basic-Nu-observed-Value is mandatory
    • Optional attribute Alert-Op-text-String
      • ▪ attribute-id = MDC_ATTR_AL_OP_TEXT_STRING (0x09 0xAE)
      • ▪ attribute-type = AlertOpTextString
      • ▪ attribute-value.length = <Variable>
      • ▪ attribute-value = <Two fields with printable ASCII>

    o. IF Accuracy attribute is present in Pulse Rate object

    • attribute-id = MDC_ATTR_NU_ACCUR_MSMT (0x09 0x4A)
    • attribute-type = FLOAT-Type (4 bytes)
    • attribute-value.length = 4 bytes
    • attribute-value = <Maximum deviation>

    p. IF Spot-check modality is used, then Conditional attribute Absolute-Time-Stamp:

    • attribute-id = MDC_ATTR_TIME_STAMP_ABS
    • attribute-type = AbsoluteTime
    • attribute-value.length = 8 bytes
    • attribute-value =
    | +| Pass/Fail criteria |

    All checked values are as specified in the test procedure.

    If the PHD uses Spot Check Modality (C_AG_PO_010=TRUE) Supplemental-Type value is MDC_MODALITY_SPOT at least for one object, ELSE the value is not MDC_MODALITY_SPOT.

    | +| Notes | | + +| | | +|-----------------|-----------------------------------------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-005 | +| TP label | Pulsatile Quality Object for Extended Configuration | + +| | | | | | | +|--------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------|--| +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | | +| | Testable items | PulseQualNumObjAttr1; M | PulseQualNumObjAttr2; R | PulseQualNumObjAttr3; M | | +| | | PulseQualNumObjAttr4; R | PulseQualNumObjAttr5; R | PulseQualNumObjAttr6; R | | +| | | PulseQualNumObjAttr7; R | PulseQualNumObjAttr8; R | PulseQualNumObjAttr9; R | | +| | | PulseQualNumObjAttr10; O | PulseQualNumObjAttr11; O | PulseQualNumObjAttr12; O | | +| | | PulseQualNumObjAttr13; O | | | | +| Test purpose | | Check that:
    Pulsatile Quality Object contains the attributes specified for Extended Configuration | | | | +| Applicability | | C_AG_OXP_173 AND C_AG_PO_098 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | | +| Other PICS | | C_AG_OXP_098 | | | | +| Initial condition | | The simulated PHG and the PHD under test are in the Configuring state. | | | | +| Test procedure | |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is in the extended range. If it is not, the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received.
    5. 5. Once the PHD under test sends an extended configuration, check the Pulsatile Quality object.
    6. 6. Pulsatile Quality Object must be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE (0x09 0x2F)
        2. attribute-type = TYPE
        3. attribute-value = (0x00 0x02 (MDC_PART_SCADA), 0x4B 0xB0 (MDC_PULS_OXIM_PERF_REL)) OR (0x00 0x02 (MDC_PART_SCADA), 0x4B 0x30 (MDC_SAT_O2_QUAL))
      2. b. If Not Recommended attribute Supplemental-Types
        1. attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES (0x0A 0x61 )
        2. attribute-type = SupplementalTypeList
          1. ▪ attribute-value.length = Sequence of TYPE (TYPE.length= 4 bytes)
        3. attribute-value = <Not relevant for this test>
      3. c. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL (0x0A 0x46)
        2. attribute-type = MetricSpecSmall (2 bytes)
        3. attribute-value ≠ 0x00 0x00
          1. ▪ bit 8 shall be set to 1, mss-acc-manager-initiated(8))
          2. ▪ bit 9 shall be set to 1, mss-acc-agent-initiated(9))

      IF the object is scanned only by a Scanner object then this bit will not be set (the PHG will control the dataflow using the Operational State attribute (scanner object)).

      1. d. IF Not Recommended attribute Metric-Structure-Small is present
        1. attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL (0x0A 0x73)
        2. attribute-type = MetricStructureSmall
    | | | | + +- attribute-value.length = 2 bytes +- attribute-value = +- e. IF Not Recommended attribute Metric-Id-List is present in the Pulsatile quality object + - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST (0x0A 0x76) + - attribute-type = MetricIdList + - attribute-value.length= SEQUENCE OF OID-Type (2 bytes) + - attribute-value = + - The [Metric-Id-List] attribute shall be used if a compound observed value is used, which does not incorporate the Metric-Id directly. The order of the Metric-Id-List shall correspond to the order of the elements in the compound observed value. Only one attribute of Metric-Id and Metric-Id-List shall be present. +- f. IF Not Recommended attribute Metric-Id-Partition is present in Pulsatile quality object + - attribute-id = MDC\_ATTR\_METRIC\_ID\_PART (0x0A 0x5F) + - attribute-type = NomPartition + - attribute-value.length = 2 bytes +- g. IF attribute Unit-Code is present in Pulsatile quality object + - attribute-id = MDC\_ATTR\_UNIT\_CODE (0x09 0x96) + - attribute-type = OID-Type + - attribute-value.length = 2 bytes + - IF Type-value = 0x4B 0xB0 (MDC\_PULS\_OXIM\_PERF\_REL) THEN + - attribute-value = 0x02 0x00 (MDC\_DIM\_DIMLESS)(recommended) + - IF Type-value = 0x4B 0x30 (MDC\_SAT\_O2\_QUAL) THEN + - attribute-value = 0x02 0x20 (MDC\_DIM\_PERCENT) (recommended) + - Vendor may use private Unit-Code, in this case, then attribute-value given by the vendor +- h. IF attribute Attribute-Val-Map is present in Pulsatile quality object + - attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP (0x0A 0x55) + - attribute-type = AttrValMap + - attribute-count = M (record for next step) + - attribute-length = M \*2 bytes + - attribute-value = +- i. IF Recommended attribute Label-String is present in Pulsatile quality object + - attribute-id = MDC\_ATTR\_ID\_LABEL\_STRING + - attribute-type = OCTET STRING + - attribute-value.length = + - attribute-value = +- j. IF Recommended attribute Unit-Label-String is present in Pulsatile quality object + - attribute-id = MDC\_ATTR\_UNIT\_LABEL\_STRING + - attribute-type = OCTET STRING + - attribute-value.length = < Variable> + - attribute-value = +- k. IF Absolute-Time-Stamp attribute is present in Pulsatile quality object + - attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS + - attribute-type = AbsoluteTime (sequence of :century, year, month,day, hour, minute, second, sec-fractions) + - attribute-value.length = 8 bytes + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | attribute-value =
    l. IF Relative-Time-Stamp attribute is present in Pulsatile quality object
    attribute-id = MDC_ATTR_TIME_STAMP_REL
    attribute-type = RelativeTime
    attribute-value.length = 4 bytes
    attribute-value =
    m. IF HiResRelative-Time-Stamp attribute is present in Pulsatile quality object
    attribute-id = MDC_ATTR_TIME_STAMP_REL_HI_RES
    attribute-type = HighResRelativeTime
    attribute-value.length = 8 bytes
    attribute-value = | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Observed value attributes are checked in the manual test procedures for [ISO/IEEE 11073-20601]. | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-006 | | | | +| TP label | Plethysmogram Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | PlethyObjAttr 1; M | PlethyObjAttr 2; R | PlethyObjAttr 3; R | +| | | PlethyObjAttr 4; R | PlethyObjAttr 5; R | PlethyObjAttr 6; R | +| | | PlethyObjAttr 7; O | | | +| Test purpose | Check that:
    Plethysmogram Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_173 AND C_AG_PO_099 AND C_AG_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with a result = accepted-unknown-config.
    3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. Check that the field Dev-Config-Id is in the extended range. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received.
    5. Once the PHD under test sends an extended configuration, check Plethysmogram object.
    6. Plethysmogram Object must be:
    a. Mandatory attribute Type
    attribute-id = MDC_ATTR_ID_TYPE (0x09 0x2F)
    attribute-type = TYPE
    attribute-value = 0x00 0x02 (MDC_PART_SCADA), 0x4B 0xB4 (MDC_PULS_OXIM_PLETH)
    b. If Not Recommended attribute Supplemental-Types | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES (0x0A 0x61)
    • attribute-type = SupplementalTypeList
    • attribute.value.lenngth= Sequence of TYPE (TYPE.length= 4 bytes)
    • attribute-value = <Nor relevant for this test>

    c. Mandatory attribute Metric-Spec-Small

    • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL (0x0A 0x46)
    • attribute-type = MetricSpecSmall (2 bytes)
    • attribute-value ≠ 0x00 0x00
      • ▪ mss-acc-manager-initiated(8)=0
      • ▪ mss-acc-agent-initiated bit is not recommended as this implies that this object's data is transmitted via MDS Event Reports, and this object data is transmitted only through Scanner object.

    d. IF Not Recommended attribute Metric-Id is present in Plethysmogram Object

    • attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL (0x0A 0x73)
    • attribute-type = MetricStructureSmall
    • attribute-value.length = 2 bytes
    • attribute-value = <Not relevant for this test>

    e. IF attribute Unit-Code is present in Plethysmogram Object

    • attribute-id = MDC_ATTR_UNIT_CODE (0x09 0x96)
    • attribute-type = OID-Type
    • attribute-value.length = 2 bytes
    • attribute-value = 0x02 0x00 (MDC_DIM_DIMLESS) (Recommended value)
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Label-String, Time-Stamp, Sample-Period, Simple-Sa-Observed-Value, Scale-and-Range-Spec and SA-Specification do not change from the ones defined in [ISO/IEEE 11073-20601], so they are tested in RT-SA test procedure for [ISO/IEEE 11073-20601] | + +| | | | | | +|----------------------|---------------------------------------------------------------------------------------------------------|------------------------|----------------------|----------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-007 | | | | +| TP label | Pulsatile Occurrence Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | PulseOccObjAttr2; M | PulseOccObjAttr3; M | PulseOccObjAttr4; R | +| | | PulseOccObjAttr5; R | PulseOccObjAttr6; R | PulseOccObjAttr7; R | +| | | PulseOccObjAttr8; R | PulseOccObjAttr9; O | PulseOccObjAttr10; R | +| | | PulseOccObjAttr11; R | PulseOccObjAttr12; R | PulseOccObjAttr13; R | +| | | PulseOccObjAttr14; R | PulseOccObjAttr15; R | PulseOccObjAttr16; R | +| | | PulseOccObjAttr17; R | | | +| Test purpose | Check that:
    Pulsatile Occurrence Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_173 AND C_AG_PO_140 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHG and the PHD under test have been associated, but the PHD configuration is unknown for the simulated PHG, so the PHD and the simulated PHG will be in the Configuring state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is in the extended range. If it is not the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-Config-Id in the extended range is received.
    5. 5. Once the PHD under test sends an extended configuration, check the Pulsatile Occurrence object.
    6. 6. Pulsatile Occurrence Object must be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE (0x09 0x2F)
        • attribute-type = TYPE
        • attribute-value = 0x00 0x02 (MDC_PART_SCADA), 0xD0 0x02 (MDC_TRIG)
      2. b. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL (0x0A 0x46)
        • attribute-type = MetricSpecSmall (2 bytes)
        • attribute-value ≠ 0x00 0x00
          • • bit 8 (mss-acc-manager-initiated(8)) must be set to 1.
          • • IF bit 9 is set(mss-acc-agent-initiated(9)) is set, the object value is updated using agent-initiated measurement transmission.
      3. c. IF Not Recommended attribute Metric-Structure-Small is present in Pulsatile Occurrence object
        • attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL (0x0A 0x73)
        • attribute-type = MetricStructureSmall
        • attribute-value.length = 2 bytes
        • attribute-value =
      4. d. IF Not Recommended attribute Metric-Id is present in Pulsatile Occurrence object
        • attribute-id = MDC_ATTR_ID_PHYSIO (0x09 0x2B)
        • attribute-type = OID-Type
        • attribute-value.length = 2 bytes
        • attribute-value =
      5. e. IF Not Recommended attribute Metric-Id-List is present in Pulsatile Occurrence objet
        • attribute-id = PHYSIOMDC_ATTR_ID_PHYSIO_LIST (0x0A 0x76)
        • attribute-type = MetricIdList
        • attribute-value.length = SEQUENCE OF OID-Type (2 bytes)
        • attribute-value =
      6. f. IF Not Recommended attribute Metric-Id-Partition is present in Pulsatile Occurrence objet
        • attribute-id = MDC_ATTR_METRIC_ID_PART (0x0A 0x5F)
        • attribute-type = NomPartition
        • attribute-value.length = 2 bytes
        • attribute-value =
      7. g. IF Not Recommended attribute Unit-Code is present in Pulsatile Occurrence object
    | + +- attribute-id = MDC\_ATTR\_UNIT\_CODE (0x09 0x96) + - attribute-type = OID-Type + - attribute-value.length = 2 bytes +- h. IF Not Recommended attribute Source-Handle-Reference is present in Pulsatile Occurrence objet +- attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF (0x4A 0x47) + - attribute-type = HANDLE + - attribute-value.length = 2 bytes + - attribute-value = + - IF the Source-Handle-Reference is defined, it should point to either the Pulsatile Quality numeric object or the Plethysmogram Real-Time Sample Array object +- i. IF Not Recommended attribute Enum-Observed-Value-Simple-Bit-Str is present in Pulsatile Occurrence object +- attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_BIT\_STR + - attribute-type = BITS-32 + - attribute-value.length = BITS-32 + - attribute-value= +- j. IF Not Recommended attribute Enum-Observed-Value-Basic-Bit-Str is present in Pulsatile Occurrence object +- attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR + - attribute-type = BITS-16 + - attribute-value.length = 2 bytes + - attribute-value = +- k. IF Not Recommended attribute Enum-Observed-Value-Simple-Str is present in Pulsatile Occurrence object +- attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_STR + - attribute-type = EnumPrintableString + - attribute-value.length = + - attribute-value = +- l. IF Not Recommended attribute Enum-Observed-Value-Simple-Bit-Str is present in Pulsatile Occurrence object +- attribute-id= MDC\_ATTR\_VAL\_ENUM\_OBS + - attribute-type = EnumObsValue + - attribute-value.length = + - attribute-value = +7. IF C\_AG\_OXP\_293 THEN: +- a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes. + - b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object. + - c. IF the mds-time-mgr-set-time bit is set: + - The PHG moves to Configuring/Sending Set Time substate and: + - IF C\_AG\_OXP\_009 THEN it issues the Set-Time action command. + - IF C\_AG\_OXP\_014 THEN it issues the Set-Base-Offset-Time action command. + - Once its internal time setting operation is completed, the PHD responds to the PHG. + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    8. Take a measurement with the PHD

    9. Wait for the PHD to send an event report nad check:

    1. a. IF Recommended attribute Enum-Observed-Value-Simple-OID
      • attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_OID
      • attribute-type = OID-Type
      • attribute-value.length = 2 bytes
      • IF it is reporting that a pulsatile occurrence has occurred then attribute-value = MDC_TRIG_BEAT
      • IF it is reporting that the maximal inrush of the pulsatile wave has occurred, then attribute-value = MDC_TRIG_BEAT_MAX_INRUSH (Maximal inrush has to be defined by the vendor, ICS)
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------|--------------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-008 | | | | +| TP label | Pulse Characteristic Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | PulseCharacEnumAttr2; M | PulseCharacEnumAttr3; M | PulseCharacEnumAttr4; R | +| | | PulseCharacEnumAttr5; R | PulseCharacEnumAttr6; R | PulseCharacEnumAttr7; R | +| | | PulseCharacEnumAttr8; R | PulseCharacEnumAttr9; O | PulseCharacEnumAttr10; R | +| | | PulseCharacEnumAttr11; R | PulseCharacEnumAttr12; R | PulseCharacEnumAttr13; R | +| | | PulseCharacEnumAttr14; R | PulseCharacEnumAttr15; R | | +| Test purpose | Check that:
    Pulse Characteristic Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_173 AND C_AG_PO_144 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | | +| Other PICS | C_AG_OXP_098 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is in the extended range. If it is not the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received.
    5. 5. Once the PHD under test sends an extended configuration, check the Pulse Characteristic object.
    6. 6. Pulsatile Characteristic Object must be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE (0x09 0x2F)
        • attribute-type = TYPE
        • attribute-value = 0x00 0x02 (MDC_PART_SCADA), 0x4C 0x38
    | | | | + +(MDC\_PULS\_OXIM\_PULS\_CHAR) + +- b. Mandatory attribute Metric-Spec-Small + - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL (0x0A 0x46) + - attribute-type = MetricSpecSmall (2 bytes) + - attribute-value ≠ 0x00 0x00 + - bit 8 (mss-acc-manager-initiated(8)) must be set + - bit 9 (mss-acc-agent-initiated(9)) must be set +- c. IF Not Recommended attribute Metric-Structure-Small is present in Pulsatile Characteristic object + - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL (0x0A 0x73) + - attribute-type = MetricStructureSmall + - attribute-value.length = Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8)) + - attribute-value = +- d. IF Not Recommended attribute Metric-Id is present in Pulsatile Characteristic object. + - attribute-id = MDC\_ATTR\_ID\_PHYSIO (0x09 0x2B) + - attribute-type = OID-Type + - attribute-value.length = 2 bytes + - attribute-value = +- e. IF Not Recommended Metric-Id-List is present in Pulsatile Characteristic object + - attribute-id = PHYSIOMDC\_ATTR\_ID\_PHYSIO\_LIST (0x0A 0x76) + - attribute-type = MetricIdList + - attribute-value.length= SEQUENCE OF OID-Type (2 bytes) + - attribute-value = +- f. IF Not Recommended attribute Metric-Id-Part is present in Pulsatile Characteristic object + - attribute-id = MDC\_ATTR\_METRIC\_ID\_PART (0x0A 0x5F) + - attribute-type = NomPartition + - attribute-value.length = 2 bytes + - attribute-value = +- g. IF Not Recommended attribute Metric-Id-Partition is present in Pulsatile Characteristic object + - attribute-id = MDC\_ATTR\_UNIT\_CODE (0x09 0x96) + - attribute-type = OID-Type + - attribute-value.length = 2 bytes + - attribute-value = +- h. IF Not Recommended attribute Source-Handle-Reference is present in Pulsatile Characteristic object + - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF (0x4A 0x47) + - attribute-type = HANDLE + - attribute-value.length = 2 bytes + - attribute-value = + - IF the Source-Handle-Reference is defined, it should point to either the Pulse Amplitude numeric object or the Plethysmogram Real-Time Sample Array object. +- i. IF attribute Enum-Observed-Value-Simple-OID is present in Pulsatile Characteristic object + - attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_OID + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = OID-Type
    • attribute-value.length = 2 bytes
    • attribute-value=
    j. IF Not Recommended Enum-Observed-Value-Simple-Bit-Str is present in Pulsatile Characteristic object_
    • attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR
    • attribute-type = BITS-32
    • attribute-value.length = 4 bytes
    • attribute-value=
    k. IF Not Recommended Enum-Observed-Value-Simple-Str is present in Pulsatile Characteristic object
    • attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR
    • attribute-type = EnumPrintableString
    • attribute-value.length =
    • attribute-value =
    l. IF Not Recommended attribute Enum-Observed-Value is present in Pulsatile Characteristic object
    • attribute-id= MDC_ATTR_VAL_ENUM_OBS
    • attribute-type = EnumObsValue
    • attribute-value.length =
    • attribute-value =
    • It complicates the modeling of the object.
    m. IF Recommended attribute Enum-Observed-Value-Basic-Bit-Str is present in Pulsatile Characteristic object
    • attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR
    • attribute-type = BITS-16 bytes
    • attribute-value.length = 2 bytes
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|----------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-009 | | | | +| TP label | Device and Sensor Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | DeviceAndSensorObjAttr1; C
    DeviceAndSensorObjAttr5; R
    DeviceAndSensorObjAttr8; R
    DeviceAndSensorObjAttr11; R
    DeviceAndSensorObjAttr17; R | DeviceAndSensorObjAttr3; M
    DeviceAndSensorObjAttr6; R
    DeviceAndSensorObjAttr9; M
    DeviceAndSensorObjAttr12; R
    DeviceAndSensorObjAttr18; R | DeviceAndSensorObjAttr4; M
    DeviceAndSensorObjAttr7; R
    DeviceAndSensorObjAttr10; R
    DeviceAndSensorObjAttr16; O | +| Test purpose | Check that:
    Device and Sensor Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_173 AND C_AG_PO_104 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | C_AG_OXP_098, C_AG_PO_145 | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is in the extended range. If it is not the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received.
    5. 5. Once the PHD under test sends an extended configuration, check the Device and Sensor object.
    6. 6. Device and Sensor object must be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE (0x09 0x2F)
        2. attribute-type = TYPE
        3. attribute-value = 0x00 0x02 (MDC_PART_SCADA), 0x4C 0x4C (MDC_PULS_OXIM_DEV_STATUS)
      2. b. Mandatory attribute Metric-Spec-Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL (0x0A 0x46)
        2. attribute-type = MetricSpecSmall (2 bytes)
        3. attribute-value ≠ 0x00 0x00
          1. ▪ bit 8 shall be set (mss-acc-manager-initiated(8))
          2. ▪ bit 9 shall be set(mss-acc-agent-initiated(9))
      3. c. IF Metric-Structure-Small attribute is present
        1. attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL (0x0A 0x73)
        2. attribute-type = MetricStructureSmall
        3. attribute-value.length = Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))
        4. attribute-value =
      4. d. IF Metric-Id attribute is present
        1. attribute-id = MDC_ATTR_ID_PHYSIO (0x09 0x2B)
        2. attribute-type = OID-Type
        3. attribute-value.length =2 bytes
        4. attribute-value = <Not relevant for this Test>
      5. e. IF Metric-Id-List attribute is present
        1. attribute-id = PHYSIOMDC_ATTR_ID_PHYSIO_LIST (0x0A 0x76)
        2. attribute-type = MetricIdList
        3. attribute-value.length= SEQUENCE OF OID-Type (2 bytes)
        4. attribute-value =
        5. The [Metric-Id-List] attribute shall be used if a compound observed value is used which does not incorporate the Metric-Id directly. The order of the Metric-Id-List shall correspond to the order of the elements in the compound observed value.
      6. f. Only one attribute of Metric-Id and Metric-Id-List shall be present
      7. g. IF Metric-Id-Partition attribute is present
        1. attribute-id = MDC_ATTR_METRIC_ID_PART (0x0A 0x5F)
        2. attribute-type = NomPartition
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value.length = 2 bytes
    • attribute-value = <Not relevant for this Test>
    h. IF Unit-code attribute is present
    • attribute-id = MDC_ATTR_UNIT_CODE (0x09 0x96)
    • attribute-type = OID-Type
    • attribute-value.length = 2 bytes
    • attribute-value = <Not relevant for this Test>
    i. IF Source-Handle-Reference attribute is present
    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF (0x4A 0x47)
    • attribute-type = HANDLE
    • attribute-value.length = 2 bytes
    • attribute-value = <Not relevant for this Test>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| TP Id | TP/PLT/PHD/CLASS/PO/BV-009_A | | | | | | | | | | | +|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|--|----------------------------|---------------------|----------------------------------------------------------------------|-------------------------|--------------------------------------------------------------|------------------------|----------------------------------------------------------------------|----------------------| +| TP label | Semantic of Device and Sensor Object | | | | | | | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | | | | | | | | +| | Testable items | DeviceAndSensorObjAttr 11;R | | | | | | | | | | +| Test purpose | Check that:
    Check the semantic of Device and Sensor Object. | | | | | | | | | | | +| Applicability | C_AG_OXP_173 AND C_AG_PO_104 AND C_AG_OXP_181 AND C_AG_OXP_000 | | | | | | | | | | | +| Other PICS | | | | | | | | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | | | | | | | | +| Test procedure |

    1. Disconnect the sensor from any person and wait for the event report.

    2. Wait for the PHD to send an event report and check:

    a. IF Enum-Observed-Value-Basic-Bit-Str attribute or Enum-Observed-Value-Simple-Bit-Str is present

    • attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR or MDC_ATTR_ENUM_OBS_VAL_SIMPL_BIT_STR
    • attribute-type = 2 bytes
    • attribute-value.length = 2 bytes
    • attribute-value = See next sub-table:
    Device or sensor conditionPulseOxDevStat bits
    The PHD reports that the sensor is disconnected from the instrument.sensor-disconnected (0)
    The PHD reports that the sensor is malfunctioning or faulty.sensor-malfunction (1)
    The PHD reports that the sensor is not properly attached or has beensensor-displaced (2)
    | | | Device or sensor condition | PulseOxDevStat bits | The PHD reports that the sensor is disconnected from the instrument. | sensor-disconnected (0) | The PHD reports that the sensor is malfunctioning or faulty. | sensor-malfunction (1) | The PHD reports that the sensor is not properly attached or has been | sensor-displaced (2) | +| Device or sensor condition | PulseOxDevStat bits | | | | | | | | | | | +| The PHD reports that the sensor is disconnected from the instrument. | sensor-disconnected (0) | | | | | | | | | | | +| The PHD reports that the sensor is malfunctioning or faulty. | sensor-malfunction (1) | | | | | | | | | | | +| The PHD reports that the sensor is not properly attached or has been | sensor-displaced (2) | | | | | | | | | | | + +| | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| | dislodged, preventing accurate measurement. | | +| | An unsupported sensor is connected to the PHD. | sensor-unsupported (3) | +| | The PHD reports that sensor is not connected to the user. | sensor-off (4) | +| | The PHD reports that there is interference due to ambient light or electrical phenomena. | sensor-interference (5) | +| | Signal analysis is currently in progress prior to measurement availability. | signal-searching (6) | +| | The PHD determines that a questionable pulse is detected | signal-pulse-questionable (7) | +| | The PHD detects a non-pulsatile signal. | signal-non-pulsatile (8) | +| | The PHD reports that the signal is erratic or is not plausible. | signal-erratic (9) | +| | The PHD reports a consistently low perfusion condition exists. | signal-low-perfusion (10) | +| | The PHD reports a poor signal exists, possibly affecting accuracy. | signal-poor (11) | +| | The PHD reports that the incoming signal cannot be analysed or is inadequate for producing a meaningful result. | signal-inadequate (12) | +| | The PHD has determined that some irregularity has been detected while processing the signal. | signal-processing-irregularity (13) | +| | A general device fault has occurred in the PHD. | device-equipment-malfunction (14) | +| |
    • • Bit 4 (sensor-off) must be set

    3. Detach the sensor from the device and wait for an event report from the PHD under test:

    • • Bit 0 (sensor-disconnected) must be set.
    | | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | | +| Notes | | | + +| | | | | +|----------------------|-----------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-011 | | | +| TP label | PM Segment Object for Extended Configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | PMSegObj 1; M | PMSegObj 2; M | +| Test purpose | Check that:
    PM Segment Object contains the attributes specified for Extended Configuration | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_141AND C_AG_OXP_181 AND C_AG_OXP_000 | | | +| Other PICS | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | +| Test procedure |
    1. 1. The simulated PHG requests PM-Segment attributes using Get-Segment-Info, (MDC_ACT_SEG_GET_INFO) using the parameter SegmSelection:
      SegmSelection := all-segments [1]
    2. 2. The response sent by the PHD : SegmentInfoList
      SegmentInfoList := SEQUENCE OF SegmentInfo
      SegmentInfo := SEQUENCE { seg-inst-no InstNumber, seg-info AttributeList }
    3. 3. The attributes for the PM-Segment must be:
      1. a. Mandatory attribute Segment-Start-Abs-Time
        1. attribute-id = MDC_ATTR_TIME_START_SEG
        2. attribute-type = AbsoluteTime
        3. attribute-length = 8 bytes
        4. attribute-value =
      2. b. Mandatory attribute Segment-End-Abs-Time
        1. attribute-id = MDC_ATTR_TIME_END_SEG
        2. attribute-type = AbsoluteTime
        3. attribute-length = 8 bytes
        4. attribute-value = <Not relevant for this test>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-012_A | | | +| TP label | Scanner Object 1 | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | ScanObj 1; M | ScanObj 3; C | +| | | ScanObj 6; O | | +| Test purpose | Check that:

    Periodic Configurable Scanner Object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_046 AND C_AG_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Scanner object must be:
      1. a. Object Class id = MDC_MOC_SCAN_CFG_PERI
      2. b. Conditional attribute Transmit-Window
        1. attribute-id= MDC_ATTR_TX_WIND
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = TransmitWindows
    • attribute-value.length = 2 bytes
    • attribute-value = <Not relevant for this test variable>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-012_B | | | | +| TP label | Scanner Object 2 | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | ScanObj 1; M | ScanObj 7; C | ScanObj 8; M | +| | | ScanObj 11; O | | | +| Test purpose | Check that:
    Episodic Configurable Scanner Object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_047 AND C_AG_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Scanner object must be:
      1. a. Object Class id = MDC_MOC_SCAN_CFG_EPI
      2. b. IF attribute Transmit Window is present
        • attribute-id= MDC_ATTR_TX_WIND
        • attribute-type = U-INT16
        • attribute-value.length = 2 bytes
        • attribute. value = <Not relevant for this test>
      3. c. Mandatory attribute Min-Reporting-Interval
        • attribute-id= MDC_ATTR_SCAN_REP_PD_MIN
        • attribute-type = RelativeTime
        • attribute-value.length = 4 bytes
        • attribute. value = <Not relevant for this test>
    | | | | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | | | | +| Notes | | | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-017 | | | +| TP label | Communication Model: Association Procedure | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | PulseAssocReq 1; M | PulseAssocReq 2; M | +| | | PulseAssocReq 4; M | PulseAssocReq 5; M | +| | | PulseAssocReq 7; M | PulseAssocReq 8; M | +| | | PulseAssocReq 10; M | PulseAssocReq 12; C | +| | | PulseAssocReq 14; C | PulseAssocReq 15; M | +| | | PulseAssocReq X; M | | +| Test purpose | Check that:
    The association procedure data exchange is correct | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_002, C_AG_OXP_017 | | | +| Initial condition | The PHD under test and the simulated PHG are in the Unassociated state. | | | +| Test procedure |
    1. 1. The PHD sends a message to associate with the simulated PHG, the expected fields sent by the PHD are:
      1. a. APDU Type
        1. field- type = AarqApdu
        2. field-length =2 bytes
        3. field-value =0xE2 0x00
        4. This value is for association request "aarq".
      2. b. The following two bytes indicate the length of the message (could be helpful to analyse the fields)
      3. c. assoc-version
        1. field- type = AssociationVersion
        2. field-length =BITS-32
        3. field- value=0x80 0x00 0x00 0x00
        4. assoc-version = 0x80 0x00 0x00 0x00 (asassoc-version1(0) set) indicates that version 1 of the association protocol is supported.
      4. d. The following four bytes indicate:
        1. data-proto-list.count ( two bytes) = 0x00 0x01 (1)
        2. Length of the message (two bytes)
      5. e. data-proto-id
        1. field- type = DataProtoId
        2. field-length =2 bytes
        3. field- value=0x50 0x79 (20601)
        4. data-proto-id=20601 indicates exchange protocol follows this standard,
        5. data-proto-info = PhdAssociationInformation.
      6. f. protocol-version
        1. field- type = Protocol Version
    | | | + +- field-length =BITS-32 +- field- value=0x80 0x00 0x00 0x00 +- This value shows that version 1 of the data exchange protocol is supported (assoc-version1(0)=1) + +#### g. encoding rules + +- field- type = EncodingRules +- field-length = 2 bytes +- field- value= + - Bit 0 (MDER) must be set + +#### h. nomenclature version + +- field- type = NomenclatureVersion +- field-length =BITS-32 +- field- value=0x80 0x00 0x00 0x00 +- This value indicates version1 is supported (nom-version1(0) is set). + +#### i. functional – units + +- field- type = FunctionalUnits +- field-length = BITS-32 +- If PHD has no Test Association capabilities: + - field- value= 0x00 0x00 0x00 0x00 +- If the PHD has tested capabilities that can be used within the Test Association: + - field- value= 0x40 0x00 0x00 0x00 +- If the PHD has tested capabilities that can be used within the Test Association and requires that the PHG establish a Test Association: field- value= 0x60 0x00 0x00 0x00 + +#### j. system type + +- field- type = SystemType +- field-length = BITS-32 +- field- value = 0x00 0x80 0x00 0x00 (sys-type-agent) + +#### k. system-id + +- field- type = OCTET STRING +- field-length = 0x00 0x0A +- field- value = 0x00 0x08 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX (octet string length = 8 | EUI-64 manufacturer and device ) +- This value will be System Id attribute of MDS Object. + +#### l. dev-config-id + +- field- type = ConfigId +- field-length = 2 bytes +- field- value = + - 0x01 0x90 or 0x01 0x91 for standard configuration. + - for extended configuration. + +#### m. data-req-mode-flags (DataReqModeCapab) + +- field- type = DataReqModeFlags +- field-length = 2 bytes +- Bit 15 shall be set (data-req-supp-init-agent(15)) +- Bits 0, 6, 8, 10 shall NOT be set. + +#### n. data-req-init-agent-count (DataReqModeCapab) + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | field- type = INT-U8
    field-length = 1 byte
    field.value = 0x00 or 0x01
    o. data-req-init-manager-count (DataReqModeCapab)
    • field- type = INT-U8
    • field-length = 1 byte
    • field.value = maximum number of concurrent manager-initiated flows supported by the PHD.
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-023 | | | +| TP label | Numeric Class general for pulse oximeter PHD. | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | NumericClassGen 1; M | NumericClassGen 2; M | +| | | PulseOccObjAttr19; M | PulseCharacEnumAttr 19; M | +| | | | NumericClassGen 3; O | +| | | | DeviceAndSensorObjAttr 19; M | +| Test purpose | Check that:

    PHD contains one mandatory numeric object for expressing SpO2, one mandatory Numeric Object for Pulse Rate, and several optional numeric objects for additional SpO2 and Pulse Rate modalities, Pulse Amplitude and reporting current settings of Physiological Threshold.

    [AND]

    Pulsatile Quality, Plethysmographic waveform, Pulsatile Occurrence, Pulsatile Characteristic and Device and sensor annunciation status object attributes are instantiated only in Extended configurations. | | | +| Applicability | C_AG_OXP_173 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_010, C_AG_OXP_041, C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_181, C_AG_PO_001, C_AG_PO_003, C_AG_PO_098, C_AG_PO_099, C_AG_PO_104, C_AG_PO_140, C_AG_PO_144 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | +| Test procedure | 1. The PHD under test sends its configuration to the simulated PHG. It must contain
    • a. APDU Type
      • field- type = PrstApdu
      • field-length =2 bytes
      • field-value =0xE7 0x00
      • This value is for presentation APDU "prst" (PrstApdu).
    • b. The following two bytes indicate the length of the message (could be helpful to analyse the fields).
    • c. The following two bytes indicate the length of the OCTET STRING that contains the DataApdu (could be helpful to analyse the fields).
    • d. invoke-id
      • field- type = InvokeIDType
      • field-length =2 bytes
      • field- value=
    | | | + +- This value identifies the message; the confirmed response that will be sent by the simulated PHG shall have the same invoke-id. + +e. message + +- field- type = +- field-length =two bytes +- field- value=0x01 0x01 (EventReportArgumentSimple) +- This field identifies the type of message sent by the PHD, for the confirmed event configuration, roiv-cmip-confirmed-event-report. + +f. The following two bytes indicate the length of the fields that make up the EventReportArgumentSimple. + +g. obj-handle (EventReportArgumentSimple) + +- field- type = HANDLE +- field-length =2 bytes +- If PHD does not support relative time : +- field- value=0x 00 +- This obj-handle represents MDS-Object. + +h. event-time (EventReportArgumentSimple) + +- field- type = Relative Time +- field-length =4 bytes +- If PHD does not support relative time: + - field- value=0x FF 0x FF 0x FF 0x FF + +i. event-type (EventReportArgumentSimple) + +- field- type = OID-Type +- field-length =2 bytes +- field- value=0x 0D 0x 1C (MDC\_NOTI\_CONFIG) + +j. The following two bytes indicate the length for event-info (ConfigReport). This value shall not be 0. This is the start of ConfigReport. + +``` +ConfigReport ::= SEQUENCE { + config-report-id ConfigId, + config-obj-list ConfigObjectList } +``` + +k. config-report-id (ConfigReport) + +- field- type = ConfigId +- field-length = 2 bytes +- field- value= 0x0190 or 0x0191 for standard configuration and a value between 0x4000 and 0x7FFF for extended configuration. + +l. The following two bytes indicate the number of ConfigObjectList, this value shall not be 0. (The PHD will have at least 2 ObjectList) + +m. The following two bytes indicate the length for ConfigObjectList, this value shall not be 0. (If we have more than one object, we have to analyse every object in one loop) then the fields that are relevant are attribute value for attribute id = MDC\_ATTR\_ID\_TYPE (0x09 0x2F) + +n. obj-class ( ConfigReport then ConfigObjectList (ConfigObject)) + +- field- type = OID-Type +- field-length = 2 bytes +- field- value= + +o. obj-handle ( ConfigReport then ConfigObjectList (ConfigObject)) + +- field- type = HANDLE + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 2 bytes
    • field- value=

    p. The following two bytes indicate the number of Attributes, this value shall not be 0. ( ConfigReport then ConfigObjectList (ConfigObject)then AttributeList)

    q. The following two bytes indicate the length (bytes) for the Attributes List, this value shall not be 0.

    r. attribute-id (ConfigReport then ConfigObjectList (ConfigObject) then Attribute List)

    • field- type = OID-Type
    • field-length = 2 bytes
    • field- value= MDC_ATTR_ID_TYPE (0x09 0x2F) then This attribute let us know the type of measurement

    s. attribute-value(ConfigReport then ConfigObjectList (ConfigObject) then Attribute List), this value depends on the attribute type. The values to be checked are:

    • SpO2: 0x00 0x02 (MDC_PART_SCADA), 0x4B 0xB8 (MDC_PULS_OXIM_SAT_O2)
    • Pulse rate: 0x00 0x02 (MDC_PART_SCADA), 0x48 0x1A (MDC_PULS_OXIM_PULSE_RATE)
    • Only for extended configuration:
      • ▪ IF C_AG_PO_098 THEN Pulsatile Quality numeric Object is present.
      • ▪ IF C_AG_PO_099 THEN Plethysmographic waveform RT-SA Object is present.
      • ▪ IF C_AG_PO_104 THEN Device and Sensor enumeration Object is present.
      • ▪ IF C_AG_PO_140 THEN Pulsatile Occurrence enumeration Object is present.
      • ▪ IF C_AG_PO_144 THEN Pulsatile Characteristic enumeration Object is present.
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHD/CLASS/PO/BV-024 | | +| TP label | Operating State. PHG to PHD Maximum APDU Size | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 3; M | +| | Spec | [ISO/IEEE 11073-10404] | +| | Testable items | PulseComMod 3; M | +| Test purpose | Check that:

    The total size of the response do not exceed of the maximum APDU size established by the specialization

    [AND]

    An PHD according to this definition shall be capable of receiving an APDU up to the size of at least Nrx. For this standard it is Nrx = 256 octets | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_173 | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | C_AG_OXP_041, C_AG_OXP_100 | +| Initial condition | The simulated PHG and the PHD are in the Operating state. | +| Test procedure |
    1. 1. The simulated PHG issues a "Remote Operation Invoke Get" command with:
      1. a. Obj-handle set to 0 (to request for MDS object)
      2. b. attribute-id-list.count = 119
      3. c. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 39 times followed by an additional MDC_ATTR_ID_MODEL and MDC_ATTR_SYS_ID
    2. 2. Check the response of the PHD.
    3. 3. The simulated PHG issues a "Remote Operation Invoke Get" command with the handle set to 0 (to request for MDS object) and an empty attribute-id-list to indicate all attributes.
    4. 4. Check the response of the PHD.
    | +| Pass/Fail criteria |
    • • In step 2, the PHD under test may respond with a rors-cmip-get listing all the requested attributes, or with a roer message. If PICS C_AG_OXP_100 = TRUE and the PHD does not respond with a rors-cmip-get message, or it responds with a roer message or a rorj(resource-limitation) message, a WARNING will appear.
      • ○ If the response is a get response, the total size of the response cannot exceed the sum of the APDU sizes of the supported specializations (limited to an absolute limit of 64512 octets):
        • ▪ Pulse oximeter -> 9216 octets
        • ▪ Weighing scales -> 896 octets
        • ▪ Glucose meter -> 5120 octets or 64512 octets if the PHD supports PM-Store
        • ▪ Blood pressure -> 896 octets
        • ▪ Thermometer -> 896 octets
        • ▪ Independent activity hub -> 5120 octets
        • ▪ Cardiovascular -> 64512 octets or 6624 octets the PHD under test only supports Step Counter Profile
        • ▪ Strength -> 64512 octets:
        • ▪ Adherence monitor -> 1024 octets
        • ▪ Peak flow -> 2030 octets
        • ▪ Body composition analyser -> 7730 octets
        • ▪ Basic ECG/Simple ECG -> 7168 octets or 64512 octets if the PHD supports PM-Store
        • ▪ Basic ECG/Heart rate -> 1280 octets or 64512 octets if the PHD supports PM-Store
        • ▪ International normalized ratio -> 896 octets or 64512 if the PHD supports PM-Store
      • ○ In the case where the PHD responds with a roer, the reason must not be protocol-violation (23)
    • • In step 4, the PHD must respond with a rors-cmip-get message.
    | +| Notes | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0. (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12): *ETSI drafting rules*. +- [b-PHD PICS & PIXIT] Personal Health Device DG2016 PICS and PIXIT excel sheet v1.11. + +- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9. + +- [b-TCRL] Test Case Reference List\_DG2016\_v1.11. + +- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.845.4-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.4-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e56ec5a7dab918f5827979990a96714062546ae2 --- /dev/null +++ b/marked/H/T-REC-H.845.4-201704-I_PDF-E/raw.md @@ -0,0 +1,769 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.845.4** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 5D: Blood pressure monitor** + +Recommendation ITU-T H.845.4 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.845.4 + +# Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5D: Blood pressure monitor + +## Summary + +Recommendation ITU-T H.845.4 provides a test suite structure (TSS) and the test purposes (TP) for blood pressure monitors in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.845.4 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5D: Device Specializations. Personal Health Device (Blood Pressure Monitor) (Version 1.7, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.845.4 | 2015-01-13 | 16 | 11.1002/1000/12265 | +| 2.0 | ITU-T H.845.4 | 2016-07-14 | 16 | 11.1002/1000/12941 | +| 3.0 | ITU-T H.845.4 | 2017-04-13 | 16 | 11.1002/1000/13222 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, Personal Health Devices interface, personal area network, personal connected health devices, touch area network, IEEE 11073 device specialization, blood pressure monitor. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Test suite structure (TSS) ..... | 5 | +| 7 Electronic attachment ..... | 7 | +| Annex A Test purposes ..... | 8 | +| A.1 TP definition conventions..... | 8 | +| A.2 Subgroup 1.3.4: Blood pressure monitor (BPM)..... | 9 | +| Bibliography..... | 26 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5D: Device Specializations. Personal Health Device (Blood Pressure Monitor) (Version 1.7, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.2 | 2012-10-05 | Initial release for Test Tool DG2011. This is the same version as "TSS&TP_1.5_PAN-LAN_PART_5D_v1.2.doc" because new features included in [b-CDG 2011] do not affect the test procedures specified in this document. | +| 1.3 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_PAN-LAN_PART_5D_v1.2.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • max APDU size for GM, BCA and ECG
    | +| 1.4 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5D_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • Adds glucose meter BLE
    • Adds BLE SSP support
    • Adds NFC new transport
    • Adds INR device specialization
    | +| 1.5 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5D_v1.4.doc" as a baseline and adds new features included in Documentation Enhancements:
    • Other PICS" row added
    | +| 1.6 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_PLT_PART_5D_v1.5.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015] | +| 1.7 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5D_v1.6.doc" as baseline and it adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016] | + +## Recommendation ITU-T H.845.4 + +### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5D: Blood pressure monitor + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 5, subpart 5D. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - **Part 5D: Blood pressure monitor** + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + +- [ISO/IEEE 11073-10407] ISO/IEEE 11073-10407-2010, *Health informatics – Personal health device communication – Device specialization – Blood pressure monitor*. + + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|----------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | + +| | | +|-------|-------------------------------------------------------| +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NaN | Not a Number | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCT | Protocol Conformance Testing | +| PCO | Point of Control and Observation | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|--------------------|------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 1.3.4 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - **Subgroup 1.3.4: Blood pressure monitor (BPM)** + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + +- Subgroup 2.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 2.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# **7 Electronic attachment** + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth Low Energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 1.3.4: Blood pressure monitor (BPM) + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|----------------| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-000 | | | | +| TP label | Get MDS Object: Mandatory, Conditional and Optional Attributes1 | | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | +| | Testable items | MDSBPAttr 1; M | MDSBPAttr 2; M | MDSBPAttr 3; M | +| | | MDSBPAttr 4; M | MDSBPAttr 5; R | MDSBPAttr 6; R | +| | | MDSBPAttr 7; R | BldExt 2; M | | +| Test purpose | Check that:
    The Personal Health Device (PHD) supports a Get command that requests all attributes
    [AND]
    The MDS Object contains the attributes specified for a Blood Pressure Monitor PHD. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 | | | | +| Other PICS | C_AG_OXP_181 | | | | +| Initial condition | The simulated Personal Health Gateway (PHG) and the PHD under test are in the Operating state. | | | | +| Test procedure |
    1. The simulated PHG issues "roiv-cmip-get" command with the handle set to 0 (to request the MDS object) and the attribute-id-list set to 0 to indicate all attributes.
    2. The PHD responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object:
      MDS Attributes:
      1. Mandatory attribute Dev-Configuration-Id
        • IF NOT C_AG_OXP_181 then attribute-value = 0x02BC (700)
        • IF C_AG_OXP_181 then attribute-value = < between 0x4000 and 0x7FFF >
      2. Attribute System-Type not present
      3. Mandatory attribute System-Type-Spec-List
        • attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST
        • attribute-type = TypeVerList
        • attribute-value.length = 4 bytes for each specialization supported
        • attribute-value = {MDC_DEV_SPEC_PROFILE_BP , 1} must be found on the list
      4. Mandatory attribute System-model
        • attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)
        • attribute-type = SystemModel
        • attribute-value.length = <Variable>
        • attribute-value ={Manufacturer, Model}
      5. IF Recommended Power-Status attribute is present:
        • attribute-id = MDC_ATTR_POWER_STAT
        • attribute-type = PowerStatus
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    attribute-value.length = 2 bytes

    attribute-value = ON_MAINS (0x8000) or ON_BATTERY(0x4000), but both bits cannot be active at the same time

    Only one of the following may be active:

    • • chargingFull(8),
    • • chargingTrickle(9),
    • • chargingOff(10),
    • • The rest of the bits must not be set.

    f IF Recommended Battery-Level attribute is present

    attribute-id = MDC_ATTR_VAL_BATT_CHARGE

    attribute-type = INT-U16

    attribute-value.length = 2 bytes

    attribute-value = <value between 0 and 100> If value >100, the meaning of the value is "undefined"

    g IF Recommended Remaining-Battery-Time attribute is present:

    attribute-id = MDC_ATTR_TIME_BATT_REMAIN

    attribute-type = BatMeasure

    attribute-value.length = 6 bytes

    attribute-value = <4 bytes to define the value. 2 remaining bytes to define the units, which shall be set to one of: MDC_DIM_MIN (0x08 0xA0), MDC_DIM_HR (0x08 0xC0), MDC_DIM_DAY (0x08 0xE0)>.

    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|----------------------|-------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-003 | | | +| TP label | Systolic, Diastolic, MAP Object for Standard Configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast 3; M | SystDiast 5; M | +| | | SystDiast 7; R | | +| | | SystDiast 9; M | SystDiast 11; M | +| | | SystDiast 15; R | | +| | | SystDiast 17; M | SystDiast 19; R | +| | | SystDiast 21; M | | +| | | SystDiast 23; M | SystDiast 25; R | +| | | SystDiast 31; C | | +| | | SystDiast 37; R | SystDiast 39; R | +| | | SystDiast 41; R | | +| | | SystDiast 43; R | SystDiast 45; C | +| | | SystDiast 47; R | | +| | | SystDiast 49; R | SystDiast 51; R | +| | | SystDiast 54; M | | +| | | SystDiast 1; M | | +| Test purpose | Check that:
    Systolic, Diastolic, MAP Object contains the attributes specified for Standard Configuration | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 AND (NOT C_AG_OXP_181) | | | +| Other PICS | | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHG and the PHD under test have been associated, but the PHD configuration is unknown to the simulated PHG, so the PHD and the simulated PHG will be in the Configuring state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x02BC (700). If it is not the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to 0x02BC is received.
    5. 5. Wait until the PHD under test has sent a standard configuration.
    6. 6. The Systolic, Diastolic, Mean Arterial Pressure object must be defined in the configuration event report and its attributes must be:
      1. a. Mandatory attribute Handle
        • attribute-id = MDC_ATTR_ID_HANDLE
        • attribute-type = HANDLE
        • attribute-value = 1
      2. b. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = 0x00 0x02(MDC_PART_SCADA) , 0x4A 0x04 (MDC_PRESS_BLD_NONINV 18948)
      3. c. Mandatory attribute Metric-Spec-Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • • Bit 0 (mss-avail-intermittent(0)) must be set.
          • • Bit 1 (mss-avail-stored-data(1)) must be set.
          • • Bit 2 (mss-upd-aperiodic(2)) must be set.
          • • Bit 3 (mss-msmt-aperiodic(3)) must be set.
          • • Bit 9 (mss-acc-agent-initiated(9)) must be set.
          • • Bits 6, 7, 10, 11 and 15 must not be set
      4. d. Mandatory attribute Metric-Structure-Small
        • attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL
        • attribute-type = MetricStructureSmall
        • attribute-value.length = 2 bytes
        • attribute-value =
          • • ms-struct = ms-struct-compound-fix (0x03)
          • • ms-compound-no = 3
      5. e. Mandatory attribute Attribute-Value-Map
        • attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP
        • attribute-type = AttrValMap (sequence of attribute-id(OID-Type))
        • attribute-length= 12 bytes
        • attribute-value map.length = 8 bytes
        • attribute-value = 0x0A 0x4C 0x00 0x02 (MDC_ATTR_NU_CMPD_VAL_OBS_BASIC, 10 MDC_ATTR_TIME_STAMP_ABS, 8)
    | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id is the identifier for the attribute that are to be reported in fixed format (that are "described" in Attribute-Value-Map) and the length is the length for this attribute, for example: MDC_ATTR_TIME_STAMP_ABS (AbsoluteTime data type)will be composed by 8 fields INT-U8 , this length is 8 bytes(0x00 0x08).

    f. Mandatory attribute Metric-Id-List

    • attribute-id = MDC_ATTR_ID_PHYSIO_LIS
    • attribute-type = MetricIdList
    • attribute-value.length= <variable>SEQUENCE OF OID-Type (INT-U16)
    • attribute-value = MDC_PRESS_BLD_NONINV_SYS, MDC_PRESS_BLD_NONINV_DIA, then MDC_PRESS_BLD_NONINV_MEAN.

    The [Metric-Id-List] attribute shall be used if a compound observed value is used, which does not incorporate the Metric-Id directly. The order of the Metric-Id-List shall correspond to the order of the elements in the compound observed value.

    g. Mandatory attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type(INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_MMHG

    h. Conditional attribute Absolute-Time-Stamp

    • attribute-id = MDC_ATTR_TIME_STAMP_ABS
    • attribute-type = AbsoluteTime
    • attribute-value.length = 8 bytes
    • If the standard configuration is not adjusted and the fixed format is used → This attribute is Mandatory.

    7. Check that no other attributes are present in the initial configuration.

    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-003_A | | | +| TP label | Systolic, Diastolic, MAP Object format for Standard Configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast 53; M | | +| Test purpose | Check that:
    Systolic, Diastolic, MAP measurement values are in the right order in event report | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 AND (NOT C_AG_OXP_181) AND C_AG_OXP_182 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. Check that the field Dev-Config-Id is set to 0x02BC (700), if it is not, PHG responds with a "unsupported-config" and waits for a new configuration.

    5. Once the PHD under test has sent a standard configuration and the simulated PHG has sent a "roiv-cmip-get" to get all the attributes of the MDS, record the value of Date-and-Time.

    6. IF C_AG_OXP_293 AND the mds-time-mgr-set-time bit is set:

    1. a. The PHG moves to Configuring/Sending Set Time substate and:
      • IF C_AG_OXP_009 it issues the Set-Time action command.
      • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
    2. b. Once its internal time setting operation is completed, the PHD responds to the PHG.

    7. Once the PHD under test is in the Operating state, take a measurement and record the value of the measurement.

    8. Wait until the PHD under test sends an Event Report to the simulated PHG, the relevant fields are:

  • a. event-type = MDC_NOTI_SCAN_REPORT_FIXED
  • b. ScanReportInfoFixed
    • obj-handle = 1
    • Cmpound Object Count = 3
    • obs-val-data.value =
      • • Systolic (2 bytes)
      • • Dyastolic (2 bytes)
      • • MAP (2 bytes)
      • • Time Stamp (8 bytes).

    • | +| Pass/Fail criteria |
    • • The received data must be coherent with that previously recorded.
    • • The Time Stamp must be coherent with the one received in the MDS attribute.
    • • The data must be received in this exact order.
    | +| Notes | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-004 | | | | +| TP label | Systolic, Diastolic, MAP Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | +| | Testable items | SystDiast 1; M | SystDiast 6; M | SystDiast 8; R | +| | | SystDiast 12; R | SystDiast 14; R | SystDiast 16; R | +| | | SystDiast 18; R | SystDiast 20; R | SystDiast 22; M | +| | | SystDiast 26; R | SystDiast 38; R | SystDiast 52; R | +| Test purpose | Check that:
    Systolic, Diastolic, MAP Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 AND C_AG_OXP_181 | | | | +| Other PICS | C_AG_OXP_182 | | | | +| Initial condition | The simulated PHG and the PHD under test have been associated, but the PHD configuration is unknown to the simulated PHG, so the PHD and the simulated PHG will be in the | | | | + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Configuring state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is in the extended range. If it is not, the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received.
    5. 5. Wait until the PHD under test has sent an extended configuration.
    6. 6. The Systolic, Diastolic, Mean Arterial Pressure object must be defined in the configuration event report and its attributes must be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value=0x00 0x02(MDC_PART_SCADA) , 0x4A 0x04 (MDC_PRESS_BLD_NONINV 18948)
      2. b. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type
        3. attribute-value.length = INT-U16
        4. attribute-value = MDC_DIM_MMHG OR MDC_DIM_KILO_PASCAL
      3. c. IF Not Recommended attribute Supplemental-Types
        1. attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES
        2. attribute-type = SupplementalTypeList
        3. attribute-value.length =Sequence of TYPE (TYPE.length= 4 bytes)
        4. attribute-value = <Not relevant for this test>
      4. d. IF Recommended attribute Metric-Structure-Small
        1. attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL
        2. attribute-type = MetricStructureSmall
        3. attribute-value.length = 2 bytes
        4. attribute-value = <Not relevant for this test>
      5. e. IF Recommended attribute Measurement-Status is present
        1. attribute-id = MDC_ATTR_MSMT_STAT
        2. attribute-type = MeasurementStatus
        3. attribute-value.length = 2 bytes
        4. attribute-value = <Not relevant for this test>
      6. f. IF Not Recommended attribute Metric-Id is present
        1. attribute-id = MDC_ATTR_ID_PHYSIO
        2. attribute-type = OID-Type
        3. attribute-value.length =INT-U16
        4. attribute-value = <Not relevant for this test>
      7. g. IF Recommended attribute Metric-Id-List is present
        1. attribute-id = MDC_ATTR_ID_PHYSIO_LIS
        2. attribute-type = MetricIdList
        3. attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
        4. attribute-value = <Not relevant for this test>
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    h. IF Not Recommended attribute Metric-Id-Partition is present

    • attribute-id = MDC_ATTR_METRIC_ID_PART
    • attribute-type = NomPartition
    • attribute-value.length = INT-U16
    • attribute-value = <Not relevant for this test>

    i. IF Not Recommended attribute Measure-Active-Period is present

    • attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE
    • attribute-type = FLOAT-Type
    • attribute-value.length = INT-U32
    • attribute-value = <Not relevant for this test>

    j. IF Not Recommended attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE
    • attribute-value.length = INT-U16
    • attribute-value = <Not relevant for this test>

    k. IF Recommended attribute Accuracy is present

    • attribute-id = MDC_ATTR_NU_ACCUR_MSMT
    • attribute-type = FLOAT-Type (INT-U32)
    • attribute-value.length = FLOAT-Type (INT-U32)
    • attribute-value = <Not Relevant for this test>.
    | +| Pass/Fail criteria |
    • • All checked values are as specified in the test procedure.
    • • IF C_AG_OXP_182 THEN check that the attribute *-Nu-Obs-Value received was the one specified in the Attribute-Value-Map.
    | +| Notes | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-005 | | | +| TP label | Pulse Object for Standard Configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | PulsRat 1; R | PulsRat 2; M | +| | | PulsRat 6; R | PulsRat 8; M | +| | | PulsRat 14; R | PulsRat 16; R | +| | | PulsRat 20; M | PulsRat 22; M | +| | | PulsRat 30; C | PulsRat 32; R | +| | | PulsRat 36; R | PulsRat 42; M | +| | | PulsRat 48; R | PulsRat 50; R | +| | | BPConcepts 4; O | | +| Test purpose | Check that:
    Pulse Object contains the attributes specified for Standard Configuration | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 AND (NOT C_AG_OXP_181) | +| Other PICS | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x02BC (700). If it is not, the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to 0x02BC is received.
    5. 5. Wait until the PHD under test sends a standard configuration.
    6. 6. The Pulse Object must be defined in the configuration event report, and its attributes must be:
      1. a. Mandatory attribute Handle
        1. attribute-id = MDC_ATTR_ID_HANDLE
        2. attribute-type = HANDLE
        3. attribute-value = 2
      2. b. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = 0x00 0x02(MDC_PART_SCADA) , 0x48 0x2A(MDC_PULS_RATE_NON_INV 18474)
      3. c. Mandatory attribute Metric-Spec-Small (for standard and extended configuration)
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. • Bit 0 (mss-avail-intermittent(0)) must be set
          2. • Bit 1 (mss-avail-stored-data(1)) must be set
          3. • Bit 2 (mss-upd-aperiodic(2)) must be set
          4. • Bit 3 (mss-msmt-aperiodic(3)) must be set
          5. • Bit 9 (mss-acc-agent-initiated(9)) must be set
          6. • Bits 6, 7, 10, 11 and 15 must not be set
      4. d. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type(INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_BEAT_PER_MIN
      5. e. Mandatory attribute Attribute-Value-Map is present
        1. attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP
        2. attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and ( INT-U16))
        3. attribute-length = 12 bytes
        4. attribute-value = MDC_ATTR_NU_VAL_OBS_BASIC OR MDC_ATTR_TIME_STAMP_ABS.
    7. 7. Check that no other attributes are present.
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | All checked values are as specified in the test procedure in order to indicate that the event report is confirmed. | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-006 | | | | +| TP label | Pulse Object for Extended Configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | +| | Testable items | PulsRat 5; M | PulsRat 7; R | PulsRat 11; R | +| | | PulsRat 13; R | PulsRat 15; R | PulsRat 17; R | +| | | PulsRat 19; R | PulsRat 21; M | PulsRat 25; R | +| | | PulsRat 37; C | PulsRat 51; R | PulsRat_1; R | +| | | BPConcepts 4; O | | | +| Test purpose | Check that:
    Pulse Object contains the attributes specified for Extended Configuration | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 AND C_AG_OXP_181 AND C_AG_BPM_003 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config.
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is in the extended range. If it is not, the PHG responds with a "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received.
    5. 5. Wait until the PHD under test sends an extended configuration.
    6. 6. Pulse Rate Object attributes must be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = 0x00 0x02(MDC_PART_SCADA) , 0x48 0x2A(MDC_PULS_RATE_NON_INV 18474)
      2. b. Mandatory attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type(INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = MDC_DIM_BEAT_PER_MIN
      3. c. IF Recommended attribute Measurement-Status is present
        • attribute-id = MDC_ATTR_MSMT_STAT
        • attribute-type = MeasurementStatus
        • attribute-value.length = 2 bytes
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value = <Not relevant for this test>
    • d. Not Recommended attribute Supplemental-Types
      • attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES
      • attribute-type = SupplementalTypeList
      • attribute-value.length = <variable>Sequence of TYPE (TYPE.length= 4 bytes)
      • attribute-value = <Not relevant for this test>
    • e. IF Not recommended attribute Metric-Structure-Small is present
      • attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL
      • attribute-type = MetricStructureSmall
      • attribute-length = 2 bytes
      • attribute-value = <Not relevant for this test>
    • f. IF Not recommended attribute Metric-Id is present
      • attribute-id = MDC_ATTR_ID_PHYSIO
      • attribute-type = OID-Type(INT-U16)
      • attribute-value.length = 2 bytes
      • attribute-value = <Not relevant for this test>
    • g. IF Not Recommended attribute Metric-Id-List is present
      • attribute-id = MDC_ATTR_ID_PHYSIO_LIS
      • attribute-type = MetricIdList
      • attribute-value = <Not relevant for this test>
    • h. IF Not recommended attribute Metric-Id-Partition is present
      • attribute-id = MDC_ATTR_METRIC_ID_PART
      • attribute-type = NomPartition(INT-U16)
      • attribute-value.length = 2 bytes
      • attribute-value = <Not relevant for this test>
    • i. IF Not recommended attribute Source-Handle-Reference is present
      • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
      • attribute-type = HANDLE(INT-U16)
      • attribute-value.length = 2 bytes
      • attribute-value = <Not relevant for this test>
    • j. IF Recommended attribute Accuracy is present
      • attribute-id = MDC_ATTR_NU_ACCUR_MSMT
      • attribute-type = FLOAT-Type (INT-U32)
      • attribute-value.length = 4 bytes
      • attribute-value = <Not relevant for this test>.
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure in order to indicate that the event report is confirmed. | +| Notes | | + +| | | | +|-----------------|--------------------------------------------|------------------------| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-007 | | +| TP label | Communication Model: Association Procedure | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------| +| Testable items | MDSEvents 2; M | MDSEvents 4; M | MDSEvents 5; M | +| | AsProc 2; M | AsProc 3; M | AsProc 4; M | +| | AsProc 5; M | AsProc 6; M | AsProc 7; M | +| | AsProc 8; M | AsProc 9; M | AsProc 10; M | +| | AsProc 12; M | AsProc 13; M | | +| Test purpose | Check that:
    The association procedure data exchange is correct | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 | | | +| Other PICS | C_AG_OXP_002, C_AG_OXP_017, C_AG_OXP_179 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | +| Test procedure | 1. The PHD sends a message to associate with the simulated PHG, the expected fields sent by that PHD are:
    1. APDU Type
      • field- type = AarqApdu
      • field-length =2 bytes
      • field-value =0xE2 0x00.
    2. assoc-version
      • field- type = AssociationVersion
      • field-length =BITS-32
      • field- value=0x80 0x00 0x00 0x00
    3. data-proto-id
      • field- type = DataProtoId(INT-U16)
      • field-length =2 bytes
      • field- value=0x50 0x79 (20601)
    4. protocol-version
      • field- type = Protocol Version
      • field-length = 4 bytes
      • field- value=0x80 0x00 0x00 0x00
    5. encoding rules
      • field- type = EncodingRules
      • field-length = 2 bytes
      • field- value= 0x80 0x00 , at least pulse oximeter will support MDER
    6. nomenclature version
      • field- type = NomenclatureVersion
      • field-length = 4 bytes
      • field- value=0x80 0x00 0x00 0x00
      • This value indicates version1 is supported (nom-version1(0) is set)
    7. functional – units
      • field- type = FunctionalUnits
      • field-length = 4 bytes
      • If NOT C_AG_OXP_179 THEN: field-value = 0x00 0x00 0x00 0x00
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • If C_AG_OXP_179 THEN: field- value= 0x40 0x00 0x00 0x00
    • If C_AG_OXP_179 AND requires that the PHG establish a Test Association: field- value= 0x60 0x00 0x00 0x00

    h. System type

    • field- type = SystemType
    • field-length = 4 bytes
    • field- value = 0x00 0x80 0x00 0x00 (sys-type-agent)

    i. System-Id

    • field- type = OCTET STRING
    • field-length = 8 bytes
    • field- value = 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX (octet string length = 8 UI-64 manufacturer and device )
    • This value will be System Id attribute of MDS Object

    j. dev-config-id

    • field- type = ConfigId(INT-U16)
    • field-length = 2 bytes
    • field- value =
      • • 0x02 0xBC for standard configuration
      • • <between 0x40 0x00 and 0x7F 0xFF > for extended configuration

    k. data-req-mode-flags (DataReqModeCapab)

    • field- type = DataReqModeFlags
    • field-length = 2 bytes
    • If the PHD supports agent-initiated measurement transfer → Bit 15 is set (data-req-supp-init-agent(15))
    • If the PHD supports requesting objects based on object handle →Bit 6 will be set (data-req-supp-scope-handle(6))
    • If the PHD supports single response →Bit 8 will be set (data-req-supp-mode-single-rsp(8))
    • If the PHD supports time unlimited data request →Bit 10 will be set (data-req-supp-mode-time-no-limit(10))

    l. data-req-init-agent-count (DataReqModeCapab)

    • field- type = INT-U8
    • field-length = 2 bytes
    • field.value = 0x01

    m. data-req-init-manager-count (DataReqModeCapab)

    • field- type = INT-U8
    • field-length = 2 bytes
    • field.value = 0x00.
    | +| Pass/Fail criteria | All checked attributes have proper values. | +| Notes | | + +| | | | +|-----------------|-----------------------------|------------------------| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-010 | | +| TP label | Not a Number (NaN) | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | + +| | | | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--|--|--|--| +| | Testable items | SysDiast 2; M | | | | | +| | | | | | | | +| Test purpose | Check that:
    If a PHD does not measure one or more systolic, diastolic, MAP values, then the special value NaN is reported instead. | | | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 AND C_AG_BPM_005 | | | | | | +| Other PICS | | | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | | | +| Test procedure | 1. Take a measurement with the PHD under test without measuring any value.
    2. Wait for the simulated PHG to receive the event report with the measurement. | | | | | | +| Pass/Fail criteria | The value of the systolic, diastolic or MAP measurements must be NaN. | | | | | | +| Notes | | | | | | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-011 | | | | +| TP label | Reporting systolic and diastolic blood pressures | | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | +| | Testable items | BPConcepts 2; M | BPConcepts 3; M | SystDiast_55; M | +| Test purpose | Check that:
    Both systolic, diastolic blood pressures and MAP are always reported together | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with a result = accepted-unknown-config.
    3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG. Record ConfigObject for every Sys/Dias/MAP object.
    4. IF C_AG_OXP_293:
    • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    • c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 5. Take some measurements with the PHD under test.
    6. Wait for the PHG to receive the event reports of the measurements. | +| Pass/Fail criteria | The values of the systolic, diastolic and mean arterial pressure must be sent always in the same object in the event report, and using the same units. | +| Notes | http://continua.plugfest.com/show_bug.cgi?id=62 | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-012 | | | +| TP label | MDS Configuration objects events for Blood Pressure Monitor PHD. | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | MDSEvents 7; M | | +| Test purpose | Check that:
    A Blood Pressure Monitor sends the MDS-Configuration-Event using a Confirmed event report and the MDS-Configuration-Event includes the event-info ConfigReport | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 | | | +| Other PICS | C_AG_OXP_010, C_AG_OXP_181, C_AG_BPM_003 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with a result = accepted-unknown-config.
    3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. Check ConfigObject ( ConfigReport → ConfigObjectList (ConfigObject)).
    IF C_AG_BPM_003 THEN Pulse Object numeric Object is present, ELSE it is not present. | | | +| Pass/Fail criteria | The configuration event report must be confirmed. | | | +| Notes | | | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-013 | | | +| TP label | MDS objects events for Blood Pressure PHD | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | MDSEvents 9; M | MDSEvents 10; M | +| | | MDSEvents 12; M | MDSEvents 13; M | +| | | MDSEvents 15; M | MDSEvents 16; M | +| | | | BldServ_2; M | +| Test purpose | Check that:
    Agent-initiated mode is supported for measurement data transmission and all types of event reports are used in confirmed mode
    [AND]
    The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [OR]

    The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar

    [OR]

    The PHD sends the MDS-Dynamic-Data-Update-MP-Fixed using a confirmed event report and it includes the event-info ScanReportInfoMPFixed

    [OR]

    The PHD sends the MDS-Dynamic-Data-Update-MP-Var using a confirmed event report and it includes the event-info ScanReportInfoMPVar

    | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189) | +| Other PICS | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | +| Test procedure |
    1. Take measurements for every supported object in the PHD under test.
    2. Wait to receive every event report and check:
      1. message
        • field- type = Event Report
        • field-length = 2 bytes
        • field- value=0x01 0x01 (EventReportArgumentSimple, confirmed).

    This field identifies the type of message sent by the PHD, for the confirmed event configuration, roiv-cmip-confirmed-event-report.

    | +| Pass/Fail criteria |

    Check that every received report is a one of the following Data APDU and that it is confirmed:

    • • MDC_NOTI_SCAN_REPORT_FIXED
    • • MDC_NOTI_SCAN_REPORT_MP_FIXED
    • • MDC_NOTI_SCAN_REPORT_VAR
    • • MDC_NOTI_SCAN_REPORT_MP_VAR
    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-014 | | | +| TP label | Config Changes Service. Contextual Attribute. | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 8; M | | +| Test purpose |

    Check that:

    Service component reports configuration changes to future measurements only

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 AND C_AG_BPM_004 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. Take some measurements with the PHD under test.
    2. Make a change to the contextual attribute Unit-Code for the Sys/Dias/MAP object.
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 3. The PHD shall send an MDS event report indicating the new contextual attribute value.
    2. 4. Take some more measurements.
    3. 5. Wait for the PHG to receive new event reports from the PHD which report the measurements from step 4.
    | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the contextual attribute that has been changed.
    • • Data has changed accordingly to a new contextual attribute.
    | +| Notes | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/BPM/BV-015 | | | +| TP label | Operating State. PHG to PHD Maximum APDU Size | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] | | +| | Testable items | CommonCharac 3; M | | +| | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | ComCh_2; M | | +| Test purpose |

    Check that:

    Check that the total size of the response do not exceed of the maximum APDU size established by the specialization

    [AND]

    A PHD according to this definition shall be capable of receiving an APDU up to the size of at least Nrx. For this standard it is Nrx = 224 octets

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_177 | | | +| Other PICS | C_AG_OXP_041, C_AG_OXP_100 | | | +| Initial condition | The simulated PHG and the PHD are in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHG issues a "Remote Operation Invoke Get" command with:
      1. a. Obj-handle set to 0 (to request for MDS object)
      2. b. attribute-id-list.count = 103
      3. c. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 34 times followed by an additional MDC_ATTR_ID_MODEL.
    2. 2. Check the response of the PHD.
    3. 3. The simulated PHG issues "Remote Operation Invoke Get" command with the handle set to 0 (to request for MDS object) and an empty attribute-id-list to indicate all attributes.
    4. 4. Check the response of the PHD.
    | | | +| Pass/Fail criteria |
    • • In step 2, the PHD under test may respond with a rors-cmip-get listing all the requested attributes, or with a roer message. If PICS C_AG_OXP_100 =TRUE and the PHD does not respond with a rors-cmip-get message, it responds with a roer message or a rorj(resource-limitation) message, a WARNING will appear.
      • If the response is a get response, the total size of the response cannot exceed the sum of the APDU sizes of the supported specializations (limited to an absolute limit of 64512 octets):
        • ○ Pulse oximeter -> 9216 octets
    | | | + +| | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ○ Weighing scales -> 896 octets
    • ○ Glucose meter -> 5120 octets or 64512 octets if the PHD supports PM-Store
    • ○ Blood pressure -> 896 octets
    • ○ Thermometer -> 896 octets
    • ○ Independent activity hub -> 5120 octets
    • ○ Cardiovascular -> 64512 octets or 6624 octets if the PHD under test only supports Step Counter Profile
    • ○ Strength -> 64512 octets:
    • ○ Adherence monitor -> 1024 octets
    • ○ Peak flow -> 2030 octets
    • ○ Body composition analyser -> 7730 octets
    • ○ Basic ECG/Simple ECG -> 7168 octets or 64512 octets if the PHD supports PM-Store
    • ○ Basic ECG/Heart Rate -> 1280 octets or 64512 octets if the PHD supports PM-Store
    • ○ International Normalized Ratio -> 896 octets or 64512 if PHD supports PM-Store
    • ○ In case it responds with a roer, the reason must not be protocol-violation (23).
    • • In step 4, the PHD must respond with a rors-cmip-get message.
    | +| Notes | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12): *ETSI drafting rules*. +- [b-PHD PICS & PIXIT] Personal Health Device DG2016 PICS and PIXIT excel sheet v1.11. + +- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9. + +- [b-TCRL] Test Case Reference List\_DG2016\_v1.11 + +- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8 + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.845.5-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.845.5-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca0dce65df64f4fb10a81b8f87284f793e4b1d3d --- /dev/null +++ b/marked/H/T-REC-H.845.5-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e92e387e62cb6d86114f61d012b89bb4f66ab5171494a2177d9dfd36f6a2a566 +size 4206 diff --git a/marked/H/T-REC-H.845.5-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.5-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..533233f9d45068308adaa9c337b9aac70d69ccd4 --- /dev/null +++ b/marked/H/T-REC-H.845.5-201704-I_PDF-E/raw.md @@ -0,0 +1,780 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.845.5** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 5E: Thermometer** + +Recommendation ITU-T H.845.5 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.845.5 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5E: Thermometer + +## Summary + +Recommendation ITU-T H.845.5 provides a test suite structure (TSS) and the test purposes (TP) for thermometers in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.845.5 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5E: Device Specializations. Personal Health Device (Thermometer) (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.845.5 | 2015-01-13 | 16 | 11.1002/1000/12266 | +| 2.0 | ITU-T H.845.5 | 2016-07-14 | 16 | 11.1002/1000/12942 | +| 3.0 | ITU-T H.845.5 | 2017-04-13 | 16 | 11.1002/1000/13223 | + +## Keywords + +Conformance testing, continua design guidelines, e-health, IEEE 11073 device specialization, ITU-T H.810, personal area network, personal connected health devices, personal health devices interface, thermometer, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|--------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Test suite structure (TSS) ..... | 5 | +| 7 | Electronic attachment ..... | 7 | +| Annex A | Test purposes ..... | 8 | +| A.1 | TP definition conventions..... | 8 | +| A.2 | Subgroup 1.3.5: Thermometer (TH)..... | 9 | +| | Bibliography..... | 23 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5E: Device Specializations. Personal Health Device (Thermometer) (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.2 | 2012-10-05 | Initial release for Test Tool DG2011. This is the same version as "TSS&TP_1.5_PAN-LAN_PART_5E_v1.2.doc" because new features included in [b-CDG 2011] do not affect the test procedures specified in this document. | +| 1.3 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_PAN-LAN_PART_5E_v1.2.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • max APDU size for GM, BCA and ECG
    | +| 1.4 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5E_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • Adds glucose meter BLE
    • Adds BLE SSP support
    • Adds NFC new transport
    • Adds INR device specialization
    | +| 1.5 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5E_v1.4.doc" as a baseline and adds new features included in Documentation Enhancements:
    • "Other PICS" row added
    | +| 1.5 | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_5E_v1.4.doc" because new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015] do not affect the test procedures specified in this document. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5E_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016] | + +## Recommendation ITU-T H.845.5 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5E: Thermometer + +## 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 5, subpart 5E. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - **Part 5E: Thermometer** + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [ISO/IEEE 11073-10408] ISO/IEEE 11073-10408-2008, *Health informatics – Personal health device communication – Device specialization – Thermometer*. + +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|----------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | + +| | | +|-------|-------------------------------------------------------| +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCHA | Personal Connected Health Alliance | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 1.3.5 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - **Subgroup 1.3.5: Thermometer (TH)** + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + +- Subgroup 2.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 2.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# **7 Electronic attachment** + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case: + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth Low Energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing: + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 1.3.5: Thermometer (TH) + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/PLT/PHD/CLASS/TH/BV-000 | | | +| TP label | Get MDS Object for Thermometer specialization: Mandatory, Conditional and Optional Attributes. PHD real-time clock | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | MDS_Obj_Atrib1; M | MDS_Obj_Atrib2; M | +| | | MDS_Obj_Atrib4; M | MDS_Obj_Atrib5; R | +| | | MDS_Obj_Atrib7; R | MDS_Obj_Atrib8; R | +| | | MDS_Serv1; M | MDS_Serv3; M | +| | | TH_CM Operat1; M | Thermometer DIM2; M | +| Test purpose | Check that:
    The Personal Health Device (PHD) supports a Get command that requests all attributes
    [AND]
    The MDS Object contains the attributes specified for a Thermometer PHD | | | +| Applicability | C_AG_OXP_171 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_181 | | | +| Initial condition | The simulated Personal Health Gateway (PHG) and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0 (to request for MDS object) and the attribute-id-list set to 0 to indicate all attributes.
    2. The PHD responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object:
      MDS Attributes:
      1. Mandatory attribute Dev-Configuration-Id
        • IF NOT C_AG_OXP_181 then attribute-value = 0x0320 (800)
        • IF C_AG_OXP_181 then attribute-value = < between 0x4000 and 0x7FFF >
      2. Attribute System-Type not present.
      3. Mandatory attribute System-Type-Spec-List
        • attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST
        • attribute-type = TypeVerList
        • attribute-value.length = 4 bytes for each specialization supported
        • attribute-value = {MDC_DEV_SPEC_PROFILE_TEMP , 1} must be found on the list
      4. Mandatory attribute System-model
        • attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)
        • attribute-type = SystemModel
        • attribute-value.length = <Variable>
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value ={Manufacturer, Model}
    • e. IF Recommended Power-Status attribute is present:
      • attribute-id = MDC_ATTR_POWER_STAT
      • attribute-type = PowerStatus
      • attribute-value.length = 2 bytes
      • attribute-value = ON_MAINS (0x8000) or ON_BATTERY(0x4000), but both bits cannot be active at the same time.
        • Only one of the following may be active:
          • ▪ chargingFull(8),
          • ▪ chargingTrickle(9),
          • ▪ chargingOff(10).
          • ▪ The rest of the bits must not be set
    • f. IF Recommended Battery-Level attribute is present
      • attribute-id = MDC_ATTR_VAL_BATT_CHARGE
      • attribute-type = INT-U16
      • attribute-value.length = 2 bytes
      • attribute-value = <value between 0 and 100> If value >100, the meaning of the value is "undefined"
    • g. IF Recommended Remaining-Battery-Time attribute is present:
      • attribute-id = MDC_ATTR_TIME_BATT_REMAIN
      • attribute-type = BatMeasure
      • attribute-value.length = 6 bytes
      • attribute-value = <4 bytes to define the value. 2 remaining bytes to define the units, which shall be set to one of: MDC_DIM_MIN (0x08 0xA0), MDC_DIM_HR (0x08 0xC0), MDC_DIM_DAY (0x08 0xE0) >
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|----------------------|-------------------------------------------------------------------|------------------------|-------------------|------------------| +| TP Id | TP/PLT/PHD/CLASS/TH/BV-002 | | | | +| TP label | MDS objects events, Association procedure | | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | | +| | Testable items | MDS_Obj_Ev1; M | MDS_Obj_Ev3; M | MDS_Obj_Ev5; M | +| | | MDS_Obj_Ev6; M | TH_Serv_Model2; M | TH_CM_Assoc1; M | +| | | TH_CM_Assoc2; M | TH_CM_Assoc3; M | TH_CM_Assoc4; M | +| | | TH_CM_Assoc5; M | TH_CM_Assoc6; M | TH_CM_Assoc7; M | +| | | TH_CM_Assoc8; M | TH_CM_Assoc9; M | TH_CM_Assoc11; M | +| | | TH_CM_Assoc12; M | TH_CM_Assoc13; M | | +| Test purpose | Check that:
    The association procedure data exchange is correct | | | | +| Applicability | C_AG_OXP_171 AND C_AG_OXP_000 | | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | C_AG_OXP_002, C_AG_OXP_017, C_AG_OXP_181 | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | +| Test procedure |
    1. 1. The PHD sends a message to associate with the simulated PHG, the expected fields sent by the PHD are:
      1. a. APDU Type
        1. field- type = AarqApdu
        2. field-length =2 bytes
        3. field-value =0xE2 0x00.
      2. b. assoc-version
        1. field- type = AssociationVersion
        2. field-length =BITS-32
        3. field- value=0x80 0x00 0x00 0x00
      3. c. data-proto-id
        1. field- type = DataProtoId (INT-U16)
        2. field-length =2 bytes
        3. field- value=0x50 0x79 (20601)
      4. d. protocol-version
        1. field- type = Protocol Version
        2. field-length = 4 bytes
        3. field- value=0x80 0x00 0x00 0x00
      5. e. encoding rules
        1. field- type = EncodingRules
        2. field-length = 2 bytes
        3. field- value =
          1. ▪ Bit 0 must be set (support MDER)
          2. ▪ Bits 1 and 2 may be set
          3. ▪ The rest of the bits must be 0
      6. f. nomenclature version
        1. field- type = NomenclatureVersion
        2. field-length = 4 bytes
        3. field- value=0x80 0x00 0x00 0x00
        4. This value indicates version 1 is supported (nom-version1(0) is set).
      7. g. functional-units
        1. field- type = FunctionalUnits
        2. field-length = 4 bytes
        3. field-value =
          1. ▪ Bit 0 must not be set
      8. h. System type
        1. field- type = SystemType
        2. field-length = 4 bytes
        3. field- value = 0x00 0x80 0x00 0x00 (sys-type-agent)
      9. i. System-Id
        1. field- type = OCTET STRING
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 8 bytes
    • field- value = 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX (octet string length = 8 UI-64 manufacturer and device )
    • This value will be System Id attribute of MDS Object.

    j. dev-config-id

    • field- type = ConfigId(INT-U16)
    • field-length = 2 bytes
    • field- value =
      • ▪ IF NOT C_AG_OXP_181 then attribute-value = 0x0320 (800)
      • ▪ ELSE <between 0x40 0x00 and 0x7F 0xFF >

    k. data-req-mode-flags (DataReqModeCapab)

    • field- type = DataReqModeFlags
    • field-length = 2 bytes
    • If the PHD supports agent-initiated measurement transfer → Bit 15 is set (data-req-supp-init-agent(15))
    • If PHD supports requesting objects based on object handle →Bit 6 will be set (data-req-supp-scope-handle(6)).
    • If PHD supports single response →Bit 8 will be set (data-req-supp-mode-single-rsp(8)).
    • If PHD supports time unlimited data request →Bit 10 will be set (data-req-supp-mode-time-no-limit(10)).

    l. data-req-init-agent-count (DataReqModeCapab)

    • field- type = INT-U8
    • field-length = 2 bytes
    • field.value = 0x01

    m. data-req-init-manager-count (DataReqModeCapab)

    • field- type = INT-U8
    • field-length = 2 bytes
    • field.value = 0x00
    | +| Pass/Fail criteria | All checked attributes have proper values. | +| Notes | | + +| | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/TH/BV-003 | | | +| TP label | MDS Configuration objects events for thermometer PHD | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | MDS_Obj_Ev7; M | TH_CM_Config 1; M | +| Test purpose | Check that:
    Thermometer sends the MDS-Configuration-Event using a Confirmed event report and it includes the event-info ConfigReport | | | +| Applicability | C_AG_OXP_171 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_010, C_AG_OXP_181 | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG:
      1. a. APDU Type
        1. field- type = PrstApdu
        2. field-length =2 bytes
        3. field-value =0xE7 0x00
      2. b. invoke-id
        1. field- type = InvokeIDType
        2. field-length =INT-U16
        3. field- value=<Not relevant for this test>
      3. c. message
        1. field- type = roiv-cmip-confirmed-event-report
        2. field-length =two bytes
        3. field- value=0x01 0x01 (EventReportArgumentSimple)
      4. d. obj-handle (EventReportArgumentSimple)
        1. field- type = HANDLE
        2. field-length =INT-U16
      5. e. event-time (EventReportArgumentSimple)
        1. field- type = Relative Time
        2. field-length =INT-U32
        3. field-value =
          • ▪ IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF
      6. f. event-type (EventReportArgumentSimple)
        1. field- type = OID-Type
        2. field-length =INT-U16
        3. field- value=0x0D 0x1C (MDC_NOTI_CONFIG)
      7. g. config-report-id (ConfigReport)
        1. field- type = ConfigId
        2. field-length = INT-U16
          • ▪ field- value = IF NOT C_AG_OXP_181 then 0x02 0xBC
          • ▪ ELSE <between 0x40 0x00 and 0x7F 0xFF >
      8. h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject))
        1. field- type = OID-Type
        2. field-length = INT-U16
        3. field- value = One or more of MDC_MOC_VMO_METRIC_NU must appear
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/TH/BV-004 | | | +| TP label | MDS objects events for thermometer PHD | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | MDS_Obj_Ev9; C | MDS_Obj_Ev11; C | +| | | MDS_Obj_Ev13; C | MDS_Obj_Ev14; M | +| | | MDS_Obj_Ev16; M | MDS_Obj_Ev17; M | +| | | TH_CM Operat 4; M | TH_Serv_ModelX; O | +| Test purpose |

    Check that:

    Agent-initiated mode is supported for measurement data transmission and all types of event reports are used in confirmed mode

    [AND]

    The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed

    [OR]

    The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar

    [OR]

    The PHD sends the MDS-Dynamic-Data-Update-MP-Fixed using a confirmed event report and it includes the event-info ScanReportInfoMPFixed

    [OR]

    The PHD sends the MDS-Dynamic-Data-Update-MP-Var using a confirmed event report and it includes the event-info ScanReportInfoMPVar

    | | | +| Applicability | C_AG_OXP_171 AND C_AG_OXP_000 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189) | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take measurements for every supported object in the PHD under test.
    2. 2. Wait to receive every event report and check:
      1. a. message
        • field- type = Event Report
        • field-length = 2 bytes
        • field- value=0x01 0x01 (EventReportArgumentSimple, confirmed)

    This field identifies the type of message sent by the PHD, for the confirmed event configuration, roiv-cmip-confirmed-event-report.

    | | | +| Pass/Fail criteria |

    Check that every received report is one of the following Data APDU and that it is confirmed:

    • • MDC_NOTI_SCAN_REPORT_FIXED
    • • MDC_NOTI_SCAN_REPORT_MP_FIXED
    • • MDC_NOTI_SCAN_REPORT_VAR
    • • MDC_NOTI_SCAN_REPORT_MP_VAR
    | | | +| Notes | | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/PLT/PHD/CLASS/TH/BV-005_A | | | +| TP label | Get Temperature Numeric Object attributes (Mandatory, Conditional and Optional), Standard configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp1; M | Num Objec Temp3; M | +| | | Num Objec Temp5; M | Num Objec Temp6; M | +| | | Num Objec Temp9; M | Num Objec Temp10; R | +| | | Num Objec Temp13; R | Num Objec Temp14; R | +| | | Num Objec Temp17; M | Num Objec Temp18; R | +| | | Num Objec Temp20; R | Num Objec Temp21; C | +| | | Num Objec Temp24; R | | +| Test purpose | Check that:
    Temperature Object contains the attributes specified for Standard Configuration | | | +| Applicability | (C_AG_OXP_171) AND (NOT C_AG_OXP_181) AND C_AG_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test have been associated, but the PHD configuration is unknown to the simulated PHG, so the PHD and the simulated PHG will be in the Configuring state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with a result = accepted-unknown-config
    3. 3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. Check that the field Dev-Config-Id is set to 0x0320 (800). If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id equal to 0x032 is received.
    5. 5. Wait until the PHD under test has sent a standard configuration.
    6. 6. The body temperature object must be defined in the configuration event report, and its attributes must be:
      1. a. Mandatory attribute Handle
        1. attribute-id = MDC_ATTR_ID_HANDLE
        2. attribute-type = HANDLE
        3. attribute-value = 1
      2. b. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = 0x00 0x02(MDC_PART_SCADA) , 0x05 0x0C (MDC_TEMP_BODY)
      3. c. Mandatory attribute Metric-Spec-Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. ▪ Bit 0 (mss-avail-intermittent) must be set.
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ Bit 1 (mss-avail-stored-data) must be set.
    • ▪ Bit 2 (mss-upd-aperiodic) must be set.
    • ▪ Bit 3 (mss-msmt-aperiodic) must be set.
    • ▪ Bit 9 (mss-acc-agent-initiated) must be set.
    • ▪ Bits 6, 7, 10, 11 and 15 must not be set

    d. Mandatory attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type(INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_DEGC

    e. Mandatory attribute Attribute-Value-Map

    • attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP Arterial Pressure
    • attribute-type = AttrValMap (sequence of attribute-id(OID-Type)
    • attribute-length= 12 bytes
    • If the configuration is standard: attribute-value map.length = 8 bytes
    • If the configuration is standard: attribute-value = 0x0A 0x4C 0x00 0x02 MDC_ATTR_NU_VAL_OBS_BASIC,MDC_ATTR_TIME_STAMP_ABS, attribute-id is the identifier for the attribute that are to be reported in fixed format (that are "described" in Attribute-Value-Map) and the length is the length for this attribute, for example: MDC_ATTR_TIME_STAMP_ABS (AbsoluteTime data type)will be composed by 8 fields INT-U8 , this length is 8 bytes(0x00 0x08).

    7. Check that no other attributes are present in the initial configuration.

    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------|---------------------| +| TP Id | TP/PLT/PHD/CLASS/TH/BV-005_B | | | | +| TP label | Get Temperature Numeric Object attributes (Mandatory, Conditional and Optional), Extended configuration | | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | | +| | Testable items | Num Objec Temp3; M | Num Objec Temp5; M | Num Objec Temp7; M | +| | | Num Objec Temp8; R | Num Objec Temp9; M | Num Objec Temp10; R | +| | | Num Objec Temp11; R | Num Objec Temp13; R | Num Objec Temp16; M | +| | | Num Objec Temp23; R | Num Objec Temp18; R | Num Objec Temp20; R | +| Test purpose | Check that:
    Temperature Object contains the attributes specified for Extended Configuration | | | | +| Applicability | (C_AG_OXP_171) AND (C_AG_OXP_181) AND C_AG_OXP_000 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test have been associated, but the PHD configuration is unknown to the simulated PHG, so the PHD and the simulated PHG will be in the Configuring state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test. | | | | + +2. The simulated PHG responds with a result = accepted-unknown-config +3. The PHD responds with a "Remote Operation Invoke | Confirmed Event Report" message with an MDC\_NOTI\_CONFIG event to send its configuration to the PHG. +4. Check that the field Dev-Config-Id is in the extended range.. If it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received. +5. Wait until the PHD under test has sent an extended configuration. +6. The body temperature object must be defined in the configuration event report, and its attributes must be: + +#### a. Mandatory attribute Handle + +- attribute-id = MDC\_ATTR\_ID\_HANDLE +- attribute-type = HANDLE +- attribute-value = + +#### b. Mandatory attribute Type + +- attribute-id = MDC\_ATTR\_ID\_TYPE +- attribute-type = TYPE +- attribute-value = 0x00 0x02(MDC\_PART\_SCADA) , (MDC\_TEMP\_zzz), as per the following list: + +| MDC_TEMP_zzz | 0xXX 0xYY | Temperature Type | +|-----------------|--------------------|--------------------------------------| +| MDC_TEMP_AXILLA | 0xE0 0x24 (57380) | Axillary (armpit) | +| MDC_TEMP_BODY | 0x4B 0x5C (19292) | General body temperature measurement | +| MDC_TEMP_EAR | 0xE0 0x0C (57356) | Ear (usually earlobe) | +| MDC_TEMP_FINGER | 0xE0 0x10 (57360 ) | Finger | +| MDC_TEMP_GIT | 0xE0 0x28 (57384 ) | Gastro-intestinal tract | +| MDC_TEMP_ORAL | 0xE0 0x08 (57352 ) | Mouth | +| MDC_TEMP_RECT | 0xE0 0x04 (57348 ) | Rectum | +| MDC_TEMP_TOE | 0xE0 0x20 (57376 ) | Toe | +| MDC_TEMP_TYMP | 0x4B 0x78 (19320 ) | Tympanum (ear drum) | + +#### c. Mandatory attribute Metric-Spec-Small + +- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL +- attribute-type = MetricSpecSmall (BITS-16) +- attribute-value ≠ 0x00 0x00 + - Bit 0 (mss-avail-intermittent) must be set. + - Bit 1 (mss-avail-stored-data) must be set. + - Bit 3 (mss-msmt-aperiodic) must be set. + - Bit 9 (mss-acc-agent-initiated) must be set. + +#### d. Mandatory attribute Unit-Code + +- attribute-id = MDC\_ATTR\_UNIT\_CODE +- attribute-type = OID-Type(INT-U16) +- attribute-value.length = 2 bytes +- attribute-value = MDC\_DIM\_DEGC (0x17 0xA0) OR MDC\_DIM\_FAHR (0x11 0x40) + +#### e. IF Not Recommended attribute Supplemental-Types + +- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES + +- attribute-type = SupplementalTypeList +- attribute-value.length = Sequence of TYPE (TYPE.length= 4 bytes) + - attribute-value = + +#### f. IF Not Recommended attribute Metric-Structure-Small + +- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL +- attribute-type = MetricStructureSmall +- attribute-value.length = 2 bytes +- attribute-value = + - ms-struct = one of the following: + - ms-struct-simple (0x01) + - ms-struct-compound (0x02) + - ms-struct-reserved (0x03) + - ms-struct-compound-simple (0x04) + - ms-compound-no = one of the following: + - IF ms-struct = ms-struct-simple THEN = 0 + - ELSE = maximum number of components in a compound value + +#### g. IF Recommended attribute Measurement-Status is present + +- attribute-id = MDC\_ATTR\_MSMT\_STAT +- attribute-type = MeasurementStatus +- attribute-value.length = 2 bytes + +#### h. Only one attribute of Metric-Id and Metric-Id-List shall be present. + +#### i. IF attribute Metric-Id is present + +- attribute-id = MDC\_ATTR\_ID\_PHYSIO +- attribute-type = OID-Type +- attribute-value.length = INT-U16 +- attribute-value = + +#### j. IF Not Recommended attribute Metric-Id-List is present + +- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS +- attribute-type = MetricIdList +- attribute-value.length= SEQUENCE OF OID-Type (INT-U16) +- attribute-value = + - The [Metric-Id-List] attribute shall be used if a compound observed value is used, which does not incorporate the Metric-Id directly. The order of the Metric-Id-List shall correspond to the order of the elements in the compound observed value. Only one attribute of Metric-Id and Metric-Id-List shall be present. + +#### k. IF attribute Metric-Id-Partition is present + +- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART +- attribute-type = NomPartition +- attribute-value.length = INT-U16 +- attribute-value = one of the next + - nom-part-unspec (0x00 0x00) + - nom-part-obj (0x00 0x01) + - nom-part-metric (0x00 0x02) + - nom-part-alert (0x00 0x03) + - nom-part-dim (0x00 0x04) + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ nom-part-vattr (0x00 0x05)
    • ▪ nom-part-pgrp (0x00 0x06)
    • ▪ nom-part-sites (0x00 0x07)
    • ▪ nom-part-infrastruc (0x00 0x08)
    • ▪ nom-part-fef (0x00 0x09)
    • ▪ nom-part-ecg-extn (0x00 0x0A)
    • ▪ nom-part-phd-dm (0x00 0x80)
    • ▪ nom-part-phd-hf (0x00 0x81)
    • ▪ nom-part-phd-ai (0x00 0x82)
    • ▪ nom-part-ret-code(0x00 0xFF)
    • ▪ nom-part-ext-nom (0x01 0x00)
    • ▪ nom-part-priv (0x04 0x00)

    l. IF Not Recommended attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE
    • attribute-value.length = INT-U16
    • attribute-value = Handle value of the associated object.

    m. IF Recommended attribute Accuracy is present

    • attribute-id = MDC_ATTR_NU_ACCUR_MSMT
    • attribute-type = FLOAT-Type (INT-U32)
    • attribute-value.length = FLOAT-Type (INT-U32)
    • attribute-value = <Not Relevant for this test>

    n. IF Not Recommended attribute Measure-Active-Period is present

    • attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE
    • attribute-type = FLOAT-Type
    • attribute-value.length = INT-U32
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/TH/BV-006 | | | +| TP label | Sample period for measurements | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | MDS_Obj_Ev10 | | +| Test purpose | Check that:
    MDS events for temperature readings is not sent no faster than 1/second | | | +| Applicability | C_AG_OXP_171 AND C_AG_OXP_000 | | | +| Other PICS | C_AG_OXP_032 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take some measurements as quickly as possible. | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. Wait for the simulated PHG to receive the event reports and record the arriving time:

    IF C_AG_OXP_032

    3. Disconnect the PHD under test from the simulated PHG.

    4. Take some measurements with the PHD under test while is disconnected.

    5. Connect the PHD to the simulated PHG.

    6. Wait until the PHD starts to send its measurements to the simulated PHG.

    | +| Pass/Fail criteria | The interval between event reports cannot be less than 1 second in both cases. | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/TH/BV-015 | | | +| TP label | Config Changes Service. Contextual Attribute. | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 8; M | | +| Test purpose |

    Check that:

    Service component reports configuration changes to future measurements only

    | | | +| Applicability | C_AG_OXP_171 AND C_AG_TH_003 AND C_AG_OXP_000 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take some measurements with the PHD under test.
    2. 2. Make a change to the contextual attribute Unit-Code for the Temperature object.
    3. 3. The PHD shall send a MDS event report indicating the new contextual attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD which report the measurements from step 4.
    | | | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the contextual attribute that has been changed.
    • • Data has changed accordingly to new contextual attribute.
    | | | + +| | | | | +|-----------------|-----------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/TH/BV-016 | | | +| TP label | Operating State. PHG to PHD Maximum APDU Size | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 3; M | | +| | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | TH_CM_Charac2; M | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    The total size of the response do not exceed of the maximum APDU size established by the specialization

    [AND]

    A PHD according to this definition shall be capable of receiving an APDU up to the size of at least Nrx. For this standard it is Nrx = 224 octets

    | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_171 | +| Other PICS | C_AG_OXP_041, C_AG_OXP_100 | +| Initial condition | The simulated PHG and the PHD are in the Operating state. | +| Test procedure |
    1. 1. The simulated PHG issues a "Remote Operation Invoke Get" command with:
      1. a. Obj-handle set to 0 (to request for MDS object)
      2. b. attribute-id-list.count = 103
      3. c. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 34 times followed by an additional MDC_ATTR_ID_MODEL
    2. 2. Check the response of the PHD.
    3. 3. The simulated PHG issues a "Remote Operation Invoke Get" command with the handle set to 0 (to request for MDS object) and an empty attribute-id-list to indicate all attributes.
    4. 4. Check the response of the PHD.
    | +| Pass/Fail criteria |
    • • In step 2, the PHD under test may respond with a rors-cmip-get listing all the requested attributes, or with a roer message. If PICS C_AG_OXP_100 = TRUE and the PHD does not respond with a rors-cmip-get message, but it responds with a roer message or rorj(resource-limitation) message, a WARNING will appear.
      • ○ If the response is a get response, the total size of the response cannot exceed the sum of the APDU sizes of the supported specializations (limited to an absolute limit of 64512 octets):
        • ▪ Pulse oximeter → 9216 octets
        • ▪ Weighing scales → 896 octets
        • ▪ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store
        • ▪ Blood pressure → 896 octets
        • ▪ Thermometer → 896 octets
        • ▪ Independent activity hub → 5120 octets
        • ▪ Cardiovascular → 64512 octets or 6624 octets the PHD under test only supports Step Counter Profile
        • ▪ Strength → 64512 octets:
        • ▪ Adherence monitor → 1024 octets
        • ▪ Peak flow → 2030 octets
        • ▪ Body composition analyser → 7730 octets
        • ▪ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store
        • ▪ Basic ECG/Heart Rate → 1280 octets or 64512 octets if the PHD supports PM-Store
        • ▪ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store
      • ○ In the case where it responds with a roer, the reason must not be protocol-violation (23)
    • • In step 4, the PHD must respond with a rors-cmip-get message.
    | + +| | | +|--------------|--| +| Notes | | +|--------------|--| + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. +- [b-PHD PICS & PIXIT] Personal Health Device DG2016 PICS and PIXIT excel sheet v1.11. + +- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9. + +- [b-TCRL] Test Case Reference List\_DG2016\_v1.11 + +- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8 + + + + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.845.6-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.6-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1b205fb7c9624b975b0e929a1cd252b25096e3b5 --- /dev/null +++ b/marked/H/T-REC-H.845.6-201704-I_PDF-E/raw.md @@ -0,0 +1,2047 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.845.6** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 5F: Cardiovascular fitness and activity +monitor** + +Recommendation ITU-T H.845.6 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.845.6 + +# Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5F: Cardiovascular fitness and activity monitor + +## Summary + +Recommendation ITU-T H.845.6 provides a test suite structure (TSS) and the test purposes (TP) for cardiovascular fitness and activity monitors in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.845.6 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5F: Device Specializations. Personal Health Device (Cardiovascular) (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.845.6 | 2015-01-13 | 16 | 11.1002/1000/12267 | +| 2.0 | ITU-T H.845.6 | 2016-07-14 | 16 | 11.1002/1000/12943 | +| 3.0 | ITU-T H.845.6 | 2017-04-13 | 16 | 11.1002/1000/13224 | + +## Keywords + +Cardiovascular fitness and activity monitor, conformance testing, Continua Design Guidelines, e-health, IEEE 11073 device specialization, ITU-T H.810, personal area network, personal connected health devices, touch area network, WAN interface. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|--------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Test suite structure (TSS) ..... | 5 | +| 7 | Electronic attachment ..... | 7 | +| Annex A | Test purposes ..... | 8 | +| A.1 | TP definition conventions..... | 8 | +| A.2 | Subgroup 1.3.6: Cardiovascular (CV) ..... | 9 | +| | Bibliography..... | 82 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5F: Device Specializations. Personal Health Device (Cardiovascular) (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.2 | 2012-10-05 | Initial release for Test Tool DG2011. This is the same version as "TSS&TP_1.5_PAN-LAN_PART_5F_v1.2.doc" because new features included in [b-CDG 2011] do not affect the test procedures specified in this document. | +| 1.3 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_PAN-LAN_PART_5F_v1.2.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • • Max APDU size for GM, BCA and ECG
    | +| 1.4 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5F_v1.4.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.5 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5F_v1.4.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row added
    | +| 1.5 | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_5F_v1.4.doc" because new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015] do not affect the test procedures specified in this document. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5F_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016] | + +## Recommendation ITU-T H.845.6 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5F: Cardiovascular fitness and activity monitor + +## 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 5, subpart 5F. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - **Part 5F: Cardiovascular fitness and activity monitor** + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + +- [ISO/IEEE 11073-10441] ISO/IEEE 11073-10441-2015, *Health informatics – Personal health device communication – Device specialization – Cardiovascular fitness and activity monitor*. + + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|---------------------| +| ATS | Abstract Test Suite | +| DUT | Device Under Test | + +| | | +|-------|-------------------------------------------------------| +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCT | Protocol Conformance Testing | +| PCO | Point of Control and Observation | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +## 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 1.3.6 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - **Subgroup 1.3.6: Cardiovascular (CV)** + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +###### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + +- Subgroup 2.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 2.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +## 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case: + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth Low Energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test: + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - GR>: This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing: + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 1.3.6: Cardiovascular (CV) + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|-------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-000 | | | | +| TP label | MDS Object for Cardiovascular fitness and activity monitor specialization | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | MDSAttr1; M | MDSAttr2; M | MDSAttr3; R | +| | | MDSAttr4; R | MDSAttr5; R | MDSAttr6; M | +| | | MDSAttr7; M | MDSAttr8; M | GETServ1; M | +| | | GETServ3; M | OperProc1; M | | +| Test purpose |

    Check that:

    The MDS Object contains the attributes specified for a Cardiovascular Personal Health Device (PHD)

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 | | | | +| Other PICS | C_AG_OXP_181 | | | | +| Initial condition | The PHD under test is in the Operating state. | | | | +| Test procedure |
    1. 1. The simulated Personal Health Gateway (PHG) issues a "roiv-cmip-get" command with the handle set to 0 (to request an MDS object) and the attribute-id-list is set to 0 to indicate all attributes.
    2. 2. The PHD responds with a "rors-cmip-get" service message in which the attribute-list contains a list of all implemented attributes of the MDS object:
      1. a. Mandatory attribute Dev-Configuration-Id
        • attribute-type = ConfigId
        • attribute-length = 2 bytes
        • attribute-value = < between 0x4000 and 0x7FFF >
      2. b. Attribute System-Type shall not be present.
      3. c. Mandatory attribute System-model
        • attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)
        • attribute-type = SystemModel
        • attribute-value.length = <Variable>
        • attribute-value = {Manufacturer, Model}
      4. d. Mandatory attribute System-Type-Spec-List
        • attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST
        • attribute-type = TypeVerList
        • attribute-value.length = 4 bytes
        • attribute-value = { MDC_DEV_SPEC_PROFILE_HF_CARDIO (0x10 0x29), 1 }
      5. e. If Recommended Power-Status attribute is present:
        • attribute-id = MDC_ATTR_POWER_STAT
        • attribute-type = PowerStatus
        • attribute-value.length = 2 bytes
        • attribute-value =
          • ON_MAINS (0x8000) or ON_BATTERY(0x4000)
          • • Only one of the following may be active:
          • • chargingFull(8),
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • chargingTrickle(9),
    • • chargingOff(10).

    f. If Recommended Battery-Level attribute is present

    • attribute-id = MDC_ATTR_VAL_BATT_CHARGE
    • attribute-type = BITS-16
    • attribute-value.length = 2 bytes
    • attribute-value = <value between 0 and 100> If value >100, the meaning of the value is "undefined"

    g. If Recommended Remaining-Battery-Time attribute is present:

    • attribute-id = MDC_ATTR_TIME_BATT_REMAIN
    • attribute-type = BatMeasure
    • attribute-value.length = 6 bytes
    • attribute-value = <4 bytes to define the value. 2 remaining bytes to define the units, which shall be set to one of: MDC_DIM_MIN (0x08 0xA0), MDC_DIM_HR (0x08 0xC0), MDC_DIM_DAY (0x08 0xE0)>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-001 | | | +| TP label | MDS Configuration objects events for Cardiovascular. | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | MDSEvent1; M | AltitudeGain1; O | +| | | Altitude1; O | Distance1; O | +| | | DescentTime1; O | Latitude1; O | +| | | Slopes1; O | Speed1; O | +| | | Incline1; O | Heart rate1; O | +| | | Power1; O | Resistance1; O | +| | | Breathing rate1; O | Energy expended1; O | +| | | CarbohydrateCal1; O | SustainedPhysAct1; O | +| | | BodyWeight1; O | Height1; O | +| | | Session1; M | Sub-session 1; O | +| | | ProgramId1; O | | +| Test purpose | Check that:
    Cardiovascular PHD sends the MDS-Configuration-Event using a Confirmed event report and it includes the event-info ConfigReport | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 | | | +| Other PICS | C_AG_OXP_010, C_AG_CV_015, C_AG_CV_016, C_AG_CV_017, C_AG_CV_018, C_AG_CV_019, C_AG_CV_020, C_AG_CV_021, C_AG_CV_022, C_AG_CV_023, C_AG_CV_024, C_AG_CV_025, C_AG_CV_026, C_AG_CV_027, C_AG_CV_028, C_AG_CV_029, C_AG_CV_030, C_AG_CV_031, C_AG_CV_032, C_AG_CV_033, C_AG_CV_034, C_AG_CV_035, C_AG_CV_036, C_AG_CV_037, C_AG_CV_038, C_AG_CV_039, C_AG_CV_040, C_AG_CV_041, C_AG_CV_042, C_AG_CV_043 | | | +| Initial condition | The simulated PHG and the PHD under test are in the Configuring state. | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with a result = accepted-unknown-config
    3. The PHD responds with a "Remote Operation Invoke Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG: | | | + +- a. APDU Type + - field- type = PrstApdu + - field-length = 2 bytes + - field-value = 0xE7 0x00 +- b. invoke-id + - field- type = InvokeIDType + - field-length = INT-U16 + - field- value = +- c. message + - field- type = roiv-cmip-confirmed-event-report + - field-length = two bytes + - field- value = 0x01 0x01 (EventReportArgumentSimple) +- d. obj-handle (EventReportArgumentSimple) + - field- type = HANDLE + - field-length = INT-U16 +- e. event-time (EventReportArgumentSimple) + - field- type = Relative Time + - field-length = INT-U32 + - field-value = + - IF NOT C\_AG\_OXP\_010 THEN value = 0xFF 0xFF 0xFF 0xFF +- f. event-type (EventReportArgumentSimple) + - field- type = OID-Type + - field-length = INT-U16 + - field- value = 0x 0D 0x 1C (MDC\_NOTI\_CONFIG) +- g. config-report-id (ConfigReport) + - field- type = ConfigId + - field-length = INT-U16 + - field- value = +- h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject)) + - field- type = OID-Type + - field-length = INT-U16 + - field- value = Objects that will be checked: + - The Session Enumeration Object must appear. + - IF C\_AG\_CV\_015 Then Altitude Gain Numeric Object is present, ELSE it is not present. + - IF C\_AG\_CV\_016 Then Program identifier Enumeration Object is present, ELSE it is not present. + - IF C\_AG\_CV\_017 Then Activity Time Enumeration Object is present, ELSE it is not present. + - IF C\_AG\_CV\_018 Then Age Numeric Object is present, ELSE it is not present. + - IF C\_AG\_CV\_019 Then Height Numeric Object is present, ELSE it is not present. + - IF C\_AG\_CV\_020 Then Body Weight Numeric Object is present, ELSE it is not present. + - IF C\_AG\_CV\_021 Then Activity Intensity Numeric Object is present, ELSE + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    it is not present.

    • • IF C_AG_CV_022 Then Sustained Phys activity threshold Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_023 Then Carbohydrate calories Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_024 Then Calories ingested Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_025 Then Energy Expended Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_026 Then Breathing Rate Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_027 Then Stride Length Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_028 Then Resistance Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_029 Then Power Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_030 Then Max User Heart Rate Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_031 Then Heart Rate Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_032 Then Altitude Loss Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_033 Then Incline Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_034 Then Cadence Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_035 Then Speed Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_036 Then Slopes Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_037 Then Longitude Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_038 Then Latitude Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_039 Then Altitude Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_040 Then Distance Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_041 Then Ascent time and Distance Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_042 Then Descent time and Distance Numeric Object is present, ELSE it is not present.
    • • IF C_AG_CV_043 Then Sub-session Enumeration Object is present, ELSE it is not present.
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-002 | | | +| TP label | MDS object events for Cardiovascular fitness activity monitor PHD. | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | MDSEvent3; M | MDSEvent4; M | +| | | MDSEvent6; M | MDSEvent7; M | +| | | MDSEvent9; M | MDSEvent10; M | +| Test purpose |

    Check that:

    Agent-initiated mode is supported for measurement data transmission and all types of event reports are used in confirmed mode

    [AND]

    The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed

    [OR]

    The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar

    [OR]

    The PHD sends the MDS-Dynamic-Data-Update-MP-Fixed using a confirmed event report and it includes the event-info ScanReportInfoMPFixed

    [OR]

    The PHD sends the MDS-Dynamic-Data-Update-MP-Var using a confirmed event report and it includes the event-info ScanReportInfoMPVar

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189) | | | +| Other PICS | | | | +| Initial condition | The PHD under test is in the Operating state. | | | +| Test procedure |
    1. Take measurements for every supported object in the PHD under test.
    2. Wait to receive every event report and check:
      1. message
        1. field- type = Event Report
        2. field-length = 2 bytes
        3. field- value = 0x01 0x01 (EventReportArgumentSimple, confirmed)

    This field identifies the type of message sent by the PHD, for the confirmed event configuration, roiv-cmip-confirmed-event-report.

    | | | +| Pass/Fail criteria |

    Check that every received report is a one of the following Data APDU and that it is confirmed:

    • MDC_NOTI_SCAN_REPORT_FIXED
    • MDC_NOTI_SCAN_REPORT_MP_FIXED
    • MDC_NOTI_SCAN_REPORT_VAR
    • MDC_NOTI_SCAN_REPORT_MP_VAR
    | | | +| Notes | | | | + +| | | | | +|-----------------|------------------------------|------------------------|------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-005 | | | +| TP label | Altitude Gain Numeric Object | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | AltitudeGain2; M | AltitudeGain3; M | +| | | | AltitudeGain4; M | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|--| +| | | AltitudeGain5; M | AltitudeGain6; M | | +| Test purpose | Check that:
    The Altitude Gain Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_015 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config"
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Altitude Gain object shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_PHD_HF MDC_HF_ALT_GAIN
      2. b. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. • bit 0 (mss-avail-intermittent(0)) shall be set.
          2. • bit 1(mss-avail-stored-data(1)) shall be set.
          3. • bit 2 (mss-updt-aperiodic(2)) shall be set.
          4. • bit 3(mss-msmt-aperiodic(3)) shall be set
          5. • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          6. • The other bits have to be 0.
      3. c. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_X_M or MDC_DIM_X_FOOT
      4. d. Mandatory attribute Source-Handle-Reference
        1. attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        2. attribute-type = HANDLE (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    5. 5. IF C_AG_OXP_293:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        1. The PHG moves to Configuring/Sending Set Time substate and:
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • IF C_AG_OXP_009 it issues the Set-Time action command.
    • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.

    Once its internal time setting operation is completed, the PHD responds to the PHG.

    1. 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    2. 7. Take a measurement in the PHD.
    3. 8. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used, with zero (0) indicating that no altitude was gained.
    | +| Notes | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-005_A | | | +| TP label | Altitude Gain, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose |

    Check that:

    Altitude Gain Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_015 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Altitude Gain object.
    | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Altitude Gain object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Altitude Gain instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------|------------------------|------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-006 | | | +| TP label | Altitude Loss Numeric Object | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | AltitudeLoss2; M | AltitudeLoss3; M | +| | | AltitudeLoss5; M | AltitudeLoss6; M | +| Test purpose |

    Check that:

    The Altitude Loss Numeric object contains the attributes specified for Extended Configuration.

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_032 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHD under test is in the Unassociated state. | +| Test procedure |
    • 1. The simulated PHG receives an association request from the PHD under test.
    • 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config"
    • 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    • 4. The Altitude Loss object shall be:
      • a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_HF MDC_HF_ALT_LOSS
      • b. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • • bit 0 (mss-avail-intermittent(0)) shall be set.
          • • bit 1(mss-avail-stored-data(1)) shall be set.
          • • bit 2 (mss-updt-aperiodic(2)) shall be set.
          • • bit 3(mss-msmt-aperiodic(3)) shall be set
          • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          • • The other bits have to be 0.
      • c. Mandatory attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type (INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = MDC_DIM_X_M or MDC_DIM_X_FOOT
      • d. Mandatory attribute Source-Handle-Reference
        • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        • attribute-type = HANDLE (INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    • 5. IF C_AG_OXP_293:
      • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      • c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 it issues the Set-Time action command.
          • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    • 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    • 7. Take a measurement in the PHD.
    | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 8. Wait until the PHG receives an event report. | +| Pass/Fail criteria |
    • In step 4, all checked values are as specified.
    • In step 8, check that only non-negative values are used, with zero (0) indicating that no altitude was lost.
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-006_A | | | +| TP label | Altitude Loss, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:
    Altitude Loss Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_032 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Altitude Loss object. | | | +| Pass/Fail criteria |
    • The timestamp attribute used for Altitude Loss object shall be the same as that used for the associated Session or Sub-session object instance.
    • The Altitude Loss instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-007 | | | | +| TP label | Altitude Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Altitude1; O | +| | | Altitude2; M | Altitude3; M | Altitude4; M | +| | | Altitude5; M | | | +| Test purpose | Check that:
    The Altitude Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_039 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Altitude object shall be: | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. Mandatory attribute Type

    attribute-id = MDC_ATTR_ID_TYPE

    attribute-type = TYPE

    attribute-value = MDC_PART_PHD_HF MDC_HF_ALT

    b. Mandatory attribute Metric-Spec_Small

    attribute-id = MDC_ATTR_METRIC_SPEC_SMALL

    attribute-type = MetricSpecSmall (BITS-16)

    attribute-value ≠ 0x00 0x00

    • • bit 0 (mss-avail-intermittent(0)) shall be set.
    • • 1(mss-avail-stored-data(1)) shall be set.
    • • bit 2 (mss-updt-aperiodic(2)) shall be set.
    • • bit 3(mss-msmt-aperiodic(3)) shall be set
    • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
    • • The other bits have to be 0.

    c. Mandatory attribute Unit-Code

    attribute-id = MDC_ATTR_UNIT_CODE

    attribute-type = OID-Type (INT-U16)

    attribute-value.length = 2 bytes

    attribute-value = MDC_DIM_X_M or MDC_DIM_X_FOOT

    d. Mandatory attribute Source-Handle-Reference

    attribute-id = MDC_ATTR_SOURCE_HANDLE_REF

    attribute-type = HANDLE (INT-U16)

    attribute-value.length = 2 bytes

    attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-007_A | | | +| TP label | Altitude, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose |

    Check that:

    Altitude Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_039 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Altitude object.
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • The timestamp attribute used for the Altitude object shall be the same as that used for the associated Session or Sub-session object instance.
    • The Altitude instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-008 | | | +| TP label | Distance Numeric Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | Distance2; M | Distance 3; M | +| | | Distance 5; M | Distance 6; M | +| Test purpose | Check that:
    The Distance Numeric object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_040 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure |
    1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Distance object shall be:
      1. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_HF MDC_HF_DISTANCE
      2. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • bit 0 (mss-avail-intermittent(0)) shall be set.
          • bit 1(mss-avail-stored-data(1)) shall be set.
          • bit 2 (mss-updt-aperiodic(2)) shall be set.
          • bit 3(mss-msmt-aperiodic(3)) shall be set
          • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          • The other bits have to be 0.
      3. Mandatory attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type (INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = MDC_DIM_X_M or MDC_DIM_X_FOOT or MDC_DIM_X_STEP
      4. Mandatory attribute Source-Handle-Reference
        • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    3. c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-008_A | | | +| TP label | Distance, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose |

    Check that:

    Distance Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_040 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Distance object
    | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Distance object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Distance instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|----------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-009 | | | | +| TP label | Ascent Time and Distance Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | AscentTime1; O | +| | | AscentTime2; M | AscentTime3; M | AscentTime4; M | +| | | AscentTime5; M | AscentTime6; R | AscentTime7; M | +| Test purpose |

    Check that:

    The Ascent Time and Distance Numeric object contains the attributes specified for Extended Configuration.

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_041 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Ascent time and Distance object shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_PHD_HF MDC_HF_ASC_TIME_DIST
      2. b. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. • bit 0 (mss-avail-intermittent(0)) shall be set.
          2. • bit 1(mss-avail-stored-data(1)) shall be set.
          3. • bit 2 (mss-updt-aperiodic(2)) shall be set.
          4. • bit 3(mss-msmt-aperiodic(3)) shall be set
          5. • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          6. • The other bits have to be 0.
      3. c. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_X_M or MDC_DIM_X_FOOT or MDC_DIM_X_STEP
      4. d. Mandatory attribute Source-Handle-Reference
        1. attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        2. attribute-type = HANDLE (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
      5. e. Recommended attribute Measure-Active-Period
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE
    • attribute-type = FLOAT-Type (INT-U32)
    • attribute-value.length = 4 bytes
    • attribute-value = <Not relevant for this test>

    5. IF C_AG_OXP_293:

    • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    • c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used (for observed values of the ascent time and distance object).
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-009_A | | | +| TP label | Ascent time and distance, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose |

    Check that:

    Ascent Time and Distance Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_041 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    • 1. Take a measurement with the PHD under test.
    • 2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Ascent time and distance Object.
    | | | +| Pass/Fail criteria |
    • • The timestamp Attribute used for Ascent time and distance object shall be the same as that used for the associated Session or Sub-session object instance.
    • • Ascent time and distance instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-010 | | | +| TP label | Descent Time and Distance Numeric Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | DescentTime2; M | DescentTime3; M | +| | | DescentTime5; M | DescentTime6; R | +| Test purpose |

    Check that:

    The Descent Time and Distance Numeric object contains the attributes specified for Extended Configuration.

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_042 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The object shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_PHD_HF MDC_HF_DESC_TIME_DIST
      2. b. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          • • bit 0 (mss-avail-intermittent(0)) shall be set.
          • • bit 1(mss-avail-stored-data(1)) shall be set.
          • • bit 2 (mss-updt-aperiodic(2)) shall be set.
          • • bit 3(mss-msmt-aperiodic(3)) shall be set
          • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          • • The other bits have to be 0.
      3. c. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_X_M or MDC_DIM_X_FOOT or MDC_DIM_X_STEP
      4. d. Mandatory attribute Source-Handle-Reference
        1. attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        2. attribute-type = HANDLE (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
      5. e. Recommended attribute Measure-Active-Period
    | | | + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|
    • attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE
    • attribute-type = FLOAT-Type (INT-U32)
    • attribute-value.length = 4 bytes
    • attribute-value = <Not relevant for this test>

    5. IF C_AG_OXP_293:

    • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    • c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-010_A | | | +| TP label | Descent time and distance, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose |

    Check that:

    Descent Time and Distance Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_042 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    • 1. Take a measurement with the PHD under test.
    • 2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Descent Time and Distance object.
    | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for Descent Time and Distance object shall be the same as the one used for the associated Session or Sub-session object instance.
    • • The Descent Time and Distance instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-011 | | | +| TP label | Latitude Numeric Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | Latitude2; M | Latitude3; M | +| | | Latitude5; M | Latitude6; M | +| Test purpose | Check that:
    The Latitude Numeric object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_038 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Latitude object shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_PHD_HF MDC_HF_LATITUDE
      2. b. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. • bit 0 (mss-avail-intermittent (0)) shall be set.
          2. • bit 1(mss-avail-stored-data (1)) shall be set.
          3. • bit 2 (mss-updt-aperiodic (2)) shall be set.
          4. • bit 3(mss-msmt-aperiodic(3)) shall be set
          5. • bit 9 (mss-acc-agent-initiated (9)) shall be set.
          6. • The other bits have to be 0.
      3. c. Not Recommended attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_ANG_DEG
      4. d. Mandatory attribute Source-Handle-Reference
        1. attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        2. attribute-type = HANDLE (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    5. 5. IF C_AG_OXP_293:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    set to 0 to indicate all attributes.

    b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.

    c. IF the mds-time-mgr-set-time bit is set:

    • The PHG moves to Configuring/Sending Set Time substate and:
      • • IF C_AG_OXP_009 it issues the Set-Time action command.
      • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
    • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that the values are limited to -180 to 180.
    | +| Notes | | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-011_A | | | | +| TP label | Latitude, timestamp values | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj2; M | NumObj3; M | | +| Test purpose |

    Check that:

    Latitude Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance

    | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_038 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Latitude object.
    | | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Latitude object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Latitude instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | | +| Notes | | | | | + +| | | | | | +|---------------------|-------------------------------------|------------------------|---------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-012 | | | | +| TP label | Longitude Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Longitude1; O | +| | | Longitude2; M | Longitude3; M | Longitude4; R | +| | | Longitude5; M | Longitude6; M | | +| Test purpose | Check that: | | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The Longitude Numeric object contains the attributes specified for Extended Configuration. | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_037 | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | +| Initial condition | The PHD under test is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Longitude object shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_PHD_HF MDC_HF_LONGITUDE
      2. b. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. • bit 0 (mss-avail-intermittent (0)) shall be set.
          2. • 1(mss-avail-stored-data (1)) shall be set.
          3. • bit 2 (mss-updt-aperiodic (2)) shall be set.
          4. • bit 3(mss-msmt-aperiodic(3)) shall be set
          5. • bit 9 (mss-acc-agent-initiated (9)) shall be set.
          6. • The other bits have to be 0.
      3. c. Not Recommended attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_ANG_DEG
      4. d. Mandatory attribute Source-Handle-Reference
        1. attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        2. attribute-type = HANDLE (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    5. 5. IF C_AG_OXP_293:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        1. The PHG moves to Configuring/Sending Set Time substate and:
          1. • IF C_AG_OXP_009 it issues the Set-Time action command.
          2. • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
        2. Once its internal time setting operation is completed, the PHD responds to the
    | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PHG.
    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    7. Take a measurement in the PHD.
    8. Wait until the PHG receives an event report. | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that the values are limited to -180 to 180.
    | +| Notes | | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-012_A | | | | +| TP label | Longitude, timestamp values | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj2; M | NumObj3; M | | +| Test purpose | Check that:

    Longitude Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_037 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure | 1. Take a measurement with the PHD under test.

    2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Longitude object. | | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Longitude object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Longitude instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-013 | | | | +| TP label | Slopes Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Slopes1; O | +| | | Slopes2; M | Slopes3; M | Slopes4; R | +| | | Slopes5; M | Slopes6; M | | +| Test purpose | Check that:

    The Slopes Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_036 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.

    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".

    3. The PHD responds with a roiv-cmip-confirmed-event report message with a | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    MDC_NOTI_CONFIG event to send its configuration to the PHG.

    1. The Slopes object shall be:
      1. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_HF MDC_HF_SLOPES
      2. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • • bit 0 (mss-avail-intermittent(0)) shall be set.
          • • bit 1(mss-avail-stored-data(1)) shall be set.
          • • 2 (mss-updt-aperiodic(2)) shall be set.
          • • bit 3(mss-msmt-aperiodic(3)) shall be set
          • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          • • The other bits have to be 0.
      3. Not Recommended attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type (INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = MDC_DIM_DIMLESS
      4. Mandatory attribute Source-Handle-Reference
        • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        • attribute-type = HANDLE (INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    2. IF C_AG_OXP_293:
      1. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 it issues the Set-Time action command.
          • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    3. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    4. Take a measurement in the PHD.
    5. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-013_A | | | +| TP label | Slopes, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:
    Slopes Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_036 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Slopes object. | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Slopes object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Slopes instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|-----------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-014 | | | | +| TP label | Speed Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Speed1; O | +| | | Speed2; M | Speed3; M | Speed4; M | +| | | Speed5; M | Speed6; M | | +| Test purpose | Check that:
    The Speed Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_035 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Speed object shall be:
    1. a. Mandatory attribute Type
      • attribute-id = MDC_ATTR_ID_TYPE
      • attribute-type = TYPE
      • attribute-value = MDC_PART_PHD_HF MDC_HF_SPEED
    2. b. Mandatory attribute Metric-Spec_Small
      • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = MetricSpecSmall (BITS-16)
    • attribute-value ≠ 0x00 0x00
      • • bit 0 (mss-avail-intermittent(0)) shall be set.
      • • bit 1(mss-avail-stored-data(1)) shall be set.
      • • bit 2 (mss-updt-aperiodic(2)) shall be set.
      • • bit 3(mss-msmt-aperiodic(3)) shall be set
      • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
      • • The other bits have to be 0.

    c. Mandatory attribute Metric-Id

    • attribute-id = MDC_ATTR_ID_PHYSIO
    • attribute-type = OID-Type
    • attribute-value.length = INT-U16
    • attribute-value = MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MEAN_NULL_INCLUDE or MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MAX or MDC_HF_MIN

    d. Mandatory attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_X_M_PER_MIN or MDC_DIM_X_FOOT_PER_MIN or MDC_DIM_X_INCH_PER_MIN or MDC_DIM_X_STEP_PER_MIN

    e. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    3. c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    4. 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    5. 7. Take a measurement in the PHD.
    6. 8. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-014_A | | | +| TP label | Speed, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:
    Speed Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_035 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Speed object. | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for Speed object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Speed instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------|-------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-015 | | | | +| TP label | Cadence Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Cadence1; O | +| | | Cadence2; M | Cadence3; M | Cadence4; M | +| | | Cadence5; R | Cadence6; M | Cadence7; M | +| Test purpose | Check that:
    The Cadence Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_034 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Cadence object shall be:
    a. Mandatory attribute Type
    attribute-id = MDC_ATTR_ID_TYPE
    attribute-type = TYPE
    attribute-value = MDC_PART_PHD_HF MDC_HF_CAD
    b. Mandatory attribute Metric-Spec_Small
    attribute-id = MDC_ATTR_METRIC_SPEC_SMALL | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = MetricSpecSmall (BITS-16)
    • attribute-value ≠ 0x00 0x00
      • • bit 0 (mss-avail-intermittent(0)) shall be set.
      • • bit 1(mss-avail-stored-data(1)) shall be set.
      • • bit 2 (mss-updt-aperiodic(2)) shall be set.
      • • bit 3(mss-msmt-aperiodic(3)) shall be set
      • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
      • • The other bits have to be 0.

    c. Mandatory attribute Metric-Id

    • attribute-id = MDC_ATTR_ID_PHYSIO
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MEAN_NULL_INCLUDE or MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MAX or MDC_HF_MIN

    d. Not Recommended attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_RPM

    e. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    • c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-015_A | | | +| TP label | Cadence, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:
    Cadence Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_034 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Cadence object. | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for Cadence object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Cadence instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------|-------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-016 | | | | +| TP label | Incline Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Incline1; O | +| | | Incline2; M | Incline3; M | Incline4; M | +| | | Incline5; M | Incline6; M | | +| Test purpose | Check that:
    The Incline Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_033 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Incline object shall be:
    1. a. Mandatory attribute Type
      • attribute-id = MDC_ATTR_ID_TYPE
      • attribute-type = TYPE
      • attribute-value = MDC_PART_PHD_HF MDC_HF_INCLINE
    2. b. Mandatory attribute Metric-Spec_Small
      • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = MetricSpecSmall (BITS-16)
    • attribute-value ≠ 0x00 0x00
      • • bit 0 (mss-avail-intermittent(0)) shall be set.
      • • bit 1(mss-avail-stored-data(1)) shall be set.
      • • bit 2 (mss-updt-aperiodic(2)) shall be set.
      • • bit 3(mss-msmt-aperiodic(3)) shall be set
      • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
      • • The other bits have to be 0.

    c. Mandatory attribute Metric-Id

    • attribute-id = MDC_ATTR_ID_PHYSIO
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MEAN_NULL_INCLUDE or MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MAX or MDC_HF_MIN

    d. Mandatory attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_PERCENT or MDC_DIM_ANG_DEG

    e. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE
    • attribute-value.length = INT-U16
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    • c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check values.
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-016_A | | | +| TP label | Incline, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:
    Incline Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_033 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Incline object. | | | +| Pass/Fail criteria |
    • • The Timestamp attribute used for Incline object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Incline instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|----------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-017 | | | | +| TP label | Heart Rate Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Heart rate1; O | +| | | Heart rate2; M | Heart rate3; M | Heart rate4; M | +| | | Heart rate5; R | Heart rate6; M | Heart rate7 M | +| Test purpose | Check that:
    The Heart Rate Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_031 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Heart rate object shall be:
    a. Mandatory attribute Type
    attribute-id = MDC_ATTR_ID_TYPE
    attribute-type = TYPE
    attribute-value = MDC_PART_PHD_HF MDC_HF_HR
    b. Mandatory attribute Metric-Spec_Small
    attribute-id = MDC_ATTR_METRIC_SPEC_SMALL | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = MetricSpecSmall (BITS-16)
    • attribute-value ≠ 0x00 0x00
      • • bit 0 (mss-avail-intermittent(0)) shall be set.
      • • bit 1(mss-avail-stored-data(1)) shall be set.
      • • bit 2 (mss-updt-aperiodic(2)) shall be set.
      • • bit 3(mss-msmt-aperiodic(3)) shall be set
      • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
      • • The other bits have to be 0.

    c. Mandatory attribute Metric-Id

    • attribute-id = MDC_ATTR_ID_PHYSIO
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MEAN_NULL_INCLUDE or MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MAX or MDC_HF_MIN

    d. Not Recommended attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_BEAT_PER_MIN

    e. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    • a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    • c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-017_A | | | | +| TP label | Heart Rate, timestamp values | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj2; M | NumObj3; M | | +| Test purpose | Check that:
    Heart Rate Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_031 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Heart rate object. | | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for Heart Rate object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Heart rate instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------|-------------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-018 | | | | +| TP label | Max user Heart Rate Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Max user heart rate1; O | +| | | Max user heart rate2; M | Max user heart rate3; M | Max user heart rate4; X | +| | | Max user heart rate5; R | Max user heart rate6; M | Max user heart rate7; M | +| Test purpose | Check that:
    The Max User Heart Rate Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_030 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Max user Heart rate object shall be:
    1. a. Mandatory attribute Type
      • attribute-id = MDC_ATTR_ID_TYPE
      • attribute-type = TYPE
      • attribute-value = MDC_PART_PHD_HF MDC_HF_HR_MAX_USER
    2. b. Mandatory attribute Metric-Spec_Small
      • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = MetricSpecSmall (BITS-16)
    • attribute-value ≠ 0x00 0x00
      • • bit 0 (mss-avail-intermittent(0)) shall be set.
      • • bit 1(mss-avail-stored-data(1)) shall be set.
      • • bit 2 (mss-updt-aperiodic(2)) shall be set.
      • • bit 3(mss-msmt-aperiodic(3)) shall be set
      • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
      • • The other bits have to be 0.

    c. Mandatory attribute Metric-Id

    • attribute-id = MDC_ATTR_ID_PHYSIO
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes

    d. Not Recommended attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_BEAT_PER_MIN

    e. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    3. c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    4. 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    5. 7. Take a measurement in the PHD.
    6. 8. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes |

    Metric-Id has been considered as mandatory, but its qualifier has to be clarified by Continua.

    Opened bug :http://certification.continuaalliance.org/bugzilla/show_bug.cgi?id=465

    | + +| | | +|-----------------|---------------------------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-018_A | +| TP label | Max user heart rate, timestamp values | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--| +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj2; M | NumObj3; M | | +| Test purpose | Check that:

    Max User Heart Rate Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_030 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure | 1. Take a measurement with the PHD under test.

    2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Max user heart rate object. | | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Max user heart rate object shall be the same as that used for the associated Session or Sub-session object instance.

    • • The Max user heart rate instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|------------|-----------| +| TP Id | | TP/PLT/PHD/CLASS/CV/BV-019 | | | +| TP label | | Power Numeric Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Power1; O | +| | | Power2; M | Power3; M | Power4; M | +| | | Power5; R | Power6; M | Power7; M | +| Test purpose | Check that:

    The Power Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_029 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.

    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".

    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.

    4. The Power object shall be:
    1. a. Mandatory attribute Type
      • attribute-id = MDC_ATTR_ID_TYPE

      • attribute-type = TYPE

      • attribute-value = MDC_PART_PHD_HF MDC_HF_POWER

    2. b. Mandatory attribute Metric-Spec_Small
      • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL

      • attribute-type = MetricSpecSmall (BITS-16)

      • attribute-value ≠ 0x00 0x00
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • bit 0 (mss-avail-intermittent(0)) shall be set.
    • • bit 1(mss-avail-stored-data(1)) shall be set.
    • • bit 2 (mss-updt-aperiodic(2)) shall be set.
    • • bit 3(mss-msmt-aperiodic(3)) shall be set
    • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
    • • The other bits have to be 0.

    c. Mandatory attribute Metric-Id

    • attribute-id = MDC_ATTR_ID_PHYSIO
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MEAN_NULL_INCLUDE or MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MAX or MDC_HF_MIN

    d. Not Recommended attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_X_WATT

    e. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    3. c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    4. 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    5. 7. Take a measurement in the PHD.
    6. 8. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | +|-----------------|------------------------------|------------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-019_A | | +| TP label | Power, timestamp values | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|--| +| | Testable items | NumObj2; M | NumObj3; M | | +| Test purpose | Check that:
    Power Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_029 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Power object. | | | | +| Pass/Fail criteria |
    • The Timestamp attribute used for the power object shall be the same as that used for the associated Session or Sub-session object instance.
    • The Power instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|----------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-020 | | | | +| TP label | Resistance Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Resistance1; O | +| | | Resistance2; M | Resistance3; M | Resistance4; M | +| | | Resistance5; R | Resistance6; M | | +| Test purpose | Check that:
    The Resistance Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_028 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Resistance object shall be:
    • Mandatory attribute Type
      • attribute-id = MDC_ATTR_ID_TYPE
      • attribute-type = TYPE
      • attribute-value = MDC_PART_PHD_HF MDC_HF_RESIST
    • Mandatory attribute Metric-Spec-Small
      • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
      • attribute-type = MetricSpecSmall (BITS-16)
      • attribute-value ≠ 0x00 0x00
        • bit 0 (mss-avail-intermittent(0)) shall be set.
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • bit 1(mss-avail-stored-data(1)) shall be set.
    • • bit 2 (mss-updt-aperiodic(2)) shall be set.
    • • bit 3(mss-msmt-aperiodic(3)) shall be set
    • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
    • • The other bits have to be 0.

    c. Mandatory attribute Metric-Id

    • attribute-id = MDC_ATTR_ID_PHYSIO
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MEAN_NULL_INCLUDE or MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MAX or MDC_HF_MIN

    d. Not recommended attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes

    e. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-020_A | | | +| TP label | Resistance, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose |

    Check that:

    Resistance Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_028 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Resistance object.
    | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for resistance object shall be the same as the used for the associated Session or Sub-session object instance.
    • • The Resistance instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-021 | | | +| TP label | Stride Numeric Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | Stride length2; M | Stride length3; M | +| | | Stride length5; M | Stride length6; M | +| Test purpose |

    Check that:

    The Stride length Numeric object contains the attributes specified for Extended Configuration.

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_027 | | | +| Other PICS | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Stride object shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_PHD_HF MDC_HF_STRIDE
      2. b. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. • bit 0 (mss-avail-intermittent(0)) shall be set.
          2. • bit 1(mss-avail-stored-data(1)) shall be set.
          3. • bit 2 (mss-updt-aperiodic(2)) shall be set.
          4. • bit 3(mss-msmt-aperiodic(3)) shall be set
          5. • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          6. • The other bits have to be 0.
      3. c. Mandatory attribute Metric-Id
        1. attribute-id = MDC_ATTR_ID_PHYSIO
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MEAN_NULL_INCLUDE or MDC_HF_MEAN_NULL_EXCLUDE or MDC_HF_MAX or MDC_HF_MIN
      4. d. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_X_M or MDC_DIM_X_INCH
      5. e. Mandatory attribute Source-Handle-Reference
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-021_A | | | +| TP label | Stride, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:
    Stride length Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Stride object. | | | +| Pass/Fail criteria |
    • The Timestamp attribute used for stride object shall be the same as the used for the associated Session or Sub-session object instance.
    • The Stride instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-022 | | | | +| TP label | Breathing Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Breathing rate1; O | +| | | Breathing rate2; M | Breathing rate3; M | Breathing rate4; M | +| | | Breathing rate5; R | Breathing rate6; M | Breathing rate7; M | +| Test purpose | Check that:
    The Breathing rate Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_026 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config". | | | | + +3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC\_NOTI\_CONFIG event to send its configuration to the PHG. +4. The Breathing object shall be: + - a. Mandatory attribute Type + - attribute-id = MDC\_ATTR\_ID\_TYPE + - attribute-type = TYPE + - attribute-value = MDC\_PART\_PHD\_HF | MDC\_RESP\_RATE + - b. Mandatory attribute Metric-Spec\_Small + - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL + - attribute-type = MetricSpecSmall (BITS-16) + - attribute-value ≠ 0x00 0x00 + - bit 0 (mss-avail-intermittent(0)) shall be set. + - bit 1(mss-avail-stored-data(1)) shall be set. + - bit 2 (mss-updt-aperiodic(2)) shall be set. + - bit 3(mss-msmt-aperiodic(3)) shall be set + - bit 9 (mss-acc-agent-initiated(9)) shall be set. + - The other bits have to be 0. + - c. Mandatory attribute Metric-Id + - attribute-id = MDC\_ATTR\_ID\_PHYSIO + - attribute-type = OID-Type + - attribute-value.length = INT-U16 + - attribute-value = MDC\_HF\_MEAN\_NULL\_EXCLUDE or MDC\_HF\_MEAN\_NULL\_INCLUDE or MDC\_HF\_MEAN\_NULL\_EXCLUDE or MDC\_HF\_MAX or MDC\_HF\_MIN + - d. Not Recommended attribute Unit-Code + - attribute-id = MDC\_ATTR\_UNIT\_CODE + - attribute-type = OID-Type + - attribute-value.length = 2 bytes + - attribute-value = MDC\_DIM\_RESP\_PER\_MIN + - e. Mandatory attribute Source-Handle-Reference + - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF + - attribute-type = HANDLE + - attribute-value.length = 2 bytes + - attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration +5. IF C\_AG\_OXP\_293: + - a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes. + - b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object. + - c. IF the mds-time-mgr-set-time bit is set: + - The PHG moves to Configuring/Sending Set Time substate and: + - IF C\_AG\_OXP\_009 it issues the Set-Time action command. + - IF C\_AG\_OXP\_014 it issues the Set-Base-Offset-Time action command. + - Once its internal time setting operation is completed, the PHD responds to the PHG. + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    2. 7. Take a measurement in the PHD.
    3. 8. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-022_A | | | +| TP label | Breathing rate, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:
    Breathing rate Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_026 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Breathing rate object.
    | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Breathing rate object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Breathing rate instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------|---------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-023 | | | | +| TP label | Energy Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Energy expended1; O | +| | | Energy expended2; M | Energy expended3; M | Energy expended4; M | +| | | Energy expended5; M | Energy expended6; M | | +| Test purpose | Check that:
    The Energy Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_025 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. The Energy object shall be:

    1. Mandatory attribute Type
      • attribute-id = MDC_ATTR_ID_TYPE
      • attribute-type = TYPE
      • attribute-value = MDC_PART_PHD_HF MDC_HF_ENERGY
    2. Mandatory attribute Metric-Spec_Small
      • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
      • attribute-type = MetricSpecSmall (BITS-16)
      • attribute-value ≠ 0x00 0x00
        • • bit 0 (mss-avail-intermittent(0)) shall be set.
        • • bit 1(mss-avail-stored-data(1)) shall be set.
        • • bit 2 (mss-updt-aperiodic(2)) shall be set.
        • • bit 3(mss-msmt-aperiodic(3)) shall be set
        • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
        • • The other bits have to be 0.
    3. Mandatory attribute Unit-Code
      • attribute-id = MDC_ATTR_UNIT_CODE
      • attribute-type = OID-Type (INT-U16)
      • attribute-value.length = 2 bytes
      • attribute-value = MDC_DIM_X_CAL or MDC_DIM_X_JOULES
    4. Mandatory attribute Source-Handle-Reference
      • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
      • attribute-type = HANDLE (NT-U16)
      • attribute-value.length = 2 bytes
      • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    1. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    3. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-023_A | | | +| TP label | Energy expended, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:

    Energy expended Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.

    2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Energy expended object. | | | +| Pass/Fail criteria |
    • • The Timestamp attribute used for the Energy expended object shall be the same as that used for the associated Session or Sub-session object instance.

    • • The Energy expended instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-024 | | | +| TP label | Calories Ingested Numeric Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | Calories ingested2; M | Calories ingested3; M | +| | | Calories ingested5; M | Calories ingested6; M | +| Test purpose | Check that:

    The Calories Ingested Numeric object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_024 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.

    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".

    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.

    4. The Calories Ingested object shall be:
    1. a. Mandatory attribute Type
      • attribute-id = MDC_ATTR_ID_TYPE

      • attribute-type = TYPE

      • attribute-value = MDC_PART_PHD_HF MDC_HF_CAL_INGEST

    2. b. Mandatory attribute Metric-Spec_Small
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
    • attribute-type = MetricSpecSmall (BITS-16)
    • attribute-value ≠ 0x00 0x00
      • • bit 0 (mss-avail-intermittent(0)) shall be set.
      • • bit 1(mss-avail-stored-data(1)) shall be set.
      • • bit 2 (mss-updt-aperiodic(2)) shall be set.
      • • bit 3(mss-msmt-aperiodic(3)) shall be set
      • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
      • • The other bits have to be 0.

    c. Not Recommended attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_X_CAL

    d. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    3. c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    4. 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    5. 7. Take a measurement in the PHD.
    6. 8. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------|-------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-024_A | | | +| TP label | Calories ingested, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that: | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Calories Ingested Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).
    [AND]
    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_024 | +| Other PICS | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Calories ingested object.
    | +| Pass/Fail criteria |
    • • The Timestamp attribute used for the Calories ingested object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Calories ingested instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-025 | | | +| TP label | Carbohydrate Calories Ingested Numeric Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | CarbohydrateCal2; M | CarbohydrateCal3; M | +| | | CarbohydrateCal5; M | CarbohydrateCal6; M | +| Test purpose | Check that:

    The Carbohydrate Calories Ingested Numeric object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_023 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Carbohydrate Calories Ingested object shall be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_HF MDC_HF_CAL_INGEST_CARB
      2. b. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • • bit 0 (mss-avail-intermittent(0)) shall be set.
          • • bit 1(mss-avail-stored-data(1)) shall be set.
          • • bit 2 (mss-updt-aperiodic(2)) shall be set.
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • bit 3(mss-msmt-aperiodic(3)) shall be set
    • bit 9 (mss-acc-agent-initiated(9)) shall be set.
    • The other bits have to be 0.

    c. Not Recommended attribute Unit-Code

    • attribute-id = MDC_ATTR_UNIT_CODE
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_X_CAL

    d. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    1. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    3. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • IF C_AG_OXP_009 it issues the Set-Time action command.
        • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • In step 4, all checked values are as specified.
    • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-025_A | | | +| TP label | Carbohydrate calories ingested, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:

    Carbohydrate Calories Ingested Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_023 | | | +| Other PICS | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | +| Test procedure |
    1. Take a measurement with the PHD under test
    2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Carbohydrate calories ingested object.
    | +| Pass/Fail criteria |
    • The timestamp attribute used for the Carbohydrate Calories Ingested object shall be the same as that used for the associated Session or Sub-session object instance.
    • The Carbohydrate calories ingested instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | +| Notes | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|----------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-026 | | | | +| TP label | Sustained Phys Activity Threshold Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | SustainedPhysAct1; O | +| | | SustainedPhysAct2; M | SustainedPhysAct3; M | SustainedPhysAct4; R | +| | | SustainedPhysAct5; M | SustainedPhysAct6; M | | +| Test purpose | Check that:

    The Sustained Phys Activity Threshold Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_022 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure |
    1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Sustained Phys Activity Threshold object shall be:
      1. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_HF MDC_HF_SUS_PA_THRESHOLD
      2. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • bit 0 (mss-avail-intermittent(0)) shall be set.
          • bit 1(mss-avail-stored-data(1)) shall be set.
          • bit 2 (mss-updt-aperiodic(2)) shall be set.
          • bit 3(mss-msmt-aperiodic(3)) shall be set
          • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          • The other bits have to be 0.
      3. Not Recommended attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type (INT-U16)
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_DIM_MIN

    d. Mandatory attribute Source-Handle-Reference

    • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
    • attribute-type = HANDLE (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    3. c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.
    4. 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    5. 7. Take a measurement in the PHD.
    6. 8. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-026_A | | | | +| TP label | Sustained phys activity threshold, timestamp values | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj2; M | NumObj3; M | | +| Test purpose | Check that:

    Sustained phys activity threshold Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_022 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Sustained phys activity threshold object.
    | | | | +| Pass/Fail criteria |
    • • The Timestamp attribute used for the Sustained phys activity threshold object shall be the same as that used for the associated Session or Sub-session object instance.
    | | | | + +| | | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • The Sustained phys activity threshold instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | +| Notes | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-027 | | | | +| TP label | Activity Intensity Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | ActIntensity1; O | +| | | ActIntensity2; M | ActIntensity3; M | ActIntensity4; R | +| | | ActIntensity5; M | ActIntensity6; M | | +| Test purpose | Check that:

    The Activity Intensity Numeric object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_021 | | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Activity Intensity object shall be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_HF MDC_HF_ACTIVITY_INTENSITY
      2. b. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • • bit 0 (mss-avail-intermittent(0)) shall be set.
          • • bit 1(mss-avail-stored-data(1)) shall be set.
          • • bit 2 (mss-updt-aperiodic(2)) shall be set.
          • • bit 3(mss-msmt-aperiodic(3)) shall be set.
          • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          • • The other bits have to be 0.
      3. c. Not Recommended attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type (INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = MDC_DIM_PERCENT
      4. d. Mandatory attribute Source-Handle-Reference
        • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        • attribute-type = HANDLE (INT-U16)
        • attribute-value.length = 2 bytes
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration

    5. IF C_AG_OXP_293:

    1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
    3. c. IF the mds-time-mgr-set-time bit is set:
      • The PHG moves to Configuring/Sending Set Time substate and:
        • • IF C_AG_OXP_009 it issues the Set-Time action command.
        • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
      • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only values between zero (0) and 100 are used. The observed value reported in this object is the percentage of maximal intensity effort expended during the measurement period, as defined by the associated Session or Sub-session object.
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-027_A | | | +| TP label | Activity intensity, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose |

    Check that:

    Activity Intensity Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_021 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Activity Intensity object.
    | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Activity Intensity object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Activity intensity instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-028 | | | +| TP label | Body Weight Numeric Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | BodyWeight2; M | BodyWeight3; M | +| | | BodyWeight5; M | BodyWeight6; M | +| Test purpose |

    Check that:

    The Body Weight Numeric object contains the attributes specified for Extended Configuration.

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_020 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Body Weight object shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_SCADA MDC_MASS_BODY_ACTUAL
      2. b. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. • bit 0 (mss-avail-intermittent(0)) shall be set.
          2. • bit 1(mss-avail-stored-data(1)) shall be set.
          3. • bit 2 (mss-updt-aperiodic(2)) shall be set.
          4. • bit 3(mss-msmt-aperiodic(3)) shall be set
          5. • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          6. • The other bits have to be 0.
      3. c. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_X_G or MDC_DIM_X_LB
      4. d. Mandatory attribute Source-Handle-Reference
        1. attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        2. attribute-type = HANDLE (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    5. 5. IF C_AG_OXP_293:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.

    b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.

    c. IF the mds-time-mgr-set-time bit is set:

    • The PHG moves to Configuring/Sending Set Time substate and:
      • • IF C_AG_OXP_009 it issues the Set-Time action command.
      • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
    • Once its internal time setting operation is completed, the PHD responds to the PHG.

    6. Wait for the PHD under test and the simulated PHG to reach the Operating state.

    7. Take a measurement in the PHD.

    8. Wait until the PHG receives an event report.

    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-028_A | | | +| TP label | Body weight, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose |

    Check that:

    Body Weight Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Body Weight object.
    | | | +| Pass/Fail criteria |
    • • The Timestamp attribute used for the Body Weight object shall be the same as that used for the associated Session or Sub-session object instance.
    • • Body weight instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|---------------------|----------------------------------|------------------------|------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-029 | | | | +| TP label | Height Numeric Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj5; M | NumObj6; M | Height1; O | +| | | Height2; M | Height3; M | Height4; M | +| | | Height5; M | Height6; M | | +| Test purpose | Check that: | | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The Body Height Numeric object contains the attributes specified for Extended Configuration. | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_019 | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | +| Initial condition | The PHD under test is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Height object shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value = MDC_PART_SCADA MDC_LEN_BODY_ACTUAL
      2. b. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. • bit 0 (mss-avail-intermittent(0)) shall be set.
          2. • bit 1(mss-avail-stored-data(1)) shall be set.
          3. • bit 2 (mss-updt-aperiodic(2)) shall be set.
          4. • bit 3(mss-msmt-aperiodic(3)) shall be set
          5. • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          6. • The other bits have to be 0.
      3. c. Mandatory attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = MDC_DIM_X_M or MDC_DIM_X_FOOT
      4. d. Mandatory attribute Source-Handle-Reference
        1. attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        2. attribute-type = HANDLE (INT-U16)
        3. attribute-value.length = 2 bytes
        4. attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    5. 5. IF C_AG_OXP_293:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        1. The PHG moves to Configuring/Sending Set Time substate and:
          1. • IF C_AG_OXP_009 it issues the Set-Time action command.
          2. • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Once its internal time setting operation is completed, the PHD responds to the PHG.
    1. 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    2. 7. Take a measurement in the PHD.
    3. 8. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-029_A | | | +| TP label | Height, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:

    Body Height Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. Take a measurement with the PHD under test.
    2. 2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Height object.
    | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Height object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Height instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-030 | | | +| TP label | Age Numeric Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj5; M | NumObj6; M | +| | | Age1; O | Age2; M | +| Test purpose | Check that:

    The Age Numeric object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_018 | | | +| Other PICS | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293 | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    2. 4. The Age object shall be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value = MDC_PART_PHD_HF MDC_HF_AGE
      2. b. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • • bit 0 (mss-avail-intermittent(0)) shall be set.
          • • bit 1(mss-avail-stored-data(1)) shall be set.
          • • bit 2 (mss-updt-aperiodic(2)) shall be set.
          • • bit 3(mss-msmt-aperiodic(3)) shall be set
          • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          • • The other bits have to be 0.
      3. c. Not Recommended attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type (INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = MDC_DIM_YR
      4. d. Mandatory attribute Source-Handle-Reference
        • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        • attribute-type = HANDLE (INT-U16)
        • attribute-value.length = 2 bytes
        • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
    3. 5. IF C_AG_OXP_293:
      1. a. Once in Configuring/Sending GetMDS substate simulated PHG issues roiv-cmip-get command with handle set to 0 (to request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object.
      3. c. IF the mds-time-mgr-set-time bit is set:
        • The PHG moves to Configuring/Sending Set Time substate and:
          • • IF C_AG_OXP_009 it issues the Set-Time action command.
          • • IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.
        • Once its internal time setting operation is completed, the PHD responds to the PHG.
    4. 6. Wait for the PHD under test and the simulated PHG to reach the Operating state.
    5. 7. Take a measurement in the PHD.
    6. 8. Wait until the PHG receives an event report.
    | +| Pass/Fail criteria |
    • • In step 4, all checked values are as specified.
    • • In step 8, check that only non-negative values are used.
    | +| Notes | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-030_A | | | +| TP label | Age, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj2; M | NumObj3; M | +| Test purpose | Check that:

    Age Numeric object instance shall have a timestamp identical to its containing object instance (i.e. Session or Sub-session).

    [AND]

    The timestamp attribute used for each object shall be the same as the one used for the associated Session or Sub-session object instance | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_018 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.

    2. Wait for the simulated PHG to receive it. Record the Time Stamp and the Measure-Active-Period of the Session and Sub-session object and of the Age object. | | | +| Pass/Fail criteria |
    • • The Timestamp attribute used for Age object shall be the same as that used for the associated Session or Sub-session object instance.

    • • The Age instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-031 | | | +| TP label | Session Enumeration Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | Session1; M | Session2; M | +| | | Session4; R | Session5; R | +| | | Session7; M | Session8; R | +| | | Session11; M | Session12; M | +| Test purpose | Check that:

    The Session Enumeration object contains the attributes specified for Extended Configuration. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 | | | +| Other PICS | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure | 1. The simulated PHG receives an association request from the PHD under test.

    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".

    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.

    4. The Session object shall be:
    • a. Mandatory attribute Type
      • attribute-id = MDC_ATTR_ID_TYPE

      • attribute-type = TYPE

      • attribute-value.length = Sequence of partition (NomPartition (INT-U16)) and
    | | | + +code (OID-Type)) + +attribute-value = MDC\_PART\_PHD\_HF | MDC\_HF\_SESSION + +#### b. Mandatory attribute Metric-Spec\_Small + +attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL + +attribute-type = MetricSpecSmall (BITS-16) + +attribute-value ≠ 0x00 0x00 + +- bit 0 (mss-avail-intermittent(0)) shall be set. +- bit 1(mss-avail-stored-data(1)) shall be set. +- bit 2 (mss-updt-aperiodic(2)) shall be set. +- bit 3(mss-msmt-aperiodic(3)) shall be set +- bit 9 (mss-acc-agent-initiated(9)) shall be set. +- The other bits have to be 0. + +#### c. Not Recommended attribute Unit-Code + +attribute-id = MDC\_ATTR\_UNIT\_CODE + +attribute-type = OID-Type (INT-U16) + +attribute-value.length = 2 bytes + +#### d. Not Recommended attribute Unit-LabelString + +attribute-id = MDC\_ATTR\_UNIT\_LABEL\_STRING + +attribute-type = OCTET STRING + +attribute-value.length = + +#### e. Optional Label-String: + +attribute-id = MDC\_ATTR\_UNIT\_LABEL\_STRING + +attribute-type = OCTET STRING + +attribute-value = If an existing acceptable nomenclature term (for activity defined in Enum-Observed-Value-Simple-Oid) is not available → attribute-value = MDC\_HF\_ACT\_UNKONWN and an appropriate clarifying text in the Label-String attribute + +#### f. Mandatory attribute Measure-Active-Period + +attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE + +attribute-type = FLOAT-Type (INT-U32) + +attribute-value.length = 4 bytes + +#### g. Mandatory attribute Enum-Observed-Value-Simple-OID + +attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_OID + +attribute-type = OID-Type (INT-U16) + +attribute-value.length = 2 bytes + +attribute-value = + +- Valid values→ MDC\_HF\_ACT\_UNKNOWN or MDC\_HF\_ACT\_MONITOR or MDC\_HF\_ACT\_SKI or MDC\_HF\_ACT\_RUN or MDC\_HF\_ACT\_BIKE or MDC\_HF\_ACT\_STAIR or MDC\_HF\_ACT\_ROW or MDC\_HF\_ACT\_HOME or MDC\_HF\_ACT\_WORK or MDC\_HF\_ACT\_WALK +- If there are multiple Sub-sessions associated: attribute-value = MDC\_HF\_ACT\_MULTIPLE + +#### h. Not Recommended attribute Enum-Observed-Value-Simple-Str + +attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_STR + +attribute-type = EnumPrintableString + +attribute-value.length = + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | i. Not Recommended attribute Enum-Observed-Value
    • attribute-id = MDC_ATTR_VAL_ENUM_OBS
    • attribute-type = EnumObsValue
    • attribute-value.length = <variable>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-032 | | | +| TP label | Session and associated Sub-session 1 | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | Sub-session 10; M | Sub-session 13; M | +| Test purpose | Check that:
    The timestamp attribute of the Sub-session shall fall within the time span specified by the Session to which it is associated.

    [AND]

    Metrics that represent observations for the Sub-session shall have a timestamp equal to the associated Sub-session object's timestamp. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_043 | | | +| Other PICS | | | | +| Initial condition | The PHD under test is in the Operating state. | | | +| Test procedure | 1. Take Measurements for the Session and Sub-session Objects in the PHD under test.
    2. Wait to receive event reports and record the Session and the Sub-session objects for later comparison. | | | +| Pass/Fail criteria |
    • If the Session object has a timestamp, the associated Sub-session objects shall have the same type of timestamp.
    | | | +| Notes | | | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-032_A | | | +| TP label | Session and associated Sub-session 2 | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | Session13; M | Session14; M | +| Test purpose | Check that:
    All Sub-sessions that are contained by the Session shall have a timestamp that falls within the time span that begins with the Session's timestamp and lasts for the Measure-Active-Period attribute.

    [AND]

    The sum of all contained Sub-session Measure-Active-Period attributes shall be equal to the Measure-Active-Period attribute of the containing Session | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_043 | | | +| Other PICS | | | | +| Initial condition | The PHD under test is in the Operating state. | | | +| Test procedure | 1. Take Measurements for the Session and Sub-session Objects in the PHD under test.
    2. Wait to receive event reports and record the Session and the Sub-session objects for later comparison. | | | +| Pass/Fail criteria |
    • The sum of the Measure-Active-Period of the Sub-sessions has to be equal to the
    | | | + +| | | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Measure-Active-Period of the Session.

    • If the Sub-session objects have a timestamp, then it shall fall in the period defined between the timestamp and the Measure-Active-Period of the session object.
    | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-033 | | | +| TP label | Sub-session Enumeration Object Attributes | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | Session16; M | Sub-session 1; O | +| | | Sub-session 3; M | Sub-session 4; R | +| | | Sub-session 6; M | Sub-session 7; M | +| | | Sub-session 9; R | Sub-session 11; R | +| Test purpose |

    Check that:

    The Sub-session Enumeration object contains the attributes specified for Extended Configuration.

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_043 | | | +| Other PICS | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | +| Test procedure |
    1. The simulated PHG receives an association request from the PHD under test.
    2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. The Sub-session object shall be:
      1. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value.length = Sequence of partition (NomPartition (INT-U16)) and code (OID-Type))
        • attribute-value = MDC_PART_PHD_HF MDC_HF_SUBSESSION
      2. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • bit 0 (mss-avail-intermittent(0)) shall be set.
          • bit 1(mss-avail-stored-data(1)) shall be set.
          • bit 2 (mss-updt-aperiodic(2)) shall be set.
          • bit 3(mss-msmt-aperiodic(3)) shall be set
          • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          • The other bits have to be 0.
      3. Not Recommended attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type (INT-U16)
        • attribute-value.length = 2 bytes
      4. Not Recommended attribute Unit-LabelString
        • attribute-id = MDC_ATTR_UNIT_LABEL_STRING
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-type = OCTET STRING
    • attribute-value.length = <variable>

    j. Optional Label-String:

    • attribute-id = MDC_ATTR_UNIT_LABEL_STRING
    • attribute-type = OCTET STRING
    • attribute-value = If an existing acceptable nomenclature term (for activity defined in Enum-Observed-Value-Simple-Oid) is not available → attribute-value = MDC_HF_ACT_UNKONWN and an appropriate clarifying text in the Label-String attribute

    e. Mandatory attribute Measure-Active-Period

    • attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE
    • attribute-type = FLOAT-Type (INT-U32)
    • attribute-value.length = 4 bytes

    f. Mandatory attribute Enum-Observed-Value-Simple-OID

    • attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIM_OID
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_HF_ACT_UNKNOWN or MDC_HF_ACT_MONITOR or MDC_HF_ACT_SKI or MDC_HF_ACT_RUN or MDC_HF_ACT_BIKE or MDC_HF_ACT_STAIR or MDC_HF_ACT_ROW or MDC_HF_ACT_HOME or MDC_HF_ACT_WORK or MDC_HF_ACT_WALK

    g. Not Recommended attribute Enum-Observed-Value-Simple-Str

    • attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIM_STR
    • attribute-type = EnumPrintableString
    • attribute-value.length = <variable>

    h. Not Recommended attribute Enum-Observed-Value

    • attribute-id = MDC_ATTR_VAL_ENUM_OBS
    • attribute-type = EnumObsValue
    • attribute-value.length = <variable>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | http://continua.plugfest.com/show_bug.cgi?id=448 | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-034 | | | | +| TP label | Activity Time Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | Session16; M | ActivityTime1; O | ActivityTime2; M | +| | | ActivityTime3; M | ActivityTime4; R | ActivityTime5; R | +| | | ActivityTime6; R | ActivityTime7; M | ActivityTime8; M | +| | | ActivityTime9; R | ActivityTime10; R | ActivityTime11; M | +| | | ActivityTime12; M | | | +| Test purpose | Check that:
    The Activity Time Enumeration Object contains the attributes specified for Extended Configuration. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_017 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test is in the Unassociated state. | | | | + +| | | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

    Test procedure

    |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Activity Time object shall be:
      1. a. Mandatory attribute Type
        • attribute-id = MDC_ATTR_ID_TYPE
        • attribute-type = TYPE
        • attribute-value.length = Sequence of partition (NomPartition (INT-U16)) and code (OID-Type)
        • attribute-value = MDC_PART_PHD_HF MDC_HF_ACTIVITY_TIME
      2. b. Mandatory attribute Metric-Spec_Small
        • attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        • attribute-type = MetricSpecSmall (BITS-16)
        • attribute-value ≠ 0x00 0x00
          • • bit 0 (mss-avail-intermittent(0)) shall be set.
          • • bit 1(mss-avail-stored-data(1)) shall be set.
          • • bit 2 (mss-updt-aperiodic(2)) shall be set.
          • • bit 3(mss-msmt-aperiodic(3)) shall be set
          • • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          • • The other bits have to be 0.
      3. c. Not Recommended attribute Unit-Code
        • attribute-id = MDC_ATTR_UNIT_CODE
        • attribute-type = OID-Type (INT-U16)
        • attribute-value.length = 2 bytes
      4. d. Mandatory attribute Source-Handle-Reference
        • attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        • attribute-type = HANDLE (INT-U16)
        • attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
      5. e. Not Recommended attribute Absolute-Time-Stamp
        • attribute-id = MDC_ATTR_TIME_STAMP_ABS
        • attribute-type = AbsoluteTime
        • attribute-value.length = 8 bytes
      6. f. Not Recommended attribute Unit-LabelString
        • attribute-id = MDC_ATTR_UNIT_LABEL_STRING
        • attribute-type = OCTET STRING
        • attribute-value.length = <variable>
        • If an existing acceptable nomenclature term (for activity defined in Enum-Observed-Value-Simple-Oid) is not available → attribute-value = MDC_HF_ACT_UNKONWN
      7. g. Mandatory attribute Measure-Active-Period
        • attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE
        • attribute-type = FLOAT-Type (INT-U32)
        • attribute-value.length = 4 bytes
    | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    h. Mandatory attribute Enum-Observed-Value-Simple-OID

    • attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIM_OID
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value = MDC_HF_ACT_AMB or MDC_HF_ACT_REST, MDC_HF_ACT_MOTOR or MDC_HF_ACT_LYING or MDC_HF_ACT_SPEEP or MDC_HF_ACT_PHYS or MDC_HF_ACT_SUS_PHYS or MDC_HF_ACT_UNKNOWN

    i. Not Recommended attribute Enum-Observed-Value-Simple-Str

    • attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIM_STR
    • attribute-type = EnumPrintableString
    • attribute-value.length = <variable>

    j. Not Recommended attribute Enum-Observed-Value

    • attribute-id = MDC_ATTR_VAL_ENUM_OBS
    • attribute-type = EnumObsValue
    • attribute-value.length = <variable>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-034_A | | | +| TP label | Activity time, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | Session15; M | ActivityTime11; M | +| Test purpose | Check that:
    Metrics that represent observations for the Session as a whole shall have a timestamp equal to the associated Session object's timestamp. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_017 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Activity time object. | | | +| Pass/Fail criteria |
    • The timestamp attribute used for the Activity time object shall be the same as that used for the associated Session or Sub-session object instance.
    • The Activity time instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | | +|-----------------|--------------------------------------|------------------------|----------------|---------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-035 | | | | +| TP label | Program Identifier Object Attributes | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | Session16; M | ProgramId1; O | ProgramId2; M | +| | | ProgramId3; M | ProgramId4; R | ProgramId5; R | +| | | ProgramId6; R | ProgramId7; R | ProgramId8; M | +| | | ProgramId9; R | ProgramId10; M | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    The Program Identifier Enumeration object contains the attributes specified for Extended Configuration. | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_016 | +| Other PICS | | +| Initial condition | The PHD under test is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHG receives an association request from the PHD under test.
    2. 2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".
    3. 3. The PHD responds with a roiv-cmip-confirmed-event report message with a MDC_NOTI_CONFIG event to send its configuration to the PHG.
    4. 4. The Program Identifier object shall be:
      1. a. Mandatory attribute Type
        1. attribute-id = MDC_ATTR_ID_TYPE
        2. attribute-type = TYPE
        3. attribute-value.length = Sequence of partition (NomPartition (INT-U16)) and code (OID-Type)
        4. attribute-value = MDC_PART_PHD_HF MDC_HF_PROGRAM_ID
      2. b. Mandatory attribute Metric-Spec_Small
        1. attribute-id = MDC_ATTR_METRIC_SPEC_SMALL
        2. attribute-type = MetricSpecSmall (BITS-16)
        3. attribute-value ≠ 0x00 0x00
          1. • bit 0 (mss-avail-intermittent(0)) shall be set.
          2. • bit 1(mss-avail-stored-data(1)) shall be set.
          3. • bit 2 (mss-updt-aperiodic(2)) shall be set.
          4. • bit 3(mss-msmt-aperiodic(3)) shall be set
          5. • bit 9 (mss-acc-agent-initiated(9)) shall be set.
          6. • The other bits have to be 0.
      3. c. Not Recommended attribute Unit-Code
        1. attribute-id = MDC_ATTR_UNIT_CODE
        2. attribute-type = OID-Type (INT-U16)
        3. attribute-value.length = 2 bytes
      4. d. Mandatory attribute Source-Handle-Reference
        1. attribute-id = MDC_ATTR_SOURCE_HANDLE_REF
        2. attribute-type = HANDLE (INT-U16)
        3. attribute-value = It must be equal to the handle of any Session or Sub-session object in the configuration
      5. e. Not Recommended attribute Absolute-Time-Stamp
        1. attribute-id = MDC_ATTR_TIME_STAMP_ABS
        2. attribute-type = AbsoluteTime
        3. attribute-value.length = 8 bytes
      6. f. Not Recommended attribute Unit-LabelString
        1. attribute-id = MDC_ATTR_UNIT_LABEL_STRING
        2. attribute-type = OCTET STRING
        3. attribute-value.length = <variable>
      7. g. Mandatory attribute Measure-Active-Period
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE
    • attribute-type = FLOAT-Type (INT-U32)
    • attribute-value.length = 4 bytes

    h. Not Recommended attribute Enum-Observed-Value-Simple-OID

    • attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIM_OID
    • attribute-type = OID-Type (INT-U16)
    • attribute-value.length = 2 bytes
    • attribute-value =

    i. Mandatory attribute Enum-Observed-Value-Simple-Str

    • attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIM_STR
    • attribute-type = EnumPrintableString
    • attribute-value.length = <variable>

    j. Not Recommended attribute Enum-Observed-Value

    • attribute-id = MDC_ATTR_VAL_ENUM_OBS
    • attribute-type = EnumObsValue
    • attribute-value.length = <variable>
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-035_A | | | +| TP label | Program identifier, timestamp values | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | Session15; M | ProgramId10; M | +| Test purpose | Check that:
    Metrics that represent observations for the Session as a whole shall have a timestamp equal to the associated Session object's timestamp. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure | 1. Take a measurement with the PHD under test.
    2. Wait for the simulated PHG to receive it. Record the timestamp and the Measure-Active-Period of the Session and Sub-session object and of the Program Identifier object. | | | +| Pass/Fail criteria |
    • • The timestamp attribute used for the Program identifier object shall be the same as that used for the associated Session or Sub-session object instance.
    • • The Program identifier instance shall have a timestamp identical to its associated Session or Sub-session object instance.
    | | | +| Notes | | | | + +| | | | | +|-----------------|----------------------------|------------------------|--------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-036 | | | +| TP label | Association Request | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | MDSMethod4; M | AssocReq1; M | +| | | AssocReq3; M | AssocReq4; M | +| | | | AssocReq5; M | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|---------------| +| | | AssocReq6; M | AssocReq7; M | AssocReq8; M | +| | | AssocReq9; M | AssocReq10; M | AssocReq11; M | +| | | AssocReq12; M | | | +| Test purpose | Check that:
    The association procedure data exchange is correct. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 | | | | +| Other PICS | C_AG_OXP_017 | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Unassociated state. | | | | +| Test procedure | 1. The PHD under test sends an AARQ message to the simulated PHG. The expected fields sent by the PHD are:
    1. APDU Type
      • field-length = 2 bytes
      • field-value = 0xE2 0x00 (AareApdu)
    2. assoc-version
      • field-type = AssociationVersion
      • field-length = BITS-32
      • field-value = 0x80 0x00 0x00 0x00
      • assoc-version = 0x80 0x00 0x00 0x00 (asassoc-version1(0) set) indicates that version 1 of the association protocol is supported.
    3. data-proto-id
      • field-type = DataProtoId
      • field-length = INT-U16
      • field-value = 0x50 0x79 (20601)
      • data-proto-id = 20601 indicates exchange protocol follows this standard, and data-proto-info field shall contain PhdAssociationInformation.
    4. protocol-version
      • field-type = Protocol Version
      • field-length = BITS-32
      • field-value = 0x80 0x00 0x00 0x00
      • This value shows that version 1 of the data exchange protocol is supported (assoc-version1(0)=1),.
    5. encoding rules
      • field-type = EncodingRules
      • field-length = BITS-16
      • field-value = depends on the encoding rules supported/selected. mder(0) always is set (MDER always is supported) and xer(1) or/and per(2) may be set (optional).
    6. nomenclature version
      • field-type = NomenclatureVersion
      • field-length = BITS-32
      • field-value = 0x80 0x00 0x00 0x00
      • This value indicates version 1 is supported (nom-version1(0) is set).
    7. functional-units
      • field-type = FunctionalUnits
      • field-length = BITS-32
      • If the PHD has no Test Association capabilities: field-value = 0x00 0x00 0x00
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    0x00

    • If the PHD has tested capabilities that can be used within Test Association: field-value = 0x40 0x00 0x00 0x00
    • If the PHD has tested capabilities that can be used within Test Association and requires that the PHG establishes a Test Association: field-value = 0x60 0x00 0x00 0x00

    h. system type

    • field-type = SystemType
    • field-length = BITS-32
    • field-value = 0x00 0x80 0x00 0x00 (sys-type-agent)

    i. system-id

    • field-type = OCTET STRING
    • field-length = 0x00 0x0A
    • field-value = 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX (EUI-64 manufacturer and device). This value will be System Id attribute of MDS Object.

    j. dev-config-id

    • field-type = ConfigId
    • field-length = INT-U16
    • field-value = <between 0x40 0x00 and 0x7F 0xFF>

    k. data-req-mode-flags (DataReqModeCapab):

    • field-type = DataReqModeFlags (BITS-16)
    • field-length = INT-U16
    • If the PHD implements only this Device Specialization: field-value = 0x00 0x01 – PHD-initiated data request/flows

    l. data-req-init-agent-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • If the PHD implements only this Device Specialization: field-value = 0x01

    m. data-req-init-manager-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • If the PHD implements only this Device Specialization: field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-041 | | | +| TP label | Config Changes Service. Altitude Gain Contextual Attribute. | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj1; M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 8; M | | +| Test purpose |

    Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values.

    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_015 AND C_AG_CV_044 | +| Other PICS | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | +| Test procedure |
    1. 1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for Altitude Gain Object (meters to feet or feet to meters.)
    3. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to a new Contextual Attribute.
    | +| Notes | | + +| | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-042 | | +| TP label | Config Changes Service. Altitude Loss Contextual Attribute | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | +| | Testable items | NumObj1; M | +| | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | Communication 8; M | +| Test purpose |

    Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values.

    | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_032 AND C_AG_CV_045 | | +| Other PICS | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | +| Test procedure |
    1. 1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for the Altitude Loss object (meters to feet or feet to meters).
    3. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to a new Contextual Attribute.
    | | +| Notes | | | + +| | | | +|-----------------|--------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-043 | | +| TP label | Config Changes Service. Altitude Contextual Attribute. | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| | Testable items | NumObj1; M | | | +| | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Communication 8; M | | | +| Test purpose | Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_039 AND C_AG_CV_046 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure |
    1. 1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for the Altitude Object (meters to feet or feet to meters).
    3. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | | | | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to a new Contextual Attribute.
    | | | | +| Notes | | | | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-044 | | | | +| TP label | Config Changes Service. Distance Contextual Attribute. | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | NumObj1; M | | | +| | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Communication 8; M | | | +| Test purpose | Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values. | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_040 AND C_AG_CV_047 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | +| Test procedure |
    1. 1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for Distance object (meters to feet, feet to meters, meters to steps, steps to meters, feet to steps or steps to feet).
    3. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | | | | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has
    | | | | + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------| +| |

    been changed.

    • Data has changed accordingly to new Contextual Attribute.
    | +| Notes | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-045 | | | +| TP label | Config Changes Service. Ascent Time and Distance Contextual Attribute. | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj1; M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 8; M | | +| Test purpose |

    Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values.

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_041 AND C_AG_CV_048 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. Make a change to the Contextual Attribute Unit-Code for Ascent Time and Distance object (meters to feet, feet to meters, meters to steps, steps to meters, feet to steps or steps to feet).
    3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. Take some more measurements.
    5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | | | +| Pass/Fail criteria |
    • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • Data has changed accordingly to new Contextual Attribute.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-046 | | | +| TP label | Config Changes Service. Descent Time and Distance Contextual Attribute. | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj1; M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 8; M | | +| Test purpose |

    Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values.

    | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_042 AND C_AG_CV_049 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. If the attribute that is going to be changed is reported in a Fixed format event report,
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    take some measurements with the PHD under test.

    1. 2. Make a change to the Contextual Attribute Unit-Code for Descent Time and Distance object (meters to feet, feet to meters, meters to steps, steps to meters, feet to steps or steps to feet).
    2. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    3. 4. Take some more measurements.
    4. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to new Contextual Attribute.
    | +| Notes | | + +| | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-047 | | +| TP label | Config Changes Service. Speed Contextual Attribute. | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | +| | Testable items | NumObj1; M | +| | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | Communication 8; M | +| Test purpose |

    Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values.

    | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_035 AND C_AG_CV_050 | | +| Other PICS | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | +| Test procedure |
    1. 1. If attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for Speed Object (meters per minute to feet, inches or steps per minute, feet per minute to meters, inches or steps per minute, steps per minute to meters, feet or inches per minute, or inches per minute to meters, feet or steps per minute).
    3. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to new Contextual Attribute.
    | | +| Notes | | | + +| | | | +|-----------------|-------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-048 | | +| TP label | Config Changes Service. Incline Contextual Attribute. | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | +| | Testable items | NumObj1; M | + +| | | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|--| +| | Spec | [b-ITU-T H.810 (2015)] | | | | +| | Testable items | Communication 8; M | | | | +| Test purpose | Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values. | | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_033 AND C_AG_CV_051 | | | | | +| Other PICS | | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | | +| Test procedure |
    1. 1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for Incline object (percent to angle degrees or angle degrees to percent).
    3. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | | | | | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to new Contextual Attribute.
    | | | | | +| Notes | | | | | | + +| | | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-049 | | | | | +| TP label | Config Changes Service. Stride-Length Contextual Attribute. | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | | +| | Testable items | NumObj1; M | | | | +| | Spec | [b-ITU-T H.810 (2015)] | | | | +| | Testable items | Communication 8; M | | | | +| Test purpose | Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values. | | | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_027 AND C_AG_CV_052 | | | | | +| Other PICS | | | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | | | +| Test procedure |
    1. 1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for Stride Length object (meters to inches or inches to meters).
    3. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | | | | | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to new Contextual Attribute.
    | | | | | + +| | | +|--------------|--| +| Notes | | +|--------------|--| + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-050 | | | +| TP label | Config Changes Service. Energy Expended Contextual Attribute. | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj1; M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 8; M | | +| Test purpose | Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_025 AND C_AG_CV_053 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for Energy Expended object (calories to joules or joules to calories).
    3. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | | | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to new Contextual Attribute.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-051 | | | +| TP label | Config Changes Service. Body Weight Contextual Attribute. | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj1; M | | +| | Spec | [ITU-T H.810(2015)] | | +| | Testable items | Communication 8; M | | +| Test purpose | Check that:

    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_020 AND C_AG_CV_054 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for Body Weight object (grams to pounds or pounds to grams).
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    2. 4. Take some more measurements.
    3. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to new Contextual Attribute.
    | +| Notes | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-052 | | | +| TP label | Config Changes Service. Height Contextual Attribute. | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | +| | Testable items | NumObj1; M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 8; M | | +| Test purpose | Check that:
    Whenever a Contextual Attribute changes, the PHD shall report these changes to the PHG using an MDS object event prior to reporting any of the dependent values. | | | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 AND C_AG_CV_020 AND C_AG_CV_054 | | | +| Other PICS | | | | +| Initial condition | The simulated PHG and the PHD under test are in the Operating state. | | | +| Test procedure |
    1. 1. If the attribute that is going to be changed is reported in a Fixed format event report, take some measurements with the PHD under test.
    2. 2. Make a change to the Contextual Attribute Unit-Code for Height Object (meters to feet or feet to meters).
    3. 3. The PHD shall send an MDS event report indicating the new Contextual Attribute value.
    4. 4. Take some more measurements.
    5. 5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.
    | | | +| Pass/Fail criteria |
    • • The PHD sends an MDS event report to inform about the Contextual Attribute that has been changed.
    • • Data has changed accordingly to new Contextual Attribute.
    | | | +| Notes | | | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHD/CLASS/CV/BV-053 | | | +| TP label | Operating State. PHG to PHD Maximum APDU Size | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 3; M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Cardio_DG 1; M | | +| Test purpose | Check that:
    Check that the total size of the response does not exceed the maximum APDU size | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | established by the specialization
    [AND]
    Continua PAN step counter service components shall be able to support a maximum APDU size of 224 octets from Continua PAN client components. | +| Applicability | C_AG_OXP_000 AND C_AG_OXP_172 | +| Other PICS | C_AG_OXP_041, C_AG_OXP_100, C_AG_CV_001 | +| Initial condition | The simulated PHG and the PHD are in the Operating state. | +| Test procedure |
    1. 1. IF the PHD supports Step Counter sub-specialization (C_AG_CV_001=TRUE) THEN the simulated PHG issues a "Remote Operation Invoke Get" command with:
      1. a. Obj-handle set to 0 (to request for MDS object)
      2. b. attribute-id-list.count = 103
      3. c. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 34 times followed by an additional MDC_ATTR_ID_MODEL
      ELSE (the PHD does not support Step Counter sub-specialization) THEN the simulated PHG issues a "Remote Operation Invoke Get" command with:
      1. d. Obj-handle set to 0 (to request for MDS object)
      2. e. attribute-id-list.count = 4087
      3. f. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 1362 times followed by an additional MDC_ATTR_ID_MODEL
    2. 2. Check the response of the PHD.
    3. 3. The simulated PHG issues a "Remote Operation Invoke Get" command with the handle set to 0 (to request for MDS object) and an empty attribute-id-list to indicate all attributes.
    4. 4. Check the response of the PHD.
    | +| Pass/Fail criteria |
    • • In step 2, the PHD under test may respond with a rors-cmip-get listing all the requested attributes, or with a roer message. If PICS C_AG_OXP_100=TRUE and the PHD does not respond with a rors-cmip-get message, it responds with a roer message or rorj(resource-limitation) message, a WARNING will appear.
      • ○ If the response is a get response, the total size of the response cannot exceed the sum of the APDU sizes of the supported specializations (limited to an absolute limit of 64512 octets):
        • ▪ Pulse oximeter → 9216 octets
        • ▪ Weighing scales → 896 octets
        • ▪ Glucose meter → 5120 octets or 64512 octets if PHD supports PM-Store
        • ▪ Blood pressure → 896 octets
        • ▪ Thermometer → 896 octets
        • ▪ Independent activity hub → 5120 octets
        • ▪ Cardiovascular → 64512 octets or 6624 octets if the PHD under test only supports Step Counter Profile
        • ▪ Strength → 64512 octets:
        • ▪ Adherence monitor → 1024 octets
        • ▪ Peak flow → 2030 octets
        • ▪ Body composition analyser → 7730 octets
        • ▪ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store
        • ▪ Basic ECG/Heart Rate → 1280 octets or 64512 octets if the PHD supports PM-Store
        • ▪ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store
    | + +| | | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ○ In the case where it responds with a roer, the reason must not be protocol-violation (23)
    • • In step 4, the PHD must respond with a rors-cmip-get message.
    | +| Notes | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0. (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12): *ETSI drafting rules*. +- [b-IEEE 11073-20601] IEEE Std 11073-20601 (2008): *Optimized exchange protocol*. +- [b-PHD PICS & PIXIT] Personal Health Device DG2016 PICS and PIXIT excel sheet v1.11. + +- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9. + +- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8 + +- [b-TCRL] Test Case Reference List\_DG2016\_v1.11 + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.846-201911-I_PDF-E/raw.md b/marked/H/T-REC-H.846-201911-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e0f9e637072a99df3a4854c8f33c89306dee3c2f --- /dev/null +++ b/marked/H/T-REC-H.846-201911-I_PDF-E/raw.md @@ -0,0 +1,7429 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.846** + +(11/2019) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 6: Personal Health Gateway** + +Recommendation ITU-T H.846 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T H.846 + +# Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 6: Personal Health Gateway + +## Summary + +Recommendation ITU-T H.846 provides a test suite structure (TSS) and the test purposes (TP) for Personal Health Gateways in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2017) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.846 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 6: Device Specializations. Personal Health Gateway (Version 1.9, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +This 2019 revision includes the power status monitor of Personal Health Devices device specialization (ISO/IEEE 11073-10427:2018) test cases as well as minor corrections. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.846 | 2015-01-13 | 16 | 11.1002/1000/12275 | +| 2.0 | ITU-T H.846 | 2016-07-14 | 16 | 11.1002/1000/12953 | +| 3.0 | ITU-T H.846 | 2017-04-29 | 16 | 11.1002/1000/13233 | +| 4.0 | ITU-T H.846 | 2018-08-29 | 16 | 11.1002/1000/13684 | +| 5.0 | ITU-T H.846 | 2019-05-14 | 16 | 11.1002/1000/13909 | +| 6.0 | ITU-T H.846 | 2019-11-29 | 16 | 11.1002/1000/14119 | + +## Keywords + +Conformance testing, Continua Design Guidelines, e-health, IEEE 11073 device specialization, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, Personal Health Gateway, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|-------------------------------------------------------------------------|-----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 4 | +| 3.1 | Terms defined elsewhere ..... | 4 | +| 3.2 | Terms defined in this Recommendation ..... | 4 | +| 4 | Abbreviations and acronyms ..... | 4 | +| 5 | Conventions ..... | 5 | +| 6 | Test suite structure (TSS) ..... | 7 | +| 7 | Electronic attachment ..... | 9 | +| Annex A | Test purposes ..... | 10 | +| A.1 | TP definition conventions..... | 10 | +| A.2 | Subgroup 2.3.1: Weighing scales (WEG) ..... | 12 | +| A.3 | Subgroup 2.3.2: Glucose meter (GL) ..... | 27 | +| A.4 | Subgroup 2.3.3: Pulse oximeter (PO)..... | 61 | +| A.5 | Subgroup 2.3.4: Blood pressure monitor (BPM)..... | 75 | +| A.6 | Subgroup 2.3.5: Thermometer (TH)..... | 95 | +| A.7 | Subgroup 2.3.6: Cardiovascular (CV) ..... | 110 | +| A.8 | Subgroup 2.3.7: Strength (ST)..... | 114 | +| A.9 | Subgroup 2.3.8: Activity hub (HUB) ..... | 118 | +| A.10 | Subgroup 2.3.9: Adherence monitor (AM) ..... | 122 | +| A.11 | Subgroup 2.3.10: Insulin pump (IP) ..... | 148 | +| A.12 | Subgroup 2.3.11: Peak flow (PF) ..... | 180 | +| A.13 | Subgroup 2.3.12: Body composition analyser (BCA)..... | 192 | +| A.14 | Subgroup 2.3.13: Basic electrocardiograph (ECG) ..... | 215 | +| A.15 | Subgroup 2.3.14: International normalized ratio (INR) ..... | 230 | +| A.16 | Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) ..... | 253 | +| A.17 | Subgroup 2.3.16: Continuous glucose monitor (CGM) ..... | 268 | +| A.18 | Subgroup 2.3.17: Power status monitor (PSM)..... | 282 | +| | Bibliography..... | 317 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 6: Device Specializations. Personal Health Gateway (Version 1.9, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.4 | 2012-10-05 | Initial release for Test Tool DG2011. It uses "TSS&TP_1.5_PAN-LAN_PART_6_v1.3.doc" as a baseline and adds the following maintenance bugs fixes:
    • • TP/PLT/MAN/CLASS/AM/BV-032: Modified according to bug report 874
    • • TP/PLT/MAN/CLASS/PF/BV-013: Modified according to bug report 875
    | +| 1.5 | 2013-05-24 | Initial release for Test Tool DG2012. It uses "TSS&TP_DG2011_PAN-LAN_PART_6_v1.4.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • • Adds glucose meter new spec version
    • • Adds body composition analyser device specialization
    • • Adds basic electrocardiograph device specialization
    | +| 1.6 | 2014-01-24 | Initial release for Test Tool DG2013. It uses "TSS&TP_DG2012_PAN-LAN_PART_6_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds BLE glucose meter
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR Device Specialization
    | +| 1.7 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_6_v1.6.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row has been added
    | +| 1.8 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_PLT_PART_6_v1.7.doc" as a baseline and adds new features included in [ITU-T H.810 (2015)]/[b-CDG 2015] | +| 1.9 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_6_v1.8.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016] | +| 1.10 | 2018-02-27 | Updates related to the inclusion of the power status monitor of Personal Health Devices device specialization [ISO/IEEE 11073-10427]
    Updates related to the inclusion of modifications of the glucose meter device specialization [ISO/IEEE 11073-10417] | +| 1.11 | 2018-10-17 | Updates related to the inclusion of the Power Status Monitor of Personal Health Devices device specialization (ISO/IEEE 11073-10427:2018) test cases. | +| 1.12 | 2019-06-13 | Second maintenance release for Test Tool DG2017. It uses ITU-T H.846 (05/2019) as a baseline and adds some updates according to the 2018/2019 maintenance activity. | + +# **Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 6: Personal Health Gateway** + +# **1 Scope** + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2017)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 6. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Device. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) + - Part 5Q: Power status monitor (PSM) + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- **Part 6: Device specializations. Personal Health Gateway** +- Part 7: Continua Design Guidelines. Personal Health Device BLE +- Part 8: Continua Design Guidelines. Personal Health Gateway BLE +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Device +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2017)] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal health systems*. +- [ISO/IEEE 11073-10404] ISO/IEEE 11073-10404:2010, *Health informatics – Personal health device communication – Part 10404: Device specialization – Pulse oximeter*. + +- [ISO/IEEE 11073-10406] ISO/IEEE 11073-10406-2012, *Health informatics – Personal health device communication – Part 10406: Device specialization – Basic electrocardiograph (ECG) (1- to 3-lead ECG)*. + +- [ISO/IEEE 11073-10407] ISO/IEEE 11073-10407:2010, *Health informatics – Personal health device communication – Part 10407: Device specialization – Blood pressure monitor, version 1.0*. + +- [ISO/IEEE 11073-10408] ISO/IEEE 11073-10408:2010, *Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer*. + +- [ISO/IEEE 11073-10415] ISO/IEEE 11073-10415:2010, *Health informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale*. + +- [ISO/IEEE 11073-10417] ISO/IEEE 11073-10417:2017, *Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter*. + +- [ISO/IEEE 11073-10418C] ISO/IEEE 11073-10418-2014, *Health informatics – Personal health device communication – Part 10418: Device specialization – International Normalized Ratio (INR) monitor, including ISO/IEEE 11073-10418:2014/Cor 1:2016*. + with + + +- [ISO/IEEE 11073-10419] ISO/IEEE 11073-10419:2016, *Health informatics – Personal health device communication – Part 10419: Device specialization – Insulin pump.* + +- [ISO/IEEE 11073-10420] ISO/IEEE 11073-10420-2012, *Health informatics – Personal health device communication – Part 10420: Device specialization – Body composition analyzer.* + +- [ISO/IEEE 11073-10421] ISO/IEEE 11073-10421:2012, *Health informatics – Personal health device communication – Part 10421: Device specialization – Peak expiratory flow monitor (peak flow).* + +- [ISO/IEEE 11073-10424] ISO/IEEE 11073-10424:2016, *Health informatics – Personal health device communication – Part 10424: Device specialization – Sleep apnoea breathing therapy equipment (SABTE).* +NOTE – equivalent to IEEE 11073-10424-2014, *Health informatics – Personal health device communication – Part 10424: Device Specialization – Sleep Apnoea Breathing Therapy Equipment (SABTE).* + +- [ISO/IEEE 11073-10425] ISO/IEEE 11073-10425:2016, *Health informatics – Personal health device communication - Part 10425: Device specialization – Continuous glucose monitor (CGM).* + +- [ISO/IEEE 11073-10427] ISO/IEEE 11073-10427:2018, *Health informatics – Personal health device communication – Part 10427: Device specialization – Power status monitor of personal health devices.* + Same publication as + +- [ISO/IEEE 11073-10441] ISO/IEEE 11073-10441:2015, *Health informatics – Personal Health Device Communication – Part 10441: Device Specialization – Cardiovascular fitness and activity monitor.* (Revision of IEEE Std 11073-10441-2008). + +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization.* +NOTE – This is shorthand to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. +- [ISO/IEEE 11073-10442] ISO/IEEE 11073-10442:2015, *Health informatics – Personal health device communication – Part 10442: Device specialization – Strength fitness equipment.* + +- [ISO/IEEE 11073-10471] ISO/IEEE 11073-10471:2010, *Health informatics – Personal health device communication – Part 10471: Device specialization – Independent living activity hub.* + + +- [ISO/IEEE 11073-10472] ISO/IEEE 11073-10472:2012, *Health informatics – Personal health device communication – Part 10472: Device specialization – Medication monitor*. + +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|--------------------------------| +| ATS | Abstract Test Suite | +| BPM | Blood Pressure Monitor | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MAP | Mean arterial pressure | +| MDS | Medical Device System | +| NaN | Not a number | + +| | | +|-------|-------------------------------------------------------| +| NFC | Near Field Communication | +| NRes | Not at this resolution | +| PAN | Personal Area Network | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| PSM | Power Status Monitor | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| UI | User interface | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to "must" or "it is required to". +- SHALL NOT is equivalent to "must not" or "it is not allowed". +- SHOULD is equivalent to "it is recommended to". +- SHOULD NOT is equivalent to "it is not recommended to". +- MAY is equivalent to "is permitted". +- MAY NOT is equivalent to "it is not required that". + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +In this document, "0x" denotes a number in hexadecimal format and a B after a number enclosed by single quotation marks (e.g., '0100'B) denotes a number in binary format. INT-Ux is used to denote an unsigned integer number with x bits (e.g., INT-U16 is an unsigned integer with 16 bits). + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2017 | – | 7.0 | Release 2017 of the CDG including maintenance updates of the CDG 2016 and additional guidelines that cover new functionalities. | – | +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [ITU-T H.810 (2016)]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-ITU-T H.810 (2015)]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-ITU-T H.810 (2013)]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6, 2.3.7, 2.3.8, 2.3.9, 2.3.10, 2.3.11, 2.3.12, 2.3.13, 2.3.14, 2.3.15 and 2.3.16 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (EXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Subgroup 1.3.17: Power status monitor (PSM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + +- Subgroup 1.4.2: Whitepaper thermometer requirements (TH) +- Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - **Subgroup 2.3.1: Weighing scales (WEG)** + - **Subgroup 2.3.2: Glucose meter (GL)** + - **Subgroup 2.3.3: Pulse oximeter (PO)** + - **Subgroup 2.3.4: Blood pressure monitor (BPM)** + - **Subgroup 2.3.5: Thermometer (TH)** + - **Subgroup 2.3.6: Cardiovascular (CV)** + - **Subgroup 2.3.7: Strength (ST)** + - **Subgroup 2.3.8: Activity hub (HUB)** + - **Subgroup 2.3.9: Adherence monitor (AM)** + - **Subgroup 2.3.10: Insulin pump (IP)** + - **Subgroup 2.3.11: Peak flow (PF)** + - **Subgroup 2.3.12: Body composition analyser (BCA)** + - **Subgroup 2.3.13: Basic electrocardiograph (ECG)** + - **Subgroup 2.3.14: International normalized ratio (INR)** + - **Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE)** + - **Subgroup 2.3.16: Continuous glucose monitor (CGM)** + - **Subgroup 2.3.17: Power status monitor (PSM)** + +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 2.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . See [b-PHD PICS & PIXIT] and [b-PHG PICS & PIXIT] and [b-TI]. + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP/TT>//// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth Low Energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. + +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 2.3.1: Weighing scales (WEG) + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---------------------------| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-001 | | | +| TP label | Association procedure PHG WEG | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | Weighing.Association 8;O | Weighing.Association 12;M | +| | | Weighing.Association 14;M | Weighing.Association 15;M | +| | | Weighing.Association 17;M | Weighing.Association 18;M | +| | | Weighing.Association 20;M | Weighing.Association 21;M | +| | | Weighing.Association 23;M | | +| Test purpose |

    Check that:

    Association Response data exchange (data-proto-id, data- proto-info):

    [data-proto-info field parameters]: The Personal Health Gateway (PHG) may use this field (System-Id) to determine the identity of the weighing scale with which it is associating and, optionally, to implement a simple access restriction policy

    [AND]

    [association response]: The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601.

    [AND]

    [association response]: In the DataProtoList structure element, the data protocol identifier shall be set to data-proto-id-20601 (i.e., data-proto-id = 0x5079)

    [AND]

    [association response data-proto-info field parameters]: The version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = 0x80000000)

    [AND]

    [association response data-proto-info field parameters]: The PHG shall respond with a single selected encoding rule that is supported by both Personal Health Device (PHD) and PHG.

    [AND]

    [association response data-proto-info field parameters]: The PHG shall support at least the MDER encoding rules

    [AND]

    [association response data-proto-info field parameters]: The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    [association response data-proto-info field parameters]: The field functional-units shall have all bits reset except for those relating to a Test Association

    [AND]

    [association response data-proto-info field parameters]: The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    [association response data-proto-info field parameters]: The system-id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    [association response data-proto-info field parameters]: The field dev-config-id shall be manager-config-response (0)

    [AND]

    | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [association response data-proto-info field parameters]: The field data-req-mode-capab shall be 0
    [AND]
    [association response data-proto-info field parameters]: The fields data-req-init-*-count shall be 0 | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '10000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16449
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0;
    2. 2. The PHG under test sends an association response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
          • ▪ If association is rejected-permanent, field-value= 0x00 0x01.
          • ▪ If association is rejected-transient, field-value= 0x00 0x02.
          • ▪ If association is accepted-unknown-config, field-value= 0x00 0x03.
          • ▪ If association is rejected-no-common-protocol, field-value= 0x00 0x04.
          • ▪ If association is rejected-no-common-parameter, field-value= 0x00 0x05.
          • ▪ If association is rejected-unknown,field-value= 0x00 0x06.
          • ▪ If association is rejected-unauthorized, field-value= 0x00 0x07.
          • ▪ If association is rejected–unsupported-assoc-version, field-value= 0x00 0x08.
      3. c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id))
      4. d. data-proto-id
        • field-type = DataProtoId
        • field-length = 2 bytes
        • field-value= 0x50 0x79 (20601)
    | + +- e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x80 0x00 0x00 0x00 +- f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time +- g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value= Bit 0 must be set (nom-version1) +- h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set +- i. system type + - field-type = SystemType + - field-length = 4 bytes (BITS-32) + - field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) +- j. system-id + - field-type = OCTET STRING + - field-length = 8 bytes + - field-value = (EUI-64 manufacturer and device) +- k. dev-config-id + - field-type = ConfigId + - field-length = 2 bytes + - field-value = 0x00 0x00 (manager-config-response) +- l. data-req-mode-flags (DataReqModeCapab) + - field-type = DataReqModeFlags + - field-length = 2 bytes + - field-value = 0x00 0x00 + - PHG response to data-req-mode-flags is always 0. +- m. data-req-init-agent-count (DataReqModeCapab) + - field-type = INT-U8 + - field-length = 1 byte + - field-value = 0x00 +- n. data-req-init-manager-count (DataReqModeCapab) + - field-type = INT-U8 + - field-length = 1 byte + +| | | +|---------------------------|-----------------------------------------------------------------------------------------| +| | field-value = 0x00 b | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-002 | | | +| TP label | Configuration Event Report. Weighing Scale standard configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4..

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x05 0xDC (Weighing Scales).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    If the result of the association response was "accepted-unknown-config"

    1. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x05 0xDC
    2. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value= it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value: 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in the Operating state the PHG is forced to enable the scanner object

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | See bug http://continua.plugfest.com/show_bug.cgi?id=123 | + +| | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-003 | | +| TP label | Attribute-Value-Map. Order change. | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | +| | Testable items | WeightNumClass 22;M | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Body Weight Object) to reverse the values to: MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_VAL_OBS_SIMP.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date first followed by a weight value (in kilograms since it is the standard configuration unit code).
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS). The weight observation should be a reasonable kilogram weight observation.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes. E.g., if there is a user interface (UI), verify that the measurement and date are displayed properly.
    • • In steps 2, 6 and 12 verify that the PHG under test uses kilograms as the unit-code for the measurement report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|-----------------|------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-004 | | | +| TP label | Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 22;M | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS. The PHG accepts the measurements (fixed format event report) and shows them correctly when the unit-code is changed.

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 AND C_MAN_WEG_001 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. (Body Weight Numeric standard configuration Unit code attribute is set to MDC_DIM_KILO_G) | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Body Weight Object) to set the values to: MDC_ATTR_NU_VAL_OBS_SIMP, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_ABS.
    2. The simulated PHD waits until it receives a confirmation.
    3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute, use pounds MDC_DIM_LB (1760).
    4. The simulated PHD waits until it receives a confirmation.
    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_SIMP attribute.
    6. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement is displayed properly).
    • In steps 4 and 6, verify that the PHG under test uses pounds as the unit-code for the measurement reports.
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-005 | | | +| TP label | Unit-Code. Change from default kilograms to pounds – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 20;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Unit-Code] attribute shall be present

    The value of the [Unit-Code] attribute shall be MDC_DIM_KILO_G.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 AND C_MAN_WEG_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (Body Weight Object) to pounds nomenclature code MDC_DIM_LB (1760).
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report using a measurement in pounds followed by date and time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends an association release request (normal).
    6. 6. The simulated PHD waits until it receives an association release response.
    7. 7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. 8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    9. 9. The simulated PHD sends a fixed event report with an observation in kilograms followed by date and time stamp.
    10. 10. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies pounds to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies kilograms to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-005_A | | | +| TP label | Unit-Code. Do not change from default kilograms to pounds – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 20;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_KILO_G. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 AND (NOT(C_MAN_WEG_001)) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (Body Weight Object) to pounds nomenclature code MDC_DIM_LB (1760).
    2. 2. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or until TO cer-mds expires.
    3. 3. If the PHG has sent a confirmation in step 2, send a confirmed fixed format event report using a measurement in pounds followed by date and time stamp.
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or TO cer-mds expires.

    5. If the PHG has sent a confirmation in step 4, ask to the operator if the measurements have been properly received and displayed.

    | +| Pass/Fail criteria |
    • • In step 2, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • • In step 4, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • • In step 5, verify that measurements do not appear, or if they do appear, they are somehow designated as 'unsupported' data.
    | +| Notes | | + +| | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-006 | | +| TP label | Unit-Code. Use default kilograms – variable format observation. | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | +| | Testable items | WeightNumClass 20;M | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Unit-Code] attribute shall be present

    The value of the [Unit-Code] attribute shall be MDC_DIM_KILO_G

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | +| Test procedure |

    1. Send a confirmed variable format event report using a measurement in kilograms.

    2. The simulated PHD waits until it receives a confirmation.

    | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data properly and applies kilograms to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | +| Notes | | | + +| | | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-007 | | +| TP label | Unit-Code. Change from default kilograms to pounds – variable format observation | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | +| | Testable items | WeightNumClass 20;M | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Unit-Code] attribute shall be present

    The value of the [Unit-Code] attribute shall be MDC_DIM_KILO_G

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 AND C_MAN_WEG_001 | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. Send a confirmed variable format event report to set the unit code to pounds MDC_DIM_LB (1760) for handle 1 (Body Weight Object) and a measurement in pounds
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a second confirmed variable format event report with just a measurement in pounds (i.e., do not transmit the unit-code attribute in the event report).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends an association release request (normal).
    6. 6. The simulated PHD waits until it receives an association release response.
    7. 7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. 8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    9. 9. The simulated PHD sends a confirmed variable event report with an observation in kilograms followed by date and time stamp (i.e., do not send the unit-code attribute it should be set to kilograms by the standard configuration).
    10. 10. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2 and 4, verify that the PHG under test is able to accept the data properly and applies pounds to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies kilograms to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-008 | | +| TP label | Maximum APDU size: Weighing Scale | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 4;M | +| Test purpose |

    Check that:

    If a PHG receives APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | +| Other PICS | | | +| Initial condition | The PHG under test is in the Operating state. | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure | 1. The simulated PHD sends a Confirmed variable event report:
    1. ScanReportInfoVar. obs_scan_var:
      • Count = 2
      • Length = 858
       ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00 (832 bytes) 00'O     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2646 (MDC_ATTR_NU_VAL_OBS_SIMP)       attribute-value: 68     }   } }
    2. Check the response of the PHG under test.
    3. The simulated PHD sends a confirmed fixed format event report with one measurement.
    4. Check the response of the PHG under test. | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-009 | | | +| TP label | Special values. Not a number – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 22; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight Object) containing an observation with the value for "not a number" (NaN, [exponent 0, mantissa + $(2^{23} - 1)$ = 0x007FFFFFF]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as
    | | | + +| | | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-010 | | | +| TP label | Special values. Not a number – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 27; C | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight Object) containing an observation with the value for NaN ([exponent 0, mantissa +(2^{23}-1) = 0x007FFFFF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-011 | | | +| TP label | Special values. Not at this resolution – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 22; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight Object) containing an observation with the value for "not at this resolution" (NRes, [exponent 0, mantissa -(2^{23}) = 0x00800000]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-012 | | | +| TP label | Special values. Not at this resolution – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 27; C | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight Object) containing an observation with the value for NRes ([exponent 0, mantissa – (2**23) = 0x00800000])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-013 | | | +| TP label | Special values. Positive infinity – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 22; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 containing an observation with the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**23 –2) = 0x007FFFFE]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-014 | | | +| TP label | Special values. Positive infinity – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 27; C | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight Object) containing an observation with the value for positive infinity (+INFINITY, [exponent 0, mantissa +( $2^{23} - 2$ ) = 0x007FFFFE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-015 | | | +| TP label | Special values. Negative infinity – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 22; M | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight Object) containing an observation with the value for negative infinity (–INFINITY, [exponent 0, mantissa –( $2^{23} - 2$ ) = 0x00800002]) and a time stamp. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-016 | | | +| TP label | Special values. Negative infinity – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 27; C | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight Object) containing an observation with the value for negative infinity (–INFINITY, [exponent 0, mantissa $-(2^{23}-2) = 0x00800002$ ]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-017 | | | +| TP label | Special values. Reserved – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 22; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Object) containing an observation with the value that is reserved (Reserved for future use, [exponent 0, mantissa $-(2^{23}-1) = 0x00800001$ ]) and a time stamp. | +| | 2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/WEG/BV-018 | | | +| TP label | Special values. Reserved – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10415] | | +| | Testable items | WeightNumClass 27; C | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_024 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight Object) containing an observation with the value for reserved (Reserved for future use, [exponent 0, mantissa $-(2^{23}-1) = 0x00800001$ ]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +### A.3 Subgroup 2.3.2: Glucose meter (GL) + +| | | | | +|---------------------|----------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-000 | | | +| TP label | Association procedure PHG GL | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | ManProcAs 1;M
    ManProcAs 4;M
    ManProcAs 7;M
    ManProcAs 10;M | ManProcAs 2;M
    ManProcAs 5;M
    ManProcAs 8;M
    ManProcAs 11;M | +| Test purpose | Check that:
    The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601. | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-proto-id-20601.

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version3 (i.e., protocol-version = 0x20000000)

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    The fields data-req-init-*-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '00100000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16440
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an association response. The fields of interest are:
    | + +- a. APDU Type + - field-length = 2 bytes + - field-value = 0xE3 0x00 (AareApdu) +- b. Result + - field-type = AssociateResult + - field-length = 2 bytes + - field-value = One of the following: + - If association is accepted, field-value= 0x00 0x00. + - If association is rejected-permanent, field-value= 0x00 0x01. + - If association is rejected-transient, field-value= 0x00 0x02. + - If association is accepted-unknown-config, field-value= 0x00 0x03. + - If association is rejected-no-common-protocol, field-value= 0x00 0x04. + - If association is rejected-no-common-parameter, field-value= 0x00 0x05. + - If association is rejected-unknown = 0x00 0x06. + - If association is rejected-unauthorized, field-value= 0x00 0x07. + - If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08. +- c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) +- d. data-proto-id + - field-type = DataProtoId + - field-length = 2 bytes + - field-value= 0x50 0x79 (20601) +- e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x20 0x00 0x00 0x00 +- f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time +- g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value= Bit 0 must be set (nom-version1) +- h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set +- i. system type + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-type = SystemType
    • field-length = 4 bytes (BITS-32)
    • field-value = 0x80 0x00 0x00 0x00 (sys-type-manager)
    j. system-id
    • field-type = OCTET STRING
    • field-length = 8 bytes
    • field-value = (EUI-64 manufacturer and device)
    k. dev-config-id
    • field-type = ConfigId
    • field-length = 2 bytes
    • field-value = 0x00 0x00 (manager-config-response)
    l. data-req-mode-flags (DataReqModeCapab)
    • field-type = DataReqModeFlags
    • field-length = 2 bytes
    • field-value = 0x00 0x00
    • PHG response to data-req-mode-flags is always 0.
    m. data-req-init-agent-count (DataReqModeCapab)
    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00
    n. data-req-init-manager-count (DataReqModeCapab)
    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +| | | | | | +|-----------------|-----------------------------------------------------------------------|---------------------------------------------------------------|---------------|----------------| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-001_A | | | | +| TP label | Configuration Event Report. Glucose Meter standard configuration 1701 | | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | | +| | Testable items | ConfProc 4;M | MDSEvents 2;M | ObjAccServ 5;M | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | | +| | Testable items | ConfEventRep 18;M | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a “Remote Operation Response Confirmed Event Report” data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field.

    [AND]

    A PHG shall support both single-person and multi-person event reports.

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | +| Other PICS | C_MAN_OXP_085 | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. The simulated PHD implements a glucose meter device specialization with standard configuration 1701. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x06 0xA5 (Glucose Meter – Std Config 1701).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x06 0xA5
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value= it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value: 0xXX 0xXX
      5. e. Event-type:
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 2 bytes
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    Wait until the Operating state is reached in both cases.

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one Blood Glucose (Undetermined plasma reference method) measurement and other fixed event report with Control Solution measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurements are correctly presented.
    | +| Notes | | + +| | | | | +|-----------------|-----------------------------------------------------------------------|---------------------------------------------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-001_B | | | +| TP label | Configuration Event Report. Glucose Meter standard configuration 1702 | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | ConfProc 4;M | MDSEvents 2;M | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a "Remote Operation Response Confirmed Event Report" data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field.

    [AND]

    A PHG shall support both single-person and multi-person event reports.

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | +| Other PICS | C_MAN_OXP_085 | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. The simulated PHD implements a glucose meter device specialization with standard configuration 1701. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x06 0xA6 (Glucose Meter – Std Config 1702).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x06 0xA6
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value= it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value: 0xXX 0xXX
      5. e. Event-type:
    | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 2 bytes
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    Wait until the Operating state is reached in both cases.

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends three fixed event reports: Blood Glucose (Undetermined plasma reference method) measurement, Control Solution measurement and Meal Context measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurements are correctly presented.
    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-002 | | | +| TP label | Maximum APDU size: Glucose Meter without PM-Store | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4;M | | +| | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | ComChar 2; M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 5080
         ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(5056 bytes)..... 00'0     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)       attribute-value: 100     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a confirmed fixed format event report with one measurement.
    4. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-002_A | | +| TP label | Maximum APDU size: Glucose Meter with PM-Store | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 4;M | +| | Spec | [ISO/IEEE 11073-10417] | +| | Testable items | ComChar 2; M | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND C_MAN_OXP_003 | | +| Other PICS | | | +| Initial condition | The PHG under test is in the Operating state. | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar.obs_scan_var:
        • Count = 2
        • Length = 64472
         ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(64448 bytes)..... 00'O     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)       attribute-value: 80     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a confirmed fixed format event report with one measurement.
    4. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-003 | | +| TP label | Blood Glucose Attribute-Value-Map. Order change (Std Config 1701) | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | +| | Testable items | BloodGL 10;M | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_ABS | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_ABS.
    | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The simulated PHD waits until it receives a confirmation.
    2. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Blood Glucose Object) to reverse the values to: MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_VAL_OBS_BASIC.
    3. 4. The simulated PHD waits until it receives a confirmation.
    4. 5. Send a confirmed fixed format event report with the date first followed by a blood glucose value (in mg/dL since it is the standard configuration unit code).
    5. 6. The simulated PHD waits until it receives a confirmation.
    6. 7. The simulated PHD sends an association release request (normal).
    7. 8. The simulated PHD waits until there is an association release response.
    8. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    9. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    10. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_ABS). The observation should be a reasonable mg/dL blood glucose observation.
    11. 12. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that the PHG under test uses mg/dL as the unit code for the measurement report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-003_A | | | +| TP label | Blood Glucose Attribute-Value-Map. Order change (Std Config 1702) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 32; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Blood Glucose Object) to reverse the values to: MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_NU_VAL_OBS_BASIC.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date first followed by a blood glucose value (in mg/dL since it is the standard configuration unit code).
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO). The observation should be a reasonable mg/dL blood glucose observation.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that the PHG under test uses mg/dL as the unit code for the measurement report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|-----------------|--------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-004 | | | +| TP label | Blood Glucose Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 10;M | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_ABS | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND C_MAN_GL_001 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. (Blood Glucose Numeric standard configuration Unit code attribute is set to MDC_DIM_MILLI_G_PER_DL) | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Blood Glucose Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_ABS.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute, use MDC_DIM_MILLI_MOLE_PER_L (4722).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC attribute.
    6. 6. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement is displayed properly).
    • • In steps 4 and 6, verify that the PHG under test uses mmol/L as the unit code for the measurement reports.
    | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-004_A | | | +| TP label | Blood Glucose Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map (Std Config 1702) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 32; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND C_MAN_GL_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. (Blood Glucose Numeric standard configuration Unit code attribute is set to MDC_DIM_MILLI_G_PER_DL) | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Blood Glucose Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute, use MDC_DIM_MILLI_MOLE_PER_L (4722).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC attribute.
    6. 6. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement is displayed properly).
    • • In steps 4 and 6, verify that the PHG under test uses mmol/L as the unit code for the measurement reports.
    | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-005 | | | +| TP label | Blood Glucose Unit-Code. Change from default mg/dL to mmol/L – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 8;M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 9; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MILLI_G_PER_DL
    [AND]
    Continua PAN client components that receive a report of a configuration change shall apply the change to future measurements only | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND C_MAN_GL_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (Blood Glucose Object) to mmol/L nomenclature code MDC_DIM_MILLI_MOLE_PER_L (4722).
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report using a measurement in mmol/L followed by date and time stamp.
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. The simulated PHD waits until it receives a confirmation.

    5. The simulated PHD sends an association release request (normal).

    6. The simulated PHD waits until it receives an association release response.

    7. The simulated PHD sends an association request using the same configuration that was used initially.

    8. If the PHG under test responds with association request response with "accepted-unknown-config", then

    • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
    • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.

    9. The simulated PHD sends a fixed event report with an observation in mg/dL followed by date and time stamp.

    10. The simulated PHD waits until it receives a confirmation.

    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies mmol/L to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies mg/dL to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-005_A | | | +| TP label | Blood Glucose Unit-Code. Do not change from default mg/dL to mmol/L – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 8;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Unit-Code] attribute shall be present

    The value of the [Unit-Code] attribute shall be MDC_DIM_MILLI_G_PER_DL

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND (NOT(C_MAN_GL_001)) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (Blood Glucose Object) to mmol/L nomenclature code MDC_DIM_MILLI_MOLE_PER_L (4722).
    2. 2. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or until TO cer-mds expires.
    3. 3. If the PHG has sent a confirmation in step 2, send a confirmed fixed format event report using a measurement in mmol/L followed by date and time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or TO cer-mds expires.
    5. 5. If the PHG has sent a confirmation in step 4, ask to the operator if the measurements have been properly received and displayed.
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • In step 2, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • In step 4, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • In step 5, verify that measurements do not appear, or if they do appear, they are somehow designated as 'unsupported' data.
    | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-006 | | | +| TP label | Blood Glucose Unit-Code. Use default mg/dL – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 8;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MILLI_G_PER_DL | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. Send a confirmed variable format event report using a measurement in mg/dL.
    2. The simulated PHD waits until it receives a confirmation. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data properly and applies mg/dL to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | +| Notes | | | | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-007 | | | +| TP label | Blood Glucose Unit-Code. Change from default mg/dL to mmol/L – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 8;M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 9; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MILLI_G_PER_DL
    [AND] | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Continua PAN client components that receive a report of a configuration change shall apply the change to future measurements only | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND C_MAN_GL_001 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. Send a confirmed variable format event report to set the unit code to mmol/L MDC_DIM_MILLI_MOLE_PER_L (4722) for handle 1 (Blood Glucose Object) and a measurement in mmol/L.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a second confirmed variable format event report with just a measurement in mmol/L (i.e., do not transmit the unit-code attribute in the event report).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends an association release request (normal).
    6. 6. The simulated PHD waits until it receives an association release response.
    7. 7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. 8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    9. 9. The simulated PHD sends a confirmed variable event report with an observation in mg/dL followed by date and time stamp (i.e., do not send the unit-code attribute it should be set to mg/dL by the standard configuration).
    10. 10. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2 and 4, verify that the PHG under test is able to accept the data properly and applies mmol/L to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies mg/dL to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-008 | | | +| TP label | Special values. Blood Glucose - Not a number – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 10; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Blood Glucose Object) containing an observation value with the value for NaN ([exponent 0, mantissa +(2**11 -1) = 0x07FF]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-009 | | | +| TP label | Special values. Blood Glucose - Not a number – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 20; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Blood Glucose Object) containing an observation value set to the value for NaN ([exponent 0, mantissa +(2**11 -1) = 0x07FF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or by blanking the display area).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|----------------------|--------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-010 | | | +| TP label | Special values. Blood Glucose - Not at this resolution – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 10; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Blood Glucose Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{**}11) = 0x0800]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-011 | | | +| TP label | Special values. Blood Glucose - Not at this resolution – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 20; M | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Blood Glucose Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{**}11) = 0x0800]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI,, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-012 | | | +| TP label | Special values. Blood Glucose - Positive infinity – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 10; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Blood Glucose Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 -2) = 0x07FE]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-013 | | | +| TP label | Special values. Blood Glucose - Positive infinity – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 20; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Blood Glucose Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 -2) = 0x07FE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-014 | | | +| TP label | Special values. Blood Glucose - Negative infinity – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 10; M | | +| Test purpose | Check that:
    The PHG receives a -INFINITY value (fixed format event report) but it does not use this value. | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Blood Glucose Object) containing an observation value set to the value for negative infinity (-\text{INFINITY}, [exponent 0, mantissa -(2^{11}-2) = 0x0802]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-015 | | | +| TP label | Special values. Blood Glucose - Negative infinity – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 20; M | | +| Test purpose | Check that:
    The PHG receives a $-\text{INFINITY}$ value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Blood Glucose Object) containing an observation value set to the value for negative infinity (-\text{INFINITY}, [exponent 0, mantissa -(2^{11}-2) = 0x0802]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-016 | | | +| TP label | Special values. Blood Glucose - Reserved – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 10; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | use this value. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Blood Glucose Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-017 | | | +| TP label | Special values. Blood Glucose - Reserved – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | BloodGL 20; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Blood Glucose Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|-----------------|----------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-018 | | | +| TP label | Control Solution Attribute-Value-Map. Order change (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 8;M | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_ID_PHYSIO MDC_ATTR_TIME_STAMP_ABS

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a Control Solution confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, the MDC_ATTR_ID_PHYSIO, then MDC_ATTR_TIME_STAMP_ABS
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Control Solution Object) to reverse the values to: MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_ID_PHYSIO.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date first followed by a control solution value (in mg/dL since it is the standard configuration unit code).
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_ID_PHYSIO, then MDC_ATTR_TIME_STAMP_ABS). The observation should be a reasonable mg/dL blood glucose observation.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that the PHG under test uses mg/dL as the unit code for the measurement report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-018_A | | | +| TP label | Control Solution Attribute-Value-Map. Order change (Std Config 1702) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 18; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_ID_PHYSIO MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a Control Solution confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_ID_PHYSIO, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Control Solution Object) to reverse the values to: MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_ID_PHYSIO.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date first followed by a control solution value (in mg/dL since it is the standard configuration unit code).
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_ID_PHYSIO, then MDC_ATTR_TIME_STAMP_BO). The observation should be a reasonable mg/dL blood glucose observation.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that the PHG under test uses mg/dL as the unit code for the measurement report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    | | | + +| | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-019 | | +| TP label | Control Solution Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map (Std Config 1701) | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | +| | Testable items | CtrlSol 8;M | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_ID_PHYSIO MDC_ATTR_TIME_STAMP_ABS | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND C_MAN_GL_002 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (Control Solution Numeric standard configuration Unit code attribute is set to MDC_DIM_MILLI_G_PER_DL). | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Control Solution Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, MDC_ATTR_ID_PHYSIO, then MDC_ATTR_TIME_STAMP_ABS.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute, use MDC_DIM_MILLI_MOLE_PER_L (4722).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC attribute.
    6. 6. The simulated PHD waits until it receives a confirmation.
    | | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement is displayed properly).
    • • In steps 4 and 6, verify that the PHG under test uses mmol/L as the unit code for the measurement reports.
    | | +| Notes | | | + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-019_A | +| TP label | Control Solution Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map (Std Config 1702) | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 18; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_ID_PHYSIO MDC_ATTR_TIME_STAMP_BO | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND C_MAN_GL_002 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (Control Solution Numeric standard configuration Unit code attribute is set to MDC_DIM_MILLI_G_PER_DL). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Control Solution Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, MDC_ATTR_ID_PHYSIO, then MDC_ATTR_TIME_STAMP_BO.
    2. The simulated PHD waits until it receives a confirmation.
    3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute, use MDC_DIM_MILLI_MOLE_PER_L (4722).
    4. The simulated PHD waits until it receives a confirmation.
    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC attribute.
    6. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement is displayed properly).
    • In steps 4 and 6, verify that the PHG under test uses mmol/L as the unit code for the measurement reports.
    | | | +| Notes | | | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-020 | | | +| TP label | Control Solution Unit-Code. Change from default mg/dL to mmol/L – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 6;M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 9; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The value of the [Unit-Code] attribute shall be MDC_DIM_MILLI_G_PER_DL
    [AND]
    Continua PAN client components that receive a report of a configuration change shall apply the change to future measurements only | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND C_MAN_GL_002 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 2 (Control Solution Object) to mmol/L nomenclature code MDC_DIM_MILLI_MOLE_PER_L (4722).
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report using a measurement in mmol/L followed by date and time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends an association release request (normal).
    6. 6. The simulated PHD waits until it receives an association release response.
    7. 7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. 8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    9. 9. The simulated PHD sends a fixed event report with an observation in mg/dL followed by date and time stamp.
    10. 10. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies mmol/L to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies mg/dL to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|-----------------|---------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-021 | | | +| TP label | Control Solution Unit-Code. Do not change from default mg/dL to mmol/L – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 6;M | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MILLI_G_PER_DL | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND (NOT(C_MAN_GL_002)) | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 2 (Control Solution Object) to mmol/L nomenclature code MDC_DIM_MILLI_MOLE_PER_L (4722).
    2. 2. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or until TO cer-mds expires.
    3. 3. If the PHG has sent a confirmation in step 2, send a confirmed fixed format event report using a measurement in mmol/L followed by date and time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or TO cer-mds expires.
    5. 5. If the PHG has sent a confirmation in step 4, ask to the operator if the measurements have been properly received and displayed.
    | +| Pass/Fail criteria |
    • • In step 2, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • • In step 4, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • • In step 5, verify that measurements do not appear, or if they do appear, they are somehow designated as 'unsupported' data.
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-022 | | | +| TP label | Control Solution Unit-Code. Use default mg/dL – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 6;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MILLI_G_PER_DL | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. Send a confirmed variable format event report using a measurement in mg/dL.
    2. 2. The simulated PHD waits until it receives a confirmation.
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data properly and applies mg/dL to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-023 | | | +| TP label | Control Solution Unit-Code. Change from default mg/dL to mmol/L – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 6;M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 9; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MILLI_G_PER_DL
    [AND]
    Continua PAN client components that receive a report of a configuration change shall apply the change to future measurements only | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 AND C_MAN_GL_002 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. Send a confirmed variable format event report to set the unit code to mmol/L MDC_DIM_MILLI_MOLE_PER_L (4722) for handle 2 (Control Solution Object) and a measurement in mmol/L.
    2. The simulated PHD waits until it receives a confirmation.
    3. Send a second confirmed variable format event report with just a measurement in mmol/L (i.e., do not transmit the unit-code attribute in the event report).
    4. The simulated PHD waits until it receives a confirmation.
    5. The simulated PHD sends an association release request (normal).
    6. The simulated PHD waits until it receives an association release response.
    7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    9. The simulated PHD sends a confirmed variable event report with an observation in mg/dL followed by date and time stamp (i.e., do not send the unit-code attribute it should be set to mg/dL by the standard configuration).
    10. The simulated PHD waits until it receives a confirmation.
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • • In steps 2 and 4, verify that the PHG under test is able to accept the data properly and applies mmol/L to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies mg/dL to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-024 | | | +| TP label | Special values. Control Solution - Not a number – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 8; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Solution Object) containing an observation value with the value for NaN ([exponent 0, mantissa $+(2^{11} - 1) = 0x07FF$ ]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-025 | | | +| TP label | Special values. Control Solution - Not a number – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 12; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Solution Object) containing an observation value set to the value for NaN ([exponent 0, mantissa +(2^{11}-1) = 0x07FF]).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-026 | | | +| TP label | Special values. Control Solution - Not at this resolution – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 8; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Solution Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{11}) = 0x0800]) and a time stamp.
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-027 | | | +| TP label | Special values. Control Solution - Not at this resolution – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 12; M | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Solution Object) containing an observation value set to the value for NRes ([exponent 0, mantissa $-(2^{11}) = 0x0800$ ]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-028 | | | +| TP label | Special values. Control Solution - Positive infinity – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 8; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Solution Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa $+(2^{11} - 2) = 0x07FE$ ]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-029 | | | +| TP label | Special values. Control Solution - Positive infinity – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 12; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Solution Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2^{11} - 2) = 0x07FE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-030 | | | +| TP label | Special values. Control Solution - Negative infinity – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 8; M | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Solution Object) containing an observation value set to the value for negative infinity (–INFINITY, [exponent 0, mantissa –(2^{11} - 2) = 0x0802]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-031 | | | +| TP label | Special values. Control Solution - Negative infinity – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 12; M | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Solution Object) containing an observation value set to the value for negative infinity (-\text{INFINITY}, [exponent 0, mantissa -(2^{11}-2) = 0x0802]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-032 | | | +| TP label | Special values. Control Solution - Reserved – fixed format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 8; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Solution Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/GL/BV-033 | | | +| TP label | Special values. Control Solution - Reserved – variable format (Std Config 1701) | | | +| Coverage | Spec | [ISO/IEEE 11073-10417] | | +| | Testable items | CtrlSol 12; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_019 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Solution Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria | Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement). | +| Notes | This test case has been considered as an implicit test case. | + +### A.4 Subgroup 2.3.3: Pulse oximeter (PO) + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-003 | | | +| TP label | Association procedure PHG PO | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | PulseAssocResp 1;M | PulseAssocResp 2;M | +| | | PulseAssocResp 6;M | PulseAssocResp 7;M | +| | | PulseAssocResp 9;M | PulseAssocResp 10;M | +| | | | PulseAssocResp 5;M | +| | | | PulseAssocResp 8;M | +| | | | PulseAssocResp 11;M | +| Test purpose |

    Check that:

    In the DataProtoList structure element, the data protocol identifier shall be set to data-proto-id-20601 (i.e., data-proto-id = 0x5079)

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = 0x80000000)

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the field functional-units shall have all bits reset except for those relating to a Test Association

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the system-id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the field dev-config-id shall be manager-config-response

    [AND]

    | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the field data-req-mode-capab-flags shall be 0

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the fields data-req-init-*-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '10000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16443
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an association response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
          • ▪ If association is rejected-permanent, field-value= 0x00 0x01.
          • ▪ If association is rejected-transient, field-value= 0x00 0x02.
          • ▪ If association is accepted-unknown-config, field-value= 0x00 0x03.
          • ▪ If association is rejected-no-common-protocol, field-value= 0x00 0x04.
          • ▪ If association is rejected-no-common-parameter, field-value= 0x00 0x05.
          • ▪ If association is rejected-unknown = 0x00 0x06.
          • ▪ If association is rejected-unauthorized, field-value= 0x00 0x07.
          • ▪ If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08.
      3. c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id))
      4. d. data-proto-id
        • field-type = DataProtoId
        • field-length = 2 bytes
        • field-value= 0x50 0x79 (20601)
    | + +- e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x80 0x00 0x00 0x00 +- f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time +- g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value= Bit 0 must be set (nom-version1) +- h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set +- i. system type + - field-type = SystemType + - field-length = 4 bytes (BITS-32) + - field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) +- j. system-id + - field-type = OCTET STRING + - field-length = 8 bytes + - field-value = (EUI-64 manufacturer and device) +- k. dev-config-id + - field-type = ConfigId + - field-length = 2 bytes + - field-value = 0x00 0x00 (manager-config-response) +- l. data-req-mode-flags (DataReqModeCapab) + - field-type = DataReqModeFlags + - field-length = 2 bytes + - field-value = 0x00 0x00 + - PHG response to data-req-mode-flags is always 0. +- m. data-req-init-agent-count (DataReqModeCapab) + - field-type = INT-U8 + - field-length = 1 byte + - field-value = 0x00 +- n. data-req-init-manager-count (DataReqModeCapab) + - field-type = INT-U8 + - field-length = 1 byte + +| | | +|---------------------------|-----------------------------------------------------------------------------------------| +| | field-value = 0x00 | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-004 | | | +| TP label | Configuration Event Report. Pulse Oximeter standard configuration 400 | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x01 0x90 (PulseOximeter).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x01 0x90.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value= it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        • field-type = HANDLE
        • field-length = 2 bytes
        • field-value = 0x00 0x00
      4. d. Event-time:
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value: 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | See http://continua.plugfest.com/show_bug.cgi?id=123 | + +| | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-005 | | +| TP label | Configuration Event Report. Pulse Oximeter standard configuration 401 | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | ConfEventRep 18;M | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | +| Other PICS | C_MAN_OXP_085 | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x01 0x91 (PulseOximeter).
    | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. The PHG under test responds with an association response, the field of interest is:

    a. Result

    • field-type = INT-U16
    • field-length = 2 bytes
    • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    If the result of the association response was "accepted-unknown-config"

    3. The simulated PHD sends a configuration event report with config-report-id set to 0x01 0x91.

    4. The PHG under test must respond with:

    b. APDU Type

    • field-length = 2 bytes
    • field-value = 0xE7 0x00 (PrstApdu)

    c. Invoke-id

    • field-type = INT-U16
    • field-length = 2 bytes
    • field-value= it must be the same as the invoke-id of the simulated PHD's message.

    d. Obj-Handle:

    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = 0x00 0x00

    e. Event-time:

    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value: 0xXX 0xXX

    f. Event-type:

    • field-length = 2 bytes
    • field-value= MDC_NOTI_CONFIG

    g. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.

    b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.

    c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    | + +| | | +|--------------|-----------------------------------------------------------------------------------------------------------------------| +| |
    • • The measurement is correctly presented.
    | +| Notes | See http://continua.plugfests.com/show_bug.cgi?id=123 | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-006 | | | +| TP label | Maximum APDU size: Pulse Oximeter | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4;M | | +| Test purpose |

    Check that:

    If a PHG receives APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 5080 
           ObservationScan ::= {   obj-handle: 1 (SPO2)   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00 (5056 bytes) 00'O     }   } } ObservationScan ::= {   obj-handle: 1 (SPO2)   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)       attribute-value: 98     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a confirmed fixed event report with one measurement.
    4. 4. Check the response of the PHG under test.
    | | | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | | | +| Notes | | | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-007 | | | +| TP label | Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | SpO2NumObjAttr 11;M | | +| Test purpose | Check that:
    For [Standard-Configuration] [Attribute-Value-Map] attribute must be present and with value MDC_ATTR_NU_VAL_OBS_BASIC | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 0x190. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (SpO2 Object) to set the values to: MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_VAL_OBS_BASIC. For handle 10 (Pulse Rate Object), set the attribute value map to: MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_VAL_OBS_BASIC
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report with the new data layout.
    4. 4. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In step 4, verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    | | | +| Notes | | | | + +| | | | | +|-----------------|------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-008 | | | +| TP label | Unit-Code. Use default % and beats per minute (BPM) – variable format observation. | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | SpO2NumObjAttr 10;M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 9; M | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    For [Standard-Configuration] [Unit-Code] value is MDC_DIM_PERCENT
    [AND]
    Continua PAN client components that receive a report of a configuration change shall apply the change to future measurements only] | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 0x190. | +| Test procedure |
    1. Send a confirmed variable format event report for handle 1 using a measurement in % and for handle 10 using a measurement in BPM.
    2. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data properly and applies % and BPM to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-009 | | | +| TP label | Supplemental-Type: SpO 2 — Standard configuration 0x191 | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | Spo2StandConf 1;C | | +| Test purpose | Check that:
    For SpO 2 numeric Object the and for Dev-Configuration-Id to 0x191 the Supplemental-Types attribute shall contain a single entry in its SupplementalTypeList, and its value shall be MDC_MODALITY_SPOT. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 0x191. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed format event report from handle 1 (SpO2 Object) that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC.
    2. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria | In step 2. Verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes and Supplemental-Type for Object with handle 1 is MDC_MODALITY_SPOT (e.g., if there is a UI, verify that the measurement and date are displayed properly). | | | +| Notes | | | | + +| | | +|-----------------|-------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-010 | +| TP label | Supplemental-Type: Pulse Rate— Standard configuration 0x191 | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | PulseRateStandConf 1;C | | | +| Test purpose | Check that:
    For Pulse Rate numeric Object the and for Dev-Configuration-Id to 0x191 the Supplemental-Types attribute shall contain a single entry in its SupplementalTypeList, and its value shall be MDC_MODALITY_SPOT. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 0x191. | | | | +| Test procedure | 1. Simulated PHD sends a confirmed fixed format event report from handle 10 (Pulse Rate Object) that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC.
    2. The simulated PHD waits until it receives a confirmation. | | | | +| Pass/Fail criteria | In step 2. Verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes and Supplemental-Type for Object with handle 10 is MDC_MODALITY_SPOT (e.g., if there is a UI, verify that the measurement and date are displayed properly). | | | | +| Notes | | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-011 | | | | +| TP label | Special values. Not a number – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 11; M | PulseRateNumObjAttr 28; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (SpO2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for NaN ([exponent 0, mantissa + $(2^{11} - 1)$ = 0x07FF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-012 | | | | +| TP label | Special values. Not a number – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 16; C | PulseRateNumObjAttr 33; C | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (SpO2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for NaN ([exponent 0, mantissa +(2**11 –1) = 0x07FF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-013 | | | | +| TP label | Special values. Not at this resolution – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 11; M | PulseRateNumObjAttr 28; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (SpO2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for NRes ([exponent 0, mantissa –(2**11) = 0x0800]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-014 | | | | +| TP label | Special values. Not at this resolution – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 16; C | PulseRateNumObjAttr 33; C | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (SpO2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2**11) = 0x0800]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-015 | | | | +| TP label | Special values. Positive infinity – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 11; M | PulseRateNumObjAttr 28; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (SpO2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 -2) = 0x07FE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-016 | | | | +| TP label | Special values. Positive infinity – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 16; C | PulseRateNumObjAttr 33; C | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (SpO2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 –2) = 0x07FE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-017 | | | | +| TP label | Special values. Negative infinity – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 11; M | PulseRateNumObjAttr 28; M | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (SpO2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for negative infinity (–INFINITY, [exponent 0, mantissa –(2**11 –2) = 0x0802]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-018 | | | | +| TP label | Special values. Negative infinity – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 16; C | PulseRateNumObjAttr 33; C | | +| Test purpose | Check that:
    The PHG receives a -INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (SpO2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for negative infinity (-INFINITY, [exponent 0, mantissa -(2**11 -2) = 0x0802]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-019 | | | | +| TP label | Special values. Reserved – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | | +| | Testable items | SpO2NumObjAttr 11; M | PulseRateNumObjAttr 28; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (SpO2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2**11 -1) = 0x0801]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------| +| TP Id | TP/PLT/PHG/CLASS/PO/BV-020 | | | +| TP label | Special values. Reserved – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10404] | | +| | Testable items | SpO2NumObjAttr 16; C | PulseRateNumObjAttr 33; C | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_026 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (SpO 2 Object) and handle 10 (Pulse Rate Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa $-(2^{11}-1) = 0x0801$ ]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +### A.5 Subgroup 2.3.4: Blood pressure monitor (BPM) + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-000 | | | +| TP label | Association procedure PHG BPM | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | ConfProc_4;M
    AsProc_16;M
    AsProc_19;M
    AsProc_22;M
    AsProc_25;M | AsProc_14;M
    AsProc_17;M
    AsProc_20;M
    AsProc_23;M | +| Test purpose | Check that:
    The PHG shall respond to a configuration notification message using a “Remote Operation Response Confirmed Event Report” data message with an MDC_NOTI_CONFIG event | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    using the ConfigReportRsp structure for the event-info field (see Table 3).

    [AND]

    In the association response message sent by the PHG:

    The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601.

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-proto-id-20601

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = 0x80000000)

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    The fields data-req-init-*-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |

    1. The simulated PHD sends an association request to the PHG under test, with the fields:

    • protocol-version = '10000000000000000000000000000000'B
    • encoding-rules= '1000000000000000'B
    • nomenclature-version = '10000000000000000000000000000000'B
    • functional-units = '00000000000000000000000000000000'B
    • system-type = '00000000100000000000000000000000'B
    • dev-config-id = 16437
    • data-rep-mode-capab =
      • ▪ data_req_mode_flags= '0000000000000001'B
    | + +- data\_req\_init\_agent\_count = 1 + - data\_req\_init\_manager\_count = 0 + - option-list.length= 0 +2. The PHG under test sends an association response. The fields of interest are: +- a. APDU Type + - field-length = 2 bytes + - field-value = 0xE3 0x00 (AareApdu) + - b. Result + - field-type = AssociateResult + - field-length = 2 bytes + - field-value = One of the following: + - If association is accepted, field-value= 0x00 0x00. + - If association is rejected-permanent, field-value= 0x00 0x01. + - If association is rejected-transient, field-value= 0x00 0x02. + - If association is accepted-unknown-config, field-value= 0x00 0x03. + - If association is rejected-no-common-protocol, field-value= 0x00 0x04. + - If association is rejected-no-common-parameter, field-value= 0x00 0x05. + - If association is rejected-unknown = 0x00 0x06. + - If association is rejected-unauthorized, field-value= 0x00 0x07. + - If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08. + - c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) + - d. data-proto-id + - field-type = DataProtoId + - field-length = 2 bytes + - field-value= 0x50 0x79 (20601) + - e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x80 0x00 0x00 0x00 + - f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time + - g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value= Bit 0 must be set (nom-version1) + - h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ Bits 1 and 2 may be set
    • ▪ The rest of the bits must not be set

    i. system type

    • field-type = SystemType
    • field-length = 4 bytes (BITS-32)
    • field-value = 0x80 0x00 0x00 0x00 (sys-type-manager)

    j. system-id

    • field-type = OCTET STRING
    • field-length = 8 bytes
    • field-value = (EUI-64 manufacturer and device)

    k. dev-config-id

    • field-type = ConfigId
    • field-length = 2 bytes
    • field-value = 0x00 0x00 (manager-config-response)

    l. data-req-mode-flags (DataReqModeCapab)

    • field-type = DataReqModeFlags
    • field-length = 2 bytes
    • field-value = 0x00 0x00
    • PHG response to data-req-mode-flags is always 0.

    m. data-req-init-agent-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00

    n. data-req-init-manager-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-001 | | | +| TP label | Configuration Event Report. Blood Pressure Meter standard configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | MDSEvents 8;M | | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose | Check that:
    A blood pressure monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response. | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | +| Other PICS | C_MAN_OXP_085 | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x02 0xBC (Blood Pressure Meter).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x02 0xBC
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value= it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value: 0xXX 0xXX
      5. e. Event-type:
        1. field-length = 2 bytes
        2. field-value= MDC_NOTI_CONFIG
      6. f. The following six bytes indicate:
        1. Event-replay-info.length (2 bytes)
        2. ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ❑ ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement with:

    • ❑ event_type = MDC_NOTI_SCAN_REPORT_FIXED
    • ❑ event_info = ScanReportInfoFixed
      • ▪ obs_scan_fixed: Sys-Diast-MAP 120-90-100 mmHg and pulse rate 60 BPM
    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | See bug http://continua.plugfest.com/show_bug.cgi?id=123 | + +| | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-003 | | +| TP label | Attribute-Value-Map. Order change. | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | +| | Testable items | SystDiast_23;M | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present. The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_CMPD_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_ABS

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report with a report from handle 1 (Non-invasive blood pressure) that matches the Attribute-Value-Map order of MDC_ATTR_NU_CMPD_VAL_OBS_BASIC, MDC_ATTR_TIME_STAMP_ABS and handle 2 (pulse) that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_TIME_STAMP_ABS
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 to reverse the values to: MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_CMPD_VAL_OBS_BASIC and to reverse handle 2 values to: MDC_ATTR_TIME_STAMP_ABS, MDC_ATTR_NU_VAL_OBS_BASIC.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with handle 1 values set to the date first
    | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    followed by blood pressure values (in millimetres of mercury (MDC_DIM_MMHG) since it is the standard configuration unit code) and handle 2 values set to the date first followed by pulse rate (in beats per minute (MDC_DIM_BEAT_PER_MIN)).

    1. 6. The simulated PHD waits until it receives a confirmation.
    2. 7. The simulated PHD sends an association release request (normal).
    3. 8. The simulated PHD waits until there is an association release response.
    4. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    5. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    6. 11. The simulated PHD sends a fixed event report for handles 1 and 2 following the standard configuration attribute-value-format (MDC_ATTR_NU_CMPD_VAL_OBS_BASIC, MDC_ATTR_TIME_STAMP_ABS) and (MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_TIME_STAMP_ABS), respectively.
    7. 12. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly). If the PHG only displays the values from handle 1 (non-invasive blood pressure) that is fine since the specification implies that PHD s nor PHG have to support (pulse) but the pulse object must be there in the standard configuration.
    • • In steps 2, 6 and 12 verify that the PHG under test uses millimetres of mercury as the unit code for the measurement report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    | +| Notes |
    • • This may require the simulated PHD to provide a proper date-and-time attribute in the MDS object.
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-004 | | | +| TP label | Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_23;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present. The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_CMPD_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_ABS

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 AND C_MAN_BPM_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | configuration. (Non-invasive blood pressure Compound Numeric standard configuration Unit code attribute is set to millimetres of mercury (MDC_DIM_MMHG)). | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Non-invasive blood pressure) to set the values to: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_ABS. For handle 2 (pulse), set the attribute value map to: MDC_ATTR_MSMT_STAT, MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_ABS.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute of handle 1, use MDC_DIM_KILO_PASCAL (3843), for handle 2, use MDC_DIM_BEAT_PER_MIN (2720).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends a confirmed variable event report with handle 1 reporting just a MDC_ATTR_NU_CMPD_VAL_OBS_BASIC attribute and handle 2 just a MDC_ATTR_NU_VAL_OBS_BASIC.
    6. 6. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement is displayed properly).
    • • In steps 4 and 6, verify that the PHG under test uses kilopascals and beats per minute as the unit codes for the measurement reports.
    | +| Notes | | + +| | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-005 | | +| TP label | Unit-Code. Change from default millimetres of mercury (mmHg) to kilopascals (kPa) – fixed format observation. | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | +| | Testable items | SystDiast_21;M | +| | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | Communication 9; M | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MMHG
    [AND]
    Continua PAN client components that receive a report of a configuration change shall apply the change to future measurements only | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 AND C_MAN_BPM_001 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (non-invasive blood pressure) to kPa nomenclature code MDC_DIM_KILO_PASCAL (3843).
      NOTE – No need to change handle 2 (pulse), since the only option is beats/minute.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report for handle 1 using a measurement in kPa (e.g., 16 kPa is 120 mmHg and 10 kPa is 80 mmHg) followed by date and time stamp and for handle 2 using a measurement in beats per minute followed by date and time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends an association release request (normal).
    6. 6. The simulated PHD waits until it receives an association release response.
    7. 7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. 8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    9. 9. The simulated PHD sends a fixed event report for handle 1 using a measurement in mmHg followed by date and time stamp and for handle 2 using a measurement in beats per minute followed by date and time stamp.
    10. 10. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies kPa and BPM to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies mmHg and BPM to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-005_A | | | +| TP label | Unit-Code. Do not change from default millimetres of mercury (mmHg) to kilopascals (kPa) – fixed format observation. | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_21;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MMHG | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 AND (NOT(C_MAN_BPM_001)) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (non-invasive blood pressure) to kPa nomenclature code
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    MDC_DIM_KILO_PASCAL (3843).
    NOTE – No need to change handle 2 (pulse), since the only option is beats/minute.

    1. 2. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or until TO cer-mds expires.
    2. 3. If the PHG has sent a confirmation in step 2, send a confirmed fixed format event report for handle 1 using a measurement in kPa (e.g., 16 kPa is 120 mmHg and 10 kPa is 80 mmHg) followed by date and time stamp and for handle 2 using a measurement in beats per minute followed by date and time stamp.
    3. 4. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or TO cer-mds expires.
    4. 5. If the PHG has sent a confirmation in step 4, ask to the operator if the measurements have been properly received and displayed.
    | +| Pass/Fail criteria |
    • • In step 2, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • • In step 4, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • • In step 5, verify that measurements do not appear, or if they do appear, they are somehow designated as 'unsupported' data.
    | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-006 | | | +| TP label | Unit-Code. Use default millimetres of mercury (mmHg) and beats per minute (BPM) – variable format observation. | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_21;M | | +| Test purpose |

    Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MMHG

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. Send a confirmed variable format event report for handle 1 using a measurement in mmHg and for handle 2 using a measurement in BPM.
    2. 2. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data properly and applies mmHg and BPM to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | +| Notes | | | | + +| | | +|-----------------|------------------------------------------------------------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-007 | +| TP label | Unit-Code. Change from default millimetres of mercury (mmHg) to kilopascals (kPa) – variable format observation. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_21;M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 9; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Unit-Code] attribute shall be present

    The value of the [Unit-Code] attribute shall be MDC_DIM_MMHG

    [AND]

    Continua PAN client components that receive a report of a configuration change shall apply the change to future measurements only

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 AND C_MAN_BPM_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. Send a confirmed variable format event report to set the unit code to kPa MDC_DIM_KILO_PASCAL (3843) for handle 1 (non-invasive blood pressure) and a measurement in kPa. For handle 2, set the unit code to beats per minute MDC_DIM_BEAT_PER_MIN (2720) and a BPM measurement value.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a second confirmed variable format event report with just a measurement in kPa and beats/min (i.e., do not transmit the unit-code attribute in the event report).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends an association release request (normal).
    6. 6. The simulated PHD waits until it receives an association release response.
    7. 7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. 8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    9. 9. The simulated PHD sends a confirmed variable event report for handle 1 with an observation in mmHg (i.e., do not send the unit-code attribute it should be set to mmHg by the standard configuration). For handle 2, use an observation of BPM.
    10. 10. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • • In steps 2 and 4, verify that the PHG under test is able to accept the data properly and applies kPa and BPM to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies mmHg and BPM to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | +| Notes | | | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-008 | | | +| TP label | Metric-id-list. Standard configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_17;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Metric-Id-List] attribute shall be present. The value of the [Metric-Id-List] attribute shall be MDC_PRESS_BLD_NONINV_SYS, MDC_PRESS_BLD_NONINV_DIA, then MDC_PRESS_BLD_NONINV_MEAN.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (non-invasive blood pressure object) containing an observation with the compound field values (SFLOAT) set to (120.0, 80.0, 93.3) and for handle 2 containing an observation (SFLOAT) of 60.0.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data and applies the data properly as systolic = 120.0, diastolic = 80.0, mean arterial pressure (MAP) = 93.3, and pulse = 60.0.
    | | | +| Notes | If there are no other tests for various different FLOAT and SFLOAT values, the values above at least help cover the negative exponent values (e.g., 120.0 is 0xF4B0 as the SFLOAT). | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-009 | | | +| TP label | Metric-id-list. Id order change – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_17;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Metric-Id-List] attribute shall be present. The value of the [Metric-Id-List] attribute shall be MDC_PRESS_BLD_NONINV_SYS, MDC_PRESS_BLD_NONINV_DIA, then MDC_PRESS_BLD_NONINV_MEAN.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (non-invasive blood pressure object) setting MDC_ATTR_ID_PHYSIO_LIST to (MDC_PRESS_BLD_NONINV_MEAN, MDC_PRESS_BLD_NONINV_SYS, then MDC_PRESS_BLD_NONINV_DIA).
    2. The simulated PHD sends a confirmed fixed event report for handle 1 containing an observation with the compound field values (SFLOAT) set to (106.6, 140.0, 90.0) along with a known time stamp, and Pulse Rate of 60 BPM along with a known time stamp.
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 3. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data and time stamp and applies the data properly as systolic = 140.0, diastolic = 90.0, MAP = 106.6.
    | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-010 | | | +| TP label | Metric-id-list. Id order change – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_17;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Metric-Id-List] attribute shall be present. The value of the [Metric-Id-List] attribute shall be MDC_PRESS_BLD_NONINV_SYS, MDC_PRESS_BLD_NONINV_DIA, then MDC_PRESS_BLD_NONINV_MEAN. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (non-invasive blood pressure object) setting MDC_ATTR_ID_PHYSIO_LIST to (MDC_PRESS_BLD_NONINV_DIA, MDC_PRESS_BLD_NONINV_MEAN, then MDC_PRESS_BLD_NONINV_SYS) in the first observation scan. In a second observation scan, for handle 1 set the compound field values (SFLOAT) to (74.0, 86.0, 110.0) along with a known time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data and time stamp and applies the data properly as systolic = 110.0, diastolic = 74.0, MAP = 86.0.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-011 | | | +| TP label | Metric-id-list. Reduced ids – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_17;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Metric-Id-List] attribute shall be present. The value of the [Metric-Id-List] attribute shall be MDC_PRESS_BLD_NONINV_SYS, MDC_PRESS_BLD_NONINV_DIA, then MDC_PRESS_BLD_NONINV_MEAN. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (non-invasive blood pressure object) setting MDC_ATTR_METRIC_STRUCT_SMALL to {ms-struct-compound-fix, 2}, MDC_ATTR_ID_PHYSIO_LIST to (MDC_PRESS_BLD_NONINV_SYS, then MDC_PRESS_BLD_NONINV_DIA) and MDC_ATTR_ATTRIBUTE_VAL_MAP to {MDC_ATTR_NU_CMPD_VAL_OBS_BASIC, 8, MDC_ATTR_TIME_STAMP_ABS, 8}.
    2. 2. The simulated PHD sends a confirmed fixed event report for handle 1 containing an observation with the compound field values (SFLOAT) set to (135.5, 86.3) along with a known time stamp.
    3. 3. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data and time stamp and applies the data properly as systolic = 135.5, diastolic = 86.3.
    | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-012 | | | +| TP label | Metric-id-list. Reduced ids – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_17;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Metric-Id-List] attribute shall be present. The value of the [Metric-Id-List] attribute shall be MDC_PRESS_BLD_NONINV_SYS, MDC_PRESS_BLD_NONINV_DIA, then MDC_PRESS_BLD_NONINV_MEAN. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (non-invasive blood pressure object) setting MDC_ATTR_METRIC_STRUCT_SMALL to {ms-struct-compound-fix, 2} and MDC_ATTR_ID_PHYSIO_LIST to (MDC_PRESS_BLD_NONINV_DIA, then MDC_PRESS_BLD_NONINV_SYS).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    3. 3. The simulated PHD sends a confirmed variable event report for handle 1 containing an observation with the compound field values (SFLOAT) set to (150.0, 95.0) along with a known time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data and time stamp and applies the data properly as systolic = 150.0, diastolic = 95.0.
    | | | +| Notes | | | | + +| | | | | +|-----------------|-----------------------------------------|------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-013 | | | +| TP label | Maximum APDU size: Blood Pressure Meter | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] | | + +| | | | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--|--|--|--| +| | Testable items | CommonCharac 4;M | | | | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | | | | +| Other PICS | | | | | | | +| Initial condition | The PHG under test is in the Operating state. | | | | | | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 856 
          ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(824 bytes)..... 00'O     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2677 (MDC_ATTR_NU_CMPD_VAL_OBS_BASIC)       attribute-value: (130 / 85 / 100)     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a confirmed fixed event report with one measurement.
    4. 4. Check the response of the PHG under test.
    | | | | | | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | | | | | | +| Notes | | | | | | | + +| | | | | | +|-----------------|-----------------------|---------------------------------------------|---------------|--| +| TP Id | | TP/PLT/PHG/CLASS/BPM/BV-014 | | | +| TP label | | Special values. Not a number – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | +| | Testable items | SystDiast_23; M | PulsRat_22; M | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate Object) containing all observation values set to the value for NaN ([exponent 0, mantissa +(2**11 –1) = 0x07FF]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-015 | | | +| TP label | Special values. Not a number – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_45; C | PulsRat_42; M | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate Object) containing all observation values set to the value for NaN ([exponent 0, mantissa +(2**11 –1) = 0x07FF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|-----------------|-------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-016 | | | +| TP label | Special values. Not at this resolution – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|--| +| | Testable items | SystDiast_23; M | PulsRat_22; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate) containing all observation values set to the value for NRes ([exponent 0, mantissa -(2^{**}11) = 0x0800]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-017 | | | | +| TP label | Special values. Not at this resolution – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | +| | Testable items | SystDiast_45; C | PulsRat_42; M | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate Object) containing all observation values set to the value for NRes ([exponent 0, mantissa -(2^{**}11) = 0x0800]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|-----------------|--------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-018 | | | | +| TP label | Special values. Positive infinity – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|--| +| | Testable items | SystDiast_23; M | PulsRat_22; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate Object) containing all observation values set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 -2) = 0x07FE]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-019 | | | | +| TP label | Special values. Positive infinity – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | +| | Testable items | SystDiast_45; C | PulsRat_42; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate Object) containing all observation values set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 -2) = 0x07FE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-020 | | | +| TP label | Special values. Negative infinity – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_23; M | PulsRat_22; M | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate Object) containing all observation values set to the value for negative infinity (–INFINITY, [exponent 0, mantissa -(2^{11}-2) = 0x0802]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-021 | | | +| TP label | Special values. Negative infinity – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | +| | Testable items | SystDiast_45; C | PulsRat_42; M | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate) containing all observation values set to the value for negative infinity (–INFINITY, [exponent 0, mantissa -(2^{11}-2) = 0x0802]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-022 | | | | +| TP label | Special values. Reserved – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | +| | Testable items | SystDiast_23; M | PulsRat_22; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate) containing all observation values set to the value for reserved (Reserved for future use, [exponent 0, mantissa $-(2^{11} - 1) = 0x0801$ ]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|--| +| TP Id | TP/PLT/PHG/CLASS/BPM/BV-023 | | | | +| TP label | Special values. Reserved – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10407] | | | +| | Testable items | SystDiast_45; C | PulsRat_42; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_020 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (Systolic/Diastolic/MAP Object) and handle 2 (Pulse Rate Object) containing all observation values set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +### A.6 Subgroup 2.3.5: Thermometer (TH) + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-003 | | | +| TP label | Association procedure PHG TH | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | TH_CM_Assoc10 ;M | TH_CM_Assoc14 ;M | +| | | TH_CM_Assoc16 ;M | TH_CM_Assoc17 ;M | +| | | TH_CM_Assoc19 ;M | TH_CM_Assoc20 ;M | +| Test purpose |

    Check that:

    The PHG may use this field to determine the identity of the thermometer with which it is associating and, optionally, to implement a simple access restriction policy

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = 0x80000000)

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The fields data-req-mode-capab, data-req-init-agent, data-req-init-manager-count shall be 0. If the PHD supports only the thermometer specialization data-req-init-agent-count shall be 1.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The PHG is in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
    | | | + +- protocol-version = '10000000000000000000000000000000'B +- encoding-rules= '1000000000000000'B +- nomenclature-version = '10000000000000000000000000000000'B +- functional-units = '00000000000000000000000000000000'B +- system-type = '00000000100000000000000000000000'B +- dev-config-id = 16447 +- data-rep-mode-capab = + - data\_req\_mode\_flags= '0000000000000001'B + - data\_req\_init\_agent\_count = 1 + - data\_req\_init\_manager\_count = 0 +- option-list.length= 0 + +2. The PHG under test sends an association response. The fields of interest are: + +- a. APDU Type + - field-length = 2 bytes + - field-value = 0xE3 0x00 (AareApdu) +- b. Result + - field-type = AssociateResult + - field-length = 2 bytes + - field-value = One of the following: + - If association is accepted, field-value= 0x00 0x00. + - If association is rejected-permanent, field-value= 0x00 0x01. + - If association is rejected-transient, field-value= 0x00 0x02. + - If association is accepted-unknown-config, field-value= 0x00 0x03. + - If association is rejected-no-common-protocol, field-value= 0x00 0x04. + - If association is rejected-no-common-parameter, field-value= 0x00 0x05. + - If association is rejected-unknown = 0x00 0x06. + - If association is rejected-unauthorized, field-value= 0x00 0x07. + - If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08. +- c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) +- d. data-proto-id + - field-type = DataProtoId + - field-length = 2 bytes + - field-value= 0x50 0x79 (20601) +- e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x80 0x00 0x00 0x00 +- f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time +- g. nomenclature version + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-type = NomenclatureVersion
    • field-length = 4 bytes (BITS-32)
    • field-value= Bit 0 must be set (nom-version1)

    h. functional units

    • field-type = FunctionalUnits
    • field-length = 4 bytes (BITS-32)
    • field-value =
      • ▪ Bit 0 must be 0
      • ▪ Bits 1 and 2 may be set
      • ▪ The rest of the bits must not be set

    i. system type

    • field-type = SystemType
    • field-length = 4 bytes (BITS-32)
    • field-value = 0x80 0x00 0x00 0x00 (sys-type-manager)

    j. system-id

    • field-type = OCTET STRING
    • field-length = 8 bytes
    • field-value = (EUI-64 manufacturer and device)

    k. dev-config-id

    • field-type = ConfigId
    • field-length = 2 bytes
    • field-value = 0x00 0x00 (manager-config-response)

    l. data-req-mode-flags (DataReqModeCapab)

    • field-type = DataReqModeFlags
    • field-length = 2 bytes
    • field-value = 0x00 0x00
    • PHG response to data-req-mode-flags is always 0.

    m. data-req-init-agent-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00

    n. data-req-init-manager-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +| | | | +|-----------------|----------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-004 | | +| TP label | Configuration Event Report. Thermometer standard configuration | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--|--| +| | Testable items | ConfEventRep 18;M | | | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | | +| Other PICS | C_MAN_OXP_085 | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x03 0x20 (Thermometer).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x03 0x20.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value= it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value: 0xXX 0xXX
      5. e. Event-type:
        1. field-length = 2 bytes
        2. field-value= MDC_NOTI_CONFIG
      6. f. The following six bytes indicate:
        1. Event-replay-info.length (2 bytes)
        2. ConfigReportRsp.config-report-id: it must be the same as config-report-id of the
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    simulated PHD's message

    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-005 | | | +| TP label | Maximum APDU size: Thermometer | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] | | +| | Testable items | CommonCharac 4;M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next one apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar.obs_scan_var:
        • Count = 2
        • Length = 856 
           ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(832 bytes)..... 00'0     }   } } ObservationScan ::= {   obj-handle: 1
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 
     attributes: AttributeList ::= {     AVA-Type ::= {         attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)         attribute-value: 36     } }
    | +| |
    1. 2. Check the response of the PHG under test.
    2. 3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    3. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-006 | | +| TP label | Attribute-Value-Map. Order change. | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | +| | Testable items | Num Objec Temp17;M | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_ABS

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_ABS.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Body Temperature Object) to reverse the values to: MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_VAL_OBS_BASIC.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date first followed by a body temperature value (in Celsius degrees since it is the standard configuration unit code).
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard
    | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    configuration.

    • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.

    11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_ABS). The observation should be a reasonable Celsius degrees body temperature observation.

    12. The simulated PHD waits until it receives a confirmation.

    | +| Pass/Fail criteria |
    • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • In steps 2, 6 and 12 verify that the PHG under test uses Celsius degrees as the unit code for the measurement report (or reports the proper value after conversion to another unit code).
    • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-007 | | | +| TP label | Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp17;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_ABS

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 AND C_MAN_TH_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. (Body Temperature Numeric standard configuration Unit code attribute is set to MDC_DIM_DEGC). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Body Temperature Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_ABS.
    2. The simulated PHD waits until it receives a confirmation.
    3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute, use MDC_DIM_FAHR (4416).
    4. The simulated PHD waits until it receives a confirmation.
    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC attribute.
    6. The simulated PHD waits until it receives a confirmation.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement is displayed properly).
    • In steps 4 and 6, verify that the PHG under test uses Fahrenheit degrees as the unit code for the measurement reports.
    | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-008 | | | +| TP label | Unit-Code. Change from default Celsius degrees to Fahrenheit degrees – fixed format observation. | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp15;M | | +| | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Communication 9; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Unit-Code] attribute shall be present

    The value of the [Unit-Code] attribute shall be MDC_DIM_DEGC

    [AND]

    Continua PAN client components that receive a report of a configuration change shall apply the change to future measurements only

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 AND C_MAN_TH_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (Body Temperature Object) to Fahrenheit nomenclature code MDC_DIM_FAHR (4416).
    2. The simulated PHD waits until it receives a confirmation.
    3. Send a confirmed fixed format event report using a measurement in Fahrenheit degrees followed by date and time stamp.
    4. The simulated PHD waits until it receives a confirmation.
    5. The simulated PHD sends an association release request (normal).
    6. The simulated PHD waits until it receives an association release response.
    7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • The simulated PHD waits until it receives a confirmation from the confirmed
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | configuration event report just sent.
    9. The simulated PHD sends a fixed event report with an observation in Celsius degrees followed by date and time stamp.
    10. The simulated PHD waits until it receives a confirmation. | +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies Fahrenheit degrees to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • In step 10, verify that the PHG under test is able to accept the data properly and applies Celsius degrees to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-008_A | | | +| TP label | Unit-Code. Do not change from default Celsius degrees to Fahrenheit degrees – fixed format observation. | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp15;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_DEGC | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 AND (NOT(C_MAN_TH_001)) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (Body Temperature Object) to Fahrenheit nomenclature code MDC_DIM_FAHR (4416).
    2. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or until TO cer-mds expires.
    3. If the PHG has sent a confirmation in step 2, send a confirmed fixed format event report using a measurement in Fahrenheit degrees followed by date and time stamp.
    4. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or TO cer-mds expires.
    5. If the PHG has sent a confirmation in step 4, ask to the operator if the measurements have been properly received and displayed.
    | | | +| Pass/Fail criteria |
    • In step 2, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • In step 4, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • In step 5, verify that measurements do not appear, or if they do appear, they are somehow designated as 'unsupported' data.
    | | | +| Notes | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-009 | | | | +| TP label | Unit-Code. Use default Celsius degrees – variable format observation. | | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | | +| | Testable items | Num Objec Temp15;M | Communication 9; M | | +| | | | | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_DEGC | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure | 1. Send a confirmed variable format event report using a measurement in Celsius degrees.
    2. The simulated PHD waits until it receives a confirmation. | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data properly and applies Celsius degrees to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-010 | | | | +| TP label | Unit-Code. Change from default Celsius degrees to Fahrenheit degrees – variable format observation. | | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | | +| | Testable items | Num Objec Temp15;M | | | +| | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Communication 9; M | | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_DEGC
    [AND]
    Continua PAN client components that receive a report of a configuration change shall apply the change to future measurements only | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 AND C_MAN_TH_001 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Send a confirmed variable format event report to set the unit code to Fahrenheit degrees MDC_DIM_FAHR (4416) for handle 1 (Body Temperature Object) and a measurement in Fahrenheit degrees.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a second confirmed variable format event report with just a measurement in Fahrenheit degrees (i.e., do not transmit the unit-code attribute in the event report).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends an association release request (normal).
    6. 6. The simulated PHD waits until it receives an association release response.
    7. 7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. 8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    9. 9. The simulated PHD sends a confirmed variable event report with an observation in Celsius degrees followed by date and time stamp (i.e., do not send the unit-code attribute it should be set to Celsius degrees by the standard configuration).
    10. 10. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2 and 4, verify that the PHG under test is able to accept the data properly and applies Fahrenheit degrees to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies Celsius degrees to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-011 | | | +| TP label | Special values. Not a number – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp17; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Temperature Object) containing an observation value with the value for NaN ([exponent 0, mantissa +(2**11 -1) = 0x07FF]) and a time stamp.
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as
    | | | + +| | | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-012 | | | +| TP label | Special values. Not a number – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp21; C | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Temperature Object) containing an observation value set to the value for NaN ([exponent 0, mantissa +(2^{11} - 1) = 0x07FF]).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-013 | | | +| TP label | Special values. Not at this resolution – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp17; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Temperature Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{11}) = 0x0800]) and a time stamp.
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-014 | | | +| TP label | Special values. Not at this resolution – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp21; C | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Temperature Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{11}) = 0x0800]).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ TH /BV-015 | | | +| TP label | Special values. Positive infinity – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp17; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Temperature Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2^{11} - 2) = 0x07FE]) and a time stamp.
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-016 | | | +| TP label | Special values. Positive infinity – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp21; C | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Temperature Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2^{11} - 2) = 0x07FE]).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-017 | | | +| TP label | Special values. Negative infinity – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp17; M | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | configuration. | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Temperature Object) containing an observation value set to the value for negative infinity (-\text{INFINITY}, [exponent 0, mantissa -(2^{11}-2) = 0x0802]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-018 | | | +| TP label | Special values. Negative infinity – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp21; C | | +| Test Purpose | Check that:

    The PHG receives a $-\text{INFINITY}$ value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Temperature Object) containing an observation value set to the value for negative infinity (-\text{INFINITY}, [exponent 0, mantissa -(2^{11}-2) = 0x0802]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-019 | | | +| TP label | Special values. Reserved – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp17; M | | +| Test purpose | Check that:

    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Temperature Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa $-(2^{11} - 1) = 0x0801$ ]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria | • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/TH/BV-020 | | | +| TP label | Special values. Reserved – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10408] | | +| | Testable items | Num Objec Temp21; C | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_025 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Temperature Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa $-(2^{11} - 1) = 0x0801$ ]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria | • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement). | | | +| Notes | This test case has been considered as an implicit test case. | | | + +### A.7 Subgroup 2.3.6: Cardiovascular (CV) + +| | | | | | +|-----------------|------------------------------|------------------------|---------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/CV/BV-002 | | | | +| TP label | Association procedure PHG CV | | | | +| Coverage | Spec | [ISO/IEEE 11073-10441] | | | +| | Testable items | AssocResp1;M | AssocResp2;M | AssocResp3;M | +| | | AssocResp4;M | AssocResp5;M | AssocResp6;M | +| | | AssocResp7;M | AssocResp8;M | AssocResp9;M | +| | | AssocResp10;M | AssocResp11;M | AssocResp12;M | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    In the association response message sent by the PHG:

    The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601.

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-proto-id-20601

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = 0x80000000)

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    The fields data-req-init-*-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND (C_MAN_OXP_023) | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '10000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16438
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
    | + +- data\_req\_init\_manager\_count = 0 + - option-list.length= 0 +2. The PHG under test sends an association response. The fields of interest are: +- a. APDU Type + - field-length = 2 bytes + - field-value = 0xE3 0x00 (AareApdu) + - b. Result + - field-type = AssociateResult + - field-length = 2 bytes + - field-value = One of the following: + - If association is accepted, field-value= 0x00 0x00. + - If association is rejected-permanent, field-value= 0x00 0x01. + - If association is rejected-transient, field-value= 0x00 0x02. + - If association is accepted-unknown-config, field-value= 0x00 0x03. + - If association is rejected-no-common-protocol, field-value= 0x00 0x04. + - If association is rejected-no-common-parameter, field-value= 0x00 0x05. + - If association is rejected-unknown = 0x00 0x06. + - If association is rejected-unauthorized, field-value= 0x00 0x07. + - If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08. + - c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) + - d. data-proto-id + - field-type = DataProtoId + - field-length = 2 bytes + - field-value= 0x50 0x79 (20601) + - e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x80 0x00 0x00 0x00 + - f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time + - g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value= Bit 0 must be set (nom-version1) + - h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ The rest of the bits must not be set
    • i. system type
      • field-type = SystemType
      • field-length = 4 bytes (BITS-32)
      • field-value = 0x80 0x00 0x00 0x00 (sys-type-manager)
    • j. system-id
      • field-type = OCTET STRING
      • field-length = 8 bytes
      • field-value = (EUI-64 manufacturer and device)
    • k. dev-config-id
      • field-type = ConfigId
      • field-length = 2 bytes
      • field-value = 0x00 0x00 (manager-config-response)
    • l. data-req-mode-flags (DataReqModeCapab)
      • field-type = DataReqModeFlags
      • field-length = 2 bytes
      • field-value = 0x00 0x00
      • PHG response to data-req-mode-flags is always 0.
    • m. data-req-init-agent-count (DataReqModeCapab)
      • field-type = INT-U8
      • field-length = 1 byte
      • field-value = 0x00
    • n. data-req-init-manager-count (DataReqModeCapab)
      • field-type = INT-U8
      • field-length = 1 byte
      • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CV/BV-003 | | | +| TP label | Maximum APDU size: Cardiovascular | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4;M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_023 AND NOT(C_MAN_CV_030) | | | +| Other PICS | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test is in the Operating state. | +| Test procedure | 1. The simulated PHD sends a Confirmed variable event report:
    1. a. ScanReportInfoVar. obs_scan_var:
      • Count = 2
      • Length = 64472
       ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(64448 bytes)..... 00'O     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2633 (MDC_ATTR_ENUM_OBS_VAL_SIMP_OID)       attribute-value: 1017 (MDC_HF_ACT_WALK)     }   } }
    2. Check the response of the PHG under test.
    3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    4. Check the response of the PHG under test. | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +### A.8 Subgroup 2.3.7: Strength (ST) + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------| +| TP Id | TP/PLT/PHG/CLASS/ST/BV-001 | | | +| TP label | Association procedure PHG ST | | | +| Coverage | Spec | [ISO/IEEE 11073-10442] | | +| | Testable items | StrenAssocRes 1;M | StrenAssocRes 2;M | +| | | StrenAssocRes 4;M | StrenAssocRes 5;M | +| | | StrenAssocRes 7;M | StrenAssocRes 8;M | +| | | StrenAssocRes 10;M | StrenAssocRes 11;M | +| Test purpose | Check that:

    In the DataProtoList structure element, the data protocol identifier shall be set to data-proto-id-20601 (i.e., data-proto-id = 0x5079)
    [AND]
    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    0x80000000).

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG.

    [AND]

    The PHG shall support at least the MDER encoding rules.

    [AND]

    The version of the nomenclature used shall be set to nom-version1

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure which shall contain the field functional-units. It shall have all bits reset except for those relating to a Test Association.

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure which shall contain the field system-type. It shall be set to sys-type-manager (i.e., system-type = 0x80000000).

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure which contain the System-Id field. It shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier.

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure which shall contain the following parameter values: The field dev-config-id shall be manager-config-response (0).

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and the contain the field data-req-mode-capab. data-req-mode-capab Shall be 0.

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure and shall contain the fields data-req-init-* count = 0

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_022 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '10000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16445
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an association response. The fields of interest are:
      1. a. APDU Type
    | + +- field-length = 2 bytes +- field-value = 0xE3 0x00 (AareApdu) + +#### b. Result + +- field-type = AssociateResult +- field-length = 2 bytes +- field-value = One of the following: + - If association is accepted, field-value= 0x00 0x00. + - If association is rejected-permanent, field-value= 0x00 0x01. + - If association is rejected-transient, field-value= 0x00 0x02. + - If association is accepted-unknown-config, field-value= 0x00 0x03. + - If association is rejected-no-common-protocol, field-value= 0x00 0x04. + - If association is rejected-no-common-parameter, field-value= 0x00 0x05. + - If association is rejected-unknown = 0x00 0x06. + - If association is rejected-unauthorized, field-value= 0x00 0x07. + - If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08. + +#### c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) + +#### d. data-proto-id + +- field-type = DataProtoId +- field-length = 2 bytes +- field-value= 0x50 0x79 (20601) + +#### e. protocol-version + +- field-type = Protocol Version +- field-length = 4 bytes (BITS-32) +- field-value= 0x80 0x00 0x00 0x00 + +#### f. encoding-rules + +- field-type = EncodingRules +- field-length = 2 bytes (BITS-16) +- field-value= depends on the encoding rules supported/selected, but only one can be supported at a time + +#### g. nomenclature version + +- field-type = NomenclatureVersion +- field-length = 4 bytes (BITS-32) +- field-value= Bit 0 must be set (nom-version1) + +#### h. functional units + +- field-type = FunctionalUnits +- field-length = 4 bytes (BITS-32) +- field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set + +#### i. system type + +- field-type = SystemType +- field-length = 4 bytes (BITS-32) + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-value = 0x80 0x00 0x00 0x00 (sys-type-manager)
    • j. system-id
      • field-type = OCTET STRING
      • field-length = 8 bytes
      • field-value = (EUI-64 manufacturer and device)
    • k. dev-config-id
      • field-type = ConfigId
      • field-length = 2 bytes
      • field-value = 0x00 0x00 (manager-config-response)
    • l. data-req-mode-flags (DataReqModeCapab)
      • field-type = DataReqModeFlags
      • field-length = 2 bytes
      • field-value = 0x00 0x00
      • PHG response to data-req-mode-flags is always 0.
    • m. data-req-init-agent-count (DataReqModeCapab)
      • field-type = INT-U8
      • field-length = 1 byte
      • field-value = 0x00
    • n. data-req-init-manager-count (DataReqModeCapab)
      • field-type = INT-U8
      • field-length = 1 byte
      • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ST/BV-002 | | | +| TP label | Maximum APDU size: Strength | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4;M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_022 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure | 1. The simulated PHD sends a Confirmed variable event report: | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. ScanReportInfoVar.obs_scan_var:

    • Count = 2
    • Length = 64472
     ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(64448 bytes).....'     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2633 (MDC_ATTR_ENUM_OBS_VAL_SIMP_OID)       attribute-value: 284 (MDC_MUSC_HEAD_FACIAL)     }   } }
    1. 2. Check the response of the PHG under test.
    2. 3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    3. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +### A.9 Subgroup 2.3.8: Activity hub (HUB) + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/HUB/BV-003 | | | +| TP label | Association procedure PHG HUB | | | +| Coverage | Spec | [ISO/IEEE 11073-10471] | | +| | Testable items | AssocResp1;M | AssocResp2;M | +| | | AssocResp4;M | AssocResp5;M | +| | | AssocResp7;M | AssocResp8;M | +| | | AssocResp10;M | AssocResp11;M | +| Test purpose |

    Check that:

    In the DataProtoList structure element, the data protocol identifier shall be set to data-protocol-id-20601

    [AND]

    The data-protocol-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = 0x80000000)

    | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    The fields data-req-init-*-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND (C_MAN_OXP_021) | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '10000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16441
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an association response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
    | + +- If association is rejected-permanent, field-value= 0x00 0x01. +- If association is rejected-transient, field-value= 0x00 0x02. +- If association is accepted-unknown-config, field-value= 0x00 0x03. +- If association is rejected-no-common-protocol, field-value= 0x00 0x04. +- If association is rejected-no-common-parameter, field-value= 0x00 0x05. +- If association is rejected-unknown = 0x00 0x06. +- If association is rejected-unauthorized, field-value= 0x00 0x07. +- If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08. + +c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) + +d. data-proto-id + +- field-type = DataProtoId +- field-length = 2 bytes +- field-value= 0x50 0x79 (20601) + +e. protocol-version + +- field-type = Protocol Version +- field-length = 4 bytes (BITS-32) +- field-value= 0x80 0x00 0x00 0x00 + +f. encoding-rules + +- field-type = EncodingRules +- field-length = 2 bytes (BITS-16) +- field-value= depends on the encoding rules supported/selected, but only one can be supported at a time + +g. nomenclature version + +- field-type = NomenclatureVersion +- field-length = 4 bytes (BITS-32) +- field-value= Bit 0 must be set (nom-version1) + +h. functional units + +- field-type = FunctionalUnits +- field-length = 4 bytes (BITS-32) +- field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set + +i. system type + +- field-type = SystemType +- field-length = 4 bytes (BITS-32) +- field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) + +j. system-id + +- field-type = OCTET STRING +- field-length = 8 bytes +- field-value = (EUI-64 manufacturer and device) + +k. dev-config-id + +- field-type = ConfigId + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 2 bytes
    • field-value = 0x00 0x00 (manager-config-response)
    • l. data-req-mode-flags (DataReqModeCapab)
      • field-type = DataReqModeFlags
      • field-length = 2 bytes
      • field-value = 0x00 0x00
      • PHG response to data-req-mode-flags is always 0.
    • m. data-req-init-agent-count (DataReqModeCapab)
      • field-type = INT-U8
      • field-length = 1 byte
      • field-value = 0x00
    • n. data-req-init-manager-count (DataReqModeCapab)
      • field-type = INT-U8
      • field-length = 1 byte
      • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/HUB/BV-004 | | | +| TP label | Maximum APDU size: Activity Hub | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4;M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_021 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 5080
         ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 
                     attribute-value: '00 (5054 bytes) 00'O             }         }     }     ObservationScan ::= {         obj-handle: 1         attributes: AttributeList ::= {             AVA-Type ::= {                 attribute-id: 2661 (MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR)                 attribute-value: 0x80 0x00 0x00 0x00             }         }     }
    1. 2. Check the response of the PHG under test.
    2. 3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    3. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +### A.10 Subgroup 2.3.9: Adherence monitor (AM) + +| | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-000 | | +| TP label | Configuration Event Report. Adherence Monitor standard configuration 7200 | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | ConfEventRep 18;M | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | +| Other PICS | C_MAN_OXP_085 | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x1c 0x20 (MedicalMonitor).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    If the result of the association response was "accepted-unknown-config"

    | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    3. The simulated PHD sends a configuration event report with config-report-id set to 0x1c 0x20.

    4. The PHG under test must respond with:

    1. APDU Type
      • field-length = 2 bytes
      • field-value = 0xE7 0x00 (PrstApdu)
    2. Invoke-id
      • field-type = INT-U16
      • field-length = 2 bytes
      • field-value= it must be the same as the invoke-id of the simulated PHD's message.
    3. Obj-Handle:
      • field-type = HANDLE
      • field-length = 2 bytes
      • field-value = 0x00 0x00
    4. Event-time:
      • field-type = INT-U32
      • field-length = 4 bytes
      • field-value: 0xXX 0xXX
    5. Event-type:
      • field-length = 2 bytes
      • field-value= MDC_NOTI_CONFIG
    6. The following six bytes indicate:
      • Event-replay-info.length (2 bytes)
      • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
      • ConfigReportRsp.config-result: One of:
        • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | The PHG can request Get MDS while they are in the Associated state. | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-001 | | | +| TP label | Configuration Event Report. Adherence Monitor standard configuration 7201 | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x1c 0x21 (MedicalMonitor).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x1c 0x21.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value= it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value: 0xXX 0xXX
      5. e. Event-type:
        1. field-length = 2 bytes
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    • a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    • c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | The PHG can request Get MDS while they are in the Associated state. | + +| | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-002 | | +| TP label | Configuration Event Report. Adherence Monitor standard configuration 7202 | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | ConfEventRep 18;M | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | +| Other PICS | C_MAN_OXP_085 | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x1c 0x22 (MedicalMonitor).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)
    | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    If the result of the association response was "accepted-unknown-config"

    1. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x1c 0x22.
    2. 4. The PHG under test must respond with:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value= it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        • field-type = HANDLE
        • field-length = 2 bytes
        • field-value = 0x00 0x00
      4. d. Event-time:
        • field-type = INT-U32
        • field-length = 4 bytes
        • field-value: 0xXX 0xXX
      5. e. Event-type:
        • field-length = 2 bytes
        • field-value= MDC_NOTI_CONFIG
      6. f. The following six bytes indicate:
        • Event-replay-info.length (2 bytes)
        • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
        • ConfigReportRsp.config-result: One of:
          • ▪ accepted-config: 0x00 0x00
    3. 5. IF C_MAN_OXP_085 THEN:
      1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
      3. c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | The PHG can request Get MDS while they are in the Associated state. | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-003 | | | +| TP label | Configuration Event Report. Adherence Monitor standard configuration 7203 | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x1c 0x23 (MedicalMonitor).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x1c 0x23.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value= it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value: 0xXX 0xXX
      5. e. Event-type:
        1. field-length = 2 bytes
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    Wait until the Operating state is reached in both cases.

    5. IF C_MAN_OXP_085:

    • a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    • c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | The PHG can request Get MDS while they are in the Associated state. | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-004 | | | +| TP label | Maximum APDU size: Adherence Monitor | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4;M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next one apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |

    1. The simulated PHD sends a Confirmed variable event report:

    • a. ScanReportInfoVar. obs_scan_var:
      • Count = 2
      • Length = 984
      • ObservationScan ::= {
        • obj-handle: 1
        • attributes: AttributeList ::= {
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 
     AVA-Type ::= {   attribute-id: 61441   attribute-value: '00.....(960 bytes)..... 00'0 } } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)       attribute-value: 3     }   } }
    1. 2. Check the response of the PHG under test.
    2. 3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    3. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-005 | | | +| TP label | Attribute-Value-Map. Order change. (0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | FixedDosage12; M | | +| Test purpose | Check that:

    For [Standard-Configuration, Fixed Dosage Medication Object] the [Attribute-Value-Map] attribute shall be present and with value MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_VAL_OBS_BASIC | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_VAL_OBS_BASIC.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Fixed Dosage Medication Object) to reverse the values to: MDC_ATTR_NU_VAL_OBS_BASIC then MDC_ATTR_TIME_STAMP_ABS.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the measurement followed by the date (absolute-time-stamp).
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    8. The simulated PHD waits until there is an association release response.

    9. The simulated PHD sends an association request using the same standard configuration that was used previously.

    10. If the PHG under test responds with association request response with "accepted-unknown-config", then

    • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
    • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.

    11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_TIME_STAMP_ABS, then MDC_ATTR_NU_VAL_OBS_BASIC). The observation should be a reasonable Fixed Dosage Medication observation.

    12. The simulated PHD waits until it receives a confirmation.

    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-006 | | | +| TP label | Attribute-Value-Map. Order change. (0x1c23) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | VarDosage12; M | UserFeedback12; M | +| Test purpose |

    Check that:

    For [Standard-Configuration, Variable Dosage Medication Object] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_TIME_STAMP_ABS MDC_ATTR_NU_VAL_OBS_SIMP

    [AND]

    For [Standard-Configuration, User Feedback Object] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_TIME_STAMP_ABS MDC_ATTR_NU_CMPD_VAL_OBS_BASIC

    [AND]

    For [Standard-Configuration, Status Reporter Object] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_TIME_STAMP_ABS MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of:
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_NU_VAL_OBS_BASIC for Variable Dosage Medication Object
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_NU_CMPD_VAL_OBS_BASIC for User Feedback Object
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR for Status Reporter Object
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Variable Dosage Medication Object), of handle 4 (User Feedback object) and of handle 3 (Status Reporter Object) to reverse the values to:
      • • MDC_ATTR_NU_VAL_OBS_BASIC then MDC_ATTR_TIME_STAMP_ABS for Variable Dosage Medication Object
      • • MDC_ATTR_NU_CMPD_VAL_OBS_BASIC then MDC_ATTR_TIME_STAMP_ABS for User Feedback Object
      • • MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR then MDC_ATTR_TIME_STAMP_ABS for Status Reporter Object
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the measurement date (absolute-time-stamp) for every object.
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (Observed value defined for every object, then MDC_ATTR_TIME_STAMP_ABS). The observations should be reasonable Variable Dosage Medication, User Feedback and Status Reporter values.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that the PHG under test uses ml as the unit code for Variable Dosage Medication report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-007 | | | +| TP label | Metric-id-list. Standard configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | UserFeedback9; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration, User Feedback Object]. Metric-Id List attribute shall be present and with value {MDC_AI_MED_UF_LOCATION, MDC_AI_MED_UF_RESPONSE}

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 4 (user feedback) containing an observation with the compound field values (SFLOAT) set to (1, 0), for handle 2 containing an observation (FLOAT) of 3 and for handle 3 containing an observation (Enum-Observed-Value-Basic-Bit-Str) with bit 0 set to 1 (A medication dosage was not dispensed within the regimen allowed timing).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data and applies the data properly as User Feedback: location = 1, response = 0, Variable Dosage Medication= 3 and Status Reporter informing that medication dosage was not dispensed within the regimen allowed timing (bit 0 set to 1).
    | | | +| Notes | | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-008 | | | +| TP label | Metric-id-list. Id order change – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | UserFeedback9; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration, User Feedback Object]. Metric-Id List attribute shall be present and with value {MDC_AI_MED_UF_LOCATION, MDC_AI_MED_UF_RESPONSE}

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 4 (user feedback) setting MDC_ATTR_ID_PHYSIO_LIST to (MDC_AI_MED_UF_RESPONSE, then MDC_AI_MED_UF_LOCATION).
    2. The simulated PHD sends a confirmed fixed event report for handle 4 containing a time-stamp and an observation with the compound field values (SFLOAT) set to (2, 3), for handle 2 containing a time-stamp and observation for Variable Dosage Medication of 3ml
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | and for handle 3 containing a time-stamp and observation for Status reporter (Bit 0 set to 1).
    3. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data and time stamp and applies the data (for compound value) properly as Location = 3, Response = 2.
    | +| Notes | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-009 | | | +| TP label | Metric-id-list. Id order change – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | UserFeedback9; M | | +| Test purpose | Check that:

    For [Standard-Configuration, User Feedback Object]. Metric-Id List attribute shall be present and with value {MDC_AI_MED_UF_LOCATION, MDC_AI_MED_UF_RESPONSE} | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 4 (user feedback) setting MDC_ATTR_ID_PHYSIO_LIST to (MDC_AI_MED_UF_RESPONSE, then MDC_AI_MED_UF_LOCATION). In a second observation scan, for handle 4 set the compound field values (SFLOAT) to (4, 5) along with a known time stamp.

    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data and time stamp and applies the data properly as Location = 5, Response = 4.
    | | | +| Notes | | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-010 | | | +| TP label | Metric-id-list. Reduced ids – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | UserFeedback9; M | | +| Test purpose | Check that:

    For [Standard-Configuration, User Feedback Object]. Metric-Id List attribute shall be present and with value {MDC_AI_MED_UF_LOCATION, MDC_AI_MED_UF_RESPONSE} | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 4 (user feedback) setting MDC_ATTR_ID_PHYSIO_LIST to (MDC_AI_MED_UF_LOCATION) and MDC_ATTR_ATTRIBUTE_VAL_MAP to { MDC_ATTR_TIME_STAMP_ABS, 8, MDC_ATTR_NU_CMPD_VAL_OBS_BASIC, 6}.
    2. 2. The simulated PHD sends a confirmed fixed event report for handle 4 containing an observation with the compound field values (SFLOAT) set to (5) along with a known time stamp.
    3. 3. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data and time stamp and applies the data properly location= 5.
    | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-011 | | | +| TP label | Metric-id-list. Reduced ids – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | UserFeedback9; M | | +| Test purpose | Check that:
    For [Standard-Configuration, User Feedback Object]. Metric-Id List attribute shall be present and with value {MDC_AI_MED_UF_LOCATION, MDC_AI_MED_UF_RESPONSE}. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 4 (user feedback) setting MDC_ATTR_ID_PHYSIO_LIST to (MDC_AI_MED_UF_LOCATION).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    3. 3. The simulated PHD sends a confirmed variable event report for handle 4 containing an observation with the compound field values (SFLOAT) set to (3.0) along with a known time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data and time stamp and applies the data properly as location = 3.0.
    | | | +| Notes | | | | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-012 | | | +| TP label | Special values. Not a number – fixed format (0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | FixedDosage12; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Fixed Dosage Medication Object) containing an observation with the value for NaN ([exponent 0, mantissa +(2**11 -1) = 0x07FF]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-013 | | | +| TP label | Special values. Not a number – variable format(0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | FixedDosage22; C | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Fixed Dosage Medication Object) containing an observation with the value for NaN ([exponent 0, mantissa +(2**11 -1) = 0x07FF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------|---------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-014 | | | +| TP label | Special values. Not at this resolution – fixed format(0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | FixedDosage12; M | | +| Test purpose | Check that: | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The PHG receives NRes value (fixed format event report) but it does not use this value. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Fixed Dosage Medication) containing an observation with the value for NRes ([exponent 0, mantissa -(2^{**}11) = 0x0800]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-015 | | | +| TP label | Special values. Not at this resolution – variable format (0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | FixedDosage22; C | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Fixed Dosage Medication) containing an observation with the value for NRes ([exponent 0, mantissa -(2^{**}11) = 0x0800]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------|-----------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-016 | | | +| TP label | Special values. Positive infinity – fixed format (0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | FixedDosage12; M | | +| Test purpose | Check that: | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 containing an observation with the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 -2) = 0x07FE]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-017 | | | +| TP label | Special values. Positive infinity – variable format(0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | FixedDosage22; C | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Fixed Dosage Medication) containing an observation with the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 -2) = 0x07FE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|-----------------|-----------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-018 | | | +| TP label | Special values. Negative infinity – fixed format (0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | FixedDosage12; M | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    The PHG receives a -INFINITY value (fixed format event report) but it does not use this value. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Fixed Dosage Medication) containing an observation with the value for negative infinity (-INFINITY, [exponent 0, mantissa -(2**11 -2) = 0x0802]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-019 | | | +| TP label | Special values. Negative infinity – variable format (0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | FixedDosage22; C | | +| Test purpose | Check that:
    The PHG receives a -INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Fixed Dosage Medication) containing an observation with the value for negative infinity (-INFINITY, [exponent 0, mantissa -(2**11 -2) = 0x0802]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|-----------------|--------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-020 | | | +| TP label | Special values. Reserved – fixed format (0x1c20) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--|--| +| | Testable items | FixedDosage12; M | | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Fixed Dosage Medication) containing an observation with the value that is reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-021 | | | | +| TP label | Special values. Reserved – variable format (0x1c20) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | | +| | Testable items | FixedDosage22; C | | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c20). | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Fixed Dosage Medication) containing an observation with the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-022 | | | | +| TP label | Special values. Not a number – fixed format (0x1c23) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | | +| | Testable items | VarDosage12; M | UserFeedback12; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for NaN ([exponent 0, mantissa +(2**23 –1) = 0x007FFFFFF] for Variable Dosage Medication, and [exponent 0, mantissa +(2**11 –1) = 0x07FF] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-023 | | | | +| TP label | Special values. Not a number – variable format (0x1c23) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | | +| | Testable items | VarDosage20; C | UserFeedback23; C | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for NaN ([exponent 0, mantissa +(2**23 –1) = 0x007FFFFFF] for Variable Dosage Medication and [exponent 0, mantissa +(2**11 –1) = 0x07FF] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|--| +| Notes | This test case has been considered as an implicit test case. | | | | +| TP Id | TP/PLT/PHG/CLASS/AM/BV-024 | | | | +| TP label | Special values. Not at this resolution – fixed format (0x1c23) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | | +| | Testable items | VarDosage12; M | UserFeedback12; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for NRes ([exponent 0, mantissa +(2**23) = 0x00800000] for Variable Dosage Medication and [exponent 0, mantissa –(2**11) = 0x0800] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|--| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-025 | | | | +| TP label | Special values. Not at this resolution – variable format (0x1c23) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | | +| | Testable items | VarDosage20; C | UserFeedback23; C | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for NRes ([exponent 0, mantissa +(2**23) = 0x00800000] for Variable Dosage Medication and [exponent 0, mantissa -(2**11) = 0x0800] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | + +| | | +|--------------|-----------------------------------------------------------------| +| | displayed in some form that indicates it is not a measurement). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-026 | | | +| TP label | Special values. Positive infinity – fixed format (0x1c23) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | VarDosage12; M | UserFeedback12; M | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**23 – 2) = 0x007FFFFE] for Variable Dosage Medication and [exponent 0, mantissa +(2**11 – 2) = 0x07FE] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-027 | | | +| TP label | Special values. Positive infinity – variable format (0x1c23) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | VarDosage20; C | UserFeedback23; C | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**23 – 2) = 0x007FFFFE] for Variable Dosage Medication and [exponent 0, mantissa +(2**11 – 2) = 0x07FE] for User Feedback).
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 0x07FE] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-028 | | | +| TP label | Special values. Negative infinity – fixed format (0x1c23) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | VarDosage12; M | UserFeedback12; M | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for negative infinity (–INFINITY, [exponent 0, mantissa -(2^{23} - 2) = 0x00800002] for Variable Dosage Medication and [exponent 0, mantissa -(2^{11} - 2) = 0x0802] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-029 | | | +| TP label | Special values. Negative infinity – variable format (0x1c23) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | VarDosage20; C | UserFeedback23; C | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | configuration (0x1c23). | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for negative infinity (-\text{INFINITY}, [exponent 0, mantissa -(2^{23} - 2) = 0x00800002] for Variable Dosage Medication and [exponent 0, mantissa -(2^{11} - 2) = 0x0802] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-030 | | | +| TP label | Special values. Reserved – fixed format (0x1c23) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | VarDosage12; M | UserFeedback12; M | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{23} - 1) = 0x00800001] for Variable Dosage Medication and [exponent 0, mantissa -(2^{11} - 1) = 0x0801] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-031 | | | +| TP label | Special values. Reserved – variable format (0x1c23) | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | VarDosage20; C | UserFeedback23; C | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | not use this value. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x1c23). | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Variable Dosage Medication) and handle 4 (User Feedback) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{23} - 1) = 0x00800001] for Variable Dosage Medication and [exponent 0, mantissa -(2^{11} - 1) = 0x0801] for User Feedback).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/AM/BV-032 | | | +| TP label | Association procedure PHG AM | | | +| Coverage | Spec | [ISO/IEEE 11073-10472] | | +| | Testable items | MM_AssocReq9; M | MM_AssocResp1; M | +| | | MM_AssocResp3; M | MM_AssocResp4; M | +| | | MM_AssocResp6; M | MM_AssocResp7; M | +| | | MM_AssocResp9; M | MM_AssocResp10; M | +| | | MM_AssocResp12; M | | +| Test purpose |

    Check that:

    In the association response message sent by the PHG:

    The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601.

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-protocol-id-20601

    [AND]

    The data-protocol-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = 0x80000000)

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    | | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    The fields data-req-init-*-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '10000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16481
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an association response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
          • ▪ If association is rejected-permanent, field-value= 0x00 0x01.
          • ▪ If association is rejected-transient, field-value= 0x00 0x02.
          • ▪ If association is accepted-unknown-config, field-value= 0x00 0x03.
          • ▪ If association is rejected-no-common-protocol, field-value= 0x00 0x04.
          • ▪ If association is rejected-no-common-parameter, field-value= 0x00 0x05.
    | + +- If association is rejected–unknown = 0x00 0x06. + - If association is rejected–unauthorized, field-value= 0x00 0x07. + - If association is rejected–unsupported-assoc-version, field-value= 0x00 0x08. +- c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) +- d. data-proto-id + - field-type = DataProtoId + - field-length = 2 bytes + - field-value= 0x50 0x79 (20601) +- e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x80 0x00 0x00 0x00 +- f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time +- g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value= Bit 0 must be set (nom-version1) +- h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set +- i. system type + - field-type = SystemType + - field-length = 4 bytes (BITS-32) + - field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) +- j. system-id + - field-type = OCTET STRING + - field-length = 8 bytes + - field-value = (EUI-64 manufacturer and device) +- k. dev-config-id + - field-type = ConfigId + - field-length = 2 bytes + - field-value = 0x00 0x00 (manager-config-response) +- l. data-req-mode-flags (DataReqModeCapab) + - field-type = DataReqModeFlags + - field-length = 2 bytes + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-value = 0x00 0x00
    • PHG response to data-req-mode-flags is always 0.

    m. data-req-init-agent-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00

    n. data-req-init-manager-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A].
    data-req-init-agent-count verification has been updated according to IEEE PHD errata. See http://continua.plugfest.com/show_bug.cgi?id=786 for further details. | + +### A.11 Subgroup 2.3.10: Insulin pump (IP) + +| | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-000 | | | +| TP label | Association procedure PHG Insulin Pump | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | ManProcAsIP 1;M | ManProcAsIP 2;M | +| | | ManProcAsIP 4;M | ManProcAsIP 5;M | +| | | ManProcAsIP 7;M | ManProcAsIP 8;M | +| | | ManProcAsIP 10;M | ManProcAsIP 11;M | +| Test purpose |

    Check that:

    The result field shall be set to an appropriate response from those defined in [ISO/IEEE 11073-20601-2016C].

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-protocol-id-20601

    [AND]

    The data-protocol-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version 2

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    If the PHD supports only the insulin pump specialization, data-req-init-agent-count shall be 1 and data-req-init-manager-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test, with the fields:
      • protocol-version = '00100000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16440
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. PHG under test sends an Association Response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
          • ▪ If association is rejected-permanent, field-value= 0x00 0x01.
          • ▪ If association is rejected-transient, field-value= 0x00 0x02.
          • ▪ If association is accepted-unknown-config, field-value= 0x00 0x03.
          • ▪ If association is rejected-no-common-protocol, field-value= 0x00 0x04.
          • ▪ If association is rejected -no-common-parameter, field-value= 0x00 0x05.
          • ▪ If association is rejected –unknown = 0x00 0x06.
          • ▪ If association is rejected -unauthorized, field-value= 0x00 0x07.
    | + +- If association is rejected –unsupported-assoc-version, field-value= 0x00 0x08. + +- c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) +- d. data-proto-id + - field-type = DataProtoId + - field-length = 2 bytes + - field-value= 0x50 0x79 (20601) +- e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x80 0x00 0x00 0x00 +- f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time +- g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value= Bit 0 must be set (nom-version1) +- h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set +- i. system type + - field-type = SystemType + - field-length = 4 bytes (BITS-32) + - field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) +- j. system-id + - field-type = OCTET STRING + - field-length = 8 bytes + - field-value = ( EUI-64 manufacturer and device ) +- k. dev-config-id + - field-type = ConfigId + - field-length = 2 bytes + - field-value = 0x00 0x00 (manager-config-response) +- l. data-req-mode-flags (DataReqModeCapab) + - field-type = DataReqModeFlags + - field-length = 2 bytes + - field-value = 0x00 0x00 + - PHG response to data-req-mode-flags is always 0. + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    m. data-req-init-agent-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00

    n. data-req-init-manager-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-----------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-001 | | | +| TP label | Configuration Event Report. Insulin Pump standard configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | ConfProcIP 4;M | MDSEventsIP 2;M | +| | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a “Remote Operation Response Confirmed Event Report” data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A PHG shall support both single-person and multi-person event reports.

    [AND]

    An Insulin pump PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. The simulated PHD implements an Insulin Pump device specialization with Standard Configuration (1900) | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x07 0x6C (Insulin Pump PHD – Std Config 1900)
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. The PHG under test responds an Association Response, the field of interest is:

    a. Result

    • field-type = INT-U16
    • field-length = 2 bytes
    • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    IF the result of the Association Response was “accepted-unknown-config”

    3. The simulated PHD sends a configuration event report with config-report-id set to 0x07 0x08

    4. The PHG under test must respond with:

    a. APDU Type

    • field-length = 2 bytes
    • field-value = 0xE7 0x00 (PrstApdu)

    b. Invoke-id

    • field-type = INT-U16
    • field-length = 2 bytes
    • field-value= it must be the same that the invoke-id of the simulated PHD's message.

    c. Obj-Handle:

    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = 0x00 0x00

    d. Event-time:

    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value: 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.

    b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.

    c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until Operating state is reached in both cases

    6. Simulated PHD sends a fixed event report with one Insulin Pump measurement

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an “accepted” message or to the Configuration Event Report with an “accepted-config”
    | + +| | | +|--------------|------------------------------------------------------------------------------------------| +| |
    • The measurement is correctly presented
    | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-002_A | | | +| TP label | Maximum APDU size: Insulin Pump without PM-Store | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4; M | | +| | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | ComCharIP 2; M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |
    1. The simulated PHD sends a Confirmed variable event report:
      1. ScanReportInfoVar.obs_scan_var:
        • Count = 2
        • Length = 7128
         ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 61441             attribute-value: '00.....( 7104 bytes)..... 00'O         }     } }  ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)             attribute-value: 3         }     } }
    2. Check the response of the PHG under test.
    3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 4. Check the response of the PHG under test. | +| Pass/Fail criteria |
    • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report"
    • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report"
    | +| Notes | | + +| | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-002_B | | +| TP label | Maximum APDU size: Insulin Pump with PM-Store | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 4; M | +| | Spec | [ISO/IEEE 11073-10419] | +| | Testable items | ComCharIP 3; M | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next one apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 AND C_MAN_OXP_003 | | +| Other PICS | | | +| Initial condition | The PHG under test is in the Operating state. | | +| Test procedure |

    1. The simulated PHD sends a Confirmed variable event report:

    a. ScanReportInfoVar. obs_scan_var:

    Count = 2

    Length = 5080

     ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 61441             attribute-value: '00.....( 5056 bytes)..... 00'O         }     } } ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 2636             (MDC_ATTR_NU_VAL_OBS_BASIC)             attribute-value: 3         }     } }
    | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. Check the response of the PHG under test.
    2. 3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    3. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report"
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report"
    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-003 | | | +| TP label | Bolus Delivered Attribute-Value-Map. Order change | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | BolusDer 22; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report with that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Bolus Delivered Object) to reverse the values to: MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_NU_VAL_OBS_BASIC.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. Send a confirmed fixed format event report with the date first followed by an Bolus Delivered value.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO). The observation should be a reasonable Bolus
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Delivered observation.

    12. The simulated PHD waits until it receives a confirmation.

    | +| Pass/Fail criteria |
    • • In Step 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In Step 2, 6 and 12 verify the PHG under test uses MDC_DIM_INTL_UNIT as the unit-code for the measurement report (or reports the proper value after convert to another unit-code)
    • • In Step 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, need to be careful about just sending these messages back to back since the ability to look at things like a UI may need there to be pauses for operator verification.
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-004 | | | +| TP label | Bolus Delivered Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | BolusDer 22; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (1900). (Bolus Delivered Numeric standard configuration Unit code attribute is set to MDC_DIM_INTL_UNIT) | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Bolus Delivered Numeric Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. Send a confirmed fixed format event report with the new data layout. For unit-code Attribute, use MDC_DIM_INTL_UNIT (5472).
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC Attribute.
    6. 6. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • • In Step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In Step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    | | | + +| | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • In Step 4 and 6, verify the PHG under test uses MDC_DIM_INTL_UNIT as the unit-code for the measurement reports
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-005 | | | +| TP label | Bolus Delivered Unit-Code. Use default Bolus Delivered units - variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | BolusDer 20; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_INTL_UNIT | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (1900). | | | +| Test procedure | 1. Send a confirmed variable format event report using a measurement in using MDC_DIM_INTL_UNIT units.
    2. The simulated PHD waits until it receives a confirmation | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data properly and applies MDC_DIM_INTL_UNIT unit to the observation (e.g., if there is a UI verify the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | +| Notes | | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-006 | | | +| TP label | Bolus Delivered Special values. Not a number - fixed format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | BolusDer 22; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Bolus Delivered Object) containing an observation value with the value for not a number (NaN (not a number) [exponent 0, mantissa +(2**11 -1) = 0x07FF]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-007 | | | | | +| TP label | Bolus Delivered Special values. Not a number - variable format (Std Config) | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | | | +| | Testable items | BolusDer 44; M | | | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | | | +| Other PICS | | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Bolus Delivered Object) containing an observation value set to the value for not a number (NaN (not a number) [exponent 0, mantissa +(2**11 -1) = 0x07FF])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | | | +| Notes | This test case has been considered as an implicit test case. | | | | | + +| | | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-008 | | | | | +| TP label | Bolus Delivered Special values. Not at this resolution - fixed format (Std Config) | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | | | +| | Testable items | BolusDer 22; M | | | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | | | +| Other PICS | | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | | | | +| Test procedure | 1. The Simulated PHD sends a confirmed fixed event report for handle 1 (Bolus Delivered Object) containing an observation value set to the value for not at this resolution (NRes (not at this resolution) [exponent 0, mantissa -(2**11) = 0x0800]) and a time stamp | | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 2. The simulated PHD waits until it receives a confirmation from the PHG under test | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-009 | | +| TP label | Bolus Delivered Special values. Not at this resolution - variable format (Std Config) | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | +| | Testable items | BolusDer 44; M | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Bolus Delivered Object) containing an observation value set to the value for not at this resolution (NRes (not at this resolution) [exponent 0, mantissa $-(2^{**11}) = 0x0800$ ])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | | +| Notes | This test case has been considered as an implicit test case. | | + +| | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-010 | | +| TP label | Bolus Delivered Special values. Positive infinity - fixed format (Std Config) | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | +| | Testable items | BolusDer 22; M | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Bolus Delivered Object) containing an observation value set to the value for positive infinity (+INFINITY) | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [exponent 0, mantissa +(2**11 –2) = 0x07FE]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-011 | | | | | +| TP label | Bolus Delivered Special values. Positive infinity - variable format (Std Config) | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | | | +| | Testable items | BolusDer 44; M | | | | +| Test purpose | Check that:
    PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | | | +| Other PICS | | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Bolus Delivered Object) containing an observation value set to the value for positive infinity (+INFINITY [exponent 0, mantissa +(2**11 –2) = 0x07FE])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | | | | | +| Notes | This test case has been considered as an implicit test case. | | | | | + +| | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-012 | | | | | +| TP label | Bolus Delivered Special values. Negative infinity - fixed format (Std Config) | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | | | +| | Testable items | BolusDer 22; M | | | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | | | +| Other PICS | | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Bolus Delivered
    | | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Object) containing an observation value set to the value for negative infinity ( $-\text{INFINITY}$ [exponent 0, mantissa $-(2^{11}-2) = 0x0802$ ]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-013 | | +| TP label | Bolus Delivered Special values. Negative infinity - variable format (Std Config) | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | +| | Testable items | BolusDer 44; M | +| Test purpose | Check that:
    PHG receives a $-\text{INFINITY}$ value (variable format event report) but it does not use this value. | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Bolus Delivered Object) containing an observation value set to the value for negative infinity (-\text{INFINITY} [exponent 0, mantissa -(2^{11}-2) = 0x0802])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | | +| Notes | This test case has been considered as an implicit test case. | | + +| | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-014 | | +| TP label | Bolus Delivered Special values. Reserved - fixed format (Std Config) | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | +| | Testable items | BolusDer 22; M | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Bolus Delivered Object) containing an observation value set to the value for reserved (Reserved for future use [exponent 0, mantissa -(2^{11}-1) = 0x0801]) and a time stamp
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-015 | | | +| TP label | Bolus Delivered Special values. Reserved - variable format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | BolusDer 44; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1900. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (Bolus Delivered Object) containing an observation value set to the value for reserved (Reserved for future use [exponent 0, mantissa -(2^{11}-1) = 0x0801])
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-016 | | | +| TP label | Current Basal Rate Setting Attribute-Value-Map. Order change | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 22;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a Current Basal Rate Setting confirmed fixed format event report with that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Current Basal Rate Setting Numeric Object) to reverse the values to: MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_NU_VAL_OBS_BASIC.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. Send a confirmed fixed format event report with the date first followed by a Current Basal Rate Setting value (in MDC_DIM_INTL_UNIT_PER_HR units since it is the standard configuration unit-code).
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO). The observation should be a reasonable Current Basal Rate Setting observation.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In Step 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In Step 2, 6 and 12 verify the PHG under test uses MDC_DIM_INTL_UNIT_PER_HR units as the unit-code for the measurement report (or reports the proper value after convert to another unit-code)
    • • In Step 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, need to be careful about just sending these messages back to back since the ability to look at things like a UI may need there to be pauses for operator verification.
    | +| Notes | | + +| | | | +|-----------------|---------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-017 | | +| TP label | Current Basal Rate Setting Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | +| | Testable items | CurrBasRate 22;M | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (Current Basal Rate Setting Numeric standard configuration Unit code attribute is set to MDC_DIM_INTL_UNIT_PER_HR) | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Current Basal Rate Setting Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. Send a confirmed fixed format event report with the new data layout. For unit-code Attribute, use MDC_DIM_INTL_UNIT_PER_HR (5696).
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC Attribute.
    6. 6. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In Step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In Step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    • • In Step 4 and 6, verify the PHG under test uses MDC_DIM_INTL_UNIT_PER_HR as the unit-code for the measurement reports
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-018 | | | +| TP label | Current Basal Rate Setting Unit-Code. Use default Current Basal Rate Setting units - variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 20; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_INTL_UNIT_PER_HR | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. Send a confirmed variable format event report using a measurement using | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_DIM_INTL_UNIT_PER_HR unit code
    2. The simulated PHD waits until it receives a confirmation | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data properly and applies the appropriate units to the observation (e.g., if there is a UI verify the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-019 | | | +| TP label | Current Basal Rate Setting Special values. Not a number - fixed format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 22;M | | +| Test purpose | Check that:
    PHG receives a NaN value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Current Basal Rate Setting Object) containing an observation value with the value for not a number (NaN (not a number) [exponent 0, mantissa +(2**11 -1) = 0x07FF]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement such as "___" or blanking the display area).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-020 | | | +| TP label | Current Basal Rate Setting Special values. Not at this resolution - fixed format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 22;M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Current Basal
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Rate Setting Object) containing an observation value set to the value for not at this resolution (NRes (not at this resolution) [exponent 0, mantissa $-(2^{11}) = 0x0800$ ]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-021 | | | +| TP label | Current Basal Rate Setting Special values. Positive infinity - fixed format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 22;M | | +| Test purpose | Check that:
    PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 2 (Current Basal Rate Setting Object) containing an observation value set to the value for positive infinity (+INFINITY [exponent 0, mantissa $+(2^{11} - 2) = 0x07FE$ ]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-022 | | | +| TP label | Current Basal Rate Setting Special values. Negative infinity - fixed format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 22;M | | +| Test purpose | Check that:
    The PHG receives a -INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed event report for handle 2 (Current Basal Rate Setting Object) containing an observation value set to the value for negative infinity (-\text{INFINITY} [exponent 0, mantissa -(2^{11}-2) = 0x0802]) and a time stamp
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-023 | | | +| TP label | Current Basal Rate Setting Special values. Reserved - fixed format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 22;M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed event report for handle 2 (Current Basal Rate Setting Object) containing an observation value set to the value for reserved (Reserved for future use [exponent 0, mantissa -(2^{11}-1) = 0x0801]) and a time stamp
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-024 | | | +| TP label | Current Basal Rate Setting Special values. Not a number - variable format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 44; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 2 (Current Basal Rate Setting Object) containing an observation value set to the value for not a number (NaN (not a number) [exponent 0, mantissa $+(2^{11}-1) = 0x07FF$ ])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-025 | | | +| TP label | Current Basal Rate Setting Special values. Not at this resolution - variable format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 44; M | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 2 (Current Basal Rate Setting Object) containing an observation value set to the value for not at this resolution (NRes (not at this resolution) [exponent 0, mantissa $-(2^{11}) = 0x0800$ ])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-026 | | | +| TP label | Current Basal Rate Setting Special values. Positive infinity - variable format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 44; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 2 (Current Basal Rate Setting Object) containing an observation value set to the value for positive infinity (+INFINITY [exponent 0, mantissa +(2^{11} - 2) = 0x07FE])
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-027 | | | +| TP label | Current Basal Rate Setting Special values. Negative infinity - variable format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 44; M | | +| Test purpose | Check that:

    The PHG receives a –INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 2 (Current Basal Rate Setting Object) containing an observation value set to the value for negative infinity (– INFINITY [exponent 0, mantissa -(2^{11} - 2) = 0x0802])
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-028 | | | +| TP label | Current Basal Rate Setting Special values. Reserved - variable format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | CurrBasRate 44; M | | +| Test purpose | Check that:

    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_071 | | | +| Other PICS | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 2 (Current Basal Rate Setting Object) containing an observation value set to the value for reserved (Reserved for future use [exponent 0, mantissa -(2^{11} - 1) = 0x0801])
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | +| Pass/Fail Criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-029_A | | | +| TP label | Schedule-Store Class methods. Get-Schedule-Segment-Info method 1 | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | SchStoreMeth 2; M | SchStoreMeth 5; M | +| Test purpose |

    Check that:

    If a PHG invokes the [Get-Schedule-Segment-Info] method it shall use the operation type roiv-cmip-confirmed-action, the Action-type MDC_ACT_SCHED_SEG_GET_INFO and the action-info-args SchedSegmSelection.

    [AND]

    For an PHG supporting the Schedule-Store class the support of the [Get-Schedule-Segment-Info], [Get-Schedule-Segment-Id-List] and [Trig-Schedule-Segment-Data-Xfer] methods is mandatory

    [AND]

    The PHG shall support at least the choice all-sched-segments in the SegmSelection action-info-args of the Get-Schedule-Segment-Info method.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one schedule segment with data stored and the Schedule-Store-Capab attribute indicates that it supports all the possible actions. | | | +| Test procedure |
    1. 1. Make the PHG under test perform a [Get-Schedule-Segment-Info] action to recover the information of all the schedule-segments.
    2. 2. The simulated PHD receives the message:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. invoke-id
        • field-type = InvokeIDType
        • field-length = 2 bytes
        • field-value= This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.
      3. c. obj-handle
        • field-type = HANDLE
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 2 bytes
    • field-value = <Handle of an existing Schedule-Store>

    d. action-type (roiv-cmip-confirmed-action)

    • field-type = OID-Type
    • field-length = 2 bytes
    • field-value = 0x0C 0x24 (MDC_ACT_SCHED_SEG_GET_INFO)

    e. action-info-args

    • SchedSegmSelection = all-sched-segments (0)
    | +| Pass/Fail criteria | The PHG shall perform Get-Schedule-Segment-Info with all-sched-segments choice and the format of the received message must be the one specified | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-029_B | | | +| TP label | Schedule-Store Class methods. Get-Schedule-Segment-Info method 2 | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | SchStoreMeth 2; M | SchStoreMeth 5; M | +| Test purpose |

    Check that:

    If a PHG invokes the [Get-Schedule-Segment-Info] method it shall use the operation type roiv-cmip-confirmed-action, the Action-type MDC_ACT_SCHED_SEG_GET_INFO and the action-info-args SchedSegmSelection.

    [AND]

    For a PHG supporting the Schedule-Store class the support of the [Get-Schedule-Segment-Info], [Get-Schedule-Segment-Id-List] and [Trig-Schedule-Segment-Data-Xfer] methods is mandatory

    [AND]

    The PHG may support the choice sched-segm-id-list in the SegmSelection action-info-args of the Get-Schedule-Segment-Info method.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one schedule segment with data stored and the Schedule-Store-Capab attribute indicates that it supports all the possible actions. | | | +| Test procedure |
    1. 1. Make the PHG under test perform a [Get-Schedule-Segment-Info] action to recover the information of specific schedule-segments.
    2. 2. The simulated PHD receives the message:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. invoke-id
        • field-type = InvokeIDType
        • field-length = 2 bytes
        • field-value= This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. obj-handle

    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = <Handle of an existing Schedule-Store>

    d. action-type (roiv-cmip-confirmed-action)

    • field-type = OID-Type
    • field-length = 2 bytes
    • field-value = 0x0C 0x24 (MDC_ACT_SCHED_SEG_GET_INFO)

    e. action-info-args

    • SchedSegmSelection = sched-segm-id-list
      • ▪ SchedSegmIdList = <List of the selected schedule-segments' instance numbers>
    | +| Pass/Fail criteria | If the PHG supports Get-Schedule-Segment-Info action with sched-segm-id-list choice, the format of the received message must be the one specified. | +| Notes | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-030 | | | | +| TP label | Schedule-Store Class methods. Get-Schedule-Segment-Id-List | | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | | +| | Testable items | SchStoreMeth 2; M | SchStoreMeth 13; M | | +| Test purpose |

    Check that:

    If a PHG invokes the [Get-Schedule-Segment-Id-List] method it shall use the operation type roiv-cmip-confirmed-action, the Action-type MDC_ACT_SCHED_SEG_GET_ID_LIST and the action-info-args set to empty [AND]

    For a PHG supporting the Schedule-Store class the support of the [Get-Schedule-Segment-Info], [Get-Schedule-Segment-Id-List] and [Trig-Schedule-Segment-Data-Xfer] methods is mandatory

    | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one schedule segment with data stored and the Schedule-Store-Capab attribute indicates that it supports all the possible actions. | | | | +| Test procedure |
    1. 1. Make the PHG under test perform a [Get-Schedule-Segment-Id-List] action to recover a list of schedule-segments' instance numbers.
    2. 2. The simulated PHD receives the message:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. invoke-id
        • field-type = InvokeIDType
        • field-length = 2 bytes
        • field-value= This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. obj-handle

    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = <Handle of an existing Schedule-Store>

    d. action-type (roiv-cmip-confirmed-action)

    • field-type = OID-Type
    • field-length = 2 bytes
    • field-value = 0x0C 0x25 (MDC_ACT_SCHED_SEG_GET_ID_LIST)

    e. action-info-args

    • <empty>
    | +| Pass/Fail criteria | The PHG shall perform Get-Schedule-Segment-Id-List action, and the format of the received message must be the one specified. | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-031 | | | +| TP label | Schedule-Store Class methods. Trig-Schedule-Segment-Data-Xfer | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | SchStoreMeth 2; M | SchStoreMeth 15; M | +| Test purpose |

    Check that:

    If a PHG invokes the [Trig-Schedule-Segment-Data-Xfer] method it shall use operation type roiv-cmip-confirmed-action, the Action-type MDC_ACT_SCHED_SEG_TRIG_XFER and the action-info-args TrigSchedSegmDataXferReq

    [AND]

    For an PHG supporting the schedule-store class the support of the [Get-Schedule-Segment-Info], [Get-Schedule-Segment-Id-List] and [Trig-Schedule-Segment-Data-Xfer] methods is mandatory

    [AND]

    The PHG retrieves specific schedule-segments by using the Trig-Schedule-Segment-Data-Xfer ACTION method with the handle of the schedule-store object to access. The argument to this ACTION method is the instance number of the segment to transfer.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one schedule segment with data stored and the Schedule-Store-Capab attribute indicates that it supports all the possible actions. | | | +| Test Procedure |
    1. 1. Make the PHG under test perform a [Trig-Schedule-Segment-Data-Xfer] action.
    2. 2. The simulated PHD receives the message:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. invoke-id
        • field-type = InvokeIDType
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 2 bytes
    • field-value= This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.

    c. obj-handle

    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = <Handle of an existing Schedule-Store>

    d. action-type (roiv-cmip-confirmed-action)

    • field-type = OID-Type
    • field-length = 2 bytes
    • field-value = 0x0C 0x26 (MDC_ACT_SCHED_SEG_TRIG_XFER)

    e. action-info-args

    • TrigSchedSegmDataXferReq.seg-inst-no = <One of the existing schedule-segments' instance number>
    | +| Pass/Fail criteria | The PHG shall perform Trig-Schedule-Segment-Data-Xfer Action and the format of the received message must be the one specified. | +| Notes | | + +| | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-032_A | | +| TP label | Schedule-Store Class methods. Segment-Data-Event 1 | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | +| | Testable items | SchedStoreEvent 3; M | +| Test purpose |

    Check that:

    The PHGs must respond to [Schedule-Segment-Data-Event] events when received.

    When responding to a [Schedule-Segment-Data-Event] event the event-reply-info parameter shall be ScheduleSegmentDataResult.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | +| Other PICS | | | +| Initial condition |

    The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one schedule segment with data stored and the Schedule-Store-Capab attribute indicates that it supports all the possible actions.

    | | +| Test procedure |
    1. 1. Make the PHG under test perform a Trig-Schedule-Segment-Data-Xfer
    2. 2. The simulated PHD responds to the message with a "TrigSchedSegmDataXferRsp"
    3. 3. The simulated PHD sends a Confirmed event report:
      1. a. Data APDU
        • Type = Invoke Confirmed Event Report
        • Action = 0x0C 0x27 (MDC_NOTI_SCHED_SEGMENT_DATA)
        • ScheduleSegmentDataEvent. SchedSegmDataEventDescr = SEQUENCE:
          • ▪ sched-segm-instance
          • ▪ sched-segm-evt-entry-index
          • ▪ sched-segm-evt-entry-count
    | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ sched-segm-evt-status = Bit 0 must be set (first entry)

    4. The PHG under test sends a response to the previous message

    1. a. Data APDU
      • Type = Response Confirmed Event Report
      • Action = 0x0C 0x27 (MDC_NOTI_SCHED_SEGMENT_DATA)
      • ScheduleSegmentDataResult SchedSegmDataEventDescr = SEQUENCE:
        • ▪ sched-segm-instance = <The one previously sent by the simulated PHD>
        • ▪ sched-segm-evt-entry-index = <The one previously sent by the simulated PHD>
        • ▪ sched-segm-evt-entry-count = <The one previously sent by the simulated PHD>
        • ▪ sched-segm-evt-status = Bits 0, 1 must be the same as the previously recorded. Bit 4 must NOT be set. One of bits 8 or 12 must be set
    | +| Pass/Fail criteria | The format of the received message must be the one specified. | +| Notes | | + +| | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-032_B | | +| TP label | Schedule-Store Class methods. Segment-Data-Event 2 | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | +| | Testable items | SchedStoreEvent 3; M | +| Test purpose |

    Check that:

    A PHG must respond to [Schedule-Segment-Data-Event] events when received.

    When responding to a [Schedule-Segment-Data-Event] event the event-reply-info parameter shall be ScheduleSegmentDataResult.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one schedule segment with data stored and the Schedule-Store-Capab attribute indicates that it supports all the possible actions. | | +| Test procedure |
    1. 1. Make the PHG under test perform a Trig-Schedule-Segment-Data-Xfer
    2. 2. The simulated PHD responds to the message with a "TrigSchedSegmDataXferRsp"
    3. 3. The simulated PHD sends a Confirmed event report:
      1. a. Data APDU
        • Type = Invoke Confirmed Event Report
        • Action = 0x0C 0x27 (MDC_NOTI_SCHED_SEGMENT_DATA)
        • ScheduleSegmentDataEvent. SchedSegmDataEventDescr = SEQUENCE:
          • ▪ sched-segm-instance
          • ▪ sched-segm-evt-entry-index
          • ▪ sched-segm-evt-entry-count
          • ▪ sched-segm-evt-status = Bit 4 (schsevtsta-agent-abort) must be set
    4. 4. PHG under test sends a response to the previous message
    | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | a. Data APDU
    • Type = Response Confirmed Event Report
    • Action = 0x0C 0x27 (MDC_NOTI_SCHED_SEGMENT_DATA)
    • ScheduleSegmentDataResult SchedSegmDataEventDescr = SEQUENCE:
      • ▪ sched-segm-instance = <The one previously sent by the simulated PHD>
      • ▪ sched-segm-evt-entry-index = <The one previously sent by the simulated PHD>
      • ▪ sched-segm-evt-entry-count = <The one previously sent by the simulated PHD>
      • ▪ sched-segm-evt-status = Bits 4 and 8 must be set
    | +| Pass/Fail criteria | The format of the received message must be the one specified. | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-033_A | | | +| TP label | Schedule-Store Class. Metric data transfer 1 | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | SchedStoreTX 1; O | SchedStoreTX 3_A; M | +| Test purpose |

    Check that:

    The PHG may query each schedule-store to determine the number of schedule-segments that exist within the schedule-store.

    [AND]

    The attribute-id-list shall be left empty to query for all attributes of the schedule-store object.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. The simulated PHD has one Schedule-Store object. | | | +| Test procedure |
    1. 1. Make the PHG under test perform a GET service to the Schedule-Store object.
    2. 2. Received message by the simulated PHD must be:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. invoke-id
        • field-type = InvokeIDType
        • field-length= 2 bytes
        • field-value= <Not relevant for this test>
      3. c. CHOICE:
        • field-value= 0x01 0x03 (roiv-cmip-get)
      4. d. obj-Handle:
        • field-type = HANDLE
        • field-length = 2 bytes
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-value = <The handle of the Schedule-Store>

    e. attribute-Id-List:

    • field-type = AttributeIdList
    • field-count = 0x00 0x00
    • field-length = 0x00 0x00
    | +| Pass/Fail criteria | The format of the received message in step 2 must be the one specified. | +| Notes | | + +| | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-033_B | | +| TP label | Schedule-Store Class. Metric data transfer 2 | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | +| | Testable items | SchedStoreTX 23;M      SchedStoreTX 24;M | +| Test purpose |

    Check that:

    When the PHG receives an event report, it shall reply with a ScheduleSegmentDataResult response that shall contain the same schedule-store-handle, sched-segm-instance number, sched-segm-evt-entry-index, and sched-segm-evt-entry-count.

    [AND]

    In the sched-segm-evt-status, the PHG shall set the schsevtsta-manager-confirm bit.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | +| Other PICS | | | +| Initial condition | The PHG under test is in the Operating state. The simulated PHD has one Schedule-Store with at least one Schedule-Segment that contains data. | | +| Test procedure |
    1. 1. Make the PHG under test retrieve the information stored in a Schedule-Segment
    2. 2. The simulated PHD responds to the TrigSchedSegmDataXferReq with an appropriate TrigSchedSegmDataXferRsp message
    3. 3. The simulated PHD sends a ScheduleSegmentDataEvent to the PHG
    4. 4. The PHG under test must respond with a ScheduleSegmentDataResult message, the fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. invoke-id
        • field-type = InvokeIDType
        • field-length= 2 bytes
        • field-value= <The same of the sent ScheduleSegmentDataEvent>
      3. c. CHOICE:
        • field-value= 0x02 0x01 (rors-cmip-confirmed-event-report)
      4. d. Obj-Handle:
        • field-type = HANDLE
        • field-length = 2 bytes
        • field-value = <The same of the sent ScheduleSegmentDataEvent>
    | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    e. CurrentTime

    • field-type = RelativeTime
    • field-length = 4 bytes
    • field-value = <Not relevant for this test>

    f. Event-type

    • field-type = OID-Type
    • field-length = 2 bytes
    • field-value = 0x0C 0x27 (MDC_NOTI_SCHED_SEGMENT_DATA)

    g. ScheduleSegmentDataResult SchedSegmDataEventDescr = SEQUENCE:

    • field-length = 12 bytes
    • field-value =
      • • sched-segm-instance = <The same of the sent ScheduleSegmentDataEvent>
      • • sched-segm-evt-entry-index = <The same of the sent ScheduleSegmentDataEvent>
      • • sched-segm-evt-entry-count = <The same of the sent ScheduleSegmentDataEvent>
      • • sched-segm-evt-status = Bit 8 (schsevtsta-manager-confirm)
    | +| Pass/Fail criteria | The format of the received message in step 4 must be the one specified. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-034 | | | +| TP label | Schedule-Store Class. Specific attributes query | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | SchedStoreTX 3_B; O | | +| Test purpose | Check that:
    Specific attributes of a Schedule-Store object may be queried by listing the desired attribute IDs found in Table E.1. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. The simulated PHD has one Schedule-Store object. | | | +| Test procedure | 1. Make the PHG under test perform a GET request to a specific list of Schedule-Store attributes
    2. Received message by the simulated PHD must be:
    1. a. APDU Type
      • field-length = 2 bytes
      • field-value = 0xE7 0x00 (PrstApdu)
    2. b. invoke-id
      • field-type = InvokeIDType
      • field-length= 2 bytes
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-value= <Not relevant for this test>
      • c. CHOICE:
    • field-value= 0x01 0x03 (roiv-cmip-get)
      • d. Obj-Handle:
    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = <The handle of the Schedule-Store>
      • e. Attribute-Id-List:
    • field-type = AttributeIdList
    • field-count = <It contains one attribute or more>
    • field-value = <Attribute-Id match Attribute-id defined for Schedule-Store attributes (Table E.1)>
    | +| Pass/Fail criteria | The format of the received message in step 2 must be the one specified. | +| Notes | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/IP/BV-035 | | | +| TP label | Schedule-Store Class. Transfer Timeout | | | +| Coverage | Spec | [ISO/IEEE 11073-10419] | | +| | Testable items | SchedSegmAttr 20; M | | +| Test purpose | Check that:
    If the [Schedule-Segment-Transfer-Timeout] expires prior to the reception of the complete schedule segment, the PHG shall transition to the Unassociated state as described in subclause 8.9.5.6 in [ISO/IEEE 11073-20601-2016C]. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_IP_001 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state and the simulated PHD has at least one Schedule-Segment with data. | | | +| Test procedure | 1. Make the PHG under test perform a [Trig-Schedule-Segment-Data-Xfer] action to retrieve data from a Schedule-Segment.
    2. The simulated PHD sends a response including TrigSchedSegmXferRsp = tschsxr-successful(0) (the request can be honored)
    3. The PHD does no send any ScheduleSegmentDataEvent for at least a period of time equal to [Schedule-Segment-Transfer-Timeout] | | | +| Pass/Fail criteria | PHG under test must wait for the last ScheduleSegmentDataEvent message for a period equal to the value of [Schedule-Segment-Transfer-Timeout]. When the time expires, PHG under test must send an abort to the simulated PHD | | | +| Notes | Due to the delay introduced by transport layer and decoder for received APDU, Test Tool accuracy maybe is not enough to measure this time-out. To get a better accuracy, it is necessary to run this test case using a hardware sniffer. | | | + +### A.12 Subgroup 2.3.11: Peak flow (PF) + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-000 | | | +| TP label | Configuration Event Report. Peak Flow standard configuration 2100 | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x08 0x34 (Peak Flow)
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x08 0x34.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        • field-type = HANDLE
        • field-length = 2 bytes
        • field-value = 0x00 0x00
      4. d. Event-time:
        • field-type = INT-U32
        • field-length = 4 bytes
        • field-value: 0xXX 0xXX
      5. e. Event-type:
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 2 bytes
    • field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    • a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    • c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | The PHG can request Get MDS while they are in the Associated state. | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-001 | | | +| TP label | Maximum APDU size: Peak Flow | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4;M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next one apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |

    1. The simulated PHD sends a Confirmed variable event report:

    • a. ScanReportInfoVar. obs_scan_var:
      • Count = 2
      • Length = 1996
      • ObservationScan ::= {
        • obj-handle: 1
        • attributes: AttributeList ::= {
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 
     AVA-Type ::= {   attribute-id: 61441   attribute-value: '00.....(1970 bytes)..... 00'0 } } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2646 (MDC_ATTR_NU_VAL_OBS_SIMP)       attribute-value: 500     }   } } }
    1. 2. Check the response of the PHG under test.
    2. 3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    3. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-002 | | | +| TP label | Attribute-Value-Map. Order change. (0x0834) | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | PEF12; M | PersBest12; M | +| | | ReadStatus12; M | FEV1S12; M | +| Test purpose |

    Check that:

    For [Standard-Configuration, PEF object] the [Attribute-Value-Map] attribute shall be present. The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS

    [AND]

    For [Standard-Configuration, Personal Best object] the [Attribute-Value-Map] attribute shall be present. The value of the [Attribute-Value-Map] attribute shall be value MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS

    [AND]

    For [Standard-Configuration, FEV1] the [Attribute-Value-Map] attribute shall be present. The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS

    [AND]

    For [Standard-Configuration, Reading status] the [Attribute-Value-Map] attribute shall be present. The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC_BIT_STRING, then MDC_ATTR_TIME_STAMP_ABS

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | +| Other PICS | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of:
      • • MDC_ATTR_NU_VAL_OBS_SIMP then MDC_ATTR_TIME_STAMP_ABS for PEF Object
      • • MDC_ATTR_NU_VAL_OBS_SIMP then MDC_ATTR_TIME_STAMP_ABS for Personal Best Object
      • • MDC_ATTR_NU_VAL_OBS_SIMP then MDC_ATTR_TIME_STAMP_ABS for FEV1 Object
      • • MDC_ATTR_NU_VAL_OBS_BASIC_BIT_STRING then MDC_ATTR_TIME_STAMP_ABS for Reading status Object
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (PEF Object), of handle 2 (Personal Best object), of handle 3 (FEV1 Object) and of handle 5 (Reading status Object) to reverse the values to:
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_NU_VAL_OBS_SIMP for PEF Object
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_NU_VAL_OBS_SIMP for Personal Best Object
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_NU_VAL_OBS_SIMP for FEV1 Object
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_NU_VAL_OBS_BASIC_BIT_STRING for Reading status Object
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date (absolute-time-stamp) by a measurement data for every object.
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (Observed value defined for every object, then MDC_ATTR_TIME_STAMP_ABS). The observations should be reasonable PEF, Personal Best, FEV1 and Reading status values.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that the PHG under test uses l/min as the unit code for PEF and Personal best report, and it uses l as the unit code for FEV1 report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    | + +| | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-003 | | | | +| TP label | Special values. Not a number – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | PEF12; M | PersBest12; M | FEV1S12; M | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1) containing an observation value set to the value for NaN ([exponent 0, mantissa +( $2^{23} - 1$ ) = 0x007FFFFF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-004 | | | | +| TP label | Special values. Not a number – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | PEF20; C | PersBest20; C | FEV1S20; C | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1) containing an observation value set to the value for NaN ([exponent 0, mantissa +( $2^{23} - 1$ ) = 0x007FFFFF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurements are displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-005 | | | | +| TP label | Special values. Not at this resolution – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | PEF12; M | PersBest12; M | FEV1S12; M | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1)containing an observation value set to the value for NRes ([exponent 0, mantissa +( $2^{23}$ ) = 0x00800000]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurements are displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-006 | | | | +| TP label | Special values. Not at this resolution – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | PEF20; C | PersBest20; C | FEV1S20; C | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) bu it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1) containing an observation value set to the value for NRes ([exponent 0, mantissa +( $2^{23}$ ) = 0x00800000]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-007 | | | | +| TP label | Special values. Positive infinity – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | PEF12; M | PersBest12; M | FEV1S12; M | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**23 – 2) = 0x007FFFFE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-008 | | | | +| TP label | Special values. Positive infinity – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | | +| | Testable items | PEF20; C | PersBest20; C | FEV1S20; C | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**23 – 2) = 0x007FFFFE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-009 | | | +| TP label | Special values. Negative infinity – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | PEF12; M | PersBest12; M | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1) containing an observation value set to the value for negative infinity (–INFINITY, [exponent 0, mantissa -(2^{23} - 2) = 0x00800002]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-010 | | | +| TP label | Special values. Negative infinity – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | PEF20; C | PersBest20; C | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1) containing an observation value set to the value for negative infinity (–INFINITY, [exponent 0, mantissa -(2^{23} - 2) = 0x00800002]).
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-011 | | | +| TP label | Special values. Reserved – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | PEF12; M | PersBest12; M | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa $-(2^{23} - 1) = 0x00800001$ ]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-012 | | | +| TP label | Special values. Reserved – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | PEF20; C | PersBest20; C | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_018 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (0x0834). | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1(PEF), handle 2 (Personal Best) and handle 3 (FEV1) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{23} - 1) = 0x00800001]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/PF/BV-013 | | | +| TP label | Association procedure PHG PF | | | +| Coverage | Spec | [ISO/IEEE 11073-10421] | | +| | Testable items | PF_AssocResp1; M | PF_AssocResp2; M | +| | | PF_AssocResp4; M | PF_AssocResp5; M | +| | | PF_AssocResp7; M | PF_AssocResp8; M | +| | | PF_AssocResp10; M | PF_AssocResp11; M | +| | | | PF_AssocResp3; M | +| | | | PF_AssocResp6; M | +| | | | PF_AssocResp9; M | +| | | | PF_AssocResp12; M | +| Test purpose |

    Check that:

    In the association response message sent by the PHG:
    The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601.

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-proto-id-20601

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = 0x80000000)

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    The fields data-req-init-*-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_016 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '10000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16481
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an association response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
          • ▪ If association is rejected-permanent, field-value= 0x00 0x01.
          • ▪ If association is rejected-transient, field-value= 0x00 0x02.
          • ▪ If association is accepted-unknown-config, field-value= 0x00 0x03.
          • ▪ If association is rejected-no-common-protocol, field-value= 0x00 0x04.
          • ▪ If association is rejected-no-common-parameter, field-value= 0x00 0x05.
          • ▪ If association is rejected-unknown = 0x00 0x06.
          • ▪ If association is rejected-unauthorized, field-value= 0x00 0x07.
          • ▪ If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08.
      3. c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id))
      4. d. data-proto-id
        • field-type = DataProtoId
        • field-length = 2 bytes
    | + +field-value= 0x50 0x79 (20601) + +#### e. protocol-version + +field-type = Protocol Version + +field-length = 4 bytes (BITS-32) + +field-value= 0x80 0x00 0x00 0x00 + +#### f. encoding-rules + +field-type = EncodingRules + +field-length = 2 bytes (BITS-16) + +field-value= depends on the encoding rules supported/selected, but only one can be supported at a time + +#### g. nomenclature version + +field-type = NomenclatureVersion + +field-length = 4 bytes (BITS-32) + +field-value= Bit 0 must be set (nom-version1) + +#### h. functional units + +field-type = FunctionalUnits + +field-length = 4 bytes (BITS-32) + +field-value = + +- Bit 0 must be 0 +- Bits 1 and 2 may be set +- The rest of the bits must not be set + +#### i. system type + +field-type = SystemType + +field-length = 4 bytes (BITS-32) + +field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) + +#### j. system-id + +field-type = OCTET STRING + +field-length = 8 bytes + +field-value = (EUI-64 manufacturer and device) + +#### k. dev-config-id + +field-type = ConfigId + +field-length = 2 bytes + +field-value = 0x00 0x00 (manager-config-response) + +#### l. data-req-mode-flags (DataReqModeCapab) + +field-type = DataReqModeFlags + +field-length = 2 bytes + +field-value = 0x00 0x00 + +PHG response to data-req-mode-flags is always 0. + +#### m. data-req-init-agent-count (DataReqModeCapab) + +field-type = INT-U8 + +field-length = 1 byte + +field-value = 0x00 + +#### n. data-req-init-manager-count (DataReqModeCapab) + +field-type = INT-U8 + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | field-length = 1 byte
    field-value = 0x00 | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. data-req-init-agent-count verification has been updated according to IEEE PHD errata. See http://continua.plugfest.com/show_bug.cgi?id=787 for further details. | + +### A.13 Subgroup 2.3.12: Body composition analyser (BCA) + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-000 | | | +| TP label | Configuration Event Report. Body Composition Analyser standard configuration 2000 | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x07D0 (BCA).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)
      If the result of the association response was "accepted-unknown-config"
    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x07D0.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = it must be the same as the invoke-id of the simulated PHD's message.
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    c. Obj-Handle:

    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = 0x00 0x00

    d. Event-time:

    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value: 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | The PHG can request Get MDS while they are in the Associated state. | + +| | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-001 | | +| TP label | Maximum APDU size: Body Composition Analyser | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 4; M | +| | Spec | [ISO/IEEE 11073-10420] | +| | Testable items | CommChar1; M | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the

    | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | +| Other PICS | | +| Initial condition | The PHG under test is in the Operating state. | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar.obs_scan_var:
        • Count = 2
        • Length = 7696
         ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(7670 bytes)..... 00'O     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)       attribute-value: 70     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    4. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-002 | | | +| TP label | Attribute-Value-Map. Order change | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 21; M | BodyHeight22; M | +| Test purpose |

    Check that:

    For [Standard-Configuration, Body Weight] the [Attribute-Value-Map] attribute shall be present and its value shall be MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS

    [AND]

    For [Standard-Configuration, Body Height] the [Attribute-Value-Map] attribute shall be present and its value shall be MDC_ATTR_NU_VAL_OBS_SIMP then

    | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_ABS.
    [AND]
    For [Standard-Configuration, Body Fat object] the [Attribute-Value-Map] attribute shall be present and its value shall be MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of:
      • • MDC_ATTR_NU_VAL_OBS_SIMP then MDC_ATTR_TIME_STAMP_ABS for Body Weight Object
      • • MDC_ATTR_NU_VAL_OBS_SIMP then MDC_ATTR_TIME_STAMP_ABS for Body Height Object
      • • MDC_ATTR_NU_VAL_OBS_SIMP then MDC_ATTR_TIME_STAMP_ABS for Body Fat Object
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Body Weight Object), of handle 2 (Body Height object) and of handle 3 (Body Fat Object) to reverse the values to:
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_NU_VAL_OBS_SIMP for Body Weight Object
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_NU_VAL_OBS_SIMP for Body Height Object
      • • MDC_ATTR_TIME_STAMP_ABS then MDC_ATTR_NU_VAL_OBS_SIMP for Body Fat Object
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date (absolute-time-stamp) by a measurement data for every object.
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (Observed value defined for every object, then MDC_ATTR_TIME_STAMP_ABS). The observations should be reasonable Body Weight, Body Height and Body Fat.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that the PHG under test uses kg as the unit code for Body Weight, it uses cm as the unit code for Body Height, and it uses % as the unit code for Body Fat report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-003 | | | +| TP label | Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 21;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration, Body Weight] the [Attribute-Value-Map] attribute shall be present and its value shall be MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS

    PHG accepts the measurements (fixed format event report) and shows them correctly when the unit-code is changed.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND C_MAN_BCA_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. (Body Weight Numeric standard configuration Unit code attribute is set to MDC_DIM_KILO_G) | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Body Weight Object) to set the values to: MDC_ATTR_NU_VAL_OBS_SIMP, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_ABS.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute, use pounds MDC_DIM_LB (1760).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_SIMP attribute.
    6. 6. The simulated PHD waits until it receives a confirmation.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement is displayed properly).
    • In steps 4 and 6, verify that the PHG under test uses pounds as the unit code for the measurement reports.
    | +| Notes | | + +| | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-004 | | +| TP label | Unit-Code Body Weight. Change from default kilograms to pounds – fixed format observation. | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | +| | Testable items | WeightNumClass 19; M | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_KILO_G. | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND C_MAN_BCA_001 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (Body Weight Object) to pounds nomenclature code MDC_DIM_LB (1760).
    2. The simulated PHD waits until it receives a confirmation.
    3. Send a confirmed fixed format event report using a measurement in pounds followed by date and time stamp.
    4. The simulated PHD waits until it receives a confirmation.
    5. The simulated PHD sends an association release request (normal).
    6. The simulated PHD waits until it receives an association release response.
    7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    9. The simulated PHD sends a fixed event report with an observation in kilograms followed by date and time stamp.
    10. The simulated PHD waits until it receives a confirmation.
    | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies pounds to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • In step 10, verify that the PHG under test is able to accept the data properly and applies kilograms to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-005 | | | +| TP label | Unit-Code Body Weight. Do not change from default kilograms to pounds – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 19; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_KILO_G. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND (NOT(C_MAN_BCA_001)) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 1 (Body Weight Object) to pounds nomenclature code MDC_DIM_LB (1760).
    2. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or until TO cer-mds expires.
    3. If the PHG has sent a confirmation in step 2, send a confirmed fixed format event report using a measurement in pounds followed by date and time stamp.
    4. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or TO cer-mds expires.
    5. If the PHG has sent a confirmation in step 4, ask to the operator if the measurements have been properly received and displayed.
    | | | +| Pass/Fail criteria |
    • In step 2, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • In step 4, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • In step 5, verify that measurements do not appear, or if they do appear, they are somehow designated as 'unsupported' data.
    | | | +| Notes | | | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-006 | | | +| TP label | Unit-Code Body Weight. Use default kilograms – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 19; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_KILO_G | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. Send a confirmed variable format event report using a measurement in kilograms.
    2. The simulated PHD waits until it receives a confirmation. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data properly and applies kilograms to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | +| Notes | | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-007 | | | +| TP label | Unit-Code Body Weight. Change from default kilograms to pounds – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 19; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_KILO_G | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND C_MAN_BCA_001 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. Send a confirmed variable format event report to set the unit code to pounds MDC_DIM_LB (1760) for handle 1 (Body Weight Object) and a measurement in pounds.
    2. The simulated PHD waits until it receives a confirmation.
    3. Send a second confirmed variable format event report with just a measurement in pounds (i.e., do not transmit the unit-code attribute in the event report).
    4. The simulated PHD waits until it receives a confirmation.
    5. The simulated PHD sends an association release request (normal).
    6. The simulated PHD waits until it receives an association release response. | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    7. The simulated PHD sends an association request using the same configuration that was used initially.

    8. If the PHG under test responds with association request response with "accepted-unknown-config", then

    • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
    • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.

    9. The simulated PHD sends a confirmed variable event report with an observation in kilograms followed by date and time stamp (i.e., do not send the unit-code attribute it should be set to kilograms by the standard configuration).

    10. The simulated PHD waits until it receives a confirmation.

    | +| Pass/Fail criteria |
    • • In steps 2 and 4, verify that the PHG under test is able to accept the data properly and applies pounds to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies kilograms to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-008 | | | +| TP label | Unit-Code Body Height. Change from default centimetres to inches – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | BodyHeight20; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Unit-Code] attribute shall be present

    The value of the [Unit-Code] attribute shall be MDC_DIM_CENTI_M.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND C_MAN_BCA_002 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 2 (Body Height Object) to inches nomenclature code MDC_DIM_INCH (1376).
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report using a measurement in inches followed by date and time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends an association release request (normal).
    6. 6. The simulated PHD waits until it receives an association release response.
    7. 7. The simulated PHD sends an association request using the same configuration that was used initially.
    8. 8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.

    9. The simulated PHD sends a fixed event report with an observation in centimetres followed by date and time stamp.

    10. The simulated PHD waits until it receives a confirmation.

    | +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies inches to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • In step 10, verify that the PHG under test is able to accept the data properly and applies centimetres to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-009 | | | +| TP label | Unit-Code Body Height. Do not change from default centimetres to inches – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | BodyHeight20; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_CENTI_M | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND (NOT(C_MAN_BCA_002)) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 2 (Body Height Object) to inches nomenclature code MDC_DIM_INCH (1376).
    2. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or until TO cer-mds expires.
    3. If the PHG has sent a confirmation in step 2, send a confirmed fixed format event report using a measurement in inches followed by date and time stamp.
    4. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or TO cer-mds expires.
    5. If the PHG has sent a confirmation in step 4, ask to the operator if the measurements have been properly received and displayed.
    | | | +| Pass/Fail criteria |
    • In step 2, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • In step 4, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • In step 5, verify that measurements do not appear, or if they do appear, they are somehow designated as 'unsupported' data.
    | | | +| Notes | | | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-010 | | | +| TP label | Unit-Code Body Height. Use default centimetres – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | BodyHeight20; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_CENTI_M | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. Send a confirmed variable format event report using a measurement in centimetres.
    2. The simulated PHD waits until it receives a confirmation. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data properly and applies centimetres to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | +| Notes | | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-011 | | | +| TP label | Unit-Code Body Height. Change from default centimetres to inches – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | BodyHeight20; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_CENTI_M | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND C_MAN_BCA_002 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. Send a confirmed variable format event report to set the unit code to inches MDC_DIM_INCH (1376) for handle 2 (Body Height Object) and a measurement in inches.
    2. The simulated PHD waits until it receives a confirmation.
    3. Send a second confirmed variable format event report with just a measurement in inches (i.e., do not transmit the unit-code attribute in the event report).
    4. The simulated PHD waits until it receives a confirmation.
    5. The simulated PHD sends an association release request (normal). | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 6. The simulated PHD waits until it receives an association release response.
    2. 7. The simulated PHD sends an association request using the same configuration that was used initially.
    3. 8. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    4. 9. The simulated PHD sends a confirmed variable event report with an observation in centimetres followed by date and time stamp (i.e., do not send the unit-code attribute it should be set to kilograms by the standard configuration).
    5. 10. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2 and 4, verify that the PHG under test is able to accept the data properly and applies inches to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 10, verify that the PHG under test is able to accept the data properly and applies centimetres to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-012 | | | +| TP label | Unit-Code Body Fat. Change from default % to kilograms/pounds – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | BodyFat21; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_PERCENT | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND C_MAN_BCA_003 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 3 (Body fat Object) to kilograms nomenclature code MDC_DIM_KILO_G (1731).
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report using a measurement in kilograms followed by date and time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 3 (Body fat Object) to pounds nomenclature code MDC_DIM_LB (1760).
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. Send a confirmed fixed format event report using a measurement in kilograms followed by date and time stamp.
    8. 8. The simulated PHD waits until it receives a confirmation.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    9. The simulated PHD sends an association release request (normal).

    10. The simulated PHD waits until it receives an association release response.

    11. The simulated PHD sends an association request using the same configuration that was used initially.

    12. If the PHG under test responds with association request response with "accepted-unknown-config", then

    • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
    • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.

    13. The simulated PHD sends a fixed event report with an observation in % followed by date and time stamp.

    14. The simulated PHD waits until it receives a confirmation.

    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies kilograms to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 8, verify that the PHG under test is able to accept the data properly and applies pounds to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 14, verify that the PHG under test is able to accept the data properly and applies % to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-013 | | | +| TP label | Unit-Code Body Fat. Do not change from default % to kilograms/pounds – fixed format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | BodyFat21; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Unit-Code] attribute shall be present

    The value of the [Unit-Code] attribute shall be MDC_DIM_PERCENT

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND (NOT(C_MAN_BCA_003)) | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Unit-Code of handle 3 (Body Fat Object) to kilograms nomenclature code MDC_DIM_KILO_G (1731).
    2. 2. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or until TO cer-mds expires.
    3. 3. If the PHG has sent a confirmation in step 2, send a confirmed fixed format event report using a measurement in inches followed by date and time stamp.
    4. 4. The simulated PHD waits until it receives a confirmation, roer message, abrt message, release association or rorj message or TO cer-mds expires.
    5. 5. If the PHG has sent a confirmation in step 4, ask to the operator if the measurements have been properly received and displayed.
    | +| Pass/Fail criteria |
    • • In step 2, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • • In step 4, verify that PHG sends a confirmation, or TOcer-mds expires, or PHG sends a roer message, abrt message, release association or rorj message.
    • • In step 5, verify that measurements do not appear, or if they do appear, they are somehow designated as 'unsupported' data.
    | +| Notes | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-014 | | | +| TP label | Unit-Code Body Fat. Use default % – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | BodyFat21; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_PERCENT | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. Send a confirmed variable format event report using a measurement in centimetres.
    2. 2. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data properly and applies centimetres to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | +| Notes | | | | + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-015 | +| TP label | Unit-Code Body Fat. Change from default % to kilograms/pounds – variable format observation | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| Coverage | Spec | [ISO/IEEE 11073-10420] | | | +| | Testable items | BodyFat21; M | | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_PERCENT | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 AND C_MAN_BCA_003 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. 1. Send a confirmed variable format event report to set the unit code to kilograms MDC_DIM_KILO_G (1731) for handle 3 (Body Fat Object) and a measurement in kilograms.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a second confirmed variable format event report with just a measurement in kilograms (i.e., do not transmit the unit-code attribute in the event report).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed variable format event report to set the unit code to pounds MDC_DIM_LB (1760) for handle 3 (Body Fat Object) and a measurement in pounds.
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. Send a second confirmed variable format event report with just a measurement in pounds (i.e., do not transmit the unit-code attribute in the event report).
    8. 8. The simulated PHD waits until it receives a confirmation.
    9. 9. The simulated PHD sends an association release request (normal).
    10. 10. The simulated PHD waits until it receives an association release response.
    11. 11. The simulated PHD sends an association request using the same configuration that was used initially.
    12. 12. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until it receives a confirmation from the confirmed configuration event report just sent.
    13. 13. The simulated PHD sends a confirmed variable event report with an observation in % followed by date and time stamp (i.e., do not send the unit-code attribute it should be set to kilograms by the standard configuration).
    14. 14. The simulated PHD waits until it receives a confirmation.
    | | | | +| Pass/Fail criteria |
    • • In steps 2 and 4, verify that the PHG under test is able to accept the data properly and applies kilograms to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In steps 6 and 8, verify that the PHG under test is able to accept the data properly and applies pounds to the observations (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    • • In step 14, verify that the PHG under test is able to accept the data properly and applies centimetres to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | | +| Notes | | | | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-016 | | | +| TP label | Special values. Not a number – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 21; M | BodyHeight22; M | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value for NaN ([exponent 0, mantissa +(2**23 –1) = 0x007FFFFFF]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-017 | | | +| TP label | Special values. Not a number – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 26; M | BodyHeight38; M | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value for NaN ([exponent 0, mantissa +(2**23 –1) = 0x007FFFFFF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|--------------| +| Notes | This test case has been considered as an implicit test case. | | | | +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-018 | | | | +| TP label | Special values. Not at this resolution – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | | +| | Testable items | WeightNumClass 21; M | BodyHeight22; M | BodyFat23; M | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value for NRes ([exponent 0, mantissa +(2**23) = 0x00800000]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|--------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-019 | | | | +| TP label | Special values. Not at this resolution – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | | +| | Testable items | WeightNumClass 26; M | BodyHeight38; M | BodyFat39; M | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value for NRes ([exponent 0, mantissa +(2**23) = 0x00800000]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|--------------| +| Notes | This test case has been considered as an implicit test case. | | | | +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-020 | | | | +| TP label | Special values. Positive infinity – fixed format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | | +| | Testable items | WeightNumClass 21; M | BodyHeight22; M | BodyFat23; M | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**23 -2) = 0x007FFFFE]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|--------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-021 | | | | +| TP label | Special values. Positive infinity – variable format | | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | | +| | Testable items | WeightNumClass 26; M | BodyHeight38; M | BodyFat39; M | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**23 -2) = 0x007FFFFE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | + +| | | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| | they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-022 | | | +| TP label | Special values. Negative infinity – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 21; M | BodyHeight22; M | +| Test purpose | Check that:
    The PHG receives a -INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value for negative infinity (-INFINITY, [exponent 0, mantissa -(2**23 -2) = 0x00800002]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-023 | | | +| TP label | Special values. Negative infinity – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 26; M | BodyHeight38; M | +| Test purpose | Check that:
    The PHG receives a -INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value for negative infinity (-INFINITY, [exponent 0, mantissa -(2**23 -2) = 0x00800002]). | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-024 | | | +| TP label | Special values. Reserved – fixed format | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 21; M | BodyHeight22; M | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value that is reserved (Reserved for future use, [exponent 0, mantissa $-(2^{23}-1) = 0x00800001$ ]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-025 | | | +| TP label | Special values. Reserved – variable format | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | WeightNumClass 26; M | BodyHeight38; M | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight), handle 2 (Body Height) and handle 3 (Body Fat) containing an observation with the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{23}-1) = 0x00800001]).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------| +| TP Id | TP/PLT/PHG/CLASS/BCA/BV-026 | | | +| TP label | Association procedure PHG BCA | | | +| Coverage | Spec | [ISO/IEEE 11073-10420] | | +| | Testable items | ManProcAsResp1; M | ManProcAsResp2; M | +| | | ManProcAsResp4; M | ManProcAsResp5; M | +| | | ManProcAsResp7; M | ManProcAsResp8; M | +| | | ManProcAsResp10; M | ManProcAsResp11; M | +| | | ManProcAsResp13; C | | +| Test purpose |

    Check that:

    In the association response message sent by the PHG:

    The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601.

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-protocol-id-20601

    [AND]

    The data-protocol-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version1 (i.e., protocol-version = 0x80000000)

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    The fields data-req-init-*-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_027 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '10000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16481
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an association response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
          • ▪ If association is rejected-permanent, field-value= 0x00 0x01.
          • ▪ If association is rejected-transient, field-value= 0x00 0x02.
          • ▪ If association is accepted-unknown-config, field-value= 0x00 0x03.
          • ▪ If association is rejected-no-common-protocol, field-value= 0x00 0x04.
          • ▪ If association is rejected -no-common-parameter, field-value= 0x00 0x05.
          • ▪ If association is rejected-unknown = 0x00 0x06.
          • ▪ If association is rejected-unauthorized, field-value= 0x00 0x07.
          • ▪ If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08.
      3. c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id))
      4. d. data-proto-id
        • field-type = DataProtoId
    | + +- field-length = 2 bytes +- field-value= 0x50 0x79 (20601) + +#### e. protocol-version + +- field-type = Protocol Version +- field-length = 4 bytes (BITS-32) +- field-value= 0x80 0x00 0x00 0x00 + +#### f. encoding-rules + +- field-type = EncodingRules +- field-length = 2 bytes (BITS-16) +- field-value= depends on the encoding rules supported/selected, but only one can be supported at a time + +#### g. nomenclature version + +- field-type = NomenclatureVersion +- field-length = 4 bytes (BITS-32) +- field-value= Bit 0 must be set (nom-version1) + +#### h. functional units + +- field-type = FunctionalUnits +- field-length = 4 bytes (BITS-32) +- field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set + +#### i. system type + +- field-type = SystemType +- field-length = 4 bytes (BITS-32) +- field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) + +#### j. system-id + +- field-type = OCTET STRING +- field-length = 8 bytes +- field-value = (EUI-64 manufacturer and device) + +#### k. dev-config-id + +- field-type = ConfigId +- field-length = 2 bytes +- field-value = 0x00 0x00 (manager-config-response) + +#### l. data-req-mode-flags (DataReqModeCapab) + +- field-type = DataReqModeFlags +- field-length = 2 bytes +- field-value = 0x00 0x00 +- PHG response to data-req-mode-flags is always 0. + +#### m. data-req-init-agent-count (DataReqModeCapab) + +- field-type = INT-U8 +- field-length = 1 byte +- field-value = 0x00 + +#### n. data-req-init-manager-count (DataReqModeCapab) + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| | field-type = INT-U8
    field-length = 1 byte
    field-value = 0x00 | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +### A.14 Subgroup 2.3.13: Basic electrocardiograph (ECG) + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-000 | | | +| TP label | Configuration Event Report. Basic ECG specialization/Heart Rate profile standard configuration 600 | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x0258 (HR).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)
      If the result of the association response was "accepted-unknown-config"
      1. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x0258.
      2. 4. The PHG under test must respond with:
        1. a. APDU Type
          • field-length = 2 bytes
          • field-value = 0xE7 0x00 (PrstApdu)
        2. b. Invoke-id
          • field-type = INT-U16
          • field-length = 2 bytes
          • field-value = it must be the same as the invoke-id of the simulated PHD's message.
        3. c. Obj-Handle:
          • field-type = HANDLE
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 2 bytes
    • field-value = 0x00

    d. Event-time:

    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value: 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | The PHG can request Get MDS while they are in the Associated state. | + +| | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-001 | | +| TP label | Maximum APDU size: Basic ECG specialization/Heart Rate profile without PM-Store | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 4;M | +| | Spec | [ISO/IEEE 11073-10406] | +| | Testable items | CommChar1; M | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | +| Other PICS | | +| Initial condition | The PHG under test is in the Operating state. | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 1248
         ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(1224 bytes)..... 00'0     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2636 (2646 (MDC_ATTR_NU_VAL_OBS_BASIC)       attribute-value: 79     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    4. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | +|-----------------|----------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-002 | | +| TP label | Maximum APDU size: Basic ECG specialization/ Simple ECG profile without PM-Store | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 4;M | +| | Spec | [ISO/IEEE 11073-10406] | +| | Testable items | CommChar1; M | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_030 | +| Other PICS | | +| Initial condition | The PHG under test is in the Operating state. | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar.obs_scan_var:
        • Count = 2
        • Length = 7136
         ObservationScan ::= {   obj-handle: 9   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(7112 bytes)..... 00'0     }   } } ObservationScan ::= {   obj-handle: 9   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2454 (MDC_ATTR_UNIT_CODE)       attribute-value: 2194 (MDC_DIM_MILLI_VOLT)     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a Confirmed variable event report with one attribute update.
    4. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | | +|-----------------|------------------------------------------------------------------------------|-----------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-003 | | | +| TP label | Maximum APDU size: Basic ECG Specialization/Heart Rate profile with PM-Store | | | +| Coverage | Spec | [[ISO/IEEE 11073-20601-2015A] and [[ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4;M | | +| | Spec | [[ISO/IEEE 11073-10406] | | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|--| +| | Testable items | CommChar1; M | | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_029 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test is in the Operating state. | | | | +| Test procedure |
    1. 1. The simulated PHG sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 64472
         ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(64448 bytes)..... 00'O     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)       attribute-value: 79     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a confirmed fixed format event report with one measurement.
    4. 4. Check the response of the PHG under test.
    | | | | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | | | | +| Notes | | | | | + +| | | | | | +|-----------------|---------------------------------------------------------------|---------------------------------------------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-004 | | | | +| TP label | Maximum APDU size: Basic ECG/Simple ECG profile with PM-Store | | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | | +| | Testable items | CommonCharac 4;M | | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| | Spec | [ISO/IEEE 11073-10406] | | +| | Testable items | CommChar1; M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_030 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 64472 
           ObservationScan ::= {   obj-handle: 9   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00 (64448 bytes)  00'O     }   } } ObservationScan ::= {   obj-handle: 9   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2454 (MDC_ATTR_UNIT_CODE)       attribute-value: 2194 (MDC_DIM_MILLI_VOLT)     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a Confirmed variable event report with one attribute update.
    4. 4. Check the response of the PHG under test.
    | | | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | | | +| Notes | | | | + +| | | | +|-----------------|--------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-005 | | +| TP label | Basic ECG Specialization/Heart Rate profile. Attribute-Value-Map. Order change | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--| +| | Testable items | HeartRate22; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_REL | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of:
      • MDC_ATTR_NU_VAL_OBS_BASIC then MDC_ATTR_TIME_STAMP_REL for Heart Rate Object
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Heart Rate Object) to reverse the values to:
      • MDC_ATTR_TIME_STAMP_REL then MDC_ATTR_NU_VAL_OBS_BASIC for Heart Rate Object
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date (relative-time-stamp) by a measurement data for Heart Rate Object.
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC then MDC_ATTR_TIME_STAMP_REL). The observations should be reasonable Heart Rate.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that the PHG under test uses beats/min as the unit code for Heart Rate (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | | | +| Notes | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-006 | | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Not a number – fixed format (Std Config 600) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | | +| | Testable items | HeartRate22; M | | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 600. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Heart Rate Object) containing an observation value with the value for NaN ([exponent 0, mantissa +(2**11 –1) = 0x07FF]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-007 | | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Not a number – variable format (Std Config 600) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | | +| | Testable items | HeartRate44; M | | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 600. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Heart Rate Object) containing an observation value set to the value for NaN ([exponent 0, mantissa +(2**11 –1) = 0x07FF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking
    | | | | + +| | | +|--------------|--------------------------------------------------------------| +| | the display area). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-008 | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Not at this resolution – fixed format (Std Config 600) | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | +| | Testable items | HeartRate22; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 600. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Heart Rate Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{11}) = 0x0800]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-009 | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Not at this resolution – variable format (Std Config 600) | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | +| | Testable items | HeartRate44; M | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 600. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Heart Rate Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{11}) = 0x0800]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-010 | | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Positive infinity – fixed format (Std Config 600) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | | +| | Testable items | HeartRate22; M | | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 600. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Heart Rate Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2^{11} - 2) = 0x07FE]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-011 | | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Positive infinity – variable format (Std Config 600) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | | +| | Testable items | HeartRate44; M | | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 600. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Heart Rate
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +( $2^{11}-2$ ) = 0x07FE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-012 | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Negative infinity – fixed format (Std Config 600) | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | +| | Testable items | HeartRate22; M | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 600. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Heart Rate Object) containing an observation value set to the value for negative infinity (–INFINITY, [exponent 0, mantissa –(2^{11}-2) = 0x0802]) and a time stamp.
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|----------------------|-------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-013 | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Negative infinity – variable format (Std Config 600) | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | +| | Testable items | HeartRate44; M | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | +| Other PICS | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 600. | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Heart Rate Object) containing an observation value set to the value for negative infinity (-\text{INFINITY}, [exponent 0, mantissa -(2^{11}-2) = 0x0802]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-014 | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Reserved – fixed format (Std Config 600) | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | +| | Testable items | HeartRate22; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 600. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Heart Rate Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-015 | | | +| TP label | Basic ECG Specialization/Heart Rate profile. Special values. Reserved – variable format (Std Config 600) | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | +| | Testable items | HeartRate44; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_029 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1701. | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Heart Rate Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa $-(2^{11}-1) = 0x0801$ ]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--------------------| +| TP Id | TP/PLT/PHG/CLASS/ECG/BV-016 | | | | +| TP label | Association procedure PHG ECG | | | | +| Coverage | Spec | [ISO/IEEE 11073-10406] | | | +| | Testable items | ManProcAsResp1; M | ManProcAsResp2; M | ManProcAsResp3; M | +| | | ManProcAsResp4; M | ManProcAsResp6; M | ManProcAsResp7; M | +| | | ManProcAsResp8; M | ManProcAsResp9; M | ManProcAsResp10; M | +| | | ManProcAsResp11; M | ManProcAsResp12; M | ManProcAsResp13; M | +| | | ManProcAsResp14; C | | | +| Test purpose |

    Check that:

    In the association response message sent by the PHG:

    The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601.

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-proto-id-20601

    [AND]

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version2 (i.e., protocol-version = 0x40000000)

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    | | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    The fields data-req-init-*-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND (C_MAN_OXP_029 OR C_MAN_OXP_030) | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '01000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16481
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an association response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
          • ▪ If association is rejected-permanent, field-value= 0x00 0x01.
          • ▪ If association is rejected-transient, field-value= 0x00 0x02.
          • ▪ If association is accepted-unknown-config, field-value= 0x00 0x03.
          • ▪ If association is rejected-no-common-protocol, field-value= 0x00 0x04.
          • ▪ If association is rejected-no-common-parameter, field-value= 0x00 0x05.
          • ▪ If association is rejected-unknown = 0x00 0x06.
          • ▪ If association is rejected-unauthorized, field-value= 0x00 0x07.
          • ▪ If association is rejected-unsupported-assoc-version, field-value= 0x00
    | + +0x08. + +- c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) +- d. data-proto-id + - field-type = DataProtoId + - field-length = 2 bytes + - field-value= 0x50 0x79 (20601) +- e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x40 0x00 0x00 0x00 +- f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time +- g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value= Bit 0 must be set (nom-version1) +- h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set +- i. system type + - field-type = SystemType + - field-length = 4 bytes (BITS-32) + - field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) +- j. system-id + - field-type = OCTET STRING + - field-length = 8 bytes + - field-value = (EUI-64 manufacturer and device) +- k. dev-config-id + - field-type = ConfigId + - field-length = 2 bytes + - field-value = 0x00 0x00 (manager-config-response) +- l. data-req-mode-flags (DataReqModeCapab) + - field-type = DataReqModeFlags + - field-length = 2 bytes + - field-value = 0x00 0x00 + - PHG response to data-req-mode-flags is always 0. +- m. data-req-init-agent-count (DataReqModeCapab) + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | field-type = INT-U8
    field-length = 1 byte
    field-value = 0x00
    n. data-req-init-manager-count (DataReqModeCapab) field-type = INT-U8
    field-length = 1 byte
    field-value = 0x00 | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +### A.15 Subgroup 2.3.14: International normalized ratio (INR) + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-000 | | | +| TP label | Association procedure PHG INR | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | ManProcAs 1;M | ManProcAs 2;M | +| | | ManProcAs 4;M | ManProcAs 5;M | +| | | ManProcAs 7;M | ManProcAs 8;M | +| | | ManProcAs 10;M | ManProcAs 11;M | +| Test purpose | Check that:
    The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601.
    [AND]
    In the DataProtoList structure element, the data protocol identifier shall be set to data-protocol-id-20601.
    [AND]
    The data-protocol-info field shall be filled in with a PhdAssociationInformation structure
    [AND]
    The version of the data exchange protocol shall be set to protocol-version 2
    [AND]
    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules
    [AND]
    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)
    [AND]
    The field functional-units shall have all bits reset except for those relating to a Test Association.
    [AND]
    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)
    [AND]
    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier
    [AND] | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    If the PHD supports only the INR specialization, data-req-init-agent-count shall be set to 0 and data-req-init-manager-count shall be set to 0.

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state. | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test, with the fields:
      • protocol-version = '01000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16440
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an association response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
          • ▪ If association is rejected-permanent, field-value= 0x00 0x01.
          • ▪ If association is rejected-transient, field-value= 0x00 0x02.
          • ▪ If association is accepted-unknown-config, field-value= 0x00 0x03.
          • ▪ If association is rejected-no-common-protocol, field-value= 0x00 0x04.
          • ▪ If association is rejected-no-common-parameter, field-value= 0x00 0x05.
          • ▪ If association is rejected-unknown = 0x00 0x06.
          • ▪ If association is rejected-unauthorized, field-value= 0x00 0x07.
          • ▪ If association is rejected-unsupported-assoc-version, field-value= 0x00 0x08.
      3. c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id))
      4. d. data-proto-id
        • field-type = DataProtoId
    | + +- field-length = 2 bytes +- field-value= 0x50 0x79 (20601) + +#### e. protocol-version + +- field-type = Protocol Version +- field-length = 4 bytes (BITS-32) +- field-value= 0x80 0x00 0x00 0x00 + +#### f. encoding-rules + +- field-type = EncodingRules +- field-length = 2 bytes (BITS-16) +- field-value= depends on the encoding rules supported/selected, but only one can be supported at a time + +#### g. nomenclature version + +- field-type = NomenclatureVersion +- field-length = 4 bytes (BITS-32) +- field-value= Bit 0 must be set (nom-version1) + +#### h. functional units + +- field-type = FunctionalUnits +- field-length = 4 bytes (BITS-32) +- field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set + +#### i. system type + +- field-type = SystemType +- field-length = 4 bytes (BITS-32) +- field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) + +#### j. system-id + +- field-type = OCTET STRING +- field-length = 8 bytes +- field-value = (EUI-64 manufacturer and device) + +#### k. dev-config-id + +- field-type = ConfigId +- field-length = 2 bytes +- field-value = 0x00 0x00 (manager-config-response) + +#### l. data-req-mode-flags (DataReqModeCapab) + +- field-type = DataReqModeFlags +- field-length = 2 bytes +- field-value = 0x00 0x00 +- PHG response to data-req-mode-flags is always 0. + +#### m. data-req-init-agent-count (DataReqModeCapab) + +- field-type = INT-U8 +- field-length = 1 byte +- field-value = 0x00 + +#### n. data-req-init-manager-count (DataReqModeCapab) + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| | field-type = INT-U8
    field-length = 1 byte
    field-value = 0x00 | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | Value for protocol-version has been modified according to [ISO/IEEE 11073-20601-2015A]. | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------------| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-001 | | | +| TP label | Configuration Event Report. INR monitor standard configuration 1800 | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | ConfProc 4;M | MDSEvents 2;M      ObjAccServ 5;M | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a "Remote Operation Response Confirmed Event Report" data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field .

    [AND]

    A PHG shall support both single-person and multi-person event reports.

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. The simulated PHD implements an INR monitor device specialization with standard configuration 1800. | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x07 0x08 (INR monitor – Std Config 1800)
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x07 0x08.
    4. 4. The PHG under test must respond with:
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. APDU Type

    • field-length = 2 bytes
    • field-value = 0xE7 0x00 (PrstApdu)

    b. Invoke-id

    • field-type = INT-U16
    • field-length = 2 bytes
    • field-value= it must be the same as the invoke-id of the simulated PHD's message.

    c. Obj-Handle:

    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = 0x00 0x00

    d. Event-time:

    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value: 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.

    b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.

    c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one INR measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | | + +| | | | +|-----------------|-----------------------------------------------------------------------|-------------------------| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-002 | | +| TP label | Configuration Event Report. Glucose Meter standard configuration 1801 | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------|----------------| +| | Testable items | ConfProc 4;M | MDSEvents 2;M | ObjAccServ 5;M | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | | +| | Testable items | ConfEventRep 18;M | | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a "Remote Operation Response Confirmed Event Report" data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field .

    [AND]

    A PHG shall support both single-person and multi-person event reports.

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | | +| Other PICS | C_MAN_OXP_085 | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. The simulated PHD implements an INR monitor device specialization with standard configuration 1801. | | | | +| Test procedure |
    1. 1. The simulated PHD sends an association request to the PHG under test with dev-config-id set to 0x07 0x09 (INR monitor – Std Config 1801).
    2. 2. The PHG under test responds with an association response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      If the result of the association response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x06 0xA5.
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = it must be the same as the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    d. Event-time:

    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value: 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value= MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same as config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in the Operating state the PHG is forced to enable the scanner object.

    Wait until the Operating state is reached in both cases.

    6. The simulated PHD sends a fixed event report with one INR measurement and other fixed event report with Control Solution measurement.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the association request with an "accepted" message or to the Configuration Event Report with an "accepted-config".
    • • The measurement is correctly presented.
    | +| Notes | | + +| | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-003 | | +| TP label | Maximum APDU size: INR monitor without PM-Store | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 4;M | +| | Spec | [ISO/IEEE 11073-10418C] | +| | Testable items | ComChar 2; M | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test is in the Operating state. | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar.obs_scan_var:
        • Count = 2
        • Length = 856
         ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(832 bytes)..... 00'O     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)       attribute-value: 1     }   } }
    2. 2. Check the response of the PHG under test.
    3. 3. The simulated PHD sends a confirmed fixed format event report with one measurement.
    4. 4. Check the response of the PHG under test.
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-004 | | +| TP label | Maximum APDU size: INR monitor with PM-Store | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 4;M | +| | Spec | [ISO/IEEE 11073-10418C] | +| | Testable items | ComChar 2; M | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on

    | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | apply to all APDUs regardless of whether a standard or extended configuration is being used. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 AND C_MAN_OXP_003 | +| Other PICS | | +| Initial condition | The PHG under test is in the Operating state. | +| Test procedure |

    1. The simulated PHD sends a Confirmed variable event report:

    a. ScanReportInfoVar. obs_scan_var:

    • Count = 2
    • Length = 64472
     ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....(64448 bytes)..... 00'O     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)       attribute-value: 1     }   } }

    2. Check the response of the PHG under test.

    3. The simulated PHD sends a confirmed fixed format event report with one measurement.

    4. Check the response of the PHG under test.

    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-005 | | | +| TP label | INR Attribute-Value-Map. Order change | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | INR 10; M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (INR Object) to reverse the values to: MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_NU_VAL_OBS_BASIC.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date first followed by an INR value.
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO). The observation should be a reasonable INR observation.
    12. 12. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that the PHG under test uses INR unit as the unit code for the measurement report (or reports the proper value after conversion to another unit code).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-006 | | | +| TP label | INR Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | INR 10;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_BO | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | +| Other PICS | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. (INR Numeric standard configuration Unit code attribute is set to MDC_DIM_INR) | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (INR Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute, use MDC_DIM_INR (6608).
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC attribute.
    6. 6. The simulated PHD waits until it receives a confirmation.
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement is displayed properly).
    • • In steps 4 and 6, verify that the PHG under test uses INR unit as the unit code for the measurement reports.
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-007 | | | +| TP label | INR Unit-Code. Use default INR units – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | INR 8;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_INR | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. Send a confirmed variable format event report using a measurement in INR unit.
    2. 2. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data properly and applies INR unit to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | + +| | | | | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|--|--|--|--| +| Notes | | | | | | | | +| TP Id | TP/PLT/PHG/CLASS/INR/BV-008 | | | | | | | +| TP label | Special values. Not a number – fixed format (Std Config 1800) | | | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | | | | | +| | Testable items | INR 10; M | | | | | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | | | | | +| Other PICS | | | | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (INR Object) containing an observation value with the value for NaN ([exponent 0, mantissa +(2**11 – 1) = 0x07FF]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | | | | | +| Notes | This test case has been considered as an implicit test case. | | | | | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|--|--| +| TP Id | | TP/PLT/PHG/CLASS/INR/BV-009 | | | +| TP label | Special values. Not a number – variable format (Std Config 1800) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | | +| | Testable items | INR 20; R | | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (INR Object) containing an observation value set to the value for NaN ([exponent 0, mantissa +(2**11 – 1) = 0x07FF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | | + +| | | +|--------------|--------------------------------------------------------------| +| | the display area). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-010 | | | +| TP label | Special values. Not at this resolution – fixed format (Std Config 1800) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | INR 10; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (INR Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{**11}) = 0x0800]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-011 | | | +| TP label | Special values. Not at this resolution – variable format (Std Config 1800) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | INR 20; R | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (INR Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{**11}) = 0x0800]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | + +| | | +|--------------|-----------------------------------------------------------------| +| | displayed in some form that indicates it is not a measurement). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-012 | | | | +| TP label | Special values. Positive infinity – fixed format (Std Config 1800) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | | +| | Testable items | INR 10; M | | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (INR Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 –2) = 0x07FE]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-013 | | | | +| TP label | Special values. Positive infinity – variable format (Std Config 1800) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | | +| | Testable items | INR 20; R | | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (INR Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2**11 –2) = 0x07FE]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-014 | | | +| TP label | Special values. Negative infinity – fixed format (Std Config 1800) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | INR 10; M | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (INR Object) containing an observation value set to the value for negative infinity (–INFINITY, [exponent 0, mantissa -(2^{11}-2) = 0x0802]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-015 | | | +| TP label | Special values. Negative infinity – variable format (Std Config 1800) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | INR 20; R | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (INR Object) containing an observation value set to the value for negative infinity (–INFINITY, [exponent 0, mantissa -(2^{11}-2) = 0x0802]).
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-016 | | | +| TP label | Special values. Reserved – fixed format (Std Config 1800) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | INR 10; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (INR Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa $-(2^{11}-1) = 0x0801$ ]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-017 | | | +| TP label | Special values. Reserved – variable format (Std Config 1800) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | INR 20; R | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (INR Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-018 | | | +| TP label | Control Calibration Attribute-Value-Map. Order change | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 7;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. 1. The simulated PHD sends a Control Solution confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation.
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Control Calibration Object) to reverse the values to: MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_NU_VAL_OBS_BASIC.
    4. 4. The simulated PHD waits until it receives a confirmation.
    5. 5. Send a confirmed fixed format event report with the date first followed by a control calibration value (in INR units since it is the standard configuration unit code).
    6. 6. The simulated PHD waits until it receives a confirmation.
    7. 7. The simulated PHD sends an association release request (normal).
    8. 8. The simulated PHD waits until there is an association release response.
    9. 9. The simulated PHD sends an association request using the same standard configuration that was used previously.
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration.
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_ATTR_TIME_STAMP_BO). The observation should be a reasonable INR units INR observation.
    12. The simulated PHD waits until it receives a confirmation. | +| Pass/Fail criteria |
    • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • In steps 2, 6 and 12 verify that the PHG under test uses INR units as the unit code for the measurement report (or reports the proper value after conversion to another unit code).
    • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may have occurred sometime in the past).
    • When automated, it is necessary to be careful about sending these messages back to back since the ability to look at things like an UI may require that there be pauses for operator verification.
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-019 | | | +| TP label | Control Calibration Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 7;M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (Control Calibration Numeric standard configuration Unit code attribute is set to MDC_DIM_INR). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Control Calibration Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_BO.
    2. The simulated PHD waits until it receives a confirmation.
    3. Send a confirmed fixed format event report with the new data layout. For the unit-code attribute, use MDC_DIM_INR (6608).
    4. The simulated PHD waits until it receives a confirmation.
    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC attribute.
    6. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the measurement and date are displayed properly).
    • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI, verify that the
    | | | + +| | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement is displayed properly).

    • In steps 4 and 6, verify that the PHG under test uses INR units as the unit code for the measurement reports.
    | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-020 | | | +| TP label | Control Calibration Unit-Code. Use default INR units – variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 6;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Unit-Code] attribute shall be present

    The value of the [Unit-Code] attribute shall be MDC_DIM_INR

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | +| Test procedure |
    1. Send a confirmed variable format event report using a measurement in INR units.
    2. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data properly and applies INR units to the observation (e.g., if there is a UI, verify that the measurement and date are displayed properly even if they are converted to a different set of units).
    | | | +| Notes | | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-021 | | | +| TP label | Special values. Not a number – fixed format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 7; M | | +| Test purpose |

    Check that:

    The PHG receives a NaN value (fixed format event report) but it does not use this value.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1801. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Calibration Object) containing an observation value with the value for NaN ([exponent 0, mantissa +(2**11 –1) = 0x07FF]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-022 | | | +| TP label | Special values. Not at this resolution – fixed format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 7; M | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1801. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Calibration Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{11}) = 0x0800]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-023 | | | +| TP label | Special values. Positive infinity – fixed format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 7; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1801. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Calibration Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2^{11} - 2) = 0x07FE]) and a time stamp.
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-024 | | | +| TP label | Special values. Negative infinity – fixed format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 7; M | | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1801. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Calibration Object) containing an observation value set to the value for negative infinity (–INFINITY, [exponent 0, mantissa $-(2^{11}-2) = 0x0802$ ]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-025 | | | +| TP label | Special values. Reserved – fixed format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 7; M | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1801. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 2 (Control Calibration | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa $-(2^{11} - 1) = 0x0801$ ]) and a time stamp.
    2. The simulated PHD waits until it receives a confirmation from the PHG under test. | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-026 | | | +| TP label | Special values. Not a number – variable format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 13; R | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1801. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Calibration Object) containing an observation value set to the value for NaN ([exponent 0, mantissa +(2^{11} - 1) = 0x07FF]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-027 | | | +| TP label | Special values. Not at this resolution – variable format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 13; R | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1801. | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Calibration Object) containing an observation value set to the value for NRes ([exponent 0, mantissa -(2^{11}) = 0x0800]).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-028 | | | +| TP label | Special values. Positive infinity – variable format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 13; R | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1801. | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Calibration Object) containing an observation value set to the value for positive infinity (+INFINITY, [exponent 0, mantissa +(2^{11} - 2) = 0x07FE]).
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-029 | | | +| TP label | Special values. Negative infinity – variable format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 13; R | | +| Test purpose | Check that:
    The PHG receives a -INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | configuration 1801. | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Calibration Object) containing an observation value set to the value for negative infinity (-\text{INFINITY}, [exponent 0, mantissa -(2^{11}-2) = 0x0802]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/INR/BV-030 | | | +| TP label | Special values. Reserved – variable format (Std Config 1801) | | | +| Coverage | Spec | [ISO/IEEE 11073-10418C] | | +| | Testable items | CtrlCal 13; R | | +| Test purpose |

    Check that:

    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_067 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1801. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 2 (Control Calibration Object) containing an observation value set to the value for reserved (Reserved for future use, [exponent 0, mantissa -(2^{11}-1) = 0x0801]).
    2. The simulated PHD waits until it receives a confirmation from the PHG under test.
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI, verify that the measurement is displayed in some form that indicates it is not a measurement).
    | | | +| Notes | This test case has been considered as an implicit test case. | | | + +### A.16 Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + +| | | | | +|-----------------|---------------------------------|------------------------|----------------| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-000 | | | +| TP label | Association procedure PHG SABTE | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | +| | Testable items | ManProcAs 1;M | ManProcAs 2;M | +| | | ManProcAs 4;M | ManProcAs 5;M | +| | | ManProcAs 7;M | ManProcAs 8;M | +| | | ManProcAs 10;M | ManProcAs 11;M | +| | | | ManProcAs 3;M | +| | | | ManProcAs 6;M | +| | | | ManProcAs 9;M | +| | | | ManProcAs 12;M | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    The result field shall be set to an appropriate response from those defined in ISO/IEEE P11073-20601.

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-protocol-id-20601.

    [AND]

    The data-protocol-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version 2

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    If the PHD supports only the SABTE specialization, data-req-init-agent-count shall be set to 0 and data-req-init-manager-count shall be set to 0.

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | +| Other PICS | | +| Initial condition | The PHG is the Unassociated state. | +| Test procedure |
    1. 1. Simulated PHD sends an Association Request to the PHG under test, with the fields:
      • protocol-version = '01000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16440
      • data-rep-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
    | + +- option-list.length= 0 + +2. The PHG under test sends an Association Response. The fields of interest are: + +- a. APDU Type + - field-length = 2 bytes + - field-value = 0xE3 0x00 (AareApdu) +- b. Result + - field-type = AssociateResult + - field-length = 2 bytes + - field-value = One of the following: + - If association is accepted, field-value= 0x00 0x00. + - If association is rejected-permanent, field-value= 0x00 0x01. + - If association is rejected-transient, field-value= 0x00 0x02. + - If association is accepted-unknown-config, field-value= 0x00 0x03. + - If association is rejected-no-common-protocol, field-value= 0x00 0x04. + - If association is rejected -no-common-parameter, field-value= 0x00 0x05. + - If association is rejected –unknown = 0x00 0x06. + - If association is rejected -unauthorized, field-value= 0x00 0x07. + - If association is rejected –unsupported-assoc-version, field-value= 0x00 0x08. +- c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) +- d. data-proto-id + - field-type = DataProtoId + - field-length = 2 bytes + - field-value= 0x50 0x79 (20601) +- e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x80 0x00 0x00 0x00 +- f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value= depends on the encoding rules supported/selected, but only one can be supported at a time +- g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value= Bit 0 must be set (nom-version1) +- h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    i. system type

    • field-type = SystemType
    • field-length = 4 bytes (BITS-32)
    • field-value = 0x80 0x00 0x00 0x00 (sys-type-manager)

    j. system-id

    • field-type = OCTET STRING
    • field-length = 8 bytes
    • field-value = ( EUI-64 manufacturer and device )

    k. dev-config-id

    • field-type = ConfigId
    • field-length = 2 bytes
    • field-value = 0x00 0x00 (manager-config-response)

    l. data-req-mode-flags (DataReqModeCapab)

    • field-type = DataReqModeFlags
    • field-length = 2 bytes
    • field-value = 0x00 0x00
    • PHG response to data-req-mode-flags is always 0.

    m. data-req-init-agent-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00

    n. data-req-init-manager-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | [AT4wireless] Value for protocol-version has been modified according to 20601-2015A. | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-001 | | | +| TP label | Configuration Event Report. SABTE standard configuration 2400 | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | +| | Testable items | ConfProc 4;M | MDSEvents 2;M | +| | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a "Remote Operation Response Confirmed Event Report" data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field .

    [AND]

    A PHG shall support both single-person and multi-person event reports.

    | | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | +| Other PICS | C_MAN_OXP_085 | +| Initial condition | The simulated PHD and the PHG under test are the Unassociated state. The simulated PHD implements a SABTE device specialization with Standard Configuration 2400 | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x09 0x60 (SABTE – Std Config 2400)
    2. 2. The PHG under test responds an Association Response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      IF the result of the Association Response was "accepted-unknown-config"

    3. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x07 0x08
    4. 4. The PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value= it must be the same that the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value: 0xXX 0xXX
      5. e. Event-type:
        1. field-length = 2 bytes
        2. field-value= MDC_NOTI_CONFIG
      6. f. The following six bytes indicate:
        1. Event-replay-info.length (2 bytes)
    | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in the Operating state the PHG is forced to enable the scanner object

    Wait until the Operating state is reached in both cases

    6. The simulated PHD sends a fixed event report with one SABTE measurement

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config"
    • • The measurement is correctly presented
    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-002 | | | +| TP label | Maximum APDU size: SABTE | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4;M | | +| | Spec | [ISO/IEEE 11073-10424] | | +| | Testable items | ComChar 2; M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 64472
         ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 
     AVA-Type ::= {     attribute-id: 61441     attribute-value: '00 (64448 bytes) 00'O     } } } ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 2636 (MDC_ATTR_NU_VAL_OBS_BASIC)             attribute-value: 1         }     } }
    1. 2. Check the response of the PHG under test
    2. 3. Simulated PHD sends a confirmed fixed format event report with one measurement.
    3. 4. Check the response of the PHG under test
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report"
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report"
    | +| Notes | | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-003 | | | +| TP label | Attribute-Value-Map. Order change | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | +| | Testable items | DPU 10; M | DFG 10; M | +| | | TherMode 8; M | DevMode 8; M | +| Test purpose |

    Check that:

    For [Standard-Configuration, Duration of Patient Use] the [Attribute-Value-Map] attribute shall be present and its value shall be MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO

    [AND]

    For [Standard-Configuration, Duration of Flow Generation] the [Attribute-Value-Map] attribute shall be present and its value shall be MDC_ATTR_NU_VAL_OBS_SIMP then MDC_ATTR_TIME_STAMP_BO.

    [AND]

    For [Standard-Configuration, Device Mode Set] the [Attribute-Value-Map] attribute shall be present and its value shall be MDC_ATTR_ENUM_OBS_VAL_SIMP_OID then MDC_ATTR_TIME_STAMP_BO.

    [AND]

    For [Standard-Configuration, Therapy Mode Set] the [Attribute-Value-Map] attribute shall be present and its value shall be MDC_ATTR_ENUM_OBS_VAL_SIMP_OID then MDC_ATTR_TIME_STAMP_BO.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | +| Other PICS | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report with that matches the Attribute-Value-Map order of:
      1. a. MDC_ATTR_NU_VAL_OBS_BASIC then MDC_ATTR_TIME_STAMP_BO for Duration of Patient Use Object
      2. b. MDC_ATTR_NU_VAL_OBS_SIMP then MDC_ATTR_TIME_STAMP_BO for Duration of Flow Generation Object
      3. c. MDC_ATTR_ENUM_OBS_VAL_SIMP_OID, then MDC_ATTR_TIME_STAMP_BO for Device Mode Set
      4. d. MDC_ATTR_ENUM_OBS_VAL_SIMP_OID, then MDC_ATTR_TIME_STAMP_BO for Therapy Mode Set.
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Duration of Patient Use) Object) handle 2 (Duration of Flow Generation Object), handle 3 (Device Mode Set Object) and handle 4 (Therapy Mode Set Object) to reverse the values to:
      1. a. MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_NU_VAL_OBS_BASIC for Duration of Patient Use Object.
      2. b. MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_NU_VAL_OBS_SIMP for Duration of Flow Generation Object.
      3. c. MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_SIMP_OID for Device Mode Set Object.
      4. d. MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_SIMP_OID for Therapy Mode Set Object.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. Send a confirmed fixed format event report with the date first followed by a value for every object.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then
      • • The simulated PHD sends the confirmed configuration event report with the standard configuration
      • • The simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (Observed value defined for every object, then MDC_ATTR_TIME_STAMP_BO). The observation should be reasonable Duration of Patient Use, Duration of Flow Generation, Device Mode Set and Therapy Mode Set observations.
    12. 12. The simulated PHD waits until it receives a confirmation
    | +| Pass/Fail criteria |
    • • In Step 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In Step 2, 6 and 12 verify the PHG under test uses minutes as the unit-code for Duration of Patient Use and Duration of Flow Generation measurement reports (or reports the proper value after convert to another unit-code)
    • • In Step 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation's time stamp (i.e., the actual observation may
    | + +| | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    have occurred sometime in the past).

    • When automated, need to be careful about just sending these messages back to back since the ability to look at things like a UI may need there to be pauses for operator verification.
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-004 | | | +| TP label | Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | +| | Testable items | DPU 10;M | | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. (Duration of Patient Use Numeric standard configuration Unit code attribute is set to MDC_DIM_MIN) | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Duration of Patient Use Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_BO.
    2. The simulated PHD waits until it receives a confirmation
    3. Send a confirmed fixed format event report with the new data layout. For unit-code Attribute, use MDC_DIM_MIN (2208).
    4. The simulated PHD waits until it receives a confirmation
    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC Attribute.
    6. The simulated PHD waits until it receives a confirmation.
    | | | +| Pass/Fail criteria |
    • In Step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • In Step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    • In Step 4 and 6, verify the PHG under test uses Duration of Patient Use unit as the unit-code for the measurement reports
    | | | +| Notes | | | | + +| | | | | +|-----------------|--------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-005 | | | +| TP label | Unit-Code Duration of Patient Use. Use default minutes - variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|--|--| +| | Testable items | DPU 8;M | | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MIN | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure | 1. Send a confirmed variable format event report using a measurement in minutes
    2. The simulated PHD waits until it receives a confirmation | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data properly and applies minutes to the observation (e.g., if there is a UI verify the measurement and date are displayed properly even if they are converted to a different set of units). | | | | +| Notes | | | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-006 | | | | +| TP label | Unit-Code Duration of Flow Generation. Use default minutes - variable format observation | | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | | +| | Testable items | DFG 8;M | | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MIN | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | | | +| Test procedure | 1. Send a confirmed variable format event report using a measurement in minutes.
    2. The simulated PHD waits until it receives a confirmation. | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data properly and applies minutes to the observation (e.g., if there is a UI verify the measurement and date are displayed properly even if they are converted to a different set of units). | | | | +| Notes | | | | | + +| | | | | | +|-----------------|---------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-007 | | | | +| TP label | Special values. Not a number - fixed format (Std Config 2400) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|--| +| | Testable items | DPU 10; M | DFG 10; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2400. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an observation value with the value for not a number (NaN (not a number) [exponent 0, mantissa +(2**11 -1) = 0x07FF for Duration of Patient Use], [exponent 0, mantissa +(2**23 -1) = 0x007FFFF for Duration of Flow Generation]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area). | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------|--| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-008 | | | | +| TP label | Special values. Not a number – variable format (Std Config 2400) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | | +| | Testable items | DPU 12; M | DFG 12; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2400. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an observation value with the value for not a number (NaN (not a number) [exponent 0, mantissa +(2**11 -1) = 0x07FF for Duration of Patient Use], [exponent 0, mantissa +(2**23 -1) = 0x007FFFF for Duration of Flow Generation]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area). | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------|--| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-009 | | | | +| TP label | Special values. Not at this resolution - fixed format (Std Config 2400) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | | +| | Testable items | DPU 10; R | DFG 10; R | | +| Test purpose | Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and PHG under test are in the Operating state using the standard configuration 2400. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an observation value set to the value for not at this resolution (NRes (not at this resolution) [exponent 0, mantissa -(2^{**11}) = 0x0800 for Duration of Patient Use], [exponent 0, mantissa -(2^{**23}) = 0x00800000 for Duration of Flow Generation])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------|--| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-010 | | | | +| TP label | Special values. Not at this resolution - variable format (Std Config 2400) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | | +| | Testable items | DPU 12; R | DFG 12; R | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2400. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an observation value set to the value for not at this resolution (NRes (not at this resolution) [exponent 0, mantissa -(2^{**11}) = 0x0800 for Duration of Patient Use], [exponent 0, mantissa -(2^{**23}) = 0x00800000 for Duration of Flow Generation])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------|--| +| Notes | This test case has been considered as an implicit test case. | | | | +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-011 | | | | +| TP label | Special values. Positive infinity - fixed format (Std Config 2400) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | | +| | Testable items | DPU 10; M | DFG 10; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2400. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an observation value set to the value for positive infinity (+INFINITY [exponent 0, mantissa +(2**11 -2) = 0x07FE for Duration of Patient Use], [exponent 0, mantissa +(2**23 -2) = 0x007FFFFE for Duration of Flow Generation]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------|--| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-012 | | | | +| TP label | Special values. Positive infinity - variable format (Std Config 2400) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | | +| | Testable items | DPU 12; R | DFG 12; R | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2400. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an observation value set to the value for positive infinity (+INFINITY [exponent 0, mantissa +(2**11 -2) = 0x07FE for Duration of Patient Use], [exponent 0, mantissa +(2**23 -2) = 0x007FFFFE for Duration of Flow Generation])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-013 | | | +| TP label | Special values. Negative infinity - fixed format (Std Config 2400) | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | +| | Testable items | DPU 10; M | DFG 10; M | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2400. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an observation value set to the value for negative infinity (– INFINITY [exponent 0, mantissa -(2^{11} - 2) = 0x0802 for Duration of Patient Use], [exponent 0, mantissa -(2^{23} - 2) = 0x00800002 for Duration of Flow Generation]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-014 | | | +| TP label | Special values. Negative infinity - variable format (Std Config 2400) | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | +| | Testable items | DPU 12; R | DFG 12; R | +| Test purpose | Check that:
    The PHG receives a –INFINITY value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2400. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | observation value set to the value for negative infinity (− INFINITY [exponent 0, mantissa $-(2^{11} - 2) = 0x0802$ for Duration of Patient Use], [exponent 0, mantissa $-(2^{23} - 2) = 0x00800002$ for Duration of Flow Generation]) | +| 2. | The simulated PHD waits until it receives a confirmation from the PHG under test | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-015 | | | +| TP label | Special values. Reserved - fixed format (Std Config 2400) | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | +| | Testable items | DPU 10; M | DFG 10; M | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2400. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an observation value set to the value for reserved (Reserved for future use [exponent 0, mantissa $-(2^{11} - 1) = 0x0801$ for Duration of Patient Use], [exponent 0, mantissa $-(2^{23} - 1) = 0x00800001$ for Duration of Flow Generation]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | | | +| Pass/Fail criteria | Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------| +| TP Id | TP/PLT/PHG/CLASS/SABTE/BV-016 | | | +| TP label | Special values. Reserved - variable format (Std Config 2400) | | | +| Coverage | Spec | [ISO/IEEE 11073-10424] | | +| | Testable items | DPU 12; R | DFG 12; R | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_069 | | | +| Other PICS | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 1800. | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report for handle 1 (Duration of Patient Use Object) and handle 2 (Duration of Flow Generation Object) containing an observation value set to the value for reserved (Reserved for future use [exponent 0, mantissa -(2^{11}-1) = 0x0801 for Duration of Patient Use], [exponent 0, mantissa -(2^{23}-1) = 0x00800001 for Duration of Flow Generation])
    2. 2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | +| Pass/Fail criteria | Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | +| Notes | This test case has been considered as an implicit test case. | + +### A.17 Subgroup 2.3.16: Continuous glucose monitor (CGM) + +| | | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-------------------| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-000 | | | | +| TP label | Association procedure PHG Continuous Glucose Monitor | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | ManProcAsCGM 1;M | ManProcAsCGM 2;M | ManProcAsCGM 3;M | +| | | ManProcAsCGM 4;M | ManProcAsCGM 5;M | ManProcAsCGM 6;M | +| | | ManProcAsCGM 7;M | ManProcAsCGM 8;M | ManProcAsCGM 9;M | +| | | ManProcAsCGM 10;M | ManProcAsCGM 11;M | ManProcAsCGM 12;M | +| Test purpose |

    Check that:

    The result field shall be set to an appropriate response from those defined in [ISO/IEEE 11073-20601-2016C].

    [AND]

    In the DataProtoList structure element, the data protocol identifier shall be set to data-protocol-id-20601

    [AND]

    The data-protocol-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version 2

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    | | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    If the PHD supports only the CGM specialization, data-req-init-agent-count shall be 0 and data-req-init-manager-count shall be 0

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | +| Other PICS | | +| Initial condition | The PHG is in the Unassociated state | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test, with the fields:
      • protocol-version = '01000000000000000000000000000000'B
      • encoding-rules= '1000000000000000'B
      • nomenclature-version = '10000000000000000000000000000000'B
      • functional-units = '00000000000000000000000000000000'B
      • system-type = '00000000100000000000000000000000'B
      • dev-config-id = 16440
      • data-req-mode-capab =
        • ▪ data_req_mode_flags= '0000000000000001'B
        • ▪ data_req_init_agent_count = 1
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. The PHG under test sends an Association Response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
      2. b. Result
        • field-type = AssociateResult
        • field-length = 2 bytes
        • field-value = One of the following:
          • ▪ If association is accepted, field-value= 0x00 0x00.
          • ▪ If association is rejected-permanent, field-value= 0x00 0x01.
          • ▪ If association is rejected-transient, field-value= 0x00 0x02.
          • ▪ If association is accepted-unknown-config, field-value= 0x00 0x03.
          • ▪ If association is rejected-no-common-protocol, field-value= 0x00 0x04.
          • ▪ If association is rejected -no-common-parameter, field-value= 0x00 0x05.
          • ▪ If association is rejected –unknown = 0x00 0x06.
          • ▪ If association is rejected -unauthorized, field-value= 0x00 0x07.
          • ▪ If association is rejected –unsupported-assoc-version, field-value= 0x00 0x08.
      3. c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id))
    | + +- d. data-proto-id + - field-type = DataProtoId + - field-length = 2 bytes + - field-value= 0x50 0x79 (20601) +- e. protocol-version + - field-type = Protocol Version + - field-length = 4 bytes (BITS-32) + - field-value= 0x40 0x00 0x00 0x00 +- f. encoding-rules + - field-type = EncodingRules + - field-length = 2 bytes (BITS-16) + - field-value = depends on the encoding rules supported/selected, but only one can be supported at a time +- g. nomenclature version + - field-type = NomenclatureVersion + - field-length = 4 bytes (BITS-32) + - field-value = Bit 0 must be set (nom-version1) +- h. functional units + - field-type = FunctionalUnits + - field-length = 4 bytes (BITS-32) + - field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set +- i. system type + - field-type = SystemType + - field-length = 4 bytes (BITS-32) + - field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) +- j. system-id + - field-type = OCTET STRING + - field-length = 8 bytes + - field-value = (EUI-64 manufacturer and device) +- k. dev-config-id + - field-type = ConfigId + - field-length = 2 bytes + - field-value = 0x00 0x00 (manager-config-response) +- l. data-req-mode-flags (DataReqModeCapab) + - field-type = DataReqModeFlags + - field-length = 2 bytes + - field-value = 0x00 0x00 + - PHG response to data-req-mode-flags is always 0. +- m. data-req-init-agent-count (DataReqModeCapab) + - field-type = INT-U8 + - field-length = 1 byte + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | field-value = 0x00
    n. data-req-init-manager-count (DataReqModeCapab)
    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-001 | | | +| TP label | Configuration Event Report. Continuous Glucose Monitor standard configuration | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | ConfProcCGM 4;M | MDSEventsCGM 2;M | +| | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a "Remote Operation Response Confirmed Event Report" data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A PHG shall support both single-person and multi-person event reports.

    [AND]

    A Continuous Glucose Monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104xx device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the Configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | The simulated PHD and the PHG under test are in the Unassociated state. The simulated PHD implements a Continuous Glucose Monitor device specialization with Standard Configuration (2500) | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x09 0xC4 (Continuous Glucose Monitor PHD – Std Config 2500)
    2. 2. The PHG under test responds an Association Response, the field of interest is:
      1. a. Result
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-type = INT-U16
    • field-length = 2 bytes
    • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

    IF the result of the Association Response was "accepted-unknown-config"

    1. 3. The simulated PHD sends a configuration event report with config-report-id set to 0x09 0xC4
    2. 4. The PHG under test must respond with:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = it must be the same that the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        • field-type = HANDLE
        • field-length = 2 bytes
        • field-value = 0x00 0x00
      4. d. Event-time:
        • field-type = INT-U32
        • field-length = 4 bytes
        • field-value = 0xXX 0xXX
      5. e. Event-type:
        • field-length = 2 bytes
        • field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicate:
        • Event-replay-info.length (2 bytes)
        • ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD's message
        • ConfigReportRsp.config-result: One of:
          • ▪ accepted-config: 0x00 0x00
    3. 5. IF C_MAN_OXP_085 THEN:
      1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
      3. c. Once in the Operating state the PHG is forced to enable the scanner object.

      Wait until the Operating state is reached in both cases

    4. 6. The simulated PHD sends a fixed event report with one CGM measurement.
    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config"
    • • The measurement is correctly presented
    | +| Notes | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-002_A | | | +| TP label | Maximum APDU size: Continuous Glucose Monitor without PM-Store | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4; M | | +| | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | ComCharCGM 2; M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |
    1. 1. The simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 856
         ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....( 832 bytes)..... 00'O     }   } }
    2. 2. Check the response of the PHG under test
    3. 3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    4. 4. Check the response of the PHG under test
    | | | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | | | + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------| +| |
    • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-002_B | | | +| TP label | Maximum APDU size: Continuous Glucose Monitor with PM-Store | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4; M | | +| | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | ComCharCGM 3; M | | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specializations the PHG supports. The buffer size limitations in this bullet and the next on apply to all APDUs regardless of whether a standard or extended configuration is being used.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 AND C_MAN_OXP_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test is in the Operating state. | | | +| Test procedure |
    1. The simulated PHD sends a Confirmed variable event report:
      1. ScanReportInfoVar.obs_scan_var:
        • Count = 2
        • Length = 5080
         ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 61441             attribute-value: '00.....( 5056 bytes)..... 00'O         }     } } ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 2636             (MDC_ATTR_NU_VAL_OBS_BASIC)             attribute-value: 100         }     } }
    2. Check the response of the PHG under test.
    3. The simulated PHD sends a Confirmed fixed event report with one measurement.
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 4. Check the response of the PHG under test. | +| Pass/Fail criteria |
    • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report"
    • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report"
    | +| Notes | | + +| | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-003 | | +| TP label | Glucose Attribute-Value-Map. Order change | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | +| | Testable items | Glucose 14; M | +| Test purpose |

    Check that:

    For [Standard-Configuration] the [Attribute-Value-Map] attribute SHALL BE PRESENT.

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC, then

    MDC_ATTR_TIME_STAMP_BO

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration. | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO
    2. The simulated PHD waits until it receives a confirmation
    3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Glucose Numeric Object) to reverse the values to MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_NU_VAL_OBS_BASIC.
    4. The simulated PHD waits until it receives a confirmation
    5. The simulated PHD sends a confirmed fixed format event report with the date first followed by a blood glucose value.
    6. The simulated PHD waits until it receives a confirmation
    7. The simulated PHD sends an Association Release Request (normal)
    8. The simulated PHD waits until there is a Association Release Response
    9. The simulated PHD sends an Association Request using the same standard configuration that was used previously
    10. If the PHG under test responds with association request response with "accepted-unknown-config", then:
      • Simulated PHD sends the confirmed configuration event report with the standard configuration
      • Simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO). The observation should be a reasonable blood glucose observation.
    12. The simulated PHD waits until it receives a confirmation
    | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • In step 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • In step 2, 6 and 12 verify that the PHG under test uses MDC_DIM_MILLI_G_PER_DL as the unit-code for the measurement report (or reports the proper value after convert to another unit-code)
    • In step 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation time stamp (i.e., the actual observation may have occurred sometime in the past).
    • When automated, need to be careful about just sending these messages back to back since the ability to look at things like an UI may need a pause for operator verification.
    | +| Notes | | + +| | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-004 | | +| TP label | Glucose Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | +| | Testable items | Glucose 14; M | +| Test purpose | Check that:
    For [Standard-Configuration] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | +| Other PICS | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (2500). (Glucose Numeric object [Unit-Code] attribute is set to MDC_DIM_MILLI_G_PER_DL) | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 1 (Glucose Numeric Object) to set the values to: MDC_ATTR_NU_VAL_OBS_BASIC, MDC_ATTR_UNIT_CODE, then MDC_ATTR_TIME_STAMP_BO.
    2. The simulated PHD waits until it receives a confirmation
    3. The simulated PHD sends a confirmed fixed format event report with the new data layout. For unit-code Attribute, use MDC_DIM_MILLI_G_PER_DL (2130).
    4. The simulated PHD waits until it receives a confirmation
    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_NU_VAL_OBS_BASIC Attribute.
    6. The simulated PHD waits until it receives a confirmation
    | | +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly).
    • In step 4 and 6, verify that the PHG under test uses MDC_DIM_MILLI_G_PER_DL as the unit-code for the measurement reports.
    | | +| Notes | | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-005 | | | +| TP label | Glucose Unit-Code. Use default Glucose units - variable format observation | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | Glucose 12; M | | +| Test purpose | Check that:
    For [Standard-Configuration] the [Unit-Code] attribute shall be present
    The value of the [Unit-Code] attribute shall be MDC_DIM_MILLI_G_PER_DL | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration (2500). | | | +| Test procedure | 1. Send a confirmed variable format event report using a measurement using MDC_DIM_MILLI_G_PER_DL units.
    2. The simulated PHD waits until it receives a confirmation | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data properly and applies MDC_DIM_MILLI_G_PER_DL unit to the observation (e.g., if there is a UI verify the measurement and date are displayed properly even if they are converted to a different set of units). | | | +| Notes | | | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-006 | | | +| TP label | Glucose Special values. Not a number - fixed format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | Glucose 14; M | | +| Test purpose | Check that:
    The PHG receives a NaN value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | +| Test procedure | 1. The simulated PHD sends a confirmed fixed event report for handle 1 (Glucose Numeric Object) containing an observation value with the value for not a number (NaN (not a number) [exponent 0, mantissa +(2**11 -1) = 0x07FF]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement such as "—" or by blanking the display area). | | | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| Notes | This test case has been considered as an implicit test case. | | | | +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-007 | | | | +| TP label | Glucose Special values. Not a number - variable format (Std Config) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | Glucose 18; M | | | +| Test purpose |

    Check that:
    The PHG receives a NaN value (variable format event report) but it does not use this value.

    | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Glucose Numeric Object) containing an observation value set to the value for not a number (NaN (not a number) [exponent 0, mantissa +(2^{11} -1) = 0x07FF])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement such as "—" or blanking the display area). | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-008 | | | | +| TP label | Glucose Special values. Not at this resolution - fixed format (Std Config) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | Glucose 14; M | | | +| Test purpose |

    Check that:
    The PHG receives NRes value (fixed format event report) but it does not use this value.

    | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Glucose Numeric Object) containing an observation value set to the value for not at this resolution (NRes (not at this resolution) [exponent 0, mantissa -(2^{11}) = 0x0800]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | | + +| | | +|--------------|--------------------------------------------------------------| +| Notes | This test case has been considered as an implicit test case. | +|--------------|--------------------------------------------------------------| + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-009 | | | +| TP label | Glucose Special values. Not at this resolution - variable format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | Glucose 18; M | | +| Test purpose | Check that:
    The PHG receives NRes value (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Glucose Numeric Object) containing an observation value set to the value for not at this resolution (NRes (not at this resolution) [exponent 0, mantissa -(2^{**}11) = 0x0800])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | +| Notes | This test case has been considered as an implicit test case. | | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-010 | | | +| TP label | Glucose Special values. Positive infinity - fixed format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | Glucose 14; M | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (fixed format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Glucose Numeric Object) containing an observation value set to the value for positive infinity (+INFINITY [exponent 0, mantissa +(2^{**}11 - 2) = 0x07FE]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | +| Pass/Fail criteria |
    • Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement).
    | | | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| Notes | This test case has been considered as an implicit test case. | | | | +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-011 | | | | +| TP label | Glucose Special values. Positive infinity - variable format (Std Config) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | Glucose 18; M | | | +| Test purpose | Check that:
    The PHG receives a +INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Glucose Numeric Object) containing an observation value set to the value for positive infinity (+INFINITY [exponent 0, mantissa +(2**11 -2) = 0x07FE])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail Criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-012 | | | | +| TP label | Glucose Special values. Negative infinity - fixed format (Std Config) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | Glucose 14; M | | | +| Test purpose | Check that:
    The PHG receives a -INFINITY value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Glucose Numeric Object) containing an observation value set to the value for negative infinity (-INFINITY [exponent 0, mantissa -(2**11 -2) = 0x0802]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| Notes | This test case has been considered as an implicit test case. | | | | +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-013 | | | | +| TP label | Glucose Special values. Negative infinity - variable format (Std Config) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | Glucose 18; M | | | +| Test purpose | Check that:
    The PHG receives a -INFINITY value (variable format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report for handle 1 (Glucose Numeric Object) containing an observation value set to the value for negative infinity (-INFINITY [exponent 0, mantissa -(2^{11}-2) = 0x0802])
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | | +| Notes | This test case has been considered as an implicit test case. | | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-014 | | | | +| TP label | Glucose Special values. Reserved - fixed format (Std Config) | | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | | +| | Testable items | Glucose 14; M | | | +| Test purpose | Check that:
    The PHG receives a Reserved for future use value (fixed format event report) but it does not use this value. | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed event report for handle 1 (Glucose Numeric Object) containing an observation value set to the value for reserved (Reserved for future use [exponent 0, mantissa -(2^{11}-1) = 0x0801]) and a time stamp
    2. The simulated PHD waits until it receives a confirmation from the PHG under test
    | | | | +| Pass/Fail criteria | Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the | | | | + +| | | +|--------------|--------------------------------------------------------------------------------| +| | measurement is displayed in some form that indicates it is not a measurement). | +| Notes | This test case has been considered as an implicit test case. | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/CGM/BV-015 | | | +| TP label | Glucose Special values. Reserved - variable format (Std Config) | | | +| Coverage | Spec | [ISO/IEEE 11073-10425] | | +| | Testable items | Glucose 18; M | | +| Test purpose | Check that:
    The PHG receives a "Reserved for future use value" (variable format event report) but it does not use this value. | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_073 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and the PHG under test are in the Operating state using the standard configuration 2500. | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report for handle 1 (Glucose Numeric Object) containing an observation value set to the value for reserved (Reserved for future use [exponent 0, mantissa $-(2^{11}-1)$ ] = 0x0801)
    2. The simulated PHD waits until it receives a confirmation from the PHG under test | | | +| Pass/Fail criteria | Verify that the PHG under test either reports an error or is able to accept the data, but does not use the values as if they were an actual measurement (e.g., if there is a UI verify the measurement is displayed in some form that indicates it is not a measurement). | | | +| Notes | This test case has been considered as an implicit test case. | | | + +### A.18 Subgroup 2.3.17: Power status monitor (PSM) + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-000 | | | +| TP label | Association procedure PHG Power Status Monitor | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | ManProcAsPSM 1;M
    ManProcAsPSM 4;M
    ManProcAsPSM 7;M
    ManProcAsPSM 10;M | ManProcAsPSM 2;M
    ManProcAsPSM 5;M
    ManProcAsPSM 8;M
    ManProcAsPSM 11;M | +| Test purpose | Check that:
    The result field shall be set to an appropriate response from those defined in IEEE Std 11073-20601.
    [AND]
    In the DataProtoList structure element, the data protocol identifier shall be set to data-protocol-20601
    [AND] | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    The data-proto-info field shall be filled in with a PhdAssociationInformation structure

    [AND]

    The version of the data exchange protocol shall be set to protocol-version 2 OR protocol-version 3

    [AND]

    The PHG shall respond with a single selected encoding rule that is supported by both PHD and PHG. The PHG shall support at least the MDER encoding rules

    [AND]

    The version of the nomenclature used shall be set to nom-version1 (i.e., nomenclature-version = 0x80000000)

    [AND]

    The field functional-units shall have all bits reset except for those relating to a Test Association.

    [AND]

    The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000)

    [AND]

    The System-Id field shall contain the unique system id of the PHG device, which shall be a valid EUI-64 type identifier

    [AND]

    The field dev-config-id shall be manager-config-response (0)

    [AND]

    The field data-req-mode-capab shall be 0

    [AND]

    If the agent supports only the PSM specialization, data-req-init-manager-count shall be 0 for standard configuration and data-req-init-agent-count shall be 1.

    | +| Applicability | C_MAN_OXP_000 AND (C_MAN_OXP_076 OR C_MAN_OXP_077) | +| Other PICS | | +| Initial condition | PHG is in the unassociated State | +| Test procedure |
    1. 1. Simulated PHD sends an Association Request to the PHG under test, with the fields:
      • protocol-version = '011100000000000000000000000000000000000000000000'B
      • encoding-rules= '10000000000000000'B
      • nomenclature-version = '1000000000000000000000000000000000000000000000000'B
      • functional-units = '000000000000000000000000000000000000000000000000'B
      • system-type = '0000000010000000000000000000000000000000'B
      • dev-config-id = 16440
      • data-req-mode-capab =
        • ▪ data_req_mode_flags= '000000000000000001'B
        • ▪ data_req_init_agent_count = 1 (for standard configuration)
        • ▪ data_req_init_manager_count = 0
      • option-list.length= 0
    2. 2. PHG under test sends an Association Response. The fields of interest are:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE3 0x00 (AareApdu)
    | + +#### b. Result + +- field-type = AssociateResult +- field-length = 2 bytes +- field-value = One of the following: + - If association is accepted, field-value= 0x00 0x00. + - If association is rejected-permanent, field-value= 0x00 0x01. + - If association is rejected-transient, field-value= 0x00 0x02. + - If association is accepted-unknown-config, field-value= 0x00 0x03. + - If association is rejected-no-common-protocol, field-value= 0x00 0x04. + - If association is rejected -no-common-parameter, field-value= 0x00 0x05. + - If association is rejected –unknown = 0x00 0x06. + - If association is rejected -unauthorized, field-value= 0x00 0x07. + - If association is rejected –unsupported-assoc-version, field-value= 0x00 0x08. + +#### c. selected-data-proto (DataProto: sequence of data-proto-id (DataProtoId) and data-proto-info(defined by data-proto-id)) + +#### d. data-proto-id + +- field-type = DataProtoId +- field-length = 2 bytes +- field-value= 0x50 0x79 (20601) + +#### e. protocol-version + +- field-type = Protocol Version +- field-length = 4 bytes (BITS-32) +- field-value= 0x40 0x00 0x00 0x00 OR 0x20 0x00 0x00 0x00 OR 0x60 0x00 0x00 0x00 + +#### f. encoding-rules + +- field-type = EncodingRules +- field-length = 2 bytes (BITS-16) +- field-value = depends on the encoding rules supported/selected, but only one can be supported at a time + +#### g. nomenclature version + +- field-type = NomenclatureVersion +- field-length = 4 bytes (BITS-32) +- field-value = Bit 0 must be set (nom-version1) + +#### h. functional units + +- field-type = FunctionalUnits +- field-length = 4 bytes (BITS-32) +- field-value = + - Bit 0 must be 0 + - Bits 1 and 2 may be set + - The rest of the bits must not be set + +#### i. system type + +- field-type = SystemType +- field-length = 4 bytes (BITS-32) +- field-value = 0x80 0x00 0x00 0x00 (sys-type-manager) + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    j. system-id

    • field-type = OCTET STRING
    • field-length = 8 bytes
    • field-value = (EUI-64 manufacturer and device)

    k. dev-config-id

    • field-type = ConfigId
    • field-length = 2 bytes
    • field-value = 0x00 0x00 (manager-config-response)

    l. data-req-mode-flags (DataReqModeCapab)

    • field-type = DataReqModeFlags
    • field-length = 2 bytes
    • field-value = 0x00 0x00
    • PHG response to data-req-mode-flags is always 0.

    m. data-req-init-agent-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00

    n. data-req-init-manager-count (DataReqModeCapab)

    • field-type = INT-U8
    • field-length = 1 byte
    • field-value = 0x00
    | +| Pass/Fail criteria | All checked values are as specified in the test procedure. | +| Notes | | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-001 | | | +| TP label | Configuration Event Report. Power Status Monitor standard configuration 2700 | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | ConfProcPSM 4;M | MDSEventsPSM 2;M | +| | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a "Remote Operation Response Confirmed Event Report" data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A Power Status Monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104zz device specialization

    | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.
    [AND]
    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD. | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | +| Other PICS | C_MAN_OXP_085 | +| Initial condition | Simulated PHD and PHG under test are in the unassociated state. Simulated PHD implements a Power Status Monitor device specialization with Standard Configuration (2700) | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x0A 0x8C (Power Status Monitor PHD – Std Config 2700)
    2. 2. PHG under test responds an Association Response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      IF the result of the Association Response was "accepted-unknown-config"

    3. 3. Simulated PHD sends a configuration event report with config-report-id set to 0x0A 0x8C
    4. 4. PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = it must be the same that the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value = 0xXX 0xXX
      5. e. Event-type:
        1. field-length = 2 bytes
        2. field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicate:
        1. Event-replay-info.length (2 bytes)
        2. ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD's message
        3. ConfigReportRsp.config-result: One of:
          • ▪ accepted-config: 0x00 0x00
    | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    5. IF C_MAN_OXP_085 THEN:

    • a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    • b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    • c. Once in Operating state PHG is forced to enable the scanner object.

    Wait until Operating state is reached in both cases

    6. Simulated PHD sends a variable event report for each Battery Status and Battery Capacity object.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config"
    • • The measurements are correctly presented
    | +| Notes | | + +| | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-002 | | +| TP label | Configuration Event Report. Power Status Monitor standard configuration 2701 | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | +| | Testable items | ConfProcPSM 4;M                      MDSEventsPSM 2;M | +| | Spec | [ISO/IEEE 11073-20601-2016C] | +| | Testable items | ConfEventRep 18;M | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a "Remote Operation Response Confirmed Event Report" data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A Power Status Monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104zz device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | +| Other PICS | C_MAN_OXP_085 | | +| Initial condition | Simulated PHD and PHG under test are in the unassociated state. Simulated PHD implements a Power Status Monitor device specialization with Standard Configuration (2701) | | +| Test procedure |

    1. The simulated PHD sends an Association Request to the PHG under test with dev-config-

    | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    id set to 0x0A 0x8C (Power Status Monitor PHD – Std Config 2701)

    1. 2. PHG under test responds an Association Response, the field of interest is:
      1. a. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unkown-config)

    IF the result of the Association Response was “accepted-unkown-config”

    1. 3. Simulated PHD sends a configuration event report with config-report-id set to 0x0A 0x8C
    2. 4. PHG under test must respond with:
      1. a. APDU Type
        • field-length = 2 bytes
        • field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = it must be the same that the invoke-id of the simulated PHD’s message.
      3. c. Obj-Handle:
        • field-type = HANDLE
        • field-length = 2 bytes
        • field-value = 0x00 0x00
      4. d. Event-time:
        • field-type = INT-U32
        • field-length = 4 bytes
        • field-value = 0xXX 0xXX
      5. e. Event-type:
        • field-length = 2 bytes
        • field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicate:
        • Event-replay-info.length (2 bytes)
        • ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD’s message
        • ConfigReportRsp.config-result: One of:
          • ▪ accepted-config: 0x00 0x00
    3. 5. IF C_MAN_OXP_085 THEN:
      1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
      3. c. Once in Operating state, PHG is forced to enable the scanner object.

    Wait until Operating state is reached in both cases

    1. 6. Simulated PHD sends a variable event report for each Battery Status and Battery Capacity object.
    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an “accepted” message or to the Configuration Event Report with an “accepted-config”
    | + +| | | +|--------------|--------------------------------------------------------------------------------------------| +| |
    • The measurements are correctly presented
    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-003 | | | +| TP label | Configuration Event Report. Power Status Monitor standard configuration 2702 | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | ConfProcPSM 4;M | MDSEventsPSM 2;M | +| | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a “Remote Operation Response Confirmed Event Report” data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A Power Status Monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104zz device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | Simulated PHD and PHG under test are in the unassociated state. Simulated PHD implements a Power Status Monitor device specialization with Standard Configuration (2702) | | | +| Test procedure |
    1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x0A 0x8C (Power Status Monitor PHD – Std Config 2702)
    2. PHG under test responds an Association Response, the field of interest is:
      1. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unkown-config)

    IF the result of the Association Response was “accepted-unkown-config”

    1. Simulated PHD sends a configuration event report with config-report-id set to 0x0A 0x8C
    2. PHG under test must respond with:
      1. APDU Type
        • field-length = 2 bytes
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-value = 0xE7 0x00 (PrstApdu)

    b. Invoke-id

    • field-type = INT-U16
    • field-length = 2 bytes
    • field-value = it must be the same that the invoke-id of the simulated PHD's message.

    c. Obj-Handle:

    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = 0x00 0x00

    d. Event-time:

    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value = 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in Operating state, PHG is forced to enable the scanner object.

    Wait until Operating state is reached in both cases

    6. Simulated PHD sends a variable event report for each Battery Status and Battery Capacity object.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config"
    • • The measurements are correctly presented
    | +| Notes | | + +| | | | | +|-----------------|------------------------------------------------------------------------------|------------------------|------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-004 | | | +| TP label | Configuration Event Report. Power Status Monitor standard configuration 2703 | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | ConfProcPSM 4;M | MDSEventsPSM 2;M | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--| +| | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a “Remote Operation Response Confirmed Event Report” data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A Power Status Monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104zz device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | Simulated PHD and PHG under test are in the unassociated state. Simulated PHD implements a Power Status Monitor device specialization with Standard Configuration (2703) | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x0A 0x8C (Power Status Monitor PHD – Std Config 2703)
    2. 2. PHG under test responds an Association Response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unkown-config)

      IF the result of the Association Response was “accepted-unkown-config”

    3. 3. Simulated PHD sends a configuration event report with config-report-id set to 0x0A 0x8C
    4. 4. PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = it must be the same that the invoke-id of the simulated PHD’s message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value = 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in Operating state, PHG is forced to enable the scanner object.

    Wait until Operating state is reached in both cases

    6. Simulated PHD sends a variable event report for each Battery Status and Battery Capacity object.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config"
    • • The measurements are correctly presented
    | +| Notes | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-005 | | | +| TP label | Configuration Event Report. Power Status Monitor standard configuration 2704 | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | ConfProcPSM 4;M | MDSEventsPSM 2;M | +| | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a "Remote Operation Response Confirmed Event Report" data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A Power Status Monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    A PHG that supports one (or more) of the ISO/IEEE 11073-104zz device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | +| Other PICS | C_MAN_OXP_085 | +| Initial condition | Simulated PHD and PHG under test are in the unassociated state. Simulated PHD implements a Power Status Monitor device specialization with Standard Configuration (2704) | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x0A 0x8C (Power Status Monitor PHD – Std Config 2704)
    2. 2. PHG under test responds an Association Response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      IF the result of the Association Response was “accepted-unknown-config”

    3. 3. Simulated PHD sends a configuration event report with config-report-id set to 0x0A 0x8C
    4. 4. PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = it must be the same that the invoke-id of the simulated PHD’s message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value = 0xXX 0xXX
      5. e. Event-type:
        1. field-length = 2 bytes
        2. field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicate:
        1. Event-replay-info.length (2 bytes)
        2. ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD’s message
        3. ConfigReportRsp.config-result: One of:
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. Once in Operating state PHG is forced to enable the scanner object.

    Wait until Operating state is reached in both cases

    6. Simulated PHD sends a variable event report for each Battery Status and Battery Capacity object.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an “accepted” message or to the Configuration Event Report with an “accepted-config”
    • • The measurements are correctly presented
    | +| Notes | | + +| | | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-006 | | | | | +| TP label | Configuration Event Report. Power Status Monitor standard configuration 2705 | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | | | +| | Testable items | ConfProcPSM 4;M | MDSEventsPSM 2;M | | | +| | Spec | [ISO/IEEE 11073-20601-2016C] | | | | +| | Testable items | ConfEventRep 18;M | | | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a “Remote Operation Response Confirmed Event Report” data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A Power Status Monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104zz device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | | | +| Other PICS | C_MAN_OXP_085 | | | | | +| Initial condition | Simulated PHD and PHG under test are in the unassociated state. Simulated PHD implements a Power Status Monitor device specialization with Standard Configuration (2705) | | | | | + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x0A 0x8C (Power Status Monitor PHD – Std Config 2705)
    2. 2. PHG under test responds an Association Response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unkown-config)

      IF the result of the Association Response was “accepted-unkown-config”

    3. 3. Simulated PHD sends a configuration event report with config-report-id set to 0x0A 0x8C
    4. 4. PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = it must be the same that the invoke-id of the simulated PHD's message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
        1. field-type = INT-U32
        2. field-length = 4 bytes
        3. field-value = 0xXX 0xXX
      5. e. Event-type:
        1. field-length = 2 bytes
        2. field-value = MDC_NOTI_CONFIG
      6. f. The following six bytes indicate:
        1. Event-replay-info.length (2 bytes)
        2. ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD's message
        3. ConfigReportRsp.config-result: One of:
          • ▪ accepted-config: 0x00 0x00
    5. 5. IF C_MAN_OXP_085 THEN:
      1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
      2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
      3. c. Once in Operating state PHG is forced to enable the scanner object.

      Wait until Operating state is reached in both cases

    6. 6. Simulated PHD sends a variable event report for each Battery Status and Battery Capacity object.
    | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • The PHG under test must respond either to the Association Request with an “accepted” message or to the Configuration Event Report with an “accepted-config”
    • The measurements are correctly presented
    | +| Notes | | + +| | | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------|--|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-007 | | | | | +| TP label | Configuration Event Report. Power Status Monitor standard configuration 2706 | | | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | | | +| | Testable items | ConfProcPSM 4;M | MDSEventsPSM 2;M | | | +| | Spec | [ISO/IEEE 11073-20601-2016C] | | | | +| | Testable items | ConfEventRep 18;M | | | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a “Remote Operation Response Confirmed Event Report” data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A Power Status Monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104zz device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | | | +| Other PICS | C_MAN_OXP_085 | | | | | +| Initial condition | Simulated PHD and PHG under test are in the unassociated state. Simulated PHD implements a Power Status Monitor device specialization with Standard Configuration (2706) | | | | | +| Test procedure |
    1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x0A 0x8C (Power Status Monitor PHD – Std Config 2706)
    2. PHG under test responds an Association Response, the field of interest is:
      1. Result
        • field-type = INT-U16
        • field-length = 2 bytes
        • field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      IF the result of the Association Response was “accepted-unknown-config”

    3. Simulated PHD sends a configuration event report with config-report-id set to 0x0A 0x8C
    4. PHG under test must respond with:
      1. APDU Type
    | | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-length = 2 bytes
    • field-value = 0xE7 0x00 (PrstApdu)

    b. Invoke-id

    • field-type = INT-U16
    • field-length = 2 bytes
    • field-value = it must be the same that the invoke-id of the simulated PHD's message.

    c. Obj-Handle:

    • field-type = HANDLE
    • field-length = 2 bytes
    • field-value = 0x00 0x00

    d. Event-time:

    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value = 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in Operating state, PHG is forced to enable the scanner object.

    Wait until Operating state is reached in both cases

    6. Simulated PHD sends a variable event report for each Battery Status and Battery Capacity object.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an “accepted” message or to the Configuration Event Report with an “accepted-config”
    • • The measurements are correctly presented
    | +| Notes | | + +| | | | | +|-----------------|------------------------------------------------------------------------------|------------------------|------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-008 | | | +| TP label | Configuration Event Report. Power Status Monitor standard configuration 2707 | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | ConfProcPSM 4;M | MDSEventsPSM 2;M | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--| +| | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | ConfEventRep 18;M | | +| Test purpose |

    Check that:

    The PHG shall respond to a configuration notification message using a “Remote Operation Response Confirmed Event Report” data message with an MDC_NOTI_CONFIG event using the ConfigReportRsp structure for the event-info field

    [AND]

    A Power Status Monitor PHG shall respond to an [MDS-Configuration-Event] using a [Confirmed] event report response.

    The Response shall include the event-reply-info [ConfigReportRsp]

    [AND]

    A PHG that supports one (or more) of the ISO/IEEE 11073-104zz device specialization standards shall be able to accept all the standard device configurations specified for the profiles listed in conformance Table 23 under Gen-4.

    [AND]

    Alternatively, the PHG may request the PHD to send the standard configuration in order to enter the configuring state and check attributes from the MDS object prior to final acceptance (or rejection) of the PHD.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | C_MAN_OXP_085 | | | +| Initial condition | Simulated PHD and PHG under test are in the unassociated state. Simulated PHD implements a Power Status Monitor device specialization with Standard Configuration (2707) | | | +| Test procedure |
    1. 1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x0A 0x8C (Power Status Monitor PHD – Std Config 2707)
    2. 2. PHG under test responds an Association Response, the field of interest is:
      1. a. Result
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00 (accepted) or 0x00 0x03 (accepted-unknown-config)

      IF the result of the Association Response was “accepted-unknown-config”

    3. 3. Simulated PHD sends a configuration event report with config-report-id set to 0x0A 0x8C
    4. 4. PHG under test must respond with:
      1. a. APDU Type
        1. field-length = 2 bytes
        2. field-value = 0xE7 0x00 (PrstApdu)
      2. b. Invoke-id
        1. field-type = INT-U16
        2. field-length = 2 bytes
        3. field-value = it must be the same that the invoke-id of the simulated PHD’s message.
      3. c. Obj-Handle:
        1. field-type = HANDLE
        2. field-length = 2 bytes
        3. field-value = 0x00 0x00
      4. d. Event-time:
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • field-type = INT-U32
    • field-length = 4 bytes
    • field-value = 0xXX 0xXX

    e. Event-type:

    • field-length = 2 bytes
    • field-value = MDC_NOTI_CONFIG

    f. The following six bytes indicate:

    • Event-replay-info.length (2 bytes)
    • ConfigReportRsp.config-report-id: it must be the same that config-report-id of the simulated PHD's message
    • ConfigReportRsp.config-result: One of:
      • ▪ accepted-config: 0x00 0x00

    5. IF C_MAN_OXP_085 THEN:

    1. a. The PHG under test moves to Configuring/Sending GetMDS substate and issues roiv-cmip-command with handle set to 0 (request for MDS object) and attribute-id-list set to 0 to indicate all attributes.
    2. b. The simulated PHD responds with a rors-cmip-get service message in which the attribute-list contains a list of all implemented attributes of the MDS object and the mds-time-mgr-set-time bit is not set.
    3. c. Once in Operating state, PHG is forced to enable the scanner object.

    Wait until Operating state is reached in both cases

    6. Simulated PHD sends a variable event report for each Battery Status and Battery Capacity object.

    | +| Pass/Fail criteria |
    • • The PHG under test must respond either to the Association Request with an "accepted" message or to the Configuration Event Report with an "accepted-config"
    • • The measurements are correctly presented
    | +| Notes | | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-009_A | | | +| TP label | Maximum APDU size: Power Status Monitor with Simple PSM profile | | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2016C] | | +| | Testable items | CommonCharac 4; M | | +| | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | ComCharPSM 2; M | SimplePSMProf 7; M | +| Test purpose |

    Check that:

    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.

    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specialization the PHG supports.

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | PHG under test is in Operating state | +| Test procedure | 1. Simulated PHD sends a Confirmed variable event report:
    a. ScanReportInfoVar. obs_scan_var:
    Count = 2
    Length = 900
     ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 61441             attribute-value: '00.....( 852 bytes)..... 00'O         }     } } ObservationScan ::= {     obj-handle: 1     attributes: AttributeList ::= {         AVA-Type ::= {             attribute-id: 2460 (MDC_ATTR_NU_CMPD_VAL_OBS)             attribute-value: 100% and 100 min remaining         }     } }
    2. Check the response of the PHG under test
    3. Simulated PHD sends a Confirmed variable event report with one measurement.
    4. Check the response of the PHG under test | +| Pass/Fail criteria |
    • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report".
    | +| Notes | Ntx is given by the formula $Ntx(i) = 28 + (102 + S) \times i$ , where "i" is the number of batteries and "S" is the maximally supported OCTET STRING.length for the Label-String attribute of the battery capacity object.
    Ntx with S = 12 is 940 octets for implementations supporting eight batteries. | + +| | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-009_B | | +| TP label | Maximum APDU size: Power Status Monitor with Advanced PSM profile | | +| Coverage | Spec | [ISO/IEEE 11073-20601-2016C] | +| | Testable items | CommonCharac 4; M | +| | Spec | [ISO/IEEE 11073-10427] | +| | Testable items | ComCharPSM 2; M      AdvPSMProf 9; M | +| Test purpose | Check that:
    If a PHG receives an APDU that is larger than the PHG's receive buffer, it shall reply with an error (roer) code of protocol-violation.
    The PHG's receive buffer shall be at least as large as the largest buffer specified in the specialization the PHG supports. | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_077 | +| Other PICS | | +| Initial condition | PHG under test is in Operating state | +| Test procedure |
    1. 1. Simulated PHD sends a Confirmed variable event report:
      1. a. ScanReportInfoVar. obs_scan_var:
        • Count = 2
        • Length = 1620
         ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 61441       attribute-value: '00.....( 1572 bytes)..... 00'O     }   } } ObservationScan ::= {   obj-handle: 1   attributes: AttributeList ::= {     AVA-Type ::= {       attribute-id: 2460 (MDC_ATTR_NU_CMPD_VAL_OBS)       attribute-value: 100% and 100 min remaining     }   } }
    2. 2. Check the response of the PHG under test
    3. 3. Simulated PHD sends a Confirmed variable event report with one measurement.
    4. 4. Check the response of the PHG under test
    | +| Pass/Fail criteria |
    • • In step 2 the PHG under test must respond with a "rors-cmip-confirmed-event-report."
    • • In step 4 the PHG under test must respond with a "rors-cmip-confirmed-event-report."
    | +| Notes |

    Ntx is given by the formula Ntx(i) = 28 + (102 + S) \times i, where "i" is the number of batteries and "S" is the maximally supported OCTET STRING.length for the Label-String attribute of the battery capacity object.

    Ntx with S = 12 is 1660 octets for implementations supporting sixteen batteries for this profile.

    | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-010 | | | +| TP label | Battery Status Attribute-Value-Map. Order change. Standard Configuration 2700. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose |

    Check that:

    For [Standard-Configurations 2700] the [Attribute-Value-Map] attribute SHALL BE PRESENT.

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO

    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | +| Other PICS | | +| Initial condition | The simulated PHD and PHG under test are in the Operating state using the standard configuration 2700 | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to reverse the values to MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed fixed format event report with the date first followed by a battery status value.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously (2700)
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then:
      • • Simulated PHD sends the confirmed configuration event report with the standard configuration 2700
      • • Simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO).
    12. 12. The simulated PHD waits until it receives a confirmation.
    13. 13. Repeat steps 1-12 for each Battery Status object.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation time stamp (i.e., the actual event may have occurred sometime in the past).
    | +| Notes | When automated, need to be careful about just sending these messages back to back since the ability to look at things like a UI may need a pause for operator verification. | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-011 | | | +| TP label | Battery Status Attribute-Value-Map. Order change. Standard Configuration 2701. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose | Check that:
    For [Standard-Configurations 2701] the [Attribute-Value-Map] attribute shall be present. | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | +| Other PICS | | +| Initial condition | The simulated PHD and PHG under test are in the Operating state using the standard configuration 2701 | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to reverse the values to MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed fixed format event report with the date first followed by a battery status value.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously (2701)
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then:
      • • Simulated PHD sends the confirmed configuration event report with the standard configuration 2701
      • • Simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO).
    12. 12. The simulated PHD waits until it receives a confirmation.
    13. 13. Repeat steps 1-12 for each Battery Status object.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation time stamp (i.e., the actual event may have occurred sometime in the past).
    | +| Notes | When automated, need to be careful about just sending these messages back to back since the ability to look at things like a UI may need a pause for operator verification. | + +| | | | | +|-----------------|--------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-012 | | | +| TP label | Battery Status Attribute-Value-Map. Order change. Standard Configuration 2702. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    For [Standard-Configurations 2702] the [Attribute-Value-Map] attribute SHALL BE PRESENT.
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | +| Other PICS | | +| Initial condition | The simulated PHD and PHG under test are in the Operating state using the standard configuration 2702 | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to reverse the values to MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed fixed format event report with the date first followed by a battery status value.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously (2702)
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then:
      • • Simulated PHD sends the confirmed configuration event report with the standard configuration 2702
      • • Simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO).
    12. 12. The simulated PHD waits until it receives a confirmation.
    13. 13. Repeat steps 1-12 for each Battery Status object.
    | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation time stamp (i.e., the actual event may have occurred sometime in the past).
    | +| Notes | When automated, need to be careful about just sending these messages back to back since the ability to look at things like an UI may need a pause for operator verification. | + +| | | | +|-----------------|--------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-013 | | +| TP label | Battery Status Attribute-Value-Map. Order change. Standard Configuration 2703. | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--|--| +| | Testable items | BattStatus 25; M | | | +| Test purpose |

    Check that:
    For [Standard-Configurations 2703] the [Attribute-Value-Map] attribute SHALL BE PRESENT.
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO

    | | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | | +| Other PICS | | | | | +| Initial condition | The simulated PHD and PHG under test are in the Operating state using the standard configuration 2702 | | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to reverse the values to MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed fixed format event report with the date first followed by a battery status value.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously (2703)
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then:
      • • Simulated PHD sends the confirmed configuration event report with the standard configuration 2703
      • • Simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO).
    12. 12. The simulated PHD waits until it receives a confirmation.
    13. 13. Repeat steps 1-12 for each Battery Status object.
    | | | | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation time stamp (i.e.,the actual event may have occurred sometime in the past).
    | | | | +| Notes | When automated, need to be careful about just sending these messages back to back since the ability to look at things like an UI may need a pause for operator verification. | | | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-014 | | | +| TP label | Battery Status Attribute-Value-Map. Order change. Standard Configuration 2704. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose |

    Check that:

    For [Standard-Configurations 2704] the [Attribute-Value-Map] attribute SHALL BE PRESENT.

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and PHG under test are in the Operating state using the standard configuration 2704 | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to reverse the values to MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed fixed format event report with the date first followed by a battery status value.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously (2704)
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then:
      • • Simulated PHD sends the confirmed configuration event report with the standard configuration 2704
      • • Simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO).
    12. 12. The simulated PHD waits until it receives a confirmation.
    13. 13. Repeat steps 1-12 for each Battery Status object.
    | | | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation time stamp (i.e., the actual event may have occurred sometime in the past).
    | | | +| Notes | When automated, need to be careful about just sending these messages back to back since | | | + +| | | +|--|--------------------------------------------------------------------------------------| +| | the ability to look at things like an UI may need a pause for operator verification. | +|--|--------------------------------------------------------------------------------------| + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-015 | | | +| TP label | Battery Status Attribute-Value-Map. Order change. Standard Configuration 2705. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose |

    Check that:

    For [Standard-Configurations 2705] the [Attribute-Value-Map] attribute SHALL BE PRESENT.

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and PHG under test are in the Operating state using the standard configuration 2705 | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to reverse the values to MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed fixed format event report with the date first followed by a battery status value.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously (2705)
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then:
      • • Simulated PHD sends the confirmed configuration event report with the standard configuration 2705
      • • Simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO).
    12. 12. The simulated PHD waits until it receives a confirmation.
    13. 13. Repeat steps 1-12 for each Battery Status object.
    | | | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation time stamp (i.e.,the actual event may have
    | | | + +| | | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | occurred sometime in the past). | +| Notes | When automated, need to be careful about just sending these messages back to back since the ability to look at things like a UI may need a pause for operator verification. | + +| | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-016 | | +| TP label | Battery Status Attribute-Value-Map. Order change. Standard Configuration 2706. | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | +| | Testable items | BattStatus 25; M | +| Test purpose |

    Check that:

    For [Standard-Configurations 2706] the [Attribute-Value-Map] attribute SHALL BE PRESENT.

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | +| Other PICS | | | +| Initial condition | The simulated PHD and PHG under test are in the Operating state using the standard configuration 2706 | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to reverse the values to MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed fixed format event report with the date first followed by a battery status value.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. The simulated PHD sends an Association Release Request (normal)
    8. 8. The simulated PHD waits until there is a Association Release Response
    9. 9. The simulated PHD sends an Association Request using the same standard configuration that was used previously (2706)
    10. 10. If the PHG under test responds with association request response with "accepted-unknown-config", then:
      • • Simulated PHD sends the confirmed configuration event report with the standard configuration 2706
      • • Simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. 11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO).
    12. 12. The simulated PHD waits until it receives a confirmation.
    13. 13. Repeat steps 1-12 for each Battery Status object.
    | | +| Pass/Fail criteria |
    • • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the
    | | + +| | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement and date are displayed properly).

    • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation time stamp (i.e., the actual event may have occurred sometime in the past).
    | +| Notes | When automated, need to be careful about just sending these messages back to back since the ability to look at things like an UI may need a pause for operator verification. | + +| | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-017 | | +| TP Label | Battery Status Attribute-Value-Map. Order change. Standard Configuration 2707. | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | +| | Testable items | BattStatus 25; M | +| Test purpose |

    Check that:

    For [Standard-Configurations 2707] the [Attribute-Value-Map] attribute SHALL BE PRESENT.

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO

    | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | +| Other PICS | | | +| Initial condition | The simulated PHD and PHG under test are in the Operating state using the standard configuration 2707 | | +| Test procedure |
    1. The simulated PHD sends a confirmed fixed format event report that matches the Attribute-Value-Map order of MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO
    2. The simulated PHD waits until it receives a confirmation
    3. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to reverse the values to MDC_ATTR_TIME_STAMP_BO, then MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR.
    4. The simulated PHD waits until it receives a confirmation
    5. The simulated PHD sends a confirmed fixed format event report with the date first followed by a battery status value.
    6. The simulated PHD waits until it receives a confirmation
    7. The simulated PHD sends an Association Release Request (normal)
    8. The simulated PHD waits until there is a Association Release Response
    9. The simulated PHD sends an Association Request using the same standard configuration that was used previously (2707)
    10. If the PHG under test responds with association request response with "accepted-unknown-config", then:
      • Simulated PHD sends the confirmed configuration event report with the standard configuration 2707
      • Simulated PHD waits until there is a confirmation to the configuration event report that was sent.
    11. The simulated PHD sends a fixed event report following the standard configuration attribute-value-format (MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO).
    12. The simulated PHD waits until it receives a confirmation.
    13. Repeat steps 1-12 for each Battery Status object.
    | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • In steps 2, 6 and 12 verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • In steps 2, 6 and 12 verify that if the PHG utilizes a date / time stamp, then the PHG uses a time stamp derived from the observation time stamp (i.e., the actual event may have occurred sometime in the past).
    | +| Notes | When automated, need to be careful about just sending these messages back to back since the ability to look at things like a UI may need a pause for operator verification. | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-018 | | | +| TP label | Battery Status Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map. Standard Configuration 2700. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose | Check that:
    For [Standard-Configurations 2700] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and PHG under test are in Operating State using the standard configuration (2700). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to set the values to: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, MDC_ATTR_ID_LABEL_STRING, then MDC_ATTR_TIME_STAMP_BO.
    2. The simulated PHD waits until it receives a confirmation
    3. The simulated PHD sends a confirmed fixed format event report with the new data layout.
    4. The simulated PHD waits until it receives a confirmation
    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR Attribute.
    6. The simulated PHD waits until it receives a confirmation
    7. Repeat steps 1-6 for each Battery Status Enumeration object
    | | | +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    | | | +| Notes | | | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-019 | | | +| TP label | Battery Status Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map. Standard Configuration 2701. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose |

    Check that:

    For [Standard-Configurations 2701] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and PHG under test are in Operating State using the standard configuration (2701). | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to set the values to: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, MDC_ATTR_ID_LABEL_STRING, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed fixed format event report with the new data layout.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR Attribute.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. Repeat steps 1-6 for each Battery Status Enumeration object (handle 4)
    | | | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    | | | +| Notes | | | | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-020 | | | +| TP label | Battery Status Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map. Standard Configuration 2702. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose |

    Check that:

    For [Standard-Configurations 2702] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO

    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | +| Other PICS | | +| Initial condition | The simulated PHD and PHG under test are in Operating State using the standard configuration (2702). | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to set the values to: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, MDC_ATTR_ID_LABEL_STRING, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed fixed format event report with the new data layout.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR Attribute.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. Repeat steps 1-6 for each Battery Status Enumeration object (handles 4 and 6)
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-021 | | | +| TP label | Battery Status Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map. Standard Configuration 2703. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose | Check that:
    For [Standard-Configurations 2703] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be
    MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and PHG under test are in Operating State using the standard configuration (2703). | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to set the values to: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, MDC_ATTR_ID_LABEL_STRING, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed fixed format event report with the new data layout.
    4. 4. The simulated PHD waits until it receives a confirmation
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR Attribute.

    6. The simulated PHD waits until it receives a confirmation

    7. Repeat steps 1-6 for each Battery Status Enumeration object (handles 4, 6 and 8)

    | +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-022 | | | +| TP label | Battery Status Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map. Standard Configuration 2704. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose |

    Check that:

    For [Standard-Configurations 2704] the [Attribute-Value-Map] attribute shall be present

    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO

    | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and PHG under test are in Operating state using the standard configuration (2704). | | | +| Test procedure |
    1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to set the values to: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, MDC_ATTR_ID_LABEL_STRING, then MDC_ATTR_TIME_STAMP_BO.
    2. The simulated PHD waits until it receives a confirmation
    3. The simulated PHD sends a confirmed fixed format event report with the new data layout.
    4. The simulated PHD waits until it receives a confirmation
    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR Attribute.
    6. The simulated PHD waits until it receives a confirmation
    7. Repeat steps 1-6 for each Battery Status Enumeration object (handles 4, 6, 8 and 10)
    | | | +| Pass/Fail criteria |
    • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    | | | +| Notes | | | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-023 | | | +| TP label | Battery Status Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map. Standard Configuration 2705. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose | Check that:
    For [Standard-Configurations 2705] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and PHG under test are in Operating State using the standard configuration (2705). | | | +| Test procedure | 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to set the values to: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, MDC_ATTR_ID_LABEL_STRING, then MDC_ATTR_TIME_STAMP_BO.
    2. The simulated PHD waits until it receives a confirmation
    3. The simulated PHD sends a confirmed fixed format event report with the new data layout.
    4. The simulated PHD waits until it receives a confirmation
    5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR Attribute.
    6. The simulated PHD waits until it receives a confirmation
    7. Repeat steps 1-6 for each Battery Status Enumeration object (handles 4, 6, 8, 10 and 12) | | | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    | | | +| Notes | | | | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-024 | | | +| TP label | Battery Status Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map. Standard Configuration 2706. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose | Check that:
    For [Standard-Configurations 2706] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | +| Other PICS | | +| Initial condition | The simulated PHD and PHG under test are in Operating State using the standard configuration (2706). | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to set the values to: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, MDC_ATTR_ID_LABEL_STRING, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed fixed format event report with the new data layout.
    4. 4. The simulated PHD waits until it receives a confirmation
    5. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR Attribute.
    6. 6. The simulated PHD waits until it receives a confirmation
    7. 7. Repeat steps 1-6 for each Battery Status Enumeration object (handles 4, 6, 8, 10, 12 and 14)
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/PLT/PHG/CLASS/PSM/BV-025 | | | +| TP label | Battery Status Attribute-Value-Map. Adding additional attributes to the Attribute-Value-Map. Standard Configuration 2707. | | | +| Coverage | Spec | [ISO/IEEE 11073-10427] | | +| | Testable items | BattStatus 25; M | | +| Test purpose | Check that:
    For [Standard-Configurations 2707] the [Attribute-Value-Map] attribute shall be present
    The value of the [Attribute-Value-Map] attribute shall be
    MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, then MDC_ATTR_TIME_STAMP_BO | | | +| Applicability | C_MAN_OXP_000 AND C_MAN_OXP_076 | | | +| Other PICS | | | | +| Initial condition | The simulated PHD and PHG under test are in Operating State using the standard configuration (2707). | | | +| Test procedure |
    1. 1. The simulated PHD sends a confirmed variable event report to change the Attribute-Value-Map configuration of handle 2 (Battery Status Enumeration Object) to set the values to: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR, MDC_ATTR_ID_LABEL_STRING, then MDC_ATTR_TIME_STAMP_BO.
    2. 2. The simulated PHD waits until it receives a confirmation
    3. 3. The simulated PHD sends a confirmed fixed format event report with the new data layout.
    4. 4. The simulated PHD waits until it receives a confirmation
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 5. The simulated PHD sends a confirmed variable event report with just MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR Attribute.
    2. 6. The simulated PHD waits until it receives a confirmation
    3. 7. Repeat steps 1-6 for each Battery Status Enumeration object (handles 4, 6, 8, 10, 12, 14 and 16)
    | +| Pass/Fail criteria |
    • • In step 4, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement and date are displayed properly).
    • • In step 6, verify that the PHG under test is able to accept the data properly and applies the correct bytes to the correct attributes (e.g., if there is a UI verify the measurement is displayed properly)
    | +| Notes | | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T X.290] Recommendation ITU-T X.290 (1994), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*. +- [b-ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI ETS 300 406] ETSI ETS 300 406 (1995), *Methods for Testing and Specifications (MTS); Protocol and profile conformance testing specifications; Standardization methodology*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.13. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.11. + +- [b-TI] PHD Testable items. Test Tool v7.0.2.0 – Excel sheet v1.10. + + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.847-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.847-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..edd62599f163b4bbf55ad8ff09fcdcbd2d46e3c3 --- /dev/null +++ b/marked/H/T-REC-H.847-201704-I_PDF-E/raw.md @@ -0,0 +1,769 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.847** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 7: Continua Design Guidelines for +Bluetooth Low Energy: Personal Health Devices** + +Recommendation ITU-T H.847 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.847 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 7: Continua Design Guidelines for Bluetooth Low Energy: Personal Health Devices + +## Summary + +Recommendation ITU-T H.847 provides a test suite structure (TSS) and the test purposes (TP) for personal health devices using Bluetooth Low Energy transport in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.847 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 7: Continua Design Guidelines. Personal Health Device BLE (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.847 | 2015-01-13 | 16 | 11.1002/1000/12276 | +| 2.0 | ITU-T H.847 | 2016-07-14 | 16 | 11.1002/1000/12954 | +| 3.0 | ITU-T H.847 | 2017-04-13 | 16 | 11.1002/1000/13236 | + +## Keywords + +Bluetooth Low Energy (BLE), conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|---------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 4 | +| 3.1 | Terms defined elsewhere ..... | 4 | +| 3.2 | Terms defined in this Recommendation ..... | 4 | +| 4 | Abbreviations and acronyms ..... | 4 | +| 5 | Conventions ..... | 5 | +| 6 | Test suite structure (TSS) ..... | 6 | +| 7 | Electronic attachment ..... | 8 | +| Annex A | Test purposes ..... | 9 | +| A.1 | TP definition conventions..... | 9 | +| A.2 | Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG)..... | 11 | +| | Bibliography..... | 24 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 7: Continua Design Guidelines. Personal Health Device BLE (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2012-10-05 | Initial release for Test Tool DG2011. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_LP-PAN_PART_7_v1.0.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • • BPM and HR profiles
    | +| 1.2 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN-TAN Interface PART_7_v1.1.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.3 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_LP-PAN_PART_7_v1.2.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row has been added
    | +| 1.4 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_LP-PAN_PART_7_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015]:
    • • Adds WS/BCA BLE device specialization
    • • Adds SABTE IEEE device specialization
    | +| 1.5 | 2016-01-26 | First maintenance release for Test Tool DG2015. It uses "TSS&TP_DG2015_LP-PAN_PART_7_v1.4.doc" as a baseline and adds some updates according to the maintenance 2015 activity. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_7_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]:
    • • Adds PLX BLE device specialization
    • • Adds CGM BLE device specialization
    | + +## Recommendation ITU-T H.847 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 7: Continua Design Guidelines for Bluetooth Low Energy: Personal Health Devices + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 7. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway +- **Part 7: Continua Design Guidelines. BLE Personal Health Device** +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [Bluetooth PHDT v1.6] Bluetooth SIG, *Personal Health Devices Transcoding White Paper, v1.6*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=310657](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=310657) +- [ISO/IEEE 11073-10404] ISO/IEEE 11073-10404:2010, *Health informatics – Personal health device communication – Part 10404: Device specialization – Pulse oximeter*. + +- [ISO/IEEE 11073-10406] ISO/IEEE 11073-10406-2012, *Health informatics – Personal health device communication – Part 10406: Device specialization – Basic electrocardiograph (ECG) (1- to 3-lead ECG)*. + +- [ISO/IEEE 11073-10407] ISO/IEEE 11073-10407:2010, *Health informatics – Personal health device communication – Part 10407: Device specialization – Blood pressure monitor, version 1.0*. + +- [ISO/IEEE 11073-10408] ISO/IEEE 11073-10408:2010, *Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer*. + +- [ISO/IEEE 11073-10415] ISO/IEEE 11073-10415:2010, *Health informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale*. + +- [ISO/IEEE 11073-10417] ISO/IEEE 11073-10417:2014, *Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter*. + +- [ISO/IEEE 11073-10418C] ISO/IEEE 11073-10418-2014, *Health informatics – Personal health device communication – Part 10418: Device specialization – International Normalized Ratio (INR) monitor, including ISO/IEEE 11073-10418:2014/Cor 1:2016*. + with + + +- [ISO/IEEE 11073-10419] ISO/IEEE 11073-10419:2016, *Health informatics – Personal health device communication – Part 10419: Device specialization – Insulin pump.* + +- [ISO/IEEE 11073-10420] ISO/IEEE 11073-10420-2012, *Health informatics – Personal health device communication – Part 10420: Device specialization – Body composition analyzer.* + +- [ISO/IEEE 11073-10421] ISO/IEEE 11073-10421:2012, *Health informatics – Personal health device communication – Part 10421: Device specialization – Peak expiratory flow monitor (peak flow).* + +- [ISO/IEEE 11073-10424] ISO/IEEE 11073-10424:2016, *Health informatics – Personal health device communication – Part 10424: Device specialization – Sleep apnoea breathing therapy equipment (SABTE).* + +NOTE – Equivalent to IEEE 11073-10424-2014, Health informatics – Personal health device communication – Part 10424: Device Specialization – Sleep Apnoea Breathing Therapy Equipment (SABTE). + +- [ISO/IEEE 11073-10425] ISO/IEEE 11073-10425:2016, *Health informatics – Personal health device communication – Part 10425: Device specialization – Continuous glucose monitor (CGM).* + +- [ISO/IEEE 11073-10441] ISO/IEEE 11073-10441-2015, *Health informatics – Personal Health Device Communication – Part 10441: Device Specialization – Cardiovascular Fitness and Activity Monitor, (Revision of IEEE Std 11073-10441-2008).* + +- [ISO/IEEE 11073-10442] ISO/IEEE 11073-10442:2015, *Health informatics – Personal health device communication – Part 10442: Device specialization – Strength fitness equipment.* + +- [ISO/IEEE 11073-10471] ISO/IEEE 11073-10471:2010, *Health informatics – Personal health device communication – Part 10471: Device specialization – Independent living activity hub.* + +- [ISO/IEEE 11073-10472] ISO/IEEE 11073-10472:2012, *Health informatics – Personal health device communication – Part 10472: Device specialization – Medication monitor.* + +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx series (in force), *Health informatics – Personal health device communication – Device specialization.* +NOTE – Shorthand is used to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. + +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd. 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------------------| +| ATS | Abstract Test Suite | +| DUT | Device Under Test | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IUT | Implementation Under Test | +| IP | Insulin Pump | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCT | Protocol Conformance Testing | +| PCO | Point of Control and Observation | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | + +| | | +|------|--------------------------------------| +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|---------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 1.1.9 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - **Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG)** + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + +- Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) +- Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) +- Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 1.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 1.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +###### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + +- Subgroup 2.2.1: General (GEN) +- Subgroup 2.2.2: PHD domain information model (DIM) +- Subgroup 2.2.3: PHD service model (SER) +- Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + - Subgroup 2.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (BLE) + - TAN: Touch area network (NFC) + - PAN-LAN-TAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose (TP). +- **TP label:** This is the title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP are included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. + +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--| +| TP Id | TP/LP-PAN/PHD/TR/BLEDG/BI-000 | | | +| TP label | Abnormal cases management – Data exchange before pairing | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing BT LE 8; M | | +| Test purpose |

    Check that:

    BLE Personal Health Device (PHD) data (other than service discovery data or capability or service name from the advertising packet) shall not be exchanged with a BLE Personal Health Gateway (PHG) prior to pairing

    | | | +| Applicability | C_AG_BLE_000 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state and they have not been paired before. | | | +| Test procedure |
    1. 1. Reset the PHD under test to the default configuration and turn it on.
    2. 2. The simulated PHG initiates discovery, it finds the PHD under test, but it does not start the pairing process.
    3. 3. The simulated PHG waits until a 2-minute timeout expires. During this time, the PHD under test shall not exchange data (except the service discovery data or capability or service name from the advertising packet) with the simulated PHG.
    | | | +| Pass/Fail criteria | In step 3, the PHD under test does not exchange data prior to pairing. | | | +| Notes | | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-------------------------------| +| TP Id | TP/LP-PAN/PHD/TR/BLEDG/BV-000 | | | +| TP label | Discoverability mode service | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing BT LE 4; M | Discovery_Pairing BT LE 10; M | +| Test purpose |

    Check that:

    BLE PHDs shall not be discoverable unless initiated by a user

    [AND]

    After a BLE PHD is successfully paired, it shall immediately (e.g. within 1 second) become undiscoverable until made discoverable again by the user.

    | | | +| Applicability | C_AG_BLE_000 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state and they have not been paired before. | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a non- discoverable Bluetooth device.
    2. 2. The simulated PHG initiates a discovery process (Scanning state). Check if the simulated
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    PHG finds the PHD under test.

    3. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).

    4. The simulated PHG initiates again a discovery process (Scanning state), it discovers the PHD under test and it completes the pairing process with the PHD under test (Initiating state).

    5. The simulated PHG initiates a new discovery process. Check if the PHD under test is discoverable or not.

    | +| Pass/Fail criteria |

    In step 2, the PHD under test shall not be discoverable.

    In step 5, the PHD under test shall not be discoverable.

    | +| Notes | | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--| +| TP Id | TP/LP-PAN/PHD/TR/BLEDG/BV-001 | | | +| TP label | Maximum Discovery service duration | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing BT LE 9; R | | +| Test purpose |

    Check that:

    BLE PHD should have a documented maximum duration for discoverable mode whereby after the maximum time, the BLE PHD ceases to be discoverable until put back into that mode by the user

    | | | +| Applicability | C_AG_BLE_000 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG support the same device specialization, they are in a Standby state and they have not been paired before. | | | +| Test procedure |
    1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. The simulated PHG waits until Twait1 = Tdiscoverable – Tguard
    3. The simulated PHG initiates a discovery process (Scanning state). Check that the simulated PHG finds the PHD under test.
    4. The simulated PHG waits (from initial time = 0) until Twait2 = Tdiscoverable + Tguard
    5. When Twait2 expires, the simulated PHG initiates a new discovery process. Check if the simulated PHG finds the PHD under test.
    | | | +| Pass/Fail criteria |

    In step 3, the PHD under test is discoverable.

    In step 5, the PHD under test should not be discoverable. If it is discoverable, the test tool gives a warning message.

    | | | +| Notes |

    Tdiscoverable is defined in PIXIT I_AG_BLEDG_006

    Tguard = Tdiscoverable/2

    | | | + +| | | | | +|-----------------|--------------------------------------------|------------------------|--| +| TP Id | TP/LP-PAN/PHD/TR/BLEDG/BV-002 | | | +| TP label | Pairing service and delete pairing service | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------|-------------------| +| | Testable items | Discovery_Pairing BT LE 7; M | Discovery_Pairing BT LE 5; R | Notify BT LE 1; R | +| Test purpose | Check that:
    BLE PHD shall support replacing its pairing
    [AND]
    BLE PHD should have a way to delete pairings
    [AND]
    If supported by the UI, BLE PHD should inform the user that pairing and authentication was successful | | | | +| Applicability | C_AG_BLE_000 | | | | +| Other PICS | C_AG_BLE DG_001 | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state and they have not been paired before. | | | | +| Test procedure | 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. The test tool simulated PHG initiates the discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. Ask the operator to remove the paired devices in the PHD under test. | | | | +| Pass/Fail criteria | In step 2, the PHD finishes the pairing process successfully.
    In step 2, if PHD supports an UI that provides information about the Bluetooth connection (C_AG_BLE DG_001 = TRUE) and the PHD has not notified the pairing and authentication process, the test tool gives a warning message.
    In step 4, if the PHD cannot remove the paired devices, the test tool gives a warning message. | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| TP Id | TP/LP-PAN/PHD/TR/BLE DG/BV-003 | | | | +| TP label | Storage pairing service | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Discovery_Pairing BT LE 11; M | | | +| Test purpose | Check that:
    BLE PHDs should store pairing data from at least the most recently paired device such that the data is persistent (e.g. with loss of power, including removal of a battery) | | | | +| Applicability | C_AG_BLE_000 | | | | +| Other PICS | C_AG_BLE DG_001 | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state and they have not been paired before. | | | | +| Test procedure | 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state). | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The simulated PHG initiates a discovery process (Scanning state), it finds the PHD under test and it establishes a pairing with the PHD under test (Initiating state).
    2. 3. Turn off the PHD under test by removing the batteries or unplugging the power supply.
    3. 4. Turn on the PHD under test again (Standby state).
    4. 5. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state). Check if the pairing process is dispatched again.
    | +| Pass/Fail criteria | In step 5, the pairing process should not be dispatched again because both devices should have stored the pairing data from the previous pairing process. If the pairing process is dispatched again then the test tool gives a WARNING message. | +| Notes | | + +| | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| TP Id | TP/LP-PAN/PHD/TR/BLEDG/BV-004 | | +| TP label | Supported service profiles | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | +| | Testable items | Discovery_Pairing BT LE 14; M | +| Test purpose | Check that:
    BLE PHD's Attribute database shall list all supported LE Services/Profiles claimed in Continua certification documentation | | +| Applicability | C_AG_BLE_000 | | +| Other PICS | C_AG_BLEDG_001 | | +| Initial condition | The PHD under test and the simulated PHG support the same device specialization, they are in a Standby state and they have not been paired before. | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it finds the PHD under test.
    3. 3. The simulated PHG discovers all the primary services of the PHD under test.
    4. 4. The test tool checks the services UUID supported by the PHD under test:
      • • IF the thermometer specialization is going to be certified (C_AG_BLE_001 = TRUE) THEN the health thermometer primary service (UUID 0x1809) shall be supported by the PHD under test.
      • • IF the blood pressure specialization is going to be certified (C_AG_BLE_004 = TRUE) THEN the blood pressure primary service (UUID 0x1810) shall be supported by the PHD under test.
      • • IF the heart rate specialization is going to be certified (C_AG_BLE_015 = TRUE) THEN the heart rate primary service (UUID 0x180D) shall be supported by the PHD under test.
      • • IF the glucose meter specialization is going to be certified (C_AG_BLE_008 = TRUE) THEN the glucose primary service (UUID 0x1808) shall be supported by the PHD under test.
      • • IF the weight scale specialization is going to be certified (C_AG_BLE_018 = TRUE) THEN Weight Scale Primary Service (UUID 0x181D) shall be supported by the PHD under test.
        1. a. IF the PHD supports Body Composition Service (C_AG_BLE_019 = TRUE) THEN Body Composition Secondary Service (UUID 0x181B) shall be supported by the PHD under test
    | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • IF the pulse oximeter specialization is going to be certified (C_AG_BLE_032 = TRUE) THEN Pulse Oximeter Primary Service (UUID 0x1822) shall be supported by the PHD under test.
    • • IF Continuous Glucose Monitoring specialization is going to be certified (C_AG_BLE_042 = TRUE) THEN CGM Primary Service (UUID 0x181F) shall be supported by the PHD under test.
    | +| Pass/Fail criteria | In step 4 the specializations claimed in the Continua certification shall match the services listed by the PHD under test. | +| Notes
    (to assist manual testing)     |

    When performing Primary Services (0x2800) discovery (using “Discover All Primary Services” or “Discovery Primary Services by Service UUID” GATT sub-procedures) on the complete attribute handle range of the device, supported primary services UUID declarations shall be included in the response to the sub-procedure.

    This response to this sub-procedure will be composed of one or more ATT response packets that include one or more handle-value pairs (one for each Primary Service discovered in the specified range) in its attribute data. Each of this handle-value pairs is composed of:

    • • Starting Attribute Handle (2 octets)
    • • Ending Attribute Handle (2 octets)
    • • Primary Service Declaration (2 octets), that will include the Short UUID of the supported Primary Service as seen in the Test Procedure.

    Additionally, if Weight Scale and Body Composition services are supported, the Body Composition Secondary Service UUID (0x181B) Service Declaration shall be returned when performing a “Find Included Services” GATT sub-procedure on the handle range that contains the Weight Scale Primary Service Declaration.

    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--| +| TP Id | TP/LP-PAN/PHD/TR/BLEDG/BV-005 | | | +| TP label | Authentication support service (Secure simple pairing support) | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Authentication BT LE 1; M | | +| Test purpose |

    Check that:

    Continua LP wireless PAN service components shall support at least one of the following Bluetooth 4.0 pairing methods depending on its I/O capabilities and the appropriate security for the service component device type: Just Works or Passkey Entry

    | | | +| Applicability | C_AG_BLE_000 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state and they have not been paired before. | | | +| Test procedure |
    1. 1. Check the PHD under test IO capabilities declared in PIXIT I_AG_BLEDG_002, the man in the middle (MITM) protection declared in PIXIT I_AG_BLEDG_003 and the association model declared in PIXIT I_AG_BLEDG_004
      1. a. IF the PHD under test does not support MITM protection (PIXIT I_AG_BLEDG_003 = FALSE) THEN
        • • IF the PHD under test supports the Just Works association model (PIXIT I_AG_BLEDG_004 = 0) THEN the test tool simulated PHG is configured with NoInputOutput capabilities and without man in the middle (MITM) support
        • • IF the PHD under test supports the Passkey Entry association model (PIXIT I_AG_BLEDG_004 = 1) THEN the combination of IO capabilities, association model and MITM support declared by the PHD under test in PIXITs is not feasible and the test case ends by giving a FAIL verdict due to inconsistency
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    among the PHD under test SSP features declared in PIXITs

    b. IF the PHD under test supports MITM protection (PIXIT I_AG_BLE DG_003 = TRUE) THEN

    • • IF the PHD under test supports the Just Works association model (PIXIT I_AG_BLE DG_004 = 0) THEN the combination of IO capabilities, association model and MITM support declared by the PHD under test in PIXITs is not feasible and the test case ends giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs
    • • IF the PHD under test supports the Passkey Entry association model (PIXIT I_AG_BLE DG_004 = 1) and DisplayOnly capabilities (PIXIT I_AG_BLE DG_002 = 0) THEN the test tool simulated PHG is configured with KeyboardOnly capabilities (see Note 1) and with MITM support
    • • IF the PHD under test supports the Passkey Entry association model (PIXIT I_AG_BLE DG_004 = 1) and DisplayYesNo capabilities (PIXIT I_AG_BLE DG_002 = 1) THEN the test tool simulated PHG is configured with KeyboardOnly capabilities (see Note 1) and with MITM support
    • • IF the PHD under test supports the Passkey Entry association model (PIXIT I_AG_BLE DG_004 = 1) and KeyboardOnly capabilities (PIXIT I_AG_BLE DG_002 = 2) THEN the test tool simulated PHG is configured with DisplayOnly capabilities (see Note 2) and with MITM support
    • • IF the PHD under test supports the Passkey Entry association model (PIXIT I_AG_BLE DG_004 = 1) and NoInputNoOutput capabilities (PIXIT I_AG_BLE DG_002 = 4) THEN the combination of IO capabilities, association model and MITM support declared by the PHD under test in PIXITs is not feasible and the test case ends by giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs
    • • IF the PHD under test supports the Passkey Entry association model (PIXIT I_AG_BLE DG_004 = 1) and KeyboardDisplay capabilities (PIXIT I_AG_BLE DG_002 = 3) THEN the test tool simulated PHG is configured with DisplayOnly capabilities (see Note 2) and with MITM support

    2. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).

    3. The simulated PHG initiates a discovery process (Scanning state), it finds the PHD under test and it establishes a pairing with the PHD under test (Initiating state)

    | +| Pass/Fail criteria | In step 3, the pairing process is completed successfully. | +| Notes |

    Note 1 – "KeyboardOnly" and "KeyboardDisplay" are both OK. The test tool simulated PHG is configured with "KeyboardOnly".

    Note 2 – "DisplayOnly", "DisplayYesNo", "KeyboardOnly" and "KeyboardDisplay" are all OK. The test tool simulated PHG is configured with "DisplayOnly".

    | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------|------------------------|------------------| +| TP Id | TP/LP-PAN/PHD/TR/BLE DG/BV-006 | | | +| TP label | Continua DG Bluetooth LE attribute requirements - System Model | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | OEM 1; M | OEM 2;M | +| | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Common MDS 2; M | String Conv 2; M | +| Test purpose |

    Check that:

    BLE PHDs implement Manufacturer Name String characteristic

    [AND]

    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    BLE PHDs shall set the Manufacturer Name String defined in the Bluetooth SIG Device Information Service to the device original manufacturer's name. If this capability is available, the Manufacturer Name String may be overwritten to the customer facing company's name by the customer

    facing company

    [AND]

    BLE PHDs implement Model Number String characteristic

    [AND]

    BLE PHDs shall set Model Number String defined in the Bluetooth SIG Device Information Service to the device original manufacturer's model number. The Model Number String field may be overwritten to the customer facing company's model by the customer facing company

    | +| Applicability | C_AG_BLE_000 | +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The test tool checks if the PHD under test implements the model number string Bluetooth characteristic.
    5. 5. IF the PHD under test implements the model number string Bluetooth characteristic value THEN
      1. a. the simulated PHG reads the model number string Bluetooth characteristic value
      2. b. the PHD under test sends the model number string Bluetooth characteristic value
    6. 6. The test tool checks if the PHD under test implements manufacturer name string Bluetooth characteristic value.
    7. 7. IF the PHD under test implements the manufacturer name string Bluetooth characteristic value THEN
      1. a. the simulated PHG reads the manufacturer name string Bluetooth characteristic value
      2. b. the PHD under test sends the manufacturer name string Bluetooth characteristic value
    | +| Pass/Fail criteria |

    In step 4, the PHD under test implements the model number string Bluetooth characteristic value

    In step 5.b, the model number string Bluetooth characteristic value matches with value declared by the vendor in PIXIT I_AG_BLE DG_010

    In step 6, the PHD under test implements the manufacturer name string Bluetooth characteristic value

    In step 5.b, the manufacturer name string Bluetooth characteristic value matches with the value declared by the vendor in PIXIT I_AG_BLE DG_009

    | +| Notes | | + +| | | | +|-----------------|-------------------------------------------------------------|------------------------| +| TP Id | TP/LP-PAN/PHD/TR/BLEDG/BV-007 | | +| TP label | Continua DG Bluetooth LE attribute requirements - System ID | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------|----------| +| | Testable items | OEM 3; M | OEM 4;M | OEM 5; M | +| | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Common MDS 3; M | MDS Conv 4; M | | +| Test purpose |

    Check that:

    BLE PHDs implement System ID characteristic

    [AND]

    The OUI part of the System ID field defined in the Bluetooth SIG Device Information Service in a BLE PHD shall remain unchanged from the value set by the original manufacturer

    [AND]

    The 40 bit manufacturer defined identifier in the System ID field defined in the Bluetooth SIG Device Information Service of a BLE PHD shall remain unchanged from the value set by the original manufacturer

    [AND]

    There shall not be multiple different System-Id values that identify the same BLE PHD

    | | | | +| Applicability | C_AG_BLE_000 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The test tool checks if the PHD under test implements the system ID Bluetooth characteristic value.
    5. 5. IF the PHD under test implements the system ID Bluetooth characteristic value THEN
      1. a. the simulated PHG reads the system ID Bluetooth characteristic value
      2. b. the PHD under test sends the manufacturer name Bluetooth characteristic value
      3. c. Disconnect the PHD under test and connect it again (Standby state).
      4. d. the test tool simulated PHG connects the PHD under test (Connection state) and it reads the system ID Bluetooth characteristic
      5. e. the PHD under test sends the manufacturer name Bluetooth characteristic value
    | | | | +| Pass/Fail criteria |

    In step 4, the PHD implements the system ID Bluetooth characteristic value.

    In step 5.b, the system ID Bluetooth characteristic value matches with the value declared by the vendor in PIXITs I_AG_BLE DG_007 and I_AG_BLE DG_008.

    In step 5.e, the system ID Bluetooth characteristic value must be the same as the value displayed in step 5.b.

    | | | | +| Notes | | | | | + +| | | | +|-----------------|----------------------------------------------------------------------------|------------------------| +| TP Id | TP/LP-PAN/PHD/TR/BLE DG/BV-008 | | +| TP label | Continua DG Bluetooth LE attribute requirements - Production Specification | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|---------------| +| | Testable items | OEM 6; M | OEM 7; M | | +| | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Common MDS 5; M | String Conv 2; M | MDS Conv 6; M | +| Test purpose |

    Check that:

    BLE PHDs implement Serial Number String and Firmware Revision String characteristics

    [AND]

    BLE PHDs shall set the Serial Number String defined in the Bluetooth SIG Device Information Service to the serial number of the device.

    [AND]

    BLE PHDs that provide a firmware identifier shall set the Firmware Revision String defined in the Bluetooth SIG Device Information Service to the firmware identifier of the device

    | | | | +| Applicability | C_AG_BLE_000 | | | | +| Other PICS | C_AG_BLE DG_002 | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The test tool checks if the PHD under test implements the serial number string Bluetooth characteristic value.
    5. 5. IF the PHD under test implements the serial number string Bluetooth characteristic value THEN
      1. a. the simulated PHG reads the serial number string Bluetooth characteristic value
      2. b. the PHD under test sends the serial number string Bluetooth characteristic value
    6. 6. The test tool checks if the PHD under test implements the firmware revision string Bluetooth characteristic value.
    7. 7. IF the PHD under test implements the firmware revision string Bluetooth characteristic value THEN
      1. a. the simulated PHG reads the firmware revision string Bluetooth characteristic value
      2. b. the PHD under test sends the firmware revision string Bluetooth characteristic value
    | | | | +| Pass/Fail criteria |

    In step 4, the PHD implements the serial number string characteristic value.

    In step 5.b, the serial number string Bluetooth characteristic value matches with the value declared by the vendor in PIXIT I_AG_BLE DG_011

    In step 6, IF PICS C_AG_BLE DG_002 = TRUE THEN the PHD implements the firmware revision string Bluetooth characteristic value.

    In step 6, IF PICS C_AG_BLE DG_002 = FALSE THEN the PHD does not implement the firmware revision string Bluetooth characteristic value.

    In step 7.b, the firmware revision string Bluetooth characteristic value matches with the value declared by the vendor in PIXIT I_AG_BLE DG_012

    | | | | +| Notes | | | | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------| +| TP Id | TP/LP-PAN/PHD/TR/BLE DG/BV-009 | | | +| TP label | Continua DG Bluetooth LE attribute requirements - Reg-Cert-Data-List | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Cert_Reg 1; M | Cert_Reg 2; M | +| | | Cert_Reg 4; M | Cert_Reg 5; M | +| | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Common MDS 14; M | Regulatory Conv 1; M | +| Test purpose |

    Check that:

    BLE PHDs shall support and fill the IEEE 11073-20601 Regulatory Certification Data List characteristic defined in the Bluetooth SIG Device Information Service with an MDER encoded version of the IEEE 11073-20601 RegCertDataList data structure

    [AND]

    All Continua BLE PHDs shall report information on which Certified Device Classes exist on the device. This includes providing information to the BLE PHG component on the transport used (Bluetooth LE) as well as the Profile used

    [AND]

    All BLE PHDs shall report information on whether or not they are regulated. This is a single Boolean entitled unregulated-device, which is set to 1 if not regulated and 0 if regulated and contained as part of IEEE 11073-20601 Regulatory Certification Data List defined in the Bluetooth SIG Device Information Service

    | | | +| Applicability | C_AG_BLE_000 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device.
    2. 2. The test tool simulated PHG initiates a discovery process, it discovers the PHD under test and it starts a pairing process with the PHD under test.
    3. 3. The test tool simulated PHG initiates a Bluetooth connection with the PHD under test.
    4. 4. The test tool checks the characteristics implemented by the PHD under test.
    5. 5. The test tool simulated PHG reads the Bluetooth equivalent characteristics "IEEE 11073-20601 Regulatory Certification Data List"
    6. 6. The PHD under test sends the "IEEE 11073-20601 Regulatory Certification Data List" Bluetooth equivalent characteristic value and the test tool checks its content:
      • Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex). auth-body-continua(2)
          • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
        • • auth-body-data:
          • - major-IG-version: 05 (hex)
          • - minor-IG-version: 00 (hex)
          • - certified-devices: SEQUENCE {CertifiedDeviceClassEntry: MDC_DEV_SPEC_PROFILE_* - 4096 + TCode x 8192, and TCode=4 (Bluetooth LE)}
      • Element:
    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • auth-body-and-struc-type:
      • - auth-body: 02 (hex). auth-body-continua(2)
      • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
    • • auth-body-data:
      • - regulation-bit-field: 00 00 (hex). Regulated device OR 80 00 (hex). Unregulated device
    | +| Pass/Fail criteria |

    In step 4, the PHD implements the "IEEE 11073-20601 Regulatory Certification Data List" characteristic value.

    In step 6, check that the IEEE 11073-20601 Regulatory Certification Data List characteristic value is as described in the test procedure and:

    • • IF the PHD under test supports the thermometer specialization (C_AG_BLE_001) THEN MDC_DEV_SPEC_PROFILE_* is MDC_DEV_SPEC_PROFILE_TEMP = 4104 and CertifiedDeviceClassEntry = 4104-4096+4*8192 = 32776
    • • IF the PHD under test supports the blood pressure specialization (C_AG_BLE_004) THEN MDC_DEV_SPEC_PROFILE_* is MDC_DEV_SPEC_PROFILE_BP = 4103 and CertifiedDeviceClassEntry = 4103-4096+4*8192 = 32775
    • • IF the PHD under test supports the heart rate specialization (C_AG_BLE_015) THEN MDC_DEV_SPEC_PROFILE_* is [MDC_DEV_SPEC_PROFILE_ECG = 4102 and MDC_DEV_SUB_SPEC_PROFILE_HR = 4237] and CertifiedDeviceClassEntry = [(4102-4096+4*8192 = 32774) and (4237-4096+4*8192 = 32909)]
    • • IF the PHD under test supports the glucose specialization (C_AG_BLE_008) THEN MDC_DEV_SPEC_PROFILE_* is MDC_DEV_SPEC_PROFILE_GLUCOSE = 4113 and CertifiedDeviceClassEntry = 4113-4096+4*8192 = 32785]
    • • IF the PHD under test supports Weight Scale specialization (C_AG_BLE_018 = TRUE and C_AG_BLE_019 = FALSE) THEN MDC_DEV_SPEC_PROFILE_* is MDC_DEV_SPEC_PROFILE_SCALE = 4111 and CertifiedDeviceClassEntry = 4111-4096+4*8192 = 32783
    • • IF the PHD under test supports Body Composition specialization (C_AG_BLE_018 = TRUE and C_AG_BLE_019 = TRUE) THEN MDC_DEV_SPEC_PROFILE_* is MDC_DEV_SPEC_PROFILE_BCA = 4116 and CertifiedDeviceClassEntry = 4116-4096+4*8192 = 32788
    • • IF the PHD under test supports Pulse Oximeter specialization (C_AG_BLE_032 = TRUE) THEN MDC_DEV_SPEC_PROFILE_* is MDC_DEV_SPEC_PROFILE_PULS_OXIM = 4100 and CertifiedDeviceClassEntry = 4100-4096+4*8192 = 32772
    • • IF the PHD under test supports Continuous Glucose Monitoring specialization (C_AG_BLE_042 = TRUE) THEN MDC_DEV_SPEC_PROFILE_* is MDC_DEV_SPEC_PROFILE_CGM = 4106 and CertifiedDeviceClassEntry = 4106-4096+4*8192 = 32778
    | +| Notes
    (to assist manual testing)     |

    To read IEEE 11073-20601 Regulatory Certification Data List characteristic (0x2A2A), Master must discover the characteristic (using "Discover All Characteristics of a Service" or "Discover Characteristics by UUID" GATT sub-procedures on the handle range of the required Service), and then read its value (using "Read Characteristic Value" GATT sub-procedure).

    The response to the Read Request will be an ATT packet including Registration Certificate Data as the stored attribute type. Its value will be composed of the following elements:

    • • Regulatory Certification Data List Count: 2 octets (0x0002)
    • • Regulatory Certification Data List Length: 2 octets
    • • Authorization body: 1 octet (0x02)
    • • Authorization Body Structure Type: 1 octet (0x01)
    • • Authorization Body Structure Length: 2 octets
    • • Major IG Version: 1 octet (0x05)
    • • Minor IG Version: 1 octet (0x01)
    • • Certified Device Class List Count: 2 octets
    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Certified Device Class List Length: 2 octets
    • • (1 or more) Certified Device Class Entry: 2 octets.
      • ▪ If PHD under test supports Thermometer specialization: 0x8008
      • ▪ If PHD under test supports Blood Pressure specialization: 0x8007
      • ▪ If PHD under test supports Heart Rate specialization: 0x8006 (ECG specialization) AND 0x808D (Heart Rate profile)
      • ▪ If PHD under test supports Glucose specialization: 0x8011
      • ▪ If PHD under test supports Weight Scale specialization: 0x800F
      • ▪ If PHD under test supports Body Composition specialization: 0x8014
      • ▪ If PHD under test supports Pulse Oximeter specialization: 0x8004
    • • Continua Regulatory Structure: 2 octets (0x0202)
    • • Continua Regulatory Structure Length: 2 octets (0x0002)
    • • Regulation Bit Field Type: 2 octets (0x0000 or 0x8000)
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------| +| TP Id | TP/LP-PAN/PHD/TR/BLEDG/BV-010 | | | +| TP label | Measurement time stamp and Date Time characteristic | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Date_Time 1; M | | +| | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | MDS Conv 9; M | HR Specific MDS 6; M | +| Test purpose | Check that:
    If BLE PHD reports the Time Stamp in measurements then it should support the Current Time Service. | | | +| Applicability | C_AG_BLE_000 AND (C_AG_BLE_001 OR C_AG_BLE_004 OR C_AG_BLE_008 OR C_AG_BLE_018 OR C_AG_BLE_032) | | | +| Other PICS | C_AG_BLE_002, C_AG_BLE_003, C_AG_BLE_005, C_AG_BLE_019, C_AG_BLE_020, C_AG_BLE_025, C_AG_BLE_030, C_AG_BLE_035 | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a measurement to the simulated PHG
      1. a. IF the PHD under test sends a thermometer measurement with a time stamp THEN:
        1. a.1 IF PICS C_AG_BLE_030 = TRUE, the test tool checks if the PHD under test supports Current Time Service
        2. a.2 IF PICS C_AG_BLE_002 = TRUE, Test Tool checks if the PHD under test implements Date Time characteristic inside the Thermometer service
      2. b. IF the PHD under test sends a blood pressure measurement with a time stamp THEN:
    | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b.1 IF PICS C_AG_BLE_030 = TRUE, the test tool checks if the PHD under test supports Current Time Service

    b.2 IF PICS C_AG_BLE_002 = TRUE, Test Tool checks if the PHD under test implements Date Time characteristic inside the Blood Pressure service

    c. IF the PHD under test sends a glucose measurement with a Base Time THEN:

    c.1 IF PICS C_AG_BLE_030 = TRUE, the test tool checks if the PHD under test supports Current Time Service

    c.2 IF PICS C_AG_BLE_002 = TRUE, Test Tool checks if the PHD under test implements Date Time characteristic inside the Glucose service

    d. IF the PHD under test sends a Weight measurement with Time Stamp THEN Test Tool checks if the PHD under test supports Current Time Service

    e. IF the PHD under test sends a Body Composition measurement with Time Stamp THEN Test Tool checks if the PHD under test supports Current Time Service

    f. IF the PHD under test sends a Pulse Oximeter measurement with Time Stamp THEN Test Tool checks if the PHD under test supports Current Time Service

    | +| Pass/Fail criteria |

    In Step 4.a.1, the PHD supports Current Time Service and PICS C_AG_BLE_003 = TRUE

    In Step 4.a.2, the PHD implements Date Time characteristic inside the Thermometer service and PICS C_AG_BLE_003 = TRUE

    In Step 4.b.1, the PHD supports Current Time Service and PICS C_AG_BLE_004 = TRUE

    In Step 4.b.2, the PHD implements Date Time characteristic inside the Blood Pressure service and PICS C_AG_BLE_004 = TRUE

    In Step 4.c.1, the PHD supports Current Time Service

    In Step 4.c.2, the PHD implements Date Time characteristic inside the Glucose service

    In Step 4.d, the PHD supports Current Time Service and PICS C_AG_BLE_020 = TRUE

    In Step 4.e, the PHD supports Current Time Service and PICS C_AG_BLE_025 = TRUE

    In Step 4.f, the PHD supports Current Time Service and PICS C_AG_BLE_035 = TRUE

    | +| Notes
    (to assist manual testing)     |

    Once enabled indications/notifications for the appropriate characteristic, the PHD under test will send the measurement. Check that a Timestamp field is present in the received measurement.

    If a Timestamp field is included check in services discovery that Current Time Service (0x1805) is present

    | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T X.290] Recommendation ITU-T X.290 (1994), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*. +- [b-ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements*. +- [b-Bluetooth HDPv1.1] Bluetooth SIG, *Health Device Profile, version 1.1*. +[https://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc\\_id=260864](https://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc_id=260864) +- [b-Bluetooth MCAP] Bluetooth SIG, *Multi-Channel Adaptation Protocol, Version 1.0. Bluetooth SIG*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=119995](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=119995) +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst" *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI ETS 300 406] ETSI ETS 300 406 (1995), *Methods for Testing and Specifications (MTS); Protocol and profile conformance testing specifications; Standardization methodology*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] Personal Health Device DG2016 *PICS and PIXIT excel sheet v1.9*. + +- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 *PICS and PIXIT excel sheet v1.9*. + +- [b-TCRL] Test Case Reference List\_DG2016\_v1.11. + +- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8. + + +[b-USB DevClass] + +USB Implementers Forum (2007-11), *Universal Serial Bus Device Class Definition for Personal Healthcare Devices, Release 1.0*, plus Errata (15 February 2008), *Personal Healthcare section*. +[http://www.usb.org/developers/docs/devclass\\_docs/Personal\\_Healthcare\\_1.zip](http://www.usb.org/developers/docs/devclass_docs/Personal_Healthcare_1.zip) + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.848-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.848-201704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..089b254fa4ce1fcb6839b60167b51797aba6714f --- /dev/null +++ b/marked/H/T-REC-H.848-201704-I_PDF-E/raw.md @@ -0,0 +1,645 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.848** + +(04/2017) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 8: Continua Design Guidelines for +Bluetooth Low Energy: Personal Health +Gateway** + +Recommendation ITU-T H.848 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.848 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 8: Continua Design Guidelines for Bluetooth Low Energy: Personal Health Gateway + +## Summary + +Recommendation ITU-T H.848 provides a test suite structure (TSS) and the test purposes (TP) for personal health gateways using Bluetooth Low Energy transport in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.848 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 8: Continua Design Guidelines. Personal Health Gateway BLE (Version 1.4, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.848 | 2015-01-13 | 16 | 11.1002/1000/12277 | +| 2.0 | ITU-T H.848 | 2016-07-14 | 16 | 11.1002/1000/12955 | +| 3.0 | ITU-T H.848 | 2017-04-13 | 16 | 11.1002/1000/13237 | + +## Keywords + +Bluetooth Low Energy (BLE), conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, touch area network, Personal Health Gateway. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|----------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Test suite structure (TSS) ..... | 5 | +| 7 | Electronic attachment ..... | 7 | +| Annex A | Test purposes ..... | 8 | +| A.1 | TP definition conventions..... | 8 | +| A.2 | Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) ..... | 9 | +| | Bibliography..... | 17 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +# Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 8: Continua Design Guidelines. Personal Health Gateway BLE (Version 1.4, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2012-10-05 | Initial release for Test Tool DG2011. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_PAN-LAN-TAN_PART_8_v1.0.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • • BPM and HR profiles
    | +| 1.2 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_LP-PAN PART_8_v1.1.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.3 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_LP-PAN_PART_8_v1.2.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row has been added
    | +| 1.3 | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_LP-PAN_PART_8_v1.2.doc" because the new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015] do not affect the test procedures specified in this document. | +| 1.4 | 2016-09-20 | It uses "TSS&TP_DG2015_PLT_PART_8_v1.3.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016] | + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 8: Continua Design Guidelines for Bluetooth Low Energy: Personal Health Gateway + +# 1 Scope + +The scope of this Recommendation1 is to provide test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 8. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- **Part 8: Continua Design Guidelines. BLE Personal Health Gateway** + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [Bluetooth PHDT v1.4] Bluetooth SIG (2013), *Personal Health Devices Transcoding White Paper, v1.4*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=294539](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=294539) +- [Bluetooth PHDT v1.5] Bluetooth SIG (2014), *Personal Health Devices Transcoding White Paper, v1.5*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=272346](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=272346) +- [Bluetooth PHDT v1.6] Bluetooth SIG (2015), *Personal Health Devices Transcoding White Paper, v1.6*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=310657](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=310657) +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization*. NOTE – Shorthand is used to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd. 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IUT | Implementation Under Test | +| IP | Insulin Pump | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new | Adrenaline | + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|---------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| | | | functionalities [b-CDG 2011]. | | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata. | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 2.1.7 (shown in bold). + +- Group 1: Personal Health Devices (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + +- Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 1.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 1.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) +- Group 2: Personal Health Gateway (PHG) +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - **Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG)** + - Subgroup 2.1.8: NFC design guidelines (NDG) + - Group 2.2: IEEE 20601 Optimized exchange protocol (EXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) + - Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + +- Subgroup 2.3.9: Adherence monitor (AM) +- Subgroup 2.3.10: Insulin pump (IP) +- Subgroup 2.3.11: Peak flow (PF) +- Subgroup 2.3.12: Body composition analyser (BCA) +- Subgroup 2.3.13: Basic electrocardiograph (ECG) +- Subgroup 2.3.14: International normalized ratio (INR) +- Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) +- Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + - Subgroup 2.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + - Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth Low Energy) + - TAN: Touch area network (NFC) + - PAN-LAN-TAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies the test purpose (TP). +- **TP label:** This is the title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP are included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-------------------| +| TP Id | TP/LP-PAN/PHG/TR/BLEDG/BV-000 | | | +| TP label | Discovery and pairing process and Pairing/Auth notification | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing BT LE 1; M | Notify BT LE 2; M | +| Test purpose |

    Check that:

    Once a BLE Personal Health Gateway (PHG) has discovered a BLE Personal Health Device (PHD) that supports a compatible service, it shall support pairing with that BLE PHD

    [AND]

    If supported by the UI, the BLE PHG shall inform the user that a pairing and authentication was successful

    | | | +| Applicability | C_MAN_BLE_000 | | | +| Other PICS | C_MAN_BLEDG_001 | | | +| Initial condition | The PHG under test and the simulated PHD are in a Standby state and they have not been paired before. | | | +| Test procedure |
    1. 1. Reset the PHG under test to default configuration and turn it on.
    2. 2. Set the simulated PHD in discoverable mode (Advertising state).
    3. 3. The PHG under test initiates a search for discoverable PHDs (Scanning state).
    4. 4. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation (Initiating state).
    5. 5. When the pairing has been completed (Connection state), IF PICS C_MAN_BLEDG_001 = TRUE then the PHG under test notifies of the successful pairing and authentication process.
    | | | +| Pass/Fail criteria |

    In step 4, the PHG under test completes the pairing process successfully.

    In step 5, if the PHG supports an UI that provides information about the Bluetooth connection (C_MAN_BLEDG_001 = TRUE) then the PHG has notified the successful pairing and authentication process.

    | | | +| Notes | | | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|-------------------------------| +| TP Id | TP/LP-PAN/PHG/TR/BLEDG/BV-001 | | | +| TP label | Store pairing data | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Discovery_Pairing BT LE 12; M | Discovery_Pairing BT LE 13; R | +| Test purpose |

    Check that:

    BLE PHG should store pairing data from at least the most recently paired device such that the data is persistent (e.g. With loss of power including removal of a battery)

    [AND]

    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | BLE PHG should store pairing data for at least the number of devices they are intended to simultaneously support. | +| Applicability | C_MAN_BLE_000 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in a Standby state and they have not been paired before. | +| Test procedure |
    1. 1. Reset the PHG under test to the default configuration and turn it on.
    2. 2. Set the simulated PHD to discoverable and pairable mode (Advertising state).
    3. 3. The PHG initiates a discovery process (Scanning state), it finds the simulated PHD, establishes a pairing with it (Initiating state) and starts a Bluetooth connection (Connection state).
    4. 4. Turn off the PHG under test and remove the batteries or unplug the power supply.
    5. 5. Turn on the PHG under test again (Standby state).
    6. 6. Set the simulated PHD in discoverable and pairable mode (Advertising state).
    7. 7. The PHG under test initiates a discovery process (Scanning state), it finds the simulated PHD and starts a Bluetooth connection with it (Connection state).
    | +| Pass/Fail criteria | In step 7, the pairing process should not be dispatched again because both devices should have stored the pairing data from the previous pairing process. If the pairing process is dispatched again then the test tool gives a WARNING message. | +| Notes | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/LP-PAN/PHG/TR/BLEDG/BV-002 | | | +| TP label | Discovered devices filter | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Notify BT LE 3; R | | +| Test purpose | Check that:
    PHG shall support all pairing methods for Bluetooth 4.0, including Just Works and Passkey Entry, if the PHG has the appropriate I/O capabilities | | | +| Applicability | C_MAN_BLE_000 | | | +| Other PICS | C_MAN_BLEDG_001 | | | +| Initial condition | The PHG under test and the simulated PHD are in a Standby state and they have not been paired before. | | | +| Test procedure |
    1. 1. Reset the PHG under test to the default configuration and turn it on.
    2. 2. Set the simulated PHD to discoverable and pairable mode.
    3. 3. The PHG initiates a discovery process, it finds the simulated PHD and establishes a pairing with it.
    | | | +| Pass/Fail criteria | In step 3, if the PHG under test does not filter the discovered devices to include only the test tool simulated PHD that supports the supported service/profile, the test tool displays a warning message.

    In step 3, if the PHG supports an UI that provides information about the Bluetooth connection (C_MAN_BLEDG_001= TRUE) check that the PHG has notified the successful pairing and authentication process. | | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--| +| Notes | | | | | +| TP Id | TP/LP-PAN/PHG/TR/BLEDG/BV-003 | | | | +| TP label | Failures notification | | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | | +| | Testable items | Notify BT LE 4; M | | | +| Test purpose |

    Check that:

    If there is a failure during the discovery, pairing and authentication process, and if supported by the UI, the BLE PHG shall inform the user whether the failure is because 1) no compatible BLE PHD was found (compatible device not found) or 2) the pairing failed (pairing failure) or 3) the authentication process timed out (authentication timeout) or 4) the user entered the incorrect passkey (incorrect PIN)

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLEDG_001 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in a Standby state and they have not been paired before. | | | | +| Test procedure |
    1. 1. Disable the simulated PHD (it is not discoverable).
    2. 2. The PHG under test initiates discovery as stated in the product documentation.
    3. 3. The simulated PHD is not discovered because it has not been initialized yet. Check the PHG under test for error messages.
    4. 4. Configure the simulated PHD with a device specialization not supported by the PHG under test.
    5. 5. Set the simulated PHD to discoverable mode.
    6. 6. The PHG under test starts a discovery and pairing process with the simulated PHD.
    7. 7. Check the PHG under test for error messages.
    8. 8. Restart the simulated PHD.
    9. 9. Restart the PHG under test.
    10. 10. Configure the simulated PHD with a device specialization that is supported by the PHG under test.
    11. 11. Disable the pairable mode in the simulated PHD.
    12. 12. The PHG under test starts a discovery and pairing process with the simulated PHD.
    13. 13. Check the PHG under test for error messages.
    14. 14. Restart the simulated PHD.
    15. 15. Restart the PHG under test.
    16. 16. Configure simulated PHD with a device specialization that is supported by the PHG under test.
    17. 17. Set the simulated PHD to discoverable and pairable mode.
    18. 18. The PHG under test starts a discovery and pairing process with the simulated PHD.
    19. 19. Force the test tool simulated PHD not to complete the authentication process.
    20. 20. Check the PHG under test for error messages.
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • In step 3, the PHG under test shall inform the user that the pairing process cannot be completed (the simulated PHD has not been found).
    • In step 7, the PHG under test shall inform the user that the pairing process cannot be completed (the simulated PHD implements an unsupported specialization).
    • In step 13, the PHG under test shall inform the user that the pairing process cannot be completed (the simulated PHD is not in pairable mode).
    • In step 20, the PHG under test shall inform the user that the authentication process cannot be completed (authentication timeout).
    | +| Notes | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--| +| TP Id | TP/LP-PAN/PHG/TR/BLE DG/BV-004 | | | +| TP label | Secure Simple Pairing with PHD with NoInputNoOutput capabilities | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Authentication BT LE 2; M | | +| Test purpose | Check that:
    PHG shall support all pairing methods for Bluetooth 4.0, including Just Works and Passkey Entry, if the PHG has the appropriate I/O capabilities. | | | +| Applicability | C_MAN_BLE_000 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in a Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. Check that the PHG under test IO capabilities are declared in PIXIT I_MAN_BLE DG_002 and the man in the middle (MITM) protection is declared in PIXIT I_MAN_BLE DG_003
      1. IF the PHG under test does not support MITM protection (PIXIT I_MAN_BDG_003 = FALSE) THEN the test tool simulated PHD is configured with NoInputNoOutput capabilities and without MITM protection and the Just Works Association Model shall be used during the pairing process and the generated link key will be unauthenticated (without MITM protection).
      2. IF the PHG under test supports MITM protection (PIXIT I_MAN_BDG_003 = TRUE) THEN
        • IF the PHG under test supports NoInputNoOutput capabilities (PIXIT I_MAN_BDG_002 = 4) THEN the combination of IO capabilities and MITM support declared by the PHG under test in PIXITs is not feasible and the test case ends by giving a FAIL verdict due to inconsistency among the PHG under test SSP features declared in PIXITs
        • IF the PHG under test supports other IO capabilities (PIXIT I_MAN_BDG_002 = 0 or 1 or 2 or 3) it will not pair with PHDs with NoInputNoOutput capabilities because they do not fulfil the security level required (i.e., MITM protection) and the test case execution ends by giving a PASS verdict
    2. Set the test tool simulated PHD in discoverable and pairable mode.
    3. The PHG under test initiates a discovery process as stated in the product documentation.
    4. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | | | +| Pass/Fail criteria | In step 4, the PHG under test completes the pairing process successfully. | | | +| Notes | | | | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--| +| TP Id | TP/LP-PAN/PHG/TR/BLEDG/BV-005 | | | +| TP label | Secure Simple Pairing with PHD with DisplayOnly capabilities | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Authentication BT LE 2; M | | +| Test purpose |

    Check that:

    PHG shall support all pairing methods for Bluetooth 4.0, including Just Works and Passkey Entry, if the PHG has the appropriate I/O capabilities.

    | | | +| Applicability | C_MAN_BLE_000 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in a Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. 1. Check that PHG under test IO capabilities are declared in PIXIT I_MAN_BDG_002 and that the MITM protection is declared in PIXIT I_MAN_BDG_003
      1. a. IF the PHG under test does not support MITM protection (PIXIT I_MAN_BDG_003 = FALSE) THEN the test tool simulated PHD is configured with Secure Simple Pairing, NoInputNoOutput capabilities and without MITM protection in addition the Just Works Association Model shall be used during the Pairing process and the generated link key will be unauthenticated (without MITM protection)
      2. b. IF the PHG under test supports MITM protection (PIXIT I_MAN_BDG_003 = TRUE) THEN
        • • IF the PHG under test supports KeyboardOnly or KeyboardDisplaycapabilities (PIXIT I_MAN_BDG_002 = 2 or 3) THEN the test tool simulated PHD is configured with Secure Simple Pairing, DisplayOnly capabilities and MITM protection in addition the passkey entry association model shall be used during the pairing process and the generated link key will be authenticated (with MITM protection)
        • • IF the PHG under test supports DisplayOnly or DisplayYesNo capabilities (PIXIT I_MAN_BDG_002 = 0 or 1) THEN it will not pair with PHDs with DisplayOnly capabilities because they do not fulfil the security level required (i.e., MITM protection) and the test case execution ends by giving a PASS verdict
        • • IF PHG under test supports NoInputNoOutput capabilities (PIXIT I_MAN_BDG_002 = 4) THEN the combination of IO capabilities and MITM support declared by the PHG under test in PIXITs is not feasible and the test case ends by giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs
    2. 2. Set the test tool simulated PHD in discoverable and pairable mode.
    3. 3. The PHG under test initiates a discovery process as stated in the product documentation.
    4. 4. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | | | +| Pass/Fail criteria | In step 4, the PHG under test completes the pairing process successfully. | | | +| Notes | | | | + +| | | | | +|-----------------|---------------------------------------------------------------|------------------------|--| +| TP Id | TP/LP-PAN/PHG/TR/BLEDG/BV-006 | | | +| TP label | Secure Simple Pairing with PHD with DisplayYesNo capabilities | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--| +| | Testable items | Authentication BT LE 2; M | | +| Test purpose | Check that:
    PHG shall support all pairing methods for Bluetooth 4.0, including Just Works and Passkey Entry, if the PHG has the appropriate I/O capabilities. | | | +| Applicability | C_MAN_BLE_000 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in a Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. 1. Check that the PHG under test IO capabilities are declared in PIXIT I_MAN_BDG_002 and that the MITM protection is declared in PIXIT I_MAN_BDG_003
      1. a. IF the PHG under test does not support MITM protection (PIXIT I_MAN_BDG_003 = FALSE) THEN the test tool simulated PHD is configured with Secure Simple Pairing, NoInputNoOutput capabilities and without MITM protection in addition the Just Works Association Model shall be used during the pairing process and the generated link key will be unauthenticated (without MITM protection)
      2. b. IF the PHG under test supports MITM protection (PIXIT I_MAN_BDG_003 = TRUE) THEN
        • • IF the PHG under test supports KeyboardOnly or KeyboardDisplay capabilities (PIXIT I_MAN_BDG_002 = 2 or 3) THEN the test tool simulated PHD is configured with Secure Simple Pairing, DisplayYesNo capabilities and with MITM protection in addition the passkey entry association model shall be used during the pairing process and the generated link key will be authenticated (with MITM protection)
        • • IF the PHG under test supports DisplayOnly or DisplayYesNo capabilities (PIXIT I_MAN_BDG_002 = 0 or 1) THEN it will not pair with PHDs with DisplayYesNo capabilities because they do not fulfil the security level required (i.e., MITM protection) and the test case execution ends by giving a PASS verdict
        • • IF the PHG under test supports NoInputNoOutput capabilities (PIXIT I_MAN_BDG_002 = 4) THEN the combination of IO capabilities and MITM support declared by the PHG under test in PIXITs is not feasible and the test case ends by giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs
    2. 2. Set the test tool simulated PHD in discoverable and pairable mode.
    3. 3. The PHG under test initiates a discovery process as stated in the product documentation.
    4. 4. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | | | +| Pass/Fail criteria | In step 4, the PHG under test completes the pairing process successfully. | | | +| Notes | | | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--| +| TP Id | TP/LP-PAN/PHG/TR/BLEDG/BV-007 | | | +| TP label | Secure Simple Pairing with PHD with KeyboardOnly capabilities | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Authentication BT LE 2; M | | +| Test purpose | Check that:
    PHG shall support all pairing methods for Bluetooth 4.0, including Just Works and Passkey Entry, if the PHG has the appropriate I/O capabilities. | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_BLE_000 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in a Disconnected state and they have not been paired before. | +| Test procedure |
    1. 1. Check that the PHG under test IO capabilities are declared in PIXIT I_MAN_BDG_002 and that the MITM protection is declared in PIXIT I_MAN_BDG_003
      1. a. IF the PHG under test does not support MITM protection (PIXIT I_MAN_BDG_003 = FALSE) THEN the test tool simulated PHD is configured with Secure Simple Pairing, NoInputNoOutput capabilities and without MITM protection and the Just Works Association Model shall be used during the pairing process and the generated link key will be unauthenticated (without MITM protection)
      2. b. IF the PHG under test supports MITM protection (PIXIT I_MAN_BDG_003 = TRUE) THEN
        • • IF the PHG under test supports DisplayOnly or DisplayYesNo or KeyboardOnly or KeyboardDisplay capabilities (PIXIT I_MAN_BDG_002 = 0 or 1 or 2 or 3) THEN the test tool simulated PHD is configured with Secure Simple Pairing, KeyboardOnly capabilities and with MITM protection in addition the passkey entry association model shall be used during the pairing process and the generated link key will be authenticated (with MITM protection)
        • • IF the PHG under test supports NoInputNoOutput capabilities (PIXIT I_MAN_BDG_002 = 4) THEN the combination of IO capabilities and MITM support declared by the PHG under test in PIXITs is not feasible and the test case ends by giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs
    2. 2. Set the test tool simulated PHD in discoverable and pairable mode.
    3. 3. The PHG under test initiates a discovery process as stated in the product documentation.
    4. 4. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.
    | +| Pass/Fail criteria | In step 4, the PHG under test completes the pairing process successfully. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--| +| TP Id | TP/LP-PAN/PHG/TR/BLEDG/BV-008 | | | +| TP label | Secure Simple Pairing with PHD with KeyboardDisplay capabilities | | | +| Coverage | Spec | [b-ITU-T H.810 (2015)] | | +| | Testable items | Authentication BT LE 2; M | | +| Test purpose | Check that:
    PHG shall support all pairing methods for Bluetooth 4.0, including Just Works and Passkey Entry, if the PHG has the appropriate I/O capabilities. | | | +| Applicability | C_MAN_BLE_000 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD support the same device specialization, they are in a Disconnected state and they have not been paired before. | | | +| Test procedure |
    1. 1. Check the PHG under test IO capabilities declared in PIXIT I_MAN_BDG_002 and the MITM protection declared in PIXIT I_MAN_BDG_003
      1. a. IF the PHG under test does not support MITM protection (PIXIT I_MAN_BDG_003 = FALSE) THEN the test tool simulated PHD is configured with Secure Simple Pairing,
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    NoInputNoOutput capabilities and without MITM protection in addition the Just Works Association Model shall be used during the pairing process and the generated link key will be unauthenticated (without MITM protection)

    b. IF the PHG under test supports MITM protection (PIXIT I_MAN_BDG_003 = TRUE) THEN

    • • IF the PHG under test supports DisplayOnly or DisplayYesNo or KeyboardOnly or KeyboardDisplay capabilities (PIXIT I_MAN_BDG_002 = 0 or 1 or 2 or 3) THEN the test tool simulated PHD is configured with Secure Simple Pairing, KeyboardDisplay capabilities and with MITM protection in addition the passkey entry association model shall be used during the pairing process and the generated link key will be authenticated (with MITM protection)
    • • IF the PHG under test supports NoInputNoOutput capabilities (PIXIT I_MAN_BDG_002 = 4) THEN the combination of IO capabilities and MITM support declared by the PHG under test in PIXITs is not feasible and the test case ends giving a FAIL verdict due to inconsistency among the PHD under test SSP features declared in PIXITs

    2. Set the test tool simulated PHD in discoverable and pairable mode.

    3. The PHG under test initiates a discovery process as stated in the product documentation.

    4. Once the simulated PHD has been discovered, make the PHG under test pair with it as stated in the documentation.

    | +| Pass/Fail criteria | In step 4, the PHG under test completes the pairing process successfully. | +| Notes | | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-Bluetooth PHDT] Bluetooth SIG (in force), *Personal Health Devices Transcoding White Paper*. +- [b-BT HDP] Bluetooth Health Device Profile and Multi-Channel Adaptation Protocol. Version 1.0. +[https://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc\\_id=119999](https://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc_id=119999) +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0. (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12): *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] Personal Health Device DG2016 *PICS and PIXIT excel sheet v1.11*. + +- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 *PICS and PIXIT excel sheet v1.9*. + +- [b-TCRL] Test Case Reference List\_DG2016\_v1.11. + +- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8. + +- [b-USB PHDC] USB Personal Healthcare Device Class v1.0 plus (2008), errata. +[http://www.usb.org/developers/docs/devclass\\_docs/Personal\\_Healthcare\\_1.zip](http://www.usb.org/developers/docs/devclass_docs/Personal_Healthcare_1.zip) + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.849-201910-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.849-201910-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f0685c6cac1a6927ab87e5140540a2828cafa0f --- /dev/null +++ b/marked/H/T-REC-H.849-201910-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aec7975d4ac023d4fa78885911d3518d106c635275d19d4dabfa93030206dfd5 +size 4095 diff --git a/marked/H/T-REC-H.849-201910-I_PDF-E/raw.md b/marked/H/T-REC-H.849-201910-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7f19c7275a698ba607b26f1a17d665d1707b7298 --- /dev/null +++ b/marked/H/T-REC-H.849-201910-I_PDF-E/raw.md @@ -0,0 +1,2227 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.849** + +(10/2019) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 9: Transcoding for Bluetooth Low Energy: +Personal Health Devices** + +Recommendation ITU-T H.849 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.849 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 9: Transcoding for Bluetooth Low Energy: Personal Health Devices + +## Summary + +Recommendation ITU-T H.849 provides a test suite structure (TSS) and the test purposes (TP) for the transcoding by personal health devices in the Personal Health Devices (PHD) interface of application-level data between the Bluetooth Low Energy Bluetooth Generic Attribute Profile format and the IEEE 11073-20601 data format, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2017) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.849 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 9: PHD Transcoding Whitepaper. Personal Health Device BLE (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +This 2019 revision provides updates to account for the inclusion of pulse oximeter and continuous glucose monitoring Bluetooth Low Energy profile test cases. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.849 | 2015-01-13 | 16 | 11.1002/1000/12278 | +| 2.0 | ITU-T H.849 | 2016-07-14 | 16 | 11.1002/1000/12956 | +| 3.0 | ITU-T H.849 | 2017-04-29 | 16 | 11.1002/1000/13238 | +| 4.0 | ITU-T H.849 | 2018-08-29 | 16 | 11.1002/1000/13685 | +| 5.0 | ITU-T H.849 | 2019-05-14 | 16 | 11.1002/1000/13910 | +| 6.0 | ITU-T H.849 | 2019-10-17 | 16 | 11.1002/1000/14098 | + +## Keywords + +Bluetooth Generic Attribute Profile, Bluetooth Low Energy (BLE), Conformance testing, Continua Design Guidelines, data format transcoding, e-health, IEEE 11073-20601, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2019 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|-----------------------------------------------------------------------------------|-----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Test suite structure (TSS) ..... | 5 | +| 7 | Electronic attachment ..... | 7 | +| Annex A | Test purposes ..... | 8 | +| A.1 | TP definition conventions..... | 8 | +| A.2 | Subgroup 1.4.1: Whitepaper general requirements (GEN) ..... | 9 | +| A.3 | Subgroup 1.4.2: Whitepaper thermometer requirements (TH) ..... | 11 | +| A.4 | Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) ..... | 13 | +| A.5 | Subgroup 1.4.4: Whitepaper heart rate requirements (HR)..... | 16 | +| A.6 | Subgroup 1.4.5: Whitepaper glucose requirements (GL)..... | 19 | +| A.7 | Subgroup 1.4.6: Whitepaper weight scale requirements (WS) ..... | 25 | +| A.8 | Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) ..... | 39 | +| A.9 | Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) ..... | 77 | +| | Bibliography..... | 115 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 9: PHD Transcoding Whitepaper. Personal Health Device BLE (Version 1.6, 2016-09-20), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2012-10-05 | Initial release for Test Tool DG2011 based on the requirements in [b-CGD 2011]. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_LP-PAN_PART_9_v1.0.doc" as a baseline and adds new features included in [b-CDG 2012]:
    • • BPM and HR profiles
    | +| 1.2 | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_LP-PAN_PART_9_v1.1.doc" as a baseline and adds new features included in [b-ITU-T H.810]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.3 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_LP-PAN_PART_9_v1.2.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row added
    | +| 1.4 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_LP-PAN_PART_9_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015]:
    • • Adds WS/BCA BLE Device Specialization
    • • Adds SABTE IEEE Device Specialization
    | +| 1.5 | 2016-01-26 | First maintenance release for Test Tool DG2015. It uses "TSS&TP_DG2015_LP-PAN_PART_9_v1.4.doc" as a baseline and adds some updates according to the Maintenance 2015 activity. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_9_v1.5.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2016)]/[b-CDG 2016]:
    • • Adds PLX BLE device specialization
    • • Adds CGM BLE device specialization
    | +| 1.7 | 2018-02-27 | Initial release for Test Tool DG2017. It adds some updates and fixes. | +| 1.8 | 2018-10-17 | It uses version 1.7 as a baseline and adds corrections due to the inclusion of PLX and CGM BLE profile test cases. | +| 1.9 | 2019-06-13 | Second maintenance release for Test Tool DG2017. It uses "H.849_201808" as a baseline and adds some updates according to the 2018/2019 maintenance activity. | + +## **Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 9: Transcoding for Bluetooth Low Energy: Personal Health Devices** + +# **1 Scope** + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2017)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 9. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Device. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) + - Part 5Q: Power status monitor (PSM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. Personal Health Device BLE + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 8: Continua Design Guidelines. Personal Health Gateway BLE +- **Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Device** +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2017)] Recommendation ITU-T H.810 (2017), *Interoperability design guidelines for personal health systems*. +- [Bluetooth PHDT v1.4] Bluetooth SIG (2013), *Personal Health Devices Transcoding White Paper, v1.4*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=294539](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=294539) +- [Bluetooth PHDT v1.5] Bluetooth SIG (2014), *Personal Health Devices Transcoding White Paper, v1.5*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=272346](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=272346) +- [Bluetooth PHDT v1.6] Bluetooth SIG (2015), *Personal Health Devices Transcoding White Paper, v1.6*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=310657](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=310657) +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization*. NOTE – Shorthand to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------------|-------------------------------------------------------| +| ATS | Abstract Test Suite | +| BLE | Bluetooth Low Energy | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GATT | Generic Attribute Profile | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| MDS | Medical Device System | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| PSM | Power Status Monitor | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purpose | +| TSS | Test Suite Structure | +| uint8, uint16 | 8 and 16 bits unsigned integer | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +# 5 Conventions + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +– SHALL is equivalent to 'must' or 'it is required to'. + +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +In this document, "0x" denotes a number in hexadecimal format, and "(dec)" after a number indicates it is expressed in decimal format. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2017 | - | 7.0 | Release 2017 of the CDG including maintenance updates of the CDG 2016 and additional guidelines that cover new functionalities. | - | +| 2016 plus errata | [b-ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of H.810 is split into eight parts in the H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|---------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure (TSS) + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 1.4.1 to 1.4.8 (shown in bold). + +– Group 1: Personal Health Device (PHD) + +- Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) +- Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) +- Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + +- Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - **Subgroup 1.4.1: General requirements (GEN)** + - **Subgroup 1.4.2: Thermometer requirements (TH)** + - **Subgroup 1.4.3: Blood pressure requirements (BPM)** + - **Subgroup 1.4.4: Heart rate requirements (HR)** + - **Subgroup 1.4.5: Glucose meter requirements (GL)** + - **Subgroup 1.4.6: Weight scale requirements (WS)** + - **Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX)** + - **Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM)** +- Group 2: Personal Health Gateway (PHG) +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) + - Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) + - Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + +- Subgroup 2.3.6: Cardiovascular (CV) +- Subgroup 2.3.7: Strength (ST) +- Subgroup 2.3.8: Activity hub (HUB) +- Subgroup 2.3.9: Adherence monitor (AM) +- Subgroup 2.3.10: Insulin pump (IP) +- Subgroup 2.3.11: Peak flow (PF) +- Subgroup 2.3.12: Body composition analyser (BCA) +- Subgroup 2.3.13: Basic electrocardiograph (ECG) +- Subgroup 2.3.14: International normalized ratio (INR) +- Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) +- Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: General requirements (GEN) + - Subgroup 2.4.2: Thermometer requirements (TH) + - Subgroup 2.4.3: Blood pressure measurement requirements (BPM) + - Subgroup 2.4.4: Heart rate requirements (HR) + - Subgroup 2.4.5: Glucose meter requirements (GL) + - Subgroup 2.4.6: Weight scale requirements (WS) + - Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) + - Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . See [b-PHD PICS & PIXIT], [b-PHG PICS & PIXIT] and [b-TI]. + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +# Annex A + +## Test purposes + +(This annex forms an integral part of this Recommendation.) + +## A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case: + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) - Local area network (ZigBee) + - LP-PAN: Low power personal area network (BLE) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test. + - BI: Invalid behaviour test. + - : This is a sequential number that identifies the test purpose. +- **TP label:** This is the title of the TP. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP are included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. + +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +## A.2 Subgroup 1.4.1: Whitepaper general requirements (GEN) + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/GEN/BV-000 | | | +| TP label | Whitepaper. Date Time characteristic | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Common MDS 6; O | | +| Test purpose | Check that:
    BLE Personal Health Device (PHD) Date Time characteristic represents the current PHD date and time | | | +| Applicability | C_AG_BLE_000 | | | +| Other PICS | C_AG_BLE_002 | | | +| Initial condition | The PHD under test and the simulated Personal Health Gateway (PHG) are in a Standby state | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The test tool checks the characteristics implemented by the PHD under test
    5. 5. IF the PHD implements the date time characteristic (C_AG_BLE_002) THEN
      1. a. The simulated PHG reads the date time characteristic value
      2. b. The test tool checks that the date time format is correct:
        • • Year: 1900 \leq \text{value} \leq 2100 OR value = 0
        • • Month: 1 \leq \text{value} \leq 12 OR value = 0
        • • Day: 1 \leq \text{value} \leq 31 OR value = 0
        • • Hours: 0 \leq \text{value} \leq 23
        • • Minutes: 0 \leq \text{value} \leq 59
        • • Seconds: 0 \leq \text{value} \leq 59
      3. c. The test operator checks that the date time value is correct
    | | | +| Pass/Fail criteria |

    In step 4, IF PICS C_AG_BLE_002 = TRUE THEN the PHD implements the date time characteristic

    In step 4, IF PICS C_AG_BLE_002 = FALSE THEN the PHD does not implement the date time characteristic

    In step 5.b, the values of date time characteristic fields are within the ranges specified in the test procedure

    In step 5.c, the date time characteristic reports a correct date and time

    | | | +| Notes | | | | + +| | | | | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/GEN/BV-001 | | | | +| TP label | Whitepaper. Current Time Service | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable Items | Common MDS 6; O | | | +| Test purpose |

    Check that:

    Current Time characteristic inside Current Time Service represents the current PHD date and time

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_030 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state)
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state)
    4. 4. Test Tool checks characteristics implemented by the PHD under test
    5. 5. IF PHD implements Current Time Service(C_AG_BLE_030) THEN
      1. a. The simulated PHG reads Current Time characteristic value
      2. b. Test Tool checks that Current Time format is correct:
        • • Year: 1900 \leq \text{value} \leq 2100 OR value = 0
        • • Month: 1 \leq \text{value} \leq 12 OR value = 0
        • • Day: 1 \leq \text{value} \leq 31 OR value = 0
        • • Hours: 0 \leq \text{value} \leq 23
        • • Minutes: 0 \leq \text{value} \leq 59
        • • Seconds: 0 \leq \text{value} \leq 59
        • • Day of Week: 0 \leq \text{value} \leq 7
        • • Fractions256: 0 \leq \text{value} \leq 255
        • • Adjust Reason: 0000????
      3. c. Test Operator checks that Current Time value is correct
    | | | | +| Pass/Fail criteria |

    In Step 4, IF PICS C_AG_BLE_030 = TRUE THEN PHD implements Current Time service

    In Step 4, IF PICS C_AG_BLE_030 = FALSE THEN PHD does not implement Current Time service

    In Step 5.b, values of Current Time characteristic fields are within the ranges specified in Test Procedure

    In Step 5.c, the Current Time characteristic reports a correct Current Time

    | | | | +| Notes
    (to assist manual testing)     |

    To read Current Time characteristic, PHG shall perform a "Read Characteristic Value" Generic attribute profile (GATT) sub-procedure on characteristic with UUID 0x2A2B. The PHG will then receive a Read Response. Check ATT packet value in the received response. (fields will all be present and in the following order):

    | | | | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|
    • • First 2 octets (Year) are between 1900 (0x076C) and 2100 (0x0834) OR they are equal to 0x0000. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
    • • Month (1 octet) will be between 1 (0x01) and 12 (0x0C) OR equal to 0 (0x00).
    • • Day (1 octet) will be between 1 (0x01) and 31 (0x1F) OR equal to 0 (0x00).
    • • Hours (1 octet) will be between 0 (0x00) and 23 (0x17).
    • • Minutes (1 octet) will be between 0 (0x00) and 59 (0x3B).
    • • Seconds (1 octet) will be between 0 (0x00) and 59 (0x3B).
    • • Day of Week (1 octet) will be between 0 (0x00) and 7 (0x07).
    • • Fractions256 (1 octet) will be between 0 (0x00) and 255 (0xFF)
    • • Adjust Reason field (8bit) will have bits 0-3 set to 0 or 1 and bits 4-7 set to 0.
    | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### A.3 Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/TH/BV-000 | | | +| TP label | Whitepaper. Temperature measurement value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Float Type 1; C | TH Numeric 7; M | +| Test purpose | Check that:

    Temperature Measurement Value field in Temperature Measurement characteristic represents the measurement value acquired by BLE PHD | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_001 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a temperature measurement to the simulated PHG
    5. 5. The test tool checks the measurement sent by the PHD under test
      1. a. IF the Temperature Units Flag = 0 (Temp in °C) THEN
        • • Check that the temperature reported in the Temperature Measurement Value (Celsius) field is coherent: 25 < \text{value} < 50
        • • The test operator checks that the temperature reported in the Temperature Measurement Value (Celsius) field is correct (value and units)
      2. b. IF the Temperature Units Flag = 1 (Temp in °F) THEN
        • • Check that the temperature reported in the Temperature Measurement Value (Fahrenheit) field is coherent: 75 < \text{value} < 125
        • • The test operator checks that the temperature reported in the Temperature Measurement Value (Fahrenheit) field is correct (value and units)
    | | | +| Pass/Fail criteria | In step 5.a, the value in the Temperature Measurement Value (Celsius) field is within the range specified in the test procedure and the value is correct.

    In step 5.b, the value in the Temperature Measurement Value (Fahrenheit) field is within the range specified in the test procedure and the value is correct. | | | +| Notes | | | | + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/TH/BV-001 | | | +| TP label | Whitepaper. Temperature time stamp value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Date-Time Conv 1; M | TH Numeric 10; M | +| Test purpose | Check that:

    Time Stamp field in Temperature Measurement characteristic represents the instant of time when BLE PHD acquired the measurement | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_001 | | | +| Other PICS | C_AG_BLE_003 | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a temperature measurement to the simulated PHG
    5. 5. The test tool checks the measurement sent by the PHD under test
      1. a. IF C_AG_BLE_003 = TRUE (time stamp is reported) THEN
        • • The test tool checks that the Time Stamp Flag = 1
        • • The test tool checks that the time stamp reported in the Time Stamp field is coherent:
          • - Year: 1900 ≤ value ≤ 2100 OR value = 0
          • - Month: 1 ≤ value ≤ 12 OR value = 0
          • - Day: 1 ≤ value ≤ 31 OR value = 0
          • - Hours: 0 ≤ value ≤ 23
          • - Minutes: 0 ≤ value ≤ 59
          • - Seconds: 0 ≤ value ≤ 59
        • • The test operator checks that the time stamp reported in the Time Stamp field is correct (value and units)
      2. b. IF C_AG_BLE_003 = FALSE (the time stamp is not reported) THEN
        • • the test tool checks that Time Stamp Flag = 0
    | | | +| Pass/Fail criteria | In step 5.a, the time stamp is reported, the value of the Time Stamp field is within the range specified in the test procedure and the value is correct.

    In step 5.a, the time stamp is not reported | | | +| Notes | | | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/TH/BV-002 | | | +| TP label | Whitepaper. Temperature type value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | TH Numeric 3; M | | +| Test purpose | Check that:

    The Temperature Type field in the Temperature Measurement characteristic or Temperature Type characteristic represent the location on the human body at which the temperature was measured by the BLE PHD | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_AG_BLE_000 AND C_AG_BLE_001 | +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a temperature measurement to the simulated PHG
    5. 5. The test tool checks the measurement sent by the PHD under test.
      1. a. IF Temperature Type Flag = 1 (Temperature Type field present) THEN check that the Temperature Type field value is correct: 1 \leq \text{value} \leq 9
      2. b. IF the Temperature Type Flag = 0 (Temperature Type field not present) THEN the simulated PHG reads the temperature type characteristic (if it is implemented) and checks that its value is correct: 1 \leq \text{value} \leq 9
    | +| Pass/Fail criteria |

    In step 5.a, the value of the Temperature Type field is within the range specified in the test procedure.

    In step 5.b, the value of the temperature type characteristic (if it is implemented) is within the range specified in the test procedure.

    | +| Notes | | + +### A.4 Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/BPM/BV-000 | | | +| TP label | Whitepaper. Blood Pressure Measurement value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Short Float Type 1; C | BP Numeric 6; M | +| Test purpose |

    Check that:

    Blood Pressure Measurement Value fields (systolic, diastolic and MAP) in Blood Pressure Measurement characteristic represents the measurement value acquired by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_004 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a blood pressure measurement to the simulated PHG.
    5. 5. The test tool checks the measurement sent by the PHD under test
      1. a. IF the Blood Pressure Units Flag = 0 (mmHg) THEN
        • • Check that the systolic value reported in the Blood Pressure Measurement Value (mmHg) field is coherent: 20 < \text{value} < 200
        • • Check that the diastolic value reported in the Blood Pressure Measurement Value (mmHg) field is coherent: 20 < \text{value} < 200
        • ▪ Check that the MAP reported in the Blood Pressure Measurement Value (mmHg) field is coherent: 20 < \text{value} < 200
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ▪ The test operator checks that the systolic value reported in the Blood Pressure Measurement Value (mmHg) field is correct (value and units)
    • ▪ The test operator checks that the diastolic value reported in the Blood Pressure Measurement Value (mmHg) field is correct (value and units)
    • • The test operator checks that the mean arterial pressure (MAP) value reported in the Blood Pressure Measurement Value (mmHg) field is correct (value and units)

    b. IF Blood Pressure Units Flag = 1 (kPa) THEN

    • • Check that the systolic value reported in the Blood Pressure Measurement Value (kPa) field is coherent: 2.66 < \text{value} < 26.66
    • • Check that the diastolic value reported in the Blood Pressure Measurement Value (kPa) field is coherent: 2.66 < \text{value} < 26.66
    • • Check that the MAP value reported in the Blood Pressure Measurement Value (kPa) field is coherent: 2.66 < \text{value} < 26.66
    • • The test operator checks that the systolic value reported in the Blood Pressure Measurement Value (kPa) field is correct (value and units)
    • • The test operator checks that the diastolic value reported in the Blood Pressure Measurement Value (kPa) field is correct (value and units)
    • • The test operator checks that the MAP value reported in the Blood Pressure Measurement Value (kPa) field is correct (value and units)
    | +| Pass/Fail criteria |

    In step 5.a, the values of the Blood Pressure Measurement Compound Value (mmHg) fields are within the range specified in the test procedure and the values are correct.

    In step 5.b, the values of the Blood Pressure Measurement Compound Value (kPa) fields are within the range specified in the test procedure and the values are correct.

    | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/BPM/BV-001 | | | +| TP label | Whitepaper. Blood Pressure Measurement, Time Stamp value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Date-Time Conv 1; M | BP Numeric 9; M | +| Test purpose |

    Check that:

    Time Stamp field in Blood Pressure Measurement characteristic represents the instant of time when BLE PHD acquired the measurement

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_004 | | | +| Other PICS | C_AG_BLE_005 | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a blood pressure measurement to the simulated PHG.
    5. 5. The test tool checks measurement sent by the PHD under test
      1. a. IF C_AG_BLE_005 = TRUE (time stamp is reported) THEN
        • • the test tool checks that Time Stamp Flag = 1
        • • the test tool checks that the time stamp reported in Time Stamp field is coherent:
          • - Year: 1900 \leq \text{value} \leq 2100 OR value = 0
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • - Month: 1 \leq \text{value} \leq 12 OR value = 0
    • - Day: 1 \leq \text{value} \leq 31 OR value = 0
    • - Hours: 0 \leq \text{value} \leq 23
    • - Minutes: 0 \leq \text{value} \leq 59
    • - Seconds: 0 \leq \text{value} \leq 59
    • • the test operator checks that the time stamp reported in the Time Stamp field is correct (value and units)

    b. IF C_AG_BLE_005 = FALSE (time stamp is not reported) THEN

    • • the test tool checks that Time Stamp Flag = 0
    | +| Pass/Fail criteria |

    In step 5.a, the time stamp is reported, the value of the Time Stamp field is within the range specified in the test procedure and the value is correct.

    In step 5.b, the time stamp is not reported.

    | +| Notes | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/BPM/BV-002 | | | | +| TP label | Whitepaper. Blood Pressure Measurement, Pulse Rate value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | Short Float Type 1; C | PR Numeric 7; M | | +| Test purpose |

    Check that:

    Pulse Rate field in Blood Pressure Measurement characteristic may be present if PHD under test supports Pulse Rate measurements, if it is present then its value represents the measurement value acquired by BLE PHD

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_004 | | | | +| Other PICS | C_AG_BLE_006 | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a blood pressure measurement to the simulated PHG.
    5. 5. The test tool checks the measurement sent by the PHD under test
      1. a. IF C_AG_BLE_006 = TRUE (the PHD reports the pulse rate) THEN
        • • the test tool checks that Pulse Rate Flag = 1
        • • the test tool checks that the pulse rate reported in the Pulse Rate field is coherent: 20 \leq \text{value} \leq 250
        • • the test operator checks that the pulse rate reported in the Pulse Rate field is correct (value and units)
      2. b. IF C_AG_BLE_006 = FALSE (the PHD does not report the pulse rate) THEN
        • • the test tool checks that the Pulse Rate Flag = 0
        • • the test tool checks that the Pulse Rate field is not reported
    | | | | +| Pass/Fail criteria |

    In step 5.a, the pulse rate is reported, the value of the Pulse Rate field is within the range specified in the test procedure and the value is correct.

    In step 5.b, the pulse rate is not reported.

    | | | | +| Notes | | | | | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/BPM/BV-003 | | | +| TP label | Whitepaper. Blood Pressure Measurement, User ID value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | UserID 2; O | | +| Test purpose | Check that:
    User ID field in Blood Pressure Measurement characteristic shall be present if PHD under test supports multiple users | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_004 | | | +| Other PICS | C_AG_BLE_007 | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a blood pressure measurement to the simulated PHG.
    5. 5. The test tool checks the measurement sent by the PHD under test
      1. a. IF C_AG_BLE_007 = TRUE (PHD supports multiple users) THEN
        • • the test tool checks that the User ID Flag = 1
        • • the test tool checks that the User ID field is reported
        • • the test operator checks that the User ID reported in the User ID field is correct
      2. b. IF C_AG_BLE_007 = FALSE (the PHD does not support multiple users) THEN
        • • the test tool checks that User ID Flag = 0
        • • the test tool checks that the User ID field value is not reported
    | | | +| Pass/Fail criteria | In step 5.a, the User ID is reported and the value is correct.
    In step 5.b, the User ID is not reported. | | | +| Notes | | | | + +### A.5 Subgroup 1.4.4: Whitepaper heart rate requirements (HR) + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/HR/BV-000 | | | +| TP label | Whitepaper. Heart Rate Measurement value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | HR Numeric 6; M | | +| Test purpose | Check that:
    Heart Rate Measurement Value field in Heart Rate Measurement characteristic represents the measurement value acquired by BLE PHD | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_015 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    2. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    3. 4. The PHD under test sends a heart rate measurement to the simulated PHG.
    4. 5. The test tool checks the measurement sent by the PHD under test
      1. a. IF Heart Rate Value Format Flag = 0 (Heart Rate Value Format is set to uint8) THEN
        • • Check that the heart rate reported in the Heart Rate Measurement Value (uint8) field is codified in uint8 format and its value is coherent: 20 < \text{value} < 250
        • • The test operator checks that the heart rate reported in the Heart Rate Measurement Value (uint8) field is correct (value and units)
      2. b. IF Heart Rate Value Format Flag = 1 (Heart Rate Value Format is set to uint16) THEN
        • • Check that the heart rate reported in the Heart Rate Measurement Value (uint16) field is codified in uint16 format and its value is coherent: 20 < \text{value} < 250
        • • The test operator checks that the heart rate reported in the Heart Rate Measurement Value (uint16) field is correct (value and units)
    | +| Pass/Fail criteria |

    In step 5.a, the value of Heart Rate Measurement (uint8) field is within the range specified in the test procedure and the value is correct.

    In step 5.b, value of the Heart Rate Measurement Value (uint16) field is within the range specified in the test procedure and the value is correct.

    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/HR/BV-002 | | | +| TP label | Whitepaper. Heart Rate Measurement, RR-Interval values | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | HR Numeric 6; M | | +| Test purpose |

    Check that:

    RR-Interval field in Heart Rate Measurement characteristic may be present if PHD under test supports RR-Interval measurements, if it is present then its value represents the measurement value acquired by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_015 | | | +| Other PICS | C_AG_BLE_017 | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a heart rate measurement to the simulated PHG
    5. 5. The test tool checks the measurement sent by the PHD under test
      1. a. IF C_AG_BLE_017 = TRUE (PHD reports RR-Interval) THEN
        • • the test tool checks that RR-Interval Flag = 1
        • • the test tool checks that the RR-Interval values reported in the RR-Interval field are coherent: 250 \leq \text{value} \leq 3000 [ticks]
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • the test operator checks that the RR-Interval values reported in the RR-Interval field are correct

    b. IF C_AG_BLE_017 = FALSE (the PHD does not report the RR-Interval) THEN

    • the test tool checks that RR-Interval Flag = 0
    • the test tool checks that the RR-Interval field is not reported
    | +| Pass/Fail criteria |

    In step 5.a, the RR-Interval is reported, the values of the RR-Interval field are within the range specified in the test procedure and the values are correct

    In step 5.b, the RR-Interval is not reported

    | +| Notes | | + +| | | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/HR/BV-003 | | | | +| TP label | Whitepaper. Heart Rate Measurement, energy expended values | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Energy Numeric 6; M | | | +| Test purpose |

    Check that:

    Energy Expended field in Heart Rate Measurement characteristic may be present if PHD under test supports Energy Expended measurements, if it is present then its value represents the measurement value acquired by BLE PHD

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_015 | | | | +| Other PICS | C_AG_BLE_031 | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | | | | +| Test procedure |
    1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state)
    2. The simulated PHG initiates discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with PHD under test (Initiating state)
    3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. The PHD under test sends a Heart Rate measurement to Simulated PHG
    5. Test Tool checks measurement sent by PHD under test
      1. IF C_AG_BLE_031 = TRUE (PHD reports Energy Expended) THEN
        • Test Tool checks that Energy Expended Flag = 1
        • Test Tool checks that Energy Expended values reported in Energy Expended field are coherent: XXX \leq \text{value} \leq XXX
        • Test Operator checks that Energy Expended values reported in Energy Expended field are correct
      2. IF C_AG_BLE_031 = FALSE (PHD does not report Energy Expended) THEN
        • Test Tool checks that Energy Expended Flag = 0
        • Test Tool checks that Energy Expended field is not reported
    | | | | +| Pass/Fail criteria |

    In Step 5.a, Energy Expended is reported, values of Energy Expended field are within the range specified in Test Procedure and the values are correct

    In Step 5.b, Energy Expended is not reported

    | | | | +| Notes | | | | | + +### A.6 Subgroup 1.4.5: Whitepaper glucose requirements (GL) + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/GL/BV-000 | | | +| TP label | Whitepaper. Glucosemeter, Glucose Concentration value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Float Type 1; C | GL Numeric 4; M | +| Test purpose | Check that:
    Glucose Measurement – Glucose Concentration value field in Glucose Measurement characteristic represents the measurement value acquired by BLE PHD | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_008 | | | +| Other PICS | C_AG_BLE_010 | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | +| Test procedure |
    1. 1. Ask the operator to acquire a glucose concentration measurement.
    2. 2. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The simulated PHG requests the PHD under test to report stored records by performing a writing operation in the record access control point (RACP).
    6. 6. The PHD under test sends a glucose measurement to the simulated PHG.
    7. 7. The test tool checks the measurement sent by the PHD under test
      1. a. IF C_AG_BLE_010 = TRUE (the PHD reports the glucose concentration, type and sample location) THEN the test tool checks that the Glucose Concentration, Type and Sample Location Present Flag = 1
        1. i. IF Glucose Concentration Units Flag = 0 THEN
          • • the test tool checks that the glucose concentration reported in the Glucose Measurement field is coherent: 0,0002 \leq \text{value} \leq 0,003 (kg/L)
          • • the test operator checks that the glucose concentration reported in the glucose measurement (kg/L) is correct (value and units)
        2. ii. IF the Glucose Concentration, Type and Sample Location Present Flag = 1 AND the Glucose Concentration Units Flag = 1 THEN
          • • the Test Tool checks that the glucose concentration reported in the glucose measurement is coherent: 0,001 \leq \text{value} \leq 0,017 (mol/L)
          • • the test operator checks that the glucose concentration reported in the glucose measurement (mol/L) is correct (value and units)
      2. b. IF C_AG_BLE_010 = FALSE (the PHD reports the glucose concentration, type and sample location) THEN
        • • the test tool checks that the Glucose Concentration, Type and Sample Location Present Flag = 0
        • • the test tool checks that the glucose concentration is not reported
    | | | +| Pass/Fail criteria |

    In step 7.a.i, the value of the Glucose Concentration field (kg/L) is within the range specified in the test procedure and the value is correct.

    In step 7.a.ii, the value of the Glucose Concentration field (mol/L) is within the range specified in the test procedure and the value is correct.

    In step 7.b, the glucose concentration is not reported.

    | | | +| Notes | | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/GL/BV-001 | | | | +| TP label | Whitepaper. Glucometer, Base Time and Time Offset values | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 5; M | Date-Time Conv 1; M | | +| Test purpose |

    Check that:

    Base Time field in Glucose Measurement characteristic represents the value of an internal real-time clock or equivalent that keeps time relative to its initial setting in resolution of seconds

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_008 | | | | +| Other PICS | C_AG_BLE_009 | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | | +| Test procedure |
    1. 1. Ask the operator to acquire a glucose concentration measurement.
    2. 2. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The simulated PHG requests the PHD under test to report stored records by performing a writing operation in the record access control point (RACP).
    6. 6. The PHD under test sends a glucose measurement to the simulated PHG.
    7. 7. The test tool checks the measurement sent by the PHD under test
      1. a. the test tool checks that the time stamps reported in the Base Time field and the Time Offset field (if present) are coherent
        • • The Base Time field is present and its value is:
          • - Year: 1900 \leq \text{value} \leq 2100
          • - Month: 1 \leq \text{value} \leq 12
          • - Day: 1 \leq \text{value} \leq 31 Hours: 0 \leq \text{value} \leq 23
          • - Minutes: 0 \leq \text{value} \leq 59
          • - Seconds: 0 \leq \text{value} \leq 59
        • • IF C_AG_BLE_009 = TRUE (the PHD reports the time offset) THEN Time Offset Flag may be set to 1, the Time Offset field may be present and its value is: -1440 \leq \text{value} \leq 1440 (minutes)
        • • IF C_AG_BLE_009 = FALSE (the PHD does not report the time offset) THEN Time Offset Flag = 0 and the Time Offset field is not present
      2. b. the test operator checks that the time stamp reported in the Base Time field and the Time Offset field are correct (value and units)
        • • IF the Time Offset field is not present or its value is 0x0000, THEN the time stamp matches with the Base Time field
        • • IF the Time Offset field is present and its value is other than 0x0000 THEN the time stamp equals base time + time offset.
    | | | | +| Pass/Fail criteria |

    In step 7.a, the base time is reported and the time offset may be reported, the values of the Base Time field and the Time Offset field are within the ranges specified in the test procedure.

    In step 7.b, the time stamp value is correct.

    | | | | +| Notes | | | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/GL/BV-002 | | | | +| TP label | Whitepaper. Glucosemeter, Type and Sample Location values | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 2; M | GL Enumeration 15; M | | +| Test purpose |

    Check that:

    The Type nibble and the Sample Location nibble comprise one octet. Therefore, when one nibble is present, both nibbles shall be present

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_008 | | | | +| Other PICS | C_AG_BLE_010 | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | | +| Test procedure |
    1. 1. Ask the operator to acquire a glucose concentration measurement and include the type and sample location information.
    2. 2. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The simulated PHG requests the PHD under test to report stored records by performing a writing operation in the record access control point (RACP).
    6. 6. The PHD under test sends a glucose measurement to the simulated PHG.
    7. 7. The test tool checks the measurement sent by the PHD under test
      1. a. IF C_AG_BLE_010 = TRUE (the PHD reports the glucose concentration, type and sample location) THEN
        • • the test tool checks that Glucose Concentration, Type and Sample Location Flag = 1
        • • the test tool checks that the Type field value reported in the glucose measurement is present, and is set to allowed values: 1 \leq \text{value} \leq 10 (dec)
        • • the test operator checks that the Type field value reported in the glucose measurement is correct
        • • the test tool checks that the Sample Location field reported in glucose measurement is present and is set to allowed values: 1 \leq \text{value} \leq 4 (dec) OR value = 15 (dec)
        • • the test operator checks that the sample location reported in the glucose measurement is correct
      2. b. IF C_AG_BLE_010 = FALSE (the PHD does not report the glucose concentration, type and sample location) THEN
        • • the test tool checks that Glucose Concentration, Type and Sample Location Flag = 0
        • • the test tool checks that the Glucose Concentration, Type and Sample Location field is not reported
    | | | | +| Pass/Fail criteria |

    In step 7.a, value of Type and Sample Location fields are within the range specified in the test procedure and the values are correct.

    In step 7.b, Type and Sample Location fields are not present

    | | | | +| Notes | | | | | + +| | | | | | +|-----------------|------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/GL/BV-003 | | | | +| TP label | Whitepaper. Glucosemeter, Sensor Status Annunciation value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--| +| | Testable items | GL Enumeration 15; M | | | +| Test purpose | Check that:
    If Sensor Status Annunciation field is sent, it is set to a valid value. | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_008 | | | | +| Other PICS | C_AG_BLE_011 | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state | | | | +| Test procedure |
    1. 1. Ask the operator to acquire a glucose concentration measurement and include, if it is possible, the Sensor Status Annunciation information.
    2. 2. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The simulated PHG requests the PHD under test to report stored records by performing a writing operation in the record access control point (RACP).
    6. 6. The PHD under test sends a glucose measurement to the simulated PHG
    7. 7. The test tool checks the measurement sent by the PHD under test
      1. a. IF C_AG_BLE_011 = TRUE (the PHD reports the sensor status annunciation) THEN
        • • the test tool checks that the Sensor Status Annunciation Flag = 1
        • • the test tool checks that the Sensor Status Annunciation field reported in the glucose measurement is present, and is set to allowed values: Bits 0 to 11 may be set to 0 or 1, Bits 11 to 15 must be set to 0
        • • the test operator checks that the Sensor Status Annunciation reported in the glucose measurement is correct
      2. b. IF C_AG_BLE_011 = FALSE (the PHD does not report sensor status annunciation) THEN
        • • the test tool checks that the Sensor Status Annunciation flag = 0
        • • the test tool checks that the Sensor Status Annunciation field is not reported
    | | | | +| Pass/Fail criteria | In step 7.a, the value of the Sensor Status Annunciation field is within the range specified in the test procedure and the value is correct.
    In step 7.b, the Sensor Status Annunciation field is not present | | | | +| Notes | | | | | + +| | | | | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/GL/BV-004 | | | | +| TP label | Whitepaper. Glucosimeter, Blood Glucose Concentration below the capabilities of the device sensor | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 6; M | | | +| Test purpose | Check that:
    IF a Blood Glucose Concentration is below the capabilities of the device sensor, it shall be indicated with a value of -INFINITY
    [AND]
    IF present, bit 6 of Sensor Status Annunciation field is set to 1 | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_008 | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | +| Test procedure |
    1. 1. Ask the operator to remove all stored measurements and then to place in a device sensor a blood sample with a blood glucose level below the capabilities of the device sensor. In addition, ask the operator to acquire a glucose concentration measurement and include, if it is possible, the Sensor Status Annunciation information.
    2. 2. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The simulated PHG requests the PHD under test to report stored records by performing a writing operation in the record access control point (RACP).
    6. 6. The PHD under test sends a glucose measurement to the simulated PHG.
    7. 7. The test tool checks the measurement sent by the PHD under test
      1. a. Glucose Concentration field
      2. b. IF the Sensor Status Annunciation field is present THEN Bit 6 = 1
    | +| Pass/Fail criteria |

    In step 7.a, the value of the Glucose Concentration field is set to 0x0802 (-INFINITY)

    In step 7.b, bit 6 of Sensor Status Annunciation field (the sensor result is lower than the device can process) is set to 1

    | +| Notes | The vendor must provide a blood sample (or a simulated blood solution) with a blood glucose level below the capabilities of device sensor. | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/GL/BV-005 | | | +| TP label | Whitepaper. Glucosimeter, Blood Glucose Concentration above the capabilities of the device sensor | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 6; M | | +| Test purpose |

    Check that:

    IF a Blood Glucose Concentration is above the capabilities of the device sensor, it shall be indicated with a value of +INFINITY

    [AND]

    IF present, bit 5 of Sensor Status Annunciation field is set to 1

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_008 AND C_AG_BLE_010 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | +| Test procedure |
    1. 1. Ask the operator to remove all stored measurements and then to place in a device sensor a blood sample with a blood glucose level above the capabilities of device sensor. In addition, ask the operator to acquire a glucose concentration measurement and include, if it is possible, the Sensor Status Annunciation information.
    2. 2. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The simulated PHG requests the PHD under test to report stored records by performing a writing operation in the record access control point (RACP).
    6. 6. The PHD under test sends a glucose measurement to the simulated PHG.
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 7. The test tool checks the measurement sent by the PHD under test
    1. Glucose Concentration field
    2. IF the Sensor Status Annunciation field is present then Bit 5 = 1
    | +| Pass/Fail criteria | In step 7.a, the value of the Glucose Concentration field is set to 0x07FE (+INFINITY)
    In step 7.b, bit 5 of the Sensor Status Annunciation field (the sensor result higher than the device can process) is set to 1 | +| Notes | The vendor must provide a blood sample (or a simulated blood solution) with a blood glucose level above the capabilities of device sensor. | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/GL/BV-006 | | | +| TP label | Whitepaper. Glucosemeter Context values | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 11; M | GL Numeric 17; M | +| | | GL Numeric 31; M | GL Enumeration 10; M | +| | | GL Enumeration 25; M | GL Enumeration 20; M | +| Test purpose | Check that:
    If Glucose Measurement Context is sent, it is set to a valid value. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_008 | | | +| Other PICS | C_AG_BLE_012 | | | +| Initial condition | The PHD under test and the simulated PHG are in a Standby state. | | | +| Test procedure |
    1. Ask the operator to acquire a glucose concentration measurement and include, if it is possible, as much as possible of Glucose measurement context information (Carbohydrate ID, Carbohydrate (kg), Meal, Tester, Health, Exercise duration, Exercise intensity, Medication ID, Medication (kg or l) and/or HbA1c).
    2. Turn on the PHD under test and configure it as a discoverable Bluetooth device (Advertising state).
    3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. The simulated PHG requests the PHD under test to report stored records by performing a writing operation in the record access control point (RACP).
    6. The PHD under test sends a glucose measurement followed by a Glucose measurement context to the simulated PHG
    7. The test tool checks the measurement sent by the PHD under test
      1. IF Context Information Follows Flag = 1 from Glucose Measurement Flags field THEN
        1. Check that the Glucose measurement is followed by a Glucose Measurement Context
        2. Check that the Glucose Measurement Context includes at least one field in addition to the Flags field and the Sequence Number field
        3. Check that the sequence number value from Glucose measurement context is the same as the value of the sequence number of its corresponding glucose measurement characteristic
        4. Check that IF Extended Flags Present Flag = 1, THEN Extended Flags field is present, and is set to 00000000
        5. Check that IF Carbohydrate ID And Carbohydrate Present Flag = 1, THEN
          • Carbohydrate ID and Carbohydrate fields are present, and Carbohydrate ID is set to allowed values (Carbohydrate ID: 1 \leq \text{value} \leq 7) and Carbohydrate is set to a coherent value (0 < \text{carbohydrate (kg)} < 0.4)
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • The test operator checks that the Carbohydrate ID and Carbohydrate reported in the Glucose measurement context are correct

    vi. Check that IF Meal Present Flag = 1, THEN

    • Meal field is present, and is set to allowed values (1 \leq \text{value} \leq 5 (dec))
    • the test operator checks that Meal reported in the Glucose measurement context is correct

    vii. Check that IF Tester-Health Present Flag = 1, THEN

    • Tester and Health fields are present and they are set to allowed values (Tester: 0 \leq \text{value} \leq 3 (dec) OR value = 15 (dec), Health: 0 \leq \text{value} \leq 5 (dec) OR value = 15)
    • the test operator checks that the Tester-Health reported in the Glucose measurement context is correct

    viii. Check that IF Exercise Duration And Exercise Intensity Present Flag = 1, THEN

    • Exercise Duration And Exercise Intensity fields are present, and Exercise intensity is set to allowed values (0 \leq \text{Exercise intensity (\%)} \leq 100)
    • the test operator checks that Exercise duration and Exercise intensity reported in the Glucose measurement context is correct

    ix. Check that IF Medication ID and Medication Present Flag = 1, THEN

    • Medication ID and Medication fields are present. If Medication Value Units Flag = 1, Medication is set in kilograms; else, Medication is set in litres. Medication ID is set to allowed values (1 \leq \text{Medication ID} \leq 5 (dec))
    • the test operator checks that the Medication ID and Medication reported in the Glucose measurement context is correct and Medication is set to a coherent value (0 < \text{Medication (l)} < 0.000002 or 0 < \text{Medication (kg)} < 0.000002)

    x. Check that IF HbA1c Present Flag = 1, THEN

    • HbA1c field is present, and is set to allowed values (0 \leq \text{HbA1c (\%)} \leq 100)
    • the test operator checks that HbA1c reported in the Glucose measurement context is correct

    b. IF Context Information Follows Flag = 0 from Glucose Measurement Flags field THEN Check that Glucose measurement is not followed by a Glucose measurement context

    | +| Pass/Fail criteria |

    In step 7.a, the Glucose measurement is followed by Glucose Measurement Context and it fulfils requisites described in the test procedure.

    In step 7.b, the Glucose Measurement Context is not received

    | +| Notes | | + +### A.7 Subgroup 1.4.6: Whitepaper weight scale requirements (WS) + +| | | | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-000 | | | +| TP label | Whitepaper. Weight Measurement, Weight value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Float Type 1; C | Weight Numeric 4; M | +| Test purpose |

    Check that:

    Weight Measurement Value field in Weight Measurement characteristic represents the measurement value acquired by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_018 | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in the Standby state | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Weight measurement to the simulated PHG.
    5. 5. Test Tool checks measurement sent by PHD under test
      1. a. IF Weight Units Flag = 0 (Kg) THEN
        • • Check that Weight reported in Weight Measurement Value (Kg) field is coherent: 200 [1 kg] < value < 200000 [1000 kg]
        • • Test Operator checks that Weight reported in Weight Measurement Value (Kg) field is correct (value and units)
      2. b. IF Weight Units Flag = 1 (lb) THEN
        • • Check that Weight reported in Weight Measurement Value (lb) field is coherent: 220 [2.2 lb] < value < 220000 [2200 lb]
        • • Test Operator checks that Weight reported in Weight Measurement Value (lb) field is correct (value and units)
    | +| Pass/Fail criteria |

    In Step 5.a, values of Weight Measurement Weight Value (Kg) fields are within the range specified in Test Procedure and the values are correct.

    In Step 5.b, values of Weight Measurement Weight Value (lb) fields are within the range specified in Test Procedure and the values are correct.

    | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-001 | | | +| TP label | Whitepaper. Weight Measurement, Time Stamp value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Date-Time Conv 1; M | Weight Numeric 6; M | +| | | BMI Numeric 6; M | Height Numeric 6; M | +| Test purpose |

    Check that:

    Time Stamp field in Weight Measurement characteristic represents the instant of time when BLE PHD acquired the measurement

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_018 | | | +| Other PICS | C_AG_BLE_020 | | | +| Initial condition | The PHD under test and the simulated PHG are in the Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with PHD under test (Connection state).
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. The PHD under test sends a Weight Measurement to the simulated PHG.

    5. Test Tool checks the measurement sent by the PHD under test

    a. IF C_AG_BLE_020 = TRUE (time stamp is reported) THEN

    • • Test Tool checks that Time Stamp Flag = 1
    • • Test Tool checks that Time Stamp reported in Time Stamp field is coherent:
      • - Year: 1900 ≤ value ≤ 2100 OR value = 0
      • - Month: 1 ≤ value ≤ 12 OR value = 0
      • - Day: 1 ≤ value ≤ 31 OR value = 0
      • - Hours: 0 ≤ value ≤ 23
      • - Minutes: 0 ≤ value ≤ 59
      • - Seconds: 0 ≤ value ≤ 59
    • • Test Operator checks that Time Stamp reported in Time Stamp field is correct (value and units)

    b. IF C_AG_BLE_020 = FALSE (time stamp is not reported) THEN

    • • Test Tool checks that Time Stamp Flag = 0
    | +| Pass/Fail criteria |

    In Step 5.a, Time Stamp is reported, value of Time Stamp field is within the range specified in Test Procedure and the value is correct.

    In Step 5.b, Time Stamp is not reported

    | +| Notes | | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-002 | | | | +| TP label | Whitepaper. Weight Measurement, Height and BMI values | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | Float Type 1; C | Height Numeric 4; M | Height Numeric 7; M | +| Test purpose |

    Check that:

    Height field in Weight Measurement characteristic may be present if PHD under test supports Weight measurements, if it is present then its value represents the measurement value acquired by BLE PHD

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_018 | | | | +| Other PICS | C_AG_BLE_021 | | | | +| Initial condition | The PHD under test and the simulated PHG are in the Standby state. | | | | +| Test procedure |

    1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).

    2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with PHD under test (Initiating state).

    3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).

    4. The PHD under test sends a Weight measurement to the simulated PHG.

    5. Test Tool checks the measurement sent by the PHD under test

    a. IF C_AG_BLE_021 = TRUE (PHD reports Height and BMI) THEN

    • • Test Tool checks that BMI and Height Flag = 1
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • a. IF Height Units Flag = 0 (m) THEN
      • - Check that Height reported in Weight Measurement Value (m) field is coherent: 1400 [1.40 m] < value < 2300 [2.30 m]
      • - Test Operator checks that Height reported in Weight Measurement Value (m) field is correct (value and units)
    • b. IF Height Units Flag = 1 (in) THEN
      • - Check that Height reported in Weight Measurement Value (in) field is coherent: 551 [55.1 in] < value < 906 [90.6 in]
      • - Test Operator checks that Height reported in Weight Measurement Value (in) field is correct (value and units)
    • • Test Tool checks that BMI reported in BMI field is coherent: 15 \le value \le 40
    • • Test Operator checks that BMI reported in BMI field is correct (value and units)

    b. IF C_AG_BLE_021 = FALSE (PHD does not report Height and BMI) THEN

    • • Test Tool checks that BMI and Height Flag = 0
    • • Test Tool checks that Height and BMI fields are not reported
    | +| Pass/Fail criteria |

    In Step 5.a, Height and BMI are reported, values of Height and BMI field are within the range specified in Test Procedure and the values are correct

    In Step 5.b, Height and BMI are not reported

    | +| Notes | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-003 | | | +| TP label | Whitepaper. Weight Measurement, BMI value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Float Type 1; C | BMI Numeric 4; M
    BMI Numeric 7; M | +| Test purpose |

    Check that:

    BMI field in Weight Measurement characteristic may be present if PHD under test supports BMI measurements, if it is present then its value represents the measurement value acquired by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_018 | | | +| Other PICS | C_AG_BLE_022 | | | +| Initial condition | The PHD under test and the simulated PHG are in the Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Weight measurement to the simulated PHG.
    5. 5. Test Tool checks measurement sent by PHD under test
      • a. IF C_AG_BLE_022 = TRUE (PHD reports BMI) THEN
        • • Test Tool checks that BMI and Height Flag = 1
        • • Test Tool checks that BMI reported in BMI field is coherent: 15 \le value \le 30
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Test Operator checks that BMI reported in BMI field is correct (value and units)

    b. IF C_AG_BLE_022 = FALSE (PHD does not report BMI) THEN

    • • Test Tool checks that BMI and Height Flag = 0
    • • Test Tool checks that BMI field is not reported
    | +| Pass/Fail criteria |

    In Step 5.a, BMI is reported, value of BMI field is within the range specified in Test Procedure and the value is correct.

    In Step 5.b, BMI is not reported.

    | +| Notes | | + +| | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-004 | | +| TP label | Whitepaper. Weight Measurement, User ID value | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | +| | Testable items | UserID15 2; O | +| Test purpose |

    Check that:

    User ID field in Weight Measurement characteristic shall be present if PHD under test supports multiple users

    | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_018 | | +| Other PICS | C_AG_BLE_023 | | +| Initial condition | The PHD under test and the simulated PHG are in the Standby state. | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The Simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Weight measurement to the simulated PHG.
    5. 5. Test Tool checks measurement sent by PHD under test
      1. a. IF C_AG_BLE_023 = TRUE (PHD supports multiple users) THEN
        • • Test Tool checks that User ID Flag = 1
        • • Test Tool checks that User ID field is reported
        • • Test Operator checks that User ID reported in User ID field is correct
      2. b. IF C_AG_BLE_023 = FALSE (PHD does not support multiple users) THEN
        • • Test Tool checks that User ID Flag = 0
        • • Test Tool checks that User ID field is not reported
    | | +| Pass/Fail criteria |

    In Step 5.a, User ID is reported and the value is correct.

    In Step 5.b, User ID is not reported.

    | | +| Notes | | | + +| | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-005 | | | | +| TP label | Whitepaper. Body Composition Measurement, Body Fat Percentage value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | Float Type 1; C | Body Fat Numeric 4; M | Body Fat Numeric 7; M | +| Test purpose | Check that:
    Body Fat Value field in Body Composition Measurement characteristic represents the measurement value acquired by BLE PHD | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_019 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Body Composition measurement to the simulated PHG.
    5. 5. Test Tool checks measurement sent by PHD under test
      • • Check that Body Fat reported in Body Composition Measurement Value (%) field is coherent: 5 < \text{value} < 30
      • • Test Operator checks that Body Fat reported in Body Composition Measurement Value (%) field is correct (value and units)
    | | | | +| Pass/Fail criteria | In Step 5, value of Body Composition Measurement Body Fat Value (%) field is within the range specified in Test Procedure and the value is correct. | | | | +| Notes | | | | | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-006 | | | | +| TP label | Whitepaper. Body Composition Measurement, Time Stamp value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | Date-Time Conv 1; M | Body Fat Numeric 6; M | Fat Free Numeric 6; M | +| | | Soft Lean Numeric 6; M | Body Water Numeric 6; M | | +| Test purpose | Check that:
    Time Stamp field in Body Composition Measurement characteristic represents the instant of time when BLE PHD acquired the measurement | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_019 | | | | +| Other PICS | C_AG_BLE_025 | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    2. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    3. 4. The PHD under test sends a Body Composition Measurement to the simulated PHG.
    4. 5. Test Tool checks measurement sent by PHD under test
      1. a. IF C_AG_BLE_025 = TRUE (time stamp is reported) THEN
        • • Test Tool checks that Time Stamp Flag = 1
        • • Test Tool checks that Time Stamp reported in Time Stamp field is coherent:
          • - Year: 1900 ≤ value ≤ 2100 OR value = 0
          • - Month: 1 ≤ value ≤ 12 OR value = 0
          • - Day: 1 ≤ value ≤ 31 OR value = 0
          • - Hours: 0 ≤ value ≤ 23
          • - Minutes: 0 ≤ value ≤ 59
          • - Seconds: 0 ≤ value ≤ 59
        • • Test Operator checks that Time Stamp reported in Time Stamp field is correct (value and units)
      2. b. IF C_AG_BLE_025 = FALSE (time stamp is not reported) THEN
        • • Test Tool checks that Time Stamp Flag = 0
    | +| Pass/Fail criteria |

    In Step 5.a, Time Stamp is reported, value of Time Stamp field is within the range specified in Test Procedure and the value is correct.

    In Step 5.b, Time Stamp is not reported.

    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-007 | | | +| TP label | Whitepaper. Body Composition Measurement, Fat Free Mass value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Float Type 1; C | Fat Free Numeric 4; M | +| Test purpose |

    Check that:

    Fat Free Mass field in Body Composition Measurement characteristic may be present if PHD under test supports Body Composition measurements, if it is present then its value represents the measurement value acquired by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_019 | | | +| Other PICS | C_AG_BLE_026 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Body Composition measurement to the simulated PHG.
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    5. Test Tool checks measurement sent by PHD under test

    a. IF C_AG_BLE_026 = TRUE (PHD reports Fat Free Mass) THEN

    • • Test Tool checks that Fat Free Mass present Flag = 1
      • a. If Measurement Units Flag = 0 (kg) THEN
        • - Check that Fat Free Mass reported in Body Composition Measurement (kg) field is coherent: 0 [0 kg] < value < 15000 [75 kg]
        • - Test operator checks that Fat Free Mass reported in Body Composition Measurement (kg) field is correct (value and units)
      • b. If Measurement Units Flag = 1 (lb) THEN
        • - Check that Fat Free Mass reported in Body Composition Measurement (lb) field is coherent: 0 [0 lb] < value < 33069 [165,35 lb]
        • - Test operator checks that Fat Free Mass reported in Body Composition Measurement (kg) field is correct (value and units)

    b. IF C_AG_BLE_026 = FALSE (PHD does not report Fat Free Mass) THEN

    • • Test Tool checks that Fat Free Mass Flag = 0
    • • Test Tool checks that Fat Free Mass field is not reported
    | +| Pass/Fail criteria |

    In Step 5.a, Fat Free Mass is reported, value of Fat Free Mass field is within the range specified in Test Procedure and the value is correct.

    In Step 5.b, Fat Free Mass is not reported.

    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-008 | | | +| TP label | Whitepaper. Body Composition Measurement, Soft Lean Mass value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Float Type 1; C | Soft Lean Numeric 4; M | +| Test purpose |

    Check that:

    Soft Lean Mass field in Body Composition Measurement characteristic may be present if PHD under test supports Soft Lean Mass measurements, if it is present then its value represents the measurement value acquired by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_019 | | | +| Other PICS | C_AG_BLE_027 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |

    1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).

    2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).

    3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).

    4. The PHD under test sends a Body Composition measurement to the simulated PHG.

    5. Test Tool checks measurement sent by PHD under test

    a. IF C_AG_BLE_027 = TRUE (PHD reports Soft Lean Mass) THEN

    • • Test Tool checks that Soft Lean Mass present Flag = 1
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. If Measurement Units Flag = 0 (kg) THEN

    • - Check that Soft Lean Mass reported in Body Composition Measurement (kg) field is coherent: 0 [0 kg] < value < 15000 [75 kg]
    • - Test operator checks that Soft Lean Mass reported in Body Composition Measurement (kg) field is correct (value and units)

    b. If Measurement Units Flag = 1 (lb) THEN

    • - Check that Soft Lean Mass reported in Body Composition Measurement (lb) field is coherent: 0 [0 lb] < value < 33069 [165,35 lb]
    • - Test operator checks that Soft Lean Mass reported in Body Composition Measurement (kg) field is correct (value and units)

    b. IF C_AG_BLE_027 = FALSE (PHD does not report Soft Lean Mass) THEN

    • • Test Tool checks that Soft Lean Mass Flag = 0
    • • Test Tool checks that Soft Lean Mass field is not reported
    | +| Pass/Fail criteria |

    In Step 5.a, Soft Lean Mass is reported, value of Soft Lean Mass field is within the range specified in Test Procedure and the value is correct.

    In Step 5.b, Soft Lean Mass is not reported.

    | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-009 | | | +| TP label | Whitepaper. Body Composition Measurement, Body Water Mass value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Float Type 1; C | Body Water Numeric 4; M      Body Water Numeric 7; M | +| Test purpose |

    Check that:

    Body Water Mass field in Body Composition Measurement characteristic may be present if PHD under test supports Body Water Mass measurements, if it is present then its value represents the measurement value acquired by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_019 | | | +| Other PICS | C_AG_BLE_028 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Body Composition measurement to the simulated PHG.
    5. 5. Test Tool checks measurement sent by PHD under test

      a. IF C_AG_BLE_028 = TRUE (PHD reports Body Water Mass) THEN

      • • Test Tool checks that Body Water Mass present Flag = 1
      • a. If Measurement Units Flag = 0 (kg) THEN
        • - Check that Body Water Mass reported in Body Composition Measurement (kg) field is coherent: 0 [0 kg] < value < 15000 [75 kg]
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • - Test operator checks that Body Water Mass reported in Body Composition Measurement (kg) field is correct (value and units)

    b. If Measurement Units Flag = 1 (lb) THEN

    • - Check that Body Water Mass reported in Body Composition Measurement (lb) field is coherent: 0 [0 lb] < value < 33069 [165,35 lb]
    • - Test operator checks that Boyd Water Mass reported in Body Composition Measurement (kg) field is correct (value and units)

    b. IF C_AG_BLE_028 = FALSE (PHD does not report Body Water Mass) THEN

    • • Test Tool checks that Body Water Mass Flag = 0
    • • Test Tool checks that Body Water Mass field is not reported
    | +| Pass/Fail criteria |

    In Step 5.a, Body Water Mass is reported, value of Body Water Mass field is within the range specified in Test Procedure and the value is correct.

    In Step 5.b, Body Water Mass is not reported.

    | +| Notes | | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-010 | | | +| TP label | Whitepaper. Body Composition Measurement, User ID value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | UserID20 2; O | | +| Test purpose |

    Check that:

    User ID field in Body Composition Measurement characteristic shall be present if PHD under test supports multiple users

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_019 | | | +| Other PICS | C_AG_BLE_029 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Body Composition measurement to the simulated PHG.
    5. 5. Test Tool checks measurement sent by PHD under test
      • a. IF C_AG_BLE_029 = TRUE (PHD supports multiple users) THEN
        • • Test Tool checks that User ID Flag = 1
        • • Test Tool checks that User ID field is reported
        • • Test Operator checks that User ID reported in User ID field is correct
      • b. IF C_AG_BLE_029 = FALSE (PHD does not support multiple users) THEN
        • • Test Tool checks that User ID Flag = 0
        • • Test Tool checks that User ID field is not reported
    | | | +| Pass/Fail criteria | In Step 5.a, User ID is reported and the value is correct. | | | + +| | | +|--------------|---------------------------------------| +| | In Step 5.b, User ID is not reported. | +| Notes | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-011 | | | | +| TP label | Whitepaper. Body Composition Measurement, Multiple Packet Measurement | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | Multi Packet Numeric 1; M | | | +| Test purpose | Check that:
    A Multiple Packet Measurement has a correct structure. | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_019 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Body Composition multiple-packet measurement (if it is possible, a Multiple Packet transmission) to the simulated PHG.
    5. 5. Test Tool checks measurement sent by the PHD under test, and checks the value of Multiple Packet Measurement flag.
    6. 6. IF Multiple Packet Measurement Flag = 1
      1. a. Test Tool receives a new Body Composition measurement
      2. b. Test Tool checks Multiple Packet Measurement flag on both measurements
      3. c. Test Tool checks the value of Body Fat Percentage field on both measurements
      4. d. Test Tool checks the value of Time Stamp field on both measurements
      5. e. Test Tool checks the value of User ID field on both measurements
      6. f. Test Tool checks the value of Basal Metabolism on both measurements
      7. g. Test Tool checks the value of Muscle Percentage on both measurements
      8. h. Test Tool checks the value of Muscle Mass on both measurements
      9. i. Test Tool checks the value of Fat Free Mass on both measurements
      10. j. Test Tool checks the value of Soft Lean Mass on both measurements
      11. k. Test Tool checks the value of Body Water Mass on both measurements
      12. l. Test Tool checks the value of Impedance on both measurements
      13. m. Test Tool checks the value of Weight on both measurements
      14. n. Test Tool checks the value of Height on both measurements
    7. 7. IF Multiple Packet Measurement Flag = 0, PHD under test does not receive a new Body Composition measurement with Multiple Packet Measurement Flag = 1
    | | | | +| Pass/Fail criteria | In Step 6.a, a new Body Composition Measurement is received.
    In Step 6.b, Multiple Packet Measurement flag on both measurements are set to 1 | | | | + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    In Step 6.c, Body Fat Percentage field on both measurements are set to the same value

    In Step 6.d, if Time Stamp field is present, it is present only in the first measurement

    In Step 6.e, if User ID field is present, it is present only in the first measurement

    In Step 6.f, if Basal Metabolism is present, it is present only in one measurement

    In Step 6.g, if Muscle Percentage is present, it is present only in one measurement

    In Step 6.h, if Muscle Mass is present, it is present only in one measurement

    In Step 6.i, if Fat Free is present, it is present only in one measurement

    In Step 6.j, if Soft Lean Mass is present, it is present only in one measurement

    In Step 6.k, if Body Water Mass is present, it is present only in one measurement

    In Step 6.l, if Impedance is present, it is present only in one measurement

    In Step 6.m, if Weight is present, it is present only in one measurement

    In Step 6.n, if Height is present, it is present only in one measurement

    In Step 7, a new Body Composition Measurement is not received, or a new Body Composition Measurement is received with Multiple Packet Measurement Flag set to 0.

    | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-012 | | | +| TP label | Whitepaper. Body Composition Measurement, Height and Weight not reported | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | BC Feature 4; M | | +| Test purpose |

    Check that:

    Height and Weight fields in Body Composition Measurement characteristic shall not be present.

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_019 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Body Composition measurement to the simulated PHG.
    5. 5. The simulated PHG reads the Body Composition Feature.
    6. 6. Test Tool checks measurement sent by PHD under test
      1. a. Test Tool checks that Weight flag = 0.
      2. b. Test Tool checks that Weight field is not reported.
      3. c. Test Tool checks that Height flag = 0.
      4. d. Test Tool checks that Height field is not reported.
    7. 7. Test Tool checks Body Composition Feature sent by PHD under test
      1. a. Test Tool checks that Height Resolution flags = 000.
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | In Step 6.a and 6.b, Weight field is not reported.
    In Step 6.c and 6.d, Height field is not reported.
    In Step 7, Height Resolution flags are zero. | +| Notes | | + +| | | | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-013 | | | | +| TP label | Whitepaper. Weight Scale Feature | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | WS Feature 4; M | | | +| Test purpose | Check that:
    Weight Scale Feature and Weight Scale Measurement are coherent. | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_018 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Weight Scale measurement to the simulated PHG.
    5. 5. The simulated PHG reads the Weight Scale Feature.
    6. 6. Test Tool checks measurement sent by PHD under test
      1. a. Test Tool checks if Time Stamp is reported.
      2. b. Test Tool checks if User ID is reported.
      3. c. Test Tool checks if BMI is reported.
    7. 7. Test Tool checks Weight Scale Feature sent by PHD under test
      1. a. Test Tool checks Time Stamp Supported bit.
      2. b. Test Tool checks Multiple Users Supported bit
      3. c. Test Tool checks BMI Supported bit
    | | | | +| Pass/Fail criteria | In Step 6.a and 7.a, if Time Stamp Supported bit =0, Time Stamp field is not reported.
    In Step 6.b and 7.b, if Multiple Users Supported bit =0, User ID field is not reported.
    In Step 6.c and 7.c, if BMI Supported bit =0, BMI field is not reported. | | | | +| Notes | | | | | + +| | | | | | +|-----------------|--------------------------------------|-----------------------|--|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/WS/BV-014 | | | | +| TP label | Whitepaper. Body Composition Feature | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | + +| | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|--| +| | Testable items | BC Feature 5; M | | | +| Test purpose | Check that:
    Body Composition Feature and Body Composition Measurement are coherent. | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_018 AND C_AG_BLE_019 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a Weight Scale measurement to the simulated PHG.
    5. 5. The simulated PHG reads the Body Composition Feature.
    6. 6. Test Tool checks measurement sent by PHD under test
      1. a. Test Tool checks if Time Stamp is reported.
      2. b. Test Tool checks if User ID is reported.
      3. c. Test Tool checks if Basal Metabolism is reported
      4. d. Test Tool checks if Muscle Percentage is reported
      5. e. Test Tool checks if Muscle Mass is reported
      6. f. Test Tool checks if Fat Free Mass is reported
      7. g. Test Tool checks if Soft Lean Mass is reported
      8. h. Test Tool checks if Body Water Mass is reported
      9. i. Test Tool checks if Impedance is reported
      10. j. Test Tool checks if Weight is reported
      11. k. Test Tool checks if Height is reported.
    7. 7. Test Tool checks Body Composition Feature sent by the PHD under test
      1. a. Test Tool checks Time Stamp Supported bit.
      2. b. Test Tool checks Multiple Users Supported bit
      3. c. Test Tool checks Basal Metabolism Supported bit
      4. d. Test Tool checks Muscle Percentage Supported bit
      5. e. Test Tool checks Muscle Mass Supported bit
      6. f. Test Tool checks Fat Free Mass Supported bit
      7. g. Test Tool checks Soft Lean Mass Supported bit
      8. h. Test Tool checks Body Water Mass Supported bit
      9. i. Test Tool checks Impedance Supported bit
      10. j. Test Tool checks Weight Supported bit
      11. k. Test Tool checks Height Supported bit
    | | | | +| Pass/Fail criteria |

    In Step 6.a and 7.a, if Time Stamp Supported bit =0, Time Stamp field is not reported

    In Step 6.b and 7.b, if Multiple Users Supported bit =0, User ID field is not reported

    In Step 6.c and 7.c, if Basal Metabolism Supported bit =0, Basal Metabolism field is not reported

    | | | | + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | In Step 6.d and 7.d, if Muscle Percentage Supported bit =0, Muscle Percentage field is not reported
    In Step 6.e and 7.e, if Muscle Mass Supported bit =0, Muscle Mass field is not reported
    In Step 6.f and 7.f, if Fat Free Mass Supported bit =0, Fat Free Mass field is not reported
    In Step 6.g and 7.g, if Soft Lean Mass Supported bit =0, Soft Lean Mass field is not reported
    In Step 6.h and 7.h, if Body Water Mass Supported bit =0, Body Water Mass field is not reported
    In Step 6.i and 7.i, if Impedance Supported bit =0, Impedance field is not reported
    In Step 6.j and 7.j, if Weight Supported bit =0, Weight field is not reported
    In Step 6.k and 7.k, if Height Supported bit =0, Height field is not reported. | +| Notes | | + +### A.8 Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------|--------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-000 | | | | +| TP label | Whitepaper. PLX Spot-Check Measurement, SpO2 and Pulse Rate values | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 1; C | SpO2 Numeric 8; M | SpO2 Numeric 10; M | +| | | PR Numeric 8; M | PR Numeric 10; M | | +| Test purpose | Check that:

    SpO2 subfield of SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic represents the measurement value acquired by BLE PHD
    [AND]
    PR subfield of SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic represents the measurement value acquired by BLE PHD | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Spot-Check measurement to the simulated PHG.
    5. 5. Check measurement sent by the PHD under test
      • • Check that SpO2 value reported in SpO2PR-Spot-Check field is coherent: 70(\%) \leq \text{value} \leq 100(\%).
      • • Check that PR value reported in SpO2PR-Spot-Check field is coherent: 20(\text{bpm}) \leq \text{value} \leq 250(\text{bpm}).
      • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Spot-Check field are correct.
    | | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | In Step 5, value of SpO2 and PR subfields of SpO2PR-Spot-Check field are within the ranges specified in Test Procedure and the values are correct. | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the PLX Spot-Check Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the PLX Spot-Check Measurement characteristic has been enabled for indications, the PHD is expected to send a PLX Spot-Check measurement to the PHG to check the required fields.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Check that:
      • 1. First subfield contains a value between 70 (0x0046) and 100 (0x0064). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 2. Second subfield contains a value between 20 (0x0014) and 250 (0x00FA). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 3. Check that received values match those actually transmitted.
    • • Timestamp field (if present, 7 octets).
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------|------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-001 | | | | +| TP label | Whitepaper. PLX Spot-Check Measurement, SpO2 and Pulse Rate values unavailable | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 2; M | SpO2 Numeric 10; M | PR Numeric 10; M | +| | | SpO2 Numeric 20; M | PR Numeric 20; M | | +| Test purpose |

    Check that:

    When SpO2 value of SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic cannot be determined the special value NaN is used (0x07FF)

    [AND]

    When PR value of SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic cannot be determined the special value NaN is used (0x07FF)

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. Simulated PHG initiates discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with PHD under test (Initiating state)
    3. 3. Simulated PHG initiates a Bluetooth connection with PHD under test (Connection state)
    4. 4. PHD under test sends a PLX Spot-Check measurement with unavailable SpO2 and PR values (e.g. simulating a measurement or device error) to Simulated PHG
    | | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    5. Check measurement sent by PHD under test

    • • Check that SpO2 value reported in SpO2PR-Spot-Check field is the special value NaN (0x07FF)
    • • Check that PR value reported in SpO2PR-Spot-Check field is the special value NaN (0x07FF)
    • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Spot-Check field are equal to the special value NaN (unavailable measurements).
    | +| Pass/Fail criteria | In Step 5, value of SpO2 and PR subfields of SpO2PR-Spot-Check field are equal to the special value NaN (0x07FF). | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the PLX Spot-Check Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the PLX Spot-Check Measurement characteristic has been enabled for indications, the PHD is expected to send a PLX Spot-Check measurement to the PHG to check the required fields.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Check that:
      1. 1. First subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      2. 2. Second subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      3. 3. Check that received values match those actually transmitted.
    • • Timestamp field (if present, 7 octets).
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-002 | | | +| TP label | Whitepaper. PLX Spot-Check Measurement, Time Stamp value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Date-Time Conv 1; M | SpO2 Numeric 9; M | +| Test purpose |

    Check that:

    Time Stamp field in PLX Spot-Check Measurement characteristic represents the instant of time when BLE PHD acquired the measurement

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 | | | +| Other PICS | C_AG_BLE_035 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    2. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    3. 4. The PHD under test sends a PLX Spot-Check Measurement to the simulated PHG.
    4. 5. Check measurement sent by the PHD under test
      1. a. IF C_AG_BLE_035 = TRUE (time stamp is reported) THEN
        • • Check that "Timestamp field is present" Flag = 1
        • • Check that the Time Stamp reported in the Timestamp field is coherent:
          • - Year: 1900 ≤ value ≤ 2100 OR value = 0
          • - Month: 1 ≤ value ≤ 12 OR value = 0
          • - Day: 1 ≤ value ≤ 31 OR value = 0
          • - Hours: 0 ≤ value ≤ 23
          • - Minutes: 0 ≤ value ≤ 59
          • - Seconds: 0 ≤ value ≤ 59
        • • Test Operator checks that the Time Stamp reported in Timestamp field is correct.
      2. b. IF C_AG_BLE_035 = FALSE (time stamp is not reported) THEN
        • • Check that "Timestamp field is present" Flag = 0.
    | +| Pass/Fail criteria |

    In Step 5.a, Time Stamp is reported, value of Timestamp field is within the range specified in Test Procedure and the value is correct.

    In Step 5.b, Time Stamp is not reported.

    | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the PLX Spot-Check Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the PLX Spot-Check Measurement characteristic has been enabled for indications, the PHD is expected to send a PLX Spot-Check measurement to the PHG to check the required fields.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 0 (Timestamp field is present) is set to 1 IF C_AG_BLE_035 = TRUE
      2. 2. Bit 0 (Timestamp field is present) is set to 0 IF C_AG_BLE_035 = FALSE
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (7 octets) will be present IF C_AG_BLE_035 = TRUE. In that case, check in that field that:
      1. 1. First 2 octets (Year) are between 1900 (0x076C) and 2100 (0x0834) OR they are equal to 0x0000. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Month (1 octet) will be between 1 (0x01) and 12 (0x0C) OR equal to 0 (0x00).
      3. 3. Day (1 octet) will be between 1 (0x01) and 31 (0x1F) OR equal to 0 (0x00).
      4. 4. Hour (1 octet) will be between 0 (0x00) and 23 (0x17).
      5. 5. Minute (1 octet) will be between 0 (0x00) and 59 (0x3B).
      6. 6. Second (1 octet) will be between 0 (0x00) and 59 (0x3B).
      7. 7. Check that received values match those actually transmitted.
    | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-003 | | | | +| TP label | Whitepaper. PLX Spot-Check Measurement, Measurement Status value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | SpO2 Numeric 7; M | PR Numeric 7; M | | +| Test purpose |

    Check that:

    If Measurement Status field is sent in PLX Spot-Check Measurement, it is set to a valid value.

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 | | | | +| Other PICS | C_AG_BLE_036 | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Spot-Check Measurement to the simulated PHG.
    5. 5. Check measurement sent by PHD under test
      1. a. IF C_AG_BLE_036 = TRUE (PHD reports Measurement Status) THEN
        • • Check that "Measurement Status field is present" Flag = 1
        • • Check that Measurement Status field reported in PLX Spot-Check Measurement is present, and is set to allowed values: bits 5 to 15 may be set to 0 or 1, Bits 0 to 4 are reserved for future use and must be set to 0
        • • Test Operator checks that the Measurement Status value reported in the PLX Spot-Check Measurement is correct
      2. b. IF C_AG_BLE_036 = FALSE (PHD does not report Measurement Status) THEN
        • • Check that "Measurement Status field is present" Flag = 0
        • • Check that Measurement Status field is not reported
    | | | | +| Pass/Fail criteria |

    In Step 5.a, value of Measurement Status field is correct.

    In Step 5.b, Measurement Status field is not present

    | | | | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the PLX Spot-Check Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the PLX Spot-Check Measurement characteristic has been enabled for indications, the PHD is expected to send a PLX Spot-Check measurement to the PHG to check the required fields.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    | | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 1 (Measurement Status field is present) is set to 1 IF C_AG_BLE_036 = TRUE
      2. 2. Bit 1 (Measurement Status field is present) is set to 0 IF C_AG_BLE_036 = FALSE
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (if present, 7 octets)
    • • Measurement Status field (2 octets) will be present IF C_AG_BLE_036 = TRUE. In that case, check in that field that:
      1. 1. Bits 0 to 4 are reserved for future use and are equal to 0. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Bits 5 to 15 may be 0 or 1. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      3. 3. Check that received values match those actually transmitted.
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-004 | | | +| TP label | Whitepaper. PLX Spot-Check Measurement, Device and Sensor Status value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DSS Enumeration 4; M | | +| Test purpose | Check that:
    If Device and Sensor Status field is sent in PLX Spot-Check Measurement, it is set to a valid value. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 | | | +| Other PICS | C_AG_BLE_037 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Spot-Check Measurement to the simulated PHG.
    5. 5. Check measurement sent by PHD under test
      1. a. IF C_AG_BLE_037 = TRUE (PHD reports Device and Sensor Status) THEN
        • • Check that "Device and Sensor Status field is present" Flag = 1
        • • Check that Device Sensor Status field reported in PLX Spot-Check Measurement is present, and is set to allowed values: bits 0 to 15 may be set to 0 or 1, Bits 16 to 23 are reserved for future use and must be set to 0
        • • Test Operator checks that the Device and Sensor Status value reported in the PLX Spot-Check Measurement is correct
      2. b. IF C_AG_BLE_037 = FALSE (PHD does not report Device and Sensor Status) THEN
    | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Check that "Device and Sensor Status field is present" Flag = 0
    • • Check that Device and Sensor Status field is not reported
    | +| Pass/Fail criteria |

    In Step 5.a, value of Device and Sensor Status field is correct.

    In Step 5.b, Device and Sensor Status field is not present.

    | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the PLX Spot-Check Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the PLX Spot-Check Measurement characteristic has been enabled for indications, the PHD is expected to send a PLX Spot-Check measurement to the PHG to check the required fields.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      • 1. Bit 2 (Device and Sensor Status field is present) is set to 1 IF C_AG_BLE_037 = TRUE
      • 2. Bit 2 (Device and Sensor Status field is present) is set to 0 IF C_AG_BLE_037 = FALSE
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (if present, 7 octets)
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (3 octets) will be present IF C_AG_BLE_037 = TRUE. In that case, check in that field that:
      • 1. Bits 16 to 23 are reserved for future use and are equal to 0. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 2. Bits 0 to 15 may be 0 or 1. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 3. Check that received values match those actually transmitted.
    • • Pulse Amplitude Index field (if present, 2 octets)
    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-005 | | | +| TP label | Whitepaper. PLX Spot-Check Measurement, Pulse Amplitude Index value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 1; C | PQ Numeric 8; M | +| Test purpose |

    Check that:

    Pulse Amplitude Index field in PLX Spot-Check Measurement characteristic represents the measurement value acquired by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 | | | +| Other PICS | C_AG_BLE_038 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    2. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    3. 4. The PHD under test sends a PLX Spot-Check measurement.
    4. 5. Check measurement sent by PHD under test
      1. a. IF C_AG_BLE_038 = TRUE (PHD reports Pulse Amplitude Index) THEN
        • • Check that "Pulse Amplitude Index field is present" Flag = 1
        • • Check that Pulse Amplitude Index value reported in Pulse Amplitude Index field is coherent: 1(\%) \leq \text{value} \leq 100(\%)
        • • Test Operator checks that the Pulse Amplitude Index value reported in the PLX Spot-Check Measurement is correct
      2. b. IF C_AG_BLE_038 = FALSE (PHD does not report Pulse Amplitude Index) THEN
        • • Check that "Pulse Amplitude Index field is present" Flag = 0
    | +| Pass/Fail criteria |

    In Step 5.a, value of Pulse Amplitude Index field is correct.

    In Step 5.b, Pulse Amplitude Index field is not present.

    | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the PLX Spot-Check Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the PLX Spot-Check Measurement characteristic has been enabled for indications, the PHD is expected to send a PLX Spot-Check measurement to the PHG to check the required fields.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 3 (Pulse Amplitude Index field is present) is set to 1 IF C_AG_BLE_038 = TRUE
      2. 2. Bit 3 (Pulse Amplitude Index field is present) is set to 0 IF C_AG_BLE_038 = FALSE
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (if present, 7 octets)
    • • Measurement Status field ( if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (2 octets) will be present IF C_AG_BLE_038 = TRUE. In that case, check in that field that:
      1. 1. It contains a value between 1 (0x0001) and 100 (0x0064). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Check that received values match those actually transmitted.
    | + +| | | | | +|---------------------|---------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-006 | | | +| TP label | Whitepaper. PLX Spot-Check Measurement, Pulse Amplitude Index value unavailable | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 2; M | PQ Numeric 8; M | +| Test purpose | Check that: | | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Pulse Amplitude Index field in PLX Spot-Check Measurement characteristic represents an unavailable value (e.g. due to a measurement or device error) using the special value NaN. | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 AND C_AG_BLE_038 | +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Spot-Check measurement with an unavailable value in the Pulse Amplitude Index field (e.g. simulating a measurement or device error).
    5. 5. Check measurement sent by PHD under test
      • • Check that "Pulse Amplitude Index field is present" Flag = 1
      • • Check that Pulse Amplitude Index value reported in Pulse Amplitude Index field is equal to special value NaN (0x07FF)
      • • Test Operator checks that the Pulse Amplitude Index value reported in the PLX Spot-Check Measurement is equal to special value NaN (0x07FF)
    | +| Pass/Fail criteria | In Step 5, value of Pulse Amplitude Index field is special value NaN (0x07FF). | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the PLX Spot-Check Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the PLX Spot-Check Measurement characteristic has been enabled for indications, the PHD is expected to send a PLX Spot-Check measurement to the PHG to check the required fields.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 3 (Pulse Amplitude Index field is present) is set to 1
      2. 2. Bit 3 (Pulse Amplitude Index field is present) is set to 0
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (if present, 7 octets)
    • • Measurement Status field ( if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (2 octets) will be present, check in that field that:
      1. 1. It contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      2. 2. Check that received values match those actually transmitted.
    | + +| | | | +|-----------------|---------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-007 | | +| TP label | Whitepaper. PLX Continuous Measurement, SpO2 and Pulse Rate Normal values | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | + +| | | | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------| +| Testable items | Short Float Type 1; C | SpO2 Numeric 18; M | SpO2 Numeric 19; M | +| | PR Numeric 18; M | PR Numeric 19; M | | +| Test purpose | Check that:
    SpO2 subfield of SpO2PR-Normal field in PLX Continuous Measurement characteristic represents the measurement value acquired by BLE PHD
    [AND]
    PR subfield of SpO2PR-Normal field in PLX Continuous Measurement characteristic represents the measurement value acquired by BLE PHD | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous measurement to the simulated PHG.
    5. 5. Check measurement sent by PHD under test
      • • Check that SpO2 value reported in SpO2PR-Normal field is coherent: 70(\%) \leq \text{value} \leq 100(\%).
      • • Check that PR value reported in SpO2PR-Normal field is coherent: 20(\text{bpm}) \leq \text{value} \leq 250(\text{bpm}).
      • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Normal field are correct.
    | | | +| Pass/Fail criteria | In Step 5, value of SpO2 and PR subfields of SpO2PR-Normal field are within the ranges specified in Test Procedure and the values are correct. | | | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Check that:
      1. 1. First subfield contains a value between 70 (0x0046) and 100 (0x0064). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Second subfield contains a value between 20 (0x0014) and 250 (0x00FA). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      3. 3. Check that received values match those actually transmitted.
    • • The SpO2PR-Fast field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • The SpO2PR-Slow field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-008 | | | +| TP label | Whitepaper. PLX Continuous Measurement, SpO2 and Pulse Rate Normal values unavailable | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 2; M | SpO2 Numeric 19; M | +| | | SpO2 Numeric 20; M | PR Numeric 20; M | +| Test purpose |

    Check that:

    When SpO2 value of SpO2PR-Normal field in PLX Continuous Measurement characteristic cannot be determined the special value NaN is used (0x07FF)

    [AND]

    When PR value of SpO2PR-Normal field in PLX Continuous Measurement characteristic cannot be determined the special value NaN is used (0x07FF)

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous measurement with unavailable SpO2 and PR values in SpO2PR-Normal field (e.g. simulating a measurement or device error) to the simulated PHG.
    5. 5. Check measurement sent by PHD under test
      • • Check that SpO2 value reported in SpO2PR-Normal field is the special value NaN (0x07FF)
      • • Check that PR value reported in SpO2PR-Normal field is the special value NaN (0x07FF)
      • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Normal field are equal to the special value NaN (unavailable measurements).
    | | | +| Pass/Fail criteria | In Step 5, value of SpO2 and PR subfields of SpO2PR-Normal field are equal to the special value NaN (0x07FF). | | | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Check that:
      1. 1. First subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      2. 2. Second subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      3. 3. Check that received values match those actually transmitted.
    • • The SpO2PR-Fast field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • The SpO2PR-Slow field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------|--------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-009 | | | | +| TP label | Whitepaper. PLX Continuous Measurement, SpO2 and Pulse Rate Fast values | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 1; C | SpO2 Numeric 14; M | SpO2 Numeric 18; M | +| | | SpO2 Numeric 19; M | PR Numeric 14; M | PR Numeric 18; M | +| | | PR Numeric 19; M | | | +| Test purpose |

    Check that:

    If present, SpO2 subfield of SpO2PR-Fast field in PLX Continuous Measurement characteristic represents the measurement value acquired by BLE PHD

    [AND]

    If present, PR subfield of SpO2PR-Fast field in PLX Continuous Measurement characteristic represents the measurement value acquired by BLE PHD

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 | | | | +| Other PICS | C_AG_BLE_039 | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous measurement to the Simulated PHG.
    5. 5. Check measurement sent by PHD under test
    | | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. IF C_AG_BLE_039 = TRUE (fast response mode is reported) THEN

    • • Check that "SpO2PR-Fast field is present" Flag = 1
    • • Check that SpO2 value reported in SpO2PR-Fast field is coherent: 70(%) ≤ value ≤ 100(%).
    • • Check that PR value reported in SpO2PR-Fast field is coherent: 20(bpm) ≤ value ≤ 250(bpm).
    • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Fast field are correct.

    b. IF C_AG_BLE_039 = FALSE (fast response mode is not reported) THEN

    • • Check that "SpO2PR-Fast field is present" Flag = 0
    | +| Pass/Fail criteria |

    In Step 5.a, value of SpO2 and PR subfields of SpO2PR-Fast field are within the ranges specified in Test Procedure and the values are correct.

    In Step 5.b, Fast Response mode is not reported

    | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      • 1. Bit 0 (SpO2PR-Fast field is present) is set to 1 IF C_AG_BLE_039 = TRUE
      • 2. Bit 0 (SpO2PR-Fast field is present) is set to 0 IF C_AG_BLE_039 = FALSE
    • • Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • The SpO2PR-Fast field (4 octets) will be present IF C_AG_BLE_039 = TRUE with two subfields, SpO2 (2 octets) and PR (2 octets). In that case, check that:
      • 1. First subfield contains a value between 70 (0x0046) and 100 (0x0064). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 2. Second subfield contains a value between 20 (0x0014) and 250 (0x00FA). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 3. Check that received values match those actually transmitted.
    • • The SpO2PR-Slow field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | + +| | | | | +|-----------------|-------------------------------------------------------------------------------------|-----------------------|--------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-010 | | | +| TP label | Whitepaper. PLX Continuous Measurement, SpO2 and Pulse Rate Fast values unavailable | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 2; M | SpO2 Numeric 14; M | +| | | SpO2 Numeric 20; M | PR Numeric 14; M | +| | | | PR Numeric 19; M | + +| | | | | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--|--| +| | | PR Numeric 20; M | | | +| Test purpose |

    Check that:

    When SpO2 value of SpO2PR-Fast field in PLX Continuous Measurement characteristic cannot be determined the special value NaN is used (0x07FF)

    [AND]

    When PR value of SpO2PR-Fast field in PLX Continuous Measurement characteristic cannot be determined the special value NaN is used (0x07FF)

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 AND C_AG_BLE_039 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous measurement with unavailable SpO2 and PR values in SpO2PR-Fast field (e.g. simulating a measurement or device error) to the simulated PHG.
    5. 5. Check measurement sent by PHD under test
      • • Check that SpO2 value reported in SpO2PR-Fast field is the special value NaN (0x07FF)
      • • Check that PR value reported in SpO2PR-Fast field is the special value NaN (0x07FF)
      • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Fast field are equal to the special value NaN (unavailable measurements).
    | | | | +| Pass/Fail criteria | In Step 5, value of SpO2 and PR subfields of SpO2PR-Fast field are equal to the special value NaN (0x07FF). | | | | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 0 (SpO2PR-Fast field is present) is set to 1
      2. 2. Bit 0 (SpO2PR-Fast field is present) is set to 0
    • • Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • The SpO2PR-Fast field (4 octets) will be present with two subfields, SpO2 (2 octets) and PR (2 octets). Check that:
      1. 1. First subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
    | | | | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. Second subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).

    3. Check that received values match those actually transmitted.

    • • The SpO2PR-Slow field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-011 | | | +| TP label | Whitepaper. PLX Continuous Measurement, SpO2 and Pulse Rate Slow values | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 1; C | SpO2 Numeric 15; M | +| | | SpO2 Numeric 19; M | PR Numeric 15; M | +| | | PR Numeric 19; M | | +| Test purpose |

    Check that:

    If present, SpO2 subfield of SpO2PR-Slow field in PLX Continuous Measurement characteristic represents the measurement value acquired by BLE PHD

    [AND]

    If present, PR subfield of SpO2PR-Slow field in PLX Continuous Measurement characteristic represents the measurement value acquired by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 | | | +| Other PICS | C_AG_BLE_040 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous measurement to the simulated PHG.
    5. 5. Check measurement sent by PHD under test
      1. a. IF C_AG_BLE_040 = TRUE (slow response mode is reported) THEN
        • • Check that "SpO2PR-Slow field is present" Flag = 1
        • • Check that SpO2 value reported in SpO2PR-Slow field is coherent: 70(%) ≤ value ≤ 100(%).
        • • Check that PR value reported in SpO2PR-Slow field is coherent: 20(bpm) ≤ value ≤ 250(bpm).
        • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Slow field are correct.
      2. b. IF C_AG_BLE_040 = FALSE (slow response mode is not reported) THEN
        • • Check that "SpO2PR-Slow field is present" Flag = 0
    | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |

    In Step 5.a, value of SpO2 and PR subfields of SpO2PR-Slow field are within the ranges specified in Test Procedure and the values are correct.

    In Step 5.b, Slow Response mode is not reported.

    | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      • 1. Bit 1 (SpO2PR-Slow field is present) is set to 1 IF C_AG_BLE_040 = TRUE
      • 2. Bit 1 (SpO2PR-Slow field is present) is set to 0 IF C_AG_BLE_040 = FALSE
    • • Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • The SpO2PR-Fast field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • The SpO2PR-Slow field (4 octets) will be present IF C_AG_BLE_039 = TRUE with two subfields, SpO2 (2 octets) and PR (2 octets). In that case, check that:
      • 1. First subfield contains a value between 70 (0x0046) and 100 (0x0064). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 2. Second subfield contains a value between 20 (0x0014) and 250 (0x00FA). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 3. Check that received values match those actually transmitted.
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | + +| | | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------|--------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-012 | | | | +| TP label | Whitepaper. PLX Continuous Measurement, SpO2 and Pulse Rate Slow values unavailable | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 2; M | SpO2 Numeric 15; M | SpO2 Numeric 19; M | +| | | SpO2 Numeric 20; M | PR Numeric 15; M | PR Numeric 19; M | +| | | PR Numeric 20; M | | | +| Test purpose |

    Check that:

    When SpO2 value of SpO2PR-Slow field in PLX Continuous Measurement characteristic cannot be determined the special value NaN is used (0x07FF)

    [AND]

    When PR value of SpO2PR-Slow field in PLX Continuous Measurement characteristic cannot be determined the special value NaN is used (0x07FF)

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 AND C_AG_BLE_040 | | | | +| Other PICS | | | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous measurement with unavailable SpO2 and PR values in SpO2PR-Slow field (e.g. simulating a measurement or device error) to the simulated PHG.
    5. 5. Check measurement sent by PHD under test
      • • Check that SpO2 value reported in SpO2PR-Slow field is the special value NaN (0x07FF)
      • • Check that PR value reported in SpO2PR-Slow field is the special value NaN (0x07FF)
      • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Slow field are equal to the special value NaN (unavailable measurements).
    | +| Pass/Fail criteria | In Step 5, value of SpO2 and PR subfields of SpO2PR-Slow field are equal to the special value NaN (0x07FF). | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 1 (SpO2PR-Slow field is present) is set to 1
      2. 2. Bit 1 (SpO2PR-Slow field is present) is set to 0
    • • Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • The SpO2PR-Fast field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • The SpO2PR-Slow field (4 octets) will be present with two subfields, SpO2 (2 octets) and PR (2 octets). Check that:
      1. 1. First subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      2. 2. Second subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      3. 3. Check that received values match those actually transmitted.
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | + +| | | | | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-013 | | | | +| TP label | Whitepaper. PLX Continuous Measurement, Measurement Status value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | SpO2 Numeric 17; M | PR Numeric 17; M | | +| Test purpose |

    Check that:

    If Measurement Status field is sent in PLX Continuous Measurement, it is set to a valid value.

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 | | | | +| Other PICS | C_AG_BLE_036 | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous Measurement to the simulated PHG.
    5. 5. Check measurement sent by PHD under test
      1. a. IF C_AG_BLE_036 = TRUE (PHD reports Measurement Status) THEN
        • • Check that "Measurement Status field is present" Flag = 1
        • • Check that Measurement Status field reported in PLX Continuous Measurement is present, and is set to allowed values: bits 5 to 15 may be set to 0 or 1, Bits 0 to 4 are reserved for future use and must be set to 0
        • • Test Operator checks that the Measurement Status value reported in the PLX Continuous Measurement is correct
      2. b. IF C_AG_BLE_036 = FALSE (PHD does not report Measurement Status) THEN
        • • Check that "Measurement Status field is present" Flag = 0
        • • Check that Measurement Status field is not reported
    | | | | +| Pass/Fail criteria |

    In Step 5.a, value of Measurement Status field is correct.

    In Step 5.b, Measurement Status field is not present

    | | | | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 2 (Measurement Status field is present) is set to 1 IF C_AG_BLE_036 = TRUE
      2. 2. Bit 2 (Measurement Status field is present) is set to 0 IF C_AG_BLE_036 = FALSE
    • • Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    | | | | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|
    • • The SpO2PR-Fast field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • The SpO2PR-Slow field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • Measurement Status field (2 octets) will be present IF C_AG_BLE_036 = TRUE. In that case, check in that field that:
      1. 1. Bits 0 to 4 are reserved for future use and are equal to 0. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Bits 5 to 15 may be 0 or 1. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      3. 3. Check that received values match those actually transmitted.
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-014 | | | +| TP label | Whitepaper. PLX Continuous Measurement, Device and Sensor Status value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DSS Enumeration 8; M | | +| Test purpose | Check that:
    If Device and Sensor Status field is sent in PLX Continuous Measurement, it is set to a valid value. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 | | | +| Other PICS | C_AG_BLE_037 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous Measurement to the simulated PHG.
    5. 5. Check measurement sent by PHD under test
      1. a. IF C_AG_BLE_037 = TRUE (PHD reports Device and Sensor Status) THEN
        • • Check that "Device and Sensor Status field is present" Flag = 1
        • • Check that Device Sensor Status field reported in PLX Continuous Measurement is present, and is set to allowed values: bits 0 to 15 may be set to 0 or 1, Bits 16 to 23 are reserved for future use and must be set to 0
        • • Test Operator checks that the Device and Sensor Status value reported in the PLX Continuous Measurement is correct
      2. b. IF C_AG_BLE_037 = FALSE (PHD does not report Device and Sensor Status) THEN
        • • Check that "Device and Sensor Status field is present" Flag = 0
        • • Check that Device and Sensor Status field is not reported
    | | | +| Pass/Fail criteria | In Step 5.a, value of Device and Sensor Status field is correct. | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | In Step 5.b, Device and Sensor Status field is not present | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      • 1. Bit 3 (Device and Sensor Status field is present) is set to 1 IF C_AG_BLE_037 = TRUE
      • 2. Bit 3 (Device and Sensor Status field is present) is set to 0 IF C_AG_BLE_037 = FALSE
    • • Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • The SpO2PR-Fast field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • The SpO2PR-Slow field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (3 octets) will be present IF C_AG_BLE_037 = TRUE. In that case, check in that field that:
      • 1. Bits 16 to 23 are reserved for future use and are equal to 0. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 2. Bits 0 to 15 may be 0 or 1. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 3. Check that received values match those actually transmitted.
    • • Pulse Amplitude Index field (if present, 2 octets)
    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-015 | | | +| TP label | Whitepaper. PLX Continuous Measurement, Pulse Amplitude Index value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 1; C | PQ Numeric 13; M | +| Test purpose | Check that:
    Pulse Amplitude Index field in PLX Continuous Measurement characteristic represents the measurement value acquired by BLE PHD | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 | | | +| Other PICS | C_AG_BLE_038 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure | 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state). | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    2. 4. The PHD under test sends a PLX Continuous measurement.
    3. 5. Check measurement sent by PHD under test
      1. a. IF C_AG_BLE_038 = TRUE (PHD reports Pulse Amplitude Index) THEN
        • • Check that "Pulse Amplitude Index field is present" Flag = 1
        • • Check that Pulse Amplitude Index value reported in Pulse Amplitude Index field is coherent: 1(\%) \leq \text{value} \leq 100(\%)
        • • Test Operator checks that the Pulse Amplitude Index value reported in the PLX Continuous Measurement is correct
      2. b. IF C_AG_BLE_038 = FALSE (PHD does not report Pulse Amplitude Index) THEN
        • • Check that "Pulse Amplitude Index field is present" Flag = 0
    | +| Pass/Fail criteria |

    In Step 5.a, value of Pulse Amplitude Index field is correct.

    In Step 5.b, Pulse Amplitude Index field is not present

    | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 4 (Pulse Amplitude Index field is present) is set to 1 IF C_AG_BLE_038 = TRUE
      2. 2. Bit 4 (Pulse Amplitude Index field is present) is set to 0 IF C_AG_BLE_038 = FALSE
    • • Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • The SpO2PR-Fast field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • The SpO2PR-Slow field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • Measurement Status field ( if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (2 octets) will be present IF C_AG_BLE_038 = TRUE. In that case, check in that field that:
      1. 1. It contains a value between 1 (0x0001) and 100 (0x0064). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Check that received values match those actually transmitted.
    | + +| | | | | +|-----------------|---------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-016 | | | +| TP label | Whitepaper. PLX Continuous Measurement, Pulse Amplitude Index value unavailable | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 2; M | PQ Numeric 13; M | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    Pulse Amplitude Index field in PLX Continuous Measurement characteristic represents an unavailable value (e.g. due to a measurement or device error) using the special value NaN.

    | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 AND C_AG_BLE_038 | +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous measurement with an unavailable value in the Pulse Amplitude Index field (e.g. simulating a measurement or device error).
    5. 5. Check measurement sent by PHD under test
      • • Check that "Pulse Amplitude Index field is present" Flag = 1
      • • Check that Pulse Amplitude Index value reported in Pulse Amplitude Index field is equal to special value NaN (0x07FF)
      • • Test Operator checks that the Pulse Amplitude Index value reported in the PLX Continuous Measurement is equal to special value NaN (0x07FF)
    | +| Pass/Fail criteria | In Step 5, the value of Pulsatile Amplitude Index field is special value NaN (0x07FF) | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 4 (Pulse Amplitude Index field is present) is set to 1
      2. 2. Bit 4 (Pulse Amplitude Index field is present) is set to 0
    • • Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • The SpO2PR-Fast field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • The SpO2PR-Slow field (if present, 4 octets), with two subfields, SpO2 (2 octets) and PR (2 octets).
    • • Measurement Status field ( if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (2 octets) will be present, check in that field that:
      1. 1. It contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      2. 2. Check that received values match those actually transmitted.
    | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-017 | | | +| TP label | Whitepaper. PLX Features, PLX Spot-Check Measurement | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLX Features 1; M | PLX Features 2; C | +| | | SpO2 Numeric 7; M | SpO2 Numeric 9; M | +| | | PQ Numeric 9; M | PR Numeric 7; M | +| Test purpose | Check that:
    PLX Features and PLX Spot-Check Measurement are coherent. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG reads the PLX Features characteristic.
    5. 5. The PHD under test sends a PLX Spot-Check Measurement to the simulated PHG.
    6. 6. Check value of Supported Features field of PLX Features characteristic
      1. a. Check Measurement Status support bit
      2. b. Check Device and Sensor Status support bit.
      3. c. Check Timestamp for Spot-Check measurements support bit.
      4. d. Check Pulse Amplitude Index support bit.
      5. e. Check that bits 8-15 are 0 (Reserved for future use)
    7. 7. IF Measurement Status support bit = 1, check value of Measurement Status Support field of PLX Features characteristic
      1. a. Check that bits 0-4 are 0 (Reserved for future use)
      2. b. Check bits 5-15. These bits may be 0 or 1.
    8. 8. IF Device and Sensor Status support bit = 1, check value of Device and Sensor Status Support field of PLX Features characteristic
      1. a. Check bits 0-15. These bits may be 0 or 1.
      2. b. Check that bits 16-23 are 0 (Reserved for future use)
    9. 9. Check measurement sent by PHD under test
      1. a. Check if Measurement Status is reported.
      2. b. If Measurement Status is reported, check its value.
      3. c. Check if Device and Sensor Status is reported.
      4. d. If Device and Sensor Status is reported, check its value.
      5. e. Check if Time Stamp is reported.
      6. f. Check if Pulse Amplitude Index is reported.
    | | | +| Pass/Fail criteria | In Step 7: | | | + +| | | +|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Measurement Status Support field is present and values match those on Test Procedure.

    In Step 8:

    • • Device and Sensor Status Support field is present and values match those on Test Procedure.

    In Step 9:

    • • If Measurement Status support bit =0, Measurement Status field is not reported. If it is 1, it is reported.
    • • If Measurement Status is supported and reported, check that only bits that are supported according to Measurement Status Support field (7.b) can be equal to 1.
    • • If Device and Sensor Status support bit =0, Device and Sensor Status field is not reported. If it is 1, it is reported.
    • • If Device and Status is supported and reported, check that only bits that are supported according to Device and Sensor Status Support field (8.b) can be equal to 1.
    • • If Time Stamp support bit =0, Time Stamp field is not reported. If it is 1, it is reported.
    • • If Pulse Amplitude Index support bit=0, Pulse Amplitude Index is not reported. If it is 1, it is reported.
    | +|

    Notes
    (to assist manual testing)

    |

    To read PLX Features characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2A60. PHG will then receive a Read Response. Check ATT packet value in the received response:

    • • Supported Features field will be present (2 octets), and it indicates features support and optional fields present. Note that bytes will be transmitted using little endian order (i.e. the least significant octet first).
      1. 1. Check Measurement Status support bit (bit 0)
      2. 2. Check Device and Sensor Status support bit (bit 1)
      3. 3. Check Timestamp for Spot-Check measurements support bit (bit 3)
      4. 4. Check Pulse Amplitude Index support bit (bit 6)
      5. 5. Check that bits 8-15 are 0 (reserved for future use).
    • • Measurement Status Support field (2 octets) will be present if Measurement Status Support bit = 2. In that case, check that (Note that bytes will be transmitted using little endian order, i.e. the least significant octet first):
      1. 1. Check bits 5-15 values.
      2. 2. Check that bits 0-4 are 0 (Reserved for future use)
    • • Device and Sensor Status Support field (3 octets) will be present if Device and Sensor Status Support bit = 1. In that case, check that (Note that bytes will be transmitted using little endian order, i.e. the least significant octet first):
      1. 1. Check bits 0-15 values.
      2. 2. Check that bits 16-23 are 0 (Reserved for future use)

    In order to enable indications on the PLX Spot-Check Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the PLX Spot-Check Measurement characteristic has been enabled for indications, the PHD is expected to send a PLX Spot-Check measurement to the PHG to check the required fields.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present.
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (if present, 7 octets). Check that:
    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 1. If Timestamp support bit = 0, Timestamp field is not present.
    2. 2. If Timestamp support bit = 1, Timestamp field is present.
    • • Measurement Status field (if present, 2 octets) Check that:
      1. 1. If Measurement Status support bit = 1, this field is present.
      2. 2. If Measurement Status support bit = 0, this field is not present.
      3. 3. Only bits that are supported according to Measurement Status Support field can be equal to 1 that (Note that bytes will be transmitted using little endian order, i.e. the least significant octet first).
    • • Device and Sensor Status field (if present, 3 octets). Check that:
      1. 1. If Device and Sensor Status support bit = 1, this field is present.
      2. 2. If Device and Sensor Status support bit = 0, this field is not present.
      3. 3. Only bits that are supported according to Device and Sensor Status Support field can be equal to 1 that (Note that bytes will be transmitted using little endian order, i.e. the least significant octet first).
    • • Pulse Amplitude Index field (if present, 2 octets). Check that:
      1. 1. If Pulse Amplitude Index support bit = 0, this field is not present.
      2. 2. If Pulse Amplitude Index support bit = 1, this field is present.
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-018 | | | +| TP label | Whitepaper. PLX Features, PLX Continuous Measurement | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLX Features 1; M | PLX Features 2; C | +| | | SpO2 Numeric 17; M | PR Numeric 17; M | +| Test purpose | Check that:
    PLX Features and PLX Continuous Measurement are coherent. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_034 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a PLX Continuous Measurement to the simulated PHG.
    5. 5. The simulated PHG reads the PLX Features characteristic.
    6. 6. Check the value of Supported Features field of PLX Features characteristic
      1. a. Check Measurement Status support bit
      2. b. Check Device and Sensor Status support bit.
      3. c. Check SpO2PR-Fast metric support bit.
      4. d. Check SpO2PR-Slow metric support bit.
      5. e. Check Pulse Amplitude Index support bit.
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 7. IF Measurement Status support bit = 1, check value of Measurement Status Support field of PLX Features characteristic
      1. a. Check that bits 0-4 are 0 (Reserved for future use)
      2. b. Check bits 5-15. These bits may be 0 or 1.
    2. 8. IF Device and Sensor Status support bit = 1, check value of Device and Sensor Status Support field of PLX Features characteristic
      1. a. Check bits 0-15. These bits may be 0 or 1.
      2. b. Check that bits 16-23 are 0 (Reserved for future use)
    3. 9. Check measurement sent by PHD under test
      1. a. Check if Measurement Status is reported.
      2. b. If Measurement Status is reported, check its value.
      3. c. Check if Device and Sensor Status is reported.
      4. d. If Device and Sensor Status is reported, check its value.
      5. e. Check if SpO2PR-Fast is reported.
      6. f. Check if SpO2PR-Slow is reported.
      7. g. Check if Pulse Amplitude Index is reported.
    | +| Pass/Fail criteria |

    In Step 7:

    • • Measurement Status Support field is present and values match those on Test Procedure.

    In Step 8:

    • • Device and Sensor Status Support field is present and values match those on Test Procedure.

    In Step 9:

    • • If Measurement Status support bit =0, Measurement Status field is not reported. If it is 1, it is reported.
    • • If Measurement Status is supported and reported, check that only bits that are supported according to Measurement Status Support field (7.b) can be equal to 1.
    • • If Device and Sensor Status support bit =0, Device and Sensor Status field is not reported. If it is 1, it is reported.
    • • If Device and Status is supported and reported, check that only bits that are supported according to Device and Sensor Status Support field (8.b) can be equal to 1.
    • • If SpO2PR-Fast support bit =0, SpO2PR-Fast field is not reported. If it is 1, it is reported.
    • • If SpO2PR-Slow support bit =0, SpO2PR-Slow field is not reported. If it is 1, it is reported.
    • • If Pulse Amplitude Index support bit=0, Pulse Amplitude Index is not reported. If it is 1, it is reported.
    | +| Notes
    (to assist manual testing)     |

    To read PLX Features characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2A60. PHG will then receive a Read Response. Check ATT packet value in the received response:

    • • Supported Features field will be present (2 octets), and it indicates features support and optional fields present. Note that bytes will be transmitted using little endian order (i.e. the least significant octet first).
      1. 1. Check Measurement Status support bit (bit 0)
      2. 2. Check Device and Sensor Status support bit (bit 1)
      3. 3. Check SpO2PR-Fast metric support bit (bit 4)
      4. 4. Check SpO2PR-Slow metric support bit (bit 5)
      5. 5. Check Pulse Amplitude Index support bit (bit 6)
    | + +6. Check that bits 8-15 are 0 (reserved for future use). + +- Measurement Status Support field (2 octets) will be present if Measurement Status Support bit = 2. In that case, check that (Note that bytes will be transmitted using little endian order, i.e. the least significant octet first): + 1. Check bits 5-15 values. + 2. Check that bits 0-4 are 0 (Reserved for future use) +- Device and Sensor Status Support field (3 octets) will be present if Device and Sensor Status Support bit = 1. In that case, check that (Note that bytes will be transmitted using little endian order, i.e. the least significant octet first): + 1. Check bits 0-15 values. + 2. Check that bits 16-23 are 0 (Reserved for future use) + +In order to enable notifications on the PLX Continuous Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications. + +Once the PLX Continuous Measurement characteristic has been enabled for notifications, the PHD is expected to send a PLX Continuous measurement to the PHG to check the required fields. + +When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order: + +- A Flags field (1 octet) will be present to indicate which optional fields are present. +- Then, the SpO2PR-Normal field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case. +- The **SpO2PR-Fast field (if present, 4 octets)**, with two subfields, SpO2 (2 octets) and PR (2 octets). Check that: + 1. If SpO2PR-Fast metric support bit = 0, this field is not present. + 2. If SpO2PR-Fast metric support bit = 1, this field is present. +- The **SpO2PR-Slow field (if present, 4 octets)**, with two subfields, SpO2 (2 octets) and PR (2 octets). Check that: + 1. If SpO2PR-Slow metric support bit = 0, this field is not present. + 2. If SpO2PR-Slow metric support bit = 1, this field is present. +- **Measurement Status field (if present, 2 octets)** Check that: + 1. If Measurement Status support bit = 1, this field is present. + 2. If Measurement Status support bit = 0, this field is not present. + 3. Only bits that are supported according to Measurement Status Support field can be equal to 1 that (Note that bytes will be transmitted using little endian order, i.e. the least significant octet first). +- **Device and Sensor Status field (if present, 3 octets)**. Check that: + 1. If Device and Sensor Status support bit = 1, this field is present. + 2. If Device and Sensor Status support bit = 0, this field is not present. + 3. Only bits that are supported according to Device and Sensor Status Support field can be equal to 1 that (Note that bytes will be transmitted using little endian order, i.e. the least significant octet first). +- **Pulse Amplitude Index field (if present, 2 octets)**. Check that: + 1. If Pulse Amplitude Index support bit = 0, this field is not present. + 2. If Pulse Amplitude Index support bit = 1, this field is present. + +| | | | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-019 | | | +| TP label | Whitepaper. PLX Features, RACP Measurement Storage support | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLX Features 1; M | SpO2 Numeric 6; M | +| Test purpose | Check that:
    Spot-Check measurements storage is supported when support bit is set in PLX Features | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 | | | +| Other PICS | C_AG_BLE_041 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Ask the operator to acquire at least a PLX Spot-Check measurement (if RACP characteristic is present, the measurements shall be temporarily stored for later transmission).
    2. 2. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The simulated PHG reads the PLX Features characteristic.
    6. 6. IF C_AG_BLE_041 = FALSE (PHD does not support Spot-Check measurements storage) THEN
      • • Check that Measurement Storage for Spot-Check support bit=0.
    7. 7. IF C_AG_BLE_041 = TRUE (PHD does support Spot-Check measurements storage) THEN
      • • Check that Measurement Storage for Spot-Check support bit=1.
      • • Check that Timestamp for Spot-Check measurements support bit = 1;
      • • Check that Record Access Control Point (0x2A52) characteristic is present.
      • • If RACP characteristic is present:
        • ▪ PHG requests the PHD under test to report stored records by performing a writing operation in the Record Access Control Point (RACP)
        • ▪ PHD under test sends a Spot-Check measurement to the PHG.
        • ▪ Check that Timestamp field is reported in measurement sent by PHD under test
    | | | +| Pass/Fail criteria |

    In Step 6, Measurement Storage for Spot-Check support bit = 0.

    In Step 7:

    • • Measurement Storage for Spot-Check support bit = 1
    • • Timestamp for Spot-Check measurements support bit = 1
    • • Record Access Control Point characteristic is present
    • • Stored measurements report Timestamp field
    | | | +| Notes
    (to assist manual testing)     | To read PLX Features characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2A60. PHG will then receive a Read Response. Check ATT packet value in the received response: | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Supported Features field will be present (2 octets), and it indicates features support and optional fields present. Note that bytes will be transmitted using little endian order (i.e. the least significant octet first).
      1. Check Measurement Storage for Spot-Check support bit (bit 2). IF C_AG_BLE_041 = FALSE, this bit will be 0, ELSE will be 1.
      2. Check Timestamp for Spot-Check measurements support bit (bit 3). IF C_AG_BLE_041 = TRUE this bit will be 1.
    • Measurement Status Support field (if present, 2 octets).
    • Device and Sensor Status Support field (if present, 3 octets)

    Once checked that RACP characteristic exists in the service, to receive PLX Spot-Check measurements from RACP characteristic, PHG enables indications on both PLX Spot-Check Measurement and Record Access Control Point characteristics. In order to enable indications, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications.

    Once both characteristics have been enabled for indications, PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value on the RACP characteristic.

    Once the PHG has performed such operation, an indication will arrive for each stored PLX Spot-Check measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the measurement indications arrive, check the value of received ATT packets (besides header and metadata). Fields and subfields will appear in the following order:

    • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets).
    • Timestamp field (if present, 7 octets). Check that:
      1. This field is present.
    • Measurement Status field (if present, 2 octets)
    • Device and Sensor Status field (if present, 3 octets)
    • Pulse Amplitude Index field (if present, 2 octets)
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-020 | | | +| TP label | Whitepaper. RACP - PLX Spot-Check Measurement, SpO2 and Pulse Rate values | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 1; C | SpO2 Numeric 8; M | +| | | PR Numeric 8; M | PR Numeric 10; M | +| Test purpose | Check that:

    SpO2 subfield of SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic represents the measurement value acquired by BLE PHD and temporarily stored using RACP characteristic.

    [AND]

    PR subfield of SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic represents the measurement value acquired by BLE PHD and temporarily stored using RACP characteristic. | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 AND C_AG_BLE_041 | +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | +| Test procedure |
    1. 1. Ask the operator to acquire at least a PLX Spot-Check measurement (the measurements shall be temporarily stored for later transmission). All measurements stored shall have available SpO2 and PR values.
    2. 2. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report stored records by performing a writing operation in the Record Access Control Point (RACP).
    6. 6. The PHD under test sends at least a PLX Spot-Check measurement to the simulated PHG.
    7. 7. Check measurement(s) sent by PHD under test:
      • • Check that SpO2 value reported in SpO2PR-Spot-Check field is coherent: 70(%) ≤ value ≤ 100(%).
      • • Check that PR value reported in SpO2PR-Spot-Check field is coherent: 20(bpm) ≤ value ≤ 250(bpm).
      • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Spot-Check field are correct.
    | +| Pass/Fail criteria | In Step 7, values of SpO2 and PR subfields of SpO2PR-Spot-Check field are within the ranges specified in Test Procedure and the values are correct. | +| Notes
    (to assist manual testing)     |

    To receive PLX Spot-Check measurements from RACP characteristic, PHG enables indications on both PLX Spot-Check Measurement and Record Access Control Point characteristics. In order to enable indications, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications.

    Once both characteristics have been enabled for indications, PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value on the RACP characteristic.

    Once the PHG has performed such operation, an indication will arrive for each stored PLX Spot-Check measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the measurement indications arrive, check the value of received ATT packets (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Check that:
      1. 1. First subfield contains a value between 70 (0x0046) and 100 (0x0064). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Second subfield contains a value between 20 (0x0014) and 250 (0x00FA). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      3. 3. Check that received values match those actually transmitted.
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Timestamp field (if present, 7 octets).
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-021 | | | +| TP label | Whitepaper. RACP - PLX Spot-Check Measurement, SpO2 and Pulse Rate values unavailable | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 2; M | SpO2 Numeric 20; M | +| Test purpose |

    Check that:

    When SpO2 value of SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic cannot be determined in temporarily stored measurements the special value NaN is used (0x07FF)

    [AND]

    When PR value of SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic cannot be determined in temporarily stored measurements the special value NaN is used (0x07FF)

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 AND C_AG_BLE_041 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Ask the operator to acquire at least a PLX Spot-Check measurement with unavailable SpO2 and PR values (e.g. simulating a measurement or device error). The measurements shall be temporarily stored for later transmission. All measurements stored shall have unavailable SpO2 and PR values.
    2. 2. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report stored records by performing a writing operation in the Record Access Control Point (RACP).
    6. 6. The PHD under test sends at least a PLX Spot-Check measurement with unavailable SpO2 and PR values to the simulated PHG.
    7. 7. Check measurement(s) sent by PHD under test:
      • • Check that SpO2 value reported in SpO2PR-Spot-Check field is the special value NaN (0x07FF)
      • • Check that PR value reported in SpO2PR-Spot-Check field is the special value NaN (0x07FF)
      • • Test Operator checks that SpO2 and Pulse Rate values reported in SpO2PR-Spot-Check field are equal to the special value NaN (unavailable measurements).
    | | | +| Pass/Fail criteria | In Step 7, values of SpO2 and PR subfields of SpO2PR-Spot-Check field are equal to the special value NaN (0x07FF). | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notes
    (to assist manual testing)     |

    To receive PLX Spot-Check measurements from RACP characteristic, PHG enables indications on both PLX Spot-Check Measurement and Record Access Control Point characteristics. In order to enable indications, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications.

    Once both characteristics have been enabled for indications, PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value on the RACP characteristic.

    Once the PHG has performed such operation, an indication will arrive for each stored PLX Spot-Check measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the measurement indications arrive, check the value of received ATT packets (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Check that:
      1. 1. First subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      2. 2. Second subfield contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      3. 3. Check that received values match those actually transmitted.
    • • Timestamp field (if present, 7 octets).
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-022 | | | +| TP label | Whitepaper. RACP - PLX Spot-Check Measurement, Time Stamp value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Date-Time Conv 1; M | SpO2 Numeric 9; M      PR Numeric 9; M | +| Test purpose | Check that:
    Time Stamp field in PLX Spot-Check Measurement characteristic represents the instant of time when BLE PHD acquired and temporarily stored the measurement using RACP characteristic | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 AND C_AG_BLE_041 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure | 1. Ask the operator to acquire at least a PLX Spot-Check measurement (the measurements shall be temporarily stored for later transmission).
    2. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state). | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    2. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    3. 5. The PHG requests the PHD under test to report stored records by performing a writing operation in the Record Access Control Point (RACP).
    4. 6. The PHD under test sends at least a PLX Spot-Check Measurement to the simulated PHG.
    5. 7. Check measurement(s) sent by PHD under test
      • • Check that "Timestamp field is present" Flag = 1
      • • Check that the Time Stamp reported in the Timestamp field is coherent:
        • - Year: 1900 \leq \text{value} \leq 2100 OR value = 0
        • - Month: 1 \leq \text{value} \leq 12 OR value = 0
        • - Day: 1 \leq \text{value} \leq 31 OR value = 0
        • - Hours: 0 \leq \text{value} \leq 23
        • - Minutes: 0 \leq \text{value} \leq 59
        • - Seconds: 0 \leq \text{value} \leq 59
      • • Test Operator checks that the Time Stamp reported in Timestamp field is correct.
    | +| Pass/Fail criteria | In Step 7, Time Stamp is always reported, value of the Timestamp field is within the range specified in Test Procedure and the value is correct. | +| Notes
    (to assist manual testing)     |

    To receive PLX Spot-Check measurements from RACP characteristic, PHG enables indications on both PLX Spot-Check Measurement and Record Access Control Point characteristics. In order to enable indications, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications.

    Once both characteristics have been enabled for indications, PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value on the RACP characteristic.

    Once the PHG has performed such operation, an indication will arrive for each stored PLX Spot-Check measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the measurement indications arrive, check the value of received ATT packets (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 0 (Timestamp field is present) is set to 1.
      2. 2. Bit 0 (Timestamp field is present) is set to 0.
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (7 octets) will be present, check in that field that:
      1. 1. First 2 octets (Year) are between 1900 (0x076C) and 2100 (0x0834) OR they are equal to 0x0000. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Month (1 octet) will be between 1 (0x01) and 12 (0x0C) OR equal to 0 (0x00).
      3. 3. Day (1 octet) will be between 1 (0x01) and 31 (0x1F) OR equal to 0 (0x00).
      4. 4. Hour (1 octet) will be between 0 (0x00) and 23 (0x17).
    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    5. Minute (1 octet) will be between 0 (0x00) and 59 (0x3B).

    6. Second (1 octet) will be between 0 (0x00) and 59 (0x3B).

    7. Check that received values match those actually transmitted.

    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-023 | | | +| TP label | Whitepaper. RACP - PLX Spot-Check Measurement, Measurement Status value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SpO2 Numeric 7; M | PR Numeric 7; M | +| Test purpose |

    Check that:

    If Measurement Status field is sent in temporarily stored PLX Spot-Check Measurements, it is set to a valid value.

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 AND C_AG_BLE_041 | | | +| Other PICS | C_AG_BLE_036 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Ask the operator to acquire at least a PLX Spot-Check measurement (the measurements shall be temporarily stored for later transmission).
    2. 2. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report stored records by performing a writing operation in the Record Access Control Point (RACP).
    6. 6. The PHD under test sends at least a PLX Spot-Check Measurement to the simulated PHG.
    7. 7. Check measurement(s) sent by PHD under test
      1. a. IF C_AG_BLE_036 = TRUE (PHD reports Measurement Status) THEN
        • • Check that "Measurement Status field is present" Flag = 1
        • • Check that Measurement Status field reported in PLX Spot-Check Measurement is present, and is set to allowed values: bits 5 to 15 may be set to 0 or 1, Bits 0 to 4 are reserved for future use and must be set to 0
        • • Test Operator checks that the Measurement Status value reported in the PLX Spot-Check Measurement is correct
      2. b. IF C_AG_BLE_036 = FALSE (PHD does not report Measurement Status) THEN
        • • Check that "Measurement Status field is present" Flag = 0
        • • Check that Measurement Status field is not reported
    | | | +| Pass/Fail criteria |

    In Step 7.a, values of Measurement Status field are correct.

    In Step 7.b, Measurement Status field is not present in any measurement

    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notes
    (to assist manual testing)     |

    To receive PLX Spot-Check measurements from RACP characteristic, PHG enables indications on both PLX Spot-Check Measurement and Record Access Control Point characteristics. In order to enable indications, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications.

    Once both characteristics have been enabled for indications, PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value on the RACP characteristic.

    Once the PHG has performed such operation, an indication will arrive for each stored PLX Spot-Check measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the measurement indications arrive, check the value of received ATT packets (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      • 1. Bit 1 (Measurement Status field is present) is set to 1 IF C_AG_BLE_036 = TRUE
      • 2. Bit 1 (Measurement Status field is present) is set to 0 IF C_AG_BLE_036 = FALSE
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (if present, 7 octets)
    • • Measurement Status field (2 octets) will be present IF C_AG_BLE_036 = TRUE. In that case, check in that field that:
      • 1. Bits 0 to 4 are reserved for future use and are equal to 0. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 2. Bits 5 to 15 may be 0 or 1. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 3. Check that received values match those actually transmitted.
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (if present, 2 octets)
    | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-024 | | | +| TP label | Whitepaper. RACP - PLX Spot-Check Measurement, Device and Sensor Status value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DSS Enumeration 4; M | | +| Test purpose | Check that:

    If Device and Sensor Status field is sent in temporarily stored PLX Spot-Check Measurements, it is set to a valid value. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 AND C_AG_BLE_041 | | | +| Other PICS | C_AG_BLE_037 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure | 1. Ask the operator to acquire at least a PLX Spot-Check measurement (the measurements shall be temporarily stored for later transmission).

    2. Turn on the PHD under test, and configure it as discoverable Bluetooth device (Advertising state). | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    2. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    3. 5. The PHG requests the PHD under test to report stored records by performing a writing operation in the Record Access Control Point (RACP).
    4. 6. The PHD under test sends at least a PLX Spot-Check Measurement to the simulated PHG.
    5. 7. Check measurement(s) sent by PHD under test
      1. a. IF C_AG_BLE_037 = TRUE (PHD reports Device and Sensor Status) THEN
        • • Check that "Device and Sensor Status field is present" Flag = 1
        • • Check that Device Sensor Status field reported in PLX Spot-Check Measurement is present, and is set to allowed values: bits 0 to 15 may be set to 0 or 1, Bits 16 to 23 are reserved for future use and must be set to 0
        • • Test Operator checks that the Device and Sensor Status value reported in the PLX Spot-Check Measurement is correct
      2. b. IF C_AG_BLE_037 = FALSE (PHD does not report Device and Sensor Status) THEN
        • • Check that "Device and Sensor Status field is present" Flag = 0
        • • Check that Device and Sensor Status field is not reported
    | +| Pass/Fail criteria |

    In Step 7.a, values of Device and Sensor Status field are correct.

    In Step 7.b, Device and Sensor Status field is not present in any measurement.

    | +| Notes
    (to assist manual testing)     |

    To receive PLX Spot-Check measurements from RACP characteristic, PHG enables indications on both PLX Spot-Check Measurement and Record Access Control Point characteristics. In order to enable indications, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications.

    Once both characteristics have been enabled for indications, PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value on the RACP characteristic.

    Once the PHG has performed such operation, an indication will arrive for each stored PLX Spot-Check measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the measurement indications arrive, check the value of received ATT packets (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 2 (Device and Sensor Status field is present) is set to 1 IF C_AG_BLE_037 = TRUE
      2. 2. Bit 2 (Device and Sensor Status field is present) is set to 0 IF C_AG_BLE_037 = FALSE
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (if present, 7 octets)
    • • Measurement Status field (if present, 2 octets)
    • • Device and Sensor Status field (3 octets) will be present IF C_AG_BLE_037 = TRUE. In that case, check in that field that:
      1. 1. Bits 16 to 23 are reserved for future use and are equal to 0. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. Bits 0 to 15 may be 0 or 1. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
    2. 3. Check that received values match those actually transmitted.
    3. 4. Pulse Amplitude Index field (if present, 2 octets)
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-025 | | | +| TP label | Whitepaper. RACP - PLX Spot-Check Measurement, Pulse Amplitude Index value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 1; C | PQ Numeric 8; M | +| Test purpose |

    Check that:

    Pulse Amplitude Index field in PLX Spot-Check Measurement characteristic represents the measurement value acquired and temporarily stored by BLE PHD

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 AND C_AG_BLE_041 | | | +| Other PICS | C_AG_BLE_038 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Ask the operator to acquire at least a PLX Spot-Check measurement (the measurements shall be temporarily stored for later transmission).
    2. 2. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report stored records by performing a writing operation in the Record Access Control Point (RACP).
    6. 6. The PHD under test sends at least a PLX Spot-Check measurement.
    7. 7. Check measurement(s) sent by PHD under test
      1. a. IF C_AG_BLE_038 = TRUE (PHD reports Pulse Amplitude Index) THEN
        • • Check that "Pulse Amplitude Index field is present" Flag = 1
        • • Check that Pulse Amplitude Index value reported in Pulse Amplitude Index field is coherent: 1(\%) \leq \text{value} \leq 100(\%)
        • • Test Operator checks that the Pulse Amplitude Index value reported in the PLX Spot-Check Measurement is correct
      2. b. IF C_AG_BLE_038 = FALSE (PHD does not report Pulse Amplitude Index) THEN
        • • Check that "Pulse Amplitude Index field is present" Flag = 0
    | | | +| Pass/Fail criteria |

    In Step 7.a, values of Pulse Amplitude Index field are correct.

    In Step 7.b, Pulse Amplitude Index field is not present in any measurement.

    | | | +| Notes
    (to assist manual testing)     |

    To receive PLX Spot-Check measurements from RACP characteristic, PHG enables indications on both PLX Spot-Check Measurement and Record Access Control Point characteristics. In order to enable indications, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications.

    | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Once both characteristics have been enabled for indications, PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value on the RACP characteristic.

    Once the PHG has performed such operation, an indication will arrive for each stored PLX Spot-Check measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the measurement indications arrive, check the value of received ATT packets (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      • 1. Bit 3 (Pulse Amplitude Index field is present) is set to 1 IF C_AG_BLE_038 = TRUE
      • 2. Bit 3 (Pulse Amplitude Index field is present) is set to 0 IF C_AG_BLE_038 = FALSE
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (if present, 7 octets)
    • • Measurement Status field ( if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (2 octets) will be present IF C_AG_BLE_038 = TRUE. In that case, check in that field that:
      • 1. It contains a value between 1 (0x0001) and 100 (0x0064). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 2. Check that received values match those actually transmitted.
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/PLX/BV-026 | | | +| TP label | Whitepaper. RACP - PLX Spot-Check Measurement, Pulse Amplitude Index value unavailable | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 2; M | PQ Numeric 8; M | +| Test purpose |

    Check that:

    Pulse Amplitude Index field in PLX Spot-Check Measurement characteristic represents an unavailable value (e.g. due to a measurement or device error) using the special value NaN in temporarily stored measurements.

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_032 AND C_AG_BLE_033 AND C_AG_BLE_038 AND C_AG_BLE_041 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Ask the operator to acquire at least a PLX Spot-Check measurement including an unavailable value in the Pulse Amplitude Index field (e.g. simulating a measurement or device error). The measurement shall be temporarily stored for later transmission. All measurements stored shall have unavailable Pulse Amplitude Index values.
    2. 2. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    2. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    3. 5. The PHG requests the PHD under test to report stored records by performing a writing operation in the Record Access Control Point (RACP).
    4. 6. The PHD under test sends at least PLX Spot-Check measurement with an unavailable value in the Pulse Amplitude Index field.
    5. 7. Check measurement(s) sent by PHD under test
      • • Check that "Pulse Amplitude Index field is present" Flag = 1
      • • Check that Pulse Amplitude Index value reported in Pulse Amplitude Index field is equal to special value NaN (0x07FF)
      • • Test Operator checks that the Pulse Amplitude Index value reported in the PLX Spot-Check Measurement is equal to special value NaN (0x07FF)
    | +| Pass/Fail criteria | In Step 7, values of Pulsatile Amplitude Index field are equal to special value NaN (0x07FF) | +| Notes
    (to assist manual testing)     |

    To receive PLX Spot-Check measurements from RACP characteristic, PHG enables indications on both PLX Spot-Check Measurement and Record Access Control Point characteristics. In order to enable indications, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications.

    Once both characteristics have been enabled for indications, PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value on the RACP characteristic.

    Once the PHG has performed such operation, an indication will arrive for each stored PLX Spot-Check measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the measurement indications arrive, check the value of received ATT packets (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check that:
      1. 1. Bit 3 (Pulse Amplitude Index field is present) is set to 1.
      2. 2. Bit 3 (Pulse Amplitude Index field is present) is set to 0.
    • • Then, the SpO2PR-Spot-Check field (4 octets) will be present, with two subfields, SpO2 (2 octets) and PR (2 octets). Values are not relevant for this test case.
    • • Timestamp field (if present, 7 octets)
    • • Measurement Status field ( if present, 2 octets)
    • • Device and Sensor Status field (if present, 3 octets)
    • • Pulse Amplitude Index field (2 octets) will be present. Check in that field that:
      1. 1. It contains the value 0x07FF. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first), so value will be received as (FF 07).
      2. 2. Check that received values match those actually transmitted.
    | + +### A.9 Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +| | | +|-----------------|--------------------------------------------------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-000 | +| TP label | Whitepaper. CGM Measurement, CGM Glucose Concentration value | + +| | | | | | +|---------------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------| +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 1; C | Glucose Numeric 6; M | Glucose Numeric 8; M | +| Test purpose | | Check that:

    CGM Glucose Concentration field in CGM Measurement characteristic represents the measurement value acquired by BLE PHD | | | +| Applicability | | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | | | | | +| Initial condition | | The PHD under test and the Simulated PHG are in Standby state. | | | +| Test procedure | |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test sends a CGM measurement to the simulated PHG.
    5. 5. Check the measurement sent by the PHD under test
      • • Check that blood glucose concentration value reported in CGM Glucose Concentration field is coherent: 0(\text{mg/dL}) \leq \text{value} \leq 2700(\text{mg/dL}).
      • • Test Operator checks that blood glucose concentration value reported in CGM Glucose Concentration field is correct.
    | | | +| Pass/Fail criteria | | In Step 5, the value of the CGM Glucose Concentration field is within the ranges specified in Test Procedure and the values are correct. | | | +| Notes
    (to assist manual testing)     | |

    In order to enable notifications on the CGM Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    For this particular Test Case, the PHD is expected to send at least a CGM Measurement notification containing one CGM Measurement record to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present. Check that:
      1. 1. Value contained is between 0 (0x0000) and 2700 (0x0A8C). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Check that received value match that actually transmitted.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      1. 1. Warning-Octet (if present, 1 octet)
      2. 2. Cal/Temp-Octet (if present, 1 octet)
      3. 3. Status-Octet (if present, 1 octet)
    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    | | | + +| | | +|--|----------------------------------------------------------------------------------------| +| |
    • E2E-CRC field (if present, 2 octets)
    | +|--|----------------------------------------------------------------------------------------| + +| | | | | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-001 | | | | +| TP label | Whitepaper. CGM Measurement, CGM Glucose Concentration value below device capabilities | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 2; M | Glucose Numeric 9; M | | +| Test purpose |

    Check that:

    If the CGM Measurement is below device capabilities, value of the CGM Glucose Concentration field shall be -INFINITY.

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. The PHD under test sends a CGM measurement below device capabilities to the simulated PHG.
    5. Check the measurement sent by the PHD under test
      • Check that blood glucose concentration value reported in CGM Glucose Concentration field is -INFINITY (0x0802)
      • Test Operator checks that blood glucose concentration value is -INFINITY (0x0802)
    | | | | +| Pass/Fail criteria | In Step 5, value of CGM Glucose Concentration field is below device capabilities and it is represented as -INFINITY (0x0802). | | | | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the CGM Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications. For this particular Test Case, the PHD is expected to send at least a CGM Measurement notification containing one CGM Measurement record to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • Then, the CGM Glucose Concentration field (2 octets) will be present. Check that:
      1. Value contained is (0x0802). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. Check that received value match that actually transmitted.
    • Time Offset field (2 octets).
    | | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Sensor Status Annunciation field (if present, up to 3 octets)
      1. Warning-Octet (if present, 1 octet)
      2. Cal/Temp-Octet (if present, 1 octet)
      3. Status-Octet (if present, 1 octet). If present, bit 6 of this octet (22 of total) shall be set to 1.
    • CGM Trend Information field (if present, 2 octets)
    • CGM Quality field (if present, 2 octets)
    • E2E-CRC field (if present, 2 octets)
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-002 | | | | +| TP label | Whitepaper. CGM Measurement, CGM Glucose Concentration value above device capabilities | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 2; M | Glucose Numeric 9; M | | +| Test purpose |

    Check that:

    If the CGM Measurement is above device capabilities, value of the CGM Glucose Concentration field shall be +INFINITY.

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. The PHD under test sends a CGM measurement above device capabilities to the simulated PHG.
    5. Check the measurement sent by the PHD under test
      • Check that blood glucose concentration value reported in CGM Glucose Concentration field is +INFINITY (0x07FE)
      • Test Operator checks that blood glucose concentration value is +INFINITY (0x07FE)
    | | | | +| Pass/Fail criteria | In Step 5, value of CGM Glucose Concentration field is above device capabilities and it is represented as +INFINITY (0x07FE). | | | | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the CGM Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    For this particular Test Case, the PHD is expected to send at least a CGM Measurement notification containing one CGM Measurement record to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    | | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present. Check that:
      1. 1. Value contained is (0x07FE). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Check that received value match that actually transmitted.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      1. 1. Warning-Octet (if present, 1 octet)
      2. 2. Cal/Temp-Octet (if present, 1 octet)
      3. 3. Status-Octet (if present, 1 octet). If present, bit 7 of this octet (23 of total) shall be set to 1.
    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-003 | | | +| TP label | Whitepaper. CGM Measurement, CGM Glucose Concentration special values | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 2; M | Glucose Numeric 10; M | +| Test purpose | Check that:
    Device reports a NaN or NRes value in the CGM Glucose Concentration field of the CGM Measurement characteristic to signal some problem during measurement. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The PHD under test shall simulate some problem during measurement and send the CGM measurement using a special value to the simulated PHG.
    5. 5. Check the measurement sent by the PHD under test
      • • Check that blood glucose concentration value reported in CGM Glucose Concentration field is set to NaN (0x07FF) or NRes (0x0800).
      • • Test Operator checks that blood glucose concentration value reported in CGM Glucose Concentration field is one of the mentioned above due to a measurement problem.
    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | In Step 5, value of CGM Glucose Concentration field is set to NaN (0x07FF) or NRes (0x0800) due to a measurement error. | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the CGM Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    For this particular Test Case, the PHD is expected to send at least a CGM Measurement notification containing one CGM Measurement record with a measurement error to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present. Check that:
      • 1. Value contained is (0x07FF) or (0x0800). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 2. Check that received value match that actually transmitted.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      • 1. Warning-Octet (if present, 1 octet)
      • 2. Cal/Temp-Octet (if present, 1 octet)
      • 3. Status-Octet (if present, 1 octet)
    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-004 | | | +| TP label | Whitepaper. CGM Measurement, Time Offset value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | BaseOffset 3; M | Glucose Numeric 7; M | +| Test purpose |

    Check that:

    Time offset field of the CGM Measurement characteristic specifies the relative time difference of the single CGM value to the session start time in minutes.

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. The PHD under test sends a CGM measurement to the simulated PHG.

    5. Check the measurement sent by the PHD under test

    • • Check value reported in Time Offset field (0x0000-0xFFFF) (uint16).
    • • Test Operator checks that time offset value in minutes specifies the relative time difference of the single CGM value to the session start time in minutes.
    | +| Pass/Fail criteria | In Step 5, value of Time Offset field specifies the relative time difference of the single CGM value to the session start time as an uint16 (0x0000-0xFFFF) in minutes. | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the CGM Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    For this particular Test Case, the PHD is expected to send at least a CGM Measurement notification containing one CGM Measurement record to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present.
    • • Time Offset field (2 octets). Check that:
      • 1. The received value match that actually transmitted.
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      • 1. Warning-Octet (if present, 1 octet)
      • 2. Cal/Temp-Octet (if present, 1 octet)
      • 3. Status-Octet (if present, 1 octet)
    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-005 | | | +| TP label | Whitepaper. CGM Measurement, Sensor Status Annunciation value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 5; M | | +| Test purpose |

    Check that:

    If Sensor Status Annunciation field is sent in CGM Measurement, its length and value are correct.

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | C_AG_BLE_043 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |

    1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).

    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    2. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    3. 4. The PHD under test sends a CGM Measurement to the simulated PHG.
    4. 5. Check the measurement sent by the PHD under test
      1. a. IF C_AG_BLE_043 = TRUE (CGM PHD reports Sensor Status Annunciation) THEN
        • • One of more of flags 5 (Sensor Status Annunciation field, Warning-Octet present), 6 (Sensor Status Annunciation field, Cal/Temp-Octet present) or 7 (Sensor Status Annunciation field, Status-Octet present) are set to 1.
        • • Check that:
          • ▪ If flag 5 is set to 1, then Sensor Status Annunciation Warning-Octet field is present (bits 0 to 7) and at least one bit is set to 1. Bits 6 and 7 shall be set to 0 (reserved for future use). Rest of bits may be set to 0 or 1.
          • ▪ If flag 6 is set to 1, then Sensor Status Annunciation Cal/Temp-Octet field is present (bits 8 to 15) and at least one bit is set to 1. Bits 14 and 15 shall be set to 0 (reserved for future use). Rest of bits may be set to 0 or 1.
          • ▪ If flag 7 is set to 1, then Sensor Status Annunciation Status-Octet field is present (bits 16 to 23) and at least one bit is set to 1. Bits may be set to 0 or 1.
        • • Test Operator checks that the Sensor Status Annunciation field value and size reported in the CGM Measurement are correct
      2. b. IF C_AG_BLE_043 = FALSE (CGM PHD does not report Sensor Status Annunciation) THEN
        • • Check that flags 5, 6 and 7 are set to 0.
        • • Check that Sensor Status Annunciation octets are not reported
    | +| Pass/Fail criteria |
    • • In Step 5.a, value and size of the Sensor Status Annunciation field are as specified according to value of Flags field.
    • • In Step 5.b, flags 5, 6 and 7 are set to 0 and Sensor Status Annunciation field is not present.
    | +| Notes
    (to assist manual testing)     |

    In order to enable notifications on the CGM Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    For this particular Test Case, the PHD is expected to send at least a CGM Measurement notification containing one CGM Measurement record to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check value of flags 5, 6 and 7.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets). Check that (note that bytes will be transmitted using little endian order (i.e., the least significant octet first):
      1. 1. If flag 5 is set to 1, then Warning-Octet is present. If present, bits 0-5 may be set to 0 or 1 and bits 6-7 shall be set to 0. If present, at least one bit shall be set to 1.
    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. If flag 6 is set to 1, then Cal/Temp-Octet is present. If present, bits 8-13 may be set to 0 or 1 and bits 14-15 shall be set to 0. If present, at least one bit shall be set to 1.

    3. If flag 7 is set to 1, then Status-Octet is present. If present, bits 16-23 may be set to 0 or 1. If present, at least one bit shall be set to 1.

    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-006 | | | +| TP label | Whitepaper. CGM Measurement, CGM Trend Information value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 7; M | | +| Test purpose | Check that:
    If CGM Trend Information field is sent in CGM Measurement, its value is correct. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | C_AG_BLE_044 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. PHD under test sends a CGM Measurement to the simulated PHG.
    5. 5. Check the measurement sent by the PHD under test
      1. a. IF C_AG_BLE_044 = TRUE (CGM PHD reports Glucose Trend Information) THEN
        • • Flag 0 (CGM Trend Information present) is set to 1.
        • • CGM Trend Information field is present as an SFLOAT value in (mg/dL)/min units.
        • • Test Operator checks that the CGM Trend Information field value reported in the CGM Measurement is correct
      2. b. IF C_AG_BLE_044 = FALSE (CGM PHD does not report Glucose Trend Information) THEN
        • • Check that flag 0 is set to 0.
        • • Check that CGM Trend Information field is not reported
    | | | +| Pass/Fail criteria |
    • • In Step 5.a, flag 0 is set to 1, CGM Trend Information field is reported and its value is correct.
    • • In Step 5.b, flags 0 is set to 0 and the CGM Trend Information field is not reported.
    | | | +| Notes
    (to assist manual testing)     | In order to enable notifications on the CGM Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications. | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    For this particular Test Case, the PHD is expected to send at least a CGM Measurement notification containing one CGM Measurement record to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check value of flag 0.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      • 1. Warning-Octet (if present, 1 octet)
      • 2. Cal/Temp-Octet (if present, 1 octet)
      • 3. Status-Octet (if present, 1 octet)
    • • CGM Trend Information field (if present, 2 octets). Check that:
      • 1. If flag 0 is set to 1, this field is present and it is set to the reported value (SFLOAT, (mg/dL)/min).
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-007 | | | +| TP label | Whitepaper. CGM Status. Time Offset value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | CGM Enumeration 4; M | PHDM Enumeration 5; M | +| Test purpose |

    Check that:

    Time offset field of the CGM Status characteristic specifies the actual relative time difference to the session start time.

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG reads the CGM Status characteristic.
    5. 5. Check the CGM Status characteristic:
      • • Check value of the Time Offset field (0x0000-0xFFFF) (uint16).
      • • Test Operator checks that time offset value in minutes specifies the actual relative time to the session start time
    | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | Value of Time Offset field matches the actual relative time difference in minutes to the session start time. | +| Notes
    (to assist manual testing)     |

    To read the CGM Status characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2AA9. PHG will then receive a Read Response. Check ATT packet value in the received response. Fields will appear in the following order:

    • • Time Offset field (2 octets) will be present. Check that:
      • 1. Its value (uint16) matches the actual relative time difference in minutes to the session start time.
    • • CGM Status field (3 octets) will be present.
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-008 | | | +| TP label | Whitepaper. CGM Status. CGM Status value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | CGM Enumeration 4; M | PHDM Enumeration 5; M | +| Test purpose |

    Check that:

    CGM Status field of the CGM Status characteristic allows the collector to request the current status from the CGM Sensor and its value and format are correct.

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The Simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG reads the CGM Status characteristic.
    5. 5. Check the CGM Status characteristic:
      • • Check value of the CGM Status field (24 bits). Bits 6-7 and 14-15 shall be set to 0 (reserved for future use). Rest of bits may be set to 0 or 1.
      • • Test Operator checks that CGM Status field matches the current status of the CGM Sensor.
    | | | +| Pass/Fail criteria | Value of CGM Status field matches the current status of the CGM Sensor and its format is correct. | | | +| Notes
    (to assist manual testing)     |

    To read the CGM Status characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2AA9. PHG will then receive a Read Response. Check ATT packet value in the received response. Fields will appear in the following order:

    • • Time Offset field (2 octets) will be present.
    • • CGM Status field (3 octets) will be present. Check that:
      • 1. Bits 6-7 and 14-15 shall be set to 0 (reserved for future use). Rest of bits may be set to 0 or 1.
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. Value matches the current status of the CGM Sensor.

    • • E2E-CRC field (if present, 2 octets)
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-009 | | | +| TP label | Whitepaper. CGM Session Start Time. Session Start Time value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 7; M | SensCal Numeric 11; M | +| | | GT Numeric 6; M | PLH Numeric 9; M | +| | | GRC Numeric 9; M | PHDM Enumeration 5; M | +| | | Date-Time Conv 1; M | CGM Enumeration 4; M | +| Test purpose |

    Check that:

    Session Start Time field in CGM Session Start Time characteristic represents the time of the initial CGM measurement.

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG reads the CGM Session Start Time characteristic.
    5. 5. Check the CGM Session Start Time characteristic:
      • • Check that the values of the subfields of the Session Start Time field are coherent:
        • - Year: 1900 \leq \text{value} \leq 2100 OR value = 0
        • - Month: 1 \leq \text{value} \leq 12 OR value = 0
        • - Day: 1 \leq \text{value} \leq 31 OR value = 0
        • - Hours: 0 \leq \text{value} \leq 23
        • - Minutes: 0 \leq \text{value} \leq 59
        • - Seconds: 0 \leq \text{value} \leq 59
      • • Test Operator checks that the value of the Session Start Time field is correct and matches the time of the initial CGM measurement.
    | | | +| Pass/Fail criteria | Value of the Session Start Time field is within the range specified in the Test Procedure and the value is correct. | | | +| Notes
    (to assist manual testing)     | To read the CGM Session Start Time characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2AAA. PHG will then receive a Read Response. Check ATT packet value in the received response. Fields will appear in the following order: | | | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Session Start Time field (7 octets) will be present. Check that:
      1. 1. First 2 octets (Year) are between 1900 (0x076C) and 2100 (0x0834) OR they are equal to 0x0000. Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Month (1 octet) will be between 1 (0x01) and 12 (0x0C) OR equal to 0 (0x00).
      3. 3. Day (1 octet) will be between 1 (0x01) and 31 (0x1F) OR equal to 0 (0x00).
      4. 4. Hour (1 octet) will be between 0 (0x00) and 23 (0x17).
      5. 5. Minute (1 octet) will be between 0 (0x00) and 59 (0x3B).
      6. 6. Second (1 octet) will be between 0 (0x00) and 59 (0x3B).
      7. 7. Check that values match those actually written to the characteristic.
    • • Time Zone field (1 octet) will be present.
    • • DST-Offset field (1 octet) will be present.
    • • E2E-CRC field (if present, 2 octets)
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-010 | | +| TP label | Whitepaper. CGM Session Run Time. CGM Session Run Time value | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | +| | Testable items | SRT Numeric 6; M | +| Test purpose | Check that:

    CGM Session Run Time field in CGM Session Run Time characteristic represents the expected run time of the CGM session in a correct format. | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | +| Other PICS | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG reads the CGM Session Run Time characteristic.
    5. 5. Check the CGM Session Run Time characteristic:
      • • Check the value (hours) of the CGM Session Run Time field (uint16)
      • • Test Operator checks that the value of the Session Run Time field is correct and matches the expected run time of the CGM Session.
    | | +| Pass/Fail criteria | Value of the CGM Session Run Time field represents the number of hours expected for a CGM session. | | +| Notes
    (to assist manual testing)     | To read the CGM Session Run Time characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2AAB. PHG will then receive a Read Response. Check ATT packet value in the received response. Fields will appear in the following order:
    • • CGM Session Run Time field (2 octets) will be present. Check:
    | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 1. Field value as an uint16 (hours)
    2. 2. Check that read value matches correct field value.
    • • E2E-CRC field (if present, 2 octets)
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-011 | | | | +| TP label | Whitepaper. CGM Feature. CGM Measurement | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | CGM Feature 1; M | CGM Feature 2; C | | +| Test purpose | Check that:
    CGM Feature characteristic and CGM Measurement fields are coherent. | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG reads the CGM Feature characteristic.
    5. 5. The PHD under test sends a CGM Measurement to the simulated PHG.
    6. 6. In the CGM Feature field of CGM Feature characteristic:
      1. a. Check Calibration support bit
      2. b. Check Patient High/Low Alerts support bit.
      3. c. Check Hypo Alerts support bit.
      4. d. Check Hyper Alerts support bit.
      5. e. Check Rate of Increase/Decrease Alerts support bit.
      6. f. Check Device Specific Alert support bit.
      7. g. Check Sensor Malfunction Detection support bit.
      8. h. Check Sensor Temperature High-Low Detection support bit.
      9. i. Check Sensor Result High-Low Detection support bit.
      10. j. Check Low Battery Detection support bit.
      11. k. Check Sensor Type Error Detection support bit.
      12. l. Check General Device Fault support bit.
      13. m. Check CGM Trend Information support bit.
      14. n. Check that bits 17-23 are 0 (Reserved for future use)
    7. 7. In CGM Measurement, if Sensor Status Annunciation field Status Octet is present:
      1. a. Check bit 1 (Device Battery Low)
      2. b. Check bit 2 (Sensor Type Incorrect for Device)
      3. c. Check bit 3 (Sensor Malfunction)
    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • d. Check bit 4 (Device Specific Alert)
    • e. Check bit 5 (General Device Fault has occurred in the sensor)
    1. 8. In CGM Measurement, if Sensor Status Annunciation field Cal/Temp Octet is present:
      • a. Check bits 9-11 (Calibration not allowed, calibration recommended, and calibration required)
      • b. Check bits 12-13 (Sensor Temperature too high for valid test/result at time of measurement, Sensor Temperature too low for valid test/result at time of measurement)
    2. 9. In CGM Measurement, if Sensor Status Annunciation field Warning Octet is present:
      • a. Check bits 16-17 (Sensor result lower than the Patient Low level and Sensor result higher than the Patient High Level).
      • b. Check bit 18 (Sensor result lower than the Hypo Level)
      • c. Check bit 19 (Sensor result higher than the Hyper Level)
      • d. Check bits 20-21 (Sensor Rate of Decrease exceeded and Sensor Rate of Increase exceeded).
      • e. Check bits 22-23 (Sensor result lower than the device can process and Sensor result higher than the device can process).
    3. 10. In CGM Measurement
      • a. Check if CGM Trend Information field is reported
    | +| Pass/Fail criteria |

    In Step 7:

    • • If Low Battery Detection support bit is set to 1 (6.j), Device Battery Low bit (1) may be set to 1, else it is set to 0.
    • • If Sensor Type Error Detection support bit is set to 1 (6.k), Sensor Type Incorrect for Device bit (2) may be set to 1, else it is set to 0.
    • • If Sensor Malfunction Detection support bit is set to 1 (6.g), Sensor Malfunction bit (3) may be set to 1, else it is set to 0.
    • • If Device Specific Alert support bit is set to 1 (6.f), Device Specific Alert bit (4) may be set to 1, else it is set to 0.
    • • If General Device Fault support bit is set to 1 (6.l), General Device Fault has occurred in the sensor bit (5) may be set to 1, else it is set to 0.

    In Step 8:

    • • If Calibration support bit is set to 1 (6.a), one of bits 9-11 (Calibration not allowed, calibration recommended, and calibration required) may be set to 1, else they are set to 0.
    • • If Sensor Temperature High-Low Detection support bit is set to 1 (6.h), one of bits 12-13 (Sensor Temperature too high for valid test/result at time of measurement, Sensor Temperature too low for valid test/result at time of measurement) may be set to 1, else they are set to 0.

    In Step 9:

    • • If Patient High/Low Alerts support bit is set to 1 (6.b), one of bits 16-17 (Sensor result lower than the Patient Low level and Sensor result higher than the Patient High Level) may be set to 1, else they are set to 0.
    • • If Hypo Alerts support bit is set to 1 (6.c), Sensor result lower than the Hypo Level bit (18) may be set to 1, else it is set to 0.
    • • If Hyper Alerts support bit is set to 1 (6.d), Sensor result higher than the Hyper Level bit (19) may be set to 1, else it is set to 0.
    • • If Rate of Increase/Decrease Alerts support bit is set to 1 (6.e), one of bits 20-21 (Sensor Rate of Decrease exceeded and Sensor Rate of Increase exceeded) may be set to 1, else they are set to 0.
    • • If Sensor Result High-Low Detection support bit is set to 1 (6.i), one of bits 22-23 (Sensor result lower than the device can process and Sensor result higher than the device can process) may be set to 1, else they are set to 0.
    | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    In Step 10:

    • • If CGM Trend Information support bit is set to 1 (6.m), CGM Trend Information field may be present, else it is not present.
    | +| Notes
    (to assist manual testing)     |

    To read CGM Feature characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2AA8. PHG will then receive a Read Response. Check ATT packet value in the received response:

    • • CGM Feature field will be present (3 octets), and it indicates features support and optional fields present. Note that bytes will be transmitted using little endian order (i.e. the least significant octet first).
      1. 1. Check support bits as stated above.
      2. 2. Check that bits 17-23 are 0 (reserved for future use).
    • • CGM Type field (4 bits) will be present.
    • • CGM Sample Location field (4 bits) will be present.
    • • E2E-CRC field (2 octets) will be present.

    In order to enable notifications on the CGM Measurement characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for notifications.

    For this particular Test Case, the PHD is expected to send at least a CGM Measurement notification containing one CGM Measurement record to the PHG to check the required fields.

    When the notification arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      1. 1. Warning-Octet (if present, 1 octet). Check bits as stated in step 7.
      2. 2. Cal/Temp-Octet (if present, 1 octet). Check bits as stated in step 8.
      3. 3. Status-Octet (if present, 1 octet). Check bits as stated in step 9.
    • • CGM Trend Information field (if present, 2 octets). Check that:
      1. 1. If CGM Trend Information support bit 1 in CGM Feature characteristic, this field may be present and if so, it is set to the reported value (SFLOAT, (mg/dL)/min). If CGM Trend Information support bit is set to 0 this field shall not be present.
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|----------------------|-------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-012 | | | +| TP label | Whitepaper. CGM Feature. CGM Status | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | CGM Feature 1; M | CGM Feature 3; C | +| Test purpose | Check that:
    CGM Feature and CGM Status characteristics are coherent. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG reads the CGM Feature characteristic.
    5. 5. The simulated PHG reads the CGM Status characteristic.
    6. 6. In the CGM Feature field of CGM Feature characteristic:
      1. a. Check Calibration support bit
      2. b. Check Patient High/Low Alerts support bit.
      3. c. Check Hypo Alerts support bit.
      4. d. Check Hyper Alerts support bit.
      5. e. Check Rate of Increase/Decrease Alerts support bit.
      6. f. Check Device Specific Alert support bit.
      7. g. Check Sensor Malfunction Detection support bit.
      8. h. Check Sensor Temperature High-Low Detection support bit.
      9. i. Check Sensor Result High-Low Detection support bit.
      10. j. Check Low Battery Detection support bit.
      11. k. Check Sensor Type Error Detection support bit.
      12. l. Check General Device Fault support bit.
      13. m. Check CGM Trend Information support bit.
      14. n. Check that bits 17-23 are 0 (Reserved for future use)
    7. 7. In CGM Status characteristic:
      1. a. Check bit 1 (Device Battery Low)
      2. b. Check bit 2 (Sensor Type Incorrect for Device)
      3. c. Check bit 3 (Sensor Malfunction)
      4. d. Check bit 4 (Device Specific Alert)
      5. e. Check bit 5 (General Device Fault has occurred in the sensor)
      6. f. Check bits 9-11 (Calibration not allowed, calibration recommended, and calibration required)
      7. g. Check bits 12-13 (Sensor Temperature too high for valid test/result at time of measurement, Sensor Temperature too low for valid test/result at time of measurement)
      8. h. Check bits 16-17 (Sensor result lower than the Patient Low level and Sensor result higher than the Patient High Level).
      9. i. Check bit 18 (Sensor result lower than the Hypo Level)
      10. j. Check bit 19 (Sensor result higher than the Hyper Level)
      11. k. Check bits 20-21 (Sensor Rate of Decrease exceeded and Sensor Rate of Increase exceeded).
      12. l. Check bits 22-23 (Sensor result lower than the device can process and Sensor result higher than the device can process).
    | +| Pass/Fail criteria | In Step 7: | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • If Low Battery Detection support bit is set to 1 (6.j), Device Battery Low bit (1) may be set to 1, else it is set to 0.
    • • If Sensor Type Error Detection support bit is set to 1 (6.k), Sensor Type Incorrect for Device bit (2) may be set to 1, else it is set to 0.
    • • If Sensor Malfunction Detection support bit is set to 1 (6.g), Sensor Malfunction bit (3) may be set to 1, else it is set to 0.
    • • If Device Specific Alert support bit is set to 1 (6.f), Device Specific Alert bit (4) may be set to 1, else it is set to 0.
    • • If General Device Fault support bit is set to 1 (6.l), General Device Fault has occurred in the sensor bit (5) may be set to 1, else it is set to 0.
    • • If Calibration support bit is set to 1 (6.a), one of bits 9-11 (Calibration not allowed, calibration recommended, and calibration required) may be set to 1, else they are set to 0.
    • • If Sensor Temperature High-Low Detection support bit is set to 1 (6.h), one of bits 12-13 (Sensor Temperature too high for valid test/result at time of measurement, Sensor Temperature too low for valid test/result at time of measurement) may be set to 1, else they are set to 0.
    • • If Patient High/Low Alerts support bit is set to 1 (6.b), one of bits 16-17 (Sensor result lower than the Patient Low level and Sensor result higher than the Patient High Level) may be set to 1, else they are set to 0.
    • • If Hypo Alerts support bit is set to 1 (6.c), Sensor result lower than the Hypo Level bit (18) may be set to 1, else it is set to 0.
    • • If Hyper Alerts support bit is set to 1 (6.d), Sensor result higher than the Hyper Level bit (20) may be set to 1, else it is set to 0.
    • • If Rate of Increase/Decrease Alerts support bit is set to 1 (6.e), one of bits 20-21 (Sensor Rate of Decrease exceeded and Sensor Rate of Increase exceeded) may be set to 1, else they are set to 0.
    • • If Sensor Result High-Low Detection support bit is set to 1 (6.i), one of bits 22-23 (Sensor result lower than the device can process and Sensor result higher than the device can process) may be set to 1, else they are set to 0.
    | +| Notes
    (to assist manual testing)     |

    To read CGM Feature characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2AA8. PHG will then receive a Read Response. Check ATT packet value in the received response:

    • • CGM Feature field will be present (3 octets), and it indicates features support and optional fields present. Note that bytes will be transmitted using little endian order (i.e. the least significant octet first).
      • 1. Check support bits as stated above.
      • 2. Check that bits 17-23 are 0 (reserved for future use).
    • • CGM Type field (4 bits) will be present.
    • • CGM Sample Location field (4 bits) will be present.
    • • E2E-CRC field (2 octets) will be present.

    To read the CGM Status characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2AA9. PHG will then receive a Read Response. Check ATT packet value in the received response. Fields will appear in the following order:

    • • Time Offset field (2 octets) will be present.
    • • CGM Status field (3 octets) will be present. Check that:
      • 1. Check bits as stated in step 7.
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-013 | | | | +| TP label | Whitepaper. CGM Feature. Type and Sample Location | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Glucose Numeric 2; M | Glucose Numeric 3; M | | +| Test purpose | Check that:
    CGM Type and CGM Sample Location fields of the CGM Feature characteristic are present in CGM Feature characteristic and set to a correct value. | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state).
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG reads the CGM Feature characteristic.
    5. 5. In the CGM Feature characteristic:
      • • Check value of CGM Type field (4bit).
      • • Check value of CGM Sample Location field (4bit).
      • • Test Operator checks that read values are correct.
    | | | | +| Pass/Fail criteria | In Step 5:
    • • CGM Type field value is one of {0x1, 0x2, 0x3, 0x4, 0x5, 0x6, 0x7, 0x8, 0x9, 0xA}.
    • • CGM Sample Location field value is one of {0x1, 0x2, 0x3, 0x4, 0x5, 0xF}.
    • • Values are correct
    | | | | +| Notes
    (to assist manual testing)     | To read CGM Feature characteristic, PHG shall perform a "Read Characteristic Value" GATT sub-procedure on characteristic with UUID 0x2AA8. PHG will then receive a Read Response. Check ATT packet value in the received response:
    • • CGM Feature field will be present (3 octets), and it indicates features support and optional fields present.
    • • CGM Type field (4 bits) will be present. Check that:
      1. 1. Value is one of the values stated above
      2. 2. Value is correct.
    • • CGM Sample Location field (4 bits) will be present. Check that:
      1. 1. Value is one of the values stated above
      2. 2. Value is correct.
    • • E2E-CRC field (2 octets) will be present.
    | | | | + +| | | +|-----------------|--------------------------------------------------------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-014 | +| TP label | Whitepaper. RACP. CGM Measurement, CGM Glucose Concentration value | + +| | | | | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|----------------------| +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 1; C | Glucose Numeric 6; M | Glucose Numeric 8; M | +| Test purpose |

    Check that:

    CGM Glucose Concentration field in CGM Measurement characteristic represents the measurement value acquired by BLE PHD and temporarily stored using RACP characteristic.

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test and acquire at least a CGM Measurement. The measurements shall be temporarily stored for later transmission.
    2. 2. Configure the PHD under test as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report all stored records by performing a writing operation in the Record Access Control Point (RACP) characteristic.
    6. 6. The PHD under test sends at least a CGM Measurement notification to the simulated PHG.
    7. 7. Check measurement(s) sent by the PHD under test:
      • • Check that blood glucose concentration value reported in CGM Glucose Concentration field is coherent: 0 \text{ (mg/dL)} \leq \text{value} \leq 2700 \text{ (mg/dL)}.
      • • Test Operator checks that blood glucose concentration value reported in CGM Glucose Concentration field is correct.
    | | | | +| Pass/Fail criteria | In Step 7, value of CGM Glucose Concentration field is within the ranges specified in Test Procedure and the values are correct. | | | | +| Notes
    (to assist manual testing)     |

    To receive temporarily stored CGM Measurements from the PHD under test, simulated PHG shall enable notifications on the CGM Measurement characteristic and indications on the Record Access Control Point (RACP) characteristic.

    In order to enable indications/notifications, simulated PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications/notifications.

    Once CGM Measurement characteristic has been enabled for notifications and Record Access Control Point characteristic has been enabled for indications, simulated PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value to the RACP characteristic.

    Once the PHG has performed such operation, a notification will arrive for each stored CGM Measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the CGM Measurement notifications arrive, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present. Check that:
    | | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 1. Value contained is between 0 (0x0000) and 100 (0x0A8C). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
    2. 2. Check that received value match that actually transmitted.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      1. 1. Warning-Octet (if present, 1 octet)
      2. 2. Cal/Temp-Octet (if present, 1 octet)
      3. 3. Status-Octet (if present, 1 octet)
    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-015 | | | | +| TP label | Whitepaper. RACP. CGM Measurement, CGM Glucose Concentration value below device capabilities | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 2; M | Glucose Numeric 9; M | | +| Test purpose | Check that:
    If a temporarily stored CGM Measurement is below device capabilities, value of the CGM Glucose Concentration field shall be -INFINITY. | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test and acquire at least a CGM Measurement with a value below device capabilities. The measurements shall be temporarily stored for later transmission.
    2. 2. Configure the PHD under test as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report all stored records by performing a writing operation in the Record Access Control Point (RACP) characteristic.
    6. 6. The PHD under test sends at least a CGM Measurement notification to the simulated PHG.
    7. 7. Check the measurements sent by the PHD under test
      • • Check that blood glucose concentration value reported in CGM Glucose Concentration field is -INFINITY (0x0802)
      • • Test Operator checks that blood glucose concentration value in CGM Glucose Concentration field is -INFINITY (0x0802)
    | | | | +| Pass/Fail criteria | In Step 7, value of CGM Glucose Concentration field is below device capabilities and it is represented as -INFINITY (0x0802). | | | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notes
    (to assist manual testing)     |

    To receive temporarily stored CGM Measurements from the PHD under test, simulated PHG shall enable notifications on the CGM Measurement characteristic and indications on the Record Access Control Point (RACP) characteristic.

    In order to enable indications/notifications, simulated PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications/notifications.

    Once CGM Measurement characteristic has been enabled for notifications and Record Access Control Point characteristic has been enabled for indications, simulated PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value to the RACP characteristic.

    Once the PHG has performed such operation, a notification will arrive for each stored CGM Measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the CGM Measurement notifications arrive, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present. Check that:
      1. 1. Value contained is (0x0802). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Check that received value match that actually transmitted.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      1. 1. Warning-Octet (if present, 1 octet)
      2. 2. Cal/Temp-Octet (if present, 1 octet)
      3. 3. Status-Octet (if present, 1 octet). If present, bit 6 of this octet (22 of total) shall be set to 1.
    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-016 | | | +| TP label | Whitepaper. RACP. CGM Measurement, CGM Glucose Concentration value above device capabilities | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 2; M | Glucose Numeric 9; M | +| Test purpose | Check that:
    If a temporarily stored CGM Measurement is above device capabilities, value of the CGM Glucose Concentration field shall be +INFINITY. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Turn on the PHD under test and acquire at least a CGM Measurement with a value above device capabilities. The measurements shall be temporarily stored for later transmission.
    2. 2. Configure the PHD under test as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report all stored records by performing a writing operation in the Record Access Control Point (RACP) characteristic.
    6. 6. The PHD under test sends at least a CGM Measurement notification to the simulated PHG.
    7. 7. Check the measurements sent by the PHD under test
      • • Check that blood glucose concentration value reported in CGM Glucose Concentration field is +INFINITY (0x07FE)
      • • Test Operator checks that blood glucose concentration value in CGM Glucose Concentration field is +INFINITY (0x07FE)
    | +| Pass/Fail criteria | In Step 7, value of CGM Glucose Concentration field is above device capabilities and it is represented as +INFINITY (0x07FE). | +| Notes
    (to assist manual testing)     |

    To receive temporarily stored CGM Measurements from the PHD under test, simulated PHG shall enable notifications on the CGM Measurement characteristic and indications on the Record Access Control Point (RACP) characteristic.

    In order to enable indications/notifications, simulated PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications/notifications.

    Once CGM Measurement characteristic has been enabled for notifications and Record Access Control Point characteristic has been enabled for indications, simulated PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value to the RACP characteristic.

    Once the PHG has performed such operation, a notification will arrive for each stored CGM Measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the CGM Measurement notifications arrive, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present. Check that:
      1. 1. Value contained is (0x07FE). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      2. 2. Check that received value match that actually transmitted.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      1. 1. Warning-Octet (if present, 1 octet)
      2. 2. Cal/Temp-Octet (if present, 1 octet)
      3. 3. Status-Octet (if present, 1 octet). If present, bit 7 of this octet (23 of total) shall be set to 1.
    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    | + +| | | +|--|----------------------------------------------------------------------------------------| +| |
    • E2E-CRC field (if present, 2 octets)
    | +|--|----------------------------------------------------------------------------------------| + +| | | | | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-017 | | | | +| TP label | Whitepaper. RACP. CGM Measurement, CGM Glucose Concentration special values | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 2; M | Glucose Numeric 10; M | | +| Test purpose |

    Check that:

    Device reports a NaN or NRes value in the CGM Glucose Concentration field of the CGM Measurement characteristic to signal some problem during measurement in temporarily stored measurements.

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. Turn on the PHD under test and acquire at least a CGM Measurement with a special value simulating a problem during measurement. The measurements shall be temporarily stored for later transmission.
    2. Configure the PHD under test as a discoverable Bluetooth device (Advertising state).
    3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. The PHG requests the PHD under test to report all stored records by performing a writing operation in the Record Access Control Point (RACP) characteristic.
    6. The PHD under test sends at least a CGM Measurement notification to the simulated PHG.
    7. Check measurements sent by the PHD under test
      • Check that blood glucose concentration value reported in CGM Glucose Concentration field is set to NaN (0x0FF) or NRes (0x0800).
      • Test Operator checks that blood glucose concentration value reported in CGM Glucose Concentration field is one of the mentioned above due to a measurement problem.
    | | | | +| Pass/Fail criteria | In Step 7, value of CGM Glucose Concentration field is set to NaN (0x0FF) or NRes (0x0800) due to a measurement error. | | | | +| Notes
    (to assist manual testing)     |

    To receive temporarily stored CGM Measurements from the PHD under test, simulated PHG shall enable notifications on the CGM Measurement characteristic and indications on the Record Access Control Point (RACP) characteristic.

    In order to enable indications/notifications, simulated PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications/notifications.

    Once CGM Measurement characteristic has been enabled for notifications and Record Access Control Point characteristic has been enabled for indications, simulated PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value to the RACP characteristic.

    Once the PHG has performed such operation, a notification will arrive for each stored CGM Measurement. Finally, an indication from the RACP characteristic will also arrive.

    | | | | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    When the CGM Measurement notifications arrive, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present. Check that:
      • 1. Value contained is (0x0OFF) or (0x0800). Note that bytes will be transmitted using little endian order (i.e., the least significant octet first).
      • 2. Check that received value match that actually transmitted.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      • 1. Warning-Octet (if present, 1 octet)
      • 2. Cal/Temp-Octet (if present, 1 octet)
      • 3. Status-Octet (if present, 1 octet)
    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-018 | | | | +| TP label | Whitepaper. RACP. CGM Measurement, Time Offset value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | BaseOffset 3; M | Glucose Numeric 7; M | | +| Test purpose |

    Check that:

    Time offset field of the temporarily stored CGM Measurements specifies the relative time difference of the single CGM value to the session start time in minutes.

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test and acquire at least a CGM Measurement. The measurements shall be temporarily stored for later transmission.
    2. 2. Configure the PHD under test as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report all stored records by performing a writing operation in the Record Access Control Point (RACP) characteristic.
    6. 6. The PHD under test sends at least a CGM Measurement notification to the simulated PHG.
    7. 7. Check the measurements sent by the PHD under test
      • • Check value reported in Time Offset field (0x0000-0xFFFF) (uint16).
    | | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Test Operator checks that time offset value in minutes specifies the relative time difference of the single CGM value to the session start time in minutes.
    | +| Pass/Fail criteria | In Step 7, value of Time Offset field specifies the relative time difference of the single CGM value to the session start time as an uint16 (0x0000-0xFFFF) in minutes. | +| Notes
    (to assist manual testing)     |

    To receive temporarily stored CGM Measurements from the PHD under test, simulated PHG shall enable notifications on the CGM Measurement characteristic and indications on the Record Access Control Point (RACP) characteristic.

    In order to enable indications/notifications, simulated PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications/notifications.

    Once CGM Measurement characteristic has been enabled for notifications and Record Access Control Point characteristic has been enabled for indications, simulated PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value to the RACP characteristic.

    Once the PHG has performed such operation, a notification will arrive for each stored CGM Measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the CGM Measurement notifications arrive, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • A Flags field (1 octet) will be present to indicate which optional fields are present. Its content is not relevant in this test case.
    • Then, the CGM Glucose Concentration field (2 octets) will be present.
    • Time Offset field (2 octets). Check that:
      1. The received value match that actually transmitted.
    • Sensor Status Annunciation field (if present, up to 3 octets)
      1. Warning-Octet (if present, 1 octet)
      2. Cal/Temp-Octet (if present, 1 octet)
      3. Status-Octet (if present, 1 octet)
    • CGM Trend Information field (if present, 2 octets)
    • CGM Quality field (if present, 2 octets)
    • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-019 | | | +| TP label | Whitepaper. RACP. CGM Measurement, Sensor Status Annunciation value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 5; M | | +| Test purpose |

    Check that:

    If Sensor Status Annunciation field is included in temporarily stored CGM Measurements, its length and value are correct.

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | C_AG_BLE_043 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. Turn on the PHD under test and acquire at least a CGM Measurement. The measurements shall be temporarily stored for later transmission.
    2. 2. Configure the PHD under test as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report all stored records by performing a writing operation in the Record Access Control Point (RACP) characteristic.
    6. 6. The PHD under test sends at least a CGM Measurement notification to the simulated PHG.
    7. 7. Check measurements sent by the PHD under test
      1. a. IF C_AG_BLE_043 = TRUE (CGM PHD reports Sensor Status Annunciation) THEN
        • • One of more of flags 5 (Sensor Status Annunciation field, Warning-Octet present), 6 (Sensor Status Annunciation field, Cal/Temp-Octet present) or 7 (Sensor Status Annunciation field, Status-Octet present) are set to 1.
        • • Check that:
          • ▪ If flag 5 is set to 1, then Sensor Status Annunciation Warning-Octet field is present (bits 0 to 7) and at least one bit is set to 1. Bits 6 and 7 shall be set to 0 (reserved for future use). Rest of bits may be set to 0 or 1.
          • ▪ If flag 6 is set to 1, then Sensor Status Annunciation Cal/Temp-Octet field is present (bits 8 to 15) and at least one bit is set to 1. Bits 14 and 15 shall be set to 0 (reserved for future use). Rest of bits may be set to 0 or 1.
          • ▪ If flag 7 is set to 1, then Sensor Status Annunciation Status-Octet field is present (bits 16 to 23) and at least one bit is set to 1. Bits may be set to 0 or 1.
        • • Test Operator checks that the Sensor Status Annunciation field value and size reported in the CGM Measurement are correct
      2. b. IF C_AG_BLE_043 = FALSE (CGM PHD does not report Sensor Status Annunciation) THEN
        • • Check that flags 5, 6 and 7 are set to 0.
        • • Check that Sensor Status Annunciation octets are not reported
    | +| Pass/Fail criteria |
    • • In Step 5.a, value and size of the Sensor Status Annunciation field are as specified according to value of Flags field.
    • • In Step 5.b, flags 5, 6 and 7 are set to 0 and Sensor Status Annunciation field is not present.
    | +| Notes
    (to assist manual testing)     |

    To receive temporarily stored CGM Measurements from the PHD under test, simulated PHG shall enable notifications on the CGM Measurement characteristic and indications on the Record Access Control Point (RACP) characteristic.

    In order to enable indications/notifications, simulated PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications/notifications.

    Once CGM Measurement characteristic has been enabled for notifications and Record Access Control Point characteristic has been enabled for indications, simulated PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value to the RACP characteristic.

    Once the PHG has performed such operation, a notification will arrive for each stored CGM Measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the CGM Measurement notifications arrive, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check value of flags 5, 6 and 7.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets). Check that (note that bytes will be transmitted using little endian order (i.e., the least significant octet first):
      • 1. If flag 5 is set to 1, then Warning-Octet is present. If present, bits 0-5 may be set to 0 or 1 and bits 6-7 shall be set to 0. If present, at least one bit shall be set to 1.
      • 2. If flag 6 is set to 1, then Cal/Temp-Octet is present. If present, bits 8-13 may be set to 0 or 1 and bits 14-15 shall be set to 0. If present, at least one bit shall be set to 1.
      • 3. If flag 7 is set to 1, then Status-Octet is present. If present, bits 16-23 may be set to 0 or 1. If present, at least one bit shall be set to 1.
    • • CGM Trend Information field (if present, 2 octets)
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-020 | | | +| TP label | Whitepaper. RACP. CGM Measurement, CGM Trend Information | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 7; M | | +| Test purpose | Check that:
    If CGM Trend Information field is included in temporarily stored CGM Measurements, its value is correct. | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | | | +| Other PICS | C_AG_BLE_044 | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test and acquire at least a CGM Measurement. The measurements shall be temporarily stored for later transmission.
    2. 2. Configure the PHD under test as a discoverable Bluetooth device (Advertising state).
    3. 3. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    4. 4. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    5. 5. The PHG requests the PHD under test to report all stored records by performing a writing operation in the Record Access Control Point (RACP) characteristic.
    6. 6. The PHD under test sends at least a CGM Measurement notification to the simulated PHG.
    7. 7. Check the measurements sent by the PHD under test
      1. a. IF C_AG_BLE_044 = TRUE (CGM PHD reports Glucose Trend Information) THEN
        • • Flag 0 (CGM Trend Information present) is set to 1.
    | | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • CGM Trend Information field is present as an SFLOAT value in (mg/dL)/min units.
    • • Test Operator checks that the CGM Trend Information field value reported in the CGM Measurement is correct

    b. IF C_AG_BLE_044 = FALSE (CGM PHD does not report Glucose Trend Information) THEN

    • • Check that flag 0 is set to 0.
    • • Check that CGM Trend Information field is not reported
    | +| Pass/Fail criteria |
    • • In Step 7.a, flag 0 is set to 1, CGM Trend Information field is reported and its value is correct.
    • • In Step 7.b, flags 0 is set to 0 and the CGM Trend Information field is not reported.
    | +| Notes
    (to assist manual testing)     |

    To receive temporarily stored CGM Measurements from the PHD under test, simulated PHG shall enable notifications on the CGM Measurement characteristic and indications on the Record Access Control Point (RACP) characteristic.

    In order to enable indications/notifications, simulated PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on the Client Characteristic Configuration Descriptor of both characteristics to write the proper value for indications/notifications.

    Once CGM Measurement characteristic has been enabled for notifications and Record Access Control Point characteristic has been enabled for indications, simulated PHG shall perform a "Report Stored Records" operation with an "All Records" operator on the RACP characteristic to receive all stored measurements. To perform this operation, PHG shall perform a "Write Characteristic Value" GATT sub-procedure to write the appropriate value to the RACP characteristic.

    Once the PHG has performed such operation, a notification will arrive for each stored CGM Measurement. Finally, an indication from the RACP characteristic will also arrive.

    When the CGM Measurement notifications arrive, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • A Size field (1 octet) will be present, representing the size of the CGM Measurement record that follows (including the Size field).
    • • A Flags field (1 octet) will be present to indicate which optional fields are present. Check value of flag 0.
    • • Then, the CGM Glucose Concentration field (2 octets) will be present.
    • • Time Offset field (2 octets).
    • • Sensor Status Annunciation field (if present, up to 3 octets)
      1. 1. Warning-Octet (if present, 1 octet)
      2. 2. Cal/Temp-Octet (if present, 1 octet)
      3. 3. Status-Octet (if present, 1 octet)
    • • CGM Trend Information field (if present, 2 octets). Check that:
      1. 1. If flag 0 is set to 1, this field is present and it is set to the reported value (SFLOAT, (mg/dL)/min).
    • • CGM Quality field (if present, 2 octets)
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|-----------------|-----------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-021 | | | +| TP label | Whitepaper. CGM Specific Ops Control Point. Communication Interval Response value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GSI Numeric 8; M | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    Communication Interval Response Operand represents the time interval (in minutes) after which the CGM Measurement characteristic is sent to the client.

    | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 | +| Other PICS | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state). The PHD has a valid Communication Interval value already set.
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG makes a request to the CGM Specific Ops control Point to get the CGM Sensor Communication Interval. To do so, it performs a CGM Communication Interval procedure using Op Code "Get CGM Communication Interval" (0x02) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code field).
    5. 5. The PHD is expected to respond with an indication including a "Communication Interval Response" Op Code (0x03) and a uint8 containing the communication interval in minutes.
    6. 6. Check indication sent by PHD under test:
      1. a. Op Code is 0x03 ("Communication Interval Response")
      2. b. Operand format is uint8
      3. c. Test Operator checks that the value of the operand matches the Communication Interval of the CGM Sensor in minutes.
    | +| Pass/Fail criteria | Op Code and Operand in the response match the requirements in Step 6. | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the CGM Specific Ops Control Point characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the CGM Specific Ops Control Point has been enabled for indications, in order to obtain the Communication Interval Response value, PHG will use the "Write Characteristic Value" GATT sub-procedure on the CGM Specific Ops Control Point characteristic to write the Op Code "0x02" (Get CGM Communication Interval). The PHD is then expected to send an indication to the PHG as a response.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • Op Code field (1 octet) will be present. Check that:
      1. 1. Field value is 0x03 (CGM Communication Interval response)
    • • Operand field (1 octet) will be present:
      1. 1. Check field value (uint8 containing the Communication Interval in minutes).
      2. 2. Check that the Communication Interval value is correct.
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | +|-----------------|-------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-022 | | +| TP label | Whitepaper. CGM Specific Ops Control Point. Calibration Value Response value. | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | + +| | Testable items | SensCal Numeric 3; M | SensCal Numeric 11; M | SensCal Numeric 12; M | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-----------------------|-----------------------| +| Test purpose |

    Check that:

    The Glucose Concentration of Calibration field of a Calibration Data Record represents the CGM Sensor blood glucose concentration calibration value in mg/dL.

    [AND]

    The Calibration Sample Location field of the Calibration Data Record represents the correct sample location.

    [AND]

    The Calibration Time field of the Calibration Data Record represents the time the calibration value was measured as a relative offset to the Session Start Time in minutes.

    | | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 AND C_AG_BLE_045 | | | | +| Other PICS | | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state). The PHD has a single Calibration Data Record stored with valid data.
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG makes a request to the CGM Specific Ops control Point to get the latest stored Calibration Data Record. To do so, it performs a Glucose Calibration procedure using Op Code "Get Glucose Calibration value" (0x05) with Operand "0xFFFF" (by performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code and Calibration Data Record Number fields respectively).
    5. 5. The PHD is expected to respond with an indication including a "Calibration Value Response" Op Code (0x06) and a Calibration Data Record structure containing the requested calibration information.
    6. 6. Check the indication sent by the PHD under test:
      1. a. Op Code is 0x06 ("Calibration Value Response")
      2. b. Operand format matches the Calibration Data Record structure.
      3. c. Check Glucose Concentration of Calibration field value (SFLOAT, mg/dL).
      4. d. Test Operator checks that the value of the Glucose Concentration of Calibration field of the Calibration Data Record represents the actual blood glucose concentration calibration value in mg/dL.
      5. e. Check that the Calibration Sample Location field has a valid value (4bits). Valid values are {0x1, 0x2, 0x3, 0x4, 0x5, 0xA}.
      6. f. Test Operator checks that the value of the Calibration Sample Location represents the correct sample location.
      7. g. Check Calibration Time field value (uint16, min).
      8. h. Test Operator checks that the value of the Calibration Time field of the Calibration Data Record matches the actual time when the calibration value was measured as a relative offset to the Session Start Time in minutes.
    | | | | +| Pass/Fail criteria | Op Code and Operand in the response match the requirements in Step 6. | | | | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the CGM Specific Ops Control Point characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the CGM Specific Ops Control Point has been enabled for indications, in order to obtain the latest Calibration Data Record, PHG will use the "Write Characteristic Value"

    | | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    GATT sub-procedure on the CGM Specific Ops Control Point characteristic to write the Op Code "0x05" (Get Glucose Calibration value) and the Operand "0xFFFF". The PHD is then expected to send an indication to the PHG as a response.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • Op Code field (1 octet) will be present. Check that:
      1. 1. Field value is 0x06 (Calibration Value Response)
    • • Calibration Value-Glucose concentration of Calibration field (2 octets) will be present:
      1. 1. Check field value (SFLOAT with a valid blood glucose concentration value in mg/dL)
      2. 2. Check that the value is correct
    • • Calibration Value – Calibration Time field (2 octets) will be present:
      1. 1. Check field value (uint16, min)
      2. 2. Check that the value is correct
    • • Calibration Value – Calibration Type field (4 bits) will be present.
    • • Calibration Value – Calibration Sample Location (4 bits) will be present
      1. 1. Check that the field has a correct value according to 6.e.
      2. 2. Check that the value is correct
    • • Calibration Value - Next Calibration Time field (2 octets) will be present.
    • • Calibration Value – Calibration Data Record Number field (2 octets) will be present.
    • • Calibration Value – Calibration Status field (1 octet) will be present.
    • • E2E-CRC field (if present, 2 octets)
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-023 | | | +| TP label | Whitepaper. CGM Specific Ops Control Point. Patient High Alert Level Response value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 10; M | | +| Test purpose | Check that:
    Patient High Alert Level Response Operand represents the correct alert level in mg/dL | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 AND C_AG_BLE_046 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state). PHD has a valid Patient High Alert Level value already set.
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG makes a request to the CGM Specific Ops control Point to get the Patient High Alert Level value. To do so, it performs a Patient High Alert Level procedure using Op Code "Get Patient High Alert Level" (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    | | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 5. The PHD is expected to respond with an indication including a "Patient High Alert Level Response" (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    2. 6. Check the indication sent by the PHD under test:
      1. a. Op Code is 0x09 ("Patient High Alert Level Response")
      2. b. Operand format is SFLOAT
      3. c. Test Operator checks that the value of the operand matches the Patient High Alert Level value of the CGM Sensor in mg/dL.
    | +| Pass/Fail criteria | Op Code and Operand in the response match the requirements in Step 6. | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the CGM Specific Ops Control Point characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the CGM Specific Ops Control Point has been enabled for indications, in order to obtain the Patient High Alert Level value, PHG will use the "Write Characteristic Value" GATT sub-procedure on the CGM Specific Ops Control Point characteristic to write the Op Code "0x08" (Get Patient High Alert Level). The PHD is then expected to send an indication to the PHG as a response.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • Op Code field (1 octet) will be present. Check that:
      1. 1. Field value is 0x09 (Patient High Alert Level Response)
    • • Operand field (1 octet) will be present:
      1. 1. Check field value (SFLOAT containing the Patient High Alert Level in mg/dL).
      2. 2. Check that the Patient High Alert Level value is correct.
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-024 | | | +| TP label | Whitepaper. CGM Specific Ops Control Point. Patient Low Alert Level Response value. | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 10; M | | +| Test purpose | Check that:
    Patient Low Alert Level Response Operand represents the correct alert level in mg/dL | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 AND C_AG_BLE_046 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state). The PHD has a valid Patient High Alert Level value already set.
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG makes a request to the CGM Specific Ops control Point to get the Patient Low Alert Level value. To do so, it performs a Patient Low Alert Level procedure using Op Code "Get Patient Low Alert Level" (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 5. The PHD is expected to respond with an indication including a "Patient Low Alert Level Response" (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    2. 6. Check the indication sent by the PHD under test:
      1. a. Op Code is 0x0C ("Patient Low Alert Level Response")
      2. b. Operand format is SFLOAT
      3. c. Test Operator checks that the value of the operand matches the Patient Low Alert Level value of the CGM Sensor in mg/dL.
    | +| Pass/Fail criteria | Op Code and Operand in the response match the requirements in Step 6. | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the CGM Specific Ops Control Point characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the CGM Specific Ops Control Point has been enabled for indications, in order to obtain the Patient Low Alert Level Response value, PHG will use the "Write Characteristic Value" GATT sub-procedure on the CGM Specific Ops Control Point characteristic to write the Op Code "0x0B" (Get Patient Low Alert Level). The PHD is then expected to send an indication to the PHG as a response.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • Op Code field (1 octet) will be present. Check that:
      1. 1. Field value is 0x0C (Patient Low Alert Level Response)
    • • Operand field (1 octet) will be present:
      1. 1. Check field value (SFLOAT containing the Patient Low Alert Level in mg/dL).
      2. 2. Check that the Patient Low Alert Level value is correct.
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-025 | | | +| TP label | Whitepaper. CGM Specific Ops Control Point. Hypo Alert Level Response value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 10; M | | +| Test purpose | Check that:
    Hypo Alert Level Response Operand represents the correct alert level in mg/dL | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 AND C_AG_BLE_047 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state). The PHD has a valid Hypo Alert Level value already set.
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG makes a request to the CGM Specific Ops control Point to get the Hypo Alert Level value. To do so, it performs a Hypo Alert procedure using Op Code "Get Hypo Alert Level" (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 5. The PHD is expected to respond with an indication including a "Hypo Alert Level Response" (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    2. 6. Check the indication sent by the PHD under test:
      1. a. Op Code is 0x0F ("Hypo Alert Level Response")
      2. b. Operand format is SFLOAT
      3. c. Test Operator checks that the value of the operand matches the Hypo Alert Level value of the CGM Sensor in mg/dL.
    | +| Pass/Fail criteria | Op Code and Operand in the response match the requirements in Step 6. | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the CGM Specific Ops Control Point characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the CGM Specific Ops Control Point has been enabled for indications, in order to obtain the Hypo Alert Level Response value, PHG will use the "Write Characteristic Value" GATT sub-procedure on the CGM Specific Ops Control Point characteristic to write the Op Code "0x0E" (Get Hypo Alert Level). The PHD is then expected to send an indication to the PHG as a response.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • Op Code field (1 octet) will be present. Check that:
      1. 1. Field value is 0x0F (Hypo Alert Level Response)
    • • Operand field (1 octet) will be present:
      1. 1. Check field value (SFLOAT containing the Hypo Alert Level in mg/dL).
      2. 2. Check that the Hypo Alert Level value is correct.
    • • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-026 | | | +| TP label | Whitepaper. CGM Specific Ops Control Point. Hyper Alert Level Response value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 10; M | | +| Test purpose | Check that:
    Hyper Alert Level Response Operand represents the correct alert level in mg/dL | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 AND C_AG_BLE_048 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. 1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state). The PHD has a valid Hyper Alert Level value already set.
    2. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    4. 4. The simulated PHG makes a request to the CGM Specific Ops control Point to get the Hyper Alert Level value. To do so, it performs a Hyper Alert procedure using Op Code "Get Hyper Alert Level" (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    5. The PHD is expected to respond with an indication including a "Hyper Alert Level Response" (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.

    6. Check the indication sent by the PHD under test:

    1. Op Code is 0x12 ("Hyper Alert Level Response")
    2. Operand format is SFLOAT
    3. Test Operator checks that the value of the operand matches the Hyper Alert Level value of the CGM Sensor in mg/dL.
    | +| Pass/Fail criteria | Op Code and Operand in the response match the requirements in Step 6. | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the CGM Specific Ops Control Point characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the CGM Specific Ops Control Point has been enabled for indications, in order to obtain the Hyper Alert Level Response value, PHG will use the "Write Characteristic Value" GATT sub-procedure on the CGM Specific Ops Control Point characteristic to write the Op Code "0x11" (Get Hyper Alert Level). The PHD is then expected to send an indication to the PHG as a response.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • Op Code field (1 octet) will be present. Check that:
      1. Field value is 0x12 (Hyper Alert Level Response)
    • Operand field (1 octet) will be present:
      1. Check field value (SFLOAT containing the Hyper Alert Level in mg/dL).
      2. Check that the Hyper Alert Level value is correct.
    • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-027 | | | +| TP label | Whitepaper. CGM Specific Ops Control Point. Rate of Decrease Alert Level Response value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 10; M | | +| Test purpose |

    Check that:

    Rate of Decrease Alert Level Response Operand represents the correct alert level in mg/dL

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 AND C_AG_BLE_049 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state). The PHD has a valid Rate of Decrease Alert Level value already set.
    2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    | | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. The simulated PHG makes a request to the CGM Specific Ops control Point to get the Rate of Decrease Alert Level value. To do so, it performs a Rate of Decrease Alert Level procedure using Op Code "Get Rate of Decrease Alert Level" (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).

    5. The PHD is expected to respond with an indication including a "Rate of Decrease Alert Level Response" (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.

    6. Check the indication sent by the PHD under test:

    1. Op Code is 0x15 ("Rate of Decrease Alert Level Response")
    2. Operand format is SFLOAT
    3. Test Operator checks that the value of the operand matches the Rate of Decrease Alert Level value of the CGM Sensor in mg/dL/min.
    | +| Pass/Fail criteria | Op Code and Operand in the response match the requirements in Step 6. | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the CGM Specific Ops Control Point characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the CGM Specific Ops Control Point has been enabled for indications, in order to obtain the Decrease Alert Level Response value, PHG will use the "Write Characteristic Value" GATT sub-procedure on the CGM Specific Ops Control Point characteristic to write the Op Code "0x14" (Get Rate of Decrease Alert Level). The PHD is then expected to send an indication to the PHG as a response.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • Op Code field (1 octet) will be present. Check that:
      1. Field value is 0x15 (Rate of Decrease Alert Level Response)
    • Operand field (1 octet) will be present:
      1. Check field value (SFLOAT containing the Rate of Decrease Alert Level in mg/dL).
      2. Check that the Rate of Decrease Alert Level value is correct.
    • E2E-CRC field (if present, 2 octets)
    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHD/PHDTW/CGM/BV-028 | | | +| TP label | Whitepaper. CGM Specific Ops Control Point. Rate of Increase Alert Level Response value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 10; M | | +| Test purpose |

    Check that:

    Rate of Increase Alert Level Response Operand represents the correct alert level in mg/dL

    | | | +| Applicability | C_AG_BLE_000 AND C_AG_BLE_042 AND C_AG_BLE_049 | | | +| Other PICS | | | | +| Initial condition | The PHD under test and the simulated PHG are in Standby state. | | | +| Test procedure |
    1. Turn on the PHD under test, and configure it as a discoverable Bluetooth device (Advertising state). The PHD has a valid Rate of Increase Alert Level value already set.
    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The simulated PHG initiates a discovery process (Scanning state), it discovers the PHD under test and it starts a pairing process with the PHD under test (Initiating state).
    2. 3. The simulated PHG initiates a Bluetooth connection with the PHD under test (Connection state).
    3. 4. The simulated PHG makes a request to the CGM Specific Ops control Point to get the Rate of Increase Alert Level value. To do so, it performs a Rate of Increase Alert Level procedure using Op Code "Get Rate of Increase Alert Level" (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    4. 5. The PHD is expected to respond with an indication including a "Rate of Increase Alert Level Response" (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    5. 6. Check the indication sent by the PHD under test:
      1. a. Op Code is 0x18 ("Rate of Increase Alert Level Response")
      2. b. Operand format is SFLOAT
      3. c. Test Operator checks that the value of the operand matches the Rate of Increase Alert Level value of the CGM Sensor in mg/dL/min.
    | +| Pass/Fail criteria | Op Code and Operand in the response match the requirements in Step 6. | +| Notes
    (to assist manual testing)     |

    In order to enable indications on the CGM Specific Ops Control Point characteristic, PHG will use the "Write Characteristic Descriptor" GATT sub-procedure on its Client Characteristic Configuration Descriptor to write the proper value for indications.

    Once the CGM Specific Ops Control Point has been enabled for indications, in order to obtain the Increase Alert Level Response value, PHG will use the "Write Characteristic Value" GATT sub-procedure on the CGM Specific Ops Control Point characteristic to write the Op Code "0x17" (Get Rate of Increase Alert Level). The PHD is then expected to send an indication to the PHG as a response.

    When the indication arrives, check the value of received ATT packet (besides header and metadata). Fields and subfields will appear in the following order:

    • • Op Code field (1 octet) will be present. Check that:
      1. 1. Field value is 0x18 (Rate of Increase Alert Level Response)
    • • Operand field (1 octet) will be present:
      1. 1. Check field value (SFLOAT containing the Rate of Increase Alert Level in mg/dL).
      2. 2. Check that the Rate of Increase Alert Level value is correct.
    • • E2E-CRC field (if present, 2 octets)
    | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011) "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance Continua Design Guidelines (2012) "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance Continua Design Guidelines (2013) "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance Continua Design Guidelines (2015) "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance Continua Design Guidelines (2016) "Iris", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.13. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.11. + +- [b-TI] PHD Testable items. Test Tool v7.0.2.0 – Excel sheet v1.10. + + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.850.2-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.850.2-202008-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9ccab805d96944f16645ef07c4b210bf97a8b504 --- /dev/null +++ b/marked/H/T-REC-H.850.2-202008-I_PDF-E/raw.md @@ -0,0 +1,1223 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.850.2** + +(08/2020) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 10B: Transcoding for Bluetooth Low +Energy: Personal Health Gateway – Blood +pressure** + +Recommendation ITU-T H.850.2 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.850.2 + +### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10B: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Blood pressure + +## Summary + +Recommendation ITU-T H.850.2 provides a test suite structure (TSS) and the test purposes (TP) for the transcoding of blood pressure data by personal health gateways in the Personal Health Devices (PHD) interface of application-level data between the Bluetooth Low Energy Bluetooth Generic Attribute Profile (GATT) format and the IEEE 11073-20601 data format, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.850.2 is a transposition of clause 3.4 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.850.2 | 2017-04-29 | 16 | 11.1002/1000/13355 | +| 2.0 | ITU-T H.850.2 | 2020-08-13 | 16 | 11.1002/1000/14346 | + +## Keywords + +Bluetooth Low Energy (BLE), Bluetooth Generic Attribute Profile, blood pressure, Conformance testing, Continua Design Guidelines, data format transcoding, e-health, IEEE 11073-20601, ITU-T H.810, Personal Health Devices interface, personal area network, personal connected health devices, Personal Health Gateway, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|--------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 3 | +| 3.1 | Terms defined elsewhere ..... | 3 | +| 3.2 | Terms defined in this Recommendation ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Test suite structure..... | 6 | +| 7 | Electronic attachment ..... | 8 | +| Annex A | Test purposes ..... | 9 | +| A.1 | TP definition conventions..... | 9 | +| A.2 | Subgroup 2.4.3 – Whitepaper Blood pressure requirements (BP) ..... | 11 | +| | Bibliography..... | 61 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of clause 3.4 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2012-10-05 | Initial release for Test Tool DG2011 based on the requirements in [b-CDG 2011]. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. It uses "TSS&TP_DG2011_LP-PAN_PART_10_v1.0.doc" as a baseline and adds new features included in [b-CDG 2012] (BPM and HR profiles). | +| 1.2 | 2014-01-24 | Initial release for Test Tool DG2013. It uses "TSS&TP_DG2012_LP-PAN_PART_10_v1.1.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.3 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.2.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row has been added
    | +| 1.4 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015]:
    • • Adds WS/BCA BLE device specialization
    • • Adds SABTE IEEE device specialization
    | +| 1.5 | 2016-01-26 | First maintenance release for Test Tool DG2015. It uses "TSS&TP_DG2015_LP-PAN_PART_10_v1.4.doc" as a baseline and adds some updates according to the Maintenance 2015 activity. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]:
    • • Adds PLX BLE device specialization
    • • Adds PLX CGM device specialization
    | +| 1.7 | 2017-07-18 | Second Maintenance Release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.6.doc" as a baseline and corrects minor typos. | +| 1.8 | 2020-06-02 | Updates related to the value of the Reg-Cert-Data-List according to [b-CDG 2017]. | + +## Recommendation ITU-T H.850.2 + +### Conformance of ITU-T H.810 personal health devices: Personal Health Devices interface Part 10B: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Blood pressure + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 10B. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway. In addition to the main part, the document is subdivided into the following subparts: + - Part 10A: Whitepaper Thermometer requirements + - **Part 10B: Whitepaper Blood pressure requirements** + - Part 10C: Whitepaper Heart rate requirements + - Part 10D: Whitepaper Glucose meter requirements + - Part 10E: Whitepaper Weighing scales requirements + - Part 10F: Whitepaper Pulse oximeter requirements + - Part 10G: Whitepaper Continuous glucose monitoring requirements + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [Bluetooth PHDT v1.4] Bluetooth SIG (2013), *Personal Health Devices Transcoding White Paper, v1.4*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=294539](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=294539) +- [Bluetooth PHDT v1.5] Bluetooth SIG (2014), *Personal Health Devices Transcoding White Paper, v1.5*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=272346](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=272346) +- [Bluetooth PHDT v1.6] Bluetooth SIG (2015), *Personal Health Devices Transcoding White Paper, v1.6*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=310657](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=310657) +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization*. + NOTE – Shorthand to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + +- [IHE PCD TF 1] IHE PCD TF 1 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 1: Integration Profiles*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol1\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol1_FT_2012-08-16.pdf) +- [IHE PCD TF 2] IHE PCD TF 2 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 2: Transactions*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol2\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol2_FT_2012-08-16.pdf) +- [IHE PCD TF 3] IHE PCD TF 3 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 3: Semantic Content*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol3\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol3_FT_2012-08-16.pdf) + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|--------------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| LSB | Least Significant Bit | +| MDS | Medical Device System | +| MSB | Most Significant Bit | + +| | | +|-------|-------------------------------------------------------| +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCD | Patient Care Device | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| RACP | Record Access Control Point | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purposes | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +## 5 Conventions + +In this text, the uppercase letter L is used as the symbol for litre. + +Several of the test purposes in Annex A refer to "WAN PCD-01 messages"; these messages are specified in the patient care device (PCD) technical framework defined in [IHE PCD TF 1], [IHE PCD TF 2] and [IHE PCD TF 3]. Similarly, the "IEEE 11073 Objects and Attributes" are defined in [ISO/IEEE 11073-104xx]. + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +In this document, hexadecimal numbers are denoted either with the prefix "0x" or by "(hex)" after the number; "(dec)" after a number indicates it is expressed in decimal format. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of ITU-T H.810 is split into eight parts in the ITU-T H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure + +The test purposes (TP) for the Personal Health Devices interface have been divided into the groups and subgroups specified below. Annex A describes the TPs for subgroup 2.4.3 (shown in bold). + +– Group 1: Personal Health Device (PHD) + +- Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) +- Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) +- Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) +- Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - **Subgroup 2.4.3: Whitepaper blood pressure requirements (BPM)** + +- Subgroup 2.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 2.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +## 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth low energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies a test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 2.4.3 – Whitepaper Blood pressure requirements (BP) + +| | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-000 | | | +| TP label | Whitepaper. Blood Pressure MDS Object - System-Type Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BPM Specific MDS 1; M | | +| Test purpose | Check that:
    PHG does not include MDS Object – System-Type attribute in transcoder output. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 3. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    4. 4. Check in PHG transcoder output for the MDS object – System-Type attribute.
    | | | +| Pass/Fail criteria | In step 4, the MDS object – System-Type attribute is not present. | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    System-Type attribute is not present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_SYS_TYPE (2438)
    • Attribute-type: TYPE
    • Attribute-value: <NOT PRESENT>

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a System-Type attribute value (67974^MDC_ATTR_SYS_TYPE^MDC).

    | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-001 | | | +| TP label | Whitepaper. Blood Pressure MDS Object - Dev-Configuration-Id Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BPM Specific MDS 2; M | | +| Test purpose |

    Check that:

    PHG includes MDS Object – Dev-Configuration-Id attribute in transcoder output.

    [AND]

    Dev-Configuration-Id value is set to any value in range of 0x4000 to 0x7FFF (Extended Configuration)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    3. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.

    4. Check in PHG transcoder output for the MDS object – Dev-Configuration-Id attribute.

    | +| Pass/Fail criteria | In step 4, the MDS object – Dev-Configuration-Id attribute is present and its value is inside the range 0x4000 - 0x7FFF. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Dev-Configuration-Id attribute is present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_DEV_CONFIG_ID (2628)
    • Attribute-type: INT-U16
    • Attribute-value: Any value inside the range 16384 - 32767 (dec) or 0x4000 – 0x7FFF (hex)

    b) WAN PCD-01 message

    According to [b-ITU-T H.810 (2013)], the Dev-Configuration-Id shall not be transmitted in the PCD-01 message; therefore it is not possible to check this attribute.

    | + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-002 | | | +| TP label | Whitepaper. Blood Pressure MDS Object - System-Type-Spec-List Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | Common MDS 15; M | BPM Specific MDS 3; M | +| Test purpose |

    Check that:

    PHG includes MDS Object – System-Type-Spec-List attribute in transcoder output.

    [AND]

    System-Type-Spec-List is set to (MDC_DEV_SPEC_PROFILE_BP, Version 1)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    3. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.

    4. Check in PHG transcoder output for the MDS object – System-Type-Spec-List attribute.

    | | | +| Pass/Fail criteria | In step 4, the MDS object – System-Type-Spec-List attribute is present and its value is (MDC_DEV_SPEC_PROFILE_BP, Version 1). | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    System-Type-Spec-List attribute is present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_SYS_TYPE_SPEC_LIST (2650)
    • Attribute-type: SEQUENCE OF {{type (INT-U16), version (INT-U16)}}
    • Attribute-value:
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • type: MDC_DEV_SPEC_PROFILE_BP or 4103 (dec) or 10 07 (hex)
    • version: 1 (dec) or 00 01 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with System-Type-Spec-List attribute value (check OBX-5):

    OBX ? NM 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a  528391^MDC_DEV_SPEC_PROFILE_BP ^MDC     R
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-003 | | | | +| TP label | Whitepaper. Blood Pressure MDS Object - Reg-Cert-Data-List Attribute | | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | | +| | Testable items | Common MDS 14; M | Regulatory Conv 1; M | | +| Test purpose |

    Check that:

    PHG transcodes IEEE 11073-20601 Regulatory Certification Data List characteristic into MDS Object – Reg-Cert-Data-List attribute

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. The simulated PHD is configured with a Blood pressure profile (device specialization) supported by the PHG under test; it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. IEEE 11073-20601 Regulatory Certification Data List (0x2A2A)
        • Format: reg-cert-data-list (opaque structure)
        • Value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 07 02 02 00 02 80 00 (hex)
          • Element:
            • auth-body-and-struc-type:
              • auth-body: 02 (hex) auth-body-continua(2)
              • auth-body-struc-type: 01 (hex). continua-version-struct(1)
            • auth-body-data:
              • major-IG-version: 08 (hex)
              • minor-IG-version: 00 (hex)
              • certified-devices: 80 07 (hex). BLE Blood Pressure
          • Element:
            • auth-body-and-struc-type:
              • auth-body: 02 (hex). auth-body-continua(2)
              • auth-body-struc-type: 02 (hex). continua-reg-struct(2)
            • auth-body-data:
              • regulation-bit-field: 80 00 (hex). Unregulated device
    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD.
    4. When the pairing has been completed (Connection state), force the PHG under test to read the IEEE 11073-20601 Regulatory Certification Data List characteristic.
    5. The simulated PHD sends the measurement to the PHG under test.
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 6. Check in PHG transcoder output for the MDS object – Reg-Cert-Data-List attribute. | +| Pass/Fail criteria | In step 6, the MDS object – Reg-Cert-Data-List attribute is present and its value matches with the IEEE 11073-20601 Regulatory Certification Data List characteristic value. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Reg-Cert-Data-List attribute is present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_REG_CERT_DATA_LIST (2635)
    • Attribute-type: SEQUENCE OF {{auth-body-and-struc-type, auth-body-data}, {...}}
    • Attribute-value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 07 02 02 00 02 80 00 (hex) [Note that 0x00 0x02 is the number of elements in the sequence and 0x00 12 is the length of the sequence]
      • i. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex) auth-body-continua(2)
          • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
        • • auth-body-data:
          • - major-IG-version: 08 (hex)
          • - minor-IG-version: 00 (hex)
          • - certified-devices: 80 07 (hex). BLE Blood Pressure
      • ii. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex). auth-body-continua(2)
          • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
        • • auth-body-data:
          • - regulation-bit-field: 80 00 (hex). Unregulated device

    b) WAN PCD-01 message

    PCD-01 message includes five segments like these with Reg-Cert-Data-List attribute value (check OBX-5 in five segments):

    OBX[? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.a 2^auth-body-continua     R
    OBX[? ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 1.0.0.a.x 6.1     R
    OBX[? NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 1.0.0.a.y 32775     R
    OBX[? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.b 2^auth-body-continua     R
    OBX[? CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 1.0.0.b.z 1^unregulated-device(0)     R
    | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-004 | | | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Handle Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BP Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Systolic/Diastolic/Map Compound Numeric Object – Handle Attribute in transcoder output

    | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [OR]
    If PHG includes Systolic/Diastolic/Map Compound Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0 | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
        6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
          • • This field is not included
        7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
          • • This field is not included
        8. viii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        9. ix. Field: Pulse Rate
          • • This field is not included
        10. x. Field: User ID
          • • This field is not included
        11. xi. Field: Measurement Status
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object
    | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | – Handle attribute. | +| Pass/Fail criteria | In step 5, the Systolic/Diastolic/Map compound numeric object – Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Handle attribute value.

    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-005 | | | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Type Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BP Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Systolic/Diastolic/Map Compound Numeric Object – Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_SCADA, MDC_PRESS_BLD_NONINV}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included
    vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
    • • This field is not included
    vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
    • • This field is not included
    viii. Field: Time Stamp
    • • Format: Date and Time
    • • Value: Not relevant
    ix. Field: Pulse Rate
    • • This field is not included
    x. Field: User ID
    • • This field is not included
    xi. Field: Measurement Status
    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.

    5. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object – Type attribute.

    | +| Pass/Fail criteria | In step 5, the Systolic/Diastolic/Map compound numeric object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_PRESS_BLD_NONINV}. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_PRESS_BLD_NONINV or 18948 (dec) or 4A 04 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute (check OBX-3):

    OBX ? 150020^MDC_PRESS_BLD_NONINV^MDC 1.0.a X
    [current_date_time].

    | + +| | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-006 | | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Metric-Spec-Small Attribute | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | +| | Testable items | BP Numeric 3; M | +| Test purpose |

    Check that:

    PHG includes Systolic/Diastolic/Map Compound Numeric Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Metric-Spec-Small is set to {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
        6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
          • • This field is not included
        7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
          • • This field is not included
        8. viii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        9. ix. Field: Pulse Rate
          • • This field is not included
        10. x. Field: User ID
          • • This field is not included
        11. xi. Field: Measurement Status
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object, Metric-Spec-Small attribute.
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | In step 5, the Systolic/Diastolic/Map compound numeric object – Metric-Spec-Small attribute is present and its value is {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-007 | | | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Metric-Structure-Small Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BP Numeric 4; M | | +| Test purpose |

    Check that:

    PHG includes Systolic/Diastolic/Map Compound Numeric Object – Metric-Structure-Small attribute in transcoder output.

    [AND]

    Metric-Structure-Small is set to {0x03, 0x03} (ms-struct-compound-fix, 3).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: Not relevant

    v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)

    • • This field is not included

    vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)

    • • This field is not included

    vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)

    • • This field is not included

    viii. Field: Time Stamp

    • • Format: Date and Time
    • • Value: Not relevant

    ix. Field: Pulse Rate

    • • This field is not included

    x. Field: User ID

    • • This field is not included

    xi. Field: Measurement Status

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.

    5. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object – Metric-Structure-Small attribute.

    | +| Pass/Fail criteria | In step 5, the Systolic/Diastolic/Map compound numeric object – Metric-Structure-Small attribute is present and its value is {0x03, 0x03} (ms-struct-compound-fix, 3). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_METRIC_STRUCT_SMALL (2675)
    • Attribute-type: SEQUENCE {ms-struct (INT-U8), ms-comp-no (INT-U8)}
    • Attribute-value:
      • • ms-struct Element: 03 (hex), ms-struct-compound-fix(3)
      • • ms-comp-no Element: 03 (hex)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Structure-Small attribute value.

    | + +| | | | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-008 | | | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Metric-Id-List Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BP Numeric 5; M | | +| Test purpose |

    Check that:

    PHG includes Systolic/Diastolic/Map Compound Numeric Object – Metric-Id-List attribute in transcoder output.

    | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [AND]
    Metric-Id-List is set to {MDC_PRESS_BLD_NONINV_SYS,
    MDC_PRESS_BLD_NONINV_DIA, MDC_PRESS_BLD_NONINV_MEAN}. | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
        6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
          • • This field is not included
        7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
          • • This field is not included
        8. viii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        9. ix. Field: Pulse Rate
          • • This field is not included
        10. x. Field: User ID
          • • This field is not included
        11. xi. Field: Measurement Status
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | – Metric-Id-List attribute. | +| Pass/Fail criteria | In step 5, the Systolic/Diastolic/Map compound numeric object – Metric-Id-List attribute is present and its value is {MDC_PRESS_BLD_NONINV_SYS, MDC_PRESS_BLD_NONINV_DIA, MDC_PRESS_BLD_NONINV_MEAN}. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id-List attribute is present:

    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_ID_PHYSIO_LIST (2678)
    • Attribute-type: SEQUENCE OF {{OID-Type(INT-U16)}}
    • Attribute-value: 00 03 00 06 4A 05 4A 06 4A 07 (hex) [Note that 0x00 0x03 is the number of elements in the sequence and 0x00 06 is the length of the sequence]
      • i. First Element: 4A 05 (hex) or 18949 (dec)
      • ii. Second Element: 4A 06 (hex) or 18950 (dec)
      • iii. Third Element: 4A 07 (hex) or 18951 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes three segments like these with a Metric-Id-List attribute values (check OBX-3 in three segments):

    OBX[? NM 150021^MDC_PRESS_BLD_NONINV_SYS^MDC  1.0.a.x 100 266016^MDC_DIM_MMHG^MDC    R  OBX[? NM 150022^MDC_PRESS_BLD_NONINV_DIA^MDC  1.0.a.y 70 266016^MDC_DIM_MMHG^MDC    R  OBX[? NM 150023^MDC_PRESS_BLD_NONINV_MEAN^MDC  1.0.a.z 80 266016^MDC_DIM_MMHG^MDC    R
    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BP/BV-009 | | | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Unit-Code Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BP Numeric 6; M | BP Numeric 7; M | +| Test purpose |

    Check that:

    PHG includes Systolic/Diastolic/Map Compound Numeric Object – Unit-Code attribute in transcoder output.

    [AND]

    IF Blood Pressure Measurement Compound Value - Systolic (mmHg), Diastolic (mmHg) and Mean Arterial Pressure (mmHg) fields of Blood Pressure Measurement characteristic are present THEN Systolic/Diastolic/Map Compound Numeric Object – Unit-Code attribute is set to MDC_DIM_MMHG

    [AND]

    IF Blood Pressure Measurement Compound Value - Systolic (kPa), Diastolic (kPa) and Mean Arterial Pressure (kPa) fields of Blood Pressure Measurement characteristic are present THEN Systolic/Diastolic/Map Compound Numeric Object – Unit-Code attribute is set to MDC_DIM_KILO_PASCAL

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a profile (device specialization) supported by the PHG under test; it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest
    | | | + +for this test case is: + +- a. Blood pressure measurement (0x2A35) +3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state). +4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value: + - a. Blood pressure measurement (0x2A35) + - i. Field: Flags + - Format: 8 bit + - Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included + - ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg) + - Format: SFLOAT + - Value: 100.0 + - iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg) + - Format: SFLOAT + - Value: 70.0 + - iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg) + - Format: SFLOAT + - Value: 80.0 + - v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa) + - This field is not included + - vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa) + - This field is not included + - vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa) + - This field is not included + - viii. Field: Time Stamp + - Format: Date and Time + - Value: Not relevant + - ix. Field: Pulse Rate + - This field is not included + - x. Field: User ID + - This field is not included + - xi. Field: Measurement Status + - This field is not included +5. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object – Unit-Code attribute. +6. The simulated PHD sends the measurement to the PHG under test with the following value: + - a. Blood pressure measurement (0x2A35) + - i. Field: Flags + - Format: 8 bit + - Value: 0000 0011 (MSB → LSB). Blood pressure measurement value in units of kPa and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
      • • This field is not included
    • iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
      • • This field is not included
    • iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
      • • This field is not included
    • v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
      • • Format: SFLOAT
      • • Value: 13.33
    • vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
      • • Format: SFLOAT
      • • Value: 9.33
    • vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
      • • Format: SFLOAT
      • • Value: 10.67
    • viii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • ix. Field: Pulse Rate
      • • This field is not included
    • x. Field: User ID
      • • This field is not included
    • xi. Field: Measurement Status
      • • This field is not included

    7. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object – Unit-Code attribute.

    | +| Pass/Fail criteria |

    In step 5, the Systolic/Diastolic/Map compound numeric object – Unit-Code attribute is present and its value is MDC_DIM_MMHG.

    In step 7, the Systolic/Diastolic/Map compound numeric object – Unit-Code attribute is present and its value is MDC_DIM_KILO_PASCAL.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_MMHG or 3872 (dec) or 0F 20 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes three segments like these with Unit-Code attribute value (check OBX-6 in three segments):

    OBX[?][NM][150021^MDC_PRESS_BLD_NONINV_SYS^MDC] 1.0.a.x[100][266016^MDC_DIM_MMHG^MDC]   R   [current_date_time]  OBX[?][NM][150022^MDC_PRESS_BLD_NONINV_DIA^MDC] 1.0.a.y[70][266016^MDC_DIM_MMHG^MDC]   R   [current_date_time]
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    OBX ? NM 150023^MDC_PRESS_BLD_NONINV_MEAN^MDC
    1.0.a.z 80 266016^MDC_DIM_MMHG^MDC
    R [ current_date_time]

    Note that "[ current_date_time]" is optional at the end of each segment because the date and time can be specified in the parent segment (OBX ?
    150020^MDC_PRESS_BLD_NONINV^MDC 1.0.a X [ current_date_time])

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_KILO_PASCAL or 3843 (dec) or 0F 03 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes three segments like these with Unit-Code attribute value (check OBX-6 in three segments):

    OBX ? NM 150021^MDC_PRESS_BLD_NONINV_SYS^MDC
    1.0.a.x 13.33 265987^MDC_DIM_KILO_PASCAL^MDC
    R [ current_date_time]

    OBX ? NM 150022^MDC_PRESS_BLD_NONINV_DIA^MDC
    1.0.a.y 9.33 265987^MDC_DIM_KILO_PASCAL^MDC
    R [ current_date_time]

    OBX ? NM 150023^MDC_PRESS_BLD_NONINV_MEAN^MDC
    1.0.a.z 10.67 265987^MDC_DIM_KILO_PASCAL^MDC
    R [ current_date_time]

    Note that "[ current_date_time]" is optional at the end of each segment because the date and time can be specified in the parent segment (OBX ?
    150020^MDC_PRESS_BLD_NONINV^MDC 1.0.a X [ current_date_time])

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-010 | | | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Absolute-Time-Stamp Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BP Numeric 9; M | Date-Time Conv 2; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | +| Test purpose |

    Check that:

    PHG transcodes Time Stamp field of Blood Pressure Measurement characteristic into Systolic/Diastolic/Map Compound Numeric Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a profile (device specialization) supported by the PHG under test; it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state)
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:

    a. Blood pressure measurement (0x2A35)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
    • ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
      • • Format: SFLOAT
      • • Value: 100.0
    • iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
      • • Format: SFLOAT
      • • Value: 70.0
    • iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
      • • Format: SFLOAT
      • • Value: 80.0
    • v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
      • • This field is not included
    • vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
      • • This field is not included
    • vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
      • • This field is not included
    • viii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: August 2nd, 2012, 10:39:27
    • ix. Field: Pulse Rate
      • • This field is not included
    • x. Field: User ID
      • • This field is not included
    • xi. Field: Measurement Status
      • • This field is not included

    5. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object – Absolute-Time-Stamp attribute

    | +| Pass/Fail criteria | In step 5, the Systolic/Diastolic/Map compound numeric object – Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field of the Blood pressure measurement characteristic and the fraction of seconds is set to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-value:

    • • century: 20 (hex) or 32 (dec)
    • • year: 12 (hex) or 18 (dec)
    • • month: 08 (hex) or 8 (dec)
    • • day: 02 (hex) or 2 (dec)
    • • hour: 10 (hex) or 16 (dec)
    • • minute: 39 (hex) or 57 (dec)
    • • second: 27 (hex) or 39 (dec)
    • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX[?] 150020^MDC_PRESS_BLD_NONINV^MDC 1.0.a     X   20120802103927+0000
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-011 | | | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Compound-Basic-Nu-Observed-Value Attribute 1 | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BP Numeric 10; M | Short Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Blood Pressure Systolic, Diastolic and Map Value fields of Blood Pressure Measurement characteristic into Systolic/Diastolic/Map Compound Numeric Object - Compound-Basic-Nu-Observed-Value attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a profile (device specialization) supported by the PHG under test; it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: 100.0
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
    | | | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: SFLOAT
    • • Value: 70.0

    iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)

    • • Format: SFLOAT
    • • Value: 80.0

    v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)

    • • This field is not included

    vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)

    • • This field is not included

    vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)

    • • This field is not included

    viii. Field: Time Stamp

    • • Format: Date and Time
    • • Value: Not relevant

    ix. Field: Pulse Rate

    • • This field is not included

    x. Field: User ID

    • • This field is not included

    xi. Field: Measurement Status

    • • This field is not included

    5. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-Observed-Value attribute.

    6. The simulated PHD sends the measurement to the PHG under test with the following value:

    a. Blood pressure measurement (0x2A35)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0000 0011 (MSB → LSB). Blood pressure measurement value in units of kPa, Time Stamp field is included and Pulse Rate, User ID and measurement Status fields are not included

    ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)

    • • This field is not included

    iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)

    • • This field is not included

    iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)

    • • This field is not included

    v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)

    • • Format: SFLOAT
    • • Value: 13.33

    vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)

    • • Format: SFLOAT
    • • Value: 9.33

    vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure

    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    (kPa)

    1. viii. Format: SFLOAT
      • Value: 10.67
    2. ix. Field: Time Stamp
      • Format: Date and Time
      • Value: Not relevant
    3. x. Field: Pulse Rate
      • This field is not included
    4. xi. Field: User ID
      • This field is not included
    5. xii. Field: Measurement Status
      • This field is not included

    7. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the Systolic/Diastolic/Map compound numeric object – Compound-Basic-Nu-Observed-Value attribute is present and its value matches with the blood pressure measurement value (mmHg) fields of the Blood pressure measurement characteristic (Systolic: 100.0, Diastolic:70.0, MAP: 80.0).

    In step 7, the Systolic/Diastolic/Map compound numeric object – Compound-Basic-Nu-Observed-Value attribute is present and its value matches with the blood pressure measurement value (kPa) fields of the Blood pressure measurement characteristic (Systolic: 13.33, Diastolic:9.33, MAP: 10.67).

    | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • Attribute-type: SEQUENCE OF {[SFLOAT]}
    • Attribute-value: 00 03 00 06 xx xx yy yy zz zz (hex), where 'xx xx' is the Systolic value, 'yy yy' is the Diastolic value and 'zz zz' is the MAP value [Note that 0x00 0x03 is the number of elements in the sequence and 0x00 06 is the length of the sequence]
      • Systolic: F3 E8 (hex) or 00 64 (hex) or 10 0A (hex) or 20 01 (hex) or 100.0 (dec)
      • Diastolic: F2 BC (hex) or 00 46 (hex) or 10 07 (hex) or 70.0 (dec)
      • MAP: F3 20 (hex) or 00 50 (hex) or 10 08 (hex) or 80.0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes three segments like these with a Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 150021^MDC_PRESS_BLD_NONINV_SYS^MDC  1.0.a.x 100 266016^MDC_DIM_MMHG^MDC    R   [current_date_time]  OBX ? NM 150022^MDC_PRESS_BLD_NONINV_DIA^MDC  1.0.a.y 70 266016^MDC_DIM_MMHG^MDC    R   [current_date_time]  OBX ? NM 150023^MDC_PRESS_BLD_NONINV_MEAN^MDC  1.0.a.z 80 266016^MDC_DIM_MMHG^MDC    R   [current_date_time]

    Note that " [current_date_time]" is optional at the end of each segment because the date and time can be specified in the parent segment (OBX ? NM 150020^MDC_PRESS_BLD_NONINV^MDC 1.0.a X [current_date_time])

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Object: Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • Attribute-type: SEQUENCE OF [{SFLOAT}]
    • Attribute-value: 00 03 00 06 E5 35 E3 A5 E4 2B (hex) [Note that 0x00 0x03 is the number of elements in the sequence and 0x00 06 is the length of the sequence]
      • • Systolic: E5 35 (hex) or 13.33 (dec)
      • • Diastolic: E3 A5 (hex) 9.33 (dec)
      • • MAP: E4 2B (hex) 10.67 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes three segments like these with a Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?][NM][150021^MDC_PRESS_BLD_NONINV_SYS^MDC  1.0.a.x 13.33 265987^MDC_DIM_KILO_PASCAL^MDC    R  [current_date_time]  OBX[?][NM][150022^MDC_PRESS_BLD_NONINV_DIA^MDC  1.0.a.y 9.33 265987^MDC_DIM_KILO_PASCAL^MDC    R  [current_date_time]  OBX[?][NM][150023^MDC_PRESS_BLD_NONINV_MEAN^MDC  1.0.a.z 10.67 265987^MDC_DIM_KILO_PASCAL^MDC    R  [current_date_time]

    Note that "[[current_date_time]]" is optional at the end of each segment because the date and time can be specified in the parent segment (OBX[?][150020^MDC_PRESS_BLD_NONINV^MDC 1.0.a X [current_date_time]])

    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-012 | | | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Compound-Basic-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | BP Numeric 10; M | Short Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Blood Pressure Systolic, Diastolic and Map Value fields of Blood Pressure Measurement characteristic into Systolic/Diastolic/Map Compound Numeric Object - Compound-Basic-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x07FF), NRes (0x0800), +INFINITY (0x07FE) and -INFINITY (0x0802)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a profile (device specialization) supported by the PHG under test; it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
    | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
    1. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
      • • Format: SFLOAT
      • • Value: 100.0
    2. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
      • • Format: SFLOAT
      • • Value: 70.0
    3. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
      • • Format: SFLOAT
      • • Value: 80.0
    4. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
      • • This field is not included
    5. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
      • • This field is not included
    6. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
      • • This field is not included
    7. viii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    8. ix. Field: Pulse Rate
      • • This field is not included
    9. x. Field: User ID
      • • This field is not included
    10. xi. Field: Measurement Status
      • • This field is not included
    1. 5. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object – Compound-Basic-Nu-Observed-Value attribute.
    2. 6. The simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: 07 FF (hex). Special value: NaN
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: 07 FF (hex). Special value: NaN
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    (mmHg)

    • • Format: SFLOAT
    • • Value: 07 FF (hex). Special value: NaN
    1. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
      • • This field is not included
    2. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
      • • This field is not included
    3. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
      • • This field is not included
    4. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    5. Field: Pulse Rate
      • • This field is not included
    6. Field: User ID
      • • This field is not included
    7. Field: Measurement Status
      • • This field is not included
    1. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object – Compound-Basic-Nu-Observed-Value attribute.
    2. The simulated PHD sends the measurement to the PHG under test with the following value:
      1. Blood pressure measurement (0x2A35)
        1. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
        2. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: 08 00 (hex). Special value: NRes
        3. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: 08 00 (hex). Special value: NRes
        4. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: 08 00 (hex). Special value: NRes
        5. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
        6. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
          • • This field is not included
        7. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
          • • This field is not included
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +- viii. Field: Time Stamp + - Format: Date and Time + - Value: Not relevant + - ix. Field: Pulse Rate + - This field is not included + - x. Field: User ID + - This field is not included + - xi. Field: Measurement Status + - This field is not included +9. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-Observed-Value attribute. +10. The simulated PHD sends the measurement to the PHG under test with the following value: +- a. Blood pressure measurement (0x2A35) + - i. Field: Flags + - Format: 8 bit + - Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included + - ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg) + - Format: SFLOAT + - Value: 07 FE (hex). Special value: +INFINITY + - iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg) + - Format: SFLOAT + - Value: 07 FE (hex). Special value: +INFINITY + - iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg) + - Format: SFLOAT + - Value: 07 FE (hex). Special value: +INFINITY + - v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa) + - This field is not included + - vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa) + - This field is not included + - vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa) + - This field is not included + - viii. Field: Time Stamp + - Format: Date and Time + - Value: Not relevant + - ix. Field: Pulse Rate + - This field is not included + - x. Field: User ID + - This field is not included + - xi. Field: Measurement Status + - This field is not included + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    11. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-Observed-Value attribute.

    12. The simulated PHD sends the measurement to the PHG under test with the following value:

    1. a. Blood pressure measurement (0x2A35)
      1. i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
      2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
        • • Format: SFLOAT
        • • Value: 08 02 (hex). Special value: -INFINITY
      3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
        • • Format: SFLOAT
        • • Value: 08 02 (hex). Special value: -INFINITY
      4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
        • • Format: SFLOAT
        • • Value: 08 02 (hex). Special value: -INFINITY
      5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
        • • This field is not included
      6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
        • • This field is not included
      7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
        • • This field is not included
      8. viii. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
      9. ix. Field: Pulse Rate
        • • This field is not included
      10. x. Field: User ID
        • • This field is not included
      11. xi. Field: Measurement Status
        • • This field is not included

    13. Check in PHG transcoder output for the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-Observed-Value attribute is present and its value is 100.0 for Systolic, 70.0 for Diastolic and 80.0 for MAP.

    In step 7, the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-Observed-Value attribute is present and its value is 0x07FF for Systolic, Diastolic and MAP.

    In step 9, the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-Observed-Value attribute is present and its value is 0x0800 for Systolic, Diastolic and MAP.

    In step 11, the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-Observed-Value attribute is present and its value is 0x07FE for Systolic, Diastolic and MAP.

    In step 13, the Systolic/Diastolic/Map compound numeric object, Compound-Basic-Nu-

    | + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Observed-Value attribute is present and its value is 0x0802 for Systolic, Diastolic and MAP. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • Attribute-type: SEQUENCE OF {{SFLOAT}}
    • Attribute-value: 00 03 00 06 xx xx yy yy zz zz (hex), where 'xx xx' is the Systolic value, 'yy yy' is the Diastolic value and 'zz zz' is the MAP value [Note that 0x00 0x03 is the number of elements in the sequence and 0x00 06 is the length of the sequence]
      • • Systolic: F3 E8 (hex) or 00 64 (hex) or 10 0A (hex) or 20 01 (hex) or 100.0 (dec)
      • • Diastolic: F2 BC (hex) or 00 46 (hex) or 10 07 (hex) or 70.0 (dec)
      • • MAP: F3 20 (hex) or 00 50 (hex) or 10 08 (hex) or 80.0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 150021^MDC_PRESS_BLD_NONINV_SYS^MDC  1.0.a.x 100 266016^MDC_DIM_MMHG^MDC    R   [current_date_time]  OBX ? NM 150022^MDC_PRESS_BLD_NONINV_DIA^MDC  1.0.a.y 70 266016^MDC_DIM_MMHG^MDC    R   [current_date_time]  OBX ? NM 150023^MDC_PRESS_BLD_NONINV_MEAN^MDC  1.0.a.z 80 266016^MDC_DIM_MMHG^MDC    R   [current_date_time]

    Note that "[[current_date_time]]" is optional at the end of each segment because the date and time can be specified in the parent segment (OBX ? 150020^MDC_PRESS_BLD_NONINV^MDC 1.0.a X [current_date_time])

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • Attribute-type: SEQUENCE OF {{SFLOAT}}
    • Attribute-value: 00 03 00 06 07 FF 07 FF 07 FF (hex) [Note that 0x00 0x03 is the number of elements in the sequence and 0x00 06 is the length of the sequence]
      • • Systolic: 07 FF (hex) or NaN (note that a decimal value is not allowed)
      • • Diastolic: 07 FF (hex) or NaN (note that a decimal value is not allowed)
      • • MAP: 07 FF (hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (150021^MDC_PRESS_BLD_NONINV_SYS^MDC, 150022^MDC_PRESS_BLD_NONINV_DIA^MDC and 150023^MDC_PRESS_BLD_NONINV_MEAN) because they have a special value and these values are not included in the PCD-01 message.

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • Systolic/Diastolic/Map compound numeric object
    • Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • Attribute-type: SEQUENCE OF {{SFLOAT}}
    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ❑ Attribute-value: 00 03 00 06 08 00 08 00 08 00(hex) [Note that 0x00 0x03 is the number of elements in the sequence and 0x00 06 is the length of the sequence]
      • • Systolic: 08 00 (hex) or NRes (note that a decimal value is not allowed)
      • • Diastolic: 08 00 (hex) or NRes (note that a decimal value is not allowed)
      • • MAP: 08 00 (hex) or NRes (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (150021^MDC_PRESS_BLD_NONINV_SYS^MDC, 150022^MDC_PRESS_BLD_NONINV_DIA^MDC and 150023^MDC_PRESS_BLD_NONINV_MEAN) because they have a special value and these values are not included in the PCD-01 message.

    In step 11, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • ❑ Systolic/Diastolic/Map compound numeric object
    • ❑ Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • ❑ Attribute-type: SEQUENCE OF [{SFLOAT}]
    • ❑ Attribute-value: 00 03 00 06 07 FE 07 FE 07 FE (hex) [Note that 0x00 0x03 is the number of elements in the sequence and 0x00 06 is the length of the sequence]
      • • Systolic: 07 FE (hex) or +INFINITY (note that a decimal value is not allowed)
      • • Diastolic: 07 FE (hex) or +INFINITY (note that a decimal value is not allowed)
      • • MAP: 07 FE (hex) or +INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (150021^MDC_PRESS_BLD_NONINV_SYS^MDC, 150022^MDC_PRESS_BLD_NONINV_DIA^MDC and 150023^MDC_PRESS_BLD_NONINV_MEAN) because they have a special value and these values are not included in the PCD-01 message.

    In step 13, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • ❑ Systolic/Diastolic/Map compound numeric object
    • ❑ Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • ❑ Attribute-type: SEQUENCE OF [{SFLOAT}]
    • ❑ Attribute-value: 00 03 00 06 08 02 08 02 08 02 (hex) [Note that 0x00 0x03 is the number of elements in the sequence and 0x00 06 is the length of the sequence]
      • • Systolic: 08 02 (hex) or -INFINITY (note that a decimal value is not allowed)
      • • Diastolic: 08 02 (hex) or -INFINITY (note that a decimal value is not allowed)
      • • MAP: 08 02 (hex) or -INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (150021^MDC_PRESS_BLD_NONINV_SYS^MDC, 150022^MDC_PRESS_BLD_NONINV_DIA^MDC and 150023^MDC_PRESS_BLD_NONINV_MEAN) because they have a special value and these values are not included in the PCD-01 message.

    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|-----------------|-----------------------------------------------------------------------------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-013 | +| TP label | Whitepaper. Systolic/Diastolic/Map Compound Numeric Object - Blood Pressure measurement value | + +| | | | | | | +|--------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-----------------|--| +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | | | +| | Testable items | Short Float Type 1; C | Date-Time Conv 1; M | BP Numeric 9; M | | +| | | BP Numeric 10; M | | | | +| Test purpose | |

    Check that:

    PHG processes correctly the Blood Pressure Measurement Compound Value (mmHg), Blood Pressure Measurement Compound Value (kPa) and Time Stamp fields of Blood Pressure Measurement

    | | | | +| Applicability | | C_MAN_BLE_000 AND C_MAN_BLE_003 | | | | +| Other PICS | | | | | | +| Initial condition | | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure | |
    1. 1. The simulated PHD is configured with a profile (device specialization) supported by the PHG under test; it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Blood pressure measurement value in units of mmHg and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: 100.0
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: 70.0
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: 80.0
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
        6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
          • • This field is not included
        7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
          • • This field is not included
        8. viii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 11:08:25
        9. ix. Field: Pulse Rate
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    x. Field: User ID

    • • This field is not included

    xi. Field: Measurement Status

    • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    6. The simulated PHD sends the measurement to the PHG under test with the following value:

    a. Blood pressure measurement (0x2A35)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0011 (MSB → LSB). Blood pressure measurement value in units of kPa and Time Stamp fields are included, Pulse Rate, User ID and measurement Status fields are not included
    • ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
      • • This field is not included
    • iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
      • • This field is not included
    • iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
      • • This field is not included
    • v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
      • • Format: SFLOAT
      • • Value: 13.33
    • vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
      • • Format: SFLOAT
      • • Value: 9.33
    • vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
      • • Format: SFLOAT
      • • Value: 10.67
    • viii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: August 2nd, 2012, 11:09:05
    • ix. Field: Pulse Rate
      • • This field is not included
    • x. Field: User ID
      • • This field is not included
    • xi. Field: Measurement Status
      • • This field is not included

    7. Check that the PHG under test accepts the measurement and decodes its value properly (measurement values, units and time stamp)

    | +| Pass/Fail criteria |

    In step 5, the PHG under test shows the following measurement: 100.0 mmHg for Systolic, 70.0 mmHg for Diastolic and 80.0 mmHg for MAP, with the time stamp '2012-08-02 11:08:25'.

    In step 7, the PHG under test shows the following measurement 13.33 kPa for Systolic, 9.33 kPa for Diastolic and 10.67 kPa for MAP, with the time stamp '2012-08-02 11:09:05'.

    | + +| | | +|--------------|--| +| Notes | | +|--------------|--| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-014 | | | +| TP label | Whitepaper. Pulse Rate Object - Handle Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | PR Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Pulse Rate object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Pulse Rate object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 AND C_MAN_BLE_005 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
        6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
          • • This field is not included
        7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
          • • This field is not included
        8. viii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        9. ix. Field: Pulse Rate
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: SFLOAT
    • • Value: Not relevant

    x. Field: User ID

    • • This field is not included

    xi. Field: Measurement Status

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.

    5. Check in PHG transcoder output for the Pulse rate object, Handle attribute.

    | +| Pass/Fail criteria | In step 5, the Pulse rate object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Pulse rate object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Handle attribute value.

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-015 | | | +| TP label | Whitepaper. Pulse Rate Object - Type Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | PR Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Systolic Pulse Rate object, Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_SCADA, MDC_PULS_RATE_NON_INV}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 AND C_MAN_BLE_005 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:

    a. Blood pressure measurement (0x2A35)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included

    ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)

    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: SFLOAT
    • • Value: Not relevant

    iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)

    • • Format: SFLOAT
    • • Value: Not relevant

    iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)

    • • Format: SFLOAT
    • • Value: Not relevant

    v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)

    • • This field is not included

    vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)

    • • This field is not included

    vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)

    • • This field is not included

    viii. Field: Time Stamp

    • • Format: Date and Time
    • • Value: Not relevant

    ix. Field: Pulse Rate

    • • Format: SFLOAT
    • • Value: Not relevant

    x. Field: User ID

    • • This field is not included

    xi. Field: Measurement Status

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.

    4. Check in PHG transcoder output for the Pulse rate object, Type attribute.

    | +| Pass/Fail criteria | In step 5, the Pulse rate object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_PULS_RATE_NON_INV} | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Pulse rate object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_PULS_RATE_NON_INV or 18474 (dec) or 48 2A (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX[?]1NMI2495463MDC_PULS_RATE_NON_INV4MDC51.0.0.a6

    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-016 | | | +| TP label | Whitepaper. Pulse Rate Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | PR Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Pulse Rate object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 AND C_MAN_BLE_005 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
        6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
          • • This field is not included
        7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
          • • This field is not included
        8. viii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        9. ix. Field: Pulse Rate
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: SFLOAT
    • • Value: Not relevant

    x. Field: User ID

    • • This field is not included

    xi. Field: Measurement Status

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.

    5. Check in PHG transcoder output for the Pulse rate object, Metric-Spec-Small attribute.

    | +| Pass/Fail criteria | In step 4, the Pulse rate object, Metric-Spec-Small attribute is present and its value is {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Pulse rate object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-017 | | | +| TP label | Whitepaper. Pulse Rate Object - Unit-Code Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | PR Numeric 4; M | | +| Test purpose |

    Check that:

    PHG includes Pulse Rate object, Unit-Code attribute in transcoder output.

    [AND]

    IF Blood Pressure Measurement – Pulse Rate field of Blood Pressure Measurement characteristic is present THEN Pulse Rate object, Unit-Code attribute is set to MDC_DIM_BEAT_PER_MIN

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 AND C_MAN_BLE_005 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement to the PHG under test with the following value:

    1. a. Blood pressure measurement (0x2A35)
      1. i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp field and Pulse Rate field are included, User ID and measurement Status fields are not included
      2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
        • • This field is not included
      6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
        • • This field is not included
      7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
        • • This field is not included
      8. viii. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
      9. ix. Field: Pulse Rate
        • • Format: SFLOAT
        • • Value: 110.0
      10. x. Field: User ID
        • • This field is not included
      11. xi. Field: Measurement Status
        • • This field is not included

    5. Check in PHG transcoder output for the Pulse rate object, Unit-Code attribute.

    | +| Pass/Fail criteria | In step 5, the Pulse rate object, Unit-Code attribute is present and its value is MDC_DIM_BEAT_PER_MIN. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes

      Unit-Code attribute is present:

      • Object: Pulse rate object
      • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
      • Attribute-type: INT-U16
      • Attribute-value: MDC_DIM_BEAT_PER_MIN or 2720 (dec) or 0A A0 (hex)
    2. b) WAN PCD-01 message
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?][NM][149546^ MDC_PULS_RATE_NON_INV ^MDC][1.0.0.a]
    10 264864^MDC_DIM_BEAT_PER_MIN^MDC R [current_date_time]

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-018 | | | +| TP label | Whitepaper. Pulse Rate Object - Absolute-Time-Stamp Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | PR Numeric 6; M | Date-Time Conv 2; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | +| Test purpose |

    Check that:

    PHG transcodes Time Stamp field of Blood Pressure Measurement characteristic into Pulse Rate Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 AND C_MAN_BLE_005 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)

    • • This field is not included

    vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)

    • • This field is not included

    viii. Field: Time Stamp

    • • Format: Date and Time
    • • Value: August 2nd, 2012, 10:39:27

    ix. Field: Pulse Rate

    • • Format: SFLOAT
    • • Value: 110.0

    x. Field: User ID

    • • This field is not included

    xi. Field: Measurement Status

    • • This field is not included

    5. Check in PHG transcoder output for the SystolicPulse rate object, Absolute-Time-Stamp attribute.

    | +| Pass/Fail criteria | In step 5, the Pulse rate object, Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field of the Blood pressure measurement characteristic and the fraction of seconds is set to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Pulse rate object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 10 (hex) or 16 (dec)
      • • minute: 39 (hex) or 57 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX[?][NM][149546]^MDC_PULS_RATE_NON_INV^MDC[1.0.0.a]
    10 264864^MDC_DIM_BEAT_PER_MIN^MDC R 20120802103927+0000

    | + +| | | | +|-----------------|---------------------------------------------------------------------|-------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-019 | | +| TP label | Whitepaper. Pulse Rate Object - Basic-Nu-Observed-Value Attribute 1 | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------|--| +| | Testable items | PR Numeric 7; M | Short Float Type 1; C | | +| Test purpose | Check that:
    PHG transcodes Blood Pressure Measurement – Heart Rate field of Blood Pressure Measurement characteristic into Pulse Rate Object - Simple-Nu-Observed-Value attribute | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 AND C_MAN_BLE_005 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood Pressure Measurement (0x2A35)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
        6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
          • • This field is not included
        7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
          • • This field is not included
        8. viii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        9. ix. Field: Pulse Rate
          • • Format: SFLOAT
          • • Value: 110.0
        10. x. Field: User ID
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • This field is not included
    xi. Field: Measurement Status
    • This field is not included
    5. Check the output of the PHG transcoder for the Pulse rate object, Basic-Nu-Observed-Value attribute. | +| Pass/Fail criteria | In step 5, the Heart rate object, Basic-Nu-Observed-Value attribute is present and its value matches with the Blood Pressure Measurement – Heart Rate Value (bpm) field of the Blood pressure measurement characteristic (110). | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Basic-Nu-Observed-Value attribute is present:
    Object: Pulse rate object
    Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    Attribute-type: SFLOAT
    Attribute-value: F4 4C (hex) or 00 6E (hex) or 01 0B (hex) or 110 (dec)
    b) WAN PCD-01 message
    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):
    OBX[?][NM][149546^MDC_PULS_RATE_NON_INV^MDC][1.0.0.a]
    10 264864^MDC_DIM_BEAT_PER_MIN^MDC R [current_date_time] | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-020 | | | +| TP label | Whitepaper. Pulse Rate Object - Basic-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | PR Numeric 7; M | Short Float Type 1; C | +| Test purpose | Check that:
    PHG transcodes Blood Pressure Measurement- Heart rate field of Blood Pressure Measurement characteristic into Heart Rate Object - Basic-Nu-Observed-Value attribute
    [AND]
    PHG assigns the following special values: NaN (0x07FF), NRes (0x0800), +INFINITY (0x07FE) and -INFINITY (0x0802) | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 AND C_MAN_BLE_005 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
    a. Blood pressure measurement (0x2A35)
    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
    a. Blood pressure measurement (0x2A35)
    i. Field: Flags
    • Format: 8 bit
    • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in
    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included

    • ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
      • • Format: SFLOAT
      • • Value: Not relevant
    • iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
      • • Format: SFLOAT
      • • Value: Not relevant
    • iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
      • • Format: SFLOAT
      • • Value: Not relevant
    • v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
      • • This field is not included
    • vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
      • • This field is not included
    • vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
      • • This field is not included
    • viii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • ix. Field: Pulse Rate
      • • Format: SFLOAT
      • • Value: 110.0
    • x. Field: User ID
      • • This field is not included
    • xi. Field: Measurement Status
      • • This field is not included

    5. Check in PHG transcoder output for the Pulse rate object, Basic-Nu-Observed-Value attribute.

    6. The simulated PHD sends the measurement to the PHG under test with the following value:

    • a. Blood pressure measurement (0x2A35)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included
      • ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      • iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      • iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    (mmHg)

    • • Format: SFLOAT
    • • Value: Not relevant

    v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)

    • • This field is not included

    vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)

    • • This field is not included

    vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)

    • • This field is not included

    viii. Field: Time Stamp

    • • Format: Date and Time
    • • Value: Not relevant

    ix. Field: Pulse Rate

    • • Format: SFLOAT
    • • Value: 07 FF (hex). Special value: NaN

    x. Field: User ID

    • • This field is not included

    xi. Field: Measurement Status

    • • This field is not included

    7. Check in PHG transcoder output for the Pulse rate object, Basic-Nu-Observed-Value attribute.

    8. The simulated PHD sends the measurement to the PHG under test with the following value:

    a. Blood pressure measurement (0x2A35)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included

    ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)

    • • Format: SFLOAT
    • • Value: Not relevant

    iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)

    • • Format: SFLOAT
    • • Value: Not relevant

    iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)

    • • Format: SFLOAT
    • • Value: Not relevant

    v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)

    • • This field is not included

    vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)

    • • This field is not included

    vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +- This field is not included +- viii. Field: Time Stamp +- Format: Date and Time + - Value: Not relevant +- ix. Field: Pulse Rate +- Format: SFLOAT + - Value: 08 00 (hex). Special value: NRes +- x. Field: User ID +- This field is not included +- xi. Field: Measurement Status +- This field is not included + +9. Check in PHG transcoder output for the Pulse rate object, Basic-Nu-Observed-Value attribute. + +10. The simulated PHD sends the measurement to the PHG under test with the following value: + +a. Blood pressure measurement (0x2A35) + +- i. Field: Flags + - Format: 8 bit + - Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included +- ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg) + - Format: SFLOAT + - Value: Not relevant +- iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg) + - Format: SFLOAT + - Value: Not relevant +- iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg) + - Format: SFLOAT + - Value: Not relevant +- v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa) + - This field is not included +- vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa) + - This field is not included +- vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa) + - This field is not included +- viii. Field: Time Stamp + - Format: Date and Time + - Value: Not relevant +- ix. Field: Pulse Rate + - Format: SFLOAT + - Value: 07 FE (hex). Special value: +INFINITY +- x. Field: User ID + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
      • • This field is not included
    • xi. Field: Measurement Status
      • • This field is not included

    11. Check in PHG transcoder output for the Pulse rate object, Basic-Nu-Observed-Value attribute.

    12. The simulated PHD sends the measurement to the PHG under test with the following value:

    1. a. Blood pressure measurement (0x2A35)
      1. i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included
      2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
        • • This field is not included
      6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
        • • This field is not included
      7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
        • • This field is not included
      8. viii. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
      9. ix. Field: Pulse Rate
        • • Format: SFLOAT
        • • Value: 08 02 (hex). Special value: -INFINITY
      10. x. Field: User ID
        • • This field is not included
      11. xi. Field: Measurement Status
        • • This field is not included

    13. Check in PHG transcoder output for the Pulse rate object, Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the Pulse rate object, Basic-Nu-Observed-Value attribute is present and its value is 110.

    In step 7, the Pulse rate object, Basic-Nu-Observed-Value attribute is present and its value is 0x07FF.

    In step 9, the Pulse rate object, Basic -Nu-Observed-Value attribute is present and its value is

    | + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    0x0800.

    In step 11, the Pulse rate object, Basic -Nu-Observed-Value attribute is present and its value is 0x07FE.

    In step 13, the Pulse rate object, Basic -Nu-Observed-Value attribute is present and its value is 0x0802.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Pulse rate object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: F4 4C (hex) or 00 6E (hex) or 01 0B (hex) or 110 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 149546^MDC_PULS_RATE_NON_INV^MDC 1.0.0.a 10  264864^MDC_DIM_BEAT_PER_MIN^MDC   R  [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Pulse rate object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (149546^ MDC_PULS_RATE_NON_INV ^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Pulse rate object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 08 00 (hex) or NRes (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (149546^MDC_PULS_RATE_NON_INV^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 11, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Pulse rate object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 07 FF (hex) or +INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (149546^MDC_PULS_RATE_NON_INV^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 13, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Pulse rate object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 08 02 (hex) or -INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (149546^MDC_PULS_RATE_NON_INV^MDC) because it has a special value and these values are not included in the PCD-01 message.

    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-021 | | | +| TP label | Whitepaper. Pulse Rate measurement value | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | Short Float Type 1; C | Date-Time Conv 1; M | +| | | PR Numeric 7; M | PR Numeric 6; M | +| Test purpose |

    Check that:

    PHG processes correctly the Pulse Rate Value (bpm) and Time Stamp fields of Blood Pressure Measurement

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_003 AND C_MAN_BLE_005 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood pressure profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Blood pressure measurement (0x2A35)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Blood pressure measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0110 (MSB → LSB). Blood pressure measurement value in units of mmHg, Time Stamp and Pulse Rate fields are included, User ID and measurement Status fields are not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)

    • Format: SFLOAT
    • Value: Not relevant

    v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)

    • This field is not included

    vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)

    • This field is not included

    vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)

    • This field is not included

    viii. Field: Time Stamp

    • Format: Date and Time
    • Value: August 2nd, 2012, 10:39:27

    ix. Field: Pulse Rate

    • Format: SFLOAT
    • Value: 110.0

    x. Field: User ID

    • This field is not included

    xi. Field: Measurement Status

    • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (pulse rate measurement value, pulse rate units and time stamp).

    | +| Pass/Fail criteria | In step 5, the PHG under test shows the following measurement Pulse Rate = 110 beats per minute (bpm) with the time stamp '2012-08-02 10:39:27'. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-022 | | | +| TP label | Whitepaper. Systolic/Diastolic/Map Numeric object, Measurement-Status Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | BP Numeric 11; M | | +| Test purpose |

    Check that:

    PHG transcodes Blood Pressure Measurement – Measurement Status field of Blood Pressure Measurement characteristic into Systolic/Diastolic/Map Numeric object, Measurement-Status attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Blood Pressure Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. Blood Pressure Feature (0x2A49)
      2. Blood Pressure Measurement (0x2A35)
    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    | | | + +4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value: + - a. Blood Pressure Feature (0x2A49) + - Format: 16 bit + - Value: 0000 0000 0000 0000 (MSB → LSB). + - b. Blood Pressure Measurement (0x2A35) + - i. Field: Flags + - Format: 8 bit + - Value: 0001 0010 (MSB → LSB). Blood Pressure Measurement Value in units of mmHg, Time Stamp and Measurement Status fields are included, Pulse Rate and User ID fields are not included. + - ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg) + - Format: SFLOAT + - Value: Not relevant + - iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg) + - Format: SFLOAT + - Value: Not relevant + - iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg) + - Format: SFLOAT + - Value: Not relevant + - v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa) + - This field is not included + - vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa) + - This field is not included + - vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa) + - This field is not included + - viii. Field: Time Stamp + - Format: Date and Time + - Value: Not relevant + - ix. Field: Pulse Rate + - This field is not included. + - x. Field: User ID + - This field is not included + - xi. Field: Measurement Status + - Format: 16 bit + - Value: 0000 0000 0000 0000 +5. Check in the PHG transcoder output the Systolic/Diastolic/Map Numeric object, Measurement-Status attribute +6. The simulated PHD sends a Measurement to the PHG under test with the following value: + - a. Blood Pressure Feature (0x2A49) + - Format: 16 bit + - Value: 0000 0000 0000 0100 (MSB → LSB). Irregular Pulse Detection supported. + - b. Blood Pressure Measurement (0x2A35) + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. i. Field: Flags
      • • Format: 8 bit
      • • Value: 0001 0010 (MSB → LSB). Blood Pressure Measurement Value in units of mmHg, Time Stamp and Measurement Status fields are included, Pulse Rate and User ID fields are not included.
    2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
      • • Format: SFLOAT
      • • Value: Not relevant
    3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
      • • Format: SFLOAT
      • • Value: Not relevant
    4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
      • • Format: SFLOAT
      • • Value: Not relevant
    5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
      • • This field is not included
    6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
      • • This field is not included
    7. vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
      • • This field is not included
    8. viii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    9. ix. Field: Pulse Rate
      • • This field is not included.
    10. x. Field: User ID
      • • This field is not included
    11. xi. Field: Measurement Status
      • • Format: 16 bit
      • • Value: 0000 0000 0000 0100

    7. Check in the PHG transcoder output the Systolic/Diastolic/Map Numeric object, Measurement-Status attribute

    | +| Pass/Fail criteria |

    In Step 5, the Systolic/Diastolic/Map object, Measurement-Status attribute is not present.

    In Step 7, the Systolic/Diastolic/Map object, Measurement-Status attribute is present and set to “questionable” (0x4000).

    | +| Notes |

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Measurement-Status attribute is present:

    • Object: Systolic/Diastolic/Map Object
    • Attribute-id: MDC_ATTR_MSMT_STAT (2375)
    • Attribute-type: BITS16
    • Attribute-value: 40 00 (hex)

    b) WAN PCD-01 message

    | + +| | | +|--|----------------------------------------------------------------------------------| +| | PCD-01 message does not include segments with Metric-Spec-Small attribute value. | +|--|----------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/BPM/BV-023 | | | +| TP label | Whitepaper. Pulse Rate object, Measurement-Status Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | PR Numeric 8; M | | +| Test purpose |

    Check that:

    PHG transcodes Blood Pressure Measurement – Measurement Status field of Blood Pressure Measurement characteristic into Pulse Rate object, Measurement-Status attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_003 AND C_MAN_BLE_005 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Blood Pressure Profile (device specialization), it has a measurement ready to be sent and it is in Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. Blood Pressure Feature (0x2A49)
      2. b. Blood Pressure Measurement (0x2A35)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the Simulated PHD and it starts a pairing process with simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Blood Pressure Feature (0x2A49)
        • • Format: 16 bit
        • • Value: 0000 0000 0000 0000 (MSB → LSB).
      2. b. Blood Pressure Measurement (0x2A35)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0110 (MSB → LSB). Blood Pressure Measurement Value in units of mmHg, Time Stamp, Pulse Rate and Measurement Status fields are included, User ID field is not included
        2. ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        3. iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        4. iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
          • • Format: SFLOAT
          • • Value: Not relevant
        5. v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
          • • This field is not included
        6. vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
          • • This field is not included
    | | | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
      • • This field is not included
    • viii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • ix. Field: Pulse Rate
      • • Format: SFLOAT
      • • Value: 110.0
    • x. Field: User ID
      • • This field is not included
    • xi. Field: Measurement Status
      • • Format: 16 bit
      • • Value: 0000 0000 0000 0000

    5. Check in the PHG transcoder output the Pulse Rate object, Measurement-Status attribute

    6. The simulated PHD sends a Measurement to the PHG under test with the following value:

    • a. Blood Pressure Feature (0x2A49)
      • • Format: 16 bit
      • • Value: 0000 0000 0000 0100 (MSB → LSB). Irregular Pulse Detection supported.
    • b. Blood Pressure Measurement (0x2A35)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0001 0110 (MSB → LSB). Blood Pressure Measurement Value in units of mmHg, Time Stamp, Pulse Rate and Measurement Status fields are included, User ID field is not included
      • ii. Field: Blood Pressure Measurement Compound Value – Systolic (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      • iii. Field: Blood Pressure Measurement Compound Value – Diastolic (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      • iv. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (mmHg)
        • • Format: SFLOAT
        • • Value: Not relevant
      • v. Field: Blood Pressure Measurement Compound Value – Systolic (kPa)
        • • This field is not included
      • vi. Field: Blood Pressure Measurement Compound Value – Diastolic (kPa)
        • • This field is not included
      • vii. Field: Blood Pressure Measurement Compound Value – Mean Arterial Pressure (kPa)
        • • This field is not included
      • viii. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    ix. Field: Pulse Rate

    • • Format: SFLOAT
    • • Value: 110.0

    x. Field: User ID

    • • This field is not included

    xi. Field: Measurement Status

    • • Format: 16 bit
    • • Value: 0000 0000 0000 0100

    7. Check in the PHG transcoder output the Pulse Rate object, Measurement-Status attribute

    | +| Pass/Fail criteria |

    In Step 5, the Pulse Rate object, Measurement-Status attribute is not present.

    In Step 7, the Pulse Rate object, Measurement-Status attribute is present and set to “questionable” (0x4000).

    | +| Notes |

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Measurement-Status attribute is present:

    • Object: Pulse Rate Object
    • Attribute-id: MDC_ATTR_MSMT_STAT (2375)
    • Attribute-type: BITS16
    • Attribute-value: 40 00 (hex)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value.

    | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-Bluetooth PHDT v1.3] Bluetooth SIG (2012), *Personal Health Devices Transcoding White Paper* (version 1.3) +[https://www.bluetooth.org/docman/handlers/downloadoc.ashx?doc\\_id=294540](https://www.bluetooth.org/docman/handlers/downloadoc.ashx?doc_id=294540) +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-CDG 2017] Personal Connected Health Alliance, Continua Design Guidelines (2017), "Keratin", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules* + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.13. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.11. + +- [b-TI] PHD Testable items. Test Tool v8.0.0.0 – Excel sheet v1.10. + + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.850.3-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.850.3-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..814ea0c32afee4ee67cf185ef1c4f24dcb0092cb --- /dev/null +++ b/marked/H/T-REC-H.850.3-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d34f44030a67aa4c4c7a66d113d089c848271d1cfae9e9319d5bd2da7a9d686 +size 4227 diff --git a/marked/H/T-REC-H.850.3-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.850.3-202008-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2223bd79a4b2fc24d9a8d5fda806c77f6439e567 --- /dev/null +++ b/marked/H/T-REC-H.850.3-202008-I_PDF-E/raw.md @@ -0,0 +1,949 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.850.3** + +(08/2020) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface Part +10C: Transcoding for Bluetooth Low Energy: +Personal Health Gateway – Heart-rate** + +Recommendation ITU-T H.850.3 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.850.3 + +### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10C: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Heart-rate + +## Summary + +Recommendation ITU-T H.850.3 provides a test suite structure (TSS) and the test purposes (TP) for the transcoding of heart rate data by personal health gateways in the Personal Health Devices (PHD) interface of application-level data between the Bluetooth Low Energy Bluetooth Generic Attribute Profile (GATT) format and the IEEE 11073-20601 data format, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.850.3 is a transposition of clause 3.5 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.850.3 | 2017-04-29 | 16 | 11.1002/1000/13356 | +| 2.0 | ITU-T H.850.3 | 2020-08-13 | 16 | 11.1002/1000/14347 | + +## Keywords + +Bluetooth generic attribute profile, Bluetooth low energy (BLE), continua design guidelines, conformance testing, data format transcoding, e-health, heart rate, IEEE 11073-20601, ITU-T H.810, personal area network, personal connected health devices, personal health devices interface, personal health gateway, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 3 | +| 3.1 Terms defined elsewhere ..... | 3 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 4 | +| 6 Test suite structure..... | 5 | +| 7 Electronic attachment ..... | 8 | +| Annex A Test purposes ..... | 9 | +| A.1 TP definition conventions..... | 9 | +| A.2 Subgroup 2.4.4 – Whitepaper Heart-rate requirements (HR)..... | 11 | +| Bibliography..... | 38 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of clause 3.5 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2012-10-05 | Initial release for Test Tool DG2011 based on the requirements in [b-CDG 2011]. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. It uses "TSS&TP_DG2011_LP-PAN_PART_10_v1.0.doc" as a baseline and adds new features included in [b-CDG 2012] (BPM and HR profiles). | +| 1.2 | 2014-01-24 | Initial release for Test Tool DG2013. It uses "TSS&TP_DG2012_LP-PAN_PART_10_v1.1.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • Adds glucose meter BLE
    • Adds BLE SSP support
    • Adds NFC new transport
    • Adds INR device specialization
    | +| 1.3 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.2.doc" as a baseline and adds new features included in Documentation Enhancements:
    • "Other PICS" row has been added
    | +| 1.4 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015]:
    • Adds WS/BCA BLE device specialization
    • Adds SABTE IEEE device specialization
    | +| 1.5 | 2016-01-26 | First maintenance release for Test Tool DG2015. It uses "TSS&TP_DG2015_LP-PAN_PART_10_v1.4.doc" as a baseline and adds some updates according to the Maintenance 2015 activity. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]:
    • Adds PLX BLE device specialization
    • Adds PLX CGM device specialization
    | +| 1.7 | 2017-07-18 | Second Maintenance Release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.6.doc" as a baseline and corrects minor typos. | +| 1.8 | 2020-06-02 | Updates related to the value of the Reg-Cert-Data-List according to [b-CDG 2017]. | + +## Recommendation ITU-T H.850.3 + +## Conformance of ITU-T H.810 personal health devices: Personal Health Devices interface Part 10C: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Heart-rate + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 10C. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway. In addition to the main part, the document is subdivided into the following subparts: + - Part 10A: Whitepaper Thermometer requirements + - Part 10B: Whitepaper Blood pressure requirements + - **Part 10C: Whitepaper Heart rate requirements** + - Part 10D: Whitepaper Glucose meter requirements + - Part 10E: Whitepaper Weighing scales requirements + - Part 10F: Whitepaper Pulse oximeter requirements + - Part 10G: Whitepaper Continuous glucose monitoring requirements + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [Bluetooth PHDT v1.4] Bluetooth SIG (2013), *Personal Health Devices Transcoding White Paper, v1.4*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=294539](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=294539) +- [Bluetooth PHDT v1.5] Bluetooth SIG (2014), *Personal Health Devices Transcoding White Paper, v1.5*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=272346](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=272346) +- [Bluetooth PHDT v1.6] Bluetooth SIG (2015), *Personal Health Devices Transcoding White Paper, v1.6*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=310657](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=310657) +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization*. + NOTE – Shorthand to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + + with + + +- [IHE PCD TF 1] IHE PCD TF 1 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 1: Integration Profiles*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol1\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol1_FT_2012-08-16.pdf) +- [IHE PCD TF 2] IHE PCD TF 2 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 2: Transactions*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol2\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol2_FT_2012-08-16.pdf) +- [IHE PCD TF 3] IHE PCD TF 3 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 3: Semantic Content*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol3\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol3_FT_2012-08-16.pdf) + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|--------------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| LSB | Least Significant Bit | +| MDS | Medical Device System | +| MSB | Most Significant Bit | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCD | Patient Care Device | + +| | | +|-------|-------------------------------------------------------| +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| RACP | Record Access Control Point | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purposes | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +# 5 Conventions + +In this text, the uppercase letter L is used as the symbol for litre. + +Several of the test purposes in Annex A refer to "WAN PCD-01 messages"; these messages are specified in the patient care device (PCD) technical framework defined in [IHE PCD TF 1], [IHE PCD TF 2] and [IHE PCD TF 3]. Similarly, the "IEEE 11073 Objects and Attributes" are defined in [ISO/IEEE 11073-104xx]. + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +In this document, hexadecimal numbers are denoted either with the prefix "0x" or by "(hex)" after the number; "(dec)" after a number indicates it is expressed in decimal format. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of ITU-T H.810 is split into eight parts in the ITU-T H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata. | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +# 6 Test suite structure + +The test purposes (TPs) for the Personal Health Devices interface have been divided into the groups and subgroups specified below. Annex A describes the TPs for subgroup 2.4.4 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 1.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 1.4.6: Whitepaper weight scale requirements (WS) + +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + - **Subgroup 2.4.4: Whitepaper heart rate requirements (HR)** + - Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + +- Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +# **7 Electronic attachment** + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth low energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies a test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 2.4.4 – Whitepaper Heart-rate requirements (HR) + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-000 | | | +| TP label | Whitepaper. Heart Rate MDS Object - System-Type Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | HR Specific MDS 1; M | | +| Test purpose | Check that:
    PHG does not include MDS object, System-Type attribute in transcoder output. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    4. Check in PHG transcoder output for the MDS object, System-Type attribute.
    | | | +| Pass/Fail criteria | In step 4, the MDS object, System-Type attribute is not present. | | | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    System-Type attribute is not present:
    Object: MDS object
    Attribute-id: MDC_ATTR_SYS_TYPE (2438)
    Attribute-type: TYPE
    Attribute-value:
    b) WAN PCD-01 message
    PCD-01 message does not include segments with a System-Type attribute value (67974^MDC_ATTR_SYS_TYPE^MDC). | | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-001 | | | +| TP label | Whitepaper. Heart Rate MDS Object - Dev-Configuration-Id Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | HR Specific MDS 2; M | | +| Test purpose | Check that:
    PHG includes MDS object, Dev-Configuration-Id attribute in transcoder output.
    [AND]
    Dev-Configuration-Id value is set to any value in range of 0x4000 to 0x7FFF (Extended Configuration) | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    3. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.

    4. Check in PHG transcoder output for the MDS object, Dev-Configuration-Id attribute.

    | +| Pass/Fail criteria | In step 4, the MDS object, Dev-Configuration-Id attribute is present, its value is inside the range 0x4000 - 0x7FFF. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Dev-Configuration-Id attribute is present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_DEV_CONFIG_ID (2628)
    • Attribute-type: INT-U16
    • Attribute-value: Any value inside the range 16384 - 32767 (dec) or 0x4000 – 0x7FFF (hex)

    b) WAN PCD-01 message

    According to [b-ITU-T H.810 (2013)], the Dev-Configuration-Id shall not be transmitted in the PCD-01 message; therefore it is not possible to check this attribute.

    | + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-002 | | | +| TP label | Whitepaper. Heart Rate MDS Object - System-Type-Spec-List Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | Common MDS 15; M | HR Specific MDS 3; M | +| Test purpose |

    Check that:

    PHG includes MDS object, System-Type-Spec-List attribute in transcoder output.

    [AND]

    System-Type-Spec-List is set to (MDC_DEV_SPEC_PROFILE_ECG, Version 1),
    (MDC_DEV_SPEC_PROFILE_HF_CARDIO, Version 1),
    (MDC_DEV_SUB_SPEC_PROFILE_HR, Version 1)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 3. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    4. 4. Check in PHG transcoder output for the MDS object, System-Type-Spec-List attribute.
    | | | +| Pass/Fail criteria | In step 4, the MDS object, System-Type-Spec-List attribute is present, its value is (MDC_DEV_SPEC_PROFILE_ECG, Version 1), (MDC_DEV_SPEC_PROFILE_HF_CARDIO, Version 1), (MDC_DEV_SUB_SPEC_PROFILE_HR, Version 1). | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    System-Type-Spec-List attribute is present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_SYS_TYPE_SPEC_LIST (2650)
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-type: SEQUENCE OF [{type (INT-U16), version (INT-U16)}]

    Attribute-value:

    • • type: MDC_DEV_SPEC_PROFILE_ECG or 4102 (dec) or 10 06 (hex)
    • • version: 1 (dec) or 00 01 (hex)
    • • type: MDC_DEV_SPEC_PROFILE_HF_CARDIO or 4137 (dec) or 10 29 (hex)
    • • version: 1 (dec) or 00 01 (hex)
    • • type: MDC_DEV_SUB_SPEC_PROFILE_HR or 4237 (dec) or 10 8D (hex)
    • • version: 1 (dec) or 00 01 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with System-Type-Spec-List attribute value (check OBX-5):

    OBX ? NM 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a  528390^MDC_DEV_SPEC_PROFILE_ECG^MDC~528425^MDC_DEV_SPEC_P ROFILE_HF_CARDIO^MDC~528525^MDC_DEV_SUB_SPEC_PROFILE_HR^M DC     R
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-003 | | | | +| TP label | Whitepaper. Heart Rate MDS Object - Reg-Cert-Data-List Attribute | | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | | +| | Testable items | Common MDS 14; M | Regulatory Conv 1; M | | +| Test purpose |

    Check that:

    PHG transcodes IEEE 11073-20601 Regulatory Certification Data List characteristic into MDS object, Reg-Cert-Data-List attribute

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. IEEE 11073-20601 Regulatory Certification Data List (0x2A2A)
        • • Format: reg-cert-data-list (opaque structure)
        • • Value: 00 02 00 14 02 01 00 0A 08 00 00 02 00 04 80 06 80 8D 02 02 00 02 80 00 (hex)
          • i. Element:
            • • auth-body-and-struc-type:
              • - auth-body: 02 (hex) auth-body-continua(2)
              • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
            • • auth-body-data:
              • - major-IG-version: 08 (hex)
              • - minor-IG-version: 00 (hex)
              • - certified-devices: 80 06 80 8D (hex). BLE ECG and BLE Heart Rate
          • ii. Element:
            • • auth-body-and-struc-type:
              • - auth-body: 02 (hex). auth-body-continua(2)
    | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
    • • auth-body-data:
      • - regulation-bit-field: 80 00 (hex). Unregulated device
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD.
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the IEEE 11073-20601 Regulatory Certification Data List characteristic.
    3. 5. The simulated PHD sends the measurement to the PHG under test.
    4. 6. Check in PHG transcoder output for the MDS object, Reg-Cert-Data-List attribute.
    | +| Pass/Fail criteria | In step 6, the MDS object, Reg-Cert-Data-List attribute is present and its value matches with the IEEE 11073-20601 Regulatory Certification Data List characteristic value. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Reg-Cert-Data-List attribute is present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_REG_CERT_DATA_LIST (2635)
    • Attribute-type: SEQUENCE OF [{auth-body-and-struc-type, auth-body-data}, {...}]
    • Attribute-value: 00 02 00 14 02 01 00 0A 08 00 00 02 00 04 80 06 80 8D 02 02 00 02 80 00
      • i. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex) auth-body-continua(2)
          • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
        • • auth-body-data:
          • - major-IG-version: 08 (hex)
          • - minor-IG-version: 00 (hex)
          • - certified-devices: 80 06 80 8D (hex). BLE ECG and BLE Heart Rate
      • ii. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex). auth-body-continua(2)
          • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
        • • auth-body-data:
          • - regulation-bit-field: 80 00 (hex). Unregulated device

    b) WAN PCD-01 message

    PCD-01 message includes five segments like these with Reg-Cert-Data-List attribute value (check OBX-5 in four segments):

    OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC  1.0.0.a 2^auth-body-continua     R  OBX ? ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC  1.0.0.a.x 6.1     R  OBX ? NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST ^MDC 1.0.0.a.y 32774~32909     R  OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC  1.0.0.b 2^auth-body-continua     R  OBX ? CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS ^MDC 1.0.0.b.z 1^unregulated-device(0)     R
    | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-004 | | | +| TP label | Whitepaper. Heart Rate MDS Object - Tick Resolution Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | HR Specific MDS 5; M | | +| Test purpose | Check that:
    PHG includes MDS object, Tick Resolution attribute in transcoder output. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_006 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Heart rate measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0000 (MSB → LSB). Heart rate measurement value in uint8 format and RR-Interval fields are present, Energy Expended field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • This field is not included
        5. v. Field: RR-Interval
          • • Format: List of uint16
          • • Value: Not relevant
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the MDS object, Tick Resolution attribute.
    | | | +| Pass/Fail criteria | In step 5, the MDS object, Tick Resolution attribute is present and its value is 1024 ticks per second. | | | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Tick Resolution attribute is present:
    Object: MDS object
    Attribute-id: MDC_ATTR_TICK_RES (2693)
    Attribute-type: FLOAT
    Attribute-value: 00 00 04 00 (hex) or FF 00 28 00 (hex) or FE 01 90 00 (hex) or FD 0F A0 00 (hex) or FC 9C 40 00 (hex) or 1024 (dec)
    b) WAN PCD-01 message | | | + +| | | +|--|---------------------------------------------------------------------------------------| +| | OBX ? NM 68229^MDC_ATTR_TICK_RES^MDC 1.0.0.a 1024
    265842^MDC_DIM_PER_SEC^MDC R | +|--|---------------------------------------------------------------------------------------| + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-005 | | | +| TP label | Whitepaper. Heart Rate Measurement Object - Handle Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | HR Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Heart rate Measurement object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Heart Rate Measurement object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Heart rate measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). Heart rate measurement value in uint8 format field is included, RR-Interval and Energy Expended fields are not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • This field is not included
        5. v. Field: RR-Interval
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the Heart rate measurement object, Handle attribute.
    | | | +| Pass/Fail criteria | In step 5, the Body temperature object, Handle attribute is not present; however, if it is present then its value is different to 0. | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    Object: Heart rate measurement object

    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Handle attribute value.

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-006 | | | +| TP label | Whitepaper. Heart Rate Measurement Object - Type Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | HR Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Heart Rate Measurement object, Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_SCADA, MDC_ECG_HEART_RATE_INSTANT}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      • a. Heart rate measurement (0x2A37)
        • i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). Heart rate measurement value in uint8 format field is included, RR-Interval and Energy Expended fields are not included
        • ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        • iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        • iv. Field: Energy Expended
          • • This field is not included
        • v. Field: RR-Interval
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the Heart rate measurement object, Type attribute.
    | | | +| Pass/Fail criteria | In step 5, the Heart rate measurement object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_ECG_HEART_RATE_INSTANT}. | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Type attribute is present:

    • Object: Heart rate measurement object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_ECG_HEART_RATE_INSTANT or 21982 (dec) or 55 DE (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX[?][NM]8410590^MDC_ECG_HEART_RATE_INSTANT^MDC 1.0.0.a 90 264864^MDC_DIM_BEAT_PER_MIN^MDC R

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-007 | | +| TP label | Whitepaper. Heart Rate Measurement Object - Metric-Spec-Small Attribute | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | +| | Testable items | HR Numeric 3; M | +| Test purpose |

    Check that:

    PHG includes Heart Rate Measurement object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x4040} (mss-avail-stored-data, mss-acc-agent-initiated).

    | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 | | +| Other PICS | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Heart rate measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). Heart rate measurement value in uint8 format field is included, RR-Interval and Energy Expended fields are not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • This field is not included
        5. v. Field: RR-Interval
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.

    5. Check in PHG transcoder output for the Heart rate measurement object, Metric-Spec-Small attribute.

    | +| Pass/Fail criteria | In step 5, the Heart rate measurement object, Metric-Spec-Small attribute is present and its value is {0x4040} (mss-avail-stored-data, mss-acc-agent-initiated). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Heart rate measurement object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: 40 40 (hex) or BITS mss-avail-stored-data(1), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-008 | | | +| TP label | Whitepaper. Heart Rate Measurement Object - Unit-Code Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | HR Numeric 4; M | | +| Test purpose |

    Check that:

    PHG includes Heart Rate Measurement object, Unit-Code attribute in transcoder output.

    [AND]

    Heart Rate Measurement object, Unit-Code attribute is set to MDC_DIM_BEAT_PER_MIN

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Heart rate measurement (0x2A37)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Heart rate measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). Heart rate measurement value in uint8 format field is included, Energy Expended and RR-Interval fields are not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: 90
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • iii. Field: Heart Rate Measurement Value (uint16)
      • • This field is not included
    • iv. Field: Energy Expended
      • • This field is not included
    • v. Field: RR-Interval
      • • This field is not included

    5. Check in PHG transcoder output for the Heart rate measurement object, Unit-Code attribute.

    6. The simulated PHD sends the measurement to the PHG under test with the following value:

    • a. Heart rate measurement (0x2A37)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0001 (MSB → LSB). Heart rate measurement value in uint16 format field is included, Energy Expended and RR-Interval fields are not included
      • ii. Field: Heart Rate Measurement Value (uint8)
        • • This field is not included
      • iii. Field: Heart Rate Measurement Value (uint16)
        • • Format: uint16
        • • Value: 110
      • iv. Field: Energy Expended
        • • This field is not included
      • v. Field: RR-Interval
        • • This field is not included

    7. Check in PHG transcoder output for the Heart rate measurement object, Unit-Code attribute.

    | +| Pass/Fail criteria |

    In step 5, the Heart rate measurement object, Unit-Code attribute is present and its value is MDC_DIM_BEAT_PER_MIN.

    In step 7, the Heart rate measurement object, Unit-Code attribute is present and its value is MDC_DIM_BEAT_PER_MIN.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • ❑ Object: Heart rate measurement object
    • ❑ Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • ❑ Attribute-type: INT-U16
    • ❑ Attribute-value: MDC_DIM_BEAT_PER_MIN or 2720 (dec) or 0A A0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX ? NM 8410590^MDC_ECG_HEART_RATE_INSTANT^MDC 1.0.0.a 90
    264864^MDC_DIM_BEAT_PER_MIN^MDC R

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • ❑ Object: Heart rate measurement object
    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_BEAT_PER_MIN or 2720 (dec) or 0A A0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?][NM][8410590^MDC_ECG_HEART_RATE_INSTANT^MDC 1.0.0.a 10 264864^MDC_DIM_BEAT_PER_MIN^MDC R

    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-009 | | | +| TP label | Whitepaper. Heart Rate Measurement Object - Simple-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | HR Numeric 6; M | | +| Test purpose |

    Check that:

    PHG transcodes Heart Rate Measurement Value field of Heart Rate Measurement characteristic into Heart Rate Measurement Object - Simple-Nu-Observed-Value attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      • a. Heart rate measurement (0x2A37)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      • a. Heart rate measurement (0x2A37)
        • i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). Heart Rate Measurement Value in uint8 format field is included, Energy Expended and RR-Interval fields are not included
        • ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: 90
        • iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        • iv. Field: Energy Expended
          • • This field is not included
        • v. Field: RR-Interval
          • • This field is not included
    5. 5. Check in PHG transcoder output for the Heart rate measurement object, Simple-Nu-Observed-Value attribute.
    6. 6. The simulated PHD sends the measurement to the PHG under test with the following value:
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0001 (MSB → LSB). Heart rate measurement value in uint16 format field is included, Energy Expended and RR-Interval fields are not included
    2. ii. Field: Heart Rate Measurement Value (uint8)
      • • This field is not included
    3. iii. Field: Heart Rate Measurement Value (uint16)
      • • Format: uint16
      • • Value: 110
    4. iv. Field: Energy Expended
      • • This field is not included
    5. v. Field: RR-Interval
      • • This field is not included

    7. Check in PHG transcoder output for the Heart rate measurement object, Simple-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the Heart rate measurement object, Simple-Nu-Observed-Value attribute is present and its value matches with the Heart Rate Measurement Value (INT-U8) field of the Heart rate measurement characteristic (90).

    In step 7, the Heart rate measurement object, Simple-Nu-Observed-Value attribute is present and its value matches with the Heart Rate Measurement Value (INT-U16) field of the Heart rate measurement characteristic (110).

    | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Heart rate measurement object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: 00 00 00 5A (hex) or 90 (dec) [Note that exponent value for this FLOAT value must be 0]

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 8410590^MDC_ECG_HEART_RATE_INSTANT^MDC 1.0.0.a 90  264864^MDC_DIM_BEAT_PER_MIN ^MDC    R

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Heart rate measurement object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: 00 00 00 6E (hex) or 110 (dec) [Note that exponent value for this FLOAT value must be 0]

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 8410590^MDC_ECG_HEART_RATE_INSTANT^MDC 1.0.0.a 10  264864^MDC_DIM_BEAT_PER_MIN ^MDC    R
    | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-010 | | | +| TP label | Whitepaper. RR-Interval Object - Handle Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | RR Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include RR-Interval object, Handle Attribute in transcoder output

    [OR]

    If PHG includes RR-Interval object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_006 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Heart rate measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0000 (MSB → LSB). Heart rate measurement value in uint8 format and RR-Interval fields are included, Energy Expended field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • This field is not included
        5. v. Field: RR-Interval
          • • Format: List of uint16
          • • Value: Not relevant
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the RR-Interval object, Handle attribute.
    | | | +| Pass/Fail criteria | In step 5, the RR-Interval object, Handle attribute is not present; however, if it is present then its value is different to 0. | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: RR-Interval object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Attribute-type: INT-U16
    Attribute-value: Any value other than 0
    b) WAN PCD-01 message
    PCD-01 message does not include segments with a Handle attribute value. | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-011 | | +| TP label | Whitepaper. RR-Interval Object - Type Attribute | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | +| | Testable items | RR Numeric 2; M | +| Test purpose | Check that:
    PHG includes RR-Interval object, Type attribute in transcoder output.
    [AND]
    Type is set to {MDC_PART_SCADA, MDC_ECG_TIME_PD_RR_GL} | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_006 | | +| Other PICS | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Heart rate measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0000 (MSB → LSB). Heart rate measurement value in uint8 format and RR-Interval fields are included, Energy Expended field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint8)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • This field is not included
        5. v. Field: RR-Interval
          • • Format: List of uint16
          • • Value: Not relevant
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the RR-Interval object, Type attribute.
    | | +| Pass/Fail criteria | In step 5, the RR-Interval object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_ECG_TIME_PD_RR_GL}. | | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Type attribute is present:

    • Object: RR-Interval object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_ECG_TIME_PD_RR_GL or 16168 (dec) or 3F 28 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these with a Type attribute value (check OBX-3):

    OBX ? NM 147240^MDC_ECG_TIME_PD_RR_GL^MDC 1.0.0.a  600268992^MDC_DIM_TICK^MDC     R  OBX ? NM 147240^MDC_ECG_TIME_PD_RR_GL^MDC 1.0.0.b  900268992^MDC_DIM_TICK^MDC     R
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-012 | | | +| TP label | Whitepaper. RR-Interval Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | RR Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes RR-Interval object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x5440} (mss-avail-stored-data, mss-acc-agent-initiated, mss-msmt-btb-metric, mss-msmt-aperiodic).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_006 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Heart rate measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0000 (MSB → LSB). Heart rate measurement value in uint8 format and RR-Interval fields are included, Energy Expended field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • This field is not included
        5. v. Field: RR-Interval
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: List of uint16
    • Value: Not relevant
    | +| |
    1. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.
    3. Check in PHG transcoder output for the RR-Interval object, Metric-Spec-Small attribute.
    | +| Pass/Fail criteria | In step 5, the RR-Interval object, Metric-Spec-Small attribute is present and its value is {0x5440} (mss-avail-stored-data, mss-acc-agent-initiated, mss-msmt-btb-metric, mss-msmt-aperiodic). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: RR-Interval object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: 54 40 (hex) or BITS mss-avail-stored-data(1), mss-msmt-aperiodic (3), mss-msmt-btb-metric (5), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-013 | | | +| TP label | Whitepaper. RR-Interval Object - Unit-Code Attribute | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | RR Numeric 5; M | | +| Test purpose |

    Check that:

    PHG includes RR-Interval object, Unit-Code attribute in transcoder output.

    [AND]

    RR-Interval object, Unit-Code attribute is set to MDC_DIM_TICK

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_006 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Heart rate profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. Heart rate measurement (0x2A37)
    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. Heart rate measurement (0x2A37)
        1. Field: Flags
          • Format: 8 bit
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 0001 0000 (MSB → LSB). Heart rate measurement value in uint8 format and RR-Interval fields are included, Energy Expended field is not included

    ii. Field: Heart Rate Measurement Value (uint8)

    • • Format: uint8
    • • Value: Not relevant

    iii. Field: Heart Rate Measurement Value (uint16)

    • • This field is not included

    iv. Field: Energy Expended

    • • This field is not included

    v. Field: RR-Interval

    • • Format: List of uint16
    • • Value: Not relevant

    5. Check in PHG transcoder output for the RR-Interval object, Unit-Code attribute.

    | +| Pass/Fail criteria | In step 5, the RR-Interval object, Unit-Code attribute is present and its value is MDC_DIM_TICK. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: RR Interval object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_TICK or 6848 (dec) or 1A C0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these with Unit-Code attribute value (check OBX-6):

    OBX ? NM 147240^ MDC_ECG_TIME_PD_RR_GL^MDC 1.0.0.a 600  268992^MDC_DIM_TICK ^MDC    R  OBX ? NM 147240^ MDC_ECG_TIME_PD_RR_GL^MDC 1.0.0.b 900  268992^MDC_DIM_TICK ^MDC    R
    | + +| | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-014 | | +| TP label | Whitepaper. RR-Interval Object -Simple-Nu-Observed-Value Attribute | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | +| | Testable items | RR Numeric 6; M | +| Test purpose |

    Check that:

    PHG transcodes the variable-size RR-Interval field of Heart Rate Measurement characteristic into RR-Interval Object - Simple-Nu-Observed-Value attribute

    | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_006 | | +| Other PICS | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | +| Test procedure |
    1. 1. The simulated PHD is configured with a profile (device specialization) supported by the PHG under test; it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
    | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. a. Heart rate measurement (0x2A37)
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Heart rate measurement (0x2A37)
        1. i. Field: Flags
          1. • Format: 8 bit
          2. • Value: 0001 0000 (MSB → LSB). Heart rate measurement value in uint8 format and RR-Interval fields are included, Energy Expended field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          1. • Format: uint8
          2. • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint16)
          1. • This field is not included
        4. iv. Field: Energy Expended
          1. • This field is not included
        5. v. Field: RR-Interval
          1. • Format: List of uint16
          2. • Value: {600, 900}
    3. 5. Check in PHG transcoder output for the RR-Interval object, Compound-Simple-Nu-Observed-Value attribute.
    | +| Pass/Fail criteria | In step 5, the RR-Interval object, Simple-Nu-Observed-Value attribute is present and its value matches with RR-Interval field of Heart rate measurement {600, 900}. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes

      Simple-Nu-Observed-Value attribute is present two times:

      • Object: RR-Interval object
      • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
      • Attribute-type: FLOAT
      • Attribute-value:
        1. • First occurrence: 00 00 02 58 (hex) or FF 00 17 70 (hex) or FE 00 EA 60 (hex) or FD 09 27 C0 (hex) or FC 5B 8D 80 (hex) or 600 (dec)
        2. • Second occurrence: 00 00 03 84 (hex) or FF 00 23 28 (hex) or FE 01 5F 90 (hex) or FD 0D BB A0 (hex) or FC 89 54 40 (hex) or 900 (dec)
    2. b) WAN PCD-01 message

      PCD-01 message includes a segment like this with a Simple-Nu-Observed-Value attribute value (check OBX-5):

      OBX ? NM 147240^MDC_ECG_TIME_PD_RR_GL^MDC 1.0.0.a 600  268992^MDC_DIM_TICK^MDC    R  OBX ? NM 147240^MDC_ECG_TIME_PD_RR_GL^MDC 1.0.0.b 900  268992^MDC_DIM_TICK^MDC    R
    | + +| | | +|-----------------|------------------------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-015 | +| TP label | Whitepaper. Heart Rate measurement value | +| Coverage | [b-Bluetooth PHDT v1.3] | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|--| +| | Testable items | HR Numeric 6; M | | | +| Test purpose |

    Check that:

    PHG processes correctly the Rate Measurement Value field of Heart Rate Measurement characteristic

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_004 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a profile (device specialization) supported by the PHG under test; it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Heart rate measurement (0x2A37)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Heart rate measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). Heart rate measurement value in uint8 format field is included, Energy Expended and RR-Interval fields are not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: 90
        3. iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • This field is not included
        5. v. Field: RR-Interval
          • • This field is not included
    5. 5. Check that the PHG accepts the measurement and decodes its value properly (pulse rate measurement).
    6. 6. The simulated PHD sends the measurement to the PHG under test with the following value:
      1. i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0001 (MSB → LSB). Heart rate measurement value in uint16 format is included, Energy Expended and RR-Interval fields are not included
      2. ii. Field: Heart Rate Measurement Value (uint8)
        • • This field is not included
      3. iii. Field: Heart Rate Measurement Value (uint16)
        • • Format: uint16
        • • Value: 110
      4. iv. Field: Energy Expended
        • • This field is not included
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    v. Field: RR-Interval

    • This field is not included

    7. Check that the PHG accepts the measurement and decodes its value properly (pulse rate measurement).

    | +| Pass/Fail criteria |

    In step 5, the PHG under test shows the following measurement Heart Rate = 90 beats per minute (bpm).

    In step 7, the PHG under test shows the following measurement Heart Rate = 110 beats per minute (bpm).

    | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-016 | | | +| TP label | Whitepaper. RR-Interval measurement value | | | +| Coverage | Spec | [b-Bluetooth PHDT v1.3] | | +| | Testable items | RR Numeric 6; M | | +| Test purpose |

    Check that:

    PHG processes correctly the RR-Interval field of Heart Rate Measurement characteristic

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_004 AND C_MAN_BLE_006 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a profile (device specialization) supported by the PHG under test; it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. Heart rate measurement (0x2A37)
    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. Heart rate measurement (0x2A37)
        1. Field: Flags
          • Format: 8 bit
          • Value: 0001 0000 (MSB → LSB). Heart rate measurement value in uint8 format and RR-Interval fields are present, Energy Expended field is not included
        2. Field: Heart Rate Measurement Value (uint8)
          • Format: uint8
          • Value: Not relevant
        3. Field: Heart Rate Measurement Value (uint16)
          • This field is not included
        4. Field: Energy Expended
          • This field is not included
        5. Field: RR-Interval
          • Format: List of uint16
          • Value: {600, 900}
    5. Check that the PHG accepts the measurement and decodes its value properly (RR-Interval measurement value).
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |

    In step 5, the PHG under test shows the following measurements:

    • • Measurement #1: RR-Interval = 586 ms or 600 ticks (1 tick = 1/1024 s)
    • • Measurement #2: RR-Interval = 879 ms or 900 ticks (1 tick = 1/1024 s)
    | +| Notes | | + +| | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-017 | | | | +| TP label | Whitepaper. Energy Expended Object - Handle Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Energy Numeric 1; O | | | +| Test purpose |

    Check that:

    PHG does not include Energy Expended object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Energy Expended object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_030 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart Rate Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. Heart Rate Measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Heart Rate Measurement Value in uint8 format and Energy Expended fields are included, RR-Interval field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • Format: uint16
          • • Value: 123
        5. v. Field: RR-Interval
          • • This field is not included.
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    5. 5. Check in PHG transcoder output the Energy Expended object, Handle attribute
    | | | | +| Pass/Fail criteria | In Step 5, the Energy Expended object, Handle attribute is not present or, if it is present then its value is different than 0. | | | | + +| | | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Energy Expended Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-018 | | | +| TP label | Whitepaper. Energy Expended Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Energy Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Energy Expended object, Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_PHD_HF, MDC_HF_ENERGY}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_030 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart Rate Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. Heart Rate Measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Heart Rate Measurement Value in uint8 format and Energy Expended fields are included, RR-Interval field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint8)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • Format: uint16
          • • Value: 123
        5. v. Field: RR-Interval
          • • This field is not included.
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Energy Expended object, Type attribute

    | +| Pass/Fail criteria | In Step 5, the Energy Expended object, Type attribute is present and its value is {MDC_PART_PHD_HF, MDC_HF_ENERGY} | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Energy Expended Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_HF or 129 (dec) or 00 81 (hex)
      • • code: MDC_HF_ENERGY or 119 (dec) or 00 77 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these with Type attribute value (check OBX-3):

    OBX[? NM 8454263^MDC_HF_ENERGY^MDC 1.0.0.a]

    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-019 | | | +| TP label | Whitepaper. Energy Expended Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Energy Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Energy Expended object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF040} (mss-avail-intermittent, mss-avail-stored-data, mss-upd-aperiodic, mss-msmt-aperiodic, mss-acc-agent-initiated).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_030 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Heart Rate Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. Heart Rate Measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Heart Rate Measurement Value in uint8 format and Energy Expended fields are included, RR-Interval field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    iii. Field: Heart Rate Measurement Value (uint16)

    • This field is not included

    iv. Field: Energy Expended

    • Format: uint16
    • Value: 123

    v. Field: RR-Interval

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Energy Expended object, Metric-Spec-Small attribute

    | +| Pass/Fail criteria | In Step 5, the Energy Expended object, Metric-Spec-Small attribute is present and its value is {0xF040} (mss-avail-intermittent, mss-avail-stored-data, mss-upd-aperiodic, mss-msmt-aperiodic, mss-acc-agent-initiated). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a. IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Energy Expended Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent (0), mss-avail-stored-data(1), mss-upd-aperiodic (2), mss-msmt-aperiodic (3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b. WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-020 | | | +| TP label | Whitepaper. Energy Expended Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Energy Numeric 4; M | | +| Test purpose |

    Check that:

    PHG includes Energy Expended object, Unit-Code attribute in transcoder output.

    [AND]

    Energy Expended object, Unit-Code attribute is set to MDC_DIM_JOULES

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_030 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Heart Rate Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. Heart Rate Measurement (0x2A37)
    3. The PHG under test initiates a discovery process (Scanning state), it discovers the
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Heart Rate Measurement (0x2A37)

    i. Field: Flags

    • Format: 8 bit
    • Value: 0000 1000 (MSB → LSB). Heart Rate Measurement Value in uint8 format and Energy Expended fields are included, RR-Interval field is not included

    ii. Field: Heart Rate Measurement Value (uint8)

    • Format: uint8
    • Value: Not relevant

    iii. Field: Heart Rate Measurement Value (uint16)

    • This field is not included

    iv. Field: Energy Expended

    • Format: uint16
    • Value: 123

    v. Field: RR-Interval

    • This field is not included

    5. Check in PHG transcoder output the Energy Expended object, Unit-Code attribute

    | +| Pass/Fail criteria | In Step 5, the Energy Expended object, Unit-Code attribute is present and its value is MDC_DIM_JOULES | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a. IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Energy Expended Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_JOULES or 6848 (dec) or 1A C0 (hex)

    b. WAN PCD-01 message

    PCD-01 message includes two segments like these with Unit-Code attribute value (check OBX-6):

    OBX ? NM 8454263^MDC_HF_ENERGY^MDC 1.0.0.a 123000
    266112^MDC_DIM_JOULES^MDC R

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-021 | | | +| TP label | Whitepaper. Energy Expended Object -Simple-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Energy Numeric 5; M | | +| Test purpose |

    Check that:

    PHG transcodes the Energy Expended field of Heart Rate Measurement characteristic into Energy Expended Object - Simple-Nu-Observed-Value attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_004 AND C_MAN_BLE_030 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. Heart Rate Measurement (0x2A37)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Heart Rate Measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Heart Rate Measurement Value in uint8 format and Energy Expended fields are included, RR-Interval field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • Format:
          • • Value:
        5. v. Field: RR-Interval
          • • This field is not included
    5. 5. Check in PHG transcoder output the Energy Expended object, Simple-Nu-Observed-Value attribute
    | +| Pass/Fail criteria | In Step 5, the Energy Expended object, Simple-Nu-Observed-Value attribute is present and its value matches with Energy Expended field of Heart Rate Measurement {} | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present two times:

    • Object: Energy Expended Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: 03 00 00 7B (hex) or 123000 (dec).

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?][NM][8454263^MDC_HF_ENERGY^MDC][1.0.0.a][123000]
    266112^MDC_DIM_JOULES^MDC    R
    | + +| | | | | +|-----------------|-----------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/HR/BV-022 | | | +| TP label | Whitepaper. Energy Expended measurement value | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Energy Numeric 5; M | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose | Check that:
    PHG processes correctly the Energy Expended field of Heart Rate Measurement characteristic | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_004 AND C_MAN_BLE_030 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. Heart Rate Measurement (0x2A37)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Heart Rate Measurement (0x2A37)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Heart Rate Measurement Value in uint8 format and Energy Expended fields are present, RR-Interval field is not included
        2. ii. Field: Heart Rate Measurement Value (uint8)
          • • Format: uint8
          • • Value: Not relevant
        3. iii. Field: Heart Rate Measurement Value (uint16)
          • • This field is not included
        4. iv. Field: Energy Expended
          • • Format: uint16
          • • Value: 123
        5. v. Field: RR-Interval
          • • This field is not included
    5. 5. Check that the PHG accepts the measurement and decodes its value properly (Energy Expended measurement value).
    | +| Pass/Fail criteria | In Step 5, the PHG under test shows the following measurements: 123000 J or 123 kJ. | +| Notes | | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-Bluetooth PHDT v1.3] Bluetooth SIG (2012), *Personal Health Devices Transcoding White Paper* (version 1.3). +[https://www.bluetooth.org/docman/handlers/downloadoc.ashx?doc\\_id=294540](https://www.bluetooth.org/docman/handlers/downloadoc.ashx?doc_id=294540) +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-CDG 2017] Personal Connected Health Alliance, Continua Design Guidelines (2017), "Keratin", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.13. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.11. + +- [b-TI] PHD Testable items. Test Tool v8.0.0.0 – Excel sheet v1.10. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.850.4-202008-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.850.4-202008-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00c533de296f6a990b6aeb78fd22e2f94df95532 --- /dev/null +++ b/marked/H/T-REC-H.850.4-202008-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3d26c33ea10ffda11a52cebac09c68f8b66fe3a17f1fac418a6d39cf3298f87 +size 4200 diff --git a/marked/H/T-REC-H.850.4-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.850.4-202008-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3f54d0998849063055365a784b7aec602d3f1fe9 --- /dev/null +++ b/marked/H/T-REC-H.850.4-202008-I_PDF-E/raw.md @@ -0,0 +1,2755 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.850.4** + +(08/2020) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 10D: Transcoding for Bluetooth Low +Energy: Personal Health Gateway – +Glucose meter** + +Recommendation ITU-T H.850.4 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.850.4 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10D: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Glucose meter + +## Summary + +Recommendation ITU-T H.850.4 provides a test suite structure (TSS) and the test purposes (TP) for the transcoding of glucose meter data by personal health gateways in the Personal Health Devices (PHD) interface of application-level data between the Bluetooth Low Energy Bluetooth Generic Attribute Profile (GATT) format and the IEEE 11073-20601 data format, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.850.4 is a transposition of clause 3.6 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.850.4 | 2017-04-29 | 16 | 11.1002/1000/13357 | +| 2.0 | ITU-T H.850.4 | 2020-08-13 | 16 | 11.1002/1000/14348 | + +## Keywords + +Bluetooth Generic Attribute Profile, Bluetooth Low Energy (BLE), Conformance testing, Continua Design Guidelines, data format transcoding, e-health, glucose meter, IEEE 11073-20601, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, Personal Health Gateway, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|------------------------------------------------------------------|-----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 3 | +| 3.1 | Terms defined elsewhere ..... | 3 | +| 3.2 | Terms defined in this Recommendation..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Test suite structure..... | 5 | +| 7 | Electronic attachment ..... | 8 | +| Annex A | Test purposes ..... | 9 | +| A.1 | TP definition conventions..... | 9 | +| A.2 | Subgroup 2.4.5 – Whitepaper Glucose meter requirements (GL)..... | 11 | +| | Bibliography..... | 180 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of clause 3.6 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2012-10-05 | Initial release for Test Tool DG2011 based on the requirements in [b-CDG 2011]. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. It uses "TSS&TP_DG2011_LP-PAN_PART_10_v1.0.doc" as a baseline and adds new features included in [b-CDG 2012] (BPM and HR profiles). | +| 1.2 | 2014-01-24 | Initial release for Test Tool DG2013. It uses "TSS&TP_DG2012_LP-PAN_PART_10_v1.1.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • Adds glucose meter BLE
    • Adds BLE SSP support
    • Adds NFC new transport
    • Adds INR device specialization
    | +| 1.3 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.2.doc" as a baseline and adds new features included in Documentation Enhancements:
    • "Other PICS" row has been added
    | +| 1.4 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015]:
    • Adds WS/BCA BLE device specialization
    • Adds SABTE IEEE device specialization
    | +| 1.5 | 2016-01-26 | First maintenance release for Test Tool DG2015. It uses "TSS&TP_DG2015_LP-PAN_PART_10_v1.4.doc" as a baseline and adds some updates according to the Maintenance 2015 activity. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]:
    • Adds PLX BLE device specialization
    • Adds PLX CGM device specialization
    | +| 1.7 | 2017-07-18 | Second Maintenance Release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.6.doc" as a baseline and corrects minor typos. | +| 1.8 | 2020-06-02 | Updates related to the value of the Reg-Cert-Data-List according to [b-CDG 2017]. | + +## Recommendation ITU-T H.850.4 + +### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10D: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Glucose meter + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 10D. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway. In addition to the main part, the document is subdivided in the following subparts: + - Part 10A: Whitepaper Thermometer requirements + - Part 10B: Whitepaper Blood pressure requirements + - Part 10C: Whitepaper Heart rate requirements + - **Part 10D: Whitepaper Glucose meter requirements** + - Part 10E: Whitepaper Weighing scales requirements + - Part 10F: Whitepaper Pulse oximeter requirements + - Part 10G: Whitepaper Continuous glucose monitoring requirements + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [Bluetooth PHDT v1.4] Bluetooth SIG (2013), *Personal Health Devices Transcoding White Paper, v1.4*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=294539](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=294539) +- [Bluetooth PHDT v1.5] Bluetooth SIG (2014), *Personal Health Devices Transcoding White Paper, v1.5*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=272346](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=272346) +- [Bluetooth PHDT v1.6] Bluetooth SIG (2015), *Personal Health Devices Transcoding White Paper, v1.6*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=310657](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=310657) +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization*. NOTE – Shorthand to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + + with + + +- [IHE PCD TF 1] IHE PCD TF 1 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 1: Integration Profiles*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol1\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol1_FT_2012-08-16.pdf) +- [IHE PCD TF 2] IHE PCD TF 2 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 2: Transactions*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol2\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol2_FT_2012-08-16.pdf) +- [IHE PCD TF 3] IHE PCD TF 3 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 3: Semantic Content*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol3\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol3_FT_2012-08-16.pdf) + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. +- 3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|--------------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| LSB | Least Significant Bit | +| MDS | Medical Device System | +| MSB | Most Significant Bit | +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCD | Patient Care Device | + +| | | +|-------|-------------------------------------------------------| +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| RACP | Record Access Control Point | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purposes | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +## 5 Conventions + +In this text, the uppercase letter L is used as the symbol for litre. + +Several of the test purposes in Annex A refer to "WAN PCD-01 messages"; these messages are specified in the patient care device (PCD) technical framework defined in [IHE PCD TF 1], [IHE PCD TF 2] and [IHE PCD TF 3]. Similarly, the "IEEE 11073 Objects and Attributes" are defined in [ISO/IEEE 11073-104xx]. + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +In this document, hexadecimal numbers are denoted either with the prefix "0x" or by "(hex)" after the number; "(dec)" after a number indicates it is expressed in decimal format. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of ITU-T H.810 is split into eight parts in the ITU-T H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata. | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure + +The test purposes (TP) for the Personal Health Devices interface have been divided into the groups and subgroups specified below. Annex A describes the TPs for subgroup 2.4.5 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + - Subgroup 1.4.4: Whitepaper heart rate requirements (HR) + - Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) + - Subgroup 1.4.6: Whitepaper weight scale requirements (WS) + +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + - Subgroup 2.4.4: Whitepaper heart rate requirements (HR) + - **Subgroup 2.4.5: Whitepaper glucose meter requirements (GL)** + - Subgroup 2.4.6: Whitepaper weight scale requirements (WS) + +- Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +## **7 Electronic attachment** + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth low energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies a test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. + +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 2.4.5 – Whitepaper Glucose meter requirements (GL) + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-000 | | | +| TP label | Whitepaper. Glucosemeter MDS Object - System-Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Specific MDS 1; M | | +| Test purpose | Check that:
    PHG does not include MDS object, System-Type attribute in transcoder output. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 3. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test.
    4. 4. Check in PHG transcoder output for the MDS object, System-Type attribute.
    | | | +| Pass/Fail criteria | In step 4, the MDS object, System-Type attribute is not present. | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    System-Type attribute is not present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_SYS_TYPE (2438)
    • Attribute-type: TYPE
    • Attribute-value: <NOT PRESENT>

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a System-Type attribute value (67974^MDC_ATTR_SYS_TYPE^MDC).

    | | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-001 | | | +| TP label | Whitepaper. Glucosemeter MDS Object - Dev-Configuration-Id Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Specific MDS 2; M | | +| Test purpose |

    Check that:

    PHG includes MDS object, Dev-Configuration-Id attribute in transcoder output.

    [AND]

    Dev-Configuration-Id value is set to any value in range of 0x4000 to 0x7FFF (Extended Configuration)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 3. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test.
    4. 4. Check in PHG transcoder output for the MDS object, Dev-Configuration-Id attribute.
    | +| Pass/Fail criteria | In step 4, the MDS object, Dev-Configuration-Id attribute is present and its value is inside the range 0x4000 - 0x7FFF. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Dev-Configuration-Id attribute is present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_DEV_CONFIG_ID (2628)
    • Attribute-type: INT-U16
    • Attribute-value: Any value inside the range 16384 - 32767 (dec) or 0x4000 – 0x7FFF (hex)

    b) WAN PCD-01 message

    According to [b-ITU-T H.810 (2013)], the Dev-Configuration-Id shall not be transmitted in the PCD-01 message; therefore it is not possible to check this attribute.

    | + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-002 | | | +| TP label | Whitepaper. Glucosemeter MDS Object - System-Type-Spec-List Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Common MDS 15; M | GL Specific MDS 3; M | +| Test purpose |

    Check that:

    PHG includes MDS object, System-Type-Spec-List attribute in transcoder output.

    [AND]

    System-Type-Spec-List is set to (MDC_DEV_SPEC_PROFILE_GLUCOSE, Version 2)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 3. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test.
    4. 4. Check in PHG transcoder output for the MDS object, System-Type-Spec-List attribute.
    | | | +| Pass/Fail criteria | In step 4, the MDS object, System-Type-Spec-List attribute is present and its value is (MDC_DEV_SPEC_PROFILE_GLUCOSE, Version 2). | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    System-Type-Spec-List attribute is present:

    | | | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Object: MDS object
    • Attribute-id: MDC_ATTR_SYS_TYPE_SPEC_LIST (2650)
    • Attribute-type: SEQUENCE OF [ {type (INT-U16), version (INT-U16)} ]
    • Attribute-value:
      • • type: MDC_DEV_SPEC_PROFILE_GLUCOSE or 4113 (dec) or 10 11 (hex)
      • • version: 2 (dec) or 00 02 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with System-Type-Spec-List attribute value (check OBX-5):

    OBX[?][NM][68186]^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a  528401^MDC_DEV_SPEC_PROFILE_GLUCOSE^MDC     R
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-003 | | | +| TP label | Whitepaper. Glucosemeter MDS Object - Reg-Cert-Data-List Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Common MDS 14; M | Regulatory Conv 1; M | +| Test purpose | Check that:

    PHG transcodes IEEE 11073-20601 Regulatory Certification Data List characteristic into MDS object, Reg-Cert-Data-List attribute | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. IEEE 11073-20601 Regulatory Certification Data List (0x2A2A)
        • • Format: reg-cert-data-list (opaque structure)
        • • Value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 11 02 02 00 02 80 00 (hex)
          • i. Element:
            • • auth-body-and-struc-type:
              • - auth-body: 02 (hex) auth-body-continua(2)
              • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
            • • auth-body-data:
              • - major-IG-version: 08 (hex)
              • - minor-IG-version: 00 (hex)
              • - certified-devices: 80 11 (hex). BLE Glucosemeter
          • ii. Element:
            • • auth-body-and-struc-type:
              • - auth-body: 02 (hex). auth-body-continua(2)
              • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
            • • auth-body-data:
              • - regulation-bit-field: 80 00 (hex). Unregulated device
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    simulated PHD and it starts a pairing process with the simulated PHD.

    1. 4. When the pairing has been completed (Connection state), force the PHG under test to read the IEEE 11073-20601 Regulatory Certification Data List characteristic.
    2. 5. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and simulated PHD sends the measurement to the PHG under test.
    3. 6. Check in PHG transcoder output for the MDS object, Reg-Cert-Data-List attribute.
    | +| Pass/Fail criteria | In step 6, the MDS object, Reg-Cert-Data-List attribute is present and its value matches with the IEEE 11073-20601 Regulatory Certification Data List characteristic value. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Reg-Cert-Data-List attribute is present:

    • Object: MDS object
    • Attribute-id: MDC_ATTR_REG_CERT_DATA_LIST (2635)
    • Attribute-type: SEQUENCE OF {[auth-body-and-struc-type, auth-body-data], {...}}
    • Attribute-value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 11 02 02 00 02 80 00 (hex) [Note that 0x00 0x02 is the number of elements in the sequence and 0x00 0x12 is the length of the sequence]
      • i. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex) auth-body-continua(2)
          • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
        • • auth-body-data:
          • - major-IG-version: 08 (hex)
          • - minor-IG-version: 00 (hex)
          • - certified-devices: 80 11 (hex). BLE Glucosemeter
      • ii. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex). auth-body-continua(2)
          • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
        • • auth-body-data:
          • - regulation-bit-field: 80 00 (hex). Unregulated device

    b) WAN PCD-01 message

    PCD-01 message includes five segments like these with Reg-Cert-Data-List attribute value (check OBX-5 in five segments):

    OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.a 2^auth-body-continua R

    OBX ? ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 1.0.0.a.x 6.1 R

    OBX ? NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 1.0.0.a.y 32785 R

    OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.b 2^auth-body-continua R

    OBX ? CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 1.0.0.b.z 1^unregulated-device(0) R

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-004 | | | +| TP label | Whitepaper. Glucosemeter Blood Glucose Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Blood Glucose object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Blood Glucose object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test.

    5. Check in PHG transcoder output for the Blood glucose object, Handle attribute.

    | +| Pass/Fail criteria | In step 5, the Blood glucose object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Blood glucose numeric object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Handle attribute value.

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-005 | | | +| TP label | Whitepaper. Glucosemeter Blood Glucose Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Blood Glucose object, Type attribute in transcoder output.

    [AND]

    Type is set to different values depending on Type field value

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Time Offset
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    v. Field: Glucose Concentration - units of kg/L

    • • Format: SFLOAT
    • • Value: Not relevant

    vi. Field: Glucose Concentration - units of mol/L

    • • This field is not included

    vii. Field: Type

    • • Format: nibble
    • • Value: Several values are checked in this test case

    viii. Field: Sample Location

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Sensor Status Annunciation

    • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the field Type set to Capillary Whole blood (0x01).
    3. 5. Check in PHG transcoder output for the Blood glucose object, Type.
    4. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with field Type set to Capillary Plasma (0x02).
    5. 7. Check in PHG transcoder output for the Blood glucose object, Type.
    6. 8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with field Type set to Venous Whole blood (0x03).
    7. 9. Check in PHG transcoder output for the Blood glucose object, Type.
    8. 10. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with field Type set to Venous Plasma (0x04).
    9. 11. Check in PHG transcoder output for the Blood glucose object, Type.
    10. 12. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with field Type set to Arterial Whole blood (0x05).
    11. 13. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the Check in PHG transcoder output for the Blood glucose object, Type.
    12. 14. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with field Type set to Arterial Plasma (0x06).
    13. 15. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the Check in PHG transcoder output for the Blood glucose object, Type.
    14. 16. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with field Type set to Undetermined
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Whole blood (0x07).

    17. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the Check in PHG transcoder output for the Blood glucose object, Type.

    18. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with field Type set to Undetermined Plasma (0x08).

    19. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the Check in PHG transcoder output for the Blood glucose object, Type.

    20. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with field Type set to Interstitial Fluid (ISF) (0x09).

    21. Check in PHG transcoder output for the Blood glucose object, Type.

    22. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with field Type set to Control Solution (0x0A).

    23. Check in PHG transcoder output for the Blood glucose object, Type.

    | +| Pass/Fail criteria |

    In step 5, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD}.

    In step 7, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_CAPILLARY_PLASMA}.

    In step 9, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_VENOUS_WHOLEBLOOD}.

    In step 11, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_VENOUS_PLASMA}.

    In step 13, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD}.

    In step 15, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_ARTERIAL_PLASMA}.

    In step 17, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD}.

    In step 19, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_UNDETERMINED_PLASMA}.

    In step 21, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_ISF}.

    In step 23, the Blood glucose object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_GLU_CONTROL}.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD or 29112 (dec) or 71 B8 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    | + +OBX[?][NM]160184^MDC\_CONC\_GLU\_CAPILLARY\_WHOLEBLOOD^MDC| +1.0.0.a|160|264274^MDC\_DIM\_MILLI\_G\_PER\_DL^MDC||||R||[current\_date\_time] + +In step 7, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Type attribute is present: + +- Object: Blood glucose object +- Attribute-id: MDC\_ATTR\_ID\_TYPE (2351) +- Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)} +- Attribute-value: + - partition: MDC\_PART\_SCADA or 2 (dec) or 00 02 (hex) + - code: MDC\_CONC\_GLU\_CAPILLARY\_PLASMA or 29116 (dec) or 71 BC (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Type attribute value (check OBX-3): + +OBX[?][NM]160188^MDC\_CONC\_GLU\_CAPILLARY\_PLASMA^MDC|1.0.0.a|160| +264274^MDC\_DIM\_MILLI\_G\_PER\_DL^MDC||||R||[current\_date\_time] + +In step 9, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Type attribute is present: + +- Object: Blood glucose object +- Attribute-id: MDC\_ATTR\_ID\_TYPE (2351) +- Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)} +- Attribute-value: + - partition: MDC\_PART\_SCADA or 2 (dec) or 00 02 (hex) + - code: MDC\_CONC\_GLU\_VENOUS\_WHOLEBLOOD or 29120 (dec) or 71 C0 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Type attribute value (check OBX-3): + +OBX[?][NM]160192^MDC\_CONC\_GLU\_VENOUS\_WHOLEBLOOD^MDC| +1.0.0.a|160|264274^MDC\_DIM\_MILLI\_G\_PER\_DL^MDC||||R||[current\_date\_time] + +In step 11, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Type attribute is present: + +- Object: Blood glucose object +- Attribute-id: MDC\_ATTR\_ID\_TYPE (2351) +- Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)} +- Attribute-value: + - partition: MDC\_PART\_SCADA or 2 (dec) or 00 02 (hex) + - code: MDC\_CONC\_GLU\_VENOUS\_PLASMA or 29124 (dec) or 71 C4 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Type attribute value (check OBX-3): + +OBX[?][NM]160196^MDC\_CONC\_GLU\_VENOUS\_PLASMA^MDC|1.0.0.a|160| +264274^MDC\_DIM\_MILLI\_G\_PER\_DL^MDC||||R||[current\_date\_time] + +In step 13, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Type attribute is present: + +- Object: Blood glucose object + +- Attribute-id: MDC\_ATTR\_ID\_TYPE (2351) +- Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)} +- Attribute-value: + - partition: MDC\_PART\_SCADA or 2 (dec) or 00 02 (hex) + - code: MDC\_CONC\_GLU\_ARTERIAL\_WHOLEBLOOD or 29128 (dec) or 71 C8 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Type attribute value (check OBX-3): + +OBX[?]|NM|160200^MDC\_CONC\_GLU\_ARTERIAL\_WHOLEBLOOD^MDC| +1.0.0.a|160|264274^MDC\_DIM\_MILLI\_G\_PER\_DL^MDC||||R||[current\_date\_time] + +In step 15, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Type attribute is present: + +- Object: Blood glucose object +- Attribute-id: MDC\_ATTR\_ID\_TYPE (2351) +- Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)} +- Attribute-value: + - partition: MDC\_PART\_SCADA or 2 (dec) or 00 02 (hex) + - code: MDC\_CONC\_GLU\_ARTERIAL\_PLASMA or 29132 (dec) or 71 CC (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Type attribute value (check OBX-3): + +OBX[?]|NM|160204^CONC\_GLU\_ARTERIAL\_PLASMA^MDC|1.0.0.a|160| +264274^MDC\_DIM\_MILLI\_G\_PER\_DL^MDC||||R||[current\_date\_time] + +In step 17, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Type attribute is present: + +- Object: Blood glucose object +- Attribute-id: MDC\_ATTR\_ID\_TYPE (2351) +- Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)} +- Attribute-value: + - partition: MDC\_PART\_SCADA or 2 (dec) or 00 02 (hex) + - code: MDC\_CONC\_GLU\_UNDETERMINED\_WHOLEBLOOD or 29292 (dec) or 72 6C (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Type attribute value (check OBX-3): + +OBX[?]|NM|160364^MDC\_CONC\_GLU\_UNDETERMINED\_WHOLEBLOOD +^MDC|1.0.0.a|160|264274^MDC\_DIM\_MILLI\_G\_PER\_DL +^MDC||||R||[current\_date\_time] + +In step 19, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Type attribute is present: + +- Object: Blood glucose object +- Attribute-id: MDC\_ATTR\_ID\_TYPE (2351) +- Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)} +- Attribute-value: + - partition: MDC\_PART\_SCADA or 2 (dec) or 00 02 (hex) + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • code: MDC_CONC_GLU_UNDETERMINED_PLASMA or 29296 (dec) or 72 70 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX[?][NM][160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC 1.0.0.a 160 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R  [current_date_time]

    In step 21, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_CONC_GLU_ISF or 29140 (dec) or 71 D4 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX[?][NM][160212^MDC_CONC_GLU_ISF^MDC 1.0.0.a 160 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R  [current_date_time]

    In step 23, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_CONC_GLU_CONTROL or 29136 (dec) or 71 D0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX[?][NM][160208^MDC_CONC_GLU_CONTROL^MDC 1.0.0.a 160 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R  [current_date_time]
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-006 | | | +| TP label | Whitepaper. Glucosimeter Blood Glucose Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Blood Glucose Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | +| Other PICS | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the Blood glucose numeric object, Metric-Spec-Small attribute.
    | +| Pass/Fail criteria | In step 5, the Blood glucose numeric object, Metric-Spec-Small attribute is present and its value is {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes

      Metric-Spec-Small attribute is present:

      • Object: Blood glucose numeric object
    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-007 | | | | +| TP label | Whitepaper. Glucosemeter Blood Glucose Object - Unit-Code Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 4; M | | | +| Test purpose |

    Check that:

    PHG includes Blood Glucose object, Unit-Code attribute in transcoder output.

    [AND]

    IF Glucose Concentration Value (kg/L) field of Glucose Measurement characteristic is present
    THEN Blood Glucose object, Unit-Code attribute is set to MDC_DIM_MILLI_G_PER_DL

    [AND]

    IF Glucose Concentration Value (mol/L or mmol/L) field of Glucose Measurement characteristic is present
    THEN Blood Glucose object, Unit-Code attribute is set to MDC_DIM_MILLI_MOLE_PER_L

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      • a. Glucose measurement (0x2A18)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:
      • a. Glucose measurement (0x2A18)
        • i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
        • ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        • iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
    | | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • iv. Field: Time Offset
      • • This field is not included
    • v. Field: Glucose Concentration - units of kg/L
      • • Format: SFLOAT
      • • Value: Not relevant
    • vi. Field: Glucose Concentration - units of mol/L
      • • This field is not included
    • vii. Field: Type
      • • Format: nibble
      • • Value: Undetermined Plasma (0x08)
    • viii. Field: Sample Location
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Sensor Status Annunciation
      • • This field is not included

    5. Check in PHG transcoder output for the Blood glucose object, Unit-Code attribute.

    6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:

    • a. Glucose measurement (0x2A18)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0110 (MSB → LSB). Glucose concentration in units of mol/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
      • ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      • iii. Field: Base Time
        • • Format: Date and Time
        • • Value: Not relevant
      • iv. Field: Time Offset
        • • This field is not included
      • v. Field: Glucose Concentration - units of kg/L
        • • This field is not included
      • vi. Field: Glucose Concentration - units of mol/L
        • • Format: SFLOAT
        • • Value: Not relevant
      • vii. Field: Type
        • • Format: nibble
        • • Value: Undetermined Plasma (0x08)
      • viii. Field: Sample Location
        • • Format: nibble
        • • Value: Not relevant
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    ix. Field: Sensor Status Annunciation

    • • This field is not included

    7. Check in PHG transcoder output for the Blood glucose object, Unit-Code attribute.

    | +| Pass/Fail criteria |

    In step 5, the Blood glucose object, Unit-Code attribute is present and its value is MDC_DIM_MILLI_G_PER_DL.

    In step 7, the Blood glucose object, Unit-Code attribute is present and its value is MDC_DIM_MILLI_MOLE_PER_L.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • ❑ Object: Blood glucose object
    • ❑ Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • ❑ Attribute-type: INT-U16
    • ❑ Attribute-value: MDC_DIM_MILLI_G_PER_DL or 2130 (dec) or 08 52 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX ? NM 160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC  1.0.0.a 160 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R  [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • ❑ Object: Blood glucose object
    • ❑ Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • ❑ Attribute-type: INT-U16
    • ❑ Attribute-value: MDC_DIM_MILLI_MOLE_PER_L or 4722 (dec) or 12 72 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX ? NM 160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC 1.0.0.a 9 266866^MDC_DIM_MILLI_MOLE_PER_L^MDC    R  [current_date_time]
    | + +| | | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-008 | | | | +| TP label | Whitepaper. Glucosimeter Blood Glucose Object - Absolute-Time-Stamp Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 5; M | Date-Time Conv 2; M | Date-Time Conv 3; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | | +| Test purpose |

    Check that:

    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into Blood Glucose Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00000011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location and Time Offset fields are included, Sensor Status Annunciation field is not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:59:27
        4. iv. Field: Time Offset
          • • Format: sint16
          • • Value: 120 minutes
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Undetermined Plasma (0x08)
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
    5. 5. Check in PHG transcoder output for the Blood glucose object, Absolute-Time-Stamp attribute.
    | +| Pass/Fail criteria | In step 5, the Blood glucose object, Absolute-Time-Stamp attribute is present, its value matches with the Base Time field in conjunction with the Time Offset and a fraction of seconds which is set to 0. | +| Notes | Possible values in typical points of observation after transcoder output are: | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 12 (hex) or 18 (dec)
      • • minute: 59 (hex) or 89 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b. WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX ? NM 160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC  1.0.0.a 160 264274^MDC_DIM_MILLI_G_PER_DL^MDC   R   20120802125927+0000
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-009 | | | +| TP label | Whitepaper. Glucosometer Blood Glucose Object - Basic-Nu-Observed-Value Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 6; M | Short Float Type 1; C | +| Test purpose | Check that:
    PHG transcodes Glucose Concentration Value field of Glucose Measurement characteristic into Blood Glucose Object - Basic-Nu-Observed-Value attribute | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
    | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
      • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Base Time
      • i. Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Time Offset
      • • This field is not included
    • v. Field: Glucose Concentration - units of kg/L
      • • Format: SFLOAT
      • • Value: 0.0016 kg/L (160 mg/dL)
    • vi. Field: Glucose Concentration - units of mol/L
      • • This field is not included
    • vii. Field: Type
      • • Format: nibble
      • • Value: Undetermined Plasma (0x08)
    • viii. Field: Sample Location
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Sensor Status Annunciation
      • • This field is not included

    5. Check in PHG transcoder output for the Blood glucose object– Basic-Nu-Observed-Value attribute.

    6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:

    • a. Glucose measurement (0x2A18)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 00000110 (MSB → LSB). Glucose concentration units of mol/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
      • ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      • iii. Field: Base Time
        • • Format: Date and Time
        • • Value: Not relevant
      • iv. Field: Time Offset
        • • This field is not included
      • v. Field: Glucose Concentration - units of kg/L
        • • This field is not included
      • vi. Field: Glucose Concentration - units of mol/L
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: SFLOAT
    • • Value: Value: 0.009 mol/L (9 mmol/L)

    vii. Field: Type

    • • Format: nibble
    • • Value: Undetermined Plasma (0x08)

    viii. Field: Sample Location

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Sensor Status Annunciation

    • • This field is not included

    7. Check in PHG transcoder output for the Blood glucose object, Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the Blood glucose object, Basic-Nu-Observed-Value attribute is present and its value matches with the Glucose measurement value (kg/L) field of the Glucose measurement characteristic: 0.0016 kg/L (160 mg/dL).

    In step 7, the Blood glucose object, Basic-Nu-Observed-Value attribute is present and its value matches with the Glucose Measurement Value (mol/L) field of the Glucose Measurement characteristic: 0.009 mol/L (9 mmol/L).

    | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: F6 40 (hex) or 160 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC
    1.0.0.a 160.0 264274^MDC_DIM_MILLI_G_PER_DL^MDC R [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: E3 84 (hex) or 9 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Basic -Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC
    1.0.0.a 9.0 266866^MDC_DIM_MILLI_MOLE_PER_L^MDC R [current_date_time]

    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-010 | | | +| TP label | Whitepaper. Glucosemeter Blood Glucose Object - Basic-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 6; M | Short Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Glucose Concentration field of Glucose Measurement characteristic into Blood Glucose object, Basic-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x07FF), NRes (0x0800), +INFINITY (0x07FE) and -INFINITY (0x0802)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: 0.0016 kg/L (160 mg/dL)
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Undetermined Plasma (0x08)
    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • viii. Field: Sample Location
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Sensor Status Annunciation
      • • This field is not included

    5. Check in PHG transcoder output for the Blood glucose object, Basic-Nu-Observed-Value attribute.

    6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:

    1. a. Glucose measurement (0x2A18)
      1. i. Field: Flags
        • • Format: 8 bit
        • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
      2. ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      3. iii. Field: Base Time
        • • Format: Date and Time
        • • Value: Not relevant
      4. iv. Field: Time Offset
        • • This field is not included
      5. v. Field: Glucose Concentration - units of kg/L
        • • Format: SFLOAT
        • • Value: 07 FF(hex). Special value: NaN
      6. vi. Field: Glucose Concentration - units of mol/L
        • • This field is not included
      7. vii. Field: Type
        • • Format: nibble
        • • Value: Undetermined Plasma (0x08)
      8. viii. Field: Sample Location
        • • Format: nibble
        • • Value: Not relevant
      9. ix. Field: Sensor Status Annunciation
        • • This field is not included

    7. Check in PHG transcoder output for the Blood glucose object, Basic-Nu-Observed-Value attribute.

    8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:

    1. a. Glucose measurement (0x2A18)
      1. i. Field: Flags
        • • Format: 8 bit
        • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L,
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included

    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Base Time
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Time Offset
      • • This field is not included
    • v. Field: Glucose Concentration - units of kg/
      • • Format: SFLOAT
      • • Value: 00 80 (hex). Special value: NRes
    • vi. Field: Glucose Concentration - units of mol/L
      • • This field is not included
    • vii. Field: Type
      • • Format: nibble
      • • Value: Undetermined Plasma (0x08)
    • viii. Field: Sample Location
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Sensor Status Annunciation
      • • This field is not included

    9. Check in PHG transcoder output for the Blood glucose object, Basic-Nu-Observed-Value attribute.

    10. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:

    • a. Glucose measurement (0x2A18)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
      • ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      • iii. Field: Base Time
        • • Format: Date and Time
        • • Value: Not relevant
      • iv. Field: Time Offset
        • • This field is not included
      • v. Field: Glucose Concentration - units of kg/L
        • • Format: SFLOAT
        • • Value: 07 FE (hex). Special value: +INFINITY
      • vi. Field: Glucose Concentration - units of mol/L
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    vii. Field: Type

    • • Format: nibble
    • • Value: Undetermined Plasma (0x08)

    viii. Field: Sample Location

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Sensor Status Annunciation

    • • This field is not included

    11. Check in PHG transcoder output for the Blood glucose object, Basic-Nu-Observed-Value attribute.

    12. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:

    a. Glucose measurement (0x2A18)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included

    ii. Field: Sequence number

    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Base Time

    • • Format: Date and Time
    • • Value: Not relevant

    iv. Field: Time Offset

    • • This field is not included

    v. Field: Glucose Concentration - units of kg/L

    • • Format: SFLOAT
    • • Value: 08 02 (hex). Special value: -INFINITY

    vi. Field: Glucose Concentration - units of mol/L

    • • This field is not included

    vii. Field: Type

    • • Format: nibble
    • • Value: Undetermined Plasma (0x08)

    viii. Field: Sample Location

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Sensor Status Annunciation

    • • This field is not included

    13. Check in PHG transcoder output for the Blood glucose object, Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the Blood glucose object, Basic-Nu-Observed-Value attribute is present and its value is 0.0016 kg/L (160 mg/dL).

    In step 7, the Blood glucose object, Basic-Nu-Observed-Value attribute is present and its

    | + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    value is 0x07FF.

    In step 9, the Blood glucose object, Basic -Nu-Observed-Value attribute is present and its value is 0x0800.

    In step 11, the Blood glucose object, Basic -Nu-Observed-Value attribute is present and its value is 0x07FE.

    In step 13, the Blood glucose object, Basic -Nu-Observed-Value attribute is present and its value is 0x0802.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: F6 40 (hex) or 160 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC 
    1.0.0.a 160.0 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC     R   [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 07 FF(hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 08 00 (hex) or NRes (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 11, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: Blood glucose object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-value: 07 FE (hex) or +INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 13, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    Object: Blood glucose object

    Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)

    Attribute-type: SFLOAT

    Attribute-value: 08 02 (hex) or -INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC) because it has a special value and these values are not included in the PCD-01 message.

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-011 | | | +| TP label | Whitepaper. Glucosemeter measurement value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 5; M | GL Numeric 6; M | +| | | Date-Time Conv 1; M | Short Float Type 1; C | +| Test purpose |

    Check that:

    PHG processes correctly the Glucose Measurement Value (kg/L), Glucose Measurement Value (mol/L) and Base Time fields of Glucose Measurement characteristic

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset and Sensor Status Annunciation fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
    | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • iii. Field: Base Time
      • • Format: Date and Time
      • • Value: August 2nd, 2012, 11:08:25
    • iv. Field: Time Offset
      • • This field is not included
    • v. Field: Glucose Concentration - units of kg/L
      • • Format: SFLOAT
      • • Value: 0.0016 kg/L (160 mg/dL)
    • vi. Field: Glucose Concentration - units of mol/L
      • • This field is not included
    • vii. Field: Type
      • • Format: nibble
      • • Value: Not relevant
    • viii. Field: Sample Location
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Sensor Status Annunciation
      • • This field is not included

    5. Check that the PHG under test accepts the measurement and decodes its value properly (glucose measurement value, glucose units and base time).

    6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:

    • a. Glucose measurement (0x2A18)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 00000111 (MSB → LSB). Glucose concentration in units of mol/L Type and Sample Location and Time Offset fields are included, Sensor Status Annunciation field is not included
      • ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      • iii. Field: Base Time
        • • Format: Date and Time
        • • Value: August 2nd, 2012, 11:09:05
      • iv. Field: Time Offset
        • • Format: sint16
        • • Value: 120 minutes
      • v. Field: Glucose Concentration - units of kg/L
        • • This field is not included
      • vi. Field: Glucose Concentration - units of mol/L
        • • Format: SFLOAT
        • • Value: Value: 0.009 mol/L (9 mmol/L)
      • vii. Field: Type
        • • Format: nibble
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Value: Undetermined Plasma (0x08)
    viii. Field: Sample Location
    • Format: nibble
    • Value: Not relevant
    ix. Field: Sensor Status Annunciation
    • This field is not included
    7. Check that the PHG under test accepts the measurement and decodes its value properly (glucose measurement value, glucose units and base time). | +| Pass/Fail criteria |

    In step 5, the PHG under test shows the following glucose measurement 160.0 mg/dL with the time stamp '2012-08-02 11:08:25'.

    In step 7, the PHG under test shows the following glucose measurement 9.0 mmol/L with the time stamp '2012-08-02 13:09:05'.

    | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-012 | | | +| TP label | Whitepaper. Glucosemeter HbA1c Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 7; O | | +| Test purpose | Check that:
    PHG does not include HbA1c object, Handle Attribute in transcoder output
    [OR]
    If PHG includes HbA1c object, Handle attribute in transcoder output, then its value shall be different than 0 | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_008 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
    a. Glucose measurement context (0x2A34)
    • i. Field: Flags
      • Format: 8 bit
      • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
    • ii. Field: Sequence number
      • Format: uint16
      • Value: Not relevant
    • iii. Field: Extended Flags
      • This field is not included
    • iv. Field: Carbohydrate ID
      • This field is not included
    • v. Field: Carbohydrate
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included
    vi. Field: Meal
    • • This field is not included
    vii. Field: Tester
    • • This field is not included
    viii. Field: Health
    • • This field is not included
    ix. Field: Exercise Duration
    • • This field is not included
    x. Field: Exercise Intensity
    • • This field is not included
    xi. Field: Medication ID
    • • This field is not included
    xii. Field: Medication
    • • This field is not included
    xiii. Field: HbA1c
    • • Format: SFLOAT
    • • Value: Not relevant
    | +| | 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.
    5. Check in PHG transcoder output for the HbA1c object, Handle attribute. | +| Pass/Fail criteria | In step 5, the HbA1c object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Handle attribute is not present, or if it is present then:
    • Object: HbA1c numeric object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0
    b) WAN PCD-01 message
    PCD-01 message does not include segments with a Handle attribute value. | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-013 | | | +| TP label | Whitepaper. Glucosemeter HbA1c Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 8; M | | +| Test purpose | Check that:
    PHG includes HbA1c object, Type attribute in transcoder output.
    [AND] | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Type is set to { MDC_PART_SCADA MDC_CONC_HBA1C } | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_008 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Field: Medication
          • • This field is not included
        13. xiii. Field: HbA1c
          • • Format: SFLOAT
          • • Value: Not relevant
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the HbA1c object, Type attribute.

    | +| Pass/Fail criteria | In step 5, the HbA1c object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_CONC_HBA1C}. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: HbA1c object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_CONC_HBA1C or 29148 (dec) or 71 DC (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX[?][NM][160220^MDC_CONC_HBA1C^MDC 1.0.0.a 5.1  262688^MDC_DIM_PERCENT^MDC     R  [current_date_time]
    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-014 | | | +| TP label | Whitepaper. Glucosemeter HbA1c Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 8a; M | | +| Test purpose |

    Check that:

    PHG includes HbA1c Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_008 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Field: Medication

    • • This field is not included

    xiii. Field: HbA1c

    • • Format: SFLOAT
    • • Value: Not relevant

    4. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    5. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    6. Check in PHG transcoder output for the HbA1c numeric object, Metric-Spec-Small attribute.

    | +| Pass/Fail criteria | In step 5, the HbA1c numeric object, Metric-Spec-Small attribute is present and its value is {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: HbA1c numeric object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 48 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-manual(12) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-015 | | | +| TP label | Whitepaper. Glucosemeter HbA1c Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 9; M | | +| Test purpose | Check that:
    PHG includes HbA1c object, Unit-Code attribute in transcoder output.
    [AND]
    HbA1c object, Unit-Code attribute is set to MDC_DIM_PERCENT | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_008 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
      • This field is not included
    • x. Field: Exercise Intensity
      • This field is not included
    • xi. Field: Medication ID
      • This field is not included
    • xii. Field: Medication
      • This field is not included
    • xiii. Field: HbA1c
      • Format: SFLOAT
      • Value: Not relevant
    5. Check in PHG transcoder output for the HbA1c object, Unit-Code attribute. | +| Pass/Fail criteria | In step 5, the HbA1c object, Unit-Code attribute is present and its value is MDC_DIM_PERCENT. | +| Notes | In step 5, possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Unit-Code attribute is present:
    Object: HbA1c object
    Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    Attribute-type: INT-U16
    Attribute-value: MDC_DIM_PERCENT or 544 (dec) or 02 20 (hex)
    b) WAN PCD-01 message
    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):
    OBX ? NM 160220^MDC_CONC_HBA1C^MDC 1.0.0.a 5.1  262688^MDC_DIM_PERCENT^MDC    R   [current_date_time]
    | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-016 | | | | +| TP label | Whitepaper. Glucosemeter HbA1c Object - Absolute-Time-Stamp Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 10; M | Date-Time Conv 2; M | Date-Time Conv 3; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | | +| Test purpose | Check that:
    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into HbA1c Object - Absolute-Time-Stamp attribute
    [AND]
    PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format
    [AND]
    The fraction of seconds in Absolute Time at transcoder output is 0 | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_008 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure | 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristics of | | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    interest for this test case are:

    1. a. Glucose measurement (0x2A18)
    2. b. Glucose measurement context (0x2A34)
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location and Time Offset fields are included. Sensor Status Annunciation field is not included and Context Information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:59:27
        4. iv. Field: Time Offset
          • • Format: sint16
          • • Value: 120 minutes
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • This field is not included
        8. viii. Field: Sample Location
          • • This field is not included
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
      2. b. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Field: Medication

    • • This field is not included

    xiii. Field: HbA1c

    • • Format: SFLOAT
    • • Value: Not relevant

    5. Check in PHG transcoder output for the HbA1c object, Absolute-Time-Stamp attribute.

    | +| Pass/Fail criteria | In step 5, the HbA1c object, Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field in conjunction with the Time Offset field of the Glucose measurement characteristic and the fraction of seconds is set to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: HbA1c object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 12 (hex) or 18 (dec)
      • • minute: 59 (hex) or 89 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value

    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------| +| | (check OBX-14):
    OBX[?][NM][160220]^MDC_CONC_HBA1C^MDC[1.0.0.a[5.1]
    262688^MDC_DIM_PERCENT^MDC[ R 20120802125927+0000 | +|--|--------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-017 | | | | +| TP label | Whitepaper. Glucosemeter HbA1c Object - Basic-Nu-Observed-Value Attribute 1 | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 11; M | Short Float Type 1; C | | +| Test purpose | Check that:

    PHG transcodes HbA1c field of Glucose Measurement Context characteristic into HbA1c Object - Basic-Nu-Observed-Value attribute | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_008 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included
    ix. Field: Exercise Duration
    • • This field is not included
    x. Field: Exercise Intensity
    • • This field is not included
    xi. Field: Medication ID
    • • This field is not included
    xii. Field: Medication
    • • This field is not included
    xiii. Field: HbA1c
    • • Format: SFLOAT
    • • Value: 5.1 %
    5. Check in PHG transcoder output for the HbA1c object– Basic-Nu-Observed-Value attribute. | +| Pass/Fail criteria | In step 5, the HbA1c object, Basic-Nu-Observed-Value attribute is present and its value matches with the HbA1c Value field of Glucose measurement context characteristic: 5.1 %. | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Basic-Nu-Observed-Value attribute is present:
    Object: HbA1c object
    Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    Attribute-type: SFLOAT
    Attribute-value: F0 33 (hex) or E1 FE (hex) or 5.1 (dec)
    b) WAN PCD-01 message
    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 160220^MDC_CONC_HBA1C^MDC 1.0.0.a 5.1
    262688^MDC_DIM_PERCENT^MDC R [current_date_time]

    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-018 | | | +| TP label | Whitepaper. Glucosemeter HbA1c Object - Basic-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 11; M | Short Float Type 1; C | +| Test purpose | Check that:
    PHG transcodes HbA1c field of Glucose Measurement Context characteristic into HbA1c object, Basic-Nu-Observed-Value attribute
    [AND]
    PHG assigns the following special values: NaN (0x07FF), NRes (0x0800), +INFINITY (0x07FE) and -INFINITY (0x0802) | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_008 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristic of | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    interest for this test case is:

    1. a. Glucose measurement context (0x2A34)
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          1. • Format: 8 bit
          2. • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
        2. ii. Field: Sequence number
          1. • Format: uint16
          2. • Value: Not relevant
        3. iii. Field: Extended Flags
          1. • This field is not included
        4. iv. Field: Carbohydrate ID
          1. • This field is not included
        5. v. Field: Carbohydrate
          1. • This field is not included
        6. vi. Field: Meal
          1. • This field is not included
        7. vii. Field: Tester
          1. • This field is not included
        8. viii. Field: Health
          1. • This field is not included
        9. ix. Field: Exercise Duration
          1. • This field is not included
        10. x. Field: Exercise Intensity
          1. • This field is not included
        11. xi. Field: Medication ID
          1. • This field is not included
        12. xii. Field: Medication
          1. • This field is not included
        13. xiii. Field: HbA1c
          1. • Format: SFLOAT
          2. • Value: 5.1 %
    3. 5. Check in PHG transcoder output for the HbA1c object, Basic-Nu-Observed-Value attribute.
    4. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. a. Glucose measurement context (0x2A34)
      1. i. Field: Flags
        • • Format: 8 bit
        • • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
      2. ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      3. iii. Field: Extended Flags
        • • This field is not included
      4. iv. Field: Carbohydrate ID
        • • This field is not included
      5. v. Field: Carbohydrate
        • • This field is not included
      6. vi. Field: Meal
        • • This field is not included
      7. vii. Field: Tester
        • • This field is not included
      8. viii. Field: Health
        • • This field is not included
      9. ix. Field: Exercise Duration
        • • This field is not included
      10. x. Field: Exercise Intensity
        • • This field is not included
      11. xi. Field: Medication ID
        • • This field is not included
      12. xii. Field: Medication
        • • This field is not included
      13. xiii. Field: HbA1c
        • • Format: SFLOAT
        • • Value: 07 FF(hex). Special value: NaN
    2. 7. Check in PHG transcoder output for the HbA1c object, Basic-Nu-Observed-Value attribute.
    3. 8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
        2. ii. Field: Sequence number
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Field: Medication

    • • This field is not included

    xiii. Field: HbA1c

    • • Format: SFLOAT
    • • Value: 00 80 (hex). Special value: NRes

    9. Check in PHG transcoder output for the HbA1c object, Basic-Nu-Observed-Value attribute.

    10. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:

    a. Glucose measurement context (0x2A34)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included

    ii. Field: Sequence number

    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included
    1. vi. Field: Meal
      • • This field is not included
    2. vii. Field: Tester
      • • This field is not included
    3. viii. Field: Health
      • • This field is not included
    4. ix. Field: Exercise Duration
      • • This field is not included
    5. x. Field: Exercise Intensity
      • • This field is not included
    6. xi. Field: Medication ID
      • • This field is not included
    7. xii. Field: Medication
      • • This field is not included
    8. xiii. Field: HbA1c
      • • Format: SFLOAT
      • • Value: 07 FE (hex). Special value: +INFINITY

    11. Check in PHG transcoder output for the HbA1c object, Basic-Nu-Observed-Value attribute.

    12. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:

    1. a. Glucose measurement context (0x2A34)
      1. i. Field: Flags
        • • Format: 8 bit
        • • Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included
      2. ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      3. iii. Field: Extended Flags
        • • This field is not included
      4. iv. Field: Carbohydrate ID
        • • This field is not included
      5. v. Field: Carbohydrate
        • • This field is not included
      6. vi. Field: Meal
        • • This field is not included
      7. vii. Field: Tester
        • • This field is not included
      8. viii. Field: Health
        • • This field is not included
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • This field is not included
    • xii. Field: Medication
      • • This field is not included
    • xiii. Field: HbA1c
      • • Format: SFLOAT
      • • Value: 08 02 (hex). Special value: -INFINITY

    13. Check in PHG transcoder output for the HbA1c object, Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the HbA1c object, Basic-Nu-Observed-Value attribute is present and its value is 5.1 %.

    In step 7, the HbA1c object, Basic -Nu-Observed-Value attribute is present and its value is 0x07FF.

    In step 9, the HbA1c object, Basic -Nu-Observed-Value attribute is present and its value is 0x0800.

    In step 11, the HbA1c object, Basic -Nu-Observed-Value attribute is present and its value is 0x07FE.

    In step 13, the HbA1c object, Basic -Nu-Observed-Value attribute is present and its value is 0x0802.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: HbA1c object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: F0 33 (hex) or E1 FE (hex) or 5.1 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 160220^MDC_CONC_HBA1C^MDC 1.0.0.a 5.1 262688 ^MDC_DIM_PERCENT^MDC     R   [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: HbA1c object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 07 FF(hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (160220^MDC_CONC_HBA1C^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 9, possible values in typical points of observation after transcoder output are:

    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: HbA1c object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 08 00 (hex) or NRes (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (160220^MDC_CONC_HBA1C^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 11, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: HbA1c object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 07 FE (hex) or +INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (160220^MDC_CONC_HBA1C^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 13, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: HbA1c object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 08 02 (hex) or -INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (160220^MDC_CONC_HBA1C^MDC) because it has a special value and these values are not included in the PCD-01 message.

    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-019 | | | +| TP label | Whitepaper. Glucosemeter HbA1c value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 10; M | GL Numeric 11; M | +| | | Date-Time Conv 1; M | Short Float Type 1; C | +| Test purpose |

    Check that:

    PHG processes correctly the HbA1c Value (%) and Base Time fields of Glucose Measurement Context characteristic

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 AND C_MAN_BLE_008 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    | | | + +2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: + - a. Glucose measurement (0x2A18) + - b. Glucose measurement context (0x2A34) +3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state). +4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are: + - a. Glucose measurement (0x2A18) + - i. Field: Flags + - Format: 8 bit + - Value: 00010010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset fields and Sensor Status Annunciation field are not included and Context Information follows + - ii. Field: Sequence number + - Format: uint16 + - Value: Not relevant + - iii. Field: Base Time + - Format: Date and Time + - Value: August 2nd, 2012, 11:08:25 + - iv. Field: Time Offset + - This field is not included + - v. Field: Glucose Concentration - units of kg/L + - Format: SFLOAT + - Value: Not relevant + - vi. Field: Glucose Concentration - units of mol/L + - This field is not included + - vii. Field: Type + - Format: nibble + - Value: Not relevant + - viii. Field: Sample Location + - Format: nibble + - Value: Not relevant + - ix. Field: Sensor Status Annunciation + - This field is not included + - b. Glucose measurement context (0x2A34) + - i. Field: Flags + - Format: 8 bit + - Value: 0100 0000 (MSB → LSB). HbA1c field is included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and Extended Flags fields are not included + - ii. Field: Sequence number + - Format: uint16 + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Field: Medication

    • • This field is not included

    xiii. Field: HbA1c

    • • Format: SFLOAT
    • • Value: 5.1 %

    5. Check that the PHG accepts the measurement and decodes its value properly (HbA1c value, HbA1c units and base time).

    | +| Pass/Fail criteria | In step 5, the PHG under test shows the following HbA1c 5.1 % with the time stamp '2012-08-02 11:08:25'. | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-020 | | | +| TP label | Whitepaper. Glucosemeter Context Exercise Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 12; O | | +| Test purpose | Check that:
    PHG does not include Context Exercise object, Handle Attribute in transcoder output
    [OR]
    If PHG includes Context Exercise object, Handle attribute in transcoder output, then its value shall be different than 0 | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_009 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    1. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Exercise Duration And Exercise Intensity fields are included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • Format: uint16
          • • Value: Not relevant
        10. x. Field: Exercise Intensity
          • • Format: uint8
          • • Value: Not relevant
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Field: Medication
          • • This field is not included
        13. xiii. Field: HbA1c
          • • This field is not included
    2. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.
    4. 5. Check in PHG transcoder output for the Context exercise object, Handle attribute.
    | +| Pass/Fail criteria | In step 5, the Context exercise object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes | Possible values in typical points of observation after transcoder output are: | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Context exercise numeric object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Handle attribute value.

    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-021 | | +| TP label | Whitepaper. Glucosemeter Context Exercise Object - Type Attribute | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | +| | Testable items | GL Numeric 13; M | +| Test purpose |

    Check that:

    PHG includes Context Exercise object, Type attribute in transcoder output.

    [AND]

    Type is set to { MDC_PART_PHD_DM MDC_CTXT_GLU_EXERCISE }

    | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_009 | | +| Other PICS | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Exercise Duration And Exercise Intensity fields are included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
    | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    ix. Field: Exercise Duration

    • • Format: uint16
    • • Value: Not relevant

    x. Field: Exercise Intensity

    • • Format: uint8
    • • Value: Not relevant

    xi. Field: Medication ID

    • • This field is not included

    xii. Field: Medication

    • • This field is not included

    xiii. Field: HbA1c

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context exercise object, Type attribute.

    | +| Pass/Fail criteria | In step 5, the Context exercise object, Type attribute is present and its value is { MDC_PART_PHD_DM MDC_CTXT_GLU_EXERCISE }. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Context exercise object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_EXERCISE or 29152 (dec) or 71 E0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX[?][NM]8417760^MDC_CTXT_GLU_EXERCISE^MDC 1.0.0.a 33  262688^MDC_DIM_PERCENT^MDC   R   [current_date_time]
    | + +| | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-022 | | +| TP label | Whitepaper. Glucosimeter Context Exercise Object - Metric-Spec-Small Attribute | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | +| | Testable items | GL Numeric 13a; M | +| Test purpose |

    Check that:

    PHG includes Context Exercise Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-

    | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_009 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Exercise Duration And Exercise Intensity fields are included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • Format: uint16
          • • Value: Not relevant
        10. x. Field: Exercise Intensity
          • • Format: uint8
          • • Value: Not relevant
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Field: Medication
          • • This field is not included
        13. xiii. Field: HbA1c
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose
    | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context exercise numeric object, Metric-Spec-Small attribute.

    | +| Pass/Fail criteria | In step 5, the Context exercise numeric object, Metric-Spec-Small attribute is present and its value is {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Context exercise numeric object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 48 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-manual(12) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-023 | | | +| TP label | Whitepaper. Glucosemeter Context Exercise Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 14; M | | +| Test purpose |

    Check that:

    PHG includes Context Exercise object, Unit-Code attribute in transcoder output.

    [AND]

    Context Exercise object, Unit-Code attribute is set to MDC_DIM_PERCENT

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_009 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Exercise Duration And Exercise Intensity fields are included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • Format: uint16
    • • Value: Not relevant

    x. Field: Exercise Intensity

    • • Format: uint8
    • • Value: Not relevant

    xi. Field: Medication ID

    • • This field is not included

    xii. Field: Medication

    • • This field is not included

    xiii. Field: HbA1c

    • • This field is not included

    5. Check in PHG transcoder output for the Context exercise object, Unit-Code attribute.

    | +| Pass/Fail criteria | In step 5, the Context exercise object, Unit-Code attribute is present and its value is MDC_DIM_PERCENT. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Context exercise object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_PERCENT or 544 (dec) or 02 20 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?][NM][8417760^MDC_CTXT_GLU_EXERCISE^MDC 1.0.0.a 33  262688^MDC_DIM_PERCENT^MDC   R  [current_date_time]
    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-024 | | | +| TP label | Whitepaper. Glucosemeter Context Exercise Object - Absolute-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 15; M | Date-Time Conv 2; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | +| Test purpose |

    Check that:

    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into Context Exercise Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_009 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location and Time Offset fields are included. Sensor Status Annunciation field is not included and Context Information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:59:27
        4. iv. Field: Time Offset
          • • Format: sint16
          • • Value: 120 minutes
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vi. Field: Glucose Concentration - units of mol/L

    • • This field is not included

    vii. Field: Type

    • • This field is not included

    viii. Field: Sample Location

    • • This field is not included

    ix. Field: Sensor Status Annunciation

    • • This field is not included

    b. Glucose measurement context (0x2A34)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0000 1000 (MSB → LSB). Exercise Duration And Exercise Intensity fields are included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Medication ID, Medication Value, Hb1Ac, and Extended Flags fields are not included

    ii. Field: Sequence number

    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • Format: uint16
    • • Value: Not relevant

    x. Field: Exercise Intensity

    • • Format: uint8
    • • Value: Not relevant

    xi. Field: Medication ID

    • • This field is not included

    xii. Field: Medication

    • • This field is not included

    xiii. Field: HbA1c

    • • This field is not included

    5. Check in PHG transcoder output for the Context exercise object, Absolute-Time-Stamp attribute.

    | +| Pass/Fail criteria | In step 6, the Context exercise object, Absolute-Time-Stamp attribute is present, its value | + +| | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | matches with the Time Stamp field in conjunction with the Time Offset field of the Glucose measurement characteristic and the fraction of seconds is set to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Context exercise object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 12 (hex) or 18 (dec)
      • • minute: 59 (hex) or 89 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX[?][NM][8417760^MDC_CTXT_GLU_EXERCISE^MDC 1.0.0.a 33 262688
    ^MDC_DIM_PERCENT^MDC R 20120802125927+0000

    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-025 | | | +| TP label | Whitepaper. Glucosemeter Context Exercise Object - Measure-Active-Period Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 16; M | | +| Test purpose |

    Check that:

    PHG transcodes Exercise Duration value field of Glucose Measurement Context characteristic into Context Exercise Object - Measure-Active-Period attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_009 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. Glucose measurement context (0x2A34)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 1000 (MSB → LSB). Exercise Duration And Exercise Intensity fields are included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Medication ID, Medication Value and HbA1c fields are not included
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate
      • • This field is not included
    • vi. Field: Meal
      • • This field is not included
    • vii. Field: Tester
      • • This field is not included
    • viii. Field: Health
      • • This field is not included
    • ix. Field: Exercise Duration
      • • Format: uint16
      • • Value: 666 seconds
    • x. Field: Exercise Intensity
      • • Format: uint8
      • • Value: Not relevant
    • xi. Field: Medication ID
      • • This field is not included
    • xii. Field: Medication
      • • This field is not included
    • xiii. Field: HbA1c
      • • This field is not included

    5. Check in PHG transcoder output for the Context exercise object, Measure-Active-Period attribute.

    | +| Pass/Fail criteria | In step 5, the Context exercise object, Measure-Active-Period attribute is present and its value is 666 seconds. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Measure-Active-Period attribute is present:

    • Object: Context exercise object
    • Attribute-id: MDC_ATTR_TIME_PD_MSMT_ACTIVE (2649)
    • Attribute-type: FLOAT
    • Attribute-value: 666 (dec) or 0000029A (hex) [Note that exponent value for this FLOAT value must be 0]
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these, one of them with a Measure-Active-Period attribute value (check OBX-5 in MDC_ATTR_TIME_PD_MSMT_ACTIVE segment):

    OBX[?][NM][8417760^MDC_CTXT_GLU_EXERCISE^MDC 1.0.0.a 33 262688^MDC_DIM_PERCENT^MDC    R  [current_date_time]
    OBX[?][NM][68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC 1.0.0.a.b 666.0 264320^MDC_DIM_SEC^MDC    R
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-026 | | | +| TP label | Whitepaper. Glucosemeter Context Exercise Object - Basic-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 17; M | Short Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Exercise Intensity value field of Glucose Measurement Context characteristic into Context Exercise Object - Basic-Nu-Observed-Value attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_009 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Exercise Duration And Exercise Intensity fields are included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included
    viii. Field: Health
    • • This field is not included
    ix. Field: Exercise Duration
    • • Format: uint16
    • • Value: Not relevant
    x. Field: Exercise Intensity
    • • Format: uint8
    • • Value: 33%
    xi. Field: Medication ID
    • • This field is not included
    xii. Field: Medication
    • • This field is not included
    xiii. Field: HbA1c
    • • This field is not included
    5. Check in PHG transcoder output for the Context exercise object– Basic-Nu-Observed-Value attribute. | +| Pass/Fail criteria | In step 5, the Context exercise object, Basic-Nu-Observed-Value attribute is present and its value matches with the Exercise Intensity Value field of Glucose measurement context characteristic: 33%. | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Basic-Nu-Observed-Value attribute is present:
    • Object: Context exercise object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 33 (dec) or 00000021 (hex) [Note that exponent value for this FLOAT value must be 0]
    b) WAN PCD-01 message
    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 8417760^MDC_CTXT_GLU_EXERCISE^MDC 1.0.0.a 33.0 262688
    ^MDC_DIM_PERCENT^MDC R [current_date_time]

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-027 | | | +| TP label | Whitepaper. Glucosemeter Context Exercise value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 15; M | GL Numeric 17; M | +| | | Date-Time Conv 1; M | Short Float Type 1; C | +| Test purpose | Check that:
    PHG processes correctly the Context Exercise Value (%) and Base Time fields of Glucose Measurement Context characteristic | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 AND C_MAN_BLE_009 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | + +| | | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

    Test procedure

    |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset fields and Sensor Status Annunciation field are not included and Context Information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 11:08:25
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
      2. b. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1000 (MSB → LSB). Exercise Duration And Exercise Intensity fields are included and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
    | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • Format: uint16
    • • Value: Not relevant

    x. Field: Exercise Intensity

    • • Format: uint8
    • • Value: 33%

    xi. Field: Medication ID

    • • This field is not included

    xii. Field: Medication

    • • This field is not included

    xiii. Field: HbA1c

    • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (Context exercise value, Context exercise units and base time).

    | +| Pass/Fail criteria | In step 5, the PHG under test shows the following Context exercise 33 % with the time stamp '2012-08-02 11:08:25'. | +| Notes | | + +| | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-028 | | | +| TP label | Whitepaper. Glucosemeter Context Medication Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 18; O | | +| Test purpose | Check that:

    PHG does not include Context Medication object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Context Medication object, Handle attribute in transcoder output, then its value shall be different than 0 | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_010 | | | +| Other PICS | | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • Format: uint8
          • • Value: Not relevant
        12. xii. Field: Medication - units of kilograms
          • • Format: SFLOAT
          • • Value: Not relevant
        13. xiii. Field: Medication - units of litres
          • • This field is not included
        14. xiv. Field: HbA1c
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | measurement followed by the Glucose measurement context to the PHG under test.
    5. Check in PHG transcoder output for the Context exercise object, Handle attribute. | +| Pass/Fail criteria | In step 5, the Context medication object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Handle attribute is not present, or if it is present then:
    Object: Context Medication numeric object
    Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    Attribute-type: INT-U16
    Attribute-value: Any value other than 0
    b) WAN PCD-01 message
    PCD-01 message does not include segments with a Handle attribute value. | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-029 | | | +| TP label | Whitepaper. Glucosemeter Context Medication Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 19; M | | +| Test purpose | Check that:
    PHG includes Context Medication object, Type attribute in transcoder output.
    [AND]
    Type is set to {MDC_PART_PHD_DM MDC_CTXT_MEDICATION} | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_010 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
    a. Glucose measurement context (0x2A34)
    i. Field: Flags
    • • Format: 8 bit
    • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
    ii. Field: Sequence number
    • • Format: uint16
    • • Value: Not relevant
    iii. Field: Extended Flags
    • • This field is not included
    iv. Field: Carbohydrate ID
    • • This field is not included
    v. Field: Carbohydrate
    • • This field is not included
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • Format: uint8
    • • Value: Not relevant

    xii. Field: Medication - units of kilograms

    • • Format: SFLOAT
    • • Value: Not relevant

    xiii. Field: Medication - units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context medication object, Type attribute.

    | +| Pass/Fail criteria | In step 5, the Context medication object, Type attribute is present and its value is { MDC_PART_PHD_DM MDC_CTXT_MEDICATION }. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Context exercise object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_MEDICATION or 29188 (dec) or 72 04 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX[?][NM][8417800^MDC_CTXT_MEDICATION_RAPIDACTING ^MDC 1.0.0.a 0.17 263890^MDC_DIM_MILLI_G^MDC   R   current_date_time]
    | + +| | | +|-----------------|----------------------------------------------------------------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-030 | +| TP label | Whitepaper. Glucosemeter Context Medication Object - Metric-Spec-Small Attribute | + +| | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 20; M | | | +| Test purpose |

    Check that:

    PHG includes Context Medication Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual).

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_010 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • Format: uint8
          • • Value: Not relevant
        12. xii. Field: Medication - units of kilograms
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: SFLOAT
    • Value: Not relevant

    xiii. Field: Medication - units of litres

    • This field is not included

    xiv. Field: HbA1c

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context Medication numeric object, Metric-Spec-Small attribute.

    | +| Pass/Fail criteria | In step 5, the Context Medication numeric object, Metric-Spec-Small attribute is present and its value is {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Context Medication numeric object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 48 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-manual(12) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-031 | | | +| TP label | Whitepaper. Glucosemeter Context Medication Object - Metric-Id Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 21; M | | +| Test purpose |

    Check that:

    PHG includes Context Medication object, Metric-Id attribute in transcoder output.

    [AND]

    Type is set to different values depending on Medication ID field value

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_010 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:

    a. Glucose measurement context (0x2A34)

    i. Field: Flags

    | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: 8 bit
    • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
    | +| |
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    | +| |
    • iii. Field: Extended Flags
      • • This field is not included
    | +| |
    • iv. Field: Carbohydrate ID
      • • This field is not included
    | +| |
    • v. Field: Carbohydrate
      • • This field is not included
    | +| |
    • vi. Field: Meal
      • • This field is not included
    | +| |
    • vii. Field: Tester
      • • This field is not included
    | +| |
    • viii. Field: Health
      • • This field is not included
    | +| |
    • ix. Field: Exercise Duration
      • • This field is not included
    | +| |
    • x. Field: Exercise Intensity
      • • This field is not included
    | +| |
    • xi. Field: Medication ID
      • • Format: uint8
      • • Value: Several values are checked in this test case
    | +| |
    • xii. Field: Medication - units of kilograms
      • • Format: SFLOAT
      • • Value: Not relevant
    | +| |
    • xiii. Field: Medication - units of litres
      • • This field is not included
    | +| |
    • xiv. Field: HbA1c
      • • This field is not included
    | +| |
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Medication ID field set to 0x01 = Rapid acting insulin) to the PHG under test.
    3. 5. Check in PHG transcoder output for the Context Medication numeric object, Metric-Id attribute.
    4. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Medication ID field set to 0x02 = Short acting insulin) to the PHG under test.
    5. 7. Check in PHG transcoder output for the Context Medication numeric object, Metric-Id attribute.
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

    attribute.

    |
    1. 8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Medication ID field set to 0x03 = Intermediate acting insulin) to the PHG under test.
    2. 9. Check in PHG transcoder output for the Context Medication numeric object, Metric-Id attribute.
    3. 10. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Medication ID field set to 0x04 = Long acting insulin) to the PHG under test.
    4. 11. Check in PHG transcoder output for the Context Medication numeric object, Metric-Id attribute.
    5. 12. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Medication ID field set to 0x05 = Pre-mixed insulin) to the PHG under test.
    6. 13. Check in PHG transcoder output for the Context Medication numeric object, Metric-Id attribute.
    | +| Pass/Fail criteria |

    In step 5, the Context medication object, Metric-Id attribute is present and its value is MDC_CTXT_MEDICATION_RAPIDACTING.

    In step 7, the Context medication object, Metric-Id attribute is present and its value is MDC_CTXT_MEDICATION_SHORTACTING.

    In step 9, the Context medication object, Metric-Id attribute is present and its value is MDC_CTXT_MEDICATION_INTERMEDIATEACTING.

    In step 11, the Context medication object, Metric-Id attribute is present and its value is MDC_CTXT_MEDICATION_LONGACTING.

    In step 13, the Context medication object, Metric-Id attribute is present and its value is MDC_CTXT_MEDICATION_PREMIX.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_ID_PHYSIO (2347)
    • Attribute-type: code (INT-U16)
    • Attribute-value: code: MDC_CTXT_MEDICATION_RAPIDACTING or 29192 (dec) or 72 08 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3):

    OBX[?] NM 8417800^MDC_CTXT_MEDICATION_RAPIDACTING ^MDC 1.0.0.a 0.17 263890^MDC_DIM_MILLI_G^MDC   R  [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_ID_PHYSIO (2347)
    • Attribute-type: code (INT-U16)
    • Attribute-value: code: MDC_CTXT_MEDICATION_SHORTACTING or 29196 (dec) or 72 0C (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Metric-Id attribute value (check

    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    OBX-3):

    OBX[?] NM 8417804^MDC_CTXT_MEDICATION_SHORTACTING ^MDC 1.0.0.a 0.18 263890^MDC_DIM_MILLI_G^MDC    R  [current_date_time]

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_ID_PHYSIO (2347)
    • Attribute-type: code (INT-U16)
    • Attribute-value: code: MDC_CTXT_MEDICATION_INTERMEDIATEACTING or 29200 (dec) or 72 10 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3):

    OBX[?] NM 8417808^ MDC_CTXT_MEDICATION_INTERMEDIATEACTING ^MDC 1.0.0.a 0.19 263890^MDC_DIM_MILLI_G^MDC    R  [current_date_time]

    In step 11, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_ID_PHYSIO (2347)
    • Attribute-type: code (INT-U16)
    • Attribute-value: code: MDC_CTXT_MEDICATION_LONGACTING or 29204 (dec) or 72 14 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3):

    OBX[?] NM 8417812^ MDC_CTXT_MEDICATION_LONGACTING ^MDC 1.0.0.a 0.20 263890^MDC_DIM_MILLI_G^MDC    R  [current_date_time]

    In step 13, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_ID_PHYSIO (2347)
    • Attribute-type: code (INT-U16)
    • Attribute-value: code: MDC_CTXT_MEDICATION_PREMIX or 29208 (dec) or 72 18 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3):

    OBX[?] NM 8417816^ MDC_CTXT_MEDICATION_PREMIX ^MDC 1.0.0.a 0.21 263890^MDC_DIM_MILLI_G^MDC    R  [current_date_time]
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|-----------------|--------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-032 | | | +| TP label | Whitepaper. Glucosemeter Context Medication Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 22; M | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    PHG includes Context Medication object, Unit-Code attribute in transcoder output.

    [AND]

    IF Medication Value (kg) field of Glucose Measurement Context characteristic is present THEN Context Medication object, Unit-Code attribute is set to MDC_DIM_MILLI_G

    [AND]

    IF Medication Value (l) field of Glucose Measurement Context characteristic is present THEN Context Medication object, Unit-Code attribute is set to MDC_DIM_MILLI_L

    | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_010 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    xi. Field: Medication ID

    • • Format: uint8
    • • Value: 0x01 (Rapid action insulin)

    xii. Field: Medication - units of kilograms

    • • Format: SFLOAT
    • • Value: Not relevant

    xiii. Field: Medication - units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    5. Check in PHG transcoder output for the Context medication object, Unit-Code attribute.

    6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:

    a. Glucose measurement context (0x2A34)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0011 0000 (MSB → LSB). Medication ID and Medication in units of litres fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included

    ii. Field: Sequence number

    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • Format: uint8
    • • Value: 0x01 (Rapid action insulin)
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • xii. Field: Medication - units of kilograms
      • • This field is not included
    • xiii. Field: Medication - units of litres
      • • Format: SFLOAT
      • • Value: Not relevant
    • xiv. Field: HbA1c
      • • This field is not included

    7. Check in PHG transcoder output for the Context medication object, Unit-Code attribute.

    | +| Pass/Fail criteria |

    In step 5, the Context medication object, Unit-Code attribute is present and its value is MDC_DIM_MILLI_G.

    In step 7, the Context medication object, Unit-Code attribute is present and its value is MDC_DIM_MILLI_L.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_MILLI_G or 1746 (dec) or 06 D2 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX ? NM 8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC  1.0.0.a 0.17 263890^MDC_DIM_MILLI_G^MDC    R  [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_MILLI_L or 1618 (dec) or 06 52 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX ? NM 8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC  1.0.0.a 0.05 263762^MDC_DIM_MILLI_L^MDC    R  [current_date_time]
    | + +| | | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-033 | | | | +| TP label | Whitepaper. Glucosometer Context Medication Object - Absolute-Time-Stamp Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 23; M | Date-Time Conv 2; M | Date-Time Conv 3; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | | +| Test purpose |

    Check that:

    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into Context Medication Object - Absolute-Time-Stamp attribute

    [AND]

    | | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format
    [AND]
    The fraction of seconds in Absolute Time at transcoder output is 0 | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_010 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location and Time Offset fields are included Sensor Status Annunciation field is not included and Context information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:59:27
        4. iv. Field: Time Offset
          • • Format: sint16
          • • Value: 120 minutes
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • This field is not included
        8. viii. Field: Sample Location
          • • This field is not included
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
      2. b. Glucose measurement context (0x2A34)
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. i. Field: Flags
      • • Format: 8 bit
      • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
    2. ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    3. iii. Field: Extended Flags
      • • This field is not included
    4. iv. Field: Carbohydrate ID
      • • This field is not included
    5. v. Field: Carbohydrate
      • • This field is not included
    6. vi. Field: Meal
      • • This field is not included
    7. vii. Field: Tester
      • • This field is not included
    8. viii. Field: Health
      • • This field is not included
    9. ix. Field: Exercise Duration
      • • This field is not included
    10. x. Field: Exercise Intensity
      • • This field is not included
    11. xi. Field: Medication ID
      • • Format: uint8
      • • Value: 0x01 (Rapid action insulin)
    12. xii. Field: Medication - units of kilograms
      • • Format: SFLOAT
      • • Value: Not relevant
    13. xiii. Field: Medication - units of litres
      • • This field is not included
    14. xiv. Field: HbA1c
      • • This field is not included

    5. Check in PHG transcoder output for the Context medication object, Absolute-Time-Stamp attribute.

    | +| Pass/Fail criteria | In step 6, the Context medication object, Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field in conjunction with the Time Offset field of the Glucose measurement characteristic and the fraction of seconds is set to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 12 (hex) or 18 (dec)
      • • minute: 59 (hex) or 89 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX[? NM 8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC
    1.0.0.a 0.17 263890^MDC_DIM_MILLI_G^MDC R 20120802125927+0000

    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-034 | | | +| TP label | Whitepaper. Glucosemeter Context Medication Object - Basic-Nu-Observed-Value Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 24; M | Short Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Medication value field of Glucose Measurement Context characteristic into Context Medication Object - Basic-Nu-Observed-Value attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_010 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
        2. ii. Field: Sequence number
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • Format: uint8
    • • Value: 0x01 (Rapid action insulin)

    xii. Field: Medication - units of kilograms

    • • Format: SFLOAT
    • • Value: 0.00000017 kg (0.17 mg)

    xiii. Field: Medication - units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    5. Check in PHG transcoder output for the Context medication object– Basic-Nu-Observed-Value attribute.

    6. The simulated PHD sends the measurement to the PHG under test with the following value:

    a. Glucose measurement context (0x2A34)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0011 0000 (MSB → LSB). Medication ID and Medication in units of litres fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included

    ii. Field: Sequence number

    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • Format: uint8
    • • Value: 0x01 (Rapid action insulin)

    xii. Field: Medication - units of kilograms

    • • This field is not included

    xiii. Field: Medication - units of litres

    • • Format: SFLOAT
    • • Value: 0.00005 litres (0.05 ml)

    xiv. Field: HbA1c

    • • This field is not included

    7. Check in PHG transcoder output for the Context medication object– Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the Context medication object, Basic-Nu-Observed-Value attribute is present and its value matches with the Medication Value field of the Glucose measurement context characteristic: 0.17 mg.

    In step 7, the Context medication object, Basic-Nu-Observed-Value attribute is present and its value matches with the Medication Value field of the Glucose measurement context characteristic: 0.05 ml.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: E0 11 (hex) or 0.17 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?][NM][8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC  1.0.0.a 0.17 263890^MDC_DIM_MILLI_G^MDC   R   [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Object: Context medication object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: E0 05 (hex) or 0.05 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?][NM][8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC]
    1.0.0.a 0.05 263762^MDC_DIM_MILLI_L^MDC    R  [current_date_time]
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-035 | | | +| TP label | Whitepaper. Glucosemeter Context Medication Object - Basic-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 24; M | Short Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Medication field of Glucose Measurement Context characteristic into Context Medication object, Basic-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x07FF), NRes (0x0800), +INFINITY (0x07FE) and -INFINITY (0x0802)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_010 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      • a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test:
      • a. Glucose measurement context (0x2A34)
        • i. Field: Flags
          • • Format: 8 bit
          • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
        • ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        • iii. Field: Extended Flags
          • • This field is not included
        • iv. Field: Carbohydrate ID
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • Format: uint8
    • • Value: 0x01 (Rapid action insulin)

    xii. Field: Medication - units of kilograms

    • • Format: SFLOAT
    • • Value: 0.00000017 kg (0.17 mg)

    xiii. Field: Medication - units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    5. Check in PHG transcoder output for the Context medication object, Basic-Nu-Observed-Value attribute.

    6. The simulated PHD sends the measurement to the PHG under test with the following value:

    a. Glucose measurement context (0x2A34)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included

    ii. Field: Sequence number

    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate

    • • This field is not included

    vi. Field: Meal

    • • This field is not included
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • vii. Field: Tester
      • • This field is not included
    • viii. Field: Health
      • • This field is not included
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • Format: uint8
      • • Value: 0x01 (Rapid action insulin)
    • xii. Field: Medication - units of kilograms
      • • Format: SFLOAT
      • • Value: 07 FF (hex). Special value: NaN
    • xiii. Field: Medication - units of litres
      • • This field is not included
    • xiv. Field: HbA1c
      • • This field is not included

    7. Check in PHG transcoder output for the Context medication object, Basic-Nu-Observed-Value attribute.

    8. The simulated PHD sends the measurement to the PHG under test with the following value:

    • a. Glucose measurement context (0x2A34)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
      • ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      • iii. Field: Extended Flags
        • • This field is not included
      • iv. Field: Carbohydrate ID
        • • This field is not included
      • v. Field: Carbohydrate
        • • This field is not included
      • vi. Field: Meal
        • • This field is not included
      • vii. Field: Tester
        • • This field is not included
      • viii. Field: Health
        • • This field is not included
      • ix. Field: Exercise Duration
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • Format: uint8
    • • Value: 0x01 (Rapid action insulin)

    xii. Field: Medication - units of kilograms

    • • Format: SFLOAT
    • • Value: 00 80 (hex). Special value: NRes

    xiii. Field: Medication - units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    9. Check in PHG transcoder output for the Context medication object, Basic-Nu-Observed-Value attribute.

    10. The simulated PHD sends the measurement to the PHG under test with the following value:

    a. Glucose measurement context (0x2A34)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate
      • • This field is not included
    • vi. Field: Meal
      • • This field is not included
    • vii. Field: Tester
      • • This field is not included
    • viii. Field: Health
      • • This field is not included
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • Format: uint8
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 0x01 (Rapid action insulin)

    xii. Field: Medication - units of kilograms

    • • Format: SFLOAT
    • • Value: 07 FE (hex). Special value: +INFINITY

    xiii. Field: Medication - units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    11. Check in PHG transcoder output for the Context medication object, Basic-Nu-Observed-Value attribute.

    12. The simulated PHD sends the measurement to the PHG under test with the following value:

    a. Glucose measurement context (0x2A34)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate
      • • This field is not included
    • vi. Field: Meal
      • • This field is not included
    • vii. Field: Tester
      • • This field is not included
    • viii. Field: Health
      • • This field is not included
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xv. Field: Medication ID
      • • Format: uint8
      • • Value: 0x01 (Rapid action insulin)
    • xvi. Field: Medication - units of kilograms
      • • Format: SFLOAT
      • • Value: 08 02 (hex). Special value: -INFINITY
    • xvii. Field: Medication - units of litres
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    xviii. Field: HbA1c

    • • This field is not included

    13. Check in PHG transcoder output for the Context medication object, Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the Context medication object, Basic-Nu-Observed-Value attribute is present and its value is 0.17 mg.

    In step 7, the Context medication object, Basic -Nu-Observed-Value attribute is present and its value is 0x07FF.

    In step 9, the Context medication object, Basic -Nu-Observed-Value attribute is present and its value is 0x0800.

    In step 11, the Context medication object, Basic -Nu-Observed-Value attribute is present and its value is 0x07FE.

    In step 13, the Context medication object, Basic -Nu-Observed-Value attribute is present and its value is 0x0802.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: E0 11 (hex) or 0.17 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC  1.0.0.a 0.17 263890^MDC_DIM_MILLI_G^MDC     R  [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 07 FF(hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 08 00 (hex) or NRes (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC) because it has a

    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    special value and these values are not included in the PCD-01 message.

    In step 11, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 07 FE (hex) or +INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC) because it has a special value and these values are not included in the PCD-01 message.

    In step 13, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic -Nu-Observed-Value attribute is present:

    • Object: Context medication object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 08 02 (hex) or -INFINITY (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC) because it has a special value and these values are not included in the PCD-01 message.

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-036 | | | +| TP label | Whitepaper. Glucosemeter Context Medication value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 23; M | GL Numeric 24; M | +| | | Date-Time Conv 1; M | Short Float Type 1; C | +| Test purpose | Check that:

    PHG processes correctly the Context Medication Value (kg), Context Medication Value (l) and Base Time fields of Glucose Measurement Context characteristic | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 AND C_MAN_BLE_010 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test:
      1. a. Glucose measurement (0x2A18)
    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 00010010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location are included, Time Offset and Sensor Status Annunciation fields are not included and Context information follows
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Base Time
      • • Format: Date and Time
      • • Value: August 2nd, 2012, 11:08:25
    • iv. Field: Time Offset
      • • This field is not included
    • v. Field: Glucose Concentration - units of kg/L
      • • Format: SFLOAT
      • • Value: Not relevant
    • vi. Field: Glucose Concentration - units of mol/L
      • • This field is not included
    • vii. Field: Type
      • • Format: nibble
      • • Value: Not relevant
    • viii. Field: Sample Location
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Sensor Status Annunciation
      • • This field is not included

    b. Glucose measurement context (0x2A34)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0001 0000 (MSB → LSB). Medication ID and Medication in units of kilograms fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate
      • • This field is not included
    • vi. Field: Meal
      • • This field is not included
    • vii. Field: Tester
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • Format: uint8
    • • Value: 0x01 (Rapid action insulin)

    xii. Field: Medication - units of kilograms

    • • Format: SFLOAT
    • • Value: 0.00000017 kg (0.17 mg)

    xiii. Field: Medication - units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (Context Medication value, Context Medication units and base time).

    6. The simulated PHD sends the Glucose measurement followed by the Glucose measurement context to the PHG under test with the following value:

    a. Glucose measurement (0x2A18)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 00010010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location are included, Time Offset and Sensor Status Annunciation fields are not included and Context information follows
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • i. Field: Base Time
      • • Format: Date and Time
      • • Value: August 2nd, 2012, 11:09:05
    • ii. Field: Time Offset
      • • This field is not included
    • iii. Field: Glucose Concentration - units of kg/L
      • • Format: SFLOAT
      • • Value: Not relevant
    • iv. Field: Glucose Concentration - units of mol/L
      • • This field is not included
    • v. Field: Type
      • • This field is not included
    • vi. Field: Sample Location
      • • This field is not included
    • vii. Field: Sensor Status Annunciation
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    b. Glucose measurement context (0x2A34)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0011 0000 (MSB → LSB). Medication ID and Medication in units of litres fields are included, and Carbohydrate ID, Carbohydrate, Meal, Tester-Health, Exercise Duration and Exercise Intensity and HbA1c fields are not included
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate
      • • This field is not included
    • vi. Field: Meal
      • • This field is not included
    • vii. Field: Tester
      • • This field is not included
    • viii. Field: Health
      • • This field is not included
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • Format: uint8
      • • Value: 0x01 (Rapid action insulin)
    • xii. Field: Medication - units of kilograms
      • • This field is not included
    • xiii. Field: Medication - units of litres
      • • Format: SFLOAT
      • • Value: 0.00005 litres (0.05 ml)
    • xiv. Field: HbA1c
      • • This field is not included

    7. Check that the PHG accepts the measurement and decodes its value properly (Context Medication value, Context Medication units and base time).

    | +| Pass/Fail criteria |

    In step 5, the PHG under test shows the following Context Medication 0.17 mg with the time stamp '2012-08-02 11:08:25'.

    In step 7, the PHG under test shows the following Context Medication 0.05 ml with the time stamp '2012-08-02 11:09:05'.

    | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-037 | | | +| TP label | Whitepaper. Glucosemeter Context Carbohydrates Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 25; O | | +| Test purpose |

    Check that:

    PHG does not include Context Carbohydrates object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Context Carbohydrates object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_011 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • Format: uint8
          • • Value: Not relevant
        5. v. Field: Carbohydrate
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • This field is not included

    xii. Field: Medication

    • This field is not included

    xiii. Field: HbA1c

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Blood glucose object, Handle attribute.

    | +| Pass/Fail criteria | In step 5, the Context carbohydrates object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Context carbohydrates numeric object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Handle attribute value.

    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-038 | | | +| TP label | Whitepaper. Glucosemeter Context Carbohydrates Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 26; M | | +| Test purpose |

    Check that:

    PHG includes Context Carbohydrates object, Type attribute in transcoder output.

    [AND]

    Type is set to { MDC_PART_PHD_DM MDC_CTXT_GLU_CARBO }

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_011 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:

    a. Glucose measurement context (0x2A34)

    i. Field: Flags

    • Format: 8 bit
    • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • Format: uint8
      • • Value: Not relevant
    • v. Field: Carbohydrate
      • • Format: SFLOAT
      • • Value: Not relevant
    • vi. Field: Meal
      • • This field is not included
    • vii. Field: Tester
      • • This field is not included
    • viii. Field: Health
      • • This field is not included
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • This field is not included
    • xii. Field: Medication
      • • This field is not included
    • xiii. Field: HbA1c
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.
    3. 5. Check in PHG transcoder output for the Context carbohydrates object, Type attribute.
    | +| Pass/Fail criteria | In step 5, the Context carbohydrates object, Type attribute is present and its value is { MDC_PART_PHD_DM MDC_CTXT_GLU_CARb }. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Context carbohydrates object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_CARb or 29156 (dec) or 71 E4 (hex)
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX ? NM 8417768^MDC_CTXT_GLU_CARB_BREAKFAST^MDC 1.0.0.a 75 263872^MDC_DIM_G^MDC R [current_date_time]

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-039 | | +| TP label | Whitepaper. Glucosemeter Context Carbohydrates Object - Metric-Spec-Small Attribute | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | +| | Testable items | GL Numeric 27; M | +| Test purpose |

    Check that:

    PHG includes Context Carbohydrates Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual).

    | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_011 | | +| Other PICS | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • Format: uint8
          • • Value: Not relevant
        5. v. Field: Carbohydrate - units of kilograms
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
    | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included
    1. ix. Field: Exercise Duration
      • • This field is not included
    2. x. Field: Exercise Intensity
      • • This field is not included
    3. xi. Field: Medication ID
      • • This field is not included
    4. xii. Medication – units of kilograms
      • • This field is not included
    5. xiii. Medication – units of litres
      • • This field is not included
    6. xiv. Field: HbA1c
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.
    3. 5. Check in PHG transcoder output for the Context carbohydrate numeric object, Metric-Spec-Small attribute.
    | +| Pass/Fail criteria | In step 5, the Context carbohydrate numeric object, Metric-Spec-Small attribute is present and its value is {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • ❑ Object: Context carbohydrates numeric object
    • ❑ Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • ❑ Attribute-type: BITS-16
    • ❑ Attribute-value: F0 48 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-manual(12) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-040 | | | +| TP label | Whitepaper. Glucosemeter Context Carbohydrates Object - Metric-Id Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 28; M | | +| Test purpose | Check that:
    PHG includes Context Carbohydrate object, Metric-Id attribute in transcoder output.
    [AND]
    Type is set to different values depending on Carbohydrate ID field value | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_011 | | | +| Other PICS | | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • Format: uint8
          • • Value: Several values are checked in this test case
        5. v. Field: Carbohydrate - units of kilograms
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Medication – units of kilograms
          • • This field is not included
        13. xiii. Medication – units of litres
          • • This field is not included
        14. xiv. Field: HbA1c
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement followed by the Glucose measurement context (Carbohydrate ID field set to 0x01 = Breakfast) to the PHG under test.

    1. 5. Check in PHG transcoder output for the Context carbohydrate numeric object, Metric-Id attribute.
    2. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Carbohydrate ID field set to 0x02 = Lunch) to the PHG under test
    3. 7. Check in PHG transcoder output for the Context carbohydrate numeric object, Metric-Id attribute.
    4. 8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Carbohydrate ID field set to 0x03 = Dinner) to the PHG under test
    5. 9. Check in PHG transcoder output for the Context carbohydrate numeric object, Metric-Id attribute.
    6. 10. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Carbohydrate ID field set to 0x04 = Snack) to the PHG under test
    7. 11. Check in PHG transcoder output for the Context carbohydrate numeric object, Metric-Id attribute.
    8. 12. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Carbohydrate ID field set to 0x05 = Drink) to the PHG under test.
    9. 13. Check in PHG transcoder output for the Context carbohydrate numeric object, Metric-Id attribute.
    10. 14. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Carbohydrate ID field set to 0x06 = Supper) to the PHG under test.
    11. 15. Check in PHG transcoder output for the Context carbohydrate numeric object, Metric-Id attribute.
    12. 16. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context (Carbohydrate ID field set to 0x07 = Brunch) to the PHG under test.
    13. 17. Check in PHG transcoder output for the Context carbohydrate numeric object, Metric-Id attribute.
    | +| Pass/Fail criteria |

    In step 5, the Context carbohydrate object, Metric-Id attribute is present and its value is MDC_CTXT_GLU_CARB_BREAKFAST.

    In step 7, the Context carbohydrate object, Metric-Id attribute is present and its value is MDC_CTXT_GLU_CARB_LUNCH.

    In step 9, the Context carbohydrate object, Metric-Id attribute is present and its value is MDC_CTXT_GLU_CARB_DINNER.

    In step 11, the Context carbohydrate object, Metric-Id attribute is present and its value is MDC_CTXT_GLU_CARB_SNACK

    In step 13, the Context carbohydrate object, Metric-Id attribute is present and its value is MDC_CTXT_GLU_CARB_DRINK.

    In step 15, the Context carbohydrate object, Metric-Id attribute is present and its value is MDC_CTXT_GLU_CARB_SUPPER.

    In step 17, the Context carbohydrate object, Metric-Id attribute is present and its value is MDC_CTXT_GLU_CARB_BRUNCH.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    | + +Metric-Id attribute is present: + +- Object: Context carbohydrate object +- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347) +- Attribute-type: code (INT-U16) +- Attribute-value: code: MDC\_CTXT\_GLU\_CARB\_BREAKFAST or 29160 (dec) or 71 E8 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3): + +OBX[?][NM][8417768^MDC\_CTXT\_GLU\_CARB\_BREAKFAST^MDC|1.0.0.a|130| +263872^MDC\_DIM\_G^MDC|||||R|||[current\_date\_time] + +In step 7, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Metric-Id attribute is present: + +- Object: Context carbohydrate object +- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347) +- Attribute-type: code (INT-U16) +- Attribute-value: code: MDC\_CTXT\_GLU\_CARB\_LUNCH or 29164 (dec) or 71 EC (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3): + +OBX[?][NM][8417772^MDC\_CTXT\_GLU\_CARB\_LUNCH^MDC|1.0.0.a|130| +263872^MDC\_DIM\_G^MDC|||||R|||[current\_date\_time] + +In step 9, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Metric-Id attribute is present: + +- Object: Context carbohydrate object +- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347) +- Attribute-type: code (INT-U16) +- Attribute-value: code: MDC\_CTXT\_GLU\_CARB\_DINNER or 29168 (dec) or 71 F0 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3): + +OBX[?][NM][8417776^MDC\_CTXT\_GLU\_CARB\_DINNER^MDC|1.0.0.a|130| +263872^MDC\_DIM\_G^MDC|||||R|||[current\_date\_time] + +In step 11, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Metric-Id attribute is present: + +- Object: Context carbohydrate object +- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347) +- Attribute-type: code (INT-U16) +- Attribute-value: code: MDC\_CTXT\_GLU\_CARB\_SNACK or 29172 (dec) or 71 F4 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3): + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    OBX[?][NM][8417780^MDC_CTXT_GLU_CARB_SNACK^MDC][1.0.0.a][130]
    263872^MDC_DIM_G^MDC [R][[current_date_time]]

    In step 13, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id attribute is present:

    • Object: Context carbohydrate object
    • Attribute-id: MDC_ATTR_ID_PHYSIO (2347)
    • Attribute-type: code (INT-U16)
    • Attribute-value: code: MDC_CTXT_GLU_CARB_DRINK or 29176 (dec) or 71 F8 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3):

    OBX[?][NM][8417784^MDC_CTXT_GLU_CARB_DRINK^MDC][1.0.0.a][130]
    263872^MDC_DIM_G^MDC [R][[current_date_time]]

    In step 15, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id attribute is present:

    • Object: Context carbohydrate object
    • Attribute-id: MDC_ATTR_ID_PHYSIO (2347)
    • Attribute-type: code (INT-U16)
    • Attribute-value: code: MDC_CTXT_GLU_CARB_SUPPER or 29180 (dec) or 71 FC (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3):

    OBX[?][NM][8417788^MDC_CTXT_GLU_CARB_SUPPER^MDC][1.0.0.a][130]
    263872^MDC_DIM_G^MDC [R][[current_date_time]]

    In step 17, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id attribute is present:

    • Object: Context carbohydrate object
    • Attribute-id: MDC_ATTR_ID_PHYSIO (2347)
    • Attribute-type: code (INT-U16)
    • Attribute-value: code: MDC_CTXT_GLU_CARB_BRUNCH or 29184 (dec) or 72 00 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Metric-Id attribute value (check OBX-3):

    OBX[?][NM][8417792^MDC_CTXT_GLU_CARB_BRUNCH^MDC][1.0.0.a][130]
    263872^MDC_DIM_G^MDC [R][[current_date_time]]

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------|-----------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-041 | | | +| TP label | Whitepaper. Glucosemeter Context Carbohydrates Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 29; M | | +| Test purpose | Check that: | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PHG includes Context Carbohydrates object, Unit-Code attribute in transcoder output.
    [AND]
    IF Carbohydrate Value (kg) field of Glucose Measurement Context characteristic is present
    THEN Context Carbohydrate object, Unit-Code attribute is set to MDC_DIM_X_G | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_011 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • Format: uint8
          • • Value: Not relevant
        5. v. Field: Carbohydrate – units of kilograms
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Medication – units of kilograms
          • • This field is not included
        13. xiii. Medication – units of litres
          • • This field is not included
    | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xiv. Field: HbA1c

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context carbohydrate object, Unit-Code attribute

    | +| Pass/Fail criteria | In step 5, the Context carbohydrate object, Unit-Code attribute is present and its value is MDC_DIM_X_G | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Context carbohydrates object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_X_G or 1728 (dec) or 06 C0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?][NM][8417768^MDC_CTXT_GLU_CARB_BREAKFAST^MDC 1.0.0.a 130 263872^MDC_DIM_G^MDC R [current_date_time]

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-042 | | | +| TP label | Whitepaper. Glucosemeter Context Carbohydrates Object - Absolute-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 30; M | Date-Time Conv 2; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | +| Test purpose |

    Check that:

    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into Context Carbohydrate Object - Absolute-Time-Stamp attribute [AND]

    PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_011 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    | | | + +4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are: + - a. Glucose measurement (0x2A18) + - i. Field: Flags + - Format: 8 bit + - Value: 00010011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location and Time Offset fields are included Sensor Status Annunciation field is not included and Context information follows + - ii. Field: Sequence number + - Format: uint16 + - Value: Not relevant + - iii. Field: Base Time + - Format: Date and Time + - Value: August 2nd, 2012, 10:59:27 + - iv. Field: Time Offset + - Format: sint16 + - Value: 120 minutes + - v. Field: Glucose Concentration - units of kg/L + - Format: SFLOAT + - Value: Not relevant + - vi. Field: Glucose Concentration - units of mol/L + - This field is not included + - vii. Field: Type + - This field is not included + - viii. Field: Sample Location + - This field is not included + - ix. Field: Sensor Status Annunciation + - This field is not included + - b. Glucose measurement context (0x2A34) + - i. Field: Flags + - Format: 8 bit + - Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included + - ii. Field: Sequence number + - Format: uint16 + - Value: Not relevant + - iii. Field: Extended Flags + - This field is not included + - iv. Field: Carbohydrate ID + - Format: uint8 + - Value: Not relevant + - v. Field: Carbohydrate - units of kilograms + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: SFLOAT
    • • Value: Not relevant

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Medication – units of kilograms

    • • This field is not included

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    5. Check in PHG transcoder output for the Context carbohydrate object, Absolute-Time-Stamp attribute.

    | +| Pass/Fail criteria | In step 5, the Context carbohydrate object, Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field in conjunction with the Time Offset field of the Glucose measurement characteristic and the fraction of seconds is set to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Context carbohydrates object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 12 (hex) or 18 (dec)
      • • minute: 59 (hex) or 89 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------| +| | OBX[?][NM]8417768^MDC_CTXT_GLU_CARB_BREAKFAST^MDC 1.0.0.a 130 263872^MDC_DIM_G^MDC R 20120802125927+0000 | +|--|-------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-043 | | | | +| TP label | Whitepaper. Glucosemeter Context Carbohydrates Object - Basic-Nu-Observed-Value Attribute 1 | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Numeric 31; M | Short Float Type 1; C | | +| Test purpose | Check that:
    PHG transcodes Carbohydrate value field of Glucose Measurement Context characteristic into Context Carbohydrate Object - Basic-Nu-Observed-Value attribute | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_011 AND C_MAN_BLE_025 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • Format: uint8
          • • Value: Not relevant
        5. v. Field: Carbohydrate - units of kilograms
          • • Format: SFLOAT
          • • Value: 0.130 kg
        6. vi. Field: Meal
          • • This field is not included
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • vii. Field: Tester
      • • This field is not included
    • viii. Field: Health
      • • This field is not included
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • This field is not included
    • xii. Medication – units of kilograms
      • • This field is not included
    • xiii. Medication – units of litres
      • • This field is not included
    • xiv. Field: HbA1c
      • • This field is not included

    5. Check in PHG transcoder output for the Context carbohydrate object– Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria | In step 5, the Context carbohydrate object, Basic-Nu-Observed-Value attribute is present and its value matches with Carbohydrate Value field of Glucose measurement context characteristic: 130 g. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Context carbohydrates object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 0082 (hex) or F514 (hex) or 130 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?][NM][8417768^MDC_CTXT_GLU_CARB_BREAKFAST^MDC][1.0.0.a][130]
    263872^MDC_DIM_G^MDC     R  [current_date_time]
    | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-044 | | | +| TP label | Whitepaper. Glucosimeter Context Carbohydrates Object - Basic-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Numeric 31; M | Short Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Carbohydrate field of Glucose Measurement Context characteristic into Context Carbohydrate object, Basic-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x07FF), NRes (0x0800), +INFINITY (0x07FE) and -INFINITY (0x0802)

    | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_011 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • Format: uint8
          • • Value: Not relevant
        5. v. Field: Carbohydrate - units of kilograms
          • • Format: SFLOAT
          • • Value: 0.130 kg
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Medication – units of kilograms
          • • This field is not included
    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    5. Check in PHG transcoder output for the Context carbohydrate object, Basic-Nu-Observed-Value attribute.

    6. The simulated PHD sends the measurement to the PHG under test with the following value:

    a. Glucose measurement context (0x2A34)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included

    ii. Field: Sequence number

    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • Format: uint8
    • • Value: Not relevant

    v. Field: Carbohydrate - units of kilograms

    • • Format: SFLOAT
    • • Value: 07 FF (hex). Special value: NaN

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Medication – units of kilograms

    • • This field is not included

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    7. Check in PHG transcoder output for the Context carbohydrate object, Basic-Nu-

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Observed-Value attribute.

    8. The simulated PHD sends the measurement to the PHG under test with the following value:

    • a. Glucose measurement context (0x2A34)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
      • ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      • iii. Field: Extended Flags
        • • This field is not included
      • iv. Field: Carbohydrate ID
        • • Format: uint8
        • • Value: Not relevant
      • v. Field: Carbohydrate - units of kilograms
        • • Format: SFLOAT
        • • Value: 00 80 (hex). Special value: NRes
      • vi. Field: Meal
        • • This field is not included
      • vii. Field: Tester
        • • This field is not included
      • viii. Field: Health
        • • This field is not included
      • ix. Field: Exercise Duration
        • • This field is not included
      • x. Field: Exercise Intensity
        • • This field is not included
      • xi. Field: Medication ID
        • • This field is not included
      • xii. Medication – units of kilograms
        • • This field is not included
      • xiii. Medication – units of litres
        • • This field is not included
      • xiv. Field: HbA1c
        • • This field is not included

    9. Check in PHG transcoder output for the Context carbohydrate object, Basic-Nu-Observed-Value attribute.

    10. The simulated PHD sends the measurement to the PHG under test with the following value:

    • a. Glucose measurement context (0x2A34)
      • i. Field: Flags
        • • Format: 8 bit
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
    1. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    2. Field: Extended Flags
      • • This field is not included
    3. Field: Carbohydrate ID
      • • Format: uint8
      • • Value: Not relevant
    4. Field: Carbohydrate - units of kilograms
      • • Format: SFLOAT
      • • Value: 07 FE (hex). Special value: +INFINITY
    5. Field: Meal
      • • This field is not included
    6. Field: Tester
      • • This field is not included
    7. Field: Health
      • • This field is not included
    8. Field: Exercise Duration
      • • This field is not included
    9. Field: Exercise Intensity
      • • This field is not included
    10. Field: Medication ID
      • • This field is not included
    11. Medication – units of kilograms
      • • This field is not included
    12. Medication – units of litres
      • • This field is not included
    13. Field: HbA1c
      • • This field is not included

    11. Check in PHG transcoder output for the Context carbohydrate object, Basic-Nu-Observed-Value attribute.

    12. The simulated PHD sends the measurement to the PHG under test with the following value:

    1. Glucose measurement context (0x2A34)
      1. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
      2. Field: Sequence number
        • • Format: uint16
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • Format: uint8
    • • Value: Not relevant

    v. Field: Carbohydrate - units of kilograms

    • • Format: SFLOAT
    • • Value: 08 02 (hex). Special value: -INFINITY

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Medication – units of kilograms

    • • This field is not included

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    13. Check in PHG transcoder output for the Context carbohydrate object, Basic-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In step 5, the Context carbohydrate object, Basic-Nu-Observed-Value attribute is present and its value is 130 g.

    In step 7, the Context carbohydrate object, Basic -Nu-Observed-Value attribute is present and its value is 0x07FF.

    In step 9, the Context carbohydrate object, Basic -Nu-Observed-Value attribute is present and its value is 0x0800.

    In step 11, the Context carbohydrate object, Basic -Nu-Observed-Value attribute is present and its value is 0x07FE.

    In step 13, the Context carbohydrate object, Basic -Nu-Observed-Value attribute is present and its value is 0x0802.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Context carbohydrates object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    | + +- Attribute-value: 0082 (hex) or F514 (hex) or 130 (dec) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with a Basic-Nu-Observed-Value attribute value (check OBX-5): + +OBX[?]|NM|8417768^MDC\_CTXT\_GLU\_CARB\_BREAKFAST^MDC|1.0.0.a|130| +263872^MDC\_DIM\_G^MDC|||||R||[current\_date\_time] + +In step 7, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Basic -Nu-Observed-Value attribute is present: + +- Object: Context carbohydrates object +- Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636) +- Attribute-type: SFLOAT +- Attribute-value: 07 FF(hex) or NaN (note that a decimal value is not allowed) + +#### b) WAN PCD-01 message + +PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (8417768^MDC\_CTXT\_GLU\_CARB\_BREAKFAST^MDC) because it has a special value and these values are not included in the PCD-01 message. + +In step 9, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Basic -Nu-Observed-Value attribute is present: + +- Object: Context carbohydrates object +- Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636) +- Attribute-type: SFLOAT +- Attribute-value: 08 00 (hex) or NRes (note that a decimal value is not allowed) + +#### b) WAN PCD-01 message + +PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (8417768^MDC\_CTXT\_GLU\_CARB\_BREAKFAST^MDC) because it has a special value and these values are not included in the PCD-01 message. + +In step 11, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Basic -Nu-Observed-Value attribute is present: + +- Object: Context carbohydrates object +- Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636) +- Attribute-type: SFLOAT +- Attribute-value: 07 FE (hex) or +INFINITY (note that a decimal value is not allowed) + +#### b) WAN PCD-01 message + +PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (8417768^MDC\_CTXT\_GLU\_CARB\_BREAKFAST^MDC) because it has a special value and these values are not included in the PCD-01 message. + +In step 13, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Basic -Nu-Observed-Value attribute is present: + +- Object: Context carbohydrates object +- Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636) +- Attribute-type: SFLOAT +- Attribute-value: 08 02 (hex) or -INFINITY (note that a decimal value is not allowed) + +#### b) WAN PCD-01 message + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PCD-01 message does not include segments with a Basic -Nu-Observed-Value attribute value (8417768^MDC_CTXT_GLU_CARB_BREAKFAST^MDC) because it has a special value and these values are not included in the PCD-01 message. | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-045 | | | +| TP label | Whitepaper. Glucosemeter Context Carbohydrates value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | Short Float Type 1; C | Date-Time Conv 1; M | +| | | GL Numeric 31; M | GL Numeric 30; M | +| Test purpose | Check that:

    PHG processes correctly the Context Carbohydrate Value (kg) and Base Time fields of Glucose Measurement Context characteristic | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 AND C_MAN_BLE_011 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location are included, Time Offset and Sensor Status Annunciation fields are not included and Context information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 11:08:25
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: nibble
    • • Value: Not relevant

    viii. Field: Sample Location

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Sensor Status Annunciation

    • • This field is not included

    b. Glucose measurement context (0x2A34)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0000 0001 (MSB → LSB). Carbohydrate ID and Carbohydrate is included and Meal, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included

    ii. Field: Sequence number

    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • Format: uint8
    • • Value: 0x01 (Breakfast)

    v. Field: Carbohydrate - units of kilograms

    • • Format: SFLOAT
    • • Value: 0.130 kg

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Medication – units of kilograms

    • • This field is not included

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (Context

    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------| +| | carbohydrates value, Context carbohydrates units and base time). | +| Pass/Fail criteria | In step 5, the PHG under test shows the following Context carbohydrate 130 g with the time stamp '2012-08-02 11:08:25'. | +| Notes | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-046 | | | +| TP label | Whitepaper. Glucosemeter Device & Sensor Annunciation Enumeration Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 1; O | | +| Test purpose |

    Check that:

    PHG does not include Device & Sensor Annunciation Enumeration object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Device & Sensor Annunciation Enumeration object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_012 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00001010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location, Sensor Status Annunciation fields are included. Time Offset field is not included. Context information does not follow
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    viii. Field: Sample Location

    • Format: nibble
    • Value: Not relevant

    ix. Field: Sensor Status Annunciation

    • Format: 16 bit
    • Value: Not relevant

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement to the PHG under test.

    5. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object, Handle attribute.

    | +| Pass/Fail criteria | In step 5, the Device & Sensor annunciation enumeration object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Device & Sensor annunciation enumeration object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Handle attribute value.

    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-047 | | | +| TP label | Whitepaper. Glucosemeter Device & Sensor Annunciation Enumeration Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 2; M | | +| Test purpose |

    Check that:

    PHG includes Device & Sensor Annunciation Enumeration object, Type attribute in transcoder output.

    [AND]

    Type is set to { MDC_PART_PHD_DM MDC_GLU_METER_DEV_STATUS }

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_012 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:

    a. Glucose measurement (0x2A18)

    i. Field: Flags

    • Format: 8 bit
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 00001010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location, Sensor Status Annunciation fields are included. Time Offset field is not included. Context information does not follow
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Base Time
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Time Offset
      • • This field is not included
    • v. Field: Glucose Concentration - units of kg/L
      • • Format: SFLOAT
      • • Value: Not relevant
    • vi. Field: Glucose Concentration - units of mol/L
      • • This field is not included
    • vii. Field: Type
      • • Format: nibble
      • • Value: Not relevant
    • viii. Field: Sample Location
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Sensor Status Annunciation
      • • Format: 16 bit
      • • Value: Not relevant
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement to the PHG under test.
    3. 5. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object, Type attribute.
    | +| Pass/Fail criteria | In step 5, the Device & Sensor annunciation enumeration object, Type attribute is present and its value is { MDC_PART_PHD_DM MDC_GLU_METER_DEV_STATUS }. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Device & Sensor annunciation enumeration object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_GLU_METER_DEV_STATUS or 29144 (dec) or 71D8 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------| +| | OBX[?][NM][8417752^MDC_GLU METER_DEV_STATUS^MDC][1.0.0.a][1^device-battery-low(0) R [current_date_time] | +|--|----------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-048 | | | +| TP label | Whitepaper. Glucosemeter Device & Sensor Annunciation Enumeration Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 3; M | | +| Test purpose |

    Check that:

    PHG includes Device & Sensor Annunciation Enumeration object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_012 AND C_MAN_BLE_025 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00001010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location, and Sensor Status Annunciation fields are included. Time Offset field is not included. Context information does not follow
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: nibble
    • • Value: Not relevant
    ix. Field: Sensor Status Annunciation
    • • Format: 16 bit
    • • Value: Not relevant
    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement to the PHG under test.
    5. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object, Metric-Spec-Small attribute. | +| Pass/Fail criteria | In step 5, the Device & Sensor annunciation enumeration object, Metric-Spec-Small attribute is present and its value is {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • θ Object: Device & Sensor annunciation enumeration object
    • θ Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • θ Attribute-type: BITS-16
    • θ Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE
    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-049 | | | | +| TP label | Whitepaper. Glucosemeter Device & Sensor Annunciation Enumeration Object - Absolute-Time-Stamp Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Enumeration 4; M | Date-Time Conv 2; M | Date-Time Conv 3; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | | +| Test purpose | Check that:
    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into Device & Sensor Annunciation Enumeration Object - Absolute-Time-Stamp attribute
    [AND]
    PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format
    [AND]
    The fraction of seconds in Absolute Time at transcoder output is 0 | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_012 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure | 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable). | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
    2. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00001011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location, Time Offset fields and Sensor Status Annunciation field are included. Context information does not follow
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:59:27
        4. iv. Field: Time Offset
          • • Format: sint16
          • • Value: 120 minutes
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Sensor Status Annunciation
          • • Format: 16 bit
          • • Value: Not relevant
    4. 5. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object, Absolute-Time-Stamp attribute.
    | +| Pass/Fail criteria | In step 5, the Device & Sensor annunciation enumeration object, Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field in conjunction with the Time Offset field of the Glucose measurement characteristic and the fraction of seconds is set to 0. | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Absolute-Time-Stamp attribute is present: | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Object: Device & Sensor annunciation enumeration object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 12 (hex) or 18 (dec)
      • • minute: 59 (hex) or 89 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX[? NM 8417752^MDC_GLU_METER_DEV_STATUS^MDC 1.0.0.a 1^device-battery-low(0) R 20120802125927+0000

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-050 | | | +| TP label | Whitepaper. Glucosimeter Device & Sensor Annunciation Enumeration Object - Enum-Observed-Value-Basic-Bit-Str Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 5; M | | +| Test purpose | Check that:

    PHG transcodes Sensor Status Annunciation value field of Glucose Measurement characteristic into Device & Sensor Annunciation Enumeration Object - Enum-Observed-Value-Basic-Bit-Str attribute | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_012 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00001010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location, and Sensor Status Annunciation fields are included. Time Offset field is not included. Context information does not follow
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
    | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: Date and Time
    • • Value: Not relevant

    iv. Field: Time Offset

    • • This field is not included

    v. Field: Glucose Concentration - units of kg/L

    • • Format: SFLOAT
    • • Value: Not relevant

    vi. Field: Glucose Concentration - units of mol/L

    • • This field is not included

    vii. Field: Type

    • • Format: nibble
    • • Value: Not relevant

    viii. Field: Sample Location

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Sensor Status Annunciation

    • • Format: 16 bit
    • • Value: Several values are checked in this test case
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000000000000001 0x0001 (MSB → LSB) = device battery low] to the PHG under test.
    3. 5. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.
    4. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000000000000010 0x0002 (MSB → LSB) = sensor malfunction] to the PHG under test.
    5. 7. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.
    6. 8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000000000000100 0x0004 (MSB → LSB) = sample size insufficient, not enough blood or control solution] to the PHG under test.
    7. 9. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.
    8. 10. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000000000001000 0x0008 (MSB → LSB) = stripo insertion error] to the PHG under test.
    9. 11. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.
    10. 12. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000000000010000 0x0010 (MSB → LSB) = strip type is incorrect] to the PHG under test.
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    13. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.

    14. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000000000100000 0x0020 (MSB → LSB) = sensor result higher than device can process] to the PHG under test.

    15. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.

    16. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000000001000000 0x0040 (MSB → LSB) = sensor result lower than device can process] to the PHG under test.

    17. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.

    18. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000000010000000 0x0080 (MSB → LSB) = ambient temperature too high for a valid test/result] to the PHG under test.

    19. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.

    20. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000000100000000 0x0100 (MSB → LSB) = ambient temperature too low for a valid test/result] to the PHG under test.

    21. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.

    22. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000001000000000 0x0200 (MSB → LSB) = reading was interrupted and/or strip was pulled too soon] to the PHG under test.

    23. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.

    24. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sensor Status Annunciation ID field set to 0000010000000000 0x0400 (MSB → LSB) = general device fault] to the PHG under test.

    25. Check in PHG transcoder output for the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute.

    | +| Pass/Fail criteria |

    In step 5, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: device-battery-low(0) → 0x8000.

    In step 7, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor-malfunction(1) → 0x4000.

    In step 9, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor-sample-size-insufficient(2) → 0x2000.

    In step 11, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor -strip-insertion(3) → 0x1000.

    In step 13, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor -strip-type-incorrect(4) → 0x0800.

    | + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    0x0800.

    In step 15, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor-result-too-high(5) → 0x0400.

    In step 17, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor-result-too-low(6) → 0x0200.

    In step 19, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor-temp-too-high(7) → 0x0100.

    In step 21, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor-temp-too-low(8) → 0x0080.

    In step 23, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor-read-interrupt(9) → 0x0040.

    In step 25, the Device & Sensor annunciation enumeration object - Enum-Observed-Value-Basic-Bit-Str attribute is present and its value matches with the Sensor Status Annunciation Value field of the Glucose measurement characteristic: sensor-gen-fault(10) → 0x0020.

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Basic-Bit-Str attribute is present:

    • Object: Device & Sensor annunciation enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)
    • Attribute-type: BITS-16
    • Attribute-value: 32768 (dec) or 0x8000 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check

    OBX[?][NM][8417752^MDC_GLU_METER_DEV_STATUS^MDC 1.0.0.a 1^device-battery-low(0)     R  [current_date_time]

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Basic-Bit-Str attribute is present:

    • Object: Device & Sensor annunciation enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)
    • Attribute-type: BITS-16
    • Attribute-value: 16384 (dec) or 0x4000 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check

    OBX[?][NM][8417752^MDC_GLU_METER_DEV_STATUS^MDC 1.0.0.a 1^sensor-malfunction(1)     R  [current_date_time]

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Basic-Bit-Str attribute is present:

    • Object: Device & Sensor annunciation enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)
    • Attribute-type: BITS-16
    • Attribute-value: 8192 (dec) or 0x2000 (hex)
    | + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check + +OBX[?][NM][8417752^MDC\_GLU\_METER\_DEV\_STATUS^MDC][1.0.0.a][1^sensor-sample-size-insufficient(2)]|||||R|||[current\_date\_time] + +In step 11, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Enum-Observed-Value-Basic-Bit-Str attribute is present: + +- Object: Device & Sensor annunciation enumeration object +- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662) +- Attribute-type: BITS-16 +- Attribute-value: 4096 (dec) or 0x1000 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check + +OBX[?][NM][8417752^MDC\_GLU\_METER\_DEV\_STATUS^MDC][1.0.0.a][1^sensor-strip-insertion(3)]|||||R|||[current\_date\_time] + +In step 13, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Enum-Observed-Value-Basic-Bit-Str attribute is present: + +- Object: Device & Sensor annunciation enumeration object +- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662) +- Attribute-type: BITS-16 +- Attribute-value: 2048(dec) or 0x0800 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check + +OBX[?][NM][8417752^MDC\_GLU\_METER\_DEV\_STATUS^MDC][1.0.0.a][1^sensor-strip-type-incorrect(4)]|||||R|||[current\_date\_time] + +In step 15, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Enum-Observed-Value-Basic-Bit-Str attribute is present: + +- Object: Device & Sensor annunciation enumeration object +- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662) +- Attribute-type: BITS-16 +- Attribute-value: 1024 (dec) or 0x0400 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check + +OBX[?][NM][8417752^MDC\_GLU\_METER\_DEV\_STATUS^MDC][1.0.0.a][1^sensor-result-too-high(5)]|||||R|||[current\_date\_time] 1^(5) + +In step 17, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Enum-Observed-Value-Basic-Bit-Str attribute is present: + +- Object: Device & Sensor annunciation enumeration object +- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662) +- Attribute-type: BITS-16 + +- Attribute-value: 512(dec) or 0x0200 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check + +OBX[?][NM][8417752^MDC\_GLU\_METER\_DEV\_STATUS^MDC][1.0.0.a][1^sensor-result-too-low(6)]|||||R|||[current\_date\_time] + +In step 19, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Enum-Observed-Value-Basic-Bit-Str attribute is present: + +- Object: Device & Sensor annunciation enumeration object +- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662) +- Attribute-type: BITS-16 +- Attribute-value: 256 (dec) or 0x0100 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check + +OBX[?][NM][8417752^MDC\_GLU\_METER\_DEV\_STATUS^MDC][1.0.0.a][1^sensor-temp-too-high(7)]|||||R|||[current\_date\_time] + +In step 21, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Enum-Observed-Value-Basic-Bit-Str attribute is present: + +- Object: Device & Sensor annunciation enumeration object +- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662) +- Attribute-type: BITS-16 +- Attribute-value: 128 (dec) or 0x0080 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check + +OBX[?][NM][8417752^MDC\_GLU\_METER\_DEV\_STATUS^MDC][1.0.0.a][1^sensor-temp-too-low(8)]|||||R|||[current\_date\_time] + +In step 23, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Enum-Observed-Value-Basic-Bit-Str attribute is present: + +- Object: Device & Sensor annunciation enumeration object +- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662) +- Attribute-type: BITS-16 +- Attribute-value: 64 (dec) or 0x0040 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check + +OBX[?][NM][8417752^MDC\_GLU\_METER\_DEV\_STATUS^MDC][1.0.0.a][1^sensor-read-interrupt(9)]|||||R|||[current\_date\_time] + +In step 25, possible values in typical points of observation after transcoder output are: + +#### a) IEEE 11073 Objects and Attributes + +Enum-Observed-Value-Basic-Bit-Str attribute is present: + +- Object: Device & Sensor annunciation enumeration object +- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662) + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-type: BITS-16
    • Attribute-value: 32 (dec) or 0x0020 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Basic-Bit-Str attribute value. Check

    OBX ? NM 8417752^MDC_GLU_METER_DEV_STATUS^MDC 1.0.0.a 1^device-gen-fault(10) R [current_date_time]

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-051 | | | | +| TP label | Whitepaper. Glucosemeter Device & Sensor Annunciation Enumeration Object value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Enumeration 4; M | GL Enumeration 5; M | Date-Time Conv 1; M | +| Test purpose |

    Check that:

    PHG processes correctly the Device & Sensor Annunciation Value and Base Time fields of Glucose Measurement characteristic

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 AND C_MAN_BLE_012 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the measurement to the PHG under test with the following value:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00001010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location, and Sensor Status Annunciation fields are included. Time Offset field is not included. Context information does not follow
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 11:08:25
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
    | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: Not relevant
    vi. Field: Glucose Concentration - units of mol/L
    • • This field is not included
    vii. Field: Type
    • • Format: nibble
    • • Value: Not relevant
    viii. Field: Sample Location
    • • Format: nibble
    • • Value: Not relevant
    ix. Field: Sensor Status Annunciation
    • • Format: 16 bit
    • • Value: device battery low (0000000000000001 MSB → LSB)
    5. Check that the PHG accepts the measurement and decodes its value properly (sensor status annunciation and base time). | +| Pass/Fail criteria | In step 5, the PHG under test shows the following 'Sensor Status Annunciation' device battery low (0000000000000001) with the time stamp '2012-08-02 11:08:25'. | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-052 | | | +| TP label | Whitepaper. Glucosemeter Context Meal Enumeration Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 6; O | | +| Test purpose | Check that:
    PHG does not include Context Meal Enumeration object, Handle Attribute in transcoder output
    [OR]
    If PHG includes Context Meal Enumeration object, Handle attribute in transcoder output, then its value shall be different than 0 | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_013 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
    a. Glucose measurement context (0x2A34)
    i. Field: Flags
    • • Format: 8 bit
    • • Value: 0000 0010 (MSB → LSB). Meal is included and Carbohydrate ID, Carbohydrate, Tester-Health, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
    ii. Field: Sequence number
    • • Format: uint16
    • • Value: Not relevant
    iii. Field: Extended Flags | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate - units of kilograms

    • • This field is not included

    vi. Field: Meal

    • • Format: uint8
    • • Value: Not relevant

    vii. Field: Tester

    • • This field is not included

    viii. Field: Health

    • • This field is not included

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Medication – units of kilograms

    • • This field is not included

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context meal enumeration object, Handle attribute.

    | +| Pass/Fail criteria | In step 5, the Context meal enumeration object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Context meal enumeration object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Handle attribute value.

    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-053 | | | +| TP label | Whitepaper. Glucosemeter Context Meal Enumeration Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 7; M | | +| Test purpose | Check that:
    PHG includes Context Meal Enumeration object, Type attribute in transcoder output.
    [AND]
    Type is set to { MDC_PART_PHD_DM MDC_CTXT_GLU_MEAL } | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_013 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Meal is included and Carbohydrate ID, Carbohydrate, Tester-Health, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate - units of kilograms
          • • This field is not included
        6. vi. Field: Meal
          • • Format: uint8
          • • Value: Not relevant
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Medication – units of kilograms
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • This field is not included

    xiii. Medication – units of litres

    • This field is not included

    xiv. Field: HbA1c

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context meal enumeration object, Type attribute.

    | +| Pass/Fail criteria | In step 5, the Context meal enumeration object, Type attribute is present and its value is { MDC_PART_PHD_DM MDC_CTXT_GLU_MEAL }. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Context meal object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • code: MDC_CTXT_GLU_MEAL or 29256 (dec) or 7248 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX[?] CWE 8417864^MDC_CTXT_GLU_MEAL^MDC 1.0.0.7
    8417868^MDC_CTXT_GLU_MEAL_PREPRANDIAL^MDC R [current_date_time]

    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-054 | | | +| TP label | Whitepaper. Glucosemeter Context Meal Enumeration Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 8; M | | +| Test purpose |

    Check that:

    PHG includes Context Meal Enumeration object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF048 (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual)}.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_013 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:

    a. Glucose measurement context (0x2A34)

    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0010 (MSB → LSB). Meal is included and Carbohydrate ID, Carbohydrate, Tester-Health, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
    2. ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    3. iii. Field: Extended Flags
      • • This field is not included
    4. iv. Field: Carbohydrate ID
      • • This field is not included
    5. v. Field: Carbohydrate - units of kilograms
      • • This field is not included
    6. vi. Field: Meal
      • • Format: uint8
      • • Value: Not relevant
    7. vii. Field: Tester
      • • This field is not included
    8. viii. Field: Health
      • • This field is not included
    9. ix. Field: Exercise Duration
      • • This field is not included
    10. x. Field: Exercise Intensity
      • • This field is not included
    11. xi. Field: Medication ID
      • • This field is not included
    12. xii. Medication – units of kilograms
      • • This field is not included
    13. xiii. Medication – units of litres
      • • This field is not included
    14. xiv. Field: HbA1c
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.
    3. 5. Check in PHG transcoder output for the Context meal enumeration object, Metric-Spec-Small attribute.
    | +| Pass/Fail criteria | In step 5, the Context meal enumeration object, Metric-Spec-Small attribute is present and its value is {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Metric-Spec-Small attribute is present:

    • Object: Context meal numeric object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 48 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-manual(12) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-055 | | | +| TP label | Whitepaper. Glucosemeter Context Meal Enumeration Object - Absolute-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 9; M | Date-Time Conv 2; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | +| Test purpose |

    Check that:

    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into Context Meal Enumeration Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_013 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location and Time Offset fields are included. Sensor Status Annunciation field is not included. Context information follows
        2. ii. Field: Sequence number
          • • Format: uint16
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: Not relevant
    • iii. Field: Base Time
      • • Format: Date and Time
      • • Value: August 2nd, 2012, 10:59:27
    • iv. Field: Time Offset
      • • Format: sint16
      • • Value: 120 minutes
    • v. Field: Glucose Concentration - units of kg/L
      • • Format: SFLOAT
      • • Value: Not relevant
    • vi. Field: Glucose Concentration - units of mol/L
      • • This field is not included
    • vii. Field: Type
      • • Format: nibble
      • • Value: Not relevant
    • viii. Field: Sample Location
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Sensor Status Annunciation
      • • This field is not included

    b. Glucose measurement context (0x2A34)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0010 (MSB → LSB). Meal is included and Carbohydrate ID, Carbohydrate, Tester-Health, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate - units of kilograms
      • • This field is not included
    • vi. Field: Meal
      • • Format: uint8
      • • Value: Not relevant
    • vii. Field: Tester
      • • This field is not included
    • viii. Field: Health
      • • This field is not included
    • ix. Field: Exercise Duration
      • • This field is not included
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • This field is not included
    • xii. Medication – units of kilograms
      • • This field is not included
    • xiii. Medication – units of litres
      • • This field is not included
    • xiv. Field: HbA1c
      • • This field is not included

    5. Check in PHG transcoder output for the Context meal enumeration object, Absolute-Time-Stamp attribute.

    | +| Pass/Fail criteria | In step 5, the Context meal enumeration object, Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field in conjunction with the Time Offset field of the Glucose measurement characteristic and the fraction of seconds is set to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Context meal object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 12 (hex) or 18 (dec)
      • • minute: 59 (hex) or 89 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value:

    OBX ? CWE 8417864^MDC_CTXT_GLU_MEAL^MDC 1.0.0.7 8417868^ MDC_CTXT_GLU_MEAL_PREPRANDIAL^MDC    R  20120802125927+0000
    | + +| | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-056 | | | +| TP label | Whitepaper. Glucosemeter Context Meal Enumeration Object - Enum-Observed-Value-Simple-OID Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 10; M | | +| Test purpose |

    Check that:

    PHG transcodes Context Meal value field of Glucose Measurement Context characteristic into Context Meal Enumeration Object - Enum-Observed-Value-Simple-OID attribute

    | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_013 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Meal is included and Carbohydrate ID, Carbohydrate, Tester-Health, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate - units of kilograms
          • • This field is not included
        6. vi. Field: Meal
          • • Format: uint8
          • • Value: Several values are checked in this test case
        7. vii. Field: Tester
          • • This field is not included
        8. viii. Field: Health
          • • This field is not included
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Medication – units of kilograms
          • • This field is not included
        13. xiii. Medication – units of litres
          • • This field is not included
        14. xiv. Field: HbA1c
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement followed by the Glucose measurement context [Meal field set to 0x01 = Preprandial (before meal)] to the PHG under test.

    1. 5. Check in PHG transcoder output for the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute.
    2. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Meal field set to 0x02 = Postprandial (after meal)] to the PHG under test.
    3. 7. Check in PHG transcoder output for the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute.
    4. 8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Meal field set to 0x03 = Fasting] to the PHG under test.
    5. 9. Check in PHG transcoder output for the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute.
    6. 10. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Meal field set to 0x04 = Casual] to the PHG under test.
    7. 11. Check in PHG transcoder output for the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute.
    8. 12. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Meal field set to 0x05 = Bedtime] to the PHG under test.
    9. 13. Check in PHG transcoder output for the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute.
    | +| Pass/Fail criteria |

    In step 5, the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Meal Value field of the Glucose measurement context characteristic: 0x1 (preprandial – before meal).

    In step 7, the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Meal Value field of the Glucose measurement context characteristic: 0x2 (postprandial – after meal).

    In step 9, the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Meal Value field of the Glucose measurement context characteristic: 0x3 (fasting).

    In step 11, the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Meal Value field of the Glucose measurement context characteristic: 0x4 (casual – snacks, drinks etc.).

    In step 13, the Context meal enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Meal Value field of the Glucose measurement context characteristic: 0x5 (bedtime).

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context meal enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_MEAL_PREPRANDIAL (29260) or 1 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417868^
    MDC_CTXT_GLU_MEAL_PREPRANDIAL^MDC

    In step 7, possible values in typical points of observation after transcoder output are:

    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context meal enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_MEAL_POSTPRANDIAL (29264) or 2 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417872^
    MDC_CTXT_GLU_MEAL_POSTPRANDIAL^MDC

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context meal enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_MEAL_FASTING (29268) or 3 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 =
    8417876^MDC_CTXT_GLU_MEAL_FASTING^MDC

    In step 11, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context meal enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_MEAL_CASUAL (29272) or 4 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417880^
    MDC_CTXT_GLU_MEAL_CASUAL^MDC

    In step 13, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context meal enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_MEAL_BEDTIME (29300) or 5 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417908
    ^MDC_CTXT_GLU_MEAL_BEDTIME^MDC

    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|-----------------|----------------------------------------------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-057 | +| TP label | Whitepaper. Glucosemeter Context Meal Enumeration Object value | + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|---------------------| +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | +| | Testable items | GL Enumeration 9; M | GL Enumeration 10; M | Date-Time Conv 1; M | +| Test purpose | Check that:

    PHG processes correctly the Context Meal Value and Base Time fields of Glucose Measurement and Glucose Measurement Context characteristics | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 AND C_MAN_BLE_013 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset fields and Sensor Status Annunciation field are not included and Context Information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 11:08:25
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ix. Field: Sensor Status Annunciation
      • • This field is not included

    b. Glucose measurement context (0x2A34)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0010 (MSB → LSB). Meal field is included and Carbohydrate ID, Carbohydrate, Tester-Health, Exercise Duration and Exercise Intensity, Medication ID, Medication Value, Extended Flags and HbA1c fields are not included
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate
      • • This field is not included
    • vi. Field: Meal
      • • Format: uint8
      • • Value: preprandial – before meal (1)
    • vii. Field: Tester
      • • This field is not included
    • viii. Field: Health
      • • This field is not included
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • This field is not included
    • xii. Field: Medication
      • • This field is not included
    • xiii. Field: HbA1c
      • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (Meal value and base time).

    | +| Pass/Fail criteria | In step 5, the PHG under test shows the following Meal preprandial – before meal (MDC_CTXT_GLU_MEAL_PREPRANDIAL or 29260) with the time stamp '2012-08-02 11:08:25'. | +| Notes | | + +| | | | +|-----------------|----------------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-058 | | +| TP label | Whitepaper. Glucosemeter Context Sample Location Enumeration Object - Handle Attribute | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--| +| | Testable items | GL Enumeration 11; O | | | +| Test purpose |

    Check that:

    PHG does not include Context Sample Location Enumeration object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Context Sample Location Enumeration object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_014 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included. Time Offset and Sensor Status Annunciation fields are not included. Context information does not follow
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Time Offset
          • • Value: Not relevant
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement to the PHG under test.
    5. Check in PHG transcoder output for the Context Sample Location Enumeration object, Handle attribute. | +| Pass/Fail criteria | In step 5, the Context Sample Location Enumeration object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Handle attribute is not present, or if it is present then:
    • Object: Context Sample Location Enumeration object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0
    b) WAN PCD-01 message
    PCD-01 message does not include segments with a Handle attribute value. | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-059 | | | +| TP label | Whitepaper. Glucosemeter Context Sample Location Enumeration Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 12; M | | +| Test purpose | Check that:
    PHG includes Context Sample Location Enumeration object, Type attribute in transcoder output.
    [AND]
    Type is set to { MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION } | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_014 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
    • a. Glucose measurement (0x2A18)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included. Time Offset and Sensor Status Annunciation fields are not included. Context information does not follow
      • ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      • iii. Field: Base Time
        • • Format: Date and Time
        • • Value: Not relevant
      • iv. Field: Time Offset
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    v. Field: Glucose Concentration - units of kg/L

    • • Format: SFLOAT
    • • Value: Not relevant

    vi. Field: Glucose Concentration - units of mol/L

    • • This field is not included

    vii. Field: Type

    • • Format: nibble
    • • Value: Not relevant

    viii. Field: Sample Location

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Sensor Status Annunciation

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement to the PHG under test.

    5. Check in PHG transcoder output for the Context Sample Location Enumeration object, Type attribute.

    | +| Pass/Fail criteria | In step 5, the Context Sample Location Enumeration object, Type attribute is present and its value is { MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION }. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Context Sample Location Enumeration object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION or 29236 (dec) or 7234 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX ? ? 8417844^MDC_CTXT_GLU_SAMPLELOCATION^MDC 1.0.0.a[[value]] 263872^MDC_DIM_G^MDC    R   current_date_time
    | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-060 | | | +| TP label | Whitepaper. Glucosemeter Context Sample Location Enumeration Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 13; M | | +| Test purpose |

    Check that:

    PHG includes Context Sample Location Enumeration object, Metric-Spec-Small attribute in transcoder output.

    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [AND]
    Metric-Spec-Small is set to {0xF048 (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual)}. | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_014 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included. Time Offset and Sensor Status Annunciation are not included. Context information does not follow
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement to the PHG under test.
    5. 5. Check in PHG transcoder output for the Context Sample Location Enumeration object, Metric-Spec-Small attribute.
    | +| Pass/Fail criteria | In step 5, the Context Sample Location Enumeration object, Metric-Spec-Small attribute is present and its value is {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | + +| | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Context Sample Location Enumeration object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 48 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-manual(12) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-061 | | | +| TP label | Whitepaper. Glucosemeter Context Sample Location Enumeration Object - Absolute-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 14; M | Date-Time Conv 2; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | +| Test purpose |

    Check that:

    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into Context Sample Location Enumeration Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_014 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00000011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location, Time Offset fields are included. Sensor Status Annunciation field is not included. Context information does not follow
        2. ii. Field: Sequence number
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Base Time

    • • Format: Date and Time
    • • Value: August 2nd, 2012, 10:59:27

    iv. Field: Time Offset

    • • Format: sint16
    • • Value: 120 minutes

    v. Field: Glucose Concentration - units of kg/L

    • • Format: SFLOAT
    • • Value: Not relevant

    vi. Field: Glucose Concentration - units of mol/L

    • • This field is not included

    vii. Field: Type

    • • Format: nibble
    • • Value: Not relevant

    viii. Field: Sample Location

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Sensor Status Annunciation

    • • This field is not included

    5. Check in PHG transcoder output for the Context Sample Location Enumeration object, Absolute-Time-Stamp attribute.

    | +| Pass/Fail criteria | In step 5, the Context Sample Location Enumeration object, Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field in conjunction with the Time Offset field of the Glucose measurement characteristic and the fraction of seconds is set to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Context Sample Location Enumeration object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 12 (hex) or 18 (dec)
      • • minute: 59 (hex) or 89 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value

    | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------| +| | (check OBX-14):
    OBX[?]? 8417844^MDC_CTXT_GLU_SAMPLELOCATION^MDC 1.0.0.a 130
    263872^MDC_DIM_G^MDC R 20120802 125927+0000 | +|--|------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-062 | | | +| TP label | Whitepaper. Glucosemeter Context Sample Location Enumeration Object - Enum-Observed-Value-Simple-OID Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 15; M | | +| Test purpose | Check that:

    PHG transcodes Context Sample Location value field of Glucose Measurement Context characteristic into Context Sample Location Enumeration Object - Enum-Observed-Value-Simple-OID attribute | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_014 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included. Time Offset and Sensor Status Annunciation fields are not included. Context information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Several values are checked in this test case
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    ix. Field: Sensor Status Annunciation

    • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sample Location ID field set to 0x01 = Finger] to the PHG under test.
    3. 5. Check in PHG transcoder output for the Context Sample Location Enumeration object - Enum-Observed-Value-Simple-OID attribute.
    4. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sample Location ID field set to 0x02 = Alternate Site Test (AST)] to the PHG under test.
    5. 7. Check in PHG transcoder output for the Context Sample Location Enumeration object - Enum-Observed-Value-Simple-OID attribute.
    6. 8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sample Location ID field set to 0x03 = Earlobe] to the PHG under test.
    7. 9. Check in PHG transcoder output for the Context Sample Location Enumeration object - Enum-Observed-Value-Simple-OID attribute.
    8. 10. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sample Location ID field set to 0x04 = Control Solution] to the PHG under test.
    9. 11. Check in PHG transcoder output for the Context Sample Location Enumeration object - Enum-Observed-Value-Simple-OID attribute.
    | +| Pass/Fail criteria |

    In step 5, the Context Sample Location Enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Sample Location Value field of the Glucose measurement characteristic: 0x1 (finger).

    In step 7, the Context Sample Location Enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Sample Location Value field of the Glucose measurement characteristic: 0x2 (alternate site test).

    In step 9, the Context Sample Location Enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Sample Location Value field of the Glucose measurement characteristic: 0x3 (earlobe).

    In step 11, the Context Sample Location Enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Sample Location Value field of the Glucose measurement characteristic: 0x4 (control solution).

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • ❑ Object: Context Sample Location Enumeration object
    • ❑ Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • ❑ Attribute-type: OID-Type(INT-U16)
    • ❑ Attribute-value: MDC_CTXT_GLU_SAMPLELOCATION_FINGER (29240) or 1 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-3 = 8417848^MDC_CTXT_GLU_SAMPLELOCATION_FINGER ^MDC

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Object: Context Sample Location Enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_SAMPLELOCATION_AST (29244) or 2 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-3 = 8417852^MDC_CTXT_GLU_SAMPLELOCATION_AST^MDC

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context Sample Location Enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE (29248) or 3 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-3 = 8417856^MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE^MDC

    In step 11, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context Sample Location Enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_SAMPLELOCATION_CTLSOLUTION(29252) or 4 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-3 = 8417860^MDC_CTXT_GLU_SAMPLELOCATION_CTLSOLUTION^MDC

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-063 | | | +| TP label | Whitepaper. Glucosemeter Context Sample Location Enumeration Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 14; M | GL Enumeration 15; M | +| Test purpose | Check that:

    PHG processes correctly the Context Sample Location Value and Base Time fields of Glucose Measurement characteristic | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 AND C_MAN_BLE_014 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The simulated PHD implements several BLE characteristics. The characteristic of | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    interest for this test case is:

    a. Glucose measurement (0x2A18)

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement [Sample Location field set to 0x0001 = Finger] followed by the Glucose measurement context to the PHG under test:

    a. Glucose measurement (0x2A18)

    • i. Field: Flags
      • Format: 8 bit
      • Value: 00000010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included. Time Offset and Sensor Status Annunciation fields are not included. Context information does not follow
    • ii. Field: Sequence number
      • Format: uint16
      • Value: Not relevant
    • iii. Field: Base Time
      • Format: Date and Time
      • Value: August 2nd, 2012, 11:08:25
    • iv. Field: Time Offset
      • This field is not included
    • v. Field: Glucose Concentration - units of kg/L
      • Format: SFLOAT
      • Value: Not relevant
    • vi. Field: Glucose Concentration - units of mol/L
      • This field is not included
    • vii. Field: Type
      • Format: nibble
      • Value: Not relevant
    • viii. Field: Sample Location
      • Format: nibble
      • Value: finger (0001 MSB → LSB)
    • ix. Field: Sensor Status Annunciation
      • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (sample location and base time).

    | +| Pass/Fail criteria | In step 5, the PHG under test shows the following Sample Location finger (MDC_CTXT_GLU_SAMPLELOCATION_FINGER or 29240) with the time stamp '2012-08-02 11:08:25'. | +| Notes | | + +| | | | +|-----------------|-------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-064 | | +| TP label | Whitepaper. Glucosimeter Context Tester Enumeration Object - Handle Attribute | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--| +| | Testable items | GL Enumeration 16; O | | | +| Test purpose |

    Check that:

    PHG does not include Context Tester Enumeration object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Context Tester Enumeration object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_015 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate - units of kilograms
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Health
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Medication – units of kilograms
          • • This field is not included
    | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xiii. Medication – units of litres

    • This field is not included

    xiv. Field: HbA1c

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context tester enumeration object, Handle attribute.

    | +| Pass/Fail criteria | In step 5, the Context tester enumeration object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Context tester enumeration object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value other than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Handle attribute value.

    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-065 | | | +| TP label | Whitepaper. Glucosemeter Context Tester Enumeration Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 17; M | | +| Test purpose |

    Check that:

    PHG includes Context Tester Enumeration object, Type attribute in transcoder output.

    [AND]

    Type is set to { MDC_PART_PHD_DM MDC_CTXT_GLU_TESTER }

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_015 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:

    a. Glucose measurement context (0x2A34)

    i. Field: Flags

    • Format: 8 bit
    • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included

    ii. Field: Sequence number

    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: uint16
    • • Value: Not relevant

    iii. Field: Extended Flags

    • • This field is not included

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate - units of kilograms

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • Format: nibble
    • • Value: Not relevant

    viii. Field: Health

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Medication – units of kilograms

    • • This field is not included

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context tester enumeration object, Type attribute.

    | +| Pass/Fail criteria | In step 5, the Context tester enumeration object, Type attribute is present and its value is { MDC_PART_PHD_DM MDC_CTXT_GLU_TESTER }. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Context Tester object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
    • code: MDC_CTXT_GLU_TESTER or 29276 (dec) or 72 5C (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX ? CWE 8417884^MDC_CTXT_GLU_TESTER^MDC 1.0.0.7
    8417888^MDC_CTXT_GLU_TESTER_SELF^MDC R [current_date_time]

    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-066 | | | +| TP label | Whitepaper. Glucosemeter Context Tester Enumeration Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 18; M | | +| Test purpose |

    Check that:

    PHG includes Context Tester Enumeration object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF048 (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual)}.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_015 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. Glucose measurement context (0x2A34)
        1. Field: Flags
          • Format: 8 bit
          • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. Field: Sequence number
          • Format: uint16
          • Value: Not relevant
        3. Field: Extended Flags
          • This field is not included
        4. Field: Carbohydrate ID
          • This field is not included
        5. Field: Carbohydrate - units of kilograms
          • This field is not included
        6. Field: Meal
          • This field is not included
        7. Field: Tester
          • Format: nibble
          • Value: Not relevant
        8. Field: Health
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Medication – units of kilograms

    • • This field is not included

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context tester enumeration object, Metric-Spec-Small attribute.

    | +| Pass/Fail criteria | In step 5, the Context tester enumeration object, Metric-Spec-Small attribute is present and its value is {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Context tester enumeration object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 48 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-manual(12) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-067 | | | +| TP label | Whitepaper. Glucosemeter Context Tester Enumeration Object - Absolute-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 19; M | Date-Time Conv 2; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | +| Test purpose |

    Check that:

    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into Context Tester Enumeration Object - Absolute-Time-Stamp attribute

    | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    [AND]

    PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_015 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location, Time Offset fields are included. Sensor Status Annunciation field is not included. Context information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:59:27
        4. iv. Field: Time Offset
          • • Format: sint16
          • • Value: 120 minutes
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ix. Field: Sensor Status Annunciation
      • • This field is not included
    • b. Glucose measurement context (0x2A34)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
      • ii. Field: Sequence number
        • • Format: uint16
        • • Value: Not relevant
      • iii. Field: Extended Flags
        • • This field is not included
      • iv. Field: Carbohydrate ID
        • • This field is not included
      • v. Field: Carbohydrate – units of kilograms
        • • This field is not included
      • vi. Field: Meal
        • • This field is not included
      • vii. Field: Tester
        • • Format: nibble
        • • Value: Not relevant
      • viii. Field: Health
        • • Format: nibble
        • • Value: Not relevant
      • ix. Field: Exercise Duration
        • • This field is not included
      • x. Field: Exercise Intensity
        • • This field is not included
      • xi. Field: Medication ID
        • • This field is not included
      • xii. Medication – units of kilograms
        • • This field is not included
      • xiii. Medication – units of litres
        • • This field is not included
      • xiv. Field: HbA1c
        • • This field is not included

    5. Check in PHG transcoder output for the Context tester enumeration object, Absolute-Time-Stamp attribute.

    | +| Pass/Fail criteria |

    In step 5, the Context tester enumeration object, Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field in conjunction with the Time Offset field of the Glucose measurement characteristic and the fraction of seconds is set to 0.

    | +| Notes |

    Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Absolute-Time-Stamp attribute is present:

    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Object: Context tester enumeration object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 12 (hex) or 18 (dec)
      • • minute: 59 (hex) or 89 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value:

    OBX ? CWE 8417884^MDC_CTXT_GLU_TESTER^MDC 1.0.0.7  8417888^MDC_CTXT_GLU_TESTER_SELF^MDC   R  20120802125927+0000
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-068 | | | +| TP label | Whitepaper. Glucosemeter Context Tester Enumeration Object - Enum-Observed-Value-Simple-OID Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 20; M | | +| Test purpose | Check that:

    PHG transcodes Context Tester value field of Glucose Measurement Context characteristic into Context Tester Enumeration Object - Enum-Observed-Value-Simple-OID attribute | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_015 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    iv. Field: Carbohydrate ID

    • • This field is not included

    v. Field: Carbohydrate - units of kilograms

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • Format: nibble
    • • Value: Several values are checked in this test case

    viii. Field: Health

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Medication – units of kilograms

    • • This field is not included

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context [Tester field set to 0x01 = Self] to the PHG under test.

    5. Check in PHG transcoder output for the Context tester enumeration object - Enum-Observed-Value-Simple-OID attribute.

    6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Tester field set to 0x02 = Health Care Professional] to the PHG under test.

    7. Check in PHG transcoder output for the Context tester enumeration object - Enum-Observed-Value-Simple-OID attribute.

    8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Tester field set to 0x03 = Lab test] to the PHG under test.

    9. Check in PHG transcoder output for the Context tester enumeration object - Enum-Observed-Value-Simple-OID attribute.

    | +| Pass/Fail criteria |

    In step 5, the Context tester enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Tester Value field of the Glucose measurement context characteristic: 0x1 (self).

    In step 7, the Context tester enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Tester Value field of the Glucose

    | + +| | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement context characteristic: 0x2 (Health Care Professional).

    In step 9, the Context tester enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Tester Value field of the Glucose measurement context characteristic: 0x3 (Lab test).

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context tester enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_TESTER_SELF (29280) or 1 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417888^MDC_CTXT_GLU_TESTER_SELF^MDC

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context tester enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_TESTER_HCP (29284) or 2 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417892^MDC_CTXT_GLU_TESTER_HCP^MDC

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context tester enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_TESTER_LAB (29288) or 3 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417896^MDC_CTXT_GLU_TESTER_LAB^MDC

    | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-069 | | | +| TP label | Whitepaper. Glucosemeter Context Tester Enumeration Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 19; M | GL Enumeration 20; M | +| Test purpose |

    Check that:

    PHG processes correctly the Context Tester Value and Base Time fields of Glucose Measurement and Glucose Measurement Context characteristics

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 AND C_MAN_BLE_015 | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset fields and Sensor Status Annunciation field are not included and Context Information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          1. ii. Format: Date and Time
            • • Value: August 2nd, 2012, 11:08:25
        4. iv. Field: Time Offset
          • • This field is not included
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
      2. b. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0100 (MSB → LSB). Tester and Health fields are included and
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Carbohydrate ID, Carbohydrate, Meal, Exercise Duration and Exercise Intensity, Medication ID, Medication Value, Extended Flags and HbA1c fields are not included

    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate
      • • This field is not included
    • vi. Field: Meal
      • • This field is not included
    • vii. Field: Tester
      • • Format: nibble
      • • Value: self (0001 MSB → LSB)
    • viii. Field: Health
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • This field is not included
    • xii. Field: Medication
      • • This field is not included
    • xiii. Field: HbA1c
      • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (Tester value and base time).

    | +| Pass/Fail criteria | In step 5, the PHG under test shows the following Tester self (MDC_CTXT_GLU_TESTER_SELF or 29280) with the time stamp '2012-08-02 11:08:25'. | +| Notes | | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-070 | | | +| TP label | Whitepaper. Glucosemeter Context Health Enumeration Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 21; O | | +| Test purpose | Check that:

    PHG does not include Context Health Enumeration object, Handle Attribute in transcoder output

    [OR] | | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | If PHG includes Context Health Enumeration object, Handle attribute in transcoder output, then its value shall be different than 0 | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_016 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucosemeter profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate - units of kilograms
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Health
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
        11. xi. Field: Medication ID
          • • This field is not included
        12. xii. Medication – units of kilograms
          • • This field is not included
        13. xiii. Medication – units of litres
          • • This field is not included
        14. xiv. Field: HbA1c
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    1. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.
    2. 5. Check in PHG transcoder output for the Context health enumeration object, Handle attribute.
    | +| Pass/Fail criteria | In step 5, the Context tester enumeration object, Handle attribute is not present; however, if it is present then its value is different to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes
      Handle attribute is not present, or if it is present then:
      • Object: Context health enumeration object
      • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
      • Attribute-type: INT-U16
      • Attribute-value: Any value other than 0
    2. b) WAN PCD-01 message
      PCD-01 message does not include segments with a Handle attribute value.
    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-071 | | | +| TP label | Whitepaper. Glucosemeter Context Health Enumeration Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 22; M | | +| Test purpose |

    Check that:

    PHG includes Context Tester Enumeration object, Type attribute in transcoder output.

    [AND]

    Type is set to { MDC_PART_PHD_DM MDC_CTXT_GLU_HEALTH }

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_016 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    v. Field: Carbohydrate - units of kilograms

    • • This field is not included

    vi. Field: Meal

    • • This field is not included

    vii. Field: Tester

    • • Format: nibble
    • • Value: Not relevant

    viii. Field: Health

    • • Format: nibble
    • • Value: Not relevant

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Medication – units of kilograms

    • • This field is not included

    xiii. Medication – units of litres

    • • This field is not included

    xiv. Field: HbA1c

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context health enumeration object, Type attribute.

    | +| Pass/Fail criteria | In step 5, the Context tester enumeration object, Type attribute is present and its value is { MDC_PART_PHD_DM MDC_CTXT_GLU_HEALTH }. | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Context Health object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_HEALTH or 29212 (dec) or 72 1C (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):

    OBX ? CWE 8417820 ^MDC_CTXT_GLU_HEALTH^MDC 1.0.0.7  8417824^MDC_CTXT_GLU_HEALTH_MINOR^MDC     R    [current_date_time]
    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-072 | | | +| TP label | Whitepaper. Glucosemeter Context Health Enumeration Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 23; M | | +| Test purpose |

    Check that:

    PHG includes Context Health Enumeration object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF048 (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual)}.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_016 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Extended Flags
          • • This field is not included
        4. iv. Field: Carbohydrate ID
          • • This field is not included
        5. v. Field: Carbohydrate - units of kilograms
          • • This field is not included
        6. vi. Field: Meal
          • • This field is not included
        7. vii. Field: Tester
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Health
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Exercise Duration
          • • This field is not included
        10. x. Field: Exercise Intensity
          • • This field is not included
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xi. Field: Medication ID

    • This field is not included

    xii. Medication – units of kilograms

    • This field is not included

    xiii. Medication – units of litres

    • This field is not included

    xiv. Field: HbA1c

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test.

    5. Check in PHG transcoder output for the Context health enumeration object, Metric-Spec-Small attribute.

    | +| Pass/Fail criteria | In step 5, the Context health enumeration object, Metric-Spec-Small attribute is present and its value is {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Context health enumeration object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 48 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-manual(12) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with a Metric-Spec-Small attribute value.

    | + +| | | | | | | +|----------------------|--------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-073 | | | | | +| TP label | Whitepaper. Glucosemeter Context Health Enumeration Object - Absolute-Time-Stamp Attribute | | | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | | | +| | Testable items | GL Enumeration 24; M | Date-Time Conv 2; M | | | +| Test purpose | | Date-Time Conv 4; M | Date-Time Conv 5; M | | | +| | |

    Check that:

    PHG transcodes Base Time field in conjunction with Time Offset field of Glucose Measurement characteristic into Context Health Enumeration Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Base Time field in conjunction with Time Offset field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_016 | | | | | +| Other PICS | | | | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 00010011 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location, Time Offset fields are included. Sensor Status Annunciation field is not included. Context information follows
        2. ii. Field: Sequence number
          • • Format: uint16
          • • Value: Not relevant
        3. iii. Field: Base Time
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:59:27
        4. iv. Field: Time Offset
          • • Format: sint16
          • • Value: 120 minutes
        5. v. Field: Glucose Concentration - units of kg/L
          • • Format: SFLOAT
          • • Value: Not relevant
        6. vi. Field: Glucose Concentration - units of mol/L
          • • This field is not included
        7. vii. Field: Type
          • • Format: nibble
          • • Value: Not relevant
        8. viii. Field: Sample Location
          • • Format: nibble
          • • Value: Not relevant
        9. ix. Field: Sensor Status Annunciation
          • • This field is not included
      2. b. Glucose measurement context (0x2A34)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity,
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Medication ID, Medication Value and HbA1c fields are not included

    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate - units of kilograms
      • • This field is not included
    • vi. Field: Meal
      • • This field is not included
    • vii. Field: Tester
      • • Format: nibble
      • • Value: Not relevant
    • viii. Field: Health
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Exercise Duration
      • • This field is not included
    • x. Field: Exercise Intensity
      • • This field is not included
    • xi. Field: Medication ID
      • • This field is not included
    • xii. Medication – units of kilograms
      • • This field is not included
    • xiii. Medication – units of litres
      • • This field is not included
    • xiv. Field: HbA1c
      • • This field is not included

    5. Check in PHG transcoder output for the Context health enumeration object, Absolute-Time-Stamp attribute.

    | +| Pass/Fail criteria | In step 5, the Context health enumeration object, Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field in conjunction with the Time Offset field of the Glucose measurement characteristic and the fraction of seconds is set to 0. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Context tester enumeration object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • year: 12 (hex) or 18 (dec)
    • month: 08 (hex) or 8 (dec)
    • day: 02 (hex) or 2 (dec)
    • hour: 12 (hex) or 18 (dec)
    • minute: 59 (hex) or 89 (dec)
    • second: 27 (hex) or 39 (dec)
    • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value:

    OBX[?][CWE][8417820^MDC_CTXT_GLU_HEALTH^MDC 1.0.0.7
    8417824^MDC_CTXT_GLU_HEALTH_MINOR^MDC R 20120802125927+0000

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-074 | | | +| TP label | Whitepaper. Glucosemeter Context Health Enumeration Object - Enum-Observed-Value-Simple-OID Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 25; M | | +| Test purpose |

    Check that:

    PHG transcodes Context Health value field of Glucose Measurement Context characteristic into Context Health Enumeration Object - Enum-Observed-Value-Simple-OID attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_007 AND C_MAN_BLE_016 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. Glucose measurement context (0x2A34)
        1. Field: Flags
          • Format: 8 bit
          • Value: 0000 0100 (MSB → LSB). Tester-Health is included and Meal, Carbohydrate ID, Carbohydrate, Exercise Duration, Exercise Intensity, Medication ID, Medication Value and HbA1c fields are not included
        2. Field: Sequence number
          • Format: uint16
          • Value: Not relevant
        3. Field: Extended Flags
          • This field is not included
        4. Field: Carbohydrate ID
          • This field is not included
        5. Field: Carbohydrate - units of kilograms
          • This field is not included
        6. Field: Meal
          • This field is not included
        7. Field: Tester
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: nibble
    • • Value: Not relevant
    viii. Field: Health
    • • Format: nibble
    • • Value: Several values are checked in this test case
    ix. Field: Exercise Duration
    • • This field is not included
    x. Field: Exercise Intensity
    • • This field is not included
    xi. Field: Medication ID
    • • This field is not included
    xii. Medication – units of kilograms
    • • This field is not included
    xiii. Medication – units of litres
    • • This field is not included
    xiv. Field: HbA1c
    • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context [Health field set to 0x01 = Minor health issues] to the PHG under test.
    3. 5. Check in PHG transcoder output for the Context HealthEnumeration object - Enum-Observed-Value-Simple-OID attribute.
    4. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Health field set to 0x02 = Major Health Issues] to the PHG under test.
    5. 7. Check in PHG transcoder output for the Context HealthEnumeration object - Enum-Observed-Value-Simple-OID attribute.
    6. 8. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Health field set to 0x03 = Menses] to the PHG under test.
    7. 9. Check in PHG transcoder output for the Context HealthEnumeration object - Enum-Observed-Value-Simple-OID attribute
    8. 10. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Health field set to 0x04 = Under stress] to the PHG under test.
    9. 11. Check in PHG transcoder output for the Context health enumeration object - Enum-Observed-Value-Simple-OID attribute.
    10. 12. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement context [Health field set to 0x05 = No health issues] to the PHG under test.
    11. 13. Check in PHG transcoder output for the Context health enumeration object - Enum-Observed-Value-Simple-OID attribute.
    | +| Pass/Fail criteria | In step 5, the Context health enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Health Value field of the Glucose | + +| | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    measurement context characteristic: 0x1 (Minor health issues).

    In step 7, the Context health enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Health Value field of the Glucose measurement context characteristic: 0x2 (Major health issues).

    In step 9, the Context health enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Health Value field of Glucose measurement context characteristic: 0x3 (Menses).

    In step 11, the Context health enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Health Value field of Glucose measurement context characteristic: 0x4 (Under stress).

    In step 13, the Context health enumeration object - Enum-Observed-Value-Simple-OID attribute is present and its value matches with the Context Health Value field of Glucose measurement context characteristic: 0x5 (No health issues).

    | +| Notes |

    In step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context health enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_HEALTH_MINOR (29216) or 1 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417824^MDC_CTXT_GLU_HEALTH_MINOR^MDC

    In step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context HealthEnumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_HEALTH_MAJOR (29220)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417828^MDC_CTXT_GLU_HEALTH_MAJOR^MDC

    In step 9, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context HealthEnumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_HEALTH_MENSES(29224)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417832^MDC_CTXT_GLU_HEALTH_MENSES^MDC

    In step 11, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Object: Context health enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_HEALTH_STRESS (29228)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 =

    8417836^MDC_CTXT_GLU_HEALTH_STRESS^MDC

    In step 13, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-OID attribute is present:

    • Object: Context health enumeration object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_OID (2633)
    • Attribute-type: OID-Type(INT-U16)
    • Attribute-value: MDC_CTXT_GLU_HEALTH_NONE (29232)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with an Enum-Observed-Value-Simple-OID attribute value. Check OBX-2 = CWE AND OBX-5 = 8417840

    ^MDC_CTXT_GLU_HEALTH_NONE^MDC

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/GL/BV-075 | | | +| TP label | Whitepaper. Glucosemeter Context Health Enumeration Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.4] | | +| | Testable items | GL Enumeration 24; M | GL Enumeration 25; M | +| | | | Date-Time Conv 1; M | +| Test purpose | Check that:

    PHG processes correctly the Context Health Value and Base Time fields of Glucose Measurement and Glucose Measurement Context characteristics | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_007 AND C_MAN_BLE_016 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Glucose profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is:
      1. a. Glucose measurement (0x2A18)
      2. b. Glucose measurement context (0x2A34)
    3. 3. The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), the PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends a Glucose measurement followed by the Glucose measurement context to the PHG under test. The measurement of interest for this test case are:
      1. a. Glucose measurement (0x2A18)
        1. i. Field: Flags
          • • Format: 8 bit
    | | | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 00010010 (MSB → LSB). Glucose concentration in units of kg/L, Type and Sample Location fields are included, Time Offset fields and Sensor Status Annunciation field are not included and Context Information follows
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Base Time
    • iii. Format: Date and Time
      • • Value: August 2nd, 2012, 11:08:25
    • iv. Field: Time Offset
      • • This field is not included
    • v. Field: Glucose Concentration - units of kg/L
      • • Format: SFLOAT
      • • Value: Not relevant
    • vi. Field: Glucose Concentration - units of mol/L
      • • This field is not included
    • vii. Field: Type
      • • Format: nibble
      • • Value: Not relevant
    • viii. Field: Sample Location
      • • Format: nibble
      • • Value: Not relevant
    • ix. Field: Sensor Status Annunciation
      • • This field is not included

    b. Glucose measurement context (0x2A34)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0100 (MSB → LSB). Tester and Health fields are included and Carbohydrate ID, Carbohydrate, Meal, Exercise Duration and Exercise Intensity, Medication ID, Medication Value, Extended Flags and HbA1c fields are not included
    • ii. Field: Sequence number
      • • Format: uint16
      • • Value: Not relevant
    • iii. Field: Extended Flags
      • • This field is not included
    • iv. Field: Carbohydrate ID
      • • This field is not included
    • v. Field: Carbohydrate
      • • This field is not included
    • vi. Field: Meal
      • • This field is not included
    • vii. Field: Tester
      • • Format: nibble
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: Not relevant

    viii. Field: Health

    • • Format: nibble
    • • Value: minor health issues (0001 MSB → LSB)

    ix. Field: Exercise Duration

    • • This field is not included

    x. Field: Exercise Intensity

    • • This field is not included

    xi. Field: Medication ID

    • • This field is not included

    xii. Field: Medication

    • • This field is not included

    xiii. Field: HbA1c

    • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (Health value and base time).

    | +| Pass/Fail criteria | In step 5, the PHG under test shows the following Health minor health issues (MDC_CTXT_GLU_HEALTH_MINOR or 29216) with the time stamp '2012-08-02 11:08:25'. | +| Notes | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-Bluetooth PHDT v1.3] Bluetooth SIG (2012), *Personal Health Devices Transcoding White Paper* (version 1.3). +[https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc\\_id=294540](https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=294540) +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-CDG 2017] Personal Connected Health Alliance, Continua Design Guidelines (2017), "Keratin", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.13. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.11. + +- [b-TI] PHD Testable items. Test Tool v8.0.0.0 – Excel sheet v1.10. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.850.5-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.850.5-202008-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4e950884dbed3c5e70b2e6828a73152219494cba --- /dev/null +++ b/marked/H/T-REC-H.850.5-202008-I_PDF-E/raw.md @@ -0,0 +1,1976 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.850.5** + +(08/2020) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 10E: Transcoding for Bluetooth Low +Energy: Personal Health Gateway – Weighing +scales** + +Recommendation ITU-T H.850.5 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.850.5 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10E: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Weighing scales + +## Summary + +Recommendation ITU-T H.850.5 provides a test suite structure (TSS) and the test purposes (TP) for the transcoding of weighing scales data by personal health gateways in the Personal Health Devices (PHD) interface of application-level data between the Bluetooth Low Energy Bluetooth Generic Attribute Profile (GATT) format and the IEEE 11073-20601 data format, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.850.5 is a transposition of clause 3.7 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.850.5 | 2017-04-29 | 16 | 11.1002/1000/13358 | +| 2.0 | ITU-T H.850.5 | 2020-08-13 | 16 | 11.1002/1000/14349 | + +## Keywords + +Bluetooth Generic Attribute Profile, Bluetooth Low Energy (BLE), Continua Design Guidelines, Conformance testing, data format transcoding, e-health, IEEE 11073-20601, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, Personal Health Gateway, touch area network, weighing scales. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|---------|-----------------------------------------------------------------|-----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 3 | +| 3.1 | Terms defined elsewhere ..... | 3 | +| 3.2 | Terms defined in this Recommendation..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Test suite structure..... | 6 | +| 7 | Electronic attachment ..... | 8 | +| Annex A | Test purposes ..... | 9 | +| A.1 | TP definition conventions..... | 9 | +| A.2 | Subgroup 2.4.6 – Whitepaper Weight scale requirements (WS)..... | 10 | +| | Bibliography..... | 133 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of clause 3.7 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2012-10-05 | Initial release for Test Tool DG2011 based on the requirements in [b-CDG 2011]. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. It uses "TSS&TP_DG2011_LP-PAN_PART_10_v1.0.doc" as a baseline and adds new features included in [b-CDG 2012] (BPM and HR profiles). | +| 1.2 | 2014-01-24 | Initial release for Test Tool DG2013. It uses "TSS&TP_DG2012_LP-PAN_PART_10_v1.1.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.3 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.2.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row has been added.
    | +| 1.4 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015]:
    • • Adds WS/BCA BLE device specialization
    • • Adds SABTE IEEE device specialization
    | +| 1.5 | 2016-01-26 | First maintenance release for Test Tool DG2015. It uses "TSS&TP_DG2015_LP-PAN_PART_10_v1.4.doc" as a baseline and adds some updates according to the Maintenance 2015 activity. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]:
    • • Adds PLX BLE device specialization
    • • Adds PLX CGM device specialization
    | +| 1.7 | 2017-07-18 | Second Maintenance Release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.6.doc" as a baseline and corrects minor typos. | +| 1.8 | 2020-06-02 | Updates related to the value of the Reg-Cert-Data-List according to [b-CDG 2017]. | + +## Recommendation ITU-T H.850.5 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10E: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Weighing scales + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 10E. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway. In addition to the main part, the document is subdivided in the following subparts: + - Part 10A: Whitepaper Thermometer requirements + - Part 10B: Whitepaper Blood pressure requirements + - Part 10C: Whitepaper Heart rate requirements + - Part 10D: Whitepaper Glucose meter requirements + - **Part 10E: Whitepaper Weighing scales requirements** + - Part 10F: Whitepaper Pulse oximeter requirements + - Part 10G: Whitepaper Continuous glucose monitoring requirements + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [Bluetooth PHDT v1.4] Bluetooth SIG (2013), *Personal Health Devices Transcoding White Paper, v1.4*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=294539](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=294539) +- [Bluetooth PHDT v1.5] Bluetooth SIG (2014), *Personal Health Devices Transcoding White Paper, v1.5*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=272346](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=272346) +- [Bluetooth PHDT v1.6] Bluetooth SIG (2015), *Personal Health Devices Transcoding White Paper, v1.6*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=310657](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=310657) +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization*. NOTE – Shorthand to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + +- [IHE PCD TF 1] IHE PCD TF 1 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 1: Integration Profiles*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol1\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol1_FT_2012-08-16.pdf) +- [IHE PCD TF 2] IHE PCD TF 2 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 2: Transactions*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol2\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol2_FT_2012-08-16.pdf) +- [IHE PCD TF 3] IHE PCD TF 3 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 3: Semantic Content*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol3\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol3_FT_2012-08-16.pdf) + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|--------------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| LSB | Least Significant Bit | +| MDS | Medical Device System | +| MSB | Most Significant Bit | + +| | | +|-------|-------------------------------------------------------| +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCD | Patient Care Device | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| RACP | Record Access Control Point | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purposes | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +## 5 Conventions + +In this text, the uppercase letter L is used as the symbol for litre. + +Several of the test purposes in Annex A refer to "WAN PCD-01 messages"; these messages are specified in the patient care device (PCD) technical framework defined in [IHE PCD TF 1], [IHE PCD TF 2] and [IHE PCD TF 3]. Similarly, the "IEEE 11073 Objects and Attributes" are defined in [ISO/IEEE 11073-104xx]. + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +In this document, hexadecimal numbers are denoted either with the prefix "0x" or by "(hex)" after the number; "(dec)" after a number indicates it is expressed in decimal format. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of ITU-T H.810 is split into eight parts in the ITU-T H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata. | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure + +The test purposes (TP) for the Personal Health Devices interface have been divided into the groups and subgroups specified below. Annex A describes the TPs for subgroup 2.4.6 (shown in bold). + +- Group 1: Personal Health Device (PHD) + - Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) + - Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) + - Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) + - Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + +- Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) +- Subgroup 2.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) +- **Subgroup 2.4.6: Whitepaper weight scale requirements (WS)** +- Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +## 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth low energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies a test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 2.4.6 – Whitepaper Weight scale requirements (WS) + +| | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-000 | | | +| TP label | Whitepaper. Weight Scale MDS Object - System-Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | WS Specific MDS 1; M | | +| Test purpose | Check that:
    PHG does not include MDS object, System-Type attribute in transcoder output. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated Personal Health Device (PHD) are in Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    4. Check in PHG transcoder output the MDS object, System-Type attribute
    | | | +| Pass/Fail criteria | In Step 4, the MDS object, System-Type attribute is not present. | | | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    System-Type attribute is not present:
    Object: MDS Object
    Attribute-id: MDC_ATTR_SYS_TYPE (2438)
    Attribute-type: TYPE
    Attribute-value:
    b) WAN PCD-01 message
    PCD-01 message does not include segments with System-Type attribute value (67974^MDC_ATTR_SYS_TYPE^MDC) | | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-001 | | | +| TP label | Whitepaper. Weight Scale MDS Object - Dev-Configuration-Id Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Common MDS 17; M | | +| Test purpose | Check that:
    PHG includes MDS object, Dev-Configuration-Id attribute in transcoder output.
    [AND]
    Dev-Configuration-Id value is set to any value in range of 0x4000 to 0x7FFF (Extended Configuration) | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | | | +| Other PICS | | | | +| Initial Condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The PHG under test initiates a discovery process (Scanning state), it discovers the
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    1. 3. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    2. 4. Check in PHG transcoder output the MDS object, Dev-Configuration-Id attribute
    | +| Pass/Fail criteria | In Step 4, the MDS object, Dev-Configuration-Id attribute is present, its value is inside the range 0x4000 - 0x7FFF | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes
      Dev-Configuration-Id attribute is present:
      • Object: MDS Object
      • Attribute-id: MDC_ATTR_DEV_CONFIG_ID (2628)
      • Attribute-type: INT-U16
      • Attribute-value: Any value inside the range 16384 - 32767 (dec) or 0x4000 – 0x7FFF (hex)
    2. b) WAN PCD-01 message
      According to Continua DG, the Dev-Configuration-Id shall not be transmitted in PCD-01 message, therefore it is not possible to check this attribute.
    | + +| | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-002 | | | +| TP label | Whitepaper. Weight Scale MDS Object - System-Type-Spec-List Attribute [Profile Scale] | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Common MDS 15; M | WS Specific MDS 2; M | +| Test purpose |

    Check that:

    PHG includes MDS object, System-Type-Spec-List attribute in transcoder output.

    [AND]

    System-Type-Spec-List is set to (MDC_DEV_SPEC_PROFILE_SCALE, Version 1)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_017 AND (NOT C_MAN_BLE_018) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable). It exposes only the Weight Scale Service.
    2. 2. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 3. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    4. 4. Check in PHG transcoder output the MDS object, System-Type-Spec-List attribute
    | | | +| Pass/Fail criteria | In Step 4, the MDS object, System-Type-Spec-List attribute is present, its value is (MDC_DEV_SPEC_PROFILE_SCALE, Version 1) | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes
      System-Type-Spec-List attribute is present:
      • Object: MDS Object
      • Attribute-id: MDC_ATTR_SYS_TYPE_SPEC_LIST (2650)
      • Attribute-type: SEQUENCE OF [ {type (INT-U16), version (INT-U16)} ]
      • Attribute-value:
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • type: MDC_DEV_SPEC_PROFILE_SCALE, 4111 (dec) or 10 0F (hex)
    • version: 1 (dec) or 00 01 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with System-Type-Spec-List attribute value (check OBX-5):

    OBX[?][NM][68186]^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a
    528399^MDC_DEV_SPEC_PROFILE_SCALE^MDC R

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-002_A | | | +| TP label | Whitepaper. Weight Scale MDS Object - System-Type-Spec-List Attribute [Profile BCA] | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Common MDS 15; M | WS Specific MDS 2; M | +| Test purpose |

    Check that:

    PHG includes MDS object, System-Type-Spec-List attribute in transcoder output.

    [AND]

    System-Type-Spec-List is set to (MDC_DEV_SPEC_PROFILE_BCA, Version 1)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_017 AND C_MAN_BLE_018 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable). It exposes both Weight Scale Service and Body Composition Service.
    2. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    4. Check in PHG transcoder output the MDS object, System-Type-Spec-List attribute
    | | | +| Pass/Fail criteria | In Step 4, the MDS object, System-Type-Spec-List attribute is present, its value is (MDC_DEV_SPEC_PROFILE_BCA, Version 1). | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    System-Type-Spec-List attribute is present:

    • Object: MDS Object
    • Attribute-id: MDC_ATTR_SYS_TYPE_SPEC_LIST (2650)
    • Attribute-type: SEQUENCE OF [ {type (INT-U16), version (INT-U16)} ]
    • Attribute-value:
      • type: MDC_DEV_SPEC_PROFILE_BCA, 4116 (dec) or 10 14 (hex)
      • version: 1 (dec) or 00 01 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with System-Type-Spec-List attribute value (check OBX-5):

    OBX[?][NM][68186]^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a
    528404^MDC_DEV_SPEC_PROFILE_BCA^MDC R

    | | | + +| | | | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-003 | | | | +| TP label | Whitepaper. Weight Scale MDS Object - Reg-Cert-Data-List Attribute [Profile Scale] | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Common MDS 14; M | Regulatory Conv 1; M | | +| Test purpose |

    Check that:

    PHG transcodes IEEE 11073-20601 Regulatory Certification Data List characteristic into MDS object, Reg-Cert-Data-List attribute

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_017 AND (NOT C_MAN_BLE_018) | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable). It exposes only the Weight Scale Service.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. IEEE 11073-20601 Regulatory Certification Data List (0x2A2A)
        • • Format: reg-cert-data-list (opaque structure)
        • • Value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 0F 02 02 00 02 80 00 (hex)
          • i. Element:
            • • auth-body-and-struc-type:
              • - auth-body: 02 (hex) auth-body-continua(2)
              • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
            • • auth-body-data:
              • - major-IG-version: 08 (hex)
              • - minor-IG-version: 00 (hex)
              • - certified-devices: 80 0F (hex) BTLE Weight Scale.
          • ii. Element:
            • • auth-body-and-struc-type:
              • - auth-body: 02 (hex). auth-body-continua(2)
              • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
            • • auth-body-data:
              • - regulation-bit-field: 80 00 (hex). Unregulated device
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD.
    4. 4. When the pairing has been completed (Connection state), force the PHG under test to read IEEE 11073-20601 Regulatory Certification Data List characteristic.
    5. 5. Check in PHG transcoder output the MDS object, Reg-Cert-Data-List attribute
    | | | | +| Pass/Fail criteria | In Step 5, the MDS object, Reg-Cert-Data-List attribute is present and its value matches with IEEE 11073-20601 Regulatory Certification Data List characteristic value | | | | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Reg-Cert-Data-List attribute is present:

    • Object: MDS Object
    • Attribute-id: MDC_ATTR_REG_CERT_DATA_LIST (2635)
    | | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-type: SEQUENCE OF {[auth-body-and-struc-type, auth-body-data], {...}}
    • Attribute-value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 0F 02 02 00 02 80 00 (hex) [Note that 0x00 0x02 is the number of elements in the sequence and 0x00 0x12 is the length of the sequence]
      • i. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex) auth-body-continua(2)
          • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
        • • auth-body-data:
          • - major-IG-version: 08 (hex)
          • - minor-IG-version: 00 (hex)
          • - certified-devices: 80 0F (hex). BTLE Weight Scale.
      • ii. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex). auth-body-continua(2)
          • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
        • • auth-body-data:
          • - regulation-bit-field: 80 00 (hex). Unregulated device

    b) WAN PCD-01 message

    PCD-01 message includes five segments like these with Reg-Cert-Data-List attribute value (check OBX-5 in five segments):

    OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.a 2^auth-body-continua     R
    OBX ? ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 1.0.0.a.x 6.1     R
    OBX ? NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 1.0.0.a.y 32783     R
    OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.b 2^auth-body-continua     R
    OBX ? CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 1.0.0.b.z 1^unregulated-device(0)     R
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-003_A | | | +| TP label | Whitepaper. Weight Scale MDS Object - Reg-Cert-Data-List Attribute [Profile BCA] | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Common MDS 14; M | Regulatory Conv 1; M | +| Test purpose | Check that:
    PHG transcodes IEEE 11073-20601 Regulatory Certification Data List characteristic into MDS object, Reg-Cert-Data-List attribute | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_017 AND C_MAN_BLE_018 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
    a. IEEE 11073-20601 Regulatory Certification Data List (0x2A2A) | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: reg-cert-data-list (opaque structure)
    • • Value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 14 02 02 00 02 80 00 (hex)
      • i. Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex) auth-body-continua(2)
          • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
        • • auth-body-data:
          • - major-IG-version: 08 (hex)
          • - minor-IG-version: 00 (hex)
          • - certified-devices: 80 14 (hex). BTLE Body Composition.
      • ii. Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex). auth-body-continua(2)
          • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
        • • auth-body-data:
          • - regulation-bit-field: 80 00 (hex). Unregulated device
    | +| Pass/Fail criteria |

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD.

    4. When the pairing has been completed (Connection state), force the PHG under test to read IEEE 11073-20601 Regulatory Certification Data List characteristic.

    5. Check in PHG transcoder output the MDS object, Reg-Cert-Data-List attribute

    In Step 6, the MDS object, Reg-Cert-Data-List attribute is present and its value matches with IEEE 11073-20601 Regulatory Certification Data List characteristic value

    | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Reg-Cert-Data-List attribute is present:

    • Object: MDS Object
    • Attribute-id: MDC_ATTR_REG_CERT_DATA_LIST (2635)
    • Attribute-type: SEQUENCE OF {auth-body-and-struc-type, auth-body-data}, {...}
    • Attribute-value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 14 02 02 00 02 80 00 (hex) [Note that 0x00 0x02 is the number of elements in the sequence and 0x00 0x12 is the length of the sequence]
      • i. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex) auth-body-continua(2)
          • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
        • • auth-body-data:
          • - major-IG-version: 08 (hex)
          • - minor-IG-version: 00 (hex)
          • - certified-devices 80 14 (hex). BTLE Body Composition.
      • ii. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex). auth-body-continua(2)
          • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
        • • auth-body-data:
          • - regulation-bit-field: 80 00 (hex). Unregulated device
    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • - regulation-bit-field: 80 00 (hex). Unregulated device

    b) WAN PCD-01 message

    PCD-01 message includes five segments like these with Reg-Cert-Data-List attribute value (check OBX-5 in five segments):

    OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.a 2^auth-body-continua     R
    OBX ? ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 1.0.0.a.x 6.1     R
    OBX ? NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 1.0.0.a.y 32788     R
    OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.b 2^auth-body-continua     R
    OBX ? CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 1.0.0.b.z 1^unregulated-device(0)     R
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-004 | | | +| TP label | Whitepaper. Weight Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Weight Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Weight Numeric object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Weight Numeric object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Weight Measurement Value in units of Kg and Time Stamp fields are included, Height, BMI and User ID fields are not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
      • This field is not included
      vi. Field: Height (in)
      • This field is not included
      vii. Field: BMI (kg/m2)
      • This field is not included
      viii. Field: User ID
      • This field is not included
    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    5. Check in PHG transcoder output the Weight Numeric object, Handle attribute | +| Pass/Fail criteria | In Step 5, the Weight Numeric object, Handle attribute is not present or, if it is present then its value is different than 0. | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Handle attribute is not present, or if it is present then:
    Object: Weight Numeric Object
    Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    Attribute-type: INT-U16
    Attribute-value: Any value different than 0
    b) WAN PCD-01 message
    PCD-01 message does not include segments with Handle attribute value | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-005 | | | +| TP label | Whitepaper. Weight Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Weight Numeric 2; M | | +| Test purpose | Check that:
    PHG includes Weight Numeric object, Type attribute in transcoder output.
    [AND]
    Type is set to {MDC_PART_SCADA, MDC_MASS_BODY_ACTUAL} | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
    a. Weight Measurement (0x2A9D)
    i. Field: Flags
    • Format: 8 bit
    • Value: 0000 0010 (MSB → LSB). Weight Measurement Value in units of Kg and Time Stamp fields are included, BMI, Height and User ID fields are not included
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ii. Field: Weight (Kg)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Weight (lb)
      • • This field is not included
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • v. Field: Height (m)
      • • This field is not included
    • vi. Field: Height (in)
      • • This field is not included
    • vii. Field: BMI (kg/m2)
      • • This field is not included
    • viii. Field: User ID
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    3. 5. Check in PHG transcoder output the Weight Numeric object, Type attribute
    | +| Pass/Fail criteria | In Step 5, the Weight Numeric object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_MASS_BODY_ACTUAL} | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Weight Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_MASS_BODY_ACTUAL or 57664 (dec) or E1 40 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX[?][188736^MDC_MASS_BODY_ACTUAL^MDC 1.0.a X [current_date_time]

    | + +| | | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-006 | | | +| TP label | Whitepaper. Weight Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Weight Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Weight Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Metric-Spec-Small is set to {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Weight Measurement Value in units of Kg and Time Stamp fields are included, Height, BMI and User ID fields are not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • This field is not included
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m2)
          • • This field is not included
        8. viii. Field: User ID
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    5. 5. Check in PHG transcoder output the Weight Numeric object, Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 5, the Weight Numeric object, Metric-Spec-Small attribute is present and its value is {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Weight Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9)
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| | set to TRUE and remaining BITS set to FALSE
    b) WAN PCD-01 message
    PCD-01 message does not include segments with Metric-Spec-Small attribute value | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-007 | | | +| TP label | Whitepaper. Weight Numeric Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Weight Numeric 4; M | Weight Numeric 5; M | +| Test purpose | Check that:
    PHG includes Weight Numeric object, Unit-Code attribute in transcoder output.
    [AND]
    IF Weight (Kg) field of Weight Measurement characteristic is present THEN Weight Numeric object, Unit-Code attribute is set to MDC_DIM_KILO_G
    [AND]
    IF Weight (lb) field of Weight Measurement characteristic is present THEN Weight Numeric object, Unit-Code attribute is set to MDC_DIM_LB | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Weight Measurement Value in units of Kg and Time Stamp fields are included, Height, BMI and User ID fields are not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • This field is not included
        6. vi. Field: Height (in)
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    vii. Field: BMI (kg/m2)

    • • This field is not included

    viii. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Weight Numeric object, Unit-Code attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Weight Measurement (0x2A9D)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0011 (MSB → LSB). Weight Measurement Value in units of Pounds and Time Stamp fields are included, Height, BMI and User ID fields are not included
    • ii. Field: Weight (Kg)
      • • This field is not included
    • iii. Field: Weight (lb)
      • • Format: UINT16
      • • Value: Not relevant
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • v. Field: Height (m)
      • • This field is not included
    • vi. Field: Height (in)
      • • This field is not included
    • vii. Field: BMI (kg/m2)
      • • This field is not included
    • viii. Field: User ID
      • • This field is not included

    7. Check in PHG transcoder output the Weight Numeric object, Unit-Code attribute

    | +| Pass/Fail criteria |

    In Step 5, the Weight Numeric object, Unit-Code attribute is present and its value is MDC_DIM_KILO_G

    In Step 7, the Weight Numeric Object – Unit-Code attribute is present and its value is MDC_DIM_LB

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Weight Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_KILO_G or 1731 (dec) or 06 C3 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    OBX ? NM 188736^MDC_MASS_BODY_ACTUAL^MDC 1.0.a XX
    263875^MDC_DIM_KILO_G^MDC R [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Weight Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_LB or 1760 (dec) or 06 E0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX ? NM 188736^MDC_MASS_BODY_ACTUAL^MDC 1.0.a XX
    263904^MDC_DIM_LB^MDC R [current_date_time]

    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-008 | | | | +| TP label | Whitepaper. Weight Numeric Object - Absolute-Time-Stamp Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Weight Numeric 6; M | Date-Time Conv 2; M | Date-Time Conv 3; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | | +| Test purpose |

    Check that:

    PHG transcodes Time Stamp field of Weight Measurement characteristic into Weight Numeric Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_024 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Weight Measurement Value in units of Kg and Time Stamp fields are included, Height, BMI and User ID fields are not included
        2. ii. Field: Weight (Kg)
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: UINT16
    • • Value: Not relevant

    iii. Field: Weight (lb)

    • • This field is not included

    iv. Field: Time Stamp

    • • Format: Date and Time
    • • Value: August 2nd, 2012, 10:39:27

    v. Field: Height (m)

    • • This field is not included

    vi. Field: Height (in)

    • • This field is not included

    vii. Field: BMI (kg/m2)

    • • This field is not included

    viii. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Weight Numeric object, Absolute-Time-Stamp attribute

    | +| Pass/Fail criteria | In Step 5, the Weight Numeric object, Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Weight Measurement characteristic and fraction of seconds is set to 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Weight Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 10 (hex) or 16 (dec)
      • • minute: 39 (hex) or 57 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX ?  188736^MDC_MASS_BODY_ACTUAL^MDC 1.0.a XX   X    20120802103927+0000
    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-009 | | | +| TP label | Whitepaper. Weight Numeric Object - Simple-Nu-Observed-Value Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Weight Numeric 7; M | Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Weight Value field of Weight Measurement characteristic into Weight Numeric Object - Simple-Nu-Observed-Value attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Weight Measurement Value in units of Kg and Time Stamp fields are included, Height, BMI and User ID fields are not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: 16000 (80.0 kg)
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • This field is not included
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m2)
          • • This field is not included
        8. viii. Field: User ID
          • • This field is not included
    5. 5. Check in PHG transcoder output the Weight Numeric object, Simple-Nu-Observed-Value attribute
    6. 6. The simulated PHD sends the Measurement to the PHG under test with the following value:
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. Weight Measurement (0x2A9D)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0011 (MSB → LSB). Weight Measurement Value in units of Pounds, Time Stamp field is included and Height, BMI and User ID fields are not included
    • ii. Field: Weight (Kg)
      • • This field is not included
    • iii. Field: Weight (lb)
      • • Format: UINT16
      • • Value: 17600 (176.0 lb)
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • v. Field: Height (m)
      • • This field is not included
    • vi. Field: Height (in)
      • • This field is not included
    • vii. Field: BMI (kg/m^2)
      • • This field is not included
    • viii. Field: User ID
      • • This field is not included

    7. Check in PHG transcoder output the Weight Numeric object, Simple-Nu-Observed-Value attribute

    | +| Pass/Fail criteria |

    In Step 5, the Weight Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Weight Measurement Value (Kg) fields of Weight Measurement characteristic (80.0)

    In Step 7, the Weight Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Weight Measurement Value (lb) fields of Weight Measurement characteristic (176.0)

    | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Weight Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 7A 12 00 (hex) or FC 0C 35 00 (hex) or FD 01 38 80 (hex) or FE 00 1F 40 (hex) or FF 00 03 20 (hex) or 00 00 00 50 (hex) or 01 00 00 08 (hex) or 80.0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 188736^MDC_MASS_BODY_ACTUAL^MDC 1.0.a 80.0  263875^MDC_DIM_KILO_G^MDC     R  [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Object: Weight Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FC 1A DB 00 (hex) or FD 02 AF 80 (hex) or FE 00 44 C0 (hex) or FF 00 06 E0 (hex) or 00 00 00 B0 (hex) or 176 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?][NM]188736^MDC_MASS_BODY_ACTUAL^MDC 1.0.a 176.0
    263904^MDC_DIM_LB^MDC R [current_date_time]

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-010 | | | +| TP label | Whitepaper. Weight Numeric Object - Simple-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Weight Numeric 7; M | Float Type 1; C | +| Test purpose | Check that:

    PHG transcodes Weight Value field of Weight Measurement characteristic into Weight Numeric Object - Simple-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x007FFFFF). | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Weight Measurement Value in units of Kg and Time Stamp fields are included, Height, BMI and User ID fields are not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: 16000 (80.0 kg)
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: Not relevant

    v. Field: Height (m)

    • • This field is not included

    vi. Field: Height (in)

    • • This field is not included

    vii. Field: BMI (kg/m2)

    • • This field is not included

    viii. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Weight Numeric object, Simple-Nu-Observed-Value attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Weight Measurement (0x2A9D)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0010 (MSB → LSB). Weight Measurement Value in units of Kg and Time Stamp fields are included, Height, BMI and User ID fields are not included
    • ii. Field: Weight (Kg)
      • • Format: UINT16
      • • Value: FF FF (hex). Unsuccessful measurement
    • iii. Field: Weight (lb)
      • • This field is not included
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • v. Field: Height (m)
      • • This field is not included
    • vi. Field: Height (in)
      • • This field is not included
    • vii. Field: BMI (kg/m2)
      • • This field is not included
    • viii. Field: User ID
      • • This field is not included

    7. Check in PHG transcoder output the Weight Numeric object, Simple-Nu-Observed-Value attribute

    | +| Pass/Fail criteria |

    In Step 5, the Weight Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 80.0.

    In Step 7, the Weight Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 0x007FFFFF.

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Weight Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-type: FLOAT
    • Attribute-value: FB 7A 12 00 (hex) or FC 0C 35 00 (hex) or FD 01 38 80 (hex) or FE 00 1F 40 (hex) or FF 00 03 20 (hex) or 00 00 00 50 (hex) or 01 00 00 08 (hex) or 80.0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[? NM 188736^MDC_MASS_BODY_ACTUAL^MDC 1.0.a 80.0 263875^MDC_DIM_KILO_G^MDC   R  [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Weight Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: 00 7F FF FF (hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segment with Simple-Nu-Observed-Value attribute value (188736^MDC_MASS_BODY_ACTUAL^MDC) because it has a special value and this value is not included in PCD-01 message.

    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-011 | | | +| TP label | Whitepaper. Weight Numeric Object - Weight Measurement value | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Float Type 1; C | Date-Time Conv 1; M | +| | | Weight Numeric 7; M | Weight Numeric 6; M | +| Test purpose | Check that:
    PHG processes correctly the Weight Measurement Value (Kg), Weight Measurement Value (lb) and Time Stamp fields of Weight Measurement | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_024 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case are:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0010 (MSB → LSB). Weight Measurement Value in units of Kg and Time Stamp fields are included, Height, BMI and User ID fields are not included
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ii. Field: Weight (Kg)
      • • Format: UINT16
      • • Value: 16000 (80.0 kg)
    • iii. Field: Weight (lb)
      • • This field is not included
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: August 2nd, 2012, 11:08:25
    • v. Field: Height (m)
      • • This field is not included
    • vi. Field: Height (in)
      • • This field is not included
    • vii. Field: BMI (kg/m2)
      • • This field is not included
    • viii. Field: User ID
      • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    • a. Weight Measurement (0x2A9D)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0011 (MSB → LSB). Weight Measurement Value in units of Pounds and Time Stamp fields are included, Height, BMI and User ID fields are not included
      • ii. Field: Weight (Kg)
        • • This field is not included
      • iii. Field: Weight (lb)
        • • Format: UINT16
        • • Value: 17600 (176.0 lb)
      • iv. Field: Time Stamp
        • • Format: Date and Time
        • • Value: August 2nd, 2012, 11:09:05
      • v. Field: Height (m)
        • • This field is not included
      • vi. Field: Height (in)
        • • This field is not included
      • vii. Field: BMI (kg/m2)
        • • This field is not included
      • viii. Field: User ID
        • • This field is not included

    7. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp)

    | +| Pass/Fail criteria | In Step 5, the PHG under test shows the following measurement: 80.0 Kg, with timestamp | + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------| +| | '2012-08-02 11:08:25'
    In Step 7, the PHG under test shows the following measurement 176.0 lbs, with timestamp '2012-08-02 11:09:05' | +| Notes | | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-012 | | | +| TP label | Whitepaper. Height Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Height Numeric 1; O | | +| Test purpose | Check that:
    PHG does not include Height Numeric object, Handle Attribute in transcoder output
    [OR]
    If PHG includes Height Numeric object, Handle attribute in transcoder output, then its value shall be different than 0 | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) AND C_MAN_BLE_019 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID fields is not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • Format: UINT16
          • • Value: Not relevant
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m^2)
          • • Format: UINT16
          • • Value: Not relevant
        8. viii. Field: User ID
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • This field is not included
    1. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    3. Check in PHG transcoder output the Height Numeric object, Handle attribute
    | +| Pass/Fail criteria | In Step 5, the Height Numeric object, Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    1. IEEE 11073 Objects and Attributes
      Handle attribute is not present, or if it is present then:
      • Object: Height Numeric Object
      • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
      • Attribute-type: INT-U16
      • Attribute-value: Any value different than 0
    2. WAN PCD-01 message
      PCD-01 message does not include segments with Handle attribute value
    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-013 | | | +| TP label | Whitepaper. Height Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Height Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Height Numeric object, Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_SCADA, MDC_LEN_BODY_ACTUAL}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_18) AND C_MAN_BLE_019 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. Weight Measurement (0x2A9D)
        1. Field: Flags
          • Format: 8 bit
          • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
        2. Field: Weight (Kg)
          • Format: UINT16
          • Value: Not relevant
        3. Field: Weight (lb)
          • This field is not included
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    iv. Field: Time Stamp

    • Format: Date and Time
    • Value: Not relevant

    v. Field: Height (m)

    • Format: UINT16
    • Value: Not relevant

    vi. Field: Height (in)

    • This field is not included

    vii. Field: BMI (kg/m2)

    • Format: UINT16
    • Value: Not relevant

    viii. Field: User ID

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Height Numeric object, Type attribute

    | +| Pass/Fail criteria | In Step 5, the Height Numeric object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_LEN_BODY_ACTUAL} | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Height Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • code: MDC_LEN_BODY_ACTUAL or 57668 (dec) or E1 44 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX[?][ ]188740^MDC_LEN_BODY_ACTUAL^MDC 1.0.a X [current_date_time]

    | + +| | | | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-014 | | | +| TP label | Whitepaper. Height Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Height Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Height Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_18) AND C_MAN_BLE_019 | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • Format: UINT16
          • • Value: Not relevant
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m2)
          • • Format: UINT16
          • • Value: Not relevant
        8. viii. Field: User ID
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    5. 5. Check in PHG transcoder output the Height Numeric object, Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 5, the Height Numeric object, Metric-Spec-Small attribute is present and its value is {0xF048} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-manual). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Height Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 48 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-manual(12) set to TRUE and remaining BITS set to FALSE
    | + +| | | +|--|----------------------------------------------------------------------------------------------------------| +| | b) WAN PCD-01 message
    PCD-01 message does not include segments with Metric-Spec-Small attribute value | +|--|----------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-015 | | | +| TP label | Whitepaper. Height Numeric Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Height Numeric 4; M | Height Numeric 5; M | +| Test purpose | Check that:
    PHG includes Weight Numeric object, Unit-Code attribute in transcoder output.
    [AND]
    IF Height (m) field of Weight Measurement characteristic is present THEN Height Numeric object, Unit-Code attribute is set to MDC_DIM_CENTI_M
    [AND]
    IF Height (in) field of Weight Measurement characteristic is present THEN Height Numeric object, Unit-Code attribute is set to MDC_DIM_INCH | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_18) AND C_MAN_BLE_019 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. PHG under test initiates discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state)
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • Format: UINT16
          • • Value: Not relevant
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • vi. Field: Height (in)
      • • This field is not included
    • vii. Field: BMI (kg/m2)
      • • Format: UINT16
      • • Value: Not relevant
    • viii. Field: User ID
      • • This field is not included

    5. Check in PHG transcoder output the Height Numeric object, Unit-Code attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    • a. Weight Measurement (0x2A9D)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 1011 (MSB → LSB). Weight Measurement Value in units of pound, Time Stamp, Height in units of inch and BMI fields are included, User ID field is not included
      • ii. Field: Weight (Kg)
        • • This field is not included
      • iii. Field: Weight (lb)
        • • Format: UINT16
        • • Value: Not relevant
      • iv. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
      • v. Field: Height (m)
        • • This field is not included
      • vi. Field: Height (in)
        • • Format: UINT16
        • • Value: Not relevant
      • vii. Field: BMI (kg/m2)
        • • Format: UINT16
        • • Value: Not relevant
      • viii. Field: User ID
        • • This field is not included

    7. Check in PHG transcoder output the Height Numeric object, Unit-Code attribute

    | +| Pass/Fail criteria |

    In Step 5, the Height Numeric object, Unit-Code attribute is present and its value is MDC_DIM_CENTI_M

    In Step 7, the Height Numeric Object – Unit-Code attribute is present and its value is MDC_DIM_INCH

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Height Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-value: MDC_DIM_CENTI_M or 1297 (dec) or 05 11 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX ? NM 188740^MDC_LEN_BODY_ACTUAL^MDC 1.0.a XX  263441^MDC_DIM_CENTI_M^MDC    R   [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    Object: Weight Numeric Object

    Attribute-id: MDC_ATTR_UNIT_CODE (2454)

    Attribute-type: INT-U16

    Attribute-value: MDC_DIM_INCH or 1376 (dec) or 05 60 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX ? NM 188740^MDC_LEN_BODY_ACTUAL^MDC 1.0.a XX  263520^MDC_DIM_INCH^MDC    R   [current_date_time]
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-016 | | | | +| TP label | Whitepaper. Height Numeric Object - Absolute-Time-Stamp Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Height Numeric 6; M | Date-Time Conv 2; M | Date-Time Conv 3; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | | +| Test purpose |

    Check that:

    PHG transcodes Time Stamp field of Weight Measurement characteristic into Height Numeric Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_18) AND C_MAN_BLE_019 AND C_MAN_BLE_024 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
    | | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: 8 bit
    • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included

    ii. Field: Weight (Kg)

    • • Format: UINT16
    • • Value: Not relevant

    iii. Field: Weight (lb)

    • • This field is not included

    iv. Field: Time Stamp

    • • Format: Date and Time
    • • Value: August 2nd, 2012, 10:39:27

    v. Field: Height (m)

    • • Format: UINT16
    • • Value: Not relevant

    vi. Field: Height (in)

    • • This field is not included

    vii. Field: BMI (kg/m2)

    • • Format: UINT16
    • • Value: Not relevant

    viii. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Height Numeric object, Absolute-Time-Stamp attribute

    | +| Pass/Fail criteria | In Step 5, the Height Numeric object, Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Weight Measurement characteristic and fraction of seconds is set to 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Height Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 10 (hex) or 16 (dec)
      • • minute: 39 (hex) or 57 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):
    OBX ? 188740^MDC_LEN_BODY_ACTUAL^MDC 1.0.a XX X
    20120802103927+0000 | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-017 | | | | +| TP label | Whitepaper. Height Numeric Object - Simple-Nu-Observed-Value Attribute 1 | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Height Numeric 7; M | Float Type 1; C | | +| Test purpose | Check that:
    PHG transcodes Height Value field of Weight Measurement characteristic into Height Numeric Object - Simple-Nu-Observed-Value attribute | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_18) AND C_MAN_BLE_019 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • Format: UINT16
          • • Value: 1800 (1.80 m)
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m^2)
    | | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: UINT16
    • • Value: Not relevant
    viii. Field: User ID
    • • This field is not included

    5. Check in PHG transcoder output the Height Numeric object, Simple-Nu-Observed-Value attribute.

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Weight Measurement (0x2A9D)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 1011 (MSB → LSB). Weight Measurement Value in units of Pounds, Time Stamp, Height in units of inch and BMI fields are included, User ID field is not included
    • ii. Field: Weight (Kg)
      • • This field is not included
    • iii. Field: Weight (lb)
      • • Format: UINT16
      • • Value: Not relevant
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • v. Field: Height (m)
      • • This field is not included
    • vi. Field: Height (in)
      • • Format: UINT16
      • • Value: 709 (70.9 in)
    • vii. Field: BMI (kg/m^2)
      • • Format: UINT16
      • • Value: Not relevant
    • viii. Field: User ID
      • • This field is not included

    7. Check in PHG transcoder output the Height Numeric object, Simple-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In Step 5, the Height Numeric object, Simple-Nu-Observed-Value (cm) attribute is present and its value matches with Height Value (m) field of Weight Measurement characteristic (1.80)

    In Step 7, the Height Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Height Value (in) field of Weight Measurement characteristic (70.9)

    | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Height Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FC 1B 77 40 (hex) or FD 02 BF 20 (hex) or FE 00 46 50 (hex) or FF 00 07 08 (hex) or 00 00 00 B4 (hex) or 01 00 00 12 (hex) or 180.0 (dec)
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 188740^MDC_LEN_BODY_ACTUAL^MDC 1.0.a 180.0  263441^MDC_DIM_CENTI_M^MDC   R   current_date_time

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Height Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 6C 2F 50 (hex) or FC 0A D1 88 (hex) or FD 01 14 F4 (hex) or FE 00 1B B2 (hex) or FF 00 02 C5 (hex) or 70.9 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 188740^MDC_LEN_BODY_ACTUAL^MDC 1.0.a 70.9  263520^MDC_DIM_INCH^MDC   R   current_date_time
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-018 | | | +| TP label | Whitepaper. Height Numeric Object - Simple-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Height Numeric 7; M | Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Height Value field of Weight Measurement characteristic into Height Numeric Object - Simple-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x007FFFFF).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_18) AND C_MAN_BLE_019 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ii. Field: Weight (Kg)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Weight (lb)
      • • This field is not included
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • v. Field: Height (m)
      • • Format: UINT16
      • • Value: 1800 (1.80 m)
    • vi. Field: Height (in)
      • • This field is not included
    • vii. Field: BMI (kg/m2)
      • • Format: UINT16
      • • Value: Not relevant
    • viii. Field: User ID
      • • This field is not included

    5. Check in PHG transcoder output the Height Numeric object, Simple-Nu-Observed-Value attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    • a. Weight Measurement (0x2A9D)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, Height, User ID field is not included
      • ii. Field: Weight (Kg)
        • • Format: UINT16
        • • Value: Not relevant
      • iii. Field: Weight (lb)
        • • This field is not included
      • iv. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
      • v. Field: Height (m)
        • • Format: UINT16
        • • Value: FF FF (hex). Unsuccessful measurement
      • vi. Field: Height (in)
        • • This field is not included
      • vii. Field: BMI (kg/m2)
        • • Format: UINT16
        • • Value: Not relevant
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    viii. Field: User ID

    • This field is not included

    7. Check in PHG transcoder output the Height Numeric object, Simple-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In Step 5, the Height Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 180.0.

    In Step 7, the Height Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 0x007FFFFFF.

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Height Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FC 1B 77 40 (hex) or FD 02 BF 20 (hex) or FE 00 46 50 (hex) or FF 00 07 08 (hex) or 00 00 00 B4 (hex) or 01 00 00 12 (hex) or 180.0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?][NM 188740^MDC_LEN_BODY_ACTUAL^MDC 1.0.a 180 263441^MDC_DIM_CENTI_M^MDC   R  [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Height Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: 00 7F FF FF (hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segment with Simple-Nu-Observed-Value attribute value (188740^MDC_LEN_BODY_ACTUAL^MDC) because it has a special value and this value is not included in PCD-01 message.

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-019 | | | +| TP label | Whitepaper. Height Numeric Object - Height value | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Float Type 1; C | Date-Time Conv 1; M | +| | | Height Numeric 7; M | Height Numeric 6; M | +| Test purpose |

    Check that:

    PHG processes correctly the Height Value (cm), Height Value (in) and Time Stamp fields of Weight Measurement

    | | | +| Applicability | C_MAN_BLE_000 AND (C_MAN_BLE_017 OR C_MAN_BLE_18) AND C_MAN_BLE_019 AND C_MAN_BLE_024 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    | | | + +2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case are: + - a. Weight Measurement (0x2A9D) +3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state). +4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value: + - a. Weight Measurement (0x2A9D) + - i. Field: Flags + - Format: 8 bit + - Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included + - ii. Field: Weight (Kg) + - Format: UINT16 + - Value: Not relevant + - iii. Field: Weight (lb) + - This field is not included + - iv. Field: Time Stamp + - Format: Date and Time + - Value: August 2nd, 2012, 11:08:25 + - v. Field: Height (m) + - Format: UINT16 + - Value: 1800 (1.80 m) + - vi. Field: Height (in) + - This field is not included + - vii. Field: BMI (kg/m2) + - Format: UINT16 + - Value: Not relevant + - viii. Field: User ID + - This field is not included +5. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp). +6. The simulated PHD sends the Measurement to the PHG under test with the following value: + - a. Weight Measurement (0x2A9D) + - i. Field: Flags + - Format: 8 bit + - Value: 0000 1011 (MSB → LSB). Weight Measurement Value in units of pound, Time Stamp, Height in units of inch and BMI fields are included, User ID field is not included + - ii. Field: Weight (Kg) + - This field is not included + - iii. Field: Weight (lb) + - Format: UINT16 + - Value: Not relevant + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    iv. Field: Time Stamp

    • Format: Date and Time
    • Value: August 2nd, 2012, 11:09:05

    v. Field: Height (m)

    • This field is not included

    vi. Field: Height (in)

    • Format: UINT16
    • Value: 709 (70.9 in)

    vii. Field: BMI (kg/m2)

    • Format: UINT16
    • Value: Not relevant

    viii. Field: User ID

    • This field is not included

    7. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    | +| Pass/Fail criteria |

    In Step 5, the PHG under test shows the following measurement: 180 cm, with timestamp '2012-08-02 11:08:25'

    In Step 7, the PHG under test shows the following measurement 70.9 in, with timestamp '2012-08-02 11:09:05'

    | +| Notes | | + +| | | | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-020 | | | | | +| TP label | Whitepaper. Body Mass Index Numeric Object - Handle Attribute | | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | | +| | Testable items | BMI Numeric 1; O | | | | +| Test purpose |

    Check that:

    PHG does not include BMI Numeric object, Handle Attribute in transcoder output

    [OR]

    If PHG includes BMI Numeric object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) AND C_MAN_BLE_020 | | | | | +| Other PICS | | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | | +| Test procedure |

    1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:

    a. Weight Measurement (0x2A9D)

    i. Field: Flags

    • Format: 8 bit
    • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID fields is not included

    ii. Field: Weight (Kg)

    • Format: UINT16
    | | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: Not relevant

    iii. Field: Weight (lb)

    • • This field is not included

    iv. Field: Time Stamp

    • • Format: Date and Time
    • • Value: Not relevant

    v. Field: Height (m)

    • • Format: UINT16
    • • Value: Not relevant

    vi. Field: Height (in)

    • • This field is not included

    vii. Field: BMI (kg/m2)

    • • Format: UINT16
    • • Value: Not relevant

    viii. Field: User ID

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the BMI Numeric object, Handle attribute

    | +| Pass/Fail criteria | In Step 5, the BMI Numeric object, Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: BMI Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-021 | | | +| TP Label | Whitepaper. Body Mass Index Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | BMI Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes BMI Numeric object, Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_SCADA, MDC_RATIO_MASS_BODY_LEN_SQ}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) AND C_MAN_BLE_020 | | | +| Other PICS | | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • Format: UINT16
          • • Value: Not relevant
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m2)
          • • Format: UINT16
          • • Value: Not relevant
        8. viii. Field: User ID
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    5. 5. Check in PHG transcoder output the BMI Numeric object, Type attribute
    | +| Pass/Fail criteria | In Step 5, the Weight Numeric object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_RATIO_MASS_BODY_LEN_SQ} | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: BMI Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_RATIO_MASS_BODY_LEN_SQ or 57680 (dec) or E1 50 (hex)

    b) WAN PCD-01 message

    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PCD-01 message includes a segment like this with Type attribute (check OBX-3):
    OBX[?][[188752^MDC_RATIO_MASS_BODY_LEN_SQ^MDC]
    1.0.a XX X [current_date_time] | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-022 | | | +| TP label | Whitepaper. Body Mass Index Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | BMI Numeric 3; M | | +| Test purpose | Check that:
    PHG includes BMI Numeric object, Metric-Spec-Small attribute in transcoder output.
    [AND]
    Metric-Spec-Small is set to {0xF042} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-calculation). | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) AND C_MAN_BLE_020 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • Format: UINT16
          • • Value: Not relevant
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m2)
          • • Format: UINT16
          • • Value: Not relevant
        8. viii. Field: User ID
          • • This field is not included
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    3. 5. Check in PHG transcoder output the BMI Numeric object, Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 5, the BMI Numeric object, Metric-Spec-Small attribute is present and its value is {0xF042} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-calculation). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes
      Metric-Spec-Small attribute is present:
      • Object: BMI Numeric Object
      • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
      • Attribute-type: BITS-16
      • Attribute-value: F0 42 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-calculation(14) set to TRUE and remaining BITS set to FALSE
    2. b) WAN PCD-01 message
      PCD-01 message does not include segments with Metric-Spec-Small attribute value
    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-023 | | | +| TP label | Whitepaper. Body Mass Index Numeric Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | BMI Numeric 4; M | BMI Numeric 5; M | +| Test purpose |

    Check that:

    PHG includes BMI Numeric object, Unit-Code attribute in transcoder output.

    [AND]

    IF BMI (Kg/m2) field of Weight Measurement characteristic is present THEN BMI Numeric object, Unit-Code attribute is set to MDC_DIM_KG_PER_M_SQ

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) AND C_MAN_BLE_020 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    ID field is not included

    ii. Field: Weight (Kg)

    • • Format: UINT16
    • • Value: Not relevant

    iii. Field: Weight (lb)

    • • This field is not included

    iv. Field: Time Stamp

    • • Format: Date and Time
    • • Value: Not relevant

    v. Field: Height (m)

    • • Format: UINT16
    • • Value: Not relevant

    vi. Field: Height (in)

    • • This field is not included

    vii. Field: BMI (kg/m2)

    • • Format: UINT16
    • • Value: Not relevant

    viii. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Height Numeric object, Unit-Code attribute

    | +| Pass/Fail criteria | In Step 5, the BMI Numeric object, Unit-Code attribute is present and its value is MDC_DIM_KG_PER_M_SQ | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • ❑ Object: BMI Numeric Object
    • ❑ Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • ❑ Attribute-type: INT-U16
    • ❑ Attribute-value: MDC_DIM_KG_PER_M_SQ or 1952 (dec) or 07 A0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX ? NM 188752^MDC_RATIO_MASS_BODY_LEN_SQ^MDC 1.0.a XX 264096^MDC_DIM_KG_PER_M_SQ^MDC R [current_date_time]

    | + +| | | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-024 | | | | +| TP label | Whitepaper. Body Mass Index Numeric Object - Absolute-Time-Stamp Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | BMI Numeric 6; M | Date-Time Conv 2; M | Date-Time Conv 3; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | | +| Test purpose |

    Check that:

    PHG transcodes Time Stamp field of Weight Measurement characteristic into BMI Numeric Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format

    | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [AND]
    The fraction of seconds in Absolute Time at transcoder output is 0 | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) AND C_MAN_BLE_020 AND C_MAN_BLE_024 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:39:27
        5. v. Field: Height (m)
          • • Format: UINT16
          • • Value: Not relevant
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m2)
          • • Format: UINT16
          • • Value: Not relevant
        8. viii. Field: User ID
          • • This field is not included
    5. 5. Check in PHG transcoder output the BMI Numeric object, Absolute-Time-Stamp attribute
    | +| Pass/Fail criteria | In Step 5, the BMI Numeric object, Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Weight Measurement characteristic and fraction of seconds is set to 0 | +| Notes | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Absolute-Time-Stamp attribute is present: | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Object: BMI Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 10 (hex) or 16 (dec)
      • • minute: 39 (hex) or 57 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX ?  188752^MDC_RATIO_MASS_BODY_LEN_SQ^MDC 1.0.a     X   20120802103927+0000
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-025 | | | +| TP label | Whitepaper. Body Mass Index Numeric Object - Simple-Nu-Observed-Value Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | BMI Numeric 7; M | Float Type 1; C | +| Test purpose | Check that:

    PHG transcodes BMI Value field of Weight Measurement characteristic into BMI Numeric Object - Simple-Nu-Observed-Value attribute | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) AND C_MAN_BLE_020 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ii. Field: Weight (Kg)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Weight (lb)
      • • This field is not included
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • v. Field: Height (m)
      • • Format: UINT16
      • • Value: Not relevant
    • vi. Field: Height (in)
      • • This field is not included
    • vii. Field: BMI
      • • Format: UINT16
      • • Value: 247 (24.7)
    • viii. Field: User ID
      • • This field is not included

    5. Check in PHG transcoder output the BMI Numeric object, Simple-Nu-Observed-Value attribute

    | +| Pass/Fail criteria | In Step 5, the BMI Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with BMI Value (kg/m 2 ) field of Weight Measurement characteristic (24.7) | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: BMI Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FF 00 00 F7 (hex) or 24.7 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 188752^MDC_RATIO_MASS_BODY_LEN_SQ^MDC 1.0.a 24.7  264096^MDC_DIM_KG_PER_M_SQ^MDC     R  [current_date_time]
    | + +| | | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-027 | | | | +| TP label | Whitepaper. BMI Numeric object, BMI value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Float Type 1; C | Date-Time Conv 1; M | BMI Numeric 6; M | +| | | BMI Numeric 7; M | | | +| Test purpose |

    Check that:

    PHG processes correctly the BMI Value (kg/m2) and Time Stamp fields of Weight Measurement

    | | | | +| Applicability | C_MAN_BLE_000 AND (C_MAN_BLE_017 OR C_MAN_BLE_018) AND C_MAN_BLE_020 AND C_MAN_024 | | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case are:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 11:08:25
        5. v. Field: Height (m)
          • • Format: UINT16
          • • Value: Not relevant
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m2)
          • • Format: UINT16
          • • Value: 247 (24.7)
        8. viii. Field: User ID
          • • This field is not included
    5. 5. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).
    | +| Pass/Fail criteria | In Step 5, the PHG under test shows the following measurement: 24.7 kg/m 2 , with timestamp '2012-08-02 11:08:25' | +| Notes | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-028 | | | +| TP label | Whitepaper. Body Fat Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Fat Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Body Fat Numeric object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Body Fat Numeric object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0000 0010 (MSB → LSB). Body Fat Percentage in units of % and Time Stamp fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • This field is not included
        9. ix. Field: Body Water Mass (lb)
          • • This field is not included
        10. x. Field: Basal Metabolism
          • • This field is not included
        11. xi. Field: Muscle Percentage
          • • This field is not included
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Body Fat Numeric object, Handle attribute

    | +| Pass/Fail criteria | In Step 5, the Body Fat Numeric object, Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Body Fat Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-029 | | | | | +| TP label | Whitepaper. Body Fat Numeric Object - Type Attribute | | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | | +| | Testable items | Body Fat Numeric 2; M | | | | +| Test purpose |

    Check that:

    PHG includes Body Fat Numeric object, Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_SCADA, MDC_BODY_FAT}

    | | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 | | | | | +| Other PICS | | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
    | | | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: 16 bit
    • • Value: 0000 0000 0000 0010 (MSB → LSB). Body Fat Percentage in units of % and Time Stamp fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included

    ii. Field: Body Fat Percentage (%)

    • • Format: UINT16
    • • Value: Not relevant

    iii. Field: Time Stamp

    • • Format: Date and Time
    • • Value: Not relevant

    iv. Field: Fat Free Mass (kg)

    • • This field is not included

    v. Field: Fat Free Mass (lb)

    • • This field is not included

    vi. Field: Soft Lean Mass (kg)

    • • This field is not included

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Body Fat Numeric object, Type attribute

    | +| Pass/Fail criteria | In Step 5, the Body Fat Numeric object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_BODY_FAT} | +| Notes | Possible values in typical points of observation after transcoder output are: | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Body Fat Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_BODY_FAT or 57676 (dec) or E1 4C (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX[?][188748^MDC_BODY_FAT^MDC 1.0.a X [current_date_time]

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-030 | | | +| TP label | Whitepaper. Body Fat Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Fat Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Body Fat Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF042} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-calculation).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0000 0010 (MSB → LSB). Body Fat Percentage in units of % and Time Stamp fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    vi. Field: Soft Lean Mass (kg)

    • • This field is not included

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    3. 5. Check in PHG transcoder output the Body Fat Numeric object, Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 5, the Body Fat Numeric object, Metric-Spec-Small attribute is present and its value is {0xF042} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-calculation). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Body Fat Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 42 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9), mss-cat-calculation(14) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-031 | | | +| TP label | Whitepaper. Body Fat Numeric Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Fat Numeric 4; M | Body Fat Numeric 5; M | +| Test purpose |

    Check that:

    PHG includes Body Fat Numeric object, Unit-Code attribute in transcoder output.

    [AND]

    IF Body Fat Percentage (%) field of Body Composition Measurement characteristic is present
    THEN Body Fat Numeric object, Unit-Code attribute is set to MDC_DIM_PERCENT

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0000 0010 (MSB → LSB). Body Fat Percentage in units of % and Time Stamp fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • This field is not included
        9. ix. Field: Body Water Mass (lb)
    | | | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Body Fat Numeric object, Unit-Code attribute

    | +| Pass/Fail criteria | In Step 5, the Body Fat Numeric object, Unit-Code attribute is present and its value is MDC_DIM_PERCENT | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Body Fat Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_PERCENT or 544 (dec) or 02 20 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6 ):

    OBX[?] NM 188748^MDC_BODY_FAT^MDC 1.0.a XX
    262688^MDC_DIM_PERCENT^MDC R current_date_time]

    | + +| | | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-032 | | | | +| TP label | Whitepaper. Body Fat Numeric Object - Absolute-Time-Stamp Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Body Fat Numeric 6; M | Date-Time Conv 2; M | Date-Time Conv 3; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | | +| Test purpose |

    Check that:

    PHG transcodes Time Stamp field of Body Composition Measurement characteristic into Body Fat Numeric Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_025 | | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          1. • Format: 16 bit
          2. • Value: 0000 0000 0000 0010 (MSB → LSB). Body Fat Percentage in units of % and Time Stamp fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          1. • Format: UINT16
          2. • Value: Not relevant
        3. iii. Field: Time Stamp
          1. • Format: Date and Time
          2. • Value: August 2nd, 2012, 10:39:27
        4. iv. Field: Fat Free Mass (kg)
          1. • This field is not included
        5. v. Field: Fat Free Mass (lb)
          1. • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          1. • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          1. • This field is not included
        8. viii. Field: Body Water Mass (kg)
          1. • This field is not included
        9. ix. Field: Body Water Mass (lb)
          1. • This field is not included
        10. x. Field: Basal Metabolism
          1. • This field is not included
        11. xi. Field: Muscle Percentage
          1. • This field is not included
        12. xii. Field: Muscle Mass
          1. • This field is not included
        13. xiii. Field: Impedance
          1. • This field is not included
        14. xiv. Field: Weight
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • This field is not included

    xv. Field: Height

    • This field is not included

    xvi. Field: User ID

    • This field is not included

    5. Check in PHG transcoder output the Body Fat Numeric object, Absolute-Time-Stamp attribute

    | +| Pass/Fail criteria | In Step 5, the Body Fat Numeric object, Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Body Composition Measurement characteristic and fraction of seconds is set to 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Body Fat Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • century: 20 (hex) or 32 (dec)
      • year: 12 (hex) or 18 (dec)
      • month: 08 (hex) or 8 (dec)
      • day: 02 (hex) or 2 (dec)
      • hour: 10 (hex) or 16 (dec)
      • minute: 39 (hex) or 57 (dec)
      • second: 27 (hex) or 39 (dec)
      • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX[?][188748^MDC_BODY_FAT^MDC 1.0.a X 20120802103927+0000

    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-033 | | | +| TP label | Whitepaper. Body Fat Numeric Object - Simple-Nu-Observed-Value Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Fat Numeric 7; M | Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Body Fat Percentage Value field of Body Composition Measurement characteristic into Body Fat Numeric Object - Simple-Nu-Observed-Value attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristic of
    | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    interest for this test case is:

    a. Body Composition Measurement (0x2A9C)

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Body Composition Measurement (0x2A9C)

    • i. Field: Flags
      • • Format: 16 bit
      • • Value: 0000 0000 0000 0010 (MSB → LSB). Body Fat Percentage in units of % and Time Stamp fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
    • ii. Field: Body Fat Percentage (%)
      • • Format: UINT16
      • • Value: 125 (12.5 %)
    • iii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Fat Free Mass (kg)
      • • This field is not included
    • v. Field: Fat Free Mass (lb)
      • • This field is not included
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    • xv. Field: Height
      • • This field is not included
    • xvi. Field: User ID
      • • This field is not included
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 5. Check in PHG transcoder output the Body Fat Numeric object, Simple-Nu-Observed-Value attribute | +| Pass/Fail criteria | In Step 5, the Body Fat Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Body Fat Percentage Value (%) field of Body Composition Measurement characteristic (12.5) | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Body Fat Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FF 00 00 7D (hex) or 12.5 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[? NM 188748^MDC_BODY_FAT^MDC 1.0.a 12.5
    262688^MDC_DIM_PERCENT^MDC R current_date_time]

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-034 | | | +| TP label | Whitepaper. Body Fat Numeric Object - Simple-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Fat Numeric 7; M | Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Body Fat Percentage Value field of Body Composition Measurement characteristic into Body Fat Numeric Object - Simple-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x007FFFFFF).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0000 0010 (MSB → LSB). Body Fat Percentage in units of % and Time Stamp fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: UINT16
    • • Value: 125 (12.5 %)
    1. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    2. Field: Fat Free Mass (kg)
      • • This field is not included
    3. Field: Fat Free Mass (lb)
      • • This field is not included
    4. Field: Soft Lean Mass (kg)
      • • This field is not included
    5. Field: Soft Lean Mass (lb)
      • • This field is not included
    6. Field: Body Water Mass (kg)
      • • This field is not included
    7. Field: Body Water Mass (lb)
      • • This field is not included
    8. Field: Basal Metabolism
      • • This field is not included
    9. Field: Muscle Percentage
      • • This field is not included
    10. Field: Muscle Mass
      • • This field is not included
    11. Field: Impedance
      • • This field is not included
    12. Field: Weight
      • • This field is not included
    13. Field: Height
      • • This field is not included
    14. Field: User ID
      • • This field is not included

    5. Check in PHG transcoder output the Body Fat Numeric object, Simple-Nu-Observed-Value attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    1. Body Composition Measurement (0x2A9C)
      1. Field: Flags
        • • Format: 16 bit
        • • Value: 0000 0000 0000 0010 (MSB → LSB). Body Fat Percentage in units of % and Time Stamp fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
      2. Field: Body Fat Percentage (%)
        • • Format: UINT16
        • • Value: FF FF (hex). Unsuccessful measurement
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    iii. Field: Time Stamp

    • • Format: Date and Time
    • • Value: Not relevant

    iv. Field: Fat Free Mass (kg)

    • • This field is not included

    v. Field: Fat Free Mass (lb)

    • • This field is not included

    vi. Field: Soft Lean Mass (kg)

    • • This field is not included

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    7. Check in PHG transcoder output the Body Fat Numeric object, Simple-Nu-Observed-Value attribute

    | +| Pass/Fail criteria |

    In Step 5, the Body Fat Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 12.5.

    In Step 7, the Body Fat Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 0x007FFFFF.

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Body Fat Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FA BE BC 20 (hex) or FB 13 12 D0 (hex) or FC 01 E8 48 (hex) or FD 00 30 D4 (hex) or FE 00 04 E2 (hex) or FF 00 00 7D (hex) or 12.5 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute

    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    value (check OBX-5):

    OBX[?][NM 188748^MDC_BODY_FAT^MDC 1.0.a 12.5]
    262688^MDC_DIM_PERCENT^MDC R [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Body Fat Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: 00 7F FF FF (hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segment with Simple-Nu-Observed-Value attribute value (188748^MDC_BODY_FAT^MDC) because it has a special value and this value is not included in PCD-01 message

    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-035 | | | +| TP label | Whitepaper. Body Fat Numeric object, Body Fat Percentage value | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Float Type 1; C | Date-Time Conv 1; M | +| | | Body Fat Numeric 7; M | Body Fat Numeric 6; M | +| Test purpose |

    Check that:

    PHG processes correctly the Body Fat Percentage Value and Time Stamp fields of Body Composition Measurement

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_018 AND C_MAN_BLE_025 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case are:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0000 0010 (MSB → LSB). Body Fat Percentage in units of % and Time Stamp fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: 125 (12.5 %)
        3. iii. Field: Time Stamp
          • • Format: Date and Time
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: August 2nd, 2012, 11:08:25

    iv. Field: Fat Free Mass (kg)

    • • This field is not included

    v. Field: Fat Free Mass (lb)

    • • This field is not included

    vi. Field: Soft Lean Mass (kg)

    • • This field is not included

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    | +| Pass/Fail criteria | In Step 5, the PHG under test shows the following measurement: 12.5 %, with timestamp '2012-08-02 11:08:25' | +| Notes | | + +| | | | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-036 | | | +| TP label | Whitepaper. Fat Free Mass Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Fat Free Numeric 1; O | | +| Test purpose | Check that:

    PHG does not include Fat Free Mass Numeric object, Handle Attribute in transcoder output
    [OR]
    If PHG includes Fat Free Mass Numeric object, Handle attribute in transcoder output, then its value shall be different than 0 | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_021 | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          1. • Format: 16 bit
          2. • Value: 0000 0000 0100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          1. • Format: UINT16
          2. • Value: Not relevant
        3. iii. Field: Time Stamp
          1. • Format: Date and Time
          2. • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          1. • Format: UINT16
          2. • Value: Not relevant
        5. v. Field: Fat Free Mass (lb)
          1. • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          1. • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          1. • This field is not included
        8. viii. Field: Body Water Mass (kg)
          1. • This field is not included
        9. ix. Field: Body Water Mass (lb)
          1. • This field is not included
        10. x. Field: Basal Metabolism
          1. • This field is not included
        11. xi. Field: Muscle Percentage
          1. • This field is not included
        12. xii. Field: Muscle Mass
          1. • This field is not included
        13. xiii. Field: Impedance
          1. • This field is not included
        14. xiv. Field: Weight
          1. • This field is not included
        15. xv. Field: Height
          1. • This field is not included
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xvi. Field: User ID

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Fat Free Mass Numeric object, Handle attribute

    | +| Pass/Fail criteria | In Step 5, the Fat Free Mass Numeric object, Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-037 | | | +| TP label | Whitepaper. Fat Free Mass Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Fat Free Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Fat Free Mass Numeric object, Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_SCADA, MDC_MASS_BODY_FAT_FREE}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_021 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. Body Composition Measurement (0x2A9C)
        1. Field: Flags
          • Format: 16 bit
          • Value: 0000 0000 0100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. Field: Body Fat Percentage (%)
          • Format: UINT16
          • Value: Not relevant
        3. Field: Time Stamp
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: Date and Time
    • • Value: Not relevant

    iv. Field: Fat Free Mass (kg)

    • • Format: UINT16
    • • Value: Not relevant

    v. Field: Fat Free Mass (lb)

    • • This field is not included

    vi. Field: Soft Lean Mass (kg)

    • • This field is not included

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Fat Free Mass Numeric object, Type attribute

    | +| Pass/Fail criteria | In Step 5, the Fat Free Mass Numeric object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_MASS_BODY_FAT_FREE} | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • code: MDC_MASS_BODY_FAT_FREE or 57684 (dec) or E1 54 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX ? 188756^MDC_MASS_BODY_FAT_FREE^MDC 1.0.a X
    current_date_time]

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-038 | | | +| TP label | Whitepaper. Fat Free Mass Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Fat Free Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Fat Free Mass Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_021 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. Body Composition Measurement (0x2A9C)
        1. Field: Flags
          • Format: 16 bit
          • Value: 0000 0000 0100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. Field: Body Fat Percentage (%)
          • Format: UINT16
          • Value: Not relevant
        3. Field: Time Stamp
          • Format: Date and Time
          • Value: Not relevant
        4. Field: Fat Free Mass (kg)
          • Format: UINT16
          • Value: Not relevant
        5. Field: Fat Free Mass (lb)
          • This field is not included
        6. Field: Soft Lean Mass (kg)
          • This field is not included
        7. Field: Soft Lean Mass (lb)
          • This field is not included
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Fat Free Mass Numeric object, Metric-Spec-Small attribute

    | +| Pass/Fail criteria | In Step 5, the Height Numeric object, Metric-Spec-Small attribute is present and its value is {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|-----------------|----------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-039 | | | +| TP label | Whitepaper. Fat Free Mass Numeric Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Fat Free Numeric 4; M | Fat Free Numeric 5; M | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    PHG includes Fat Free Mass Numeric object, Unit-Code attribute in transcoder output.

    [AND]

    IF Fat Free Mass (kg) field of Body Composition Measurement characteristic is present THEN Height Numeric object, Unit-Code attribute is set to MDC_DIM_KILO_G

    [AND]

    IF Fat Free Mass (lb) field of Body Composition Measurement characteristic is present THEN Height Numeric object, Unit-Code attribute is set to MDC_DIM_LB

    | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_021 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • This field is not included
        9. ix. Field: Body Water Mass (lb)
    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in the PHG transcoder output the Fat Free Mass Numeric object, Unit-Code attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Body Composition Measurement (0x2A9C)

    • i. Field: Flags
      • • Format: 16 bit
      • • Value: 0000 0000 0100 0011 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of pound fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
    • ii. Field: Body Fat Percentage (%)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Fat Free Mass (kg)
      • • This field is not included
    • v. Field: Fat Free Mass (lb)
      • • Format: UINT16
      • • Value: Not relevant
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included
    1. Field: Basal Metabolism
      • • This field is not included
    2. Field: Muscle Percentage
      • • This field is not included
    3. Field: Muscle Mass
      • • This field is not included
    4. Field: Impedance
      • • This field is not included
    5. Field: Weight
      • • This field is not included
    6. Field: Height
      • • This field is not included
    7. Field: User ID
      • • This field is not included

    7. Check in PHG transcoder output the Fat Free Mass Numeric object, Unit-Code attribute

    | +| Pass/Fail criteria |

    In Step 5, the Fat Free Mass Numeric object, Unit-Code attribute is present and its value is MDC_DIM_KILO_G

    In Step 7, the Fat Free Mass Numeric Object – Unit-Code attribute is present and its value is MDC_DIM_LB

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_KILO_G or 1731 (dec) or 06 C3 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?] NM 188756^MDC_MASS_BODY_FAT_FREE^MDC 1.0.a XX  263875^MDC_DIM_KILO_G^MDC    R  [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_LB or 1760 (dec) or 06 E0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?] NM 188756^MDC_MASS_BODY_FAT_FREE^MDC 1.0.a XX  263904^MDC_DIM_LB^MDC    R  [current_date_time]
    | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-040 | | | | +| TP label | Whitepaper. Fat Free Mass Numeric Object - Absolute-Time-Stamp Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Fat Free Numeric 6; M | Date-Time Conv 2; M | Date-Time Conv 3; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | | +| Test purpose |

    Check that:

    PHG transcodes Time Stamp field of Body Composition Measurement characteristic into Fat Free Mass Numeric Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_021 AND C_MAN_BLE_025 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:39:27
        4. iv. Field: Fat Free Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
    | | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Fat Free Mass Numeric object, Absolute-Time-Stamp attribute

    | +| Pass/Fail criteria | In Step 5, the Fat Free Mass Numeric object, Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Body Composition Measurement characteristic and fraction of seconds is set to 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 10 (hex) or 16 (dec)
      • • minute: 39 (hex) or 57 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    | + +| | | +|--|--------------------------------------------------------------------------------| +| | OBX[?][188756^MDC_MASS_BODY_FAT_FREE^MDC 1.0.a XX X
    20120802103927+0000 | +|--|--------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-041 | | | +| TP label | Whitepaper. Fat Free Mass Numeric Object - Simple-Nu-Observed-Value Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Fat Free Numeric 7; M | Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Fat Free Mass Value field of Body Composition Measurement characteristic into Fat Free Mass Numeric Object - Simple-Nu-Observed-Value attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_021 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • Format: UINT16
          • • Value: 12800 (64.0 kg)
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    • xv. Field: Height
      • • This field is not included
    • xvi. Field: User ID
      • • This field is not included

    5. Check in PHG transcoder output the Fat Free Mass Numeric object, Simple-Nu-Observed-Value attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    • a. Body Composition Measurement (0x2A9C)
      • i. Field: Flags
        • • Format: 16 bit
        • • Value: 0000 0000 0100 0011 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of pound fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
      • ii. Field: Body Fat Percentage (%)
        • • Format: UINT16
        • • Value: Not relevant
      • iii. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
      • iv. Field: Fat Free Mass (kg)
        • • This field is not included
      • v. Field: Fat Free Mass (lb)
        • • Format: UINT16
        • • Value: 14080 (140.8 lb)
      • vi. Field: Soft Lean Mass (kg)
        • • This field is not included
      • vii. Field: Soft Lean Mass (lb)
        • • This field is not included
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    7. Check in PHG transcoder output the Fat Free Mass Numeric object, Simple-Nu-Observed-Value attribute

    | +| Pass/Fail criteria |

    In Step 5, the Fat Free Mass Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Fat Free Mass Value (kg) field of Body Composition Measurement characteristic (64.0)

    In Step 7, the Fat Free Mass Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Fat Free Mass Value (lb) field of Body Composition Measurement characteristic (140.8)

    | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 61 A8 00 (hex) or FC 09 C4 00 (hex) or FD 00 FA 00 (hex) or FE 00 19 00 (hex) or FF 00 02 80 (hex) or 00 00 00 40 (hex) or 64.0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[? NM 188756^MDC_MASS_BODY_FAT_FREE^MDC 1.0.a 64.0  263875^MDC_DIM_KILO_G^MDC    R  [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB D6 D8 00 (hex) or FC 15 7C 00 (hex) or FD 02 26 00 (hex) or FE 00 37 00 (hex) or FF 00 05 80 (hex) or 140.8 (dec)
    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?][NM][188756^MDC_MASS_BODY_FAT_FREE^MDC][1.0.a][140.8]
    263904^MDC_DIM_LB^MDC][[R]][[current_date_time]]

    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-042 | | | +| TP label | Whitepaper. Fat Free Mass Numeric Object - Simple-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Fat Free Numeric 7; M | Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Fat Free Mass Value field of Body Composition Measurement characteristic into Fat Free Mass Numeric Object - Simple-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x007FFFFFF).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_021 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • Format: UINT16
          • • Value: 12800 (64.0 kg)
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    • xv. Field: Height
      • • This field is not included
    • xvi. Field: User ID
      • • This field is not included

    5. Check in PHG transcoder output the Fat Free Mass Numeric object, Simple-Nu-Observed-Value attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    • a. Body Composition Measurement (0x2A9C)
      • i. Field: Flags
        • • Format: 16 bit
        • • Value: 0000 0000 0100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
      • ii. Field: Body Fat Percentage (%)
        • • Format: UINT16
        • • Value: Not relevant
      • iii. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
      • iv. Field: Fat Free Mass (kg)
        • • Format: UINT16
        • • Value: FF FF (hex). Unsuccessful measurement
      • v. Field: Fat Free Mass (lb)
        • • This field is not included
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vi. Field: Soft Lean Mass (kg)

    • • This field is not included

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    7. Check in PHG transcoder output the Fat Free Mass Numeric object, Simple-Nu-Observed-Value attribute

    | +| Pass/Fail criteria |

    In Step 5, the Fat Free Mass Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 64.0.

    In Step 7, the Fat Free Mass Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 0x007FFFFFF.

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 61 A8 00 (hex) or FC 09 C4 00 (hex) or FD 00 FA 00 (hex) or FE 00 19 00 (hex) or FF 00 02 80 (hex) or 00 00 00 40 (hex) or 64.0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?][NM][188756]^MDC_MASS_BODY_FAT_FREE^MDC[1.0.a][64.0]
    263875^MDC_DIM_KILO_G^MDC[     R    ][current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-type: FLOAT
    • Attribute-value: 00 7F FF FF (hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segment with Simple-Nu-Observed-Value attribute value (188756^MDC_MASS_BODY_FAT_FREE^MDC) because it has a special value and this value is not included in PCD-01 message

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-043 | | | +| TP label | Whitepaper. Fat Free Mass Numeric Object - Fat Free Mass value | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Float Type 1; C | Date-Time Conv 1; M | +| | | Fat Free Numeric 7; M | Fat Free Numeric 6; M | +| Test purpose |

    Check that:

    PHG processes correctly the Fat Free Mass Value (kg), Fat Free Mass Value (lb) and Time Stamp fields of Body Composition Measurement

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_018 AND C_MAN_BLE_021 AND C_MAN_BLE_025 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this test case are:
      • a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      • a. Body Composition Measurement (0x2A9C)
        • i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 0100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        • ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        • iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 11:08:25
        • iv. Field: Fat Free Mass (kg)
          • • Format: UINT16
          • • Value: 12800 (64.0 kg)
        • v. Field: Fat Free Mass (lb)
          • • This field is not included
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    • xv. Field: Height
      • • This field is not included
    • xvi. Field: User ID
      • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    • a. Body Composition Measurement (0x2A9C)
      • i. Field: Flags
        • • Format: 16 bit
        • • Value: 0000 0000 0100 0011 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Fat Free Mass in units of pound fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
      • ii. Field: Body Fat Percentage (%)
        • • Format: UINT16
        • • Value: Not relevant
      • iii. Field: Time Stamp
        • • Format: Date and Time
        • • Value: August 2nd, 2012, 11:09:05
      • iv. Field: Fat Free Mass (kg)
        • • This field is not included
      • v. Field: Fat Free Mass (lb)
        • • Format: UINT16
        • • Value: 14080 (140.8 lb)
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vi. Field: Soft Lean Mass (kg)

    • • This field is not included

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    7. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    | +| Pass/Fail criteria |

    In Step 5, the PHG under test shows the following measurement: 64.0 kg, with timestamp '2012-08-02 11:08:25'

    In Step 7, the PHG under test shows the following measurement 140.8 lbs, with timestamp '2012-08-02 11:09:05'

    | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-044 | | | +| TP label | Whitepaper. Soft Lean Mass Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Soft Lean Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Soft Lean Mass Numeric object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Soft Lean Mass Numeric object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_022 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:

    a. Body Composition Measurement (0x2A9C)

    • i. Field: Flags
      • • Format: 16 bit
      • • Value: 0000 0000 1000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
    • ii. Field: Body Fat Percentage (%)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Fat Free Mass (kg)
      • • This field is not included
    • v. Field: Fat Free Mass (lb)
      • • This field is not included
    • vi. Field: Soft Lean Mass (kg)
      • • Format: UINT16
      • • Value: Not relevant
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    • xv. Field: Height
      • • This field is not included
    • xvi. Field: User ID
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Soft Lean Mass Numeric object, Handle attribute

    | +| Pass/Fail criteria | In Step 5, the Soft Lean Mass Numeric object, Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • ❑ Object: Soft Lean Mass Numeric Object
    • ❑ Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • ❑ Attribute-type: INT-U16
    • ❑ Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-045 | | | +| TP label | Whitepaper. Soft Lean Mass Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Soft Lean Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Soft Lean Mass Numeric object, Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_SCADA, MDC_MASS_BODY_SOFT_LEAN}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_022 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 1000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    v. Field: Fat Free Mass (lb)

    • • This field is not included

    vi. Field: Soft Lean Mass (kg)

    • • Format: UINT16
    • • Value: Not relevant

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Soft Lean Mass Numeric object, Type attribute

    | +| Pass/Fail criteria | In Step 5, the Weight Numeric object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_MASS_BODY_SOFT_LEAN} | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_MASS_BODY_SOFT_LEAN or 57688 (dec) or E1 58 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    | + +| | | +|--|--------------------------------------------------------------------------------| +| | OBX ? 188760^MDC_MASS_BODY_SOFT_LEAN^MDC
    1.0.a X [current_date_time] | +|--|--------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-046 | | | +| TP label | Whitepaper. Soft Lean Mass Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Soft Lean Numeric 3; M | | +| Test purpose | Check that:
    PHG includes Soft Lean Mass Numeric object, Metric-Spec-Small attribute in transcoder output.
    [AND]
    Metric-Spec-Small is set to {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_022 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 1000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • This field is not included
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    • xv. Field: Height
      • • This field is not included
    • xvi. Field: User ID
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    3. 5. Check in PHG transcoder output the Soft Lean Mass Numeric object, Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 5, the Soft Lean Mass Numeric object, Metric-Spec-Small attribute is present and its value is {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes
    Metric-Spec-Small attribute is present:

    • Object: Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message
    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-047 | | | +| TP label | Whitepaper. Soft Lean Mass Numeric Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Soft Lean Numeric 4; M | Soft Lean Numeric 5; M | +| Test purpose | Check that:
    PHG includes Soft Lean Numeric object, Unit-Code attribute in transcoder output.
    [AND]
    IF Soft Lean Mass (Kg) field of Body Composition Measurement characteristic is present | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | THEN Soft Lean Mass Numeric object, Unit-Code attribute is set to MDC_DIM_KILO_G
    [AND]
    IF Soft Lean Mass (lb) field of Body Composition Measurement characteristic is present
    THEN Soft Lean Mass Numeric object, Unit-Code attribute is set to MDC_DIM_LB | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_022 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 1000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • This field is not included
        9. ix. Field: Body Water Mass (lb)
          • • This field is not included
        10. x. Field: Basal Metabolism
          • • This field is not included
        11. xi. Field: Muscle Percentage
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Soft Lean Mass Numeric object, Unit-Code attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Body Composition Measurement (0x2A9C)

    • i. Field: Flags
      • • Format: 16 bit
      • • Value: 0000 0000 1000 0011 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of pound fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
    • ii. Field: Body Fat Percentage (%)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Fat Free Mass (kg)
      • • This field is not included
    • v. Field: Fat Free Mass (lb)
      • • This field is not included
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • Format: UINT16
      • • Value: Not relevant
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xii. Field: Muscle Mass

    • This field is not included

    xiii. Field: Impedance

    • This field is not included

    xiv. Field: Weight

    • This field is not included

    xv. Field: Height

    • This field is not included

    xvi. Field: User ID

    • This field is not included

    7. Check in PHG transcoder output the Soft Lean Mass Numeric object, Unit-Code attribute.

    | +| Pass/Fail criteria |

    In Step 5, the Soft Lean Mass Numeric object, Unit-Code attribute is present and its value is MDC_DIM_KILO_G

    In Step 7, the Soft Lean Mass Numeric object, Unit-Code attribute is present and its value is MDC_DIM_LB

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_KILO_G or 1731 (dec) or 06 C3 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?][NM][188760^MDC_MASS_BODY_SOFT_LEAN^MDC][1.0.a][XX]
    263875^MDC_DIM_KILO_G^MDC     R  [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_LB or 1760 (dec) or 06 E0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?][NM][188760^MDC_MASS_BODY_SOFT_LEAN^MDC][1.0.a][XX]
    263904^MDC_DIM_LB^MDC     R  [current_date_time]
    | + +| | | | | +|-----------------|---------------------------------------------------------------------------|------------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-048 | | | +| TP label | Whitepaper. Soft Lean Mass Numeric Object - Absolute-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Soft Lean Numeric 6; M | Date-Time Conv 2; M | +| | | Date-Time Conv 4; M | Date-Time Conv 5; M | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    PHG transcodes Time Stamp field of Body Composition Measurement characteristic into Soft Lean Mass Numeric Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_022 AND C_MAN_BLE_025 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 1000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:39:27
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • This field is not included
        9. ix. Field: Body Water Mass (lb)
    | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Soft Lean Mass Numeric object, Absolute-Time-Stamp attribute

    | +| Pass/Fail criteria | In Step 5, the Soft Lean Mass Numeric object, Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Body Composition Measurement characteristic and fraction of seconds is set to 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 10 (hex) or 16 (dec)
      • • minute: 39 (hex) or 57 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX[?][188760^MDC_MASS_BODY_SOFT_LEAN^MDC 1.0.a     X    20120802103927+0000
    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-049 | | | +| TP label | Whitepaper. Soft Lean Mass Numeric Object - Simple-Nu-Observed-Value Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Soft Lean Numeric 7; M | Float Type 1; C | +| Test purpose | Check that:

    PHG transcodes Soft Lean Mass Value field of Body Composition Measurement characteristic into Soft Lean Mass Numeric Object - Simple-Nu-Observed-Value attribute | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_022 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 1000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • Format: UINT16
          • • Value: 8760 (43.8 kg)
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • This field is not included
        9. ix. Field: Body Water Mass (lb)
    | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Soft Lean Mass Numeric object, Simple-Nu-Observed-Value attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Body Composition Measurement (0x2A9C)

    i. Field: Flags

    • • Format: 16 bit
    • • Value: 0000 0000 1000 0011 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of pound fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included

    ii. Field: Body Fat Percentage (%)

    • • Format: UINT16
    • • Value: Not relevant

    iii. Field: Time Stamp

    • • Format: Date and Time
    • • Value: Not relevant

    iv. Field: Fat Free Mass (kg)

    • • This field is not included

    v. Field: Fat Free Mass (lb)

    • • This field is not included

    vi. Field: Soft Lean Mass (kg)

    • • This field is not included

    vii. Field: Soft Lean Mass (lb)

    • • Format: UINT16
    • • Value: 9640 (96.4 lb)

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    7. Check in PHG transcoder output the Soft Lean Mass Numeric object, Simple-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In Step 5, the Soft Lean Mass Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Soft Lean Mass Value (kg) field of Body Composition Measurement characteristic (43.8)

    In Step 7, the Soft Lean Mass Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Soft Lean Mass Value (lb) field of Body Composition Measurement characteristic (96.4).

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 42 D5 60 (hex) or FC 06 AE F0 (hex) or FD 00 AB 18 (hex) or FE 00 11 1C (hex) or FF 00 01 B6 (hex) or 43.8 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[?] NM 188760^MDC_MASS_BODY_SOFT_LEAN^MDC 1.0.a 43.8  263875^MDC_DIM_KILO_G^MDC     R  [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 93 18 40 (hex) or FC 0E B5 A0 (hex) or FD 01 78 90 (hex) or FE 00 25 A8 (hex) or FF 00 03 C4 (hex) or 96.4 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    | + +| | | +|--|------------------------------------------------------------------------------------------------------------| +| | OBX{? NM 188760^MDC_MASS_BODY_SOFT_LEAN^MDC 1.0.a 96.4
    263904^MDC_DIM_LB^MDC R [current_date_time] | +|--|------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-050 | | | +| TP label | Whitepaper. Soft Lean Mass Numeric Object - Simple-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Soft Lean Numeric 7; M | Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Soft Lean Mass Value field of Body Composition Measurement characteristic into Soft Lean Mass Numeric Object - Simple-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x007FFFFF)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_022 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 1000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • Format: UINT16
          • • Value: 8760 (43.8 kg)
    | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    • xv. Field: Height
      • • This field is not included
    • xvi. Field: User ID
      • • This field is not included

    5. Check in PHG transcoder output the Soft Lean Mass Numeric object, Simple-Nu-Observed-Value attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    • a. Body Composition Measurement (0x2A9C)
      • i. Field: Flags
        • • Format: 16 bit
        • • Value: 0000 0000 1000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
      • ii. Field: Body Fat Percentage (%)
        • • Format: UINT16
        • • Value: Not relevant
      • iii. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
      • iv. Field: Fat Free Mass (kg)
        • • This field is not included
      • v. Field: Fat Free Mass (lb)
        • • This field is not included
      • vi. Field: Soft Lean Mass (kg)
        • • Format: UINT16
        • • Value: FF FF (hex). Unsuccessful measurement
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    7. Check in PHG transcoder output the Soft Lean Mass Numeric object, Simple-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In Step 5, the Soft Lean Mass Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 43.8.

    In Step 7, the Soft Lean Mass Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 0x007FFFFFF.

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 42 D5 60 (hex) or FC 06 AE F0 (hex) or FD 00 AB 18 (hex) or FE 00 11 1C (hex) or FF 00 01 B6 (hex) or 43.8 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[? NM 188760^MDC_MASS_BODY_SOFT_LEAN ^MDC 1.0.a 43.8  263875^MDC_DIM_KILO_G ^MDC    R  [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: 00 7F FF FF (hex) or NaN (note that a decimal value is not allowed)
    | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b) WAN PCD-01 message

    PCD-01 message does not include segment with Simple-Nu-Observed-Value attribute value (188760^MDC_MASS_BODY_SOFT_LEAN^MDC) because it has a special value and this value is not included in PCD-01 message

    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-051 | | | +| TP label | Whitepaper. Soft Lean Mass Numeric object, Soft Lean Mass value | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Float Type 1; C | Date-Time Conv 1; M | +| | | Soft Lean Numeric 7; M | Soft Lean Numeric 6; M | +| Test purpose |

    Check that:

    PHG processes correctly the Soft Lean Mass Value (kg) and Time Stamp fields of Body Composition Measurement

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_018 AND C_MAN_BLE_022 AND C_MAN_BLE_025 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this test case are:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0000 1000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 11:08:25
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • Format: UINT16
          • • Value: 8760 (43.8 kg)
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    • xv. Field: Height
      • • This field is not included
    • xvi. Field: User ID
      • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    • a. Body Composition Measurement (0x2A9C)
      • i. Field: Flags
        • • Format: 16 bit
        • • Value: 0000 0000 1000 0011 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Soft Lean Mass in units of pound fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Body Water Mass, Impedance, Weight, Height and User ID fields are not included
      • ii. Field: Body Fat Percentage (%)
        • • Format: UINT16
        • • Value: Not relevant
      • iii. Field: Time Stamp
        • • Format: Date and Time
        • • Value: August 2nd, 2012, 11:09:05
      • iv. Field: Fat Free Mass (kg)
        • • This field is not included
      • v. Field: Fat Free Mass (lb)
        • • This field is not included
      • vi. Field: Soft Lean Mass (kg)
        • • This field is not included
      • vii. Field: Soft Lean Mass (lb)
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: UINT16
    • • Value: 9640 (96.4 lb)

    viii. Field: Body Water Mass (kg)

    • • This field is not included

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    7. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    | +| Pass/Fail criteria |

    In Step 5, the PHG under test shows the following measurement: 43.8 kg, with timestamp '2012-08-02 11:08:25'

    In Step 7, the PHG under test shows the following measurement: 96.4 lbs, with timestamp '2012-08-02 11:09:05'

    | +| Notes | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-052 | | | +| TP label | Whitepaper. Body Water Mass Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Water Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Body Water Numeric object, Handle Attribute in transcoder output

    [OR]

    If PHG includes Body Water Numeric object, Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_023 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. Body Composition Measurement (0x2A9C)

    • i. Field: Flags
      • • Format: 16 bit
      • • Value: 0000 0001 0000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Impedance, Weight, Height and User ID fields are not included
    • ii. Field: Body Fat Percentage (%)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Fat Free Mass (kg)
      • • This field is not included
    • v. Field: Fat Free Mass (lb)
      • • This field is not included
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • Format: UINT16
      • • Value: Not relevant
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    • xv. Field: Height
      • • This field is not included
    • xvi. Field: User ID
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Body Water Numeric object, Handle attribute

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria | In Step 5, the Body Water Numeric object, Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Body Water Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-053 | | | +| TP label | Whitepaper. Body Water Mass Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Water Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Body Water Numeric object, Type attribute in transcoder output.

    [AND]

    Type is set to {MDC_PART_SCADA, MDC_MASS_BODY_WATER}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_023 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0001 0000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
    | | | + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • Format: UINT16
    • • Value: Not relevant

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Body Water Numeric object, Type attribute

    | +| Pass/Fail criteria | In Step 5, the Weight Numeric object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_MASS_BODY_WATER} | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • ❑ Object: Body Water Numeric Object
    • ❑ Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • ❑ Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • ❑ Attribute-value:
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_MASS_BODY_WATER or 57692 (dec) or E1 5C (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX ?  188764^MDC_MASS_BODY_WATER^MDC  1.0.a     X  [current_date_time]
    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-054 | | | +| TP label | Whitepaper. Body Water Mass Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Water Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Body Water Numeric object, Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated).

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_023 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0001 0000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant
        9. ix. Field: Body Water Mass (lb)
          • • This field is not included
        10. x. Field: Basal Metabolism
          • • This field is not included
        11. xi. Field: Muscle Percentage
    | | | + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    5. Check in PHG transcoder output the Body Water Numeric object, Metric-Spec-Small attribute

    | +| Pass/Fail criteria | In Step 5, the Body Water Numeric object, Metric-Spec-Small attribute is present and its value is {0xF040} (mss-avail-intermittent mss-avail-stored-data mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated). | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Body Water Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent(0), mss-avail-stored-data(1), mss-upd-aperiodic(2), mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-055 | | | +| TP label | Whitepaper. Body Water Mass Numeric Object - Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Water Numeric 4; M | Body Water Numeric 5; M | +| Test purpose |

    Check that:

    PHG includes Body Water Numeric object, Unit-Code attribute in transcoder output.

    [AND]

    IF Body Water Mass (Kg) field of Body Composition Measurement characteristic is present
    THEN Body Water Numeric object, Unit-Code attribute is set to MDC_DIM_KILO_G

    [AND]

    IF Body Water Mass (lb) field of Body Composition Measurement characteristic is present
    THEN Body Water Numeric object, Unit-Code attribute is set to MDC_DIM_LB

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_023 | | | +| Other PICS | | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0001 0000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant
        9. ix. Field: Body Water Mass (lb)
          • • This field is not included
        10. x. Field: Basal Metabolism
          • • This field is not included
        11. xi. Field: Muscle Percentage
          • • This field is not included
        12. xii. Field: Muscle Mass
          • • This field is not included
        13. xiii. Field: Impedance
          • • This field is not included
        14. xiv. Field: Weight
    | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Body Water Numeric object, Unit-Code attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Body Composition Measurement (0x2A9C)

    • i. Field: Flags
      • • Format: 16 bit
      • • Value: 0000 0001 0000 0011 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of pound fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Fat Free Mass, Impedance, Weight, Height and User ID fields are not included
    • ii. Field: Body Fat Percentage (%)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Fat Free Mass (kg)
      • • This field is not included
    • v. Field: Fat Free Mass (lb)
      • • This field is not included
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • Format: UINT16
      • • Value: Not relevant
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
      • • This field is not included
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xv. Field: Height

    • This field is not included

    xvi. Field: User ID

    • This field is not included

    7. Check in PHG transcoder output the Body Water Numeric object, Unit-Code attribute.

    | +| Pass/Fail criteria |

    In Step 5, the Body Water Numeric object, Unit-Code attribute is present and its value is MDC_DIM_KILO_G

    In Step 7, the Body Water Numeric object, Unit-Code attribute is present and its value is MDC_DIM_LB

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Body Water Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_KILO_G or 1731 (dec) or 06 C3 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?][NM][188764^MDC_MASS_BODY_WATER^MDC][1.0.a][XX]
    263875^MDC_DIM_KILO_G^MDC][[R]][[current_date_time]]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Body Water Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: INT-U16
    • Attribute-value: MDC_DIM_LB or 1760 (dec) or 06 E0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[?][NM][188764^MDC_MASS_BODY_WATER^MDC][1.0.a][XX]
    263904^MDC_DIM_LB^MDC][[R]][[current_date_time]]
    | + +| | | | | +|---------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-056 | | | +| TP label | Whitepaper. Body Water Mass Numeric Object - Absolute-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Water Numeric 6; M | Date-Time Conv 2; M | +| Test purpose | | Date-Time Conv 4; M | Date-Time Conv 5; M | +| | |

    Check that:

    PHG transcodes Time Stamp field of Body Composition Measurement characteristic into Body Water Numeric Object - Absolute-Time-Stamp attribute

    [AND]

    PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format

    [AND]

    The fraction of seconds in Absolute Time at transcoder output is 0

    | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_023 AND C_MAN_BLE_025 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0001 0000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 10:39:27
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant
        9. ix. Field: Body Water Mass (lb)
          • • This field is not included
        10. x. Field: Basal Metabolism
          • • This field is not included
        11. xi. Field: Muscle Percentage
          • • This field is not included
        12. xii. Field: Muscle Mass
          • • This field is not included
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Body Water Numeric object, Absolute-Time-Stamp attribute

    | +| Pass/Fail criteria | In Step 5, the Body Water Numeric object, Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Body Composition Measurement characteristic and fraction of seconds is set to 0 | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Absolute-Time-Stamp attribute is present:

    • Object: Body Water Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)
    • Attribute-type: SEQUENCE {century (INT-U8), year (INT-U8), month (INT-U8), day (INT-U8), hour (INT-U8), minute (INT-U8), second (INT-U8), sec-fractions (INT-U8)} (BCD encoding)
    • Attribute-value:
      • • century: 20 (hex) or 32 (dec)
      • • year: 12 (hex) or 18 (dec)
      • • month: 08 (hex) or 8 (dec)
      • • day: 02 (hex) or 2 (dec)
      • • hour: 10 (hex) or 16 (dec)
      • • minute: 39 (hex) or 57 (dec)
      • • second: 27 (hex) or 39 (dec)
      • • sec-fractions: 00 (hex) or 0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):

    OBX ? 188764^MDC_MASS_BODY_WATER^MDC 1.0.a X
    20120802103927+0000

    | + +| | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-057 | | +| TP label | Whitepaper. Body Water Mass Numeric Object - Simple-Nu-Observed-Value Attribute 1 | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | +| | Testable items | Body Water Numeric 7; M      Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Body Water Mass Value field of Body Composition Measurement characteristic into Body Water Numeric Object - Simple-Nu-Observed-Value attribute

    | | +| Applicability | C MAN_BLE_000 AND C MAN_BLE_002 AND C MAN_BLE_018 AND C MAN_BLE_023 | | +| Other PICS | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0001 0000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • Format: UINT16
          • • Value: 9500 (47.5 kg)
        9. ix. Field: Body Water Mass (lb)
          • • This field is not included
        10. x. Field: Basal Metabolism
          • • This field is not included
        11. xi. Field: Muscle Percentage
          • • This field is not included
        12. xii. Field: Muscle Mass
          • • This field is not included
        13. xiii. Field: Impedance
          • • This field is not included
        14. xiv. Field: Weight
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Body Water Numeric object, Simple-Nu-Observed-Value attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Body Composition Measurement (0x2A9C)

    • i. Field: Flags
      • • Format: 16 bit
      • • Value: 0000 0001 0000 0011 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of pound fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Fat Free Mass, Impedance, Weight, Height and User ID fields are not included
    • ii. Field: Body Fat Percentage (%)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Fat Free Mass (kg)
      • • This field is not included
    • v. Field: Fat Free Mass (lb)
      • • This field is not included
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • Format: UINT16
      • • Value: 10450 (104.5 lb)
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    • xiv. Field: Weight
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    7. Check in PHG transcoder output the Body Water Numeric object, Simple-Nu-Observed-Value attribute.

    | +| Pass/Fail criteria |

    In Step 5, the Body Water Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Body Water Mass Value (kg) field of Body Composition Measurement characteristic (47.5)

    In Step 7, the Body Water Numeric object, Simple-Nu-Observed-Value attribute is present and its value matches with Body Water Mass Value (lb) field of Body Composition Measurement characteristic (104.5).

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Body Water Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 48 7A B0 (hex) or FC 07 3F 78 (hex) or FD 00 B9 8C (hex) or FE 00 12 8E (hex) or FF 00 01 DB (hex) or 47.5 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 188764^MDC_MASS_BODY_WATER^MDC 1.0.a 47.5 
    263875^MDC_DIM_KILO_G^MDC     R   current_date_time

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Body Water Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 9F 74 50 (hex) or FC 0F F2 08 (hex) or FD 01 98 34 (hex) or FE 00 28 D2 (hex) or FF 00 04 15 (hex) or 104.5 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 188764^MDC_MASS_BODY_WATER^MDC 1.0.a 104.5 
    263904^MDC_DIM_LB^MDC     R   current_date_time
    | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-058 | | | +| TP label | Whitepaper. Body Water Mass Numeric Object - Simple-Nu-Observed-Value Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Body Water Numeric 7; M | Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes Body Water Mass Value field of Body Composition Measurement characteristic into Body Water Numeric Object - Simple-Nu-Observed-Value attribute

    | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [AND]
    PHG assigns the following special values: NaN (0x007FFFFFF). | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_023 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0001 0000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • Format: UINT16
          • • Value: 9500 (47.5 kg)
        9. ix. Field: Body Water Mass (lb)
          • • This field is not included
        10. x. Field: Basal Metabolism
          • • This field is not included
        11. xi. Field: Muscle Percentage
          • • This field is not included
        12. xii. Field: Muscle Mass
    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check in PHG transcoder output the Body Water Numeric object, Simple-Nu-Observed-Value attribute

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Body Composition Measurement (0x2A9C)

    • i. Field: Flags
      • • Format: 16 bit
      • • Value: 0000 0001 0000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Impedance, Weight, Height and User ID fields are not included
    • ii. Field: Body Fat Percentage (%)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • iv. Field: Fat Free Mass (kg)
      • • This field is not included
    • v. Field: Fat Free Mass (lb)
      • • This field is not included
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • Format: UINT16
      • • Value: FF FF (hex). Unsuccessful measurement.
    • ix. Field: Body Water Mass (lb)
      • • This field is not included
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    7. Check in PHG transcoder output the Soft Lean Mass Numeric object, Simple-Nu-Observed-Value attribute

    | +| Pass/Fail criteria |

    In Step 5, the Body Water Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 47.5.

    In Step 7, the Body Water Numeric object, Simple-Nu-Observed-Value attribute is present and its value is 0x007FFFFF.

    | +| Notes |

    In Step 5, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Body Water Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FB 48 7A B0 (hex) or FC 07 3F 78 (hex) or FD 00 B9 8C (hex) or FE 00 12 8E (hex) or FF 00 01 DB (hex) or 47.5 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX ? NM 188764^MDC_MASS_BODY_WATER ^MDC 1.0.a 47.5  263875^MDC_DIM_KILO_G ^MDC    R  [current_date_time]

    In Step 7, possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Body Water Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: 00 7F FF FF (hex) or NaN (note that a decimal value is not allowed)

    b) WAN PCD-01 message

    PCD-01 message does not include segment with Simple-Nu-Observed-Value attribute value (188764^MDC_MASS_BODY_WATER^MDC) because it has a special value and this value is not included in PCD-01 message

    | + +| | | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|-------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-059 | | | | +| TP label | Whitepaper. Body Water Mass Numeric object, Body Water Mass value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | +| | Testable items | Float Type 1; C | Date-Time Conv 1; M | Body Water Numeric 6; M | +| | | Body Water Numeric 7; M | | | +| Test purpose | Check that:
    PHG processes correctly the Body Water Mass Value (kg) and Time Stamp fields of Body Composition Measurement | | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_018 AND C_MAN_BLE_023 AND C_MAN_BLE_025 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this test case are:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0001 0000 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Fat Free Mass, Soft Lean Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: August 2nd, 2012, 11:08:25
        4. iv. Field: Fat Free Mass (kg)
          • • This field is not included
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • This field is not included
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • Format: UINT16
          • • Value: 9500 (47.5 kg)
        9. ix. Field: Body Water Mass (lb)
          • • This field is not included
        10. x. Field: Basal Metabolism
          • • This field is not included
        11. xi. Field: Muscle Percentage
          • • This field is not included
        12. xii. Field: Muscle Mass
          • • This field is not included
        13. xiii. Field: Impedance
    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    5. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    6. The simulated PHD sends the Measurement to the PHG under test with the following value:

    a. Body Composition Measurement (0x2A9C)

    • i. Field: Flags
      • • Format: 16 bit
      • • Value: 0000 0001 0000 0011 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp and Body Water Mass in units of pound fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Soft Lean Mass, Fat Free Mass, Impedance, Weight, Height and User ID fields are not included
    • ii. Field: Body Fat Percentage (%)
      • • Format: UINT16
      • • Value: Not relevant
    • iii. Field: Time Stamp
      • • Format: Date and Time
      • • Value: August 2nd, 2012, 11:09:05
    • iv. Field: Fat Free Mass (kg)
      • • This field is not included
    • v. Field: Fat Free Mass (lb)
      • • This field is not included
    • vi. Field: Soft Lean Mass (kg)
      • • This field is not included
    • vii. Field: Soft Lean Mass (lb)
      • • This field is not included
    • viii. Field: Body Water Mass (kg)
      • • This field is not included
    • ix. Field: Body Water Mass (lb)
      • • Format: UINT16
      • • Value: 10450 (104.5 lb)
    • x. Field: Basal Metabolism
      • • This field is not included
    • xi. Field: Muscle Percentage
      • • This field is not included
    • xii. Field: Muscle Mass
      • • This field is not included
    • xiii. Field: Impedance
      • • This field is not included
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included
    xiv. Field: Weight
    • • This field is not included
    xv. Field: Height
    • • This field is not included
    xvi. Field: User ID
    • • This field is not included
    7. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp). | +| Pass/Fail criteria | In Step 5, the PHG under test shows the following measurement: 47.5 kg, with timestamp '2012-08-02 11:08:25'
    In Step 7, the PHG under test shows the following measurement: 104.5 lbs, with timestamp '2012-08-02 11:09:05' | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-060 | | | +| TP label | Whitepaper. Weight Scale Feature Characteristic – Measurement Resolution | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | WS Feature 1; M | WS Feature 2; M | +| | | WS Feature 4; M | WS Feature 5; M | +| | | | WS Feature 6; M | +| Test purpose | Check that:
    PHG transcodes Weight Scale measurements and presents them properly in transcoder output. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_017 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Weight Scale Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case are:
      1. Weight Scale Feature (0x2A9E)
        • Format: 32 bit
        • Value: 0000 0000 0000 0000 0000 0001 0011 0111 (MSB → LSB). Time Stamp, Multiple Users, Height and BMI supported. Weight resolution of 0.01 kg / 0.02 lb, Height resolution of 0.005 m / 0.5 in.
      2. Weight Measurement (0x2A9D)
    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. When the pairing has been completed (Connection state), force the PHG under test to read the Weight Scale Feature characteristic.
    5. The simulated PHD sends the Measurement to the PHG under test with the following value:
      1. Weight Measurement (0x2A9D)
        1. Field: Flags
          • Format: 8 bit
          • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height and BMI fields are included, User ID fields is not included
    | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ii. Field: Weight (Kg)
      • • Format: UINT16
      • • Value: 16094 (80.47 kg)
    • iii. Field: Weight (lb)
      • • This field is not included
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • v. Field: Height (m)
      • • Format: UINT16
      • • Value: 1805 (1.805 m)
    • vi. Field: Height (in)
      • • This field is not included
    • vii. Field: BMI (kg/m2)
      • • Format: UINT16.
      • • Value: Not relevant
    • viii. Field: User ID
      • • This field is not included

    6. Check in PHG transcoder output the measurements values.

    | +| Pass/Fail criteria | In Step 5, the PHG under test shows the following measurements: Weight 80.47 kg, Height 180.5 cm. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Weight Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FE 00 1F 6F (hex) or 80.47 (dec)

    Simple-Nu-Observed-Value attribute is present:

    • Height Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FF 00 07 0D (hex) or 180.5 (dec)
    | + +| | | | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|--|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-061 | | | | | +| TP label | Whitepaper. Body Composition Feature Characteristic – Measurement Resolution | | | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | | | +| | Testable items | BC Feature 1; M | BC Feature 2; M | | | +| Test purpose | | BC Feature 5; M | BC Feature 6; M | | | +| | | BC Feature 7; M | | | | +| Applicability | Check that:
    PHG transcodes Body Composition measurements and presents them properly in transcoder output. | | | | | +| Other PICS | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 | | | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this test case are:
      1. a. Body Composition Feature (0x2A9B)
        • • Format: 32 bit
        • • Value: 0000 0000 0000 0000 0011 0000 1110 0011 (MSB → LSB). Time Stamp, Multiple Users, Fat Free Mass, Soft Lean Mass and Body Water Mass supported. Weight resolution of 0.01 kg / 0.02 lb.
      2. b. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), force the PHG under test to read the Body Composition Scale Feature characteristic.
    5. 5. The simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0000 0001 1100 0010 (MSB → LSB). Body Fat Percentage in units of %, Time Stamp, Fat Free Mass in units of Kg, Soft Lean Mass in units of Kg and Body Water Mass in units of Kg fields are included, Basal Metabolism, Muscle Percentage, Muscle Mass, Impedance, Weight, Height and User ID fields are not included
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        4. iv. Field: Fat Free Mass (kg)
          • • Format: UINT16
          • • Value: 12864 (64.32 kg)
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • Format: UINT16
          • • Value: 14022 (70.11 kg)
        7. vii. Field: Soft Lean Mass (lb)
          • • This field is not included
        8. viii. Field: Body Water Mass (kg)
          • • Format: UINT16
          • • Value: 11296 (56.48 kg)
        9. ix. Field: Body Water Mass (lb)
          • • This field is not included
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    x. Field: Basal Metabolism

    • • This field is not included

    xi. Field: Muscle Percentage

    • • This field is not included

    xii. Field: Muscle Mass

    • • This field is not included

    xiii. Field: Impedance

    • • This field is not included

    xiv. Field: Weight

    • • This field is not included

    xv. Field: Height

    • • This field is not included

    xvi. Field: User ID

    • • This field is not included

    6. Check in PHG transcoder output the measurements values.

    | +| Pass/Fail criteria | In Step 6, the PHG under test shows the following measurements: Fat Free Mass 64.32 kg, Soft Lean Mass 70.11 kg, Body Water Mass 56.48 kg. | +| Notes |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Fat Free Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FE 00 19 20 (hex) or 64.32 (dec)

    Simple-Nu-Observed-Value attribute is present:

    • Soft Lean Mass Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FE 00 1B 63 (hex) or 70.11 (dec)

    Simple-Nu-Observed-Value attribute is present:

    • Body Water Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: FE 00 16 10 (hex) or 56.48 (dec)
    | + +| | | | +|----------------------|----------------------------------------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-062 | | +| TP label | Whitepaper. Weight Measurement – Height and BMI pair | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | +| | Testable items | Pair Numeric 1; M | +| Test purpose |

    Check that:

    Weight Measurement includes, if present, both Height and BMI Value fields as a pair.

    | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_017 | | +| Other PICS | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this test case is:
      1. a. Weight Measurement (0x2A9D)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1010 (MSB → LSB). Weight Measurement Value in units of Kg, Time Stamp, Height in units of metre and BMI fields are included, User ID field is not included
        2. ii. Field: Weight (Kg)
          • • Format: UINT16
          • • Value: Not relevant
        3. iii. Field: Weight (lb)
          • • This field is not included
        4. iv. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant
        5. v. Field: Height (m)
          • • Format: UINT16
          • • Value: 1800 (1.80 m)
        6. vi. Field: Height (in)
          • • This field is not included
        7. vii. Field: BMI (kg/m2)
          • • Format: UINT16
          • • Value: 247 (24.7)
        8. viii. Field: User ID
          • • This field is not included
    5. 5. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).
    6. 6. The simulated PHD sends the Measurement to the PHG under test with the following value:
      1. a. Weight Measurement (0x2A9D)
        1. i. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 1011 (MSB → LSB). Weight Measurement Value in units of pound, Time Stamp, Height in units of inch and BMI fields are included, User ID field is not included
        2. ii. Field: Weight (Kg)
          • • This field is not included
    | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • iii. Field: Weight (lb)
      • • Format: UINT16
      • • Value: Not relevant
    • iv. Field: Time Stamp
      • • Format: Date and Time
      • • Value: Not relevant
    • v. Field: Height (m)
      • • Format: UINT16
      • • Value: 1800 (1.80 m)
    • vi. Field: Height (in)
      • • This field is not included.
    • vii. Field: BMI (kg/m2)
      • • This field is not included.
    • viii. Field: User ID
      • • This field is not included.

    7. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    8. The simulated PHD sends the Measurement to the PHG under test with the following value:

    • a. Weight Measurement (0x2A9D)
      • i. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 1011 (MSB → LSB). Weight Measurement Value in units of pound, Time Stamp, Height in units of inch and BMI fields are included, User ID field is not included
      • ii. Field: Weight (Kg)
        • • This field is not included
      • iii. Field: Weight (lb)
        • • Format: UINT16
        • • Value: Not relevant
      • iv. Field: Time Stamp
        • • Format: Date and Time
        • • Value: Not relevant
      • v. Field: Height (m)
        • • This field is not included.
      • vi. Field: Height (in)
        • • This field is not included.
      • vii. Field: BMI (kg/m2)
        • • Format: UINT16
        • • Value: 247 (24.7)
      • viii. Field: User ID
        • • This field is not included.

    9. Check that the PHG accepts the measurement and decodes its value properly (measurement values, units and time stamp).

    | +| Pass/Fail criteria | In Step 5, both Height and BMI measurements are properly received and transcoded by the | + +| | | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PHG.
    In Step 7, the PHG shows an error message due to the absence of BMI Value.
    In Step 9, the PHG shows an error message due to the absence of Height Value. | +| Notes | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/WS/BV-063 | | | +| TP label | Whitepaper. Body Composition Measurement Characteristic – Multiple Packet Measurement | | | +| Coverage | Spec | [Bluetooth PHDT v1.5] | | +| | Testable items | Multi Packet Numeric 1; M | | +| Test purpose | Check that:
    PHG is able to transcode a measurement that has been sent in two pieces. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_018 AND C_MAN_BLE_038 | | | +| Other PICS | C_MAN_BLE_026, C_MAN_BLE_027, C_MAN_BLE_028, C_MAN_BLE_029,
    C_MAN_BLE_031, C_MAN_BLE_032, C_MAN_BLE_033, C_MAN_BLE_034,
    C_MAN_BLE_035 | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Profile (device specialization) supported by the PHG under test, it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this test case are:
      1. a. Body Composition Measurement (0x2A9C)
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state) the simulated PHD sends the next message split in two independent Body Composition Measurements:
      1. a. Body Composition Measurement (0x2A9C)
        1. i. Field: Flags
          • • Format: 16 bit
          • • Value: 0001 X XXXX XXX0 (MSB → LSB). Multiple Packet Measurement bit is set to 1. Measurement Units bit is set to 0. The other bits are set following the PICS
        2. ii. Field: Body Fat Percentage (%)
          • • Format: UINT16
          • • Value: 125 (12.5 %)
        3. iii. Field: Time Stamp
          • • Format: Date and Time
          • • Value: Not relevant. Present if (C_MAN_BLE_026 = TRUE)
        4. iv. Field: Fat Free Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant. Present if (C_MAN_BLE_032 = TRUE)
        5. v. Field: Fat Free Mass (lb)
          • • This field is not included
        6. vi. Field: Soft Lean Mass (kg)
          • • Format: UINT16
          • • Value: Not relevant. Present if (C_MAN_BLE_033 = TRUE)
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vii. Field: Soft Lean Mass (lb)

    • • This field is not included

    viii. Field: Body Water Mass (kg)

    • • Format: UINT16
    • • Value: Not relevant. Present if (C_MAN_BLE_034 = TRUE)

    ix. Field: Body Water Mass (lb)

    • • This field is not included

    x. Field: Basal Metabolism

    • • Format: UINT16
    • • Value: Not relevant. Present if (C_MAN_BLE_028 = TRUE)

    xi. Field: Muscle Percentage

    • • Format: UINT16
    • • Value: Not relevant. Present if (C_MAN_BLE_029 = TRUE)

    xii. Field: Muscle Mass (kg)

    • • Format: UINT16
    • • Value: Not relevant. Present if (C_MAN_BLE_031 = TRUE)

    xiii. Field: Muscle Mass (lb)

    • • This field is not included

    xiv. Field: Impedance

    • • Format: UINT16
    • • Value: Not relevant. Present if (C_MAN_BLE_035 = TRUE)

    xv. Field: Weight

    • • This field is not included

    xvi. Field: Height

    • • This field is not included

    xvii. Field: User ID

    • • Format: UINT8
    • • Value: Not relevant. Present if (C_MAN_BLE_027 = TRUE)

    5. The PHG receives the first Body Composition Measurement, checks that Multiple Packet Measurement bit Flag is set to 1, and waits for the second Body Composition Measurement.

    6. The PHG receives the second Body Composition Measurement.

    7. Check in PHG transcoder output the measurements values.

    | +| Pass/Fail criteria | In Step 7, both pieces of the Measurement are presented in transcoder output as a unique Measurement. | +| Notes | | + +# Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-Bluetooth PHDT v1.3] Bluetooth SIG (2012), *Personal Health Devices Transcoding White Paper* (version 1.3) +[https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc\\_id=294540](https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=294540) +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-CDG 2017] Personal Connected Health Alliance, Continua Design Guidelines (2017), "Keratin", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.13. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.11. + +- [b-TI] PHD Testable items. Test Tool v8.0.0.0 – Excel sheet v1.10. + + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.850.7-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.850.7-202008-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..100e218eec0012f317a4ff18399bd7cc45142140 --- /dev/null +++ b/marked/H/T-REC-H.850.7-202008-I_PDF-E/raw.md @@ -0,0 +1,2920 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.850.7** + +(08/2020) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS +E-health multimedia systems, services and applications – +Interoperability compliance testing of personal health +systems (HRN, PAN, LAN, TAN and WAN) + +--- + +**Conformance of ITU-T H.810 personal health +system: Personal Health Devices interface +Part 10G: Transcoding for Bluetooth Low +Energy: Personal Health Gateway – Continuous +glucose monitoring** + +Recommendation ITU-T H.850.7 + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.850.7 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10G: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Continuous glucose monitoring + +## Summary + +Recommendation ITU-T H.850.7 provides a test suite structure (TSS) and the test purposes (TP) for the transcoding of continuous glucose monitoring data by personal health gateways (PHGs) in the Personal Health Devices (PHD) interface of application-level data between the Bluetooth Low Energy Bluetooth Generic Attribute Profile (GATT) format and the IEEE 11073-20601 data format, of which Recommendation ITU-T H.810 (2016) is the base Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. + +Recommendation ITU-T H.850.7 is a transposition of clause 3.9 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. A number of versions of this specification existed before transposition. + +This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.850.7 | 2017-04-29 | 16 | 11.1002/1000/13360 | +| 2.0 | ITU-T H.850.7 | 2019-11-29 | 16 | 11.1002/1000/14122 | +| 3.0 | ITU-T H.850.7 | 2020-08-13 | 16 | 11.1002/1000/14351 | + +## Keywords + +Bluetooth Generic Attribute Profile, Bluetooth Low Energy (BLE), Conformance testing, Continua Design Guidelines, continuous glucose monitoring, data format transcoding, e-health, IEEE 11073-20601, ITU-T H.810, personal area network, personal connected health devices, Personal Health Devices interface, Personal Health Gateway, touch area network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 3 | +| 3.1 Terms defined elsewhere ..... | 3 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 4 | +| 6 Test suite structure..... | 6 | +| 7 Electronic attachment ..... | 8 | +| Annex A Test purposes ..... | 9 | +| A.1 TP definition conventions..... | 9 | +| A.2 Subgroup 2.4.8 – Whitepaper Continuous glucose monitoring requirements (CGM) ..... | 10 | +| Bibliography..... | 186 | + +**Electronic attachment:** This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +## Introduction + +This Recommendation is a transposition of clause 3.9 of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 10: PHD Transcoding Whitepaper. Personal Health Gateway (Version 1.7, 2017-07-18), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. + +| Version | Date | Revision history | +|---------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1.0 | 2012-10-05 | Initial release for Test Tool DG2011 based on the requirements in [b-CDG 2011]. | +| 1.1 | 2013-05-24 | Initial release for Test Tool DG2012. It uses "TSS&TP_DG2011_LP-PAN_PART_10_v1.0.doc" as a baseline and adds new features included in [b-CDG 2012] (BPM and HR profiles). | +| 1.2 | 2014-01-24 | Initial release for Test Tool DG2013. It uses "TSS&TP_DG2012_LP-PAN_PART_10_v1.1.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]:
    • • Adds glucose meter BLE
    • • Adds BLE SSP support
    • • Adds NFC new transport
    • • Adds INR device specialization
    | +| 1.3 | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.2.doc" as a baseline and adds new features included in Documentation Enhancements:
    • • "Other PICS" row has been added
    | +| 1.4 | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_LP-PAN_PART_10_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015]:
    • • Adds WS/BCA BLE device specialization
    • • Adds SABTE IEEE device specialization
    | +| 1.5 | 2016-01-26 | First maintenance release for Test Tool DG2015. It uses "TSS&TP_DG2015_LP-PAN_PART_10_v1.4.doc" as a baseline and adds some updates according to the Maintenance 2015 activity. | +| 1.6 | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]:
    • • Adds PLX BLE device specialization
    • • Adds PLX CGM device specialization
    | +| 1.7 | 2017-07-18 | Second Maintenance Release for Test Tool DG2016. It uses "TSS&TP_DG2016_LP-PAN_PART_10_v1.6.doc" as a baseline and corrects minor typos. | +| 1.8 | 2018-10-17 | It uses version 1.7 as a baseline and adds corrections due to the inclusion of CGM BLE profile test cases. | +| 1.9 | 2020-06-02 | Updates related to the value of the Reg-Cert-Data-List according to [b-CDG 2017]. | + +## Recommendation ITU-T H.850.7 + +## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10G: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Continuous glucose monitoring + +# 1 Scope + +The scope of this Recommendation1 is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices interface based on the requirements defined in the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability at this interface. + +The TSS and TP for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 10G. + +- Part 1: Optimized exchange protocol. Personal Health Device +- Part 2: Optimized exchange protocol. Personal Health Gateway +- Part 3: Continua design guidelines. Personal Health Device +- Part 4: Continua design guidelines. Personal Health Gateway +- Part 5: Device specializations. Personal Health Devices interface. This document is divided into the following subparts: + - Part 5A: Weighing scales + - Part 5B: Glucose meter + - Part 5C: Pulse oximeter + - Part 5D: Blood pressure monitor + - Part 5E: Thermometer + - Part 5F: Cardiovascular fitness and activity monitor + - Part 5G: Strength fitness equipment + - Part 5H: Independent living activity hub + - Part 5I: Adherence monitor + - Part 5J: Insulin pump + - Part 5K: Peak expiratory flow monitor + - Part 5L: Body composition analyser + - Part 5M: Basic electrocardiograph + - Part 5N: International normalized ratio monitor + - Part 5O: Sleep apnoea breathing therapy equipment (SABTE) + - Part 5P: Continuous glucose monitor (CGM) + +--- + +1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. + +- Part 6: Device specializations. Personal Health Gateway +- Part 7: Continua Design Guidelines. BLE Personal Health Device +- Part 8: Continua Design Guidelines. BLE Personal Health Gateway +- Part 9: Personal Health Devices Transcoding Whitepaper. Personal Health Devices +- Part 10: Personal Health Devices Transcoding Whitepaper. Personal Health Gateway. In addition to the main part, the document is subdivided in the following subparts: + - Part 10A: Whitepaper Thermometer requirements + - Part 10B: Whitepaper Blood pressure requirements + - Part 10C: Whitepaper Heart rate requirements + - Part 10D: Whitepaper Glucose meter requirements + - Part 10E: Whitepaper Weighing scales requirements + - Part 10F: Whitepaper Pulse oximeter requirements + - **Part 10G: Whitepaper Continuous glucose monitoring requirements** + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.810 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*. +- [Bluetooth PHDT v1.4] Bluetooth SIG (2013), *Personal Health Devices Transcoding White Paper, v1.4*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=294539](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=294539) +- [Bluetooth PHDT v1.5] Bluetooth SIG (2014), *Personal Health Devices Transcoding White Paper, v1.5*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=272346](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=272346) +- [Bluetooth PHDT v1.6] Bluetooth SIG (2015), *Personal Health Devices Transcoding White Paper, v1.6*. +[https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc\\_id=310657](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=310657) +- [ISO/IEEE 11073-104xx] ISO/IEEE 11073-104xx (in force), *Health informatics – Personal health device communication – Device specialization*. NOTE – Shorthand to refer to the collection of device specialization standards that utilize [ISO/IEEE 11073-20601-2015A], where xx can be any number from 01 to 99, inclusive. +- [ISO/IEEE 11073-20601-2015A] ISO/IEEE 11073-20601:2010, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2010 Amd 1:2015. + with + + +- [ISO/IEEE 11073-20601-2016C] ISO/IEEE 11073-20601:2016, *Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol*, including ISO/IEEE 11073-20601:2016/Cor.1:2016. + with + +- [IHE PCD TF 1] IHE PCD TF 1 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 1: Integration Profiles*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol1\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol1_FT_2012-08-16.pdf) +- [IHE PCD TF 2] IHE PCD TF 2 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 2: Transactions*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol2\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol2_FT_2012-08-16.pdf) +- [IHE PCD TF 3] IHE PCD TF 3 (2012), *IHE Patient Care Device Technical Framework – Revision 2.0. Volume 3: Semantic Content*. +[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_PCD\\_TF\\_Rev2-0\\_Vol3\\_FT\\_2012-08-16.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Rev2-0_Vol3_FT_2012-08-16.pdf) + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ISO/IEEE 11073-20601-2016C]: A node that collects and transmits personal health data to an associated manager. + +**3.1.2 manager** [ISO/IEEE 11073-20601-2016C]: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|--------------------------------| +| ATS | Abstract Test Suite | +| CDG | Continua Design Guidelines | +| CGM | Continuous Glucose Monitor | +| DUT | Device Under Test | +| GUI | Graphical User Interface | +| INR | International Normalized Ratio | +| IP | Insulin Pump | +| IUT | Implementation Under Test | +| LSB | Least Significant Bit | +| MDS | Medical Device System | +| MSB | Most Significant Bit | + +| | | +|-------|-------------------------------------------------------| +| NFC | Near Field Communication | +| PAN | Personal Area Network | +| PCD | Patient Care Device | +| PCO | Point of Control and Observation | +| PCT | Protocol Conformance Testing | +| PHD | Personal Health Device | +| PHDC | Personal Healthcare Device Class | +| PHG | Personal Health Gateway | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| RACP | Record Access Control Point | +| SABTE | Sleep Apnoea Breathing Therapy Equipment | +| SCR | Static Conformance Review | +| SDP | Service Discovery Protocol | +| SOAP | Simple Object Access Protocol | +| TCRL | Test Case Reference List | +| TCWG | Test and Certification Working Group | +| TP | Test Purposes | +| TSS | Test Suite Structure | +| USB | Universal Serial Bus | +| WDM | Windows Driver Model | + +## 5 Conventions + +In this text, the uppercase letter L is used as the symbol for litre. + +Several of the test purposes in Annex A refer to "WAN PCD-01 messages"; these messages are specified in the patient care device (PCD) technical framework defined in [IHE PCD TF 1], [IHE PCD TF 2] and [IHE PCD TF 3]. Similarly, the "IEEE 11073 Objects and Attributes" are defined in [ISO/IEEE 11073-104xx]. + +The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT" in this Recommendation are to be interpreted as in [b-ETSI SR 001 262]. + +- SHALL is equivalent to 'must' or 'it is required to'. +- SHALL NOT is equivalent to 'must not' or 'it is not allowed'. +- SHOULD is equivalent to 'it is recommended to'. +- SHOULD NOT is equivalent to 'it is not recommended to'. +- MAY is equivalent to 'is permitted'. +- MAY NOT is equivalent to 'it is not required that'. + +NOTE – The above-mentioned key words are capitalized for illustrative purposes only and they do not appear capitalized within this Recommendation. + +In this document, hexadecimal numbers are denoted either with the prefix "0x" or by "(hex)" after the number; "(dec)" after a number indicates it is expressed in decimal format. + +Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. + +**Table 1 – List of designations associated with the various versions of the CDG** + +| CDG release | Transposed as | Version | Description | Designation | +|------------------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016 plus errata | [ITU-T H.810 (2016)] | 6.1 | Release 2016 plus errata noting all ratified bugs [b-CDG 2016]. | – | +| 2016 | – | 6.0 | Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. | Iris | +| 2015 plus errata | [b-ITU-T H.810 (2015)] | 5.1 | Release 2015 plus errata noting all ratified bugs [b-CDG 2015]. The 2013 edition of ITU-T H.810 is split into eight parts in the ITU-T H.810-series. | – | +| 2015 | – | 5.0 | Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. | Genome | +| 2013 plus errata | [b-ITU-T H.810 (2013)] | 4.1 | Release 2013 plus errata noting all ratified bugs [b-CDG 2013]. | – | +| 2013 | – | 4.0 | Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. | Endorphin | +| 2012 plus errata | – | 3.1 | Release 2012 plus errata noting all ratified bugs [b-CDG 2012]. | – | +| 2012 | – | 3.0 | Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. | Catalyst | +| 2011 plus errata | – | 2.1 | CDG 2011 integrated with identified errata. | – | +| 2011 | – | 2.0 | Release 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities [b-CDG 2011]. | Adrenaline | +| 2010 plus errata | – | 1.6 | CDG 2010 integrated with identified errata. | – | +| 2010 | – | 1.5 | Release 2010 of the CDG with maintenance updates of the CDG Version 1 and additional guidelines that cover new functionalities [b-CDG 2010]. | 1.5 | +| 1.0 | – | 1.0 | First released version of the CDG [b-CDG 1.0]. | – | + +## 6 Test suite structure + +The test purposes (TP) for the Personal Health Devices interface have been divided into the groups and subgroups specified below. Annex A describes the TPs for subgroup 2.4.8 (shown in bold). + +– Group 1: Personal Health Device (PHD) + +- Group 1.1: Transport (TR) + - Subgroup 1.1.1: Design guidelines: Common (DGC) + - Subgroup 1.1.2: USB design guidelines (UDG) + - Subgroup 1.1.3: Bluetooth design guidelines (BDG) + - Subgroup 1.1.4: Pulse oximeter design guidelines (PODG) + - Subgroup 1.1.5: Cardiovascular design guidelines (CVDG) + - Subgroup 1.1.6: Activity hub design guidelines (HUBDG) + - Subgroup 1.1.7: ZigBee design guidelines (ZDG) + - Subgroup 1.1.8: Glucose meter design guidelines (GLDG) + - Subgroup 1.1.9: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 1.1.10: Basic electrocardiograph design guidelines (ECGDG) + - Subgroup 1.1.11: NFC design guidelines (NDG) +- Group 1.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 1.2.1: PHD domain information model (DIM) + - Subgroup 1.2.2: PHD service model (SER) + - Subgroup 1.2.3: PHD communication model (COM) +- Group 1.3: Devices class specializations (CLASS) + - Subgroup 1.3.1: Weighing scales (WEG) + - Subgroup 1.3.2: Glucose meter (GL) + - Subgroup 1.3.3: Pulse oximeter (PO) + - Subgroup 1.3.4: Blood pressure monitor (BPM) + - Subgroup 1.3.5: Thermometer (TH) + - Subgroup 1.3.6: Cardiovascular (CV) + - Subgroup 1.3.7: Strength (ST) + - Subgroup 1.3.8: Activity hub (HUB) + - Subgroup 1.3.9: Adherence monitor (AM) + - Subgroup 1.3.10: Insulin pump (IP) + - Subgroup 1.3.11: Peak flow (PF) + - Subgroup 1.3.12: Body composition analyser (BCA) + - Subgroup 1.3.13: Basic electrocardiograph (ECG) + - Subgroup 1.3.14: International normalized ratio (INR) + - Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 1.3.16: Continuous glucose monitor (CGM) +- Group 1.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 1.4.1: Whitepaper general requirements (GEN) + - Subgroup 1.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 1.4.3: Whitepaper blood pressure requirements (BPM) + +- Subgroup 1.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 1.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 1.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 1.4.7: Whitepaper pulse oximeter requirements (PLX) +- Subgroup 1.4.8: Whitepaper continuous glucose monitoring requirements (CGM) + +### – Group 2: Personal Health Gateway (PHG) + +- Group 2.1: Transport (TR) + - Subgroup 2.1.1: Design guidelines: Common (DGC) + - Subgroup 2.1.2: USB design guidelines (UDG) + - Subgroup 2.1.3: Bluetooth design guidelines (BDG) + - Subgroup 2.1.4: Cardiovascular design guidelines (CVDG) + - Subgroup 2.1.5: Activity hub design guidelines (HUBDG) + - Subgroup 2.1.6: ZigBee design guidelines (ZDG) + - Subgroup 2.1.7: Bluetooth low energy design guidelines (BLEDG) + - Subgroup 2.1.8: NFC design guidelines (NDG) +- Group 2.2: IEEE 20601 Optimized exchange protocol (OXP) + - Subgroup 2.2.1: General (GEN) + - Subgroup 2.2.2: PHD domain information model (DIM) + - Subgroup 2.2.3: PHD service model (SER) + - Subgroup 2.2.4: PHD communication model (COM) +- Group 2.3: Devices class specializations (CLASS) + - Subgroup 2.3.1: Weighing scales (WEG) + - Subgroup 2.3.2: Glucose meter (GL) + - Subgroup 2.3.3: Pulse oximeter (PO) + - Subgroup 2.3.4: Blood pressure monitor (BPM) + - Subgroup 2.3.5: Thermometer (TH) + - Subgroup 2.3.6: Cardiovascular (CV) + - Subgroup 2.3.7: Strength (ST) + - Subgroup 2.3.8: Activity hub (HUB) + - Subgroup 2.3.9: Adherence monitor (AM) + - Subgroup 2.3.10: Insulin pump (IP) + - Subgroup 2.3.11: Peak flow (PF) + - Subgroup 2.3.12: Body composition analyser (BCA) + - Subgroup 2.3.13: Basic electrocardiograph (ECG) + - Subgroup 2.3.14: International normalized ratio (INR) + - Subgroup 2.3.15: Sleep apnoea breathing therapy equipment (SABTE) + - Subgroup 2.3.16: Continuous glucose monitor (CGM) +- Group 2.4: Personal health device transcoding whitepaper (PHDTW) + - Subgroup 2.4.1: Whitepaper general requirements (GEN) + - Subgroup 2.4.2: Whitepaper thermometer requirements (TH) + - Subgroup 2.4.3: Whitepaper blood pressure measurement requirements (BPM) + +- Subgroup 2.4.4: Whitepaper heart rate requirements (HR) +- Subgroup 2.4.5: Whitepaper glucose meter requirements (GL) +- Subgroup 2.4.6: Whitepaper weight scale requirements (WS) +- Subgroup 2.4.7: Whitepaper pulse oximeter requirements (PLX) +- **Subgroup 2.4.8: Whitepaper continuous glucose monitoring requirements (CGM)** + +## 7 Electronic attachment + +The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from . + +In the electronic attachment, letters "C" and "I" in the column labelled "Mandatory" are used to distinguish between "PICS" and "PIXIT" respectively during testing. If the cell is empty, the corresponding PICS is "independent". If the field contains a "C", the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the "SCR\_Expression" field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. + +## Annex A + +### Test purposes + +(This annex forms an integral part of this Recommendation.) + +### A.1 TP definition conventions + +The test purposes (TPs) are defined according to the following rules: + +- **TP Id:** This is a unique identifier (TP///// – ). It is specified according to the naming convention defined below: + - Each test purpose identifier is introduced by the prefix "TP". + - : This is the test tool that will be used in the test case. + - PAN: Personal area network (Bluetooth or USB) + - LAN: Local area network (ZigBee) + - PAN-LAN: Personal area network (Bluetooth or USB) – Local area network (ZigBee) + - LP-PAN: Low power personal area network (Bluetooth low energy) + - TAN: Touch area network (NFC) + - PLT: Personal area network (Bluetooth or USB) – Local area network (ZigBee) – Touch area network (NFC) + - : This is the device under test. + - PHD: Personal Health Device + - PHG: Personal Health Gateway + - : This identifies a group of test cases. + - : This identifies a subgroup of test cases. + - : This identifies the type of testing. + - BV: Valid behaviour test + - BI: Invalid behaviour test + - : This is a sequential number that identifies a test purpose. +- **TP label:** This is the TP's title. +- **Coverage:** This contains the specification reference and clause to be checked by the TP. + - Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. + - Testable item: This contains the testable items to be checked by the TP. +- **Test purpose:** This is a description of the requirements to be tested. +- **Applicability:** This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an "ALL" in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). +- **Other PICS:** This contains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. +- **Initial condition:** This indicates the state to which the DUT needs to be moved at the beginning of TC execution. +- **Test procedure:** This describes the steps to be followed in order to execute the test case. +- **Pass/Fail criteria:** This provides criteria to decide whether the DUT passes or fails the test case. + +### A.2 Subgroup 2.4.8 – Whitepaper Continuous glucose monitoring requirements (CGM) + +| | | | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-000 | | | +| TP label | Whitepaper. Continuous Glucose Monitoring MDS Object - System-Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | CGM Specific MDS 1; M | | +| Test purpose | Check that:
    PHG does not include MDS Object – System-Type attribute in transcoder output. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated Personal Health Device (PHD) are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.
    4. Check in PHG transcoder output the MDS Object – System-Type attribute
    | | | +| Pass/Fail criteria | In Step 4, the MDS Object – System-Type attribute is not present. | | | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    System-Type attribute is not present:

    • Object: MDS Object
    • Attribute-id: MDC_ATTR_SYS_TYPE (2438)
    • Attribute-type: TYPE
    • Attribute-value: <NOT PRESENT>

    b) WAN PCD-01 message

    PCD-01 message does not include segments with System-Type attribute value (67974^MDC_ATTR_SYS_TYPE^MDC)

    | | | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-001 | | | +| TP label | Whitepaper. Continuous Glucose Monitoring MDS Object - Dev-Configuration-Id Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Common MDS 17; M | | +| Test purpose |

    Check that:

    PHG includes MDS Object – Dev-Configuration-Id attribute in transcoder output.

    [AND]

    Dev-Configuration-Id value is set to any value in range of 0x4000 to 0x7FFF (Extended Configuration)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    3. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    4. Check in PHG transcoder output the MDS Object – Dev-Configuration-Id attribute

    | +| Pass/Fail criteria | In Step 4, the MDS Object – Dev-Configuration-Id attribute is present, its value is inside the range 0x4000 - 0x7FFF | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes
    Dev-Configuration-Id attribute is present:

    • Object: MDS Object
    • Attribute-id: MDC_ATTR_DEV_CONFIG_ID (2628)
    • Attribute-type: INT-U16
    • Attribute-value: Any value inside the range 16384 - 32767 (dec) or 0x4000 – 0x7FFF (hex)

    b) WAN PCD-01 message

    According to Continua DG, the Dev-Configuration-Id shall not be transmitted in PCD-01 message, therefore it is not possible to check this attribute.

    | + +| | | | | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-002 | | | | +| TP label | Whitepaper. Continuous Glucose Monitoring MDS Object - System-Type-Spec-List Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Common MDS 15; M | CGM Specific MDS 2; M | | +| Test purpose |

    Check that:

    PHG includes MDS Object – System-Type-Spec-List attribute in transcoder output.

    [AND]

    System-Type-Spec-List is set to (MDC_DEV_SPEC_PROFILE_CGM, Version 1)

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |

    1. The simulated PHD is configured with a Continuous Glucose Monitoring (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).

    2. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    3. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.

    4. Check in PHG transcoder output the MDS Object – System-Type-Spec-List attribute

    | | | | +| Pass/Fail criteria | In Step 4, the MDS Object – System-Type-Spec-List attribute is present, its value is (MDC_DEV_SPEC_PROFILE_CGM, Version 1) | | | | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes
    System-Type-Spec-List attribute is present:

    • Object: MDS Object
    • Attribute-id: MDC_ATTR_SYS_TYPE_SPEC_LIST (2650)
    • Attribute-type: SEQUENCE OF { type (INT-U16), version (INT-U16) }
    | | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-value:

    • type: MDC_DEV_SPEC_PROFILE_CGM, 4106 (dec) or 10 0A (hex)
    • version: 1 (dec) or 00 01 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with System-Type-Spec-List attribute value (check OBX-5):

    OBX ? NM 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a
    528410^MDC_DEV_SPEC_PROFILE_CGM^MDC R

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-003 | | | | +| TP label | Whitepaper. Continuous Glucose Monitoring MDS Object - Reg-Cert-Data-List Attribute | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Common MDS 14; M | Regulatory Conv 1; M | | +| Test purpose |

    Check that:

    PHG transcodes IEEE 11073-20601 Regulatory Certification Data List characteristic into MDS Object – Reg-Cert-Data-List attribute

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).
    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. IEEE 11073-20601 Regulatory Certification Data List (0x2A2A)
        • Format: reg-cert-data-list (opaque structure)
        • Value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 1A 02 02 00 02 80 00 (hex)
          • Element:
            • auth-body-and-struc-type:
              • auth-body: 02 (hex) auth-body-continua(2)
              • auth-body-struc-type: 01 (hex). continua-version-struct(1)
            • auth-body-data:
              • major-IG-version: 08 (hex)
              • minor-IG-version: 00 (hex)
              • certified-devices: 80 1A (hex) BLE Continuous Glucose Monitor
          • Element:
            • auth-body-and-struc-type:
              • auth-body: 02 (hex). auth-body-continua(2)
              • auth-body-struc-type: 02 (hex). continua-reg-struct(2)
            • auth-body-data:
              • regulation-bit-field: 80 00 (hex). Unregulated device
    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with simulated PHD.
    4. When the pairing has been completed (Connection state), force the PHG under test to read IEEE 11073-20601 Regulatory Certification Data List characteristic.
    | | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 5. Check in the PHG transcoder output the MDS Object – Reg-Cert-Data-List attribute | +| Pass/Fail criteria | In Step 5, the MDS Object – Reg-Cert-Data-List attribute is present and its value matches with IEEE 11073-20601 Regulatory Certification Data List characteristic value | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Reg-Cert-Data-List attribute is present:

    • Object: MDS Object
    • Attribute-id: MDC_ATTR_REG_CERT_DATA_LIST (2635)
    • Attribute-type: SEQUENCE OF {{auth-body-and-struc-type, auth-body-data}, {...}}
    • Attribute-value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 1A 02 02 00 02 80 00 (hex) [Note that 0x00 0x02 is the number of elements in the sequence and 0x00 0x12 is the length of the sequence]
      • i. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex) auth-body-continua(2)
          • - auth-body-struc-type: 01 (hex). continua-version-struct(1)
        • • auth-body-data:
          • - major-IG-version: 08 (hex)
          • - minor-IG-version: 00 (hex)
          • - certified-devices: 80 1A (hex). BLE Continuous Glucose Monitor
      • ii. Reg-Cert-Data Element:
        • • auth-body-and-struc-type:
          • - auth-body: 02 (hex). auth-body-continua(2)
          • - auth-body-struc-type: 02 (hex). continua-reg-struct(2)
        • • auth-body-data:
          • - regulation-bit-field: 80 00 (hex). Unregulated device

    b) WAN PCD-01 message

    PCD-01 message includes five segments like these with Reg-Cert-Data-List attribute value (check OBX-5 in five segments):

    OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.a 2^auth-body-continua     R OBX ? ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 1.0.0.a.x 7.0     R OBX ? NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 1.0.0.a.y 32794     R OBX ? CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.b 2^auth-body-continua     R OBX ? CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 1.0.0.b.z 1^unregulated-device(0)     R
    | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-004 | | | +| TP label | Whitepaper. Glucose Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 1; O | | +| Test purpose | Check that:
    PHG does not include Glucose Numeric Object – Handle Attribute in transcoder output. | | | + +| | | +|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [OR]
    If PHG includes Glucose Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0 | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
          • • Value: not relevant
        4. iv. Field: Time Offset
          • • Format: uint16
          • • Value: not relevant
        5. v. Field: Sensor Status Annunciation
          • • This field is not included
        6. vi. Field: CGM Trend Information
          • • This field is not included
        7. vii. Field: CGM Quality
          • • This field is not included
        8. viii. Field: E2E-CRC
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics. Then, the simulated PHD sends the CGM measurement to the PHG under test.
    5. 5. Check in the PHG transcoder output the Glucose Numeric Object – Handle attribute
    6. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    7. 7. Check in the PHG transcoder output the Glucose Numeric Object – Handle attribute
    | +| Pass/Fail criteria | In Step 5 and 7, the Glucose Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0. | +| Notes
    (To assist manual)     | Possible values in typical points of observation after transcoder output are: | + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| testing) | a) IEEE 11073 Objects and Attributes
    Handle attribute is not present, or if it is present then:
    • Object: Glucose Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0
    b) WAN PCD-01 message
    PCD-01 message does not include segments with Handle attribute value | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-005 | | | +| TP label | Whitepaper. Glucose Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 2; M | | +| Test purpose | Check that:
    PHG includes Glucose Numeric Object – Type attribute in transcoder output.
    [AND]
    Type is set to the correct value according to CGM Type field value | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0000 0000 0000 (MSB → LSB). No extra features supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: 0x1 (capillary wholeblood)
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: 8 bit
    • • Value: 0000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
    1. iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: not relevant
    2. iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    3. v. Field: Sensor Status Annunciation
      • • This field is not included
    4. vi. Field: CGM Trend Information
      • • This field is not included
    5. vii. Field: CGM Quality
      • • This field is not included
    6. viii. Field: E2E-CRC
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature characteristic and CGM Session Start Time characteristic.
    3. 5. The simulated PHD sends the Measurement to the PHG under test.
    4. 6. Check in the PHG transcoder output the Glucose Numeric Object – Type attribute
    5. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    6. 8. Check in the PHG transcoder output the Glucose Numeric Object – Type attribute
    7. 9. End current CGM session and start a new one. The simulated PHD will now have CGM Type field of the CGM Feature characteristic set to 0x2 (capillary plasma). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Type attribute as in step 6 and 8.
    8. 10. End current CGM session and start a new one. The simulated PHD will now have CGM Type field of the CGM Feature characteristic set to 0x3 (venous wholeblood). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Type attribute as in step 6 and 8.
    9. 11. End current CGM session and start a new one. The simulated PHD will now have CGM Type field of the CGM Feature characteristic set to 0x4 (venous plasma). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Type attribute as in step 6 and 8.
    10. 12. End current CGM session and start a new one. The simulated PHD will now have CGM Type field of the CGM Feature characteristic set to 0x5 (arterial wholeblood). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Type attribute as in step 6 and 8.
    11. 13. End current CGM session and start a new one. The simulated PHD will now have CGM Type field of the CGM Feature characteristic set to 0x6 (arterial plasma). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Type attribute as in step 6 and 8.
    12. 14. End current CGM session and start a new one. The simulated PHD will now have CGM Type field of the CGM Feature characteristic set to 0x7 (undetermined wholeblood). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Type attribute as in step 6 and 8.
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    15. End current CGM session and start a new one. The simulated PHD will now have CGM Type field of the CGM Feature characteristic set to 0x8 (undetermined plasma). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Type attribute as in step 6 and 8.

    16. End current CGM session and start a new one. The simulated PHD will now have CGM Type field of the CGM Feature characteristic set to 0x9 (interstitial fluid – ISF). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Type attribute as in step 6 and 8.

    17. End current CGM session and start a new one. The simulated PHD will now have CGM Type field of the CGM Feature characteristic set to 0xA (control solution). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Type attribute as in step 6 and 8.

    | +| Pass/Fail criteria |
    • • In Step 6 and 8, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD}
    • • In Step 9, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_CAPILLARY_PLASMA} in both cases.
    • • In Step 10, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_VENOUS_WHOLEBLOOD} in both cases.
    • • In Step 11, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_VENOUS_PLASMA} in both cases.
    • • In Step 12, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD} in both cases.
    • • In Step 13, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_ARTERIAL_PLASMA} in both cases.
    • • In Step 14, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD} in both cases.
    • • In Step 15, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_UNDETERMINED_PLASMA} in both cases.
    • • In Step 16, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_ISF} in both cases.
    • • In Step 17, the Glucose Numeric Object – Type attribute is set to {MDC_PART_SCADA MDC_CONC_GLU_CONTROL} in both cases.
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Glucose Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value (Steps 6 & 8):
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD or 29112 (dec) or 71 B8 (hex)
    • Attribute-value (Step 9):
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_CONC_GLU_CAPILLARY_PLASMA or 29116 (dec) or 71 BC (hex)
    • Attribute-value (Step 10):
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
      • • code: MDC_CONC_GLU_VENOUS_WHOLEBLOOD or 29120 (dec) or 71 C0 (hex)
    • Attribute-value (Step 11):
      • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • code: MDC_CONC_GLU_VENOUS_PLASMA or 29124 (dec) or 71 C4 (hex)

    Attribute-value (Step 12):

    • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
    • • code: MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD or 29128 (dec) or 71 C8 (hex)

    Attribute-value (Step 13):

    • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
    • • code: MDC_CONC_GLU_ARTERIAL_PLASMA or 29132 (dec) or 71 CC (hex)

    Attribute-value (Step 14):

    • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
    • • code: MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD or 29292 (dec) or 72 6C (hex)

    Attribute-value (Step 15):

    • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
    • • code: MDC_CONC_GLU_UNDETERMINED_PLASMA or 29296 (dec) or 72 70 (hex)

    Attribute-value (Step 16):

    • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
    • • code: MDC_CONC_GLU_ISF or 29140 (dec) or 71 D4 (hex)

    Attribute-value (Step 17):

    • • partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)
    • • code: MDC_CONC_GLU_CONTROL or 29136 (dec) or 71 D0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    • • Steps 6 & 8
      OBX n NM 160184^MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD^MDC m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]
    • • Step 9
      OBX n NM 160188^MDC_CONC_GLU_CAPILLARY_PLASMA^MDC m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]
    • • Step 10
      OBX n NM 160192^MDC_CONC_GLU_VENOUS_WHOLEBLOOD^MDC m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]
    • • Step 11
      OBX n NM 160196^MDC_CONC_GLU_VENOUS_PLASMA^MDC m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]
    • • Step 12
      OBX n NM 160200^MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD^MDC m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]
    • • Step 13
      OBX n NM 160204^MDC_CONC_GLU_ARTERIAL_PLASMA^MDC m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]
    • • Step 14
      OBX n NM 160364^MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD^MDC m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]
    • • Step 15
      OBX n NM 160368^MDC_CONC_GLU_UNDETERMINED_PLASMA^MDC
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    m.0.0.x[[value]]264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]

    • Step 16
      OBX[n NM 160212^MDC_CONC_GLU_ISF^MDC m.0.0.x[[value]]264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]
    • Step 17
      OBX[n NM 160208^MDC_CONC_GLU_CONTROL^MDC m.0.0.x[[value]]264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-006 | | | +| TP label | Whitepaper. Glucose Numeric Object – Supplemental-Types Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 3; O | | +| Test purpose |

    Check that:

    PHG may include Glucose Numeric Object – Supplemental-Types attribute in transcoder output.

    [AND]

    If present, Supplemental-Types is set to the correct value according to CGM Sample Location field value

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. CGM Feature (0x2AA8)
        1. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 0000 (MSB → LSB). No extra features supported.
        2. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. Field: CGM Sample Location
          • Format: 4 bit
          • Value: 0x1 (finger)
        4. Field: E2E-CRC
          • Format: uint16
          • Value: not relevant
      2. CGM Measurement (0x2AA7)
        1. Field: Size
          • Format: uint8
        2. Field: Flags
          • Format: 8 bit
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 0000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
    1. iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: not relevant
    2. iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    3. v. Field: Sensor Status Annunciation
      • • This field is not included
    4. vi. Field: CGM Trend Information
      • • This field is not included
    5. vii. Field: CGM Quality
      • • This field is not included
    6. viii. Field: E2E-CRC
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    3. 5. The simulated PHD sends the Measurement to PHG under test.
    4. 6. Check in the PHG transcoder output the Glucose Numeric Object–Supplemental-Types attribute
    5. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    6. 8. Check in the PHG transcoder output the Glucose Numeric Object – Supplemental-Types attribute
    7. 9. End current CGM session and start a new one. The simulated PHD will now have CGM Sample Location field of the CGM Feature characteristic set to 0x2 (alternative site test). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Supplemental-Types attribute as in step 6 and 8.
    8. 10. End current CGM session and start a new one. The simulated PHD will now have CGM Sample Location field of the CGM Feature characteristic set to 0x3 (earlobe). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Supplemental-Types attribute as in step 6 and 8.
    9. 11. End current CGM session and start a new one. The simulated PHD will now have CGM Sample Location field of the CGM Feature characteristic set to 0x4 (control solution). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Supplemental-Types attribute as in step 6 and 8.
    10. 12. End current CGM session and start a new one. The simulated PHD will now have CGM Sample Location field of the CGM Feature characteristic set to 0x5 (subcutaneous tissue). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Supplemental-Types attribute as in step 6 and 8.
    11. 13. End current CGM session and start a new one. The simulated PHD will now have CGM Sample Location field of the CGM Feature characteristic set to 0xF (sample location value not available). Repeat steps 3-8 and check in PHG transcoder output the Glucose Numeric Object-Supplemental-Types attribute as in step 6 and 8.
    | +| Pass/Fail criteria |
    • • In Step 6 and 8, if present, the Glucose Numeric Object – Supplemental-Types attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_FINGER}
    • • In Step 9, if present, the Glucose Numeric Object – Supplemental-Types attribute is set to
    | + +| | | +|----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_AST} in both cases.

    • • In Step 10, if present, the Glucose Numeric Object – Supplemental-Types attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE} in both cases.
    • • In Step 11, if present, the Glucose Numeric Object – Supplemental-Types attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_CTRLSOLUTION} in both cases.
    • • In Step 12, if present, the Glucose Numeric Object – Supplemental-Types attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_SUBCUTANEOUS} in both cases.
    • • In Step 13, if present, the Glucose Numeric Object – Supplemental-Types attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_UNDERTERMINED} in both cases.
    | +|

    Notes
    (To assist manual testing)

    |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    If Supplemental-Types attribute is present:

    • Object: Glucose Numeric Object
    • Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)
    • Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value (Steps 6 & 8):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_FINGER or 29240 (dec) or 72 38 (hex)
    • Attribute-value (Step 9):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_AST or 29244 (dec) or 72 3C (hex)
    • Attribute-value (Step 10):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE or 29248 (dec) or 72 40 (hex)
    • Attribute-value (Step 11):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_CTRLSOLUTION or 29252 (dec) or 72 44 (hex)
    • Attribute-value (Step 12):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_SUBCUTANEOUS or 29241 (dec) or 72 39 (hex)
    • Attribute-value (Step 13):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_UNDERTERMINED or 29237 (dec) or 72 35 (hex)

    b) WAN PCD-01 message

    If Supplemental-Types is present, PCD-01 message includes a facet OBX segment of the CGM measurement OBX segment with Supplemental-Types attribute (check OBX-3 and OBX-5):

    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL ^MDC     R   [date_time]
    • • Steps 6 & 8
    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
    8417848^MDC_CTXT_GLU_SAMPLELOCATION_FINGER^MDC R
    • Step 9
    OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
    8417852^MDC_CTXT_GLU_SAMPLELOCATION_AST^MDC R
    • Step 10
    OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
    8417856^MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE^MDC R
    • Step 11
    OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
    8417860^MDC_CTXT_GLU_SAMPLELOCATION_CTRLSOLUTION^MDC R
    • Step 12
    OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
    8417849^MDC_CTXT_GLU_SAMPLELOCATION_SUBCUTANEOUS^MDC R
    • Step 13
    OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
    8417845^MDC_CTXT_GLU_SAMPLELOCATION_UNDERTERMINED^MDC R | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-007 | | | +| TP label | Whitepaper. Glucose Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 4; M | | +| Test purpose | Check that:
    PHG includes Glucose Numeric Object – Metric-Spec-Small attribute in transcoder output.
    [AND]
    Metric-Spec-Small is set to {0xC042}. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. CGM Measurement (0x2AA7)
        1. Field: Size
          • Format: uint8
        2. Field: Flags
          • Format: 8 bit
          • Value: 0000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. Field: CGM Glucose Concentration (mg/dL)
          • Format: SFLOAT
          • Value: not relevant
    | | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    iv. Field: Time Offset

    • • Format: uint16
    • • Value: not relevant

    v. Field: Sensor Status Annunciation

    • • This field is not included

    vi. Field: CGM Trend Information

    • • This field is not included

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG to read the CGM Feature and CGM Session Start Time characteristics. Then, the simulated PHD sends the Measurement to PHG under test.

    5. Check in PHG transcoder output the Glucose Numeric Object– Metric-Spec-Small attribute

    6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    7. Check in the PHG transcoder output the Glucose Numeric Object – Metric-Spec-Small attribute

    | +| Pass/Fail criteria | In Step 5 and 7, the Glucose Numeric Object – Metric-Spec-Small attribute is present and its value is {0xC042} (mss-avail-intermittent mss-avail-stored-data mss-acc-agent-initiated mss-cat-calculation) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Glucose Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: 0xC042 (hex) or BITS mss-avail-intermittent (0), mss-avail-stored-data (1), mss-acc-agent-initiated(9), mss-cat-calculation(14) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-008 | | | +| TP label | Whitepaper. Glucose Numeric Object – Measurement-Status Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 5; O | | +| Test purpose |

    Check that:

    PHG may include Glucose Numeric Object – Measurement-Status attribute in transcoder output.

    [AND]

    If present and related to the Sensor Status Annunciation field, Measurement-Status is set to the correct value

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 1111 1111 1111 (MSB → LSB). Calibration supported, patient high/low alerts supported, hypo alerts supported, hyper alerts supported, rate of increase/decrease alerts supported, device specific alert supported, sensor malfunction detection supported, sensor temperature high-low detection supported, sensor result high-low detection supported, low battery detection supported, sensor type error detection supported, general device fault supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0100 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: SFLOAT
    • • Value: not relevant

    iv. Field: Time Offset

    • • Format: uint16
    • • Value: not relevant

    v. Field: Sensor Status Annunciation

    • • Format: 8 bit
    • • Value: 0000 1000 (MSB → LSB) (calibration required).

    vi. Field: CGM Trend Information

    • • This field is not included

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the simulated PHG to read the CGM Feature and CGM Session Start Time characteristics. Then, the simulated PHD sends the Measurement to the PHG under test.
    3. 5. Check in the PHG transcoder output the Glucose Numeric Object– Measurement-Status attribute.
    4. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    5. 7. Check in the PHG transcoder output the Glucose Numeric Object – Measurement-Status attribute
    6. 8. The simulated PHD sends a Measurement to PHG under test with Sensor Status Annunciation field set to 0001 0000 (MSB → LSB), sensor temperature too high for valid test/result at time of measurement (bit 12). All remaining fields remain equal to those in step 2. The simulated PHD also deletes all stored records in RACP and stores an identical measurement. Repeat steps 5-7.
    7. 9. The simulated PHD sends a Measurement to PHG under test with Sensor Status Annunciation field set to 0010 0000 (MSB → LSB), sensor temperature too low for valid test/result at time of measurement (bit 13). All remaining fields remain equal to those in step 2. The simulated PHD also deletes all stored records in RACP and stores an identical measurement. Repeat steps 5-7.
    8. 10. The simulated PHD sends a Measurement to PHG under test with Sensor Status Annunciation field set to 0000 0001 (MSB → LSB) and Flags field set to 1000 0000 (MSB → LSB), Sensor result lower than the Patient Low level (bit 16). All remaining fields remain equal to those in step 2. The simulated PHD also deletes all stored records in RACP and stores an identical measurement. Repeat steps 5-7.
    9. 11. The simulated PHD sends a Measurement to PHG under test with Sensor Status Annunciation field set to 0000 0010 (MSB → LSB) and Flags field set to 1000 0000 (MSB → LSB), Sensor result higher than the Patient Low level (bit 17). All remaining fields remain equal to those in step 2. The simulated PHD also deletes all stored records in RACP and stores an identical measurement. Repeat steps 5-7.
    10. 12. The simulated PHD sends a Measurement to PHG under test with Sensor Status Annunciation field set to 0000 0100 (MSB → LSB) and Flags field set to 1000 0000 (MSB → LSB), Sensor result lower than the Hypo level (bit 18). All remaining fields remain equal to those in step 2. The simulated PHD also deletes all stored records in RACP and stores an identical measurement. Repeat steps 5-7.
    11. 13. The simulated PHD sends a Measurement to PHG under test with Sensor Status Annunciation field set to 0000 1000 (MSB → LSB) and Flags field set to 1000 0000 (MSB → LSB), Sensor result higher than the Hyper level (bit 19). All remaining fields remain equal to those in step 2. The simulated PHD also deletes all stored records in RACP and
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    stores an identical measurement. Repeat steps 5-7.

    14. The simulated PHD sends a Measurement to PHG under test with Sensor Status Annunciation field set to 0100 0000 (MSB → LSB) and Flags field set to 1000 0000 (MSB → LSB), sensor result lower than the device can process (bit 22). All remaining fields remain equal to those in step 2. The simulated PHD also deletes all stored records in RACP and stores an identical measurement. Repeat steps 5-7.

    15. The simulated PHD sends a Measurement to PHG under test with Sensor Status Annunciation field set to 1000 0000 (MSB → LSB) and Flags field set to 1000 0000 (MSB → LSB), sensor result higher than the device can process (bit 23). All remaining fields remain equal to those in step 2. The simulated PHD also deletes all stored records in RACP and stores an identical measurement. Repeat steps 5-7.

    | +| Pass/Fail criteria |
    • • In Step 5 and 7 the Glucose Numeric Object – Measurement-Status attribute, if present, is set to “questionable” (bit 1).
    • • In Step 8 the Glucose Numeric Object – Measurement-Status attribute, if present, is set to “invalid” (bit 0).
    • • In Step 9 the Glucose Numeric Object – Measurement-Status, if present, is set to “invalid” (bit 0).
    • • In Step 10 the Glucose Numeric Object – Measurement-Status attribute, if present, is set to “measurement outside threshold boundaries” (bit 14)
    • • In Step 11 the Glucose Numeric Object – Measurement-Status attribute, if present, is set to “measurement outside threshold boundaries” (bit 14)
    • • In Step 12 the Glucose Numeric Object – Measurement-Status attribute, if present, is set to “measurement outside threshold boundaries” (bit 14)
    • • In Step 13 the Glucose Numeric Object – Measurement-Status attribute, if present, is set to “measurement outside threshold boundaries” (bit 14)
    • • In Step 14 the Glucose Numeric Object – Measurement-Status attribute, if present, is set to “invalid” (bit 0).
    • • In Step 15 the Glucose Numeric Object – Measurement-Status attribute, if present, is set to “invalid” (bit 0).
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    If Measurement-Status attribute is present:

    • Object: Glucose Numeric Object
    • Attribute-id: MDC_ATTR_MSMT_STAT (2375)
    • Attribute-type: BITS16
    • Attribute-value (Steps 5 & 7): “questionable” (0x4000)
    • Attribute-value (Step 8): “invalid” (0x8000)
    • Attribute-value (Step 9): “invalid” (0x8000)
    • Attribute-value (Step 10): “measurement outside threshold boundaries” (0x0002)
    • Attribute-value (Step 11): “measurement outside threshold boundaries” (0x0002)
    • Attribute-value (Step 12): “measurement outside threshold boundaries” (0x0002)
    • Attribute-value (Step 13): “measurement outside threshold boundaries” (0x0002)
    • Attribute-value (Step 14): “invalid” (0x8000)
    • Attribute-value (Step 15): “invalid” (0x8000)

    b) WAN PCD-01 message

    If Measurement-Status is present, PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):

    • • Steps 5 & 7
      OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
      ^MDC QUES R [date_time]
    • • Step 8
    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC INV X [date_time]

    • • Step 9

    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC INV X [date_time]

    • • Step 10

    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC ALACT R [date_time]

    • • Step 11

    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC ALACT R [date_time]

    • • Step 12

    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC ALACT R [date_time]

    • • Step 13

    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC ALACT R [date_time]

    • • Step 14

    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC INV X [date_time]

    • • Step 15

    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC INV X [date_time]

    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-009 | | | +| TP label | Whitepaper. Glucose Numeric Object – Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 6; M | | +| Test purpose |

    Check that:

    PHG includes Glucose Numeric Object – Unit-Code attribute in transcoder output.

    [AND]

    Unit-Code attribute value is set to MDC_DIM_MILLI_G_PER_DL

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). CGM Trend information not present, CGM
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.

    • iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: not relevant
    • iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    • v. Field: Sensor Status Annunciation
      • • This field is not included
    • vi. Field: CGM Trend Information
      • • This field is not included
    • vii. Field: CGM Quality
      • • This field is not included
    • viii. Field: E2E-CRC
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG to read the CGM Feature and CGM Session Start Time characteristic. Then, the simulated PHD sends the Measurement to the PHG under test.
    3. 5. Check in the PHG transcoder output the Glucose Numeric Object– Unit-Code attribute.
    4. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP) and the simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    5. 7. Check in the PHG transcoder output the Glucose Numeric Object – Unit-Code attribute
    | +| Pass/Fail criteria | In Step 5 and 7 the Glucose Numeric Object – Unit-Code attribute is present and its value is set to MDC_DIM_MILLI_G_PER_DL | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Glucose Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: OID-Type
    • Attribute-value: MDC_DIM_MILLI_G_PER_DL or 2130 (dec) or 08 52 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[n][NM][GlucoseType][m.0.0.x][value][264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC R [date_time]

    | + +| | | | | +|-----------------|-----------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-010 | | | +| TP label | Whitepaper. Glucose Numeric Object – Base-Offset-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 7; M | BaseOffset 3; M | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    PHG includes Glucose Numeric Object Base-Offset-Time-Stamp attribute in transcoder output.

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation

    | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Session Start Time (0x2AAA)
        1. i. Field: Session Start Time
          • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
          • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
        2. ii. Field: Time Zone
          • • Format: sint8
          • • Value: 4 (UTC+1:00)
        3. iii. Field: DST-Offset
          • • Format: uint8
          • • Value: 4 (Daylight Time (+1h))
        4. iv. Field: E2E-CRC
          • • This field is not included
      2. b. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
          • • Value: not relevant
        4. iv. Field: Time Offset
          • • Format: uint16
          • • Value: 20
        5. v. Field: Sensor Status Annunciation
          • • This field is not included
        6. vi. Field: CGM Trend Information
          • • This field is not included
        7. vii. Field: CGM Quality
    | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • This field is not included
    viii. Field: E2E-CRC
    • • This field is not included
    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Features and CGM Session Start Time characteristics.
    5. The simulated PHD sends the Measurement to the PHG under test.
    6. Check in the PHG transcoder output the Glucose Numeric Object–Base-Offset-Time-Stamp attribute
    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    8. Check in PHG transcoder output the Glucose Numeric Object – Base-Offset-Time-Stamp attribute | +| Pass/Fail criteria | In Step 6 and 8, the Glucose Numeric Object – Base-Offset-Time-Stamp is set to the addition of CGM Session Start Time characteristic's Session Start Time (May 12, 2016, 16:39:27) field plus CGM Measurement characteristic's Time Offset field (20 min). | +| Notes
    (To assist manual testing)     | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Base-Offset-Time-Stamp attribute is present:
    • Object: Glucose Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
    • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
    • Attribute-value: addition of
      • • CGM Session Start Time characteristic Session Start Time field (May 12, 2016, 16:39:27)
      • • CGM Measurement characteristic Time Offset field (20m)
    Note that the same Base-Offset-Time-Stamp can have different representations depending on bo-time-offset value. If it is set to 20 min (CGM Measurement characteristic Time Offset field), then Base-Offset-Time-Stamp value shall be {3672059967, 0, 20}
    b) WAN PCD-01 message
    PCD-01 message includes a segment like this with Base-Offset-Time-Stamp attribute value (check OBX-14):
    OBX n NM [GlucoseType] m.0.0.x [value] 264274^MDC_DIM_MILLI_G_PER_DL
    ^MDC R [value described in a) coded in DTM format] | + +| | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-011_A | | | +| TP label | Whitepaper. Glucose Numeric Object – Basic-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 8; M | | +| Test purpose | Check that:
    PHG includes Glucose Numeric Object Basic-Nu-Observed-Value attribute in transcoder output.
    [AND]
    Basic-Nu-Observed-Value attribute is set to the correct value. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
          • • Value: 160.0
        4. iv. Field: Time Offset
          • • Format: uint16
          • • Value: not relevant
        5. v. Field: Sensor Status Annunciation
          • • This field is not included
        6. vi. Field: CGM Trend Information
          • • This field is not included
        7. vii. Field: CGM Quality
          • • This field is not included
        8. viii. Field: E2E-CRC
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed (Connection state), force the PHG to read the CGM Feature and CGM Session Start Time characteristics. Then, the simulated PHD sends the Measurement to the PHG under test.
    5. 5. Check in the PHG transcoder output the Glucose Numeric Object–Basic-Nu-Observed-Value attribute
    6. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    7. 7. Check in the PHG transcoder output the Glucose Numeric Object – Basic-Nu-Observed-Value attribute
    | +| Pass/Fail criteria | In Step 5 and 7, the Glucose Numeric Object – Basic-Nu-Observed-Value is set to 160 mg/dL | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes
      Basic-Nu-Observed-Value attribute is present:
      • Object: Glucose Numeric Object
      • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-type: SFLOAT

    Attribute-value: 160 (dec) or 00A0 (hex) or 0110 (hex) or F640 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX[n NM [GlucoseType] m.0.0.x 160 264274^MDC_DIM_MILLI_G_PER_DL^MDC
    R [date_time]

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-011_B | | | +| TP label | Whitepaper. Glucose Numeric Object – Basic-Nu-Observed-Value Attribute Special Values | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 9; M | Glucose Numeric 10; M | +| | | Float Type 2; M | Float Type 1; C | +| Test purpose |

    Check that:

    PHG transcodes CGM Glucose Concentration field of CGM Measurement characteristic into Glucose Numeric Object – Basic-Nu-Observed-Value attribute

    [AND]

    PHG assigns the following special values: NaN (0x07FF), NRes (0x0800), +INFINITY (0x07FE) and -INFINITY (0x0802)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 1111 1111 1111 (MSB → LSB). Calibration supported, patient high/low alerts supported, hypo alerts supported, hyper alerts supported, rate of increase/decrease alerts supported, device specific alert supported, sensor malfunction detection supported, sensor temperature high-low detection supported, sensor result high-low detection supported, low battery detection supported, sensor type error detection supported, general device fault supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Measurement (0x2AA7)
    | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. i. Field: Size
      • • Format: uint8
    2. ii. Field: Flags
      • • Format: 8 bit
      • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
    3. iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: 07 FF (hex). Special value: NaN
    4. iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    5. v. Field: Sensor Status Annunciation
      • • Format: 8 bit
      • • Value: 0000 1000 (MSB → LSB) (sensor malfunction).
    6. vi. Field: CGM Trend Information
      • • This field is not included
    7. vii. Field: CGM Quality
      • • This field is not included
    8. viii. Field: E2E-CRC
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), the simulated PHD sends the Measurement to the PHG under test.
    3. 5. Check in the PHG transcoder output the Glucose Numeric Object–Basic-Nu-Observed-Value attribute
    4. 6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    5. 7. Check in the PHG transcoder output the Glucose Numeric Object – Basic-Nu-Observed-Value attribute
    6. 8. The simulated PHD sends a CGM Measurement to PHG under test with the following values. The simulated PHD also deletes all previous stored records in RACP and stores an identical measurement in it.
      1. a. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 08 00(hex). Special value: NRes

    iv. Field: Time Offset

    • • Format: uint16
    • • Value: not relevant

    v. Field: Sensor Status Annunciation

    • • Format: 8 bit
    • • Value: 0000 1000 (MSB → LSB) (sensor malfunction).

    vi. Field: CGM Trend Information

    • • This field is not included

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included

    9. Repeat steps 5-7 to check in transcoder output the Glucose Numeric Object – Basic-Nu-Observed-Value attribute.

    10. The simulated PHD sends a CGM Measurement to PHG under test with the following values. The simulated PHD also deletes all stored records in RACP and stores an identical measurement in it.

    a. CGM Measurement (0x2AA7)

    i. Field: Size

    • • Format: uint8

    ii. Field: Flags

    • • Format: 8 bit
    • • Value: 1000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present.

    iii. Field: CGM Glucose Concentration (mg/dL)

    • • Format: SFLOAT
    • • Value: 08 02(hex). Special value: -INFINITY

    iv. Field: Time Offset

    • • Format: uint16
    • • Value: not relevant

    v. Field: Sensor Status Annunciation

    • • Format: 8 bit
    • • Value: 0100 0000 (MSB → LSB) (sensor result lower than the device can process).

    vi. Field: CGM Trend Information

    • • This field is not included

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included

    11. Repeat steps 5-7 to check in transcoder output the Glucose Numeric Object – Basic-Nu-Observed-Value attribute

    12. The simulated PHD sends a CGM Measurement to PHG under test with the following

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    values. The simulated PHD also deletes all stored records in RACP and stores an identical measurement in it.

    a. CGM Measurement (0x2AA7)

    • i. Field: Size
      • • Format: uint8
    • ii. Field: Flags
      • • Format: 8 bit
      • • Value: 1000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present.
    • iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: 07 FE(hex). Special value: +INFINITY
    • iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    • v. Field: Sensor Status Annunciation
      • • Format: 8 bit
      • • Value: 1000 0000 (MSB → LSB) (sensor result higher than the device can process).
    • vi. Field: CGM Trend Information
      • • This field is not included
    • vii. Field: CGM Quality
      • • This field is not included
    • viii. Field: E2E-CRC
      • • This field is not included

    13. Repeat steps 5-7 to check in transcoder output the Glucose Numeric Object – Basic-Nu-Observed-Value attribute

    | +| Pass/Fail criteria |
    • • In Step 5 and 7, the Glucose Numeric Object – Basic-Nu-Observed-Value is set to 0x07FF
    • • In Step 9, the Glucose Numeric Object – Basic-Nu-Observed-Value is set to 0x0800 for both cases.
    • • In Step 11, the Glucose Numeric Object – Basic-Nu-Observed-Value is set to 0x0802 for both cases.
    • • In Step 13, the Glucose Numeric Object – Basic-Nu-Observed-Value is set to 0x07FE for both cases.
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Glucose Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value (Steps 5 & 7): 0x07FF (hex)
    • Attribute-value (Step 9): 0x0800 (hex)
    • Attribute-value (Step 11): 0x0802 (hex)
    • Attribute-value (Step 13): 0x07FE (hex)

    b) WAN PCD-01 message

    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Steps 5 & 7
      OBX n NM [GlucoseType] m.0.0.x 264274^MDC_DIM_MILLI_G_PER_DL^MDC
      NAN X [date_time]
    • • Step 9
      OBX n NM [GlucoseType] m.0.0.x 264274^MDC_DIM_MILLI_G_PER_DL^MDC
      OTH X [date_time]
    • • Step 11
      OBX n NM [GlucoseType] m.0.0.x 264274^MDC_DIM_MILLI_G_PER_DL^MDC
      NINF X [date_time]
    • • Step 13
      OBX n NM [GlucoseType] m.0.0.x 264274^MDC_DIM_MILLI_G_PER_DL^MDC
      PINF X [date_time]
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-012 | | | +| TP label | Whitepaper. Glucose Numeric Object – Threshold-Notification-Text-String | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Glucose Numeric 11; O | | +| Test purpose | Check that:

    PHG may transcode bits 16 through 19 of the CGM Sensor Status Annunciation field of CGM Measurement characteristic into Glucose Numeric Object – Threshold-Notification-Text-String attribute | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 1111 1111 1111 (MSB → LSB). Calibration supported, patient high/low alerts supported, hypo alerts supported, hyper alerts supported, rate of increase/decrease alerts supported, device specific alert supported, sensor malfunction detection supported, sensor temperature high-low detection supported, sensor result high-low detection supported, low battery detection supported, sensor type error detection supported, general device fault supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
    | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant

    b. CGM Measurement (0x2AA7)

    • i. Field: Size
      • • Format: uint8
    • ii. Field: Flags
      • • Format: 8 bit
      • • Value: 1000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present.
    • iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: not relevant
    • iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    • v. Field: Sensor Status Annunciation
      • • Format: 8 bit
      • • Value: 0000 0001 (MSB → LSB) (sensor result lower than the patient low level).
    • vi. Field: CGM Trend Information
      • • This field is not included
    • vii. Field: CGM Quality
      • • This field is not included
    • viii. Field: E2E-CRC
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), the simulated PHD sends the Measurement to the PHG under test.

    5. Check in the PHG transcoder output the Glucose Numeric Object– Threshold-Notification-Text-String attribute

    6. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    7. Check in the PHG transcoder output the Glucose Numeric Object – Threshold-Notification-Text-String attribute

    8. The simulated PHD sends a CGM Measurement to the PHG under test with the following values. The simulated PHD also deletes all previous stored records in RACP and stores an identical measurement in it.

    a. CGM Measurement (0x2AA7)

    • i. Field: Size
      • • Format: uint8
    • ii. Field: Flags
      • • Format: 8 bit
      • • Value: 1000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present..
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: not relevant
    2. iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    3. v. Field: Sensor Status Annunciation
      • • Format: 8 bit
      • • Value: 0000 0010 (MSB → LSB) (sensor result higher than the patient high level).
    4. vi. Field: CGM Trend Information
      • • This field is not included
    5. vii. Field: CGM Quality
      • • This field is not included
    6. viii. Field: E2E-CRC
      • • This field is not included

    9. Repeat steps 5-7 to check in transcoder output the Glucose Numeric Object – Threshold-Notification-Text-String attribute.

    10. The simulated PHD sends a CGM Measurement to PHG under test with the following values. The simulated PHD also deletes all stored records in RACP and stores an identical measurement in it.

    1. a. CGM Measurement (0x2AA7)
      1. i. Field: Size
        • • Format: uint8
      2. ii. Field: Flags
        • • Format: 8 bit
        • • Value: 1000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present.
      3. iii. Field: CGM Glucose Concentration (mg/dL)
        • • Format: SFLOAT
        • • Value: not relevant
      4. iv. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant
      5. v. Field: Sensor Status Annunciation
        • • Format: 8 bit
        • • Value: 0000 0100 (MSB → LSB) (sensor result lower than the Hypo level).
      6. vi. Field: CGM Trend Information
        • • This field is not included
      7. vii. Field: CGM Quality
        • • This field is not included
      8. viii. Field: E2E-CRC
        • • This field is not included

    11. Repeat steps 5-7 to check in transcoder output the Glucose Numeric Object – Threshold-

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Notification-Text-String attribute

    12. The simulated PHD sends a CGM Measurement to PHG under test with the following values. The simulated PHD also deletes all stored records in RACP and stores an identical measurement in it.

    1. a. CGM Measurement (0x2AA7)
      1. i. Field: Size
        • • Format: uint8
      2. ii. Field: Flags
        • • Format: 8 bit
        • • Value: 1000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present.
      3. iii. Field: CGM Glucose Concentration (mg/dL)
        • • Format: SFLOAT
        • • Value: not relevant
      4. iv. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant
      5. v. Field: Sensor Status Annunciation
        • • Format: 8 bit
        • • Value: 0000 1000 (MSB → LSB) (sensor result higher than the Hyper Level).
      6. vi. Field: CGM Trend Information
        • • This field is not included
      7. vii. Field: CGM Quality
        • • This field is not included
      8. viii. Field: E2E-CRC
        • • This field is not included

    13. Repeat steps 5-7 to check in transcoder output the Glucose Numeric Object – Threshold-Notification-Text-String attribute

    | +| Pass/Fail criteria |
    • • In Step 5 and 7, if present, the Glucose Numeric Object – Threshold-Notification-Text-String is set to an OCTET STRING with a readable description of the threshold notification “sensor result lower than the patient low level”
    • • In Step 9, if present, the Glucose Numeric Object – Threshold-Notification-Text-String is set to an OCTET STRING with a readable description of the threshold notification “sensor result higher than the patient high level” for both cases.
    • • In Step 11, if present, the Glucose Numeric Object – Threshold-Notification-Text-String is set to an OCTET STRING with a readable description of the threshold notification “sensor result lower than the Hypo level” for both cases.
    • • In Step 13, if present,, the Glucose Numeric Object – Threshold-Notification-Text-String is set to an OCTET STRING with a readable description of the threshold notification “sensor result higher than the Hyper level” for both cases.
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    If Threshold-Notification-Text-String attribute is present:

    • Object: Glucose Numeric Object
    • Attribute-id: MDC_ATTR_THRES_NOTIF_TEXT_STRING (2696)
    • Attribute-type: OCTET STRING
    • Attribute-value (Steps 5 & 7): readable description of the threshold notification “sensor
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    result lower than the patient low level”

    • Attribute-value (Step 9): readable description of the threshold notification “sensor result higher than the patient high level”
    • Attribute-value (Step 11): readable description of the threshold notification “sensor result lower than the Hypo level”
    • Attribute-value (Step 13): readable description of the threshold notification “sensor result higher than the Hyper level”

    b) WAN PCD-01 message

    Threshold-Notification-Text-String attribute is not included in PCD-01 message

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-013 | | | +| TP label | Whitepaper. Sensor Calibration Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SensCal Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Sensor Calibration Numeric Object – Handle Attribute in transcoder output.

    [OR]

    If PHG includes Sensor Calibration Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The simulated PHD has a Calibration Data Record stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • Format: uint8
          • Value: 0x06 (Glucose Calibration Value Response)
        2. ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
    | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: SFLOAT
    • Value: not relevant

    iii. Field: Calibration Value – Calibration Time

    • Format: uint16
    • Value: not relevant

    iv. Field: Calibration Value – Calibration Type

    • Format: 4 bit
    • Value: not relevant

    v. Field: Calibration Value – Calibration Sample Location

    • Format: 4 bit
    • Value: not relevant

    vi. Field: Calibration Value - Next Calibration Time

    • Format: uint16
    • Value: not relevant

    vii. Field: Calibration Value – Calibration Data Record Number

    • Format: uint16
    • Value: not relevant

    viii. Field: Calibration Value – Calibration Status

    • Format: 8 bit
    • Value: not relevant

    ix. Field: E2E-CRC

    • This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0xFFFF”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).

    5. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information.

    6. Check in PHG transcoder output the Sensor Calibration Numeric Object – Handle attribute

    | +| Pass/Fail criteria | In Step 6, the Sensor Calibration Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Sensor Calibration Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | +|-----------------|----------------------------------------------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-014 | +| TP label | Whitepaper. Sensor Calibration Numeric Object - Type Attribute | + +| | | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | SensCal Numeric 2; M | | | +| Test purpose | Check that:
    PHG includes Sensor Calibration Numeric Object – Type attribute in transcoder output.
    [AND]
    Type is set to MDC_PART_PHD_DM MDC_CGM_SENSOR_CALIBRATION | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The simulated PHD has a Calibration Data Record stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x06 (Glucose Calibration Value Response)
        2. ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
          1. Format: SFLOAT
          2. Value: not relevant
        3. iii. Field: Calibration Value – Calibration Time
          1. Format: uint16
          2. Value: not relevant
        4. iv. Field: Calibration Value – Calibration Type
          1. Format: 4 bit
          2. Value: not relevant
        5. v. Field: Calibration Value – Calibration Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        6. vi. Field: Calibration Value - Next Calibration Time
    | | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: uint16
    • Value: not relevant

    vii. Field: Calibration Value – Calibration Data Record Number

    • Format: uint16
    • Value: not relevant

    viii. Field: Calibration Value – Calibration Status

    • Format: 8 bit
    • Value: not relevant

    ix. Field: E2E-CRC

    • This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0xFFFF”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).

    5. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information.

    6. Check in PHG transcoder output the Sensor Calibration Numeric Object – Type attribute

    | +| Pass/Fail criteria | In Step 6, the Sensor Calibration Numeric Object – Type attribute is present and set to MDC_PART_PHD_DM MDC_CGM_SENSOR_CALIBRATION | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Sensor Calibration Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CGM_SENSOR_CALIBRATION or 29428 (dec) or 72 F4 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX n NM 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC  m.0.0.x [value] [unit]   R  [date_time]
    | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-015 | | | +| TP label | Whitepaper. Sensor Calibration Numeric Object – Supplemental-Types Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SensCal Numeric 3; O | | +| Test purpose |

    Check that:

    PHG may include Sensor Calibration Numeric Object – Supplemental-Types attribute in transcoder output.

    [AND]

    If present, Supplemental-Types is set to the correct value according to Sample Location Nibble in Calibration Data Record

    | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The simulated PHD has six different Calibration Data Records stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x06 (Glucose Calibration Value Response)
        2. ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
          1. Format: SFLOAT
          2. Value: not relevant
        3. iii. Field: Calibration Value – Calibration Time
          1. Format: uint16
          2. Value: not relevant
        4. iv. Field: Calibration Value – Calibration Type
          1. Format: 4 bit
          2. Value: not relevant
        5. v. Field: Calibration Value – Calibration Sample Location
          1. Format: 4 bit
          2. Value (CDR number 1): 0x1 (finger)
          3. Value (CDR number 2): 0x2 (alternative site test)
          4. Value (CDR number 3): 0x3 (earlobe)
          5. Value (CDR number 4): 0x4 (control solution)
          6. Value (CDR number 5): 0x5 (subcutaneous tissue)
          7. Value (CDR number 6): 0xF (sample location value not available)
        6. vi. Field: Calibration Value - Next Calibration Time
          1. Format: uint16
          2. Value: not relevant
    | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vii. Field: Calibration Value – Calibration Data Record Number

    • Format: uint16
    • Value: 1 to 6 (six Calibration Data Records (CDR) stored)

    viii. Field: Calibration Value – Calibration Status

    • Format: 8 bit
    • Value: not relevant

    ix. Field: E2E-CRC

    • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0001”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).
    3. 5. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information.
    4. 6. Check in PHG transcoder output the Sensor Calibration Numeric Object – Supplemental-Types attribute
    5. 7. Force the PHG to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0002”. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information. Check in PHG transcoder output the Sensor Calibration Numeric Object – Supplemental-Types attribute
    6. 8. Force the PHG to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0003”. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information. Check in PHG transcoder output the Sensor Calibration Numeric Object – Supplemental-Types attribute
    7. 9. Force the PHG to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0004”. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information. Check in PHG transcoder output the Sensor Calibration Numeric Object – Supplemental-Types attribute
    8. 10. Force the PHG to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0005”. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information. Check in PHG transcoder output the Sensor Calibration Numeric Object – Supplemental-Types attribute
    9. 11. Force the PHG to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0006”. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information. Check in PHG transcoder output the Sensor Calibration Numeric Object – Supplemental-Types attribute
    | +| Pass/Fail criteria |
    • • In Step 6, if present, the Sensor Calibration Numeric Object – Supplemental-Types attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_FINGER}
    • • In Step 7, if present, the Sensor Calibration Numeric Object – Supplemental-Types attribute is to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_AST}
    • • In Step 8, if present, the Sensor Calibration Numeric Object – Supplemental-Types attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE}
    • • In Step 9, if present, the Sensor Calibration Numeric Object – Supplemental-Types attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_CTRLSOLUTION}
    • • In Step 10, if present the Sensor Calibration Numeric Object – Supplemental-Types
    | + +| | | +|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_SUBCUTANEOUS}

    • • In Step 11, if present, the Sensor Calibration Numeric Object – Supplemental-Types attribute is set to {MDC_PART_PHD_DM MDC_CTXT_GLU_SAMPLELOCATION_UNDERTERMINED}
    | +|

    Notes
    (To assist manual testing)

    |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    If Supplemental-Types attribute is present:

    • Object: Sensor Calibration Numeric Object
    • Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)
    • Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value (Step 6):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_FINGER or 29240 (dec) or 72 38 (hex)
    • Attribute-value (Step 7):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_AST or 29244 (dec) or 72 3C (hex)
    • Attribute-value (Step 8):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE or 29248 (dec) or 72 40 (hex)
    • Attribute-value (Step 9):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_CTRLSOLUTION or 29252 (dec) or 72 44 (hex)
    • Attribute-value (Step 10):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_SUBCUTANEOUS or 29241 (dec) or 72 39 (hex)
    • Attribute-value (Step 11):
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CTXT_GLU_SAMPLELOCATION_UNDERTERMINED or 29237 (dec) or 72 35 (hex)

    b) WAN PCD-01 message

    If Supplemental-Types is present, PCD-01 message includes a facet OBX segment of the Sensor Calibration OBX segment with Supplemental-Types attribute (check OBX-3 and OBX-5):

    OBX n NM 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC m.0.0.x [value] [unit] R [date_time]

    • • Step 6
      OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y 8417848^MDC_CTXT_GLU_SAMPLELOCATION_FINGER^MDC R
    • • Step 7
      OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y 8417852^MDC_CTXT_GLU_SAMPLELOCATION_AST^MDC R
    • • Step 8
      OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
    | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 8417856^MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE^MDC R
    • • Step 9
      OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
      8417860^MDC_CTXT_GLU_SAMPLELOCATION_CTRL SOLUTION^MDC R
    • • Step 10
      OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
      8417849^MDC_CTXT_GLU_SAMPLELOCATION_SUBCUTANEOUS^MDC R
    • • Step 11
      OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y
      8417845^MDC_CTXT_GLU_SAMPLELOCATION_UNDERTERMINED^MDC R
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-016_A | | | +| TP label | Whitepaper. Sensor Calibration Numeric Object - Metric-Spec-Small Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SensCal Numeric 4; M | SensCal Numeric 6; M | +| Test purpose | Check that:
    PHG includes Sensor Calibration Numeric Object – Metric-Spec-Small attribute in transcoder output.
    [AND]
    Metric-Spec-Small is set to {0x604C} when the calibration is updated manually by the user. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The simulated PHD has a Calibration Data Record stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
          • Value: not relevant
        4. iv. Field: E2E-CRC
          • Format: uint16
          • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • Format: uint8
          • Value: 0x06 (Glucose Calibration Value Response)
        2. ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
    | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: SFLOAT
    • Value: not relevant

    iii. Field: Calibration Value – Calibration Time

    • Format: uint16
    • Value: not relevant

    iv. Field: Calibration Value – Calibration Type

    • Format: 4 bit
    • Value: not relevant

    v. Field: Calibration Value – Calibration Sample Location

    • Format: 4 bit
    • Value: not relevant

    vi. Field: Calibration Value - Next Calibration Time

    • Format: uint16
    • Value: not relevant

    vii. Field: Calibration Value – Calibration Data Record Number

    • Format: uint16
    • Value: not relevant

    viii. Field: Calibration Value – Calibration Status

    • Format: 8 bit
    • Value: not relevant

    ix. Field: E2E-CRC

    • This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to request the last Calibration Data Record stored performing a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0xFFFF”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).

    5. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information, which was manually updated by the user.

    6. Check in PHG transcoder output the Sensor Calibration Numeric Object – Metric-Spec-Small attribute

    | +| Pass/Fail criteria | In Step 6, the Sensor Calibration Numeric Object – Metric-Spec-Small attribute is present and its value is {0x604C} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-manual mss-cat-setting) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Sensor Calibration Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: 0x604C (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-manual(12), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-016_B | | | +| TP label | Whitepaper. Sensor Calibration Numeric Object - Metric-Spec-Small Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SensCal Numeric 4; M | SensCal Numeric 5; M | +| Test purpose |

    Check that:

    PHG includes Sensor Calibration Numeric Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x6044} when the Glucose Calibration procedure has been executed.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x06 (Glucose Calibration Value Response)
        2. ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
          1. Format: SFLOAT
          2. Value: not relevant
        3. iii. Field: Calibration Value – Calibration Time
          1. Format: uint16
          2. Value: not relevant
        4. iv. Field: Calibration Value – Calibration Type
          1. Format: 4 bit
          2. Value: not relevant
    | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    v. Field: Calibration Value – Calibration Sample Location

    Format: 4 bit

    Value: not relevant

    vi. Field: Calibration Value - Next Calibration Time

    Format: uint16

    Value: not relevant

    vii. Field: Calibration Value – Calibration Data Record Number

    Format: uint16

    Value: not relevant

    viii. Field: Calibration Value – Calibration Status

    Format: 8 bit

    Value: not relevant

    ix. Field: E2E-CRC

    This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.

    5. Force the PHG to calibrate the CGM Sensor, writing a “Set Glucose Calibration Value” Op Code (0x04) and a Calibration Data Record operand with valid values. The simulated PHD will respond with an indication including a Response Op Code value of “Success”.

    6. Then request the last Calibration Data Record stored performing a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0xFFFF”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).

    7. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the previously set calibration information.

    8. Check in the PHG transcoder output the Sensor Calibration Numeric Object – Metric-Spec-Small

    | +| Pass/Fail criteria | In Step 6, the Sensor Calibration Numeric Object – Metric-Spec-Small attribute is present and its value is {0x6044} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-setting) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    Object: Sensor Calibration Numeric Object

    Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)

    Attribute-type: BITS-16

    Attribute-value: 0x6044 (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-017 | | | +| TP label | Whitepaper. Sensor Calibration Numeric Object – Measurement-Status Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SensCal Numeric 7; O | SensCal Numeric 8; M | +| Test purpose |

    Check that:

    PHG may include Sensor Calibration Numeric Object – Measurement-Status attribute in transcoder output.

    [AND]

    If present and related to the Sensor Status Annunciation field, Measurement-Status is set to the correct value

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The simulated PHD has four different Calibration Data Records stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x06 (Glucose Calibration Value Response)
        2. ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
          1. Format: SFLOAT
          2. Value: not relevant
        3. iii. Field: Calibration Value – Calibration Time
          1. Format: uint16
          2. Value: not relevant
        4. iv. Field: Calibration Value – Calibration Type
          1. Format: 4 bit
          2. Value: not relevant
        5. v. Field: Calibration Value – Calibration Sample Location
    | | | + +| | | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: 4 bit
    • Value: not relevant

    vi. Field: Calibration Value - Next Calibration Time

    • Format: uint16
    • Value: not relevant

    vii. Field: Calibration Value – Calibration Data Record Number

    • Format: uint16
    • Value: 1 to 4 (four Calibration Data Records (CDR) stored)

    viii. Field: Calibration Value – Calibration Status

    • Format: 8 bit
    • Value (CDR number 1): 0000 0001 (calibration data rejected)
    • Value (CDR number 2): 0000 0010 (calibration data out-of-range)
    • Value (CDR number 3): 0000 0100 (calibration process pending)
    • Value (CDR number 4): 0000 0000

    ix. Field: E2E-CRC

    • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0001”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).
    3. 5. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information.
    4. 6. Check in PHG transcoder output the Sensor Calibration Numeric Object – Measurement-Status attribute
    5. 7. Force the PHG to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0002”. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information. Check in PHG transcoder output the Sensor Calibration Numeric Object – Measurement-Status attribute
    6. 8. Force the PHG to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0003”. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information. Check in PHG transcoder output the Sensor Calibration Numeric Object – Measurement-Status attribute
    7. 9. Force the PHG to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0x0004”. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information. Check in PHG transcoder output the Sensor Calibration Numeric Object – Measurement-Status attribute
    | +| Pass/Fail criteria |
    • • In Step 6 the Sensor Calibration Numeric Object – Measurement-Status attribute, if present, is set to “invalid” (bit 0).
    • • In Step 7 the Sensor Calibration Numeric Object – Measurement-Status attribute, if present, is set to “invalid” (bit 0).
    • • In Step 8 the Sensor Calibration Numeric Object – Measurement-Status, if present, is set to “calibration-ongoing” (bit 3).
    • • In Step 9 the Sensor Calibration Numeric Object – Measurement-Status attribute, if present, is set to “validated-data” (bit 8)
    | +| Notes
    (To assist manual)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    | + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| testing) |

    If Measurement-Status attribute is present:

    • Object: Sensor Calibration Numeric Object
    • Attribute-id: MDC_ATTR_MSMT_STAT (2375)
    • Attribute-type: BITS16
    • Attribute-value (Step 6): "invalid" (0x8000)
    • Attribute-value (Step 7): "invalid" (0x8000)
    • Attribute-value (Step 8): "calibration-ongoing" (0x1000)
    • Attribute-value (Step 9): "validated-data" (0x0080)

    b) WAN PCD-01 message

    If Measurement-Status is present, PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):

    • • Step 6
      OBX n NM 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC
      m.0.0.x [value] [unit] INV X [date_time]
    • • Step 7
      OBX n NM 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC
      m.0.0.x [value] [unit] INV X [date_time]
    • • Step 8
      OBX n NM 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC
      m.0.0.x [value] [unit] CAL R [date_time]
    • • Step 9
      OBX n NM 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC
      m.0.0.x [value] [unit] R [date_time]
    | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-018 | | | +| TP label | Whitepaper. Sensor Calibration Numeric Object – Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SensCal Numeric 10; M | | +| Test purpose | Check that:
    PHG includes Sensor Calibration Numeric Object – Unit-Code attribute in transcoder output.
    [AND]
    Unit-Code attribute value is set to MDC_DIM_MILLI_G_PER_DL | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The simulated PHD has a Calibration Data Record stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      • a. CGM Feature (0x2AA8)
        • i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
        • ii. Field: CGM Type
          • Format: 4 bit
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
      • Value: not relevant
    • iii. Field: CGM Sample Location
      • Format: 4 bit
      • Value: not relevant
    • iv. Field: E2E-CRC
      • Format: uint16
      • Value: not relevant
    • b. CGM Specific Ops Control Point (0x2AAC)
      • i. Field: Op Code
        • Format: uint8
        • Value: 0x06 (Glucose Calibration Value Response)
      • ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
        • Format: SFLOAT
        • Value: not relevant
      • iii. Field: Calibration Value – Calibration Time
        • Format: uint16
        • Value: not relevant
      • iv. Field: Calibration Value – Calibration Type
        • Format: 4 bit
        • Value: not relevant
      • v. Field: Calibration Value – Calibration Sample Location
        • Format: 4 bit
        • Value: not relevant
      • vi. Field: Calibration Value - Next Calibration Time
        • Format: uint16
        • Value: not relevant
      • vii. Field: Calibration Value – Calibration Data Record Number
        • Format: uint16
        • Value: not relevant
      • viii. Field: Calibration Value – Calibration Status
        • Format: 8 bit
        • Value: not relevant
      • ix. Field: E2E-CRC
        • This field is not present
    • 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    • 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0xFFFF”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).
    • 5. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information.
    • 6. Check in PHG transcoder output the Sensor Calibration Numeric Object – Unit-Code attribute
    | +| Pass/Fail criteria | In Step 6, the Sensor Calibration Numeric Object – Unit-Code attribute is present and set to | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_DIM_MILLI_G_PER_DL | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Sensor Calibration Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: OID-Type
    • Attribute-value: MDC_DIM_MILLI_G_PER_DL or 2130 (dec) or 08 52 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX n NM 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC m.0.0.x[[value]]
    264274^MDC_DIM_MILLI_G_PER_DL^MDC R [date_time]

    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-019 | | | +| TP label | Whitepaper. Sensor Calibration Numeric Object – Base-Offset-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SensCal Numeric 11; M | BaseOffset 3; M | +| Test purpose |

    Check that:

    PHG includes Glucose Numeric Object Base-Offset-Time-Stamp attribute in transcoder output.

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The simulated PHD has a Calibration Data Record stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Session Start Time (0x2AAA)
        1. i. Field: Session Start Time
          • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
          • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
        2. ii. Field: Time Zone
          • Format: sint8
          • Value: 4 (UTC+1:00)
        3. iii. Field: DST-Offset
          • Format: uint8
          • Value: 4 (Daylight Time (+1h))
        4. iv. Field: E2E-CRC
          • This field is not included
      2. b. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
        • Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
      • ii. Field: CGM Type
        • Format: 4 bit
        • Value: not relevant
      • iii. Field: CGM Sample Location
        • Format: 4 bit
        • Value: not relevant
      • iv. Field: E2E-CRC
        • Format: uint16
        • Value: not relevant
    • c. CGM Specific Ops Control Point (0x2AAC)
      • i. Field: Op Code
        • Format: uint8
        • Value: 0x06 (Glucose Calibration Value Response)
      • ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
        • Format: SFLOAT
        • Value: not relevant
      • iii. Field: Calibration Value – Calibration Time
        • Format: uint16 (min)
        • Value: 20
      • iv. Field: Calibration Value – Calibration Type
        • Format: 4 bit
        • Value: not relevant
      • v. Field: Calibration Value – Calibration Sample Location
        • Format: 4 bit
        • Value: not relevant
      • vi. Field: Calibration Value - Next Calibration Time
        • Format: uint16
        • Value: not relevant
      • vii. Field: Calibration Value – Calibration Data Record Number
        • Format: uint16
        • Value: not relevant
      • viii. Field: Calibration Value – Calibration Status
        • Format: 8 bit
        • Value: not relevant
      • ix. Field: E2E-CRC
        • This field is not present
    • 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    • 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0xFFFF”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).
    • 5. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    calibration information.

    6. Check in PHG transcoder output the Sensor Calibration Numeric Object – Base-Offset-Time-Stamp attribute

    | +| Pass/Fail criteria | In Step 6 and 8, the Sensor Calibration Numeric Object – Base-Offset-Time-Stamp is set to the addition of CGM Session Start Time characteristic's Session Start Time (May 12, 2016, 16:39:27) field plus the Calibration Time field of the obtained Calibration Data Record (20 min). | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Base-Offset-Time-Stamp attribute is present:

    • Object: Sensor Calibration Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
    • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
    • Attribute-value: addition of
      • • CGM Session Start Time characteristic Session Start Time field (May 12, 2016, 16:39:27)
      • • CGM Special Ops Control Point characteristic Calibration Time field (20m)

    Note that the same Base-Offset-Time-Stamp can have different representations depending on bo-time-offset value. If it is set to 20 min (CGM Measurement characteristic's Time Offset field), then Base-Offset-Time-Stamp value shall be {3672059967, 0, 20}

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Base-Offset-Time-Stamp attribute value (check OBX-14):

    OBX n NM 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC m.0.0.x[[value]] 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R    [value described in a) coded in DTM format]
    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-020 | | | +| TP label | Whitepaper. Sensor Calibration Numeric Object – Basic-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SensCal Numeric 12; M | | +| Test purpose |

    Check that:

    PHG includes Sensor Calibration Numeric Object Basic-Nu-Observed-Value attribute in transcoder output.

    [AND]

    Basic-Nu-Observed-Value attribute is set to the correct value.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The simulated PHD has a Calibration Data Record stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
      • ii. Field: CGM Type
        • Format: 4 bit
        • Value: not relevant
      • iii. Field: CGM Sample Location
        • Format: 4 bit
        • Value: not relevant
      • iv. Field: E2E-CRC
        • Format: uint16
        • Value: not relevant
    • b. CGM Specific Ops Control Point (0x2AAC)
      • i. Field: Op Code
        • Format: uint8
        • Value: 0x06 (Glucose Calibration Value Response)
      • ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
        • Format: SFLOAT (mg/dL)
        • Value: 115.3
      • iii. Field: Calibration Value – Calibration Time
        • Format: uint16
        • Value: not relevant
      • iv. Field: Calibration Value – Calibration Type
        • Format: 4 bit
        • Value: not relevant
      • v. Field: Calibration Value – Calibration Sample Location
        • Format: 4 bit
        • Value: not relevant
      • vi. Field: Calibration Value - Next Calibration Time
        • Format: uint16
        • Value: not relevant
      • vii. Field: Calibration Value – Calibration Data Record Number
        • Format: uint16
        • Value: not relevant
      • viii. Field: Calibration Value – Calibration Status
        • Format: 8 bit
        • Value: not relevant
      • ix. Field: E2E-CRC
        • This field is not present
    • 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    • 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0xFFFF”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).
    • 5. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information.
    • 6. Check in PHG transcoder output the Sensor Calibration Numeric Object – Basic-Nu-
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Observed-Value attribute | +| Pass/Fail criteria | In Step 6, the Sensor Calibration Numeric Object – Unit-Code attribute is present and set to MDC_DIM_MILLI_G_PER_DL | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Sensor Calibration Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 115.3 (dec) or F481 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX n NM 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC m.0.0.x 15.3 264274^MDC_DIM_MILLI_G_PER_DL^MDC R date_time

    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-021 | | | +| TP label | Whitepaper. Sensor Run-time Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SRT Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Sensor Run-time Numeric Object – Handle Attribute in transcoder output.

    [OR]

    If PHG includes Sensor Run-time Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Session Start Time (0x2AAA)
        1. i. Field: Session Start Time
          • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
          • • Value: not relevant
        2. ii. Field: Time Zone
          • • Format: sint8
          • • Value: not relevant
        3. iii. Field: DST-Offset
          • • Format: uint8
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • This field is not included
    | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b. CGM Session Run Time (0x2AAB)

    • i. Field: Session Run Time
      • • Format: uint16
      • • Value: not relevant
    • ii. Field: E2E-CRC
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature, CGM Session Start Time and CGM Session Run Time characteristics.

    5. Check in the PHG transcoder output the Sensor Run-time Numeric Object – Handle attribute

    | +| Pass/Fail criteria | In Step 5, the Sensor Run-time Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Sensor Run-time Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-022 | | | +| TP label | Whitepaper. Sensor Run-time Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SRT Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Sensor Run-time Numeric Object – Type attribute in transcoder output.

    [AND]

    Type is set to MDC_PART_PHD_DM MDC_CGM_SENSOR_RUN_TIME

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).

    2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:

    • a. CGM Session Start Time (0x2AAA)
      • i. Field: Session Start Time
        • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
        • • Value: not relevant
      • ii. Field: Time Zone
        • • Format: sint8
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant

    iii. Field: DST-Offset

    • • Format: uint8
    • • Value: not relevant

    iv. Field: E2E-CRC

    • • This field is not included

    b. CGM Session Run Time (0x2AAB)

    i. Field: Session Run Time

    • • Format: uint16
    • • Value: not relevant

    ii. Field: E2E-CRC

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature, CGM Session Start Time and CGM Session Run Time characteristics.

    5. Check in the PHG transcoder output the Sensor Run-time Numeric Object – Type attribute

    | +| Pass/Fail criteria | In Step 5, the Sensor Run-time Numeric Object – Type attribute is present and its value is MDC_PART_PHD_DM MDC_CGM_SENSOR_RUN_TIME | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is not present, or if it is present then:

    • Object: Sensor Run-time Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CGM_SENSOR_RUN_TIME or 29432 (dec) or 72 F8 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX[n NM 8418040^MDC_CGM_SENSOR_RUN_TIME^MDC m.0.0.x[[value]]
    264384^MDC_DIM_HR^MDC R [date_time]

    | + +| | | | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-023 | | | +| TP label | Whitepaper. Sensor Run-time Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SRT Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Sensor Run-time Numeric Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x7046}.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Session Start Time (0x2AAA)
        1. i. Field: Session Start Time
          • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
          • • Value: not relevant
        2. ii. Field: Time Zone
          • • Format: sint8
          • • Value: not relevant
        3. iii. Field: DST-Offset
          • • Format: uint8
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • This field is not included
      2. b. CGM Session Run Time (0x2AAB)
        1. i. Field: Session Run Time
          • • Format: uint16
          • • Value: not relevant
        2. ii. Field: E2E-CRC
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature, CGM Session Start Time and CGM Session Run Time characteristics.
    5. 5. Check in PHG transcoder output the Sensor Run-time Numeric Object – Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 5 the Sensor Run-time Numeric Object – Metric-Spec-Small attribute is present and its value is {0x7046} (mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-calculation mss-avail-stored-data mss-cat-setting) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes
      Metric-Spec-Small attribute is present:
      • Object: Sensor Run-time Numeric Object
      • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
      • Attribute-type: BITS-16
      • Attribute-value: 0x7046 (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic (2), mss-msmt-aperiodic (3), mss-acc-agent-initiated(9), mss-cat-setting(13), mss-cat-calculation(14) set to TRUE and remaining BITS set to FALSE
    2. b) WAN PCD-01 message
      PCD-01 message does not include segments with Metric-Spec-Small attribute value
    | + +| | | | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-024 | | | +| TP label | Whitepaper. Sensor Run-time Numeric Object – Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SRT Numeric 4; M | | +| Test purpose | Check that:
    PHG includes Sensor Run-time Numeric Object – Unit-Code attribute in transcoder output.
    [AND]
    Unit-Code attribute value is set to MDC_DIM_HR | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Session Start Time (0x2AAA)
        1. i. Field: Session Start Time
          • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
          • • Value: not relevant
        2. ii. Field: Time Zone
          • • Format: sint8
          • • Value: not relevant
        3. iii. Field: DST-Offset
          • • Format: uint8
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • This field is not included
      2. b. CGM Session Run Time (0x2AAB)
        1. i. Field: Session Run Time
          • • Format: uint16
          • • Value: not relevant
        2. ii. Field: E2E-CRC
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature, CGM Session Start Time and CGM Session Run Time characteristics.
    5. 5. Check in PHG transcoder output the Sensor Run-time Numeric Object – Unit-Code attribute
    | | | +| Pass/Fail criteria | In Step 5 the Sensor Run-time Numeric Object – Unit-Code attribute is present and its value is set to MDC_DIM_HR | | | +| Notes
    (To assist manual testing)     | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Unit-Code attribute is present:
    Object: Sensor Run-time Numeric Object | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: OID-Type
    • Attribute-value: MDC_DIM_HR or 2240 (dec) or 08 C0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[n NM 8418040^MDC_CGM_SENSOR_RUN_TIME^MDC m.0.0.x[value]] 264384^MDC_DIM_HR^MDC    R  [date_time]
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-025 | | | +| TP label | Whitepaper. Sensor Run-time Numeric Object – Base-Offset-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SRT Numeric 5; M | BaseOffset 2; M | +| Test purpose |

    Check that:

    PHG includes Sensor Run-time Numeric Object Base-Offset-Time-Stamp attribute in transcoder output.

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Session Start Time (0x2AAA)
        1. i. Field: Session Start Time
          • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
          • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
        2. ii. Field: Time Zone
          • • Format: sint8
          • • Value: 4 (UTC+1:00)
        3. iii. Field: DST-Offset
          • • Format: uint8
          • • Value: 4 (Daylight Time (+1h))
        4. iv. Field: E2E-CRC
          • • This field is not included
      2. b. CGM Session Run Time (0x2AAB)
        1. i. Field: Session Run Time
          • • Format: uint16
          • • Value: not relevant
        2. ii. Field: E2E-CRC
          • • This field is not included
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    1. 4. When the pairing has been completed, force the PHG to read CGM Feature, CGM Session Start Time and CGM Session Run Time characteristics.
    2. 5. Check in PHG transcoder output the Sensor Run-time Numeric Object – Base-Offset-Time-Stamp attribute
    | +| Pass/Fail criteria | In Step 5, the Sensor Run-time Numeric Object – Base-Offset-Time-Stamp is set to the CGM Session Start Time characteristic's Session Start Time (May 12, 2016, 16:39:27) field. | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes

      Base-Offset-Time-Stamp attribute is present:

      • Object: Sensor Run-time Numeric Object
      • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
      • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
      • Attribute-value:
        • • CGM Session Start Time characteristic Session Start Time field (May 12, 2016, 16:39:27)

      Note that the same Base-Offset-Time-Stamp can have different representations depending on bo-time-offset value. If it is set to 0 min then Base-Offset-Time-Stamp value shall be {3672059967, 0, 0}

    2. b) WAN PCD-01 message

      PCD-01 message includes a segment like this with Base-Offset-Time-Stamp attribute value (check OBX-14):

      OBX n NM 8418040^MDC_CGM_SENSOR_RUN_TIME^MDC m.0.0.x[[value]] 264384^MDC_DIM_HR^MDC    R   [value described in a) coded in DTM format]
    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-026 | | | +| TP label | Whitepaper. Sensor Run-time Numeric Object – Simple-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | SRT Numeric 6; M | | +| Test purpose |

    Check that:

    PHG includes Sensor Run-time Numeric Object Simple-Nu-Observed-Value attribute in transcoder output.

    [AND]

    Simple-Nu-Observed-Value attribute is set to the correct value.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Session Start Time (0x2AAA)
        1. i. Field: Session Start Time
          • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
          • • Value: not relevant
        2. ii. Field: Time Zone
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: sint8
    • • Value: not relevant

    iii. Field: DST-Offset

    • • Format: uint8
    • • Value: not relevant

    iv. Field: E2E-CRC

    • • This field is not included

    b. CGM Session Run Time (0x2AAB)

    i. Field: Session Run Time

    • • Format: uint16 (h)
    • • Value: 168

    ii. Field: E2E-CRC

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature, CGM Session Start Time and CGM Session Run Time characteristics.

    5. Check in PHG transcoder output the Sensor Run-time Numeric Object – Simple-Nu-Observed-Value attribute

    | +| Pass/Fail criteria | In Step 5 the Sensor Run-time Numeric Object – Simple-Nu-Observed-Value is set to 0x000000A8 (uint16 value converted to FLOAT-Type with an exponent of 0). | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Simple-Nu-Observed-Value attribute is present:

    • Object: Sensor Run-time Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)
    • Attribute-type: FLOAT
    • Attribute-value: 168 (dec) or 000000A8 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Simple-Nu-Observed-Value attribute value (check OBX-5):

    OBX[n NM 8418040^MDC_CGM_SENSOR_RUN_TIME^MDC m.0.0.x 168 264384^MDC_DIM_HR^MDC R [date_time]

    | + +| | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-027 | | | +| TP label | Whitepaper. Glucose Sampling Interval Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GSI Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include .Glucose Sampling Interval Numeric Object – Handle Attribute in transcoder output.

    [OR]

    If PHG includes .Glucose Sampling Interval Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has a manually entered communication interval value stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • • Format: uint8
          • • Value: 0x03
        2. ii. Field: Operand
          • • Format: uint8 (min)
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to perform a CGM Communication Interval procedure using Op Code "Get CGM Communication Interval" (0x02) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code field).
    5. 5. The simulated PHD will respond with an indication including a "Communication Interval Response" Op Code (0x03) and an UINT8 containing the communication interval in minutes.
    6. 6. Check in PHG transcoder output the Glucose Sampling Interval Numeric Object – Handle attribute
    | +| Pass/Fail criteria | In Step 6, the Glucose Sampling Interval Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes

      Handle attribute is not present, or if it is present then:

      • Object: Glucose Sampling Interval Numeric Object
      • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
      • Attribute-type: INT-U16
      • Attribute-value: Any value different than 0
    2. b) WAN PCD-01 message

      PCD-01 message does not include segments with Handle attribute value

    | + +| | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-028 | | | +| TP label | Whitepaper. Glucose Sampling Interval Numeric Object – Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GSI Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Glucose Sampling Interval Numeric Object – Type Attribute in transcoder output.

    [OR]

    Type is set to MDC_PART_PHD_DM MDC_CGM_SENSOR_SAMPLE_INTERVAL

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has a manually entered communication interval value stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • • Format: uint8
          • • Value: 0x03
        2. ii. Field: Operand
          • • Format: uint8 (min)
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to perform a CGM Communication Interval procedure using Op Code “Get CGM Communication Interval” (0x02) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code field).
    5. 5. The simulated PHD will respond with an indication including a “Communication Interval Response” Op Code (0x03) and an UINT8 containing the communication interval in minutes.
    6. 6. Check in PHG transcoder output the Glucose Sampling Interval Numeric Object – Type attribute
    | +| Pass/Fail criteria | In Step 6, the Glucose Sampling Interval Numeric Object – Type attribute is present and set to MDC_PART_PHD_DM MDC_CGM_SENSOR_SAMPLE_INTERVAL | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is not present, or if it is present then:

    • Object: Glucose Sampling Interval Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CGM_SENSOR_SAMPLE_INTERVAL or 29436 (dec) or 72 FC (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX[n NM 8418044^MDC_CGM_SENSOR_SAMPLE_INTERVAL^MDC  m.0.0.x [value] 264352^MDC_DIM_MIN^MDC     R  [date_time]
    | + +| | | | | +|---------------------|--------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-029_A | | | +| TP label | Whitepaper. Glucose Sampling Interval Numeric Object - Metric-Spec-Small Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GSI Numeric 3; M | GSI Numeric 5; M | +| Test purpose | Check that: | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PHG includes Glucose Sampling Interval Numeric Object – Metric-Spec-Small attribute in transcoder output.
    [AND]
    Metric-Spec-Small is set to {0x604C} when the communication interval was updated manually by the user | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has a manually entered communication interval value stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • • Format: uint8
          • • Value: 0x03
        2. ii. Field: Operand
          • • Format: uint8 (min)
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to perform a CGM Communication Interval procedure using Op Code “Get CGM Communication Interval” (0x02) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code field).
    5. 5. The simulated PHD will respond with an indication including a “Communication Interval Response” Op Code (0x03) and an UINT8 containing the communication interval in minutes.
    6. 6. Check in PHG transcoder output the Glucose Sampling Interval Numeric Object – Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 6, the Glucose Sampling Interval Numeric Object – Metric-Spec-Small attribute is present and its value is {0x604C} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-manual mss-cat-setting) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Glucose Sampling Interval Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: 60 4C (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-manual(12), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | +|-----------------|--------------------------------------------------------------------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-029_B | +| TP label | Whitepaper. Glucose Sampling Interval Numeric Object - Metric-Spec-Small Attribute 2 | + +| | | | | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|--| +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | GSI Numeric 3; M | GSI Numeric 4; M | | +| Test purpose |

    Check that:

    PHG includes Glucose Sampling Interval Numeric Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x6044} when the CGM Communication Interval procedure has been executed

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_044 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • • Format: uint8
          • • Value: 0x03
        2. ii. Field: Operand
          • • Format: uint8 (min)
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to set the communication interval by performing a CGM Communication Interval procedure using Op Code “Set CGM Communication Interval” (0x01) followed by a valid UINT8 value in minutes (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Operand fields, respectively). The simulated PHD will respond with an indication including a Response Op Code value of “Success”.
    5. 5. Then force the PHG to perform a CGM Communication Interval procedure using Op Code “Get CGM Communication Interval” (0x02) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code field).
    6. 6. The simulated PHD will respond with an indication including a “Communication Interval Response” Op Code (0x03) and an UINT8 containing the entered communication interval in minutes.
    7. 7. Check in the PHG transcoder output the Glucose Sampling Interval Numeric Object – Metric-Spec-Small attribute
    | | | | +| Pass/Fail criteria | In Step 7, the Sensor Calibration Numeric Object – Metric-Spec-Small attribute is present and its value is {0x6044} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-setting) | | | | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Glucose Sampling Interval Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    | | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-value: 60 44 (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-030 | | | +| TP label | Whitepaper. Glucose Sampling Interval Numeric Object – Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GSI Numeric 6; M | | +| Test purpose |

    Check that:

    PHG includes Glucose Sampling Interval Numeric – Unit-Code attribute in transcoder output.

    [AND]

    Unit-Code attribute value is set to MDC_DIM_MIN

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has a manually entered communication interval value stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • • Format: uint8
          • • Value: 0x03
        2. ii. Field: Operand
          • • Format: uint8 (min)
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to perform a CGM Communication Interval procedure using Op Code “Get CGM Communication Interval” (0x02) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code field).
    5. 5. The simulated PHD will respond with an indication including a “Communication Interval Response” Op Code (0x03) and an UINT8 containing the communication interval in minutes.
    6. 6. Check in the PHG transcoder output the Glucose Sampling Interval Numeric Object – Unit-Code attribute
    | | | +| Pass/Fail criteria | In Step 6 the Glucose Sampling Interval Numeric Object – Unit-Code attribute is present and its value is set to MDC_DIM_MIN | | | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    Object: Glucose Sampling Interval Numeric Object

    Attribute-id: MDC_ATTR_UNIT_CODE (2454)

    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-type: OID-Type

    Attribute-value: MDC_DIM_MIN or 2208 (dec) or 08 A0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX n NM 8418044^MDC_CGM_SENSOR_SAMPLE_INTERVAL^MDC m.0.0.x [value] 264352^MDC_DIM_MIN^MDC R [date_time]

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-031 | | | +| TP label | Whitepaper. Glucose Sampling Interval Numeric Object – Base-Offset-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GSI Numeric 7; M | BaseOffset 1; M | +| Test purpose |

    Check that:

    PHG includes Glucose Sampling Interval Numeric Object Base-Offset-Time-Stamp attribute in transcoder output.

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation (Base-Offset-Time-Stamp attribute will be derived from the collector's time at the time of collection)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has a manually entered communication interval value stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • • Format: uint8
          • • Value: 0x03
        2. ii. Field: Operand
          • • Format: uint8 (min)
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to perform a CGM Communication Interval procedure using Op Code "Get CGM Communication Interval" (0x02) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code field).
    5. 5. The simulated PHD will respond with an indication including a "Communication Interval Response" Op Code (0x03) and an UINT8 containing the communication interval in minutes.
    6. 6. Check in PHG transcoder output the Glucose Sampling Interval Numeric Object – Base-Offset-Time-Stamp attribute
    | | | +| Pass/Fail criteria | In Step 6 the Glucose Sampling Interval Numeric Object – Base-Offset-Time-Stamp attribute is present and it is set to the collector's time at the time of collection. | | | +| Notes | Possible values in typical points of observation after transcoder output are: | | | + +| | | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| (To assist manual testing) |

    a) IEEE 11073 Objects and Attributes

    Base-Offset-Time-Stamp attribute is present:

    • Object: Glucose Sampling Interval Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
    • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
    • Attribute-value: collector's time at the time of collection.

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Base-Offset-Time-Stamp attribute value (check OBX-14):

    OBX n NM 8418044^MDC_CGM_SENSOR_SAMPLE_INTERVAL^MDC  m.0.0.x [value] 264352^MDC_DIM_MIN^MDC    R  [value described in a) coded in DTM format]
    | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-032 | | | +| TP label | Whitepaper. Glucose Sampling Interval Numeric Object – Basic-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GSI Numeric 8; M | | +| Test purpose |

    Check that:

    PHG includes Glucose Sampling Interval Numeric Object Basic-Nu-Observed-Value attribute in transcoder output.

    [AND]

    Basic-Nu-Observed-Value attribute is set to the correct value.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has a manually entered communication interval value stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:
      1. a. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • • Format: uint8
          • • Value: 0x03
        2. ii. Field: Operand
          • • Format: uint8 (min)
          • • Value: 15
        3. iii. Field: E2E-CRC
          • • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to perform a CGM Communication Interval procedure using Op Code “Get CGM Communication Interval” (0x02) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code field).
    5. 5. The simulated PHD will respond with an indication including a “Communication Interval Response” Op Code (0x03) and an UINT8 containing the communication interval in minutes.
    | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 6. Check in PHG transcoder output the Glucose Sampling Interval Numeric Object – Basic-Nu-Observed-Value attribute | +| Pass/Fail criteria | In Step 6 the Glucose Sampling Interval Numeric Object – Basic-Nu-Observed-Value attribute is present and it is set to 0x000F (SFLOAT-Type conversion of uint8 with exponent of 0) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Glucose Sampling Interval Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 15 (dec) or 000F (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX[n NM 8418044^MDC_CGM_SENSOR_SAMPLE_INTERVAL^MDC m.0.0.x 15 264352^MDC_DIM_MIN^MDC R [date_time]

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-033 | | | +| TP label | Whitepaper. Glucose trend Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Glucose trend Numeric Object – Handle Attribute in transcoder output.

    [OR]

    If PHG includes Glucose trend Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 1000 0000 0000 0000 (MSB → LSB). CGM trend information supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • iv. Field: E2E-CRC
      • • Format: uint16
      • • Value: not relevant
    • b. CGM Measurement (0x2AA7)
      • i. Field: Size
        • • Format: uint8
      • ii. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0001 (MSB → LSB). CGM Trend information present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
      • iii. Field: CGM Glucose Concentration (mg/dL)
        • • Format: SFLOAT
        • • Value: not Relevant
      • iv. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant
      • v. Field: Sensor Status Annunciation
        • • This field is not included
      • vi. Field: CGM Trend Information (mg/dL)/min
        • • Format: SFLOAT
        • • Value: not relevant
      • vii. Field: CGM Quality
        • • This field is not included
      • viii. Field: E2E-CRC
        • • This field is not included
    1. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    3. The simulated PHD sends the Measurement to the PHG under test.
    4. Check in the PHG transcoder output the Glucose trend Numeric Object– Handle attribute
    5. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    6. Check in the PHG transcoder output the Glucose trend Numeric Object – Handle attribute
    | +| Pass/Fail criteria | In Step 6 and 8, the Glucose Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Glucose trend Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0
    | + +| | | +|--|-----------------------------------------------------------------------------------------------| +| | b) WAN PCD-01 message
    PCD-01 message does not include segments with Handle attribute value | +|--|-----------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-034 | | | +| TP label | Whitepaper. Glucose trend Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 2; M | | +| Test purpose | Check that:
    PHG includes Glucose trend Numeric Object – Type attribute in transcoder output.
    [AND]
    Type is set to MDC_PART_PHD_DM MDC_CONC_GLU_TREND | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 1000 0000 0000 0000 (MSB → LSB). CGM trend information supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0001 (MSB → LSB). CGM Trend information present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
    | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
      • • Value: not Relevant
    • iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    • v. Field: Sensor Status Annunciation
      • • This field is not included
    • vi. Field: CGM Trend Information (mg/dL)/min
      • • Format: SFLOAT
      • • Value: not relevant
    • vii. Field: CGM Quality
      • • This field is not included
    • viii. Field: E2E-CRC
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.

    5. The simulated PHD sends the Measurement to the PHG under test.

    6. Check in the PHG transcoder output the Glucose trend Numeric Object– Type attribute

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    8. Check in PHG transcoder output the Glucose trend Numeric Object – Type attribute

    | +| Pass/Fail criteria | In Step 6 and 8, the Glucose Numeric Object – Type attribute is present and its value is MDC_PART_PHD_DM MDC_CONC_GLU_TREND | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is not present, or if it is present then:

    • Object: Glucose trend Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CONC_GLU_TREND or 29400 (dec) or 72 D8 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX n NM 8418008^MDC_CONC_GLU_TREND^MDC m.0.0.x [value]  266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC     R  [date_time]
    | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-035 | | | +| TP label | Whitepaper. Glucose trend Numeric Object - Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 3; M | | +| Test purpose |

    Check that:

    PHG includes Glucose trend Numeric Object – Metric-Spec-Small attribute in transcoder

    | | | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | output.
    [AND]
    Metric-Spec-Small is set to {0xF042}. | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 1000 0000 0000 0000 (MSB → LSB). CGM trend information supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0000 0001 (MSB → LSB). CGM Trend information present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
          • • Value: not Relevant
        4. iv. Field: Time Offset
          • • Format: uint16
          • • Value: not relevant
        5. v. Field: Sensor Status Annunciation
          • • This field is not included
        6. vi. Field: CGM Trend Information (mg/dL)/min
          • • Format: SFLOAT
          • • Value: not relevant
    | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    vii. Field: CGM Quality

    • This field is not included

    viii. Field: E2E-CRC

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.

    5. The simulated PHD sends the Measurement to the PHG under test.

    6. Check in the PHG transcoder output the Glucose trend Numeric Object– Metric-Spec-Small attribute

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    8. Check in PHG transcoder output the Glucose trend Numeric Object – Metric-Spec-Small attribute

    | +| Pass/Fail criteria | In Step 6 and 8, the Glucose trend Numeric Object – Metric-Spec-Small attribute is present and its value is {0xF042} (mss-avail-intermittent mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-cat-calculation mss-avail-stored-data) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Glucose trend Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: 0xF042 (hex) or BITS mss-avail-intermittent (0), mss-avail-stored-data (1), mss-upd-aperiodic (2), mss-msmt-aperiodic (3), mss-acc-agent-initiated(9), mss-cat-calculation(14) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-036 | | | +| TP label | Whitepaper. Glucose trend Numeric Object – Measurement-Status Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 4; O | | +| Test purpose |

    Check that:

    PHG may include Glucose trend Numeric Object – Measurement-Status attribute in transcoder output.

    [AND]

    If present, and related to Sensor Status Annunciation field, Measurement-Status is set to the correct value.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.

    | | | + +2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: + - a. CGM Feature (0x2AA8) + - i. Field: CGM Feature + - Format: 24 bit + - Value: 0000 0000 1000 0000 0001 0000 (MSB → LSB). CGM trend information supported, rate of increase/decrease alert supported. + - ii. Field: CGM Type + - Format: 4 bit + - Value: not relevant + - iii. Field: CGM Sample Location + - Format: 4 bit + - Value: not relevant + - iv. Field: E2E-CRC + - Format: uint16 + - Value: not relevant + - b. CGM Measurement (0x2AA7) + - i. Field: Size + - Format: uint8 + - ii. Field: Flags + - Format: 8 bit + - Value: **1**000 000**1** (MSB → LSB). CGM Trend information present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present. + - iii. Field: CGM Glucose Concentration (mg/dL) + - Format: SFLOAT + - Value: not Relevant + - iv. Field: Time Offset + - Format: uint16 + - Value: not relevant + - v. Field: Sensor Status Annunciation + - Format: 8 bit + - Value: 000**1** 0000 (MSB → LSB) (sensor rate of decrease exceeded). + - vi. Field: CGM Trend Information (mg/dL)/min + - Format: SFLOAT + - Value: not relevant + - vii. Field: CGM Quality + - This field is not included + - viii. Field: E2E-CRC + - This field is not included +3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state). +4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics. +5. The simulated PHD sends the Measurement to the PHG under test. + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    6. Check in the PHG transcoder output the Glucose trend Numeric Object– Measurement-Status attribute

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    8. Check in the PHG transcoder output the Glucose trend Numeric Object – Measurement-Status attribute

    9. The simulated PHD sends a Measurement to PHG under test with Sensor Status Annunciation field set to 0010 0000 (MSB → LSB), sensor rate of increase exceeded (bit 21). All remaining fields remain equal to those in step 2. The simulated PHD also deletes all stored records in RACP and stores an identical measurement. Repeat steps 5-7.

    | +| Pass/Fail criteria |
    • • In Step 6 and 8 the Glucose trend Numeric Object – Measurement-Status attribute, if present, is set to “measurement outside threshold boundaries” (bit 14).
    • • In Step 9 the Glucose trend Numeric Object – Measurement-Status attribute, if present is set to “measurement outside threshold boundaries” (bit 14) for both cases.
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    If Measurement-Status attribute is present:

    • Object: Glucose trend Numeric Object
    • Attribute-id: MDC_ATTR_MSMT_STAT (2375)
    • Attribute-type: BITS16
    • Attribute-value (Steps 6 & 8): “measurement outside threshold boundaries” (0x0020)
    • Attribute-value (Step 9): “measurement outside threshold boundaries” (0x0020)

    b) WAN PCD-01 message

    If Measurement-Status is present, PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):

    • • Steps 6 & 8
      OBX n NM 8418008^MDC_CONC_GLU_TREND^MDC m.0.0.x [value] [266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC] ALACT R [date_time]
    • • Step 9
      OBX n NM 8418008^MDC_CONC_GLU_TREND^MDC m.0.0.x [value] [266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC] ALACT R [date_time]
    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-037 | | | +| TP label | Whitepaper. Glucose trend Numeric Object – Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 5; M | | +| Test purpose |

    Check that:

    PHG includes Glucose trend Numeric Object – Unit-Code attribute in transcoder output.

    [AND]

    Unit-Code attribute value is set to MDC_DIM_MILLI_G_PER_DL_PER_MIN

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.

    | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:

    • a. CGM Feature (0x2AA8)
      • i. Field: CGM Feature
        • • Format: 24 bit
        • • Value: 0000 0000 1000 0000 0000 0000 (MSB → LSB). CGM trend information supported.
      • ii. Field: CGM Type
        • • Format: 4 bit
        • • Value: not relevant
      • iii. Field: CGM Sample Location
        • • Format: 4 bit
        • • Value: not relevant
      • iv. Field: E2E-CRC
        • • Format: uint16
        • • Value: not relevant
    • b. CGM Measurement (0x2AA7)
      • i. Field: Size
        • • Format: uint8
      • ii. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0001 (MSB → LSB). CGM Trend information present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
      • iii. Field: CGM Glucose Concentration (mg/dL)
        • • Format: SFLOAT
        • • Value: not relevant
      • iv. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant
      • v. Field: Sensor Status Annunciation
        • • This field is not included
      • vi. Field: CGM Trend Information (mg/dL)/min
        • • Format: SFLOAT
        • • Value: not relevant
      • vii. Field: CGM Quality
        • • This field is not included
      • viii. Field: E2E-CRC
        • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.

    5. The simulated PHD sends the Measurement to the PHG under test.

    6. Check in PHG transcoder output the Glucose trend Numeric Object– Unit-Code attribute

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    8. Check in PHG transcoder output the Glucose trend Numeric Object – Unit-Code attribute

    | +| Pass/Fail criteria | In Step 6 and 8 the Glucose trend Numeric Object – Unit-Code attribute is present and its value is set to MDC_DIM_MILLI_G_PER_DL_PER_MIN | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Glucose trend Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: OID-Type
    • Attribute-value: MDC_DIM_MILLI_G_PER_DL_PER_MIN or 4724 (dec) or 12 74 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):

    OBX[n NM 8418008^MDC_CONC_GLU_TREND^MDC m.0.0.x[[value]] 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC    R  [date_time]
    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-038 | | | +| TP label | Whitepaper. Glucose trend Numeric Object – Base-Offset-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 6; M | BaseOffset 3; M | +| Test purpose |

    Check that:

    PHG includes Glucose trend Numeric Object Base-Offset-Time-Stamp attribute in transcoder output.

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 1000 0000 0000 0000 (MSB → LSB). CGM trend information supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
    | | | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • iii. Field: CGM Sample Location
      • • Format: 4 bit
      • • Value: not relevant
    • iv. Field: E2E-CRC
      • • Format: uint16
      • • Value: not relevant

    b. CGM Measurement (0x2AA7)

    • i. Field: Size
      • • Format: uint8
    • ii. Field: Flags
      • • Format: 8 bit
      • • Value: 0000 0001 (MSB → LSB). CGM Trend information present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
    • iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: not relevant
    • iv. Field: Time Offset
      • • Format: uint16
      • • Value: 20 (min)
    • v. Field: Sensor Status Annunciation
      • • This field is not included
    • vi. Field: CGM Trend Information (mg/dL)/min
      • • Format: SFLOAT
      • • Value: not relevant
    • vii. Field: CGM Quality
      • • This field is not included
    • viii. Field: E2E-CRC
      • • This field is not included

    c. CGM Session Start Time (0x2AAA)

    • i. Field: Session Start Time
      • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
      • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
    • ii. Field: Time Zone
      • • Format: sint8
      • • Value: 4 (UTC+1:00)
    • iii. Field: DST-Offset
      • • Format: uint8
      • • Value: 4 (Daylight Time (+1h))
    • iv. Field: E2E-CRC
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    read the CGM Feature and CGM Session Start Time characteristics.

    1. 5. The simulated PHD sends the Measurement to the PHG under test.
    2. 6. Check in the PHG transcoder output the Glucose trend Numeric Object– Base-Offset-Time-Stamp attribute
    3. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    4. 8. Check in PHG transcoder output the Glucose trend Numeric Object – Base-Offset-Time-Stamp attribute
    | +| Pass/Fail criteria | In Step 6 and 8, the Glucose Numeric Object – Base-Offset-Time-Stamp is set to the addition of CGM Session Start Time characteristic's Session Start Time (May 12, 2016, 16:39:27) field plus CGM Measurement characteristic's Time Offset field (20 min). | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Base-Offset-Time-Stamp attribute is present:

    • Object: Glucose trend Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
    • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
    • Attribute-value: addition of
      • • CGM Session Start Time characteristic Session Start Time field (May 12, 2016, 16:39:27)
      • • CGM Measurement characteristic Time Offset field (20m)

    Note that the same Base-Offset-Time-Stamp can have different representations depending on bo-time-offset value. If it is set to 20 min (CGM Measurement characteristic's Time Offset field), then Base-Offset-Time-Stamp value shall be {3672059967, 0, 20}

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Base-Offset-Time-Stamp attribute value (check OBX-14):

    OBX n NM 8418008^MDC_CONC_GLU_TREND^MDC m.0.0.x [value]  266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC     R  [value described in a) coded in DTM format]
    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-039 | | | +| TP label | Whitepaper. Glucose trend Numeric Object – Basic-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 7; M | | +| Test purpose |

    Check that:

    PHG includes Glucose trend Numeric Object Basic-Nu-Observed-Value attribute in transcoder output.

    [AND]

    Basic-Nu-Observed-Value attribute is set to the correct value.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    | | | + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

    2.

    |

    The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:

    • a. CGM Feature (0x2AA8)
      • i. Field: CGM Feature
        • • Format: 24 bit
        • • Value: 0000 0000 1000 0000 0000 0000 (MSB → LSB). CGM trend information supported.
      • ii. Field: CGM Type
        • • Format: 4 bit
        • • Value: not relevant
      • iii. Field: CGM Sample Location
        • • Format: 4 bit
        • • Value: not relevant
      • iv. Field: E2E-CRC
        • • Format: uint16
        • • Value: not relevant
    • b. CGM Measurement (0x2AA7)
      • i. Field: Size
        • • Format: uint8
      • ii. Field: Flags
        • • Format: 8 bit
        • • Value: 0000 0001 (MSB → LSB). CGM Trend information present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
      • iii. Field: CGM Glucose Concentration (mg/dL)
        • • Format: SFLOAT
        • • Value: not relevant
      • iv. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant
      • v. Field: Sensor Status Annunciation
        • • This field is not included
      • vi. Field: CGM Trend Information (mg/dL)/min
        • • Format: SFLOAT
        • • Value: 3.6
      • vii. Field: CGM Quality
        • • This field is not included
      • viii. Field: E2E-CRC
        • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.

    5. The simulated PHD sends the Measurement to the PHG under test.

    6. Check in the PHG transcoder output the Glucose trend Numeric Object– Basic-Nu-

    | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Observed-Value attribute

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    8. Check in PHG transcoder output the Glucose trend Numeric Object – Basic-Nu-Observed-Value attribute

    | +| Pass/Fail criteria | In Step 6 and 8, the Glucose trend Numeric Object – Basic-Nu-Observed-Value is set to 3.6 (mg/dL)/min | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Basic-Nu-Observed-Value attribute is present:

    • Object: Glucose trend Numeric Object
    • Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)
    • Attribute-type: SFLOAT
    • Attribute-value: 3.6 (dec) or F0 24 (hex) or E1 68 (hex) or DE 10 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):

    OBX[n NM 8418008^MDC_CONC_GLU_TREND^MDC m.0.0.x 3.6  266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC    R  [date_time]
    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-040 | | | +| TP label | Whitepaper. Glucose trend Numeric Object – Threshold-Notification-Text-String | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GT Numeric 8; O | | +| Test purpose |

    Check that:

    PHG may transcode bits 20 and 21 of the CGM Sensor Status Annunciation field of CGM Measurement characteristic into Glucose trend Numeric Object – Threshold-Notification-Text-String attribute

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 1000 0000 0001 0000 (MSB → LSB). CGM trend information supported, rate of increase/decrease alerts supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
    | | | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant

    iv. Field: E2E-CRC

    • • Format: uint16
    • • Value: not relevant

    b. CGM Measurement (0x2AA7)

    • i. Field: Size
      • • Format: uint8
    • ii. Field: Flags
      • • Format: 8 bit
      • • Value: 1000 0001 (MSB → LSB). CGM Trend information present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present.
    • iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: not relevant
    • iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    • v. Field: Sensor Status Annunciation
      • • Format: 8 bit
      • • Value: 0001 0000 (MSB → LSB) (sensor rate of decrease exceeded).
    • vi. Field: CGM Trend Information (mg/dL)/min
      • • Format: SFLOAT
      • • Value: not relevant
    • vii. Field: CGM Quality
      • • This field is not included
    • viii. Field: E2E-CRC
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.

    5. The simulated PHD sends the Measurement to the PHG under test.

    6. Check in the PHG transcoder output the Glucose trend Numeric Object– Threshold-Notification-Text-String attribute

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    8. Check in PHG transcoder output the Glucose trend Numeric Object – Threshold-Notification-Text-String attribute

    9. The simulated PHD sends a CGM Measurement to PHG under test with the following values. The simulated PHD also deletes all previous stored records in RACP and stores an identical measurement in it.

    a. CGM Measurement (0x2AA7)

    • i. Field: Size
      • • Format: uint8
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    ii. Field: Flags

    • Format: 8 bit
    • Value: 1000 0001 (MSB → LSB). CGM Trend information present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present.

    iii. Field: CGM Glucose Concentration (mg/dL)

    • Format: SFLOAT
    • Value: not relevant

    iv. Field: Time Offset

    • Format: uint16
    • Value: not relevant

    v. Field: Sensor Status Annunciation

    • Format: 8 bit
    • Value: 0010 0000 (MSB → LSB) (sensor rate of increase exceeded).

    vi. Field: CGM Trend Information (mg/dL)/min

    • Format: SFLOAT
    • Value: not relevant

    vii. Field: CGM Quality

    • This field is not included

    viii. Field: E2E-CRC

    • This field is not included

    10. Repeat steps 6-8 to check in transcoder output the Glucose trend Numeric Object – Threshold-Notification-Text-String attribute.

    | +| Pass/Fail criteria |
    • In Step 6 and 8, if present, the Glucose trend Numeric Object – Threshold-Notification-Text-String is set to an OCTET STRING that may contain a readable description of the threshold notification “sensor rate of decrease exceeded”
    • In Step 10, if present, the Glucose trend Numeric Object – Threshold-Notification-Text-String is set to an OCTET STRING that may contain a readable description of the threshold notification “sensor rate of increase exceeded” for both cases.
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    If Threshold-Notification-Text-String attribute is present:

    • Object: Glucose trend Numeric Object
    • Attribute-id: MDC_ATTR_THRES_NOTIF_TEXT_STRING (2696)
    • Attribute-type: OCTET STRING
    • Attribute-value (Steps 6 & 8): readable description of the threshold notification “sensor rate of decrease exceeded”
    • Attribute-value (Step 10): readable description of the threshold notification “sensor rate of increase exceeded”

    b) WAN PCD-01 message

    Threshold-Notification-Text-String attribute is not included in PCD-01 message

    | + +| | | | | +|-----------------|------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-041 | | | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable | PLH Numeric 1; O | | + +| | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--| +| | items | | | | +| Test purpose |

    Check that:

    PHG does not include Patient low/high thresholds Compound Numeric Object – Handle Attribute in transcoder output.

    [OR]

    If PHG includes Patient low/high thresholds Compound Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_046 AND C_MAN_BLE_048 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has manually entered Patient Low Alert Level and Patient High Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • Format: uint8
          • Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
        2. ii. Field: Operand
          • Format: SFLOAT (mg/dL)
          • Value: not relevant
        3. iii. Field: E2E-CRC
          • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    5. 5. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    6. 6. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low
    | | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Alert Level" (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    7. The simulated PHD will respond with an indication including a "Patient Low Alert Level Response" (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    8. Check in the PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Handle attribute | +| Pass/Fail criteria | In Step 8, the Patient low/high thresholds Compound Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Patient low/high thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-042 | | | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Patient low/high thresholds Compound Numeric Object – Type attribute in transcoder output.

    [AND]

    Type is set to MDC_PART_PHD_DM
    MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_046 AND C_MAN_BLE_048 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has manually entered Patient Low Alert Level and Patient High Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Value: not relevant
    • iv. Field: E2E-CRC
      • Format: uint16
      • Value: not relevant
    • b. CGM Specific Ops Control Point (0x2AAC)
      • i. Field: Op Code
        • Format: uint8
        • Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
      • ii. Field: Operand
        • Format: SFLOAT (mg/dL)
        • Value: not relevant
      • iii. Field: E2E-CRC
        • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 5. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    4. 6. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low Alert Level” (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    5. 7. The simulated PHD will respond with an indication including a “Patient Low Alert Level Response” (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    6. 8. Check in PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Type attribute
    | +| Pass/Fail criteria | In Step 8, the Patient low/high thresholds Compound Numeric Object – Type attribute is present and set to MDC_PART_PHD_DM MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Patient low/high thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH or 29404 (dec) or 72 DC (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX n  8418012^MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH^MDC  m.0.x.0     X   [date_time]
    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-043_A | | | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object - Metric-Spec-Small Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 3; M | PLH Numeric 5; M | +| Test purpose |

    Check that:

    PHG includes Patient low/high thresholds Compound Numeric Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x604C} when the patient low/high thresholds were updated manually by the user

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_046 AND C_MAN_BLE_048 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has manually entered Patient Low Alert Level and Patient High Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
        2. ii. Field: Operand
          1. Format: SFLOAT (mg/dL)
          2. Value: not relevant
        3. iii. Field: E2E-CRC
          1. This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Session Start Time characteristics, and then to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    1. 5. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    2. 6. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low Alert Level” (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 7. The simulated PHD will respond with an indication including a “Patient Low Alert Level Response” (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    4. 8. Check in PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Type attributeCheck in PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 8, the Patient low/high thresholds Compound Numeric Object – Metric-Spec-Small attribute is present and its value is {0x604C} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-manual mss-cat-setting) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes
      Metric-Spec-Small attribute is present:
      • Object: Patient low/high thresholds Compound Numeric Object
      • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
      • Attribute-type: BITS-16
      • Attribute-value: 60 4C (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-manual(12), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE
    2. b) WAN PCD-01 message
      PCD-01 message does not include segments with Metric-Spec-Small attribute value
    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-043_B | | | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object - Metric-Spec-Small Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 3; M | PLH Numeric 4; M | +| Test purpose |

    Check that:

    PHG includes Patient low/high thresholds Compound Numeric Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x6044} when the Patient High/Low Alert Level procedure has been executed

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_045 AND C_MAN_BLE_046 AND C_MAN_BLE_047 AND C_MAN_BLE_048 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
        • Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
      • ii. Field: CGM Type
        • Format: 4 bit
        • Value: not relevant
      • iii. Field: CGM Sample Location
        • Format: 4 bit
        • Value: not relevant
      • iv. Field: E2E-CRC
        • Format: uint16
        • Value: not relevant
    • b. CGM Specific Ops Control Point (0x2AAC)
      • i. Field: Op Code
        • Format: uint8
        • Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
      • ii. Field: Operand
        • Format: SFLOAT (mg/dL)
        • Value: not relevant
      • iii. Field: E2E-CRC
        • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    3. 5. Force the PHG to set the patient high threshold by performing a Patient High Alert procedure using Op Code “Set Patient High Alert Level” (0x07) followed by a valid SFLOAT value (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Operand fields respectively). The simulated PHD will respond with an indication including a Response Op Code value of “Success”.
    4. 6. Force the PHG to set the patient low threshold by performing a Patient Low Alert procedure using Op Code “Set Patient Low Alert Level” (0x0A) followed by a valid SFLOAT value (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Operand fields respectively). The simulated PHD will respond with an indication including a Response Op Code value of “Success”.
    5. 7. Then, force the PHG to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    6. 8. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    7. 9. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low Alert Level” (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    8. 10. The simulated PHD will respond with an indication including a “Patient Low Alert Level Response” (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    9. 11. Check in PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Type attribute
      Check in PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 11, the Patient low/high thresholds Compound Numeric Object – Metric-Spec-Small attribute is present and its value is {0x6044} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-setting) | +| Notes | Possible values in typical points of observation after transcoder output are: | + +| | | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| (To assist manual testing) | a) IEEE 11073 Objects and Attributes
    Metric-Spec-Small attribute is present:
    Object: Patient low/high thresholds Compound Numeric Object
    Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    Attribute-type: BITS-16
    Attribute-value: 0x6044 (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE | +| | b) WAN PCD-01 message
    PCD-01 message does not include segments with Metric-Spec-Small attribute value | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-044 | | | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object – Metric-Structure-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 6; M | | +| Test purpose | Check that:
    PHG includes Patient low/high thresholds Compound Numeric Object – Metric-Structure-Small attribute in transcoder output.
    [AND]
    Metric-Structure-Small is set to {0x40, 0x02} | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_046 AND C_MAN_BLE_048 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has manually entered Patient Low Alert Level and Patient High Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
          • Value: not relevant
        4. iv. Field: E2E-CRC
          • Format: uint16
          • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
    | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: uint8
    • Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
    • ii. Field: Operand
      • Format: SFLOAT (mg/dL)
      • Value: not relevant
    • iii. Field: E2E-CRC
      • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 5. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    4. 6. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low Alert Level” (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    5. 7. The simulated PHD will respond with an indication including a “Patient Low Alert Level Response” (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    6. 8. Check in PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Metric-Structure-Small attribute
    | +| Pass/Fail criteria | In Step 8, the Patient low/high thresholds Compound Numeric Object – Metric-Structure-Small attribute is present and set to 0x40 (ms-struct-compound), 0x02 (number of components is 2) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Structure-Small attribute is present:

    • Object: Patient low/high thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_STRUCT_SMALL (2675)
    • Attribute-type: SEQUENCE {ms-struct (INT-U8), ms-comp-no (INT-U8)}
    • Attribute-value:
      • • ms-struct: 0x40 (ms-struct-compound)
      • • ms-comp-no: 0x02 (number of components)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Structure-Small attribute value

    | + +| | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-045 | | | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object – Metric-Id-List Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 7; M | | +| Test purpose |

    Check that:

    PHG includes Patient low/high thresholds Compound Numeric Object – Metric-Id-List attribute in transcoder output.

    [AND]

    Metric-Id-List is set to { 0x0002, 0x0004, MDC_CONC_GLU_PATIENT_THRESHOLD_LOW, MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH }

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_046 | | | + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | AND C_MAN_BLE_048 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has manually entered Patient Low Alert Level and Patient High Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
        2. ii. Field: Operand
          1. Format: SFLOAT (mg/dL)
          2. Value: not relevant
        3. iii. Field: E2E-CRC
          1. This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    5. 5. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    6. 6. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low Alert Level” (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    7. 7. The simulated PHD will respond with an indication including a “Patient Low Alert Level Response” (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    8. 8. Check in PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Metric-Id-List attribute
    | +| Pass/Fail criteria | In Step 8, the Patient low/high thresholds Compound Numeric Object – Metric-Id-List attribute is present and set to 0x0002 (count of metric ids is 2), 0x0004 (list length is 4 octets), MDC_CONC_GLU_PATIENT_THRESHOLD_LOW, | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id-List attribute is present:

    • Object: Patient low/high thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_ID_PHYSIO_LIST (2678)
    • Attribute-type: SEQUENCE OF {{OID-Type(INT-U16)}}
    • Attribute-value: 0x0002 (number of elements), 0x0004 (length of the sequence), followed by
      • • First element: MDC_CONC_GLU_PATIENT_THRESHOLD_LOW (0x72DD)
      • • Second element: MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH (0x72DE)

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these with Metric-Id-List attribute values (check OBX-3 in both segments):

    OBX[n NM 8418013^MDC_CONC_GLU_PATIENT_THRESHOLD_LOW^MDC  m.0.x.a [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R
    OBX[n NM 8418014^MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH^MDC  m.0.x.b [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R
    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-046 | | | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object – Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 8; M | | +| Test purpose |

    Check that:

    PHG includes Patient low/high thresholds Compound Numeric Object – Unit-Code attribute in transcoder output.

    [AND]

    Unit-Code is set to MDC_DIM_MILLI_G_PER_DL

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_046 AND C_MAN_BLE_048 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has manually entered Patient Low Alert Level and Patient High Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
    | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Value: not relevant
    • iv. Field: E2E-CRC
      • Format: uint16
      • Value: not relevant
    • b. CGM Specific Ops Control Point (0x2AAC)
      • i. Field: Op Code
        • Format: uint8
        • Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
      • ii. Field: Operand
        • Format: SFLOAT (mg/dL)
        • Value: not relevant
      • iii. Field: E2E-CRC
        • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 5. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    4. 6. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low Alert Level” (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    5. 7. The simulated PHD will respond with an indication including a “Patient Low Alert Level Response” (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    6. 8. Check in the PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Unit-Code attribute
    | +| Pass/Fail criteria | In Step 8, the Patient low/high thresholds Compound Numeric Object – Unit-Code attribute is present and set to MDC_DIM_MILLI_G_PER_DL | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Patient low/high thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: OID-Type
    • Attribute-value: MDC_DIM_MILLI_G_PER_DL or 2130 (dec) or 0x0852 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these with Unit-Code attribute value (check OBX-6 in both segments):

    OBX[n NM 8418013^MDC_CONC_GLU_PATIENT_THRESHOLD_LOW^MDC  m.0.x.a [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R
    OBX[n NM 8418014^MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH^MDC  m.0.x.b [value] 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R
    | + +| | | +|-----------------|----------------------------------------------------------------------------------------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-047 | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object – Base-Offset-Time-Stamp Attribute | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 9; M | BaseOffset 1; M | +| Test purpose |

    Check that:

    PHG includes Patient low/high thresholds Compound Numeric Object – Base-Offset-Time-Stamp Attribute

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation (Base-Offset-Time-Stamp attribute will be derived from the collector's time at the time of collection)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_046 AND C_MAN_BLE_048 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Patient Low Alert Level and Patient High Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
        2. ii. Field: Operand
          1. Format: SFLOAT (mg/dL)
          2. Value: not relevant
        3. iii. Field: E2E-CRC
          1. This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 5. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    2. 6. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low Alert Level” (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 7. The simulated PHD will respond with an indication including a “Patient Low Alert Level Response” (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    4. 8. Check in PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Base-Offset-Time-Stamp attribute
    | +| Pass/Fail criteria | In Step 8, the Patient low/high thresholds Compound Numeric Object – Base-Offset-Time-Stamp attribute is present and it is set to the collector’s time at the time of collection. | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Base-Offset-Time-Stamp attribute is present:

    • Object: Patient low/high thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
    • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
    • Attribute-value: collector’s time at the time of collection.

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Base-Offset-Time-Stamp attribute (check OBX-14):

    OBX n 8418012^MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH^MDC m.0.x.0 n X [value described in a) coded in DTM format]

    | + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-048 | | | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PLH Numeric 10; M | | +| Test purpose |

    Check that:

    PHG includes Patient low/high thresholds Compound Numeric Object Compound-Basic-Nu-Observed-Value attribute in transcoder output.

    [AND]

    Compound-Basic-Nu-Observed-Value attribute is set to the correct value.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_046 AND C_MAN_BLE_048 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has manually entered Patient Low Alert Level and Patient High Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ii. Field: CGM Type
      • Format: 4 bit
      • Value: not relevant
    • iii. Field: CGM Sample Location
      • Format: 4 bit
      • Value: not relevant
    • iv. Field: E2E-CRC
      • Format: uint16
      • Value: not relevant

    b. CGM Specific Ops Control Point (0x2AAC)

    • i. Field: Op Code
      • Format: uint8
      • Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
    • ii. Field: Operand
      • Format: SFLOAT (mg/dL)
      • Value: 72.0 (Patient Low threshold) / 144.0 (Patient High threshold)
    • iii. Field: E2E-CRC
      • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 5. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.
    4. 6. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low Alert Level” (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    5. 7. The simulated PHD will respond with an indication including a “Patient Low Alert Level Response” (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.
    6. 8. Check in PHG transcoder output the Patient low/high thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute
    | +| Pass/Fail criteria | In Step 8, the Patient low/high thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute is set to 0x0002 (count of components is 2), 0x0004 (component list length is 4 octets), the Patient Low Alert Level Response Operand followed by the Patient High Alert Level Response Operand | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • Object: Patient low/high thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • Attribute-type: SEQUENCE OF {[SFLOAT]}
    • Attribute-value: 0x0002 (number of elements), 0x0004 (length of the sequence), followed by
      • • First element (Patient Low Alert Level Response Operand): 00 48 (hex) or F2 D0 (hex) or 72.0 (dec)
      • • Second element (Patient High Level Response Operand): 00 90 (hex) or F5 A0 (hex) or 144.0 (dec)
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these with Compound-Basic-Nu-Observed-Value attribute value (check OBX-5 in both segments):

    OBX n NM 8418013^MDC_CONC_GLU_PATIENT_THRESHOLD_LOW^MDC m.0.x.a 72.0 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R
    OBX n NM 8418014^MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH^MDC m.0.x.b 144.0 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-049 | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 1; O | | +| Test purpose |

    Check that:

    PHG does not include Device hypo/hyper thresholds Compound Numeric Object – Handle Attribute in transcoder output.

    [OR]

    If PHG includes Device hypo/hyper thresholds Compound Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Hypo and Hyper Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • Format: uint8
          • Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
        2. ii. Field: Operand
    | | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: SFLOAT (mg/dL)
    • Value: not relevant

    iii. Field: E2E-CRC

    • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    3. 5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code "Get Hypo Alert Level" (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code). simulated PHD will respond with an indication including a "Hypo Alert Level Response" (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    4. 6. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code "Get Hyper Alert Level" (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code). The simulated PHD will respond with an indication including a "Hyper Alert Level Response" (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    5. 7. Check in PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Handle attribute
    | +| Pass/Fail criteria | In Step 7, the Device hypo/hyper thresholds Compound Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Device hypo/hyper thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-050 | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 2; M | | +| Test purpose |

    Check that:

    PHG includes Device hypo/hyper thresholds Compound Numeric Object – Type attribute in transcoder output.

    [AND]

    Type is set to MDC_PART_PHD_DM MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Hypo and Hyper Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    a. CGM Feature (0x2AA8)

    • i. Field: CGM Feature
      • Format: 24 bit
      • Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
    • ii. Field: CGM Type
      • Format: 4 bit
      • Value: not relevant
    • iii. Field: CGM Sample Location
      • Format: 4 bit
      • Value: not relevant
    • iv. Field: E2E-CRC
      • Format: uint16
      • Value: not relevant

    b. CGM Specific Ops Control Point (0x2AAC)

    • i. Field: Op Code
      • Format: uint8
      • Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
    • ii. Field: Operand
      • Format: SFLOAT (mg/dL)
      • Value: not relevant
    • iii. Field: E2E-CRC
      • This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.

    5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code “Get Hypo Alert Level” (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hypo Alert Level Response” (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.

    6. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code “Get Hyper Alert Level” (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hyper Alert Level Response” (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.

    7. Check in the PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Type attribute

    | +| Pass/Fail criteria | In Step 7, the Device hypo/hyper thresholds CompoundNumeric Object – Type attribute is present and set to MDC_PART_PHD_DM MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Device hypo/hyper thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-value:

    • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
    • • code: MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER or 29408 (dec) or 72 E0 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX n 8418016^MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER^MDC
    m.0.x.0 X [date_time]

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-051_A | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object - Metric-Spec-Small Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 3; M | DHH Numeric 4; M | +| Test purpose |

    Check that:

    PHG includes Device hypo/hyper thresholds Compound Numeric Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x604C} when the hypo/hyper thresholds were updated manually by the user

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Hypo and Hyper Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
          • Value: not relevant
        4. iv. Field: E2E-CRC
          • Format: uint16
          • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • Format: uint8
          • Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Response)

    ii. Field: Operand

    Format: SFLOAT (mg/dL)

    Value: not relevant

    iii. Field: E2E-CRC

    This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.

    5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code "Get Hypo Alert Level" (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code). The simulated PHD will respond with an indication including a "Hypo Alert Level Response" (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.

    6. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code "Get Hyper Alert Level" (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code). The simulated PHD will respond with an indication including a "Hyper Alert Level Response" (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.

    7. Check in PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Metric-Spec-Small attribute

    | +| Pass/Fail criteria | In Step 7, the Device hypo/hyper thresholds Compound Numeric Object – Metric-Spec-Small attribute is present and its value is {0x604C} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-manual mss-cat-setting) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    Object: Device hypo/hyper thresholds Compound Numeric Object

    Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)

    Attribute-type: BITS-16

    Attribute-value: 60 4C (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-manual(12), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-051_B | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object - Metric-Spec-Small Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 3; M | DHH Numeric 4; M | +| Test purpose |

    Check that:

    PHG includes Device hypo/hyper thresholds Compound Numeric Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x6044} when either the Hypo Alert or Hyper Alert procedure has been executed

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) AND (C_MAN_BLE_049 OR C_MAN_BLE_051) | | | + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
        2. ii. Field: Operand
          1. Format: SFLOAT (mg/dL)
          2. Value: not relevant
        3. iii. Field: E2E-CRC
          1. This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    5. 5. IF C_MAN_BLE_049 = TRUE, force the PHG to set the Hypo Alert Level by performing a Hypo Alert procedure using Op Code “Set Hypo Alert Level” (0x0D) followed by a valid SFLOAT value (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Operand fields respectively). The simulated PHD will respond with an indication including a Response Op Code value of “Success”.
    6. 6. IF C_MAN_BLE_051 = TRUE, force the PHG to set the Hyper Alert Level by performing a Hyper Alert procedure using Op Code “Set Hyper Alert Level” (0x10) followed by a valid SFLOAT value (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Operand fields respectively). The simulated PHD will respond with an indication including a Response Op Code value of “Success”.
    7. 7. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code “Get Hypo Alert Level” (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hypo Alert Level Response” (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    8. 8. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code “Get Hyper Alert Level” (0x11) (performing a write operation to the CGM Specific
    | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Ops Control Point characteristic's Op Code). The simulated PHD will respond with an indication including a "Hyper Alert Level Response" (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    9. Check in PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Metric-Spec-Small attribute | +| Pass/Fail criteria | In Step 9, the Device hypo/hyper thresholds Compound Numeric Object – Metric-Spec-Small attribute is present and its value is {0x6044} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-setting) | +| Notes
    (To assist manual testing)     | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Metric-Spec-Small attribute is present:
    • Object: Device hypo/hyper thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: 0x6044 (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE
    b) WAN PCD-01 message
    PCD-01 message does not include segments with Metric-Spec-Small attribute value | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-052 | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object – Metric-Structure-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 6; M | | +| Test purpose | Check that:
    PHG includes Device hypo/hyper thresholds Compound Numeric Object – Metric-Structure-Small attribute in transcoder output.
    [AND]
    Metric-Structure-Small is set to {0x40, 0x02} | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Hypo and Hyper Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
    | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Value: not relevant
    • iv. Field: E2E-CRC
      • Format: uint16
      • Value: not relevant
    • b. CGM Specific Ops Control Point (0x2AAC)
      • i. Field: Op Code
        • Format: uint8
        • Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
      • ii. Field: Operand
        • Format: SFLOAT (mg/dL)
        • Value: not relevant
      • iii. Field: E2E-CRC
        • This field is not present
    • 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    • 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    • 5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code “Get Hypo Alert Level” (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hypo Alert Level Response” (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    • 6. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code “Get Hyper Alert Level” (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hyper Alert Level Response” (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    • 7. Check in the PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Metric-Structure-Small attribute
    | +| Pass/Fail criteria | In Step 7, the Device hypo/hyper thresholds Compound Numeric Object – Metric-Structure-Small attribute is present and set to 0x40 (ms-struct-compound), 0x02 (number of components is 2) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Structure-Small attribute is present:

    • Object: Device hypo/hyper thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_STRUCT_SMALL (2675)
    • Attribute-type: SEQUENCE {ms-struct (INT-U8), ms-comp-no (INT-U8)}
    • Attribute-value:
      • • ms-struct: 0x40 (ms-struct-compound)
      • • ms-comp-no: 0x02 (number of components)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Structure-Small attribute value

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-053 | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object – Metric-Id-List Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 7; M | | +| Test purpose |

    Check that:

    PHG includes Device hypo/hyper thresholds Compound Numeric Object – Metric-Id-List attribute in transcoder output.

    [AND]

    Metric-Id-List is set to { 0x0002, 0x0004, MDC_CONC_GLU_THRESHOLD_HYPO, MDC_CONC_GLU_THRESHOLD_HYPER }

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Hypo and Hyper Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature Format: 24 bit Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
        2. ii. Field: CGM Type Format: 4 bit Value: not relevant
        3. iii. Field: CGM Sample Location Format: 4 bit Value: not relevant
        4. iv. Field: E2E-CRC Format: uint16 Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code Format: uint8 Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
        2. ii. Field: Operand Format: SFLOAT (mg/dL) Value: not relevant
        3. iii. Field: E2E-CRC This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code “Get Hypo Alert Level” (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hypo Alert Level Response” (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.

    6. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code “Get Hyper Alert Level” (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hyper Alert Level Response” (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.

    7. Check in the PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Metric-Id-List attribute

    | +| Pass/Fail criteria | In Step 7, the Device hypo/hyper thresholds Compound Numeric Object – Metric-Id-List attribute is present and set to 0x0002 (count of metric ids is 2), 0x0004 (list length is 4 octets), MDC_CONC_GLU_THRESHOLD_HYPO, MDC_CONC_GLU_THRESHOLD_HYPER | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id-List attribute is present:

    • Object: Device hypo/hyper thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_ID_PHYSIO_LIST (2678)
    • Attribute-type: SEQUENCE OF {[OID-Type(INT-U16)]}
    • Attribute-value: 0x0002 (number of elements), 0x0004 (length of the sequence), followed by
      • • First element: MDC_CONC_GLU_THRESHOLD_HYPO (0x72E1)
      • • Second element: MDC_CONC_GLU_THRESHOLD_HYPER (0x72E2)

    b) WAN PCD-01 message

    If both Hypo/Hyper Alert Level Responses are received, then PCD-01 message includes two segments like these with Metric-Id-List attribute values (check OBX-3 in both segments):

    OBX[n NM 8418017^MDC_CONC_GLU_THRESHOLD_HYPO^MDC m.0.x.a [value]] 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R  OBX[n NM 8418018^MDC_CONC_GLU_THRESHOLD_HYPER^MDC  m.0.x.b [value]]264274^MDC_DIM_MILLI_G_PER_DL^MDC    R

    Note: If one of the responses is not available, its related segment will appear with an empty [value], the value “NAN” in OBX-8 and the value “X” in OBX-11

    | + +| | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-054 | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object – Unit-Code Attribute | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | +| | Testable items | DHH Numeric 8; M | +| Test purpose |

    Check that:

    PHG includes Device hypo/hyper thresholds Compound Numeric Object – Unit-Code attribute in transcoder output.

    [AND]

    Unit-Code is set to MDC_DIM_MILLI_G_PER_DL

    | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | | +| Other PICS | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | +| Test procedure | 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    specialization). The PHD has manually entered Hypo and Hyper Alert Level values stored.

    1. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
        2. ii. Field: Operand
          1. Format: SFLOAT (mg/dL)
          2. Value: not relevant
        3. iii. Field: E2E-CRC
          1. This field is not present
    2. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    4. 5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code “Get Hypo Alert Level” (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hypo Alert Level Response” (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    5. 6. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code “Get Hyper Alert Level” (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hyper Alert Level Response” (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    6. 7. Check in the PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Unit-Code attribute
    | +| Pass/Fail criteria | In Step 7, the Device hypo/hyper thresholds Compound Numeric Object – Unit-Code attribute is present and set to MDC_DIM_MILLI_G_PER_DL | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes

      Unit-Code attribute is present:

      1. Object: Device hypo/hyper thresholds Compound Numeric Object
      2. Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-type: OID-Type
    • Attribute-value: MDC_DIM_MILLI_G_PER_DL or 2130 (dec) or 0x0852 (hex)

    b) WAN PCD-01 message

    If both Hypo/Hyper Alert Level Responses are received, then PCD-01 message includes two segments like these with Unit-Code attribute value (check OBX-6 in both segments):

    OBX n NM 8418017^MDC_CONC_GLU_THRESHOLD_HYPO^MDC m.0.x.a[[value]] 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R  OBX n NM 8418018^MDC_CONC_GLU_THRESHOLD_HYPER^MDC  m.0.x.b[[value]] 264274^MDC_DIM_MILLI_G_PER_DL^MDC    R

    Note: If one of the responses is not available, its related segment will appear with an empty [value], the value "NAN" in OBX-8 and the value "X" in OBX-11

    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-055 | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object – Base-Offset-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 9; M | BaseOffset 1; M | +| Test purpose |

    Check that:

    PHG includes Device hypo/hyper thresholds Compound Numeric Object – Base-Offset-Time-Stamp Attribute

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation (Base-Offset-Time-Stamp attribute will be derived from the collector's time at the time of collection)

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Hypo and Hyper Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
          • Value: not relevant
        4. iv. Field: E2E-CRC
          • Format: uint16
          • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
    | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. i. Field: Op Code
      • Format: uint8
      • Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
    2. ii. Field: Operand
      • Format: SFLOAT (mg/dL)
      • Value: not relevant
    3. iii. Field: E2E-CRC
      • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    3. 5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code "Get Hypo Alert Level" (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code). The simulated PHD will respond with an indication including a "Hypo Alert Level Response" (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    4. 6. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code "Get Hyper Alert Level" (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code). The simulated PHD will respond with an indication including a "Hyper Alert Level Response" (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    5. 7. Check in PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Base-Offset-Time-Stamp attribute
    | +| Pass/Fail criteria | In Step 7, the Device hypo/hyper thresholds Compound Numeric Object – Base-Offset-Time-Stamp attribute is present and it is set to the collector's time at the time of collection. | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    1. a) IEEE 11073 Objects and Attributes

      Base-Offset-Time-Stamp attribute is present:

      • Object: Device hypo/hyper thresholds Compound Numeric Object
      • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
      • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
      • Attribute-value: collector's time at the time of collection.
    2. b) WAN PCD-01 message

      PCD-01 message includes a segment like this with Type attribute (check OBX-14):

      OBX n  8418016^MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER^MDC  m.0.x.0     X  [value described in a) coded in DTM format]
    | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-056_A | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 10; M | | +| Test purpose |

    Check that:

    PHG includes Device hypo/hyper thresholds Compound Numeric Object Compound-Basic-Nu-Observed-Value attribute in transcoder output.

    [AND]

    Compound-Basic-Nu-Observed-Value attribute is set to the correct value.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Hypo and Hyper Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          Format: 24 bit
          Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
        2. ii. Field: CGM Type
          Format: 4 bit
          Value: not relevant
        3. iii. Field: CGM Sample Location
          Format: 4 bit
          Value: not relevant
        4. iv. Field: E2E-CRC
          Format: uint16
          Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          Format: uint8
          Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
        2. ii. Field: Operand
          Format: SFLOAT (mg/dL)
          Value: 36.0 (Hypo Alert Level Response) / 360.0 (Hyper Alert Level Response)
        3. iii. Field: E2E-CRC
          This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code “Get Hypo Alert Level” (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hypo Alert Level Response” (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.

    6. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code “Get Hyper Alert Level” (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hyper Alert Level Response” (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.

    7. Check in PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute

    | +| Pass/Fail criteria | In Step 7, the Device hypo/hyper thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute is set to 0x0002 (count of components is 2), 0x0004 (component list length is 4 octets), the Hypo Alert Level Response Operand followed by the Hyper Alert Level Response Operand | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • Object: Device hypo/hyper thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • Attribute-type: SEQUENCE OF {SFLOAT}
    • Attribute-value: 0x0002 (number of elements), 0x0004 (length of the sequence), followed by
      • • IF C_MAN_BLE_050 = TRUE, first element (Hypo Alert Level Response Operand) will be set to: 00 24 (hex) or F1 68 (hex) or EE 10 (hex) or 36.0 (dec). IF C_MAN_BLE_050 = FALSE, first element will be set to NaN (0x07FF)
      • • IF C_MAN_BLE_052 = TRUE, second element (Hyper Alert Level Response Operand) will be set to: 01 24 (hex) or FE 10 (hex) or 360.0 (dec). IF C_MAN_BLE_052 = FALSE, second element will be set to NaN (0x07FF)

    b) WAN PCD-01 message

    If both Hypo/Hyper Alert Level Responses are received, PCD-01 message includes two segments like these with Compound-Basic-Nu-Observed-Value attribute value (check OBX-5 in both segments):

    OBX[n NM 8418017^MDC_CONC_GLU_THRESHOLD_HYPO^MDC m.0.x.a 36.0  264274^MDC_DIM_MILLI_G_PER_DL^MDC    R
    OBX[n NM 8418018^MDC_CONC_GLU_THRESHOLD_HYPER^MDC m.0.x.b 360.0  264274^MDC_DIM_MILLI_G_PER_DL^MDC    R

    Note: If one of the responses is not available, its related segment will appear with an empty [value], the value “NAN” in OBX-8 and the value “X” in OBX-11

    | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-056_B | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value Attribute Special Values | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | DHH Numeric 10; M | DHH Numeric 11; M | +| Test purpose |

    Check that:

    PHG includes Device hypo/hyper thresholds Compound Numeric Object Compound-Basic-Nu-Observed-Value attribute in transcoder output.

    [AND]

    If only one of the Hypo Alert or the Hyper Alert support is indicated in the CGM Feature characteristic, NaN will be used for the component of the Compound-Basic-Nu-Observed-

    | | | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Value that corresponds with the unsupported alert. | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Hypo and Hyper Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      • a. CGM Feature (0x2AA8)
        • i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0000 0100 (MSB → LSB). Hypo Alerts supported.
        • ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        • iii. Field: CGM Sample Location
          • Format: 4 bit
          • Value: not relevant
        • iv. Field: E2E-CRC
          • Format: uint16
          • Value: not relevant
      • b. CGM Specific Ops Control Point (0x2AAC)
        • i. Field: Op Code
          • Format: uint8
          • Value: 0x0F (Hypo Alert Level Response)
        • ii. Field: Operand
          • Format: SFLOAT (mg/dL)
          • Value: 36.0 (Hypo Alert Level Response)
        • iii. Field: E2E-CRC
          • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    5. 5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code "Get Hypo Alert Level" (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code). The simulated PHD will respond with an indication including a "Hypo Alert Level Response" (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    6. 6. IF C_MAN_BLE_050 = TRUE, check in PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute.
    7. 7. End current CGM session and start a new one.
    8. 8. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization) and implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      • a. CGM Feature (0x2AA8)
        • i. Field: CGM Feature
    | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: 24 bit
    • Value: 0000 0000 0000 0000 0000 1000 (MSB → LSB). Hyper Alerts supported.
    • ii. Field: CGM Type
      • Format: 4 bit
      • Value: not relevant
    • iii. Field: CGM Sample Location
      • Format: 4 bit
      • Value: not relevant
    • iv. Field: E2E-CRC
      • Format: uint16
      • Value: not relevant
    • b. CGM Specific Ops Control Point (0x2AAC)
      • Field: Op Code
        • Format: uint8
        • Value: 0x12 (Hyper Alert Level Response)
      • i. Field: Operand
        • Format: SFLOAT (mg/dL)
        • Value: 360.0 (Hyper Alert Level Response)
      • ii. Field: E2E-CRC
        • This field is not present
    1. 9. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 10. When the pairing has been completed, IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code “Get Hyper Alert Level” (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hyper Alert Level Response” (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    3. 11. IF C_MAN_BLE_052 = TRUE, Check in PHG transcoder output the Device hypo/hyper thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute
    | +| Pass/Fail criteria |
    • • If Step 6 was checked, the Device hypo/hyper thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute is set to 0x0002 (count of components is 2), 0x0004 (component list length is 4 octets), the Hypo Alert Level Response Operand followed by the special value NaN (0x07FF)
    • • If Step 11 was checked, the Device hypo/hyper thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute is set to 0x0002 (count of components is 2), 0x0004 (component list length is 4 octets), the special value NaN (0x07FF) followed by the Hyper Alert Level Response Operand
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • Object: Device hypo/hyper thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • Attribute-type: SEQUENCE OF {(SFLOAT)}
    • Attribute-value (If Step 6 was checked): 0x0002 (number of elements), 0x0004 (length of the sequence), followed by
      • • First element (Hypo Alert Level Response Operand): 00 24 (hex) or F1 68 (hex) or EE 10 (hex) or 36.0 (dec)
      • • Second element (Hyper Alert Level Response Operand): NaN (0x07FF)
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-value (if Step 11 was checked): 0x0002 (number of elements), 0x0004 (length of the sequence), followed by
      • • First element (Hypo Alert Level Response Operand): NaN (0x07FF)
      • • Second element (Hyper Alert Level Response Operand): 01 24 (hex) or FE 10 (hex) or 360.0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes two segments like this with Compound-Basic-Nu-Observed-Value attribute value (check OBX-5):

    • • If Step 6 was checked: 
      OBX n NM 8418017^MDC_CONC_GLU_THRESHOLD_HYPO^MDC m.0.x.a 36.0  264274^MDC_DIM_MILLI_G_PER_DL^MDC    R
      OBX n NM 8418017^MDC_CONC_GLU_THRESHOLD_HYPO^MDC m.0.x.a   264274^MDC_DIM_MILLI_G_PER_DL^MDC  NAN  X
    • • IF Step 11 was checked: 
      OBX n NM 8418017^MDC_CONC_GLU_THRESHOLD_HYPO^MDC m.0.x.a   264274^MDC_DIM_MILLI_G_PER_DL^MDC  NAN  X
      OBX n NM 8418018^MDC_CONC_GLU_THRESHOLD_HYPER^MDC m.0.x.b 360.0  264274^MDC_DIM_MILLI_G_PER_DL^MDC    R
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-057 | | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 1; O | | +| Test purpose | Check that:

    PHG does not include Glucose rate of charge thresholds Compound Numeric Object – Handle Attribute in transcoder output.

    [OR]

    If PHG includes Glucose rate of charge thresholds Compound Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0 | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Rate of Decrease and Increase Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Value: not relevant

    iv. Field: E2E-CRC

    • Format: uint16
    • Value: not relevant

    2. CGM Specific Ops Control Point (0x2AAC)

    • i. Field: Op Code
      • Format: uint8
    • ii. Field: Op Code – Response Codes
      • Format: 8 bit
      • Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)
    • iii. Field: Operand
      • Format: SFLOAT (mg/dL/min)
      • Value: not relevant
    • iv. Field: E2E-CRC
      • This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Rate of Decrease Alert Level procedure using Op Code “Get Rate of Decrease Alert Level” (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    5. The simulated PHD will respond with an indication including a “Rate of Decrease Alert Level Response” (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.

    6. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    7. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.

    8. Check in PHG transcoder output the Glucose rate of charge thresholds Compound Numeric Object – Handle attribute

    | +| Pass/Fail criteria | In Step 8, the Glucose rate of charge thresholds Compound Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: Glucose rate of charge thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | + +| | | | +|-----------------|----------------------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-058 | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object - Type Attribute | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--|--| +| | Testable items | GRC Numeric 2; M | | | +| Test purpose |

    Check that:

    PHG includes Glucose rate of change thresholds Compound Numeric Object – Type attribute in transcoder output.

    [AND]

    Type is set to MDC_PART_PHD_DM MDC_CONC_GLU_RATE_THRESHOLDS

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Rate of Decrease and Increase Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
        2. ii. Field: Op Code – Response Codes
          1. Format: 8 bit
          2. Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)
        3. iii. Field: Operand
          1. Format: SFLOAT (mg/dL/min)
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Rate of Decrease Alert Level procedure using Op Code “Get Rate of Decrease Alert Level” (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    | | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    5. The simulated PHD will respond with an indication including a “Rate of Decrease Alert Level Response” (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.

    6. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    7. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.

    8. Check in the PHG transcoder output the Glucose rate of charge thresholds Compound Numeric Object – Type attribute

    | +| Pass/Fail criteria | In Step 8, the Glucose rate of charge thresholds Compound Numeric Object – Type attribute is present and set to MDC_PART_PHD_DM MDC_CONC_GLU_RATE_THRESHOLDS | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: Glucose rate of charge thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_CONC_GLU_RATE_THRESHOLDS or 29412 (dec) or 72 E4 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segments like this with Type attribute (check OBX-3):

    OBX n 8391520^MDC_CONC_GLU_RATE_THRESHOLDS^MDC
    m.0.x.0 X [date_time]

    | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-059_A | | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object - Metric-Spec-Small Attribute 1 | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 3; M | GRCNumeric 5; M | +| Test purpose |

    Check that:

    PHG includes Glucose rate of charge thresholds Compound Numeric Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0x604C} when the rate of change thresholds were updated manually by the user.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Rate of Decrease and Increase Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
    | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: 24 bit
    • Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
    • ii. Field: CGM Type
      • Format: 4 bit
      • Value: not relevant
    • iii. Field: CGM Sample Location
      • Format: 4 bit
      • Value: not relevant
    • iv. Field: E2E-CRC
      • Format: uint16
      • Value: not relevant

    b. CGM Specific Ops Control Point (0x2AAC)

    • i. Field: Op Code
      • Format: uint8
    • ii. Field: Op Code – Response Codes
      • Format: 8 bit
      • Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)
    • iii. Field: Operand
      • Format: SFLOAT (mg/dL/min)
      • Value: not relevant
    • iv. Field: E2E-CRC
      • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Rate of Decrease Alert Level procedure using Op Code “Get Rate of Decrease Alert Level” (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 5. The simulated PHD will respond with an indication including a “Rate of Decrease Alert Level Response” (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    4. 6. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    5. 7. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    6. 8. Check in the PHG transcoder output the Glucose rate of charge thresholds Compound Numeric Object – Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 8, the Patient low/high thresholds Compound Numeric Object – Metric-Spec-Small attribute is present and its value is {0x604C} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-manual mss-cat-setting) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Glucose rate of charge thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    | + +| | | +|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Attribute-type: BITS-16
    • Attribute-value: 60 4C (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-manual(12), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE
    | +| b) | WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-059_B | | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object - Metric-Spec-Small Attribute 2 | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 3; M | GRC Numeric 4; M | +| Test purpose | Check that:
    PHG includes Glucose rate of charge thresholds Compound Numeric Object – Metric-Spec-Small attribute in transcoder output.
    [AND]
    Metric-Spec-Small is set to {0x6044} when the Rate of Increase/Decrease Alert Level procedure has been executed | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 AND C_MAN_BLE_053 AND C_MAN_BLE_055 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization).
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
          • Value: not relevant
        4. iv. Field: E2E-CRC
          • Format: uint16
          • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • Format: uint8
        2. ii. Field: Op Code – Response Codes
          • Format: 8 bit
          • Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)
    | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    iii. Field: Operand

    • Format: SFLOAT (mg/dL/min)
    • Value: not relevant

    iv. Field: E2E-CRC

    • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    3. 5. Force the PHG to set the Rate of Decrease Alert Level by performing a Rate of Decrease Alert Level procedure using Op Code “Set Rate of Decrease Alert Level” (0x13) followed by a valid SFLOAT value (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Operand fields respectively). The simulated PHD will respond with an indication including a Response Op Code value of “Success”.
    4. 6. Force the PHG to set the Rate of Increase Alert Level by performing a Rate of Increase Alert Level procedure using Op Code “Set Rate of Increase Alert Level” (0x16) followed by a valid SFLOAT value (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Operand fields respectively). The simulated PHD will respond with an indication including a Response Op Code value of “Success”.
    5. 7. Then, force the PHG to perform a Rate of Decrease Alert Level procedure using Op Code “Get Rate of Decrease Alert Level” (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    6. 8. The simulated PHD will respond with an indication including a “Rate of Decrease Alert Level Response” (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    7. 9. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    8. 10. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    9. 11. Check in the PHG transcoder output the Glucose rate of charge thresholds Compound Numeric Object – Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 11, the Glucose rate of charge thresholds Compound Numeric Object – Metric-Spec-Small attribute is present and its value is {0x6044} (mss-avail-stored-data mss-upd-aperiodic mss-acc-agent-initiated mss-cat-setting) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: Glucose rate of charge thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: 60 44 (hex) or BITS mss-avail-stored-data (1), mss-upd-aperiodic(2), mss-acc-agent-initiated(9), mss-cat-setting(13) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-060 | | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object – Metric-Structure-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 6; M | | +| Test purpose |

    Check that:

    PHG includes Glucose rate of charge thresholds Compound Numeric Object – Metric-Structure-Small attribute in transcoder output.

    [AND]

    Metric-Structure-Small is set to {0x40, 0x02}

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Rate of Decrease and Increase Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)
        2. ii. Field: Operand
          1. Format: SFLOAT (mg/dL/min)
          2. Value: not relevant
        3. iii. Field: E2E-CRC
          1. This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Rate of Decrease Alert Level
    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    procedure using Op Code “Get Rate of Decrease Alert Level” (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    1. 5. The simulated PHD will respond with an indication including a “Rate of Decrease Alert Level Response” (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    2. 6. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 7. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    4. 8. Check in PHG transcoder output the Glucose rate of charge thresholds Compound Numeric Object – Metric-Structure-Small attribute
    | +| Pass/Fail criteria | In Step 8, the Glucose rate of charge thresholds Compound Numeric Object – Metric-Structure-Small attribute is present and set to 0x40 (ms-struct-compound), 0x02 (number of components is 2) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Structure-Small attribute is present:

    • Object: Glucose rate of charge thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_METRIC_STRUCT_SMALL (2675)
    • Attribute-type: SEQUENCE {ms-struct (INT-U8), ms-comp-no (INT-U8)}
    • Attribute-value:
      • • ms-struct: 0x40 (ms-struct-compound)
      • • ms-comp-no: 0x02 (number of components)

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Structure-Small attribute value

    | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-061 | | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object – Metric-Id-List Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 7; M | | +| Test purpose |

    Check that:

    PHG includes Glucose rate of charge thresholds Compound Numeric Object – Metric-Id-List attribute in transcoder output.

    [AND]

    Metric-Id-List is set to { 0x0002, 0x0004, MDC_CONC_GLU_RATE_THRESHOLD_INCREASE, MDC_CONC_GLU_RATE_THRESHOLD_DECREASE }

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Rate of Decrease and Increase Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
    | | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. i. Field: CGM Feature
      • Format: 24 bit
      • Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
    2. ii. Field: CGM Type
      • Format: 4 bit
      • Value: not relevant
    3. iii. Field: CGM Sample Location
      • Format: 4 bit
      • Value: not relevant
    4. iv. Field: E2E-CRC
      • Format: uint16
      • Value: not relevant

    b. CGM Specific Ops Control Point (0x2AAC)

    1. i. Field: Op Code
      • Format: uint8
      • Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)
    2. ii. Field: Operand
      • Format: SFLOAT (mg/dL/min)
      • Value: not relevant
    3. iii. Field: E2E-CRC
      • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Rate of Decrease Alert Level procedure using Op Code “Get Rate of Decrease Alert Level” (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 5. The simulated PHD will respond with an indication including a “Rate of Decrease Alert Level Response” (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    4. 6. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    5. 7. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    6. 8. Check in PHG transcoder output the Glucose rate of charge thresholds Compound Numeric Object – Metric-Id-List attribute
    | +| Pass/Fail criteria | In Step 8, the Glucose rate of charge thresholds Compound Numeric Object – Metric-Id-List attribute is present and set to 0x0002 (count of metric ids is 2), 0x0004 (list length is 4 octets), MDC_CONC_GLU_RATE_THRESHOLD_INCREASE, MDC_CONC_GLU_RATE_THRESHOLD_DECREASE | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Id-List attribute is present:

    • Object: Glucose rate of charge thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_ID_PHYSIO_LIST (2678)
    • Attribute-type: SEQUENCE OF {OID-Type(INT-U16)}
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Attribute-value: 0x0002 (number of elements), 0x0004 (length of the sequence), followed by

    • • First element: MDC_CONC_GLU_RATE_THRESHOLD_INCREASE (0x72E5)
    • • Second element: MDC_CONC_GLU_RATE_THRESHOLD_DECREASE (0x72E6)

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these with Metric-Id-List attribute values (check OBX-3 in both segments):

    OBX n NM 8391521^MDC_CONC_GLU_RATE_THRESHOLD_INCREASE^MDC  m.0.x.a [value] 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC    R
    OBX n NM 8391522^MDC_CONC_GLU_RATE_THRESHOLD_DECREASE^MDC  m.0.x.b [value] 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC    R
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-062 | | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object – Unit-Code Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 8; M | | +| Test purpose |

    Check that:

    PHG includes Glucose rate of charge thresholds Compound Numeric Object – Unit-Code attribute in transcoder output.

    [AND]

    Unit-Code is set to MDC_DIM_MILLI_G_PER_DL_PER_MIN

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Rate of Decrease and Increase Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
        2. ii. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. iii. Field: CGM Sample Location
          • Format: 4 bit
          • Value: not relevant
        4. iv. Field: E2E-CRC
          • Format: uint16
          • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
    | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • i. Field: Op Code
      • Format: uint8
      • Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)
    • ii. Field: Operand
      • Format: SFLOAT (mg/dL/min)
      • Value: not relevant
    • iii. Field: E2E-CRC
      • This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Rate of Decrease Alert Level procedure using Op Code “Get Rate of Decrease Alert Level” (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    5. The simulated PHD will respond with an indication including a “Rate of Decrease Alert Level Response” (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.

    6. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    7. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.

    8. Check in PHG transcoder output the Glucose rate of charge thresholds Compound Numeric Object – Unit-Code attribute

    | +| Pass/Fail criteria | In Step 8, the Glucose rate of charge thresholds Compound Numeric Object – Unit-Code attribute is present and set to MDC_DIM_MILLI_G_PER_DL_PER_MIN | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Unit-Code attribute is present:

    • Object: Glucose rate of charge thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_UNIT_CODE (2454)
    • Attribute-type: OID-Type
    • Attribute-value: MDC_DIM_MILLI_G_PER_DL_PER_MIN or 4724 (dec) or 0x1274 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these with Unit-Code attribute value (check OBX-6 in both segments):

    OBX n NM 8391521^MDC_CONC_GLU_RATE_THRESHOLD_INCREASE^MDC
    m.0.x.a [value] 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC R

    OBX n NM 8391522^MDC_CONC_GLU_RATE_THRESHOLD_DECREASE^MDC
    m.0.x.b [value] 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC R

    | + +| | | | | +|-----------------|----------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-063 | | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object – Base-Offset-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 9; M | BaseOffset 1; M | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose |

    Check that:

    PHG includes Glucose rate of change thresholds Compound Numeric Object – Base-Offset-Time-Stamp Attribute

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation (Base-Offset-Time-Stamp attribute will be derived from the collector's time at the time of collection)

    | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Rate of Decrease and Increase Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          1. Format: 24 bit
          2. Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
        2. ii. Field: CGM Type
          1. Format: 4 bit
          2. Value: not relevant
        3. iii. Field: CGM Sample Location
          1. Format: 4 bit
          2. Value: not relevant
        4. iv. Field: E2E-CRC
          1. Format: uint16
          2. Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          1. Format: uint8
          2. Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)
        2. ii. Field: Operand
          1. Format: SFLOAT (mg/dL/min)
          2. Value: not relevant
        3. iii. Field: E2E-CRC
          1. This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Rate of Decrease Alert Level procedure using Op Code "Get Rate of Decrease Alert Level" (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    5. 5. The simulated PHD will respond with an indication including a "Rate of Decrease Alert Level Response" (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    6. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    7. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.

    8. Check in the PHG transcoder output the Glucose rate of charge thresholds Compound Numeric Object – Base-Offset-Time-Stamp attribute

    | +| Pass/Fail criteria | In Step 8, the Glucose rate of charge thresholds Compound Numeric Object – Base-Offset-Time-Stamp attribute is present and it is set to the collector’s time at the time of collection. | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Base-Offset-Time-Stamp attribute is present:

    • Object: Glucose rate of charge thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
    • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
    • Attribute-value: collector’s time at the time of collection.

    b) WAN PCD-01 message

    PCD-01 message includes a segments like this with Base-Offset-Time-Stamp attribute (check OBX-14):

    OBX[n][8391520^MDC_CONC_GLU_RATE_THRESHOLDS^MDC m.0.x.0] X
    value described in a) coded in DTM format]

    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-064 | | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | GRC Numeric 10; M | | +| Test purpose |

    Check that:

    PHG includes Glucose rate of charge thresholds Compound Numeric Object Compound-Basic-Nu-Observed-Value attribute in transcoder output.

    [AND]

    Compound-Basic-Nu-Observed-Value attribute is set to the correct value.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Rate of Decrease and Increase Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
        2. ii. Field: CGM Type
    | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Format: 4 bit
    • Value: not relevant

    iii. Field: CGM Sample Location

    • Format: 4 bit
    • Value: not relevant

    iv. Field: E2E-CRC

    • Format: uint16
    • Value: not relevant

    b. CGM Specific Ops Control Point (0x2AAC)

    i. Field: Op Code

    • Format: uint8
    • Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)

    ii. Field: Operand

    • Format: SFLOAT (mg/dL/min)
    • Value: 9.0 (Rate of Decrease Alert Level Response) / 9.0 (Rate of Increase Alert Level Response)

    iii. Field: E2E-CRC

    • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Rate of Decrease Alert Level procedure using Op Code “Get Rate of Decrease Alert Level” (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    3. 5. The simulated PHD will respond with an indication including a “Rate of Decrease Alert Level Response” (0x15) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    4. 6. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    5. 7. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    6. 8. Check in PHG transcoder output the Glucose rate of charge thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute
    | +| Pass/Fail criteria | In Step 8, the Glucose rate of charge thresholds Compound Numeric Object – Compound-Basic-Nu-Observed-Value attribute is set to 0x0002 (count of components is 2), 0x0004 (component list length is 4 octets), the Rate of Increase Alert Level Response Operand followed by the Rate of Decrease Alert Level Response Operand | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Compound-Basic-Nu-Observed-Value attribute is present:

    • Object: Glucose rate of charge thresholds Compound Numeric Object
    • Attribute-id: MDC_ATTR_NU_CMPD_VAL_OBS_BASIC (2677)
    • Attribute-type: SEQUENCE OF {[SFLOAT]}
    • Attribute-value: 0x0002 (number of elements), 0x0004 (length of the sequence), followed by
      • • First element (Rate of Increase Alert Level Response Operand): 00 09 (hex) or F0 5A (hex) or E3 84 (hex) or 9.0 (dec)
    | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • Second element (Rate of Decrease Alert Level Response Operand): 00 09 (hex) or F0 5A (hex) or E3 84 (hex) or 9.0 (dec)

    b) WAN PCD-01 message

    PCD-01 message includes two segments like these with Compound-Basic-Nu-Observed-Value attribute value (check OBX-5 in both segments):

    OBX n NM 8391521^MDC_CONC_GLU_RATE_THRESHOLD_INCREASE^MDC m.0.x.a 9.0 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC    R
    OBX n NM 8391522^MDC_CONC_GLU_RATE_THRESHOLD_DECREASE^MDC m.0.x.b 9.0 266868^MDC_DIM_MILLI_G_PER_DL_PER_MIN^MDC    R
    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-065 | | | +| TP label | Whitepaper. PHD DM Status Enumeration Object - Handle Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PHDM Enumeration 1; O | | +| Test purpose |

    Check that:

    PHG does not include PHD DM Status Enumeration Object – Handle Attribute in transcoder output.

    [OR]

    If PHG includes PHD DM Status Enumeration Object – Handle attribute in transcoder output, then its value shall be different than 0

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. CGM Feature (0x2AA8)
        1. Field: CGM Feature
          • Format: 24 bit
          • Value: 0000 0000 0000 1010 0000 0000 (MSB → LSB). Low Battery detection supported, General Device Fault supported.
        2. Field: CGM Type
          • Format: 4 bit
          • Value: not relevant
        3. Field: CGM Sample Location
          • Format: 4 bit
          • Value: not relevant
        4. Field: E2E-CRC
          • Format: uint16
          • Value: not relevant
      2. CGM Status (0x2AA8)
        1. Field: Time Offset
          • Format: uint16
    | | | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant.
    • ii. Field: CGM Status
      • • Format: 24 bit
      • • Value: not relevant
    • iii. Field: E2E-CRC
      • • This field is not included
    • c. CGM Measurement (0x2AA7)
      • i. Field: Size
        • • Format: uint8
      • ii. Field: Flags
        • • Format: 8 bit
        • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
      • iii. Field: CGM Glucose Concentration (mg/dL)
        • • Format: SFLOAT
        • • Value: not Relevant
      • iv. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant
      • v. Field: Sensor Status Annunciation
        • • Format: 8 bit
        • • Value: not relevant
      • vi. Field: CGM Trend Information (mg/dL)
        • • This field is not included
      • vii. Field: CGM Quality
        • • This field is not included
      • viii. Field: E2E-CRC
        • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    3. 5. The simulated PHD sends the Measurement to PHG under test
    4. 6. Check in the PHG transcoder output the PHD DM Status Enumeration Object– Handle attribute
    5. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test
    6. 8. Check in the PHG transcoder output the PHD DM Status Enumeration Object – Handle attribute
    7. 9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.
    8. 10. Check in the PHG transcoder output the PHD DM Status Enumeration Object – Handle attribute
    | +| Pass/Fail criteria | In Step 6, 8 and 10, the PHD DM Status Enumeration Object – Handle attribute is not present or, if it is present then its value is different than 0 | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Handle attribute is not present, or if it is present then:

    • Object: PHD DM Status Enumeration Object
    • Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    • Attribute-type: INT-U16
    • Attribute-value: Any value different than 0

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Handle attribute value

    | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-066 | | | +| TP label | Whitepaper. PHD DM Status Enumeration Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PHDM Enumeration 2; M | | +| Test purpose |

    Check that:

    PHG includes PHD DM Status Enumeration Object – Type attribute in transcoder output.

    [AND]

    Type is set to MDC_PART_PHD_DM MDC_PHD_DM_DEV_STAT

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 1010 0000 0000 (MSB → LSB). Low Battery detection supported, General Device Fault supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Status (0x2AA8)
        1. i. Field: Time Offset
          • • Format: uint16
    | | | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant.
    1. ii. Field: CGM Status
      • • Format: 24 bit
      • • Value: not relevant
    2. iii. Field: E2E-CRC
      • • This field is not included
    1. c. CGM Measurement (0x2AA7)
      1. i. Field: Size
        • • Format: uint8
      2. ii. Field: Flags
        • • Format: 8 bit
        • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
      3. iii. Field: CGM Glucose Concentration (mg/dL)
        • • Format: SFLOAT
        • • Value: not Relevant
      4. iv. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant
      5. v. Field: Sensor Status Annunciation
        • • Format: 8 bit
        • • Value: not relevant
      6. vi. Field: CGM Trend Information (mg/dL)
        • • This field is not included
      7. vii. Field: CGM Quality
        • • This field is not included
      8. viii. Field: E2E-CRC
        • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    3. 5. The simulated PHD sends the Measurement to the PHG under test.
    4. 6. Check in PHG transcoder output the PHD DM Status Enumeration Object– Type attribute
    5. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test
    6. 8. Check in the PHG transcoder output the PHD DM Status Enumeration Object – Type attribute
    7. 9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.
    8. 10. Check in the PHG transcoder output the PHD DM Status Enumeration Object – Type attribute
    | +| Pass/Fail criteria | In Step 6, 8 and 10, the PHD DM Status Enumeration Object – Type attribute is present and its value is MDC_PART_PHD_DM MDC_PHD_DM_DEV_STAT | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is present:

    • Object: PHD DM Status Enumeration Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • • code: MDC_PHD_DM_DEV_STAT or 20000 (dec) or 4E 20 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segments like this with Type attribute (check OBX-3):

    OBX[n CWE 8408608^MDC_PHD_DM_DEV_STAT^MDC
    m.0.0.a value ] R date_time

    | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-067 | | | +| TP label | Whitepaper. PHD DM Status Enumeration Object - Supplemental-Types Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PHDM Enumeration 3; O | | +| Test purpose |

    Check that:

    PHG may include PHD DM Status Enumeration Object – Supplemental-Types attribute in transcoder output.

    [AND]

    If present, Supplemental-Types is set to a correct value

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 1010 0000 0000 (MSB → LSB). Low Battery detection supported, General Device Fault supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
    | | | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant

    b. CGM Status (0x2AA8)

    • i. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant.
    • ii. Field: CGM Status
      • • Format: 24 bit
      • • Value: not relevant
    • iii. Field: E2E-CRC
      • • This field is not included

    c. CGM Measurement (0x2AA7)

    • i. Field: Size
      • • Format: uint8
    • ii. Field: Flags
      • • Format: 8 bit
      • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
    • iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: not Relevant
    • iv. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant
    • v. Field: Sensor Status Annunciation
      • • Format: 8 bit
      • • Value: not relevant
    • vi. Field: CGM Trend Information (mg/dL)
      • • This field is not included
    • vii. Field: CGM Quality
      • • This field is not included
    • viii. Field: E2E-CRC
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.

    5. The simulated PHD sends the Measurement to the PHG under test.

    6. Check in the PHG transcoder output the PHD DM Status Enumeration Object–Supplemental-Types attribute

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    8. Check in the PHG transcoder output the PHD DM Status Enumeration Object – Supplemental-Types attribute

    9. Force the PHG under test to read the CGM Status characteristic to actively request the

    | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | status of the CGM sensor.
    10. Check in the PHG transcoder output the PHD DM Status Enumeration Object – Supplemental-Types attribute | +| Pass/Fail criteria | In Step 6, 8 and 10, the PHD DM Status Enumeration Object – Supplemental-Types attribute may be present. If present, it is set to one of the following values:
    MDC_CGM_DEV_TYPE_SENSOR, MDC_CGM_DEV_TYPE_TRANSMITTER, MDC_CGM_DEV_TYPE_RECEIVER, or MDC_CGM_DEV_TYPE_OTHER | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Supplemental-Types attribute may be present. If it is present:

    • Object: PHD DM Status Enumeration Object
    • Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)
    • Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex) followed by one of:
      • • code: MDC_CGM_DEV_TYPE_SENSOR or 29460 (dec) or 73 14 (hex)
      • • code: MDC_CGM_DEV_TYPE_TRANSMITTER or 29461 (dec) or 73 15 (hex)
      • • code: MDC_CGM_DEV_TYPE_RECEIVER or 29462 (dec) or 73 16 (hex)
      • • code: MDC_CGM_DEV_TYPE_OTHER or 29463 (dec) or 73 17 (hex)

    b) WAN PCD-01 message

    If Supplemental-Types attribute is present, PCD-01 message includes a facet OBX segment of the PHD DM Status OBX segment with Supplemental-Types attribute (check OBX-3 and OBX-5):

    OBX[n]CWE 8408608^MDC_PHD_DM_DEV_STAT^MDC  m.0.0.a [value]     R  [date_time]

    The following facet OBX segments are allowed:

    OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.a.y  8418068^MDC_CGM_DEV_TYPE_SENSOR^MDC     R
    OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.a.y  8418069^MDC_CGM_DEV_TYPE_TRANSMITTER^MDC     R
    OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.a.y  8418070^MDC_CGM_DEV_TYPE_RECEIVER^MDC     R
    OBX[n]CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.a.y  8418071^MDC_CGM_DEV_TYPE_OTHER^MDC     R
    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-068 | | | +| TP label | Whitepaper. PHD DM Status Enumeration Object – Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PHDM Enumeration 4; M | | +| Test purpose |

    Check that:

    PHG includes PHD DM Status Enumeration Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    Metric-Spec-Small is set to {0xF040}.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | + +| | | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

    Test procedure

    |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 1010 0000 0000 (MSB → LSB). Low Battery detection supported, General Device Fault supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Status (0x2AA8)
        1. i. Field: Time Offset
          • • Format: uint16
          • • Value: not relevant.
        2. ii. Field: CGM Status
          • • Format: 24 bit
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not included
      3. c. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
          • • Value: not relevant
        4. iv. Field: Time Offset
          • • Format: uint16
          • • Value: not relevant
        5. v. Field: Sensor Status Annunciation
          • • Format: 8 bit
    | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant

    vi. Field: CGM Trend Information (mg/dL)

    • • This field is not included

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    3. 5. The simulated PHD sends the Measurement to the PHG under test.
    4. 6. Check in the PHG transcoder output the PHD DM Status Enumeration Object– Metric-Spec-Small attribute
    5. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    6. 8. Check in the PHG transcoder output the PHD DM Status Enumeration Object – Metric-Spec-Small attribute
    7. 9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.
    8. 10. Check in PHG transcoder output the PHD DM Status Enumeration Object – Metric-Spec-Small attribute
    | +| Pass/Fail criteria | In Step 6, 8 and 10, the PHD DM Status Enumeration Object – Metric-Spec-Small attribute is present and its value is 0xF040 (mss-avail-intermittent mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-avail-stored-data) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: PHD DM Status Enumeration Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: F0 40 (hex) or BITS mss-avail-intermittent (0), mss-avail-stored-data (1), mss-upd-aperiodic (2), mss-msmt-aperiodic (3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-069 | | | +| TP label | Whitepaper. PHD DM Status Enumeration Object – Base-Offset-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PHDM Enumeration 5; M | BaseOffset 3; M | +| Test purpose |

    Check that:

    PHG includes PHD DM Status Enumeration Object Base-Offset-Time-Stamp attribute in transcoder output.

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation

    | | | + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 1010 0000 0000 (MSB → LSB). Low Battery detection supported, General Device Fault supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Status (0x2AA8)
        1. i. Field: Time Offset
          • • Format: uint16
          • • Value: 5 (min)
        2. ii. Field: CGM Status
          • • Format: 24 bit
          • • Value: not relevant
        3. iii. viii. Field: E2E-CRC
          • • This field is not included
      3. c. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
          • • Value: not Relevant
        4. iv. Field: Time Offset
          • • Format: uint16
    | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 20 (min)

    v. Field: Sensor Status Annunciation

    • • Format: 8 bit
    • • Value: not relevant

    vi. Field: CGM Trend Information (mg/dL)

    • • This field is not included

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included

    d. CGM Session Start Time (0x2AAA)

    i. Field: Session Start Time

    • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
    • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)

    ii. Field: Time Zone

    • • Format: sint8
    • • Value: 4 (UTC+1:00)

    iii. Field: DST-Offset

    • • Format: uint8
    • • Value: 4 (Daylight Time (+1h))

    iv. Field: E2E-CRC

    • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    3. 5. The simulated PHD sends the Measurement to the PHG under test.
    4. 6. Check in the PHG transcoder output PHD DM Status Enumeration Object – Base-Offset-Time-Stamp attribute.
    5. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    6. 8. Check in the PHG transcoder output the PHD DM Status Enumeration Object - Base-Offset-Time-Stamp attribute.
    7. 9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.
    8. 10. Check in the PHG transcoder output the PHD DM Status Enumeration Object - Base-Offset-Time-Stamp attribute.
    | +| Pass/Fail criteria |
    • • In Step 6 and 8 the PHD DM Status Enumeration Object - Base-Offset-Time-Stamp attribute is present and set is to the addition of CGM Session Start Time characteristic's Session Start Time field (May 12, 2016, 16:39:27) plus CGM Measurement characteristic's Time Offset field (20 min).
    • • In Step 10 the PHD DM Status Enumeration Object - Base-Offset-Time-Stamp attribute is present and set is to the addition of CGM Session Start Time characteristic's Session Start Time field (May 12, 2016, 16:39:27) plus CGM Status characteristic's Time Offset field (5 min).
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Base-Offset-Time-Stamp attribute is present:

    • Object: PHD DM Status Enumeration Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
    • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
    • Attribute-value: addition of
      • • CGM Session Start Time characteristic Session Start Time field (May 12, 2016, 16:39:27)
      • • Steps 6 & 8
        CGM Measurement characteristic Time Offset field (20m)
      • • Steps 10
        CGM Status characteristic Time Offset field (5m)

    Note that the same Base-Offset-Time-Stamp can have different representations depending on bo-time-offset value. If it is set to 20 min (CGM Measurement or CGM Status characteristic Time Offset field), then Base-Offset-Time-Stamp value shall be {3672059967, 0, 20} or {3672059967, 0, 5}

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Base-Offset-Time-Stamp attribute value (check OBX-14):

    OBX n CWE 8408608^MDC_PHD_DM_DEV_STAT^MDC m.0.0.a [value] R [value described in a) coded in DTM format]

    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-070 | | | +| TP label | Whitepaper. PHD DM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | PHDM Enumeration 6; M | | +| Test purpose |

    Check that:

    PHG includes PHD DM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute in transcoder output.

    [AND]

    Enum-Observed-Value-Simple-Bit-Str is set to the correct value.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 1010 0000 0000 (MSB → LSB). Low Battery detection supported, General Device Fault supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant
    1. iii. Field: CGM Sample Location
      • • Format: 4 bit
      • • Value: not relevant
    2. iv. Field: E2E-CRC
      • • Format: uint16
      • • Value: not relevant
    1. b. CGM Status (0x2AA8)
      1. i. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant.
      2. ii. Field: CGM Status
        • • Format: 24 bit
        • • Value: 0000 0000 0000 0000 0000 0010 (MSB -> LSB). Device Battery Low.
      3. iii. Field: E2E-CRC
        • • Format: uint16
        • • Value: not relevant
    2. c. CGM Measurement (0x2AA7)
      1. i. Field: Size
        • • Format: uint8
      2. ii. Field: Flags
        • • Format: 8 bit
        • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
      3. iii. Field: CGM Glucose Concentration (mg/dL)
        • • Format: SFLOAT
        • • Value: not Relevant
      4. iv. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant
      5. v. Field: Sensor Status Annunciation
        • • Format: 8 bit
        • • Value: 0000 0010 (MSB -> LSB). Device Battery Low.
      6. vi. Field: CGM Trend Information (mg/dL)
        • • This field is not included
      7. vii. Field: CGM Quality
        • • This field is not included
      8. viii. Field: E2E-CRC
        • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.

    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +5. The simulated PHD sends the Measurement to the PHG under test. +6. Check in PHG transcoder output the PHD DM Status Enumeration Object– Enum-Observed-Value-Simple-Bit-Str attribute +7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test. +8. Check in the PHG transcoder output the PHD DM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute +9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor. +10. Check in the PHG transcoder output the PHD DM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute +11. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + - a. CGM Status (0x2AA8) + - i. Field: CGM Status + - Format: 24 bit + - Value: 0000 0000 0000 0000 0010 0000 (MSB -> LSB). General device fault has occurred in the sensor. + - b. CGM Measurement (0x2AA7) + - i. Field: Flags + - Format: 8 bit + - Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present. + - ii. Field: Sensor Status Annunciation + - Format: 8 bit + - Value: 0010 0000 (MSB -> LSB). General device fault has occurred in the sensor. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the PHD DM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. +12. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + - a. CGM Status (0x2AA8) + - i. Field: CGM Status + - Format: 24 bit + - Value: 0000 0000 0000 0001 0000 0000 (MSB -> LSB). Time synchronization between sensor and collector required. + - b. CGM Measurement (0x2AA7) + - i. Field: Flags + - Format: 8 bit + - Value: 0100 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) present, Sensor Status Annunciation Field (Status-Octet) not present. + - ii. Field: Sensor Status Annunciation + - Format: 8 bit + - Value: 0000 0001 (MSB -> LSB). Time synchronization between sensor and collector required. + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the PHD DM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. | +| Pass/Fail criteria |
    • In Step 6, 8 and 10, the PHD DM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 25 set to 1 (device-status-battery-low). Rest of bits set to 0.
    • In Step 11, the PHD DM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 5 set to 1 (device-status-error). Rest of bits set to 0.
    • In Step 12, the PHD DM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 16 set to 1 (device-status-service-time-sync-required). Rest of bits set to 0.
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-Bit-Str attribute is present:

    • Object: PHD DM Status Enumeration Object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR (2661)
    • Attribute-type: BITS-32
    • Attribute-value (Steps 6,8,10): 02 00 00 00 (hex)
    • Attribute-value (Step 11): 00 00 00 20 (hex)
    • Attribute-value (Step 12): 00 00 01 00 (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Enum-Observed-Value-Basic-Bit-Str attribute value (check OBX-5):

    • Steps 6, 8 & 10
      OBX n CWE 8408608^MDC_PHD_DM_DEV_STAT^MDC m.0.0.a 1^device-status-battery-low(25) R [date_time]
    • Step 11
      OBX n CWE 8408608^MDC_PHD_DM_DEV_STAT^MDC m.0.0.a 1^device-status-error(5) R [date_time]
    • Step 12
      OBX n CWE 8408608^MDC_PHD_DM_DEV_STAT^MDC m.0.0.a 1^device-status-service-time-sync-required(16) R [date_time]
    | + +| | | | | | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-071 | | | | | +| TP label | Whitepaper. CGM Status Enumeration Object - Handle Attribute | | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | | +| | Testable items | CGM Enumeration 1; O | | | | +| Test purpose |

    Check that:

    PHG does not include CGM Status Enumeration Object – Handle Attribute in transcoder output.

    [OR]

    If PHG includes CGM Status Enumeration Object – Handle attribute in transcoder output, then its value shall be different than 0

    | | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | | | +| Other PICS | | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | | +| Test procedure |
    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising
    | | | | | + +state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored. + +2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: + +a. CGM Feature (0x2AA8) + +i. Field: CGM Feature + +- Format: 24 bit +- Value: 0000 0000 0000 0101 1011 1111 (MSB → LSB). Sensor Type Error Detection supported, Device Specific Alert supported, Calibration supported, Sensor Temperature High-Low Detection supported, Patient High/Low Alerts supported, Hypo Alerts supported, Hyper Alerts supported, Rate of Increase/Decrease Alerts supported, Sensor Result High-Low Detection supported. + +ii. Field: CGM Type + +- Format: 4 bit +- Value: not relevant + +iii. Field: CGM Sample Location + +- Format: 4 bit +- Value: not relevant + +iv. Field: E2E-CRC + +- Format: uint16 +- Value: not relevant + +b. CGM Status (0x2AA8) + +i. Field: Time Offset + +- Format: uint16 +- Value: not relevant. + +ii. Field: CGM Status + +- Format: 24 bit +- Value: not relevant + +iii. Field: E2E-CRC + +- This field is not included + +c. CGM Measurement (0x2AA7) + +i. Field: Size + +- Format: uint8 + +ii. Field: Flags + +- Format: 8 bit +- Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present. + +iii. Field: CGM Glucose Concentration (mg/dL) + +- Format: SFLOAT +- Value: not Relevant + +iv. Field: Time Offset + +- Format: uint16 +- Value: not relevant + +v. Field: Sensor Status Annunciation + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: 8 bit
    • • Value: not relevant
    vi. Field: CGM Trend Information (mg/dL)
    • • This field is not included
    vii. Field: CGM Quality
    • • This field is not included
    viii. Field: E2E-CRC
    • • This field is not included
    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    5. The simulated PHD sends the Measurement to the PHG under test.
    6. Check in PHG transcoder output CGM Status Enumeration Object - Handle attribute.
    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    8. Check in the PHG transcoder output the CGM Status Enumeration Object - Handle attribute.
    9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.
    10. Check in the PHG transcoder output the CGM Status Enumeration Object - Handle attribute. | +| Pass/Fail criteria | In Step 6, 8 and 10, the CGM Status Enumeration Object - Handle attribute is not present or, if it is present then its value is different than 0 | +| Notes
    (To assist manual testing)     | Possible values in typical points of observation after transcoder output are:
    a) IEEE 11073 Objects and Attributes
    Handle attribute is not present, or if it is present then:
    Object: CGM Status Enumeration Object
    Attribute-id: MDC_ATTR_ID_HANDLE (2337)
    Attribute-type: INT-U16
    Attribute-value: Any value different than 0
    b) WAN PCD-01 message
    PCD-01 message does not include segments with Handle attribute value | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-072 | | | +| TP label | Whitepaper. CGM Status Enumeration Object - Type Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | CGM Enumeration 2; M | | +| Test purpose | Check that:
    PHG includes CGM Status Enumeration Object – Type attribute in transcoder output.
    [AND]
    Type is set to MDC_PART_PHD_DM MDC_CGM_DEV_STAT | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0101 1011 1111 (MSB → LSB). Sensor Type Error Detection supported, Device Specific Alert supported, Calibration supported, Sensor Temperature High-Low Detection supported, Patient High/Low Alerts supported, Hypo Alerts supported, Hyper Alerts supported, Rate of Increase/Decrease Alerts supported, Sensor Result High-Low Detection supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Status (0x2AA8)
        1. i. Field: Time Offset
          • • Format: uint16
          • • Value: not relevant.
        2. ii. Field: CGM Status
          • • Format: 24 bit
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not included
      3. c. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
          • • Value: not Relevant
        4. iv. Field: Time Offset
          • • Format: uint16
          • • Value: not relevant
    | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    v. Field: Sensor Status Annunciation

    • Format: 8 bit
    • Value: not relevant

    vi. Field: CGM Trend Information (mg/dL)

    • This field is not included

    vii. Field: CGM Quality

    • This field is not included

    viii. Field: E2E-CRC

    • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.

    5. The simulated PHD sends the Measurement to the PHG under test.

    6. Check in the PHG transcoder output CGM Status Enumeration Object - Type attribute.

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    8. Check in the PHG transcoder output the CGM Status Enumeration Object - Type attribute.

    9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.

    10. Check in the PHG transcoder output the CGM Status Enumeration Object - Type attribute.

    | +| Pass/Fail criteria | In Step 6, 8 and 10, the CGM Status Enumeration Object - Type attribute is present and set to MDC_PART_PHD_DM MDC_CGM_DEV_STAT | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Type attribute is not present, or if it is present then:

    • Object: CGM Status Enumeration Object
    • Attribute-id: MDC_ATTR_ID_TYPE (2351)
    • Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}
    • Attribute-value:
      • partition: MDC_PART_PHD_DM or 128 (dec) or 00 80 (hex)
      • code: MDC_CGM_DEV_STAT or 29452 (dec) or 73 0C (hex)

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Type attribute (check OBX-3):

    OBX[n CWE 8418060^MDC_CGM_DEV_STAT^MDC  m.0.0.a [value]     R  [date_time]
    | + +| | | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-073 | | | +| TP label | Whitepaper. CGM Status Enumeration Object – Metric-Spec-Small Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | CGM Enumeration 3; M | | +| Test purpose |

    Check that:

    PHG includes CGM Status Enumeration Object – Metric-Spec-Small attribute in transcoder output.

    [AND]

    | | | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Metric-Spec-Small is set to {0x F040}. | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0101 1011 1111 (MSB → LSB). Sensor Type Error Detection supported, Device Specific Alert supported, Calibration supported, Sensor Temperature High-Low Detection supported, Patient High/Low Alerts supported, Hypo Alerts supported, Hyper Alerts supported, Rate of Increase/Decrease Alerts supported, Sensor Result High-Low Detection supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Status (0x2AA8)
        1. i. Field: Time Offset
          • • Format: uint16
          • • Value: not relevant.
        2. ii. Field: CGM Status
          • • Format: 24 bit
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not included
      3. c. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
    | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not Relevant

    iv. Field: Time Offset

    • • Format: uint16
    • • Value: not relevant

    v. Field: Sensor Status Annunciation

    • • Format: 8 bit
    • • Value: not relevant

    vi. Field: CGM Trend Information (mg/dL)

    • • This field is not included

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    3. 5. The simulated PHD sends the Measurement to the PHG under test.
    4. 6. Check in the PHG transcoder output CGM Status Enumeration Object – Metric-Spec-Small attribute.
    5. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    6. 8. Check in the PHG transcoder output the CGM Status Enumeration Object - Metric-Spec-Small attribute.
    7. 9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.
    8. 10. Check in the PHG transcoder output the CGM Status Enumeration Object - Metric-Spec-Small attribute.
    | +| Pass/Fail criteria | In Step 6, 8 and 10, the CGM Status Enumeration Object - Metric-Spec-Small attribute is present and set to 0xF040 (mss-avail-intermittent mss-upd-aperiodic mss-msmt-aperiodic mss-acc-agent-initiated mss-avail-stored-data) | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Metric-Spec-Small attribute is present:

    • Object: CGM Status Enumeration Object
    • Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)
    • Attribute-type: BITS-16
    • Attribute-value: 0xF040 (hex) or BITS mss-avail-intermittent (0), mss-avail-stored-data (1), mss-upd-aperiodic (2), mss-msmt-aperiodic(3), mss-acc-agent-initiated (9) set to TRUE and remaining BITS set to FALSE

    b) WAN PCD-01 message

    PCD-01 message does not include segments with Metric-Spec-Small attribute value

    | + +| | | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-074 | | | +| TP label | Whitepaper. CGM Status Enumeration Object – Base-Offset-Time-Stamp Attribute | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | CGM Enumeration 4; M | BaseOffset 3; M | +| Test purpose |

    Check that:

    PHG includes CGM Status Enumeration Object Base-Offset-Time-Stamp attribute in transcoder output.

    [AND]

    Base-Offset-Time-Stamp attribute is set to the correct value according to Base-Offset time stamp derivation

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0101 1011 1111 (MSB → LSB). Sensor Type Error Detection supported, Device Specific Alert supported, Calibration supported, Sensor Temperature High-Low Detection supported, Patient High/Low Alerts supported, Hypo Alerts supported, Hyper Alerts supported, Rate of Increase/Decrease Alerts supported, Sensor Result High-Low Detection supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Status (0x2AA8)
        1. i. Field: Time Offset
          • • Format: uint16
          • • Value: 5 (min)
        2. ii. Field: CGM Status
          • • Format: 24 bit
          • • Value: not relevant
        3. iii. Field: E2E-CRC
          • • This field is not included
      3. c. CGM Measurement (0x2AA7)
    | | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • i. Field: Size
      • • Format: uint8
    • ii. Field: Flags
      • • Format: 8 bit
      • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
    • iii. Field: CGM Glucose Concentration (mg/dL)
      • • Format: SFLOAT
      • • Value: not Relevant
    • iv. Field: Time Offset
      • • Format: uint16
      • • Value: 20 (min)
    • v. Field: Sensor Status Annunciation
      • • Format: 8 bit
      • • Value: not relevant
    • vi. Field: CGM Trend Information (mg/dL)
      • • This field is not included
    • vii. Field: CGM Quality
      • • This field is not included
    • viii. Field: E2E-CRC
      • • This field is not included

    d. CGM Session Start Time (0x2AAA)

    • i. Field: Session Start Time
      • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
      • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
    • ii. Field: Time Zone
      • • Format: sint8
      • • Value: 4 (UTC+1:00)
    • iii. Field: DST-Offset
      • • Format: uint8
      • • Value: 4 (Daylight Time (+1h))
    • iv. Field: E2E-CRC
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.

    5. The simulated PHD sends the Measurement to PHG under test.

    6. Check in the PHG transcoder output CGM Status Enumeration Object – Base-Offset-Time-Stamp attribute.

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.

    8. Check in the PHG transcoder output the CGM Status Enumeration Object - Base-Offset-Time-Stamp attribute.

    | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.

    10. Check in the PHG transcoder output the CGM Status Enumeration Object - Base-Offset-Time-Stamp attribute.

    | +| Pass/Fail criteria |
    • In Step 6 and 8 the CGM Status Enumeration Object - Base-Offset-Time-Stamp attribute is present and set is to the addition of CGM Session Start Time characteristic's Session Start Time (May 12, 2016, 14:39:27) field plus CGM Measurement characteristic's Time Offset field (20 min).
    • In Step 10 the CGM Status Enumeration Object - Base-Offset-Time-Stamp attribute is present and set is to the addition of CGM Session Start Time characteristic's Session Start Time (May 12, 2016, 14:39:27) field plus CGM Status characteristic's Time Offset field (5 min).
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Base-Offset-Time-Stamp attribute is present:

    • Object: CGM Status Enumeration Object
    • Attribute-id: MDC_ATTR_TIME_STAMP_BO (2690)
    • Attribute-type: SEQUENCE {bo-seconds (INT-U32), bo-fraction (INT-U16), bo-time-offset (INT-I16)}
    • Attribute-value: addition of
      • CGM Session Start Time characteristic Session Start Time field (May 12, 2016, 14:39:27)
      • Steps 6 & 8
        CGM Measurement characteristic Time Offset field (20m)
      • Step 10
        CGM Status characteristic Time Offset field (5m)

    Note that the same Base-Offset-Time-Stamp can have different representations depending on bo-time-offset value. If it is set to 20 min (CGM Measurement or CGM Status characteristic Time Offset field), then Base-Offset-Time-Stamp value shall be {3672059967, 0, 20} or {3672059967, 0, 5}

    b) WAN PCD-01 message

    PCD-01 message includes a segment like this with Base-Offset-Time-Stamp attribute value (check OBX-14):

    OBX n CWE 8418060^MDC_CGM_DEV_STAT^MDC m.0.0.a[[value] R [value described in a) coded in DTM format]

    | + +| | | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--|--| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-075 | | | | | +| TP label | Whitepaper. CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str | | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | | +| | Testable items | CGM Enumeration 4; M | | | | +| Test purpose |

    Check that:

    PHG includes CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute in transcoder output.

    [AND]

    Enum-Observed-Value-Simple-Bit-Str is set to the correct value.

    | | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | | | +| Other PICS | | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | | + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0101 1011 1111 (MSB → LSB). Sensor Type Error Detection supported, Device Specific Alert supported, Calibration supported, Sensor Temperature High-Low Detection supported, Patient High/Low Alerts supported, Hypo Alerts supported, Hyper Alerts supported, Rate of Increase/Decrease Alerts supported, Sensor Result High-Low Detection supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Status (0x2AA8)
        1. i. Field: Time Offset
          • • Format: uint16
          • • Value: 20 (min)
        2. ii. Field: CGM Status
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0000 0000 0001 (MSB -> LSB). Session stopped.
        3. iii. Field: E2E-CRC
          • • This field is not included
      3. c. CGM Measurement (0x2AA7)
        1. i. Field: Size
          • • Format: uint8
        2. ii. Field: Flags
          • • Format: 8 bit
          • • Value: 1000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present.
        3. iii. Field: CGM Glucose Concentration (mg/dL)
          • • Format: SFLOAT
          • • Value: not Relevant
        4. iv. Field: Time Offset
          • • Format: uint16
          • • Value: not relevant
    | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +- v. Field: Sensor Status Annunciation + - Format: 8 bit + - Value: 0000 0001 (MSB -> LSB). Session stopped. + - vi. Field: CGM Trend Information (mg/dL) + - This field is not included + - vii. Field: CGM Quality + - This field is not included + - viii. Field: E2E-CRC + - This field is not included +3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state). + 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics. + 5. The simulated PHD sends the Measurement to the PHG under test. + 6. Check in the PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute + 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test. + 8. Check in the PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute + 9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor. + 10. Check in the PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute + 11. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + - a. CGM Status (0x2AA8) + - i. Field: CGM Status + - Format: 24 bit + - Value: 0000 0000 0000 0000 0000 0100 (MSB -> LSB). Sensor type incorrect for device. + - b. CGM Measurement (0x2AA7) + - i. Field: Flags + - Format: 8 bit + - Value: 1000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present. + - ii. Field: Sensor Status Annunciation + - Format: 8 bit + - Value: 0000 0100 (MSB -> LSB). Sensor type incorrect for device. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object– Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + 12. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + - a. CGM Status (0x2AA8) + - i. Field: CGM Status + +- Format: 24 bit +- Value: 0000 0000 0000 0000 0000 1000 (MSB -> LSB). Sensor malfunction. + +#### b. CGM Measurement (0x2AA7) + +##### i. Field: Flags + +- Format: 8 bit +- Value: 1000 0000 (MSB -> LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present. + +##### ii. Field: Sensor Status Annunciation + +- Format: 8 bit +- Value: 0000 1000 (MSB -> LSB). Sensor malfunction. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +##### 13. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +#### a. CGM Status (0x2AA8) + +##### i. Field: CGM Status + +- Format: 24 bit +- Value: 0000 0000 0000 0000 0001 0000 (MSB -> LSB). Device specific alert. + +#### b. CGM Measurement (0x2AA7) + +##### i. Field: Flags + +- Format: 8 bit +- Value: 1000 0000 (MSB -> LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) present. + +##### ii. Field: Sensor Status Annunciation + +- Format: 8 bit +- Value: 0001 0000 (MSB -> LSB). Device specific alert. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +##### 14. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +#### a. CGM Status (0x2AA8) + +##### i. Field: CGM Status + +- Format: 24 bit +- Value: 0000 0000 0000 0010 0000 0000 (MSB -> LSB). Calibration not allowed. + +#### b. CGM Measurement (0x2AA7) + +##### i. Field: Flags + +- Format: 8 bit +- Value: 0100 0000 (MSB -> LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) present, Sensor Status Annunciation Field (Status-Octet) not present. + +##### ii. Field: Sensor Status Annunciation + +- Format: 8 bit +- Value: 0000 0010 (MSB -> LSB). Calibration not allowed. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +15. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +a. CGM Status (0x2AA8) + +i. Field: CGM Status + +- Format: 24 bit +- Value: 0000 0000 0000 0100 0000 0000 (MSB -> LSB). Calibration recommended. + +b. CGM Measurement (0x2AA7) + +i. Field: Flags + +- Format: 8 bit +- Value: 0100 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) present, Sensor Status Annunciation Field (Status-Octet) not present. + +ii. Field: Sensor Status Annunciation + +- Format: 8 bit +- Value: 0000 0100 (MSB -> LSB). Calibration recommended. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +16. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +a. CGM Status (0x2AA8) + +i. Field: CGM Status + +- Format: 24 bit +- Value: 0000 0000 0000 1000 0000 0000 (MSB -> LSB). Calibration required. + +b. CGM Measurement (0x2AA7) + +i. Field: Flags + +- Format: 8 bit +- Value: 0100 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) present, Sensor Status Annunciation Field (Status-Octet) not present. + +ii. Field: Sensor Status Annunciation + +- Format: 8 bit +- Value: 0000 1000 (MSB -> LSB). Calibration required. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +17. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +a. CGM Status (0x2AA8) + +i. Field: CGM Status + +- Format: 24 bit + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: 0000 0000 0001 0000 0000 0000 (MSB -> LSB). Sensor temperature too high for valid test/result at time of measurement.

    b. CGM Measurement (0x2AA7)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0100 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) present, Sensor Status Annunciation Field (Status-Octet) not present.
    • ii. Field: Sensor Status Annunciation
      • • Format: 8 bit
      • • Value: 0001 0000 (MSB -> LSB). Sensor temperature too high for valid test/result at time of measurement.

    The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10.

    18. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields:

    a. CGM Status (0x2AA8)

    • i. Field: CGM Status
      • • Format: 24 bit
      • • Value: 0000 0000 0010 0000 0000 0000 (MSB -> LSB). Sensor temperature too low for valid test/result at time of measurement.

    b. CGM Measurement (0x2AA7)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0100 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) present, Sensor Status Annunciation Field (Status-Octet) not present.
    • ii. Field: Sensor Status Annunciation
      • • Format: 8 bit
      • • Value: 0010 0000 (MSB -> LSB). Sensor temperature too low for valid test/result at time of measurement.

    The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10.

    19. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields:

    a. CGM Status (0x2AA8)

    • i. Field: CGM Status
      • • Format: 24 bit
      • • Value: 0000 0001 0000 0000 0000 0000 (MSB -> LSB). Sensor result lower than the patient low level.

    b. CGM Measurement (0x2AA7)

    • i. Field: Flags
      • • Format: 8 bit
      • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
    | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### ii. Field: Sensor Status Annunciation + +- Format: 8 bit +- Value: 0000 0001 (MSB -> LSB). Sensor result lower than the patient low level. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +20. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +#### a. CGM Status (0x2AA8) + +##### i. Field: CGM Status + +- Format: 24 bit +- Value: 0000 0010 0000 0000 0000 0000 (MSB -> LSB). Sensor result higher than the patient low level. + +#### b. CGM Measurement (0x2AA7) + +##### i. Field: Flags + +- Format: 8 bit +- Value: 0010 0000 (MSB -> LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present. + +##### ii. Field: Sensor Status Annunciation + +- Format: 8 bit +- Value: 0000 0010 (MSB -> LSB). Sensor result higher than the patient low level. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +21. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +#### a. CGM Status (0x2AA8) + +##### i. Field: CGM Status + +- Format: 24 bit +- Value: 0000 0100 0000 0000 0000 0000 (MSB -> LSB). Sensor result lower than the hypo level. + +#### b. CGM Measurement (0x2AA7) + +##### i. Field: Flags + +- Format: 8 bit +- Value: 0010 0000 (MSB -> LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present. + +##### ii. Field: Sensor Status Annunciation + +- Format: 8 bit +- Value: 0000 0100 (MSB -> LSB). Sensor result lower than the hypo level. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +22. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +- a. CGM Status (0x2AA8) + - i. Field: CGM Status + - Format: 24 bit + - Value: 0000 1000 0000 0000 0000 0000 (MSB -> LSB). Sensor result lower than the hyper level. +- b. CGM Measurement (0x2AA7) + - i. Field: Flags + - Format: 8 bit + - Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present. + - ii. Field: Sensor Status Annunciation + - Format: 8 bit + - Value: 0000 1000 (MSB -> LSB). Sensor result lower than the hyper level. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +23. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +- a. CGM Status (0x2AA8) + - i. Field: CGM Status + - Format: 24 bit + - Value: 0001 0000 0000 0000 0000 0000 (MSB -> LSB). Sensor rate of decrease exceeded. +- b. CGM Measurement (0x2AA7) + - i. Field: Flags + - Format: 8 bit + - Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present. + - ii. Field: Sensor Status Annunciation + - Format: 8 bit + - Value: 0001 0000 (MSB -> LSB). Sensor rate of decrease exceeded. + +The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10. + +24. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields: + +- a. CGM Status (0x2AA8) + - i. Field: CGM Status + - Format: 24 bit + - Value: 0010 0000 0000 0000 0000 0000 (MSB -> LSB). Sensor rate of increase exceeded. +- b. CGM Measurement (0x2AA7) + - i. Field: Flags + - Format: 8 bit + - Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    Quality not present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.

    ii. Field: Sensor Status Annunciation

    • • Format: 8 bit
    • • Value: 0010 0000 (MSB -> LSB). Sensor rate of increase exceeded.

    The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10.

    25. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields:

    a. CGM Status (0x2AA8)

    i. Field: CGM Status

    • • Format: 24 bit
    • • Value: 0100 0000 0000 0000 0000 0000 (MSB -> LSB). Sensor result lower than the device can process.

    b. CGM Measurement (0x2AA7)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.

    ii. Field: Sensor Status Annunciation

    • • Format: 8 bit
    • • Value: 0100 0000 (MSB -> LSB). Sensor result lower than the device can process.

    The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10.

    26. End current CGM session and start a new one. The simulated PHD will now have the following values in the specified fields:

    a. CGM Status (0x2AA8)

    i. Field: CGM Status

    • • Format: 24 bit
    • • Value: 1000 0000 0000 0000 0000 0000 (MSB -> LSB). Sensor result higher than the device can process.

    b. CGM Measurement (0x2AA7)

    i. Field: Flags

    • • Format: 8 bit
    • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.

    ii. Field: Sensor Status Annunciation

    • • Format: 8 bit
    • • Value: 1000 0000 (MSB -> LSB). Sensor result higher than the device can process.

    The rest of the fields will remain with the same value as in step 2. Repeat steps 3-10 to check in PHG transcoder output the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str attribute like in 6, 8 and 10.

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pass/Fail criteria |
    • • In Step 6, 8 and 10, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 0 set to 1 (sensor-session-stopped). Rest of bits set to 0.
    • • In Step 11, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 2 set to 1 (sensor-type-incorrect). Rest of bits set to 0.
    • • In Step 12, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 3 set to 1 (sensor-malfunction). Rest of bits set to 0.
    • • In Step 13, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 4 set to 1 (device-specific-alert). Rest of bits set to 0.
    • • In Step 14, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 7 set to 1 (sensor-calibration-not-allowed). Rest of bits set to 0.
    • • In Step 15, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 8 set to 1 (sensor-calibration-recommended). Rest of bits set to 0.
    • • In Step 16, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 9 set to 1 (sensor-calibration-required). Rest of bits set to 0.
    • • In Step 17, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 10 set to 1 (sensor-temp-too-high). Rest of bits set to 0.
    • • In Step 18, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 11 set to 1 (sensor-temp-too-low). Rest of bits set to 0.
    • • In Step 19, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 12 set to 1 (sensor-result-below-patient-low). Rest of bits set to 0.
    • • In Step 20, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 13 set to 1 (sensor-result-above-patient-high). Rest of bits set to 0.
    • • In Step 21, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 14 set to 1 (sensor-low-hypo). Rest of bits set to 0.
    • • In Step 22, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 15 set to 1 (sensor-high-hyper). Rest of bits set to 0.
    • • In Step 23, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 16 set to 1 (sensor-rate-decrease-exceeded). Rest of bits set to 0.
    • • In Step 24, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 17 set to 1 (sensor-rate-increase-exceeded). Rest of bits set to 0.
    • • In Step 25, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 18 set to 1 (sensor-result-too-low). Rest of bits set to 0.
    • • In Step 26, the CGM Status Enumeration Object – Enum-Observed-Value-Simple-Bit-Str is present with bit 19 set to 1 (sensor-result-too-high). Rest of bits set to 0.
    | +| Notes
    (To assist manual testing)     |

    Possible values in typical points of observation after transcoder output are:

    a) IEEE 11073 Objects and Attributes

    Enum-Observed-Value-Simple-Bit-Str attribute is present:

    • Object: PHD DM Status Enumeration Object
    • Attribute-id: MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR (2661)
    • Attribute-type: BITS-32
    • Attribute-value (Steps 6,8,10): 00 00 00 01 (hex)
    • Attribute-value (Step 11): 00 00 00 04 (hex)
    • Attribute-value (Step 12): 00 00 00 08 (hex)
    • Attribute-value (Step 13): 00 00 00 10 (hex)
    • Attribute-value (Step 14): 00 00 00 80 (hex)
    • Attribute-value (Step 15): 00 00 01 00 (hex)
    • Attribute-value (Step 16): 00 00 02 00 (hex)
    • Attribute-value (Step 17): 00 00 04 00 (hex)
    • Attribute-value (Step 18): 00 00 08 00 (hex)
    | + +- Attribute-value (Step 19): 00 00 10 00 (hex) +- Attribute-value (Step 20): 00 00 20 00 (hex) +- Attribute-value (Step 21): 00 00 40 00 (hex) +- Attribute-value (Step 22): 00 00 80 00 (hex) +- Attribute-value (Step 23): 00 01 00 00 (hex) +- Attribute-value (Step 24): 00 02 00 00 (hex) +- Attribute-value (Step 25): 00 04 00 00 (hex) +- Attribute-value (Step 26): 00 08 00 00 (hex) + +#### b) WAN PCD-01 message + +PCD-01 message includes a segment like this with Enum-Observed-Value-Basic-Bit-Str attribute value (check OBX-5): + +- Steps 6, 8 &10 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-session-stopped(0)|||||R||[date\_time] +- Step 11 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-type-incorrect(2)|||||R||[date\_time] +- Step 12 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-malfunction(3)|||||R||[date\_time] +- Step 13 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^device-specific-alert(4)|||||R||[date\_time] +- Step 14 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-calibration-not-allowed(7)|||||R||[date\_time] +- Step 15 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-calibration-recommended(8)|||||R||[date\_time] +- Step 16 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-calibration-required(9)|||||R||[date\_time] +- Step 17 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-temp-too-high(10)|||||R||[date\_time] +- Step 18 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-temp-too-low(11)|||||R||[date\_time] +- Step 19 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-result-below-patient-low(12)|||||R||[date\_time] +- Step 20 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-result-above-patient-high(13)|||||R||[date\_time] +- Step 21 +OBX|n|CWE|8418060^MDC\_CGM\_DEV\_STAT^MDC|1.0.0.a|1^sensor-low-hypo(14)|||||R||[date\_time] +- Step 22 + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    OBX[n CWE 8418060^MDC_CGM_DEV_STAT^MDC 1.0.0.a 1^sensor-high-hyper(15) R [date_time]

    • • Step 23

    OBX[n CWE 8418060^MDC_CGM_DEV_STAT^MDC 1.0.0.a 1^sensor-rate-decrease-exceeded(16) R [date_time]

    • • Step 24

    OBX[n CWE 8418060^MDC_CGM_DEV_STAT^MDC 1.0.0.a 1^sensor-rate-increase-exceeded(17) R [date_time]

    • • Step 25

    OBX[n CWE 8418060^MDC_CGM_DEV_STAT^MDC 1.0.0.a 1^sensor-result-too-low(18) R [date_time]

    • • Step 26

    OBX[n CWE 8418060^MDC_CGM_DEV_STAT^MDC 1.0.0.a 1^sensor-result-too-high(19) R [date_time]

    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-076 | | | | +| TP label | Whitepaper. Glucose Numeric Object value | | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | | +| | Testable items | Short Float Type 1; C | BaseOffset 3; M | Glucose Numeric 7; M | +| | | Glucose Numeric 8; M | | | +| Test purpose |

    Check that:

    PHG processes correctly the values of the CGM Glucose Concentration field (mg/dL) and the Time Offset field (m) of the CGM Measurement characteristic and the CGM Session Start Time field of the CGM Session Start Time characteristic.

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Session Start Time (0x2AAA)
        1. i. Field: Session Start Time
          • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
          • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
        2. ii. Field: Time Zone
          • • Format: sint8
          • • Value: 4 (UTC+1:00)
        3. iii. Field: DST-Offset
          • • Format: uint8
          • • Value: 4 (Daylight Time (+1h))
        4. iv. Field: E2E-CRC
          • • This field is not included
      2. b. CGM Measurement (0x2AA7)
        1. i. Field: Size
    | | | | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: uint8

    ii. Field: Flags

    • • Format: 8 bit
    • • Value: 0000 0000 (MSB → LSB). CGM Trend information not present, CGM Quality not present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.

    iii. Field: CGM Glucose Concentration (mg/dL)

    • • Format: SFLOAT
    • • Value: 160.0

    iv. Field: Time Offset

    • • Format: uint16
    • • Value: 20

    v. Field: Sensor Status Annunciation

    • • This field is not included

    vi. Field: CGM Trend Information

    • • This field is not included

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Features and CGM Session Start Time characteristics.

    5. The simulated PHD sends the Measurement to the PHG under test.

    6. Check that the PHG accepts the measurement and decodes its value properly (glucose concentration value, units and time stamp)

    7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test

    8. Check that the PHG accepts the measurement and decodes its value properly (glucose concentration value, units and time stamp)

    | +| Pass/Fail criteria | In Steps 6 and 8, the PHG under test shows the following measurement: Glucose Concentration = 160(mg/dL) with timestamp '2016-05-12 16:59:27' | +| Notes
    (To assist manual testing)     | | + +| | | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-077 | | | +| TP label | Whitepaper. Sensor Calibration Numeric Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 1; C | BaseOffset 3; M | +| | | SensCal Numeric 12; M | SensCal Numeric 11; M | +| Test purpose | Check that:
    PHG processes correctly the values of the Calibration Value – Glucose concentration of Calibration field (mg/dL) and the Calibration Time field (m) of the CGM Specific Ops Control Point characteristic when it receives a Calibration Value Response, and the CGM Session Start Time field of the CGM Session Start Time characteristic. | | | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | +| Other PICS | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The simulated PHD has a Calibration Data Record stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Session Start Time (0x2AAA)
        1. i. Field: Session Start Time
          • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
          • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
        2. ii. Field: Time Zone
          • • Format: sint8
          • • Value: 4 (UTC+1:00)
        3. iii. Field: DST-Offset
          • • Format: uint8
          • • Value: 4 (Daylight Time (+1h))
        4. iv. Field: E2E-CRC
          • • This field is not included
      2. b. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Calibration supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      3. c. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • • Format: uint8
          • • Value: 0x06 (Glucose Calibration Value Response)
        2. ii. Field: Calibration Value – Glucose concentration of Calibration (mg/dL)
          • • Format: SFLOAT (mg/dL)
          • • Value: 115.3
        3. iii. Field: Calibration Value – Calibration Time
          • • Format: uint16 (min)
          • • Value: 20
        4. iv. Field: Calibration Value – Calibration Type
    | + +| | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Format: 4 bit
    • • Value: not relevant

    v. Field: Calibration Value – Calibration Sample Location

    • • Format: 4 bit
    • • Value: not relevant

    vi. Field: Calibration Value - Next Calibration Time

    • • Format: uint16
    • • Value: not relevant

    vii. Field: Calibration Value – Calibration Data Record Number

    • • Format: uint16
    • • Value: not relevant

    viii. Field: Calibration Value – Calibration Status

    • • Format: 8 bit
    • • Value: not relevant

    ix. Field: E2E-CRC

    • • This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Glucose Calibration procedure using Op Code “Get Glucose Calibration value” (0x05) with Operand “0xFFFF”(by performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code and Calibration Data Record Number fields respectively).

    5. The simulated PHD will respond with an indication including a “Calibration Value Response” Op Code (0x06) and a Calibration Data Record containing the requested calibration information.

    6. Check that the PHG accepts the measurement and decodes its value properly (glucose concentration calibration value, units and time stamp).

    | +| Pass/Fail criteria | In Step 6, the PHG under test shows the following measurement: Glucose Concentration of Calibration= 115.3(mg/dL) with timestamp '2016-05-12 16:59:27' | +| Notes
    (To assist manual testing)     | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-078 | | | +| TP label | Whitepaper. Sensor Run-time Numeric Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | BaseOffset 2; M | SRT Numeric 5; M | +| Test purpose | Check that:

    PHG processes correctly the values of the Session Run Time field (h) of the CGM Session Run Time characteristic and the CGM Session Start Time field of the CGM Session Start Time characteristic. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure | 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). | | | + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:

    a. CGM Session Start Time (0x2AAA)

    • i. Field: Session Start Time
      • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
      • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
    • ii. Field: Time Zone
      • • Format: sint8
      • • Value: 4 (UTC+1:00)
    • iii. Field: DST-Offset
      • • Format: uint8
      • • Value: 4 (Daylight Time (+1h))
    • iv. Field: E2E-CRC
      • • This field is not included

    b. CGM Session Run Time (0x2AAB)

    • i. Field: Session Run Time
      • • Format: uint16 (h)
      • • Value: 168
    • ii. Field: E2E-CRC
      • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature, CGM Session Start Time and CGM Session Run Time characteristics.

    5. Check that the PHG decodes values properly (session run time, units and time stamp).

    | +| Pass/Fail criteria | In Step 5, the PHG under test shows the following measurement: Sensor Run Time = 168 (h) with timestamp '2016-05-12 16:39:27' | +| Notes
    (To assist manual testing)     | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-079 | | | +| TP label | Whitepaper. Glucose Sampling Interval Numeric Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | BaseOffset 1; M | GSI Numeric 8; M | +| Test purpose |

    Check that:

    PHG processes correctly the value of the Operand field (m) of the CGM Specific Ops Control Point when it receives a Communication Interval Response, and sets the timestamp to the collector's time of the collection

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has a manually entered communication interval value stored.

    2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is:

    | | | + +| | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. a. CGM Specific Ops Control Point (0x2AAC)
      1. i. Field: Op Code
        • • Format: uint8
        • • Value: 0x03
      2. ii. Field: Operand
        • • Format: uint8 (min)
        • • Value: 15
      3. iii. Field: E2E-CRC
        • • This field is not present
    2. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    3. 4. When the pairing has been completed, force the PHG to perform a CGM Communication Interval procedure using Op Code “Get CGM Communication Interval” (0x02) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code field).
    4. 5. The simulated PHD will respond with an indication including a “Communication Interval Response” Op Code (0x03) and an UINT8 containing the communication interval in minutes.
    5. 6. Check that the PHG decodes values properly (glucose sampling interval and units)
    | +| Pass/Fail criteria | In Step 6, the PHG under test shows the following measurement: Glucose Sampling Interval = 15 (m) with timestamp set to the collector's time of the collection | +| Notes
    (To assist manual testing)     | | + +| | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-080 | | | +| TP label | Whitepaper. Glucose trend Numeric Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 1; C | BaseOffset 3; M | +| | | GT Numeric 7; M | GT Numeric 6; M | +| Test purpose |

    Check that:

    PHG processes correctly the values of the CGM Trend Information field ((mg/dL)/min) and the Time Offset field (m) of the CGM Measurement characteristic and the CGM Session Start Time field of the CGM Session Start Time characteristic.

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 1000 0000 0000 0000 (MSB → LSB). CGM trend information supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant

    iii. Field: CGM Sample Location

    • • Format: 4 bit
    • • Value: not relevant

    iv. Field: E2E-CRC

    • • Format: uint16
    • • Value: not relevant

    b. CGM Measurement (0x2AA7)

    i. Field: Size

    • • Format: uint8

    ii. Field: Flags

    • • Format: 8 bit
    • • Value: 0000 0001 (MSB → LSB). CGM Trend information present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) not present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.

    iii. Field: CGM Glucose Concentration (mg/dL)

    • • Format: SFLOAT
    • • Value: not relevant

    iv. Field: Time Offset

    • • Format: uint16
    • • Value: 20 (min)

    v. Field: Sensor Status Annunciation

    • • This field is not included

    vi. Field: CGM Trend Information (mg/dL)/min

    • • Format: SFLOAT
    • • Value: 3.6

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included

    c. CGM Session Start Time (0x2AAA)

    i. Field: Session Start Time

    • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
    • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)

    ii. Field: Time Zone

    • • Format: sint8
    • • Value: 4 (UTC+1:00)

    iii. Field: DST-Offset

    • • Format: uint8
    • • Value: 4 (Daylight Time (+1h))

    iv. Field: E2E-CRC

    • • This field is not included

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the

    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    1. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    2. 5. The simulated PHD sends the Measurement to the PHG under test.
    3. 6. Check that the PHG accepts the measurement and decodes its value properly (glucose trend value, units and time stamp).
    4. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    5. 8. Check that the PHG accepts the measurement and decodes its value properly (glucose trend value, units and time stamp).
    | +| Pass/Fail criteria | In Steps 6 and 8, the PHG under test shows the following measurement: Glucose Trend = 3.6 (mg/dL/min) with timestamp '2016-05-12 16:59:27' | +| Notes
    (To assist manual testing)     | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-081 | | | +| TP label | Whitepaper. Patient low/high thresholds Compound Numeric Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 1; C | BaseOffset 1; M | +| | | PLH Numeric 10; M | PLH Numeric 9; M | +| Test purpose |

    Check that:

    PHG processes correctly the values of the Operand fields (mg/dL) of the CGM Specific Ops Control Point characteristic when it receives a Patient High Alert Level Response and a Patient Low Alert Level Response, and sets the timestamp to the collector's time of the collection

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_046 AND C_MAN_BLE_048 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has manually entered Patient Low Alert Level and Patient High Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0000 0000 0010 (MSB → LSB). Patient High/Low Alerts supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
    | | | + +| | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    b. CGM Specific Ops Control Point (0x2AAC)

    • i. Field: Op Code
      • • Format: uint8
      • • Value: 0x09 (Patient High Alert Level Response) / 0x0C (Patient Low Alert Level Response)
    • ii. Field: Operand
      • • Format: SFLOAT (mg/dL)
      • • Value: 72.0 (Patient Low threshold) / 144.0 (Patient High threshold)
    • iii. Field: E2E-CRC
      • • This field is not present

    3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).

    4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Patient High Alert procedure using Op Code “Get Patient High Alert Level” (0x08) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    5. The simulated PHD will respond with an indication including a “Patient High Alert Level Response” (0x09) Op Code and an SFLOAT containing the requested value in mg/dL.

    6. Force the PHG to perform a Patient Low Alert procedure using Op Code “Get Patient Low Alert Level” (0x0B) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).

    7. The simulated PHD will respond with an indication including a “Patient Low Alert Level Response” (0x0C) Op Code and an SFLOAT containing the requested value in mg/dL.

    8. Check that the PHG accepts the measurement and decodes its value properly (patient low and high thresholds and units).

    | +| Pass/Fail criteria | In Step 8, the PHG under test shows the following measurement: Patient Low threshold = 72.0 (mg/dL), Patient High threshold = 144.0 (mg/dL) with timestamp set to the collector’s time of the collection | +| Notes
    (To assist manual testing)     | | + +| | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-082 | | | +| TP label | Whitepaper. Device hypo/hyper thresholds Compound Numeric Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | Short Float Type 1; C | BaseOffset 1; M | +| | | DHH Numeric 10; M | DHH Numeric 9; M | +| Test purpose |

    Check that:

    PHG processes correctly the values of the Operand fields (mg/dL) of the CGM Specific Ops Control Point characteristic when it receives a Hypo Alert Level Response and a Hyper Alert Level Response, and sets the timestamp to the collector’s time of the collection

    | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND (C_MAN_BLE_050 OR C_MAN_BLE_052) | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |

    1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). PHD has manually entered Hypo and Hyper Alert Level values stored.

    2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:

    a. CGM Feature (0x2AA8)

    | | | + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. i. Field: CGM Feature
      • • Format: 24 bit
      • • Value: 0000 0000 0000 0000 0000 1100 (MSB → LSB). Hypo Alerts and Hyper Alerts supported.
    2. ii. Field: CGM Type
      • • Format: 4 bit
      • • Value: not relevant
    3. iii. Field: CGM Sample Location
      • • Format: 4 bit
      • • Value: not relevant
    4. iv. Field: E2E-CRC
      • • Format: uint16
      • • Value: not relevant
    1. b. CGM Specific Ops Control Point (0x2AAC)
      1. i. Field: Op Code
        • • Format: uint8
        • • Value: 0x0F (Hypo Alert Level Response) / 0x12 (Hyper Alert Level Response)
      2. ii. Field: Operand
        • • Format: SFLOAT (mg/dL)
        • • Value: 36.0 (Hypo Alert Level Response) / 360.0 (Hyper Alert Level Response)
      3. iii. Field: E2E-CRC
        • • This field is not present
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics.
    3. 5. IF C_MAN_BLE_050 = TRUE, force the PHG to perform a Hypo Alert procedure using Op Code “Get Hypo Alert Level” (0x0E) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hypo Alert Level Response” (0x0F) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    4. 6. IF C_MAN_BLE_052 = TRUE, force the PHG to perform a Hyper Alert procedure using Op Code “Get Hyper Alert Level” (0x11) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code). The simulated PHD will respond with an indication including a “Hyper Alert Level Response” (0x12) Op Code and an SFLOAT containing the requested alert level in mg/dL.
    5. 7. Check that the PHG accepts the measurement and decodes its value properly (hypo and hyper thresholds and units).
    | +| Pass/Fail criteria | In Step 7, the PHG under test shows the following measurement: Hypo threshold = 36.0 (mg/dL), Hyper threshold = 360.0 (mg/dL) with timestamp set to the collector's time of the collection | +| Notes
    (To assist manual testing)     | | + +| | | | +|-----------------|-----------------------------------------------------------------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-083 | | +| TP label | Whitepaper. Glucose rate of charge thresholds Compound Numeric Object value | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | + +| | | | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|------------------| +| | Testable items | Short Float Type 1; C | BaseOffset 1; M | GRC Numeric 9; M | +| | | GRC Numeric 10; M | | | +| Test purpose |

    Check that:

    PHG processes correctly the values of the Operand fields (mg/dL) of the CGM Specific Ops Control Point characteristic when it receives a Rate of Decrease Alert Level Response and a Rate of Decrease Alert Level Response, and sets the timestamp to the collector's time of the collection

    | | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 AND C_MAN_BLE_054 AND C_MAN_BLE_056 | | | | +| Other PICS | | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization). The PHD has manually entered Rate of Decrease and Increase Alert Level values stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0000 0001 0000 (MSB → LSB). Rate of Increase/Decrease Alerts supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Specific Ops Control Point (0x2AAC)
        1. i. Field: Op Code
          • • Format: uint8
          • • Value: 0x15 (Rate of Decrease Alert Level Response) / 0x18 (Rate of Increase Alert Level Response)
        2. ii. Field: Operand
          • • Format: SFLOAT (mg/dL/min)
          • • Value: 9.0 (Rate of Decrease Alert Level Response) / 9.0 (Rate of Increase Alert Level Response)
        3. iii. Field: E2E-CRC
          • • This field is not present
    3. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    4. 4. When the pairing has been completed, force the PHG to read CGM Feature and CGM Session Start Time characteristics, and then to perform a Rate of Decrease Alert Level procedure using Op Code "Get Rate of Decrease Alert Level" (0x14) (performing a write operation to the CGM Specific Ops Control Point characteristic's Op Code).
    5. 5. The simulated PHD will respond with an indication including a "Rate of Decrease Alert Level Response" (0x15) Op Code and an SFLOAT containing the requested alert level in
    | | | | + +| | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

    mg/dL/min.

    1. 6. Force the PHG to perform a Rate of Increase Alert Level procedure using Op Code “Get Rate of Increase Alert Level” (0x17) (performing a write operation to the CGM Specific Ops Control Point characteristic’s Op Code).
    2. 7. The simulated PHD will respond with an indication including a “Rate of Increase Alert Level Response” (0x18) Op Code and an SFLOAT containing the requested alert level in mg/dL/min.
    3. 8. Check that PHG accepts the measurement and decodes its value properly (glucose rate of decrease and increase thresholds and units).
    | +| Pass/Fail criteria | In Step 8, the PHG under test shows the following measurement: Glucose rate of decrease threshold = 9.0 (mg/dL/min), Glucose rate of increase threshold = 9.0 (mg/dL/min) with timestamp set to the collector’s time of the collection | +| Notes
    (To assist manual testing)     | | + +| | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-084 | | | +| TP label | Whitepaper. PHD DM Status Enumeration Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | BaseOffset 3; M | PHDM Enumeration 5; M | +| Test purpose | Check that:
    PHG processes correctly the values of the Sensor Status Annunciation field and the Time Offset field (m) of the CGM Measurement characteristic, the CGM Status field of the CGM Status characteristic and the CGM Session Start Time field of the CGM Session Start Time characteristic. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 1010 0000 0000 (MSB → LSB). Low Battery detection supported, General Device Fault supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
          • • Value: not relevant
        3. iii. Field: CGM Sample Location
          • • Format: 4 bit
          • • Value: not relevant
        4. iv. Field: E2E-CRC
          • • Format: uint16
          • • Value: not relevant
      2. b. CGM Status (0x2AA8)
    | | | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • i. Field: Time Offset
      • • Format: uint16
      • • Value: not relevant.
    • ii. Field: CGM Status
      • • Format: 24 bit
      • • Value: 0000 0000 0000 0000 0000 0010 (MSB -> LSB). Device Battery Low.
    • iii. Field: E2E-CRC
      • • This field is not included
    • c. CGM Measurement (0x2AA7)
      • i. Field: Size
        • • Format: uint8
      • ii. Field: Flags
        • • Format: 8 bit
        • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.
      • iii. Field: CGM Glucose Concentration (mg/dL)
        • • Format: SFLOAT
        • • Value: not Relevant
      • iv. Field: Time Offset
        • • Format: uint16
        • • Value: not relevant
      • v. Field: Sensor Status Annunciation
        • • Format: 8 bit
        • • Value: 0000 0010 (MSB -> LSB). Device Battery Low.
      • vi. Field: CGM Trend Information (mg/dL)
        • • This field is not included
      • vii. Field: CGM Quality
        • • This field is not included
      • viii. Field: E2E-CRC
        • • This field is not included
    • d. CGM Session Start Time (0x2AAA)
      • i. Field: Session Start Time
        • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
        • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
      • ii. Field: Time Zone
        • • Format: sint8
        • • Value: 4 (UTC+1:00)
      • iii. Field: DST-Offset
        • • Format: uint8
        • • Value: 4 (Daylight Time (+1h))
      • iv. Field: E2E-CRC
        • • This field is not included
    | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    3. 5. The simulated PHD sends the Measurement to the PHG under test.
    4. 6. Check that the PHG accepts the measurement and decodes its value properly (sensor status and time stamp).
    5. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test.
    6. 8. Check that the PHG accepts the measurement and decodes its value properly (sensor status and time stamp).
    7. 9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.
    8. 10. Check that the PHG accepts the measurement and decodes its value properly (sensor status and time stamp).
    | +| Pass/Fail criteria | In Step 6, 8 and 10, the PHG under test shows the following measurement: PHD DM Status = 'device-status-battery-low' (1) with timestamp '2016-05-12 16:59:27' | +| Notes
    (To assist manual testing)     | | + +| | | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------| +| TP Id | TP/LP-PAN/PHG/PHDTW/CGM/BV-085 | | | +| TP label | Whitepaper. CGM Status Enumeration Object value | | | +| Coverage | Spec | [Bluetooth PHDT v1.6] | | +| | Testable items | BaseOffset 3; M | CGM Enumeration 4; M | +| Test purpose | Check that:

    PHG processes correctly the values of the Sensor Status Annunciation field and the Time Offset field (m) of the CGM Measurement characteristic, the CGM Status field of the CGM Status characteristic and the CGM Session Start Time field of the CGM Session Start Time characteristic. | | | +| Applicability | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_043 | | | +| Other PICS | | | | +| Initial condition | The PHG under test and the simulated PHD are in the Standby state. | | | +| Test procedure |
    1. 1. The simulated PHD is configured with a Continuous Glucose Monitoring Profile (device specialization), it has a CGM measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also has an identical CGM measurement temporarily stored.
    2. 2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
      1. a. CGM Feature (0x2AA8)
        1. i. Field: CGM Feature
          • • Format: 24 bit
          • • Value: 0000 0000 0000 0101 1011 1111 (MSB → LSB). Sensor Type Error Detection supported, Device Specific Alert supported, Calibration supported, Sensor Temperature High-Low Detection supported, Patient High/Low Alerts supported, Hypo Alerts supported, Hyper Alerts supported, Rate of Increase/Decrease Alerts supported, Sensor Result High-Low Detection supported.
        2. ii. Field: CGM Type
          • • Format: 4 bit
    | | | + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • • Value: not relevant

    iii. Field: CGM Sample Location

    • • Format: 4 bit
    • • Value: not relevant

    iv. Field: E2E-CRC

    • • Format: uint16
    • • Value: not relevant

    b. CGM Status (0x2AA8)

    i. Field: Time Offset

    • • Format: uint16
    • • Value: 20 (min)

    ii. Field: CGM Status

    • • Format: 24 bit
    • • Value: 0000 0000 0000 0000 0000 0001 (MSB -> LSB). Session stopped.

    iii. Field: E2E-CRC

    • • This field is not included

    c. CGM Measurement (0x2AA7)

    i. Field: Size

    • • Format: uint8

    ii. Field: Flags

    • • Format: 8 bit
    • • Value: 0010 0000 (MSB → LSB). CGM Trend information not present, CGM Quality nor present, Sensor Status Annunciation Field (Warning-Octet) present, Sensor Status Annunciation Field (Cal/Temp-Octet) not present, Sensor Status Annunciation Field (Status-Octet) not present.

    iii. Field: CGM Glucose Concentration (mg/dL)

    • • Format: SFLOAT
    • • Value: not Relevant

    iv. Field: Time Offset

    • • Format: uint16
    • • Value: 20 (min)

    v. Field: Sensor Status Annunciation

    • • Format: 8 bit
    • • Value: 0000 0001 (MSB -> LSB). Session stopped.

    vi. Field: CGM Trend Information (mg/dL)

    • • This field is not included

    vii. Field: CGM Quality

    • • This field is not included

    viii. Field: E2E-CRC

    • • This field is not included

    d. CGM Session Start Time (0x2AAA)

    i. Field: Session Start Time

    • • Format: {uint16, uint8, uint8, uint8, uint8, uint8}
    • • Value: {2016, 5, 12, 16, 39, 27} (May 12, 2016, 16:39:27)
    | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
    • ii. Field: Time Zone
      • • Format: sint8
      • • Value: 4 (UTC+1:00)
    • iii. Field: DST-Offset
      • • Format: uint8
      • • Value: 4 (Daylight Time (+1h))
    • vi. Field: E2E-CRC
      • • This field is not included
    1. 3. The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).
    2. 4. When the pairing has been completed (Connection state), force the PHG under test to read the CGM Feature and CGM Session Start Time characteristics.
    3. 5. The simulated PHD sends the Measurement to the PHG under test.
    4. 6. Check that the PHG accepts the measurement and decodes its value properly (sensor status and time stamp).
    5. 7. The PHG under test requests the simulated PHD to report stored records by performing a writing operation in the Record Access Control Point (RACP). The simulated PHD sends the temporarily stored CGM measurement to the PHG under test
    6. 8. Check that the PHG accepts the measurement and decodes its value properly (sensor status and time stamp).
    7. 9. Force the PHG under test to read the CGM Status characteristic to actively request the status of the CGM sensor.
    8. 10. Check that the PHG accepts the measurement and decodes its value properly (sensor status and time stamp).
    | +| Pass/Fail criteria | In Step 6, 8 and 10, the PHG under test shows the following measurement: CGM Status = 'sensor-session-stopped' (0) with timestamp '2016-05-12 16:59:27' | +| Notes
    (To assist manual testing)     | | + +## Bibliography + +- [b-ITU-T H.810 (2013)] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T H.810 (2015)] Recommendation ITU-T H.810 (2015), *Interoperability design guidelines for personal health systems*. +- [b-Bluetooth PHDT v1.3] Bluetooth SIG (2012), *Personal Health Devices Transcoding White Paper* (version 1.3) +[https://www.bluetooth.org/docman/handlers/downloadoc.ashx?doc\\_id=294540](https://www.bluetooth.org/docman/handlers/downloadoc.ashx?doc_id=294540) +- [b-CDG 1.0] Continua Health Alliance, Continua Design Guidelines v1.0 (2008), *Continua Design Guidelines*. +- [b-CDG 2010] Continua Health Alliance, Continua Design Guidelines v1.5 (2010), *Continua Design Guidelines*. +- [b-CDG 2011] Continua Health Alliance, Continua Design Guidelines (2011), "Adrenaline", *Continua Design Guidelines*. +- [b-CDG 2012] Continua Health Alliance, Continua Design Guidelines (2012), "Catalyst", *Continua Design Guidelines*. +- [b-CDG 2013] Continua Health Alliance, Continua Design Guidelines (2013), "Endorphin", *Continua Design Guidelines*. +- [b-CDG 2015] Continua Health Alliance, Continua Design Guidelines (2015), "Genome", *Continua Design Guidelines*. +- [b-CDG 2016] Personal Connected Health Alliance, Continua Design Guidelines (2016), "Iris", *Continua Design Guidelines*. +- [b-CDG 2017] Personal Connected Health Alliance, Continua Design Guidelines (2017), "Keratin", *Continua Design Guidelines*. +- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*. + +- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.13. + +- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.11. + +- [b-TI] PHD Testable items. Test Tool v8.0.0.0 – Excel sheet v1.10. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/raw.md b/marked/H/T-REC-H.860-201404-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ee37f52b6609ffedf5de6b6fa7c86fe12d9d49ad --- /dev/null +++ b/marked/H/T-REC-H.860-201404-I_PDF-E/raw.md @@ -0,0 +1,2516 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.860** + +(04/2014) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia services and applications – +Multimedia e-health data exchange services + +--- + +**Multimedia e-health data exchange services: +Data schema and supporting services** + +Recommendation ITU-T H.860 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue, with the acronym "ITU" in a larger, bold blue font above it. + +ITU logo + +International +Telecommunication +Union + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|----------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| Mobility interworking procedures | H.550–H.559 | +| Mobile multimedia collaboration inter-working procedures | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN and WAN) | H.820–H.849 | +| Multimedia e-health data exchange services | H.860–H.869 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T H.860 + +## Multimedia e-health data exchange services: Data schema and supporting services + +## Summary + +Recommendation ITU-T H.860 specifies a common health schema applicable to a wide range of health systems – e.g., clinical and wellness – and describes the supporting services and systems architecture for a health data exchange that allows an exchange of multimedia health data between a health provider, a controlling function and a patient. The services this Recommendation describes include both point-of-care and personal healthcare services. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.860 | 2014-04-13 | 16 | 11.1002/1000/12163 | + +## Keywords + +Architecture, data dictionary, e-health, schema. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2015 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|-------|----------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 1 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Overview of the current data standard challenges in healthcare ..... | 3 | +| 6.1 | Health data transactions..... | 5 | +| 6.2 | Common health data schema..... | 5 | +| 6.3 | Service architecture ..... | 6 | +| 6.4 | Collaborative development process..... | 6 | +| 7 | Systems overview ..... | 7 | +| 7.1 | Participants ..... | 7 | +| 7.2 | Transaction types..... | 8 | +| 7.3 | Transmission..... | 8 | +| 7.4 | Validation and storage..... | 8 | +| 7.5 | Analysis ..... | 8 | +| 7.6 | Statistics and insights ..... | 8 | +| 7.7 | Governance..... | 9 | +| 8 | Common health data schema ..... | 9 | +| 9 | Health transactions..... | 11 | +| 10 | Health transactions transmission ..... | 11 | +| 11 | Validation ..... | 12 | +| | Annex A – Common health data schema ..... | 13 | +| | Annex B – Health transactions..... | 20 | +| | Annex C – Validation rules definition ..... | 23 | +| | Appendix I – Illustrative governance model..... | 33 | +| I.1 | Collaborative development framework ..... | 33 | +| | Appendix II – Health transactions XML..... | 35 | +| II.1 | ClaimSubmission..... | 35 | +| II.2 | RemittanceAdvice ..... | 36 | +| II.3 | DataSubmission..... | 36 | +| | Appendix III – Web services definition..... | 40 | +| III.1 | UploadTransaction ..... | 40 | +| III.2 | GetNewTransactions ..... | 40 | +| III.3 | DownloadTransaction..... | 40 | + +| | Page | | +|-------------------|----------------------------------------------------------------------|----| +| III.4 | SetTransactionDownloaded..... | 41 | +| III.5 | CheckNewPriorAuthorizationTransactions..... | 41 | +| III.6 | GetNewPriorAuthorizationTransactions ..... | 41 | +| III.7 | GetPrescriptions ..... | 41 | +| III.8 | SearchTransactions..... | 42 | +| III.9 | Web services returned values ..... | 43 | +| III.10 | XML format..... | 43 | +| Appendix IV – | Illustrative use case ..... | 44 | +| Appendix V – | Illustrative implementation architecture..... | 48 | +| V.1 | Centralized health exchange..... | 48 | +| V.2 | Peer-to-peer health exchange ..... | 48 | +| Appendix VI – | Data standards for national workflow and low resource settings ..... | 50 | +| VI.1 | National workflow in a high resource setting..... | 52 | +| VI.2 | National workflow in a low resource setting..... | 52 | +| Appendix VII – | Continua Design Guidelines – Illustrative use case ..... | 54 | +| VII.1 | Continua pulse oximeter reading..... | 55 | +| VII.2 | Continua thermometer reading ..... | 61 | +| Bibliography..... | | 66 | + +# Recommendation ITU-T H.860 + +## Multimedia e-health data exchange services: Data schema and supporting services + +# 1 Scope + +This Recommendation defines the following for health data exchange: + +- A common health data schema to form a common language, for all participants in the health system, to exchange health information. +- Formats and mechanisms for exchanging health information. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ISO 3166-1] ISO 3166-1 (2013), *Codes for the representation of names of countries and their subdivisions – Part 1: Country codes*. + +[ISO 4217] ISO 4217 (2008), *Codes for the representation of currencies and funds*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +None. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 e-claim:** A digital representation of a medical bill generated by a health provider for submission using telecommunications to a controlling function. + +**3.2.2 prior request:** A process initiated by a health provider to obtain permission from a controlling function prior to providing service to a patient. + +**3.2.3 prior authorization:** An approval provided by a controlling function to a health provider to provide service to a patient. + +**3.2.4 remittance advice:** An explanation of payment provided by the controlling function, which provides details about the health provider's e-claim payment. A denied e-claim would contain the required explanations for denial. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------------|--------------------------------------------------------------------------------| +| API | Application Programming Interface | +| APR-DRG | All Patient Refined Diagnosis Related Group | +| AR-DRG | Australian Refined Diagnosis Related Group | +| ASN.1 | Abstract Syntax Notation One | +| CCAM | Common Classification of Medical Procedures | +| CCI | Cardiovascular Credentialing International | +| CEN/TC 251 | Comité Européen de Normalisation – Technical Committee 251 | +| CHDS | Common Health Data Schema | +| CMS | Care Management System | +| CPT-4 | Current Procedural Terminology (4th Edition) | +| CPT-5 | Current Procedural Terminology (5th Edition) | +| DICOM | Digital Imaging and Communications in Medicine | +| DRG | Diagnosis Related Group | +| EHR | Electronic Health Record | +| ESB | Enterprise Service Bus | +| e-Health | Electronic Health | +| e-Prescription | Electronic Prescription | +| GOÄ | Gebührenordnung für Ärzte (fees for doctors (medical fee schedule)) | +| HCPCS | Healthcare Common Procedure Coding System | +| HIE | Health Information Exchange | +| HIPPA | Health Insurance Portability and Accountability Act | +| HIS | Hospital Information System | +| HL7 | Health Level Seven International | +| HTTPS | Hypertext Transfer Protocol Secure | +| ICD | International Classification of Diseases | +| ICD-9 | International Classification of Diseases, 9th Edition | +| ICD-9-CM | International Classification of Diseases, 9th Edition, Clinical Modification | +| ICD-10 | International Classification of Diseases, 10th Edition | +| ICD-10-PCS | International Classification of Diseases, 10th Edition Procedure Coding System | +| ICD-11 | International Classification of Diseases, 11th Edition | +| ICPC-2 | International Classification of Primary Care, Second edition | +| ID | Identifier | +| IEEE | Institute of Electrical and Electronics Engineers | + +| | | +|------------|--------------------------------------------------------------------------------------------| +| IHE | Integrating the Healthcare Enterprise | +| IR-DRG | International-Refined Diagnostic Related Group | +| ISO | International Organization for Standardization | +| ISO/TC 215 | ISO/Technical Committee 215 – Health informatics | +| LOINC | Logical Observation Identifiers Names and Codes | +| m-Health | mobile Health | +| MS-DRG | Medicare Severity Diagnosis Related Group | +| NCD | Non Communicable Disease | +| NGO | Non-Governmental Organization | +| NHS | National Health Service | +| NOMESCO | Nordic Medico- Statistical Committee | +| OPS-301 | Operationen – und Prozedurenschlüssel § 301 SGB V | +| OPCS-4.6 | Office of Population Censuses and Surveys – Classification of Interventions and Procedures | +| RIM | Reference Information Model | +| SMS | Short Message Services | +| SSL | Secure Socket Layer | +| Swiss-DRG | Swiss Diagnosis Related Group | +| TARMED | Tarif Médical (medical fee) | +| WHO | World Health Organization | +| XML | Extensible Markup Language | + +## 5 Conventions + +In this Recommendation: + +- The expression "is required to" indicates a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. +- The expression "is recommended to" indicates a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. +- The expression "can optionally" indicates an optional requirement which is permissible, without implying any sense of being recommended. + +## 6 Overview of the current data standard challenges in healthcare + +Worldwide, healthcare outputs are flattening while costs continue to increase. It is widely accepted that electronic health (e-health) systems hold great promise, in a broad range of health systems worldwide, for improving global access to healthcare services, improving health system performance and improving health outcomes. And yet, technological obstacles continue to hinder the promise of e-health systems; these include the lack of global interoperability standards for e-health and technical + +infrastructure barriers [b-ITU-T TWR-EH-2011]. In the interests of addressing these technological obstacles, this Recommendation proposes an additional global interoperability standard for e-health. + +There is already a rich ecosystem of standards for e-health, including telecommunications and messaging standards (e.g., short message service (SMS) and extensible markup language (XML) [b-W3C XML 1.0]), specific health code sets (e.g., for diagnosis, clinical treatment and clinical observations), and e-health standards including digital imaging and communications in medicine (DICOM), Comité Européen de Normalisation – Technical Committee 251 (CEN/TC 251), Health Level Seven International (HL7), Integrating the Healthcare Enterprise (IHE), ISO/Technical Committee 215 – Health informatics (ISO/TC 215), ISO/IEEE 11073 [b-ISO/IEEE 11073] and ITU-T technology watch report [b-ITU-T TWR-EH-2012]. + +One prominent and widely adopted set of standards are those developed by HL7 [b-HL7-RIM]. "Open integration" models (such as those developed by HL7) allow for a broad range of data to be transmitted (e.g., messages, documents, services) under the definition of the standard. However, there remains scope for differences in data definitions between functionally similar data senders (for example, different clinics within a market may adopt HL7 compliant messaging that uses different data elements). Such diversity may create difficulty among data receivers that receive data from a range of data senders. + +In this context, and based on e-health implementations in a range of health markets, a data exchange model has been developed based on a defined set of stakeholders (e.g., patient, clinician, insurer, and regulator) and a defined set of data interactions among these stakeholders. These data exchange interactions are termed "health data transactions". A "transaction-first" approach adds additional standardization to "open integration" standards by defining the transactions and the data elements through a collaborative development framework, where all participants in a health systems agree on which health problems need to be solved and then determining which transactions and data elements are required to solve these health problems. This achieves a functional level of interoperability. + +The use of standardized content for health data transactions enables health markets to deploy health data systems more rapidly, at lower cost, with access to mobile and personal health devices, and with an ability to progressively increase functionality as stakeholder requirements evolve. Standardization between health markets creates the potential for shareable practice and applications. Stakeholder benefits include: + +- patient: ability to access personal health data compiled from multiple sources through simple portals; +- clinician: ability to exchange structured data with other clinicians and access patient data from a range of sources (subject to patient consent where applicable); +- public health officer: ability to access anonymized patient data from across the population to rapidly assess disease burden and the effectiveness of interventions; +- health regulator: ability to access patient-level data to assess the safety and effectiveness of healthcare providers; +- health insurer or commissioner: ability to access patient data across their covered lifespan to enable risk assessment. + +This Recommendation comprises four components: + +- 1) an initial set of health data transactions required by a defined health system; +- 2) an initial common health data schema capable of supporting the health data transactions required by a defined health system; +- 3) the key elements of service architecture to provide health data transactions; + +4) a health system level governance model called the "collaborative development process". Additional details on these four components are as follows. + +### **6.1 Health data transactions** + +Health data transactions are built upon existing industry standard code sets for health data, for example: + +- diagnoses and presenting complaints may be codified using the World Health Organization (WHO) international classification of diseases (ICD); +- clinical activities (e.g., clinical examination, laboratory tests, surgery, treatment) may be codified using the American Medical Association's (AMA) current procedural terminology (CPT) codes; +- logical observation identifiers names and codes (LOINC) for clinical observation data. + +Each health data transaction uses the minimum possible dataset within the scope of the defined health data transaction. This data parsimony carries two important benefits: + +- 1) health data transactions are compact (typically 15-20 kilobytes) and are thus suitable for systems with limited bandwidth (including mobile); +- 2) data exchange based on the minimum required data helps ensure data security and compliance with data protection laws, and the principles set out in key health data regulations such as the US Health Insurance Portability And Accountability Act (HIPAA) law [bUS HIPAA] and the UK Caldicott principles [b-UK CP]. + +Health data transactions specify which data fields are mandatory and which are optional, the syntax of data within each field and validation ranges for data within certain fields (where applicable). This definition enables the administrative validation of the exchanged data as a key component of data quality assurance. + +For each data element in a health data transaction the specific version of the data set used is defined separately from the data itself, meaning that any version of these code sets may be used (e.g., ICD 9th edition (ICD-9) or ICD 10th edition (ICD-10); CPT 4th edition (CPT-4) or CPT 5th edition (CPT-5)). Where necessary, compatibility with existing legacy IT systems is delivered by middleware applications based on read-across tables (for example, Translating International Classification Of Primary Care, second edition (ICPC-2) to ICD-10). Whilst such read-across is not perfect (data can be lost through one-to-many asymmetry in certain code sets), a functional level of interoperability can be achieved using this method. + +### **6.2 Common health data schema** + +For each health system deploying this standard, a common health data schema (CHDS) is built by combining the data elements required for each of the health data transactions within a defined health system. Each health data transaction is made up of a subset of the CHDS. To ensure the full exchange of data to fulfil each health data transaction, mandatory fields are included. Data within the CHDS beyond the mandatory fields may be included as optional fields. + +The CHDS contains substantial clinical data (e.g., diagnosis, clinical activity such as assessment and treatment, drugs and devices used and clinical outcomes). Such data is included for primary purposes (typically, clinical and administrative) but selected data (whether patient identifiable, anonymized or aggregated) may also be provided to stakeholders for a range of secondary uses (e.g., research or regulation) according to role-based access. The CHDS is flexible for a wide range of use cases, and the structured nature of data also significantly simplifies both storage and analytics. A shared overall + +structure of CHDSs and common data elements help to ensure functional data exchange interoperability between health systems with divergent CHDSs. + +Health data is transmitted in XML [b-W3C XML 1.0] enabling data collection, transmission, storage and analysis by a wide array of devices, including personal computers, basic 2G mobile phones, modern smartphones and personal health devices. Routine health data transmissions are very compact (typically less than 20 kilobytes) avoiding the need for costly architecture and enabling the use of mobile applications. This Recommendation supports defined role-based access and is, therefore, adaptable for compliance with data protection and confidentiality laws and regulations in a range of markets. + +### **6.3 Service architecture** + +Health data systems using this Recommendation are simple and modular; they can be built from simple, standard and low-cost Internet components. The modular nature of the architecture enables implementation within existing health data systems where these exist (or full system implementation where such systems do not exist). + +The health data standards in this Recommendation aim to provide simple and interoperable exchange for core health data transactions, creating data for a range of clinical and non-clinical uses based on a collaborative development framework (see Appendix I). This Recommendation does not aim to provide an exchange for all the data that may be required for clinical care (for example, detailed clinical and nursing notes and images such as x-rays or scan results). However, data from this Recommendation may be used as a log of clinical activities, thus supporting the peer-to-peer exchange of additional data where this is required. + +### **6.4 Collaborative development process** + +The deployment of a health data system compliant with this Recommendation requires an iterative development process. To ensure inclusiveness, balance and the acceptance of the development recommendations made, this process requires the active participation of the key health system stakeholders and users of health data. Typically this includes physicians, other clinical staff, the management of healthcare providers/facilities, health insurers (where applicable), health regulators, patients and caretakers, and voluntary/non-governmental organizations (NGOs). Further details are provided in Appendix I. + +Strong governance of this process is important to ensure a balance of future flexibility (for additional functionality) and ongoing simplicity, structure and parsimony of the data model and service architecture. The Chair of the collaborative development process must have a strong understanding of health data IT systems (particularly as set out in this Recommendation) and detailed knowledge of the structure of the health system, including the key operational details related to the exchange of data between health system stakeholders. + +In light of its importance, the collaborative development process is a key component of this Recommendation. + +The process may be set out in seven stages: + +- 1) review of health data exchange requirements of health system stakeholders +- 2) mapping of additional health data exchange requirements into specifications for the development of existing health data transactions (for extended functionality) and/or new health data transactions +- 3) refinement of the common health data schema (to support all health data transactions) +- 4) refinement of the service architecture (where required) + +- 5) piloting and beta testing +- 6) hardening +- 7) scalable deployment. + +Through the collaborative development process, the standards for data exchange in a health system will evolve over time (typically with additional functionality as the health system progresses through a health data maturity model). + +## 7 Systems overview + +The objective of this clause is to describe the high-level architecture of a health data exchange. Figure 7-1 illustrates the components of the architecture. + +![Figure 7-1 – Health data exchange diagram showing the architecture of a health system. A central cloud contains Service function, Security function, Validation engine, and Analysis engine. External participants include Patient, Mobile applications and devices, Personal health devices, Healthcare provider, and Controlling function. Arrows show data flow between these participants and the central cloud. Items in red are in scope for this Recommendation.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +The diagram illustrates the health data exchange architecture. At the center is a cloud representing the core system, which contains four functional blocks: 'Service function', 'Security function', 'Validation engine', and 'Analysis engine'. Surrounding this central cloud are five external entities: + +- Patient** (top left): Connected to the cloud by a solid blue line. +- Mobile applications and devices** (top center): Represented by an 'app' icon and two smartphones. A red dashed arrow labeled 'Health and wellness' points from the cloud to them. +- Personal health devices** (top right): Represented by a fitness tracker icon. A red dashed arrow labeled 'Clinical measurement' points from the cloud to it. +- Healthcare provider** (bottom left): Represented by a doctor icon. A red dashed arrow labeled 'Clinical data and measurement' points from the cloud to them. +- Controlling function** (bottom right): Represented by a person icon. A red dashed arrow labeled 'Remittance' points from the cloud to them. + +Additional red dashed arrows originate from the 'Healthcare provider' and point to the cloud, labeled 'Authorization requests' and 'Claims'. A red dashed arrow also points from the 'Controlling function' to the cloud, labeled 'Authorization'. A solid blue line connects the 'Controlling function' to the cloud. A note at the bottom left states 'NOTE – Items in red are in scope for this Recommendation'. A reference code 'H.860(14)\_F7-1' is in the bottom right corner. + +Figure 7-1 – Health data exchange diagram showing the architecture of a health system. A central cloud contains Service function, Security function, Validation engine, and Analysis engine. External participants include Patient, Mobile applications and devices, Personal health devices, Healthcare provider, and Controlling function. Arrows show data flow between these participants and the central cloud. Items in red are in scope for this Recommendation. + +**Figure 7-1 – Health data exchange** + +### 7.1 Participants + +The participants in a health system include: + +- **patient**: the recipient of health services; +- **healthcare provider**: an individual or an institution that provides preventive, curative, promotional, or rehabilitative healthcare services in a systematic way to individuals, families or communities; +- **controlling function**: an entity other than the patient that finances or reimburses the cost of health services. In most cases, this term refers to insurance carriers, other third-party payers, or health plan sponsors (employers or unions), although the term may also be applied to controlling functions within a health provider, for example, in monitoring operations that are funded by block budget; + +- **mobile applications and devices:** a consumer mobile device and/or mobile application that captures health and wellness information; +- **personal health devices:** a consumer wearable device that captures a person's health data (e.g., fitness monitor, jogging monitor, sleep monitor, oximeter, heart rate monitor). + +### 7.2 Transaction types + +The participant will submit transactions through the system. The transaction can include a: + +- **prior request** submitted from health provider to the controlling function; +- **prior authorization** submitted by the controlling function to the health provider; +- **claim** submitted by the health provider to the controlling function; +- **remittance advice** submitted by the controlling function to the health provider; +- **person register** submitted by the health provider to the controlling function; +- **data submission** transaction to submit a patient's health and wellness readings from a health device and/or mobile application to a health provider. + +### 7.3 Transmission + +The transactions are encoded based on a CHDS (see clause 8). + +The transactions are formatted in XML and transmitted via secure connection (e.g., hypertext transfer protocol secure (HTTPS)). + +### 7.4 Validation and storage + +The health data exchange receives the transaction and performs the following functions: + +- authenticates the transaction based on credentials supplied (e.g., username and password based, certificate-based, card-based, biometrics); +- validates that the transaction is from a licensed entity (validates the controlling function or health provider licence ID); +- validates the contents and eligibility of the transaction based on established business and validation rules; +- encrypts and stores the transaction in local storage. + +### 7.5 Analysis + +The XML [b-W3C XML 1.0] transaction files from the health data exchange are stored in the data repository for further processing. A parser translates the XML documents into a relational data structure. + +A multidimensional model is applied and the data is made available via data cubes for analysis. + +### 7.6 Statistics and insights + +The aggregation of the transactions in a multidimensional model allows an analysis of population wide health information. The outputs of the analysis may include: + +- health statistics and/or +- quality indicators addressing individual patient and population health, as well as health provider and clinician performance. + +### 7.7 Governance + +Establishing one or more governance bodies helps to ensure the adoption of a common data standard as well as ensuring ongoing exchange of information with improving quality. There are typically at least three governance roles that need to be performed (whether by one or more than one governance bodies): + +- 1) **Oversee data standards:** reviews and recommends changes and additions to health data exchange standards, such as transactions, codes and business rules. The data standards panel can include representatives of health providers, accountability authority, regulators and government officials. To ensure transparency all proposed changes and panel decisions should be publically available. +- 2) **Manage data access:** subject to patient and commercial confidentiality and the implementation of appropriate security measures, data received through the health data exchange should be made available, in order to ensure transparency, improve healthcare and build trust. Data access requests may be submitted to an authorized panel (which may be called the 'data control panel') by any organization – whether submitting data or not. An end-user licence agreement governs access to the data and codifies the applicable laws and regulations. Application access to data may be purpose-based (that is based on the intended use of the data) or role-based (that is, based on the role of the entity requesting the data). Where role-based functional roles may be used to determine the functionality available to a user, and access roles may be used to determine which data a user is permitted to access. Role-based access and end-user licence agreements are defined and refined on an ongoing basis by the data control panel, which may be made up of representatives of health providers, relevant accountability authorities, regulators and government officials. To ensure transparency all requests and panel decisions should be publically available. +- 3) **Maintain technical standards:** all changes to the transaction file XML format, the architecture definition, security and encryption protocol used to transmit the transaction file to the health data exchange are reviewed and recommended by a technical standard panel. This panel can include IT representatives of health providers and controlling functions. To ensure transparency all proposed changes and panel decisions should be made publically available. + +## 8 Common health data schema + +The objective of this clause is to describe the CHDS, which forms the foundation for the health data exchange. The CHDS forms the common language that allows all participants in a health system to exchange relevant health information. The following high-level use case describes the interactions between the entities in the healthcare system. + +*Healthcare systems help individual **persons** obtain better health. A person can be a patient who has an **encounter** with a **health provider**. The health provider then claims some or all of the charges from the controlling function. The **controlling function** in turn collects insurance premiums (**financing**) from its members, who are individual persons.* + +*When a patient has an **encounter** with a health provider, the health provider needs to know what was done with the patient (e.g., **activity** such as a lab test) to be able to charge for it. Activities may or may not lead to an **observation**, such as the result of a lab test. (See Appendix IV for an illustrative use case of a patient, health provider and controlling function interaction.)* + +Figure 8-1 describes the common health data schema data types. + +![](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +| Person | Health provider | Controlling function | Administrative | +|-----------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| +| Demographic information | Clinical information | Financial information | | +| PERSON
    FirstName    Nationality
    LastName    City
    ContactNumber    PostCode
    Birthdate    GovtID
    Gender | DIAGNOSIS
    Type
    CodeSet
    Code | CLAIM
    IDProvider    Gross
    IDPayer    PatientShare
    MemberID    Net
    PayerID    PaymentReference
    ProviderID | HEADER
    SenderID
    ReceiverID
    SenderSource
    TransactionDate | +| MEMBER
    HealthID
    Relation
    PrincipalID | ENCOUNTER
    ID    Type
    PatientID    End
    FacilityID    EndType
    Start    TransferSource
    StartType    TransferDestination
    RespClinicianID | CONTRACT
    PackageName    ExpiryDate
    StartDate    GrossPremium
    RenewalDate    PremiumCurrency | RESUBMISSION
    Type
    Comment
    Attachment | +| | ACTIVITY
    ID    ClinicianID
    Start    PriorAuthorizationID
    Type    PaymentAmount
    End    DenialCode
    Code    ListGross
    Quantity    PatientShare
    Net | AUTHORIZATION REQUEST
    Type
    ID
    Date
    Ordered | | +| | OBSERVATION
    Type    Value
    CodeSet    ValueType
    Code | AUTHORIZATION
    Result    End
    ID    Limit
    DenialCode    Comment
    Start | | + +H.860(14)\_F8-1 + +**Figure 8-1 – Common health data schema** + +- **encounter** – starts when a patient is first brought under the care of a responsible healthcare professional and ends when the patient stops being under the care of a responsible healthcare professional at the healthcare provider. +- **claim** – an original request for payment for health services provided to a single patient. Claims are generally linked to patients who are covered by health insurance. For the purposes of this guidance, any invoices made out to non-insured patients should also be considered as claims. +- **activity** – any claim item or encounter item. Generally a claim item corresponds to an encounter item, so every claim item/activity item is considered an activity. This could be the case, for example, for a first outpatient consultation or a prescription, two separate activities. Some encounter items however do not correspond with claim items. +- **observation** – the result of an encounter activity such as a diagnostic test, lab work, etc. An activity may have multiple observations, but an observation can only be the result of one activity. In the simplest form, for example, a blood pressure test (the activity) results in a blood pressure reading (the observation). + +The common health data schema incorporates industry standards for health coding and includes: + +- **clinical procedures** – any standard code sets such as CPT-4, ICD-10 procedure coding system (ICD-10-PCS), cardiovascular credentialing international (CCI), operationen – und prozedurenschlüssel (OPS-301), office of population censuses and surveys – classification of interventions and procedures (OPCS-4.6), common classification of medical procedures (CCAM), Nordic medico-statistical committee (NOMESCO), Gebührenordnung für Ärzte (GOÄ), Nomenclature des prestations de santé, tarif médical (TARMED), Classificatie van verrichtingen). + +- **clinical diagnosis** – any ICD derivatives ICD-9-(WHO, clinical modification (CM)), ICD-10-(WHO, German modification (GM), Australian consortium (AM), CM), ICD-11-WHO. +- **observations** – LOINC. +- **diagnosis related groups (DRGs)** – any of the current DRG systems, such as all patient refined (APR)-DRGs), Medicare severity (MS)-DRGs, Australian refined (AR)-DRG, German(G)-DRG, Nord-DRG, international-refined (IR)-DRG, Swiss-DRG, amongst others. + +See Annex A for full common health data schema details. + +## 9 Health transactions + +The objective of this clause is to describe the health transactions, which adhere to the common health data schema described in clause 8 and forms the bases of the exchange between the various health entities. Following is an example list of typical health data transactions in a health system with one or more health payers and multiple healthcare providers: + +- **PriorRequest:** submitted by the health provider to the controlling function, this is a request for permission prior to providing service to a patient; it can be used as an electronic prescription (e-prescription). +- **PriorAuthorization:** submitted by the controlling function, this is the response to the health provider providing authorization to provide service to the patient. +- **PersonRegister:** submitted by the health provider, the person registered at the time of the visit is submitted to the accountability authority. +- **ClaimSubmission:** submitted by a health provider to send a medical bill to the controlling function in order to be reimbursed for the service provided. +- **RemittanceAdvice:** submitted by a controlling function explaining the details of the payment made to the health provider based on the claim submitted. In the event that the claim is denied, an explanation of denial is submitted. +- **DataSubmission:** submitted by the patient via a health device or a mobile application. This transaction submits health and wellness measurement data to a health provider. + +All the above transaction types follow a standard XML [b-W3C XML 1.0] format. + +See Appendix II for health transaction XML [b-W3C XML 1.0] samples. + +## 10 Health transactions transmission + +The transactions described in clause 9 are transmitted using a secure and encrypted channel (e.g., web service call over HTTPS [b-IETF RFC 2616], [b-IETF RFC 2818]). The available transaction transmissions are as follows: + +- **uploadTransaction:** used to upload the above-mentioned transaction files to the health data exchange. This transmission mechanism should be agnostic of the transaction file being submitted. +- **downloadTransactionFile:** used to download transaction files from the health data exchange. +- **getNewTransactions:** used to determine whether a transaction file is available for download. +- **setTransactionDownloaded:** used to flag a transaction file as 'downloaded' in order to prevent submitting multiple copies of the same transaction. + +- **checkNewPriorAuthorizationTransactions**: used by providers to determine whether there are prior authorization transactions available for download. +- **getNewPriorAuthorizationTransactions**: used by health providers to download prior authorizations sent by the accountability authority. +- **getPrescriptions**: used by pharmacists to download prescription transactions from the health data exchange. +- **searchTransactions**: used by the controlling functions and providers to search the health data exchange for their relevant transactions. + +See Appendix IV for an illustrative example of transactions. Figure 10-1 illustrates the interactions of the system. + +![Interaction diagram showing the central 'Health data exchange' interacting with 'Health provider', 'Pharmacy', and 'Controlling function' participants. The diagram includes authentication steps and various transaction flows like PersonRegister, ClaimSubmission, PriorRequest, PriorAuthorization, RemittanceAdvice, and DataSubmission. A small label 'H.860(14)_F10-1' is present in the bottom right of the diagram area.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +The diagram illustrates the interactions within a healthcare system. At the center is the 'Health data exchange', which contains four functional blocks: 'Service function', 'Security function', 'Validation engine', and 'Analysis engine'. Four external participants interact with this central exchange, each with an 'Authenticate' step: + +- Health provider** (left): Sends 'PersonRegister', 'ClaimSubmission', and 'PriorRequest' to the Health data exchange. +- Pharmacy** (top): Sends 'ClaimSubmission' and 'GetPrescriptions' to the Health data exchange. +- Controlling function** (right): Sends 'PriorAuthorization' and 'RemittanceAdvice' to the Health data exchange. +- Pharmacy** (bottom): Sends 'DataSubmission' to the Health data exchange. + +A small label 'H.860(14)\_F10-1' is located in the bottom right corner of the diagram. + +Interaction diagram showing the central 'Health data exchange' interacting with 'Health provider', 'Pharmacy', and 'Controlling function' participants. The diagram includes authentication steps and various transaction flows like PersonRegister, ClaimSubmission, PriorRequest, PriorAuthorization, RemittanceAdvice, and DataSubmission. A small label 'H.860(14)\_F10-1' is present in the bottom right of the diagram area. + +**Figure 10-1 – Interaction diagram** + +See Appendix IV for an illustrative use case of transactions between key participants in a healthcare system + +## 11 Validation + +The validation engine in the health data exchange parses through each transaction and validates the permission, contents and eligibility. Based on the transaction type it determines the appropriate validation rule to apply. + +See Annex C for validation rule details. + +## Annex A + +### Common health data schema + +(This annex forms an integral part of this Recommendation.) + +Table A.1 contains details of each element of the common health data schema defined in this Recommendation. + +**Table A.1 – Details of elements of the common health data schema** + +| Data object | Data field | Description | Data type | Example | +|--------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------|------------------|---------------------| +| Person | | | | | +| | Person.FirstName | First name of person receiving activity | string | jane | +| | Person.LastName | Last name of person receiving activity | string | doe | +| | Person.ContactNumber | Contact number of person receiving activity | string | 07555
    121212 | +| | Person.BirthDate | Date of birth of person receiving activity | date and time | 28/10/2012
    09:30 | +| | Person.Gender | 0 = Female
    1 = Male
    9 = Unknown | integer | 0 | +| | Person.Nationality | Nationality of person receiving activity, using [ISO 3166-1] two-letter code | string | uk | +| | Person.City | City of residence of person receiving activity | string | london | +| | Person.PostCode | Residential post code of person receiving activity | string | TW2 2SW | +| | Person.GovtID | Government-issued ID (e.g., passport number, social security number, national ID card number) of person receiving activity | string | 12345678 | +| Member | | | | | +| | Member.HealthID | Patient's health system number (e.g., health insurance member number) | string | 23456789 | +| | Member.Relation | Information about family relationships: Principal, Spouse, Child, Parent, Other with reference to principal's family member | string | principal | + +**Table A.1 – Details of elements of the common health data schema** + +| Data object | Data field | Description | Data type | Example | +|--------------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---------------------| +| | Member.PrincipalID | MemberID of the principal member of the family | string | 34567890 | +| Encounter | | | | | +| | Encounter.ID | Unique number (for that provider) assigned by the healthcare provider to identify an encounter | string | abc12345 | +| | Encounter.Type | 1 = No Bed + No emergency room
    2 = No Bed + Emergency room
    3 = Inpatient Bed + No emergency room
    4 = Inpatient Bed + Emergency room
    5 = Daycase Bed + No emergency room
    6 = Daycase Bed + Emergency room
    7 = Home
    8 = Assisted living facility
    9 = Mobile unit
    10 = Ambulance | integer | 1 | +| | Encounter.PatientID | Unique number (for that provider) that a specific healthcare provider assigns to a patient (e.g., medical record number) | string | ab123456 | +| | Encounter.FacilityID | Unique ID of facility responsible for encounter (e.g., government issued facility licence number) | string | abcd1234 | +| | Encounter.RespClinicianID | Unique ID of responsible clinician using unique number for that clinician (e.g., government licence number) | string | def4567 | +| | Encounter.Start | Date and time the patient comes under the care of the responsible clinician | date and time | 28/10/2012
    09:30 | + +**Table A.1 – Details of elements of the common health data schema** + +| Data object | Data field | Description | Data type | Example | +|--------------------|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---------------------| +| | Encounter.StartType | 1 = Elective, i.e., encounter was scheduled in advance
    2 = Emergency
    3 = Transfer from another healthcare provider
    4 = Live birth
    5 = Stillbirth
    6 = Dead on arrival
    7 = Continuing encounter
    8 = Transfer admission from non-acute care | integer | 1 | +| | Encounter.End | Date and time the patient ceases to be under the direct care of the responsible clinician | date and time | 28/10/2012
    11:30 | +| | Encounter.EndType | 1 = Discharged with approval
    2 = Discharged against advice
    3 = Discharged absent without leave
    4 = Discharge and transfer to another healthcare provider
    5 = Discharge and transfer to a non-healthcare provider
    6 = Not discharged
    7 = Dead | integer | 1 | +| | Encounter.TransferSource | Healthcare facility from which a hospital transfer originated (used only when Encounter.StartType = 3) | string | abcde123 | +| | Encounter.TransferDestination | Healthcare facility to which a hospital transfer is made (at the end of an Encounter.EndType = 3) | string | abcdef12 | +| Diagnosis | | | | | +| | Diagnosis.Type | Type of Diagnosis being recorded (i.e., principal, secondary, tertiary or admitting) | string | principal | +| | Diagnosis.CodeSet | Codeset used for diagnosis (e.g., ICD-9-CM, ICD-10) | string | icd-10 | +| | Diagnosis.Code | Diagnosis code value in type specified by Diagnosis.CodeSet | string | c23.2 | + +**Table A.1 – Details of elements of the common health data schema** + +| Data object | Data field | Description | Data type | Example | +|--------------------|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---------------------| +| Activity | | | | | +| | Activity.ID | Unique identifier that a specific healthcare provider assigns to an activity | string | cdefghi | +| | Activity.Start | Date and time at which activity started | date and time | 28/10/2012
    09:45 | +| | Activity.Type | Type of activity, e.g., Procedures, Drugs or Services
    1 = CPT
    2 = HCPC
    3 = Drug
    4 = Generic drug
    5 = Service code
    6 = DRG
    7 = Dental | integer | 8 | +| | Activity.End | Date and time at which activity ended | date and time | 28/10/2012
    09:45 | +| | Activity.Code | Code, specified by the Activity.Type, for the activity performed | string | 10 | +| | Activity.Quantity | Number of units (quantity) for a specific activity | integer | 1 | +| | Activity.Net | Net charges billed by the provider to the payer for this activity | integer | 75 | +| | Activity.ClinicianID | Clinician providing the activity for the patient (typically government licence number) | string | abcdefg1 | +| | Activity.PriorAuthorization ID | Authorization ID provided by the payer | string | abcdefgh | +| | Activity.PaymentAmount | For RemittanceAdvice:
    Amount paid by the payer towards the provider's claim
    For PriorAuthorization:
    Amount of guaranteed payment for the activity | string | 500 | +| | Activity.DenialCode | Code that indicates the reason for denial or adjustment of authorization/payment by the payer | integer | den12345 | +| | Activity.List | List price before any adjustments of discounts | string | 5000 | + +**Table A.1 – Details of elements of the common health data schema** + +| Data object | Data field | Description | Data type | Example | +|--------------------|-----------------------|---------------------------------------------------------------------------------------------------|------------------|------------------------------| +| | Activity.Gross | Total monetary amount of the charges included on the activity | string | 4000 | +| | Activity.PatientShare | Any fee that the payer is expecting the provider to collect from the patient | string | 1000 | +| Observation | | | | | +| | Observation.Type | Type of observation being recorded | integer | plain film
    AP chest x-ray | +| | Observation.CodeSet | Codeset used to record observation (e.g., LOINC) | string | loinc | +| | Observation.Code | Code describing the observation value | string | clinical | +| | Observation.Value | Observed value of the activity | string | 450 | +| | Observation.ValueType | Unit of measure for the observation value | string | milligrams | +| Claim | | | | | +| | Claim.IDProvider | Unique number assigned by the health provider to identify the claim | string | xyz789 | +| | Claim.IDPayer | Unique number assigned by a payer to identify the claim | string | bcd234 | +| | Claim.MemberID | Patient's insurance member number | string | cde345 | +| | Claim.PayerID | Unique ID for the payer (insurance provider) e.g., a government licence number | string | insurer5678 | +| | Claim.ProviderID | Unique ID for the healthcare provider (e.g., a government licence number) | string | hospital3456 | +| | Claim.Currency | Currency of claim amount, using [ISO 4217] currency code | string | gbp | +| | Claim.Gross | Total amount of the charges included on the claim (includes any amount to be paid by the patient) | integer | 2000 | +| | Claim.PatientShare | Amount to be paid by a patient to a provider according to the terms of their insurance plan | integer | 200 | + +**Table A.1 – Details of elements of the common health data schema** + +| Data object | Data field | Description | Data type | Example | +|------------------------------|-----------------------------------|----------------------------------------------------------------------------------------------------------------------|------------------|----------------| +| | Claim.Net | Net charges included on the claim (amount the provider is expected to be paid by the payer) | integer | 1800 | +| | Claim.PaymentReference | Unique ID for the payment transaction (e.g., cheque number, electronic funds transfer number) generated by the payer | string | xyza1234 | +| Contract | | | | | +| | Contract.PackageName | Name of health insurance product, generated by the payer | string | gold plus | +| | Contract.StartDate | Start date of health insurance coverage, generated by the payer | date and time | 10/28/12 | +| | Contract.ExpiryDate | End date of health insurance coverage, generated by the payer | date and time | 27/10/2013 | +| | Contract.RenewalDate | Renewal date of health insurance coverage, generated by the payer | date and time | 9/26/13 | +| | Contract.Premium Currency | Currency of health insurance premium, using [ISO 4217] currency code | string | gbp | +| | Contract.GrossPremium | Premium payable for defined health insurance coverage | integer | 1000 | +| Authorization request | | | | | +| | AuthorizationRequest.ID | Unique ID for PriorRequest transaction | string | pr1234 | +| | AuthorizationRequest.Type | Type of PriorRequest | string | authorization | +| | AuthorizationRequest.Date Ordered | Submit date of PriorRequest | date | 28/10/2012 | +| Authorization | | | | | +| | Authorization.ID | Unique ID for PriorAuthorization | string | pa5678 | +| | Authorization.Result | Indication of whether PriorAuthorization is approved or denied | string | yes | +| | Authorization.DenialCode | Reason code for PriorAuthorization denial | string | DC9876 | +| | Authorization.Start | Valid start date for PriorAuthorization | date | 15/2/2013 | + +**Table A.1 – Details of elements of the common health data schema** + +| Data object | Data field | Description | Data type | Example | +|---------------------|-------------------------|-----------------------------------------------------------------------------------------------------------|------------------|-------------------------| +| | Authorization.End | Valid end date for PriorAuthorization | date | 15/3/2013 | +| | Authorization.Limit | Monetary limit for the authorized charge amount | integer | 1000 | +| | Authorization.Comment | PriorAuthorization comments | string | | +| Header | | | | | +| | Header.SenderID | Unique ID of the entity sending the transaction | string | xxx3456 | +| | Header.ReceiverID | Unique ID of the entity receiving the transaction | string | yyy7654 | +| | Header.SenderSource | Source of the transaction (used to indicate whether transaction is from clinic or medical/fitness device) | string | fitbit | +| | Header.TransactionDate | Date and time stamp of the transaction | date and time | 2011-06-16T00:00:00.000 | +| Resubmission | | | | | +| | Resubmission.Type | The type of resubmission | string | claim | +| | Resubmission.Comment | Comments providing additional information for resubmission | string | | +| | Resubmission.Attachment | Supporting documentation for resubmission | | | + +## Annex B + +### Health transactions + +(This annex forms an integral part of this Recommendation.) + +Table B.1 contains the list of the health transactions and the common health data schemas that are required as part of the transaction. In the table "R" designates required elements and "O" designates optional ones. + +**Table B.1 – Matrix of required and option data elements and transactions** + +| | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|---------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| Header | | | | | | | +| SenderID | R | R | R | R | R | R | +| ReceiverID | R | R | R | R | R | R | +| TransactionDate | R | R | R | R | R | R | +| RecordCount | R | R | R | R | R | R | +| Person | | | | | | | +| Person.FirstName | | | O | | | | +| Person.LastName | | | O | | | | +| Person.ContactNumber | | | O | | | | +| Person.BirthDate | | | R | | | | +| Person.Gender | | | R | | | | +| Person.Nationality | | | R | | | | +| Person.City | | | R | | | | +| Person.GovtID | | | R | R | | | +| Member | | | | | | | +| Member.HealthID | | | R | | | | +| Member.Relation | | | R | | | | +| Member.PrincipalID | | | O | | | | +| Encounter | | | | | | | +| Encounter.ID | R | O | | O | | | +| Encounter.Type | R | | | O | | | +| Encounter.PatientID | R | | | | | | +| Encounter.FacilityID | R | O | | R | | | +| Encounter.RespClinicianID | R | | | | | | +| Encounter.Start | R | | | | | | +| Encounter.StartType | O | | | | | | +| Encounter.End | O | | | | | | +| Encounter.EndType | O | | | | | | + +**Table B.1 – Matrix of required and option data elements and transactions** + +| | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|-------------------------------|-------------------------|--------------------------|------------------------|----------------------|----------------------------|--------------------| +| Encounter.TransferSource | O | | | | | | +| Encounter.TransferDestination | O | | | | | | +| Diagnosis | | | | | | | +| Diagnosis.Type | R | | | R | R | | +| Diagnosis.CodeSet | R | | | R | R | | +| Diagnosis.Code | R | | | R | R | | +| Activity | | | | | | | +| Activity.ID | O | O | | R | R | | +| Activity.Start | R | R | | O | | R | +| Activity.Type | R | R | | R | R | R | +| Activity.End | R | R | | O | O | | +| Activity.Code | R | R | | R | R | | +| Activity.Quantity | R | R | | O | O | | +| Activity.Net | R | R | | R | R | | +| Activity.ClinicianID | R | R | | O | | | +| Activity.PriorAuthorizationID | O | O | | | | | +| Activity.PaymentAmount | | R | | | R | | +| Activity.DenialCode | | O | | | | | +| Activity.List | | O | | | O | | +| Activity.Gross | | O | | | O | | +| Activity.PatientShare | | O | | | | | +| Observation | | | | | | | +| Observation.Type | R | | | R | R | R | +| Observation.CodeSet | R | | | R | R | R | +| Observation.Code | R | | | R | R | R | +| Observation.Value | R | | | R | R | R | +| Observation.ValueType | R | | | R | R | R | +| Claim | | | | | | | +| Claim.IDProvider | R | R | | R | R | | +| Claim.IDPayer | O | R | | O | O | | +| Claim.MemberID | O | | | R | | | +| Claim.PayerID | R | | | R | | | +| Claim.ProviderID | R | O | | R | | | +| Claim.Currency | R | | | | | | +| Claim.Gross | R | | | | | | +| Claim.PatientShare | R | | | | | | + +**Table B.1 – Matrix of required and option data elements and transactions** + +| | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|----------------------------------|-------------------------|--------------------------|------------------------|----------------------|----------------------------|--------------------| +| Claim.Net | R | | | | | | +| Claim.PaymentReference | | R | | | | | +| Contract | | | | | | | +| Contract.PackageName | O | | R | | | | +| Contract.StartDate | | | R | | | | +| Contract.ExpiryDate | | | R | | | | +| Contract.RenewalDate | | | R | | | | +| Contract.PremiumCurrency | | | R | | | | +| Contract.GrossPremium | | | R | | | | +| Authorization request | | | | | | | +| AuthorizationRequest.ID | | | | R | | | +| AuthorizationRequest.Type | | | | R | | | +| AuthorizationRequest.DateOrdered | | | | O | | | +| AUTHORIZATION | | | | | | | +| Authorization.ID | | | | R | R | | +| Authorization.Result | | | | | O | | +| Authorization.DenialCode | | | | | O | | +| Authorization.Start | | | | | R | | +| Authorization.End | | | | | R | | +| Authorization.Limit | | | | | O | | +| Authorization.Comment | | | | | O | | +| RESUBMISSION | | | | | | | +| Resubmission.Type | R | | | R | | | +| Resubmission.Comment | R | | | R | | | +| Resubmission.Attachment | O | | | O | | | + +## Annex C + +### Validation rules definition + +(This annex forms an integral part of this Recommendation.) + +Annex C describes the validation rules as outlined in clause 10. The rules in Tables C.1 and C.2 are used to validate the transaction submitted through the health data exchange + +**Table C.1 – Details of validation rules for schema elements** + +| # | Data object | Data element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|---|-------------|-------------------|--------------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 1 | Global | N/A | zip file uploaded must contain only one XML file | • | | | | | • | +| 2 | Global | N/A | names of files uploaded may not contain reserved XML symbols | | • | | | | | +| 3 | Global | Date | cannot be less than 01/01/1900 | | | • | | | | +| 4 | Global | Date and time | cannot be less than 01/01/1900 00:00 | | | | | • | | +| 5 | Header | Header.SenderID | must be a valid payer government/commercial licence | • | | | • | • | | +| 6 | Header | Header.SenderID | must be a valid payer registered data provider | | | | | | • | +| 7 | Header | Header.ReceiverID | must be a valid payer government/commercial licence | | | | • | • | • | + +**Table C.1 – Details of validation rules for schema elements** + +| # | Data object | Data element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|----|-------------|------------------------|----------------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 8 | Header | Header.RecordCount | must be equal to the number of records in the e-claim file | • | | | | | | +| 9 | Header | Header.TransactionDate | must be equal to the current date | | | | | • | | +| 10 | Person | Person.BirthDate | <= Header.TransactionDate | • | • | | | | | +| 11 | Person | Person.Nationality | must have a correct value from the list of nationalities | | | | • | | | +| 12 | Person | Person.GovtID | must have a correct value | | | | • | | | +| 13 | Member | Member.ID | must be unique within a file | | | | | • | | +| 14 | Member | Member.RelationTo | must be equal to Member.ID if Member.Relation = 'Principal' | | | | • | • | | +| 15 | Member | Member.RelationTo | must have a value if Member.Relation is not 'Principal' | | | | | • | | +| 16 | Member | Member.RelationTo | must be equal to a MemberID, where Member.Relation = Principal | | | | | • | | +| 17 | Encounter | Encounter.Type | must have a value | | • | | | | | +| 18 | Encounter | Encounter.FacilityID | must be a valid payer government/commercial licence | • | | | | | | +| 19 | Encounter | Encounter.FacilityID | must have a value | | • | | | | | +| 20 | Encounter | Encounter.FacilityID | must be a valid payer government/commercial licence | | • | | | | | +| 21 | Encounter | Encounter.FacilityID | must be a valid payer government/commercial licence | • | • | | • | | | + +**Table C.1 – Details of validation rules for schema elements** + +| # | Data object | Data element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|----|-------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 22 | Encounter | Encounter.Start | must have a value | | • | | | | | +| 23 | Encounter | Encounter.Start | must be before Header.TransactionDate | | • | | | | | +| 24 | Encounter | Encounter.End | must have a value for inpatient | | | • | | | | +| 25 | Encounter | Encounter.End | must be greater than Encounter.Start | • | | | • | | | +| 26 | Encounter | Encounter.EndType | must have a value for inpatient | • | | | | | | +| 27 | Encounter | Encounter.Start, End, Activity.Start | start and end dates of all encounters must not overlap, Encounter.End for outpatients is defined by maximum activity start | • | | | | | | +| 28 | Encounter | Encounter.TransferSource | must be a valid payer government/commercial licence | • | | | | | | +| 29 | Encounter | Encounter.Transfer Destination | must be a valid payer government/commercial licence | • | | | | | | +| 30 | Diagnosis | Diagnosis.Type | must be Principal, Secondary or Admitting | | • | | | | | +| 31 | Diagnosis | Diagnosis.Code | must be a valid ICD code | | • | | | | | +| 32 | Diagnosis | Diagnosis.Code | must be unique within a claim | • | • | • | • | • | | +| 33 | Diagnosis | Diagnosis.Code | must be unique within an authorization | • | • | • | • | • | | +| 34 | Activity | Activity.ID | must be unique within a claim | • | | | | | • | + +**Table C.1 – Details of validation rules for schema elements** + +| # | Data object | Data element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|----|-------------|----------------|----------------------------------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 35 | Activity | Activity.ID | must be present in all or none of the activities within a particular claim | • | | | | | | +| 36 | Activity | Activity.ID | must be unique within an authorization | • | | | • | | | +| 37 | Activity | Activity.Start | must have a value | • | • | | | | • | +| 38 | Activity | Activity.Start | >= Encounter.Start and <= Encounter.End | • | | | | | | +| 39 | Activity | Activity.Start | must be within 24 hours from Encounter.Start if Encounter.Type = Outpatient | • | | | • | | | +| 40 | Activity | Activity.Start | <= Header.TransactionDate | | | • | | | • | +| 41 | Activity | Activity.Start | = Encounter.Start if Activity.Type = 9 (IR-DRG) | • | | | • | | | +| 42 | Activity | Activity.Type | must be 3 = CPT, 4 = HCPCS, 5 = Drug, 6 = Dental, 8 = Service code or 9 = IR-DRG | • | | | • | | | +| 43 | Activity | Activity.Type | = 9 (IR-DRG) is only allowed for in-patient claims | • | | | • | | | +| 45 | Activity | Activity.Code | must have a value | • | • | • | • | • | • | +| 47 | Activity | Activity.Code | must be a valid ICD code | • | | | | | | +| 48 | Activity | Activity.Code | must be a valid CPT code | • | | | • | | | +| 49 | Activity | Activity.Code | must be a valid HCPCS code | • | | | | | | +| 50 | Activity | Activity.Code | must be a valid Drug code | • | • | | | | | + +**Table C.1 – Details of validation rules for schema elements** + +| # | Data object | Data element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|----|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 51 | Activity | Activity.Code | must be a valid Dental code | | | • | | | | +| 52 | Activity | Activity.Code | must be a valid Service code | • | | | | | | +| 53 | Activity | Activity.Code | must be a valid DRG code | • | | | | | | +| 54 | Activity | Activity.Code | must have LOINC observations | • | • | | | | | +| 55 | Activity | Activity.Code | must have at least one Common Dental observation if Activity.Type = 6 and dental code has 'Tooth Number Required'='Yes' | • | | | | | | +| 56 | Activity | Activity.Code | must have no modifier if Activity.Type = 3 (CPT) | • | | | | | | +| 57 | Activity | Activity.Quantity | must be greater than zero | • | | | | | | +| 58 | Activity | Activity.Net | must have a value | • | | | | | | +| 59 | Activity | Activity.Net | sum of all Activity.Net must be equal to Claim.Net of the latest Claim.Submission transaction with same combination of ClaimID/ProviderID | • | | | | | | +| 60 | Activity | Activity.Net | >= 0 | • | | | • | | | +| 61 | Activity | Activity.Clinician | must have a value | • | | | | | | +| 62 | Activity | Activity.Clinician | must be a valid payer government/commercial licence | • | | | | | | +| 63 | Activity | Activity.Clinician | must not be a Pharmacist | • | | | | | | +| 64 | Activity | Activity.PaymentAmount | must have a value | • | | | | | | + +**Table C.1 – Details of validation rules for schema elements** + +| # | Data object | Data element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|----|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 65 | Activity | Activity.PaymentAmount | must be equal to Activity.Net for all activities in a claim if the sum of Activity.Net = sum of Activity.PaymentAmount | • | | | | | | +| 66 | Activity | Activity.DenialCode | must be a valid denial code | • | | | | | | +| 67 | Activity | Activity.DenialCode | must have a value if Activity.Net <> Activity.PaymentAmount | • | • | | | | | +| 68 | Activity | Activity.DenialCode | must be empty if Activity.Net = Activity.PaymentAmount | • | | | | | | +| 69 | Activity | Activity.DenialCode | must be empty if Activity.Net = 0 | • | | | | | | +| 70 | Activity | Activity.List | > 0 | • | | | | | | +| 71 | Activity | Activity.PatientShare | >= 0 | • | | | | | | +| 72 | Observation | Observation.Type | must have a value | | | | • | | • | +| 73 | Observation | Observation.Code | must be a valid LOINC code if Observation.Type = LOINC | | | | • | | • | +| 74 | Observation | Observation.Code | must have a valid value | | | | | • | • | +| 75 | Observation | Observation.Code | must be a valid Common Tooth Numbering code if Observation.Type = Common Dental | | | | • | • | | +| 76 | Observation | Observation.Value | must have a value | | | | | • | • | +| 77 | Observation | Observation.Value | must be numeric if Observation.Type = LOINC | | | | • | • | • | + +**Table C.1 – Details of validation rules for schema elements** + +| # | Data object | Data element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|----|-------------|-----------------------|-------------------------------------------------------------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 78 | Observation | Observation.ValueType | must be valid (list of LOINC codes with their allowed value types is published on data dictionary web site) | | | | • | | • | +| 79 | Observation | Observation.ValueType | must have a value | | | | | • | • | +| 80 | Claim | Claim.N/A | must have one principal diagnosis only | • | • | | | | | +| 81 | Claim | Claim.ID | must have a value | • | • | | | | | +| 82 | Claim | Claim.ID | must be unique within a claim transaction | | | • | | | | +| 83 | Claim | Claim.ID | RemittanceAdvice cannot be resubmitted before receiving claim resubmission | | • | | | | | +| 84 | Claim | Claim.ID | Claim cannot be resubmitted before receiving corresponding Remittance.Advice transaction | • | • | | | | | +| 85 | Claim | Claim.IDPayer | can exist only in combination with one Claim.ID | | • | | | | | +| 86 | Claim | Claim.IDPayer | must have value if Header.SenderID = Payer | | | • | | | | +| 87 | Claim | Claim.MemberID | must be present in at least one Person.Register transaction | • | • | • | • | • | | +| 88 | Claim | Claim.PayerID | must have a value | • | • | | | | | +| 89 | Claim | Claim.PayerID | must be a valid payer government/commercial licence | • | • | | • | | | + +**Table C.1 – Details of validation rules for schema elements** + +| # | Data object | Data element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|-----|-------------|--------------------|------------------------------------------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 90 | Claim | Claim.ProviderID | must have a value | • | | | | | | +| 91 | Claim | Claim.ProviderID | must be a valid payer government/commercial licence | • | | | • | • | | +| 92 | Claim | Claim.ProviderID | must be a valid payer government/commercial licence | | | • | | | | +| 93 | Claim | Claim.ProviderID | must be unique within a claim transaction | • | • | • | • | | | +| 94 | Claim | Claim.ProviderID | must be a valid payer government/commercial licence | • | • | • | • | • | | +| 95 | Claim | Claim.ProviderID | RemittanceAdvice cannot be resubmitted before receiving claim resubmission | | • | | | | | +| 96 | Claim | Claim.ProviderID | claim cannot be resubmitted before receiving corresponding Remittance.Advice transaction | • | • | • | • | • | | +| 97 | Claim | Claim.GovermentID | must have a correct value | | | • | | | | +| 98 | Claim | Claim.Gross | must have a value | • | | | • | | | +| 99 | Claim | Claim.Gross | must be greater than or equal to PatientShare + Net | • | | | • | | | +| 100 | Claim | Claim.PatientShare | must have a value | • | • | | | | | +| 101 | Claim | Claim.PatientShare | >= 0 | • | | | | | | +| 102 | Claim | Claim.Net | must have a value | • | | | • | • | | +| 103 | Claim | Claim.Net | must be equal to the sum of all its Activity.Net values | • | • | | | | | + +**Table C.1 – Details of validation rules for schema elements** + +| # | Data object | Data element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|-----|-------------|------------------------|-----------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 104 | Claim | Claim.Net | $\geq 0$ | | • | | | | | +| 105 | Claim | Claim.DateSettlement | must have a value | | • | | | | | +| 106 | Claim | Claim.DateSettlement | must be after the latest Activity.Start in the claim | | | • | | | | +| 107 | Claim | Claim.PaymentReference | must have value if sum of Activity.PaymentAmount $\neq 0$ | • | | | | | | +| 108 | Contract | Contract.ExpiryDate | $\geq$ Contract.StartDate | • | | | | | | +| 109 | Contract | Contract.ExpiryDate | $\geq$ Contract.RenewalDate | | | • | | | | +| 110 | Contract | Contract.RenewalDate | $\geq$ Contract.StartDate | • | | | | | | + +Table C.2 – Details of validation rules for Authorization ata element + +| # | Transaction type | Object | Element | Rule | Claim submission | Remittance advice | Person register | Prior request | Prior authorization | Data submit | +|----|------------------|-----------|-------------|------------------------------------------------------------------|------------------|-------------------|-----------------|---------------|---------------------|-------------| +| 1 | Authorization | Claim | PayerID | must have a value | • | • | • | • | • | | +| 2 | Authorization | Claim | PayerID | = Header.ReceiverID | | • | | | | | +| 3 | Authorization | Claim | PayerID | = Header.SenderID | • | • | • | • | • | | +| 4 | Authorization | Claim | IDPayer | must have a value | • | • | | • | • | | +| 5 | Authorization | Person | ID | must have a value | • | • | | • | • | | +| 6 | Authorization | Person | ID | must be unique within a file | • | • | | • | • | | +| 7 | Authorization | Claim | PayerID | must be a valid payer licence | • | • | | • | • | | +| 8 | Authorization | Claim | Denial Code | must be a valid denial code | • | • | | • | • | | +| 9 | Authorization | Activity | Start | must have a value | • | • | | • | • | | +| 10 | Authorization | Activity | End | must have a value | • | • | | • | • | | +| 11 | Authorization | Activity | End | >= Authorization.Start | • | • | | • | • | | +| 12 | Authorization | Member | HealthID | must be present in at least one Person.Register transaction | • | • | • | • | • | | +| 14 | Authorization | Activity | Start | >= Activity.Start of the correspondent Prior.Request transaction | • | • | | | | | +| 15 | Authorization | Activity | Start | <= Header.TransactionDate | • | • | | • | • | | +| 16 | Authorization | Diagnosis | Code | must have one principal diagnosis only | • | • | | • | | | +| 17 | Authorization | Claim | IDPayer | <= Header.TransactionDate | | • | | | | | +| 18 | Authorization | Claim | Denial Code | must not be present if Authorization.Type = "Prescription" | | • | | | • | | + +## Appendix I + +### Illustrative governance model + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Collaborative development framework + +This Recommendation was developed with substantial involvement of health stakeholders in a range of health markets. Through the collaborative development process determined by the data standards panel (Figure I.1), the real-world use cases for health data exchange between defined health system stakeholders have been codified into an initial set of health data transactions, which are all based on a single CHDS. Thus the CHDS has been, and continues to be, modified through the governance process to deliver additional health data transactions, whilst maintaining its basic structure and compact file size. + +![Figure I.1 – Data standards panel. A circular governance model diagram with a central 'Data standards panel' connected to three main stakeholders: 'Government authority representative', 'Health provider representative', and 'Controlling function representative'. Each stakeholder has associated 'Example' boxes listing users of data.](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +**Example :** +In the UK this would include the following Secondary users of data: +1. Public Health +2. Regulator +3. Academia +4. Pharmaceuticals +5. Etc. + +**Government authority** + +**Government authority representative** + +**Data standards panel** + +- Review and approve changes to the data standards +- Review and approve changes to transaction types + +**Health provider representative** + +**Health providers** + +**Example :** +In the UK this would include the following Primary users of data: +1. General Practitioners (primary care physicians) +2. Acute care (specialist physicians) +3. Community care, e.g., district nurses +4. Care commissioning groups (CCGs, care commissioner/payer) +5. Social care +6. Mental health +7. Patient +8. Care givers + +**Controlling function representative** + +**Controlling function** + +**Example :** +In the UK this would include the following Primary users of data: +1. NHS +2. CSU (Commissioning support unit) + +H.860(14)\_FI.1 + +Figure I.1 – Data standards panel. A circular governance model diagram with a central 'Data standards panel' connected to three main stakeholders: 'Government authority representative', 'Health provider representative', and 'Controlling function representative'. Each stakeholder has associated 'Example' boxes listing users of data. + +Figure I.1 – Data standards panel + +The deployment of this Recommendation depends on the iterative matching (through the collaborative development process) of health system requirements with defined health data transactions and the underlying CHDS. Health systems differ in their structure (e.g., those with a single (e.g., government) healthcare payer or those with plural private healthcare payers) and the requirements of health sector stakeholders for health data (e.g., in response to a health data maturity model). In response, the deployment of systems based on this recommended standard may be adapted to meet the specific requirements of an individual health system. However, all health systems operating the data standards in this Recommendation will have a technical capability to combine and share data; this will be subject to data protection and confidentiality laws and regulations. + +## Appendix II + +### Health transactions XML + +(This appendix does not form an integral part of this Recommendation.) + +Appendix II describes the XML sample for the health transactions. + +NOTE – An abstract syntax notation one (ASN.1) [ITU-T X.680] schema equivalent to the XML sample can be used in order to provide a compact encoding. + +### II.1 ClaimSubmission + +``` + + + xyz789 + 23456789 + insurer + hospital1234 + 111-1111-1111111-1 + 800 + 174 + 626 + + + MF2057 + 1 + 1245 + 01/01/2009 12:00 + 01/01/2010 15:00 + 3 + 2 + + + Principal + 012.13 + + + 01/01/2009 13:00 + 3 + 77057 + 1 + 313 + clinician3456 + + + CPT + 77057 + 3342F + CPT + + + + 01/01/2009 13:00 + 3 + 77052 + 1 + 313 + clinician3456 + + +``` + +### II.2 RemittanceAdvice + +``` + +
    + insurance1234 + hospital5678 + 06/01/2009 15:00 + 1 +
    + + hospital1234 + insurer4567 + + 08/01/2013 13:00 + 3 + 0031T + 1 + 6000 + clinician1234 + 1235 + 6000 + 500 + 5500 + + +``` + +### II.3 DataSubmission + +The health data exchange calls the HumanAPI ([www.humanapi.co](http://www.humanapi.co)) web service ([http://humanapi.co/v1/human/heart\\_rate](http://humanapi.co/v1/human/heart_rate)) to retrieve heart rate information and translates it to the ITU-T H.860 format. + +``` + + + 1 + 2 + 2013-06- +21T02:19:14.596Z + 62 + bpm + +``` + +``` + + + 1 + 2013-06-21T02:19:14.596Z + 2 + HHHHHH + 2013-06-21T02:19:14.596Z + + LOINC + NNNNN-M + bpm + 62 + + +``` + +The health data exchange calls the HumanAPI ([www.humanapi.co](http://www.humanapi.co)) web service ([http://humanapi.co/v1/human/blood\\_pressure](http://humanapi.co/v1/human/blood_pressure)) to retrieve heart rate information and translates it to the ITU-T H.860 format. + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
    <!-- HumanAPI Example of a BLOOD PRESSURE Reading --> <BloodPressure>   <ID>1</ID>   <userID>2</userID>   <timestamp>2013-06- 21T02:19:14.596Z</timestamp>   <value>     <systolic>122</systolic>     <diastolic>77</diastolic>   </value>   <unit>mmHg</unit> </BloodPressure>
    | 
    <!-- HumanAPI BLOOD PRESSURE reading mapped to the ITU-T H.860 format. --> <Activity>   <ID>3</ID>   <start>2013-06-21T02:19:14.596Z</start>   <type>2</type>      <!-- CPT -->   <code>BBBBB</code> <!-- CPT Code for Blood Pressure Measurement -->   <end>2013-06-21T02:19:14.596Z</end>   <Observation>     <type>LOINC</type> <!-- LOINC Code for BloodPressure Systolic -->     <code>NNNNN-A</code>     <valueType>mmHg</valueType>     <value>122</value>   </Observation>   <Observation>     <type>LOINC</type> <!-- LOINC Code for BloodPressure Diastolic -->     <code>NNNNN-B</code>     <valueType>mmHg</valueType>     <value>77</value>   </Observation> </Activity>
    | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +The health data exchange calls a jogging monitoring device web service (developer.nike.com) web service (GET [https://api.nike.com/me/sport/activities/104019031?access\\_token={access\\_token}](https://api.nike.com/me/sport/activities/104019031?access_token={access_token})) to retrieve activity information and translates it to the ITU-T H.860 format. + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
    <!-- Example of RUN activity --> <activityId>42505310606</activityId> <activityType>RUN</activityType> <startTime>2013-08- 25T14:13:03Z</startTime> <activityTimeZone>Asia/Baku</activityTime Zone> <status>COMPLETE</status> <deviceType>SPORTWATCH</deviceType> <metricSummary>   <calories>423</calories>   <fuel>1334</fuel>   <distance>6.051599979400635</dista nce>   <duration>0:32:23.000</duration> </metricSummary>
    | 
    <!-- RUN activity mapped to the ITU-T H.860 format. --> <Activity>   <ID>42505310606</ID>   <start>2013-08-25T14:13:03Z</start>   <type>2</type>      <!-- CPT -->   <code>RRRRR</code> <!-- CPT Code for Run Activity Measurement -->   <end>2013-08-25T14:13:03Z</end>   <Observation>     <type>LOINC</type>     <code>CCCCC-A</code> <!-- LOINC Code for Calories -->     <valueType>joule</valueType>     <value>423</value>   </Observation>   <Observation>     <type>LOINC</type>     <code>FFFFF-B</code> <!-- LOINC Code for Nike fuel -->     <valueType>NikeFuel</valueType>     <value>1334</value>   </Observation>   <Observation>     <type>LOINC</type>     <code>DDDDD-A</code> <!-- LOINC Code for Distance -->     <valueType>km</valueType>     <value>6.051599979400635</value>   </Observation>   <Observation>     <type>LOINC</type>     <code>TTTTT-B</code> <!-- LOINC Code for Duration -->     <valueType>millisecond</valueType>     <value>1933800</value> <!-- duration converted to milliseconds-->   </Observation> </Activity>
    | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| The health data exchange calls a fitness monitoring web service (dev.fitbit.com) (GET /1/user-/activities/date/2010-03-27.xml) to retrieve step information and translates it to the ITU-T H.860 format. | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
    <!-- Example of STEP activity --> <activityLog> <activityId>51007</activityId> <activityParentID>90019</activityParentID>     <calories>230</calories>     <description>7mph</description>     <distance>2.04</distance>     <duration>1097053</duration>     <hasStartTime>false</hasStartTime>     <isFavorite>true</isFavorite>     <logId>1154701</logId>     <name>Treadmill, 0% Incline</name>     <startTime>00:00</startTime>     <steps>3783</steps> </activityLog>
    | 
    <!-- STEP activity mapped to the ITU-T H.860 format. --> <Activity>     <ID>51007</ID>     <start>2013-08-25T14:13:03Z</start>     <type>2</type> <!-- CPT -->     <code>SSSSSS</code> <!-- CPT Code for Step     Activity Measurement -->     <end>2013-08-25T14:13:03Z</end>     <Observation>         <type>LOINC</type>         <code>CCCC-A</code> <!-- LOINC Code         for Calories -->         <valueType>joule</value>         <value>230</value>     </Observation>     <Observation>         <type>LOINC</type>         <code>SSSSS-B</code> <!-- LOINC Code         for Steps -->         <valueType>steps</value>         <value>3783</value>     </Observation>     <Observation>         <type>LOINC</type>         <code>DDDDD-A</code> <!-- LOINC Code         for Distance -->         <valueType>km</value>         <value>3.28306</value> <!-- distance         converted to km-->     </Observation>     <Observation>         <type>LOINC</type>         <code>TTTTT-B</code> <!-- LOINC Code         for Duration -->         <valueType>millisecond</value>         <value>1097053</value> <!-- duration         converted to ms-->     </Observation> </Activity>
    | +| The health data exchange calls a sleep activity monitoring web service (dev.fitbit.com) (GET /1/user-/sleep/date/2010-03-27.xml) to retrieve sleep information and translates it to the ITU-T H.860 format. | | +| 
    <!-- Example of SLEEP activity --> <sleepLog>     <isMainSleep>true</isMainSleep>     <logId>29744</logId>     <efficiency>98</efficiency>     <startTime>2011-06- 6T00:00:00.000</startTime>     <duration>28800000</duration>     <minutesToFallAsleep>0</minutesTo allAsleep>     <minutesAsleep>480</minutesAsleep>     <minutesAwake>0</minutesAwake>     <minutesAfterWakeup>0</minutesAfte rWakeup>     <awakeningsCount>0</awakeningsCoun t>     <timeInBed>480</timeInBed> </sleepLog>
    | 
    <!-- SLEEP activity mapped to the ITU-T H.860 format. --> <Activity>     <ID>29744</ID>     <start>2011-06-16T00:00:00.000</start>     <type>2</type> <!-- CPT -->     <code>SLSLSL</code> <!-- CPT Code for Sleep     Activity Measurement -->     <end>2013-08-25T14:13:03Z</end>     <Observation>         <type>LOINC</type>         <code>EEEE-A</code> <!-- LOINC Code for         Sleep Efficiency -->         <valueType>%</value>         <value>98</value>     </Observation>     <Observation>         <type>LOINC</type>         <code>MINFA-A</code> <!-- LOINC Code for Min.         to Fall Asleep -->         <valueType>min</value>         <value>0</value>     </Observation>     <Observation>         <type>LOINC</type>         <code>MINASL-A</code> <!-- LOINC Code for Min.         Asleep -->         <valueType>min</value>         <value>480</value>     </Observation>     <Observation>
    | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 
     <type>LOINC</type> <code>MINAW-B</code> <!-- LOINC Code for Min. Awake --> <valueType>min</value> <value>0</value> </Observation> <Observation> <type>LOINC</type> <code>MINAA-B</code> <!-- LOINC Code for Min. After Awake --> <valueType>min</value> <value>0</value> </Observation> <Observation> <type>LOINC</type> <code>AWCNT-B</code> <!-- LOINC Code for Awakenings Count --> <valueType>min</value> <value>0</value> </Observation> <Observation> <type>LOINC</type> <code>TIBED-B</code> <!-- LOINC Code for Time in Bed --> <valueType>min</value> <value>480</value> </Observation> </Activity>
    | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## Appendix III + +### Web services definition + +(This appendix does not form an integral part of this Recommendation.) + +Appendix III describes the web services for the transaction transmission as outlined in clause 10. + +### III.1 UploadTransaction + +This web service is used to upload new transactions to the health data exchange. + +``` +int UploadTransaction(string login, + string pwd, + byte[] fileContent, + string fileName, + out string errorMessage) +``` + +| | | +|--------------|------------------------------------------------------------------------------------------------------| +| login | User login name to connect to the health data exchange | +| pwd | User password to connect to the health data exchange | +| fileContent | Content of the file to upload | +| fileName | Uploaded file name; this file name will be used later to show users the available files for download | +| errorMessage | Error message value returned | + +### III.2 GetNewTransactions + +This web service is used to get a list of new transactions available on the health data exchange. The service returns back a list of transactions that have not yet been downloaded. + +``` +int GetNewTransactions(string login, + string pwd, + out string transactionResults, + out string errorMessage) +``` + +| | | +|--------------------|----------------------------------------------------------------------------------| +| login | User login name to connect to the health data exchange | +| pwd | User password to connect to the health data exchange | +| fileContent | Content of the file to upload | +| transactionResults | Output parameter that contains xml with description of the new transaction files | +| errorMessage | Error message value returned | + +### III.3 DownloadTransaction + +The web service returns a transaction file. + +``` +int DownloadTransaction(string login, string pwd, + string fileID, + out byte[] file, + out string errorMessage) +``` + +| | | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Login | User login name to connect to the health data exchange | +| Pwd | User password to connect to the health data exchange | +| fileID | ID of the file to receive the downloading link for; this ID is received from the XML file returned by GetNewTransactions web services | +| File | File content as byte array returned by the web server to the caller | +| errorMessage | Error message value returned | + +### III.4 SetTransactionDownloaded + +The web service is used to flag the downloaded file as downloaded. + +``` +int SetTransactionDownloaded(string login, string pwd, + string fileID, + out string errorMessage) +``` + +| | | +|--------------|--------------------------------------------------------| +| Login | User login name to connect to the health data exchange | +| Pwd | User password to connect to the health data exchange | +| fileID | ID of the file to set as 'downloaded' | +| errorMessage | Error message value returned | + +### III.5 CheckNewPriorAuthorizationTransactions + +This web service is used to check if new Prior.Request or Prior.Authorization transactions are available on the health data exchange. The service returns back a reply if at least one such transaction exists. + +``` +int CheckNewPriorAuthorizationTransactions + (string login, string pwd, + out string errorMessage) +``` + +| | | +|--------------|--------------------------------------------------------| +| Login | User login name to connect to the health data exchange | +| Pwd | User password to connect to the health data exchange | +| errorMessage | Error message value returned | + +### III.6 GetNewPriorAuthorizationTransactions + +This web service is used to get a list of new Prior.Request or Prior.Authorization transactions available on the health data exchange. The service returns back a list of transactions that have not yet been downloaded. + +``` +int GetNewPriorAuthorizationTransactions + (string login, string pwd, + string transactionResults, + out string errorMessage) +``` + +| | | +|--------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Login | User login name to connect to the health data exchange | +| Pwd | User password to connect to the health data exchange | +| transactionResults | Output parameter that contains XML with description of the new e-claim files with Prior.Request and Prior.Authorization transactions | +| errorMessage | Error message value returned | + +### III.7 GetPrescriptions + +This web service is used to check prescription transaction that contains a list of approved trade drugs available for dispensing. + +``` + +int GetPrescriptions(string login, + string pwd, + string payerID, + string memberID, + out byte[] prescription, + out string errorMessage) + +``` + +| | | +|--------------|--------------------------------------------------------------------------------------| +| Login | User login name to connect to the health data exchange | +| Pwd | User password to connect to the health data exchange | +| payerID | Content of the file to upload | +| memberID | Output parameter that contains xml with description of the new transaction files | +| prescription | Output parameter that contains prescription transaction that contains approved drugs | +| errorMessage | Error message value returned | + +### III.8 SearchTransactions + +The web service performs advanced search for sent and received transactions. + +``` + +int SearchTransactions(string login, + string pwd, + int direction, + string callerLicense, + string ePartner, + int transactionID, + string transactionFileName, + string transactionFromDate, + string transactionToDate, + out string transactionResults, + out string errorMessage) + +``` + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Login | User login name to connect to the health data exchange | +| Pwd | User password to connect to the health data exchange | +| Direction | flag indicating if function will search for sent or received transactions; sent=1; received=2 | +| ePartner | Licence ID of the ePartner
    • – if direction = 1 then ePartner licence ID is used to find transactions sent to the ePartner
    • – if direction = 2 then ePartner licence is used to find transactions received from the ePartner;
    | +| transactionID | ID of transactions to search for. The following values can be used:
    • 1 – ALL transactions
    • 2 – Claim.Submission transactions
    • 3 – Person.Register transactions
    • 4 – Remittance.Advice
    • 5 – Prior.Request transaction
    • 6 – Prior.Authorization transaction
    | +| transactionFileName | Partial or complete transaction file name to search for; e.g., string 'Oct' will return all transactions with the word 'Oct' in the filename e.g., 'ClaimSubmissionOct2013.xml' | +| transactionFromDate | 'From Date' to search for transactions.
    Date format = 'dd/MM/yyyy hh:mm:ss' | + +| | | +|--------------------|------------------------------------------------------------------------------------| +| transactionToDate | 'To Date' to search for transactions.
    Date format = 'dd/MM/yyyy hh:mm:ss' | +| transactionResults | Output parameter that contains XML with description of the found transaction files | +| errorMessage | Error message value returned | + +### III.9 Web services returned values + +All of the above web services have a standard return value as part of the **errorMessage** value. The supported returned values are shown in Table III.1. + +**Table III.1 – Values for errorMessage** + +| | | +|----|-------------------------------------------------------------------------------| +| 0 | Operation is successful | +| 1 | Transaction validation succeeded with warnings | +| 2 | No new prior authorization transactions are available for download | +| 3 | Prescription transaction is not returned – member has no approved trade drugs | +| -1 | Login failed for the user | +| -2 | Transaction validation failed with errors | +| -3 | Required input parameter is empty, or null, or contains invalid value | +| -4 | Unexpected error occurred | +| -5 | The specified file is not found | +| -6 | Transaction is not supported | + +### III.10 XML format + +For 'GetNewTransactions', 'GetNewPriorAuthorizationTransactions' and 'SearchTransactions' the **transactionResults** parameter will return XML in the following format: + +``` + + + + + + + +``` + +| | | +|-----------------|-------------------------------------------------------------------------| +| FileID | Unique file ID | +| FileName | Original file name uploaded by the sender | +| SenderID | Transaction file sender | +| ReceiverID | Transaction file receiver | +| TransactionDate | Value from the transaction file's TransactionDate value | +| IsDownloaded | True = file has been downloaded
    False = file has not been downloaded | + +## Appendix IV Illustrative use case + +(This appendix does not form an integral part of this Recommendation.) + +![Sequence diagram illustrating an illustrative use case for health data exchange between a Primary care provider, Health data exchange, and a Controlling function. The diagram is split into two parts by a dashed line. Part 1 shows the prior authorization process: 1. Patient books appointment; 2. PCP sends PriorRequest; 3. Controlling function sends PriorAuthorization; 4. PCP checks transactions; 5. PCP gets transactions. Part 2 shows the claim submission process: 4. Patient visits PCP; 5. PCP performs assessment and books x-ray; 6. PCP submits ClaimSubmission; 7. Controlling function sends RemittanceAdvice; 5. PCP downloads transaction; 6. PCP sets transaction downloaded.](8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg) + +**Part 1: Prior Authorization** + +- 1** A patient notices worsening pain in left hip whilst walking, and books an appointment with a primary care physician (PCP) for an initial assessment. +- 2** The PCP sends an 'Authorization Request' to the insurance company for an outpatient assessment of the patient. + - Primary care provider → Health data exchange: uploadTransaction: *PriorRequest* (1) + - Health data exchange → Controlling function: downloadTransaction (2) + - Controlling function → Health data exchange: uploadTransaction: *PriorAuthorization* (3) +- 3** The insurance company reviews the authorization request and sends an authorization notification to the PCP. +- Primary care provider → Health data exchange: CheckNewPriorAuthorizationTransactions (4) +- Primary care provider → Health data exchange: GetNewPriorAuthorizationTransactions (5) + +--- + +**Part 2: Claim Submission** + +- 4** The patient visits PCP for initial assessment. +- 5** The PCP performs a clinical assessment confirming a presenting complaint of moderate pain in the left hip (ICD-9CM code [CODE1]) + - The PCP books a plain-film x-ray of the left hip (CPT-4 code [CODE3]) at a local hospital + - The PCP arranges a follow-up appointment with the patient in two weeks' time. +- 6** The PCP submits an electronic claim for reimbursement of outpatient patient assessment (CPT-4 code [CODE2]). + - Primary care provider → Health data exchange: uploadTransaction: *ClaimSubmission* (1) + - Health data exchange → Controlling function: downloadTransaction (2) + - Controlling function → Health data exchange: setTransactionDownloaded (3) + - Controlling function → Health data exchange: uploadTransaction: *RemittanceAdvice* (4) + - Health data exchange → Primary care provider: downloadTransaction (5) + - Primary care provider → Health data exchange: setTransactionDownloaded (6) +- 7** The insurance company reviews the PCP's claim and submits a 'RemittanceAdvice' indicating how much of the claim will be covered by the payer. + +Sequence diagram illustrating an illustrative use case for health data exchange between a Primary care provider, Health data exchange, and a Controlling function. The diagram is split into two parts by a dashed line. Part 1 shows the prior authorization process: 1. Patient books appointment; 2. PCP sends PriorRequest; 3. Controlling function sends PriorAuthorization; 4. PCP checks transactions; 5. PCP gets transactions. Part 2 shows the claim submission process: 4. Patient visits PCP; 5. PCP performs assessment and books x-ray; 6. PCP submits ClaimSubmission; 7. Controlling function sends RemittanceAdvice; 5. PCP downloads transaction; 6. PCP sets transaction downloaded. + +H.860(14)\_FIV.1 + +**Figure IV.1 – Illustrative use case, part 1** + +![Sequence diagram illustrating an illustrative use case (part 2) involving a patient, secondary care hospital, primary care provider, and a controlling function via a health data exchange.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +The diagram illustrates a sequence of interactions between a patient, a secondary care hospital, a primary care provider, and a controlling function, mediated by a health data exchange. + +**Participants:** + +- Patient:** Represented by an icon. Note 8: "The patient visits the secondary care hospital for an x-ray." +- Secondary care hospital:** The main actor on the left. It sends and receives various transactions through the health data exchange. +- Primary care provider:** Located at the bottom, connected to the secondary care hospital via a DICOM transmission. Note 13: "The patient's x-ray is electronically transmitted to the PCP (using DICOM standards)." +- Health data exchange:** A central dashed box acting as a mediator for transactions. +- Controlling function:** Located on the right, it receives and sends transactions through the health data exchange. Note 10: "The Insurance company reviews the authorization request and sends an authorization notification to the secondary care hospital." and Note 12: "The Insurance company reviews the claim and submits a 'RemittanceAdvice' indicating how much of the claim will be covered by the payer." + +**Sequence of Interactions:** + +- The secondary care hospital sends an *uploadTransaction: PriorRequest* (1) to the health data exchange. Note 9: "The secondary care hospital sends an 'Authorization Request' to the insurance company for a plain-film x-ray of the left hip for the patient." +- The health data exchange sends a *downloadTransaction* (2) to the controlling function. +- The controlling function sends an *uploadTransaction: PriorAuthorization* (3) to the health data exchange. +- The secondary care hospital sends a *CheckNewPriorAuthorizationTransactions* (4) to the health data exchange. +- The secondary care hospital sends a *GetNewPriorAuthorizationTransactions* (5) to the health data exchange. +- The secondary care hospital sends an *uploadTransaction: ClaimSubmission* (6) to the health data exchange. Note 11: "The secondary care hospital submits a claim for plain film x-ray, left hip (CPT-4 code [CODE2])." +- The health data exchange sends a *downloadTransaction* (7) to the controlling function. +- The controlling function sends a *setTransactionDownloaded* (8) to the health data exchange. +- The controlling function sends an *uploadTransaction: RemittanceAdvice* (9) to the health data exchange. +- The health data exchange sends a *downloadTransaction* (10) to the secondary care hospital. +- The secondary care hospital sends a *setTransactionDownloaded* (6) to the health data exchange. + +**Additional Flow:** + +- The primary care provider transmits data via **DICOM** to the secondary care hospital. Note 13: "The patient's x-ray is electronically transmitted to the PCP (using DICOM standards)." + +H.860(14)\_FIV.2 + +Sequence diagram illustrating an illustrative use case (part 2) involving a patient, secondary care hospital, primary care provider, and a controlling function via a health data exchange. + +Figure IV.2 – Illustrative use case, part 2 + +![Sequence diagram illustrating a healthcare use case, part 3. The diagram is split into two horizontal sections by a dashed line. The top section shows interactions between a Primary care provider, a Controlling function, and a Health data exchange, with steps 14-17. The bottom section shows interactions between a Secondary care hospital, a Controlling function, and a Health data exchange, with steps 18-24. Various transactions like ClaimSubmission, PriorRequest, and RemittanceAdvice are shown between the entities.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +**Top Section: Primary care provider interactions** + +- 14** The patient attends follow-up appointment with the PCP. +- 15** The PCP makes a diagnosis of moderate to severe osteoarthritis of the left hip (ICD-9CM code [CODE4]) and refers the patient back to the secondary care hospital for review by an orthopaedic surgeon. +- 16** The PCP submits an electronic claim for reimbursement of outpatient patient assessment (CPT-4 code [CODE2]). +- 17** The Insurance company reviews the authorization request and sends an authorization notification to the PCP. + +**Sequence Details (Top Section):** + +- 1: uploadTransaction: *ClaimSubmission* (Primary care provider to Health data exchange) +- 2: downloadTransaction (Health data exchange to Controlling function) +- 3: setTransactionDownloaded (Controlling function to Health data exchange) +- 4: uploadTransaction: *RemittanceAdvice* (Controlling function to Health data exchange) +- 5: downloadTransaction (Health data exchange to Primary care provider) +- 6: setTransactionDownloaded (Primary care provider to Health data exchange) + +--- + +**Bottom Section: Secondary care hospital interactions** + +- 18** The patient visits the secondary care hospital for a review by the orthopaedic surgeon. +- 19** The orthopaedic surgeon performs a clinical assessment and reviews the original plain film x-rays (*available on the hospital PACS system, which is enabled by DICOM standards*). The orthopaedic surgeon confirms a diagnosis of moderate to severe osteoarthritis of the left hip (ICD-9CM code [CODE4]) and, in consultation with the patient, books elective surgery to replace the left hip with a prosthesis (a left hip two-surface arthroplasty, CPT-4 [CODE5]) at the secondary care hospital. +- 20** The secondary care hospital sends an 'Authorization Request' to the insurance company for an elective left hip two-surface arthroplasty, CPT-4 [CODE5]. +- 21** The Insurance company reviews the authorization request and sends an authorization notification to the secondary care hospital. +- 22** The patient receives notification of the date and time of surgery. +- 23** The secondary care hospital submits a claim for outpatient patient assessment by orthopaedic surgeon (CPT-4 code [CODE2]). +- 24** The Insurance company reviews the secondary care hospital's claim and submits a 'RemittanceAdvice' indicating how much of the claim will be covered by the payer. + +**Sequence Details (Bottom Section):** + +- 1: uploadTransaction: *PriorRequest* (Secondary care hospital to Health data exchange) +- 2: downloadTransaction (Health data exchange to Controlling function) +- 3: uploadTransaction: *PriorAuthorization* (Controlling function to Health data exchange) +- 4: CheckNewPriorAuthorizationTransactions (Secondary care hospital to Health data exchange) +- 5: GetNewPriorAuthorizationTransactions (Secondary care hospital to Health data exchange) +- 6: uploadTransaction: *ClaimSubmission* (Secondary care hospital to Health data exchange) +- 7: downloadTransaction (Health data exchange to Controlling function) +- 8: setTransactionDownloaded (Controlling function to Health data exchange) +- 9: uploadTransaction: *RemittanceAdvice* (Controlling function to Health data exchange) +- 10: downloadTransaction (Health data exchange to Secondary care hospital) +- 6: setTransactionDownloaded (Secondary care hospital to Health data exchange) + +Sequence diagram illustrating a healthcare use case, part 3. The diagram is split into two horizontal sections by a dashed line. The top section shows interactions between a Primary care provider, a Controlling function, and a Health data exchange, with steps 14-17. The bottom section shows interactions between a Secondary care hospital, a Controlling function, and a Health data exchange, with steps 18-24. Various transactions like ClaimSubmission, PriorRequest, and RemittanceAdvice are shown between the entities. + +**Figure IV.3 – Illustrative use case, part 3** + +![Sequence diagrams for two use cases (25-28 and 29-30) showing interactions between a Secondary care hospital, Health data exchange, and a Controlling function. The diagrams include lifelines, message sequences (1-6), and associated text boxes with IDs 25-30.](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +**Use Case 25-28: Patient Admitted to Secondary Care Hospital** + +**25** The Patient is admitted to the secondary care hospital for an elective left hip two-surface arthroplasty, CPT-4 [CODE5]. + +**26** The PCP submits an electronic claim for reimbursement of outpatient patient assessment (CPT-4 code [CODE2]). + +**27** The Insurance company reviews the claim and submits a 'RemittanceAdvice' indicating how much of the claim will be covered by the payer. + +**28** The procedure is successful and the patient is discharged from the secondary care hospital the following day with a follow-up appointment with the orthopaedic surgeon in two weeks' time. + +**Sequence:** + +- 1: uploadTransaction: *ClaimSubmission* (Secondary care hospital → Health data exchange) +- 2: downloadTransaction (Health data exchange → Controlling function) +- 3: setTransactionDownloaded (Controlling function → Health data exchange) +- 4: uploadTransaction: *RemittanceAdvice* (Controlling function → Health data exchange) +- 5: downloadTransaction (Health data exchange → Secondary care hospital) +- 6: setTransactionDownloaded (Health data exchange → Secondary care hospital) + +--- + +**Use Case 29-30: Patient Follow-up Appointment** + +**29** The Patient visits the secondary care hospital for the follow-up appointment with the orthopaedic surgeon and is discharged back to the care of his PCP. + +**30** The secondary care hospital submits a claim for outpatient patient assessment by orthopaedic surgeon (CPT-4 code [CODE2]). + +**30** The Insurance company reviews the claim and submits a 'RemittanceAdvice' indicating how much of the claim will be covered by the payer. + +**Sequence:** + +- 1: uploadTransaction: *ClaimSubmission* (Secondary care hospital → Health data exchange) +- 2: downloadTransaction (Health data exchange → Controlling function) +- 3: setTransactionDownloaded (Controlling function → Health data exchange) +- 4: uploadTransaction: *RemittanceAdvice* (Controlling function → Health data exchange) +- 5: downloadTransaction (Health data exchange → Secondary care hospital) +- 6: setTransactionDownloaded (Health data exchange → Secondary care hospital) + +H.860(14)\_FIV.4 + +Sequence diagrams for two use cases (25-28 and 29-30) showing interactions between a Secondary care hospital, Health data exchange, and a Controlling function. The diagrams include lifelines, message sequences (1-6), and associated text boxes with IDs 25-30. + +**Figure IV.4 – Illustrative use case, part 4** + +## Appendix V + +### Illustrative implementation architecture + +(This appendix does not form an integral part of this Recommendation.) + +This Recommendation can use various architectures to exchange standardized health information. Two examples are listed below. + +### V.1 Centralized health exchange + +This model uses a centralized architecture to exchange health information between all participating entities. The centralized entity typically uses an enterprise service bus (ESB) to exchange the data and will have a centralized validation engine and analytics engine. This model is typically seen in a large health system with multiple health providers and controlling function. See Figure V.1. + +A single entity, either government (e.g., Health Authority or Ministry of Health) or a commercial entity governs and operates the centralized health exchange with inputs from all participating entities. + +![Diagram of Centralized health data exchange architecture](db5deafdae53dbc7d5972957f708c691_img.jpg) + +The diagram illustrates a centralized health data exchange architecture. At the center is a cloud representing the exchange hub, containing three functional blocks: 'Services function' (with a sub-block for 'Security function'), 'Validation engine', and 'Analysis engine'. Four external entities are connected to this central hub: a 'Patient' (top left), 'Mobile applications and devices' (top center, labeled 'Health and wellness'), 'Personal health devices' (top right, labeled 'Clinical measurement'), and a 'Healthcare provider' (bottom left, labeled 'Clinical data and measurement'). A 'Controlling function' (bottom right) is also connected. Dashed arrows indicate data flow from the Patient, Mobile applications, Personal health devices, and Healthcare provider towards the central hub. From the central hub, dashed arrows point to the Controlling function, labeled 'Claims', 'Remittance', and 'Authorization'. A dashed arrow also points from the Controlling function back to the central hub, labeled 'Authorization requests'. The entire diagram is enclosed in a dashed rectangular border. The label 'H.860(14)\_FV.1' is located in the bottom right corner of the diagram area. + +Diagram of Centralized health data exchange architecture + +Figure V.1 – Centralized health data exchange + +### V.2 Peer-to-peer health exchange + +This model is a decentralized architecture. Each participating entity ensures that the data exchanged conforms to ITU-T H.860. They also ensure that the data is validated prior to submitting the data to the other entity. The connections are peer-to-peer between participating entities. This type of model is typically seen where there are few entities to connect and/or in a low resource scenario where the cost of building, operating and governing a centralized exchange architecture is cost prohibitive. The peer-to-peer health exchange can often be used as the first step in implementing ITU-T H.860. The exchange can move to a centralized model when the number of participants reaches a point where + +peer-to-peer management of the exchange becomes administratively prohibitive or when implementing a centralized exchange becomes cost permissible. See Figure V.2. + +![Diagram of peer-to-peer health data exchange showing interactions between a Patient, Mobile applications and devices, Personal health devices, ITU-T H.860 enabled systems (Healthcare provider), and Controlling function(s).](284768c5ee1a05aa1b9ce396f606a040_img.jpg) + +The diagram illustrates a peer-to-peer health data exchange architecture. At the top left, a **Patient** icon is shown. Dashed arrows originate from the Patient, labeled **Personal data capture** pointing to **Mobile applications and devices** (represented by an **app** icon and a smartphone), **Patient health and wellness** pointing to **ITU-T H.860 enabled systems** (represented by a **Healthcare provider(s)** icon), and **Patient health visit** pointing to another **ITU-T H.860 enabled systems** (represented by a **Controlling function(s)** icon). The **Mobile applications and devices** are connected to a central box labeled **ITU-T H.860 enabled mobile apps, devices and personal health devices**. This central box is connected to the **Personal health devices** (represented by a fitness tracker icon) via a solid blue line. A dashed arrow labeled **Clinical measurement** points from the **Personal health devices** to the **ITU-T H.860 enabled systems** (Controlling function(s)). A dashed green arrow labeled **Remittance authorization** points from the **ITU-T H.860 enabled systems** (Healthcare provider(s)) to the **ITU-T H.860 enabled systems** (Controlling function(s)). A dashed purple arrow labeled **Claims Authorization requests** points from the **ITU-T H.860 enabled systems** (Healthcare provider(s)) to the **ITU-T H.860 enabled systems** (Controlling function(s)). The text **H.860(14)\_FV.2** is located near the bottom right. + +Diagram of peer-to-peer health data exchange showing interactions between a Patient, Mobile applications and devices, Personal health devices, ITU-T H.860 enabled systems (Healthcare provider), and Controlling function(s). + +**Figure V.2 – Peer-to-peer health data exchange** + +## Appendix VI + +### Data standards for national workflow and low resource settings + +(This appendix does not form an integral part of this Recommendation.) + +The data standard set out in this Recommendation establishes an iterative process for delivering the interoperability of health data by establishing a collaborative development framework. Within the collaborative development framework, the stakeholders that use health data within a defined health market jointly define the specific health data exchange problems that need to be solved, and define health data transactions that meet these challenges. The definitions of health data transactions include the data elements contained within those transactions, the approved format or syntax for these data elements, and which data elements are mandatory and which are optional. The sum of all data elements across the health data transactions within a health market defines the common health data schema for that market. + +The data standards set out in this Recommendation are, therefore, adopted within the context of a health market, and are able to adapt to the health data exchange problems that need to be solved. This collaborative development framework thus applies to any health system (whether it is a multi-payer or single payer, multi-provider or single provider). The components of the collaborative development framework are as follows: + +- **define health problem** – determine the desired health outcomes (e.g., mortality, morbidity/disease burden, life expectancy) or disease-specific outcomes (e.g., obesity, cardiovascular disease). Desired outcomes can also be operational (e.g., regulation, patient education, telehealth, mobile health (m-health), integration with non-healthcare sector). +- **define health system stakeholders** – identify health system stakeholders that need to be involved to solve the health problem (e.g., health providers, health payers, health authority, patients). Establish a governance body that includes all the key health systems stakeholders. +- **define health transactions** – identify the transactions that need to be implemented to exchange the required data to solve the health problem (e.g., claims submission, e-prescription, screening data transmission). +- **define common health data schema** – identify the data standard data element required for each transaction to exchange the required information between the health system participants (e.g., patient information, screening data). +- **define systems architecture** – based on current e-health system assessment and technology capabilities, determine the systems architecture required to enable the transaction and data exchange. +- **assess e-health readiness** – assess e-health capabilities within the health system. Determine which standard technologies have been adopted (e.g., electronic health record (EHR), HIS, care management system (CMS)) and what health standards are in use (e.g., ICD, CPT LOINC, HL7). +- **manage changes to data standards & architecture** – establish a governance process with key health systems stakeholders to review request for changes to the transaction, data standards and systems architecture. + +Figure VI.1 Illustrates the collaborative development framework. + +![A flowchart titled 'Collaborative development framework' showing five sequential steps: Define health problem, Define health system stakeholders, Define health transactions, Define common health data schema, and Define system architecture. Each step has a corresponding description box below it. A central bar labeled 'Assess e-health readiness' spans across the middle. Below this bar is a box for assessing capabilities and a 'Manage changes to data standards and architecture' box with its own description.](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +**Define health problem** + +**Define health system stakeholders** + +**Define health transactions** + +**Define common health data schema** + +**Define system architecture** + +**Desired Health outcomes:** + +- Mortality, morbidity/disease burden, life expectancy; +- Disease-specific outcomes + +**Operational** + +- Regulation +- Patient education +- Telehealth, m-health +- Integration with non-healthcare sector + +Identify health system stakeholders that need to be involved to solve the health problem (e.g., health providers, health payers, health authority, patients, etc.). Establish a governance body that includes all the key health system's stakeholders + +Identify the transactions that need to be implemented to exchange the required data to solve the health problem (e.g., claims submission, e-prescription, screening data transmission) + +Identify the data standard data element required for each transactions to exchange the required information between the health system participant (e.g., patient information, screening data) + +Based on current eHealth system assessment and technology capabilities, determine the system architecture required to enable the transaction and data exchange + +**Assess e-health readiness** + +Assess e-health capabilities within the health systems. Determine which standard technologies have been adopted (EHR, HIS, CMS) and what health standards are in use (ICD, CPT LOINC, HL7, etc.) + +**Manage changes to data standards and architecture** + +Establish a governance process with key health systems stakeholders to review request for changes to the transaction, data standards and systems architecture + +H.860(14)\_FVI.1 + +A flowchart titled 'Collaborative development framework' showing five sequential steps: Define health problem, Define health system stakeholders, Define health transactions, Define common health data schema, and Define system architecture. Each step has a corresponding description box below it. A central bar labeled 'Assess e-health readiness' spans across the middle. Below this bar is a box for assessing capabilities and a 'Manage changes to data standards and architecture' box with its own description. + +**Figure VI.1 – Collaborative development framework** + +Below are two illustrative examples of health markets, including the characteristics of the market and the unmet need(s) addressed by the data standard set out in this Recommendation. + +### **VI.1 National workflow in a high resource setting** + +#### **VI.1.1 Characteristics of a high resource setting** + +- 1) Well-established healthcare system +- 2) Health system structure may feature: + - a) Health insurance (with one or more payers and one or more providers) + - b) A form of internal provider-payer/commissioner market (e.g., national health service (NHS) England) + - c) No payer-provider split +- 3) Likely to feature legacy health IT systems and well-established e-health components (e.g., EHR, telehealth) and established health standards (e.g., CPT, ICD, LOINC, HL7). + +#### **VI.1.2 Health problems to be solved in a high resource setting** + +- 1) Functional integration of existing health IT systems to deliver: + - a) Greater transparency on health outcomes and their determinants (e.g., quality metrics) + - b) Ultimately, better health outcomes +- 2) Achievement of health system efficiency gains through better coordination of clinical care across institutional boundaries +- 3) Creation of population health approaches based on the integration of health data from multiple sources +- 4) Creation of "asset based" community health approaches that are integrated with healthcare system approaches. + +### **VI.2 National workflow in a low resource setting** + +#### **VI.2.1 Characteristics of a low resource setting** + +- 1) Relative lack of an established healthcare system (for example, insufficient suppliers of healthcare to meet population demand) +- 2) Health system structure may feature: + - a) Health insurance (with one or more payers and one or more providers) + - b) Form of internal provider-payer/commissioner market (e.g., NHS England), or + - c) No payer-provider split. +- 3) Limited and fragmented implementation of health IT systems (e.g., e-health, EHR, HIS, CMS). + +#### **VI.2.2 Health problems to be solved in a low resource setting** + +- 1) Support for creation of basic health IT functionality (e.g., EHR, disease and treatment registries, electronic claims processing (where there is health insurance), e-prescription) +- 2) Implementation of basic health IT systems (e.g., clinic management software (CMS) and hospital information systems (HIS), electronic claims processing, health information exchange (HIE)) +- 3) Ensure strong functionality and foundation for additional functional development whilst ensuring compatibility with low bandwidth environments (including basic mobile) + +- 4) Ensure system is capable of managing information governance as it continues to evolve, including dynamic consent. + +#### **VI.2.3 Illustrative scenario – enable health screening in rural areas** + +In this scenario, rural areas have low access to healthcare. Residents often have to travel hours to get to a healthcare facility. The cost to get to a healthcare facility (both direct and lost opportunity costs) often far exceeds the cost of treatment. To overcome this, an NGO has been established to send social workers to the rural areas and provide basic health screening and basic medical care. + +While technology is used to screen patients and capture basic clinical data, it is often a manual and time-consuming process to aggregate and analyse the data. The NGO will also need to share data with healthcare providers to establish an EHR. They will need to submit the clinical data to health payers to get reimbursed for their services and finally they will benefit from sending the data to the health regulator for them to build population health data statistics. + +The collaborative development framework will be used to solve this health problem: + +- **define health problem** – enable transmission of rural screening data to participants of the national health system, +- **define health systems stakeholders** – identify which health entity will be exchanging the data (i.e., NGO, health provider, patient, health insurance, health regulator), +- **define health transaction** – data submit to health provider, claims submission to health insurance, data submit to health regulator, +- **define common health data schema** – identify which of the data standards data elements are required for each transaction identified (e.g., patient, activity, observation, diagnosis, claim), +- **define system architecture** – determine what cost effective technology can be used to capture and transmit rural health screening information (mobile table, web based technologies, [b-ITU-T H.810] certified devices). + +## Appendix VII + +### Continua Design Guidelines – Illustrative use case + +(This appendix does not form an integral part of this Recommendation.) + +The Continua Design Guidelines in [b-ITU-T H.810] contain specifications to ensure the interoperability of devices used for applications monitoring personal health. It enables the end-to-end, plug-and-play connectivity of devices and services for personal health management and healthcare delivery. + +ITU-T H.810 certified devices are one of many source systems that feed into the ITU-T H.860 system. They provide personal health data (e.g., temperature, heart rate and blood glucose) transmitted using existing industry standards [b-HL7 CDA R2]. + +Systems using ITU-T H.860 consume the data output from ITU-T H.810 devices and transform the data packets to the ITU-T H.860 format. See Figure VII.1. + +In Figure VII.2, ITU-T H.860 systems receive the HL7 CDA R2 formatted message from the ITU-T H.810 device. The ITU-T H.860 system will parse the message and extract and transform the necessary data. + +![Diagram of ITU-T H.810 and ITU-T H.860 architecture showing data flow from various health monitoring devices through a WAN interface to a backend system and then to various health record systems.](802707b774f2d2973b49cea2020e8453_img.jpg) + +The diagram illustrates the architecture for health monitoring data flow. On the left, a box titled "Facility office home mobile" contains an "Application hosting device" (WAN observation sender) connected to three types of ITU-T H.810 devices: TAN device (TAN-IF), PAN device (PAN-IF), and LAN device (LAN-IF). Below this, icons represent various health monitoring scenarios: a person with a blood pressure cuff, a person with a scale and a heart rate monitor, and a person on an exercise bike. A green line labeled "WAN interface" connects the "WAN observation sender" to a "WAN device" (WAN observation receiver) in the "Backend" box on the right. The "WAN device" is connected to an "HRN device", which in turn is connected to three boxes: "PHRs", "Physician EMRs", and "EHRs". These three boxes are collectively labeled as "ITU-T H.860 systems". A legend at the bottom left indicates that asterisks (\*) represent ITU-T H.810 devices and interfaces. The diagram is labeled H.860(14)\_FVII.1 at the bottom right. + +Diagram of ITU-T H.810 and ITU-T H.860 architecture showing data flow from various health monitoring devices through a WAN interface to a backend system and then to various health record systems. + +Figure VII.1 – ITU-T H.810 and ITU-T H.860 architecture + +![Figure VII.2 – ITU-T H.810 and ITU-T H.860 conceptual architecture. The diagram shows a central cloud representing the ITU-T H.860 system, containing an HRN receiver device, service functions (Security, Validation, Analysis), and a controlling function. Data flows from ITU-T H.810 personal health devices (Application hosting device, WAN device, HRN sender device, TAN device, PAN device, LAN device) through the cloud to mobile applications and devices, and to a healthcare provider. The healthcare provider sends claims and authorization requests to the cloud, which in turn sends remittance and authorization back to the provider. A patient is also shown connected to the cloud.](6f11044c88ea04e43de06c3491defeee_img.jpg) + +The diagram illustrates the conceptual architecture for ITU-T H.810 and ITU-T H.860. At the top, a dashed green box labeled 'ITU-T H.810 personal health devices' contains an 'Application hosting device' connected to a 'WAN device' and an 'HRN sender device'. The 'Application hosting device' is also connected to 'TAN device', 'PAN device', and 'LAN device' via 'TAN-IF', 'PAN-IF', and 'LAN-IF' respectively. The 'WAN device' and 'HRN sender device' are connected to a central cloud. The cloud contains an 'HRN receiver device' and three functional blocks: 'Service function' (with 'Security function'), 'Validation engine', and 'Analysis engine'. Below the cloud, a 'Healthcare provider' sends 'Claims' and 'Authorization requests' to the cloud, which responds with 'Remittance' and 'Authorization'. A 'Patient' is also connected to the cloud. To the right, 'Clinical measurement via HL7 CDA R2' and 'Health and wellness data' are shown being processed by 'Mobile applications and devices' (represented by an 'app' icon and smartphones). The text 'H.860(14)\_FVII.2' is in the bottom right corner. + +Figure VII.2 – ITU-T H.810 and ITU-T H.860 conceptual architecture. The diagram shows a central cloud representing the ITU-T H.860 system, containing an HRN receiver device, service functions (Security, Validation, Analysis), and a controlling function. Data flows from ITU-T H.810 personal health devices (Application hosting device, WAN device, HRN sender device, TAN device, PAN device, LAN device) through the cloud to mobile applications and devices, and to a healthcare provider. The healthcare provider sends claims and authorization requests to the cloud, which in turn sends remittance and authorization back to the provider. A patient is also shown connected to the cloud. + +**Figure VII.2 – ITU-T H.810 and ITU-T H.860 conceptual architecture** + +The following examples illustrate the outputs from ITU-T H.810 devices (in HL7 CDA R2 format) and the conversion of the relevant elements of the ITU-T H.810 continua data to the ITU-T H.860 format. + +The example below illustrates extracts from: + +- 1) pulse oximeter +- 2) thermometer. + +In the examples below, the ITU-T H.860 system will extract the following information: + +- **activity:** Activity.Start, Activity.ID, Activity.End, +- **observation:** Observation.Type, Observation.Code, Observation.ValueType, Observation.Value. + +### VII.1 Continua pulse oximeter reading + +Figure VII.3 displays the output of an [b-ITU-T H.810] compliant pulse oximeter. The output is in HL7 CDA R2 format. + +``` + + + + + +``` + +``` + + + +Continua CESL 1.5 PHMR Document + + + + + + + + + + + + + + + + + + John + Smith + + + + + + + + + + +``` + +``` + + + + + + + + Good Health Clinic + + + 58 Dover Rd. + Durham + NH + 03857 + USA + + + + + + + + + 42 End O' The Universe +Lane + Magrathea + Confusion + 12345 + The Universe + + + + + + Dr. + Zaphod + Beeblebrox + + + + Heart of Gold Hospital + + + 42 End O' The Universe +Lane + Magrathea + Confusion + 12345 + The Universe + + + + + + + +``` + +``` + + + + + GUI Manager + CESL + + + + + + + + + + + + + + + + +
    + + + + Vital Signs + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + +moodCode="EVN"> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + +
    +     + +
    + + + + Medical Equipment + +
    +     + +
    + + + + Results + No Results. +
    +     +     +     +     + +``` + +**Figure VII.3 – Output of an ITU-T H.810 compliant pulse oximeter** + +Figure VII.4 displays the transformation of the [b-ITU-T H.810] compliant pulse oximeter HL7 message into the ITU-T H.860 format. + +``` + + + 2.16.840.1.113883.1.3 + 2013-12-18T06:27:06Z + 2 + 2010F + 2013-12-18T06:27:06Z + + SNOMED + 431314004 + % + 97.5 + + + SNOMED + 78564009 + bpm + 80.0 + + + SNOMED + 431314004 + % + 99 + + + SNOMED + 78564009 + bpm + 86.8 + + +``` + +**Figure VII.4 – Pulse oximeter HL7 message converted into the ITU-T H.860 format** + +### VII.2 Continua thermometer reading + +Figure VII.5 displays the output of an [b-ITU-T H.810] compliant thermometer. The output is in [b-HL7 CDA R2] format. + +``` + +> + +
    + + + + Medical Equipment + + + + + + + + +``` + +``` + + + + + + + + + + + + + + +
    System TypeSystem ModelSystem ManufacturerSystem IDProduction SpecRegulated
    Blood Pressure MonitorPulse Master 2000Acme1F-3E-46-78-9A-BC-DE-F1 + Unspecified: + Serial Number: 584216
    + Part Number: 69854
    + Hardware Revision: 2.1
    + Software Revision: 1.1
    + Protocol Revision: 1.0
    + Prod Spec GMDN: +     		Regulated
    +     + + + + + + + Regulated Device + + + + + + + + + + + + + + + +``` + +``` + + + Model: Pulse Master 2000 + Serial number:584216 + Part number: 69854 + Hardware revision: 2.1 + Software revision: 1.1 + Protocol revision: 1.0 + Unspecified (free text comment): + + + + Acme + + + + + + + + + + + +
    + +
    + + + + Vital Signs + + Thermometer Results + + + + + + + + + + + + + + + +
    Date/TimeBody TempFinger TempOral Temp
    2008050110403399.9 deg F88.8 deg F37.5 deg C
    +     + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + "/> + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + +
    + +``` + +**Figure VII.5 – Output of an ITU-T H.810 compliant thermometer** + +Figure VII.6 displays the transformation of the [b-ITU-T H.810] certified thermometer reading HL7 message into the ITU-T H.860 format. + +``` + + + + 42505310606 + 2008-05-11T10:40:33Z + 2 + CCCCC + 2008-05-11T10:40:33Z + + SNOMED + 386725007 + degF + 99.9 + + + SNOMED + 433588001 + degF + 88.8 + + + SNOMED + 415945006 + Cel + 37.5 + + + +``` + +**Figure VII.6 – Thermometer HL7 message converted into the ITU-T H.860 format** + +## Bibliography + +- [b-ITU-T H.810] Recommendation ITU-T H.810 (2013), *Interoperability design guidelines for personal health systems*. +- [b-ITU-T X.680] Recommendation ITU-T X.680 (2008) | ISO/IEC 8824-1:2008, *Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation*. +- [b-ITU-T TWR-EH-2011] ITU-T Technology Watch Report (January 2011), *Standards and eHealth*. +[https://www.itu.int/dms\\_pub/itu-t/oth/0B/15/T0B1500000B3302PDFE.pdf](https://www.itu.int/dms_pub/itu-t/oth/0B/15/T0B1500000B3302PDFE.pdf) +- [b-ITU-T TWR-EH-2012] ITU-T Technology Watch Report (April 2012), *E-health Standards and Interoperability*. +[http://www.itu.int/dms\\_pub/itu-t/oth/23/01/T23010000170001PDFE.pdf](http://www.itu.int/dms_pub/itu-t/oth/23/01/T23010000170001PDFE.pdf) +- [b-HL7-RIM] Health Level Seven (2005-04), *HL7 Reference Information Model*. + +- [b-HL7 CDA R2] Health Level Seven (2005-04), *HL7 Clinical Document Architecture, Release 2.0*. +[http://www.hl7.org/documentcenter/private/standards/cda/r2/cda\\_r2\\_normativewebedition2010.zip](http://www.hl7.org/documentcenter/private/standards/cda/r2/cda_r2_normativewebedition2010.zip) +- [b-IETF RFC 2616] IETF RFC 2616 (1999), *Hypertext Transfer Protocol -- HTTP/1.1*. +- [b-IETF RFC 2818] IETF RFC 2818 (2000), *HTTP Over TLS*. +- [b-ISO/IEEE 11073] IEEE 11073, Family of standards: *Health informatics – Medical/health device communication standards*. +- [b-W3C XML 1.0] W3C XML1.0 (2008), *Extensible Markup Language (XML) 1.0*. +- [b-Podolak] Podolak I., Harrison O., Vetter P. (2012), *Measuring health data management maturity in Abu Dhabi*, Health Policy and Technology, September, Vol. 1, Issue 3; pp. 127-136. +- [b-UK CP] UK Caldicott Principles (revised as Version 2, 2013), + and +[https://www.gov.uk/government/uploads/system/uploads/attachment\\_data/file/192572/2900774\\_InfoGovernance\\_accv2.pdf](https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/192572/2900774_InfoGovernance_accv2.pdf) +- [b-Vetter] Vetter P., Boecker K. (2012), *Benefits of a single payment system: Case study of Abu Dhabi health system reforms*, Health Policy, Dec. 108(2-3):105-14. +- [b-US HIPAA] US HIPAA (Health Insurance Portability and Accountability Act) Law (1996) + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.861.1-201803-I_PDF-E/raw.md b/marked/H/T-REC-H.861.1-201803-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..01f0871cd3230ad9f042abd1161266e4eb57821c --- /dev/null +++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/raw.md @@ -0,0 +1,566 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.861.1** + +(03/2018) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia services and applications – +Multimedia e-health data exchange services + +# --- **Requirements on establishing brain healthcare quotients** + +Recommendation ITU-T H.861.1 + +## ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence | H.420–H.429 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T H.861.1 + +# Requirements on establishing brain healthcare quotients + +## Summary + +Recommendation ITU-T H.861.1 describes healthcare indices derived from neuroimaging analysis that are called brain healthcare quotients (BHQs), intended to be used for facilitating the communication of information about brain status. It describes the requirements on how such an index is created and also how some concrete BHQs can be defined and calculated. This Recommendation also includes examples of services using BHQs to better monitor health for supporting active and alert living. By its defining requirements, BHQs are linked to various healthcare aspects of human life and can be used to improve lifestyles. It gives standardized measurements and indices of brain conditions for specialists and non-specialists. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.861.1 | 2018-03-29 | 16 | 11.1002/1000/13572 | + +## Keywords + +Brain, e-health, multimedia brain information platform, MBI-PF, neuroimaging. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Background..... | 3 | +| 7 Brain healthcare quotients ..... | 4 | +| 7.1 Types of MRI images ..... | 4 | +| 7.2 Types of BHQs ..... | 5 | +| 7.3 Uses of BHQ..... | 5 | +| 7.4 Requirements for creating a brain healthcare quotient..... | 5 | +| Annex A – The GM-BHQ grey matter volume index ..... | 7 | +| A.1 Definition..... | 7 | +| A.2 GM-BHQ and health aspect: ageing..... | 7 | +| Annex B – The FA-BHQ fractional anisotropy index ..... | 9 | +| B.1 Definition..... | 9 | +| B.2 FA-BHQ and health aspect: ageing..... | 10 | +| Appendix I – Example method for obtaining GM-BHQ and FA-BHQ..... | 11 | +| Appendix II – An example of reproducibility tests at different facilities ..... | 12 | +| Appendix III – A practical use case: BHQ for citizens..... | 13 | +| Bibliography..... | 14 | + + + +# Recommendation ITU-T H.861.1 + +# Requirements on establishing brain healthcare quotients + +## 1 Scope + +This Recommendation describes the requirements of a brain healthcare quotient (BHQ), a healthcare index derived from neuroimaging analysis intended to be used for facilitating the communication of information on brain status. It describes the requirements on how such an index is created and also how some concrete BHQs can be defined and calculated. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.861.0] Recommendation ITU-T H.861.0 (2017), *Requirements on communication platform for multimedia brain information*. + +[ISO 12052] ISO 12052:2006 (2017), *Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management*. + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 brain healthcare quotient** [ITU-T H.861.0]: A numerical indicator representing physical characteristics of the brain that are purported to be indicative of some state of a health related condition. + +**3.1.2 magnetic resonance imaging** [ITU-T H.861.0]: A medical imaging technique used in radiology to investigate the anatomy and physiology of the body in both health and disease. + +**3.1.3 multimedia brain information platform** [ITU-T H.861.0]: A platform for exchange information and data concerning the brain such as MRI data. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 brain dry dock examination**: A form of preventive medicine, coined after "human dry-dock", where examinations with typical MRIs are conducted to check for brain-related problems. + +**3.2.2 diffusion tensor imaging (DTI)**: A magnetic resonance imaging technique that enables the measurement of the restricted diffusion of water in tissue, in order to produce neural tract images instead of using this data solely for the purpose of assigning contrast or colours to pixels in a cross-sectional image. + +**3.2.3 fractional anisotropy:** A scalar value between zero and one that describes the degree of anisotropy of a diffusion process. It is a measure often used in diffusion imaging where it is thought to reflect fibre density, axonal diameter and myelination in white matter. It is taken as a useful measure of connectivity in the brain that can be derived from the diffusion tensor imaging (DTI) dataset. + +**3.2.4 grey matter:** A major component of the central nervous system, consisting of neuronal cell bodies, neuropil (dendrites and myelinated, as well as unmyelinated axons), glial cells (astroglia and oligodendrocytes), synapses and capillaries. + +**3.2.5 human dry-dock:** A system of general medical check-up or health appraisal, where a voluntary (supposedly healthy) client undergoes a series of medical examinations, such as blood tests, urine and faecal tests, X-rays and ultrasonography, over the course of one or two days, after which the results of the tests are explained to the client in a consultation with a doctor, with some advice on how the client can maintain his/her health. + +**3.2.6 (brain) morphometry:** The measurement of brain structures and changes thereof during development, ageing, learning, disease and evolution. Since autopsy-like dissection is generally impossible on living brains, brain morphometry starts with non-invasive neuroimaging data, typically obtained from magnetic resonance imaging (MRI). + +**3.2.7 voxel-based morphometry:** A neuroimaging analysis technique that allows the investigation of focal differences in brain anatomy using a statistical approach. + +**3.2.8 white matter:** Areas of the central nervous system that are mainly made up of myelinated axons (also called tracts). + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|---------------------------------------| +| AAL | Automated Anatomical Labelling | +| AHI | Apnoea–Hypopnoea index | +| BDE | Brain dry Dock Examination | +| BHQ | Brain Healthcare Quotient | +| DTI | Diffusion Tensor Imaging | +| FA | Fractional Anisotropy | +| FA-BHQ | Fractional Anisotropy – BHQ | +| FMRI | Functional Magnetic Resonance Imaging | +| GM | Grey Matter | +| GM-BHQ | Grey Matter-BHQ | +| GMV | Grey Matter Volume | +| KPIs | Key Performance Indicators | +| MBI-PF | Multimedia Brain Information Platform | +| MRI | Magnetic Resonance Imaging | +| VBM | Voxel-Based Morphometry | +| WM | White Matter | + +# 5 Conventions + +The following conventions are used in this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. + +# 6 Background + +It is understood that the multimedia brain information platform (MBI-PF) should be able to exchange not only imaging data (e.g., MRI data which experts only can use) but metadata about brain functions, including indicators of brain health level, which is useful for various application services for e-health (e.g., monitoring one's health status of the brain, evaluating lifestyles from the point of brain health). + +Such indicators are important in practice as MRI data sometimes cannot so easily be interpreted. Even when continuous monitoring of the brain is possible, some minute differences and changes over time can be overlooked, resulting in a grave situation when the change is clearly visible to the human eye. + +Brain images contain a variety of information, but the conventional medical model often failed to provide useful information for cases other than clear cases of brain disorders. For example, in a typical brain dry dock examination (BDE), a patient would often ask the doctor about the health status of his brain, but often all the doctor can say is "it is normal for your age". In fact, whether the patient is really "normal for his age" is the subjective opinion of the doctor. + +On the other hand, studies based on brain imaging have shown that the brain can change due to various factors, such as: + +- ageing shrinks brain size; +- some diseases shrink the brain; +- some activities such as learning can enlarge the brain. + +It is also to be noted that various "indicators" are used in many healthcare and medical areas. Examples are the atherogenic index for cardiovascular disease and the apnoea–hypopnoea index (AHI) for sleep apnoea syndrome. Considering the fact that these indices are used successfully to raise awareness of a patient's heart condition and sleep quality, there is a possibility that citizens can have a better understanding of his or her own brain if brain information can be represented by an indicator using the images ordinarily obtained by general brain health screening using MRI. Moreover, such an index may help citizens to reconsider how they manage their brain healthcare. + +This point becomes more salient when data is exchanged among different organizations, because these organizations may have different equipment, with different makes and features. The resulting data may be readily interpreted by the experts who are accustomed to the equipment, but not by other equally qualified experts. + +Therefore, it is necessary to describe the well-managed criteria for creating and using such indicators of brain health for sustainable growth of e-health services of the brain. + +# 7 Brain healthcare quotients + +This clause describes the background rationale for a BHQ and the types of BHQ derived from, specifically the grey matter-BHQ (GM-BHQ) and the fractional anisotropy – BHQ (FA-BHQ). + +The definition of other quotients is for further study. + +### 7.1 Types of MRI images + +There are several MRI techniques generally used in BDE. For example: + +- T1 weighted image: this is one of the basic pulse sequences in MRI and demonstrates differences in the T1 relaxation times of tissues. This is appropriate for seeing the "shape" of the brain. +- T2 weighted image: this is appropriate for seeing "diseases" such as cerebral infarction and encephalitis. +- Diffusion-weighted image: this is appropriate for observing acute strokes. + +In practice, these images are evaluated by "visual inspection". This means that considerable amount of training is necessary to correctly "see" or gather information from these images. + +There are other MRI techniques that are expected to be used more often in BDE, such as: + +- Diffused tensor image: this can help evaluate the "nerve fibres" of the brain. +- Resting-state functional MRI (fMRI): this can evaluate the network (connectivity) of brain. + +In any of these methods, the original raw image cannot be directly evaluated but has to be processed with imaging processes to provide useful information. + +Neuroscientific findings have shown that several well-known quantitative features of the brain can be associated with the characteristics of brain functions. For example, the volume of grey matter (GM) is associated with various learning possibilities, whereas the complexity in white matter (WM) is associated with the efficiency of information transmission. There already exists systematic means to measure and quantify these characteristics in a scientifically viable way. + +These quantitative characteristics in turn are sometime linked to some human properties related to health, such as age or gender. If these quantitative features of the brain can be universally obtainable in statistically significant ways, these quantities can be interpreted as indicating aspects of health-related properties and thus can be used as "indices" for these aspects of the brain. + +These indices are defined here as brain healthcare quotients (BHQs). Once established, it is expected that BHQs can be used not only by experts but also by non-experts. + +The purpose here is to represent the information about (healthy) the brain in a simple format (i.e., as a number), taking into account the following factors: + +- the brain has diversity, as with individuals; +- the biggest factor for shrinking the brain is "ageing"; +- the level of shrinking can change depending on the region of the brain; +- in a disease model, "localized/regional" information is sought after, from the "healthcare" point of view; it is more understandable with a simple value. + +Thus the requirement on such an index (BHQ) is that although analysing each region of brain, the final result is represented as an integrated value, which will provide a value which is easily understood by, e.g., a subject in BDE. + +## 7.2 Types of BHQs + +Two types of BHQ are described in annexes A and B: GM-BHQ based on the volume of GM, as assessed by voxel-based morphometry (VBM), and FA-BHQ based on the FA value of WM, as assessed by Diffusion tensor imaging (DTI) analysis. + +Methods that are well established and proven to have high reproducibility are chosen to represent these physical features. Thus: + +- Grey matter: voxel-based morphometry (VBM) is adopted; +- White matter: voxel-based analysis using FA image is adopted. + +BHQs other than GM-BHQ and FA-BHQ are also plausible. For example, quantification of hyper-intensities reflecting ischemic changes of the brain can be the white-matter hyper-intensity BHQ (WMH-BHQ). Though both GM-BHQ and FA-BHQ are based on measurements of the whole brain, it is plausible to think of a BHQ based on measurements of a specific area of the brain. Also there can be a BHQ related to a health aspect other than age. For example, a certain type of BHQ may be found to be correlated to some blood components. These other potential BHQs are for future study. + +The following figure shows the relationship between these BHQs. + +![A hierarchical diagram showing the relationship between different types of Brain Health Quotients (BHQs). At the top level is 'BHQ'. Below it, 'GM-BHQ' and 'FA-BHQ' are shown as branches. Further down, there are two more branches labeled '....-BHQ' and '....-BHQ', which are grouped by a bracket labeled 'For future study'. The diagram is labeled 'H.861.1(18)_F01' at the bottom right.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +``` +graph TD; BHQ --> GM-BHQ; BHQ --> FA-BHQ; BHQ --> P1[....-BHQ]; BHQ --> P2[....-BHQ]; P1 & P2 --- FFS[For future study]; FFS --- H861118_F01[H.861.1(18)_F01]; +``` + +A hierarchical diagram showing the relationship between different types of Brain Health Quotients (BHQs). At the top level is 'BHQ'. Below it, 'GM-BHQ' and 'FA-BHQ' are shown as branches. Further down, there are two more branches labeled '....-BHQ' and '....-BHQ', which are grouped by a bracket labeled 'For future study'. The diagram is labeled 'H.861.1(18)\_F01' at the bottom right. + +**Figure 1 – Relationship between different BHQs** + +## 7.3 Uses of BHQ + +BHQ can be used for several purposes: + +- It will allow the exchange of information about the brain in a standardized way. +As BHQ is a standardized index about a physical characteristic of the brain, it will allow the information, e.g., the size of GM, to be exchanged and utilized in different organizations and comparison can be made possible. +- It can be used to detect minute changes in the brain of a person in the course of time. +Since BHQ is numerical and easily calculated with an algorithm, it is easy to detect a very small change in the physical makeup of the brain of a person. Such a small change may not be easily detected by looking at the actual image from MRI. This feature of BHQ can be utilized to monitor temporal changes of the brain of a person, leading to early detection of any significant features that may affect that person. +- It can be used in combination with other health indices. +Since BHQ is a numerical index it can be combined with other indices, for example, AHI, to see if there is a correlation between the state of the brain and other symptoms of that person. + +## 7.4 Requirements for creating a brain healthcare quotient + +Depending on the type of brain data or metadata exchanged on the MBI-PF, or on services or applications utilizing such data, there could be various types of BHQ. It is sought to define KPIs in the creation of the BHQ itself, and also in service operation. + +The selection of indicators for creating a BHQ is based inter alia on the following principles: + +- The BHQ is required to be built on the basis of neuroscience. + +- The BHQ is required to be derived from neuroimaging analysis. +- The BHQ is required to consider the regional differences of the brain. +- The BHQ is required to be linked to healthcare aspects. +- The BHQ is required to represent the state of health-related conditions. +- The BHQ is required to employ a standardized score (e.g., mean of population is 100 and 1 standard deviation is 15, so that 95% of population falls within the range of 70-130.). +- The BHQ is recommended to be built upon an established method to assure its validity. +- The BHQ is recommended to be tested for reproducibility at different facilities. + +## Annex A + +### The GM-BHQ grey matter volume index + +(This annex forms an integral part of this Recommendation.) + +### A.1 Definition + +GM-BHQ is an index that represents "brain volume" considering regional differences of the brain. Grey matter is a major component of the central nervous system and it consists of neuronal cell bodies, neuropil (dendrites and myelinated, as well as unmyelinated axons), glial cells (astroglia and oligodendrocytes), synapses and capillaries. + +![MRI image of GM. The image shows a cross-section of a brain with a highlighted region of grey matter. A dashed box labeled 'Object of indicator' zooms in on the highlighted area. The image is labeled 'MRI' and 'H.861.1(18)_FA.1'.](eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg) + +MRI image of GM. The image shows a cross-section of a brain with a highlighted region of grey matter. A dashed box labeled 'Object of indicator' zooms in on the highlighted area. The image is labeled 'MRI' and 'H.861.1(18)\_FA.1'. + +Figure A.1 – MRI image of GM + +In GM, an appropriate amount of expanse of dendrites and a reasonable increase in synapses of the neural cells are thought to be signs of a good state of health [b-Erickson]. This good health induces high plasticity in synapses and can be interpreted as indicating flexibility of learning in the future [b-Kandel]. This brain state is reflected in the GM volume [b-Ashburner]. GM-BHQ is the indicator that quantifies the volume of GM. + +Voxel-based morphometry (VBM) is one of the well-known neuroimaging analysis techniques that allows investigation of focal differences in brain anatomy. It uses a statistical approach of statistical parametric mapping. GM-BHQ is defined by the volume of GM, as assessed by VBM. + +GM-BHQ is obtained with a two-step procedure. First, local GM-BHQs is calculated for 116 regions of the brain. Then, the (Global) GM-BHQ is defined as the sum of the local GM-BHQs. The formula for GM-BHQ is as follows; + +$$(Global) GM\_BHQ = \frac{1}{n} \sum_{j=1}^n \left( 100 + 15 \times \frac{SubGMV_j - C_{meanj}}{C_{sdj}} \right)$$ + +where: + +$j$ : region of brain based on certain atlases + +$SubGMV_j$ : grey matter volume (GMV) of a subject in region $j$ + +$C_{meanj}$ : average of GMV of control subjects + +$C_{sdj}$ : standard deviation of GMV of control subjects + +### A.2 GM-BHQ and health aspect: ageing + +Figure A.2 shows that the value of GM-BHQ significantly declines as people become older. This indicates that ageing decreases the volume of GM. + +**GM-BHQ** + +![Scatter plot showing the correlation between GM-BHQ and AGE. The y-axis is labeled GM-BHQ and ranges from 70.0 to 130.0. The x-axis is labeled AGE and ranges from 10 to 70. A dashed regression line is shown with the equation y = -0.57x + 128 and R² = 0.34. The plot is labeled H.861.1(18)_FA.2.](0b8b087a7baa471015d3ffeaa43d9a6c_img.jpg) + +A scatter plot showing the relationship between GM-BHQ (Y-axis) and AGE (X-axis). The Y-axis ranges from 70.0 to 130.0 with major grid lines every 10.0 units. The X-axis ranges from 10 to 70 with major grid lines every 10 units. There are approximately 50 data points represented by blue dots. A dashed black regression line is drawn through the data points, showing a negative correlation. The regression equation $y = -0.57x + 128$ and the coefficient of determination $R^2 = 0.34$ are displayed in the bottom-left corner of the plot area. The plot is labeled H.861.1(18)\_FA.2 in the bottom-right corner. + +Scatter plot showing the correlation between GM-BHQ and AGE. The y-axis is labeled GM-BHQ and ranges from 70.0 to 130.0. The x-axis is labeled AGE and ranges from 10 to 70. A dashed regression line is shown with the equation y = -0.57x + 128 and R² = 0.34. The plot is labeled H.861.1(18)\_FA.2. + +**Figure A.2 – Correlation between GM-BHQ and ageing** + +## Annex B + +### The FA-BHQ fractional anisotropy index + +(This annex forms an integral part of this Recommendation.) + +### B.1 Definition + +White matter refers to the areas of the central nervous system that are mainly made up of myelinated axons. Healthy WM is reflected by dense axonal packing [b-Tromp], as well as the expanse of glial cells, which support nerve cells. + +![Figure B.1: FA image derived from DTI. The figure shows an MRI scan of a brain cross-section on the left, labeled 'MRI'. A small rectangular region is highlighted with an orange box. On the right, a magnified view of this region is shown, labeled 'Object of indicator'. The magnified view shows a dense network of white matter fibers. The image is labeled H.861.1(18)_FB.1 at the bottom right.](1145fc59efdc7dacc8d3c715d7ff3248_img.jpg) + +Figure B.1: FA image derived from DTI. The figure shows an MRI scan of a brain cross-section on the left, labeled 'MRI'. A small rectangular region is highlighted with an orange box. On the right, a magnified view of this region is shown, labeled 'Object of indicator'. The magnified view shows a dense network of white matter fibers. The image is labeled H.861.1(18)\_FB.1 at the bottom right. + +Figure B.1 – FA image derived from DTI + +The fibre density, axonal diameter and myelination in WM is typically associated with the value of fractional anisotropy. This value is taken as a useful measure of connectivity in the brain that can be derived from the DTI dataset. The transmission efficiency of the network between brain regions is thus supported by WM integrity, which is reflected in the FA of axons [b-Johansen-Berg], as measured by DTI. + +This is the basis of the FA-BHQ, based on the FA value of WM, as assessed by DTI. + +DTI has the following characteristics: + +- can be used to observe the microstructure of brain tissue and nerve fibres; +- used primarily for: + - visualizing neural fibres (tractography) + - evaluating the integrity of neural fibres. +- Primary parameters for evaluating the integrity: mean diffusivity (MD) and fractional anisotropy (FA): + - MD: index expressing how easy diffusion occurs (mean diffusivity (MD) describes the rotationally invariant magnitude of water diffusion within brain tissue); + - FA: index representing the degree of anisotropy the diffusion has. + +Similar to GM-BHQ, FA-BHQ is defined by the following equation: + +$$(Global) FA\_BHQ = \frac{1}{n} \sum_{j=1}^n \left( 100 + 15 \times \frac{SubFA_j - C_{mean_j}}{C_{sd_j}} \right)$$ + +where: + +*j*: region of brain based on certain atlases + +*SubFAj*: fractional anisotropy (FA) of a subject in region *j* + +*Cmeanj*: average of FA of control subjects + +*Csdj*: standard deviation of FA of control subjects + +### B.2 FA-BHQ and health aspect: ageing + +Figure B.2 shows that the value of FA-BHQ significantly declines as people become older. This may reflect brain deterioration as people age, which suggests that BHQ is an appropriate indicator for brain health status. + +![Scatter plot showing the correlation between FA-BHQ and AGE. The y-axis is labeled FA-BHQ and ranges from 90.0 to 110.0. The x-axis is labeled AGE and ranges from 20 to 70. A dashed regression line is shown with the equation y = -0.15x + 108 and R² = 0.13. The data points show a slight downward trend as age increases.](a430996a9e8993deb0c6b25da234744b_img.jpg) + +Figure B.2 is a scatter plot showing the correlation between FA-BHQ (Y-axis) and AGE (X-axis). The Y-axis ranges from 90.0 to 110.0, and the X-axis ranges from 20 to 70. A dashed regression line is shown with the equation $y = -0.15x + 108$ and $R^2 = 0.13$ . + +| AGE | FA-BHQ | +|-----|--------| +| 25 | 106.0 | +| 32 | 108.5 | +| 35 | 101.5 | +| 40 | 107.0 | +| 45 | 103.0 | +| 50 | 104.5 | +| 55 | 106.0 | +| 60 | 99.5 | +| 62 | 97.0 | + +H.861.1(18)\_FB.2 + +Scatter plot showing the correlation between FA-BHQ and AGE. The y-axis is labeled FA-BHQ and ranges from 90.0 to 110.0. The x-axis is labeled AGE and ranges from 20 to 70. A dashed regression line is shown with the equation y = -0.15x + 108 and R² = 0.13. The data points show a slight downward trend as age increases. + +**Figure B.2 – Correlation between FA-BHQ and ageing** + +FA-BHQ evaluates the integrity of fibre tract, and it builds on white matter, i.e., fibres that are connecting brain areas. + +## Appendix I + +### Example method for obtaining GM-BHQ and FA-BHQ + +(This appendix does not form an integral part of this Recommendation.) + +Figures I.1 and I.2 describe how GM-BHQ and FA-BHQ, respectively, can be obtained. + +![Flowchart for obtaining GM-BHQ. Steps: Calculate intracranial volume, Extract grey matter, Warp to standard space, Smoothing/proportional scaling. Control data: Calculate Z-score based on mean and standard deviation of control. Then, standardize voxel value by 100 + 15 × Z-score. Standardized image: Calculate local BHQ within regions defined by an atlas. Final step: Calculate (Global) GM-BHQ by averaging local BHQ.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +| File | AAL_1 | AAL_2 | AAL_3 | AAL_4 | +|----------|-------|-------|-------|-------| +| bhq_pV_M | 96.4 | 86.3 | 99.9 | 93.9 | +| bhq_pV_M | 111.5 | 109.9 | 102.3 | 100.8 | +| bhq_pV_M | 94.8 | 96.8 | 103.4 | 100.2 | + + + +| | DL | DM | | +|--|---------|---------|--------| +| | AAL_115 | AAL_116 | GM-BHQ | +| | 115.6 | 128.1 | 98.0 | +| | 92.4 | 101.1 | 102.6 | +| | 110.0 | 115.2 | 99.2 | + +H.861.1(18)\_FI.1 + +Flowchart for obtaining GM-BHQ. Steps: Calculate intracranial volume, Extract grey matter, Warp to standard space, Smoothing/proportional scaling. Control data: Calculate Z-score based on mean and standard deviation of control. Then, standardize voxel value by 100 + 15 × Z-score. Standardized image: Calculate local BHQ within regions defined by an atlas. Final step: Calculate (Global) GM-BHQ by averaging local BHQ. + +Figure I.1 – Example of how GM-BHQ can be obtained + +![Flowchart for obtaining FA-BHQ. Steps: Eddy current correction, Remove non-brain regions/calculate FA map, Warp to standard space. Control data: Calculate Z-score based on mean and standard deviation of control. Then, standardize voxel value by 100 + 15 × Z-score. Standardized image: Calculate local BHQ within regions defined by an atlas. Final step: Calculate (Global) FA-BHQ by averaging local BHQ.](21ad58fee90f2be50708ff541d225507_img.jpg) + +| File | JHU_1 | JHU_2 | JHU_3 | +|-----------|-------|-------|-------| +| bhq_pD_MR | 82.3 | 107.3 | 103.6 | + + + +| | AV | AW | AX | +|--|--------|--------|--------| +| | JHU_47 | JHU_48 | FA-BHQ | +| | 100.5 | 107.3 | 99.9 | + +H.861.1(18)\_FI.2 + +Flowchart for obtaining FA-BHQ. Steps: Eddy current correction, Remove non-brain regions/calculate FA map, Warp to standard space. Control data: Calculate Z-score based on mean and standard deviation of control. Then, standardize voxel value by 100 + 15 × Z-score. Standardized image: Calculate local BHQ within regions defined by an atlas. Final step: Calculate (Global) FA-BHQ by averaging local BHQ. + +Figure I.2 – Illustration of how FA-BHQ can be obtained + +## Appendix II + +### An example of reproducibility tests at different facilities + +(This appendix does not form an integral part of this Recommendation.) + +In the case of GM-BHQ and FA-BHQ, the data acquired at different MRI facilities are tested. Data is acquired at the Kyoto University (N=58) and the University of Tokyo (N=54), respectively. The relationship between age and BHQ showed the same trend with the brain data scanned at both facilities (GM-BHQ: The Pearson correlation coefficient R, R=0.57, b=-0.56, p<.001 at Kyoto University, R=0.55, b=-0.51, p<.001 at Tokyo University, FA-BHQ: R=0.36, b=-0.14, p<.01 at Kyoto University, R=0.36, b=-0.19, p<.01 at Tokyo University). Therefore, GM-BHQ and FA-BHQ have reproducibility as health indicators. + +## Appendix III + +### A practical use case: BHQ for citizens + +(This appendix does not form an integral part of this Recommendation.) + +Appendix III describes BHQ-School as a use case of BHQ, in which the general public uses BHQ. BHQ-School aims to find solutions that might potentially contribute to brain health by having BHQ widely used by not only researchers or companies but also the general public. + +For the general public to participate in BHQ-School, a person leverages "one's own BHQ" or "brain age" inferred from the BHQ to find solutions to maintain or improve brain health including diet and exercise matched to the brain health status, appropriate sleep duration to protect brain health, and hobbies or lifestyle environments to improve brain health. By sharing such activities of citizen scientists and researchers, it will enable the scientific discovery of the lifestyles that are good for brain health. + +![Diagram illustrating the connection between academia and citizen science via BHQ.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +The diagram, titled "Connecting academia and citizen science via BHQ", shows a flow from left to right. On the left, a blue circle contains two scientists in lab coats working with a brain scan and data. A line connects this circle to a central area. In the center, four icons represent different activities: "Drinking" (a man drinking from a cup), "Exercise" (a woman on a treadmill), "Hobby" (a person working at a desk), and "Nature" (a person watering plants). Each icon is connected to a small brain icon. Below these icons, a box states "Scientific discovery of brain-friendly lifestyles by citizen researchers". The entire central section is enclosed in a large green oval. In the bottom right corner, the text "H.861.1(18)\_FIV.1" is present. + +Diagram illustrating the connection between academia and citizen science via BHQ. + +Figure III.1 – Citizen science by BHQ + +## Bibliography + +- [b-Ashburner] Ashburner J, Friston KJ (2000), Voxel-based morphometry – *the methods*. Neuroimage, 11: 805-21. +- [b-Erickson] Erickson K.I., Leckie R.L. (2014), Weinstein AM, *Physical activity, fitness, and gray matter volume*. Neurobiol. Aging, 35 Suppl 2: S20-8. +- [b-Johansen-Berg] Johansen-Berg H (2010), *Behavioural relevance of variation in white matter microstructure*. Curr. Opin. Neurol., 23: 351-8. +- [b-Kandel] Kandel E, Schwartz J, Jessell T, Siegelbaum S, Hudspeth AJ. (2012), *Principles of Neural Science*. McGraw-Hill, New York. +- [b-Nemoto] Nemoto K, Oka H, Fukuda H, Yamakawa Y (2017), *MRI-based Brain Healthcare Quotients: A bridge between neural and behavioral analyses for keeping the brain healthy*. PLoS One, Oct 27;12(10). +- [b-Tromp] Tromp D, DTI Scalars (FA, MD, AD, RD) (2016), *How do they relate to brain structure?* The Winnower; 3: e146119.94778. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.862.0-201911-I_PDF-E/27b22513fc27a0ff5f230b062ad3112f_img.jpg b/marked/H/T-REC-H.862.0-201911-I_PDF-E/27b22513fc27a0ff5f230b062ad3112f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf522fd1c05ffe82095fd888f534dc46a45f921a --- /dev/null +++ b/marked/H/T-REC-H.862.0-201911-I_PDF-E/27b22513fc27a0ff5f230b062ad3112f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0ffc5a716f27ca2723bdb7d62a1566cf0dded2af0707734165df1246dfb544c +size 50901 diff --git a/marked/H/T-REC-H.862.0-201911-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.862.0-201911-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7 --- /dev/null +++ b/marked/H/T-REC-H.862.0-201911-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055 +size 6859 diff --git a/marked/H/T-REC-H.862.0-201911-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/H/T-REC-H.862.0-201911-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13cc10b80297817cab1588455deac50dc82d0593 --- /dev/null +++ b/marked/H/T-REC-H.862.0-201911-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1556aa5cbffc8bd5a2be614faedf5826949c9dd43870fee296824409eac6fee7 +size 47927 diff --git a/marked/H/T-REC-H.862.0-201911-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.862.0-201911-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56de98f5eb7e26fed0117153ac8cc7da63d251f2 --- /dev/null +++ b/marked/H/T-REC-H.862.0-201911-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:099a21176aca691a2b90bfa42f1aa673e3f8d385f1220618f3d7eccbe0785669 +size 33302 diff --git a/marked/H/T-REC-H.862.0-201911-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/H/T-REC-H.862.0-201911-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f7c4684181fb2f028a14ee4884c4a4221ee7f4d --- /dev/null +++ b/marked/H/T-REC-H.862.0-201911-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:106c01089a32afee145e6ea50e245b15b5e19a585e5094660eb51ae71f860829 +size 30823 diff --git a/marked/H/T-REC-H.862.0-201911-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.862.0-201911-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..404c3adc59e0a4fec96395c4c19a4eca5867a17a --- /dev/null +++ b/marked/H/T-REC-H.862.0-201911-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:250677a7ec356d2e54980c234781df4c891ddfb0f55dd4129c641c6d9557a559 +size 25667 diff --git a/marked/H/T-REC-H.862.0-201911-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.862.0-201911-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d87c0fc2cebfd2cf2019b0eb5c9c6da91e8ca11a --- /dev/null +++ b/marked/H/T-REC-H.862.0-201911-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f08ffd48b079ff025d48ddc0e6036b81b3bdbcf2d1a2b95491797065aa74b08 +size 53694 diff --git a/marked/H/T-REC-H.862.2-202008-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/H/T-REC-H.862.2-202008-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c725de63c53c5c823ee927b917db4fc2c3524288 --- /dev/null +++ b/marked/H/T-REC-H.862.2-202008-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d143ce0f6ce23e094cce1c2e60c76465f1bbfad8fceff715c45eea5c4c541bcd +size 26257 diff --git a/marked/H/T-REC-H.862.2-202008-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.862.2-202008-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/H/T-REC-H.862.2-202008-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/H/T-REC-H.862.2-202008-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.862.2-202008-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd399b22ddb259407e95527c8f68ea0d9a38631c --- /dev/null +++ b/marked/H/T-REC-H.862.2-202008-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a015a2b663b16ec0d3734379daea39ea05dd0ce456f7b113df0bc4af38efbedc +size 43350 diff --git a/marked/H/T-REC-H.862.2-202008-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/H/T-REC-H.862.2-202008-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13cf8479668b400fee30b270d157659e44ca0a8c --- /dev/null +++ b/marked/H/T-REC-H.862.2-202008-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:425f7258b5f92df1680805db53e0a0acf54a8943d9e8db83ad03bacdfa81c632 +size 27348 diff --git a/marked/H/T-REC-H.862.3-202008-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/H/T-REC-H.862.3-202008-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5961c6e0cef5e91c66700bc808e5220b5e1a465 --- /dev/null +++ b/marked/H/T-REC-H.862.3-202008-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aeb143b33aff230c0a6ffc61e34d287bbbd21454234dc4163729124bfd1d98b +size 31697 diff --git a/marked/H/T-REC-H.862.3-202008-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/marked/H/T-REC-H.862.3-202008-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53e18d552e421b566204ca52f40e0a2172715035 --- /dev/null +++ b/marked/H/T-REC-H.862.3-202008-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b700bf67b31cee683086b18f0dd8af2df16addc8bdadecadf001dcbddcafa68b +size 64668 diff --git a/marked/H/T-REC-H.862.3-202008-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.862.3-202008-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60ef77d0113b78491f8fd1fca72f1904a031c89e --- /dev/null +++ b/marked/H/T-REC-H.862.3-202008-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:107cfe2c98dc17ae4e735f861ba057606b5293ac62e1b8bcb137fd3ccc062c97 +size 7037 diff --git a/marked/H/T-REC-H.862.3-202008-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/H/T-REC-H.862.3-202008-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfb10544b84192ea58f45d3f966c4df837830235 --- /dev/null +++ b/marked/H/T-REC-H.862.3-202008-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6197c7ae66134eb3ba1fd2e7a01bb5f1f8db152a4626859946d5f82764d46fee +size 45783 diff --git a/marked/H/T-REC-H.862.3-202008-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/H/T-REC-H.862.3-202008-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b751d66a9a6bc56af5b0a5eddf8c55faa0878ed0 --- /dev/null +++ b/marked/H/T-REC-H.862.3-202008-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92cd21747d89140ca8433e79ddaa635efc6b5845330d4fff3fdea23699252aaf +size 76797 diff --git a/marked/H/T-REC-H.862.3-202008-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/H/T-REC-H.862.3-202008-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3736ff4e1015a83cc6aa223704edaccc88232eac --- /dev/null +++ b/marked/H/T-REC-H.862.3-202008-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:010ea66ad8800a3c24302a737f844eadb41a40a3843bb4fbeb70917233f5bf79 +size 56177 diff --git a/marked/H/T-REC-H.862.3-202008-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/H/T-REC-H.862.3-202008-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a9c5d001339eabe5f584f67b60e20e633b1b252 --- /dev/null +++ b/marked/H/T-REC-H.862.3-202008-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d09795f4c6a6d2dc2f2a1608ba8d7c9ba6ced27c08590e0257d7d943671aa7f9 +size 29420 diff --git a/marked/H/T-REC-H.862.4-202106-I_PDF-E/raw.md b/marked/H/T-REC-H.862.4-202106-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3ab0bb94f894758c7ccaafbc22509b75e322bf2c --- /dev/null +++ b/marked/H/T-REC-H.862.4-202106-I_PDF-E/raw.md @@ -0,0 +1,588 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.862.4** + +(06/2021) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Multimedia e-health data exchange services + +--- + +**Framework for information and communication +technology olfactory function test systems** + +Recommendation ITU-T H.862.4 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, sans-serif font superimposed on the globe. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Content delivery and ubiquitous sensor network applications | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.862.4 + +# Framework for information and communication technology olfactory function test systems + +## Summary + +Recommendation ITU-T H.862.4 defines the framework for information and communication technology (ICT) olfactory function test systems. The scope of this Recommendation is focused on the method of the olfactory function test generated by the perception of the user's condition, the mechanically controlled scents spray, the evaluation of the user's response, and the olfactory test procedures. + +The olfactory function test can be carried out by considering human factors related to the human olfactory. It can be sprayed by mechanically controlling a certain amount of fragrance. It is also possible to present a fragrance at intervals optimized for olfactory fatigue. In addition, it is possible to prevent the fragrance from being perceived completely differently due to the residual fragrance by solving the problem of fragrance mixing between olfactory tests through cleaning. + +The ICT olfactory function test system framework is largely composed of three stages. The first step is to judge the state of the user and determine whether it is possible to perform an olfactory test. The second step is to emit an appropriate fragrance and receive a response from the user according to the test procedure. The third step is to evaluate the user's olfactory ability by analysing the user's response to the test procedure. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.862.4 | 2021-06-13 | 16 | 11.1002/1000/14689 | + +## Keywords + +Dementia, human factors, ICT olfactory function test, scent diffusing system. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2021 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 1 | +| 6 Background..... | 1 | +| 7 System framework architecture ..... | 2 | +| 8 System framework entities ..... | 3 | +| 8.1 User data processing module..... | 3 | +| 8.2 Olfactory test management module..... | 4 | +| 8.3 Test procedure database module ..... | 4 | +| 8.4 Scent diffusing control module ..... | 5 | +| 8.5 Olfactory function test analysis module ..... | 5 | +| 9 Olfactory function test procedures..... | 6 | +| 9.1 Test odour identification..... | 6 | +| 9.2 Test olfactory threshold ..... | 6 | +| 9.3 Test olfactory recognition..... | 7 | +| 9.4 Test odour discrimination..... | 7 | +| Bibliography..... | 9 | + + + +# Recommendation ITU-T H.862.4 + +## Framework for information and communication technology olfactory function test systems + +# 1 Scope + +This Recommendation describes the framework for an olfactory function test system. + +In particular, the scope of this Recommendation includes: + +- Architectural framework; +- System framework entities; +- Olfactory function test procedures. + +## 2 References + +None. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 biosignal** [b-ITU-T X.1094]: Any measurable signal in living beings (physical, chemical or electrical) that can be measured or monitored, such as a ballistocardiogram (BCG), electroencephalogram (EEG), electrocardiogram (ECG) and photoplethysmogram (PPG). + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 olfactory fatigue:** The temporary inability to distinguish a particular odour after prolonged exposure to that scent. + +**3.2.2 olfactory function:** The ability to detect odorous substances in the air through the nose. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +EEG Electroencephalogram + +ICT Information and Communication Technology + +## 5 Conventions + +None. + +## 6 Background + +Olfactory function is not only a simple sense of smell in daily life but is also an essential function of safety that enables humans to be evacuated in advance from any dangerous situation. Many tests for olfactory disorders have been widely conducted. The existing olfactory test is in the form of a scent and questionnaire using a scratch paper, pen, and a bottle. Recently, the information and communication technology (ICT)-based olfactory test method has been spreading widely. + +The olfactory test is largely divided into four types, which consists of a method of measuring identification, discrimination, recognition, and the threshold of smell. In addition to this, the olfactory function test has been proven to be related to the cognitive function and has recently been gaining currency as an early screening tool for dementia such as the Alzheimer's disease. However, a problem has risen in the effectiveness of the inspection being limited due to the inaccuracies of the questionnaire method. + +The olfactory test examines every step from detecting the smell of the nose to the memory process in the brain. It is classified according to the function of each stage and consists of four measurement types: odour identification, olfactory discrimination, odour recognition, and olfactory threshold. The olfactory test is currently widely used in otolaryngology hospitals as a tool to measure olfactory-related diseases, and dementia screening tests are also being attempted in neurology hospitals. + +## **7 System framework architecture** + +The questionnaire olfactory test is a method in which the fragrance is brought directly into the nose and smelled, so the amount of incense flowing into the nose is not uniform. Since the fragrances must be presented manually, the interval between them is not constant, and if a specific odour is smelled repeatedly, the probability of olfactory fatigue that changes olfactory ability increases. In addition, the difficulty of cleaning the residual scent mixes, after the fragrance presentation in the questionnaire method is also a problem. This being an important factor as it lowers the effect of the examination due to the characteristic of the smell of sense which perceives the fragrance differently even with slight changes in the smell. + +The olfactory performance test can be carried out by considering human factors related to the human olfactory. It can be sprayed by mechanically controlling a certain amount of fragrance, and the fragrance can be sprayed at intervals that is optimized for olfactory fatigue. It is also possible to prevent the fragrance from being perceived completely differently due to the residual fragrance by solving the problem of fragrance mixing between olfactory tests through cleaning. + +The olfactory performance testing framework consists of three stages. + +The user data processing measures the user's condition in determining whether an olfactory inspection is suitable while also helping to focus on the inspection. + +The olfactory test management manages to spray the scent according to the test procedure database and receive the user's scent evaluation input. + +The scent diffusing system controls the scent of a certain concentration and mass and performs cleaning for residual scent through the outside air. At the same time, the olfactory function test analysis receives the response of four types of olfactory tests and then analyses user input to perform olfactory tests. + +![Figure 1 – ICT-based olfactory function test system framework. The diagram shows four main modules: User data processing, Olfactory test management, Olfactory function test analysis, and Scent diffusing control, with a Test procedure database. User data processing includes input, EEG, biosignal, and location acquisition, leading to cognitive evaluation, compliance, inhalation time, and nose location recognition. Olfactory test management includes data management, result generation, execution, and scent diffusing management. Olfactory function test analysis includes response analysis, report, status analysis, and disorder screening. Scent diffusing control includes selection, cleaning, concentration, and outlet control. The Test procedure database includes odour identification, threshold, recognition, and discrimination. Arrows show data flow between modules and the database.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +graph TD + subgraph User_data_processing [User data processing] + U1[User input acquisition] --> U2[User cognitive evaluation] + U3[EEG data acquisition] --> U4[Compliance recognition] + U5[Biosignal data acquisition] --> U6[Inhale time recognition] + U7[Location data acquisition] --> U8[Nose location recognition] + end + + subgraph Olfactory_test_management [Olfactory test management] + O1[User data management] --> O2[Test result generation] + O3[Olfactory test execution] --> O4[Scent diffusing management] + end + + subgraph Olfactory_function_test_analysis [Olfactory function test analysis] + A1[User response analysis] --> A2[Olfactory test report] + A3[User status analysis] --> A4[Smell disorder screening] + end + + subgraph Scent_diffusing_control [Scent diffusing control] + C1[Scent selection control] --> C2[Cleaning control] + C3[Concentration control] --> C4[Outlet control] + end + + subgraph Test_procedure_database [Test procedure database] + D1[Test odour identification] --> D2[Test olfactory threshold] + D3[Test olfactory recognition] --> D4[Test odour discrimination] + end + + User_data_processing --> Olfactory_test_management + Olfactory_test_management --> Olfactory_function_test_analysis + Olfactory_function_test_analysis --> Scent_diffusing_control + Scent_diffusing_control --> User_data_processing + Test_procedure_database --> Olfactory_test_management + Olfactory_test_management --> Test_procedure_database + Olfactory_function_test_analysis --> Test_procedure_database + Test_procedure_database --> Olfactory_function_test_analysis + +``` + +Figure 1 – ICT-based olfactory function test system framework. The diagram shows four main modules: User data processing, Olfactory test management, Olfactory function test analysis, and Scent diffusing control, with a Test procedure database. User data processing includes input, EEG, biosignal, and location acquisition, leading to cognitive evaluation, compliance, inhalation time, and nose location recognition. Olfactory test management includes data management, result generation, execution, and scent diffusing management. Olfactory function test analysis includes response analysis, report, status analysis, and disorder screening. Scent diffusing control includes selection, cleaning, concentration, and outlet control. The Test procedure database includes odour identification, threshold, recognition, and discrimination. Arrows show data flow between modules and the database. + +Figure 1 – ICT-based olfactory function test system framework + +## 8 System framework entities + +### 8.1 User data processing module + +This module receives the user's input electroencephalogram (EEG) signal, biosignal and location for the olfactory test and processes it by pattern recognition to automatically recognize the user's status and whether to comply with the test, the time to smell the fragrance and the location of the nose. + +#### 8.1.1 User input acquisition submodule + +This submodule receives input through the user's screen and voice, then stores it. + +#### 8.1.2 EEG data acquisition submodule + +The EEG signal attached to the user's head stores the EEG signal within 100 ms after the fragrance is injected. + +#### 8.1.3 Biosignal data acquisition submodule + +This submodule stores signals collected by remote or attached biosignal equipment. + +#### 8.1.4 Location data acquisition submodule + +This submodule measures and stores information about the distance between the user and the fragrance. + +#### 8.1.5 User cognitive evaluation submodule + +The validity of user input is evaluated through user input value and EEG signal. + +- Input: user input data, user EEG data +- Output: user cognition evaluation result + +#### 8.1.6 Compliance recognition submodule + +This submodule interprets the user's EEG signal and biosignal data to recognize the user's compliance with the test. + +- Input: user EEG data, user biosignal data +- Output: user compliance recognition result + +#### **8.1.7 Inhale time recognition submodule** + +This submodule analyses user's biosignal data to recognize the user's inhale time in a breath. + +- Input: user biosignal data +- Output: user inhale time result + +#### **8.1.8 Nose location recognition submodule** + +This submodule recognizes the user's nose location through location data. + +- Input: user location data +- Output: user inhale time result + +### **8.2 Olfactory test management module** + +After receiving the information of the user receiving the olfactory test, fusion is performed, and the olfactory test is performed using the olfactory test procedure, the scent is executed accordingly, and the result is generated according to the olfactory test. + +#### **8.2.1 User data management submodule** + +This submodule receives and fuses user data and provides it for olfactory inspection. + +- Input: user data +- Output: user information + +#### **8.2.2 Olfactory test execution submodule** + +This submodule performs the olfactory inspection procedure based on the user's information and the fragrance information is generated accordingly. + +- Input: user information, test procedure database +- Output: scent diffusing data + +#### **8.2.3 Scent diffusing management submodule** + +This submodule generates data that can control the scent diffusing device to generate scent diffusing information. + +- Input: scent diffusing information +- Output: scent diffusing procedure + +#### **8.2.4 Test result generation submodule** + +This submodule generates information to the user by using the olfactory function test result. + +- Input: test analysis data +- Output: test analysis display + +### **8.3 Test procedure database module** + +This module provides an olfactory test procedure suitable for olfactory test steps. + +- Input: pre-defined database +- Output: olfactory test procedure + +#### **8.3.1 Test odour identification submodule** + +This submodule sprays one type of familiar fragrance to check whether it is identified from the names of fragrances presented on the screen view. + +#### **8.3.2 Olfactory threshold submodule** + +This submodule uses a special fragrance and measures the minimum concentration that can smell incense with one step i.e., from low to high. + +#### **8.3.3 Test olfactory recognition submodule** + +This submodule sprays some of the fragrances, the rest of the fragrances are then sprayed to check if the overlapped scents can be recognized. + +#### **8.3.4 Test odour discrimination submodule** + +This submodule randomly sprays two types of scents respectively to check and prevent odour discrimination. + +### **8.4 Scent diffusing control module** + +This module controls scent diffusing, which is composed of submodules to select the fragrance, adjust the concentration of the fragrance, scent outlet and to clean the inside. + +- Input: scent diffusing procedure +- Output: scent diffusing result + +#### **8.4.1 Scent selection control submodule** + +This submodule opens and closes the associated valve to create the selected fragrance. + +#### **8.4.2 Concentration control submodule** + +This submodule adjusts the combination of fragrance and air to adjust the concentration of fragrance. + +#### **8.4.3 Outlet control submodule** + +This submodule adjusts the opening and closing of the outlet to discharge the fragrance at a predetermined intensity. + +#### **8.4.4 Cleaning control submodule** + +This submodule cleans the inside of the contaminated sprayed scent. + +### **8.5 Olfactory function test analysis module** + +This module analyses the user's sense of smell according to the result of the olfactory function and screens the problem of the smell accordingly. + +- Input: user data information, test procedure data, scent diffusing result +- Output: test analysis data + +#### **8.5.1 User response analysis submodule** + +This submodule reviews the user's data and analyse the reliability of the response. + +#### **8.5.2 User status analysis submodule** + +This submodule compares and analyses the comparative group and olfactory test result according to the user's status. + +#### **8.5.3 Olfactory test report submodule** + +This submodule analyses test results according to the user's response in various test procedures. + +#### **8.5.4 Smell disorder screening submodule** + +This submodule analyses the tendency of various olfactory disorders and screens the smell disorders. + +## 9 Olfactory function test procedures + +These test procedures consist of the most commonly used four types of olfactory function tests in the hospitals, and each of which examines a person's ability to smell at each stage of the olfactory process. + +### 9.1 Test odour identification + +The purpose of the test odour identification is to test whether the brain can process information about the smell by seeing whether the user can identify or remember the name of the scent. To do this, a candidate is presented, multiple scent names are presented in the multiple-choice, and the user's answer is collected to evaluate whether it is correct. + +![Flowchart of the test odour identification procedure](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +``` +graph TD; A[Candidate scent selection] --> B[Candidate scent diffusion]; B --> C[Candidate scent name matching test]; +``` + +The diagram shows a vertical flow of three steps: 'Candidate scent selection' at the top, 'Candidate scent diffusion' in the middle, and 'Candidate scent name matching test' at the bottom, connected by downward arrows. + +Flowchart of the test odour identification procedure + +H.862.4(21)\_F02 + +Figure 2 – Test odour identification procedure + +#### 9.1.1 Candidate scent selection + +This procedure sets the candidate scent to diffuse from first to last. + +#### 9.1.2 Candidate scent diffusion + +This procedure sprays the user with the selected scent. + +#### 9.1.3 Candidate scent name matching test + +This procedure tests to see if the user can name the candidate scent in the multiple-choice. + +### 9.2 Test olfactory threshold + +The purpose of the test olfactory threshold is to test the sensitivity of a person's sense of smell by measuring the concentration with the lowest odour. For this, the lowest concentration that can be perceived by the sense of smell is obtained by measuring whether the scent can be smelled by increasing its concentration sequentially. + +![Flowchart of the test olfactory threshold procedure](cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg) + +``` +graph TD; A[Candidate concentration selection] --> B[Candidate concentration and air diffusion]; B --> C[Candidate concentration perception test]; +``` + +The diagram shows a vertical flow of three steps: 'Candidate concentration selection' at the top, 'Candidate concentration and air diffusion' in the middle, and 'Candidate concentration perception test' at the bottom, connected by downward arrows. + +Flowchart of the test olfactory threshold procedure + +H.862.4(21)\_F03 + +Figure 3 – Test olfactory threshold procedure + +#### 9.2.1 Candidate concentration selection + +This procedure sets the candidate concentration to diffuse from minimum to maximum. + +#### 9.2.2 Candidate concentration and air diffusion + +This procedure randomly sprays the user with the selected concentration of scent once, air twice or more. + +#### 9.2.3 Candidate concentration perception test + +This procedure tests to see if the user can perceive the candidate concentration of scent from the air in the multiple-choice. + +### 9.3 Test olfactory recognition + +The purpose of the olfactory test recognition is to test if the user can remember the scent which is previously smelled in memory and remembered when smelled again. To do this, after suggesting and memorizing a scent, multiple scents are presented to evaluate if they can find a previously memorized scent. + +![Flowchart of the Test olfactory recognition procedure](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` +graph TD; A[Target scent pre-diffusion] --> B[Candidate scent selection]; B --> C[Candidate scent diffusion]; C --> D[Target scent memory recall test]; +``` + +The diagram illustrates the 'Test olfactory recognition procedure' as a vertical flowchart. It consists of four rectangular boxes, each containing a step name, connected by downward-pointing arrows. The steps are: 'Target scent pre-diffusion', 'Candidate scent selection', 'Candidate scent diffusion', and 'Target scent memory recall test'. The entire flowchart is enclosed in a light blue rectangular border. + +Flowchart of the Test olfactory recognition procedure + +H.862.4(21)\_F04 + +Figure 4 – Test olfactory recognition procedure + +#### 9.3.1 Target scent pre-diffusion + +This procedure sprays the target scent to remember it in advance. + +#### 9.3.2 Candidate scent selection + +This procedure randomly sets the candidate scent to diffuse between the target scent and the distracting scent. + +#### 9.3.3 Candidate scent diffusion + +This procedure sprays the user with the selected scent. + +#### 9.3.4 Target scent memory recall test + +This procedure tests to see if the user can recall the target scent memory from the candidate scent. + +### 9.4 Test odour discrimination + +The purpose of the test odour discrimination is to evaluate whether the user's sense of smell can recognize and distinguish differences in odours. To this end, the user is sequentially sprayed with the same scent and one different scent and evaluated whether it is possible to distinguish the other scent. + +![Flowchart of the test odour discrimination procedure](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` +graph TD; A[Candidate and distracting scent selection] --> B[Candidate and distracting scent diffusion]; B --> C[Candidate scent finding test]; +``` + +The diagram illustrates a three-step process for odour discrimination testing. It consists of three rectangular boxes arranged vertically, connected by downward-pointing arrows. The first box is labeled 'Candidate and distracting scent selection', the second is 'Candidate and distracting scent diffusion', and the third is 'Candidate scent finding test'. The entire flowchart is enclosed in a light blue rectangular border. Below the border, the text 'H.862.4(21)\_F05' is displayed. + +Flowchart of the test odour discrimination procedure + +**Figure 5 – Test odour discrimination procedure** + +#### **9.4.1 Candidate & distracting scent selection** + +This procedure sets the candidate & distracting scent to diffuse from first to last. + +#### **9.4.2 Candidate & distracting scent diffusion** + +This procedure randomly sprays the user with the selected scent once, the distracting scent twice or more. + +#### **9.4.3 Candidate scent finding test** + +This procedure tests to see if the user can find the candidate scent from the distracting scent in the multiple-choice. + +## Bibliography + +- [b-ITU-T X.1094] Recommendation ITU-T X.1094 (2019), *Telebiometric authentication using biosignals*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/1c94fd3cebf58af136144f14160d128e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..743207cc49188f8e62b55344707d8dc482eddcc6 --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/1c94fd3cebf58af136144f14160d128e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92741f608286c747bda0949392f5a0867c762e5188e7daab971d88f7ade3df2a +size 57883 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02c867db247b73a15587957467b2922ca0b6db76 --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e06becb0e1455c118f5723a2d03305113ce40e113ee9ae5d7f4e43b70f1a9f4 +size 6126 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11abcb65249789d6e586813f088558c67f0f0945 --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0740273c230bf5cfdf99300ba5a6e30895576fee802d94d08f543f08d2bd5a5d +size 30242 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59a2bbe25c4a56e830794e9674cc8e7a1b701b3d --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b6588a193fae07b63ecaff9964b7412152652c64ae6b53fe63d52b72f27dc89 +size 23153 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0026f337f219b7577e5e43bed1fb039e5cc51eb1 --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d28a210533c71eae2ce9b5540b2c39ab5e092b0abbc1ff920cf1137d53f1292 +size 31520 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce7410d91bcae20b914412cc17ef563b926ff261 --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dec470e057a06382be39feb08b61b0fdb0f463f9ade0e48c8a8cea7e3694052 +size 54653 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e70f25afc0dc6f8fcf5daaec0db7284f0a9a186d --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77785d82d44f07b4f84d3e3a5f10d9ef488f98d4bb2cadecaa224afde4d1d634 +size 24507 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11553bdcabfb0032e19add5a193660014427fe9a --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f10f47f61d203e732b903a2b66051250f5767e463134375fc740c480d367f93 +size 33253 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1ef4e94a67305bd56ea33451acfc76107c089d2 --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03089ade9c04fd1dce11cc4f583a6d1ccb78d43520b8846a8dff95f501a8783a +size 32752 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg b/marked/H/T-REC-H.862.5-202106-I_PDF-E/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fbaf4f4f0b5f679dd56978761d7b4b5229fdee6 --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7878f78823c4d602c8f763fabc1bf8f767e7118599e1ca343e6c18af3c534a2 +size 25286 diff --git a/marked/H/T-REC-H.862.5-202106-I_PDF-E/raw.md b/marked/H/T-REC-H.862.5-202106-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6615618f6b768b5ff8f8ed26112054e8db1044f8 --- /dev/null +++ b/marked/H/T-REC-H.862.5-202106-I_PDF-E/raw.md @@ -0,0 +1,752 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.862.5** + +(06/2021) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Multimedia e-health data exchange services + +--- + +**Emotion enabled multimodal user interface +based on artificial neural networks** + +Recommendation ITU-T H.862.5 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a white grid pattern, overlaid by a stylized 'ITU' text in blue. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Content delivery and ubiquitous sensor network applications | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.862.5 + +# Emotion enabled multimodal user interface based on artificial neural networks + +## Summary + +Recommendation ITU-T H.862.5 provides functional entities and architecture for emotion enabled multimodal user interface based on artificial neural network. + +As emotion technology continues to make big improvements in human-computer interaction (HCI) areas, many companies and researchers have been studying emotion technology. Various applications using multimodality and emotion analysis are also introduced these days with artificial intelligence technology. However, many of the current systems do not yet infer human emotion properly because some systems are either too dependent on certain sources, or too weak for real circumstances. + +Therefore, the proposed system architecture is for multimodal user interface (UI) based on emotion analysis with some properties and illustrations, and data with an artificial neural network. The multimedia data for the input is composed of text, speech, and image. For the unimodal emotion analysis, the data is pre-processed in the corresponding module. For example, the text data is pre-processed by data augmentation, person attributes recognition, topic cluster recognition, document summarization, named entity recognition, sentence splitter, keyword cluster, and sentence to graph functions. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.862.5 | 2021-06-13 | 16 | 11.1002/1000/14690 | + +## Keywords + +Emotion expansion, multimedia knowledge database, multimodal emotion analysis, unimodal emotion analysis. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2021 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Functional architecture ..... | 2 | +| 6.1 Architectural framework ..... | 2 | +| 7 Functional entities..... | 3 | +| 7.1 Multimedia processing – pre-processing module..... | 3 | +| 7.2 Emotion analysis neural network – unimodal network ..... | 6 | +| 7.3 Emotion analysis neural network – multimodal network..... | 8 | +| 7.4 Emotion expansion module – complex emotion generation ..... | 9 | +| 7.5 Multimedia knowledge database ..... | 10 | +| 8 Application to multimodal emotion analysis ..... | 11 | +| Appendix I – Survey on SDO's activity regarding typical emotional service ..... | 13 | +| I.1 SDO activities on emotion..... | 13 | +| Bibliography..... | 15 | + + + +# Recommendation ITU-T H.862.5 + +## Emotion enabled multimodal user interface based on artificial neural networks + +## 1 Scope + +This Recommendation describes the functional entities and architecture for emotion enabled multimodal user interface based on artificial neural networks. + +In particular, the scope of this Recommendation includes: + +- Architectural framework; +- Functional entities; +- Interfaces; +- Application to multimodal emotion analysis. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +None. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 named entity recognition** [b-ITU-T F.746.3]: A function that recognizes named entities such as PLO which are people, locations and organizations from the sentences. The PLO can be decomposed into more specific named entities depending on the applications. + +**3.1.2 natural language processing** [b-ITU-T F.746.3]: A method that analyses text in natural languages through several processes such as part-of-speech recognition, syntactic analysis and semantic analysis. + +**3.1.3 semantic analysis** [b-ITU-T F.746.3]: A function that recognizes the semantic relations among the words around predicates that exist in the same sentence. The semantic analysis function then generates a semantic predicate-argument structure (PAS). + +**3.1.4 speech** [b-ITU-T H.703]: Speech is the vocalized form of human communication. + +**3.1.5 syntactic analysis** [b-ITU-T F.746.3]: A function that analyses sentence structures and generates dependency relations among words based on dependency grammars. + +**3.1.6 knowledge base** [b-ITU-T F.746.7]: A collection of knowledge resources that consist of structured and unstructured data. The knowledge base is used to provide information to the various applications that are related to information provisioning such as question answering (QA) systems and search systems. + +**3.1.7 question answering** [b-ITU-T F.746.7]: A system that provides answers in a natural language to questions which are in the natural language form by analysing the questions and all the knowledge resources that are available to the system. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------| +| CNN | Convolutional Neural Networks | +| LSTM | Long Short-Term Memory | +| NE | Named Entity | +| NN | Neural Network | +| POS | Part of Speech | +| QA | Question Answering | +| STT | Speech-to-Text | +| UI | User Interface | + +## 5 Conventions + +None. + +## 6 Functional architecture + +### 6.1 Architectural framework + +Figure 1 shows the proposed system architecture for multimodal user interface (UI) based on emotion analysis with some properties and illustrations. The multimedia data is composed of text, speech, and image. For the unimodal emotion analysis, the data is pre-processed in each analysis module. In other words, after the pre-processing stage, three unimodal networks analyse each data. The multimodal network then integrates the state vectors that denote recognized emotion from each unimodal process. The emotion obtained by the multimodal network expands to complex emotion through a complex emotion generation module. + +![Figure 1 – Emotion enabled multimodal UI architecture diagram](1c94fd3cebf58af136144f14160d128e_img.jpg) + +The diagram illustrates the 'Emotion enabled multimodal UI architecture'. It is divided into three main functional blocks: 'Multimedia processing', 'Emotion Analysis neural network', and 'Emotion expansion'. Inputs 'Speech to text' and 'Video' enter the 'Multimedia processing' block. 'Speech to text' feeds into 'Text processing', while 'Video' feeds into 'Image processing'. Both, along with direct input, also feed into 'Speech processing'. The outputs of these three processing paths enter the 'Emotion Analysis neural network' block, specifically the 'Unimodal network' which contains 'Text analysis', 'Speech analysis', and 'Image analysis'. These unimodal analyses feed into a 'Multimodal network'. The 'Multimodal network' output goes to the 'Emotion expansion' block, specifically the 'Complex emotion generation' module. A 'Multimedia knowledge database' is shown below the 'Emotion Analysis neural network' block, with arrows indicating data flow to and from the 'Multimodal network' and the 'Complex emotion generation' module. A feedback loop is shown from the 'Complex emotion generation' module back to the 'Speech to text' input. + +Figure 1 – Emotion enabled multimodal UI architecture diagram + +**Figure 1 – Emotion enabled multimodal UI architecture** + +The proposed UI architecture presents the emotion analysis processes for how to pre-process emotional sources and integrate unimodal networks. The system composing proper methods is a key factor for multimodal emotion analysis. + +## 7 Functional entities + +### 7.1 Multimedia processing – pre-processing module + +In the pre-processing module low-level handcrafted features are produced from text input, audio input and image input, respectively. That is, the data pre-processing module performs the embedding function of transforming the text data, audio data and image data into vector types that can be used for machine learning. The text input is produced from the audio input by STT (speech-to-text) or speech recognition module. + +### 7.1.1 Text processing + +As shown in Figure 2, the text data is pre-processed by a natural language processing method that includes text data augmentation, person attributes recognition for text, topic cluster recognition, document summarization, named entity (NE) recognition, sentence splitter, and keyword cluster sub-functions. + +![Diagram of the Text processing module showing seven sub-functions arranged in a grid.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +The diagram illustrates the 'Text processing' module as a grid of sub-functions. The title 'Text processing' is centered at the top. Below it, the functions are arranged in three rows: the first row contains 'Text data augmentation' and 'Person attributes recognition for text'; the second row contains 'Topic cluster recognition' and 'Document summarization'; and the third row contains 'Named entity recognition', 'Sentence splitter', and 'Keyword cluster'. A label 'H.862.5(21)\_F02' is located at the bottom right of the diagram. + +| Text processing | | | +|---------------------------|----------------------------------------|-----------------| +| Text data augmentation | Person attributes recognition for text | | +| Topic cluster recognition | Document summarization | | +| Named entity recognition | Sentence splitter | Keyword cluster | + +H.862.5(21)\_F02 + +Diagram of the Text processing module showing seven sub-functions arranged in a grid. + +Figure 2 – Text processing module + +##### 7.1.1.1 Text data augmentation + +The role of the text data augmentation function is to increase the training text data to improve the performance of the emotion recognition network. It takes the original text data as input and produces/returns the new training data using various augmentation methods such as the thesaurus, word embedding, and back translation. The natural language sentences are expanded for the trainer through an expansion tool that takes the input sentences and analyses them for part of speech (POS) tagging. The primary parts of speech in the sentences are expanded to the secondary POS through a search for similar words in the database or in the synonym dictionary. The input sentences are then expanded by replacing them with those of the extracted secondary POS. Finally, the newly generated input sentences used for training will then be verified for grammatical correctness. + +- Input: text data +- Output: text data + +##### 7.1.1.2 Person attribute recognition for text + +The person attribute recognition for text function finds speakers in the text, analyses the characteristics of the speakers and recognizes attributes such as gender and age. + +- Input: text data +- Output: attributes of the speaker + +##### 7.1.1.3 Topic cluster recognition + +Topic recognition function recognizes topics of the text and calculates the importance of each topic by analysing the statistics of the words mathematically. + +- Input: text data +- Output: topic cluster of the text data and their importance measures + +#### 7.1.1.4 Document summarization + +Document summarization function divides the original text into multiple blocks of phrases and extracts the summarized sentence which represents each block of phrases. + +- Input: text data +- Output: summarized sentences + +##### 7.1.1.5 Named entity recognition + +The named entity recognition function extracts nouns in the text data which is provided by a part-of-speech analyser. It then recognizes the named entities for the extracted nouns. + +- Input: text data +- Output: nouns in the text and corresponding named entities + +#### 7.1.1.6 Sentence splitter + +Sentence splitter separates each sentence from the input text data that may consist of multiple sentences. + +- Input: text data +- Output: sentences in the text data + +##### 7.1.1.7 Keyword cluster + +Keyword cluster function makes groups for the keywords which are extracted from the text data based on relation description features among the keywords such as a similarity feature. + +- Input: text data +- Output: keyword cluster + +#### 7.1.2 Speech processing + +As shown in Figure 3, speech data is pre-processed by speech data augmentation, person attributes recognition for speech, noise reduction, voice separation, and voice activity detection sub-functions. + +![Diagram of the Speech processing module showing five sub-functions: Speech data augmentation, Person attributes recognition for speech, Noise reduction, Voice separation, and Voice activity detection.](c6005b2627c6ca10f6b0e94cdb34858d_img.jpg) + +The diagram illustrates the 'Speech processing' module as a rectangular box containing five sub-functions arranged in a grid. The top row contains 'Speech data augmentation', 'Person attributes recognition for speech', and 'Noise reduction'. The bottom row contains 'Voice separation' and 'Voice activity detection', which spans the width of the second and third columns. + +| | | | +|--------------------------|------------------------------------------|-----------------| +| Speech processing | | | +| Speech data augmentation | Person attributes recognition for speech | Noise reduction | +| Voice separation | Voice activity detection | | + +H.862.5(21)\_F03 + +Diagram of the Speech processing module showing five sub-functions: Speech data augmentation, Person attributes recognition for speech, Noise reduction, Voice separation, and Voice activity detection. + +Figure 3 – Speech processing module + +##### 7.1.2.1 Speech data augmentation + +Speech data augmentation function performs the role of increasing the training data for the performance enhancement of the emotion recognition network. It takes the original speech data and produces new training data using various augmentation methods such as time warping and frequency masking. + +- Input: speech data +- Output: speech data + +#### **7.1.2.2 Person attributes recognition for speech** + +Person attributes recognition for speech function finds the speaker in the speech data, analyses his features and recognizes features such as gender and age. + +- Input: speech data +- Output: attributes of the speaker + +##### **7.1.2.3 Noise reduction** + +Noise reduction function removes from the speech data various noises such as background sound, white noise, and third person utterances. + +- Input: speech data +- Output: speech data + +##### **7.1.2.4 Voice separation** + +Voice separation function separates the background sound and voice from the speech data. + +- Input: speech data +- Output: voice and background sound + +##### **7.1.2.5 Voice activity detection** + +Voice activity detection function removes the non-linguistic meaningless section in the speech data. + +- Input: speech data +- Output: voice without non-linguistic meaningless section + +#### **7.1.3 Image processing** + +Figure 4 shows that the image data is pre-processed by image data augmentation, person attributes recognition for image, noise reduction, object detection, face detection, and gesture recognition sub-functions. + +![A diagram titled 'Image processing' showing a 2x3 grid of sub-functions: Image data augmentation, Person attributes recognition for image, Noise reduction, Object detection, Face detection, and Gesture recognition. Below the grid is the text H.862.5(21)_F04.](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg) + +| Image processing | | | +|-------------------------|-----------------------------------------|---------------------| +| Image data augmentation | Person attributes recognition for image | Noise reduction | +| Object detection | Face detection | Gesture recognition | + +H.862.5(21)\_F04 + +A diagram titled 'Image processing' showing a 2x3 grid of sub-functions: Image data augmentation, Person attributes recognition for image, Noise reduction, Object detection, Face detection, and Gesture recognition. Below the grid is the text H.862.5(21)\_F04. + +**Figure 4 – Image processing module** + +#### **7.1.3.1 Image data augmentation** + +Image data augmentation function performs the role of increasing the training data for the performance enhancement of the emotion recognition network. It takes the original image data and produces new training data using various augmentation methods such as cropping, translation, and flipping. + +- Input: image data +- Output: image data + +#### **7.1.3.2 Person attributes recognition for image** + +Person attributes recognition for image function finds the person in the image data, analyses individual features, and recognizes features like gender, age, and clothes of the person. + +- Input: image data +- Output: location information and other attributes of a person + +#### **7.1.3.3 Noise reduction** + +Noise reduction function does the role of removing noise from the image data. This function also generates training data after the sensor noises and illuminance disparities are removed. + +- Input: image data +- Output: image data + +#### **7.1.3.4 Object detection** + +Object detection function classifies the backgrounds in the image data that can be used for emotion recognition tasks. It produces the coordinate values of the relevant pixels and classification results. + +- Input: image data +- Output: location information of the background image and classification results + +#### **7.1.3.5 Face detection** + +Face detection function finds a persons' face in the image data and produces the pixel coordinate values. + +- Input: image data +- Output: location information of the found faces + +#### **7.1.3.6 Gesture recognition** + +Gesture recognition function recognizes the ongoing gestures from a single image or consecutive images taken at a certain time interval. It returns the recognition results as the output. + +- Input: single or consecutively taken image data +- Output: gesture classification results + +### **7.2 Emotion analysis neural network – unimodal network** + +After the pre-processing stage, three unimodal networks analyse each data as shown in Figure 5. And then, the multimodal network integrates state vectors from each unimodal process. + +The text emotion inference engine recognizes the inner emotion embedded in the text input from the low-level features using the neural network (NN) which consists of an input layer, at least two hidden layers and a softmax layer. The output of the softmax layer is the emotion vector. The emotion vector is composed of probabilities of seven types of basic emotions such as happiness, sadness, fear, disgust, anger, surprise, and neutral [b-Ekman]. One of the hidden layers produces, as the output, high-level features from the low-level features by dimensionality reduction. The text emotion inference engine produces one hidden layer output of the neural network as a state vector which will be used as the input to the multimodal network. + +Like the text emotion inference engine, the speech emotion inference engine and the image emotion inference engine infer the innate emotion from the low-level features in the audio and image input, using the neural network and produces the state vector to be input to the multimodal network. The text emotion inference engine and the speech emotion inference engine can use the long short-term memory (LSTM) network. The image emotion inference engine can use the convolutional neural network (CNN). Each unimodal module has a trainer module and trains the related neural network of the emotion inference engine at the training stage. + +![Diagram of the Unimodal network module showing three parallel analysis paths: Text, Speech, and Image. Each path consists of a Trainer, an emotion inference engine, and outputs a State vector and Emotion.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +``` + +graph TD + subgraph Unimodal_network [Unimodal network] + subgraph Text_analysis [Text analysis] + T1[Trainer (Text)] --> T2[Text emotion inference engine] + T2 --> T3[State vector] + T2 --> T4[Emotion] + end + subgraph Speech_analysis [Speech analysis] + S1[Trainer (Speech)] --> S2[Speech emotion inference engine] + S2 --> S3[State vector] + S2 --> S4[Emotion] + end + subgraph Image_analysis [Image analysis] + I1[Trainer (Image)] --> I2[Image emotion inference engine] + I2 --> I3[State vector] + I2 --> I4[Emotion] + end + end + +``` + +H.862.5(21)\_F05 + +Diagram of the Unimodal network module showing three parallel analysis paths: Text, Speech, and Image. Each path consists of a Trainer, an emotion inference engine, and outputs a State vector and Emotion. + +**Figure 5 – Unimodal network module** + +#### 7.2.1 Text analysis + +#### 7.2.1.1 Trainer for the text analysis + +The trainer for the text analysis trains the neural networks using the text data information produced in the pre-processing stage in clause 7.1.1. + +- Input: pre-processed text data +- Output: text emotion inference engine + +#### 7.2.1.2 Text emotion inference engine + +Text emotion inference engine analyses the input text data information and produces emotion and state vector result value using the neural network from the trainer. + +- Input: pre-processed text data +- Output: state vector, emotion + +#### 7.2.2 Speech analysis + +#### 7.2.2.1 Trainer for speech analysis + +The trainer for the speech analysis trains the neural network using the speech data information produced in the pre-processing stage described in clause 7.1.2. + +- Input: pre-processed speech data +- Output: speech emotion inference engine + +#### **7.2.2.2 Speech emotion inference engine** + +Speech emotion inference engine analyses the input speech data information and produces emotion and state vector result value using the neural network from the trainer. + +- Input: pre-processed speech data +- Output: state vector, emotion + +#### **7.2.3 Image analysis** + +#### **7.2.3.1 Trainer for image analysis** + +The trainer for image analysis trains the neural network with the image data information generated in the image processing stage described in clause 7.1.3. + +- Input: pre-processed image data +- Output: text emotion inference engine + +#### **7.2.3.2 Image emotion inference engine** + +Image emotion inference engine uses the neural network trained in the trainer for image analysis. This engine analyses image data information as input and generates emotion, state vector result values. + +- Input: pre-processed image data +- Output: state vector, emotion + +### **7.3 Emotion analysis neural network – multimodal network** + +Multimodal network consists of a state vector integration module, a multimodal trainer module, and a multimodal emotion inference engine as presented in Figure 6. + +The state vector integration module combines the state vector generated in the text analysis module, the state vector generated in the speech analysis module and the state vector generated in the image analysis module and produces an integrated state vector as the output. That is, the state vector integration module formulates the common feature representation by integrating all the high-level features extracted from the unimodal networks. + +The training module performs the training process of the neural network for the multimodal emotion inference engine at the training stage. + +The multimodal emotion inference engine analyses the relation among the features from the different modalities and recognizes the emotion using the neural network which consists of an input layer, at least two hidden layers and a softmax layer. The output of the softmax layer is the corresponding emotion vector. The emotion vector, for example, can be classified as "happiness." + +![Figure 6: Multimodal network module diagram. The diagram shows a 'Multimodal network' box containing three components: 'State vector integration (Dimension reduction)', 'Trainer (Multimodal)', and 'Multimodal emotion inference engine'. Arrows indicate a sequential flow: from 'State vector integration' to 'Trainer', then to 'Multimodal emotion inference engine', and finally to the output 'Emotion'. A label 'H.862.5(21)_F06' is at the bottom right.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +graph TD + subgraph Multimodal_network [Multimodal network] + A[State vector integration +(Dimension reduction)] --> B[Trainer +(Multimodal)] + B --> C[Multimodal emotion inference engine] + C --> D[Emotion] + end + +``` + +Figure 6: Multimodal network module diagram. The diagram shows a 'Multimodal network' box containing three components: 'State vector integration (Dimension reduction)', 'Trainer (Multimodal)', and 'Multimodal emotion inference engine'. Arrows indicate a sequential flow: from 'State vector integration' to 'Trainer', then to 'Multimodal emotion inference engine', and finally to the output 'Emotion'. A label 'H.862.5(21)\_F06' is at the bottom right. + +**Figure 6 – Multimodal network module** + +#### 7.3.1 State vector integration + +The state vector integration function combines the state vectors generated from the unimodal network modules and produces the integrated state vector. + +- Input: state vectors +- Output: integrated state vector + +#### 7.3.2 Trainer for multimodal network + +The trainer trains the neural network with the integrated state vector. + +- Input: integrated state vector +- Output: multimodal emotion inference engine + +#### 7.3.3 Multimodal emotion inference engine + +Multimodal emotion inference engine analyses the integrated state vector from the input data and makes inferences on the multimodal emotion. + +- Input: integrated state vector +- Output: multimodal emotion + +### 7.4 Emotion expansion module – complex emotion generation + +The emotion obtained by multimodal network expands to complex emotion through a complex emotion generation module. The complex emotion generation module, which is presented in Figure 7, decides on the final emotion based on the probabilities on the basic emotion types produced from the multimodal network. + +The complex emotion generation module can decide on one specific emotion as the final emotion type in case the probability of one basic emotion is eminently higher than other emotion types (for example when the probability is higher than 80%). + +When the probability of two types of basic emotion is eminently higher than other emotion types (for example when the probability of top rank basic emotion and second rank one is higher than 40%, respectively), the complex emotion generation module can decide on the complex emotion corresponding to the combination of two basic emotion based on the artificial emotion model, as the final one. + +Alternatively, the emotion inference result values can be different on each unimodal case, which is when, for instance, the basic emotion type inferred from the speech is different from that of the image. In that case, the complex emotion generation module decides on the final complex emotion + +corresponding to a combination of the emotion types inferred from the three different unimodal networks + +![Flowchart of the Emotion expansion module. The module is enclosed in a dashed box labeled 'Emotion expansion'. Inside, a box labeled 'Complex emotion generation' contains three sub-components: 'Artificial emotion model', 'Trainer (Complex emotion)', and 'Complex emotion inference engine', connected by downward arrows. The final output of the module is 'Complex emotion'. A label 'H.862.5(21)_F07' is at the bottom right.](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +``` +graph TD; subgraph Emotion_expansion [Emotion expansion]; subgraph Complex_emotion_generation [Complex emotion generation]; A[Artificial emotion model] --> B[Trainer (Complex emotion)]; B --> C[Complex emotion inference engine]; end; C --> D[Complex emotion]; +``` + +Flowchart of the Emotion expansion module. The module is enclosed in a dashed box labeled 'Emotion expansion'. Inside, a box labeled 'Complex emotion generation' contains three sub-components: 'Artificial emotion model', 'Trainer (Complex emotion)', and 'Complex emotion inference engine', connected by downward arrows. The final output of the module is 'Complex emotion'. A label 'H.862.5(21)\_F07' is at the bottom right. + +Figure 7 – Emotion expansion module + +#### 7.4.1 Artificial emotion model + +The artificial emotion model generates complex emotion data by combining basic emotions based on emotion probabilities. + +- Input: basic emotion data +- Output: complex emotion data + +#### 7.4.2 Trainer for complex emotion generation + +The trainer trains neural networks for complex emotion generation using complex emotion data. + +- Input: complex emotion data +- Output: complex emotion inference engine + +#### 7.4.3 Complex emotion inference engine + +Complex emotion inference engine makes inferences on complex emotions by analysing complex emotion data and basic emotion data (multimodal emotion and unimodal emotion). + +- Input: complex emotion data, multimodal emotion, unimodal emotion +- Output: complex emotion + +### 7.5 Multimedia knowledge database + +Multimedia knowledge database presented in Figure 8, generates and store datasets to train the emotion recognition model based on a large amount of multimedia data received from outside sources. + +In the multimedia knowledge database, the intelligent studio tool helps to generate labelled data for given videos by annotating text-emotion data, speech-emotion data, and image-emotion data with "given emotion tags which are provided by the data manager". The labelled data can be used to train the unimodal networks and multimodal networks. + +In the general training process for emotion recognition, the multimodal data are collected from the target contents which contain more than one type of media data. From the collected data, the primary feature vectors are generated for each type of media data. User data are also used for generating the primary feature vectors based on the user information and the content information of the user's preferences. These two types of primary feature vectors are integrated to generate the secondary feature vectors, which will then be used in deciding the corresponding emotion vectors based on the multiple training data. In the multimodal emotion recognition process, the relations between the resulting multiple secondary feature vectors from different media types and the emotion vectors are used as the training data set to recognize emotion. + +The training processes for different media types are explained in the following clauses. + +![Diagram of the Multimedia knowledge database module. A dashed box labeled 'Multimedia knowledge database' contains a flow: 'Video data' points to 'Intelligence studio', which points to a stack of three boxes: 'Text-emotion data', 'Speech-emotion data', and 'Image-emotion data'. The label 'H.862.5(21)_F08' is at the bottom right.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +``` +graph LR; subgraph Multimedia_knowledge_database [Multimedia knowledge database]; direction LR; A[Video data] --> B[Intelligence studio]; B --> C[Text-emotion data]; B --> D[Speech-emotion data]; B --> E[Image-emotion data]; end; style C fill:#fff,stroke:#000; style D fill:#fff,stroke:#000; style E fill:#fff,stroke:#000; +``` + +Diagram of the Multimedia knowledge database module. A dashed box labeled 'Multimedia knowledge database' contains a flow: 'Video data' points to 'Intelligence studio', which points to a stack of three boxes: 'Text-emotion data', 'Speech-emotion data', and 'Image-emotion data'. The label 'H.862.5(21)\_F08' is at the bottom right. + +**Figure 8 – Multimedia knowledge database module** + +## 8 Application to multimodal emotion analysis + +When people talk, they use multiple modalities. Emotion is one of the key features to understand the meaning of the utterances made by the speaker. Therefore, a conversation system with the capability to recognize emotion can better understand the user and produce a better reply. It is a human-machine conversation system where the computer can recognize emotion in the user's speech and/or text, also using the video information of the face of the human to produce a reply. + +In the conversation system with emotion capability, emotion is recognised in the following way typically and reflected in the speech production side. First, a set of emotion related cues is extracted from text, voice, and video. Then, each recognition module for text, voice, and video, recognises emotion independently. The emotion recognition module determines the final emotion based on each emotion. The emotion will be transferred to the dialogue processing module. Then the dialogue processing module produces the reply based on the final emotion and meaning from the text and video analysis. Finally, the speech synthesis module produces the speech from the reply through text. The production side can also produce the reply with an emotion. + +A typical application that uses emotion in the conversation is the chatbot application. The chatbot application is widely used to provide services such as answering questions for customers in different industry domains. The multimodal capabilities enhance the customers' satisfaction with the provided services. The emotion analysis function also provides a better understanding of the customers' needs. For example, a user who uses the virtual customer service may also be able to receive a service with a smile from a chatbot. The user can interact with the chatbot via a multimodal interface such as text, voice, image, music, facial expression, video, etc. The modalities and media types used can vary depending on the application scenario. + +Other example applications that use multimodal emotion analysis include a service where speech carries information not only about the lexical content, but also about a variety of other aspects such as age, gender, signature, and the emotional state of the speaker. Speech synthesis is evolving towards supporting these aspects. This is the case, for instance, of a human-machine dialogue where the message conveyed by the machine is more effective if it carries an emotion properly related to the emotion detected in the human speaker. + +Another example application is in the machine translation service domains. Automatic speech translation technology denotes technology that recognizes a voice uttered in a language by a speaker, converts the recognized voice into another language through automatic translation, and outputs a converted voice as text-type subtitles or as a synthesized voice thereby preserving the speaker's features including their emotion features in the translated speech. As interest in voice synthesis increases among main technologies for automatic interpretation, the research is concentrated on personalized voice synthesis, which is a technology that outputs a target language as a synthesis voice which is similar to the tone (or an utterance style with emotion) of a speaker. + +Figure 9 shows an example of a personalized automatic translation system that reflects emotional features in the translated speech. The automatic interpretation system for generating a synthetic sound having characteristics similar to those of the original speaker's voice including a speech recognition to generate text data for an original speech signal of the original speaker and extract characteristic information such as the pitch information, vocal intensity information, speech speed information, emotion features and vocal tract characteristic information of the original speech. The text data is then produced by the speech recognition module and goes through the automatic translation module to generate a synthesis-target translation and a speech synthesis module to generate a synthetic sound that resembles the original speaker using the extracted characteristic information. + +![Block diagram of a personalized automatic translation system. The system takes 'Text' and 'Speech' as inputs. 'Text' is processed by 'Translation' to produce 'Translation result'. 'Speech' is processed by 'Speech recognition' to produce 'Text' and by 'Speech feature extraction' to produce 'Speech features with emotion'. Both 'Translation result' and 'Speech features with emotion' are processed by 'Speech synthesis' to produce the final 'Personalized speech'.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +``` +graph LR; Text --> Translation; Speech --> SR[Speech recognition]; SR --> Text2[Text]; Text2 --> Translation; Translation --> TR[Translation result]; Speech --> SFE[Speech feature extraction]; SFE --> SF[Speech features with emotion]; TR --> SS[Speech synthesis]; SF --> SS; SS --> PS[Personalized speech]; +``` + +H.862.5(21)\_F09 + +Block diagram of a personalized automatic translation system. The system takes 'Text' and 'Speech' as inputs. 'Text' is processed by 'Translation' to produce 'Translation result'. 'Speech' is processed by 'Speech recognition' to produce 'Text' and by 'Speech feature extraction' to produce 'Speech features with emotion'. Both 'Translation result' and 'Speech features with emotion' are processed by 'Speech synthesis' to produce the final 'Personalized speech'. + +**Figure 9 – Personalized automatic translation system** + +## Appendix I + +### Survey on SDO's activity regarding typical emotional service + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 SDO activities on emotion + +Emotion-based studies are already progressing in several SDOs and is briefly summarized in some ITU-T Recommendations that are published. However, before further adopting new current neural networks in emotional-based multimodality user interfaces (UI), it is necessary to review the status of these activities. + +#### I.1.1 W3C + +The multimodal interaction working group [b-W3C MMI] has published a working draft of EMMA, *Extensible MultiModal Annotation markup language* Version 2.0 [b-W3C EMMA]. This specification describes markup for representing interpretations of user input (speech, keystrokes, pen input, etc.) and productions of system output together with annotations for confidence scores, timestamps, medium, etc. It forms part of the proposals for the W3C multimodal interaction framework. + +The emotion incubator group will discuss and propose scientifically valid representations of those aspects of emotional states that appear to be relevant for several use cases. The group will condense these considerations into a formal draft specification. + +Emotion-oriented (or "affective") computing is gaining importance as interactive technological systems become more sophisticated. Representing the emotional states of a user or the emotional states to be simulated by a user interface requires a suitable representation format. Although several non-standard mark-up languages containing elements of emotion annotation have been proposed, none of these languages have undergone thorough scrutiny by emotion researchers, nor have they been designed for the generality of use in a broad range of application areas. + +The deliverables are: + +- Final Report of the (First) Emotion Incubator Group, 10 July 2007 +- Emotion Markup Language: Requirements with Priorities, 13 May 2008 +- Elements of an EmotionML 1.0, Final Report of the Emotion Markup Language Incubator Group, 20 November 2008 + +#### I.1.2 ISO/IEC JTC 1/SC 35 + +This group is the standardization in the field of user-system interfaces in information and communication technology (ICT) environments. It provides support for these interfaces to serve all users, including people having accessibility or other specific needs, with a priority of meeting the JTC 1 requirements for cultural and linguistic adaptability [b-ISO/IEC JTC 1/SC 35]. + +This includes: + +- user interface accessibility (requirements, needs, methods, techniques and enablers); +- cultural and linguistic adaptability and accessibility (such as evaluation of cultural and linguistic adaptability of ICT products, harmonized human language equivalents, localization parameters, voice messaging menus); +- user interface objects, actions, and attributes; +- methods and technologies for controlling and navigating within systems, devices and applications in visual, auditory, tactile and other sensorial modalities (such as by voice, vision, movement, gestures); + +- symbols, functionality and interactions of user interfaces (such as graphical, tactile and auditory icons, graphical symbols and other user interface elements); +- visual, auditory, tactile and other sensorial input and output devices and methods in ICT environments (for devices such as keyboards, displays, mice); +- user interfaces for mobile devices, handheld devices and remote interactions + +Further, ISO/IEC CD 30150 is under development. + +- Information technology – Affective computing user interface – Framework + +#### **I.1.3 OMA** + +OMA multimodal and multi-device service requirements' document describe the requirements for multimodal and multi-devices services in the scope of the OMA architecture. Such services enable access to mobile services through different modalities (e.g., keypad, graphic user interface (GUI), voice, handwriting) or devices. + +- The requirements are primarily viewed from an end user point of view. Implications are derived in terms of requirements on network operators, service providers and terminal manufacturers. +- The requirements apply only to the supporting applications or services for which multimodal or multi-device interactions make sense and are desired. Applications and services may otherwise be designed without providing such a user experience. + +OMA multimodal and multi-device enabler architecture documents describe the architecture needed for the OMA multimodal and multi-device enabler. Such a multimodal and multi-device enabler enables access to mobile services through different modalities (e.g., keypad, graphic user interface, voice, handwriting) or devices. + +- The architecture enables applications or services supporting multimodal or multi-device user interactions with minimal changes to the programming model for non-multimodal and multi-device applications or services such as browsing. + +## Bibliography + +- [b-ITU-T H.703] Recommendation ITU-T H.703 (2016), *Enhanced user interface framework for IPTV terminal devices*. +- [b-ITU-T F.746.3] Recommendation ITU-T F.746.3 (2015), *Intelligent question answering service framework*. +- [b-ITU-T F.746.7] Recommendation ITU-T F.746.7 (2018), *Metadata for an intelligent question answering service*. +- [b-ISO/IEC JTC 1/SC 35] ISO/IEC JTC 1/SC 35, *User interfaces*. + +- [b-Ekman] Ekman, P. (1999). *Basic Emotions*. In T. Dalgleish and T. Power (Eds.) *The Handbook of Cognition and Emotion* Pp. 45-60. Sussex, U.K.: John Wiley & Sons, Ltd. +- [b-W3C MMI] Multimodal Interaction Working Group (2015). + +- [b-W3C EMMA] W3C Working Group Note (2017), *Extensible MultiModal Annotation markup language Version 2.0*. + + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.862.7-202401-I_PDF-E/3b621c21b0af3a504a28d2547e87138f_img.jpg b/marked/H/T-REC-H.862.7-202401-I_PDF-E/3b621c21b0af3a504a28d2547e87138f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e85f11d12bb96d731870c2eb689c863b8ebb0a1 --- /dev/null +++ b/marked/H/T-REC-H.862.7-202401-I_PDF-E/3b621c21b0af3a504a28d2547e87138f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:952a08105a6f1336815bc1e6f3fbc6bad6a62302129c38ee49a95ab3ac508724 +size 27860 diff --git a/marked/H/T-REC-H.862.7-202401-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.862.7-202401-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/H/T-REC-H.862.7-202401-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/H/T-REC-H.862.7-202401-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.862.7-202401-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8369997e347c6f6ef41f899dbdce09178cc4be98 --- /dev/null +++ b/marked/H/T-REC-H.862.7-202401-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:beaca43074488d166fe3251f20afe971c87a649fb9ac0278b8eab65d569047eb +size 31654 diff --git a/marked/H/T-REC-H.862.7-202401-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.862.7-202401-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21e9f88ae0a7ccb4d21eca111d62c15d4ab66572 --- /dev/null +++ b/marked/H/T-REC-H.862.7-202401-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:413c71b61b2eff6eee2c72536dfec015deb1868f7bfe07dce3b918840f5158fb +size 85136 diff --git a/marked/H/T-REC-H.862.7-202401-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/H/T-REC-H.862.7-202401-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e810beaa8aa6501a661c8dfedb76559f062cde7d --- /dev/null +++ b/marked/H/T-REC-H.862.7-202401-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e01b27e2fda7be92ef20329d9c0224f6ab6109248d9dc28b7d88e67123823a61 +size 40588 diff --git a/marked/H/T-REC-H.862.7-202401-I_PDF-E/raw.md b/marked/H/T-REC-H.862.7-202401-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..97521b6c309df6db06082e015528279d5ad67bbe --- /dev/null +++ b/marked/H/T-REC-H.862.7-202401-I_PDF-E/raw.md @@ -0,0 +1,429 @@ + + +# Recommendation + +## **ITU-T H.862.7 (01/2024)** + +SERIES H: Audiovisual and multimedia systems + +E-health multimedia systems, services and applications – +Multimedia e-health data exchange services + +--- + +# **Interoperability framework for sleep management services** + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +### **Audiovisual and multimedia systems** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | +| Personal health systems | H.810-H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820-H.859 | +| Multimedia e-health data exchange services | H.860-H.869 | +| Safe listening | H.870-H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.862.7 + +# Interoperability framework for sleep management services + +## Summary + +Recommendation ITU-T H.862.7 specifies an open, interoperable application programming interface (API) for smart sleep management devices and sleep services. In order to provide an individual with optimal sleep, data collection, analysis, and customized services on individual sleep are required. For this, interoperability between sleep management devices and services based on the Internet of things must be secured. Interoperability of services covered by Recommendation ITU-T H.862.7 includes interoperability of data and interoperability at the API level. + +Sleep occupies a third of our lives, and helps to relieve the physical and mental fatigue experienced during the day. Therefore, it is possible to obtain an improvement effect that can enhance quality of life based on the understanding of sleep time and quality through sleep monitoring. + +With the growth of the sleep market, various sleep monitoring products combined with information and communication technology have been launched, mainly composed of dedicated applications and sensors. The use of products composed of such dedicated software for each sensor is a major limitation in service operation. This is due to difficulties of integration with existing service data and sharing data with other services when changing the product or using it with other services. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.862.7 | 2024-01-13 | 16 | 11.1002/1000/15765 | + +## Keywords + +Interoperability framework, sleep management services. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Background..... | 2 | +| 7 Interoperability between sleep management devices and services..... | 2 | +| 7.1 Sleep management services ..... | 2 | +| 7.2 Interoperability points ..... | 3 | +| 7.3 Interoperability targets..... | 3 | +| 7.4 End-to-end security ..... | 5 | +| 8 Interoperability framework..... | 5 | +| 8.1 Service function..... | 6 | +| 8.2 Interoperability data core..... | 6 | +| Bibliography..... | 8 | + + + +# Recommendation ITU-T H.862.7 + +# Interoperability framework for sleep management services + +# 1 Scope + +This Recommendation specifies sleep management service functions that are based on an open application programming interface (API) and a method for securing interoperability in terms of data and management. + +This Recommendation includes: + +- an open API for sleep management services; +- function APIs; +- management APIs; +- interoperability between sleeping devices and services. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +None. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 interoperability** [b-ITU-T Y.101]: The ability of two or more systems or applications to exchange information and to mutually use the information that has been exchanged. + +**3.1.2 open interface** [b-ITU-T Y.4201]: A public standard for connecting hardware to hardware and software to software. Open interfaces are designed and documented for safe and easy use by third party developers and freely available to all. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------------------| +| API | Application Programming Interface | +| ECG | Electrocardiogram | +| EEG | Electroencephalogram | +| FHIR | Fast Healthcare Interoperability Resources | + +# 5 Conventions + +None. + +# 6 Background + +Humans spend about one-third of their lives sleeping. The duration or quality of sleep greatly affects quality of life and health. Various types of device have been invented and used to improve the quality of sleep for a better life. Recently, devices have evolved from the passive form to monitor and improve sleep quality by direct intervention. In order to provide optimized sleep, customized services are required through individual sleep data collection and analysis. The sleep management service in this Recommendation follows the requirements of [b-ITU-T H.862.0]. + +This Recommendation provides an open interoperability API for smart sleep management devices and services. + +# 7 Interoperability between sleep management devices and services + +## 7.1 Sleep management services + +A sleep management service requires various components such as an Internet of things (IoT) sleep management device (the core element), network infrastructure and a service platform. + +Various technologies are used in a sleep management service for communication between a device, data relay unit, personal service terminal unit and service platform. + +A sleep management service includes IoT protocols, security and personal information protection, data analysis and management, a service coordinator and service management. + +When the perspective is expanded to various services and devices for sleep management, interoperability becomes an important consideration in service development and operation. The components of a sleep management service are shown in Figure 1. + +![Figure 1: Components of a sleep management service. The diagram shows a flow from left to right: Sleep aid device, Relay unit, Interoperability points, Sleep management platform, Interoperability points, and Applications/services. The Sleep aid device is connected to the Relay unit and the first Interoperability points. The Relay unit is connected to the first Interoperability points. The first Interoperability points are connected to the Sleep management platform. The Sleep management platform is connected to the second Interoperability points. The second Interoperability points are connected to the Applications/services. The diagram is labeled H.862.7(24) in the bottom right corner.](3b621c21b0af3a504a28d2547e87138f_img.jpg) + +``` + +graph LR + A[Sleep aid device] <--> B[Relay unit] + A <--> C[Interoperability points] + B <--> C + C <--> D[Sleep management platform] + D <--> E[Interoperability points] + E <--> F[Applications/services] + +``` + +Figure 1: Components of a sleep management service. The diagram shows a flow from left to right: Sleep aid device, Relay unit, Interoperability points, Sleep management platform, Interoperability points, and Applications/services. The Sleep aid device is connected to the Relay unit and the first Interoperability points. The Relay unit is connected to the first Interoperability points. The first Interoperability points are connected to the Sleep management platform. The Sleep management platform is connected to the second Interoperability points. The second Interoperability points are connected to the Applications/services. The diagram is labeled H.862.7(24) in the bottom right corner. + +**Figure 1 – Components of a sleep management service** + +Although there are many standards applicable to IoT and lifelog interoperability, the following problems exist in accommodating various requirements of sleep management services. + +- While IoT standards are simple to apply to the functions of sleep management devices, such application increases their production cost. +- The Health Level 7 fast healthcare interoperability resource [b-HL7 FHIR R5a] is used for lifelog interoperability, but this standard only deals with data interoperability, so it is inappropriate to apply to services. + +## 7.2 Interoperability points + +Interoperability points include devices, relays, platforms and application services. Sleep management devices are connected to the service platform through relays or by themselves. A service platform is connected to application programs or services. + +## 7.3 Interoperability targets + +In the sleep management service, interoperability targets include service data, service contents, and service functions. + +### 7.3.1 Service data + +Service data are those for sleep monitoring. Sleep monitoring data are expressed as measurement values measured by sleep aid devices or as values for combined sleep duration and quality. It is not easy to integrate sleep measurement values in terms of services because there are various sensors. In addition, it is difficult to accurately express sleep monitoring state because sensors have different accuracies. Various methods are used to express duration and quality of sleep in various services. Figure 2 is a diagram for data conversion for sleep management services. + +![Diagram showing data conversion for sleep management services. It consists of three vertical columns: Sensor data, Sleep common data, and Service data. Sensor data includes Pulse, Sound, Press, ECG, EEG, and Etc. Sleep common data includes Bedtime, Sleep stage, Sleep duration, Wake-up time, and Sleep goal. Service data includes Data visualization.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +| Sensor data | Sleep common data | Service data | +|-------------|-------------------|--------------------| +| Pulse | Bedtime | Data visualization | +| Sound | Sleep stage | | +| Press | Sleep duration | | +| ECG | Wake-up time | | +| EEG | Sleep goal | | +| Etc. | | | + +Diagram showing data conversion for sleep management services. It consists of three vertical columns: Sensor data, Sleep common data, and Service data. Sensor data includes Pulse, Sound, Press, ECG, EEG, and Etc. Sleep common data includes Bedtime, Sleep stage, Sleep duration, Wake-up time, and Sleep goal. Service data includes Data visualization. + +H.862.7(24) + +ECG: electrocardiogram; EEG: electroencephalogram + +**Figure 2 – Data conversion for sleep management services [b-ITU-T H.862.1]** + +### 7.3.2 Service content + +Service content includes sounds, images, etc. to provide a sleep service. Service content is provided in the form of advice, white noise and visualization images to help sleep. These contents should be standardized so that they are used for various services with interoperability. + +#### 7.3.2.1 Providing personalized sleep content + +Sleep content is provided to users according to their disease or habit. In order to provide customized services to users, it is necessary to record and analyse their sleep diseases and habits. Figure 3 shows the basic process for providing personalized sleep content. + +![Flowchart showing the process of providing customized content. Inputs: User information (Sleep disease, sleep pattern) and Sleep monitoring device. These lead to Personalized sleep management service. This service leads to IoT device, Personalized service contents, and Sleep guideline. Reference: H.862.7(24).](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +``` + +graph LR + A["User information +(Sleep disease, sleep pattern)"] --> B["Personalized sleep +management service"] + C["Sleep monitoring device"] --> B + B --> D["IoT device"] + B --> E["Personalized service +contents"] + B --> F["Sleep guideline"] + style H862724[H.862.7(24)] + +``` + +Flowchart showing the process of providing customized content. Inputs: User information (Sleep disease, sleep pattern) and Sleep monitoring device. These lead to Personalized sleep management service. This service leads to IoT device, Personalized service contents, and Sleep guideline. Reference: H.862.7(24). + +**Figure 3 – Process of providing customized content** + +Service content data are composed of web standard documents, image and video standards, and IoT standard device control forms rather than user interface-dependent functions to provide contents of various expression types. Content is listed by type in Table 1. + +**Table 1 – Content by type** + +| Content type | Content composition | Example | +|--------------------|--------------------------------------------------------|-------------------------------------------------------------------------| +| Visual data | Visual contents composed of text, images, videos, etc. | Images or video clips and text on the books | +| Auditory data | Audio files that are heard through the auditory sense | Sound for the sleep induction (white noise) | +| Environmental data | IoT devices that help for sleeping | Sleep surroundings (lighting control, humidity and temperature control) | + +### 7.3.3 Service functions + +Sleep service functions are classified as those for information provision, recording and improvement. + +#### 7.3.3.1 Sleep information provision + +Sleep information provision is a function that provides content helpful for sleep. Sleep information provision is divided into two types: one that provides information related to sleep at random; and one that identifies sleep problems and provides customized information to the user. Personalized information is helpful for both records and disorders of sleep. + +#### 7.3.3.2 Sleep record + +A sleep record is classified as one by a user or one containing information obtained from an IoT device. Such records are important functional elements for checking the quantity and quality of the sleep of users and providing customized services to them. In order for sleep records to be interoperable, they must be expressed based on a common data model that is expressed in various services. As shown in Figure 2, it is expressed in the form of sleep common data in [b-ITU-T H.862.1]. + +#### 7.3.3.3 Sleep improvement + +Sleep improvement is the provision of digital services to assist sleep. Sleep improvement is a form of content provision, and involves detection of status in real time with an IoT device. In order to secure interoperability in sleep improvement, an IoT standard-based device connection method for service provision is utilized. + +### 7.3.4 Service devices + +Sleep management services employ devices to monitor, induce and improve sleep, as listed in Table 2. These devices are required to follow standard interfaces and protocols to ensure interoperability. + +**Table 2 – Type of devices** + +| Device type | Description | +|--------------------|----------------------------------------------------------------| +| Sleep monitoring | Devices to measure and record your sleep | +| Sleep induction | A device that helps you fall asleep using lights, sounds, etc. | +| Sleep improvement | Personalized device to improve sleep disorders | + +## **7.4 End-to-end security** + +Security is essential to processing sensitive health information. This Recommendation has been developed to support the development of secure systems. + +Security that is excessive or insufficient can be both costly and risky. Security is dynamic and becomes more demanding over time. Therefore, security must be considered comprehensively. + +Security standards considered in sleep management services are listed in Table 3, which includes advanced security and privacy requirements, such as identity management and prevention of source denial. Confidentiality means that only those who have the right to know have access to the data. Integrity ensures that the data is not tampered with or modified in any way to compromise the reliability of the data. Availability means timely access to information. Identity management enables the association of health information with the correct individuals by managing user identities across services. Nonrepudiation of origin is achieved using digital signatures, which guarantee that the sender of information cannot deny having sent it. + +**Table 3 – An overview of security standards used in sleep management services** + +| Standards development organizations | Security standards | Security requirements | +|--------------------------------------------|---------------------------|-----------------------------------------------------------------| +| IETF | [b-IEFC RFC 5246] | Network protocol, confidentiality, integrity and authentication | +| HL7 | [b-HL7 FHIRR5b] | Auditing | +| W3C | [b-W3C XML] | Data encryption | +| Bluetooth Special Interest Group | [b-Bluetooth HDP] | Confidentiality, integrity and authentication | + +# **8 Interoperability framework** + +Interoperability in management services is required to be considered from the perspective of data, content and devices of sleep. The interoperability framework for sleep management services is shown in Figure 4. + +![Diagram of the Interoperability framework for sleep management services. The diagram shows three main components: Service data, Service contents, and Service devices on the left; a central box containing three functions: Sleep record function (Data API, Data translation, Data processing), Sleep information provision function (Information API, Contents management, Data processing), and Sleep induction and improvement function (Sleep analysis, Personalized IoT control, State change monitoring); and an Interoperability data core on the right containing Service ontology, Common data model, Device registry, Service data repository, and Service API. The label H.862.7(24) is at the bottom right.](d4af765160d04ecef538e5066006dc77_img.jpg) + +The diagram illustrates the Interoperability framework for sleep management services. It is structured as follows: + +- Service data**, **Service contents**, and **Service devices** are listed vertically on the left. +- The central part consists of three stacked boxes representing service functions: + - Sleep record function**: contains **Data API**, **Data translation**, and **Data processing**. + - Sleep information provision function**: contains **Information API**, **Contents management**, and **Data processing**. + - Sleep induction and improvement function**: contains **Sleep analysis**, **Personalized IoT control**, and **State change monitoring**. +- The **Interoperability data core** is on the right, containing: + - Service ontology** + - Common data model** + - Device registry** + - Service data repository** + - Service API** +- The label **H.862.7(24)** is located at the bottom right of the diagram. + +Diagram of the Interoperability framework for sleep management services. The diagram shows three main components: Service data, Service contents, and Service devices on the left; a central box containing three functions: Sleep record function (Data API, Data translation, Data processing), Sleep information provision function (Information API, Contents management, Data processing), and Sleep induction and improvement function (Sleep analysis, Personalized IoT control, State change monitoring); and an Interoperability data core on the right containing Service ontology, Common data model, Device registry, Service data repository, and Service API. The label H.862.7(24) is at the bottom right. + +**Figure 4 – Interoperability framework for sleep management services** + +## 8.1 Service function + +This function records sleep provided by the sleep management service, provides information, and induces and improves sleep. + +### 8.1.1 Sleep record function + +This function records and processes sleep data, consisting of data API, data translation and data processing. + +### 8.1.2 Sleep information provision function + +This function provides sleep-related information. consisting of information API, component management and data process. + +### 8.1.3 Sleep induction and improvement function + +This function analyses sleep data and provides functions to induce and improve sleep, consisting of sleep analysis, personalized IoT control and state change monitoring. + +## 8.2 Interoperability data core + +This function refers to the basic elements to provide interoperability in sleep management services, including the items in clauses 8.2.1 and 8.2.5. + +### 8.2.1 Service ontology + +In order to provide semantic interoperability of services, an ontology-based semantic interoperability framework is utilized. + +### 8.2.2 Common data model + +Data collected from various sensors must be stored and provided in the form of a common data model to ensure interoperability. The common data model converts various types of information into an abstracted form of common data and may be provided as visualized information to a user. + +### 8.2.3 Device registry + +In order to provide services with the data of various manufacturers, for each device, metadata is stored and a method for identification is provided. + +### **8.2.4 Service data repository** + +The sleep management service stores data collected from devices and data necessary for the service in order to measure and manage the sleep of the user. + +### **8.2.5 Service application programming interface** + +APIs that should be provided include those for management of users, data and services, as well as APIs for functional interoperability. These APIs are provided in open form. In particular, the API that collects and transmits the sleep state from the sensor exchanges data in association with other service providers through a standardized open interface, such as those described in [b-HL7 FHIR R5b]. + +# Bibliography + +- [b-ITU-T H.862.0] Recommendation ITU-T H.862.0 (2019), *Requirements and framework for ICT sleep management service models*. +- [b-ITU-T H.862.1] Recommendation ITU-T H.862.1 (2020), *Data model for sleep management services*. +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global information infrastructure terminology: Terms and definitions*. +- [b-ITU-T Y.4201] Recommendation ITU-T Y.4201 (2018), *High-level requirements and reference framework of smart city platforms*. +- [b-Bluetooth HDP] Bluetooth SIG (2024), *Health device profile 1.1*. Available [viewed 2024-03-14] at: +- [b-HL7 FHIR R5a] HL7 FHIR Release 5 (2011+), *FHIR overview*. Available [viewed 2024-03-18] at: +- [b-HL7 FHIR R5b] HL7 FHIR Release 5 (2011+), *Resource AuditEvent – Content*. Available [viewed 2024-03-18] at: +- [b-IETF RFC 5246] IETF RFC 5246 (2008), *The transport layer security (TLS) protocol – Version 1.2*. +- [b-W3C XML] W3C Recommendation (2013), *XML encryption syntax and processing – Version 1.1*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.862.8-202503-I_PDF-E/raw.md b/marked/H/T-REC-H.862.8-202503-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ef72ee69af119d39e681f638519b6b8707717257 --- /dev/null +++ b/marked/H/T-REC-H.862.8-202503-I_PDF-E/raw.md @@ -0,0 +1,668 @@ + + +# Recommendation **ITU-T H.862.8 (03/2025)** + +SERIES H: Audiovisual and multimedia systems + +E-health multimedia systems, services and applications – +Multimedia e-health data exchange services + +--- + +# **Requirements and framework of the occupational health service platform** + +![ITU logo](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features the letters "ITU" in a bold, blue, sans-serif font, superimposed on a stylized globe icon with intersecting lines. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +### **Audiovisual and multimedia systems** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | +| Personal health systems | H.810-H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820-H.859 | +| Multimedia e-health data exchange services | H.860-H.869 | +| Safe listening | H.870-H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.862.8 + +# Requirements and framework of the occupational health service platform + +## Summary + +According to the WHO, occupational health is a field of public health focused on promoting and maintaining the highest levels of physical, mental, and social well-being for workers across all occupations. Achieving this occupational health goal requires tracking and monitoring workers' health, identifying symptoms related to occupational factors, and providing appropriate diagnoses and treatments. Another critical aspect of occupational health is preventing exposure to occupational hazards that could harm workers' health. These hazards depend on factors such as the type of work, the level of physical and mental exertion involved, the materials and products used, and the working environment. + +To monitor workers' health and occupational hazards effectively, various Internet of things (IoT) devices can be used to monitor health status and workplace environments. The collected data can be stored in the occupational health service platform, to provide occupational health services such as health surveillance, mass immunization, injury management, and mental treatments. A key challenge for the occupational health service platform is providing standardized approaches to manage occupational health data from diverse sources and formats, such as personal health records, health devices, sensors, and other platforms. Moreover, it is essential to ensure the collected data is delivered appropriately to various users including healthcare professionals, health service providers, researchers, labour and safety policymakers, and workers. To address these challenges, the platform should enable the construction and exchange of occupational health data in an interoperable way. + +Recommendation ITU-T H.862.8 outlines the framework and requirements for the occupational health service platform. This framework aims to enhance data collection, processing, privacy protection, and interoperability among data sources and users. The platform supports various occupational health use cases, including monitoring workers' health, informing policy development, and implementing of tailored health programs for workers. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.862.8 | 2025-03-16 | 21 | 11.1002/1000/16249 | + +## Keywords + +Healthcare platform, occupational data for health, occupational health. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|--------------|---------------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Framework of the occupational health service platform ..... | 3 | +| 6.1 | Overview ..... | 3 | +| 6.2 | Conceptual framework of the occupational health service platform..... | 4 | +| 7 | Requirements for the occupational health service platform ..... | 5 | +| 7.1 | Occupational health data collection..... | 5 | +| 7.2 | Data classification ..... | 5 | +| 7.3 | Data storage management..... | 6 | +| 7.4 | Data integration and interoperability..... | 6 | +| 7.5 | Networking..... | 7 | +| 7.6 | Privacy and security support ..... | 7 | +| Appendix I | – Implementation details of the occupational health service platform ..... | 8 | +| I.1 | Overview ..... | 8 | +| I.2 | Data sources of the occupational health service platform ..... | 8 | +| I.3 | Users of the occupational health service platform ..... | 9 | +| I.4 | Functions of the occupational health service platform..... | 9 | +| Appendix II | – Use cases of the occupational health service platform ..... | 13 | +| II.1 | Use case for occupational health surveillance with occupational hazard analysis ..... | 13 | +| II.2 | Use case for occupational injury and illness management..... | 14 | +| II.3 | Use case for mass immunization ..... | 15 | +| Bibliography | ..... | 18 | + + + +# Recommendation ITU-T H.862.8 + +## Requirements and framework of the occupational health service platform + +# 1 Scope + +This Recommendation describes the requirements and framework of occupational health service platforms. The scope of this Recommendation includes: + +- Requirements for the occupational health service platform. +- Framework for the occupational health service platform. +- Use-cases of occupational health service platforms (Appendix II). + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.81x] Recommendations ITU-T H.81x-series (2019), *Interoperability design guidelines for personal connected health systems*. +- [HL7 FHIR] HL7 (2023), *HL7 FHIR Release #5 Health Level 7 Fast Health Interoperability Resources*. + +- [IEEE 802.11] IEEE Std 802.11 (2020), *Telecommunications and Information Exchange between Systems – Local and Metropolitan Area Networks – Specific Requirements – Part 11: Wireless LAN medium Access Control (MAC) and Physical Layer (PHY) Specifications*. +- [IETF RFC 8446] IETF RFC 8446 (2018), *The Transport Layer Security (TLS) Protocol Version 1.3*. + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 electronic health record (EHR)** [b-ITU-T H.810]: The electronic health record (EHR) is a longitudinal electronic record of patient health information generated by one or more encounters in any care delivery setting. Included in this information are patient demographics, progress notes, problems, medications, vital signs, past medical history, immunizations, laboratory data and radiology reports. The EHR automates and streamlines the clinician's workflow. The EHR has the ability to generate a complete record of a clinical patient encounter as well as supporting other care-related activities directly or indirectly via an interface including evidence-based decision support, quality management and outcomes reporting. + +**3.1.2 electronic medical record (EMR)** [b-ITU-T H.810]: EMRs are computerized legal clinical records created in care delivery organizations (CDOs) such as hospitals and physician offices. An + +electronic medical record is owned by the organization, practice or corporation that provided the health care be it a clinic, a hospital or a doctor. + +**3.1.3 enterprise system** [b-ISO 41014]: A combination of computer hardware and software applications that an organization uses to support its business processes and operations. + +**3.1.4 healthcare organization** [b-ISO 22886]: Healthcare organization involved in the direct or indirect provision of healthcare. + +**3.1.5 occupational health** [b-WHO]: Area of work in public health to promote and maintain the highest degree of physical, mental and social well-being of workers in all occupations. + +### **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following term: + +**3.2.1 occupational data for health (ODH)**: A set of information about work environments, workers health status and histories, aimed at improving occupational safety and well-being. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------------------| +| AES | Advanced Encryption Standards | +| BMI | Body Mass Index | +| CDG | Continua Design Guidelines | +| CDO | Care Delivery Organization | +| CoAP | Constrained Application Protocol | +| CSV | Comma-Separated Values | +| DICOM | Digital Imaging and Communications in Medicine | +| EHR | Electronic Health Record | +| EMR | Electronic Medical Record | +| FHIR | Fast Health Interoperability Resources | +| GDPR | General Data Protection Regulation | +| HL7 | Health Level 7 | +| HTTPS | Hypertext Transfer Protocol Secure | +| ICD | International Classification of Diseases | +| IG | Implementation Guide | +| IHE | Integrating the Healthcare Enterprise | +| IPA | International Patient Access | +| IPS | International Patient Summary | +| JSON | JavaScript Object Notation | +| LAN | Local Area Network | +| MFA | Multi-Factor Authentication | +| MQTT | Message Queuing Telemetry Transport | +| ODH | Occupational Data for Health | + +| | | +|------|-----------------------------------------------| +| OSHA | Occupational Safety and Health Administration | +| PHD | Personal Health Device | +| PPE | Personal Protective Equipment | +| RBAC | Role-Based Access Control | +| RIM | Reference Information Model | +| RSA | Rivest-Shamir-Adleman | +| SQL | Structured Query Language | +| SSL | Secure Sockets Layer | +| TLS | Transport Layer Security | +| WAN | Wide Area Network | +| WLAN | Wireless Local Area Network | +| WPA3 | Wi-Fi Protected Access 3 | + +# 5 Conventions + +In this Recommendation: + +The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. + +The keywords "**is recommended**" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +The keywords "**can optionally**" and "**may**" indicate an optional requirement which is permissible, without implying any sense of being recommended. These terms are not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. + +# 6 Framework of the occupational health service platform + +### 6.1 Overview + +The occupational health service platform is a comprehensive solution designed to provide the monitoring, management, and enhancement of workers' health and safety, encompassing not only physical health but also mental and social well-being. The key objectives of the occupational health service platform are to integrate and process data from workers and workplaces into a standardized format that enables various users, such as healthcare professionals and health-related service providers, to use data for improving workers health and occupational safety. To allow easy access and improve interoperability, the platform is responsible for constructing the occupational data for health (ODH) data, which is used for comprehensively managing information in addition to the health records, such as occupational hazards, working environment, occupational history, and the health status of workers. ODH data types include employment status, job duties, occupational exposures, industry and occupation details, as well as working conditions. These data are used to provide a comprehensive view of the worker's occupational health and safety landscape. + +To generate ODH data for workers, the platform continuously monitors health status and working environments using Internet of things (IoT) devices and their context awareness capabilities. For instance, workers' health statuses are tracked through wearable devices, and working environments are monitored by sensors placed in the workplaces. This data is analysed in real time, facilitating + +decisions for medical support for workers, and determining of occupational hazards. Additionally, information about workers' employment status is collected from the company's human resources management system to enrich the ODH data. To facilitate information exchange among healthcare providers, public health experts, and occupational health professionals, the platform provides a standardized user interface while supporting security, privacy, and healthcare policies. + +## 6.2 Conceptual framework of the occupational health service platform + +Figure 1 shows the conceptual framework of the occupational health service platform. The platform is designed to focus on the collection and construction of ODH from diverse sources and to provide services to various data users. This framework integrates data collection, management, analysis, and service functionalities to support occupational health services. + +![Figure 1 – Conceptual framework of the occupational health service platform. The diagram shows three main components: ODH data sources, the Occupational health service platform, and ODH data consumers. The ODH data sources include IoT devices, Health records (EHRs, PHRs), Occupational data, and Social histories. These sources connect to the platform via various protocols: IoT protocols, Health IT standards (HL7, IHE, etc.), Enterprise specific protocols, and Proprietary protocols. The platform itself is divided into three vertical sections: Data source interface, a central column of functional blocks (Occupational health services/Application support, Data analysis and intelligence, Occupational data for health (ODH), Data management, Data collection), and a User interface. The platform connects to ODH data consumers (Healthcare organization/Professionals, Health-related service providers, Labour and safety policy makers, Insurance companies, Enterprise resource management system, and Other occupational health service platforms) via Health IT standards (HL7, IHE, etc.) and Enterprise specific protocols. A small label 'H.862.8(25)' is in the bottom right corner.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 1 – Conceptual framework of the occupational health service platform. The diagram shows three main components: ODH data sources, the Occupational health service platform, and ODH data consumers. The ODH data sources include IoT devices, Health records (EHRs, PHRs), Occupational data, and Social histories. These sources connect to the platform via various protocols: IoT protocols, Health IT standards (HL7, IHE, etc.), Enterprise specific protocols, and Proprietary protocols. The platform itself is divided into three vertical sections: Data source interface, a central column of functional blocks (Occupational health services/Application support, Data analysis and intelligence, Occupational data for health (ODH), Data management, Data collection), and a User interface. The platform connects to ODH data consumers (Healthcare organization/Professionals, Health-related service providers, Labour and safety policy makers, Insurance companies, Enterprise resource management system, and Other occupational health service platforms) via Health IT standards (HL7, IHE, etc.) and Enterprise specific protocols. A small label 'H.862.8(25)' is in the bottom right corner. + +**Figure 1 – Conceptual framework of the occupational health service platform** + +Data sources are categorized into the following subsets: + +- IoT devices including IoT sensors located in workplaces, health monitoring devices worn by workers, and health screening equipment; +- Health records that contain clinical data related to workers' diagnoses and treatments for diseases associated with occupational impacts; +- Enterprise systems which store information about workers' occupational status and workplace environment; and +- Social histories that provide information about workers' lifestyles and social status. + +From collecting data from data sources, the occupational health service platform uses data to construct and manage ODH. The platform also has some functionalities to support occupational health services and applications that use ODH for various services such as health program management, insurance support, alerts and reporting, and emergency supports. + +The users of the ODH and of the occupational health services provided by the platform include: + +- Healthcare organizations, which support medical care; +- Health-related service providers, supporting non-medical care; +- Labour and safety policymakers, who develop regulations and policies for workplace safety and worker health; +- Insurance companies, which use the data to assess workplace injuries and associated risks; + +- Enterprise resource management systems, which enhance and optimize working environments and workers' occupational status. + +Implementation details of the occupational health service platform are presented in Appendix I and use cases are presented in Appendix II. + +# **7 Requirements for the occupational health service platform** + +## **7.1 Occupational health data collection** + +To generate and manage ODH for workers and workplaces, the occupational health service platform collects data based on following requirements: + +- REQ-CO-01: The occupational health service platform is required to be able to collect occupation-related healthcare data of workers from healthcare organizations. +- REQ-CO-02: The occupational health service platform is required to collect health-related data of workers from IoT devices. + +NOTE 1 – IoT devices include wearable devices worn by workers and IoT devices located at workplaces to measure workers' health status. + +- REQ-CO-03: The occupational health service platform is required to collect occupational environment status data from IoT devices located in workplaces. + +NOTE 2 – IoT devices include sensors to measure physical, biological and chemical factors of workplaces. + +- REQ-CO-04: The occupational health service platform is required to collect occupational status data from an enterprise resource management system. + +NOTE 3 – Occupational status data includes working schedules, employment status, work classification, job histories of workers (e.g., current/past jobs, longest held occupation), etc. + +- REQ-CO-05: The occupational health service platform is recommended to be able to collect healthcare histories from health-related organizations. +- REQ-CO-06: The occupational health service platform is recommended to be able to collect regulations information from policy systems related to health and safety. +- REQ-CO-07: The occupational health service platform is recommended to be able to collect public health information of areas where the work site is located or may be affected. +- REQ-CO-08: The occupational health service platform can optionally collect social histories or lifestyle data of workers and can be used for workers health management. + +NOTE 4 – Lifestyle data includes information about smoking and alcohol use, sleeping hours, etc. + +- REQ-CO-09: The occupational health service platform can optionally collect information about unpaid work (e.g., work on a family farm) and some volunteer positions, especially those that are most likely to pose health risks. + +## **7.2 Data classification** + +To construct ODH and provide a statistics service from collected data, the occupational health service platform classifies data based on following requirements: + +- REQ-CL-01: The occupational health service platform is required to classify data according to identification of individuals. +- REQ-CL-02: The occupational health service platform is required to classify data according to workplace information including location and division. + +NOTE 1 – For example, the occupational health service platform classifies data per building to analyse mass immunization. In another example the occupational health service platform defines occupational hazards based on divisions of unique and specific job characteristics. + +- REQ-CL-03: The occupational health service platform is recommended to classify data according to personal status including age and gender. + +NOTE 2 – The concentration of women workers in particular occupations may lead to a specific pattern of injury and disease. + +- REQ-CL-04: The occupational health service platform is recommended to classify data according to workers that have special occupation histories. + +NOTE 3 – Examples of special occupation histories include combat zone experience, working at nuclear power plants, etc. + +- REQ-CL-05: The occupational health service platform is recommended to classify data according to special disease groups. + +NOTE 4 – The international classification of diseases (ICD) or equivalent disease classification systems are used to classify diseases. + +- REQ-CL-06: The occupational health service platform can optionally classify data based on marital status, race, ethnic group, military status or religion. + +## 7.3 Data storage management + +To manage data storage, the occupational health service platform has requirements to provide the following functionalities: + +- REQ-ST-01: The occupational health service platform is required to provide a storage system to store and retrieve data. +- REQ-ST-02: The occupational health service platform is recommended to define and process data retention policies specifying the lifetime of data depending on their data types. +- REQ-ST-03: The occupational health service platform is recommended to have functions to establish and to process metadata queries and responses. +- REQ-ST-04: The occupational health service platform is recommended to have separated backup storage to prevent data loss caused by failures of the main storage. +- REQ-ST-05: The occupational health service platform is recommended to implement auditing mechanisms and activity logs to track data access, sharing, and modifications. +- REQ-ST-06: The occupational health service platform can optionally determine whether data is to extend its lifetime or be deleted when the lifetime is expired. + +## 7.4 Data integration and interoperability + +To integrate data to ensure the interoperability of collected data, the occupational health service platform has the following requirements: + +- REQ-INT-01: The occupational health service platform is recommended to generate and transmit collected data into HL7 FHIR [HL7 FHIR]. +- REQ-INT-02: The occupational health service platform is recommended to support capabilities of reporting worker's health status as electronic documents. + +NOTE 1 – HL7 CDA [b-HL7 CDA] can be used to generate exchangeable electronic documents. + +- REQ-INT-03: The occupational health service platform is recommended to provide service interfaces to health devices that are implemented based on Continua Design Guidelines (CDG) [ITU-T H.81x]. +- REQ-INT-04: The occupational health service platform is recommended to provide interfaces with public health organizations to exchange occupational health information. + +NOTE 2 – Occupational health information includes disease information, occupational safety regulations, public health advisories, and epidemiological data. + +- REQ-INT-05: The occupational health service platform can optionally offer data normalization and validation processes for IoT-generated health data, ensuring consistency and quality. +- REQ-INT-06: The occupational health service platform can optionally apply advanced analytics technologies from the collected health data to support occupational health policy decision-making. +- REQ-INT-07: The occupational health service platform can optionally support data exchange between other occupational health service platforms to provide consistent tracing of workers' health status. +- REQ-INT-08: The occupational health service platform can optionally generate as international patient summary (IPS) [b-ISO 27269] or international patient access IPA [b-HL7 IPA] to exchange workers' health summaries. + +## 7.5 Networking + +The occupational health service platform has the following requirements to exchange data between data sources and users: + +- REQ-NET-01: The occupational health service platform is required to support multiple network connections for numerous category sensors, health devices and users, such as a cellular networks and non-cellular networks. Non-cellular networks include wired networks and wireless local area networks (WLANs) [IEEE 802.11]. +- REQ-NET-02: The occupational health service platform is required to support IPv4 and IPv6 protocols. +- REQ-NET-03: The occupational health service platform is required to support at least one IoT messaging protocol to acquisition data between IoT devices. +- REQ-NET-04: The occupational health service platform is recommended to use TLS/SSL [IETF RFC 8446] for data encryption and Wi-Fi protected access 3 (WPA3) for wireless security. + +## 7.6 Privacy and security support + +To support privacy and security, the occupational health service platform has the following requirements: + +- REQ-PS-01: The occupational health service platform is required to provide authentication and access control based on purpose and role for users. +- REQ-PS-02: The occupational health service platform is required to reject requests from users who do not have authority to access data. +- REQ-PS-03: The occupational health service platform is required to establish data retention policies and procedures to comply with privacy regulations and protect personal health information. +- REQ-PS-04: The occupational health service platform is recommended to provide authority for adding, modifying and deleting data by different users' access to the platform. +- REQ-PS-05: The occupational health service platform is recommended to provide informed consent for the use of their health data from workers, specifying the purpose and duration of data usage. +- REQ-PS-06: The occupational health service platform is recommended to maintain time synchronization to ensure that access permissions are granted or revoked based on specified time constraints. + +# Appendix I + +## Implementation details of the occupational health service platform + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Overview + +This appendix describes the implementation details of the occupational health service platform. + +### I.2 Data sources of the occupational health service platform + +The occupational health service platform collects multiple types of data from various sources, as presented below: + +- a) Healthcare data of workers: Obtained from healthcare organizations having electronic health record (EHR) and electronic medical record (EMR) systems compliant with [b-ISO 10781]. This includes clinical data such as diagnoses, prescriptions, diagnostic images, laboratory/pathology results and administrative information: + - i) Diagnoses data: Information on current and past diagnoses during occupation. + - ii) Prescriptions data: Details on medications prescribed to workers, including dosage and duration. + - iii) Diagnostic images: Imaging data such as X-rays, magnetic resonance imaging (MRI), or CT scans, which are generated for workers' injuries and treatments. + - iv) Laboratory/pathology results: Medical reports generated after analysing samples taken from a workers' body such as blood, tissue, organ, urine, or other bodily fluids. + - v) Other administrative data: Including medical visit summaries, treatment notes, appointment dates and billing details. +- b) Health-related data of workers: Generated from wearable devices, health monitors, or worksite questionnaires. This data encompasses biometrics, physical activities, and body measurements collected in real-time or periodically, depending on the device capabilities: + - i) Biometrics data: Blood pressure, heart rate, body temperature and blood oxygen saturation level. + - ii) Activity data: Activity type, moving distance and calorie consumption. + - iii) Physical body measurement data: Height, weight and body mass index (BMI). +- c) Occupational environment data: Collected from IoT sensors and enterprise resource management systems to monitor workplace conditions. It includes information on environmental hazards, machinery operation, and potential exposure risks, collected for hazard identification and emergency detection: + - i) Construction materials: Information on chemical and metal materials present in the workplace. It includes asbestos levels in insulation, silica dust in manufacturing areas, lead levels in paint, and solvents or other chemicals used in production processes. + - ii) Machinery: Type of machines, hours of operation and noise levels of machinery. + - iii) Potential hazard factors: Includes environmental data such as particulate matter levels, CO2 levels, noise levels in decibels, temperature and humidity. +- d) Occupational status data: Provided by enterprise systems, covering job-related information such as activities, schedules, and employer details: + - i) Job activities: Specific tasks such as heavy lifting, operating heavy machinery, repetitive tasks and handling chemical or biohazard materials. + - ii) Schedules: Working hours, shift patterns, overtime records and break times. + +- iii) Employer details: Employing organization including company name, location, department and supervisor's name. +- e) Workers' status data: Self-reported by workers or gathered through questionnaires, covering lifestyle and social information, including education, lifestyle habits, and social support indicators. + - i) Education: Level of education completed. + - ii) Relationships: Family and social connections such as marital status, number of dependents and social support. + - iii) Veteran status. + - iv) Smoking/alcohol uses. + - v) Sleeping hours and patterns. + - vi) Food insecurities. +- f) Regulations and public health data: Collected from governmental or health-related organizations, including occupational safety regulations, public health advisories, and epidemiological data. + - i) Laws: Regional or country laws such as Occupational Safety and Health Administration (OSHA) regulations on exposure limits, personal protective equipment (PPE) requirements and permissible noise levels. + - ii) Public health advisories: Notices related to emerging health risks, such as COVID-19 advisories for workplace safety, alerts about local flu outbreaks or heat advisories during summer months. + - iii) Disease and epidemiological research findings: Includes data on disease prevalence, occupational health studies on conditions like carpal tunnel syndrome, and research on exposure to hazardous substances. + +### **I.3 Users of the occupational health service platform** + +Users who are using ODH, and applications that are provided by the occupational health service platform, are listed below: + +- Healthcare organizations/professionals: Utilize ODH to improve occupational health outcomes and provide data-driven care. +- Health-related service providers: Use data for non-medical health services, including rehabilitation and mental health support. +- Labour & Safety policy makers: Leverage data to enhance workplace safety regulations and create evidence-based policies. +- Insurance companies: Access data to process claims related to workplace injuries and assess associated risks. +- Enterprise resource management systems: Integrate data to monitor employee health, manage absences, and ensure compliance with health and safety standards. +- Other occupational health service platforms: Share anonymized data and insights across different platforms to enhance occupational health initiatives. + +### **I.4 Functions of the occupational health service platform** + +#### **I.4.1 Data collection** + +Data collection is responsible for gathering diverse data from various sources to construct ODH. This functionality ensures that all relevant health data and environmental data are captured, providing the raw information needed for further processing and analysis: + +- a) Data source interface supports: The platform provides various interfaces to facilitate seamless data collection from different sources: + - i) IoT interfaces for health devices: For health data exchange between the platform and health devices, the service interface implemented based on CDG and HL7 FHIR implementation guidelines (IG) for personal health devices (PHDs) is used. For more general communication with IoT devices or gateways, the platform supports at least one of the IoT protocols such as Open Connectivity Foundation (OCF), oneM2M or Matter. + - ii) IoT interfaces for workplace sensors: The platform supports multiple network connections for numerous kinds of sensors in workplaces, such as wired network via Ethernet, and wireless network via WLAN [IEEE 802.11]. + - iii) Interfaces for healthcare organizations: Health records from medical databases and electronic health records (EHR) systems can be downloaded into the platform using HL7 FHIR. Additionally, the platform additionally implements healthcare standardized interfaces such as, Integrating the Healthcare Enterprise (IHE) and Continua with secure data transfer. + +#### **I.4.2 Data management** + +The data management function is crucial for securely storing, organizing, and managing the collected data. It ensures that data from various sources is integrated, classified, and readily accessible for further analysis and processing for constructing comprehensive ODH. The data management function supports the following capabilities as minimum: + +- a) Data storage: The platform stores aggregated data from multiple sources in a centralized database, ensuring data integrity and availability. For storage management, the platform implements structured query language (SQL)-based relational database solutions to store, update, remove, search, and retrieve information. +- b) Data classification: The platform classifies integrated data into relevant categories for further processing such as data analysis or ODH construction. Collected data is categorized into the following features: + - i) Individuals: The platform classifies data depending on the person to whom the data is related. It is necessary to construct ODH for each employee in this platform. For classifying individuals, the platform is required to use a unique identification such as employee ID. + - ii) Workplace: To analyse occupational hazards, the platform categorizes environment data according to workplace. For example, data can be classified by geographical information, building/floor/room number or team. + - iii) Groups: For occupational health surveillance or research purposes, the platform classifies data into specific groups. The platform can classify health related parameters of specific gender or age. Also, based on job histories of employees, the platform can classify the data of employees who had special jobs such as working at nuclear power plants, chemical factories or in combat zones. + - iv) Socials: The platform can optionally use social histories of workers for analysing health impacts by providing a broader context for understanding health risks. Examples include special disease groups during a pandemic, marital status, race, ethnic groups or religions. + - v) Other parameters can be used for categorizing data depending on different purposes. + +#### **I.4.3 ODH construction and management** + +The ODH construction and management function is responsible for transforming integrated data into ODH that is compatible for the exchange of data across various users. To do this, the function ensures that data is standardized, enriched and structured to provide representation of workers' health and + +occupational status. The ODH construction and management function supports the following capabilities as minimum: + +- Data integration to ODH: The platform uses HL7 FHIR implementation guidelines (IG) for ODH [b-FHIR-ODH] with additional enhancements of supporting data parameters, that cover the information work type and status to be used for clinical decision support, population health activities, value-based care and public health reporting. +- ODH data management: The platform implements a mechanism for management data within the ODH to ensure that the dataset remains current and relevant. This mechanism includes the policy management of updating and deleting data, tracking of data changes, version control, and supporting data integrity. + +#### **I.4.4 Data analysis and intelligence** + +The data analysis and intelligence functions are used for analysing the structured ODH data to generate actionable insights. Analytics, machine learning, and other intelligence techniques can be used for implementing this function to detect risks, assess impacts, and provide a comprehensive understanding of workplace health and safety. The data analysis and intelligence function supports the following capabilities as minimum: + +- Occupational risk and hazard detection: The platform utilizes a data analytic service to detect patterns and anomalies that may indicate health risks or unsafe conditions in workplaces. +- Assessment and cause analysis: The platform evaluates the impact of health incidents and identifies their underlying causes, which involves analysing trends, correlations and root causes of health issues. Results can provide insights to help decision-making and preventive actions. +- Logging and audit trailing: By implementing logging audit trails to track changes, access and usage of the data, the platform ensures transparency and accountability. Also, this capability supports compliance with regulations and internal policies. +- Visualization and reporting: This capability supports to create visualizations to represent data insights in an easily understandable format. This includes charts, graphs, dashboards, and other visual tools. +- AI integration: This capability utilizes artificial intelligence (AI) to enhance data analysis capabilities to provide predictions of occupational health risks. + +#### **I.4.5 Applications and services** + +The occupational health service platform provides various health programs and services that improve workplace health and safety, support employees, and streamline processes related to occupational health management. These applications and services are consumed by users of the platform. This function supports the following capabilities as minimum: + +- a) Occupational health program management: Applications used to create, schedule and monitor various occupational health programs such as, preventive health screenings, vaccination drives, wellness initiatives and chronic disease management. To manage health programs, the following technical methods can be implemented in the platform: + - i) Program templates: Pre-defined templates that can be customized to fit for the purposes of each program. + - ii) Scheduling tools: Tools to schedule health program activities, such as screenings, vaccinations, and follow-up appointments. It can be integrated with organizational calendars to ensure that these activities are coordinated with work schedules. + - iii) Tracking and monitoring: Systems can be implemented to track employee participation in health programs, including sign-ups, attendance, and engagement levels. Also, the + +system can involve monitoring tools for tracking changes in health metrics, employee feedback, and overall program effectiveness. + +- iv) Documentation: It supports making documents to maintain and report health program activities, participation, and outcomes. This documentation can be utilized to support compliance with health and safety regulations. +- b) Insurance support: This application supports submission and processing of insurance claims related to workplace injuries and illnesses. It manages access to necessary ODH data for insurance assessments, ensuring accurate and timely claim verification. +- c) Alerts and reporting: This application generates alerts for events from other functions in the platform and sends alerts to relevant stakeholders. Reporting provides details on health status, program outcomes, and incident analysis. +- d) Emergency support: This application offers resources and support during emergency situations, such as workplace accidents. When an emergency is detected and reported to the platform, it provides real-time updates and data exchanges to all relevant organizations and coordinates emergency response efforts, including medical assistance, evacuation plans, and communication with emergency services. + +#### I.4.6 Security and privacy + +In the occupational health service platform, security and privacy are essential functions for protecting sensitive health and environmental data. This function ensures that data privacy is maintained, access is controlled, and all data handling processes comply with relevant regulations and standards. For security and privacy, the occupational health service platform supports at least the following capabilities: + +- Access control: The platform implements access control methods to ensure that authorized users can access data. To do this, role-based access control (RBAC) is used to provide different access policies depending on users. In specific cases of healthcare information exchanges between the platform and health professionals, the platform provides information security methodologies defined in [b-ISO 27799]. Further information security control can be implemented by following guidelines defined in [b-ISO 27002]. +- Authentication: Multi-factor authentication (MFA) is used to add an extra layer of security, ensuring that access to sensitive data requires multiple forms of verification (e.g., password, biometric verification, and security tokens). +- Permission and consent management: Data stored in the platform is generated by workers' IoT devices, environmental sensors owned by the company, or medical records managed by healthcare providers. To share and use this information, the platform provides a mechanism to clearly define the owner of data and to grant permission for this data from consents. +- Data encryption: For transmitting data securely between data sources, data users and the platform, the platform uses HTTP over TLS [b-IETF RFC 2818] as a secure communication protocol. Also, the platform uses AES to prevent sensitive data stored in the database and storage system. +- Data anonymization and de-identification: In the case of data use for research purposes, the platform implements the pseudonymization process defined in [b-ISO 25237] to protect personal health information. Also, the platform implements de-identification of data with the following guidelines defined in [b-ITU-T X.1771]. + +# Appendix II + +## Use cases of the occupational health service platform + +(This appendix does not form an integral part of this Recommendation.) + +### II.1 Use case for occupational health surveillance with occupational hazard analysis + +Occupational health surveillance aims to detect, predict and eliminate occupational hazards such as chemical, physical, or psychological threats in the workplace that enable workers' health to be protected. One example is a workplace where workers handle chemical materials that possibly cause disease. Workers in such a workplace are suggested to have health devices for measuring health status that is determined as premonitory symptoms of disease, and employers are suggested to provide periodical medical tests for workers. During the occupational health program including testing and examinations, employers can use the information of participants to re-schedule workloads in order to minimize impacts for degradation of occupation performance. + +To support this use case, features of the occupational health service platform are listed below: + +- Collecting and integrating data from IoT devices and health records. +- Data analysis for hazard detection and health risks. +- Alerts and reporting to workers, healthcare professionals, and employers. +- Consent and access control for data collection and usage. +- Supports for creation and monitoring of occupational health programs, including tools for re-scheduling workloads and for implementing preventive measures. +- Feedback and tracking for continuous improvement. + +Figure II.1 describes the operational procedure for occupational health surveillance with occupational hazard analysis. + +![Figure II.1 – Operational procedure for occupational health surveillance with occupational hazard analysis. The diagram shows the flow of data from various sources through an Occupational health service platform to different stakeholders.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +The diagram illustrates the operational procedure for occupational health surveillance. It features a central **Occupational health service platform** with several internal components and external interactions. + +**Internal Platform Components:** + +- Occupational health services/Application support:** Includes Health program management (6), Alert and reporting (4), and Security and privacy control (1). +- Data analysis and intelligence:** Processes data from the Occupational data for health (ODH) section. +- Occupational data for health (ODH):** A grid containing Health-related monitoring data, Work status data, Social histories, Job histories, Health records, Workplace data, Occupational hazard data, and more (...). +- Data management:** Handles data collection (2) and feeds into the ODH section. +- Data source interface:** Receives input from external sources. +- User interface:** Provides output to external stakeholders. + +**External Interactions:** + +- Worker:** + - 1. Device and consent registration (input to platform). + - 2. Worker's health device sends health status (input to platform). + - 5. Worker visits healthcare professional for evaluations, tests, and treatments (output from platform). +- Health equipment in workplaces / Sensors in workplace:** + - 2. Send workers health status / Send workplace status (input to platform). +- Healthcare providers:** + - 4. Health and incident information (output from platform). + - 5. Update health records with diagnosis, treatment (input from platform). +- Employer:** + - 6. Report result (output from platform). + - 6. Feedback and update surveillance (input from platform). + +The diagram is labeled H.862.8(25) in the bottom right corner. + +Figure II.1 – Operational procedure for occupational health surveillance with occupational hazard analysis. The diagram shows the flow of data from various sources through an Occupational health service platform to different stakeholders. + +**Figure II.1 – Operational procedure for occupational health surveillance with occupational hazard analysis** + +- 1) Device registration: Workers wear IoT health monitoring devices and register to the platform. During registration, workers consent for data collection and usage by the occupational health service platform. +- 2) Data collection and aggregation: Data collected from IoT devices that are worn on the workers' bodies or located in workplaces are transmitted to the occupational health service platform. Data can be collected periodically or depending on pre-defined events. Once data is received, the platform aggregates and classifies data and then stores it in the database. +- 3) Data analysis and risk detection: The platform can provide algorithms to analyse the aggregated data to detect health risks and workplace hazards. +- 4) Alerts to healthcare providers: When health risks are identified and occupational hazards are detected, the platform generate alerts to the healthcare providers. Healthcare providers can receive alerts with ODH including potential health issues and reported incidents +- 5) Related actions from healthcare providers: If needed, workers visit healthcare providers for evaluations and treatments. Results including medical evaluations and treatments are sent to the platform and the ODH is updated with health records, test results, and treatment plans. +- 6) Reporting actions / continuous monitoring: The platform notifies to employer (or EMS) for occupational health surveillance actions. Based on reports, employers can adjust work conditions and workloads. Also, employers give feedbacks to the platform for tracking corresponding issues and health risks. + +### **II.2 Use case for occupational injury and illness management** + +Occupational injury and illness management aims to detect events when a worker is injured or falls ill in the workplace, identify the injury or illness, connect patient workers to healthcare professionals, and report the case to the occupational management system and insurance organization. Based on the report of the worker who is injured, it is required to collect the status of the worker's health, case of injury, and factors that caused the injury. All collected data is required to be documented for case reports used for the occupation management system, as well as for medical reports that will be used by hospitals. Based on the reports, employers can initiate patient registration for injured workers to receive medical care. Additionally, it is suggested to claim insurance for injured workers and workload improvements by the occupation management system. The occupational injury and illness management process includes the following features: + +- Incident reporting from workers and logging of all reported incidents for tracking and analysis. +- Assessment of the impact of injuries using data from IoT devices. +- Analyse environmental and situational data to determine the cause of incidents before medical treatment. +- Generate alerts for healthcare providers, employers, and insurance companies when incidents are reported. +- Support the creation and monitoring of health and recovery programs. +- Provide access to incident and health data for the insurance company for verification and claims assessment. + +Figure II.2 shows the operational procedure for occupational injury and illness management. + +![Diagram of the Operational procedure for occupational injury and illness management. The central 'Occupational health service platform' is shown with layers: Occupational health services/Application support (Health program management, Insurance support, Alert and reporting, Emergencies support), Data analysis and intelligence, Occupational data for health (ODH) (Health-related monitoring data, Work status data, Social histories, Job histories, Health records, Workplace data, Occupational hazard data, ...), Data management, and Data collection. Data flows from Worker (Report injuries, Send workers health status), Worker's health device (Send workers health status), and Sensors in workplace (Send workplace status) through the Data source interface. The platform interacts with Healthcare providers (Report incident and symptoms, Update health records), Insurance company (Access incident and health data), and Employer (Report injuries, Feedbacks) through the User interface. A 'Visit doctor' step is shown at the top right.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +The diagram illustrates the operational procedure for occupational injury and illness management. At the center is the **Occupational health service platform**, which is structured into several layers: + +- Occupational health services/Application support**: Includes Health program management, Insurance support, Alert and reporting, and Emergencies support. +- Data analysis and intelligence**. +- Occupational data for health (ODH)**: Includes Health-related monitoring data, Work status data, Social histories, Job histories, Health records, Workplace data, Occupational hazard data, and more. +- Data management**. +- Data collection**. + +The platform interacts with three main external entities through interfaces: + +- Data source interface**: Receives data from a **Worker** (who can **Report injuries** via an **Equipped device** and **Send workers health status** via a **Worker's health device**) and **Sensors in workplace** (which **Send workplace status**). +- User interface**: Interacts with **Healthcare providers** (who receive **Report incident and symptoms** and **Update health records with diagnosis, treatment**), an **Insurance company** (which **Access incident and health data**), and the **Employer** (who receive **Report injuries** and **Feedbacks**). + +A **Visit doctor** step is indicated at the top right, showing a flow from the platform to the healthcare providers. The diagram is labeled H.862.8(25). + +Diagram of the Operational procedure for occupational injury and illness management. The central 'Occupational health service platform' is shown with layers: Occupational health services/Application support (Health program management, Insurance support, Alert and reporting, Emergencies support), Data analysis and intelligence, Occupational data for health (ODH) (Health-related monitoring data, Work status data, Social histories, Job histories, Health records, Workplace data, Occupational hazard data, ...), Data management, and Data collection. Data flows from Worker (Report injuries, Send workers health status), Worker's health device (Send workers health status), and Sensors in workplace (Send workplace status) through the Data source interface. The platform interacts with Healthcare providers (Report incident and symptoms, Update health records), Insurance company (Access incident and health data), and Employer (Report injuries, Feedbacks) through the User interface. A 'Visit doctor' step is shown at the top right. + +**Figure II.2 – Operational procedure for occupational injury and illness management** + +- 1) Injury report: Worker reports incidents or symptoms to the platform. +- 2) Assessment of impact: When a report is received, the platform begins tracking the case and collecting data from IoT devices and workplace sensors to assess the impact of the injury. Based on collected information, the platform analyses environmental and situational data to determine the cause of the incident before medical treatment. +- 3) Incident alerts: The platform generates alerts for the incident and sends it to designated healthcare providers including ODH with updated incident and symptoms. In emergency cases, the platform provides biometric information such as vital signs, blood pressure collected from the worker's wearable device, to paramedics. At the same time, the platform sends an alert to employer for notification and workload scheduling. +- 4) Medical care of injured worker: Healthcare professionals conduct medical evaluations and prescribe necessary treatments. ODH sent from the platform can be used for medical evaluations and clinical decisions. Workers visit healthcare providers for initial evaluations and treatments. +- 5) Update health status of workers: After medical care, healthcare providers update ODH to the platform with treatment plans, test results, and recommendations. Based on that, the platform tracks the recovery progress with regular updates from healthcare providers. Additionally, the platform can provide data to the therapists for a recovery program. +- 6) Insurance claim: After medical treatments, insurance companies access incident and health data for processing claims. The platform manages access control for insurance companies and provides required data for insurance claims. + +### II.3 Use case for mass immunization + +Mass immunization aims to deliver vaccines to a large number of people at one or more locations in a short interval of time. For occupational health and safety, employers can undertake mass immunization programs to maximize the health of employees. One example is the launching of a COVID-19 vaccination program in the workplace, which tracks the distribution of virus, suggests related workers to immunize by connecting to hospitals where they are available to provide vaccines, and provides an occupation policy to workers such as quarantine or work schedule modification. In extreme cases of large distribution of disease in a workplace, it is suggested to operate point of distribution (PoD) with the stronger restrictions. Mass immunization includes the following features: + +- Schedule immunization sessions and manage appointments. +- Track participation and compliance with immunization programs. +- Continuously monitor health data before and after immunization. +- Implement strict access controls to protect immunization records and health data. +- Provide anonymized data for government monitoring and policy making. +- Facilitate communication between workers, healthcare providers, employers, and government organizations. + +Figure II.3 shows the operational procedure for mass immunization. + +![Diagram of the operational procedure for mass immunization. The central component is the 'Occupational health service platform', which is divided into several layers: 'Occupational health services/Application support' (containing Health program management, Insurance support, Alert and reporting), 'Data analysis and intelligence', 'Occupational data for health (ODH)' (containing Health-related monitoring data, Work status data, Social histories, Job histories, Health records, Workplace data, Occupational hazard data, and more), 'Data management', and 'Data collection'. The platform has a 'Data source interface' on the left and a 'User interface' on the right. On the left, 'Workers' (represented by icons) use an 'Equipped device' (a smartwatch) to 'Monitor health status' (step 4), which feeds into the platform. On the right, the platform interacts with 'Healthcare providers' (step 2: Schedule immunization sessions; step 3: Report immunization result; step 4: Report adverse reactions), 'Government organization' (step 1: Issues guidelines for mass immunization; step 5: Report immunization summaries), and 'Employer' (step 2: Workload scheduling adjustment; step 5: Report immunization summaries). A large curved arrow at the top shows step 3: 'Administer vaccines to workers' from the Healthcare providers back to the Workers. A small text 'H.862.8(25)' is in the bottom right corner.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +Diagram of the operational procedure for mass immunization. The central component is the 'Occupational health service platform', which is divided into several layers: 'Occupational health services/Application support' (containing Health program management, Insurance support, Alert and reporting), 'Data analysis and intelligence', 'Occupational data for health (ODH)' (containing Health-related monitoring data, Work status data, Social histories, Job histories, Health records, Workplace data, Occupational hazard data, and more), 'Data management', and 'Data collection'. The platform has a 'Data source interface' on the left and a 'User interface' on the right. On the left, 'Workers' (represented by icons) use an 'Equipped device' (a smartwatch) to 'Monitor health status' (step 4), which feeds into the platform. On the right, the platform interacts with 'Healthcare providers' (step 2: Schedule immunization sessions; step 3: Report immunization result; step 4: Report adverse reactions), 'Government organization' (step 1: Issues guidelines for mass immunization; step 5: Report immunization summaries), and 'Employer' (step 2: Workload scheduling adjustment; step 5: Report immunization summaries). A large curved arrow at the top shows step 3: 'Administer vaccines to workers' from the Healthcare providers back to the Workers. A small text 'H.862.8(25)' is in the bottom right corner. + +**Figure II.3 – Operational procedure for mass immunization** + +- 1) Initialization of mass immunization: Based on requests from health organizations and local policy, the government issues guidelines and requests enterprises to plan mass immunization in response to public health concerns. +- 2) Planning immunization program: The platform schedules immunization sessions and makes appointments with healthcare professionals. Also, the platform communicates with the employer for workload adjustment during the immunization period. +- 3) Operating immunization program: Based on scheduling, healthcare providers administer vaccines to workers. During the program, initial health assessments before immunization and monitoring for immediate reactions post-vaccination are performed. After vaccination, healthcare providers update ODH of workers to the platform with changed health records. +- 4) Monitoring post-immunization health status: To monitor post-immunization symptoms and adverse reactions, IoT devices monitor workers' health data and send it to the platform. The platform tracks important biometric parameters such as vital signs, and analyses to detect potential side effects or adverse reactions. If needed due to adverse reaction, the platform transmits alerts to healthcare providers for treatments. + +- 5) Report summaries of immunization: When the immunization program is concluded, the platform aggregates immunization records and health data and make summaries for immunization. Then the platform makes reports of summaries and sends it to the government and ensures compliance with guidelines. Additionally, the platform reports summaries to the employer and uses feedback to update monitoring policy for continuous tracking. + +## Bibliography + +- [b-ITU-T H.810] Recommendation ITU-T H.810 (2019), *Interoperability design guidelines for personal connected health systems: Introduction*. +- [b-ITU-T X.1771] Recommendation ITU-T X.1771 (2024), *Security guidelines for combining de-identified data using trusted third party*. +- [b-FHIR-ODH] HL7 (2022), *HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1, STU 1.3 (Standard for Trial Use)*. + +- [b-HL7 CDA] HL7 (2005), *Reaffirmation of HL7 V3 Standard: Clinical Document Architecture, Release 2*. +- [b-HL7 IPA] HL7 (2023), *International Patient Access (IPA) Implementation Guide*. +- [b-IETF RFC 2818] IETF RFC 2818 (2000), *HTTP over TLS*. +- [b-ISO 10781] ISO 10781 (2023), *Health informatics – HL7 Electronic Health Record-System Functional Model, Release 2.1 (EHR FM)*. +- [b-ISO 22886] ISO 22886 (2020), *Healthcare organization management – Vocabulary*. +- [b-ISO 25237] ISO 25237 (2017), *Health informatics – Pseudonymization*. +- [b-ISO 27002] ISO 27002 (2022), *Information security, cybersecurity and privacy protection – Information security controls*. +- [b-ISO 27269] ISO 27269 (2021), *Health informatics – International patient summary*. +- [b-ISO 27799] ISO 27799 (2016), *Health informatics – Information security management in health using ISO/IEC 27002*. +- [b-ISO 41014] ISO 41014 (2020), *Facility management – Development of a facility management strategy*. +- [b-WHO] WHO, *Occupational health*. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d7af7436bab49367684ee510133c0d095d44aad --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b00e3927b73ca3c945a17e81fe5d165062ab5de39526cf696166f5345076b4a1 +size 32821 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/103781b498cc6846ffc11a041e14dc3e_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/103781b498cc6846ffc11a041e14dc3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..593fdb84de82fdbf34766f510b820fa6267c3124 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/103781b498cc6846ffc11a041e14dc3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1208826584f32032da520a76e19b9bab86453e5a990a7a757767e7316f2ef621 +size 42763 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c395c4bbde83b1e232652a43f51538278c116f51f710c37e20a073f7333726c8 +size 6134 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5616ec579ec80f5dc8db9833b55e860c52cfc0a9 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af41619f948fa77ea457f01286b3d8d5a3fc3d97e501be50e3b4675c0f1a5312 +size 168474 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/30ffebf544a71997b61e5f4be3d321ef_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/30ffebf544a71997b61e5f4be3d321ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..784bb6b2c9a377a801f1d8a116b5bc1728ac2896 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/30ffebf544a71997b61e5f4be3d321ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:496bc21f7611f58840c2dbf023e78774797899754734492b92f4f19dc79225bb +size 19136 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/35135a8841884b7bb6fa58c3d9665c13_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/35135a8841884b7bb6fa58c3d9665c13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a272ef20c967a6a3612eec5bf12558dfd904c5ea --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/35135a8841884b7bb6fa58c3d9665c13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e87901906225eeda12273a185e0814e84eff26854e8fbe94728f9095412de7c1 +size 28692 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/37290987e9d8f148b8a59c405e9c60d7_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/37290987e9d8f148b8a59c405e9c60d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e18607524bff65d2587274eb72dc8beb57418ec --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/37290987e9d8f148b8a59c405e9c60d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f650588b62c648b4c5869c85b317301c8d75e6a34e7286de079c360f36c79f39 +size 92707 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/56a7fc5964ed9463fa47ca8a60568dec_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/56a7fc5964ed9463fa47ca8a60568dec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4176a5cfa010082fe7867f4786ced15813c5b7a --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/56a7fc5964ed9463fa47ca8a60568dec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2555409eace7bc5e89c479853e6e52622d45eeef09115b3f53c83196f9f80b65 +size 42348 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdac3bb8941759724c8d8722456053053efd0d87 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4f6012ecbbafb93856d43dd97a1e3421bd468902a685aa3e741b5294c9f7e15 +size 73781 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/62039fd2a1ef7b03f84c0fe5d8911860_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/62039fd2a1ef7b03f84c0fe5d8911860_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4382e16a307a9a63f52bbdc77aabaf801470eb26 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/62039fd2a1ef7b03f84c0fe5d8911860_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddc30bdabaa2a43831f8af717ebbc235ed3183742c10acf07e55913f7870cd59 +size 16673 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..899aa3a7ed6f65ba83bb10846eed4ea22588894f --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a7b869d6cfafdaa3600a58bb949d41089e2824e1fcdbbd0165306e8d3d410cf +size 27699 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/7b517f15a2d307945bd78e30c13a75bd_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/7b517f15a2d307945bd78e30c13a75bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5878d648b9afe2b1567c2cd9f19bae1945adb17 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/7b517f15a2d307945bd78e30c13a75bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d8c4a133d439e49e0c0a6d3837132bec62dbb6fe02a0505cd1e1c6656c99c25 +size 29882 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/8e1263a63a8c36c001a0c913d7e7fcce_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/8e1263a63a8c36c001a0c913d7e7fcce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99c4ca305ec231ea1a1692d9c3c4bceec1fe013d --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/8e1263a63a8c36c001a0c913d7e7fcce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:759a71351d74e6cf193fbfff653936fee7fa611b0a0eba1d5a1bcdb946d35488 +size 72049 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/93fa4105c1d3c48fee6b3fd97b631387_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/93fa4105c1d3c48fee6b3fd97b631387_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58120a545a12c41ce3b12986684ea9473c013fff --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/93fa4105c1d3c48fee6b3fd97b631387_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5be5a6805b61c16a4025813331d24ebb67bed626c019ad097358bbca843879bc +size 56112 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c05e4177d8325eef1627d8730f3257d2e4c4363c --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:716702fad7f071a75677ce0b780d4e5aa817ed577078e1572cdb66ab0621060c +size 106376 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/a8523d225a4e279ab9e02f3c28cfa36a_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/a8523d225a4e279ab9e02f3c28cfa36a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0825b267d8783b0d96267b833a6d8a8e17448d89 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/a8523d225a4e279ab9e02f3c28cfa36a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f471a6afb55f8f7ff85908c8eca0ac937422703da4da8f956ff4ca16da2931f +size 103026 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/c2462d2d2ea40cd436ba726b995d21f5_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/c2462d2d2ea40cd436ba726b995d21f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f4cdf898ffa4960d517ec506f7390e0e53aad23 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/c2462d2d2ea40cd436ba726b995d21f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c540eece36f9dc8f3623491a5217165723d48f39d4e5ad1402e7ce255c10140b +size 47431 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8973f1ee15c7a05460c37b07fb99f1c32df199d --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9844f4b33282abc4c682d46fe36f96d304f28ca43fea422b79b88f08c8ce1b46 +size 34661 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8abf33c8ff4b51ae83442e6506dde8328867453 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3c5e96faa3826e40fb2dc548ee844f58a520f3789274ae8a34a4b6bcdf964a9 +size 288168 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/ceb147a82430b08b7ffd0ea53313cc47_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/ceb147a82430b08b7ffd0ea53313cc47_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c75fb6f2434717b0c48d95faaf8e4e4876ac7ebd --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/ceb147a82430b08b7ffd0ea53313cc47_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ec7e0ebd31f5d80457ac14db8c55a5fbe5c4a29ee1866c47fa40e97691ac883 +size 85844 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/daff947a443eb2a4735e3a81b6f756d9_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/daff947a443eb2a4735e3a81b6f756d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef4d4ccac3378f8c818bea08ac43b492760e27b0 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/daff947a443eb2a4735e3a81b6f756d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd8bcc7c152472a9f00011cce11bb7c25f3f5f186fe9c16eab34883a7889a0c9 +size 60342 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/dbc1673750fd53d4203f4d93963fdab6_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/dbc1673750fd53d4203f4d93963fdab6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e240a97aa5f475f534581fb4024ea7c92325dfad --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/dbc1673750fd53d4203f4d93963fdab6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:098a963042ee18902a2c1474a1f731e7235690c8a3bd924b72022795ef4941a4 +size 43525 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/e046996962d6740cf050a5640e0c6b40_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/e046996962d6740cf050a5640e0c6b40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e5d25980416864ba54a2c38146ca7b16a33a526 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/e046996962d6740cf050a5640e0c6b40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b77ea7d00b71d9a0c7a5ee7614f6010e9b462a20c2007fd14fdb80c542e6b7f3 +size 25993 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eeacf6f52fe629fe6693deb2ad1fc392fe2f26a3 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bf595d7697a9ad816576c3107ecfc18c88679b14b5a9efc16843454b6e587cd +size 34086 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg b/marked/H/T-REC-H.870-202203-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..494d573d9faf27df1751eae59c8d12c4df8004c7 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a86161411ff961d8bb58ff89f3100dc5843b89f5a9fd98ea5700039647b5eb6 +size 26674 diff --git a/marked/H/T-REC-H.870-202203-I_PDF-E/raw.md b/marked/H/T-REC-H.870-202203-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6490bc10e0f54095658eef781af2fbd738d11cd0 --- /dev/null +++ b/marked/H/T-REC-H.870-202203-I_PDF-E/raw.md @@ -0,0 +1,1694 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.870** + +(03/2022) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Safe listening + +--- + +**Guidelines for safe listening devices/systems** + +Recommendation ITU-T H.870 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features the letters "ITU" in a bold, blue, sans-serif font, superimposed on a stylized globe icon with latitude and longitude lines. + +ITU logo + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Content delivery and ubiquitous sensor network applications | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.870 + +# Guidelines for safe listening devices/systems + +## Summary + +Recommendation ITU-T H.870 describes the requirements on safe listening devices and systems, called personal/portable audio systems, especially those for playing music, to protect people from hearing loss. It also gives a glossary for common understanding as well as background information on sound, hearing and hearing loss. + +It recommends the criteria for avoiding unsafe listening: one for adults and the other for children, both based on the equal energy principle, the assumption that equal amounts of sound energy will cause equal amounts of sound induced permanent threshold shift regardless of the distribution of the energy over time. + +Importantly, this Recommendation provides guidelines on health communication for safe listening so that appropriate warning messages can be delivered effectively when necessary. Examples of such messages can be found in Appendix VII. + +Finally, this Recommendation also gives information about the implementation of dosimetry and related issues. + +Communication devices and assistive devices are excluded from the scope of this Recommendation. Gaming devices are also for future study. + +This standard was developed collaboratively by the World Health Organization (WHO) and ITU under the 'Make Listening Safe' initiative, and it is adopted by both organizations. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.870 | 2018-08-29 | 16 | 11.1002/1000/13686 | +| 2.0 | ITU-T H.870 (V2) | 2022-03-16 | 16 | 11.1002/1000/14953 | + +## Keywords + +Dose, personal audio system, safe listening, sound pressure level, sound-induced hearing loss. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2022 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|-------------------------------------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 4 | +| 4 | Abbreviations and acronyms ..... | 6 | +| 5 | Conventions ..... | 7 | +| 6 | Safe listening: Introduction..... | 7 | +| 6.1 | Background..... | 8 | +| 6.2 | Personal audio system ..... | 8 | +| 7 | Damage risk criteria..... | 10 | +| 7.1 | Operational modes..... | 10 | +| 7.2 | Uncertainty in dose estimate ..... | 12 | +| 8 | Measurement methods ..... | 12 | +| 8.1 | Dosimetry ..... | 12 | +| 9 | Sensitivity range and frequency response of headphones ..... | 13 | +| 10 | Profiles..... | 14 | +| 11 | Health communication..... | 14 | +| 11.1 | Purpose of including health communication as part of the standards for safe listening personal audio systems..... | 14 | +| 11.2 | Key recommendations for communication as part of standards for safe listening devices ..... | 15 | +| 12 | Ambient noise control..... | 19 | +| 12.1 | Passive attenuation of the background noise..... | 19 | +| 12.2 | Active noise reduction of background noise ..... | 20 | +| 12.3 | Benefits of noise-isolating earphones..... | 20 | +| 12.4 | Safety concerns associated with noise-isolating earphones ..... | 20 | +| 13 | Volume control ..... | 20 | +| 13.1 | Volume limiting..... | 20 | +| 13.2 | Password-protected volume control ..... | 21 | +| 14 | Guidance on ancillary concerns..... | 21 | +| | Appendix I – Status report ..... | 22 | +| | Appendix II – Dose estimation functionality for implementation in a personal audio system ..... | 23 | +| II.1 | Introduction ..... | 23 | +| II.2 | Main related standards..... | 23 | +| II.3 | Definition of dose in the context of acoustic dosimetry..... | 23 | + +| | Page | | +|-------------------|--------------------------------------------------------------------------------------------------|----| +| II.4 | Weighting of different frequencies..... | 23 | +| II.5 | Signal capture point in a personal audio system (PAS) ..... | 24 | +| II.6 | Handling of left and right channels ..... | 25 | +| II.7 | Dosimeter implementation example..... | 25 | +| II.8 | Handling of computational complexity ..... | 26 | +| II.9 | Handling of dose over days and weeks ..... | 26 | +| II.10 | Case of unknown headphone characteristics ..... | 26 | +| II.11 | Alternative audio signal capture point..... | 28 | +| II.13 | Uncertainties..... | 29 | +| Appendix III – | European Standard EN 71-1 for toys ..... | 30 | +| Appendix IV – | "Music" versus "noise" ..... | 31 | +| Appendix V – | On stapedius muscle reflex..... | 32 | +| Appendix VI – | Consideration of recovery phase..... | 33 | +| Appendix VII – | Example of health communication ..... | 35 | +| VII.1 | Recommendations to develop warnings and cues for action messages for device interfaces ..... | 35 | +| VII.2 | Suggested flow (an example) of information as part of standards for safe listening devices ..... | 35 | +| VII.3 | Example of how the information on listening parameters can be conveyed to the user ..... | 36 | +| VII.4 | Warnings and cues for actions..... | 37 | +| Appendix VIII – | Mechanism of hearing and impact of impact of sound ..... | 40 | +| VIII.1 | Sound and waves ..... | 40 | +| VIII.2 | Mechanism of hearing and hearing loss ..... | 40 | +| VIII.3 | Measurement of sound energy..... | 43 | +| VIII.4 | Equal energy principle..... | 46 | +| Bibliography..... | | 47 | + +# Introduction + +There is growing concern about the rising exposure to loud sounds in recreational settings such as nightclubs, discotheques, pubs, bars, cinemas, concerts, sporting events and even fitness classes. With the popularization of technology, devices such as personal audio systems are often listened to at high volumes and for prolonged periods of time. Regular participation in such activities poses a serious threat of irreversible hearing loss. + +The World Health Organization (WHO) estimates that [b-WHO-2018]: + +- Over 1.5 billion people globally experience some degree of hearing loss due to different causes. Of these, 430 million require hearing rehabilitation to ensure optimal functioning. These numbers are projected to rise in coming decades, unless action is taken to mitigate risk factors for hearing loss. +- Over a billion young people worldwide could be at risk of hearing loss due to unsafe listening practices. +- Among teenagers and young adults 12 to 35 years old in middle- and high-income countries: + - Nearly 50% listen to unsafe levels of sound with the use of personal audio devices such as MP3 players and smartphones. + - Around 40% are exposed to potentially damaging sound levels at nightclubs, discotheques and bars. + +The increasing sales of smartphones, with over 1.5 billion devices sold globally in 2019 alone, is another indicator of potential risk. This increased accessibility and use of personal audio systems for listening to music is coupled with their use at high volume and for long durations. Such risk-associated behaviours can permanently damage hearing capacity. + +In consideration of these facts, WHO launched the 'Make Listening Safe' initiative in 2015. The overall vision of this initiative is to ensure that people of all ages can enjoy listening with full protection of their hearing. + +Its aim is to reduce the risk of hearing loss posed by unsafe exposure to sounds in recreational settings. In order to achieve this, WHO has identified three specific objectives: + +- 1) Regulate exposure to loud sounds through personal audio systems. +- 2) Change listening behaviours among the target population. +- 3) Limit sound exposure in recreational settings. + +This Recommendation is a result of the collaboration between WHO and ITU on the 'Make Listening Safe' initiative, and is a common standard recognized by both organizations. + + + +## Recommendation ITU-T H.870 + +## Guidelines for safe listening devices/systems + +# 1 Scope + +This Recommendation describes the requirements on safe listening devices and systems, especially those for playing and listening to music, to protect people from hearing loss. + +As market trends have blurred the distinction between some listening devices and personal audio devices, use-cases are included to ensure this Recommendation applies as widely as reasonably practicable. + +NOTE 1 – Some of these use-cases follow the principle of classifying energy sources and prescribing safeguards against those sources as enshrined in [IEC 62368-1]. + +For the purposes of this Recommendation, the following types of devices are excluded: + +- two-way communication devices (such as walkie-talkies, etc.); +- rehabilitative and medical devices (e.g., hearing aids, FM systems and other assistive listening devices (ALD) approved as part of hearing aid and cochlear implant systems, etc.); +- personal sound amplification products/devices; +- professional audio equipment and devices. + +NOTE 2 – There are concerns about the exposure to sound from portable game consoles, but this is for future study. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.100.1] Recommendation ITU-T G.100.1 (2015), *The use of the decibel and of relative levels in speechband telecommunications*. +- [ITU-T P.57] Recommendation ITU-T P.57 (2021), *Artificial ears*. +- [ITU-T P.58] Recommendation ITU-T P.58 (2021), *Head and torso simulator for telephonometry*. +- [ITU-T P.380] Recommendation ITU-T P.380 (2003), *Electro-acoustic measurements on headsets*. +- [ITU-T P.381] Recommendation ITU-T P.381 (2020), *Technical requirements and test methods for the universal wired headset or headphone interface of digital mobile terminals*. +- [ITU-T P.382] Recommendation ITU-T P.382 (2020), *Technical requirements and test methods for multi-microphone wired headset or headphone interfaces of digital wireless terminals*. + +- [EN 50332-1] CENELEC EN 50332-1:2013, *Sound system equipment: Headphones and earphones associated with personal music players. Maximum sound pressure level measurement methodology. General method for "one package equipment"*. +- [EN 50332-2] CENELEC EN 50332-2:2013, *Sound system equipment: Headphones and earphones associated with personal music players. Maximum sound pressure level measurement methodology. Matching of sets with headphones if either or both are offered separately, or are offered as one package equipment but with standardised connectors between the two allowing to combine components of different manufacturers or different design*. +- [EN 50332-3] CENELEC EN 50332-3:2017, *Sound system equipment: Headphones and earphones associated with personal music players – Maximum sound pressure level measurement methodology – Part 3: Measurement method for sound dose management*. +- [IEC 60268-1] IEC 60268-1:1985, *Sound system equipment – Part 1: General*. +- [IEC 61252] IEC 61252:1993, *Electroacoustics – Specifications for personal sound exposure meters*, including its AMD1:200 and AMD2:2017. +- [IEC 61672-1] IEC 61672-1:2013, *Electroacoustics – Sound level meters – Part 1: Specifications*. +- [IEC 62368-1] IEC 62368-1:2018, *Audio/video, information and communication technology equipment – Part 1: Safety requirements*. +- [ISO 226] ISO 226:2003, *Acoustics – Normal equal-loudness-level contours*. +- [ISO 11904-1] ISO 11904-1:2002, *Acoustics – Determination of sound immision from sound sources placed close to the ear – Part 1: Technique using a microphone in a real ear (MIRE technique)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 calculated sound dose** [IEC 62368-1]: One-week rolling estimate of sound exposure expressed in percent of the maximum regarded as safe. + +NOTE – See B.4 of [EN 50332-3] for additional information. + +**3.1.2 diffuse-field frequency response of HATS (sound pick-up)** [ITU-T P.58]: Difference, in dB, between the third-octave spectrum level of the acoustic pressure at the ear-drum reference point (DRP) and the third-octave spectrum level of the acoustic pressure at the HATS reference point (HRP) in a diffuse sound field with the HATS absent. + +**3.1.3 eardrum reference point** [b-ITU-T P.10]: A point located at the end of the ear canal, corresponding to the eardrum position. + +**3.1.4 free sound field** [ISO 3745]: A field in a homogenous, isotropic medium free of boundaries. + +**3.1.5 free-field frequency response of HATS (sound pick-up)** [ITU-T P.58]: Difference, in dB, between the third-octave spectrum level of the acoustic pressure at the ear-drum reference point (DRP) and the third-octave spectrum level of the acoustic pressure at the HATS reference point (HRP) in a free sound field with the HATS absent (test point). + +**3.1.6 head and torso simulator (HATS)** [b-ITU-T P.10]: Manikin extending downward from the top of the head to the waist, designed to simulate the sound pick-up characteristics and the acoustic diffraction produced by a median human adult and to reproduce the acoustic field generated by the human mouth. + +**3.1.7 instructed person** [IEC 62368-1]: Instructed person is a term applied to persons who have been instructed and trained by a skilled person, or who are supervised by a skilled person, to identify energy sources that may cause pain (see Table 1) and to take precautions to avoid unintentional contact with or exposure to those energy sources. Under normal operating conditions, abnormal operating conditions or single fault conditions, instructed persons should not be exposed to parts comprising energy sources capable of causing injury. + +**3.1.8 material hearing impairment** [b-NIOSH]: An average of the hearing threshold levels for both ears that exceeds 25 dBHL at 1000, 2000, 3000 and 4000 Hz. + +**3.1.9 microphone-in-real-ear** [ISO 11904-1]: Refers to measurements carried out using miniature or probe microphones inserted in the ears of human subjects. + +**3.1.10 momentary exposure level** [IEC 62368-1]: Metric for estimating 1s sound exposure level from the HD 483-1 S2 test signal applied to both channels, based on [EN 50332-1], clause 4.2. + +NOTE 1 – MEL is measured in dB. + +NOTE 2 – See B.3 of [EN 50332-3] for additional information. + +**3.1.11 ordinary person** [IEC 62368-1]: Ordinary person is the term applied to all persons other than instructed persons and skilled persons. Ordinary persons include not only users of the equipment, but also all persons who may have access to the equipment or who may be in the vicinity of the equipment. Under normal operating conditions or abnormal operating conditions, ordinary persons should not be exposed to parts comprising energy sources capable of causing pain or injury. Under a single fault condition, ordinary persons should not be exposed to parts comprising energy sources capable of causing injury. + +**3.1.12 personal music/media player** [IEC 62368-1]: A personal music player is a portable equipment intended for use by an ordinary person, that: + +- Is designed to allow the user to listen to audio or audio-visual content / material; and +- Uses a listening device, such as headphones or earphones that can be worn in or on or around the ears; and +- Has a player that can be body worn (of a size suitable to be carried in a clothing pocket) and is intended for the user to walk around while in continuous use (for example, on a street, in a subway, at an airport, etc.). + +NOTE – Examples are portable CD players, MP3 audio players, mobile phones with MP3 type features, PDAs or similar equipment. + +**3.1.13 skilled person** [IEC 62368-1]: Skilled person is a term applied to persons who have training or experience in the equipment technology, particularly in knowing the various energies and energy magnitudes used in the equipment. Skilled persons are expected to use their training and experience to recognize energy sources capable of causing pain or injury and to take action for protection from injury from those energies. Skilled persons should also be protected against unintentional contact or exposure to energy sources capable of causing injury. + +**3.1.14 sound exposure** [EN 50332-3]: A-weighted sound pressure, $p_A$ , squared and integrated over a stated period of time between $t_2$ and $t_1$ : + +$$E = \int_{t_1}^{t_2} (p_A(t))^2 dt$$ + +**3.1.15 sound pressure level** [b-ITU-R V.574]: The logarithm, generally expressed in decibels (dB SPL), of the ratio of sound pressure and a reference pressure $p_0$ , often 20 $\mu\text{Pa}$ . Note that a factor of 20 is used when the ratio is between two sound pressures, rather than between two sound intensities. + +$$SPL = 20 \log_{10} \left( \frac{p}{p_0} \right)$$ + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 acoustic reflex threshold:** The sound pressure level (SPL) at which a sound stimulus triggers stapedius muscle reflex (SMR). + +**3.2.2 acoustic trauma:** A single exposure to sound resulting in immediate injury to the auditory system. + +**3.2.3 damage-risk criteria:** An archaic term referring to the risk of noise induced hearing loss (NIHL) presented by various levels of noise exposure. In this Recommendation this term is replaced with several preferred contemporary terms: 'dose-response relationship', 'risk', or 'exposure limit'. + +**3.2.4 dBA:** Decibels of sound pressure level measured using the A-weighting network [IEC 61672] and [IEC 60268-1], see also Figure II.2; a frequency weighting intended to measure low-intensity noise (around 40 phon loudness level) but which has also become commonly used for measuring occupational and environmental noise exposures. + +NOTE – The latter use is based on studies of noise-exposed workplace populations in the 1950s and 1960s. That work recommended the use of A-weighting given both its availability in sound level meters and its ability to predict the dose-response relationship over the noise spectra studied [b-Burns-1973] and [b-Burns-Robinson]. Subsequent to that work, the analyses of noise exposed populations upon which the weekly sound allowance in this document are based used A-weighting in measuring noise exposure [b-Neitzel] and [b-Fligor]. + +**3.2.5 dBFS:** dB full scale is the signal level of a digital signal relative to its overload or maximum level. Different conventions exist. It is common to assign a digital representation of a full-scale sinusoidal the value of 0 dBFS RMS. The peak level can then reach +3.01 dBFS. In other cases, the RMS level of a digital full-scale square wave is assigned 0 dBFS RMS. The maximum peak level is then also 0 dBFS. For the latter cases, dBFS is equivalent to dBov. (dBov: dB relative to digital overload is the signal level of a digital signal relative to its overload or maximum level. See [ITU-T G.100.1].) + +**3.2.6 dBHL:** Decibels of hearing level at a certain frequency; a level used to measure an audiometric hearing threshold relative to the level defined as normal. + +NOTE – It is the ear's sensitivity in a human with normal hearing, at different frequencies, that is the reference. Figure 1 of [ISO 226] shows standardized equal-loudness contours at different sound levels and a mapping of phon (loudness) against dB SPL (level). The two scales meet at 1 kHz. dB SPL is by definition referenced at the threshold of hearing at 1 kHz, i.e., 0 phon (and 0 dB SPL). + +**3.2.7 diffuse sound field:** A field where at any position in the medium, sound is incident from all directions with equal intensities and random phase. The reverberant sound does not vary with receiver position. (Adapted from [b-Vér].) + +**3.2.8 (sound) dose:** The total quantity of sound energy received by the human ear during a specified period. In the context of this Recommendation, it is the same as sound exposure (see clause 3.1.14). The unit of (sound) dose is $\text{Pa}^2\text{h}$ . + +**3.2.9 dosimetry:** The calculation and assessment of the dose received by the human ear. + +**3.2.10 equal energy principle:** The premise that the total effect of sound is proportional to the total amount of sound energy received by the ear, irrespective of the distribution of that energy in time. According to this principle, equal amounts of sound energy are expected to cause equal amounts of sound induced permanent threshold shift regardless of the distribution of the energy across time. This principle allows the question of hearing damage risk posed by a sound exposure to be related to a sound dose. + +**3.2.11 equivalent continuous A-weighted sound pressure level:** A continuous sound pressure level (SPL) in dBA which is considered to pose the same risk as a time-varying SPL, calculated using a 3-dB exchange rate between level and time. Mathematically, it is represented as: + +$$L_{Aeq,T} = 10 \lg \left\{ \frac{1}{T} \int_{t_1}^{t_2} p_A^2(t) dt \right\} / p_0^2 \text{ dBA}$$ + +where: + +$L_{Aeq,T}$ is the equivalent continuous A-weighted sound pressure level re 20 $\mu\text{Pa}$ , determined over a time integration interval $T = t_2 - t_1$ + +$p_A(t)$ is the instantaneous A-weighted sound pressure of the sound signal + +$p_0$ is the reference sound pressure of 20 $\mu\text{Pa}$ . + +**3.2.12 equivalent continuous average sound level normalized:** A continuous SPL in dBA which is considered to pose the same risk as a certain time-varying SPL pattern measured using a 3-dB exchange rate and normalized to an $n$ -hour exposure period. For example, the value for $n$ could be 8, in which case this may also be referred to as an $L_{A8h}$ or $L_{EX8h}$ , or $n=40$ , $L_{EX40h}$ . + +**3.2.13 excess risk:** The risk of sound induced hearing loss (SIHL) associated with a specific amount of exposure. + +**3.2.14 exchange rate:** The change in average noise level (in dB) that corresponds to a doubling or halving of allowable exposure time. + +**3.2.15 frequency response:** In this context, frequency response is short for "sensitivity vs. frequency response", sometimes referred to as the "tone curve" of an audio device, such as a headphone, loudspeaker, microphone, amplifier, etc. + +**3.2.16 hearing threshold level:** Sound pressure level (SPL) at specific audiometric test frequencies, measured in dBHL. + +**3.2.17 listening device:** A wearable device used to deliver sound to the ear. + +Consists of a transducer and fitting to accommodate in the ear, on the ear or over the ear listening. Examples are headphones and earphones. + +Headphones and earphones may include amplifiers and other electronics, such as for wireless or digital connection, signal processing, noise cancellation, or even media storage for subsequent playback. As such, headphones and earphones with such functionality could be classed as personal audio systems. + +NOTE – The principle of classifying energy sources and proscribing safeguards against those sources is enshrined in [IEC 62368-1], on which much of this Recommendation is based. + +**3.2.18 media:** Audio or audio-visual content for the purposes of entertainment whereby long-term exposure may result in hearing loss. Examples are music, gaming and podcasts. + +**3.2.19 personal audio device:** A portable device designed to be worn on the body or fit in the clothing pocket to listen to various forms of media. It can be connected to a listening device. An example of a personal audio device is a personal media player (PMP). + +**3.2.20 personal audio system (PAS):** A system of a personal audio device and a listening device. Examples are a personal media player (PMP) connected to headphones, and headphones capable of playing locally stored content independently of an external PAD. + +**3.2.21 safe listening device:** A personal audio device/system that meets the requirements and criteria to minimize the users' risk of acquiring hearing loss, (as a consequence of its use) can possibly be termed as a safe listening device. It could include music players (MP3 players, smartphones and personal music players) used with a listening device. + +**3.2.22 sound allowance:** A dose estimate of sound exposure over a certain rolling period of time (e.g., daily or weekly), commonly expressed as a percentage of the maximum regarded as safe. A weekly sound allowance is equivalent to 100% calculated sound dose (CSD). + +**3.2.23 sound-induced:** Refers to a state or a quality resulting from exposure to sound. The sound may be (part of) music or "noise", which implies the sound is not desirable. + +**3.2.24 sound-induced permanent threshold shift:** Synonymous with permanent sound induced hearing loss (SIHL). + +**3.2.25 sound-induced temporary threshold shift:** Sound induced hearing loss (SIHL) that results from exposure to sound but recovers after a sufficient time spent in low sound conditions. + +**3.2.26 sound-induced tinnitus:** Perception of phantom sound in the ears or head that are either temporary or permanent, following excessive sound exposure. + +**3.2.27 stapedius muscle reflex:** The process in which the stapedius and tensor tympani muscles of the ossicles contract when the ear is exposed to high intensity sound. This is also called auditory reflex. + +**3.2.28 transducer:** An electronic device that converts energy from one form to another. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------------------------------------------| +| ALD | Assistive Listening Devices | +| ANR | Active Noise Reduction | +| ART | Acoustic Reflex Threshold | +| CLL | Chosen Listening Level | +| CSD | Calculated Sound Dose | +| DAC | Digital to Analogue Conversion | +| dBA | Decibels of sound pressure level measured using the A-weighting network | +| dBFS | Decibel Full Scale | +| dBHL | Decibels of Hearing Level | +| DRP | Eardrum Reference Point | +| ER | Exchange Rate | +| HATS | Head And Torso Simulator | +| HTL | Hearing Threshold Level | +| LEQ | Equivalent continuous average sound level | +| LEX | Equivalent continuous average sound level normalized | +| MIRE | Microphone-In-Real-Ear | + +| | | +|-------|-----------------------------------------| +| NIHL | Noise Induced Hearing Loss | +| NIPTS | Noise Induced Permanent Threshold Shift | +| PAD | Personal Audio Device | +| PAS | Personal Audio System | +| PLD | Personal Listening Device | +| PMP | Personal Media Player | +| RMS | Root Mean Squared | +| SEL | Sound Exposure Level | +| SIHL | Sound Induced Hearing Loss | +| SLD | Safe Listening Device | +| SMR | Stapedius Muscle Reflex | +| SPL | Sound Pressure Level | +| TTS | Temporary Threshold Shift | +| VR | Virtual Reality | + +# 5 Conventions + +None. + +# 6 Safe listening: Introduction + +Temporary and permanent hearing threshold shifts from exposure to sound and noise is an increasing public health problem, particularly in children and adolescents. In fact, sound-induced hearing loss (SIHL) is the leading cause of preventable hearing loss in the world. From the early 1990s to 2000, it was estimated that the number of young people with SIHL has increased from 6.7% to 18.8%. Some of this can be attributed to the fact that in this day and age, young people are utilizing their leisure time with activities that expose them to high levels of music using personal audio systems (PAS) or attending communal events such as concerts, bars, clubs, etc. Despite this emerging epidemic, there are currently almost no standards set to limit sound exposure in non-occupational settings, especially for PAS. This Recommendation addresses this standardization gap. + +It may be considered that prevention of hearing loss through safe listening practices is the responsibility of the individual. However, the onus of raising awareness and creating an environment for safe listening lies with the community, manufacturers of devices, governments and other stakeholders. + +Hearing loss can occur as a consequence of listening to high levels of sound over prolonged periods of time. The unsafe use of personal audio devices (PADs) poses a threat to the hearing of millions. + +Such hearing loss is permanent, but it can largely be prevented through safe listening practices. Appropriate technology can help to reduce the risk of unsafe listening. A personal audio device/system in compliance with standards which serve to minimize the users' risk of acquiring hearing loss, (as a consequence of its use) can possibly be termed as a safe listening device/system. + +The term safe listening refers to listening behaviour that does not put peoples' hearing at risk. A person's risk of losing his/her hearing depends on how loud, for how long and how often the person is exposed to loud sounds. Such exposure may be through personal audio devices or in + +entertainment venues as well as in the surrounding environment, such as in traffic, in the workplace or at home. + +The term sound allowance refers to the acceptable level of sound energy an individual can receive without putting his/her hearing at risk. The term “weekly sound allowance” is equivalent in meaning to “100% calculated sound dose (CSD)” (see clause 3.1.1). It is recommended to use the term 'sound allowance' for health communication purposes, rather than 'dose'. It should be also noted that the sound allowance determined as described by this Recommendation ignores sound exposure from sources other than personal audio devices. Depending on what those exposures are, a risk of hearing loss may still exist for an individual. + +Use-cases for consideration when applying this Recommendation can be found in [b-FSTP-SLD-UC]. + +## 6.1 Background + +Appendix VIII provides background information for safe listening. + +## 6.2 Personal audio system + +The definition for personal audio system (PAS) is given in clause 3.2.20, and Figure 6-1 shows the general architecture of a PAS. + +![Figure 6-1: Architecture of a personal audio system (PAS). The diagram shows a 'Personal audio system' containing a 'Personal audio device' and a 'Listening device'. The 'Personal audio device' includes a 'Source' (pink box), an 'Effect' (cyan box), a 'Volume control' (yellow box), and a 'DAC' (yellow box). The 'Source' connects to the 'Effect', which connects to the 'Volume control', which connects to the 'DAC'. The 'DAC' connects to the 'Listening device' via an 'IF' (Interface). The 'Listening device' contains a 'Transducer' (yellow box).](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +``` +graph LR + subgraph PAS [Personal audio system] + subgraph PAD [Personal audio device] + Source[Source] --> Effect1[Effect] + Effect1 --> Volume[Volume control] + Volume --> DAC[DAC] + Effect2[Effect] --> DAC + end + subgraph LD [Listening device] + Transducer[Transducer] + end + DAC -- IF --> Transducer +``` + +Figure 6-1: Architecture of a personal audio system (PAS). The diagram shows a 'Personal audio system' containing a 'Personal audio device' and a 'Listening device'. The 'Personal audio device' includes a 'Source' (pink box), an 'Effect' (cyan box), a 'Volume control' (yellow box), and a 'DAC' (yellow box). The 'Source' connects to the 'Effect', which connects to the 'Volume control', which connects to the 'DAC'. The 'DAC' connects to the 'Listening device' via an 'IF' (Interface). The 'Listening device' contains a 'Transducer' (yellow box). + +**Figure 6-1 – Architecture of a personal audio system (PAS)** + +In this diagram, "source" can be either stored locally on the device or retrieved remotely, e.g., streamed from a local server or the Internet. + +A PAS is intended for use by an ordinary person and + +- is designed to allow the user to listen to audio or audio-visual content/material; and +- uses a listening device, such as headphones or earphones that can be worn in or on or around the ears; and +- has a player that can be body worn (of a size suitable to be carried in a clothing pocket) and is intended for the user to walk around with while in continuous use (for example, on a street, in a subway, at an airport, etc.); and +- has means the user uses to adjust the volume of sound delivered to the ear. + +Examples are portable CD players; MP3 audio players; mobile phones or tablets smart watches with MP3 type features; headphones which can locally store audio content or with built-in wireless connection to a music server without use of a separate PAD. + +The requirements do not apply to: + +- professional equipment; + +- hearing aid equipment and other devices for assistive listening; +- the following type of analogue personal music players: + - long distance radio receiver (for example, a multiband radio receiver or world band radio receiver, an AM radio receiver), and + - cassette player/recorder; + +NOTE 1 – This exemption has been allowed because this technology is falling out of use, and it is expected that in a few years it will no longer exist. This exemption will not be extended to other technologies. + +- a player while connected to an external amplifier that does not allow the user to walk around while it is in use. + +NOTE 2 – In addition to the above, communication devices are excluded from the scope of this Recommendation. + +NOTE 3 – In the meantime, the immediate focus is on music, but gaming and virtual reality is for future study. + +### 6.2.1 Consideration of headphones and earphones + +The situation of headphones/earphones listening using portable equipment is different from domestic loudspeaker reproduction. Studies of the habits of headphone listening with portable music players indicate that the listening level varies greatly from person to person [b-SCENIHR]. With some portable players and headphones it is possible to play at high levels. The portability of the equipment also increases the risk of reaching high exposure times. + +When exposed to a high-level sound field such as in a concert or club, there may be perceivable body vibration in addition to stimuli via the ears. In the case of earphones/headphones, the vibration part is missing. + +Figure 6-2 contains an example of the relationship between headphone type (earbuds and supra-aural or isolators) and chosen listening levels (CLLs) depending on the surroundings (airplane, bus, quiet, etc.). + +![Bar chart showing the percentage of subjects with chosen listening levels (CLLs) of 85 dBA and greater for two headphone types across different noise environments. The y-axis is 'Percentage of subjects with CLLs 85 dBA and greater' (0-60). The x-axis shows environments: Quiet, PN 50, PN 60, PN 70, Bus 70, Airplane 75, PN 80. Legend: Black bars = Earbuds and supra-aural; Grey bars = Isolators. Asterisks (*) indicate significant differences for PN 70, Bus 70, Airplane 75, and PN 80.](dbc1673750fd53d4203f4d93963fdab6_img.jpg) + +| Environment | Earbuds and supra-aural (%) | Isolators (%) | +|-------------|-----------------------------|---------------| +| Quiet | ~7 | ~4 | +| PN 50 | ~9 | ~4 | +| PN 60 | ~14 | ~4 | +| PN 70 | ~28* | ~11 | +| Bus 70 | ~25* | ~6 | +| Airplane 75 | ~31* | ~14 | +| PN 80 | ~52* | ~28 | + +H.870(22)\_F6-2 + +Bar chart showing the percentage of subjects with chosen listening levels (CLLs) of 85 dBA and greater for two headphone types across different noise environments. The y-axis is 'Percentage of subjects with CLLs 85 dBA and greater' (0-60). The x-axis shows environments: Quiet, PN 50, PN 60, PN 70, Bus 70, Airplane 75, PN 80. Legend: Black bars = Earbuds and supra-aural; Grey bars = Isolators. Asterisks (\*) indicate significant differences for PN 70, Bus 70, Airplane 75, and PN 80. + +Figure 6-2 – Headphone type and chosen listening level [b-Portnuff] + +### 6.2.2 Note on individuality + +Individual differences in the dimensions of the ear canal affect the frequency and amplitude of the ear canal resonance. + +That consideration of factors such as height and gender differences as well as the head circumference of an individual or even the measurement of the resonance characteristics of the ear canal of an individual will lead to alleviating the individual differences is strongly suggested by the hitherto medical practices. + +### 6.2.3 Guidance on measurement + +If measuring the analogue electrical output level of a PAS, the procedures described in clause 7.2.2 of [ITU-T P.381] using the relevant specified test set-up, should be used. This includes playback of a certain programme simulation signal at a defined digital level, simulation of the headphones using a resistive load and appropriate measurement of the output voltage of the player. + +If measuring the overall electro-acoustic sensitivity of headphones/earphones, the procedures described in clause 8.2.2 of [ITU-T P.381] using the relevant specified test set-up, should be used. If measuring the electro-acoustic sensitivity of headphones/earphones as a function of frequency, the procedures described in clause 8.1.5 of [ITU-T P.381] using the relevant specified test set-up, should be used. This may be used for example for a dose estimator, as described in Appendix II of this Recommendation. + +These headphone measurements include playback of a certain programme simulation signal at a defined electrical level, a head and torso simulator (HATS), appropriate measurement of the output sound pressure for a certain input voltage, including averaging over several 're-seatings' of the headphones on the HATS. + +These ITU-T Recommendations partly refer to the CENELEC EN 50332 series of specifications, for harmonization purposes. For digital interfaces, guidance is also found in the CENELEC specifications. + +NOTE – [ITU-T P.381] refers to the commonly used 3-pole or 4-pole 3.5 mm or 2.5 mm diameter jack/plug. For 5-pole connectors, guidance is found in [ITU-T P.382]. + +If measuring the overall acoustic output level of a portable music player including headphones/earphones, the procedure in [EN 50332-1] should be used. + +# 7 Damage risk criteria + +## 7.1 Operational modes + +It is required that PASs or PADs shall include a system that tracks the user's exposure time, and estimates sound level and usage of a reference exposure (sound allowance). This includes all media playback through the device or system (i.e., stored locally or streamed) during times when the user is using ear/headphones. Voice calls may be excluded as they are specified separately by other standards. + +This system shall determine the exposure of the user based on the following mode: + +- Mode 1: (WHO) standard level for adults: this will apply 1.6 Pa2h per 7 days as the reference exposure. + +NOTE 1 – The value is adapted from [IEC 62368-1] and is based on the values mentioned in [b-2009/490/EC], which stipulated that sound is safe when below 80 dB(A) for a maximum of 40 hours per week. Therefore, the value of 100% calculated sound dose (CSD) corresponds to 80 dB(A) for 40 hours. + +It is recommended that the device or system offer a more conservative mode to users that prefer or benefit from a more conservative level as outlined in mode 2: + +- Mode 2: (WHO) standard level for users that prefer or may benefit from lower sound levels (e.g., for children): this will apply 0.51 Pa2h per 7 days as the reference exposure. + +The device or system should allow the users to select their reference exposure as one of the above-mentioned two modes. + +NOTE 2 – Reference exposures are derived from 80 dBA (Mode1) and 75 dBA (Mode 2) SPL for 40 hours per week (which in turn is derived from 8 hours per day, 5 days/week). + +NOTE 3 – An alternative to expressing exposure in terms of % used, is to express the *time left* until reaching a certain exposure (e.g., remaining playback time at the current playback level until reaching 100%). + +It is recommended that mode choice be given when using the player for the first time (or when the device is reset to factory settings). It is recommended that the user be able to change the mode choice at any later time, e.g., via a device configuration menu. + +Examples of weekly listening time duration based on sound allowance for the modes above can be found in Table 1 and Table 2. + +**Table 1 – Example of weekly listening time for Mode 1** + +| dB(A) SPL | Weekly (1.6 Pa2h) | +|------------------|-------------------------------------| +| 107 | 4.5 min | +| 104 | 9.5 min | +| 101 | 19 min | +| 98 | 37.5 min | +| 95 | 75 min | +| 92 | 2.5 h | +| 89 | 5 h | +| 86 | 10 h | +| 83 | 20 h | +| 80 | 40 h | + +**Table 2 – Example of weekly listening time for Mode 2** + +| dB(A) SPL | Weekly (0.51 Pa2h) | +|------------------|--------------------------------------| +| 107 | 1.5 min | +| 104 | 3 min | +| 101 | 6 min | +| 98 | 12 min | +| 95 | 24 min | +| 92 | 48 min | +| 89 | 1 h 36 min | +| 86 | 3 h 15 min | +| 83 | 6 h 24 min | +| 80 | 12 h 30 min | +| 77 | 25 h | +| 75 | 40 h | + +## 7.2 Uncertainty in dose estimate + +In estimating sound dose there is some uncertainty. Some sources for uncertainties are: + +- sound source; +- variation in headphone characteristics of a single model, due to production tolerances; +- variation due to unknown headphone type; +- manufacturing tolerance; +- errors due to incorrect manual selection of headphone type; +- variations in fit to the artificial ear during characterization; +- imperfect relation between artificial ears and real ears; +- imperfect relation between a standardized diffuse-field correction and a variety of human head-related transfer functions; +- variations in fit to the human ears; +- uncertainties in characterization of player characteristics, especially due to non-linear processing in the alternative implementation shown in Figure II.5; +- errors in calculations; +- users' individual susceptibility to sound exposure; +- exposure from other sources. + +Since some of these uncertainties are typically several dB, and an error of 3 dB constitutes a 100% dose error, uncertainties of dose estimation can be expected to be hundreds of percent. It is therefore suggested to refrain from signalling "safe" and "green" to the user based on dose readings below a certain limit. + +The dose estimation is however relevant in accounting for the general trends: + +- higher signal level means higher risk +- longer exposure means higher risk +- the spectral content of the music is accounted for. + +Further details on this subject remain for future study. + +# 8 Measurement methods + +## 8.1 Dosimetry + +### 8.1.1 Main related standards + +[EN 50332-1], [EN 50332-2] and [EN 50332-3] describe a dose measurement system in a PMP. [IEC 61252] describes acoustic dosimeters to be worn on the body. + +### 8.1.2 Definition of dose in the context of acoustic dosimetry + +A dose in the context of acoustic dosimetry is calculated as follows: + +$$dose = \int_{t_1}^{t_2} (p_A(t))^2 dt$$ + +where $p_A$ is the A-weighted and diffuse-field corrected sound pressure. + +For example, the dose acquired when being subjected to 80 dBSPL(A) during an exposure duration of 40 h is calculated as follows: + +- The root mean square (RMS) sound pressure is $10^{\frac{80}{20}} \cdot \frac{20\mu Pa}{1Pa} = 0.2 Pa$ . Consequently, the dose is $0.2^2 \cdot 40 = 1.6 Pa^2 h$ . + +Such a specific dose may be defined as a reference dose and the measured exposure estimation during a certain period may be expressed as a percentage of this reference dose. + +1.6 Pa2h constitutes 100% weekly sound allowance, corresponding to 100% calculated sound dose (CSD) as defined in [EN 50332-3]. + +For an example of dosimetry implementation, see Appendix II. + +### 8.1.3 Testing of dosimeter functionality + +The dosimeter functionality is tested by playing the programme simulation sound according to [EN 50332-1] and [IEC 60268-1] and measuring the time until the dose estimate reaches 100% CSD, using interpolation and tolerances as described in [EN 50332-3]. Such testing may be performed in the acoustic domain (when a headset of known sensitivity versus frequency response is used) or in the electrical domain using a 32 Ω resistive load (when the headset characteristics are unknown). See measurement set-up information in [ITU-T P.381]. + +NOTE – Testing methods for digital signal such as in [EN 50332-1] should also be considered and are for further study. + +It is recommended to verify that the dose grows at twice the rate for every 3 dB increase in output level when varying content levels from −28 to −4 dBFS (see dBFS definition in [EN 50332-1]) and similarly when varying volume control settings. + +It is recommended to test the A-weighting filter and other detailed dosimeter characteristics as described in [IEC 61252]. + +## 9 Sensitivity range and frequency response of headphones + +Knowledge of the gain of the signal chain from volume control(s) available to the user and the sensitivity of the listening device are important for calculating the sound dose with reasonable precision. For the simplest PAS comprised of a PAD connected to a passive headphone (containing no electronics) of an unknown type, the calculated sound dose shall assume the maximum permitted headphone sensitivity [EN 50332-3]. + +However, the user convenience resulting from headphones with digital wireless or wired interfaces has led to a rapid shift away from such simple passive headphones. This brings new possibilities to make CSD more accurate and foster safe listening better, including: + +- Communication of sensitivity, including changes due to internal processing, by a listening device to a PAD. +- Calculation within the listening device of CSD increments during a listening session, for communication to PADs. +- System knowledge of the quality of the seal to the individual user's ears, providing a more relevant sensitivity value than that measured on laboratory acoustic test mannequins. +- Personalised processing to improve clarity of content, making lower levels more acceptable. + +An increasingly common PAS that is capable of implementing these possibilities is comprised of a smartphone PAD connected via Bluetooth to a headphone containing signal processing capabilities. Given these existing technical capabilities and to spur future developments, two general principles are recommended: + +- Calculation of sound dose increments should be determined as late as possible in the signal chain – from stored music file to the ear, as this is where the best estimate of increments to CSD are to be had. In particular, CSD increments shall include the effect of all volume controls in the signal chain. + +- Accumulating the CSD over time to determine the fraction of the weekly sound allowance a user has received is best done in a device that includes a visual display to enable rich health communication messages to best influence user behaviour. Such a device is also best positioned to maintain or connect to a database storing the user personal health information. + +Considering these principles, if a listening device is capable of communicating via a digital interface its sensitivity values, as affected by the current volume setting, these shall be used instead of the maximum permitted headphone sensitivity. Furthermore, if a listening device is capable of determining CSD increments for a whole or partial listening session and communicating that via a digital interface, a PAS shall use these values instead of or the PAD's calculation of CSD increment. + +Such capabilities potentially allow making listening safer in use cases beyond the simple single music player use case. This is an area for further study. + +# 10 Profiles + +A proposed goal of profiles or different grades of PAS is to provide a means of indicating to end users the comparative accuracy of different PAS implementations, in a simple and meaningful manner, to build trust in the calculated sound dose and the resulting notifications. + +# 11 Health communication + +The 'Make Listening Safe' strategy (see Appendix I) aims to reduce the risk of hearing loss through promotion of safe listening among its target group (users of personal audio devices). In view of this, the standard for safe listening devices includes a tool that will allow people to monitor their own personal sound exposure. Such a tool shall serve the purpose of giving the choice of safe listening to the users, while maintaining good quality sound output. Along with this tool, it is important that users of devices be empowered to make the right listening choice through greater awareness and information. + +For this purpose, this clause outlines health communication aspects that shall be applied for complete implementation of standards for safe listening devices. + +This clause aims at informing manufacturers of personal audio devices on how to promote safe listening practices among users/consumers. Specifically, it presents evidence-based recommendations on how to communicate the risks of unsafe listening and support users/consumers in the adoption of appropriate behaviour in this field. The recommendations are informed by evidence available in peer reviewed literature or gained through the study of listening habits of the target group i.e., users of personal audio devices. + +## 11.1 Purpose of including health communication as part of the standards for safe listening personal audio systems + +The intent is to provide users with information and guidance to enable them to make safe listening choices. These include providing: + +- 'Personal usage information', in order for the user to know: + - their own listening habits (use of daily and weekly sound allowance) + - how to use safe listening features of the specific devices; +- 'Personalized recommendations and cues for actions' for safe listening, customized based on each user's listening profile +- 'General information' on + - safe listening and ways to practice it + +- the risk associated with unsafe listening +- the risk of hearing loss due to loud sounds from sources other than the personal audio system. + +This information and guidance shall be shared by default with users via their mobile devices in order to reduce the risk of hearing loss. + +## **11.2 Key recommendations for communication as part of standards for safe listening devices** + +Information and messages on safe listening shall be provided through: + +- the device interface1 (wherever an appropriate audio or visual interface is available) +- instruction manuals + +Information about the safe listening features of the device should be included on or in the packaging. + +### **11.2.1 Device interface user information** + +Clauses 11.2.1.1 and 11.2.1.2 outline information that shall be available to the user through the device interface. + +#### **11.2.1.1 Personal usage information** + +Information regarding various listening parameters defining the users' listening habits shall be accessible to users in order to allow them to keep track of their exposure to sound through the device. In cases of devices with a screen, this could be through an icon on the screen. Through the icon, the user shall be able to see their use of daily/weekly sound allowance in an easy-to-understand presentation, e.g., the person may be able to view how much of the weekly sound allowance has been used and to see how their listening behaviour has been over the past seven days. + +In devices without a screen, the information shall be made available through alternative means, such as audio cues or via another device with a screen. + +NOTE – For such devices (without screens), feedback to the user may not be provided in real time but it can be provided at a later time. + +The device (when capable) should display: + +- a) the average sound level for the day and week; +- b) the time for which the user has listened in hours and minutes over the day and the week. + +Figure 11-1 gives a non-normative example of information provided on a smartphone visual interface for safe listening. + +--- + +1 Refers to the hardware components (such as screen) that allow a user to interact with an electronic device. + +![Four smartphone screens showing sound exposure statistics and warnings. The first screen shows 51.6% allowance. The second shows 52% allowance with a bar chart. The third shows 119.5% allowance with a red warning circle. The fourth shows 120% allowance with a red bar chart. All screens show 'Sound track #5 Disclosure' and playback controls.](9ce50bc10864dc86e1cdee4be08f1897_img.jpg) + +The figure displays four smartphone screens illustrating the user interface for sound exposure monitoring. Each screen shows the current sound allowance as a percentage of the weekly limit, along with listening statistics and playback controls for 'Sound track #5 Disclosure'. + +- Screen 1:** Shows a green circular progress indicator at 51.6%. +- Screen 2:** Shows a green bar chart at 52% with the text 'Time left: 01:14:17', 'Today's listening time: 37 min', and 'Average dB level (Leq) : 93.3 dB'. +- Screen 3:** Shows a red circular progress indicator at 119.5%. +- Screen 4:** Shows a red bar chart at 120% with the text 'Time left: 00:00:00', 'Today's listening time: 1:80h', and 'Average dB level (Leq) : 93.5 dB'. + +Four smartphone screens showing sound exposure statistics and warnings. The first screen shows 51.6% allowance. The second shows 52% allowance with a bar chart. The third shows 119.5% allowance with a red warning circle. The fourth shows 120% allowance with a red bar chart. All screens show 'Sound track #5 Disclosure' and playback controls. + +H.870(18)-Err.1(18)\_F11-1 + +**Figure 11-1 – Examples of information provided on a smartphone visual interface for safe listening** + +#### 11.2.1.2 Messages + +The device shall provide the user with warnings and cues for action: + +- The device shall give relevant warnings and cues for actions when the user exceeds 100% of the weekly allowance. Suggestions for the development of such messages are provided in Appendix VII. + - The user shall receive first a "warning" expressed through text and visuals informing that a threshold has been reached and that from this point on, further listening at the same volume will pose a risk for his/her hearing. + - The warning shall be followed by a "cue for action" in which the user is offered the choice to either accept the risk of continued listening or protect his/her hearing. The "cue for action" should be linked to active options on the device such as: + - automatic safe volume option, by which the device automatically changes the volume to achieve a safer listening level; + - direct access to volume settings; + - set up of default volume limits; + - remind later option; + - ignore and continue option. + - If the user fails to take any action, the volume shall automatically be reduced as described in clause 13.1 (a sound level at the DRP, with diffuse-field correction, no greater than 80 or 75 dBA (according to the mode selected)). + +NOTE 1 – The timeframe for implementation of this feature by manufacturers will be in line with the recommendations made by CENELEC. + +NOTE 2 – If, upon reaching 100% of the user's weekly allowance, the level is automatically reduced to 80 dBA (75 dBA for sensitive listeners), the user's sound exposure will continue to increase beyond 100%. Such an action is therefore not fully protective against further risk to hearing; rather, the intention is to ensure that listening proceeds at no more than a moderate level until the user has acknowledged the warning. + +- b) The device should provide relevant messages when the sound allowance usage reaches certain pre-determined levels. Refer to Appendix VII.1 for the suggested levels at which warnings/cues can be given and sample content. + +Such warnings depend on the device's capability and should be multimodal, e.g., in the form of visual, vibratory or audible warnings, in order to ensure that the user's attention can be directed towards these. Figure 11-2 gives non-normative examples of messaging displayed in a smart watch. + +![Figure 11-2 shows two smartwatch screens displaying 'SAFELISTEN' messages. The left screen shows: '50% of daily allowance: You have spent 50% of your safe listening allowance for the day. Keep the volume low to listen longer.' The right screen shows: 'Hey! Your last sound dose was 60%. Well done! Keep listening safely.'](56a7fc5964ed9463fa47ca8a60568dec_img.jpg) + +The image shows two smartwatch screens side-by-side. Both screens have a dark blue background with a white header that says 'SAFELISTEN' next to a headphone icon. The left screen displays the text: '50% of daily allowance: You have spent 50% of your safe listening allowance for the day. Keep the volume low to listen longer.' The right screen displays the text: 'Hey! Your last sound dose was 60%. Well done! Keep listening safely.' + +Figure 11-2 shows two smartwatch screens displaying 'SAFELISTEN' messages. The left screen shows: '50% of daily allowance: You have spent 50% of your safe listening allowance for the day. Keep the volume low to listen longer.' The right screen shows: 'Hey! Your last sound dose was 60%. Well done! Keep listening safely.' + +H.870(18)\_F11-2 + +**Figure 11-2 – Example of messaging displayed in a smart watch** + +- Daily messages: The device should provide a daily summary message that is based on the user's listening behaviour over the past days, encouraging safe listening habits and discouraging or warning against unsafe listening habits. Examples of such messages are provided in clause VII.3. + +### 11.2.2 General information + +- When the device has a screen, information on what is safe listening and its benefits, as well as the risks posed by unsafe listening, shall be displayed on the screen. + +NOTE – It is expected that the information above is accessible without the need for excessive navigation. + +The availability of this information shall be indicated on the user interface (home screen) through a distinct and recognizable icon. Figure 11-3 gives a non-normative example of a safe listening icon displayed on a smartphone screen. + +![Figure 11-3: A smartphone screen displaying the Safelisten app icon among other app icons like Settings, Travel, Email, and Games. The status bar shows the time 14:15.](7b517f15a2d307945bd78e30c13a75bd_img.jpg) + +Figure 11-3: A smartphone screen displaying the Safelisten app icon among other app icons like Settings, Travel, Email, and Games. The status bar shows the time 14:15. + +H.870(18)\_F11-3 + +**Figure 11-3 – Safe listening icon displayed on a smartphone screen** + +There should be a tutorial informing users of what is safe listening, what the risks are of unsafe listening, the device's safe listening features and how to use them. The screens should also include links to relevant webpages where the user can find more information. Figure 11-4 gives non-normative examples of screens linking to information on safe listening and external links. + +![Figure 11-4: Two side-by-side smartphone screens. The left screen is titled 'Safelisten' and contains questions: 'How does loud music affect my ears?', 'What is safe listening?' (with a waveform icon), and 'How can I make listening safe on my device?' (with a device icon). A button at the bottom says 'No, thanks. Play my music'. The right screen is titled 'Information' and contains: 'What are the first signs of hearing damage?' (with a hearing icon), a text block about hearing damage, 'What does hearing loss sound like?' (with a sound wave icon), a list of links: 'Centres for disease control and prevention' and 'Hear the world', and buttons for 'What is safe listening?' and 'OK, thanks. Play my music'.](daff947a443eb2a4735e3a81b6f756d9_img.jpg) + +Figure 11-4: Two side-by-side smartphone screens. The left screen is titled 'Safelisten' and contains questions: 'How does loud music affect my ears?', 'What is safe listening?' (with a waveform icon), and 'How can I make listening safe on my device?' (with a device icon). A button at the bottom says 'No, thanks. Play my music'. The right screen is titled 'Information' and contains: 'What are the first signs of hearing damage?' (with a hearing icon), a text block about hearing damage, 'What does hearing loss sound like?' (with a sound wave icon), a list of links: 'Centres for disease control and prevention' and 'Hear the world', and buttons for 'What is safe listening?' and 'OK, thanks. Play my music'. + +H.870(18)\_F11-4 + +**Figure 11-4 – Examples of screens linking to information on safe listening and external links** + +### 11.2.3 Information through means other than the device itself: + +#### 11.2.3.1 User manual + +The user manual shall clearly state that unsafe listening practices with the use of the device pose the risk of permanent hearing loss. + +It should also give details of the volume-limiting functions and cues for action. + +The user manual should also clearly outline how the allowance-assessment system works and refer to its uncertainty. + +The manual should clearly indicate that information on the device does not take into account additional sources of sound exposures either from other audio devices or environmental sound exposure. + +The manual could also provide information regarding hearing protections from loud environmental sounds, in order to minimize the risk of hearing loss. + +#### **11.2.3.2 Packaging** + +It is highly recommended that a message/warning be included on or in the external packaging of the devices. It is recommended that such a warning/message be: + +- concise, simple and clear +- accompanied by a relevant illustration +- positioned on a plain background. + +#### **11.2.3.3 Website and advertising** + +Information on safe listening should be included on the manufacturer's website/s (e.g., supporting the device interface information, see clause 11.2.1). + +Text contained on the manufacturer's website must be evidence-based and aligned to the recommendations of the WHO/ITU safe listening standards. A link to the WHO website and other relevant, reputable websites could be included. + +Wherever possible, advertising of products could also provide relevant information. Such information can refer to both the potential harm to hearing through improper use of their device and the advantages of listening safely in order to maintain healthy hearing while enjoying a good listening experience. + +# **12 Ambient noise control** + +Given that the listening level is tightly related to the level of the ambient noise (for example, see Figure 9 in [b-Portnuff]), the use of earphones that provide some degree of attenuation of the ambient noise leads users to choose reduced listening levels, hence diminish the overall noise exposure. This attenuation of ambient noise can be done through passive means or by involving active noise control that provides an electronic cancellation of the ambient noise [b-Berger-Voix]. + +## **12.1 Passive attenuation of the background noise** + +A first approach to limit the ambient noise during music listening consists in merging the features of the earphone with the noise isolation provided by a passive hearing protection device. Such earphones can be large around-the ear headphones where a hard shell and the soft cushion will ensure a proper attenuation of ambient noise. It can also come as in-ear earphones that use roll-down foam earplug tips, pre-moulded tips, or even custom moulded tips to provide a substantial amount of attenuation when properly fitted in the ear canal [b-Smith-Voix]. These products simply utilize passive attenuation and are sometimes referred to as noise-isolating headset/earphones. Their proper attenuation of ambient sounds requires a tight fit between the tip of the earphones and the wearer's ear canal, that cannot be achieved with the ubiquitous "button receiver", see intra-concha earphone in [ITU-T P.57], that only seats in the concha or at the entrance of the ear canal and does not provide any substantial attenuation. + +## 12.2 Active noise reduction of background noise + +Some earphones featuring active noise reduction (ANR) have been commercialized over the last decades as around or over-the-ear headphones as well as in-ear earphones. These ANR devices use an analogue or digital controller to generate a sound wave that is of the same magnitude but opposite phase as the initial disturbance (the ambient noise). They can quite effectively cancel or reduce the background noise in the area of the user's eardrum. + +## 12.3 Benefits of noise-isolating earphones + +The main auditory benefit of using noise isolating earphones, assuming they are properly fitted, is that they enable the wearer to lower the listening level to a safer value, as the ambient noise is partially reduced as shown in Figure 9 of [b-Portnuff] (see also [b-Voix,Cocq,Hager]). However, the proper fit of in-ear noise-isolating earphones can be difficult to achieve in the first place and/or to maintain consistently over time. Slight changes in the fit of noise-isolating earphones not only affect the amount of attenuation that these devices provide, but also affect the frequency response of the earphones and dramatically increase the uncertainty associated with the sound pressure level delivered in the occluded ear canal. This latter effect is particularly pronounced with passive in-ear earphones that rely on a perfectly sealed ear canal for superior noise isolation and optimal frequency response. + +## 12.4 Safety concerns associated with noise-isolating earphones + +Isolating earphones need to provide a high attenuation in order to be effective at reducing the ambient noise. This can also raise some concerns regarding the safety of using such isolating devices in day-to-day activities, not to mention the distraction induced by music listening itself. Indeed, noise-isolating earphones, when properly fitted, may reduce ambient noises to very low levels that may be harder to perceive. That combined with the fact that the music being played back will further mask the residual ambient noise, it is easy to understand that the auditory situational awareness will be compromised. Ambient noise with useful information, such as a person calling or a car honking, will be lost and the detection, recognition and identification of all hazardous sound sources will be compromised. Besides, the localization of the source in azimuth and elevation, as well as estimation of distance, speed and direction capabilities can all be impacted by the use of noise isolating earphones. + +For this reason, it is recommended that manufacturers warn the users of the risks faced when using the PAS and accompanying earphones/headphones during activities where auditory cues can be crucial (street jogging, car driving, etc.) and where the loss of such cues could potentially endanger their physical safety. + +# 13 Volume control + +## 13.1 Volume limiting + +The device or system shall provide the user with a suitable method for volume-limiting. This refers to a feature which provides a message relative to a predetermined reference exposure (sound allowance) limit and when this message is unacknowledged, the device or system shall automatically reduce the volume of the device to achieve a sound level at the DRP, with diffuse-field correction, no greater than 80 or 75 dBA (according to the mode selected). It is further recommended that this should be set as the default option and that the user should have the option of turning this feature off if they do not wish to use this setting. + +When this is implemented, a volume limiting option message shall be automatically provided when the user reaches 100% of the weekly allowance. The user shall be given a message, which will allow them the option to "continue listening" in case they do not wish the device volume to reduce. When the message is not acknowledged, the default action will be to reduce the volume to achieve + +the predetermined sound level. If possible, the users should be given the option to customize this level (the level at which they would like their device to limit the volume) according to their preference. + +## **13.2 Password-protected volume control** + +The device or system shall have the option whereby the maximum sound output can be fixed and locked in the settings, possibly through the use of a password. + +The intent of this feature is to allow parents (or other adults) to limit the maximum sound output of the child's device, in a way that cannot be changed by the child. + +The feature may also be used by individual users in order to limit their own sound exposure, if they wish to do so, by fixing the maximum output on their device. + +## **14 Guidance on ancillary concerns** + +In addition to the direct effect of the transducer and the playing device in PAS themselves, there are several points that may need to be taken into account when a PAS is deemed safe. [b-ITU-T P.360] has some information in this regard. + +- When a headphone or an earphone is connected, there may be an acute noise (clicks and pops) due to transients (undesirable noise) in the system. +- Certain devices, when connected or "paired" together, give off a "confirmation-sound" to indicate that the devices are successfully paired. In such a case, the sound level of the confirmation sound may need to be in the safe range. + +Note that this cannot be measured by a "dosimeter" on a PAD. + +# Appendix I + +## Status report + +(This appendix does not form an integral part of this Recommendation.) + +WHO estimates that currently over 1.5 billion people worldwide experience some degree of hearing loss, nearly 30% of which is disabling hearing loss. It is estimated that with the current demographic trends, by 2050, there could be over 2.5 billion people with hearing loss globally. While this upward trend reflects changes in population demographics, it also underlines the need to address the preventable causes of hearing loss. + +One of the main avoidable causes of hearing loss is termed as noise-induced hearing loss, which refers to hearing loss due to overexposure of ears to sound energy, including music listened to over personal audio devices and systems. WHO estimates that 1.1 billion people between 12 to 35 years of age are at risk of hearing loss due to unsafe listening practices. This makes it an issue of imminent public health concern, especially since even now, unaddressed hearing loss poses an annual global cost of USD 980 billion. + +Responding to the request of its Member States in the World Health Assembly resolution WHA70.13, WHO is working with other stakeholders to mitigate the risk of hearing loss due to unsafe listening by raising awareness and promoting safe listening behaviours. Making this change requires that users of personal audio devices or systems should be able to access devices/systems that include safe listening features. + +To this end, WHO, with help from ITU, conducted a gap-analysis of standards related to safe listening. The results are found in the report at: + +[https://cdn.who.int/media/docs/default-source/documents/health-topics/deafness-and-hearing-loss/monograph\\_on\\_situation\\_analysis\\_and\\_background\\_for\\_standards\\_for\\_safe\\_listening\\_systems.pdf?sfvrsn=336b9823\\_5](https://cdn.who.int/media/docs/default-source/documents/health-topics/deafness-and-hearing-loss/monograph_on_situation_analysis_and_background_for_standards_for_safe_listening_systems.pdf?sfvrsn=336b9823_5). + +Other related background documents on the "Making Listening Safe" initiative can be found at , with an overview at [https://itu.int/en/ITU-T/studygroups/2017-2020/16/Documents/Safe\\_listening\\_initiative\\_background\\_201804.docx](https://itu.int/en/ITU-T/studygroups/2017-2020/16/Documents/Safe_listening_initiative_background_201804.docx). + +Following the launch of version 1 of this standard, few business entities have implemented some of its recommendations, which are providing essential information on and options for safe listening to their users. The second version of this standard will ensure its applicability to a wider range of devices and offer more safe listening features to people, in an effort to promote safe listening and mitigate the growing risk of hearing loss globally. + +# Appendix II + +## Dose estimation functionality for implementation in a personal audio system + +(This appendix does not form an integral part of this Recommendation.) + +## II.1 Introduction + +This appendix describes an example of how a dosimeter can be implemented in a personal audio system (PAS) when measuring the digital media signal and considering known or assumed properties of headphones. It is based on the equal energy principle in hearing impairment risk assessments, where the squared A-weighted sound pressure, integrated over the exposure time, constitutes the dose. + +The uncertainties involved in such dose estimations (e.g., confidence interval) are also discussed. + +## II.2 Main related standards + +[EN 50332-3] describes a dose measurement system in a personal media player (PMP) and this appendix is intended only as supplementary information to that standard. + +[IEC 61252] describes acoustic dosimeters to be worn on the body. + +## II.3 Definition of dose in the context of acoustic dosimetry + +$$dose = \int_{t_1}^{t_2} (p_A(t))^2 dt$$ + +where $p_A$ is the A-weighted and diffuse-field corrected sound pressure. + +For example, the dose acquired when being subjected to 80 dBSPL, exposure duration of 40 h is calculated as follows: + +- The RMS sound pressure is $10^{\frac{80}{20}} \cdot \frac{20\mu Pa}{1Pa} = 0.2 Pa$ . Accordingly, the dose is $0.2^2 \cdot 40 = 1.6 Pa^2 h$ . + +Such a specific dose may be defined as a reference dose and the measured exposure estimation during a certain period may be expressed as a percentage of this reference dose. [EN 50332-3] defines the dose explained above as a 100% CSD. Furthermore, it considers only the dose acquired during a rolling 7 days. + +## II.4 Weighting of different frequencies + +The potential hearing damage of interest for the dose estimation occurs in the cochlea in the inner ear, see Figure II.1 for reference. It would be intuitive that measurements were corrected to reflect directly the excitation of the hair cells in the cochlea. However, the vast majority of research on noise-induced hearing loss is based on sound level meter readings in the "free field" in e.g., factories (strictly speaking typically something between free field and diffuse field conditions). Therefore, risk assessment and action limits are based on such readings. Although the A-weighting was not developed specifically for hearing loss risk assessment, research has shown that sound level meter readings in the free field correlate reasonably well with observed noise-induced hearing loss, when the squared A-weighted sound pressure is integrated over the exposure time. + +![Figure II.1: Conceptual view of the roles of the different corrections used in measurements. The diagram shows a linear flow: Sound sources → Room → Body and outer ear → Eardrum → Middle ear → Inner ear. Above the flow, a curved arrow labeled 'DRP to diffuse-field correction' points from the Inner ear back to the Room. Below the flow, a long arrow labeled 'A-weighting' spans from the Room to the Inner ear. The label H.870(18)_FII.1 is at the bottom right.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +Figure II.1: Conceptual view of the roles of the different corrections used in measurements. The diagram shows a linear flow: Sound sources → Room → Body and outer ear → Eardrum → Middle ear → Inner ear. Above the flow, a curved arrow labeled 'DRP to diffuse-field correction' points from the Inner ear back to the Room. Below the flow, a long arrow labeled 'A-weighting' spans from the Room to the Inner ear. The label H.870(18)\_FII.1 is at the bottom right. + +**Figure II.1 – Conceptual view of the roles of the different corrections used in measurements, to give certain weightings to various frequencies** + +When the earphone/headphone/headset characteristics are measured at the eardrum reference point (DRP) using a head and torso simulator, the diffuse-field correction transforms the measurement to a quantity comparable with typical sound level meter readings in the free/diffuse field. Since the original research included sound sources from a variety of incidence angles to the workers' ears, no specific incidence angle (e.g., free-field correction for frontal incidence at an elevation of 0 degrees) is assumed in the risk estimation, rather the diffuse-field correction is used, as an average representation of various incidence angles. + +Figure II.2 shows A-weighting and DRP to diffuse-field weighting. + +![Figure II.2: A graph comparing A-weighting and DRP to diffuse-field weighting. The y-axis is [dB] from -60 to 10. The x-axis is [Hz] on a logarithmic scale from 10^2 to 10^4. The blue line represents A-weighting, which peaks around 1-2 kHz. The yellow line represents DRP to diffuse-field weighting, which is relatively flat between 100 Hz and 10 kHz, with some dips. The label H.870(18)_FII.2 is at the bottom right.](5bf611979ab0126ebd219a1c6eda6b1e_img.jpg) + +Figure II.2: A graph comparing A-weighting and DRP to diffuse-field weighting. The y-axis is [dB] from -60 to 10. The x-axis is [Hz] on a logarithmic scale from 10^2 to 10^4. The blue line represents A-weighting, which peaks around 1-2 kHz. The yellow line represents DRP to diffuse-field weighting, which is relatively flat between 100 Hz and 10 kHz, with some dips. The label H.870(18)\_FII.2 is at the bottom right. + +**Figure II.2 – A-weighting [IEC 60268-1] and DRP to diffuse-field correction/weighting [ITU-T P.58]** + +## II.5 Signal capture point in a personal audio system (PAS) + +Figure II.3 contains an example of an audio player system and preferred dosimeter capture point where the measured signal $x$ is collected just before digital-to-analogue conversion. + +Since $p_A$ is typically not readily available, it is shown here how to estimate $p_A$ based on a digital signal in the player (PAD, personal audio device, which does not have a transducer) and other known or assumed characteristics of PAD and headphones. + +Table II.1 describes the quantities needed for dose estimation. + +![Block diagram of an audio player system showing the signal flow from multiple Media sources through Effects, summation, Vol ctrl, Effects, DAC, Headphones, DRP to DF, and A-weight to produce the preferred dosimeter capture point p_A. Below the diagram, labels S_DAC, S_EA(f), and A(f) are shown with arrows pointing to the corresponding blocks.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +H.870(18)\_FII.3 + +Block diagram of an audio player system showing the signal flow from multiple Media sources through Effects, summation, Vol ctrl, Effects, DAC, Headphones, DRP to DF, and A-weight to produce the preferred dosimeter capture point p\_A. Below the diagram, labels S\_DAC, S\_EA(f), and A(f) are shown with arrows pointing to the corresponding blocks. + +**Figure II.3 – Example of audio player system and preferred dosimeter capture point** + +**Table II.1 – Quantities needed for dose estimation** + +| Quantity | Description | Unit | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| $x_L$ and $x_R$ | Digital signals for the left and right channels, taken in the PAS audio system after the summation of all audio sources, after volume control and after all audio processing. | sample value | +| $S_{DAC}$ | Sensitivity of the digital-to-analogue converter and subsequent analogue circuitry. In case the headset has a digital input, this parameter is attributed to the headset rather than the player. | Volt/sample value | +| $S_{EA}(f)$ | Electro-acoustic sensitivity of the headphones, measured at the eardrum reference point (DRP) and then corrected using DRP to diffuse-field correction for the frequency range 20 to 20 kHz. See [ITU-T P.381] for the measurement method of headset receiving frequency response, [ITU-T P.58] for diffuse-field correction and [ITU-T P.380] for additional information such as five times re-seating and averaging. | Pascal/Volt | +| $A(f)$ | A-weighting filter network, see [IEC 61672-1] for a general specification and [IEC 61252] for a dosimeter design goal. | Volt/Volt | +| $T$ | Duration of the segment. | Hours | + +## II.6 Handling of left and right channels + +For simplicity, and based on some measurements, in implementation and interpretation of results, the power average of the left and right channels is used for a single dose estimation (see [b-SG16-R17]). + +## II.7 Dosimeter implementation example + +For a discrete time, segment-based implementation, the estimation of a daily/weekly dose can be implemented accordingly, in time or frequency domain: + +- Acquire $n$ samples per channel of the signal $x$ , (typically over a 1 second time window). Filter the signal to consider DAC, headphone and A-weighting. + +$$z(k) = filter(x(k), [S_{DAC} \cdot S_{EA}(f) \cdot A(f)])$$ + +- Calculate the mean power of the left and right channels and multiply by the duration of the segment. + +$$\underline{dose_{segment}} = T \cdot \frac{1}{n} \sum_{k=1}^n \frac{1}{2} (z(k)_L^2 + z(k)_R^2)$$ + +- Add the dose contribution to the previously accumulated dose estimate. + +$$\underline{dose_m} = \underline{dose_{m-1}} + \underline{dose_{segment}}$$ + +- (Optional): Present the dose reading for the present day and the previous 6 days. + +- 5) (Optional): Express the total dose as a percentage of the reference dose. +- 6) If midnight has passed: store the dose for the concluded day, reset the daily dose to zero and measure for the new day. + +NOTE – The storage of the cumulating dose shall have sufficient accuracy to avoid nulling small portions from a single segment. + +## II.8 Handling of computational complexity + +To save calculation resources and increase battery time, the signals may be decimated (without anti-aliasing filters). Care shall be taken that the accuracy remains sufficient, for music and speech signals. Care shall also be taken that the filtering remains appropriate, for the decimated signal. + +Filtering implementations may be simplified to a certain extent. + +## II.9 Handling of dose over days and weeks + +It is recommended to store each day's dose estimate during a rolling 7-day period. The accumulated dose during the present day and the six previous days is compared to the reference dose explained in clause II.3. + +Figure II.4 shows an example of accumulation of dose over 7 days, constituting in total $1.6 \text{ Pa}^2\text{h}$ , hence 100% calculated sound dose. + +![Bar chart showing the accumulation of dose over 7 days. The y-axis is labeled [Pa²h] and ranges from 0 to 0.6. The x-axis is labeled Day and ranges from 1 to 7. The bars show the following approximate values: Day 1: 0.08, Day 2: 0.4, Day 3: 0.1, Day 4: 0.5, Day 5: 0.05, Day 6: 0.15, Day 7: 0.35. The total dose is 1.6 Pa²h.](30ffebf544a71997b61e5f4be3d321ef_img.jpg) + +| Day | Dose ( $\text{Pa}^2\text{h}$ ) | +|--------------|--------------------------------| +| 1 | 0.08 | +| 2 | 0.4 | +| 3 | 0.1 | +| 4 | 0.5 | +| 5 | 0.05 | +| 6 | 0.15 | +| 7 | 0.35 | +| Total | 1.6 | + +Bar chart showing the accumulation of dose over 7 days. The y-axis is labeled [Pa²h] and ranges from 0 to 0.6. The x-axis is labeled Day and ranges from 1 to 7. The bars show the following approximate values: Day 1: 0.08, Day 2: 0.4, Day 3: 0.1, Day 4: 0.5, Day 5: 0.05, Day 6: 0.15, Day 7: 0.35. The total dose is 1.6 Pa²h. + +H.870(18)\_FII.4 + +**Figure II.4 – Example of accumulation of dose over 7 days, constituting in total $1.6 \text{ Pa}^2\text{h}$ , hence 100% CSD** + +## II.10 Case of unknown headphone characteristics + +In many cases, the headphone type may not be known to the player and its sensitivity can vary significantly, as illustrated in Figure II.5. In such a case, the dosimeter assumes: + +- maximum permitted headphone sensitivity, meaning a simulated programme signal characteristic voltage (SPCV) of 75 mV, see [EN 50332-2] and [ITU-T P.381]; +- flat frequency response after diffuse-field correction; +- headset impedance $32 \Omega$ (relevant when identifying $S_{DAC}$ ). + +This means that $S_{EA}(f)$ is set to a constant of 12.55 Pascal/Volt. + +![Figure II.5: Earphone Rx response comparison on HATS. A line graph showing dB SPL (Y-axis, 20 to 90) versus Frequency (X-axis, 10 to 100,000 Hz) for nine different earphones and headphones. The legend identifies the curves: Insert 1 (green), Insert 2 (blue), Intraconcha 1 (orange), Intraconcha 2 (grey), Supraaural 2 (yellow), Circumaural 1 (dark blue), Circumaural 2 (light blue), and Supraaural 1 (pink). The graph shows significant variability in sensitivity across the frequency range, with some models peaking around 80 dB SPL and others dropping below 30 dB SPL at higher frequencies.](24b549c0c4b79c515b244625cf4f4978_img.jpg) + +Figure II.5: Earphone Rx response comparison on HATS. A line graph showing dB SPL (Y-axis, 20 to 90) versus Frequency (X-axis, 10 to 100,000 Hz) for nine different earphones and headphones. The legend identifies the curves: Insert 1 (green), Insert 2 (blue), Intraconcha 1 (orange), Intraconcha 2 (grey), Supraaural 2 (yellow), Circumaural 1 (dark blue), Circumaural 2 (light blue), and Supraaural 1 (pink). The graph shows significant variability in sensitivity across the frequency range, with some models peaking around 80 dB SPL and others dropping below 30 dB SPL at higher frequencies. + +**Figure II.5 – Illustration on the variability of sensitivity for nine headphones and earphones** + +Table II.2 shows headset characteristics at maximum permitted sensitivity according to [EN 50332-2], in 1/3-octave bands. + +**Table II.2 – Illustration of headset characteristics at maximum permitted sensitivity** + +| Programme simulation noise | | | Headset response | | | A-weighting | | | A-weighted acoustic | | | +|----------------------------------|-----------|-----------------------|-------------------------------------------------------------|----------|--------|---------------|--------|-----------|---------------------|--------|--------------------| +| IEC 60268-1 (adjusted for 75 mV) | | | Flat DF-corrected response
    SPCV = 75 mV;
    [EN 50332-2] | | | [IEC 61672-1] | | | [EN 50332-1] | | | +| [Hz] | PSM [dBV] | PSM [V 2 ] | [Hz] | [dBPa/V] | [Pa/V] | [Hz] | [dB] | [gain] | [Hz] | [dBPa] | [Pa 2 ] | +| 20 | -48.56 | 1.39E-05 | 20 | 25.10 | 12.55 | 20 | -50.40 | -2.52E+01 | 20 | -73.85 | 4.12E-08 | +| 25 | -45.26 | 2.98E-05 | 25 | 25.10 | 12.55 | 25 | -44.82 | -2.24E+01 | 25 | -64.98 | 3.18E-07 | +| 31.5 | -42.46 | 5.68E-05 | 31.5 | 25.10 | 12.55 | 31.5 | -39.53 | -1.98E+01 | 31.5 | -56.89 | 2.05E-06 | +| 40 | -40.26 | 9.43E-05 | 40 | 25.10 | 12.55 | 40 | -34.54 | -1.73E+01 | 40 | -49.70 | 1.07E-05 | +| 50 | -38.56 | 1.39E-04 | 50 | 25.10 | 12.55 | 50 | -30.28 | -1.51E+01 | 50 | -43.73 | 4.24E-05 | +| 63 | -37.36 | 1.84E-04 | 63 | 25.10 | 12.55 | 63 | -26.22 | -1.31E+01 | 63 | -38.48 | 1.42E-04 | +| 80 | -36.46 | 2.26E-04 | 80 | 25.10 | 12.55 | 80 | -22.40 | -1.12E+01 | 80 | -33.75 | 4.21E-04 | +| 100 | -35.96 | 2.54E-04 | 100 | 25.10 | 12.55 | 100 | -19.15 | -9.57E+00 | 100 | -30.00 | 1.00E-03 | +| 125 | -35.56 | 2.78E-04 | 125 | 25.10 | 12.55 | 125 | -16.19 | -8.10E+00 | 125 | -26.65 | 2.16E-03 | +| 160 | -35.26 | 2.98E-04 | 160 | 25.10 | 12.55 | 160 | -13.25 | -6.62E+00 | 160 | -23.40 | 4.57E-03 | +| 200 | -35.16 | 3.05E-04 | 200 | 25.10 | 12.55 | 200 | -10.85 | -5.42E+00 | 200 | -20.90 | 8.12E-03 | +| 250 | -35.06 | 3.12E-04 | 250 | 25.10 | 12.55 | 250 | -8.68 | -4.34E+00 | 250 | -18.63 | 1.37E-02 | +| 315 | -35.06 | 3.12E-04 | 315 | 25.10 | 12.55 | 315 | -6.64 | -3.32E+00 | 315 | -16.60 | 2.19E-02 | + +**Table II.2 – Illustration of headset characteristics at maximum permitted sensitivity** + +| Programme simulation noise | | | Headset response | | | A-weighting | | | A-weighted acoustic | | | +|----------------------------------|-------------------------|-----------------------|-------------------------------------------------------------|----------|--------|---------------|-------|-----------|---------------------|--------------------------|--------------------| +| IEC 60268-1 (adjusted for 75 mV) | | | Flat DF-corrected response
    SPCV = 75 mV;
    [EN 50332-2] | | | [IEC 61672-1] | | | [EN 50332-1] | | | +| [Hz] | PSM [dBV] | PSM [V 2 ] | [Hz] | [dBPa/V] | [Pa/V] | [Hz] | [dB] | [gain] | [Hz] | [dBPa] | [Pa 2 ] | +| 400 | -35.06 | 3.12E-04 | 400 | 25.10 | 12.55 | 400 | -4.77 | -2.39E+00 | 400 | -14.73 | 3.37E-02 | +| 500 | -35.06 | 3.12E-04 | 500 | 25.10 | 12.55 | 500 | -3.25 | -1.62E+00 | 500 | -13.20 | 4.78E-02 | +| 630 | -35.06 | 3.12E-04 | 630 | 25.10 | 12.55 | 630 | -1.91 | -9.54E-01 | 630 | -11.86 | 6.51E-02 | +| 800 | -35.06 | 3.12E-04 | 800 | 25.10 | 12.55 | 800 | -0.79 | -3.97E-01 | 800 | -10.75 | 8.41E-02 | +| 1000 | -35.16 | 3.05E-04 | 1000 | 25.10 | 12.55 | 1000 | 0.00 | 0.00E+00 | 1000 | -10.06 | 9.87E-02 | +| 1250 | -35.36 | 2.91E-04 | 1250 | 25.10 | 12.55 | 1250 | 0.58 | 2.88E-01 | 1250 | -9.68 | 1.08E-01 | +| 1600 | -35.66 | 2.72E-04 | 1600 | 25.10 | 12.55 | 1600 | 0.99 | 4.97E-01 | 1600 | -9.56 | 1.11E-01 | +| 2000 | -36.06 | 2.48E-04 | 2000 | 25.10 | 12.55 | 2000 | 1.20 | 6.01E-01 | 2000 | -9.75 | 1.06E-01 | +| 2500 | -36.66 | 2.16E-04 | 2500 | 25.10 | 12.55 | 2500 | 1.27 | 6.36E-01 | 2500 | -10.28 | 9.37E-02 | +| 3150 | -37.56 | 1.76E-04 | 3150 | 25.10 | 12.55 | 3150 | 1.20 | 6.01E-01 | 3150 | -11.25 | 7.49E-02 | +| 4000 | -38.76 | 1.33E-04 | 4000 | 25.10 | 12.55 | 4000 | 0.96 | 4.82E-01 | 4000 | -12.69 | 5.38E-02 | +| 5000 | -40.16 | 9.65E-05 | 5000 | 25.10 | 12.55 | 5000 | 0.56 | 2.78E-01 | 5000 | -14.50 | 3.55E-02 | +| 6300 | -42.06 | 6.23E-05 | 6300 | 25.10 | 12.55 | 6300 | -0.11 | -5.70E-02 | 6300 | -17.07 | 1.96E-02 | +| 8000 | -44.46 | 3.58E-05 | 8000 | 25.10 | 12.55 | 8000 | -1.14 | -5.72E-01 | 8000 | -20.50 | 8.91E-03 | +| 10000 | -46.96 | 2.02E-05 | 10000 | 25.10 | 12.55 | 10000 | -2.49 | -1.24E+00 | 10000 | -24.34 | 3.68E-03 | +| 12500 | -49.86 | 1.03E-05 | 12500 | 25.10 | 12.55 | 12500 | -4.25 | -2.12E+00 | 12500 | -29.01 | 1.26E-03 | +| 16000 | -53.26 | 4.72E-06 | 16000 | 25.10 | 12.55 | 16000 | -6.70 | -3.35E+00 | 16000 | -34.86 | 3.27E-04 | +| 20000 | -56.66 | 2.16E-06 | 20000 | 25.10 | 12.55 | 20000 | -9.34 | -4.67E+00 | 20000 | -40.90 | 8.13E-05 | +| | | | | | | | | | | | | +| | total [V 2 ] | 5.63E-03 | | | | | | | | total [Pa 2 ] | 9.97E-01 | +| | total [V] | 7.50E-02 | | | | | | | | total [Pa] | 9.99E-01 | +| | | | | | | | | | | total dBSPL | 9.40E+01 | + +NOTE – An [IEC 60268-1] programme simulation noise signal of 75 mV generates a sound pressure level of 94 dBSPL(A). + +## II.11 Alternative audio signal capture point + +When the implementation shown in Figure II.3 is not feasible, a simplified dosimeter may be implemented as follows. + +In case the signal is captured at a point further from the output of the device (e.g., inside a specific media application which can access only its own media stream), the influence of the downstream digital audio system such as volume control and sound effects have to be accounted for by a best-effort approach. The system identification of $S_{PAD}$ across volume control settings, may have to be performed at multiple content levels, to account for possible non-linear processing. + +Figure II.6 shows an example of a player audio system in the case where the signal $y$ is captured inside a specific media source application. + +![Block diagram of an audio system showing multiple media sources, effects, volume control, DAC, headphones, and weighting functions.](f57c7b37d7a05a99618104f390089f03_img.jpg) + +The diagram illustrates an audio system architecture. On the left, multiple 'Media' blocks are shown, each followed by an 'Effects' block. The outputs of these 'Effects' blocks are summed at a central node marked with a '+' sign. Below the second 'Media' block, there is a signal 'y' entering an 'Effects' block. The summed signal then passes through a 'Vol ctrl' (Volume control) block, followed by another 'Effects' block, a 'DAC' (Digital-to-Analog Converter) block, and 'Headphones'. Below the 'Headphones' block, the signal is labeled $S_{EA}(f)$ . The signal then passes through a 'DRP to DF' (Dynamic Range Processing to Frequency) block, and finally an 'A-weight' block, which outputs the final signal $\bar{p}_A$ . Below the 'A-weight' block, the signal is labeled $A(f)$ . A long horizontal arrow at the bottom, spanning from the first 'Media' block to the 'DRP to DF' block, is labeled $S_{PAC}(f, vol, level)$ . In the bottom right corner, the text 'H.870(18)\_FII.6' is present. + +Block diagram of an audio system showing multiple media sources, effects, volume control, DAC, headphones, and weighting functions. + +NOTE – The influence of volume control and sound effects have to be accounted for by a best-effort approach. The characteristics of the player are functions of frequency, volume control setting and potentially the level of the content. + +**Figure II.6 – Example of player audio system in cases where the signal $y$ is captured inside a specific media source application** + +Refer to clause 8.1.3. + +## II.13 Uncertainties + +Refer to clause 7.2. + +# Appendix III + +## European Standard EN 71-1 for toys + +(This appendix does not form an integral part of this Recommendation.) + +European Standard [b-EN 71-1] clause 4.20 "Acoustics" specifies requirements that are also applicable to tape players, CD players and other similar electronic toys when they are provided with headphones or earphones. In particular: + +"... a) The A-weighted emission sound pressure level, $L_{pA}$ , produced by *close-to-the-ear toys* shall not exceed 80 dB when measured in a free field. The A-weighted emission sound pressure level, $L_{pA}$ , produced by *close-to-the-ear toys* shall not exceed 90 dB when measured using an ear coupler. + +... e) The C-weighted peak emission sound pressure level, $L_{pC}$ peak, produced by any type of toy excluding toys using percussion caps shall not exceed 115 dB. + +... f) If the C-weighted peak emission sound pressure level, $L_{pC}$ peak, produced by a toy exceeds 110 dB, the potential danger to hearing shall be drawn to the attention of the user by a warning (see 7.14)." + +NOTE – Clause 8.28 of [b-EN 71-1] specifies the method to be used for determination of emission sound pressure level in toys. + +Clause 7.14 of [b-EN 71-1] "Acoustics" prescribes that toys which produce high impulse sound levels, or their packaging shall carry the following warning: "*Warning. Do not use close to the ear! Misuse may cause damage to hearing.*" + +Clause A.25 of [b-EN 71-1] "Acoustics" alerts that "the sensitivity of children to loud noise is basically unknown. However, there are scientists who hold the opinion that since the auditory canal in children is smaller than in adults, there is a different amplification which makes children more sensitive to high-frequency sounds. Impulse sounds are especially hazardous since it is very difficult for the human ear to determine the sound levels due to the very short time factor. It is a fact that permanent damage to hearing may occur after only one exposure to high peak sound levels." + +# Appendix IV + +## **"Music" versus "noise"** + +(This appendix does not form an integral part of this Recommendation.) + +The following is taken from [b-Neitzel and Fligor]: + +Lindgren and Axelsson (Lindgren and Axelsson 1983) examined 10 subjects in a study of temporary threshold shift (TTS) resulting from exposures to non-musical noise and found that these exposures resulted in TTS severity that exceeded those from musical noise of the same duration and overall A-weighted sound pressure level. Four of the subjects experienced essentially the same TTS from both sources, while six experienced greater TTS from the non-musical exposure than from the musical exposure. This provides some evidence that the content of sound and the resulting subjective perceptions of exposure may affect the risk of TTS. In a separate study, Axelsson and Lindgren (Axelsson and Lindgren 1981) documented TTS effects among musicians that were less than those of audience members. + +Strasser, Erle, and Legler (Strasser et al. 2003) also studied 10 subjects over three energetically equivalent exposures to music and non-music sound over three days. Classical music (2 h exposure, mean 91 dBA) was found to be associated with substantially less TTS (10 dB vs. 25 dB) compared to industrial noise of the same duration and mean level, as well as an energetically equivalent industrial level (94 dB for 1 h) and which recovered much faster (100 min vs. 800 min). As with the Lindgren and Axelsson study, this study suggests that the content of sound may affect the risk of TTS. + +Strasser, Irle, and Scholz (Strasser et al. 1999) examined four energetically similar exposures (94 dB for 1 hr): white noise, industrial noise, heavy metal music and classical music. Industrial noise and heavy metal music were found to induce a similar amount of TTS and to require similar durations of time to recover (i.e., restitution time). However, classical music was found to result in less TTS and shorter restitution times than industrial noise, heavy metal music, or white noise. As with the previous studies, this study highlights potentially different consequences of exposure to classical music than to other types of music and industrial noise. + +Mostafapour 1998 (Mostafapour et al. 1998) prospectively examined hearing loss among 50 university student subjects (mean age 22.1 years). They compared noise exposures (assessed via self-reported participation in a number of occupational and non-occupational events, as well as firearms use) to observed degree of hearing loss. The authors noted no association between qualitative exposure to any of the assessed sources of noise and presence of a noise notch (determined via pure tone audiometry), and determined that there was low risk of NIHL among the subjects. + +Finally, Swanson et al (Swanson et al. 1987) exposed 20 male subjects to music and noise of approximately equivalent energy (about 106 dBA) and for the same 10-min duration. Both exposures resulted in a significant post-exposure audiometric TTS at 4 and 6 kHz. TTS was significantly greater from music exposures among subjects who reported disliking the music used in the experiment. This study further supports the notion that subjective factors related to music may influence the risk of hearing loss resulting from music exposure, though it should be noted that audiometric testing involves a cognitive element that could conceivably be negatively influenced/biased by fatigue, loss of motivation, or frustration. + +# Appendix V + +## On stapedius muscle reflex + +(This appendix does not form an integral part of this Recommendation.) + +Stapedius muscle reflex (SMR), also known as acoustic middle ear reflex, is the process in which the stapedius and tensor tympani muscles of the ossicles contract when the ear is exposed to high intensity sound. This reflex has been extensively studied [b-Moller 1995]. Contraction of the stapedius muscle reduces sound transmission through the middle ear. It is believed, therefore, that this mechanism is in place, among other things, in order to decrease the transmission of vibrational energy to the cochlea. The threshold of the human acoustic middle ear reflex is approximately 85 dB above the normal hearing threshold though there are considerable individual variations. [b-Moller 2013]. + +# Appendix VI + +## Consideration of recovery phase + +(This appendix does not form an integral part of this Recommendation.) + +There is an accumulation phase and there is a recovery phase in the auditory system. The current dosimetry for an occupational setting does not take this into account. There are cases where sleeping quarters are not quiet (ships), in that case the sleeping is not considered "quiet" and the details are for future study. More information is needed. + +Acoustic trauma is a single exposure to sound resulting in immediate injury to the auditory system. It is sometimes called sound injury. + +Generally, the threshold level for acoustic trauma is accepted as 200 Pa or 140 dB SPL (peak). The literature suggests that in highly susceptible individuals, this threshold might be as low as 79.6 Pa or 132 dB SPL (peak) [b-Price 1981]. + +Sound-induced auditory injury is known to follow a dose-effect relationship. Sound "overdose" results in metabolic overload, leading to apoptosis of structures in cochlea and primary auditory nerve fibres. + +Well established damage risk criteria in workplace noise exposure studies show that: + +- 85 dBA for 8-hour daily exposure, 40-hr weekly exposure over working lifetime (5.06 Pa2h) (8% at risk for "material hearing impairment"); +- 90 dBA for 8-hour daily exposure, 40-hr weekly exposure over working lifetime (16 Pa2h) (25% at risk for "material hearing impairment"). + +Single-number level limiting ignores well-established science. + +[b-Nixon-Glorig 1961] demonstrates that, after two years of exposure, permanent hearing loss starts to develop at 4 kHz for the group exposed to 92 dBA and already after four months for the group exposed to 97 dBA. Figure VI.1 adapted from [b-Nixon-Glorig 1961] shows noise-induced permanent threshold shifts (NIPTS) plotted against years of occupational exposure to noise for workers at three levels of noise. These threshold shifts have been corrected for the changes with age found in persons without occupational exposure to noise. The graphs are for a test tone of 4 kHz and the data points are medians. The average A-weighted sound levels were 83 dB for group A, 92 dB for group B and 97 dB for group C. + +![A line graph showing Noise-induced permanent threshold shifts (NIPTS) in DB at 4 KC on the y-axis (0 to 50) against Exposure time in years on a logarithmic x-axis (1 to 100). Three data series, A, B, and C, are plotted. Series C (triangles) shows the highest NIPTS, reaching approximately 45-50 dB. Series B (circles) reaches approximately 25-30 dB. Series A (circles) shows the lowest NIPTS, reaching approximately 10-15 dB. All series show an initial increase in NIPTS with exposure time, followed by a plateau.](103781b498cc6846ffc11a041e14dc3e_img.jpg) + +| Exposure time in years | NIPTS in DB at 4 KC (Series A) | NIPTS in DB at 4 KC (Series B) | NIPTS in DB at 4 KC (Series C) | +|------------------------|--------------------------------|--------------------------------|--------------------------------| +| 1 | 0 | 0 | 15 | +| 2 | 2 | 2 | 28 | +| 5 | 5 | 23 | 45 | +| 10 | 11 | 27 | 48 | +| 20 | 12 | 28 | 45 | +| 30 | 11 | 27 | 45 | +| 40 | 10 | 27 | 42 | +| 50 | 11 | 27 | 42 | + +A line graph showing Noise-induced permanent threshold shifts (NIPTS) in DB at 4 KC on the y-axis (0 to 50) against Exposure time in years on a logarithmic x-axis (1 to 100). Three data series, A, B, and C, are plotted. Series C (triangles) shows the highest NIPTS, reaching approximately 45-50 dB. Series B (circles) reaches approximately 25-30 dB. Series A (circles) shows the lowest NIPTS, reaching approximately 10-15 dB. All series show an initial increase in NIPTS with exposure time, followed by a plateau. + +**Figure VI.1 – Noise-induced permanent threshold shifts (NIPTS) plotted against years of occupational exposure to noise for workers at three levels of noise** + +# Appendix VII + +## Example of health communication + +(This appendix does not form an integral part of this Recommendation.) + +## VII.1 Recommendations to develop warnings and cues for action messages for device interfaces + +The messages should be developed in consideration of the factors mentioned above. Messages should aim to gain attention, build interest and encourage users to practice safe listening. They should share actionable information, provide viable alternative behaviours and facilitate safe listening practices. + +Points to consider while developing such messages/cues are (see examples in clause VII.4): + +- They should clearly convey the benefits of safe listening and the risks of not doing so. +- There should be 3-4 variations of each message that can convey the information in a non-repetitive manner, designed to address a wide audience. +- Texts should use plain and clear language that is jargon-free and written below the 8th grade level to ensure that they can be understood by the majority of users. +- Some messages should be positively and others negatively worded (refer to clause VII.4.3 for examples). +- Written information should be complemented by pictorial information for ease of understanding. +- The messages shall be based on recommendations from a credible source. +- Wherever possible, the messages should be pre-tested by the manufacturer before use. + +## VII.2 Suggested flow (an example) of information as part of standards for safe listening devices + +Figure VII.1 contains a suggested flow (an example) that aims to explain how the communication aspects of this Recommendation can be implemented within the devices. + +![Flowchart showing the flow of information as part of standards for safe listening devices. The flow starts with Packaging, followed by User manual, Device interface, First use, Personal usage, Notifications, and Daily alerts. Each stage has associated requirements for information delivery.](cbb2d311b20781a595488445ded48d0a_img.jpg) + +``` + +graph TD + Packaging --> User_manual + User_manual --> Device_interface + Device_interface --> First_use + First_use --> Personal_usage + Personal_usage --> Notifications + Notifications --> Daily_alerts + +``` + +**Packaging** + +- A clear, concise message/warning included on the external packaging of the devices, wherever possible. +- Message should appear on a plain background and be short, simple, and clear, with a relevant illustration. + +**User manual** + +- The manual should clearly state that unsafe listening practices of the device may pose the risk of permanent hearing loss. +- It should indicate that the device is equipped with safety features to help users protect their hearing +- This message should align with the information provided through the device interface. It should contain similar texts regarding the risks of hearing loss from unsafe listening and the recommendations for safe listening. +- It should also detail the safe listening features within the device. + +**Device interface** + +- A visible icon on the device screen will direct users to the general information on safe listening. +- This icon will also lead the user to a display (in devices with screens) which provides information regarding individuals' listening parameters and (daily and weekly) usage statistics. + +**First use** + +- The first use of ear/headphones with the device should direct the user to a tutorial with information on safe listening, how to practise it, and their personal listening profile (same information as available through the icon). +- It will describe the standard levels for adults and children and allow the user to select a level. +- User will be given the option to set up how often and at what levels of usage they wish to receive the notifications. + +**Personal usage** + +- The information on the daily/weekly sound allowance consumption is available to users at any time through the distinctive icon above mentioned +- Calculation should include all sounds played through the music players or online, so long as ear/headphones are used. +- The displayed information should include: weekly allowance used and remaining; listening time (for the day/week), and indicate how the user's listening has been for the past 7 days, including current day, where possible. + +**Notifications** + +- Warnings and cues for action shall be delivered every time the user reaches 100% of the allowance exposure levels and also as per settings customized by the user. +- These should be visual (where possible) and audible/vibratory to ensure that the user's attention be directed towards these. +- The notifications should include information on the level of audio usage and the corresponding recommendations for safe listening (see clause VII.4.1 for examples). + +**Daily alerts** + +- Each day the first time a user connects to ear/headphones or starts playing music, the device could give a welcome message based on the usage on the previous days/week (see clause VII.4.2 for examples). + +Flowchart showing the flow of information as part of standards for safe listening devices. The flow starts with Packaging, followed by User manual, Device interface, First use, Personal usage, Notifications, and Daily alerts. Each stage has associated requirements for information delivery. + +H.870(18)\_FVII.1 + +**Figure VII.1 – Flow of information as part of standards for safe listening devices** + +## **VII.3 Example of how the information on listening parameters can be conveyed to the user** + +Through a clearly recognisable icon, users should be able to access a "dedicated space (screen)" on the device where information on the user's listening habits is stored, visualized and interpreted. In this space, the user will access a graphic representation of his/her overall listening habits or patterns and learn if (and what type of) unsafe listening practices have occurred. The visualization of the user's listening habits will include: + +- graphic display of the use of weekly sound allowance; +- graphic display of daily sound exposure through a colour-coded display; +- duration of listening, over each day and the past 7 days in hours and minutes. + +### **VII.3.1 Information on use of weekly allowance** + +Use of weekly allowance can be graphically conveyed as illustrated in Figure VII.2. + +![Figure VII.2: A 3D pie chart showing 60% Used (red) and 40% Remaining (green). Text to the right: Listening time (for last seven days): 4 hours 20 minutes. Source: H.870(18)_FVII.2](35135a8841884b7bb6fa58c3d9665c13_img.jpg) + +Listening time (for last seven days): +4 hours 20 minutes + +H.870(18)\_FVII.2 + +Figure VII.2: A 3D pie chart showing 60% Used (red) and 40% Remaining (green). Text to the right: Listening time (for last seven days): 4 hours 20 minutes. Source: H.870(18)\_FVII.2 + +**Figure VII.2 – Illustration of how graphically conveying the use of a weekly allowance** + +### **VII.3.2 Information on how the user has used the allowance on any day** + +For the purpose of this display, the maximum daily allowance will be equal to weekly allowance divided by 7 (approx. 15% of the weekly allowance). + +Usage for the last 7 days (including the present day) would be indicated by a range of colours depicting different levels of usage, e.g., deep red for over 100% use and green when use is below 50%. + +For the purpose of this communication, each day would be considered as a separate unit and colour coding for the day would not take the previous days' exposure into account. Hence, the user would start with green icon each day, irrespective of the usage pattern over past days. + +### **VII.3.3 Listening time** + +Information on the overall time the user spent listening to audio content through the device each day, will also be displayed as shown in Figure VII.3. + +![Figure VII.3: A timeline showing daily listening times from Date-6 to Date (today) with corresponding color-coded circles. A color scale at the bottom ranges from Safe (green) to Unsafe (red). Source: H.870(18)_FVII.3](e046996962d6740cf050a5640e0c6b40_img.jpg) + +| Date-6 | Date-5 | Date-4 | Date-3 | Date-2 | Date-1 | Date (today) | +|--------|--------|--------|--------|--------|--------|--------------| +| 1h05m | 1h20m | 2h01m | 1h50m | 2h05m | 3h02m | 2h50m | + +H.870(18)\_FVII.3 + +Figure VII.3: A timeline showing daily listening times from Date-6 to Date (today) with corresponding color-coded circles. A color scale at the bottom ranges from Safe (green) to Unsafe (red). Source: H.870(18)\_FVII.3 + +**Figure VII.3 – Information on the overall daily time the user spent listening to audio content** + +## **VII.4 Warnings and cues for actions** + +This clause provides some examples of warnings and cues for action for the safe listening features. + +### **VII.4.1 Examples of warnings and cues based on weekly use** + +Information when user reaches: + +- a) 80% of weekly allowance: friendly warning message + - *You have already spent **80%** of your allowance. Turn down the volume to protect your hearing.* + - *Reduce volume/Stop listening/Ignore warning/ go to personal usage information* + OR + +- *Hello! It looks like you have been playing a lot of loud music lately. Why don't you take a short break to protect your hearing.* + - *Reduce volume/Stop listening/Ignore warning/ go to personal usage information* +- b) 100% of weekly allowance: warning message (with an option to pause listening immediately) +- *You are now **OVER 100%** of your safe listening allowance. Unsafe listening poses a risk to your hearing.* + - *Reduce volume/Stop listening/Ignore warning/ go to personal usage information* +- OR +- *Hey! You have played too much loud music recently. Take a break and protect your hearing.* + - *Reduce volume/Stop listening/Ignore warning/ go to personal usage information* + +Unless the user accepts to 'ignore warning' or to 'pause listening', the default will reduce the volume to achieve a pre-specified moderate sound level (equivalent to 80 or 75 dBA). + +### VII.4.2 Examples of messages based on daily use + +Daily message (when opening the app or at player page) which should be based on the user's use of sound allowance over the last few days: + +- a) Mostly in green (where the user stays below 50% weekly usage most days, not exceeding the allowance on any day): encouraging messages +- *Good job. This is the way to listen well* +- OR +- *Good job! Keep playing music safely for endless fun.* + - *Well done. Keep listening safely and have endless fun.* +- b) Mostly green or yellow/orange (where the user stays below 80% on most days, not exceeding the allowance on any day): +- *Be careful and listen safely.* + - *Hey! It seems that sometimes you enjoy high volume! Be careful and protect your hearing for endless fun!* + - *You can listen safely for longer by lowering the volume.* +- c) Mostly yellow/orange with occasional red (where the user is not exceeding the allowance on any day): +- *Be careful! Keep the volume down to listen safely for longer* + - *Hey! It seems that sometimes you enjoy loud music! Be careful and protect your hearing for endless fun!* + - *Hey! You should watch how you listen.* +- d) Mostly red (exceeding the allowance on most days): +- *You are putting your hearing at risk. Keep the volume low to listen safely* + - *Hey! You need to watch how you listen. Turn it down.* + - *Hey! It seems that you enjoy really loud music! Don't put your hearing at risk and have endless fun.* + +### VII.4.3 Examples of messages with positive versus negative frame; and emotional versus rational appeal + +##### Positive frame + +- **You exceeded your daily allowance for safe listening.** *Keeping the volume low lets you listen safely for longer without risk to hearing. Turn it down.* + +##### Negative frame + +- **You exceeded your daily allowance for safe listening.** *If you keep listening this way, you risk damaging your hearing forever. Turn it down.* + +##### Rational appeal + +- *The evidence says that if you listen to music above the 80 dBA SPL, for 8 hours or its equivalent, you might damage your hearing forever. Turn down the volume.* + +##### Emotional appeal + +- *Once you lose your hearing, it will not come back. Listen safely. Turn down the volume.* + +# Appendix VIII + +## Mechanism of hearing and impact of impact of sound + +(This appendix does not form an integral part of this Recommendation.) + +This clause gives background information for safe listening. + +## VIII.1 Sound and waves + +Sound is a wave in a medium, such as air, produced by a vibrating body. Waves transmit energy without transmitting matter. A sound wave is a longitudinal wave, i.e., the direction of motion that creates the wave is the same as the wave motion. Waves propagate in a medium by displacing differences in force or pressure from one place to another. In particular, the transmission or propagation of energy in the sound-conducting medium is in the form of alternate compressions and rarefactions of the medium. At a certain point in time, there are interleaving compressions and rarefactions in the medium, which in turn produce variations in pressure. When air is compressed, the pressure is higher than the atmospheric pressure and when it is rarefied, the pressure is lower. + +The magnitude of compression and rarefaction in the propagating medium determines the intensity of the sound, while how often the compressions and rarefactions alternate determines the frequency of the sound. Energy from the motion of sound waves flows through the eardrums and into the inner ear, where it registers as sound. Intensity $I$ is the energy $E$ per unit of time $t$ that is flowing across a surface of unit area $a$ , or $I$ is power flowing across the surface of area $a$ . + +A pure tone is a simple sound whose pressure variations are sinusoidal in form, which is called in acoustics as the sine wave. The sine waves are periodic. + +The speed of a sound wave depends on the nature of the sound-conducting medium. The speed of sound waves depends somewhat on the temperature of the air. At room temperature ( $20^{\circ}\text{C}$ ) the speed is 344 metres per second (m/s), corresponding to 1238 km/h. + +## VIII.2 Mechanism of hearing and hearing loss + +As shown in Figure VIII.1, the ear is comprised of three parts: the outer ear, the middle ear and the inner ear. The middle ear consists of the tympanic membrane (also called eardrum) that terminates the ear canal and three small bones (collectively called ossicles): the malleus, incus and stapes. Two small muscles, the tensor tympani muscle and stapedius muscle are also in the middle ear. The inner ear is the innermost part of the ear and consists of the cochlea, the vestibular apparatus and the vestibulocochlear nerve. "Sound" can be considered as a series of vibrations. These vibrations arrive at an ear and are captured by the pinna. Sound travels as a wave into the ear canal down to the eardrum, which vibrates and converts the wave into mechanical energy. The ear canal has a length of approximately 2.5 cm and a diameter of approximately 0.6 cm. The sound (or its mechanical energy) then passes through the ossicles in the middle ear cavity. + +![Anatomical diagram of the human ear showing the outer, middle, and inner ear with various structures labeled.](37290987e9d8f148b8a59c405e9c60d7_img.jpg) + +This diagram illustrates the anatomy of the human ear, divided into three main sections: the Outer ear, Middle ear, and Inner ear. The Outer ear includes the Pinna and Concha, leading into the External auditory canal (meatus). The Middle ear contains the Tympanic membrane and the Auditory ossicles (Malleus (hammer), Incus (anvil), and Stapes (stirrup)). The Inner ear features the Vestibular apparatus, Vestibulocochlear nerve, and Cochlea. A detailed inset on the right shows the ossicles in more detail, with labels for the Head and Footplate of the stapes, and the Oval and Round windows. The diagram is also labeled with 'Temporal bone' and 'Eustachian tube'. A small code 'H.870(22)\_FVIII.1' is visible in the bottom right corner. + +Anatomical diagram of the human ear showing the outer, middle, and inner ear with various structures labeled. + +H.870(22)\_FVIII.1 + +**Figure VIII.1 – Illustration of the human ear** + +These bones amplify the mechanical energy which is transferred to the inner ear through the oval window of the cochlea (inner ear). The stapes taps on the oval window causing vibration of the fluid in the inner ear and this movement passes through the fluid-filled cochlea. + +![Simplified anatomical diagram of the ear canal and internal structures.](c2462d2d2ea40cd436ba726b995d21f5_img.jpg) + +This simplified diagram shows the ear canal and internal structures. Labels include Pinna, Ear canal, Ossicles, Ear drum, Auditory nerve, Cochlea, and Eustachian tube. The diagram uses a color-coded system where red lines point to specific anatomical features. A small code 'H.870(22)\_FVIII.2' is visible in the bottom right corner. + +Simplified anatomical diagram of the ear canal and internal structures. + +H.870(22)\_FVIII.2 + +**Figure VIII.2 – Ear canal** + +![A detailed anatomical diagram of the human ear, showing the external, middle, and inner ear. The external ear includes the ear canal and eardrum (tympanum). The middle ear contains the ossicles: hammer (malleus), anvil (incus), and stirrup (stapes), and is filled with air. The inner ear is a snail-shaped cochlea containing perilymph and endolymph. It features the organ of Corti with cilia, a tectorial membrane, and auditory nerves. Other labeled parts include the oval window, round window, and Eustachian tube. A dashed line separates the middle ear from the inner ear.](ceb147a82430b08b7ffd0ea53313cc47_img.jpg) + +A detailed anatomical diagram of the human ear, showing the external, middle, and inner ear. The external ear includes the ear canal and eardrum (tympanum). The middle ear contains the ossicles: hammer (malleus), anvil (incus), and stirrup (stapes), and is filled with air. The inner ear is a snail-shaped cochlea containing perilymph and endolymph. It features the organ of Corti with cilia, a tectorial membrane, and auditory nerves. Other labeled parts include the oval window, round window, and Eustachian tube. A dashed line separates the middle ear from the inner ear. + +H.870(22)\_FVIII.3 + +**Figure VIII.3 – Illustration of the cochlea** + +As shown in Figure VIII.2 and Figure VIII.3, the cochlea is a snail shaped organ. In the cochlea, there are thousands of hair cells called basilar hairs. As the sound goes through the cochlea, it moves the fluid which moves the hair cells, sending electrical impulses up the auditory nerve to the brain. These electrical signals are then interpreted as sound. + +When overexposure to sound occurs, the hair cells in an ear become overstimulated. Once the hair cells are overstimulated, they become fatigued and stop responding to sound. This may result in temporary threshold shift (TTS), a temporary hearing loss following sound exposure, which can last a few minutes to a few days. After a period of quiet, the hair cells will recover. + +However, repeated exposure to excessive sound over time will kill these hair cells, and they lose their ability to recover. This can result in permanent threshold shift (PTS), sound-induced permanent loss of hearing sensitivity associated with irreversible cochlear hair cell damage. + +Figure VIII.4 shows the cochlea and the hair cells. + +![Illustration of the cochlea and hair cells. The left side shows a cross-section of the human ear with the cochlea highlighted. The right side shows a magnified view of the cochlea's interior, illustrating the hair cells. A single hair cell is shown in detail, with its stereocilia (hair-like projections) and a green rectangular body. The label H.870(22)_FVIII.4 is visible in the bottom right corner.](8e1263a63a8c36c001a0c913d7e7fcce_img.jpg) + +Illustration of the cochlea and hair cells. The left side shows a cross-section of the human ear with the cochlea highlighted. The right side shows a magnified view of the cochlea's interior, illustrating the hair cells. A single hair cell is shown in detail, with its stereocilia (hair-like projections) and a green rectangular body. The label H.870(22)\_FVIII.4 is visible in the bottom right corner. + +**Figure VIII.4 – Illustration of the cochlea and the hair cells** + +In Figure VIII.5, the hair cells of the cochlea on the left are of a person with normal hearing, and the one on the right shows the permanent damage overexposure to sound can cause. + +![Illustration of sound induced damage in hair cells. The top part shows three green rectangular hair cells with yellow stereocilia. The bottom part shows two magnified views of the cochlea's interior. The left view shows healthy hair cells, while the right view shows damaged hair cells that are bent or broken. A blue arrow points from the healthy view to the damaged view. The label H.870(22)_FVIII.5 is visible in the bottom right corner.](93fa4105c1d3c48fee6b3fd97b631387_img.jpg) + +Illustration of sound induced damage in hair cells. The top part shows three green rectangular hair cells with yellow stereocilia. The bottom part shows two magnified views of the cochlea's interior. The left view shows healthy hair cells, while the right view shows damaged hair cells that are bent or broken. A blue arrow points from the healthy view to the damaged view. The label H.870(22)\_FVIII.5 is visible in the bottom right corner. + +**Figure VIII.5 – Illustration of sound induced damage in hair cells** + +## **VIII.3 Measurement of sound energy** + +### **VIII.3.1 Pressure** + +Because of earth's gravity, the weight of the atmosphere exerts a pressure in all directions on everything, called atmospheric pressure. Its value is $10^5$ Newton/m2; that is, 105 Pascal (Pa). + +The displacement of a wave is the amount of disturbance from equilibrium produced by the wave. + +Peak-to-peak refers to the change between minimum and maximum values of a sinusoidal wave or signal. Figure VIII.6 shows the concept of peak-to-peak. + +![Figure VIII.6: Concepts of signal amplitude and peak to peak value. The diagram shows a sine wave on a horizontal axis. A vertical double-headed arrow from the axis to the first peak is labeled 'Amplitude'. Another vertical double-headed arrow from the first peak to the first trough is labeled 'Peak to peak'. The source code 'H.870(22)_FVIII.6' is visible at the bottom right of the diagram.](62039fd2a1ef7b03f84c0fe5d8911860_img.jpg) + +Figure VIII.6: Concepts of signal amplitude and peak to peak value. The diagram shows a sine wave on a horizontal axis. A vertical double-headed arrow from the axis to the first peak is labeled 'Amplitude'. Another vertical double-headed arrow from the first peak to the first trough is labeled 'Peak to peak'. The source code 'H.870(22)\_FVIII.6' is visible at the bottom right of the diagram. + +**Figure VIII.6 – Concepts of signal amplitude and peak to peak value** + +Amplitude of a sound wave is often calculated as root mean square (RMS) values. Root mean square is the square root of the mean (average) value of the squared function of the instantaneous values. The RMS value is computed by first squaring the waveform instantaneous values ( $s$ ), then finding the mean over a cycle ( $m$ ) and finally by taking the square root ( $r$ ). + +### VIII.3.2 Decibels + +Editor's note: move this explanation to an Appendix + +The 'bel' (symbol B) expresses the ratio of two values by the decimal logarithm of this ratio. This unit is not often used, having been replaced by the decibel (symbol dB) which is one-tenth of a bel. + +A logarithmic unit used to express the ratio of two values of a physical quantity. One of these values is often a standard reference value, in which case the decibel is used to express the level relative to that reference. The mathematical statement of this idea is + +$$L_2 - L_1 = \text{Log}10 \left( \frac{I_2}{I_1} \right)$$ + +The verbal translation is that the difference in levels, measured in decibels (dB), between sounds 2 and 1 is given by the common (base 10) logarithm of the ratio of the intensities. The factor of 10 is included to expand the scale. A review of the log function makes a few features of the level (decibel) scale apparent. Because $\log(1) = 0$ , if sounds 1 and 2 have the same intensity then the difference in their levels is 0. The function of the log scale is to transform ratios into differences. If $L_2$ is twice $L_1$ then $L_2 - L_1 = 3 \text{ dB}$ , no matter what the actual value of $L_2, L_1$ might be. That is because $\log(2) = 0.3$ [b-Hartmann]. + +#### VIII.3.2.2 dB SPL + +Although the decibel scale is a ratio scale in which a quantity is always compared with another quantity, it is common for individual sound levels to be expressed in decibels as though the measure were absolute. Sound pressure level is the logarithm, generally expressed in decibels, of the ratio of sound pressure $p$ and a reference pressure $p_{0A}$ , often $20 \mu\text{Pa}$ . Note that a factor of 20 is used when the ratio is between two sound pressures, rather than two sound intensities. + +$$SPL = 20 \left( \frac{p}{p_{0A}} \right)$$ + +#### VIII.3.2.3 dBA + +dBA is decibels of sound pressure level measured using the A-weighting network; a level frequency weighting intended to measure low-intensity sound (around 40 phon loudness level) but which has become commonly used also for measuring occupational and environmental sound exposures. + +Figure VIII.7 shows a conceptual view of the roles of the different corrections used in measurements, to give certain weightings to various frequencies. + +![Figure VIII.7: Conceptual view of the roles of the different corrections used in measurements, to give certain weightings to various frequencies. The diagram shows a flow from Sound sources to Room, Body and outer ear, Eardrum, Middle ear, and Inner ear. A large arrow labeled 'A-weighting' points from left to right across the bottom. A smaller arrow labeled 'DRP to diffuse-field correction' points from the top towards the 'Body and outer ear' block. The diagram is labeled H.870(22)_FVIII.7 at the bottom right.](fc02903382cebe6fc11e4c0d74b5313f_img.jpg) + +``` +graph LR; A[Sound sources] --> B[Room]; B --> C[Body and outer ear]; C --> D[Eardrum]; D --> E[Middle ear]; E --> F[Inner ear]; +``` + +Figure VIII.7: Conceptual view of the roles of the different corrections used in measurements, to give certain weightings to various frequencies. The diagram shows a flow from Sound sources to Room, Body and outer ear, Eardrum, Middle ear, and Inner ear. A large arrow labeled 'A-weighting' points from left to right across the bottom. A smaller arrow labeled 'DRP to diffuse-field correction' points from the top towards the 'Body and outer ear' block. The diagram is labeled H.870(22)\_FVIII.7 at the bottom right. + +**Figure VIII.7 – Conceptual view of the roles of the different corrections used in measurements, to give certain weightings to various frequencies** + +#### **VIII.3.2.4 dBFS** + +dB full scale is the signal level of a digital signal relative to its overload or maximum level. Different conventions exist. It is common to assign a digital representation of a full-scale sinusoidal the value of 0 dBFS RMS. The peak level can then reach +3.01 dBFS. In other cases, the RMS level of a digital full-scale square wave is assigned 0 dBFS RMS. The maximum peak level is then also 0 dBFS. For the latter cases, dBFS is equivalent to dBov. + +NOTE – Also known as dBov, dB relative to digital overload is the signal level of a digital signal relative to its overload or maximum level. See [ITU-T G.100.1]. + +#### **VIII.3.2.5 dBHL** + +dBHL is decibels of hearing level at a certain frequency; a level used to measure audiometric hearing threshold relative to a defined normal. + +As described in [ISO 226], the sensitivity of the human ear varies greatly depending on the frequency of the incoming sound. If, and if the volume is turned up in order to obtain enough loudness in the low-frequency range that is important for many genres of music, the ear may be exposed to excessive energy at the higher frequencies to which it is especially sensitive. + +Figure VIII.8 shows acoustics normal equal-loudness-level contours. + +![Figure VIII.8: Acoustics normal equal-loudness-level contours. The graph plots Sound pressure level [dB] on the y-axis (from -10 to 130) against Frequency [Hz] on a logarithmic x-axis (from 16 to 16000). It shows two sets of curves for equal loudness levels (20, 40, 60, 80, 100 phon) and a minimum level. The '2003 new' curves are shown as solid red lines, and the 'Previous' curves are shown as dashed blue lines. The new curves are generally higher than the previous ones, especially in the mid-frequency range. A legend indicates that the red lines are the 2003 new curves, which are neither the Robinson-Dadson old curves nor the Fletcher-Munson curves. The text 'New (red line) revised curves of ISO 226:2003' is at the top. The label 'H.870(22)_FVIII.8' is at the bottom right.](a8523d225a4e279ab9e02f3c28cfa36a_img.jpg) + +Figure VIII.8: Acoustics normal equal-loudness-level contours. The graph plots Sound pressure level [dB] on the y-axis (from -10 to 130) against Frequency [Hz] on a logarithmic x-axis (from 16 to 16000). It shows two sets of curves for equal loudness levels (20, 40, 60, 80, 100 phon) and a minimum level. The '2003 new' curves are shown as solid red lines, and the 'Previous' curves are shown as dashed blue lines. The new curves are generally higher than the previous ones, especially in the mid-frequency range. A legend indicates that the red lines are the 2003 new curves, which are neither the Robinson-Dadson old curves nor the Fletcher-Munson curves. The text 'New (red line) revised curves of ISO 226:2003' is at the top. The label 'H.870(22)\_FVIII.8' is at the bottom right. + +**Figure VIII.8 – Acoustics normal equal-loudness-level contours** + +## VIII.4 Equal energy principle + +The equal energy principle is the premise that the total effect of sound is proportional to the total amount of sound energy received by the ear, irrespective of the distribution of that energy in time. + +According to this principle, equal amounts of sound energy are expected to cause equal amounts of sound-induced permanent threshold shift regardless of the distribution of the energy over time. + +Based on this principle, a 'dose' of sound energy may be defined as the squared A-weighted sound pressure, $P_A$ , integrated over the exposure time $T = t_2 - t_1$ . + +Mathematically, this is expressed as: + +$$dose = \int_{t_1}^{t_2} (P_A(t))^2 dt$$ + +where $P_A$ is the A-weighted and diffuse-field corrected sound pressure. + +The unit of this value is Pascal squared hours, or $\text{Pa}^2\text{h}$ . + +# Bibliography + +- [b-ITU-T P.10] Recommendation ITU-T P.10/G.100 (2017), *Vocabulary for performance and quality of service*. +- [b-ITU-T P.360] Recommendation ITU-T P.360 (2006), *Efficiency of devices for preventing the occurrence of excessive acoustic pressure by telephone receivers and assessment of daily noise exposure of telephone users*. +- [b-ITU-T T.180] Recommendation ITU-T T.180 (1998), *Homogeneous access mechanism to communication services*. +- [b-ITU-R V.574] Recommendation ITU-R V.574 (2015), *Use of the decibel and the nepier in telecommunications*. +- [b-Berger] Berger, E.H. and Royster, L.H. (1996), *In search of meaningful measures of hearing protector effectiveness*. +- [b-Berger-Voix] Elliott H. Berger and Jérémie Voix (2018), *Hearing Protection Devices*, in *The Noise Manual*, 6th Edition, American Industrial Hygiene Association. +- [b-Blanco-Wetherill] A. Blanco and J. Wetherill (April 2019), Headphones Market Report Worldwide Outlook, Futuresource Consulting Ltd. +, pg. 11 & 22. +- [b-Borg] Erik Borg, Roland Nilsson, Gunnar Lidén. (1979), *Fatigue and recovery of the human acoustic stapedius reflex in industrial noise*, The Journal of the Acoustical Society of America Vol. 65, 846. +- [b-Brask] Torben Brask (1978), *The Noise Protection Effect of the Stapedius Reflex*, Acta Oto-Laryngologica Vol. 86, – Issue sup360. +- [b-Brask-2009] Torben Brask (2009), *The Noise Protection Effect of the Stapedius Reflex*, Acta Oto-Laryngologica Vol. 86, 1978 – Issue sup360. +- [b-Burns-1973] William Burns (1973), *Noise and Man*, J.B. Lippincott Company, ISBN 9780397580989, pp. 243-247. +- [b-Burns-Robinson] W. Burns and D.W. Robinson, (1970) *Hearing and Noise in Industry*, Her Majesty's Stationery Office, pp. 142-145. This full document can be found here: +- [b-EN 71-1] CEN EN 71-1:2014, *Safety of toys – Part 1: Mechanical and physical properties*. +- [b-2009/490/EC] European Commission, *Commission Decision of 23 June 2009 on the safety requirements to be met by European standards for personal music players pursuant to Directive 2001/95/EC of the European Parliament and of the Council* +- [b-Fligor] Brian J. Fligor, and Terri Ives. "Does Earphone Type Affect Risk for Recreational Noise-Induced Hearing Loss?" in *2006 Noise Induced Hearing Loss (NIHL) Children's Conference Proceedings*. +- [b-FSTP-SLD-UC] ITU Technical Paper (2022), *Gap analysis: Use cases of safe listening devices*. + + +- [b-Hammershøi] Hammershøi, D., & Møller, H. (2008), *Determination of noise immission from sound sources close to the ears*. Acustica United with Acta Acustica, 94 (1). +- [b-Hansen] C. Hansen (2006), *Occupational exposure to noise: evaluation, prevention and control – chapter 1 Fundamentals of acoustics*. [http://www.who.int/occupational\\_health/publications/occupnoise/en/](http://www.who.int/occupational_health/publications/occupnoise/en/) +- [b-Hartmann] William M. Hartmann. *Physical Description of Signals* in [b-Moore]. +- [b-Loy] Gareth Loy, *Musimathics*. MIT (2011) +- [b-Moller 1995] Henrik Möller (1995), *Transfer characteristics of headphones measured on human ears*, J. Audio Eng. Soc:43, pp. 203-217. +- [b-Moller 2013] Aage R. Moller, (2013) *Hearing*, 3rd ed. Plural Publishing. +- [b-Moore] Brian C.J. Moore (ed.) (1995) *Hearing*. Academic Press. +- [b-Neitzel and Fligor] R. Neitzel and B. Fligor (2019), *Risk of noise-induced hearing loss due to recreational sound: Review and recommendations*. The Journal of the Acoustical Society of America 146, 3911; +- [b-NIOSH] National Institute for Occupational Safety and Health. (1998). *Criteria for a recommended standard: Occupational noise exposure, revised criteria*. Pub. No. 98-126. +- [b-Nixon-Glorig, 1961] J.C. Nixon and A. Gorig (1961), *Noise-Induced Permanent Threshold Shift at 2000 cps and 4000 cps*, The Journal of the Acoustical Society of America, Vol.33, Issue 7, 904. +- [b-Portnuff] Portnuff C.D., Fligor B.J., Arehart K.H. (2011), *Teenage use of portable listening devices: a hazard to hearing?* Journal of the American Academy of Audiology. Nov-Dec; 22(10):663-77. +- [b-Price 1981] Price, G. R. (1981), *Implications of a Critical Level in the Ear for Assessment of Noise Hazard at High Intensities*, J. Acoust. Soc. Am. 69, 171-177. +- [b-SCENIHR] Scientific Committee on Emerging and Newly Identified Health Risks (2008), *Potential health risks of exposure to noise from personal music players and mobile phones including a music playing function*. European Commission. +- [b-SG16-R17] ITU-T Study Group 16, *Report of the fourth meeting of Study Group 16* (Geneva, 19-29 March 2019) – Working Party 2/16 (Multimedia e-services). +- [b-Silman] Shlomo Silman. (1984), *The Acoustic Reflex: Basic Principles and Clinical Applications*, Academic Press. +- [b-Smith-Voix] Jérémie Voix, Pegeen Smith, and Elliott H. Berger (2018), *Field Fit-Testing and Attenuation Measurement Procedures*, The Noise Manual, 6th Edition, American Industrial Hygiene Association. +- [b-SMR] Kei J. (2012), *Acoustic stapedial reflexes in healthy neonates—normative data and test-retest reliability*. J Am Acad Audiol. 23(1):46-56. +- [b-Vér] I. Vér, L. Beranek (2006), *Noise and Vibration Control Engineering*. + +- [b-Voix,Cocq,Hager] J. Voix, C. Le Cocq, and L. D. Hager (2008), *The Healthy Benefits of Isolating Earphones*, in Proceedings of Meetings on Acoustics, vol. 4, p. 050003. +- [b-WHO 2018] World Health Organization, *Deafness and hearing loss*, (visited 2022-06-01) +- [b-Zakrisson] John-Erik Zakrisson & Erik Borg. (1974), *Stapedius Reflex and Auditory Fatigue*, Journal of Audiology, Vol. 13, pp. 231-35. +- [b-Zakrisson] John-Erik Zakrisson. (1979), *The effect of the stapedius reflex on attenuation and poststimulatory auditory fatigue at different frequencies*. Acta Otolaryngol Suppl. 360:118-21. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.871-201907-I_PDF-E/raw.md b/marked/H/T-REC-H.871-201907-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..24785c669f322bd52e13b9c8a47f744053f40137 --- /dev/null +++ b/marked/H/T-REC-H.871-201907-I_PDF-E/raw.md @@ -0,0 +1,457 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**H.871** + +(07/2019) + +SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS + +E-health multimedia systems, services and applications – +Safe listening + +# --- **Safe listening guidelines for personal sound amplifiers** + +Recommendation ITU-T H.871 + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'.](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a stylized globe with a red lightning bolt striking across it. To the right of the globe, the text "ITU" is written in a bold, blue font, and below it, "International Telecommunication Union" is written in a smaller, blue font. + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'. + +# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | | +| General | H.200–H.219 | +| Transmission multiplexing and synchronization | H.220–H.229 | +| Systems aspects | H.230–H.239 | +| Communication procedures | H.240–H.259 | +| Coding of moving video | H.260–H.279 | +| Related systems aspects | H.280–H.299 | +| Systems and terminal equipment for audiovisual services | H.300–H.349 | +| Directory services architecture for audiovisual and multimedia services | H.350–H.359 | +| Quality of service architecture for audiovisual and multimedia services | H.360–H.369 | +| Telepresence, immersive environments, virtual and extended reality | H.420–H.439 | +| Supplementary services for multimedia | H.450–H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | | +| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509 | +| Mobility for H-Series multimedia systems and services | H.510–H.519 | +| Mobile multimedia collaboration applications and services | H.520–H.529 | +| Security for mobile multimedia systems and services | H.530–H.539 | +| Security for mobile multimedia collaboration applications and services | H.540–H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | | +| Architecture for vehicular gateways | H.550–H.559 | +| Vehicular gateway interfaces | H.560–H.569 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | | +| Broadband multimedia services over VDSL | H.610–H.619 | +| Advanced multimedia services and applications | H.620–H.629 | +| Ubiquitous sensor network applications and Internet of Things | H.640–H.649 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | | +| General aspects | H.700–H.719 | +| IPTV terminal devices | H.720–H.729 | +| IPTV middleware | H.730–H.739 | +| IPTV application event handling | H.740–H.749 | +| IPTV metadata | H.750–H.759 | +| IPTV multimedia application frameworks | H.760–H.769 | +| IPTV service discovery up to consumption | H.770–H.779 | +| Digital Signage | H.780–H.789 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | | +| Personal health systems | H.810–H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859 | +| Multimedia e-health data exchange services | H.860–H.869 | +| Safe listening | H.870–H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.871 + +# Safe listening guidelines for personal sound amplifiers + +## Summary + +Recommendation ITU-T H.871 complements ITU-T H.870 "Guidelines for safe listening devices/systems". Currently there is no international standard for personal sound amplifiers (PSAs). These devices, which are freely available to anyone, require this standard to ensure that these devices are safe for users and do not further damage users' hearing. + +PSAs are non-medical devices, intended for people with normal hearing and a) can have a design physically comparable to hearing aids, in which case they are called personal sound amplification products (PSAPs) or b) can also simply be an application on any smartphone or other device, in which case they are called personal sound amplification applications (PSAAs). + +As defined in ITU-T H.870, the sound exposure should be limited to an accumulated dose (100 % calculated sound dose (CSD)) over 7 days of in total $1.6 \text{ Pa}^2\text{h}$ which corresponds to 80 dBA for 40 hours to prevent noise-induced hearing loss. When the 100% CSD is reached, the sound level should suddenly drop, and the user will get a suggestion to lower the sound level, since the weekly sound listening dose is exceeded. + +When PSAPs and PSAAs do not have the capacity to measure CSD, the output level of the device needs to be permanently limited to 95 dBA, so that a user is unlikely to use the device at a level higher than 80 dBA, since the dynamic range of speech has a crest factor of 12 to 17 dB. + +The U.S. Food and Drug Administration has carried out considerable work on these devices and their work is referenced in this Recommendation. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T H.871 | 2019-07-29 | 16 | 11.1002/1000/13967 | + +## Keywords + +Hearing aid, hearing assistive technology, hearing enhancer, noise induced hearing loss, personal sound amplifier, personal sound amplifier app, personal sound amplifier product, safe listening, safe sound output, wearable personal amplifiers. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2019 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Introduction..... | 2 | +| 6.1 Characteristics of personal sound amplifiers..... | 3 | +| 6.2 Physical characteristics of personal sound amplifiers ..... | 4 | +| 7 Requirements for safe listening for personal sound amplifiers ..... | 5 | +| 8 Consumer information ..... | 6 | +| Appendix I Further information from practical testing..... | 7 | +| Appendix II Maximum Sound Output Level for Personal Sound Amplifiers ..... | 8 | +| Bibliography..... | 9 | + + + +# Recommendation ITU-T H.871 + +# Safe listening guidelines for personal sound amplifiers + +## 1 Scope + +This Recommendation describes safety requirements for personal sound amplifiers (PSAs), including both personal sound amplification products (PSAPs) and personal sound amplification apps (PSAAs) types, to protect people from further hearing loss. + +Currently there is no international standard for PSAs; a standard is needed to ensure that these devices, which are freely available to anyone, are safe for users and do not further damage users' hearing. + +[ITU-T H.870] provides safe listening standards but excludes PSAs. Therefore, this Recommendation follows the logic and concept of [ITU-T H.870] but is specifically intended for PSAs. + +This Recommendation provides characteristics of PSAs and suggests ways of informing consumers about the potential unacceptable noise levels when using these devices for prolonged periods of time. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T H.870] Recommendation ITU-T H.870 (2018), *Guidelines for safe listening devices/systems*. + +[EN 50332-3] EN 50332-3: 2017, *Sound system equipment: headphones and earphones associated with personal music players - Maximum sound pressure level measurement methodology - Part 3: Measurement method for sound dose management*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 calculated sound dose** [b-IEC 62368-1]: One week rolling estimate of sound exposure expressed in percent of the maximum considered safe. + +**3.1.2 hearing aid – hearing instrument** [b-IEC 60601-2-66]: Medical electrical equipment which picks up sound and delivers processed sound to the ear canal through air-conduction. A hearing instrument includes all detachable parts that are essential for the performance of its intended use. + +**3.1.3 personal audio system (PAS)** [ITU-T H.870]: A system of a personal audio device and a listening device. + +**3.1.4 sound dose** [ITU-T H.870]: The total quantity of sound received by the human ear during a specified period. The unit of (sound) dose is Pa2h. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 hearing assistive device:** Any wearable instrument or device designed for assisting a person's hearing ability. + +**3.2.2 personal sound amplifier (PSA):** A non-medical electronic device or software amplifying sounds picked up by a microphone, intended for people with normal hearing which can have a design physically comparable to a hearing aid or it can be an app on any smartphone or other device. + +**3.2.3 personal sound amplification app (PSAA):** A non-medical software amplifying sounds picked up by a microphone, intended for people with normal hearing designed as an app on any smartphone or other device. + +**3.2.4 personal sound amplification product (PSAP):** A non-medical electronic device amplifying sounds picked up by a microphone, intended for people with normal hearing with a design physically comparable to a hearing aid. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|------------------------------------------| +| ALD | Assistive Listening Device | +| App | Application | +| BTE | Behind the Ear | +| CSD | Calculated Sound Dose | +| DAC | Digital to Analogue Conversion | +| dBA | A-Weighted Decibels | +| dB SPL | Decibel Sound Pressure Level | +| FDA | U.S. Food and Drug Administration | +| HA | Hearing Aid | +| HAD | Hearing Assistive Device | +| ITE | In the Ear | +| PSA | Personal Sound Amplifier | +| PSAA | Personal Sound Amplification Application | +| PSAP | Personal Sound Amplification Product | +| RMS | Root Mean Square | + +## 5 Conventions + +None. + +# 6 Introduction + +At the World Health Assembly held on 30 May 2017, delegates of World Health Organization agreed to intensify action to prevent deafness and hearing loss. Some 360 million people across the world live with disabling hearing loss, a total that includes 32 million children and nearly 180 million older adults. Nearly 90% of people with hearing loss live in low- and middle-income countries which often lack resources and strategies to address hearing loss [b-WHA]. + +Personal sound amplifiers are non-medical devices which amplify sounds picked up by a microphone. This device is intended for people with normal hearing and can: a) have a design physically comparable to a hearing aid, in which case it is called personal sound amplification product (PSAP) or b) simply be an application (app) on any smartphone or other device, in which case it is called a personal sound amplification application (PSAA). In practice, it is frequently seen that people with (mild) hearing loss buy and use these devices as an alternative to hearing aids. + +Personal sound amplifiers are intended to be introduced in the ear to amplify environmental sounds for people with no hearing impairment. Examples of situations in which personal sound amplifiers are typically suggested for use include bird watching, listening to lectures, listening to a distant speaker or listening to soft sounds that would be difficult for normal hearing individuals to hear (e.g., distant conversations, conversations in noisy environments, theatre performances). + +Until recently, these devices consisted of portable amplifying systems, but with the advent of downloadable amplifying software, this category has broadened to include mobile and body-worn devices with amplifier apps. + +NOTE – As the original definition by the U.S. Food and Drug Administration (FDA) does not specify software as a PSAP, the definition in clause 3.2.4 is adopted in this Recommendation. + +The latest developments of these products, coupled with personal music players, are used to listen to sounds without any safety levels. For further information see Appendix I. + +## 6.1 Characteristics of personal sound amplifiers + +A PSA is typically a device with two transducers, one for audio input (microphone) and the other for audio output (loudspeaker), and which typically modifies, e.g., amplifies, the input sound. + +The main difference between personal audio systems, the topic of [ITU-T H.870], and PSAs, as illustrated in Figures 1 and 2, is that for the latter the input is not a pre-recorded audio file, but rather any live input signal in the environment that is picked up by the microphone(s) of the PSAs. Further, the majority of the currently available PSAs do not have the capacity to measure the weekly sound exposure dose. In Figure 2, the interface (IF) between the PSA device and the listening device may be within the same hardware. + +![Figure 1: Graphic presentation of a personal audio system. The diagram shows a 'Personal audio system' containing a 'Personal audio device' and a 'Listening device'. The 'Personal audio device' includes 'Multiple sources (Microphone excluded)', 'Effect', 'Volume control', and 'DAC'. The 'Listening device' includes a 'Transducer'. An 'IF' (Interface) connects the 'DAC' to the 'Transducer'.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +``` +graph LR + subgraph PAS [Personal audio system] + subgraph PAD [Personal audio device] + MS[Multiple sources +(Microphone excluded)] --> E1[Effect] + E1 --> VC[Volume control] + VC --> E2[Effect] + E2 --> DAC + end + subgraph LD [Listening device] + T[Transducer] + end + DAC -- IF --> T + end +``` + +Figure 1: Graphic presentation of a personal audio system. The diagram shows a 'Personal audio system' containing a 'Personal audio device' and a 'Listening device'. The 'Personal audio device' includes 'Multiple sources (Microphone excluded)', 'Effect', 'Volume control', and 'DAC'. The 'Listening device' includes a 'Transducer'. An 'IF' (Interface) connects the 'DAC' to the 'Transducer'. + +Figure 1 – Graphic presentation of a personal audio system + +![Block diagram of a personal sound amplifier (PSAP) showing signal flow from microphone to transducer via internal processing blocks (Effect, Volume control, DAC) and an interface (IF).](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the internal architecture of a personal sound amplifier. It is divided into two main components: a 'Personal amplifier device' and a 'Listening device'. Inside the 'Personal amplifier device', a 'Microphone signal' (green box) is processed through an 'Effect' block (cyan), then a 'Volume control' block (yellow), and another 'Effect' block (cyan). The signal then passes through a 'DAC' (yellow) block. An interface (IF) connects the 'DAC' to a 'Transducer' (yellow) inside the 'Listening device'. The entire system is labeled 'Personal sound amplifier' at the bottom. The code H.871(19)\_F02 is present in the bottom right corner. + +Block diagram of a personal sound amplifier (PSAP) showing signal flow from microphone to transducer via internal processing blocks (Effect, Volume control, DAC) and an interface (IF). + +**Figure 2 – Graphic presentation of a personal sound amplifier** + +## **6.2 Physical characteristics of personal sound amplifiers** + +PSAPs are typically worn around the ear, the organ for hearing. + +While there are other possible designs, two typical types include the behind the ear (BTE) type or the in the ear (ITE) type, as illustrated in Figures 3 and 4, respectively. + +![Photograph of a Behind-the-Ear (BTE) type PSAP with labels for its physical components: Microphone, Behind the ear housing, Battery compartment, Hook (on top of the ear shell), Cable (between hook and loudspeaker), Eartip (silicone – fits in the ear canal), and Loudspeaker.](61ce9760bffbecba8f5e63310be1ebec_img.jpg) + +This photograph shows a Behind-the-Ear (BTE) type PSAP. The device consists of a 'Behind the ear housing' (brown) that sits behind the ear, connected by a 'Cable (between hook and loudspeaker)' to an 'Eartip (silicone – fits in the ear canal)'. The 'Microphone' is located on the top of the housing, and the 'Battery compartment' is on the bottom. A 'Hook (on top of the ear shell)' secures the device. The 'Loudspeaker' is at the end of the eartip. The code H.871(19)\_F03 is visible in the bottom right corner. + +Photograph of a Behind-the-Ear (BTE) type PSAP with labels for its physical components: Microphone, Behind the ear housing, Battery compartment, Hook (on top of the ear shell), Cable (between hook and loudspeaker), Eartip (silicone – fits in the ear canal), and Loudspeaker. + +**Figure 3 – Example of a BTE-type PSAP** + +![Photograph of an In-The-Ear (ITE) type PSAP with labels for its physical components: Volume control, Microphone, Eartip (silicone – fits in the ear canal), and Housing (in the earshell).](f0d1b18586b17005ffd3fce23280b5a5_img.jpg) + +This photograph shows an In-The-Ear (ITE) type PSAP. The device is a compact 'Housing (in the earshell)' (brown) that fits directly into the ear canal. It features a 'Volume control' knob and a 'Microphone' on its side. An 'Eartip (silicone – fits in the ear canal)' is attached to the front. The code H.871(19)\_F04 is visible in the bottom right corner. + +Photograph of an In-The-Ear (ITE) type PSAP with labels for its physical components: Volume control, Microphone, Eartip (silicone – fits in the ear canal), and Housing (in the earshell). + +**Figure 4 – Example of an ITE-type PSAP** + +A PSAA is typically an app stored on a smart device, such as a smartphone, which provides sound amplification. Figure 5 illustrates a typical setup of a PSAA. + +![Diagram of an app in smart device-type PSAA. The diagram shows a smartphone containing a Microphone, an Analogue to digital converter, a Digital signal processor, a Digital to analogue converter, and an Amplifier App. The signal flow is: Acoustic input to Microphone, then to Analogue to digital converter (Analogue to Binary (Digital)), then to Digital signal processor, then to Digital to analogue converter (Binary (Digital) to Analogue), and finally to the Amplifier App. The output of the Amplifier App is connected to Wired or wireless connected headphones. The diagram is labeled H.871(19)_F05.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Diagram of an app in smart device-type PSAA. The diagram shows a smartphone containing a Microphone, an Analogue to digital converter, a Digital signal processor, a Digital to analogue converter, and an Amplifier App. The signal flow is: Acoustic input to Microphone, then to Analogue to digital converter (Analogue to Binary (Digital)), then to Digital signal processor, then to Digital to analogue converter (Binary (Digital) to Analogue), and finally to the Amplifier App. The output of the Amplifier App is connected to Wired or wireless connected headphones. The diagram is labeled H.871(19)\_F05. + +**Figure 5 – Diagram of an app in smart device-type PSAA** + +## 7 Requirements for safe listening for personal sound amplifiers + +It is recommended that PSAs follow the requirements listed below: + +- R1: It is required that weekly maximum sound dose needs to be less than 1.6 Pa2h, which corresponds to 80 dBA for 40 hours. For example, at 89 dBA, the exposure time shall be limited to 5 hours/week. For other exposure levels, a linear interpolation and extrapolation applies. Measurements taken of the dynamic range of sound should be accounted for and the reasonably foreseeable use of the products. [ITU-T H.870]. +- R2: When these devices do not have the capacity to measure weekly sound dose, the maximum output of the device needs to be permanently limited to 95 dBA; a user then is unlikely to use the device at a level higher than 80 dBA since the dynamic range of speech has a crest factor of 12 to 17 dB. +- R3: personal sound amplifiers need to provide adequate warnings in advertisements, user guides and packaging detailing the risks of further damaging the user's hearing as a result of using the device, and provide information to users showing how to avoid these risks. + +[EN 50332-3] defines 1.6 Pa2h (equivalent to 80 dBA Leq40) as the weekly sound allowance, i.e., a 100% calculated sound dose (CSD) acquired over a period of 7 days. + +In line with [ITU-T H.870], a PSA shall provide the user with warnings and cues for action when the user exceeds 100% of the weekly allowance. The requirements are provided in [ITU-T H.870] clause 11.2.1.2: + +- The user shall receive first a "warning" expressed through text, visuals, or other means indicating that a threshold has been reached and that from this point on, further listening at the same volume will pose a risk to their hearing. +- The warning shall be followed by a "cue for action" in which the user is offered the choice to either accept the risk of continued listening or protect their hearing. The "cue for action" should be linked to active options on the device such as: + - automatic safe volume option, by which the device automatically changes the volume to a safe volume level; + - direct access to volume settings; + - setup of default volume limits; + - remind later option; + +- ignore and continue option. +- If the user fails to take any action, the volume will automatically be reduced to below the standard level (80 or 75 dBA as selected). + +The details are for further study. + +## **8 Consumer information** + +All personal sound amplifiers advertising, user guides and packaging shall carry consumer information. The information is required to contain: + +- a description of the product as a PSA; +- a list and description of the safety features are built into the product; +- consumer advice related to hearing loss prevention; +- all of the information on packaging indicated in [ITU-T H.870]. + +The details are for further study. + +## Appendix I + +### Further information from practical testing + +(This appendix does not form an integral part of this Recommendation.) + +The position paper issued jointly by the European Association of Hearing Aid Professionals (AEA) and the European Federation of Hard of Hearing People (EFHOH) in 2015 [b-AEA/EFHOH PSAP] raises the question of safety levels for PSAP products that were tested; some that were tested presented 130.0 dB SPL maximum output level. This level is much louder than the 80 dBA at which the exposure time shall be limited to 40 hours/week according to the European Commission Decision (EC) No 490/2009 [b- EC/490/2009]. + +A total of the 27 devices were analysed according to the test specification in [b-IEC 60118-7]. They were measured to have a maximum power level (OSPL 90) of more than 120 dB SPL (significantly higher than the 85 dBSPL maximum safety level), with 23 of them showing a maximum power level of 125 dBSPL or more (8 devices had a maximum power level of 130 dB SPL or more). + +None of the products tested had a limitation on the maximum power output or the capacity to measure weekly sound exposure dose. + +## Appendix II + +## Maximum Sound Output Level for Personal Sound Amplifiers + +(This appendix does not form an integral part of this Recommendation.) + +Personal sound amplifiers include both PSAA and PSAPs. + +PSAPs are defined by the FDA as "*wearable electronic products that are intended to amplify sounds for people who are not hearing impaired*" [b-FDA-PSAP]. + +For PSAs, there is no known available international recommendation at this time. + +According to this Recommendation, the maximum output of PSAs should be set to 95 dBA, when these devices do not have the capacity to measure weekly sound dose. + +Hearing aids are typically limited in maximum output level, which is done by the hearing aid professional after a full assessment of a user's hearing functionality, to prevent further hearing loss [b-Safe Max Output]. + +As seen in Figure II.1, Johnson [b-Safe Max Output] recommends that the maximum sound output be limited to 90 dBSPL root mean square (RMS) level for persons with normal hearing. + +| An algebraic restatement of the regression equations holding expected PTS constant at 3.5 dB HL to show safe output SPL as a function of hearing loss. (source: Johnson 2017, table 1) | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| 4FAdB HL threshold | Safe Output SPL (overall dB) | +| 0 | 90 | +| 5 | 92 | +| 10 | 94 | +| 15 | 95 | +| 20 | 97 | +| 25 | 99 | +| ... | ... | + + + +| The relationship between 4FA dB HL threshold and the safe output SPL output expected from hearing aids fit to prescriptive settings alongside safe output SPL. (source: Johnson 2017, table 2) | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------------------| +| 4FAdB HL threshold | Output SPL (RMS level)* prescription | Safe Output SPL (RMS level)** | +| 0 | 83 | 90 | +| 5 | 85 | 92 | +| 10 | 88 | 94 | +| 15 | 90 | 95 | +| 20 | 92 | 97 | +| 25 | 94 | 99 | +| ... | ... | ... | + +\* for an 80 dB input level for compressive hearing aid amplification at prescription recommendations +\*\* for 3.5 dB HL Permanent Threshold Shift for an exposure of at least 8 hours + +**Figure II.1 – Tables presenting maximum sound output limit** + +Since personal sound amplifiers, when not used for recreation use, will mostly be used to understand speech in quiet and in background noise, the dynamic range or crest factor (the difference in dB between the instantaneous peak of a signal and its RMS value) of speech is essential. According to Chasin [b-CREST FACTOR 12], the crest factor for speech is 12 dB. [b-Safe Max Output], [b-IEC 60118-0] + +In section 7.4.3 of [b-IEC 60118-0], the reference test gain is set to 17 dB under the average maximum output of the hearing aid, to ensure that speech will not be distorted, which is also based on the dynamic range (or crest factor) of speech. + +Based on these findings, for PSAs that do not have the capacity to measure weekly sound dose, the maximum output of the device needs to be limited to 95 dBA. + +## Bibliography + +- [b-IEC 60118-0] IEC 60118-0:2015, *Electroacoustics – Hearing aids – Part 0: Measurement of the performance characteristics of hearing aids.* +- [b-IEC 60118-7] IEC 60118-7:2005, *Electroacoustics – Hearing aids – Part 7: Measurement of the performance characteristics of hearing aids for production, supply and delivery quality assurance purposes.* +- [b-IEC 60601-2-66] IEC 60601-2-66: 2015, *Medical electrical equipment – Part 2-66: Particular requirements for the basic safety and essential performance of hearing instruments and hearing instrument systems.* +- [b-IEC 62368-1] IEC 62368-1:2018, *Audio/video, information and communication technology equipment – Part 1: Safety requirements.* +- [b-AEA/EFHOH PSAP] AEA, EFHOH, *Paper on the potential risk of using "Personal Sound Amplification Products"*, December 2015. + +- [b-CREST FACTOR 12] Marshall Chasin, (2012), *Music and Hearing Aids – An Introduction, Trends in Amplification*, 16(3), pp. 136-139. +- [b-EC/490/2009] EC/490/2009, *Commission Decision of 23 June 2009 on the safety requirements to be met by European standards for personal music players pursuant to Directive 2001/95/EC of the European Parliament and of the Council (Text with EEA relevance).* + +- [b-FDA-PSAP] FDA (2013), *Regulatory Requirements for Hearing Aid Devices and Personal Sound Amplification Products – Draft Guidance for Industry and Food and Drug Administration Staff.* + +- [b-Safe Max Output] Earl E. Johnson (2017), *Safety limit warning levels for the avoidance of excessive sound amplification to protect against further hearing loss*, *International Journal of Audiology*, 56:11, pp. 829-836. +- [b-WHA] World Health Assembly, *Resolution on Hearing loss and Deafness.* +[http://apps.who.int/gb/ebwha/pdf\\_files/WHA70/A70\\_R13-en.pdf?ua=1&ua=1](http://apps.who.int/gb/ebwha/pdf_files/WHA70/A70_R13-en.pdf?ua=1&ua=1) + + + + + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/008b6e24fa6aef654a11223efed035dd_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/008b6e24fa6aef654a11223efed035dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec7a0333a38f5ecf81ea124ec84b9629d2c892d6 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/008b6e24fa6aef654a11223efed035dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e73d222b8fa5fbe077154bfcf3f2e390182b4aef56cc564d968aa3d8319b3678 +size 47338 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/19fd552435a80d0ffda518b710d16908_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/19fd552435a80d0ffda518b710d16908_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..399b9dbb0386e21e76be6970b5fb344077195a06 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/19fd552435a80d0ffda518b710d16908_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1086ec7fe8e43591ef905c1a8dce5dacff367c93c82255848b6086751926a101 +size 23378 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26a305af1f97840d1cb5c6e04b6d42b311f1be7e --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ae629e0ecbb7a950a704c298400644c559e45130e6e9a489424ab06a5424bc3 +size 44831 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/3fec67008a13a4bccaf6914c862b2e42_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/3fec67008a13a4bccaf6914c862b2e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a02e55043ff5e126791ce50801bd174db77aa6a --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/3fec67008a13a4bccaf6914c862b2e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6366210571d3bf151b575af7b4fb5d33f69d2b3b7869c87f43bae7004241a259 +size 36372 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/474827f04e18dc4a3b073e8785813a76_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/474827f04e18dc4a3b073e8785813a76_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3de744e3267ace09b66d88953fce427c7ae62807 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/474827f04e18dc4a3b073e8785813a76_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e09d35e262f7219c17d9553c719501b151e9fe6f25baad8ffe2d91c3d844e88 +size 20793 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/53d30aa4ecaa092477cb3ef6ec874bec_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/53d30aa4ecaa092477cb3ef6ec874bec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ada341db0511e5586e53c7964c30ffade1843dd2 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/53d30aa4ecaa092477cb3ef6ec874bec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53600b9b32ab3c612a1f7e0296bef0058a7249a4ff4a6a9ddc8cf2c5cbf324ca +size 135621 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/7119b28e39fa3784606bf8b8f44e4f9d_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/7119b28e39fa3784606bf8b8f44e4f9d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f33be195557dcefec7358a5d884a159652453740 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/7119b28e39fa3784606bf8b8f44e4f9d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ee06d3070f07269425cc56d8355dd4db93dc6c2c4141026c955fcff5f058462 +size 33720 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/7adda64806b35031fadb1fd5a227a9f8_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/7adda64806b35031fadb1fd5a227a9f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..718f1ce47c204e8cb79619911dd9b2d88123e788 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/7adda64806b35031fadb1fd5a227a9f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c275933c7fa841a8de5dede5597b428307ce2e621660ce0ee51e107a0fb744a +size 48428 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1dd2c8e07b3dbdaf7c7166b4bd74d60a3e5ef09 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b349b704b13588cfe224604cd083b934a646b61dc203f9df44f2e590045828a9 +size 78872 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/84cebc242b1af66723a02cdf67fc98c9_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/84cebc242b1af66723a02cdf67fc98c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef6a20186fa136f0e35393afb8045e31cac3abba --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/84cebc242b1af66723a02cdf67fc98c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a04a61d0cb5273408914ef94e030d6613e2d1a04fbc7356707eceaf2de92c65 +size 51692 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/953203b3208524d293d4a65c0569324c_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/953203b3208524d293d4a65c0569324c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d40349e2e69d96762c3d25d3cb4282627327527c --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/953203b3208524d293d4a65c0569324c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7d7303312f3ab8e5c18ed725b66e651d5c681e66c9bb860740ffae92013f625 +size 51197 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52360a9539d5714db191d108a4466a15671e87f9 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeeada272c2a3f6c07246546cb3211d1acedeeb3b6486c14c1e3aecb9353dad8 +size 44837 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/aa92b0cf694be554991b65dbd284f9d4_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/aa92b0cf694be554991b65dbd284f9d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3062ed79061950299cbd6d05b8a134471915cd9 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/aa92b0cf694be554991b65dbd284f9d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5574a1176e0da2e845b0df910307b977bf26f3692d9e7bff2f6da3084f485727 +size 52260 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/f3ce2d7158eb708e3487b8e35415db35_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/f3ce2d7158eb708e3487b8e35415db35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02a719e49f4cc5bcc24ae78ffc64ee9083fcd297 --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/f3ce2d7158eb708e3487b8e35415db35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fdf5aaf44ecff7744306b2157be85d471570a641c7b459ef38282c66fa575ba +size 43212 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/f88d85789030ae43f43d61fe4ac3e64e_img.jpg b/marked/H/T-REC-H.872-202410-I_PDF-E/f88d85789030ae43f43d61fe4ac3e64e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c32c04a1599fbfb1a26e9c5166bd5627ac518a0e --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/f88d85789030ae43f43d61fe4ac3e64e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f306491493d7b97f68dddb70da12a4afa7c140419c15079246e14cd6c5865113 +size 40171 diff --git a/marked/H/T-REC-H.872-202410-I_PDF-E/raw.md b/marked/H/T-REC-H.872-202410-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b68eebf3a432530681576586a8284ee5b9aa251f --- /dev/null +++ b/marked/H/T-REC-H.872-202410-I_PDF-E/raw.md @@ -0,0 +1,1289 @@ + + +# Recommendation**ITU-T H.872 (10/2024)** + +SERIES H: Audiovisual and multimedia systems + +E-health multimedia systems, services and applications – +Safe listening + +--- + +### **Safe listening for video gameplay and esports** + +![ITU logo](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T H-SERIES RECOMMENDATIONS + +## **Audiovisual and multimedia systems** + +| | | +|---------------------------------------------------------------------------------------------|--------------------| +| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100-H.199 | +| INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200-H.499 | +| MOBILITY AND COLLABORATION PROCEDURES | H.500-H.549 | +| VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) | H.550-H.599 | +| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES | H.600-H.699 | +| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV | H.700-H.799 | +| E-HEALTH MULTIMEDIA SYSTEMS, SERVICES AND APPLICATIONS | H.800-H.899 | +| Personal health systems | H.810-H.819 | +| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820-H.859 | +| Multimedia e-health data exchange services | H.860-H.869 | +| Safe listening | H.870-H.879 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T H.872 + +# Safe listening for video gameplay and esports + +## Summary + +Recommendation ITU-T H.872 is aimed at reducing the risk of hearing loss among video game players. It is aligned with the principles of sound levels, exposure measurement and communication outlined in Recommendation ITU-T H.870. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T H.872 | 2024-10-29 | 16 | 11.1002/1000/16190 | + +## Keywords + +Esports, safe listening, sound-induced hearing loss, video gameplay, video gaming. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-------|------------------------------------------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 5 | +| 4 | Abbreviations and acronyms ..... | 7 | +| 5 | Conventions ..... | 8 | +| 6 | Background..... | 8 | +| 6.1 | Safe listening introduction..... | 8 | +| 6.2 | Video gameplay device ..... | 9 | +| 6.3 | Video gameplay software (titles)..... | 10 | +| 7 | Damage risk criteria..... | 11 | +| 7.1 | Operational modes for video gameplay devices (VGD) ..... | 11 | +| 7.2 | Uncertainty in dose estimate ..... | 12 | +| 8 | Safe listening features for video gameplay devices..... | 13 | +| 8.1 | Dosimetry ..... | 13 | +| 8.2 | Dosimetry user interface..... | 13 | +| 8.3 | Volume control system..... | 14 | +| 8.4 | Headphone safety mode ..... | 15 | +| 9 | Safe listening features for video gameplay software..... | 15 | +| 9.1 | Safe listening warnings/messages ..... | 15 | +| 9.2 | Sound category and master volume controls..... | 16 | +| 9.3 | Title dependent safe listening features ..... | 16 | +| 9.4 | Headphone safety mode ..... | 18 | +| 10 | Textual health warnings..... | 18 | +| 10.1 | User guides and other written information..... | 18 | +| 10.2 | Safe listening feature information ..... | 19 | +| 11 | Guidance on ancillary concerns..... | 19 | +| | Appendix I – Status report ..... | 20 | +| | Appendix II – Information on implementing dosimetry ..... | 21 | +| II.1 | Dose estimation functionality for implementation in a video gameplay device..... | 21 | +| II.2 | Volume-limiting and messaging considerations ..... | 21 | +| | Appendix III – Example of safe listening warnings ..... | 24 | +| III.1 | Safe listening warnings: Example of a safe listening warning upon initial load of a video gameplay software title..... | 24 | +| III.2 | Safe listening warnings: Example of safe listening warning during gameplay..... | 24 | + +| | Page | +|-------------------------------------------------------------------------------------------------|------| +| III.3 Safe listening warnings: Example of safe listening warning upon exit of the game..... | 25 | +| Appendix IV – Examples of textual information provided to the user ..... | 27 | +| IV.1 Textual information provided with video gameplay devices ..... | 27 | +| IV.2 Safe listening feature information examples for within video gameplay software titles..... | 30 | +| Appendix V – Safe listening for live esports venues and events ..... | 32 | +| V.1 Live esports event background ..... | 32 | +| V.2 Main features for live esports events ..... | 32 | +| Bibliography..... | 34 | + +# Introduction + +Globally, over one billion people are at risk of hearing loss due to unsafe listening in recreational settings. To address this, the World Health Organization (WHO) launched the *Make Listening Safe* initiative aimed to promote safe listening and reduce hearing loss. + +Amongst the outputs of this initiative was the WHO/ITU H.870 standard for safe listening devices and systems. This standard aims to promote safe listening and minimize the risk of hearing loss among users of personal audio devices/systems. However, video gameplay devices, including those used in competitive video gameplay (esports) are not covered by this standard. Esports and video gameplay are rapidly becoming one of the largest entertainment industries worldwide reaching over 3 billion people, with approximately 1.7 billion game players participating in video gameplay via a personal computer (PC) or a video game console (that are most likely played with sound on or with headphones). + +From a public health perspective, video gameplay and esports may expose game players to risky health behaviours including prolonged exposure to loud sounds. It is the responsibility of public health and standardization agencies, governments and industry to ensure that health risks associated with esports and video gameplay are minimized including the promotion of safer listening practices. For these reasons, WHO and ITU have developed a universal standard for safe listening in video gameplay and esports. This standard includes the standardization of sound levels, sound exposure measurement, information provision, and warnings. + + + +# Recommendation ITU-T H.872 + +## Safe listening for video gameplay and esports + +# 1 Scope + +This Recommendation provides comprehensive safe listening guidelines for devices, video game titles (software) and audio peripherals used for the purposes of video gameplay, either in home entertainment or esports contexts. Devices include video game consoles, handheld or mobile devices and personal computers (PCs), headphones and headsets. + +The guidelines herein are designed to ensure auditory health and prevent hearing damage for all types of video game players, across a wide spectrum of video gameplay scenarios and equipment. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.100.1] Recommendation ITU-T G.100.1 (2015), *The use of the decibel and of relative levels in speech band telecommunications*. +- [ITU-T H.870] Recommendation ITU-T H.870 (V2) (03/2022), *Guidelines for safe listening devices/systems*. +- [EN 50332-1] CENELEC EN 50332-1:2013, *Sound system equipment: Headphones and earphones associated with personal music players. Maximum sound pressure level measurement methodology. General method for "one package equipment"*. +- [EN 50332-2] CENELEC EN 50332-2:2013, *Sound system equipment: Headphones and earphones associated with personal music players. Maximum sound pressure level measurement methodology. Matching of sets with headphones if either or both are offered separately, or are offered as one package equipment but with standardised connectors between the two allowing to combine components of different manufacturers or different design*. +- [EN 50332-3] CENELEC EN 50332-3:2017, *Sound system equipment: Headphones and earphones associated with personal music players – Maximum sound pressure level measurement methodology – Part 3: Measurement method for sound dose management*. +- [IEC 61252] IEC 61252:1993+AMD1:2000+AMD2:2017, *Electroacoustics – Specifications for personal sound exposure meters*. + +- [IEC 61672-1] IEC 61672-1:2013, *Electroacoustics – Sound level meters – Part 1: Specifications*. +- [IEC 62368-1] IEC 62368-1:2018, *Audio/video, information and communication technology equipment – Part 1: Safety requirements*. +- [ISO 226] ISO 226:2003, *Acoustics – Normal equal-loudness-level contours*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 acoustic reflex threshold** [ITU-T H.870]: The sound pressure level (SPL) at which a sound stimulus triggers stapedius muscle reflex (SMR). + +**3.1.2 acoustic trauma** [ITU-T H.870]: A single exposure to sound resulting in immediate injury to the auditory system. + +**3.1.3 calculated sound dose** [IEC 62368-1]: One-week rolling estimate of sound exposure expressed in percent of the maximum regarded as safe. + +NOTE – See B.4 of [EN 50332-3] for additional information. + +**3.1.4 damage-risk criteria** [ITU-T H.870]: An archaic term referring to the risk of noise induced hearing loss (NIHL) presented by various levels of noise exposure. In [ITU-T H.870] this term is replaced with several preferred contemporary terms: "dose-response relationship", "risk", or "exposure limit". + +**3.1.5 dBA** [ITU-T H.870]: Decibels of sound pressure level measured using the A-weighting network [IEC 61672] and [IEC 60268-1], see also Figure II.2 of [ITU-T H.870]; a frequency weighting intended to measure low-intensity noise (around 40 phon loudness level) but which has also become commonly used for measuring occupational and environmental noise exposures. + +NOTE – The latter use is based on studies of noise-exposed workplace populations in the 1950s and 1960s. That work recommended the use of A-weighting given both its availability in sound level meters and its ability to predict the dose-response relationship over the noise spectra studied [b-Burns-1973] and [b-Burns-Robinson]. Subsequent to that work, the analyses of noise exposed populations upon which the weekly sound allowance in this document are based used A-weighting in measuring noise exposure [b-Neitzel] and [b-Fligor]. + +**3.1.6 dBFS** [ITU-T H.870]: dB full scale is the signal level of a digital signal relative to its overload or maximum level. Different conventions exist. It is common to assign a digital representation of a full-scale sinusoidal the value of 0 dBFS RMS. The peak level can then reach +3.01 dBFS. In other cases, the RMS level of a digital full-scale square wave is assigned 0 dBFS RMS. The maximum peak level is then also 0 dBFS. For the latter cases, dBFS is equivalent to dBov. (dBov: dB relative to digital overload is the signal level of a digital signal relative to its overload or maximum level. See [ITU-T G.100.1].) + +**3.1.7 dBHL** [ITU-T H.870]: Decibels of hearing level at a certain frequency; a level used to measure an audiometric hearing threshold relative to the level defined as normal. + +NOTE – It is the ear's sensitivity in a human with normal hearing, at different frequencies, that is the reference. Figure 1 of [ISO 226] shows standardized equal-loudness contours at different sound levels and a mapping of phon (loudness) against dB SPL (level). The two scales meet at 1 kHz. dB SPL is by definition referenced at the threshold of hearing at 1 kHz, i.e., 0 phon (and 0 dB SPL). + +**3.1.8 diffuse-field frequency response of head and torso simulator (sound pick-up)** [b-ITU-T P.58]: Difference, in decibels, between the third octave spectrum level of the acoustic pressure at the eardrum reference point and the third octave spectrum level of the acoustic pressure at the head and torso simulator (HATS) reference point in a diffuse sound field with the HATS absent. + +**3.1.9 diffuse sound field** [ITU-T H.870]: A field where at any position in the medium, sound is incident from all directions with equal intensities and random phase. The reverberant sound does not vary with receiver position. (Adapted from [b-Vér].) + +**3.1.10 (sound) dose** [ITU-T H.870]: The total quantity of sound energy received by the human ear during a specified period. In the context of this [ITU-T H.870], it is the same as sound exposure (see clause 3.1.14 of [ITU-T H.870]). The unit of (sound) dose is Pa2h. + +**3.1.11 dosimetry** [ITU-T H.870]: The calculation and assessment of the dose received by the human ear. + +**3.1.12 eardrum reference point** [b-ITU-T P.10]: A point located at the end of the ear canal, corresponding to the eardrum position. + +**3.1.13 equal energy principle** [ITU-T H.870]: The premise that the total effect of sound is proportional to the total amount of sound energy received by the ear, irrespective of the distribution of that energy in time. According to this principle, equal amounts of sound energy are expected to cause equal amounts of sound induced permanent threshold shift regardless of the distribution of the energy across time. This principle allows the question of hearing damage risk posed by a sound exposure to be related to a sound dose. + +**3.1.14 equivalent continuous A-weighted sound pressure level** [ITU-T H.870]: A continuous sound pressure level (SPL) in dBA which is considered to pose the same risk as a time-varying SPL, calculated using a 3-dB exchange rate between level and time. Mathematically, it is represented as: + +$$L_{Aeq,T} = 10 \lg \left\{ \frac{1}{T} \int_{t_1}^{t_2} p_A^2(t) dt \right\} / p_0^2 \text{ dBA}$$ + +where: + +$L_{Aeq,T}$ is the equivalent continuous A-weighted sound pressure level re 20 $\mu\text{Pa}$ , determined over a time integration interval $T = t_2 - t_1$ + +$p_A(t)$ is the instantaneous A-weighted sound pressure of the sound signal + +$p_0$ is the reference sound pressure of 20 $\mu\text{Pa}$ . + +**3.1.15 equivalent continuous average sound level normalized** [ITU-T H.870]: A continuous SPL in dBA which is considered to pose the same risk as a certain time-varying SPL pattern measured using a 3-dB exchange rate and normalized to an $n$ -hour exposure period. For example, the value for $n$ could be 8, in which case this may also be referred to as an $L_{A8\text{hn}}$ or $L_{\text{EX}8\text{h}}$ ", or $n = 40$ , $L_{\text{EX}40\text{h}}$ . + +**3.1.16 excess risk** [ITU-T H.870]: The risk of sound induced hearing loss (SIHL) associated with a specific amount of exposure. + +**3.1.17 exchange rate** [ITU-T H.870]: The change in average noise level (in dB) that corresponds to a doubling or halving of allowable exposure time. + +**3.1.18 free sound field** [ISO 3745]: A field in a homogeneous, isotropic medium free of boundaries. + +**3.1.19 free-field frequency response of head and torso simulator (sound pick-up)** [b-ITU-T P.58]: Difference, in decibels, between the third octave spectrum level of the acoustic pressure at the eardrum reference point and the third octave spectrum level of the acoustic pressure at the head and torso simulator (HATS) reference point in a free sound field with the HATS absent (test point). + +**3.1.20 frequency response** [ITU-T H.870]: In this context, frequency response is short for "sensitivity vs. frequency response", sometimes referred to as the "tone curve" of an audio device, such as a headphone, loudspeaker, microphone, amplifier, etc. + +**3.1.21 head and torso simulator (HATS)** [b-ITU-T P.10]: Manikin extending downward from the top of the head to the waist, designed to simulate the sound pick-up characteristics and the acoustic diffraction produced by a median human adult and to reproduce the acoustic field generated by the human mouth. + +**3.1.22 hearing threshold level** [ITU-T H.870]: Sound pressure level (SPL) at specific audiometric test frequencies, measured in dBHL. + +**3.1.23 instructed person** [IEC 62368-1]: Instructed person is a term applied to persons who have been instructed and trained by a skilled person, or who are supervised by a skilled person, to identify energy sources that may cause pain (see Table 1) and to take precautions to avoid unintentional + +contact with or exposure to those energy sources. Under normal operating conditions, abnormal operating conditions or single fault conditions, instructed persons should not be exposed to parts comprising energy sources capable of causing injury. + +**3.1.24 listening device** [ITU-T H.870]: A wearable device used to deliver sound to the ear. Consists of a transducer and fitting to accommodate in the ear, on the ear or over the ear listening. Examples are headphones and earphones. Headphones and earphones may include amplifiers and other electronics, such as for wireless or digital connection, signal processing, noise cancellation, or even media storage for subsequent playback. As such, headphones and earphones with such functionality could be classed as personal audio systems. + +NOTE – The principle of classifying energy sources and proscribing safeguards against those sources is enshrined in [IEC 62368-1], on which much of this Recommendation is based. + +**3.1.25 loudness K-weighted full scale (LKFS)** [b-ITU-R BS.1770-5]: This designation signifies: Loudness, K-weighted, relative to nominal full scale. The LKFS unit is equivalent to a decibel in that an increase in the level of a signal by 1 dB will cause the loudness reading to increase by 1 LKFS. + +**3.1.26 loudness unit full scale (LUFS)** [EBU R 128-2023]: LUFS' is equivalent to 'LKFS' (which is used in [b-ITU-R BS.1770-5]). The EBU uses 'LUFS' which is compliant with international naming conventions. + +**3.1.27 hearing loss** [b-WHO 2021]: A person is said to have hearing loss if their hearing capacity is reduced and they are not able to hear as well as someone with normal hearing. "Normal" hearing typically refers to hearing thresholds of 20 dB or better in both ears. + +**3.1.28 material hearing impairment** [b-NIOSH]: An average of the hearing threshold levels for both ears that exceeds 25 dBHL at 1000, 2000, 3000 and 4000 Hz. + +**3.1.29 microphone-in-real-ear** [ISO 11904-1]: Refers to measurements carried out using miniature or probe microphones inserted in the ears of human subjects. + +**3.1.30 momentary exposure level** [IEC 62368-1]: Metric for estimating 1s sound exposure level from the HD 483-1 S2 test signal applied to both channels, based on [EN 50332-1], clause 4.2. + +NOTE 1 – MEL is measured in dB. + +NOTE 2 – See B.3 of [EN 50332-3] for additional information. + +**3.1.31 ordinary person** [IEC 62368-1]: Ordinary person is the term applied to all persons other than instructed persons and skilled persons. Ordinary persons include not only users of the equipment, but also all persons who may have access to the equipment or who may be in the vicinity of the equipment. Under normal operating conditions or abnormal operating conditions, ordinary persons should not be exposed to parts comprising energy sources capable of causing pain or injury. Under a single fault condition, ordinary persons should not be exposed to parts comprising energy sources capable of causing injury. + +**3.1.32 personal music/media player** [IEC 62368-1]: A personal music player is a portable equipment intended for use by an ordinary person, that: + +- Is designed to allow the user to listen to audio or audio-visual content/material; and +- Uses a listening device, such as headphones or earphones that can be worn in or on or around the ears; and +- Has a player that can be body worn (of a size suitable to be carried in a clothing pocket) and is intended for the user to walk around while in continuous use (for example, on a street, in a subway, at an airport, etc.). + +NOTE – Examples are portable CD players, MP3 audio players, mobile phones with MP3 type features, PDAs or similar equipment. + +**3.1.33 personal audio device** [ITU-T H.870]: A portable device designed to be worn on the body or fit in the clothing pocket to listen to various forms of media. It can be connected to a listening device. An example of a personal audio device is a personal media player (PMP). + +**3.1.34 personal audio system (PAS)** [ITU-T H.870]: A system of a personal audio device and a listening device. Examples are a personal media player (PMP) connected to headphones, and headphones capable of playing locally stored content independently of an external PAD. + +**3.1.35 skilled person** [IEC 62368-1]: Skilled person is a term applied to persons who have training or experience in the equipment technology, particularly in knowing the various energies and energy magnitudes used in the equipment. Skilled persons are expected to use their training and experience to recognize energy sources capable of causing pain or injury and to take action for protection from injury from those energies. Skilled persons should also be protected against unintentional contact or exposure to energy sources capable of causing injury. + +**3.1.36 sound allowance** [ITU-T H.870]: A dose estimate of sound exposure over a certain rolling period of time (e.g., daily or weekly), commonly expressed as a percentage of the maximum regarded as safe. A weekly sound allowance is equivalent to 100% calculated sound dose (CSD). + +$$E = \int_{t_1}^{t_2} (p_A(t))^2 dt$$ + +**3.1.37 sound-induced** [ITU-T H.870]: Refers to a state or a quality resulting from exposure to sound. The sound may be (part of) music or "noise", which implies the sound is not desirable. + +**3.1.38 sound-induced permanent threshold shift** [ITU-T H.870]: Synonymous with permanent sound induced hearing loss (SIHL). + +**3.1.39 sound-induced temporary threshold shift** [ITU-T H.870]: Sound induced hearing loss (SIHL) that results from exposure to sound but recovers after a sufficient time spent in low sound conditions. + +**3.1.40 sound-induced tinnitus** [ITU-T H.870]: Perception of phantom sound in the ears or head that are either temporary or permanent, following excessive sound exposure. + +**3.1.41 sound pressure level** [b-ITU-R V.574]: The logarithm, generally expressed in decibels (dB SPL), of the ratio of sound pressure and a reference pressure $p_0$ , often 20 $\mu\text{Pa}$ . Note that a factor of 20 is used when the ratio is between two sound pressures, rather than between two sound intensities. + +$$SPL = 20 \log_{10} \left( \frac{p}{p_0} \right)$$ + +**3.1.42 stapedius muscle reflex** [ITU-T H.870]: The process in which the stapedius and tensor tympani muscles of the ossicles contract when the ear is exposed to high intensity sound. This is also called auditory reflex. + +**3.1.43 transducer** [ITU-T H.870]: An electronic device that converts energy from one form to another. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms. + +**3.2.1 audio peripheral:** An external device that either captures or outputs sound and connects to a computer system for the purpose of enabling or contributing to video game audio. In the context of video gameplay, audio peripherals typically include (but are not limited to) earphones, headphones and headsets. + +**3.2.2 close fitting audio devices:** Such as headphones, earphones, ear buds, in ear monitors (IEMs); wireless and wired, which often feature both sound producing components (e.g., drivers, speakers, etc) as well as sound capturing components (e.g., microphones). + +**3.2.3 dynamic range compression:** Refers to a signal processing technique that will reduce the ratio between the highest and lowest amplitudes of an audio signal, thus altering the dynamic of a sound signal. + +**3.2.4 esports:** Competitive and organized computer and video gameplay, in which two or more parties (individuals or teams) face each other under regulated and balanced conditions. + +**3.2.5 esports live event:** An esports live event (ELE) can be defined as an event around competitive video gameplay(s), involving video game tournaments and related content. These events are conducted in a live format, sometimes in designated venues, where esports enthusiasts gather to witness the gameplay, competition and associated entertainment. The primary focus of ELEs is the hosting of video game tournaments, where players or teams compete against each other, and during gameplay ELEs may feature sound reinforcement audio systems, multimedia displays (such as large screens) and stages to showcase the gameplay, commentary and highlights to the audience. + +**3.2.6 free-field audio devices:** Such as speakers, soundbars and sound systems. + +**3.2.7 game player:** A person that plays video games on video gameplay devices. + +**3.2.8 handheld or portable console:** A portable gameplay system designed for on-the-go video gameplay. + +**3.2.9 headphone safety mode:** A hearing protection feature used within a video gameplay device or software that activates when a game player switches from free-field loudspeaker to headphone or headset audio peripheral. + +**3.2.10 home game console:** A game console designed to be stationary. + +**3.2.11 in-ear monitor:** A device with earbud-like fitted earpieces used to provide audio to a listener while eliminating external noise. + +**3.2.12 input accessories:** Various hardware accessories like keyboards, joysticks, steering wheels, gamepads and motion-sensing devices that enhance gameplay for specific genres and may include onboard microphone systems. + +**3.2.13 location-based entertainment (LBE):** A type of entertainment that occurs in a physical location beyond the confines of one's home. + +**3.2.14 loudness unit:** The unit of measurement used in the process of quantifying a digital recording's perceived loudness by analysing the average level over time. + +**3.2.15 mobile devices:** Smartphones and tablets with capabilities to run and play video games, often available through app stores. + +**3.2.16 passive gameplay:** Refers to a section of a video game where the game player is not actively participating but still observing game play. This type of gameplay is most commonly found in multiplayer games where a game player has been eliminated from the game temporarily. + +**3.2.17 passive gameplay audio:** Refers to the video game soundtrack that is produced during passive gameplay moments of a video gameplay session. Passive gameplay audio includes sound effects, music, voice chat or dialogue that occur during moments of a video game where the game player is not actively involved or participating in the game play. + +**3.2.18 personal computer (PC):** Computer (including laptops) with capabilities to run and play video games. + +**3.2.19 safe listening gameplay device:** A video gameplay device designed to include features and functionalities that prioritize the well-being of the user's auditory health during gameplay. The primary objective of a safe listening gameplay device is to promote responsible and healthy video gameplay practices by safeguarding users from excessive sound levels that could lead to hearing impairment, tinnitus and/or discomfort. + +**3.2.20 smart listening mode:** A video game software user interface option, typically found in sound or audio settings menus. When enabled, it activates available safe listening features within a specific video game software title. + +**3.2.21 sound category volume controls:** Settings in a video game that allow the player to adjust the volume levels of various key audio components to the game player's preferences, such as background music, sound effects, dialogue, voice chat and other in-game audio categories. + +**3.2.22 speaker:** A device for converting electrical energy into acoustical signal energy that is radiated into a room or open air. It includes transducers that are in-built into the video gameplay device or are external to these, e.g., loudspeakers, sound bars, or sound reinforcement speakers. + +**3.2.23 video game:** An electronic game that involves interaction with a user interface or input device (such as a joystick, controller, keyboard, or motion sensing device) to generate visual and/or audio feedback for a player. Video games encompass a wide variety of genres and formats, ranging from simple arcade games to complex, immersive simulations. They can be played on various platforms, including personal computers, video game consoles, handheld devices, and mobile phones. + +**3.2.24 video game audience participant:** Someone who observes the video game play of others but is not playing the game. Video game audience participants can include (but are not limited to) people viewing video game events being streamed via an online broadcasting service (live or pre-recorded) or people viewing live esports events at venues. + +**3.2.25 video game console:** A purposed game playing system designed to connect to televisions or monitors, providing a platform to run video games. + +**3.2.26 video gameplay device (VGD):** A device designed for executing the software instructions that constitute a video game. It comprises a combination of hardware, firmware and an operating system that facilitates the playing, processing, rendering and production of immersive video and audio gameplay content. A VGD can be designed to be stationary, such as a video game console or arcade game device, or portable. In the context of this safe listening standard, examples of VGDs include video game consoles, handheld or mobile devices, and personal computers (PCs). + +**3.2.27 video gameplay peripheral:** An additional video game hardware connected to a VGD that provides some sort of additional functionality relevant to a particular video game being executed. Whilst peripherals can provide a range of functions, those most relevant to this standard are peripheral devices capable of reproducing or capturing audio. + +**3.2.28 video gameplay software:** Video gameplay software, in the context of digital entertainment, refers to computer programs and applications specifically crafted to facilitate interactive engagement with video gameplay content. + +**3.2.29 video gameplay software title:** Name or title given to a specific video game software program or application used to distinguish one video game from another. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------------| +| AR | Augmented Reality | +| CSD | Calculated Sound Dosage | +| DRP | Eardrum Reference Point | +| ELE | Esports Live Event | +| LU | Loudness Unit | +| LUFS | Loudness Unit relative to Full Scale | +| PAS | Personal Audio Systems | + +| | | +|------|----------------------------| +| PC | Personal Computer | +| SIHL | Sound-Induced Hearing Loss | +| VGD | Video Gameplay Device | +| VR | Virtual Reality | + +# 5 Conventions + +In this Recommendation: + +- The word "shall" is used to express mandatory requirements for conformance to this Specification. When used to express a mandatory constraint on the values of syntax elements or the values of variables derived from these syntax elements, it is the responsibility of the encoder to ensure that the constraint is fulfilled. +- The word "may" is used to refer to behaviour that is allowed, but not necessarily required. +- The word "should" is used to refer to behaviour of an implementation that is encouraged to be followed under anticipated ordinary circumstances, but is not a mandatory requirement for conformance to this Specification. + +# 6 Background + +## 6.1 Safe listening introduction + +Temporary and permanent hearing threshold shifts from exposure to sound and noise is an increasing public health problem, particularly in children and adolescents. In fact, sound-induced hearing loss (SIHL) is the leading cause of preventable hearing loss in the world. From the early 1990s to 2000, it was estimated that the number of young people with SIHL has increased from 6.7% to 18.8% [b-Smith 2000]. Some of this can be attributed to the fact that in this day and age, young people are utilizing their leisure time with activities that expose them to high levels of music using personal audio systems (PAS) or attending communal events such as concerts, bars, clubs, etc. + +Hearing loss can occur as a consequence of listening to high levels of sound over prolonged periods of time. In addition to the above-mentioned sources of leisure sound, the unsafe use of video gameplay devices (VGDs) poses a threat to the hearing of millions [b-Dillard 2024]. + +Hearing loss caused by sound exposure is permanent, but it can largely be prevented through safe listening practices. It may be considered that prevention of hearing loss through safe listening practices is the responsibility of the individual. However, the onus of raising awareness and creating an environment for safe listening lies with the community, manufacturers of devices, governments and other stakeholders. + +Appropriate technology can help to reduce the risk of unsafe listening. A personal audio device/system in compliance with safe listening standards, which serve to minimize the users' risk of acquiring hearing loss (as a consequence of its use), can be termed as a safe listening device/system. + +The term safe listening refers to listening behaviour that does not put peoples' hearing at risk. A person's risk of losing his/her hearing depends on how loud, for how long and how often the person is exposed to loud sounds. Such exposure may be through personal audio devices or in entertainment venues as well as in the surrounding environment, such as in traffic, in the workplace or at home. + +The term sound allowance refers to the acceptable level of sound energy an individual can receive without putting his/her hearing at risk. The term "weekly sound allowance" is equivalent in meaning to "100% calculated sound dose (CSD)" (see clause 3.1.3). It is recommended to use the term 'sound allowance' for health communication purposes, rather than 'dose'. It should be also noted that the sound allowance determined as described by this Recommendation ignores sound exposure from + +sources other than personal audio devices. Depending on what those exposures are, a risk of hearing loss may still exist for an individual. + +## 6.2 Video gameplay device + +Figure 6-1 illustrates the general architecture of a VGD, following the definition in clause 3.2. + +![Figure 6-1: Architecture of a video gameplay device (VGD). The diagram shows the flow of audio from various sources within a 'Video game system' to a 'Listening device*'. Sources include 'Game software' (Music, SFX, dialogue, etc.), 'Voice chat', 'External music streaming player', and 'Other media'. These are mixed via 'Game audio mix' and then controlled by 'Game Vol', 'Chat Vol', 'Music Vol', and 'Other Vol' knobs. The mixed audio goes to a 'Master volume' knob, then a 'DAC' (Digital-to-Analog Converter). The DAC output goes to a '(Device volume)' knob and a 'Transducer' (headphones/speakers). Feedback from the 'Listening device*' includes 'Headphone Status**' and 'Headphone Dosimetry**'. A 'Game player microphone (Chat)' is also shown within the listening device area.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Figure 6-1: Architecture of a video gameplay device (VGD). The diagram shows the flow of audio from various sources within a 'Video game system' to a 'Listening device\*'. Sources include 'Game software' (Music, SFX, dialogue, etc.), 'Voice chat', 'External music streaming player', and 'Other media'. These are mixed via 'Game audio mix' and then controlled by 'Game Vol', 'Chat Vol', 'Music Vol', and 'Other Vol' knobs. The mixed audio goes to a 'Master volume' knob, then a 'DAC' (Digital-to-Analog Converter). The DAC output goes to a '(Device volume)' knob and a 'Transducer' (headphones/speakers). Feedback from the 'Listening device\*' includes 'Headphone Status\*\*' and 'Headphone Dosimetry\*\*'. A 'Game player microphone (Chat)' is also shown within the listening device area. + +H.872(24) + +NOTE – Items in dashed boxes may or may not be present or active during game play. Voice chat may be provided as part of the game itself, or via an external app such as Discord. Game provided music may be supplanted by the player via an external music player, such as Spotify. + +\* Listening Devices may include linear processing, such as gain or frequency shaping and non-linear processing, such as compression or dynamic range equalization. Any of these can be dynamic. + +NOTE – Location of Master Volume, DAC or other controls may depend on user configuration. For example, DAC and/or Volume control may be located in the Listening device (Such as USB headphones, or analogue headsets with hardware volume controls). + +\*\* Headset Status and/or Dosimetry may or may not be available. In some cases, the make/model headset may be known which may help map digital audio level to SPL. Dosimetry may also be included. But generally the listening hardware is unknown. + +NOTE 1 – Items in dashed boxes may or may not be present or active during game play. Voice chat may be provided as part of the game itself, or via an external app such as Discord. + +NOTE 2 – Game provided music may be supplanted by the player via an external music player, such as Spotify. + +NOTE 3 – Location of Master Volume, DAC or other controls may depend on user configuration. For example, DAC and/or Volume control may be located in the Listening device (such as USB headphones, or analogue headsets with hardware volume controls). + +NOTE 4 – Headset Status may or may not be available. In some cases, the make/model headset may be known which can help map digital audio level to SPL. Status may include also dosimetry, but generally the listening hardware is unknown. + +**Figure 6-1 – Architecture of a video gameplay device (VGD)** + +A VGD is intended for use by an individual or individuals and + +- is designed to enable the user to engage with video gameplay content; +- utilizes a display screen for visual presentation; +- incorporates video gameplay peripherals such as controllers, keyboards or motion-sensitive devices for interactive input; +- features an audio component for delivering sound effects and immersive audio experiences; +- can be carried or placed in close proximity to the user during operation (for example, played within proximity to television/computer screen, held in hands, placed on a surface); and +- provides adjustable settings for visual and auditory output. + +Examples of VGDs include video game consoles, personal computers (PCs), handheld gameplay devices and mobile devices with gameplay capabilities; wearable gameplay accessories with integrated displays and interaction mechanisms; devices equipped with virtual reality (VR) or augmented reality (AR) functionalities. + +The provisions outlined do not apply to: + +- hearing aids, hearing aid equipment and other specialized devices for assistive listening; +- location-entertainment such as arcade games. + +NOTE – The listed exemptions are subject to reassessment as technology progresses. + +While the current scope emphasizes gameplay and visual content, considerations for virtual reality and immersive experiences are for future study. + +## **6.3 Video gameplay software (titles)** + +Video gameplay software, in the context of digital entertainment, refers to computer programs and applications specifically crafted to facilitate interactive engagement with video gameplay content. This software is intricately designed to enhance user experiences through interactive elements and is typically designed to include both visual and audio content to create a sense of immersion. Key features of video gameplay software include: + +- **Interactive engagement:** Gameplay software enables users to actively participate in video gameplay experiences by providing a platform for user input and interaction. This can involve controlling characters, making decisions, and influencing the virtual environment; +- **Visual presentation:** Utilizing display screens for visual presentation, gameplay software delivers graphics and dynamic visuals that contribute to the immersive nature of video games; +- **User input devices:** Gameplay software is compatible with various video gameplay peripherals, including controllers, keyboards, microphones, and motion-sensitive devices. These peripherals serve as interfaces, allowing users to control and navigate the virtual world created by the software; +- **Audio component:** To enrich the gameplay experience, gameplay software incorporates audio components that deliver sound effects, music, and other auditory cues. This audio component (also referred to as the soundtrack) is typically designed to be reproduced by speakers or close-fitting audio devices or transducers such as headphones, earphones or in-ear monitors; +- **Adjustable settings:** Providing users with adjustable settings for visual and auditory output, gameplay software allows individuals to customize their gameplay experience based on personal preferences. This adaptability enhances accessibility and accommodates diverse user preferences. + +Examples of platforms hosting video gameplay software include video game consoles, PCs, handheld video gameplay devices and mobile devices with gameplay capabilities. Additionally, video gameplay software can extend to wearable gameplay accessories featuring integrated displays and interaction mechanisms, as well as devices equipped with virtual reality (VR) or augmented reality (AR) functionalities. + +The provisions outlined do not apply to: + +- Gameplay software specifically developed for the purpose of auditory diagnosis or rehabilitation; +- Gameplay software designed with no soundtrack at all. + +# 7 Damage risk criteria + +## 7.1 Operational modes for video gameplay devices (VGD) + +The following considerations are taken from clause 7.1 of [ITU-T H.870], for the convenience of the reader. In case of any discrepancy, the provisions in [ITU-T H.870] prevail. + +It is required that VGD paired with a personal audio accessory (such as a headphone) shall include a system that tracks the user's exposure time, and estimates sound level and usage of a reference exposure (sound allowance). This includes all media playback through the device or system (i.e., stored locally or streamed) during times when the user is using ear/headphones. + +This system shall determine the exposure of the user based on the following mode: + +- Mode 1: (WHO) standard level for adults: this will apply 1.6 Pa2h per 7 days as the reference exposure. + +NOTE 1 – The value is adapted from [IEC 62368-1] and is based on the values mentioned in [b-2009/490/EC], which stipulated that sound is safe when below 80 dB(A) for a maximum of 40 hours per week. Therefore, the value of 100% calculated sound dose (CSD) corresponds to 80 dB(A) for 40 hours. + +The VGD should offer a more conservative mode to users that prefer or benefit from a more conservative level as outlined in Mode 2: + +- Mode 2: (WHO) standard level for users that prefer or may benefit from lower sound levels (e.g., for children): this will apply 0.51 Pa2h per 7 days as the reference exposure. + +The device or system should allow the users to select their reference exposure as one of the above-mentioned two modes. + +NOTE 2 – Reference exposures are derived from 80 dBA (Mode 1) and 75 dBA (Mode 2) sound pressure level (SPL) for 40 hours per week (which in turn is derived from 8 hours per day, 5 days/week). + +NOTE 3 – An alternative to expressing exposure in terms of percentage used, is to express the *time left* until reaching a certain exposure (e.g., remaining playback time at the current playback level until reaching 100%). + +It is recommended that mode choice be given when using the player for the first time (or when the device is reset to factory settings). It is recommended that the user be able to change the mode choice at any later time, e.g., via a device configuration menu. + +Examples of weekly listening time duration based on sound allowance for the modes above can be found in Table 1 and Table 2. + +**Table 1 – Example of weekly listening time for Mode 1** + +| dB(A) SPL | Weekly (1.6 Pa 2 h) | +|-----------|--------------------------------| +| 107 | 4.5 min | +| 104 | 9.5 min | +| 101 | 19 min | +| 98 | 37.5 min | +| 95 | 75 min | +| 92 | 2.5 h | +| 89 | 5 h | +| 86 | 10 h | +| 83 | 20 h | +| 80 | 40 h | + +**Table 2 – Example of weekly listening time for Mode 2** + +| dB(A) SPL | Weekly (0.51 Pa2h) | +|------------------|--------------------------------------| +| 107 | 1.5 min | +| 104 | 3 min | +| 101 | 6 min | +| 98 | 12 min | +| 95 | 24 min | +| 92 | 48 min | +| 89 | 1 h 36 min | +| 86 | 3 h 15 min | +| 83 | 6 h 24 min | +| 80 | 12 h 30 min | +| 77 | 25 h | +| 75 | 40 h | + +## 7.2 Uncertainty in dose estimate + +The following considerations are taken from clause 7.2 of [ITU-T H.870], for the convenience of the reader. In case of any discrepancy, the provisions in [ITU-T H.870] prevail. + +In estimating sound dose there is some uncertainty. Some sources for uncertainties are: + +- sound source; +- variation in headphone characteristics of a single model, due to production tolerances; +- variation due to unknown headphone type; +- manufacturing tolerance; +- errors due to incorrect manual selection of headphone type; +- variations pertaining to the artificial ear during characterization; +- imperfect relation between artificial ears and real ears; +- imperfect relation between a standardized diffuse-field correction and a variety of human head-related transfer functions; +- variations pertaining to the human ears; +- uncertainties in characterization of player characteristics, especially due to non-linear processing in the alternative implementation shown in Figure II.5 of [ITU-T H.870]; +- errors in calculations; +- exposure from other sources; +- variation in headphone characteristics between models, for instance sensitivity and impedance. + +Since some of these uncertainties are typically several dB, and an error of 3 dB constitutes a 100% dose error, uncertainties of dose estimation can be expected to be greater than a hundred percent. It is therefore suggested to refrain from signalling "safe" and "green" to the user based on dose readings below a certain limit. + +The dose estimation is however relevant in accounting for general trends: + +- higher signal level means higher risk; + +- longer exposure means higher risk; +- the spectral content of the audio is accounted for. + +Further details on this subject remain for future study. + +See Appendix II in [ITU-T H.870] for a discussion on implementation of dose estimation functionality. + +For dose measurement methods, refer to clause 8 of [ITU-T H.870]. + +# **8 Safe listening features for video gameplay devices** + +VGDs include, but are not limited to, video game consoles, personal computers (PCs), handheld gameplay devices, mobile devices, virtual reality, augmented reality devices, and includes the operating systems which may be installed upon these devices for it to operate. + +Among the various components integral to the video game experience, VGDs stand out as a pivotal factor that can directly influence the resulting sound pressure level experienced by game players. This influence becomes particularly pronounced in scenarios where the entire video gameplay setup is sourced from a single vendor or manufacturer, where all operating equipment values will be known, and calculated sound dosage can be more accurately recorded. + +The following clause outlines features required in order for a VGD to become compliant with this standard. + +## **8.1 Dosimetry** + +A VGD connected to headphones or earphones shall track the level and duration of the user's exposure to sound as a percentage used of a reference exposure, also known as a user's "sound allowance". + +The user should have the option to choose one of two modes that determine the total sound dose they can safely consume: + +- Mode 1 for adults: 80 dB (A-weighted) for 40 hours per week; +- Mode 2 for children: 75 dB (A-weighted) for 40 hours per week. + +Where feasible, the calculation should be made across multiple devices used by the same individual, for example, personal audio systems, VGDs and others. It is ideal to provide a single estimate for the individual. + +NOTE – Where feasible, a VGD may also be able to calculate sound dosage for both closefitting audio peripheral devices (headphones, earphones, in-ear monitors etc.) and free field audio devices (loudspeakers, surround sound arrays etc.), including location-based entertainment. The detail of such is for future study. Consideration needs to be made where a single VGD is used by multiple users, dosimetry should be calculated on an individual user basis. This specific information (whether the dosimetry is user specific or not) should be provided to the users. + +See Appendix II of [ITU-T H.870] for information on implementation of dosimetry. + +### **8.2 Dosimetry user interface** + +A VGD shall provide dosimetry information to the user in a clear, easily accessible and user-friendly user interface. + +User interface features shall include, at the minimum: + +- Rolling 7-day recorded information on sound allowance use; +- A suitable indication of whether activity is "Safe/OK" or "Unsafe/Not OK". Where possible, this calculation should be calculated across multiple devices used by the same individual. Where such harmonization isn't possible, users must be informed that listening over multiple + +devices can reduce the accuracy of the estimate presented and that the user should exercise caution and keep volumes low; + +- Information on how to listen safely; +- Information on safe listening features available in the VGD. + +Examples are shown in Appendix II, in particular Figures II.1 to II.4. + +#### 8.2.1 Messages + +The VGD shall provide messages about general sound allowance use, such as time spent, sound allowance consumption and/or prediction of when the sound allowance will be exceeded. These can be delivered at appropriate times that do not break video gameplay immersion. Messages could be provided: + +- a) upon the initial boot of the VGD prior to a game title being loaded; +- b) upon the end of a video gameplay session at the exit screen; +- c) using real-time notifications by using in-game notification systems. + +Should in-game notification systems be the selected method of safe listening notifications for the video gameplay device, provisions need to be made to ensure safe listening notifications should still occur even if the user enables "do not disturb" or similar modes. + +When the VGD dosimetry system establishes the game player has exceeded 100% of their weekly allowance, the user shall be provided with a cue for action. + +##### 8.2.1.1 Cue for action message + +The VGD shall give relevant warnings and cues for actions when the user exceeds 100% of the weekly allowance, without interrupting the game session or breaking the immersive experience. + +- The user shall receive, first a "warning" expressed through text and visual notification informing that the weekly sound allowance has been exceeded and that from this point on, further listening at the same volume will pose a risk to their hearing. +- The warning shall be followed by a "cue for action" in which the user is offered the choice to either accept the risk of continued listening or protect their hearing. The "cue for action" should be linked to active options on the device such as: + - automatic safe volume option, by which the device automatically changes the volume to achieve a safer listening level; + - direct access to volume settings; + - set-up of default volume limits; + - remind later option; + - ignore and continue option. +- If the user fails to take any action, the volume shall automatically be reduced as described in clause 8.3.1 (a sound level at the eardrum reference point (DRP), with diffuse-field correction, no greater than 80 or 75 dBA (according to the mode selected)). + +NOTE – See Appendix II for examples of this type of message. + +### 8.3 Volume control system + +A VGD shall provide an easily accessible and configurable volume control system (which is in accordance with the selected operational mode) to mitigate the risk of permanent hearing damage for game players and participants by setting the default volume levels to a safe listening level. + +NOTE – In the context of video game audio, "volume control" refers to the mechanism by which players and users can adjust the intensity or loudness of sound output generated by a video game. A volume control system + +can work manually, with input from the game player, or can be part of an automatic volume control system, which is controlled by the VGD. + +#### 8.3.1 Volume limiting + +The VGD shall provide the user with a suitable method for volume limiting when headphones or earphones are detected. This refers to a feature which provides a message relative to a predetermined reference exposure (sound allowance) limit in accordance with clause 8.1. + +A volume limiting option message shall be automatically provided when the user reaches 100% of the weekly allowance. The user shall be given a message in accordance with clause 8.2.1.1 which will allow them the option to "continue listening" in case they do not wish the device volume to reduce. When the message is not acknowledged, the default action will be to reduce the volume of the device to achieve a sound level at the eardrum reference point (DRP), with diffuse-field correction, no greater than 80 or 75 dBA (according to the mode selected). If possible, the users should be given the option to customize this level (the level at which they would like their device to limit the volume) according to their preference. It is further recommended that this should be set as the default option and that the user should have the option of turning this feature off if they do not wish to use this setting. + +NOTE – If, upon reaching 100% of the user's weekly allowance, the level is automatically reduced to 80 dBA (75 dBA for sensitive listeners), the user's sound exposure will continue to increase beyond 100%. Such an action is therefore not fully protective against further risk to hearing; rather, the intention is to ensure that listening proceeds at no more than a moderate level until the user has acknowledged the warning, without interrupting the game session or breaking the immersive experience. + +#### 8.3.2 Password-protected sound output control + +The VGD shall have the option where if it has a child/parental account system (also known as parental controls), the maximum sound output can be fixed and locked in the settings, possibly through the use of a password. The intent of this feature is to allow parents (or other adults) to limit the maximum sound output of the child's device, in a way that cannot be changed by the child. + +### 8.4 Headphone safety mode + +A VGD shall provide a default headphone safety mode where the audio output of VGD for headphones is also intended for use with a speaker and the audio output level is not stored separately for each type of audio peripheral. + +The default headphone safety mode shall be implemented when the VGD is capable of detecting that users are moving from free-field to headphones on the same audio output. In such instances an automatic volume reduction of at least 3 dB occurs. + +## 9 Safe listening features for video gameplay software + +Safe listening feature compliance can be achieved by a video game software title, separate to that of the VGD it is designed to run on. Should equivalent features be available on the VGD, they are not required to be included in the video gameplay software and can be omitted. + +## 9.1 Safe listening warnings/messages + +Video gameplay software **shall provide a message/warning to game players regarding** auditory risks (e.g., hearing loss, tinnitus) associated with loud sounds and extended exposure, which can occur when taking part in video gameplay activities. + +NOTE 1 – The warnings/messages described in this clause are separate and are of a different nature to those outlined in clause 8.2.1, and are of a general health information nature, as opposed to warnings related to dosimetry readings. + +NOTE 2 – See Appendix III for examples of warnings/messages. + +#### 9.1.1 Initial load screen warnings + +The video gameplay software warning shall be displayed upon initial loading of the game, notifying the game player that loud sounds and extended exposure to sound can be a source of unsafe listening. The warning should include: + +- a description of safe sound level dosage; +- examples of auditory symptoms to be aware of in case of hearing damage (e.g., ringing in the ears, fullness in the ear, loss of sensitivity to other sounds etc.); +- The message should also indicate that absence of these symptoms does not necessarily indicate an absence of hearing damage. + +#### 9.1.2 After a period of continuous gameplay + +The game title **shall provide additional notifications/messages** during convenient moments in the game that do not break video gameplay immersion. + +NOTE 1 – When accessing audio options, convenient moments may include the end of a round of gameplay, after completing a level, after losing a life, when pausing game, at the end of two-hours of continuous gameplay, upon exit etc. + +NOTE 2 – See clause II.2 for a visual example. + +### 9.2 Sound category and master volume controls + +The video game software **shall include independent sound category volume controls** allowing the game player to adjust levels of and selectively mute different sounds within the game. This could be, for example, under the game audio menu options. + +Sound category volume controls of this nature can provide game players an efficient way to reduce and mute: + +- 1) the overall master volume level within the game, and +- 2) specific sounds that they feel are not required based on their gameplay style. + +Sound category volume channel controls **should** be easily and readily available to the individual, so that adjustments for comfort are quick to perform. + +Examples of such controls could be: + +- Game dialogue level; +- Sound effects level; +- Music level; +- Voice chat level. + +NOTE – In designing the user interface for the sound category volume channel controls, universal design principles should be taken into account, so that adjustments are quick to perform. See [b-ISO/TC 159/SC 4], [b-ISO 9241-210] and [b-ISO 24508] for more information. + +### 9.3 Title dependent safe listening features + +The video game **should include default safe listening features within the game** with the intent to reduce the overall sound exposure and risk of hearing damage among game players. + +This document acknowledges the diverse range of soundtracks, gameplay styles and listening requirements of video gameplay software titles. As such, developers are encouraged to consider the implementation of safe listening features, some of which are listed below. + +#### 9.3.1 Feature 1: Game audio output scaling + +A video games' output should be scaled so that a 30-minute integrated window is measured at no higher than $-23$ loudness unit relative to full scale (LUFS) with a deviation of $\pm 2$ loudness unit (LU). The true peak level should not exceed $-1$ dBTP (dB true peak). + +NOTE 1 – [b-EBU R 128] uses $-23$ LUFS $\pm 1$ LU and [b-Sony ASWG-R001] uses $-24$ LKFS $\pm 2$ LU. Both standards use $-1$ dBTP true peak level, measured with a meter compliant with [b-ITU-R BS.1770] and [b-TECH 3341]. + +NOTE 2 – Loudness K-weighted full scale (LKFS), originally defined in [b-ITU-R BS.1770], is synonymous with LUFS, with LUFS being compliant with international naming conventions [b-EBU R 128]. + +NOTE 3 – There is a reference implementation of the algorithm in [ITU-R BS.1770-5] which can be found in [b-ITU-T G.191]. + +NOTE 4 – Should a video game software title be specifically designed for game play on a handheld or portable device with on board loudspeaker with insufficient dynamic range to appropriately reproduce a soundtrack scaled for $-23$ LUFS $\pm 2$ LU, an alternative $-18$ LUFS $\pm 2$ LU can be used, and the inclusion of a headphone output safety mode with reduction of 5 dB is strongly recommended (see clause 8.4). + +#### 9.3.2 Feature 2: Player dynamic range setup + +Video gameplay software should include an initial dynamic range test, which can establish what sounds are "loud" to the game player, and what sounds are at lowest levels of audibility based on the gameplayer's own audio system. + +This information is to be used to set the initial volume of the game title (avoiding starting the game at an uncomfortably loud volume) and/or calibrate a dynamic range compression mechanism which can be used to limit loud sounds throughout gameplay. The usefulness and implementation of dynamic range compression is for further study. + +#### 9.3.3 Feature 3: Tinnitus sounds removal + +Tinnitus sounds refer to sound effects that provide a simulation of tinnitus in response to a particular gameplay event, such as when a player is overwhelmed by an enemy during a fight or directly exposed to an explosion or flashbang. + +Should such sound effects exist within a particular game, an option should be provided to remove such sounds when first running the game. Once selected, the setting should be maintained unless the player opts to change the setting in the audio menu of the game. + +To better assess whether this feature is suitable, the game player could be asked if they have troublesome tinnitus (ringing or buzzing in their ears that is made worse by certain in-game audio sounds). + +#### 9.3.4 Feature 4: Passive gameplay audio reduction + +The video game software should include automated attenuation of game audio components of a video game during periods of passive, non-interactive gameplay by a minimum of 3 LUs (e.g., audio between rounds of a first-person shooter). + +The most common intended application of this definition will be towards sections of game play in between rounds of a multiplayer game, where a game player has been excluded from participating in the game until a new round begins. + +#### 9.3.5 Feature 5: Subtitles + +Video gameplay software should enable subtitles by default, which can facilitate gameplay at lower volumes. + +#### **9.3.6 Feature 6: Equalization presets** + +The video gameplay should include adjustable equalization presets which apply filters to reduce the mid and high frequency range. Reducing this particular frequency range can reduce harshness, spikes in intensity and ear fatigue. + +#### **9.3.7 Feature 7: Smart listening mode preset** + +In a similar way to how modern game menus manage graphics quality, the video game should combine and enable by default, relevant safe listening features available within that software title under one, easy to enable settings preset. + +A smart listening preset should be aimed at reducing the total sound dosage a game player will receive during a gameplay session, whilst minimally affecting the gameplay experience. + +#### **9.3.8 Feature 8: Audio Behaviour Telemetry** + +Game software developers should consider adding audio behaviour telemetry to their games, to help determine player listening behaviours, such as if/when the user changes app/system volume during gameplay, end-user settings for category volume sliders, time spent in gameplay sessions, etc. + +## **9.4 Headphone safety mode** + +Video game play software titles should provide a default headphone safety mode where the audio output of VGD for headphones is also intended for use with a speaker and the audio output level is not stored separately for each type of audio peripheral. + +The default headphone safety mode should be implemented when the video game play software title is capable of detecting that users are moving from free-field to headphones on the same audio output. In such instances an automatic volume reduction of at least 3 dB occurs. + +This feature is not required when the VGD on which the video gameplay software title is released provides an equivalent feature. + +# **10 Textual health warnings** + +See clause 11 in [ITU-T H.870] for a discussion on the importance of health communication to inform and empower the end user of listening devices, such as VGDs, to make the right listening choice through greater awareness and information. + +## **10.1 User guides and other written information** + +VGDs and video game software shall provide appropriate text-based information to game players in user guides or related electronic resources and websites. + +This information should go beyond a minimum set of instructions and aim to change behaviour. It should include: + +- a simple statement confirming that loud sounds can be a source of unsafe listening due to potential volume levels and duration of gameplay; +- a list of common auditory symptoms that can occur when unsafe listening has occurred, including tinnitus and loss of hearing sensitivity; +- simple instructions to incorporate safe listening into gameplay, including references to more information as well as any onboard features they can use. + +Such information should avoid technical or complex terminology, or references that are not easy to understand for a lay person. + +Appendix IV gives some examples of appropriate and insufficient warnings. + +## **10.2 Safe listening feature information** + +To ensure the effective use of safe listening features, VGDs or video gameplay software titles shall include information pertaining to the purpose and/or rationale of safe listening features available within their systems. + +NOTE – See Figures IV.5, IV.6, IV.7 and IV.8 for examples. + +# **11 Guidance on ancillary concerns** + +In addition to the direct effect of the transducer and the playing device connected to the VGD, there are several points that may need to be taken into account when a VGD is deemed safe. [b-ITU-T P.360] has some information in this regard. + +- When a headphone or an earphone is connected, there may be an acute noise (clicks and pops) due to transients (undesirable noise) in the system; +- Certain devices, when connected or "paired" together, give off a "confirmation-sound" to indicate that the devices are successfully paired. In such a case, the sound level of the confirmation sound may need to be in the safe range. + +Such sounds cannot be measured by a dosimeter on a VGD. + +Effort has been made to accommodate a transition between certain transducers, namely from loudspeaker to earphones/headphones, which may unintentionally cause an increase in volume under certain circumstances. See clauses 8.4 and 9.4. + +# Appendix I + +## Status report + +(This appendix does not form an integral part of this Recommendation.) + +WHO estimates that currently over 1.5 billion people worldwide experience some degree of hearing loss, nearly 30% of which is disabling hearing loss. It is estimated that with the current demographic trends, by 2050, there could be over 2.5 billion people with hearing loss globally. While this upward trend reflects changes in population demographics, it also underlines the need to address the preventable causes of hearing loss [b-WHO 2021]. + +One of the main avoidable causes of hearing loss is termed as "noise-induced" hearing loss, which refers to hearing loss due to overexposure of ears to sound energy, including recreational sources, such as music listened to over personal audio devices as well as exposure to sound from video gameplay activities. WHO estimates that more than one billion people are at risk of hearing loss due to unsafe listening practices, which makes it an issue of imminent public health concern, especially since even now, unaddressed hearing loss poses an annual global cost of USD 980 billion [b-WHO 2021]. + +Responding to the request of its Member States in the World Health Assembly resolution WHA70.13, WHO is working with other stakeholders to mitigate the risk of hearing loss due to unsafe listening by raising awareness and promoting safe listening behaviours. Making this change requires that users of video gameplay devices and related gameplay audio accessories should be able to access these devices that include safe listening features. + +To this end, WHO completed a background paper, reviewing approaches related to safe listening from video gameplay devices and esports activities, which included a systematic scoping review [b-Dillard 2024], international game player survey and stakeholder interviews. The results are found in the paper which is available at [b-WHO safe listening]. + +Other related background documents on the "Making Listening Safe" initiative can be found at . + +# Appendix II + +## Information on implementing dosimetry + +(This appendix does not form an integral part of this Recommendation.) + +### II.1 Dose estimation functionality for implementation in a video gameplay device + +The considerations that are found in Appendix II of [ITU-T H.870] apply with the understanding that references to personal audio systems (PAS) or personal audio devices (PAD) should be read as video gameplay devices (VGD). + +### II.2 Volume-limiting and messaging considerations + +While dose estimation implementation is comparable between this standard and [ITU-T H.870], some additional consideration of the immersive experience of video games should be considered when implementing sound dosage messages and warnings on VGDs, as the immersive experience can be affected by the arrival time of messages. + +As per clause 8.2.1, this standard recommends the VGD shall provide messages about general sound allowance use, such as time spent, sound allowance consumption and/or prediction of when sound allowance will be exceeded. Providing these warnings to the game player earlier than 100% CSD will provide the game player the opportunity to change behaviours and/or consider what other listening activities they have participated in that week to gauge whether they may already be at their weekly limit. + +As preserving immersion is also important to the gameplay experience, early warnings and access to general sound allowance allows players to be informed about their sound dose without disrupting their gameplay. See Figures II.1 to II.4 for examples of dosimetry safe listening messaging for VGDs. + +![Figure II.1: Sound Exposure information screen showing exposure status, volume dose graph, and informational text.](953203b3208524d293d4a65c0569324c_img.jpg) + +The figure shows a 'Sound Exposure information' screen. At the top, it says 'Sound Exposure information'. Below that, 'Exposure status: OK' is displayed. A bar chart titled 'Volume dose when playing' shows data for Sunday through Saturday, with a 'Total' bar on the right. The y-axis ranges from 0% to 90% in 10% increments. The bars show varying levels of volume dose, with the 'Total' bar being the highest, around 85%. To the right of the chart, there is text explaining that the device has detected listening behaviour over the last seven days, which is estimated to be acceptable. It also warns that this only measures listening on this system and doesn't include other activities. A link to sonrosoft.com/hearing is provided. At the bottom, there is a prompt: 'I HAVE SEEN THIS INFORMATION (Press □)'. + +| Day | Volume Dose (%) | +|-----------|-----------------| +| Sunday | 25 | +| Monday | 30 | +| Tuesday | 5 | +| Wednesday | 15 | +| Thursday | 5 | +| Friday | 20 | +| Saturday | 25 | +| Total | 85 | + +Figure II.1: Sound Exposure information screen showing exposure status, volume dose graph, and informational text. + +Figure II.1 – Dosimetry information: Safe/OK status when voluntarily accessed from a sound menu + +![Bar chart showing volume dose over time. The y-axis ranges from 0% to 120% in 20% increments. The x-axis shows time intervals: 15:00, 15:05, 15:10, 15:15, 15:20, 15:25, 15:30, 15:35. Bars for 15:00, 15:05, 15:10, 15:15, 15:20, 15:25, and 15:30 are blue and below 40%. The bar for 15:35 is red and reaches approximately 100%.](a2dcc4a0703102026ec86e82caa4985e_img.jpg) + +### Sound Exposure information + +**Exposure status: At Risk** + +Volume dose when playing + +..... + +Your Sonrosoft PlayBox has detected listening behaviour over the **last seven days** which is estimated to be **at risk**. + +In order to protect your hearing, we strongly recommend playing at lower volumes. + +For more information about hearing loss and what you can do about it, visit [sonrosoft.com/hearing](http://sonrosoft.com/hearing) + +Set volume to safe level (Press □) + +Continue playing at current volume (not recommended) (Press X) + +Bar chart showing volume dose over time. The y-axis ranges from 0% to 120% in 20% increments. The x-axis shows time intervals: 15:00, 15:05, 15:10, 15:15, 15:20, 15:25, 15:30, 15:35. Bars for 15:00, 15:05, 15:10, 15:15, 15:20, 15:25, and 15:30 are blue and below 40%. The bar for 15:35 is red and reaches approximately 100%. + +**Figure II.2 – Dosimetry information: Unsafe/Not OK status when voluntarily accessed from a sound menu** + +![](7119b28e39fa3784606bf8b8f44e4f9d_img.jpg) + +### VIDEO GAME + +**Safe listening warning** + +Your Sonrosoft PlayBox has detected listening behaviour over the **last seven days** which is likely to be unsafe. If you continue to listen at these volumes so frequently you could be risking permanent hearing loss. + +For more information, see the hearing section of the Sonrosoft PlayBox Accessibility menu. + +For more information about hearing loss and what you can do about it, visit [sonrosoft.com/hearing](http://sonrosoft.com/hearing) + +..... + +Press X to accept the risk to your hearing and continue listening at current volume + +Press O to activate a safer listening mode (recommended) + +**Figure II.3 – Dosimetry information: Warning message shown upon exceeding 100% CSD** + +![Screenshot of the VGD initial load screen showing navigation menus, a 'WELCOME' header, a game carousel, and dosimetry icons for battery (100%) and volume (75%) in the top right corner.](008b6e24fa6aef654a11223efed035dd_img.jpg) + +The image shows a screenshot of a video game's initial load screen. The background is dark with a diagonal light grey stripe. At the top left, there's a logo, followed by menu items: HOME, STORE, LIBRARY, and SETTINGS. In the top right corner, there are two icons: a battery icon labeled '100 %' and an ear icon labeled '75%'. The word 'WELCOME' is centered in large, bold, white capital letters. Below it, a horizontal carousel displays five game covers, flanked by left and right arrow buttons. The word 'SONY' is written vertically on the left and right sides of the carousel. At the bottom right, there's a '....' icon. + +Screenshot of the VGD initial load screen showing navigation menus, a 'WELCOME' header, a game carousel, and dosimetry icons for battery (100%) and volume (75%) in the top right corner. + +Figure II.4 – Dosimetry information: VGD initial load screen with safe listening icon and dosage indicator in the top right corner + +# Appendix III + +## Example of safe listening warnings + +(This appendix does not form an integral part of this Recommendation.) + +### III.1 Safe listening warnings: Example of a safe listening warning upon initial load of a video gameplay software title + +Compliant game software titles include a warning, during the first load of the game, as illustrated in Figure III.1. This warning should include the following information: + +- A warning to the game player of potential risk to hearing from exposure to loud sounds; +- Examples of potential symptoms to be aware of that indicate unsafe listening. + +![Figure III.1: Initial load screen warning example. A screenshot of a video game load screen with a dark background. At the top, the text 'VIDEO GAME LOAD SCREEN' is displayed in large, white, uppercase letters. Below this, a section titled 'Safe listening warning' is highlighted with a vertical orange line to its left. The warning text explains that video gaming can cause unsafe listening and permanent hearing damage, especially when combined with other activities. It cites WHO safe limits (80 dB for 40 hours for adults, 75 dB for children) and notes that the limit halves for every 3 dB increase. A bulleted list of signs of hearing damage includes ringing or buzzing, loss of sensitivity, and recommendations from family and friends. A link to 'listensafe.org' is provided at the bottom. A series of five white dots is visible on the left side of the screen.](aa92b0cf694be554991b65dbd284f9d4_img.jpg) + +**VIDEO GAME LOAD SCREEN** + +**Safe listening warning** + +Video gaming can be a source of unsafe listening, which can lead to permanent hearing damage, especially when combined with other listening activities. + +The World Health Organization (WHO) has established a safe limit of 80 dB for 40 hours a week for adults, and 75 dB for children. This safe limit halves for every 3 dB increase (equivalent to a few increments on a typical volume control). + +Watch out for the signs of hearing damage: + +- Ringing or buzzing in the ear after gameplay +- Loss of hearing sensitivity after gameplay +- Recommendations from family and friends to turn the volume down + +For more information, visit [listensafe.org](https://listensafe.org) + +Figure III.1: Initial load screen warning example. A screenshot of a video game load screen with a dark background. At the top, the text 'VIDEO GAME LOAD SCREEN' is displayed in large, white, uppercase letters. Below this, a section titled 'Safe listening warning' is highlighted with a vertical orange line to its left. The warning text explains that video gaming can cause unsafe listening and permanent hearing damage, especially when combined with other activities. It cites WHO safe limits (80 dB for 40 hours for adults, 75 dB for children) and notes that the limit halves for every 3 dB increase. A bulleted list of signs of hearing damage includes ringing or buzzing, loss of sensitivity, and recommendations from family and friends. A link to 'listensafe.org' is provided at the bottom. A series of five white dots is visible on the left side of the screen. + +Figure III.1 – Initial load screen warning example + +### III.2 Safe listening warnings: Example of safe listening warning during gameplay + +At a convenient in-game moment (e.g., at the end of a round of gameplay, after completing a level, after losing a life, when pausing game, etc.) a warning message is displayed. + +In the example in Figure III.2, the warning is being displayed during pause screen, and notifies the game player of the amount of time they have been exposed to sound in this particular game play session. + +![A screenshot of a video game pause screen. The title 'PAUSE SCREEN' is at the top left. On the left is a menu with options: RESUME GAME, CONTROL MENU, DISPLAY MENU, GRAPHICS MENU, SOUND MENU, and a '....' icon. On the right is a 'Safe listening warning' box. It states: 'Your current gameplay session has now lasted longer than two hours. Now may be a good time for a break to rest your hearing. Watch out for the signs of hearing damage: • Ringing or buzzing in the ear after gameplay • Loss of hearing sensitivity after gameplay • Recommendations from family and friends to turn the volume down. For more information, visit listen safe.org'.](84cebc242b1af66723a02cdf67fc98c9_img.jpg) + +A screenshot of a video game pause screen. The title 'PAUSE SCREEN' is at the top left. On the left is a menu with options: RESUME GAME, CONTROL MENU, DISPLAY MENU, GRAPHICS MENU, SOUND MENU, and a '....' icon. On the right is a 'Safe listening warning' box. It states: 'Your current gameplay session has now lasted longer than two hours. Now may be a good time for a break to rest your hearing. Watch out for the signs of hearing damage: • Ringing or buzzing in the ear after gameplay • Loss of hearing sensitivity after gameplay • Recommendations from family and friends to turn the volume down. For more information, visit listen safe.org'. + +**Figure III.2 – An example of Safe listening warning in shown in the pause menu** + +### **III.3 Safe listening warnings: Example of safe listening warning upon exit of the game** + +For warnings placed upon game exit, a final message should be displayed prompting the gamer to check their hearing status with simple messaging. For example, as illustrated in Figure III.3: + +- Are your ears ringing? +- Does your hearing seem muffled after your latest gameplay session? +- Has anyone in your household mentioned your video game volume is too loud? +- Did you know: hearing damage can occur without any symptoms? + +The warning should display for a reasonable amount of time to allow the game player sufficient time to read the displayed content, and could include a call to action to confirm understanding, e.g. "I have seen this message". + +![Screenshot of an 'EXIT SCREEN' from a video game. The screen is black with white text. At the top left, 'EXIT SCREEN' is written in large, bold, white capital letters. In the center, a question 'Are you sure you want to exit?' is displayed in white, with 'YES' in orange and 'NO' in white below it. To the left of this question is a vertical orange line. Below the question, the heading 'Safe listening warning' is in white. Underneath, a paragraph explains that hearing damage can occur without symptoms and lists three signs: ringing ears, muffled hearing, or others mentioning the volume is too loud. A link to 'listensafe.org' is provided at the bottom. On the left side of the screen, there are five white dots arranged vertically.](7adda64806b35031fadb1fd5a227a9f8_img.jpg) + +**EXIT SCREEN** + +Are you sure you want to exit? +**YES** | NO + +**Safe listening warning** + +Hearing damage can occur without any symptoms, but you can still watch out for the signs that you may have been listening too loudly: + +- Are your ears ringing? +- Does your hearing seem muffled after your latest gameplay session? +- Has anyone mentioned your video game volume is too loud? + +For more information, visit [listensafe.org](https://listensafe.org) + +Screenshot of an 'EXIT SCREEN' from a video game. The screen is black with white text. At the top left, 'EXIT SCREEN' is written in large, bold, white capital letters. In the center, a question 'Are you sure you want to exit?' is displayed in white, with 'YES' in orange and 'NO' in white below it. To the left of this question is a vertical orange line. Below the question, the heading 'Safe listening warning' is in white. Underneath, a paragraph explains that hearing damage can occur without symptoms and lists three signs: ringing ears, muffled hearing, or others mentioning the volume is too loud. A link to 'listensafe.org' is provided at the bottom. On the left side of the screen, there are five white dots arranged vertically. + +**Figure III.3 – Safe listening warning on exit of video game** + +# Appendix IV + +## Examples of textual information provided to the user + +(This appendix does not form an integral part of this Recommendation.) + +### IV.1 Textual information provided with video gameplay devices + +- Provide a simple statement confirming that activities which include exposure to loud sounds can lead to hearing damage; +- Provide a list of common auditory symptoms that can indicate hearing damage, including tinnitus and loss of hearing sensitivity; +- The message should also indicate that absence of these symptoms does not necessarily indicate an absence of hearing damage; +- Provide simple instructions to incorporate safe listening into video gameplay, including references to more information as well as any onboard features they can use; +- Avoid technical or complex terminology, or references that are not easy to understand for a lay person. + +Examples are illustrated in Figures IV.1 to IV.4. + +![Figure IV.1: Example of an insufficient text-based warning. A box titled 'Hearing Damage' containing a bullet point with an ear icon and the text 'To prevent possible hearing damage, do not listen at high volume levels for long periods.' Ear icon](474827f04e18dc4a3b073e8785813a76_img.jpg) + +**Hearing Damage** + +- To prevent possible hearing damage, do not listen at high volume levels for long periods. + +Figure IV.1: Example of an insufficient text-based warning. A box titled 'Hearing Damage' containing a bullet point with an ear icon and the text 'To prevent possible hearing damage, do not listen at high volume levels for long periods.' Ear icon + +Figure IV.1 – Example of an insufficient text-based warning + +![Figure IV.2: Example of an overly technical example of a text-based warning. A box titled 'Using headphones or earphones' containing a paragraph about connectors, a 'CAUTION:' section with bold text about sound pressure and equalizer settings, and a detailed paragraph about EN 50332-2 specifications.](53d30aa4ecaa092477cb3ef6ec874bec_img.jpg) + +**Using headphones or earphones** + +If your computer has both a headphone connector and an audio-out connector, always use the headphone connector for headphones (also called a headset) or earphones. + +**CAUTION:** +**Excessive sound pressure from earphones and headphones can cause hearing loss. Adjustment of the equalizer to maximum increases the earphone and headphone output voltage and the sound pressure level. Therefore, to protect your hearing, adjust the equalizer to an appropriate level.** + +Excessive use of headphones or earphones for a long period of time at high volume can be dangerous if the output of the headphone or earphone connectors do not comply with specifications of EN 50332-2. The headphone output connector of your computer complies with EN 50332-2 Sub clause 7. This specification limits the computer's maximum wide band true RMS output voltage to 150 mV. To help protect against hearing loss, ensure that the headphones or earphones you use also comply with EN 50332-2 (Clause 7 limits) for a wide band characteristic voltage of 75 mV. Using headphones that do not comply with EN 50332-2 can be dangerous due to excessive sound pressure levels. + +Figure IV.2: Example of an overly technical example of a text-based warning. A box titled 'Using headphones or earphones' containing a paragraph about connectors, a 'CAUTION:' section with bold text about sound pressure and equalizer settings, and a detailed paragraph about EN 50332-2 specifications. + +Figure IV.2 – Example of an overly technical example of a text-based warning + +#### **Warning: Protect Your Hearing During Gameplay!** + +Video gaming and esports activities can provide exciting and immersive experiences, but it's important to be aware that they can also pose risks to your hearing due to high volume levels and extended gameplay. To ensure your auditory well-being, follow these guidelines: + +#### **Recognize the common signs of hearing damage:** + +- Tinnitus: If you experience ringing, buzzing, or hissing sounds in your ears, it could be a sign of auditory damage. +- Loss of Hearing Sensitivity: If you find it harder to hear quiet sounds or conversations, take action to prevent further hearing loss. + +#### **Safe Listening Practices:** + +- Adjust Volume: Keep your gaming device's volume at a comfortable level. If you can't hear external sounds while playing, it's too loud. +- Take Breaks: Give your ears a break by taking 5-10 minute breaks every hour of gameplay. This helps reduce strain on your hearing. +- Use Headphones Wisely: Opt for over-ear headphones that provide better noise isolation at lower volumes. +- Enable Volume Limiting: Check your gaming device's settings to enable this feature. +- Listen to Your Body: If you notice discomfort, pain, or auditory symptoms, take a break and allow your ears to recover. + +#### **Get More Information:** + +- Refer to your device's user manual or visit the manufacturer's website for details on safe listening practices. +- Explore resources from reputable sources like the World Health Organization (WHO) and hearing health organizations. + +#### **Remember, responsible gameplay includes looking out for your hearing.** + +By incorporating safe listening practices into your gameplay routine, you can enjoy a world of video games while safeguarding your hearing for years to come. + +**Figure IV.3 – Example of a sufficient text-based warning** + +![PlayBox logo featuring a stylized game console with a joystick and buttons, set against a red background with a yellow and black border. The word 'PLAYBOX' is written in a bold, yellow, blocky font below the console.](19fd552435a80d0ffda518b710d16908_img.jpg) + +PlayBox logo featuring a stylized game console with a joystick and buttons, set against a red background with a yellow and black border. The word 'PLAYBOX' is written in a bold, yellow, blocky font below the console. + +#### PlayBox User guide + +#### **Warning: protect your hearing while gaming!** + +Playing video games can be really fun, but loud sounds can hurt your hearing if you play for too long. Follow these tips to keep your ears healthy: +Watch for signs of hearing damage: + +- **Ringing or buzzing:** if you hear ringing or buzzing in your ears during or after gameplay, it could mean your hearing is being damaged. +- **Hard to hear:** if you struggle to hear quiet sounds or conversations, take action to protect your hearing. + +#### **Safe listening tips:** + +- **Keep the volume down!** Set your game volume at a comfortable level. If you can't hear external noises, it might be probably too loud. +- **Take breaks:** give your ears a rest by taking 5-10 minute breaks every hour. This helps prevent ear strain. +- **Choose headphones carefully:** use over-ear headphones that block out noise. These can help you play at lower volumes. +- **Use volume limits:** check your device settings to limit the maximum volume. +- **Listen to your body:** if your ears hurt or you notice hearing problems, take a break and let your ears rest. Get more info: +- **Check the manual:** If using other audio devices such as headphones or earphones, check the manual or the manufacturer's website for safe listening tips. +- **Visit trusted sources:** Find more information from places like the World Health Organization (WHO) and other hearing health organizations. + +**Remember:** playing safely means protecting your ears. By following these tips, you can enjoy gaming without damaging your hearing. + +Figure IV.4 – Alternative example of a sufficient text-based warning + +### IV.2 Safe listening feature information examples for within video gameplay software titles + +To ensure the effective use of any safe listening features available within a video game software title, compliant titles shall also include necessary supporting information within the video game itself to inform, guide and encourage the gameplayer of any features that have been included for the purpose of safe listening. + +At the point of activation and access (for example an in-game sound or audio menu), software titles shall: + +- Provide a short description of the safe listening feature, including rationale and purpose with regards to safe listening; +- Provide guidance to the gameplayer how to use the safe listening feature; +- Information should avoid technical or complex terminology, or references that are not easy to understand for a lay person, or younger audiences. + +Examples are illustrated in Figures IV.5 to IV.8. + +![Screenshot of a video game menu titled 'SAFE LISTENING FEATURES' showing information about Tinnitus Sounds.](33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg) + +The screenshot shows a dark menu with the title "SAFE LISTENING FEATURES" at the top. On the left, a list of menu items includes "SOUND CATEGORY CONTROLS", "TINNITUS SOUNDS" (highlighted), "DYNAMIC RANGE TEST", and "PASSIVE GAMEPLAY AUDIO", followed by a "....." separator. The right side features a section titled "Tinnitus Sounds" with a description: "Tinnitus is a ringing or buzzing sound which can occur when you are exposed to loud sounds. There are moments during this game when sound effects will play for the purpose of simulating tinnitus. If you experience tinnitus in your daily life and find that these types of sound effects cause your own tinnitus to worsen, it is recommended that you enable this feature." Below this are two buttons: "DISABLE TINNITUS SOUNDS" (with an orange dot) and "ENABLE TINNITUS SOUNDS". + +Screenshot of a video game menu titled 'SAFE LISTENING FEATURES' showing information about Tinnitus Sounds. + +Figure IV.5 – Safe listening feature information: tinnitus sounds + +![Screenshot of a video game menu titled 'SAFE LISTENING FEATURES' showing information about Sound Category Controls.](f88d85789030ae43f43d61fe4ac3e64e_img.jpg) + +The screenshot shows a dark menu with the title "SAFE LISTENING FEATURES" at the top. On the left, a list of menu items includes "SOUND CATEGORY CONTROLS" (highlighted), "TINNITUS SOUNDS", "DYNAMIC RANGE TEST", and "PASSIVE GAMEPLAY AUDIO", followed by a "....." separator. The right side features a section titled "Sound Category Controls" with a description: "This game provides you with control over various sounds within the soundtrack. The purpose of this feature is to allow you to reduce sounds that you may find too loud or enhance sounds that are important to your gameplay. It is recommended that you use this feature if you are having trouble hearing a particular sound, instead of simply raising the entire volume level." Below this is a button labeled "SET SOUND CATEGORY CONTROLS" in orange text. + +Screenshot of a video game menu titled 'SAFE LISTENING FEATURES' showing information about Sound Category Controls. + +Figure IV.6 – Safe listening feature information: sound category volume controls + +![Screenshot of the 'SAFE LISTENING FEATURES' menu in a video game. The menu is titled 'SAFE LISTENING FEATURES' and lists several options: SOUND CATEGORY CONTROLS, TINNITUS SOUNDS, DYNAMIC RANGE TEST (highlighted), and PASSIVE GAMEPLAY AUDIO. The 'Dynamic Range Test' section provides information about balancing sounds for personal comfort and includes a 'BEGIN THE TEST' button.](3fec67008a13a4bccaf6914c862b2e42_img.jpg) + +**SAFE LISTENING FEATURES** + +SOUND CATEGORY CONTROLS +TINNITUS SOUNDS +**DYNAMIC RANGE TEST** +PASSIVE GAMEPLAY AUDIO + +..... + +**Dynamic Range Test** + +To ensure sounds played within this game are balanced to your personal comfort levels and audio system, this game includes a feature that allows you to indicate how you hear. + +Completing this test will allow softer sound effects to be audible and louder sounds to be set at a comfortable level. + +**BEGIN THE TEST** + +Screenshot of the 'SAFE LISTENING FEATURES' menu in a video game. The menu is titled 'SAFE LISTENING FEATURES' and lists several options: SOUND CATEGORY CONTROLS, TINNITUS SOUNDS, DYNAMIC RANGE TEST (highlighted), and PASSIVE GAMEPLAY AUDIO. The 'Dynamic Range Test' section provides information about balancing sounds for personal comfort and includes a 'BEGIN THE TEST' button. + +Figure IV.7 – Safe listening feature information: dynamic range test + +![Screenshot of the 'SOUND MENU' in a video game. The menu shows various settings, all of which are currently set to 'ON': SMART LISTENING MODE, AUDIO OUTPUT SCALING, TINNITUS SOUNDS REMOVAL, SOUND REDUCTION BETWEEN ROUNDS, and EQUALIZATION PRESET. The menu is titled 'SOUND MENU' and includes the text 'ACME: THE VIDEO GAME' at the bottom.](f3ce2d7158eb708e3487b8e35415db35_img.jpg) + +VIDEO GAME ACME + +**SOUND MENU** + +VIDEO GAME MENU + +SMART LISTENING MODE < ON > + +- AUDIO OUTPUT SCALING < ON > +- TINNITUS SOUNDS REMOVAL < ON > +- SOUND REDUCTION BETWEEN ROUNDS < ON > +- EQUALIZATION PRESET < ON > + +ACME: THE VIDEO GAME + +..... + +Screenshot of the 'SOUND MENU' in a video game. The menu shows various settings, all of which are currently set to 'ON': SMART LISTENING MODE, AUDIO OUTPUT SCALING, TINNITUS SOUNDS REMOVAL, SOUND REDUCTION BETWEEN ROUNDS, and EQUALIZATION PRESET. The menu is titled 'SOUND MENU' and includes the text 'ACME: THE VIDEO GAME' at the bottom. + +Figure IV.8 – Safe listening feature information: example of smart listening mode + +# Appendix V + +## Safe listening for live esports venues and events + +(This appendix does not form an integral part of this Recommendation.) + +The text below is adapted from the WHO Global standard for safe listening venues and events, [WHO, 2022] and the [b-HSTP-SLD-Venue]. + +### V.1 Live esports event background + +A live esports event is organized for the purpose of hosting competitive matches in front of a live audience. It involves: + +- the assembly of professional and/or amateur players and teams to compete in a tournament or match; +- the utilization of video game consoles, PCs, or other gameplay devices as the primary platform for gameplay; +- the incorporation of a stage and visual display to present the ongoing gameplay and related content to the live audience; +- the implementation of an audio system that delivers in-game sound effects, commentator commentary, crowd reactions, and event-related announcements; and +- the provision of seating or standing areas for the live audience to watch the matches in person. + +Examples of ELEs encompass international esports tournaments, local competitive events and exhibition matches that bring together professional and amateur players for high-stakes competition. ELEs showcase a range of esports genres, including multiplayer online battle arena (MOBA), first-person shooter (FPS), real-time strategy (RTS) and more. + +These provisions do not apply to: + +- recreational video gameplay sessions or casual gatherings; +- non-competitive video gameplay events conducted in an unstructured way; +- competitive esports events without live in-person component, e.g. streamed online only. + +NOTE 1 – This exemption recognizes the distinct nature of esports events and their focus on competitive gameplay. Non-competitive video gameplay events are subject to different considerations. + +The future exploration of video gameplay and virtual reality integration within the esports live event setting is anticipated for subsequent study. + +NOTE 2 – The recommendations made in this document apply to video gameplay hardware and software (game titles) used during esports. The external sound in the esports venue (other than that heard through the video gameplay hardware and software) is outside the scope of this document. Features of a safe listening entertainment venue are covered in [b-HSTP-SLD-Venue]. + +### V.2 Main features for live esports events + +[b-HSTP-SLD-Venue] presents a systematic and comprehensive approach to achieving safe listening practices within live events and venues. It methodically balances the imperative of ensuring auditory safety with the desire to preserve the entertainment value inherent in live performances. This framework serves as the foundation upon which the subsequent recommendations for volume control in esports live event audiences are built. + +#### V.2.1 Sound level limit + +An upper limit of 100 dB $L_{Aeq, 15\ min}$ shall be imposed for the venue, keeping sound safe and enjoyable for the audience. + +#### **V.2.2 Sound level monitoring** + +Live monitoring of sound levels shall be performed by a designated staff member using calibrated equipment. + +#### **V.2.3 Venue acoustics and sound systems** + +Sound system and venue acoustics shall be optimized ensuring safe listening and improved sound quality. + +#### **V.2.4 Personal hearing protection** + +Hearing protection, such as earplugs, along with appropriate instructions should be available to audience members. + +#### **V.2.5 Quiet zones** + +**Esports live events shall include quiet rooms** for competitors and audience members. In addition, adequate breaks shall be taken between the competitive rounds when sound levels shall be kept below 80 dBA, in order to provide a break from sound exposure. + +#### **V.2.6 Appropriate training and information** + +Esports players, audience members and venue staff shall be provided information to make them aware of practical steps they can take to ensure safe listening. + +## Bibliography + +- [b-ITU-T G.191] Recommendation ITU-T G.191 (2024), *Software tools for speech and audio coding standardization*. +- [b-ITU-T P.10] Recommendation ITU-T P.10 (2024), *New definitions for inclusion in Recommendation ITU-T P.10/G.100*. +- [b-ITU-T P.58] Recommendation ITU-T P.58 (2023), *Head and torso simulator for telephonometry*. +- [b-ITU-T P.360] Recommendation ITU-T P.360 (2006), *Efficiency of devices for preventing the occurrence of excessive acoustic pressure by telephone receivers and assessment of daily noise exposure of telephone users*. +- [b-ITU-R BS.1770-5] Recommendation ITU-R BS.1770-5 (2023), *Algorithms to measure audio programme loudness and true-peak audio level*. +- [b-Dillard 2024] Lauren K. Dillard, Peter Mulas, Carolina Der, Xinxing Fu, Shelly Chadha, *Risk of sound-induced hearing loss from exposure to video gaming or esports: a systematic scoping review*, BMJ Public Health 2024; 2:e000253. doi:10.1136/bmjph-2023-000253. +- [b-EBU R 128] EBU Recommendation R 128 (2023), *Loudness normalisation and permitted maximum level of audio signals*. + +- [b-FSTP-SLD-UC] Technical Paper ITU-T FSTP-SLD-UC (2022), *Gap analysis: Use cases of safe listening devices*. + +- [b-HSTP-SLD-Venue] Technical Paper ITU-T HSTP-SLD-Venue (2024), *Guideline on safe listening at venues and events*. [URL to be defined] +Technically aligned publication with WHO (2022) "WHO global standard for safe listening venues and events". + +- [b-ISO 9241-210] ISO 9241-210:2019, *Ergonomics of human-system interaction, part 210: Human-centred design for interactive systems*. + +- [b-ISO 11904-1] ISO 11904-1:2002, *Acoustics – Determination of sound immission from sound sources placed close to the ear – Part 1: Technique using a microphone in a real ear (MIRE technique)*. +- [b-ISO 11904-2] ISO 11904-2:2021, *Acoustics – Determination of sound immission from sound sources placed close to the ear. Part 2: Technique using a manikin*. + +- [b-ISO 24508] ISO 24508:2019, *Ergonomics – Accessible design – Guidelines for designing tactile symbols and characters*. +- [b-ISO/TC 159/SC 4] ISO Technical Committee 159, Sub-Committee 4: *Ergonomics of human-system interaction*, + (visited 2024-08-28) +- [b-NIOSH] Chan, Henry S. *Occupational noise exposure; criteria for a recommended standard*. (1998). NIOSH Numbered Publications + + +- [b-Smith 2000] Smith P.A., Davis A., Ferguson M., Lutman M.E., *The prevalence and type of social noise exposure in young adults in England*, Noise Health, 2000; 2(6):41-56. PMID: 12689478. +- [b-Sony ASWG-R001] Sony Worldwide Studios Audio Standards Working Group (ASWG), Recommendation ASWG-R001 v1.10, *Average loudness and peak levels of audio content on Sony computer entertainment platforms*, August 2013. +- [b-Tang 2023] Tang D., Sum R.K., Li M., Ma R., Chung P., Ho R.W., *What is esports? A systematic scoping review and concept analysis of esports*, Heliyon, 2023 Dec 3; 9(12):e23248. [10.1016/j.heliyon.2023.e23248](https://doi.org/10.1016/j.heliyon.2023.e23248) +- [b-TECH 3341] EBU TECH 3341 Supplementary information for R128 (2023), "*EBU Mode*" metering to supplement Loudness normalisation. +- [b-WHO 2021] World Health Organization, *World Report on Hearing* (2021). +- [b-WHO 2022] World Health Organization, *Global standard for safe listening for live venues and events* (2022). +- [b-WHO safe listening] World Health Organization, Safe listening in video gaming & esports - A World Health Organization background study (2023). [https://cdn.who.int/media/docs/default-source/ncds/sdr/deafness-and-hearing-loss/safe-listening-in-video-gaming-and-esports.pdf?sfvrsn=cccd86e2\\_4](https://cdn.who.int/media/docs/default-source/ncds/sdr/deafness-and-hearing-loss/safe-listening-in-video-gaming-and-esports.pdf?sfvrsn=cccd86e2_4) + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file